@Marvin when I do prefect deploy --all, it turn all the flows in deployment ON, I would like do keep the deployments as is

To help you with your query about using

prefect deploy --all

, I need to understand which version of Prefect you are using, as the behavior of this command can vary between versions. Could you please confirm your Prefect version? If you're not sure, you can check using the command

prefect --version

.

@Marvin 2.20.1

In Prefect 2.x, the

prefect deploy --all

command is used to deploy all deployments. However, it does not specifically control whether the deployments are activated or turned off. This command simply ensures that all specified deployments are updated based on their current configuration. If you're looking to manage the state of your deployments (keeping some off or inactive), you would need to control that through your deployment configuration or by deploying each one individually with specific parameters. Based on the Prefect 2.x documentation, here's what you should consider: - Deployments don't have an inherent "on" or "off" state in the way you're describing. You might be confusing deployment with scheduling or other operational controls. - If your goal is to manage active schedules, you should look into flow schedules and ensure that the schedules are either enabled or disabled as needed. You can find more details in the Prefect 2.x deployment guides: https://docs-2.prefect.io/latest/guides/prefect-deploy/ To achieve precise control, you may need to use specific deployment patterns or manage schedules directly in your Prefect infrastructure.