This repository was archived by the owner on Apr 8, 2021. It is now read-only.
Add escalation ids to services #20
Open
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.
PR to add escalation policy id
escalation_id
to the services table.The point of this PR is to enable joining of the
services
andescalation_policies
table onescalation_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 (joiningservices
andincidents
andincidents
andescalation_policies
). This is not entirely reliable as services policies can be changed. Addingescalation_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.