-
Notifications
You must be signed in to change notification settings - Fork 16
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
[DPE-5588] Check against invalid arch #539
base: main
Are you sure you want to change the base?
Conversation
125f6ab
to
e3cab7b
Compare
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.
we may want to reconsider our approach here for in-place upgrades/rollbacks
(i.e. if someone refreshes from correct arch to incorrect arch)
at least with refresh v3, this change may prevent rollbacks that we could potentially recover from on the wrong arch, but ensuring rollback safety might be a bit complicated
cd91153
to
751a0b4
Compare
751a0b4
to
7686ce3
Compare
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.
still have concerns about rollbacks & how this could makes things worse than if we continue to raise uncaught exception (#539 (review))
everything else looks good!
Not sure what you mean by that. Mind bringing this up during today's Technical Sync? |
This PR introduces the usage of the newly created architecture lib (see #560) into the charm itself.
The shape of the integration tests, as well as the helper used to get the built charm in the architecture that mismatches the one of the host itself, have been adapted from the one Lucas created for PostgreSQL-k8s (see code).