Unique key of the aggregator
Unique type of the aggregator
The application key.
Specifies the fields to get for an object.
This filter parameter can be used to filter by model specific queryable fields of the object
Examples:-
Used to filter by the identifier of the object.
Used to filter by the key of the object.
Sets the maximum number of results per page, or items to return in a paginated {@code List} call. See List Pagination.
Used to filter by the name of the object.
Unique Oracle-assigned identifier for the request. If you need to contact Oracle about a particular request, please provide the request ID.
For list pagination. The value for this parameter is the {@code opc-next-page} or the {@code opc-prev-page} response header from the previous {@code List} call. See List Pagination.
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
Specifies the field to sort by. Accepts only one field. By default, when you sort by time fields, results are shown in descending order. All other fields default to ascending order. Sorting related parameters are ignored when parameter {@code query} is present (search operation and sorting order is by relevance score in descending order).
Specifies sort order to use, either {@code ASC} (ascending) or {@code DESC} (descending).
The workspace ID.
Click here to see how to use ListRuntimePipelinesRequest.