Serverless App Engine:UpdateJob

The ID of the job template to update.

The Java Development Kit (JDK) version that the deployment package depends on. The following versions are supported:

• Open JDK 8

• Open JDK 7

• Dragonwell 11

• Dragonwell 8

• openjdk-8u191-jdk-alpine3.9

• openjdk-7u201-jdk-alpine3.9

This parameter is not supported when Package Type is set to Image.

The Tomcat version that the deployment package depends on. The following versions are supported:

• apache-tomcat-7.0.91

• apache-tomcat-8.5.42

This parameter is not supported when Package Type is set to Image.

The version of the deployment package. This parameter is required if Package Type is set to FatJar, War, or PythonZip.

The URL of the deployment package. This parameter is required if Package Type is set to FatJar, War, or PythonZip.

The URL of the image. This parameter is required if Package Type is set to Image.

The startup command of the image. The command must be an executable object that exists in the container. Example:

command:
      - echo
      - abc
      - >
      - file0

In this example, Command="echo" and CommandArgs=["abc", ">", "file0"].

The arguments of the image startup Command. The value must be a JSON array that is converted to a string. Format:

["a","b"]

In the preceding example, CommandArgs=["abc", ">", "file0"]. The ["abc", ">", "file0"] array is converted to a string. This parameter is optional.

The environment variables of the container. You can customize environment variables or reference variables from a ConfigMap. To reference a ConfigMap, you must create a ConfigMap instance first. For more information, see CreateConfigMap. The value is a JSON string. The following fields are supported:

• Custom variables

  • name: the name of the environment variable.

  • value: the value of the environment variable.

• Reference variables from a ConfigMap

  • name: The name of the environment variable. You can reference a single key-value pair or all key-value pairs. To reference all key-value pairs, set the value to 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 ID of the ConfigMap.

  • key: The key of the key-value pair. If you want to reference all key-value pairs, do not configure this field.

The custom mapping between a hostname and an IP address in the container. The value is a JSON string. The following fields are supported:

• hostName: the domain name or hostname.

• ip: the IP address.

The options of the JAR package to start the application. The default startup command of the application is: $JAVA_HOME/bin/java $JarStartOptions -jar $CATALINA_OPTS "$package_path" $JarStartArgs

The arguments of the JAR package to start the application. The default startup command of the application is: $JAVA_HOME/bin/java $JarStartOptions -jar $CATALINA_OPTS "$package_path" $JarStartArgs

The version of the application runtime environment in High-speed Service Framework (HSF), such as an Ali-Tomcat container.

The configurations of collecting logs to Log Service.

• Use the Log Service resources that are automatically created by SAE: [{"logDir":"","logType":"stdout"},{"logDir":"/tmp/a.log"}].

• Use a custom Log Service resource: [{"projectName":"test-sls","logType":"stdout","logDir":"","logstoreName":"sae","logtailName":""},{"projectName":"test","logDir":"/tmp/a.log","logstoreName":"sae","logtailName":""}].

The following fields are supported:

• projectName: The name of the Log Service project.

• logDir: The log path.

• logType: The log type. stdout indicates the standard output log of the container. You can specify only one standard output. If you do not configure this field, file logs are collected.

• logstoreName: The name of the Logstore in Log Service.

• logtailName: The name of the Logtail. If you do not specify this parameter, a new Logtail is created.

If the SLS configuration is not changed during a deployment, you do not need to configure this parameter. To stop using the log collection feature, set the value of this parameter to an empty string ("").

The time zone. Default value: Asia/Shanghai.

The ID of the Apsara File Storage NAS file system. If the configurations are not changed during a deployment, you do not need to configure this parameter. To clear the NAS configurations, set the value of this parameter to an empty string ("").

The mount target of the NAS file system in the virtual private cloud (VPC) where the job template is located. If the configurations are not changed during a deployment, you do not need to configure this parameter. To clear the NAS configurations, set the value of this parameter to an empty string ("").

The description of the NAS mount. If the configurations are not changed during a deployment, you do not need to configure this parameter. To clear the NAS configurations, set the value of this parameter to an empty string ("") in the request.

