Skip to content

Deploy and run the Databricks bundle

This guide validates, plans, deploys, and runs the repository's bricksgdpr_dbt_workflow job.

The default dev bundle target has no schedule. It writes the canonical demo catalog and is intended for one deployer.

Prerequisites

Complete the first deployment, including the secret, persona groups, and access controls. Authenticate the bricksgdpr CLI profile and source the reviewed .env; this supplies the required BUNDLE_VAR_warehouse_id.

Validate the bundle

databricks bundle validate --strict --profile bricksgdpr

Validation should resolve the dev target, the bricksgdpr_dbt_workflow job, and the configured SQL warehouse without an error.

Inspect the plan

databricks bundle plan --profile bricksgdpr

Review every proposed workspace change before continuing.

Warning

Deployment changes workspace state. Stop if the plan targets an unexpected workspace path, job, warehouse, or catalog.

Deploy and summarize

databricks bundle deploy --profile bricksgdpr
databricks bundle summary --profile bricksgdpr

The summary should show one deployed job named bricksgdpr_dbt_workflow under the deployer's private bundle workspace path.

Run the workflow

databricks bundle run bricksgdpr_dbt_workflow --profile bricksgdpr

The job's build_and_validate task performs this sequence:

  1. bootstrap the project catalog;
  2. build every governed relation except the live access-control tests;
  3. apply access controls;
  4. run the access-control tests; and
  5. run the complete dbt build.

Serverless Jobs compute runs the pinned dbt environment. The configured SQL warehouse executes the generated SQL.

Use another compatible warehouse

Override the reviewed environment value only when the target warehouse is serverless or pro and is intended for this deployment:

databricks bundle validate --strict --profile bricksgdpr \
  --var="warehouse_id=<warehouse-id>"

The variable applies to that command. Supply the same reviewed override to later bundle commands that must use it.

Note

The bundle excludes acceptance/**, docs/**, scripts/**, and profiles.yml from workspace synchronization. Account identity provisioning and temporary-persona acceptance remain separate explicit operations.

Consult the bundle job reference for exact timeouts, dependencies, and synchronization rules.