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 #1632

Closed
hashibot opened this issue Sep 11, 2017 · 4 comments
Closed

add support for CAA DNS records to aws_route53_record resource #1632

hashibot opened this issue Sep 11, 2017 · 4 comments
Labels
enhancement Requests to existing resources that expand the functionality or scope.

Comments

@hashibot
Copy link

This issue was originally opened by @danielnbarbosa as hashicorp/terraform#16054. It was migrated here as a result of the provider split. The original body of the issue is below.


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
@hashibot hashibot added the enhancement Requests to existing resources that expand the functionality or scope. label Sep 11, 2017
@bflad
Copy link
Contributor

bflad commented Sep 11, 2017

@danielnbarbosa this support was merged into master a few weeks ago via #1465. However, it has not been "released" yet via version 0.1.5, 0.2.0, or 1.0.0 given the current CHANGELOG. You may wish to participate in #1592 asking for releases of this provider more often if its something you're wanting something sooner rather than later.

@stack72
Copy link
Contributor

stack72 commented Sep 13, 2017

@Ninir I believe this can be closed via #1465

@Ninir
Copy link
Contributor

Ninir commented Sep 13, 2017

Hi folks,

This request was merged in #1467 and followed in #1465, closing! 😄

(Thanks for the ping @stack72 ! 👍 )

@Ninir Ninir closed this as completed Sep 13, 2017
@ghost
Copy link

ghost commented Apr 11, 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. Thanks!

@ghost ghost locked and limited conversation to collaborators Apr 11, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement Requests to existing resources that expand the functionality or scope.
Projects
None yet
Development

No branches or pull requests

4 participants