-
Notifications
You must be signed in to change notification settings - Fork 989
Move Ingress and Gateway extensions to Aspire.Hosting namespace #16588
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
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -2,8 +2,9 @@ | |
| // The .NET Foundation licenses this file to you under the MIT license. | ||
|
|
||
| using Aspire.Hosting.ApplicationModel; | ||
| using Aspire.Hosting.Kubernetes; | ||
|
|
||
| namespace Aspire.Hosting.Kubernetes; | ||
| namespace Aspire.Hosting; | ||
|
Comment on lines
4
to
+7
|
||
|
|
||
| /// <summary> | ||
| /// Provides extension methods for configuring Kubernetes Ingress resources in the Aspire application model. | ||
|
|
||
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.
This namespace move changes the public API surface. The generated API baseline file (src/Aspire.Hosting.Kubernetes/api/Aspire.Hosting.Kubernetes.cs) should be regenerated/updated so it reflects KubernetesGatewayExtensions under the new Aspire.Hosting namespace (and doesn’t continue to omit these APIs), otherwise API review artifacts and baseline checks will be inaccurate.