← All updates Databricks Update One-Pager Navy version
databricks Platform · Updated Jun 3, 2026

Declarative Automation Bundles will soon default to use the direct deployment…

On July 24, 2026, Declarative Automation Bundles will start using the direct deployment engine by default instead of the Terraform deployment engine.

What it does

On July 24, 2026, Declarative Automation Bundles will start using the direct deployment engine by default instead of the Terraform deployment engine. This will trigger a migration for all bundles still using the Terraform deployment engine. The Terraform deployment engine will eventually be removed and no longer available.

Why it matters

The new direct deployment engine uses the Databricks Go SDK and has the following benefits: Avoids issues with firewalls, proxies, and custom provider registries Detailed diffs of changes available using bundle plan o json Faster deployment No requirement to download Terraform and terraform provider databricks before deployment Reduced time to release new bundle resources, because there is no need to align with a Terraform provider release How do I start using direct deployment?

Architecture
Databricks Platform → Platform
In short

On July 24, 2026, Declarative Automation Bundles will start using the direct deployment engine by default instead of the Terraform deployment engine. This will trigger a migration for all bundles still using the Terraform deployment engine.

Read the full documentation ↗
Key takeaway
On July 24, 2026, Declarative Automation Bundles will start using the direct deployment engine by default instead of the Terraform deployment engine.
2026-06-03-375405d7 Generated by the Databricks Updates Agent · browse all updates