You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I inspected the verbose debug output with the -v, --verbose flag.
Are you an Up Pro subscriber?
Description
AWS_PROFILE environment variable is interfering with AWS SDK V3 credentials
Describe the bug or feature.
When migrating from V2 to V3 AWS SDK i discovered that AWS_PROFILE is persisted in the lambda execution environment variables.
The only location that I defined this was in the "profile" section of up.json, the new AWS SDK version fails to load because of this.
Describe the steps required to reproduce the issue if applicable.
you can either run the ./run.test.sh or follow the outlined steps in the project README.md
Prerequisites
up upgrade
)-v, --verbose
flag.Description
AWS_PROFILE environment variable is interfering with AWS SDK V3 credentials
Describe the bug or feature.
When migrating from V2 to V3 AWS SDK i discovered that AWS_PROFILE is persisted in the lambda execution environment variables.
The only location that I defined this was in the "profile" section of up.json, the new AWS SDK version fails to load because of this.
Steps to Reproduce
I created a sample app and published the repo to demonstrate this issue:
https://github.com/benkauffman/apex-up-aws-sdk-v3-bug-example
Describe the steps required to reproduce the issue if applicable.
you can either run the ./run.test.sh or follow the outlined steps in the project README.md
Slack
Join us on Slack https://chat.apex.sh/
The text was updated successfully, but these errors were encountered: