Increase IMDS retry count to 5 #43249
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
christothes
requested review from
KarishmaGhiya,
ahsonkhan,
billwert,
chlowell,
maorleger and
pvaneck
ahsonkhan
reviewed
Apr 5, 2024
sdk/identity/Azure.Identity/src/DefaultAzureCredentialFactory.cs
Outdated
Show resolved
Hide resolved
ahsonkhan
approved these changes
Apr 5, 2024
christothes
force-pushed
the
chriss/mi-retryCount
branch
from
1a3178e to
639be26
Compare
christothes
requested review from
ArthurMa1978,
JoshLove-msft,
KrzysztofCwalina,
annelo-msft,
jsquire,
m-nash,
pallavit and
tg-msft
as code owners
jsquire
approved these changes
Apr 8, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Contributing to the Azure SDK
Please see our CONTRIBUTING.md if you are not familiar with contributing to this repository or have questions.
For specific information about pull request etiquette and best practices, see this section.