create
******


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

Attaches the specified DRG to the specified VCN. A VCN can be attached
to only one DRG at a time, and vice versa. The response includes a
*DrgAttachment* object with its own OCID. For more information about
DRGs, see Dynamic Routing Gateways (DRGs).

You may optionally specify a *display name* for the attachment,
otherwise a default is provided. It does not have to be unique, and
you can change it. Avoid entering confidential information.

For the purposes of access control, the DRG attachment is
automatically placed into the same compartment as the VCN. For more
information about compartments and access control, see Overview of the
IAM Service.


Usage
=====

   oci network drg-attachment create [OPTIONS]


Options
=======


--drg-id [text]
---------------

The OCID of the DRG. [required]


--vcn-id [text]
---------------

The OCID of the VCN. [required]


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

A user-friendly name. Does not have to be unique. Avoid entering
confidential information.


--route-table-id [text]
-----------------------

The OCID of the route table the DRG attachment will use.

If you don't specify a route table here, the DRG attachment is created
without an associated route table. The Networking service does NOT
automatically associate the attached VCN's default route table with
the DRG attachment.

For information about why you would associate a route table with a DRG
attachment, see Advanced Scenario: Transit Routing.


--wait-for-state [ATTACHING|ATTACHED|DETACHING|DETACHED]
--------------------------------------------------------

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. If
timeout is reached, a return code of 2 is returned. For any other
error, a return code of 1 is returned.


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