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

Phantom TXT record blocking provider version update #54

Open
billmcmath-insider opened this issue Aug 15, 2023 · 1 comment
Open

Phantom TXT record blocking provider version update #54

billmcmath-insider opened this issue Aug 15, 2023 · 1 comment

Comments

@billmcmath-insider
Copy link

We are trying to update our version of the Constellix provider from version 0.3.11 to 0.4.5. This is the only change we have in the PR, however a phantom change in a TXT record is being picked up and stopping merging of the change.

The TXT record with the phantom change is on the root domain, where we have 1 record with 15 roundrobin values in it. The change that Terraform is seeing is that the individual values are being reordered in the list, e.g.

~ resource "constellix_txt_record" "root_TXT" {
        id          = "12345678"
        # (8 unchanged attributes hidden)

      ~ roundrobin {
          ~ value        = "apple-domain-verification=a-value" -> "google-site-verification=gsv-value-1"
            # (1 unchanged attribute hidden)
        }
      ~ roundrobin {
          ~ value        = "facebook-domain-verification=fb-value" -> "google-site-verification=gsv-value-2"
            # (1 unchanged attribute hidden)
        }
      ~ roundrobin {
      ...
      etc.

This wouldn't be much of an issue except that it's stopping the Terraform code from being deployed.

Error: Contents are identical

  with constellix_txt_record.root_TXT,
  on constellix.tf line 718, in resource "constellix_txt_record" "root_TXT":
 718: resource "constellix_txt_record" "root_TXT" {

We have attempted to resolve this by deleting the resource from the state and importing it again, but the same behaviour was seen.

@mivalsten
Copy link

This is actually an issue with 0.4.5 importing resources wrong. A workaround for that is to change TTL of a record and then change it back to correct value.

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

2 participants