AWS nuke not working with credential_process + source_profile + role_arn combination

[reegnz]

Expected Behaviour

Given config:

[profile test]
region = us-west-2
credential_process = cat ./cred.json

[profile testnoassume]
source_profile = test

[profile testassume]
source_profile = test
role_arn = arn:aws:iam::222222222222:role/OrganizationAccountAccessRole

When:

• executing aws-nuke with profile testassume or testnoassume

Then:

• aws-nuke should connect to aws properly.

Actual Behaviour

aws-nuke fails the following commands:

$ aws-nuke --config config.yaml --profile testassume
Error: failed to create default session in us-east-1: SharedConfigAssumeRoleError: failed to load assume role for arn:aws:iam::222222222222:role/OrganizationAccountAccessRole, source profile has no shared credentials

and

$ aws-nuke --config config.yaml --profile testnoassume
Error: failed get caller identity: NoCredentialProviders: no valid providers in chain. Deprecated.
	For verbose messaging see aws.Config.CredentialsChainVerboseErrors

Additional Context

https://docs.aws.amazon.com/cli/latest/topic/config-vars.html#sourcing-credentials-from-external-processes

Very similar issue:
hashicorp/packer#7142 (comment)

Looks like this could be an SDK issue, so upgrading to the latest go sdk might solve this.

[reegnz]

i will try and upgrade to a newer sdk and see if it fixes this issue.