Pulse #13 highlights: Pebble’s identity feature is coming soon, a lot of documentation work is done, CI/automated tests are improved, and more.
Ops
- Released a new version v2.14.1.
- Improvements: clean up after running setup_root_logging in test_log; add checks and
log_targets
toops.testing
(WIP). - CI: Made
update-charm-tests
run monthly; PR title validation against conventional commit; added artefact attestation; - Research to extend
ops.log
to capture warnings and tested this. Not merged since warnings are already in Juju debug-log (although not extremely beautiful). - Worked on the pebble-change-updated-notice spec and the Pebble check events spec.
- Reviewed the Pydantic integration spec and came up with an alternative proposal.
Charming
- Run
charm-relation-interfaces
on a schedule, including some minor fixes in the dependency. It’s still WIP, need to publish a new version of the dependency and figure out a way to send push notifications.
Scenario
- Adding Scenario classes that match the ops status classes (WIP).
- Minor fixes: moved the cloud specification to Model.
Pebble
- Significant work on the new identities feature (WIP; see PR 428, 429, 430, 431, 434).
- Improving performance: avoid acquiring state lock for every API request (WIP).
- Adding a new feature where lanes are used to start services (WIP), this will also fix issue 231.
- Some minor fixes: a work around with
user.Lookup
not returningUnknownUserError
; don’t hold planLock while calling plan-changed listeners (WIP).
Documentation
- Juju SDK: Updated the How to register an interface and How to write interface tests guides with latest content and examples; improved a few how-to docs with more links to code and examples; restructured and filled in some gaps in How to add a relation to a charm.
- Ops: Continue working on enriching the ops API reference; added
ops.main
docs; added a basic security policy. - Pebble: Created a new tutorial, a how-to-install guide, and some reusable content to better organize the documentation. More how-to and reference docs will come soon.
- Scenario: a basic API reference docs (WIP); adding instructions for moving from 6.x to 7.x (WIP).