-
Notifications
You must be signed in to change notification settings - Fork 138
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
Adding headers to requests for Alertmanager provider. #1020
Comments
The Provider API already supports the specification of a token inside a secret: https://fluxcd.io/flux/components/notification/providers/#token-example But the notification-controller/internal/notifier/opsgenie.go Lines 43 to 57 in fa7d9f2
And, if the token is not empty, use it more or less like this: notification-controller/internal/notifier/opsgenie.go Lines 81 to 83 in fa7d9f2
It's an easy implementation. @d4rkfella are you willing to contribute this feature? |
I could give it a shot . Looks easy enough for me :P |
Opened a pull request , let me know if i did it correctly. |
Hello, i've been trying to create alertmanager provider using oauth as an authentication method. What i did was create a docker image that runs a script to obtain an access token then create a secret with the obtained token like this .
I've manually tested the token with curl and i can authenticate no problem, but when the notification controller tries to send an alert it not adding the header i have specified in the referenced secret. Is it currently possible to add headers to the requests for an Alertmanager provider ?
The text was updated successfully, but these errors were encountered: