request: Update aws/aws-sdk-go to 1.22.0

[007]

Terraform Version

Terraform v0.12.6

Expected Behavior

Order of precedence for AWS credentials follows CLI precedence

Actual Behavior

Upstream change made AWS_PROFILE override AWS_*_KEY behavior

Steps to Reproduce

I can't reproduce this directly, but I know that this will bite someone who expects AWS CLI precedence. I believe setting AWS_PROFILE=nonexistent and having AWS_*_KEY values set to valid key+secret will show the behavior.

Additional Context

This may affect terraform-provider-aws too, but I haven't investigated which version of aws-sdk-go it is using.

References

#22253 changed the behavior by pulling the then-current [email protected], the newest upstream release is [email protected] which changes the precedence back (closer) to CLI order.

[teamterraform]

Hi @007,

Thanks for filing this.
Core actually depends on the AWS provider, so as to ensure that the client behavior matches.
Once the AWS provider is updated, we can pull the new dependencies from there.

[bflad]

It appears this may have been resolved awhile ago -- the AWS Go SDK dependency on master is v1.25.3 and will soon be updated to v1.30.12. If there are still lingering issues on the latest version of the Terraform CLI, please do not hesitate to open a new issue and we will take a fresh look. 👍

[ghost]

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.