Summary
The `ssh connect` command now supports a `--base-environment` flag for custom serverless session environments. Bundles received fixes for persistent drift on model serving endpoints and spurious updates when `apply_policy_default_values` is set on job tasks.
Summary generated by brickster.ai. For the full changelog and any code/binary attachments, follow the GitHub link above.
More from databricks/cli
The `workspace export-dir` command now sanitizes invalid filenames instead of aborting, and `ssh connect` defaults to a bash login shell starting in the user's workspace home. Bundles now print modern job run URLs, resolve `registered_model_id` references directly, and fix issues with `postgres_role` recreation and spurious cluster recreates.
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.
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 more Databricks resource types directly from the CLI. Databricks Bundles gain a --select flag for partial deployments, improved retry logic for transient errors, and support for Terraform references and Lakebase project hard-deletes.