https://flyte.org
Join Slack
Hi team, can we use imperative workflow as a subworkflow? [confirm it is working] However, when I ad...
# flyte-support
b
Hi team, can we use imperative workflow as a subworkflow? [confirm it is working] However, when I add an imperative workflow inside a helper function, I received the following error:
Copy code
File ".../site-packages/flytekit/core/workflow.py", line 545, in 
add_entity
raise Exception("Can't already be compiling")
Exception: Can't already be compiling
Sample code:
Copy code
@task
def upload_sources() -> FlyteDirectory:
    ...

def helper_func(
    params: str,
    name: str
) -> Workflow:
    test_workflow = Workflow(name=name)
    test_workflow.add_workflow_input("params", str)
    uploaded_sources_node = test_workflow.add_entity(upload_sources)
    ...

    return test_workflow(
        params=params
    )
We want to customize the workflow name for users using imperative workflow. If this doesn't work, do we have any other workaround? cc: @glamorous-carpet-83516
t
name is just an attribute.
should be pretty easy to override after the fact.
but when you do test_workflow(…) you’re invoking the workflow. is that what you want to do?
b
Can we override a normal workflow’s name?
Yeah we want to return the workflow and have the users to call this helper function to customize the workflow’s name
Imperative workflow seems to be customizable
But the serialization will fail at uploaded_sources_node = test_workflow.add_entity(upload_sources)
Found the 
with_overrides(name="...")
approach
t
oh sorry, hopped off.
yes that is one yes.
8 Views
Open in Slack
PreviousNext
Powered by

Flyte

Flyte enables production-grade orchestration for machine learning workflows and data processing created to accelerate local workflows to production.

Powered by