feat: Add get-on-call-information action to backend plugin#149
Open
benjdlambert wants to merge 2 commits intoPagerDuty:mainfrom
Open
feat: Add get-on-call-information action to backend plugin#149benjdlambert wants to merge 2 commits intoPagerDuty:mainfrom
get-on-call-information action to backend plugin#149benjdlambert wants to merge 2 commits intoPagerDuty:mainfrom
Conversation
get-on call-information action to backend pluginget-on-call-information action to backend plugin
ac9ddcc to
4fadf61
Compare
4fadf61 to
f11947d
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
OK, so this PR does a few things here.
First off, we're bumping to the latest 1.49 release. Whilst not strictly required, it's nice to be up to date 🎉 I also added
We're then adding a
get-on-call-informationaction to the backend plugin, which takes integration keys from catalog entities and returns information including user details, schedule summaries, and escalation policy summaries.I've deprecated the
/oncall-usersroute, but happy to just break that if we think that's a better option, and replaced it with a/oncallendpoint instead which returns richer on-call data.We've had this internally for some time but thinking it's better placed upstream 🙏
Affected plugin
Type of change
Checklist
If this is a breaking change 👇
Acknowledgement
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
Disclaimer: We value your time and bandwidth. As such, any pull requests created on non-triaged issues might not be successful.