Deleting a Key Pair Tag
Function
This API is used to delete a key pair tag.
Calling Method
For details, see Calling APIs.
Authorization Information
Each account has all the permissions required to call all APIs, but IAM users must be assigned the required permissions.
- If you are using role/policy-based authorization, see Permissions Policies and Supported Actions for details on the required permissions.
- If you are using identity policy-based authorization, no identity policy-based permission required for calling this API.
URI
DELETE /v3/{project_id}/keypairs/{resource_id}/tags/{key}
| Parameter | Mandatory | Type | Description |
|---|---|---|---|
| project_id | Yes | String | Definition Project ID. For details, see Obtaining a Project ID. Constraints N/A Range The value returned by the IAM API is used, which contains 32 characters. Default Value N/A |
| resource_id | Yes | String | Definition Resource ID Constraints N/A Range N/A Default Value N/A |
| key | Yes | String | Definition Tag name Constraints For the same key pair, a tag key can have only one tag value. A tag key can be used for multiple key pairs. A key pair can have at most 20 tags. Range The value can contain 1 to 128 characters and must match the regular expression ^((?!\s)(?!sys)[\p{L}\p{Z}\p{N}_.:=+\-@]*)(?. |
Request Parameters
| Parameter | Mandatory | Type | Description |
|---|---|---|---|
| X-Auth-Token | Yes | String | Definition User token. It can be obtained by calling the IAM API. The value of X-Subject-Token in the response header is the user token. Constraints N/A Range Obtain the value by calling the IAM API for obtaining the user token. Default Value N/A |
Response Parameters
Status code: 204
None
Example Requests
None
Example Responses
None
Status Codes
| Status Code | Description |
|---|---|
| 204 | |
| 400 | Invalid parameter. |
| 401 | Authorization failed. |
| 403 | Insufficient permissions. |
| 404 | Resource or key not found. |
| 500 | System error. |
Error Codes
See Error Codes.
What is your overall rating for this page?
Thank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot