You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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).
The text was updated successfully, but these errors were encountered:
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
locked and limited conversation to collaborators
May 3, 2020
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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
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).The text was updated successfully, but these errors were encountered: