Liquibase tries to re-execute scripts in containerized deployed application

Support
#1

I have an application that runs against a postgres database.

For my devops pipepines I attempted to create a docker image and get it deployed. The deployed version does not start due Liquibase trying to recreate existing tables.

Liquibase uses the path to the migration files as the key to identify if they should be executed or not. The path can differ depending on how the application is started.

The issue is exactly as described here How to alter databasechangelog.filename for Spring Boot and Liquibase? - Stack Overflow

The proposed solution would be to include logicalFilePath to decouple it from the physical file path. This is currently not part of the generated Liquibase files and would require changing all existing files.

I found a post on liquibase forum from just a few days ago that discusses the topic.

For now I can continue since it should be a separate db anyway, but sometimes it is useful to be able to debug against an existing database in early development.

#3

bump

#4

Hello Tom!

Sorry for the late reply.

Thank you for the proposed improvement! The issue has been created.
Is this issue also appears for jmix library scripts (e.g. for /io/jmix/data/liquibase/changelog.xml)?

Regards,
Dmitry

1 Like
#5

No, it doesn’t seem to be an issue, the same goes for plugins like multitenancy and audit.

It seems to be correct when the migration scripts reside in a .jar file and only pops up when they reside in an exploded deployment.

I didn’t notice this aspect before, I just use the vanilla jmix build.gradle and added the bootBuildImage task. Perhaps packaging as ,jar would solve the issue, but I have to admit I never used bootBuildImage before.

image

1 Like