-
Notifications
You must be signed in to change notification settings - Fork 475
Relaxed force_new constraint on catalog attribute in databricks_pipeline resource to allow changing the default catalog for existing pipelines
#5180
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Conversation
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
pietern
reviewed
Nov 4, 2025
…s_pipeline` resource to allow changing the default catalog for existing pipelines Pipelines will still be recreated when switching between `storage` and `catalog` modes, but changing the catalog value in an existing catalog-based pipeline no longer requires recreation. Resolves #4692
a604d6b to
259d086
Compare
pietern
approved these changes
Dec 2, 2025
|
If integration tests don't run automatically, an authorized user can run them manually by following the instructions below: Trigger: Inputs:
Checks will be approved automatically on success. |
deco-sdk-tagging bot
added a commit
that referenced
this pull request
Dec 3, 2025
## Release v1.98.0 ### New Features and Improvements * Relaxed `force_new` constraint on `catalog` attribute in `databricks_pipeline` resource to allow changing the default catalog for existing pipelines ([#5180](#5180)). * Add `databricks_users` data source ([#4028](#4028)) * Improve `databricks_service_principals` data source ([#5164](#5164)) * Add `feature_engineering_kafka_config` resource and data source ([#5240](#5240)) ### Bug Fixes * Fix spurious plan diffs in `databricks_model_serving` and `databricks_model_serving_provisioned_throughput` resources due to tag reordering ([#5120](#5120)) * Move Spark Version selector defaults to Terraform ([#5219](#5219)). ### Documentation * Document tag policies in `databricks_access_control_rule_set` ([#5209](#5209)). * Document missing `aws_attributes.ebs_*` properties in `databricks_cluster` ([#5196](#5196)). * Document support for serverless workspaces on GCP ([#5124](#5124)) * Document data object types for share resource ([#5244](#5244)) ### Exporter * Added support for `databricks_data_quality_monitor` resource ([#5193](#5193)). * Added support for `databricks_account_federation_policy`, `databricks_custom_app_integration`, `databricks_quality_monitor_v2`, `databricks_service_principal_federation_policy` resources ([#5237](#5237)). * Added support for `databricks_budget_policy` resource ([#5217](#5217)). * Fix typo in the name of environment variable ([#5158](#5158)). * Export permission assignments on workspace level ([#5169](#5169)). * Added support for UC Tag policies ([#5213](#5213)). * Added support for Databricks Apps resources ([#5208](#5208)). * Added support for Database Instance resource (aka Lakebase) ([#5212](#5212)). * Added support for workspace and account settings v2 ([#5230](#5230)). ### Internal Changes * Update Go SDK to v0.92.0 ([#5240](#5240)) * Bump github.com/hashicorp/terraform-plugin-framework from 1.16.1 to 1.17.0 ([#5247](#5247))
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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
Pipelines will still be recreated when switching between
storageandcatalogmodes, but changing the catalog value in an existing catalog-based pipeline no longer requires recreation.Resolves #4692, Resolves #4567
Tests
make testrun locallydocs/folderinternal/acceptanceNEXT_CHANGELOG.mdfile