NAME
    gcloud alpha alloydb instances update - updates an AlloyDB instance within
        a given cluster

SYNOPSIS
    gcloud alpha alloydb instances update INSTANCE --cluster=CLUSTER
        --region=REGION [--async] [--availability-type=AVAILABILITY_TYPE]
        [--cpu-count=CPU_COUNT] [--database-flags=FLAG=VALUE,[FLAG=VALUE,...]]
        [--read-pool-node-count=READ_POOL_NODE_COUNT] [GCLOUD_WIDE_FLAG ...]

DESCRIPTION
    (ALPHA) Updates an AlloyDB instance within a given cluster.

EXAMPLES
    To update the number of nodes in the read pool, run:

        $ gcloud alpha alloydb instances update my-read-instance \
            --cluster=my-cluster --region=us-central1 \
            --read-pool-node-count=3

POSITIONAL ARGUMENTS
     INSTANCE
        AlloyDB instance ID

REQUIRED FLAGS
     --cluster=CLUSTER
        AlloyDB cluster ID

     --region=REGION
        Regional location (e.g. asia-east1, us-east1). See the full list of
        regions at https://cloud.google.com/sql/docs/instance-locations.

OPTIONAL FLAGS
     --async
        Return immediately, without waiting for the operation in progress to
        complete.

     --availability-type=AVAILABILITY_TYPE
        Specifies level of availability. AVAILABILITY_TYPE must be (currently
        only one value is supported):

         REGIONAL
            Provides high availability and is recommended for production
            instances; instance automatically fails over to another zone within
            your selected region.

     --cpu-count=CPU_COUNT
        Whole number value indicating how many vCPUs the machine should
        contain. Each vCPU count corresponds to a N2 high-mem machine:
        (https://cloud.google.com/compute/docs/general-purpose-machines#n2_machines).
        CPU_COUNT must be one of: 2, 4, 8, 16, 32, 64.

     --database-flags=FLAG=VALUE,[FLAG=VALUE,...]
        Comma-separated list of database flags to set on the instance. Use an
        equals sign to separate flag name and value. Flags without values, like
        skip_grant_tables, can be written out without a value after, e.g.,
        skip_grant_tables=. Use on/off for booleans. View the Instance Resource
        API for allowed flags. (e.g., --database-flags
        max_allowed_packet=55555,skip_grant_tables=,log_output=1)

     --read-pool-node-count=READ_POOL_NODE_COUNT
        Read capacity, i.e. number of nodes in a read pool instance.

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. These variants are also available:

        $ gcloud alloydb instances update

        $ gcloud beta alloydb instances update

