Closed
Description
Description
Hi there,
Would it be possible / an okay idea to not require a default datasource definition if multi-tenancy / programmatic datasource configuration is used? I'm not sure how at all this would be implemented, but from a developer experience point-of-view, this would be nice. No having to define extra non-used properties in application.properties just to avoid errors when the application tries to start.
Implementation ideas
Perhaps a sort of escape hatch, where if an implementation of TenantConnectionResolver is detected in the CDI container, a message is logged letting the developer know that they are now on their own for validating their configuration and that quarkus will not check to make sure a datasource is configured before starting.