From 5ee298dfc242d4970339bb9559aab5ddde90ffe7 Mon Sep 17 00:00:00 2001 From: Nathan Nowack Date: Fri, 8 Sep 2023 12:03:07 -0500 Subject: [PATCH] a couple words --- flows-advanced/using_state_hooks/README.md | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/flows-advanced/using_state_hooks/README.md b/flows-advanced/using_state_hooks/README.md index 924cd3a8..83dc58d4 100644 --- a/flows-advanced/using_state_hooks/README.md +++ b/flows-advanced/using_state_hooks/README.md @@ -6,13 +6,14 @@ This recipe demonstrates two different ways to trigger a deployment when a Prefe #### Method 1: `run_deployment` in a state hook -- **Direct Invocation**: Directly calls `run_deployment` to trigger the downstream deployment. -- **Parameter Passing**: Passes the result of the upstream flow run as a parameter to the downstream deployment. +- Directly calls `run_deployment` to trigger the downstream deployment. +- Passes the result of the upstream flow run as a parameter to the downstream deployment. #### Method 2: `emit_event` in a state hook -- **Event-based Invocation**: Emits a custom event using `emit_event` that is meant to trigger the downstream deployment. -- **Configuration**: Allows for more flexible triggering logic, as defined in `prefect.yaml`. +- Emits a custom event using `emit_event` that is meant to trigger the downstream deployment. +- Again, passes the result of the upstream flow run as a parameter to the downstream deployment, but via the event payload. +- Allows for more flexible triggering logic / downstream actions, defined in a trigger attached the deployment in `prefect.yaml`. ---