Hello everyone, I have customized my `dagster.yaml...
# ask-community
r
Hello everyone, I have customized my
dagster.yaml
and
workspace.yaml
to run Dagster over ECS (which is working fine so far), but I need another version of them to run Dagster locally (for development and testing purpose). How would you suggest I should do? Should I have two different versions of those files? One for ECS and one for local Dagster? Is there a way to tweak the files so that they are interpreted differently between environments?
d
Hi Romain - a separate set of files probably makes sense here as I imagine the contents are fairly different
👍 1
r
Hello @daniel here is the solution we have found : we have three files, 1
dagster.yaml
, 1
dagster-ecs.yaml
and 1
dagster-local.yaml
. The idea here is that we use very different RunLauncher or LogStorage instances between environnements, something that cannot be mapped onto env variables (afaik). When working in a local environment, we copy the content of
dagster-local.yaml
into
dagster.yaml
and
dagster-ecs.yaml
when pushing the code to ECS. It works fine, but I think being able to explicitely select the instance file at deployment time (like
dagit -w workspace.yml -i custom-dagster.yaml
) would be a nice addition. What do you think?