New version: AWS v1.86.0 #83398
Merged
New version: AWS v1.86.0 #83398
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
Contributor
JuliaRegistrator
commented
May 11, 2023
JuliaRegistrator
commented
- Registering package: AWS
- Repository: https://github.com/JuliaCloud/AWS.jl
- Created by: @omus
- Version: v1.86.0
- Commit: 9a4322a87c0860e5257476e9b06c961a98e93664
- Reviewed by: @omus
- Reference: JuliaCloud/AWS.jl@9a4322a#commitcomment-112938783
- Description: Julia interface to AWS
UUID: fbe9abb3-538b-5e4e-ba9e-bc94f4f92ebc Repo: https://github.com/JuliaCloud/AWS.jl.git Tree: 9368c9a4e009474f03603e0d06b77b458648de5a Registrator tree SHA: f73a20c99934db92a256057d0d83ba394036a701
JuliaRegistrator
referenced
this pull request
in JuliaCloud/AWS.jl
May 11, 2023
621: Update credential precedence to match AWS CLI r=omus a=omus I noticed there were some credential precedence ordering differences between AWS.jl and AWS CLI. I ended up doing some experimentation with pairing different AWS CLI settings to determine the precedence ordering used by AWS CLI. Here are the results of those tests: - aws `--profile` used over env `AWS_ACCESS_KEY_ID`/`AWS_SECRET_ACCESS_KEY` - aws `--profile` used over env `AWS_PROFILE` - env `AWS_ACCESS_KEY_ID`/`AWS_SECRET_ACCESS_KEY` used over env `AWS_PROFILE` - env `AWS_ACCESS_KEY_ID`/`AWS_SECRET_ACCESS_KEY` used over config file `sso_*` - config file `sso_*` used over `~/.aws/credentials` (if exists) - `~/.aws/credentials` (if exists) used over config file `credential_process` - config file `credential_process` used over config file `aws_access_key_id`/`aws_secret_access_key` - config file `aws_access_key_id`/`aws_secret_access_key` used over EC2 instance metadata - config file `aws_access_key_id`/`aws_secret_access_key` used over `AWS_CONTAINER_CREDENTIALS_FULL_URI` Using `aws-cli/2.11.13 Python/3.11.3 Darwin/22.4.0 source/arm64 prompt/off` Notes: - Defining `sso_account_id` or `sso_role_name` in a profile without other `sso_*` keys results in an error about missing required configuration. Defining `sso_start_url` and `sso_region` by themselves doesn't produce this error. - Specifying the AWS credential file with `AWS_SHARED_CREDENTIALS_FILE` just replaces `~/.aws/credentials` - Tested this by specifying bad credentials in one source and valid ones in the other. As I didn't have an SSO setup to test against I could only force these to fail. - Some additional testing was done to verify that the credential preference ordering is linear. I didn't find any examples of non-linear ordering. Co-authored-by: Curtis Vogt <[email protected]>
JuliaRegistrator
temporarily deployed
to
stopwatch
GitHub Actions
Inactive
|
Your If you want to prevent this pull request from being auto-merged, simply leave a comment. If you want to post a comment without blocking auto-merging, you must include the text |
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.