Skip to content
All topics

Asset Bundles

Recent items mentioning Asset Bundles across the Databricks ecosystem — releases, news, videos, and community Q&A. Updated hourly.

19 recent items19 releases

What is Asset Bundles?

Declarative Automation Bundles, formerly Databricks Asset Bundles, are the infrastructure-as-code layer for Databricks projects. You describe everything a project needs in configuration files: jobs, pipelines, dashboards, model serving endpoints, and MLflow experiments and registered models. The Databricks CLI then validates that definition and deploys the whole project to a workspace as one unit.

Bundles exist to bring ordinary software engineering practice to data and AI work. Because the entire project lives in version-controlled files, you get code review, testing, and CI/CD instead of hand-edited jobs that drift apart across workspaces. The same bundle deploys to development, staging, and production with per-target overrides, so promoting a pipeline is a deploy command rather than a rebuild by hand.

Bundles have been generally available since April 2024. The rename to Declarative Automation Bundles landed in March 2026, partly because the word assets was ambiguous on the platform. The direction since GA: resources can be defined in Python as well as YAML, bundles are editable in the workspace UI, and new bundles created with CLI 1.3.0 or later deploy through a direct engine instead of Terraform.

Why were Databricks Asset Bundles renamed?

Databricks renamed them Declarative Automation Bundles on March 16, 2026, saying the new name better reflects what bundles do and that assets meant too many different things on the platform. The change is non-breaking: the bundle CLI command still works and existing configuration needs no edits.

Are bundles generally available?

Yes. Bundles reached GA in April 2024 with Databricks CLI 0.218.0. Editing, testing, and deploying bundles from the workspace UI became generally available in October 2025.

Do I have to write YAML, or can I use Python?

YAML is the default format for bundle configuration. Python support is also generally available (since October 2025, with CLI 0.275.0), and it lets you define resources in Python and modify them programmatically during deployment.

Do bundles use Terraform under the hood?

Older bundles deploy through a Terraform-based engine, but bundles created with CLI 1.3.0 or later default to the direct deployment engine, which became generally available in June 2026. Either way you never write Terraform yourself; the CLI handles validation and deployment from your bundle files.

Sources: What are Declarative Automation Bundles?, Databricks docs · Declarative Automation Bundles feature release notes, Databricks docs · Declarative Automation Bundles FAQs, Databricks docs

What's happening in Asset BundlesAI synthesis · updated Nov 19, 2026

Databricks CLI v1.26.0 expanded Asset Bundles with support for feature spec resources and resource grant dependencies, while preventing redeployments from overwriting manually configured app compute sizes 8. Operational workflows are concurrently maturing around new deployment history tracking 4, pre-deployment policy-as-code governance 9, and unified multi-environment CI/CD delivery 10.

Generated daily from the 10 most recent items mentioning Asset Bundles. Click any [N] to jump to the source.

Get Tuesday's version of this

Tracking Asset Bundles? The Tuesday email carries what moved across the whole ecosystem, not just this topic. Free, one-click unsubscribe.

Read past issues first