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
What problem are you trying to solve?
If deploying via GitOps tools such as FluxCD or ArgoCD, you must store the alert Slack or Teams webhook in git. This is less than desirable and it would be great if the chart supported pulling from a secret.
Describe the solution you'd like
Ability to use Slack or Teams webhook from a Kubernetes secret such as is already done for various other items in the chart like product key
Ideally some value like:
globalSlackWebhookUrlSecretName
The text was updated successfully, but these errors were encountered:
Hey @adickinson72! I think this is the line you're referring to which would put the webhook URL in git? If so, I agree that being able to add your webhook URL as a secret would be a good enhancement!
@thomasvn - yes exactly thats the line I was referring to!
Appreciate the guidance on the ConfigMap suggestion. Will probably end up doing that as a workaround but definitely think it's worthwhile as enhancement
What problem are you trying to solve?
If deploying via GitOps tools such as FluxCD or ArgoCD, you must store the alert Slack or Teams webhook in git. This is less than desirable and it would be great if the chart supported pulling from a secret.
Describe the solution you'd like
Ability to use Slack or Teams webhook from a Kubernetes secret such as is already done for various other items in the chart like product key
Ideally some value like:
globalSlackWebhookUrlSecretName
The text was updated successfully, but these errors were encountered: