-
-
Notifications
You must be signed in to change notification settings - Fork 910
$AWS_PROFILE is not honored #906
Description
This mentions something similar, and suggests using --configure, but that apparently uses the ~/.s3cfg file. Shouldn't I be able to use a command like AWS_PROFILE=foo s3cmd ... and use the "foo" profile from ~/.aws/credentials?
As someone who routinely uses multiple aws profiles, this is painful because I don't really want to keep another file in sync, and I also don't want to have to view my credentials files and copy/paste environment variables for AWS_ACCESS_KEY_ID/AWS_SECRET_ACCESS_KEY.
If there is agreement that this is a bug, I can probably submit a patch.
EDIT: found this comment from 2015 suggesting using the credentials file, and this mention in the same thread that a patch would be accepted. Can anyone confirm this is still desired?