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

Interpolation allows non-existent properties to be set on a resource #1507

Closed
johnrengelman opened this issue Apr 13, 2015 · 2 comments · Fixed by #1626
Closed

Interpolation allows non-existent properties to be set on a resource #1507

johnrengelman opened this issue Apr 13, 2015 · 2 comments · Fixed by #1626
Assignees

Comments

@johnrengelman
Copy link
Contributor

I was updating some documentation and came across a configuration that didn't seem correct:
https://www.terraform.io/docs/providers/aws/r/route53_zone.html

resource "aws_route53_zone" "main" {
  name = "example.com"
}

resource "aws_route53_zone" "dev {
  name = "dev.example.com"
  parent_route53_zone = "${aws_route53_zone.main.zone_id}"
}

The parent_route53_zone doesn't exist in the schema for the route53_zone resource, but this configuration doesn't throw an error.

However, if you change the value of the property from an interpolated value to a static value parent_route53_zone = "test", then you will get an error during evaluation of the configuration (which is what should be expected).

@mitchellh
Copy link
Contributor

Yeah that is really weird. Tagged.

@ghost
Copy link

ghost commented May 3, 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 May 3, 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