-
Notifications
You must be signed in to change notification settings - Fork 13
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
running role on its own wiped top_links #5
Comments
It was run with a config file that explicitly sets it to |
I need to disagree, it was run with default group_vars, so I would expect not to change any state. Ideally would be to provide clear explanation what extra should be included on top of the server role to not change the state |
Those vars/options are set in a playbook in another repo, it's unrelated to this role. |
I think the best solution to this is ome/design#70 |
@aleksandra-tarkowska : you ok with the status of this in ome/design#70 ? |
@manics: I'm assuming this is good to close then. Can re-open if you think this has any remaining TODOs. |
Running role https://github.com/IDR/deployment/pull/9/files#diff-859e93e6ca33aa77acc85c0429403580R55 with default deployment vars in a upgrade context wiped top_links
omero.web.ui.top_links=[]
. Would be really nice if existing config is not affected in an upgrade modeThe text was updated successfully, but these errors were encountered: