Liquibase forward engineering lets teams generate version-controlled changelogs directly from their SqlDBM models, closing the gap between design and automated deployment. The model stays as the single source of truth while Liquibase handles safe, incremental, git-connected rollouts of governed database change-management workflows.
This feature is currently available for the following projects due to intricacies in the syntax:
- Snowflake
Generating Liquibase scripts
Liquibase script generation is available on the Forward Engineering (FE) page for available projects. Just like existing FE capabilities, Liquibase supports both full Create and Alter (from pervious revisions) scripts.
The format is compatible with the latest Liquibase version.
Generating Full changelogs
On the revisions step (2), select the "Full changelog" option (default) to generate the entire project with all objects included.
By default, the latest revision is selected.
Select a historic revision from list to generate a snapshot of the desired state.
Once selected, press the "Generate Liquibase" button at the top to generate the script.
Generating diffs/alters
On the revisions step (2), select the "Changeset diff" option to generate the only the alters from a previous revision.
By default, the latest two revisions are selected as the from/to candidates.
Select a historic revision from list to generate the alter between the two revisions.
Once selected, press the "Generate Liquibase" button at the top to generate the script.
Pushing to git
Before pushing to git, ensure that a User Connection is selected in the project settings (see related article) with a valid git integration.
Once a full or alter script is generated, press the "Push to Git" button.
Optionally, configure the desired target folder for the generated YAML asset in the dropdown menu of the "Push to Git" button.
See also