Skip to content

Conversation

@tellnes
Copy link
Contributor

@tellnes tellnes commented Dec 8, 2025

Adds the target_ips attribute to the aws_route53_resolver_rule data source.

Rollback Plan

If a change needs to be reverted, we will publish an updated version of the library.

Changes to Security Controls

Are there any changes to security controls (access controls, encryption, logging) in this pull request? If so, explain.

No changes to security controls.

Description

Exposes the target IP addresses configured for Route53 Resolver FORWARD rules. Each target includes ip, ipv6, port, and protocol fields.

This data is available from the AWS API and is already exposed in the corresponding resource, so this change brings the data source to feature parity for read operations.

The implementation reuses the existing flattenRuleTargetIPs function from the resource to maintain consistency.

Note: The server_name_indication field is not included in this PR as it is being added separately in #40127 to avoid conflicts and ensure proper implementation across both the resource and data source.

References

Output from Acceptance Testing

% make testacc TESTS=TestAccRoute53ResolverRuleDataSource_targetIPs PKG=route53resolver

Pending - will update once available.

@tellnes tellnes requested a review from a team as a code owner December 8, 2025 19:13
@github-actions
Copy link
Contributor

github-actions bot commented Dec 8, 2025

Community Guidelines

This comment is added to every new Pull Request to provide quick reference to how the Terraform AWS Provider is maintained. Please review the information below, and thank you for contributing to the community that keeps the provider thriving! 🚀

Voting for Prioritization

  • Please vote on this Pull Request by adding a 👍 reaction to the original post to help the community and maintainers prioritize it.
  • Please see our prioritization guide for additional information on how the maintainers handle prioritization.
  • Please do not leave +1 or other comments that do not add relevant new information or questions; they generate extra noise for others following the Pull Request and do not help prioritize the request.

Pull Request Authors

  • Review the contribution guide relating to the type of change you are making to ensure all of the necessary steps have been taken.
  • Whether or not the branch has been rebased will not impact prioritization, but doing so is always a welcome surprise.

@github-actions
Copy link
Contributor

github-actions bot commented Dec 8, 2025

✅ Thank you for correcting the previously detected issues! The maintainers appreciate your efforts to make the review process as smooth as possible.

@github-actions github-actions bot added needs-triage Waiting for first response or review from a maintainer. documentation Introduces or discusses updates to documentation. tests PRs: expanded test coverage. Issues: expanded coverage, enhancements to test infrastructure. service/route53resolver Issues and PRs that pertain to the route53resolver service. size/M Managed by automation to categorize the size of a PR. labels Dec 8, 2025
@tellnes tellnes force-pushed the f-route53-resolver-rule-data-source-target-ips branch from 13d8eca to 887a2a5 Compare December 8, 2025 19:16
@justinretzolk justinretzolk added enhancement Requests to existing resources that expand the functionality or scope. and removed needs-triage Waiting for first response or review from a maintainer. labels Dec 9, 2025
Adds the `target_ips` attribute to the `aws_route53_resolver_rule`
data source to expose the list of target IP addresses configured
for FORWARD rules. This includes IPv4 (`ip`), IPv6 (`ipv6`),
port, and protocol information for each target.
@tellnes tellnes force-pushed the f-route53-resolver-rule-data-source-target-ips branch from 887a2a5 to a86fe80 Compare December 10, 2025 19:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Introduces or discusses updates to documentation. enhancement Requests to existing resources that expand the functionality or scope. service/route53resolver Issues and PRs that pertain to the route53resolver service. size/M Managed by automation to categorize the size of a PR. tests PRs: expanded test coverage. Issues: expanded coverage, enhancements to test infrastructure.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants