-
Notifications
You must be signed in to change notification settings - Fork 227
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
feat(service): PagerDuty service integration #933
Conversation
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.
Hi @tecnologer, thank you for your PR, impressive stuff!
Minimal nitpicks really. Ready to merge once you fixed those.
I think
golangci-lint run --fix ./service/pagerduty
should automatically do most of the work for you by fixing almost all linter complaints.
Cheers :)
done, linter's complaints fixed |
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
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #933 +/- ##
===========================================
- Coverage 74.10% 31.69% -42.42%
===========================================
Files 44 63 +19
Lines 1572 2726 +1154
===========================================
- Hits 1165 864 -301
- Misses 307 1741 +1434
- Partials 100 121 +21 ☔ View full report in Codecov by Sentry. |
@tecnologer Hm, looks like the linter is still failing. I checked locally and golangci-lint run --fix ./service/pagerduty removes the two problematic comments no problem. |
@tecnologer merging! Thanks for your contribution again :) |
Description
PagerDuty integration as a notify service.
Motivation and Context
We implemented it for internal usage at DefectDojo and decided to contribute to the community.
How Has This Been Tested?
Unit tests for exported methods, test mock the client, and a proof of concept in a separate test project.
Screenshots / Output (if appropriate):
Types of changes
Checklist: