feat: dry-run shadow mode for pipeline evaluation#66
Merged
dwsmith1983 merged 5 commits intomainfrom Mar 12, 2026
Merged
Conversation
Observation-only mode that evaluates trigger conditions, validation rules, and SLA projections against real sensor data without executing jobs or starting Step Functions. Publishes DRY_RUN_WOULD_TRIGGER, DRY_RUN_LATE_DATA, DRY_RUN_SLA_PROJECTION, and DRY_RUN_DRIFT events to EventBridge for comparison against the existing orchestrator.
github-actions
bot
added
tests
Remove unused sensorData parameter from handleDryRunTrigger (unparam), invert nested if-blocks to use continue (gocritic nestingReduce), and assign v0.9.0 to the dry-run changelog entry.
Addresses common misidentification of Interlock as an orchestrator. New "What Interlock Is (and Isn't)" section clarifies that Interlock is a safety controller that gates the trigger path — not a scheduler or orchestrator replacement.
Cancel previously only published SLA_MET and swallowed BREACH, leaving reruns with no SLA outcome notification. Now always publishes a binary MET or BREACH verdict and propagates publish errors so the step function can retry on transient failures. Also adds RERUN_ACCEPTED and JOB_COMPLETED to the EventBridge alert filter so rerun lifecycle events reach Slack.
Add dedicated guide page walking through the end-to-end dry-run workflow: setup, evaluation flow, monitoring events, SLA projection, drift detection, going live, and troubleshooting. Add missing _index.md for the guides section with card navigation.
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
1 participant
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.
Summary
dryRun: truemode that evaluates trigger conditions, validation rules, and SLA projections against real sensor data without executing jobs or starting Step FunctionsDRY_RUN_WOULD_TRIGGER,DRY_RUN_LATE_DATA,DRY_RUN_SLA_PROJECTION,DRY_RUN_DRIFThandleSLACalculatefor consistent deadline resolutionChanges
pkg/types/pipeline.go—DryRun boolon PipelineConfigpkg/types/events.go— 4 new event typespkg/types/dynamo.go—DryRunSK()helperinternal/store/control.go—WriteDryRunMarker(conditional write) /GetDryRunMarker(consistent read)internal/lambda/dryrun.go— core dry-run logic (handleDryRunTrigger, handleDryRunPostRunSensor, publishDryRunSLAProjection)internal/lambda/stream_router.go— dry-run branch after calendar exclusion checkinternal/lambda/postrun.go— dry-run branch for post-run driftinternal/validation/config.go— dryRun requiresjob.typeandschedule.trigger