Repository navigation
Release: v3.1.0
Pre-release
Pre-release
packages/databricks-vscode
The first pre-release of version 3. These notes compare it with version 2.23.1. Your bundle projects and profiles carry over, and so do your settings, apart from the ones listed under "Changed or removed". Version 3 is on the VS Code Marketplace only for now, so Cursor and other editors that install from Open VSX get version 2. A Databricks remote session installs version 2 in its remote window. To go back to version 2, open Databricks in the Extensions view and choose "Switch to Release Version".
New
- A Connection view at the top of the Databricks sidebar shows the window's workspace connection and its Unity Gateway connection, each with its profile, host, workspace and user.
- Unity Gateway models in VS Code Chat, under "Databricks", once you sign in with "Databricks: Sign in to Unity Gateway". Unity Gateway has a sign-in of its own, which can be another workspace than your project's. In 2.23.1 it was behind the
chat.unityGatewayexperiment. It isn't available in Cursor or in a Databricks remote session. - A Models & AI tools view shows how many models Unity Gateway offers, where they come from, and the AI tools, with or without a folder open. Clicking the Models row opens Chat's model picker.
- Unified hosts (one URL for an account and its workspaces): the sign-in wizard asks for the workspace before the browser opens, and a profile that is signed in to the account but names no workspace shows a "Select a workspace" button. The wizard doesn't offer a personal access token there, because the CLI can't save a workspace for one.
- When the window is connected to a workspace, "Create a new Databricks project" asks only for the parent folder, and the new project uses that workspace's profile.
- The Python, Python Debugger, Jupyter and YAML extensions are an extension pack: installed with Databricks, and started only when a feature needs one.
Fixed
- A Databricks config file the extension creates is readable only by you.
- On Windows, non-ASCII text in the project's environment file and in notebooks run with
%runreaches Python as written.
Changed or removed
- Version 3 needs VS Code 1.128 or later. On an older VS Code, you stay on version 2.
- The Configuration view is now called Project. Signing in moved to the Connection view above it, and the AI tools rows to Models & AI tools. The Project view no longer has an "Auth Type" row or "Copy Auth Type": the Connection view's workspace row names the profile.
- The Bundle Resource Explorer view is now a Resources group in the Project view.
- The Bundle Variables view is now a Variables group in the Project view, with Override and Reset on its row.
- The Quick Start guide is now a walkthrough, "Get started with Databricks", which VS Code opens on install, instead of a Markdown page.
- The Documentation view is gone: its guides are in the Get started walkthrough, and the bundles guide is also linked from the Project view when no folder is open.
- The "Databricks Connect enabled" or "disabled" status bar item is gone. The Python environment rows in the Project view show the same state.
- "Databricks: Logout" is now "Databricks: Sign out".
- The first sign-in on a machine with no profiles saves its profile without asking for a name: as the bundle target's
workspace.profilewhen the target sets a valid one, otherwise asDEFAULT. The bundle target's own name is no longer used for it. The CLI usesDEFAULTfordatabrickscommands in a terminal unlessDATABRICKS_CONFIG_PROFILEorDATABRICKS_HOSTis set or the config file names another default profile, so those commands now use aDEFAULTprofile by default. - With no compute chosen for a target, and no cluster named in its bundle, runs and Databricks Connect use serverless compute, instead of asking for one. "Upload and Run File" needs a cluster, so it's hidden until one is attached.
- Before a setup has run, the "Select compute", "Set up Python environment" and "Attach a cluster" rows are no longer red.
- Code run with Databricks Connect, and notebook kernels, no longer see
ARM_CLIENT_ID,ARM_CLIENT_SECRET,ARM_TENANT_ID,ARM_USE_MSIorGOOGLE_CREDENTIALSfrom VS Code's environment, outside a Databricks remote session: the Databricks SDK there signs in with the project's profile. If your code needs them, set them inpython.envFileand give the profile an explicitauth_type. - The
databricks.logs.*settings are gone. Set the level of the "Databricks Logs" output with "Developer: Set Log Level...". - Migrating a
project.jsonproject to a bundle is no longer offered. To migrate one, open it with version 2.23 first.