Just a shoutout to the prefect team for v2.4.0. 🎉 😛arty-parrot: This release actually solves my two last annoyances I had with prefect 2.0, namely not being able to set custom parameters and schedule timezones via CLI. • Support for setting custom parameter values directly from the deployment build CLI • New CLI for interacting with and setting custom timezone-dependent schedules for your deployments incl. the ability to pause or resume a schedule directly from the CLI Thanks to the team for this awesome release and it's incredible to see how fast prefect 2.0 moves in the perfect direction.

Also shoutout to @Dustin Ngo who added all those CLI enhancements!

Same same! Cheers to the Prefect team 💯

Hello, so I was trying out the CLI commands for setting timezones / schedules 1. build 2. apply 3. set-schedule I ran the above commands in the order shown, and I noticed that the schedule and timezone were updated in the UI, but not in the deployment.yaml file Observed:

schedule: null

Expected:

schedule:
  cron: * * * * * 
  timezone: ...
  day_or: true

Is this expected behavior?

@CA Lee could you open a GitHub issue with a minimal reproducible example and share here? not enough information to say atm