Deploying a bundle with the Azure Databricks CLI

Databricks Asset Bundles let you package notebooks, jobs, pipelines, and configuration as source-controlled YAML (databricks.yml) and deploy them consistently using the Databricks CLI. The CLI provides commands to validate, deploy, run, and destroy bundles across environments such as dev, staging, and prod using named targets.

1 · Learn the must-know

• 1A bundle is initialized with 'databricks bundle init' (optionally from a template) and defined by a root databricks.yml plus resource YAML files describing jobs, pipelines, and other assets.
• 2'databricks bundle validate' checks the configuration and resolves variables/targets before deployment, catching syntax and reference errors early.
• 3'databricks bundle deploy -t <target>' uploads bundle artifacts to the Databricks workspace and creates or updates the corresponding jobs/pipelines defined for that target.
• 4Targets in databricks.yml can set mode: development or mode: production, which affects behaviors like resource naming prefixes, run-as identity, and whether resources are treated as disposable.
• 5The CLI must be authenticated (e.g., via a configured profile or OAuth/PAT) with the correct workspace URL before running bundle commands, and the active profile/target determines which workspace receives the deployment.
• 6'databricks bundle run <resource-name>' executes a deployed job or pipeline, while 'databricks bundle destroy' tears down all resources created by that bundle deployment for a given target.

2 · Check your understanding