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
It would be nice to have a mopsos-notifications Helm chart that installs the needed notification templates and secrets needed for sending CloudEvents from Argo CDnotifications.
We need to check if/how argocd-notifications supports this first tho. If it doesn't, then we could have the mopsos-notifications chart schedule a job that uses some very simple kubectl --patch magic to get the job done.
The text was updated successfully, but these errors were encountered:
Currently Argo CD notifications supports configuring notifications in a single configmap specified by the config-map-name flag (default: argocd-notifications-cm).
If we want to have different charts manage different bits of the configmap, then we would probably have to raise an issue with upstream, asking them to support discovering templates in multiple configmaps via labels selectors.
As a workaround we can configure them globally for now, or to solve this issue we can do a hacky kubectl patch job.
This would be interesting to raise upstream, as I'm going to face similar pains in the future with regards to policy.csv also being in a single ConfigMap.
It would be nice to have a
mopsos-notifications
Helm chart that installs the needed notification templates and secrets needed for sending CloudEvents from Argo CD notifications.We need to check if/how argocd-notifications supports this first tho. If it doesn't, then we could have the mopsos-notifications chart schedule a job that uses some very simple
kubectl --patch
magic to get the job done.The text was updated successfully, but these errors were encountered: