Hi! The changes for V2 look interesting, and I'm excited to learn more about them. In V1, we could imperatively create `ShellTask`s and wire up dependencies with

Task.set_dependencies()

. In V2, the equivalent of the

ShellTask

class seems to be the

shell_run_command

function in the

prefect-shell

package. Additionally, V2 seems to be much more declarative with a focus on the

@task

and

@flow

decorators. Is there a way to still wire up dependencies imperatively in V2? If one did, would it be an anti-pattern? For context, we have a large set of jobs and dependencies listed in yaml files. In V1, we could parse the yaml, create ShellTasks, and wire up dependencies with

Task.set_dependencies()

. I'm looking for the equivalent in V2. I don't see references to that functionality in the V2 docs, but perhaps I'm missing it. Thank you!

check out https://discourse.prefect.io/t/can-i-define-my-tasks-as-classes-rather-than-functions/54#prefect-20-1

Thank you @Anna Geller