@alicloud/vpc20160428 7.2.5 → 7.3.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (131) hide show
  1. package/dist/client.d.ts +195 -104
  2. package/dist/client.js +239 -136
  3. package/dist/client.js.map +1 -1
  4. package/dist/models/ActivateRouterInterfaceRequest.d.ts +1 -0
  5. package/dist/models/ActivateRouterInterfaceRequest.js.map +1 -1
  6. package/dist/models/AllocateEipAddressRequest.d.ts +14 -14
  7. package/dist/models/AssociateVpcCidrBlockRequest.d.ts +5 -5
  8. package/dist/models/AssociateVpcCidrBlockResponseBody.d.ts +1 -1
  9. package/dist/models/AttachDhcpOptionsSetToVpcRequest.d.ts +2 -2
  10. package/dist/models/AttachVbrToVpconnRequest.d.ts +6 -4
  11. package/dist/models/AttachVbrToVpconnRequest.js.map +1 -1
  12. package/dist/models/AttachVbrToVpconnResponseBody.d.ts +1 -1
  13. package/dist/models/CompletePhysicalConnectionLoarequest.d.ts +11 -11
  14. package/dist/models/ConnectRouterInterfaceRequest.d.ts +1 -1
  15. package/dist/models/CreateCustomerGatewayRequest.d.ts +4 -4
  16. package/dist/models/CreateCustomerGatewayResponseBody.d.ts +1 -1
  17. package/dist/models/CreateEnhancedVpnGatewayRequest.d.ts +3 -3
  18. package/dist/models/CreateFailoverTestJobRequest.d.ts +10 -10
  19. package/dist/models/CreateFailoverTestJobResponseBody.d.ts +1 -1
  20. package/dist/models/CreateRouteTargetGroupRequest.d.ts +8 -9
  21. package/dist/models/CreateRouteTargetGroupRequest.js.map +1 -1
  22. package/dist/models/CreateVirtualPhysicalConnectionRequest.d.ts +9 -9
  23. package/dist/models/CreateVswitchRequest.d.ts +26 -9
  24. package/dist/models/CreateVswitchRequest.js +4 -0
  25. package/dist/models/CreateVswitchRequest.js.map +1 -1
  26. package/dist/models/DeleteBgpNetworkRequest.d.ts +4 -4
  27. package/dist/models/DeletePublicIpAddressPoolCidrBlockRequest.d.ts +3 -3
  28. package/dist/models/DeleteRouteEntriesRequest.d.ts +2 -2
  29. package/dist/models/DeleteRouteEntriesResponseBody.d.ts +2 -2
  30. package/dist/models/DescribePhysicalConnectionLoarequest.d.ts +2 -1
  31. package/dist/models/DescribePhysicalConnectionLoarequest.js.map +1 -1
  32. package/dist/models/DescribePhysicalConnectionLoaresponseBody.d.ts +9 -6
  33. package/dist/models/DescribePhysicalConnectionLoaresponseBody.js.map +1 -1
  34. package/dist/models/DescribePhysicalConnectionsRequest.d.ts +53 -2
  35. package/dist/models/DescribePhysicalConnectionsRequest.js.map +1 -1
  36. package/dist/models/DescribeRouterInterfacesRequest.d.ts +7 -7
  37. package/dist/models/DescribeRouterInterfacesResponseBody.d.ts +1 -1
  38. package/dist/models/DescribeVbrHaResponseBody.d.ts +3 -3
  39. package/dist/models/DescribeVirtualBorderRoutersForPhysicalConnectionRequest.d.ts +3 -3
  40. package/dist/models/DescribeVpcGrantRulesToEcrRequest.d.ts +7 -7
  41. package/dist/models/DescribeVpcGrantRulesToEcrResponseBody.d.ts +8 -8
  42. package/dist/models/DescribeVpcsRequest.d.ts +6 -6
  43. package/dist/models/DescribeVpcsResponseBody.d.ts +1 -1
  44. package/dist/models/EnablePhysicalConnectionRequest.d.ts +5 -7
  45. package/dist/models/EnablePhysicalConnectionRequest.js.map +1 -1
  46. package/dist/models/GetNatGatewayAttributeRequest.d.ts +1 -1
  47. package/dist/models/GetNatGatewayAttributeResponseBody.d.ts +20 -20
  48. package/dist/models/GetVpcPrefixListAssociationsRequest.d.ts +3 -3
  49. package/dist/models/GetVpcPrefixListAssociationsResponseBody.d.ts +9 -9
  50. package/dist/models/GrantInstanceToVbrRequest.d.ts +6 -6
  51. package/dist/models/GrantInstanceToVbrShrinkRequest.d.ts +6 -6
  52. package/dist/models/ListVirtualPhysicalConnectionsRequest.d.ts +7 -7
  53. package/dist/models/ListVirtualPhysicalConnectionsResponseBody.d.ts +20 -20
  54. package/dist/models/ModifyPhysicalConnectionAttributeRequest.d.ts +10 -3
  55. package/dist/models/ModifyPhysicalConnectionAttributeRequest.js.map +1 -1
  56. package/dist/models/ModifyVpcAttributeRequest.d.ts +4 -4
  57. package/dist/models/ModifyVpcCidrBlockRequest.d.ts +78 -0
  58. package/dist/models/ModifyVpcCidrBlockRequest.js +68 -0
  59. package/dist/models/ModifyVpcCidrBlockRequest.js.map +1 -0
  60. package/dist/models/ModifyVpcCidrBlockResponse.d.ts +19 -0
  61. package/dist/models/ModifyVpcCidrBlockResponse.js +69 -0
  62. package/dist/models/ModifyVpcCidrBlockResponse.js.map +1 -0
  63. package/dist/models/ModifyVpcCidrBlockResponseBody.d.ts +21 -0
  64. package/dist/models/ModifyVpcCidrBlockResponseBody.js +58 -0
  65. package/dist/models/ModifyVpcCidrBlockResponseBody.js.map +1 -0
  66. package/dist/models/ModifyVswitchAttributeRequest.d.ts +13 -3
  67. package/dist/models/ModifyVswitchAttributeRequest.js +2 -0
  68. package/dist/models/ModifyVswitchAttributeRequest.js.map +1 -1
  69. package/dist/models/MoveResourceGroupRequest.d.ts +1 -1
  70. package/dist/models/ReleaseEipAddressRequest.d.ts +2 -2
  71. package/dist/models/UnassociateVpcCidrBlockRequest.d.ts +3 -3
  72. package/dist/models/UpdateDhcpOptionsSetAttributeRequest.d.ts +12 -12
  73. package/dist/models/UpdateIpv4gatewayAttributeRequest.d.ts +6 -6
  74. package/dist/models/model.d.ts +3 -0
  75. package/dist/models/model.js +11 -5
  76. package/dist/models/model.js.map +1 -1
  77. package/package.json +1 -1
  78. package/src/client.ts +250 -136
  79. package/src/models/ActivateRouterInterfaceRequest.ts +2 -1
  80. package/src/models/AllocateEipAddressRequest.ts +14 -14
  81. package/src/models/AssociateVpcCidrBlockRequest.ts +5 -5
  82. package/src/models/AssociateVpcCidrBlockResponseBody.ts +1 -1
  83. package/src/models/AttachDhcpOptionsSetToVpcRequest.ts +2 -2
  84. package/src/models/AttachVbrToVpconnRequest.ts +6 -4
  85. package/src/models/AttachVbrToVpconnResponseBody.ts +1 -1
  86. package/src/models/CompletePhysicalConnectionLoarequest.ts +11 -11
  87. package/src/models/ConnectRouterInterfaceRequest.ts +1 -1
  88. package/src/models/CreateCustomerGatewayRequest.ts +4 -4
  89. package/src/models/CreateCustomerGatewayResponseBody.ts +1 -1
  90. package/src/models/CreateEnhancedVpnGatewayRequest.ts +3 -3
  91. package/src/models/CreateFailoverTestJobRequest.ts +10 -10
  92. package/src/models/CreateFailoverTestJobResponseBody.ts +1 -1
  93. package/src/models/CreateRouteTargetGroupRequest.ts +8 -9
  94. package/src/models/CreateVirtualPhysicalConnectionRequest.ts +9 -9
  95. package/src/models/CreateVswitchRequest.ts +30 -9
  96. package/src/models/DeleteBgpNetworkRequest.ts +4 -4
  97. package/src/models/DeletePublicIpAddressPoolCidrBlockRequest.ts +3 -3
  98. package/src/models/DeleteRouteEntriesRequest.ts +2 -2
  99. package/src/models/DeleteRouteEntriesResponseBody.ts +2 -2
  100. package/src/models/DescribePhysicalConnectionLoarequest.ts +2 -1
  101. package/src/models/DescribePhysicalConnectionLoaresponseBody.ts +9 -6
  102. package/src/models/DescribePhysicalConnectionsRequest.ts +54 -3
  103. package/src/models/DescribeRouterInterfacesRequest.ts +7 -7
  104. package/src/models/DescribeRouterInterfacesResponseBody.ts +1 -1
  105. package/src/models/DescribeVbrHaResponseBody.ts +3 -3
  106. package/src/models/DescribeVirtualBorderRoutersForPhysicalConnectionRequest.ts +3 -3
  107. package/src/models/DescribeVpcGrantRulesToEcrRequest.ts +7 -7
  108. package/src/models/DescribeVpcGrantRulesToEcrResponseBody.ts +8 -8
  109. package/src/models/DescribeVpcsRequest.ts +6 -6
  110. package/src/models/DescribeVpcsResponseBody.ts +1 -1
  111. package/src/models/EnablePhysicalConnectionRequest.ts +5 -7
  112. package/src/models/GetNatGatewayAttributeRequest.ts +1 -1
  113. package/src/models/GetNatGatewayAttributeResponseBody.ts +20 -20
  114. package/src/models/GetVpcPrefixListAssociationsRequest.ts +3 -3
  115. package/src/models/GetVpcPrefixListAssociationsResponseBody.ts +9 -9
  116. package/src/models/GrantInstanceToVbrRequest.ts +6 -6
  117. package/src/models/GrantInstanceToVbrShrinkRequest.ts +6 -6
  118. package/src/models/ListVirtualPhysicalConnectionsRequest.ts +7 -7
  119. package/src/models/ListVirtualPhysicalConnectionsResponseBody.ts +20 -20
  120. package/src/models/ModifyPhysicalConnectionAttributeRequest.ts +10 -3
  121. package/src/models/ModifyVpcAttributeRequest.ts +4 -4
  122. package/src/models/ModifyVpcCidrBlockRequest.ts +101 -0
  123. package/src/models/ModifyVpcCidrBlockResponse.ts +40 -0
  124. package/src/models/ModifyVpcCidrBlockResponseBody.ts +34 -0
  125. package/src/models/ModifyVswitchAttributeRequest.ts +15 -3
  126. package/src/models/MoveResourceGroupRequest.ts +1 -1
  127. package/src/models/ReleaseEipAddressRequest.ts +2 -2
  128. package/src/models/UnassociateVpcCidrBlockRequest.ts +3 -3
  129. package/src/models/UpdateDhcpOptionsSetAttributeRequest.ts +12 -12
  130. package/src/models/UpdateIpv4gatewayAttributeRequest.ts +6 -6
  131. package/src/models/model.ts +3 -0
package/src/client.ts CHANGED
@@ -49,42 +49,6 @@ export default class Client extends OpenApi {
49
49
  'cn-zhengzhou-nebula-1': "vpc-nebula.cn-qingdao-nebula.aliyuncs.com",
50
50
  'eu-west-1-oxs': "vpc-nebula.cn-shenzhen-cloudstone.aliyuncs.com",
51
51
  'rus-west-1-pop': "vpc.aliyuncs.com",
52
- 'cn-beijing': "vpc.cn-beijing.aliyuncs.com",
53
- 'cn-heyuan': "vpc.cn-heyuan.aliyuncs.com",
54
- 'cn-zhangjiakou': "vpc.cn-zhangjiakou.aliyuncs.com",
55
- 'ap-northeast-2': "vpc.ap-northeast-2.aliyuncs.com",
56
- 'ap-northeast-1': "vpc.ap-northeast-1.aliyuncs.com",
57
- 'ap-southeast-1': "vpc.ap-southeast-1.aliyuncs.com",
58
- 'ap-southeast-3': "vpc.ap-southeast-3.aliyuncs.com",
59
- 'ap-southeast-5': "vpc.ap-southeast-5.aliyuncs.com",
60
- 'ap-southeast-6': "vpc.ap-southeast-6.aliyuncs.com",
61
- 'ap-southeast-7': "vpc.ap-southeast-7.aliyuncs.com",
62
- 'ap-southeast-8': "vpc.ap-southeast-8.aliyuncs.com",
63
- 'cn-zhongwei': "vpc.cn-zhongwei.aliyuncs.com",
64
- 'cn-wulanchabu': "vpc.cn-wulanchabu.aliyuncs.com",
65
- 'cn-qingdao': "vpc.cn-qingdao.aliyuncs.com",
66
- 'cn-wuhan-lr': "vpc.cn-wuhan-lr.aliyuncs.com",
67
- 'cn-shanghai': "vpc.cn-shanghai.aliyuncs.com",
68
- 'cn-hongkong': "vpc.cn-hongkong.aliyuncs.com",
69
- 'cn-shenzhen': "vpc.cn-shenzhen.aliyuncs.com",
70
- 'cn-nanjing': "vpc.cn-nanjing.aliyuncs.com",
71
- 'cn-fuzhou': "vpc.cn-fuzhou.aliyuncs.com",
72
- 'cn-chengdu': "vpc.cn-chengdu.aliyuncs.com",
73
- 'cn-guangzhou': "vpc.cn-guangzhou.aliyuncs.com",
74
- 'cn-huhehaote': "vpc.cn-huhehaote.aliyuncs.com",
75
- 'us-southeast-1': "vpc.us-southeast-1.aliyuncs.com",
76
- 'eu-west-1': "vpc.eu-west-1.aliyuncs.com",
77
- 'eu-west-2': "vpc.eu-west-2.aliyuncs.com",
78
- 'eu-central-1': "vpc.eu-central-1.aliyuncs.com",
79
- 'us-east-1': "vpc.us-east-1.aliyuncs.com",
80
- 'sa-east-1': "vpc.sa-east-1.aliyuncs.com",
81
- 'us-west-1': "vpc.us-west-1.aliyuncs.com",
82
- 'na-south-1': "vpc.na-south-1.aliyuncs.com",
83
- 'me-east-1': "vpc.me-east-1.aliyuncs.com",
84
- 'me-central-1': "vpc.me-central-1.aliyuncs.com",
85
- 'cn-beijing-finance-1': "vpc.cn-beijing-finance-1.aliyuncs.com",
86
- 'cn-heyuan-acdr-1': "vpc.cn-heyuan-acdr-1.aliyuncs.com",
87
- 'cn-wulanchabu-gic-1': "vpc.cn-wulanchabu-gic-1.aliyuncs.com",
88
52
  };
89
53
  this.checkConfig(config);
90
54
  this._endpoint = this.getEndpoint("vpc", this._regionId, this._endpointRule, this._network, this._suffix, this._endpointMap, this._endpoint);
@@ -107,7 +71,7 @@ export default class Client extends OpenApi {
107
71
  * Activates a router interface that is in the Inactive state.
108
72
  *
109
73
  * @remarks
110
- * After you call the ActivateRouterInterface operation, the router interface enters the **Activating** state and then enters the **Active** state after activation succeeds.
74
+ * After you call the ActivateRouterInterface operation, the router interface enters the **Activating** state. After the activation succeeds, the router interface enters the **Active** state.
111
75
  * Before you call this operation, the router interface must be in the **Inactive** state. The initial state of a newly created router interface is **Idle**. In non-express connect mode, you can call CreateRouterInterface to create both ends of the connection, call ModifyRouterInterfaceAttribute to configure peer information for each end, and then call ConnectRouterInterface to establish the connection. When the interface is in the **Active** state, you can call DeactivateRouterInterface to change it to the **Inactive** state, and then call this operation to reactivate it. You can call DescribeRouterInterfaceAttribute to query the current state.
112
76
  * > You cannot activate a router interface that has an overdue payment.
113
77
  *
@@ -159,7 +123,7 @@ export default class Client extends OpenApi {
159
123
  * Activates a router interface that is in the Inactive state.
160
124
  *
161
125
  * @remarks
162
- * After you call the ActivateRouterInterface operation, the router interface enters the **Activating** state and then enters the **Active** state after activation succeeds.
126
+ * After you call the ActivateRouterInterface operation, the router interface enters the **Activating** state. After the activation succeeds, the router interface enters the **Active** state.
163
127
  * Before you call this operation, the router interface must be in the **Inactive** state. The initial state of a newly created router interface is **Idle**. In non-express connect mode, you can call CreateRouterInterface to create both ends of the connection, call ModifyRouterInterfaceAttribute to configure peer information for each end, and then call ConnectRouterInterface to establish the connection. When the interface is in the **Active** state, you can call DeactivateRouterInterface to change it to the **Inactive** state, and then call this operation to reactivate it. You can call DescribeRouterInterfaceAttribute to query the current state.
164
128
  * > You cannot activate a router interface that has an overdue payment.
165
129
  *
@@ -838,8 +802,8 @@ export default class Client extends OpenApi {
838
802
  * Applies for an elastic IP address (EIP).
839
803
  *
840
804
  * @remarks
841
- * Before you call this operation, make sure that you fully understand the billing methods and pricing of EIPs. For more information, see [Billing overview](https://help.aliyun.com/document_detail/122035.html).
842
- * After you call this operation, an EIP in the **Available** state is randomly allocated in the specified region. EIPs support only ICMP, TCP, and UDP at the transport layer. EIPs do not support IGMP or SCTP.
805
+ * Make sure that you are familiar with the billing methods and pricing of EIPs before you call this operation. For more information, see [Billing overview](https://help.aliyun.com/document_detail/122035.html).
806
+ * After you call this operation, an EIP in the **Available** state is randomly allocated in the specified region. EIPs support only ICMP, TCP, and UDP at the transport layer. IGMP and SCTP are not supported.
843
807
  *
844
808
  * @param request - AllocateEipAddressRequest
845
809
  * @param runtime - runtime options for this request RuntimeOptions
@@ -965,8 +929,8 @@ export default class Client extends OpenApi {
965
929
  * Applies for an elastic IP address (EIP).
966
930
  *
967
931
  * @remarks
968
- * Before you call this operation, make sure that you fully understand the billing methods and pricing of EIPs. For more information, see [Billing overview](https://help.aliyun.com/document_detail/122035.html).
969
- * After you call this operation, an EIP in the **Available** state is randomly allocated in the specified region. EIPs support only ICMP, TCP, and UDP at the transport layer. EIPs do not support IGMP or SCTP.
932
+ * Make sure that you are familiar with the billing methods and pricing of EIPs before you call this operation. For more information, see [Billing overview](https://help.aliyun.com/document_detail/122035.html).
933
+ * After you call this operation, an EIP in the **Available** state is randomly allocated in the specified region. EIPs support only ICMP, TCP, and UDP at the transport layer. IGMP and SCTP are not supported.
970
934
  *
971
935
  * @param request - AllocateEipAddressRequest
972
936
  * @returns AllocateEipAddressResponse
@@ -2724,7 +2688,7 @@ export default class Client extends OpenApi {
2724
2688
  }
2725
2689
 
2726
2690
  /**
2727
- * Associates a Virtual Border Router (VBR) instance with shared Express Connect circuits.
2691
+ * Associates a Virtual Border Router (VBR) instance with shared Express Connect circuits. This API is used to migrate an existing VBR that was pushed cross-account to shared Express Connect circuits (shared port), completing the shared Express Connect circuits form transformation. Only the partner (Express Connect circuit owner) can call this operation.
2728
2692
  *
2729
2693
  * @param request - AttachVbrToVpconnRequest
2730
2694
  * @param runtime - runtime options for this request RuntimeOptions
@@ -2771,7 +2735,7 @@ export default class Client extends OpenApi {
2771
2735
  }
2772
2736
 
2773
2737
  /**
2774
- * Associates a Virtual Border Router (VBR) instance with shared Express Connect circuits.
2738
+ * Associates a Virtual Border Router (VBR) instance with shared Express Connect circuits. This API is used to migrate an existing VBR that was pushed cross-account to shared Express Connect circuits (shared port), completing the shared Express Connect circuits form transformation. Only the partner (Express Connect circuit owner) can call this operation.
2775
2739
  *
2776
2740
  * @param request - AttachVbrToVpconnRequest
2777
2741
  * @returns AttachVbrToVpconnResponse
@@ -3124,10 +3088,12 @@ export default class Client extends OpenApi {
3124
3088
  }
3125
3089
 
3126
3090
  /**
3127
- * Completes the construction acceptance for an Express Connect circuit.
3091
+ * Calls CompletePhysicalConnectionLOA to complete the construction and backfill the completion information after the LOA is approved and the line construction is finished.
3128
3092
  *
3129
3093
  * @remarks
3130
- * Completes the construction acceptance by calling the CompletePhysicalConnectionLOA operation. Before calling this operation, call DescribePhysicalConnectionLOA to query the LOA status. This operation can be called only when the status is **Available** or **Complete**. After an LOA application is submitted, the status changes to **Applying**. After the application is approved, the status changes to **Available**. If the application is rejected, the status changes to **Rejected**. For a rejected application, call SecondApplyPhysicalConnectionLOA to resubmit the application. After the construction acceptance is completed, the LOA status changes to **Complete**.
3094
+ * Calls the CompletePhysicalConnectionLOA operation to complete the construction. Before calling this operation, call DescribePhysicalConnectionLOA to query the LOA status. You can call this operation only when the status is **Available** or **Complete**. After an LOA application is submitted, the status changes to **Applying**. After the application is approved, the status changes to **Available**. If the application is rejected, the status changes to **Rejected**. For a rejected application, call SecondApplyPhysicalConnectionLOA to reapply. After the construction is completed, the LOA status changes to **Complete**.
3095
+ * Complete call chain:
3096
+ * CreatePhysicalConnection → ApplyPhysicalConnectionLOA (LOA enters the Applying state) → Wait for approval (Available after approval; Rejected if denied, in which case call SecondApplyPhysicalConnectionLOA or ApplyPhysicalConnectionLOA again to reapply) → CompletePhysicalConnectionLOA (backfill completion information, LOA enters the Completing state) → ConfirmPhysicalConnection (confirm the Express Connect circuit, LOA enters the Complete state).
3131
3097
  *
3132
3098
  * @param request - CompletePhysicalConnectionLOARequest
3133
3099
  * @param runtime - runtime options for this request RuntimeOptions
@@ -3206,10 +3172,12 @@ export default class Client extends OpenApi {
3206
3172
  }
3207
3173
 
3208
3174
  /**
3209
- * Completes the construction acceptance for an Express Connect circuit.
3175
+ * Calls CompletePhysicalConnectionLOA to complete the construction and backfill the completion information after the LOA is approved and the line construction is finished.
3210
3176
  *
3211
3177
  * @remarks
3212
- * Completes the construction acceptance by calling the CompletePhysicalConnectionLOA operation. Before calling this operation, call DescribePhysicalConnectionLOA to query the LOA status. This operation can be called only when the status is **Available** or **Complete**. After an LOA application is submitted, the status changes to **Applying**. After the application is approved, the status changes to **Available**. If the application is rejected, the status changes to **Rejected**. For a rejected application, call SecondApplyPhysicalConnectionLOA to resubmit the application. After the construction acceptance is completed, the LOA status changes to **Complete**.
3178
+ * Calls the CompletePhysicalConnectionLOA operation to complete the construction. Before calling this operation, call DescribePhysicalConnectionLOA to query the LOA status. You can call this operation only when the status is **Available** or **Complete**. After an LOA application is submitted, the status changes to **Applying**. After the application is approved, the status changes to **Available**. If the application is rejected, the status changes to **Rejected**. For a rejected application, call SecondApplyPhysicalConnectionLOA to reapply. After the construction is completed, the LOA status changes to **Complete**.
3179
+ * Complete call chain:
3180
+ * CreatePhysicalConnection → ApplyPhysicalConnectionLOA (LOA enters the Applying state) → Wait for approval (Available after approval; Rejected if denied, in which case call SecondApplyPhysicalConnectionLOA or ApplyPhysicalConnectionLOA again to reapply) → CompletePhysicalConnectionLOA (backfill completion information, LOA enters the Completing state) → ConfirmPhysicalConnection (confirm the Express Connect circuit, LOA enters the Complete state).
3213
3181
  *
3214
3182
  * @param request - CompletePhysicalConnectionLOARequest
3215
3183
  * @returns CompletePhysicalConnectionLOAResponse
@@ -3286,11 +3254,11 @@ export default class Client extends OpenApi {
3286
3254
  }
3287
3255
 
3288
3256
  /**
3289
- * Initiates a connection from the requester VPC router interface to the accepter.
3257
+ * Calls the ConnectRouterInterface operation to initiate a connection from the requester VPC router interface to the accepter.
3290
3258
  *
3291
3259
  * @remarks
3292
- * After you call this operation, the router interface enters the **Connecting** state. After the connection is established, the router interface enters the **Active** state.
3293
- * When you call this operation to create a VPC, note the following items:
3260
+ * After you invoke this operation, the router interface enters the **Connecting** state and transitions to the **Active** state after the connection is established.
3261
+ * When you invoke this operation to create a VPC, note the following items:
3294
3262
  * - Only a requester VPC router interface in the **Idle** state can initiate a connection to the accepter VPC.
3295
3263
  * - A maximum of one pair of interconnected router interfaces can exist between any two routers.
3296
3264
  * - If your account has a router interface with an overdue payment, you cannot initiate a connection.
@@ -3340,11 +3308,11 @@ export default class Client extends OpenApi {
3340
3308
  }
3341
3309
 
3342
3310
  /**
3343
- * Initiates a connection from the requester VPC router interface to the accepter.
3311
+ * Calls the ConnectRouterInterface operation to initiate a connection from the requester VPC router interface to the accepter.
3344
3312
  *
3345
3313
  * @remarks
3346
- * After you call this operation, the router interface enters the **Connecting** state. After the connection is established, the router interface enters the **Active** state.
3347
- * When you call this operation to create a VPC, note the following items:
3314
+ * After you invoke this operation, the router interface enters the **Connecting** state and transitions to the **Active** state after the connection is established.
3315
+ * When you invoke this operation to create a VPC, note the following items:
3348
3316
  * - Only a requester VPC router interface in the **Idle** state can initiate a connection to the accepter VPC.
3349
3317
  * - A maximum of one pair of interconnected router interfaces can exist between any two routers.
3350
3318
  * - If your account has a router interface with an overdue payment, you cannot initiate a connection.
@@ -4666,18 +4634,28 @@ export default class Client extends OpenApi {
4666
4634
  }
4667
4635
 
4668
4636
  /**
4669
- * Creates a failover test job for Express Connect.
4637
+ * Calls the CreateFailoverTestJob operation to create a failover test job for Express Connect.
4670
4638
  *
4671
4639
  * @remarks
4672
- * You cannot create a failover test job in the following scenarios:
4673
- * - A failover test job is already running in the current region and the job type of the new failover test job is set to StartNow.
4640
+ * Resource status requirements (prerequisites)
4641
+ * - Before creating a failover test job, ensure that the test resources and their associated resources are in the following states. Otherwise, the creation fails:
4642
+ * - ResourceType set to PHYSICALCONNECTION: The Express Connect circuit (including shared Express Connect circuits) must be in the Enabled state with normal billing status (no overdue payment). Otherwise, IncorrectStatus.ResourceId or IncorrectBusinessStatus.ResourceId is returned.
4643
+ * - ResourceType set to VIRTUALBORDERROUTER: The VBR must be in the active state with no overdue payment, and the Express Connect circuit to which the VBR belongs must also be in the Enabled state with no overdue payment.
4644
+ * - ResourceType set to BGPPEER: The BGP peer must be in the Available state, the VBR to which it belongs must be in the active state, and the Express Connect circuit to which the VBR belongs must be in the Enabled state, all with no overdue payment.
4645
+ * How to check and advance the Express Connect circuit status
4646
+ * - Call DescribePhysicalConnections to query the Status field of the Express Connect circuit. If the circuit is not in the Enabled state (for example, it is in the Allocated or Confirmed state), advance it along the following state transition path:
4647
+ * - Allocated (port reserved, pending confirmation) → Call ConfirmPhysicalConnection to confirm → Confirmed → Call EnablePhysicalConnection to activate (asynchronous; poll DescribePhysicalConnections after activation to confirm) → Enabled.
4648
+ * - Note: EnablePhysicalConnection only supports activating Express Connect circuits in the Confirmed state. If the circuit is in the Allocated state, call ConfirmPhysicalConnection first.
4649
+ * - When JobType is set to StartLater, the status check described above is performed during the job creation phase. When you subsequently call StartFailoverTestJob to start the job, the resource status is checked again. If the resource status does not meet the requirements at that time (for example, the circuit is no longer in the Enabled state), the start operation fails.
4650
+ * The following scenarios do not support creating failover test jobs:
4651
+ * - A failover test job is already running in the current region, and the job type of the new failover test job is set to start immediately.
4674
4652
  * - The Express Connect circuit instance or shared Express Connect circuit instance has not been paid for or has an overdue payment.
4675
4653
  * - The Express Connect circuit instance or shared Express Connect circuit instance is already in another running failover test job.
4676
4654
  *
4677
4655
  * - The Express Connect circuit instance has more than one shared Express Connect circuit.
4678
- * - The Express Connect circuit instance has more than one cross-account Virtual Border Router (VBR).
4656
+ * - The Express Connect circuit instance has more than one cross-account VBR.
4679
4657
  * - The shared Express Connect circuit instance is not associated with a VBR.
4680
- * - The VLAN of the shared Express Connect circuit instance is set to 0.
4658
+ * - The VLAN configuration of the shared Express Connect circuit instance is 0.
4681
4659
  *
4682
4660
  * @param request - CreateFailoverTestJobRequest
4683
4661
  * @param runtime - runtime options for this request RuntimeOptions
@@ -4756,18 +4734,28 @@ export default class Client extends OpenApi {
4756
4734
  }
4757
4735
 
4758
4736
  /**
4759
- * Creates a failover test job for Express Connect.
4737
+ * Calls the CreateFailoverTestJob operation to create a failover test job for Express Connect.
4760
4738
  *
4761
4739
  * @remarks
4762
- * You cannot create a failover test job in the following scenarios:
4763
- * - A failover test job is already running in the current region and the job type of the new failover test job is set to StartNow.
4740
+ * Resource status requirements (prerequisites)
4741
+ * - Before creating a failover test job, ensure that the test resources and their associated resources are in the following states. Otherwise, the creation fails:
4742
+ * - ResourceType set to PHYSICALCONNECTION: The Express Connect circuit (including shared Express Connect circuits) must be in the Enabled state with normal billing status (no overdue payment). Otherwise, IncorrectStatus.ResourceId or IncorrectBusinessStatus.ResourceId is returned.
4743
+ * - ResourceType set to VIRTUALBORDERROUTER: The VBR must be in the active state with no overdue payment, and the Express Connect circuit to which the VBR belongs must also be in the Enabled state with no overdue payment.
4744
+ * - ResourceType set to BGPPEER: The BGP peer must be in the Available state, the VBR to which it belongs must be in the active state, and the Express Connect circuit to which the VBR belongs must be in the Enabled state, all with no overdue payment.
4745
+ * How to check and advance the Express Connect circuit status
4746
+ * - Call DescribePhysicalConnections to query the Status field of the Express Connect circuit. If the circuit is not in the Enabled state (for example, it is in the Allocated or Confirmed state), advance it along the following state transition path:
4747
+ * - Allocated (port reserved, pending confirmation) → Call ConfirmPhysicalConnection to confirm → Confirmed → Call EnablePhysicalConnection to activate (asynchronous; poll DescribePhysicalConnections after activation to confirm) → Enabled.
4748
+ * - Note: EnablePhysicalConnection only supports activating Express Connect circuits in the Confirmed state. If the circuit is in the Allocated state, call ConfirmPhysicalConnection first.
4749
+ * - When JobType is set to StartLater, the status check described above is performed during the job creation phase. When you subsequently call StartFailoverTestJob to start the job, the resource status is checked again. If the resource status does not meet the requirements at that time (for example, the circuit is no longer in the Enabled state), the start operation fails.
4750
+ * The following scenarios do not support creating failover test jobs:
4751
+ * - A failover test job is already running in the current region, and the job type of the new failover test job is set to start immediately.
4764
4752
  * - The Express Connect circuit instance or shared Express Connect circuit instance has not been paid for or has an overdue payment.
4765
4753
  * - The Express Connect circuit instance or shared Express Connect circuit instance is already in another running failover test job.
4766
4754
  *
4767
4755
  * - The Express Connect circuit instance has more than one shared Express Connect circuit.
4768
- * - The Express Connect circuit instance has more than one cross-account Virtual Border Router (VBR).
4756
+ * - The Express Connect circuit instance has more than one cross-account VBR.
4769
4757
  * - The shared Express Connect circuit instance is not associated with a VBR.
4770
- * - The VLAN of the shared Express Connect circuit instance is set to 0.
4758
+ * - The VLAN configuration of the shared Express Connect circuit instance is 0.
4771
4759
  *
4772
4760
  * @param request - CreateFailoverTestJobRequest
4773
4761
  * @returns CreateFailoverTestJobResponse
@@ -7379,11 +7367,11 @@ export default class Client extends OpenApi {
7379
7367
  * Creates a route target group instance.
7380
7368
  *
7381
7369
  * @remarks
7382
- * - **CreateRouteTargetGroup** is an asynchronous operation. After you invoke this operation, the system returns an instance ID, but the routing target group instance is not yet created. The creation node continues in the background. You can invoke **ListRouteTargetGroup** to query the creation status of the routing target group:
7370
+ * - **CreateRouteTargetGroup** is an asynchronous operation. After you invoke this operation, the system returns an instance ID, but the routing target group instance is not yet created. The creation task continues in the background. You can invoke **ListRouteTargetGroup** to query the creation status of the routing target group:
7383
7371
  * - If the routing target group is in the **Pending** state, the routing target group is being created.
7384
7372
  * - If the routing target group is in the **Available**, **Unavailable**, **Switched**, or **Abnormal** state, the routing target group is created.
7385
- * - **Active/standby pattern**: When you create a routing target group, you must configure primary and secondary instances that are in different zones and of the same type.
7386
- * - **Primary instance**: The weight is 100. The primary instance handles all traffic under normal conditions and takes effect when health checks pass.
7373
+ * - **Active/standby mode**: When you create a routing target group, configure primary and secondary instances that are in different zones and of the same type.
7374
+ * - **Primary instance**: The weight is 100. The primary instance handles all traffic under normal conditions and takes effect when health checks are successful.
7387
7375
  * - **Secondary instance**: The weight is 0. The secondary instance takes over traffic when the primary instance fails, serving as disaster recovery and backup.
7388
7376
  *
7389
7377
  * @param request - CreateRouteTargetGroupRequest
@@ -7450,11 +7438,11 @@ export default class Client extends OpenApi {
7450
7438
  * Creates a route target group instance.
7451
7439
  *
7452
7440
  * @remarks
7453
- * - **CreateRouteTargetGroup** is an asynchronous operation. After you invoke this operation, the system returns an instance ID, but the routing target group instance is not yet created. The creation node continues in the background. You can invoke **ListRouteTargetGroup** to query the creation status of the routing target group:
7441
+ * - **CreateRouteTargetGroup** is an asynchronous operation. After you invoke this operation, the system returns an instance ID, but the routing target group instance is not yet created. The creation task continues in the background. You can invoke **ListRouteTargetGroup** to query the creation status of the routing target group:
7454
7442
  * - If the routing target group is in the **Pending** state, the routing target group is being created.
7455
7443
  * - If the routing target group is in the **Available**, **Unavailable**, **Switched**, or **Abnormal** state, the routing target group is created.
7456
- * - **Active/standby pattern**: When you create a routing target group, you must configure primary and secondary instances that are in different zones and of the same type.
7457
- * - **Primary instance**: The weight is 100. The primary instance handles all traffic under normal conditions and takes effect when health checks pass.
7444
+ * - **Active/standby mode**: When you create a routing target group, configure primary and secondary instances that are in different zones and of the same type.
7445
+ * - **Primary instance**: The weight is 100. The primary instance handles all traffic under normal conditions and takes effect when health checks are successful.
7458
7446
  * - **Secondary instance**: The weight is 0. The secondary instance takes over traffic when the primary instance fails, serving as disaster recovery and backup.
7459
7447
  *
7460
7448
  * @param request - CreateRouteTargetGroupRequest
@@ -8291,7 +8279,7 @@ export default class Client extends OpenApi {
8291
8279
  * @remarks
8292
8280
  * When you call this operation to create a vSwitch, take note of the following items:
8293
8281
  * - The number of vSwitches in each VPC cannot exceed 150.
8294
- * - The first IP address and the last three IP addresses of each vSwitch CIDR block are reserved by the system. For example, the system reserved IP addresses of 192.168.1.0/24 are 192.168.1.0, 192.168.1.253, 192.168.1.254, and 192.168.1.255.
8282
+ * - The first and last three IP addresses of each vSwitch CIDR block are reserved by the system. For example, the system reserved IP addresses of 192.168.1.0/24 are 192.168.1.0, 192.168.1.253, 192.168.1.254, and 192.168.1.255.
8295
8283
  * - The number of cloud service instances in a vSwitch cannot exceed the remaining available cloud service instances in the VPC (15,000 minus the current number of cloud service instances).
8296
8284
  * - A cloud service instance can belong to only one vSwitch.
8297
8285
  * - vSwitches do not support multicast or broadcast.
@@ -8313,6 +8301,10 @@ export default class Client extends OpenApi {
8313
8301
  query["CidrBlock"] = request.cidrBlock;
8314
8302
  }
8315
8303
 
8304
+ if (!$dara.isNull(request.cidrMask)) {
8305
+ query["CidrMask"] = request.cidrMask;
8306
+ }
8307
+
8316
8308
  if (!$dara.isNull(request.clientToken)) {
8317
8309
  query["ClientToken"] = request.clientToken;
8318
8310
  }
@@ -8325,6 +8317,10 @@ export default class Client extends OpenApi {
8325
8317
  query["Ipv6CidrBlock"] = request.ipv6CidrBlock;
8326
8318
  }
8327
8319
 
8320
+ if (!$dara.isNull(request.ipv6CidrMask)) {
8321
+ query["Ipv6CidrMask"] = request.ipv6CidrMask;
8322
+ }
8323
+
8328
8324
  if (!$dara.isNull(request.ownerAccount)) {
8329
8325
  query["OwnerAccount"] = request.ownerAccount;
8330
8326
  }
@@ -8388,7 +8384,7 @@ export default class Client extends OpenApi {
8388
8384
  * @remarks
8389
8385
  * When you call this operation to create a vSwitch, take note of the following items:
8390
8386
  * - The number of vSwitches in each VPC cannot exceed 150.
8391
- * - The first IP address and the last three IP addresses of each vSwitch CIDR block are reserved by the system. For example, the system reserved IP addresses of 192.168.1.0/24 are 192.168.1.0, 192.168.1.253, 192.168.1.254, and 192.168.1.255.
8387
+ * - The first and last three IP addresses of each vSwitch CIDR block are reserved by the system. For example, the system reserved IP addresses of 192.168.1.0/24 are 192.168.1.0, 192.168.1.253, 192.168.1.254, and 192.168.1.255.
8392
8388
  * - The number of cloud service instances in a vSwitch cannot exceed the remaining available cloud service instances in the VPC (15,000 minus the current number of cloud service instances).
8393
8389
  * - A cloud service instance can belong to only one vSwitch.
8394
8390
  * - vSwitches do not support multicast or broadcast.
@@ -8851,7 +8847,18 @@ export default class Client extends OpenApi {
8851
8847
  * Invokes the CreateVirtualPhysicalConnection operation to create shared Express Connect circuits.
8852
8848
  *
8853
8849
  * @remarks
8854
- * Before calling this operation, understand the creation process and environment requirements for shared Express Connect circuits. For more information, see [Overview of shared Express Connect circuits](https://help.aliyun.com/document_detail/146571.html) and [Partner operation guide](https://help.aliyun.com/document_detail/155987.html).
8850
+ * Before you call this operation, familiarize yourself with the creation process and environment requirements for shared Express Connect circuits. For more information, see [Overview of shared Express Connect circuits](https://help.aliyun.com/document_detail/146571.html) and [Partner operation guide](https://help.aliyun.com/document_detail/155987.html).
8851
+ * Before you call this operation, make sure the following conditions are met:
8852
+ * - The Express Connect circuit specified by PhysicalConnectionId is in the Enabled state. The complete process for an Express Connect circuit to reach the Enabled state includes payment and manual steps that cannot be fully automated through OpenAPI:
8853
+ * - CreatePhysicalConnection: Creates an Express Connect circuit.
8854
+ * - LOA construction authorization: If you need to enter the data center for construction, call ApplyPhysicalConnectionLOA → wait for manual LOA approval → CompletePhysicalConnectionLOA (FinishWork=true). LOA approval and construction are manual/offline steps.
8855
+ * - ConfirmPhysicalConnection: Reports construction completion. The circuit must be in the Allocated state. After success, it enters the Confirmed state.
8856
+ * - After the Confirmed state, port usage fees must be paid before the circuit enters the Enabled state. For automation scenarios, call DescribePhysicalConnections first to confirm the target circuit is in the Enabled state before calling this operation.
8857
+ * - The VlanId is not already used by an existing VBR or shared Express Connect circuit on the Express Connect circuit (valid values: 0 to 2999).
8858
+ * - The Spec value does not exceed the remaining allocatable bandwidth of the Express Connect circuit or the shared circuit bandwidth limit configured for the account that owns the Express Connect circuit.
8859
+ * - VpconnAliUid is the tenant\\"s Alibaba Cloud account (RAM users or partner accounts are not supported). Cross-site pushing is not allowed by default.
8860
+ * - The number of shared Express Connect circuits on a single Express Connect circuit has not exceeded the quota.
8861
+ * - The Express Connect circuit is not bound to a QoS policy, the access device supports MPBGP, and the access point allows the creation of shared Express Connect circuits.
8855
8862
  *
8856
8863
  * @param request - CreateVirtualPhysicalConnectionRequest
8857
8864
  * @param runtime - runtime options for this request RuntimeOptions
@@ -8929,7 +8936,18 @@ export default class Client extends OpenApi {
8929
8936
  * Invokes the CreateVirtualPhysicalConnection operation to create shared Express Connect circuits.
8930
8937
  *
8931
8938
  * @remarks
8932
- * Before calling this operation, understand the creation process and environment requirements for shared Express Connect circuits. For more information, see [Overview of shared Express Connect circuits](https://help.aliyun.com/document_detail/146571.html) and [Partner operation guide](https://help.aliyun.com/document_detail/155987.html).
8939
+ * Before you call this operation, familiarize yourself with the creation process and environment requirements for shared Express Connect circuits. For more information, see [Overview of shared Express Connect circuits](https://help.aliyun.com/document_detail/146571.html) and [Partner operation guide](https://help.aliyun.com/document_detail/155987.html).
8940
+ * Before you call this operation, make sure the following conditions are met:
8941
+ * - The Express Connect circuit specified by PhysicalConnectionId is in the Enabled state. The complete process for an Express Connect circuit to reach the Enabled state includes payment and manual steps that cannot be fully automated through OpenAPI:
8942
+ * - CreatePhysicalConnection: Creates an Express Connect circuit.
8943
+ * - LOA construction authorization: If you need to enter the data center for construction, call ApplyPhysicalConnectionLOA → wait for manual LOA approval → CompletePhysicalConnectionLOA (FinishWork=true). LOA approval and construction are manual/offline steps.
8944
+ * - ConfirmPhysicalConnection: Reports construction completion. The circuit must be in the Allocated state. After success, it enters the Confirmed state.
8945
+ * - After the Confirmed state, port usage fees must be paid before the circuit enters the Enabled state. For automation scenarios, call DescribePhysicalConnections first to confirm the target circuit is in the Enabled state before calling this operation.
8946
+ * - The VlanId is not already used by an existing VBR or shared Express Connect circuit on the Express Connect circuit (valid values: 0 to 2999).
8947
+ * - The Spec value does not exceed the remaining allocatable bandwidth of the Express Connect circuit or the shared circuit bandwidth limit configured for the account that owns the Express Connect circuit.
8948
+ * - VpconnAliUid is the tenant\\"s Alibaba Cloud account (RAM users or partner accounts are not supported). Cross-site pushing is not allowed by default.
8949
+ * - The number of shared Express Connect circuits on a single Express Connect circuit has not exceeded the quota.
8950
+ * - The Express Connect circuit is not bound to a QoS policy, the access device supports MPBGP, and the access point allows the creation of shared Express Connect circuits.
8933
8951
  *
8934
8952
  * @param request - CreateVirtualPhysicalConnectionRequest
8935
8953
  * @returns CreateVirtualPhysicalConnectionResponse
@@ -10258,6 +10276,9 @@ export default class Client extends OpenApi {
10258
10276
  /**
10259
10277
  * Deletes an advertised Border Gateway Protocol (BGP) network.
10260
10278
  *
10279
+ * @remarks
10280
+ * Before calling this operation, ensure that the BgpNetwork is in the Available state. You can query the Status field by calling DescribeBgpNetworks. After a resource is created by AddBgpNetwork, it enters the Pending state. Wait until the state changes to Available before calling this operation.
10281
+ *
10261
10282
  * @param request - DeleteBgpNetworkRequest
10262
10283
  * @param runtime - runtime options for this request RuntimeOptions
10263
10284
  * @returns DeleteBgpNetworkResponse
@@ -10317,6 +10338,9 @@ export default class Client extends OpenApi {
10317
10338
  /**
10318
10339
  * Deletes an advertised Border Gateway Protocol (BGP) network.
10319
10340
  *
10341
+ * @remarks
10342
+ * Before calling this operation, ensure that the BgpNetwork is in the Available state. You can query the Status field by calling DescribeBgpNetworks. After a resource is created by AddBgpNetwork, it enters the Pending state. Wait until the state changes to Available before calling this operation.
10343
+ *
10320
10344
  * @param request - DeleteBgpNetworkRequest
10321
10345
  * @returns DeleteBgpNetworkResponse
10322
10346
  */
@@ -12484,11 +12508,11 @@ export default class Client extends OpenApi {
12484
12508
  *
12485
12509
  * @remarks
12486
12510
  * Before you call this operation, take note of the following items:
12487
- * - Before deleting an IP address pool, make sure that the IP addresses in the pool are not in use.
12511
+ * - Before you delete an IP address pool, make sure that the IP addresses in the pool are not in use.
12488
12512
  * - **DeletePublicIpAddressPool** is an asynchronous operation. After a request is sent, the system returns a request ID and runs the task in the background. You can call [ListPublicIpAddressPools](https://help.aliyun.com/document_detail/429433.html) to query the status of the IP address pool.
12489
12513
  * - If the IP address pool is in the **Deleting** state, the IP address pool is being deleted. In this state, you can only perform query operations.
12490
12514
  * - If the IP address pool cannot be found, the IP address pool is deleted.
12491
- * - **DeletePublicIpAddressPool** does not support concurrent deletion of the same IP address pool.
12515
+ * - You cannot call **DeletePublicIpAddressPool** to concurrently delete the same IP address pool.
12492
12516
  *
12493
12517
  * @param request - DeletePublicIpAddressPoolRequest
12494
12518
  * @param runtime - runtime options for this request RuntimeOptions
@@ -12551,11 +12575,11 @@ export default class Client extends OpenApi {
12551
12575
  *
12552
12576
  * @remarks
12553
12577
  * Before you call this operation, take note of the following items:
12554
- * - Before deleting an IP address pool, make sure that the IP addresses in the pool are not in use.
12578
+ * - Before you delete an IP address pool, make sure that the IP addresses in the pool are not in use.
12555
12579
  * - **DeletePublicIpAddressPool** is an asynchronous operation. After a request is sent, the system returns a request ID and runs the task in the background. You can call [ListPublicIpAddressPools](https://help.aliyun.com/document_detail/429433.html) to query the status of the IP address pool.
12556
12580
  * - If the IP address pool is in the **Deleting** state, the IP address pool is being deleted. In this state, you can only perform query operations.
12557
12581
  * - If the IP address pool cannot be found, the IP address pool is deleted.
12558
- * - **DeletePublicIpAddressPool** does not support concurrent deletion of the same IP address pool.
12582
+ * - You cannot call **DeletePublicIpAddressPool** to concurrently delete the same IP address pool.
12559
12583
  *
12560
12584
  * @param request - DeletePublicIpAddressPoolRequest
12561
12585
  * @returns DeletePublicIpAddressPoolResponse
@@ -12571,7 +12595,7 @@ export default class Client extends OpenApi {
12571
12595
  * @remarks
12572
12596
  * Before you call this operation, take note of the following information:
12573
12597
  * - Before deleting a CIDR block, make sure that the CIDR block is not in use.
12574
- * - **DeletePublicIpAddressPoolCidrBlock** is an asynchronous operation. After a request is sent, the system returns a request ID, but the CIDR block is not yet deleted. The deletion task continues to run in the background. You can call [ListPublicIpAddressPoolCidrBlocks](https://help.aliyun.com/document_detail/429436.html) to query the status of the CIDR block in the IP address pool.
12598
+ * - **DeletePublicIpAddressPoolCidrBlock** is an asynchronous operation. After a request is sent, the system returns a request ID and runs the deletion task in the background. You can call [ListPublicIpAddressPoolCidrBlocks](https://help.aliyun.com/document_detail/429436.html) to query the status of the CIDR block in the IP address pool.
12575
12599
  * - If the CIDR block is in the **Deleting** state, the CIDR block is being deleted. In this state, you can only perform query operations.
12576
12600
  * - If the CIDR block cannot be found, the CIDR block is deleted.
12577
12601
  * - The **DeletePublicIpAddressPoolCidrBlock** operation does not support concurrent deletion of the same CIDR block.
@@ -12642,7 +12666,7 @@ export default class Client extends OpenApi {
12642
12666
  * @remarks
12643
12667
  * Before you call this operation, take note of the following information:
12644
12668
  * - Before deleting a CIDR block, make sure that the CIDR block is not in use.
12645
- * - **DeletePublicIpAddressPoolCidrBlock** is an asynchronous operation. After a request is sent, the system returns a request ID, but the CIDR block is not yet deleted. The deletion task continues to run in the background. You can call [ListPublicIpAddressPoolCidrBlocks](https://help.aliyun.com/document_detail/429436.html) to query the status of the CIDR block in the IP address pool.
12669
+ * - **DeletePublicIpAddressPoolCidrBlock** is an asynchronous operation. After a request is sent, the system returns a request ID and runs the deletion task in the background. You can call [ListPublicIpAddressPoolCidrBlocks](https://help.aliyun.com/document_detail/429436.html) to query the status of the CIDR block in the IP address pool.
12646
12670
  * - If the CIDR block is in the **Deleting** state, the CIDR block is being deleted. In this state, you can only perform query operations.
12647
12671
  * - If the CIDR block cannot be found, the CIDR block is deleted.
12648
12672
  * - The **DeletePublicIpAddressPoolCidrBlock** operation does not support concurrent deletion of the same CIDR block.
@@ -12656,16 +12680,16 @@ export default class Client extends OpenApi {
12656
12680
  }
12657
12681
 
12658
12682
  /**
12659
- * Batch deletes custom route entries.
12683
+ * Calls DeleteRouteEntries to batch delete custom route entries.
12660
12684
  *
12661
12685
  * @remarks
12662
12686
  * When you call this operation to delete routing entries, note the following items:
12663
12687
  * - Only routing entries in the **Available** state can be deleted.
12664
- * - Routing entries cannot be deleted if the VPC to which the route table belongs is creating or deleting a vSwitch or routing entries.
12665
- * - The **DeleteRouteEntries** operation is asynchronous. After you send a request, the system returns a request ID, but the custom route entry is not yet deleted. The deletion task continues to run in the background. You can call [DescribeRouteEntryList](https://help.aliyun.com/document_detail/138148.html) to query the deletion status of the custom route entry:
12666
- * - If the custom route entry is in the **Deleting** state, the custom route entry is being deleted.
12667
- * - If the specified custom route entry cannot be found, the custom route entry is deleted.
12668
- * - The **DeleteRouteEntries** operation does not support concurrent batch deletion of routing entries from route tables in the same VPC.
12688
+ * - Routing entries cannot be deleted if the VPC that contains the route table is creating or deleting a vSwitch or routing entry.
12689
+ * - The **DeleteRouteEntries** operation is asynchronous. After you send a request, the system returns a request ID, but the routing entry is not yet deleted. The deletion task is still running in the background. You can call [DescribeRouteEntryList](https://help.aliyun.com/document_detail/138148.html) to query the deletion status of the routing entry:
12690
+ * - If the routing entry is in the **Deleting** state, the routing entry is being deleted.
12691
+ * - If the specified routing entry cannot be found, the routing entry is deleted.
12692
+ * - The **DeleteRouteEntries** operation does not support concurrent batch deletion of routing entries in route tables within the same VPC.
12669
12693
  *
12670
12694
  * @param request - DeleteRouteEntriesRequest
12671
12695
  * @param runtime - runtime options for this request RuntimeOptions
@@ -12724,16 +12748,16 @@ export default class Client extends OpenApi {
12724
12748
  }
12725
12749
 
12726
12750
  /**
12727
- * Batch deletes custom route entries.
12751
+ * Calls DeleteRouteEntries to batch delete custom route entries.
12728
12752
  *
12729
12753
  * @remarks
12730
12754
  * When you call this operation to delete routing entries, note the following items:
12731
12755
  * - Only routing entries in the **Available** state can be deleted.
12732
- * - Routing entries cannot be deleted if the VPC to which the route table belongs is creating or deleting a vSwitch or routing entries.
12733
- * - The **DeleteRouteEntries** operation is asynchronous. After you send a request, the system returns a request ID, but the custom route entry is not yet deleted. The deletion task continues to run in the background. You can call [DescribeRouteEntryList](https://help.aliyun.com/document_detail/138148.html) to query the deletion status of the custom route entry:
12734
- * - If the custom route entry is in the **Deleting** state, the custom route entry is being deleted.
12735
- * - If the specified custom route entry cannot be found, the custom route entry is deleted.
12736
- * - The **DeleteRouteEntries** operation does not support concurrent batch deletion of routing entries from route tables in the same VPC.
12756
+ * - Routing entries cannot be deleted if the VPC that contains the route table is creating or deleting a vSwitch or routing entry.
12757
+ * - The **DeleteRouteEntries** operation is asynchronous. After you send a request, the system returns a request ID, but the routing entry is not yet deleted. The deletion task is still running in the background. You can call [DescribeRouteEntryList](https://help.aliyun.com/document_detail/138148.html) to query the deletion status of the routing entry:
12758
+ * - If the routing entry is in the **Deleting** state, the routing entry is being deleted.
12759
+ * - If the specified routing entry cannot be found, the routing entry is deleted.
12760
+ * - The **DeleteRouteEntries** operation does not support concurrent batch deletion of routing entries in route tables within the same VPC.
12737
12761
  *
12738
12762
  * @param request - DeleteRouteEntriesRequest
12739
12763
  * @returns DeleteRouteEntriesResponse
@@ -17914,7 +17938,7 @@ export default class Client extends OpenApi {
17914
17938
  * Queries information about Express Connect circuits in a specified region.
17915
17939
  *
17916
17940
  * @remarks
17917
- * By default, the system queries information about all Express Connect circuits in the specified region. You can use the filter options provided by the **DescribePhysicalConnections** operation to query information about specific Express Connect circuits. For the supported filter options, refer to the description of **Key** in the **request parameters** section of this topic.
17941
+ * By default, the system queries information about all Express Connect circuits in the specified region. You can use the filter options provided by the **DescribePhysicalConnections** operation to query information about specific Express Connect circuits. For the filter options supported by the system, see the description of **Key** in the **request parameters** section of this topic.
17918
17942
  *
17919
17943
  * @param request - DescribePhysicalConnectionsRequest
17920
17944
  * @param runtime - runtime options for this request RuntimeOptions
@@ -17992,7 +18016,7 @@ export default class Client extends OpenApi {
17992
18016
  * Queries information about Express Connect circuits in a specified region.
17993
18017
  *
17994
18018
  * @remarks
17995
- * By default, the system queries information about all Express Connect circuits in the specified region. You can use the filter options provided by the **DescribePhysicalConnections** operation to query information about specific Express Connect circuits. For the supported filter options, refer to the description of **Key** in the **request parameters** section of this topic.
18019
+ * By default, the system queries information about all Express Connect circuits in the specified region. You can use the filter options provided by the **DescribePhysicalConnections** operation to query information about specific Express Connect circuits. For the filter options supported by the system, see the description of **Key** in the **request parameters** section of this topic.
17996
18020
  *
17997
18021
  * @param request - DescribePhysicalConnectionsRequest
17998
18022
  * @returns DescribePhysicalConnectionsResponse
@@ -18516,7 +18540,7 @@ export default class Client extends OpenApi {
18516
18540
  }
18517
18541
 
18518
18542
  /**
18519
- * Queries router interfaces in a specified region by calling the DescribeRouterInterfaces operation.
18543
+ * Queries router interfaces in a specified region.
18520
18544
  *
18521
18545
  * @param request - DescribeRouterInterfacesRequest
18522
18546
  * @param runtime - runtime options for this request RuntimeOptions
@@ -18583,7 +18607,7 @@ export default class Client extends OpenApi {
18583
18607
  }
18584
18608
 
18585
18609
  /**
18586
- * Queries router interfaces in a specified region by calling the DescribeRouterInterfaces operation.
18610
+ * Queries router interfaces in a specified region.
18587
18611
  *
18588
18612
  * @param request - DescribeRouterInterfacesRequest
18589
18613
  * @returns DescribeRouterInterfacesResponse
@@ -20025,7 +20049,7 @@ export default class Client extends OpenApi {
20025
20049
  * Queries created VPCs.
20026
20050
  *
20027
20051
  * @remarks
20028
- * The **DescribeVpcs** operation may return the **Throttling.DeepPageSkip** error code during frequent deep paging operations. Reduce the query frequency or use sequential paging.
20052
+ * The **DescribeVpcs** operation may return the **Throttling.DeepPageSkip** error code during frequent deep paging or page skipping. Reduce the query frequency or use sequential paging.
20029
20053
  *
20030
20054
  * @param request - DescribeVpcsRequest
20031
20055
  * @param runtime - runtime options for this request RuntimeOptions
@@ -20119,7 +20143,7 @@ export default class Client extends OpenApi {
20119
20143
  * Queries created VPCs.
20120
20144
  *
20121
20145
  * @remarks
20122
- * The **DescribeVpcs** operation may return the **Throttling.DeepPageSkip** error code during frequent deep paging operations. Reduce the query frequency or use sequential paging.
20146
+ * The **DescribeVpcs** operation may return the **Throttling.DeepPageSkip** error code during frequent deep paging or page skipping. Reduce the query frequency or use sequential paging.
20123
20147
  *
20124
20148
  * @param request - DescribeVpcsRequest
20125
20149
  * @returns DescribeVpcsResponse
@@ -21660,11 +21684,12 @@ export default class Client extends OpenApi {
21660
21684
  * Enables an Express Connect circuit that is in the Confirmed state. After the circuit is enabled, it enters the Enabled state.
21661
21685
  *
21662
21686
  * @remarks
21663
- * When you call this operation, take note of the following items:
21664
- * - You can enable only an Express Connect circuit that is in the **Confirmed** state.
21665
- * - After the circuit is enabled, it enters the **Enabled** state.
21666
- * - **EnablePhysicalConnection** is an asynchronous operation. After you send a request, the system returns an instance ID, but the Express Connect circuit is not yet enabled. The enabling task is still running in the background. You can call [DescribePhysicalConnections](https://help.aliyun.com/document_detail/2982519.html) to query the status of the Express Connect circuit.
21667
- * - **EnablePhysicalConnection** does not support concurrent enabling of the same Express Connect circuit that is in the **Confirmed** state.
21687
+ * When you invoke this operation, note the following items:
21688
+ * - You can enable only an Express Connect circuit that is in the Confirmed state. After the circuit is enabled, it enters the Enabled state. To reach the Confirmed state, complete the following steps in sequence: call CreatePhysicalConnection to create a circuit (Initial → Allocating), wait for resource allocation to complete (Allocating → Allocated), and then call ConfirmPhysicalConnection after construction is complete (Allocated → Confirmed).
21689
+ * - A billing activation step occurs between the Confirmed and Enabled states. By default (if ByPassSp is not specified or ByPassSp is set to false), the system automatically creates a billing order in the sales and billing system when you invoke this operation. The circuit is enabled only after the order is created. To skip the billing order flow and directly enable the circuit, set ByPassSp to true. This capability is available only to whitelist accounts. For more information, see the ByPassSp parameter description.
21690
+ * - The EnablePhysicalConnection operation is asynchronous. The system returns a success response, but the Express Connect circuit is not yet fully enabled because the backend enablement task is still in progress. You can invoke DescribePhysicalConnections to query the enablement status of the Express Connect circuit.
21691
+ * - The EnablePhysicalConnection operation does not support concurrent enablement of the same Express Connect circuit that is in the Confirmed state. Concurrent invocations return an error.
21692
+ * If the Express Connect circuit is already in the Enabled state, invoking this operation again returns a success response (idempotent).
21668
21693
  *
21669
21694
  * @param request - EnablePhysicalConnectionRequest
21670
21695
  * @param runtime - runtime options for this request RuntimeOptions
@@ -21726,11 +21751,12 @@ export default class Client extends OpenApi {
21726
21751
  * Enables an Express Connect circuit that is in the Confirmed state. After the circuit is enabled, it enters the Enabled state.
21727
21752
  *
21728
21753
  * @remarks
21729
- * When you call this operation, take note of the following items:
21730
- * - You can enable only an Express Connect circuit that is in the **Confirmed** state.
21731
- * - After the circuit is enabled, it enters the **Enabled** state.
21732
- * - **EnablePhysicalConnection** is an asynchronous operation. After you send a request, the system returns an instance ID, but the Express Connect circuit is not yet enabled. The enabling task is still running in the background. You can call [DescribePhysicalConnections](https://help.aliyun.com/document_detail/2982519.html) to query the status of the Express Connect circuit.
21733
- * - **EnablePhysicalConnection** does not support concurrent enabling of the same Express Connect circuit that is in the **Confirmed** state.
21754
+ * When you invoke this operation, note the following items:
21755
+ * - You can enable only an Express Connect circuit that is in the Confirmed state. After the circuit is enabled, it enters the Enabled state. To reach the Confirmed state, complete the following steps in sequence: call CreatePhysicalConnection to create a circuit (Initial → Allocating), wait for resource allocation to complete (Allocating → Allocated), and then call ConfirmPhysicalConnection after construction is complete (Allocated → Confirmed).
21756
+ * - A billing activation step occurs between the Confirmed and Enabled states. By default (if ByPassSp is not specified or ByPassSp is set to false), the system automatically creates a billing order in the sales and billing system when you invoke this operation. The circuit is enabled only after the order is created. To skip the billing order flow and directly enable the circuit, set ByPassSp to true. This capability is available only to whitelist accounts. For more information, see the ByPassSp parameter description.
21757
+ * - The EnablePhysicalConnection operation is asynchronous. The system returns a success response, but the Express Connect circuit is not yet fully enabled because the backend enablement task is still in progress. You can invoke DescribePhysicalConnections to query the enablement status of the Express Connect circuit.
21758
+ * - The EnablePhysicalConnection operation does not support concurrent enablement of the same Express Connect circuit that is in the Confirmed state. Concurrent invocations return an error.
21759
+ * If the Express Connect circuit is already in the Enabled state, invoking this operation again returns a success response (idempotent).
21734
21760
  *
21735
21761
  * @param request - EnablePhysicalConnectionRequest
21736
21762
  * @returns EnablePhysicalConnectionResponse
@@ -22099,7 +22125,7 @@ export default class Client extends OpenApi {
22099
22125
  * Queries the information about a single NAT gateway instance.
22100
22126
  *
22101
22127
  * @remarks
22102
- * This operation queries the information about a single Internet NAT gateway or VPC NAT gateway. The term "NAT gateway" in this topic refers to both types without distinction.
22128
+ * This operation queries the information about a single Internet NAT gateway or VPC NAT gateway. The term "NAT gateway" in this topic does not distinguish between the two types.
22103
22129
  *
22104
22130
  * @param request - GetNatGatewayAttributeRequest
22105
22131
  * @param runtime - runtime options for this request RuntimeOptions
@@ -22157,7 +22183,7 @@ export default class Client extends OpenApi {
22157
22183
  * Queries the information about a single NAT gateway instance.
22158
22184
  *
22159
22185
  * @remarks
22160
- * This operation queries the information about a single Internet NAT gateway or VPC NAT gateway. The term "NAT gateway" in this topic refers to both types without distinction.
22186
+ * This operation queries the information about a single Internet NAT gateway or VPC NAT gateway. The term "NAT gateway" in this topic does not distinguish between the two types.
22161
22187
  *
22162
22188
  * @param request - GetNatGatewayAttributeRequest
22163
22189
  * @returns GetNatGatewayAttributeResponse
@@ -22919,7 +22945,18 @@ export default class Client extends OpenApi {
22919
22945
  * Invokes the GrantInstanceToVbr operation to grant authorization of a VPC-connected instance to a VBR instance for cross-account VBR uplink scenarios.
22920
22946
  *
22921
22947
  * @remarks
22922
- * When creating a cross-account VBR uplink connection, you must grant authorization of the VPC-connected instance to the VBR instance.
22948
+ * This operation is used for cross-account scenarios. Before calling this operation, ensure that the following resources are ready:
22949
+ * **Account A (VPC owner, the caller of this operation):**
22950
+ * - A VPC has been created and is in the Available state (CreateVpc).
22951
+ * **Account B (VBR owner, the account specified by VbrOwnerUid):** When GrantType=Specify, the VBRs specified in VbrInstanceIds must already be created. Creating a VBR depends on the complete Express Connect circuit lifecycle:
22952
+ * 1. Call CreatePhysicalConnection to create an Express Connect circuit.
22953
+ * 2. Apply for a Letter of Authorization (LOA) and complete the construction (ApplyPhysicalConnectionLOA → CompletePhysicalConnectionLOA). The Express Connect circuit enters the Confirmed state.
22954
+ * 3. Call EnablePhysicalConnection to enable the Express Connect circuit (the circuit must be in the Confirmed state).
22955
+ * 4. Call CreateVirtualBorderRouter to create a VBR (the Express Connect circuit must be in the Enabled state. Otherwise, the error InvalidPhysicalConnectionId.NotEnabled is returned).
22956
+ * After the preceding preparations are complete, Account A calls this operation to grant the VPC to the VBR of Account B:
22957
+ * - GrantType=All: Grants authorization to all VBRs under Account B (only the validity of VbrOwnerUid is verified. The VBRs do not need to be created yet).
22958
+ * - GrantType=Specify: Grants authorization to specified VBRs. The instances in VbrInstanceIds must already exist in the region specified by VbrRegionNo under the account specified by VbrOwnerUid. Otherwise, the error Instance.NotExist is returned.
22959
+ * Note: VbrOwnerUid cannot be the same as the caller\\"s account. Otherwise, the error Parameter.Illegal is returned.
22923
22960
  *
22924
22961
  * @param tmpReq - GrantInstanceToVbrRequest
22925
22962
  * @param runtime - runtime options for this request RuntimeOptions
@@ -22979,7 +23016,18 @@ export default class Client extends OpenApi {
22979
23016
  * Invokes the GrantInstanceToVbr operation to grant authorization of a VPC-connected instance to a VBR instance for cross-account VBR uplink scenarios.
22980
23017
  *
22981
23018
  * @remarks
22982
- * When creating a cross-account VBR uplink connection, you must grant authorization of the VPC-connected instance to the VBR instance.
23019
+ * This operation is used for cross-account scenarios. Before calling this operation, ensure that the following resources are ready:
23020
+ * **Account A (VPC owner, the caller of this operation):**
23021
+ * - A VPC has been created and is in the Available state (CreateVpc).
23022
+ * **Account B (VBR owner, the account specified by VbrOwnerUid):** When GrantType=Specify, the VBRs specified in VbrInstanceIds must already be created. Creating a VBR depends on the complete Express Connect circuit lifecycle:
23023
+ * 1. Call CreatePhysicalConnection to create an Express Connect circuit.
23024
+ * 2. Apply for a Letter of Authorization (LOA) and complete the construction (ApplyPhysicalConnectionLOA → CompletePhysicalConnectionLOA). The Express Connect circuit enters the Confirmed state.
23025
+ * 3. Call EnablePhysicalConnection to enable the Express Connect circuit (the circuit must be in the Confirmed state).
23026
+ * 4. Call CreateVirtualBorderRouter to create a VBR (the Express Connect circuit must be in the Enabled state. Otherwise, the error InvalidPhysicalConnectionId.NotEnabled is returned).
23027
+ * After the preceding preparations are complete, Account A calls this operation to grant the VPC to the VBR of Account B:
23028
+ * - GrantType=All: Grants authorization to all VBRs under Account B (only the validity of VbrOwnerUid is verified. The VBRs do not need to be created yet).
23029
+ * - GrantType=Specify: Grants authorization to specified VBRs. The instances in VbrInstanceIds must already exist in the region specified by VbrRegionNo under the account specified by VbrOwnerUid. Otherwise, the error Instance.NotExist is returned.
23030
+ * Note: VbrOwnerUid cannot be the same as the caller\\"s account. Otherwise, the error Parameter.Illegal is returned.
22983
23031
  *
22984
23032
  * @param request - GrantInstanceToVbrRequest
22985
23033
  * @returns GrantInstanceToVbrResponse
@@ -24735,7 +24783,7 @@ export default class Client extends OpenApi {
24735
24783
  }
24736
24784
 
24737
24785
  /**
24738
- * Queries information about shared Express Connect circuits by calling the ListVirtualPhysicalConnections operation.
24786
+ * Queries information about shared Express Connect circuits.
24739
24787
  *
24740
24788
  * @param request - ListVirtualPhysicalConnectionsRequest
24741
24789
  * @param runtime - runtime options for this request RuntimeOptions
@@ -24810,7 +24858,7 @@ export default class Client extends OpenApi {
24810
24858
  }
24811
24859
 
24812
24860
  /**
24813
- * Queries information about shared Express Connect circuits by calling the ListVirtualPhysicalConnections operation.
24861
+ * Queries information about shared Express Connect circuits.
24814
24862
  *
24815
24863
  * @param request - ListVirtualPhysicalConnectionsRequest
24816
24864
  * @returns ListVirtualPhysicalConnectionsResponse
@@ -27909,13 +27957,13 @@ export default class Client extends OpenApi {
27909
27957
  }
27910
27958
 
27911
27959
  /**
27912
- * Modifies the configuration of an Express Connect circuit.
27960
+ * Modifies the configurations of an Express Connect circuit.
27913
27961
  *
27914
27962
  * @remarks
27915
27963
  * When you call this operation, note the following items:
27916
27964
  * - You can modify the specifications and redundant circuit ID only for Express Connect circuits in the **Initial**, **Enabled**, or **Rejected** state.
27917
27965
  * - You cannot modify Express Connect circuits in the **Canceled**, **Allocating**, **AllocationFailed**, or **Terminated** state.
27918
- * - An Express Connect circuit in the **Rejected** state enters the **Initial** state after it is modified.
27966
+ * - After an Express Connect circuit in the **Rejected** state is modified, it enters the **Initial** state.
27919
27967
  *
27920
27968
  * @param request - ModifyPhysicalConnectionAttributeRequest
27921
27969
  * @param runtime - runtime options for this request RuntimeOptions
@@ -28010,13 +28058,13 @@ export default class Client extends OpenApi {
28010
28058
  }
28011
28059
 
28012
28060
  /**
28013
- * Modifies the configuration of an Express Connect circuit.
28061
+ * Modifies the configurations of an Express Connect circuit.
28014
28062
  *
28015
28063
  * @remarks
28016
28064
  * When you call this operation, note the following items:
28017
28065
  * - You can modify the specifications and redundant circuit ID only for Express Connect circuits in the **Initial**, **Enabled**, or **Rejected** state.
28018
28066
  * - You cannot modify Express Connect circuits in the **Canceled**, **Allocating**, **AllocationFailed**, or **Terminated** state.
28019
- * - An Express Connect circuit in the **Rejected** state enters the **Initial** state after it is modified.
28067
+ * - After an Express Connect circuit in the **Rejected** state is modified, it enters the **Initial** state.
28020
28068
  *
28021
28069
  * @param request - ModifyPhysicalConnectionAttributeRequest
28022
28070
  * @returns ModifyPhysicalConnectionAttributeResponse
@@ -28878,6 +28926,10 @@ export default class Client extends OpenApi {
28878
28926
  query["Ipv6CidrBlock"] = request.ipv6CidrBlock;
28879
28927
  }
28880
28928
 
28929
+ if (!$dara.isNull(request.ipv6CidrMask)) {
28930
+ query["Ipv6CidrMask"] = request.ipv6CidrMask;
28931
+ }
28932
+
28881
28933
  if (!$dara.isNull(request.ownerAccount)) {
28882
28934
  query["OwnerAccount"] = request.ownerAccount;
28883
28935
  }
@@ -29374,6 +29426,68 @@ export default class Client extends OpenApi {
29374
29426
  return await this.modifyVpcAttributeWithOptions(request, runtime);
29375
29427
  }
29376
29428
 
29429
+ /**
29430
+ * Modifies the primary or secondary CIDR block of a VPC.
29431
+ *
29432
+ * @param request - ModifyVpcCidrBlockRequest
29433
+ * @param runtime - runtime options for this request RuntimeOptions
29434
+ * @returns ModifyVpcCidrBlockResponse
29435
+ */
29436
+ async modifyVpcCidrBlockWithOptions(request: $_model.ModifyVpcCidrBlockRequest, runtime: $dara.RuntimeOptions): Promise<$_model.ModifyVpcCidrBlockResponse> {
29437
+ request.validate();
29438
+ let query = { };
29439
+ if (!$dara.isNull(request.clientToken)) {
29440
+ query["ClientToken"] = request.clientToken;
29441
+ }
29442
+
29443
+ if (!$dara.isNull(request.dryRun)) {
29444
+ query["DryRun"] = request.dryRun;
29445
+ }
29446
+
29447
+ if (!$dara.isNull(request.originalCidrBlock)) {
29448
+ query["OriginalCidrBlock"] = request.originalCidrBlock;
29449
+ }
29450
+
29451
+ if (!$dara.isNull(request.regionId)) {
29452
+ query["RegionId"] = request.regionId;
29453
+ }
29454
+
29455
+ if (!$dara.isNull(request.targetCidrBlock)) {
29456
+ query["TargetCidrBlock"] = request.targetCidrBlock;
29457
+ }
29458
+
29459
+ if (!$dara.isNull(request.vpcId)) {
29460
+ query["VpcId"] = request.vpcId;
29461
+ }
29462
+
29463
+ let req = new $OpenApiUtil.OpenApiRequest({
29464
+ query: OpenApiUtil.query(query),
29465
+ });
29466
+ let params = new $OpenApiUtil.Params({
29467
+ action: "ModifyVpcCidrBlock",
29468
+ version: "2016-04-28",
29469
+ protocol: "HTTPS",
29470
+ pathname: "/",
29471
+ method: "POST",
29472
+ authType: "AK",
29473
+ style: "RPC",
29474
+ reqBodyType: "formData",
29475
+ bodyType: "json",
29476
+ });
29477
+ return $dara.cast<$_model.ModifyVpcCidrBlockResponse>(await this.callApi(params, req, runtime), new $_model.ModifyVpcCidrBlockResponse({}));
29478
+ }
29479
+
29480
+ /**
29481
+ * Modifies the primary or secondary CIDR block of a VPC.
29482
+ *
29483
+ * @param request - ModifyVpcCidrBlockRequest
29484
+ * @returns ModifyVpcCidrBlockResponse
29485
+ */
29486
+ async modifyVpcCidrBlock(request: $_model.ModifyVpcCidrBlockRequest): Promise<$_model.ModifyVpcCidrBlockResponse> {
29487
+ let runtime = new $dara.RuntimeOptions({ });
29488
+ return await this.modifyVpcCidrBlockWithOptions(request, runtime);
29489
+ }
29490
+
29377
29491
  /**
29378
29492
  * Modifies the configuration of a prefix list.
29379
29493
  *
@@ -30296,7 +30410,7 @@ export default class Client extends OpenApi {
30296
30410
  * Modifies the resource group to which a cloud resource belongs.
30297
30411
  *
30298
30412
  * @remarks
30299
- * The **ChangeResourceGroup** operation does not support concurrent modifications to the resource group of Express Connect circuit resources within the same Express Connect circuit instance.
30413
+ * The **ChangeResourceGroup** operation does not support concurrent modifications of the resource group for Express Connect circuit resources within the same Express Connect circuit instance.
30300
30414
  *
30301
30415
  * @param request - MoveResourceGroupRequest
30302
30416
  * @param runtime - runtime options for this request RuntimeOptions
@@ -30358,7 +30472,7 @@ export default class Client extends OpenApi {
30358
30472
  * Modifies the resource group to which a cloud resource belongs.
30359
30473
  *
30360
30474
  * @remarks
30361
- * The **ChangeResourceGroup** operation does not support concurrent modifications to the resource group of Express Connect circuit resources within the same Express Connect circuit instance.
30475
+ * The **ChangeResourceGroup** operation does not support concurrent modifications of the resource group for Express Connect circuit resources within the same Express Connect circuit instance.
30362
30476
  *
30363
30477
  * @param request - MoveResourceGroupRequest
30364
30478
  * @returns MoveResourceGroupResponse
@@ -31019,16 +31133,16 @@ export default class Client extends OpenApi {
31019
31133
  }
31020
31134
 
31021
31135
  /**
31022
- * Releases a specified Elastic IP Address (EIP).
31136
+ * Releases a specified elastic IP address (EIP).
31023
31137
  *
31024
31138
  * @remarks
31025
- * Before you invoke this operation, take note of the following items:
31026
- * - Before releasing an EIP, make sure the following conditions are met:
31139
+ * Before you invoke this operation, take note of the following information:
31140
+ * - Before you release an EIP, make sure that the following conditions are met:
31027
31141
  * - Only EIPs in the **Available** state can be released.
31028
31142
  * - Only EIPs that use the pay-as-you-go billing method can be released. Subscription EIPs cannot be released.
31029
- * - The **ReleaseEipAddress** operation is asynchronous. After you send a request, the system returns a request ID, but the EIP instance has not been released yet. The release node is still running in the background. You can invoke [DescribeEipAddresses](https://help.aliyun.com/document_detail/120193.html) to query the status of the EIP instance:
31030
- * - If the EIP instance is in the **Releasing** state, the EIP instance is being released. In this state, you can only execute query operations.
31031
- * - If the EIP instance cannot be found, the EIP instance has been released.
31143
+ * - The **ReleaseEipAddress** operation is asynchronous. After you send a request, the system returns a request ID. However, the EIP instance is not immediately released because the release node is still running in the background. You can invoke [DescribeEipAddresses](https://help.aliyun.com/document_detail/120193.html) to query the status of the EIP instance:
31144
+ * - If the EIP instance is in the **Releasing** state, the EIP instance is being released. In this state, you can only execute query operations and cannot execute other operations.
31145
+ * - If the EIP instance cannot be found, the EIP instance is released.
31032
31146
  * - The **ReleaseEipAddress** operation does not support concurrent release of the same EIP instance.
31033
31147
  *
31034
31148
  * @param request - ReleaseEipAddressRequest
@@ -31080,16 +31194,16 @@ export default class Client extends OpenApi {
31080
31194
  }
31081
31195
 
31082
31196
  /**
31083
- * Releases a specified Elastic IP Address (EIP).
31197
+ * Releases a specified elastic IP address (EIP).
31084
31198
  *
31085
31199
  * @remarks
31086
- * Before you invoke this operation, take note of the following items:
31087
- * - Before releasing an EIP, make sure the following conditions are met:
31200
+ * Before you invoke this operation, take note of the following information:
31201
+ * - Before you release an EIP, make sure that the following conditions are met:
31088
31202
  * - Only EIPs in the **Available** state can be released.
31089
31203
  * - Only EIPs that use the pay-as-you-go billing method can be released. Subscription EIPs cannot be released.
31090
- * - The **ReleaseEipAddress** operation is asynchronous. After you send a request, the system returns a request ID, but the EIP instance has not been released yet. The release node is still running in the background. You can invoke [DescribeEipAddresses](https://help.aliyun.com/document_detail/120193.html) to query the status of the EIP instance:
31091
- * - If the EIP instance is in the **Releasing** state, the EIP instance is being released. In this state, you can only execute query operations.
31092
- * - If the EIP instance cannot be found, the EIP instance has been released.
31204
+ * - The **ReleaseEipAddress** operation is asynchronous. After you send a request, the system returns a request ID. However, the EIP instance is not immediately released because the release node is still running in the background. You can invoke [DescribeEipAddresses](https://help.aliyun.com/document_detail/120193.html) to query the status of the EIP instance:
31205
+ * - If the EIP instance is in the **Releasing** state, the EIP instance is being released. In this state, you can only execute query operations and cannot execute other operations.
31206
+ * - If the EIP instance cannot be found, the EIP instance is released.
31093
31207
  * - The **ReleaseEipAddress** operation does not support concurrent release of the same EIP instance.
31094
31208
  *
31095
31209
  * @param request - ReleaseEipAddressRequest
@@ -33243,10 +33357,10 @@ export default class Client extends OpenApi {
33243
33357
  }
33244
33358
 
33245
33359
  /**
33246
- * Calls the UnassociateVpcCidrBlock operation to delete a secondary CIDR block from a VPC.
33360
+ * Invokes UnassociateVpcCidrBlock to delete a secondary CIDR block from a VPC.
33247
33361
  *
33248
33362
  * @remarks
33249
- * - Before you delete a secondary CIDR block from a VPC, delete the vSwitches created with the secondary CIDR block. For more information, see [DeleteVSwitch](https://help.aliyun.com/document_detail/35746.html).
33363
+ * - Before deleting a secondary CIDR block from a VPC, delete the vSwitches that are created with the secondary CIDR block. For more information, see [DeleteVSwitch](https://help.aliyun.com/document_detail/35746.html).
33250
33364
  * - The **UnassociateVpcCidrBlock** operation does not support concurrently deleting secondary CIDR blocks from the same VPC.
33251
33365
  *
33252
33366
  * @param request - UnassociateVpcCidrBlockRequest
@@ -33310,10 +33424,10 @@ export default class Client extends OpenApi {
33310
33424
  }
33311
33425
 
33312
33426
  /**
33313
- * Calls the UnassociateVpcCidrBlock operation to delete a secondary CIDR block from a VPC.
33427
+ * Invokes UnassociateVpcCidrBlock to delete a secondary CIDR block from a VPC.
33314
33428
  *
33315
33429
  * @remarks
33316
- * - Before you delete a secondary CIDR block from a VPC, delete the vSwitches created with the secondary CIDR block. For more information, see [DeleteVSwitch](https://help.aliyun.com/document_detail/35746.html).
33430
+ * - Before deleting a secondary CIDR block from a VPC, delete the vSwitches that are created with the secondary CIDR block. For more information, see [DeleteVSwitch](https://help.aliyun.com/document_detail/35746.html).
33317
33431
  * - The **UnassociateVpcCidrBlock** operation does not support concurrently deleting secondary CIDR blocks from the same VPC.
33318
33432
  *
33319
33433
  * @param request - UnassociateVpcCidrBlockRequest