[Storage] Switch from ClientSecretCredential to DefaultAzureCredential
#35651
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
vincenttran-msft
requested review from
scbedd,
mccoyp,
annatisch,
jalauzon-msft and
weirongw23-msft
as code owners
|
API change check API changes are not detected in this pull request. |
6 tasks
mccoyp
approved these changes
May 18, 2024
|
/azp run python - storage - tests |
|
Azure Pipelines successfully started running 1 pipeline(s). |
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.
This PR aims to move away from using discrete
ClientSecretCredentialfor OAuth operations and to instead now useDefaultAzureCredential.This also means that you have to routinely do
az loginwhen running OAuth tests to refresh your permission, but will get away from those pesky secrets 馃槃TODO: