Summary
SSH connection error messages are improved with server logs, and the GPU accelerator startup timeout is increased. Bundle deployments now correctly handle Unicode in variable references and prevent drift from backend schema normalizations.
Summary generated by brickster.ai. For the full changelog and any code/binary attachments, follow the GitHub link above.
More from databricks/cli
The `direct` deployment engine is now Generally Available and the default for new deployments, with existing deployments retaining their current engine. New CLI commands include `databricks quickstart` for an introduction and `databricks version --check` to report available updates.
* direct: Fix updating the apps after the Go SDK upgrade ([#5444](https://github.com/databricks/cli/pull/5444))
The experimental open command now supports opening a wider range of Databricks resource types directly in the workspace. Bundles gain a new --select flag for planning and deploying subsets of resources, improved retry logic for transient HTTP errors, and support for Terraform references.
Bundle users now receive a suggestion to set `bundle.engine: direct` in `databricks.yml` when using direct-only resources with the Terraform engine. Vector search indexes are now supported as a direct-engine bundle resource, including UC grants and destructive operation confirmations.
OAuth tokens for interactive logins are now stored in OS-native secure stores by default, requiring re-authentication after upgrading. A new `databricks aitools` command group is added for installing Databricks skills into coding agents.
The `vector_search_endpoints` configuration and commands now use `target_qps` instead of `min_qps`, requiring updates to `databricks.yml` and CLI invocations. Authentication commands received several usability improvements, including better keyring handling, clearer profile selection, and improved host input.