Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ignoreMissingMigrations default not specified #1678

codingthat opened this issue Jun 20, 2017 · 1 comment

ignoreMissingMigrations default not specified #1678

codingthat opened this issue Jun 20, 2017 · 1 comment


Copy link

@codingthat codingthat commented Jun 20, 2017

What version of Flyway are you using?


What did you do?

Opened flyway.conf to set it up for the first time.

What did you expect to see?

A default mentioned.

What did you see instead?
# Ignore missing migrations when reading the metadata table. These are migrations that were performed by an
# older deployment of the application that are no longer available in this version. For example: we have migrations
# available on the classpath with versions 1.0 and 3.0. The metadata table indicates that a migration with version 2.0
# (unknown to us) has also been applied. Instead of bombing out (fail fast) with an exception, a
# warning is logged and Flyway continues normally. This is useful for situations where one must be able to deploy
# a newer version of the application even though it doesn't contain migrations included with an older one anymore.
# true to continue normally and log a warning, false to fail fast with an exception.
# flyway.ignoreMissingMigrations=
@axelfontaine axelfontaine added this to the Flyway 5.0.0 milestone Jun 20, 2017
axelfontaine added a commit to flyway/ that referenced this issue Nov 27, 2017
Copy link

@axelfontaine axelfontaine commented Nov 27, 2017

Good catch! Fixed.

dohrayme pushed a commit to dohrayme/flyway that referenced this issue Feb 3, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants
You can’t perform that action at this time.