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_zone with comment argument is not working (when it changed) #5317

Closed
smaeda-ks opened this issue Feb 25, 2016 · 4 comments
Closed

Comments

@smaeda-ks
Copy link

Hi,

I tried to use "comment" argument in aws_route53_zone{}.
But comment value did not changed.

Official Document: https://www.terraform.io/docs/providers/aws/r/route53_zone.html

At First,
I have applied without comment argument like this.

resource "aws_route53_zone" "test-domain" {
    name = "test-domain"
    vpc_id = #omitted
}

Then, I can see default comment value "Managed by Terraform" set by Terraform in AWS console.
Next I tried to add comment argument that code.

resource "aws_route53_zone" "test-domain" {
    name = "test-domain"
    comment = "test-domain"
    vpc_id = #omitted
}

But comment value did not changed.
Is this a bug? or in the specification?

Thanks.

FYI

$ terraform version
Terraform v0.6.11

$ curl http://169.254.169.254/latest/meta-data/placement/availability-zone
ap-northeast-1

PS
I tried with v0.6.12 but same result.

@stack72
Copy link
Contributor

stack72 commented Feb 25, 2016

Hi @smaeda-ks, I am just about to open a PR that fixes this issue :)

@smaeda-ks
Copy link
Author

Hi @stack72,

Cool!!
Super thanks.

@stack72
Copy link
Contributor

stack72 commented Feb 26, 2016

Closed by @5318 :)

@stack72 stack72 closed this as completed Feb 26, 2016
@ghost
Copy link

ghost commented Apr 27, 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 27, 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

2 participants