gcloud: Wed May 24 10:23:00 UTC 2023

gcloud/compute/interconnects/attachments/dedicated/create

@@ -11,7 +11,8 @@ SYNOPSIS
         [--customer-router-ipv6-interface-id=PEER_INTERFACE_ID]
         [--description=DESCRIPTION] [--enable-admin] [--encryption=ENCRYPTION]
         [--ipsec-internal-addresses=[ADDRESSES]] [--mtu=MTU] [--region=REGION]
-        [--stack-type=STACK_TYPE] [--vlan=VLAN] [GCLOUD_WIDE_FLAG ...]
+        [--stack-type=STACK_TYPE] [--subnet-length=SUBNET_LENGTH] [--vlan=VLAN]
+        [GCLOUD_WIDE_FLAG ...]
 
 DESCRIPTION
     gcloud compute interconnects attachments dedicated create is used to create
@@ -73,11 +74,11 @@ OPTIONAL FLAGS
         Up to 16 candidate prefixes that can be used to restrict the allocation
         of cloudRouterIpAddress and customerRouterIpAddress for this
         attachment. All prefixes must be within link-local address space.
-        Google will attempt to select an unused /29 from the supplied candidate
-        subnet(s), or all of link-local space if no subnets supplied. Google
-        will not re-use a /29 already in-use by your project, even if it's
-        contained in one of the candidate subnets. The request will fail if all
-        /29s within the candidate subnets are in use at Google's edge.
+        Google attempts to select an unused subnet of SUBNET_LENGTH from the
+        supplied candidate subnet(s), or all of link-local space if no subnets
+        supplied. Google does not re-use a subnet already in-use by your
+        project, even if it's contained in one of the candidate subnets. The
+        request fails if all candidate subnets are in use at Google's edge.
 
      --cloud-router-ipv6-interface-id=INTERFACE_ID
         If supplied, the interface id (index within the subnet) to be used for
@@ -166,6 +167,14 @@ OPTIONAL FLAGS
          IPV4_ONLY
             Only IPv4 protocol is enabled on this attachment.
 
+     --subnet-length=SUBNET_LENGTH
+        The length of the IPv4 subnet mask for this attachment. 29 is the
+        default value, except for attachments on Cross-Cloud Interconnects
+        whose remote location's "constraints.subnetLengthRange" field specifies
+        a minimum subnet length of 30. In that case, the default value is 30.
+        The default value is recommended when there's no requirement on the
+        subnet length. SUBNET_LENGTH must be one of: 29, 30.
+
      --vlan=VLAN
         Desired VLAN for this attachment, in the range 2-4093. If not supplied,
         Google will automatically select a VLAN.

gcloud/compute/interconnects/create

@@ -2,11 +2,12 @@ NAME
     gcloud compute interconnects create - create a Compute Engine interconnect
 
 SYNOPSIS
-    gcloud compute interconnects create NAME --customer-name=CUSTOMER_NAME
+    gcloud compute interconnects create NAME
         --interconnect-type=INTERCONNECT_TYPE --link-type=LINK_TYPE
         --location=LOCATION --requested-link-count=REQUESTED_LINK_COUNT
-        [--admin-enabled] [--description=DESCRIPTION]
-        [--noc-contact-email=NOC_CONTACT_EMAIL] [GCLOUD_WIDE_FLAG ...]
+        [--admin-enabled] [--customer-name=CUSTOMER_NAME]
+        [--description=DESCRIPTION] [--noc-contact-email=NOC_CONTACT_EMAIL]
+        [--remote-location=REMOTE_LOCATION] [GCLOUD_WIDE_FLAG ...]
 
 DESCRIPTION
     gcloud compute interconnects create is used to create interconnects. An
@@ -26,15 +27,21 @@ EXAMPLES
             --noc-contact-email=noc@example.com \
             --description="Example interconnect"
 
+    To create a Cross-Cloud Interconnect, run:
+
+        $ gcloud compute interconnects create example-cc-interconnect \
+            --interconnect-type=DEDICATED \
+            --link-type=LINK_TYPE_ETHERNET_10G_LR \
+            --location=example-zone1-1 --requested-link-count=1 \
+            --remote-location=example-remote-location \
+            --noc-contact-email=noc@example.com \
+            --description="Example Cross-Cloud Interconnect"
+
 POSITIONAL ARGUMENTS
      NAME
         Name of the interconnect to create.
 
 REQUIRED FLAGS
-     --customer-name=CUSTOMER_NAME
-        Customer name to put in the Letter of Authorization as the party
-        authorized to request an interconnect.
-
      --interconnect-type=INTERCONNECT_TYPE
         Type of the interconnect. INTERCONNECT_TYPE must be one of:
 
@@ -66,6 +73,12 @@ OPTIONAL FLAGS
         operational and will carry traffic across any functioning linked
         interconnect attachments. Use --no-admin-enabled to disable it.
 
+     --customer-name=CUSTOMER_NAME
+        Customer name to put in the Letter of Authorization as the party
+        authorized to request an interconnect. This field is required for most
+        interconnects, however it is prohibited when creating a Cross-Cloud
+        Interconnect.
+
      --description=DESCRIPTION
         An optional, textual description for the interconnect.
 
@@ -73,6 +86,12 @@ OPTIONAL FLAGS
         Email address to contact the customer NOC for operations and
         maintenance notifications regarding this interconnect.
 
+     --remote-location=REMOTE_LOCATION
+        The remote location for a Cross-Cloud Interconnect. The remote
+        locations can be listed by using the gcloud compute interconnects
+        remote-locations list command to find the appropriate remote location
+        to use when creating a Cross-Cloud Interconnect.
+
 GCLOUD WIDE FLAGS
     These flags are available to all commands: --access-token-file, --account,
     --billing-project, --configuration, --flags-file, --flatten, --format,

gcloud/compute/interconnects/help

@@ -29,6 +29,10 @@ GROUPS
      locations
         Read and manipulate Compute Engine interconnect locations.
 
+     remote-locations
+        Read and manipulate Google Compute Engine interconnect remote
+        locations.
+
 COMMANDS
     COMMAND is one of the following:
 

gcloud/compute/interconnects/remote-locations/describe

@@ -0,0 +1,37 @@
+NAME
+    gcloud compute interconnects remote-locations describe - describe a Google
+        Compute Engine interconnect remote location
+
+SYNOPSIS
+    gcloud compute interconnects remote-locations describe NAME
+        [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    Displays all data associated with Google Compute Engine interconnect remote
+    location in a project.
+
+EXAMPLES
+    Example of usage:
+
+        $ gcloud compute interconnects remote-locations describe \
+            my-remote-location
+
+POSITIONAL ARGUMENTS
+     NAME
+        Name of the Cloud Interconnect remote location to describe.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+NOTES
+    These variants are also available:
+
+        $ gcloud alpha compute interconnects remote-locations describe
+
+        $ gcloud beta compute interconnects remote-locations describe
+

gcloud/compute/interconnects/remote-locations/help

@@ -0,0 +1,32 @@
+NAME
+    gcloud compute interconnects remote-locations - read and manipulate Google
+        Compute Engine interconnect remote locations
+
+SYNOPSIS
+    gcloud compute interconnects remote-locations COMMAND
+        [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    Read and manipulate Cloud Interconnect remote locations.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --help.
+
+    Run $ gcloud help for details.
+
+COMMANDS
+    COMMAND is one of the following:
+
+     describe
+        Describe a Google Compute Engine interconnect remote location.
+
+     list
+        List Google Compute Engine Cloud Interconnect remote locations.
+
+NOTES
+    These variants are also available:
+
+        $ gcloud alpha compute interconnects remote-locations
+
+        $ gcloud beta compute interconnects remote-locations
+

gcloud/compute/interconnects/remote-locations/list

@@ -0,0 +1,71 @@
+NAME
+    gcloud compute interconnects remote-locations list - list Google Compute
+        Engine Cloud Interconnect remote locations
+
+SYNOPSIS
+    gcloud compute interconnects remote-locations list [--filter=EXPRESSION]
+        [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri]
+        [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    gcloud compute interconnects remote-locations list displays all Google
+    Compute Engine Cloud Interconnect remote locations in a project.
+
+EXAMPLES
+    To list all Cloud Interconnect remote locations in a project in table form,
+    run:
+
+        $ gcloud compute interconnects remote-locations list
+
+    To list the URIs of all Cloud Interconnect remote locations in a project,
+    run:
+
+        $ gcloud compute interconnects remote-locations list --uri
+
+LIST COMMAND FLAGS
+     --filter=EXPRESSION
+        Apply a Boolean filter EXPRESSION to each resource item to be listed.
+        If the expression evaluates True, then that item is listed. For more
+        details and examples of filter expressions, run $ gcloud topic filters.
+        This flag interacts with other flags that are applied in this order:
+        --flatten, --sort-by, --filter, --limit.
+
+     --limit=LIMIT
+        Maximum number of resources to list. The default is unlimited. This
+        flag interacts with other flags that are applied in this order:
+        --flatten, --sort-by, --filter, --limit.
+
+     --page-size=PAGE_SIZE
+        Some services group resource list output into pages. This flag
+        specifies the maximum number of resources per page. The default is
+        determined by the service if it supports paging, otherwise it is
+        unlimited (no paging). Paging may be applied before or after --filter
+        and --limit depending on the service.
+
+     --sort-by=[FIELD,...]
+        Comma-separated list of resource field key names to sort by. The
+        default order is ascending. Prefix a field with ``~'' for descending
+        order on that field. This flag interacts with other flags that are
+        applied in this order: --flatten, --sort-by, --filter, --limit.
+
+     --uri
+        Print a list of resource URIs instead of the default output, and change
+        the command output to a list of URIs. If this flag is used with
+        --format, the formatting is applied on this URI list. To display URIs
+        alongside other keys instead, use the uri() transform.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+NOTES
+    These variants are also available:
+
+        $ gcloud alpha compute interconnects remote-locations list
+
+        $ gcloud beta compute interconnects remote-locations list
+