@alicloud/vpc20160428 7.2.5 → 7.3.0

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 (118) hide show
  1. package/dist/client.d.ts +193 -102
  2. package/dist/client.js +228 -98
  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 +3 -3
  21. package/dist/models/CreateVirtualPhysicalConnectionRequest.d.ts +9 -9
  22. package/dist/models/DeleteBgpNetworkRequest.d.ts +4 -4
  23. package/dist/models/DeletePublicIpAddressPoolCidrBlockRequest.d.ts +3 -3
  24. package/dist/models/DeleteRouteEntriesRequest.d.ts +2 -2
  25. package/dist/models/DeleteRouteEntriesResponseBody.d.ts +2 -2
  26. package/dist/models/DescribePhysicalConnectionLoarequest.d.ts +2 -1
  27. package/dist/models/DescribePhysicalConnectionLoarequest.js.map +1 -1
  28. package/dist/models/DescribePhysicalConnectionLoaresponseBody.d.ts +9 -6
  29. package/dist/models/DescribePhysicalConnectionLoaresponseBody.js.map +1 -1
  30. package/dist/models/DescribePhysicalConnectionsRequest.d.ts +53 -2
  31. package/dist/models/DescribePhysicalConnectionsRequest.js.map +1 -1
  32. package/dist/models/DescribeRouterInterfacesRequest.d.ts +7 -7
  33. package/dist/models/DescribeRouterInterfacesResponseBody.d.ts +1 -1
  34. package/dist/models/DescribeVbrHaResponseBody.d.ts +3 -3
  35. package/dist/models/DescribeVirtualBorderRoutersForPhysicalConnectionRequest.d.ts +3 -3
  36. package/dist/models/DescribeVpcGrantRulesToEcrRequest.d.ts +7 -7
  37. package/dist/models/DescribeVpcGrantRulesToEcrResponseBody.d.ts +8 -8
  38. package/dist/models/DescribeVpcsRequest.d.ts +6 -6
  39. package/dist/models/DescribeVpcsResponseBody.d.ts +1 -1
  40. package/dist/models/EnablePhysicalConnectionRequest.d.ts +5 -7
  41. package/dist/models/EnablePhysicalConnectionRequest.js.map +1 -1
  42. package/dist/models/GetNatGatewayAttributeRequest.d.ts +1 -1
  43. package/dist/models/GetNatGatewayAttributeResponseBody.d.ts +20 -20
  44. package/dist/models/GrantInstanceToVbrRequest.d.ts +6 -6
  45. package/dist/models/GrantInstanceToVbrShrinkRequest.d.ts +6 -6
  46. package/dist/models/ListVirtualPhysicalConnectionsRequest.d.ts +7 -7
  47. package/dist/models/ListVirtualPhysicalConnectionsResponseBody.d.ts +20 -20
  48. package/dist/models/ModifyPhysicalConnectionAttributeRequest.d.ts +10 -3
  49. package/dist/models/ModifyPhysicalConnectionAttributeRequest.js.map +1 -1
  50. package/dist/models/ModifyVpcAttributeRequest.d.ts +4 -4
  51. package/dist/models/ModifyVpcCidrBlockRequest.d.ts +78 -0
  52. package/dist/models/ModifyVpcCidrBlockRequest.js +68 -0
  53. package/dist/models/ModifyVpcCidrBlockRequest.js.map +1 -0
  54. package/dist/models/ModifyVpcCidrBlockResponse.d.ts +19 -0
  55. package/dist/models/ModifyVpcCidrBlockResponse.js +69 -0
  56. package/dist/models/ModifyVpcCidrBlockResponse.js.map +1 -0
  57. package/dist/models/ModifyVpcCidrBlockResponseBody.d.ts +21 -0
  58. package/dist/models/ModifyVpcCidrBlockResponseBody.js +58 -0
  59. package/dist/models/ModifyVpcCidrBlockResponseBody.js.map +1 -0
  60. package/dist/models/MoveResourceGroupRequest.d.ts +1 -1
  61. package/dist/models/ReleaseEipAddressRequest.d.ts +2 -2
  62. package/dist/models/UnassociateVpcCidrBlockRequest.d.ts +3 -3
  63. package/dist/models/UpdateDhcpOptionsSetAttributeRequest.d.ts +8 -8
  64. package/dist/models/UpdateIpv4gatewayAttributeRequest.d.ts +6 -6
  65. package/dist/models/model.d.ts +3 -0
  66. package/dist/models/model.js +11 -5
  67. package/dist/models/model.js.map +1 -1
  68. package/package.json +1 -1
  69. package/src/client.ts +236 -98
  70. package/src/models/ActivateRouterInterfaceRequest.ts +2 -1
  71. package/src/models/AllocateEipAddressRequest.ts +14 -14
  72. package/src/models/AssociateVpcCidrBlockRequest.ts +5 -5
  73. package/src/models/AssociateVpcCidrBlockResponseBody.ts +1 -1
  74. package/src/models/AttachDhcpOptionsSetToVpcRequest.ts +2 -2
  75. package/src/models/AttachVbrToVpconnRequest.ts +6 -4
  76. package/src/models/AttachVbrToVpconnResponseBody.ts +1 -1
  77. package/src/models/CompletePhysicalConnectionLoarequest.ts +11 -11
  78. package/src/models/ConnectRouterInterfaceRequest.ts +1 -1
  79. package/src/models/CreateCustomerGatewayRequest.ts +4 -4
  80. package/src/models/CreateCustomerGatewayResponseBody.ts +1 -1
  81. package/src/models/CreateEnhancedVpnGatewayRequest.ts +3 -3
  82. package/src/models/CreateFailoverTestJobRequest.ts +10 -10
  83. package/src/models/CreateFailoverTestJobResponseBody.ts +1 -1
  84. package/src/models/CreateRouteTargetGroupRequest.ts +3 -3
  85. package/src/models/CreateVirtualPhysicalConnectionRequest.ts +9 -9
  86. package/src/models/DeleteBgpNetworkRequest.ts +4 -4
  87. package/src/models/DeletePublicIpAddressPoolCidrBlockRequest.ts +3 -3
  88. package/src/models/DeleteRouteEntriesRequest.ts +2 -2
  89. package/src/models/DeleteRouteEntriesResponseBody.ts +2 -2
  90. package/src/models/DescribePhysicalConnectionLoarequest.ts +2 -1
  91. package/src/models/DescribePhysicalConnectionLoaresponseBody.ts +9 -6
  92. package/src/models/DescribePhysicalConnectionsRequest.ts +54 -3
  93. package/src/models/DescribeRouterInterfacesRequest.ts +7 -7
  94. package/src/models/DescribeRouterInterfacesResponseBody.ts +1 -1
  95. package/src/models/DescribeVbrHaResponseBody.ts +3 -3
  96. package/src/models/DescribeVirtualBorderRoutersForPhysicalConnectionRequest.ts +3 -3
  97. package/src/models/DescribeVpcGrantRulesToEcrRequest.ts +7 -7
  98. package/src/models/DescribeVpcGrantRulesToEcrResponseBody.ts +8 -8
  99. package/src/models/DescribeVpcsRequest.ts +6 -6
  100. package/src/models/DescribeVpcsResponseBody.ts +1 -1
  101. package/src/models/EnablePhysicalConnectionRequest.ts +5 -7
  102. package/src/models/GetNatGatewayAttributeRequest.ts +1 -1
  103. package/src/models/GetNatGatewayAttributeResponseBody.ts +20 -20
  104. package/src/models/GrantInstanceToVbrRequest.ts +6 -6
  105. package/src/models/GrantInstanceToVbrShrinkRequest.ts +6 -6
  106. package/src/models/ListVirtualPhysicalConnectionsRequest.ts +7 -7
  107. package/src/models/ListVirtualPhysicalConnectionsResponseBody.ts +20 -20
  108. package/src/models/ModifyPhysicalConnectionAttributeRequest.ts +10 -3
  109. package/src/models/ModifyVpcAttributeRequest.ts +4 -4
  110. package/src/models/ModifyVpcCidrBlockRequest.ts +101 -0
  111. package/src/models/ModifyVpcCidrBlockResponse.ts +40 -0
  112. package/src/models/ModifyVpcCidrBlockResponseBody.ts +34 -0
  113. package/src/models/MoveResourceGroupRequest.ts +1 -1
  114. package/src/models/ReleaseEipAddressRequest.ts +2 -2
  115. package/src/models/UnassociateVpcCidrBlockRequest.ts +3 -3
  116. package/src/models/UpdateDhcpOptionsSetAttributeRequest.ts +8 -8
  117. package/src/models/UpdateIpv4gatewayAttributeRequest.ts +6 -6
  118. package/src/models/model.ts +3 -0
