Hello, I'm a newbie to dagster coming from airflow. I often used jinja templates to make sure my dags were idempotent in regards to the date of execution via

{{ds_nodash}}

. Does anyone know how to achieve the same thing with dagster ? I would love a pointer to the documentation in regards to this feature. It constitutes a crucial element that could entice my team to move from airflow. Thanks !

this is an interesting question for me, like how do I know the last successful run of a job or the last materialization of an asset?

Here is a more complete description of the problem if it interests anyone... https://stackoverflow.com/questions/73601292/how-to-specify-use-idempotent-date-of-execution-within-dagster-assets-jobs

one option is to use a custom run_id or run_key. that's how some are doing this. but it will not help with last execution dates

It's not possible to get a list of executions via the Metadata or write to the Metadata??

If your asset is partitioned, or time partitioned, in an Op function you can provide a ‘context: OpExecutionContext’ parameter as the first parameter that will have access to

context.partition_key

or

context.partition_time_window

https://docs.dagster.io/_apidocs/execution#dagster.OpExecutionContext

other I know are tags : https://docs.dagster.io/concepts/ops-jobs-graphs/metadata-tags#specifying-tags