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

add support for CAA DNS records to aws_route53_record resource #16054

Closed
danielnbarbosa opened this issue Sep 8, 2017 · 3 comments
Closed

add support for CAA DNS records to aws_route53_record resource #16054

danielnbarbosa opened this issue Sep 8, 2017 · 3 comments

Comments

@danielnbarbosa
Copy link

The new CAA record is supported by AWS Route53 but not considered a valid type by terraform. CAA is used to whitelist which certificate authorities are authorized to issue SSL certificates for your domain. It is quite new and was only added to AWS on August 21, 2017. CAs are expected to start enforcing it in September 2017.

Terraform Version

Terraform v0.10.4

Terraform Configuration Files

resource "aws_route53_record" "pear_caa" {
  zone_id = "${aws_route53_zone.pear.zone_id}"
  name    = "pear.md"
  type    = "CAA"
  ttl     = "300"
  records = ["0 issue \"godaddy.com\""]
}

Expected Behavior

terraform plan should work

Actual Behavior

terraform plan returns error on resource type:

1 error(s) occurred:

* module.global_prod.aws_route53_record.pear_caa: "type" must be one of [SOA, A, TXT, NS, CNAME, MX, NAPTR, PTR, SRV, SPF, AAAA]

Steps to Reproduce

Please list the full steps required to reproduce the issue, for example:

  1. terraform plan
@007
Copy link

007 commented Sep 9, 2017

@hashibot
Copy link
Contributor

This issue has been automatically migrated to hashicorp/terraform-provider-aws#1632 because it looks like an issue with that provider. If you believe this is not an issue with the provider, please reply to this issue and let us know.

@ghost
Copy link

ghost commented Apr 7, 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 7, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants