Hey everybody I'm using projects and when deployi...
# ask-community
m
Hey everybody I'm using projects and when deploying some flow, the
deployment.yaml
file is all empty as you can see on the 🧵 Is this file supposed to be filled with some informations such as work_pool?
a
Yes, you can give information for creating deployments in this file or via options provided when running
prefect deploy
. This section of the docs provides an overview of the
deployment.yaml
file when using a Prefect project: https://docs.prefect.io/latest/concepts/projects/#the-deployment-yaml-file
m
Hey @alex thanks for answering me I'm running this cli command:
prefect deploy alocacao/alocacao.py:main -n alocacao-deploy  -p alocacao-work
Isn't this supposed to be enough to add the data inside deployment.yaml?
a
Yes, that is enough info to create a deployment, and a deployment should have been created as long as the flow and work pool referenced exist. However, those values won’t be added to
deployment.yaml
when running
prefect deploy
. Instead you would add those values yourself and commit them to source control.
m
I think I'm bit confused right now Before projects, when running the prefect deploy I would usually have this .yaml as output:
with projects, I should fill the values (name, version, work_pool etc) manually?
a
Yes, you should either add the values you want to your
deployment.yaml
file, or provide those values via the CLI. yYes,
m
This is the point, I'm passing the name and the work pool already via cli
prefect deploy alocacao/alocacao.py:main -n alocacao-deploy  -p alocacao-work
at least these two values didn't should be filled on the deployment.yaml? Or am I missing something?
a
I recommend filling them in the
deployment.yaml
file, but if you provide the deployment name and entrypoint via the CLI, nothing is required in
deployment.yaml
. The CLI options and the
deployment.yaml
file values are used together to create a deployment.