1
0
Fork 0
mirror of https://github.com/imjasonh/gcloud-help synced 2026-07-13 16:37:00 +00:00

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

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

View file

@ -33,28 +33,37 @@ EXAMPLES
To clone an instance from its current state (most recent binary log
coordinates):
$ gcloud beta sql instances clone instance-foo instance-bar
$ gcloud beta sql instances clone my-source-instance \
my-cloned-instance
To clone a MySQL instance from an earlier point in time (past binary log
coordinates):
$ gcloud beta sql instances clone instance-foo instance-bar \
--bin-log-file-name mysql-bin.000020 --bin-log-position 170
$ gcloud beta sql instances clone my-source-instance \
my-cloned-instance --bin-log-file-name mysql-bin.000020 \
--bin-log-position 170
To clone a MySQL source instance at a specific point in time:
$ gcloud beta sql instances clone instance-foo instance-bar \
--point-in-time '2012-11-15T16:19:00.094Z'
$ gcloud beta sql instances clone my-source-instance \
my-cloned-instance --point-in-time '2012-11-15T16:19:00.094Z'
To clone a PostgreSQL source instance at a specific point in time:
$ gcloud beta sql instances clone instance-foo instance-bar \
--point-in-time '2012-11-15T16:19:00.094Z'
$ gcloud beta sql instances clone my-source-instance \
my-cloned-instance --point-in-time '2012-11-15T16:19:00.094Z'
To clone a SQL Server source instance at a specific point in time:
$ gcloud beta sql instances clone instance-foo instance-bar \
--point-in-time '2012-11-15T16:19:00.094Z'
$ gcloud beta sql instances clone my-source-instance \
my-cloned-instance --point-in-time '2012-11-15T16:19:00.094Z'
To clone a deleted instance, include the name and deletion time of the
source instance:
$ gcloud beta sql instances clone my-source-instance \
my-cloned-instance \
--source-instance-deletion-time '2012-11-15T16:19:00.094Z'
POSITIONAL ARGUMENTS
SOURCE

View file

@ -215,7 +215,10 @@ FLAGS
--cpu=CPU
Whole number value indicating how many cores are desired in the
machine. Both --cpu and --memory must be specified if a custom machine
type is desired, and the --tier flag must be omitted.
type is desired, and the --tier flag must be omitted.--cpu and --memory
flags are not compatible with the Enterprise Plus edition. These flags
should not be used when creating an Enterprise Plus edition, as the
machine configuration is determined by the --tier flag instead.
--custom-subject-alternative-names=DNS,[DNS,[DNS]]
A comma-separated list of DNS names to add to the instance's SSL
@ -385,7 +388,10 @@ FLAGS
machine. A size unit should be provided (eg. 3072MiB or 9GiB) - if no
units are specified, GiB is assumed. Both --cpu and --memory must be
specified if a custom machine type is desired, and the --tier flag must
be omitted.
be omitted. --cpu and --memory flags are not compatible with the
Enterprise Plus edition. These flags should not be used when creating
an Enterprise Plus edition, as the machine configuration is determined
by the --tier flag instead.
--network=NETWORK
Network in the current project that the instance will be part of. To

View file

@ -16,6 +16,11 @@ EXAMPLES
$ gcloud beta sql instances get-latest-recovery-time instance-foo
To retrieve the latest recovery time for an instance that has been deleted:
$ gcloud beta sql instances get-latest-recovery-time instance-foo \
--source-instance-deletion-time '2012-11-15T16:19:00.094Z'
POSITIONAL ARGUMENTS
INSTANCE
Cloud SQL instance ID.

View file

@ -45,6 +45,7 @@ SYNOPSIS
[--password-policy-password-change-interval=PASSWORD_POLICY_PASSWORD_CHANGE_INTERVAL]
[--password-policy-reuse-interval=PASSWORD_POLICY_REUSE_INTERVAL]
[--pricing-plan=PRICING_PLAN, -p PRICING_PLAN]
[--reconcile-psa-networking]
[--[no-]recreate-replicas-on-primary-crash]
[--remove-deny-maintenance-period] [--replication=REPLICATION]
[--replication-lag-max-seconds-for-recreate=REPLICATION_LAG_MAX_SECONDS_FOR_RECREATE]
@ -164,7 +165,10 @@ FLAGS
--cpu=CPU
Whole number value indicating how many cores are desired in the
machine. Both --cpu and --memory must be specified if a custom machine
type is desired, and the --tier flag must be omitted.
type is desired, and the --tier flag must be omitted.--cpu and --memory
flags are not compatible with the Enterprise Plus edition. These flags
should not be used when creating an Enterprise Plus edition, as the
machine configuration is determined by the --tier flag instead.
--database-version=DATABASE_VERSION
The database engine type and versions. If left unspecified, no changes
@ -342,7 +346,10 @@ FLAGS
machine. A size unit should be provided (eg. 3072MiB or 9GiB) - if no
units are specified, GiB is assumed. Both --cpu and --memory must be
specified if a custom machine type is desired, and the --tier flag must
be omitted.
be omitted. --cpu and --memory flags are not compatible with the
Enterprise Plus edition. These flags should not be used when creating
an Enterprise Plus edition, as the machine configuration is determined
by the --tier flag instead.
--network=NETWORK
Network in the current project that the instance will be part of. To
@ -388,6 +395,12 @@ FLAGS
First Generation instances only. The pricing plan for this instance.
PRICING_PLAN must be one of: PER_USE, PACKAGE.
--reconcile-psa-networking
Reconciles the instance's PSA networking configuration. If the instance
is already on a PSA network, the DNS zone and records associated with
the PSA write endpoint are either added if missing or updated if
incorrect.
--[no-]recreate-replicas-on-primary-crash
Allow/Disallow replica recreation when a primary MySQL instance
operating in reduced durability mode crashes. Not recreating the