The OCID of the compartment containing the resource this quota applies to.
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 description you assign to the quota.
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 quota.
The quota's current state. After creating a quota, make sure its {@code lifecycleState} is set to ACTIVE before using it.
Locks associated with this resource.
The name you assign to the quota during creation. The name must be unique across all quotas in the tenancy and cannot be changed.
An array of one or more quota statements written in the declarative quota statement language.
Date and time the quota was created, in the format defined by RFC 3339. Example: {@code 2016-08-25T21:10:29.600Z}
Quotas are applied on top of the service limits and inherited through the nested compartment hierarchy. Quotas allow compartment admins to limit resource consumption and set boundaries around acceptable resource use. The term "quota" can be interpreted as the following: