[release/13.3] Move Ingress and Gateway extensions to Aspire.Hosting namespace#16633
Conversation
KubernetesGatewayExtensions and KubernetesIngressExtensions were in the Aspire.Hosting.Kubernetes namespace, requiring users to add an explicit using directive. Move them to Aspire.Hosting to match the convention used by other extension methods like KubernetesEnvironmentExtensions and KubernetesServiceExtensions. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
|
🚀 Dogfood this PR with:
curl -fsSL https://raw.githubusercontent.com/microsoft/aspire/main/eng/scripts/get-aspire-cli-pr.sh | bash -s -- 16633Or
iex "& { $(irm https://raw.githubusercontent.com/microsoft/aspire/main/eng/scripts/get-aspire-cli-pr.ps1) } 16633" |
|
🎬 CLI E2E Test Recordings — 66 recordings uploaded (commit View all recordings
📹 Recordings uploaded automatically from CI run #25196949581 |
|
All failures are unrelated. Merging. |
|
No documentation PR is required for this change. This PR moves
|
Backport of #16588 to release/13.3
/cc @mitchdenny
Customer Impact
Current code breaks our normal extension method pattern. This PR fixes it and avoids a breaking change in the future.
Testing
Risk
Regression?