-
Notifications
You must be signed in to change notification settings - Fork 9k
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
[Docs]: data source aws_route53_zone missing id and name attribute #37908
Comments
Community NoteVoting for Prioritization
Volunteering to Work on This Issue
|
I can pick this up, but would need clarification before:
|
I didn't read the paragraph below, I wonder how many other terraform programmers run into the same problem. I wanted to query for the Zone ID and I knew I could do that, but when I glanced at the docs and it wasn't listed in the attributes section I was confused as I knew I did this before. I looked at my old code to confirm. Other data sources generally do not have that additional paragraph. I would prefer to remove the paragraph and add the arguments listed to the attribute section. But this is more of a personal preference. I leave it up to you what you want to do about the reference documentation. |
@justinretzolk is there any kind of standard to follow? |
Warning This issue has been closed, meaning that any additional comments are hard for our team to see. Please assume that the maintainers will not see them. Ongoing conversations amongst community members are welcome, however, the issue will be locked after 30 days. Moving conversations to another venue, such as the AWS Provider forum, is recommended. If you have additional concerns, please open a new issue, referencing this one where needed. |
Documentation Link
https://registry.terraform.io/providers/hashicorp/aws/5.53.0/docs/data-sources/route53_zone
Description
Missing attribute id for data source aws_route53_zone
This is used when querying for the zone_id of a route53 zone. This functionality does work but not stated in the documentation.
References
No response
Would you like to implement a fix?
None
The text was updated successfully, but these errors were encountered: