1
0
Fork 0
mirror of https://github.com/imjasonh/gcloud-help synced 2026-07-15 17:35:31 +00:00

gcloud: Thu Jun 22 10:31:35 UTC 2023

This commit is contained in:
Automated 2023-06-22 10:31:35 +00:00
parent 2102dc5511
commit dc0d916cee
219 changed files with 5076 additions and 1639 deletions

View file

@ -31,6 +31,9 @@ COMMANDS
failover
Failover an AlloyDB instance within a given cluster.
inject-fault
Inject fault on an AlloyDB instance within a given cluster.
list
Lists AlloyDB instances in a given cluster.

View file

@ -0,0 +1,56 @@
NAME
gcloud alloydb instances inject-fault - inject fault on an AlloyDB instance
within a given cluster
SYNOPSIS
gcloud alloydb instances inject-fault INSTANCE --cluster=CLUSTER
--fault-type=FAULT_TYPE --region=REGION [--async]
[GCLOUD_WIDE_FLAG ...]
DESCRIPTION
Inject fault on an AlloyDB instance within a given cluster.
EXAMPLES
To Inject fault on an instance, run:
$ gcloud alloydb instances inject-fault my-instance \
--cluster=my-cluster --region=us-central1 --fault-type=stop-vm
POSITIONAL ARGUMENTS
INSTANCE
AlloyDB instance ID
REQUIRED FLAGS
--cluster=CLUSTER
AlloyDB cluster ID
--fault-type=FAULT_TYPE
Specifies fault type. FAULT_TYPE must be (only one value is supported):
stop-vm
stop-vm fault type supports stopping the VM.
--region=REGION
Regional location (e.g. asia-east1, us-east1). See the full list of
regions at https://cloud.google.com/sql/docs/instance-locations.
OPTIONAL FLAGS
--async
Return immediately, without waiting for the operation in progress to
complete.
GCLOUD WIDE FLAGS
These flags are available to all commands: --access-token-file, --account,
--billing-project, --configuration, --flags-file, --flatten, --format,
--help, --impersonate-service-account, --log-http, --project, --quiet,
--trace-token, --user-output-enabled, --verbosity.
Run $ gcloud help for details.
NOTES
These variants are also available:
$ gcloud alpha alloydb instances inject-fault
$ gcloud beta alloydb instances inject-fault