Cancel or delete a deployment
/apiplatform/management/v1/gateways/{gwId}/deployments/{depId}
Cancels the {depId}
deployment in REQUESTING
state or deletes the {depId}
deployment in REJECTED
state on the {gwId}
gateway.
Users requesting this resource must be assigned the API Manager, or Gateway Manager role and must be issued the Deploy to Gateway or Request Deployment to Gateway grant for the specified gateway. Users must also be issued the Deploy API grant for the deployment they want to cancel or delete.
Request
- application/json
-
depId: string
A unique ID referencing a specific deployment.
-
gwId: string
A unique ID referencing a specific gateway.
Response
- application/json
204 Response
403 Response
object
-
detail(optional):
string
Detailed error message
-
errorCode(optional):
string
Application specific error code
-
errorDetails(optional):
array errorDetails
additional errors
-
errorPath(optional):
string
-
instance(optional):
string
URI to the link that provides more detail about the error
-
status(optional):
string
HTTP status code
-
title:
string
Summary error message
-
type:
string
Error type
500 Response
object
-
detail(optional):
string
Detailed error message
-
errorCode(optional):
string
Application specific error code
-
errorDetails(optional):
array errorDetails
additional errors
-
errorPath(optional):
string
-
instance(optional):
string
URI to the link that provides more detail about the error
-
status(optional):
string
HTTP status code
-
title:
string
Summary error message
-
type:
string
Error type
Examples
The following example shows how to cancel or delete a deployment by submitting a DELETE request on the REST resource using cURL. For more information about cURL, see Use cURL
curl -i -X DELETE
-H "Authorization: Bearer access_token"
https://example.com/apiplatform/management/v1/gateways/{gwId}/deployments/{depId}
-
{gwId}
is the unique of a gateway. To retrieve available gateway Ids, see Get gateways. -
{depId}
is the unique Id for a deployment. To retrieve available deployment Ids, see Get deployed APIs.
Example of Response Headers
The following shows an example of the response headers.
HTTP/1.1 204 No Content Server: Oracle-Traffic-Director/12.2.1.0.0 Date: Fri, 17 Mar 2017 09:45:33 GMT X-oracle-dms-ecid: f102c33f-1c5b-4409-806d-03bf5706c492-0002b5e4 X-oracle-dms-rid: 0:1 Via: 1.1 otd_opc Proxy-agent: Oracle-Traffic-Director/12.2.1.0.0