deps: github.com/aws/aws-sdk-go@v1.20.4

[bflad]

Relevant changes:

• backend/s3: Support for chaining assume IAM role from AWS shared configuration files
• backend/s3: Fix AWS shared configuration file credential source not assuming a role with environment and ECS credentials

References:

• https://github.com/aws/aws-sdk-go/releases/tag/v1.20.0
• aws/session: Add support for chaining source_profile with credential_source aws/aws-sdk-go#2579
• Environment credential_source in shared config does not assume role aws/aws-sdk-go#2385

Updated via:

$ go get github.com/aws/aws-sdk-go@v1.20.4
$ go mod tidy
$ go mod vendor

Output from acceptance testing:

--- PASS: TestBackend_impl (0.00s)
--- PASS: TestBackendConfig (0.39s)
--- PASS: TestBackendConfig_invalidKey (0.00s)
--- PASS: TestBackend (3.02s)
--- PASS: TestBackendLocked (12.61s)
--- PASS: TestBackendExtraPaths (3.02s)
--- PASS: TestBackendPrefixInWorkspace (1.78s)
--- PASS: TestKeyEnv (9.55s)
--- PASS: TestRemoteClient_impl (0.00s)
--- PASS: TestRemoteClient (1.54s)
--- PASS: TestRemoteClientLocks (6.18s)
--- PASS: TestForceUnlock (9.57s)
--- PASS: TestRemoteClient_clientMD5 (11.79s)
--- PASS: TestRemoteClient_stateChecksum (12.68s)

[tombuildsstuff]

LGTM 👍

[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.