get
***


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

Gets the current representation of the given bucket in the given
namespace.


Usage
=====

   oci os bucket get [OPTIONS]


Options
=======


--namespace-name, --namespace, -ns [text]
-----------------------------------------

The top-level namespace used for the request. If not provided, this
parameter will be obtained internally using a call to 'oci os ns get'


--bucket-name, --name, -bn [text]
---------------------------------

The name of the bucket. Avoid entering confidential information.
Example: *my-new-bucket1* [required]


--if-match [text]
-----------------

The entity tag to match. For creating and committing a multipart
upload to an object, this is the entity tag of the target object. For
uploading a part, this is the entity tag of the target part.


--if-none-match [text]
----------------------

The entity tag to avoid matching. The only valid value is '*', which
indicates that the request should fail if the object already exists.
For creating and committing a multipart upload, this is the entity tag
of the target object. For uploading a part, this is the entity tag of
the target part.


--fields [approximateCount|approximateSize]
-------------------------------------------

Bucket summary includes the 'namespace', 'name', 'compartmentId',
'createdBy', 'timeCreated', and 'etag' fields. This parameter can also
include 'approximateCount' (Approximate number of objects) and
'approximateSize' (total approximate size in bytes of all objects).
For example 'approximateCount,approximateSize'


--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.
