-
Notifications
You must be signed in to change notification settings - Fork 1.9k
Don't ignore logicalFilePath when including changelogs #6664
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
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good fix.
5fdffb0
to
d5f3f6b
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Tested manually with spring boot and with the CLI. Works as expected.
d5f3f6b
to
bb62f7f
Compare
Be careful because if you pull the default docker image |
* chore: don't ignore logicalFilePath & parent tree cascading when including changelogs. * fix: use raw value * fix: do not overwrite previous result * chore: refactoring * Integration test added to validate changeset identifiers use the right logicalFilePath --------- Co-authored-by: Daniel Mallorga <dmallorga@liquibase.com>
* chore: don't ignore logicalFilePath & parent tree cascading when including changelogs. * fix: use raw value * fix: do not overwrite previous result * chore: refactoring * Integration test added to validate changeset identifiers use the right logicalFilePath --------- Co-authored-by: Daniel Mallorga <dmallorga@liquibase.com> (cherry picked from commit 6c524fc)
* chore: don't ignore logicalFilePath & parent tree cascading when including changelogs. * fix: use raw value * fix: do not overwrite previous result * chore: refactoring * Integration test added to validate changeset identifiers use the right logicalFilePath --------- Co-authored-by: Daniel Mallorga <dmallorga@liquibase.com>
Impact
Description
Don't ignore logicalFilePath & parent tree cascading when including changelogs.
Things to be aware of
Right now this kind of including fails:
As it produces th following changeset id, ignoring the child logicalFilePath:
This fix makes it produces the expected changeset ids:
This fix also accounts for more levels, so you can have:
It produces:
Additional Context
Fixes #6656