Is there a way to execute a liquibase update so that it stops running a specified point in the change log?
I know that I can update (n) changesets using updateCount but that would require some complicated calculations which would b impractical in any kind of automated manner.
What I am looking for is something that is similar to the rollback command but works in the forward direction rather than reverse.
We are implementing Liquibase for a very large and complex project with multiple database instances in several environments. We want to be able to uplift the database to different levels depending on the environment from a single changelog
-
Learn
-
Resources
-
Free Tools
OSS Risk Scanner Database DevOps Risk AssessmentCheat Sheets
Snowflake + Liquibase Databricks + Liquibase -
eBooks
6 Liquibase Community Risks & How to Avoid Guide: SOC 2 Compliance at the Database Layer Guide: Quantify the Value of Liquibase Secure -
Comparison Guides
Liquibase vs. Flyway Liquibase vs. Bytebase Liquibase Community vs Liquibase Secure
-
- Quickstart
- Get Started
- Documentation
- University
-
Resources
- Connect
- Contribute
- Join
- Blog