Skip to content

Conversation

fg91
Copy link
Member

@fg91 fg91 commented Mar 8, 2025

We provide an example how to chain tasks and sub workflows with the >> operator. I was recently asked by a user whether this works for launchplans as well as we don't provide an example for this case.
As this does in fact work, I'm adding an example in this PR.

@fg91 fg91 requested review from neverett and ppiegaze as code owners March 8, 2025 10:46
@fg91 fg91 self-assigned this Mar 8, 2025
@fg91 fg91 added the documentation Improvements or additions to documentation label Mar 8, 2025
thomasjpfan
thomasjpfan previously approved these changes Mar 13, 2025
Copy link
Contributor

@thomasjpfan thomasjpfan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@thomasjpfan
Copy link
Contributor

Syncing with master so you get #1784 should fix the CI.

@fg91 fg91 force-pushed the fg91/doc/chain-launchplans branch from 9d7019a to 07a4543 Compare March 20, 2025 21:23
Signed-off-by: Fabio Grätz <[email protected]>
@fg91 fg91 enabled auto-merge (squash) March 20, 2025 22:13
@fg91 fg91 requested a review from thomasjpfan March 20, 2025 22:14
@fg91
Copy link
Member Author

fg91 commented Mar 20, 2025

We'll also need to update this:

https://github.com/flyteorg/flyte/blob/eeac1014362204aba86985253964595990465f12/docs/user_guide/advanced_composition/chaining_flyte_entities.md?plain=1#L32

So the changes appear in the docs.

flyteorg/flyte#6317 Already done but I'll need to adapt the commit sha after merging this pr @thomasjpfan

@fg91 fg91 merged commit ab2e8e8 into master Mar 24, 2025
62 checks passed
@fg91 fg91 deleted the fg91/doc/chain-launchplans branch March 24, 2025 17:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Improvements or additions to documentation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants