DetachService

POST {{baseUrl}}/serviceGateways/:serviceGatewayId/actions/detachService

Removes the specified Service from the list of enabled Service objects for the specified gateway. You do not need to remove any route rules that specify this Service object's cidrBlock as the destination CIDR. However, consider removing the rules if your intent is to permanently disable use of the Service through this service gateway.

Note: The DetachServiceId operation is an easy way to remove an individual Service from the service gateway. Compare it with UpdateServiceGateway, which replaces the entire existing list of enabled Service objects with the list that you provide in the Update call. UpdateServiceGateway also lets you block all traffic through the service gateway without having to remove each of the individual Service objects.

Request Body

{"serviceId"=>"in"}

HEADERS

KeyDatatypeRequiredDescription
if-matchstringFor optimistic concurrency control. In the PUT or DELETE call for a resource, set the if-match
parameter to the value of the etag from a previous GET or POST response for that resource. The resource
will be updated or deleted only if the etag you provide matches the resource's current etag value.
Content-Typestring
Datestring(Required) Current Date
Authorizationstring(Required) Signature Authentication on Authorization header
x-content-sha256string(Required) Content sha256 for POST, PUT and PATCH operations

RESPONSES

status: OK

{"compartmentId":"Ut eu esse consectetur","id":"eu ad anim","lifecycleState":"TERMINATING","vcnId":"ea culpa et Duis deserunt","blockTraffic":false,"services":[{"value":"\u003cError: Too many levels of nesting to fake this schema\u003e"},{"value":"\u003cError: Too many levels of nesting to fake this schema\u003e"}],"definedTags":{},"displayName":"Lorem Excepteur mini","freeformTags":{},"routeTableId":"ex","timeCreated":"2015-12-17T16:51:12.199Z"}