-
Couldn't load subscription status.
- Fork 713
[release/9.5] Fix ParameterProcessor to use ExecutionContextOptions and skip excluded resources #11782
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
…ed resources - Use DistributedApplicationExecutionContextOptions constructor in CollectDependentParameterResourcesAsync - Copy ServiceProvider from existing execution context when available - Skip resources excluded from publish using IsExcludedFromPublish() - Add tests to verify ServiceProvider access and excluded resource filtering Co-authored-by: davidfowl <95136+davidfowl@users.noreply.github.com>
Use the executionContext from constructor instead of creating a new publishExecutionContext Co-authored-by: davidfowl <95136+davidfowl@users.noreply.github.com>
|
🚀 Dogfood this PR with:
curl -fsSL https://raw.githubusercontent.com/dotnet/aspire/main/eng/scripts/get-aspire-cli-pr.sh | bash -s -- 11782Or
iex "& { $(irm https://raw.githubusercontent.com/dotnet/aspire/main/eng/scripts/get-aspire-cli-pr.ps1) } 11782" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Targeted fix, low risk, Fixing experience of new feature. Approved
Backport of #11734 to release/9.5
/cc @davidfowl @copilot
Customer Impact
While processing parameters for deploy, we don't exclude resources that should be excluded from publish. This runs logic that should not run which sometimes breaks because it shouldn't run and includes more parameters than necessary.
Testing
Automated and manual.
Risk
Low
Regression?
No