We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
https://fluxcd.io/flux/components/notification/providers/#github-dispatch into a github actions workflow that leaves a comment, with https://fluxcd.io/flux/components/notification/alerts/ to feed it events from the preview objects.
For the first pass, just have the workflow log the payload and then exit, to work out what information is actually in there.
Have each preview include its own Alert object with metadata that links it to the PR.
Like in https://flux-iac.github.io/tofu-controller/use-tf-controller/flux-receiver-and-alert/, patch out the kind enum in the Alert CRD and add RBAC for the extra objects.
kind
The text was updated successfully, but these errors were encountered:
Depends on fluxcd/notification-controller#996
Sorry, something went wrong.
No branches or pull requests
https://fluxcd.io/flux/components/notification/providers/#github-dispatch into a github actions workflow that leaves a comment, with https://fluxcd.io/flux/components/notification/alerts/ to feed it events from the preview objects.
For the first pass, just have the workflow log the payload and then exit, to work out what information is actually in there.
Have each preview include its own Alert object with metadata that links it to the PR.
Like in https://flux-iac.github.io/tofu-controller/use-tf-controller/flux-receiver-and-alert/, patch out the
kind
enum in the Alert CRD and add RBAC for the extra objects.The text was updated successfully, but these errors were encountered: