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

After downgrading account, cannot remove teams from pagerduty_escalation_policy #927

Open
one000mph opened this issue Aug 19, 2024 · 0 comments

Comments

@one000mph
Copy link

Terraform Version

Terraform v1.5.7
on darwin_arm64

  • provider registry.terraform.io/datadog/datadog v3.43.0
  • provider registry.terraform.io/hashicorp/aws v5.63.0
  • provider registry.terraform.io/pagerduty/pagerduty v3.15.4

Affected Resource(s)

  • pagerduty_escalation_policy

Terraform Configuration Files

resource "pagerduty_escalation_policy" "escalationpolicy" {
  name      = "${var.escalation_policy_name} escalation policy"
  num_loops = 2

  dynamic "rule" {
    for_each = data.pagerduty_user.user
    content {
      escalation_delay_in_minutes = 10
      target {
        type = "user_reference"
        id   = rule.value.id
      }
    }
  }
}

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 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

  1. terraform apply with teams = []
  2. 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.
  3. 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:

  • None that I could find.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant