@alicloud/sae20190506 2.12.2 → 2.12.4

package/src/models/DeployApplicationRequest.ts

@@ -4,10 +4,39 @@ import { InitContainerConfig } from "./InitContainerConfig";
 import { SidecarContainerConfig } from "./SidecarContainerConfig";
 
 
+export class DeployApplicationRequestRaspConfig extends $dara.Model {
+  enableRasp?: boolean;
+  raspAppKey?: string;
+  raspAppName?: string;
+  static names(): { [key: string]: string } {
+    return {
+      enableRasp: 'EnableRasp',
+      raspAppKey: 'RaspAppKey',
+      raspAppName: 'RaspAppName',
+    };
+  }
+
+  static types(): { [key: string]: any } {
+    return {
+      enableRasp: 'boolean',
+      raspAppKey: 'string',
+      raspAppName: 'string',
+    };
+  }
+
+  validate() {
+    super.validate();
+  }
+
+  constructor(map?: { [key: string]: any }) {
+    super(map);
+  }
+}
+
 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 for cross-account image pulling. For more information, see [Grant permissions across Alibaba Cloud accounts by using a RAM role](https://help.aliyun.com/document_detail/223585.html).
    * 
    * @example
    * acs:ram::123456789012****:role/adminrole
@@ -15,17 +44,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 instance ID. This parameter is required when **ImageUrl** is set to a Container Registry Enterprise instance image.
    * 
    * @example
    * cri-xxxxxx
    */
   acrInstanceId?: string;
+  /**
+   * @remarks
+   * The AliyunAgent version.
+   * 
+   * @example
+   * 4.4.2
+   */
   agentVersion?: string;
+  /**
+   * @remarks
+   * The ALB gateway ReadinessGate configuration.
+   * 
+   * @example
+   * default
+   */
   albIngressReadinessGate?: string;
   /**
    * @remarks
-   * The ID of the application.
+   * The ID of the application to deploy.
    * 
    * This parameter is required.
    * 
@@ -35,10 +78,10 @@ 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:
+   * Specifies whether to associate an elastic IP address (EIP). Valid values:
    * 
-   * *   **true**: The EIP is associated with the application instance.
-   * *   **false**: The EIP is not associated with the application instance.
+   * - **true**: associates an EIP.
+   * - **false**: does not associate an EIP.
    * 
    * @example
    * true
@@ -46,10 +89,9 @@ 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:
-   * 
-   * *   **true**: turns on Logon-free Sharing
-   * *   **false**: turns off Logon-free Sharing
+   * Specifies whether to automatically enable the application elastic scaling policy. Valid values:
+   * - **true**: enabled.
+   * - **false**: disabled.
    * 
    * @example
    * true
@@ -57,7 +99,7 @@ export class DeployApplicationRequest extends $dara.Model {
   autoEnableApplicationScalingRule?: boolean;
   /**
    * @remarks
-   * The interval between batches during a batch release. Unit: minutes.
+   * The interval between deployment batches. Unit: seconds.
    * 
    * @example
    * 10
@@ -68,20 +110,21 @@ export class DeployApplicationRequest extends $dara.Model {
    * The description of the change order.
    * 
    * @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:
-   * 
-   *     command:
-   *           - echo
-   *           - abc
-   *           - >
-   *           - file0
+   * The image startup command. The command must be an executable object in the container. Example:
    * 
-   * In this example, the Command parameter is set to `Command="echo", CommandArgs=["abc", ">", "file0"]`.
+   * ```
+   * command:
+   *       - echo
+   *       - abc
+   *       - >
+   *       - file0
+   * ```
+   * Based on the preceding example, `Command="echo", CommandArgs=["abc", ">", "file0"]`.
    * 
    * @example
    * echo
@@ -89,11 +132,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 of the image startup command. These are the arguments required by the startup command specified in **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 preceding example, `CommandArgs=["abc", ">", "file0"]`, where `["abc", ">", "file0"]` must be converted to a String type, and the internal format is a JSON array. If this parameter is not required, leave it empty.
    * 
    * @example
    * ["a","b"]
@@ -101,14 +144,14 @@ 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 **ConfigMap** mount description. Use a ConfigMap created on the namespace configuration items page to inject configuration information into the container. Settings:
    * 
-   * *   **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.
+   * - **configMapId**: the ConfigMap instance ID. You can obtain it by calling the [ListNamespacedConfigMaps](https://help.aliyun.com/document_detail/176917.html) operation.
+   * - **key**: the key.
    * 
-   * > You can use `sae-sys-configmap-all` to mount all keys.
+   * > You can mount all keys by passing the `sae-sys-configmap-all` parameter.
    * 
-   * *   **mountPath**: the mount path in the container.
+   * - **mountPath**: the mount path.
    * 
    * @example
    * [{"configMapId":16,"key":"test","mountPath":"/tmp"}]
@@ -116,16 +159,15 @@ 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:
-   * 
-   * *   **500**
-   * *   **1000**
-   * *   **2000**
-   * *   **4000**
-   * *   **8000**
-   * *   **12000**
-   * *   **16000**
-   * *   **32000**
+   * The CPU resources required for each instance. Unit: millicores. This parameter cannot be set to 0. Only the following defined specifications are supported:
+   * - **500**
+   * - **1000**
+   * - **2000**
+   * - **4000**
+   * - **8000**
+   * - **12000**
+   * - **16000**
+   * - **32000**
    * 
    * @example
    * 1000
@@ -133,10 +175,10 @@ 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:
+   * The custom host mapping in the container. Valid values:
    * 
-   * *   **hostName**: the domain name or hostname.
-   * *   **ip**: the IP address.
+   * - **hostName**: the domain name or hostname.
+   * - **ip**: the IP address.
    * 
    * @example
    * [{"hostName":"samplehost","ip":"127.0.0.1"}]
@@ -144,11 +186,10 @@ export class DeployApplicationRequest extends $dara.Model {
   customHostAlias?: string;
   /**
    * @remarks
-   * Custom image type. To it to empty string to use pre-built image.
-   * 
-   * - internet: Public network image
+   * The custom image type. If the image is not a custom image, set this parameter to an empty string:
    * 
-   * - intranet: Private network image
+   * - internet: public image.
+   * - intranet: private image.
    * 
    * @example
    * internet
@@ -156,10 +197,9 @@ 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.
-   * 
-   * *   **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.
+   * This parameter takes effect only for applications in the stopped state. If you call the **DeployApplication** operation for a running application, the application is immediately redeployed.
+   * - **true**: default value. Deploys immediately, applies the new deployment configuration, and starts instances.
+   * - **false**: applies the new deployment configuration only, without starting application instances.
    * 
    * @example
    * true
@@ -167,7 +207,7 @@ export class DeployApplicationRequest extends $dara.Model {
   deploy?: string;
   /**
    * @remarks
-   * The version of .NET
+   * The version of the .NET framework: 
    * 
    * - .NET 3.1
    * - .NET 5.0
@@ -181,19 +221,26 @@ 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 in the HSF framework, such as the Ali-Tomcat container.
    * 
    * @example
    * 3.5.3
    */
   edasContainerVersion?: string;
+  /**
+   * @remarks
+   * The shared ephemeral storage configuration.
+   * 
+   * @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:
+   * Specifies whether to enable Application High Availability Service (AHAS). Valid values:
    * 
-   * *   **true**: Access to AHAS is enabled.
-   * *   **false**: Access to AHAS is disabled.
+   * - **true**: enables AHAS.
+   * - **false**: does not enable AHAS.
    * 
    * @example
    * false
@@ -201,11 +248,10 @@ export class DeployApplicationRequest extends $dara.Model {
   enableAhas?: string;
   /**
    * @remarks
-   * Enable CPU Burst.
-   * 
-   * true: enable
+   * Specifies whether to enable the CPU Burst feature:
    * 
-   * false: disable
+   * - true: enabled.
+   * - false: disabled.
    * 
    * @example
    * true
@@ -213,36 +259,48 @@ 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:
+   * Specifies whether to enable traffic canary release rules. This rule applies only to applications that use the Spring Cloud or Dubbo framework. Valid values:
    * 
-   * *   **true**: The canary release rules are enabled.
-   * *   **false**: The canary release rules are disabled.
+   * - **true**: enables canary release rules.
+   * - **false**: disables canary release rules.
    * 
    * @example
    * false
    */
   enableGreyTagRoute?: boolean;
-  enableNamespaceAgentVersion?: boolean;
   /**
    * @remarks
-   * Enable new ARMS features.
+   * Specifies whether to reuse the namespace Agent version configuration.
    * 
-   * - true: enable
+   * @example
+   * true
+   */
+  enableNamespaceAgentVersion?: boolean;
+  /**
+   * @remarks
+   * Specifies whether to enable the new ARMS feature:
    * 
-   * - false: disable
+   * - true: enabled.
+   * - false: disabled.
    * 
    * @example
    * true
    */
   enableNewArms?: boolean;
-  enablePrometheus?: boolean;
   /**
    * @remarks
-   * Enable Sidecar resource isolation.
+   * Specifies whether to enable custom Prometheus metric collection.
    * 
-   * true: enable
+   * @example
+   * false
+   */
+  enablePrometheus?: boolean;
+  /**
+   * @remarks
+   * Specifies whether to enable sidecar resource isolation:
    * 
-   * false: disable
+   * - true: enables isolation.
+   * - false: does not enable isolation.
    * 
    * @example
    * true
@@ -250,36 +308,42 @@ 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:
-   * 
-   * *   Customize
-   * 
-   *     *   **name**: the name of the environment variable.
-   *     *   **value**: the value of the environment variable.
-   * 
-   * *   Reference ConfigMap
-   * 
-   *     *   **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.
-   * 
-   * *   Reference secret dictionary
-   * 
-   *     *   **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.
+   * The container environment variable parameters. You can customize environment variables or reference ConfigMap items. To reference a ConfigMap item, create a ConfigMap instance first. For more information, see [CreateConfigMap](https://help.aliyun.com/document_detail/176914.html). Valid values:
+   * - Custom configuration
+   *     - **name**: the name of the environment variable.
+   *     - **value**: the value of the environment variable. This takes priority over valueFrom.
+   * - Reference a ConfigMap item (valueFrom)
+   *     - **name**: the name of the environment variable. To reference all keys, enter `sae-sys-configmap-all-<ConfigMap name>`, such as `sae-sys-configmap-all-test1`.
+   *     - **valueFrom**: the environment variable reference. Set the value to `configMapRef`.
+   *     - **configMapId**: the ConfigMap ID.
+   *     - **key**: the key. Do not set this field if you want to reference all keys.
+   * - Reference a secret (valueFrom)
+   *     - **name**: the name of the environment variable. To reference all keys, enter `sae-sys-secret-all-<secret name>`, such as `sae-sys-secret-all-test1`.
+   *     - **valueFrom**: the environment variable reference. Set the value to `secretRef`.
+   *     - **secretId**: the secret ID.
+   *     - **key**: the key. Do not set this field if you want to 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 corresponding secret ID.
    * 
    * @example
    * 10
@@ -287,7 +351,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 image URL. This parameter is required when **Package Type** is set to **Image**.
    * 
    * @example
    * registry.cn-hangzhou.aliyuncs.com/sae_test/ali_sae_test:0.0.1
@@ -295,12 +359,12 @@ export class DeployApplicationRequest extends $dara.Model {
   imageUrl?: string;
   /**
    * @remarks
-   * Initialize container configuration.
+   * The init 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`.
+   * The startup arguments for a JAR package-based application. The default startup command is `$JAVA_HOME/bin/java $JarStartOptions -jar $CATALINA_OPTS "$package_path" $JarStartArgs`.
    * 
    * @example
    * -Xms4G -Xmx4G
@@ -308,7 +372,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`.
+   * The startup options for a JAR package-based application. The default startup command is `$JAVA_HOME/bin/java $JarStartOptions -jar $CATALINA_OPTS "$package_path" $JarStartArgs`.
    * 
    * @example
    * custom-option
@@ -316,16 +380,16 @@ 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 on which the deployment package depends. Valid values:
    * 
-   * *   **Open JDK 8**
-   * *   **Open JDK 7**
-   * *   **Dragonwell 11**
-   * *   **Dragonwell 8**
-   * *   **openjdk-8u191-jdk-alpine3.9**
-   * *   **openjdk-7u201-jdk-alpine3.9**
+   * - **Open JDK 8**
+   * - **Open JDK 7**
+   * - **Dragonwell 11**
+   * - **Dragonwell 8**
+   * - **openjdk-8u191-jdk-alpine3.9**
+   * - **openjdk-7u201-jdk-alpine3.9**
    * 
-   * This parameter is not returned if the **PackageType** parameter is set to **Image**.
+   * This parameter is not supported when **Package Type** is set to **Image**.
    * 
    * @example
    * Open JDK 8
@@ -333,60 +397,78 @@ 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 summary of log collection configurations for Kafka. Valid values:
    * 
-   * *   **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.
+   * - **kafkaEndpoint**: the endpoint of the Kafka API.
+   * - **kafkaInstanceId**: the Kafka instance ID.
+   * - **kafkaConfigs**: the configuration summary for one or more log entries. For example values and parameter descriptions, 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:
+   * The container health check. Containers that fail the health check are shutdown and recovered. The following methods are supported:
    * 
-   * *   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}`
+   * - **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}`
+   * - **tcpSocket**: for example, `{"tcpSocket":{"port":18091},"initialDelaySeconds":11,"periodSeconds":10,"timeoutSeconds":1}`
    * 
-   * > You can use only one method to perform the health check.
+   * > Only one method can be selected for health checks.
    * 
-   * The following table describes the parameters that are used in the preceding statements.
+   * Settings:
    * 
-   * *   **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**: sets the health check command.
+   * - **httpGet.path**: the access path.
+   * - **httpGet.scheme**: **HTTP** or **HTTPS**.
+   * - **httpGet.isContainKeyWord**: **true** indicates that the keyword is included, **false** indicates that the keyword is not included, and the absence of this field indicates that the advanced feature is not used.
+   * - **httpGet.keyWord**: the custom keyword. The **isContainKeyWord** field must be present when this parameter is used.
+   * - **tcpSocket.port**: the port for TCP connection detection.
+   * - **initialDelaySeconds**: sets the initial delay for the health check. Default value: 10. Unit: seconds.
+   * - **periodSeconds**: sets the health check epoch. Default value: 30. Unit: seconds.
+   * - **timeoutSeconds**: sets the health check timeout period. Default value: 1. Unit: seconds. If this parameter is set to 0 or is not set, the default timeout period is 1 second.
    * 
    * @example
    * {"exec":{"command":["sleep","5s"]},"initialDelaySeconds":10,"timeoutSeconds":11}
    */
   liveness?: string;
   lokiConfigs?: string;
+  /**
+   * @remarks
+   * The maximum surge instance percentage. Valid values:
+   * 
+   * If the minimum number of available instances is 100%, the maximum surge cannot be set to 0. If this parameter is set to **-1**, the system-recommended value of 30% is used, which is 30% of the current number of instances. For example, if the current number of instances is 10, the value is 10 × 30% = 3.
+   * 
+   * @example
+   * -1
+   */
   maxSurgeInstanceRatio?: number;
-  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 maximum number of surge instances. Valid values:
+   * 
+   * If the minimum number of available instances is 100%, the maximum surge cannot be set to 0.
+   * If this parameter is set to **-1**, the system-recommended value of 30% is used, which is 30% of the current number of instances. For example, if the current number of instances is 10, the value is 10 × 30% = 3.
    * 
-   * *   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.
+   * @example
+   * -1
+   */
+  maxSurgeInstances?: number;
+  /**
+   * @remarks
+   * The memory required for each instance. Unit: MB. This parameter cannot be set to 0. The memory has a one-to-one mapping with CPU. Only the following defined specifications are supported:
+   * - **1024**: corresponds to 500 and 1000 millicores of CPU.
+   * - **2048**: corresponds to 500, 1000, and 2000 millicores of CPU.
+   * - **4096**: corresponds to 1000, 2000, and 4000 millicores of CPU.
+   * - **8192**: corresponds to 2000, 4000, and 8000 millicores of CPU.
+   * - **12288**: corresponds to 12000 millicores of CPU.
+   * - **16384**: corresponds to 4000, 8000, and 16000 millicores of CPU.
+   * - **24576**: corresponds to 12000 millicores of CPU.
+   * - **32768**: corresponds to 16000 millicores of CPU.
+   * - **65536**: corresponds to 8000, 16000, and 32000 millicores of CPU.
+   * - **131072**: corresponds to 32000 millicores of CPU.
    * 
    * @example
    * 1024
@@ -394,11 +476,12 @@ export class DeployApplicationRequest extends $dara.Model {
   memory?: number;
   /**
    * @remarks
-   * The Nacos registry. Valid values:
+   * Specifies the Nacos registry. Valid values:
+   * - **0**: Serverless App Engine built-in Nacos.
+   * - **1**: self-managed Nacos.
+   * - **2**: Microservices Engine (MSE) commercial edition Nacos.
    * 
-   * *   **0**: SAE built-in Nacos registry
-   * *   **1**: self-managed Nacos registry
-   * *   **2** : MSE Nacos registry
+   * > If you select Serverless App Engine built-in Nacos, you cannot obtain the configuration of the built-in Nacos.
    * 
    * @example
    * "0"
@@ -406,13 +489,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, which takes effect only when the registry type is MSE Nacos Enterprise Edition.
    * 
    * @example
    * {\\"instanceId\\":\\"mse-cn-zvp2bh6h70r\\",\\"namespace\\":\\"4c0aa74f-57cb-423c-b6af-5d9f2d0e3dbd\\"}
@@ -420,29 +497,23 @@ export class DeployApplicationRequest extends $dara.Model {
   microRegistrationConfig?: string;
   /**
    * @remarks
-   * Configure Microservices Governance
-   * 
-   * Whether to enable microservices governance (enable):
-   * - true: Enable
-   * - false: Disable
+   * Configures microservice governance.
    * 
-   * Configure lossless online/offline deployment (mseLosslessRule):
+   * - Specifies whether to enable microservice governance (enable):
    * 
-   * delayTime: Delay duration (unit: seconds)
+   *    - true: enabled.
    * 
-   * enable: Whether to enable lossless deployment
+   *   - false: disabled.
    * 
-   * - true: Enable
+   * - Configures lossless online/offline (mseLosslessRule):
    * 
-   * - false: Disable
+   *   - delayTime: the delay time.
    * 
-   * notice: Whether to enable notifications
+   *   - enable: specifies whether to enable the lossless online feature. true indicates enabled, and false indicates disabled.
    * 
-   * - true: Enable
+   *   - notice: specifies whether to enable the notification feature. true indicates enabled, and false indicates disabled.
    * 
-   * - false: Disable
-   * 
-   * warmupTime: Small-traffic warm-up duration (unit: seconds)
+   *   - warmupTime: the warm-up duration for low-traffic scenarios. Unit: seconds.
    * 
    * @example
    * {"enable": true,"mseLosslessRule": {"delayTime": 0,"enable": false,"notice": false,"warmupTime": 120}}
@@ -450,12 +521,12 @@ 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 percentage of available instances. Valid 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**: the initialization value, which indicates that the percentage is not used.
+   *  - **0~100**: the unit is percentage, rounded up. For example, if this parameter is set to **50**% and the current number of instances is 5, the minimum number of available instances is 3.
    * 
-   * > 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%**.
+   * > When both **MinReadyInstance** and **MinReadyInstanceRatio** are specified and the value of **MinReadyInstanceRatio** is not **-1**, the **MinReadyInstanceRatio** parameter takes precedence. For example, if **MinReadyInstances** is set to **5** and **MinReadyInstanceRatio** is set to **50**, the value **50** is used to calculate the minimum number of available instances.
    * 
    * @example
    * -1
@@ -463,12 +534,12 @@ export class DeployApplicationRequest extends $dara.Model {
   minReadyInstanceRatio?: number;
   /**
    * @remarks
-   * The minimum number of available instances. Special values:
+   * The minimum number of available instances. Valid values:
    * 
-   * *   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 this parameter is set to **0**, service is interrupted during the upgrade.
+   * - If this parameter is set to **-1**, the system-recommended value is used, which is 25% of the current number of instances. If the current number of instances is 5, 5 × 25% = 1.25, which is rounded up to 2.
    * 
-   * > Make sure that at least one instance is available during application deployment and rollback to prevent business interruptions.
+   * > The minimum number of available instances for each rolling deployment should be ≥ 1 to prevent service interruption.
    * 
    * @example
    * 1
@@ -476,7 +547,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 do not recommend that you configure this field. Configure **NasConfigs** instead. The NAS mount description. If the configuration has not changed during deployment, you do not need to set this parameter (that is, the **MountDesc** field does not need to be included in the request). To clear the NAS configuration, set the value of this field to an empty string (that is, set the value of the **MountDesc** field to "" in the request).
    * 
    * @example
    * [{mountPath: "/tmp", nasPath: "/"}]
@@ -484,7 +555,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 do not recommend that you configure this field. Configure **NasConfigs** instead. The mount point of the NAS file system in the VPC of the application. If the configuration has not changed during deployment, you do not need to set this parameter (that is, the **MountHost** field does not need to be included in the request). To clear the NAS configuration, set the value of this field to an empty string (that is, set the value of the **MountHost** field to "" in the request).
    * 
    * @example
    * 10d3b4bc9****.com
@@ -492,13 +563,12 @@ export class DeployApplicationRequest extends $dara.Model {
   mountHost?: string;
   /**
    * @remarks
-   * The configurations of mounting the NAS file system. Take note of the following rules:
-   * 
-   * *   **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.
+   * The NAS mount configuration. Valid values:
+   * - **mountPath**: the container mount path.
+   * - **readOnly**: set to **false** for read and write permission.
+   * - **nasId**: the NAS ID.
+   * - **mountDomain**: the container mount point address. For more information, see [DescribeMountTargets](https://help.aliyun.com/document_detail/62626.html).
+   * - **nasPath**: the NAS relative file directory.
    * 
    * @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 +576,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 do not recommend that you configure this field. Configure **NasConfigs** instead. The ID of the NAS file system. If the configuration has not changed during deployment, you do not need to set this parameter (that is, the **NasId** field does not need to be included in the request). To clear the NAS configuration, set the value of this field to an empty string (that is, set the value of the **NasId** field to "" in the request).
    * 
    * @example
    * 10d3b4****
@@ -514,13 +584,11 @@ export class DeployApplicationRequest extends $dara.Model {
   nasId?: string;
   /**
    * @remarks
-   * SAE edition.
-   * 
-   * - lite: the lightweight edition.
+   * The application version:
    * 
-   * - std: the standard edition.
-   * 
-   * - pro: the professional edition.
+   * - lite: lite edition.
+   * - std: standard edition.
+   * - pro: professional edition.
    * 
    * @example
    * pro
@@ -528,9 +596,10 @@ 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 identity provider role in the same region in advance. For more information, see [Create an OIDC identity provider](https://help.aliyun.com/document_detail/2331022.html) and [Create a role for SSO identity provider](https://help.aliyun.com/document_detail/2331016.html).
    * 
    * @example
    * sae-test
@@ -538,7 +607,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 +615,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 +623,14 @@ 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.
-   * 
-   * *   **bucketName**: the name of the OSS bucket.
-   * 
-   * *   **bucketPath**: the directory or object in OSS. If the specified directory or object does not exist, an error is returned.
-   * 
-   * *   **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**: specifies whether to only allow the container path to read data from the OSS directory. Valid values:
+   * The OSS mount description. Parameter settings:
    * 
-   *     *   **true**: The container path only has read permission on the OSS directory.
-   *     *   **false**: The application has read and write permissions.
+   * - **bucketName**: the bucket name.
+   * - **bucketPath**: the folder or object that you created in OSS. If the OSS mount folder does not exist, an exception is triggered.
+   * - **mountPath**: the container path in Serverless App Engine. If the path already exists, it is an overwrite relationship. If the path does not exist, it is created.
+   * - **readOnly**: specifies whether the container path has read-only permission on the mounted folder resources. Valid values:
+   *     - **true**: read-only permission.
+   *     - **false**: read and write permission.
    * 
    * @example
    * [{"bucketName": "oss-bucket", "bucketPath": "data/user.data", "mountPath": "/usr/data/user.data", "readOnly": true}]
@@ -573,26 +638,26 @@ 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 application package type. Valid values:
+   * 
+   * - When you deploy with Java, the following types are supported: **FatJar**, **War**, and **Image**.
+   * - When you deploy with PHP, the following types 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**
+   * - When you deploy with Python, the following types are supported: **PythonZip** and **Image**.
    * 
    * @example
    * FatJar
@@ -600,7 +665,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 the deployment package. This parameter is required when **Package Type** is set to **FatJar**, **War**, or **PythonZip**.
    * 
    * @example
    * http://myoss.oss-cn-hangzhou.aliyuncs.com/my-buc/2019-06-30/****.jar
@@ -608,7 +673,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 the deployment package. This parameter is required when **Package Type** is set to **FatJar**, **War**, or **PythonZip**.
    * 
    * @example
    * 1.0.1
@@ -616,7 +681,7 @@ export class DeployApplicationRequest extends $dara.Model {
   packageVersion?: string;
   /**
    * @remarks
-   * The dependent PHP version of PHP package. Image is not supported.
+   * The PHP version on which the deployment package depends. Not supported for images.
    * 
    * @example
    * PHP-FPM 7.0
@@ -624,7 +689,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 that the PHP server loads the configuration file from this path. You do not need to manage the configuration content because Serverless App Engine automatically renders the correct configuration file.
    * 
    * @example
    * /usr/local/etc/php/conf.d/arms.ini
@@ -632,7 +697,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 +705,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 application startup configuration. Ensure that the PHP server uses this configuration file for startup.
    * 
    * @example
    * /usr/local/etc/php/php.ini
@@ -648,7 +713,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"\\]}}`
+   * The script that is run after the container starts. A script is triggered immediately after the container is created. Format: `{"exec":{"command":["sh","-c","echo hello"\\]}}`.
    * 
    * @example
    * {"exec":{"command":["sh","-c","echo hello"]}}
@@ -656,7 +721,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"\\]}}`
+   * The script that is run before the container stops. A script is triggered before the container is deleted. Format: `{"exec":{"command":["sh","-c","echo hello"\\]}}`.
    * 
    * @example
    * {"exec":{"command":["sh","-c","echo hello"]}}
@@ -664,20 +729,19 @@ 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:
+   * Enables K8s Service-based service registration and discovery. Valid values:
    * 
-   * *   **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.
+   * - **portProtocols**: the port and protocol. Valid port values: [1,65535]. Valid protocol values: **TCP** and **UDP**.
+   * - **portAndProtocol**: the port and protocol. Valid port values: [1,65535]. Valid protocol values: **TCP** and **UDP**. **portProtocols is recommended. If portProtocols is set, only portProtocols takes effect**.
+   * - **enable**: enables K8s Service-based 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 environment. **PYTHON 3.9.15** is supported.
    * 
    * @example
    * PYTHON 3.9.15
@@ -685,17 +749,18 @@ 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.
+   * The custom installation module dependencies. By default, the dependencies defined in the requirements.txt file in the root folder are installed. If no dependencies are configured or custom packages are needed, you can specify the dependencies to install.
    * 
    * @example
    * Flask==2.0
    */
   pythonModules?: string;
+  raspConfig?: DeployApplicationRequestRaspConfig;
   /**
    * @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.
+   * The application startup status check. Containers that fail multiple health checks are shut down and restarted. Containers that do not pass the health check do not receive SLB traffic. The **exec**, **httpGet**, and **tcpSocket** methods are supported. For specific examples, see the **Liveness** parameter.
    * 
-   * > You can use only one method to perform the health check.
+   * > Only one method can be selected for health checks.
    * 
    * @example
    * {"exec":{"command":["sleep","6s"]},"initialDelaySeconds":15,"timeoutSeconds":12}
@@ -711,14 +776,14 @@ 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 **Secret** mount description. Use a secret created on the namespace secrets page to inject sensitive information into the container. Settings:
    * 
-   * - secretId: Secret instance ID. Obtain via the ListSecrets interface.
+   * - **secretId**: the secret instance ID. You can obtain it by calling the ListSecrets operation.
+   * - **key**: the key.
    * 
-   * - key: Key-value pair. Note: Set the parameter sae-sys-secret-all to mount all keys.
+   * > You can mount all keys by passing the `sae-sys-secret-all` parameter.
    * 
-   * - mountPath: Mount path.
+   * - **mountPath**: the mount path.
    * 
    * @example
    * [{“secretId":10,”key":"test","mountPath":"/tmp"}]
@@ -726,7 +791,7 @@ export class DeployApplicationRequest extends $dara.Model {
   secretMountDesc?: string;
   /**
    * @remarks
-   * Security group ID.
+   * The security group ID.
    * 
    * @example
    * sg-wz969ngg2e49q5i4****
@@ -734,7 +799,7 @@ export class DeployApplicationRequest extends $dara.Model {
   securityGroupId?: string;
   /**
    * @remarks
-   * The gray-release tag of the application.
+   * The canary release tags configured for the application.
    * 
    * @example
    * {\\"alicloud.service.tag\\":\\"g1\\"}
@@ -742,41 +807,47 @@ export class DeployApplicationRequest extends $dara.Model {
   serviceTags?: string;
   /**
    * @remarks
-   * The configuration of the container.
+   * The sidecar container configuration.
    */
   sidecarContainersConfig?: SidecarContainerConfig[];
   /**
    * @remarks
-   * The logging configurations of Log Service.
+   * The configuration for log collection to Simple Log Service.
    * 
-   * *   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":""}]`.
+   * - Use SLS resources automatically created by Serverless App Engine: `[{"logDir":"","logType":"stdout"},{"logDir":"/tmp/a.log"}]`.
+   * - Use custom SLS resources: `[{"projectName":"test-sls","logType":"stdout","logDir":"","logstoreName":"sae","logtailName":""},{"projectName":"test","logDir":"/tmp/a.log","logstoreName":"sae","logtailName":""}]`.
    * 
-   * The following table describes the parameters that are used in the preceding statements.
+   * Settings:
    * 
-   * *   **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.
+   * - **projectName**: the name of the project in Simple Log Service.  
+   * - **logDir**: the log path.
+   * - **logType**: the log type. **stdout** indicates container standard output logs, and only one entry can be set. If this parameter is not set, file logs are collected.
+   * - **logstoreName**: the name of the Logstore in Simple Log Service.
+   * - **logtailName**: the name of the Logtail in Simple Log Service. If this parameter is not specified, a new Logtail is created by automatic creation.
    * 
-   * 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.
+   * If the SLS collection configuration has not changed during multiple deployments, you do not need to set this parameter (that is, the **SlsConfigs** field does not need to be included in the request). If you no longer need the SLS collection feature, set the value of this field to an empty string (that is, set the value of the **SlsConfigs** field to "" in the request).
    * 
-   * > 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.
+   * > A project that is automatically created with the application is deleted when the application is deleted. Therefore, do not select a project that is automatically created by Serverless App Engine when selecting an existing project.
    * 
    * @example
    * [{"logDir":"","logType":"stdout"},{"logDir":"/tmp/a.log"}]
    */
   slsConfigs?: string;
+  /**
+   * @remarks
+   * 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.
+   * Enables the application startup probe.
    * 
-   * Note: 
+   * - Check succeeded: indicates that the application started successfully. If you configured Liveness and Readiness checks, they are performed after the application starts successfully.
+   * - Check failed: indicates that the application failed to start. An exception is reported and the application is automatically restarted.
    * 
-   * Supports exec, httpGet, and tcpSocket methods. For specific examples, see Liveness Parameters.
-   * Only one method can be selected for health checks.
+   * > This is the description content.
+   * > - The exec, httpGet, and tcpSocket methods are supported. For specific examples, see the Liveness parameter.
+   * > - Only one method can be selected for health checks.
    * 
    * @example
    * {"exec":{"command":["sh","-c","cat /home/admin/start.sh"]},"initialDelaySeconds":30,"periodSeconds":30,"timeoutSeconds":2}
@@ -784,23 +855,20 @@ export class DeployApplicationRequest extends $dara.Model {
   startupProbe?: string;
   /**
    * @remarks
-   * Configure K8s Service-based Service Registration/Discovery and Full-Chain Grayscale Capabilities
-   * 
-   * - enable: Whether to enable full-link grayscale based on K8s Service (set to "true" to enable; set to "false" to disable).
-   * 
-   * - namespaceId: Namespace ID
-   * 
-   * - portAndProtocol: Listener port and protocol. Format: {"Port:Protocol Type":"Container Port"}
-   * - portProtocols: Define service ports and protocols
-   * port: Port
-   * protocol: Protocol
-   * targetPort: Container port
-   * 
-   * - pvtzDiscoveryName: Service discovery name
+   * Configures K8s Service-based service registration and discovery with end-to-end canary release:
    * 
-   * - serviceId: Service ID
-   * 
-   * - serviceName: Service name
+   * - enable: specifies whether to enable end-to-end canary release based on K8s Service.
+   *   - true: enabled.
+   *   - false: disabled.
+   * - namespaceId: the namespace ID.
+   * - portAndProtocol: the listening port and protocol. Format: {"port:protocol type":"container port"}.
+   * - portProtocols: defines the service port and protocol.
+   *   - port: the port.
+   *   - protocol: the protocol.
+   *   - targetPort: the container port.
+   * - pvtzDiscoveryName: the service discovery 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 +876,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 period. Default value: 30. Unit: seconds. Valid values: 1 to 300.
    * 
    * @example
    * 10
@@ -824,13 +892,13 @@ 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 this parameter to "" or "{}" to delete the configuration. Valid values:
    * 
-   * *   **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.
+   * - **port**: the port number. Valid values: 1024 to 65535. Ports smaller than 1024 require root permissions. Because the container is configured with admin permissions, specify a port greater than 1024. Default value: 8080.
+   * - **contextPath**: the access path. Default value: root directory "/".
+   * - **maxThreads**: the connection pool size. Default value: 400.
+   * - **uriEncoding**: the encoding format of Tomcat. Valid values: **UTF-8**, **ISO-8859-1**, **GBK**, and **GB2312**. Default value: **ISO-8859-1**.
+   * - **useBodyEncodingForUri**: specifies whether to use **BodyEncoding for URL**. Default value: **true**.
    * 
    * @example
    * {"port":8080,"contextPath":"/","maxThreads":400,"uriEncoding":"ISO-8859-1","useBodyEncodingForUri":true}
@@ -838,23 +906,20 @@ 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 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}}`
-   * 
-   * The following table describes the parameters that are used in the preceding statements.
+   * The deployment policy. When the minimum number of available instances is 1, the value of the **UpdateStrategy** field is "". When the minimum number of available instances is greater than 1, examples are as follows:
+   *  
+   *  - Grayscale 1 instance + 2 subsequent batches + automatic batching + 1-minute batch interval: `{"type":"GrayBatchUpdate","batchUpdate":{"batch":2,"releaseType":"auto","batchWaitTime":1},"grayUpdate":{"gray":1}}`
+   *   - Grayscale 1 instance + 2 subsequent batches + manual batching: `{"type":"GrayBatchUpdate","batchUpdate":{"batch":2,"releaseType":"manual"},"grayUpdate":{"gray":1}}`
+   *   - 2 batches + automatic batching + 0-minute batch interval: `{"type":"BatchUpdate","batchUpdate":{"batch":2,"releaseType":"auto","batchWaitTime":0}}`
    * 
-   * *   **type**: the type of the release policy. Valid values: **GrayBatchUpdate** and **BatchUpdate**.
+   * Settings:
+   *   - **type**: the publish policy type. Valid values: **GrayBatchUpdate** (grayscale publish) and **BatchUpdate** (batch publish).
+   *   - **batchUpdate**: the batch publish policy.
+   *     - **batch**: the number of publish batches.
+   *     - **releaseType**: the processing method between batches. Valid values: **auto** (automatic) and **manual** (manual).
+   *     - **batchWaitTime**: the interval between batches. Unit: minutes.
    * 
-   * *   **batchUpdate**: the phased release policy.
-   * 
-   *     *   **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.
-   * 
-   * *   **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**.
+   *   - **grayUpdate**: the number of grayscale instances. This parameter is required when **type** is set to **GrayBatchUpdate**.
    * 
    * @example
    * {"type":"GrayBatchUpdate","batchUpdate":{"batch":2,"releaseType":"auto","batchWaitTime":1},"grayUpdate":{"gray":1}}
@@ -862,7 +927,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 vSwitch where the network interface controllers (NICs) of the application instance reside. The vSwitch must be in the specified VPC.
    * 
    * @example
    * vsw-bp12mw1f8k3jgygk9****
@@ -870,7 +935,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 deploying a WAR package-based application. The configuration procedure is the same as that for the startup command of an image-based deployment. For more information, see [Configure a startup command](https://help.aliyun.com/document_detail/96677.html).
    * 
    * @example
    * CATALINA_OPTS=\\"$CATALINA_OPTS $Options\\" catalina.sh run
@@ -878,12 +943,12 @@ 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 on which the deployment package depends. Valid values:
    * 
-   * *   **apache-tomcat-7.0.91**
-   * *   **apache-tomcat-8.5.42**
+   * - **apache-tomcat-7.0.91**
+   * - **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 set to **Image**.
    * 
    * @example
    * apache-tomcat-7.0.91
@@ -959,6 +1024,7 @@ export class DeployApplicationRequest extends $dara.Model {
       pvtzDiscoverySvc: 'PvtzDiscoverySvc',
       python: 'Python',
       pythonModules: 'PythonModules',
+      raspConfig: 'RaspConfig',
       readiness: 'Readiness',
       replicas: 'Replicas',
       secretMountDesc: 'SecretMountDesc',
@@ -1049,6 +1115,7 @@ export class DeployApplicationRequest extends $dara.Model {
       pvtzDiscoverySvc: 'string',
       python: 'string',
       pythonModules: 'string',
+      raspConfig: DeployApplicationRequestRaspConfig,
       readiness: 'string',
       replicas: 'number',
       secretMountDesc: 'string',
@@ -1076,6 +1143,9 @@ export class DeployApplicationRequest extends $dara.Model {
     if(this.labels) {
       $dara.Model.validateMap(this.labels);
     }
+    if(this.raspConfig && typeof (this.raspConfig as any).validate === 'function') {
+      (this.raspConfig as any).validate();
+    }
     if(Array.isArray(this.sidecarContainersConfig)) {
       $dara.Model.validateArray(this.sidecarContainersConfig);
     }