chore: Bump ops from 2.9.0 to 2.10.0

[dependabot]

Bumps ops from 2.9.0 to 2.10.0.

Release notes

Sourced from ops's releases.

2.10.0 Pebble custom notices, adjustments to relation-broken, and more

This release adds support for Pebble custom notices, including in the Harness testing framework, and removes the broken relation from the model's relations list when in the relation-broken event. There's also the usual collection of documentation improvements, bug fixes, and other minor improvements.

Pebble Notices

Pebble now includes a subsystem called Notices, each of which has a type and a key (currently the only type is "custom"). Custom notices allow the workload to wake up the charm when something interesting happens with the workload, for example, when a PostgreSQL backup process finishes, or some kind of alert occurs.

Workloads can run pebble notify to record an occurrence of a custom notice, providing a unique key and optional data, and Juju will trigger a PebbleCustomNotice event on the charm for it to take appropriate action.

Support for Pebble Notices is available from Juju 3.4.0 onwards. Read the docs about how to use custom notices from the workload container.

Relation-Broken

When a charm is handling a relation-broken event, the relation is on the verge of being removed. A common pattern in charms is to iterate through Model.relations (to generate a configuration file, for example), and the broken relation should not be included with the active relations. To simplify charm code, Model.relations now excludes the broken relation. The relation is still accessible via the event's .relation attribute, and all Relation objects now have an .active attribute to distinguish between the broken relation (active == False) and other relations (active == True).

The plan is that this change will also appear when using the Juju hook tools directly in a future version of Juju.

This does not change accessing the relation data during relation-broken, and this does not change any behaviour in relation-departed.

Features

• feat: support for Pebble Notices in canonical/operator#1086 and in canonical/operator#1100
• feat: add Relation.active, exclude inactive relations from Model.relations in canonical/operator#1091
• feat: when handling actions, print uncaught exceptions to stderr in canonical/operator#1087
• feat: model error on testing module if invalid status set by charm by @​yanksyoon in canonical/operator#1107
• feat: add support for v2 fields in CharmMeta in canonical/operator#1106

Fixes

• fix: add pebble log targets and checks to testing plan by @​PietroPasotti in canonical/operator#1111
• fix(charm): make collect-status a LifeCycleEvent to avoid logging it by @​PietroPasotti in canonical/operator#1080

Documentation

• docs: update README.md in light of changes to charmcraft init output by @​tmihoc in canonical/operator#1089
• docs: document limitations with pushing locked or bind-mount files in canonical/operator#1094
• docs: add instructions on how to use a custom version of ops in a Charm in canonical/operator#1092

Tooling

• build: migrate to pyproject.toml in canonical/operator#1068
• ci: use a trusted publisher token for publishing to PyPI in canonical/operator#1061
• fix(typing): update to latest version of Pyright and fix errors in canonical/operator#1105

Many thanks to @​PietroPasotti, @​yanksyoon, and @​tmihoc for their contributions to this release!

Full Changelog: canonical/operator@2.9.0...2.10.0

Changelog

Sourced from ops's changelog.

2.10.0

• Added support for Pebble Notices (PebbleCustomNoticeEvent, get_notices, and so on)
• Added Relation.active, and excluded inactive relations from Model.relations
• Added full support for charm metadata v2 (in particular, extended ContainerMeta, and various info links in CharmMeta)

Commits

• 3dd4621 Bump version for release. (#1117)
• 94263b0 ci: reinstate postgresql-operator tests now that issue is fixed (#1116)
• d49fa98 fix(charm): make collect-status a LifeCycleEvent to avoid logging it (#1080)
• 4678130 fix: add pebble log targets and checks to testing plan (#1111)
• dc47640 feat: add support for v2 fields in CharmMeta (#1106)
• 41a4ad4 ci: use a trusted publisher token for publishing to PyPI (#1061)
• aa04950 build: migrate to pyproject.toml (#1068)
• cc29ea3 feat: add Relation.active, exclude inactive relations from Model.relations (#...
• ea1cf19 feat: model error on testing module if invalid status set by charm (#1107)
• 261c441 fix(typing): update to latest version of Pyright and fix errors (#1105)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)