imjasonh/gcloud-help
1
0
Fork 0
mirror of https://github.com/imjasonh/gcloud-help synced 2026-07-18 14:56:05 +00:00
Code Activity

gcloud: Sat Jun 14 05:31:37 UTC 2025

Browse source
This commit is contained in:
Automated 2025-06-14 05:31:37 +00:00
parent 1799759190
commit fa40c10f6a
712 changed files with 17386 additions and 4918 deletions
Download patch file Download diff file Expand all files Collapse all files

4
gcloud/beta/alloydb/clusters/create
View file

@ -54,7 +54,7 @@ OPTIONAL FLAGS
for this cluster will be created in the allocated range. The range name
must comply with RFC 1035. Specifically, the name must be 1-63
characters long and match the regular expression
[a-z]([-a-z0-9][a-z0-9])?.
[a-z]([-a-z0-9]*[a-z0-9])?.
--async
Return immediately, without waiting for the operation in progress to
@ -62,7 +62,7 @@ OPTIONAL FLAGS
--database-version=DATABASE_VERSION
Database version of the cluster. DATABASE_VERSION must be one of:
POSTGRES_14, POSTGRES_15, POSTGRES_16.
POSTGRES_14, POSTGRES_15, POSTGRES_16, POSTGRES_17.
--enable-private-service-connect
Enable Private Service Connect (PSC) connectivity for the cluster.

2
gcloud/beta/alloydb/clusters/create-secondary
View file

@ -50,7 +50,7 @@ OPTIONAL FLAGS
for this cluster will be created in the allocated range. The range name
must comply with RFC 1035. Specifically, the name must be 1-63
characters long and match the regular expression
[a-z]([-a-z0-9][a-z0-9])?.
[a-z]([-a-z0-9]*[a-z0-9])?.
--async
Return immediately, without waiting for the operation in progress to

3
gcloud/beta/alloydb/clusters/help
View file

@ -39,8 +39,7 @@ COMMANDS
(BETA) List AlloyDB clusters in a given project and region.
migrate-cloud-sql
(BETA) Migrate Cloud SQL instance to an AlloyDB cluster using an
existing Cloud SQL backup.
(BETA) Migrate Cloud SQL instance to an AlloyDB cluster.
promote
(BETA) Promote an AlloyDB SECONDARY cluster in a given project and

16
gcloud/beta/alloydb/clusters/migrate-cloud-sql
View file

@ -1,6 +1,6 @@
NAME
gcloud beta alloydb clusters migrate-cloud-sql - migrate Cloud SQL instance
to an AlloyDB cluster using an existing Cloud SQL backup
to an AlloyDB cluster
SYNOPSIS
gcloud beta alloydb clusters migrate-cloud-sql CLUSTER
@ -30,8 +30,8 @@ SYNOPSIS
[GCLOUD_WIDE_FLAG ...]
DESCRIPTION
(BETA) Migrate Cloud SQL instance to an AlloyDB cluster using an existing
Cloud SQL backup.
(BETA) This command migrates a Cloud SQL instance to an AlloyDB cluster
using an existing Cloud SQL backup.
EXAMPLES
To migrate a Cloud SQL instance to an AlloyDB cluster from a backup, run:
@ -80,7 +80,7 @@ OPTIONAL FLAGS
for this cluster will be created in the allocated range. The range name
must comply with RFC 1035. Specifically, the name must be 1-63
characters long and match the regular expression
[a-z]([-a-z0-9][a-z0-9])?.
[a-z]([-a-z0-9]*[a-z0-9])?.
--async
Return immediately, without waiting for the operation in progress to
@ -88,7 +88,7 @@ OPTIONAL FLAGS
--database-version=DATABASE_VERSION
Database version of the cluster. DATABASE_VERSION must be one of:
POSTGRES_14, POSTGRES_15, POSTGRES_16.
POSTGRES_14, POSTGRES_15, POSTGRES_16, POSTGRES_17.
--enable-private-service-connect
Enable Private Service Connect (PSC) connectivity for the cluster.
@ -343,8 +343,10 @@ GCLOUD WIDE FLAGS
Run $ gcloud help for details.
NOTES
This command is currently in beta and might change without notice. This
variant is also available:
This command is currently in beta and might change without notice. These
variants are also available:
$ gcloud alloydb clusters migrate-cloud-sql
$ gcloud alpha alloydb clusters migrate-cloud-sql

21
gcloud/beta/alloydb/clusters/restore
View file

@ -58,16 +58,17 @@ REQUIRED FLAGS
This flag argument must be specified if any of the other arguments
in this group are specified.
--source-cluster=SOURCE_CLUSTER
AlloyDB source cluster to restore from. This must either be the
full cluster name
(projects/myProject/locations/us-central1/backups/myCluster) or the
cluster ID (myCluster). In the second case, the project and
location are assumed to be the same as the restored cluster that is
being created.
Source for a point in time restore operation.
This flag argument must be specified if any of the other arguments
in this group are specified.
Exactly one of these must be specified:
--source-cluster=SOURCE_CLUSTER
AlloyDB source cluster to restore from. This must either be the
full cluster name
(projects/myProject/locations/us-central1/backups/myCluster) or
the cluster ID (myCluster). In the second case, the project and
location are assumed to be the same as the restored cluster that
is being created.
OPTIONAL FLAGS
--allocated-ip-range-name=ALLOCATED_IP_RANGE_NAME
@ -76,7 +77,7 @@ OPTIONAL FLAGS
for this cluster will be created in the allocated range. The range name
must comply with RFC 1035. Specifically, the name must be 1-63
characters long and match the regular expression
[a-z]([-a-z0-9][a-z0-9])?.
[a-z]([-a-z0-9]*[a-z0-9])?.
--async
Return immediately, without waiting for the operation in progress to

8
gcloud/beta/alloydb/instances/update
View file

@ -4,7 +4,8 @@ NAME
SYNOPSIS
gcloud beta alloydb instances update INSTANCE --cluster=CLUSTER
--region=REGION [--allowed-psc-projects=[ALLOWED_PSC_PROJECTS,...]]
--region=REGION [--activation-policy=ACTIVATION_POLICY]
[--allowed-psc-projects=[ALLOWED_PSC_PROJECTS,...]]
[--assign-inbound-public-ip=ASSIGN_INBOUND_PUBLIC_IP] [--async]
[--authorized-external-networks=[AUTHORIZED_NETWORK,...]]
[--availability-type=AVAILABILITY_TYPE]
@ -52,6 +53,11 @@ REQUIRED FLAGS
regions at https://cloud.google.com/sql/docs/instance-locations.
OPTIONAL FLAGS
--activation-policy=ACTIVATION_POLICY
Activation Policy for the instance. Required to START or STOP an
instance. ALWAYS - The instance is up and running. NEVER - The instance
is stopped. ACTIVATION_POLICY must be one of: ALWAYS, NEVER.
--allowed-psc-projects=[ALLOWED_PSC_PROJECTS,...]
Comma-separated list of allowed consumer projects to create endpoints
for Private Service Connect (PSC) connectivity for the instance. Only