Argo CD Notifications fire in another env when only test overlay changes (mono-repo, ApplicationSet, autosync)

[john-lee-otsk]

Hi team — I’m seeing cross-environment notifications in a mono-repo setup.

Although Argo CD Notifications are configured only for the dev environment (k8s/overlays/dev/applicationset.yaml), a commit under test or stage overlays also triggers an on-deployed notification in dev. The dev notification’s commit message matches the non-dev commit, even though dev manifests weren’t changed.

Repository layout (simplified)
application-config/
├─ applicationset/kustomize/overlays/{dev,stage,test}/apps-applicationset.yaml
├─ apps/
│ ├─ frontend/k8s/{base,overlays/{dev,stage,test}}
│ ├─ backend/k8s/{base,overlays/{dev,stage,test}}
│ └─ ... (other apps with {dev,stage,test} overlays)
└─ infras/...

How apps are generated
All environments are currently pointed at the same branch (e.g., main / HEAD).
Example (dev overlay ApplicationSet excerpt — similar for stage/test)

spec:
  generators:
    - git:
        repoURL: https://github.com/ocean-network-express/application-config.git
        revision: main
        directories:
          - path: apps/**/k8s/overlays/dev
  template:
    spec:
      source:
        repoURL: https://github.com/ocean-network-express/application-config.git
        targetRevision: main

What actually happens

• Commit to: apps/frontend/k8s/overlays/test/kustomization.yaml
• Expected: No alarms / only alarm is configured in dev environment.
• Observed: The dev app also shows a new sync in History (Succeeded + Healthy) and sends the app-deployed notification with the test commit message.