flytekit.remote.entities.FlyteLaunchPlan¶
- class flytekit.remote.entities.FlyteLaunchPlan(id, *args, **kwargs)[source]¶
A class encapsulating a remote Flyte launch plan.
Methods
- compile(ctx, *args, **kwargs)[source]¶
- Parameters:
ctx (FlyteContext)
- construct_node_metadata()¶
Used when constructing the node that encapsulates this task as part of a broader workflow definition.
- Return type:
NodeMetadata
- classmethod from_flyte_idl(pb2)¶
- Parameters:
pb2 (flyteidl.admin.launch_plan_pb2.LaunchPlanSpec)
- Return type:
LaunchPlanSpec
- local_execute(ctx, **kwargs)¶
- Parameters:
ctx (FlyteContext)
- Return type:
- classmethod promote_from_model(id, model)[source]¶
- Parameters:
id (Identifier)
model (LaunchPlanSpec)
- Return type:
- short_string()¶
- Return type:
Text
- to_flyte_idl()¶
- Return type:
flyteidl.admin.launch_plan_pb2.LaunchPlanSpec
- verbose_string()¶
- Return type:
Text
Attributes
- annotations
The annotations to execute the workflow with :rtype: flytekit.models.common.Annotations
- auth_role
The authorization method with which to execute the workflow. :rtype: flytekit.models.common.AuthRole
- default_inputs
Input values to be passed for the execution :rtype: flytekit.models.interface.ParameterMap
- entity_metadata
LaunchPlanMetadata
- Type:
rtype
- entity_type_text
- fixed_inputs
Fixed, non-overridable inputs for the Launch Plan :rtype: flytekit.models.literals.LiteralMap
- flyte_workflow
- id
- interface
The interface is not technically part of the admin.LaunchPlanSpec in the IDL, however the workflow ID is, and from the workflow ID, fetch will fill in the interface. This is nice because then you can __call__ the= object and get a node.
- is_empty
- is_scheduled
- labels
The labels to execute the workflow with :rtype: flytekit.models.common.Labels
- max_parallelism
- name
- overwrite_cache
- python_interface
- raw_output_data_config
Where to store offloaded data like Blobs and Schemas :rtype: flytekit.models.common.RawOutputDataConfig
- resource_type
- security_context
- workflow_id