Christian Lam05/26/2022, 11:07 PM
on an existing dagster deployment that is on ECS but was using
. I am able to successfully launch jobs that have code loaded from
config, however when I try to launch jobs that are loaded from
I get the following error:
I do not have this issue when using
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.
. 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?
sean05/27/2022, 12:37 PM
jordan05/27/2022, 1:09 PM
sean05/31/2022, 1:27 PM
Christian Lam05/31/2022, 9:16 PM