Remove AspNetCore dependency in Npgsql EF Core component #427
Conversation
The Npgsql EF Core component currently adds the EF developer page in development environments. This means the Npgsql EF Core component is dependent on the ASP.NET Core shared framework, which brings more dependencies on it in other app models (ex. Worker apps). Removing this functionality because this dependency is not desirable and we don't have it in the SQL Server component. Fix #146
|
@davidfowl where are you on this right now? You said again today "all apps are web apps" due to them needing health checks endpoints. |
They don't need health checks endpoints. Specifically Worker apps can't have them since they don't have a You can configure health checks to run in a HostedService and periodically check health and log it. https://learn.microsoft.com/en-us/aspnet/core/host-and-deploy/health-checks?view=aspnetcore-7.0#health-check-publisher |
|
They need health checks endpoints if the environment only supports endpoints for probing though right? |
If they need to expose HTTP endpoints, then they aren't "Worker" apps anymore. |
I think this decoupling is fine. |
danmoseley
added
the
area-integrations
The Npgsql EF Core component currently adds the EF developer page in development environments. This means the Npgsql EF Core component is dependent on the ASP.NET Core shared framework, which brings more dependencies on it in other app models (ex. Worker apps).
Removing this functionality because this dependency is not desirable and we don't have it in the SQL Server component.
Fix #146