-
Notifications
You must be signed in to change notification settings - Fork 869
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
object_store: different behavior from aws cli for default profile #4137
Comments
What happens if you set I'm struggling to devise a way to achieve this without potentially breaking downstreams in unpredictable ways, we only want to use the aws-config credentials (used to provide AWS_PROFILE) if explicitly opted into by the user. As feature flags should be strictly additive, they are insufficient to gate this functionality. |
It's acceptable workaround, but I also hope there is a warn message when I expect the default profile without the environment variable set but |
FYI #4163 might provide a mechanism for users to opt-in to AWS CLI compatibility, by using the CLI to generate the credentials |
|
Describe the bug
Object store doesn't use the default profile in
~/.aws/config
To Reproduce
aws_profile
~/.aws/config
AWS_PROFILE
valueExpected behavior
object store uses the [default] section for
s3
even if there is noAWS_PROFILE
in the environment variablesAdditional context
Maybe related code position:
https://github.com/apache/arrow-rs/blob/master/object_store/src/aws/mod.rs#L1040
The text was updated successfully, but these errors were encountered: