-
Notifications
You must be signed in to change notification settings - Fork 139
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
Add support for PagerDuty #527
Conversation
Thanks for this PR @MartiUK ! |
Hi @makkes, @stefanprodan is there anything else needed to progress this PR further? |
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.
Just a couple of nits, otherwise lgtm
Please resolve the conflicts with |
1bdba27
to
5fa67ce
Compare
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.
LGTM, thank you! 🥳
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.
This looks great, some tiny nits only from me.
Your generated CRD manifests don't match the code. Please run |
c029a27
to
22c1a39
Compare
34fca2e
to
090038c
Compare
Signed-off-by: Martin Kemp <[email protected]>
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.
LGTM
Thanks @MartiUK 🏅
This PR adds support for PagerDuty.
There are some assumptions made in regards to what should trigger an incident, I'm happy to be corrected on this.
It would be nice to allow Alerts to override some Provider settings e.g. override the channel (integration key) to send alerts to different PagerDuty integrations without needed to create a Provider for each.