Skip to content
This repository was archived by the owner on Apr 8, 2021. It is now read-only.

Conversation

cordway
Copy link

@cordway cordway commented Sep 9, 2020

PR to add escalation policy id escalation_id to the services table.

The point of this PR is to enable joining of the services and escalation_policies table on escalation_id. This is helpful in being able to easily determine the escalation policy of a service. Right now it is only possible to get a services escalation policy by going through a particular incident (joining services and incidents and incidents and escalation_policies). This is not entirely reliable as services policies can be changed. Adding escalation_id is only a few lines change as the ID is easily available in the JSON response from the pagerduty api.

Locally verified, able to create tables & load data with escalation_id now present in services table.

@CLAassistant
Copy link

CLA assistant check
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
You have signed the CLA already but the status is still pending? Let us recheck it.

Co-authored-by: Alex Turek <[email protected]>
@cordway cordway force-pushed the add_escalation_ids_to_services branch from b29e4d3 to b63bfc9 Compare September 10, 2020 22:25
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants