The OCID of the compartment that contains the application.
Application configuration for functions in this application (passed as environment variables). Can be overridden by function configuration. Keys must be ASCII strings consisting solely of letters, digits, and the '_' (underscore) character, and must not begin with a digit. Values should be limited to printable unicode characters.
Example: {@code {\"MY_FUNCTION_CONFIG\": \"ConfVal\"}}
The maximum size for all configuration keys and values is limited to 4KB. This is measured as the sum of octets necessary to represent each key and value in UTF-8.
Defined tags for this resource. Each key is predefined and scoped to a namespace. For more information, see Resource Tags.
Example: {@code {\"Operations\": {\"CostCenter\": \"42\"}}}
The display name of the application. The display name is unique within the compartment containing the application.
Free-form tags for this resource. Each tag is a simple key-value pair with no predefined name, type, or namespace. For more information, see Resource Tags.
Example: {@code {\"Department\": \"Finance\"}}
The OCID of the application.
The current state of the application.
The OCIDs of the Network Security Groups to add the application to.
Valid values are {@code GENERIC_X86}, {@code GENERIC_ARM} and {@code GENERIC_X86_ARM}. Default is {@code GENERIC_X86}. Setting this to {@code GENERIC_X86}, will run the functions in the application on X86 processor architecture. Setting this to {@code GENERIC_ARM}, will run the functions in the application on ARM processor architecture. When set to {@code GENERIC_X86_ARM}, functions in the application are run on either X86 or ARM processor architecture. Accepted values are: {@code GENERIC_X86}, {@code GENERIC_ARM}, {@code GENERIC_X86_ARM}
The OCIDs of the subnets in which to run functions in the application.
A syslog URL to which to send all function logs. Supports tcp, udp, and tcp+tls. The syslog URL must be reachable from all of the subnets configured for the application. Note: If you enable the OCI Logging service for this application, the syslogUrl value is ignored. Function logs are sent to the OCI Logging service, and not to the syslog URL.
Example: {@code tcp://logserver.myserver:1234}
The time the application was created, expressed in RFC 3339 timestamp format.
Example: {@code 2018-09-12T22:47:12.613Z}
The time the application was updated, expressed in RFC 3339 timestamp format. Example: {@code 2018-09-12T22:47:12.613Z}
An application contains functions and defined attributes shared between those functions, such as network configuration and configuration. Avoid entering confidential information.