Jump to

• Request
• Response
• Examples

Delete a capacity category

delete

/rest/ofscMetadata/v1/capacityCategories/{label}

This operation deletes the specified capacity category.

Request

Path Parameters

• label(required): string
  Minimum Length: 1

  Maximum Length: 40

  The label of the capacity category.

Back to Top

Response

Supported Media Types

• application/schema+json
• application/json

204 Response

This section describes the 204 status response for this operation.

Default Response

This section describes the default error response for this operation.

Body ()

Root Schema : Error

Type: object

Show Source

• detail: string
  The detailed description of this error.
• status: string
  The HTTP status code of this error.
• title(required): string
  The brief description of this error.
• type(required): string
  The URL of the web page containing more details about this error.

{
    "properties":{
        "type":{
            "type":"string",
            "description":"The URL of the web page containing more details about this error."
        },
        "title":{
            "type":"string",
            "description":"The brief description of this error."
        },
        "status":{
            "type":"string",
            "description":"The HTTP status code of this error."
        },
        "detail":{
            "type":"string",
            "description":"The detailed description of this error."
        }
    },
    "required":[
        "type",
        "title"
    ]
}

Back to Top

Examples

The following example shows how to delete a capacity category by submitting a DELETE request on the REST resource.

Example of Request Header

The following shows an example of the request header.

DELETE /rest/ofscMetadata/v1/capacityCategories/test1
Connection: close
Accept-Encoding: gzip,deflate
Authorization: Basic bXlyb290QHFhNTUwMzox
Host: <instance_name>.fs.ocs.oraclecloud.com
User-Agent: Apache-HttpClient/4.1.1 (java 1.5)

Example of Response Header

The following shows an example of the response header.

HTTP/1.1 204 No Content
Server: nginx
Date: Wed, 23 Aug 2017 14:53:00 GMT
Content-Type: text/html; charset=utf-8
Connection: keep-alive
Access-Control-Allow-Credentials: true
Strict-Transport-Security: max-age=31536000; includeSubDomains;

Back to Top