gcloud: Wed Jan 8 10:03:00 UTC 2025

gcloud/alpha/compute/interconnects/attachments/dedicated/create

@@ -60,6 +60,8 @@ OPTIONAL FLAGS
             20 Gbit/s
          50g
             50 Gbit/s
+         100g
+            100 Gbit/s
 
      --candidate-ipv6-subnets=[IPV6_SUBNET,...]
         The candididate-ipv6-subnets field is not available.

gcloud/alpha/compute/interconnects/attachments/dedicated/update

@@ -50,6 +50,8 @@ FLAGS
             20 Gbit/s
          50g
             50 Gbit/s
+         100g
+            100 Gbit/s
 
      --candidate-ipv6-subnets=[IPV6_SUBNET,...]
         The candididate-ipv6-subnets field is not available.

gcloud/alpha/compute/interconnects/cross-site-networks/create

@@ -4,7 +4,7 @@ NAME
 
 SYNOPSIS
     gcloud alpha compute interconnects cross-site-networks create NAME
-        --project=PROJECT [--description=DESCRIPTION] [GCLOUD_WIDE_FLAG ...]
+        [--description=DESCRIPTION] [GCLOUD_WIDE_FLAG ...]
 
 DESCRIPTION
     (ALPHA) gcloud alpha compute interconnects cross-site-networks create is
@@ -22,13 +22,9 @@ EXAMPLES
 
 POSITIONAL ARGUMENTS
      NAME
-        Name of the cross site network to create.
+        Name of the crossSiteNetwork to create.
 
-REQUIRED FLAGS
-     --project=PROJECT
-        A project for the cross site network.
-
-OPTIONAL FLAGS
+FLAGS
      --description=DESCRIPTION
         An optional, textual description for the cross site network.
 

gcloud/alpha/compute/interconnects/cross-site-networks/delete

@@ -0,0 +1,30 @@
+NAME
+    gcloud alpha compute interconnects cross-site-networks delete - delete
+        Compute Engine cross site networks
+
+SYNOPSIS
+    gcloud alpha compute interconnects cross-site-networks delete NAME
+        [NAME ...] [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    (ALPHA) gcloud alpha compute interconnects cross-site-networks delete
+    deletes Compute Engine cross site networks.
+
+POSITIONAL ARGUMENTS
+     NAME [NAME ...]
+        Names of the crossSiteNetworks to delete.
+
+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
+    This command is currently in alpha and might change without notice. If this
+    command fails with API permission errors despite specifying the correct
+    project, you might be trying to access an API with an invitation-only early
+    access allowlist.
+

gcloud/alpha/compute/interconnects/cross-site-networks/help

@@ -20,6 +20,15 @@ COMMANDS
      create
         (ALPHA) Create a Compute Engine cross site network.
 
+     delete
+        (ALPHA) Delete Compute Engine cross site networks.
+
+     list
+        (ALPHA) List Google Compute Engine cross site networks.
+
+     update
+        (ALPHA) Update a Compute Engine cross site network.
+
 NOTES
     This command is currently in alpha and might change without notice. If this
     command fails with API permission errors despite specifying the correct

gcloud/alpha/compute/interconnects/cross-site-networks/list

@@ -0,0 +1,68 @@
+NAME
+    gcloud alpha compute interconnects cross-site-networks list - list Google
+        Compute Engine cross site networks
+
+SYNOPSIS
+    gcloud alpha compute interconnects cross-site-networks list
+        [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE]
+        [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    (ALPHA) gcloud alpha compute interconnects cross-site-networks list
+    displays all Google Compute Engine cross site networks in a project.
+
+EXAMPLES
+    To list all cross site networks in a project in table form, run:
+
+        $ gcloud alpha compute interconnects cross-site-networks list
+
+    To list the URIs of all cross site networks in a project, run:
+
+        $ gcloud alpha compute interconnects cross-site-networks 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
+    This command is currently in alpha and might change without notice. If this
+    command fails with API permission errors despite specifying the correct
+    project, you might be trying to access an API with an invitation-only early
+    access allowlist.
+

gcloud/alpha/compute/interconnects/cross-site-networks/update

@@ -0,0 +1,35 @@
+NAME
+    gcloud alpha compute interconnects cross-site-networks update - update a
+        Compute Engine cross site network
+
+SYNOPSIS
+    gcloud alpha compute interconnects cross-site-networks update NAME
+        [--description=DESCRIPTION] [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    (ALPHA) gcloud alpha compute interconnects cross-site-networks update is
+    used to update cross site networks. A cross site network encapsulates wire
+    groups.
+
+POSITIONAL ARGUMENTS
+     NAME
+        Name of the crossSiteNetwork to update.
+
+FLAGS
+     --description=DESCRIPTION
+        An optional, textual description for the cross site network.
+
+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
+    This command is currently in alpha and might change without notice. If this
+    command fails with API permission errors despite specifying the correct
+    project, you might be trying to access an API with an invitation-only early
+    access allowlist.
+

gcloud/alpha/compute/interconnects/help

@@ -43,6 +43,9 @@ GROUPS
         (ALPHA) Read and manipulate Google Compute Engine interconnect remote
         locations.
 
+     wire-groups
+        (ALPHA) Create or manipulate wire groups.
+
 COMMANDS
     COMMAND is one of the following:
 

gcloud/alpha/compute/interconnects/wire-groups/create

@@ -0,0 +1,106 @@
+NAME
+    gcloud alpha compute interconnects wire-groups create - create a Compute
+        Engine wire group
+
+SYNOPSIS
+    gcloud alpha compute interconnects wire-groups create NAME
+        --bandwidth-unmetered=BANDWIDTH_UNMETERED
+        --cross-site-network=CROSS_SITE_NETWORK --type=TYPE
+        [--admin-enabled=ADMIN_ENABLED]
+        [--bandwidth-allocation=BANDWIDTH_ALLOCATION]
+        [--bandwidth-metered=BANDWIDTH_METERED] [--description=DESCRIPTION]
+        [--fault-response=FAULT_RESPONSE]
+        [--network-service-class=NETWORK_SERVICE_CLASS]
+        [--validate-only=VALIDATE_ONLY] [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    (ALPHA) gcloud alpha compute interconnects wire-groups create is used to
+    create wire groups. A wire group represents a group of redundant wires
+    between interconnects in two different metros. Each WireGroup belongs to a
+    CrossSiteNetwork.
+
+    For an example, refer to the EXAMPLES section below.
+
+EXAMPLES
+    To create a wire group, run:
+
+        $ gcloud alpha compute interconnects wire-groups create \
+            example-wire-group --project my-project \
+            --cross-site-network example-cross-site-network --type WIRE \
+            --bandwidth-unmetered 10g --network-service-class BRONZE \
+            --bandwidth-allocation ALLOCATE_PER_WIRE
+
+POSITIONAL ARGUMENTS
+     NAME
+        Name of the wire group to create.
+
+REQUIRED FLAGS
+     --bandwidth-unmetered=BANDWIDTH_UNMETERED
+        The amount of unmetered bandwidth to assign to the wire group.
+
+     --cross-site-network=CROSS_SITE_NETWORK
+        Name of the crossSiteNetwork to operate on.
+
+     --type=TYPE
+        The type for the wire group. TYPE must be one of:
+
+         BOX_AND_CROSS
+            Box and cross
+         REDUNDANT
+            Redundant
+         WIRE
+            Wire
+
+OPTIONAL FLAGS
+     --admin-enabled=ADMIN_ENABLED
+        Set admin-enabled on the wire group.
+
+     --bandwidth-allocation=BANDWIDTH_ALLOCATION
+        The bandwidth allocation for the wire group. BANDWIDTH_ALLOCATION must
+        be one of:
+
+         ALLOCATE_PER_WIRE
+            Allocate per wire.
+         SHARED_WITH_WIRE_GROUP
+            Shared with wire group.
+
+     --bandwidth-metered=BANDWIDTH_METERED
+        The amount of metered bandwidth to assign to the wire group.
+
+     --description=DESCRIPTION
+        An optional, textual description for the wire group.
+
+     --fault-response=FAULT_RESPONSE
+        The fault response for the wire group. FAULT_RESPONSE must be one of:
+
+         DISABLED_PORT
+            Disabled port
+         NONE
+            None
+
+     --network-service-class=NETWORK_SERVICE_CLASS
+        The network service class for the wire group. NETWORK_SERVICE_CLASS
+        must be one of:
+
+         BRONZE
+            Bronze.
+         GOLD
+            Gold.
+
+     --validate-only=VALIDATE_ONLY
+        Only validates the configuration, but does not create it.
+
+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
+    This command is currently in alpha and might change without notice. If this
+    command fails with API permission errors despite specifying the correct
+    project, you might be trying to access an API with an invitation-only early
+    access allowlist.
+

gcloud/alpha/compute/interconnects/wire-groups/help

@@ -0,0 +1,28 @@
+NAME
+    gcloud alpha compute interconnects wire-groups - create or manipulate wire
+        groups
+
+SYNOPSIS
+    gcloud alpha compute interconnects wire-groups COMMAND
+        [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    (ALPHA) Create or manipulate wire groups.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --help.
+
+    Run $ gcloud help for details.
+
+COMMANDS
+    COMMAND is one of the following:
+
+     create
+        (ALPHA) Create a Compute Engine wire group.
+
+NOTES
+    This command is currently in alpha and might change without notice. If this
+    command fails with API permission errors despite specifying the correct
+    project, you might be trying to access an API with an invitation-only early
+    access allowlist.
+