@alicloud/sae20190506 2.12.1 → 2.12.3

package/src/models/DeployApplicationRequest.ts

@@ -7,7 +7,7 @@ import { SidecarContainerConfig } from "./SidecarContainerConfig";
 export class DeployApplicationRequest extends $dara.Model {
   /**
    * @remarks
-   * The Alibaba Cloud Resource Name (ARN) required for a RAM role to obtain images across accounts. For more information, see [Grant permissions across Alibaba Cloud accounts by using a RAM role](https://help.aliyun.com/document_detail/223585.html).
+   * The ARN of the RAM role required to pull images across accounts. For more information, see [Authorize cross-account image pulls using RAM roles](https://help.aliyun.com/document_detail/223585.html).
    * 
    * @example
    * acs:ram::123456789012****:role/adminrole
@@ -15,17 +15,31 @@ export class DeployApplicationRequest extends $dara.Model {
   acrAssumeRoleArn?: string;
   /**
    * @remarks
-   * The ID of Container Registry Enterprise Edition instance N. This parameter is required when the **ImageUrl** parameter is set to the URL of an image in an ACR Enterprise Edition instance.
+   * The Container Registry Enterprise Edition instance ID. Required when **ImageUrl** is from Container Registry Enterprise Edition.
    * 
    * @example
    * cri-xxxxxx
    */
   acrInstanceId?: string;
+  /**
+   * @remarks
+   * The AliyunAgent version.
+   * 
+   * @example
+   * 4.4.2
+   */
   agentVersion?: string;
+  /**
+   * @remarks
+   * The ALB gateway readiness gate configuration.
+   * 
+   * @example
+   * default
+   */
   albIngressReadinessGate?: string;
   /**
    * @remarks
-   * The ID of the application.
+   * The ID of the application to deploy.
    * 
    * This parameter is required.
    * 
@@ -35,10 +49,11 @@ export class DeployApplicationRequest extends $dara.Model {
   appId?: string;
   /**
    * @remarks
-   * Specifies whether to associate an EIP with the node pool. Take note of the following rules:
+   * Whether to associate an EIP. Values:
+   * 
+   * - **true**: Associate.
    * 
-   * *   **true**: The EIP is associated with the application instance.
-   * *   **false**: The EIP is not associated with the application instance.
+   * - **false**: Do not associate.
    * 
    * @example
    * true
@@ -46,10 +61,11 @@ export class DeployApplicationRequest extends $dara.Model {
   associateEip?: boolean;
   /**
    * @remarks
-   * Specifies whether to automatically enable an auto scaling policy for the application. Take note of the following rules:
+   * Whether to automatically enable application Auto Scaling rules. Values:
    * 
-   * *   **true**: turns on Logon-free Sharing
-   * *   **false**: turns off Logon-free Sharing
+   * - **true**: Enable.
+   * 
+   * - **false**: Disable.
    * 
    * @example
    * true
@@ -57,7 +73,7 @@ export class DeployApplicationRequest extends $dara.Model {
   autoEnableApplicationScalingRule?: boolean;
   /**
    * @remarks
-   * The interval between batches during a batch release. Unit: minutes.
+   * The wait time between batches, in seconds.
    * 
    * @example
    * 10
@@ -65,23 +81,25 @@ export class DeployApplicationRequest extends $dara.Model {
   batchWaitTime?: number;
   /**
    * @remarks
-   * The description of the change order.
+   * The description of the release task.
    * 
    * @example
-   * Start the application
+   * Start application
    */
   changeOrderDesc?: string;
   /**
    * @remarks
-   * The command that is used to start the image. The command must be an existing executable object in the container. Sample statements:
+   * The startup command for your image. This command must be an executable object inside the container. Example:
    * 
-   *     command:
-   *           - echo
-   *           - abc
-   *           - >
-   *           - file0
+   * ```
+   * command:
+   *       - echo
+   *       - abc
+   *       - >
+   *       - file0
+   * ```
    * 
-   * In this example, the Command parameter is set to `Command="echo", CommandArgs=["abc", ">", "file0"]`.
+   * In this example, Command="echo" and `CommandArgs=["abc", ">", "file0"]`.
    * 
    * @example
    * echo
@@ -89,11 +107,11 @@ export class DeployApplicationRequest extends $dara.Model {
   command?: string;
   /**
    * @remarks
-   * The parameters of the image startup command. The CommandArgs parameter specifies the parameters that are required for the **Command** parameter. You can specify the name in one of the following formats:
+   * The arguments for the startup command **Command**. Format:
    * 
    * `["a","b"]`
    * 
-   * In the preceding example, the CommandArgs parameter is set to `CommandArgs=["abc", ">", "file0"]`. The data type of `["abc", ">", "file0"]` must be an array of strings in the JSON format. This parameter is optional.
+   * In the earlier example, `CommandArgs=["abc", ">", "file0"]`. The value `["abc", ">", "file0"]` must be converted to a string in JSON array format. Leave this field empty if no arguments are needed.
    * 
    * @example
    * ["a","b"]
@@ -101,14 +119,15 @@ export class DeployApplicationRequest extends $dara.Model {
   commandArgs?: string;
   /**
    * @remarks
-   * The description of the **ConfigMap** instance mounted to the application. Use configurations created on the Configuration Items page to configure containers. The following table describes the parameters that are used in the preceding statements.
+   * The mount description for a **ConfigMap**. Use configuration items created on the namespace configuration page to inject configuration into your container. Parameters:
+   * 
+   * - **configMapId**: The ID of the ConfigMap instance. Get it by calling the [ListNamespacedConfigMaps](https://help.aliyun.com/document_detail/176917.html) API.
    * 
-   * *   **congfigMapId**: the ID of the ConfigMap instance. You can call the [ListNamespacedConfigMaps](https://help.aliyun.com/document_detail/176917.html) operation to obtain the ID.
-   * *   **key**: the key.
+   * - **key**: The key.
    * 
-   * > You can use `sae-sys-configmap-all` to mount all keys.
+   * > You can mount all keys by passing `sae-sys-configmap-all`.
    * 
-   * *   **mountPath**: the mount path in the container.
+   * - **mountPath**: The mount path.
    * 
    * @example
    * [{"configMapId":16,"key":"test","mountPath":"/tmp"}]
@@ -116,16 +135,23 @@ export class DeployApplicationRequest extends $dara.Model {
   configMapMountDesc?: string;
   /**
    * @remarks
-   * The CPU specifications that are required for each instance. Unit: millicores. This parameter cannot be set to 0. Valid values:
+   * The CPU required per instance, in milliCPU. Cannot be zero. Supported fixed specifications:
+   * 
+   * - **500**
+   * 
+   * - **1000**
+   * 
+   * - **2000**
    * 
-   * *   **500**
-   * *   **1000**
-   * *   **2000**
-   * *   **4000**
-   * *   **8000**
-   * *   **12000**
-   * *   **16000**
-   * *   **32000**
+   * - **4000**
+   * 
+   * - **8000**
+   * 
+   * - **12000**
+   * 
+   * - **16000**
+   * 
+   * - **32000**
    * 
    * @example
    * 1000
@@ -133,10 +159,11 @@ export class DeployApplicationRequest extends $dara.Model {
   cpu?: number;
   /**
    * @remarks
-   * The custom mappings between hostnames and IP addresses in the container. Take note of the following rules:
+   * Custom host mappings inside your container. Values:
+   * 
+   * - **hostName**: A domain name or hostname.
    * 
-   * *   **hostName**: the domain name or hostname.
-   * *   **ip**: the IP address.
+   * - **ip**: An IP address.
    * 
    * @example
    * [{"hostName":"samplehost","ip":"127.0.0.1"}]
@@ -144,7 +171,7 @@ export class DeployApplicationRequest extends $dara.Model {
   customHostAlias?: string;
   /**
    * @remarks
-   * Custom image type. To it to empty string to use pre-built image.
+   * The custom image type. Set to an empty string for non-custom images:
    * 
    * - internet: Public network image
    * 
@@ -156,10 +183,11 @@ export class DeployApplicationRequest extends $dara.Model {
   customImageNetworkType?: string;
   /**
    * @remarks
-   * This parameter takes effect only for applications that are in the Stopped state. If you call the **DeployApplication** operation to manage a running application, the application is immediately redeployed.
+   * This parameter applies only to stopped applications. If you call **DeployApplication** on a running application, it deploys immediately.
    * 
-   * *   **true** (default): specifies that the system immediately deploys the application, enables new configurations, and pulls application instances.
-   * *   **false**: specifies that the system only enables the new configurations.
+   * - **true**: Default. Deploys immediately, applies the new configuration, and starts instances.
+   * 
+   * - **false**: Applies the new configuration only. Does not start application instances.
    * 
    * @example
    * true
@@ -167,12 +195,16 @@ export class DeployApplicationRequest extends $dara.Model {
   deploy?: string;
   /**
    * @remarks
-   * The version of .NET
+   * The .NET framework version:
    * 
    * - .NET 3.1
+   * 
    * - .NET 5.0
+   * 
    * - .NET 6.0
+   * 
    * - .NET 7.0
+   * 
    * - .NET 8.0
    * 
    * @example
@@ -181,19 +213,27 @@ export class DeployApplicationRequest extends $dara.Model {
   dotnet?: string;
   /**
    * @remarks
-   * The version of the container, such as Ali-Tomcat, in which an application developed based on High-speed Service Framework (HSF) is deployed.
+   * The version of the application runtime environment for HSF applications, such as Ali-Tomcat containers.
    * 
    * @example
    * 3.5.3
    */
   edasContainerVersion?: string;
+  /**
+   * @remarks
+   * The configuration for shared temporary storage.
+   * 
+   * @example
+   * [{\\"name\\":\\"workdir\\",\\"mountPath\\":\\"/usr/local/tomcat/webapps\\"}]
+   */
   emptyDirDesc?: string;
   /**
    * @remarks
-   * Indicates whether access to Application High Availability Service (AHAS) is enabled. Take note of the following rules:
+   * Whether to integrate with AHAS. Values:
    * 
-   * *   **true**: Access to AHAS is enabled.
-   * *   **false**: Access to AHAS is disabled.
+   * - **true**: Integrate with AHAS.
+   * 
+   * - **false**: Do not integrate with AHAS.
    * 
    * @example
    * false
@@ -201,11 +241,11 @@ export class DeployApplicationRequest extends $dara.Model {
   enableAhas?: string;
   /**
    * @remarks
-   * Enable CPU Burst.
+   * Whether to enable CPU Burst:
    * 
-   * true: enable
+   * - true: Enable.
    * 
-   * false: disable
+   * - false: Do not enable.
    * 
    * @example
    * true
@@ -213,36 +253,51 @@ export class DeployApplicationRequest extends $dara.Model {
   enableCpuBurst?: boolean;
   /**
    * @remarks
-   * Indicates whether canary release rules are enabled. Canary release rules apply only to applications in Spring Cloud and Dubbo frameworks. Take note of the following rules:
+   * Whether to enable traffic canary rules. These rules apply only to Spring Cloud and Dubbo applications. Values:
+   * 
+   * - **true**: Enable canary rules.
    * 
-   * *   **true**: The canary release rules are enabled.
-   * *   **false**: The canary release rules are disabled.
+   * - **false**: Disable canary rules.
    * 
    * @example
    * false
    */
   enableGreyTagRoute?: boolean;
+  /**
+   * @remarks
+   * Whether to reuse the namespace Agent version configuration.
+   * 
+   * @example
+   * true
+   */
   enableNamespaceAgentVersion?: boolean;
   /**
    * @remarks
-   * Enable new ARMS features.
+   * Whether to enable the new ARMS feature:
    * 
-   * - true: enable
+   * - true: Enable.
    * 
-   * - false: disable
+   * - false: Do not enable.
    * 
    * @example
    * true
    */
   enableNewArms?: boolean;
+  /**
+   * @remarks
+   * Whether to enable Prometheus custom metric collection.
+   * 
+   * @example
+   * false
+   */
   enablePrometheus?: boolean;
   /**
    * @remarks
-   * Enable Sidecar resource isolation.
+   * Whether to isolate sidecar resources:
    * 
-   * true: enable
+   * - true: Isolate.
    * 
-   * false: disable
+   * - false: Do not isolate.
    * 
    * @example
    * true
@@ -250,36 +305,60 @@ export class DeployApplicationRequest extends $dara.Model {
   enableSidecarResourceIsolated?: boolean;
   /**
    * @remarks
-   * The environment variables. You can configure custom environment variables or reference a ConfigMap. If you want to reference a ConfigMap, you must first create a ConfigMap. For more information, see [CreateConfigMap](https://help.aliyun.com/document_detail/176914.html). Take note of the following rules:
+   * The environment variables for your container. You can define custom variables or reference configuration items. To reference a configuration item, first create a ConfigMap instance. For more information, see [CreateConfigMap](https://help.aliyun.com/document_detail/176914.html). Values:
+   * 
+   * - Custom configuration
+   * 
+   *   - **name**: The name of the environment variable.
+   * 
+   *   - **value**: The value of the environment variable. Takes precedence over valueFrom.
+   * 
+   * - Reference a configuration item (valueFrom)
+   * 
+   *   - **name**: The name of the environment variable. You can reference a single key or all keys. To reference all keys, use `sae-sys-configmap-all-<configmap-name>`, for example `sae-sys-configmap-all-test1`.
+   * 
+   *   - **valueFrom**: The reference type. Set to `configMapRef`.
    * 
-   * *   Customize
+   *   - **configMapId**: The ID of the ConfigMap instance.
    * 
-   *     *   **name**: the name of the environment variable.
-   *     *   **value**: the value of the environment variable.
+   *   - **key**: The key. Omit this field if you reference all keys.
    * 
-   * *   Reference ConfigMap
+   * - Reference a secret (valueFrom)
    * 
-   *     *   **name**: the name of the environment variable. You can reference one or all keys. If you want to reference all keys, specify `sae-sys-configmap-all-<ConfigMap name>`. Example: `sae-sys-configmap-all-test1`.
-   *     *   **valueFrom**: the reference of the environment variable. Set the value to `configMapRef`.
-   *     *   **configMapId**: the ConfigMap ID.
-   *     *   **key**: the key. If you want to reference all keys, do not configure this parameter.
+   *   - **name**: The name of the environment variable. You can reference a single key or all keys. To reference all keys, use `sae-sys-secret-all-<secret-name>`, for example `sae-sys-secret-all-test1`.
    * 
-   * *   Reference secret dictionary
+   *   - **valueFrom**: The reference type. Set to `secretRef`.
    * 
-   *     *   **name**: the name of the environment variable. You can reference one or all keys. If you want to reference all keys, specify `sae-sys-secret-all-<Secret dictionary name>`. Example: `sae-sys-secret-all-test1`.
-   *     *   **valueFrom**: the reference of the environment variable. Set the value to `secretRef`.
-   *     *   **secretId**: the secret dictionary ID.
-   *     *   **key**: the key. If you want to reference all keys, do not configure this parameter.
+   *   - **secretId**: The ID of the secret.
+   * 
+   *   - **key**: The key. Omit this field if you reference all keys.
    * 
    * @example
-   * [{"name":"envtmp","value":"0"}]
+   * [ { "name": "sae-sys-configmap-all-hello", "valueFrom": { "configMapRef": { "configMapId": 100, "key": "" } } }, { "name": "hello", "valueFrom": { "configMapRef": { "configMapId": 101, "key": "php-fpm" } } }, { "name": "sae-sys-secret-all-hello", "valueFrom": { “secretRef": { “secretId": 100, "key": "" } } }, { "name": “password”, "valueFrom": { “secretRef": { “secretId": 101, "key": “password” } } }, { "name": "envtmp", "value": "newenv" } ]
    */
   envs?: string;
   gpuConfig?: string;
+  /**
+   * @remarks
+   * The Nginx version:
+   * 
+   * - nginx 1.20
+   * 
+   * - nginx 1.22
+   * 
+   * - nginx 1.24
+   * 
+   * - nginx 1.26
+   * 
+   * - nginx 1.28
+   * 
+   * @example
+   * nginx 1.28
+   */
   html?: string;
   /**
    * @remarks
-   * The ID of the corresponding Secret.
+   * The ID of the corresponding secret.
    * 
    * @example
    * 10
@@ -287,7 +366,7 @@ export class DeployApplicationRequest extends $dara.Model {
   imagePullSecrets?: string;
   /**
    * @remarks
-   * The URL of the image. This parameter is returned only if the **PackageType** parameter is set to **Image**.
+   * The registry address of your image. Required when **Package Type** is **Image**.
    * 
    * @example
    * registry.cn-hangzhou.aliyuncs.com/sae_test/ali_sae_test:0.0.1
@@ -295,12 +374,12 @@ export class DeployApplicationRequest extends $dara.Model {
   imageUrl?: string;
   /**
    * @remarks
-   * Initialize container configuration.
+   * The initialization container configuration.
    */
   initContainersConfig?: InitContainerConfig[];
   /**
    * @remarks
-   * The arguments in the JAR package. The arguments are used to start the application container. The default startup command is `$JAVA_HOME/bin/java $JarStartOptions -jar $CATALINA_OPTS "$package_path" $JarStartArgs`.
+   * Startup arguments for your JAR package. Default startup command: `$JAVA_HOME/bin/java $JarStartOptions -jar $CATALINA_OPTS "$package_path" $JarStartArgs`
    * 
    * @example
    * -Xms4G -Xmx4G
@@ -308,7 +387,7 @@ export class DeployApplicationRequest extends $dara.Model {
   jarStartArgs?: string;
   /**
    * @remarks
-   * The option settings in the JAR package. The settings are used to start the application container. The default startup command for application deployment is `$JAVA_HOME/bin/java $JarStartOptions -jar $CATALINA_OPTS "$package_path" $JarStartArgs`.
+   * Startup options for your JAR package. Default startup command: `$JAVA_HOME/bin/java $JarStartOptions -jar $CATALINA_OPTS "$package_path" $JarStartArgs`
    * 
    * @example
    * custom-option
@@ -316,16 +395,21 @@ export class DeployApplicationRequest extends $dara.Model {
   jarStartOptions?: string;
   /**
    * @remarks
-   * The version of the Java development kit (JDK) on which the deployment package of the application depends. The following versions are supported:
+   * The JDK version that your deployment package depends on. Supported versions include the following:
+   * 
+   * - **Open JDK 8**
+   * 
+   * - **Open JDK 7**
+   * 
+   * - **Dragonwell 11**
+   * 
+   * - **Dragonwell 8**
    * 
-   * *   **Open JDK 8**
-   * *   **Open JDK 7**
-   * *   **Dragonwell 11**
-   * *   **Dragonwell 8**
-   * *   **openjdk-8u191-jdk-alpine3.9**
-   * *   **openjdk-7u201-jdk-alpine3.9**
+   * - **openjdk-8u191-jdk-alpine3.9**
    * 
-   * This parameter is not returned if the **PackageType** parameter is set to **Image**.
+   * - **openjdk-7u201-jdk-alpine3.9**
+   * 
+   * This parameter is not supported when **Package Type** is **Image**.
    * 
    * @example
    * Open JDK 8
@@ -333,60 +417,99 @@ export class DeployApplicationRequest extends $dara.Model {
   jdk?: string;
   /**
    * @remarks
-   * The logging configurations of Message Queue for Apache Kafka. Take note of the following rules:
+   * The configuration for collecting logs to Kafka. Values:
+   * 
+   * - **kafkaEndpoint**: The endpoint for the Kafka API.
+   * 
+   * - **kafkaInstanceId**: The Kafka instance ID.
    * 
-   * *   **kafkaEndpoint**: the endpoint of the Message Queue for Apache Kafka API.
-   * *   **kafkaInstanceId**: the ID of the Message Queue for Apache Kafka instance.
-   * *   **kafkaConfigs**: One or more logging configurations of Message Queue for Apache Kafka. For information about sample values and parameters, see the request parameter **KafkaLogfileConfig** in this topic.
+   * - **kafkaConfigs**: The configuration for one or more log entries. For examples and details, see the \\*\\*kafkaConfigs\\*\\* request parameter in this topic.
    * 
    * @example
-   * {"kafkaEndpoint":"10.0.X.XXX:XXXX,10.0.X.XXX:XXXX,10.0.X.XXX:XXXX\\","kafkaInstanceId":"alikafka_pre-cn-7pp2l8kr****","kafkaConfigs":[{"logType":"file_log","logDir":"/tmp/a.log","kafkaTopic":"test2"},{"logType":"stdout","logDir":"","kafkaTopic":"test"}]}
+   * {"kafkaEndpoint":"10.0.X.XXX:XXXX,10.0.X.XXX:XXXX,10.0.X.XXX:XXXX","kafkaInstanceId":"alikafka_pre-cn-7pp2l8kr****","kafkaConfigs":[{"logType":"file_log","logDir":"/tmp/a.log","kafkaTopic":"test2"},{"logType":"stdout","logDir":"","kafkaTopic":"test"}]}
    */
   kafkaConfigs?: string;
   labels?: { [key: string]: string };
   /**
    * @remarks
-   * The details of the availability check that was performed on the container. If the container fails this health check multiple times, the system disables and restarts the container. You can use one of the following methods to perform the health check:
+   * Health checks for your container. Containers that fail health checks are terminated and restarted. Supported methods:
+   * 
+   * - **exec**: For example, `{"exec":{"command":["sh","-c","cat/home/admin/start.sh"]},"initialDelaySeconds":30,"periodSeconds":30,"timeoutSeconds":2}`
+   * 
+   * - **httpGet**: For example, `{"httpGet":{"path":"/","port":18091,"scheme":"HTTP","isContainKeyWord":true,"keyWord":"SAE"},"initialDelaySeconds":11,"periodSeconds":10,"timeoutSeconds":1}`
    * 
-   * *   Example of **exec**: `{"exec":{"command":["sh","-c","cat/home/admin/start.sh"]},"initialDelaySeconds":30,"periodSeconds":30,"timeoutSeconds":2}`
-   * *   Sample code of the **httpGet** method: `{"httpGet":{"path":"/","port":18091,"scheme":"HTTP","isContainKeyWord":true,"keyWord":"SAE"},"initialDelaySeconds":11,"periodSeconds":10,"timeoutSeconds":1}`
-   * *   Sample code of the **tcpSocket** method: `{"tcpSocket":{"port":18091},"initialDelaySeconds":11,"periodSeconds":10,"timeoutSeconds":1}`
+   * - **tcpSocket**: For example, `{"tcpSocket":{"port":18091},"initialDelaySeconds":11,"periodSeconds":10,"timeoutSeconds":1}`
    * 
-   * > You can use only one method to perform the health check.
+   * > You can select only one health check method.
    * 
-   * The following table describes the parameters that are used in the preceding statements.
+   * Parameters:
    * 
-   * *   **exec.command**: the health check command.
-   * *   **httpGet.path**: the request path.
-   * *   **httpGet.scheme**: the protocol that is used to perform the health check. Valid values: **HTTP** and **HTTPS**.
-   * *   **httpGet.isContainKeyWord**: indicates whether the response contains keywords. Valid values: **true** and **false**. If this field is not returned, the advanced settings are not used.
-   * *   **httpGet.keyWord**: the custom keyword. This parameter is available only if the **isContainKeyWord** field is returned.
-   * *   **tcpSocket.port**: the port that is used to check the status of TCP connections.
-   * *   **initialDelaySeconds**: the delay of the health check. Default value: 10. Unit: seconds.
-   * *   **periodSeconds**: the interval at which health checks are performed. Default value: 30. Unit: seconds.
-   * *   **timeoutSeconds**: the timeout period of the health check. Default value: 1. Unit: seconds. If you set this parameter to 0 or leave this parameter empty, the timeout period is automatically set to 1 second.
+   * - **exec.command**: The health check command.
+   * 
+   * - **httpGet.path**: The path to access.
+   * 
+   * - **httpGet.scheme**: **HTTP** or **HTTPS**.
+   * 
+   * - **httpGet.isContainKeyWord**: **true** means the response contains a keyword. **false** means it does not. If omitted, advanced features are disabled.
+   * 
+   * - **httpGet.keyWord**: Your custom keyword. Include **isContainKeyWord** when using this field.
+   * 
+   * - **tcpSocket.port**: The port for TCP connection checks.
+   * 
+   * - **initialDelaySeconds**: The delay before the first health check, in seconds. Default is 10.
+   * 
+   * - **periodSeconds**: The interval between health checks, in seconds. Default is 30.
+   * 
+   * - **timeoutSeconds**: The timeout for each health check, in seconds. Default is 1. If set to 0 or omitted, the default is 1 second.
    * 
    * @example
    * {"exec":{"command":["sleep","5s"]},"initialDelaySeconds":10,"timeoutSeconds":11}
    */
   liveness?: string;
   lokiConfigs?: string;
+  /**
+   * @remarks
+   * The maximum number of surge instances as a percentage of total instances. Values:
+   * 
+   * If the minimum available instances is 100%, the maximum surge cannot be set to 0. If set to -1, the system uses its recommended value: 30% of your current instance count. For example, with 10 instances, 10 × 30% = 3.
+   * 
+   * @example
+   * -1
+   */
   maxSurgeInstanceRatio?: number;
+  /**
+   * @remarks
+   * The maximum number of surge instances during a rolling update. Values:
+   * 
+   * If the minimum available instances is 100%, the maximum surge cannot be set to 0. If set to -1, the system uses its recommended value: 30% of your current instance count. For example, with 10 instances, 10 × 30% = 3.
+   * 
+   * @example
+   * -1
+   */
   maxSurgeInstances?: number;
   /**
    * @remarks
-   * The memory size that is required by each instance. Unit: MB. This parameter cannot be set to 0. The values of this parameter correspond to the values of the Cpu parameter:
+   * The memory required per instance, in MB. Cannot be zero. Memory and CPU are paired. Supported fixed specifications:
+   * 
+   * - **1024**: Pairs with 500 and 1000 milliCPU.
+   * 
+   * - **2048**: Pairs with 500, 1000, and 2000 milliCPU.
+   * 
+   * - **4096**: Pairs with 1000, 2000, and 4000 milliCPU.
+   * 
+   * - **8192**: Pairs with 2000, 4000, and 8000 milliCPU.
+   * 
+   * - **12288**: Pairs with 12000 milliCPU.
+   * 
+   * - **16384**: Pairs with 4000, 8000, and 16000 milliCPU.
+   * 
+   * - **24576**: Pairs with 12000 milliCPU.
+   * 
+   * - **32768**: Pairs with 16000 milliCPU.
+   * 
+   * - **65536**: Pairs with 8000, 16000, and 32000 milliCPU.
    * 
-   * *   This parameter is set to **1024** if the Cpu parameter is set to 500 or 1000.
-   * *   This parameter is set to **2048** if the Cpu parameter is set to 500, 1000, or 2000.
-   * *   This parameter is set to **4096** if the Cpu parameter is set to 1000, 2000, or 4000.
-   * *   This parameter is set to **8192** if the Cpu parameter is set to 2000, 4000, or 8,000.
-   * *   This parameter is set to **12288** if the Cpu parameter is set to 12000.
-   * *   This parameter is set to **16384** if the Cpu parameter is set to 4000, 8000, or 16000.
-   * *   This parameter is set to **24576** if the Cpu parameter is set to 12000.
-   * *   This parameter is set to **32768** if the Cpu parameter is set to 16000.
-   * *   This parameter is set to **65536** if the Cpu parameter is set to 8000, 16000, or 32000.
-   * *   This parameter is set to **131072** if the Cpu parameter is set to 32000.
+   * - **131072**: Pairs with 32000 milliCPU.
    * 
    * @example
    * 1024
@@ -394,11 +517,15 @@ export class DeployApplicationRequest extends $dara.Model {
   memory?: number;
   /**
    * @remarks
-   * The Nacos registry. Valid values:
+   * Select a Nacos registry center. Values:
    * 
-   * *   **0**: SAE built-in Nacos registry
-   * *   **1**: self-managed Nacos registry
-   * *   **2** : MSE Nacos registry
+   * - **0**: Built-in Nacos in SAE.
+   * 
+   * - **1**: Self-managed Nacos.
+   * 
+   * - **2**: MSE Nacos Commercial Edition.
+   * 
+   * > If you select built-in Nacos in SAE, you cannot retrieve its configuration.
    * 
    * @example
    * "0"
@@ -406,13 +533,7 @@ export class DeployApplicationRequest extends $dara.Model {
   microRegistration?: string;
   /**
    * @remarks
-   * Select the edition of Nacos.
-   * 
-   * - 0: SAE built-in Nacos. Unable to get the configuration of SAE built-in Nacos.
-   * 
-   * - 1: Self-built Nacos from users.
-   * 
-   * - 2: MSE enterprise Nacos.
+   * The registry configuration. Applies only when the registry type is MSE Nacos Enterprise Edition.
    * 
    * @example
    * {\\"instanceId\\":\\"mse-cn-zvp2bh6h70r\\",\\"namespace\\":\\"4c0aa74f-57cb-423c-b6af-5d9f2d0e3dbd\\"}
@@ -420,29 +541,23 @@ export class DeployApplicationRequest extends $dara.Model {
   microRegistrationConfig?: string;
   /**
    * @remarks
-   * Configure Microservices Governance
-   * 
-   * Whether to enable microservices governance (enable):
-   * - true: Enable
-   * - false: Disable
-   * 
-   * Configure lossless online/offline deployment (mseLosslessRule):
+   * Configure microservice governance features.
    * 
-   * delayTime: Delay duration (unit: seconds)
+   * - Enable microservice governance (enable):
    * 
-   * enable: Whether to enable lossless deployment
+   *   - true: Enable
    * 
-   * - true: Enable
+   *   - false: Disable
    * 
-   * - false: Disable
+   * - Configure graceful start and shutdown (mseLosslessRule):
    * 
-   * notice: Whether to enable notifications
+   *   - delayTime: Delay time
    * 
-   * - true: Enable
+   *   - enable: Whether to enable graceful start. true enables it. false disables it.
    * 
-   * - false: Disable
+   *   - notice: Whether to enable notifications. true enables them. false disables them.
    * 
-   * warmupTime: Small-traffic warm-up duration (unit: seconds)
+   *   - warmupTime: Warm-up duration for small traffic, in seconds.
    * 
    * @example
    * {"enable": true,"mseLosslessRule": {"delayTime": 0,"enable": false,"notice": false,"warmupTime": 120}}
@@ -450,12 +565,13 @@ export class DeployApplicationRequest extends $dara.Model {
   microserviceEngineConfig?: string;
   /**
    * @remarks
-   * The percentage of the minimum number of available instances. Take note of the following rules:
+   * The minimum number of available instances as a percentage of total instances. Values:
    * 
-   * *   If you set the value to **-1**, the minimum number of available instances is not determined based on this parameter. Default value: -1.
-   * *   If you set the value to a number **from 0 to 100**, the minimum number of available instances is calculated by using the following formula: Current number of instances × (Value of MinReadyInstanceRatio × 100%). The value is the nearest integer rounded up from the calculated result. For example, if the percentage is set to **50**% and five instances are available, the minimum number of available instances is 3.
+   * - **-1**: Use the default value. No percentage is applied.
    * 
-   * > When both **MinReadyInstance** and **MinReadyInstanceRatio** are specified and **MinReadyInstanceRatio** is set to a number from 0 to 100, the value of **MinReadyInstanceRatio**** takes precedence. For example, if **MinReadyInstances** is set to **5, and **MinReadyInstanceRatio** is set to **50**, the minimum number of available instances is set to the nearest integer rounded up from the calculated result of the following formula: Current number of instances × **50%**.
+   * - **0–100**: Percentage value. Rounded up. For example, if set to **50**% and you have 5 instances, the minimum is 3.
+   * 
+   * > If both **MinReadyInstances** and **MinReadyInstanceRatio** are provided, and **MinReadyInstanceRatio** is not **-1**, then **MinReadyInstanceRatio** takes precedence. For example, if **MinReadyInstances** is **5** and **MinReadyInstanceRatio** is **50**, the system calculates the minimum based on 50%.
    * 
    * @example
    * -1
@@ -463,12 +579,13 @@ export class DeployApplicationRequest extends $dara.Model {
   minReadyInstanceRatio?: number;
   /**
    * @remarks
-   * The minimum number of available instances. Special values:
+   * The minimum number of instances that remain available during a rolling update. Values:
+   * 
+   * - If set to **0**, your application experiences downtime during updates.
    * 
-   * *   If you set the value to **0**, business interruptions occur when the application is updated.
-   * *   If you set the value to \\*\\*-1\\*\\*, the minimum number of available instances is automatically set to a system-recommended value. The value is the nearest integer to which the calculated result of the following formula is rounded up: Current number of instances × 25%. For example, if five instances are available, the minimum number of available instances is calculated by using the following formula: 5 × 25% = 1.25. In this case, the minimum number of available instances is 2.
+   * - If set to -1, the system uses its recommended value: 25% of your current instance count. For example, with 5 instances, 5 × 25% = 1.25, rounded up to 2.
    * 
-   * > Make sure that at least one instance is available during application deployment and rollback to prevent business interruptions.
+   * > We recommend setting this value to at least 1 to avoid service interruptions.
    * 
    * @example
    * 1
@@ -476,7 +593,7 @@ export class DeployApplicationRequest extends $dara.Model {
   minReadyInstances?: number;
   /**
    * @remarks
-   * The configurations for mounting the NAS file system. After the application is created, you may want to call other operations to manage the application. If you do not want to change the NAS configurations in these subsequent operations, you can omit the **MountDesc** parameter in the requests. If you want to unmount the NAS file system, you must set the **MountDesc** values in the subsequent requests to an empty string ("").
+   * We recommend using **NasConfigs** instead of this field. The NAS mount description. If your NAS configuration remains unchanged, omit this parameter. To clear your NAS configuration, set this field to an empty string.
    * 
    * @example
    * [{mountPath: "/tmp", nasPath: "/"}]
@@ -484,7 +601,7 @@ export class DeployApplicationRequest extends $dara.Model {
   mountDesc?: string;
   /**
    * @remarks
-   * The mount target of the NAS file system in the VPC where the application is deployed. If you do not need to modify this configuration during the deployment, configure the **MountHost** parameter only in the first request. You do not need to include this parameter in subsequent requests. If you need to remove this configuration, leave the **MountHost** parameter empty in the request.
+   * We recommend using **NasConfigs** instead of this field. The mount target of the NAS in your application\\"s VPC. If your NAS configuration remains unchanged, omit this parameter. To clear your NAS configuration, set this field to an empty string.
    * 
    * @example
    * 10d3b4bc9****.com
@@ -492,13 +609,17 @@ export class DeployApplicationRequest extends $dara.Model {
   mountHost?: string;
   /**
    * @remarks
-   * The configurations of mounting the NAS file system. Take note of the following rules:
+   * The configuration for mounting NAS. Values:
    * 
-   * *   **mountPath**: the mount path of the container.
-   * *   **readOnly**: If you set the value to **false**, the application has the read and write permissions.
-   * *   **nasId**: the ID of the NAS file system.
-   * *   **mountDomain**: the domain name of the mount target. For more information, see [DescribeMountTargets](https://help.aliyun.com/document_detail/62626.html).
-   * *   **nasPath**: the directory in the NAS file system.
+   * - **mountPath**: The mount path in the container.
+   * 
+   * - **readOnly**: Set to **false** for read and write permissions.
+   * 
+   * - **nasId**: The NAS ID.
+   * 
+   * - **mountDomain**: The mount target address. For more information, see [DescribeMountTargets](https://help.aliyun.com/document_detail/62626.html).
+   * 
+   * - **nasPath**: The relative directory in NAS.
    * 
    * @example
    * [{"mountPath":"/test1","readOnly":false,"nasId":"nasId1","mountDomain":"nasId1.cn-shenzhen.nas.aliyuncs.com","nasPath":"/test1"},{"nasId":"nasId2","mountDomain":"nasId2.cn-shenzhen.nas.aliyuncs.com","readOnly":false,"nasPath":"/test2","mountPath":"/test2"}]
@@ -506,7 +627,7 @@ export class DeployApplicationRequest extends $dara.Model {
   nasConfigs?: string;
   /**
    * @remarks
-   * The ID of the File Storage NAS file system. After the application is created, you may want to call other operations to manage the application. If you do not want to change the NAS configurations in these subsequent operations, you can omit the **NasId** parameter in the requests. If you want to unmount the NAS file system, you must set the **NasId** values in the subsequent requests to an empty string ("").
+   * We recommend using **NasConfigs** instead of this field. The ID of the NAS file system. If your NAS configuration remains unchanged, omit this parameter. To clear your NAS configuration, set this field to an empty string.
    * 
    * @example
    * 10d3b4****
@@ -514,13 +635,13 @@ export class DeployApplicationRequest extends $dara.Model {
   nasId?: string;
   /**
    * @remarks
-   * SAE edition.
+   * The application version:
    * 
-   * - lite: the lightweight edition.
+   * - lite: Lite Edition
    * 
-   * - std: the standard edition.
+   * - std: Standard Edition
    * 
-   * - pro: the professional edition.
+   * - pro: Professional Edition
    * 
    * @example
    * pro
@@ -528,9 +649,9 @@ export class DeployApplicationRequest extends $dara.Model {
   newSaeVersion?: string;
   /**
    * @remarks
-   * The name of the RAM role used to authenticate the user identity.
+   * The RAM role for identity authentication.
    * 
-   * >  You need to create an OpenID Connect (OIDC) identity provider (IdP) and an identity provider (IdP) for role-based single sign-on (SSO) in advance. For more information, see [Creates an OpenID Connect (OIDC) identity provider (IdP)](https://help.aliyun.com/document_detail/2331022.html) and [Creates an identity provider (IdP) for role-based single sign-on (SSO)](https://help.aliyun.com/document_detail/2331016.html).
+   * > Create an OIDC identity provider and an associated role in the same region before using this parameter. For more information, see [Create an OIDC identity provider](https://help.aliyun.com/document_detail/2331022.html) and [Create a role for SSO identity providers](https://help.aliyun.com/document_detail/2331016.html).
    * 
    * @example
    * sae-test
@@ -538,7 +659,7 @@ export class DeployApplicationRequest extends $dara.Model {
   oidcRoleName?: string;
   /**
    * @remarks
-   * The AccessKey ID that is used to read data from and write data to Object Storage Service (OSS) buckets.
+   * The AccessKey ID for OSS read and write operations.
    * 
    * @example
    * xxxxxx
@@ -546,7 +667,7 @@ export class DeployApplicationRequest extends $dara.Model {
   ossAkId?: string;
   /**
    * @remarks
-   * The AccessKey secret that is used to read data from and write data to OSS buckets.
+   * The AccessKey secret for OSS read and write operations.
    * 
    * @example
    * xxxxxx
@@ -554,18 +675,19 @@ export class DeployApplicationRequest extends $dara.Model {
   ossAkSecret?: string;
   /**
    * @remarks
-   * Information of the Object Storage Service (OSS) bucket mounted to the application. The following table describes the parameters that are used in the preceding statements.
+   * The OSS mount description. Parameters:
+   * 
+   * - **bucketName**: The name of the bucket.
    * 
-   * *   **bucketName**: the name of the OSS bucket.
+   * - **bucketPath**: The directory or object in OSS. If the directory does not exist, an error occurs.
    * 
-   * *   **bucketPath**: the directory or object in OSS. If the specified directory or object does not exist, an error is returned.
+   * - **mountPath**: The path in your SAE container. If the path exists, it is overwritten. If it does not exist, it is created.
    * 
-   * *   **mountPath**: the directory of the container in SAE. If the path already exists, the newly specified path overwrites the previous one. If the path does not exist, it is created.
+   * - **readOnly**: Whether the container path has read-only access to the mounted resource. Values:
    * 
-   * *   **readOnly**: specifies whether to only allow the container path to read data from the OSS directory. Valid values:
+   *   - **true**: Read-only.
    * 
-   *     *   **true**: The container path only has read permission on the OSS directory.
-   *     *   **false**: The application has read and write permissions.
+   *   - **false**: Read and write.
    * 
    * @example
    * [{"bucketName": "oss-bucket", "bucketPath": "data/user.data", "mountPath": "/usr/data/user.data", "readOnly": true}]
@@ -573,26 +695,43 @@ export class DeployApplicationRequest extends $dara.Model {
   ossMountDescs?: string;
   /**
    * @remarks
-   * The package type.
-   * 
-   * When using Java, FatJar, War and Image are supported.
-   * When using Python, PythonZip and Image are supported.
-   * When using PHP, the followings are supported:
-   * - PhpZip
-   * - IMAGE_PHP_5_4
-   * - IMAGE_PHP_5_4_ALPINE
-   * - IMAGE_PHP_5_5
-   * - IMAGE_PHP_5_5_ALPINE
-   * - IMAGE_PHP_5_6
-   * - IMAGE_PHP_5_6_ALPINE
-   * - IMAGE_PHP_7_0
-   * - IMAGE_PHP_7_0_ALPINE
-   * - IMAGE_PHP_7_1
-   * - IMAGE_PHP_7_1_ALPINE
-   * - IMAGE_PHP_7_2
-   * - IMAGE_PHP_7_2_ALPINE
-   * - IMAGE_PHP_7_3
-   * - IMAGE_PHP_7_3_ALPINE
+   * The type of your application package. Values:
+   * 
+   * - For Java applications: **FatJar**, **War**, and **Image**.
+   * 
+   * - For PHP applications:
+   * 
+   *   - **PhpZip**
+   * 
+   *   - **IMAGE_PHP_5_4**
+   * 
+   *   - **IMAGE_PHP_5_4_ALPINE**
+   * 
+   *   - **IMAGE_PHP_5_5**
+   * 
+   *   - **IMAGE_PHP_5_5_ALPINE**
+   * 
+   *   - **IMAGE_PHP_5_6**
+   * 
+   *   - **IMAGE_PHP_5_6_ALPINE**
+   * 
+   *   - **IMAGE_PHP_7_0**
+   * 
+   *   - **IMAGE_PHP_7_0_ALPINE**
+   * 
+   *   - **IMAGE_PHP_7_1**
+   * 
+   *   - **IMAGE_PHP_7_1_ALPINE**
+   * 
+   *   - **IMAGE_PHP_7_2**
+   * 
+   *   - **IMAGE_PHP_7_2_ALPINE**
+   * 
+   *   - **IMAGE_PHP_7_3**
+   * 
+   *   - **IMAGE_PHP_7_3_ALPINE**
+   * 
+   * - For Python applications: **PythonZip** and **Image**.
    * 
    * @example
    * FatJar
@@ -600,7 +739,7 @@ export class DeployApplicationRequest extends $dara.Model {
   packageType?: string;
   /**
    * @remarks
-   * The address of the deployment package. This parameter is required when the **PackageType** parameter is set to **FatJar**, **War**, or **PythonZip**.
+   * The URL of your deployment package. Required when **Package Type** is **FatJar**, **War**, or **PythonZip**.
    * 
    * @example
    * http://myoss.oss-cn-hangzhou.aliyuncs.com/my-buc/2019-06-30/****.jar
@@ -608,7 +747,7 @@ export class DeployApplicationRequest extends $dara.Model {
   packageUrl?: string;
   /**
    * @remarks
-   * The version of the deployment package. This parameter is required when the **PackageType** parameter is set to **FatJar**, **War**, or **PythonZip**.
+   * The version number of your deployment package. Required when **Package Type** is **FatJar**, **War**, or **PythonZip**.
    * 
    * @example
    * 1.0.1
@@ -616,7 +755,7 @@ export class DeployApplicationRequest extends $dara.Model {
   packageVersion?: string;
   /**
    * @remarks
-   * The dependent PHP version of PHP package. Image is not supported.
+   * The PHP version that your PHP deployment package depends on. Not supported for images.
    * 
    * @example
    * PHP-FPM 7.0
@@ -624,7 +763,7 @@ export class DeployApplicationRequest extends $dara.Model {
   php?: string;
   /**
    * @remarks
-   * The path on which the PHP configuration file for application monitoring is mounted. Make sure that the PHP server loads the configuration file. SAE automatically generates the corresponding configuration file. No manual operations are required.
+   * The mount path for PHP application monitoring. Ensure your PHP server loads the configuration file at this path. You do not need to manage the configuration content. SAE renders the correct configuration automatically.
    * 
    * @example
    * /usr/local/etc/php/conf.d/arms.ini
@@ -632,7 +771,7 @@ export class DeployApplicationRequest extends $dara.Model {
   phpArmsConfigLocation?: string;
   /**
    * @remarks
-   * The details of the PHP configuration file.
+   * The content of the PHP configuration file.
    * 
    * @example
    * k1=v1
@@ -640,7 +779,7 @@ export class DeployApplicationRequest extends $dara.Model {
   phpConfig?: string;
   /**
    * @remarks
-   * The path on which the PHP configuration file for application startup is mounted. Make sure that the PHP server uses this configuration file during the startup.
+   * The mount path for the PHP startup configuration. Ensure your PHP server uses this configuration file to start.
    * 
    * @example
    * /usr/local/etc/php/php.ini
@@ -648,7 +787,7 @@ export class DeployApplicationRequest extends $dara.Model {
   phpConfigLocation?: string;
   /**
    * @remarks
-   * The script that is run immediately after the container is started. Example: `{"exec":{"command":["sh","-c","echo hello"\\]}}`
+   * A script that runs after your container starts. It executes immediately after the container is created. Format: `{"exec":{"command":["sh","-c","echo hello"]}}`
    * 
    * @example
    * {"exec":{"command":["sh","-c","echo hello"]}}
@@ -656,7 +795,7 @@ export class DeployApplicationRequest extends $dara.Model {
   postStart?: string;
   /**
    * @remarks
-   * The script that is run before the container is stopped. Example: `{"exec":{"command":["sh","-c","echo hello"\\]}}`
+   * A script that runs before your container stops. It executes just before the container is deleted. Format: `{"exec":{"command":["sh","-c","echo hello"]}}`
    * 
    * @example
    * {"exec":{"command":["sh","-c","echo hello"]}}
@@ -664,20 +803,21 @@ export class DeployApplicationRequest extends $dara.Model {
   preStop?: string;
   /**
    * @remarks
-   * The configurations of Kubernetes Service-based service registration and discovery. Take note of the following rules:
+   * Enable K8s Service registration and discovery. Values:
+   * 
+   * - **portProtocols**: Port and protocol. Port range is [1,65535]. Protocols supported: **TCP** and **UDP**.
+   * 
+   * - portAndProtocol: Port and protocol. Port range is [1,65535]. Protocols supported: **TCP** and **UDP**. **portProtocols** takes precedence. If both are set, only **portProtocols** applies.
    * 
-   * *   **serviceName**: the name of the Alibaba Cloud service. Format: `<Custom content>-<Namespace ID>`. `-<Namespace ID>` is automatically specified based on the namespace in which an application resides and cannot be changed. For example, if you select the default namespace in the China (Beijing) region, `-cn-beijing-default` is automatically specified.
-   * *   **namespaceId**: the namespace ID.
-   * *   **portAndProtocol**: the port number and protocol. Valid values of the port number: 1 to 65535. Valid values of the protocol: **TCP** and **UDP**.
-   * *   **enable**: enables the Kubernetes Service-based registration and discovery feature.
+   * - **enable**: Enable K8s Service registration and discovery.
    * 
    * @example
-   * {"serviceName":"bwm-poc-sc-gateway-cn-beijing-front","namespaceId":"cn-beijing:front","portAndProtocol":{"18012":"TCP"},"enable":true}
+   * {"portProtocols":[{"port":18012,"protocol":"TCP"}],"portAndProtocol":{"18012":"TCP"},"enable":true}
    */
   pvtzDiscoverySvc?: string;
   /**
    * @remarks
-   * The Python environment. Set the value to **PYTHON 3.9.15**.
+   * The Python runtime environment. Supported: **PYTHON 3.9.15**.
    * 
    * @example
    * PYTHON 3.9.15
@@ -685,7 +825,7 @@ export class DeployApplicationRequest extends $dara.Model {
   python?: string;
   /**
    * @remarks
-   * The configurations for installing custom module dependencies. By default, the dependencies defined by the requirements.txt file in the root directory are installed. If the package does not contain this file and you do not configure custom dependencies in the package, specify the dependencies that you want to install in the text box.
+   * Custom module dependencies. By default, dependencies defined in requirements.txt in the root directory are installed. If no configuration or custom packages exist, specify the dependencies to install.
    * 
    * @example
    * Flask==2.0
@@ -693,9 +833,9 @@ export class DeployApplicationRequest extends $dara.Model {
   pythonModules?: string;
   /**
    * @remarks
-   * The details of the health check that was performed on the container. If the container fails this health check multiple times, the system disables and restarts the container. Containers that fail health checks cannot receive traffic from Server Load Balancer (SLB) instances. You can use the **exec**, **httpGet**, or **tcpSocket** method to perform health checks. For more information, see the description of the **Liveness** parameter.
+   * Startup status checks for your application. Containers that repeatedly fail readiness checks are terminated and restarted. Containers that fail readiness checks receive no SLB traffic. Supports **exec**, **httpGet**, and **tcpSocket**. For examples, see the **Liveness** parameter.
    * 
-   * > You can use only one method to perform the health check.
+   * > You can select only one health check method.
    * 
    * @example
    * {"exec":{"command":["sleep","6s"]},"initialDelaySeconds":15,"timeoutSeconds":12}
@@ -711,14 +851,15 @@ export class DeployApplicationRequest extends $dara.Model {
   replicas?: number;
   /**
    * @remarks
-   * Secret Mount Description
-   * Use the secret dictionaries created in the Namespace Secret Dictionary page to inject information into containers. Parameter descriptions are as follows:
+   * The mount description for a **Secret**. Use secrets created on the namespace secrets page to inject sensitive information into your container. Parameters:
    * 
-   * - secretId: Secret instance ID. Obtain via the ListSecrets interface.
+   * - **secretId**: The ID of the secret instance. Get it by calling the ListSecrets API.
    * 
-   * - key: Key-value pair. Note: Set the parameter sae-sys-secret-all to mount all keys.
+   * - **key**: The key.
    * 
-   * - mountPath: Mount path.
+   * > You can mount all keys by passing `sae-sys-secret-all`.
+   * 
+   * - **mountPath**: The mount path.
    * 
    * @example
    * [{“secretId":10,”key":"test","mountPath":"/tmp"}]
@@ -726,7 +867,7 @@ export class DeployApplicationRequest extends $dara.Model {
   secretMountDesc?: string;
   /**
    * @remarks
-   * Security group ID.
+   * The security group ID.
    * 
    * @example
    * sg-wz969ngg2e49q5i4****
@@ -734,7 +875,7 @@ export class DeployApplicationRequest extends $dara.Model {
   securityGroupId?: string;
   /**
    * @remarks
-   * The gray-release tag of the application.
+   * The canary tags configured for your application.
    * 
    * @example
    * {\\"alicloud.service.tag\\":\\"g1\\"}
@@ -742,41 +883,55 @@ export class DeployApplicationRequest extends $dara.Model {
   serviceTags?: string;
   /**
    * @remarks
-   * The configuration of the container.
+   * Container configuration information.
    */
   sidecarContainersConfig?: SidecarContainerConfig[];
   /**
    * @remarks
-   * The logging configurations of Log Service.
+   * The configuration for collecting logs to Simple Log Service (SLS).
+   * 
+   * - Using SAE-managed SLS resources: `[{"logDir":"","logType":"stdout"},{"logDir":"/tmp/a.log"}]`.
+   * 
+   * - Using custom SLS resources: `[{"projectName":"test-sls","logType":"stdout","logDir":"","logstoreName":"sae","logtailName":""},{"projectName":"test","logDir":"/tmp/a.log","logstoreName":"sae","logtailName":""}]`.
+   * 
+   * Parameters:
+   * 
+   * - **projectName**: The name of the SLS project.
    * 
-   * *   To use Log Service resources that are automatically created by SAE, set this parameter to `[{"logDir":"","logType":"stdout"},{"logDir":"/tmp/a.log"}]`.
-   * *   To use custom Log Service resources, set this parameter to `[{"projectName":"test-sls","logType":"stdout","logDir":"","logstoreName":"sae","logtailName":""},{"projectName":"test","logDir":"/tmp/a.log","logstoreName":"sae","logtailName":""}]`.
+   * - **logDir**: The log file path.
    * 
-   * The following table describes the parameters that are used in the preceding statements.
+   * - logType: The log type. **stdout** means standard output logs from the container. Only one **stdout** entry is allowed. If omitted, file logs are collected.
    * 
-   * *   **projectName**: the name of the Log Service project.
-   * *   **logDir**: the path in which logs are stored.
-   * *   **logType**: the log type. **stdout**: the standard output log of the container. You can specify only one stdout value for this parameter. If you leave this parameter empty, file logs are collected.
-   * *   **logstoreName**: the name of the Logstore in Log Service.
-   * *   **logtailName**: the name of the Logtail configuration in Log Service. If you do not configure this parameter, a new Logtail configuration is created.
+   * - **logstoreName**: The name of the SLS Logstore.
    * 
-   * If you do not need to modify the logging configurations when you deploy the application, configure the **SlsConfigs** parameter only in the first request. You do not need to include this parameter in subsequent requests. If you no longer need to use Log Service, leave the **SlsConfigs** parameter empty in the request.
+   * - **logtailName**: The name of the SLS Logtail. If omitted, a new Logtail is created.
    * 
-   * > A Log Service project that is automatically created by SAE when you create an application is deleted when the application is deleted. Therefore, when you create an application, you cannot select a Log Service project that is automatically created by SAE for log collection.
+   * If your SLS collection configuration remains unchanged across deployments, omit this parameter. To disable SLS collection, set this field to an empty string.
+   * 
+   * > Projects automatically created by SAE are deleted when the application is deleted. Do not select these projects when choosing an existing project.
    * 
    * @example
    * [{"logDir":"","logType":"stdout"},{"logDir":"/tmp/a.log"}]
    */
   slsConfigs?: string;
+  /**
+   * @remarks
+   * The SLS log tags.
+   */
   slsLogEnvTags?: string;
   /**
    * @remarks
-   * Check Failure: Indicates that the application failed to start. The system will report the exception and automatically restart it.
+   * Enable application startup probing.
+   * 
+   * - Success: The application starts successfully. If you configure Liveness and Readiness checks, they run after startup.
    * 
-   * Note: 
+   * - Failure: The application fails to start. SAE reports an error and restarts the container automatically.
    * 
-   * Supports exec, httpGet, and tcpSocket methods. For specific examples, see Liveness Parameters.
-   * Only one method can be selected for health checks.
+   * > Description
+   * >
+   * > - Supports exec, httpGet, and tcpSocket. For examples, see the Liveness parameter.
+   * >
+   * > - You can select only one health check method.
    * 
    * @example
    * {"exec":{"command":["sh","-c","cat /home/admin/start.sh"]},"initialDelaySeconds":30,"periodSeconds":30,"timeoutSeconds":2}
@@ -784,23 +939,31 @@ export class DeployApplicationRequest extends $dara.Model {
   startupProbe?: string;
   /**
    * @remarks
-   * Configure K8s Service-based Service Registration/Discovery and Full-Chain Grayscale Capabilities
+   * Configures service discovery and end-to-end canary release based on a Kubernetes Service:
+   * 
+   * - enable: Specifies whether to enable the end-to-end canary release feature.
+   * 
+   *   - true: Enables the feature.
+   * 
+   *   - false: Disables the feature.
+   * 
+   * - namespaceId: The namespace ID.
+   * 
+   * - portAndProtocol: The listening port and protocol. The format is {"\\<port>:\\<protocol>":"\\<target_port>"}.
    * 
-   * - enable: Whether to enable full-link grayscale based on K8s Service (set to "true" to enable; set to "false" to disable).
+   * - portProtocols: A list of ports and protocols for the service.
    * 
-   * - namespaceId: Namespace ID
+   *   - port: The port number.
    * 
-   * - portAndProtocol: Listener port and protocol. Format: {"Port:Protocol Type":"Container Port"}
-   * - portProtocols: Define service ports and protocols
-   * port: Port
-   * protocol: Protocol
-   * targetPort: Container port
+   *   - protocol: The protocol.
    * 
-   * - pvtzDiscoveryName: Service discovery name
+   *   - targetPort: The container port.
    * 
-   * - serviceId: Service ID
+   * - pvtzDiscoveryName: The service discovery name.
    * 
-   * - serviceName: Service name
+   * - serviceId: The service ID.
+   * 
+   * - serviceName: The service name.
    * 
    * @example
    * {\\"enable\\":\\"false\\",\\"namespaceId\\":\\"cn-beijing:test\\",\\"portAndProtocol\\":{\\"2000:TCP\\":\\"18081\\"},\\"portProtocols\\":[{\\"port\\":2000,\\"protocol\\":\\"TCP\\",\\"targetPort\\":18081}],\\"pvtzDiscoveryName\\":\\"cn-beijing-1421801774382676\\",\\"serviceId\\":\\"3513\\",\\"serviceName\\":\\"demo-gray.test\\"}
@@ -808,7 +971,7 @@ export class DeployApplicationRequest extends $dara.Model {
   swimlanePvtzDiscoverySvc?: string;
   /**
    * @remarks
-   * The timeout period for a graceful shutdown. Default value: 30. Unit: seconds. Valid values: 1 to 300.
+   * The graceful shutdown timeout, in seconds. Default is 30. Valid values: 1–300.
    * 
    * @example
    * 10
@@ -816,7 +979,7 @@ export class DeployApplicationRequest extends $dara.Model {
   terminationGracePeriodSeconds?: number;
   /**
    * @remarks
-   * The time zone. Default value: **Asia/Shanghai**.
+   * The time zone. Default is **Asia/Shanghai**.
    * 
    * @example
    * Asia/Shanghai
@@ -824,13 +987,17 @@ export class DeployApplicationRequest extends $dara.Model {
   timezone?: string;
   /**
    * @remarks
-   * The Tomcat configuration. If you want to cancel this configuration, set this parameter to "" or "{}". The following variables are included in the configuration: Take note of the following rules:
+   * The Tomcat configuration. Set to an empty string or {} to delete the configuration. Values:
+   * 
+   * - **port**: Port range is 1024–65535. Ports below 1024 require root privileges. Because containers run with admin privileges, use ports above 1024. Default is 8080.
+   * 
+   * - **contextPath**: The access path. Default is the root directory /.
+   * 
+   * - **maxThreads**: The size of the connection pool. Default is 400.
+   * 
+   * - uriEncoding: The encoding format for Tomcat. Options include **UTF-8**, **ISO-8859-1**, **GBK**, and **GB2312**. Default is **ISO-8859-1**.
    * 
-   * *   **port**: the port number. The port number ranges from 1024 to 65535. Though the admin permissions are configured for the container, the root permissions are required to perform operations on ports whose number is smaller than 1024. Enter a value that ranges from 1025 to 65535 because the container has only the admin permissions. If you do not specify this parameter, the default port number 8080 is used.
-   * *   **contextPath**: the path. Default value: /. This value indicates the root directory.
-   * *   **maxThreads**: the maximum number of connections in the connection pool. Default value: 400.
-   * *   **uriEncoding**: the URI encoding scheme in the Tomcat container. Valid values: UTF-8, ISO-8859-1, GBK, and GB2312.************ If you do not specify this parameter, the default value **ISO-8859-1** is used.
-   * *   **useBodyEncoding**: specifies whether to use the encoding scheme specified in the request body for URI query parameters. Default value: true.
+   * - **useBodyEncodingForUri**: Whether to use body encoding for URLs. Default is **true**.
    * 
    * @example
    * {"port":8080,"contextPath":"/","maxThreads":400,"uriEncoding":"ISO-8859-1","useBodyEncodingForUri":true}
@@ -838,23 +1005,27 @@ export class DeployApplicationRequest extends $dara.Model {
   tomcatConfig?: string;
   /**
    * @remarks
-   * The deployment policy. If the minimum number of available instances is 1, the value of the **UpdateStrategy** parameter is an empty string (""). If the minimum number of available instances is greater than 1, the following strategies can be configured:
+   * The release strategy. When MinReadyInstances equals 1, set UpdateStrategy to an empty string. When **MinReadyInstances** is greater than 1, examples include the following:
    * 
-   * *   The application is deployed on an instance. The remaining instances are automatically classified into two release batches whose interval is set to 1. In this case, the parameter is set to `{"type":"GrayBatchUpdate","batchUpdate":{"batch":2,"releaseType":"auto","batchWaitTime":1},"grayUpdate":{"gray":1}}`.
-   * *   The application is deployed on an instance. The remaining instances are manually classified into two release batches. In this case, the parameter is set to `{"type":"GrayBatchUpdate","batchUpdate":{"batch":2,"releaseType":"manual"},"grayUpdate":{"gray":1}}`.
-   * *   All instances are automatically classified into two release batches. The application is deployed on the instances of the two batches in parallel. In this case, the parameter is set to `{"type":"BatchUpdate","batchUpdate":{"batch":2,"releaseType":"auto","batchWaitTime":0}}`
+   * - Canary release with 1 instance, followed by 2 automatic batches with a 1-minute interval: `{"type":"GrayBatchUpdate","batchUpdate":{"batch":2,"releaseType":"auto","batchWaitTime":1},"grayUpdate":{"gray":1}}`
    * 
-   * The following table describes the parameters that are used in the preceding statements.
+   * - Canary release with 1 instance, followed by 2 manual batches: `{"type":"GrayBatchUpdate","batchUpdate":{"batch":2,"releaseType":"manual"},"grayUpdate":{"gray":1}}`
    * 
-   * *   **type**: the type of the release policy. Valid values: **GrayBatchUpdate** and **BatchUpdate**.
+   * - Two automatic batches with a 0-minute interval: `{"type":"BatchUpdate","batchUpdate":{"batch":2,"releaseType":"auto","batchWaitTime":0}}`
    * 
-   * *   **batchUpdate**: the phased release policy.
+   * Parameters:
    * 
-   *     *   **batch**: the number of release batches.
-   *     *   **releaseType**: the processing method for the batches. Valid values: **auto** and **manual**.
-   *     *   **batchWaitTime**: the interval between release batches. Unit: seconds.
+   * - **type**: The release strategy type. Options are **GrayBatchUpdate** (canary release) or **BatchUpdate** (phased release).
    * 
-   * *   **grayUpdate**: the number of release batches in the phased release after a canary release. This parameter is returned only if the **type** parameter is set to **GrayBatchUpdate**.
+   * - **batchUpdate**: The phased release strategy.
+   * 
+   *   - **batch**: The number of batches.
+   * 
+   *   - **releaseType**: How batches are processed. Options are **auto** (automatic) or **manual** (manual).
+   * 
+   *   - **batchWaitTime**: The wait time between batches, in minutes.
+   * 
+   * - **grayUpdate**: The number of canary instances. Required when **type** is **GrayBatchUpdate**.
    * 
    * @example
    * {"type":"GrayBatchUpdate","batchUpdate":{"batch":2,"releaseType":"auto","batchWaitTime":1},"grayUpdate":{"gray":1}}
@@ -862,7 +1033,7 @@ export class DeployApplicationRequest extends $dara.Model {
   updateStrategy?: string;
   /**
    * @remarks
-   * The ID of the vSwitch, where the EIP of the application instances resides. The vSwitch must reside in the VPC above.
+   * The virtual switch where your application instance elastic network interfaces reside. This switch must be in the specified VPC.
    * 
    * @example
    * vsw-bp12mw1f8k3jgygk9****
@@ -870,7 +1041,7 @@ export class DeployApplicationRequest extends $dara.Model {
   vSwitchId?: string;
   /**
    * @remarks
-   * The startup command of the WAR package. For information about how to configure the startup command, see [Configure startup commands](https://help.aliyun.com/document_detail/96677.html).
+   * The startup command for your WAR package. Configure it the same way as the startup command for images. For more information, see [Set the startup command](https://help.aliyun.com/document_detail/96677.html).
    * 
    * @example
    * CATALINA_OPTS=\\"$CATALINA_OPTS $Options\\" catalina.sh run
@@ -878,12 +1049,13 @@ export class DeployApplicationRequest extends $dara.Model {
   warStartOptions?: string;
   /**
    * @remarks
-   * The version of the Tomcat container on which the deployment package depends. Valid values:
+   * The Tomcat version that your deployment package depends on. Supported versions include the following:
+   * 
+   * - **apache-tomcat-7.0.91**
    * 
-   * *   **apache-tomcat-7.0.91**
-   * *   **apache-tomcat-8.5.42**
+   * - **apache-tomcat-8.5.42**
    * 
-   * This parameter is not returned if the **PackageType** parameter is set to **Image**.
+   * This parameter is not supported when **Package Type** is **Image**.
    * 
    * @example
    * apache-tomcat-7.0.91