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}
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.
The OCID of the service mesh in which this access policy is created.
A user-friendly name. The name has to be unique within the same service mesh and cannot be changed after creation. Avoid entering confidential information.
Example: {@code My unique resource name}
List of applicable rules.
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.
Access policies enable administrators to restrict the access of certain services.