From e79446071040a3f20817c7b499c40f68c3dd3c60 Mon Sep 17 00:00:00 2001 From: Tony Meyer Date: Thu, 5 Sep 2024 16:46:44 +1200 Subject: [PATCH] docs: config-changed is triggered by Juju trust (#1357) Note that `juju trust` changes will trigger a config-changed event. I couldn't find any other cases that aren't already mentioned in the `ConfigChangedEvent` doc that would trigger config-changed, so I hope this is all. Fixes #1211. --- ops/charm.py | 1 + 1 file changed, 1 insertion(+) diff --git a/ops/charm.py b/ops/charm.py index e6d35c3a3..dcd13d2dd 100644 --- a/ops/charm.py +++ b/ops/charm.py @@ -304,6 +304,7 @@ class ConfigChangedEvent(HookEvent): rescheduling, on unit upgrade or refresh, and so on. - As a specific instance of the above point: when networking changes (if the machine reboots and comes up with a different IP). + - When the app config changes, for example when `juju trust` is run. Any callback method bound to this event cannot assume that the software has already been started; it should not start stopped