Hi Flyte community, The ExecutionCreateRequest pr...
# ask-the-community
j
Hi Flyte community, The ExecutionCreateRequest proto does not contain a field to pass the workflow id that we want to create an execution for. It only has a field for an ExecutionSpec that accepts a launch plan id. Does this mean that we need to create a launch plan for each workflow to use the Flyte Admin ExecutionCreate API operation? https://github.com/flyteorg/flytekit-java/blob/be2f4f664765c26b0b0eff94c81a2b9af32[…]e/flyteidl-protos/src/main/proto/flyteidl/admin/execution.proto
Copy code
message ExecutionCreateRequest {
    // Name of the project the execution belongs to.
    // +required
    string project = 1;

    // Name of the domain the execution belongs to.
    // A domain can be considered as a subset within a specific project.
    // +required
    string domain = 2;

    // User provided value for the resource.
    // If none is provided the system will generate a unique string.
    // +optional
    string name = 3;

    // Additional fields necessary to launch the execution.
    // +optional
    ExecutionSpec spec = 4;

    // The inputs required to start the execution. All required inputs must be
    // included in this map. If not required and not provided, defaults apply.
    // +optional
    core.LiteralMap inputs = 5;
}
k
yes, each workflow must have a launch plan
k
by default a default launch should be created with the same name
148 Views