Skip to content

Conversation

carlcsaposs-canonical
Copy link
Contributor

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))

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))
Copy link
Collaborator

@paulomach paulomach left a 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?

@carlcsaposs-canonical
Copy link
Contributor Author

this charm shouldn't be affected, right?

as currently written, yes (we don't use collect status or deferred events)
libs might be affected if they use custom events, but I don't think any custom events are emitted on relation broken

but this change in ops will prevent this charm from using deferred or custom events in the future

@taurus-forever
Copy link

@paulomach what is our pissition here? Renovate pushes us to ops 2.15 (security update)... but we need to make decision here first AFAIK.

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

Successfully merging this pull request may close these issues.

3 participants