@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/dist/client.js
CHANGED
|
@@ -139,7 +139,7 @@ class Client extends openapi_core_1.default {
|
|
|
139
139
|
* Activates a router interface that is in the Inactive state.
|
|
140
140
|
*
|
|
141
141
|
* @remarks
|
|
142
|
-
* After you call the ActivateRouterInterface operation, the router interface enters the **Activating** state
|
|
142
|
+
* After you call the ActivateRouterInterface operation, the router interface enters the **Activating** state. After the activation succeeds, the router interface enters the **Active** state.
|
|
143
143
|
* 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.
|
|
144
144
|
* > You cannot activate a router interface that has an overdue payment.
|
|
145
145
|
*
|
|
@@ -185,7 +185,7 @@ class Client extends openapi_core_1.default {
|
|
|
185
185
|
* Activates a router interface that is in the Inactive state.
|
|
186
186
|
*
|
|
187
187
|
* @remarks
|
|
188
|
-
* After you call the ActivateRouterInterface operation, the router interface enters the **Activating** state
|
|
188
|
+
* After you call the ActivateRouterInterface operation, the router interface enters the **Activating** state. After the activation succeeds, the router interface enters the **Active** state.
|
|
189
189
|
* 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.
|
|
190
190
|
* > You cannot activate a router interface that has an overdue payment.
|
|
191
191
|
*
|
|
@@ -779,8 +779,8 @@ class Client extends openapi_core_1.default {
|
|
|
779
779
|
* Applies for an elastic IP address (EIP).
|
|
780
780
|
*
|
|
781
781
|
* @remarks
|
|
782
|
-
*
|
|
783
|
-
* 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.
|
|
782
|
+
* 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).
|
|
783
|
+
* 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.
|
|
784
784
|
*
|
|
785
785
|
* @param request - AllocateEipAddressRequest
|
|
786
786
|
* @param runtime - runtime options for this request RuntimeOptions
|
|
@@ -881,8 +881,8 @@ class Client extends openapi_core_1.default {
|
|
|
881
881
|
* Applies for an elastic IP address (EIP).
|
|
882
882
|
*
|
|
883
883
|
* @remarks
|
|
884
|
-
*
|
|
885
|
-
* 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.
|
|
884
|
+
* 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).
|
|
885
|
+
* 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.
|
|
886
886
|
*
|
|
887
887
|
* @param request - AllocateEipAddressRequest
|
|
888
888
|
* @returns AllocateEipAddressResponse
|
|
@@ -2395,7 +2395,7 @@ class Client extends openapi_core_1.default {
|
|
|
2395
2395
|
return await this.attachDhcpOptionsSetToVpcWithOptions(request, runtime);
|
|
2396
2396
|
}
|
|
2397
2397
|
/**
|
|
2398
|
-
* Associates a Virtual Border Router (VBR) instance with shared Express Connect circuits.
|
|
2398
|
+
* 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.
|
|
2399
2399
|
*
|
|
2400
2400
|
* @param request - AttachVbrToVpconnRequest
|
|
2401
2401
|
* @param runtime - runtime options for this request RuntimeOptions
|
|
@@ -2436,7 +2436,7 @@ class Client extends openapi_core_1.default {
|
|
|
2436
2436
|
return $dara.cast(await this.callApi(params, req, runtime), new $_model.AttachVbrToVpconnResponse({}));
|
|
2437
2437
|
}
|
|
2438
2438
|
/**
|
|
2439
|
-
* Associates a Virtual Border Router (VBR) instance with shared Express Connect circuits.
|
|
2439
|
+
* 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.
|
|
2440
2440
|
*
|
|
2441
2441
|
* @param request - AttachVbrToVpconnRequest
|
|
2442
2442
|
* @returns AttachVbrToVpconnResponse
|
|
@@ -2747,10 +2747,12 @@ class Client extends openapi_core_1.default {
|
|
|
2747
2747
|
return await this.checkVpnBgpEnabledWithOptions(request, runtime);
|
|
2748
2748
|
}
|
|
2749
2749
|
/**
|
|
2750
|
-
*
|
|
2750
|
+
* Calls CompletePhysicalConnectionLOA to complete the construction and backfill the completion information after the LOA is approved and the line construction is finished.
|
|
2751
2751
|
*
|
|
2752
2752
|
* @remarks
|
|
2753
|
-
*
|
|
2753
|
+
* 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**.
|
|
2754
|
+
* Complete call chain:
|
|
2755
|
+
* 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).
|
|
2754
2756
|
*
|
|
2755
2757
|
* @param request - CompletePhysicalConnectionLOARequest
|
|
2756
2758
|
* @param runtime - runtime options for this request RuntimeOptions
|
|
@@ -2815,10 +2817,12 @@ class Client extends openapi_core_1.default {
|
|
|
2815
2817
|
return $dara.cast(await this.callApi(params, req, runtime), new $_model.CompletePhysicalConnectionLOAResponse({}));
|
|
2816
2818
|
}
|
|
2817
2819
|
/**
|
|
2818
|
-
*
|
|
2820
|
+
* Calls CompletePhysicalConnectionLOA to complete the construction and backfill the completion information after the LOA is approved and the line construction is finished.
|
|
2819
2821
|
*
|
|
2820
2822
|
* @remarks
|
|
2821
|
-
*
|
|
2823
|
+
* 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**.
|
|
2824
|
+
* Complete call chain:
|
|
2825
|
+
* 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).
|
|
2822
2826
|
*
|
|
2823
2827
|
* @param request - CompletePhysicalConnectionLOARequest
|
|
2824
2828
|
* @returns CompletePhysicalConnectionLOAResponse
|
|
@@ -2885,11 +2889,11 @@ class Client extends openapi_core_1.default {
|
|
|
2885
2889
|
return await this.confirmPhysicalConnectionWithOptions(request, runtime);
|
|
2886
2890
|
}
|
|
2887
2891
|
/**
|
|
2888
|
-
*
|
|
2892
|
+
* Calls the ConnectRouterInterface operation to initiate a connection from the requester VPC router interface to the accepter.
|
|
2889
2893
|
*
|
|
2890
2894
|
* @remarks
|
|
2891
|
-
* After you
|
|
2892
|
-
* When you
|
|
2895
|
+
* After you invoke this operation, the router interface enters the **Connecting** state and transitions to the **Active** state after the connection is established.
|
|
2896
|
+
* When you invoke this operation to create a VPC, note the following items:
|
|
2893
2897
|
* - Only a requester VPC router interface in the **Idle** state can initiate a connection to the accepter VPC.
|
|
2894
2898
|
* - A maximum of one pair of interconnected router interfaces can exist between any two routers.
|
|
2895
2899
|
* - If your account has a router interface with an overdue payment, you cannot initiate a connection.
|
|
@@ -2933,11 +2937,11 @@ class Client extends openapi_core_1.default {
|
|
|
2933
2937
|
return $dara.cast(await this.callApi(params, req, runtime), new $_model.ConnectRouterInterfaceResponse({}));
|
|
2934
2938
|
}
|
|
2935
2939
|
/**
|
|
2936
|
-
*
|
|
2940
|
+
* Calls the ConnectRouterInterface operation to initiate a connection from the requester VPC router interface to the accepter.
|
|
2937
2941
|
*
|
|
2938
2942
|
* @remarks
|
|
2939
|
-
* After you
|
|
2940
|
-
* When you
|
|
2943
|
+
* After you invoke this operation, the router interface enters the **Connecting** state and transitions to the **Active** state after the connection is established.
|
|
2944
|
+
* When you invoke this operation to create a VPC, note the following items:
|
|
2941
2945
|
* - Only a requester VPC router interface in the **Idle** state can initiate a connection to the accepter VPC.
|
|
2942
2946
|
* - A maximum of one pair of interconnected router interfaces can exist between any two routers.
|
|
2943
2947
|
* - If your account has a router interface with an overdue payment, you cannot initiate a connection.
|
|
@@ -4064,18 +4068,28 @@ class Client extends openapi_core_1.default {
|
|
|
4064
4068
|
return await this.createExpressConnectTrafficQosRuleWithOptions(request, runtime);
|
|
4065
4069
|
}
|
|
4066
4070
|
/**
|
|
4067
|
-
*
|
|
4071
|
+
* Calls the CreateFailoverTestJob operation to create a failover test job for Express Connect.
|
|
4068
4072
|
*
|
|
4069
4073
|
* @remarks
|
|
4070
|
-
*
|
|
4071
|
-
* -
|
|
4074
|
+
* Resource status requirements (prerequisites)
|
|
4075
|
+
* - Before creating a failover test job, ensure that the test resources and their associated resources are in the following states. Otherwise, the creation fails:
|
|
4076
|
+
* - 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.
|
|
4077
|
+
* - 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.
|
|
4078
|
+
* - 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.
|
|
4079
|
+
* How to check and advance the Express Connect circuit status
|
|
4080
|
+
* - 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:
|
|
4081
|
+
* - Allocated (port reserved, pending confirmation) → Call ConfirmPhysicalConnection to confirm → Confirmed → Call EnablePhysicalConnection to activate (asynchronous; poll DescribePhysicalConnections after activation to confirm) → Enabled.
|
|
4082
|
+
* - Note: EnablePhysicalConnection only supports activating Express Connect circuits in the Confirmed state. If the circuit is in the Allocated state, call ConfirmPhysicalConnection first.
|
|
4083
|
+
* - 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.
|
|
4084
|
+
* The following scenarios do not support creating failover test jobs:
|
|
4085
|
+
* - 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.
|
|
4072
4086
|
* - The Express Connect circuit instance or shared Express Connect circuit instance has not been paid for or has an overdue payment.
|
|
4073
4087
|
* - The Express Connect circuit instance or shared Express Connect circuit instance is already in another running failover test job.
|
|
4074
4088
|
*
|
|
4075
4089
|
* - The Express Connect circuit instance has more than one shared Express Connect circuit.
|
|
4076
|
-
* - The Express Connect circuit instance has more than one cross-account
|
|
4090
|
+
* - The Express Connect circuit instance has more than one cross-account VBR.
|
|
4077
4091
|
* - The shared Express Connect circuit instance is not associated with a VBR.
|
|
4078
|
-
* - The VLAN of the shared Express Connect circuit instance is
|
|
4092
|
+
* - The VLAN configuration of the shared Express Connect circuit instance is 0.
|
|
4079
4093
|
*
|
|
4080
4094
|
* @param request - CreateFailoverTestJobRequest
|
|
4081
4095
|
* @param runtime - runtime options for this request RuntimeOptions
|
|
@@ -4140,18 +4154,28 @@ class Client extends openapi_core_1.default {
|
|
|
4140
4154
|
return $dara.cast(await this.callApi(params, req, runtime), new $_model.CreateFailoverTestJobResponse({}));
|
|
4141
4155
|
}
|
|
4142
4156
|
/**
|
|
4143
|
-
*
|
|
4157
|
+
* Calls the CreateFailoverTestJob operation to create a failover test job for Express Connect.
|
|
4144
4158
|
*
|
|
4145
4159
|
* @remarks
|
|
4146
|
-
*
|
|
4147
|
-
* -
|
|
4160
|
+
* Resource status requirements (prerequisites)
|
|
4161
|
+
* - Before creating a failover test job, ensure that the test resources and their associated resources are in the following states. Otherwise, the creation fails:
|
|
4162
|
+
* - 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.
|
|
4163
|
+
* - 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.
|
|
4164
|
+
* - 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.
|
|
4165
|
+
* How to check and advance the Express Connect circuit status
|
|
4166
|
+
* - 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:
|
|
4167
|
+
* - Allocated (port reserved, pending confirmation) → Call ConfirmPhysicalConnection to confirm → Confirmed → Call EnablePhysicalConnection to activate (asynchronous; poll DescribePhysicalConnections after activation to confirm) → Enabled.
|
|
4168
|
+
* - Note: EnablePhysicalConnection only supports activating Express Connect circuits in the Confirmed state. If the circuit is in the Allocated state, call ConfirmPhysicalConnection first.
|
|
4169
|
+
* - 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.
|
|
4170
|
+
* The following scenarios do not support creating failover test jobs:
|
|
4171
|
+
* - 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.
|
|
4148
4172
|
* - The Express Connect circuit instance or shared Express Connect circuit instance has not been paid for or has an overdue payment.
|
|
4149
4173
|
* - The Express Connect circuit instance or shared Express Connect circuit instance is already in another running failover test job.
|
|
4150
4174
|
*
|
|
4151
4175
|
* - The Express Connect circuit instance has more than one shared Express Connect circuit.
|
|
4152
|
-
* - The Express Connect circuit instance has more than one cross-account
|
|
4176
|
+
* - The Express Connect circuit instance has more than one cross-account VBR.
|
|
4153
4177
|
* - The shared Express Connect circuit instance is not associated with a VBR.
|
|
4154
|
-
* - The VLAN of the shared Express Connect circuit instance is
|
|
4178
|
+
* - The VLAN configuration of the shared Express Connect circuit instance is 0.
|
|
4155
4179
|
*
|
|
4156
4180
|
* @param request - CreateFailoverTestJobRequest
|
|
4157
4181
|
* @returns CreateFailoverTestJobResponse
|
|
@@ -6382,8 +6406,8 @@ class Client extends openapi_core_1.default {
|
|
|
6382
6406
|
* - If the routing target group is in the **Pending** state, the routing target group is being created.
|
|
6383
6407
|
* - If the routing target group is in the **Available**, **Unavailable**, **Switched**, or **Abnormal** state, the routing target group is created.
|
|
6384
6408
|
* - **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.
|
|
6385
|
-
* - **Primary instance**: The weight is 100. The primary instance
|
|
6386
|
-
* - **Secondary instance**: The weight is 0. The secondary instance takes over traffic
|
|
6409
|
+
* - **Primary instance**: The weight is 100. The primary instance carries all traffic under normal conditions and takes effect when health checks are successful.
|
|
6410
|
+
* - **Secondary instance**: The weight is 0. The secondary instance takes over traffic after the primary instance fails and serves as disaster recovery and backup.
|
|
6387
6411
|
*
|
|
6388
6412
|
* @param request - CreateRouteTargetGroupRequest
|
|
6389
6413
|
* @param runtime - runtime options for this request RuntimeOptions
|
|
@@ -6443,8 +6467,8 @@ class Client extends openapi_core_1.default {
|
|
|
6443
6467
|
* - If the routing target group is in the **Pending** state, the routing target group is being created.
|
|
6444
6468
|
* - If the routing target group is in the **Available**, **Unavailable**, **Switched**, or **Abnormal** state, the routing target group is created.
|
|
6445
6469
|
* - **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.
|
|
6446
|
-
* - **Primary instance**: The weight is 100. The primary instance
|
|
6447
|
-
* - **Secondary instance**: The weight is 0. The secondary instance takes over traffic
|
|
6470
|
+
* - **Primary instance**: The weight is 100. The primary instance carries all traffic under normal conditions and takes effect when health checks are successful.
|
|
6471
|
+
* - **Secondary instance**: The weight is 0. The secondary instance takes over traffic after the primary instance fails and serves as disaster recovery and backup.
|
|
6448
6472
|
*
|
|
6449
6473
|
* @param request - CreateRouteTargetGroupRequest
|
|
6450
6474
|
* @returns CreateRouteTargetGroupResponse
|
|
@@ -7626,7 +7650,18 @@ class Client extends openapi_core_1.default {
|
|
|
7626
7650
|
* Invokes the CreateVirtualPhysicalConnection operation to create shared Express Connect circuits.
|
|
7627
7651
|
*
|
|
7628
7652
|
* @remarks
|
|
7629
|
-
* Before
|
|
7653
|
+
* 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).
|
|
7654
|
+
* Before you call this operation, make sure the following conditions are met:
|
|
7655
|
+
* - 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:
|
|
7656
|
+
* - CreatePhysicalConnection: Creates an Express Connect circuit.
|
|
7657
|
+
* - 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.
|
|
7658
|
+
* - ConfirmPhysicalConnection: Reports construction completion. The circuit must be in the Allocated state. After success, it enters the Confirmed state.
|
|
7659
|
+
* - 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.
|
|
7660
|
+
* - 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).
|
|
7661
|
+
* - 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.
|
|
7662
|
+
* - VpconnAliUid is the tenant\\"s Alibaba Cloud account (RAM users or partner accounts are not supported). Cross-site pushing is not allowed by default.
|
|
7663
|
+
* - The number of shared Express Connect circuits on a single Express Connect circuit has not exceeded the quota.
|
|
7664
|
+
* - 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.
|
|
7630
7665
|
*
|
|
7631
7666
|
* @param request - CreateVirtualPhysicalConnectionRequest
|
|
7632
7667
|
* @param runtime - runtime options for this request RuntimeOptions
|
|
@@ -7691,7 +7726,18 @@ class Client extends openapi_core_1.default {
|
|
|
7691
7726
|
* Invokes the CreateVirtualPhysicalConnection operation to create shared Express Connect circuits.
|
|
7692
7727
|
*
|
|
7693
7728
|
* @remarks
|
|
7694
|
-
* Before
|
|
7729
|
+
* 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).
|
|
7730
|
+
* Before you call this operation, make sure the following conditions are met:
|
|
7731
|
+
* - 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:
|
|
7732
|
+
* - CreatePhysicalConnection: Creates an Express Connect circuit.
|
|
7733
|
+
* - 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.
|
|
7734
|
+
* - ConfirmPhysicalConnection: Reports construction completion. The circuit must be in the Allocated state. After success, it enters the Confirmed state.
|
|
7735
|
+
* - 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.
|
|
7736
|
+
* - 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).
|
|
7737
|
+
* - 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.
|
|
7738
|
+
* - VpconnAliUid is the tenant\\"s Alibaba Cloud account (RAM users or partner accounts are not supported). Cross-site pushing is not allowed by default.
|
|
7739
|
+
* - The number of shared Express Connect circuits on a single Express Connect circuit has not exceeded the quota.
|
|
7740
|
+
* - 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.
|
|
7695
7741
|
*
|
|
7696
7742
|
* @param request - CreateVirtualPhysicalConnectionRequest
|
|
7697
7743
|
* @returns CreateVirtualPhysicalConnectionResponse
|
|
@@ -8818,6 +8864,9 @@ class Client extends openapi_core_1.default {
|
|
|
8818
8864
|
/**
|
|
8819
8865
|
* Deletes an advertised Border Gateway Protocol (BGP) network.
|
|
8820
8866
|
*
|
|
8867
|
+
* @remarks
|
|
8868
|
+
* 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.
|
|
8869
|
+
*
|
|
8821
8870
|
* @param request - DeleteBgpNetworkRequest
|
|
8822
8871
|
* @param runtime - runtime options for this request RuntimeOptions
|
|
8823
8872
|
* @returns DeleteBgpNetworkResponse
|
|
@@ -8868,6 +8917,9 @@ class Client extends openapi_core_1.default {
|
|
|
8868
8917
|
/**
|
|
8869
8918
|
* Deletes an advertised Border Gateway Protocol (BGP) network.
|
|
8870
8919
|
*
|
|
8920
|
+
* @remarks
|
|
8921
|
+
* 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.
|
|
8922
|
+
*
|
|
8871
8923
|
* @param request - DeleteBgpNetworkRequest
|
|
8872
8924
|
* @returns DeleteBgpNetworkResponse
|
|
8873
8925
|
*/
|
|
@@ -10759,11 +10811,11 @@ class Client extends openapi_core_1.default {
|
|
|
10759
10811
|
*
|
|
10760
10812
|
* @remarks
|
|
10761
10813
|
* Before you call this operation, take note of the following items:
|
|
10762
|
-
* - Before
|
|
10814
|
+
* - Before you delete an IP address pool, make sure that the IP addresses in the pool are not in use.
|
|
10763
10815
|
* - **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.
|
|
10764
10816
|
* - 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.
|
|
10765
10817
|
* - If the IP address pool cannot be found, the IP address pool is deleted.
|
|
10766
|
-
* - **DeletePublicIpAddressPool**
|
|
10818
|
+
* - You cannot call **DeletePublicIpAddressPool** to concurrently delete the same IP address pool.
|
|
10767
10819
|
*
|
|
10768
10820
|
* @param request - DeletePublicIpAddressPoolRequest
|
|
10769
10821
|
* @param runtime - runtime options for this request RuntimeOptions
|
|
@@ -10817,11 +10869,11 @@ class Client extends openapi_core_1.default {
|
|
|
10817
10869
|
*
|
|
10818
10870
|
* @remarks
|
|
10819
10871
|
* Before you call this operation, take note of the following items:
|
|
10820
|
-
* - Before
|
|
10872
|
+
* - Before you delete an IP address pool, make sure that the IP addresses in the pool are not in use.
|
|
10821
10873
|
* - **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.
|
|
10822
10874
|
* - 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.
|
|
10823
10875
|
* - If the IP address pool cannot be found, the IP address pool is deleted.
|
|
10824
|
-
* - **DeletePublicIpAddressPool**
|
|
10876
|
+
* - You cannot call **DeletePublicIpAddressPool** to concurrently delete the same IP address pool.
|
|
10825
10877
|
*
|
|
10826
10878
|
* @param request - DeletePublicIpAddressPoolRequest
|
|
10827
10879
|
* @returns DeletePublicIpAddressPoolResponse
|
|
@@ -10836,7 +10888,7 @@ class Client extends openapi_core_1.default {
|
|
|
10836
10888
|
* @remarks
|
|
10837
10889
|
* Before you call this operation, take note of the following information:
|
|
10838
10890
|
* - Before deleting a CIDR block, make sure that the CIDR block is not in use.
|
|
10839
|
-
* - **DeletePublicIpAddressPoolCidrBlock** is an asynchronous operation. After a request is sent, the system returns a request ID
|
|
10891
|
+
* - **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.
|
|
10840
10892
|
* - If the CIDR block is in the **Deleting** state, the CIDR block is being deleted. In this state, you can only perform query operations.
|
|
10841
10893
|
* - If the CIDR block cannot be found, the CIDR block is deleted.
|
|
10842
10894
|
* - The **DeletePublicIpAddressPoolCidrBlock** operation does not support concurrent deletion of the same CIDR block.
|
|
@@ -10897,7 +10949,7 @@ class Client extends openapi_core_1.default {
|
|
|
10897
10949
|
* @remarks
|
|
10898
10950
|
* Before you call this operation, take note of the following information:
|
|
10899
10951
|
* - Before deleting a CIDR block, make sure that the CIDR block is not in use.
|
|
10900
|
-
* - **DeletePublicIpAddressPoolCidrBlock** is an asynchronous operation. After a request is sent, the system returns a request ID
|
|
10952
|
+
* - **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.
|
|
10901
10953
|
* - If the CIDR block is in the **Deleting** state, the CIDR block is being deleted. In this state, you can only perform query operations.
|
|
10902
10954
|
* - If the CIDR block cannot be found, the CIDR block is deleted.
|
|
10903
10955
|
* - The **DeletePublicIpAddressPoolCidrBlock** operation does not support concurrent deletion of the same CIDR block.
|
|
@@ -10910,16 +10962,16 @@ class Client extends openapi_core_1.default {
|
|
|
10910
10962
|
return await this.deletePublicIpAddressPoolCidrBlockWithOptions(request, runtime);
|
|
10911
10963
|
}
|
|
10912
10964
|
/**
|
|
10913
|
-
*
|
|
10965
|
+
* Calls DeleteRouteEntries to batch delete custom route entries.
|
|
10914
10966
|
*
|
|
10915
10967
|
* @remarks
|
|
10916
10968
|
* When you call this operation to delete routing entries, note the following items:
|
|
10917
10969
|
* - Only routing entries in the **Available** state can be deleted.
|
|
10918
|
-
* - Routing entries cannot be deleted if the VPC
|
|
10919
|
-
* - The **DeleteRouteEntries** operation is asynchronous. After you send a request, the system returns a request ID, but the
|
|
10920
|
-
* - If the
|
|
10921
|
-
* - If the specified
|
|
10922
|
-
* - The **DeleteRouteEntries** operation does not support concurrent batch deletion of routing entries
|
|
10970
|
+
* - Routing entries cannot be deleted if the VPC that contains the route table is creating or deleting a vSwitch or routing entry.
|
|
10971
|
+
* - 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:
|
|
10972
|
+
* - If the routing entry is in the **Deleting** state, the routing entry is being deleted.
|
|
10973
|
+
* - If the specified routing entry cannot be found, the routing entry is deleted.
|
|
10974
|
+
* - The **DeleteRouteEntries** operation does not support concurrent batch deletion of routing entries in route tables within the same VPC.
|
|
10923
10975
|
*
|
|
10924
10976
|
* @param request - DeleteRouteEntriesRequest
|
|
10925
10977
|
* @param runtime - runtime options for this request RuntimeOptions
|
|
@@ -10969,16 +11021,16 @@ class Client extends openapi_core_1.default {
|
|
|
10969
11021
|
return $dara.cast(await this.callApi(params, req, runtime), new $_model.DeleteRouteEntriesResponse({}));
|
|
10970
11022
|
}
|
|
10971
11023
|
/**
|
|
10972
|
-
*
|
|
11024
|
+
* Calls DeleteRouteEntries to batch delete custom route entries.
|
|
10973
11025
|
*
|
|
10974
11026
|
* @remarks
|
|
10975
11027
|
* When you call this operation to delete routing entries, note the following items:
|
|
10976
11028
|
* - Only routing entries in the **Available** state can be deleted.
|
|
10977
|
-
* - Routing entries cannot be deleted if the VPC
|
|
10978
|
-
* - The **DeleteRouteEntries** operation is asynchronous. After you send a request, the system returns a request ID, but the
|
|
10979
|
-
* - If the
|
|
10980
|
-
* - If the specified
|
|
10981
|
-
* - The **DeleteRouteEntries** operation does not support concurrent batch deletion of routing entries
|
|
11029
|
+
* - Routing entries cannot be deleted if the VPC that contains the route table is creating or deleting a vSwitch or routing entry.
|
|
11030
|
+
* - 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:
|
|
11031
|
+
* - If the routing entry is in the **Deleting** state, the routing entry is being deleted.
|
|
11032
|
+
* - If the specified routing entry cannot be found, the routing entry is deleted.
|
|
11033
|
+
* - The **DeleteRouteEntries** operation does not support concurrent batch deletion of routing entries in route tables within the same VPC.
|
|
10982
11034
|
*
|
|
10983
11035
|
* @param request - DeleteRouteEntriesRequest
|
|
10984
11036
|
* @returns DeleteRouteEntriesResponse
|
|
@@ -15411,7 +15463,7 @@ class Client extends openapi_core_1.default {
|
|
|
15411
15463
|
* Queries information about Express Connect circuits in a specified region.
|
|
15412
15464
|
*
|
|
15413
15465
|
* @remarks
|
|
15414
|
-
* 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
|
|
15466
|
+
* 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.
|
|
15415
15467
|
*
|
|
15416
15468
|
* @param request - DescribePhysicalConnectionsRequest
|
|
15417
15469
|
* @param runtime - runtime options for this request RuntimeOptions
|
|
@@ -15476,7 +15528,7 @@ class Client extends openapi_core_1.default {
|
|
|
15476
15528
|
* Queries information about Express Connect circuits in a specified region.
|
|
15477
15529
|
*
|
|
15478
15530
|
* @remarks
|
|
15479
|
-
* 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
|
|
15531
|
+
* 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.
|
|
15480
15532
|
*
|
|
15481
15533
|
* @param request - DescribePhysicalConnectionsRequest
|
|
15482
15534
|
* @returns DescribePhysicalConnectionsResponse
|
|
@@ -15920,7 +15972,7 @@ class Client extends openapi_core_1.default {
|
|
|
15920
15972
|
return await this.describeRouterInterfaceAttributeWithOptions(request, runtime);
|
|
15921
15973
|
}
|
|
15922
15974
|
/**
|
|
15923
|
-
* Queries router interfaces in a specified region
|
|
15975
|
+
* Queries router interfaces in a specified region.
|
|
15924
15976
|
*
|
|
15925
15977
|
* @param request - DescribeRouterInterfacesRequest
|
|
15926
15978
|
* @param runtime - runtime options for this request RuntimeOptions
|
|
@@ -15976,7 +16028,7 @@ class Client extends openapi_core_1.default {
|
|
|
15976
16028
|
return $dara.cast(await this.callApi(params, req, runtime), new $_model.DescribeRouterInterfacesResponse({}));
|
|
15977
16029
|
}
|
|
15978
16030
|
/**
|
|
15979
|
-
* Queries router interfaces in a specified region
|
|
16031
|
+
* Queries router interfaces in a specified region.
|
|
15980
16032
|
*
|
|
15981
16033
|
* @param request - DescribeRouterInterfacesRequest
|
|
15982
16034
|
* @returns DescribeRouterInterfacesResponse
|
|
@@ -17203,7 +17255,7 @@ class Client extends openapi_core_1.default {
|
|
|
17203
17255
|
* Queries created VPCs.
|
|
17204
17256
|
*
|
|
17205
17257
|
* @remarks
|
|
17206
|
-
* The **DescribeVpcs** operation may return the **Throttling.DeepPageSkip** error code during frequent deep paging
|
|
17258
|
+
* 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.
|
|
17207
17259
|
*
|
|
17208
17260
|
* @param request - DescribeVpcsRequest
|
|
17209
17261
|
* @param runtime - runtime options for this request RuntimeOptions
|
|
@@ -17280,7 +17332,7 @@ class Client extends openapi_core_1.default {
|
|
|
17280
17332
|
* Queries created VPCs.
|
|
17281
17333
|
*
|
|
17282
17334
|
* @remarks
|
|
17283
|
-
* The **DescribeVpcs** operation may return the **Throttling.DeepPageSkip** error code during frequent deep paging
|
|
17335
|
+
* 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.
|
|
17284
17336
|
*
|
|
17285
17337
|
* @param request - DescribeVpcsRequest
|
|
17286
17338
|
* @returns DescribeVpcsResponse
|
|
@@ -18609,11 +18661,12 @@ class Client extends openapi_core_1.default {
|
|
|
18609
18661
|
* Enables an Express Connect circuit that is in the Confirmed state. After the circuit is enabled, it enters the Enabled state.
|
|
18610
18662
|
*
|
|
18611
18663
|
* @remarks
|
|
18612
|
-
* When you
|
|
18613
|
-
* - You can enable only an Express Connect circuit that is in the
|
|
18614
|
-
* -
|
|
18615
|
-
* -
|
|
18616
|
-
* -
|
|
18664
|
+
* When you invoke this operation, note the following items:
|
|
18665
|
+
* - 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).
|
|
18666
|
+
* - 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.
|
|
18667
|
+
* - 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.
|
|
18668
|
+
* - 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.
|
|
18669
|
+
* If the Express Connect circuit is already in the Enabled state, invoking this operation again returns a success response (idempotent).
|
|
18617
18670
|
*
|
|
18618
18671
|
* @param request - EnablePhysicalConnectionRequest
|
|
18619
18672
|
* @param runtime - runtime options for this request RuntimeOptions
|
|
@@ -18666,11 +18719,12 @@ class Client extends openapi_core_1.default {
|
|
|
18666
18719
|
* Enables an Express Connect circuit that is in the Confirmed state. After the circuit is enabled, it enters the Enabled state.
|
|
18667
18720
|
*
|
|
18668
18721
|
* @remarks
|
|
18669
|
-
* When you
|
|
18670
|
-
* - You can enable only an Express Connect circuit that is in the
|
|
18671
|
-
* -
|
|
18672
|
-
* -
|
|
18673
|
-
* -
|
|
18722
|
+
* When you invoke this operation, note the following items:
|
|
18723
|
+
* - 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).
|
|
18724
|
+
* - 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.
|
|
18725
|
+
* - 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.
|
|
18726
|
+
* - 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.
|
|
18727
|
+
* If the Express Connect circuit is already in the Enabled state, invoking this operation again returns a success response (idempotent).
|
|
18674
18728
|
*
|
|
18675
18729
|
* @param request - EnablePhysicalConnectionRequest
|
|
18676
18730
|
* @returns EnablePhysicalConnectionResponse
|
|
@@ -18991,7 +19045,7 @@ class Client extends openapi_core_1.default {
|
|
|
18991
19045
|
* Queries the information about a single NAT gateway instance.
|
|
18992
19046
|
*
|
|
18993
19047
|
* @remarks
|
|
18994
|
-
* This operation queries the information about a single Internet NAT gateway or VPC NAT gateway. The term "NAT gateway" in this topic
|
|
19048
|
+
* 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.
|
|
18995
19049
|
*
|
|
18996
19050
|
* @param request - GetNatGatewayAttributeRequest
|
|
18997
19051
|
* @param runtime - runtime options for this request RuntimeOptions
|
|
@@ -19041,7 +19095,7 @@ class Client extends openapi_core_1.default {
|
|
|
19041
19095
|
* Queries the information about a single NAT gateway instance.
|
|
19042
19096
|
*
|
|
19043
19097
|
* @remarks
|
|
19044
|
-
* This operation queries the information about a single Internet NAT gateway or VPC NAT gateway. The term "NAT gateway" in this topic
|
|
19098
|
+
* 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.
|
|
19045
19099
|
*
|
|
19046
19100
|
* @param request - GetNatGatewayAttributeRequest
|
|
19047
19101
|
* @returns GetNatGatewayAttributeResponse
|
|
@@ -19705,7 +19759,18 @@ class Client extends openapi_core_1.default {
|
|
|
19705
19759
|
* Invokes the GrantInstanceToVbr operation to grant authorization of a VPC-connected instance to a VBR instance for cross-account VBR uplink scenarios.
|
|
19706
19760
|
*
|
|
19707
19761
|
* @remarks
|
|
19708
|
-
*
|
|
19762
|
+
* This operation is used for cross-account scenarios. Before calling this operation, ensure that the following resources are ready:
|
|
19763
|
+
* **Account A (VPC owner, the caller of this operation):**
|
|
19764
|
+
* - A VPC has been created and is in the Available state (CreateVpc).
|
|
19765
|
+
* **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:
|
|
19766
|
+
* 1. Call CreatePhysicalConnection to create an Express Connect circuit.
|
|
19767
|
+
* 2. Apply for a Letter of Authorization (LOA) and complete the construction (ApplyPhysicalConnectionLOA → CompletePhysicalConnectionLOA). The Express Connect circuit enters the Confirmed state.
|
|
19768
|
+
* 3. Call EnablePhysicalConnection to enable the Express Connect circuit (the circuit must be in the Confirmed state).
|
|
19769
|
+
* 4. Call CreateVirtualBorderRouter to create a VBR (the Express Connect circuit must be in the Enabled state. Otherwise, the error InvalidPhysicalConnectionId.NotEnabled is returned).
|
|
19770
|
+
* After the preceding preparations are complete, Account A calls this operation to grant the VPC to the VBR of Account B:
|
|
19771
|
+
* - 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).
|
|
19772
|
+
* - 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.
|
|
19773
|
+
* Note: VbrOwnerUid cannot be the same as the caller\\"s account. Otherwise, the error Parameter.Illegal is returned.
|
|
19709
19774
|
*
|
|
19710
19775
|
* @param tmpReq - GrantInstanceToVbrRequest
|
|
19711
19776
|
* @param runtime - runtime options for this request RuntimeOptions
|
|
@@ -19757,7 +19822,18 @@ class Client extends openapi_core_1.default {
|
|
|
19757
19822
|
* Invokes the GrantInstanceToVbr operation to grant authorization of a VPC-connected instance to a VBR instance for cross-account VBR uplink scenarios.
|
|
19758
19823
|
*
|
|
19759
19824
|
* @remarks
|
|
19760
|
-
*
|
|
19825
|
+
* This operation is used for cross-account scenarios. Before calling this operation, ensure that the following resources are ready:
|
|
19826
|
+
* **Account A (VPC owner, the caller of this operation):**
|
|
19827
|
+
* - A VPC has been created and is in the Available state (CreateVpc).
|
|
19828
|
+
* **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:
|
|
19829
|
+
* 1. Call CreatePhysicalConnection to create an Express Connect circuit.
|
|
19830
|
+
* 2. Apply for a Letter of Authorization (LOA) and complete the construction (ApplyPhysicalConnectionLOA → CompletePhysicalConnectionLOA). The Express Connect circuit enters the Confirmed state.
|
|
19831
|
+
* 3. Call EnablePhysicalConnection to enable the Express Connect circuit (the circuit must be in the Confirmed state).
|
|
19832
|
+
* 4. Call CreateVirtualBorderRouter to create a VBR (the Express Connect circuit must be in the Enabled state. Otherwise, the error InvalidPhysicalConnectionId.NotEnabled is returned).
|
|
19833
|
+
* After the preceding preparations are complete, Account A calls this operation to grant the VPC to the VBR of Account B:
|
|
19834
|
+
* - 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).
|
|
19835
|
+
* - 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.
|
|
19836
|
+
* Note: VbrOwnerUid cannot be the same as the caller\\"s account. Otherwise, the error Parameter.Illegal is returned.
|
|
19761
19837
|
*
|
|
19762
19838
|
* @param request - GrantInstanceToVbrRequest
|
|
19763
19839
|
* @returns GrantInstanceToVbrResponse
|
|
@@ -21248,7 +21324,7 @@ class Client extends openapi_core_1.default {
|
|
|
21248
21324
|
return await this.listVSwitchCidrReservationsWithOptions(request, runtime);
|
|
21249
21325
|
}
|
|
21250
21326
|
/**
|
|
21251
|
-
* Queries information about shared Express Connect circuits
|
|
21327
|
+
* Queries information about shared Express Connect circuits.
|
|
21252
21328
|
*
|
|
21253
21329
|
* @param request - ListVirtualPhysicalConnectionsRequest
|
|
21254
21330
|
* @param runtime - runtime options for this request RuntimeOptions
|
|
@@ -21310,7 +21386,7 @@ class Client extends openapi_core_1.default {
|
|
|
21310
21386
|
return $dara.cast(await this.callApi(params, req, runtime), new $_model.ListVirtualPhysicalConnectionsResponse({}));
|
|
21311
21387
|
}
|
|
21312
21388
|
/**
|
|
21313
|
-
* Queries information about shared Express Connect circuits
|
|
21389
|
+
* Queries information about shared Express Connect circuits.
|
|
21314
21390
|
*
|
|
21315
21391
|
* @param request - ListVirtualPhysicalConnectionsRequest
|
|
21316
21392
|
* @returns ListVirtualPhysicalConnectionsResponse
|
|
@@ -23951,13 +24027,13 @@ class Client extends openapi_core_1.default {
|
|
|
23951
24027
|
return await this.modifyNetworkAclAttributesWithOptions(request, runtime);
|
|
23952
24028
|
}
|
|
23953
24029
|
/**
|
|
23954
|
-
* Modifies the
|
|
24030
|
+
* Modifies the configurations of an Express Connect circuit.
|
|
23955
24031
|
*
|
|
23956
24032
|
* @remarks
|
|
23957
24033
|
* When you call this operation, note the following items:
|
|
23958
24034
|
* - You can modify the specifications and redundant circuit ID only for Express Connect circuits in the **Initial**, **Enabled**, or **Rejected** state.
|
|
23959
24035
|
* - You cannot modify Express Connect circuits in the **Canceled**, **Allocating**, **AllocationFailed**, or **Terminated** state.
|
|
23960
|
-
* -
|
|
24036
|
+
* - After an Express Connect circuit in the **Rejected** state is modified, it enters the **Initial** state.
|
|
23961
24037
|
*
|
|
23962
24038
|
* @param request - ModifyPhysicalConnectionAttributeRequest
|
|
23963
24039
|
* @param runtime - runtime options for this request RuntimeOptions
|
|
@@ -24034,13 +24110,13 @@ class Client extends openapi_core_1.default {
|
|
|
24034
24110
|
return $dara.cast(await this.callApi(params, req, runtime), new $_model.ModifyPhysicalConnectionAttributeResponse({}));
|
|
24035
24111
|
}
|
|
24036
24112
|
/**
|
|
24037
|
-
* Modifies the
|
|
24113
|
+
* Modifies the configurations of an Express Connect circuit.
|
|
24038
24114
|
*
|
|
24039
24115
|
* @remarks
|
|
24040
24116
|
* When you call this operation, note the following items:
|
|
24041
24117
|
* - You can modify the specifications and redundant circuit ID only for Express Connect circuits in the **Initial**, **Enabled**, or **Rejected** state.
|
|
24042
24118
|
* - You cannot modify Express Connect circuits in the **Canceled**, **Allocating**, **AllocationFailed**, or **Terminated** state.
|
|
24043
|
-
* -
|
|
24119
|
+
* - After an Express Connect circuit in the **Rejected** state is modified, it enters the **Initial** state.
|
|
24044
24120
|
*
|
|
24045
24121
|
* @param request - ModifyPhysicalConnectionAttributeRequest
|
|
24046
24122
|
* @returns ModifyPhysicalConnectionAttributeResponse
|
|
@@ -25195,6 +25271,60 @@ class Client extends openapi_core_1.default {
|
|
|
25195
25271
|
let runtime = new $dara.RuntimeOptions({});
|
|
25196
25272
|
return await this.modifyVpcAttributeWithOptions(request, runtime);
|
|
25197
25273
|
}
|
|
25274
|
+
/**
|
|
25275
|
+
* Modifies the primary or secondary CIDR block of a VPC.
|
|
25276
|
+
*
|
|
25277
|
+
* @param request - ModifyVpcCidrBlockRequest
|
|
25278
|
+
* @param runtime - runtime options for this request RuntimeOptions
|
|
25279
|
+
* @returns ModifyVpcCidrBlockResponse
|
|
25280
|
+
*/
|
|
25281
|
+
async modifyVpcCidrBlockWithOptions(request, runtime) {
|
|
25282
|
+
request.validate();
|
|
25283
|
+
let query = {};
|
|
25284
|
+
if (!$dara.isNull(request.clientToken)) {
|
|
25285
|
+
query["ClientToken"] = request.clientToken;
|
|
25286
|
+
}
|
|
25287
|
+
if (!$dara.isNull(request.dryRun)) {
|
|
25288
|
+
query["DryRun"] = request.dryRun;
|
|
25289
|
+
}
|
|
25290
|
+
if (!$dara.isNull(request.originalCidrBlock)) {
|
|
25291
|
+
query["OriginalCidrBlock"] = request.originalCidrBlock;
|
|
25292
|
+
}
|
|
25293
|
+
if (!$dara.isNull(request.regionId)) {
|
|
25294
|
+
query["RegionId"] = request.regionId;
|
|
25295
|
+
}
|
|
25296
|
+
if (!$dara.isNull(request.targetCidrBlock)) {
|
|
25297
|
+
query["TargetCidrBlock"] = request.targetCidrBlock;
|
|
25298
|
+
}
|
|
25299
|
+
if (!$dara.isNull(request.vpcId)) {
|
|
25300
|
+
query["VpcId"] = request.vpcId;
|
|
25301
|
+
}
|
|
25302
|
+
let req = new openapi_core_2.$OpenApiUtil.OpenApiRequest({
|
|
25303
|
+
query: openapi_core_2.OpenApiUtil.query(query),
|
|
25304
|
+
});
|
|
25305
|
+
let params = new openapi_core_2.$OpenApiUtil.Params({
|
|
25306
|
+
action: "ModifyVpcCidrBlock",
|
|
25307
|
+
version: "2016-04-28",
|
|
25308
|
+
protocol: "HTTPS",
|
|
25309
|
+
pathname: "/",
|
|
25310
|
+
method: "POST",
|
|
25311
|
+
authType: "AK",
|
|
25312
|
+
style: "RPC",
|
|
25313
|
+
reqBodyType: "formData",
|
|
25314
|
+
bodyType: "json",
|
|
25315
|
+
});
|
|
25316
|
+
return $dara.cast(await this.callApi(params, req, runtime), new $_model.ModifyVpcCidrBlockResponse({}));
|
|
25317
|
+
}
|
|
25318
|
+
/**
|
|
25319
|
+
* Modifies the primary or secondary CIDR block of a VPC.
|
|
25320
|
+
*
|
|
25321
|
+
* @param request - ModifyVpcCidrBlockRequest
|
|
25322
|
+
* @returns ModifyVpcCidrBlockResponse
|
|
25323
|
+
*/
|
|
25324
|
+
async modifyVpcCidrBlock(request) {
|
|
25325
|
+
let runtime = new $dara.RuntimeOptions({});
|
|
25326
|
+
return await this.modifyVpcCidrBlockWithOptions(request, runtime);
|
|
25327
|
+
}
|
|
25198
25328
|
/**
|
|
25199
25329
|
* Modifies the configuration of a prefix list.
|
|
25200
25330
|
*
|
|
@@ -25976,7 +26106,7 @@ class Client extends openapi_core_1.default {
|
|
|
25976
26106
|
* Modifies the resource group to which a cloud resource belongs.
|
|
25977
26107
|
*
|
|
25978
26108
|
* @remarks
|
|
25979
|
-
* The **ChangeResourceGroup** operation does not support concurrent modifications
|
|
26109
|
+
* The **ChangeResourceGroup** operation does not support concurrent modifications of the resource group for Express Connect circuit resources within the same Express Connect circuit instance.
|
|
25980
26110
|
*
|
|
25981
26111
|
* @param request - MoveResourceGroupRequest
|
|
25982
26112
|
* @param runtime - runtime options for this request RuntimeOptions
|
|
@@ -26029,7 +26159,7 @@ class Client extends openapi_core_1.default {
|
|
|
26029
26159
|
* Modifies the resource group to which a cloud resource belongs.
|
|
26030
26160
|
*
|
|
26031
26161
|
* @remarks
|
|
26032
|
-
* The **ChangeResourceGroup** operation does not support concurrent modifications
|
|
26162
|
+
* The **ChangeResourceGroup** operation does not support concurrent modifications of the resource group for Express Connect circuit resources within the same Express Connect circuit instance.
|
|
26033
26163
|
*
|
|
26034
26164
|
* @param request - MoveResourceGroupRequest
|
|
26035
26165
|
* @returns MoveResourceGroupResponse
|
|
@@ -26605,16 +26735,16 @@ class Client extends openapi_core_1.default {
|
|
|
26605
26735
|
return await this.recoverVirtualBorderRouterWithOptions(request, runtime);
|
|
26606
26736
|
}
|
|
26607
26737
|
/**
|
|
26608
|
-
* Releases a specified
|
|
26738
|
+
* Releases a specified elastic IP address (EIP).
|
|
26609
26739
|
*
|
|
26610
26740
|
* @remarks
|
|
26611
|
-
* Before you invoke this operation, take note of the following
|
|
26612
|
-
* - Before
|
|
26741
|
+
* Before you invoke this operation, take note of the following information:
|
|
26742
|
+
* - Before you release an EIP, make sure that the following conditions are met:
|
|
26613
26743
|
* - Only EIPs in the **Available** state can be released.
|
|
26614
26744
|
* - Only EIPs that use the pay-as-you-go billing method can be released. Subscription EIPs cannot be released.
|
|
26615
|
-
* - The **ReleaseEipAddress** operation is asynchronous. After you send a request, the system returns a request ID,
|
|
26616
|
-
* - If the EIP instance is in the **Releasing** state, the EIP instance is being released. In this state, you can only execute query operations.
|
|
26617
|
-
* - If the EIP instance cannot be found, the EIP instance
|
|
26745
|
+
* - 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:
|
|
26746
|
+
* - 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.
|
|
26747
|
+
* - If the EIP instance cannot be found, the EIP instance is released.
|
|
26618
26748
|
* - The **ReleaseEipAddress** operation does not support concurrent release of the same EIP instance.
|
|
26619
26749
|
*
|
|
26620
26750
|
* @param request - ReleaseEipAddressRequest
|
|
@@ -26659,16 +26789,16 @@ class Client extends openapi_core_1.default {
|
|
|
26659
26789
|
return $dara.cast(await this.callApi(params, req, runtime), new $_model.ReleaseEipAddressResponse({}));
|
|
26660
26790
|
}
|
|
26661
26791
|
/**
|
|
26662
|
-
* Releases a specified
|
|
26792
|
+
* Releases a specified elastic IP address (EIP).
|
|
26663
26793
|
*
|
|
26664
26794
|
* @remarks
|
|
26665
|
-
* Before you invoke this operation, take note of the following
|
|
26666
|
-
* - Before
|
|
26795
|
+
* Before you invoke this operation, take note of the following information:
|
|
26796
|
+
* - Before you release an EIP, make sure that the following conditions are met:
|
|
26667
26797
|
* - Only EIPs in the **Available** state can be released.
|
|
26668
26798
|
* - Only EIPs that use the pay-as-you-go billing method can be released. Subscription EIPs cannot be released.
|
|
26669
|
-
* - The **ReleaseEipAddress** operation is asynchronous. After you send a request, the system returns a request ID,
|
|
26670
|
-
* - If the EIP instance is in the **Releasing** state, the EIP instance is being released. In this state, you can only execute query operations.
|
|
26671
|
-
* - If the EIP instance cannot be found, the EIP instance
|
|
26799
|
+
* - 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:
|
|
26800
|
+
* - 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.
|
|
26801
|
+
* - If the EIP instance cannot be found, the EIP instance is released.
|
|
26672
26802
|
* - The **ReleaseEipAddress** operation does not support concurrent release of the same EIP instance.
|
|
26673
26803
|
*
|
|
26674
26804
|
* @param request - ReleaseEipAddressRequest
|
|
@@ -28540,10 +28670,10 @@ class Client extends openapi_core_1.default {
|
|
|
28540
28670
|
return await this.unassociateRouteTableWithOptions(request, runtime);
|
|
28541
28671
|
}
|
|
28542
28672
|
/**
|
|
28543
|
-
*
|
|
28673
|
+
* Invokes UnassociateVpcCidrBlock to delete a secondary CIDR block from a VPC.
|
|
28544
28674
|
*
|
|
28545
28675
|
* @remarks
|
|
28546
|
-
* - Before
|
|
28676
|
+
* - 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).
|
|
28547
28677
|
* - The **UnassociateVpcCidrBlock** operation does not support concurrently deleting secondary CIDR blocks from the same VPC.
|
|
28548
28678
|
*
|
|
28549
28679
|
* @param request - UnassociateVpcCidrBlockRequest
|
|
@@ -28597,10 +28727,10 @@ class Client extends openapi_core_1.default {
|
|
|
28597
28727
|
return $dara.cast(await this.callApi(params, req, runtime), new $_model.UnassociateVpcCidrBlockResponse({}));
|
|
28598
28728
|
}
|
|
28599
28729
|
/**
|
|
28600
|
-
*
|
|
28730
|
+
* Invokes UnassociateVpcCidrBlock to delete a secondary CIDR block from a VPC.
|
|
28601
28731
|
*
|
|
28602
28732
|
* @remarks
|
|
28603
|
-
* - Before
|
|
28733
|
+
* - 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).
|
|
28604
28734
|
* - The **UnassociateVpcCidrBlock** operation does not support concurrently deleting secondary CIDR blocks from the same VPC.
|
|
28605
28735
|
*
|
|
28606
28736
|
* @param request - UnassociateVpcCidrBlockRequest
|
|
@@ -28674,7 +28804,7 @@ class Client extends openapi_core_1.default {
|
|
|
28674
28804
|
return await this.untagResourcesForExpressConnectWithOptions(request, runtime);
|
|
28675
28805
|
}
|
|
28676
28806
|
/**
|
|
28677
|
-
* Modifies the configuration of a DHCP options set
|
|
28807
|
+
* Modifies the configuration of a DHCP options set.
|
|
28678
28808
|
*
|
|
28679
28809
|
* @param request - UpdateDhcpOptionsSetAttributeRequest
|
|
28680
28810
|
* @param runtime - runtime options for this request RuntimeOptions
|
|
@@ -28742,7 +28872,7 @@ class Client extends openapi_core_1.default {
|
|
|
28742
28872
|
return $dara.cast(await this.callApi(params, req, runtime), new $_model.UpdateDhcpOptionsSetAttributeResponse({}));
|
|
28743
28873
|
}
|
|
28744
28874
|
/**
|
|
28745
|
-
* Modifies the configuration of a DHCP options set
|
|
28875
|
+
* Modifies the configuration of a DHCP options set.
|
|
28746
28876
|
*
|
|
28747
28877
|
* @param request - UpdateDhcpOptionsSetAttributeRequest
|
|
28748
28878
|
* @returns UpdateDhcpOptionsSetAttributeResponse
|