autoload-credentials doesn't import aws credential in env var

Bug #1977463 reported by Natasha Ho
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Canonical Juju
Expired
Undecided
Unassigned

Bug Description

juju version:
It's reproducible on 2.9.31-ubuntu-amd64
It's unclear which version of juju where this bug is introduced.

What cloud?
AWS. I did not test on other clouds

Steps:
```
export AWS_ACCESS_KEY_ID=test-access=id
export AWS_SECRET_ACCESS_KEY=test-secret-access-key
juju autoload-credentials --client aws
```

Observed output:
Looking for cloud and credential information on local client...
No cloud credentials found.

Revision history for this message
Ian Booth (wallyworld) wrote :

It looks like juju only checks environment variables if there are no credentials defined in ~/.aws/credentials

This behaviour is not new. Whether juju should always look for both env and .aws credentials is another question. I suspect the thinking was that if there were .aws credentials, that should be the definitive source of truth.

Can you confirm that if you rename ~/.aws it now works? It may be we just need to document this better.

Changed in juju:
status: New → Incomplete
Revision history for this message
Natasha Ho (natashaho) wrote :

I don't have ~/.aws on my machine

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for juju because there has been no activity for 60 days.]

Changed in juju:
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.