Options
All
  • Public
  • Public/Protected
  • All
Menu

Namespace ListStagesRequest

example

Click here to see how to use ListStagesRequest.

Properties

Optional limit

limit: undefined | number

The maximum number of items to return.

Optional opcRequestId

opcRequestId: undefined | string

The client request ID 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.

remediationRunId

remediationRunId: string

Unique Remediation Run identifier path parameter.

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 used to sort Stages. Only one sort order is allowed. Default order for status is the following sequence: CREATED, IN_PROGRESS, SUCCEEDED, FAILED, CANCELING, and CANCELED. Default order for timeCreated is descending. Default order for timeFinished is descending. Default order for timeStarted is descending. Default order for type is the following sequence: DETECT, RECOMMEND, VERIFY, and APPLY.

Optional sortOrder

sortOrder: model.SortOrder

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

Optional status

status: undefined | string

A filter to return only Stages that match the specified status.

Optional type

type: model.RemediationRunStageType

A filter to return only Stages that match the specified type.