TXT records always require re-creation v 2.0.0-rc1

[wiggly]

Creating a TXT record works but attempting to plan immediately afterwards indicates that changes are required.

This appears to be due to quote-handling.

Example output after having already created the record successfully;

  # gandi_livedns_record.test_txt_menutia_io will be updated in-place
  ~ resource "gandi_livedns_record" "test_txt_menutia_io" {
        id     = "menutia.io/test001/TXT"
        name   = "test001"
        ttl    = 3600
        type   = "TXT"
      ~ values = [
          - "\"this is a test\"",
          + "this is a test",
        ]
        zone   = "menutia.io"
    }

[wiggly]

I have since realised that you can add embedded quotes for this but I find it a bit unintuitive that this is required seeing as the record is obviously meant to accept text content.

[scottmuc]

I can confirm I have the same issue with TXT records.

[fgm]

Similar case. Also similar to #2.

  ~ resource "gandi_livedns_record" "txt" {
        id     = "example.com/@/TXT"
        name   = "@"
      ~ values = [
          + "\"facebook-domain-verification=whateverfb\"",
          + "\"google-site-verification=whatevergoogle\"",
          - "facebook-domain-verification=whateverfb",
          - "google-site-verification=whatevergoogle,
        ]
        # (3 unchanged attributes hidden)
    }

In addition, with terraform 1.0.2, it adds a warning on the plan operation like this:

Unless you have made equivalent changes to your configuration, or ignored the relevant attributes using ignore_changes, the following plan may include actions to undo or respond to these changes.

The warning is worrying. When checking the zone on Gandi, however after the apply step succeeds, the zone entries appear normal:

@ 1800 IN TXT "facebook-domain-verification=whateverfb"
@ 1800 IN TXT "google-site-verification=whatevergoogle"

If there is no envisioned solution, as the existence of the problem since #2 suggests, maybe the docs could add a note not to worry about these ?

[fgm]

Actually, I noticed that using the following format, there is no longer an issue with TF 1.0.4 and the latest Gandi provider:

resource "gandi_livedns_record" "txt" {
  zone   = data.gandi_domain.domain.id
  name   = "@"
  type   = "TXT"
  ttl    = module.defaults.ttl_txt
  values = [
    "\"facebook-domain-verification=fbvalue\"",
    "\"google-site-verification=googlevalue\"",
    "\"keybase-site-verification=keybasevalue"",
  ]
}

[robbyoconnor]

I assume this is no longer an issue?

[scottmuc]

@robbyoconnor I'm due for a TF and Gandi provider upgrade. If/when I do that, I'll post my results.

[vincentbernat]

I have ran into this issue too. As long as you quote the values, this is not an issue. I suppose this could be fixed more gracefully by normalizing a bit. This would fix #41 too. For me, it works good enough and I won't propose a fix myself.