Steps to reproduce
- Terraform destroy (just to clean house)
- Terraform apply (all resources applied successfully)
- Terraform apply (Resource changes apply to remove extraneous brackets)
Diff example
# module.custommodule.vinyldns_record_set.dns_instance6[0] will be updated in-place
~ resource "vinyldns_record_set" "dns_instance6" {
id = "18b67c48-a348-4241-9fc9-9dff4c8235b4:82d3d9c6-acb6-43c0-a655-e81a0c7f252f"
name = "hostname"
~ record_addresses = [
- "64:558:fc0a:3:f816:3eff:fed7:badd",
+ "[64:558:fc0a:3:f816:3eff:fed7:badd]",
]
ttl = 120
type = "AAAA"
zone_id = "18b67c48-a348-4241-9fc9-9dff4c8235b4"
}
I don't see this with IPv4 A records. You can run terraform apply as much as you like and every time it thinks it needs to change the IP address. I'm guessing there's a missmatch between IPv6 formatting rules between the API and the TF provider. Found in releases TF11 + 0.9.4 & TF12 + 0.9.5.
Steps to reproduce
Diff example
I don't see this with IPv4 A records. You can run terraform apply as much as you like and every time it thinks it needs to change the IP address. I'm guessing there's a missmatch between IPv6 formatting rules between the API and the TF provider. Found in releases TF11 + 0.9.4 & TF12 + 0.9.5.