create
******


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

Creates a new tag namespace in the specified compartment.

You must specify the compartment ID in the request object (remember
that the tenancy is simply the root compartment).

You must also specify a *name* for the namespace, which must be unique
across all namespaces in your tenancy and cannot be changed. The name
can contain any ASCII character except the space (_) or period (.).
Names are case insensitive. That means, for example, "myNamespace" and
"mynamespace" are not allowed in the same tenancy. Once you created a
namespace, you cannot change the name. If you specify a name that's
already in use in the tenancy, a 409 error is returned.

You must also specify a *description* for the namespace. It does not
have to be unique, and you can change it with UpdateTagNamespace.

Tag namespaces cannot be deleted, but they can be retired. See
Retiring Key Definitions and Namespace Definitions for more
information.


Usage
=====

   oci iam tag-namespace create [OPTIONS]


Options
=======


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

The OCID of the tenancy containing the tag namespace. [required]


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

The name you assign to the tag namespace during creation. It must be
unique across all tag namespaces in the tenancy and cannot be changed.
[required]


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

The description you assign to the tag namespace during creation.
[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.


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