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

running role on its own wiped top_links #5

Closed
atarkowska opened this issue Feb 22, 2017 · 6 comments
Closed

running role on its own wiped top_links #5

atarkowska opened this issue Feb 22, 2017 · 6 comments

Comments

@atarkowska
Copy link
Member

atarkowska commented Feb 22, 2017

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 mode

@manics
Copy link
Member

manics commented Feb 22, 2017

@atarkowska
Copy link
Member Author

atarkowska commented Feb 22, 2017

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

@manics
Copy link
Member

manics commented Feb 22, 2017

Those vars/options are set in a playbook in another repo, it's unrelated to this role.

@manics
Copy link
Member

manics commented Mar 9, 2017

I think the best solution to this is ome/design#70

@joshmoore
Copy link
Member

@aleksandra-tarkowska : you ok with the status of this in ome/design#70 ?

@joshmoore
Copy link
Member

@manics: I'm assuming this is good to close then. Can re-open if you think this has any remaining TODOs.

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

3 participants