Skip to content

Update Databricks CLI to v1.27.0 - #2333

Merged
abdelrahmanomar1515 merged 3 commits into
mainfrom
update-cli-v1.27.0
Nov 20, 2026
Merged

abdelrahmanomar1515 merged 3 commits into
mainfrom
update-cli-v1.27.0

Conversation

@eng-dev-ecosystem-bot

Copy link
Copy Markdown
Collaborator

Update Databricks CLI to v1.27.0

@rugpanov

Copy link
Copy Markdown
Contributor

Executive summary — Databricks CLI v1.24.0 → v1.27.0

Notable

  • The CLI is now published on PyPI as databricks (uvx databricks, uv tool install databricks, pipx/pip install databricks). It replaces the legacy databricks-cli package. (#7704, #7777)
  • ⚠️ Breaking: the --refresh / --full-refresh flags of pipelines run and pipeline bundle run now take space-separated lists, not comma-separated ones. Names that contain spaces need backticks. file:<path> selectors are new. (#7184)
  • ⚠️ Behavior change: aitools install / update / uninstall exit with code 1 when they do nothing they were asked to do. (#7481)

CLI

  • AI tools (aitools)
    • New error_category values: MANIFEST_NOT_FOUND, PERMISSION_DENIED, FILESYSTEM, SKILLS_FETCH_FAILED, RELEASE_LOOKUP_FAILED, RATE_LIMITED, MANIFEST_INVALID, STATE_INVALID, PLUGIN_CLI_TIMEOUT. (#7380, #7475)
    • A new recovery field in --output json. (#7480)
    • Plugins install even when the skill files fail. (#7479)
    • Skills install for agents whose CLI is not on PATH. (#7482)
    • Only the Databricks marketplace is refreshed. (#7473)
    • A 20s capability-check timeout. (#7472)
    • Windows .cmd/.bat shims that exit with an error are now reported as shim-exited-with-error. (#7476)
    • Manifest path-traversal guard. (#7722)
    • No prompts when an agent runs the command, and no "Proceed?" step. (#7477, #7478, #7469)
    • The install directory is printed. (#7668)
    • New aitools auto-install disable|enable. A global-scope uninstall now also turns auto-install off. (#7701)
    • aitools commands now send telemetry. They can add about 3–6s on a slow or unreachable workspace. Opt out with DATABRICKS_CLI_DISABLE_TELEMETRY=1. (#7467, #7470)
    • Install hints now cover Codex, Cursor, Copilot CLI, Gemini and other agents. There is also a native Claude Code plugin hint. No hints print on auth, version, completion commands or CLI subprocesses. (#7586, #7585, #7692, #7452, #7471)
    • The telemetry wait during install is now bounded. (#7468)
  • New commands
    • sandbox fs (cp/ls/cat/mkdir/rm) and sandbox forward. (#7372, #7395)
    • databricks feedback. (#7724)
    • Beta pipelines test, plus the pipeline testing property in bundles. (#7429)
  • Reliability
    • fs and UC Volumes retry transient errors and timeouts. This fixes a regression from v1.10.0. (#7556, #7559)
    • The telemetry upload at exit is bounded. (#7467)
    • auth login stops the workspace lookup after about 5s. Before, it retried for about 5 min. (#7522)
    • No warning when the host-metadata request times out. (#7752)
  • Fixes
    • %pip in Jupyter over ssh connect on serverless v5/v6 and recent DBR. (#7263)
    • labs panics. (#7673)
    • fs completion. (#7679)
    • Prompts and pagers in MSYS2 / Git Bash. (#7699)
    • NO_COLOR no longer disables prompts. (#7700)
    • auth docker logout hint. (#7363)
  • AI Runtime (air)
    • About 50 changes across air run/list/get/logs/cancel/convert-to-dabs: richer JSON output, terminal-width layout, snapshot validation and PyTorch warnings.
    • CRITICAL removed from compute.priority_class. (#7371)
    • Behavior change: air logs now exits after it prints the current logs. Use --follow to stream. (#7658)

Bundles

  • New resources and fields
    • postgres_data_apis (Private Preview). (#7160)
    • feature_specs. (#7364)
    • catalogs.isolation_mode. (#7463)
    • lifecycle.depends_on on grants and permissions. (#7435)
    • Registered-model aliases are now applied on deploy. (#7163)
  • Templates and hosts
    • Built-in templates write ?w=<id> into workspace.host when the workspace ID is known. (#7350)
    • Templates get .workspace (Hostname/ID/URL) and .workspace.URLID. (#7349, #7388)
    • New DATABRICKS_BUNDLE_INIT_WORKSPACE_HOST_PROFILE. (#7410)
  • Validate and summary
    • --include-locations now includes variable declarations and value sources. (#7351)
    • An explicit false on optional booleans is kept. (#7412)
    • No warning when resource and top-level permissions name the same principal. (#7291)
  • Deploy correctness
    • Fixes for stale grants and permissions after a rename or recreate. (#7345, #7361)
    • App compute_size is no longer reset. (#7461)
    • Fixes for spurious drift on clusters and Lakeflow Connect. (#7577, #7603)
    • Drift detection for app source_code_path/git_source. (#6399)
    • Schema renames in place. (#7343, #7718)
    • Feature name casing. (#7398)
    • Immutable-sync bind. (#7329)
    • Serverless panic with local libraries. (#7725)
    • tgz+git artifacts. (#7674)
    • trigger_pause_status on triggers[]. (#7450)
    • "missing in state" recovery. (#7676)
    • pipelines dry-run no longer starts a real run when given a job key. (#7672)
  • Resilience
    • Retries for file uploads, the deploy lock, destroy and deletes. (#7521, #7594, #7597, #7708)
    • The direct engine reuses resources that were created even though the create request timed out: Lakebase, features, serving endpoints, dashboards, MCP and model services. (#7557, #7602, #7747, #7757, #7767, #7782)
    • App updates wait while the app compute is UPDATING. (#7606)
    • Recovery hint when an app's service principal is missing. (#7533)

Dependency updates

What could be integrated into the VS Code extension experience

🔴 Must fix in (or before) this bump

1. The partial pipeline refresh breaks: tables are joined with commas. Bug fix, small. (#7184)

  • picksToString joins the selected datasets with "," (packages/databricks-vscode/src/bundle/BundlePipelinesManager.ts:537-542).
  • deployAndRunSelectedTables passes that string as one argument after --refresh / --full-refresh (packages/databricks-vscode/src/ui/bundle-resource-explorer/BundleCommands.ts:288-291).
  • On v1.27.0, a selection of two or more tables reaches the CLI as a single comma-joined selector, so it no longer means "these N tables". This affects the "Run selected tables" action and the full-refresh confirmation flow.
  • Fix:
    • Join with " " and wrap names that contain spaces in backticks. CustomOutputTerminal.spawn calls child_process.spawn(cmd, args, options) without a shell (packages/databricks-vscode/src/bundle/run/CustomOutputTerminal.ts:40), so one space-joined argument reaches the CLI unchanged and needs no shell quoting.
    • Add a unit test for picksToString. No *.test.ts covers it now.
  • Keep the quick-pick's own comma parsing (stringToDatasets, BundlePipelinesManager.ts:544-549, placeholder at :378-379). It is a UI input format, not the CLI wire format.
  • A related limitation already exists: the free-form "run with args" path splits on " " (BundleCommands.ts:268). Users therefore cannot type a quoted multi-table --refresh "a b". This matters more now that the CLI expects spaces. You can fix it here (shell-style parsing) or later.

2. Check that bundle summary --include-locations still parses. Verification only. (#7351)

  • The extension runs bundle summary --include-locations (packages/databricks-vscode/src/cli/CliWrapper.ts:1084-1086).
  • It drops all locations unless __locations.version === 1 (packages/databricks-vscode/src/ui/bundle-resource-explorer/utils/SourceLocationUtils.ts:9-15).
  • v1.25.0 adds variable declarations and value sources to this output. Diff a v1.27.0 summary against v1.24.0 to confirm two things:
    • version is still 1.
    • The locations values for resources.* keep the [fileIdx, line, col] shape (SourceLocationUtils.ts:18-19).
  • If either changed, "go to source" in the Bundle Resource Explorer stops working with no error.

🟢 Low effort, existing plumbing

3. Show the new recovery hint when aitools install fails. Cleanup, small. (#7480)

  • AiToolsInstallOutput has no recovery field (packages/databricks-vscode/src/cli/CliWrapper.ts:272-278).
  • describeAiToolsInstallFailure builds the user-facing message from error plus each agent's message only (packages/databricks-vscode/src/aitools/aiToolsInstallOutput.ts:16-33). AiToolsManager appends that message to the error (packages/databricks-vscode/src/aitools/AiToolsManager.ts:636-647).
  • Add the field and append it to the message. Keep it out of telemetry, like message.

4. Honor VS Code's telemetry setting for aitools calls. Flag-flip on existing plumbing. (#7467)

  • aitools commands now send CLI telemetry. On a slow or unreachable workspace, list can take up to about 3s longer and install/update/uninstall up to about 6s longer.
  • The extension runs aitools list from AiToolsManager.initialize() (AiToolsManager.ts:323-340, via :450 / :487). It also runs install, update and uninstall.
  • aitoolsEnv() sets no opt-out (packages/databricks-vscode/src/cli/CliWrapper.ts:816-827).
  • The extension already exposes the user's choice as Telemetry.isTelemetryEnabled (packages/databricks-vscode/src/telemetry/index.ts:131-133). Set DATABRICKS_CLI_DISABLE_TELEMETRY=1 in aitoolsEnv() when that is false.

5. aitools exit-code and auto-install changes. Mostly no-op. One UX note.

  • #7481 exit codes:
    • aitoolsInstall always passes --agents (CliWrapper.ts:860-869), and a skipped agent is already fatal there (see the note at AiToolsManager.test.ts:537).
    • aitoolsUpdate and aitoolsUninstall already turn any non-zero exit into a ProcessError (CliWrapper.ts:907-921, :932-946).
    • Result: a run that does nothing now shows as a failure. This includes the silent update path. Expect AITOOLS_UPDATE / AITOOLS_UNINSTALL success:false counts to rise a little.
  • New error_category values: no-op. summarizeAiToolsInstallErrors passes the categories through unchanged (aiToolsInstallOutput.ts:41-61), so telemetry picks them up with no code change.
  • #7701: databricks.aitools.uninstall at global scope now also turns off CLI auto-install. Consider saying so in the uninstall confirmation.
  • No-ops: #7469, #7472, #7473, #7474, #7476, #7477, #7478, #7479, #7482, #7668, #7722. The extension runs non-interactively with --output json and closeStdin (CliWrapper.ts:870-876), and already handles delivery: "skills" (CliWrapper.ts:241).

6. Bundle schema and Resource Explorer support for the new resources. Mostly automatic. Optional cleanup.

  • YAML completion: automatic. bundleAutocompleteProvider reads databricks bundle schema from the bundled binary at runtime (packages/databricks-vscode/src/bundle/bundleAutocompleteProvider.ts:13, CliWrapper.ts:802-808). postgres_data_apis, feature_specs, catalogs.isolation_mode and pipeline testing therefore complete with no change.
  • Resource Explorer: already shown, generic icon. Types outside KNOWN_RESOURCE_TYPES (packages/databricks-vscode/src/ui/bundle-resource-explorer/types.ts:36-39) render through UnknownResourceTreeNode.getRootGroups (ResourceTypeHeaderTreeNode.ts:124-128). New types get the generic icon unless you add them to KNOWN_ICON_RESOURCE_TYPES (types.ts:40-52).
  • Optional cleanup: regenerate the typed BundleSchema.ts with yarn workspace databricks run package:bundle-schema:write (packages/databricks-vscode/package.json:1994). Only typed accesses need this.

🟡 Medium effort, net-new on existing plumbing

7. Use the workspace ID in workspace.host (?w=<id>) to pick the right profile. Net-new, small to medium. (#7350, #7349, #7388)

  • The extension's bundle init passes authProvider.toEnv(), which includes DATABRICKS_WORKSPACE_ID when known (packages/databricks-vscode/src/configuration/auth/AuthProvider.ts:256-265; init env at CliWrapper.ts:1110-1121). Projects created through the wizard on a shared host will now contain host: https://…?w=<id>.
  • normalizeHost drops the query string (packages/databricks-vscode/src/utils/urlUtils.ts:34). All bundle-host matching compares hostnames only:
    • LoginWizard.ts:139
    • ConfigModel.ts:365
    • RemoteTargetHostManager.ts:143
    • ConnectionManager.ts:450
  • So this is not a regression. On a host that several workspaces share, though, the profile picker lists every profile on that hostname, not the one that matches ?w=.
  • The login path already writes ?w= (DatabricksCliCheck.ts:142-144). Reading w/o when the extension resolves the bundle host and filtering profiles by workspaceId would complete the loop.

8. "Refresh this file's datasets" from the editor. Net-new, medium. (#7184)

  • Pipeline bundle run now accepts file:<path> selectors.
  • The existing plumbing covers most of the work:
    • deployAndRun and the bundle run arg builder (CliWrapper.ts:1363-1371).
    • __locations, which can map a source file to its pipeline key (SourceLocationUtils.ts).
    • The current partial-refresh flow (BundleCommands.ts:277-294).
  • New work: an editor or explorer context-menu command and the file-to-pipeline resolution. Depends on fix Run tests on PRs #1.

9. Go to definition for bundle variables. Net-new, medium. (#7351)

  • bundle summary --include-locations now reports where each variable is declared and where its resolved value comes from.
  • The variables view builds its state from the pre-validate and validate configs (packages/databricks-vscode/src/bundle/models/BundleVariableModel.ts:163-213) and has no source links today.
  • The location parsing already exists (SourceLocationUtils.ts), but variable keys are not yet read. Confirm the exact key format in v1.27.0 output first (see Add contribution instructions #2).

🔵 Larger, net-new feature work

10. A pipelines test integration (Beta). Net-new, large. (#7429)

  • The extension has no test runner for pipelines. It would need a new command and a way to show results, for example in the VS Code Test Explorer or the pipeline tree.
  • The testing YAML property gets completion automatically (Integrate with lgtm.com #6). Given the Beta status, this can wait.

No-ops / transparent for the extension

  • AI Runtime (air …): the extension never invokes air. No code references it.
  • sandbox fs / sandbox forward, databricks feedback, labs fixes, auth docker: the extension does not invoke these.
  • fs and Volumes retries (#7556, #7559): the extension does not call databricks fs; it syncs through sync (cli/SyncTasks.ts). Bundle uploads to Volumes benefit for free.
  • Bundle deploy, plan and destroy fixes and retries: free improvements to the extension's deploy, destroy and plan flows. Nothing to change.
  • pipelines dry-run fix (#7672): the extension validates with bundle run --validate-only (BundleCommands.ts:274), not dry-run.
  • Explicit false booleans (#7412): BundleVariableModel does not read sensitive or the other affected fields.
  • auth login 5s lookup cap (#7522): the extension passes ?w=<id> when it knows the ID (DatabricksCliCheck.ts:142-144) and always passes --timeout (:152). Only faster.
  • Host-metadata timeout warning removed (#7752): less stderr noise in the bundle output channel.
  • ssh connect %pip fix (#7263): the extension uses ssh connect (CliWrapper.ts:156). Users get the fix with no change.
  • Agent install hints (#7585, #7586, #7692, #7452, #7471): the hints go to stderr, and the CLI suppresses them for subprocesses. The extension reads structured output from stdout.
  • NO_COLOR, MSYS2/ConPTY: terminal-only changes.
  • PyPI distribution (#7704):
    • The extension always runs its absolute cliPath, so its own calls are unaffected.
    • In integrated terminals the bundled bin/ is appended to PATH (packages/databricks-vscode/src/extension.ts:787-790). A pip/uv-installed databricks in an active venv therefore shadows the bundled CLI there. The legacy package already did this, but a modern PyPI CLI makes a version mismatch more likely and harder to notice.
    • No code change is needed. A docs note may help.
  • Go SDK, Go toolchain and vulnerability bumps: no-op. The extension uses the JS SDK. The go-runewidth change (#7391) saves about 30ms on every CLI spawn the extension makes.

🤖 Auto-generated executive summary of the CLI v1.24.0 → v1.27.0 changelog. Integration notes are opportunities, not commitments — verify before acting.

@github-actions

Copy link
Copy Markdown
Contributor

If integration tests don't run automatically, an authorized user can run them manually by following the instructions below:

Trigger:
go/deco-tests-run/vscode

Inputs:

  • PR number: 2333
  • Commit SHA: 18bb9858b30fb5abe23e837599e882a0745588c5

Checks will be approved automatically on success.

@abdelrahmanomar1515 abdelrahmanomar1515 left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Reviewed the bundled CLI upgrade from 1.24.0 to 1.27.0. The original bump broke multi-table pipeline refresh. I pushed the compatibility fix in 18bb985 and verified that CLI 1.27 accepts the arguments for both refresh modes. All seven focused tests passed on the repository’s pinned VS Code 1.138.0. The build and lint passed locally.


This review was generated with GitHub MCP.

@rugpanov

Copy link
Copy Markdown
Contributor

Executive summary — Databricks CLI v1.24.0 → v1.27.0

⚠️ Breaking change for the extension: in v1.27.0, bundle run / pipelines run changed --refresh and --full-refresh from comma-separated lists to space-separated lists (#7184). The extension still sends commas. See item 1 below.

CLI

  • Distribution: the CLI is now on PyPI as databricks (uvx databricks, pipx install databricks, …). The package contains only the prebuilt binary (#7704, #7777).
  • New commands:
    • sandbox fs (cp/ls/cat/mkdir/rm) (#7372) and sandbox forward (#7395).
    • feedback (#7724).
    • Beta pipelines test, plus the pipeline testing property in bundles (#7429).
    • aitools auto-install disable|enable (#7701).
  • Pipelines: pipelines run and pipeline bundle run accept file:<path> selectors. --refresh/--full-refresh now take space-separated lists. Names that contain spaces need backticks (#7184).
  • aitools behavior changes:
    • install/update/uninstall now exit 1 when they do nothing (#7481).
    • A global-scope uninstall also turns off auto-install (#7701).
    • New error_category values: MANIFEST_NOT_FOUND, PERMISSION_DENIED, FILESYSTEM, SKILLS_FETCH_FAILED, RELEASE_LOOKUP_FAILED, RATE_LIMITED, MANIFEST_INVALID, STATE_INVALID, PLUGIN_CLI_TIMEOUT (#7380, #7475).
    • A new recovery field in --output json (#7480).
    • Plugins still install when skill files fail (#7479).
    • The plugin capability check now waits 20s instead of 5s (#7472).
    • aitools commands now send usage telemetry and can take up to ~6s longer on an unreachable workspace (#7467).
    • Many smaller fixes to aitools prompts and hints (#7469, #7473, #7474, #7476–#7478, #7482, #7586, #7585, #7692, #7722).
  • Reliability:
    • fs retries reads and deletes on DBFS/Volumes (#7556).
    • Volumes operations retry on 408/429/5xx again, fixing a regression from v1.10.0 (#7559).
    • The exit-time telemetry upload is now bounded by its timeout (#7467).
    • The /.well-known/databricks-config timeout no longer prints a warning (#7752).
  • Auth: the optional workspace lookup in auth login now stops after ~5s, down from ~5min (#7522). auth docker suggests logout --delete when several profiles match the same workspace (#7363).
  • Misc:
    • %pip works in Jupyter over ssh connect on serverless env 5/6 and recent DBR (#7263).
    • MSYS2/Git Bash prompts work under ConPTY (#7699).
    • NO_COLOR no longer turns off prompts (#7700).
    • Fixed labs panics (#7673) and fs completion (#7679).
    • Startup is ~30ms faster (#7391).
  • AI Runtime (air): a large batch of changes across #7368–#7744, with richer air get/air list JSON and TUI fixes. One behavior change: air logs now exits by default, so pass -f to stream (#7658). CRITICAL priority is removed (#7371).

Bundles

  • New resources and fields:
    • postgres_data_apis (Private Preview) (#7160).
    • feature_specs with UC grants (#7364).
    • Catalog isolation_mode (#7463).
    • lifecycle.depends_on can target *.grants / *.permissions (#7435).
    • Registered model aliases are now applied (#7163).
  • Introspection:
    • The --include-locations output of bundle validate/bundle summary now includes variable declarations and the source of each resolved value (#7351).
    • An explicit false on optional booleans is no longer dropped from validate -o json (#7412).
  • Templates / workspace routing:
    • Built-in templates add ?w=<id> to workspace.host (#7350).
    • New .workspace / .workspace.URLID template data (#7349, #7388).
    • New DATABRICKS_BUNDLE_INIT_WORKSPACE_HOST_PROFILE env var (#7410).
  • Plan/drift fixes:
    • Grants and permissions of renamed or recreated resources are no longer re-applied (#7345, #7361).
    • No more false drift for single-node cluster spark_conf/custom_tags (#7577) or Lakeflow Connect staging options (#7603).
    • Drift detection for app source_code_path/git_source (#6399).
    • Schemas are renamed in place (#7343, #7718).
    • A deploy no longer resets app compute_size (#7461).
  • Deploy resilience:
    • Retries for uploads, the deploy lock, destroy, and direct-engine deletes (#7521, #7594, #7597, #7708).
    • Direct-engine recovery of resources whose create call timed out but still succeeded (#7602, #7747, #7757, #7767, #7782).
    • App updates retry while compute is UPDATING (#7606).
  • Bug fixes:
    • Serverless + local libraries panic (#7725).
    • tgz+git artifacts in subdirectories (#7674).
    • bind with sync_mode: immutable (#7329).
    • Empty-ID state entries (#7676).
    • pipelines dry-run starting a real run (#7672).
    • Uppercase feature names (#7398).
    • trigger_pause_status now applies to triggers[] (#7450).

Dependency updates

What could be integrated into the VS Code extension experience

Must handle in (or alongside) this bump

  1. Fix the partial pipeline refresh argument format. Cleanup / bug fix, small.

    • picksToString joins the selected datasets with commas: .join(",") at packages/databricks-vscode/src/bundle/BundlePipelinesManager.ts:541.
    • deployAndRunSelectedTables passes that string as one argument after --refresh / --full-refresh (src/ui/bundle-resource-explorer/BundleCommands.ts:287-292), and that ends up in bundle run --target <t> <key> … (src/cli/CliWrapper.ts:1364-1371).
    • After #7184, a selection of two or more tables gets a comma list where the CLI now expects spaces, so "Run selected tables" will probably target the wrong selection or fail. The full-refresh variant has the same problem.
    • Fix: join with " " and wrap any name that contains a space in backticks.
    • The user-facing quick pick can keep accepting comma input (BundlePipelinesManager.ts:379, parsed by stringToDatasets at :544-547). Only the CLI encoding needs to change.
    • There are no unit tests for this path today, so add one next to the fix.
    • We could not run the new binary here (bin/ is not fetched), so please confirm with a manual two-table run.
    • Related: the free-form "run with arguments" path splits user input on spaces (BundleCommands.ts:268), so quoted or backticked names typed there will still break. This is a pre-existing limitation that is now more visible.
  2. Check that __locations still parses after #7351. Verification; cleanup if it fails.

    • The extension already calls bundle summary --include-locations (src/cli/CliWrapper.ts:1083-1091).
    • It types __locations as {version, files, locations} (src/bundle/models/BundleRemoteStateModel.ts:32-38).
    • getSourceLocation returns nothing unless version === 1, and it looks up resources.<key> (src/ui/bundle-resource-explorer/utils/SourceLocationUtils.ts:10-18).
    • If the new variable data changed the version or the shape, "Go to source" on jobs, pipelines and tasks would stop working without any error. Quick check: run "Go to source" from the resource explorer on the new binary.
  3. AI tools: re-check error and exit-code handling. Mostly transparent; small cleanup.

    • Exit code 1 on "nothing done" (#7481):
      • aitoolsInstall already handles a non-zero exit with a JSON result (src/cli/CliWrapper.ts:877-890). runInstallCli turns it into an error toast and an error telemetry result (src/aitools/AiToolsManager.ts:615-648).
      • The extension never calls the CLI with an empty agent list (CliWrapper.ts:856-858).
      • The change is that "every requested agent skipped" now shows as an error instead of a silent success. The same applies to an all-failed update/uninstall, which throw at CliWrapper.ts:916-919 / :941-944.
      • Expect a step change in the AITOOLS_INSTALL/AITOOLS_UPDATE success rate after this bump. It is not a regression.
    • New error_category tokens: they pass straight through to telemetry with no allowlist (src/aitools/aiToolsInstallOutput.ts:43-60), so no code change is needed. Optionally, update the examples in the globalErrorCategory comment (src/telemetry/constants.ts:417-420).
    • Global uninstall now also turns off auto-install (#7701). The confirmation dialog says only Uninstall Databricks AI tools (${location})? (src/aitools/AiToolsCommands.ts:510-514). Consider adding that side effect to the text when location === "global". This is a copy change.

Low effort, existing plumbing

  1. Show the CLI's recovery hint when an AI tools install fails (#7480). Small, uses existing plumbing.

    • Add recovery?: string to AiToolsInstallOutput (src/cli/CliWrapper.ts:272-278).
    • Accept it in parseAiToolsInstallOutput.
    • Append it in describeAiToolsInstallFailure (src/aitools/aiToolsInstallOutput.ts:16-33). That string is already added to the toast message (AiToolsManager.ts:636-643).
    • Like message, keep it out of telemetry.
  2. Regenerate the static bundle schema typings. Cleanup, one command.

    • YAML autocomplete already uses the bundled binary's live bundle schema (src/bundle/bundleAutocompleteProvider.ts:13, src/cli/CliWrapper.ts:802-808). This means feature_specs, postgres_data_apis, catalog isolation_mode and pipeline testing complete without code changes.
    • The checked-in src/bundle/BundleSchema.ts has none of them (0 matches). Run yarn workspace databricks run package:bundle-schema:write (package.json:1994) in this PR so the TS types match.

Transparent wins (no action needed)

  • New resource types (feature_specs, postgres_data_apis) show in the resource explorer through the generic UnknownResourceTreeNode grouping (src/ui/bundle-resource-explorer/UnknownResourceTreeNode.ts:72-95). Only jobs/pipelines have dedicated nodes (ResourceTypeHeaderTreeNode.ts:25-27).
  • Workspace-ID-aware templates (#7349, #7350, #7388):
    • The init wizard runs bundle init with getBundleInitEnvVars (src/bundle/BundleInitWizard.ts:189,199-204; src/cli/CliWrapper.ts:1111-1121).
    • That includes authProvider.toEnv(), which sets DATABRICKS_CONFIG_PROFILE and, when known, DATABRICKS_WORKSPACE_ID (src/configuration/auth/AuthProvider.ts:256-262).
    • As a result, projects created on SPOG hosts get ?w=<id> automatically.
    • DATABRICKS_BUNDLE_INIT_WORKSPACE_HOST_PROFILE (#7410) is not needed.
  • auth login 5s lookup cap (#7522): the re-login flow already sends ?w=<id> when it knows the ID (src/configuration/auth/DatabricksCliCheck.ts:139-146). The cap only shortens the case where the ID is unknown.
  • %pip over ssh connect (#7263): helps users of the extension's SSH flow (src/cli/CliWrapper.ts:156). No change is needed.
  • Deploy, plan and drift fixes, plus upload, lock and destroy retries: all inside bundle deploy/destroy/summary, which the extension shells out to. Users just see fewer spurious failures. The validate -o json false-boolean fix (#7412) does not affect any field the extension reads.
  • Other no-ops for the extension:
    • All air changes.
    • sandbox fs/sandbox forward, feedback, labs fixes, fs retries and completion (the extension has no fs calls).
    • The PyPI distribution.
    • MSYS2/ConPTY, NO_COLOR, the well-known-config warning.
    • The template-only additions.
    • aitools install text-output changes: the extension uses --output json with stdin closed (CliWrapper.ts:859-876).
    • The Go SDK and toolchain bumps.
  • Small thing to check: #7586 adds install hints when Cursor or Copilot CLI run the CLI. Bundle stderr goes to the output channel at error level (CliWrapper.ts:1065-1067). A quick check in Cursor would confirm that the new hint does not show there.

Net-new feature work this unlocks (larger)

  1. "Refresh tables in this file" for pipelines (#7184 file:<path> selectors). Net-new, medium.

    • Today the table picker offers dataset names only (BundlePipelinesManager.ts:372-430).
    • We could add an editor/explorer context action on a pipeline source file that runs bundle run <pipeline> --refresh "file:<path>".
    • It would reuse deployAndRun (BundleCommands.ts:287) and the existing run-status plumbing.
    • The new part is mapping a file to its pipeline.
  2. Variable "go to definition" and value provenance in the Bundle Variables view (#7351). Net-new, medium.

    • VariableTreeNode shows only the target and default values, with no command or location (src/ui/bundle-variables/VariableTreeNode.ts:42-62).
    • BundleVariableModel builds its state from pre-validate and validate config, not from __locations (src/bundle/models/BundleVariableModel.ts:163-175).
    • The source locations already come back from bundle summary --include-locations and the parsing utilities exist (SourceLocationUtils.ts). This work would extend the __locations type, pass it into the variable model, and add an "Open declaration" command plus a "value from: target / override / env" description.
  3. Pipeline tests (Beta) from the resource explorer (#7429 pipelines test + testing property). Net-new, medium to large.

    • Autocomplete for testing is free (item 5).
    • A "Run pipeline tests" action on PipelineTreeNode would need a new CLI wrapper, output parsing, and probably Test Explorer integration.
    • The command is Beta, so it is reasonable to wait for the output format to settle.
  4. AI tools auto-install toggle (#7701 aitools auto-install disable|enable). Net-new, small, optional.

    • The extension already persists databricks.aitools.hideInstallPrompt (src/vscode-objs/StateStorage.ts:123) and owns the install flow.
    • A toggle in the AI tools section of the configuration view could call the new subcommand.
    • This is only useful if bundled-CLI upgrades actually trigger the CLI's own auto-install, so check that first.

🤖 Auto-generated executive summary of the CLI v1.24.0 → v1.27.0 changelog. Integration notes are opportunities, not commitments — verify before acting.

@abdelrahmanomar1515
abdelrahmanomar1515 merged commit 286b4e9 into main Nov 20, 2026
10 checks passed
@github-actions github-actions Bot mentioned this pull request Nov 20, 2026
abdelrahmanomar1515 added a commit that referenced this pull request Nov 20, 2026
## packages/databricks-vscode
##  (2026-11-20)

* Handle GitHub Copilot detected only through VS Code's copilot shim
(#2295)
([5e677a5](5e677a5)),
closes
[#2295](#2295)
* Invite signed-in users to try the version 3 pre-release, once (#2331)
([5fc60f8](5fc60f8)),
closes
[#2331](#2331)
* Update Databricks CLI to v1.27.0 (#2333)
([286b4e9](286b4e9)),
closes
[#2333](#2333)



## packages/databricks-vscode-types
##  (2026-11-20)

---------

Co-authored-by: releasebot <noreply@github.com>
Co-authored-by: Abdurrahman Abdulaziz <abdelrahman_omar_1515@yahoo.com>

This branch was successfully deployed

1 active deployment
test-trigger-is — 18bb9858 Deployed Nov 20, 2026 by abdelrahmanomar1515 via Trigger Tests #2585
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants