How does ArgoCD Notifications work?

Question

Accepted Answer

**ArgoCD Notifications** — notifications about ArgoCD events (sync, health, deploy).

**Triggers:**
```yaml
apiVersion: v1
kind: ConfigMap
metadata:
  name: argocd-notifications-cm
  namespace: argocd
data:
  trigger.on-sync-succeeded: |-
    - when: app.status.operationState.phase in ["Succeeded"]
      send: [app-sync-succeeded]
  trigger.on-sync-failed: |-
    - when: app.status.operationState.phase in ["Error", "Failed"]
      send: [app-sync-failed]
  trigger.on-health-degraded: |-
    - when: app.status.health.status == "Degraded"
      send: [app-health-degraded]

template.app-sync-succeeded: |
    message: |
      Application {{.app.metadata.name}} sync succeeded.
      Revision: {{.app.status.sync.revision}}
  template.app-sync-failed: |
    message: |
      Application {{.app.metadata.name}} sync FAILED.
      Error: {{.app.status.operationState.message}}

service.slack: |
    token: $slack-token
    signingSecret: $slack-signing-secret

service.webhook.github: |
    url: https://api.github.com/repos/{owner}/{repo}/statuses/{revision}
    headers:
      - name: Authorization
        value: token $github-token
```

**Application annotations (enabling):**
```yaml
metadata:
  annotations:
    notifications.argoproj.io/subscribe.on-sync-succeeded.slack: "#deploys"
    notifications.argoproj.io/subscribe.on-sync-failed.slack: "#alerts"
    notifications.argoproj.io/subscribe.on-health-degraded.pagerduty: "service-key"
```

**Services:** Slack, GitHub, GitLab, Microsoft Teams, PagerDuty, OpsGenie, Email, Webhook.

DevOps: How does ArgoCD Notifications work?