-
Notifications
You must be signed in to change notification settings - Fork 74
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
Rename mutable to managed #109
base: main
Are you sure you want to change the base?
Conversation
To stay consistent with Galaxy's terminology
Also, ref galaxyproject/galaxy#9362 |
@@ -12,7 +12,7 @@ galaxy_manage_paths: no | |||
galaxy_manage_clone: yes | |||
galaxy_manage_download: no | |||
galaxy_manage_static_setup: yes | |||
galaxy_manage_mutable_setup: yes | |||
galaxy_manage_managed_setup: yes |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
galaxy_manage_managed_setup: yes | |
galaxy_manage_managed_setup: "{{ galaxy_manage_mutable_setup | default(yes) }}" |
maybe something like this to ensure that people who don't read the upgrade notice can use the legacy value? @natefoo what are your opinions on that. "Read the release notes or else?"
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have no objections. @natefoo - up to you?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, and we'll need to default all the other changed vars as well.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Coolie. Sorry for the extra work, but figure it'll be a bit more userfriendly.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It shouldn't be too bad as you can do:
galaxy_managed_data_dir: "{{ galaxy_mutable_data_dir }}"
Rather than defaulting each instance of its usage. Hopefully that all plays nicely with the layout stuff.
To stay consistent with Galaxy's terminology
Note: "manage 'managed'" is rather awkward and "manage 'galaxy-managed'" may be less so; but in the big picture 'galaxy-managed' creates more inconsistency even across this repo alone, so it's not worth it, IMHO.
Ref: galaxyproject/galaxy#9444