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

Why preventing mutable configurations from being overwritten? #179

Closed
drosofff opened this issue Jan 6, 2023 · 1 comment
Closed

Why preventing mutable configurations from being overwritten? #179

drosofff opened this issue Jan 6, 2023 · 1 comment

Comments

@drosofff
Copy link
Member

drosofff commented Jan 6, 2023

# force: no in the following 2 tasks will not overwrite existing configs

If I understand correctly, to change a mutable configuration using this role, you'll have first to delete the current config from the host before replaying the playbook ?

@hexylena
Copy link
Member

hexylena commented Jan 6, 2023

Yes, this is correct. The mutable directory, once created, is more or less "maintained" by a lot of different galaxy processes. Manually changing the files is possible, but if we overwrote the file on deploy, we'd be constantly losing changes Galaxy is trying to make to those files (e.g. installation of genomes/etc)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants