POSITIONAL ARGUMENTS

NAME

Name of the interconnect attachment to create.

REQUIRED FLAGS

--edge-availability-domain=AVAILABILITY_DOMAIN

Desired edge availability domain for this attachment: availability-domain-1, availability-domain-2, any.
In each metro where the Partner can connect to Google, there are two sets of redundant hardware. These sets are described as edge availability domain 1 and 2. Within a metro, Google will only schedule maintenance in one availability domain at a time. This guarantee does not apply to availability domains outside the metro; Google may perform maintenance in (say) New York availability domain 1 at the same time as Chicago availability domain 1.
AVAILABILITY_DOMAIN must be one of:

any

Any Availability Domain

availability-domain-1

Edge Availability Domain 1

availability-domain-2

Edge Availability Domain 2

--router=ROUTER

The Google Cloud Router to use for dynamic routing.

OPTIONAL FLAGS

--description=DESCRIPTION

Human-readable plain-text description of attachment.

--enable-admin

Administrative status of the interconnect attachment. If not provided on creation, defaults to disabled. When this is enabled, the attachment is operational and will carry traffic. Use --no-enable-admin to disable it.

--region=REGION

Region of the interconnect attachment to create. If not specified, you may be prompted to select a region.
To avoid prompting when this flag is omitted, you can set the compute/region property:

$ gcloud config set compute/region REGION

A list of regions can be fetched by running:

$ gcloud compute regions list

To unset the property, run:

$ gcloud config unset compute/region

Alternatively, the region can be stored in the environment variable CLOUDSDK_COMPUTE_REGION.

GCLOUD WIDE FLAGS

NOTES

$ gcloud compute interconnects attachments partner create $ gcloud beta compute interconnects attachments partner create