Fixed resolving secrets for keyvault references in run mode#8751
Merged
Fixed resolving secrets for keyvault references in run mode#8751
Conversation
- Moved token credential resolution out of the AzureProvisioner so it can shared. - Configure the secret resolving in both configure and provision cases.
Member
|
Looks good. Should we be hotfixing this? |
Contributor
Author
|
Yep |
mitchdenny
approved these changes
Apr 13, 2025
Contributor
|
Legend |
Contributor
Author
|
/backport to release/9.2 |
Contributor
|
Started backporting to release/9.2: https://github.com/dotnet/aspire/actions/runs/14430623244 |
1 task
5 tasks
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Description
Fixes #8750
Checklist
template=02-docs-request.yml)):