Querying Transit Subnets by Tag
Function
This API is used to query transit subnets by tag.
TMS uses this API to filter and list transit subnets by tag.
Calling Method
For details, see Calling APIs.
URI
POST /v3/{project_id}/transit-subnets/resource_instances/action
Parameter |
Mandatory |
Type |
Description |
---|---|---|---|
project_id |
Yes |
String |
Specifies the project ID. |
Request Parameters
Parameter |
Mandatory |
Type |
Description |
---|---|---|---|
X-Auth-Token |
Yes |
String |
User token. It is a response to the API for obtaining a user token. This API is the only one that does not require authentication. The value of X-Subject-Token in the response header is the token value. |
Parameter |
Mandatory |
Type |
Description |
---|---|---|---|
offset |
No |
String |
Specifies the index position. The query starts from the next data record indexed by this parameter. When querying resources on the first page, you do not need to specify this parameter. When querying resources on subsequent pages, set this parameter to the value returned in the response body for querying resources on the previous page. This parameter is not available when action is set to count. If action is set to filter, the value must be a positive number, and the default value is 0. |
limit |
No |
String |
Specifies the number of records to be queried. This parameter is not available when action is set to count. If action is set to filter, the default value is 1000, which is also the maximum value. The minimum value is 1. The value cannot be a negative number. |
action |
Yes |
String |
Specifies the operation to be performed. The value can be filter or count. The value filter indicates pagination query. The value count indicates that the total number of query results meeting the search criteria will be returned. |
matches |
No |
Array of Match objects |
Specifies the search field. The tag key is the field to be matched, for example, resource_name. The tag value indicates the value to be matched. This field is a fixed dictionary value. You can determine whether fuzzy match is required based on different fields. For example, if key is set to resource_name, fuzzy search (case insensitive) is used by default. If value is an empty string, exact match is used. If key is set to resource_id, exact match is used. Currently, only resource_name is supported. |
not_tags |
No |
Array of Tags objects |
The resources to be queried do not contain tags listed in not_tags. Each resource to be queried contains a maximum of 20 keys. Each tag key can have a maximum of 20 tag values. The structure body cannot be missing, and the key cannot be left blank or set to an empty string. Each tag key must be unique, and each tag value in a tag must be unique.Resources that do not contain the tags listed in not_tags will be returned.Keys are in AND relationship, and values in a tag are in OR relationship.If this parameter is not specified, all resources will be returned. |
tags |
No |
Array of Tags objects |
The resources to be queried contain tags listed in tags. Each resource to be queried contains a maximum of 20 keys. Each tag key can have a maximum of 20 tag values. The structure body cannot be missing, and the key cannot be left blank or set to an empty string. Each tag key must be unique, and each tag value in a tag must be unique.Resources that contain the tags listed in *tags will be returned.Keys are in AND relationship, and values in a tag are in OR relationship.If this parameter is not specified, all resources will be returned. |
tags_any |
No |
Array of Tags objects |
The resources to be queried contain any tag listed in tags_any. Each resource to be queried contains a maximum of 20 keys. Each tag key can have a maximum of 20 tag values. The structure body cannot be missing, and the key cannot be left blank or set to an empty string. Each tag key must be unique, and each tag value in a tag must be unique.Resources that contain any tag listed in *tags_any will be returned.Keys are in AND relationship, and values in a tag are in OR relationship.If this parameter is not specified, all resources will be returned. |
not_tags_any |
No |
Array of Tags objects |
The resources to be queried do not contain any tag listed in not_tags_any. Each resource to be queried contains a maximum of 20 keys. Each tag key can have a maximum of 20 tag values. The structure body cannot be missing, and the key cannot be left blank or set to an empty string. Each tag key must be unique, and each tag value in a tag must be unique.Resources that do not contain any tag listed in not_tags_any will be returned.Keys are in AND relationship, and values in a tag are in OR relationship.If this parameter is not specified, all resources will be returned. |
Parameter |
Mandatory |
Type |
Description |
---|---|---|---|
key |
Yes |
String |
Specifies the tag key used to search for resources. |
value |
Yes |
String |
Specifies the tag value used to search for resources. |
Parameter |
Mandatory |
Type |
Description |
---|---|---|---|
key |
Yes |
String |
Specifies the tag key. A key can contain up to 128 Unicode characters. (The system does not verify key when searching for resources.) key cannot be left blank or be an empty string. key cannot contain spaces. Before using the value of key, delete spaces before and after the value. |
values |
Yes |
Array of strings |
Specifies the list of tag values. Each value can contain a maximum of 255 Unicode characters and cannot contain spaces. Before verification and use, delete spaces before and after the value. The value can be an empty array but cannot be left blank. If values is not specified, any parameter value can be queried. All values of a tag key are in the OR relationship. The system verifies the length, but not the character set of values when searching for resources. |
Response Parameters
Status code: 200
Parameter |
Type |
Description |
---|---|---|
resources |
Array of Resource objects |
Specifies the resource list. |
request_id |
String |
Specifies the request ID. |
total_count |
Integer |
Specifies the total number of records. |
Parameter |
Type |
Description |
---|---|---|
resource_detail |
Object |
Specifies the resource details. This parameter is used for extension and is left blank by default. |
resource_id |
String |
Specifies the resource ID. |
resource_name |
String |
Specifies the resource name. This parameter is an empty string by default if there is no resource name. |
resource_tag |
Array of ResourceTag objects |
Specifies the list of queried tags. If no tag is matched, an empty array is returned. |
Example Requests
-
Querying transit subnets by tag (Setting action to filter and limit to 1000)
POST https://{Endpoint}/v3/cfa563efb77d4b6d9960781d82530fd8/transit-subnets/resource_instances/action { "offset" : "0", "limit" : "1000", "action" : "filter", "not_tags_any" : [ { "key" : "owner", "values" : "tag_1_value" } ] }
-
Querying transit subnets by tag (Setting action to count and specifying search criteria)
POST https://{Endpoint}/v3/cfa563efb77d4b6d9960781d82530fd8/transit-subnets/resource_instances/action { "action" : "count", "tags" : [ { "key" : "key1", "values" : [ "value1", "value2" ] } ], "matches" : [ { "key" : "resource_name", "value" : "resource1" } ] }
Example Responses
Status code: 200
Query operation succeeded.
Example 1: the response body when action is set to filter
Example 2: the response body when action is set to count
-
Example 1
{ "resources" : [ { "resource_detail" : null, "resource_id" : "ae33be9b-d2c0-441b-a8d0-f6dafedf1778", "resource_name" : "transit_subnets", "resource_tag" : [ { "key" : "key1", "value" : "value1" }, { "key" : "key2", "value" : "value1" } ] } ], "request_id" : "9e47d9476cfd346f864cb77acb274185", "total_count" : 1 }
-
Example 2
{ "request_id" : "d70aabc854d3d301f9bb106e6b70ac99", "total_count" : 100 }
Status Codes
Status Code |
Description |
---|---|
200 |
Query operation succeeded. Example 1: the response body when action is set to filter Example 2: the response body when action is set to count |
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