-
Notifications
You must be signed in to change notification settings - Fork 6
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.
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
Support embedded step definition in CWL #56
Comments
This is a bit tricky because in our situation, we usually want each step to refer to an existing/deployed process in the EMS's catalogue. |
This kind of use case must be described in #61 |
More details about expected behaviour defined in Best Practices: https://docs.ogc.org/bp/20-089r1.html#toc28 Allow definition of a See also: https://www.commonwl.org/v1.2/CommandLineTool.html#Packed_documents |
|
It is not currently possible to embed steps in a CWL workflow definition in weaver.
According to the CWL spec, it is possible to have step definitions in the workflow itself.
The text was updated successfully, but these errors were encountered: