Bump databricks-sdk-go from v0.170.0 to v0.171.0 - #6320
Merged
Merged
Conversation
Regenerate the pinned OpenAPI spec SHA, CLI command stubs, bundle JSON schema, validation code, direct-engine resources, the DABs field map, and pydabs Python models to match v0.171.0. Notable surface changes: catalog McpService/ModelProviderService/ModelService drop the browse fields (IncludeBrowse/BrowseOnly); jobs gain triggers and ai_runtime_task fields; pipelines gain an API source connector; apps gains forward_user_access_token. Co-authored-by: Isaac
Co-authored-by: Isaac
shreyas-goenka
marked this pull request as ready for review
August 19, 2026 11:14
Handle new SDK fields surfaced by the v0.171.0 bump in the direct engine: add jobs.CreateJob.Triggers to makeCreateJob (exhaustruct), add jobs.Job.TriggerDetails to JobRemote and makeJobRemote (TestJobRemote coverage), and add apps forward_user_access_token to UpdateMaskFields (TestAppDoUpdate; updates the apps update goldens). Drop the now-redundant model_serving_endpoints telemetry_config.table_names ignore_remote_changes entry from resources.yml since resources.generated.yml now produces it. Co-authored-by: Isaac
Adding jobs.Job.TriggerDetails to JobRemote surfaces resources.jobs.*.trigger_details.* as REMOTE fields; regenerate out.fields.txt to match (validate-generated / generate-check). Co-authored-by: Isaac
andrewnester
approved these changes
Aug 19, 2026
Contributor
Author
|
integration tests are passing. |
Collaborator
Integration test reportCommit: 0e992d8
138 interesting tests: 79 MISS, 47 FAIL, 4 KNOWN, 4 flaky, 2 SKIP, 2 RECOVERED
Top 50 slowest tests (at least 2 minutes):
|
deco-sdk-tagging Bot
added a commit
that referenced
this pull request
Aug 20, 2026
## Release v1.13.0 ### Notable Changes * `bundle deploy` now reports the per-resource actions it took, how many files it synced, and a summary of created/changed/deleted/unchanged resources; `bundle destroy` reports how many resources it deleted. `-q` prints only the summaries, `-qq` only warnings and errors. ([#5720](#5720)) ### CLI * `databricks aitools install` now supports Goose, installing Databricks agent skills into its skills directory. * Error messages for failed key lookups and variable references now suggest the closest matching key if one is found. ([#6208](#6208)) * Released binaries are now built against the FIPS 140-3 validated Go Cryptographic Module, with FIPS 140-3 mode enabled by default. TLS connections negotiate only FIPS-approved cipher suites, which drops ChaCha20 and CBC from what the client offers. FIPS mode can be disabled at startup with `GODEBUG=fips140=off`, which restores the previous TLS behaviour ([#6262](#6262)). * `databricks environments setup-local` now removes a `databricks-connect` pin from `[project].dependencies`, an optional-dependency extra, or a dependency group when its version range conflicts with the compute target's `databricks-connect` version, so `uv sync` no longer fails with an unsatisfiable resolution when a template ships a conflicting pin. A pin that co-resolves, carries no version, or is marker-gated is left untouched, and each removed pin is reported with the new `W_DBCONNECT_CONSOLIDATED` warning. Wildcard version pins such as `==15.1.*` are now also checked for conflicts with the environment's constraints. ### Bundles * Allow dashes in the catalog and schema names prompted by `databricks bundle init`, and backtick-quote the catalog and schema identifiers in the SQL generated by the built-in templates so names with dashes work at runtime. * Fixed `bundle.git.branch`, `bundle.git.commit`, and `bundle.git.origin_url` being empty for bundles deployed from a workspace Git folder that has Git CLI access. The workspace API does not report git metadata for those folders, so it is now read from the Repos API instead. * direct: job_runs deploy progress lines now include the resource key (e.g. `Output from job_runs.foo: id=123: ...`) so concurrent runs are easier to tell apart. * direct: `resources.job_runs` can set `lifecycle.triggers.on_bundle_deploy: true` to re-fire the run on every bundle deploy. Removing the trigger does not recreate the existing run. * When migrating a bundle to the direct deployment engine, resources that only the direct engine supports (e.g. instance pools, catalogs) are now skipped by the deploy that migrates the state instead of failing it. They are created by the next deploy, which runs on the migrated state. * Warn on invalid `secret_scopes` permission levels (`READ`, `WRITE`, `MANAGE`); fail under `bundle validate --strict`. * Reject secret scope permissions that name no principal, instead of failing after the scope is created. * Write the deployment state atomically so an interrupted save cannot leave a state file that the CLI refuses to read. * Warn when the deployment state was last written by a newer CLI version than the one running. * Support pip extras (e.g. `[train]`) on local wheels in a job environment's `dependencies` ([#1602](#1602)). ### Dependency Updates * Bump `github.com/databricks/databricks-sdk-go` from v0.170.0 to v0.171.0 ([#6320](#6320)). * Bump the Databricks Terraform provider to 1.127.0 ([#6319](#6319)). * Bump Go toolchain to 1.26.6 ([#6266](#6266)). * Bump Go toolchain to 1.26.7 ([#6325](#6325)).
jariaspdev-lab
pushed a commit
to jariaspdev-lab/cli
that referenced
this pull request
Aug 25, 2026
## Changes
The direct engine planned an Apps update on every deploy, so each
`bundle deploy` issued a no-op `Apps.CreateUpdate` call. Every plan
looked like this, with a remote value and no local one:
```json
"forward_user_access_token": { "action": "update", "remote": true }
```
`forward_user_access_token` became part of `apps.App` in
databricks-sdk-go v0.171.0 (databricks#6320) and was added to the app update mask,
but nothing classified it. The backend enables token forwarding and
reports it as `true` even when the bundle omits the field, so the remote
`true` read as drift, `hasAppChanges` returned true, and the update
fired.
Declared under `backend_defaults`, exactly like `compute_size`: the
remote value is skipped when the config omits the field, while an
explicit value in the config still diffs normally (so real drift is
still caught).
janniklasrose
pushed a commit
that referenced
this pull request
Sep 15, 2026
janniklasrose
pushed a commit
that referenced
this pull request
Sep 15, 2026
## Changes
The direct engine planned an Apps update on every deploy, so each
`bundle deploy` issued a no-op `Apps.CreateUpdate` call. Every plan
looked like this, with a remote value and no local one:
```json
"forward_user_access_token": { "action": "update", "remote": true }
```
`forward_user_access_token` became part of `apps.App` in
databricks-sdk-go v0.171.0 (#6320) and was added to the app update mask,
but nothing classified it. The backend enables token forwarding and
reports it as `true` even when the bundle omits the field, so the remote
`true` read as drift, `hasAppChanges` returned true, and the update
fired.
Declared under `backend_defaults`, exactly like `compute_size`: the
remote value is skipped when the config omits the field, while an
explicit value in the config still diffs normally (so real drift is
still caught).
janniklasrose
pushed a commit
that referenced
this pull request
Sep 15, 2026
## Release v1.13.0 ### Notable Changes * `bundle deploy` now reports the per-resource actions it took, how many files it synced, and a summary of created/changed/deleted/unchanged resources; `bundle destroy` reports how many resources it deleted. `-q` prints only the summaries, `-qq` only warnings and errors. ([#5720](#5720)) ### CLI * `databricks aitools install` now supports Goose, installing Databricks agent skills into its skills directory. * Error messages for failed key lookups and variable references now suggest the closest matching key if one is found. ([#6208](#6208)) * Released binaries are now built against the FIPS 140-3 validated Go Cryptographic Module, with FIPS 140-3 mode enabled by default. TLS connections negotiate only FIPS-approved cipher suites, which drops ChaCha20 and CBC from what the client offers. FIPS mode can be disabled at startup with `GODEBUG=fips140=off`, which restores the previous TLS behaviour ([#6262](#6262)). * `databricks environments setup-local` now removes a `databricks-connect` pin from `[project].dependencies`, an optional-dependency extra, or a dependency group when its version range conflicts with the compute target's `databricks-connect` version, so `uv sync` no longer fails with an unsatisfiable resolution when a template ships a conflicting pin. A pin that co-resolves, carries no version, or is marker-gated is left untouched, and each removed pin is reported with the new `W_DBCONNECT_CONSOLIDATED` warning. Wildcard version pins such as `==15.1.*` are now also checked for conflicts with the environment's constraints. ### Bundles * Allow dashes in the catalog and schema names prompted by `databricks bundle init`, and backtick-quote the catalog and schema identifiers in the SQL generated by the built-in templates so names with dashes work at runtime. * Fixed `bundle.git.branch`, `bundle.git.commit`, and `bundle.git.origin_url` being empty for bundles deployed from a workspace Git folder that has Git CLI access. The workspace API does not report git metadata for those folders, so it is now read from the Repos API instead. * direct: job_runs deploy progress lines now include the resource key (e.g. `Output from job_runs.foo: id=123: ...`) so concurrent runs are easier to tell apart. * direct: `resources.job_runs` can set `lifecycle.triggers.on_bundle_deploy: true` to re-fire the run on every bundle deploy. Removing the trigger does not recreate the existing run. * When migrating a bundle to the direct deployment engine, resources that only the direct engine supports (e.g. instance pools, catalogs) are now skipped by the deploy that migrates the state instead of failing it. They are created by the next deploy, which runs on the migrated state. * Warn on invalid `secret_scopes` permission levels (`READ`, `WRITE`, `MANAGE`); fail under `bundle validate --strict`. * Reject secret scope permissions that name no principal, instead of failing after the scope is created. * Write the deployment state atomically so an interrupted save cannot leave a state file that the CLI refuses to read. * Warn when the deployment state was last written by a newer CLI version than the one running. * Support pip extras (e.g. `[train]`) on local wheels in a job environment's `dependencies` ([#1602](#1602)). ### Dependency Updates * Bump `github.com/databricks/databricks-sdk-go` from v0.170.0 to v0.171.0 ([#6320](#6320)). * Bump the Databricks Terraform provider to 1.127.0 ([#6319](#6319)). * Bump Go toolchain to 1.26.6 ([#6266](#6266)). * Bump Go toolchain to 1.26.7 ([#6325](#6325)).
renaudhartert-db
pushed a commit
to sunishsheth2009/cli
that referenced
this pull request
Sep 18, 2026
…6712) ## Changes Use the typed `SecretsUc.GetSecret` in `ResourceSecret.DoRead` instead of a hand-written `client.Do`. ## Why The raw call was necessary when it landed, but an SDK bump silently obsoleted it: - **2026-08-06 (databricks#5861):** UC secret support added on SDK v0.166.0, where `GetSecretRequest` had only `FullName` — hence the raw `include_value` call. - **2026-08-12:** SDK v0.171.0 adds `IncludeValue` to `GetSecretRequest`. - **2026-08-19 (databricks#6320):** CLI bumps to v0.171.0, making the workaround removable. This removes the workaround and its now-inaccurate comment. The wire request is unchanged: `GET /api/2.1/unity-catalog/secrets/{id}?include_value=true`. ## Tests `secrets` acceptance tests pass with no golden diff. This pull request and its description were written by Isaac. Co-authored-by: Isaac <no-reply@databricks.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.