Bring your towel and join one of the fastest growing data communities. Welcome to our second-generation open source orchestration platform, a completely rethought approach to dataflow automation.

Prefect Community

What is the difference between flow.set_dependency and flow.add_edge in Prefect 1.0?

ideally, don't use any of those :joy: those are for the imperative API, which no longer exists in Prefect 2.0 - the default Prefect version now

the right way to set dependencies for tasks that don't pass data is:
• 1.0 - upstrea_tasks argument
• 2.0 - wait_for
the <http://docs.prefect.io|docs.prefect.io> + <http://docs-v1.prefect.io|docs-v1.prefect.io> will show more info

how would you use them here? <https://gist.github.com/edmondo1984/61a805b170ebed4bcb7d3ee3a84b7a2d>

When you use the @task annotation is not obvious to me how to use the upstream task

below this line <https://gist.github.com/edmondo1984/61a805b170ebed4bcb7d3ee3a84b7a2d#file-runner-py-L115> I would add a line `upstream_tasks=[setup_task]`

you don't need to wrap that in build_flow, I'd encourage taking it out

I am not sure I understood that, can you please clarify? This is very useful

I'd encourage you to check the getting started guide: <https://docs-v1.prefect.io/core/concepts/tasks.html>

even though at this point, starting with 2.0 makes more sense <https://orion-docs.prefect.io/>