@alicloud/vpc20160428 7.3.0 → 7.3.2
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 +144 -142
- package/dist/client.js +153 -178
- package/dist/client.js.map +1 -1
- package/dist/models/AddCommonBandwidthPackageIpRequest.d.ts +4 -4
- package/dist/models/CreateCommonBandwidthPackageRequest.d.ts +15 -15
- package/dist/models/CreateDhcpOptionsSetRequest.d.ts +7 -7
- package/dist/models/CreateFlowLogRequest.d.ts +17 -9
- package/dist/models/CreateFlowLogRequest.js.map +1 -1
- package/dist/models/CreateRouteEntriesRequest.d.ts +17 -17
- package/dist/models/CreateRouteEntriesResponseBody.d.ts +3 -3
- package/dist/models/CreateRouteEntryRequest.d.ts +8 -8
- package/dist/models/CreateRouteTargetGroupRequest.d.ts +5 -6
- package/dist/models/CreateRouteTargetGroupRequest.js.map +1 -1
- package/dist/models/CreateVpnPbrRouteEntryRequest.d.ts +15 -15
- package/dist/models/CreateVpnPbrRouteEntryResponseBody.d.ts +3 -3
- package/dist/models/CreateVpnRouteEntryRequest.d.ts +7 -7
- package/dist/models/CreateVpnRouteEntryResponseBody.d.ts +2 -2
- package/dist/models/CreateVswitchCidrReservationRequest.d.ts +11 -11
- 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/DeleteRouteEntriesRequest.d.ts +3 -3
- package/dist/models/DeleteRouteEntriesResponseBody.d.ts +3 -3
- package/dist/models/DeleteRouteEntryRequest.d.ts +3 -3
- package/dist/models/DescribeRouteEntryListRequest.d.ts +6 -6
- package/dist/models/DescribeRouteEntryListResponseBody.d.ts +3 -2
- package/dist/models/DescribeRouteEntryListResponseBody.js +2 -0
- package/dist/models/DescribeRouteEntryListResponseBody.js.map +1 -1
- package/dist/models/DescribeVswitchAttributesRequest.d.ts +2 -2
- package/dist/models/DescribeVswitchAttributesResponseBody.d.ts +1 -1
- package/dist/models/GetDhcpOptionsSetRequest.d.ts +1 -1
- package/dist/models/GetDhcpOptionsSetResponseBody.d.ts +1 -1
- package/dist/models/GetVpcPrefixListAssociationsRequest.d.ts +3 -3
- package/dist/models/GetVpcPrefixListAssociationsResponseBody.d.ts +17 -9
- package/dist/models/GetVpcPrefixListAssociationsResponseBody.js +2 -0
- package/dist/models/GetVpcPrefixListAssociationsResponseBody.js.map +1 -1
- package/dist/models/GetVpcRouteEntrySummaryRequest.d.ts +7 -7
- package/dist/models/GetVpcRouteEntrySummaryResponseBody.d.ts +8 -8
- package/dist/models/ModifyRouteEntryRequest.d.ts +4 -4
- 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/RemoveCommonBandwidthPackageIpRequest.d.ts +8 -4
- package/dist/models/RemoveCommonBandwidthPackageIpRequest.js.map +1 -1
- package/dist/models/RetryVpcPrefixListAssociationRequest.d.ts +7 -7
- package/dist/models/SwitchActiveRouteTargetRequest.d.ts +3 -3
- package/dist/models/UpdateDhcpOptionsSetAttributeRequest.d.ts +10 -10
- package/package.json +1 -1
- package/src/client.ts +156 -178
- package/src/models/AddCommonBandwidthPackageIpRequest.ts +4 -4
- package/src/models/CreateCommonBandwidthPackageRequest.ts +15 -15
- package/src/models/CreateDhcpOptionsSetRequest.ts +7 -7
- package/src/models/CreateFlowLogRequest.ts +17 -9
- package/src/models/CreateRouteEntriesRequest.ts +17 -17
- package/src/models/CreateRouteEntriesResponseBody.ts +3 -3
- package/src/models/CreateRouteEntryRequest.ts +8 -8
- package/src/models/CreateRouteTargetGroupRequest.ts +5 -6
- package/src/models/CreateVpnPbrRouteEntryRequest.ts +15 -15
- package/src/models/CreateVpnPbrRouteEntryResponseBody.ts +3 -3
- package/src/models/CreateVpnRouteEntryRequest.ts +7 -7
- package/src/models/CreateVpnRouteEntryResponseBody.ts +2 -2
- package/src/models/CreateVswitchCidrReservationRequest.ts +11 -11
- package/src/models/CreateVswitchRequest.ts +30 -9
- package/src/models/DeleteRouteEntriesRequest.ts +3 -3
- package/src/models/DeleteRouteEntriesResponseBody.ts +3 -3
- package/src/models/DeleteRouteEntryRequest.ts +3 -3
- package/src/models/DescribeRouteEntryListRequest.ts +6 -6
- package/src/models/DescribeRouteEntryListResponseBody.ts +5 -2
- package/src/models/DescribeVswitchAttributesRequest.ts +2 -2
- package/src/models/DescribeVswitchAttributesResponseBody.ts +1 -1
- package/src/models/GetDhcpOptionsSetRequest.ts +1 -1
- package/src/models/GetDhcpOptionsSetResponseBody.ts +1 -1
- package/src/models/GetVpcPrefixListAssociationsRequest.ts +3 -3
- package/src/models/GetVpcPrefixListAssociationsResponseBody.ts +19 -9
- package/src/models/GetVpcRouteEntrySummaryRequest.ts +7 -7
- package/src/models/GetVpcRouteEntrySummaryResponseBody.ts +8 -8
- package/src/models/ModifyRouteEntryRequest.ts +4 -4
- package/src/models/ModifyVswitchAttributeRequest.ts +15 -3
- package/src/models/RemoveCommonBandwidthPackageIpRequest.ts +8 -4
- package/src/models/RetryVpcPrefixListAssociationRequest.ts +7 -7
- package/src/models/SwitchActiveRouteTargetRequest.ts +3 -3
- package/src/models/UpdateDhcpOptionsSetAttributeRequest.ts +10 -10
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);
|
|
@@ -329,12 +293,12 @@ class Client extends openapi_core_1.default {
|
|
|
329
293
|
* Adds an elastic IP address (EIP) to an Internet Shared Bandwidth instance.
|
|
330
294
|
*
|
|
331
295
|
* @remarks
|
|
332
|
-
* Before
|
|
296
|
+
* Before you invoke this operation, take note of the following items:
|
|
333
297
|
* - When you invoke this operation to add an EIP to an Internet Shared Bandwidth instance, the EIP must meet the following conditions:
|
|
334
|
-
* - The
|
|
298
|
+
* - The billing method of the EIP is pay-as-you-go.
|
|
335
299
|
* - The EIP is in the same region as the Internet Shared Bandwidth instance.
|
|
336
300
|
* - The line type of the EIP is the same as that of the Internet Shared Bandwidth instance.
|
|
337
|
-
* - The **AddCommonBandwidthPackageIp** operation is asynchronous. After you send a request, the system returns a request ID,
|
|
301
|
+
* - The **AddCommonBandwidthPackageIp** operation is asynchronous. After you send a request, the system returns a request ID. However, the EIP is not yet added to the Internet Shared Bandwidth instance. The addition node is still running in the background. You can invoke [DescribeCommonBandwidthPackages](https://help.aliyun.com/document_detail/120309.html) to query the association status between the Internet Shared Bandwidth instance and the EIP.
|
|
338
302
|
* - If the association status is **BINDING**, the Internet Shared Bandwidth instance is being associated with the EIP. In this state, you can only execute query operations.
|
|
339
303
|
* - If the association status is **BINDED**, the Internet Shared Bandwidth instance is associated with the EIP.
|
|
340
304
|
*
|
|
@@ -395,12 +359,12 @@ class Client extends openapi_core_1.default {
|
|
|
395
359
|
* Adds an elastic IP address (EIP) to an Internet Shared Bandwidth instance.
|
|
396
360
|
*
|
|
397
361
|
* @remarks
|
|
398
|
-
* Before
|
|
362
|
+
* Before you invoke this operation, take note of the following items:
|
|
399
363
|
* - When you invoke this operation to add an EIP to an Internet Shared Bandwidth instance, the EIP must meet the following conditions:
|
|
400
|
-
* - The
|
|
364
|
+
* - The billing method of the EIP is pay-as-you-go.
|
|
401
365
|
* - The EIP is in the same region as the Internet Shared Bandwidth instance.
|
|
402
366
|
* - The line type of the EIP is the same as that of the Internet Shared Bandwidth instance.
|
|
403
|
-
* - The **AddCommonBandwidthPackageIp** operation is asynchronous. After you send a request, the system returns a request ID,
|
|
367
|
+
* - The **AddCommonBandwidthPackageIp** operation is asynchronous. After you send a request, the system returns a request ID. However, the EIP is not yet added to the Internet Shared Bandwidth instance. The addition node is still running in the background. You can invoke [DescribeCommonBandwidthPackages](https://help.aliyun.com/document_detail/120309.html) to query the association status between the Internet Shared Bandwidth instance and the EIP.
|
|
404
368
|
* - If the association status is **BINDING**, the Internet Shared Bandwidth instance is being associated with the EIP. In this state, you can only execute query operations.
|
|
405
369
|
* - If the association status is **BINDED**, the Internet Shared Bandwidth instance is associated with the EIP.
|
|
406
370
|
*
|
|
@@ -3547,7 +3511,7 @@ class Client extends openapi_core_1.default {
|
|
|
3547
3511
|
* @remarks
|
|
3548
3512
|
* - **CreateDhcpOptionsSet** is an asynchronous operation. After you invoke this operation, the system returns an instance ID but the DHCP options set is not yet created. The background node is still in progress. You can invoke [GetDhcpOptionsSet](https://help.aliyun.com/document_detail/448820.html) to query the creation status of the DHCP options set:
|
|
3549
3513
|
* - If the vSwitch is in the **Pending** state, the DHCP options set is being configured.
|
|
3550
|
-
* - If the vSwitch is in the **
|
|
3514
|
+
* - If the vSwitch is in the **Active** state, the DHCP options set is active.
|
|
3551
3515
|
*
|
|
3552
3516
|
* @param request - CreateDhcpOptionsSetRequest
|
|
3553
3517
|
* @param runtime - runtime options for this request RuntimeOptions
|
|
@@ -3623,7 +3587,7 @@ class Client extends openapi_core_1.default {
|
|
|
3623
3587
|
* @remarks
|
|
3624
3588
|
* - **CreateDhcpOptionsSet** is an asynchronous operation. After you invoke this operation, the system returns an instance ID but the DHCP options set is not yet created. The background node is still in progress. You can invoke [GetDhcpOptionsSet](https://help.aliyun.com/document_detail/448820.html) to query the creation status of the DHCP options set:
|
|
3625
3589
|
* - If the vSwitch is in the **Pending** state, the DHCP options set is being configured.
|
|
3626
|
-
* - If the vSwitch is in the **
|
|
3590
|
+
* - If the vSwitch is in the **Active** state, the DHCP options set is active.
|
|
3627
3591
|
*
|
|
3628
3592
|
* @param request - CreateDhcpOptionsSetRequest
|
|
3629
3593
|
* @returns CreateDhcpOptionsSetResponse
|
|
@@ -4188,7 +4152,7 @@ class Client extends openapi_core_1.default {
|
|
|
4188
4152
|
* Creates a flow log.
|
|
4189
4153
|
*
|
|
4190
4154
|
* @remarks
|
|
4191
|
-
* *CreateFlowLog** is an asynchronous operation. After you
|
|
4155
|
+
* *CreateFlowLog** is an asynchronous operation. After you call this operation, the system returns an instance ID, but the flow log has not been created yet. The creation task is still running in the background. You can call [DescribeFlowLogs](https://help.aliyun.com/document_detail/448670.html) to query the creation status of the flow log:
|
|
4192
4156
|
* - If the flow log is in the **Activating** state, the flow log is being created.
|
|
4193
4157
|
* - If the flow log is in the **Active** state, the flow log is created and activated.
|
|
4194
4158
|
*
|
|
@@ -4273,7 +4237,7 @@ class Client extends openapi_core_1.default {
|
|
|
4273
4237
|
* Creates a flow log.
|
|
4274
4238
|
*
|
|
4275
4239
|
* @remarks
|
|
4276
|
-
* *CreateFlowLog** is an asynchronous operation. After you
|
|
4240
|
+
* *CreateFlowLog** is an asynchronous operation. After you call this operation, the system returns an instance ID, but the flow log has not been created yet. The creation task is still running in the background. You can call [DescribeFlowLogs](https://help.aliyun.com/document_detail/448670.html) to query the creation status of the flow log:
|
|
4277
4241
|
* - If the flow log is in the **Activating** state, the flow log is being created.
|
|
4278
4242
|
* - If the flow log is in the **Active** state, the flow log is created and activated.
|
|
4279
4243
|
*
|
|
@@ -6069,17 +6033,17 @@ class Client extends openapi_core_1.default {
|
|
|
6069
6033
|
return await this.createPublicIpAddressPoolWithOptions(request, runtime);
|
|
6070
6034
|
}
|
|
6071
6035
|
/**
|
|
6072
|
-
* Creates custom route entries in a route table of a
|
|
6036
|
+
* Creates custom route entries in a route table of a vRouter in bulk.
|
|
6073
6037
|
*
|
|
6074
6038
|
* @remarks
|
|
6075
|
-
* - **CreateRouteEntries** is an asynchronous operation. After you invoke this operation, the system returns an instance ID, but the route has not been created yet. The system
|
|
6076
|
-
* - If the route is in the **Creating** state, the route is being created.
|
|
6077
|
-
* - If the route is in the **Created** state, the route
|
|
6078
|
-
* - **CreateRouteEntries** does not support concurrent
|
|
6079
|
-
* **
|
|
6039
|
+
* - **CreateRouteEntries** is an asynchronous operation. After you invoke this operation, the system returns an instance ID, but the custom route entry has not been created yet. The system is still running the task in the background. You can invoke [DescribeRouteEntryList](https://help.aliyun.com/document_detail/138148.html) to query the creation status of the custom route entry:
|
|
6040
|
+
* - If the custom route entry is in the **Creating** state, the custom route entry is being created.
|
|
6041
|
+
* - If the custom route entry is in the **Created** state, the custom route entry has been created.
|
|
6042
|
+
* - **CreateRouteEntries** does not support concurrent bulk creation of custom route entries in the same VPC.
|
|
6043
|
+
* **When you use this operation to add custom route entries to a route table of a vRouter, take note of the following items:**
|
|
6080
6044
|
* - A route table can contain a maximum of 200 custom route entries.
|
|
6081
6045
|
* - The destination CIDR block (**DstCidrBlock**) of a custom route entry cannot be the same as, contain, or be contained by the CIDR block of a vSwitch in the VPC.
|
|
6082
|
-
* - The destination CIDR block (**DstCidrBlock**) of a custom route entry cannot point to or be contained by 100.64.0.0/10.
|
|
6046
|
+
* - The destination CIDR block (**DstCidrBlock**) of a custom route entry cannot point to 100.64.0.0/10 or be contained by 100.64.0.0/10.
|
|
6083
6047
|
* - The destination CIDR blocks (**DstCidrBlock**) of route entries in the same route table must be unique.
|
|
6084
6048
|
* - If the specified destination CIDR block (**DstCidrBlock**) is an IP address, the system processes it with a 32-bit mask.
|
|
6085
6049
|
* - Multiple custom route entries can point to the same next hop (**NextHop**).
|
|
@@ -6133,17 +6097,17 @@ class Client extends openapi_core_1.default {
|
|
|
6133
6097
|
return $dara.cast(await this.callApi(params, req, runtime), new $_model.CreateRouteEntriesResponse({}));
|
|
6134
6098
|
}
|
|
6135
6099
|
/**
|
|
6136
|
-
* Creates custom route entries in a route table of a
|
|
6100
|
+
* Creates custom route entries in a route table of a vRouter in bulk.
|
|
6137
6101
|
*
|
|
6138
6102
|
* @remarks
|
|
6139
|
-
* - **CreateRouteEntries** is an asynchronous operation. After you invoke this operation, the system returns an instance ID, but the route has not been created yet. The system
|
|
6140
|
-
* - If the route is in the **Creating** state, the route is being created.
|
|
6141
|
-
* - If the route is in the **Created** state, the route
|
|
6142
|
-
* - **CreateRouteEntries** does not support concurrent
|
|
6143
|
-
* **
|
|
6103
|
+
* - **CreateRouteEntries** is an asynchronous operation. After you invoke this operation, the system returns an instance ID, but the custom route entry has not been created yet. The system is still running the task in the background. You can invoke [DescribeRouteEntryList](https://help.aliyun.com/document_detail/138148.html) to query the creation status of the custom route entry:
|
|
6104
|
+
* - If the custom route entry is in the **Creating** state, the custom route entry is being created.
|
|
6105
|
+
* - If the custom route entry is in the **Created** state, the custom route entry has been created.
|
|
6106
|
+
* - **CreateRouteEntries** does not support concurrent bulk creation of custom route entries in the same VPC.
|
|
6107
|
+
* **When you use this operation to add custom route entries to a route table of a vRouter, take note of the following items:**
|
|
6144
6108
|
* - A route table can contain a maximum of 200 custom route entries.
|
|
6145
6109
|
* - The destination CIDR block (**DstCidrBlock**) of a custom route entry cannot be the same as, contain, or be contained by the CIDR block of a vSwitch in the VPC.
|
|
6146
|
-
* - The destination CIDR block (**DstCidrBlock**) of a custom route entry cannot point to or be contained by 100.64.0.0/10.
|
|
6110
|
+
* - The destination CIDR block (**DstCidrBlock**) of a custom route entry cannot point to 100.64.0.0/10 or be contained by 100.64.0.0/10.
|
|
6147
6111
|
* - The destination CIDR blocks (**DstCidrBlock**) of route entries in the same route table must be unique.
|
|
6148
6112
|
* - If the specified destination CIDR block (**DstCidrBlock**) is an IP address, the system processes it with a 32-bit mask.
|
|
6149
6113
|
* - Multiple custom route entries can point to the same next hop (**NextHop**).
|
|
@@ -6160,44 +6124,44 @@ class Client extends openapi_core_1.default {
|
|
|
6160
6124
|
* Creates a custom route entry on a vRouter or Virtual Border Router (VBR).
|
|
6161
6125
|
*
|
|
6162
6126
|
* @remarks
|
|
6163
|
-
* - **CreateRouteEntry** is
|
|
6164
|
-
* - If the route is in the **Creating** state, the route is being
|
|
6165
|
-
* - If the route is in the **Created** state, the route has been
|
|
6166
|
-
* - **CreateRouteEntry** does not support concurrent
|
|
6167
|
-
* - **CreateRouteEntry** may return the **TaskConflict** error code in concurrent scenarios. Retry the
|
|
6168
|
-
* **When you use this operation to add
|
|
6169
|
-
* > When the route to be added is a prefix list route, the route quota is calculated based on the sum of existing routes and the maximum number of entries in the prefix list route. The sum cannot exceed the route quota.
|
|
6170
|
-
* - A route table can contain
|
|
6171
|
-
* - The destination CIDR block (**DestinationCidrBlock**) of a custom route entry cannot be the same as
|
|
6172
|
-
* - The destination CIDR block (**DestinationCidrBlock**) of a custom route entry can be a more specific CIDR block than the
|
|
6127
|
+
* - The **CreateRouteEntry** operation is asynchronous. After you send a request, the system returns an instance ID while the custom route entry is still being added in the background. You can invoke [DescribeRouteEntryList](https://help.aliyun.com/document_detail/138148.html) to query the status of the custom route entry:
|
|
6128
|
+
* - If the custom route entry is in the **Creating** state, the custom route entry is being added.
|
|
6129
|
+
* - If the custom route entry is in the **Created** state, the custom route entry has been added.
|
|
6130
|
+
* - The **CreateRouteEntry** operation does not support concurrent addition of custom route entries in the same VPC or the same VBR.
|
|
6131
|
+
* - The **CreateRouteEntry** operation may return the **TaskConflict** error code in concurrent scenarios. Retry the request as appropriate.
|
|
6132
|
+
* **When you use this operation to add custom route entries to a route table of a vRouter, take note of the following items:**
|
|
6133
|
+
* > When the route to be added is a prefix list route, the route quota is calculated based on the sum of existing routes and the maximum number of route entries in the prefix list route. The sum cannot exceed the route quota limit.
|
|
6134
|
+
* - A route table can contain a maximum of 200 custom route entries.
|
|
6135
|
+
* - The destination CIDR block (**DestinationCidrBlock**) of a custom route entry cannot be the same as the CIDR block of a vSwitch in the VPC. The destination CIDR block can contain the CIDR block of a vSwitch but cannot be contained by the CIDR block of a vSwitch.
|
|
6136
|
+
* - The destination CIDR block (**DestinationCidrBlock**) of a custom route entry can be a more specific CIDR block than the system route CIDR block `100.64.0.0/10` used by cloud services, but cannot be the same as this CIDR block.
|
|
6173
6137
|
* <notice>The system route with the destination CIDR block `100.64.0.0/10` is used for communication among cloud services within the VPC. Exercise caution when you configure a more specific route. Incorrect configurations may cause cloud services to become inaccessible.</notice>
|
|
6174
|
-
* -
|
|
6175
|
-
* - If the specified destination CIDR block (**DestinationCidrBlock**) is an IP address,
|
|
6138
|
+
* - Route entries in the same route table cannot have the same destination CIDR block (**DestinationCidrBlock**).
|
|
6139
|
+
* - If the specified destination CIDR block (**DestinationCidrBlock**) is an IP address, the system processes it with a 32-bit mask.
|
|
6176
6140
|
* - Multiple custom route entries can point to the same next hop (**NextHopId**).
|
|
6177
6141
|
* - The next hop (**NextHopId**) of a custom route entry must be in the same VPC as the route table.
|
|
6178
6142
|
* - You can configure ECMP routing by using the **NextHopList** parameter settings:
|
|
6179
6143
|
* * To add a non-ECMP custom route, specify the **DestinationCidrBlock**, **NextHopType**, and **NextHopId** parameters. Do not specify the **NextHopList** parameter.
|
|
6180
6144
|
*
|
|
6181
6145
|
* * To add an ECMP route, specify the **DestinationCidrBlock** and **NextHopList** parameters. Do not specify the **NextHopType** or **NextHopId** parameter.
|
|
6182
|
-
* **When you use this operation to add
|
|
6183
|
-
* - A route table can contain
|
|
6146
|
+
* **When you use this operation to add custom route entries to a route table of a Virtual Border Router (VBR), take note of the following items:**
|
|
6147
|
+
* - A route table can contain a maximum of 200 custom route entries.
|
|
6184
6148
|
*
|
|
6185
6149
|
* - The **NextHopList** parameter is not supported.
|
|
6186
6150
|
*
|
|
6187
|
-
* - The destination CIDR block (**DestinationCidrBlock**) of a custom route entry can be a more specific CIDR block than the
|
|
6151
|
+
* - The destination CIDR block (**DestinationCidrBlock**) of a custom route entry can be a more specific CIDR block than the system route CIDR block `100.64.0.0/10` used by cloud services, but cannot be the same as this CIDR block.
|
|
6188
6152
|
* <notice>The system route with the destination CIDR block `100.64.0.0/10` is used for communication among cloud services within the VPC. Exercise caution when you configure a more specific route. Incorrect configurations may cause cloud services to become inaccessible.</notice>
|
|
6189
6153
|
*
|
|
6190
|
-
* -
|
|
6154
|
+
* - Route entries in the same route table cannot have the same destination CIDR block (**DestinationCidrBlock**).
|
|
6191
6155
|
*
|
|
6192
|
-
* - If the specified destination CIDR block (**DestinationCidrBlock**) is an IP address,
|
|
6156
|
+
* - If the specified destination CIDR block (**DestinationCidrBlock**) is an IP address, the system processes it with a 32-bit mask.
|
|
6193
6157
|
*
|
|
6194
6158
|
* - Multiple custom route entries can point to the same next hop (**NextHopId**).
|
|
6195
6159
|
*
|
|
6196
|
-
* - The next hop (**NextHopId**) of a custom route entry must be
|
|
6160
|
+
* - The next hop (**NextHopId**) of a custom route entry must be the vRouter interface associated with the VBR.
|
|
6197
6161
|
*
|
|
6198
|
-
* - You can
|
|
6162
|
+
* - You can add route entries to a VBR only when the VBR is in the **Active** state, the corresponding Express Connect circuit is in the **Enabled** state, and the circuit is not locked due to overdue payment.
|
|
6199
6163
|
*
|
|
6200
|
-
* - Only
|
|
6164
|
+
* - Only non-ECMP route entries are supported. Specify the **DestinationCidrBlock**, **NextHopType**, and **NextHopId** parameters. Do not specify the **NextHopList** parameter.
|
|
6201
6165
|
*
|
|
6202
6166
|
* @param request - CreateRouteEntryRequest
|
|
6203
6167
|
* @param runtime - runtime options for this request RuntimeOptions
|
|
@@ -6268,44 +6232,44 @@ class Client extends openapi_core_1.default {
|
|
|
6268
6232
|
* Creates a custom route entry on a vRouter or Virtual Border Router (VBR).
|
|
6269
6233
|
*
|
|
6270
6234
|
* @remarks
|
|
6271
|
-
* - **CreateRouteEntry** is
|
|
6272
|
-
* - If the route is in the **Creating** state, the route is being
|
|
6273
|
-
* - If the route is in the **Created** state, the route has been
|
|
6274
|
-
* - **CreateRouteEntry** does not support concurrent
|
|
6275
|
-
* - **CreateRouteEntry** may return the **TaskConflict** error code in concurrent scenarios. Retry the
|
|
6276
|
-
* **When you use this operation to add
|
|
6277
|
-
* > When the route to be added is a prefix list route, the route quota is calculated based on the sum of existing routes and the maximum number of entries in the prefix list route. The sum cannot exceed the route quota.
|
|
6278
|
-
* - A route table can contain
|
|
6279
|
-
* - The destination CIDR block (**DestinationCidrBlock**) of a custom route entry cannot be the same as
|
|
6280
|
-
* - The destination CIDR block (**DestinationCidrBlock**) of a custom route entry can be a more specific CIDR block than the
|
|
6235
|
+
* - The **CreateRouteEntry** operation is asynchronous. After you send a request, the system returns an instance ID while the custom route entry is still being added in the background. You can invoke [DescribeRouteEntryList](https://help.aliyun.com/document_detail/138148.html) to query the status of the custom route entry:
|
|
6236
|
+
* - If the custom route entry is in the **Creating** state, the custom route entry is being added.
|
|
6237
|
+
* - If the custom route entry is in the **Created** state, the custom route entry has been added.
|
|
6238
|
+
* - The **CreateRouteEntry** operation does not support concurrent addition of custom route entries in the same VPC or the same VBR.
|
|
6239
|
+
* - The **CreateRouteEntry** operation may return the **TaskConflict** error code in concurrent scenarios. Retry the request as appropriate.
|
|
6240
|
+
* **When you use this operation to add custom route entries to a route table of a vRouter, take note of the following items:**
|
|
6241
|
+
* > When the route to be added is a prefix list route, the route quota is calculated based on the sum of existing routes and the maximum number of route entries in the prefix list route. The sum cannot exceed the route quota limit.
|
|
6242
|
+
* - A route table can contain a maximum of 200 custom route entries.
|
|
6243
|
+
* - The destination CIDR block (**DestinationCidrBlock**) of a custom route entry cannot be the same as the CIDR block of a vSwitch in the VPC. The destination CIDR block can contain the CIDR block of a vSwitch but cannot be contained by the CIDR block of a vSwitch.
|
|
6244
|
+
* - The destination CIDR block (**DestinationCidrBlock**) of a custom route entry can be a more specific CIDR block than the system route CIDR block `100.64.0.0/10` used by cloud services, but cannot be the same as this CIDR block.
|
|
6281
6245
|
* <notice>The system route with the destination CIDR block `100.64.0.0/10` is used for communication among cloud services within the VPC. Exercise caution when you configure a more specific route. Incorrect configurations may cause cloud services to become inaccessible.</notice>
|
|
6282
|
-
* -
|
|
6283
|
-
* - If the specified destination CIDR block (**DestinationCidrBlock**) is an IP address,
|
|
6246
|
+
* - Route entries in the same route table cannot have the same destination CIDR block (**DestinationCidrBlock**).
|
|
6247
|
+
* - If the specified destination CIDR block (**DestinationCidrBlock**) is an IP address, the system processes it with a 32-bit mask.
|
|
6284
6248
|
* - Multiple custom route entries can point to the same next hop (**NextHopId**).
|
|
6285
6249
|
* - The next hop (**NextHopId**) of a custom route entry must be in the same VPC as the route table.
|
|
6286
6250
|
* - You can configure ECMP routing by using the **NextHopList** parameter settings:
|
|
6287
6251
|
* * To add a non-ECMP custom route, specify the **DestinationCidrBlock**, **NextHopType**, and **NextHopId** parameters. Do not specify the **NextHopList** parameter.
|
|
6288
6252
|
*
|
|
6289
6253
|
* * To add an ECMP route, specify the **DestinationCidrBlock** and **NextHopList** parameters. Do not specify the **NextHopType** or **NextHopId** parameter.
|
|
6290
|
-
* **When you use this operation to add
|
|
6291
|
-
* - A route table can contain
|
|
6254
|
+
* **When you use this operation to add custom route entries to a route table of a Virtual Border Router (VBR), take note of the following items:**
|
|
6255
|
+
* - A route table can contain a maximum of 200 custom route entries.
|
|
6292
6256
|
*
|
|
6293
6257
|
* - The **NextHopList** parameter is not supported.
|
|
6294
6258
|
*
|
|
6295
|
-
* - The destination CIDR block (**DestinationCidrBlock**) of a custom route entry can be a more specific CIDR block than the
|
|
6259
|
+
* - The destination CIDR block (**DestinationCidrBlock**) of a custom route entry can be a more specific CIDR block than the system route CIDR block `100.64.0.0/10` used by cloud services, but cannot be the same as this CIDR block.
|
|
6296
6260
|
* <notice>The system route with the destination CIDR block `100.64.0.0/10` is used for communication among cloud services within the VPC. Exercise caution when you configure a more specific route. Incorrect configurations may cause cloud services to become inaccessible.</notice>
|
|
6297
6261
|
*
|
|
6298
|
-
* -
|
|
6262
|
+
* - Route entries in the same route table cannot have the same destination CIDR block (**DestinationCidrBlock**).
|
|
6299
6263
|
*
|
|
6300
|
-
* - If the specified destination CIDR block (**DestinationCidrBlock**) is an IP address,
|
|
6264
|
+
* - If the specified destination CIDR block (**DestinationCidrBlock**) is an IP address, the system processes it with a 32-bit mask.
|
|
6301
6265
|
*
|
|
6302
6266
|
* - Multiple custom route entries can point to the same next hop (**NextHopId**).
|
|
6303
6267
|
*
|
|
6304
|
-
* - The next hop (**NextHopId**) of a custom route entry must be
|
|
6268
|
+
* - The next hop (**NextHopId**) of a custom route entry must be the vRouter interface associated with the VBR.
|
|
6305
6269
|
*
|
|
6306
|
-
* - You can
|
|
6270
|
+
* - You can add route entries to a VBR only when the VBR is in the **Active** state, the corresponding Express Connect circuit is in the **Enabled** state, and the circuit is not locked due to overdue payment.
|
|
6307
6271
|
*
|
|
6308
|
-
* - Only
|
|
6272
|
+
* - Only non-ECMP route entries are supported. Specify the **DestinationCidrBlock**, **NextHopType**, and **NextHopId** parameters. Do not specify the **NextHopList** parameter.
|
|
6309
6273
|
*
|
|
6310
6274
|
* @param request - CreateRouteEntryRequest
|
|
6311
6275
|
* @returns CreateRouteEntryResponse
|
|
@@ -6402,12 +6366,12 @@ class Client extends openapi_core_1.default {
|
|
|
6402
6366
|
* Creates a route target group instance.
|
|
6403
6367
|
*
|
|
6404
6368
|
* @remarks
|
|
6405
|
-
* - **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:
|
|
6406
6370
|
* - If the routing target group is in the **Pending** state, the routing target group is being created.
|
|
6407
6371
|
* - If the routing target group is in the **Available**, **Unavailable**, **Switched**, or **Abnormal** state, the routing target group is created.
|
|
6408
|
-
* - **Active/standby
|
|
6409
|
-
* - **Primary instance**: The weight is 100. The primary instance
|
|
6410
|
-
* - **Secondary instance**: The weight is 0. The secondary instance takes over traffic
|
|
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.
|
|
6374
|
+
* - **Secondary instance**: The weight is 0. The secondary instance takes over traffic when the primary instance fails, serving as disaster recovery and backup.
|
|
6411
6375
|
*
|
|
6412
6376
|
* @param request - CreateRouteTargetGroupRequest
|
|
6413
6377
|
* @param runtime - runtime options for this request RuntimeOptions
|
|
@@ -6463,12 +6427,12 @@ class Client extends openapi_core_1.default {
|
|
|
6463
6427
|
* Creates a route target group instance.
|
|
6464
6428
|
*
|
|
6465
6429
|
* @remarks
|
|
6466
|
-
* - **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:
|
|
6467
6431
|
* - If the routing target group is in the **Pending** state, the routing target group is being created.
|
|
6468
6432
|
* - If the routing target group is in the **Available**, **Unavailable**, **Switched**, or **Abnormal** state, the routing target group is created.
|
|
6469
|
-
* - **Active/standby
|
|
6470
|
-
* - **Primary instance**: The weight is 100. The primary instance
|
|
6471
|
-
* - **Secondary instance**: The weight is 0. The secondary instance takes over traffic
|
|
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.
|
|
6435
|
+
* - **Secondary instance**: The weight is 0. The secondary instance takes over traffic when the primary instance fails, serving as disaster recovery and backup.
|
|
6472
6436
|
*
|
|
6473
6437
|
* @param request - CreateRouteTargetGroupRequest
|
|
6474
6438
|
* @returns CreateRouteTargetGroupResponse
|
|
@@ -7175,7 +7139,7 @@ class Client extends openapi_core_1.default {
|
|
|
7175
7139
|
* @remarks
|
|
7176
7140
|
* When you call this operation to create a vSwitch, take note of the following items:
|
|
7177
7141
|
* - The number of vSwitches in each VPC cannot exceed 150.
|
|
7178
|
-
* - 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.
|
|
7179
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).
|
|
7180
7144
|
* - A cloud service instance can belong to only one vSwitch.
|
|
7181
7145
|
* - vSwitches do not support multicast or broadcast.
|
|
@@ -7196,6 +7160,9 @@ class Client extends openapi_core_1.default {
|
|
|
7196
7160
|
if (!$dara.isNull(request.cidrBlock)) {
|
|
7197
7161
|
query["CidrBlock"] = request.cidrBlock;
|
|
7198
7162
|
}
|
|
7163
|
+
if (!$dara.isNull(request.cidrMask)) {
|
|
7164
|
+
query["CidrMask"] = request.cidrMask;
|
|
7165
|
+
}
|
|
7199
7166
|
if (!$dara.isNull(request.clientToken)) {
|
|
7200
7167
|
query["ClientToken"] = request.clientToken;
|
|
7201
7168
|
}
|
|
@@ -7205,6 +7172,9 @@ class Client extends openapi_core_1.default {
|
|
|
7205
7172
|
if (!$dara.isNull(request.ipv6CidrBlock)) {
|
|
7206
7173
|
query["Ipv6CidrBlock"] = request.ipv6CidrBlock;
|
|
7207
7174
|
}
|
|
7175
|
+
if (!$dara.isNull(request.ipv6CidrMask)) {
|
|
7176
|
+
query["Ipv6CidrMask"] = request.ipv6CidrMask;
|
|
7177
|
+
}
|
|
7208
7178
|
if (!$dara.isNull(request.ownerAccount)) {
|
|
7209
7179
|
query["OwnerAccount"] = request.ownerAccount;
|
|
7210
7180
|
}
|
|
@@ -7257,7 +7227,7 @@ class Client extends openapi_core_1.default {
|
|
|
7257
7227
|
* @remarks
|
|
7258
7228
|
* When you call this operation to create a vSwitch, take note of the following items:
|
|
7259
7229
|
* - The number of vSwitches in each VPC cannot exceed 150.
|
|
7260
|
-
* - 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.
|
|
7261
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).
|
|
7262
7232
|
* - A cloud service instance can belong to only one vSwitch.
|
|
7263
7233
|
* - vSwitches do not support multicast or broadcast.
|
|
@@ -7276,15 +7246,15 @@ class Client extends openapi_core_1.default {
|
|
|
7276
7246
|
return await this.createVSwitchWithOptions(request, runtime);
|
|
7277
7247
|
}
|
|
7278
7248
|
/**
|
|
7279
|
-
* Creates a reserved CIDR block for a vSwitch.
|
|
7249
|
+
* Creates a reserved CIDR block for a vSwitch by calling the CreateVSwitchCidrReservation operation.
|
|
7280
7250
|
*
|
|
7281
7251
|
* @remarks
|
|
7282
7252
|
* When you invoke this operation to create a reserved CIDR block for a vSwitch, take note of the following items:
|
|
7283
|
-
* - The maximum number of reserved IPv4 and IPv6 CIDR blocks in a VPC is 100 each.
|
|
7253
|
+
* - The maximum number of reserved IPv4 CIDR blocks and reserved IPv6 CIDR blocks in a VPC is 100 each.
|
|
7284
7254
|
* - A reserved CIDR block cannot contain the system reserved IP addresses of the vSwitch to which it belongs.
|
|
7285
|
-
* - IPv4 CIDR block: The first and last three IP addresses of the vSwitch are system reserved IP addresses.
|
|
7286
|
-
* - IPv6 CIDR block: The first and last nine IP addresses of the vSwitch are system reserved IP addresses.
|
|
7287
|
-
* - The **CreateVSwitchCidrReservation** operation is asynchronous. After you send a request, the system returns an instance ID, but the reserved CIDR block for a vSwitch has not been created. The
|
|
7255
|
+
* - IPv4 CIDR block: The first IP address and the last three IP addresses of the vSwitch are system reserved IP addresses.
|
|
7256
|
+
* - IPv6 CIDR block: The first IP address and the last nine IP addresses of the vSwitch are system reserved IP addresses.
|
|
7257
|
+
* - The **CreateVSwitchCidrReservation** operation is asynchronous. After you send a request, the system returns an instance ID, but the reserved CIDR block for a vSwitch has not been created. The system continues to run the background node. You can invoke [ListVSwitchCidrReservations](https://help.aliyun.com/document_detail/610155.html) to query the creation status of the reserved CIDR block for a vSwitch:
|
|
7288
7258
|
* - If the reserved CIDR block for a vSwitch is in the **Assigning** state, the reserved CIDR block for a vSwitch is being allocated.
|
|
7289
7259
|
* - If the reserved CIDR block for a vSwitch is in the **Assigned** state, the reserved CIDR block for a vSwitch has been allocated.
|
|
7290
7260
|
*
|
|
@@ -7360,15 +7330,15 @@ class Client extends openapi_core_1.default {
|
|
|
7360
7330
|
return $dara.cast(await this.callApi(params, req, runtime), new $_model.CreateVSwitchCidrReservationResponse({}));
|
|
7361
7331
|
}
|
|
7362
7332
|
/**
|
|
7363
|
-
* Creates a reserved CIDR block for a vSwitch.
|
|
7333
|
+
* Creates a reserved CIDR block for a vSwitch by calling the CreateVSwitchCidrReservation operation.
|
|
7364
7334
|
*
|
|
7365
7335
|
* @remarks
|
|
7366
7336
|
* When you invoke this operation to create a reserved CIDR block for a vSwitch, take note of the following items:
|
|
7367
|
-
* - The maximum number of reserved IPv4 and IPv6 CIDR blocks in a VPC is 100 each.
|
|
7337
|
+
* - The maximum number of reserved IPv4 CIDR blocks and reserved IPv6 CIDR blocks in a VPC is 100 each.
|
|
7368
7338
|
* - A reserved CIDR block cannot contain the system reserved IP addresses of the vSwitch to which it belongs.
|
|
7369
|
-
* - IPv4 CIDR block: The first and last three IP addresses of the vSwitch are system reserved IP addresses.
|
|
7370
|
-
* - IPv6 CIDR block: The first and last nine IP addresses of the vSwitch are system reserved IP addresses.
|
|
7371
|
-
* - The **CreateVSwitchCidrReservation** operation is asynchronous. After you send a request, the system returns an instance ID, but the reserved CIDR block for a vSwitch has not been created. The
|
|
7339
|
+
* - IPv4 CIDR block: The first IP address and the last three IP addresses of the vSwitch are system reserved IP addresses.
|
|
7340
|
+
* - IPv6 CIDR block: The first IP address and the last nine IP addresses of the vSwitch are system reserved IP addresses.
|
|
7341
|
+
* - The **CreateVSwitchCidrReservation** operation is asynchronous. After you send a request, the system returns an instance ID, but the reserved CIDR block for a vSwitch has not been created. The system continues to run the background node. You can invoke [ListVSwitchCidrReservations](https://help.aliyun.com/document_detail/610155.html) to query the creation status of the reserved CIDR block for a vSwitch:
|
|
7372
7342
|
* - If the reserved CIDR block for a vSwitch is in the **Assigning** state, the reserved CIDR block for a vSwitch is being allocated.
|
|
7373
7343
|
* - If the reserved CIDR block for a vSwitch is in the **Assigned** state, the reserved CIDR block for a vSwitch has been allocated.
|
|
7374
7344
|
*
|
|
@@ -8485,9 +8455,10 @@ class Client extends openapi_core_1.default {
|
|
|
8485
8455
|
* - Before you create a policy-based route, make sure that you have created an IPsec-VPN connection. For more information, see [CreateVpnConnection](https://help.aliyun.com/document_detail/120391.html).
|
|
8486
8456
|
* - Before you create a policy-based route, we recommend that you familiarize yourself with the limits and matching rules of policy-based routes. For more information, see [Use policy-based routes](https://help.aliyun.com/document_detail/110777.html).
|
|
8487
8457
|
* ### Limits
|
|
8488
|
-
* -
|
|
8489
|
-
*
|
|
8490
|
-
*
|
|
8458
|
+
* - For single-tunnel VPN gateways:
|
|
8459
|
+
* - 0.0.0.0/0 is not supported as the destination CIDR block of a policy-based route.
|
|
8460
|
+
* - CIDR blocks that overlap with 100.64.0.0/10 (including 100.64.0.0/10 itself, its subnets, and parent CIDR blocks that contain it) are not supported as the destination CIDR block of a policy-based route.
|
|
8461
|
+
* - **CreateVpnPbrRouteEntry** is an asynchronous operation. After you send a request, the system returns the policy-based route information, but the route has not been created yet. The system continues to create the route in the background. You can invoke the [DescribeVpnGateway](https://help.aliyun.com/document_detail/73720.html) operation to query the instance status of the VPN gateway to determine the creation status of the policy-based routing node:
|
|
8491
8462
|
* - If the VPN gateway instance is in the **updating** state, the policy-based route is being created.
|
|
8492
8463
|
* - If the VPN gateway instance is in the **active** state, the policy-based route is created.
|
|
8493
8464
|
* - The **CreateVpnPbrRouteEntry** operation does not support concurrent creation of policy-based routes for the same VPN gateway instance.
|
|
@@ -8571,9 +8542,10 @@ class Client extends openapi_core_1.default {
|
|
|
8571
8542
|
* - Before you create a policy-based route, make sure that you have created an IPsec-VPN connection. For more information, see [CreateVpnConnection](https://help.aliyun.com/document_detail/120391.html).
|
|
8572
8543
|
* - Before you create a policy-based route, we recommend that you familiarize yourself with the limits and matching rules of policy-based routes. For more information, see [Use policy-based routes](https://help.aliyun.com/document_detail/110777.html).
|
|
8573
8544
|
* ### Limits
|
|
8574
|
-
* -
|
|
8575
|
-
*
|
|
8576
|
-
*
|
|
8545
|
+
* - For single-tunnel VPN gateways:
|
|
8546
|
+
* - 0.0.0.0/0 is not supported as the destination CIDR block of a policy-based route.
|
|
8547
|
+
* - CIDR blocks that overlap with 100.64.0.0/10 (including 100.64.0.0/10 itself, its subnets, and parent CIDR blocks that contain it) are not supported as the destination CIDR block of a policy-based route.
|
|
8548
|
+
* - **CreateVpnPbrRouteEntry** is an asynchronous operation. After you send a request, the system returns the policy-based route information, but the route has not been created yet. The system continues to create the route in the background. You can invoke the [DescribeVpnGateway](https://help.aliyun.com/document_detail/73720.html) operation to query the instance status of the VPN gateway to determine the creation status of the policy-based routing node:
|
|
8577
8549
|
* - If the VPN gateway instance is in the **updating** state, the policy-based route is being created.
|
|
8578
8550
|
* - If the VPN gateway instance is in the **active** state, the policy-based route is created.
|
|
8579
8551
|
* - The **CreateVpnPbrRouteEntry** operation does not support concurrent creation of policy-based routes for the same VPN gateway instance.
|
|
@@ -8586,16 +8558,16 @@ class Client extends openapi_core_1.default {
|
|
|
8586
8558
|
return await this.createVpnPbrRouteEntryWithOptions(request, runtime);
|
|
8587
8559
|
}
|
|
8588
8560
|
/**
|
|
8589
|
-
* Creates a destination route for a VPN gateway instance
|
|
8561
|
+
* Creates a destination route for a VPN gateway instance. After the destination route is created, the VPN gateway instance matches the destination route based on the destination IP address of the traffic and then forwards the traffic based on the matched destination route.
|
|
8590
8562
|
*
|
|
8591
8563
|
* @remarks
|
|
8592
8564
|
* ### Before you begin
|
|
8593
8565
|
* - Before you create a destination route, make sure that you have created an IPsec-VPN connection. For more information, see [CreateVpnConnection](https://help.aliyun.com/document_detail/2526947.html).
|
|
8594
8566
|
* - Before you create a destination route, we recommend that you understand the matching rules of destination routes. For more information, see [Configure destination routes](https://help.aliyun.com/document_detail/112476.html).
|
|
8595
8567
|
* ### Limits
|
|
8596
|
-
* -
|
|
8597
|
-
* -
|
|
8598
|
-
* - The **CreateVpnRouteEntry** operation is asynchronous. After you send a request, the system returns the destination
|
|
8568
|
+
* - 0.0.0.0/0 is not supported as the destination CIDR block of a destination route.
|
|
8569
|
+
* - For single-tunnel VPN gateways, CIDR blocks that overlap with 100.64.0.0/10 (including 100.64.0.0/10 itself, its subnets, and parent CIDR blocks that contain it) are not supported as the destination CIDR block of a destination route.
|
|
8570
|
+
* - The **CreateVpnRouteEntry** operation is asynchronous. After you send a request, the system returns the destination routing configuration but the destination route is not yet created. The creation node is still running in the background. You can invoke [DescribeVpnGateway](https://help.aliyun.com/document_detail/73720.html) to query the creation status of the destination route:
|
|
8599
8571
|
* - If the VPN gateway instance is in the **updating** state, the destination route is being created.
|
|
8600
8572
|
* - If the VPN gateway instance is in the **active** state, the destination route is created.
|
|
8601
8573
|
* - The **CreateVpnRouteEntry** operation does not support concurrent creation of destination routes for the same VPN gateway.
|
|
@@ -8666,16 +8638,16 @@ class Client extends openapi_core_1.default {
|
|
|
8666
8638
|
return $dara.cast(await this.callApi(params, req, runtime), new $_model.CreateVpnRouteEntryResponse({}));
|
|
8667
8639
|
}
|
|
8668
8640
|
/**
|
|
8669
|
-
* Creates a destination route for a VPN gateway instance
|
|
8641
|
+
* Creates a destination route for a VPN gateway instance. After the destination route is created, the VPN gateway instance matches the destination route based on the destination IP address of the traffic and then forwards the traffic based on the matched destination route.
|
|
8670
8642
|
*
|
|
8671
8643
|
* @remarks
|
|
8672
8644
|
* ### Before you begin
|
|
8673
8645
|
* - Before you create a destination route, make sure that you have created an IPsec-VPN connection. For more information, see [CreateVpnConnection](https://help.aliyun.com/document_detail/2526947.html).
|
|
8674
8646
|
* - Before you create a destination route, we recommend that you understand the matching rules of destination routes. For more information, see [Configure destination routes](https://help.aliyun.com/document_detail/112476.html).
|
|
8675
8647
|
* ### Limits
|
|
8676
|
-
* -
|
|
8677
|
-
* -
|
|
8678
|
-
* - The **CreateVpnRouteEntry** operation is asynchronous. After you send a request, the system returns the destination
|
|
8648
|
+
* - 0.0.0.0/0 is not supported as the destination CIDR block of a destination route.
|
|
8649
|
+
* - For single-tunnel VPN gateways, CIDR blocks that overlap with 100.64.0.0/10 (including 100.64.0.0/10 itself, its subnets, and parent CIDR blocks that contain it) are not supported as the destination CIDR block of a destination route.
|
|
8650
|
+
* - The **CreateVpnRouteEntry** operation is asynchronous. After you send a request, the system returns the destination routing configuration but the destination route is not yet created. The creation node is still running in the background. You can invoke [DescribeVpnGateway](https://help.aliyun.com/document_detail/73720.html) to query the creation status of the destination route:
|
|
8679
8651
|
* - If the VPN gateway instance is in the **updating** state, the destination route is being created.
|
|
8680
8652
|
* - If the VPN gateway instance is in the **active** state, the destination route is created.
|
|
8681
8653
|
* - The **CreateVpnRouteEntry** operation does not support concurrent creation of destination routes for the same VPN gateway.
|
|
@@ -10962,16 +10934,16 @@ class Client extends openapi_core_1.default {
|
|
|
10962
10934
|
return await this.deletePublicIpAddressPoolCidrBlockWithOptions(request, runtime);
|
|
10963
10935
|
}
|
|
10964
10936
|
/**
|
|
10965
|
-
*
|
|
10937
|
+
* Deletes custom route entries in a batch.
|
|
10966
10938
|
*
|
|
10967
10939
|
* @remarks
|
|
10968
|
-
* When you call this operation to delete
|
|
10969
|
-
* - Only
|
|
10970
|
-
* -
|
|
10971
|
-
* - The **DeleteRouteEntries** operation is asynchronous. After you send a request, the system returns a request ID,
|
|
10972
|
-
* - If the
|
|
10973
|
-
* - If the specified
|
|
10974
|
-
* - The **DeleteRouteEntries** operation does not support concurrent batch deletion of
|
|
10940
|
+
* When you call this operation to delete route entries, take note of the following items:
|
|
10941
|
+
* - Only route entries in the **Available** state can be deleted.
|
|
10942
|
+
* - Route entries cannot be deleted if the VPC to which the route table belongs has a vSwitch or route entry being created or deleted.
|
|
10943
|
+
* - The **DeleteRouteEntries** operation is asynchronous. After you send a request, the system returns a request ID. However, the route entry is not yet deleted. The deletion task runs in the background. You can call [DescribeRouteEntryList](https://help.aliyun.com/document_detail/138148.html) to query the deletion status of the route entry:
|
|
10944
|
+
* - If the route entry is in the **Deleting** state, the route entry is being deleted.
|
|
10945
|
+
* - If the specified route entry cannot be found, the route entry is deleted.
|
|
10946
|
+
* - The **DeleteRouteEntries** operation does not support concurrent batch deletion of route entries from route tables in the same VPC.
|
|
10975
10947
|
*
|
|
10976
10948
|
* @param request - DeleteRouteEntriesRequest
|
|
10977
10949
|
* @param runtime - runtime options for this request RuntimeOptions
|
|
@@ -11021,16 +10993,16 @@ class Client extends openapi_core_1.default {
|
|
|
11021
10993
|
return $dara.cast(await this.callApi(params, req, runtime), new $_model.DeleteRouteEntriesResponse({}));
|
|
11022
10994
|
}
|
|
11023
10995
|
/**
|
|
11024
|
-
*
|
|
10996
|
+
* Deletes custom route entries in a batch.
|
|
11025
10997
|
*
|
|
11026
10998
|
* @remarks
|
|
11027
|
-
* When you call this operation to delete
|
|
11028
|
-
* - Only
|
|
11029
|
-
* -
|
|
11030
|
-
* - The **DeleteRouteEntries** operation is asynchronous. After you send a request, the system returns a request ID,
|
|
11031
|
-
* - If the
|
|
11032
|
-
* - If the specified
|
|
11033
|
-
* - The **DeleteRouteEntries** operation does not support concurrent batch deletion of
|
|
10999
|
+
* When you call this operation to delete route entries, take note of the following items:
|
|
11000
|
+
* - Only route entries in the **Available** state can be deleted.
|
|
11001
|
+
* - Route entries cannot be deleted if the VPC to which the route table belongs has a vSwitch or route entry being created or deleted.
|
|
11002
|
+
* - The **DeleteRouteEntries** operation is asynchronous. After you send a request, the system returns a request ID. However, the route entry is not yet deleted. The deletion task runs in the background. You can call [DescribeRouteEntryList](https://help.aliyun.com/document_detail/138148.html) to query the deletion status of the route entry:
|
|
11003
|
+
* - If the route entry is in the **Deleting** state, the route entry is being deleted.
|
|
11004
|
+
* - If the specified route entry cannot be found, the route entry is deleted.
|
|
11005
|
+
* - The **DeleteRouteEntries** operation does not support concurrent batch deletion of route entries from route tables in the same VPC.
|
|
11034
11006
|
*
|
|
11035
11007
|
* @param request - DeleteRouteEntriesRequest
|
|
11036
11008
|
* @returns DeleteRouteEntriesResponse
|
|
@@ -11040,14 +11012,14 @@ class Client extends openapi_core_1.default {
|
|
|
11040
11012
|
return await this.deleteRouteEntriesWithOptions(request, runtime);
|
|
11041
11013
|
}
|
|
11042
11014
|
/**
|
|
11043
|
-
* Invokes the DeleteRouteEntry operation to delete a route from the route table of a
|
|
11015
|
+
* Invokes the DeleteRouteEntry operation to delete a route from the route table of a vRouter or Virtual Border Router (VBR).
|
|
11044
11016
|
*
|
|
11045
11017
|
* @remarks
|
|
11046
|
-
* When you call this operation to delete a route, note the following items:
|
|
11018
|
+
* When you call this operation to delete a route, take note of the following items:
|
|
11047
11019
|
* - Only routes in the **Available** state can be deleted.
|
|
11048
|
-
* - A route cannot be deleted
|
|
11020
|
+
* - A route cannot be deleted while the VPC that contains the route table is creating or deleting a vSwitch or route.
|
|
11049
11021
|
* - To delete a route from the route table of a VBR, call the [DescribeRouteEntryList](https://help.aliyun.com/document_detail/138148.html) operation to query the **NextHopId** of the route that you want to delete, and then call this operation to delete the route.
|
|
11050
|
-
* - The **DeleteRouteEntry** operation is asynchronous. After you send a request, the system returns a request ID, but the route has not been deleted yet. The deletion task
|
|
11022
|
+
* - The **DeleteRouteEntry** operation is asynchronous. After you send a request, the system returns a request ID, but the route has not been deleted yet. The deletion task runs in the background. You can call [DescribeRouteEntryList](https://help.aliyun.com/document_detail/138148.html) to query the deletion status of the route:
|
|
11051
11023
|
* - If the route is in the **Deleting** state, the route is being deleted.
|
|
11052
11024
|
* - If the specified route cannot be found, the route is deleted.
|
|
11053
11025
|
* - The **DeleteRouteEntry** operation does not support concurrent deletion of routes from the route table within the same VPC or VBR.
|
|
@@ -11109,14 +11081,14 @@ class Client extends openapi_core_1.default {
|
|
|
11109
11081
|
return $dara.cast(await this.callApi(params, req, runtime), new $_model.DeleteRouteEntryResponse({}));
|
|
11110
11082
|
}
|
|
11111
11083
|
/**
|
|
11112
|
-
* Invokes the DeleteRouteEntry operation to delete a route from the route table of a
|
|
11084
|
+
* Invokes the DeleteRouteEntry operation to delete a route from the route table of a vRouter or Virtual Border Router (VBR).
|
|
11113
11085
|
*
|
|
11114
11086
|
* @remarks
|
|
11115
|
-
* When you call this operation to delete a route, note the following items:
|
|
11087
|
+
* When you call this operation to delete a route, take note of the following items:
|
|
11116
11088
|
* - Only routes in the **Available** state can be deleted.
|
|
11117
|
-
* - A route cannot be deleted
|
|
11089
|
+
* - A route cannot be deleted while the VPC that contains the route table is creating or deleting a vSwitch or route.
|
|
11118
11090
|
* - To delete a route from the route table of a VBR, call the [DescribeRouteEntryList](https://help.aliyun.com/document_detail/138148.html) operation to query the **NextHopId** of the route that you want to delete, and then call this operation to delete the route.
|
|
11119
|
-
* - The **DeleteRouteEntry** operation is asynchronous. After you send a request, the system returns a request ID, but the route has not been deleted yet. The deletion task
|
|
11091
|
+
* - The **DeleteRouteEntry** operation is asynchronous. After you send a request, the system returns a request ID, but the route has not been deleted yet. The deletion task runs in the background. You can call [DescribeRouteEntryList](https://help.aliyun.com/document_detail/138148.html) to query the deletion status of the route:
|
|
11120
11092
|
* - If the route is in the **Deleting** state, the route is being deleted.
|
|
11121
11093
|
* - If the specified route cannot be found, the route is deleted.
|
|
11122
11094
|
* - The **DeleteRouteEntry** operation does not support concurrent deletion of routes from the route table within the same VPC or VBR.
|
|
@@ -24126,7 +24098,7 @@ class Client extends openapi_core_1.default {
|
|
|
24126
24098
|
return await this.modifyPhysicalConnectionAttributeWithOptions(request, runtime);
|
|
24127
24099
|
}
|
|
24128
24100
|
/**
|
|
24129
|
-
*
|
|
24101
|
+
* Calls the ModifyRouteEntry operation to modify the name, description, and next hop of a custom route entry.
|
|
24130
24102
|
*
|
|
24131
24103
|
* @remarks
|
|
24132
24104
|
* - The **ModifyRouteEntry** operation does not support concurrent modifications to the name and description of the same custom route entry.
|
|
@@ -24195,7 +24167,7 @@ class Client extends openapi_core_1.default {
|
|
|
24195
24167
|
return $dara.cast(await this.callApi(params, req, runtime), new $_model.ModifyRouteEntryResponse({}));
|
|
24196
24168
|
}
|
|
24197
24169
|
/**
|
|
24198
|
-
*
|
|
24170
|
+
* Calls the ModifyRouteEntry operation to modify the name, description, and next hop of a custom route entry.
|
|
24199
24171
|
*
|
|
24200
24172
|
* @remarks
|
|
24201
24173
|
* - The **ModifyRouteEntry** operation does not support concurrent modifications to the name and description of the same custom route entry.
|
|
@@ -24852,6 +24824,9 @@ class Client extends openapi_core_1.default {
|
|
|
24852
24824
|
if (!$dara.isNull(request.ipv6CidrBlock)) {
|
|
24853
24825
|
query["Ipv6CidrBlock"] = request.ipv6CidrBlock;
|
|
24854
24826
|
}
|
|
24827
|
+
if (!$dara.isNull(request.ipv6CidrMask)) {
|
|
24828
|
+
query["Ipv6CidrMask"] = request.ipv6CidrMask;
|
|
24829
|
+
}
|
|
24855
24830
|
if (!$dara.isNull(request.ownerAccount)) {
|
|
24856
24831
|
query["OwnerAccount"] = request.ownerAccount;
|
|
24857
24832
|
}
|
|
@@ -27279,17 +27254,17 @@ class Client extends openapi_core_1.default {
|
|
|
27279
27254
|
return await this.replaceVpcDhcpOptionsSetWithOptions(request, runtime);
|
|
27280
27255
|
}
|
|
27281
27256
|
/**
|
|
27282
|
-
*
|
|
27257
|
+
* Redeploys the latest prefix list by calling the RetryVpcPrefixListAssociation operation.
|
|
27283
27258
|
*
|
|
27284
27259
|
* @remarks
|
|
27285
|
-
* - After you modify the information of a prefix list instance, if the route table associated with the prefix list instance does not automatically update the prefix list instance information, you can call this operation to
|
|
27286
|
-
* - The **RetryVpcPrefixListAssociation** operation is asynchronous. After you send a request, the system returns a request ID,
|
|
27287
|
-
* - If the
|
|
27288
|
-
* - If the
|
|
27289
|
-
* - If the
|
|
27290
|
-
* - The **RetryVpcPrefixListAssociation** operation does not support concurrent retry
|
|
27260
|
+
* - After you modify the information of a prefix list instance, if the route table associated with the prefix list instance does not automatically update the prefix list instance information, you can call this operation to redeploy the latest prefix list instance to the associated route table.
|
|
27261
|
+
* - The **RetryVpcPrefixListAssociation** operation is asynchronous. After you send a request, the system returns a request ID. However, the latest prefix list instance is not yet redeployed, and the redeployment task is still running in the background. You can call [GetVpcPrefixListAssociations](https://help.aliyun.com/document_detail/445478.html) to query the latest deployment status of the prefix list instance:
|
|
27262
|
+
* - If the deployment status of the prefix list instance is **Modifying**, the latest prefix list instance is being redeployed.
|
|
27263
|
+
* - If the deployment status of the prefix list instance is **ModifyFailed**, the latest prefix list instance failed to be redeployed.
|
|
27264
|
+
* - If the deployment status of the prefix list instance is **Created**, the latest prefix list instance is redeployed.
|
|
27265
|
+
* - The **RetryVpcPrefixListAssociation** operation does not support concurrent retry of redeploying the latest prefix list instance for the same prefix list.
|
|
27291
27266
|
* ## Scenarios
|
|
27292
|
-
* When you modify a prefix list instance, the modification succeeds as long as the CIDR blocks are valid, no conflicting CIDR blocks exist, and the maximum number of entries for the prefix list instance is not exceeded. However, the reference may fail due to issues on the referencing side, such as quota limits or a route conflict with existing routing entries. After you resolve the
|
|
27267
|
+
* When you modify a prefix list instance, the modification succeeds as long as the CIDR blocks are valid, no conflicting CIDR blocks exist, and the maximum number of entries for the prefix list instance is not exceeded. However, the reference may fail due to issues on the referencing side, such as quota limits or a route conflict with existing routing entries. After you resolve the issue on the referencing side, call the **RetryVpcPrefixListAssociation** operation to redeploy the latest prefix list instance.
|
|
27293
27268
|
*
|
|
27294
27269
|
* @param request - RetryVpcPrefixListAssociationRequest
|
|
27295
27270
|
* @param runtime - runtime options for this request RuntimeOptions
|
|
@@ -27345,17 +27320,17 @@ class Client extends openapi_core_1.default {
|
|
|
27345
27320
|
return $dara.cast(await this.callApi(params, req, runtime), new $_model.RetryVpcPrefixListAssociationResponse({}));
|
|
27346
27321
|
}
|
|
27347
27322
|
/**
|
|
27348
|
-
*
|
|
27323
|
+
* Redeploys the latest prefix list by calling the RetryVpcPrefixListAssociation operation.
|
|
27349
27324
|
*
|
|
27350
27325
|
* @remarks
|
|
27351
|
-
* - After you modify the information of a prefix list instance, if the route table associated with the prefix list instance does not automatically update the prefix list instance information, you can call this operation to
|
|
27352
|
-
* - The **RetryVpcPrefixListAssociation** operation is asynchronous. After you send a request, the system returns a request ID,
|
|
27353
|
-
* - If the
|
|
27354
|
-
* - If the
|
|
27355
|
-
* - If the
|
|
27356
|
-
* - The **RetryVpcPrefixListAssociation** operation does not support concurrent retry
|
|
27326
|
+
* - After you modify the information of a prefix list instance, if the route table associated with the prefix list instance does not automatically update the prefix list instance information, you can call this operation to redeploy the latest prefix list instance to the associated route table.
|
|
27327
|
+
* - The **RetryVpcPrefixListAssociation** operation is asynchronous. After you send a request, the system returns a request ID. However, the latest prefix list instance is not yet redeployed, and the redeployment task is still running in the background. You can call [GetVpcPrefixListAssociations](https://help.aliyun.com/document_detail/445478.html) to query the latest deployment status of the prefix list instance:
|
|
27328
|
+
* - If the deployment status of the prefix list instance is **Modifying**, the latest prefix list instance is being redeployed.
|
|
27329
|
+
* - If the deployment status of the prefix list instance is **ModifyFailed**, the latest prefix list instance failed to be redeployed.
|
|
27330
|
+
* - If the deployment status of the prefix list instance is **Created**, the latest prefix list instance is redeployed.
|
|
27331
|
+
* - The **RetryVpcPrefixListAssociation** operation does not support concurrent retry of redeploying the latest prefix list instance for the same prefix list.
|
|
27357
27332
|
* ## Scenarios
|
|
27358
|
-
* When you modify a prefix list instance, the modification succeeds as long as the CIDR blocks are valid, no conflicting CIDR blocks exist, and the maximum number of entries for the prefix list instance is not exceeded. However, the reference may fail due to issues on the referencing side, such as quota limits or a route conflict with existing routing entries. After you resolve the
|
|
27333
|
+
* When you modify a prefix list instance, the modification succeeds as long as the CIDR blocks are valid, no conflicting CIDR blocks exist, and the maximum number of entries for the prefix list instance is not exceeded. However, the reference may fail due to issues on the referencing side, such as quota limits or a route conflict with existing routing entries. After you resolve the issue on the referencing side, call the **RetryVpcPrefixListAssociation** operation to redeploy the latest prefix list instance.
|
|
27359
27334
|
*
|
|
27360
27335
|
* @param request - RetryVpcPrefixListAssociationRequest
|
|
27361
27336
|
* @returns RetryVpcPrefixListAssociationResponse
|
|
@@ -28804,7 +28779,7 @@ class Client extends openapi_core_1.default {
|
|
|
28804
28779
|
return await this.untagResourcesForExpressConnectWithOptions(request, runtime);
|
|
28805
28780
|
}
|
|
28806
28781
|
/**
|
|
28807
|
-
* Modifies the configuration of a DHCP options set.
|
|
28782
|
+
* Modifies the configuration of a DHCP options set by calling the UpdateDhcpOptionsSetAttribute operation.
|
|
28808
28783
|
*
|
|
28809
28784
|
* @param request - UpdateDhcpOptionsSetAttributeRequest
|
|
28810
28785
|
* @param runtime - runtime options for this request RuntimeOptions
|
|
@@ -28872,7 +28847,7 @@ class Client extends openapi_core_1.default {
|
|
|
28872
28847
|
return $dara.cast(await this.callApi(params, req, runtime), new $_model.UpdateDhcpOptionsSetAttributeResponse({}));
|
|
28873
28848
|
}
|
|
28874
28849
|
/**
|
|
28875
|
-
* Modifies the configuration of a DHCP options set.
|
|
28850
|
+
* Modifies the configuration of a DHCP options set by calling the UpdateDhcpOptionsSetAttribute operation.
|
|
28876
28851
|
*
|
|
28877
28852
|
* @param request - UpdateDhcpOptionsSetAttributeRequest
|
|
28878
28853
|
* @returns UpdateDhcpOptionsSetAttributeResponse
|