Bryan Weber
02/15/2023, 8:31 PMpyflyte package
+ flytectl register
flow to push the tasks to my flyte cluster. The tasks run fine, and the image does not need to include the actual task code.
Now for reusability, I’d like to break my task package into several modules and define a workflow in a different module, thus I need to import the tasks in the workflow module. Is there a way to make this work with the protobuf registration? I’m getting errors that the task module could not be found, which makes sense since the image doesn’t contain that code. It’d be nice not to have to rebuild my docker image every time a workflow/task changes, since most of the “business logic” code (upon which the tasks depend) is fairly stable and doesn’t require updates in the image too oftenKevin Su
02/15/2023, 9:04 PMBryan Weber
02/15/2023, 9:05 PMpyflyte package
+ flytectl register
for production: https://docs.flyte.org/projects/cookbook/en/latest/getting_started/package_register.html#productionizing-your-workflows which is why I was trying to go that routeKevin Su
02/15/2023, 9:09 PMBryan Weber
02/15/2023, 9:10 PMKevin Su
02/15/2023, 9:11 PM