Bump Terraform provider from v1.125.0 to v1.126.0 - #6250
Merged
Conversation
## Changes Bump the pinned Databricks Terraform provider from v1.125.0 to v1.126.0. The v1.126.0 release contains no bundle-relevant resource or field schema changes; only the pinned provider version and archive checksums change. ## Tests Acceptance goldens regenerated via `./task test-update` (no golden changes). Co-authored-by: Isaac
…ment The v1.124.0->v1.125.0 bump has not been released yet, so its unreleased changelog fragment is superseded by this v1.126.0 bump; drop it to avoid a duplicate Dependency Updates line, and expand the PR link in the new fragment. Co-authored-by: Isaac
The v1.124.0->v1.125.0 bump is merged but unreleased, so this fragment now covers the whole unreleased range in a single Dependency Updates line, and expands the PR link (the prior commit only staged the fragment removal). Co-authored-by: Isaac
pietern
approved these changes
Aug 12, 2026
janniklasrose
enabled auto-merge
August 12, 2026 12:38
denik
approved these changes
Aug 12, 2026
denik
approved these changes
Aug 12, 2026
Collaborator
Integration test reportCommit: 721ba21
8 interesting tests: 4 RECOVERED, 4 SKIP
Top 5 slowest tests (at least 2 minutes):
|
deco-sdk-tagging Bot
added a commit
that referenced
this pull request
Aug 12, 2026
## Release v1.12.0 ### CLI * `databricks aitools install` now supports Gemini CLI, installing Databricks agent skills into its skills directory. * `databricks aitools install` now supports Pi, installing Databricks agent skills into its skills directory. * A locally built CLI (`go build`, without release flags) now reports the next release version with a `-dev` prerelease, e.g. `1.12.0-dev+abcdef123456`, instead of `0.0.0-dev+abcdef123456`. The old string sorted below every published release even though a local build is newer than the latest release; the new one sorts above the latest release and below the release it will become, matching what goreleaser already produces for snapshot builds. * Added the `databricks environments setup-local` command, which provisions (or updates) a local Python environment matched to a Databricks compute target. It resolves the target to an environment key, fetches the pinned Python version, databricks-connect version, and dependency constraints published for that key, then provisions a matched `.venv` with uv. ### Bundles * Added a `cascade_on_destroy` field to the pipeline resource to control whether destroying a pipeline also deletes its datasets (MVs, STs, Views). When unset, the server default applies; set `cascade_on_destroy: false` to retain the datasets on destroy. Supported with the direct deployment engine ([#5846](#5846)). * Fix `bundle.deployment.lock.force` being ignored. The `--force-lock` flag's default value overwrote the value configured in `databricks.yml`, so setting the field had no effect and a stale deployment lock could only be overridden with the flag. ([#6188](#6188)) * direct: experimental `job_runs` now sends a CLI-managed idempotency token on every run-now, so an SDK retry after a lost response returns the same run. Configured `idempotency_token` values are rejected. * direct: the experimental `job_runs` resource now waits for the triggered run to finish, so other resources can reference its outcome (e.g. `${resources.job_runs.nightly.state.result_state}`). A run that does not succeed fails the deploy, naming the failed task, and is run again on the next deploy. If a deploy is interrupted while waiting, the next one resumes waiting on the same run. * direct: Fixed model serving `telemetry_config` drift and applied planned telemetry updates. Unsupported endpoint types now fail when telemetry is applied; create may still succeed because it drops the field ([#6106](#6106)). * The `cli_version` field in the direct engine's deployment state (`resources.json`) now records the CLI version that last wrote the state. Previously it kept the version of the CLI that first created the state. * Add support for UC secrets resource ([#5861](#5861)) ### Dependency Updates * Bump `github.com/databricks/databricks-sdk-go` from v0.166.0 to v0.169.0. * Bump Terraform provider from v1.124.0 to v1.126.0 ([#6250](#6250)).
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.125.0 to v1.126.0.
The v1.126.0 release contains no bundle-relevant resource or field schema changes; only the pinned provider version and archive checksums in the generated schema change.
Why
Keep the CLI's pinned Terraform provider current; v1.126.0 was released 2026-08-12.
Tests
Acceptance goldens regenerated via
./task test-update— no golden changes. Full acceptance suite passes locally on both engines.This PR was written by Claude Code.