Deleting Resource Tags of a Specified Cluster in Batches
Function
This API is used to delete resource tags of a specified cluster in batches.

-
This API is idempotent. If the tag key of the to-be-deleted tag does not exist, the tag will be deleted.
URI
POST /api/v3/projects/{project_id}/clusters/{cluster_id}/tags/delete
Parameter |
Mandatory |
Type |
Description |
---|---|---|---|
project_id |
Yes |
String |
Details: Project ID. For details about how to obtain the value, see How to Obtain Parameters in the API URI. Constraints: None Options: Project IDs of the account Default value: N/A |
cluster_id |
Yes |
String |
Details: Cluster ID. For details about how to obtain the value, see How to Obtain Parameters in the API URI. Constraints: None Options: Cluster IDs Default value: N/A |
Request Parameters
Parameter |
Mandatory |
Type |
Description |
---|---|---|---|
Content-Type |
Yes |
String |
Details: The request body type or format Constraints: The GET method is not verified. Options:
Default value: N/A |
X-Auth-Token |
Yes |
String |
Details: Requests for calling an API can be authenticated using either a token or AK/SK. If token-based authentication is used, this parameter is mandatory and must be set to a user token. For details, see Obtaining a User Token. Constraints: None Options: N/A Default value: N/A |
Parameter |
Mandatory |
Type |
Description |
---|---|---|---|
tags |
Yes |
Array of ResourceDeleteTag objects |
List of cluster resource tags to be deleted |
Parameter |
Mandatory |
Type |
Description |
---|---|---|---|
key |
No |
String |
The key value of the resource tag
|
Response Parameters
Status code: 204
No Content
None
Example Requests
Deleting Resource Tags of a Specified Cluster in Batches
POST /api/v3/projects/{project_id}/clusters/{cluster_id}/tags/delete { "tags" : [ { "key" : "key1" }, { "key" : "key2" } ] }
Example Responses
None
Status Codes
Status Code |
Description |
---|---|
204 |
No Content |
Error Codes
See Error Codes.
Feedback
Was this page helpful?
Provide feedbackThank 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