-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
Remove unconfigured datasource #36687
Conversation
Thanks for your pull request! The title of your pull request does not follow our editorial rules. Could you have a look?
This message is automatically generated by a bot. |
So I manually dispatched the build but it skipped everything. Don't know why. And my laptop is dying so I can't build all quarkus ;) |
The workflow ignores the |
So I had to amend hibernate extension that had to explicitely take care of UnconfiguredDataSource. |
Yes indeed I did spoke to quickly. Fixing all this and now correcting the real errors which are for the moment, extension that needed to explicitly handle unconfigured datasources as error cases... |
Maybe we should list those and discuss this more widely before you spend too much time on it, as we're not sure yet this is the right approach... please ping me when you get a full build listing all errors. |
Looking at the tests, I realized that this removal of UnconfiguredDatasource is hitting a few problems because "deactivating" datasources is sometimes necessary, but the only way we provide to do this is implicit, by not providing connection info. I'll try to implement a way to explicitly "deactivate" a datasource through a configuration property as discussed on quarkus-dev, and will send a PR. We'll see where this leads us. Thanks for the initial investigation @jtama! |
See also #37265 |
Fixes #36666