You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
During build time, I generate the OpenAPI spec by setting <OpenApiGenerateDocumentsOnBuild>true</OpenApiGenerateDocumentsOnBuild> in the Wolverine API project, which runs dotnet-getdocument to generate the spec.
It all works fine in VS 2022, when the Postgres Docker container is up and running. But building in CI environments and the like, I get a DB connection error, because no Postgres DB exists.
Describe the solution you'd like
It would be nice to be able to bootstrap Wolverine it requiring a working DB connection.
Maybe a IServiceCollection extension similar to .DisableAllExternalWolverineTransports()?
Host=await AlbaHost.For<Program>(builder =>{ builder.ConfigureServices(services =>{// Override the Wolverine configuration to disable external DB connectivity services.DisableAllExternalDatabaseConnections();});});
Describe alternatives you've considered
For CI build steps it is of course possible to add a Posgres container.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
During build time, I generate the OpenAPI spec by setting
<OpenApiGenerateDocumentsOnBuild>true</OpenApiGenerateDocumentsOnBuild>
in the Wolverine API project, which runsdotnet-getdocument
to generate the spec.It all works fine in VS 2022, when the Postgres Docker container is up and running. But building in CI environments and the like, I get a DB connection error, because no Postgres DB exists.
Describe the solution you'd like
It would be nice to be able to bootstrap Wolverine it requiring a working DB connection.
Maybe a
IServiceCollection
extension similar to.DisableAllExternalWolverineTransports()
?Describe alternatives you've considered
For CI build steps it is of course possible to add a Posgres container.
The text was updated successfully, but these errors were encountered: