Modifies the name, description, and automatic route publishing setting for a VBR connection on an Enterprise Edition transit router.
Operation description
UpdateTransitRouterVbrAttachmentAttribute is an asynchronous operation. After you send a request, the system returns a RequestId, but the operation is still in progress in the background. You can call the ListTransitRouterVbrAttachments operation to query the status of the VBR connection.
If a VBR connection is in the Modifying state, you can only query the VBR connection and cannot perform other operations.
If a VBR connection is in the Attached state, the modification is complete.
Try it now
Test
RAM authorization
|
Action |
Access level |
Resource type |
Condition key |
Dependent action |
|
cen:UpdateTransitRouterVbrAttachmentAttribute |
update |
*TransitRouterVbrAttachment
|
None | None |
Request parameters
|
Parameter |
Type |
Required |
Description |
Example |
| ClientToken |
string |
No |
The client token that is used to ensure the idempotence of the request. You can use your client to generate a token, but you must make sure that the token is unique among different requests. The client token can contain only ASCII characters. Note
If you do not specify this parameter, the system automatically uses the RequestId of the request as the ClientToken. The RequestId may be different for each API request. |
02fb3da4-130e-11e9-8e44-001**** |
| TransitRouterAttachmentId |
string |
Yes |
The ID of the VBR connection. |
tr-attach-oyf70wfuorwx87**** |
| TransitRouterAttachmentName |
string |
No |
The new name of the VBR connection. The name can be empty or 1 to 128 characters in length. It cannot start with |
testname |
| TransitRouterAttachmentDescription |
string |
No |
The new description of the VBR connection. The description can be empty or 1 to 256 characters in length. It cannot start with |
testdesc |
| AutoPublishRouteEnabled |
boolean |
No |
Specifies whether to allow the Enterprise Edition transit router to automatically publish routes to the VBR instance. Valid values:
|
true |
| DryRun |
boolean |
No |
Specifies whether to perform a dry run. Valid values:
|
false |
Response elements
|
Element |
Type |
Description |
Example |
|
object |
The response. |
||
| RequestId |
string |
The request ID. |
91B36DC3-FF8A-45C3-AC1E-456B1789136D |
Examples
Success response
JSON format
{
"RequestId": "91B36DC3-FF8A-45C3-AC1E-456B1789136D"
}
Error codes
|
HTTP status code |
Error code |
Error message |
Description |
|---|---|---|---|
| 400 | InvalidTransitRouterAttachmentId.NotFound | TransitRouterAttachmentId is not found. | The error message returned because the ID of the network instance does not exist. |
| 400 | IncorrectStatus.TransitRouterAttachment | The status of TransitRouterAttachment is incorrect. | The error message returned because the status of the transit router attachment does not support this operation. Try again later. |
| 400 | InvalidParameter | Invalid parameter. | The error message returned because the parameter is set to an invalid value. |
| 400 | Unauthorized | The AccessKeyId is unauthorized. | The error message returned because you do not have the permissions to perform this operation. |
| 400 | InvalidParameter.OrderType | The specified parameter OrderType is invalid. | The specified parameter OrderType is invalid. |
| 400 | InvalidOperation.OrderTypeMustMatchGrantCrossAccount | The OrderType must be the same as the OrderType in the grant cross-account record. | The OrderType must be the same as the OrderType in the grant cross-account record. |
| 400 | OperationFailed.GrantCrossAccountNotExist | Cross-account authorization does not exist. | Cross-account authorization does not exist. |
See Error Codes for a complete list.
Release notes
See Release Notes for a complete list.