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
Defined a context in the configmap and the notification was trigger. However the .context.fieldname always shows this is with Argo rollouts. Here is the configmap for the notification
...
data:
context: |
region: "east"
environmentName: "staging"
I'm having the same issue using Slack. The same notifications-engine is supposed to be used by both, ArgoCD and Argo Rollouts, but it doesn't seem to work for the second one.
Defined a context in the configmap and the notification was trigger. However the .context.fieldname always shows this is with Argo rollouts. Here is the configmap for the notification
...
data:
context: |
region: "east"
environmentName: "staging"
service.webhook.form: |
url: http://172.20.2.210:4566/00000000000/canary-status-queue
headers:
- name: Content-Type
value: application/x-www-form-urlencoded
template.rollout-completed: |
webhook:
form:
method: POST
body: Action=SendMessage&MessageBody={"environment":"{{ .context.environmentName }}","rollout":"{{.rollout.metadata.name}}","status":"completed"}
{{.context.xxx}} are in several sample templates, does this field only work for ArgoCD?
The text was updated successfully, but these errors were encountered: