Add job_runs lifecycle.triggers.on_value_change - #6341
Open
radakam wants to merge 2 commits into
Open
Conversation
Re-fire a run when a resolved expression changes, including resource refs that become deploy-graph edges. Removing the trigger is a state-only update.
radakam
marked this pull request as ready for review
August 21, 2026 15:59
Contributor
Approval status: pending
|
Include the on_value_change input and state paths required by generated-file validation.
Collaborator
Integration test reportCommit: 0db1f4b
10 interesting tests: 4 SKIP, 2 KNOWN, 2 FAIL, 2 RECOVERED
|
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
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
Add
lifecycle.triggers.on_value_changeforresources.job_runs(direct engine). The run is recreated when the resolved expression changes.${resources.*}refs become deploy-graph dependencies. Multiple triggers are separate list entries (one key each). Removing the trigger updates state only and does not start a new run.Why
job_runsalready supporton_bundle_deployandon_file_change. Watching a resolved value (variable or resource id) is the remaining trigger from the job_runs design, so a run can re-fire when an upstream resource or interpolated value changes.Tests
prevent_destroy), PrepareState/PrepareInputConfig, DropJobRunValueChangeConfigRefs, OverrideChangeDesc (remove vs change).on_value_change: two expressions; changing one var recreates (other fingerprint stays); removing both triggers is an update with no run-now.on_value_change_ref: concatenated${resources.jobs.other.id}-${resources.jobs.extra.id};depends_onincludes both jobs; persisted state is[OTHER_ID]-[EXTRA_ID];READPLAN=""andREADPLAN=1.