This commit is contained in:
Alexei Znamensky 2025-07-27 00:22:32 +12:00
commit 2727c1634d
2 changed files with 4 additions and 5 deletions

View file

@ -106,9 +106,8 @@ options:
description:
- Identifies the incident to which this O(state) should be applied.
- For O(state=triggered) - If there is no open (in other words unresolved) incident with this key, a new one is created.
If there is already an open incident with a matching key, this event is appended to that incident's
log. The event key provides an easy way to 'de-dup' problem reports. If no O(incident_key) is provided, then it is
generated by PagerDuty.
If there is already an open incident with a matching key, this event is appended to that incident's log. The event
key provides an easy way to 'de-dup' problem reports. If no O(incident_key) is provided, then it is generated by PagerDuty.
- For O(state=acknowledged) or O(state=resolved) - This should be the incident_key you received back when the incident
was first opened by a trigger event. Acknowledge events referencing resolved or nonexistent incidents is discarded.
link_url:

View file

@ -50,8 +50,8 @@ options:
- Prompts are processed in the same order as the packages list.
- You can optionally specify an answer to any question in the list.
- If no answer is provided, the list item contains only the regular expression.
- "To specify an answer, the item is a dict with the regular expression as key and the answer as value
C(my_regular_expression: 'an_answer')."
- "To specify an answer, the item is a dict with the regular expression as key and the answer as value C(my_regular_expression:
'an_answer')."
- You can provide a list containing items with or without answer.
- A prompt list can be shorter or longer than the packages list but it issues a warning.
- If you want to specify that a package does not need prompts in the middle of a list, V(null).