Bump databricks-sdk-go from v0.182.0 to v0.185.0 by janniklasrose · Pull Request #6928 · databricks/cli

janniklasrose · 2026-10-05T14:21:51Z

Changes

Bump github.com/databricks/databricks-sdk-go from v0.182.0 to v0.185.0.

New mason workspace and private-network-gateways account command groups.
New job environment_variables and on_maintenance_start / on_maintenance_complete notifications; new pipeline transformer Avro/Protobuf options and TikTok Ads/Smartsheet ingestion; surfaced in the JSON schema and PyDABs models.
jobs.DeploymentSpec.command_path and ml.SchemaRegistryConfig.api_secret_ref are no longer required.
cligen: drop the deprecated limit alias for mason search-memories so only one --page-size flag is registered (the duplicate flag panicked at startup).
Suppress new SA1019 warnings for the now-deprecated pipeline development field, which remains a supported bundle config field.
Override the plain command_path and gcp_availability descriptions so the PyDABs Sphinx docs stay valid RST (the spec descriptions use Markdown).

Why

Routine SDK update. The pinned OpenAPI spec SHA moves with it (4648d66f → 841910972e) and downstream artifacts are regenerated.

Tests

Regenerated downstream artifacts (cli.json, command stubs, schema, validation, direct-engine YAML, refschema, TF map, PyDABs). Acceptance goldens regenerated and the full suite passes under both engines; the root-module unit suite (11677 tests), full lint, task checks, and the PyDABs test/lint/docs suite all pass.

This pull request and its description were written by Isaac.

## Changes Bump `github.com/databricks/databricks-sdk-go` from v0.182.0 to v0.185.0. - New `mason` workspace and `private-network-gateways` account command groups. - New job `environment_variables` and `on_maintenance_start` / `on_maintenance_complete` notifications; new pipeline `transformer` Avro/Protobuf options and TikTok Ads/Smartsheet ingestion; surfaced in the JSON schema and PyDABs models. - `jobs.DeploymentSpec.command_path` and `ml.SchemaRegistryConfig.api_secret_ref` are no longer required. - cligen: drop the deprecated `limit` alias for `mason search-memories` so only one `--page-size` flag is registered (the duplicate flag panicked at startup). - Suppress new SA1019 warnings for the now-deprecated pipeline `development` field, which remains a supported bundle config field. - Override the plain `command_path` and `gcp_availability` descriptions so the PyDABs Sphinx docs stay valid RST (the spec descriptions use Markdown). ## Why Routine SDK update. The pinned OpenAPI spec SHA moves with it (4648d66f -> 841910972e) and downstream artifacts are regenerated. ## Tests Regenerated downstream artifacts (cli.json, command stubs, schema, validation, direct-engine YAML, refschema, TF map, PyDABs). Acceptance goldens regenerated and the full suite passes under both engines; the root-module unit suite (11677 tests), full lint (pinned go1.26.8), `task checks`, and the PyDABs test/lint/docs suite all pass. Co-authored-by: Isaac <no-reply@databricks.com>

Co-authored-by: Isaac <no-reply@databricks.com>

The two upstream descriptions that aren't valid reStructuredText -- jobs.DeploymentSpec.command_path (a Markdown code fence) and compute.InstancePoolGcpAttributes.gcp_availability (an unindented bullet continuation) -- were patched in bundle/internal/schema/annotations.yml, which also changed the bundle JSON schema's plain descriptions. Move them to the existing python/codegen jsonschema_patch burn-down list, extended with a field-level FIELD_DESCRIPTIONS counterpart to DESCRIPTIONS, so annotations.yml and jsonschema.json keep the upstream text and only the generated PyDABs docstrings are patched for the Sphinx docs build. Co-authored-by: Isaac <no-reply@databricks.com>

janniklasrose · 2026-10-05T14:32:47Z

 		Description:          config.Description,
 		EditMode:             config.EditMode,
 		EmailNotifications:   config.EmailNotifications,
+		EnvironmentVariables: config.EnvironmentVariables,


hand-edited due to exhauststruct

generate-validation runs gofmt; go1.27's gofmt breaks the map-literal alignment group for two short pipeline enum keys that sit under a very long sibling key, while the pinned go1.26.8 (CI) keeps them aligned. Regenerated under go1.26.8 so the committed file matches what the validate-generated CI job produces. Co-authored-by: Isaac <no-reply@databricks.com>

eng-dev-ecosystem-bot · 2026-10-05T15:18:53Z

Integration test report

Commit: a7d2f5e

Run: 37333591438

	Env	✅pass	🙈skip	Time
✅	aws linux	276	19	3:33
✅	aws windows	278	17	2:53
✅	azure linux	275	19	3:35
✅	azure windows	277	17	3:22
✅	gcp linux	276	19	3:35
✅	gcp windows	278	17	3:09

