Serverless App Engine:UpdateJob

The ID of the job template to update.

The JDK version that the deployment package depends on. Supported versions:

• Open JDK 8

• Open JDK 7

• Dragonwell 11

• Dragonwell 8

• openjdk-8u191-jdk-alpine3.9

• openjdk-7u201-jdk-alpine3.9

Not supported when Package Type is Image.

The Tomcat version that the deployment package depends on. Supported versions:

• apache-tomcat-7.0.91

• apache-tomcat-8.5.42

Not supported when Package Type is Image.

The version number of the deployment package. Required when Package Type is FatJar, War, or PythonZip.

The URL of the deployment package. Required when Package Type is FatJar, War, or PythonZip.

The image address. Required when Package Type is Image.

The startup command for the image. This 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 for the startup command Command. Format:

["a","b"]

In the preceding example, CommandArgs=["abc", ">", "file0"]. The value ["abc", ">", "file0"] must be converted into a JSON array string. If no arguments are required, leave this parameter empty.

Environment variables for the container. You can define custom environment variables or reference ConfigMaps. To reference a ConfigMap, create a ConfigMap instance first. For more information, see CreateConfigMap. Values:

• Custom configuration

  • name: The name of the environment variable.

  • value: The value of the environment variable.

• Reference a ConfigMap

  • name: The name of the environment variable. To reference a single key or all keys, enter sae-sys-configmap-all-<ConfigMap name>, such as sae-sys-configmap-all-test1.

  • valueFrom: The reference type of the environment variable. Set the value to configMapRef.

  • configMapId: The ID of the ConfigMap.

  • key: The key. Do not set this field if you reference all key-value pairs.

Custom host mappings in the container. Values:

• hostName: The domain name or hostname.

• ip: The IP address.

Startup options for JAR packages. Default startup command: $JAVA_HOME/bin/java $JarStartOptions -jar $CATALINA_OPTS "$package_path" $JarStartArgs

Startup arguments for JAR packages. Default startup command: $JAVA_HOME/bin/java $JarStartOptions -jar $CATALINA_OPTS "$package_path" $JarStartArgs

The runtime environment version for jobs in the HSF framework, such as the Ali-Tomcat container.

Configuration for log collection to Simple Log Service (SLS).

• Use SLS resources automatically created by SAE: [{"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":""}].

Parameters:

• projectName: The name of the SLS project.

• logDir: The log path.

• logType: The log type. stdout indicates standard output logs from the container. You can configure only one stdout log entry. If this parameter is not specified, file logs are collected.

• logstoreName: The name of the SLS Logstore.

• logtailName: The name of the SLS Logtail. If not specified, a new Logtail is created.

If the SLS collection configuration remains unchanged during redeployment, you do not need to specify this parameter (exclude the SlsConfigs field from the request). To disable SLS collection, set this field to an empty string (SlsConfigs="").

The time zone. Default value: Asia/Shanghai.

The ID of the NAS file system. If the NAS configuration remains unchanged during deployment, you do not need to specify this parameter (exclude the NasId field from the request). To clear the NAS configuration, set this field to an empty string (NasId="").

The mount target of the NAS file system in the VPC of the job template. If the NAS configuration remains unchanged during deployment, you do not need to specify this parameter (exclude the MountHost field from the request). To clear the NAS configuration, set this field to an empty string (MountHost="").

The NAS mount description. If the NAS configuration remains unchanged during deployment, you do not need to specify this parameter (exclude the MountDesc field from the request). To clear the NAS configuration, set this field to an empty string (MountDesc="").

A script that runs after the container starts. This script runs immediately after the container is created. Format: {"exec":{"command":\["sh","-c","echo hello"\]}}

A script that runs before the container stops. This script runs before the container is deleted. Format: {"exec":{"command":\["sh","-c","echo hello"\]}}

The startup command for WAR package deployment tasks. The configuration steps are the same as those for image deployment startup commands. For more information, see Configure startup commands.

The ConfigMap mount description. Use ConfigMaps created on the namespace ConfigMap page to inject configuration information into containers. Parameters:

• configMapId: The ID of the ConfigMap instance. You can obtain it by calling the ListNamespacedConfigMaps operation.

• key: The key.

• mountPath: The mount path.

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

The mount path for the PHP task startup configuration file. Ensure that the PHP server uses this configuration file to start.

The content of the PHP configuration file.

Tomcat file configuration. Set this parameter to "" or "{}" to delete the configuration. Parameters:

• port: The port range is 1024 to 65535. Ports below 1024 require root permissions. Because containers run with admin permissions, use ports above 1024. If not configured, the default port is 8080.

• contextPath: The access path. Default value: root directory "/".

• maxThreads: The size of the connection pool. Default value: 400.

• uriEncoding: The encoding format of Tomcat. Valid values: UTF-8, ISO-8859-1, GBK, and GB2312. Default value: ISO-8859-1.

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

OSS mount description. Parameters:

• bucketName: The bucket name.

• bucketPath: The directory or OSS object that you created in OSS. If the OSS mount directory does not exist, an exception occurs.

• mountPath: The container path in SAE. If the path already exists, it is overwritten. If the path does not exist, it is created.

• readOnly: Specifies whether the container path has read-only access to the mounted directory. Values:

  • true: Read-only permission.

  • false: Read and write permission.

The AccessKey ID for OSS read and write operations.

The AccessKey secret for OSS read and write operations.

The ID of the Container Registry Enterprise Edition instance.

The ID of the Container Registry Enterprise Edition instance. Required when ImageUrl is from Container Registry Enterprise Edition.

The ARN of the RAM role required for cross-account image pulling. For more information, see Authorize cross-cloud account access using RAM roles.

The ID of the corresponding secret.

Job trigger configuration based on job type.

• Scheduled task: Set type to time, config to a Cron expression, and timezone to a specific time zone. Example: {"type":"time","config":"0 1 */1 * ?","timezone":"GMT+8:00"}

• Manually triggered node instance: Set type to http and config to specific HTTP trigger rules. For more information, see Request parameters SourceHttpEventParameters. Example: {"type":"http","config":{"type":"HTTPS","method":["GET"],"ip":[],"referer":[],"securityConfig":"none"}}

Job concurrency policy. Values:

• Forbid: Prevents concurrent job execution. A new job is not created if the previous job is still running.

• Allow: Allows concurrent job execution.

• Replace: Replaces the previous job with a new job if the previous job is still running when the new job is scheduled.

The job timeout period. Unit: seconds.

The number of job retries.

Enable job sharding.

Job sharding parameters.

The number of concurrent job instances.

The ID of the referenced job target.

The programming language of the program. Supported languages: java, php, python, and shell.

The Python environment. Supports PYTHON 3.9.15.

Dependencies for custom installation. By default, dependencies defined in requirements.txt in the root directory are installed. If no configuration or custom packages are provided, you can specify the dependencies to install.