List of events

[tmihoc (Teodora Mihoc)]

Event > List of events

In charms, events are of two basic kinds – Juju events and Ops events.

• Juju events
• Ops events

Juju events

The complete list of Juju events includes the following statically-named events:

• Lifecycle events
  • collect-metrics (deprecated)
  • config-changed
  • install
  • leader-elected
  • leader-settings-changed
  • post-series-upgrade
  • pre-series-upgrade
  • remove
  • start
  • stop
  • update-status
  • upgrade-charm
• Secret events
  • secret-changed
  • secret-expired
  • secret-remove
  • secret-rotate

And the following dynamically-named events:

The placeholder element stands for the names defined in the charmcraft.yaml file of the charm.

For each action supported by the charm:

• <action name>-action

For each container attached to the charm:

• <container>-pebble-custom-notice
• <container>-pebble-ready
• <container>-pebble-check-failed (in Juju 3.6 and above)
• <container>-pebble-check-recovered (in Juju 3.6 and above)

For each relation endpoint supported by the charm, five relation events:

• Relation events
  • <relation name>-relation-broken
  • <relation name>-relation-changed
  • <relation name>-relation-created
  • <relation name>-relation-departed
  • <relation name>-relation-joined

For each storage endpoint supported by the charm, two storage events:

• Storage events
  • <storage name>-storage-attached
  • <storage name>-storage-detaching

Ops events

The operator framework defines some events to facilitate the charm lifecycle management. These events are internal in the sense that Juju is completely unaware of them. Juju emits, say, a start event, but the operator framework can emit on the charm, on top of start, any number of events. Deferred events, or any of these ops events:

• collect-app-status
• collect-unit-status
• pre-commit
• commit

In addition to this, every Framework object (including charms) can define its own custom events.

See more: Custom event