Back to Guides

By Version

Edit this Page

Using Flyway

Flyway is a popular database migration tool that is commonly used in JVM environments.

Quarkus provides first class support for using Flyway as will be explained in this guide.

Setting up support for Flyway

As shown in the Developing with Flyway section, to start using Flyway with your project, you just need to:

add your migrations to the src/main/resources/db/migration folder as you usually do with Flyway
activate the migrate-at-start option to migrate the schema automatically or inject the Flyway object and run your migration as you normally do

In your build file, add the following dependencies:

the Flyway extension
your JDBC driver extension (quarkus-jdbc-postgresql, quarkus-jdbc-h2, quarkus-jdbc-mariadb, …)
unless you’re using in-memory or file databases (such as H2 or SQLite), you need to add a flyway module dependency corresponding to the database you’re using. (for more details)

pom.xml

<!-- Flyway specific dependencies -->
<dependency>
    <groupId>io.quarkus</groupId>
    <artifactId>quarkus-flyway</artifactId>
</dependency>

<!-- JDBC driver dependencies -->
<dependency>
    <groupId>io.quarkus</groupId>
    <artifactId>quarkus-jdbc-postgresql</artifactId>
</dependency>

<!-- Flyway SQL Server specific dependencies -->
<dependency>
    <groupId>org.flywaydb</groupId>
    <artifactId>flyway-sqlserver</artifactId>
</dependency>

<!-- Flyway MariaDB/MySQL specific dependencies -->
<dependency>
    <groupId>org.flywaydb</groupId>
    <artifactId>flyway-mysql</artifactId>
</dependency>

<!-- Flyway Oracle specific dependencies -->
<dependency>
    <groupId>org.flywaydb</groupId>
    <artifactId>flyway-database-oracle</artifactId>
</dependency>

<!-- Flyway PostgreSQL specific dependencies -->
<dependency>
    <groupId>org.flywaydb</groupId>
    <artifactId>flyway-database-postgresql</artifactId>
</dependency>

<!-- Flyway DB2 specific dependencies -->
<dependency>
    <groupId>org.flywaydb</groupId>
    <artifactId>flyway-database-db2</artifactId>
</dependency>

<!-- Derby specific dependencies -->
<dependency>
    <groupId>org.flywaydb</groupId>
    <artifactId>flyway-database-derby</artifactId>
</dependency>

<!-- HSQLDB specific dependencies -->
<dependency>
    <groupId>org.flywaydb</groupId>
    <artifactId>flyway-database-hsqldb</artifactId>
</dependency>

<!-- Informix specific dependencies -->
<dependency>
    <groupId>org.flywaydb</groupId>
    <artifactId>flyway-database-informix</artifactId>
</dependency>

<!-- Redshift specific dependencies -->
<dependency>
    <groupId>org.flywaydb</groupId>
    <artifactId>flyway-database-redshift</artifactId>
</dependency>

<!-- Saphana specific dependencies -->
<dependency>
    <groupId>org.flywaydb</groupId>
    <artifactId>flyway-database-saphana</artifactId>
</dependency>

<!-- Snowflake specific dependencies -->
<dependency>
    <groupId>org.flywaydb</groupId>
    <artifactId>flyway-database-snowflake</artifactId>
</dependency>

<!-- Sybasease specific dependencies -->
<dependency>
    <groupId>org.flywaydb</groupId>
    <artifactId>flyway-database-sybasease</artifactId>
</dependency>

<!-- Firebird specific dependencies -->
<dependency>
    <groupId>org.flywaydb</groupId>
    <artifactId>flyway-firebird</artifactId>
</dependency>

<!-- BigQuery specific dependencies -->
<dependency>
    <groupId>org.flywaydb</groupId>
    <artifactId>flyway-gcp-bigquery</artifactId>
</dependency>

<!-- Spanner specific dependencies -->
<dependency>
    <groupId>org.flywaydb</groupId>
    <artifactId>flyway-gcp-spanner</artifactId>
</dependency>

<!-- Singlestore specific dependencies -->
<dependency>
    <groupId>org.flywaydb</groupId>
    <artifactId>flyway-singlestore</artifactId>
</dependency>

build.gradle

// Flyway specific dependencies
implementation("io.quarkus:quarkus-flyway")
// JDBC driver dependencies
implementation("io.quarkus:quarkus-jdbc-postgresql")
// Flyway SQL Server specific dependencies
implementation("org.flywaydb:flyway-sqlserver")
// Flyway MariaDB/MySQL specific dependencies
implementation("org.flywaydb:flyway-mysql")
// Flyway Oracle specific dependencies
implementation("org.flywaydb:flyway-database-oracle")
// Flyway PostgreSQL specific dependencies
implementation("org.flywaydb:flyway-database-postgresql")
// Flyway DB2 specific dependencies
implementation("org.flywaydb:flyway-database-db2")
// Flyway Derby specific dependencies
implementation("org.flywaydb:flyway-database-derby")
// HSQLDB specific dependencies
implementation("org.flywaydb:flyway-database-hsqldb")
// Informix specific dependencies
implementation("org.flywaydb:flyway-database-informix")
// Redshift specific dependencies
implementation("org.flywaydb:flyway-database-redshift")
// Saphana specific dependencies
implementation("org.flywaydb:flyway-database-saphana")
// Snowflake specific dependencies
implementation("org.flywaydb:flyway-database-snowflake")
// Sybasease specific dependencies
implementation("org.flywaydb:flyway-database-sybasease")
// Firebird specific dependencies
implementation("org.flywaydb:flyway-firebird")
// BigQuery specific dependencies
implementation("org.flywaydb:flyway-gcp-bigquery")
// Spanner specific dependencies
implementation("org.flywaydb:flyway-gcp-spanner")
// Singlestore specific dependencies
implementation("org.flywaydb:flyway-singlestore:10.15.0")

Flyway support relies on the Quarkus datasource config. It can be customized for the default datasource as well as for every named datasource. First, you need to add the datasource config to the application.properties file in order to allow Flyway to manage the schema. Also, you can customize the Flyway behaviour by using the following properties:

Configuration property fixed at build time - All other configuration properties are overridable at runtime

