Add support for AWS_PROFILE environment variable #206
Merged
Conversation
This file contains 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
…an AWS_DEFAULT_PROFILE)
|
Ok, thanks for that @alewando . I will double check that and merge if all good. |
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.
This PR adds support for using the AWS_PROFILE environment variable to specify which credential profile to use. This is in line with the AWS CLI and most other SDKs (boto, for example). Use of AWS_DEFAULT_PROFILE is deprecated, and AWS_PROFILE has been preferred for a long while now (see https://docs.aws.amazon.com/cli/latest/userguide/cli-environment.html).
Similar to the support in AWS_CLI, though, AWS_PROFILE has a lower precedence than AWS_DEFAULT_PROFILE (for backwards compatibility). So if both are set, then AWS_DEFAULT_PROFILE is honored.