-
Notifications
You must be signed in to change notification settings - Fork 154
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(opsgenie): Add support for setting priority in Opsgenie notification #267
feat(opsgenie): Add support for setting priority in Opsgenie notification #267
Conversation
6613522
to
8ddfc22
Compare
Codecov ReportAttention:
Additional details and impacted files@@ Coverage Diff @@
## master #267 +/- ##
==========================================
+ Coverage 54.79% 54.99% +0.19%
==========================================
Files 35 35
Lines 3376 3386 +10
==========================================
+ Hits 1850 1862 +12
+ Misses 1254 1251 -3
- Partials 272 273 +1 ☔ View full report in Codecov by Sentry. |
4e7d028
to
eedc5d3
Compare
…tions Signed-off-by: Bofa Alsarah <[email protected]>
eedc5d3
to
595b339
Compare
Thank you @bofaalsarah , could you please add test for it ? |
Signed-off-by: Bofa Alsarah <[email protected]>
Done ✅ |
Signed-off-by: Bofa Alsarah <[email protected]>
LGTM, thank you |
@bofaalsarah only one thing, could you please add some documentation about it? it can be dedicated PR |
Sure, I will create another PR for the documentation |
This PR adds support for setting the priority field in Opsgenie notifications. If a priority is provided in the notification, it will be included in the alert creation request to Opsgenie. Additionally, the code now checks for missing description in Opsgenie notifications and returns an error if it's missing.