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

dagster

When dagster runs on ECS, does it get the container definitions from `dagsterdaemon` or from `workflows_user_code`?

I see that there is a variable that is being inherited from dagsterdaemon :thinking_face: (or at least it looks like it)

It infers some of its container definitions from wherever the run is being launched - typically that’s dagster daemon (like if it’s a schedule or sensor) or sometimes dagit (like if you’re launching from the UI).

Is there an easy way to configure environment variables? :thinking_face:

I mean - for the new ecs task that spins up, not for the dagsterdaemon task itself. I would love to override a variable that is sent to datadog to be able to distinguish logs from the dagsterdaemon task from the one that is, in fact, running the code.

Yup - added recently actually:

<https://github.com/dagster-io/dagster/blob/master/CHANGES.md#new-1>

You can either add it to all runs by configuring it where you configure your user code launcher in your dagster.yaml

Or you can add it to runs for a certain user code server via: <https://docs.dagster.io/_apidocs/cli#cmdoption-dagster-api-grpc-container-context>

Here’s the actual change - there are some examples in the tests although we could admittedly do a better job of documenting this in our docs.

<@U018K0G2Y85> docs “Add docs examples for configuring ECS env vars”

Created issue at: <https://github.com/dagster-io/dagster/issues/8675>