Skip to content

Using country + georegions on regions leads to dirty plans #323

@JanBerktold

Description

@JanBerktold

Hi there,

When using a region within a record on the latest versions, we are seeing dirty plans caused by re-ordering of the country/georegions (see below). This persists across plan/apply cycles.

      - regions {
          - meta = {
              - "country"   = "RU,CA,MX,US"
              - "georegion" = "EUROPE,US-CENTRAL,US-WEST,AFRICA,US-EAST"
            } -> null
          - name = "NA-EMEA" -> null
        }
      + regions {
          + meta = {
              + "country"   = "CA,MX,RU,US"
              + "georegion" = "AFRICA,EUROPE,US-CENTRAL,US-EAST,US-WEST"
            }
          + name = "NA-EMEA"
        }

Terraform Version

on darwin_arm64
+ provider registry.terraform.io/hashicorp/aws v5.58.0
+ provider registry.terraform.io/hashicorp/http v3.4.3
+ provider registry.terraform.io/ns1-terraform/ns1 v2.3.1

Affected Resource(s)

  • resource_record

Debug Output

Please provider a link to a GitHub Gist containing the complete debug output: https://www.terraform.io/docs/internals/debugging.html. Please do NOT paste the debug output in the issue; just paste a link to the Gist.

Panic Output

If Terraform produced a panic, please provide a link to a GitHub Gist containing the output of the crash.log.

Expected Behavior

There should not by any changes.

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions