The availability domain (AD) for which the capacity request was made.
The OCID of the tenancy from which the request was made.
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 resources requested as part of this request
The display name of the capacity request.
Simple key-value pair that is applied without any predefined name, type or scope. Exists for cross-compatibility only. Example: {@code {"bar-key": "value"}}
The OCID of the capacity request.
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 lifecycle state of the resource.
The name of the OCI service in consideration. For example, Compute, Exadata, and so on.
The OCID of the availability catalog against which the capacity request was placed.
The OCID of the customer group to which this customer belongs to.
The name of the region for which the capacity request was made.
The different states the capacity request goes through.
System tags for this resource. Each key is predefined and scoped to a namespace. Example: {@code {"orcl-cloud": {"free-tier-retained": "true"}}}
The time when the capacity request was created.
The time when the capacity request was updated.
A single request of some quantity of a specific server type, in a specific location and expected delivery date. The maximum amount possible to request is the smallest number between the number of servers available for purchase and the number of servers allowed by the constraints (For example, power, network, physical space, and so on).