@Marvin In Prefect 3, I am deploying from a command line script, via

prefect --no-prompt deploy --all

with a local prefect.yaml file. Is there a way to overwrite the deployment definitions, but to not overwrite the schedule? I would like any schedule changes that are made in the Prefect Cloud UI to supercede what is pushed by my CICD system.

To address your need for overriding deployment definitions without affecting the schedule, Prefect 3.x provides a way to manage deployments through the

prefect.yaml

file and the

prefect deploy

command. However, it appears that the CLI does not have a built-in option to specifically exclude the schedule from being overwritten when deploying. Here's what you can do: 1. Manage Schedules Separately: You could set up schedules directly in the Prefect Cloud UI and avoid including them in your

prefect.yaml

file. This way, any changes made in the UI will not be overwritten by the CI/CD deployment process. 2. Custom Deployment Logic: If you need more control, you might consider creating a custom script that modifies the

prefect.yaml

file or uses the Prefect API to update deployments without changing the schedule. For more detailed information on deployment and schedules in Prefect 3.x, you can refer to the following documentation: - Deployment Mechanics - Schedule Management If you need further customization or have more specific requirements, you might need to explore Prefect's API or consider contributing to Prefect's open-source codebase to add this feature.