Skip to content

Doc: Explain how to chain launch plans #6317

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
fg91 merged 2 commits into from
Mar 24, 2025
Merged

Doc: Explain how to chain launch plans #6317

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
722e4c4
Doc: Explain how to chain launch plans
Mar 8, 2025
f651142
Update commit hash
Mar 24, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
24 changes: 20 additions & 4 deletions docs/user_guide/advanced_composition/chaining_flyte_entities.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7,7 +7,7 @@
```

Flytekit offers a mechanism for chaining Flyte entities using the `>>` operator.
This is particularly valuable when chaining tasks and subworkflows without the need for data flow between the entities.
This is particularly valuable when chaining tasks, subworkflows, and launch plans without the need for data flow between the entities.

```{note}
To clone and run the example code on this page, see the [Flytesnacks repo][flytesnacks].
Expand All @@ -32,22 +32,38 @@ Just like tasks, you can chain {ref}`subworkflows <subworkflow>`.
:lines: 34-49
```

## Launch plans

Like subworkflows, you can chain {ref}`launch plans <Launch plans>`.


```{literalinclude} /examples/advanced_composition/advanced_composition/chain_entities.py
:caption: advanced_composition/chain_entities.py
:lines: 55-60
```

To run the provided workflows on the Flyte cluster, use the following commands:

```
pyflyte run --remote \
https://raw.githubusercontent.com/flyteorg/flytesnacks/69dbe4840031a85d79d9ded25f80397c6834752d/examples/advanced_composition/advanced_composition/chain_entities.py \
https://raw.githubusercontent.com/flyteorg/flytesnacks/ab2e8e84362c5b06d2eea0d1d6e29ea7fe460608/examples/advanced_composition/advanced_composition/chain_entities.py \
chain_tasks_wf
```

```
pyflyte run --remote \
https://raw.githubusercontent.com/flyteorg/flytesnacks/69dbe4840031a85d79d9ded25f80397c6834752d/examples/advanced_composition/advanced_composition/chain_entities.py \
https://raw.githubusercontent.com/flyteorg/flytesnacks/ab2e8e84362c5b06d2eea0d1d6e29ea7fe460608/examples/advanced_composition/advanced_composition/chain_entities.py \
chain_workflows_wf
```

```
pyflyte run --remote \
https://raw.githubusercontent.com/flyteorg/flytesnacks/ab2e8e84362c5b06d2eea0d1d6e29ea7fe460608/examples/advanced_composition/advanced_composition/chain_entities.py \
chain_launchplans_wf
```

:::{note}
Chaining tasks and subworkflows is not supported in local environments.
Chaining tasks, subworkflows, and launch plans is not supported in local environments.
Follow the progress of this issue [here](https://github.com/flyteorg/flyte/issues/4080).
:::

Expand Down
Loading