opsgenie / terraform-provider-opsgenie

Terraform OpsGenie provider
https://registry.terraform.io/providers/opsgenie/opsgenie/latest/docs
Mozilla Public License 2.0
100 stars 135 forks source link

`400 Bad Request` after import and change *first* time of `opsgenie_service` #441

Open Mazorius opened 1 month ago

Mazorius commented 1 month ago

Terraform Version

1.5.7

Affected Resource(s)

Terraform Configuration Files

locals {
  test = {
    services = [
      {
        name        = "Test 1"
        description = "description"
        tags        = ["TEST-1", "TAG"]
      },
      {
        name        = "Test 2"
        description = "description"
        tags        = ["TEST-2", "TAG"]
      },
    ]
  }
}

resource "opsgenie_service" "test" {
  for_each = {
    for service in local.test.services : service.name => service
  }

  name        = each.value.name
  description = each.value.description
  tags        = each.value.tags
  team_id     = opsgenie_team.test.id
}

Expected Behavior

The scripts run successful every time.

Actual Behavior

During initial run after import a 400 bad request happens. A second run is successful.

Steps to Reproduce

  1. Get ID of already manually created service inside a team.
  2. Import into state terraform import 'opsgenie_service.test["Test 1"]' 2387A5D4-21AC-4D94-B431-7313786F66D2
  3. terraform plan -out plan.cache
  4. terraform apply plan.cache