Liquibase configuration to run different sql scripts test vs prod

Question

Is there a way to configure liquibase to run different sql scripts test vs prod with maven?

That seems like a bad idea, then you haven't necessarily run and tested those scripts before trying to do so in prod. This may be an XY problem; what's the problem you're trying to solve with this? — jonrsharpe
– jonrsharpe, Commented May 7, 2020 at 6:44
To add dummy data into the test database and to avoid doing that in prod environment. — matheo
– matheo, Commented May 7, 2020 at 6:48
Perhaps that should be a separate task to migrating? This is usually referred to as seeding. — jonrsharpe
– jonrsharpe, Commented May 7, 2020 at 6:49

htshame · Accepted Answer · 2020-05-07 09:16:14Z

2

To solve the problem you can use Liquibase context. It allows you to execute only specific changeSets which are related to the provided context.

For maven you can use -Dliquibase.contexts=test_context

If you have a Spring applications, you can use spring.liquibase.contexts=test_context

And in changeSets set context attribute:

<changeSet id="foo" author="bat" context="text_context">
   <!-- your logic here -->
</changeSet>

answered May 7, 2020 at 9:16

htshame

7,4655 gold badges43 silver badges66 bronze badges

Sign up to request clarification or add additional context in comments.

2 Comments

ronak Over a year ago

Here's a link that may help as well: liquibase.org/2014/11/contexts-vs-labels.html It is context vs labels and outlines the way liquibase can control which script in which environment will get ran, and includes when to use either context, label, or both.

ru51an Over a year ago

Works like a charm! You can also use labels instead of contexts

Collectives™ on Stack Overflow

Liquibase configuration to run different sql scripts test vs prod

1 Answer 1

2 Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

2 Comments

Your Answer

Sign up or log in

Post as a guest

Related