fix: Correct iterator name in dynamic timeouts blocks #526
+13
−6
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Fixed incorrect iterator reference in dynamic
timeoutsblocks. Changed fromeach.valuetotimeouts.valueto match the actual iterator label in bothaws_rds_clusterandaws_rds_cluster_instanceresources.Motivation and Context
The dynamic blocks for timeouts were using
each.valueinstead oftimeouts.value, which would cause runtime errors whenvar.cluster_timeoutsorvar.instance_timeoutsare set. This fix ensures the timeouts configuration works correctly when provided.Breaking Changes
No breaking changes. This is a bug fix that corrects the implementation to work as intended.
How Has This Been Tested?
examples/*to demonstrate and validate my change(s)examples/*projectspre-commit run -aon my pull request