job_runs: plan skip for in-progress runs and trigger removal - #6357
Merged
Merged
Conversation
radakam
marked this pull request as ready for review
August 24, 2026 10:04
Collaborator
Integration test reportCommit: 59d0cb6
6 interesting tests: 4 SKIP, 1 RECOVERED, 1 flaky
Top 7 slowest tests (at least 2 minutes):
|
denik
approved these changes
Aug 24, 2026
Keep update semantics for adopting an in-progress run while moving its wait to the framework hook, and treat removal of on_bundle_deploy as unchanged.
radakam
force-pushed
the
job-runs-fix-update-actions
branch
from
August 24, 2026 11:00
c8fbdd5 to
86fe2a3
Compare
radakam
enabled auto-merge
August 24, 2026 11:00
denik
reviewed
Aug 24, 2026
denik
self-requested a review
August 24, 2026 11:08
Contributor
I don't understand this. Why not: "plan skip rather than update when job run is in progress" |
radakam
disabled auto-merge
August 24, 2026 11:11
A run that is still going should not be recreated, but skip is the plan action that leaves it alone. That also drops DoUpdate, so an interrupted wait is not resumed; interrupted_run records that limitation.
radakam
changed the title
denik
approved these changes
Aug 24, 2026
denik
left a comment
denik
left a comment
Contributor
There was a problem hiding this comment.
Should be included in .nextchanges as well, since it's affects user-visible plan
Collaborator
Integration test reportCommit: 15e3d2f
68 interesting tests: 32 FAIL, 32 flaky, 2 SKIP, 1 KNOWN, 1 RECOVERED
Top 50 slowest tests (at least 2 minutes):
|
deco-sdk-tagging Bot
added a commit
that referenced
this pull request
Aug 26, 2026
## Release v1.14.0 ### Notable Changes * Bundles still on Terraform state are now migrated to the direct engine automatically, after a deploy whose dry-run conversion comes back clean. To opt out, set `engine: terraform` under `bundle` or `DATABRICKS_BUNDLE_ENGINE=terraform`. See https://docs.databricks.com/aws/en/dev-tools/bundles/direct ### CLI * Fixed idle `databricks ssh connect` sessions disconnecting after a few minutes, on dedicated clusters and on serverless. The tunnel now keeps itself warm: the SSH client and the SSH server on the compute exchange keepalives every 30 seconds, and the CLI's proxy pings the tunnel's websocket every 20 seconds. A session nobody is typing into stays connected, with no need to set `ServerAliveInterval` by hand. ### Bundles * `bundle plan` no longer reports a permanent, unconvergeable update on `securable_kind` for Unity Catalog `TABLE` securables declared under an app's `resources`. The field is computed by the backend (output-only), so it is now ignored during drift detection. Direct engine only ([#6342](#6342)). * Add support for the `cluster_policies` resource type in Declarative Automation Bundles. Cluster policies are only supported in direct deployment mode. * `bundle destroy` no longer counts resources that are already gone remotely in its `Destroy: N deleted` summary. Such deletes only clean up stale state and are not listed under the deletion prompt, so they are now excluded from the count as well, matching the terraform engine. * `bundle destroy` now also removes the directory named after the bundle, not just the target directory beneath it, when `workspace.root_path` ends in `${bundle.name}/${bundle.target}` — which includes the default root path. It is removed non-recursively, so it stays in place while another target of the same bundle is still deployed there. Previously every destroy left an empty directory behind ([#6317](#6317)). * `job_runs` now plans skip for a run that is still in progress and when `on_bundle_deploy` is removed, instead of treating either case as an update. ([#6357](#6357)) * Added `DATABRICKS_BUNDLE_RESOURCE_MAX_WAIT` (in seconds) to cap how long deploy and destroy wait for a resource. Direct engine only. * Fixed `bundle deploy` on the direct engine failing with `Nothing to update`, or reporting a change it never applied, when a schema, catalog, volume, registered model or external location field was removed from the configuration or set outside the bundle. The update now sends the fields the plan reports as cleared instead of dropping them. ### Dependency Updates * Bump `github.com/databricks/databricks-sdk-go` from v0.171.0 to v0.175.0 ([#6322](#6322)). * Bump Terraform provider from v1.127.0 to v1.128.0 ([#6323](#6323)).
janniklasrose
pushed a commit
that referenced
this pull request
Sep 15, 2026
## Changes - Plan skip for an in-progress run instead of update, and drop `DoUpdate`. - Plan skip when `on_bundle_deploy` is removed, instead of a state-only update. ## Why A run that is still going should not be recreated, but skip is the action that leaves it alone. That also means an interrupted wait is not resumed. Removing a trigger requires no action: it should neither re-run the job nor report a resource update. ## Tests `interrupted_run` asserts skip for an in-progress run and records the Badness that the next deploy does not wait. `on_bundle_deploy` covers trigger removal as unchanged.
janniklasrose
pushed a commit
that referenced
this pull request
Sep 15, 2026
## Release v1.14.0 ### Notable Changes * Bundles still on Terraform state are now migrated to the direct engine automatically, after a deploy whose dry-run conversion comes back clean. To opt out, set `engine: terraform` under `bundle` or `DATABRICKS_BUNDLE_ENGINE=terraform`. See https://docs.databricks.com/aws/en/dev-tools/bundles/direct ### CLI * Fixed idle `databricks ssh connect` sessions disconnecting after a few minutes, on dedicated clusters and on serverless. The tunnel now keeps itself warm: the SSH client and the SSH server on the compute exchange keepalives every 30 seconds, and the CLI's proxy pings the tunnel's websocket every 20 seconds. A session nobody is typing into stays connected, with no need to set `ServerAliveInterval` by hand. ### Bundles * `bundle plan` no longer reports a permanent, unconvergeable update on `securable_kind` for Unity Catalog `TABLE` securables declared under an app's `resources`. The field is computed by the backend (output-only), so it is now ignored during drift detection. Direct engine only ([#6342](#6342)). * Add support for the `cluster_policies` resource type in Declarative Automation Bundles. Cluster policies are only supported in direct deployment mode. * `bundle destroy` no longer counts resources that are already gone remotely in its `Destroy: N deleted` summary. Such deletes only clean up stale state and are not listed under the deletion prompt, so they are now excluded from the count as well, matching the terraform engine. * `bundle destroy` now also removes the directory named after the bundle, not just the target directory beneath it, when `workspace.root_path` ends in `${bundle.name}/${bundle.target}` — which includes the default root path. It is removed non-recursively, so it stays in place while another target of the same bundle is still deployed there. Previously every destroy left an empty directory behind ([#6317](#6317)). * `job_runs` now plans skip for a run that is still in progress and when `on_bundle_deploy` is removed, instead of treating either case as an update. ([#6357](#6357)) * Added `DATABRICKS_BUNDLE_RESOURCE_MAX_WAIT` (in seconds) to cap how long deploy and destroy wait for a resource. Direct engine only. * Fixed `bundle deploy` on the direct engine failing with `Nothing to update`, or reporting a change it never applied, when a schema, catalog, volume, registered model or external location field was removed from the configuration or set outside the bundle. The update now sends the fields the plan reports as cleared instead of dropping them. ### Dependency Updates * Bump `github.com/databricks/databricks-sdk-go` from v0.171.0 to v0.175.0 ([#6322](#6322)). * Bump Terraform provider from v1.127.0 to v1.128.0 ([#6323](#6323)).
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
DoUpdate.on_bundle_deployis removed, instead of a state-only update.Why
A run that is still going should not be recreated, but skip is the action that leaves it alone. That also means an interrupted wait is not resumed.
Removing a trigger requires no action: it should neither re-run the job nor report a resource update.
Tests
interrupted_runasserts skip for an in-progress run and records the Badness that the next deploy does not wait.on_bundle_deploycovers trigger removal as unchanged.