[New Data Source]: List of AWS ROUTE53 RECORDS. Providing differents ways to filter

[luarx]

Description

A new datasource to obtain a list of aws route53 records using different filters.

The main use case why this is requested is to create a Terraform logic that:

• Obtains a list of aws_route53_records (this is were the new datasource will be required)
• Loops the previous list to create a aws_route53_health_check resource for each of those records

Requested Resource(s) and/or Data Source(s)

data "aws_route53_records" "selected" {
  [optional] zone_id = "test.com."
  [optional] name=  "*.blabla.test.com." (this accepts regex)
  [optional] private_zone = true
}

Potential Terraform Configuration

No response

References

No response

Would you like to implement a fix?

No

[github-actions]

Community Note

Voting for Prioritization

• Please vote on this issue by adding a 👍 reaction to the original post to help the community and maintainers prioritize this request.
• Please see our prioritization guide for information on how we prioritize.
• Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request.

Volunteering to Work on This Issue

• If you are interested in working on this issue, please leave a comment.
• If this would be your first contribution, please review the contribution guide.

[justinretzolk]

Relates: #27851
Relates: #24045

[PT-GD]

In implementing this, please also include tags as a filter, just as in https://registry.terraform.io/providers/hashicorp/aws/latest/docs/data-sources/route53_zone#tags .

An example use cases would include a Kubernetes cluster where a load balancer is constructed by a controller in the cluster, however other Terraform resources depend on the dynamically generated name of the load balancer.

[Siddarthyuvaraj]

PR has been raised for this issue
#38186

[github-actions]

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.