I am currently testing

EcsRunLauncher

on an existing dagster deployment that is on ECS but was using

DefaultRunLauncher

. I am able to successfully launch jobs that have code loaded from

python_file

in the

workspace.yaml

config, however when I try to launch jobs that are loaded from

python_package

I get the following error:

Encountered ImportError: `No module named 'data-dagster-workspaces.workspaces'` while importing module data-dagster-workspaces.workspaces.rad_data.repositories. Local modules were resolved using the working directory `/opt/dagster/dagster_home`. If another working directory should be used, please explicitly specify the appropriate path using the `-d` or `--working-directory` for CLI based targets or the `working_directory` configuration option for workspace targets.

I do not have this issue when using

DefaultRunLauncher

. Is there a way to configure the ecs launcher task to recognize the working directory or packages without having to change the import statements in the existing code?

cc @jordan @Joe

https://docs.dagster.io/concepts/repositories-workspaces/workspaces#workspaces You should be able to override the working directory in you workspace.yaml

Christian, have you been able to resolve your issue/answer your questions?

Yes this answered my question and solved the particular issue that prompted it. Thanks for the support here!