@alicloud/cs20151215 6.6.5 → 6.7.1

package/src/models/AttachInstancesRequest.ts

@@ -7,14 +7,14 @@ import { Tag } from "./Tag";
 export class AttachInstancesRequest extends $dara.Model {
   /**
    * @remarks
-   * The CPU management policy of the node. The following policies are supported if the Kubernetes version of the cluster is 1.12.6 or later:
+   * The CPU management policy of the node. The following policies are supported for clusters of version 1.12.6 or later:
    * 
-   * *   `static`: allows pods with specific resource characteristics on the node to be granted enhanced CPU affinity and exclusivity.
-   * *   `none`: uses default CPU affinity.
+   * - `static`: Allows pods with certain resource characteristics on the node to be granted enhanced CPU affinity and exclusivity.
+   * - `none`: Uses the existing default CPU affinity scheme.
    * 
-   * Default value: `none`
+   * Default value: `none`.
    * 
-   * >  This parameter is not supported if you specify `nodepool_id`.
+   * > After you specify `nodepool_id`, this parameter is not supported.
    * 
    * @example
    * none
@@ -22,19 +22,20 @@ export class AttachInstancesRequest extends $dara.Model {
   cpuPolicy?: string;
   /**
    * @remarks
-   * Specifies whether to store container data and images on data disks. Valid value:
+   * Specifies whether to store container data and images on a data cloud disk. Valid values:
    * 
-   * *   `true`: stores container data and images on data disks.
-   * *   `false`: does not store container data or images on data disks.
+   * - `true`: Stores container data and images on a data cloud disk.
+   * 
+   * - `false`: Does not store container data and images on a data cloud disk.
    * 
    * Default value: `false`.
    * 
-   * How data disks are attached:
    * 
-   * *   If the ECS instance is already attached with data disks and the file system of the last data disk is not initialized, the system automatically formats this data disk to ext4. Then, the system uses the disk to store the data in the /var/lib/docker and /var/lib/kubelet directories.
-   * *   If no data disk is attached to the ECS instance, the system does not purchase a new data disk.
+   * Data cloud disk mounting rules:
    * 
-   * >  If you choose to store container data and images on data disks and a data disk is already attached to the ECS instance, the original data on this data disk is cleared. You can back up the disk to prevent data loss.
+   * - If the ECS instance has data cloud disks mounted and the file system of the last data cloud disk is not initialized, the system automatically formats the data cloud disk to EXT4 to store the content of /var/lib/docker and /var/lib/kubelet (the default data directories for the Docker container runtime and the kubelet component, respectively).
+   * - If the ECS instance has no data cloud disks mounted, no new data cloud disk is mounted.
+   * > If you choose to store data on a data cloud disk and the ECS instance already has data cloud disks mounted, existing data on the data cloud disk is lost. Back up your data in advance.
    * 
    * @example
    * false
@@ -42,13 +43,13 @@ export class AttachInstancesRequest extends $dara.Model {
   formatDisk?: boolean;
   /**
    * @remarks
-   * The custom image ID. If you do not specify this parameter, the default system image is used.
+   * The custom image ID.
    * 
-   * > 
+   * - If you specify a custom image ID, the system cloud disk image of the instance is replaced with the custom image.
    * 
-   * *   If you specify a custom image, the custom image is used to deploy the operating system on the system disk of the node.
+   * - If you do not specify this parameter, the default system image is used.
    * 
-   * *   This parameter is not supported if you specify `nodepool_id`.
+   * > After you specify `nodepool_id`, this parameter is not supported.
    * 
    * @example
    * aliyun_2_1903_x64_20G_alibase_20200529.vhd
@@ -56,21 +57,22 @@ export class AttachInstancesRequest extends $dara.Model {
   imageId?: string;
   /**
    * @remarks
-   * The ECS instances that you want to add.
+   * The list of ECS instances to be added.
    * 
    * This parameter is required.
    */
   instances?: string[];
   /**
    * @remarks
-   * Specifies whether the node that you want to add is an Edge Node Service (ENS) node. Valid value:
+   * Specifies whether the node to be added is an edge node, that is, an Edge Node Service (ENS) node. Valid values:
+   * 
+   * - `true`: The node to be added is an edge node.
    * 
-   * *   `true`: the node that you want to add is an ENS node.
-   * *   `false`: the node that you want to add is not an ENS node.
+   * - `false`: The node to be added is not an edge node.
    * 
    * Default value: `false`.
    * 
-   * >  If the node that you want to add is an ENS node, you must set the value to `true`. This allows you to identify the node.
+   * > If the node is an edge node, set this parameter to `true` to identify the node type as an ENS node.
    * 
    * @example
    * false
@@ -78,10 +80,11 @@ export class AttachInstancesRequest extends $dara.Model {
   isEdgeWorker?: boolean;
   /**
    * @remarks
-   * Specifies whether to retain the instance name. Valid value:
+   * Specifies whether to retain the original instance name. Valid values:
+   * 
+   * - `true`: Retains the instance name.
    * 
-   * *   `true`: retains the instance name.
-   * *   `false`: does not retain the instance name.
+   * - `false`: Does not retain the instance name.
    * 
    * Default value: `false`.
    * 
@@ -91,9 +94,8 @@ export class AttachInstancesRequest extends $dara.Model {
   keepInstanceName?: boolean;
   /**
    * @remarks
-   * The name of the key pair used to log on to the ECS instances. You must specify this parameter or `login_password`.
-   * 
-   * >  This parameter is not supported if you specify `nodepool_id`.
+   * The name of the key pair for the instances to be added. Specify either key_pair or password. You can also leave both parameters empty.
+   * > After you specify `nodepool_id`, this parameter is not supported.
    * 
    * @example
    * security-key
@@ -101,7 +103,7 @@ export class AttachInstancesRequest extends $dara.Model {
   keyPair?: string;
   /**
    * @remarks
-   * The ID of the node pool to which the node is added. If you do not specify this parameter, the node is added to the default node pool.
+   * The node pool ID. If you do not specify this parameter, the node is added to the default node pool.
    * 
    * @example
    * np615c0e0966124216a0412e10afe0****
@@ -109,9 +111,14 @@ export class AttachInstancesRequest extends $dara.Model {
   nodepoolId?: string;
   /**
    * @remarks
-   * The SSH logon password used to log on to the ECS instances. You must specify this parameter or `key_pair`. The password must be 8 to 30 characters in length, and must contain at least three of the following character types: uppercase letters, lowercase letters, digits, and special characters. The password cannot contain backslashes (\\\\) or double quotation marks (").
+   * The SSH logon password for the instances to be added. Specify either key_pair or password. You can also leave both parameters empty.
+   * 
+   * The password must meet the following requirements:
+   * - The password must be 8 to 30 characters in length.
+   * - The password must contain uppercase letters, lowercase letters, digits, and special characters at the same time.
+   * - The password cannot contain backslashes (\\) or double quotation marks (").
    * 
-   * The password is encrypted during data transfer to ensure security.
+   * The password is encrypted during transmission for security purposes.
    * 
    * @example
    * Hello1234
@@ -119,31 +126,45 @@ export class AttachInstancesRequest extends $dara.Model {
   password?: string;
   /**
    * @remarks
-   * A list of ApsaraDB RDS instances.
+   * The list of ApsaraDB RDS instances.
    */
   rdsInstances?: string[];
   /**
    * @remarks
    * The container runtime.
+   * > After you specify `nodepool_id`, this parameter is not supported.
+   * 
+   * name: The name of the container runtime. ACK supports the following three container runtimes:
+   * 
+   * - containerd: Recommended. Supported by all cluster versions.
+   * - Sandboxed-Container.runv: Sandboxed container that provides higher isolation. Supported by clusters of version 1.24 or earlier.
+   * - docker: Supported by clusters of version 1.22 or earlier.
+   * 
+   * Default value: containerd.
+   * 
+   * containerd: The container runtime version. Default value: the latest version.
    * 
-   * >  This parameter is not supported if you specify `nodepool_id`.
+   * For more information about changes to the sandboxed container runtime, see [Release notes for the sandboxed container runtime](https://help.aliyun.com/document_detail/160312.html).
    */
   runtime?: Runtime;
   /**
    * @remarks
-   * The labels that you want to add to the node. When you add labels to a node, the following rules apply:
+   * The node labels. Label definition rules:
    * 
-   * *   A label is a case-sensitive key-value pair. You can add up to 20 labels.
-   * *   The key must be unique and cannot exceed 64 characters in length. The value can be empty and cannot exceed 128 characters in length. Keys and values cannot start with `aliyun`, `acs:`, `https://`, or `http://`. For more information, see [Labels and Selectors](https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/#syntax-and-character-set).
+   * - Labels are case-sensitive key-value pairs. You can set up to 20 labels.
+   * - Label keys cannot be duplicate and can be up to 64 characters in length.
+   * - Label values can be empty and can be up to 128 characters in length.
+   * - Label keys and values cannot start with `aliyun`, `acs:`, `https://`, or `http://`.
    * 
-   * >  This parameter is not supported if you specify `nodepool_id`.
+   * For more information, see [Labels and Selectors](https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/#syntax-and-character-set).
+   * > After you specify `nodepool_id`, this parameter is not supported.
    */
   tags?: Tag[];
   /**
    * @remarks
-   * The user-defined data on the node. For more information, see [Use instance user data to automatically run commands or scripts on instance startup](https://help.aliyun.com/document_detail/49121.html).
+   * The instance user data of the node. For more information, see [Generate instance user data](https://help.aliyun.com/document_detail/49121.html).
    * 
-   * >  This parameter is not supported if you specify `nodepool_id`.
+   * > After you specify `nodepool_id`, this parameter is not supported.
    * 
    * @example
    * IyEvdXNyL2Jpbi9iYXNoCmVjaG8gIkhlbGxvIEFDSyEi

package/src/models/AttachInstancesResponseBody.ts

@@ -5,7 +5,7 @@ import * as $dara from '@darabonba/typescript';
 export class AttachInstancesResponseBodyList extends $dara.Model {
   /**
    * @remarks
-   * The code that indicates the task result.
+   * The status code of the node addition result.
    * 
    * @example
    * 200
@@ -13,7 +13,7 @@ export class AttachInstancesResponseBodyList extends $dara.Model {
   code?: string;
   /**
    * @remarks
-   * The ID of the ECS instance.
+   * The ECS instance ID.
    * 
    * @example
    * i-2ze0lgm3y6iylcbt****
@@ -21,7 +21,7 @@ export class AttachInstancesResponseBodyList extends $dara.Model {
   instanceId?: string;
   /**
    * @remarks
-   * Indicates whether the ECS instance is successfully added to the ACK cluster.
+   * The description of the node addition result.
    * 
    * @example
    * successful
@@ -55,7 +55,7 @@ export class AttachInstancesResponseBodyList extends $dara.Model {
 export class AttachInstancesResponseBody extends $dara.Model {
   /**
    * @remarks
-   * The details of the added nodes.
+   * The list of node addition information.
    */
   list?: AttachInstancesResponseBodyList[];
   /**

package/src/models/AttachInstancesToNodePoolRequest.ts

@@ -5,19 +5,20 @@ import * as $dara from '@darabonba/typescript';
 export class AttachInstancesToNodePoolRequest extends $dara.Model {
   /**
    * @remarks
-   * Specifies whether to store container data and images on data disks. Valid values:
+   * Specifies whether to store container data and images on a data cloud disk. Valid values:
    * 
-   * *   `true`: stores container data and images on data disks.
-   * *   `false`: does not store container data or images on data disks.
+   * - `true`: Stores container data and images on a data cloud disk.
+   * 
+   * - `false`: Does not store container data and images on a data cloud disk.
    * 
    * Default value: `false`.
    * 
-   * How to mount a data disk:
    * 
-   * *   If the ECS instances are already mounted with data disks and the file system of the last data disk is not initialized, the system automatically formats this data disk to ext4 and mounts it to /var/lib/docker and /var/lib/kubelet.
-   * *   If no data disk is attached to the ECS instances, the system does not purchase a new data disk.
+   * Data cloud disk mounting rules:
    * 
-   * > If you choose to store container data and images on a data disk and the data disk is already mounted to the ECS instance, the existing data on the data disk will be cleared. You can back up the disk to avoid data loss.
+   * - If the ECS instance has data cloud disks attached and the file system of the last data cloud disk is not initialized, the system automatically formats the data cloud disk as EXT4 to store /var/lib/docker and /var/lib/kubelet.
+   * - If the ECS instance has no data cloud disks attached, no new data cloud disk is mounted.
+   * > If you choose to store data on a data cloud disk and the ECS instance already has data cloud disks attached, existing data on the data cloud disk is lost. Back up your data in advance.
    * 
    * @example
    * false
@@ -25,15 +26,16 @@ export class AttachInstancesToNodePoolRequest extends $dara.Model {
   formatDisk?: boolean;
   /**
    * @remarks
-   * The IDs of the instances to be added.
+   * The list of ECS instances to be added.
    */
   instances?: string[];
   /**
    * @remarks
-   * Specifies whether to retain the instance name. Valid values:
+   * Specifies whether to retain the original instance name. Valid values:
+   * 
+   * - `true`: Retains the instance name.
    * 
-   * *   `true`: retains the instance name.
-   * *   `false`: does not retain the instance name.
+   * - `false`: Does not retain the instance name.
    * 
    * Default value: `true`.
    * 
@@ -43,7 +45,7 @@ export class AttachInstancesToNodePoolRequest extends $dara.Model {
   keepInstanceName?: boolean;
   /**
    * @remarks
-   * The SSH password that is used to log on to the instance.
+   * The SSH logon password of the instances to be added.
    * 
    * @example
    * ******

package/src/models/CheckControlPlaneLogEnableResponseBody.ts

@@ -5,7 +5,7 @@ import * as $dara from '@darabonba/typescript';
 export class CheckControlPlaneLogEnableResponseBody extends $dara.Model {
   /**
    * @remarks
-   * The ID of the Alibaba Cloud account to which the resource belongs.
+   * The Alibaba Cloud account ID.
    * 
    * @example
    * 162981*****
@@ -13,14 +13,14 @@ export class CheckControlPlaneLogEnableResponseBody extends $dara.Model {
   aliuid?: string;
   /**
    * @remarks
-   * The control plane components for which log collection is enabled.
+   * The list of components for which control plane logging is enabled.
    * 
    * This parameter is required.
    */
   components?: string[];
   /**
    * @remarks
-   * The name of the Simple Log Service project that you want to use to store the logs of control plane components.
+   * The name of the Simple Log Service (SLS) project that stores the control plane component logs.
    * 
    * Default value: k8s-log-$Cluster ID.
    * 
@@ -30,9 +30,7 @@ export class CheckControlPlaneLogEnableResponseBody extends $dara.Model {
   logProject?: string;
   /**
    * @remarks
-   * The retention period of the log data stored in the Logstore. Valid values: 1 to 3000. Unit: days.
-   * 
-   * Default value: 30.
+   * The data retention period of logs in the SLS Logstore. Unit: days.
    * 
    * @example
    * 30

package/src/models/CheckServiceRoleRequest.ts

@@ -5,7 +5,7 @@ import * as $dara from '@darabonba/typescript';
 export class CheckServiceRoleRequestRoles extends $dara.Model {
   /**
    * @remarks
-   * The server role name. For more information about the service roles and their permissions in ACK, see [ACK roles](https://help.aliyun.com/document_detail/86483.html).
+   * Container service role name. For information about container service roles and permission scopes included in ACK, see [ACK service roles](https://help.aliyun.com/document_detail/86483.html).
    * 
    * This parameter is required.
    * 
@@ -37,7 +37,7 @@ export class CheckServiceRoleRequestRoles extends $dara.Model {
 export class CheckServiceRoleRequest extends $dara.Model {
   /**
    * @remarks
-   * The list of service roles you want to check.
+   * The list of service roles to check.
    * 
    * This parameter is required.
    */

package/src/models/CheckServiceRoleResponseBody.ts

@@ -5,12 +5,7 @@ import * as $dara from '@darabonba/typescript';
 export class CheckServiceRoleResponseBodyRoles extends $dara.Model {
   /**
    * @remarks
-   * Indicates whether the service role is assigned to ACK.
-   * 
-   * Valid values:
-   * 
-   * *   true: The role is assigned to ACK.
-   * *   false: The role is not assigned to ACK.
+   * Indicates whether the service role has been granted.
    * 
    * @example
    * true
@@ -18,7 +13,7 @@ export class CheckServiceRoleResponseBodyRoles extends $dara.Model {
   granted?: boolean;
   /**
    * @remarks
-   * The message that is displayed for a role that is not assigned to ACK.
+   * The prompt message returned when the service role is not granted.
    * 
    * @example
    * The role does not exist: AliyunCSManagedAutoScalerRole
@@ -26,7 +21,7 @@ export class CheckServiceRoleResponseBodyRoles extends $dara.Model {
   message?: string;
   /**
    * @remarks
-   * The name of the service role.
+   * The service role name.
    * 
    * @example
    * AliyunCSManagedAutoScalerRole
@@ -60,7 +55,7 @@ export class CheckServiceRoleResponseBodyRoles extends $dara.Model {
 export class CheckServiceRoleResponseBody extends $dara.Model {
   /**
    * @remarks
-   * The check results.
+   * The service role check results.
    */
   roles?: CheckServiceRoleResponseBodyRoles[];
   static names(): { [key: string]: string } {

package/src/models/CleanClusterUserPermissionsRequest.ts

@@ -5,10 +5,9 @@ import * as $dara from '@darabonba/typescript';
 export class CleanClusterUserPermissionsRequest extends $dara.Model {
   /**
    * @remarks
-   * Specifies whether to forcefully delete the specified kubeconfig files. Valid values:
-   * 
-   * *   false (default): checks the cluster access records within the previous seven days before deleting the kubeconfig files. The kubeconfig files are not deleted if cluster access records are found or fail to be retrieved.
-   * *   true: forcefully deletes the kubeconfig files without checking the cluster access records.
+   * Specifies whether to force delete the specified KubeConfig. Valid values:
+   * - false (default): Before deleting the KubeConfig, the system checks whether cluster access records exist within the last seven days. If access records exist or cannot be retrieved, the deletion is not allowed.
+   * - true: Force deletes the KubeConfig without checking cluster access records.
    * 
    * @example
    * false

package/src/models/CleanUserPermissionsRequest.ts

@@ -5,15 +5,14 @@ import * as $dara from '@darabonba/typescript';
 export class CleanUserPermissionsRequest extends $dara.Model {
   /**
    * @remarks
-   * The cluster IDs. If you specify a list of cluster IDs, only the kubeconfig files and RBAC permissions of the clusters that belong to the current user in the list are revoked.
+   * The list of cluster IDs. If this list is specified, only the KubeConfig credentials and RBAC permissions of the current user in the specified clusters are cleaned up.
    */
   clusterIds?: string[];
   /**
    * @remarks
-   * Specifies whether to forcefully delete the specified kubeconfig files. Valid values:
-   * 
-   * *   false (default): checks the cluster access records within the previous seven days before deleting the kubeconfig files. The kubeconfig files are not deleted if cluster access records are found or fail to be retrieved.
-   * *   true: forcefully deletes the kubeconfig files without checking the cluster access records.
+   * Specifies whether to force delete the specified KubeConfig. Valid values:
+   * - false (default): Before deleting the KubeConfig, the system checks whether cluster access records exist within the last seven days. If access records exist or cannot be retrieved, the deletion is not allowed.
+   * - true: Force deletes the KubeConfig without checking cluster access records.
    * 
    * @example
    * false

package/src/models/CleanUserPermissionsShrinkRequest.ts

@@ -5,15 +5,14 @@ import * as $dara from '@darabonba/typescript';
 export class CleanUserPermissionsShrinkRequest extends $dara.Model {
   /**
    * @remarks
-   * The cluster IDs. If you specify a list of cluster IDs, only the kubeconfig files and RBAC permissions of the clusters that belong to the current user in the list are revoked.
+   * The list of cluster IDs. If this list is specified, only the KubeConfig credentials and RBAC permissions of the current user in the specified clusters are cleaned up.
    */
   clusterIdsShrink?: string;
   /**
    * @remarks
-   * Specifies whether to forcefully delete the specified kubeconfig files. Valid values:
-   * 
-   * *   false (default): checks the cluster access records within the previous seven days before deleting the kubeconfig files. The kubeconfig files are not deleted if cluster access records are found or fail to be retrieved.
-   * *   true: forcefully deletes the kubeconfig files without checking the cluster access records.
+   * Specifies whether to force delete the specified KubeConfig. Valid values:
+   * - false (default): Before deleting the KubeConfig, the system checks whether cluster access records exist within the last seven days. If access records exist or cannot be retrieved, the deletion is not allowed.
+   * - true: Force deletes the KubeConfig without checking cluster access records.
    * 
    * @example
    * false

package/src/models/CreateAutoRepairPolicyRequest.ts

@@ -5,7 +5,7 @@ import * as $dara from '@darabonba/typescript';
 export class CreateAutoRepairPolicyRequestRulesIncidents extends $dara.Model {
   /**
    * @remarks
-   * The incident name.
+   * The name of the fault.
    * 
    * @example
    * Node.FaultNeedReboot.HOST
@@ -13,7 +13,7 @@ export class CreateAutoRepairPolicyRequestRulesIncidents extends $dara.Model {
   name?: string;
   /**
    * @remarks
-   * The incident type.
+   * The type of the fault.
    * 
    * @example
    * system
@@ -45,7 +45,7 @@ export class CreateAutoRepairPolicyRequestRulesIncidents extends $dara.Model {
 export class CreateAutoRepairPolicyRequestRulesRepairProcedureInterventionApprovedLabel extends $dara.Model {
   /**
    * @remarks
-   * The label key.
+   * The key of the label.
    * 
    * @example
    * k8s.aliyun.com/incident
@@ -53,7 +53,7 @@ export class CreateAutoRepairPolicyRequestRulesRepairProcedureInterventionApprov
   key?: string;
   /**
    * @remarks
-   * The label value.
+   * The value of the label.
    * 
    * @example
    * approved
@@ -85,7 +85,7 @@ export class CreateAutoRepairPolicyRequestRulesRepairProcedureInterventionApprov
 export class CreateAutoRepairPolicyRequestRulesRepairProcedureInterventionInquiringLabel extends $dara.Model {
   /**
    * @remarks
-   * The label key.
+   * The key of the label.
    * 
    * @example
    * k8s.aliyun.com/incident
@@ -93,7 +93,7 @@ export class CreateAutoRepairPolicyRequestRulesRepairProcedureInterventionInquir
   key?: string;
   /**
    * @remarks
-   * The label value.
+   * The value of the label.
    * 
    * @example
    * inquiring
@@ -125,7 +125,7 @@ export class CreateAutoRepairPolicyRequestRulesRepairProcedureInterventionInquir
 export class CreateAutoRepairPolicyRequestRulesRepairProcedureIntervention extends $dara.Model {
   /**
    * @remarks
-   * The label that grants authorization for the repair step. To approve the step, add this label to the node. After the action is complete, ACK automatically removes both the inquiry and approval labels for this step. If this label is not added promptly, the repair procedure halts and the node remains impaired.
+   * The label configuration for authorization confirmation. When you add the following label to the node, you authorize ACK to execute the action in this stage. After completing the action in this stage, ACK automatically removes the authorization inquiry and authorization confirmation labels for this stage. If you do not add the following label to authorize the action promptly, ACK does not execute the action in this stage or subsequent actions, and the node may remain in a damaged state.
    */
   approvedLabel?: CreateAutoRepairPolicyRequestRulesRepairProcedureInterventionApprovedLabel;
   /**
@@ -138,12 +138,12 @@ export class CreateAutoRepairPolicyRequestRulesRepairProcedureIntervention exten
   enable?: boolean;
   /**
    * @remarks
-   * The label used to request authorization for the repair step. When this step begins, ACK applies this label to the node and waits for approval before performing the action.
+   * The label configuration for authorization inquiry. When this stage is reached, ACK adds the following label to your node and waits for you to authorize the execution of the action in this stage.
    */
   inquiringLabel?: CreateAutoRepairPolicyRequestRulesRepairProcedureInterventionInquiringLabel;
   /**
    * @remarks
-   * The manual approval type.
+   * The type of manual approval.
    * 
    * @example
    * label
@@ -185,17 +185,17 @@ export class CreateAutoRepairPolicyRequestRulesRepairProcedureIntervention exten
 export class CreateAutoRepairPolicyRequestRulesRepairProcedure extends $dara.Model {
   /**
    * @remarks
-   * Configuration parameters for the repair step.
+   * The configuration parameters of the repair procedure.
    */
   config?: { [key: string]: any };
   /**
    * @remarks
-   * Settings for manual intervention.
+   * The configuration for manual intervention in the procedure.
    */
   intervention?: CreateAutoRepairPolicyRequestRulesRepairProcedureIntervention;
   /**
    * @remarks
-   * The name of the repair step.
+   * The name of the procedure.
    * 
    * @example
    * Drain
@@ -235,7 +235,7 @@ export class CreateAutoRepairPolicyRequestRulesRepairProcedure extends $dara.Mod
 export class CreateAutoRepairPolicyRequestRules extends $dara.Model {
   /**
    * @remarks
-   * The incidents that the rule detects.
+   * The list of identified faults.
    */
   incidents?: CreateAutoRepairPolicyRequestRulesIncidents[];
   /**
@@ -275,7 +275,7 @@ export class CreateAutoRepairPolicyRequestRules extends $dara.Model {
 export class CreateAutoRepairPolicyRequest extends $dara.Model {
   /**
    * @remarks
-   * The name of the auto repair policy.
+   * The name of the self-healing rule.
    * 
    * @example
    * test
@@ -283,7 +283,7 @@ export class CreateAutoRepairPolicyRequest extends $dara.Model {
   name?: string;
   /**
    * @remarks
-   * The resource subtype to which the auto repair policy applies.
+   * The resource subtype that the self-healing rule can be bound to.
    * 
    * @example
    * ess
@@ -291,7 +291,7 @@ export class CreateAutoRepairPolicyRequest extends $dara.Model {
   resourceSubType?: string;
   /**
    * @remarks
-   * The resource type to which the auto repair policy applies.
+   * The resource type that the self-healing rule can be bound to.
    * 
    * @example
    * nodepool
@@ -299,7 +299,7 @@ export class CreateAutoRepairPolicyRequest extends $dara.Model {
   resourceType?: string;
   /**
    * @remarks
-   * The sub-rules for the auto repair policy.
+   * The list of self-healing sub-rules.
    * 
    * @example
    * ["np-xxx"]

package/src/models/CreateAutoRepairPolicyResponseBody.ts

@@ -5,7 +5,7 @@ import * as $dara from '@darabonba/typescript';
 export class CreateAutoRepairPolicyResponseBody extends $dara.Model {
   /**
    * @remarks
-   * The auto-repair policy ID.
+   * The self-healing rule ID.
    * 
    * @example
    * r-xxxxxxx