Deletes a ConfigMap instance.

Debugging

OpenAPI Explorer automatically calculates the signature value. For your convenience, we recommend that you call this operation in OpenAPI Explorer. OpenAPI Explorer dynamically generates the sample code of the operation for different SDKs.

Request headers

This operation uses only common request headers. For more information, see Common request and response headers.

Request syntax

DELETE /pop/v1/sam/configmap/configMap HTTP/1.1

Request parameters

Parameter Type Location Required Example Description
ConfigMapId Long Query Yes 1

The ID of the ConfigMap instance that you want to delete. You can call the ListNamespacedConfigMaps operation to obtain the ID of the ConfigMap instance.

Response parameters

Parameter Type Example Description
RequestId String 91F93257-7A4A-4BD3-9A7E-2F6EAE6D****

The ID of the request.

Message String success

The returned information. Valid values:

  • If the call is successful, success is returned.
  • If the call fails, an error code is returned.
TraceId String 0a98a02315955564772843261e****

The ID of the trace. The ID is used to query the details of a request.

Data Object

The returned result.

ConfigMapId Long 1

The ID of the deleted ConfigMap instance.

ErrorCode String Empty

The returned error code. Valid values:

  • If the call is successful, the ErrorCode parameter is not returned.
  • If the call fails, the ErrorCode parameter is returned. For more information, see the "Error codes" section of this topic.
Code String 200

The HTTP status code. Valid values:

  • 2xx: indicates that the call was successful.
  • 3xx: indicates that the call was redirected.
  • 4xx: indicates that the call failed.
  • 5xx: indicates that a server error occurred.
Success Boolean true

Indicates whether the ConfigMap instance was deleted. Valid values:

  • true: The instance was deleted.
  • false: The instance failed to be deleted.

Examples

Sample requests

DELETE /pop/v1/sam/configmap/configMap?ConfigMapId=1 HTTP/1.1
Host:sae.aliyuncs.com
Content-Type:application/json

Sample success responses

XML format

HTTP/1.1 200 OK
Content-Type:application/xml

<DeleteConfigMapResponse>
    <RequestId>91F93257-7A4A-4BD3-9A7E-2F6EAE6D****</RequestId>
    <Message>success</Message>
    <TraceId>0a98a02315955564772843261e****</TraceId>
    <Data>
        <ConfigMapId>1</ConfigMapId>
    </Data>
    <Code>200</Code>
    <Success>true</Success>
</DeleteConfigMapResponse>

JSON format

HTTP/1.1 200 OK
Content-Type:application/json

{
  "RequestId" : "91F93257-7A4A-4BD3-9A7E-2F6EAE6D****",
  "Message" : "success",
  "TraceId" : "0a98a02315955564772843261e****",
  "Data" : {
    "ConfigMapId" : 1
  },
  "Code" : "200",
  "Success" : true
}

Error codes

HttpCode Error code Error message Description
400 InvalidParameter.NotEmpty You must specify the parameter %s. The error message returned because the value of the %s parameter is invalid. This parameter cannot be left empty.
400 InvalidParameter.Obviously The specified parameter is invalid {%s}. The error message returned because the value of the %s parameter is invalid.
400 InvalidParameter.WithMessage The parameter is invalid {%s}: %s The error message returned because the value of the %s parameter is invalid: %s.
400 MountConflict.ConfigMap Conflict detected for ConfigMap path %s. The error message returned because the %s path on which you want to mount the ConfigMap object is occupied.
400 NotFound.ConfigMap The ConfigMap object (ID: %s) does not exist. The error message returned because the specified ConfigMap object whose ID is %s does not exist.
400 NotFound.ConfigMapKey The key %s of ConfigMap object (ID: %s) does not exist. The error message returned because the %s key of the ConfigMap object whose ID is %s does not exist.
400 DeleteFail.ConfigMapReferenced Failed to delete the ConfigMap. It has been used by other applications. The error message returned because the system failed to delete the ConfigMap object. Other applications are using the ConfigMap object.
500 OperationFailed.RPCError Internal RPC request processing error. The error message returned because the system failed to process an internal RPC request.
404 InvalidNamespaceId.NotFound The specified NamespaceId does not exist. The error message returned because the specified namespace ID does not exist.

For a list of error codes, visit the API Error Center.