Databricks CLI upgraded to version 1.11.0 alongside planned migrations for bundle engines.

Tooling updates in August focused on integrating Databricks CLI v1.11.0 into core developer environments [7]. The update enabled developers to launch SSH tunnels directly while extending Unity Catalog support to remote SSH sessions [7]. Alongside this integration, authentication boundaries received notable adjustments. In Databricks SDK v0.176.0, developers implemented new safeguards that prevented alternative credential strategies, specifically Databricks CLI authentication, from silently accessing normal-access credentials during OAuth machine-to-machine and workload identity federation role assumption flows [2].

Databricks Asset Bundles continued their transition away from the legacy Terraform backend. IDE tooling added explicit warnings whenever a bundle configuration continued to rely on the deprecated Terraform engine [3]. At the same time, community announcements detailed upcoming plans for Databricks CLI v1.14.0, which was scheduled to introduce automatic post-deployment migrations to the direct execution engine [4]. This transition aimed to simplify bundle deployment logic and eliminate external execution overhead across deployment pipelines.

Local development workflows connected to the CLI ecosystem also gained improvements in runtime consistency. Tooling introduced automated local Python virtual environment creation designed to mirror target cluster runtime versions and installed package dependencies [1, 6]. By configuring local virtual environments to match target clusters directly, the tooling addressed common configuration mismatches between local workstations and remote workspace execution [6].