What should have happened?
Teams should be removed from escalation policies
Actual Behavior
What actually happened?
Teams are still associated with my escalation policy behind-the-scenes. I am also unable to remove teams from my escalation policies via the API. A GET request tohttps://api.pagerduty.com/escalation_policies still shows teams associated although they are not visible or editable in any way I can find.
Steps to Reproduce
terraform apply with teams = []
The apply is successful, however when terraform plan runs again it retrieves the same Escalation Policy object from pagerduty via API and removing the teams again shows up as a change to apply.
Infinite loop of doom
Important Factoids
N/A I assume this affects any team that used to have a >Business plan and then chose to downgrade.
References
Are there any other GitHub issues (open or closed) or Pull Requests that should be linked here? For example:
Terraform Version
Terraform v1.5.7 on darwin_arm64
Affected Resource(s)
Terraform Configuration Files
Debug Output
https://gist.github.com/one000mph/a06e271776274c53080146464f4ce7fa
Panic Output
N/A
Expected Behavior
What should have happened? Teams should be removed from escalation policies
Actual Behavior
What actually happened? Teams are still associated with my escalation policy behind-the-scenes. I am also unable to remove teams from my escalation policies via the API. A GET request to
https://api.pagerduty.com/escalation_policies
still shows teams associated although they are not visible or editable in any way I can find.Steps to Reproduce
terraform apply
withteams = []
terraform plan
runs again it retrieves the same Escalation Policy object from pagerduty via API and removing the teams again shows up as a change to apply.Important Factoids
N/A I assume this affects any team that used to have a >Business plan and then chose to downgrade.
References
Are there any other GitHub issues (open or closed) or Pull Requests that should be linked here? For example: