-
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
Update ops to v2.14 #273
base: main
Are you sure you want to change the base?
Update ops to v2.14 #273
Conversation
Workaround for breaking change in ops 2.10: canonical/operator#1091 (comment) Workaround may break during deferred ops events or collect status ops events (canonical/operator#1091 (comment))
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.
Let's see Tony's response before merge, but even with that, this charm shouldn't be affected, right?
as currently written, yes (we don't use collect status or deferred events) but this change in ops will prevent this charm from using deferred or custom events in the future |
@paulomach what is our pissition here? Renovate pushes us to ops 2.15 (security update)... but we need to make decision here first AFAIK. |
Workaround for breaking change in ops 2.10: canonical/operator#1091 (comment)
Workaround may break during deferred ops events or collect status ops events (canonical/operator#1091 (comment))