Abort building block run
POST/api/meshobjects/meshbuildingblockruns/:uuid/abort
Aborts a meshBuildingBlockRun with behavior APPLY that has not finished. Dry runs and destroy runs cannot be
aborted. A run that waits, for example for approval, ends at once. A synchronous run in progress ends when its
runner stops it. An asynchronous run ends at once in meshStack, but its external pipeline may go on, so an aborted
run does not prove that the infrastructure changes stopped. Read the meshBuildingBlock to see the result, because
this API version shows an aborted run as FAILED. A run that cannot be aborted answers with 409.
Admins and the workspace that owns the building block definition may abort any run, and only they may reject a run that waits for approval. The workspace or project of the building block may abort other runs while the definition has run transparency on. A CLI login needs write or full access.
Request
Responses
- 202
- 400
- 401
- 403
- 404
- 406
- 409
Abort accepted
The request is invalid. The message names the invalid part.
The request has no valid authentication.
The authenticated user or API key lacks the permission for this request.
The resource does not exist, or you may not see it.
The Accept header names no media type of this operation, or a version that is no longer supported.
The request conflicts with the current state, for example with an existing object of the same name. The message names the conflict.