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

google_dns_record_set always wants to update TXT records that are not escape-quoted #863

Closed
abevoelker opened this issue Dec 14, 2017 · 1 comment
Labels

Comments

@abevoelker
Copy link

Terraform Version

Terraform v0.11.1
+ provider.google v1.4.0

Affected Resource(s)

  • google_dns_record_set

Terraform Configuration Files

resource "google_dns_record_set" "foo" {
  name = "example.com."
  type = "TXT"
  ttl  = 300
  managed_zone = "foo-zone"

  rrdatas = ["foo"]
}

Debug Output

https://gist.github.com/abevoelker/e35529ee72f8b0619a9cae0130c8ce03

Panic Output

N/A

Expected Behavior

After the initial terraform apply, subsequent terraform plan operations should say "No changes. Infrastructure is up-to-date."

Actual Behavior

terraform plan continually wants to update the DNS record.

Steps to Reproduce

  1. terraform apply
  2. terraform plan

Important Factoids

I can work around the issue by escape-quoting the value (rrdatas = ["\"foo\""]), however the documentation makes it sound like that should only be required for values with spaces in them.

References

@paddycarver paddycarver self-assigned this Dec 14, 2017
@danawillow danawillow added the bug label Jan 26, 2018
paddycarver added a commit that referenced this issue Mar 1, 2018
This treats record set RRdata values as equivalent if they're quoted and
unquoted, as the GCP backend likes to return TXT records quoted.
paddycarver added a commit that referenced this issue Mar 6, 2018
modular-magician added a commit to modular-magician/terraform-provider-google that referenced this issue Sep 27, 2019
Signed-off-by: Modular Magician <magic-modules@google.com>
@ghost
Copy link

ghost commented Mar 29, 2020

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. If you feel I made an error 🤖 🙉 , please reach out to my human friends 👉 hashibot-feedback@hashicorp.com. Thanks!

@ghost ghost locked and limited conversation to collaborators Mar 29, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

3 participants