-
Notifications
You must be signed in to change notification settings - Fork 2.2k
FINERACT-2423: Fix invalid Liquibase changelog filename with space #5264
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
base: develop
Are you sure you want to change the base?
FINERACT-2423: Fix invalid Liquibase changelog filename with space #5264
Conversation
| xsi:schemaLocation="http://www.liquibase.org/xml/ns/dbchangelog http://www.liquibase.org/xml/ns/dbchangelog/dbchangelog-4.1.xsd"> | ||
| <include file="parts/0003_postgresql_specific_initial_data.xml" relativeToChangelogFile="true"/> | ||
| <include file="parts/0004_camelcase_column_renaming.xml" relativeToChangelogFile="true"/> | ||
| <include file="parts/0004_camelcase_column_renaming.xml" relativeToChangelogFile="true"/> |
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.
we dont need this extra space
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.
Thanks for the review.
I’ve removed the unnecessary whitespace in changelog-tenant.xml and added a new Liquibase changeset to safely fix the invalid 0072 filename so it won’t be executed twice.
Please let me know if anything else is needed.
fineract-provider/src/main/resources/db/changelog/tenant/changelog-tenant.xml
Show resolved
Hide resolved
adamsaghy
left a comment
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.
Kindly see my concerns!
|
Thanks for pointing this out, and apologies for the confusion earlier. I understand your concern now — renaming alone can break existing databases because Liquibase tracks executed changesets by filename. I am addressing this by adding a new changeset that executes before 0072_add_result_and_status_to_command_source.xml, which updates the filename entry in DATABASECHANGELOG. This ensures:
I’ll update the PR shortly with this fix. Thanks for your patience and for highlighting this. |
...ovider/src/main/resources/db/changelog/tenant/parts/0071_1_fix_invalid_filename_for_0072.xml
Outdated
Show resolved
Hide resolved
6187378 to
3cd23b2
Compare
Please run |
@adamsaghy Thanks for pointing this out. |
|
I am afraid my advice was not correct... i see it is still failing in some situations. Let try with this please: |
Description
This PR fixes an invalid Liquibase changelog filename that contained a space in its name.
Liquibase does not support filenames with spaces reliably, which caused build and verification failures.
The change renames the affected changelog file to a space-free name and updates the corresponding reference to ensure consistency and successful execution.
Changes Made
Renamed the invalid Liquibase changelog file to match Fineract naming conventions
Updated the tenant changelog (changelog-tenant.xml) to reference the corrected file
Ensured no functional or logical changes to the database schema itself
Updated changelog-tenant.xml to reference the corrected filename
Testing
Ran ./gradlew spotlessApply
Ran ./gradlew build
Verified Liquibase changelog integrity locally
JIRA Ticket
https://issues.apache.org/jira/browse/FINERACT-2423
Checklist