Would it be reasonable to add a

timezone

attribute to

FreshnessPolicy

? Here’s my use-case: we have a provider that makes a dataset available every day at 2AM local time. I’d like to make a

FreshnessPolicy

with

maximum_lag_minutes=24*60

and a

cron_schedule=0 2 * * *

but the cron schedule is in UTC, so I have to adjust, e.g.:

cron_schedule=0 7 * * *

but because of daylight savings 😭, I actually have 2 different “UTC hour” to provide, (e.g.:

7

and

6

or whatever), which is not possible (without restarting the server). I’ve mentioned timezones in the past, not sure if there are any plans to formalize that a little more within Dagster; this would be another use case.

Hey @Philippe Laflamme - mind filing a github issue for this? It's a very reasonable request. cc @owen

Done: https://github.com/dagster-io/dagster/issues/12006