Notable Changes
- Bundles still on Terraform state are now migrated to the direct engine automatically, after a deploy whose dry-run conversion comes back clean. To opt out, set
engine: terraformunderbundleorDATABRICKS_BUNDLE_ENGINE=terraform. See https://docs.databricks.com/aws/en/dev-tools/bundles/direct
CLI
- Fixed idle
databricks ssh connectsessions disconnecting after a few minutes, on dedicated clusters and on serverless. The tunnel now keeps itself warm: the SSH client and the SSH server on the compute exchange keepalives every 30 seconds, and the CLI's proxy pings the tunnel's websocket every 20 seconds. A session nobody is typing into stays connected, with no need to setServerAliveIntervalby hand.
Bundles
bundle planno longer reports a permanent, unconvergeable update onsecurable_kindfor Unity CatalogTABLEsecurables declared under an app'sresources. The field is computed by the backend (output-only), so it is now ignored during drift detection. Direct engine only (#6342).- Add support for the
cluster_policiesresource type in Declarative Automation Bundles. Cluster policies are only supported in direct deployment mode. bundle destroyno longer counts resources that are already gone remotely in itsDestroy: N deletedsummary. Such deletes only clean up stale state and are not listed under the deletion prompt, so they are now excluded from the count as well, matching the terraform engine.bundle destroynow also removes the directory named after the bundle, not just the target directory beneath it, whenworkspace.root_pathends in${bundle.name}/${bundle.target}— which includes the default root path. It is removed non-recursively, so it stays in place while another target of the same bundle is still deployed there. Previously every destroy left an empty directory behind (#6317).job_runsnow plans skip for a run that is still in progress and whenon_bundle_deployis removed, instead of treating either case as an update. (#6357)- Added
DATABRICKS_BUNDLE_RESOURCE_MAX_WAIT(in seconds) to cap how long deploy and destroy wait for a resource. Direct engine only. - Fixed
bundle deployon the direct engine failing withNothing to update, or reporting a change it never applied, when a schema, catalog, volume, registered model or external location field was removed from the configuration or set outside the bundle. The update now sends the fields the plan reports as cleared instead of dropping them.