imjasonh/gcloud-help
1
0
Fork 0
mirror of https://github.com/imjasonh/gcloud-help synced 2026-07-17 14:26:34 +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

16
gcloud/sql/instances/clone
View file

@ -33,29 +33,35 @@ EXAMPLES
To clone an instance from its current state (most recent binary log
coordinates):
$ gcloud sql instances clone instance-foo instance-bar
$ gcloud 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 sql instances clone instance-foo instance-bar \
$ gcloud 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 sql instances clone instance-foo instance-bar \
$ gcloud 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 sql instances clone instance-foo instance-bar \
$ gcloud 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 sql instances clone instance-foo instance-bar \
$ gcloud 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 sql instances clone my-source-instance my-cloned-instance \
--source-instance-deletion-time '2012-11-15T16:19:00.094Z'
POSITIONAL ARGUMENTS
SOURCE
Cloud SQL instance ID of the source.

10
gcloud/sql/instances/create
View file

@ -188,7 +188,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
@ -344,7 +347,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

5
gcloud/sql/instances/get-latest-recovery-time
View file

@ -16,6 +16,11 @@ EXAMPLES
$ gcloud sql instances get-latest-recovery-time instance-foo
To retrieve the latest recovery time for an instance that has been deleted:
$ gcloud 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.

10
gcloud/sql/instances/patch
View file

@ -145,7 +145,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
@ -317,7 +320,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