Asset Bundles
Recent items mentioning Asset Bundles across the Databricks ecosystem — releases, news, videos, and community Q&A. Updated hourly.
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
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.
Databricks Asset Bundles adds support for feature spec resources and resource grant dependencies, while preventing redeployments from resetting manually configured app compute sizes. Additionally, the AI Runtime accelerates execution through parallel snapshot compression for large Git repositories and workspace connection reuse.
Databricks Asset Bundles now deploy registered model aliases to Unity Catalog and resolve bugs that repeatedly reapplied permissions and grants to recreated resources. The CLI also restores Databricks-specific pip magic execution in Jupyter notebooks over SSH and removes the CRITICAL compute priority class from AI Runtime.
Databricks Asset Bundles now utilize a multipart upload endpoint for improved deployment throughput and automatically retry operations encountering transient server errors. This release also adds uv workspace support for local environment setup alongside fixes for bundle deployment binding, immutable folders, and relative path resolution.
Release: v2.21.0 (#2248)
Databricks Asset Bundles now exclusively deploy using the direct engine, removing the Terraform deployment engine and its bundled binary. This release also restores default TLS certificate verification for SDK calls and sorts folders alphabetically in the Workspace File System view.
The Terraform deployment engine for Databricks Asset Bundles has been removed, requiring users to migrate to the direct engine or remain on CLI v1.19.x. Additional updates include a fix for large integer corruption in API commands, group-level run-as support in bundles, and expanded authentication options for Databricks Apps.
The CLI introduces a preview image push command for the Databricks Artifact Registry, preconfigures coding assistants in serverless SSH sessions, and adds expiration flags for Postgres branch creation. In Asset Bundles, clusters now support library configurations, Terraform deployments migrate to the direct engine prior to execution, and Postgres snapshot schedules are restricted to YAML.
AI Runtime commands have moved from experimental to databricks air, and SSH commands now support keeping detached background processes running after tunnel disconnect. Databricks Asset Bundles direct engine resolved multiple issues around unnecessary resource recreations, Unity Catalog grant convergence, and Git-sourced Python tasks.
Databricks Asset Bundles introduces PyDABs catalog support, updates default templates to Databricks Runtime 16.4, and adds validation checks before completing migrations to the direct engine. The release also fixes several direct deployment engine update bugs and improves Python fallback handling during local environment setup.
Databricks Asset Bundles now correctly handles app updates during bundle deployment when an active deployment already exists. It also fixes reference resolution and deployment failures for resource keys starting with an underscore.
Bundles automatically migrate from Terraform state to the direct engine on clean deploys (opt-out via engine: terraform), and SSH sessions stay connected during idle periods with automatic keepalives every 30 seconds. Direct engine bundle operations now correctly handle removed configuration fields, support cluster policies resources, and include a DATABRICKS_BUNDLE_RESOURCE_MAX_WAIT timeout setting.
Databricks Asset Bundles now report detailed resource action summaries and file sync counts during deploy and destroy operations, alongside fixes for workspace Git folder metadata and state migration. The CLI now enables FIPS 140-3 compliance by default for TLS connections, adds Goose support to aitools, and automatically resolves conflicting databricks-connect pins in local environment setups.
The databricks genie ask command is now stable (promoted from experimental), enabling practitioners to ask natural-language questions about their data directly from the CLI. Multiple reliability and usability improvements ship, including auth profile validation timeouts, fixes for GCS-backed UC Volumes deletion, bundle validation for sql_warehouse configurations, opt-in spark_python_task file downloads in bundle generation, and instance_pools resource support in Declarative Automation Bundles.
Databricks Asset Bundles now includes a select flag in the direct deployment engine to plan and deploy specific resource subsets, along with support for Terraform references and automatic transient HTTP retries. The experimental open command expands to support additional workspace resources such as volumes and vector search endpoints, while notebook task paths now correctly preserve Lakeflow Designer files.
Databricks Asset Bundles now support a DeploymentMode field for both Deployment and Version objects. Workspace settings include new fields for CollaborationPlatformConnectivity and EffectiveCollaborationPlatformConnectivity.
Databricks Asset Bundles deployment and version objects in the SDK now include a deployment mode field. The settings service added new fields to track collaboration platform connectivity and its effective status.
Databricks CLI v1.0.0 is now generally available, moving interactive OAuth token storage to OS-native secure stores by default and requiring users to re-authenticate with databricks auth login. This release also introduces the databricks aitools command group for managing coding agent skills and adds new Lakebase Postgres resources for Databricks Asset Bundles.
This release introduces a new bundle package and workspace-level service for managing Databricks Asset Bundles. It also adds an MtlsConfig field to ml.AuthConfig for mTLS authentication configurations.
This release introduces a breaking change that renames the min_qps configuration and CLI flag to target_qps for vector search endpoints, and it stops applying bundle name prefixes to these endpoints. Additionally, it improves the interactive authentication profile pickers, enhances OS keyring token storage behavior, and fixes bundle bugs related to nested notebook directory generation and multi-profile authentication propagation.
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.