tustvold opened a new pull request, #2891:
URL: https://github.com/apache/arrow-rs/pull/2891
_Draft as not properly tested_
# Which issue does this PR close?
<!--
We generally require a GitHub issue to be filed for all bug fixes and
enhancements and this helps us generate change logs for our releases. You can
link an issue to this PR using the GitHub syntax. For example `Closes #123`
indicates that this PR will close issue #123.
-->
Closes #2178
# Rationale for this change
<!--
Why are you proposing this change? If this is already explained clearly in
the issue then this section is not needed.
Explaining clearly why changes are proposed helps reviewers understand your
changes and offer better suggestions for fixes.
-->
Support for the more esoteric AWS auth options has been requested in various
places, rather than forcing downstreams to workaround this by using an SDK such
as aws-sdk-rust, lets just provide an option to use aws-sdk-rust to get
credentials from a profile. This lets people explicitly opt-in to the full
suite of credential providers, with the accompanying dependency explosion,
whilst still using the same code for actual communication with object storage.
I still would argue aws-vault is a superior solution for credential management
than using AWS named profiles, but we should meet users where they currently
are.
# What changes are included in this PR?
<!--
There is no need to duplicate the description in the issue here but it is
sometimes worth providing a summary of the individual changes in this PR.
-->
Adds an optional aws_profile feature which uses aws-config to provide the
full suite of AWS credential functionality, including SSO, external credential
providers, role chaining, etc...
# Are there any user-facing changes?
No
<!--
If there are user-facing changes then we may require documentation to be
updated before approving the PR.
-->
<!---
If there are any breaking changes to public APIs, please add the `breaking
change` label.
-->
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