janniklasrose · 2026-10-05T15:14:18Z

 # that docutils rejects as malformed. Rewritten as a list-table.
 # See sqlgateway/scheduler/api/proto/endpoint_common.proto.
 DESCRIPTIONS: dict[str, str] = {
    "sql.SpotInstancePolicy": (


@Sankalp-Mittal can we remove this now?

yes the PR fixing this was merged 2 weeks ago

Per review: rather than hand-maintaining an RST copy of upstream descriptions we can't render, drop the description for jobs.DeploymentSpec.command_path and compute.InstancePoolGcpAttributes.gcp_availability in the pydabs codegen patch layer (DROP_FIELD_DESCRIPTIONS / drop_field_descriptions). The fields keep their types; only the broken docstrings are omitted so the Sphinx docs build. annotations.yml and jsonschema.json keep the upstream text. Co-authored-by: Isaac <no-reply@databricks.com>

janniklasrose · 2026-10-05T15:33:40Z

+# docutils parses as an unterminated inline literal.
+# compute.InstancePoolGcpAttributes.gcp_availability: the final bullet wraps onto
+# an unindented continuation line, which docutils rejects as an unexpected unindent.
+DROP_FIELD_DESCRIPTIONS: dict[str, list[str]] = {


hand-edited, needs agent guidance to update jsonschema_patch when pydabs docgen fails on certain fields

…atabricks#6946) ## Changes New dev/test-only env var `DATABRICKS_LITESWAP_TARGET`. When it is set, every request from workspace, account, and bundle clients carries `x-databricks-traffic-id: testenv://liteswap/<target>`, which routes it to that LiteSwap pre-prod unit. - `libs/liteswap`: `Apply(ctx, cfg)` sets `cfg.Headers` (SDK hook from databricks/databricks-sdk-go#1846, available since databricks#6928) when the env var is set. - Called where the CLI builds its configs: `MustAccountClient`, `MustWorkspaceClient`, and `bundle/config/workspace.go`. Clients built from `w.Config` for raw calls (DMS, filer, AIR, pipelines, telemetry, ...) pick the header up from these. ## Why Developers testing a service on a LiteSwap unit need CLI traffic routed there. The header format matches the existing hidden SSH `--liteswap` flag. Out of scope for now: `databricks api` (builds its own config) and the SSH flag, which could later move to this mechanism. No changelog entry, since this is dev/test only. ## Tests New acceptance test `acceptance/cmd/liteswap-target` records request headers for a workspace command, an account command, and `bundle validate`, and checks the header is absent when the env var is unset. This pull request and its description were written by Isaac. Co-authored-by: Isaac <no-reply@databricks.com>

## Release v1.20.0 ### Notable Changes * Remove the Terraform deployment engine. `bundle.engine: terraform` and `DATABRICKS_BUNDLE_ENGINE=terraform` now error, and a failed migration of existing Terraform state is reported as an error instead of falling back to Terraform. To keep deploying with Terraform, use Databricks CLI v1.19.x. ([#6888](#6888), [#6889](#6889)) ### CLI * `databricks aitools install` now supports Kiro, installing Databricks agent skills into its skills directory. ([#6908](#6908)) * Fixed `databricks api` corrupting integers larger than 2^53 (such as job and pipeline ids) — request bodies and responses now preserve them exactly. ([#6884](#6884)) * Added `--auth-mode` and `--set <plugin>.<resourceKey>.authMode=obo|sp|both` to `databricks apps init` so AppKit resources can be accessed on behalf of the user, by the service principal, or both. The default stays service principal. ([#6886](#6886)) * `databricks apps init` now requires a value for every field a service principal resource binding references, prompting for missing values in an interactive terminal and otherwise failing with the `--set` key to use, instead of creating a project with unset variables. ([#6903](#6903)) * Add `databricks apps init --package-manager <npm|pnpm>` to select the package manager for Node.js templates. Infer the default quietly from template lockfiles and AppKit version, check prerequisites before creating files, and preserve template formatting and pnpm version pins. ([#6902](#6902)) * Select npm or pnpm from `packageManager` declarations and lockfiles for `apps validate` and project validation during `apps deploy`. ([#6892](#6892)) * Fix `auth docker host` reporting the credential helper as configured when its executable is missing from `PATH`. ([#6880](#6880)) * Warn when the CLI binary was built more than 6 months ago and recommend updating. ([#6898](#6898)) ### AI Runtime * Add an experimental rank-partitioned container images to AI Runtime jobs. ([#6841](#6841)) * Support snapshot fields directly under `code_source` without requiring `type` or a nested `snapshot` block. ([#6927](#6927)) * Map AIR priority and Unity Catalog image fields when converting run configurations to bundles. ([#6905](#6905)) * Add workspace backend validation to `air run --dry-run`. ([#6934](#6934)) ### Bundles * Warn that `bundle.terraform` is deprecated and has no effect since the Terraform deployment engine was removed. ([#6940](#6940)) * Direct engine now detects and applies an explicitly configured zero-value boolean or float (e.g. `gcp_attributes.use_preemptible_executors: false`, `azure_attributes.spot_bid_max_price: 0`) added to a resource first deployed without the field, matching the existing handling of an explicit integer zero. ([#6882](#6882)) * Fix `bundle deployment migrate` failing with "no such file or directory" when the Terraform state has no resources or the configuration no longer declares any of them. ([#6958](#6958)) * `bundle run` and `pipelines run` now send the per-update `development` parameter for pipelines in development mode targets. Setting `development` on a pipeline is deprecated and now emits a warning; use `mode: development` instead. ([#6863](#6863)) * Remove the hidden `bundle debug terraform` command. ([#6933](#6933)) * Add support for `run_as.group_name` at the bundle and target levels for jobs and pipelines. ([#6676](#6676)) * Fix recreating a secret scope that was deleted outside of the bundle with the direct deployment engine. ([#6970](#6970)) * Accept title-case booleans (`True`/`False`, as rendered by Azure Pipelines) for boolean variables, and accept the same boolean strings (`yes`/`no`, `on`/`off`, ...) in Python bundles as in YAML. ([#6942](#6942)) ### Dependency Updates * Bump `github.com/databricks/databricks-sdk-go` from v0.182.0 to v0.185.0. ([#6928](#6928))

The v0.185.0 SDK bump (databricks#6928) added `environment_variables` to jobs. Each entry's `spec.files` lists `.env` files that tasks load at runtime, which the backend reads only from `/Workspace/...` or `/Volumes/...` paths. Relative paths in that list were passed through untranslated, so a path relative to the bundle would not resolve. This adds a job-level path rewrite pattern for `resources.jobs.*.environment_variables[*].spec.files[*]`, translating relative paths to their deployed workspace locations like other job file paths. Absolute `/Volumes` and `/Workspace` paths pass through unchanged, and jobs using `git_source` continue to skip path translation as before. This pull request and its description were written by Isaac. --------- Co-authored-by: Isaac <no-reply@databricks.com>

janniklasrose and others added 2 commits October 5, 2026 14:15

Add PR link to changelog fragment

df7bd97

Co-authored-by: Isaac <no-reply@databricks.com>

github-actions Bot added the DABs DABs related issues label Oct 5, 2026

janniklasrose commented Oct 5, 2026

View reviewed changes

github-actions Bot added the PyDABs label Oct 5, 2026

janniklasrose commented Oct 5, 2026

View reviewed changes

janniklasrose marked this pull request as ready for review October 5, 2026 15:34

janniklasrose requested review from a team as code owners October 5, 2026 15:34

janniklasrose requested review from anton-107 and renaudhartert-db October 5, 2026 15:34

denik approved these changes Oct 6, 2026

View reviewed changes

janniklasrose added this pull request to the merge queue Oct 6, 2026

Merged via the queue into main with commit c3baf71 Oct 6, 2026
36 checks passed

janniklasrose deleted the janniklasrose/bump-sdk-0.185.0 branch October 6, 2026 11:15

Sankalp-Mittal mentioned this pull request Oct 6, 2026

Add DATABRICKS_LITESWAP_TARGET to route requests to a liteswap unit #6946

Merged

yiweidai-db mentioned this pull request Oct 6, 2026

Resolve job project-environment paths relative to bundle YAML #6909

Closed

rugpanov mentioned this pull request Oct 7, 2026

Update Databricks CLI to v1.20.0 databricks/databricks-vscode#2241

Closed

yiweidai-db mentioned this pull request Oct 7, 2026

Resolve job project-environment paths relative to bundle YAML #6983

Merged

pietern mentioned this pull request Oct 8, 2026

Translate paths in job environment_variables files #6985

Merged

rugpanov mentioned this pull request Oct 8, 2026

Update Databricks CLI to v1.20.0 and remove Terraform bundling databricks/databricks-vscode#2243

Merged

Navigation Menu

Repository navigation

Bump databricks-sdk-go from v0.182.0 to v0.185.0 - #6928

Bump databricks-sdk-go from v0.182.0 to v0.185.0#6928
janniklasrose merged 5 commits into
mainfrom
janniklasrose/bump-sdk-0.185.0

janniklasrose commented Oct 5, 2026

Uh oh!

janniklasrose Oct 5, 2026

Uh oh!

Uh oh!

eng-dev-ecosystem-bot commented Oct 5, 2026 •

edited

Loading

Uh oh!

janniklasrose Oct 5, 2026

Uh oh!

Sankalp-Mittal Oct 6, 2026

Uh oh!

Uh oh!

janniklasrose Oct 5, 2026

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants

Conversation

janniklasrose commented Oct 5, 2026

Changes

Why

Tests

Uh oh!

janniklasrose Oct 5, 2026

Choose a reason for hiding this comment

Uh oh!

Uh oh!

eng-dev-ecosystem-bot commented Oct 5, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Integration test report

Uh oh!

janniklasrose Oct 5, 2026

Choose a reason for hiding this comment

Uh oh!

Sankalp-Mittal Oct 6, 2026

Choose a reason for hiding this comment

Uh oh!

Uh oh!

janniklasrose Oct 5, 2026

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants

eng-dev-ecosystem-bot commented Oct 5, 2026 •

edited

Loading