Flyway V8 Community Edition and `ignoreMissingMigrations`

Hello and thank you for this wonderful project! Sorry for not following the issue template, but my question is pretty short.

The ignoreMissingMigrations configuration is deprecated in 8.0.0 and will be removed in the next major version. It is recommended to switch to ignoreMigrationPatterns. But doing so results in runtime errors stating that ignoreMigrationPatterns config requires the Teams subscription! I would like to clarify if it is really planned that a paid subscription will soon be required just to have the ability to skip missing migrations?

This functionality is pretty basic and it is required in order to have an opportunity to quickly rollback application deployments (if migrations are backward-compatible).

[DoodleBobBuffPants]

@johnou When migrations are marked DELETE their success value is kept the same, however we treat deleted migrations as if the change they were making was also removed from the DB, which is why they appear as PENDING when they are restored, and is why they are applied again

[johnou]

it does however repair now invokes deleteMissingMigrations which I’d like to avoid, we’ve had a few situations where we’d have to correct a migration that has already been applied to test / staging environment but at the same time retain missing migrations in the history table.