Dayten Sheffar
05/02/2023, 7:57 PMroot/
__init__.py
dagster_modules/
__init__.py
module_1/
__init__.py
ops/ assets/ etc...
module_2/
__init__.py
ops/ assets/ etc...
workspace.yaml
shared_stuff_module/
__init__.py
some_constants.py
some_helper_functions.py
other_stuff_like_dbt_project/
...
where workspace.yaml
is (among tons of other efforts):
load_from:
- python_package:
package_name: module_1
- python_package:
package_name: module_2
- python_package:
package_name: shared_stuff_module
and the modules show up in UI but with error loading saying module cannot be found
If I leave out the 2nd and 3rd entries under load_from
, then module_1
loads, but it can’t find relative imports from shared_stuff_module
.
Any help appreciatedDayten Sheffar
05/02/2023, 7:59 PMDayten Sheffar
05/02/2023, 8:00 PMshared_stuff_module
(i.e., helpers/
) doesnt really need to be under load_from
I guess since there are no dagster assets, ops, etc… in there, but I can’t resolve the relative imports in say module_1Dayten Sheffar
05/02/2023, 8:03 PMDayten Sheffar
05/02/2023, 8:04 PMDayten Sheffar
05/02/2023, 8:42 PMmy_ml_pipeline
and my_data_pipeline
were further nested in a folder called dagster_modules
, can you leave workspace.yaml
in the root and just change the contents of workspace.yaml
to be like, python_module:
<http://dagster_modules.my|dagster_modules.my>_ml_pipeline
?Dayten Sheffar
05/02/2023, 8:43 PMhelpers
folder that contains no dagster assets etc.Odette Harary
05/02/2023, 8:55 PM