Replies: 1 comment
-
|
It was a pain to get it working, but now it works. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
While JPA configuration for migrationStrategy in Wildfly is clear, how to configure this step in Quarkus based KC?
There is no official configuration at https://www.keycloak.org/server/all-config
There is some support in code
QuarkusJpaConnectionProviderFactory.java#L172, but I'm too blind to use/configure it?!?
I'm using Keycloak 17.0.1
Update 1:
Comming from Wildfly CLI configuration to configure connectionsJpa:
I would expect, according to Configuring providers in Quarkus
spi-<spi-id>-<provider-id>-<property>=<value>to setup the JPA spi in that way:
bin/kc.sh start --spi-connectionsJpa-default-migrationStrategy=manualUpdate 2:
Ok, in meantime I found the issue #10871 comment to use quarkus as provider
I was not that far away with my spi config 😃
but using
--spi-connections-jpa-quarkus-migration-strategy=manualstill does not work as expected.I have an empty DB schema and want to have a SQL file genertated instead of automatically DB table creation.
final Update:
Based on default value for initializeEmpty:
boolean initializeEmpty = config.getBoolean("initializeEmpty", true);, finally I just missed that additional spi config:--spi-connections-jpa-quarkus-initialize-empty=falseBeta Was this translation helpful? Give feedback.
All reactions