-
Notifications
You must be signed in to change notification settings - Fork 170
Closed
Description
I tried this:
Description:
In the schema, there is a run.workflow element that defines a sub-workflow.
However, it’s not entirely clear how this definition is supposed to be used.
The workflow definition currently specifies the following properties:
namespacenameversioninput
As I understand it, a sub-workflow should behave similarly to a regular workflow — meaning it should at least contain a do definition or some equivalent execution logic.
It would be helpful to clarify:
- whether a sub-workflow must include its own
dosection, - how it inherits or overrides inputs/outputs,
- and how its execution context is handled relative to the parent workflow.
specification/schema/workflow.yaml
Line 783 in 833d25d
| - title: RunWorkflow |
This happened:
I can define sub-workflow
I expected this:
No response
Is there a workaround?
No response
Anything else?
No response
Area(s)
No response
Community Notes
- Please vote by adding a 👍 reaction to the issue to help us prioritize.
- If you are interested to work on this issue, please leave a comment.name: Bug Report 🐞
Metadata
Metadata
Assignees
Labels
No labels
Type
Projects
Status
Done