gcloud-help/gcloud/beta/compute/interconnects/attachments/dedicated/update

NAME
    gcloud beta compute interconnects attachments dedicated update - update a
        Compute Engine dedicated interconnect attachment

SYNOPSIS
    gcloud beta compute interconnects attachments dedicated update NAME
        [--bandwidth=BANDWIDTH]
        [--candidate-cloud-router-ipv6-address=CANDIDATE_CLOUD_ROUTER_IPV6_ADDRESS]
        [--candidate-customer-router-ipv6-address=CANDIDATE_CUSTOMER_ROUTER_IPV6_ADDRESS]
        [--candidate-ipv6-subnets=[IPV6_SUBNET,...]]
        [--cloud-router-ipv6-interface-id=INTERFACE_ID]
        [--customer-router-ipv6-interface-id=PEER_INTERFACE_ID]
        [--description=DESCRIPTION] [--enable-admin] [--mtu=MTU]
        [--region=REGION] [--stack-type=STACK_TYPE]
        [--update-labels=[KEY=VALUE,...]]
        [--clear-labels | --remove-labels=[KEY,...]] [GCLOUD_WIDE_FLAG ...]

DESCRIPTION
    (BETA) gcloud beta compute interconnects attachments dedicated update is
    used to update interconnect attachments. An interconnect attachment is what
    binds the underlying connectivity of an interconnect to a path into and out
    of the customer's cloud network.

POSITIONAL ARGUMENTS
     NAME
        Name of the interconnect attachment to patch.

FLAGS
     --bandwidth=BANDWIDTH
        Provisioned capacity of the attachment. BANDWIDTH must be one of:

         50m
            50 Mbit/s
         100m
            100 Mbit/s
         200m
            200 Mbit/s
         300m
            300 Mbit/s
         400m
            400 Mbit/s
         500m
            500 Mbit/s
         1g
            1 Gbit/s
         2g
            2 Gbit/s
         5g
            5 Gbit/s
         10g
            10 Gbit/s
         20g
            20 Gbit/s
         50g
            50 Gbit/s
         100g
            100 Gbit/s

     --candidate-cloud-router-ipv6-address=CANDIDATE_CLOUD_ROUTER_IPV6_ADDRESS
        Single IPv6 address + prefix length to be configured on the cloud
        router interface for this interconnect attachment. Example:
        2001:db8::1/125

     --candidate-customer-router-ipv6-address=CANDIDATE_CUSTOMER_ROUTER_IPV6_ADDRESS
        Single IPv6 address + prefix length to be configured on the customer
        router interface for this interconnect attachment. Example:
        2001:db8::2/125

     --candidate-ipv6-subnets=[IPV6_SUBNET,...]
        The candididate-ipv6-subnets field is not available.

     --cloud-router-ipv6-interface-id=INTERFACE_ID
        cloud-router-ipv6-interface-id field is not available.

     --customer-router-ipv6-interface-id=PEER_INTERFACE_ID
        customer-router-ipv6-interface-id field is not available.

     --description=DESCRIPTION
        Human-readable plain-text description of attachment.

     --enable-admin
        Administrative status of the interconnect attachment. When this is
        enabled, the attachment is operational and will carry traffic. Use
        --no-enable-admin to disable it.

     --mtu=MTU
        Maximum transmission unit (MTU) is the size of the largest IP packet
        passing through this interconnect attachment. Must be one of 1440,
        1460, 1500, or 8896. If not specified, the value will default to 1440.

     --region=REGION
        Region of the interconnect attachment to patch. If not specified, you
        might be prompted to select a region (interactive mode only).

        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.

     --stack-type=STACK_TYPE
        Stack type of the protocol(s) enabled on this interconnect attachment.
        STACK_TYPE must be one of:

         IPV4_IPV6
            Both IPv4 and IPv6 protocols are enabled on this attachment.
         IPV4_ONLY
            Only IPv4 protocol is enabled on this attachment.

     --update-labels=[KEY=VALUE,...]
        List of label KEY=VALUE pairs to update. If a label exists, its value
        is modified. Otherwise, a new label is created.

        Keys must start with a lowercase character and contain only hyphens
        (-), underscores (_), lowercase characters, and numbers. Values must
        contain only hyphens (-), underscores (_), lowercase characters, and
        numbers.

     At most one of these can be specified:

       --clear-labels
          Remove all labels. If --update-labels is also specified then
          --clear-labels is applied first.

          For example, to remove all labels:

              $ gcloud beta compute interconnects attachments dedicated update \
                --clear-labels

          To remove all existing labels and create two new labels, foo and baz:

              $ gcloud beta compute interconnects attachments dedicated update \
                --clear-labels --update-labels foo=bar,baz=qux

       --remove-labels=[KEY,...]
          List of label keys to remove. If a label does not exist it is
          silently ignored. If --update-labels is also specified then
          --update-labels is applied first.

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 attachments dedicated update

        $ gcloud alpha compute interconnects attachments dedicated update