daviewales opened a new issue, #7204: URL: https://github.com/apache/arrow-rs/issues/7204
**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*) --> Currently, `object_store` automatically detects Azure credentials from environment variables and IMDS. `object_store` also supports retrieving credentials from Azure CLI, however, it does not automatically try this. If you want to retrieve credentials from Azure CLI, you need to manually specify `use_azure_cli=True`. **Describe the solution you'd like** <!-- A clear and concise description of what you want to happen. --> Ideally, `object_store` would try `use_azure_cli=True` if no environment or IMDS credentials can be found. This makes it possible to easily test code on your local machine (based on your Azure CLI credentials), then deploy the code unchanged to an Azure VM, and it will automatically use the environment or IMDS credentials, without requiring any code changes. **Describe alternatives you've considered** <!-- A clear and concise description of any alternative solutions or features you've considered. --> A workaround is to add `AZURE_USE_AZURE_CLI=True` to your local environment variables while testing. However, this is an extra step. **Additional context** <!-- Add any other context or screenshots about the feature request here. --> Most Azure libraries fall back to the Azure CLI credential if environment or IMDS credentials are not found. For example, `fsspec/adlfs`, `azure.identity.DefaultAzureCredential`, `polars`, `pandas`. I'm aware of #6470, but I'm wondering if simply adding a fallback to an already supported authentication method is more in scope than completely replicating `DefaultAzureCredential`. -- 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]
