Excited about Orion. I have a question/feature request, which I think may make a lot more sense in the context of Orion than original Prefect... If I want some tasks within a flow to operate with a shared filesystem, there's not easy way to do that in Prefect if the flow as a whole is running in a distributed fashion. However, perhaps in Orion you could have some sub part of the flow which runs as though that bit of the flow was "local", i.e. you could do

[download from s3] => [unzip] => [do something interesting] => [upload to somewhere]

as a series of tasks that run sequentially on a single filesystem, but as part of a larger flow where tasks are run on entirely separate filesystems. The advantage of allowing these steps to be full-blown tasks rather than just functions is that you can get dashboard level visibility, retries, and better use of library tasks etc. A related thought - could you compile a dbt graph into a nested part of a prefect flow, so you get full visibility into what dbt is doing at the level of Prefect. That would be cool.

Hey Daniel! I love the enthusiasm and the ideas -- just to make sure I understand, are you asking for an easy way to have some tasks run distributed (e.g., with a daskexecutor) and other tasks run locally in the main flow process (e.g., with a local executor)? If so, that's definitely on our radar. Also the dbt subgraph idea is really interesting -- there are definitely ways of achieving that with Orion that were not possible in current Prefect...

yeah - that's what i meant. It sounds like Orion is going to be great!