@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.
- package/dist/client.d.ts +193 -102
- package/dist/client.js +228 -98
- package/dist/client.js.map +1 -1
- package/dist/models/ActivateRouterInterfaceRequest.d.ts +1 -0
- package/dist/models/ActivateRouterInterfaceRequest.js.map +1 -1
- package/dist/models/AllocateEipAddressRequest.d.ts +14 -14
- package/dist/models/AssociateVpcCidrBlockRequest.d.ts +5 -5
- package/dist/models/AssociateVpcCidrBlockResponseBody.d.ts +1 -1
- package/dist/models/AttachDhcpOptionsSetToVpcRequest.d.ts +2 -2
- package/dist/models/AttachVbrToVpconnRequest.d.ts +6 -4
- package/dist/models/AttachVbrToVpconnRequest.js.map +1 -1
- package/dist/models/AttachVbrToVpconnResponseBody.d.ts +1 -1
- package/dist/models/CompletePhysicalConnectionLoarequest.d.ts +11 -11
- package/dist/models/ConnectRouterInterfaceRequest.d.ts +1 -1
- package/dist/models/CreateCustomerGatewayRequest.d.ts +4 -4
- package/dist/models/CreateCustomerGatewayResponseBody.d.ts +1 -1
- package/dist/models/CreateEnhancedVpnGatewayRequest.d.ts +3 -3
- package/dist/models/CreateFailoverTestJobRequest.d.ts +10 -10
- package/dist/models/CreateFailoverTestJobResponseBody.d.ts +1 -1
- package/dist/models/CreateRouteTargetGroupRequest.d.ts +3 -3
- package/dist/models/CreateVirtualPhysicalConnectionRequest.d.ts +9 -9
- package/dist/models/DeleteBgpNetworkRequest.d.ts +4 -4
- package/dist/models/DeletePublicIpAddressPoolCidrBlockRequest.d.ts +3 -3
- package/dist/models/DeleteRouteEntriesRequest.d.ts +2 -2
- package/dist/models/DeleteRouteEntriesResponseBody.d.ts +2 -2
- package/dist/models/DescribePhysicalConnectionLoarequest.d.ts +2 -1
- package/dist/models/DescribePhysicalConnectionLoarequest.js.map +1 -1
- package/dist/models/DescribePhysicalConnectionLoaresponseBody.d.ts +9 -6
- package/dist/models/DescribePhysicalConnectionLoaresponseBody.js.map +1 -1
- package/dist/models/DescribePhysicalConnectionsRequest.d.ts +53 -2
- package/dist/models/DescribePhysicalConnectionsRequest.js.map +1 -1
- package/dist/models/DescribeRouterInterfacesRequest.d.ts +7 -7
- package/dist/models/DescribeRouterInterfacesResponseBody.d.ts +1 -1
- package/dist/models/DescribeVbrHaResponseBody.d.ts +3 -3
- package/dist/models/DescribeVirtualBorderRoutersForPhysicalConnectionRequest.d.ts +3 -3
- package/dist/models/DescribeVpcGrantRulesToEcrRequest.d.ts +7 -7
- package/dist/models/DescribeVpcGrantRulesToEcrResponseBody.d.ts +8 -8
- package/dist/models/DescribeVpcsRequest.d.ts +6 -6
- package/dist/models/DescribeVpcsResponseBody.d.ts +1 -1
- package/dist/models/EnablePhysicalConnectionRequest.d.ts +5 -7
- package/dist/models/EnablePhysicalConnectionRequest.js.map +1 -1
- package/dist/models/GetNatGatewayAttributeRequest.d.ts +1 -1
- package/dist/models/GetNatGatewayAttributeResponseBody.d.ts +20 -20
- package/dist/models/GrantInstanceToVbrRequest.d.ts +6 -6
- package/dist/models/GrantInstanceToVbrShrinkRequest.d.ts +6 -6
- package/dist/models/ListVirtualPhysicalConnectionsRequest.d.ts +7 -7
- package/dist/models/ListVirtualPhysicalConnectionsResponseBody.d.ts +20 -20
- package/dist/models/ModifyPhysicalConnectionAttributeRequest.d.ts +10 -3
- package/dist/models/ModifyPhysicalConnectionAttributeRequest.js.map +1 -1
- package/dist/models/ModifyVpcAttributeRequest.d.ts +4 -4
- package/dist/models/ModifyVpcCidrBlockRequest.d.ts +78 -0
- package/dist/models/ModifyVpcCidrBlockRequest.js +68 -0
- package/dist/models/ModifyVpcCidrBlockRequest.js.map +1 -0
- package/dist/models/ModifyVpcCidrBlockResponse.d.ts +19 -0
- package/dist/models/ModifyVpcCidrBlockResponse.js +69 -0
- package/dist/models/ModifyVpcCidrBlockResponse.js.map +1 -0
- package/dist/models/ModifyVpcCidrBlockResponseBody.d.ts +21 -0
- package/dist/models/ModifyVpcCidrBlockResponseBody.js +58 -0
- package/dist/models/ModifyVpcCidrBlockResponseBody.js.map +1 -0
- package/dist/models/MoveResourceGroupRequest.d.ts +1 -1
- package/dist/models/ReleaseEipAddressRequest.d.ts +2 -2
- package/dist/models/UnassociateVpcCidrBlockRequest.d.ts +3 -3
- package/dist/models/UpdateDhcpOptionsSetAttributeRequest.d.ts +8 -8
- package/dist/models/UpdateIpv4gatewayAttributeRequest.d.ts +6 -6
- package/dist/models/model.d.ts +3 -0
- package/dist/models/model.js +11 -5
- package/dist/models/model.js.map +1 -1
- package/package.json +1 -1
- package/src/client.ts +236 -98
- package/src/models/ActivateRouterInterfaceRequest.ts +2 -1
- package/src/models/AllocateEipAddressRequest.ts +14 -14
- package/src/models/AssociateVpcCidrBlockRequest.ts +5 -5
- package/src/models/AssociateVpcCidrBlockResponseBody.ts +1 -1
- package/src/models/AttachDhcpOptionsSetToVpcRequest.ts +2 -2
- package/src/models/AttachVbrToVpconnRequest.ts +6 -4
- package/src/models/AttachVbrToVpconnResponseBody.ts +1 -1
- package/src/models/CompletePhysicalConnectionLoarequest.ts +11 -11
- package/src/models/ConnectRouterInterfaceRequest.ts +1 -1
- package/src/models/CreateCustomerGatewayRequest.ts +4 -4
- package/src/models/CreateCustomerGatewayResponseBody.ts +1 -1
- package/src/models/CreateEnhancedVpnGatewayRequest.ts +3 -3
- package/src/models/CreateFailoverTestJobRequest.ts +10 -10
- package/src/models/CreateFailoverTestJobResponseBody.ts +1 -1
- package/src/models/CreateRouteTargetGroupRequest.ts +3 -3
- package/src/models/CreateVirtualPhysicalConnectionRequest.ts +9 -9
- package/src/models/DeleteBgpNetworkRequest.ts +4 -4
- package/src/models/DeletePublicIpAddressPoolCidrBlockRequest.ts +3 -3
- package/src/models/DeleteRouteEntriesRequest.ts +2 -2
- package/src/models/DeleteRouteEntriesResponseBody.ts +2 -2
- package/src/models/DescribePhysicalConnectionLoarequest.ts +2 -1
- package/src/models/DescribePhysicalConnectionLoaresponseBody.ts +9 -6
- package/src/models/DescribePhysicalConnectionsRequest.ts +54 -3
- package/src/models/DescribeRouterInterfacesRequest.ts +7 -7
- package/src/models/DescribeRouterInterfacesResponseBody.ts +1 -1
- package/src/models/DescribeVbrHaResponseBody.ts +3 -3
- package/src/models/DescribeVirtualBorderRoutersForPhysicalConnectionRequest.ts +3 -3
- package/src/models/DescribeVpcGrantRulesToEcrRequest.ts +7 -7
- package/src/models/DescribeVpcGrantRulesToEcrResponseBody.ts +8 -8
- package/src/models/DescribeVpcsRequest.ts +6 -6
- package/src/models/DescribeVpcsResponseBody.ts +1 -1
- package/src/models/EnablePhysicalConnectionRequest.ts +5 -7
- package/src/models/GetNatGatewayAttributeRequest.ts +1 -1
- package/src/models/GetNatGatewayAttributeResponseBody.ts +20 -20
- package/src/models/GrantInstanceToVbrRequest.ts +6 -6
- package/src/models/GrantInstanceToVbrShrinkRequest.ts +6 -6
- package/src/models/ListVirtualPhysicalConnectionsRequest.ts +7 -7
- package/src/models/ListVirtualPhysicalConnectionsResponseBody.ts +20 -20
- package/src/models/ModifyPhysicalConnectionAttributeRequest.ts +10 -3
- package/src/models/ModifyVpcAttributeRequest.ts +4 -4
- package/src/models/ModifyVpcCidrBlockRequest.ts +101 -0
- package/src/models/ModifyVpcCidrBlockResponse.ts +40 -0
- package/src/models/ModifyVpcCidrBlockResponseBody.ts +34 -0
- package/src/models/MoveResourceGroupRequest.ts +1 -1
- package/src/models/ReleaseEipAddressRequest.ts +2 -2
- package/src/models/UnassociateVpcCidrBlockRequest.ts +3 -3
- package/src/models/UpdateDhcpOptionsSetAttributeRequest.ts +8 -8
- package/src/models/UpdateIpv4gatewayAttributeRequest.ts +6 -6
- package/src/models/model.ts +3 -0
package/src/client.ts
CHANGED
|
@@ -107,7 +107,7 @@ export default class Client extends OpenApi {
|
|
|
107
107
|
* Activates a router interface that is in the Inactive state.
|
|
108
108
|
*
|
|
109
109
|
* @remarks
|
|
110
|
-
* After you call the ActivateRouterInterface operation, the router interface enters the **Activating** state
|
|
110
|
+
* 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
111
|
* 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
112
|
* > You cannot activate a router interface that has an overdue payment.
|
|
113
113
|
*
|
|
@@ -159,7 +159,7 @@ export default class Client extends OpenApi {
|
|
|
159
159
|
* Activates a router interface that is in the Inactive state.
|
|
160
160
|
*
|
|
161
161
|
* @remarks
|
|
162
|
-
* After you call the ActivateRouterInterface operation, the router interface enters the **Activating** state
|
|
162
|
+
* 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
163
|
* 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
164
|
* > You cannot activate a router interface that has an overdue payment.
|
|
165
165
|
*
|
|
@@ -838,8 +838,8 @@ export default class Client extends OpenApi {
|
|
|
838
838
|
* Applies for an elastic IP address (EIP).
|
|
839
839
|
*
|
|
840
840
|
* @remarks
|
|
841
|
-
*
|
|
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.
|
|
841
|
+
* 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).
|
|
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. IGMP and SCTP are not supported.
|
|
843
843
|
*
|
|
844
844
|
* @param request - AllocateEipAddressRequest
|
|
845
845
|
* @param runtime - runtime options for this request RuntimeOptions
|
|
@@ -965,8 +965,8 @@ export default class Client extends OpenApi {
|
|
|
965
965
|
* Applies for an elastic IP address (EIP).
|
|
966
966
|
*
|
|
967
967
|
* @remarks
|
|
968
|
-
*
|
|
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.
|
|
968
|
+
* 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).
|
|
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. IGMP and SCTP are not supported.
|
|
970
970
|
*
|
|
971
971
|
* @param request - AllocateEipAddressRequest
|
|
972
972
|
* @returns AllocateEipAddressResponse
|
|
@@ -2724,7 +2724,7 @@ export default class Client extends OpenApi {
|
|
|
2724
2724
|
}
|
|
2725
2725
|
|
|
2726
2726
|
/**
|
|
2727
|
-
* Associates a Virtual Border Router (VBR) instance with shared Express Connect circuits.
|
|
2727
|
+
* 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
2728
|
*
|
|
2729
2729
|
* @param request - AttachVbrToVpconnRequest
|
|
2730
2730
|
* @param runtime - runtime options for this request RuntimeOptions
|
|
@@ -2771,7 +2771,7 @@ export default class Client extends OpenApi {
|
|
|
2771
2771
|
}
|
|
2772
2772
|
|
|
2773
2773
|
/**
|
|
2774
|
-
* Associates a Virtual Border Router (VBR) instance with shared Express Connect circuits.
|
|
2774
|
+
* 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
2775
|
*
|
|
2776
2776
|
* @param request - AttachVbrToVpconnRequest
|
|
2777
2777
|
* @returns AttachVbrToVpconnResponse
|
|
@@ -3124,10 +3124,12 @@ export default class Client extends OpenApi {
|
|
|
3124
3124
|
}
|
|
3125
3125
|
|
|
3126
3126
|
/**
|
|
3127
|
-
*
|
|
3127
|
+
* Calls CompletePhysicalConnectionLOA to complete the construction and backfill the completion information after the LOA is approved and the line construction is finished.
|
|
3128
3128
|
*
|
|
3129
3129
|
* @remarks
|
|
3130
|
-
*
|
|
3130
|
+
* 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**.
|
|
3131
|
+
* Complete call chain:
|
|
3132
|
+
* 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
3133
|
*
|
|
3132
3134
|
* @param request - CompletePhysicalConnectionLOARequest
|
|
3133
3135
|
* @param runtime - runtime options for this request RuntimeOptions
|
|
@@ -3206,10 +3208,12 @@ export default class Client extends OpenApi {
|
|
|
3206
3208
|
}
|
|
3207
3209
|
|
|
3208
3210
|
/**
|
|
3209
|
-
*
|
|
3211
|
+
* Calls CompletePhysicalConnectionLOA to complete the construction and backfill the completion information after the LOA is approved and the line construction is finished.
|
|
3210
3212
|
*
|
|
3211
3213
|
* @remarks
|
|
3212
|
-
*
|
|
3214
|
+
* 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**.
|
|
3215
|
+
* Complete call chain:
|
|
3216
|
+
* 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
3217
|
*
|
|
3214
3218
|
* @param request - CompletePhysicalConnectionLOARequest
|
|
3215
3219
|
* @returns CompletePhysicalConnectionLOAResponse
|
|
@@ -3286,11 +3290,11 @@ export default class Client extends OpenApi {
|
|
|
3286
3290
|
}
|
|
3287
3291
|
|
|
3288
3292
|
/**
|
|
3289
|
-
*
|
|
3293
|
+
* Calls the ConnectRouterInterface operation to initiate a connection from the requester VPC router interface to the accepter.
|
|
3290
3294
|
*
|
|
3291
3295
|
* @remarks
|
|
3292
|
-
* After you
|
|
3293
|
-
* When you
|
|
3296
|
+
* After you invoke this operation, the router interface enters the **Connecting** state and transitions to the **Active** state after the connection is established.
|
|
3297
|
+
* When you invoke this operation to create a VPC, note the following items:
|
|
3294
3298
|
* - Only a requester VPC router interface in the **Idle** state can initiate a connection to the accepter VPC.
|
|
3295
3299
|
* - A maximum of one pair of interconnected router interfaces can exist between any two routers.
|
|
3296
3300
|
* - If your account has a router interface with an overdue payment, you cannot initiate a connection.
|
|
@@ -3340,11 +3344,11 @@ export default class Client extends OpenApi {
|
|
|
3340
3344
|
}
|
|
3341
3345
|
|
|
3342
3346
|
/**
|
|
3343
|
-
*
|
|
3347
|
+
* Calls the ConnectRouterInterface operation to initiate a connection from the requester VPC router interface to the accepter.
|
|
3344
3348
|
*
|
|
3345
3349
|
* @remarks
|
|
3346
|
-
* After you
|
|
3347
|
-
* When you
|
|
3350
|
+
* After you invoke this operation, the router interface enters the **Connecting** state and transitions to the **Active** state after the connection is established.
|
|
3351
|
+
* When you invoke this operation to create a VPC, note the following items:
|
|
3348
3352
|
* - Only a requester VPC router interface in the **Idle** state can initiate a connection to the accepter VPC.
|
|
3349
3353
|
* - A maximum of one pair of interconnected router interfaces can exist between any two routers.
|
|
3350
3354
|
* - If your account has a router interface with an overdue payment, you cannot initiate a connection.
|
|
@@ -4666,18 +4670,28 @@ export default class Client extends OpenApi {
|
|
|
4666
4670
|
}
|
|
4667
4671
|
|
|
4668
4672
|
/**
|
|
4669
|
-
*
|
|
4673
|
+
* Calls the CreateFailoverTestJob operation to create a failover test job for Express Connect.
|
|
4670
4674
|
*
|
|
4671
4675
|
* @remarks
|
|
4672
|
-
*
|
|
4673
|
-
* -
|
|
4676
|
+
* Resource status requirements (prerequisites)
|
|
4677
|
+
* - Before creating a failover test job, ensure that the test resources and their associated resources are in the following states. Otherwise, the creation fails:
|
|
4678
|
+
* - 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.
|
|
4679
|
+
* - 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.
|
|
4680
|
+
* - 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.
|
|
4681
|
+
* How to check and advance the Express Connect circuit status
|
|
4682
|
+
* - 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:
|
|
4683
|
+
* - Allocated (port reserved, pending confirmation) → Call ConfirmPhysicalConnection to confirm → Confirmed → Call EnablePhysicalConnection to activate (asynchronous; poll DescribePhysicalConnections after activation to confirm) → Enabled.
|
|
4684
|
+
* - Note: EnablePhysicalConnection only supports activating Express Connect circuits in the Confirmed state. If the circuit is in the Allocated state, call ConfirmPhysicalConnection first.
|
|
4685
|
+
* - 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.
|
|
4686
|
+
* The following scenarios do not support creating failover test jobs:
|
|
4687
|
+
* - 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
4688
|
* - The Express Connect circuit instance or shared Express Connect circuit instance has not been paid for or has an overdue payment.
|
|
4675
4689
|
* - The Express Connect circuit instance or shared Express Connect circuit instance is already in another running failover test job.
|
|
4676
4690
|
*
|
|
4677
4691
|
* - 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
|
|
4692
|
+
* - The Express Connect circuit instance has more than one cross-account VBR.
|
|
4679
4693
|
* - The shared Express Connect circuit instance is not associated with a VBR.
|
|
4680
|
-
* - The VLAN of the shared Express Connect circuit instance is
|
|
4694
|
+
* - The VLAN configuration of the shared Express Connect circuit instance is 0.
|
|
4681
4695
|
*
|
|
4682
4696
|
* @param request - CreateFailoverTestJobRequest
|
|
4683
4697
|
* @param runtime - runtime options for this request RuntimeOptions
|
|
@@ -4756,18 +4770,28 @@ export default class Client extends OpenApi {
|
|
|
4756
4770
|
}
|
|
4757
4771
|
|
|
4758
4772
|
/**
|
|
4759
|
-
*
|
|
4773
|
+
* Calls the CreateFailoverTestJob operation to create a failover test job for Express Connect.
|
|
4760
4774
|
*
|
|
4761
4775
|
* @remarks
|
|
4762
|
-
*
|
|
4763
|
-
* -
|
|
4776
|
+
* Resource status requirements (prerequisites)
|
|
4777
|
+
* - Before creating a failover test job, ensure that the test resources and their associated resources are in the following states. Otherwise, the creation fails:
|
|
4778
|
+
* - 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.
|
|
4779
|
+
* - 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.
|
|
4780
|
+
* - 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.
|
|
4781
|
+
* How to check and advance the Express Connect circuit status
|
|
4782
|
+
* - 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:
|
|
4783
|
+
* - Allocated (port reserved, pending confirmation) → Call ConfirmPhysicalConnection to confirm → Confirmed → Call EnablePhysicalConnection to activate (asynchronous; poll DescribePhysicalConnections after activation to confirm) → Enabled.
|
|
4784
|
+
* - Note: EnablePhysicalConnection only supports activating Express Connect circuits in the Confirmed state. If the circuit is in the Allocated state, call ConfirmPhysicalConnection first.
|
|
4785
|
+
* - 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.
|
|
4786
|
+
* The following scenarios do not support creating failover test jobs:
|
|
4787
|
+
* - 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
4788
|
* - The Express Connect circuit instance or shared Express Connect circuit instance has not been paid for or has an overdue payment.
|
|
4765
4789
|
* - The Express Connect circuit instance or shared Express Connect circuit instance is already in another running failover test job.
|
|
4766
4790
|
*
|
|
4767
4791
|
* - 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
|
|
4792
|
+
* - The Express Connect circuit instance has more than one cross-account VBR.
|
|
4769
4793
|
* - The shared Express Connect circuit instance is not associated with a VBR.
|
|
4770
|
-
* - The VLAN of the shared Express Connect circuit instance is
|
|
4794
|
+
* - The VLAN configuration of the shared Express Connect circuit instance is 0.
|
|
4771
4795
|
*
|
|
4772
4796
|
* @param request - CreateFailoverTestJobRequest
|
|
4773
4797
|
* @returns CreateFailoverTestJobResponse
|
|
@@ -7383,8 +7407,8 @@ export default class Client extends OpenApi {
|
|
|
7383
7407
|
* - If the routing target group is in the **Pending** state, the routing target group is being created.
|
|
7384
7408
|
* - If the routing target group is in the **Available**, **Unavailable**, **Switched**, or **Abnormal** state, the routing target group is created.
|
|
7385
7409
|
* - **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
|
|
7387
|
-
* - **Secondary instance**: The weight is 0. The secondary instance takes over traffic
|
|
7410
|
+
* - **Primary instance**: The weight is 100. The primary instance carries all traffic under normal conditions and takes effect when health checks are successful.
|
|
7411
|
+
* - **Secondary instance**: The weight is 0. The secondary instance takes over traffic after the primary instance fails and serves as disaster recovery and backup.
|
|
7388
7412
|
*
|
|
7389
7413
|
* @param request - CreateRouteTargetGroupRequest
|
|
7390
7414
|
* @param runtime - runtime options for this request RuntimeOptions
|
|
@@ -7454,8 +7478,8 @@ export default class Client extends OpenApi {
|
|
|
7454
7478
|
* - If the routing target group is in the **Pending** state, the routing target group is being created.
|
|
7455
7479
|
* - If the routing target group is in the **Available**, **Unavailable**, **Switched**, or **Abnormal** state, the routing target group is created.
|
|
7456
7480
|
* - **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
|
|
7458
|
-
* - **Secondary instance**: The weight is 0. The secondary instance takes over traffic
|
|
7481
|
+
* - **Primary instance**: The weight is 100. The primary instance carries all traffic under normal conditions and takes effect when health checks are successful.
|
|
7482
|
+
* - **Secondary instance**: The weight is 0. The secondary instance takes over traffic after the primary instance fails and serves as disaster recovery and backup.
|
|
7459
7483
|
*
|
|
7460
7484
|
* @param request - CreateRouteTargetGroupRequest
|
|
7461
7485
|
* @returns CreateRouteTargetGroupResponse
|
|
@@ -8851,7 +8875,18 @@ export default class Client extends OpenApi {
|
|
|
8851
8875
|
* Invokes the CreateVirtualPhysicalConnection operation to create shared Express Connect circuits.
|
|
8852
8876
|
*
|
|
8853
8877
|
* @remarks
|
|
8854
|
-
* Before
|
|
8878
|
+
* 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).
|
|
8879
|
+
* Before you call this operation, make sure the following conditions are met:
|
|
8880
|
+
* - 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:
|
|
8881
|
+
* - CreatePhysicalConnection: Creates an Express Connect circuit.
|
|
8882
|
+
* - 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.
|
|
8883
|
+
* - ConfirmPhysicalConnection: Reports construction completion. The circuit must be in the Allocated state. After success, it enters the Confirmed state.
|
|
8884
|
+
* - 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.
|
|
8885
|
+
* - 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).
|
|
8886
|
+
* - 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.
|
|
8887
|
+
* - VpconnAliUid is the tenant\\"s Alibaba Cloud account (RAM users or partner accounts are not supported). Cross-site pushing is not allowed by default.
|
|
8888
|
+
* - The number of shared Express Connect circuits on a single Express Connect circuit has not exceeded the quota.
|
|
8889
|
+
* - 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
8890
|
*
|
|
8856
8891
|
* @param request - CreateVirtualPhysicalConnectionRequest
|
|
8857
8892
|
* @param runtime - runtime options for this request RuntimeOptions
|
|
@@ -8929,7 +8964,18 @@ export default class Client extends OpenApi {
|
|
|
8929
8964
|
* Invokes the CreateVirtualPhysicalConnection operation to create shared Express Connect circuits.
|
|
8930
8965
|
*
|
|
8931
8966
|
* @remarks
|
|
8932
|
-
* Before
|
|
8967
|
+
* 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).
|
|
8968
|
+
* Before you call this operation, make sure the following conditions are met:
|
|
8969
|
+
* - 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:
|
|
8970
|
+
* - CreatePhysicalConnection: Creates an Express Connect circuit.
|
|
8971
|
+
* - 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.
|
|
8972
|
+
* - ConfirmPhysicalConnection: Reports construction completion. The circuit must be in the Allocated state. After success, it enters the Confirmed state.
|
|
8973
|
+
* - 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.
|
|
8974
|
+
* - 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).
|
|
8975
|
+
* - 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.
|
|
8976
|
+
* - VpconnAliUid is the tenant\\"s Alibaba Cloud account (RAM users or partner accounts are not supported). Cross-site pushing is not allowed by default.
|
|
8977
|
+
* - The number of shared Express Connect circuits on a single Express Connect circuit has not exceeded the quota.
|
|
8978
|
+
* - 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
8979
|
*
|
|
8934
8980
|
* @param request - CreateVirtualPhysicalConnectionRequest
|
|
8935
8981
|
* @returns CreateVirtualPhysicalConnectionResponse
|
|
@@ -10258,6 +10304,9 @@ export default class Client extends OpenApi {
|
|
|
10258
10304
|
/**
|
|
10259
10305
|
* Deletes an advertised Border Gateway Protocol (BGP) network.
|
|
10260
10306
|
*
|
|
10307
|
+
* @remarks
|
|
10308
|
+
* 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.
|
|
10309
|
+
*
|
|
10261
10310
|
* @param request - DeleteBgpNetworkRequest
|
|
10262
10311
|
* @param runtime - runtime options for this request RuntimeOptions
|
|
10263
10312
|
* @returns DeleteBgpNetworkResponse
|
|
@@ -10317,6 +10366,9 @@ export default class Client extends OpenApi {
|
|
|
10317
10366
|
/**
|
|
10318
10367
|
* Deletes an advertised Border Gateway Protocol (BGP) network.
|
|
10319
10368
|
*
|
|
10369
|
+
* @remarks
|
|
10370
|
+
* 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.
|
|
10371
|
+
*
|
|
10320
10372
|
* @param request - DeleteBgpNetworkRequest
|
|
10321
10373
|
* @returns DeleteBgpNetworkResponse
|
|
10322
10374
|
*/
|
|
@@ -12484,11 +12536,11 @@ export default class Client extends OpenApi {
|
|
|
12484
12536
|
*
|
|
12485
12537
|
* @remarks
|
|
12486
12538
|
* Before you call this operation, take note of the following items:
|
|
12487
|
-
* - Before
|
|
12539
|
+
* - Before you delete an IP address pool, make sure that the IP addresses in the pool are not in use.
|
|
12488
12540
|
* - **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
12541
|
* - 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
12542
|
* - If the IP address pool cannot be found, the IP address pool is deleted.
|
|
12491
|
-
* - **DeletePublicIpAddressPool**
|
|
12543
|
+
* - You cannot call **DeletePublicIpAddressPool** to concurrently delete the same IP address pool.
|
|
12492
12544
|
*
|
|
12493
12545
|
* @param request - DeletePublicIpAddressPoolRequest
|
|
12494
12546
|
* @param runtime - runtime options for this request RuntimeOptions
|
|
@@ -12551,11 +12603,11 @@ export default class Client extends OpenApi {
|
|
|
12551
12603
|
*
|
|
12552
12604
|
* @remarks
|
|
12553
12605
|
* Before you call this operation, take note of the following items:
|
|
12554
|
-
* - Before
|
|
12606
|
+
* - Before you delete an IP address pool, make sure that the IP addresses in the pool are not in use.
|
|
12555
12607
|
* - **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
12608
|
* - 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
12609
|
* - If the IP address pool cannot be found, the IP address pool is deleted.
|
|
12558
|
-
* - **DeletePublicIpAddressPool**
|
|
12610
|
+
* - You cannot call **DeletePublicIpAddressPool** to concurrently delete the same IP address pool.
|
|
12559
12611
|
*
|
|
12560
12612
|
* @param request - DeletePublicIpAddressPoolRequest
|
|
12561
12613
|
* @returns DeletePublicIpAddressPoolResponse
|
|
@@ -12571,7 +12623,7 @@ export default class Client extends OpenApi {
|
|
|
12571
12623
|
* @remarks
|
|
12572
12624
|
* Before you call this operation, take note of the following information:
|
|
12573
12625
|
* - 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
|
|
12626
|
+
* - **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
12627
|
* - 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
12628
|
* - If the CIDR block cannot be found, the CIDR block is deleted.
|
|
12577
12629
|
* - The **DeletePublicIpAddressPoolCidrBlock** operation does not support concurrent deletion of the same CIDR block.
|
|
@@ -12642,7 +12694,7 @@ export default class Client extends OpenApi {
|
|
|
12642
12694
|
* @remarks
|
|
12643
12695
|
* Before you call this operation, take note of the following information:
|
|
12644
12696
|
* - 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
|
|
12697
|
+
* - **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
12698
|
* - 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
12699
|
* - If the CIDR block cannot be found, the CIDR block is deleted.
|
|
12648
12700
|
* - The **DeletePublicIpAddressPoolCidrBlock** operation does not support concurrent deletion of the same CIDR block.
|
|
@@ -12656,16 +12708,16 @@ export default class Client extends OpenApi {
|
|
|
12656
12708
|
}
|
|
12657
12709
|
|
|
12658
12710
|
/**
|
|
12659
|
-
*
|
|
12711
|
+
* Calls DeleteRouteEntries to batch delete custom route entries.
|
|
12660
12712
|
*
|
|
12661
12713
|
* @remarks
|
|
12662
12714
|
* When you call this operation to delete routing entries, note the following items:
|
|
12663
12715
|
* - Only routing entries in the **Available** state can be deleted.
|
|
12664
|
-
* - Routing entries cannot be deleted if the VPC
|
|
12665
|
-
* - The **DeleteRouteEntries** operation is asynchronous. After you send a request, the system returns a request ID, but the
|
|
12666
|
-
* - If the
|
|
12667
|
-
* - If the specified
|
|
12668
|
-
* - The **DeleteRouteEntries** operation does not support concurrent batch deletion of routing entries
|
|
12716
|
+
* - Routing entries cannot be deleted if the VPC that contains the route table is creating or deleting a vSwitch or routing entry.
|
|
12717
|
+
* - 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:
|
|
12718
|
+
* - If the routing entry is in the **Deleting** state, the routing entry is being deleted.
|
|
12719
|
+
* - If the specified routing entry cannot be found, the routing entry is deleted.
|
|
12720
|
+
* - The **DeleteRouteEntries** operation does not support concurrent batch deletion of routing entries in route tables within the same VPC.
|
|
12669
12721
|
*
|
|
12670
12722
|
* @param request - DeleteRouteEntriesRequest
|
|
12671
12723
|
* @param runtime - runtime options for this request RuntimeOptions
|
|
@@ -12724,16 +12776,16 @@ export default class Client extends OpenApi {
|
|
|
12724
12776
|
}
|
|
12725
12777
|
|
|
12726
12778
|
/**
|
|
12727
|
-
*
|
|
12779
|
+
* Calls DeleteRouteEntries to batch delete custom route entries.
|
|
12728
12780
|
*
|
|
12729
12781
|
* @remarks
|
|
12730
12782
|
* When you call this operation to delete routing entries, note the following items:
|
|
12731
12783
|
* - Only routing entries in the **Available** state can be deleted.
|
|
12732
|
-
* - Routing entries cannot be deleted if the VPC
|
|
12733
|
-
* - The **DeleteRouteEntries** operation is asynchronous. After you send a request, the system returns a request ID, but the
|
|
12734
|
-
* - If the
|
|
12735
|
-
* - If the specified
|
|
12736
|
-
* - The **DeleteRouteEntries** operation does not support concurrent batch deletion of routing entries
|
|
12784
|
+
* - Routing entries cannot be deleted if the VPC that contains the route table is creating or deleting a vSwitch or routing entry.
|
|
12785
|
+
* - 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:
|
|
12786
|
+
* - If the routing entry is in the **Deleting** state, the routing entry is being deleted.
|
|
12787
|
+
* - If the specified routing entry cannot be found, the routing entry is deleted.
|
|
12788
|
+
* - The **DeleteRouteEntries** operation does not support concurrent batch deletion of routing entries in route tables within the same VPC.
|
|
12737
12789
|
*
|
|
12738
12790
|
* @param request - DeleteRouteEntriesRequest
|
|
12739
12791
|
* @returns DeleteRouteEntriesResponse
|
|
@@ -17914,7 +17966,7 @@ export default class Client extends OpenApi {
|
|
|
17914
17966
|
* Queries information about Express Connect circuits in a specified region.
|
|
17915
17967
|
*
|
|
17916
17968
|
* @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
|
|
17969
|
+
* 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
17970
|
*
|
|
17919
17971
|
* @param request - DescribePhysicalConnectionsRequest
|
|
17920
17972
|
* @param runtime - runtime options for this request RuntimeOptions
|
|
@@ -17992,7 +18044,7 @@ export default class Client extends OpenApi {
|
|
|
17992
18044
|
* Queries information about Express Connect circuits in a specified region.
|
|
17993
18045
|
*
|
|
17994
18046
|
* @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
|
|
18047
|
+
* 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
18048
|
*
|
|
17997
18049
|
* @param request - DescribePhysicalConnectionsRequest
|
|
17998
18050
|
* @returns DescribePhysicalConnectionsResponse
|
|
@@ -18516,7 +18568,7 @@ export default class Client extends OpenApi {
|
|
|
18516
18568
|
}
|
|
18517
18569
|
|
|
18518
18570
|
/**
|
|
18519
|
-
* Queries router interfaces in a specified region
|
|
18571
|
+
* Queries router interfaces in a specified region.
|
|
18520
18572
|
*
|
|
18521
18573
|
* @param request - DescribeRouterInterfacesRequest
|
|
18522
18574
|
* @param runtime - runtime options for this request RuntimeOptions
|
|
@@ -18583,7 +18635,7 @@ export default class Client extends OpenApi {
|
|
|
18583
18635
|
}
|
|
18584
18636
|
|
|
18585
18637
|
/**
|
|
18586
|
-
* Queries router interfaces in a specified region
|
|
18638
|
+
* Queries router interfaces in a specified region.
|
|
18587
18639
|
*
|
|
18588
18640
|
* @param request - DescribeRouterInterfacesRequest
|
|
18589
18641
|
* @returns DescribeRouterInterfacesResponse
|
|
@@ -20025,7 +20077,7 @@ export default class Client extends OpenApi {
|
|
|
20025
20077
|
* Queries created VPCs.
|
|
20026
20078
|
*
|
|
20027
20079
|
* @remarks
|
|
20028
|
-
* The **DescribeVpcs** operation may return the **Throttling.DeepPageSkip** error code during frequent deep paging
|
|
20080
|
+
* 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
20081
|
*
|
|
20030
20082
|
* @param request - DescribeVpcsRequest
|
|
20031
20083
|
* @param runtime - runtime options for this request RuntimeOptions
|
|
@@ -20119,7 +20171,7 @@ export default class Client extends OpenApi {
|
|
|
20119
20171
|
* Queries created VPCs.
|
|
20120
20172
|
*
|
|
20121
20173
|
* @remarks
|
|
20122
|
-
* The **DescribeVpcs** operation may return the **Throttling.DeepPageSkip** error code during frequent deep paging
|
|
20174
|
+
* 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
20175
|
*
|
|
20124
20176
|
* @param request - DescribeVpcsRequest
|
|
20125
20177
|
* @returns DescribeVpcsResponse
|
|
@@ -21660,11 +21712,12 @@ export default class Client extends OpenApi {
|
|
|
21660
21712
|
* Enables an Express Connect circuit that is in the Confirmed state. After the circuit is enabled, it enters the Enabled state.
|
|
21661
21713
|
*
|
|
21662
21714
|
* @remarks
|
|
21663
|
-
* When you
|
|
21664
|
-
* - You can enable only an Express Connect circuit that is in the
|
|
21665
|
-
* -
|
|
21666
|
-
* -
|
|
21667
|
-
* -
|
|
21715
|
+
* When you invoke this operation, note the following items:
|
|
21716
|
+
* - 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).
|
|
21717
|
+
* - 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.
|
|
21718
|
+
* - 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.
|
|
21719
|
+
* - 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.
|
|
21720
|
+
* If the Express Connect circuit is already in the Enabled state, invoking this operation again returns a success response (idempotent).
|
|
21668
21721
|
*
|
|
21669
21722
|
* @param request - EnablePhysicalConnectionRequest
|
|
21670
21723
|
* @param runtime - runtime options for this request RuntimeOptions
|
|
@@ -21726,11 +21779,12 @@ export default class Client extends OpenApi {
|
|
|
21726
21779
|
* Enables an Express Connect circuit that is in the Confirmed state. After the circuit is enabled, it enters the Enabled state.
|
|
21727
21780
|
*
|
|
21728
21781
|
* @remarks
|
|
21729
|
-
* When you
|
|
21730
|
-
* - You can enable only an Express Connect circuit that is in the
|
|
21731
|
-
* -
|
|
21732
|
-
* -
|
|
21733
|
-
* -
|
|
21782
|
+
* When you invoke this operation, note the following items:
|
|
21783
|
+
* - 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).
|
|
21784
|
+
* - 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.
|
|
21785
|
+
* - 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.
|
|
21786
|
+
* - 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.
|
|
21787
|
+
* If the Express Connect circuit is already in the Enabled state, invoking this operation again returns a success response (idempotent).
|
|
21734
21788
|
*
|
|
21735
21789
|
* @param request - EnablePhysicalConnectionRequest
|
|
21736
21790
|
* @returns EnablePhysicalConnectionResponse
|
|
@@ -22099,7 +22153,7 @@ export default class Client extends OpenApi {
|
|
|
22099
22153
|
* Queries the information about a single NAT gateway instance.
|
|
22100
22154
|
*
|
|
22101
22155
|
* @remarks
|
|
22102
|
-
* This operation queries the information about a single Internet NAT gateway or VPC NAT gateway. The term "NAT gateway" in this topic
|
|
22156
|
+
* 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
22157
|
*
|
|
22104
22158
|
* @param request - GetNatGatewayAttributeRequest
|
|
22105
22159
|
* @param runtime - runtime options for this request RuntimeOptions
|
|
@@ -22157,7 +22211,7 @@ export default class Client extends OpenApi {
|
|
|
22157
22211
|
* Queries the information about a single NAT gateway instance.
|
|
22158
22212
|
*
|
|
22159
22213
|
* @remarks
|
|
22160
|
-
* This operation queries the information about a single Internet NAT gateway or VPC NAT gateway. The term "NAT gateway" in this topic
|
|
22214
|
+
* 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
22215
|
*
|
|
22162
22216
|
* @param request - GetNatGatewayAttributeRequest
|
|
22163
22217
|
* @returns GetNatGatewayAttributeResponse
|
|
@@ -22919,7 +22973,18 @@ export default class Client extends OpenApi {
|
|
|
22919
22973
|
* Invokes the GrantInstanceToVbr operation to grant authorization of a VPC-connected instance to a VBR instance for cross-account VBR uplink scenarios.
|
|
22920
22974
|
*
|
|
22921
22975
|
* @remarks
|
|
22922
|
-
*
|
|
22976
|
+
* This operation is used for cross-account scenarios. Before calling this operation, ensure that the following resources are ready:
|
|
22977
|
+
* **Account A (VPC owner, the caller of this operation):**
|
|
22978
|
+
* - A VPC has been created and is in the Available state (CreateVpc).
|
|
22979
|
+
* **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:
|
|
22980
|
+
* 1. Call CreatePhysicalConnection to create an Express Connect circuit.
|
|
22981
|
+
* 2. Apply for a Letter of Authorization (LOA) and complete the construction (ApplyPhysicalConnectionLOA → CompletePhysicalConnectionLOA). The Express Connect circuit enters the Confirmed state.
|
|
22982
|
+
* 3. Call EnablePhysicalConnection to enable the Express Connect circuit (the circuit must be in the Confirmed state).
|
|
22983
|
+
* 4. Call CreateVirtualBorderRouter to create a VBR (the Express Connect circuit must be in the Enabled state. Otherwise, the error InvalidPhysicalConnectionId.NotEnabled is returned).
|
|
22984
|
+
* After the preceding preparations are complete, Account A calls this operation to grant the VPC to the VBR of Account B:
|
|
22985
|
+
* - 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).
|
|
22986
|
+
* - 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.
|
|
22987
|
+
* Note: VbrOwnerUid cannot be the same as the caller\\"s account. Otherwise, the error Parameter.Illegal is returned.
|
|
22923
22988
|
*
|
|
22924
22989
|
* @param tmpReq - GrantInstanceToVbrRequest
|
|
22925
22990
|
* @param runtime - runtime options for this request RuntimeOptions
|
|
@@ -22979,7 +23044,18 @@ export default class Client extends OpenApi {
|
|
|
22979
23044
|
* Invokes the GrantInstanceToVbr operation to grant authorization of a VPC-connected instance to a VBR instance for cross-account VBR uplink scenarios.
|
|
22980
23045
|
*
|
|
22981
23046
|
* @remarks
|
|
22982
|
-
*
|
|
23047
|
+
* This operation is used for cross-account scenarios. Before calling this operation, ensure that the following resources are ready:
|
|
23048
|
+
* **Account A (VPC owner, the caller of this operation):**
|
|
23049
|
+
* - A VPC has been created and is in the Available state (CreateVpc).
|
|
23050
|
+
* **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:
|
|
23051
|
+
* 1. Call CreatePhysicalConnection to create an Express Connect circuit.
|
|
23052
|
+
* 2. Apply for a Letter of Authorization (LOA) and complete the construction (ApplyPhysicalConnectionLOA → CompletePhysicalConnectionLOA). The Express Connect circuit enters the Confirmed state.
|
|
23053
|
+
* 3. Call EnablePhysicalConnection to enable the Express Connect circuit (the circuit must be in the Confirmed state).
|
|
23054
|
+
* 4. Call CreateVirtualBorderRouter to create a VBR (the Express Connect circuit must be in the Enabled state. Otherwise, the error InvalidPhysicalConnectionId.NotEnabled is returned).
|
|
23055
|
+
* After the preceding preparations are complete, Account A calls this operation to grant the VPC to the VBR of Account B:
|
|
23056
|
+
* - 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).
|
|
23057
|
+
* - 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.
|
|
23058
|
+
* Note: VbrOwnerUid cannot be the same as the caller\\"s account. Otherwise, the error Parameter.Illegal is returned.
|
|
22983
23059
|
*
|
|
22984
23060
|
* @param request - GrantInstanceToVbrRequest
|
|
22985
23061
|
* @returns GrantInstanceToVbrResponse
|
|
@@ -24735,7 +24811,7 @@ export default class Client extends OpenApi {
|
|
|
24735
24811
|
}
|
|
24736
24812
|
|
|
24737
24813
|
/**
|
|
24738
|
-
* Queries information about shared Express Connect circuits
|
|
24814
|
+
* Queries information about shared Express Connect circuits.
|
|
24739
24815
|
*
|
|
24740
24816
|
* @param request - ListVirtualPhysicalConnectionsRequest
|
|
24741
24817
|
* @param runtime - runtime options for this request RuntimeOptions
|
|
@@ -24810,7 +24886,7 @@ export default class Client extends OpenApi {
|
|
|
24810
24886
|
}
|
|
24811
24887
|
|
|
24812
24888
|
/**
|
|
24813
|
-
* Queries information about shared Express Connect circuits
|
|
24889
|
+
* Queries information about shared Express Connect circuits.
|
|
24814
24890
|
*
|
|
24815
24891
|
* @param request - ListVirtualPhysicalConnectionsRequest
|
|
24816
24892
|
* @returns ListVirtualPhysicalConnectionsResponse
|
|
@@ -27909,13 +27985,13 @@ export default class Client extends OpenApi {
|
|
|
27909
27985
|
}
|
|
27910
27986
|
|
|
27911
27987
|
/**
|
|
27912
|
-
* Modifies the
|
|
27988
|
+
* Modifies the configurations of an Express Connect circuit.
|
|
27913
27989
|
*
|
|
27914
27990
|
* @remarks
|
|
27915
27991
|
* When you call this operation, note the following items:
|
|
27916
27992
|
* - You can modify the specifications and redundant circuit ID only for Express Connect circuits in the **Initial**, **Enabled**, or **Rejected** state.
|
|
27917
27993
|
* - You cannot modify Express Connect circuits in the **Canceled**, **Allocating**, **AllocationFailed**, or **Terminated** state.
|
|
27918
|
-
* -
|
|
27994
|
+
* - After an Express Connect circuit in the **Rejected** state is modified, it enters the **Initial** state.
|
|
27919
27995
|
*
|
|
27920
27996
|
* @param request - ModifyPhysicalConnectionAttributeRequest
|
|
27921
27997
|
* @param runtime - runtime options for this request RuntimeOptions
|
|
@@ -28010,13 +28086,13 @@ export default class Client extends OpenApi {
|
|
|
28010
28086
|
}
|
|
28011
28087
|
|
|
28012
28088
|
/**
|
|
28013
|
-
* Modifies the
|
|
28089
|
+
* Modifies the configurations of an Express Connect circuit.
|
|
28014
28090
|
*
|
|
28015
28091
|
* @remarks
|
|
28016
28092
|
* When you call this operation, note the following items:
|
|
28017
28093
|
* - You can modify the specifications and redundant circuit ID only for Express Connect circuits in the **Initial**, **Enabled**, or **Rejected** state.
|
|
28018
28094
|
* - You cannot modify Express Connect circuits in the **Canceled**, **Allocating**, **AllocationFailed**, or **Terminated** state.
|
|
28019
|
-
* -
|
|
28095
|
+
* - After an Express Connect circuit in the **Rejected** state is modified, it enters the **Initial** state.
|
|
28020
28096
|
*
|
|
28021
28097
|
* @param request - ModifyPhysicalConnectionAttributeRequest
|
|
28022
28098
|
* @returns ModifyPhysicalConnectionAttributeResponse
|
|
@@ -29374,6 +29450,68 @@ export default class Client extends OpenApi {
|
|
|
29374
29450
|
return await this.modifyVpcAttributeWithOptions(request, runtime);
|
|
29375
29451
|
}
|
|
29376
29452
|
|
|
29453
|
+
/**
|
|
29454
|
+
* Modifies the primary or secondary CIDR block of a VPC.
|
|
29455
|
+
*
|
|
29456
|
+
* @param request - ModifyVpcCidrBlockRequest
|
|
29457
|
+
* @param runtime - runtime options for this request RuntimeOptions
|
|
29458
|
+
* @returns ModifyVpcCidrBlockResponse
|
|
29459
|
+
*/
|
|
29460
|
+
async modifyVpcCidrBlockWithOptions(request: $_model.ModifyVpcCidrBlockRequest, runtime: $dara.RuntimeOptions): Promise<$_model.ModifyVpcCidrBlockResponse> {
|
|
29461
|
+
request.validate();
|
|
29462
|
+
let query = { };
|
|
29463
|
+
if (!$dara.isNull(request.clientToken)) {
|
|
29464
|
+
query["ClientToken"] = request.clientToken;
|
|
29465
|
+
}
|
|
29466
|
+
|
|
29467
|
+
if (!$dara.isNull(request.dryRun)) {
|
|
29468
|
+
query["DryRun"] = request.dryRun;
|
|
29469
|
+
}
|
|
29470
|
+
|
|
29471
|
+
if (!$dara.isNull(request.originalCidrBlock)) {
|
|
29472
|
+
query["OriginalCidrBlock"] = request.originalCidrBlock;
|
|
29473
|
+
}
|
|
29474
|
+
|
|
29475
|
+
if (!$dara.isNull(request.regionId)) {
|
|
29476
|
+
query["RegionId"] = request.regionId;
|
|
29477
|
+
}
|
|
29478
|
+
|
|
29479
|
+
if (!$dara.isNull(request.targetCidrBlock)) {
|
|
29480
|
+
query["TargetCidrBlock"] = request.targetCidrBlock;
|
|
29481
|
+
}
|
|
29482
|
+
|
|
29483
|
+
if (!$dara.isNull(request.vpcId)) {
|
|
29484
|
+
query["VpcId"] = request.vpcId;
|
|
29485
|
+
}
|
|
29486
|
+
|
|
29487
|
+
let req = new $OpenApiUtil.OpenApiRequest({
|
|
29488
|
+
query: OpenApiUtil.query(query),
|
|
29489
|
+
});
|
|
29490
|
+
let params = new $OpenApiUtil.Params({
|
|
29491
|
+
action: "ModifyVpcCidrBlock",
|
|
29492
|
+
version: "2016-04-28",
|
|
29493
|
+
protocol: "HTTPS",
|
|
29494
|
+
pathname: "/",
|
|
29495
|
+
method: "POST",
|
|
29496
|
+
authType: "AK",
|
|
29497
|
+
style: "RPC",
|
|
29498
|
+
reqBodyType: "formData",
|
|
29499
|
+
bodyType: "json",
|
|
29500
|
+
});
|
|
29501
|
+
return $dara.cast<$_model.ModifyVpcCidrBlockResponse>(await this.callApi(params, req, runtime), new $_model.ModifyVpcCidrBlockResponse({}));
|
|
29502
|
+
}
|
|
29503
|
+
|
|
29504
|
+
/**
|
|
29505
|
+
* Modifies the primary or secondary CIDR block of a VPC.
|
|
29506
|
+
*
|
|
29507
|
+
* @param request - ModifyVpcCidrBlockRequest
|
|
29508
|
+
* @returns ModifyVpcCidrBlockResponse
|
|
29509
|
+
*/
|
|
29510
|
+
async modifyVpcCidrBlock(request: $_model.ModifyVpcCidrBlockRequest): Promise<$_model.ModifyVpcCidrBlockResponse> {
|
|
29511
|
+
let runtime = new $dara.RuntimeOptions({ });
|
|
29512
|
+
return await this.modifyVpcCidrBlockWithOptions(request, runtime);
|
|
29513
|
+
}
|
|
29514
|
+
|
|
29377
29515
|
/**
|
|
29378
29516
|
* Modifies the configuration of a prefix list.
|
|
29379
29517
|
*
|
|
@@ -30296,7 +30434,7 @@ export default class Client extends OpenApi {
|
|
|
30296
30434
|
* Modifies the resource group to which a cloud resource belongs.
|
|
30297
30435
|
*
|
|
30298
30436
|
* @remarks
|
|
30299
|
-
* The **ChangeResourceGroup** operation does not support concurrent modifications
|
|
30437
|
+
* 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
30438
|
*
|
|
30301
30439
|
* @param request - MoveResourceGroupRequest
|
|
30302
30440
|
* @param runtime - runtime options for this request RuntimeOptions
|
|
@@ -30358,7 +30496,7 @@ export default class Client extends OpenApi {
|
|
|
30358
30496
|
* Modifies the resource group to which a cloud resource belongs.
|
|
30359
30497
|
*
|
|
30360
30498
|
* @remarks
|
|
30361
|
-
* The **ChangeResourceGroup** operation does not support concurrent modifications
|
|
30499
|
+
* 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
30500
|
*
|
|
30363
30501
|
* @param request - MoveResourceGroupRequest
|
|
30364
30502
|
* @returns MoveResourceGroupResponse
|
|
@@ -31019,16 +31157,16 @@ export default class Client extends OpenApi {
|
|
|
31019
31157
|
}
|
|
31020
31158
|
|
|
31021
31159
|
/**
|
|
31022
|
-
* Releases a specified
|
|
31160
|
+
* Releases a specified elastic IP address (EIP).
|
|
31023
31161
|
*
|
|
31024
31162
|
* @remarks
|
|
31025
|
-
* Before you invoke this operation, take note of the following
|
|
31026
|
-
* - Before
|
|
31163
|
+
* Before you invoke this operation, take note of the following information:
|
|
31164
|
+
* - Before you release an EIP, make sure that the following conditions are met:
|
|
31027
31165
|
* - Only EIPs in the **Available** state can be released.
|
|
31028
31166
|
* - 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,
|
|
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
|
|
31167
|
+
* - 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:
|
|
31168
|
+
* - 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.
|
|
31169
|
+
* - If the EIP instance cannot be found, the EIP instance is released.
|
|
31032
31170
|
* - The **ReleaseEipAddress** operation does not support concurrent release of the same EIP instance.
|
|
31033
31171
|
*
|
|
31034
31172
|
* @param request - ReleaseEipAddressRequest
|
|
@@ -31080,16 +31218,16 @@ export default class Client extends OpenApi {
|
|
|
31080
31218
|
}
|
|
31081
31219
|
|
|
31082
31220
|
/**
|
|
31083
|
-
* Releases a specified
|
|
31221
|
+
* Releases a specified elastic IP address (EIP).
|
|
31084
31222
|
*
|
|
31085
31223
|
* @remarks
|
|
31086
|
-
* Before you invoke this operation, take note of the following
|
|
31087
|
-
* - Before
|
|
31224
|
+
* Before you invoke this operation, take note of the following information:
|
|
31225
|
+
* - Before you release an EIP, make sure that the following conditions are met:
|
|
31088
31226
|
* - Only EIPs in the **Available** state can be released.
|
|
31089
31227
|
* - 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,
|
|
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
|
|
31228
|
+
* - 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:
|
|
31229
|
+
* - 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.
|
|
31230
|
+
* - If the EIP instance cannot be found, the EIP instance is released.
|
|
31093
31231
|
* - The **ReleaseEipAddress** operation does not support concurrent release of the same EIP instance.
|
|
31094
31232
|
*
|
|
31095
31233
|
* @param request - ReleaseEipAddressRequest
|
|
@@ -33243,10 +33381,10 @@ export default class Client extends OpenApi {
|
|
|
33243
33381
|
}
|
|
33244
33382
|
|
|
33245
33383
|
/**
|
|
33246
|
-
*
|
|
33384
|
+
* Invokes UnassociateVpcCidrBlock to delete a secondary CIDR block from a VPC.
|
|
33247
33385
|
*
|
|
33248
33386
|
* @remarks
|
|
33249
|
-
* - Before
|
|
33387
|
+
* - 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
33388
|
* - The **UnassociateVpcCidrBlock** operation does not support concurrently deleting secondary CIDR blocks from the same VPC.
|
|
33251
33389
|
*
|
|
33252
33390
|
* @param request - UnassociateVpcCidrBlockRequest
|
|
@@ -33310,10 +33448,10 @@ export default class Client extends OpenApi {
|
|
|
33310
33448
|
}
|
|
33311
33449
|
|
|
33312
33450
|
/**
|
|
33313
|
-
*
|
|
33451
|
+
* Invokes UnassociateVpcCidrBlock to delete a secondary CIDR block from a VPC.
|
|
33314
33452
|
*
|
|
33315
33453
|
* @remarks
|
|
33316
|
-
* - Before
|
|
33454
|
+
* - 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
33455
|
* - The **UnassociateVpcCidrBlock** operation does not support concurrently deleting secondary CIDR blocks from the same VPC.
|
|
33318
33456
|
*
|
|
33319
33457
|
* @param request - UnassociateVpcCidrBlockRequest
|
|
@@ -33399,7 +33537,7 @@ export default class Client extends OpenApi {
|
|
|
33399
33537
|
}
|
|
33400
33538
|
|
|
33401
33539
|
/**
|
|
33402
|
-
* Modifies the configuration of a DHCP options set
|
|
33540
|
+
* Modifies the configuration of a DHCP options set.
|
|
33403
33541
|
*
|
|
33404
33542
|
* @param request - UpdateDhcpOptionsSetAttributeRequest
|
|
33405
33543
|
* @param runtime - runtime options for this request RuntimeOptions
|
|
@@ -33482,7 +33620,7 @@ export default class Client extends OpenApi {
|
|
|
33482
33620
|
}
|
|
33483
33621
|
|
|
33484
33622
|
/**
|
|
33485
|
-
* Modifies the configuration of a DHCP options set
|
|
33623
|
+
* Modifies the configuration of a DHCP options set.
|
|
33486
33624
|
*
|
|
33487
33625
|
* @param request - UpdateDhcpOptionsSetAttributeRequest
|
|
33488
33626
|
* @returns UpdateDhcpOptionsSetAttributeResponse
|