Hello Community, We have around 50 deployments in our prefect project, each deployment has got a big/long number of parameters. We used to implement all deployment using the

Deployment

stack, each deployment in its own file, each file has a

deployment.apply()

which would deploy it when run. We are currently migrating to using

prefect.yaml

(our understanding is that

Deployment

is getting deprecated). My question is: is it normal to put all deployments in same file? this would lead to a huge yaml file that could easily become unmaintainable, if not, what do you guys use as patterns to circumvent this?

@Hamza Mogni We solved this by putting a comment part in the top of each flow:

interesting, thanks. By curiosity, how do you manage flows that have multiple deployments linked to it?

We are not using the doing things like one flow -> many deployments.

hi @Hamza Mogni - there's a --prefect-file flag for

prefect deploy

so you dont have to keep all your definitions in the same yaml file

Hello @Nate yes we are creating multiple flows for same deployments, i was only curious how they manage it using that approach (docstrings). yes I tried using

--prefect-file

but my understanding is that it only takes one file path as an argument, meaning there would be a need for a preprocessing step to merge definitions from separate yaml files into a single one and then feed the output to --prefect-file.

aha yes you're correct if deployments in all files would depend on the same definitions that would indeed be required alternatively you can use the python interface if you want to employ a modular approach to apply common deployment config and organize it however you can organize python code

ah yes, a global definitions approach would be very nice, possibly in a separate file like

global-definitions.yaml

which would be automatically picked up by prefect before applying deployments from different yaml files

yeah that sounds very doable. are you open to creating an enhancement issue for this?

yup, would like to try and work on it also but don't know where to start, might take me some considerable time to dig it

no worries! just articulating the problem in an issue would be helpful but i can do so later if not

yes will definitely create the issue as a first step 👌