@alicloud/cs20151215 7.2.5 → 7.2.6

package/src/models/RemoveNodePoolNodesRequest.ts

@@ -5,10 +5,9 @@ import * as $dara from '@darabonba/typescript';
 export class RemoveNodePoolNodesRequest extends $dara.Model {
   /**
    * @remarks
-   * Specifies whether to remove the nodes concurrently. Valid values:
-   * 
-   * - true: removes the nodes from the scaling group concurrently.
-   * - false: removes the nodes from the scaling group sequentially.
+   * Specifies whether to remove nodes concurrently. Valid values:
+   * - true: Nodes are removed from the scaling group concurrently.
+   * - false: Nodes are removed from the scaling group sequentially.
    * 
    * Default value: false.
    * 
@@ -19,8 +18,8 @@ export class RemoveNodePoolNodesRequest extends $dara.Model {
   /**
    * @remarks
    * Specifies whether to drain the nodes. Valid values:
-   * - true: drains the nodes.
-   * - false: does not drain the nodes.
+   * - true: Drain the nodes.
+   * - false: Do not drain the nodes.
    * 
    * @example
    * true
@@ -28,14 +27,22 @@ export class RemoveNodePoolNodesRequest extends $dara.Model {
   drainNode?: boolean;
   /**
    * @remarks
-   * The list of instances to remove.
+   * The drain timeout period in seconds. Valid values: (0, 1800]. Default value: 1800. This parameter takes effect only when drain_node is set to true.
+   * 
+   * @example
+   * 600
+   */
+  drainTimeoutSeconds?: number;
+  /**
+   * @remarks
+   * The list of instances to be removed.
    */
   instanceIds?: string[];
   /**
    * @remarks
    * **[Deprecated]**
    * 
-   * The list of nodes to remove.
+   * The list of nodes to be removed.
    * 
    * >Danger: This parameter is deprecated. Use `instance_ids` instead.</danger>
    * 
@@ -45,10 +52,10 @@ export class RemoveNodePoolNodesRequest extends $dara.Model {
   /**
    * @remarks
    * Specifies whether automatic release the nodes. Valid values:
-   * - true: releases the nodes.
-   * - false: does not release the nodes.
+   * - true: Release the nodes.
+   * - false: Do not release the nodes.
    * 
-   * Subscription nodes are not automatically released when you remove them. Automatic release subscription nodes, [change the billing method of the nodes from subscription to pay-as-you-go](https://www.alibabacloud.com/help/en/ecs/change-the-billing-method-of-an-instance-from-subscription-to-pay-as-you-go-1) and then release them in the ECS console.
+   * Removing nodes does not automatically release subscription nodes. Automatic release subscription nodes, [change the billing method of the nodes from subscription to pay-as-you-go](https://www.alibabacloud.com/help/en/ecs/change-the-billing-method-of-an-instance-from-subscription-to-pay-as-you-go-1), and then log on to the ECS console automatic release them.
    * 
    * @example
    * true
@@ -58,6 +65,7 @@ export class RemoveNodePoolNodesRequest extends $dara.Model {
     return {
       concurrency: 'concurrency',
       drainNode: 'drain_node',
+      drainTimeoutSeconds: 'drain_timeout_seconds',
       instanceIds: 'instance_ids',
       nodes: 'nodes',
       releaseNode: 'release_node',
@@ -68,6 +76,7 @@ export class RemoveNodePoolNodesRequest extends $dara.Model {
     return {
       concurrency: 'boolean',
       drainNode: 'boolean',
+      drainTimeoutSeconds: 'number',
       instanceIds: { 'type': 'array', 'itemType': 'string' },
       nodes: { 'type': 'array', 'itemType': 'string' },
       releaseNode: 'boolean',

package/src/models/RemoveNodePoolNodesShrinkRequest.ts

@@ -5,10 +5,9 @@ import * as $dara from '@darabonba/typescript';
 export class RemoveNodePoolNodesShrinkRequest extends $dara.Model {
   /**
    * @remarks
-   * Specifies whether to remove the nodes concurrently. Valid values:
-   * 
-   * - true: removes the nodes from the scaling group concurrently.
-   * - false: removes the nodes from the scaling group sequentially.
+   * Specifies whether to remove nodes concurrently. Valid values:
+   * - true: Nodes are removed from the scaling group concurrently.
+   * - false: Nodes are removed from the scaling group sequentially.
    * 
    * Default value: false.
    * 
@@ -19,8 +18,8 @@ export class RemoveNodePoolNodesShrinkRequest extends $dara.Model {
   /**
    * @remarks
    * Specifies whether to drain the nodes. Valid values:
-   * - true: drains the nodes.
-   * - false: does not drain the nodes.
+   * - true: Drain the nodes.
+   * - false: Do not drain the nodes.
    * 
    * @example
    * true
@@ -28,14 +27,22 @@ export class RemoveNodePoolNodesShrinkRequest extends $dara.Model {
   drainNode?: boolean;
   /**
    * @remarks
-   * The list of instances to remove.
+   * The drain timeout period in seconds. Valid values: (0, 1800]. Default value: 1800. This parameter takes effect only when drain_node is set to true.
+   * 
+   * @example
+   * 600
+   */
+  drainTimeoutSeconds?: number;
+  /**
+   * @remarks
+   * The list of instances to be removed.
    */
   instanceIdsShrink?: string;
   /**
    * @remarks
    * **[Deprecated]**
    * 
-   * The list of nodes to remove.
+   * The list of nodes to be removed.
    * 
    * >Danger: This parameter is deprecated. Use `instance_ids` instead.</danger>
    * 
@@ -45,10 +52,10 @@ export class RemoveNodePoolNodesShrinkRequest extends $dara.Model {
   /**
    * @remarks
    * Specifies whether automatic release the nodes. Valid values:
-   * - true: releases the nodes.
-   * - false: does not release the nodes.
+   * - true: Release the nodes.
+   * - false: Do not release the nodes.
    * 
-   * Subscription nodes are not automatically released when you remove them. Automatic release subscription nodes, [change the billing method of the nodes from subscription to pay-as-you-go](https://www.alibabacloud.com/help/en/ecs/change-the-billing-method-of-an-instance-from-subscription-to-pay-as-you-go-1) and then release them in the ECS console.
+   * Removing nodes does not automatically release subscription nodes. Automatic release subscription nodes, [change the billing method of the nodes from subscription to pay-as-you-go](https://www.alibabacloud.com/help/en/ecs/change-the-billing-method-of-an-instance-from-subscription-to-pay-as-you-go-1), and then log on to the ECS console automatic release them.
    * 
    * @example
    * true
@@ -58,6 +65,7 @@ export class RemoveNodePoolNodesShrinkRequest extends $dara.Model {
     return {
       concurrency: 'concurrency',
       drainNode: 'drain_node',
+      drainTimeoutSeconds: 'drain_timeout_seconds',
       instanceIdsShrink: 'instance_ids',
       nodesShrink: 'nodes',
       releaseNode: 'release_node',
@@ -68,6 +76,7 @@ export class RemoveNodePoolNodesShrinkRequest extends $dara.Model {
     return {
       concurrency: 'boolean',
       drainNode: 'boolean',
+      drainTimeoutSeconds: 'number',
       instanceIdsShrink: 'string',
       nodesShrink: 'string',
       releaseNode: 'boolean',

package/src/models/UpdateClusterAuditLogConfigRequest.ts

@@ -6,7 +6,8 @@ export class UpdateClusterAuditLogConfigRequest extends $dara.Model {
   /**
    * @remarks
    * Specifies whether to disable the cluster audit log feature. Valid values:
-   * - false: enables the audit log feature or updates the audit log configurations.
+   * - false: enables the audit log feature or updates the audit log configuration.
+   * 
    * - true: disables the audit log feature.
    * 
    * @example
@@ -15,9 +16,9 @@ export class UpdateClusterAuditLogConfigRequest extends $dara.Model {
   disable?: boolean;
   /**
    * @remarks
-   * The [SLS project](https://help.aliyun.com/document_detail/48873.html) where the [Logstore](https://help.aliyun.com/document_detail/48874.html) for cluster audit logs is located.
+   * The [SLS project](https://help.aliyun.com/document_detail/48873.html) where the [Logstore](https://help.aliyun.com/document_detail/48874.html) for cluster audit logs is stored.
    * 
-   * - The default value is k8s-log-{clusterid}.
+   * - Default value: k8s-log-{clusterid}.
    * 
    * - After you enable the cluster audit log feature, a Logstore for cluster audit logs is created in the specified SLS project.
    * 

package/src/models/UpdateUserPermissionsRequest.ts

@@ -5,9 +5,9 @@ import * as $dara from '@darabonba/typescript';
 export class UpdateUserPermissionsRequestBody extends $dara.Model {
   /**
    * @remarks
-   * The ID of the target cluster.
+   * The ID of the target cluster for authorization.
    * 
-   * This parameter is not required when the role_type parameter is set to all-clusters.
+   * This parameter is not required when the role_type parameter is set to `all-clusters`.
    * 
    * @example
    * c796c60***
@@ -15,10 +15,10 @@ export class UpdateUserPermissionsRequestBody extends $dara.Model {
   cluster?: string;
   /**
    * @remarks
-   * Specifies whether the authorization is custom. A custom authorization uses a custom ClusterRole name for the role_name parameter.
+   * Specifies whether the authorization is a custom authorization, which means the role_name parameter uses a custom ClusterRole name.
    * 
-   * Valid values:
    * - true: The authorized role is a custom cluster role.
+   * 
    * - false: The authorized role is a preset cluster role.
    * 
    * @example
@@ -27,10 +27,10 @@ export class UpdateUserPermissionsRequestBody extends $dara.Model {
   isCustom?: boolean;
   /**
    * @remarks
-   * Specifies whether the authorized entity is a RAM role.
+   * Specifies whether the authorization is for a RAM role.
    * 
-   * Valid values:
    * - true: The authorization is for a RAM role.
+   * 
    * - false: The authorization is for a Resource Access Management (RAM) user.
    * 
    * @example
@@ -39,7 +39,7 @@ export class UpdateUserPermissionsRequestBody extends $dara.Model {
   isRamRole?: boolean;
   /**
    * @remarks
-   * The namespace name. This parameter is empty by default for cluster-level authorization.
+   * The name of the namespace. This parameter is empty by default when the authorization is at the cluster level.
    * 
    * @example
    * test
@@ -49,15 +49,16 @@ export class UpdateUserPermissionsRequestBody extends $dara.Model {
    * @remarks
    * The preset role name. Valid values:
    * 
-   * - admin: administrator.
-   * - admin-view: read-only administrator.
-   * - ops: O&M engineer.
-   * - dev: developer.
-   * - restricted: restricted user.
+   * - `admin`: administrator.
+   * - `admin-view`: read-only administrator.
+   * - `ops`: O&M engineer.
+   * - `dev`: developer.
+   * - `restricted`: restricted user.
    * - A custom ClusterRole name.
    * 
-   * > - The admin, admin-view, and ops roles do not support authorization at the **namespace level**.
-   * > - The admin-view role does not support authorization at the **all-clusters level**.
+   * 
+   * > - `admin`, `admin-view`, and `ops`: Authorization at the **namespace level** is not supported.
+   * > - `admin-view`: Authorization at the **all-clusters level** is not supported.
    * 
    * @example
    * ops
@@ -67,9 +68,9 @@ export class UpdateUserPermissionsRequestBody extends $dara.Model {
    * @remarks
    * The authorization type. Valid values:
    * 
-   * - cluster: cluster level.
-   * - namespace: namespace level.
-   * - all-clusters: all-clusters level.
+   * - `cluster`: cluster level.
+   * - `namespace`: namespace level.
+   * - `all-clusters`: all-clusters level.
    * 
    * @example
    * cluster
@@ -114,11 +115,10 @@ export class UpdateUserPermissionsRequest extends $dara.Model {
   body?: UpdateUserPermissionsRequestBody[];
   /**
    * @remarks
-   * The authorization method. Valid values:
-   * 
-   * - `apply`: Fully updates permissions. This operation overwrites the existing cluster permissions of the target RAM user or RAM role. The request must include all permission configurations to be granted to the target RAM user or RAM role.
-   * - `delete`: Deletes permissions. This operation deletes only the cluster authorization information specified in the request and does not affect other cluster permissions of the RAM user or RAM role.
-   * - `patch`: Adds permissions. This operation adds only the cluster authorization information specified in the request and does not affect other cluster permissions of the RAM user or RAM role.
+   * The authorization mode. Valid values:
+   * - `apply`: Fully updates permissions. The operation to fully update the cluster authorization information of a RAM user or RAM role overwrites the existing cluster permissions of the target RAM user or RAM role. The request must include all permission configurations that you want to grant to the target RAM user or RAM role.
+   * - `delete`: Deletes permissions. Only the cluster authorization information specified in the request is deleted. Other cluster permissions of the RAM user or RAM role are not affected.
+   * - `patch`: Adds permissions. Only the cluster authorization information specified in the request is added. Other cluster permissions of the RAM user or RAM role are not affected.
    * 
    * Default value: `apply`.
    *