Tighten WithOrigin generic constraint for Front Door

[eerhardt]

Update WithOrigin to require T : IComputeResource, IResourceWithEndpoints, making the constraint more restrictive. WithOrigin needs to accept an IComputeResource that has endpoints.

[github-actions]

🚀 Dogfood this PR with:

⚠️ WARNING: Do not do this without first carefully reviewing the code of this PR to satisfy yourself it is safe.

curl -fsSL https://raw.githubusercontent.com/microsoft/aspire/main/eng/scripts/get-aspire-cli-pr.sh | bash -s -- 16409

Or

• Run remotely in PowerShell:

iex "& { $(irm https://raw.githubusercontent.com/microsoft/aspire/main/eng/scripts/get-aspire-cli-pr.ps1) } 16409"

[Copilot]

Pull request overview

This PR tightens the generic constraint on AzureFrontDoorExtensions.WithOrigin<T> to ensure origins are compute resources that also expose endpoints, aligning the API contract with Front Door’s requirement to resolve an origin host address from a compute environment.

Changes:

• Updated WithOrigin<T> to require T : IComputeResource, IResourceWithEndpoints.
• Adjusted the null-argument unit test to use a type (ProjectResource) that satisfies the new constraint.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.

File	Description
tests/Aspire.Hosting.Azure.Tests/AzureFrontDoorTests.cs	Updates the null-argument test to compile with the tightened WithOrigin<T> constraint.
src/Aspire.Hosting.Azure.FrontDoor/AzureFrontDoorExtensions.cs	Tightens WithOrigin<T>’s generic constraint to require compute resources with endpoints.

[Copilot]

The new generic constraint requires T to be an IComputeResource as well as IResourceWithEndpoints, but the XML docs above still describe T only as a resource with endpoints. Please update the <typeparam name="T"> documentation to reflect that T must be a compute resource with endpoints (to avoid confusing API consumers).

[eerhardt]

@copilot apply changes based on this feedback

[github-actions]

Re-running the failed jobs in the CI workflow for this pull request because 1 job was identified as retry-safe transient failures in the CI run attempt.
GitHub was asked to rerun all failed jobs for that attempt, and the rerun is being tracked in the rerun attempt.
The job links below point to the failed attempt jobs that matched the retry-safe transient failure rules.

• Tests / Templates-NUnit_NewUpAndBuildSupportProjectTemplatesTests / Templates-NUnit_NewUpAndBuildSupportProjectTemplatesTests (windows-latest) - Failed step 'Install sdk for nuget based testing' will be retried because the job log shows a likely transient infrastructure network failure. Matched pattern: /builds\.dotnet\.microsoft\.com.{0,160}(timed out|failed to connect|could not resolve|ENOTFOUND|ECONNRESET|EPROTO|Bad Gateway|SSL connection could not be established)/i.