gcloud: Wed Apr 30 11:00:00 UTC 2025

gcloud/beta/compute/interconnects/groups/add-members

@@ -0,0 +1,46 @@
+NAME
+    gcloud beta compute interconnects groups add-members - add member
+        interconnects to a Compute Engine interconnect group
+
+SYNOPSIS
+    gcloud beta compute interconnects groups add-members NAME
+        --interconnects=[INTERCONNECT,...] [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    (BETA) gcloud beta compute interconnects groups add-members is used to add
+    member interconnects to an interconnect group.
+
+    For an example, refer to the EXAMPLES section below.
+
+EXAMPLES
+    To add interconnects interconnect1 and interconnect2 to interconnect group
+    example-interconnect-group, run:
+
+        $ gcloud beta compute interconnects groups add-members \
+            example-interconnect-group \
+            --interconnects=interconnect1,interconnect2
+
+POSITIONAL ARGUMENTS
+     NAME
+        Name of the interconnect group to update.
+
+REQUIRED FLAGS
+     --interconnects=[INTERCONNECT,...]
+        Member interconnects to add to or remove from the interconnect group.
+
+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 beta and might change without notice. These
+    variants are also available:
+
+        $ gcloud compute interconnects groups add-members
+
+        $ gcloud alpha compute interconnects groups add-members
+

gcloud/beta/compute/interconnects/groups/create

@@ -0,0 +1,68 @@
+NAME
+    gcloud beta compute interconnects groups create - create a Compute Engine
+        interconnect group
+
+SYNOPSIS
+    gcloud beta compute interconnects groups create NAME
+        --intended-topology-capability=INTENDED_TOPOLOGY_CAPABILITY
+        [--description=DESCRIPTION] [--interconnects=[INTERCONNECT,...]]
+        [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    (BETA) gcloud beta compute interconnects groups create is used to create
+    interconnect groups. An interconnect group connects a set of redundant
+    interconnects between Google and the customer.
+
+    For an example, refer to the EXAMPLES section below.
+
+EXAMPLES
+    To create an interconnect group capable of PRODUCTION_CRITICAL, run:
+
+        $ gcloud beta compute interconnects groups create \
+            example-interconnect-group \
+            --intended-topology-capability=PRODUCTION_CRITICAL \
+            --description="Example interconnect group"
+
+    It is easy to add members to an existing interconnect group after creation
+    using the add-members command.
+
+    To create an interconnect group capable of PRODUCTION_NON_CRITICAL, with
+    two members at creation time, run:
+
+        $ gcloud beta compute interconnects groups create \
+            example-interconnect-group \
+            --intended-topology-capability=PRODUCTION_NON_CRITICAL \
+            --interconnects=interconnect-1,interconnect-2
+
+POSITIONAL ARGUMENTS
+     NAME
+        Name of the interconnect group to create.
+
+REQUIRED FLAGS
+     --intended-topology-capability=INTENDED_TOPOLOGY_CAPABILITY
+        The reliability the user intends this group to be capable of, in terms
+        of the Interconnect product SLAs.
+
+OPTIONAL FLAGS
+     --description=DESCRIPTION
+        An optional, textual description for the interconnect group.
+
+     --interconnects=[INTERCONNECT,...]
+        Member interconnects to add to the interconnect group initially.
+
+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 beta and might change without notice. These
+    variants are also available:
+
+        $ gcloud compute interconnects groups create
+
+        $ gcloud alpha compute interconnects groups create
+

gcloud/beta/compute/interconnects/groups/create-members

@@ -0,0 +1,138 @@
+NAME
+    gcloud beta compute interconnects groups create-members - create new member
+        interconnects in a Compute Engine interconnect group
+
+SYNOPSIS
+    gcloud beta compute interconnects groups create-members NAME
+        --interconnect=[INTERCONNECT,...] [--admin-enabled]
+        [--customer-name=CUSTOMER_NAME] [--description=DESCRIPTION]
+        [--facility=FACILITY]
+        [--intent-mismatch-behavior=INTENT_MISMATCH_BEHAVIOR]
+        [--interconnect-type=INTERCONNECT_TYPE] [--link-type=LINK_TYPE]
+        [--noc-contact-email=NOC_CONTACT_EMAIL]
+        [--requested-features=[FEATURES,...]]
+        [--requested-link-count=REQUESTED_LINK_COUNT] [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    (BETA) gcloud beta compute interconnects groups create-members is used to
+    create new member interconnects in an interconnect group.
+
+    For an example, refer to the EXAMPLES section below.
+
+EXAMPLES
+    To create interconnects interconnect1 and interconnect2 in interconnect
+    group example-interconnect-group, run:
+
+        $ gcloud beta compute interconnects groups create-members \
+            example-interconnect-group --interconnect-type=DEDICATED \
+            --link-type=LINK_TYPE_ETHERNET_10G_LR --requested-link-count=1 \
+            --facility=iad-1 --interconnect="name=interconnect1" \
+            --interconnect="name=interconnect2"
+
+POSITIONAL ARGUMENTS
+     NAME
+        Name of the interconnect group to create members.
+
+REQUIRED FLAGS
+     --interconnect=[INTERCONNECT,...]
+        New member interconnects to create in the interconnect group. To create
+        multiple interconnects, this flag should be specified multiple times.
+
+        Each interconnect takes in the same set of flags as the gcloud compute
+        interconnects create command, except instead of a location, a facility
+        must be specified. These flags are defined as a comma separated list of
+        flag=value pairs.
+
+        Example: --interconnect
+        name=interconnect1,facility=iad-1,description="my
+        interconnect",link-type=LINK_TYPE_ETHERNET_10G_LR,requested-link-count=1,
+        interconnect-type=DEDICATED,admin-enabled,
+        noc-contact-email=noc@google.com,customer-name=customer-name
+        requested-features=MACSEC:CROSS_SITE_NETWORK
+
+        Note that for multiple requested-features, use a colon (:) as the
+        delimiter, as the comma is used to separate the flags. Similarly, if
+        you need to use a comma in another flag value, you should set an
+        alternative delimiter for the --interconnect flag. Run gcloud topic
+        escaping for more information.
+
+OPTIONAL FLAGS
+     --admin-enabled
+        Administrative status of the interconnect. If not provided on creation,
+        defaults to enabled. When this is enabled, the interconnect is
+        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.
+
+     --facility=FACILITY
+        The facility (zone free location) to create the interconnect in.
+
+     --intent-mismatch-behavior=INTENT_MISMATCH_BEHAVIOR
+        The behavior when the intent of the interconnect group does not match
+        the topology capability of the member interconnects.
+        INTENT_MISMATCH_BEHAVIOR must be one of: REJECT, CREATE.
+
+     --interconnect-type=INTERCONNECT_TYPE
+        Type of the interconnect. INTERCONNECT_TYPE must be one of:
+
+         DEDICATED
+            Dedicated private interconnect.
+         PARTNER
+            Partner interconnect. Only available to approved partners.
+
+     --link-type=LINK_TYPE
+        Type of the link for the interconnect. LINK_TYPE must be one of:
+
+         LINK_TYPE_ETHERNET_100G_LR
+            100Gbps Ethernet, LR Optics.
+         LINK_TYPE_ETHERNET_10G_LR
+            10Gbps Ethernet, LR Optics.
+         LINK_TYPE_ETHERNET_400G_LR4
+            400Gbps Ethernet, LR4 Optics.
+
+     --noc-contact-email=NOC_CONTACT_EMAIL
+        Email address to contact the customer NOC for operations and
+        maintenance notifications regarding this interconnect.
+
+     --requested-features=[FEATURES,...]
+        List of features requested for this interconnect. FEATURES must be one
+        of:
+
+         CROSS_SITE_NETWORK
+            If specified then the interconnect is created on Cross-Site Network
+            capable hardware ports. This parameter can only be provided during
+            interconnect INSERT and cannot be changed using interconnect PATCH.
+         MACSEC
+            If specified then the interconnect is created on MACsec capable
+            hardware ports. If not specified, the interconnect is created on
+            non-MACsec capable ports first, if available. This parameter can
+            only be provided during interconnect INSERT and cannot be changed
+            using interconnect PATCH.
+
+     --requested-link-count=REQUESTED_LINK_COUNT
+        Target number of physical links in the link bundle.
+
+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 beta and might change without notice. These
+    variants are also available:
+
+        $ gcloud compute interconnects groups create-members
+
+        $ gcloud alpha compute interconnects groups create-members
+

gcloud/beta/compute/interconnects/groups/delete

@@ -0,0 +1,43 @@
+NAME
+    gcloud beta compute interconnects groups delete - delete Compute Engine
+        interconnect groups
+
+SYNOPSIS
+    gcloud beta compute interconnects groups delete NAME [NAME ...]
+        [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    (BETA) gcloud beta compute interconnects groups delete is used to delete
+    interconnect groups.
+
+    For an example, refer to the EXAMPLES section below.
+
+EXAMPLES
+    To delete an interconnect group, run:
+
+        $ gcloud beta compute interconnects groups delete \
+            example-interconnect-group"
+
+    Although not shown in this example, you can delete multiple interconnect
+    groups in a single command.
+
+POSITIONAL ARGUMENTS
+     NAME [NAME ...]
+        Names of the interconnect groups 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 beta and might change without notice. These
+    variants are also available:
+
+        $ gcloud compute interconnects groups delete
+
+        $ gcloud alpha compute interconnects groups delete
+

gcloud/beta/compute/interconnects/groups/describe

@@ -0,0 +1,40 @@
+NAME
+    gcloud beta compute interconnects groups describe - describe a Compute
+        Engine interconnect group
+
+SYNOPSIS
+    gcloud beta compute interconnects groups describe NAME
+        [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    (BETA) gcloud beta compute interconnects groups describe is used to
+    describe an interconnect group.
+
+    For an example, refer to the EXAMPLES section below.
+
+EXAMPLES
+    To describe interconnect group example-interconnect-group, run:
+
+        $ gcloud beta compute interconnects groups describe \
+            example-interconnect-group
+
+POSITIONAL ARGUMENTS
+     NAME
+        Name of the interconnect group 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
+    This command is currently in beta and might change without notice. These
+    variants are also available:
+
+        $ gcloud compute interconnects groups describe
+
+        $ gcloud alpha compute interconnects groups describe
+

gcloud/beta/compute/interconnects/groups/get-operational-status

@@ -0,0 +1,41 @@
+NAME
+    gcloud beta compute interconnects groups get-operational-status - get the
+        operational status of a Compute Engine interconnect group
+
+SYNOPSIS
+    gcloud beta compute interconnects groups get-operational-status NAME
+        [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    (BETA) gcloud beta compute interconnects groups get-operational-status is
+    used to get the operational status of an interconnect group.
+
+    For an example, refer to the EXAMPLES section below.
+
+EXAMPLES
+    To get the operational status of interconnect group
+    example-interconnect-group, run:
+
+        $ gcloud beta compute interconnects groups get-operational-status \
+            example-interconnect-group
+
+POSITIONAL ARGUMENTS
+     NAME
+        Name of the interconnect group to get operational status.
+
+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 beta and might change without notice. These
+    variants are also available:
+
+        $ gcloud compute interconnects groups get-operational-status
+
+        $ gcloud alpha compute interconnects groups get-operational-status
+

gcloud/beta/compute/interconnects/groups/help

@@ -0,0 +1,56 @@
+NAME
+    gcloud beta compute interconnects groups - create or manipulate
+        interconnect groups
+
+SYNOPSIS
+    gcloud beta compute interconnects groups COMMAND [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    (BETA) Create or manipulate interconnect groups.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --help.
+
+    Run $ gcloud help for details.
+
+COMMANDS
+    COMMAND is one of the following:
+
+     add-members
+        (BETA) Add member interconnects to a Compute Engine interconnect group.
+
+     create
+        (BETA) Create a Compute Engine interconnect group.
+
+     create-members
+        (BETA) Create new member interconnects in a Compute Engine interconnect
+        group.
+
+     delete
+        (BETA) Delete Compute Engine interconnect groups.
+
+     describe
+        (BETA) Describe a Compute Engine interconnect group.
+
+     get-operational-status
+        (BETA) Get the operational status of a Compute Engine interconnect
+        group.
+
+     list
+        (BETA) List interconnect groups.
+
+     remove-members
+        (BETA) Remove member interconnects from a Compute Engine interconnect
+        group.
+
+     update
+        (BETA) Update a Compute Engine interconnect group.
+
+NOTES
+    This command is currently in beta and might change without notice. These
+    variants are also available:
+
+        $ gcloud compute interconnects groups
+
+        $ gcloud alpha compute interconnects groups
+

gcloud/beta/compute/interconnects/groups/list

@@ -0,0 +1,67 @@
+NAME
+    gcloud beta compute interconnects groups list - list interconnect groups
+
+SYNOPSIS
+    gcloud beta compute interconnects groups list [--filter=EXPRESSION]
+        [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri]
+        [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    (BETA) gcloud beta compute interconnects groups list is used to list
+    interconnect groups.
+
+    For an example, refer to the EXAMPLES section below.
+
+EXAMPLES
+    To list interconnect groups, run:
+
+        $ gcloud beta compute interconnects groups list
+
+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 beta and might change without notice. These
+    variants are also available:
+
+        $ gcloud compute interconnects groups list
+
+        $ gcloud alpha compute interconnects groups list
+

gcloud/beta/compute/interconnects/groups/remove-members

@@ -0,0 +1,46 @@
+NAME
+    gcloud beta compute interconnects groups remove-members - remove member
+        interconnects from a Compute Engine interconnect group
+
+SYNOPSIS
+    gcloud beta compute interconnects groups remove-members NAME
+        --interconnects=[INTERCONNECT,...] [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    (BETA) gcloud beta compute interconnects groups remove-members is used to
+    remove member interconnects from an interconnect group.
+
+    For an example, refer to the EXAMPLES section below.
+
+EXAMPLES
+    To remove interconnects interconnect1 and interconnect2 from interconnect
+    group example-interconnect-group, run:
+
+        $ gcloud beta compute interconnects groups remove-members \
+            example-interconnect-group \
+            --interconnects=interconnect1,interconnect2
+
+POSITIONAL ARGUMENTS
+     NAME
+        Name of the interconnect group to update.
+
+REQUIRED FLAGS
+     --interconnects=[INTERCONNECT,...]
+        Member interconnects to add to or remove from the interconnect group.
+
+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 beta and might change without notice. These
+    variants are also available:
+
+        $ gcloud compute interconnects groups remove-members
+
+        $ gcloud alpha compute interconnects groups remove-members
+

gcloud/beta/compute/interconnects/groups/update

@@ -0,0 +1,73 @@
+NAME
+    gcloud beta compute interconnects groups update - update a Compute Engine
+        interconnect group
+
+SYNOPSIS
+    gcloud beta compute interconnects groups update NAME
+        [--description=DESCRIPTION]
+        [--intended-topology-capability=INTENDED_TOPOLOGY_CAPABILITY]
+        [--interconnects=[INTERCONNECT,...]] [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    (BETA) gcloud beta compute interconnects groups update is used to update
+    interconnect groups.
+
+    For an example, refer to the EXAMPLES section below.
+
+EXAMPLES
+    To update an interconnect group example-interconnect-group's intended
+    topology capability to PRODUCTION_CRITICAL, run:
+
+        $ gcloud beta compute interconnects groups update \
+            example-interconnect-group \
+            --intended-topology-capability=PRODUCTION_CRITICAL
+
+    To update an interconnect group example-interconnect-group's description to
+    "example interconnect group description", run:
+
+        $ gcloud beta compute interconnects groups update \
+            example-interconnect-group \
+            --description="example interconnect group description"
+
+    To update an interconnect group example-interconnect-group's member
+    interconnects to interconnect-1 and interconnect-2, run:
+
+        $ gcloud beta compute interconnects groups update \
+            example-interconnect-group \
+            --interconnects=interconnect-1,interconnect-2
+
+    Although you can add or remove member interconnects using this command, it
+    is recommended to add or remove member interconnects using the add-members
+    and remove-members commands.
+
+POSITIONAL ARGUMENTS
+     NAME
+        Name of the interconnect group to update.
+
+FLAGS
+     --description=DESCRIPTION
+        An optional, textual description for the interconnect group.
+
+     --intended-topology-capability=INTENDED_TOPOLOGY_CAPABILITY
+        The reliability the user intends this group to be capable of, in terms
+        of the Interconnect product SLAs.
+
+     --interconnects=[INTERCONNECT,...]
+        Member interconnects to set the interconnect group to contain.
+
+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 beta and might change without notice. These
+    variants are also available:
+
+        $ gcloud compute interconnects groups update
+
+        $ gcloud alpha compute interconnects groups update
+