The script that is executed after the container is started. Example: {"exec":{"command":["sh","-c","echo hello"]}}

The script that is executed before the container is stopped. Example: {"exec":{"command":["sh","-c","echo hello"]}}

The startup command for the application that is deployed in a WAR package. The procedure is the same as that for configuring the startup command for an image. For more information, see Set a startup command.

The description of the ConfigMap instance that is mounted to the container. You can use the ConfigMap instance created on the Namespace Configurations page to inject configurations into the container. The value is a JSON string. The following fields are supported:

• configMapId: The ID of the ConfigMap instance. You can call the ListNamespacedConfigMaps operation to obtain the ID.

• key: The key of the key-value pair.

• mountPath: The mount path.

The graceful timeout period. Default value: 30. Unit: seconds. Valid values: 1 to 300.

The path on which the PHP application startup configuration file is mounted. Make sure that the PHP server uses this configuration file to start the application.

The content of the PHP configuration file.

The configurations of the Tomcat file. If you set this parameter to "" or "{}", the configurations are deleted. The value is a JSON string. The following fields are supported:

• port: The port number. Valid values: 1024 to 65535. The root permission is required to perform operations on ports whose number is smaller than 1024. The container is configured with the administrator permission. Therefore, specify a port whose number is greater than 1024. If you do not configure this field, the default port 8080 is used.

• contextPath: The context path. Default value: /.

• maxThreads: The maximum number of connections in the connection pool. Default value: 400.

• uriEncoding: The URI encoding scheme in Tomcat. Supported values: UTF-8, ISO-8859-1, GBK, and GB2312. If you do not set this parameter, the default value ISO-8859-1 is used.

• useBodyEncodingForUri: Specifies whether to use BodyEncoding for URL. Default value: true.

The description of the OSS mount. The value is a JSON string. The following parameters are supported:

• bucketName: the name of the bucket.

• bucketPath: the directory or object that you created in OSS. An exception occurs if the specified OSS mount directory does not exist.

• mountPath: The path in the SAE container. If the path exists, the new path overwrites the existing one. If the path does not exist, a new path is created.

• readOnly: specifies whether a container has the read-only permission on the resources in the mount directory.

  • true: The container has the read-only permission.

  • false: The container has the read and write permissions.

The AccessKey ID that is used to read data from and write data to OSS.

The AccessKey secret that is used to read data from and write data to OSS.

The ID of the Container Registry Enterprise Edition instance.

The ID of the Container Registry Enterprise Edition instance. This parameter is required if ImageUrl is set to an image in a Container Registry Enterprise Edition instance.

The Alibaba Cloud Resource Name (ARN) of the RAM role that is required to pull images across accounts. For more information, see Grant permissions across Alibaba Cloud accounts by using a RAM role.

The ID of the secret.

Specifies whether to enable image acceleration.

The trigger configuration. Configure this parameter based on the job type.

• Cron job: Set the type field to time, the config field to a cron expression, and the timezone field to the desired time zone. Example: {"type":"time","config":"0 1 */1 * ?","timezone":"GMT+8:00"}

• One-time job: Set the type field to http and configure the config field with specific HTTP trigger rules. For more information, see SourceHttpEventParameters. Example: {"type":"http","config":{"type":"HTTPS","method":["GET"],"ip":[],"referer":[],"securityConfig":"none"}}

The policy of running concurrent jobs. Valid values:

• Forbid: A new job is not created if the previous job is not completed.

• Allow: Concurrent jobs are allowed.

• Replace: When the time to create a new job is reached, the new job replaces the previous job if the previous job is not completed.

The timeout period for the job. Unit: seconds.

The number of retries for the job.

Enables job sharding.

The parameters for job sharding.

The number of concurrent instances for the job.

The ID of the referenced application.

The programming language. Supported values: java, php, python, and shell.

The Python environment. PYTHON 3.9.15 is supported.

The custom module dependencies. By default, the dependencies that are defined in the requirements.txt file in the root directory of the package are installed. If you do not configure this parameter or the package does not have a requirements.txt file, you can specify the dependencies that you want to install.

The configurations of mounting a NAS file system.

The BestEffort policy.