Update local dev aliases and ignores - #65
Conversation
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 9fbeb080b6
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
|
|
||
| alias nvimdiff="nvim -d" | ||
| alias awslocal="AWS_ACCESS_KEY_ID=dummy AWS_SECRET_ACCESS_KEY=dummy aws --endpoint-url=http://localhost:4566" | ||
| alias awslocal="AWS_REGION=ap-northeast-1 AWS_ACCESS_KEY_ID=dummy AWS_SECRET_ACCESS_KEY=dummy aws --endpoint-url=http://localhost:4566" |
There was a problem hiding this comment.
Hardcoding AWS_REGION=ap-northeast-1 in the awslocal alias can break common LocalStack command sequences that assume us-east-1 defaults (for example, S3 bucket creation commands that omit a location constraint). This is a behavioral regression from the prior alias because every invocation is now forced into a non-default region, so existing scripts and one-liners that previously worked can start failing unless callers add explicit region-specific flags.
Useful? React with 👍 / 👎.
1 participant
Summary
Tests