The OCID of a compartment.
User provided key and value pair configuration, which is assigned through constants or parameter.
Defined tags for this resource. Each key is predefined and scoped to a namespace. See Resource Tags. Example: {@code {"foo-namespace": {"bar-key": "value"}}}
The OCID of a pipeline.
Optional description about the deployment stage.
Deployment stage display name, which can be renamed and is not necessarily unique. Avoid entering confidential information.
A Docker image artifact OCID.
Simple key-value pair that is applied without any predefined name, type or scope. Exists for cross-compatibility only. See Resource Tags. Example: {@code {"bar-key": "value"}}
Function environment OCID.
Timeout for execution of the Function. Value in seconds. Note: Numbers greater than Number.MAX_SAFE_INTEGER will result in rounding issues.
Unique identifier that is immutable on creation.
A message describing the current state in more detail. For example, can be used to provide actionable information for a resource in Failed state.
The current state of the deployment stage.
Maximum usable memory for the Function (in MB). Note: Numbers greater than Number.MAX_SAFE_INTEGER will result in rounding issues.
The OCID of a project.
Usage of system tag keys. These predefined keys are scoped to namespaces. See Resource Tags. Example: {@code {"orcl-cloud": {"free-tier-retained": "true"}}}
Time the deployment stage was created. Format defined by RFC3339.
Time the deployment stage was updated. Format defined by RFC3339.
Specifies the Function stage.