Precondition in databaseChangeLog should allow to skip the whole file

Environment

Liquibase Version: 3.4

Liquibase Integration & Version: CLI

Liquibase Extension(s) & Version:

Database Vendor & Version:

Operating System Type & Version:

Description

There is no option to conditionally include a file or to skip executing file if preConditions in databaseChangeLog fails

Steps To Reproduce

List the steps to reproduce the behavior.

1. Create ABC table
2. Execute:

<databaseChangeLog xmlns='http://www.liquibase.org/xml/ns/dbchangelog' xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance' xsi:schemaLocation='http://www.liquibase.org/xml/ns/dbchangelog http://www.liquibase.org/xml/ns/dbchangelog/dbchangelog-3.4.xsd'>

    <preConditions onFail="CONTINUE"> <!-- CONTINUE not supported -->
        <not><tableExists tableName="ABC"/></not>
    </preConditions>

    <include file="tables.xml" relativeToChangelogFile="true"/>

</databaseChangeLog>

Actual Behavior

It fails because preConditions in databaseChangeLog supports only WARN and HALT. CONTINUE is not supported:

org.xml.sax.SAXParseException: cvc-enumeration-valid: Value 'CONTINUE' is not facet-valid with respect to enumeration '[HALT, WARN]'. It must be a value from the enumeration.

Expected/Desired Behavior

When ABC table exists, the whole databaseChangeLog should be skipped.

Additional Context

It was reported before: https://liquibase.jira.com/browse/CORE-1421 https://liquibase.jira.com/browse/CORE-917

[nealeu]

@CristianDuta It depends on your situation. We have some changelog files that we omit in order to reduce the number being loaded. In particular we now have e.g. changelog-2021-onwards.xml which is linked from changelog-2020-onwards.xml, and for production systems we set a year for database updates so we don’t load all the XML for changes that have all been applied. For CI, we also add in contexts to apply test data and some feature toggles.

[esselesse]

What about this feature? Is it in process?