Charm Tech pulse 2026#21

charm
1

In this pulse, the team focuses on wrapping up roadmap items, and preparing for the Sprints. We worked on modelling the juju-*-proxy model configs in Ops, and made Jubilant report on how long wait took when it finished.

We also released api-demo-server 3.0.0, with support for use in 12-factor charms. This brought a breaking change to the From zero to hero: Write your first Kubernetes charm tutorial. If you run into any trouble, please let us know.

Ops

  • Started work on modelling juju-*-proxy model configs from Juju (#2832).
  • Made the testing event class public as ops.testing.Event (#2760).
  • Avoided exponential backtracking in the ops.testing storage name check (#2800).

Charming

  • Made pip-audit run on a frozen requirements.txt file (#183, #126).
  • Released api-demo-server 3.0.0, with support for use in 12-factor charms (#101, #102, #103).
  • In Jubilant: reported how long wait took when it succeeds or the error callable fires (#419).
  • Added to Jubilant an ssh_key argument to Juju.ssh and Juju.scp (#430).

Charmlibs

  • Worked on a how-to guide for designing a charm interface library API (#748).

Documentation

  • Started work on adding a how-to set up production integration guide in ops documentation (#2835).
  • Added a compact topic index to the Pebble doc homepage (#1123).
  • Made sure that every Jubilant page has a high-quality description for search engine snippets (#437).
  • Added a documentation section to Jubilant’s contributing guide (#438).
2 Likes