Description
Re-opening #30468 because this should be addressed as far as I can tell (just closing a clearly relevant issue and even locking the communication doesn't help with actually solving problems).
Is your feature request related to a problem? Please describe.
In the past the Azure library ecosystem was fragmented in terms of credential handling. An infamous error when trying to work with the alleged standard DefaultAzureCredential is:
AttributeError: 'DefaultAzureCredential' object has no attribute 'signed_session'
According to this StackOverflow question, the goal is to clean up the credentials handling:
As of May 2022, all SDKs have been re-released with native support for azure-identity. If you still encounter this error with a given SDK on its latest version, please open an issue asking for a re-release of that SDK here: https://github.com/Azure/azure-sdk-for-python/issues
azure-batch as of its latest version 13.0.0 (released on Nov 9th 2022) still does not support DefaultAzureCredential.
This issue has been raised a few times before:
- azure-identity is not compatible with azure-batch #23583
- Azure BatchServiceClient does not work with DefaultAzureCredential #28739
The issues vaguely mention that this feature will come eventually (#23583 (comment) suggesting by the end of 2022, which apparently hasn't happened), but the tickets have been closed, without actually being resolved.
It would be great we can have a proper "tracking issue" that actually gets closed, once the feature really is there. This way, users can really react to the change. Closing the issues without really having resolved the issue only leads to confusion (implying that it might work already), and misses an opportunity to use the issue ticket as an "announcement" to its watchers via the closing action.
Describe the solution you'd like
Re-release azure-batch with DefaultAzureCredential support and keep this issue open until that point.