"create"
********

* Description

* Usage

* Required Parameters

* Optional Parameters

* Global Parameters

* Example using required parameter


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

Creates a new security attribute in the specified security attribute
namespace.

The security attribute requires either the OCID or the name of the
security attribute namespace that will contain this security
attribute.

You must specify a *name* for the attribute, which must be unique
across all attributes in the security attribute namespace and cannot
be changed. The only valid characters for security attribute names
are: 0-9, A-Z, a-z, -, _ characters. Names are case insensitive. That
means, for example, “mySecurityAttribute” and “mysecurityattribute”
are not allowed in the same namespace. If you specify a name that’s
already in use in the security attribute namespace, a 409 error is
returned.

The security attribute must have a *description*. It does not have to
be unique, and you can change it with UpdateSecurityAttribute.

The security attribute must have a value type, which is specified with
a validator. Security attribute can use either a static value or a
list of possible values. Static values are entered by a user applying
the security attribute to a resource. Lists are created by the user
and the user must apply a value from the list. Lists are validated.


Usage
=====

   oci security-attribute security-attribute create [OPTIONS]


Required Parameters
===================

--description [text]

The description you assign to the security attribute during creation.

--name [text]

The name you assign to the security attribute during creation. This is
the security attribute key. The name must be unique within the
namespace and cannot be changed.

--security-attribute-namespace-id [text]

The OCID of the security attribute namespace.


Optional Parameters
===================

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

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

--validator [complex type]

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 [text]

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. Multiple
states can be specified, returning on the first state. For example, "
--wait-for-state" SUCCEEDED "--wait-for-state" FAILED would return on
whichever lifecycle state is reached first. If timeout is reached, a
return code of 2 is returned. For any other error, a return code of 1
is returned.

Accepted values are:

   ACTIVE, DELETED, DELETING, INACTIVE

--wait-interval-seconds [integer]

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


Global Parameters
=================

Use "oci --help" for help on global parameters.

"--auth-purpose", "--auth", "--cert-bundle", "--cli-auto-prompt", "--
cli-rc-file", "--config-file", "--connection-timeout", "--debug", "--
defaults-file", "--endpoint", "--generate-full-command-json-input", "
--generate-param-json-input", "--help", "--latest-version", "--max-
retries", "--no-retry", "--opc-client-request-id", "--opc-request-id",
"--output", "--profile", "--proxy", "--query", "--raw-output", "--
read-timeout", "--realm-specific-endpoint", "--region", "--release-
info", "--request-id", "--version", "-?", "-d", "-h", "-i", "-v"


Example using required parameter
================================

Copy the following CLI commands into a file named example.sh. Run the
command by typing “bash example.sh” and replacing the example
parameters with your own.

Please note this sample will only work in the POSIX-compliant bash-
like shell. You need to set up the OCI configuration and appropriate
security policies before trying the examples.

       export compartment_id=<substitute-value-of-compartment_id> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/security-attribute/security-attribute-namespace/create.html#cmdoption-compartment-id
       export description=<substitute-value-of-description> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/security-attribute/security-attribute-namespace/create.html#cmdoption-description
       export name=<substitute-value-of-name> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/security-attribute/security-attribute-namespace/create.html#cmdoption-name

       security_attribute_namespace_id=$(oci security-attribute security-attribute-namespace create --compartment-id $compartment_id --description $description --name $name --query data.id --raw-output)

       oci security-attribute security-attribute create --description $description --name $name --security-attribute-namespace-id $security_attribute_namespace_id
