@Marvin From which version of Prefect can we start using emit_event()?

I'm sorry, but I couldn't find the specific Prefect version that introduced the

emit_event()

function. You may want to check the Prefect change logs or their GitHub repository for this information.

@Taylor Curran Any luck with this?

emit_event should be available in all recent versions, what version are you on?

2.13.1

it should be available, from prefect.events import emit_event

Quick question regarding the same: We are currently deploying the flows locally using the python deploy script. In this case, how do I utilize/include the YAML file while using emit_events?

the use of emit_event should have no direct bearing on how you deploy in general, as far as the deployment story goes,

emit_event

just a regular function that you may or may not call in a flow (which happens to create an Event in the workspace indicated by your PREFECT_API_URL) what are you using emit_event for?

Context: flow1 -> flow2 Want to trigger flow3 once flow1 reaches completed state without blocking flow2's execution. Currently achieving it via hook & run_deployment(timeout = 0), would like to try out events for the same test case.

ah i see - yeah, so theres a couple ways to go about it firstly, flow runs completing is already an Event, so you dont even need to emit an event manually unless you need to distinguish between different "kinds" of completed states for flow 1, a random example being maybe "finished in under 10 mins" --> "prefect.flow-run.CompletedQuickly" event, "finished in over 10 mins" --> "prefect.flow-run.CompletedSlowly" event if all you care about is triggering flow 3 upon completion of flow 1, you just need to re-deploy flow 3 to have a trigger that `expect`s the completion flow 1 event for example here's a prefect.flow-run.Completed event, where the

related

resources are the interesting bit

Do you have any example code that I could refer to especially for this one "_if all you care about is triggering flow 3 upon completion of flow 1, you just need to re-deploy flow 3 to have a trigger that `expect`s the completion flow 1 event_".

thats the yaml trigger just above here, that would be like your flow 3 in your

prefect.yaml

. you'd replace

match_related:
        prefect.resource.role: deployment
        prefect.resource.name: the-deployment-name-for-flow-1

As I mentioned earlier, my python_deploy.py script & folder structure looks something like this:

how do I utilize/include the YAML file while using emit_events?

when i heard this i thought you meant you were switching from python deploy script to

prefect.yaml

build_from_flow

should be thought of as being deprecated (it is not literally deprecated but will be). it is for building deployments run by agents and it is not meant to be used with

prefect.yaml

you can fully define all your deployments with a

prefect.yaml

, but if you really want python deployment definitions, you can ask @Taylor Curran about .deploy, which does all the things build_from_flow does, but for workers (modern recommendation)