-
Notifications
You must be signed in to change notification settings - Fork 867
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Make secrets available for notification templates #3455
Comments
* feat: expose secrets for notification templates Signed-off-by: Etien Roznik <[email protected]> * feat: expose secrets for notification templates Signed-off-by: Etien Roznik <[email protected]> --------- Signed-off-by: Etien Roznik <[email protected]>
Hey, unfortunately this is not working even in the latest release for webhooks. Given the following secret:
and the following notification:
I am still getting the following controller log:
So The MR linked in this issue suggests that the enhancement is included in the latest release. Any help would be greatly appreciated. Cheers Oliver |
@eroznik , @zachaller , do you have any ideas what I am doing wrong? |
OK, I guess I cannot use the secret substitution in templates. |
Hey @oliverkuntze , afaik the path template should work.. but you have to use the parameter a bit differently:
should be
|
Summary
I'd like to expose secret data in notification templates, this would have to be done here. I'd suggest we do it similar to what I did on ArgoCD and if needed, we can add a feature flag to include secrets just conditionally.
Use Cases
This was already done on ArgoCD and it is useful to trigger webhooks that require auth data in payloads.
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: