-
Notifications
You must be signed in to change notification settings - Fork 846
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature Request: Configurable Timeout for AzureCLICredential in azidentity
#21985
Comments
Its configurable in the python sdk
|
You can control this timeout by setting a deadline on the azure-sdk-for-go/sdk/azidentity/azure_cli_credential.go Lines 105 to 110 in 7d4a3cb
|
Hi @Aricg. Thank you for opening this issue and giving us the opportunity to assist. We believe that this has been addressed. If you feel that further discussion is needed, please add a comment with the text "/unresolve" to remove the "issue-addressed" label and continue the conversation. |
thanks. Azure/kubelogin#362 |
Hi @Aricg, since you haven’t asked that we |
Feature Request: Configurable Timeout for AzureCLICredential
Description
make the timeout duration configurable in the
AzureCLICredential
of theazidentity
package. Currently, the timeout is hardcoded to 10 seconds.Justification
Suggested Implementation
The timeout could be made configurable through the
AzureCLICredentialOptions
struct. For instance, a new fieldTimeout
could be added to this struct. This new field would then be used in theauthenticate
method ofAzureCLICredential
.this would I believe be a Non-Intrusive Addition: Adding a new field to a struct in Go does not alter the existing behavior of the struct for current users. Existing code that creates and uses AzureCLICredentialOptions without setting the new Timeout field will continue to function as before, as Go initializes unspecified fields to their zero value.
Current Code Reference
The current implementation with the hardcoded timeout is located here:
azure_sdk_for_go/azure_cli_credential.go at e1d15b65278a1c714f2dd1349fa4098d72d0fe7b
Additional Context
This feature request is motivated by intermittent failures observed in projects that use
azidentity
, specifically when integrating with tools likekubelogin
. An example of such an issue can be found here: kubelogin issue #223The text was updated successfully, but these errors were encountered: