Uses

Use the check to enhance deployment control of specific changesets by requiring one or more contexts be assigned to every changeset in a changelog. Whether in automation or manual testing of proposed schema changes at the dev level, contexts provide better deployment control. Using contexts allows just the changesets that match the specified contexts filter(s) to be run. For example, a team could provide contexts to change sets by "dev," "staging," "prod," or all three "dev, staging, prod," and when a Liquibase job is run, only the specified subset of context-matching changesets will be deployed. This policy check, like other checks, can be configured with a "severity" level that returns an exit code designed to stop automated jobs, giving your team time to apply this Liquibase best practice.

Note: Contexts and Labels are similar, but the best-practice is to use context for deployment environments and labels more like free-form tags for features, content, release, or other process-centric filter.

Before you begin

1. Ensure that you have correctly specified your Liquibase Pro license key.

2. Ensure that the --checks-scope parameter includes the scope of this check.

--license-key=<string>
--checks-scope=<string>

--license-key=<string>
--checks-scope=<string>