Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Instructions how to update AP snakemake #433

Open
jkosinski opened this issue Oct 16, 2024 · 2 comments
Open

Instructions how to update AP snakemake #433

jkosinski opened this issue Oct 16, 2024 · 2 comments
Assignees
Labels
documentation Improvements or additions to documentation
Milestone

Comments

@jkosinski
Copy link
Collaborator

Could you add, perhaps here:


what to do if a user has:

  1. deployed the pipeline with snakedeploy deploy-workflow
  2. edited config.yaml and added the list files
  3. run the pipeline and sth did not work (eg. bug or whatever
    and then we fixed the AP and then the user wants to
  4. update the AP snakemake and re-run in the same folder and reusing the previous config.yaml

From the provided instruction, I would just re-run snakedeploy deploy-workflow but would they work and not delete my config and list files?

(I am exactly in this situation right now ;-)

@jkosinski jkosinski added the documentation Improvements or additions to documentation label Oct 16, 2024
@jkosinski jkosinski added this to the Priority1 milestone Oct 16, 2024
@DimaMolod
Copy link
Collaborator

I think if you use --branch main, you just re-run without even re-deploying. And if you use some release tag, you'll need to re-deploy to the new folder using the new tag (given there is one after we fixed a bug) and then copy the config.yaml file into the new config folder. Is that correct, @maurerv?

@maurerv
Copy link
Collaborator

maurerv commented Oct 16, 2024

Things should be stable before you deploy :)

Running snakedeploy will always remove and fetch all files that are included in the particular tag. So your changes to config.yaml and sample_sheet.csv will be overwritten

@DimaMolod DimaMolod mentioned this issue Oct 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
None yet
Development

No branches or pull requests

3 participants