KirillTsyganov opened a new pull request, #46837:
URL: https://github.com/apache/arrow/pull/46837

   Adding ConfigureClientSecretCredential to AzureFilesystem, which is already 
implemented at the C++, but hasn't been propagated to python library.
   
   `ClientSecretCredential` is how one can authenticate to Azure resource using 
Service Principle (SP). We need this in context of AzureML, where 
ComputeInstance (personal VM) can use `DefaultAzureCredential` and pyarrow 
works, but on ComputeCluster `DefaultAzureCredential` doesn't work and we need 
to use SP to authenticate to Azure storage account.
   
   Also adding unit tests for AzureFileSystem options
   
   Thanks for opening a pull request!
   
   If this is your first pull request you can find detailed information on how 
to contribute here:
   
     * [New Contributor's 
Guide](https://arrow.apache.org/docs/dev/developers/guide/step_by_step/pr_lifecycle.html#reviews-and-merge-of-the-pull-request)
     * [Contributing 
Overview](https://arrow.apache.org/docs/dev/developers/overview.html)
   
   Please remove this line and the above text before creating your pull request.
   
   ### Rationale for this change
   
   ### What changes are included in this PR?
   
   ### Are these changes tested?
   
   ### Are there any user-facing changes?
   
   **This PR includes breaking changes to public APIs.** (If there are any 
breaking changes to public APIs, please explain which changes are breaking. If 
not, you can remove this.)
   
   **This PR contains a "Critical Fix".** (If the changes fix either (a) a 
security vulnerability, (b) a bug that caused incorrect or invalid data to be 
produced, or (c) a bug that causes a crash (even when the API contract is 
upheld), please provide explanation. If not, you can remove this.)
   


-- 
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]

Reply via email to