Skip to content

Conversation

@FlorinAndrei
Copy link
Contributor

@FlorinAndrei FlorinAndrei commented Oct 31, 2025

Description

This module can optionally create Route53 records for the load balancers. The records are of type A, aliases.
The aws_route53_record resource, when created as an alias, allows setting the mandatory attribute evaluate_target_health, with possible values true or false.
This module forces evaluate_target_health = true for all aliases.
So I allowed the users to set this attribute.

Motivation and Context

Modules should not force choices on users, when choices exist.
Also, I have other resources of this kind, and we don't always force evaluate_target_health = true there.

Breaking Changes

None. The evaluate_target_health remains optional, with a default value of true which matches the current behavior of the module.

How Has This Been Tested?

  • I have updated at least one of the examples/* to demonstrate and validate my change(s)
  • I have tested and validated these changes using one or more of the provided examples/* projects
  • I have tested it with my own code, which is identical to the examples when it comes to Route53
  • I have executed pre-commit run -a on my pull request

@FlorinAndrei
Copy link
Contributor Author

I've tested that by flipping the attribute back and forth between true and false the Route53 record is indeed updated accordingly.

@bryantbiggs bryantbiggs changed the title allow setting evaluate_target_health for Route53 records feat: Allow setting evaluate_target_health for Route53 records Nov 3, 2025
@bryantbiggs bryantbiggs merged commit ebad35b into terraform-aws-modules:master Nov 3, 2025
9 checks passed
antonbabenko pushed a commit that referenced this pull request Nov 3, 2025
## [10.2.0](v10.1.0...v10.2.0) (2025-11-03)

### Features

* Allow setting `evaluate_target_health` for Route53 records ([#423](#423)) ([ebad35b](ebad35b))
@antonbabenko
Copy link
Member

This PR is included in version 10.2.0 🎉

@github-actions
Copy link

github-actions bot commented Dec 4, 2025

I'm going to lock this pull request 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 related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Dec 4, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants