Uh oh!
There was an error while loading. Please reload this page.
test-only: Add cascade field to pipeline resource for destroy - #5874
Closed
andrewnester wants to merge 2 commits into
Closed
test-only: Add cascade field to pipeline resource for destroy#5874andrewnester wants to merge 2 commits into
andrewnester wants to merge 2 commits into
Conversation
Add a `cascade` field to the pipeline bundle resource that controls whether destroying a pipeline also deletes its datasets (materialized views, streaming tables, and views). When unset, the server default applies (cascade); set `cascade: false` to retain the datasets on destroy. The field is delete-time only: it is not part of the pipeline spec, so it is never sent on create/update. The direct engine persists it in state (via a PipelineState wrapper around CreatePipeline, mirroring the sql_warehouse lifecycle pattern) and reads it at delete time, force-sending cascade so an explicit false survives query-string omitempty (honored for query params as of databricks-sdk-go v0.152.0). A cascade-only change is a state-only update with no pipeline API call. cascade is classified input_only so it does not show remote drift. The terraform engine drops the field for now: the pinned provider has no such attribute yet (pending terraform-provider-databricks#5860), so terraform-engine support is a follow-up. Co-authored-by: Isaac
Contributor
Approval status: pending
|
andrewnestertemporarily deployed
to
test-trigger-is
July 9, 2026 08:53 — with 
GitHub Actions
Inactive
andrewnestertemporarily deployed
to
test-trigger-is
July 9, 2026 08:53 — with GitHub Actions
Inactive
eng-dev-ecosystem-bot
commented
Jul 9, 2026
Collaborator
Integration test reportCommit: b69096c
8 interesting tests: 4 RECOVERED, 4 SKIP
Top 10 slowest tests (at least 2 minutes):
|
lennartkats-db
approved these changes
Jul 10, 2026
Uh oh!
There was an error while loading. Please reload this page.
lennartkats-db
requested changes
Jul 10, 2026
lennartkats-db
commented
Jul 10, 2026
Contributor
@andrewnester I suppose this is you exercising the tests for a slightly older version of #5846? |
andrewnester
commented
Jul 10, 2026
ContributorAuthor
Yes, exactly, this is just to run the tests as we can't run them from forks yet |
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
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.
Used for testing: #5846