package/dist/client.d.ts CHANGED
@@ -12,7 +12,7 @@ export default class Client extends OpenApi {
12
12
  * Activates a router interface that is in the Inactive state.
13
13
  *
14
14
  * @remarks
15
- * After you call the ActivateRouterInterface operation, the router interface enters the **Activating** state and then enters the **Active** state after activation succeeds.
15
+ * After you call the ActivateRouterInterface operation, the router interface enters the **Activating** state. After the activation succeeds, the router interface enters the **Active** state.
16
16
  * 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.
17
17
  * > You cannot activate a router interface that has an overdue payment.
18
18
  *
@@ -25,7 +25,7 @@ export default class Client extends OpenApi {
25
25
  * Activates a router interface that is in the Inactive state.
26
26
  *
27
27
  * @remarks
28
- * After you call the ActivateRouterInterface operation, the router interface enters the **Activating** state and then enters the **Active** state after activation succeeds.
28
+ * After you call the ActivateRouterInterface operation, the router interface enters the **Activating** state. After the activation succeeds, the router interface enters the **Active** state.
29
29
  * 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.
30
30
  * > You cannot activate a router interface that has an overdue payment.
31
31
  *
@@ -243,8 +243,8 @@ export default class Client extends OpenApi {
243
243
  * Applies for an elastic IP address (EIP).
244
244
  *
245
245
  * @remarks
246
- * 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).
247
- * 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.
246
+ * 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).
247
+ * 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.
248
248
  *
249
249
  * @param request - AllocateEipAddressRequest
250
250
  * @param runtime - runtime options for this request RuntimeOptions
@@ -255,8 +255,8 @@ export default class Client extends OpenApi {
255
255
  * Applies for an elastic IP address (EIP).
256
256
  *
257
257
  * @remarks
258
- * 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).
259
- * 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.
258
+ * 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).
259
+ * 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.
260
260
  *
261
261
  * @param request - AllocateEipAddressRequest
262
262
  * @returns AllocateEipAddressResponse
