Repository navigation
fix: set AWS region to ap-south-2 for consistent resource management - #166
Merged
Merged
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
This pull request includes a minor version bump for the
serverpackage and an update to the AWS deployment script to ensure regional consistency for AWS CLI calls.Deployment script improvements:
aws/aws.shto explicitly setAWS_DEFAULT_REGIONandAWS_REGIONenvironment variables to the stack's region, preventing mismatches between local configuration and the actual stack location. This ensures that operations like tearing down resources target the correct AWS region.Version update:
serverpackage version from4.11.36to4.11.37inserver/package.json.