charmcraft team mailing list archive

[John Lenton <chipaca@xxxxxxxxxxxxx>]

Release highlights:

   -

   Controller-side storage is now used automatically (i.e. without the
   charm author needing to set the use_juju_for_storage flag on
   main) when we’re sure it’s needed. It can still be forced on or
   off via that flag to main.
   -

   A workaround for Juju’s lp:1880637
   <https://bugs.launchpad.net/bugs/1880637> to address #293
   <https://github.com/canonical/operator/issues/293>, so
   pod.set_spec's k8s_resources works as expected. But note #387
   <https://github.com/canonical/operator/issues/387>,
   as “as expected” might not be as *you* expect.
   -

   If charm code is run in an environment that does not set
   JUJU_VERSION, default to 0.0.0 instead of raising an exception. This
   means all the feature checks will fail, but the charm can still
   progress. Please let us know if this is not what you want; this
   impacts #372 <https://github.com/canonical/operator/issues/372>.
   -

   Charm authors can now use harness.hooks_disabled() as a context
   manager to run a block of code without events being fired for them.
   Without this you’d have to wrap that code in disable/enable
   pairs.