Hi- if you have some common code that should be shared between flows (let's say creation of some common resource, or a custom task type) what's the best way to lay this out? I'm currently putting this in a separate library and making sure it's available in the docker base image, but it feels a bit suboptimal as the only point of this code is to be used by the flows and so ideally it would live alongside them. Is there something better I can do here?

Hi @Chris Martin - I think that's the best pattern at the moment, outside of creating a pip-installable package that you can include in your flows. I'd encourage you open an issue with a description of what you'd like to see!

Hi @nicholas I've raised https://github.com/PrefectHQ/prefect/discussions/3077