Adding or Deleting Cluster Tags in Batches
Function
This API is used to add or delete tags in batches for Elasticsearch, Logstash, and OpenSearch clusters.
Calling Method
For details, see Calling APIs.
URI
POST /v1.0/{project_id}/{resource_type}/{cluster_id}/tags/action
|
Parameter |
Mandatory |
Type |
Description |
|---|---|---|---|
|
project_id |
Yes |
String |
Definition: Project ID. For details about how to obtain the project ID and name, see Obtaining the Project ID and Name. Constraints: N/A Value range: Project ID of the account. Default value: N/A |
|
cluster_id |
Yes |
String |
Definition: ID of the cluster for which you want to add or delete tags in batches. For details about how to obtain the cluster ID, see Obtaining the Cluster ID. Constraints: N/A Value range: Cluster ID. Default value: N/A |
|
resource_type |
Yes |
String |
Definition: Cluster resource type. Currently, its value can only be css-cluster. Constraints: N/A Value range: css-cluster: Indicates the cluster type. Default value: N/A |
Request Parameters
|
Parameter |
Mandatory |
Type |
Description |
|---|---|---|---|
|
action |
Yes |
String |
Definition: Cluster tag operation type. This attribute is used to identify the required operation type. Constraints: N/A Value range:
Default value: N/A |
|
tags |
Yes |
Array of Tag objects |
Definition: List of cluster tags. Constraints: N/A Value range: N/A Default value: N/A |
|
Parameter |
Mandatory |
Type |
Description |
|---|---|---|---|
|
key |
Yes |
String |
Definition: Tag key. Constraints:
Value range: N/A Default value: N/A |
|
value |
Yes |
String |
Definition: Tag value. Constraints:
Value range: N/A Default value: N/A |
Response Parameters
Status code: 204
Request succeeded.
None
Example Requests
Create cluster tags in batches.
POST https://{Endpoint}/v1.0/{project_id}/css-cluster/4f3deec3-efa8-4598-bf91-560aad1377a3/tags/action
{
"action" : "create",
"tags" : [ {
"key" : "K1",
"value" : "V1"
}, {
"key" : "K2",
"value" : "V2"
} ]
}
Example Responses
None
Status Codes
|
Status Code |
Description |
|---|---|
|
204 |
Request succeeded. |
|
400 |
Invalid request. Do not retry the request before modification. |
|
409 |
The request could not be completed due to a conflict with the current state of the resource. This status code indicates that the resource that the client attempts to create already exists, or the request fails to be processed because of the update of the conflict request. |
|
412 |
The server did not meet one of the preconditions contained in the request. |
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.