Liquibase boosts Snowflake control plane governance

Liquibase has released Liquibase Secure 5.1, adding support for governing Snowflake control plane changes. The update extends its change-control approach beyond database schema updates to cover access, data movement, and execution settings.

The release highlights Snowflake configuration changes as a growing governance priority for organisations running analytics and data products on the platform. These updates often fall outside the approval and audit processes used for schema evolution, even though they can affect permissions, data sharing, and automated workloads.

Liquibase Secure 5.1 introduces "Modelled Change Control" for Snowflake. It treats certain control plane changes as modelled objects rather than scripts, enabling more consistent policy enforcement, clearer drift detection, and a stronger audit trail.

Snowflake's control plane includes administrative and operational settings above the data structures themselves. This spans access and security configuration, controls for data sharing and movement, platform and cost controls, and automated execution. While many enterprises apply structured governance to schema changes, control plane updates still often arrive as ad hoc scripts or manual steps, complicating review and evidence collection.

Governance gap

Control plane changes can be risky when Snowflake serves multiple business teams and downstream applications. A permissions change can widen access to sensitive datasets. A sharing update can change a data product's compliance footprint. An execution change can alter how pipelines run and which workloads consume resources.

Liquibase argues that the practices used in application delivery and schema management should also apply to these platform-level adjustments. In data and AI programmes, misconfigurations can have wider effects because training data and features may flow through multiple pipelines and products.

Secure 5.1 applies standardised workflows across environments and teams for Snowflake control plane changes. It also generates evidence for each governed change and flags drift when updates occur outside the approved process.

Liquibase expects the release to help teams block risky changes before production, standardise delivery across environments, generate audit evidence, detect out-of-band updates, and support reversibility through rollback procedures. These capabilities align with controls that regulated industries often require, including traceability and separation of duties.

"As enterprises modernize their developer platforms for AI-driven delivery, change control at the database layer has become a prerequisite, not a nice-to-have," said Mirek Novotny, Sr. Director of Product, Liquibase. "If Snowflake control plane changes aren't governed and observable, you can't prove control. Liquibase Secure 5.1 brings predictability and evidence to the changes that matter most, without slowing teams down."

Broader coverage

Alongside Snowflake, Liquibase Secure 5.1 adds support for Couchbase, AWS Keyspaces, DataStax Enterprise, and AlloyDB. It also extends support for Databricks and MongoDB.

Liquibase says its platform covers more than 60 database and data-store environments across legacy and cloud services. That breadth reflects how large organisations often run multiple data platforms at once. Governance teams can struggle when controls and evidence differ across systems, even when the underlying policy intent is consistent.

This breadth also drives competition among database change governance tools, with differentiation around connector coverage and integration depth. Organisations want consistent controls and reporting across a heterogeneous estate, without stitching together multiple tools that each cover only a narrow set of platforms.

DataOps context

The Snowflake support also reflects a broader shift in how data teams operate. DataOps and platform engineering increasingly mirror software delivery, with repeatable pipelines and shared internal platforms. This raises expectations for automation and review, including for changes once handled only by specialist administrators.

Liquibase positions the Snowflake support as relevant to AI readiness as well as security and compliance. The goal is to control changes that could affect sensitive training data, expand data sharing, or modify execution behaviour in ways that are hard to detect after the fact.

Liquibase Secure 5.1 is available now. Liquibase says it will continue adding database platform support and expanding modelled change types for cloud data services.