Execute an approved request
POST/approval/:id/execute
Starts the action behind an approved request (a deployment, a scope, a set of changes). Use it when the request is approved but the action waits for someone to start it. That is the case with the explicit execution_trigger of a checklist specification, and with a reviewer's approval when the trigger is automatic_approval.
Executing a request that already ran (execution_status is success), or that is being executed right now, does nothing: the call answers 200 with the request as it is, and the action isn't sent twice. A request whose execution failed can be executed again.
The response carries the request after the attempt. Check its execution_status: success when the action started, failed when it didn't.
Request
Responses
- 200
- 400
- 4XX
- 5XX
The request was executed, or it had already been. Read execution_status for the result.
The request can't be executed: it isn't approved, it expired, its execution window closed, or it isn't pending to execute. The detail names the reason.
The request couldn't be processed. For example, a parameter is invalid, the resource doesn't exist, or you don't have permission. The body is a problem details object (RFC 9457).
Something went wrong on nullplatform's side. The body is a problem details object (RFC 9457).