Skip to content

Conversation

jma127
Copy link

@jma127 jma127 commented Aug 7, 2018

This commit allows the credentials to be read from ~/.aws/credentials
or user-specified (via envvar) file if .s3cfg exists but does not have
authentication options.

The previous behavior is that s3cmd will not read credentials from the
above path as long as .s3cfg exists (even if it contains no
authentication options).

@jma127 jma127 force-pushed the master branch 4 times, most recently from 485d3a6 to 1174ba0 Compare August 8, 2018 00:04
@jma127
Copy link
Author

jma127 commented Aug 8, 2018

OK, this should be in a semi-decent state now. Please let me know if any changes are needed.

nonexistent or empty.

This commit allows the credentials to be read from ~/.aws/credentials
or user-specified (via envvar) file if .s3cfg exists but does not have
authentication options.

The previous behavior is that s3cmd will *not* read credentials from the
above path as long as .s3cfg exists (even if it contains no
authentication options).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant