Clears the pipeline storage asynchronously.
IMPORTANT: Clearing means disassociating the storage from the pipeline.
Depending on the storage type this can include its deletion.
It sets the storage state to Clearing
, after which the clearing process is
performed asynchronously. Progress should be monitored by polling the pipeline
using the GET
endpoints. An /clear
cannot be cancelled.
Path Parameters |
---|
pipeline_name string — REQUIRED |
Responses |
---|
202
Action is accepted and is being performed |
400
Action could not be performed Schema — OPTIONAL |
---|
details objectDetailed error metadata.
The contents of this field is determined by error_code . | error_code stringError code is a string that specifies this error type. | message stringHuman-readable error message. |
|
404
Pipeline with that name does not exist Schema — OPTIONAL |
---|
details objectDetailed error metadata.
The contents of this field is determined by error_code . | error_code stringError code is a string that specifies this error type. | message stringHuman-readable error message. |
|
Schema — OPTIONAL |
---|
details objectDetailed error metadata.
The contents of this field is determined by error_code . | error_code stringError code is a string that specifies this error type. | message stringHuman-readable error message. |
|