tencentcloud-sdk-nodejs-intl-en 3.0.1051 → 3.0.1053

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "tencentcloud-sdk-nodejs-intl-en",
-  "version": "3.0.1051",
+  "version": "3.0.1053",
   "description": "腾讯云 API NODEJS SDK",
   "main": "index.js",
   "scripts": {

package/tencentcloud/as/v20180419/as_client.js

@@ -193,7 +193,8 @@ class AsClient extends AbstractClient {
     /**
      * This API is used to pause the ongoing instance refresh activity.
 * In the paused status, the scaling group will also be disabled.
-* Instances that are currently being updated will not be paused, instances pending updates will have their updates paused.
+* The instances that are currently being updated or scaled out will not be paused, but instances pending updates will have their updates paused.
+* During scale-in, all instances have already been updated and cannot be paused.
      * @param {StopInstanceRefreshRequest} req
      * @param {function(string, StopInstanceRefreshResponse):void} cb
      * @public
@@ -571,11 +572,12 @@ When scale-in protection is enabled, the instance will not be removed in scale-i
     }
 
     /**
-     * This API is used to generate a new instance refresh activity, which also supports batched refreshing and operations such as pausing, resuming, and canceling. The interface returns the RefreshActivityId for the rollback activity.
-* Instances pending refresh in the original activity are updated to a canceled status. Nonexistent instances are disregarded, while instances in all other statuses proceed to enter the rollback process.
-* Instances that were being refreshed in the original activity will not be immediately terminated; instead, the rollback activity will be executed after their refresh has been completed.
-* Rollback is supported for activities that are in a paused status or those with the most recent successful refresh; it is not supported for activities in other statuses.
-* When the original refresh activity involves reinstalling instances, for the ImageId parameter, it will automatically restore to the image ID before the rollback; for parameters such as UserData, EnhancedService, LoginSettings, and HostName, they will still be retrieved from the launch configuration, requiring users to manually modify the launch configuration before initiating the rollback.
+     * This API is used to generate a new instance refresh activity, which also supports batch refreshing and operations such as pausing, resuming, and canceling. This API returns RefreshActivityId for the rollback activity.
+* The instances pending refresh in the original activity are updated to canceled status. Nonexistent instances are disregarded, while instances in all other statuses proceed to enter the rollback process.
+* The instances that are being refreshed in the original activity will not be immediately terminated. Instead, the rollback activity will be executed after their refresh complete.
+* Rollback is supported for activities that are in the paused status or those succeeded in refreshing last time. It is not supported for activities in other statuses.
+* When the original refresh activity involves reinstalling instances, for the ImageId parameter, it will automatically recover to the image ID before the rollback; for parameters such as UserData, EnhancedService, LoginSettings, and HostName, they will still be read from the launch configuration, requiring users to manually modify the launch configuration before initiating the rollback.
+* The rollback activity does not support the MaxSurge parameter currently.
      * @param {RollbackInstanceRefreshRequest} req
      * @param {function(string, RollbackInstanceRefreshResponse):void} cb
      * @public
@@ -920,7 +922,9 @@ If you configured a notification, Auto Scaling will notify the TDMQ queue of the
     }
 
     /**
-     * This API is used to resume the paused instance refresh activity, allowing it to retry failed instances in the current batch or proceed with refreshing subsequent batches. Note that calling this interface is ineffective when the activity is not in a paused status.
+     * This API is used to resume the paused instance refresh activity, allowing it to retry failed instances in the current batch or proceed with refreshing subsequent batches. Note that calling this API is ineffective when the activity is not in a paused status.
+
+- When the MaxSurge parameter is used, the activity may be paused due to scale-out or scale-in failures. This API can also be used to retry scaling operations.
      * @param {ResumeInstanceRefreshRequest} req
      * @param {function(string, ResumeInstanceRefreshResponse):void} cb
      * @public
@@ -932,9 +936,11 @@ If you configured a notification, Auto Scaling will notify the TDMQ queue of the
 
     /**
      * This API is used to cancel the instance refresh activity of the scaling group.
-* Batches that have already been refreshed or are currently being refreshed remain unaffected; batches pending refresh will be canceled.
-* If a refresh fails, the affected instances will remain in the standby status and require manual intervention by the user to either attempt to exit the standby status or destroy the instances.
-* Rollback operations are not allowed after cancellation, and resuming is also unsupported.
+* The batches that have already been refreshed or are currently being refreshed remain unaffected, but the batches pending refresh will be canceled.
+* If a refresh fails, the affected instances will remain in the secondary status, and require manual intervention to exit the secondary status or terminate the instances.
+* Rollback operations are not allowed after cancellation, and recovery is also unsupported.
+* The instances temporarily scaled out due to the MaxSurge parameter are automatically terminated after cancellation.
+* During scale-in, all instances have already been updated and cannot be canceled.
      * @param {CancelInstanceRefreshRequest} req
      * @param {function(string, CancelInstanceRefreshResponse):void} cb
      * @public

package/tencentcloud/as/v20180419/models.js

@@ -2793,11 +2793,20 @@ class RollingUpdateSettings extends  AbstractModel {
         this.BatchNumber = null;
 
         /**
-         * Pause policy between batches. Default value: Automatic. Valid values: <br><li>FIRST_BATCH_PAUSE: Pause after the first batch update completes.</li> <li>BATCH_INTERVAL_PAUSE: Pause between each batch update.</li> <li>AUTOMATIC: No pauses.
+         * Pause policy between batches. Default value: Automatic. Valid values:
+<li>FIRST_BATCH_PAUSE: Pause after the first batch of updates is completed.</li>
+<li>BATCH_INTERVAL_PAUSE: Pause between batches.</li>
+<li>AUTOMATIC: Do not pause.</li>
          * @type {string || null}
          */
         this.BatchPause = null;
 
+        /**
+         * The maximum additional quantity of instances. After this parameter is set, create a batch of additional pay-as-you-go instances according to the launch configuration before the rolling update starts. After the rolling update is completed, the additional instances will be terminated.This parameter is used to ensure a certain number of instances available during the rolling update. The maximum additional quantity of instances cannot exceed the number of refreshing instances in a single batch of the rolling update. The rollback process does not support this parameter currently.
+         * @type {number || null}
+         */
+        this.MaxSurge = null;
+
     }
 
     /**
@@ -2809,6 +2818,7 @@ class RollingUpdateSettings extends  AbstractModel {
         }
         this.BatchNumber = 'BatchNumber' in params ? params.BatchNumber : null;
         this.BatchPause = 'BatchPause' in params ? params.BatchPause : null;
+        this.MaxSurge = 'MaxSurge' in params ? params.MaxSurge : null;
 
     }
 }
@@ -7136,7 +7146,7 @@ class ResumeInstanceRefreshRequest extends  AbstractModel {
         this.RefreshActivityId = null;
 
         /**
-         * The recovery method for the current batch's failed instances. If there are no failed instances, this parameter becomes invalid. Default value: RETRY. Valid values: <br><li>RETRY: Retry refreshing failed instances in the current batch.</li> <li>CONTINUE: Skip failed instances in the current batch.
+         * Recovery mode of instances that have failed to be refreshed in the current batch. If there are no failed instances, this parameter is invalid. Default value: RETRY. Valid values: <li>RETRY: Retry instances that have failed to be refreshed in the current batch.</li> <li>CONTINUE: Skip instances that have failed to be refreshed in the current batch.</li>
          * @type {string || null}
          */
         this.ResumeMode = null;

package/tencentcloud/common/sdk_version.js

@@ -1,2 +1,2 @@
-const sdkVersion = "3.0.1051";
+const sdkVersion = "3.0.1053";
 module.exports = sdkVersion