hi! I would like to understand a bit more how is people calling the code for the flows. So far what we are doing is having 1 repo with many flows. Then a build script that will create 1 single docker image, then assign that single docker storage to all flows (basically like

for flow in flows: flow.storage = docker

) and register the flows. This allows for easily reuse the same image, dependencies, etc. Now I've started a new project integrating feast and I want to have some flows to materialize the views. That means I guess having 1 flow per thing I want to materialize, then following the same pattern as above but on a different project. Starts to be a bit of too much repetition (although it works well tbh). Is other people doing something similar? How do you deal with distributing the code for the flows? I can only find using docker images because the flows often have dependencies on other python modules.

Interesting approach! Instead of looping over flows before registration in order to attach storage to each, you may approach it via a shared function. But there is no right or wrong here, the for-loop approach is totally valid, too! It may be worth noting: when you run flow locally, then storage and run configurations are ignored, so attaching it directly to the Flow object is fine and won't result in flow registration when triggering a local run.

How do you deal with distributing the code for the flows?

One idea worth exploring is using flow storage purely for flow code (e.g. using S3 or GitHub) and then packaging code dependencies via a separate mechanism. The most convenient approach is building a custom package since for local development, you can even install that in editable mode if you want, and use the same logic to python code dependencies for production by installing the same package within your Docker image

Yes I'm just being lazy and delaying the upgrade, but I say that's easier probably I should start there :P

If you are on a self-serve tier, you would need to sign up for Cloud 2.0 account here and get started as shown here. For agent/infra setup, we will build more and more examples under this Discourse tag if you are on Enterprise, you can talk to Sales and they have a cool process to make migration easy: sales@prefect.io

amazing, thank you. @Anna Geller