Should DefaultAzureCredential expose that it is using ChainedTokenCredential? #4419
Labels
Azure.Identity
bug
This issue requires a change to an existing behavior in the product in order to be resolved.
Client
This issue points to a problem in the data-plane of the library.
I'd rather let the user know that DefaultAzureCredential is using ChainedTokenCredential, so that should they want to build their own credential chain, or customize it, the credential suggests the next step for them.
But there is opinion to not expose it, so that is why I am opening this issue - to discuss it.
If we decide to not expose it, let's also update README.md and DefaultAzureCredential's doxygen coments, because we documented it there.
See #4409 (comment)
The text was updated successfully, but these errors were encountered: