gcloud-help/gcloud/compute/reservations/update

NAME
    gcloud compute reservations update - update Compute Engine reservations

SYNOPSIS
    gcloud compute reservations update RESERVATION
        [--add-share-with=PROJECT,[PROJECT,...]]
        [--early-access-maintenance=EARLY_ACCESS_MAINTENANCE]
        [--[no-]enable-emergent-maintenance]
        [--remove-share-with=PROJECT,[PROJECT,...]]
        [--reservation-sharing-policy=RESERVATION_SHARING_POLICY]
        [--scheduling-type=SCHEDULING_TYPE] [--vm-count=VM_COUNT] [--zone=ZONE]
        [GCLOUD_WIDE_FLAG ...]

DESCRIPTION
    Update Compute Engine reservations.

EXAMPLES
    To add project-1,project-2,project-3 to the list of projects that are
    shared with a Compute Engine reservation, my-reservation in zone:
    us-central1-a, run:

        $ gcloud compute reservations update my-reservation \
          --add-share-with=project-1,project-2,project-3 \
          --zone=us-central1-a

    To remove project-1,project-2,project-3 from the list of projects that are
    shared with a Compute Engine reservation, my-reservation in zone:
    us-central1-a, run:

        $ gcloud compute reservations update my-reservation \
          --remove-share-with=project-1,project-2,project-3 \
          --zone=us-central1-a

    To update the number of reserved VM instances to 500 for a Compute Engine
    reservation, my-reservation in zone: us-central1-a, run:

        $ gcloud compute reservations update my-reservation \
          --zone=us-central1-a --vm-count=500

POSITIONAL ARGUMENTS
     RESERVATION
        Name of the reservation to update.

FLAGS
     --add-share-with=PROJECT,[PROJECT,...]
        If this reservation is shared (--share-setting is projects), then
        specify a comma-separated list of projects to share the reservation
        with. You must list the projects using project IDs or project numbers.

     --early-access-maintenance=EARLY_ACCESS_MAINTENANCE
        Enable this feature to receive quarterly updates and new features for
        your reservation earlier than the standard schedule..
        EARLY_ACCESS_MAINTENANCE must be one of:

         NO_EARLY_ACCESS
            Standard maintenance schedule. The reservation doesn't have early
            access maintenance.
         WAVE1
            Provides the earliest available notification and maintenance.
         WAVE2
            Provides notification and maintenance after WAVE1, but before the
            standard maintenance schedule.

     --[no-]enable-emergent-maintenance
        Enables the reservation to receive notifications when urgent
        maintenance for a GPU VM starts after the VM encounters a host error.
        Use --enable-emergent-maintenance to enable and
        --no-enable-emergent-maintenance to disable.

     --remove-share-with=PROJECT,[PROJECT,...]
        A list of specific projects to remove from the list of projects that
        this reservation is shared with. List must contain project IDs or
        project numbers.

     --reservation-sharing-policy=RESERVATION_SHARING_POLICY
        The reservation sharing policy to use for this reservation.
        RESERVATION_SHARING_POLICY must be one of:

         ALLOW_ALL
            The reservation can be shared with Google Cloud services.
         DISALLOW_ALL
            The reservation won't be shared with Google Cloud services. If you
            omit this flag during creation, the default value is DISALLOW_ALL.

     --scheduling-type=SCHEDULING_TYPE
        How Compute Engine schedules maintenance events for your reserved
        hosts. SCHEDULING_TYPE must be one of:

         GROUPED
            In GROUPED mode, maintenance is synchronized across all your VMs.
         INDEPENDENT
            In INDEPENDENT mode, your VMs have different, unsynchronized
            maintenance schedules.

     --vm-count=VM_COUNT
        The number of VM instances that are allocated to this reservation. The
        value of this field must be an int in the range [1, 1000].

     --zone=ZONE
        Zone of the reservation to update. If not specified and the
        compute/zone property isn't set, you might be prompted to select a zone
        (interactive mode only).

        To avoid prompting when this flag is omitted, you can set the
        compute/zone property:

            $ gcloud config set compute/zone ZONE

        A list of zones can be fetched by running:

            $ gcloud compute zones list

        To unset the property, run:

            $ gcloud config unset compute/zone

        Alternatively, the zone can be stored in the environment variable
        CLOUDSDK_COMPUTE_ZONE.

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 reservations update

        $ gcloud beta compute reservations update