Configuration property	Type	Default
`quarkus.flyway.enabled` Whether Flyway is enabled during the build. If Flyway is disabled, the Flyway beans won’t be created and Flyway won’t be usable. Environment variable: `QUARKUS_FLYWAY_ENABLED` Show more	boolean	`true`
`quarkus.flyway.locations` Comma-separated list of locations to scan recursively for migrations. The location type is determined by its prefix. Unprefixed locations or locations starting with classpath: point to a package on the classpath and may contain both SQL and Java-based migrations. Locations starting with filesystem: point to a directory on the filesystem, may only contain SQL migrations and are only scanned recursively down non-hidden directories. Environment variable: `QUARKUS_FLYWAY_LOCATIONS` Show more	list of string	`db/migration`
`quarkus.flyway.callbacks` Comma-separated list of fully qualified class names of Callback implementations to use to hook into the Flyway lifecycle. The `org.flywaydb.core.api.callback.Callback` subclass must have a no-args constructor and must not be abstract. These classes must also not have any fields that hold state (unless that state is initialized in the constructor). Environment variable: `QUARKUS_FLYWAY_CALLBACKS` Show more	list of string
`quarkus.flyway.active` Flag to activate/deactivate Flyway for a specific datasource at runtime. Environment variable: `QUARKUS_FLYWAY_ACTIVE` Show more	boolean	`'true' if the datasource is active; 'false' otherwise`
`quarkus.flyway.connect-retries` The maximum number of retries when attempting to connect to the database. After each failed attempt, Flyway will wait up to the configured `connect-retries-interval` duration before attempting to connect again, up to the maximum number of times specified by connectRetries. Environment variable: `QUARKUS_FLYWAY_CONNECT_RETRIES` Show more	int
`quarkus.flyway.connect-retries-interval` The maximum time between retries when attempting to connect to the database. This will cap the interval between connect retries to the value provided. Environment variable: `QUARKUS_FLYWAY_CONNECT_RETRIES_INTERVAL` Show more	Duration	`120 seconds`
`quarkus.flyway.default-schema` Sets the default schema managed by Flyway. This schema name is case-sensitive. If not specified, but schemas is, Flyway uses the first schema in that list. If that is also not specified, Flyway uses the default schema for the database connection. Consequences: This schema will be the one containing the schema history table. This schema will be the default for the database connection (provided the database supports this concept). Environment variable: `QUARKUS_FLYWAY_DEFAULT_SCHEMA` Show more	string
`quarkus.flyway.jdbc-url` The JDBC URL that Flyway uses to connect to the database. Falls back to the datasource URL if not specified. Environment variable: `QUARKUS_FLYWAY_JDBC_URL` Show more	string
`quarkus.flyway.username` The username that Flyway uses to connect to the database. If no specific JDBC URL is configured, falls back to the datasource username if not specified. Environment variable: `QUARKUS_FLYWAY_USERNAME` Show more	string
`quarkus.flyway.password` The password that Flyway uses to connect to the database. If no specific JDBC URL is configured, falls back to the datasource password if not specified. Environment variable: `QUARKUS_FLYWAY_PASSWORD` Show more	string
`quarkus.flyway.schemas` Comma-separated case-sensitive list of schemas managed by Flyway. The first schema in the list will be automatically set as the default one during the migration. It will also be the one containing the schema history table. Environment variable: `QUARKUS_FLYWAY_SCHEMAS` Show more	list of string
`quarkus.flyway.table` The name of Flyway’s schema history table. By default (single-schema mode), the schema history table is placed in the default schema for the connection provided by the datasource. When the flyway.schemas property is set (multi-schema mode), the schema history table is placed in the first schema of the list. Environment variable: `QUARKUS_FLYWAY_TABLE` Show more	string
`quarkus.flyway.sql-migration-prefix` The file name prefix for versioned SQL migrations. Versioned SQL migrations have the following file name structure: prefixVERSIONseparatorDESCRIPTIONsuffix , which using the defaults translates to V1.1__My_description.sql Environment variable: `QUARKUS_FLYWAY_SQL_MIGRATION_PREFIX` Show more	string
`quarkus.flyway.repeatable-sql-migration-prefix` The file name prefix for repeatable SQL migrations. Repeatable SQL migrations have the following file name structure: prefixSeparatorDESCRIPTIONsuffix , which using the defaults translates to R__My_description.sql Environment variable: `QUARKUS_FLYWAY_REPEATABLE_SQL_MIGRATION_PREFIX` Show more	string
`quarkus.flyway.clean-at-start` true to execute Flyway clean command automatically when the application starts, false otherwise. Environment variable: `QUARKUS_FLYWAY_CLEAN_AT_START` Show more	boolean	`false`
`quarkus.flyway.clean-disabled` true to prevent Flyway clean operations, false otherwise. Environment variable: `QUARKUS_FLYWAY_CLEAN_DISABLED` Show more	boolean	`false`
`quarkus.flyway.clean-on-validation-error` true to automatically call clean when a validation error occurs, false otherwise. Environment variable: `QUARKUS_FLYWAY_CLEAN_ON_VALIDATION_ERROR` Show more	boolean	`false`
`quarkus.flyway.migrate-at-start` true to execute Flyway automatically when the application starts, false otherwise. Environment variable: `QUARKUS_FLYWAY_MIGRATE_AT_START` Show more	boolean	`false`
`quarkus.flyway.repair-at-start` true to execute a Flyway repair command when the application starts, false otherwise. Environment variable: `QUARKUS_FLYWAY_REPAIR_AT_START` Show more	boolean	`false`
`quarkus.flyway.validate-at-start` true to execute a Flyway validate command when the application starts, false otherwise. Environment variable: `QUARKUS_FLYWAY_VALIDATE_AT_START` Show more	boolean	`false`
`quarkus.flyway.baseline-on-migrate` true to execute Flyway baseline before migrations This flag is ignored if the flyway_schema_history table exists in the current schema or if the current schema is empty. Note that this will not automatically call migrate, you must either enable baselineAtStart or programmatically call flyway.migrate(). Environment variable: `QUARKUS_FLYWAY_BASELINE_ON_MIGRATE` Show more	boolean	`false`
`quarkus.flyway.baseline-at-start` true to execute Flyway baseline automatically when the application starts. This flag is ignored if the flyway_schema_history table exists in the current schema. This will work even if the current schema is empty. Environment variable: `QUARKUS_FLYWAY_BASELINE_AT_START` Show more	boolean	`false`
`quarkus.flyway.baseline-version` The initial baseline version. Environment variable: `QUARKUS_FLYWAY_BASELINE_VERSION` Show more	string
`quarkus.flyway.baseline-description` The description to tag an existing schema with when executing baseline. Environment variable: `QUARKUS_FLYWAY_BASELINE_DESCRIPTION` Show more	string
`quarkus.flyway.validate-on-migrate` Whether to automatically call validate when performing a migration. Environment variable: `QUARKUS_FLYWAY_VALIDATE_ON_MIGRATE` Show more	boolean	`true`
`quarkus.flyway.out-of-order` Allows migrations to be run "out of order". Environment variable: `QUARKUS_FLYWAY_OUT_OF_ORDER` Show more	boolean	`false`
`quarkus.flyway.ignore-missing-migrations` Ignore missing migrations when reading the history table. When set to true migrations from older versions present in the history table but absent in the configured locations will be ignored (and logged as a warning), when false (the default) the validation step will fail. Environment variable: `QUARKUS_FLYWAY_IGNORE_MISSING_MIGRATIONS` Show more	boolean	`false`
`quarkus.flyway.ignore-future-migrations` Ignore future migrations when reading the history table. When set to true migrations from newer versions present in the history table but absent in the configured locations will be ignored (and logged as a warning), when false (the default) the validation step will fail. Environment variable: `QUARKUS_FLYWAY_IGNORE_FUTURE_MIGRATIONS` Show more	boolean	`false`
`quarkus.flyway.placeholders."placeholder-key"` Sets the placeholders to replace in SQL migration scripts. Environment variable: `QUARKUS_FLYWAY_PLACEHOLDERS__PLACEHOLDER_KEY_` Show more	Map<String,String>
`quarkus.flyway.create-schemas` Whether Flyway should attempt to create the schemas specified in the schemas property Environment variable: `QUARKUS_FLYWAY_CREATE_SCHEMAS` Show more	boolean	`true`
`quarkus.flyway.placeholder-prefix` Prefix of every placeholder (default: ${ ) Environment variable: `QUARKUS_FLYWAY_PLACEHOLDER_PREFIX` Show more	string
`quarkus.flyway.placeholder-suffix` Suffix of every placeholder (default: } ) Environment variable: `QUARKUS_FLYWAY_PLACEHOLDER_SUFFIX` Show more	string
`quarkus.flyway.init-sql` The SQL statements to run to initialize a new database connection immediately after opening it. Environment variable: `QUARKUS_FLYWAY_INIT_SQL` Show more	string
`quarkus.flyway.validate-migration-naming` Whether to validate migrations and callbacks whose scripts do not obey the correct naming convention. A failure can be useful to check that errors such as case sensitivity in migration prefixes have been corrected. Environment variable: `QUARKUS_FLYWAY_VALIDATE_MIGRATION_NAMING` Show more	boolean	`false`
`quarkus.flyway.ignore-migration-patterns` Ignore migrations during validate and repair according to a given list of patterns (see https://flywaydb.org/documentation/configuration/parameters/ignoreMigrationPatterns for more information). When this configuration is set, the ignoreFutureMigrations and ignoreMissingMigrations settings are ignored. Patterns are comma separated. Environment variable: `QUARKUS_FLYWAY_IGNORE_MIGRATION_PATTERNS` Show more	list of string
Named datasources	Type	Default
`quarkus.flyway."datasource-name".locations` Comma-separated list of locations to scan recursively for migrations. The location type is determined by its prefix. Unprefixed locations or locations starting with classpath: point to a package on the classpath and may contain both SQL and Java-based migrations. Locations starting with filesystem: point to a directory on the filesystem, may only contain SQL migrations and are only scanned recursively down non-hidden directories. Environment variable: `QUARKUS_FLYWAY__DATASOURCE_NAME__LOCATIONS` Show more	list of string	`db/migration`
`quarkus.flyway."datasource-name".callbacks` Comma-separated list of fully qualified class names of Callback implementations to use to hook into the Flyway lifecycle. The `org.flywaydb.core.api.callback.Callback` subclass must have a no-args constructor and must not be abstract. These classes must also not have any fields that hold state (unless that state is initialized in the constructor). Environment variable: `QUARKUS_FLYWAY__DATASOURCE_NAME__CALLBACKS` Show more	list of string
`quarkus.flyway."datasource-name".active` Flag to activate/deactivate Flyway for a specific datasource at runtime. Environment variable: `QUARKUS_FLYWAY__DATASOURCE_NAME__ACTIVE` Show more	boolean	`'true' if the datasource is active; 'false' otherwise`
`quarkus.flyway."datasource-name".connect-retries` The maximum number of retries when attempting to connect to the database. After each failed attempt, Flyway will wait up to the configured `connect-retries-interval` duration before attempting to connect again, up to the maximum number of times specified by connectRetries. Environment variable: `QUARKUS_FLYWAY__DATASOURCE_NAME__CONNECT_RETRIES` Show more	int
`quarkus.flyway."datasource-name".connect-retries-interval` The maximum time between retries when attempting to connect to the database. This will cap the interval between connect retries to the value provided. Environment variable: `QUARKUS_FLYWAY__DATASOURCE_NAME__CONNECT_RETRIES_INTERVAL` Show more	Duration	`120 seconds`
`quarkus.flyway."datasource-name".default-schema` Sets the default schema managed by Flyway. This schema name is case-sensitive. If not specified, but schemas is, Flyway uses the first schema in that list. If that is also not specified, Flyway uses the default schema for the database connection. Consequences: This schema will be the one containing the schema history table. This schema will be the default for the database connection (provided the database supports this concept). Environment variable: `QUARKUS_FLYWAY__DATASOURCE_NAME__DEFAULT_SCHEMA` Show more	string
`quarkus.flyway."datasource-name".jdbc-url` The JDBC URL that Flyway uses to connect to the database. Falls back to the datasource URL if not specified. Environment variable: `QUARKUS_FLYWAY__DATASOURCE_NAME__JDBC_URL` Show more	string
`quarkus.flyway."datasource-name".username` The username that Flyway uses to connect to the database. If no specific JDBC URL is configured, falls back to the datasource username if not specified. Environment variable: `QUARKUS_FLYWAY__DATASOURCE_NAME__USERNAME` Show more	string
`quarkus.flyway."datasource-name".password` The password that Flyway uses to connect to the database. If no specific JDBC URL is configured, falls back to the datasource password if not specified. Environment variable: `QUARKUS_FLYWAY__DATASOURCE_NAME__PASSWORD` Show more	string
`quarkus.flyway."datasource-name".schemas` Comma-separated case-sensitive list of schemas managed by Flyway. The first schema in the list will be automatically set as the default one during the migration. It will also be the one containing the schema history table. Environment variable: `QUARKUS_FLYWAY__DATASOURCE_NAME__SCHEMAS` Show more	list of string
`quarkus.flyway."datasource-name".table` The name of Flyway’s schema history table. By default (single-schema mode), the schema history table is placed in the default schema for the connection provided by the datasource. When the flyway.schemas property is set (multi-schema mode), the schema history table is placed in the first schema of the list. Environment variable: `QUARKUS_FLYWAY__DATASOURCE_NAME__TABLE` Show more	string
`quarkus.flyway."datasource-name".sql-migration-prefix` The file name prefix for versioned SQL migrations. Versioned SQL migrations have the following file name structure: prefixVERSIONseparatorDESCRIPTIONsuffix , which using the defaults translates to V1.1__My_description.sql Environment variable: `QUARKUS_FLYWAY__DATASOURCE_NAME__SQL_MIGRATION_PREFIX` Show more	string
`quarkus.flyway."datasource-name".repeatable-sql-migration-prefix` The file name prefix for repeatable SQL migrations. Repeatable SQL migrations have the following file name structure: prefixSeparatorDESCRIPTIONsuffix , which using the defaults translates to R__My_description.sql Environment variable: `QUARKUS_FLYWAY__DATASOURCE_NAME__REPEATABLE_SQL_MIGRATION_PREFIX` Show more	string
`quarkus.flyway."datasource-name".clean-at-start` true to execute Flyway clean command automatically when the application starts, false otherwise. Environment variable: `QUARKUS_FLYWAY__DATASOURCE_NAME__CLEAN_AT_START` Show more	boolean	`false`
`quarkus.flyway."datasource-name".clean-disabled` true to prevent Flyway clean operations, false otherwise. Environment variable: `QUARKUS_FLYWAY__DATASOURCE_NAME__CLEAN_DISABLED` Show more	boolean	`false`
`quarkus.flyway."datasource-name".clean-on-validation-error` true to automatically call clean when a validation error occurs, false otherwise. Environment variable: `QUARKUS_FLYWAY__DATASOURCE_NAME__CLEAN_ON_VALIDATION_ERROR` Show more	boolean	`false`
`quarkus.flyway."datasource-name".migrate-at-start` true to execute Flyway automatically when the application starts, false otherwise. Environment variable: `QUARKUS_FLYWAY__DATASOURCE_NAME__MIGRATE_AT_START` Show more	boolean	`false`
`quarkus.flyway."datasource-name".repair-at-start` true to execute a Flyway repair command when the application starts, false otherwise. Environment variable: `QUARKUS_FLYWAY__DATASOURCE_NAME__REPAIR_AT_START` Show more	boolean	`false`
`quarkus.flyway."datasource-name".validate-at-start` true to execute a Flyway validate command when the application starts, false otherwise. Environment variable: `QUARKUS_FLYWAY__DATASOURCE_NAME__VALIDATE_AT_START` Show more	boolean	`false`
`quarkus.flyway."datasource-name".baseline-on-migrate` true to execute Flyway baseline before migrations This flag is ignored if the flyway_schema_history table exists in the current schema or if the current schema is empty. Note that this will not automatically call migrate, you must either enable baselineAtStart or programmatically call flyway.migrate(). Environment variable: `QUARKUS_FLYWAY__DATASOURCE_NAME__BASELINE_ON_MIGRATE` Show more	boolean	`false`
`quarkus.flyway."datasource-name".baseline-at-start` true to execute Flyway baseline automatically when the application starts. This flag is ignored if the flyway_schema_history table exists in the current schema. This will work even if the current schema is empty. Environment variable: `QUARKUS_FLYWAY__DATASOURCE_NAME__BASELINE_AT_START` Show more	boolean	`false`
`quarkus.flyway."datasource-name".baseline-version` The initial baseline version. Environment variable: `QUARKUS_FLYWAY__DATASOURCE_NAME__BASELINE_VERSION` Show more	string
`quarkus.flyway."datasource-name".baseline-description` The description to tag an existing schema with when executing baseline. Environment variable: `QUARKUS_FLYWAY__DATASOURCE_NAME__BASELINE_DESCRIPTION` Show more	string
`quarkus.flyway."datasource-name".validate-on-migrate` Whether to automatically call validate when performing a migration. Environment variable: `QUARKUS_FLYWAY__DATASOURCE_NAME__VALIDATE_ON_MIGRATE` Show more	boolean	`true`
`quarkus.flyway."datasource-name".out-of-order` Allows migrations to be run "out of order". Environment variable: `QUARKUS_FLYWAY__DATASOURCE_NAME__OUT_OF_ORDER` Show more	boolean	`false`
`quarkus.flyway."datasource-name".ignore-missing-migrations` Ignore missing migrations when reading the history table. When set to true migrations from older versions present in the history table but absent in the configured locations will be ignored (and logged as a warning), when false (the default) the validation step will fail. Environment variable: `QUARKUS_FLYWAY__DATASOURCE_NAME__IGNORE_MISSING_MIGRATIONS` Show more	boolean	`false`
`quarkus.flyway."datasource-name".ignore-future-migrations` Ignore future migrations when reading the history table. When set to true migrations from newer versions present in the history table but absent in the configured locations will be ignored (and logged as a warning), when false (the default) the validation step will fail. Environment variable: `QUARKUS_FLYWAY__DATASOURCE_NAME__IGNORE_FUTURE_MIGRATIONS` Show more	boolean	`false`
`quarkus.flyway."datasource-name".placeholders."placeholder-key"` Sets the placeholders to replace in SQL migration scripts. Environment variable: `QUARKUS_FLYWAY__DATASOURCE_NAME__PLACEHOLDERS__PLACEHOLDER_KEY_` Show more	Map<String,String>
`quarkus.flyway."datasource-name".create-schemas` Whether Flyway should attempt to create the schemas specified in the schemas property Environment variable: `QUARKUS_FLYWAY__DATASOURCE_NAME__CREATE_SCHEMAS` Show more	boolean	`true`
`quarkus.flyway."datasource-name".placeholder-prefix` Prefix of every placeholder (default: ${ ) Environment variable: `QUARKUS_FLYWAY__DATASOURCE_NAME__PLACEHOLDER_PREFIX` Show more	string
`quarkus.flyway."datasource-name".placeholder-suffix` Suffix of every placeholder (default: } ) Environment variable: `QUARKUS_FLYWAY__DATASOURCE_NAME__PLACEHOLDER_SUFFIX` Show more	string
`quarkus.flyway."datasource-name".init-sql` The SQL statements to run to initialize a new database connection immediately after opening it. Environment variable: `QUARKUS_FLYWAY__DATASOURCE_NAME__INIT_SQL` Show more	string
`quarkus.flyway."datasource-name".validate-migration-naming` Whether to validate migrations and callbacks whose scripts do not obey the correct naming convention. A failure can be useful to check that errors such as case sensitivity in migration prefixes have been corrected. Environment variable: `QUARKUS_FLYWAY__DATASOURCE_NAME__VALIDATE_MIGRATION_NAMING` Show more	boolean	`false`
`quarkus.flyway."datasource-name".ignore-migration-patterns` Ignore migrations during validate and repair according to a given list of patterns (see https://flywaydb.org/documentation/configuration/parameters/ignoreMigrationPatterns for more information). When this configuration is set, the ignoreFutureMigrations and ignoreMissingMigrations settings are ignored. Patterns are comma separated. Environment variable: `QUARKUS_FLYWAY__DATASOURCE_NAME__IGNORE_MIGRATION_PATTERNS` Show more	list of string

Configuration property

Type

Default

quarkus.flyway.enabled

Whether Flyway is enabled during the build.

If Flyway is disabled, the Flyway beans won’t be created and Flyway won’t be usable.

Environment variable: QUARKUS_FLYWAY_ENABLED

boolean

true

quarkus.flyway.locations

Comma-separated list of locations to scan recursively for migrations. The location type is determined by its prefix.

Unprefixed locations or locations starting with classpath: point to a package on the classpath and may contain both SQL and Java-based migrations.

Locations starting with filesystem: point to a directory on the filesystem, may only contain SQL migrations and are only scanned recursively down non-hidden directories.

Environment variable: QUARKUS_FLYWAY_LOCATIONS

list of string

db/migration

quarkus.flyway.callbacks

Comma-separated list of fully qualified class names of Callback implementations to use to hook into the Flyway lifecycle. The org.flywaydb.core.api.callback.Callback subclass must have a no-args constructor and must not be abstract. These classes must also not have any fields that hold state (unless that state is initialized in the constructor).

Environment variable: QUARKUS_FLYWAY_CALLBACKS

list of string

quarkus.flyway.active

Flag to activate/deactivate Flyway for a specific datasource at runtime.

Environment variable: QUARKUS_FLYWAY_ACTIVE

boolean

'true' if the datasource is active; 'false' otherwise

quarkus.flyway.connect-retries

The maximum number of retries when attempting to connect to the database.

After each failed attempt, Flyway will wait up to the configured connect-retries-interval duration before attempting to connect again, up to the maximum number of times specified by connectRetries.

Environment variable: QUARKUS_FLYWAY_CONNECT_RETRIES

int

quarkus.flyway.connect-retries-interval

The maximum time between retries when attempting to connect to the database.

This will cap the interval between connect retries to the value provided.

Environment variable: QUARKUS_FLYWAY_CONNECT_RETRIES_INTERVAL

Duration

120 seconds

quarkus.flyway.default-schema

Sets the default schema managed by Flyway. This schema name is case-sensitive. If not specified, but schemas is, Flyway uses the first schema in that list. If that is also not specified, Flyway uses the default schema for the database connection.

Consequences:

This schema will be the one containing the schema history table.
This schema will be the default for the database connection (provided the database supports this concept).

Environment variable: QUARKUS_FLYWAY_DEFAULT_SCHEMA

string

quarkus.flyway.jdbc-url

The JDBC URL that Flyway uses to connect to the database. Falls back to the datasource URL if not specified.

Environment variable: QUARKUS_FLYWAY_JDBC_URL

string

quarkus.flyway.username

The username that Flyway uses to connect to the database. If no specific JDBC URL is configured, falls back to the datasource username if not specified.

Environment variable: QUARKUS_FLYWAY_USERNAME

string

quarkus.flyway.password

The password that Flyway uses to connect to the database. If no specific JDBC URL is configured, falls back to the datasource password if not specified.

Environment variable: QUARKUS_FLYWAY_PASSWORD

string

quarkus.flyway.schemas

Comma-separated case-sensitive list of schemas managed by Flyway. The first schema in the list will be automatically set as the default one during the migration. It will also be the one containing the schema history table.

Environment variable: QUARKUS_FLYWAY_SCHEMAS

list of string

quarkus.flyway.table

The name of Flyway’s schema history table. By default (single-schema mode), the schema history table is placed in the default schema for the connection provided by the datasource. When the flyway.schemas property is set (multi-schema mode), the schema history table is placed in the first schema of the list.

Environment variable: QUARKUS_FLYWAY_TABLE

string

quarkus.flyway.sql-migration-prefix

The file name prefix for versioned SQL migrations. Versioned SQL migrations have the following file name structure: prefixVERSIONseparatorDESCRIPTIONsuffix , which using the defaults translates to V1.1__My_description.sql

Environment variable: QUARKUS_FLYWAY_SQL_MIGRATION_PREFIX

string

quarkus.flyway.repeatable-sql-migration-prefix

The file name prefix for repeatable SQL migrations. Repeatable SQL migrations have the following file name structure: prefixSeparatorDESCRIPTIONsuffix , which using the defaults translates to R__My_description.sql

Environment variable: QUARKUS_FLYWAY_REPEATABLE_SQL_MIGRATION_PREFIX

string

quarkus.flyway.clean-at-start

true to execute Flyway clean command automatically when the application starts, false otherwise.

Environment variable: QUARKUS_FLYWAY_CLEAN_AT_START

boolean

false

quarkus.flyway.clean-disabled

true to prevent Flyway clean operations, false otherwise.

Environment variable: QUARKUS_FLYWAY_CLEAN_DISABLED

boolean

false

quarkus.flyway.clean-on-validation-error

true to automatically call clean when a validation error occurs, false otherwise.

Environment variable: QUARKUS_FLYWAY_CLEAN_ON_VALIDATION_ERROR

boolean

false

quarkus.flyway.migrate-at-start

true to execute Flyway automatically when the application starts, false otherwise.

Environment variable: QUARKUS_FLYWAY_MIGRATE_AT_START

boolean

false

quarkus.flyway.repair-at-start

true to execute a Flyway repair command when the application starts, false otherwise.

Environment variable: QUARKUS_FLYWAY_REPAIR_AT_START

boolean

false

quarkus.flyway.validate-at-start

true to execute a Flyway validate command when the application starts, false otherwise.

Environment variable: QUARKUS_FLYWAY_VALIDATE_AT_START

boolean

false

quarkus.flyway.baseline-on-migrate

true to execute Flyway baseline before migrations This flag is ignored if the flyway_schema_history table exists in the current schema or if the current schema is empty. Note that this will not automatically call migrate, you must either enable baselineAtStart or programmatically call flyway.migrate().

Environment variable: QUARKUS_FLYWAY_BASELINE_ON_MIGRATE

boolean

false

quarkus.flyway.baseline-at-start

true to execute Flyway baseline automatically when the application starts. This flag is ignored if the flyway_schema_history table exists in the current schema. This will work even if the current schema is empty.

Environment variable: QUARKUS_FLYWAY_BASELINE_AT_START

boolean

false

quarkus.flyway.baseline-version

The initial baseline version.

Environment variable: QUARKUS_FLYWAY_BASELINE_VERSION

string

quarkus.flyway.baseline-description

The description to tag an existing schema with when executing baseline.

Environment variable: QUARKUS_FLYWAY_BASELINE_DESCRIPTION

string

quarkus.flyway.validate-on-migrate

Whether to automatically call validate when performing a migration.

Environment variable: QUARKUS_FLYWAY_VALIDATE_ON_MIGRATE

boolean

true

quarkus.flyway.out-of-order

Allows migrations to be run "out of order".

Environment variable: QUARKUS_FLYWAY_OUT_OF_ORDER

boolean

false

quarkus.flyway.ignore-missing-migrations

Ignore missing migrations when reading the history table. When set to true migrations from older versions present in the history table but absent in the configured locations will be ignored (and logged as a warning), when false (the default) the validation step will fail.

Environment variable: QUARKUS_FLYWAY_IGNORE_MISSING_MIGRATIONS

boolean

false

quarkus.flyway.ignore-future-migrations

Ignore future migrations when reading the history table. When set to true migrations from newer versions present in the history table but absent in the configured locations will be ignored (and logged as a warning), when false (the default) the validation step will fail.

Environment variable: QUARKUS_FLYWAY_IGNORE_FUTURE_MIGRATIONS

boolean

false

quarkus.flyway.placeholders."placeholder-key"

Sets the placeholders to replace in SQL migration scripts.

Environment variable: QUARKUS_FLYWAY_PLACEHOLDERS__PLACEHOLDER_KEY_

Map<String,String>

quarkus.flyway.create-schemas

Whether Flyway should attempt to create the schemas specified in the schemas property

Environment variable: QUARKUS_FLYWAY_CREATE_SCHEMAS

boolean

true

quarkus.flyway.placeholder-prefix

Prefix of every placeholder (default: ${ )

Environment variable: QUARKUS_FLYWAY_PLACEHOLDER_PREFIX

string

quarkus.flyway.placeholder-suffix

Suffix of every placeholder (default: } )

Environment variable: QUARKUS_FLYWAY_PLACEHOLDER_SUFFIX

string

quarkus.flyway.init-sql

The SQL statements to run to initialize a new database connection immediately after opening it.

Environment variable: QUARKUS_FLYWAY_INIT_SQL

string

quarkus.flyway.validate-migration-naming

Whether to validate migrations and callbacks whose scripts do not obey the correct naming convention. A failure can be useful to check that errors such as case sensitivity in migration prefixes have been corrected.

Environment variable: QUARKUS_FLYWAY_VALIDATE_MIGRATION_NAMING

boolean

false

quarkus.flyway.ignore-migration-patterns

Ignore migrations during validate and repair according to a given list of patterns (see https://flywaydb.org/documentation/configuration/parameters/ignoreMigrationPatterns for more information). When this configuration is set, the ignoreFutureMigrations and ignoreMissingMigrations settings are ignored. Patterns are comma separated.

Environment variable: QUARKUS_FLYWAY_IGNORE_MIGRATION_PATTERNS

list of string

Named datasources

Type

Default

quarkus.flyway."datasource-name".locations

Comma-separated list of locations to scan recursively for migrations. The location type is determined by its prefix.

Unprefixed locations or locations starting with classpath: point to a package on the classpath and may contain both SQL and Java-based migrations.

Locations starting with filesystem: point to a directory on the filesystem, may only contain SQL migrations and are only scanned recursively down non-hidden directories.

Environment variable: QUARKUS_FLYWAY__DATASOURCE_NAME__LOCATIONS

list of string

db/migration

quarkus.flyway."datasource-name".callbacks

Environment variable: QUARKUS_FLYWAY__DATASOURCE_NAME__CALLBACKS

list of string

quarkus.flyway."datasource-name".active

Flag to activate/deactivate Flyway for a specific datasource at runtime.

Environment variable: QUARKUS_FLYWAY__DATASOURCE_NAME__ACTIVE

boolean

'true' if the datasource is active; 'false' otherwise

quarkus.flyway."datasource-name".connect-retries

The maximum number of retries when attempting to connect to the database.

After each failed attempt, Flyway will wait up to the configured connect-retries-interval duration before attempting to connect again, up to the maximum number of times specified by connectRetries.

Environment variable: QUARKUS_FLYWAY__DATASOURCE_NAME__CONNECT_RETRIES

int

quarkus.flyway."datasource-name".connect-retries-interval

The maximum time between retries when attempting to connect to the database.

This will cap the interval between connect retries to the value provided.

Environment variable: QUARKUS_FLYWAY__DATASOURCE_NAME__CONNECT_RETRIES_INTERVAL

Duration

120 seconds

quarkus.flyway."datasource-name".default-schema

Consequences:

This schema will be the one containing the schema history table.
This schema will be the default for the database connection (provided the database supports this concept).

Environment variable: QUARKUS_FLYWAY__DATASOURCE_NAME__DEFAULT_SCHEMA

string

quarkus.flyway."datasource-name".jdbc-url

The JDBC URL that Flyway uses to connect to the database. Falls back to the datasource URL if not specified.

Environment variable: QUARKUS_FLYWAY__DATASOURCE_NAME__JDBC_URL

string

quarkus.flyway."datasource-name".username

The username that Flyway uses to connect to the database. If no specific JDBC URL is configured, falls back to the datasource username if not specified.

Environment variable: QUARKUS_FLYWAY__DATASOURCE_NAME__USERNAME

string

quarkus.flyway."datasource-name".password

The password that Flyway uses to connect to the database. If no specific JDBC URL is configured, falls back to the datasource password if not specified.

Environment variable: QUARKUS_FLYWAY__DATASOURCE_NAME__PASSWORD

string

quarkus.flyway."datasource-name".schemas

Environment variable: QUARKUS_FLYWAY__DATASOURCE_NAME__SCHEMAS

list of string

quarkus.flyway."datasource-name".table

Environment variable: QUARKUS_FLYWAY__DATASOURCE_NAME__TABLE

string

quarkus.flyway."datasource-name".sql-migration-prefix

Environment variable: QUARKUS_FLYWAY__DATASOURCE_NAME__SQL_MIGRATION_PREFIX

string

quarkus.flyway."datasource-name".repeatable-sql-migration-prefix

Environment variable: QUARKUS_FLYWAY__DATASOURCE_NAME__REPEATABLE_SQL_MIGRATION_PREFIX

string

quarkus.flyway."datasource-name".clean-at-start

true to execute Flyway clean command automatically when the application starts, false otherwise.

Environment variable: QUARKUS_FLYWAY__DATASOURCE_NAME__CLEAN_AT_START

boolean

false

quarkus.flyway."datasource-name".clean-disabled

true to prevent Flyway clean operations, false otherwise.

Environment variable: QUARKUS_FLYWAY__DATASOURCE_NAME__CLEAN_DISABLED

boolean

false

quarkus.flyway."datasource-name".clean-on-validation-error

true to automatically call clean when a validation error occurs, false otherwise.

Environment variable: QUARKUS_FLYWAY__DATASOURCE_NAME__CLEAN_ON_VALIDATION_ERROR

boolean

false

quarkus.flyway."datasource-name".migrate-at-start

true to execute Flyway automatically when the application starts, false otherwise.

Environment variable: QUARKUS_FLYWAY__DATASOURCE_NAME__MIGRATE_AT_START

boolean

false

quarkus.flyway."datasource-name".repair-at-start

true to execute a Flyway repair command when the application starts, false otherwise.

Environment variable: QUARKUS_FLYWAY__DATASOURCE_NAME__REPAIR_AT_START

boolean

false

quarkus.flyway."datasource-name".validate-at-start

true to execute a Flyway validate command when the application starts, false otherwise.

Environment variable: QUARKUS_FLYWAY__DATASOURCE_NAME__VALIDATE_AT_START

boolean

false

quarkus.flyway."datasource-name".baseline-on-migrate

Environment variable: QUARKUS_FLYWAY__DATASOURCE_NAME__BASELINE_ON_MIGRATE

boolean

false

quarkus.flyway."datasource-name".baseline-at-start

Environment variable: QUARKUS_FLYWAY__DATASOURCE_NAME__BASELINE_AT_START

boolean

false

quarkus.flyway."datasource-name".baseline-version

The initial baseline version.

Environment variable: QUARKUS_FLYWAY__DATASOURCE_NAME__BASELINE_VERSION

string

quarkus.flyway."datasource-name".baseline-description

The description to tag an existing schema with when executing baseline.

Environment variable: QUARKUS_FLYWAY__DATASOURCE_NAME__BASELINE_DESCRIPTION

string

quarkus.flyway."datasource-name".validate-on-migrate

Whether to automatically call validate when performing a migration.

Environment variable: QUARKUS_FLYWAY__DATASOURCE_NAME__VALIDATE_ON_MIGRATE

boolean

true

quarkus.flyway."datasource-name".out-of-order

Allows migrations to be run "out of order".

Environment variable: QUARKUS_FLYWAY__DATASOURCE_NAME__OUT_OF_ORDER

boolean

false

quarkus.flyway."datasource-name".ignore-missing-migrations

Environment variable: QUARKUS_FLYWAY__DATASOURCE_NAME__IGNORE_MISSING_MIGRATIONS

boolean

false

quarkus.flyway."datasource-name".ignore-future-migrations

Environment variable: QUARKUS_FLYWAY__DATASOURCE_NAME__IGNORE_FUTURE_MIGRATIONS

boolean

false

quarkus.flyway."datasource-name".placeholders."placeholder-key"

Sets the placeholders to replace in SQL migration scripts.

Environment variable: QUARKUS_FLYWAY__DATASOURCE_NAME__PLACEHOLDERS__PLACEHOLDER_KEY_

Map<String,String>

quarkus.flyway."datasource-name".create-schemas

Whether Flyway should attempt to create the schemas specified in the schemas property

Environment variable: QUARKUS_FLYWAY__DATASOURCE_NAME__CREATE_SCHEMAS

boolean

true

quarkus.flyway."datasource-name".placeholder-prefix

Prefix of every placeholder (default: ${ )

Environment variable: QUARKUS_FLYWAY__DATASOURCE_NAME__PLACEHOLDER_PREFIX

string

quarkus.flyway."datasource-name".placeholder-suffix

Suffix of every placeholder (default: } )

Environment variable: QUARKUS_FLYWAY__DATASOURCE_NAME__PLACEHOLDER_SUFFIX

string

quarkus.flyway."datasource-name".init-sql

The SQL statements to run to initialize a new database connection immediately after opening it.

Environment variable: QUARKUS_FLYWAY__DATASOURCE_NAME__INIT_SQL

string

quarkus.flyway."datasource-name".validate-migration-naming

Environment variable: QUARKUS_FLYWAY__DATASOURCE_NAME__VALIDATE_MIGRATION_NAMING

boolean

false

quarkus.flyway."datasource-name".ignore-migration-patterns

Environment variable: QUARKUS_FLYWAY__DATASOURCE_NAME__IGNORE_MIGRATION_PATTERNS

list of string

About the Duration format

To write duration values, use the standard java.time.Duration format. See the Duration#parse() Java API documentation for more information.

You can also use a simplified format, starting with a number:

If the value is only a number, it represents time in seconds.
If the value is a number followed by ms, it represents time in milliseconds.

In other cases, the simplified format is translated to the java.time.Duration format for parsing:

If the value is a number followed by h, m, or s, it is prefixed with PT.
If the value is a number followed by d, it is prefixed with P.

Developing with Flyway

The following is an example for the application.properties file:

# configure your datasource
quarkus.datasource.db-kind=postgresql
quarkus.datasource.username=sarah
quarkus.datasource.password=connor
quarkus.datasource.jdbc.url=jdbc:postgresql://localhost:5432/mydatabase

# Run Flyway migrations automatically
quarkus.flyway.migrate-at-start=true

# More Flyway configuration options
# quarkus.flyway.baseline-on-migrate=true
# quarkus.flyway.baseline-version=1.0.0
# quarkus.flyway.baseline-description=Initial version
# quarkus.flyway.connect-retries=10
# quarkus.flyway.schemas=TEST_SCHEMA
# quarkus.flyway.table=flyway_quarkus_history
# quarkus.flyway.locations=db/location1,db/location2
# quarkus.flyway.sql-migration-prefix=X
# quarkus.flyway.repeatable-sql-migration-prefix=K

Add a SQL migration to the default folder following the Flyway naming conventions: src/main/resources/db/migration/V1.0.0__Quarkus.sql

CREATE TABLE quarkus
(
  id   INT,
  name VARCHAR(20)
);
INSERT INTO quarkus(id, name)
VALUES (1, 'QUARKED');

Now you can start your application and Quarkus will run the Flyway’s migrate method according to your config.

With quarkus.flyway.migrate-at-start=true, as in the example above, Quarkus will execute the Flyway migration as part of the application startup.

@ApplicationScoped
public class MigrationService {
    // You can Inject the object if you want to use it manually
    @Inject
    Flyway flyway; (1)

    public void checkMigration() {
        // This will print 1.0.0
        System.out.println(flyway.info().current().getVersion().toString());
    }
}

1	Inject the Flyway object if you want to use it directly

In dev mode Quarkus will automatically restart the application if any of the existing migration scripts get modified. If you want to take advantage of this while developing and testing new migration scripts, you will want to set %dev.quarkus.flyway.clean-at-start=true, so that Flyway actually runs the modified migration.

Repairing the Flyway schema history table

There are different scenarios which may require repairing the Flyway schema history table. One such scenario is when a migration fails in a database which doesn’t support transactional DDL statements.

In such situations the Flyway repair command comes in handy. In Quarkus this can either be executed automatically before the migration by setting quarkus.flyway.repair-at-start=true or manually by injecting the Flyway object and calling Flyway#repair().

Multiple datasources

Flyway can be configured for multiple datasources. The Flyway properties are prefixed exactly the same way as the named datasources, for example:

quarkus.datasource.db-kind=h2
quarkus.datasource.username=username-default
quarkus.datasource.jdbc.url=jdbc:h2:tcp://localhost/mem:default
quarkus.datasource.jdbc.max-size=13

quarkus.datasource.users.db-kind=h2
quarkus.datasource.users.username=username1
quarkus.datasource.users.jdbc.url=jdbc:h2:tcp://localhost/mem:users
quarkus.datasource.users.jdbc.max-size=11

quarkus.datasource.inventory.db-kind=h2
quarkus.datasource.inventory.username=username2
quarkus.datasource.inventory.jdbc.url=jdbc:h2:tcp://localhost/mem:inventory
quarkus.datasource.inventory.jdbc.max-size=12

# Flyway configuration for the default datasource
quarkus.flyway.schemas=DEFAULT_TEST_SCHEMA
quarkus.flyway.locations=db/default/location1,db/default/location2
quarkus.flyway.migrate-at-start=true

# Flyway configuration for the "users" datasource
quarkus.flyway.users.schemas=USERS_TEST_SCHEMA
quarkus.flyway.users.locations=db/users/location1,db/users/location2
quarkus.flyway.users.migrate-at-start=true

# Flyway configuration for the "inventory" datasource
quarkus.flyway.inventory.schemas=INVENTORY_TEST_SCHEMA
quarkus.flyway.inventory.locations=db/inventory/location1,db/inventory/location2
quarkus.flyway.inventory.migrate-at-start=true

Notice there’s an extra bit in the key. The syntax is as follows: quarkus.flyway.[optional name.][datasource property].

Without configuration, Flyway is set up for every datasource using the default settings.

Customizing Flyway

In cases where Flyway needs to be configured in addition to the configuration options that Quarkus provides, the io.quarkus.flyway.FlywayConfigurationCustomizer class comes in handy.

To customize Flyway for the default datasource, simply add a bean like so:

@Singleton
public static class MyCustomizer implements FlywayConfigurationCustomizer {

    @Override
    public void customize(FluentConfiguration configuration) {
        // do something with configuration
    }
}

When named datasources are used, the @FlywayDataSource annotation can be used to specify the datasource to which the customizer applies. For example, if there are multiple datasources one of which is called users and customization of Flyway is needed for only that datasource, then the following code can be used:

@Singleton
@FlywayDataSource("users")
public static class UsersCustomizer implements FlywayConfigurationCustomizer {

    @Override
    public void customize(FluentConfiguration configuration) {
        // do something with configuration
    }
}

Using the Flyway object

In case you are interested in using the Flyway object directly, you can inject it as follows:

@ApplicationScoped
public class MigrationService {
    // You can Inject the object if you want to use it manually
    @Inject
    Flyway flyway; (1)

    @Inject
    @FlywayDataSource("inventory") (2)
    Flyway flywayForInventory;

    @Inject
    @Named("flyway_users") (3)
    Flyway flywayForUsers;

    public void checkMigration() {
        // Use the flyway instance manually
        flyway.clean(); (4)
        flyway.migrate();
        // This will print 1.0.0
        System.out.println(flyway.info().current().getVersion().toString());
    }
}

1	Inject the Flyway object if you want to use it directly
2	Inject Flyway for named datasources using the Quarkus `FlywayDataSource` qualifier
3	Inject Flyway for named datasources
4	Use the Flyway instance directly

Flyway and Hibernate ORM

When using Flyway together with Hibernate ORM, you can use the Dev UI to generate the initial schema creation script.

You can find more information about this feature in the Hibernate ORM guide.

Flyway and Reactive datasources

Flyway internally relies on a JDBC datasource, whereas reactive use cases will rely on reactive SQL clients, either directly or through Hibernate Reactive. This is not a problem in Quarkus, because a single configured datasource can be made available both through reactive clients and JDBC.

To use Flyway on a datasource you otherwise access reactively, simply make sure to configure that datasource both as JDBC and reactive. This involves in particular adding dependencies to Quarkus extensions for both the JDBC driver and the reactive client, for instance quarkus-jdbc-postgresql and quarkus-reactive-pg-client.

Flyway on Kubernetes

Sometimes, it’s helpful not to execute Flyway initialization on each application startup. One such example is when deploying

on Kubernetes, where it doesn’t make sense to execute Flyway on every single replica. Instead it’s desirable to execute it once and then start the actual application without Flyway. To support this use case, when generating manifests for Kubernetes the generated manifests contain a Kubernetes initialization Job for Flyway. The Job performs initialization and the actual Pod, will starts once the Job is successfully completed.

Disabling

The feature is enabled by default and can be globally disabled, using:

quarkus.kubernetes.init-task-defaults.enabled=false

or on OpenShift:

quarkus.openshift.init-task-defaults.enabled=false

Using a custom image that controls waiting for the Job

To change the wait-for image which by default is groundnuty/k8s-wait-for:no-root-v1.7 you can use:

quarkus.kubernetes.init-task-defaults.wait-for-container.image=my/wait-for-image:1.0

or on OpenShift:

quarkus.openshift.init-task-defaults.wait-for-container.image=my/wait-for-image:1.0

Note: In this context globally means for all extensions that support init task externalization.

Setting up support for Flyway
Developing with Flyway
- Repairing the Flyway schema history table
Multiple datasources
Customizing Flyway
Using the Flyway object
Flyway and Hibernate ORM
Flyway and Reactive datasources
Flyway on Kubernetes
- Disabling
- Using a custom image that controls waiting for the Job

Using Flyway

Setting up support for Flyway

Developing with Flyway

Repairing the Flyway schema history table

Multiple datasources

Customizing Flyway

Using the Flyway object

Flyway and Hibernate ORM

Flyway and Reactive datasources

Flyway on Kubernetes

Disabling

Using a custom image that controls waiting for the Job

Related content

On the same extensions

On the same topics