Hi,
I really appreciate your tool, as I was evaluating it for our application. Geat work.
Now my question which I hope was not asked before (search did not bring up anything):
Is it possible to assign different onFail actions, depending on which of the checks in the preconditions failed?
Example:
I want to add a column to a table, but it may happen in our environment, that the whole table does not exist.
If the column (and so the table) already exists the change should be marked RAN. But if the whole table does not exist, CONTINUE, as the table could be added later on.
My first approach was to have an onFail and onError attribute and then run the check
-
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