Querying VPC Attachments
Function
This API is used to query the VPC attachments of the enterprise router.
Constraints
There are some constraints:
-
Filtering query is supported. The supported query criteria include id, state, enterprise_project_id, and vpc_id. You can query multiple resources at a time or use combined criteria to query resources.
-
Pagination query is supported. You can use limit and marker together for pagination query.
-
Only sorting by a single field (id, name, description, created_at, or updated_at) is supported.
Calling Method
For details, see Calling APIs.
URI
GET /v3/{project_id}/enterprise-router/{er_id}/vpc-attachments
Parameter |
Mandatory |
Type |
Description |
---|---|---|---|
project_id |
Yes |
String |
Project ID |
er_id |
Yes |
String |
Enterprise router ID |
Parameter |
Mandatory |
Type |
Description |
---|---|---|---|
limit |
No |
Integer |
Number of records on each page. Value range: 0 to 2000 Minimum: 0 Maximum: 2000 |
marker |
No |
String |
ID of the last enterprise router on the previous page. If this parameter is left blank, the first page is queried. This parameter must be used together with limit. Minimum: 1 Maximum: 128 |
state |
No |
Array of strings |
Attachment status. Value options: pending, available, modifying, deleting, deleted, failed, pending_acceptance, rejected, and initiating_request |
id |
No |
Array of strings |
Query by resource ID. Multiple resources can be queried at a time. |
sort_key |
No |
Array of strings |
Keyword for sorting. The keyword can be id, name, or state. By default, id is used. |
sort_dir |
No |
Array of strings |
Sorting order. There are two value options: asc (ascending order) and desc (descending order). The default value is asc. |
vpc_id |
No |
Array of strings |
VPC id |
Request Parameters
None
Response Parameters
Status code: 200
Parameter |
Type |
Description |
---|---|---|
vpc_attachments |
Array of VpcAttachmentDetails objects |
VPC attachments |
page_info |
PageInfo object |
Pagination query information |
request_id |
String |
Request ID |
Parameter |
Type |
Description |
---|---|---|
id |
String |
VPC attachment ID |
name |
String |
VPC attachment name |
vpc_id |
String |
VPC id |
virsubnet_id |
String |
VPC subnet ID |
auto_create_vpc_routes |
Boolean |
The default value is false. If this parameter is set to true, routes with this enterprise router as the next hop and 10.0.0.0/8, 172.16.0.0/12, and 192.168.0.0/16 as the destinations will be automatically added to the route tables of the VPC. Default: false |
state |
String |
VPC attachment status. The value can be pending, available, modifying, deleting, deleted, failed, initiating_request, rejected, pending_acceptance, freezed, or invalid. |
created_at |
String |
Creation time in the format of YYYY-MM-DDTHH:mm:ss.sssZ |
updated_at |
String |
Update time in the format of YYYY-MM-DDTHH:MM:SS |
tags |
Array of Tag objects |
Tag information |
description |
String |
Description of the VPC attachment |
project_id |
String |
Project ID |
vpc_project_id |
String |
ID of the project that the VPC belongs to |
route_synchronization |
RouteSynchronization object |
Route synchronization setting. |
Parameter |
Type |
Description |
---|---|---|
key |
String |
Tag key.
Minimum: 1 Maximum: 128 |
value |
String |
Tag value.
Minimum: 0 Maximum: 255 |
Parameter |
Type |
Description |
---|---|---|
route_synchronization_enable |
Boolean |
Whether to enable route synchronization. |
vpc_route_table_type |
String |
VPC route table where routes are to be synchronized. |
route_type |
String |
Type of the route to be synchronized. |
conflict_policy |
String |
A conflict policy that specifies whether to synchronize routes with the same destination and next hop to the VPC route table. |
Example Requests
-
Querying all VPC attachments in pagination
GET https://{erouter_endpoint}/v3/08d5a9564a704afda6039ae2babbef3c/enterprise-router/vpc-attachments?limit=10
-
Querying all VPC attachments
GET https://{erouter_endpoint}/v3/08d5a9564a704afda6039ae2babbef3c/enterprise-router/vpc-attachments
Example Responses
Status code: 200
OK
{ "vpc_attachments" : [ { "id" : "6f83b848-8331-4271-ac0c-ef94b7686402", "name" : "vpc-attach-01", "vpc_id" : "b715e131-3371-4e17-a2de-4f669e24439a", "virsubnet_id" : "aacdc21d-90f9-45ef-ab48-80ec1bbe15b8", "project_id" : "08d5a9564a704afda6039ae2babbef3c", "state" : "available", "created_at" : "2020-03-11T15:13:31Z", "updated_at" : "2020-03-11T15:13:31Z" }, { "id" : "6f83b848-8331-4271-ac0c-ef94b7686402", "name" : "vpc-attach-01", "vpc_id" : "4b8567f6-358f-4a7f-8cd3-3cbb82c0b25f", "virsubnet_id" : "2b55f334-a15e-43a9-ab11-b34c2dbb6fac", "project_id" : "08d5a9564a704afda6039ae2babbef3c", "state" : "available", "created_at" : "2020-03-11T15:13:31Z", "updated_at" : "2020-03-11T15:13:31Z" } ], "page_info" : { "next_marker" : "1", "current_count" : 2 }, "request_id" : "915a14a6-867b-4af7-83d1-70efceb146f9" }
Status Codes
Status Code |
Description |
---|---|
200 |
OK |
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