Uh oh!
There was an error while loading. Please reload this page.
Conversation
## Changes See https://github.com/databricks/terraform-provider-databricks/releases/tag/v1.98.0 ## Why Nominal upgrade to match the SDK version. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
pietern
requested review from
andrewnester, anton-107, denik and shreyas-goenka
as code ownersDecember 4, 2025 08:34
pieterntemporarily deployed
to
test-trigger-is
December 4, 2025 08:34 — with 
GitHub Actions
Inactive
pieterntemporarily deployed
to
test-trigger-is
December 4, 2025 08:46 — with GitHub Actions
Inactive
pieterntemporarily deployed
to
test-trigger-is
December 4, 2025 08:47 — with GitHub Actions
Inactive
pieterntemporarily deployed
to
test-trigger-is
December 4, 2025 08:54 — with GitHub Actions
Inactive
- Update acceptance test outputs for provider v1.98.0 - Reflect pipeline recreation behavior changes in new provider - Update prevent-destroy test to exercise recreation with storage instead of catalog ## Provider v1.98.0 Behavior Changes The key behavioral change in Terraform provider v1.98.0 is that **pipeline catalog updates no longer trigger recreation**. The provider relaxed the force_new constraint on the catalog attribute, allowing in-place updates. This affects several acceptance tests: - Pipeline recreation tests now show 'update' instead of 'recreate' - API calls changed from DELETE+POST to PUT for catalog changes - The prevent-destroy test was updated to use 'storage' (which still triggers recreation) instead of 'catalog' to properly exercise the prevent_destroy lifecycle behavior
pieterntemporarily deployed
to
test-trigger-is
December 4, 2025 08:59 — with GitHub Actions
Inactive
Collaborator
Commit: 983571e
9 interesting tests: 7 KNOWN, 2 SKIP
Top 20 slowest tests (at least 2 minutes):
|
andrewnester
approved these changes
Dec 4, 2025
andrewnestertemporarily deployed
to
test-trigger-is
December 4, 2025 09:51 — with GitHub Actions
Inactive
The exec() function was incorrectly using 'locals=' as a keyword argument, which is not valid Python syntax. Changed to use positional arguments instead. This fixes the remote_add_tag acceptance test which was failing with: TypeError: exec() takes no keyword arguments Also regenerates the test output files that were previously deleted.
pieterntemporarily deployed
to
test-trigger-is
December 4, 2025 10:38 — with GitHub Actions
Inactive
pieterntemporarily deployed
to
test-trigger-is
December 4, 2025 10:46 — with GitHub Actions
Inactive
pietern
commented
Dec 4, 2025
| try: | ||
| exec(script, locals=my_locals) | ||
| exec(script, my_locals) |
ContributorAuthor
There was a problem hiding this comment.
Needed for compat with Python < 3.13.
| "catalog": deployplan.ActionTypeRecreate, | ||
| "ingestion_definition.connection_name": deployplan.ActionTypeRecreate, | ||
| "storage": deployplan.ActionTypeRecreate, | ||
| "ingestion_definition.connection_name": deployplan.ActionTypeRecreate, |
| foo: | ||
| name: pipeline foo | ||
| catalog: mycatalog | ||
| storage: dbfs:/my-storage |
ContributorAuthor
There was a problem hiding this comment.
Storage triggers recreation. The test is about recreation.
Uh oh!
There was an error while loading. Please reload this page.
eng-dev-ecosystem-bot
commented
Dec 4, 2025
Collaborator
Commit: 1fb3125
27 interesting tests: 18 flaky, 7 KNOWN, 1 SKIP, 1 RECOVERED
Top 50 slowest tests (at least 2 minutes):
|
deco-sdk-taggingBot
added a commit
that referenced
this pull request
Dec 4, 2025
## Release v0.279.0 ### Notable Changes * New deployment engine for DABs that does not require Terraform is available to try in experimental mode. Not recommended for production workloads yet. Documentation at [docs/direct.md](docs/direct.md). ### CLI * Introduce `databricks apps logs` command to tail app logs from the CLI ([#3908](#3908)) ### Bundles * Add support for alerts to DABs ([#4004](#4004)) * Allow `file://` URIs in job libraries to reference runtime filesystem paths (e.g., JARs pre-installed on clusters via init scripts). These paths are no longer treated as local files to upload. ([#3884](#3884)) * Pipeline catalog changes now trigger in-place updates instead of recreation (Terraform provider v1.98.0 behavior change) ([#4082](#4082)) ### Dependency updates * Bump Terraform provider to v1.98.0 ([#4082](#4082))
denik pushed a commit
that referenced
this pull request
May 20, 2026
## Changes See https://github.com/databricks/terraform-provider-databricks/releases/tag/v1.98.0 The main behavioral change in Terraform provider v1.98.0 is that **pipeline catalog updates no longer trigger recreation**. The provider relaxed the `force_new` constraint on the `catalog` attribute, allowing in-place updates via `PUT` instead of requiring `DELETE` + `POST`. This affects how bundles handle pipeline catalog changes: - Changing a pipeline's catalog now performs an update operation instead of recreate - The `prevent_destroy` lifecycle no longer blocks catalog changes (since no recreation occurs) - Tests were updated to use `storage` location changes (which still trigger recreation) to properly exercise `prevent_destroy` behavior ## Why Nominal upgrade to match the SDK version. --------- Co-authored-by: Claude <noreply@anthropic.com>
denik pushed a commit
that referenced
this pull request
May 20, 2026
## Release v0.279.0 ### Notable Changes * New deployment engine for DABs that does not require Terraform is available to try in experimental mode. Not recommended for production workloads yet. Documentation at [docs/direct.md](docs/direct.md). ### CLI * Introduce `databricks apps logs` command to tail app logs from the CLI ([#3908](#3908)) ### Bundles * Add support for alerts to DABs ([#4004](#4004)) * Allow `file://` URIs in job libraries to reference runtime filesystem paths (e.g., JARs pre-installed on clusters via init scripts). These paths are no longer treated as local files to upload. ([#3884](#3884)) * Pipeline catalog changes now trigger in-place updates instead of recreation (Terraform provider v1.98.0 behavior change) ([#4082](#4082)) ### Dependency updates * Bump Terraform provider to v1.98.0 ([#4082](#4082))
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 freeto 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
See https://github.com/databricks/terraform-provider-databricks/releases/tag/v1.98.0
The main behavioral change in Terraform provider v1.98.0 is that pipeline catalog updates no longer trigger recreation. The provider relaxed the
force_newconstraint on thecatalogattribute, allowing in-place updates viaPUTinstead of requiringDELETE+POST.This affects how bundles handle pipeline catalog changes:
prevent_destroylifecycle no longer blocks catalog changes (since no recreation occurs)storagelocation changes (which still trigger recreation) to properly exerciseprevent_destroybehaviorWhy
Nominal upgrade to match the SDK version.