Updating a VPC Attachment
Function
This API is used to update basic information about a VPC attachment.
Calling Method
For details, see Calling APIs.
Authorization Information
Each account root user has all the permissions required to call all APIs, but IAM users must be assigned the following required identity policy-based permissions. For details about the required permissions, see Permissions Policies and Supported Actions.
URI
PUT /v3/{project_id}/enterprise-router/{er_id}/vpc-attachments/{vpc_attachment_id}
|
Parameter |
Mandatory |
Type |
Description |
|---|---|---|---|
|
project_id |
Yes |
String |
Project ID |
|
er_id |
Yes |
String |
Enterprise router ID |
|
vpc_attachment_id |
Yes |
String |
VPC attachment ID |
Request Parameters
|
Parameter |
Mandatory |
Type |
Description |
|---|---|---|---|
|
vpc_attachment |
No |
UpdateVpcAttachmentBody object |
Request body for updating VPC information |
|
Parameter |
Mandatory |
Type |
Description |
|---|---|---|---|
|
description |
No |
String |
Description of the VPC attachment. The value contains a maximum of 36 characters in UUID format with hyphens (-). Minimum: 0 Maximum: 255 |
|
name |
No |
String |
VPC attachment name. The value can contain 1 to 64 characters, including letters, digits, underscores (_), hyphens (-), and periods (.). Minimum: 1 Maximum: 64 |
Response Parameters
Status code: 200
|
Parameter |
Type |
Description |
|---|---|---|
|
vpc_attachment |
VpcAttachmentDetails object |
VPC attachment |
|
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 |
|
|
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.sssZ |
|
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 |
Example Requests
Updating a VPC attachment (changing its name to new-vpc-attach)
PUT https://{erouter_endpoint}/v3/08d5a9564a704afda6039ae2babbef3c/enterprise-router/f1a28dfd-186f-4625-b6b1-f05e5e8609c0/vpc-attachments/3b9724e9-49ec-4d21-9191-3d703133b910
{
"vpc_attachment" : {
"name" : "new-vpc-attach"
}
}
Example Responses
Status code: 200
OK
{
"vpc_attachment" : {
"id" : "3b9724e9-49ec-4d21-9191-3d703133b910",
"name" : "new-vpc-attach",
"vpc_id" : "b715e131-3371-4e17-a2de-4f669e24439a",
"virsubnet_id" : "aacdc21d-90f9-45ef-ab48-80ec1bbe15b8",
"auto_create_vpc_routes" : false,
"project_id" : "08d5a9564a704afda6039ae2babbef3c",
"state" : "available",
"created_at" : "2020-03-11T15:13:31Z",
"updated_at" : "2020-03-11T15:13:31Z"
},
"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.