Good morning! I'd like please ask if events and blocks are not available for Prefect server running in EKS, for example.

To clarify, the worker does not execute the

@flow

code, it's just responsible for launching the environment (process, container, ECS task, etc.) to run the flow function?

Are the slides for today already posted somewhere?

Thanks!

Day 2 Slides:

104 Lab - 🧑‍🔬 👩‍🔬 Use a flow from the 103 lab • Make a deployment via interactive CLI commands • Start a worker • Run a deployment from the UI • See the flow run logs in the UI • Stretch: Create a deployment that has default parameters & override the default parameters at runtime in the UI

GitHub Repo for PACC incase you need it. G ✨

We’ll regroup at 9:50am ET. Feel free to take a break prior to that. 🙂

How was the 104 lab? (emoji)

So a flow contains its code, its task runner definition, etc., a work pool knows where/how flows get executed (infra), and a deployment is a named binding of a flow to a work pool (many-to-many)?

So if a flow calls another flow function directly, the subflow function code runs in the same process+infra as the parent flow function; but it sounds like a flow can instead launch a deployment, in which case that subflow gets launched on new infra and is monitored remotely via the API? Either way, the flow runs for all subflows will still appear in the UI as shown in the slides?

Are there any plans to offer automations and events in the OSS offering, or is this expected to remain a proprietary feature of Prefect Cloud?

BTW Marvin's awesome! We use it internally and absolutely love it!

When it comes to RRules, is it possible to stack multiple RRules with multiple black out dates?

Posting my question from the call: What's the right way to remove deployments from a prefect environment via CI/CD processes. Along the same lines, are there any suggestions for promoting blocks between prefect environments (i.e. dev->stage->prod)?

105 Lab - 🧑‍🔬 👩‍🔬 • Create a deployment that uses one of the new workflow patterns you’ve seen in this module. • See the prefect.yaml. Use GitHub or other git-repo-based code storage. ◦ Don’t forget to push your code! • Add a schedule. • Pause the schedule.

Workflow Design Patterns blog post if you want to read more.

Beyond Scheduling: Event-Driven Flows with Prefect 🚀 (using webhooks and automations)

Here’s a blog post with an example of using event-based deployments with Prefect, webhooks, GitHub, and Marvin.

We’ll get back together in 7 minutes at 10:52am ET. Feel free to take a break prior. 🙂

If work pools have a type, and workers have a type, what does it mean to start a worker with a type that doesn't match its workpool?

Bonus content slides:

Work Queues info in docs.

Please take 2 minutes to fill out our feedback survey. We are always working to improve this course and hear what you’d like in an advanced course: https://forms.gle/cQzCGJtVFMQs7qNV9

Thank you all for your hard work and focus! prefect spin

Book a Rubber Duck session to talk through your use case: https://calendly.com/prefect-experts/prefect-product-advocates

Feel free to connect on LinkedIn and stay in touch! https://www.linkedin.com/in/-jeffhale/

Hello @Jeff Hale, could you please post the recording of the latest class? Thank you.

Day 2 recording: https://us06web.zoom.us/rec/share/YGEjZ6zjPHLN_h-wHZzaFyhbotX8B0jrpwIn_VXAj-aM_7Ql76d2AAx38bhgcnEG.oGLpIVC3Qt4hMyZz?startTime=1694695654000 Passcode: 2=EN%1#9