Allow empty names in dme_record (dnsmadeasy)

[hashibot]

This issue was originally opened by @benosman as hashicorp/terraform#9034. It was migrated here as part of the provider split. The original body of the issue is below.

---

I'm having issues setting any kind of record with an empty name field. Name field is required so must be present.

Terraform Version

Terraform v0.7.4

Affected Resource(s)

• dme_record

  Terraform Configuration Files

resource "dme_record" "a_record" {
  domainid = "${var.domainid}"
  name = ""
  type = "A"
  value = "8.8.8.8"
  ttl = "600"
  gtdLocation = "DEFAULT"
}

resource "dme_record" "txt_record" {
  domainid = "${var.domainid}"
  name = ""
  type = "TXT"
  value = "v=spf1 mx a"
  ttl = "600"
  gtdLocation = "DEFAULT"
}

Debug Output

https://gist.github.com/benosman/b4381a3b871c1bee8ec9243fb1fb12c0

Expected Behavior

Records should have been added on the TLD.

Actual Behavior

500 Internal server error.

Steps to Reproduce

1. terraform apply

   References

Similar issues on other DNS providers:

• GH-8944 - dyn_record
• GH-7534 - aws_route53_record

[BlinkyStitt]

So is there any workaround for this? I can't set MX records

[emsearcy]

@WyseNynja I'm also just looking into DME via Terraform and running into these issues. I happen to be using a Makefile for Terraform to automate variable secrets ... I extended it with local build steps to use a patched DME provider. You're welcome to use this as-is or as a reference to rebuild the provider from your own patches, until the maintainers apply these fixes. Mine currently builds with patches to address issues #3, #10, and soniah/dnsmadeeasy#3:

https://gist.github.com/emsearcy/40cdef0efa80d5e61116474f2442eff9

[nkatarmal-crest]

Closing this issue, as provider has been redeveloped and released.