propagate-triggering-event - Branch - PrefectHQ/prefect

Propagates the currently triggering event (if any) for composite triggers

#17854Merged

Comparing

propagate-triggering-event

(

72a0f16

) with

main

(

0c719df

)

Untouched: 2

Ignored: 6

Benchmarks

Passed

bench_import_prefect_flow

benches/bench_import.py

1.2 s1.2 s

bench_task_decorator

benches/bench_tasks.py

-1%

449.8 µs453.7 µs

Ignored

bench_task_submit

benches/bench_tasks.py

Ignored

+16%

8.6 ms7.4 ms

bench_task_call

benches/bench_tasks.py

Ignored

-10%

156.1 ms172.9 ms

bench_flow_decorator

benches/bench_flows.py

Ignored

+12%

4.5 ms4 ms

bench_import_prefect

benches/bench_import.py

Ignored

2.7 ms2.7 ms

bench_flow_call[options1]

benches/bench_flows.py

Ignored

106.1 ms105.6 ms

bench_flow_call[options0]

benches/bench_flows.py

Ignored

-1%

157.2 ms159.4 ms

Commits

Click on a commit to change the comparison range

Base

main

0c719df

-0.17%

Propagates the currently triggering event (if any) for composite triggers Just like an event trigger, a composite trigger _may_ have a triggering event that caused it to fire (like when all of its component triggers are Reactive event triggers, a pretty common case). Here, we propagate that triggering event up through the firings so that folks can access it from templates. More importantly, this allows actions to make inferences from the triggering event (like being able to infer a deployment from it for the `PauseDeployment` action, for example).

79d42df

6 months ago

by chrisguidry

-0.24%

Merge branch 'main' into propagate-triggering-event

72a0f16

6 months ago

by chrisguidry

Home Terms Privacy Docs