Ignore Migration Patterns
Published 31 October 2023
Ignore Migration Patterns
Description
Ignore migrations during validate
and repair
according to a given list of patterns.
Only Missing
migrations are ignored during repair
.
Patterns
Patterns are of the form type
:status
with *
matching type
or status
.
type
must be one of (case insensitive):
repeatable
versioned
*
(will match any of the above)
status
must be one of (case insensitive):
Missing
Pending
Ignored
Future
*
(will match any of the above)
For example, the pattern to ignore missing repeatables is:
repeatable:missing
Patterns are comma separated. For example, to ignore missing repeatable migrations and pending versioned migrations:
repeatable:missing,versioned:pending
The *
wild card is also supported, thus:
*:missing
will ignore missing migrations no matter their type and:
repeatable:*
will ignore repeatables regardless of their state.
Default
*:future
Usage
Commandline
./flyway -ignoreMigrationPatterns="repeatable:missing" validate
TOML Configuration File
[flyway]
ignoreMigrationPatterns = ["repeatable:missing"]
Configuration File
flyway.ignoreMigrationPatterns=repeatable:missing
Environment Variable
FLYWAY_IGNORE_MIGRATION_PATTERNS=repeatable:missing
API
Flyway.configure()
.ignoreMigrationPatterns("repeatable:missing")
.load()
Gradle
flyway {
ignoreMigrationPatterns = ['repeatable:missing']
}
Maven
<configuration>
<ignoreMigrationPatterns>
<ignoreMigrationPattern>repeatable:missing</ignoreMigrationPattern>
</ignoreMigrationPatterns>
</configuration>
Clearing the value
By default, future
migrations are ignored. You can unset this by assigning an empty string to ignoreMigrationPatterns
For example, in your configuration file you would add:
flyway.ignoreMigrationPatterns=