The availability domain (AD) for which the capacity request is made. If this is specified then the capacity will be validated and fulfilled within the scope of this AD.
Since all resources are at tenancy level hence this will be the ocid of the tenancy where operation is to be performed.
The date by which the capacity requested by customers before dateFinalCustomerOrder needs to be fulfilled.
Defined tags for this resource. Each key is predefined and scoped to a namespace. Example: {@code {"foo-namespace": {"bar-key": "value"}}}
Meaningful text about the capacity request.
A list of different resources requested by the user.
An user-friendly name for the capacity request. Does not have to be unique, and it's changeable. Avoid entering confidential information.
Simple key-value pair that is applied without any predefined name, type or scope. Exists for cross-compatibility only. Example: {@code {"bar-key": "value"}}
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 name of the OCI service in consideration. For example, Compute, Exadata, and so on.
The OCID of the availability catalog against which capacity request is made.
The name of the region for which the capacity request is made.
The subset of request states available for creating the capacity request.
Details about the create request for the capacity request.