Skip to content
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

Support for Liquibase #5957

Closed
tqvarnst opened this issue Dec 5, 2019 · 10 comments
Closed

Support for Liquibase #5957

tqvarnst opened this issue Dec 5, 2019 · 10 comments
Assignees
Labels
kind/extension-proposal Discuss and Propose new extensions triage/out-of-date This issue/PR is no longer valid or relevant

Comments

@tqvarnst
Copy link
Contributor

tqvarnst commented Dec 5, 2019

Describe the extension
An extension to be able to use Liquibase database migration (https://www.liquibase.org/) as part of a Quarkus project.

Interested in this extension, please +1 via the emoji/reaction feature of GitHub (top right).

Configuration suggestion

# Add your application.properties here, if applicable.

Additional context
(Add any other context about the proposal here.)

@tqvarnst tqvarnst added the kind/extension-proposal Discuss and Propose new extensions label Dec 5, 2019
@tqvarnst tqvarnst changed the title Support for Liquid Base Support for Liquibase Dec 5, 2019
@gsmet
Copy link
Member

gsmet commented Dec 5, 2019

We already have Flyway. What would this one bring to the plate?

@andrejpetras
Copy link
Contributor

Hi,

we have lot of JEE applications using the liquibase tool to manage the database changes. We would like to move to the quarkus and also minimize the migration effort and keep the liquibase tool.

I managed to build the liquibase in the native image (it is crazy project) with a postgresql driver. https://github.com/1000kit/liquibase
I believe it should be possible to write the liquibase quarkus extension.

We are happy to contribute to this extension.

@maxandersen
Copy link
Member

@gsmet Liquibase has an abstraction layer so you can express migrations at a higher level which then gets converted into specific dialect so nicer to use if targeting multiple databases (like h2 for dev and postgresql for prod). Flyway is more "tuneable" but less generic so I say its worth getting both supported.

@andrejpetras contribution will be welcome! lets see what we can make happen!

@maxandersen
Copy link
Member

btw. looks like https://www.baeldung.com/quarkus-extension-java have a good start - i haven't tested if it works :)

@andrejpetras
Copy link
Contributor

I am back on the quarkus track ;) If nobody picked up this issue then please assign it to me, I will prepare the PR for it

@maxandersen
Copy link
Member

@andrejpetras there you go - looking forward to it :)

@liebig
Copy link

liebig commented Jan 7, 2020

Any news here? A Liquibase support would be great.

@andrejpetras
Copy link
Contributor

@liebig PR for liquibase extension #6334

@liebig
Copy link

liebig commented Jan 7, 2020

Oh great, thanks for the information and the implementation.

@maxandersen
Copy link
Member

this was merged a while back. closing.

@gsmet gsmet added the triage/out-of-date This issue/PR is no longer valid or relevant label Jun 17, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/extension-proposal Discuss and Propose new extensions triage/out-of-date This issue/PR is no longer valid or relevant
Projects
None yet
Development

No branches or pull requests

5 participants