Fetches all pages of results. If you provide this option, then you cannot provide the
Provide input to this command as a JSON document from a file using the file://path-to/file syntax.
--generate-full-command-json-input option can be used to generate a sample json file to be used with this command option. The key names are pre-populated and match the command option names (converted to camelCase format, e.g. compartment-id –> compartmentId), while the values of the keys need to be populated by the user before using the sample file as an input to this command. For any command option that accepts multiple values, the value of the key can be a JSON array.
Options can still be provided on the command line. If an option exists in both the JSON document and the command line then the command line specified value will be used.
For examples on usage of this option, please see our “using CLI with advanced JSON options” link: https://docs.cloud.oracle.com/iaas/Content/API/SDKDocs/cliusing.htm#AdvancedJSONOptions
The maximum number of items to return.
The position at which to start retrieving results. This must come from the opc-next-page header field of a previous response.
When fetching results, the number of results to fetch per call. Only valid when used with
--limit, and ignored otherwise.
The field to sort by. Only one sort order may be provided. The default order for timeAccepted is descending.
Accepted values are:
The sort order to use, either ‘ASC’ or ‘DESC’.
Accepted values are:
oci --help for help on global parameters.
Copy the following CLI commands into a file named example.sh. Run the command by typing “bash example.sh” and replacing the example parameters with your own.
export work_request_id=<substitute-value-of-work_request_id> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/ai-vision/work-request-log-entry/list-work-request-logs.html#cmdoption-work-request-id oci ai-vision work-request-log-entry list-work-request-logs --work-request-id $work_request_id