mirror of
https://github.com/imjasonh/gcloud-help
synced 2026-07-18 06:47:12 +00:00
gcloud: Wed Mar 9 08:39:30 UTC 2022
This commit is contained in:
parent
5829e94e90
commit
7d82d0fc32
210 changed files with 7192 additions and 887 deletions
|
|
@ -5,7 +5,8 @@ SYNOPSIS
|
|||
gcloud alpha compute commitments create COMMITMENT --plan=PLAN
|
||||
(--resources=[local-ssd=LOCAL-SSD],[memory=MEMORY],[vcpu=VCPU]
|
||||
--resources-accelerator=[count=COUNT],[type=TYPE]) [--auto-renew]
|
||||
[--region=REGION] [--type=TYPE; default="general-purpose"]
|
||||
[--region=REGION] [--split-source-commitment=SPLIT_SOURCE_COMMITMENT]
|
||||
[--type=TYPE; default="general-purpose"]
|
||||
[--reservations-from-file=RESERVATIONS_FROM_FILE
|
||||
| [--reservation=RESERVATION : --reservation-zone=RESERVATION_ZONE
|
||||
--accelerator=[count=COUNT],[type=TYPE]
|
||||
|
|
@ -84,6 +85,9 @@ OPTIONAL FLAGS
|
|||
Alternatively, the region can be stored in the environment variable
|
||||
CLOUDSDK_COMPUTE_REGION.
|
||||
|
||||
--split-source-commitment=SPLIT_SOURCE_COMMITMENT
|
||||
Split the resources of previous commitment into a new commitment.
|
||||
|
||||
--type=TYPE; default="general-purpose"
|
||||
Type of commitment. memory-optimized indicates that the commitment is
|
||||
for memory-optimized VMs. TYPE must be one of: accelerator-optimized,
|
||||
|
|
|
|||
|
|
@ -72,6 +72,10 @@ COMMANDS
|
|||
snapshot
|
||||
(ALPHA) Create snapshots of Compute Engine persistent disks.
|
||||
|
||||
start-async-replication
|
||||
(ALPHA) Start asynchronous replication on a Compute Engine persistent
|
||||
disk.
|
||||
|
||||
stop-async-replication
|
||||
(ALPHA) Stop async replication on a Compute Engine persistent disk.
|
||||
|
||||
|
|
|
|||
|
|
@ -67,8 +67,7 @@ FLAGS
|
|||
|
||||
--guest-flush
|
||||
Create an application-consistent snapshot by informing the OS to
|
||||
prepare for the snapshot process. Currently only supported on Windows
|
||||
instances using the Volume Shadow Copy Service (VSS).
|
||||
prepare for the snapshot process.
|
||||
|
||||
--labels=[KEY=VALUE,...]
|
||||
List of label KEY=VALUE pairs to add.
|
||||
|
|
|
|||
104
gcloud/alpha/compute/disks/start-async-replication
Normal file
104
gcloud/alpha/compute/disks/start-async-replication
Normal file
|
|
@ -0,0 +1,104 @@
|
|||
NAME
|
||||
gcloud alpha compute disks start-async-replication - start asynchronous
|
||||
replication on a Compute Engine persistent disk
|
||||
|
||||
SYNOPSIS
|
||||
gcloud alpha compute disks start-async-replication DISK_NAME
|
||||
--secondary-disk=SECONDARY_DISK [--region=REGION | --zone=ZONE]
|
||||
[--secondary-disk-region=SECONDARY_DISK_REGION
|
||||
| --secondary-disk-zone=SECONDARY_DISK_ZONE] [GCLOUD_WIDE_FLAG ...]
|
||||
|
||||
DESCRIPTION
|
||||
(ALPHA) gcloud alpha compute disks start-async-replication starts async
|
||||
replication on a Compute Engine persistent disk. This command must be
|
||||
invoked on the primary disk and --secondary-disk must be provided.
|
||||
|
||||
EXAMPLES
|
||||
Replication can only be started from the primary scope. To start
|
||||
replication from the primary disk 'my-disk-1' in zone us-east1-a to the
|
||||
secondary disk 'my-disk-2' in zone us-west1-a:
|
||||
|
||||
$ gcloud alpha compute disks start-async-replication my-disk-1 \
|
||||
--zone=us-east1-a --secondary-disk=my-disk-2 \
|
||||
--secondary-disk-zone=us-west1-a
|
||||
|
||||
POSITIONAL ARGUMENTS
|
||||
DISK_NAME
|
||||
Name of the disk to operate on.
|
||||
|
||||
REQUIRED FLAGS
|
||||
--secondary-disk=SECONDARY_DISK
|
||||
Secondary disk for asynchronous replication. This flag is required when
|
||||
starting replication. It is also required when stopping replication on
|
||||
the primary disk. It must not be used when stopping replication on the
|
||||
secondary disk.
|
||||
|
||||
OPTIONAL FLAGS
|
||||
At most one of these can be specified:
|
||||
|
||||
--region=REGION
|
||||
Region of the disk to operate on. If not specified, you might be
|
||||
prompted to select a region (interactive mode only).
|
||||
|
||||
To avoid prompting when this flag is omitted, you can set the
|
||||
compute/region property:
|
||||
|
||||
$ gcloud config set compute/region REGION
|
||||
|
||||
A list of regions can be fetched by running:
|
||||
|
||||
$ gcloud compute regions list
|
||||
|
||||
To unset the property, run:
|
||||
|
||||
$ gcloud config unset compute/region
|
||||
|
||||
Alternatively, the region can be stored in the environment variable
|
||||
CLOUDSDK_COMPUTE_REGION.
|
||||
|
||||
--zone=ZONE
|
||||
Zone of the disk to operate on. If not specified and the compute/zone
|
||||
property isn't set, you might be prompted to select a zone
|
||||
(interactive mode only).
|
||||
|
||||
To avoid prompting when this flag is omitted, you can set the
|
||||
compute/zone property:
|
||||
|
||||
$ gcloud config set compute/zone ZONE
|
||||
|
||||
A list of zones can be fetched by running:
|
||||
|
||||
$ gcloud compute zones list
|
||||
|
||||
To unset the property, run:
|
||||
|
||||
$ gcloud config unset compute/zone
|
||||
|
||||
Alternatively, the zone can be stored in the environment variable
|
||||
CLOUDSDK_COMPUTE_ZONE.
|
||||
|
||||
At most one of these can be specified:
|
||||
|
||||
--secondary-disk-region=SECONDARY_DISK_REGION
|
||||
Region of the secondary disk for asynchronous replication. Overrides
|
||||
the default compute/region property value for this command
|
||||
invocation.
|
||||
|
||||
--secondary-disk-zone=SECONDARY_DISK_ZONE
|
||||
Zone of the secondary disk for asynchronous replication. Overrides
|
||||
the default compute/zone property value for this command invocation.
|
||||
|
||||
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
|
||||
This command is currently in alpha and might change without notice. If this
|
||||
command fails with API permission errors despite specifying the correct
|
||||
project, you might be trying to access an API with an invitation-only early
|
||||
access allowlist.
|
||||
|
||||
|
|
@ -14,8 +14,8 @@ SYNOPSIS
|
|||
| --target-ssl-proxy=TARGET_SSL_PROXY
|
||||
| --target-tcp-proxy=TARGET_TCP_PROXY
|
||||
| --target-vpn-gateway=TARGET_VPN_GATEWAY) [--allow-global-access]
|
||||
[--description=DESCRIPTION] [--ip-protocol=IP_PROTOCOL]
|
||||
[--is-mirroring-collector]
|
||||
[--allow-psc-global-access] [--description=DESCRIPTION]
|
||||
[--ip-protocol=IP_PROTOCOL] [--is-mirroring-collector]
|
||||
[--load-balancing-scheme=LOAD_BALANCING_SCHEME] [--network=NETWORK]
|
||||
[--network-tier=NETWORK_TIER]
|
||||
[--service-directory-registration=SERVICE_DIRECTORY_REGISTRATION]
|
||||
|
|
@ -171,6 +171,12 @@ OPTIONAL FLAGS
|
|||
the LOAD_BALANCING_SCHEME set to INTERNAL and the target must be either
|
||||
a backend service or a target instance.
|
||||
|
||||
--allow-psc-global-access
|
||||
If specified, then clients from all regions can access this Private
|
||||
Service Connect forwarding rule. This can only be specified if the
|
||||
forwarding rule's target is a service attachment
|
||||
(--target-service-attachment).
|
||||
|
||||
--description=DESCRIPTION
|
||||
Optional textual description for the forwarding rule.
|
||||
|
||||
|
|
|
|||
|
|
@ -58,6 +58,10 @@ SYNOPSIS
|
|||
[--image-family-scope=IMAGE_FAMILY_SCOPE
|
||||
--image-project=IMAGE_PROJECT --image=IMAGE
|
||||
| --image-family=IMAGE_FAMILY | --source-snapshot=SOURCE_SNAPSHOT]
|
||||
[--instance-kms-key=INSTANCE_KMS_KEY
|
||||
: --instance-kms-keyring=INSTANCE_KMS_KEYRING
|
||||
--instance-kms-location=INSTANCE_KMS_LOCATION
|
||||
--instance-kms-project=INSTANCE_KMS_PROJECT]
|
||||
[--maintenance-policy=MAINTENANCE_POLICY
|
||||
| --on-host-maintenance=MAINTENANCE_POLICY]
|
||||
[--network-interface=[PROPERTY=VALUE,...]
|
||||
|
|
@ -945,6 +949,37 @@ FLAGS
|
|||
▸ https://compute.googleapis.com/compute/v1/projects/myproject/global/snapshots/snapshot
|
||||
▸ snapshot
|
||||
|
||||
Key resource - The Cloud KMS (Key Management Service) cryptokey that will
|
||||
be used to protect the instance. The arguments in this group can be used
|
||||
to specify the attributes of this resource.
|
||||
|
||||
--instance-kms-key=INSTANCE_KMS_KEY
|
||||
ID of the key or fully qualified identifier for the key. To set the
|
||||
kms-key attribute:
|
||||
▸ provide the argument --instance-kms-key on the command line.
|
||||
|
||||
This flag must be specified if any of the other arguments in this
|
||||
group are specified.
|
||||
|
||||
--instance-kms-keyring=INSTANCE_KMS_KEYRING
|
||||
The KMS keyring of the key. To set the kms-keyring attribute:
|
||||
▸ provide the argument --instance-kms-key on the command line with
|
||||
a fully specified name;
|
||||
▸ provide the argument --instance-kms-keyring on the command line.
|
||||
|
||||
--instance-kms-location=INSTANCE_KMS_LOCATION
|
||||
The Cloud location for the key. To set the kms-location attribute:
|
||||
▸ provide the argument --instance-kms-key on the command line with
|
||||
a fully specified name;
|
||||
▸ provide the argument --instance-kms-location on the command line.
|
||||
|
||||
--instance-kms-project=INSTANCE_KMS_PROJECT
|
||||
The Cloud project for the key. To set the kms-project attribute:
|
||||
▸ provide the argument --instance-kms-key on the command line with
|
||||
a fully specified name;
|
||||
▸ provide the argument --instance-kms-project on the command line;
|
||||
▸ set the property core/project.
|
||||
|
||||
Maintenance Behavior.
|
||||
|
||||
At most one of these can be specified:
|
||||
|
|
|
|||
|
|
@ -47,8 +47,7 @@ OPTIONAL FLAGS
|
|||
|
||||
--guest-flush
|
||||
Create an application-consistent machine image by informing the OS to
|
||||
prepare for the snapshot process. Currently only supported on Windows
|
||||
instances using the Volume Shadow Copy Service (VSS).
|
||||
prepare for the snapshot process.
|
||||
|
||||
--require-csek-key-create
|
||||
Refuse to create machine images not protected by a user managed key in
|
||||
|
|
|
|||
|
|
@ -118,8 +118,7 @@ OPTIONAL FLAGS
|
|||
|
||||
--guest-flush
|
||||
Create an application-consistent machine image by informing the OS to
|
||||
prepare for the snapshot process. Currently only supported on Windows
|
||||
instances using the Volume Shadow Copy Service (VSS).
|
||||
prepare for the snapshot process.
|
||||
|
||||
--guest-os-features=[GUEST_OS_FEATURE,...]
|
||||
This parameter enables one or more features for VM instances that use
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue