cargo lambda deploy didn't seem to respect region argument? #839
Description
This was from a Github action job:
CLI command:
cargo lambda deploy --extension --region us-east-2 --lambda-dir target/lambda/x86-64 \
--binary-name XXX "XXX" | tee -a /tmp/lambda-deploy.out
Environment:
AWS_DEFAULT_REGION: us-east-1
AWS_REGION: us-east-1
AWS_ACCESS_KEY_ID: ***
AWS_SECRET_ACCESS_KEY: ***
AWS_SESSION_TOKEN: ***
And I got the output:
✅ extension uploaded successfully 🎉
🛠️ binary last compiled 23 seconds ago
🔍 extension arn: arn:aws:lambda:us-east-1:12345xxx:layer:XXX:3
My expectation would have been that it deployed to us-east-2 since the CLI arg would have taken precedence?