The OCID of the compartment that contains the work request. Work requests should be scoped to the same compartment as the resource the work request affects. If the work request concerns multiple resources, and those resources are not in the same compartment, it is up to the service team to pick the primary resource whose compartment should be used.
The OCID of the deployment in which to list resources.
A filter to return only the resources that match the entire 'displayName' given.
A filter to return only the resources that match the 'lifecycleState' given.
The maximum number of items to return.
The client request ID for tracing.
The page token representing the page at which to start retrieving results. This is usually retrieved from a previous list call.
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
The field to sort by. Only one sort order can be provided. Default order for 'timeCreated' is descending. Default order for 'displayName' is ascending. If no value is specified timeCreated is the default.
The sort order to use, either 'asc' or 'desc'.
Click here to see how to use ListDeploymentUpgradesRequest.