Hi everyone, I am wondering about project structur...
# flyte-support
p
Hi everyone, I am wondering about project structure when I am working with Flyte. Is it necessary that all the @task and @workflow decorators have to be in a single file (or multiple files at same level) in the parent directory? I am figuring out a way where I can segregate the functionalities and reuse them better. Now I have a single long file with all of them mashed together, and some function calls separated which don't need @task annotation
h
@polite-fish-93728, tasks, workflows, and other Flyte entities do not have to be in a single file. Keep in mind that
pyflyte run
has this assumption (i.e. it was made for quick experimentation), but there are other ways of registering Flyte entities (e.g.
pyflyte register
, etc).
p
ah okay, I guess we stuck to pyflyte run, thanks for the info! Let me explore
register
functionality
👍 1