mirror of
https://github.com/imjasonh/gcloud-help
synced 2026-07-12 07:58:28 +00:00
gcloud: Wed May 7 10:56:18 UTC 2025
This commit is contained in:
parent
b03a332ad8
commit
dfebca5b6c
222 changed files with 6775 additions and 1046 deletions
|
|
@ -12,6 +12,8 @@ SYNOPSIS
|
|||
--enable-continuous-backup
|
||||
[--continuous-backup-encryption-key=CONTINUOUS_BACKUP_ENCRYPTION_KEY
|
||||
: --continuous-backup-encryption-key-keyring=CONTINUOUS_BACKUP_ENCRYPTION_KEY_KEYRING --continuous-backup-encryption-key-location=CONTINUOUS_BACKUP_ENCRYPTION_KEY_LOCATION --continuous-backup-encryption-key-project=CONTINUOUS_BACKUP_ENCRYPTION_KEY_PROJECT]]
|
||||
[--deny-maintenance-period-end-date=DENY_MAINTENANCE_PERIOD_END_DATE
|
||||
--deny-maintenance-period-start-date=DENY_MAINTENANCE_PERIOD_START_DATE --deny-maintenance-period-time=DENY_MAINTENANCE_PERIOD_TIME]
|
||||
[--disable-automated-backup
|
||||
| [--automated-backup-days-of-week=[DAYS_OF_WEEK,...]
|
||||
--automated-backup-start-times=[START_TIMES,...]
|
||||
|
|
@ -136,6 +138,29 @@ OPTIONAL FLAGS
|
|||
on the command line;
|
||||
▫ set the property core/project.
|
||||
|
||||
Specify preferred day and time for maintenance deny period.
|
||||
|
||||
--deny-maintenance-period-end-date=DENY_MAINTENANCE_PERIOD_END_DATE
|
||||
Date when the deny maintenance period ends, that is 2020-11-01 or
|
||||
11-01 for recurring.
|
||||
|
||||
This flag argument must be specified if any of the other arguments in
|
||||
this group are specified.
|
||||
|
||||
--deny-maintenance-period-start-date=DENY_MAINTENANCE_PERIOD_START_DATE
|
||||
Date when the deny maintenance period begins, that is 2020-11-01 or
|
||||
11-01 for recurring.
|
||||
|
||||
This flag argument must be specified if any of the other arguments in
|
||||
this group are specified.
|
||||
|
||||
--deny-maintenance-period-time=DENY_MAINTENANCE_PERIOD_TIME
|
||||
Time when the deny maintenance period starts and ends, for example
|
||||
05:00, in UTC time zone.
|
||||
|
||||
This flag argument must be specified if any of the other arguments in
|
||||
this group are specified.
|
||||
|
||||
Automated backup policy. If unspecified, automated backups are disabled.
|
||||
|
||||
At most one of these can be specified:
|
||||
|
|
|
|||
|
|
@ -17,6 +17,9 @@ SYNOPSIS
|
|||
[--maintenance-window-any
|
||||
| --maintenance-window-day=MAINTENANCE_WINDOW_DAY
|
||||
--maintenance-window-hour=MAINTENANCE_WINDOW_HOUR]
|
||||
[--remove-deny-maintenance-period
|
||||
| --deny-maintenance-period-end-date=DENY_MAINTENANCE_PERIOD_END_DATE
|
||||
--deny-maintenance-period-start-date=DENY_MAINTENANCE_PERIOD_START_DATE --deny-maintenance-period-time=DENY_MAINTENANCE_PERIOD_TIME]
|
||||
[GCLOUD_WIDE_FLAG ...]
|
||||
|
||||
DESCRIPTION
|
||||
|
|
@ -222,6 +225,36 @@ OPTIONAL FLAGS
|
|||
This flag argument must be specified if any of the other arguments
|
||||
in this group are specified.
|
||||
|
||||
Specify maintenance deny period.
|
||||
|
||||
At most one of these can be specified:
|
||||
|
||||
--remove-deny-maintenance-period
|
||||
Remove the deny maintenance period.
|
||||
|
||||
Specify preferred day and time for maintenance deny period.
|
||||
|
||||
--deny-maintenance-period-end-date=DENY_MAINTENANCE_PERIOD_END_DATE
|
||||
Date when the deny maintenance period ends, that is 2020-11-01 or
|
||||
11-01 for recurring.
|
||||
|
||||
This flag argument must be specified if any of the other arguments
|
||||
in this group are specified.
|
||||
|
||||
--deny-maintenance-period-start-date=DENY_MAINTENANCE_PERIOD_START_DATE
|
||||
Date when the deny maintenance period begins, that is 2020-11-01 or
|
||||
11-01 for recurring.
|
||||
|
||||
This flag argument must be specified if any of the other arguments
|
||||
in this group are specified.
|
||||
|
||||
--deny-maintenance-period-time=DENY_MAINTENANCE_PERIOD_TIME
|
||||
Time when the deny maintenance period starts and ends, for example
|
||||
05:00, in UTC time zone.
|
||||
|
||||
This flag argument must be specified if any of the other arguments
|
||||
in this group are specified.
|
||||
|
||||
GCLOUD WIDE FLAGS
|
||||
These flags are available to all commands: --access-token-file, --account,
|
||||
--billing-project, --configuration, --flags-file, --flatten, --format,
|
||||
|
|
|
|||
|
|
@ -15,6 +15,7 @@ SYNOPSIS
|
|||
[--[no-]insights-config-record-application-tags]
|
||||
[--[no-]insights-config-record-client-address]
|
||||
[--machine-type=MACHINE_TYPE] [--[no-]outbound-public-ip]
|
||||
[--psc-auto-connections=[network=NETWORK],[project=PROJECT]]
|
||||
[--psc-network-attachment-uri=PSC_NETWORK_ATTACHMENT_URI]
|
||||
[--read-pool-node-count=READ_POOL_NODE_COUNT]
|
||||
[--[no-]require-connectors]
|
||||
|
|
@ -151,6 +152,33 @@ OPTIONAL FLAGS
|
|||
Add outbound Public IP connectivity to an AlloyDB instance. Use
|
||||
--outbound-public-ip to enable and --no-outbound-public-ip to disable.
|
||||
|
||||
--psc-auto-connections=[network=NETWORK],[project=PROJECT]
|
||||
Comma-separated list of consumer project and consumer network pairs to
|
||||
create endpoints for Private Service Connect (PSC) connectivity for the
|
||||
instance. Only instances in PSC-enabled clusters are allowed to set
|
||||
this field. Both project and network must be specified. (e.g.,
|
||||
--psc-auto-connections=project=project1,network=projects/vpc-host-project1/global/networks/network1
|
||||
--psc-auto-connections=project=project2,network=projects/vpc-host-project2/global/networks/network2).
|
||||
Sets psc_auto_connections value.
|
||||
|
||||
network
|
||||
Required, Sets network value.
|
||||
|
||||
project
|
||||
Required, Sets project value.
|
||||
|
||||
Shorthand Example:
|
||||
|
||||
--psc-auto-connections=network=string,project=string
|
||||
|
||||
JSON Example:
|
||||
|
||||
--psc-auto-connections='{"network": "string", "project": "string"}'
|
||||
|
||||
File Example:
|
||||
|
||||
--psc-auto-connections=path_to_file.(yaml|json)
|
||||
|
||||
--psc-network-attachment-uri=PSC_NETWORK_ATTACHMENT_URI
|
||||
Full URI of the network attachment that is configured to support
|
||||
outbound connectivity from an AlloyDB instance which uses Private
|
||||
|
|
|
|||
|
|
@ -10,6 +10,7 @@ SYNOPSIS
|
|||
[--availability-type=AVAILABILITY_TYPE]
|
||||
[--database-flags=FLAG=VALUE,[FLAG=VALUE,...]]
|
||||
[--[no-]outbound-public-ip]
|
||||
[--psc-auto-connections=[network=NETWORK],[project=PROJECT]]
|
||||
[--psc-network-attachment-uri=PSC_NETWORK_ATTACHMENT_URI]
|
||||
[--[no-]require-connectors] [--ssl-mode=SSL_MODE]
|
||||
[GCLOUD_WIDE_FLAG ...]
|
||||
|
|
@ -86,6 +87,33 @@ OPTIONAL FLAGS
|
|||
Add outbound Public IP connectivity to an AlloyDB instance. Use
|
||||
--outbound-public-ip to enable and --no-outbound-public-ip to disable.
|
||||
|
||||
--psc-auto-connections=[network=NETWORK],[project=PROJECT]
|
||||
Comma-separated list of consumer project and consumer network pairs to
|
||||
create endpoints for Private Service Connect (PSC) connectivity for the
|
||||
instance. Only instances in PSC-enabled clusters are allowed to set
|
||||
this field. Both project and network must be specified. (e.g.,
|
||||
--psc-auto-connections=project=project1,network=projects/vpc-host-project1/global/networks/network1
|
||||
--psc-auto-connections=project=project2,network=projects/vpc-host-project2/global/networks/network2).
|
||||
Sets psc_auto_connections value.
|
||||
|
||||
network
|
||||
Required, Sets network value.
|
||||
|
||||
project
|
||||
Required, Sets project value.
|
||||
|
||||
Shorthand Example:
|
||||
|
||||
--psc-auto-connections=network=string,project=string
|
||||
|
||||
JSON Example:
|
||||
|
||||
--psc-auto-connections='{"network": "string", "project": "string"}'
|
||||
|
||||
File Example:
|
||||
|
||||
--psc-auto-connections=path_to_file.(yaml|json)
|
||||
|
||||
--psc-network-attachment-uri=PSC_NETWORK_ATTACHMENT_URI
|
||||
Full URI of the network attachment that is configured to support
|
||||
outbound connectivity from an AlloyDB instance which uses Private
|
||||
|
|
|
|||
|
|
@ -18,6 +18,8 @@ SYNOPSIS
|
|||
[--psc-network-attachment-uri=PSC_NETWORK_ATTACHMENT_URI]
|
||||
[--read-pool-node-count=READ_POOL_NODE_COUNT]
|
||||
[--[no-]require-connectors] [--ssl-mode=SSL_MODE]
|
||||
[--clear-psc-auto-connections
|
||||
| --psc-auto-connections=[network=NETWORK],[project=PROJECT]]
|
||||
[GCLOUD_WIDE_FLAG ...]
|
||||
|
||||
DESCRIPTION
|
||||
|
|
@ -162,6 +164,40 @@ OPTIONAL FLAGS
|
|||
ENCRYPTED_ONLY
|
||||
SSL connections are required. CA verification is not enforced.
|
||||
|
||||
PSC auto connection options for an AlloyDB instance.
|
||||
|
||||
At most one of these can be specified:
|
||||
|
||||
--clear-psc-auto-connections
|
||||
Remove all PSC auto connections for an AlloyDB instance.
|
||||
|
||||
--psc-auto-connections=[network=NETWORK],[project=PROJECT]
|
||||
Comma-separated list of consumer project and consumer network pairs
|
||||
to create endpoints for Private Service Connect (PSC) connectivity
|
||||
for the instance. Only instances in PSC-enabled clusters are allowed
|
||||
to set this field. Both project and network must be specified. (e.g.,
|
||||
--psc-auto-connections=project=project1,network=projects/vpc-host-project1/global/networks/network1
|
||||
--psc-auto-connections=project=project2,network=projects/vpc-host-project2/global/networks/network2).
|
||||
Sets psc_auto_connections value.
|
||||
|
||||
network
|
||||
Required, Sets network value.
|
||||
|
||||
project
|
||||
Required, Sets project value.
|
||||
|
||||
Shorthand Example:
|
||||
|
||||
--psc-auto-connections=network=string,project=string
|
||||
|
||||
JSON Example:
|
||||
|
||||
--psc-auto-connections='{"network": "string", "project": "string"}'
|
||||
|
||||
File Example:
|
||||
|
||||
--psc-auto-connections=path_to_file.(yaml|json)
|
||||
|
||||
GCLOUD WIDE FLAGS
|
||||
These flags are available to all commands: --access-token-file, --account,
|
||||
--billing-project, --configuration, --flags-file, --flatten, --format,
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue