Discussion on "[Mastering Oracle SQLcl Liquibase - Part 3/3] - Synchronize your existing environments"

Rafal Grzegorczyk · 2023-09-19T08:41:16.610Z

In previous parts, you've learned how to start using SQLcl Liquibase with a new database and then track your database changes made after. In this part, I will show you how to synchronize your existing environments with Liquibase. Using my tips, you c...

Hi Richard! Thanks for asking. The answer is: it depends :) I would see some approaches for that:

Every developer cleans his mess before you will run the generate-schema command versus DEV and then update to UAT ( so you don't have those tables then)
Manually remove those changesets (with those 5 not needed tables) from files generated by generate-schema and then update to UAT
You run generate-schema only at the beginning of your journey with SQLcl Liquibase. After that, every developer creates his changesets and commits them to git. Those 5 tables will not be added there, so they will not be deployed to UAT during the update.
After running generate-schema on DEV, edit the changesets with those 5 tables and add a tag contexts="DEV_ONLY" ( or any other name ). When deploying to UAT, use liquibase update -changelog-file controller.xml contexts="!DEV_ONLY." Thanks to that, changes with contexts DEV_ONLY will not be deployed.

And a few more approaches, I suppose. Hope it helps. Rafal

Search Hashnode

[Mastering Oracle SQLcl Liquibase - Part 3/3] - Synchronize your existing environments

Responses(1)