Options
All
  • Public
  • Public/Protected
  • All
Menu

Namespace ListCccUpgradeSchedulesRequest

example

Click here to see how to use ListCccUpgradeSchedulesRequest.

Properties

Optional accessLevel

accessLevel: AccessLevel

Valid values are RESTRICTED and ACCESSIBLE. Default is RESTRICTED. Setting this to ACCESSIBLE returns only those compartments for which the user has INSPECT permissions directly or indirectly (permissions can be on a resource in a subcompartment). When set to RESTRICTED permissions are checked and no partial results are displayed.

Optional cccUpgradeScheduleId

cccUpgradeScheduleId: undefined | string

Compute Cloud@Customer upgrade schedule OCID.

Optional compartmentId

compartmentId: undefined | string

The OCID of the compartment in which to list resources.

Optional compartmentIdInSubtree

compartmentIdInSubtree: undefined | false | true

Default is false. When set to true, the hierarchy of compartments is traversed and all compartments and sub-compartments in the tenancy are returned. Depends on the 'accessLevel' setting.

Optional displayName

displayName: undefined | string

A filter to return only resources that match the entire display name given.

Optional displayNameContains

displayNameContains: undefined | string

A filter to return only resources whose display name contains the substring.

Optional lifecycleState

lifecycleState: undefined | string

A filter to return resources only when their lifecycleState matches the given lifecycleState.

Optional limit

limit: undefined | number

The maximum number of items to return.

Optional opcRequestId

opcRequestId: undefined | string

The client request OCID for tracing.

Optional page

page: undefined | string

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

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. Default order for timeCreated is descending. Default order for displayName is ascending.

Optional sortOrder

sortOrder: model.SortOrder

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