-
Notifications
You must be signed in to change notification settings - Fork 132
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
Feature: Add option to pass additional headers via secretRef to the generic notification provider #291
Conversation
Hi @boxcee ! Thanks for your contribution here, Can you please update the PR description with some explanation about what is added here? When you are ready to have it reviewed, can you please make sure the DCO bot is satisfied, and that you have squashed and/or |
Signed-off-by: Moritz Schmitz von Hülst <moritz@hauptstadtoffice.com>
@yebyen done 👍🏾 |
@yebyen |
controllers/provider_controller.go
Outdated
@@ -32,6 +32,8 @@ import ( | |||
"sigs.k8s.io/controller-runtime/pkg/controller" | |||
"sigs.k8s.io/controller-runtime/pkg/predicate" | |||
|
|||
"gopkg.in/yaml.v3" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please remove this dependency and use sigs.k8s.io/yaml
metadata: | ||
name: generic-secret | ||
namespace: default | ||
data: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please use stringData
e.g.
stringData:
headers: |
Authorization: token
X-Forwarded-Proto: https
Also explain how the headers
are used.
Signed-off-by: Moritz Schmitz von Hülst <moritz@hauptstadtoffice.com>
Can you provide a bit more detail about the example of use for documentation? I understand the sample and the change, I'm just unsure about how the GitHub side of the configuration would look like, and how Flux users should discover this feature. The example added in the doc isn't given any context or description in the current revision of the PR. That would make this finished, afaict 👍 @boxcee the branch has merge conflicts right now and so, looks like it must be rebased in order to merge. |
Superseded by #317 |
@boxcee hi, how do you trigger Github workflows with /dispatches URL with generic notification provider? It seems that Github repository_dispatch trigger requires a mandatory |
The generic notification provider should have a little more configuration options.
We have a use-case where we want to kick-off Github workflows based on deployments. A feature to add additional headers would allow us to do this. Without additional headers we are not able to authenticate with Github though, since it requires an
Authorization
header with the personal access token set.