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
First of all, I thought configuration set in env vars would always be considered, but as far as I understand only the Maven and Gradle integrations obey these variables since they use the ConfigUtil. In other words, settings env vars has no effect on the Java API as long as I instantiate Flyway by myself: new Flyway(). On the Java API I'm expected to call the configuration setters (setCleanDisabled(...)) also before using the Flyway object.
In addition, things behave different for the Spring Boot Autoconfiguration. If I'm having my Flyway object injected, Spring Boot will configure it for me - by using Spring's configuration enviroment. Thus I can use environment variables here, but I have to stick to Spring's property notation, e.g. flyway.clean-disabled=true.
I had to learn this the hard way. Could you please clarify this in the documentation?
The text was updated successfully, but these errors were encountered: