[release/13.4] Reference Foundry project from hosted agent target#17704
Conversation
|
🚀 Dogfood this PR with:
curl -fsSL https://raw.githubusercontent.com/microsoft/aspire/main/eng/scripts/get-aspire-cli-pr.sh | bash -s -- 17704Or
iex "& { $(irm https://raw.githubusercontent.com/microsoft/aspire/main/eng/scripts/get-aspire-cli-pr.ps1) } 17704" |
194f27b to
74ea592
Compare
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Seed Foundry project outputs in tests that directly invoke hosted-agent environment resolution, matching the provisioning state available during deployment. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
74ea592 to
b7ac7c1
Compare
|
❓ CLI E2E Tests unknown — 110 passed, 0 failed, 2 unknown (commit View all recordings
📹 Recordings uploaded automatically from CI run #26668769663 |
…r hosted agents Documents that in publish mode, Aspire automatically injects Foundry project connection environment variables into the deployment container (the actual workload). Previously the docs only mentioned container registry publishing; this adds the connection injection behavior fixed by microsoft/aspire#17704. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
|
Pull request created: #1133
|
|
📝 Documentation has been drafted in microsoft/aspire.dev#1133 targeting Updated Note This draft PR needs human review before merging. |
Backport of #17687 to release/13.4
/cc @davidfowl @tommasodotNET
Customer Impact
Customers deploying Foundry hosted agents in publish mode could miss the Foundry project connection environment annotations on the actual deployment target, causing the generated/existing container target to be deployed without the Foundry project connection configuration it needs.
Testing
Source PR validation ran
./restore.shanddotnet test --project tests/Aspire.Hosting.Foundry.Tests/Aspire.Hosting.Foundry.Tests.csproj --no-launch-profile -- --filter-not-trait "quarantined=true" --filter-not-trait "outerloop=true". Additional targeted validation was run forAspire.Hosting.Azure.Tests.FoundryExtensionsTestsandAsHostedAgent_InPublishMode_AddsProjectReferenceToDeploymentTarget.Risk
Low. The change is localized to Foundry hosted-agent publish-mode reference placement and related tests; run-mode behavior and public API are unchanged.
Regression?
Unknown - no linked issue or explicit regression statement in the source PR.