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
While reading the Slack integration documentation, I noticed a potential issue with the example YAML.
The secret's name seems to be incorrectly specified in the documentation.
In the YAML snippet, the name field is shown as "secret-name". However, it should be argo-rollouts-notification-secret?
apiVersion: v1kind: Secretmetadata:
name: <secret-name> // It should be `argo-rollouts-notification-secret` ?stringData:
slack-token: <Oauth-access-token>
# 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
While reading the Slack integration documentation, I noticed a potential issue with the example YAML.
The secret's name seems to be incorrectly specified in the documentation.
In the YAML snippet, the name field is shown as "secret-name". However, it should be
argo-rollouts-notification-secret
?Reference: source code
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: