The cloud-native orchestrator for the whole development lifecycle, with integrated lineage and observability.

dagster

Is there a way to grab code location name to be shown in slack when using `make_slack_on_run_failure_sensor` ? I see it is not there in the `RunFailureSensorContext`.

hi <@U04EZSM3M8C>! It's a bit burried, but context.dagster_run.external_job_origin.external_repository_origin.code_location_origin.code_location_name should be what you want

Wow, how would I see a list of fields I an get from `RunFailureSensorContext`? I would have never gone that far searching for it.

Few days before, Daniel mentioned about the environment variable `DAGSTER_RUN_JOB_NAME` which was a blessing as it is saving us heaps of time when running the jobs as we load only the job that is running. How can I see list of environment variables that Dagster sets?

to be honest, I just went into the codebase and started clicking around haha: <https://sourcegraph.com/github.com/dagster-io/dagster/-/blob/python_modules/dagster/dagster/_core/definitions/run_status_sensor_definition.py?L250:7-250:30|https://sourcegraph.com/github.com/dagster-io/dagster/-/blob/python_modules/dagster/[…]ore/definitions/run_status_sensor_definition.py?L250:7-250:30>

I believe the DAGSTER_RUN_JOB_NAME is a run-launcher specific thing (where it's not set for all run launchers)

the most reliable thing would probably just be an `env | grep DAGSTER` sort of thing in your prod environment

Hey <@U01J51Y6B9D>, a question regarding the use of variable `DAGSTER_RUN_JOB_NAME`. We have multiple code locations in our instance. When a run is being instantiated, will dagster load all the code definitions in all the code locations or only the specific code location?

Earlier, we had one code location with all the jobs in it and use of this variable helped us a lot to save up the process at the time of runs but now that we have split out the code locations, I'm wondering if we still need to use it.

Hi! Assuming each of the code locations lives in a different file, then only the specified code location will be loaded in the runtime process