[release/8.0] Use TokenCredential for Cosmos tests #33966
Merged
Conversation
This file contains 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
AndriySvyryd
force-pushed
the
SecureCosmos_8.0
branch
3 times, most recently
from
052919f
to
206b928
Compare
roji
approved these changes
Jun 12, 2024
AndriySvyryd
force-pushed
the
SecureCosmos_8.0
branch
from
206b928
to
d1a2bed
Compare
AndriySvyryd
added
Servicing-consider
Servicing-approved
and removed
tell-mode
Servicing-consider
labels
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.
Port of #33956
Required for https://devdiv.visualstudio.com/DevDiv/_workitems/edit/2054020
Description
We test the EF Cosmos DB provider against an Azure Cosmos DB account. A new requirement for these non-production accounts is to use managed identity authentication.
This PR contains the changes needed to prevent build failures once local auth is disabled for these accounts. It was erroneously merged after code complete without explicit approval.
Customer impact
N/A
How found
S360
Regression
N/A
Testing
Tested using a manual pipeline run
Risk
Low, test-only change