Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docs: explicitly document that collect-status is is run on *every* hook #1399

Merged
merged 3 commits into from
Sep 29, 2024
+3 −1
Merged

docs: explicitly document that collect-status is is run on *every* hook #1399

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
eaf59c8
docs: explicitly document that collect-status is is run on *every* hook
james-garner-canonical Sep 27, 2024
dbd0467
docs: make this more concise
james-garner-canonical Sep 27, 2024
f3f3e76
docs: make this even more concise
james-garner-canonical Sep 29, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 3 additions & 1 deletion ops/charm.py
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1104,7 +1104,9 @@ class CollectStatusEvent(LifecycleEvent):

The framework will trigger these events after the hook code runs
successfully (``collect_app_status`` will only be triggered on the leader
unit). If any statuses were added by the event handler using
unit). This happens on every Juju event, whether it was
:meth:`observed <ops.Framework.observe>` or not.
If any statuses were added by the event handler using
:meth:`add_status`, the framework will choose the highest-priority status
and set that as the status (application status for ``collect_app_status``,
or unit status for ``collect_unit_status``).
Expand Down
Loading