Getting back together momentarily. 🙂

Is there something presented on screen?

We’ll chat about ControlFlow tomorrow in our Bonus section if folks are interested. 🤖

103 Lab: • In the UI, make a Slack notification automation for a flow run completion ◦ ❗️use an Email block type • Check out the event feed in the UI • Create a Markdown artifact that prints a weather forecast in a nicely formatted table • Stretch 1: Create a flow that contains a task that takes advantage of caching

Accessing third party secrets (just in case) 🫢

Datalake example which uses event triggers and S3

Thank you all! See you tomorrow at the same zoom channel and time.

🎥 Day 1 Recording: https://us06web.zoom.us/rec/share/q1VX6iuO6pAIzjpIjGM0yzpd77fPMMJpcFc9yfh5llRkfQN2jyHX3SLo-i3EozKH.948ix3nduf1Fp-4u Passcode: Rm9*67.1

What’s one thing you learned yesterday? (thread)

What’s the one thing that’s the most fuzzy in your understanding? (thread)

Day 2 slides:

104 lab: • Create a deployment with .deploy() that uses a Process work pool to run any flow you created • Create a Process work pool from the UI • Create a deployment that references flow code stored in your own GitHub repository • Use your earlier fetch weather flow if you like • ❗️Push your code to your GitHub repo manually • Start a worker to pick up scheduled flow runs • Run it! 🚀 • Stretch 1: Pause and resume the work pool from the UI. Stretch 2: Experiment with adjusting fields in a work pool base job template. Stretch 3: If you have Docker installed: Create a deployment where you bake your flow code into a Docker image with .deploy(). • Don’t push the image to a repository (or log in + push to DockerHub). Don’t forget to: • Start Docker on your machine • Create a Docker work pool

We’ll get back together at 10am ET. Feel free to take a ☕️ break prior.

Worker flags and options 🧵

When using

run_deployment

, does the parent flow fail when the sub-flow fails?

Man. Didn't know too much about event based stuff until today. This opens up so many oppurtunities to make it more real time runs. This is awesome. Currenlty we are running so many jobs based on schedule which I don't like this will open up a lot to run much more event based and real time

Lab 105 instructions: • Create a deployment with subflows. • Create a flow that uses _run_deployment_ to run another deployment. • Stretch 1: Create a custom event in Python that triggers a notification action in an automation. • Stretch 2: Create a webhook. Create an automation that pauses work when the webhook fires.

To enable the new flow run page. Click on My Profile under the drop down on the top left in the UI. Then select Feature Previews and toggle it on.

106 lab instructions: • Create an interactive workflow that pauses a flow run for input from a user. • Create a variable in the UI or with code. Use the variable in your code. • Stretch 1: Use a compound trigger in an automation. • Stretch 2: Use a metric trigger in an automation. • Bonus: create and resolve an incident (if available).

If calling

run_deployment

from a flow: 1. The nested flow is visible in the parent flow in the UI. 2. If a bad parameter is passed to the nested flow, then the parent flow fails. 3. If an exception is raised in the nested flow so that the nested flow fails, the nested flow shows as failed in the UI, but the parent flow shows as completed.

Pulling folks back momentarily.

Variables https://docs-3.prefect.io/3.0/develop/variables#set-and-get-variables

Thank you for all your hard work and focus in this course! Please take a few minutes to fill out this feedback form let us know what went well and what we could improve for future courses. https://forms.gle/Yk83s6kjG7yeBUQw9

Talk through your use case with a Prefect Engineer: https://calendly.com/prefect-experts/prefect-product-advocates

There was a question on Wednesday about capturing events. Got a code snippet in the 🧵

Will you be posting the video if Day 2? Or did I miss that link somewhere?

🎥 Day 2 Recording link: https://us06web.zoom.us/rec/share/Mw3Rj9_YUZdh3L7QE5LXGSwzm7iIp52Z-8tAwSem4e41yLFLP0GfqTWJKYWg9LIL.Ng3DJ18etKhaCYER?startTime=1729169634000 Passcode: $wiP0j!3

archived the channel