Options
All
  • Public
  • Public/Protected
  • All
Menu

Namespace ListOccAvailabilitiesRequest

example

Click here to see how to use ListOccAvailabilitiesRequest.

Properties

Optional dateExpectedCapacityHandover

dateExpectedCapacityHandover: undefined | string

The capacity handover date of the capacity constraint to filter the list of capacity constraints.

Optional limit

limit: undefined | number

The maximum number of items to return.

occAvailabilityCatalogId

occAvailabilityCatalogId: string

The OCID of the availability catalog.

Optional opcRequestId

opcRequestId: undefined | string

The client request ID for tracing. The only valid characters for request IDs are letters, numbers, underscore, and dash.

Optional page

page: undefined | string

A token representing the position at which to start retrieving results. This must come from {@code opc-next-page} header field of a previous response.

Optional resourceName

resourceName: undefined | string

The name of the resource to filter the list of capacity constraints.

Optional resourceType

resourceType: undefined | string

Resource type using which the capacity constraints of an availability catalog can be filtered.

Optional retryConfiguration

retryConfiguration: RetryConfiguration

RetryConfiguration to be used for the request NOTE : Retries are not supported for requests that have binary or stream bodies this also affects UploadManager operations For all requests with binary/stream bodies, retry attempts are not made

Optional sortBy

sortBy: SortBy

The field to sort by. Only one sort order may be provided. The default order for resource name is ascending. The default order for date of capacity handover is descending.

Optional sortOrder

sortOrder: model.SortOrder

The sort order to use, either 'ASC' or 'DESC'.

Optional workloadType

workloadType: undefined | string

Workload type using the resources in an availability catalog can be filtered.