OncePer Argo CD notification logic #21650
ajax-bychenok-y
started this conversation in
General
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I am playing with Argo CD notifications in particular with
OncePer
parameter in trigger section.In general documentation recommends to use there something unique like git revision or so.
Git revision is not suitable for me because it sends notification for each sync action (new replicas count in manifests or so).
But I wish to send notification only for newer image tag. It's is unique but till I don't wish to deploy previous version because it seems that notification subsystem uses own history.
Let me be more specific. Supposing i have
And release next images versions:
Is it possible to count changes only with previous version and get notification for last
1.26
image?Beta Was this translation helpful? Give feedback.
All reactions