Andreas Nigg

09/14/2022, 9:44 AM
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.
:blob-attention-gif: 8
πŸš€ 3
πŸ‘ 1
:thank-you: 3
πŸŽ‰ 5
❀️ 5

Anna Geller

09/14/2022, 10:42 AM
Also shoutout to @Dustin Ngo who added all those CLI enhancements!
πŸ™Œ 2

Blake Hamm

09/14/2022, 3:32 PM
Same same! Cheers to the Prefect team πŸ’―
:thank-you: 1

CA Lee

10/17/2022, 1:58 PM
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
  cron: * * * * * 
  timezone: ...
  day_or: true
Is this expected behavior?

Anna Geller

10/17/2022, 9:07 PM
@CA Lee could you open a GitHub issue with a minimal reproducible example and share here? not enough information to say atm