We are trying to find a good way to build up a dependency graph from deployments so that deployments all trigger the downstream deployments that depend on them. Are there any best practices around this? I realize I could do this with automations, but there are limits to how many automations a workspace can have. On top of that, it would also be nice to have these dependencies specified as code, and to my knowledge automations can not be specified as code. I would also love for this to not be structured as subflows so that it is easy for things to be triggered in different places and there is no requirement of importing a flow into a master flow. It would also be preferred that someone could make their flow depend on an upstream flow without going into the upstream flow and adding a line at the end of the flow like

run_deployment(...)

. Plus this way would limit a flow to depend on only 1 upstream flow from finishing. I have a few ideas on how we could potentially do this, but I was wondering if anyone here has set up something like this before? It seems like something prefect could be built to handle?

Hey Nelson, thanks for this writeup. There are probably a few different ways to go about something like this, and while we can and will continue to make it more natural and ergonomic, it’s probably pushing the limits of the system as it is today. Interested to hear what others in the community might have to say, but would you be willing to hop on a call sometime this week or next to chat in more depth about your goals here?

I definitely would. Ill make time for this whenever you are free.

Great, will DM you now.