@alicloud/ess20220222 1.8.4 → 1.8.6

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.js CHANGED
@@ -51,6 +51,7 @@ exports.TagResourcesRequestTags = exports.StartInstanceRefreshRequestDesiredConf
51
51
  /**
52
52
  */
53
53
  const tea_util_1 = __importStar(require("@alicloud/tea-util")), $Util = tea_util_1;
54
+ const gateway_pop_1 = __importDefault(require("@alicloud/gateway-pop"));
54
55
  const openapi_client_1 = __importStar(require("@alicloud/openapi-client")), $OpenApi = openapi_client_1;
55
56
  const openapi_util_1 = __importDefault(require("@alicloud/openapi-util"));
56
57
  const endpoint_util_1 = __importDefault(require("@alicloud/endpoint-util"));
@@ -6195,6 +6196,7 @@ class ModifyScheduledTaskRequest extends $tea.Model {
6195
6196
  recurrenceEndTime: 'RecurrenceEndTime',
6196
6197
  recurrenceType: 'RecurrenceType',
6197
6198
  recurrenceValue: 'RecurrenceValue',
6199
+ regionId: 'RegionId',
6198
6200
  resourceOwnerAccount: 'ResourceOwnerAccount',
6199
6201
  resourceOwnerId: 'ResourceOwnerId',
6200
6202
  scalingGroupId: 'ScalingGroupId',
@@ -6217,6 +6219,7 @@ class ModifyScheduledTaskRequest extends $tea.Model {
6217
6219
  recurrenceEndTime: 'string',
6218
6220
  recurrenceType: 'string',
6219
6221
  recurrenceValue: 'string',
6222
+ regionId: 'string',
6220
6223
  resourceOwnerAccount: 'string',
6221
6224
  resourceOwnerId: 'number',
6222
6225
  scalingGroupId: 'string',
@@ -13802,6 +13805,9 @@ exports.TagResourcesRequestTags = TagResourcesRequestTags;
13802
13805
  class Client extends openapi_client_1.default {
13803
13806
  constructor(config) {
13804
13807
  super(config);
13808
+ this._productId = "Ess";
13809
+ let gatewayClient = new gateway_pop_1.default();
13810
+ this._spi = gatewayClient;
13805
13811
  this._endpointRule = "regional";
13806
13812
  this._endpointMap = {
13807
13813
  'cn-qingdao': "ess.aliyuncs.com",
@@ -13905,7 +13911,12 @@ class Client extends openapi_client_1.default {
13905
13911
  reqBodyType: "formData",
13906
13912
  bodyType: "json",
13907
13913
  });
13908
- return $tea.cast(await this.callApi(params, req, runtime), new ApplyEciScalingConfigurationResponse({}));
13914
+ if (tea_util_1.default.isUnset(this._signatureVersion) || !tea_util_1.default.equalString(this._signatureVersion, "v4")) {
13915
+ return $tea.cast(await this.callApi(params, req, runtime), new ApplyEciScalingConfigurationResponse({}));
13916
+ }
13917
+ else {
13918
+ return $tea.cast(await this.execute(params, req, runtime), new ApplyEciScalingConfigurationResponse({}));
13919
+ }
13909
13920
  }
13910
13921
  /**
13911
13922
  * Applies a scaling configuration of the Elastic Container Instance type. If you want to create and manage scaling configurations of the Elastic Container Instance type by using a configuration file, you can call the ApplyEciScalingConfiguration operation.
@@ -13989,7 +14000,12 @@ class Client extends openapi_client_1.default {
13989
14000
  reqBodyType: "formData",
13990
14001
  bodyType: "json",
13991
14002
  });
13992
- return $tea.cast(await this.callApi(params, req, runtime), new ApplyScalingGroupResponse({}));
14003
+ if (tea_util_1.default.isUnset(this._signatureVersion) || !tea_util_1.default.equalString(this._signatureVersion, "v4")) {
14004
+ return $tea.cast(await this.callApi(params, req, runtime), new ApplyScalingGroupResponse({}));
14005
+ }
14006
+ else {
14007
+ return $tea.cast(await this.execute(params, req, runtime), new ApplyScalingGroupResponse({}));
14008
+ }
13993
14009
  }
13994
14010
  /**
13995
14011
  * Creates and manages scaling groups by using configuration files. You can call the ApplyScalingGroup operation to create and manage scaling groups by using configuration files with efficiency.
@@ -14085,7 +14101,12 @@ class Client extends openapi_client_1.default {
14085
14101
  reqBodyType: "formData",
14086
14102
  bodyType: "json",
14087
14103
  });
14088
- return $tea.cast(await this.callApi(params, req, runtime), new AttachAlbServerGroupsResponse({}));
14104
+ if (tea_util_1.default.isUnset(this._signatureVersion) || !tea_util_1.default.equalString(this._signatureVersion, "v4")) {
14105
+ return $tea.cast(await this.callApi(params, req, runtime), new AttachAlbServerGroupsResponse({}));
14106
+ }
14107
+ else {
14108
+ return $tea.cast(await this.execute(params, req, runtime), new AttachAlbServerGroupsResponse({}));
14109
+ }
14089
14110
  }
14090
14111
  /**
14091
14112
  * Attaches Application Load Balancer (ALB) server groups to a scaling group. To seamlessly adjust the number of instances in response to changes in your business workload or to maintain the uninterrupted accessibility of your application, you can call the AttachAlbServerGroups operation. By attaching ALB server groups to your scaling group, this operation enables Auto Scaling to automatically tailor your computing capacity to your business needs. Furthermore, it optimizes traffic routing by dynamically allocating incoming requests based on current workload patterns, which significantly improves the stability and performance of your application.
@@ -14162,7 +14183,12 @@ class Client extends openapi_client_1.default {
14162
14183
  reqBodyType: "formData",
14163
14184
  bodyType: "json",
14164
14185
  });
14165
- return $tea.cast(await this.callApi(params, req, runtime), new AttachDBInstancesResponse({}));
14186
+ if (tea_util_1.default.isUnset(this._signatureVersion) || !tea_util_1.default.equalString(this._signatureVersion, "v4")) {
14187
+ return $tea.cast(await this.callApi(params, req, runtime), new AttachDBInstancesResponse({}));
14188
+ }
14189
+ else {
14190
+ return $tea.cast(await this.execute(params, req, runtime), new AttachDBInstancesResponse({}));
14191
+ }
14166
14192
  }
14167
14193
  /**
14168
14194
  * Associates one or more ApsaraDB RDS instances with a scaling group.
@@ -14256,7 +14282,12 @@ class Client extends openapi_client_1.default {
14256
14282
  reqBodyType: "formData",
14257
14283
  bodyType: "json",
14258
14284
  });
14259
- return $tea.cast(await this.callApi(params, req, runtime), new AttachInstancesResponse({}));
14285
+ if (tea_util_1.default.isUnset(this._signatureVersion) || !tea_util_1.default.equalString(this._signatureVersion, "v4")) {
14286
+ return $tea.cast(await this.callApi(params, req, runtime), new AttachInstancesResponse({}));
14287
+ }
14288
+ else {
14289
+ return $tea.cast(await this.execute(params, req, runtime), new AttachInstancesResponse({}));
14290
+ }
14260
14291
  }
14261
14292
  /**
14262
14293
  * Adds instances to a scaling group to provide services or restarts Elastic Compute Service (ECS) instances stopped in Economical Mode to provide services. You can call the AttachInstances operation to add ECS instances, elastic container instances, or third-party instances managed by Alibaba Cloud to your scaling group to provide services. You can also call this operation to restart ECS instances stopped in Economical Mode in your scaling group to provide services.
@@ -14341,7 +14372,12 @@ class Client extends openapi_client_1.default {
14341
14372
  reqBodyType: "formData",
14342
14373
  bodyType: "json",
14343
14374
  });
14344
- return $tea.cast(await this.callApi(params, req, runtime), new AttachLoadBalancersResponse({}));
14375
+ if (tea_util_1.default.isUnset(this._signatureVersion) || !tea_util_1.default.equalString(this._signatureVersion, "v4")) {
14376
+ return $tea.cast(await this.callApi(params, req, runtime), new AttachLoadBalancersResponse({}));
14377
+ }
14378
+ else {
14379
+ return $tea.cast(await this.execute(params, req, runtime), new AttachLoadBalancersResponse({}));
14380
+ }
14345
14381
  }
14346
14382
  /**
14347
14383
  * Attaches load balancers to a scaling group. Auto Scaling supports the attachment of load balancers to scaling groups. Load balancers help distribute the access traffic to the instances in scaling groups, which effectively improves the service performance of the scaling groups. You can call the AttachLoadBalancers operation to attach one or more load balancers to your scaling group.
@@ -14407,7 +14443,12 @@ class Client extends openapi_client_1.default {
14407
14443
  reqBodyType: "formData",
14408
14444
  bodyType: "json",
14409
14445
  });
14410
- return $tea.cast(await this.callApi(params, req, runtime), new AttachServerGroupsResponse({}));
14446
+ if (tea_util_1.default.isUnset(this._signatureVersion) || !tea_util_1.default.equalString(this._signatureVersion, "v4")) {
14447
+ return $tea.cast(await this.callApi(params, req, runtime), new AttachServerGroupsResponse({}));
14448
+ }
14449
+ else {
14450
+ return $tea.cast(await this.execute(params, req, runtime), new AttachServerGroupsResponse({}));
14451
+ }
14411
14452
  }
14412
14453
  /**
14413
14454
  * Attaches server groups to a scaling group. To seamlessly adjust the number of instances in response to changes in your business workload or to maintain the uninterrupted accessibility of your application, you can call the AttachServerGroups operation. By attaching Application Load Balancer (ALB) or Network Load Balancer (NLB) server groups to your scaling group, this operation enables Auto Scaling to automatically tailor your computing capacity to your business needs. Furthermore, it optimizes traffic routing by dynamically allocating incoming requests based on current workload patterns, which significantly improves the stability and performance of your application.
@@ -14481,7 +14522,12 @@ class Client extends openapi_client_1.default {
14481
14522
  reqBodyType: "formData",
14482
14523
  bodyType: "json",
14483
14524
  });
14484
- return $tea.cast(await this.callApi(params, req, runtime), new AttachVServerGroupsResponse({}));
14525
+ if (tea_util_1.default.isUnset(this._signatureVersion) || !tea_util_1.default.equalString(this._signatureVersion, "v4")) {
14526
+ return $tea.cast(await this.callApi(params, req, runtime), new AttachVServerGroupsResponse({}));
14527
+ }
14528
+ else {
14529
+ return $tea.cast(await this.execute(params, req, runtime), new AttachVServerGroupsResponse({}));
14530
+ }
14485
14531
  }
14486
14532
  /**
14487
14533
  * Attaches vServer groups to a scaling group. After a Classic Load Balancer (CLB) instance is attached to your scaling group, the instances in the scaling group are automatically added as backend servers of the CLB instance. These servers then handle requests forwarded by the CLB instance, streamlining the processing of incoming traffic. To direct varying access requests to separate backend servers or to distribute requests based on domain names or URLs, you can call the AttachVServerGroups operation. This operation enables the addition of multiple vServer groups, allowing for efficient management of various backend server configurations tailored to your routing preferences.
@@ -14511,7 +14557,7 @@ class Client extends openapi_client_1.default {
14511
14557
  return await this.attachVServerGroupsWithOptions(request, runtime);
14512
14558
  }
14513
14559
  /**
14514
- * Cancels an instance refresh task. Take note that new instances that are used to replace old instances or that are scaled out still exist after you call this operation.
14560
+ * Cancels an instance refresh task. Take note that instances whose configurations were already updated by running an instance refresh task remain intact even after you cancel the task.
14515
14561
  *
14516
14562
  * @remarks
14517
14563
  * You cannot call this operation to cancel instance refresh tasks that are being rolled back.
@@ -14552,10 +14598,15 @@ class Client extends openapi_client_1.default {
14552
14598
  reqBodyType: "formData",
14553
14599
  bodyType: "json",
14554
14600
  });
14555
- return $tea.cast(await this.callApi(params, req, runtime), new CancelInstanceRefreshResponse({}));
14601
+ if (tea_util_1.default.isUnset(this._signatureVersion) || !tea_util_1.default.equalString(this._signatureVersion, "v4")) {
14602
+ return $tea.cast(await this.callApi(params, req, runtime), new CancelInstanceRefreshResponse({}));
14603
+ }
14604
+ else {
14605
+ return $tea.cast(await this.execute(params, req, runtime), new CancelInstanceRefreshResponse({}));
14606
+ }
14556
14607
  }
14557
14608
  /**
14558
- * Cancels an instance refresh task. Take note that new instances that are used to replace old instances or that are scaled out still exist after you call this operation.
14609
+ * Cancels an instance refresh task. Take note that instances whose configurations were already updated by running an instance refresh task remain intact even after you cancel the task.
14559
14610
  *
14560
14611
  * @remarks
14561
14612
  * You cannot call this operation to cancel instance refresh tasks that are being rolled back.
@@ -14613,7 +14664,12 @@ class Client extends openapi_client_1.default {
14613
14664
  reqBodyType: "formData",
14614
14665
  bodyType: "json",
14615
14666
  });
14616
- return $tea.cast(await this.callApi(params, req, runtime), new ChangeResourceGroupResponse({}));
14667
+ if (tea_util_1.default.isUnset(this._signatureVersion) || !tea_util_1.default.equalString(this._signatureVersion, "v4")) {
14668
+ return $tea.cast(await this.callApi(params, req, runtime), new ChangeResourceGroupResponse({}));
14669
+ }
14670
+ else {
14671
+ return $tea.cast(await this.execute(params, req, runtime), new ChangeResourceGroupResponse({}));
14672
+ }
14617
14673
  }
14618
14674
  /**
14619
14675
  * Changes a resource group. Resource groups are a means to categorize and manage cloud resources, such as scaling groups, based on specific objectives, permissions, or ownership. In large, multifaceted organizations that manage numerous projects and users, this feature adopts a tiered management approach, simplifying management tasks and improving the effectiveness and oversight of resource allocation. You can call the ChangeResourceGroup operation to move your scaling groups from one resource group to another resource group, which facilitates streamlined monitoring and management within the context of the new group. This operation eliminates the need for repetitive and time-consuming cross-service resource queries, thereby enhancing operational efficiency.
@@ -14680,7 +14736,12 @@ class Client extends openapi_client_1.default {
14680
14736
  reqBodyType: "formData",
14681
14737
  bodyType: "json",
14682
14738
  });
14683
- return $tea.cast(await this.callApi(params, req, runtime), new CompleteLifecycleActionResponse({}));
14739
+ if (tea_util_1.default.isUnset(this._signatureVersion) || !tea_util_1.default.equalString(this._signatureVersion, "v4")) {
14740
+ return $tea.cast(await this.callApi(params, req, runtime), new CompleteLifecycleActionResponse({}));
14741
+ }
14742
+ else {
14743
+ return $tea.cast(await this.execute(params, req, runtime), new CompleteLifecycleActionResponse({}));
14744
+ }
14684
14745
  }
14685
14746
  /**
14686
14747
  * Ends the timeout period of a lifecycle hook ahead of schedule. If you have created a lifecycle hook for your scaling group, you can call the CompleteLifecycleAction operation to end the timeout period of the lifecycle hook ahead of schedule based on your business requirements.
@@ -14783,7 +14844,12 @@ class Client extends openapi_client_1.default {
14783
14844
  reqBodyType: "formData",
14784
14845
  bodyType: "json",
14785
14846
  });
14786
- return $tea.cast(await this.callApi(params, req, runtime), new CreateAlarmResponse({}));
14847
+ if (tea_util_1.default.isUnset(this._signatureVersion) || !tea_util_1.default.equalString(this._signatureVersion, "v4")) {
14848
+ return $tea.cast(await this.callApi(params, req, runtime), new CreateAlarmResponse({}));
14849
+ }
14850
+ else {
14851
+ return $tea.cast(await this.execute(params, req, runtime), new CreateAlarmResponse({}));
14852
+ }
14787
14853
  }
14788
14854
  /**
14789
14855
  * Creates event-triggered tasks. If your business encounters unexpected traffic surges or has no specific patterns, you can call the CreateAlarm operation to create an event-triggered task and associate a CloudMonitor metric with the task. This allows you to dynamically adjust the number of Elastic Compute Service (ECS) instances or elastic container instances in your scaling group and keep updated on the real-time metric data, which facilitates cloud resource management and maintenance.
@@ -14803,7 +14869,7 @@ class Client extends openapi_client_1.default {
14803
14869
  return await this.createAlarmWithOptions(request, runtime);
14804
14870
  }
14805
14871
  /**
14806
- * CreateDiagnoseReport
14872
+ * Creates a diagnostic report.
14807
14873
  *
14808
14874
  * @param request - CreateDiagnoseReportRequest
14809
14875
  * @param runtime - runtime options for this request RuntimeOptions
@@ -14826,10 +14892,15 @@ class Client extends openapi_client_1.default {
14826
14892
  reqBodyType: "formData",
14827
14893
  bodyType: "json",
14828
14894
  });
14829
- return $tea.cast(await this.callApi(params, req, runtime), new CreateDiagnoseReportResponse({}));
14895
+ if (tea_util_1.default.isUnset(this._signatureVersion) || !tea_util_1.default.equalString(this._signatureVersion, "v4")) {
14896
+ return $tea.cast(await this.callApi(params, req, runtime), new CreateDiagnoseReportResponse({}));
14897
+ }
14898
+ else {
14899
+ return $tea.cast(await this.execute(params, req, runtime), new CreateDiagnoseReportResponse({}));
14900
+ }
14830
14901
  }
14831
14902
  /**
14832
- * CreateDiagnoseReport
14903
+ * Creates a diagnostic report.
14833
14904
  *
14834
14905
  * @param request - CreateDiagnoseReportRequest
14835
14906
  * @returns CreateDiagnoseReportResponse
@@ -15016,7 +15087,12 @@ class Client extends openapi_client_1.default {
15016
15087
  reqBodyType: "formData",
15017
15088
  bodyType: "json",
15018
15089
  });
15019
- return $tea.cast(await this.callApi(params, req, runtime), new CreateEciScalingConfigurationResponse({}));
15090
+ if (tea_util_1.default.isUnset(this._signatureVersion) || !tea_util_1.default.equalString(this._signatureVersion, "v4")) {
15091
+ return $tea.cast(await this.callApi(params, req, runtime), new CreateEciScalingConfigurationResponse({}));
15092
+ }
15093
+ else {
15094
+ return $tea.cast(await this.execute(params, req, runtime), new CreateEciScalingConfigurationResponse({}));
15095
+ }
15020
15096
  }
15021
15097
  /**
15022
15098
  * Creates a scaling configuration of the Elastic Container Instance type. Auto Scaling uses the scaling configuration as a template to create elastic container instances to meet your business requirements during scale-out events.
@@ -15092,7 +15168,12 @@ class Client extends openapi_client_1.default {
15092
15168
  reqBodyType: "formData",
15093
15169
  bodyType: "json",
15094
15170
  });
15095
- return $tea.cast(await this.callApi(params, req, runtime), new CreateLifecycleHookResponse({}));
15171
+ if (tea_util_1.default.isUnset(this._signatureVersion) || !tea_util_1.default.equalString(this._signatureVersion, "v4")) {
15172
+ return $tea.cast(await this.callApi(params, req, runtime), new CreateLifecycleHookResponse({}));
15173
+ }
15174
+ else {
15175
+ return $tea.cast(await this.execute(params, req, runtime), new CreateLifecycleHookResponse({}));
15176
+ }
15096
15177
  }
15097
15178
  /**
15098
15179
  * Creates one or more lifecycle hooks in a scaling group. A lifecycle hook allows you to execute custom actions like sending notifications or automating script execution at critical stages (such as instance startup and termination) in the lifecycle of an instance. Implementing the lifecycle hook feature allows for finer control and management of instances. For example, you can verify configurations, set up custom tasks, or back up data on your instances when lifecycle hooks take effect, thus enhancing the flexibility and reliability of application deployment.
@@ -15114,9 +15195,9 @@ class Client extends openapi_client_1.default {
15114
15195
  * Creates a notification rule. You can call the CreateNotificationConfiguration operation to create a notification rule to stay informed about scaling events or resource changes. This helps you learn about the dynamic status of your scaling group in real time and further automates the management of scaling events.
15115
15196
  *
15116
15197
  * @remarks
15117
- * You can enable a CloudMonitor system event, Message Service (MNS) queue, or MNS topic to receive notifications. When a scaling event of the specified type or resource change occurs in your scaling group, Auto Scaling automatically sends notifications to CloudMonitor or MNS.
15198
+ * You can specify CloudMonitor system events, Simple Message Queue (SMQ, formerly MNS) topics, or SMQ queues as notification recipients. When a scaling event of the specified type or resource change occurs in your scaling group, Auto Scaling automatically sends notifications to CloudMonitor or SMQ.
15118
15199
  * * You cannot specify the same recipient for notifications of different event types in a scaling group.
15119
- * For example, you cannot enable the same CloudMonitor system event, MNS topic, or MNS queue to receive notifications of different event types in a scaling group.
15200
+ * For example, you cannot enable the same CloudMonitor system event, SMQ topic, or SMQ queue to receive notifications of different event types in a scaling group.
15120
15201
  *
15121
15202
  * @param request - CreateNotificationConfigurationRequest
15122
15203
  * @param runtime - runtime options for this request RuntimeOptions
@@ -15160,15 +15241,20 @@ class Client extends openapi_client_1.default {
15160
15241
  reqBodyType: "formData",
15161
15242
  bodyType: "json",
15162
15243
  });
15163
- return $tea.cast(await this.callApi(params, req, runtime), new CreateNotificationConfigurationResponse({}));
15244
+ if (tea_util_1.default.isUnset(this._signatureVersion) || !tea_util_1.default.equalString(this._signatureVersion, "v4")) {
15245
+ return $tea.cast(await this.callApi(params, req, runtime), new CreateNotificationConfigurationResponse({}));
15246
+ }
15247
+ else {
15248
+ return $tea.cast(await this.execute(params, req, runtime), new CreateNotificationConfigurationResponse({}));
15249
+ }
15164
15250
  }
15165
15251
  /**
15166
15252
  * Creates a notification rule. You can call the CreateNotificationConfiguration operation to create a notification rule to stay informed about scaling events or resource changes. This helps you learn about the dynamic status of your scaling group in real time and further automates the management of scaling events.
15167
15253
  *
15168
15254
  * @remarks
15169
- * You can enable a CloudMonitor system event, Message Service (MNS) queue, or MNS topic to receive notifications. When a scaling event of the specified type or resource change occurs in your scaling group, Auto Scaling automatically sends notifications to CloudMonitor or MNS.
15255
+ * You can specify CloudMonitor system events, Simple Message Queue (SMQ, formerly MNS) topics, or SMQ queues as notification recipients. When a scaling event of the specified type or resource change occurs in your scaling group, Auto Scaling automatically sends notifications to CloudMonitor or SMQ.
15170
15256
  * * You cannot specify the same recipient for notifications of different event types in a scaling group.
15171
- * For example, you cannot enable the same CloudMonitor system event, MNS topic, or MNS queue to receive notifications of different event types in a scaling group.
15257
+ * For example, you cannot enable the same CloudMonitor system event, SMQ topic, or SMQ queue to receive notifications of different event types in a scaling group.
15172
15258
  *
15173
15259
  * @param request - CreateNotificationConfigurationRequest
15174
15260
  * @returns CreateNotificationConfigurationResponse
@@ -15395,7 +15481,12 @@ class Client extends openapi_client_1.default {
15395
15481
  reqBodyType: "formData",
15396
15482
  bodyType: "json",
15397
15483
  });
15398
- return $tea.cast(await this.callApi(params, req, runtime), new CreateScalingConfigurationResponse({}));
15484
+ if (tea_util_1.default.isUnset(this._signatureVersion) || !tea_util_1.default.equalString(this._signatureVersion, "v4")) {
15485
+ return $tea.cast(await this.callApi(params, req, runtime), new CreateScalingConfigurationResponse({}));
15486
+ }
15487
+ else {
15488
+ return $tea.cast(await this.execute(params, req, runtime), new CreateScalingConfigurationResponse({}));
15489
+ }
15399
15490
  }
15400
15491
  /**
15401
15492
  * Creates scaling configurations. When you call the CreateScalingConfiguration operation, you can specify the scaling group ID, instance type, and image to create a scaling configuration of the Elastic Compute Service (ECS) type.
@@ -15605,7 +15696,12 @@ class Client extends openapi_client_1.default {
15605
15696
  reqBodyType: "formData",
15606
15697
  bodyType: "json",
15607
15698
  });
15608
- return $tea.cast(await this.callApi(params, req, runtime), new CreateScalingGroupResponse({}));
15699
+ if (tea_util_1.default.isUnset(this._signatureVersion) || !tea_util_1.default.equalString(this._signatureVersion, "v4")) {
15700
+ return $tea.cast(await this.callApi(params, req, runtime), new CreateScalingGroupResponse({}));
15701
+ }
15702
+ else {
15703
+ return $tea.cast(await this.execute(params, req, runtime), new CreateScalingGroupResponse({}));
15704
+ }
15609
15705
  }
15610
15706
  /**
15611
15707
  * Creates a scaling group. You can call the CreateScalingGroup operation to automate the adjustment of computing power of a specific type based on your business requirements and scaling polices.
@@ -15760,7 +15856,12 @@ class Client extends openapi_client_1.default {
15760
15856
  reqBodyType: "formData",
15761
15857
  bodyType: "json",
15762
15858
  });
15763
- return $tea.cast(await this.callApi(params, req, runtime), new CreateScalingRuleResponse({}));
15859
+ if (tea_util_1.default.isUnset(this._signatureVersion) || !tea_util_1.default.equalString(this._signatureVersion, "v4")) {
15860
+ return $tea.cast(await this.callApi(params, req, runtime), new CreateScalingRuleResponse({}));
15861
+ }
15862
+ else {
15863
+ return $tea.cast(await this.execute(params, req, runtime), new CreateScalingRuleResponse({}));
15864
+ }
15764
15865
  }
15765
15866
  /**
15766
15867
  * Creates a scaling rule. The purpose of a scaling rule varies based on its type. You can use a scaling rule to trigger a scaling activity or adjust the boundary values for a scaling group. You can call the CreateScalingRule operation to create different types of scaling rules based on your business requirements. For example, if your business requires only automatic adjustment of the boundary values for your scaling group, you can call this operation to create a predictive scaling rule.
@@ -15872,7 +15973,12 @@ class Client extends openapi_client_1.default {
15872
15973
  reqBodyType: "formData",
15873
15974
  bodyType: "json",
15874
15975
  });
15875
- return $tea.cast(await this.callApi(params, req, runtime), new CreateScheduledTaskResponse({}));
15976
+ if (tea_util_1.default.isUnset(this._signatureVersion) || !tea_util_1.default.equalString(this._signatureVersion, "v4")) {
15977
+ return $tea.cast(await this.callApi(params, req, runtime), new CreateScheduledTaskResponse({}));
15978
+ }
15979
+ else {
15980
+ return $tea.cast(await this.execute(params, req, runtime), new CreateScheduledTaskResponse({}));
15981
+ }
15876
15982
  }
15877
15983
  /**
15878
15984
  * Creates a scheduled task. A scheduled task is a type of scaling task that enables automatic execution of a specific scaling rule at a specified point in time. You can call the CreateScheduledTask operation to create a scheduled task to implement automatic scaling of computing resources. This ensures your business continuity and minimizes resource costs.
@@ -15934,7 +16040,12 @@ class Client extends openapi_client_1.default {
15934
16040
  reqBodyType: "formData",
15935
16041
  bodyType: "json",
15936
16042
  });
15937
- return $tea.cast(await this.callApi(params, req, runtime), new DeactivateScalingConfigurationResponse({}));
16043
+ if (tea_util_1.default.isUnset(this._signatureVersion) || !tea_util_1.default.equalString(this._signatureVersion, "v4")) {
16044
+ return $tea.cast(await this.callApi(params, req, runtime), new DeactivateScalingConfigurationResponse({}));
16045
+ }
16046
+ else {
16047
+ return $tea.cast(await this.execute(params, req, runtime), new DeactivateScalingConfigurationResponse({}));
16048
+ }
15938
16049
  }
15939
16050
  /**
15940
16051
  * Deactivates a scaling configuration.
@@ -15985,7 +16096,12 @@ class Client extends openapi_client_1.default {
15985
16096
  reqBodyType: "formData",
15986
16097
  bodyType: "json",
15987
16098
  });
15988
- return $tea.cast(await this.callApi(params, req, runtime), new DeleteAlarmResponse({}));
16099
+ if (tea_util_1.default.isUnset(this._signatureVersion) || !tea_util_1.default.equalString(this._signatureVersion, "v4")) {
16100
+ return $tea.cast(await this.callApi(params, req, runtime), new DeleteAlarmResponse({}));
16101
+ }
16102
+ else {
16103
+ return $tea.cast(await this.execute(params, req, runtime), new DeleteAlarmResponse({}));
16104
+ }
15989
16105
  }
15990
16106
  /**
15991
16107
  * Deletes an event-triggered task. If your business pattern is unpredictable or prone to unforeseen traffic spikes, you can create event-triggered tasks by associating CloudMonitor metrics to effectively monitor fluctuations in your business workload. Upon detecting that the criteria for alerts, as specified in event-triggered tasks, are fulfilled, Auto Scaling promptly issues alerts and executes the scaling rules predefined within those tasks. This process occurs within the predefined effective time windows of the tasks, thereby facilitating the automatic increase or decrease of Elastic Compute Service (ECS) instances or elastic container instances within your scaling groups. Ultimately, this mechanism ensures the dynamic optimization of resources based on real-time workload demands. If you no longer need an event-triggered task, you can call the DeleteAlarm operation to delete it.
@@ -16041,7 +16157,12 @@ class Client extends openapi_client_1.default {
16041
16157
  reqBodyType: "formData",
16042
16158
  bodyType: "json",
16043
16159
  });
16044
- return $tea.cast(await this.callApi(params, req, runtime), new DeleteEciScalingConfigurationResponse({}));
16160
+ if (tea_util_1.default.isUnset(this._signatureVersion) || !tea_util_1.default.equalString(this._signatureVersion, "v4")) {
16161
+ return $tea.cast(await this.callApi(params, req, runtime), new DeleteEciScalingConfigurationResponse({}));
16162
+ }
16163
+ else {
16164
+ return $tea.cast(await this.execute(params, req, runtime), new DeleteEciScalingConfigurationResponse({}));
16165
+ }
16045
16166
  }
16046
16167
  /**
16047
16168
  * Deletes a scaling configuration of the Elastic Container Instance type. If the scaling configuration of a scaling group is in the Inactive state and the scaling group contains no elastic container instances created from the scaling configuration, you can call the DeleteEciScalingConfiguration operation to delete the scaling configuration to free up the scaling configuration quota.
@@ -16108,7 +16229,12 @@ class Client extends openapi_client_1.default {
16108
16229
  reqBodyType: "formData",
16109
16230
  bodyType: "json",
16110
16231
  });
16111
- return $tea.cast(await this.callApi(params, req, runtime), new DeleteLifecycleHookResponse({}));
16232
+ if (tea_util_1.default.isUnset(this._signatureVersion) || !tea_util_1.default.equalString(this._signatureVersion, "v4")) {
16233
+ return $tea.cast(await this.callApi(params, req, runtime), new DeleteLifecycleHookResponse({}));
16234
+ }
16235
+ else {
16236
+ return $tea.cast(await this.execute(params, req, runtime), new DeleteLifecycleHookResponse({}));
16237
+ }
16112
16238
  }
16113
16239
  /**
16114
16240
  * Deletes a lifecycle hook. If you no longer require a lifecycle hook, you can call the DeleteLifecycleHook operation to delete it, which frees up the lifecycle hook quota.
@@ -16164,7 +16290,12 @@ class Client extends openapi_client_1.default {
16164
16290
  reqBodyType: "formData",
16165
16291
  bodyType: "json",
16166
16292
  });
16167
- return $tea.cast(await this.callApi(params, req, runtime), new DeleteNotificationConfigurationResponse({}));
16293
+ if (tea_util_1.default.isUnset(this._signatureVersion) || !tea_util_1.default.equalString(this._signatureVersion, "v4")) {
16294
+ return $tea.cast(await this.callApi(params, req, runtime), new DeleteNotificationConfigurationResponse({}));
16295
+ }
16296
+ else {
16297
+ return $tea.cast(await this.execute(params, req, runtime), new DeleteNotificationConfigurationResponse({}));
16298
+ }
16168
16299
  }
16169
16300
  /**
16170
16301
  * Deletes event notification rules. The event notification feature facilitates efficient issue identification and event management by automatically forwarding notifications from Auto Scaling to designated endpoints such as CloudMonitor or Message Service (MNS) topics and queues. If you no longer require an event notification rule, you can call the DeleteNotificationConfiguration operation to delete it.
@@ -16217,7 +16348,12 @@ class Client extends openapi_client_1.default {
16217
16348
  reqBodyType: "formData",
16218
16349
  bodyType: "json",
16219
16350
  });
16220
- return $tea.cast(await this.callApi(params, req, runtime), new DeleteScalingConfigurationResponse({}));
16351
+ if (tea_util_1.default.isUnset(this._signatureVersion) || !tea_util_1.default.equalString(this._signatureVersion, "v4")) {
16352
+ return $tea.cast(await this.callApi(params, req, runtime), new DeleteScalingConfigurationResponse({}));
16353
+ }
16354
+ else {
16355
+ return $tea.cast(await this.execute(params, req, runtime), new DeleteScalingConfigurationResponse({}));
16356
+ }
16221
16357
  }
16222
16358
  /**
16223
16359
  * Deletes a scaling configuration that is used to create Elastic Compute Service (ECS) instances.
@@ -16288,7 +16424,12 @@ class Client extends openapi_client_1.default {
16288
16424
  reqBodyType: "formData",
16289
16425
  bodyType: "json",
16290
16426
  });
16291
- return $tea.cast(await this.callApi(params, req, runtime), new DeleteScalingGroupResponse({}));
16427
+ if (tea_util_1.default.isUnset(this._signatureVersion) || !tea_util_1.default.equalString(this._signatureVersion, "v4")) {
16428
+ return $tea.cast(await this.callApi(params, req, runtime), new DeleteScalingGroupResponse({}));
16429
+ }
16430
+ else {
16431
+ return $tea.cast(await this.execute(params, req, runtime), new DeleteScalingGroupResponse({}));
16432
+ }
16292
16433
  }
16293
16434
  /**
16294
16435
  * Deletes a scaling group. If you want to enable policy-based automatic addition or removal of instances of a specific type to meet evolving business requirements, you can create scaling groups to manage your computing power with ease. The computing power refers to the instances that provide the computing capability. If you no longer require a scaling group, you can call the DeleteScalingGroup operation to delete it to free up the scaling group quota.
@@ -16351,7 +16492,12 @@ class Client extends openapi_client_1.default {
16351
16492
  reqBodyType: "formData",
16352
16493
  bodyType: "json",
16353
16494
  });
16354
- return $tea.cast(await this.callApi(params, req, runtime), new DeleteScalingRuleResponse({}));
16495
+ if (tea_util_1.default.isUnset(this._signatureVersion) || !tea_util_1.default.equalString(this._signatureVersion, "v4")) {
16496
+ return $tea.cast(await this.callApi(params, req, runtime), new DeleteScalingRuleResponse({}));
16497
+ }
16498
+ else {
16499
+ return $tea.cast(await this.execute(params, req, runtime), new DeleteScalingRuleResponse({}));
16500
+ }
16355
16501
  }
16356
16502
  /**
16357
16503
  * Deletes a scaling rule.
@@ -16402,7 +16548,12 @@ class Client extends openapi_client_1.default {
16402
16548
  reqBodyType: "formData",
16403
16549
  bodyType: "json",
16404
16550
  });
16405
- return $tea.cast(await this.callApi(params, req, runtime), new DeleteScheduledTaskResponse({}));
16551
+ if (tea_util_1.default.isUnset(this._signatureVersion) || !tea_util_1.default.equalString(this._signatureVersion, "v4")) {
16552
+ return $tea.cast(await this.callApi(params, req, runtime), new DeleteScheduledTaskResponse({}));
16553
+ }
16554
+ else {
16555
+ return $tea.cast(await this.execute(params, req, runtime), new DeleteScheduledTaskResponse({}));
16556
+ }
16406
16557
  }
16407
16558
  /**
16408
16559
  * Deletes scheduled tasks. For workloads with predictable patterns, you can create scheduled tasks to align with your business requirements and optimize resource utilization for cost savings. These tasks automatically ensure that sufficient computing resources are provisioned in anticipation of peak hours and efficiently release unused resources during off-peak hours, thereby streamlining operational efficiency and reducing expenses. If you no longer require a scheduled task, you can call the DeleteScheduledTask operation to delete it.
@@ -16471,7 +16622,12 @@ class Client extends openapi_client_1.default {
16471
16622
  reqBodyType: "formData",
16472
16623
  bodyType: "json",
16473
16624
  });
16474
- return $tea.cast(await this.callApi(params, req, runtime), new DescribeAlarmsResponse({}));
16625
+ if (tea_util_1.default.isUnset(this._signatureVersion) || !tea_util_1.default.equalString(this._signatureVersion, "v4")) {
16626
+ return $tea.cast(await this.callApi(params, req, runtime), new DescribeAlarmsResponse({}));
16627
+ }
16628
+ else {
16629
+ return $tea.cast(await this.execute(params, req, runtime), new DescribeAlarmsResponse({}));
16630
+ }
16475
16631
  }
16476
16632
  /**
16477
16633
  * Queries event-triggered tasks. You can call the DescribeAlarms operation to learn about the configurations of event-triggered tasks and keep updated on monitoring data changes. This helps you troubleshoot system resource issues at the earliest opportunity and ensures system stability and reliability.
@@ -16519,7 +16675,12 @@ class Client extends openapi_client_1.default {
16519
16675
  reqBodyType: "formData",
16520
16676
  bodyType: "json",
16521
16677
  });
16522
- return $tea.cast(await this.callApi(params, req, runtime), new DescribeAlertConfigurationResponse({}));
16678
+ if (tea_util_1.default.isUnset(this._signatureVersion) || !tea_util_1.default.equalString(this._signatureVersion, "v4")) {
16679
+ return $tea.cast(await this.callApi(params, req, runtime), new DescribeAlertConfigurationResponse({}));
16680
+ }
16681
+ else {
16682
+ return $tea.cast(await this.execute(params, req, runtime), new DescribeAlertConfigurationResponse({}));
16683
+ }
16523
16684
  }
16524
16685
  /**
16525
16686
  * Queries the status of scaling activities that trigger text message, internal message, or email-based notifications. When you call the DescribeAlertConfiguration operation, you must specify the scaling group ID and region ID to query the status of the desired scaling activities. A scaling activity can be in one of the following states: Successful, Failed, and Rejected.
@@ -16532,7 +16693,7 @@ class Client extends openapi_client_1.default {
16532
16693
  return await this.describeAlertConfigurationWithOptions(request, runtime);
16533
16694
  }
16534
16695
  /**
16535
- * DescribeDiagnoseReports
16696
+ * Queries the diagnostic reports.
16536
16697
  *
16537
16698
  * @param request - DescribeDiagnoseReportsRequest
16538
16699
  * @param runtime - runtime options for this request RuntimeOptions
@@ -16555,10 +16716,15 @@ class Client extends openapi_client_1.default {
16555
16716
  reqBodyType: "formData",
16556
16717
  bodyType: "json",
16557
16718
  });
16558
- return $tea.cast(await this.callApi(params, req, runtime), new DescribeDiagnoseReportsResponse({}));
16719
+ if (tea_util_1.default.isUnset(this._signatureVersion) || !tea_util_1.default.equalString(this._signatureVersion, "v4")) {
16720
+ return $tea.cast(await this.callApi(params, req, runtime), new DescribeDiagnoseReportsResponse({}));
16721
+ }
16722
+ else {
16723
+ return $tea.cast(await this.execute(params, req, runtime), new DescribeDiagnoseReportsResponse({}));
16724
+ }
16559
16725
  }
16560
16726
  /**
16561
- * DescribeDiagnoseReports
16727
+ * Queries the diagnostic reports.
16562
16728
  *
16563
16729
  * @param request - DescribeDiagnoseReportsRequest
16564
16730
  * @returns DescribeDiagnoseReportsResponse
@@ -16603,7 +16769,12 @@ class Client extends openapi_client_1.default {
16603
16769
  reqBodyType: "formData",
16604
16770
  bodyType: "json",
16605
16771
  });
16606
- return $tea.cast(await this.callApi(params, req, runtime), new DescribeEciScalingConfigurationDetailResponse({}));
16772
+ if (tea_util_1.default.isUnset(this._signatureVersion) || !tea_util_1.default.equalString(this._signatureVersion, "v4")) {
16773
+ return $tea.cast(await this.callApi(params, req, runtime), new DescribeEciScalingConfigurationDetailResponse({}));
16774
+ }
16775
+ else {
16776
+ return $tea.cast(await this.execute(params, req, runtime), new DescribeEciScalingConfigurationDetailResponse({}));
16777
+ }
16607
16778
  }
16608
16779
  /**
16609
16780
  * Queries the details of a scaling configuration. You can query a scaling configuration by its ID to learn about its details such as the temporary storage size, number of IPv6 addresses, and bandwidth of the elastic IP address (EIP). The scaling configuration details can be obtained as a YAML file.
@@ -16669,7 +16840,12 @@ class Client extends openapi_client_1.default {
16669
16840
  reqBodyType: "formData",
16670
16841
  bodyType: "json",
16671
16842
  });
16672
- return $tea.cast(await this.callApi(params, req, runtime), new DescribeEciScalingConfigurationsResponse({}));
16843
+ if (tea_util_1.default.isUnset(this._signatureVersion) || !tea_util_1.default.equalString(this._signatureVersion, "v4")) {
16844
+ return $tea.cast(await this.callApi(params, req, runtime), new DescribeEciScalingConfigurationsResponse({}));
16845
+ }
16846
+ else {
16847
+ return $tea.cast(await this.execute(params, req, runtime), new DescribeEciScalingConfigurationsResponse({}));
16848
+ }
16673
16849
  }
16674
16850
  /**
16675
16851
  * Queries scaling configurations of the Elastic Container Instance type. When you call the DescribeEciScalingConfigurations operation, you can specify ScalingGroupId, ScalingConfigurationIds, or ScalingConfigurationNames to query details about the desired scaling configurations, such as the instance bidding policy, instance type, image pulling policy, and load balancing weight of each elastic container instance. This can help you select a suitable template for creating elastic container instances or reference existing scaling configurations before you modify the automatic scaling policy for elastic container instances.
@@ -16682,7 +16858,7 @@ class Client extends openapi_client_1.default {
16682
16858
  return await this.describeEciScalingConfigurationsWithOptions(request, runtime);
16683
16859
  }
16684
16860
  /**
16685
- * DescribeElasticStrength
16861
+ * Queries the scaling strength of a scaling configuration. The success rate of scale-out events depends on the scaling strength of the scaling configuration that you want to use. By checking the scaling strength of a scaling configuration, you can enable Auto Scaling to measure its performance and improve specific configurations.
16686
16862
  *
16687
16863
  * @param request - DescribeElasticStrengthRequest
16688
16864
  * @param runtime - runtime options for this request RuntimeOptions
@@ -16705,10 +16881,15 @@ class Client extends openapi_client_1.default {
16705
16881
  reqBodyType: "formData",
16706
16882
  bodyType: "json",
16707
16883
  });
16708
- return $tea.cast(await this.callApi(params, req, runtime), new DescribeElasticStrengthResponse({}));
16884
+ if (tea_util_1.default.isUnset(this._signatureVersion) || !tea_util_1.default.equalString(this._signatureVersion, "v4")) {
16885
+ return $tea.cast(await this.callApi(params, req, runtime), new DescribeElasticStrengthResponse({}));
16886
+ }
16887
+ else {
16888
+ return $tea.cast(await this.execute(params, req, runtime), new DescribeElasticStrengthResponse({}));
16889
+ }
16709
16890
  }
16710
16891
  /**
16711
- * DescribeElasticStrength
16892
+ * Queries the scaling strength of a scaling configuration. The success rate of scale-out events depends on the scaling strength of the scaling configuration that you want to use. By checking the scaling strength of a scaling configuration, you can enable Auto Scaling to measure its performance and improve specific configurations.
16712
16893
  *
16713
16894
  * @param request - DescribeElasticStrengthRequest
16714
16895
  * @returns DescribeElasticStrengthResponse
@@ -16768,7 +16949,12 @@ class Client extends openapi_client_1.default {
16768
16949
  reqBodyType: "formData",
16769
16950
  bodyType: "json",
16770
16951
  });
16771
- return $tea.cast(await this.callApi(params, req, runtime), new DescribeInstanceRefreshesResponse({}));
16952
+ if (tea_util_1.default.isUnset(this._signatureVersion) || !tea_util_1.default.equalString(this._signatureVersion, "v4")) {
16953
+ return $tea.cast(await this.callApi(params, req, runtime), new DescribeInstanceRefreshesResponse({}));
16954
+ }
16955
+ else {
16956
+ return $tea.cast(await this.execute(params, req, runtime), new DescribeInstanceRefreshesResponse({}));
16957
+ }
16772
16958
  }
16773
16959
  /**
16774
16960
  * Queries instance refresh tasks. If you want to view the basic information and execution progress of an instance refresh task, you can call the DescribeInstanceRefreshes operation.
@@ -16781,7 +16967,7 @@ class Client extends openapi_client_1.default {
16781
16967
  return await this.describeInstanceRefreshesWithOptions(request, runtime);
16782
16968
  }
16783
16969
  /**
16784
- * Queries the details of a lifecycle hook. If you want to query the details of a lifecycle hook, you can call the DescribeLifecycleActions operation. For example, you can query the execution status and ID of a lifecycle hook, along with the Elastic Compute Service (ECS) instances on which the lifecycle hook takes effect. When you call this operation, you can specify parameters such as ScalingActivityId, LifecycleActionToken, and MaxResults to query the details of a lifecycle hook.
16970
+ * Queries lifecycle hook actions. When you call the DescribeLifecycleActions operation, you can specify parameters such as ScalingActivityId, NextToken, and MaxResults to query the details such as the action status and ID of a lifecycle hook. You can also call this operation to query the IDs of Elastic Compute Service (ECS) instances on which the lifecycle hook takes effect.
16785
16971
  *
16786
16972
  * @remarks
16787
16973
  * If a scaling activity is executed and a lifecycle hook is created for the scaling activity, the lifecycle hook triggers a lifecycle action. A lifecycle action can be in one of the following states:
@@ -16832,10 +17018,15 @@ class Client extends openapi_client_1.default {
16832
17018
  reqBodyType: "formData",
16833
17019
  bodyType: "json",
16834
17020
  });
16835
- return $tea.cast(await this.callApi(params, req, runtime), new DescribeLifecycleActionsResponse({}));
17021
+ if (tea_util_1.default.isUnset(this._signatureVersion) || !tea_util_1.default.equalString(this._signatureVersion, "v4")) {
17022
+ return $tea.cast(await this.callApi(params, req, runtime), new DescribeLifecycleActionsResponse({}));
17023
+ }
17024
+ else {
17025
+ return $tea.cast(await this.execute(params, req, runtime), new DescribeLifecycleActionsResponse({}));
17026
+ }
16836
17027
  }
16837
17028
  /**
16838
- * Queries the details of a lifecycle hook. If you want to query the details of a lifecycle hook, you can call the DescribeLifecycleActions operation. For example, you can query the execution status and ID of a lifecycle hook, along with the Elastic Compute Service (ECS) instances on which the lifecycle hook takes effect. When you call this operation, you can specify parameters such as ScalingActivityId, LifecycleActionToken, and MaxResults to query the details of a lifecycle hook.
17029
+ * Queries lifecycle hook actions. When you call the DescribeLifecycleActions operation, you can specify parameters such as ScalingActivityId, NextToken, and MaxResults to query the details such as the action status and ID of a lifecycle hook. You can also call this operation to query the IDs of Elastic Compute Service (ECS) instances on which the lifecycle hook takes effect.
16839
17030
  *
16840
17031
  * @remarks
16841
17032
  * If a scaling activity is executed and a lifecycle hook is created for the scaling activity, the lifecycle hook triggers a lifecycle action. A lifecycle action can be in one of the following states:
@@ -16852,7 +17043,7 @@ class Client extends openapi_client_1.default {
16852
17043
  return await this.describeLifecycleActionsWithOptions(request, runtime);
16853
17044
  }
16854
17045
  /**
16855
- * Queries lifecycle hooks. If you want to check whether the configurations of your lifecycle hooks are correct or you want to query the details of multiple lifecycle hooks at the same time, you can call the DescribeLifecycleHooks operation. You can specify lifecycle hook IDs or scaling group IDs when you call this operation. This operation returns details such as the default actions, scaling activities, Alibaba Cloud Resource Names (ARNs) of notification recipients, and timeout periods of lifecycle hooks.
17046
+ * Queries lifecycle hooks. When you call this operation, you can specify the lifecycle hook ID or scaling group ID to query the details of the desired lifecycle hook, such as the default action after the lifecycle hook times out, scaling activity that corresponds to the lifecycle hook, Alibaba Cloud Resource Name (ARN) of the notification recipient, and effective period of the lifecycle hook.
16856
17047
  *
16857
17048
  * @remarks
16858
17049
  * You can use one of the following methods to query lifecycle hooks:
@@ -16908,10 +17099,15 @@ class Client extends openapi_client_1.default {
16908
17099
  reqBodyType: "formData",
16909
17100
  bodyType: "json",
16910
17101
  });
16911
- return $tea.cast(await this.callApi(params, req, runtime), new DescribeLifecycleHooksResponse({}));
17102
+ if (tea_util_1.default.isUnset(this._signatureVersion) || !tea_util_1.default.equalString(this._signatureVersion, "v4")) {
17103
+ return $tea.cast(await this.callApi(params, req, runtime), new DescribeLifecycleHooksResponse({}));
17104
+ }
17105
+ else {
17106
+ return $tea.cast(await this.execute(params, req, runtime), new DescribeLifecycleHooksResponse({}));
17107
+ }
16912
17108
  }
16913
17109
  /**
16914
- * Queries lifecycle hooks. If you want to check whether the configurations of your lifecycle hooks are correct or you want to query the details of multiple lifecycle hooks at the same time, you can call the DescribeLifecycleHooks operation. You can specify lifecycle hook IDs or scaling group IDs when you call this operation. This operation returns details such as the default actions, scaling activities, Alibaba Cloud Resource Names (ARNs) of notification recipients, and timeout periods of lifecycle hooks.
17110
+ * Queries lifecycle hooks. When you call this operation, you can specify the lifecycle hook ID or scaling group ID to query the details of the desired lifecycle hook, such as the default action after the lifecycle hook times out, scaling activity that corresponds to the lifecycle hook, Alibaba Cloud Resource Name (ARN) of the notification recipient, and effective period of the lifecycle hook.
16915
17111
  *
16916
17112
  * @remarks
16917
17113
  * You can use one of the following methods to query lifecycle hooks:
@@ -16956,7 +17152,12 @@ class Client extends openapi_client_1.default {
16956
17152
  reqBodyType: "formData",
16957
17153
  bodyType: "json",
16958
17154
  });
16959
- return $tea.cast(await this.callApi(params, req, runtime), new DescribeLimitationResponse({}));
17155
+ if (tea_util_1.default.isUnset(this._signatureVersion) || !tea_util_1.default.equalString(this._signatureVersion, "v4")) {
17156
+ return $tea.cast(await this.callApi(params, req, runtime), new DescribeLimitationResponse({}));
17157
+ }
17158
+ else {
17159
+ return $tea.cast(await this.execute(params, req, runtime), new DescribeLimitationResponse({}));
17160
+ }
16960
17161
  }
16961
17162
  /**
16962
17163
  * Queries resource quotas. For example, you can call the DescribeLimitation operation to query the maximum numbers of scheduled tasks that you can create in a scaling group, load balancers that you can attach to a scaling group, instances that you can add to a scaling group, and scaling configurations that you can create in a scaling group.
@@ -17004,7 +17205,12 @@ class Client extends openapi_client_1.default {
17004
17205
  reqBodyType: "formData",
17005
17206
  bodyType: "json",
17006
17207
  });
17007
- return $tea.cast(await this.callApi(params, req, runtime), new DescribeNotificationConfigurationsResponse({}));
17208
+ if (tea_util_1.default.isUnset(this._signatureVersion) || !tea_util_1.default.equalString(this._signatureVersion, "v4")) {
17209
+ return $tea.cast(await this.callApi(params, req, runtime), new DescribeNotificationConfigurationsResponse({}));
17210
+ }
17211
+ else {
17212
+ return $tea.cast(await this.execute(params, req, runtime), new DescribeNotificationConfigurationsResponse({}));
17213
+ }
17008
17214
  }
17009
17215
  /**
17010
17216
  * Queries notification settings. You can call the DescribeNotificationConfiguration operation to query notification settings of scaling events or resource changes, including the notification types and methods.
@@ -17046,7 +17252,12 @@ class Client extends openapi_client_1.default {
17046
17252
  reqBodyType: "formData",
17047
17253
  bodyType: "json",
17048
17254
  });
17049
- return $tea.cast(await this.callApi(params, req, runtime), new DescribeNotificationTypesResponse({}));
17255
+ if (tea_util_1.default.isUnset(this._signatureVersion) || !tea_util_1.default.equalString(this._signatureVersion, "v4")) {
17256
+ return $tea.cast(await this.callApi(params, req, runtime), new DescribeNotificationTypesResponse({}));
17257
+ }
17258
+ else {
17259
+ return $tea.cast(await this.execute(params, req, runtime), new DescribeNotificationTypesResponse({}));
17260
+ }
17050
17261
  }
17051
17262
  /**
17052
17263
  * Queries notification types. You can call the DescribeNotificationTypes operation to query the types of notifications on scaling events or resource changes occurred in your scaling groups. Notifications are triggered in scenarios such as successful scale-out events, successful scale-in events, expiration of scheduled tasks, and partially successful scale-out events.
@@ -17082,7 +17293,12 @@ class Client extends openapi_client_1.default {
17082
17293
  reqBodyType: "formData",
17083
17294
  bodyType: "json",
17084
17295
  });
17085
- return $tea.cast(await this.callApi(params, req, runtime), new DescribePatternTypesResponse({}));
17296
+ if (tea_util_1.default.isUnset(this._signatureVersion) || !tea_util_1.default.equalString(this._signatureVersion, "v4")) {
17297
+ return $tea.cast(await this.callApi(params, req, runtime), new DescribePatternTypesResponse({}));
17298
+ }
17299
+ else {
17300
+ return $tea.cast(await this.execute(params, req, runtime), new DescribePatternTypesResponse({}));
17301
+ }
17086
17302
  }
17087
17303
  /**
17088
17304
  * Queries instance types. When you call the DescribePatternTypes operation, you can specify attributes such as the vSwitch ID, number of vCPUs, memory size, instance family, and maximum acceptable price to filer instance types that meet your business requirements.
@@ -17130,7 +17346,12 @@ class Client extends openapi_client_1.default {
17130
17346
  reqBodyType: "formData",
17131
17347
  bodyType: "json",
17132
17348
  });
17133
- return $tea.cast(await this.callApi(params, req, runtime), new DescribeRegionsResponse({}));
17349
+ if (tea_util_1.default.isUnset(this._signatureVersion) || !tea_util_1.default.equalString(this._signatureVersion, "v4")) {
17350
+ return $tea.cast(await this.callApi(params, req, runtime), new DescribeRegionsResponse({}));
17351
+ }
17352
+ else {
17353
+ return $tea.cast(await this.execute(params, req, runtime), new DescribeRegionsResponse({}));
17354
+ }
17134
17355
  }
17135
17356
  /**
17136
17357
  * Queries regions. Before you activate Auto Scaling, you can call the DescribeRegions operation to query the regions where Auto Scaling is officially launched. This preliminary step facilitates the strategic selection of both the optimal region and availability zones for activating Auto Scaling, thereby guaranteeing the finest access speeds and operational efficiency within your chosen geographical area.
@@ -17204,7 +17425,12 @@ class Client extends openapi_client_1.default {
17204
17425
  reqBodyType: "formData",
17205
17426
  bodyType: "json",
17206
17427
  });
17207
- return $tea.cast(await this.callApi(params, req, runtime), new DescribeScalingActivitiesResponse({}));
17428
+ if (tea_util_1.default.isUnset(this._signatureVersion) || !tea_util_1.default.equalString(this._signatureVersion, "v4")) {
17429
+ return $tea.cast(await this.callApi(params, req, runtime), new DescribeScalingActivitiesResponse({}));
17430
+ }
17431
+ else {
17432
+ return $tea.cast(await this.execute(params, req, runtime), new DescribeScalingActivitiesResponse({}));
17433
+ }
17208
17434
  }
17209
17435
  /**
17210
17436
  * Queries scaling activities. You can call the DescribeScalingActivities operation to query the results of scaling activities triggered by scheduled tasks, event-triggered tasks, or manual execution of scaling rules. For example, you can query the status and cause of a scaling activity. You can also query the total number of instances after a scaling activity is complete.
@@ -17222,7 +17448,7 @@ class Client extends openapi_client_1.default {
17222
17448
  return await this.describeScalingActivitiesWithOptions(request, runtime);
17223
17449
  }
17224
17450
  /**
17225
- * Queries the details of a scaling activity. The DescribeScalingActivityDetail operation enables you to access and monitor the details of a scaling activity, which is beneficial for troubleshooting and performance analysis purposes.
17451
+ * Queries the details of a scaling activity. You can query a scaling activity by its ID. The scaling activity details include the scaling activity status, error code, and error message. You can efficiently troubleshoot issues and analyze service performance based on the error message.
17226
17452
  *
17227
17453
  * @param request - DescribeScalingActivityDetailRequest
17228
17454
  * @param runtime - runtime options for this request RuntimeOptions
@@ -17257,10 +17483,15 @@ class Client extends openapi_client_1.default {
17257
17483
  reqBodyType: "formData",
17258
17484
  bodyType: "json",
17259
17485
  });
17260
- return $tea.cast(await this.callApi(params, req, runtime), new DescribeScalingActivityDetailResponse({}));
17486
+ if (tea_util_1.default.isUnset(this._signatureVersion) || !tea_util_1.default.equalString(this._signatureVersion, "v4")) {
17487
+ return $tea.cast(await this.callApi(params, req, runtime), new DescribeScalingActivityDetailResponse({}));
17488
+ }
17489
+ else {
17490
+ return $tea.cast(await this.execute(params, req, runtime), new DescribeScalingActivityDetailResponse({}));
17491
+ }
17261
17492
  }
17262
17493
  /**
17263
- * Queries the details of a scaling activity. The DescribeScalingActivityDetail operation enables you to access and monitor the details of a scaling activity, which is beneficial for troubleshooting and performance analysis purposes.
17494
+ * Queries the details of a scaling activity. You can query a scaling activity by its ID. The scaling activity details include the scaling activity status, error code, and error message. You can efficiently troubleshoot issues and analyze service performance based on the error message.
17264
17495
  *
17265
17496
  * @param request - DescribeScalingActivityDetailRequest
17266
17497
  * @returns DescribeScalingActivityDetailResponse
@@ -17323,7 +17554,12 @@ class Client extends openapi_client_1.default {
17323
17554
  reqBodyType: "formData",
17324
17555
  bodyType: "json",
17325
17556
  });
17326
- return $tea.cast(await this.callApi(params, req, runtime), new DescribeScalingConfigurationsResponse({}));
17557
+ if (tea_util_1.default.isUnset(this._signatureVersion) || !tea_util_1.default.equalString(this._signatureVersion, "v4")) {
17558
+ return $tea.cast(await this.callApi(params, req, runtime), new DescribeScalingConfigurationsResponse({}));
17559
+ }
17560
+ else {
17561
+ return $tea.cast(await this.execute(params, req, runtime), new DescribeScalingConfigurationsResponse({}));
17562
+ }
17327
17563
  }
17328
17564
  /**
17329
17565
  * Queries scaling configurations.
@@ -17371,7 +17607,12 @@ class Client extends openapi_client_1.default {
17371
17607
  reqBodyType: "formData",
17372
17608
  bodyType: "json",
17373
17609
  });
17374
- return $tea.cast(await this.callApi(params, req, runtime), new DescribeScalingGroupDetailResponse({}));
17610
+ if (tea_util_1.default.isUnset(this._signatureVersion) || !tea_util_1.default.equalString(this._signatureVersion, "v4")) {
17611
+ return $tea.cast(await this.callApi(params, req, runtime), new DescribeScalingGroupDetailResponse({}));
17612
+ }
17613
+ else {
17614
+ return $tea.cast(await this.execute(params, req, runtime), new DescribeScalingGroupDetailResponse({}));
17615
+ }
17375
17616
  }
17376
17617
  /**
17377
17618
  * Queries a scaling group. You can call the DescribeScalingGroupDetail operation to query the basic information, instances, and scaling configurations of a scaling group. If you set OutputFormat to YAML for a scaling group of the Elastic Container Instance type, the output is a Kubernetes Deployment file in the YAML format.
@@ -17384,7 +17625,7 @@ class Client extends openapi_client_1.default {
17384
17625
  return await this.describeScalingGroupDetailWithOptions(request, runtime);
17385
17626
  }
17386
17627
  /**
17387
- * DescribeScalingGroupDiagnoseDetails
17628
+ * Queries the latest diagnosis details for a scaling group. Diagnosis details are only returned in the presence of exceptions.
17388
17629
  *
17389
17630
  * @param request - DescribeScalingGroupDiagnoseDetailsRequest
17390
17631
  * @param runtime - runtime options for this request RuntimeOptions
@@ -17407,10 +17648,15 @@ class Client extends openapi_client_1.default {
17407
17648
  reqBodyType: "formData",
17408
17649
  bodyType: "json",
17409
17650
  });
17410
- return $tea.cast(await this.callApi(params, req, runtime), new DescribeScalingGroupDiagnoseDetailsResponse({}));
17651
+ if (tea_util_1.default.isUnset(this._signatureVersion) || !tea_util_1.default.equalString(this._signatureVersion, "v4")) {
17652
+ return $tea.cast(await this.callApi(params, req, runtime), new DescribeScalingGroupDiagnoseDetailsResponse({}));
17653
+ }
17654
+ else {
17655
+ return $tea.cast(await this.execute(params, req, runtime), new DescribeScalingGroupDiagnoseDetailsResponse({}));
17656
+ }
17411
17657
  }
17412
17658
  /**
17413
- * DescribeScalingGroupDiagnoseDetails
17659
+ * Queries the latest diagnosis details for a scaling group. Diagnosis details are only returned in the presence of exceptions.
17414
17660
  *
17415
17661
  * @param request - DescribeScalingGroupDiagnoseDetailsRequest
17416
17662
  * @returns DescribeScalingGroupDiagnoseDetailsResponse
@@ -17482,7 +17728,12 @@ class Client extends openapi_client_1.default {
17482
17728
  reqBodyType: "formData",
17483
17729
  bodyType: "json",
17484
17730
  });
17485
- return $tea.cast(await this.callApi(params, req, runtime), new DescribeScalingGroupsResponse({}));
17731
+ if (tea_util_1.default.isUnset(this._signatureVersion) || !tea_util_1.default.equalString(this._signatureVersion, "v4")) {
17732
+ return $tea.cast(await this.callApi(params, req, runtime), new DescribeScalingGroupsResponse({}));
17733
+ }
17734
+ else {
17735
+ return $tea.cast(await this.execute(params, req, runtime), new DescribeScalingGroupsResponse({}));
17736
+ }
17486
17737
  }
17487
17738
  /**
17488
17739
  * Queries information about scaling groups, such as the basic information, instances, and scaling configurations.
@@ -17566,7 +17817,12 @@ class Client extends openapi_client_1.default {
17566
17817
  reqBodyType: "formData",
17567
17818
  bodyType: "json",
17568
17819
  });
17569
- return $tea.cast(await this.callApi(params, req, runtime), new DescribeScalingInstancesResponse({}));
17820
+ if (tea_util_1.default.isUnset(this._signatureVersion) || !tea_util_1.default.equalString(this._signatureVersion, "v4")) {
17821
+ return $tea.cast(await this.callApi(params, req, runtime), new DescribeScalingInstancesResponse({}));
17822
+ }
17823
+ else {
17824
+ return $tea.cast(await this.execute(params, req, runtime), new DescribeScalingInstancesResponse({}));
17825
+ }
17570
17826
  }
17571
17827
  /**
17572
17828
  * Queries instances in a scaling group. You can call the DescribeScalingInstances operation to query instance details, such as the number of preemptible instances in the Running state, the number of Elastic Compute Service (ECS) instances, the warm-up status of ECS instances, and the lifecycle status of ECS instances in a scaling group. You can specify the scaling group whose instances you want to query by scaling group ID. If you want to filter instances based on conditions, such as the instance health status, lifecycle status, or creation method, you can also call this operation.
@@ -17644,7 +17900,12 @@ class Client extends openapi_client_1.default {
17644
17900
  reqBodyType: "formData",
17645
17901
  bodyType: "json",
17646
17902
  });
17647
- return $tea.cast(await this.callApi(params, req, runtime), new DescribeScalingRulesResponse({}));
17903
+ if (tea_util_1.default.isUnset(this._signatureVersion) || !tea_util_1.default.equalString(this._signatureVersion, "v4")) {
17904
+ return $tea.cast(await this.callApi(params, req, runtime), new DescribeScalingRulesResponse({}));
17905
+ }
17906
+ else {
17907
+ return $tea.cast(await this.execute(params, req, runtime), new DescribeScalingRulesResponse({}));
17908
+ }
17648
17909
  }
17649
17910
  /**
17650
17911
  * Queries scaling rules. When you call this operation, you can specify the ID, name, or Alibaba Cloud Resource Name (ARN) of a scaling rule to query the details of the scaling rule. For example, you can query the adjustment method, instance warm-up period, and associated event-triggered tasks of the desired scaling rule.
@@ -17731,7 +17992,12 @@ class Client extends openapi_client_1.default {
17731
17992
  reqBodyType: "formData",
17732
17993
  bodyType: "json",
17733
17994
  });
17734
- return $tea.cast(await this.callApi(params, req, runtime), new DescribeScheduledTasksResponse({}));
17995
+ if (tea_util_1.default.isUnset(this._signatureVersion) || !tea_util_1.default.equalString(this._signatureVersion, "v4")) {
17996
+ return $tea.cast(await this.callApi(params, req, runtime), new DescribeScheduledTasksResponse({}));
17997
+ }
17998
+ else {
17999
+ return $tea.cast(await this.execute(params, req, runtime), new DescribeScheduledTasksResponse({}));
18000
+ }
17735
18001
  }
17736
18002
  /**
17737
18003
  * Queries scheduled tasks. A scheduled task is a predefined task that triggers the automatic execution of a scaling rule at the specified point in time. It ensures an automatic scaling of computing resources to fulfill your business demands at a minimum cost. After you create a scheduled task, you can call the DescribeScheduledTasks operation to query the details of the task, such as the execution time point and the scaling group ID. You can also call this operation to query the total number of existing scheduled tasks.
@@ -17791,7 +18057,12 @@ class Client extends openapi_client_1.default {
17791
18057
  reqBodyType: "formData",
17792
18058
  bodyType: "json",
17793
18059
  });
17794
- return $tea.cast(await this.callApi(params, req, runtime), new DetachAlbServerGroupsResponse({}));
18060
+ if (tea_util_1.default.isUnset(this._signatureVersion) || !tea_util_1.default.equalString(this._signatureVersion, "v4")) {
18061
+ return $tea.cast(await this.callApi(params, req, runtime), new DetachAlbServerGroupsResponse({}));
18062
+ }
18063
+ else {
18064
+ return $tea.cast(await this.execute(params, req, runtime), new DetachAlbServerGroupsResponse({}));
18065
+ }
17795
18066
  }
17796
18067
  /**
17797
18068
  * Detaches Application Load Balancer (ALB) server groups from a scaling group. When you call the DetachAlbServerGroups operation, you can specify the scaling group ID, ALB server group ID, and port used by Elastic Compute Service (ECS) instances in the desired ALB server group to detach one or more ALB server groups from your scaling group.
@@ -17804,7 +18075,7 @@ class Client extends openapi_client_1.default {
17804
18075
  return await this.detachAlbServerGroupsWithOptions(request, runtime);
17805
18076
  }
17806
18077
  /**
17807
- * Disassociates one or more ApsaraDB RDS instances from a scaling group.
18078
+ * Detaches one or more ApsaraDB RDS instances from a scaling group. If you want to decrease the number of ApsaraDB RDS instances attached to your scaling group, you can call the DetachDBInstance operation. This operation liberates ApsaraDB RDS instances from your scaling group, thereby significantly boosting the agility and efficiency in managing and allocating your resources.
17808
18079
  *
17809
18080
  * @param request - DetachDBInstancesRequest
17810
18081
  * @param runtime - runtime options for this request RuntimeOptions
@@ -17851,10 +18122,15 @@ class Client extends openapi_client_1.default {
17851
18122
  reqBodyType: "formData",
17852
18123
  bodyType: "json",
17853
18124
  });
17854
- return $tea.cast(await this.callApi(params, req, runtime), new DetachDBInstancesResponse({}));
18125
+ if (tea_util_1.default.isUnset(this._signatureVersion) || !tea_util_1.default.equalString(this._signatureVersion, "v4")) {
18126
+ return $tea.cast(await this.callApi(params, req, runtime), new DetachDBInstancesResponse({}));
18127
+ }
18128
+ else {
18129
+ return $tea.cast(await this.execute(params, req, runtime), new DetachDBInstancesResponse({}));
18130
+ }
17855
18131
  }
17856
18132
  /**
17857
- * Disassociates one or more ApsaraDB RDS instances from a scaling group.
18133
+ * Detaches one or more ApsaraDB RDS instances from a scaling group. If you want to decrease the number of ApsaraDB RDS instances attached to your scaling group, you can call the DetachDBInstance operation. This operation liberates ApsaraDB RDS instances from your scaling group, thereby significantly boosting the agility and efficiency in managing and allocating your resources.
17858
18134
  *
17859
18135
  * @param request - DetachDBInstancesRequest
17860
18136
  * @returns DetachDBInstancesResponse
@@ -17932,7 +18208,12 @@ class Client extends openapi_client_1.default {
17932
18208
  reqBodyType: "formData",
17933
18209
  bodyType: "json",
17934
18210
  });
17935
- return $tea.cast(await this.callApi(params, req, runtime), new DetachInstancesResponse({}));
18211
+ if (tea_util_1.default.isUnset(this._signatureVersion) || !tea_util_1.default.equalString(this._signatureVersion, "v4")) {
18212
+ return $tea.cast(await this.callApi(params, req, runtime), new DetachInstancesResponse({}));
18213
+ }
18214
+ else {
18215
+ return $tea.cast(await this.execute(params, req, runtime), new DetachInstancesResponse({}));
18216
+ }
17936
18217
  }
17937
18218
  /**
17938
18219
  * Removes instances from a scaling group. If an enabled scaling group has no ongoing scaling activities, you can call the DetachInstances operation to remove one or more Elastic Compute Service (ECS) instances, elastic container instances, or Alibaba Cloud-hosted third-party instances from the scaling group.
@@ -18004,7 +18285,12 @@ class Client extends openapi_client_1.default {
18004
18285
  reqBodyType: "formData",
18005
18286
  bodyType: "json",
18006
18287
  });
18007
- return $tea.cast(await this.callApi(params, req, runtime), new DetachLoadBalancersResponse({}));
18288
+ if (tea_util_1.default.isUnset(this._signatureVersion) || !tea_util_1.default.equalString(this._signatureVersion, "v4")) {
18289
+ return $tea.cast(await this.callApi(params, req, runtime), new DetachLoadBalancersResponse({}));
18290
+ }
18291
+ else {
18292
+ return $tea.cast(await this.execute(params, req, runtime), new DetachLoadBalancersResponse({}));
18293
+ }
18008
18294
  }
18009
18295
  /**
18010
18296
  * Detaches Classic Load Balancer (CLB, formerly known as Server Load Balancer or SLB) instances from a scaling group. If the current CLB instance no longer meets your business requirements, you can call the DetachLoadBalancers operation to detach it from your scaling group. When you call this operation, you can use ScalingGroupId, LoadBalancer.N, and ForceDetach to specify one or more CLB instances to detach. You can also determine whether to call this operation asynchronously and whether to remove the Elastic Compute Service (ECS) instances acting as backend servers from the backend server groups of the CLB instance. You can call this operation to detach only CLB instances from a scaling group.
@@ -18061,7 +18347,12 @@ class Client extends openapi_client_1.default {
18061
18347
  reqBodyType: "formData",
18062
18348
  bodyType: "json",
18063
18349
  });
18064
- return $tea.cast(await this.callApi(params, req, runtime), new DetachServerGroupsResponse({}));
18350
+ if (tea_util_1.default.isUnset(this._signatureVersion) || !tea_util_1.default.equalString(this._signatureVersion, "v4")) {
18351
+ return $tea.cast(await this.callApi(params, req, runtime), new DetachServerGroupsResponse({}));
18352
+ }
18353
+ else {
18354
+ return $tea.cast(await this.execute(params, req, runtime), new DetachServerGroupsResponse({}));
18355
+ }
18065
18356
  }
18066
18357
  /**
18067
18358
  * Detach server groups from a scaling group. To seamlessly adjust the number of instances in response to changes in your business workload or to maintain the uninterrupted accessibility of your application, you can call the DetachServerGroups operation. By detaching Application Load Balancer (ALB) or Network Load Balancer (NLB) server groups from your scaling group, this operation enables Auto Scaling to automatically tailor your computing capacity to your business needs. Furthermore, it optimizes traffic routing by dynamically allocating incoming requests based on current workload patterns, which significantly improves the stability and performance of your application.
@@ -18126,7 +18417,12 @@ class Client extends openapi_client_1.default {
18126
18417
  reqBodyType: "formData",
18127
18418
  bodyType: "json",
18128
18419
  });
18129
- return $tea.cast(await this.callApi(params, req, runtime), new DetachVServerGroupsResponse({}));
18420
+ if (tea_util_1.default.isUnset(this._signatureVersion) || !tea_util_1.default.equalString(this._signatureVersion, "v4")) {
18421
+ return $tea.cast(await this.callApi(params, req, runtime), new DetachVServerGroupsResponse({}));
18422
+ }
18423
+ else {
18424
+ return $tea.cast(await this.execute(params, req, runtime), new DetachVServerGroupsResponse({}));
18425
+ }
18130
18426
  }
18131
18427
  /**
18132
18428
  * Detaches vServer groups from a scaling group. Auto Scaling supports the attachment of load balancers to scaling groups to improve service performance. If the load balancer currently attached to your scaling group is no longer needed to distribute the access traffic to the instances in your scaling group, you can call the DetachVServerGroups operation to detach one or more vServer groups of this load balancer from the scaling group.
@@ -18185,7 +18481,12 @@ class Client extends openapi_client_1.default {
18185
18481
  reqBodyType: "formData",
18186
18482
  bodyType: "json",
18187
18483
  });
18188
- return $tea.cast(await this.callApi(params, req, runtime), new DisableAlarmResponse({}));
18484
+ if (tea_util_1.default.isUnset(this._signatureVersion) || !tea_util_1.default.equalString(this._signatureVersion, "v4")) {
18485
+ return $tea.cast(await this.callApi(params, req, runtime), new DisableAlarmResponse({}));
18486
+ }
18487
+ else {
18488
+ return $tea.cast(await this.execute(params, req, runtime), new DisableAlarmResponse({}));
18489
+ }
18189
18490
  }
18190
18491
  /**
18191
18492
  * Disables an event-triggered task. If your business pattern is unpredictable or prone to unforeseen traffic spikes, you can create event-triggered tasks by associating CloudMonitor metrics to effectively monitor fluctuations in your business workload. Upon detecting that the criteria for alerts, as specified in event-triggered tasks, are fulfilled, Auto Scaling promptly issues alerts and executes the scaling rules predefined within those tasks. This process occurs within the predefined effective time windows of the tasks, thereby facilitating the automatic increase or decrease of Elastic Compute Service (ECS) instances or elastic container instances within your scaling groups. Ultimately, this mechanism ensures the dynamic optimization of resources based on real-time workload demands. If you currently do not need an event-triggered task, you can call the DisableAlarm operation to disable it.
@@ -18244,7 +18545,12 @@ class Client extends openapi_client_1.default {
18244
18545
  reqBodyType: "formData",
18245
18546
  bodyType: "json",
18246
18547
  });
18247
- return $tea.cast(await this.callApi(params, req, runtime), new DisableScalingGroupResponse({}));
18548
+ if (tea_util_1.default.isUnset(this._signatureVersion) || !tea_util_1.default.equalString(this._signatureVersion, "v4")) {
18549
+ return $tea.cast(await this.callApi(params, req, runtime), new DisableScalingGroupResponse({}));
18550
+ }
18551
+ else {
18552
+ return $tea.cast(await this.execute(params, req, runtime), new DisableScalingGroupResponse({}));
18553
+ }
18248
18554
  }
18249
18555
  /**
18250
18556
  * Disables a scaling group. If you temporarily do not require a scaling group that is in the Enabled state, you can call the DisableScalingGroup operation to disable it.
@@ -18297,7 +18603,12 @@ class Client extends openapi_client_1.default {
18297
18603
  reqBodyType: "formData",
18298
18604
  bodyType: "json",
18299
18605
  });
18300
- return $tea.cast(await this.callApi(params, req, runtime), new EnableAlarmResponse({}));
18606
+ if (tea_util_1.default.isUnset(this._signatureVersion) || !tea_util_1.default.equalString(this._signatureVersion, "v4")) {
18607
+ return $tea.cast(await this.callApi(params, req, runtime), new EnableAlarmResponse({}));
18608
+ }
18609
+ else {
18610
+ return $tea.cast(await this.execute(params, req, runtime), new EnableAlarmResponse({}));
18611
+ }
18301
18612
  }
18302
18613
  /**
18303
18614
  * Enables an event-triggered task. If your business pattern is unpredictable or prone to unforeseen traffic spikes, you can create event-triggered tasks by associating CloudMonitor metrics to effectively monitor fluctuations in your business workload. Upon detecting that the criteria for alerts, as specified in event-triggered tasks, are fulfilled, Auto Scaling promptly issues alerts and executes the scaling rules predefined within those tasks. This process occurs within the predefined effective time windows of the tasks, thereby facilitating the automatic increase or decrease of Elastic Compute Service (ECS) instances or elastic container instances within your scaling groups. Ultimately, this mechanism ensures the dynamic optimization of resources based on real-time workload demands. If you want to reuse an event-triggered task that is in the Disabled state, you can call the EnableAlarm operation to enable it.
@@ -18377,7 +18688,12 @@ class Client extends openapi_client_1.default {
18377
18688
  reqBodyType: "formData",
18378
18689
  bodyType: "json",
18379
18690
  });
18380
- return $tea.cast(await this.callApi(params, req, runtime), new EnableScalingGroupResponse({}));
18691
+ if (tea_util_1.default.isUnset(this._signatureVersion) || !tea_util_1.default.equalString(this._signatureVersion, "v4")) {
18692
+ return $tea.cast(await this.callApi(params, req, runtime), new EnableScalingGroupResponse({}));
18693
+ }
18694
+ else {
18695
+ return $tea.cast(await this.execute(params, req, runtime), new EnableScalingGroupResponse({}));
18696
+ }
18381
18697
  }
18382
18698
  /**
18383
18699
  * Enables a scaling group. If a scaling group is in the Disabled state and contains an instance configuration source such as a launch template or a scaling configuration, you can call the EnableScalingGroup operation to enable the scaling group. This operation permits Auto Scaling to dynamically adjust the computing power (also known as the number of instances) in the scaling group based on your business requirements.
@@ -18446,7 +18762,12 @@ class Client extends openapi_client_1.default {
18446
18762
  reqBodyType: "formData",
18447
18763
  bodyType: "json",
18448
18764
  });
18449
- return $tea.cast(await this.callApi(params, req, runtime), new EnterStandbyResponse({}));
18765
+ if (tea_util_1.default.isUnset(this._signatureVersion) || !tea_util_1.default.equalString(this._signatureVersion, "v4")) {
18766
+ return $tea.cast(await this.callApi(params, req, runtime), new EnterStandbyResponse({}));
18767
+ }
18768
+ else {
18769
+ return $tea.cast(await this.execute(params, req, runtime), new EnterStandbyResponse({}));
18770
+ }
18450
18771
  }
18451
18772
  /**
18452
18773
  * Puts an Elastic Compute Service (ECS) instance into the Standby state.
@@ -18526,7 +18847,12 @@ class Client extends openapi_client_1.default {
18526
18847
  reqBodyType: "formData",
18527
18848
  bodyType: "json",
18528
18849
  });
18529
- return $tea.cast(await this.callApi(params, req, runtime), new ExecuteScalingRuleResponse({}));
18850
+ if (tea_util_1.default.isUnset(this._signatureVersion) || !tea_util_1.default.equalString(this._signatureVersion, "v4")) {
18851
+ return $tea.cast(await this.callApi(params, req, runtime), new ExecuteScalingRuleResponse({}));
18852
+ }
18853
+ else {
18854
+ return $tea.cast(await this.execute(params, req, runtime), new ExecuteScalingRuleResponse({}));
18855
+ }
18530
18856
  }
18531
18857
  /**
18532
18858
  * Executes a scaling rule. To adjust the number of Elastic Compute Service (ECS) instances or elastic container instances, you can manually execute a scaling rule or enable Auto Scaling to execute a scaling rule. You can call the ExecuteScalingRule operation to execute simple scaling rules or step scaling rules. Auto Scaling automatically executes target tracking scaling rules and predictive scaling rules on your behalf without requiring explicit execution calls.
@@ -18600,7 +18926,12 @@ class Client extends openapi_client_1.default {
18600
18926
  reqBodyType: "formData",
18601
18927
  bodyType: "json",
18602
18928
  });
18603
- return $tea.cast(await this.callApi(params, req, runtime), new ExitStandbyResponse({}));
18929
+ if (tea_util_1.default.isUnset(this._signatureVersion) || !tea_util_1.default.equalString(this._signatureVersion, "v4")) {
18930
+ return $tea.cast(await this.callApi(params, req, runtime), new ExitStandbyResponse({}));
18931
+ }
18932
+ else {
18933
+ return $tea.cast(await this.execute(params, req, runtime), new ExitStandbyResponse({}));
18934
+ }
18604
18935
  }
18605
18936
  /**
18606
18937
  * Removes an instance from the Standby state. When a scale-in event is triggered in a scaling group, Auto Scaling does not remove Elastic Compute Service (ECS) instances or elastic container instances that are in the Standby state from the scaling group. If you want to restart the instances that are in the Standby state, you can call the ExitStandby operation to remove the instances from the Standby state and put them into the In Service state.
@@ -18661,7 +18992,12 @@ class Client extends openapi_client_1.default {
18661
18992
  reqBodyType: "formData",
18662
18993
  bodyType: "json",
18663
18994
  });
18664
- return $tea.cast(await this.callApi(params, req, runtime), new ListTagKeysResponse({}));
18995
+ if (tea_util_1.default.isUnset(this._signatureVersion) || !tea_util_1.default.equalString(this._signatureVersion, "v4")) {
18996
+ return $tea.cast(await this.callApi(params, req, runtime), new ListTagKeysResponse({}));
18997
+ }
18998
+ else {
18999
+ return $tea.cast(await this.execute(params, req, runtime), new ListTagKeysResponse({}));
19000
+ }
18665
19001
  }
18666
19002
  /**
18667
19003
  * Queries the tag keys added to Auto Scaling resources. Querying tag keys facilitates easier classification, identification, and monitoring of your Auto Scaling resources, thereby enhancing the flexibility and convenience of your resource management processes.
@@ -18674,7 +19010,7 @@ class Client extends openapi_client_1.default {
18674
19010
  return await this.listTagKeysWithOptions(request, runtime);
18675
19011
  }
18676
19012
  /**
18677
- * Queries tags. You can call the ListTagResources operation to query tags that are added to Auto Scaling resources, thereby clarifying resource utilization and facilitating efficient management. This operation aids in the automation of resource categorization and permission management processes.
19013
+ * Queries tags. You can call the ListTagResources operation to query tags that are added to Auto Scaling resources, thereby clarifying resource utilization and facilitating efficient resource management. This operation aids in the automation of resource categorization and permission management processes.
18678
19014
  *
18679
19015
  * @remarks
18680
19016
  * Specify at least one of the following request parameters: `ResourceIds` and `Tags`. `Tags.Key` and `Tags.Value` are used to specify the query objects.
@@ -18722,10 +19058,15 @@ class Client extends openapi_client_1.default {
18722
19058
  reqBodyType: "formData",
18723
19059
  bodyType: "json",
18724
19060
  });
18725
- return $tea.cast(await this.callApi(params, req, runtime), new ListTagResourcesResponse({}));
19061
+ if (tea_util_1.default.isUnset(this._signatureVersion) || !tea_util_1.default.equalString(this._signatureVersion, "v4")) {
19062
+ return $tea.cast(await this.callApi(params, req, runtime), new ListTagResourcesResponse({}));
19063
+ }
19064
+ else {
19065
+ return $tea.cast(await this.execute(params, req, runtime), new ListTagResourcesResponse({}));
19066
+ }
18726
19067
  }
18727
19068
  /**
18728
- * Queries tags. You can call the ListTagResources operation to query tags that are added to Auto Scaling resources, thereby clarifying resource utilization and facilitating efficient management. This operation aids in the automation of resource categorization and permission management processes.
19069
+ * Queries tags. You can call the ListTagResources operation to query tags that are added to Auto Scaling resources, thereby clarifying resource utilization and facilitating efficient resource management. This operation aids in the automation of resource categorization and permission management processes.
18729
19070
  *
18730
19071
  * @remarks
18731
19072
  * Specify at least one of the following request parameters: `ResourceIds` and `Tags`. `Tags.Key` and `Tags.Value` are used to specify the query objects.
@@ -18783,7 +19124,12 @@ class Client extends openapi_client_1.default {
18783
19124
  reqBodyType: "formData",
18784
19125
  bodyType: "json",
18785
19126
  });
18786
- return $tea.cast(await this.callApi(params, req, runtime), new ListTagValuesResponse({}));
19127
+ if (tea_util_1.default.isUnset(this._signatureVersion) || !tea_util_1.default.equalString(this._signatureVersion, "v4")) {
19128
+ return $tea.cast(await this.callApi(params, req, runtime), new ListTagValuesResponse({}));
19129
+ }
19130
+ else {
19131
+ return $tea.cast(await this.execute(params, req, runtime), new ListTagValuesResponse({}));
19132
+ }
18787
19133
  }
18788
19134
  /**
18789
19135
  * Queries the tag keys associated with Auto Scaling resources to facilitate a deeper comprehension of those resources. By doing so, you can categorize and manage your Auto Scaling resources more efficiently.
@@ -18883,7 +19229,12 @@ class Client extends openapi_client_1.default {
18883
19229
  reqBodyType: "formData",
18884
19230
  bodyType: "json",
18885
19231
  });
18886
- return $tea.cast(await this.callApi(params, req, runtime), new ModifyAlarmResponse({}));
19232
+ if (tea_util_1.default.isUnset(this._signatureVersion) || !tea_util_1.default.equalString(this._signatureVersion, "v4")) {
19233
+ return $tea.cast(await this.callApi(params, req, runtime), new ModifyAlarmResponse({}));
19234
+ }
19235
+ else {
19236
+ return $tea.cast(await this.execute(params, req, runtime), new ModifyAlarmResponse({}));
19237
+ }
18887
19238
  }
18888
19239
  /**
18889
19240
  * Modifies an event-triggered task.
@@ -18941,7 +19292,12 @@ class Client extends openapi_client_1.default {
18941
19292
  reqBodyType: "formData",
18942
19293
  bodyType: "json",
18943
19294
  });
18944
- return $tea.cast(await this.callApi(params, req, runtime), new ModifyAlertConfigurationResponse({}));
19295
+ if (tea_util_1.default.isUnset(this._signatureVersion) || !tea_util_1.default.equalString(this._signatureVersion, "v4")) {
19296
+ return $tea.cast(await this.callApi(params, req, runtime), new ModifyAlertConfigurationResponse({}));
19297
+ }
19298
+ else {
19299
+ return $tea.cast(await this.execute(params, req, runtime), new ModifyAlertConfigurationResponse({}));
19300
+ }
18945
19301
  }
18946
19302
  /**
18947
19303
  * Sets the status of scaling activities that prompt text message or email notifications.
@@ -19134,7 +19490,12 @@ class Client extends openapi_client_1.default {
19134
19490
  reqBodyType: "formData",
19135
19491
  bodyType: "json",
19136
19492
  });
19137
- return $tea.cast(await this.callApi(params, req, runtime), new ModifyEciScalingConfigurationResponse({}));
19493
+ if (tea_util_1.default.isUnset(this._signatureVersion) || !tea_util_1.default.equalString(this._signatureVersion, "v4")) {
19494
+ return $tea.cast(await this.callApi(params, req, runtime), new ModifyEciScalingConfigurationResponse({}));
19495
+ }
19496
+ else {
19497
+ return $tea.cast(await this.execute(params, req, runtime), new ModifyEciScalingConfigurationResponse({}));
19498
+ }
19138
19499
  }
19139
19500
  /**
19140
19501
  * Modifies a scaling configuration of the Elastic Container Instance type. When you call the ModifyEciScalingConfiguration operation, you can specify the ID, name, and instance properties of the scaling configuration whose information you want to modify. You can modify the instance restart policy, instance bidding policy, and elastic IP address (EIP) bandwidth.
@@ -19192,7 +19553,12 @@ class Client extends openapi_client_1.default {
19192
19553
  reqBodyType: "formData",
19193
19554
  bodyType: "json",
19194
19555
  });
19195
- return $tea.cast(await this.callApi(params, req, runtime), new ModifyInstanceAttributeResponse({}));
19556
+ if (tea_util_1.default.isUnset(this._signatureVersion) || !tea_util_1.default.equalString(this._signatureVersion, "v4")) {
19557
+ return $tea.cast(await this.callApi(params, req, runtime), new ModifyInstanceAttributeResponse({}));
19558
+ }
19559
+ else {
19560
+ return $tea.cast(await this.execute(params, req, runtime), new ModifyInstanceAttributeResponse({}));
19561
+ }
19196
19562
  }
19197
19563
  /**
19198
19564
  * Modifies the information of an Elastic Compute Service (ECS) instance. When you call the ModifyInstanceAttribute operation, you can specify attributes such as the instance ID, scaling group ID, and region ID to modify the attributes of an ECS instance in a scaling group. You can modify only the hosting attributes of instances that are manually added to scaling groups.
@@ -19272,7 +19638,12 @@ class Client extends openapi_client_1.default {
19272
19638
  reqBodyType: "formData",
19273
19639
  bodyType: "json",
19274
19640
  });
19275
- return $tea.cast(await this.callApi(params, req, runtime), new ModifyLifecycleHookResponse({}));
19641
+ if (tea_util_1.default.isUnset(this._signatureVersion) || !tea_util_1.default.equalString(this._signatureVersion, "v4")) {
19642
+ return $tea.cast(await this.callApi(params, req, runtime), new ModifyLifecycleHookResponse({}));
19643
+ }
19644
+ else {
19645
+ return $tea.cast(await this.execute(params, req, runtime), new ModifyLifecycleHookResponse({}));
19646
+ }
19276
19647
  }
19277
19648
  /**
19278
19649
  * Modifies a lifecycle hook. If an existing lifecycle hook does not meet your business requirements anymore, you can call the ModifyLifecycleHook operation to modify the information such as the scaling event, timeout period, and default action of the lifecycle hook. Before you modify a lifecycle hook, you can locate the lifecycle hook by its ID, name, or scaling group.
@@ -19334,7 +19705,12 @@ class Client extends openapi_client_1.default {
19334
19705
  reqBodyType: "formData",
19335
19706
  bodyType: "json",
19336
19707
  });
19337
- return $tea.cast(await this.callApi(params, req, runtime), new ModifyNotificationConfigurationResponse({}));
19708
+ if (tea_util_1.default.isUnset(this._signatureVersion) || !tea_util_1.default.equalString(this._signatureVersion, "v4")) {
19709
+ return $tea.cast(await this.callApi(params, req, runtime), new ModifyNotificationConfigurationResponse({}));
19710
+ }
19711
+ else {
19712
+ return $tea.cast(await this.execute(params, req, runtime), new ModifyNotificationConfigurationResponse({}));
19713
+ }
19338
19714
  }
19339
19715
  /**
19340
19716
  * Modifies event notification rules. Event notification rules support automatic sending of notifications to CloudMonitor, Message Service (MNS) topics, or MNS queues when a specified type of events occur. This helps you learn about the dynamics of your scaling group at the earliest opportunity and further automate resource management. If an existing event notification rule does not meet your business requirements, you can call the ModifyNotificationConfiguration operation to modify the event notification rule, without the need to create a new rule. Take not that you cannot modify the notification method of an event notification rule by calling this operation.
@@ -19555,7 +19931,12 @@ class Client extends openapi_client_1.default {
19555
19931
  reqBodyType: "formData",
19556
19932
  bodyType: "json",
19557
19933
  });
19558
- return $tea.cast(await this.callApi(params, req, runtime), new ModifyScalingConfigurationResponse({}));
19934
+ if (tea_util_1.default.isUnset(this._signatureVersion) || !tea_util_1.default.equalString(this._signatureVersion, "v4")) {
19935
+ return $tea.cast(await this.callApi(params, req, runtime), new ModifyScalingConfigurationResponse({}));
19936
+ }
19937
+ else {
19938
+ return $tea.cast(await this.execute(params, req, runtime), new ModifyScalingConfigurationResponse({}));
19939
+ }
19559
19940
  }
19560
19941
  /**
19561
19942
  * Modifies a scaling configuration.
@@ -19714,7 +20095,12 @@ class Client extends openapi_client_1.default {
19714
20095
  reqBodyType: "formData",
19715
20096
  bodyType: "json",
19716
20097
  });
19717
- return $tea.cast(await this.callApi(params, req, runtime), new ModifyScalingGroupResponse({}));
20098
+ if (tea_util_1.default.isUnset(this._signatureVersion) || !tea_util_1.default.equalString(this._signatureVersion, "v4")) {
20099
+ return $tea.cast(await this.callApi(params, req, runtime), new ModifyScalingGroupResponse({}));
20100
+ }
20101
+ else {
20102
+ return $tea.cast(await this.execute(params, req, runtime), new ModifyScalingGroupResponse({}));
20103
+ }
19718
20104
  }
19719
20105
  /**
19720
20106
  * Modifies a scaling group. If you want to enable policy-based automatic addition or removal of instances of a specific type to meet evolving business requirements, you can modify scaling groups to adjust your computing power with ease. The computing power refers to the instances that provide the computing capability. When your scaling group cannot meet your business requirements, you can call the ModifyScalingGroup operation to modify scaling group attributes such as the maximum, minimum, and expected numbers of instances. This prevents repeated creation and configuration of scaling groups, which saves you a lot of time and resource costs.
@@ -19843,7 +20229,12 @@ class Client extends openapi_client_1.default {
19843
20229
  reqBodyType: "formData",
19844
20230
  bodyType: "json",
19845
20231
  });
19846
- return $tea.cast(await this.callApi(params, req, runtime), new ModifyScalingRuleResponse({}));
20232
+ if (tea_util_1.default.isUnset(this._signatureVersion) || !tea_util_1.default.equalString(this._signatureVersion, "v4")) {
20233
+ return $tea.cast(await this.callApi(params, req, runtime), new ModifyScalingRuleResponse({}));
20234
+ }
20235
+ else {
20236
+ return $tea.cast(await this.execute(params, req, runtime), new ModifyScalingRuleResponse({}));
20237
+ }
19847
20238
  }
19848
20239
  /**
19849
20240
  * Modifies a scaling rule. If an existing scaling rule cannot meet your business requirements, you can call the ModifyScalingRule operation to modify the scaling rule, without the need to create a new one. This streamlines your workflow, enhancing operational efficiency while also contributing to cost optimization by avoiding redundant steps.
@@ -19904,6 +20295,9 @@ class Client extends openapi_client_1.default {
19904
20295
  if (!tea_util_1.default.isUnset(request.recurrenceValue)) {
19905
20296
  query["RecurrenceValue"] = request.recurrenceValue;
19906
20297
  }
20298
+ if (!tea_util_1.default.isUnset(request.regionId)) {
20299
+ query["RegionId"] = request.regionId;
20300
+ }
19907
20301
  if (!tea_util_1.default.isUnset(request.resourceOwnerAccount)) {
19908
20302
  query["ResourceOwnerAccount"] = request.resourceOwnerAccount;
19909
20303
  }
@@ -19939,7 +20333,12 @@ class Client extends openapi_client_1.default {
19939
20333
  reqBodyType: "formData",
19940
20334
  bodyType: "json",
19941
20335
  });
19942
- return $tea.cast(await this.callApi(params, req, runtime), new ModifyScheduledTaskResponse({}));
20336
+ if (tea_util_1.default.isUnset(this._signatureVersion) || !tea_util_1.default.equalString(this._signatureVersion, "v4")) {
20337
+ return $tea.cast(await this.callApi(params, req, runtime), new ModifyScheduledTaskResponse({}));
20338
+ }
20339
+ else {
20340
+ return $tea.cast(await this.execute(params, req, runtime), new ModifyScheduledTaskResponse({}));
20341
+ }
19943
20342
  }
19944
20343
  /**
19945
20344
  * Modifies a scheduled task. If an existing scheduled task cannot meet your business requirements, you can call the ModifyScheduledTask operation to adjust its parameter settings including the scaling rule to execute and the boundary values of your scaling group, without the need to create a new scheduled task. This operation provides a flexible way to optimize scheduled tasks.
@@ -20008,7 +20407,12 @@ class Client extends openapi_client_1.default {
20008
20407
  reqBodyType: "formData",
20009
20408
  bodyType: "json",
20010
20409
  });
20011
- return $tea.cast(await this.callApi(params, req, runtime), new RebalanceInstancesResponse({}));
20410
+ if (tea_util_1.default.isUnset(this._signatureVersion) || !tea_util_1.default.equalString(this._signatureVersion, "v4")) {
20411
+ return $tea.cast(await this.callApi(params, req, runtime), new RebalanceInstancesResponse({}));
20412
+ }
20413
+ else {
20414
+ return $tea.cast(await this.execute(params, req, runtime), new RebalanceInstancesResponse({}));
20415
+ }
20012
20416
  }
20013
20417
  /**
20014
20418
  * Rebalances the distribution of Elastic Compute Service (ECS) instances across zones. If ECS instances are unevenly distributed across multiple zones, you can call the RebalanceInstances operation to rebalance the distribution of the ECS instances across the zones.
@@ -20033,8 +20437,8 @@ class Client extends openapi_client_1.default {
20033
20437
  * Extends the time window during which Elastic Compute Service (ECS) instances stay in a Pending state. If the current time window during which an ECS instance stays in a Pending state is not sufficient for you to complete custom operations on the ECS instance, you can call the RecordLifecycleActionHeartbeat operation to extend the time window. When you call this operation, you can specify lifecycleHookId, lifecycleActionToken, and heartbeatTimeout to extend the time window for the desired ECS instance.
20034
20438
  *
20035
20439
  * @remarks
20036
- * You can call this operation only when the desired ECS instance enters a Pending state.\\
20037
- * An ECS instance can stay in a Pending state for up to six hours. Each time an ECS instance enters a Pending state, you can extend the time window during which the ECS instance stays in a Pending state up to 20 times.
20440
+ * You can call this operation only to extend the time window during which Elastic Compute Service (ECS) instances stay in a Pending state.
20441
+ * An ECS instance can stay in a Pending state for up to six hours. Each time an ECS instance enters a Pending state, you can extend the time window during which the ECS instance stays in the Pending state up to 20 times.
20038
20442
  *
20039
20443
  * @param request - RecordLifecycleActionHeartbeatRequest
20040
20444
  * @param runtime - runtime options for this request RuntimeOptions
@@ -20078,14 +20482,19 @@ class Client extends openapi_client_1.default {
20078
20482
  reqBodyType: "formData",
20079
20483
  bodyType: "json",
20080
20484
  });
20081
- return $tea.cast(await this.callApi(params, req, runtime), new RecordLifecycleActionHeartbeatResponse({}));
20485
+ if (tea_util_1.default.isUnset(this._signatureVersion) || !tea_util_1.default.equalString(this._signatureVersion, "v4")) {
20486
+ return $tea.cast(await this.callApi(params, req, runtime), new RecordLifecycleActionHeartbeatResponse({}));
20487
+ }
20488
+ else {
20489
+ return $tea.cast(await this.execute(params, req, runtime), new RecordLifecycleActionHeartbeatResponse({}));
20490
+ }
20082
20491
  }
20083
20492
  /**
20084
20493
  * Extends the time window during which Elastic Compute Service (ECS) instances stay in a Pending state. If the current time window during which an ECS instance stays in a Pending state is not sufficient for you to complete custom operations on the ECS instance, you can call the RecordLifecycleActionHeartbeat operation to extend the time window. When you call this operation, you can specify lifecycleHookId, lifecycleActionToken, and heartbeatTimeout to extend the time window for the desired ECS instance.
20085
20494
  *
20086
20495
  * @remarks
20087
- * You can call this operation only when the desired ECS instance enters a Pending state.\\
20088
- * An ECS instance can stay in a Pending state for up to six hours. Each time an ECS instance enters a Pending state, you can extend the time window during which the ECS instance stays in a Pending state up to 20 times.
20496
+ * You can call this operation only to extend the time window during which Elastic Compute Service (ECS) instances stay in a Pending state.
20497
+ * An ECS instance can stay in a Pending state for up to six hours. Each time an ECS instance enters a Pending state, you can extend the time window during which the ECS instance stays in the Pending state up to 20 times.
20089
20498
  *
20090
20499
  * @param request - RecordLifecycleActionHeartbeatRequest
20091
20500
  * @returns RecordLifecycleActionHeartbeatResponse
@@ -20164,7 +20573,12 @@ class Client extends openapi_client_1.default {
20164
20573
  reqBodyType: "formData",
20165
20574
  bodyType: "json",
20166
20575
  });
20167
- return $tea.cast(await this.callApi(params, req, runtime), new RemoveInstancesResponse({}));
20576
+ if (tea_util_1.default.isUnset(this._signatureVersion) || !tea_util_1.default.equalString(this._signatureVersion, "v4")) {
20577
+ return $tea.cast(await this.callApi(params, req, runtime), new RemoveInstancesResponse({}));
20578
+ }
20579
+ else {
20580
+ return $tea.cast(await this.execute(params, req, runtime), new RemoveInstancesResponse({}));
20581
+ }
20168
20582
  }
20169
20583
  /**
20170
20584
  * Removes one or more instances from a scaling group. If your scaling group is enabled and contains no ongoing scaling activities, you can call the RemoveInstances operation to remove instances that you no longer require from the scaling group.
@@ -20225,7 +20639,12 @@ class Client extends openapi_client_1.default {
20225
20639
  reqBodyType: "formData",
20226
20640
  bodyType: "json",
20227
20641
  });
20228
- return $tea.cast(await this.callApi(params, req, runtime), new ResumeInstanceRefreshResponse({}));
20642
+ if (tea_util_1.default.isUnset(this._signatureVersion) || !tea_util_1.default.equalString(this._signatureVersion, "v4")) {
20643
+ return $tea.cast(await this.callApi(params, req, runtime), new ResumeInstanceRefreshResponse({}));
20644
+ }
20645
+ else {
20646
+ return $tea.cast(await this.execute(params, req, runtime), new ResumeInstanceRefreshResponse({}));
20647
+ }
20229
20648
  }
20230
20649
  /**
20231
20650
  * Resumes an instance refresh task.
@@ -20238,7 +20657,7 @@ class Client extends openapi_client_1.default {
20238
20657
  return await this.resumeInstanceRefreshWithOptions(request, runtime);
20239
20658
  }
20240
20659
  /**
20241
- * Resumes suspended processes in a scaling group.
20660
+ * Resumes suspended processes in a scaling group. This operation allows Auto Scaling to proceed with executing these processes according to their predefined rules and logic. For example, if you resume the health check process in your scaling group, Auto Scaling automatically detects and removes any instances deemed unhealthy from the scaling group.
20242
20661
  *
20243
20662
  * @param request - ResumeProcessesRequest
20244
20663
  * @param runtime - runtime options for this request RuntimeOptions
@@ -20279,10 +20698,15 @@ class Client extends openapi_client_1.default {
20279
20698
  reqBodyType: "formData",
20280
20699
  bodyType: "json",
20281
20700
  });
20282
- return $tea.cast(await this.callApi(params, req, runtime), new ResumeProcessesResponse({}));
20701
+ if (tea_util_1.default.isUnset(this._signatureVersion) || !tea_util_1.default.equalString(this._signatureVersion, "v4")) {
20702
+ return $tea.cast(await this.callApi(params, req, runtime), new ResumeProcessesResponse({}));
20703
+ }
20704
+ else {
20705
+ return $tea.cast(await this.execute(params, req, runtime), new ResumeProcessesResponse({}));
20706
+ }
20283
20707
  }
20284
20708
  /**
20285
- * Resumes suspended processes in a scaling group.
20709
+ * Resumes suspended processes in a scaling group. This operation allows Auto Scaling to proceed with executing these processes according to their predefined rules and logic. For example, if you resume the health check process in your scaling group, Auto Scaling automatically detects and removes any instances deemed unhealthy from the scaling group.
20286
20710
  *
20287
20711
  * @param request - ResumeProcessesRequest
20288
20712
  * @returns ResumeProcessesResponse
@@ -20292,7 +20716,7 @@ class Client extends openapi_client_1.default {
20292
20716
  return await this.resumeProcessesWithOptions(request, runtime);
20293
20717
  }
20294
20718
  /**
20295
- * Rolls back an instance refresh task. If the configurations of an instance refresh task cannot meet your business requirements, you can call this operation to roll back the task. During the rollback process, Auto Scaling creates instances based on the active scaling configuration to replace instances that are created based on the configurations of the instance refresh task.
20719
+ * Rolls back an instance refresh task. If an instance refresh task cannot meet your business requirements, you can call the RollbackInstanceRefresh operation. When you roll back an instance refresh task, Auto Scaling creates new instances based on the active scaling configuration to replace the instances whose configurations are already updated by running the task.
20296
20720
  *
20297
20721
  * @param request - RollbackInstanceRefreshRequest
20298
20722
  * @param runtime - runtime options for this request RuntimeOptions
@@ -20330,10 +20754,15 @@ class Client extends openapi_client_1.default {
20330
20754
  reqBodyType: "formData",
20331
20755
  bodyType: "json",
20332
20756
  });
20333
- return $tea.cast(await this.callApi(params, req, runtime), new RollbackInstanceRefreshResponse({}));
20757
+ if (tea_util_1.default.isUnset(this._signatureVersion) || !tea_util_1.default.equalString(this._signatureVersion, "v4")) {
20758
+ return $tea.cast(await this.callApi(params, req, runtime), new RollbackInstanceRefreshResponse({}));
20759
+ }
20760
+ else {
20761
+ return $tea.cast(await this.execute(params, req, runtime), new RollbackInstanceRefreshResponse({}));
20762
+ }
20334
20763
  }
20335
20764
  /**
20336
- * Rolls back an instance refresh task. If the configurations of an instance refresh task cannot meet your business requirements, you can call this operation to roll back the task. During the rollback process, Auto Scaling creates instances based on the active scaling configuration to replace instances that are created based on the configurations of the instance refresh task.
20765
+ * Rolls back an instance refresh task. If an instance refresh task cannot meet your business requirements, you can call the RollbackInstanceRefresh operation. When you roll back an instance refresh task, Auto Scaling creates new instances based on the active scaling configuration to replace the instances whose configurations are already updated by running the task.
20337
20766
  *
20338
20767
  * @param request - RollbackInstanceRefreshRequest
20339
20768
  * @returns RollbackInstanceRefreshResponse
@@ -20416,7 +20845,12 @@ class Client extends openapi_client_1.default {
20416
20845
  reqBodyType: "formData",
20417
20846
  bodyType: "json",
20418
20847
  });
20419
- return $tea.cast(await this.callApi(params, req, runtime), new ScaleWithAdjustmentResponse({}));
20848
+ if (tea_util_1.default.isUnset(this._signatureVersion) || !tea_util_1.default.equalString(this._signatureVersion, "v4")) {
20849
+ return $tea.cast(await this.callApi(params, req, runtime), new ScaleWithAdjustmentResponse({}));
20850
+ }
20851
+ else {
20852
+ return $tea.cast(await this.execute(params, req, runtime), new ScaleWithAdjustmentResponse({}));
20853
+ }
20420
20854
  }
20421
20855
  /**
20422
20856
  * Scales instances. The ScaleWithAdjustment operation differs from the ExecuteScalingRule operation in that ScaleWithAdjust can directly scale instances without requiring you to create a scaling rule in advance.
@@ -20476,7 +20910,12 @@ class Client extends openapi_client_1.default {
20476
20910
  reqBodyType: "formData",
20477
20911
  bodyType: "json",
20478
20912
  });
20479
- return $tea.cast(await this.callApi(params, req, runtime), new SetGroupDeletionProtectionResponse({}));
20913
+ if (tea_util_1.default.isUnset(this._signatureVersion) || !tea_util_1.default.equalString(this._signatureVersion, "v4")) {
20914
+ return $tea.cast(await this.callApi(params, req, runtime), new SetGroupDeletionProtectionResponse({}));
20915
+ }
20916
+ else {
20917
+ return $tea.cast(await this.execute(params, req, runtime), new SetGroupDeletionProtectionResponse({}));
20918
+ }
20480
20919
  }
20481
20920
  /**
20482
20921
  * Sets deletion protection for a scaling group. If you enable deletion protection for a scaling group, you cannot delete the scaling group. If you disable deletion protection for a scaling group, you can directly delete the scaling group. You can call the SetGroupDeletionProtection operation to enable or disable deletion protection.
@@ -20527,7 +20966,12 @@ class Client extends openapi_client_1.default {
20527
20966
  reqBodyType: "formData",
20528
20967
  bodyType: "json",
20529
20968
  });
20530
- return $tea.cast(await this.callApi(params, req, runtime), new SetInstanceHealthResponse({}));
20969
+ if (tea_util_1.default.isUnset(this._signatureVersion) || !tea_util_1.default.equalString(this._signatureVersion, "v4")) {
20970
+ return $tea.cast(await this.callApi(params, req, runtime), new SetInstanceHealthResponse({}));
20971
+ }
20972
+ else {
20973
+ return $tea.cast(await this.execute(params, req, runtime), new SetInstanceHealthResponse({}));
20974
+ }
20531
20975
  }
20532
20976
  /**
20533
20977
  * Sets instance health. At times, the automatic health check system might not sufficiently determine the precise health status of your Elastic Compute Service (ECS) instances or elastic container instances. To overcome this, you can call the SetInstanceHealth operation to swiftly pinpoint problematic instances and resolve issues. This operation is designed to more precisely align with real-world business requirements and tackle O\\&M hurdles efficiently.
@@ -20587,7 +21031,12 @@ class Client extends openapi_client_1.default {
20587
21031
  reqBodyType: "formData",
20588
21032
  bodyType: "json",
20589
21033
  });
20590
- return $tea.cast(await this.callApi(params, req, runtime), new SetInstancesProtectionResponse({}));
21034
+ if (tea_util_1.default.isUnset(this._signatureVersion) || !tea_util_1.default.equalString(this._signatureVersion, "v4")) {
21035
+ return $tea.cast(await this.callApi(params, req, runtime), new SetInstancesProtectionResponse({}));
21036
+ }
21037
+ else {
21038
+ return $tea.cast(await this.execute(params, req, runtime), new SetInstancesProtectionResponse({}));
21039
+ }
20591
21040
  }
20592
21041
  /**
20593
21042
  * Puts or removes Elastic Compute Service (ECS) instances into or from the Protected state. After you put an ECS instance into the Protected state, the ECS instance will not be stopped or released when a scale-in event is triggered. In this case, you can manually delete the ECS instance in the Auto Scaling console or by calling the RemoveInstances operation.
@@ -20606,13 +21055,13 @@ class Client extends openapi_client_1.default {
20606
21055
  return await this.setInstancesProtectionWithOptions(request, runtime);
20607
21056
  }
20608
21057
  /**
20609
- * Starts an instance refresh task. If you want to batch update instance images, modify information in scaling configurations, and scale out instances based on new configurations, you can call the StartInstanceRefresh.html operation. After you start an instance refresh task, Auto Scaling gradually creates new instances from the desired configurations provided by the task to replace old instances. When all replacements are complete, the configurations of instances in your scaling group perfectly match your expectations.
21058
+ * Starts an instance refresh task. If you want to apply a new scaling configuration in a scaling group or update the image specified in a scaling configuration, you can call the StartInstanceRefresh operation.
20610
21059
  *
20611
21060
  * @remarks
20612
21061
  * Only one instance refresh task can be executed at a time in a scaling group.
20613
- * * Instance refresh tasks are currently supported only by scaling groups of the Elastic Compute Service (ECS) type and using **the priority policy**. Scaling groups that use the number of vCPUs as the method to calculate the group capacity or scaling groups whose instance reclaim mode is **Economical Mode** or **Forcibly Recycle** do not support instance refresh tasks.
20614
- * * During the execution of an instance refresh task, scaling events can be complete as expected. Take note that instances that are scaled out use the desired configurations provided by the instance refresh task.
20615
- * * Instance refresh tasks does not take effect on instances that are manually added and instances that are in the Standby and Protected states.
21062
+ * * You can start instance refresh tasks for Elastic Compute Service (ECS) instances in scaling groups that use the **priority policy** as the scaling policy. Scaling groups whose capacity is measured based on the **number of vCPUs** and scaling groups whose instance reclaim mode is **Economical Mode** or **Forcibly Recycle** do not support the StartInstanceRefresh operation.
21063
+ * * When you start an instance refresh task, scaling events can be completed as expected. Take note that instances that are scaled out use the configurations specified in the instance refresh task.
21064
+ * * The StartInstanceRefresh operation does not take effect on instances that are manually added or instances that are in the Standby and Protected states.
20616
21065
  *
20617
21066
  * @param request - StartInstanceRefreshRequest
20618
21067
  * @param runtime - runtime options for this request RuntimeOptions
@@ -20662,16 +21111,21 @@ class Client extends openapi_client_1.default {
20662
21111
  reqBodyType: "formData",
20663
21112
  bodyType: "json",
20664
21113
  });
20665
- return $tea.cast(await this.callApi(params, req, runtime), new StartInstanceRefreshResponse({}));
21114
+ if (tea_util_1.default.isUnset(this._signatureVersion) || !tea_util_1.default.equalString(this._signatureVersion, "v4")) {
21115
+ return $tea.cast(await this.callApi(params, req, runtime), new StartInstanceRefreshResponse({}));
21116
+ }
21117
+ else {
21118
+ return $tea.cast(await this.execute(params, req, runtime), new StartInstanceRefreshResponse({}));
21119
+ }
20666
21120
  }
20667
21121
  /**
20668
- * Starts an instance refresh task. If you want to batch update instance images, modify information in scaling configurations, and scale out instances based on new configurations, you can call the StartInstanceRefresh.html operation. After you start an instance refresh task, Auto Scaling gradually creates new instances from the desired configurations provided by the task to replace old instances. When all replacements are complete, the configurations of instances in your scaling group perfectly match your expectations.
21122
+ * Starts an instance refresh task. If you want to apply a new scaling configuration in a scaling group or update the image specified in a scaling configuration, you can call the StartInstanceRefresh operation.
20669
21123
  *
20670
21124
  * @remarks
20671
21125
  * Only one instance refresh task can be executed at a time in a scaling group.
20672
- * * Instance refresh tasks are currently supported only by scaling groups of the Elastic Compute Service (ECS) type and using **the priority policy**. Scaling groups that use the number of vCPUs as the method to calculate the group capacity or scaling groups whose instance reclaim mode is **Economical Mode** or **Forcibly Recycle** do not support instance refresh tasks.
20673
- * * During the execution of an instance refresh task, scaling events can be complete as expected. Take note that instances that are scaled out use the desired configurations provided by the instance refresh task.
20674
- * * Instance refresh tasks does not take effect on instances that are manually added and instances that are in the Standby and Protected states.
21126
+ * * You can start instance refresh tasks for Elastic Compute Service (ECS) instances in scaling groups that use the **priority policy** as the scaling policy. Scaling groups whose capacity is measured based on the **number of vCPUs** and scaling groups whose instance reclaim mode is **Economical Mode** or **Forcibly Recycle** do not support the StartInstanceRefresh operation.
21127
+ * * When you start an instance refresh task, scaling events can be completed as expected. Take note that instances that are scaled out use the configurations specified in the instance refresh task.
21128
+ * * The StartInstanceRefresh operation does not take effect on instances that are manually added or instances that are in the Standby and Protected states.
20675
21129
  *
20676
21130
  * @param request - StartInstanceRefreshRequest
20677
21131
  * @returns StartInstanceRefreshResponse
@@ -20681,7 +21135,7 @@ class Client extends openapi_client_1.default {
20681
21135
  return await this.startInstanceRefreshWithOptions(request, runtime);
20682
21136
  }
20683
21137
  /**
20684
- * Suspends an instance refresh task. You can call this operation to suspend an ongoing instance refresh task for observation.
21138
+ * Suspends an instance refresh task. If you are not sure that you want to roll back an ongoing instance refresh task whose configurations you think has an issue, you can call the SuspendInstanceRefresh operation to suspend the task.
20685
21139
  *
20686
21140
  * @remarks
20687
21141
  * You cannot call this operation to suspend an instance refresh task that is being rolled back.
@@ -20722,10 +21176,15 @@ class Client extends openapi_client_1.default {
20722
21176
  reqBodyType: "formData",
20723
21177
  bodyType: "json",
20724
21178
  });
20725
- return $tea.cast(await this.callApi(params, req, runtime), new SuspendInstanceRefreshResponse({}));
21179
+ if (tea_util_1.default.isUnset(this._signatureVersion) || !tea_util_1.default.equalString(this._signatureVersion, "v4")) {
21180
+ return $tea.cast(await this.callApi(params, req, runtime), new SuspendInstanceRefreshResponse({}));
21181
+ }
21182
+ else {
21183
+ return $tea.cast(await this.execute(params, req, runtime), new SuspendInstanceRefreshResponse({}));
21184
+ }
20726
21185
  }
20727
21186
  /**
20728
- * Suspends an instance refresh task. You can call this operation to suspend an ongoing instance refresh task for observation.
21187
+ * Suspends an instance refresh task. If you are not sure that you want to roll back an ongoing instance refresh task whose configurations you think has an issue, you can call the SuspendInstanceRefresh operation to suspend the task.
20729
21188
  *
20730
21189
  * @remarks
20731
21190
  * You cannot call this operation to suspend an instance refresh task that is being rolled back.
@@ -20779,7 +21238,12 @@ class Client extends openapi_client_1.default {
20779
21238
  reqBodyType: "formData",
20780
21239
  bodyType: "json",
20781
21240
  });
20782
- return $tea.cast(await this.callApi(params, req, runtime), new SuspendProcessesResponse({}));
21241
+ if (tea_util_1.default.isUnset(this._signatureVersion) || !tea_util_1.default.equalString(this._signatureVersion, "v4")) {
21242
+ return $tea.cast(await this.callApi(params, req, runtime), new SuspendProcessesResponse({}));
21243
+ }
21244
+ else {
21245
+ return $tea.cast(await this.execute(params, req, runtime), new SuspendProcessesResponse({}));
21246
+ }
20783
21247
  }
20784
21248
  /**
20785
21249
  * Suspends scaling processes. This operation empowers you to selectively pause distinct scaling processes within a particular scaling group, enabling you to carry out alternative tasks and achieve more granular management over your scaling operations.
@@ -20792,7 +21256,7 @@ class Client extends openapi_client_1.default {
20792
21256
  return await this.suspendProcessesWithOptions(request, runtime);
20793
21257
  }
20794
21258
  /**
20795
- * Creates and attaches tags. You can call the TagResources operation to uniformly create and attach tags to your Auto Scaling resources, streamlining resource management. This capability empowers you to categorize resources based on tags, thereby enhancing the overall efficiency of resource allocation and utilization.
21259
+ * Creates and adds tags. You can call the TagResources operation to uniformly create and attach tags to your Auto Scaling resources, streamlining resource management. This capability empowers you to categorize resources based on tags, thereby enhancing the overall efficiency of resource allocation and utilization.
20796
21260
  *
20797
21261
  * @remarks
20798
21262
  * You can attach up to 20 tags to a scaling group.
@@ -20842,10 +21306,15 @@ class Client extends openapi_client_1.default {
20842
21306
  reqBodyType: "formData",
20843
21307
  bodyType: "json",
20844
21308
  });
20845
- return $tea.cast(await this.callApi(params, req, runtime), new TagResourcesResponse({}));
21309
+ if (tea_util_1.default.isUnset(this._signatureVersion) || !tea_util_1.default.equalString(this._signatureVersion, "v4")) {
21310
+ return $tea.cast(await this.callApi(params, req, runtime), new TagResourcesResponse({}));
21311
+ }
21312
+ else {
21313
+ return $tea.cast(await this.execute(params, req, runtime), new TagResourcesResponse({}));
21314
+ }
20846
21315
  }
20847
21316
  /**
20848
- * Creates and attaches tags. You can call the TagResources operation to uniformly create and attach tags to your Auto Scaling resources, streamlining resource management. This capability empowers you to categorize resources based on tags, thereby enhancing the overall efficiency of resource allocation and utilization.
21317
+ * Creates and adds tags. You can call the TagResources operation to uniformly create and attach tags to your Auto Scaling resources, streamlining resource management. This capability empowers you to categorize resources based on tags, thereby enhancing the overall efficiency of resource allocation and utilization.
20849
21318
  *
20850
21319
  * @remarks
20851
21320
  * You can attach up to 20 tags to a scaling group.
@@ -20908,7 +21377,12 @@ class Client extends openapi_client_1.default {
20908
21377
  reqBodyType: "formData",
20909
21378
  bodyType: "json",
20910
21379
  });
20911
- return $tea.cast(await this.callApi(params, req, runtime), new UntagResourcesResponse({}));
21380
+ if (tea_util_1.default.isUnset(this._signatureVersion) || !tea_util_1.default.equalString(this._signatureVersion, "v4")) {
21381
+ return $tea.cast(await this.callApi(params, req, runtime), new UntagResourcesResponse({}));
21382
+ }
21383
+ else {
21384
+ return $tea.cast(await this.execute(params, req, runtime), new UntagResourcesResponse({}));
21385
+ }
20912
21386
  }
20913
21387
  /**
20914
21388
  * Removes tags from Auto Scaling resources simultaneously. This operation streamlines resource management activities, enhances system efficiency, and mitigates potential security vulnerabilities. Once a tag is removed from a particular resource, and if it is not re-added to any other resource, the system will automatically delete the unused tag.
@@ -20921,7 +21395,7 @@ class Client extends openapi_client_1.default {
20921
21395
  return await this.untagResourcesWithOptions(request, runtime);
20922
21396
  }
20923
21397
  /**
20924
- * Checks whether Auto Scaling is authorized to access Elastic Compute Service (ECS) and Elastic Container Instance resources.
21398
+ * Checks whether the specified Alibaba Cloud account assumes the AliyunServiceRoleForAutoScaling service-linked role. An account can be used to operate Elastic Compute Service (ECS) instances and elastic container instances only after it assumes the service-linked role.
20925
21399
  *
20926
21400
  * @param request - VerifyAuthenticationRequest
20927
21401
  * @param runtime - runtime options for this request RuntimeOptions
@@ -20959,10 +21433,15 @@ class Client extends openapi_client_1.default {
20959
21433
  reqBodyType: "formData",
20960
21434
  bodyType: "json",
20961
21435
  });
20962
- return $tea.cast(await this.callApi(params, req, runtime), new VerifyAuthenticationResponse({}));
21436
+ if (tea_util_1.default.isUnset(this._signatureVersion) || !tea_util_1.default.equalString(this._signatureVersion, "v4")) {
21437
+ return $tea.cast(await this.callApi(params, req, runtime), new VerifyAuthenticationResponse({}));
21438
+ }
21439
+ else {
21440
+ return $tea.cast(await this.execute(params, req, runtime), new VerifyAuthenticationResponse({}));
21441
+ }
20963
21442
  }
20964
21443
  /**
20965
- * Checks whether Auto Scaling is authorized to access Elastic Compute Service (ECS) and Elastic Container Instance resources.
21444
+ * Checks whether the specified Alibaba Cloud account assumes the AliyunServiceRoleForAutoScaling service-linked role. An account can be used to operate Elastic Compute Service (ECS) instances and elastic container instances only after it assumes the service-linked role.
20966
21445
  *
20967
21446
  * @param request - VerifyAuthenticationRequest
20968
21447
  * @returns VerifyAuthenticationResponse
@@ -21007,7 +21486,12 @@ class Client extends openapi_client_1.default {
21007
21486
  reqBodyType: "formData",
21008
21487
  bodyType: "json",
21009
21488
  });
21010
- return $tea.cast(await this.callApi(params, req, runtime), new VerifyUserResponse({}));
21489
+ if (tea_util_1.default.isUnset(this._signatureVersion) || !tea_util_1.default.equalString(this._signatureVersion, "v4")) {
21490
+ return $tea.cast(await this.callApi(params, req, runtime), new VerifyUserResponse({}));
21491
+ }
21492
+ else {
21493
+ return $tea.cast(await this.execute(params, req, runtime), new VerifyUserResponse({}));
21494
+ }
21011
21495
  }
21012
21496
  /**
21013
21497
  * Verifies whether Auto Scaling is activated. This operation guarantees that in response to shifts in business workloads or variations in incoming traffic, the system will automatically adjust resource provisioning. This auto-scaling capability enhances the overall system performance, ensuring high availability and improved flexibility to accommodate dynamic demands.