tustvold opened a new issue, #169: URL: https://github.com/apache/arrow-rs-object-store/issues/169
**Is your feature request related to a problem or challenge? Please describe what you are trying to do.** <!-- A clear and concise description of what the problem is. Ex. I'm always frustrated when [...] (This section helps Arrow developers understand the context and *why* for this feature, in addition to the *what*) --> All the cloud providers provide CLIs for interacting with their service offering, a number of these come with fairly convoluted configuration setups for sourcing credentials. By and large these do not follow any widely adopted standard, and are inordinately complex. **Describe the solution you'd like** <!-- A clear and concise description of what you want to happen. --> Rather than implementing all the various different authentication options, a truly herculean task, we could provide an option to shell out the CLI to obtain the credentials. @roeap added this for Azure in https://github.com/apache/arrow-rs/pull/3698. Both AWS and GCP support this with ``` aws sts get-session-token gcloud auth print-access-token ``` This would provide an escape hatch for CLI tools, without requiring a large amount of custom tooling. It would also provide complete coverage of all the options, including functionality that is not supported yet in any Rust library (e.g. GCP workload federation). Finally it would allow for workloads to choose to maximise compatibility by explicitly opting into using CLI-generated credentials apache/arrow-rs#4137 **Describe alternatives you've considered** <!-- A clear and concise description of any alternative solutions or features you've considered. --> **Additional context** <!-- Add any other context or screenshots about the feature request here. --> https://github.com/apache/arrow-rs/pull/2891 added experimental support for AWS_PROFILE https://github.com/apache/arrow-rs/issues/3797 tracks adding support for more complex GCP authentication -- 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]
