Based on the step order provided, the job will be added to that step. When a pipeline runs, it will run all steps in their provided order. So in this example jobs 87f... and 3a7... will run in parallel before job 337...
The response to this request will show the updated pipeline, allowing you to verify that it looks as expected.
As stated in the API doc, you will need to list every value in the request. Otherwise the value will be defaulted and likely lost.
Running a Pipeline
curl --location -g --request POST '{{impulse-protocol}}://{{impulse-domain}}:{{impulse-port}}/private/pipeliner/pipelines/{{pipelineID}}/start'
The response will include the id of the pipeline transaction . This can be used to track the status of the transaction.
Tracking Pipeline Transaction Status
curl --location -g --request GET '{{impulse-protocol}}://{{impulse-domain}}:{{impulse-port}}/private/pipeliner/pipelines/{{pipelineID}}/transactions/9bfe48f8-bf1f-11ec-bccf-0242ac150009'
Canceling a Pipeline Transaction
curl --request POST '{{impulse-protocol}}://{{impulse-domain}}:{{impulse-port}}/private/pipeliner/pipelines/{{pipelineID}}/transactions/{{pipelineTransactionID}}/cancel'
This will cancel all sync transactions related to this pipeline transaction stopping the processes from continuing further.
To create a pipeline, you will want multiple jobs created. After you have created 2+ jobs you can get started with creating a pipeline. You can use the to do this.
The best way to create a pipeline is to do it in iterations. Start by creating an empty pipeline using the .
Using all three of these values you can add a job to the pipeline by using the . This example adds three jobs to the pipeline. Two at step 0 and one at step 1.
The to add a job to a pipeline step can be used to remove a job from a pipeline step. The payload is the same for both the DELETE and POST requests.
To update the pipeline with a new name or add multiple jobs/steps in a single request you can use the .
Once the object has be edited you can send it as a payload to the same endpoint in a .
Like a job pipelines can be run. This is done by using the pipeliner's . This request will start a pipeline transaction which is combination of standard syncTransactions .
To track the status of the pipeline transaction, you can use the .
The response will show the list of sync transaction started by the pipeline. You can then view the status of each . The response will also show if the pipeline transaction is active and the last step that was completed by the pipeline.
Similar to a sync transaction you can also cancel a pipeline transaction. You can use the .
