Get Applications Application
Constructors
Properties
The ARN of the RAM role required when pulling images across accounts.
The ID of the ACR EE instance.
Application description information. No more than 1024 characters.
The first ID of the resource.
Mirror startup command parameters. The parameters required for the above start command. For example: 1d.
ConfigMap mount description.
Indicates That the Application of the Creation Time.
Custom host mapping in the container. For example: {"hostName":"samplehost","ip":"127.0.0.1"}.
The operating environment used by the Pandora application.
The virtual switch where the elastic network card of the application instance is located. The switch must be located in the aforementioned VPC. The switch also has a binding relationship with the SAE namespace. If it is left blank, the default is the vSwitch ID bound to the namespace.
The JAR package starts application parameters. Application default startup command: $JAVA_HOME/bin/java $JarStartOptions -jar $CATALINA_OPTS "$package_path" $JarStartArgs.
The JAR package starts the application option. Application default startup command: $JAVA_HOME/bin/java $JarStartOptions -jar $CATALINA_OPTS "$package_path" $JarStartArgs.
The Minimum Available Instance. On the Change Had Promised during the Available Number of Instances to Be.
Mount description information.
SAE namespace ID. Only namespaces whose names are lowercase letters and dashes (-) are supported, and must start with a letter. The namespace can be obtained by calling the DescribeNamespaceList interface.
ID of the mounted NAS, Must be in the same region as the cluster. It must have an available mount point creation quota, or its mount point must be on a switch in the VPC. If it is not filled in and the mountDescs field is present, a NAS will be automatically purchased and mounted on the switch in the VPC by default.
OSS AccessKey Secret.
OSS mount description information.
The OSS mount detail.
Application package type. Support FatJar, War and Image.
Deployment package address. Only FatJar or War type applications can configure the deployment package address.
The version number of the deployment package. Required when the Package Type is War and FatJar.
The PHP application monitors the mount path, and you need to ensure that the PHP server will load the configuration file of this path. You don't need to pay attention to the configuration content, SAE will automatically render the correct configuration file.
PHP application startup configuration mount path, you need to ensure that the PHP server will start using this configuration file.
Application startup status checks, containers that fail multiple health checks will be shut down and restarted. Containers that do not pass the health check will not receive SLB traffic. For example: {"exec":{"command":"sh","-c","cat /home/admin/start.sh"},"initialDelaySeconds":30,"periodSeconds":30,"timeoutSeconds ":2}.
Security group ID.
SLS configuration.
Graceful offline timeout, the default is 30, the unit is seconds. The value range is 1~60.
Tomcat file configuration, set to "" or "{}" means to delete the configuration: useDefaultConfig: Whether to use a custom configuration, if it is true, it means that the custom configuration is not used; if it is false, it means that the custom configuration is used. If you do not use custom configuration, the following parameter configuration will not take effect. contextInputType: Select the access path of the application. war: No need to fill in the custom path, the access path of the application is the WAR package name. root: No need to fill in the custom path, the access path of the application is /. custom: You need to fill in the custom path in the custom path below. contextPath: custom path, this parameter only needs to be configured when the contextInputType type is custom. httpPort: The port range is 1024~65535. Ports less than 1024 need Root permission to operate. Because the container is configured with Admin permissions, please fill in a port greater than 1024. If not configured, the default is 8080. maxThreads: Configure the number of connections in the connection pool, the default size is 400. uriEncoding: Tomcat encoding format, including UTF-8, ISO-8859-1, GBK and GB2312. If not set, the default is ISO-8859-1. useBodyEncoding: Whether to use BodyEncoding for URL.
The VPC corresponding to the SAE namespace. In SAE, a namespace can only correspond to one VPC and cannot be modified. Creating a SAE application in the namespace for the first time will form a binding relationship. Multiple namespaces can correspond to a VPC. If you leave it blank, it will default to the VPC ID bound to the namespace.
WAR package launch application option. Application default startup command: java $JAVA_OPTS $CATALINA_OPTS -Options org.apache.catalina.startup.Bootstrap "$@" start.
The version of tomcat that the deployment package depends on. Image type applications are not supported.