Querying Resources by Tag
Function
This API is used to query resources in a project by tag.
By default, resources and resource tags are in descending order of their creation time.
URI
POST /autoscaling-api/v1/{project_id}/{resource_type}/resource_instances/action
Parameter |
Mandatory |
Type |
Description |
---|---|---|---|
project_id |
Yes |
String |
Specifies the project ID. |
resource_type |
Yes |
String |
Specifies the resource type. An example value is scaling_group_tag. |
Request
Parameter |
Mandatory |
Type |
Description |
---|---|---|---|
tags |
No |
Array of Tag objects |
Specifies filter criteria with tags included. A maximum of 10 keys can be contained. The structure body must be complete. For details, see Table 3. |
tags_any |
No |
Array of Tag objects |
Specifies filter criteria with any tag included. A maximum of 10 keys can be contained. For details, see Table 3. |
not_tags |
No |
Array of Tag objects |
Specifies filter criteria without tags included. A maximum of 10 keys can be contained. For details, see Table 3. |
not_tags_any |
No |
Array of Tag objects |
Specifies filter criteria without any tag included. A maximum of 10 keys can be contained. For details, see Table 3. |
limit |
No |
String |
Specifies the maximum number of query records. The maximum value is 1,000, and the minimum value is 1.
|
marker |
No |
String |
Marks the paging location (index position). You are advised to use the offset parameter to set the index position. Marks the paging location (resource ID or index location). |
action |
Yes |
String |
Specifies the operation, which can be filter or count.
|
offset |
No |
String |
Specifies the index position. The query starts from the next image indexed by this parameter. The value must be a non-negative number. You do not need to specify this parameter when querying resources on the first page. When you query resources on subsequent pages, set offset to the location returned in the response body for the previous query.
|
matches |
No |
Array of match objects |
Specifies fuzzy search. For details, see Table 4. |
Parameter |
Mandatory |
Type |
Description |
---|---|---|---|
key |
Yes |
String |
Specifies the tag key. It contains a maximum of 36 Unicode characters. It cannot be left blank (This parameter is not verified in the search process.) A maximum of 10 keys are allowed and the key cannot be left blank or an empty string. Each key must be unique. |
values |
Yes |
Array of strings |
Specifies tag values. A value contains a maximum of 43 Unicode characters. A key contains a maximum of 10 values. Each value of the same key must be unique.
|
Parameter |
Mandatory |
Type |
Description |
---|---|---|---|
key |
Yes |
String |
Specifies the key based on which to query resources. The parameter value can only be resource_name. |
value |
Yes |
String |
Specifies the value. The value is a fixed dictionary value. A value contains a maximum of 255 Unicode characters. If the value is an empty string or resource_id, exact match is used. |
Example Request
- This example queries the details of AS groups of a tenant using the following search criteria: including the tag (key = key1 and value = value1), excluding the tag (key = key2 and value = value2), index position 100, and a maximum number of 100 records.
POST https: //{Endpoint}/autoscaling-api/v1/{project_id}/scaling_group_tag/resource_instances/action { "offset": "100", "limit": "100", "action": "filter", "matches": [{ "key": "resource_name", "value": "resource1" }], "not_tags": [{ "key": "key2", "values": ["value2"] }], "tags": [{ "key": "key1", "values": ["value1"] }] }
- This example counts the number of AS groups for a tenant using the following search criteria: including the tag (key = key1 and value = value1) and excluding the tag (key = key2 and value = value2).
POST https: //{Endpoint}/autoscaling-api/v1/{project_id}/scaling_group_tag/resource_instances/action { "action": "count", "not_tags": [{ "key": "key2", "values": ["value2"] }], "tags": [{ "key": "key1", "values": ["value1"] }], "matches": [{ "key": "resource_name", "value": "resource1" }] }
Response
Parameter |
Type |
Description |
---|---|---|
resources |
Array of Resource objects |
Specifies tag resources. For details, see Table 6. |
total_count |
Integer |
Specifies the total number of records. When action is set to count, only this parameter is returned. The values of resources and marker are not returned. |
marker |
String |
Specifies the paging location identifier. |
Parameter |
Type |
Description |
---|---|---|
resource_id |
String |
Specifies the resource ID. |
resource_detail |
String |
Specifies the resource details. |
tags |
Array of ResourceTag objects |
Specifies tags. If there is no tag, the field tags is taken as an empty array by default. For details, see Table 7. |
resource_name |
String |
Specifies the resource name. If there is no resource, this parameter is an empty string by default. |
Example Response
- Example response when action is set to filter
{ "resources": [{ "resource_id": "64af4b6f-ec51-4436-8004-7a8f30080c87", "resource_detail": "SCALING_GROUP_TAG", "tags": [{ "key": "key1","value": "value1" }], "resource_name": "as_scaling_group_1" }, { "resource_id": "7122ef51-604b-40e7-b9b2-1de4cd78dc60", "resource_detail": "SCALING_GROUP_TAG", "tags": [{ "key": "key1","value": "value1" }], "resource_name": "as_scaling_group_2" }], "marker": "2", "total_count": 2 }
- Example response when action is set to count
{ "total_count": 1000 }
Returned Values
- Normal
- Abnormal
Returned Value
Description
400 Bad Request
The server failed to process the request.
401 Unauthorized
You must enter the username and password to access the requested page.
403 Forbidden
You are forbidden to access the requested page.
404 Not Found
The server could not find the requested page.
405 Method Not Allowed
You are not allowed to use the method specified in the request.
406 Not Acceptable
The response generated by the server could not be accepted by the client.
407 Proxy Authentication Required
You must use the proxy server for authentication to process the request.
408 Request Timeout
The request timed out.
409 Conflict
The request could not be processed due to a conflict.
500 Internal Server Error
Failed to complete the request because of an internal service error.
501 Not Implemented
Failed to complete the request because the server does not support the requested function.
502 Bad Gateway
Failed to complete the request because the request is invalid.
503 Service Unavailable
Failed to complete the request because the system is unavailable.
504 Gateway Timeout
A gateway timeout error occurred.
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