@@ -763,7 +763,7 @@ export default class Client extends OpenApi {
763
763
  */
764
764
  attachDhcpOptionsSetToVpc(request: $_model.AttachDhcpOptionsSetToVpcRequest): Promise<$_model.AttachDhcpOptionsSetToVpcResponse>;
765
765
  /**
766
- * Associates a Virtual Border Router (VBR) instance with shared Express Connect circuits.
766
+ * 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.
767
767
  *
768
768
  * @param request - AttachVbrToVpconnRequest
769
769
  * @param runtime - runtime options for this request RuntimeOptions
@@ -771,7 +771,7 @@ export default class Client extends OpenApi {
771
771
  */
772
772
  attachVbrToVpconnWithOptions(request: $_model.AttachVbrToVpconnRequest, runtime: $dara.RuntimeOptions): Promise<$_model.AttachVbrToVpconnResponse>;
773
773
  /**
774
- * Associates a Virtual Border Router (VBR) instance with shared Express Connect circuits.
774
+ * 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.
775
775
  *
776
776
  * @param request - AttachVbrToVpconnRequest
777
777
  * @returns AttachVbrToVpconnResponse
@@ -881,10 +881,12 @@ export default class Client extends OpenApi {
881
881
  */
882
882
  checkVpnBgpEnabled(request: $_model.CheckVpnBgpEnabledRequest): Promise<$_model.CheckVpnBgpEnabledResponse>;
883
883
  /**
884
- * Completes the construction acceptance for an Express Connect circuit.
884
+ * Calls CompletePhysicalConnectionLOA to complete the construction and backfill the completion information after the LOA is approved and the line construction is finished.
885
885
  *
886
886
  * @remarks
887
- * 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**.
887
+ * 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**.
888
+ * Complete call chain:
889
+ * 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).
888
890
  *
889
891
  * @param request - CompletePhysicalConnectionLOARequest
890
892
  * @param runtime - runtime options for this request RuntimeOptions
@@ -892,10 +894,12 @@ export default class Client extends OpenApi {
892
894
  */
893
895
  completePhysicalConnectionLOAWithOptions(request: $_model.CompletePhysicalConnectionLOARequest, runtime: $dara.RuntimeOptions): Promise<$_model.CompletePhysicalConnectionLOAResponse>;
894
896
  /**
895
- * Completes the construction acceptance for an Express Connect circuit.
897
+ * Calls CompletePhysicalConnectionLOA to complete the construction and backfill the completion information after the LOA is approved and the line construction is finished.
896
898
  *
897
899
  * @remarks
898
- * 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**.
900
+ * 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**.
901
+ * Complete call chain:
902
+ * 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).
899
903
  *
900
904
  * @param request - CompletePhysicalConnectionLOARequest
901
905
  * @returns CompletePhysicalConnectionLOAResponse
@@ -917,11 +921,11 @@ export default class Client extends OpenApi {
917
921
  */
918
922
  confirmPhysicalConnection(request: $_model.ConfirmPhysicalConnectionRequest): Promise<$_model.ConfirmPhysicalConnectionResponse>;
919
923
  /**
920
- * Initiates a connection from the requester VPC router interface to the accepter.
924
+ * Calls the ConnectRouterInterface operation to initiate a connection from the requester VPC router interface to the accepter.
921
925
  *
922
926
  * @remarks
923
- * After you call this operation, the router interface enters the **Connecting** state. After the connection is established, the router interface enters the **Active** state.
924
- * When you call this operation to create a VPC, note the following items:
927
+ * After you invoke this operation, the router interface enters the **Connecting** state and transitions to the **Active** state after the connection is established.
928
+ * When you invoke this operation to create a VPC, note the following items:
925
929
  * - Only a requester VPC router interface in the **Idle** state can initiate a connection to the accepter VPC.
926
930
  * - A maximum of one pair of interconnected router interfaces can exist between any two routers.
927
931
  * - If your account has a router interface with an overdue payment, you cannot initiate a connection.
@@ -932,11 +936,11 @@ export default class Client extends OpenApi {
932
936
  */
933
937
  connectRouterInterfaceWithOptions(request: $_model.ConnectRouterInterfaceRequest, runtime: $dara.RuntimeOptions): Promise<$_model.ConnectRouterInterfaceResponse>;
934
938
  /**
935
- * Initiates a connection from the requester VPC router interface to the accepter.
939
+ * Calls the ConnectRouterInterface operation to initiate a connection from the requester VPC router interface to the accepter.
936
940
  *
937
941
  * @remarks
938
- * After you call this operation, the router interface enters the **Connecting** state. After the connection is established, the router interface enters the **Active** state.
939
- * When you call this operation to create a VPC, note the following items:
942
+ * After you invoke this operation, the router interface enters the **Connecting** state and transitions to the **Active** state after the connection is established.
943
+ * When you invoke this operation to create a VPC, note the following items:
940
944
  * - Only a requester VPC router interface in the **Idle** state can initiate a connection to the accepter VPC.
941
945
  * - A maximum of one pair of interconnected router interfaces can exist between any two routers.
942
946
  * - If your account has a router interface with an overdue payment, you cannot initiate a connection.
@@ -1283,18 +1287,28 @@ export default class Client extends OpenApi {
1283
1287
  */
1284
1288
  createExpressConnectTrafficQosRule(request: $_model.CreateExpressConnectTrafficQosRuleRequest): Promise<$_model.CreateExpressConnectTrafficQosRuleResponse>;
1285
1289
  /**
1286
- * Creates a failover test job for Express Connect.
1287
- *
1288
- * @remarks
1289
- * You cannot create a failover test job in the following scenarios:
1290
- * - 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.
1290
+ * Calls the CreateFailoverTestJob operation to create a failover test job for Express Connect.
1291
+ *
1292
+ * @remarks
1293
+ * Resource status requirements (prerequisites)
1294
+ * - Before creating a failover test job, ensure that the test resources and their associated resources are in the following states. Otherwise, the creation fails:
1295
+ * - 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.
1296
+ * - 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.
1297
+ * - 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.
1298
+ * How to check and advance the Express Connect circuit status
1299
+ * - 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:
1300
+ * - Allocated (port reserved, pending confirmation) → Call ConfirmPhysicalConnection to confirm → Confirmed → Call EnablePhysicalConnection to activate (asynchronous; poll DescribePhysicalConnections after activation to confirm) → Enabled.
1301
+ * - Note: EnablePhysicalConnection only supports activating Express Connect circuits in the Confirmed state. If the circuit is in the Allocated state, call ConfirmPhysicalConnection first.
1302
+ * - 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.
1303
+ * The following scenarios do not support creating failover test jobs:
1304
+ * - 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.
1291
1305
  * - The Express Connect circuit instance or shared Express Connect circuit instance has not been paid for or has an overdue payment.
1292
1306
  * - The Express Connect circuit instance or shared Express Connect circuit instance is already in another running failover test job.
1293
1307
  *
1294
1308
  * - The Express Connect circuit instance has more than one shared Express Connect circuit.
1295
- * - The Express Connect circuit instance has more than one cross-account Virtual Border Router (VBR).
1309
+ * - The Express Connect circuit instance has more than one cross-account VBR.
1296
1310
  * - The shared Express Connect circuit instance is not associated with a VBR.
1297
- * - The VLAN of the shared Express Connect circuit instance is set to 0.
1311
+ * - The VLAN configuration of the shared Express Connect circuit instance is 0.
1298
1312
  *
1299
1313
  * @param request - CreateFailoverTestJobRequest
1300
1314
  * @param runtime - runtime options for this request RuntimeOptions
@@ -1302,18 +1316,28 @@ export default class Client extends OpenApi {
1302
1316
  */
1303
1317
  createFailoverTestJobWithOptions(request: $_model.CreateFailoverTestJobRequest, runtime: $dara.RuntimeOptions): Promise<$_model.CreateFailoverTestJobResponse>;
1304
1318
  /**
1305
- * Creates a failover test job for Express Connect.
1306
- *
1307
- * @remarks
1308
- * You cannot create a failover test job in the following scenarios:
1309
- * - 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.
1319
+ * Calls the CreateFailoverTestJob operation to create a failover test job for Express Connect.
1320
+ *
1321
+ * @remarks
1322
+ * Resource status requirements (prerequisites)
1323
+ * - Before creating a failover test job, ensure that the test resources and their associated resources are in the following states. Otherwise, the creation fails:
1324
+ * - 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.
1325
+ * - 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.
1326
+ * - 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.
1327
+ * How to check and advance the Express Connect circuit status
1328
+ * - 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:
1329
+ * - Allocated (port reserved, pending confirmation) → Call ConfirmPhysicalConnection to confirm → Confirmed → Call EnablePhysicalConnection to activate (asynchronous; poll DescribePhysicalConnections after activation to confirm) → Enabled.
1330
+ * - Note: EnablePhysicalConnection only supports activating Express Connect circuits in the Confirmed state. If the circuit is in the Allocated state, call ConfirmPhysicalConnection first.
1331
+ * - 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.
1332
+ * The following scenarios do not support creating failover test jobs:
1333
+ * - 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.
1310
1334
  * - The Express Connect circuit instance or shared Express Connect circuit instance has not been paid for or has an overdue payment.
1311
1335
  * - The Express Connect circuit instance or shared Express Connect circuit instance is already in another running failover test job.
1312
1336
  *
1313
1337
  * - The Express Connect circuit instance has more than one shared Express Connect circuit.
1314
- * - The Express Connect circuit instance has more than one cross-account Virtual Border Router (VBR).
1338
+ * - The Express Connect circuit instance has more than one cross-account VBR.
1315
1339
  * - The shared Express Connect circuit instance is not associated with a VBR.
1316
- * - The VLAN of the shared Express Connect circuit instance is set to 0.
1340
+ * - The VLAN configuration of the shared Express Connect circuit instance is 0.
1317
1341
  *
1318
1342
  * @param request - CreateFailoverTestJobRequest
1319
1343
  * @returns CreateFailoverTestJobResponse
@@ -2023,8 +2047,8 @@ export default class Client extends OpenApi {
2023
2047
  * - If the routing target group is in the **Pending** state, the routing target group is being created.
2024
2048
  * - If the routing target group is in the **Available**, **Unavailable**, **Switched**, or **Abnormal** state, the routing target group is created.
2025
2049
  * - **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.
2026
- * - **Primary instance**: The weight is 100. The primary instance handles all traffic under normal conditions and takes effect when health checks pass.
2027
- * - **Secondary instance**: The weight is 0. The secondary instance takes over traffic when the primary instance fails, serving as disaster recovery and backup.
2050
+ * - **Primary instance**: The weight is 100. The primary instance carries all traffic under normal conditions and takes effect when health checks are successful.
2051
+ * - **Secondary instance**: The weight is 0. The secondary instance takes over traffic after the primary instance fails and serves as disaster recovery and backup.
2028
2052
  *
2029
2053
  * @param request - CreateRouteTargetGroupRequest
2030
2054
  * @param runtime - runtime options for this request RuntimeOptions
@@ -2039,8 +2063,8 @@ export default class Client extends OpenApi {
2039
2063
  * - If the routing target group is in the **Pending** state, the routing target group is being created.
2040
2064
  * - If the routing target group is in the **Available**, **Unavailable**, **Switched**, or **Abnormal** state, the routing target group is created.
2041
2065
  * - **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.
2042
- * - **Primary instance**: The weight is 100. The primary instance handles all traffic under normal conditions and takes effect when health checks pass.
2043
- * - **Secondary instance**: The weight is 0. The secondary instance takes over traffic when the primary instance fails, serving as disaster recovery and backup.
2066
+ * - **Primary instance**: The weight is 100. The primary instance carries all traffic under normal conditions and takes effect when health checks are successful.
2067
+ * - **Secondary instance**: The weight is 0. The secondary instance takes over traffic after the primary instance fails and serves as disaster recovery and backup.
2044
2068
  *
2045
2069
  * @param request - CreateRouteTargetGroupRequest
2046
2070
  * @returns CreateRouteTargetGroupResponse
@@ -2400,7 +2424,18 @@ export default class Client extends OpenApi {
2400
2424
  * Invokes the CreateVirtualPhysicalConnection operation to create shared Express Connect circuits.
2401
2425
  *
2402
2426
  * @remarks
2403
- * 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).
2427
+ * 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).
2428
+ * Before you call this operation, make sure the following conditions are met:
2429
+ * - 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:
2430
+ * - CreatePhysicalConnection: Creates an Express Connect circuit.
2431
+ * - 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.
2432
+ * - ConfirmPhysicalConnection: Reports construction completion. The circuit must be in the Allocated state. After success, it enters the Confirmed state.
2433
+ * - 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.
2434
+ * - 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).
2435
+ * - 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.
2436
+ * - VpconnAliUid is the tenant\\"s Alibaba Cloud account (RAM users or partner accounts are not supported). Cross-site pushing is not allowed by default.
2437
+ * - The number of shared Express Connect circuits on a single Express Connect circuit has not exceeded the quota.
2438
+ * - 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.
2404
2439
  *
2405
2440
  * @param request - CreateVirtualPhysicalConnectionRequest
2406
2441
  * @param runtime - runtime options for this request RuntimeOptions
@@ -2411,7 +2446,18 @@ export default class Client extends OpenApi {
2411
2446
  * Invokes the CreateVirtualPhysicalConnection operation to create shared Express Connect circuits.
2412
2447
  *
2413
2448
  * @remarks
2414
- * 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).
2449
+ * 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).
2450
+ * Before you call this operation, make sure the following conditions are met:
2451
+ * - 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:
2452
+ * - CreatePhysicalConnection: Creates an Express Connect circuit.
2453
+ * - 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.
2454
+ * - ConfirmPhysicalConnection: Reports construction completion. The circuit must be in the Allocated state. After success, it enters the Confirmed state.
2455
+ * - 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.
2456
+ * - 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).
2457
+ * - 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.
2458
+ * - VpconnAliUid is the tenant\\"s Alibaba Cloud account (RAM users or partner accounts are not supported). Cross-site pushing is not allowed by default.
2459
+ * - The number of shared Express Connect circuits on a single Express Connect circuit has not exceeded the quota.
2460
+ * - 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.
2415
2461
  *
2416
2462
  * @param request - CreateVirtualPhysicalConnectionRequest
2417
2463
  * @returns CreateVirtualPhysicalConnectionResponse
@@ -2762,6 +2808,9 @@ export default class Client extends OpenApi {
2762
2808
  /**
2763
2809
  * Deletes an advertised Border Gateway Protocol (BGP) network.
2764
2810
  *
2811
+ * @remarks
2812
+ * 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.
2813
+ *
2765
2814
  * @param request - DeleteBgpNetworkRequest
2766
2815
  * @param runtime - runtime options for this request RuntimeOptions
2767
2816
  * @returns DeleteBgpNetworkResponse
@@ -2770,6 +2819,9 @@ export default class Client extends OpenApi {
2770
2819
  /**
2771
2820
  * Deletes an advertised Border Gateway Protocol (BGP) network.
2772
2821
  *
2822
+ * @remarks
2823
+ * 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.
2824
+ *
2773
2825
  * @param request - DeleteBgpNetworkRequest
2774
2826
  * @returns DeleteBgpNetworkResponse
2775
2827
  */
@@ -3411,11 +3463,11 @@ export default class Client extends OpenApi {
3411
3463
  *
3412
3464
  * @remarks
3413
3465
  * Before you call this operation, take note of the following items:
3414
- * - Before deleting an IP address pool, make sure that the IP addresses in the pool are not in use.
3466
+ * - Before you delete an IP address pool, make sure that the IP addresses in the pool are not in use.
3415
3467
  * - **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.
3416
3468
  * - 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.
3417
3469
  * - If the IP address pool cannot be found, the IP address pool is deleted.
3418
- * - **DeletePublicIpAddressPool** does not support concurrent deletion of the same IP address pool.
3470
+ * - You cannot call **DeletePublicIpAddressPool** to concurrently delete the same IP address pool.
3419
3471
  *
3420
3472
  * @param request - DeletePublicIpAddressPoolRequest
3421
3473
  * @param runtime - runtime options for this request RuntimeOptions
@@ -3427,11 +3479,11 @@ export default class Client extends OpenApi {
3427
3479
  *
3428
3480
  * @remarks
3429
3481
  * Before you call this operation, take note of the following items:
3430
- * - Before deleting an IP address pool, make sure that the IP addresses in the pool are not in use.
3482
+ * - Before you delete an IP address pool, make sure that the IP addresses in the pool are not in use.
3431
3483
  * - **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.
3432
3484
  * - 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.
3433
3485
  * - If the IP address pool cannot be found, the IP address pool is deleted.
3434
- * - **DeletePublicIpAddressPool** does not support concurrent deletion of the same IP address pool.
3486
+ * - You cannot call **DeletePublicIpAddressPool** to concurrently delete the same IP address pool.
3435
3487
  *
3436
3488
  * @param request - DeletePublicIpAddressPoolRequest
3437
3489
  * @returns DeletePublicIpAddressPoolResponse
@@ -3443,7 +3495,7 @@ export default class Client extends OpenApi {
3443
3495
  * @remarks
3444
3496
  * Before you call this operation, take note of the following information:
3445
3497
  * - Before deleting a CIDR block, make sure that the CIDR block is not in use.
3446
- * - **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.
3498
+ * - **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.
3447
3499
  * - If the CIDR block is in the **Deleting** state, the CIDR block is being deleted. In this state, you can only perform query operations.
3448
3500
  * - If the CIDR block cannot be found, the CIDR block is deleted.
3449
3501
  * - The **DeletePublicIpAddressPoolCidrBlock** operation does not support concurrent deletion of the same CIDR block.
@@ -3459,7 +3511,7 @@ export default class Client extends OpenApi {
3459
3511
  * @remarks
3460
3512
  * Before you call this operation, take note of the following information:
3461
3513
  * - Before deleting a CIDR block, make sure that the CIDR block is not in use.
3462
- * - **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.
3514
+ * - **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.
3463
3515
  * - If the CIDR block is in the **Deleting** state, the CIDR block is being deleted. In this state, you can only perform query operations.
3464
3516
  * - If the CIDR block cannot be found, the CIDR block is deleted.
3465
3517
  * - The **DeletePublicIpAddressPoolCidrBlock** operation does not support concurrent deletion of the same CIDR block.
@@ -3469,16 +3521,16 @@ export default class Client extends OpenApi {
3469
3521
  */
3470
3522
  deletePublicIpAddressPoolCidrBlock(request: $_model.DeletePublicIpAddressPoolCidrBlockRequest): Promise<$_model.DeletePublicIpAddressPoolCidrBlockResponse>;
3471
3523
  /**
3472
- * Batch deletes custom route entries.
3524
+ * Calls DeleteRouteEntries to batch delete custom route entries.
3473
3525
  *
3474
3526
  * @remarks
3475
3527
  * When you call this operation to delete routing entries, note the following items:
3476
3528
  * - Only routing entries in the **Available** state can be deleted.
3477
- * - Routing entries cannot be deleted if the VPC to which the route table belongs is creating or deleting a vSwitch or routing entries.
3478
- * - 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:
3479
- * - If the custom route entry is in the **Deleting** state, the custom route entry is being deleted.
3480
- * - If the specified custom route entry cannot be found, the custom route entry is deleted.
3481
- * - The **DeleteRouteEntries** operation does not support concurrent batch deletion of routing entries from route tables in the same VPC.
3529
+ * - Routing entries cannot be deleted if the VPC that contains the route table is creating or deleting a vSwitch or routing entry.
3530
+ * - 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:
3531
+ * - If the routing entry is in the **Deleting** state, the routing entry is being deleted.
3532
+ * - If the specified routing entry cannot be found, the routing entry is deleted.
3533
+ * - The **DeleteRouteEntries** operation does not support concurrent batch deletion of routing entries in route tables within the same VPC.
3482
3534
  *
3483
3535
  * @param request - DeleteRouteEntriesRequest
3484
3536
  * @param runtime - runtime options for this request RuntimeOptions
@@ -3486,16 +3538,16 @@ export default class Client extends OpenApi {
3486
3538
  */
3487
3539
  deleteRouteEntriesWithOptions(request: $_model.DeleteRouteEntriesRequest, runtime: $dara.RuntimeOptions): Promise<$_model.DeleteRouteEntriesResponse>;
3488
3540
  /**
3489
- * Batch deletes custom route entries.
3541
+ * Calls DeleteRouteEntries to batch delete custom route entries.
3490
3542
  *
3491
3543
  * @remarks
3492
3544
  * When you call this operation to delete routing entries, note the following items:
3493
3545
  * - Only routing entries in the **Available** state can be deleted.
3494
- * - Routing entries cannot be deleted if the VPC to which the route table belongs is creating or deleting a vSwitch or routing entries.
3495
- * - 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:
3496
- * - If the custom route entry is in the **Deleting** state, the custom route entry is being deleted.
3497
- * - If the specified custom route entry cannot be found, the custom route entry is deleted.
3498
- * - The **DeleteRouteEntries** operation does not support concurrent batch deletion of routing entries from route tables in the same VPC.
3546
+ * - Routing entries cannot be deleted if the VPC that contains the route table is creating or deleting a vSwitch or routing entry.
3547
+ * - 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:
3548
+ * - If the routing entry is in the **Deleting** state, the routing entry is being deleted.
3549
+ * - If the specified routing entry cannot be found, the routing entry is deleted.
3550
+ * - The **DeleteRouteEntries** operation does not support concurrent batch deletion of routing entries in route tables within the same VPC.
3499
3551
  *
3500
3552
  * @param request - DeleteRouteEntriesRequest
3501
3553
  * @returns DeleteRouteEntriesResponse
@@ -4751,7 +4803,7 @@ export default class Client extends OpenApi {
4751
4803
  * Queries information about Express Connect circuits in a specified region.
4752
4804
  *
4753
4805
  * @remarks
4754
- * 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.
4806
+ * 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.
4755
4807
  *
4756
4808
  * @param request - DescribePhysicalConnectionsRequest
4757
4809
  * @param runtime - runtime options for this request RuntimeOptions
@@ -4762,7 +4814,7 @@ export default class Client extends OpenApi {
4762
4814
  * Queries information about Express Connect circuits in a specified region.
4763
4815
  *
4764
4816
  * @remarks
4765
- * 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.
4817
+ * 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.
4766
4818
  *
4767
4819
  * @param request - DescribePhysicalConnectionsRequest
4768
4820
  * @returns DescribePhysicalConnectionsResponse
@@ -4875,7 +4927,7 @@ export default class Client extends OpenApi {
4875
4927
  */
4876
4928
  describeRouterInterfaceAttribute(request: $_model.DescribeRouterInterfaceAttributeRequest): Promise<$_model.DescribeRouterInterfaceAttributeResponse>;
4877
4929
  /**
4878
- * Queries router interfaces in a specified region by calling the DescribeRouterInterfaces operation.
4930
+ * Queries router interfaces in a specified region.
4879
4931
  *
4880
4932
  * @param request - DescribeRouterInterfacesRequest
4881
4933
  * @param runtime - runtime options for this request RuntimeOptions
@@ -4883,7 +4935,7 @@ export default class Client extends OpenApi {
4883
4935
  */
4884
4936
  describeRouterInterfacesWithOptions(request: $_model.DescribeRouterInterfacesRequest, runtime: $dara.RuntimeOptions): Promise<$_model.DescribeRouterInterfacesResponse>;
4885
4937
  /**
4886
- * Queries router interfaces in a specified region by calling the DescribeRouterInterfaces operation.
4938
+ * Queries router interfaces in a specified region.
4887
4939
  *
4888
4940
  * @param request - DescribeRouterInterfacesRequest
4889
4941
  * @returns DescribeRouterInterfacesResponse
@@ -5195,7 +5247,7 @@ export default class Client extends OpenApi {
5195
5247
  * Queries created VPCs.
5196
5248
  *
5197
5249
  * @remarks
5198
- * The **DescribeVpcs** operation may return the **Throttling.DeepPageSkip** error code during frequent deep paging operations. Reduce the query frequency or use sequential paging.
5250
+ * 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.
5199
5251
  *
5200
5252
  * @param request - DescribeVpcsRequest
5201
5253
  * @param runtime - runtime options for this request RuntimeOptions
@@ -5206,7 +5258,7 @@ export default class Client extends OpenApi {
5206
5258
  * Queries created VPCs.
5207
5259
  *
5208
5260
  * @remarks
5209
- * The **DescribeVpcs** operation may return the **Throttling.DeepPageSkip** error code during frequent deep paging operations. Reduce the query frequency or use sequential paging.
5261
+ * 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.
5210
5262
  *
5211
5263
  * @param request - DescribeVpcsRequest
5212
5264
  * @returns DescribeVpcsResponse
@@ -5583,11 +5635,12 @@ export default class Client extends OpenApi {
5583
5635
  * Enables an Express Connect circuit that is in the Confirmed state. After the circuit is enabled, it enters the Enabled state.
5584
5636
  *
5585
5637
  * @remarks
5586
- * When you call this operation, take note of the following items:
5587
- * - You can enable only an Express Connect circuit that is in the **Confirmed** state.
5588
- * - After the circuit is enabled, it enters the **Enabled** state.
5589
- * - **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.
5590
- * - **EnablePhysicalConnection** does not support concurrent enabling of the same Express Connect circuit that is in the **Confirmed** state.
5638
+ * When you invoke this operation, note the following items:
5639
+ * - 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).
5640
+ * - 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.
5641
+ * - 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.
5642
+ * - 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.
5643
+ * If the Express Connect circuit is already in the Enabled state, invoking this operation again returns a success response (idempotent).
5591
5644
  *
5592
5645
  * @param request - EnablePhysicalConnectionRequest
5593
5646
  * @param runtime - runtime options for this request RuntimeOptions
@@ -5598,11 +5651,12 @@ export default class Client extends OpenApi {
5598
5651
  * Enables an Express Connect circuit that is in the Confirmed state. After the circuit is enabled, it enters the Enabled state.
5599
5652
  *
5600
5653
  * @remarks
5601
- * When you call this operation, take note of the following items:
5602
- * - You can enable only an Express Connect circuit that is in the **Confirmed** state.
5603
- * - After the circuit is enabled, it enters the **Enabled** state.
5604
- * - **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.
5605
- * - **EnablePhysicalConnection** does not support concurrent enabling of the same Express Connect circuit that is in the **Confirmed** state.
5654
+ * When you invoke this operation, note the following items:
5655
+ * - 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).
5656
+ * - 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.
5657
+ * - 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.
5658
+ * - 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.
5659
+ * If the Express Connect circuit is already in the Enabled state, invoking this operation again returns a success response (idempotent).
5606
5660
  *
5607
5661
  * @param request - EnablePhysicalConnectionRequest
5608
5662
  * @returns EnablePhysicalConnectionResponse
@@ -5703,7 +5757,7 @@ export default class Client extends OpenApi {
5703
5757
  * Queries the information about a single NAT gateway instance.
5704
5758
  *
5705
5759
  * @remarks
5706
- * 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.
5760
+ * 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.
5707
5761
  *
5708
5762
  * @param request - GetNatGatewayAttributeRequest
5709
5763
  * @param runtime - runtime options for this request RuntimeOptions
@@ -5714,7 +5768,7 @@ export default class Client extends OpenApi {
5714
5768
  * Queries the information about a single NAT gateway instance.
5715
5769
  *
5716
5770
  * @remarks
5717
- * 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.
5771
+ * 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.
5718
5772
  *
5719
5773
  * @param request - GetNatGatewayAttributeRequest
5720
5774
  * @returns GetNatGatewayAttributeResponse
@@ -5919,7 +5973,18 @@ export default class Client extends OpenApi {
5919
5973
  * Invokes the GrantInstanceToVbr operation to grant authorization of a VPC-connected instance to a VBR instance for cross-account VBR uplink scenarios.
5920
5974
  *
5921
5975
  * @remarks
5922
- * When creating a cross-account VBR uplink connection, you must grant authorization of the VPC-connected instance to the VBR instance.
5976
+ * This operation is used for cross-account scenarios. Before calling this operation, ensure that the following resources are ready:
5977
+ * **Account A (VPC owner, the caller of this operation):**
5978
+ * - A VPC has been created and is in the Available state (CreateVpc).
5979
+ * **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:
5980
+ * 1. Call CreatePhysicalConnection to create an Express Connect circuit.
5981
+ * 2. Apply for a Letter of Authorization (LOA) and complete the construction (ApplyPhysicalConnectionLOA → CompletePhysicalConnectionLOA). The Express Connect circuit enters the Confirmed state.
5982
+ * 3. Call EnablePhysicalConnection to enable the Express Connect circuit (the circuit must be in the Confirmed state).
5983
+ * 4. Call CreateVirtualBorderRouter to create a VBR (the Express Connect circuit must be in the Enabled state. Otherwise, the error InvalidPhysicalConnectionId.NotEnabled is returned).
5984
+ * After the preceding preparations are complete, Account A calls this operation to grant the VPC to the VBR of Account B:
5985
+ * - 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).
5986
+ * - 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.
5987
+ * Note: VbrOwnerUid cannot be the same as the caller\\"s account. Otherwise, the error Parameter.Illegal is returned.
5923
5988
  *
5924
5989
  * @param tmpReq - GrantInstanceToVbrRequest
5925
5990
  * @param runtime - runtime options for this request RuntimeOptions
@@ -5930,7 +5995,18 @@ export default class Client extends OpenApi {
5930
5995
  * Invokes the GrantInstanceToVbr operation to grant authorization of a VPC-connected instance to a VBR instance for cross-account VBR uplink scenarios.
5931
5996
  *
5932
5997
  * @remarks
5933
- * When creating a cross-account VBR uplink connection, you must grant authorization of the VPC-connected instance to the VBR instance.
5998
+ * This operation is used for cross-account scenarios. Before calling this operation, ensure that the following resources are ready:
5999
+ * **Account A (VPC owner, the caller of this operation):**
6000
+ * - A VPC has been created and is in the Available state (CreateVpc).
6001
+ * **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:
6002
+ * 1. Call CreatePhysicalConnection to create an Express Connect circuit.
6003
+ * 2. Apply for a Letter of Authorization (LOA) and complete the construction (ApplyPhysicalConnectionLOA → CompletePhysicalConnectionLOA). The Express Connect circuit enters the Confirmed state.
6004
+ * 3. Call EnablePhysicalConnection to enable the Express Connect circuit (the circuit must be in the Confirmed state).
6005
+ * 4. Call CreateVirtualBorderRouter to create a VBR (the Express Connect circuit must be in the Enabled state. Otherwise, the error InvalidPhysicalConnectionId.NotEnabled is returned).
6006
+ * After the preceding preparations are complete, Account A calls this operation to grant the VPC to the VBR of Account B:
6007
+ * - 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).
6008
+ * - 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.
6009
+ * Note: VbrOwnerUid cannot be the same as the caller\\"s account. Otherwise, the error Parameter.Illegal is returned.
5934
6010
  *
5935
6011
  * @param request - GrantInstanceToVbrRequest
5936
6012
  * @returns GrantInstanceToVbrResponse
@@ -6300,7 +6376,7 @@ export default class Client extends OpenApi {
6300
6376
  */
6301
6377
  listVSwitchCidrReservations(request: $_model.ListVSwitchCidrReservationsRequest): Promise<$_model.ListVSwitchCidrReservationsResponse>;
6302
6378
  /**
6303
- * Queries information about shared Express Connect circuits by calling the ListVirtualPhysicalConnections operation.
6379
+ * Queries information about shared Express Connect circuits.
6304
6380
  *
6305
6381
  * @param request - ListVirtualPhysicalConnectionsRequest
6306
6382
  * @param runtime - runtime options for this request RuntimeOptions
@@ -6308,7 +6384,7 @@ export default class Client extends OpenApi {
6308
6384
  */
6309
6385
  listVirtualPhysicalConnectionsWithOptions(request: $_model.ListVirtualPhysicalConnectionsRequest, runtime: $dara.RuntimeOptions): Promise<$_model.ListVirtualPhysicalConnectionsResponse>;
6310
6386
  /**
6311
- * Queries information about shared Express Connect circuits by calling the ListVirtualPhysicalConnections operation.
6387
+ * Queries information about shared Express Connect circuits.
6312
6388
  *
6313
6389
  * @param request - ListVirtualPhysicalConnectionsRequest
6314
6390
  * @returns ListVirtualPhysicalConnectionsResponse
@@ -7031,13 +7107,13 @@ export default class Client extends OpenApi {
7031
7107
  */
7032
7108
  modifyNetworkAclAttributes(request: $_model.ModifyNetworkAclAttributesRequest): Promise<$_model.ModifyNetworkAclAttributesResponse>;
7033
7109
  /**
7034
- * Modifies the configuration of an Express Connect circuit.
7110
+ * Modifies the configurations of an Express Connect circuit.
7035
7111
  *
7036
7112
  * @remarks
7037
7113
  * When you call this operation, note the following items:
7038
7114
  * - You can modify the specifications and redundant circuit ID only for Express Connect circuits in the **Initial**, **Enabled**, or **Rejected** state.
7039
7115
  * - You cannot modify Express Connect circuits in the **Canceled**, **Allocating**, **AllocationFailed**, or **Terminated** state.
7040
- * - An Express Connect circuit in the **Rejected** state enters the **Initial** state after it is modified.
7116
+ * - After an Express Connect circuit in the **Rejected** state is modified, it enters the **Initial** state.
7041
7117
  *
7042
7118
  * @param request - ModifyPhysicalConnectionAttributeRequest
7043
7119
  * @param runtime - runtime options for this request RuntimeOptions
@@ -7045,13 +7121,13 @@ export default class Client extends OpenApi {
7045
7121
  */
7046
7122
  modifyPhysicalConnectionAttributeWithOptions(request: $_model.ModifyPhysicalConnectionAttributeRequest, runtime: $dara.RuntimeOptions): Promise<$_model.ModifyPhysicalConnectionAttributeResponse>;
7047
7123
  /**
7048
- * Modifies the configuration of an Express Connect circuit.
7124
+ * Modifies the configurations of an Express Connect circuit.
7049
7125
  *
7050
7126
  * @remarks
7051
7127
  * When you call this operation, note the following items:
7052
7128
  * - You can modify the specifications and redundant circuit ID only for Express Connect circuits in the **Initial**, **Enabled**, or **Rejected** state.
7053
7129
  * - You cannot modify Express Connect circuits in the **Canceled**, **Allocating**, **AllocationFailed**, or **Terminated** state.
7054
- * - An Express Connect circuit in the **Rejected** state enters the **Initial** state after it is modified.
7130
+ * - After an Express Connect circuit in the **Rejected** state is modified, it enters the **Initial** state.
7055
7131
  *
7056
7132
  * @param request - ModifyPhysicalConnectionAttributeRequest
7057
7133
  * @returns ModifyPhysicalConnectionAttributeResponse
@@ -7387,6 +7463,21 @@ export default class Client extends OpenApi {
7387
7463
  * @returns ModifyVpcAttributeResponse
7388
7464
  */
7389
7465
  modifyVpcAttribute(request: $_model.ModifyVpcAttributeRequest): Promise<$_model.ModifyVpcAttributeResponse>;
7466
+ /**
7467
+ * Modifies the primary or secondary CIDR block of a VPC.
7468
+ *
7469
+ * @param request - ModifyVpcCidrBlockRequest
7470
+ * @param runtime - runtime options for this request RuntimeOptions
7471
+ * @returns ModifyVpcCidrBlockResponse
7472
+ */
7473
+ modifyVpcCidrBlockWithOptions(request: $_model.ModifyVpcCidrBlockRequest, runtime: $dara.RuntimeOptions): Promise<$_model.ModifyVpcCidrBlockResponse>;
7474
+ /**
7475
+ * Modifies the primary or secondary CIDR block of a VPC.
7476
+ *
7477
+ * @param request - ModifyVpcCidrBlockRequest
7478
+ * @returns ModifyVpcCidrBlockResponse
7479
+ */
7480
+ modifyVpcCidrBlock(request: $_model.ModifyVpcCidrBlockRequest): Promise<$_model.ModifyVpcCidrBlockResponse>;
7390
7481
  /**
7391
7482
  * Modifies the configuration of a prefix list.
7392
7483
  *
@@ -7635,7 +7726,7 @@ export default class Client extends OpenApi {
7635
7726
  * Modifies the resource group to which a cloud resource belongs.
7636
7727
  *
7637
7728
  * @remarks
7638
- * The **ChangeResourceGroup** operation does not support concurrent modifications to the resource group of Express Connect circuit resources within the same Express Connect circuit instance.
7729
+ * The **ChangeResourceGroup** operation does not support concurrent modifications of the resource group for Express Connect circuit resources within the same Express Connect circuit instance.
7639
7730
  *
7640
7731
  * @param request - MoveResourceGroupRequest
7641
7732
  * @param runtime - runtime options for this request RuntimeOptions
@@ -7646,7 +7737,7 @@ export default class Client extends OpenApi {
7646
7737
  * Modifies the resource group to which a cloud resource belongs.
7647
7738
  *
7648
7739
  * @remarks
7649
- * The **ChangeResourceGroup** operation does not support concurrent modifications to the resource group of Express Connect circuit resources within the same Express Connect circuit instance.
7740
+ * The **ChangeResourceGroup** operation does not support concurrent modifications of the resource group for Express Connect circuit resources within the same Express Connect circuit instance.
7650
7741
  *
7651
7742
  * @param request - MoveResourceGroupRequest
7652
7743
  * @returns MoveResourceGroupResponse
@@ -7832,16 +7923,16 @@ export default class Client extends OpenApi {
7832
7923
  */
7833
7924
  recoverVirtualBorderRouter(request: $_model.RecoverVirtualBorderRouterRequest): Promise<$_model.RecoverVirtualBorderRouterResponse>;
7834
7925
  /**
7835
- * Releases a specified Elastic IP Address (EIP).
7926
+ * Releases a specified elastic IP address (EIP).
7836
7927
  *
7837
7928
  * @remarks
7838
- * Before you invoke this operation, take note of the following items:
7839
- * - Before releasing an EIP, make sure the following conditions are met:
7929
+ * Before you invoke this operation, take note of the following information:
7930
+ * - Before you release an EIP, make sure that the following conditions are met:
7840
7931
  * - Only EIPs in the **Available** state can be released.
7841
7932
  * - Only EIPs that use the pay-as-you-go billing method can be released. Subscription EIPs cannot be released.
7842
- * - 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:
7843
- * - If the EIP instance is in the **Releasing** state, the EIP instance is being released. In this state, you can only execute query operations.
7844
- * - If the EIP instance cannot be found, the EIP instance has been released.
7933
+ * - 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:
7934
+ * - 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.
7935
+ * - If the EIP instance cannot be found, the EIP instance is released.
7845
7936
  * - The **ReleaseEipAddress** operation does not support concurrent release of the same EIP instance.
7846
7937
  *
7847
7938
  * @param request - ReleaseEipAddressRequest
@@ -7850,16 +7941,16 @@ export default class Client extends OpenApi {
7850
7941
  */
7851
7942
  releaseEipAddressWithOptions(request: $_model.ReleaseEipAddressRequest, runtime: $dara.RuntimeOptions): Promise<$_model.ReleaseEipAddressResponse>;
7852
7943
  /**
7853
- * Releases a specified Elastic IP Address (EIP).
7944
+ * Releases a specified elastic IP address (EIP).
7854
7945
  *
7855
7946
  * @remarks
7856
- * Before you invoke this operation, take note of the following items:
7857
- * - Before releasing an EIP, make sure the following conditions are met:
7947
+ * Before you invoke this operation, take note of the following information:
7948
+ * - Before you release an EIP, make sure that the following conditions are met:
7858
7949
  * - Only EIPs in the **Available** state can be released.
7859
7950
  * - Only EIPs that use the pay-as-you-go billing method can be released. Subscription EIPs cannot be released.
7860
- * - 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:
7861
- * - If the EIP instance is in the **Releasing** state, the EIP instance is being released. In this state, you can only execute query operations.
7862
- * - If the EIP instance cannot be found, the EIP instance has been released.
7951
+ * - 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:
7952
+ * - 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.
7953
+ * - If the EIP instance cannot be found, the EIP instance is released.
7863
7954
  * - The **ReleaseEipAddress** operation does not support concurrent release of the same EIP instance.
7864
7955
  *
7865
7956
  * @param request - ReleaseEipAddressRequest
@@ -8478,10 +8569,10 @@ export default class Client extends OpenApi {
8478
8569
  */
8479
8570
  unassociateRouteTable(request: $_model.UnassociateRouteTableRequest): Promise<$_model.UnassociateRouteTableResponse>;
8480
8571
  /**
8481
- * Calls the UnassociateVpcCidrBlock operation to delete a secondary CIDR block from a VPC.
8572
+ * Invokes UnassociateVpcCidrBlock to delete a secondary CIDR block from a VPC.
8482
8573
  *
8483
8574
  * @remarks
8484
- * - 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).
8575
+ * - 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).
8485
8576
  * - The **UnassociateVpcCidrBlock** operation does not support concurrently deleting secondary CIDR blocks from the same VPC.
8486
8577
  *
8487
8578
  * @param request - UnassociateVpcCidrBlockRequest
@@ -8490,10 +8581,10 @@ export default class Client extends OpenApi {
8490
8581
  */
8491
8582
  unassociateVpcCidrBlockWithOptions(request: $_model.UnassociateVpcCidrBlockRequest, runtime: $dara.RuntimeOptions): Promise<$_model.UnassociateVpcCidrBlockResponse>;
8492
8583
  /**
8493
- * Calls the UnassociateVpcCidrBlock operation to delete a secondary CIDR block from a VPC.
8584
+ * Invokes UnassociateVpcCidrBlock to delete a secondary CIDR block from a VPC.
8494
8585
  *
8495
8586
  * @remarks
8496
- * - 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).
8587
+ * - 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).
8497
8588
  * - The **UnassociateVpcCidrBlock** operation does not support concurrently deleting secondary CIDR blocks from the same VPC.
8498
8589
  *
8499
8590
  * @param request - UnassociateVpcCidrBlockRequest
@@ -8516,7 +8607,7 @@ export default class Client extends OpenApi {
8516
8607
  */
8517
8608
  untagResourcesForExpressConnect(request: $_model.UntagResourcesForExpressConnectRequest): Promise<$_model.UntagResourcesForExpressConnectResponse>;
8518
8609
  /**
8519
- * Modifies the configuration of a DHCP options set by calling the UpdateDhcpOptionsSetAttribute operation.
8610
+ * Modifies the configuration of a DHCP options set.
8520
8611
  *
8521
8612
  * @param request - UpdateDhcpOptionsSetAttributeRequest
8522
8613
  * @param runtime - runtime options for this request RuntimeOptions
@@ -8524,7 +8615,7 @@ export default class Client extends OpenApi {
8524
8615
  */
8525
8616
  updateDhcpOptionsSetAttributeWithOptions(request: $_model.UpdateDhcpOptionsSetAttributeRequest, runtime: $dara.RuntimeOptions): Promise<$_model.UpdateDhcpOptionsSetAttributeResponse>;
8526
8617
  /**
8527
- * Modifies the configuration of a DHCP options set by calling the UpdateDhcpOptionsSetAttribute operation.
8618
+ * Modifies the configuration of a DHCP options set.
8528
8619
  *
8529
8620
  * @param request - UpdateDhcpOptionsSetAttributeRequest
8530
8621
  * @returns UpdateDhcpOptionsSetAttributeResponse