Doc: Provide example of launchplan chaining#1783
Merged
Conversation
3 tasks
thomasjpfan
previously approved these changes
Mar 13, 2025
Contributor
thomasjpfan
left a comment
There was a problem hiding this comment.
We'll also need to update this:
So the changes appear in the docs.
Contributor
|
Syncing with |
Signed-off-by: Fabio Grätz <fabiogratz@googlemail.com>
9d7019a to
07a4543
Compare
Member
Author
flyteorg/flyte#6317 Already done but I'll need to adapt the commit sha after merging this pr @thomasjpfan |
thomasjpfan
approved these changes
Mar 24, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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.