You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Oct 19, 2024. It is now read-only.
Copy file name to clipboardExpand all lines: docs/triggers.md
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -48,7 +48,7 @@ data:
48
48
49
49
In some cases, the trigger condition might be "flapping". The example below illustrates the problem.
50
50
The trigger is supposed to generate a notification once when Argo CD application is successfully synchronized and healthy.
51
-
However the application health status might intermittently switch to `Progressing` and then back to `Healthy` so the trigger might unnecessary generate
51
+
However, the application health status might intermittently switch to `Progressing` and then back to `Healthy` so the trigger might unnecessarily generate
52
52
multiple notifications. The `oncePer` field configures triggers to generate the notification only when the corresponding application field changes.
53
53
The `on-deployed` trigger from the example below sends the notification only once per observed Git revision of the deployment repository.
0 commit comments