@alicloud/vpc20160428 7.2.5 → 7.3.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/dist/client.d.ts +195 -104
- package/dist/client.js +239 -136
- 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 +8 -9
- package/dist/models/CreateRouteTargetGroupRequest.js.map +1 -1
- package/dist/models/CreateVirtualPhysicalConnectionRequest.d.ts +9 -9
- package/dist/models/CreateVswitchRequest.d.ts +26 -9
- package/dist/models/CreateVswitchRequest.js +4 -0
- package/dist/models/CreateVswitchRequest.js.map +1 -1
- 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/GetVpcPrefixListAssociationsRequest.d.ts +3 -3
- package/dist/models/GetVpcPrefixListAssociationsResponseBody.d.ts +9 -9
- 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/ModifyVswitchAttributeRequest.d.ts +13 -3
- package/dist/models/ModifyVswitchAttributeRequest.js +2 -0
- package/dist/models/ModifyVswitchAttributeRequest.js.map +1 -1
- 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 +12 -12
- 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 +250 -136
- 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 +8 -9
- package/src/models/CreateVirtualPhysicalConnectionRequest.ts +9 -9
- package/src/models/CreateVswitchRequest.ts +30 -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/GetVpcPrefixListAssociationsRequest.ts +3 -3
- package/src/models/GetVpcPrefixListAssociationsResponseBody.ts +9 -9
- 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/ModifyVswitchAttributeRequest.ts +15 -3
- 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 +12 -12
- package/src/models/UpdateIpv4gatewayAttributeRequest.ts +6 -6
- package/src/models/model.ts +3 -0
package/dist/client.js
CHANGED
|
@@ -86,42 +86,6 @@ class Client extends openapi_core_1.default {
|
|
|
86
86
|
'cn-zhengzhou-nebula-1': "vpc-nebula.cn-qingdao-nebula.aliyuncs.com",
|
|
87
87
|
'eu-west-1-oxs': "vpc-nebula.cn-shenzhen-cloudstone.aliyuncs.com",
|
|
88
88
|
'rus-west-1-pop': "vpc.aliyuncs.com",
|
|
89
|
-
'cn-beijing': "vpc.cn-beijing.aliyuncs.com",
|
|
90
|
-
'cn-heyuan': "vpc.cn-heyuan.aliyuncs.com",
|
|
91
|
-
'cn-zhangjiakou': "vpc.cn-zhangjiakou.aliyuncs.com",
|
|
92
|
-
'ap-northeast-2': "vpc.ap-northeast-2.aliyuncs.com",
|
|
93
|
-
'ap-northeast-1': "vpc.ap-northeast-1.aliyuncs.com",
|
|
94
|
-
'ap-southeast-1': "vpc.ap-southeast-1.aliyuncs.com",
|
|
95
|
-
'ap-southeast-3': "vpc.ap-southeast-3.aliyuncs.com",
|
|
96
|
-
'ap-southeast-5': "vpc.ap-southeast-5.aliyuncs.com",
|
|
97
|
-
'ap-southeast-6': "vpc.ap-southeast-6.aliyuncs.com",
|
|
98
|
-
'ap-southeast-7': "vpc.ap-southeast-7.aliyuncs.com",
|
|
99
|
-
'ap-southeast-8': "vpc.ap-southeast-8.aliyuncs.com",
|
|
100
|
-
'cn-zhongwei': "vpc.cn-zhongwei.aliyuncs.com",
|
|
101
|
-
'cn-wulanchabu': "vpc.cn-wulanchabu.aliyuncs.com",
|
|
102
|
-
'cn-qingdao': "vpc.cn-qingdao.aliyuncs.com",
|
|
103
|
-
'cn-wuhan-lr': "vpc.cn-wuhan-lr.aliyuncs.com",
|
|
104
|
-
'cn-shanghai': "vpc.cn-shanghai.aliyuncs.com",
|
|
105
|
-
'cn-hongkong': "vpc.cn-hongkong.aliyuncs.com",
|
|
106
|
-
'cn-shenzhen': "vpc.cn-shenzhen.aliyuncs.com",
|
|
107
|
-
'cn-nanjing': "vpc.cn-nanjing.aliyuncs.com",
|
|
108
|
-
'cn-fuzhou': "vpc.cn-fuzhou.aliyuncs.com",
|
|
109
|
-
'cn-chengdu': "vpc.cn-chengdu.aliyuncs.com",
|
|
110
|
-
'cn-guangzhou': "vpc.cn-guangzhou.aliyuncs.com",
|
|
111
|
-
'cn-huhehaote': "vpc.cn-huhehaote.aliyuncs.com",
|
|
112
|
-
'us-southeast-1': "vpc.us-southeast-1.aliyuncs.com",
|
|
113
|
-
'eu-west-1': "vpc.eu-west-1.aliyuncs.com",
|
|
114
|
-
'eu-west-2': "vpc.eu-west-2.aliyuncs.com",
|
|
115
|
-
'eu-central-1': "vpc.eu-central-1.aliyuncs.com",
|
|
116
|
-
'us-east-1': "vpc.us-east-1.aliyuncs.com",
|
|
117
|
-
'sa-east-1': "vpc.sa-east-1.aliyuncs.com",
|
|
118
|
-
'us-west-1': "vpc.us-west-1.aliyuncs.com",
|
|
119
|
-
'na-south-1': "vpc.na-south-1.aliyuncs.com",
|
|
120
|
-
'me-east-1': "vpc.me-east-1.aliyuncs.com",
|
|
121
|
-
'me-central-1': "vpc.me-central-1.aliyuncs.com",
|
|
122
|
-
'cn-beijing-finance-1': "vpc.cn-beijing-finance-1.aliyuncs.com",
|
|
123
|
-
'cn-heyuan-acdr-1': "vpc.cn-heyuan-acdr-1.aliyuncs.com",
|
|
124
|
-
'cn-wulanchabu-gic-1': "vpc.cn-wulanchabu-gic-1.aliyuncs.com",
|
|
125
89
|
};
|
|
126
90
|
this.checkConfig(config);
|
|
127
91
|
this._endpoint = this.getEndpoint("vpc", this._regionId, this._endpointRule, this._network, this._suffix, this._endpointMap, this._endpoint);
|
|
@@ -139,7 +103,7 @@ class Client extends openapi_core_1.default {
|
|
|
139
103
|
* Activates a router interface that is in the Inactive state.
|
|
140
104
|
*
|
|
141
105
|
* @remarks
|
|
142
|
-
* After you call the ActivateRouterInterface operation, the router interface enters the **Activating** state
|
|
106
|
+
* 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
107
|
* 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
108
|
* > You cannot activate a router interface that has an overdue payment.
|
|
145
109
|
*
|
|
@@ -185,7 +149,7 @@ class Client extends openapi_core_1.default {
|
|
|
185
149
|
* Activates a router interface that is in the Inactive state.
|
|
186
150
|
*
|
|
187
151
|
* @remarks
|
|
188
|
-
* After you call the ActivateRouterInterface operation, the router interface enters the **Activating** state
|
|
152
|
+
* 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
153
|
* 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
154
|
* > You cannot activate a router interface that has an overdue payment.
|
|
191
155
|
*
|
|
@@ -779,8 +743,8 @@ class Client extends openapi_core_1.default {
|
|
|
779
743
|
* Applies for an elastic IP address (EIP).
|
|
780
744
|
*
|
|
781
745
|
* @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.
|
|
746
|
+
* 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).
|
|
747
|
+
* 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
748
|
*
|
|
785
749
|
* @param request - AllocateEipAddressRequest
|
|
786
750
|
* @param runtime - runtime options for this request RuntimeOptions
|
|
@@ -881,8 +845,8 @@ class Client extends openapi_core_1.default {
|
|
|
881
845
|
* Applies for an elastic IP address (EIP).
|
|
882
846
|
*
|
|
883
847
|
* @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.
|
|
848
|
+
* 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).
|
|
849
|
+
* 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
850
|
*
|
|
887
851
|
* @param request - AllocateEipAddressRequest
|
|
888
852
|
* @returns AllocateEipAddressResponse
|
|
@@ -2395,7 +2359,7 @@ class Client extends openapi_core_1.default {
|
|
|
2395
2359
|
return await this.attachDhcpOptionsSetToVpcWithOptions(request, runtime);
|
|
2396
2360
|
}
|
|
2397
2361
|
/**
|
|
2398
|
-
* Associates a Virtual Border Router (VBR) instance with shared Express Connect circuits.
|
|
2362
|
+
* 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
2363
|
*
|
|
2400
2364
|
* @param request - AttachVbrToVpconnRequest
|
|
2401
2365
|
* @param runtime - runtime options for this request RuntimeOptions
|
|
@@ -2436,7 +2400,7 @@ class Client extends openapi_core_1.default {
|
|
|
2436
2400
|
return $dara.cast(await this.callApi(params, req, runtime), new $_model.AttachVbrToVpconnResponse({}));
|
|
2437
2401
|
}
|
|
2438
2402
|
/**
|
|
2439
|
-
* Associates a Virtual Border Router (VBR) instance with shared Express Connect circuits.
|
|
2403
|
+
* 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
2404
|
*
|
|
2441
2405
|
* @param request - AttachVbrToVpconnRequest
|
|
2442
2406
|
* @returns AttachVbrToVpconnResponse
|
|
@@ -2747,10 +2711,12 @@ class Client extends openapi_core_1.default {
|
|
|
2747
2711
|
return await this.checkVpnBgpEnabledWithOptions(request, runtime);
|
|
2748
2712
|
}
|
|
2749
2713
|
/**
|
|
2750
|
-
*
|
|
2714
|
+
* Calls CompletePhysicalConnectionLOA to complete the construction and backfill the completion information after the LOA is approved and the line construction is finished.
|
|
2751
2715
|
*
|
|
2752
2716
|
* @remarks
|
|
2753
|
-
*
|
|
2717
|
+
* 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**.
|
|
2718
|
+
* Complete call chain:
|
|
2719
|
+
* 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
2720
|
*
|
|
2755
2721
|
* @param request - CompletePhysicalConnectionLOARequest
|
|
2756
2722
|
* @param runtime - runtime options for this request RuntimeOptions
|
|
@@ -2815,10 +2781,12 @@ class Client extends openapi_core_1.default {
|
|
|
2815
2781
|
return $dara.cast(await this.callApi(params, req, runtime), new $_model.CompletePhysicalConnectionLOAResponse({}));
|
|
2816
2782
|
}
|
|
2817
2783
|
/**
|
|
2818
|
-
*
|
|
2784
|
+
* Calls CompletePhysicalConnectionLOA to complete the construction and backfill the completion information after the LOA is approved and the line construction is finished.
|
|
2819
2785
|
*
|
|
2820
2786
|
* @remarks
|
|
2821
|
-
*
|
|
2787
|
+
* 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**.
|
|
2788
|
+
* Complete call chain:
|
|
2789
|
+
* 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
2790
|
*
|
|
2823
2791
|
* @param request - CompletePhysicalConnectionLOARequest
|
|
2824
2792
|
* @returns CompletePhysicalConnectionLOAResponse
|
|
@@ -2885,11 +2853,11 @@ class Client extends openapi_core_1.default {
|
|
|
2885
2853
|
return await this.confirmPhysicalConnectionWithOptions(request, runtime);
|
|
2886
2854
|
}
|
|
2887
2855
|
/**
|
|
2888
|
-
*
|
|
2856
|
+
* Calls the ConnectRouterInterface operation to initiate a connection from the requester VPC router interface to the accepter.
|
|
2889
2857
|
*
|
|
2890
2858
|
* @remarks
|
|
2891
|
-
* After you
|
|
2892
|
-
* When you
|
|
2859
|
+
* After you invoke this operation, the router interface enters the **Connecting** state and transitions to the **Active** state after the connection is established.
|
|
2860
|
+
* When you invoke this operation to create a VPC, note the following items:
|
|
2893
2861
|
* - Only a requester VPC router interface in the **Idle** state can initiate a connection to the accepter VPC.
|
|
2894
2862
|
* - A maximum of one pair of interconnected router interfaces can exist between any two routers.
|
|
2895
2863
|
* - If your account has a router interface with an overdue payment, you cannot initiate a connection.
|
|
@@ -2933,11 +2901,11 @@ class Client extends openapi_core_1.default {
|
|
|
2933
2901
|
return $dara.cast(await this.callApi(params, req, runtime), new $_model.ConnectRouterInterfaceResponse({}));
|
|
2934
2902
|
}
|
|
2935
2903
|
/**
|
|
2936
|
-
*
|
|
2904
|
+
* Calls the ConnectRouterInterface operation to initiate a connection from the requester VPC router interface to the accepter.
|
|
2937
2905
|
*
|
|
2938
2906
|
* @remarks
|
|
2939
|
-
* After you
|
|
2940
|
-
* When you
|
|
2907
|
+
* After you invoke this operation, the router interface enters the **Connecting** state and transitions to the **Active** state after the connection is established.
|
|
2908
|
+
* When you invoke this operation to create a VPC, note the following items:
|
|
2941
2909
|
* - Only a requester VPC router interface in the **Idle** state can initiate a connection to the accepter VPC.
|
|
2942
2910
|
* - A maximum of one pair of interconnected router interfaces can exist between any two routers.
|
|
2943
2911
|
* - If your account has a router interface with an overdue payment, you cannot initiate a connection.
|
|
@@ -4064,18 +4032,28 @@ class Client extends openapi_core_1.default {
|
|
|
4064
4032
|
return await this.createExpressConnectTrafficQosRuleWithOptions(request, runtime);
|
|
4065
4033
|
}
|
|
4066
4034
|
/**
|
|
4067
|
-
*
|
|
4035
|
+
* Calls the CreateFailoverTestJob operation to create a failover test job for Express Connect.
|
|
4068
4036
|
*
|
|
4069
4037
|
* @remarks
|
|
4070
|
-
*
|
|
4071
|
-
* -
|
|
4038
|
+
* Resource status requirements (prerequisites)
|
|
4039
|
+
* - Before creating a failover test job, ensure that the test resources and their associated resources are in the following states. Otherwise, the creation fails:
|
|
4040
|
+
* - 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.
|
|
4041
|
+
* - 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.
|
|
4042
|
+
* - 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.
|
|
4043
|
+
* How to check and advance the Express Connect circuit status
|
|
4044
|
+
* - 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:
|
|
4045
|
+
* - Allocated (port reserved, pending confirmation) → Call ConfirmPhysicalConnection to confirm → Confirmed → Call EnablePhysicalConnection to activate (asynchronous; poll DescribePhysicalConnections after activation to confirm) → Enabled.
|
|
4046
|
+
* - Note: EnablePhysicalConnection only supports activating Express Connect circuits in the Confirmed state. If the circuit is in the Allocated state, call ConfirmPhysicalConnection first.
|
|
4047
|
+
* - 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.
|
|
4048
|
+
* The following scenarios do not support creating failover test jobs:
|
|
4049
|
+
* - 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
4050
|
* - The Express Connect circuit instance or shared Express Connect circuit instance has not been paid for or has an overdue payment.
|
|
4073
4051
|
* - The Express Connect circuit instance or shared Express Connect circuit instance is already in another running failover test job.
|
|
4074
4052
|
*
|
|
4075
4053
|
* - 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
|
|
4054
|
+
* - The Express Connect circuit instance has more than one cross-account VBR.
|
|
4077
4055
|
* - The shared Express Connect circuit instance is not associated with a VBR.
|
|
4078
|
-
* - The VLAN of the shared Express Connect circuit instance is
|
|
4056
|
+
* - The VLAN configuration of the shared Express Connect circuit instance is 0.
|
|
4079
4057
|
*
|
|
4080
4058
|
* @param request - CreateFailoverTestJobRequest
|
|
4081
4059
|
* @param runtime - runtime options for this request RuntimeOptions
|
|
@@ -4140,18 +4118,28 @@ class Client extends openapi_core_1.default {
|
|
|
4140
4118
|
return $dara.cast(await this.callApi(params, req, runtime), new $_model.CreateFailoverTestJobResponse({}));
|
|
4141
4119
|
}
|
|
4142
4120
|
/**
|
|
4143
|
-
*
|
|
4121
|
+
* Calls the CreateFailoverTestJob operation to create a failover test job for Express Connect.
|
|
4144
4122
|
*
|
|
4145
4123
|
* @remarks
|
|
4146
|
-
*
|
|
4147
|
-
* -
|
|
4124
|
+
* Resource status requirements (prerequisites)
|
|
4125
|
+
* - Before creating a failover test job, ensure that the test resources and their associated resources are in the following states. Otherwise, the creation fails:
|
|
4126
|
+
* - 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.
|
|
4127
|
+
* - 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.
|
|
4128
|
+
* - 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.
|
|
4129
|
+
* How to check and advance the Express Connect circuit status
|
|
4130
|
+
* - 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:
|
|
4131
|
+
* - Allocated (port reserved, pending confirmation) → Call ConfirmPhysicalConnection to confirm → Confirmed → Call EnablePhysicalConnection to activate (asynchronous; poll DescribePhysicalConnections after activation to confirm) → Enabled.
|
|
4132
|
+
* - Note: EnablePhysicalConnection only supports activating Express Connect circuits in the Confirmed state. If the circuit is in the Allocated state, call ConfirmPhysicalConnection first.
|
|
4133
|
+
* - 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.
|
|
4134
|
+
* The following scenarios do not support creating failover test jobs:
|
|
4135
|
+
* - 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
4136
|
* - The Express Connect circuit instance or shared Express Connect circuit instance has not been paid for or has an overdue payment.
|
|
4149
4137
|
* - The Express Connect circuit instance or shared Express Connect circuit instance is already in another running failover test job.
|
|
4150
4138
|
*
|
|
4151
4139
|
* - 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
|
|
4140
|
+
* - The Express Connect circuit instance has more than one cross-account VBR.
|
|
4153
4141
|
* - The shared Express Connect circuit instance is not associated with a VBR.
|
|
4154
|
-
* - The VLAN of the shared Express Connect circuit instance is
|
|
4142
|
+
* - The VLAN configuration of the shared Express Connect circuit instance is 0.
|
|
4155
4143
|
*
|
|
4156
4144
|
* @param request - CreateFailoverTestJobRequest
|
|
4157
4145
|
* @returns CreateFailoverTestJobResponse
|
|
@@ -6378,11 +6366,11 @@ class Client extends openapi_core_1.default {
|
|
|
6378
6366
|
* Creates a route target group instance.
|
|
6379
6367
|
*
|
|
6380
6368
|
* @remarks
|
|
6381
|
-
* - **CreateRouteTargetGroup** is an asynchronous operation. After you invoke this operation, the system returns an instance ID, but the routing target group instance is not yet created. The creation
|
|
6369
|
+
* - **CreateRouteTargetGroup** is an asynchronous operation. After you invoke this operation, the system returns an instance ID, but the routing target group instance is not yet created. The creation task continues in the background. You can invoke **ListRouteTargetGroup** to query the creation status of the routing target group:
|
|
6382
6370
|
* - If the routing target group is in the **Pending** state, the routing target group is being created.
|
|
6383
6371
|
* - If the routing target group is in the **Available**, **Unavailable**, **Switched**, or **Abnormal** state, the routing target group is created.
|
|
6384
|
-
* - **Active/standby
|
|
6385
|
-
* - **Primary instance**: The weight is 100. The primary instance handles all traffic under normal conditions and takes effect when health checks
|
|
6372
|
+
* - **Active/standby mode**: When you create a routing target group, configure primary and secondary instances that are in different zones and of the same type.
|
|
6373
|
+
* - **Primary instance**: The weight is 100. The primary instance handles all traffic under normal conditions and takes effect when health checks are successful.
|
|
6386
6374
|
* - **Secondary instance**: The weight is 0. The secondary instance takes over traffic when the primary instance fails, serving as disaster recovery and backup.
|
|
6387
6375
|
*
|
|
6388
6376
|
* @param request - CreateRouteTargetGroupRequest
|
|
@@ -6439,11 +6427,11 @@ class Client extends openapi_core_1.default {
|
|
|
6439
6427
|
* Creates a route target group instance.
|
|
6440
6428
|
*
|
|
6441
6429
|
* @remarks
|
|
6442
|
-
* - **CreateRouteTargetGroup** is an asynchronous operation. After you invoke this operation, the system returns an instance ID, but the routing target group instance is not yet created. The creation
|
|
6430
|
+
* - **CreateRouteTargetGroup** is an asynchronous operation. After you invoke this operation, the system returns an instance ID, but the routing target group instance is not yet created. The creation task continues in the background. You can invoke **ListRouteTargetGroup** to query the creation status of the routing target group:
|
|
6443
6431
|
* - If the routing target group is in the **Pending** state, the routing target group is being created.
|
|
6444
6432
|
* - If the routing target group is in the **Available**, **Unavailable**, **Switched**, or **Abnormal** state, the routing target group is created.
|
|
6445
|
-
* - **Active/standby
|
|
6446
|
-
* - **Primary instance**: The weight is 100. The primary instance handles all traffic under normal conditions and takes effect when health checks
|
|
6433
|
+
* - **Active/standby mode**: When you create a routing target group, configure primary and secondary instances that are in different zones and of the same type.
|
|
6434
|
+
* - **Primary instance**: The weight is 100. The primary instance handles all traffic under normal conditions and takes effect when health checks are successful.
|
|
6447
6435
|
* - **Secondary instance**: The weight is 0. The secondary instance takes over traffic when the primary instance fails, serving as disaster recovery and backup.
|
|
6448
6436
|
*
|
|
6449
6437
|
* @param request - CreateRouteTargetGroupRequest
|
|
@@ -7151,7 +7139,7 @@ class Client extends openapi_core_1.default {
|
|
|
7151
7139
|
* @remarks
|
|
7152
7140
|
* When you call this operation to create a vSwitch, take note of the following items:
|
|
7153
7141
|
* - The number of vSwitches in each VPC cannot exceed 150.
|
|
7154
|
-
* - The first
|
|
7142
|
+
* - The first and last three IP addresses of each vSwitch CIDR block are reserved by the system. For example, the system reserved IP addresses of 192.168.1.0/24 are 192.168.1.0, 192.168.1.253, 192.168.1.254, and 192.168.1.255.
|
|
7155
7143
|
* - The number of cloud service instances in a vSwitch cannot exceed the remaining available cloud service instances in the VPC (15,000 minus the current number of cloud service instances).
|
|
7156
7144
|
* - A cloud service instance can belong to only one vSwitch.
|
|
7157
7145
|
* - vSwitches do not support multicast or broadcast.
|
|
@@ -7172,6 +7160,9 @@ class Client extends openapi_core_1.default {
|
|
|
7172
7160
|
if (!$dara.isNull(request.cidrBlock)) {
|
|
7173
7161
|
query["CidrBlock"] = request.cidrBlock;
|
|
7174
7162
|
}
|
|
7163
|
+
if (!$dara.isNull(request.cidrMask)) {
|
|
7164
|
+
query["CidrMask"] = request.cidrMask;
|
|
7165
|
+
}
|
|
7175
7166
|
if (!$dara.isNull(request.clientToken)) {
|
|
7176
7167
|
query["ClientToken"] = request.clientToken;
|
|
7177
7168
|
}
|
|
@@ -7181,6 +7172,9 @@ class Client extends openapi_core_1.default {
|
|
|
7181
7172
|
if (!$dara.isNull(request.ipv6CidrBlock)) {
|
|
7182
7173
|
query["Ipv6CidrBlock"] = request.ipv6CidrBlock;
|
|
7183
7174
|
}
|
|
7175
|
+
if (!$dara.isNull(request.ipv6CidrMask)) {
|
|
7176
|
+
query["Ipv6CidrMask"] = request.ipv6CidrMask;
|
|
7177
|
+
}
|
|
7184
7178
|
if (!$dara.isNull(request.ownerAccount)) {
|
|
7185
7179
|
query["OwnerAccount"] = request.ownerAccount;
|
|
7186
7180
|
}
|
|
@@ -7233,7 +7227,7 @@ class Client extends openapi_core_1.default {
|
|
|
7233
7227
|
* @remarks
|
|
7234
7228
|
* When you call this operation to create a vSwitch, take note of the following items:
|
|
7235
7229
|
* - The number of vSwitches in each VPC cannot exceed 150.
|
|
7236
|
-
* - The first
|
|
7230
|
+
* - The first and last three IP addresses of each vSwitch CIDR block are reserved by the system. For example, the system reserved IP addresses of 192.168.1.0/24 are 192.168.1.0, 192.168.1.253, 192.168.1.254, and 192.168.1.255.
|
|
7237
7231
|
* - The number of cloud service instances in a vSwitch cannot exceed the remaining available cloud service instances in the VPC (15,000 minus the current number of cloud service instances).
|
|
7238
7232
|
* - A cloud service instance can belong to only one vSwitch.
|
|
7239
7233
|
* - vSwitches do not support multicast or broadcast.
|
|
@@ -7626,7 +7620,18 @@ class Client extends openapi_core_1.default {
|
|
|
7626
7620
|
* Invokes the CreateVirtualPhysicalConnection operation to create shared Express Connect circuits.
|
|
7627
7621
|
*
|
|
7628
7622
|
* @remarks
|
|
7629
|
-
* Before
|
|
7623
|
+
* 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).
|
|
7624
|
+
* Before you call this operation, make sure the following conditions are met:
|
|
7625
|
+
* - 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:
|
|
7626
|
+
* - CreatePhysicalConnection: Creates an Express Connect circuit.
|
|
7627
|
+
* - 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.
|
|
7628
|
+
* - ConfirmPhysicalConnection: Reports construction completion. The circuit must be in the Allocated state. After success, it enters the Confirmed state.
|
|
7629
|
+
* - 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.
|
|
7630
|
+
* - 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).
|
|
7631
|
+
* - 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.
|
|
7632
|
+
* - VpconnAliUid is the tenant\\"s Alibaba Cloud account (RAM users or partner accounts are not supported). Cross-site pushing is not allowed by default.
|
|
7633
|
+
* - The number of shared Express Connect circuits on a single Express Connect circuit has not exceeded the quota.
|
|
7634
|
+
* - 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
7635
|
*
|
|
7631
7636
|
* @param request - CreateVirtualPhysicalConnectionRequest
|
|
7632
7637
|
* @param runtime - runtime options for this request RuntimeOptions
|
|
@@ -7691,7 +7696,18 @@ class Client extends openapi_core_1.default {
|
|
|
7691
7696
|
* Invokes the CreateVirtualPhysicalConnection operation to create shared Express Connect circuits.
|
|
7692
7697
|
*
|
|
7693
7698
|
* @remarks
|
|
7694
|
-
* Before
|
|
7699
|
+
* 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).
|
|
7700
|
+
* Before you call this operation, make sure the following conditions are met:
|
|
7701
|
+
* - 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:
|
|
7702
|
+
* - CreatePhysicalConnection: Creates an Express Connect circuit.
|
|
7703
|
+
* - 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.
|
|
7704
|
+
* - ConfirmPhysicalConnection: Reports construction completion. The circuit must be in the Allocated state. After success, it enters the Confirmed state.
|
|
7705
|
+
* - 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.
|
|
7706
|
+
* - 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).
|
|
7707
|
+
* - 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.
|
|
7708
|
+
* - VpconnAliUid is the tenant\\"s Alibaba Cloud account (RAM users or partner accounts are not supported). Cross-site pushing is not allowed by default.
|
|
7709
|
+
* - The number of shared Express Connect circuits on a single Express Connect circuit has not exceeded the quota.
|
|
7710
|
+
* - 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
7711
|
*
|
|
7696
7712
|
* @param request - CreateVirtualPhysicalConnectionRequest
|
|
7697
7713
|
* @returns CreateVirtualPhysicalConnectionResponse
|
|
@@ -8818,6 +8834,9 @@ class Client extends openapi_core_1.default {
|
|
|
8818
8834
|
/**
|
|
8819
8835
|
* Deletes an advertised Border Gateway Protocol (BGP) network.
|
|
8820
8836
|
*
|
|
8837
|
+
* @remarks
|
|
8838
|
+
* 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.
|
|
8839
|
+
*
|
|
8821
8840
|
* @param request - DeleteBgpNetworkRequest
|
|
8822
8841
|
* @param runtime - runtime options for this request RuntimeOptions
|
|
8823
8842
|
* @returns DeleteBgpNetworkResponse
|
|
@@ -8868,6 +8887,9 @@ class Client extends openapi_core_1.default {
|
|
|
8868
8887
|
/**
|
|
8869
8888
|
* Deletes an advertised Border Gateway Protocol (BGP) network.
|
|
8870
8889
|
*
|
|
8890
|
+
* @remarks
|
|
8891
|
+
* 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.
|
|
8892
|
+
*
|
|
8871
8893
|
* @param request - DeleteBgpNetworkRequest
|
|
8872
8894
|
* @returns DeleteBgpNetworkResponse
|
|
8873
8895
|
*/
|
|
@@ -10759,11 +10781,11 @@ class Client extends openapi_core_1.default {
|
|
|
10759
10781
|
*
|
|
10760
10782
|
* @remarks
|
|
10761
10783
|
* Before you call this operation, take note of the following items:
|
|
10762
|
-
* - Before
|
|
10784
|
+
* - Before you delete an IP address pool, make sure that the IP addresses in the pool are not in use.
|
|
10763
10785
|
* - **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
10786
|
* - 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
10787
|
* - If the IP address pool cannot be found, the IP address pool is deleted.
|
|
10766
|
-
* - **DeletePublicIpAddressPool**
|
|
10788
|
+
* - You cannot call **DeletePublicIpAddressPool** to concurrently delete the same IP address pool.
|
|
10767
10789
|
*
|
|
10768
10790
|
* @param request - DeletePublicIpAddressPoolRequest
|
|
10769
10791
|
* @param runtime - runtime options for this request RuntimeOptions
|
|
@@ -10817,11 +10839,11 @@ class Client extends openapi_core_1.default {
|
|
|
10817
10839
|
*
|
|
10818
10840
|
* @remarks
|
|
10819
10841
|
* Before you call this operation, take note of the following items:
|
|
10820
|
-
* - Before
|
|
10842
|
+
* - Before you delete an IP address pool, make sure that the IP addresses in the pool are not in use.
|
|
10821
10843
|
* - **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
10844
|
* - 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
10845
|
* - If the IP address pool cannot be found, the IP address pool is deleted.
|
|
10824
|
-
* - **DeletePublicIpAddressPool**
|
|
10846
|
+
* - You cannot call **DeletePublicIpAddressPool** to concurrently delete the same IP address pool.
|
|
10825
10847
|
*
|
|
10826
10848
|
* @param request - DeletePublicIpAddressPoolRequest
|
|
10827
10849
|
* @returns DeletePublicIpAddressPoolResponse
|
|
@@ -10836,7 +10858,7 @@ class Client extends openapi_core_1.default {
|
|
|
10836
10858
|
* @remarks
|
|
10837
10859
|
* Before you call this operation, take note of the following information:
|
|
10838
10860
|
* - 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
|
|
10861
|
+
* - **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
10862
|
* - 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
10863
|
* - If the CIDR block cannot be found, the CIDR block is deleted.
|
|
10842
10864
|
* - The **DeletePublicIpAddressPoolCidrBlock** operation does not support concurrent deletion of the same CIDR block.
|
|
@@ -10897,7 +10919,7 @@ class Client extends openapi_core_1.default {
|
|
|
10897
10919
|
* @remarks
|
|
10898
10920
|
* Before you call this operation, take note of the following information:
|
|
10899
10921
|
* - 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
|
|
10922
|
+
* - **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
10923
|
* - 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
10924
|
* - If the CIDR block cannot be found, the CIDR block is deleted.
|
|
10903
10925
|
* - The **DeletePublicIpAddressPoolCidrBlock** operation does not support concurrent deletion of the same CIDR block.
|
|
@@ -10910,16 +10932,16 @@ class Client extends openapi_core_1.default {
|
|
|
10910
10932
|
return await this.deletePublicIpAddressPoolCidrBlockWithOptions(request, runtime);
|
|
10911
10933
|
}
|
|
10912
10934
|
/**
|
|
10913
|
-
*
|
|
10935
|
+
* Calls DeleteRouteEntries to batch delete custom route entries.
|
|
10914
10936
|
*
|
|
10915
10937
|
* @remarks
|
|
10916
10938
|
* When you call this operation to delete routing entries, note the following items:
|
|
10917
10939
|
* - 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
|
|
10940
|
+
* - Routing entries cannot be deleted if the VPC that contains the route table is creating or deleting a vSwitch or routing entry.
|
|
10941
|
+
* - 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:
|
|
10942
|
+
* - If the routing entry is in the **Deleting** state, the routing entry is being deleted.
|
|
10943
|
+
* - If the specified routing entry cannot be found, the routing entry is deleted.
|
|
10944
|
+
* - The **DeleteRouteEntries** operation does not support concurrent batch deletion of routing entries in route tables within the same VPC.
|
|
10923
10945
|
*
|
|
10924
10946
|
* @param request - DeleteRouteEntriesRequest
|
|
10925
10947
|
* @param runtime - runtime options for this request RuntimeOptions
|
|
@@ -10969,16 +10991,16 @@ class Client extends openapi_core_1.default {
|
|
|
10969
10991
|
return $dara.cast(await this.callApi(params, req, runtime), new $_model.DeleteRouteEntriesResponse({}));
|
|
10970
10992
|
}
|
|
10971
10993
|
/**
|
|
10972
|
-
*
|
|
10994
|
+
* Calls DeleteRouteEntries to batch delete custom route entries.
|
|
10973
10995
|
*
|
|
10974
10996
|
* @remarks
|
|
10975
10997
|
* When you call this operation to delete routing entries, note the following items:
|
|
10976
10998
|
* - 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
|
|
10999
|
+
* - Routing entries cannot be deleted if the VPC that contains the route table is creating or deleting a vSwitch or routing entry.
|
|
11000
|
+
* - 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:
|
|
11001
|
+
* - If the routing entry is in the **Deleting** state, the routing entry is being deleted.
|
|
11002
|
+
* - If the specified routing entry cannot be found, the routing entry is deleted.
|
|
11003
|
+
* - The **DeleteRouteEntries** operation does not support concurrent batch deletion of routing entries in route tables within the same VPC.
|
|
10982
11004
|
*
|
|
10983
11005
|
* @param request - DeleteRouteEntriesRequest
|
|
10984
11006
|
* @returns DeleteRouteEntriesResponse
|
|
@@ -15411,7 +15433,7 @@ class Client extends openapi_core_1.default {
|
|
|
15411
15433
|
* Queries information about Express Connect circuits in a specified region.
|
|
15412
15434
|
*
|
|
15413
15435
|
* @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
|
|
15436
|
+
* 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
15437
|
*
|
|
15416
15438
|
* @param request - DescribePhysicalConnectionsRequest
|
|
15417
15439
|
* @param runtime - runtime options for this request RuntimeOptions
|
|
@@ -15476,7 +15498,7 @@ class Client extends openapi_core_1.default {
|
|
|
15476
15498
|
* Queries information about Express Connect circuits in a specified region.
|
|
15477
15499
|
*
|
|
15478
15500
|
* @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
|
|
15501
|
+
* 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
15502
|
*
|
|
15481
15503
|
* @param request - DescribePhysicalConnectionsRequest
|
|
15482
15504
|
* @returns DescribePhysicalConnectionsResponse
|
|
@@ -15920,7 +15942,7 @@ class Client extends openapi_core_1.default {
|
|
|
15920
15942
|
return await this.describeRouterInterfaceAttributeWithOptions(request, runtime);
|
|
15921
15943
|
}
|
|
15922
15944
|
/**
|
|
15923
|
-
* Queries router interfaces in a specified region
|
|
15945
|
+
* Queries router interfaces in a specified region.
|
|
15924
15946
|
*
|
|
15925
15947
|
* @param request - DescribeRouterInterfacesRequest
|
|
15926
15948
|
* @param runtime - runtime options for this request RuntimeOptions
|
|
@@ -15976,7 +15998,7 @@ class Client extends openapi_core_1.default {
|
|
|
15976
15998
|
return $dara.cast(await this.callApi(params, req, runtime), new $_model.DescribeRouterInterfacesResponse({}));
|
|
15977
15999
|
}
|
|
15978
16000
|
/**
|
|
15979
|
-
* Queries router interfaces in a specified region
|
|
16001
|
+
* Queries router interfaces in a specified region.
|
|
15980
16002
|
*
|
|
15981
16003
|
* @param request - DescribeRouterInterfacesRequest
|
|
15982
16004
|
* @returns DescribeRouterInterfacesResponse
|
|
@@ -17203,7 +17225,7 @@ class Client extends openapi_core_1.default {
|
|
|
17203
17225
|
* Queries created VPCs.
|
|
17204
17226
|
*
|
|
17205
17227
|
* @remarks
|
|
17206
|
-
* The **DescribeVpcs** operation may return the **Throttling.DeepPageSkip** error code during frequent deep paging
|
|
17228
|
+
* 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
17229
|
*
|
|
17208
17230
|
* @param request - DescribeVpcsRequest
|
|
17209
17231
|
* @param runtime - runtime options for this request RuntimeOptions
|
|
@@ -17280,7 +17302,7 @@ class Client extends openapi_core_1.default {
|
|
|
17280
17302
|
* Queries created VPCs.
|
|
17281
17303
|
*
|
|
17282
17304
|
* @remarks
|
|
17283
|
-
* The **DescribeVpcs** operation may return the **Throttling.DeepPageSkip** error code during frequent deep paging
|
|
17305
|
+
* 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
17306
|
*
|
|
17285
17307
|
* @param request - DescribeVpcsRequest
|
|
17286
17308
|
* @returns DescribeVpcsResponse
|
|
@@ -18609,11 +18631,12 @@ class Client extends openapi_core_1.default {
|
|
|
18609
18631
|
* Enables an Express Connect circuit that is in the Confirmed state. After the circuit is enabled, it enters the Enabled state.
|
|
18610
18632
|
*
|
|
18611
18633
|
* @remarks
|
|
18612
|
-
* When you
|
|
18613
|
-
* - You can enable only an Express Connect circuit that is in the
|
|
18614
|
-
* -
|
|
18615
|
-
* -
|
|
18616
|
-
* -
|
|
18634
|
+
* When you invoke this operation, note the following items:
|
|
18635
|
+
* - 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).
|
|
18636
|
+
* - 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.
|
|
18637
|
+
* - 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.
|
|
18638
|
+
* - 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.
|
|
18639
|
+
* If the Express Connect circuit is already in the Enabled state, invoking this operation again returns a success response (idempotent).
|
|
18617
18640
|
*
|
|
18618
18641
|
* @param request - EnablePhysicalConnectionRequest
|
|
18619
18642
|
* @param runtime - runtime options for this request RuntimeOptions
|
|
@@ -18666,11 +18689,12 @@ class Client extends openapi_core_1.default {
|
|
|
18666
18689
|
* Enables an Express Connect circuit that is in the Confirmed state. After the circuit is enabled, it enters the Enabled state.
|
|
18667
18690
|
*
|
|
18668
18691
|
* @remarks
|
|
18669
|
-
* When you
|
|
18670
|
-
* - You can enable only an Express Connect circuit that is in the
|
|
18671
|
-
* -
|
|
18672
|
-
* -
|
|
18673
|
-
* -
|
|
18692
|
+
* When you invoke this operation, note the following items:
|
|
18693
|
+
* - 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).
|
|
18694
|
+
* - 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.
|
|
18695
|
+
* - 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.
|
|
18696
|
+
* - 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.
|
|
18697
|
+
* If the Express Connect circuit is already in the Enabled state, invoking this operation again returns a success response (idempotent).
|
|
18674
18698
|
*
|
|
18675
18699
|
* @param request - EnablePhysicalConnectionRequest
|
|
18676
18700
|
* @returns EnablePhysicalConnectionResponse
|
|
@@ -18991,7 +19015,7 @@ class Client extends openapi_core_1.default {
|
|
|
18991
19015
|
* Queries the information about a single NAT gateway instance.
|
|
18992
19016
|
*
|
|
18993
19017
|
* @remarks
|
|
18994
|
-
* This operation queries the information about a single Internet NAT gateway or VPC NAT gateway. The term "NAT gateway" in this topic
|
|
19018
|
+
* 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
19019
|
*
|
|
18996
19020
|
* @param request - GetNatGatewayAttributeRequest
|
|
18997
19021
|
* @param runtime - runtime options for this request RuntimeOptions
|
|
@@ -19041,7 +19065,7 @@ class Client extends openapi_core_1.default {
|
|
|
19041
19065
|
* Queries the information about a single NAT gateway instance.
|
|
19042
19066
|
*
|
|
19043
19067
|
* @remarks
|
|
19044
|
-
* This operation queries the information about a single Internet NAT gateway or VPC NAT gateway. The term "NAT gateway" in this topic
|
|
19068
|
+
* 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
19069
|
*
|
|
19046
19070
|
* @param request - GetNatGatewayAttributeRequest
|
|
19047
19071
|
* @returns GetNatGatewayAttributeResponse
|
|
@@ -19705,7 +19729,18 @@ class Client extends openapi_core_1.default {
|
|
|
19705
19729
|
* Invokes the GrantInstanceToVbr operation to grant authorization of a VPC-connected instance to a VBR instance for cross-account VBR uplink scenarios.
|
|
19706
19730
|
*
|
|
19707
19731
|
* @remarks
|
|
19708
|
-
*
|
|
19732
|
+
* This operation is used for cross-account scenarios. Before calling this operation, ensure that the following resources are ready:
|
|
19733
|
+
* **Account A (VPC owner, the caller of this operation):**
|
|
19734
|
+
* - A VPC has been created and is in the Available state (CreateVpc).
|
|
19735
|
+
* **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:
|
|
19736
|
+
* 1. Call CreatePhysicalConnection to create an Express Connect circuit.
|
|
19737
|
+
* 2. Apply for a Letter of Authorization (LOA) and complete the construction (ApplyPhysicalConnectionLOA → CompletePhysicalConnectionLOA). The Express Connect circuit enters the Confirmed state.
|
|
19738
|
+
* 3. Call EnablePhysicalConnection to enable the Express Connect circuit (the circuit must be in the Confirmed state).
|
|
19739
|
+
* 4. Call CreateVirtualBorderRouter to create a VBR (the Express Connect circuit must be in the Enabled state. Otherwise, the error InvalidPhysicalConnectionId.NotEnabled is returned).
|
|
19740
|
+
* After the preceding preparations are complete, Account A calls this operation to grant the VPC to the VBR of Account B:
|
|
19741
|
+
* - 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).
|
|
19742
|
+
* - 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.
|
|
19743
|
+
* Note: VbrOwnerUid cannot be the same as the caller\\"s account. Otherwise, the error Parameter.Illegal is returned.
|
|
19709
19744
|
*
|
|
19710
19745
|
* @param tmpReq - GrantInstanceToVbrRequest
|
|
19711
19746
|
* @param runtime - runtime options for this request RuntimeOptions
|
|
@@ -19757,7 +19792,18 @@ class Client extends openapi_core_1.default {
|
|
|
19757
19792
|
* Invokes the GrantInstanceToVbr operation to grant authorization of a VPC-connected instance to a VBR instance for cross-account VBR uplink scenarios.
|
|
19758
19793
|
*
|
|
19759
19794
|
* @remarks
|
|
19760
|
-
*
|
|
19795
|
+
* This operation is used for cross-account scenarios. Before calling this operation, ensure that the following resources are ready:
|
|
19796
|
+
* **Account A (VPC owner, the caller of this operation):**
|
|
19797
|
+
* - A VPC has been created and is in the Available state (CreateVpc).
|
|
19798
|
+
* **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:
|
|
19799
|
+
* 1. Call CreatePhysicalConnection to create an Express Connect circuit.
|
|
19800
|
+
* 2. Apply for a Letter of Authorization (LOA) and complete the construction (ApplyPhysicalConnectionLOA → CompletePhysicalConnectionLOA). The Express Connect circuit enters the Confirmed state.
|
|
19801
|
+
* 3. Call EnablePhysicalConnection to enable the Express Connect circuit (the circuit must be in the Confirmed state).
|
|
19802
|
+
* 4. Call CreateVirtualBorderRouter to create a VBR (the Express Connect circuit must be in the Enabled state. Otherwise, the error InvalidPhysicalConnectionId.NotEnabled is returned).
|
|
19803
|
+
* After the preceding preparations are complete, Account A calls this operation to grant the VPC to the VBR of Account B:
|
|
19804
|
+
* - 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).
|
|
19805
|
+
* - 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.
|
|
19806
|
+
* Note: VbrOwnerUid cannot be the same as the caller\\"s account. Otherwise, the error Parameter.Illegal is returned.
|
|
19761
19807
|
*
|
|
19762
19808
|
* @param request - GrantInstanceToVbrRequest
|
|
19763
19809
|
* @returns GrantInstanceToVbrResponse
|
|
@@ -21248,7 +21294,7 @@ class Client extends openapi_core_1.default {
|
|
|
21248
21294
|
return await this.listVSwitchCidrReservationsWithOptions(request, runtime);
|
|
21249
21295
|
}
|
|
21250
21296
|
/**
|
|
21251
|
-
* Queries information about shared Express Connect circuits
|
|
21297
|
+
* Queries information about shared Express Connect circuits.
|
|
21252
21298
|
*
|
|
21253
21299
|
* @param request - ListVirtualPhysicalConnectionsRequest
|
|
21254
21300
|
* @param runtime - runtime options for this request RuntimeOptions
|
|
@@ -21310,7 +21356,7 @@ class Client extends openapi_core_1.default {
|
|
|
21310
21356
|
return $dara.cast(await this.callApi(params, req, runtime), new $_model.ListVirtualPhysicalConnectionsResponse({}));
|
|
21311
21357
|
}
|
|
21312
21358
|
/**
|
|
21313
|
-
* Queries information about shared Express Connect circuits
|
|
21359
|
+
* Queries information about shared Express Connect circuits.
|
|
21314
21360
|
*
|
|
21315
21361
|
* @param request - ListVirtualPhysicalConnectionsRequest
|
|
21316
21362
|
* @returns ListVirtualPhysicalConnectionsResponse
|
|
@@ -23951,13 +23997,13 @@ class Client extends openapi_core_1.default {
|
|
|
23951
23997
|
return await this.modifyNetworkAclAttributesWithOptions(request, runtime);
|
|
23952
23998
|
}
|
|
23953
23999
|
/**
|
|
23954
|
-
* Modifies the
|
|
24000
|
+
* Modifies the configurations of an Express Connect circuit.
|
|
23955
24001
|
*
|
|
23956
24002
|
* @remarks
|
|
23957
24003
|
* When you call this operation, note the following items:
|
|
23958
24004
|
* - You can modify the specifications and redundant circuit ID only for Express Connect circuits in the **Initial**, **Enabled**, or **Rejected** state.
|
|
23959
24005
|
* - You cannot modify Express Connect circuits in the **Canceled**, **Allocating**, **AllocationFailed**, or **Terminated** state.
|
|
23960
|
-
* -
|
|
24006
|
+
* - After an Express Connect circuit in the **Rejected** state is modified, it enters the **Initial** state.
|
|
23961
24007
|
*
|
|
23962
24008
|
* @param request - ModifyPhysicalConnectionAttributeRequest
|
|
23963
24009
|
* @param runtime - runtime options for this request RuntimeOptions
|
|
@@ -24034,13 +24080,13 @@ class Client extends openapi_core_1.default {
|
|
|
24034
24080
|
return $dara.cast(await this.callApi(params, req, runtime), new $_model.ModifyPhysicalConnectionAttributeResponse({}));
|
|
24035
24081
|
}
|
|
24036
24082
|
/**
|
|
24037
|
-
* Modifies the
|
|
24083
|
+
* Modifies the configurations of an Express Connect circuit.
|
|
24038
24084
|
*
|
|
24039
24085
|
* @remarks
|
|
24040
24086
|
* When you call this operation, note the following items:
|
|
24041
24087
|
* - You can modify the specifications and redundant circuit ID only for Express Connect circuits in the **Initial**, **Enabled**, or **Rejected** state.
|
|
24042
24088
|
* - You cannot modify Express Connect circuits in the **Canceled**, **Allocating**, **AllocationFailed**, or **Terminated** state.
|
|
24043
|
-
* -
|
|
24089
|
+
* - After an Express Connect circuit in the **Rejected** state is modified, it enters the **Initial** state.
|
|
24044
24090
|
*
|
|
24045
24091
|
* @param request - ModifyPhysicalConnectionAttributeRequest
|
|
24046
24092
|
* @returns ModifyPhysicalConnectionAttributeResponse
|
|
@@ -24776,6 +24822,9 @@ class Client extends openapi_core_1.default {
|
|
|
24776
24822
|
if (!$dara.isNull(request.ipv6CidrBlock)) {
|
|
24777
24823
|
query["Ipv6CidrBlock"] = request.ipv6CidrBlock;
|
|
24778
24824
|
}
|
|
24825
|
+
if (!$dara.isNull(request.ipv6CidrMask)) {
|
|
24826
|
+
query["Ipv6CidrMask"] = request.ipv6CidrMask;
|
|
24827
|
+
}
|
|
24779
24828
|
if (!$dara.isNull(request.ownerAccount)) {
|
|
24780
24829
|
query["OwnerAccount"] = request.ownerAccount;
|
|
24781
24830
|
}
|
|
@@ -25195,6 +25244,60 @@ class Client extends openapi_core_1.default {
|
|
|
25195
25244
|
let runtime = new $dara.RuntimeOptions({});
|
|
25196
25245
|
return await this.modifyVpcAttributeWithOptions(request, runtime);
|
|
25197
25246
|
}
|
|
25247
|
+
/**
|
|
25248
|
+
* Modifies the primary or secondary CIDR block of a VPC.
|
|
25249
|
+
*
|
|
25250
|
+
* @param request - ModifyVpcCidrBlockRequest
|
|
25251
|
+
* @param runtime - runtime options for this request RuntimeOptions
|
|
25252
|
+
* @returns ModifyVpcCidrBlockResponse
|
|
25253
|
+
*/
|
|
25254
|
+
async modifyVpcCidrBlockWithOptions(request, runtime) {
|
|
25255
|
+
request.validate();
|
|
25256
|
+
let query = {};
|
|
25257
|
+
if (!$dara.isNull(request.clientToken)) {
|
|
25258
|
+
query["ClientToken"] = request.clientToken;
|
|
25259
|
+
}
|
|
25260
|
+
if (!$dara.isNull(request.dryRun)) {
|
|
25261
|
+
query["DryRun"] = request.dryRun;
|
|
25262
|
+
}
|
|
25263
|
+
if (!$dara.isNull(request.originalCidrBlock)) {
|
|
25264
|
+
query["OriginalCidrBlock"] = request.originalCidrBlock;
|
|
25265
|
+
}
|
|
25266
|
+
if (!$dara.isNull(request.regionId)) {
|
|
25267
|
+
query["RegionId"] = request.regionId;
|
|
25268
|
+
}
|
|
25269
|
+
if (!$dara.isNull(request.targetCidrBlock)) {
|
|
25270
|
+
query["TargetCidrBlock"] = request.targetCidrBlock;
|
|
25271
|
+
}
|
|
25272
|
+
if (!$dara.isNull(request.vpcId)) {
|
|
25273
|
+
query["VpcId"] = request.vpcId;
|
|
25274
|
+
}
|
|
25275
|
+
let req = new openapi_core_2.$OpenApiUtil.OpenApiRequest({
|
|
25276
|
+
query: openapi_core_2.OpenApiUtil.query(query),
|
|
25277
|
+
});
|
|
25278
|
+
let params = new openapi_core_2.$OpenApiUtil.Params({
|
|
25279
|
+
action: "ModifyVpcCidrBlock",
|
|
25280
|
+
version: "2016-04-28",
|
|
25281
|
+
protocol: "HTTPS",
|
|
25282
|
+
pathname: "/",
|
|
25283
|
+
method: "POST",
|
|
25284
|
+
authType: "AK",
|
|
25285
|
+
style: "RPC",
|
|
25286
|
+
reqBodyType: "formData",
|
|
25287
|
+
bodyType: "json",
|
|
25288
|
+
});
|
|
25289
|
+
return $dara.cast(await this.callApi(params, req, runtime), new $_model.ModifyVpcCidrBlockResponse({}));
|
|
25290
|
+
}
|
|
25291
|
+
/**
|
|
25292
|
+
* Modifies the primary or secondary CIDR block of a VPC.
|
|
25293
|
+
*
|
|
25294
|
+
* @param request - ModifyVpcCidrBlockRequest
|
|
25295
|
+
* @returns ModifyVpcCidrBlockResponse
|
|
25296
|
+
*/
|
|
25297
|
+
async modifyVpcCidrBlock(request) {
|
|
25298
|
+
let runtime = new $dara.RuntimeOptions({});
|
|
25299
|
+
return await this.modifyVpcCidrBlockWithOptions(request, runtime);
|
|
25300
|
+
}
|
|
25198
25301
|
/**
|
|
25199
25302
|
* Modifies the configuration of a prefix list.
|
|
25200
25303
|
*
|
|
@@ -25976,7 +26079,7 @@ class Client extends openapi_core_1.default {
|
|
|
25976
26079
|
* Modifies the resource group to which a cloud resource belongs.
|
|
25977
26080
|
*
|
|
25978
26081
|
* @remarks
|
|
25979
|
-
* The **ChangeResourceGroup** operation does not support concurrent modifications
|
|
26082
|
+
* 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
26083
|
*
|
|
25981
26084
|
* @param request - MoveResourceGroupRequest
|
|
25982
26085
|
* @param runtime - runtime options for this request RuntimeOptions
|
|
@@ -26029,7 +26132,7 @@ class Client extends openapi_core_1.default {
|
|
|
26029
26132
|
* Modifies the resource group to which a cloud resource belongs.
|
|
26030
26133
|
*
|
|
26031
26134
|
* @remarks
|
|
26032
|
-
* The **ChangeResourceGroup** operation does not support concurrent modifications
|
|
26135
|
+
* 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
26136
|
*
|
|
26034
26137
|
* @param request - MoveResourceGroupRequest
|
|
26035
26138
|
* @returns MoveResourceGroupResponse
|
|
@@ -26605,16 +26708,16 @@ class Client extends openapi_core_1.default {
|
|
|
26605
26708
|
return await this.recoverVirtualBorderRouterWithOptions(request, runtime);
|
|
26606
26709
|
}
|
|
26607
26710
|
/**
|
|
26608
|
-
* Releases a specified
|
|
26711
|
+
* Releases a specified elastic IP address (EIP).
|
|
26609
26712
|
*
|
|
26610
26713
|
* @remarks
|
|
26611
|
-
* Before you invoke this operation, take note of the following
|
|
26612
|
-
* - Before
|
|
26714
|
+
* Before you invoke this operation, take note of the following information:
|
|
26715
|
+
* - Before you release an EIP, make sure that the following conditions are met:
|
|
26613
26716
|
* - Only EIPs in the **Available** state can be released.
|
|
26614
26717
|
* - 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
|
|
26718
|
+
* - 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:
|
|
26719
|
+
* - 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.
|
|
26720
|
+
* - If the EIP instance cannot be found, the EIP instance is released.
|
|
26618
26721
|
* - The **ReleaseEipAddress** operation does not support concurrent release of the same EIP instance.
|
|
26619
26722
|
*
|
|
26620
26723
|
* @param request - ReleaseEipAddressRequest
|
|
@@ -26659,16 +26762,16 @@ class Client extends openapi_core_1.default {
|
|
|
26659
26762
|
return $dara.cast(await this.callApi(params, req, runtime), new $_model.ReleaseEipAddressResponse({}));
|
|
26660
26763
|
}
|
|
26661
26764
|
/**
|
|
26662
|
-
* Releases a specified
|
|
26765
|
+
* Releases a specified elastic IP address (EIP).
|
|
26663
26766
|
*
|
|
26664
26767
|
* @remarks
|
|
26665
|
-
* Before you invoke this operation, take note of the following
|
|
26666
|
-
* - Before
|
|
26768
|
+
* Before you invoke this operation, take note of the following information:
|
|
26769
|
+
* - Before you release an EIP, make sure that the following conditions are met:
|
|
26667
26770
|
* - Only EIPs in the **Available** state can be released.
|
|
26668
26771
|
* - 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
|
|
26772
|
+
* - 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:
|
|
26773
|
+
* - 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.
|
|
26774
|
+
* - If the EIP instance cannot be found, the EIP instance is released.
|
|
26672
26775
|
* - The **ReleaseEipAddress** operation does not support concurrent release of the same EIP instance.
|
|
26673
26776
|
*
|
|
26674
26777
|
* @param request - ReleaseEipAddressRequest
|
|
@@ -28540,10 +28643,10 @@ class Client extends openapi_core_1.default {
|
|
|
28540
28643
|
return await this.unassociateRouteTableWithOptions(request, runtime);
|
|
28541
28644
|
}
|
|
28542
28645
|
/**
|
|
28543
|
-
*
|
|
28646
|
+
* Invokes UnassociateVpcCidrBlock to delete a secondary CIDR block from a VPC.
|
|
28544
28647
|
*
|
|
28545
28648
|
* @remarks
|
|
28546
|
-
* - Before
|
|
28649
|
+
* - 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
28650
|
* - The **UnassociateVpcCidrBlock** operation does not support concurrently deleting secondary CIDR blocks from the same VPC.
|
|
28548
28651
|
*
|
|
28549
28652
|
* @param request - UnassociateVpcCidrBlockRequest
|
|
@@ -28597,10 +28700,10 @@ class Client extends openapi_core_1.default {
|
|
|
28597
28700
|
return $dara.cast(await this.callApi(params, req, runtime), new $_model.UnassociateVpcCidrBlockResponse({}));
|
|
28598
28701
|
}
|
|
28599
28702
|
/**
|
|
28600
|
-
*
|
|
28703
|
+
* Invokes UnassociateVpcCidrBlock to delete a secondary CIDR block from a VPC.
|
|
28601
28704
|
*
|
|
28602
28705
|
* @remarks
|
|
28603
|
-
* - Before
|
|
28706
|
+
* - 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
28707
|
* - The **UnassociateVpcCidrBlock** operation does not support concurrently deleting secondary CIDR blocks from the same VPC.
|
|
28605
28708
|
*
|
|
28606
28709
|
* @param request - UnassociateVpcCidrBlockRequest
|