witty-wall-39635
03/14/2023, 12:42 AMpyflyte register
was failing because a module's path was not included in syspath. To workaround this failure and allow the registration command to complete, I added the path to PYTHONPATH
. However, when I try to run the workflow that's successfully registered, pyflyte-execute
fails in the pod that Flyte launches because that same module whose path I had included in PYTHONPATH
was not packaged into the tar file that contains the workflow logic. Does pyflyte register
support a workaround that allows me to pass in specific module paths that aren't included in the default registration logic (and package those module paths)? I would prefer not to change my project layout if possible.
Project layout:
root
|__ module_with_workflow_and_tasks
|__ build
|__ generated
|__source
|__..
|__ _module_not_loaded_
Update: I've temporarily worked around the issue by adding init.py to every subdirectory (build, generated, source) and adding the path to module_not_loaded as an additional argument to pyflyte register