job_runs: add lifecycle.triggers.on_file_change - #6309
Conversation
Integration test reportCommit: 17857f9
7 interesting tests: 4 SKIP, 3 flaky
Top 15 slowest tests (at least 2 minutes):
|
Approval status: pending
|
b8c20f6 to
8744e5e
Compare
8744e5e to
47994d8
Compare
|
|
||
| t.Run("unset", func(t *testing.T) { | ||
| state := (&ResourceJobRun{}).PrepareState(&resources.JobRun{}) | ||
| assert.Nil(t, state.Lifecycle) |
There was a problem hiding this comment.
not sure this adds coverage on top of acc tests?
There was a problem hiding this comment.
could you review other tests in job_run_test.go as well; if they are not covered by acc tests, should we add acc test instead?
There was a problem hiding this comment.
Good point, dropped duplicates and added destroy_unfinished_run acceptance test to convert a few more, I think it makes sense to keep the remaining tests here. What do you think?
Re-fire a run when matched file contents change, using stable hash fingerprints so mtime-only updates (touch) do not recreate.
Satisfy the linter on PrepareState literals after adding OnFileChange, and refresh out.fields.txt so validate-generated stays green.
Reject patterns outside the sync root and directory-only matches so the trigger cannot fingerprint escaped paths or silently disarm.
Drop size/mtime fingerprints and the resolve fast path so content identity alone drives recreate, and touch no longer needs a planner exception.
The modernize linter rejects the manual m[k]=v copy loop, failing CI lint.
Honor .gitignore and sync.exclude when hashing matches. Cover mysubdir globs, READPLAN, and keep LF on Windows so restored files hash cleanly.
The glob test edits migrations/ignored.txt, but the test .gitignore excluded it from the commit so CI clones would miss the file.
Plan serialization is already covered by on_file_change; the glob cases only assert the hash map.
Cover deploying glob hashes from a saved plan, not only from a live re-plan.
Keep the gitignore fixture as dot_gitignore so it does not affect the repo while developing, drop unit tests that duplicate acceptance coverage, and allocate trigger state once when a trigger is armed.
The previous simplification omitted OnBundleDeploy from the struct literal, which the linter rejects.
Always persist the same lifecycle.triggers shape so trigger fingerprints compare at the same paths. Wrap on_file_change hashes in files so dropping the trigger updates instead of recreating.
Nest lifecycle by value so structdiff descends to the leaf that changed instead of reporting the whole subtree, and let RemapState supply the empty shape. GetRun never returns the fingerprints, so the remote type no longer advertises a lifecycle it cannot fill.
Drop the files wrapper so plan diffs land on lifecycle.triggers.on_file_change, matching the config path without an extra state-only level.
The trigger, PrepareState and OverrideChangeDesc cases are asserted end to end by on_bundle_deploy and on_file_change, so the unit copies only duplicated goldens. Keep the ones acceptance cannot reach without stubbing GetRun.
Flattening on_file_change to a map made an unarmed trigger drop out of the serialized state, so the three plans that print an unarmed job_run now report an empty triggers object.
The unit test staged an asynchronous cancellation by hand; the acceptance test shows the real request order a user's destroy produces. Also drops two unit tests that the on_file_change acceptance tests already cover.
Directory-only and sync-excluded matches silently disarmed the trigger. Treat them as errors, warn that ** is not recursive, and cover both in acc.
The goldens were captured against a one-line-taller databricks.yml, so CI failed after the source settled on line 24.
Clearing a trigger is now a skip, so the plan reports the run as unchanged and the deploy makes no API call.
0756969 to
4e7b960
Compare
| "seed.txt": "" | ||
| } | ||
| }, | ||
| "lifecycle.triggers.on_file_change['seed.txt']": { |
There was a problem hiding this comment.
Non blocking but still a bit weird that have both "lifecycle.triggers.on_file_change['seed.txt']" and "lifecycle.triggers.on_file_change" here.
Patterns must still land under the sync root. Reject **, warn when a glob matches directories, and skip only when the trigger itself is cleared.
Changes
Add
lifecycle.triggers.on_file_changeforresources.job_runs(direct engine).touchdoes not re-fire..gitignoreandsync.exclude).lifecycle.triggers.on_file_changepath-to-hash map, nested by value so a plan diff lands on the file.prevent_destroy. Warn when a pattern matches nothing, and when**is used, sincefilepath.Globtreats it as a single*.Why
Users need to re-run a job when local inputs change (SQL migrations, notebooks, configs) without re-firing on every deploy. Content hashes keep the trigger stable under sync noise while still catching real edits.
A pattern that resolves to nothing would silently disarm the trigger, so the cases that cannot re-arm later (directory-only and sync-excluded matches) are errors, while a pattern that matches no file yet is only a warning.
Tests
resolve_job_run_file_triggers; trigger validation for an empty pattern, both keys set, neither key set,on_bundle_deploy: false, and theprevent_destroyconflict.on_file_change— first deploy fires; unchanged redeploy andtouchplan nothing; an edit recreates (including READPLAN); deleting the file warns and re-fires; restoring it re-fires again; removing the trigger is unchanged with norun-now.on_file_change_glob—migrations/*plusmysubdir/*.txt; matches appearing and disappearing re-fire; files below the glob and gitignored files do not;**warns and matches the same files as*; READPLAN.on_file_change_errors— pattern outside the sync root, a glob matching only directories, one matching a directory plus a sync-excluded file, one matching only sync-excluded files, and the no-match warning.destroy_unfinished_run— a run left going by an interrupted deploy is cancelled before it is deleted.job_run_test.goshrinks where an acceptance test now asserts the same behavior, so coverage lives where the user-visible output is checked.