From 61f0e01507f4bf287c48d2585ac2a26cfcfdc1bc Mon Sep 17 00:00:00 2001 From: Alexei Znamensky <103110+russoz@users.noreply.github.com> Date: Sun, 27 Jul 2025 00:14:53 +1200 Subject: [PATCH] Update plugins/modules/pagerduty_alert.py --- plugins/modules/pagerduty_alert.py | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/plugins/modules/pagerduty_alert.py b/plugins/modules/pagerduty_alert.py index 3dabe4438d..16bdf4d7ee 100644 --- a/plugins/modules/pagerduty_alert.py +++ b/plugins/modules/pagerduty_alert.py @@ -106,9 +106,9 @@ 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 __FIXME__(will) be 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 __FIXME__(will) - be 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: