imjasonh/gcloud-help
1
0
Fork 0
mirror of https://github.com/imjasonh/gcloud-help synced 2026-07-11 07:29:40 +00:00
Code Activity

gcloud: Wed Mar 5 10:41:25 UTC 2025

Browse source
This commit is contained in:
Automated 2025-03-05 10:41:25 +00:00
parent a597993b2e
commit 6dc93282df
279 changed files with 4198 additions and 801 deletions
Download patch file Download diff file Expand all files Collapse all files

3
gcloud/alloydb/clusters/help
View file

@ -50,6 +50,9 @@ COMMANDS
update
Update an AlloyDB cluster within a given project and region.
upgrade
Upgrade an AlloyDB cluster within a given project and region.
NOTES
These variants are also available:

50
gcloud/alloydb/clusters/upgrade Normal file
View file

@ -0,0 +1,50 @@
NAME
gcloud alloydb clusters upgrade - upgrade an AlloyDB cluster within a given
project and region
SYNOPSIS
gcloud alloydb clusters upgrade CLUSTER --region=REGION --version=VERSION
[--async] [GCLOUD_WIDE_FLAG ...]
DESCRIPTION
Upgrade an AlloyDB cluster within a given project and region.
EXAMPLES
To upgrade a cluster, run:
$ gcloud alloydb clusters upgrade my-cluster --region=us-central1 \
--version=POSTGRES_15
POSITIONAL ARGUMENTS
CLUSTER
AlloyDB cluster ID
REQUIRED FLAGS
--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.
--version=VERSION
Target database version for the upgrade. VERSION must be one of:
POSTGRES_14, POSTGRES_15, POSTGRES_16.
OPTIONAL FLAGS
--async
Return immediately, without waiting for the operation in progress to
complete.
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 alloydb clusters upgrade
$ gcloud beta alloydb clusters upgrade

2
gcloud/alloydb/instances/create
View file

@ -47,7 +47,7 @@ REQUIRED FLAGS
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, 96, 128.
CPU_COUNT must be one of: 1, 2, 4, 8, 16, 32, 64, 96, 128.
--instance-type=INSTANCE_TYPE
Specifies instance type. INSTANCE_TYPE must be one of:

2
gcloud/alloydb/instances/update
View file

@ -90,7 +90,7 @@ OPTIONAL FLAGS
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, 96, 128.
CPU_COUNT must be one of: 1, 2, 4, 8, 16, 32, 64, 96, 128.
--database-flags=FLAG=VALUE,[FLAG=VALUE,...]
Comma-separated list of database flags to set on the instance. Use an