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.
PagerDuty has a special-purpose API to return who is currently on-call for an escalation policy:
https://pdt-circular.pagerduty.com/api/v1/escalation_policies/on_call
It's not documented, but you can also stick an EP parameter in there, IE
https://pdt-circular.pagerduty.com/api/v1/escalation_policies/123456/on_call
There's some logic I need to fix as far as primary vs. secondary goes. Right now, it just returns the first two user entries in the 'user' blob, when what it should actually do is return the first user with level=1, and then the first user with level=2. Or, to get fancier, it should actually return all users on a given level.