What has the Charm Tech team been up to in pulse #14? The highlights: finished most of the Pebble Identities implementation, significant work on the new Scenario 7.0 API, and agreed on and implemented the new Pebble health check events for Juju.
We also have one team member finishing his onboarding, and another on holiday, so it’s been a bit lighter this pulse.
Ops and charming
- Finalised the spec for the new Pebble health check events (JU046).
- Implemented the necessary changes for these health check events in Ops, Juju, and Pebble.
- Helped review the Airbyte charm for listing.
Scenario
Significant work on the Scenario 7.0 “updated API” branch, including:
- Using sets instead of lists for State components.
- Requiring keyword arguments for most dataclasses.
- Basic API reference docs, generated locally, to help review the new 7.0 API.
- Drafted upgrade guide for upgrading to the 7.0 API.
Pebble
Significant work on Pebble Identities, as well as some initial work to improve how we handle locks:
- Merged the core Identities work (PRs 428, 429, 430, and 431).
- Reviewed and iterated on actually using Identities for API access (aim to merge next week).
- Draft PR to remove the legacy Warnings code – still under discussion.
- Pulling in the snapd RestartManager refactoring. This is part of the work to avoid holding the state lock on every request.
- Don’t hold planLock while calling plan-changed listeners.
Documentation
- Drafted how-to guide for storage.