This document describes the
stop event is emitted only once: when the Juju controller is ready to destroy the unit. When handling the
stop event, charms should gracefully terminate all services for the supported application and update any relevant cluster/leader information to remove or update any data relating to the current unit. Additionally, the charm should ensure that the software will not automatically start again on reboot.
On kubernetes charms, the
stop event will occur on pod churn, when the unit dies. On machine charms, the stop event will be fired as part of the teardown sequence when a unit goes down.
Ways to force the occurrence of a
ops, you can observe the
stop event like you would any other:
stop event object does not expose any specific attributes.
Last updated 5 months ago.