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 has been archived by the owner on Feb 7, 2024. It is now read-only.
Let's assume we have a single gitops repo responsible for hold app configurations (creating a clear separation of source code and configuration, but without spreading around into multiple repositorys) as follow:
TARGET REVISION: HEAD
├── App-1
│ ├── base
│ └── overlays
├── App-2
│ ├── base
│ └── overlays
└── App-3
├── base
└── overlays
The on-deployed will trigger a new slack message for each new revision which is completely fine and expected, however if you promote a change to App 1 synchronization messages still being sent to App 2 and App 3. Is there any chance to also filter app paths associated with each revision ?
The text was updated successfully, but these errors were encountered:
caueasantos
changed the title
oncePeer enhancements - Trigger messages only when manifest changes
oncePeer enhancement - Trigger messages only when manifest changes
Jan 24, 2021
Let's assume we have a
single gitops repo
responsible for hold app configurations (creating a clear separation of source code and configuration, but without spreading around into multiple repositorys) as follow:The
on-deployed
will trigger a new slack message for each new revision which is completely fine and expected, however if you promote a change to App 1 synchronization messages still being sent to App 2 and App 3. Is there any chance to also filter app paths associated with each revision ?The text was updated successfully, but these errors were encountered: