Is there a way to have a shared variable available across all the ops within a job, whose value can also be updated by a certain op in the job? Essentially, an editable environment variable for a job.

You mean something like this? https://docs.dagster.io/concepts/configuration/config-schema#passing-configuration-to-multiple-ops-in-a-job

Yes but I also need the ability to update that resource's value from each op. For example, consider a STATUS resource for which I want value to be updated as it moves through different stages - first op will set it as Started, second op will update it to InProgress and third will update it to Completed.

@Anoop Sharma there’s no mechanism for that currently. I think your best bet at the moment would be to have some resource that’s backed by a persistent store, since there’s no guarantees that the ops would execute in the same process or even on the same machine (depends on the executor / run launcher).

Got it. Thanks.