Querying Resources by Tag
Function
Query resources by 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, the following identity policy-based permissions are required.
Action
Access Level
Resource Type (*: required)
Condition Key
Alias
Dependencies
cts:resource:filter
List
-
-
-
-
URI
POST /v3/{project_id}/{resource_type}/resource-instances/filter
|
Parameter |
Mandatory |
Type |
Description |
|---|---|---|---|
|
project_id |
Yes |
String |
Project ID. |
|
resource_type |
Yes |
String |
Resource type. The value is fixed to cts-tracker for CTS. |
|
Parameter |
Mandatory |
Type |
Description |
|---|---|---|---|
|
limit |
No |
Integer |
Number of records to be queried, which ranges from 1 to 1,000. If this parameter is not passed, the default value is 1000. |
|
offset |
No |
String |
Index position. The query starts from the next data record specified by offset. The value must be a number and cannot be negative. The default value is 0. |
Request Parameters
|
Parameter |
Mandatory |
Type |
Description |
|---|---|---|---|
|
without_any_tag |
No |
Boolean |
Whether to query only untagged resources. If this parameter is set to true, all resources without tags are queried. In this case, the true field is ignored. If this parameter is set to false or not specified, it does not take effect, meaning that all resources are returned or resources are filtered by tags or matches. |
|
tags |
No |
Array of TmsTags objects |
Tag list. A maximum of 20 keys can be included. Each key has a maximum of 20 values. |
|
matches |
No |
Array of Match objects |
Field to be matched. This parameter specifies the key-value pair to be matched in the query. If value is left blank, exact matching will work. Otherwise, fuzzy matching will work. |
Response Parameters
Status code: 200
|
Parameter |
Type |
Description |
|---|---|---|
|
resources |
Array of Resource objects |
Resource tag details. |
|
total_count |
Integer |
Total number of records in the list, which is irrelevant to pagination. |
|
Parameter |
Type |
Description |
|---|---|---|
|
resource_id |
String |
Resource ID. |
|
resource_detail |
String |
Resource details. The value is a resource object used for expansion. It is left blank by default. |
|
tags |
Map<String,ResourceTag> |
Tags of resources. If there is no tag, the value is an empty array by default. |
|
resource_name |
String |
Resource name. |
|
Parameter |
Type |
Description |
|---|---|---|
|
key |
String |
Tag key. A tag key contains a maximum of 128 Unicode characters. It can contain letters, digits, spaces, and special characters _.:=+-@. It cannot start or end with a space, or start with sys. |
|
value |
String |
Tag value. Each value contains a maximum of 255 Unicode characters. If value is specified, tags are deleted by key and value. If value is not specified, tags are deleted by key. A tag value can contain letters, digits, spaces, and special characters _.:/=+-@. It cannot start or end with a space. |
Example Requests
Query resources by tag.
https://{endpoint}/v3/{project_id}/{resource_type}/resource-instances/filter
{
"offset" : "100",
"limit" : "100",
"action" : "filter",
"without_any_tag" : true,
"tags" : [ {
"key" : "key1",
"values" : [ "*value1", "value2" ]
} ],
"tags_any" : [ {
"key" : "key1",
"values" : [ "*value1", "value2" ]
} ],
"not_tags" : [ {
"key" : "key1",
"values" : [ "*value1", "value2" ]
} ],
"not_tags_any" : [ {
"key" : "key1",
"values" : [ "*value1", "value2" ]
} ],
"sys_tags" : [ {
"key" : "key1",
"values" : [ "*value1", "value2" ]
} ],
"matches" : [ {
"key" : "resource_name",
"value" : "resource1"
} ]
}
Example Responses
Status code: 200
Request succeeded.
{
"total_count" : 1000,
"resources" : [ {
"resource_detail" : "",
"resource_id" : "xxx",
"resource_name" : "system",
"tags" : [ {
"key" : "_sys_enterprise_project_id",
"value" : "0"
}, {
"key" : "key1",
"value" : "value1"
} ]
} ]
}
Status Codes
|
Status Code |
Description |
|---|---|
|
200 |
Request succeeded. |
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