Refactor DefaultAzureCredential usage#14951
Merged
eerhardt merged 6 commits intomicrosoft:release/13.2from Mar 6, 2026
Merged
Conversation
Contributor
|
🚀 Dogfood this PR with:
curl -fsSL https://raw.githubusercontent.com/dotnet/aspire/main/eng/scripts/get-aspire-cli-pr.sh | bash -s -- 14951Or
iex "& { $(irm https://raw.githubusercontent.com/dotnet/aspire/main/eng/scripts/get-aspire-cli-pr.ps1) } 14951" |
Member
Author
|
/deployment-test |
Contributor
|
🚀 Deployment tests starting on PR #14951... This will deploy to real Azure infrastructure. Results will be posted here when complete. |
Contributor
|
❌ Deployment E2E Tests failed Summary: 13 passed, 12 failed, 0 cancelled Passed Tests
Failed Tests
🎬 Terminal Recordings
|
… parameterless ctor is obsolete.
Contributor
|
The polyglot languages could use such helpers ... one day |
sebastienros
approved these changes
Mar 5, 2026
eerhardt
added
the
breaking-change
Merged
17 tasks
christothes
reviewed
Mar 5, 2026
Contributor
|
❌ Deployment E2E Tests failed Summary: 25 passed, 1 failed, 0 cancelled Passed Tests
Failed Tests
🎬 Terminal Recordings
|
JamesNK
reviewed
Mar 5, 2026
JamesNK
approved these changes
Mar 6, 2026
eerhardt
added a commit
to eerhardt/aspire
that referenced
this pull request
Mar 7, 2026
* Refactor DefaultAzureCredential usage Using the parameterless ctor of DefaultAzureCredential is not recommended. Instead try to detect when we are running in Azure and use Azure credentials. Fallback to using just development credentials when we can't detect we are in Azure. Users can always provide their own to override this behavior. * Update to latest Azure.Identity and use the correct ctor now that the parameterless ctor is obsolete. * Update README docs with the latest information.
Copilot AI
pushed a commit
that referenced
this pull request
Mar 10, 2026
* Refactor DefaultAzureCredential usage Using the parameterless ctor of DefaultAzureCredential is not recommended. Instead try to detect when we are running in Azure and use Azure credentials. Fallback to using just development credentials when we can't detect we are in Azure. Users can always provide their own to override this behavior. * Update to latest Azure.Identity and use the correct ctor now that the parameterless ctor is obsolete. * Update README docs with the latest information.
Closed
1 task
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.
Using the parameterless ctor of DefaultAzureCredential is not recommended. Instead try to detect when we are running in Azure and use Azure credentials. Fallback to using just development credentials when we can't detect we are in Azure.
Users can always provide their own to override this behavior.
Checklist
aspire.devissue:[13.2] Document breaking change on DefaultAzureCredential in client integrations aspire.dev#516