Liquibase is an open-source database schema change management tool that enables teams to track, version, and deploy database changes easily and consistently. By utilizing migration scripts called “changesets,” Liquibase allows developers to manage schema updates, rollbacks, and track database changes across environments. Liquibase is widely used for database migrations because it supports multiple database types and integrates seamlessly into CI/CD pipelines, making it an essential tool for database version control.

Liquibase migrations serve as the backbone for managing database schema changes in various environments, including OLTP databases like Postgres or MySQL. These changes often propagate through an organization’s data architecture, impacting data warehouses such as BigQuery or Snowflake, which are populated via ETL tools like Fivetran or Stitch. Once in the data warehouse, the data undergoes transformations using tools like dbt or Matillion and is ultimately consumed by BI tools such as Looker or Tableau.

Because database migrations are so central to this process, any change made upstream via Liquibase migrations can affect the entire data pipeline. Schema modifications—such as altering column names or removing columns—can have far-reaching consequences on downstream processes, including dashboards, machine learning models, and analytics. It is crucial for teams to be notified of schema changes early on to avoid potential data quality issues and ensure that all dependent systems remain in sync.

Foundational’s Code Engine automates schema and lineage extraction by parsing Liquibase migration files. This automation allows users to detect and evaluate schema changes during the development phase or in pending Pull Requests (PRs). With this early visibility, teams can proactively assess the downstream impact of these changes before they are deployed, preventing disruptions in production environments.

Unlike tools that extract schema information from the database after deployment, Foundational parses Liquibase migration files directly from the code repository. This approach gives teams a much earlier view of schema changes, allowing for proactive assessment and reducing the risk of breakages that could affect production systems.

For example, instead of waiting until a migration is applied to the database, Foundational analyzes Liquibase migration scripts and highlights potential downstream impacts, ensuring that all stakeholders are informed before the changes are committed.

Setting up schema and lineage extraction for Liquibase with Foundational is straightforward. Simply connect your repository that contains the Liquibase migration files, and Foundational’s Code Engine will automatically detect and extract the schema details.

Once connected, the Code Engine scans and processes the Liquibase migration scripts, giving you full visibility into schema and lineage changes within your data infrastructure, without the need for direct access to your database.