Skip to content
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

Infer PagerDuty Service members from escalation policies #27

Open
wilsonehusin opened this issue May 1, 2024 · 0 comments
Open

Infer PagerDuty Service members from escalation policies #27

wilsonehusin opened this issue May 1, 2024 · 0 comments

Comments

@wilsonehusin
Copy link
Member

PagerDuty organizations may not be using the "Teams" resource and only "Service". While we support importing "Service" as "Team", it's still dependent on Teams API.

Consider the scenario of PagerDuty organization with:

  • Service, linked to Escalation Policy
  • Escalation Policy, linked to On-call Schedule
  • On-call Schedule has members in rotation

We can infer the FireHydrant team members for the given Service, through the list of members in rotation for On-call schedule.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant