create
******


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

Creates a new compartment in your tenancy.

**Important:** Compartments cannot be deleted.

You must specify your tenancy's OCID as the compartment ID in the
request object. Remember that the tenancy is simply the root
compartment. For information about OCIDs, see Resource Identifiers.

You must also specify a *name* for the compartment, which must be
unique across all compartments in your tenancy. You can use this name
or the OCID when writing policies that apply to the compartment. For
more information about policies, see How Policies Work.

You must also specify a *description* for the compartment (although it
can be an empty string). It does not have to be unique, and you can
change it anytime with UpdateCompartment.

After you send your request, the new object's *lifecycleState* will
temporarily be CREATING. Before using the object, first make sure its
*lifecycleState* has changed to ACTIVE.


Usage
=====

   oci iam compartment create [OPTIONS]


Options
=======


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

The OCID of the tenancy containing the compartment. [required]


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

The name you assign to the compartment during creation. The name must
be unique across all compartments in the tenancy. Avoid entering
confidential information. [required]


--description [text]
--------------------

The description you assign to the compartment during creation. Does
not have to be unique, and it's changeable. [required]


--freeform-tags [complex type]
------------------------------

Free-form tags for this resource. Each tag is a simple key-value pair
with no predefined name, type, or namespace. For more information, see
Resource Tags. Example: *{"Department": "Finance"}* This is a complex
type whose value must be valid JSON. The value can be provided as a
string on the command line or passed in as a file using the
file://path/to/file syntax.

The --generate-param-json-input option can be used to generate an
example of the JSON which must be provided. We recommend storing this
example in a file, modifying it as needed and then passing it back in
via the file:// syntax.


--defined-tags [complex type]
-----------------------------

Defined tags for this resource. Each key is predefined and scoped to a
namespace. For more information, see Resource Tags. Example:
*{"Operations": {"CostCenter": "42"}}* This is a complex type whose
value must be valid JSON. The value can be provided as a string on the
command line or passed in as a file using the file://path/to/file
syntax.

The --generate-param-json-input option can be used to generate an
example of the JSON which must be provided. We recommend storing this
example in a file, modifying it as needed and then passing it back in
via the file:// syntax.


--wait-for-state [CREATING|ACTIVE|INACTIVE|DELETING|DELETED]
------------------------------------------------------------

This operation creates, modifies or deletes a resource that has a
defined lifecycle state. Specify this option to perform the action and
then wait until the resource reaches a given lifecycle state.


--max-wait-seconds [integer]
----------------------------

The maximum time to wait for the resource to reach the lifecycle state
defined by --wait-for-state. Defaults to 1200 seconds.


--wait-interval-seconds [integer]
---------------------------------

Check every --wait-interval-seconds to see whether the resource to see
if it has reached the lifecycle state defined by --wait-for-state.
Defaults to 30 seconds.


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

Provide input to this command as a JSON document from a file.

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


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

Show this message and exit.
