mirror of
https://github.com/imjasonh/gcloud-help
synced 2026-07-15 09:25:44 +00:00
gcloud: Sat Jun 14 05:31:37 UTC 2025
This commit is contained in:
parent
1799759190
commit
fa40c10f6a
712 changed files with 17386 additions and 4918 deletions
|
|
@ -161,7 +161,10 @@ OPTIONAL 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
|
||||
|
|
@ -255,7 +258,10 @@ OPTIONAL 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
|
||||
|
|
|
|||
|
|
@ -34,35 +34,30 @@ EXAMPLES
|
|||
To clone an instance from its current state (most recent binary log
|
||||
coordinates):
|
||||
|
||||
$ gcloud alpha sql instances clone instance-foo instance-bar
|
||||
$ gcloud alpha 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 alpha sql instances clone instance-foo instance-bar \
|
||||
--bin-log-file-name mysql-bin.000020 --bin-log-position 170
|
||||
$ gcloud alpha 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 alpha sql instances clone instance-foo instance-bar \
|
||||
--point-in-time '2012-11-15T16:19:00.094Z'
|
||||
$ gcloud alpha 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 alpha sql instances clone instance-foo instance-bar \
|
||||
--point-in-time '2012-11-15T16:19:00.094Z'
|
||||
$ gcloud alpha 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 alpha sql instances clone instance-foo instance-bar \
|
||||
--point-in-time '2012-11-15T16:19:00.094Z'
|
||||
|
||||
To specify the allocated IP range for the private IP target Instance
|
||||
(reserved for future use):
|
||||
|
||||
$ gcloud alpha sql instances clone my-source-instance \
|
||||
my-cloned-instance \
|
||||
--allocated-ip-range-name cloned-instance-ip-range
|
||||
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:
|
||||
|
|
@ -71,6 +66,13 @@ EXAMPLES
|
|||
my-cloned-instance \
|
||||
--source-instance-deletion-time '2012-11-15T16:19:00.094Z'
|
||||
|
||||
To specify the allocated IP range for the private IP target Instance
|
||||
(reserved for future use):
|
||||
|
||||
$ gcloud alpha sql instances clone my-source-instance \
|
||||
my-cloned-instance \
|
||||
--allocated-ip-range-name cloned-instance-ip-range
|
||||
|
||||
POSITIONAL ARGUMENTS
|
||||
SOURCE
|
||||
Cloud SQL instance ID of the source.
|
||||
|
|
|
|||
|
|
@ -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
|
||||
|
|
|
|||
|
|
@ -16,6 +16,11 @@ EXAMPLES
|
|||
|
||||
$ gcloud alpha sql instances get-latest-recovery-time instance-foo
|
||||
|
||||
To retrieve the latest recovery time for an instance that has been deleted:
|
||||
|
||||
$ gcloud alpha 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.
|
||||
|
|
|
|||
|
|
@ -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
|
||||
|
|
|
|||
|
|
@ -41,24 +41,20 @@ OPTIONAL FLAGS
|
|||
|
||||
--password-policy-allowed-failed-attempts=PASSWORD_POLICY_ALLOWED_FAILED_ATTEMPTS
|
||||
Number of failed login attempts allowed before a user is locked out.
|
||||
This flag is available only for MySQL.
|
||||
|
||||
--[no-]password-policy-enable-failed-attempts-check
|
||||
Enables the failed login attempts check if set to true. This flag is
|
||||
available only for MySQL. Use
|
||||
Enables the failed login attempts check if set to true. Use
|
||||
--password-policy-enable-failed-attempts-check to enable and
|
||||
--no-password-policy-enable-failed-attempts-check to disable.
|
||||
|
||||
--[no-]password-policy-enable-password-verification
|
||||
The current password must be specified when altering the password. This
|
||||
flag is available only for MySQL. Use
|
||||
The current password must be specified when altering the password. Use
|
||||
--password-policy-enable-password-verification to enable and
|
||||
--no-password-policy-enable-password-verification to disable.
|
||||
|
||||
--password-policy-password-expiration-duration=PASSWORD_POLICY_PASSWORD_EXPIRATION_DURATION
|
||||
Expiration duration after a password is updated, for example, 2d for 2
|
||||
days. See gcloud topic datetimes for information on duration formats.
|
||||
This flag is available only for MySQL.
|
||||
|
||||
--type=TYPE
|
||||
Cloud SQL user's type. It determines the method to authenticate the
|
||||
|
|
|
|||
|
|
@ -57,24 +57,20 @@ OPTIONAL FLAGS
|
|||
|
||||
--password-policy-allowed-failed-attempts=PASSWORD_POLICY_ALLOWED_FAILED_ATTEMPTS
|
||||
Number of failed login attempts allowed before a user is locked out.
|
||||
This flag is available only for MySQL.
|
||||
|
||||
--[no-]password-policy-enable-failed-attempts-check
|
||||
Enables the failed login attempts check if set to true. This flag is
|
||||
available only for MySQL. Use
|
||||
Enables the failed login attempts check if set to true. Use
|
||||
--password-policy-enable-failed-attempts-check to enable and
|
||||
--no-password-policy-enable-failed-attempts-check to disable.
|
||||
|
||||
--[no-]password-policy-enable-password-verification
|
||||
The current password must be specified when altering the password. This
|
||||
flag is available only for MySQL. Use
|
||||
The current password must be specified when altering the password. Use
|
||||
--password-policy-enable-password-verification to enable and
|
||||
--no-password-policy-enable-password-verification to disable.
|
||||
|
||||
--password-policy-password-expiration-duration=PASSWORD_POLICY_PASSWORD_EXPIRATION_DURATION
|
||||
Expiration duration after a password is updated, for example, 2d for 2
|
||||
days. See gcloud topic datetimes for information on duration formats.
|
||||
This flag is available only for MySQL.
|
||||
|
||||
GCLOUD WIDE FLAGS
|
||||
These flags are available to all commands: --access-token-file, --account,
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue