From c9689252989d6d3fa8c1d20be3c5e84f8f7d2ba0 Mon Sep 17 00:00:00 2001 From: Pedro Igor Date: Fri, 26 Aug 2022 09:23:39 -0300 Subject: [PATCH] Fix the provider id in the database migration example (#14038) Closes #14037 --- docs/guides/src/main/server/db.adoc | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/guides/src/main/server/db.adoc b/docs/guides/src/main/server/db.adoc index 97ee27144d..e936458393 100644 --- a/docs/guides/src/main/server/db.adoc +++ b/docs/guides/src/main/server/db.adoc @@ -141,16 +141,16 @@ Keycloak automatically chooses the appropriate JDBC driver for your vendor. To setup the JPA migrationStrategy (manual/update/validate) you should setup JPA provider as follows: .Setting the `migration-strategy` for the `quarkus` provider of the `connections-jpa` SPI -<@kc.start parameters="--spi-connections-jpa-quarkus-migration-strategy=manual"/> +<@kc.start parameters="--spi-connections-jpa-legacy-migration-strategy=manual"/> If you want to get a SQL file for DB initialization, too, you have to add this additional SPI initializeEmpty (true/false): .Setting the `initialize-empty` for the `quarkus` provider of the `connections-jpa` SPI -<@kc.start parameters="--spi-connections-jpa-quarkus-initialize-empty=false"/> +<@kc.start parameters="--spi-connections-jpa-legacy-initialize-empty=false"/> In the same way the migrationExport to point to a specific file and location: .Setting the `migration-export` for the `quarkus` provider of the `connections-jpa` SPI -<@kc.start parameters="--spi-connections-jpa-quarkus-migration-export=/"/> +<@kc.start parameters="--spi-connections-jpa-legacy-migration-export=/"/>