Summary
The user is working on a workflow that consists of a generic part and a custom part. They want to implement a parameter in the top-level workflow to decide which workflow runs after the generic part. They have attempted to create a function, do_next_step, to reference and execute the next step based on a string input. They also explored using importlib to dynamically import modules and functions for the next steps, but this requires maintaining separate launch plans for each step. The user is seeking a way to retrieve the latest launch plan at runtime using the Flyte client, but has not found a method to trigger a dynamic workflow from the Flyte API object. They also considered triggering a workflow from within a task, which is less ideal. Lastly, they are contemplating generating the workflow dynamically using an imperative approach and registering it as needed. Overall, the user aims to determine and execute subsequent steps in a workflow based on input arguments.