Generated java-async 2022-02-22 for Ess.

Author: sdk-team

ess-20220222/ChangeLog.txt

@@ -1,3 +1,6 @@
+2024-12-18 Version: 1.0.29
+- Generated java-async 2022-02-22 for Ess.
+
 2024-12-12 Version: 1.0.28
 - Generated java-async 2022-02-22 for Ess.
 

ess-20220222/pom.xml

@@ -3,7 +3,7 @@
   <modelVersion>4.0.0</modelVersion>
   <groupId>com.aliyun</groupId>
   <artifactId>alibabacloud-ess20220222</artifactId>
-  <version>1.0.28</version>
+  <version>1.0.29</version>
   <packaging>jar</packaging>
   <name>alibabacloud-ess20220222</name>
   <description>Alibaba Cloud Ess (20220222) Async SDK for Java

ess-20220222/src/main/java/com/aliyun/sdk/service/ess20220222/AsyncClient.java

@@ -350,10 +350,10 @@ static AsyncClient create() {
 
     /**
      * <b>description</b> :
-     * <p>  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.</p>
+     * <p>  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.</p>
      * <ul>
      * <li>You cannot specify the same recipient for notifications of different event types in a scaling group.
-     * 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.</li>
+     * 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.</li>
      * </ul>
      * 
      * @param request the request parameters of CreateNotificationConfiguration  CreateNotificationConfigurationRequest
@@ -1043,8 +1043,8 @@ static AsyncClient create() {
 
     /**
      * <b>description</b> :
-     * <p>You can call this operation only when the desired ECS instance enters a Pending state.\
-     * 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.</p>
+     * <p>You can call this operation only to extend the time window during which Elastic Compute Service (ECS) instances stay in a Pending state.
+     * 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.</p>
      * 
      * @param request the request parameters of RecordLifecycleActionHeartbeat  RecordLifecycleActionHeartbeatRequest
      * @return RecordLifecycleActionHeartbeatResponse
@@ -1139,9 +1139,9 @@ static AsyncClient create() {
      * <b>description</b> :
      * <p>  Only one instance refresh task can be executed at a time in a scaling group.</p>
      * <ul>
-     * <li>Instance refresh tasks are currently supported only by scaling groups of the Elastic Compute Service (ECS) type and using <strong>the priority policy</strong>. Scaling groups that use the number of vCPUs as the method to calculate the group capacity or scaling groups whose instance reclaim mode is <strong>Economical Mode</strong> or <strong>Forcibly Recycle</strong> do not support instance refresh tasks.</li>
-     * <li>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.</li>
-     * <li>Instance refresh tasks does not take effect on instances that are manually added and instances that are in the Standby and Protected states.</li>
+     * <li>You can start instance refresh tasks for Elastic Compute Service (ECS) instances in scaling groups that use the <strong>priority policy</strong> as the scaling policy. Scaling groups whose capacity is measured based on the <strong>number of vCPUs</strong> and scaling groups whose instance reclaim mode is <strong>Economical Mode</strong> or <strong>Forcibly Recycle</strong> do not support the StartInstanceRefresh operation.</li>
+     * <li>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.</li>
+     * <li>The StartInstanceRefresh operation does not take effect on instances that are manually added or instances that are in the Standby and Protected states.</li>
      * </ul>
      * 
      * @param request the request parameters of StartInstanceRefresh  StartInstanceRefreshRequest

ess-20220222/src/main/java/com/aliyun/sdk/service/ess20220222/DefaultAsyncClient.java

@@ -595,10 +595,10 @@ public CompletableFuture<CreateLifecycleHookResponse> createLifecycleHook(Create
 
     /**
      * <b>description</b> :
-     * <p>  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.</p>
+     * <p>  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.</p>
      * <ul>
      * <li>You cannot specify the same recipient for notifications of different event types in a scaling group.
-     * 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.</li>
+     * 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.</li>
      * </ul>
      * 
      * @param request the request parameters of CreateNotificationConfiguration  CreateNotificationConfigurationRequest
@@ -2056,8 +2056,8 @@ public CompletableFuture<RebalanceInstancesResponse> rebalanceInstances(Rebalanc
 
     /**
      * <b>description</b> :
-     * <p>You can call this operation only when the desired ECS instance enters a Pending state.\
-     * 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.</p>
+     * <p>You can call this operation only to extend the time window during which Elastic Compute Service (ECS) instances stay in a Pending state.
+     * 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.</p>
      * 
      * @param request the request parameters of RecordLifecycleActionHeartbeat  RecordLifecycleActionHeartbeatRequest
      * @return RecordLifecycleActionHeartbeatResponse
@@ -2260,9 +2260,9 @@ public CompletableFuture<SetInstancesProtectionResponse> setInstancesProtection(
      * <b>description</b> :
      * <p>  Only one instance refresh task can be executed at a time in a scaling group.</p>
      * <ul>
-     * <li>Instance refresh tasks are currently supported only by scaling groups of the Elastic Compute Service (ECS) type and using <strong>the priority policy</strong>. Scaling groups that use the number of vCPUs as the method to calculate the group capacity or scaling groups whose instance reclaim mode is <strong>Economical Mode</strong> or <strong>Forcibly Recycle</strong> do not support instance refresh tasks.</li>
-     * <li>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.</li>
-     * <li>Instance refresh tasks does not take effect on instances that are manually added and instances that are in the Standby and Protected states.</li>
+     * <li>You can start instance refresh tasks for Elastic Compute Service (ECS) instances in scaling groups that use the <strong>priority policy</strong> as the scaling policy. Scaling groups whose capacity is measured based on the <strong>number of vCPUs</strong> and scaling groups whose instance reclaim mode is <strong>Economical Mode</strong> or <strong>Forcibly Recycle</strong> do not support the StartInstanceRefresh operation.</li>
+     * <li>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.</li>
+     * <li>The StartInstanceRefresh operation does not take effect on instances that are manually added or instances that are in the Standby and Protected states.</li>
      * </ul>
      * 
      * @param request the request parameters of StartInstanceRefresh  StartInstanceRefreshRequest

ess-20220222/src/main/java/com/aliyun/sdk/service/ess20220222/models/ApplyEciScalingConfigurationRequest.java

@@ -1,6 +1,11 @@
 // This file is auto-generated, don't edit it. Thanks.
 package com.aliyun.sdk.service.ess20220222.models;
 
+import com.aliyun.sdk.gateway.pop.*;
+import darabonba.core.*;
+import darabonba.core.async.*;
+import darabonba.core.sync.*;
+import darabonba.core.client.*;
 import darabonba.core.RequestModel;
 import darabonba.core.TeaModel;
 import com.aliyun.sdk.gateway.pop.models.*;

ess-20220222/src/main/java/com/aliyun/sdk/service/ess20220222/models/ApplyEciScalingConfigurationResponse.java

@@ -1,6 +1,11 @@
 // This file is auto-generated, don't edit it. Thanks.
 package com.aliyun.sdk.service.ess20220222.models;
 
+import com.aliyun.sdk.gateway.pop.*;
+import darabonba.core.*;
+import darabonba.core.async.*;
+import darabonba.core.sync.*;
+import darabonba.core.client.*;
 import darabonba.core.RequestModel;
 import darabonba.core.TeaModel;
 import com.aliyun.sdk.gateway.pop.models.*;
@@ -13,7 +18,7 @@
  */
 public class ApplyEciScalingConfigurationResponse extends Response {
     @com.aliyun.core.annotation.NameInMap("headers")
-    private java.util.Map < String, String > headers;
+    private java.util.Map<String, String> headers;
 
     @com.aliyun.core.annotation.NameInMap("statusCode")
     private Integer statusCode;
@@ -40,7 +45,7 @@ public Builder toBuilder() {
     /**
      * @return headers
      */
-    public java.util.Map < String, String > getHeaders() {
+    public java.util.Map<String, String> getHeaders() {
         return this.headers;
     }
 
@@ -60,7 +65,7 @@ public ApplyEciScalingConfigurationResponseBody getBody() {
 
     public interface Builder extends Response.Builder<ApplyEciScalingConfigurationResponse, Builder> {
 
-        Builder headers(java.util.Map < String, String > headers);
+        Builder headers(java.util.Map<String, String> headers);
 
         Builder statusCode(Integer statusCode);
 
@@ -74,7 +79,7 @@ public interface Builder extends Response.Builder<ApplyEciScalingConfigurationRe
     private static final class BuilderImpl
             extends Response.BuilderImpl<ApplyEciScalingConfigurationResponse, Builder>
             implements Builder {
-        private java.util.Map < String, String > headers; 
+        private java.util.Map<String, String> headers; 
         private Integer statusCode; 
         private ApplyEciScalingConfigurationResponseBody body; 
 
@@ -93,7 +98,7 @@ private BuilderImpl(ApplyEciScalingConfigurationResponse response) {
          * headers.
          */
         @Override
-        public Builder headers(java.util.Map < String, String > headers) {
+        public Builder headers(java.util.Map<String, String> headers) {
             this.headers = headers;
             return this;
         }

ess-20220222/src/main/java/com/aliyun/sdk/service/ess20220222/models/ApplyEciScalingConfigurationResponseBody.java

@@ -1,6 +1,11 @@
 // This file is auto-generated, don't edit it. Thanks.
 package com.aliyun.sdk.service.ess20220222.models;
 
+import com.aliyun.sdk.gateway.pop.*;
+import darabonba.core.*;
+import darabonba.core.async.*;
+import darabonba.core.sync.*;
+import darabonba.core.client.*;
 import darabonba.core.RequestModel;
 import darabonba.core.TeaModel;
 import com.aliyun.sdk.gateway.pop.models.*;

ess-20220222/src/main/java/com/aliyun/sdk/service/ess20220222/models/ApplyScalingGroupRequest.java

@@ -1,6 +1,11 @@
 // This file is auto-generated, don't edit it. Thanks.
 package com.aliyun.sdk.service.ess20220222.models;
 
+import com.aliyun.sdk.gateway.pop.*;
+import darabonba.core.*;
+import darabonba.core.async.*;
+import darabonba.core.sync.*;
+import darabonba.core.client.*;
 import darabonba.core.RequestModel;
 import darabonba.core.TeaModel;
 import com.aliyun.sdk.gateway.pop.models.*;

ess-20220222/src/main/java/com/aliyun/sdk/service/ess20220222/models/ApplyScalingGroupResponse.java

@@ -1,6 +1,11 @@
 // This file is auto-generated, don't edit it. Thanks.
 package com.aliyun.sdk.service.ess20220222.models;
 
+import com.aliyun.sdk.gateway.pop.*;
+import darabonba.core.*;
+import darabonba.core.async.*;
+import darabonba.core.sync.*;
+import darabonba.core.client.*;
 import darabonba.core.RequestModel;
 import darabonba.core.TeaModel;
 import com.aliyun.sdk.gateway.pop.models.*;
@@ -13,7 +18,7 @@
  */
 public class ApplyScalingGroupResponse extends Response {
     @com.aliyun.core.annotation.NameInMap("headers")
-    private java.util.Map < String, String > headers;
+    private java.util.Map<String, String> headers;
 
     @com.aliyun.core.annotation.NameInMap("statusCode")
     private Integer statusCode;
@@ -40,7 +45,7 @@ public Builder toBuilder() {
     /**
      * @return headers
      */
-    public java.util.Map < String, String > getHeaders() {
+    public java.util.Map<String, String> getHeaders() {
         return this.headers;
     }
 
@@ -60,7 +65,7 @@ public ApplyScalingGroupResponseBody getBody() {
 
     public interface Builder extends Response.Builder<ApplyScalingGroupResponse, Builder> {
 
-        Builder headers(java.util.Map < String, String > headers);
+        Builder headers(java.util.Map<String, String> headers);
 
         Builder statusCode(Integer statusCode);
 
@@ -74,7 +79,7 @@ public interface Builder extends Response.Builder<ApplyScalingGroupResponse, Bui
     private static final class BuilderImpl
             extends Response.BuilderImpl<ApplyScalingGroupResponse, Builder>
             implements Builder {
-        private java.util.Map < String, String > headers; 
+        private java.util.Map<String, String> headers; 
         private Integer statusCode; 
         private ApplyScalingGroupResponseBody body; 
 
@@ -93,7 +98,7 @@ private BuilderImpl(ApplyScalingGroupResponse response) {
          * headers.
          */
         @Override
-        public Builder headers(java.util.Map < String, String > headers) {
+        public Builder headers(java.util.Map<String, String> headers) {
             this.headers = headers;
             return this;
         }

ess-20220222/src/main/java/com/aliyun/sdk/service/ess20220222/models/ApplyScalingGroupResponseBody.java

@@ -1,6 +1,11 @@
 // This file is auto-generated, don't edit it. Thanks.
 package com.aliyun.sdk.service.ess20220222.models;
 
+import com.aliyun.sdk.gateway.pop.*;
+import darabonba.core.*;
+import darabonba.core.async.*;
+import darabonba.core.sync.*;
+import darabonba.core.client.*;
 import darabonba.core.RequestModel;
 import darabonba.core.TeaModel;
 import com.aliyun.sdk.gateway.pop.models.*;