Uh oh!
There was an error while loading. Please reload this page.
Bump TF to 1.117.0 - #5421
Conversation
Commit: cf83302 |
simonfaltum
commented
Jun 3, 2026
This looks clean and the checksums match the 1.117.0 release, so the bump itself looks good to me. One thing I wanted to check: don't we also need to regenerate the acceptance goldens? A few of them pin the provider version in the recorded user-agent, so I think the terraform variants will drift from 1.115.0 to 1.117.0. The ones I spotted:
I think Also, the lint and direct-test failures look like they're coming from the SDK bump in #5361 (new |
aa90007 to
ce96ba0Comparejanniklasrose
commented
Jun 3, 2026
@simonfaltum re #5421 (comment) all got more or less auto-addressed after rebase |
Uh oh!
There was an error while loading. Please reload this page.
eng-dev-ecosystem-bot
commented
Jun 3, 2026
Commit: 25e2071 |
## Release v1.2.0 ### CLI * `experimental open` now opens every DABs resource type that has a workspace URL, picking up `catalogs`, `schemas`, `volumes`, `database_instances`, `database_catalogs`, `synced_database_tables`, `postgres_catalogs`, `postgres_synced_tables`, `quality_monitors`, `vector_search_endpoints`, and `vector_search_indexes` ([#5346](#5346)). ### Bundles * Retry transient HTTP 5xx and 408 errors in direct deployment engine ([#5349](#5349), [#5364](#5364)). * Preserve `.designer.ipynb` suffix when translating notebook task paths so Lakeflow Designer files referenced from a `notebook_task` resolve correctly in the workspace ([#5370](#5370)). * Fix script output dropping last line without trailing newline ([#4995](#4995)). * engine/direct: Add `--select` flag to `bundle plan` and `bundle deploy` to plan/deploy a subset of resources (e.g. `--select my_job` or `--select jobs.my_job`); resources referenced by the selection are included transitively ([#5413](#5413)). * Support `purge_on_delete: true` on `postgres_projects` so bundles can hard-delete a Lakebase project on destroy (skipping the soft-delete retention window) ([#5414](#5414)). * Support terraform references in direct engine ([#5392](#5392)) * Support lifecycle.started for SQL warehouses ([#5348](#5348)) ### Dependency updates * Bump Go toolchain to 1.26.4 ([#5420](#5420)). * Bump `github.com/databricks/databricks-sdk-go` from v0.136.0 to v0.141.0 ([#5361](#5361)) * Bump Terraform provider from v1.115.0 to v1.117.0 ([#5421](#5421))
Brings committed generator outputs back in sync with their inputs; a fresh generate is now a no-op. What had drifted: - OpenAPI annotations against the current `.codegen/_openapi_sha` (databricks#5361 advanced the sha but didn't re-run the extraction, which needs `DATABRICKS_OPENAPI_SPEC`), adding the new Vector Search Index resource and propagating to `jsonschema.json`, `jsonschema_for_docs.json`, bundle docs, and pydabs models. - `bundle/internal/tf/schema` against the pinned provider (v1.117.0, bumped in databricks#5421). - `bundle/terraform_dabs_map/generated.go`. Other generators (genkit, refschema, validation, direct engine, schema-map) produced no diff. The Taskfile gap that let the annotations go stale is intentional (placeholder/human-curation workflow) and will be addressed separately. This pull request and its description were written by Isaac.
Changes
Bump TF provider to v1.117.0
Stacked on #5361
Why
Align releases
Tests
task generate-tf-schemawas no-op besides version & sha