Execute a Pipeline with Input Set References
Bad Request
Internal server error
Returns pipeline execution details V2
{- "inputSetReferences": [
- "string"
], - "withMergedPipelineYaml": true,
- "stageIdentifiers": [
- "string"
]
}
{- "status": "SUCCESS",
- "code": "DEFAULT_ERROR_CODE",
- "message": "string",
- "correlationId": "string",
- "errors": [
- {
- "fieldId": "string",
- "error": "string"
}
]
}
Execute a Pipeline with Runtime Input YAML
Enter Runtime Input YAML if the Pipeline contains Runtime Inputs. Please refer to https://ngdocs.harness.io/article/f6yobn7iq0 and https://ngdocs.harness.io/article/1eishcolt3 to see how to generate Runtime Input YAML for a Pipeline.
Bad Request
Internal server error
Returns pipeline execution details
"string"
{- "status": "SUCCESS",
- "code": "DEFAULT_ERROR_CODE",
- "message": "string",
- "correlationId": "string",
- "errors": [
- {
- "fieldId": "string",
- "error": "string"
}
]
}
Executes an Interrupt on a Given Execution
Bad Request
Internal server error
Takes a possible Interrupt value and applies it onto the execution referred by the planExecutionId
curl -i -X PUT \ 'https://app.harness.io/gateway/pipeline/api/pipeline/execute/interrupt/{planExecutionId}?accountIdentifier=string&orgIdentifier=string&projectIdentifier=string&interruptType=ABORTALL' \ -H 'x-api-key: YOUR_API_KEY_HERE'
{- "status": "SUCCESS",
- "code": "DEFAULT_ERROR_CODE",
- "message": "string",
- "correlationId": "string",
- "errors": [
- {
- "fieldId": "string",
- "error": "string"
}
]
}