Dell PowerStore REST API Developers Guide

PDF

Deleting a resource instance

To delete a resource instance, use the following request components:

Table 1. Example of a resource instance delete operationThis table shows the components of a DELETE operation including the headers, URI pattern, and body.
Component	Details
Headers	Accept: application/json Authorization: <auth_cookie> If a resource type has request arguments for the DELETE operation, you must also use the following header: Content-Type: application/json
Operation	DELETE
URI pattern	/api/rest/<resource_type>/<id> where: <resource_type> is the resource type of the instance that you want to delete. <id> is the unique identifier of the instance that you want to delete. For additional functionality, such as making the request an asynchronous request, you can append one or more request parameters to the URI.
Body	For most resource types, the body of a DELETE request is empty. However, if a resource type has request arguments for the DELETE operation, they are passed as a comma-separated list of standard JSON name:value pairs.

If the request succeeds, it returns a 204 No Content HTTP status code and an empty response body. If the request does not succeed, the server returns a 4xx or 5xx HTTP status code in the response header and a message entity in the response body.

Deleting a volume_group instance

The following request deletes the volume_group instance that has an id of 23772434-6373-4748-aa1a-f4197475812a:

Table 2. Example of a volume group delete operationThis table shows the components of a DELETE operation to delete a volume group and shows the details of those components.
Component	Details
Headers	Accept: application/json Content-Type: application/json Authorization: <auth_cookie>
Request	DELETE https://1.2.3.4/api/rest/volume_group/23772434-6373-4748-aa1a-f4197475812a
Request body	Empty.
Response body	Empty.