fix: Use the specified region to retrieve the current AWS region #348
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
emuesuenu
changed the title
fix: use var.region in aws_region data source to retrieve correct region
antonbabenko
pushed a commit
that referenced
this pull request
Aug 5, 2025
## [5.3.1](v5.3.0...v5.3.1) (2025-08-05) ### Bug Fixes * Use the specified region to retrieve the current AWS region ([#348](#348)) ([453fcb9](453fcb9))
|
This PR is included in version 5.3.1 🎉 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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
This PR fixes an issue in the
aws_regiondata source by correctly utilizing thevar.regionvariable to ensure the correct AWS region is retrieved. Previously, the region was hardcoded or incorrectly referenced, leading to potential mismatches or unexpected behaviors.Motivation and Context
Using a hardcoded or incorrectly referenced AWS region can result in deployments occurring in unintended regions, potentially causing resource conflicts or compliance issues. By using the existing
var.region, this change ensures consistency and correctness in the configuration.#347
Breaking Changes
No breaking changes introduced. This modification simply corrects the region reference.
How Has This Been Tested?
examples/*to demonstrate and validate my change(s)examples/*projectspre-commit run -aon my pull request