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
Many of the docs of the Argo Rollout notification services make it seem that you can subscribe Argo CD Application to Argo Rollout triggers or access Argo CD Application data (e.g. .app.metadata.name) in Argo Rollout templates. This is incorrect per #3990 as Argo Rollouts notifications only has context to Rollout resources.
To Reproduce
Expected behavior
Screenshots
Version
Logs
# Paste the logs from the rollout controller
# Logs for the entire controller:
kubectl logs -n argo-rollouts deployment/argo-rollouts
# Logs for a specific rollout:
kubectl logs -n argo-rollouts deployment/argo-rollouts | grep rollout=<ROLLOUTNAME
Message from the maintainers:
Impacted by this bug? Give it a 👍. We prioritize the issues with the most 👍.
The text was updated successfully, but these errors were encountered:
Checklist:
Describe the bug
Many of the docs of the Argo Rollout notification services make it seem that you can subscribe Argo CD Application to Argo Rollout triggers or access Argo CD Application data (e.g.
.app.metadata.name
) in Argo Rollout templates. This is incorrect per #3990 as Argo Rollouts notifications only has context to Rollout resources.To Reproduce
Expected behavior
Screenshots
Version
Logs
Message from the maintainers:
Impacted by this bug? Give it a 👍. We prioritize the issues with the most 👍.
The text was updated successfully, but these errors were encountered: