CLI v1.20.0 removed the Terraform deployment engine from Asset Bundles, leaving the direct engine

The main change in October was the end of the Terraform deployment engine. CLI v1.20.0 removed it, so users had to migrate to the direct engine or stay on v1.19.x. The same release fixed large integer corruption in API commands, added group-level run-as support in bundles, and widened authentication options for Databricks Apps [29]. A later release note described Asset Bundles as deploying exclusively with the direct engine, with the bundled Terraform binary gone [21]. CLI v1.21.0 followed with a multipart upload endpoint for higher deployment throughput, automatic retries on transient server errors, and uv workspace support for local environment setup. It also fixed bundle deployment binding, immutable folders, and relative path resolution [18].

Several items used the name Declarative Automation Bundles next to the older DAB name [8][15][25]. One request asked for custom_tags and budget_policy_id support in presets [25]. Another asked for alert resources to load query_text from an external .sql file [12]. A video roundup also covered DAB changes alongside Lakeflow Jobs and Apps updates [17].

The community spent much of the month on Genie spaces. Practitioners asked how to link a bundle-managed Genie space to a dashboard across environments [5], how to handle table ordering in Genie spaces [20], and shared a write-up on deploying Genie spaces and agents to different environments [16]. Other threads covered CI/CD design. Topics included permissions a bundle cannot declare [14], managing Unity Catalog objects through GitHub Actions [4], monorepos and dependencies [2], and project structure [31]. An Azure DevOps walkthrough was also published [13].