Repository navigation
Conversation
EvertonSA
marked this pull request as ready for review
March 19, 2025 16:19
EvertonSA
marked this pull request as draft
March 20, 2025 07:04
Contributor
Author
|
converting to draft as tests broke and i also would like a second opinion on this issue |
Contributor
|
This pull request has been automatically marked as stale because it has not had recent activity. It will be closed in 5 days if no further activity occurs. Thank you for your contributions. |
github-actions
Bot
added
the
stale
Closed
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
closes #47950
Problem: If multiple tasks run in parallel on the same execution instance there is high chance the instance metadata limit is reached as documented here #47950. The call do metadata API was implemented long time ago and today it feels like no other microsoft integration adhered to this strategy (check before call).
This PR removes this behavior and let
azure.identityManagedIdentityCredentialclass fails naturally.