Allows individual schedules to run at a fixed timezone (overridding whatever timezone has been set on the instance).
- R1:fe88d204fa88: Add execution_timezone field to schedules
Won't this be confusing in the playground and backfill UIs now? I feel like if they want their schedule to run every hour exactly, they should use UTC execution_timezone. But if they configure an hourly schedule in a DST timezone, the partitions should be local to their timezone and the behavior at DST boundaries should be documented.
Maybe mark this argument on all the decorators with the new experimental feature flags
Where do these show up again?
Shouldn't all these tests now freeze the time in UTC?
The result would be the same even if this were 1 minute later right?
just as output in the scheduler process
For 0.10.0 IMO we should require execution_timezone on all schedules, so this should become an invariant violation
I don't think so no, there's no guarantee that the server running them will be in UTC
yeah, will update to make more clear