Juju events¶

For a web app charm, the following events are observed:

Hook	Description	Action
<container name>_pebble_ready	Fired on Kubernetes charms when the requested container is ready.	Validate the charm configuration, run pending migrations and restart the workload.
config_changed`	Usually fired in response to a configuration change using the CLI.	Validate the charm configuration, run pending migrations and restart the workload.
`secret_storage_relation_created`	Fired when the relation is first created.	Generate a new secret and store it in the relation data.
`secret_storage_relation_changed`	Fired when a new unit joins in an existing relation and whenever the related unit changes its settings.	Validate the charm configuration, run pending migrations and restart the workload.
`secret_storage_relation_departed`	Fired when a unit departs from an existing relation.	Validate the charm configuration, run pending migrations and restart the workload.
`update_status`	Fired at regular intervals.	Validate the configuration, run pending migrations and restart the workload.
`secret_changed`	Fired when the secret owner publishes a new secret revision.	Validate the configuration, run pending migrations and restart the workload.
`database_created`	Fired when a new database is created.	Validate the configuration, run pending migrations and restart the workload.
`endpoints_changed`	Fired when the database endpoints change.	Validate the configuration, run pending migrations and restart the workload.
`database_relation_broken`	Fired when a unit participating in a non-peer relation is removed.	Validate the configuration, run pending migrations and restart the workload.
`ingress_ready`	Fired when the ingress for the web app is ready.	Validate the configuration, run pending migrations and restart the workload.
`ingress_revoked`	Fired when the ingress for the web app is not ready anymore.	Validate the configuration, run pending migrations and restart the workload.
`redis_relation_updated`	Fired when a new unit joins in an existing relation and whenever the related unit changes its settings.	Validate the configuration, run pending migrations and restart the workload.
s3_credentials_changed	Fired when the S3 credentials are changed.	Validate the configuration, run pending migrations and restart the workload.
s3_credentials_gone	Fired when the S3 credentials are removed.	Validate the configuration, run pending migrations and restart the workload.
`saml_data_available`	Fired when new SAML data is present in the relation.	Validate the configuration, run pending migrations and restart the workload.
`rabbitmq_ready`	Fired after a `rabbitmq_cjoined` event.	Validate the configuration, run pending migrations and restart the workload.
`rabbitmq_connected`	Fired after a `rabbitmq_changed` or `rabbitmq_broken` event.	Validate the configuration, run pending migrations and restart the workload.
`rabbitmq_joined`	Fired when a new unit joins in an existing relation.	Request access to the RabbitMQ server and emit a connected event.
`rabbitmq_changed`	Fired when a new unit joins in an existing relation and whenever the related unit changes its settings.	Request access to the RabbitMQ server and emit a ready event.
`rabbitmq_broken`	Fired when a unit participating in a non-peer relation is removed.	Emit a ready event.
`rabbitmq_departed`	Fired when a related unit is no longer related.	Validate the charm configuration, run pending migrations and restart the workload.
`tracing_endpoint_changed`	Fired when one of the receiver endpoints changes.	Validate the charm configuration, run pending migrations and restart the workload.
`tracing_endpoint_removed`	Fired when one of the receiver endpoints is removed.	Validate the charm configuration, run pending migrations and restart the workload.
`smtp_data_available`	Fired when new SMTP data is present in the relation.	Validate the charm configuration, run pending migrations and restart the workload.
`rotate_secret_key`	Fired when `secret-rotate` is executed.	Generate a new secret token for the application.