-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Flyway 7 Breaking Changes Announcements #2705
Comments
Thanks for announcing these changes early on and allowing us to comment.
As long as these locations may be empty without Flyway considering that to be an error, this is a great idea. I lost countless hours to debugging Flyway only to find out I had a typo in one of the locations. Zooming out a little, though, it feels like a breach with the concept of "dynamic discovery" currently used: As it is now, it feels to me like Flyway is trying to be "smart" with information about the migrations being decentralized, so (Many disliked this "smartness", including me, see #2698, #2541, #2610, #2647, #2683, ...) In contrast, it could be "dumb", with information about the migrations being centralized, so instead of By being strict on "locations" (which is one of the few centralized configuration points), Flyway somewhat limits the ways I interact with it. For example, we currently have just one Flyway configuration for both production and setups with a test fixture:
Since we make sure not to include demo-data in a production setup, there is no need to have two different Flyway configurations. So with Flyway 7.0, we'll either have to make structural changes to our deployment setup. Providing an empty In conclusion, I'd like the following most:
Lacking that, I'd wish for a configuration option |
Can you please provide an example of using dots (.) as path separators to help us understand what kind of cases will be forbidden? |
@cowwoc Internally, paths that began with
Is converted internally to:
Such paths will produce an error in V7. The code is in |
@MikielAgutu Perfect, thanks. |
Any update on support to have the script location from s3 bucket path |
This will be coming in Flyway v7. We do not have a release date for this, but you can see the v7 work on the v7 branch: https://github.com/flyway/flyway/tree/v7 |
That is Great,Thanks! |
Flyway 7 is released!
Flyway 7 has now been released. You can find the official list of the breaking changes in the release notes: https://flywaydb.org/documentation/releaseNotes#7.0.0.
The text below is possibly out of date now. I'll keep it for posterity. Refer to the release notes for the complete information.
Flyway 7 is due roughly in the summer of this year. We plan to make the following breaking changes on the first version 7 release:
Platform support
Breaking changes
flyway.locations
will produce errors instead of warnings.
) as path separators inflyway.locations
will be deprecated and produce an error when usedMigrationType.SPRING_JDBC
andMigrationType.UNDO_SPRING_JDBC
will be removedMigrationType.JDBC
andMigrationType.UNDO_JDBC
insteadFlyway
class-
to be passed to the configFiles argumentComments and questions are welcome. This post will be updated with more changes in the run up to version 7.
The text was updated successfully, but these errors were encountered: