Conversation
Co-authored-by: Isaac
Collaborator
Integration test reportCommit: ab358b3
25 interesting tests: 13 SKIP, 7 KNOWN, 3 RECOVERED, 2 flaky
|
# Conflicts: # libs/structs/structwalk/walktype_test.go
Co-authored-by: Isaac
anton-107
approved these changes
Jul 1, 2026
simonfaltum
approved these changes
Jul 1, 2026
simonfaltum
left a comment
simonfaltum
left a comment
Member
There was a problem hiding this comment.
LGTM but check the comments
denik
reviewed
Jul 2, 2026
Comment on lines
2222
to
+2225
| resources.model_serving_endpoints.*.tags[*].value string ALL | ||
| resources.model_serving_endpoints.*.telemetry_config *serving.TelemetryConfig ALL | ||
| resources.model_serving_endpoints.*.telemetry_config.inference_table_config *serving.TelemetryInferenceTableConfig ALL | ||
| resources.model_serving_endpoints.*.telemetry_config.inference_table_config.name string ALL |
Contributor
There was a problem hiding this comment.
Why do we have both resources.model_serving_endpoints.*.endpoint_details.telemetry_config.inference_table_config.name and resources.model_serving_endpoints.*.telemetry_config.inference_table_config.name ?
Sometimes when they have separate remote field they omit input field in GET responses, do we have test that asserts that resources.model_serving_endpoints.*.telemetry_config.inference_table_config.name is safe to rely on?
Contributor
Author
There was a problem hiding this comment.
Interesting... I can check.
|
|
||
| ignore_remote_changes: | ||
| - field: telemetry_config.inference_table_config.name | ||
| reason: spec:output_only |
Contributor
There was a problem hiding this comment.
output only?? It's present in ALL(input,state,remote).
If it's really output only we don't need it in state and we should forbid users from setting it.
Contributor
Author
There was a problem hiding this comment.
Hmm, this one is generated.
The annotation comes from the spec's field behaviors. Per the comment for the field, its value is produced by the server, yet the field is present in the resource's configuration type (it uses the create type).
We should fix this. Not in this PR though.
| // experiments / databricks_mlflow_experiment: 1 tf-only | ||
| // jobs / databricks_job: 11 renames | ||
| // jobs / databricks_job: 10 dabs-only | ||
| // jobs / databricks_job: 32 dabs-only |
Contributor
There was a problem hiding this comment.
I'd expect this to be reverted by terraform PR but I don't see that #5792
Contributor
Author
There was a problem hiding this comment.
I'll rebase that one on top of this.
deco-sdk-tagging Bot
added a commit
that referenced
this pull request
Jul 2, 2026
## Release v1.6.0 ### CLI * `ssh connect` now accepts a `--base-environment` flag to run a serverless session on a custom base environment. It takes an `env.yaml` path, a `workspace-base-environments/...` resource ID, or a base environment display name, and is rejected together with `--environment-version` or `--cluster` ([#5706](#5706)). * `databricks aitools install` is now plugin-first: it installs the Databricks plugin through each agent's own CLI (Claude Code, Codex, GitHub Copilot) instead of copying raw skill files. Agents without a plugin (OpenCode, Antigravity) still get skill files, and Cursor prints the `/add-plugin databricks` step. Use `--skills-only` to force raw skill files for every agent, or `--path <dir>` to write skills to a directory ([#5738](#5738)). * `databricks labs list` now only shows projects that can be installed ([#5560](#5560)). ### Bundles * direct: Fixed persistent drift on `model_serving_endpoints` caused by the `traffic_config` field ([#5708](#5708)). * direct: Fix spurious update when `apply_policy_default_values: true` is set on job task, for-each-task, or job cluster new_cluster ([#5731](#5731)). Also fix spurious updates for for-each-task clusters due to missing backend defaults for `data_security_mode`, `node_type_id`, `driver_node_type_id`, `driver_instance_pool_id`, `enable_elastic_disk`, and `enable_local_disk_encryption`. * direct: Cluster resize now falls back to regular update if resize fails due to `INVALID_STATE` ([#5716](#5716)). * `bundle generate dashboard` now honors the `--key` flag when naming the generated resource, and rejects combining `--existing-path`, `--existing-id`, and `--resource` instead of silently ignoring all but one ([#5492](#5492)). * Fixed `bundle deployment migrate` failing on `model_serving_endpoints`/`database_instances` with permissions (regression since v1.5.0) ([#5775](#5775)). * After a terraform deploy, the CLI now dry-runs a migration to the direct engine (writing nothing locally or remotely) and reports the outcome via telemetry, warning if the migration could not be completed ([#5797](#5797)). ### Dependency updates * Bump `github.com/databricks/databricks-sdk-go` from v0.147.0 to v0.152.0 ([#5773](#5773)). * Bump Terraform provider from v1.118.0 to v1.120.0 ([#5792](#5792)).
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
5 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.
Changes
Bumps databricks-sdk-go from v0.147.0 to v0.152.0 and regenerates
cli.json, command stubs, bundle schemas, validation code, Python dataclasses, and direct-engine resource types from the v0.152.0 OpenAPI spec.Manual fixups for SDK changes:
telemetry_configfield on serving endpoints wired through the direct-enginemodel_serving_endpointsresource (carried through the remote type so it participates in drift detection).ReplaceExistingcreate-time flag set on the postgresdatabaseandroleresource bodies (not exposed in bundle config).InitialBranchSpecfield set on the postgresprojectresource body, alongside the existingInitialEndpointSpec.New top-level command appears from the spec (
ai-search).Why
Keep the CLI current with the latest Databricks Go SDK and OpenAPI spec.
Tests
All non-integration unit and acceptance tests pass.
This pull request and its description were written by Isaac.