What has Charm Tech been up to in pulse #6? In short: @ironcore864 has been busy contributing improvements to ops, including his first feature! @tony-meyer and @benhoyt have also been pushing out some ops and Pebble improvements ahead of our planned releases next week, as well as spending time on reviewing.
The ops library
- @ironcore864’s first feature has landed: you can now get cloud specification details (on machine charms), rather than having to use the credential-get hook tool manually
- We fixed up the way that ops verifies observer signatures, so that if you’re decorating observer methods in a way that changes the signature (like adding an extra argument), this works properly now.
- We fixed an issue where attaching storage in Harness, before you
begin, would not work as expected - We fixed an issue where Harness was trying too hard to help you in leader-elected events, and actually confusing people instead
- We spent some time reviewing PRs from @ppasotti (thanks!) - most significantly, a refactoring of ops.main that, in addition to improving readability and maintainability, should make it easier to experiment
- We did a large triage of all the open tickets, so it should be clearer when we’re planning on doing them
We’re expecting to release ops 2.12 next week.
Charming
- @benhoyt, @tony-meyer, and @ppasotti talked about adjustments to the Scenario API, and have agreed on most of these - we’ll continue working on it and start working towards a 7.0 branch where you’ll be able to see these and try them out
- We updated our guidance on when using defer() is appropriate and when you’d be better off using another approach
Pebble
- We fixed a bug where very long log lines would crash Pebble
- Pebble now stops immediately when the context is cancelled
- @benhoyt spent some time working with @hpidcock on Pebble auth and
PEBBLE_COPY_ONCE - @benhoyt reviewed lots of PRs coming in from various teams (thanks!), including a large refactoring of the
Planmanager
We’re expecting to release Pebble 1.10 next week.