You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now FlywayMigrationInitializer is a plain unordered InitializingBean. As a result, we have little control over when it's executed. How about putting a higher priority on it or making it configurable?
For example, my application includes a bean that creates an executor and checks status periodically. Unfortunately it's being initialized before Flyway migration, so it fails to query the database.
The text was updated successfully, but these errors were encountered:
Right now
FlywayMigrationInitializer
is a plain unorderedInitializingBean
. As a result, we have little control over when it's executed. How about putting a higher priority on it or making it configurable?For example, my application includes a bean that creates an executor and checks status periodically. Unfortunately it's being initialized before Flyway migration, so it fails to query the database.
The text was updated successfully, but these errors were encountered: