You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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.
The text was updated successfully, but these errors were encountered:
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.
We are trying to update our version of the Constellix provider from version
0.3.11
to0.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.
This wouldn't be much of an issue except that it's stopping the Terraform code from being deployed.
We have attempted to resolve this by deleting the resource from the state and importing it again, but the same behaviour was seen.
The text was updated successfully, but these errors were encountered: