Bump Terraform provider from v1.128.0 to v1.131.0 - #6544
Merged
Merged
Conversation
Bump `github.com/databricks/databricks-sdk-go` from v0.175.0 to v0.177.0 and the pinned OpenAPI spec SHA to `0f2c9a3d`. Regenerated all downstream artifacts from the new spec: CLI command stubs, bundle JSON schema, validation, direct-engine resources, pydabs models, and the DABs<->TF field map. User-visible additions include the jobs continuous `maintenance_window` field and the pipelines RabbitMQ connector options; the postgres branch `source_snapshot` field is now handled as immutable/input-only by the direct engine. The v0.177.0 `ml.*` field removals (feature-engineering) are not referenced by hand-written CLI code, so they required no source changes. The SDK now marks the pipelines `continuous` field deprecated; it remains a supported bundle config field, so its four usages carry `//nolint:staticcheck` (SA1019). Keep the CLI current with the latest SDK and provide a clean base for upcoming feature work. Acceptance goldens regenerated via `-update` (help text + refschema). The non-update verify pass is green apart from load-induced terraform-engine timeout flakes, each confirmed passing in isolation. Root-module unit suite passes (9532 tests). `./task fmt`, `./task lint`, and `./task checks` clean. Co-authored-by: Isaac <no-reply@databricks.com>
janniklasrose
force-pushed
the
bump-tf-1.131.0
branch
from
September 7, 2026 09:23
e41f46d to
b87fab3
Compare
janniklasrose
marked this pull request as ready for review
September 7, 2026 09:25
Co-authored-by: Isaac <no-reply@databricks.com>
## Changes
Bump the pinned Databricks Terraform provider from v1.128.0 to v1.131.0.
The provider caught up to databricks-sdk-go v0.177.0, so several fields that
were DABs-only are now mapped in bundle/terraform_dabs_map/generated.go:
- jobs `continuous.maintenance_window` and `triggers.continuous.maintenance_window`
- cluster `{driver,worker}_node_type_flexibility.aws_context_id`
- jobs `alert_task.parameters`
- postgres branch `source_snapshot` (spec and status)
New generated schema: `databricks_postgres_snapshot_schedule` resource + data
source, and the iam-v2 external group/service-principal/user data sources.
## Tests
Acceptance goldens regenerated via `-update` (no golden changes — the new
provider fields are additive and the provider version is masked in output).
Verify pass green apart from pre-existing load-induced terraform-engine timeout
flakes, each confirmed passing in isolation.
Co-authored-by: Isaac <no-reply@databricks.com>
Co-authored-by: Isaac <no-reply@databricks.com>
andrewnester
approved these changes
Sep 7, 2026
Co-authored-by: Isaac <no-reply@databricks.com>
janniklasrose
force-pushed
the
bump-tf-1.131.0
branch
from
September 7, 2026 09:43
b87fab3 to
1360d8f
Compare
denik
approved these changes
Sep 7, 2026
Collaborator
Integration test reportCommit: 1360d8f
Top 4 slowest tests (at least 2 minutes):
|
deco-sdk-tagging Bot
added a commit
that referenced
this pull request
Sep 9, 2026
## Release v1.16.0 ### CLI * `aitools install` now registers the official Claude marketplace if it is missing before installing the Databricks Claude plugin. ([#6485](#6485)) * `databricks aitools install --output json` now reports an `error_category` for a failed or skipped install (per agent, and at the top level for a failure with no per-agent entry), giving coding agents and CI a stable classification of why an install did not complete. ([#6482](#6482)) * `databricks aitools install` honors `--output json`, emitting a structured `{scope, agents[...]}` document that reports each agent's delivery and install status so coding agents and CI can consume the result without scraping the text output. JSON mode requires `--scope` and `--agents` so the command runs without interactive prompts. ([#6481](#6481)) * `databricks bundle sync` now prints sync progress (`Action: PUT`, `Uploaded ...`) by default, matching `databricks sync`. Previously it was silent unless `--output` was passed. Use `--output json` for machine-readable output. ([#6568](#6568)) * Support major-only DBR runtime versions such as `19.x-scala2.13` in the cluster picker used by `databricks auth login --configure-cluster` and `databricks labs`. ([#6574](#6574)) * Deprecated the `databricks environments setup-local --constraints-only` flag in favour of the orthogonal `--no-dbconnect`; the flag still works as a hidden alias but is hidden from `--help` and prints a one-line deprecation notice, and will be removed in a later release. ([#6470](#6470)) * Add orthogonal `--no-constraints` and `--no-dbconnect` flags to `databricks environments setup-local`: `--no-constraints` skips writing the remote Python-version and dependency pins, and `--no-dbconnect` skips the databricks-connect dependency. ([#6464](#6464)) * `databricks environments setup-local` now reports a distinct `E_PROVISION_CONFLICT` error code in `--output json` when the project's dependencies conflict with the pins written for the target environment, making the requirements unsatisfiable (the same conflict surfaced as a `W_USER_CONSTRAINT_CONFLICT` warning); it is reported after the project files are written, without attempting the doomed provisioning, while other provisioning failures continue to report `E_PROVISION`. ([#6479](#6479)) * `databricks ssh connect` and `ssh setup` now verify the tunnel's SSH host key against the key the workspace published for the connection, recorded in `~/.databricks/ssh-tunnel-known-hosts/<name>` instead of `~/.ssh/known_hosts`. Reconnecting with a name used before no longer fails with `Host key verification failed` when the compute behind that name changed, and no longer needs a manual `ssh-keygen -R`; host blocks written by an earlier `databricks ssh setup` pick this up once you re-run it. ([#6557](#6557)) * Stop `databricks ssh connect --ide` from adding a duplicate entry to the IDE's Remote Explorer on every connect: the remote authority is now the SSH host alias alone, instead of embedding the per-instance remote OS user. ([#6550](#6550)) * Add `--max-clients` and `--server-timeout` flags to `databricks ssh setup`, and `--server-timeout` to `databricks ssh connect`. Both are fixed when the SSH tunnel server job is submitted, so `ssh setup` now serializes them into the generated `ProxyCommand` instead of falling back to the built-in defaults. ([#6547](#6547)) * `ssh connect` sessions no longer end when the tunnel's websocket connection is lost. The CLI reattaches to the running session and replays the bytes that were missed, so the shell and everything running in it stay intact, and a transient failure to open a replacement connection for the periodic auth refresh is retried rather than ending the session. Reattaching requires an SSH server started by a CLI that supports it; against an older server the connection behaves as before. ([#6558](#6558)) ### Bundles * Added PyDABs (Python) support for secrets: `Resources.add_secret` and the `secret_mutator` decorator. ([#6553](#6553)) * Fix job and pipeline environment dependencies with a `*` version wildcard (e.g. `numpy==2.5.*`) being treated as local file paths. ([#6555](#6555)) * Add the `postgres_snapshot_schedules` bundle resource for managing a Lakebase Postgres branch's automatic-snapshot schedule (direct deployment engine only). ([#6449](#6449)) ### Dependency Updates * Bump `github.com/databricks/databricks-sdk-go` from v0.175.0 to v0.177.0. ([#6448](#6448)) * Bump Terraform provider from v1.128.0 to v1.131.0. ([#6544](#6544))
alex-khakhlyuk
pushed a commit
to alex-khakhlyuk/cli
that referenced
this pull request
Sep 10, 2026
…databricks#6546) ## Changes Fix `tools/validate_nextchanges.py` to attribute each `.nextchanges/` fragment to the PR that actually introduced it, rather than always the current PR. The changelog-preview check requires every fragment's trailing PR link to name the current PR. It infers the expected PR from the squash-merge commit subject (`(#N)`), falling back to the current PR for fragments not yet on main. That fallback is wrong for a **gh-stacked PR**: the fragments inherited from earlier PRs in the stack are added by ordinary branch commits (no `(#N)` subject), so they were attributed to the top PR — and CI failed even though each fragment already carried the correct link to the earlier PR. Concretely, [databricks#6544](databricks#6544) (stacked on the SDK bump [databricks#6448](databricks#6448)) failed with: ``` .nextchanges/dependency-updates/bump-sdk-0.177.0.md: trailing PR link databricks#6448 must include the PR that added this fragment (databricks#6544) ``` ## Fix A fragment that already exists on the PR's **base branch** was introduced by an earlier PR (upstream, or lower in the stack), so it is no longer attributed to the current PR — it keeps its own link and is only required to be well-formed. Fragments the PR genuinely adds still must name the current PR, as before. - `infer_expected_pr` returns `None` (no specific PR imposed) when the fragment is present on the base branch (`fragment_on_base`), instead of falling back to the current PR. - The base branch is `BASE_REF` (`github.event.pull_request.base.ref`) in CI, or a best-effort `gh` lookup locally (`detect_base_ref` / `current_branch_base`, mirroring the existing PR detection). - The changelog-preview workflow now passes `BASE_REF` to the validate step. Behavior is unchanged for non-stacked PRs, pushes to main (fragments keep their `(#N)` attribution), and the merge queue's shallow checkout (PR-link checks are already skipped there). ## Tests - Existing doctests pass (`python -m doctest tools/validate_nextchanges.py`). - Reproduced a two-branch stack in a scratch repo: the old code fails on the inherited fragment with the same error as databricks#6544; with `BASE_REF` set to the base branch it passes. The genuinely-new fragment still requires the top PR's link. This pull request and its description were written by Isaac. --------- Co-authored-by: Isaac <no-reply@databricks.com>
janniklasrose
added a commit
that referenced
this pull request
Sep 15, 2026
## Changes Bump the pinned Databricks Terraform provider from v1.128.0 to v1.131.0. Stacked on #6448 (SDK bump to v0.177.0): v1.131.0 pins databricks-sdk-go v0.177.0, so the provider caught up to several fields that were previously DABs-only and are now mapped in `bundle/terraform_dabs_map/generated.go`: - jobs `continuous.maintenance_window` (and `triggers.continuous.maintenance_window`) - cluster `{driver,worker}_node_type_flexibility.aws_context_id` - jobs `alert_task.parameters` - postgres branch `source_snapshot` New generated schema includes the `databricks_postgres_snapshot_schedule` resource + data source and the iam-v2 external identity data sources. ## Why Keep the pinned Terraform provider current with the SDK bump. ## Tests Acceptance goldens regenerated via `-update` — no golden changes (the new provider fields are additive and the provider version is masked in acceptance output). Verify pass green apart from pre-existing load-induced terraform-engine timeout flakes, each confirmed passing in isolation. _This PR was written by Claude Code._ --------- Co-authored-by: Isaac <no-reply@databricks.com>
janniklasrose
added a commit
that referenced
this pull request
Sep 15, 2026
…#6546) ## Changes Fix `tools/validate_nextchanges.py` to attribute each `.nextchanges/` fragment to the PR that actually introduced it, rather than always the current PR. The changelog-preview check requires every fragment's trailing PR link to name the current PR. It infers the expected PR from the squash-merge commit subject (`(#N)`), falling back to the current PR for fragments not yet on main. That fallback is wrong for a **gh-stacked PR**: the fragments inherited from earlier PRs in the stack are added by ordinary branch commits (no `(#N)` subject), so they were attributed to the top PR — and CI failed even though each fragment already carried the correct link to the earlier PR. Concretely, [#6544](#6544) (stacked on the SDK bump [#6448](#6448)) failed with: ``` .nextchanges/dependency-updates/bump-sdk-0.177.0.md: trailing PR link #6448 must include the PR that added this fragment (#6544) ``` ## Fix A fragment that already exists on the PR's **base branch** was introduced by an earlier PR (upstream, or lower in the stack), so it is no longer attributed to the current PR — it keeps its own link and is only required to be well-formed. Fragments the PR genuinely adds still must name the current PR, as before. - `infer_expected_pr` returns `None` (no specific PR imposed) when the fragment is present on the base branch (`fragment_on_base`), instead of falling back to the current PR. - The base branch is `BASE_REF` (`github.event.pull_request.base.ref`) in CI, or a best-effort `gh` lookup locally (`detect_base_ref` / `current_branch_base`, mirroring the existing PR detection). - The changelog-preview workflow now passes `BASE_REF` to the validate step. Behavior is unchanged for non-stacked PRs, pushes to main (fragments keep their `(#N)` attribution), and the merge queue's shallow checkout (PR-link checks are already skipped there). ## Tests - Existing doctests pass (`python -m doctest tools/validate_nextchanges.py`). - Reproduced a two-branch stack in a scratch repo: the old code fails on the inherited fragment with the same error as #6544; with `BASE_REF` set to the base branch it passes. The genuinely-new fragment still requires the top PR's link. This pull request and its description were written by Isaac. --------- Co-authored-by: Isaac <no-reply@databricks.com>
janniklasrose
pushed a commit
that referenced
this pull request
Sep 15, 2026
## Release v1.16.0 ### CLI * `aitools install` now registers the official Claude marketplace if it is missing before installing the Databricks Claude plugin. ([#6485](#6485)) * `databricks aitools install --output json` now reports an `error_category` for a failed or skipped install (per agent, and at the top level for a failure with no per-agent entry), giving coding agents and CI a stable classification of why an install did not complete. ([#6482](#6482)) * `databricks aitools install` honors `--output json`, emitting a structured `{scope, agents[...]}` document that reports each agent's delivery and install status so coding agents and CI can consume the result without scraping the text output. JSON mode requires `--scope` and `--agents` so the command runs without interactive prompts. ([#6481](#6481)) * `databricks bundle sync` now prints sync progress (`Action: PUT`, `Uploaded ...`) by default, matching `databricks sync`. Previously it was silent unless `--output` was passed. Use `--output json` for machine-readable output. ([#6568](#6568)) * Support major-only DBR runtime versions such as `19.x-scala2.13` in the cluster picker used by `databricks auth login --configure-cluster` and `databricks labs`. ([#6574](#6574)) * Deprecated the `databricks environments setup-local --constraints-only` flag in favour of the orthogonal `--no-dbconnect`; the flag still works as a hidden alias but is hidden from `--help` and prints a one-line deprecation notice, and will be removed in a later release. ([#6470](#6470)) * Add orthogonal `--no-constraints` and `--no-dbconnect` flags to `databricks environments setup-local`: `--no-constraints` skips writing the remote Python-version and dependency pins, and `--no-dbconnect` skips the databricks-connect dependency. ([#6464](#6464)) * `databricks environments setup-local` now reports a distinct `E_PROVISION_CONFLICT` error code in `--output json` when the project's dependencies conflict with the pins written for the target environment, making the requirements unsatisfiable (the same conflict surfaced as a `W_USER_CONSTRAINT_CONFLICT` warning); it is reported after the project files are written, without attempting the doomed provisioning, while other provisioning failures continue to report `E_PROVISION`. ([#6479](#6479)) * `databricks ssh connect` and `ssh setup` now verify the tunnel's SSH host key against the key the workspace published for the connection, recorded in `~/.databricks/ssh-tunnel-known-hosts/<name>` instead of `~/.ssh/known_hosts`. Reconnecting with a name used before no longer fails with `Host key verification failed` when the compute behind that name changed, and no longer needs a manual `ssh-keygen -R`; host blocks written by an earlier `databricks ssh setup` pick this up once you re-run it. ([#6557](#6557)) * Stop `databricks ssh connect --ide` from adding a duplicate entry to the IDE's Remote Explorer on every connect: the remote authority is now the SSH host alias alone, instead of embedding the per-instance remote OS user. ([#6550](#6550)) * Add `--max-clients` and `--server-timeout` flags to `databricks ssh setup`, and `--server-timeout` to `databricks ssh connect`. Both are fixed when the SSH tunnel server job is submitted, so `ssh setup` now serializes them into the generated `ProxyCommand` instead of falling back to the built-in defaults. ([#6547](#6547)) * `ssh connect` sessions no longer end when the tunnel's websocket connection is lost. The CLI reattaches to the running session and replays the bytes that were missed, so the shell and everything running in it stay intact, and a transient failure to open a replacement connection for the periodic auth refresh is retried rather than ending the session. Reattaching requires an SSH server started by a CLI that supports it; against an older server the connection behaves as before. ([#6558](#6558)) ### Bundles * Added PyDABs (Python) support for secrets: `Resources.add_secret` and the `secret_mutator` decorator. ([#6553](#6553)) * Fix job and pipeline environment dependencies with a `*` version wildcard (e.g. `numpy==2.5.*`) being treated as local file paths. ([#6555](#6555)) * Add the `postgres_snapshot_schedules` bundle resource for managing a Lakebase Postgres branch's automatic-snapshot schedule (direct deployment engine only). ([#6449](#6449)) ### Dependency Updates * Bump `github.com/databricks/databricks-sdk-go` from v0.175.0 to v0.177.0. ([#6448](#6448)) * Bump Terraform provider from v1.128.0 to v1.131.0. ([#6544](#6544))
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
4 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
Bump the pinned Databricks Terraform provider from v1.128.0 to v1.131.0.
Stacked on #6448 (SDK bump to v0.177.0): v1.131.0 pins databricks-sdk-go
v0.177.0, so the provider caught up to several fields that were previously
DABs-only and are now mapped in
bundle/terraform_dabs_map/generated.go:continuous.maintenance_window(andtriggers.continuous.maintenance_window){driver,worker}_node_type_flexibility.aws_context_idalert_task.parameterssource_snapshotNew generated schema includes the
databricks_postgres_snapshot_scheduleresource + data source and the iam-v2 external identity data sources.
Why
Keep the pinned Terraform provider current with the SDK bump.
Tests
Acceptance goldens regenerated via
-update— no golden changes (the newprovider fields are additive and the provider version is masked in acceptance
output). Verify pass green apart from pre-existing load-induced terraform-engine
timeout flakes, each confirmed passing in isolation.
This PR was written by Claude Code.