@Dorian Vanunu RE your question about event based cache invalidation

102 lab instructions: • Make a new flow that grabs different weather data from open-meteo • Add retries • Add a subflow that transforms or aggregates the data • Start a Prefect server instance • Run your flow • Inspect in the UI • Stretch: add caching

Share your 102 code in this 🧵:

We’ll get back together in the main channel at 2pm ET. Feel free to take a break before then. 🙂

if you encounter an error that says:

database is locked

🧵

103 Lab Instructions • Use a previously made flow • Use Prefect Cloud • Make an email notification automation for flow run completion • Run the flow a few times • Check out the event feed in the UI • Stretch: create a Slack notification automation

📣 A few notes on the lab 📣 • Make sure to create a workspace in Prefect Cloud • Then make sure to sign in using

prefect cloud login

• Run your flow again and you’ll see it pop up on the flow runs tab • Now you’ll be able to automate against it

Slack tips if you work on that 🧵:

🙂 We’ll get back together at 3pm ET. Give yourself a break before then!

Home stretch! ⚡️

pip install -U prefect

to upgrade

104 Lab Instructions • If you have flow function parameters, create default arguments in your flow function • Make a deployment via interactive CLI commands • Start a worker • Run a deployment from the UI • Check out the deployment and flow run in the UI • Stretch 1: create a deployment in the root of your local repo with prefect project init • Stretch 2: run your second deployment with a different work pool and worker (specify worker when you create deployment)

Let’s get back together at 3:45pm ET to wrap up for the day. 🙂

Give me 🚀 if you got a deployment running, please.

👋 We’ll kick off at noon ET in Zoom!

Good morning y'all! Attached please find the viewing link for yesterday's training. Passcode is SnqK1h&b. Feel free to share with anyone who could not make it.

What are you into in the winter? Popcorn question on mic. ❄️

Could you please send the zoom link for today session

Haha love the hamster GIF Jeff

Nifty cron helper website: https://crontab.guru/

@Jeff Hale or @Emil Christensen could one of you post the lab goals?

This message was deleted.

• Create a deployment with an entrypoint flow with several parameters • Edit the deployment from the UI to override the parameters • Add two types of schedules - add each a different way (CLI, UI) • Pause the schedules • Create two kinds of artifacts in your flow code code • See your artifacts in the UI • Stretch: use a variable in your flow

We're running into this error in Room 2 - any thoughts on what could be the issue causing this error? 🧐

We’ll touch on this when we return, but one thing to keep in mind when running flows and creating deployments is which work pool you’re using. If you haven’t already, you should create a process work pool. You can do this automatically when you start a worker:

prefect worker start --name default --type process

Then when you create deployments, make sure to reference the pool. For example,

prefect deployment build ... --pool default ...

We’ll regroup at 1pm ET. Feel free to take a break prior. 🙂

Share your code from 105 lab in this 🧵:

Lab 201 instructions: • Make a deployment that uses Docker • Create a work pool and worker for the deployment • Run the deployment • Stretch 1: push the image to Docker Hub • Stretch 2: use Kubernetes Stretch 3: tag your deployment with a git SHA using _run_shell_script_ *new in 2.10.13

if anyone’s free to pop into breakout room 1, we’re getting a little tied up on the expected

requirements.txt

location