hi flyte team, I noticed that when flyte is running serialization of a python file. It will look at the all the files's imports transitively and register all the flyte entities.. I wonder if there is a way to avoid such behavior and change it to: only register task entities from other files and subworkflows. Basically if a workflow is not used in the workflow of the current file. It will be ignored. Is there any drawbacks with such approach? The current behavior causes unexpected registration of unrelated worfflows for us. cc: @future-monitor-58430 @rapid-wall-26163

i can’t think of a drawback off the top of my head, except maybe how this setting would be exposed to the user in a way that’s not confusing. would want to run this by eduardo or thomas as well

I am planning on adding an additional workflow field in serialization settings https://github.com/flyteorg/flytekit/blob/master/flytekit/configuration/__init__.py#L816 not sure if this is a good practice or not. Just a general question, does

pyflyte run wf

try to register everything as well? or it only register the entities related to workflow

wf

? From code reading, I think it should register everything here

what about

@dynamic

?