Hello, has anyone encounted an error while setting

is_schedule_active

property in deployment.yaml? Error:

'deployments/func-deployment.yaml' did not conform to deployment spec: ValidationError(model='Deployment', errors=[{'loc': ('is_schedule_active',), 'msg': 'extra fields not permitted', 'type': 'value_error.extra'}])

This is using S3 block storage. If using LocalFileStorage, I believe this error does not occur. Prefect version: 2.3.2 Removing the field:

is_schedule_active: false

, the deployment can be applied successfully, but the user would need to login to the UI to manually disable the schedule. This is especially painful if triggered on each CI/CD run.

I have great news, this PR adds commands: prefect deployment pause-schedule flow/deployment, same with resuming and setting schedules from CI CD https://github.com/PrefectHQ/prefect/pull/6697

Thanks Anna ! Great to know

@Anna Geller can we deactivate/pause a schedule by default after deploying via Python script when using

Deployment.build_from_flow()

?

no, but you can do that in a single command e.g. from your CI/CD:

prefect deployment pause-schedule flow/deploy

But in this case I have to switch between CLI and Python script between my deployment...not ideal.

I'd recommend CLI, it's better UX and better for CI/CD

We decide to go down the Python road because we also need to deploy blocks which is not possible over CLI. And there are other benefits like handle parameters, using Python constants/functions etc...

not yet, but certainly will be in the Future, plus you could do both from CI/CD or IaC when needed - example https://github.com/anna-geller/dataflow-ops/blob/main/.github/workflows/ecs_prefect_agent.yml