---
layout: default
navsection: api
navmenu: API Methods
title: "pipeline_templates"
...
{% comment %}
Copyright (C) The Arvados Authors. All rights reserved.
SPDX-License-Identifier: CC-BY-SA-3.0
{% endcomment %}
p=. *Legacy. This endpoint is read-only and disabled by default in new installations.*
API endpoint base: @https://{{ site.arvados_api_host }}/arvados/v1/pipeline_templates@
Object type: @p5p6p@
Example UUID: @zzzzz-p5p6p-0123456789abcde@
h2. Resource
Deprecated. A pipeline template is a collection of jobs that can be instantiated as a pipeline_instance.
Each PipelineTemplate has, in addition to the "Common resource fields":{{site.baseurl}}/api/resources.html:
table(table table-bordered table-condensed).
|_. Attribute|_. Type|_. Description|_. Example|
|name|string|||
|components|hash|||
The pipeline template consists of "name" and "components".
table(table table-bordered table-condensed).
|_. Attribute |_. Type |_. Accepted values |_. Required|_. Description|
|name |string |any |yes |The human-readable name of the pipeline template.|
|components |object |JSON object containing job submission objects|yes |The component jobs that make up the pipeline, with the component name as the key. |
h3. Components
The components field of the pipeline template is a JSON object which describes the individual steps that make up the pipeline. Each component is an Arvados job submission. "Parameters for job submissions are described on the job method page.":{{site.baseurl}}/api/methods/jobs.html#create In addition, a component can have the following parameters:
table(table table-bordered table-condensed).
|_. Attribute |_. Type |_. Accepted values |_. Required|_. Description|
|output_name |string or boolean|string or false |no |If a string is provided, use this name for the output collection of this component. If the value is false, do not create a permanent output collection (an temporary intermediate collection will still be created). If not provided, a default name will be assigned to the output.|
h3. Script parameters
When used in a pipeline, each parameter in the 'script_parameters' attribute of a component job can specify that the input parameter must be supplied by the user, or the input parameter should be linked to the output of another component. To do this, the value of the parameter should be JSON object containing one of the following attributes:
table(table table-bordered table-condensed).
|_. Attribute |_. Type |_. Accepted values |_. Description|
|default |any |any |The default value for this parameter.|
|required |boolean |true or false |Specifies whether the parameter is required to have a value or not.|
|dataclass |string |One of 'Collection', 'File' [1], 'number', or 'text' |Data type of this parameter.|
|search_for |string |any string |Substring to use as a default search string when choosing inputs.|
|output_of |string |the name of another component in the pipeline |Specifies that the value of this parameter should be set to the 'output' attribute of the job that corresponds to the specified component.|
|title |string |any string |User friendly title to display when choosing parameter values|
|description |string |any string |Extended text description for describing expected/valid values for the script parameter|
|link_name |string |any string |User friendly name to display for the parameter value instead of the actual parameter value|
The 'output_of' parameter is especially important, as this is how components are actually linked together to form a pipeline. Component jobs that depend on the output of other components do not run until the parent job completes and has produced output. If the parent job fails, the entire pipeline fails.
fn1. The 'File' type refers to a specific file within a Keep collection in the form 'collection_hash/filename', for example '887cd41e9c613463eab2f0d885c6dd96+83/bob.txt'.
The 'search_for' parameter is meaningful only when input dataclass of type Collection or File is used. If a value is provided, this will be preloaded into the input data chooser dialog in Workbench. For example, if your input dataclass is a File and you are interested in a certain filename extention, you can preconfigure it in this attribute.
h3. Examples
This is a pipeline named "Filter MD5 hash values" with two components, "do_hash" and "filter". The "input" script parameter of the "do_hash" component is required to be filled in by the user, and the expected data type is "Collection". This also specifies that the "input" script parameter of the "filter" component is the output of "do_hash", so "filter" will not run until "do_hash" completes successfully. When the pipeline runs, past jobs that meet the criteria described above may be substituted for either or both components to avoid redundant computation.
{
"name": "Filter MD5 hash values",
"components": {
"do_hash": {
"script": "hash.py",
"repository": "you/you",
"script_version": "master",
"script_parameters": {
"input": {
"required": true,
"dataclass": "Collection",
"search_for": ".fastq.gz",
"title":"Please select a fastq file"
}
},
},
"filter": {
"script": "0-filter.py",
"repository": "you/you",
"script_version": "master",
"script_parameters": {
"input": {
"output_of": "do_hash"
}
},
}
}
}
This pipeline consists of three components. The components "thing1" and "thing2" both depend on "cat_in_the_hat". Once the "cat_in_the_hat" job is complete, both "thing1" and "thing2" can run in parallel, because they do not depend on each other.
{
"name": "Wreck the house",
"components": {
"cat_in_the_hat": {
"script": "cat.py",
"repository": "you/you",
"script_version": "master",
"script_parameters": { }
},
"thing1": {
"script": "thing1.py",
"repository": "you/you",
"script_version": "master",
"script_parameters": {
"input": {
"output_of": "cat_in_the_hat"
}
},
},
"thing2": {
"script": "thing2.py",
"repository": "you/you",
"script_version": "master",
"script_parameters": {
"input": {
"output_of": "cat_in_the_hat"
}
},
},
}
}
This pipeline consists of three components. The component "cleanup" depends on "thing1" and "thing2". Both "thing1" and "thing2" are started immediately and can run in parallel, because they do not depend on each other, but "cleanup" cannot begin until both "thing1" and "thing2" have completed.
{
"name": "Clean the house",
"components": {
"thing1": {
"script": "thing1.py",
"repository": "you/you",
"script_version": "master",
"script_parameters": { }
},
"thing2": {
"script": "thing2.py",
"repository": "you/you",
"script_version": "master",
"script_parameters": { }
},
"cleanup": {
"script": "cleanup.py",
"repository": "you/you",
"script_version": "master",
"script_parameters": {
"mess1": {
"output_of": "thing1"
},
"mess2": {
"output_of": "thing2"
}
}
}
}
}
h2. Methods
See "Common resource methods":{{site.baseurl}}/api/methods.html for more information about @create@, @delete@, @get@, @list@, and @update@.
Required arguments are displayed in %{background:#ccffcc}green%.
h3. create
Create a new PipelineTemplate.
Arguments:
table(table table-bordered table-condensed).
|_. Argument |_. Type |_. Description |_. Location |_. Example |
|pipeline_template|object||query||
h3. delete
Delete an existing PipelineTemplate.
Arguments:
table(table table-bordered table-condensed).
|_. Argument |_. Type |_. Description |_. Location |_. Example |
{background:#ccffcc}.|uuid|string|The UUID of the PipelineTemplate in question.|path||
h3. get
Gets a PipelineTemplate's metadata by UUID.
Arguments:
table(table table-bordered table-condensed).
|_. Argument |_. Type |_. Description |_. Location |_. Example |
{background:#ccffcc}.|uuid|string|The UUID of the PipelineTemplate in question.|path||
h3. list
List pipeline_templates.
See "common resource list method.":{{site.baseurl}}/api/methods.html#index
h3. update
Update attributes of an existing PipelineTemplate.
Arguments:
table(table table-bordered table-condensed).
|_. Argument |_. Type |_. Description |_. Location |_. Example |
{background:#ccffcc}.|uuid|string|The UUID of the PipelineTemplate in question.|path||
|pipeline_template|object||query||