A list of certificate authority resources to use for creating leaf certificates for mTLS authentication. Currently we only support one certificate authority, but this may expand in future releases. Request with more than one certificate authority will be rejected.
The OCID of the compartment.
Defined tags for this resource. Each key is predefined and scoped to a namespace. Example: {@code {"foo-namespace": {"bar-key": "value"}}}
Description of the resource. It can be changed after creation. Avoid entering confidential information.
Example: {@code This is my new resource}
A user-friendly name. The name does not have to be unique and can be changed after creation. Avoid entering confidential information.
Example: {@code My new resource}
Simple key-value pair that is applied without any predefined name, type or scope. Exists for cross-compatibility only. Example: {@code {"bar-key": "value"}}
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 a Failed state.
The current state of the Resource.
Usage of system tag keys. These predefined keys are scoped to namespaces. Example: {@code {"orcl-cloud": {"free-tier-retained": "true"}}}
The time when this resource was created in an RFC3339 formatted datetime string.
The time when this resource was updated in an RFC3339 formatted datetime string.
The mesh resource is the top-level container that represents the logical boundary of application traffic between the services and deployments that reside within it. A mesh also provides a unit of access control.