@ancient-wolf-19325 If I want to re-use a task or a workflow in my own workflow, one way of doing it is to use

@reference_task

or

@reference_launch_plan

decorators. Is there an alternative?

Yes, an alternative to using

@reference_task

or

@reference_launch_plan

is to directly import and use the task or workflow in your own workflow. This can be done by importing the task or workflow from another module and using it as a dependency in your workflow. For example, you can import a task from another workflow and use it directly:

from flytekit import task, workflow

# Import the task from another module
from another_module import task_1

@task
def task_2(i: int) -> float:
    return float(i) * 2.0

@workflow
def my_workflow(i: int) -> float:
    result = task_1(i=i)
    return task_2(i=result)

This approach allows you to reuse tasks and workflows without needing to use reference decorators. Would you like more details on this approach? Sources: - Flyte Discussion on Task Reuse - Flyte Discussion on Reference Tasks 👍 1 button 👎 0 button 💡 Hint: Mention @ancient-wolf-19325 in the thread for followups.

@ancient-wolf-19325 I think you missed the approach which relies on

FlyteRemote

https://docs.flyte.org/en/latest/api/flytekit/design/control_plane.html#design-control-plane

You are correct. Another approach to reusing tasks or workflows is to use the

FlyteRemote

class to fetch and execute remote tasks or workflows. This method allows you to interact with Flyte entities that are registered on a Flyte backend. Here's an example of how to use

FlyteRemote

to fetch and execute a remote workflow:

from flytekit.remote import FlyteRemote
from flytekit.configuration import Config

# Initialize FlyteRemote with the appropriate configuration
remote = FlyteRemote(
    config=Config.for_endpoint(endpoint="flyte.example.net"),
    default_project="flytesnacks",
    default_domain="development",
)

# Fetch the remote workflow
flyte_workflow = remote.fetch_workflow(name="my_workflow", version="v1")

# Execute the remote workflow
execution = remote.execute(
    flyte_workflow, inputs={"input_param": 1}, wait=True
)

# Access the outputs of the execution
print(execution.outputs)

This approach allows you to dynamically fetch and execute workflows or tasks that are registered on a Flyte backend, providing flexibility in managing and reusing Flyte entities. Would you like more details on this approach? Sources: - Flyte Control Plane Design - Flyte Remote API 👍 0 button 👎 0 button 💡 Hint: Mention @runllm in the thread for followups.