@Javier Ochoa if i remember correctly, in prefect 1 you could associate a set of parameters with the schedule itself, and then that schedule with a flow in prefect 2 you could create a new deployment for each unique schedule you'd like to apply and do the same for parameters (overriding values as needed)

we have an ssl certificate issue when trying to run worker, room 8

We’ll get back together at 8 minutes till 10am ET. Feel free to take a quick stretch break.

Override default parameters on the deployment UI doesnt show in quick run, it still asks to provide parameters, is it a bug ?

room 6

Prefect worker (or agent) as background service - short answer, you can use systemd on linux.

tasks: if you need caching, task runners, and not to call other tasks flows: if you want an observable container for anything! (except caching and submitting to task runners 🙂 )

@Salman Mohammed here's the relevant doc on defining triggers in a

prefect.yaml

Duckers on a boat party. marvin duck 🛥️ kubernetes party

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

PACC Aug 22-23 2023 bonus - part 3.pdf

@Jeff Hale could you share the presentation recording afterward, please?

@Jeff Hale Could you please share the previous docker presentation?

@Jeff Hale On a poor network, hence asking questions here -- Any plan in pipeline to support other languages? Typescript etc? If yes, any timelines for that?

prefect-gcp library has some Vertex AI options - but not a push work pool yet.

Thank you for all your hard work! Please take 2 minutes to let us know what went well and what could be improved for future PACCs - and let us know what you’d like to see in a Pro Cert course. https://docs.google.com/forms/d/e/1FAIpQLScsy8kyDSkmI_ONrjTfyEU-MTVp8cI3pJ7EwBNGeDok_6T42w/viewform?usp=sharing

What is the expected timeline for fine-grained ACL in Prefect Cloud?

thank you

@Jeff Hale for the pro course, would be nice to get an email from Prefect. i will 100% forget to check if it's available. thx for putting on a good course. today was extra helpful!

Thanks guys, that was awesome, lots of things got much clearer now!

Feel free to connect over LinkedIn: https://www.linkedin.com/in/-jeffhale/

Thank you to everyone who filled out the feedback survey already. Please take 2 minutes to do so if you haven’t yet. 🙂

Issue is up for a GCP Vertex AI Worker type.

Day 2 Recording: https://us06web.zoom.us/rec/share/8dJsC58XSrqPlAI9c6RqbLPUA7xsoBZ-AKehCfD_RUPQ6PlOJj7T4WKk6ejWd0M.PeeylIqRZpqj_iWX Passcode: jD%YN*3%

Hello, I have a problem, I remember in the course, the team told us to use workers instead of agents. When I changed my command to use worker I get the following error, So I wonder if I am doing something wrong here:

Traceback (most recent call last):
  File "/home/javier/git/nzero/usg-prefect-2/.venv/lib/python3.9/site-packages/prefect/workers/base.py", line 784, in _submit_run
    await self._check_flow_run(flow_run)
  File "/home/javier/git/nzero/usg-prefect-2/.venv/lib/python3.9/site-packages/prefect/workers/base.py", line 770, in _check_flow_run
    raise ValueError(
ValueError: Flow run UUID('53a4f0fc-1802-4986-8a72-a15cbd1f4674') was created from deployment 'my-worker' which is configured with a storage block. Workers currently only support local storage. Please use an agent to execute this flow run.

hey prefect fam, any update on the pydantic 2 upgrade?

archived the channel