Bump Terraform provider to v1.124.0 - #6174
Merged
Merged
Conversation
## Changes Bump the pinned Databricks Terraform provider from v1.123.0 to v1.124.0. Notable schema changes: - Added `databricks_ai_gateway_mcp_service`, `databricks_ai_gateway_model_provider_service` and `databricks_ai_gateway_model_service` resources. - Added the corresponding singular and plural AI Gateway data sources. The change is additive: no fields were removed or became required, and the DABs/Terraform field map is unchanged. ## Why Dependency update. ## Tests Schema and field map regenerated. Acceptance suite passes without golden changes. _This PR was written by Claude Code._ Co-authored-by: Isaac
Merged
denik
approved these changes
Aug 5, 2026
Member
Author
|
Skipping integ tests on windows (stalled due to infra issue), linux ones are passing |
janniklasrose
added a commit
that referenced
this pull request
Aug 5, 2026
## Changes Bump `github.com/databricks/databricks-sdk-go` from v0.165.0 to v0.166.0 and the pinned OpenAPI spec SHA to `fc2245ecebf2878cd80f078ad060b6838283dfac`. Notable SDK/spec changes: - Added the `ai-gateway` workspace command group. - `AiRuntimeTask` and its `ComputeSpec`/`DeploymentSpec` fields moved from Private Preview to Public Preview, so they are no longer hidden from the bundle JSON schema or the pydabs models. - Added `UpdateOperation` and several new fields to the bundle-deployments service. The release is additive, so no CLI code needed adapting. ## Why Dependency update. ## Tests All generated artifacts regenerated (`generate-clijson`, `generate-cligen`, `generate-check`, `generate-schema-map`). The only acceptance golden change is the new `ai-gateway` line in `acceptance/help/output.txt`. Locally green: acceptance suite without `-update`, the full root-module unit suite, `./task fmt`, `./task lint` and `./task checks`. ## Related PRs Stacked on #6174 (Terraform provider v1.124.0), which pins this SDK version in its own `go.mod`. Rebase onto `main` once that lands. _This PR was written by Claude Code._
Collaborator
Integration test reportCommit: 1ff9d0a
119 interesting tests: 75 MISS, 37 FAIL, 4 RECOVERED, 2 SKIP, 1 KNOWN
Top 50 slowest tests (at least 2 minutes):
|
Collaborator
Integration test reportCommit: 1ff9d0a
319 interesting tests: 292 MISS, 22 FAIL, 4 RECOVERED, 1 SKIP
Top 50 slowest tests (at least 2 minutes):
|
deco-sdk-tagging Bot
added a commit
that referenced
this pull request
Aug 6, 2026
## Release v1.11.0 ### CLI * Fixed `databricks repos get/update/delete` failing with `object at path "..." is not a repo` for Git-CLI-enabled folders (currently in preview), which the workspace API reports as directories rather than repos ([#6181](#6181)). * Support `dbfs:/Skills/...` paths in `databricks fs` commands, routed to the Files API. ([#6147](#6147)) ### Bundles * For jobs where `ai_runtime_task.code_source_path` is a relative path to a local directory, the directory is now packaged into a tarball (honoring `.gitignore` and `sync.include`/`sync.exclude`), uploaded during deployment, and `code_source_path` is rewritten to the uploaded workspace path. ([#6110](#6110)) * Added JSON output to `bundle init`. Running `databricks bundle init <template> -o json` now reports the files the template wrote, relative to the output directory. This lets callers that pass `--output-dir` learn where the template materialized instead of assuming the output is a single directory named after the project. The default text output is unchanged. ([#6161](#6161)) * The terraform deployment engine is deprecated and will stop working in a future version of the CLI. Setting `bundle.engine: terraform` now emits a deprecation warning. See https://docs.databricks.com/aws/en/dev-tools/bundles/direct for how to migrate to the direct deployment engine. ([#6099](#6099)) * Fixed the direct deployment engine planning a spurious `create` for an empty `grants: []` list. Terraform records no grants resource for such a list, so `bundle plan` after `bundle deployment migrate` no longer reports an action for it. Emptying a previously deployed list still revokes the grants, after which the node is dropped from the deployment state instead of being reported as unchanged forever. ([#6039](#6039)) * Fixed `bundle generate` downloading notebooks found inside a folder without their file extension. They are now exported like top-level notebooks, so a Python notebook lands as `notebook.py` instead of an extensionless file ([#6144](#6144)). * direct: `webhook_notifications.on_*` destinations on jobs, tasks, and `for_each_task` are now compared as unordered sets. Previously the Jobs API returning these lists in a different order than submitted produced a phantom diff that `bundle plan` and `bundle deploy` could never converge past, reporting `1 to change` on every run ([#6060](#6060)). * Fixed a pipeline with `allow_duplicate_names: true` never converging on the direct engine: the field is only accepted on create/update and is never returned by the pipelines GET API, so every subsequent `bundle plan` reported the pipeline as a perpetual update. ([#6076](#6076)) * direct: A local change to an input-only field (one the API accepts on write but never returns on read, e.g. pipelines' `run_as` or external locations' `skip_validation`) is no longer silently skipped when the new value coincidentally matches the field's fabricated remote value. Previously such a change could hit the `remote_already_set` shortcut and be dropped from the plan. ([#6112](#6112)) * Revert usage of RedactiveSenstiveFields (added in [#5896](#5896), released in 1.10.0) which lead to incorrect behaviour (permanent drift) for duration field in Postgres resources ([#6179](#6179)). * Document postgres resource fields in the json schema ([#6164](#6164), [#6163](#6163)). * direct: Recreating a `vector_search_indexes` resource no longer fails with "Index ... is currently pending deletion" when the backend has not yet released the index name. The create is now retried until the name becomes available. ([#6143](#6143)) ### Dependency Updates * Bump `github.com/databricks/databricks-sdk-go` from v0.165.0 to v0.166.0. ([#6175](#6175)) * Upgrade Terraform provider to 1.124.0. ([#6174](#6174))
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.
Changes
Bump the pinned Databricks Terraform provider from v1.123.0 to v1.124.0.
Notable schema changes:
databricks_ai_gateway_mcp_service,databricks_ai_gateway_model_provider_serviceanddatabricks_ai_gateway_model_serviceresources.The change is additive: no fields were removed or became required, and the DABs/Terraform field map (
bundle/terraform_dabs_map/generated.go) is unchanged.Why
Dependency update.
Tests
Schema and field map regenerated. The acceptance suite passes without
-updateand required no golden changes at all.Note:
./task generate-tf-schemainitially failed withno available releases match the given constraints 1.124.0. On a Databricks machine~/.terraformrcredirectsregistry.terraform.ioto the internalterraform-proxy.cloud.databricks.com, whose mirror had not yet indexed v1.124.0, so codegen ran against a local filesystem mirror of the GitHub release zip. Codegen still fetched and verified the real GitHub SHA256 checksums forroot.go.This PR was written by Claude Code.