flytekit.LaunchPlan

class flytekit.LaunchPlan(name: str, workflow: flytekit.core.workflow.WorkflowBase, parameters: flytekit.models.interface.ParameterMap, fixed_inputs: flytekit.models.literals.LiteralMap, schedule: Optional[flytekit.models.schedule.Schedule] = None, notifications: Optional[List[flytekit.models.common.Notification]] = None, labels: Optional[flytekit.models.common.Labels] = None, annotations: Optional[flytekit.models.common.Annotations] = None, raw_output_data_config: Optional[flytekit.models.common.RawOutputDataConfig] = None, auth_role: Optional[flytekit.models.common.AuthRole] = None)[source]
__init__(name: str, workflow: flytekit.core.workflow.WorkflowBase, parameters: flytekit.models.interface.ParameterMap, fixed_inputs: flytekit.models.literals.LiteralMap, schedule: Optional[flytekit.models.schedule.Schedule] = None, notifications: Optional[List[flytekit.models.common.Notification]] = None, labels: Optional[flytekit.models.common.Labels] = None, annotations: Optional[flytekit.models.common.Annotations] = None, raw_output_data_config: Optional[flytekit.models.common.RawOutputDataConfig] = None, auth_role: Optional[flytekit.models.common.AuthRole] = None)[source]

Initialize self. See help(type(self)) for accurate signature.

Methods

__init__(name, workflow, parameters, …[, …])

Initialize self.

create(name, workflow[, default_inputs, …])

get_default_launch_plan(ctx, workflow)

Users should probably call the get_or_create function defined below instead.

get_or_create(workflow[, name, …])

This function offers a friendlier interface for creating launch plans.

Attributes

CACHE

annotations

fixed_inputs

labels

name

notifications

parameters

python_interface

raw_output_data_config

saved_inputs

schedule

workflow