This message was deleted.

To fix the deprecation warnings you're encountering, you should migrate from using the deprecated fields in the

Deployment

object to the new approach of defining schedules. The field 'schedule' and the

is_schedule_active

flag are being deprecated, and you are advised to define schedules in the

schedules

list instead, and use the

active

flag within a schedule. According to the Prefect documentation, you can create a

prefect.yaml

file from a recipe or scratch and add the

schedule

section with specifics like

cron

expression,

timezone

, and

active

state. Schedules can be set to inactive with the

active: false

tag. You should also revise the CI/CD processes commands that are used to manage deployment schedules and replace them with any updated commands provided by Prefect which manipulate schedules according to the new structure. Unfortunately, the results don't cover the latest commands replacing the deprecated ones (

set-schedule

,

pause-schedule

,

resume-schedule

). For these command replacements, I recommend consulting the latest Prefect documentation. If detailed steps are not found there, it may be valuable to reach out to the Prefect community or review the latest changelogs for guidance on migrating these commands.