@Marvin Is it possible to emit an event and design the event handler without using an YAML file?

In Prefect 2.x, events are automatically emitted by various Prefect objects including flows, tasks, deployments, work queues, and logs. You can also emit custom events using the Prefect SDK by making use of the

emit_event

method to send events to the Prefect events API. For instance, the following Python code emits an event:

python
from prefect.events import emit_event

def some_function(name: str="kiki") -> None:
    print(f"hi {name}!")
    emit_event(event=f"{name}")

Regarding designing event handlers without using a YAML file, there is no direct information from the documents retrieved. However, I can gather that the event handlers configured in Prefect are tied to automations which are often defined in the Prefect Cloud UI or via code. Typically, Prefect Cloud provides an interactive dashboard for analyzing and taking action on events, thus allowing you to define your event handlers through the UI instead of using a YAML file. To create custom event handlers programmatically, you would generally define the logic inside your Prefect flows or tasks, set up automations in the UI, or use the Prefect API, depending on what exactly you are trying to achieve. If you are looking for more specific information about implementing custom event handlers in code without using a YAML file, please let me know, and I can look for more detailed instructions or examples.

what do you mean by

design the event handler

?

Get this code into the flow design without the YAML file. We're currently using a different approach to deploy the flows so using YAML config files are not an option now.

Hi Sanjeev, you all are using

.deploy()

or

build_from_flow()

for your deployments? You should be able to fill in any of the same fields.

or if you're using serve https://prefect-community.slack.com/files/U02GMEZU18B/F05R8PWR197/wait_for_upstream_deployments_py.py

Hi Taylor, Using

build_from_flow()

, does the

emit_event()

part remain unchanged?

emit event should be separate / decoupled from any deployment code like build_from_flow() what do you mean? do you guys emit events in the same scripts where you define deployments?

Oh no no. I should've been much clearer. my bad.