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

aws_route53_record resources not working when mixed case is used in name #3564

Closed
kxseven opened this issue Oct 20, 2015 · 3 comments · Fixed by #3574
Closed

aws_route53_record resources not working when mixed case is used in name #3564

kxseven opened this issue Oct 20, 2015 · 3 comments · Fixed by #3574

Comments

@kxseven
Copy link

kxseven commented Oct 20, 2015

Summary

  • AWS Route53 resource getting created every time terraform apply is run
  • no resource gets added to the terraform.tfstate file, even after successfully reporting that the resource gets created (it does get created in Route53)

To Reproduce

  • This is an SRV required for MS Active Directory

    resource "aws_route53_record" "ldap_tcp_DefaultFirstSiteSame_sites_domainDnsZones" {
        zone_id = "ABCDEFGHIJKLMNOP"
        name = "_ldap._tcp.default-First-Site-Name._sites.domainDnsZones"
        type = "SRV"
        ttl = "600"
        records = [ "0 100 389 msad-pdc.test.mydomain.com." ]
    }
    
  • This version of it works however;

    resource "aws_route53_record" "ldap_tcp_defaultfirstsitename_sites_domaindnszones" {
        zone_id = "ABCDEFGHIJKLMNOP"
        name = "_ldap._tcp.default-first-site-name._sites.domaindnszones"
        type = "SRV"
        ttl = "600"
        records = [ "0 100 389 msad-pdc.test.mydomain.com." ]
    }
    

Suggestions

  • Have the code always function in lowercase
  • Update the docs to highlight that mixed-case name and name properties are not supported
@catsby
Copy link
Contributor

catsby commented Oct 20, 2015

Thanks @kxseven – I opened #3574 to address this

@kxseven
Copy link
Author

kxseven commented Oct 27, 2015

Duplicate of issue #3246 it seems. Closing this dupe.

@kxseven kxseven closed this as completed Oct 27, 2015
@ghost
Copy link

ghost commented Apr 30, 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 have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

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

Successfully merging a pull request may close this issue.

2 participants