create
******


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

Creates a new tag in the specified tag namespace.

You must specify either the OCID or the name of the tag namespace that
will contain this tag definition.

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

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


Usage
=====

   oci iam tag create [OPTIONS]


Options
=======


--tag-namespace-id [text]
-------------------------

The OCID of the tag namespace. [required]


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

The name you assign to the tag during creation. The name must be
unique within the tag namespace and cannot be changed. [required]


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

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


--is-cost-tracking [boolean]
----------------------------

Indicates whether the tag is enabled for cost tracking.


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