-
Notifications
You must be signed in to change notification settings - Fork 7
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
Add in-place upgrades #242
Conversation
TODO:
|
1c3e3df
to
31a9651
Compare
This reverts commit 39e5075.
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.
Left some extra suggestions. I will review the core of the upgrade lib later today.
@Mehdi-Bendriss I haven't updated the guards for non-upgrade event handlers since #190—let me know if there's anything I should update Given that the scope of this PR is upgrades for simple deployments only, not sure what's desired here |
Co-authored-by: phvalguima <pedro.guimaraes@canonical.com>
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.
Thanks Carl! Great work! I do not have major concerns here, only a few comments
Spin of #242, [following this discussion](#242 (review)). Adds an integration test to ensure we have the correct version in the `workload_version` file. --------- Co-authored-by: Carl Csaposs <carl.csaposs@canonical.com>
Ported from canonical/mysql-router-operator#88
upgrade.py, machine_upgrade.py and event handlers in charm.py are mostly shared with upgrade.py, machine_upgrade.py and event handlers in abstract_charm.py/machine_charm.py in MySQL Router VM charm
Non-upgrade event handler guards implemented per https://docs.google.com/spreadsheets/d/1_qjINUoj5Mi7PlXhCdpwQ0170bIZSgpvNFMAnTOtuQw/edit#gid=0