Spinnaker Create Pipeline from Command Line: Difference between revisions
Jump to navigation
Jump to search
Line 9: | Line 9: | ||
{ | { | ||
"schema": "v2", | "schema": "v2", | ||
"application": " | "application": "aiml-automation-test", | ||
"name": "color-pipeline", | "name": "color-pipeline", | ||
"keepWaitingPipelines": false, | "keepWaitingPipelines": false, | ||
Line 26: | Line 26: | ||
{ | { | ||
"refId": "1", | "refId": "1", | ||
"name": " | "name": "Do you like the color ${execution.trigger.parameters['color']}?", | ||
"type": "manualJudgment", | "type": "manualJudgment", | ||
"instructions": "Do you like the ${execution.trigger.parameters['color']} color?", | "instructions": "Do you like the ${execution.trigger.parameters['color']} color?", |
Revision as of 03:46, 31 May 2023
Internal
Overview
A pipeline, including its parameters, can be fully declared in a JSON file and then instantiated via CLI.
The JSON representation is similar to:
{
"schema": "v2",
"application": "aiml-automation-test",
"name": "color-pipeline",
"keepWaitingPipelines": false,
"limitConcurrent": true,
"parameterConfig": [
{
"name": "color",
"default": "blue",
"label": "The Color",
"description": "The color to be presented to the user",
"pinned": true,
"required": true
}
],
"stages": [
{
"refId": "1",
"name": "Do you like the color ${execution.trigger.parameters['color']}?",
"type": "manualJudgment",
"instructions": "Do you like the ${execution.trigger.parameters['color']} color?",
"judgmentInputs": [
{
"value": "Yes"
},
{
"value": "No"
}
],
"failPipeline": true
}
]
}
Once saved in some-file.json
, the pipeline can be created with:
spin pipeline save --file ./some-file.json