A workflow consists of a tree of
Job is an independent, named unit that can contain an array of
steps and/or a set of sub-
Job runs asynchronously, and therefore
Jobs may run in any order. Although all the sub-jobs are guaranteed to be executed after the parent job completes. Outputs of the parent jobs can be referenced as the input of any of its sub-jobs.
run will run all jobs in a workflow.
Job index can be provided to
run to execute a specific job.
Step is a wrapper invocation. An array of
Steps runs synchronously--i.e. in the order defined in the workflow.
The result of a
Step can be passed as an input argument to a
Step that is its child in the tree hierarchy.
Users can configure the Polywrap client used to execute a workflow.
This is done by providing the Polywrap CLI's
run command with the path to a custom
It must implement and export a function named
getClientConfig function accepts the default
ClientConfig as an argument and returns the custom Polywrap
It must be implemented with the following signature:
The output of a workflow can be written as a file in the JSON or YAML format with the
output-file option of the Polywrap CLI's
Workflow output is printed to the console by default.
Console output can be suppressed with the
quiet option of the Polywrap CLI's