documentation/Reference/Configuration/Flyway Namespace/Flyway Ignore Migration Patterns Setting.md
Ignore migrations during validate and repair according to a given list of patterns.
Only Missing migrations are ignored during repair.
Patterns are of the form type:status with * matching type or status.
type must be one of (case insensitive):
repeatableversioned* (will match any of the above)status must be one of (case insensitive):
MissingPendingIgnoredFuture* (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.
String array
"*:future"
./flyway -ignoreMigrationPatterns="repeatable:missing" validate
[flyway]
ignoreMigrationPatterns = ["repeatable:missing"]
flyway.ignoreMigrationPatterns=repeatable:missing
FLYWAY_IGNORE_MIGRATION_PATTERNS=repeatable:missing
Flyway.configure()
.ignoreMigrationPatterns("repeatable:missing")
.load()
flyway {
ignoreMigrationPatterns = ['repeatable:missing']
}
<configuration>
<ignoreMigrationPatterns>
<ignoreMigrationPattern>repeatable:missing</ignoreMigrationPattern>
</ignoreMigrationPatterns>
</configuration>
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=