list
****


Description
===========

Gets a list of Autonomous Data Warehouse backups based on either the
*autonomousDataWarehouseId* or *compartmentId* specified as a query
parameter.


Usage
=====

   oci db autonomous-data-warehouse-backup list [OPTIONS]


Options
=======


--autonomous-data-warehouse-id [text]
-------------------------------------

The database OCID.


--compartment-id, -c [text]
---------------------------

The compartment OCID.


--limit [integer]
-----------------

The maximum number of items to return per page.


--page [text]
-------------

The pagination token to continue listing from.


--sort-by [TIMECREATED|DISPLAYNAME]
-----------------------------------

The field to sort by.  You can provide one sort order (*sortOrder*).
Default order for TIMECREATED is descending.  Default order for
DISPLAYNAME is ascending. The DISPLAYNAME sort order is case
sensitive.

**Note:** If you do not include the availability domain filter, the
resources are grouped by availability domain, then sorted.


--sort-order [ASC|DESC]
-----------------------

The sort order to use, either ascending (*ASC*) or descending
(*DESC*).


--lifecycle-state [CREATING|ACTIVE|DELETING|DELETED|FAILED]
-----------------------------------------------------------

A filter to return only resources that match the given lifecycle state
exactly.


--display-name [text]
---------------------

A filter to return only resources that match the entire display name
given. The match is not case sensitive.


--all
-----

Fetches all pages of results. If you provide this option, then you
cannot provide the --limit option.


--page-size [integer]
---------------------

When fetching results, the number of results to fetch per call. Only
valid when used with --all or --limit, and ignored otherwise.


--from-json [text]
------------------

Provide input to this command as a JSON document from a file using the
file://path-to/file syntax.

The --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/Conte
nt/API/SDKDocs/cliusing.htm#AdvancedJSONOptions


-?, -h, --help
--------------

For detailed help on any of these individual commands, enter <command>
--help.
