Assignment

A named mapping of packages onto the work you deliver. It answers the question of where a policy applies, and it is the only one of the four governance objects that connects governance to your pipelines.

Catalog

A container for packages. Every workspace starts with the read-only Liquibase Default Catalog, the 60 checks built into Liquibase Secure 6.0 grouped into seven packages by category. Catalogs you create sit alongside it, and importing a checks settings file creates one.

Changelog

The ordered file — SQL, XML, YAML, or JSON — that lists your database changes as changesets. The changelog is the source of truth for what should be true in a database. In Liquibase Server, a registered changelog is different: the record that deployment runs are attributed to on the dashboards. See Create a database change and Register a changelog.

Changeset

The unit of change: a set of changes uniquely identified by id, author, and changelog path, deployed once and recorded in the DATABASECHANGELOG table. One logical change per changeset. See Create a database change.

Check

One rule. Require primary key when creating table is a check. Each check carries a severity, a category, and a set of parameters you can tune, and it inspects either your changelogs or a snapshot of the database itself.

Package

A named group of checks. Packages are the unit you hand around. You assign a package rather than a check, which is what makes a standard something a team adopts in one action instead of thirty.