diff --git a/gcloud/_version b/gcloud/_version index 677cfe4bb..f28bd1253 100644 --- a/gcloud/_version +++ b/gcloud/_version @@ -1,8 +1,8 @@ -Google Cloud SDK 486.0.0 -alpha 2024.07.26 -beta 2024.07.26 +Google Cloud SDK 487.0.0 +alpha 2024.08.06 +beta 2024.08.06 bq 2.1.7 -bundled-python3-unix 3.11.8 -core 2024.07.26 +bundled-python3-unix 3.11.9 +core 2024.08.06 gcloud-crc32c 1.0.0 gsutil 5.30 diff --git a/gcloud/alpha/artifacts/generic/download b/gcloud/alpha/artifacts/generic/download index a55b5d76e..8b3ff6abc 100644 --- a/gcloud/alpha/artifacts/generic/download +++ b/gcloud/alpha/artifacts/generic/download @@ -4,8 +4,9 @@ NAME SYNOPSIS gcloud alpha artifacts generic download --destination=DESTINATION - --package=ARTIFACT --version=VERSION [--name=NAME] - [--location=LOCATION --repository=REPOSITORY] [GCLOUD_WIDE_FLAG ...] + --package=ARTIFACT --version=VERSION [--chunk-size=CHUNK_SIZE] + [--name=NAME] [--location=LOCATION --repository=REPOSITORY] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Download a generic artifact from a generic artifact repository. @@ -19,6 +20,14 @@ EXAMPLES --version=v0.1.0 --destination=/path/to/destination/ \ --name=myfile.txt + To download version v0.1.0 of myfile.txt in 8000 byte chunks located in a + repository in "us-central1" to /path/to/destination/: + + $ gcloud alpha artifacts generic download --location=us-central1 \ + --project=myproject --repository=myrepo --package=mypackage \ + --version=v0.1.0 --destination=/path/to/destination/ \ + --name=myfile.txt --chunk-size=8000 + To download all files of version v0.1.0 and package mypackage located in a repository in "us-central1" to /path/to/destination/ while maintaining the folder hierarchy: @@ -38,6 +47,10 @@ REQUIRED FLAGS The version of the artifact to download. OPTIONAL FLAGS + --chunk-size=CHUNK_SIZE + If specified, the chunk size (bytes) to use for downloading the + package. + --name=NAME If specified, the file name within the artifact to download. diff --git a/gcloud/alpha/batch/jobs/cancel b/gcloud/alpha/batch/jobs/cancel new file mode 100644 index 000000000..a79bd709d --- /dev/null +++ b/gcloud/alpha/batch/jobs/cancel @@ -0,0 +1,65 @@ +NAME + gcloud alpha batch jobs cancel - cancel a job + +SYNOPSIS + gcloud alpha batch jobs cancel (JOB : --location=LOCATION) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) This command can fail for the following reasons: + ▪ The job specified does not exist. + ▪ The active account does not have permission to cancel the given job. + +EXAMPLES + To cancel the job with name projects/foo/locations/us-central1/jobs/bar, + run: + + $ gcloud alpha batch jobs cancel \ + projects/foo/locations/us-central1/jobs/bar + +POSITIONAL ARGUMENTS + Job resource - The Batch job resource. If --location not specified,the + current batch/location is used. The arguments in this group can be used to + specify the attributes of this resource. (NOTE) Some attributes are not + given arguments in this group but can be set in other ways. + + To set the project attribute: + ◆ provide the argument JOB on the command line with a fully specified + name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + JOB + ID of the job or fully qualified identifier for the job. + + To set the job attribute: + ▸ provide the argument JOB on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + Google Cloud location for the job. + + To set the location attribute: + ▸ provide the argument JOB on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ set the property batch/location. + +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. + diff --git a/gcloud/alpha/batch/jobs/help b/gcloud/alpha/batch/jobs/help index 9ab8ac37e..905006830 100644 --- a/gcloud/alpha/batch/jobs/help +++ b/gcloud/alpha/batch/jobs/help @@ -23,6 +23,9 @@ GCLOUD WIDE FLAGS COMMANDS COMMAND is one of the following: + cancel + (ALPHA) Cancel a job. + delete (ALPHA) Delete a job. diff --git a/gcloud/alpha/compute/firewall-rules/migrate b/gcloud/alpha/compute/firewall-rules/migrate index 622daf658..bb181fe35 100644 --- a/gcloud/alpha/compute/firewall-rules/migrate +++ b/gcloud/alpha/compute/firewall-rules/migrate @@ -9,6 +9,7 @@ SYNOPSIS | --target-firewall-policy=TARGET_FIREWALL_POLICY) [--exclusion-patterns-file=EXCLUSION_PATTERNS_FILE] [--export-terraform-script] [--force] + [--skip-migrate-target-service-accounts-to-tags] [--tag-mapping-file=TAG_MAPPING_FILE] [--terraform-script-output-file=TERRAFORM_SCRIPT_OUTPUT_FILE] [GCLOUD_WIDE_FLAG ...] @@ -63,6 +64,10 @@ OPTIONAL FLAGS If set, migration will succeed even if the tool detects that original rule evaluation order cannot be preserved. + --skip-migrate-target-service-accounts-to-tags + If set, migration will keep target service accounts as they are and + will not try to replace them with secure tags. + --tag-mapping-file=TAG_MAPPING_FILE Path to a JSON file with legacy tags and service accounts to secure tags mapping. diff --git a/gcloud/alpha/compute/instance-templates/create b/gcloud/alpha/compute/instance-templates/create index e0fe61b2a..b041adfc6 100644 --- a/gcloud/alpha/compute/instance-templates/create +++ b/gcloud/alpha/compute/instance-templates/create @@ -6,14 +6,15 @@ SYNOPSIS gcloud alpha compute instance-templates create NAME [--accelerator=[count=COUNT],[type=TYPE]] [--no-boot-disk-auto-delete] [--boot-disk-device-name=BOOT_DISK_DEVICE_NAME] + [--boot-disk-interface=BOOT_DISK_INTERFACE] [--boot-disk-provisioned-iops=BOOT_DISK_PROVISIONED_IOPS] [--boot-disk-provisioned-throughput=BOOT_DISK_PROVISIONED_THROUGHPUT] [--boot-disk-size=BOOT_DISK_SIZE] [--boot-disk-type=BOOT_DISK_TYPE] [--can-ip-forward] [--configure-disk=[PROPERTY=VALUE,...]] [--create-disk=[PROPERTY=VALUE,...]] [--description=DESCRIPTION] [--discard-local-ssds-at-termination-timestamp=DISCARD_LOCAL_SSDS_AT_TERMINATION_TIMESTAMP] - [--disk=[auto-delete=AUTO-DELETE], - [boot=BOOT],[device-name=DEVICE-NAME],[mode=MODE],[name=NAME]] + [--disk=[auto-delete=AUTO-DELETE],[boot=BOOT],[device-name=DEVICE-NAME], + [interface=INTERFACE],[mode=MODE],[name=NAME]] [--[no-]enable-nested-virtualization] [--[no-]enable-uefi-networking] [--enable-watchdog-timer] [--external-ipv6-address=EXTERNAL_IPV6_ADDRESS] @@ -126,6 +127,12 @@ FLAGS option can only be specified if a new boot disk is being created (as opposed to mounting an existing persistent disk). + --boot-disk-interface=BOOT_DISK_INTERFACE + Indicates the interface to use for the boot disk. The value must be one + of the following: + ◆ SCSI + ◆ NVME + --boot-disk-provisioned-iops=BOOT_DISK_PROVISIONED_IOPS Indicates how many IOPS to provision for the disk. This sets the number of I/O operations per second that the disk can handle. Value must be @@ -274,6 +281,12 @@ FLAGS The name of the storage pool in which the new disk is created. The new disk and the storage pool must be in the same location. + interface + The interface to use with the disk. The value must be one of the + following: + ▸ SCSI + ▸ NVME + boot If yes, indicates that this is a boot disk. The instance will use the first partition of the disk for its root file system. The @@ -371,15 +384,15 @@ FLAGS For more information about the --discard-local-ssd flag, see https://cloud.google.com/compute/docs/disks/local-ssd#stop_instance. - --disk=[auto-delete=AUTO-DELETE],[boot=BOOT],[device-name=DEVICE-NAME],[mode=MODE],[name=NAME] - Attaches an existing persistent disk to the instances. + --disk=[auto-delete=AUTO-DELETE],[boot=BOOT],[device-name=DEVICE-NAME],[interface=INTERFACE],[mode=MODE],[name=NAME] + Attaches an existing disk to the instances. name The disk to attach to the instances. If you create more than one instance, you can only attach a disk in read-only mode. By default, - you attach a zonal persistent disk located in the same zone of the - instance. If you want to attach a regional persistent disk, you - must specify the disk using its URI; for example, + you attach a zonal disk located in the same zone of the instance. + If you want to attach a regional disk, you must specify the disk + using its URI; for example, projects/myproject/regions/us-central1/disks/my-regional-disk. mode @@ -402,7 +415,13 @@ FLAGS If set to yes, the persistent disk is automatically deleted when the instance is deleted. However, if you detach the disk from the instance, deleting the instance doesn't delete the disk. The - default value for this is yes. + default value is yes. + + interface + The interface to use for the disk. The value must be one of the + following: + ▸ SCSI + ▸ NVME --[no-]enable-nested-virtualization If set to true, enables nested virtualization for the instance. Use diff --git a/gcloud/alpha/compute/instance-templates/create-with-container b/gcloud/alpha/compute/instance-templates/create-with-container index 5e7e07419..d42506501 100644 --- a/gcloud/alpha/compute/instance-templates/create-with-container +++ b/gcloud/alpha/compute/instance-templates/create-with-container @@ -7,6 +7,7 @@ SYNOPSIS gcloud alpha compute instance-templates create-with-container NAME [--accelerator=[count=COUNT],[type=TYPE]] [--no-boot-disk-auto-delete] [--boot-disk-device-name=BOOT_DISK_DEVICE_NAME] + [--boot-disk-interface=BOOT_DISK_INTERFACE] [--boot-disk-provisioned-iops=BOOT_DISK_PROVISIONED_IOPS] [--boot-disk-provisioned-throughput=BOOT_DISK_PROVISIONED_THROUGHPUT] [--boot-disk-size=BOOT_DISK_SIZE] [--boot-disk-type=BOOT_DISK_TYPE] @@ -24,8 +25,8 @@ SYNOPSIS [--container-restart-policy=POLICY; default="always"] [--container-stdin] [--container-tty] [--create-disk=[PROPERTY=VALUE,...]] [--description=DESCRIPTION] - [--disk=[auto-delete=AUTO-DELETE], - [boot=BOOT],[device-name=DEVICE-NAME],[mode=MODE],[name=NAME]] + [--disk=[auto-delete=AUTO-DELETE],[boot=BOOT],[device-name=DEVICE-NAME], + [interface=INTERFACE],[mode=MODE],[name=NAME]] [--external-ipv6-address=EXTERNAL_IPV6_ADDRESS] [--external-ipv6-prefix-length=EXTERNAL_IPV6_PREFIX_LENGTH] [--internal-ipv6-address=INTERNAL_IPV6_ADDRESS] @@ -116,6 +117,12 @@ FLAGS option can only be specified if a new boot disk is being created (as opposed to mounting an existing persistent disk). + --boot-disk-interface=BOOT_DISK_INTERFACE + Indicates the interface to use for the boot disk. The value must be one + of the following: + ◆ SCSI + ◆ NVME + --boot-disk-provisioned-iops=BOOT_DISK_PROVISIONED_IOPS Indicates how many IOPS to provision for the disk. This sets the number of I/O operations per second that the disk can handle. Value must be @@ -364,6 +371,12 @@ FLAGS The name of the storage pool in which the new disk is created. The new disk and the storage pool must be in the same location. + interface + The interface to use with the disk. The value must be one of the + following: + ▸ SCSI + ▸ NVME + multi-writer If yes, the disk is created in multi-writer mode so that it can be attached with read-write access to two VMs. The default value is @@ -391,15 +404,15 @@ FLAGS --description=DESCRIPTION Specifies a textual description for the instance template. - --disk=[auto-delete=AUTO-DELETE],[boot=BOOT],[device-name=DEVICE-NAME],[mode=MODE],[name=NAME] - Attaches an existing persistent disk to the instances. + --disk=[auto-delete=AUTO-DELETE],[boot=BOOT],[device-name=DEVICE-NAME],[interface=INTERFACE],[mode=MODE],[name=NAME] + Attaches an existing disk to the instances. name The disk to attach to the instances. If you create more than one instance, you can only attach a disk in read-only mode. By default, - you attach a zonal persistent disk located in the same zone of the - instance. If you want to attach a regional persistent disk, you - must specify the disk using its URI; for example, + you attach a zonal disk located in the same zone of the instance. + If you want to attach a regional disk, you must specify the disk + using its URI; for example, projects/myproject/regions/us-central1/disks/my-regional-disk. mode @@ -426,7 +439,13 @@ FLAGS If set to yes, the persistent disk is automatically deleted when the instance is deleted. However, if you detach the disk from the instance, deleting the instance doesn't delete the disk. The - default value for this is yes. + default value is yes. + + interface + The interface to use for the disk. The value must be one of the + following: + ▸ SCSI + ▸ NVME --external-ipv6-address=EXTERNAL_IPV6_ADDRESS Assigns the given external IPv6 address to the instance that is diff --git a/gcloud/alpha/compute/instances/attach-disk b/gcloud/alpha/compute/instances/attach-disk index 14c6a5ac0..a4400465f 100644 --- a/gcloud/alpha/compute/instances/attach-disk +++ b/gcloud/alpha/compute/instances/attach-disk @@ -5,7 +5,8 @@ SYNOPSIS gcloud alpha compute instances attach-disk INSTANCE_NAME --disk=DISK [--boot] [--csek-key-file=FILE] [--device-name=DEVICE_NAME] [--disk-scope=DISK_SCOPE; default="zonal"] [--force-attach] - [--mode=MODE; default="rw"] [--zone=ZONE] [GCLOUD_WIDE_FLAG ...] + [--interface=INTERFACE] [--mode=MODE; default="rw"] [--zone=ZONE] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) gcloud alpha compute instances attach-disk is used to attach a disk @@ -82,6 +83,14 @@ OPTIONAL FLAGS the previous instance fails at first. The server will continue trying to detach the disk from the previous instance in the background. + --interface=INTERFACE + The interface of the disk. INTERFACE must be one of: + + NVME + NVME + SCSI + SCSI + --mode=MODE; default="rw" Specifies the mode of the disk. MODE must be one of: diff --git a/gcloud/alpha/compute/instances/bulk/create b/gcloud/alpha/compute/instances/bulk/create index 2eccbc7c5..b2b09d9a5 100644 --- a/gcloud/alpha/compute/instances/bulk/create +++ b/gcloud/alpha/compute/instances/bulk/create @@ -9,6 +9,7 @@ SYNOPSIS [--accelerator=[count=COUNT],[type=TYPE]] [--no-address] [--async] [--no-boot-disk-auto-delete] [--boot-disk-device-name=BOOT_DISK_DEVICE_NAME] + [--boot-disk-interface=BOOT_DISK_INTERFACE] [--boot-disk-provisioned-iops=BOOT_DISK_PROVISIONED_IOPS] [--boot-disk-provisioned-throughput=BOOT_DISK_PROVISIONED_THROUGHPUT] [--boot-disk-size=BOOT_DISK_SIZE] [--boot-disk-type=BOOT_DISK_TYPE] @@ -165,6 +166,12 @@ OPTIONAL FLAGS option can only be specified if a new boot disk is being created (as opposed to mounting an existing persistent disk). + --boot-disk-interface=BOOT_DISK_INTERFACE + Indicates the interface to use for the boot disk. The value must be one + of the following: + ◆ SCSI + ◆ NVME + --boot-disk-provisioned-iops=BOOT_DISK_PROVISIONED_IOPS Indicates how many IOPS to provision for the disk. This sets the number of I/O operations per second that the disk can handle. Value must be @@ -296,6 +303,12 @@ OPTIONAL FLAGS The name of the storage pool in which the new disk is created. The new disk and the storage pool must be in the same location. + interface + The interface to use with the disk. The value must be one of the + following: + ▸ SCSI + ▸ NVME + boot If yes, indicates that this is a boot disk. The instance will use the first partition of the disk for its root file system. The diff --git a/gcloud/alpha/compute/instances/create b/gcloud/alpha/compute/instances/create index 0fd6cc0fd..55bdda6e8 100644 --- a/gcloud/alpha/compute/instances/create +++ b/gcloud/alpha/compute/instances/create @@ -8,6 +8,7 @@ SYNOPSIS [--availability-domain=AVAILABILITY_DOMAIN] [--no-boot-disk-auto-delete] [--boot-disk-device-name=BOOT_DISK_DEVICE_NAME] + [--boot-disk-interface=BOOT_DISK_INTERFACE] [--boot-disk-provisioned-iops=BOOT_DISK_PROVISIONED_IOPS] [--boot-disk-provisioned-throughput=BOOT_DISK_PROVISIONED_THROUGHPUT] [--boot-disk-size=BOOT_DISK_SIZE] [--boot-disk-type=BOOT_DISK_TYPE] @@ -16,7 +17,8 @@ SYNOPSIS [--description=DESCRIPTION] [--discard-local-ssds-at-termination-timestamp=DISCARD_LOCAL_SSDS_AT_TERMINATION_TIMESTAMP] [--disk=[auto-delete=AUTO-DELETE],[boot=BOOT],[device-name=DEVICE-NAME], - [force-attach=FORCE-ATTACH],[mode=MODE],[name=NAME],[scope=SCOPE]] + [force-attach=FORCE-ATTACH], + [interface=INTERFACE],[mode=MODE],[name=NAME],[scope=SCOPE]] [--enable-display-device] [--[no-]enable-nested-virtualization] [--[no-]enable-uefi-networking] [--enable-watchdog-timer] [--erase-windows-vss-signature] @@ -191,6 +193,12 @@ FLAGS option can only be specified if a new boot disk is being created (as opposed to mounting an existing persistent disk). + --boot-disk-interface=BOOT_DISK_INTERFACE + Indicates the interface to use for the boot disk. The value must be one + of the following: + ◆ SCSI + ◆ NVME + --boot-disk-provisioned-iops=BOOT_DISK_PROVISIONED_IOPS Indicates how many IOPS to provision for the disk. This sets the number of I/O operations per second that the disk can handle. Value must be @@ -315,6 +323,12 @@ FLAGS The name of the storage pool in which the new disk is created. The new disk and the storage pool must be in the same location. + interface + The interface to use with the disk. The value must be one of the + following: + ▸ SCSI + ▸ NVME + boot If yes, indicates that this is a boot disk. The instance will use the first partition of the disk for its root file system. The @@ -471,15 +485,15 @@ FLAGS For more information about the --discard-local-ssd flag, see https://cloud.google.com/compute/docs/disks/local-ssd#stop_instance. - --disk=[auto-delete=AUTO-DELETE],[boot=BOOT],[device-name=DEVICE-NAME],[force-attach=FORCE-ATTACH],[mode=MODE],[name=NAME],[scope=SCOPE] - Attaches an existing persistent disk to the instances. + --disk=[auto-delete=AUTO-DELETE],[boot=BOOT],[device-name=DEVICE-NAME],[force-attach=FORCE-ATTACH],[interface=INTERFACE],[mode=MODE],[name=NAME],[scope=SCOPE] + Attaches an existing disk to the instances. name The disk to attach to the instances. If you create more than one instance, you can only attach a disk in read-only mode. By default, - you attach a zonal persistent disk located in the same zone of the - instance. If you want to attach a regional persistent disk, you - must specify the disk using its URI; for example, + you attach a zonal disk located in the same zone of the instance. + If you want to attach a regional disk, you must specify the disk + using its URI; for example, projects/myproject/regions/us-central1/disks/my-regional-disk. mode @@ -502,7 +516,13 @@ FLAGS If set to yes, the persistent disk is automatically deleted when the instance is deleted. However, if you detach the disk from the instance, deleting the instance doesn't delete the disk. The - default value for this is yes. + default value is yes. + + interface + The interface to use for the disk. The value must be one of the + following: + ▸ SCSI + ▸ NVME scope Can be zonal or regional. If zonal, the disk is interpreted as a diff --git a/gcloud/alpha/compute/instances/create-with-container b/gcloud/alpha/compute/instances/create-with-container index 2094b51b0..0d5165a1f 100644 --- a/gcloud/alpha/compute/instances/create-with-container +++ b/gcloud/alpha/compute/instances/create-with-container @@ -7,6 +7,7 @@ SYNOPSIS [INSTANCE_NAMES ...] [--accelerator=[count=COUNT],[type=TYPE]] [--no-boot-disk-auto-delete] [--boot-disk-device-name=BOOT_DISK_DEVICE_NAME] + [--boot-disk-interface=BOOT_DISK_INTERFACE] [--boot-disk-provisioned-iops=BOOT_DISK_PROVISIONED_IOPS] [--boot-disk-provisioned-throughput=BOOT_DISK_PROVISIONED_THROUGHPUT] [--boot-disk-size=BOOT_DISK_SIZE] [--boot-disk-type=BOOT_DISK_TYPE] @@ -26,7 +27,8 @@ SYNOPSIS [--create-disk=[PROPERTY=VALUE,...]] [--description=DESCRIPTION] [--discard-local-ssds-at-termination-timestamp=DISCARD_LOCAL_SSDS_AT_TERMINATION_TIMESTAMP] [--disk=[auto-delete=AUTO-DELETE],[boot=BOOT],[device-name=DEVICE-NAME], - [force-attach=FORCE-ATTACH],[mode=MODE],[name=NAME],[scope=SCOPE]] + [force-attach=FORCE-ATTACH], + [interface=INTERFACE],[mode=MODE],[name=NAME],[scope=SCOPE]] [--[no-]enable-nested-virtualization] [--external-ipv6-address=EXTERNAL_IPV6_ADDRESS] [--external-ipv6-prefix-length=EXTERNAL_IPV6_PREFIX_LENGTH] @@ -131,6 +133,12 @@ FLAGS option can only be specified if a new boot disk is being created (as opposed to mounting an existing persistent disk). + --boot-disk-interface=BOOT_DISK_INTERFACE + Indicates the interface to use for the boot disk. The value must be one + of the following: + ◆ SCSI + ◆ NVME + --boot-disk-provisioned-iops=BOOT_DISK_PROVISIONED_IOPS Indicates how many IOPS to provision for the disk. This sets the number of I/O operations per second that the disk can handle. Value must be @@ -374,6 +382,12 @@ FLAGS The name of the storage pool in which the new disk is created. The new disk and the storage pool must be in the same location. + interface + The interface to use with the disk. The value must be one of the + following: + ▸ SCSI + ▸ NVME + multi-writer If yes, the disk is created in multi-writer mode so that it can be attached with read-write access to two VMs. The default value is @@ -415,15 +429,15 @@ FLAGS For more information about the --discard-local-ssd flag, see https://cloud.google.com/compute/docs/disks/local-ssd#stop_instance. - --disk=[auto-delete=AUTO-DELETE],[boot=BOOT],[device-name=DEVICE-NAME],[force-attach=FORCE-ATTACH],[mode=MODE],[name=NAME],[scope=SCOPE] - Attaches an existing persistent disk to the instances. + --disk=[auto-delete=AUTO-DELETE],[boot=BOOT],[device-name=DEVICE-NAME],[force-attach=FORCE-ATTACH],[interface=INTERFACE],[mode=MODE],[name=NAME],[scope=SCOPE] + Attaches an existing disk to the instances. name The disk to attach to the instances. If you create more than one instance, you can only attach a disk in read-only mode. By default, - you attach a zonal persistent disk located in the same zone of the - instance. If you want to attach a regional persistent disk, you - must specify the disk using its URI; for example, + you attach a zonal disk located in the same zone of the instance. + If you want to attach a regional disk, you must specify the disk + using its URI; for example, projects/myproject/regions/us-central1/disks/my-regional-disk. mode @@ -450,7 +464,13 @@ FLAGS If set to yes, the persistent disk is automatically deleted when the instance is deleted. However, if you detach the disk from the instance, deleting the instance doesn't delete the disk. The - default value for this is yes. + default value is yes. + + interface + The interface to use for the disk. The value must be one of the + following: + ▸ SCSI + ▸ NVME scope Can be zonal or regional. If zonal, the disk is interpreted as a diff --git a/gcloud/alpha/compute/instances/detach-disk b/gcloud/alpha/compute/instances/detach-disk index 08cd8f907..6b845caf7 100644 --- a/gcloud/alpha/compute/instances/detach-disk +++ b/gcloud/alpha/compute/instances/detach-disk @@ -19,7 +19,7 @@ DESCRIPTION $ sudo umount /dev/disk/by-id/google-DEVICE_NAME EXAMPLES - To detach a disk named 'my-disk' to an instance named 'my-instance', run: + To detach a disk named 'my-disk' from an instance named 'my-instance', run: $ gcloud alpha compute instances detach-disk my-instance \ --disk=my-disk diff --git a/gcloud/alpha/compute/queued-resources/create b/gcloud/alpha/compute/queued-resources/create index 5221d772c..4d3ee1f63 100644 --- a/gcloud/alpha/compute/queued-resources/create +++ b/gcloud/alpha/compute/queued-resources/create @@ -10,6 +10,7 @@ SYNOPSIS [--accelerator=[count=COUNT],[type=TYPE]] [--no-address] [--async] [--no-boot-disk-auto-delete] [--boot-disk-device-name=BOOT_DISK_DEVICE_NAME] + [--boot-disk-interface=BOOT_DISK_INTERFACE] [--boot-disk-provisioned-iops=BOOT_DISK_PROVISIONED_IOPS] [--boot-disk-provisioned-throughput=BOOT_DISK_PROVISIONED_THROUGHPUT] [--boot-disk-size=BOOT_DISK_SIZE] [--boot-disk-type=BOOT_DISK_TYPE] @@ -149,6 +150,12 @@ OPTIONAL FLAGS option can only be specified if a new boot disk is being created (as opposed to mounting an existing persistent disk). + --boot-disk-interface=BOOT_DISK_INTERFACE + Indicates the interface to use for the boot disk. The value must be one + of the following: + ◆ SCSI + ◆ NVME + --boot-disk-provisioned-iops=BOOT_DISK_PROVISIONED_IOPS Indicates how many IOPS to provision for the disk. This sets the number of I/O operations per second that the disk can handle. Value must be @@ -280,6 +287,12 @@ OPTIONAL FLAGS The name of the storage pool in which the new disk is created. The new disk and the storage pool must be in the same location. + interface + The interface to use with the disk. The value must be one of the + following: + ▸ SCSI + ▸ NVME + boot If yes, indicates that this is a boot disk. The instance will use the first partition of the disk for its root file system. The diff --git a/gcloud/alpha/container/clusters/create b/gcloud/alpha/container/clusters/create index b8a6f6544..cdcb5b2c3 100644 --- a/gcloud/alpha/container/clusters/create +++ b/gcloud/alpha/container/clusters/create @@ -474,7 +474,8 @@ FLAGS --enable-cloud-logging is also deprecated and will be removed in an upcoming release. Please use --logging (optionally with --monitoring). For more details, please read: - https://cloud.google.com/stackdriver/docs/solutions/gke/installing. + https://cloud.google.com/kubernetes-engine/docs/concepts/about-logs and + https://cloud.google.com/kubernetes-engine/docs/how-to/configure-metrics. --enable-cloud-monitoring (DEPRECATED) Automatically send metrics from pods in the cluster to the @@ -484,7 +485,9 @@ FLAGS Legacy Logging and Monitoring is deprecated. Thus, flag --enable-cloud-monitoring is also deprecated. Please use --monitoring (optionally with --logging). For more details, please read: - https://cloud.google.com/stackdriver/docs/solutions/gke/installing. + https://cloud.google.com/kubernetes-engine/docs/how-to/configure-metrics + and + https://cloud.google.com/kubernetes-engine/docs/concepts/about-logs. --enable-cloud-run-alpha Enable Cloud Run alpha features on this cluster. Selecting this option @@ -615,7 +618,8 @@ FLAGS The --enable-logging-monitoring-system-only flag is deprecated and will be removed in an upcoming release. Please use --logging and --monitoring instead. For more information, please read: - https://cloud.google.com/stackdriver/docs/solutions/gke/installing. + https://cloud.google.com/kubernetes-engine/docs/concepts/about-logs and + https://cloud.google.com/kubernetes-engine/docs/how-to/configure-metrics. --enable-managed-prometheus Enables managed collection for Managed Service for Prometheus in the @@ -685,7 +689,8 @@ FLAGS The --enable-stackdriver-kubernetes flag is deprecated and will be removed in an upcoming release. Please use --logging and --monitoring instead. For more information, please read: - https://cloud.google.com/stackdriver/docs/solutions/gke/installing. + https://cloud.google.com/kubernetes-engine/docs/concepts/about-logs and + https://cloud.google.com/kubernetes-engine/docs/how-to/configure-metrics. Flags for vertical pod autoscaling: @@ -792,7 +797,7 @@ FLAGS are: SYSTEM, WORKLOAD, API_SERVER, CONTROLLER_MANAGER, SCHEDULER, NONE For more information, see - https://cloud.google.com/stackdriver/docs/solutions/gke/installing#available-logs + https://cloud.google.com/kubernetes-engine/docs/concepts/about-logs#available-logs Examples: @@ -936,7 +941,7 @@ FLAGS STATEFULSET, STORAGE, CADVISOR, KUBELET, DCGM For more information, see - https://cloud.google.com/stackdriver/docs/solutions/gke/installing#available-metrics + https://cloud.google.com/kubernetes-engine/docs/how-to/configure-metrics#available-metrics Examples: diff --git a/gcloud/alpha/container/clusters/create-auto b/gcloud/alpha/container/clusters/create-auto index 8175c9ef1..ab93c1608 100644 --- a/gcloud/alpha/container/clusters/create-auto +++ b/gcloud/alpha/container/clusters/create-auto @@ -290,7 +290,7 @@ FLAGS be included. For more information, see - https://cloud.google.com/stackdriver/docs/solutions/gke/installing#available-logs + https://cloud.google.com/kubernetes-engine/docs/concepts/about-logs#available-logs Examples: @@ -308,7 +308,7 @@ FLAGS STATEFULSET, STORAGE, CADVISOR, KUBELET, DCGM For more information, see - https://cloud.google.com/stackdriver/docs/solutions/gke/installing#available-metrics + https://cloud.google.com/kubernetes-engine/docs/how-to/configure-metrics#available-metrics Examples: diff --git a/gcloud/alpha/container/clusters/update b/gcloud/alpha/container/clusters/update index 3e7c6e2b6..4729963b2 100644 --- a/gcloud/alpha/container/clusters/update +++ b/gcloud/alpha/container/clusters/update @@ -375,7 +375,9 @@ REQUIRED FLAGS The --enable-logging-monitoring-system-only flag is deprecated and will be removed in an upcoming release. Please use --logging and --monitoring instead. For more information, please read: - https://cloud.google.com/stackdriver/docs/solutions/gke/installing. + https://cloud.google.com/kubernetes-engine/docs/concepts/about-logs + and + https://cloud.google.com/kubernetes-engine/docs/how-to/configure-metrics. --enable-master-authorized-networks Allow only specified set of CIDR blocks (specified by the @@ -451,7 +453,9 @@ REQUIRED FLAGS The --enable-stackdriver-kubernetes flag is deprecated and will be removed in an upcoming release. Please use --logging and --monitoring instead. For more information, please read: - https://cloud.google.com/stackdriver/docs/solutions/gke/installing. + https://cloud.google.com/kubernetes-engine/docs/concepts/about-logs + and + https://cloud.google.com/kubernetes-engine/docs/how-to/configure-metrics. Flags for vertical pod autoscaling: @@ -1374,7 +1378,7 @@ REQUIRED FLAGS NONE For more information, see - https://cloud.google.com/stackdriver/docs/solutions/gke/installing#available-logs + https://cloud.google.com/kubernetes-engine/docs/concepts/about-logs#available-logs Examples: @@ -1390,7 +1394,7 @@ REQUIRED FLAGS STATEFULSET, STORAGE, CADVISOR, KUBELET, DCGM For more information, see - https://cloud.google.com/stackdriver/docs/solutions/gke/installing#available-metrics + https://cloud.google.com/kubernetes-engine/docs/how-to/configure-metrics#available-metrics Examples: @@ -1424,7 +1428,7 @@ REQUIRED FLAGS The --logging-service flag is deprecated and will be removed in an upcoming release. Please use --logging instead. For more information, please read: - https://cloud.google.com/stackdriver/docs/solutions/gke/installing. + https://cloud.google.com/kubernetes-engine/docs/concepts/about-logs. --monitoring-service=MONITORING_SERVICE (DEPRECATED) Monitoring service to use for the cluster. Options are: @@ -1436,7 +1440,7 @@ REQUIRED FLAGS The --monitoring-service flag is deprecated and will be removed in an upcoming release. Please use --monitoring instead. For more information, please read: - https://cloud.google.com/stackdriver/docs/solutions/gke/installing. + https://cloud.google.com/kubernetes-engine/docs/how-to/configure-metrics. Basic auth diff --git a/gcloud/alpha/container/fleet/memberships/describe b/gcloud/alpha/container/fleet/memberships/describe index af5e18605..db840f728 100644 --- a/gcloud/alpha/container/fleet/memberships/describe +++ b/gcloud/alpha/container/fleet/memberships/describe @@ -17,7 +17,7 @@ EXAMPLES Then describe it: - $ gcloud alpha container fleet memberships describe MEMBERSHIP_NAME + $ gcloud alpha container fleet memberships describe MEMBERSHIP POSITIONAL ARGUMENTS Membership resource - The cluster membership to describe. The arguments in diff --git a/gcloud/alpha/container/hub/memberships/describe b/gcloud/alpha/container/hub/memberships/describe index 6d597f86b..1c05f7ff5 100644 --- a/gcloud/alpha/container/hub/memberships/describe +++ b/gcloud/alpha/container/hub/memberships/describe @@ -17,7 +17,7 @@ EXAMPLES Then describe it: - $ gcloud alpha container hub memberships describe MEMBERSHIP_NAME + $ gcloud alpha container hub memberships describe MEMBERSHIP POSITIONAL ARGUMENTS Membership resource - The cluster membership to describe. The arguments in diff --git a/gcloud/alpha/firestore/databases/create b/gcloud/alpha/firestore/databases/create index 5ed34534d..b9f7d6a3e 100644 --- a/gcloud/alpha/firestore/databases/create +++ b/gcloud/alpha/firestore/databases/create @@ -35,6 +35,13 @@ EXAMPLES $ gcloud alpha firestore databases create --location=nam5 \ --enable-pitr + To create a Firestore Native database in nam5 encrypted by a + Customer-managed encryption key (CMEK). + + $ gcloud alpha firestore databases create --location=nam5 \ + --kms-key-name=projects/PROJECT_ID/locations/us/keyRings/\ + KEY_RING_ID/cryptoKeys/CRYPTO_KEY_ID + REQUIRED FLAGS --location=LOCATION The location to operate on. Available locations are listed at diff --git a/gcloud/alpha/network-connectivity/spokes/delete b/gcloud/alpha/network-connectivity/spokes/delete index aaa9a735d..df57ea9a4 100644 --- a/gcloud/alpha/network-connectivity/spokes/delete +++ b/gcloud/alpha/network-connectivity/spokes/delete @@ -67,7 +67,9 @@ 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. This variant is also available: + access allowlist. These variants are also available: $ gcloud network-connectivity spokes delete + $ gcloud beta network-connectivity spokes delete + diff --git a/gcloud/alpha/network-connectivity/spokes/describe b/gcloud/alpha/network-connectivity/spokes/describe index 955aa0ae6..12aabf967 100644 --- a/gcloud/alpha/network-connectivity/spokes/describe +++ b/gcloud/alpha/network-connectivity/spokes/describe @@ -63,7 +63,9 @@ 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. This variant is also available: + access allowlist. These variants are also available: $ gcloud network-connectivity spokes describe + $ gcloud beta network-connectivity spokes describe + diff --git a/gcloud/alpha/network-connectivity/spokes/list b/gcloud/alpha/network-connectivity/spokes/list index 72cd25ca6..483981ae0 100644 --- a/gcloud/alpha/network-connectivity/spokes/list +++ b/gcloud/alpha/network-connectivity/spokes/list @@ -77,7 +77,9 @@ 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. This variant is also available: + access allowlist. These variants are also available: $ gcloud network-connectivity spokes list + $ gcloud beta network-connectivity spokes list + diff --git a/gcloud/alpha/recommender/recommendations/list b/gcloud/alpha/recommender/recommendations/list index 04111aa08..d37c61848 100644 --- a/gcloud/alpha/recommender/recommendations/list +++ b/gcloud/alpha/recommender/recommendations/list @@ -18,8 +18,6 @@ DESCRIPTION respectively, are listed. If the --recursive flag is set, recommendations for child resources and projects are also listed. Supported recommenders can be found here: https://cloud.google.com/recommender/docs/recommenders. - The following Google Cloud resources are supported: project, - billing_account, folder and organization. EXAMPLES Lists recommendations for a Cloud project. $ gcloud alpha recommender recommendations list \ @@ -59,17 +57,20 @@ FLAGS https://cloud.google.com/recommender/docs/recommenders --recursive=BOOLEAN_VALUE - By default, --recursive is set to false and can be ommitted. If + By default, --recursive is set to false and can be omitted. If --recursive=true is used, in addition to listing the recommendations - for the specified organization, billing account, or folder, recursively - list all of the recommendations for that resource's child resources, - including their descendents (for example, a folder's sub-folders), and - for that resource's child projects. For example, when using the - --recursive flag and specifying an organization, the response lists all - of the recommendations associated with that organization, all of the + for the specified organization or folder, recursively lists all of the + recommendations for the resource's child resources, including their + descendents (for example, a folder's sub-folders), and for the + resource's child projects. For example, when using the --recursive flag + and specifying an organization, the response lists all of the + recommendations associated with that organization, all of the recommendations associated with that organization's folders and sub-folders, and all of the recommendations associated with that - organization's child projects. + organization's child projects. The maximum number of resources + (organization, folders, projects, and descendant resources) that can be + accessed at once with the --recursive flag is 100. For a larger number + of nested resources, use BigQuery Export. LIST COMMAND FLAGS --filter=EXPRESSION diff --git a/gcloud/alpha/run/deploy b/gcloud/alpha/run/deploy index 84995d526..8a41ed314 100644 --- a/gcloud/alpha/run/deploy +++ b/gcloud/alpha/run/deploy @@ -30,8 +30,7 @@ SYNOPSIS --execution-environment=EXECUTION_ENVIRONMENT --[no-]invoker-iam-check --max-surge=MAX_SURGE --remove-containers=[CONTAINER,...] --revision-suffix=REVISION_SUFFIX - --scaling-mode=SCALING_MODE - --service-max-instances=SERVICE_MAX_INSTANCES + --scaling=SCALING --service-max-instances=SERVICE_MAX_INSTANCES --service-min-instances=SERVICE_MIN_INSTANCES --[no-]session-affinity --vpc-connector=VPC_CONNECTOR --vpc-egress=VPC_EGRESS --add-cloudsql-instances=[CLOUDSQL-INSTANCES,...] @@ -484,9 +483,8 @@ FLAGS to a revision named 'helloworld-v1'. Set empty string to clear the suffix and resume server-assigned naming. - --scaling-mode=SCALING_MODE - The scaling mode to use for this resource. SCALING_MODE must be one - of: + --scaling=SCALING + The scaling mode to use for this resource. SCALING must be one of: automatic The number of instances is scaled automatically based on the diff --git a/gcloud/alpha/run/services/update b/gcloud/alpha/run/services/update index 2d87ce72c..fc2c43b55 100644 --- a/gcloud/alpha/run/services/update +++ b/gcloud/alpha/run/services/update @@ -25,8 +25,7 @@ SYNOPSIS --execution-environment=EXECUTION_ENVIRONMENT --[no-]invoker-iam-check --max-surge=MAX_SURGE --remove-containers=[CONTAINER,...] --revision-suffix=REVISION_SUFFIX - --scaling-mode=SCALING_MODE - --service-max-instances=SERVICE_MAX_INSTANCES + --scaling=SCALING --service-max-instances=SERVICE_MAX_INSTANCES --service-min-instances=SERVICE_MIN_INSTANCES --[no-]session-affinity --vpc-connector=VPC_CONNECTOR --vpc-egress=VPC_EGRESS --add-cloudsql-instances=[CLOUDSQL-INSTANCES,...] @@ -370,9 +369,8 @@ FLAGS to a revision named 'helloworld-v1'. Set empty string to clear the suffix and resume server-assigned naming. - --scaling-mode=SCALING_MODE - The scaling mode to use for this resource. SCALING_MODE must be one - of: + --scaling=SCALING + The scaling mode to use for this resource. SCALING must be one of: automatic The number of instances is scaled automatically based on the diff --git a/gcloud/alpha/run/workers/deploy b/gcloud/alpha/run/workers/deploy index 5790809fa..0a61d8ae1 100644 --- a/gcloud/alpha/run/workers/deploy +++ b/gcloud/alpha/run/workers/deploy @@ -6,7 +6,7 @@ SYNOPSIS [--breakglass=JUSTIFICATION] [--description=DESCRIPTION] [--max-instances=MAX_INSTANCES] [--max-surge=MAX_SURGE] [--min-instances=MIN_INSTANCES] [--no-promote] [--region=REGION] - [--revision-suffix=REVISION_SUFFIX] [--scaling-mode=SCALING_MODE] + [--revision-suffix=REVISION_SUFFIX] [--scaling=SCALING] [--service-account=SERVICE_ACCOUNT] [--vpc-egress=VPC_EGRESS] [--add-cloudsql-instances=[CLOUDSQL-INSTANCES,...] | --clear-cloudsql-instances @@ -123,8 +123,8 @@ FLAGS a revision named 'helloworld-v1'. Set empty string to clear the suffix and resume server-assigned naming. - --scaling-mode=SCALING_MODE - The scaling mode to use for this resource. SCALING_MODE must be one of: + --scaling=SCALING + The scaling mode to use for this resource. SCALING must be one of: automatic The number of instances is scaled automatically based on the usage diff --git a/gcloud/alpha/run/workers/update b/gcloud/alpha/run/workers/update index b1391f496..4ce335589 100644 --- a/gcloud/alpha/run/workers/update +++ b/gcloud/alpha/run/workers/update @@ -7,7 +7,7 @@ SYNOPSIS [--breakglass=JUSTIFICATION] [--description=DESCRIPTION] [--max-instances=MAX_INSTANCES] [--max-surge=MAX_SURGE] [--min-instances=MIN_INSTANCES] [--no-promote] [--region=REGION] - [--revision-suffix=REVISION_SUFFIX] [--scaling-mode=SCALING_MODE] + [--revision-suffix=REVISION_SUFFIX] [--scaling=SCALING] [--service-account=SERVICE_ACCOUNT] [--[no-]session-affinity] [--vpc-egress=VPC_EGRESS] [--add-cloudsql-instances=[CLOUDSQL-INSTANCES,...] @@ -124,8 +124,8 @@ FLAGS a revision named 'helloworld-v1'. Set empty string to clear the suffix and resume server-assigned naming. - --scaling-mode=SCALING_MODE - The scaling mode to use for this resource. SCALING_MODE must be one of: + --scaling=SCALING + The scaling mode to use for this resource. SCALING must be one of: automatic The number of instances is scaled automatically based on the usage diff --git a/gcloud/alpha/scc/findings/bulk-mute b/gcloud/alpha/scc/findings/bulk-mute index 5e4ff16fc..567eb22e3 100644 --- a/gcloud/alpha/scc/findings/bulk-mute +++ b/gcloud/alpha/scc/findings/bulk-mute @@ -6,7 +6,7 @@ SYNOPSIS gcloud alpha scc findings bulk-mute (--folder=FOLDER | --organization=ORGANIZATION | --project=PROJECT) [--filter=FILTER] [--location=LOCATION; default="global"] - [GCLOUD_WIDE_FLAG ...] + [--mute-state=MUTE_STATE; default="muted"] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Bulk mute Security Command Center findings based on a filter. @@ -68,6 +68,10 @@ OPTIONAL FLAGS location that is specified when data residency controls are enabled for Security Command Center. + --mute-state=MUTE_STATE; default="muted" + Desired mute state of the finding. MUTE_STATE must be one of: muted, + undefined. + GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, diff --git a/gcloud/alpha/scc/findings/set-mute b/gcloud/alpha/scc/findings/set-mute index c590cc337..d9832476b 100644 --- a/gcloud/alpha/scc/findings/set-mute +++ b/gcloud/alpha/scc/findings/set-mute @@ -49,7 +49,8 @@ POSITIONAL ARGUMENTS REQUIRED FLAGS --mute=MUTE - Desired mute state of the finding. MUTE must be one of: muted, unmuted. + Desired mute state of the finding. MUTE must be one of: muted, unmuted, + undefined. OPTIONAL FLAGS --location=LOCATION; default="global" diff --git a/gcloud/alpha/scc/iac-validation-reports/describe b/gcloud/alpha/scc/iac-validation-reports/describe new file mode 100644 index 000000000..c919624fb --- /dev/null +++ b/gcloud/alpha/scc/iac-validation-reports/describe @@ -0,0 +1,80 @@ +NAME + gcloud alpha scc iac-validation-reports describe - describe a Cloud + Security Command Center IaC Validation Report + +SYNOPSIS + gcloud alpha scc iac-validation-reports describe + (REPORT : --location=LOCATION --organization=ORGANIZATION) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Describe a Cloud Security Command Center (SCC) IaC Validation + Report. Takes the name of the report as an argument. + + Returns IAC Validation Report as response. + +EXAMPLES + Describe an IAC Validation report named + organizations/123/locations/global/reports/abcef-gh : + + $ gcloud alpha scc iac-validation-reports describe \ + organizations/123/locations/global/reports/abcef-gh + + or, run: + + $ gcloud alpha scc iac-validation-reports describe abcef-gh \ + --organization=123 --location=global + +POSITIONAL ARGUMENTS + Report resource - IAC Validation report to be described. For example + organizations/123/locations/global/reports/abcef-gh. The arguments in this + group can be used to specify the attributes of this resource. + + This must be specified. + + REPORT + ID of the report or fully qualified identifier for the report. + + To set the report attribute: + ▸ provide the argument report on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + ID of the location where the resource exists (for example, global). + + To set the location attribute: + ▸ provide the argument report on the command line with a fully + specified name; + ▸ provide the argument --location on the command line. + + --organization=ORGANIZATION + ID of the organization which is the parent of the resource. + + To set the organization attribute: + ▸ provide the argument report on the command line with a fully + specified name; + ▸ provide the argument --organization on the command line. + +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. + +API REFERENCE + This command uses the securityposture/v1alpha API. The full documentation + for this API can be found at: + https://cloud.google.com/security-command-center + +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. This variant is also available: + + $ gcloud scc iac-validation-reports describe + diff --git a/gcloud/alpha/scc/iac-validation-reports/help b/gcloud/alpha/scc/iac-validation-reports/help index 0f93c627a..e1c598222 100644 --- a/gcloud/alpha/scc/iac-validation-reports/help +++ b/gcloud/alpha/scc/iac-validation-reports/help @@ -20,6 +20,14 @@ COMMANDS (ALPHA) Create a Cloud Security Command Center (SCC) IaC Validation Report. + describe + (ALPHA) Describe a Cloud Security Command Center (SCC) IaC Validation + Report. + + list + (ALPHA) Lists all the Cloud Security Command Center (SCC) IaC + validation reports for an organization. + NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct diff --git a/gcloud/alpha/scc/iac-validation-reports/list b/gcloud/alpha/scc/iac-validation-reports/list new file mode 100644 index 000000000..e95d9f5ff --- /dev/null +++ b/gcloud/alpha/scc/iac-validation-reports/list @@ -0,0 +1,72 @@ +NAME + gcloud alpha scc iac-validation-reports list - lists all the Cloud Security + Command Center IaC validation reports for an organization + +SYNOPSIS + gcloud alpha scc iac-validation-reports list PARENT [--filter=EXPRESSION] + [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Lists all the Cloud Security Command Center (SCC) IaC validation + reports for an organization. + +EXAMPLES + To list Cloud Security Command Center IaC validation reports for + organization 123 in the global location, run: + + $ gcloud alpha scc iac-validation-reports list \ + organizations/123/locations/global/reports + +POSITIONAL ARGUMENTS + PARENT + Parent of IaC validation reports. Formatted as + organizations//locations//reports. + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + +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. + +API REFERENCE + This command uses the securityposture/v1alpha API. The full documentation + for this API can be found at: + https://cloud.google.com/security-command-center + +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. This variant is also available: + + $ gcloud scc iac-validation-reports list + diff --git a/gcloud/alpha/scc/muteconfigs/create b/gcloud/alpha/scc/muteconfigs/create index 94e3b2627..07eea672c 100644 --- a/gcloud/alpha/scc/muteconfigs/create +++ b/gcloud/alpha/scc/muteconfigs/create @@ -4,7 +4,8 @@ NAME SYNOPSIS gcloud alpha scc muteconfigs create MUTE_CONFIG [--description=DESCRIPTION] - [--filter=FILTER] [--location=LOCATION; default="global"] + [--expiry-time=EXPIRY_TIME] [--filter=FILTER] + [--location=LOCATION; default="global"] [--type=TYPE; default="static"] [--folder=FOLDER | --organization=ORGANIZATION | --project=PROJECT] [GCLOUD_WIDE_FLAG ...] @@ -48,6 +49,12 @@ FLAGS --description=DESCRIPTION The text that will be used to describe a mute configuration. + --expiry-time=EXPIRY_TIME + The expiry of the mute config. Only applicable for dynamic configs. If + the expiry is set, when the config expires, it is removed from all + findings. See $ gcloud topic datetimes for information on supported + time formats. + --filter=FILTER The filter string which will applied to findings muted by a mute configuration. @@ -63,6 +70,10 @@ FLAGS location that is specified when data residency controls are enabled for Security Command Center. + --type=TYPE; default="static" + The mute configuration type. Immutable after creation. TYPE must be one + of: static, dynamic. + At most one of these can be specified: --folder=FOLDER diff --git a/gcloud/alpha/scc/muteconfigs/update b/gcloud/alpha/scc/muteconfigs/update index 6486fb46e..49caf14c4 100644 --- a/gcloud/alpha/scc/muteconfigs/update +++ b/gcloud/alpha/scc/muteconfigs/update @@ -4,8 +4,8 @@ NAME SYNOPSIS gcloud alpha scc muteconfigs update MUTE_CONFIG [--description=DESCRIPTION] - [--filter=FILTER] [--location=LOCATION; default="global"] - [--update-mask=UPDATE_MASK] + [--expiry-time=EXPIRY_TIME] [--filter=FILTER] + [--location=LOCATION; default="global"] [--update-mask=UPDATE_MASK] [--folder=FOLDER | --organization=ORGANIZATION | --project=PROJECT] [GCLOUD_WIDE_FLAG ...] @@ -49,6 +49,12 @@ FLAGS --description=DESCRIPTION The text that will be used to describe a mute configuration. + --expiry-time=EXPIRY_TIME + The expiry of the mute config. Only applicable for dynamic configs. If + the expiry is set, when the config expires, it is removed from all + findings. See $ gcloud topic datetimes for information on supported + time formats. + --filter=FILTER The filter string which will applied to findings muted by a mute configuration. diff --git a/gcloud/alpha/sql/instances/switchover b/gcloud/alpha/sql/instances/switchover index 468817e09..e1e49a260 100644 --- a/gcloud/alpha/sql/instances/switchover +++ b/gcloud/alpha/sql/instances/switchover @@ -41,7 +41,9 @@ 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. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud sql instances switchover $ gcloud beta sql instances switchover diff --git a/gcloud/artifacts/generic/download b/gcloud/artifacts/generic/download index 6daa62d4d..59ae9d500 100644 --- a/gcloud/artifacts/generic/download +++ b/gcloud/artifacts/generic/download @@ -4,8 +4,9 @@ NAME SYNOPSIS gcloud artifacts generic download --destination=DESTINATION - --package=ARTIFACT --version=VERSION [--name=NAME] - [--location=LOCATION --repository=REPOSITORY] [GCLOUD_WIDE_FLAG ...] + --package=ARTIFACT --version=VERSION [--chunk-size=CHUNK_SIZE] + [--name=NAME] [--location=LOCATION --repository=REPOSITORY] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION Download a generic artifact from a generic artifact repository. @@ -19,6 +20,14 @@ EXAMPLES --version=v0.1.0 --destination=/path/to/destination/ \ --name=myfile.txt + To download version v0.1.0 of myfile.txt in 8000 byte chunks located in a + repository in "us-central1" to /path/to/destination/: + + $ gcloud artifacts generic download --location=us-central1 \ + --project=myproject --repository=myrepo --package=mypackage \ + --version=v0.1.0 --destination=/path/to/destination/ \ + --name=myfile.txt --chunk-size=8000 + To download all files of version v0.1.0 and package mypackage located in a repository in "us-central1" to /path/to/destination/ while maintaining the folder hierarchy: @@ -38,6 +47,10 @@ REQUIRED FLAGS The version of the artifact to download. OPTIONAL FLAGS + --chunk-size=CHUNK_SIZE + If specified, the chunk size (bytes) to use for downloading the + package. + --name=NAME If specified, the file name within the artifact to download. diff --git a/gcloud/beta/artifacts/generic/download b/gcloud/beta/artifacts/generic/download index e07f9f8a7..c54296809 100644 --- a/gcloud/beta/artifacts/generic/download +++ b/gcloud/beta/artifacts/generic/download @@ -4,8 +4,9 @@ NAME SYNOPSIS gcloud beta artifacts generic download --destination=DESTINATION - --package=ARTIFACT --version=VERSION [--name=NAME] - [--location=LOCATION --repository=REPOSITORY] [GCLOUD_WIDE_FLAG ...] + --package=ARTIFACT --version=VERSION [--chunk-size=CHUNK_SIZE] + [--name=NAME] [--location=LOCATION --repository=REPOSITORY] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) Download a generic artifact from a generic artifact repository. @@ -19,6 +20,14 @@ EXAMPLES --version=v0.1.0 --destination=/path/to/destination/ \ --name=myfile.txt + To download version v0.1.0 of myfile.txt in 8000 byte chunks located in a + repository in "us-central1" to /path/to/destination/: + + $ gcloud beta artifacts generic download --location=us-central1 \ + --project=myproject --repository=myrepo --package=mypackage \ + --version=v0.1.0 --destination=/path/to/destination/ \ + --name=myfile.txt --chunk-size=8000 + To download all files of version v0.1.0 and package mypackage located in a repository in "us-central1" to /path/to/destination/ while maintaining the folder hierarchy: @@ -38,6 +47,10 @@ REQUIRED FLAGS The version of the artifact to download. OPTIONAL FLAGS + --chunk-size=CHUNK_SIZE + If specified, the chunk size (bytes) to use for downloading the + package. + --name=NAME If specified, the file name within the artifact to download. diff --git a/gcloud/beta/compute/firewall-rules/migrate b/gcloud/beta/compute/firewall-rules/migrate index 7ce56ac3d..a5d84eb1e 100644 --- a/gcloud/beta/compute/firewall-rules/migrate +++ b/gcloud/beta/compute/firewall-rules/migrate @@ -9,6 +9,7 @@ SYNOPSIS | --target-firewall-policy=TARGET_FIREWALL_POLICY) [--exclusion-patterns-file=EXCLUSION_PATTERNS_FILE] [--export-terraform-script] [--force] + [--skip-migrate-target-service-accounts-to-tags] [--tag-mapping-file=TAG_MAPPING_FILE] [--terraform-script-output-file=TERRAFORM_SCRIPT_OUTPUT_FILE] [GCLOUD_WIDE_FLAG ...] @@ -63,6 +64,10 @@ OPTIONAL FLAGS If set, migration will succeed even if the tool detects that original rule evaluation order cannot be preserved. + --skip-migrate-target-service-accounts-to-tags + If set, migration will keep target service accounts as they are and + will not try to replace them with secure tags. + --tag-mapping-file=TAG_MAPPING_FILE Path to a JSON file with legacy tags and service accounts to secure tags mapping. diff --git a/gcloud/beta/compute/instance-templates/create b/gcloud/beta/compute/instance-templates/create index ef754c4c0..1348b9e70 100644 --- a/gcloud/beta/compute/instance-templates/create +++ b/gcloud/beta/compute/instance-templates/create @@ -6,14 +6,15 @@ SYNOPSIS gcloud beta compute instance-templates create NAME [--accelerator=[count=COUNT],[type=TYPE]] [--no-boot-disk-auto-delete] [--boot-disk-device-name=BOOT_DISK_DEVICE_NAME] + [--boot-disk-interface=BOOT_DISK_INTERFACE] [--boot-disk-provisioned-iops=BOOT_DISK_PROVISIONED_IOPS] [--boot-disk-provisioned-throughput=BOOT_DISK_PROVISIONED_THROUGHPUT] [--boot-disk-size=BOOT_DISK_SIZE] [--boot-disk-type=BOOT_DISK_TYPE] [--can-ip-forward] [--configure-disk=[PROPERTY=VALUE,...]] [--create-disk=[PROPERTY=VALUE,...]] [--description=DESCRIPTION] [--discard-local-ssds-at-termination-timestamp=DISCARD_LOCAL_SSDS_AT_TERMINATION_TIMESTAMP] - [--disk=[auto-delete=AUTO-DELETE], - [boot=BOOT],[device-name=DEVICE-NAME],[mode=MODE],[name=NAME]] + [--disk=[auto-delete=AUTO-DELETE],[boot=BOOT],[device-name=DEVICE-NAME], + [interface=INTERFACE],[mode=MODE],[name=NAME]] [--[no-]enable-nested-virtualization] [--[no-]enable-uefi-networking] [--external-ipv6-address=EXTERNAL_IPV6_ADDRESS] [--external-ipv6-prefix-length=EXTERNAL_IPV6_PREFIX_LENGTH] @@ -120,6 +121,12 @@ FLAGS option can only be specified if a new boot disk is being created (as opposed to mounting an existing persistent disk). + --boot-disk-interface=BOOT_DISK_INTERFACE + Indicates the interface to use for the boot disk. The value must be one + of the following: + ◆ SCSI + ◆ NVME + --boot-disk-provisioned-iops=BOOT_DISK_PROVISIONED_IOPS Indicates how many IOPS to provision for the disk. This sets the number of I/O operations per second that the disk can handle. Value must be @@ -268,6 +275,12 @@ FLAGS The name of the storage pool in which the new disk is created. The new disk and the storage pool must be in the same location. + interface + The interface to use with the disk. The value must be one of the + following: + ▸ SCSI + ▸ NVME + boot If yes, indicates that this is a boot disk. The instance will use the first partition of the disk for its root file system. The @@ -365,15 +378,15 @@ FLAGS For more information about the --discard-local-ssd flag, see https://cloud.google.com/compute/docs/disks/local-ssd#stop_instance. - --disk=[auto-delete=AUTO-DELETE],[boot=BOOT],[device-name=DEVICE-NAME],[mode=MODE],[name=NAME] - Attaches an existing persistent disk to the instances. + --disk=[auto-delete=AUTO-DELETE],[boot=BOOT],[device-name=DEVICE-NAME],[interface=INTERFACE],[mode=MODE],[name=NAME] + Attaches an existing disk to the instances. name The disk to attach to the instances. If you create more than one instance, you can only attach a disk in read-only mode. By default, - you attach a zonal persistent disk located in the same zone of the - instance. If you want to attach a regional persistent disk, you - must specify the disk using its URI; for example, + you attach a zonal disk located in the same zone of the instance. + If you want to attach a regional disk, you must specify the disk + using its URI; for example, projects/myproject/regions/us-central1/disks/my-regional-disk. mode @@ -396,7 +409,13 @@ FLAGS If set to yes, the persistent disk is automatically deleted when the instance is deleted. However, if you detach the disk from the instance, deleting the instance doesn't delete the disk. The - default value for this is yes. + default value is yes. + + interface + The interface to use for the disk. The value must be one of the + following: + ▸ SCSI + ▸ NVME --[no-]enable-nested-virtualization If set to true, enables nested virtualization for the instance. Use diff --git a/gcloud/beta/compute/instance-templates/create-with-container b/gcloud/beta/compute/instance-templates/create-with-container index 4752b0e42..2e341810e 100644 --- a/gcloud/beta/compute/instance-templates/create-with-container +++ b/gcloud/beta/compute/instance-templates/create-with-container @@ -7,6 +7,7 @@ SYNOPSIS gcloud beta compute instance-templates create-with-container NAME [--accelerator=[count=COUNT],[type=TYPE]] [--no-boot-disk-auto-delete] [--boot-disk-device-name=BOOT_DISK_DEVICE_NAME] + [--boot-disk-interface=BOOT_DISK_INTERFACE] [--boot-disk-provisioned-iops=BOOT_DISK_PROVISIONED_IOPS] [--boot-disk-provisioned-throughput=BOOT_DISK_PROVISIONED_THROUGHPUT] [--boot-disk-size=BOOT_DISK_SIZE] [--boot-disk-type=BOOT_DISK_TYPE] @@ -24,8 +25,8 @@ SYNOPSIS [--container-restart-policy=POLICY; default="always"] [--container-stdin] [--container-tty] [--create-disk=[PROPERTY=VALUE,...]] [--description=DESCRIPTION] - [--disk=[auto-delete=AUTO-DELETE], - [boot=BOOT],[device-name=DEVICE-NAME],[mode=MODE],[name=NAME]] + [--disk=[auto-delete=AUTO-DELETE],[boot=BOOT],[device-name=DEVICE-NAME], + [interface=INTERFACE],[mode=MODE],[name=NAME]] [--external-ipv6-address=EXTERNAL_IPV6_ADDRESS] [--external-ipv6-prefix-length=EXTERNAL_IPV6_PREFIX_LENGTH] [--internal-ipv6-address=INTERNAL_IPV6_ADDRESS] @@ -111,6 +112,12 @@ FLAGS option can only be specified if a new boot disk is being created (as opposed to mounting an existing persistent disk). + --boot-disk-interface=BOOT_DISK_INTERFACE + Indicates the interface to use for the boot disk. The value must be one + of the following: + ◆ SCSI + ◆ NVME + --boot-disk-provisioned-iops=BOOT_DISK_PROVISIONED_IOPS Indicates how many IOPS to provision for the disk. This sets the number of I/O operations per second that the disk can handle. Value must be @@ -359,6 +366,12 @@ FLAGS The name of the storage pool in which the new disk is created. The new disk and the storage pool must be in the same location. + interface + The interface to use with the disk. The value must be one of the + following: + ▸ SCSI + ▸ NVME + multi-writer If yes, the disk is created in multi-writer mode so that it can be attached with read-write access to two VMs. The default value is @@ -386,15 +399,15 @@ FLAGS --description=DESCRIPTION Specifies a textual description for the instance template. - --disk=[auto-delete=AUTO-DELETE],[boot=BOOT],[device-name=DEVICE-NAME],[mode=MODE],[name=NAME] - Attaches an existing persistent disk to the instances. + --disk=[auto-delete=AUTO-DELETE],[boot=BOOT],[device-name=DEVICE-NAME],[interface=INTERFACE],[mode=MODE],[name=NAME] + Attaches an existing disk to the instances. name The disk to attach to the instances. If you create more than one instance, you can only attach a disk in read-only mode. By default, - you attach a zonal persistent disk located in the same zone of the - instance. If you want to attach a regional persistent disk, you - must specify the disk using its URI; for example, + you attach a zonal disk located in the same zone of the instance. + If you want to attach a regional disk, you must specify the disk + using its URI; for example, projects/myproject/regions/us-central1/disks/my-regional-disk. mode @@ -421,7 +434,13 @@ FLAGS If set to yes, the persistent disk is automatically deleted when the instance is deleted. However, if you detach the disk from the instance, deleting the instance doesn't delete the disk. The - default value for this is yes. + default value is yes. + + interface + The interface to use for the disk. The value must be one of the + following: + ▸ SCSI + ▸ NVME --external-ipv6-address=EXTERNAL_IPV6_ADDRESS Assigns the given external IPv6 address to the instance that is diff --git a/gcloud/beta/compute/instances/attach-disk b/gcloud/beta/compute/instances/attach-disk index 2d2d56934..0ac3028f4 100644 --- a/gcloud/beta/compute/instances/attach-disk +++ b/gcloud/beta/compute/instances/attach-disk @@ -5,7 +5,8 @@ SYNOPSIS gcloud beta compute instances attach-disk INSTANCE_NAME --disk=DISK [--boot] [--csek-key-file=FILE] [--device-name=DEVICE_NAME] [--disk-scope=DISK_SCOPE; default="zonal"] [--force-attach] - [--mode=MODE; default="rw"] [--zone=ZONE] [GCLOUD_WIDE_FLAG ...] + [--interface=INTERFACE] [--mode=MODE; default="rw"] [--zone=ZONE] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) gcloud beta compute instances attach-disk is used to attach a disk @@ -82,6 +83,14 @@ OPTIONAL FLAGS the previous instance fails at first. The server will continue trying to detach the disk from the previous instance in the background. + --interface=INTERFACE + The interface of the disk. INTERFACE must be one of: + + NVME + NVME + SCSI + SCSI + --mode=MODE; default="rw" Specifies the mode of the disk. MODE must be one of: diff --git a/gcloud/beta/compute/instances/bulk/create b/gcloud/beta/compute/instances/bulk/create index 279ada1e0..9ac5d04b3 100644 --- a/gcloud/beta/compute/instances/bulk/create +++ b/gcloud/beta/compute/instances/bulk/create @@ -9,6 +9,7 @@ SYNOPSIS [--accelerator=[count=COUNT],[type=TYPE]] [--no-address] [--async] [--no-boot-disk-auto-delete] [--boot-disk-device-name=BOOT_DISK_DEVICE_NAME] + [--boot-disk-interface=BOOT_DISK_INTERFACE] [--boot-disk-provisioned-iops=BOOT_DISK_PROVISIONED_IOPS] [--boot-disk-provisioned-throughput=BOOT_DISK_PROVISIONED_THROUGHPUT] [--boot-disk-size=BOOT_DISK_SIZE] [--boot-disk-type=BOOT_DISK_TYPE] @@ -162,6 +163,12 @@ OPTIONAL FLAGS option can only be specified if a new boot disk is being created (as opposed to mounting an existing persistent disk). + --boot-disk-interface=BOOT_DISK_INTERFACE + Indicates the interface to use for the boot disk. The value must be one + of the following: + ◆ SCSI + ◆ NVME + --boot-disk-provisioned-iops=BOOT_DISK_PROVISIONED_IOPS Indicates how many IOPS to provision for the disk. This sets the number of I/O operations per second that the disk can handle. Value must be @@ -293,6 +300,12 @@ OPTIONAL FLAGS The name of the storage pool in which the new disk is created. The new disk and the storage pool must be in the same location. + interface + The interface to use with the disk. The value must be one of the + following: + ▸ SCSI + ▸ NVME + boot If yes, indicates that this is a boot disk. The instance will use the first partition of the disk for its root file system. The diff --git a/gcloud/beta/compute/instances/create b/gcloud/beta/compute/instances/create index 39b4867e2..61485ed75 100644 --- a/gcloud/beta/compute/instances/create +++ b/gcloud/beta/compute/instances/create @@ -5,8 +5,10 @@ NAME SYNOPSIS gcloud beta compute instances create INSTANCE_NAMES [INSTANCE_NAMES ...] [--accelerator=[count=COUNT],[type=TYPE]] [--async] + [--availability-domain=AVAILABILITY_DOMAIN] [--no-boot-disk-auto-delete] [--boot-disk-device-name=BOOT_DISK_DEVICE_NAME] + [--boot-disk-interface=BOOT_DISK_INTERFACE] [--boot-disk-provisioned-iops=BOOT_DISK_PROVISIONED_IOPS] [--boot-disk-provisioned-throughput=BOOT_DISK_PROVISIONED_THROUGHPUT] [--boot-disk-size=BOOT_DISK_SIZE] [--boot-disk-type=BOOT_DISK_TYPE] @@ -15,7 +17,8 @@ SYNOPSIS [--description=DESCRIPTION] [--discard-local-ssds-at-termination-timestamp=DISCARD_LOCAL_SSDS_AT_TERMINATION_TIMESTAMP] [--disk=[auto-delete=AUTO-DELETE],[boot=BOOT],[device-name=DEVICE-NAME], - [force-attach=FORCE-ATTACH],[mode=MODE],[name=NAME],[scope=SCOPE]] + [force-attach=FORCE-ATTACH], + [interface=INTERFACE],[mode=MODE],[name=NAME],[scope=SCOPE]] [--enable-display-device] [--[no-]enable-nested-virtualization] [--[no-]enable-uefi-networking] [--erase-windows-vss-signature] [--external-ipv6-address=EXTERNAL_IPV6_ADDRESS] @@ -156,6 +159,14 @@ FLAGS Return immediately, without waiting for the operation in progress to complete. + --availability-domain=AVAILABILITY_DOMAIN + Specifies the availability domain that this VM instance should be + scheduled on. The number of availability domains that a VM can be + scheduled on is specified when you create the spread placement policy. + + Specify a value from 1 to the number of domains that are available in + your placement policy. + --boot-disk-auto-delete Automatically delete boot disks when their instances are deleted. Enabled by default, use --no-boot-disk-auto-delete to disable. @@ -165,6 +176,12 @@ FLAGS option can only be specified if a new boot disk is being created (as opposed to mounting an existing persistent disk). + --boot-disk-interface=BOOT_DISK_INTERFACE + Indicates the interface to use for the boot disk. The value must be one + of the following: + ◆ SCSI + ◆ NVME + --boot-disk-provisioned-iops=BOOT_DISK_PROVISIONED_IOPS Indicates how many IOPS to provision for the disk. This sets the number of I/O operations per second that the disk can handle. Value must be @@ -289,6 +306,12 @@ FLAGS The name of the storage pool in which the new disk is created. The new disk and the storage pool must be in the same location. + interface + The interface to use with the disk. The value must be one of the + following: + ▸ SCSI + ▸ NVME + boot If yes, indicates that this is a boot disk. The instance will use the first partition of the disk for its root file system. The @@ -411,15 +434,15 @@ FLAGS For more information about the --discard-local-ssd flag, see https://cloud.google.com/compute/docs/disks/local-ssd#stop_instance. - --disk=[auto-delete=AUTO-DELETE],[boot=BOOT],[device-name=DEVICE-NAME],[force-attach=FORCE-ATTACH],[mode=MODE],[name=NAME],[scope=SCOPE] - Attaches an existing persistent disk to the instances. + --disk=[auto-delete=AUTO-DELETE],[boot=BOOT],[device-name=DEVICE-NAME],[force-attach=FORCE-ATTACH],[interface=INTERFACE],[mode=MODE],[name=NAME],[scope=SCOPE] + Attaches an existing disk to the instances. name The disk to attach to the instances. If you create more than one instance, you can only attach a disk in read-only mode. By default, - you attach a zonal persistent disk located in the same zone of the - instance. If you want to attach a regional persistent disk, you - must specify the disk using its URI; for example, + you attach a zonal disk located in the same zone of the instance. + If you want to attach a regional disk, you must specify the disk + using its URI; for example, projects/myproject/regions/us-central1/disks/my-regional-disk. mode @@ -442,7 +465,13 @@ FLAGS If set to yes, the persistent disk is automatically deleted when the instance is deleted. However, if you detach the disk from the instance, deleting the instance doesn't delete the disk. The - default value for this is yes. + default value is yes. + + interface + The interface to use for the disk. The value must be one of the + following: + ▸ SCSI + ▸ NVME scope Can be zonal or regional. If zonal, the disk is interpreted as a diff --git a/gcloud/beta/compute/instances/create-with-container b/gcloud/beta/compute/instances/create-with-container index db002ec86..e652ad048 100644 --- a/gcloud/beta/compute/instances/create-with-container +++ b/gcloud/beta/compute/instances/create-with-container @@ -7,6 +7,7 @@ SYNOPSIS [INSTANCE_NAMES ...] [--accelerator=[count=COUNT],[type=TYPE]] [--no-boot-disk-auto-delete] [--boot-disk-device-name=BOOT_DISK_DEVICE_NAME] + [--boot-disk-interface=BOOT_DISK_INTERFACE] [--boot-disk-provisioned-iops=BOOT_DISK_PROVISIONED_IOPS] [--boot-disk-provisioned-throughput=BOOT_DISK_PROVISIONED_THROUGHPUT] [--boot-disk-size=BOOT_DISK_SIZE] [--boot-disk-type=BOOT_DISK_TYPE] @@ -26,7 +27,8 @@ SYNOPSIS [--create-disk=[PROPERTY=VALUE,...]] [--description=DESCRIPTION] [--discard-local-ssds-at-termination-timestamp=DISCARD_LOCAL_SSDS_AT_TERMINATION_TIMESTAMP] [--disk=[auto-delete=AUTO-DELETE],[boot=BOOT],[device-name=DEVICE-NAME], - [force-attach=FORCE-ATTACH],[mode=MODE],[name=NAME],[scope=SCOPE]] + [force-attach=FORCE-ATTACH], + [interface=INTERFACE],[mode=MODE],[name=NAME],[scope=SCOPE]] [--[no-]enable-nested-virtualization] [--external-ipv6-address=EXTERNAL_IPV6_ADDRESS] [--external-ipv6-prefix-length=EXTERNAL_IPV6_PREFIX_LENGTH] @@ -125,6 +127,12 @@ FLAGS option can only be specified if a new boot disk is being created (as opposed to mounting an existing persistent disk). + --boot-disk-interface=BOOT_DISK_INTERFACE + Indicates the interface to use for the boot disk. The value must be one + of the following: + ◆ SCSI + ◆ NVME + --boot-disk-provisioned-iops=BOOT_DISK_PROVISIONED_IOPS Indicates how many IOPS to provision for the disk. This sets the number of I/O operations per second that the disk can handle. Value must be @@ -368,6 +376,12 @@ FLAGS The name of the storage pool in which the new disk is created. The new disk and the storage pool must be in the same location. + interface + The interface to use with the disk. The value must be one of the + following: + ▸ SCSI + ▸ NVME + multi-writer If yes, the disk is created in multi-writer mode so that it can be attached with read-write access to two VMs. The default value is @@ -409,15 +423,15 @@ FLAGS For more information about the --discard-local-ssd flag, see https://cloud.google.com/compute/docs/disks/local-ssd#stop_instance. - --disk=[auto-delete=AUTO-DELETE],[boot=BOOT],[device-name=DEVICE-NAME],[force-attach=FORCE-ATTACH],[mode=MODE],[name=NAME],[scope=SCOPE] - Attaches an existing persistent disk to the instances. + --disk=[auto-delete=AUTO-DELETE],[boot=BOOT],[device-name=DEVICE-NAME],[force-attach=FORCE-ATTACH],[interface=INTERFACE],[mode=MODE],[name=NAME],[scope=SCOPE] + Attaches an existing disk to the instances. name The disk to attach to the instances. If you create more than one instance, you can only attach a disk in read-only mode. By default, - you attach a zonal persistent disk located in the same zone of the - instance. If you want to attach a regional persistent disk, you - must specify the disk using its URI; for example, + you attach a zonal disk located in the same zone of the instance. + If you want to attach a regional disk, you must specify the disk + using its URI; for example, projects/myproject/regions/us-central1/disks/my-regional-disk. mode @@ -444,7 +458,13 @@ FLAGS If set to yes, the persistent disk is automatically deleted when the instance is deleted. However, if you detach the disk from the instance, deleting the instance doesn't delete the disk. The - default value for this is yes. + default value is yes. + + interface + The interface to use for the disk. The value must be one of the + following: + ▸ SCSI + ▸ NVME scope Can be zonal or regional. If zonal, the disk is interpreted as a diff --git a/gcloud/beta/compute/instances/detach-disk b/gcloud/beta/compute/instances/detach-disk index 4b89cbf9d..c0ad8ac25 100644 --- a/gcloud/beta/compute/instances/detach-disk +++ b/gcloud/beta/compute/instances/detach-disk @@ -19,7 +19,7 @@ DESCRIPTION $ sudo umount /dev/disk/by-id/google-DEVICE_NAME EXAMPLES - To detach a disk named 'my-disk' to an instance named 'my-instance', run: + To detach a disk named 'my-disk' from an instance named 'my-instance', run: $ gcloud beta compute instances detach-disk my-instance \ --disk=my-disk diff --git a/gcloud/beta/container/clusters/create b/gcloud/beta/container/clusters/create index f67dec779..a54418fde 100644 --- a/gcloud/beta/container/clusters/create +++ b/gcloud/beta/container/clusters/create @@ -469,7 +469,8 @@ FLAGS --enable-cloud-logging is also deprecated and will be removed in an upcoming release. Please use --logging (optionally with --monitoring). For more details, please read: - https://cloud.google.com/stackdriver/docs/solutions/gke/installing. + https://cloud.google.com/kubernetes-engine/docs/concepts/about-logs and + https://cloud.google.com/kubernetes-engine/docs/how-to/configure-metrics. --enable-cloud-monitoring (DEPRECATED) Automatically send metrics from pods in the cluster to the @@ -479,7 +480,9 @@ FLAGS Legacy Logging and Monitoring is deprecated. Thus, flag --enable-cloud-monitoring is also deprecated. Please use --monitoring (optionally with --logging). For more details, please read: - https://cloud.google.com/stackdriver/docs/solutions/gke/installing. + https://cloud.google.com/kubernetes-engine/docs/how-to/configure-metrics + and + https://cloud.google.com/kubernetes-engine/docs/concepts/about-logs. --enable-cloud-run-alpha Enable Cloud Run alpha features on this cluster. Selecting this option @@ -610,7 +613,8 @@ FLAGS The --enable-logging-monitoring-system-only flag is deprecated and will be removed in an upcoming release. Please use --logging and --monitoring instead. For more information, please read: - https://cloud.google.com/stackdriver/docs/solutions/gke/installing. + https://cloud.google.com/kubernetes-engine/docs/concepts/about-logs and + https://cloud.google.com/kubernetes-engine/docs/how-to/configure-metrics. --enable-managed-prometheus Enables managed collection for Managed Service for Prometheus in the @@ -680,7 +684,8 @@ FLAGS The --enable-stackdriver-kubernetes flag is deprecated and will be removed in an upcoming release. Please use --logging and --monitoring instead. For more information, please read: - https://cloud.google.com/stackdriver/docs/solutions/gke/installing. + https://cloud.google.com/kubernetes-engine/docs/concepts/about-logs and + https://cloud.google.com/kubernetes-engine/docs/how-to/configure-metrics. Flags for vertical pod autoscaling: @@ -773,7 +778,7 @@ FLAGS are: SYSTEM, WORKLOAD, API_SERVER, CONTROLLER_MANAGER, SCHEDULER, NONE For more information, see - https://cloud.google.com/stackdriver/docs/solutions/gke/installing#available-logs + https://cloud.google.com/kubernetes-engine/docs/concepts/about-logs#available-logs Examples: @@ -917,7 +922,7 @@ FLAGS STATEFULSET, STORAGE, CADVISOR, KUBELET, DCGM For more information, see - https://cloud.google.com/stackdriver/docs/solutions/gke/installing#available-metrics + https://cloud.google.com/kubernetes-engine/docs/how-to/configure-metrics#available-metrics Examples: diff --git a/gcloud/beta/container/clusters/create-auto b/gcloud/beta/container/clusters/create-auto index 58a7951d0..79249f67d 100644 --- a/gcloud/beta/container/clusters/create-auto +++ b/gcloud/beta/container/clusters/create-auto @@ -289,7 +289,7 @@ FLAGS be included. For more information, see - https://cloud.google.com/stackdriver/docs/solutions/gke/installing#available-logs + https://cloud.google.com/kubernetes-engine/docs/concepts/about-logs#available-logs Examples: @@ -307,7 +307,7 @@ FLAGS STATEFULSET, STORAGE, CADVISOR, KUBELET, DCGM For more information, see - https://cloud.google.com/stackdriver/docs/solutions/gke/installing#available-metrics + https://cloud.google.com/kubernetes-engine/docs/how-to/configure-metrics#available-metrics Examples: diff --git a/gcloud/beta/container/clusters/update b/gcloud/beta/container/clusters/update index 82b407ec4..446b299d6 100644 --- a/gcloud/beta/container/clusters/update +++ b/gcloud/beta/container/clusters/update @@ -373,7 +373,9 @@ REQUIRED FLAGS The --enable-logging-monitoring-system-only flag is deprecated and will be removed in an upcoming release. Please use --logging and --monitoring instead. For more information, please read: - https://cloud.google.com/stackdriver/docs/solutions/gke/installing. + https://cloud.google.com/kubernetes-engine/docs/concepts/about-logs + and + https://cloud.google.com/kubernetes-engine/docs/how-to/configure-metrics. --enable-master-authorized-networks Allow only specified set of CIDR blocks (specified by the @@ -449,7 +451,9 @@ REQUIRED FLAGS The --enable-stackdriver-kubernetes flag is deprecated and will be removed in an upcoming release. Please use --logging and --monitoring instead. For more information, please read: - https://cloud.google.com/stackdriver/docs/solutions/gke/installing. + https://cloud.google.com/kubernetes-engine/docs/concepts/about-logs + and + https://cloud.google.com/kubernetes-engine/docs/how-to/configure-metrics. Flags for vertical pod autoscaling: @@ -1353,7 +1357,7 @@ REQUIRED FLAGS NONE For more information, see - https://cloud.google.com/stackdriver/docs/solutions/gke/installing#available-logs + https://cloud.google.com/kubernetes-engine/docs/concepts/about-logs#available-logs Examples: @@ -1369,7 +1373,7 @@ REQUIRED FLAGS STATEFULSET, STORAGE, CADVISOR, KUBELET, DCGM For more information, see - https://cloud.google.com/stackdriver/docs/solutions/gke/installing#available-metrics + https://cloud.google.com/kubernetes-engine/docs/how-to/configure-metrics#available-metrics Examples: @@ -1403,7 +1407,7 @@ REQUIRED FLAGS The --logging-service flag is deprecated and will be removed in an upcoming release. Please use --logging instead. For more information, please read: - https://cloud.google.com/stackdriver/docs/solutions/gke/installing. + https://cloud.google.com/kubernetes-engine/docs/concepts/about-logs. --monitoring-service=MONITORING_SERVICE (DEPRECATED) Monitoring service to use for the cluster. Options are: @@ -1415,7 +1419,7 @@ REQUIRED FLAGS The --monitoring-service flag is deprecated and will be removed in an upcoming release. Please use --monitoring instead. For more information, please read: - https://cloud.google.com/stackdriver/docs/solutions/gke/installing. + https://cloud.google.com/kubernetes-engine/docs/how-to/configure-metrics. Basic auth diff --git a/gcloud/beta/container/fleet/memberships/describe b/gcloud/beta/container/fleet/memberships/describe index bf44829ad..377c87e35 100644 --- a/gcloud/beta/container/fleet/memberships/describe +++ b/gcloud/beta/container/fleet/memberships/describe @@ -17,7 +17,7 @@ EXAMPLES Then describe it: - $ gcloud beta container fleet memberships describe MEMBERSHIP_NAME + $ gcloud beta container fleet memberships describe MEMBERSHIP POSITIONAL ARGUMENTS Membership resource - The cluster membership to describe. The arguments in diff --git a/gcloud/beta/container/hub/memberships/describe b/gcloud/beta/container/hub/memberships/describe index bebb3b9bc..73d8c711a 100644 --- a/gcloud/beta/container/hub/memberships/describe +++ b/gcloud/beta/container/hub/memberships/describe @@ -17,7 +17,7 @@ EXAMPLES Then describe it: - $ gcloud beta container hub memberships describe MEMBERSHIP_NAME + $ gcloud beta container hub memberships describe MEMBERSHIP POSITIONAL ARGUMENTS Membership resource - The cluster membership to describe. The arguments in diff --git a/gcloud/beta/firestore/databases/create b/gcloud/beta/firestore/databases/create index 532466011..bda723b65 100644 --- a/gcloud/beta/firestore/databases/create +++ b/gcloud/beta/firestore/databases/create @@ -5,8 +5,8 @@ NAME SYNOPSIS gcloud beta firestore databases create --location=LOCATION [--database=DATABASE; default="(default)"] [--delete-protection] - [--enable-pitr] [--type=TYPE; default="firestore-native"] - [GCLOUD_WIDE_FLAG ...] + [--enable-pitr] [--kms-key-name=KMS_KEY_NAME] + [--type=TYPE; default="firestore-native"] [GCLOUD_WIDE_FLAG ...] EXAMPLES To create a Firestore Native database in nam5. @@ -35,6 +35,13 @@ EXAMPLES $ gcloud beta firestore databases create --location=nam5 \ --enable-pitr + To create a Firestore Native database in nam5 encrypted by a + Customer-managed encryption key (CMEK). + + $ gcloud beta firestore databases create --location=nam5 \ + --kms-key-name=projects/PROJECT_ID/locations/us/keyRings/\ + KEY_RING_ID/cryptoKeys/CRYPTO_KEY_ID + REQUIRED FLAGS --location=LOCATION The location to operate on. Available locations are listed at @@ -71,6 +78,19 @@ OPTIONAL FLAGS If set to true, PITR on the new database will be enabled. By default, this feature is not enabled. + --kms-key-name=KMS_KEY_NAME + The resource ID of a Cloud KMS key. If set, the database created will + be a Customer-Managed Encryption Key (CMEK) database encrypted with + this key. This feature is allowlist only in initial launch. + + Only a key in the same location as this database is allowed to be used for encryption. + For Firestore's nam5 multi-region, this corresponds to Cloud KMS location us. + For Firestore's eur3 multi-region, this corresponds to Cloud KMS location europe. + See https://cloud.google.com/kms/docs/locations. + + This value should be the KMS key resource ID in the format of `projects/{project_id}/locations/{kms_location}/keyRings/{key_ring}/cryptoKeys/{crypto_key}`. + How to retrieve this resource ID is listed at https://cloud.google.com/kms/docs/getting-resource-ids#getting_the_id_for_a_key_and_version. + --type=TYPE; default="firestore-native" The type of the database. TYPE must be one of: firestore-native, datastore-mode. diff --git a/gcloud/beta/firestore/databases/list b/gcloud/beta/firestore/databases/list index ebd4e053d..3789ad165 100644 --- a/gcloud/beta/firestore/databases/list +++ b/gcloud/beta/firestore/databases/list @@ -3,15 +3,23 @@ NAME the project SYNOPSIS - gcloud beta firestore databases list [--filter=EXPRESSION] [--limit=LIMIT] - [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + gcloud beta firestore databases list [--show-deleted] [--filter=EXPRESSION] + [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] EXAMPLES - To list all Firestore databases. + To list all active Firestore databases. $ gcloud beta firestore databases list + To list all Firestore databases including deleted databases. + + $ gcloud beta firestore databases list --show-deleted + +FLAGS + --show-deleted + Show the deleted databases. + LIST COMMAND FLAGS --filter=EXPRESSION Apply a Boolean filter EXPRESSION to each resource item to be listed. diff --git a/gcloud/beta/network-connectivity/spokes/delete b/gcloud/beta/network-connectivity/spokes/delete new file mode 100644 index 000000000..fe02bf126 --- /dev/null +++ b/gcloud/beta/network-connectivity/spokes/delete @@ -0,0 +1,77 @@ +NAME + gcloud beta network-connectivity spokes delete - delete a spoke + +SYNOPSIS + gcloud beta network-connectivity spokes delete SPOKE [--async] + [--global | --region=REGION] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Delete the specified spoke. + +EXAMPLES + To delete a spoke named myspoke in the us-central1 region, run: + + $ gcloud beta network-connectivity spokes delete myspoke \ + --region=us-central1 + +POSITIONAL ARGUMENTS + Spoke resource - Name of the spoke to delete. This represents a Cloud + resource. (NOTE) Some attributes are not given arguments in this group but + can be set in other ways. + + To set the project attribute: + ◆ provide the argument spoke on the command line with a fully specified + name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + To set the location attribute: + ◆ provide the argument spoke on the command line with a fully specified + name; + ◆ provide the argument --global on the command line; + ◆ provide the argument --region on the command line. + + This must be specified. + + SPOKE + ID of the spoke or fully qualified identifier for the spoke. + + To set the spoke attribute: + ▸ provide the argument spoke on the command line. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + At most one of these can be specified: + + --global + Indicates that the spoke is global. + + --region=REGION + A Google Cloud region. To see the names of regions, see Viewing a + list of available regions + (https://cloud.google.com/compute/docs/regions-zones/viewing-regions-zones#viewing_a_list_of_available_regions). + +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. + +API REFERENCE + This command uses the networkconnectivity/v1 API. The full documentation + for this API can be found at: + https://cloud.google.com/network-connectivity/docs/reference/networkconnectivity/rest + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud network-connectivity spokes delete + + $ gcloud alpha network-connectivity spokes delete + diff --git a/gcloud/beta/network-connectivity/spokes/describe b/gcloud/beta/network-connectivity/spokes/describe new file mode 100644 index 000000000..33d9d4538 --- /dev/null +++ b/gcloud/beta/network-connectivity/spokes/describe @@ -0,0 +1,74 @@ +NAME + gcloud beta network-connectivity spokes describe - describe a spoke + +SYNOPSIS + gcloud beta network-connectivity spokes describe SPOKE + [--global | --region=REGION] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Retrieve and display details about a spoke. + +EXAMPLES + To display details about a spoke named myspoke in the us-central1 region, + run: + + $ gcloud beta network-connectivity spokes describe myspoke \ + --region=us-central1 + +POSITIONAL ARGUMENTS + Spoke resource - Name of the spoke to describe. This represents a Cloud + resource. (NOTE) Some attributes are not given arguments in this group but + can be set in other ways. + + To set the project attribute: + ◆ provide the argument spoke on the command line with a fully specified + name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + To set the location attribute: + ◆ provide the argument spoke on the command line with a fully specified + name; + ◆ provide the argument --global on the command line; + ◆ provide the argument --region on the command line. + + This must be specified. + + SPOKE + ID of the spoke or fully qualified identifier for the spoke. + + To set the spoke attribute: + ▸ provide the argument spoke on the command line. + +FLAGS + At most one of these can be specified: + + --global + Indicates that the spoke is global. + + --region=REGION + A Google Cloud region. To see the names of regions, see Viewing a + list of available regions + (https://cloud.google.com/compute/docs/regions-zones/viewing-regions-zones#viewing_a_list_of_available_regions). + +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. + +API REFERENCE + This command uses the networkconnectivity/v1 API. The full documentation + for this API can be found at: + https://cloud.google.com/network-connectivity/docs/reference/networkconnectivity/rest + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud network-connectivity spokes describe + + $ gcloud alpha network-connectivity spokes describe + diff --git a/gcloud/beta/network-connectivity/spokes/help b/gcloud/beta/network-connectivity/spokes/help index 5d4518ca5..e9ecab420 100644 --- a/gcloud/beta/network-connectivity/spokes/help +++ b/gcloud/beta/network-connectivity/spokes/help @@ -3,7 +3,8 @@ NAME Center spokes SYNOPSIS - gcloud beta network-connectivity spokes GROUP [GCLOUD_WIDE_FLAG ...] + gcloud beta network-connectivity spokes GROUP | COMMAND + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) Manage Network Connectivity Center spokes. @@ -22,9 +23,24 @@ GROUPS linked-router-appliances (BETA) Manage Router appliance spokes. + linked-vpc-network + (BETA) Manage VPC spokes. + linked-vpn-tunnels (BETA) Manage VPN spokes. +COMMANDS + COMMAND is one of the following: + + delete + (BETA) Delete a spoke. + + describe + (BETA) Describe a spoke. + + list + (BETA) List spokes. + NOTES This command is currently in beta and might change without notice. These variants are also available: diff --git a/gcloud/beta/network-connectivity/spokes/linked-vpc-network/create b/gcloud/beta/network-connectivity/spokes/linked-vpc-network/create new file mode 100644 index 000000000..e28e6db77 --- /dev/null +++ b/gcloud/beta/network-connectivity/spokes/linked-vpc-network/create @@ -0,0 +1,102 @@ +NAME + gcloud beta network-connectivity spokes linked-vpc-network create - create + a new VPC spoke + +SYNOPSIS + gcloud beta network-connectivity spokes linked-vpc-network create SPOKE + --hub=HUB --vpc-network=VPC_NETWORK [--async] + [--description=DESCRIPTION] [--exclude-export-ranges=[CIDR_RANGE,...]] + [--global] [--include-export-ranges=[CIDR_RANGE,...]] + [--labels=[KEY=VALUE,...]] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Create a new VPC spoke. + +EXAMPLES + To create a VPC spoke named myspoke, run: + + $ gcloud beta network-connectivity spokes linked-vpc-network \ + create myspoke \ + --hub="https://www.googleapis.com/networkconnectivity/v1/project\ + s/my-project/locations/global/hubs/my-hub" --global \ + --vpc-network="https://www.googleapis.com/compute/v1/projects/my\ + -project/global/networks/my-vpc" + +POSITIONAL ARGUMENTS + Spoke resource - Name of the spoke to create. This represents a Cloud + resource. (NOTE) Some attributes are not given arguments in this group but + can be set in other ways. + + To set the project attribute: + ◆ provide the argument spoke on the command line with a fully specified + name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + To set the location attribute: + ◆ provide the argument spoke on the command line with a fully specified + name; + ◆ provide the argument --global on the command line. + + This must be specified. + + SPOKE + ID of the spoke or fully qualified identifier for the spoke. + + To set the spoke attribute: + ▸ provide the argument spoke on the command line. + +REQUIRED FLAGS + --hub=HUB + Hub that the spoke will attach to. The hub must already exist. + + --vpc-network=VPC_NETWORK + VPC network that the spoke provides connectivity to. The resource must + already exist. + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --description=DESCRIPTION + Description of the spoke to create. + + --exclude-export-ranges=[CIDR_RANGE,...] + Subnet IP address range(s) to hide from other VPC networks that are + connected through Network Connectivity Center. + + --global + Indicates that the spoke is global. + + --include-export-ranges=[CIDR_RANGE,...] + Subnet IP address range(s) to export to other VPC networks that are + connected through Network Connectivity Center. + + --labels=[KEY=VALUE,...] + List of label KEY=VALUE pairs to add. + + Keys must start with a lowercase character and contain only hyphens + (-), underscores (_), lowercase characters, and numbers. Values must + contain only hyphens (-), underscores (_), lowercase characters, and + numbers. + +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. + +API REFERENCE + This command uses the networkconnectivity/v1 API. The full documentation + for this API can be found at: + https://cloud.google.com/network-connectivity/docs/reference/networkconnectivity/rest + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud network-connectivity spokes linked-vpc-network create + diff --git a/gcloud/beta/network-connectivity/spokes/linked-vpc-network/help b/gcloud/beta/network-connectivity/spokes/linked-vpc-network/help new file mode 100644 index 000000000..663286b5a --- /dev/null +++ b/gcloud/beta/network-connectivity/spokes/linked-vpc-network/help @@ -0,0 +1,31 @@ +NAME + gcloud beta network-connectivity spokes linked-vpc-network - manage VPC + spokes + +SYNOPSIS + gcloud beta network-connectivity spokes linked-vpc-network COMMAND + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Manage VPC spokes. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + create + (BETA) Create a new VPC spoke. + + update + (BETA) Update a VPC spoke. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud network-connectivity spokes linked-vpc-network + diff --git a/gcloud/beta/network-connectivity/spokes/linked-vpc-network/update b/gcloud/beta/network-connectivity/spokes/linked-vpc-network/update new file mode 100644 index 000000000..f36952ce7 --- /dev/null +++ b/gcloud/beta/network-connectivity/spokes/linked-vpc-network/update @@ -0,0 +1,103 @@ +NAME + gcloud beta network-connectivity spokes linked-vpc-network update - update + a VPC spoke + +SYNOPSIS + gcloud beta network-connectivity spokes linked-vpc-network update SPOKE + [--async] [--description=DESCRIPTION] [--global] + [--update-labels=[KEY=VALUE,...]] + [--clear-labels | --remove-labels=[KEY,...]] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Update the details of a VPC spoke. + +EXAMPLES + To update the description of a global VPC spoke named my-spoke, run: + + $ gcloud beta network-connectivity spokes linked-vpc-network \ + update myspoke --global --description="new spoke description" + +POSITIONAL ARGUMENTS + Spoke resource - Name of the spoke to update. This represents a Cloud + resource. (NOTE) Some attributes are not given arguments in this group but + can be set in other ways. + + To set the project attribute: + ◆ provide the argument spoke on the command line with a fully specified + name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + To set the location attribute: + ◆ provide the argument spoke on the command line with a fully specified + name; + ◆ provide the argument --global on the command line. + + This must be specified. + + SPOKE + ID of the spoke or fully qualified identifier for the spoke. + + To set the spoke attribute: + ▸ provide the argument spoke on the command line. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --description=DESCRIPTION + New description of the spoke. + + --global + Indicates that the spoke is global. + + --update-labels=[KEY=VALUE,...] + List of label KEY=VALUE pairs to update. If a label exists, its value + is modified. Otherwise, a new label is created. + + Keys must start with a lowercase character and contain only hyphens + (-), underscores (_), lowercase characters, and numbers. Values must + contain only hyphens (-), underscores (_), lowercase characters, and + numbers. + + At most one of these can be specified: + + --clear-labels + Remove all labels. If --update-labels is also specified then + --clear-labels is applied first. + + For example, to remove all labels: + + $ gcloud beta network-connectivity spokes linked-vpc-network \ + update --clear-labels + + To remove all existing labels and create two new labels, foo and baz: + + $ gcloud beta network-connectivity spokes linked-vpc-network \ + update --clear-labels --update-labels foo=bar,baz=qux + + --remove-labels=[KEY,...] + List of label keys to remove. If a label does not exist it is + silently ignored. If --update-labels is also specified then + --update-labels is applied first. + +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. + +API REFERENCE + This command uses the networkconnectivity/v1 API. The full documentation + for this API can be found at: + https://cloud.google.com/network-connectivity/docs/reference/networkconnectivity/rest + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud network-connectivity spokes linked-vpc-network update + diff --git a/gcloud/beta/network-connectivity/spokes/list b/gcloud/beta/network-connectivity/spokes/list new file mode 100644 index 000000000..6b6441c01 --- /dev/null +++ b/gcloud/beta/network-connectivity/spokes/list @@ -0,0 +1,79 @@ +NAME + gcloud beta network-connectivity spokes list - list spokes + +SYNOPSIS + gcloud beta network-connectivity spokes list [--global | --region=REGION] + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Retrieve and display a list of all spokes in the specified project. + +EXAMPLES + To list all spokes in the us-central1 region, run: + + $ gcloud beta network-connectivity spokes list --region=us-central1 + + To list all spokes in all regions, run: + + $ gcloud beta network-connectivity spokes list + +FLAGS + At most one of these can be specified: + + --global + Indicates that the spoke is global. + + --region=REGION + A Google Cloud region. To see the names of regions, see Viewing a + list of available regions + (https://cloud.google.com/compute/docs/regions-zones/viewing-regions-zones#viewing_a_list_of_available_regions). + Use ``-`` to specify all regions. + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + +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. + +API REFERENCE + This command uses the networkconnectivity/v1 API. The full documentation + for this API can be found at: + https://cloud.google.com/network-connectivity/docs/reference/networkconnectivity/rest + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud network-connectivity spokes list + + $ gcloud alpha network-connectivity spokes list + diff --git a/gcloud/beta/sql/instances/switchover b/gcloud/beta/sql/instances/switchover index 5699d3ba9..10008f08b 100644 --- a/gcloud/beta/sql/instances/switchover +++ b/gcloud/beta/sql/instances/switchover @@ -38,8 +38,10 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud sql instances switchover $ gcloud alpha sql instances switchover diff --git a/gcloud/compute/health-checks/create/http b/gcloud/compute/health-checks/create/http index f84dcbd08..35cf4463f 100644 --- a/gcloud/compute/health-checks/create/http +++ b/gcloud/compute/health-checks/create/http @@ -9,7 +9,7 @@ SYNOPSIS [--healthy-threshold=HEALTHY_THRESHOLD; default=2] [--host=HOST] [--proxy-header=PROXY_HEADER; default="NONE"] [--request-path=REQUEST_PATH; default="/"] [--response=RESPONSE] - [--timeout=TIMEOUT; default="5s"] + [--source-regions=REGION,...,[...]] [--timeout=TIMEOUT; default="5s"] [--unhealthy-threshold=UNHEALTHY_THRESHOLD; default=2] [--global | --region=REGION] [--port=PORT; default=80 --port-name=PORT_NAME --use-serving-port] @@ -69,6 +69,18 @@ FLAGS empty, presence of specified string in first 1024 characters of response body determines health. Only ASCII characters allowed. + --source-regions=REGION,...,[...] + Define the list of Google Cloud regions from which health checks are + performed. This option is supported only for global health checks that + will be referenced by DNS routing policies. If specified, the + --check-interval field should be at least 30 seconds. The + --proxy-header and --request fields (for TCP health checks) are not + supported with this option. + + If --source-regions is specified for a health check, then that health + check cannot be used by a backend service or by a managed instance + group (for autohealing). + --timeout=TIMEOUT; default="5s" If Google Compute Engine doesn't receive a healthy response from the instance by the time specified by the value of this flag, the health diff --git a/gcloud/compute/health-checks/create/https b/gcloud/compute/health-checks/create/https index 7ea97cb1b..74a737313 100644 --- a/gcloud/compute/health-checks/create/https +++ b/gcloud/compute/health-checks/create/https @@ -9,7 +9,7 @@ SYNOPSIS [--healthy-threshold=HEALTHY_THRESHOLD; default=2] [--host=HOST] [--proxy-header=PROXY_HEADER; default="NONE"] [--request-path=REQUEST_PATH; default="/"] [--response=RESPONSE] - [--timeout=TIMEOUT; default="5s"] + [--source-regions=REGION,...,[...]] [--timeout=TIMEOUT; default="5s"] [--unhealthy-threshold=UNHEALTHY_THRESHOLD; default=2] [--global | --region=REGION] [--port=PORT; default=80 --port-name=PORT_NAME --use-serving-port] @@ -69,6 +69,18 @@ FLAGS empty, presence of specified string in first 1024 characters of response body determines health. Only ASCII characters allowed. + --source-regions=REGION,...,[...] + Define the list of Google Cloud regions from which health checks are + performed. This option is supported only for global health checks that + will be referenced by DNS routing policies. If specified, the + --check-interval field should be at least 30 seconds. The + --proxy-header and --request fields (for TCP health checks) are not + supported with this option. + + If --source-regions is specified for a health check, then that health + check cannot be used by a backend service or by a managed instance + group (for autohealing). + --timeout=TIMEOUT; default="5s" If Google Compute Engine doesn't receive a healthy response from the instance by the time specified by the value of this flag, the health diff --git a/gcloud/compute/health-checks/create/tcp b/gcloud/compute/health-checks/create/tcp index 7cf7fb686..4169dfc9c 100644 --- a/gcloud/compute/health-checks/create/tcp +++ b/gcloud/compute/health-checks/create/tcp @@ -8,7 +8,8 @@ SYNOPSIS [--description=DESCRIPTION] [--enable-logging] [--healthy-threshold=HEALTHY_THRESHOLD; default=2] [--proxy-header=PROXY_HEADER; default="NONE"] [--request=REQUEST] - [--response=RESPONSE] [--timeout=TIMEOUT; default="5s"] + [--response=RESPONSE] [--source-regions=REGION,...,[...]] + [--timeout=TIMEOUT; default="5s"] [--unhealthy-threshold=UNHEALTHY_THRESHOLD; default=2] [--global | --region=REGION] [--port=PORT; default=80 --port-name=PORT_NAME --use-serving-port] @@ -72,6 +73,18 @@ FLAGS successful handshake, only configure --response to match an explicit --request. + --source-regions=REGION,...,[...] + Define the list of Google Cloud regions from which health checks are + performed. This option is supported only for global health checks that + will be referenced by DNS routing policies. If specified, the + --check-interval field should be at least 30 seconds. The + --proxy-header and --request fields (for TCP health checks) are not + supported with this option. + + If --source-regions is specified for a health check, then that health + check cannot be used by a backend service or by a managed instance + group (for autohealing). + --timeout=TIMEOUT; default="5s" If Google Compute Engine doesn't receive a healthy response from the instance by the time specified by the value of this flag, the health diff --git a/gcloud/compute/health-checks/update/http b/gcloud/compute/health-checks/update/http index 22a73dfad..de67bba0a 100644 --- a/gcloud/compute/health-checks/update/http +++ b/gcloud/compute/health-checks/update/http @@ -6,7 +6,8 @@ SYNOPSIS [--check-interval=CHECK_INTERVAL] [--description=DESCRIPTION] [--enable-logging] [--healthy-threshold=HEALTHY_THRESHOLD] [--host=HOST] [--proxy-header=PROXY_HEADER] - [--request-path=REQUEST_PATH] [--response=RESPONSE] [--timeout=TIMEOUT] + [--request-path=REQUEST_PATH] [--response=RESPONSE] + [--source-regions=REGION,...,[...]] [--timeout=TIMEOUT] [--unhealthy-threshold=UNHEALTHY_THRESHOLD] [--global | --region=REGION] [--port=PORT --port-name=PORT_NAME --use-serving-port] @@ -66,6 +67,18 @@ FLAGS empty, presence of specified string in first 1024 characters of response body determines health. Only ASCII characters allowed. + --source-regions=REGION,...,[...] + Define the list of Google Cloud regions from which health checks are + performed. This option is supported only for global health checks that + will be referenced by DNS routing policies. If specified, the + --check-interval field should be at least 30 seconds. The + --proxy-header and --request fields (for TCP health checks) are not + supported with this option. + + If --source-regions is specified for a health check, then that health + check cannot be used by a backend service or by a managed instance + group (for autohealing). + --timeout=TIMEOUT If Google Compute Engine doesn't receive a healthy response from the instance by the time specified by the value of this flag, the health diff --git a/gcloud/compute/health-checks/update/https b/gcloud/compute/health-checks/update/https index e0e9eb405..b54da864e 100644 --- a/gcloud/compute/health-checks/update/https +++ b/gcloud/compute/health-checks/update/https @@ -6,7 +6,8 @@ SYNOPSIS [--check-interval=CHECK_INTERVAL] [--description=DESCRIPTION] [--enable-logging] [--healthy-threshold=HEALTHY_THRESHOLD] [--host=HOST] [--proxy-header=PROXY_HEADER] - [--request-path=REQUEST_PATH] [--response=RESPONSE] [--timeout=TIMEOUT] + [--request-path=REQUEST_PATH] [--response=RESPONSE] + [--source-regions=REGION,...,[...]] [--timeout=TIMEOUT] [--unhealthy-threshold=UNHEALTHY_THRESHOLD] [--global | --region=REGION] [--port=PORT --port-name=PORT_NAME --use-serving-port] @@ -66,6 +67,18 @@ FLAGS empty, presence of specified string in first 1024 characters of response body determines health. Only ASCII characters allowed. + --source-regions=REGION,...,[...] + Define the list of Google Cloud regions from which health checks are + performed. This option is supported only for global health checks that + will be referenced by DNS routing policies. If specified, the + --check-interval field should be at least 30 seconds. The + --proxy-header and --request fields (for TCP health checks) are not + supported with this option. + + If --source-regions is specified for a health check, then that health + check cannot be used by a backend service or by a managed instance + group (for autohealing). + --timeout=TIMEOUT If Google Compute Engine doesn't receive a healthy response from the instance by the time specified by the value of this flag, the health diff --git a/gcloud/compute/health-checks/update/tcp b/gcloud/compute/health-checks/update/tcp index 7dd98cf5b..3f1d3960d 100644 --- a/gcloud/compute/health-checks/update/tcp +++ b/gcloud/compute/health-checks/update/tcp @@ -6,7 +6,8 @@ SYNOPSIS [--check-interval=CHECK_INTERVAL] [--description=DESCRIPTION] [--enable-logging] [--healthy-threshold=HEALTHY_THRESHOLD] [--proxy-header=PROXY_HEADER] [--request=REQUEST] [--response=RESPONSE] - [--timeout=TIMEOUT] [--unhealthy-threshold=UNHEALTHY_THRESHOLD] + [--source-regions=REGION,...,[...]] [--timeout=TIMEOUT] + [--unhealthy-threshold=UNHEALTHY_THRESHOLD] [--global | --region=REGION] [--port=PORT --port-name=PORT_NAME --use-serving-port] [GCLOUD_WIDE_FLAG ...] @@ -70,6 +71,18 @@ FLAGS --request. Setting this to an empty string will clear any existing response value. + --source-regions=REGION,...,[...] + Define the list of Google Cloud regions from which health checks are + performed. This option is supported only for global health checks that + will be referenced by DNS routing policies. If specified, the + --check-interval field should be at least 30 seconds. The + --proxy-header and --request fields (for TCP health checks) are not + supported with this option. + + If --source-regions is specified for a health check, then that health + check cannot be used by a backend service or by a managed instance + group (for autohealing). + --timeout=TIMEOUT If Google Compute Engine doesn't receive a healthy response from the instance by the time specified by the value of this flag, the health diff --git a/gcloud/compute/instance-templates/create b/gcloud/compute/instance-templates/create index 2b89748ff..28c1f4765 100644 --- a/gcloud/compute/instance-templates/create +++ b/gcloud/compute/instance-templates/create @@ -6,14 +6,15 @@ SYNOPSIS gcloud compute instance-templates create NAME [--accelerator=[count=COUNT],[type=TYPE]] [--no-boot-disk-auto-delete] [--boot-disk-device-name=BOOT_DISK_DEVICE_NAME] + [--boot-disk-interface=BOOT_DISK_INTERFACE] [--boot-disk-provisioned-iops=BOOT_DISK_PROVISIONED_IOPS] [--boot-disk-provisioned-throughput=BOOT_DISK_PROVISIONED_THROUGHPUT] [--boot-disk-size=BOOT_DISK_SIZE] [--boot-disk-type=BOOT_DISK_TYPE] [--can-ip-forward] [--configure-disk=[PROPERTY=VALUE,...]] [--create-disk=[PROPERTY=VALUE,...]] [--description=DESCRIPTION] [--discard-local-ssds-at-termination-timestamp=DISCARD_LOCAL_SSDS_AT_TERMINATION_TIMESTAMP] - [--disk=[auto-delete=AUTO-DELETE], - [boot=BOOT],[device-name=DEVICE-NAME],[mode=MODE],[name=NAME]] + [--disk=[auto-delete=AUTO-DELETE],[boot=BOOT],[device-name=DEVICE-NAME], + [interface=INTERFACE],[mode=MODE],[name=NAME]] [--[no-]enable-nested-virtualization] [--[no-]enable-uefi-networking] [--external-ipv6-address=EXTERNAL_IPV6_ADDRESS] [--external-ipv6-prefix-length=EXTERNAL_IPV6_PREFIX_LENGTH] @@ -109,6 +110,12 @@ FLAGS option can only be specified if a new boot disk is being created (as opposed to mounting an existing persistent disk). + --boot-disk-interface=BOOT_DISK_INTERFACE + Indicates the interface to use for the boot disk. The value must be one + of the following: + ◆ SCSI + ◆ NVME + --boot-disk-provisioned-iops=BOOT_DISK_PROVISIONED_IOPS Indicates how many IOPS to provision for the disk. This sets the number of I/O operations per second that the disk can handle. Value must be @@ -257,6 +264,12 @@ FLAGS The name of the storage pool in which the new disk is created. The new disk and the storage pool must be in the same location. + interface + The interface to use with the disk. The value must be one of the + following: + ▸ SCSI + ▸ NVME + boot If yes, indicates that this is a boot disk. The instance will use the first partition of the disk for its root file system. The @@ -336,15 +349,15 @@ FLAGS For more information about the --discard-local-ssd flag, see https://cloud.google.com/compute/docs/disks/local-ssd#stop_instance. - --disk=[auto-delete=AUTO-DELETE],[boot=BOOT],[device-name=DEVICE-NAME],[mode=MODE],[name=NAME] - Attaches an existing persistent disk to the instances. + --disk=[auto-delete=AUTO-DELETE],[boot=BOOT],[device-name=DEVICE-NAME],[interface=INTERFACE],[mode=MODE],[name=NAME] + Attaches an existing disk to the instances. name The disk to attach to the instances. If you create more than one instance, you can only attach a disk in read-only mode. By default, - you attach a zonal persistent disk located in the same zone of the - instance. If you want to attach a regional persistent disk, you - must specify the disk using its URI; for example, + you attach a zonal disk located in the same zone of the instance. + If you want to attach a regional disk, you must specify the disk + using its URI; for example, projects/myproject/regions/us-central1/disks/my-regional-disk. mode @@ -367,7 +380,13 @@ FLAGS If set to yes, the persistent disk is automatically deleted when the instance is deleted. However, if you detach the disk from the instance, deleting the instance doesn't delete the disk. The - default value for this is yes. + default value is yes. + + interface + The interface to use for the disk. The value must be one of the + following: + ▸ SCSI + ▸ NVME --[no-]enable-nested-virtualization If set to true, enables nested virtualization for the instance. Use diff --git a/gcloud/compute/instance-templates/create-with-container b/gcloud/compute/instance-templates/create-with-container index b03747077..d85367de2 100644 --- a/gcloud/compute/instance-templates/create-with-container +++ b/gcloud/compute/instance-templates/create-with-container @@ -6,6 +6,7 @@ SYNOPSIS gcloud compute instance-templates create-with-container NAME [--no-boot-disk-auto-delete] [--boot-disk-device-name=BOOT_DISK_DEVICE_NAME] + [--boot-disk-interface=BOOT_DISK_INTERFACE] [--boot-disk-provisioned-iops=BOOT_DISK_PROVISIONED_IOPS] [--boot-disk-provisioned-throughput=BOOT_DISK_PROVISIONED_THROUGHPUT] [--boot-disk-size=BOOT_DISK_SIZE] [--boot-disk-type=BOOT_DISK_TYPE] @@ -23,8 +24,8 @@ SYNOPSIS [--container-restart-policy=POLICY; default="always"] [--container-stdin] [--container-tty] [--create-disk=[PROPERTY=VALUE,...]] [--description=DESCRIPTION] - [--disk=[auto-delete=AUTO-DELETE], - [boot=BOOT],[device-name=DEVICE-NAME],[mode=MODE],[name=NAME]] + [--disk=[auto-delete=AUTO-DELETE],[boot=BOOT],[device-name=DEVICE-NAME], + [interface=INTERFACE],[mode=MODE],[name=NAME]] [--external-ipv6-address=EXTERNAL_IPV6_ADDRESS] [--external-ipv6-prefix-length=EXTERNAL_IPV6_PREFIX_LENGTH] [--internal-ipv6-address=INTERNAL_IPV6_ADDRESS] @@ -96,6 +97,12 @@ FLAGS option can only be specified if a new boot disk is being created (as opposed to mounting an existing persistent disk). + --boot-disk-interface=BOOT_DISK_INTERFACE + Indicates the interface to use for the boot disk. The value must be one + of the following: + ◆ SCSI + ◆ NVME + --boot-disk-provisioned-iops=BOOT_DISK_PROVISIONED_IOPS Indicates how many IOPS to provision for the disk. This sets the number of I/O operations per second that the disk can handle. Value must be @@ -344,6 +351,12 @@ FLAGS The name of the storage pool in which the new disk is created. The new disk and the storage pool must be in the same location. + interface + The interface to use with the disk. The value must be one of the + following: + ▸ SCSI + ▸ NVME + replica-zones Required for each regional disk associated with the instance. Specify the URLs of the zones where the disk should be replicated @@ -353,15 +366,15 @@ FLAGS --description=DESCRIPTION Specifies a textual description for the instance template. - --disk=[auto-delete=AUTO-DELETE],[boot=BOOT],[device-name=DEVICE-NAME],[mode=MODE],[name=NAME] - Attaches an existing persistent disk to the instances. + --disk=[auto-delete=AUTO-DELETE],[boot=BOOT],[device-name=DEVICE-NAME],[interface=INTERFACE],[mode=MODE],[name=NAME] + Attaches an existing disk to the instances. name The disk to attach to the instances. If you create more than one instance, you can only attach a disk in read-only mode. By default, - you attach a zonal persistent disk located in the same zone of the - instance. If you want to attach a regional persistent disk, you - must specify the disk using its URI; for example, + you attach a zonal disk located in the same zone of the instance. + If you want to attach a regional disk, you must specify the disk + using its URI; for example, projects/myproject/regions/us-central1/disks/my-regional-disk. mode @@ -388,7 +401,13 @@ FLAGS If set to yes, the persistent disk is automatically deleted when the instance is deleted. However, if you detach the disk from the instance, deleting the instance doesn't delete the disk. The - default value for this is yes. + default value is yes. + + interface + The interface to use for the disk. The value must be one of the + following: + ▸ SCSI + ▸ NVME --external-ipv6-address=EXTERNAL_IPV6_ADDRESS Assigns the given external IPv6 address to the instance that is diff --git a/gcloud/compute/instances/attach-disk b/gcloud/compute/instances/attach-disk index 371fab1e7..98ddab3e1 100644 --- a/gcloud/compute/instances/attach-disk +++ b/gcloud/compute/instances/attach-disk @@ -5,7 +5,8 @@ SYNOPSIS gcloud compute instances attach-disk INSTANCE_NAME --disk=DISK [--boot] [--csek-key-file=FILE] [--device-name=DEVICE_NAME] [--disk-scope=DISK_SCOPE; default="zonal"] [--force-attach] - [--mode=MODE; default="rw"] [--zone=ZONE] [GCLOUD_WIDE_FLAG ...] + [--interface=INTERFACE] [--mode=MODE; default="rw"] [--zone=ZONE] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION gcloud compute instances attach-disk is used to attach a disk to an @@ -82,6 +83,14 @@ OPTIONAL FLAGS the previous instance fails at first. The server will continue trying to detach the disk from the previous instance in the background. + --interface=INTERFACE + The interface of the disk. INTERFACE must be one of: + + NVME + NVME + SCSI + SCSI + --mode=MODE; default="rw" Specifies the mode of the disk. MODE must be one of: diff --git a/gcloud/compute/instances/bulk/create b/gcloud/compute/instances/bulk/create index b31bd85a0..455f11510 100644 --- a/gcloud/compute/instances/bulk/create +++ b/gcloud/compute/instances/bulk/create @@ -9,6 +9,7 @@ SYNOPSIS [--accelerator=[count=COUNT],[type=TYPE]] [--no-address] [--async] [--no-boot-disk-auto-delete] [--boot-disk-device-name=BOOT_DISK_DEVICE_NAME] + [--boot-disk-interface=BOOT_DISK_INTERFACE] [--boot-disk-provisioned-iops=BOOT_DISK_PROVISIONED_IOPS] [--boot-disk-provisioned-throughput=BOOT_DISK_PROVISIONED_THROUGHPUT] [--boot-disk-size=BOOT_DISK_SIZE] [--boot-disk-type=BOOT_DISK_TYPE] @@ -159,6 +160,12 @@ OPTIONAL FLAGS option can only be specified if a new boot disk is being created (as opposed to mounting an existing persistent disk). + --boot-disk-interface=BOOT_DISK_INTERFACE + Indicates the interface to use for the boot disk. The value must be one + of the following: + ◆ SCSI + ◆ NVME + --boot-disk-provisioned-iops=BOOT_DISK_PROVISIONED_IOPS Indicates how many IOPS to provision for the disk. This sets the number of I/O operations per second that the disk can handle. Value must be @@ -290,6 +297,12 @@ OPTIONAL FLAGS The name of the storage pool in which the new disk is created. The new disk and the storage pool must be in the same location. + interface + The interface to use with the disk. The value must be one of the + following: + ▸ SCSI + ▸ NVME + boot If yes, indicates that this is a boot disk. The instance will use the first partition of the disk for its root file system. The diff --git a/gcloud/compute/instances/create b/gcloud/compute/instances/create index d85b1ff61..9b14bb6ff 100644 --- a/gcloud/compute/instances/create +++ b/gcloud/compute/instances/create @@ -5,8 +5,10 @@ NAME SYNOPSIS gcloud compute instances create INSTANCE_NAMES [INSTANCE_NAMES ...] [--accelerator=[count=COUNT],[type=TYPE]] [--async] + [--availability-domain=AVAILABILITY_DOMAIN] [--no-boot-disk-auto-delete] [--boot-disk-device-name=BOOT_DISK_DEVICE_NAME] + [--boot-disk-interface=BOOT_DISK_INTERFACE] [--boot-disk-provisioned-iops=BOOT_DISK_PROVISIONED_IOPS] [--boot-disk-provisioned-throughput=BOOT_DISK_PROVISIONED_THROUGHPUT] [--boot-disk-size=BOOT_DISK_SIZE] [--boot-disk-type=BOOT_DISK_TYPE] @@ -15,7 +17,8 @@ SYNOPSIS [--description=DESCRIPTION] [--discard-local-ssds-at-termination-timestamp=DISCARD_LOCAL_SSDS_AT_TERMINATION_TIMESTAMP] [--disk=[auto-delete=AUTO-DELETE],[boot=BOOT],[device-name=DEVICE-NAME], - [force-attach=FORCE-ATTACH],[mode=MODE],[name=NAME],[scope=SCOPE]] + [force-attach=FORCE-ATTACH], + [interface=INTERFACE],[mode=MODE],[name=NAME],[scope=SCOPE]] [--enable-display-device] [--[no-]enable-nested-virtualization] [--[no-]enable-uefi-networking] [--erase-windows-vss-signature] [--external-ipv6-address=EXTERNAL_IPV6_ADDRESS] @@ -153,6 +156,14 @@ FLAGS Return immediately, without waiting for the operation in progress to complete. + --availability-domain=AVAILABILITY_DOMAIN + Specifies the availability domain that this VM instance should be + scheduled on. The number of availability domains that a VM can be + scheduled on is specified when you create the spread placement policy. + + Specify a value from 1 to the number of domains that are available in + your placement policy. + --boot-disk-auto-delete Automatically delete boot disks when their instances are deleted. Enabled by default, use --no-boot-disk-auto-delete to disable. @@ -162,6 +173,12 @@ FLAGS option can only be specified if a new boot disk is being created (as opposed to mounting an existing persistent disk). + --boot-disk-interface=BOOT_DISK_INTERFACE + Indicates the interface to use for the boot disk. The value must be one + of the following: + ◆ SCSI + ◆ NVME + --boot-disk-provisioned-iops=BOOT_DISK_PROVISIONED_IOPS Indicates how many IOPS to provision for the disk. This sets the number of I/O operations per second that the disk can handle. Value must be @@ -286,6 +303,12 @@ FLAGS The name of the storage pool in which the new disk is created. The new disk and the storage pool must be in the same location. + interface + The interface to use with the disk. The value must be one of the + following: + ▸ SCSI + ▸ NVME + boot If yes, indicates that this is a boot disk. The instance will use the first partition of the disk for its root file system. The @@ -390,15 +413,15 @@ FLAGS For more information about the --discard-local-ssd flag, see https://cloud.google.com/compute/docs/disks/local-ssd#stop_instance. - --disk=[auto-delete=AUTO-DELETE],[boot=BOOT],[device-name=DEVICE-NAME],[force-attach=FORCE-ATTACH],[mode=MODE],[name=NAME],[scope=SCOPE] - Attaches an existing persistent disk to the instances. + --disk=[auto-delete=AUTO-DELETE],[boot=BOOT],[device-name=DEVICE-NAME],[force-attach=FORCE-ATTACH],[interface=INTERFACE],[mode=MODE],[name=NAME],[scope=SCOPE] + Attaches an existing disk to the instances. name The disk to attach to the instances. If you create more than one instance, you can only attach a disk in read-only mode. By default, - you attach a zonal persistent disk located in the same zone of the - instance. If you want to attach a regional persistent disk, you - must specify the disk using its URI; for example, + you attach a zonal disk located in the same zone of the instance. + If you want to attach a regional disk, you must specify the disk + using its URI; for example, projects/myproject/regions/us-central1/disks/my-regional-disk. mode @@ -421,7 +444,13 @@ FLAGS If set to yes, the persistent disk is automatically deleted when the instance is deleted. However, if you detach the disk from the instance, deleting the instance doesn't delete the disk. The - default value for this is yes. + default value is yes. + + interface + The interface to use for the disk. The value must be one of the + following: + ▸ SCSI + ▸ NVME scope Can be zonal or regional. If zonal, the disk is interpreted as a diff --git a/gcloud/compute/instances/create-with-container b/gcloud/compute/instances/create-with-container index 2cf8f6b33..3abd231d3 100644 --- a/gcloud/compute/instances/create-with-container +++ b/gcloud/compute/instances/create-with-container @@ -7,6 +7,7 @@ SYNOPSIS [INSTANCE_NAMES ...] [--accelerator=[count=COUNT],[type=TYPE]] [--no-boot-disk-auto-delete] [--boot-disk-device-name=BOOT_DISK_DEVICE_NAME] + [--boot-disk-interface=BOOT_DISK_INTERFACE] [--boot-disk-provisioned-iops=BOOT_DISK_PROVISIONED_IOPS] [--boot-disk-provisioned-throughput=BOOT_DISK_PROVISIONED_THROUGHPUT] [--boot-disk-size=BOOT_DISK_SIZE] [--boot-disk-type=BOOT_DISK_TYPE] @@ -26,7 +27,8 @@ SYNOPSIS [--create-disk=[PROPERTY=VALUE,...]] [--description=DESCRIPTION] [--discard-local-ssds-at-termination-timestamp=DISCARD_LOCAL_SSDS_AT_TERMINATION_TIMESTAMP] [--disk=[auto-delete=AUTO-DELETE],[boot=BOOT],[device-name=DEVICE-NAME], - [force-attach=FORCE-ATTACH],[mode=MODE],[name=NAME],[scope=SCOPE]] + [force-attach=FORCE-ATTACH], + [interface=INTERFACE],[mode=MODE],[name=NAME],[scope=SCOPE]] [--[no-]enable-nested-virtualization] [--external-ipv6-address=EXTERNAL_IPV6_ADDRESS] [--external-ipv6-prefix-length=EXTERNAL_IPV6_PREFIX_LENGTH] @@ -123,6 +125,12 @@ FLAGS option can only be specified if a new boot disk is being created (as opposed to mounting an existing persistent disk). + --boot-disk-interface=BOOT_DISK_INTERFACE + Indicates the interface to use for the boot disk. The value must be one + of the following: + ◆ SCSI + ◆ NVME + --boot-disk-provisioned-iops=BOOT_DISK_PROVISIONED_IOPS Indicates how many IOPS to provision for the disk. This sets the number of I/O operations per second that the disk can handle. Value must be @@ -366,6 +374,12 @@ FLAGS The name of the storage pool in which the new disk is created. The new disk and the storage pool must be in the same location. + interface + The interface to use with the disk. The value must be one of the + following: + ▸ SCSI + ▸ NVME + replica-zones Required for each regional disk associated with the instance. Specify the URLs of the zones where the disk should be replicated @@ -389,15 +403,15 @@ FLAGS For more information about the --discard-local-ssd flag, see https://cloud.google.com/compute/docs/disks/local-ssd#stop_instance. - --disk=[auto-delete=AUTO-DELETE],[boot=BOOT],[device-name=DEVICE-NAME],[force-attach=FORCE-ATTACH],[mode=MODE],[name=NAME],[scope=SCOPE] - Attaches an existing persistent disk to the instances. + --disk=[auto-delete=AUTO-DELETE],[boot=BOOT],[device-name=DEVICE-NAME],[force-attach=FORCE-ATTACH],[interface=INTERFACE],[mode=MODE],[name=NAME],[scope=SCOPE] + Attaches an existing disk to the instances. name The disk to attach to the instances. If you create more than one instance, you can only attach a disk in read-only mode. By default, - you attach a zonal persistent disk located in the same zone of the - instance. If you want to attach a regional persistent disk, you - must specify the disk using its URI; for example, + you attach a zonal disk located in the same zone of the instance. + If you want to attach a regional disk, you must specify the disk + using its URI; for example, projects/myproject/regions/us-central1/disks/my-regional-disk. mode @@ -424,7 +438,13 @@ FLAGS If set to yes, the persistent disk is automatically deleted when the instance is deleted. However, if you detach the disk from the instance, deleting the instance doesn't delete the disk. The - default value for this is yes. + default value is yes. + + interface + The interface to use for the disk. The value must be one of the + following: + ▸ SCSI + ▸ NVME scope Can be zonal or regional. If zonal, the disk is interpreted as a diff --git a/gcloud/compute/instances/detach-disk b/gcloud/compute/instances/detach-disk index 03a279e5b..80ddb0821 100644 --- a/gcloud/compute/instances/detach-disk +++ b/gcloud/compute/instances/detach-disk @@ -19,7 +19,7 @@ DESCRIPTION $ sudo umount /dev/disk/by-id/google-DEVICE_NAME EXAMPLES - To detach a disk named 'my-disk' to an instance named 'my-instance', run: + To detach a disk named 'my-disk' from an instance named 'my-instance', run: $ gcloud compute instances detach-disk my-instance --disk=my-disk diff --git a/gcloud/container/clusters/create b/gcloud/container/clusters/create index 08bb547d0..820a01aaa 100644 --- a/gcloud/container/clusters/create +++ b/gcloud/container/clusters/create @@ -463,7 +463,8 @@ FLAGS --enable-cloud-logging is also deprecated and will be removed in an upcoming release. Please use --logging (optionally with --monitoring). For more details, please read: - https://cloud.google.com/stackdriver/docs/solutions/gke/installing. + https://cloud.google.com/kubernetes-engine/docs/concepts/about-logs and + https://cloud.google.com/kubernetes-engine/docs/how-to/configure-metrics. --enable-cloud-monitoring (DEPRECATED) Automatically send metrics from pods in the cluster to the @@ -473,7 +474,9 @@ FLAGS Legacy Logging and Monitoring is deprecated. Thus, flag --enable-cloud-monitoring is also deprecated. Please use --monitoring (optionally with --logging). For more details, please read: - https://cloud.google.com/stackdriver/docs/solutions/gke/installing. + https://cloud.google.com/kubernetes-engine/docs/how-to/configure-metrics + and + https://cloud.google.com/kubernetes-engine/docs/concepts/about-logs. --enable-cloud-run-alpha Enable Cloud Run alpha features on this cluster. Selecting this option @@ -632,7 +635,8 @@ FLAGS The --enable-stackdriver-kubernetes flag is deprecated and will be removed in an upcoming release. Please use --logging and --monitoring instead. For more information, please read: - https://cloud.google.com/stackdriver/docs/solutions/gke/installing. + https://cloud.google.com/kubernetes-engine/docs/concepts/about-logs and + https://cloud.google.com/kubernetes-engine/docs/how-to/configure-metrics. Flags for vertical pod autoscaling: @@ -703,7 +707,7 @@ FLAGS are: SYSTEM, WORKLOAD, API_SERVER, CONTROLLER_MANAGER, SCHEDULER, NONE For more information, see - https://cloud.google.com/stackdriver/docs/solutions/gke/installing#available-logs + https://cloud.google.com/kubernetes-engine/docs/concepts/about-logs#available-logs Examples: @@ -846,7 +850,7 @@ FLAGS STATEFULSET, STORAGE, CADVISOR, KUBELET, DCGM For more information, see - https://cloud.google.com/stackdriver/docs/solutions/gke/installing#available-metrics + https://cloud.google.com/kubernetes-engine/docs/how-to/configure-metrics#available-metrics Examples: diff --git a/gcloud/container/clusters/create-auto b/gcloud/container/clusters/create-auto index 3fc15bdad..3c5ad1ca4 100644 --- a/gcloud/container/clusters/create-auto +++ b/gcloud/container/clusters/create-auto @@ -285,7 +285,7 @@ FLAGS be included. For more information, see - https://cloud.google.com/stackdriver/docs/solutions/gke/installing#available-logs + https://cloud.google.com/kubernetes-engine/docs/concepts/about-logs#available-logs Examples: @@ -302,7 +302,7 @@ FLAGS STATEFULSET, STORAGE, CADVISOR, KUBELET, DCGM For more information, see - https://cloud.google.com/stackdriver/docs/solutions/gke/installing#available-metrics + https://cloud.google.com/kubernetes-engine/docs/how-to/configure-metrics#available-metrics Examples: diff --git a/gcloud/container/clusters/update b/gcloud/container/clusters/update index 54f31a55b..2620349bc 100644 --- a/gcloud/container/clusters/update +++ b/gcloud/container/clusters/update @@ -403,7 +403,9 @@ REQUIRED FLAGS The --enable-stackdriver-kubernetes flag is deprecated and will be removed in an upcoming release. Please use --logging and --monitoring instead. For more information, please read: - https://cloud.google.com/stackdriver/docs/solutions/gke/installing. + https://cloud.google.com/kubernetes-engine/docs/concepts/about-logs + and + https://cloud.google.com/kubernetes-engine/docs/how-to/configure-metrics. Flags for vertical pod autoscaling: @@ -1225,7 +1227,7 @@ REQUIRED FLAGS NONE For more information, see - https://cloud.google.com/stackdriver/docs/solutions/gke/installing#available-logs + https://cloud.google.com/kubernetes-engine/docs/concepts/about-logs#available-logs Examples: @@ -1241,7 +1243,7 @@ REQUIRED FLAGS STATEFULSET, STORAGE, CADVISOR, KUBELET, DCGM For more information, see - https://cloud.google.com/stackdriver/docs/solutions/gke/installing#available-metrics + https://cloud.google.com/kubernetes-engine/docs/how-to/configure-metrics#available-metrics Examples: @@ -1274,7 +1276,7 @@ REQUIRED FLAGS The --logging-service flag is deprecated and will be removed in an upcoming release. Please use --logging instead. For more information, please read: - https://cloud.google.com/stackdriver/docs/solutions/gke/installing. + https://cloud.google.com/kubernetes-engine/docs/concepts/about-logs. --monitoring-service=MONITORING_SERVICE (DEPRECATED) Monitoring service to use for the cluster. Options are: @@ -1286,7 +1288,7 @@ REQUIRED FLAGS The --monitoring-service flag is deprecated and will be removed in an upcoming release. Please use --monitoring instead. For more information, please read: - https://cloud.google.com/stackdriver/docs/solutions/gke/installing. + https://cloud.google.com/kubernetes-engine/docs/how-to/configure-metrics. Basic auth diff --git a/gcloud/container/fleet/memberships/describe b/gcloud/container/fleet/memberships/describe index ff78d512e..4fc0e9496 100644 --- a/gcloud/container/fleet/memberships/describe +++ b/gcloud/container/fleet/memberships/describe @@ -17,7 +17,7 @@ EXAMPLES Then describe it: - $ gcloud container fleet memberships describe MEMBERSHIP_NAME + $ gcloud container fleet memberships describe MEMBERSHIP POSITIONAL ARGUMENTS Membership resource - The cluster membership to describe. The arguments in diff --git a/gcloud/container/hub/memberships/describe b/gcloud/container/hub/memberships/describe index 0d6502977..88c20d5d5 100644 --- a/gcloud/container/hub/memberships/describe +++ b/gcloud/container/hub/memberships/describe @@ -17,7 +17,7 @@ EXAMPLES Then describe it: - $ gcloud container hub memberships describe MEMBERSHIP_NAME + $ gcloud container hub memberships describe MEMBERSHIP POSITIONAL ARGUMENTS Membership resource - The cluster membership to describe. The arguments in diff --git a/gcloud/filestore/instances/create b/gcloud/filestore/instances/create index 23c7a3bc8..4aa714d97 100644 --- a/gcloud/filestore/instances/create +++ b/gcloud/filestore/instances/create @@ -9,7 +9,9 @@ SYNOPSIS --network=[connect-mode=CONNECT-MODE], [name=NAME],[reserved-ip-range=RESERVED-IP-RANGE] [--async] [--description=DESCRIPTION] [--labels=[KEY=VALUE,...]] - [--location=LOCATION] [--region=REGION] + [--location=LOCATION] + [--performance=[iops-by-capacity],[max-read-iops=MAX-READ-IOPS], + [max-read-iops-per-gb=MAX-READ-IOPS-PER-GB]] [--region=REGION] [--source-instance=SOURCE_INSTANCE] [--tier=TIER; default="BASIC_HDD"] [--kms-key=KMS_KEY : --kms-keyring=KMS_KEYRING --kms-location=KMS_LOCATION --kms-project=KMS_PROJECT] @@ -26,9 +28,10 @@ EXAMPLES --tier=TIER --file-share=name=VOLUME_NAME,capacity=CAPACITY \ --network=name=NETWORK_NAME,\ reserved-ip-range=RESERVED_IP_RANGE,connect-mode=CONNECT_MODE \ - --zone=ZONE --kms-key=KMS-KEY --kms-keyring=KMS_KEYRING \ - --kms-location=KMS_LOCATION --kms-project=KMS_PROJECT \ - --flags-file=FLAGS_FILE --source-instance=SOURCE_INSTANCE + --zone=ZONE --performance=PERFORMANCE --kms-key=KMS-KEY \ + --kms-keyring=KMS_KEYRING --kms-location=KMS_LOCATION \ + --kms-project=KMS_PROJECT --flags-file=FLAGS_FILE \ + --source-instance=SOURCE_INSTANCE Example json configuration file: { "--file-share": { "capacity": "61440", @@ -206,6 +209,58 @@ OPTIONAL FLAGS --location=LOCATION Location of the Cloud Filestore instance/operation. + --performance=[iops-by-capacity],[max-read-iops=MAX-READ-IOPS],[max-read-iops-per-gb=MAX-READ-IOPS-PER-GB] + Performance configuration for the instance. This flag is used to + configure the read IOPS provisioned for the instance. The instance's + write IOPS and read/write throughputs will be derived from the + configured read IOPS. For more information about the derived + performance limits see + https://cloud.google.com/filestore/docs/performance. Must be one of: + + iops-by-capacity + Default configuration. Automatically provisions the instance IOPS + based on its capacity. If the user changes the instance capacity, + IOPS will be automatically adjusted accordingly. The available IOPS + for a given capacity can be found here: https://cloud.google.com/filestore/docs/performance. + + max-read-iops + The number of IOPS to provision for the instance. + MAX-READ-IOPS must be in multiple of 1000 and in the supported IOPS + range for the current capacity of the instance. + For more details, see: https://cloud.google.com/filestore/docs/performance. + + max-read-iops-per-gb + Is used for setting the max IOPS of the instance by + specifying the IOPS per GB. When this parameter is used, the + max IOPS are derived from the instance capacity: + The instance max IOPS will be calculated by multiplying the + capacity of the instance (GB) by MAX-READ-IOPS-PER-GB, and rounding + to the nearest 1000. The max IOPS will be changed + dynamically based on the instance capacity. + MAX-READ-IOPS-PER-GB must be in the supported range of the instance. + For more details, see: https://cloud.google.com/filestore/docs/performance. + + Examples: + + Configure an instance implicitly with iops_by_capacity performance: + + $ gcloud filestore instances create example-cluster + + Configure an instance explicitly with iops_by_capacity performance: + + $ gcloud filestore instances create example-cluster \ + --performance=iops_by_capacity + + Configure an instance with max-read-iops performance: + + $ gcloud filestore instances create example-cluster \ + --performance=max-read-iops=1000 + + Configure an instance with max-read-iops-per-gb performance: + + $ gcloud filestore instances create example-cluster \ + --performance=max-read-iops-per-gb=5 + --region=REGION Region of the Cloud Filestore instance. diff --git a/gcloud/filestore/instances/update b/gcloud/filestore/instances/update index e65a1efd6..194feb47f 100644 --- a/gcloud/filestore/instances/update +++ b/gcloud/filestore/instances/update @@ -3,7 +3,9 @@ NAME SYNOPSIS gcloud filestore instances update (INSTANCE : --zone=ZONE) [--async] - [--description=DESCRIPTION] [--location=LOCATION] [--region=REGION] + [--description=DESCRIPTION] [--location=LOCATION] + [--performance=[iops-by-capacity],[max-read-iops=MAX-READ-IOPS], + [max-read-iops-per-gb=MAX-READ-IOPS-PER-GB]] [--region=REGION] [--update-labels=[KEY=VALUE,...]] [--clear-labels | --remove-labels=[KEY,...]] [[--file-share=[capacity=CAPACITY], @@ -102,6 +104,58 @@ FLAGS --location=LOCATION Location of the Cloud Filestore instance/operation. + --performance=[iops-by-capacity],[max-read-iops=MAX-READ-IOPS],[max-read-iops-per-gb=MAX-READ-IOPS-PER-GB] + Performance configuration for the instance. This flag is used to + configure the read IOPS provisioned for the instance. The instance's + write IOPS and read/write throughputs will be derived from the + configured read IOPS. For more information about the derived + performance limits see + https://cloud.google.com/filestore/docs/performance. Must be one of: + + iops-by-capacity + Default configuration. Automatically provisions the instance IOPS + based on its capacity. If the user changes the instance capacity, + IOPS will be automatically adjusted accordingly. The available IOPS + for a given capacity can be found here: https://cloud.google.com/filestore/docs/performance. + + max-read-iops + The number of IOPS to provision for the instance. + MAX-READ-IOPS must be in multiple of 1000 and in the supported IOPS + range for the current capacity of the instance. + For more details, see: https://cloud.google.com/filestore/docs/performance. + + max-read-iops-per-gb + Is used for setting the max IOPS of the instance by + specifying the IOPS per GB. When this parameter is used, the + max IOPS are derived from the instance capacity: + The instance max IOPS will be calculated by multiplying the + capacity of the instance (GB) by MAX-READ-IOPS-PER-GB, and rounding + to the nearest 1000. The max IOPS will be changed + dynamically based on the instance capacity. + MAX-READ-IOPS-PER-GB must be in the supported range of the instance. + For more details, see: https://cloud.google.com/filestore/docs/performance. + + Examples: + + Configure an instance implicitly with iops_by_capacity performance: + + $ gcloud filestore instances update example-cluster + + Configure an instance explicitly with iops_by_capacity performance: + + $ gcloud filestore instances update example-cluster \ + --performance=iops_by_capacity + + Configure an instance with max-read-iops performance: + + $ gcloud filestore instances update example-cluster \ + --performance=max-read-iops=1000 + + Configure an instance with max-read-iops-per-gb performance: + + $ gcloud filestore instances update example-cluster \ + --performance=max-read-iops-per-gb=5 + --region=REGION Region of the Cloud Filestore instance. diff --git a/gcloud/firestore/databases/create b/gcloud/firestore/databases/create index 676cbd21b..b7ebe9ffe 100644 --- a/gcloud/firestore/databases/create +++ b/gcloud/firestore/databases/create @@ -5,8 +5,8 @@ NAME SYNOPSIS gcloud firestore databases create --location=LOCATION [--database=DATABASE; default="(default)"] [--delete-protection] - [--enable-pitr] [--type=TYPE; default="firestore-native"] - [GCLOUD_WIDE_FLAG ...] + [--enable-pitr] [--kms-key-name=KMS_KEY_NAME] + [--type=TYPE; default="firestore-native"] [GCLOUD_WIDE_FLAG ...] EXAMPLES To create a Firestore Native database in nam5. @@ -34,6 +34,13 @@ EXAMPLES $ gcloud firestore databases create --location=nam5 --enable-pitr + To create a Firestore Native database in nam5 encrypted by a + Customer-managed encryption key (CMEK). + + $ gcloud firestore databases create --location=nam5 \ + --kms-key-name=projects/PROJECT_ID/locations/us/keyRings/\ + KEY_RING_ID/cryptoKeys/CRYPTO_KEY_ID + REQUIRED FLAGS --location=LOCATION The location to operate on. Available locations are listed at @@ -70,6 +77,19 @@ OPTIONAL FLAGS If set to true, PITR on the new database will be enabled. By default, this feature is not enabled. + --kms-key-name=KMS_KEY_NAME + The resource ID of a Cloud KMS key. If set, the database created will + be a Customer-Managed Encryption Key (CMEK) database encrypted with + this key. This feature is allowlist only in initial launch. + + Only a key in the same location as this database is allowed to be used for encryption. + For Firestore's nam5 multi-region, this corresponds to Cloud KMS location us. + For Firestore's eur3 multi-region, this corresponds to Cloud KMS location europe. + See https://cloud.google.com/kms/docs/locations. + + This value should be the KMS key resource ID in the format of `projects/{project_id}/locations/{kms_location}/keyRings/{key_ring}/cryptoKeys/{crypto_key}`. + How to retrieve this resource ID is listed at https://cloud.google.com/kms/docs/getting-resource-ids#getting_the_id_for_a_key_and_version. + --type=TYPE; default="firestore-native" The type of the database. TYPE must be one of: firestore-native, datastore-mode. diff --git a/gcloud/firestore/databases/list b/gcloud/firestore/databases/list index f7f44ff74..0eb698077 100644 --- a/gcloud/firestore/databases/list +++ b/gcloud/firestore/databases/list @@ -3,15 +3,23 @@ NAME project SYNOPSIS - gcloud firestore databases list [--filter=EXPRESSION] [--limit=LIMIT] - [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + gcloud firestore databases list [--show-deleted] [--filter=EXPRESSION] + [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] EXAMPLES - To list all Firestore databases. + To list all active Firestore databases. $ gcloud firestore databases list + To list all Firestore databases including deleted databases. + + $ gcloud firestore databases list --show-deleted + +FLAGS + --show-deleted + Show the deleted databases. + LIST COMMAND FLAGS --filter=EXPRESSION Apply a Boolean filter EXPRESSION to each resource item to be listed. diff --git a/gcloud/netapp/volumes/create b/gcloud/netapp/volumes/create index e28e6d5e2..22b7581e0 100644 --- a/gcloud/netapp/volumes/create +++ b/gcloud/netapp/volumes/create @@ -18,6 +18,8 @@ SYNOPSIS [kerberos-5p-read-only=KERBEROS-5P-READ-ONLY], [kerberos-5p-read-write=KERBEROS-5P-READ-WRITE], [nfsv3=NFSV3],[nfsv4=NFSV4]] [--labels=[KEY=VALUE,...]] + [--large-capacity=LARGE_CAPACITY] + [--multiple-endpoints=MULTIPLE_ENDPOINTS] [--restricted-actions=RESTRICTED_ACTION,[...]] [--security-style=SECURITY_STYLE; default="SECURITY_STYLE_UNSPECIFIED"] [--smb-settings=SMB_SETTING,[SMB_SETTING,...]] @@ -169,6 +171,14 @@ OPTIONAL FLAGS contain only hyphens (-), underscores (_), lowercase characters, and numbers. + --large-capacity=LARGE_CAPACITY + Boolean flag indicating whether Volume is a large capacity Volume or + not + + --multiple-endpoints=MULTIPLE_ENDPOINTS + Boolean flag indicating whether Volume is a multiple endpoints Volume + or not + --restricted-actions=RESTRICTED_ACTION,[...] Actions to be restricted for a volume. Valid restricted action options are: 'DELETE'. diff --git a/gcloud/network-connectivity/spokes/delete b/gcloud/network-connectivity/spokes/delete index ac23eed6b..ddabb20c4 100644 --- a/gcloud/network-connectivity/spokes/delete +++ b/gcloud/network-connectivity/spokes/delete @@ -68,7 +68,9 @@ API REFERENCE https://cloud.google.com/network-connectivity/docs/reference/networkconnectivity/rest NOTES - This variant is also available: + These variants are also available: $ gcloud alpha network-connectivity spokes delete + $ gcloud beta network-connectivity spokes delete + diff --git a/gcloud/network-connectivity/spokes/describe b/gcloud/network-connectivity/spokes/describe index 202b88079..a8664677d 100644 --- a/gcloud/network-connectivity/spokes/describe +++ b/gcloud/network-connectivity/spokes/describe @@ -65,7 +65,9 @@ API REFERENCE https://cloud.google.com/network-connectivity/docs/reference/networkconnectivity/rest NOTES - This variant is also available: + These variants are also available: $ gcloud alpha network-connectivity spokes describe + $ gcloud beta network-connectivity spokes describe + diff --git a/gcloud/network-connectivity/spokes/linked-vpc-network/create b/gcloud/network-connectivity/spokes/linked-vpc-network/create index bdd546e2a..10fc6768a 100644 --- a/gcloud/network-connectivity/spokes/linked-vpc-network/create +++ b/gcloud/network-connectivity/spokes/linked-vpc-network/create @@ -93,3 +93,9 @@ API REFERENCE This command uses the networkconnectivity/v1 API. The full documentation for this API can be found at: https://cloud.google.com/network-connectivity/docs/reference/networkconnectivity/rest + +NOTES + This variant is also available: + + $ gcloud beta network-connectivity spokes linked-vpc-network create + diff --git a/gcloud/network-connectivity/spokes/linked-vpc-network/help b/gcloud/network-connectivity/spokes/linked-vpc-network/help index c8c5ef6fa..77342a48f 100644 --- a/gcloud/network-connectivity/spokes/linked-vpc-network/help +++ b/gcloud/network-connectivity/spokes/linked-vpc-network/help @@ -21,3 +21,9 @@ COMMANDS update Update a VPC spoke. + +NOTES + This variant is also available: + + $ gcloud beta network-connectivity spokes linked-vpc-network + diff --git a/gcloud/network-connectivity/spokes/linked-vpc-network/update b/gcloud/network-connectivity/spokes/linked-vpc-network/update index e422cb6d5..fb9df16ba 100644 --- a/gcloud/network-connectivity/spokes/linked-vpc-network/update +++ b/gcloud/network-connectivity/spokes/linked-vpc-network/update @@ -94,3 +94,9 @@ API REFERENCE This command uses the networkconnectivity/v1 API. The full documentation for this API can be found at: https://cloud.google.com/network-connectivity/docs/reference/networkconnectivity/rest + +NOTES + This variant is also available: + + $ gcloud beta network-connectivity spokes linked-vpc-network update + diff --git a/gcloud/network-connectivity/spokes/list b/gcloud/network-connectivity/spokes/list index d24e622a1..4fe0d73b1 100644 --- a/gcloud/network-connectivity/spokes/list +++ b/gcloud/network-connectivity/spokes/list @@ -70,7 +70,9 @@ API REFERENCE https://cloud.google.com/network-connectivity/docs/reference/networkconnectivity/rest NOTES - This variant is also available: + These variants are also available: $ gcloud alpha network-connectivity spokes list + $ gcloud beta network-connectivity spokes list + diff --git a/gcloud/scc/findings/bulk-mute b/gcloud/scc/findings/bulk-mute index afb286544..2476ef7fc 100644 --- a/gcloud/scc/findings/bulk-mute +++ b/gcloud/scc/findings/bulk-mute @@ -6,7 +6,7 @@ SYNOPSIS gcloud scc findings bulk-mute (--folder=FOLDER | --organization=ORGANIZATION | --project=PROJECT) [--filter=FILTER] [--location=LOCATION; default="global"] - [GCLOUD_WIDE_FLAG ...] + [--mute-state=MUTE_STATE; default="muted"] [GCLOUD_WIDE_FLAG ...] DESCRIPTION Bulk mute Security Command Center findings based on a filter. @@ -66,6 +66,10 @@ OPTIONAL FLAGS location that is specified when data residency controls are enabled for Security Command Center. + --mute-state=MUTE_STATE; default="muted" + Desired mute state of the finding. MUTE_STATE must be one of: muted, + undefined. + GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, diff --git a/gcloud/scc/findings/set-mute b/gcloud/scc/findings/set-mute index d6cd015d7..1727dffd1 100644 --- a/gcloud/scc/findings/set-mute +++ b/gcloud/scc/findings/set-mute @@ -49,7 +49,8 @@ POSITIONAL ARGUMENTS REQUIRED FLAGS --mute=MUTE - Desired mute state of the finding. MUTE must be one of: muted, unmuted. + Desired mute state of the finding. MUTE must be one of: muted, unmuted, + undefined. OPTIONAL FLAGS --location=LOCATION; default="global" diff --git a/gcloud/scc/iac-validation-reports/describe b/gcloud/scc/iac-validation-reports/describe new file mode 100644 index 000000000..744d4fe87 --- /dev/null +++ b/gcloud/scc/iac-validation-reports/describe @@ -0,0 +1,76 @@ +NAME + gcloud scc iac-validation-reports describe - describe a Cloud Security + Command Center IaC Validation Report + +SYNOPSIS + gcloud scc iac-validation-reports describe + (REPORT : --location=LOCATION --organization=ORGANIZATION) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Describe a Cloud Security Command Center (SCC) IaC Validation Report. Takes + the name of the report as an argument. + + Returns IAC Validation Report as response. + +EXAMPLES + Describe an IAC Validation report named + organizations/123/locations/global/reports/abcef-gh : + + $ gcloud scc iac-validation-reports describe \ + organizations/123/locations/global/reports/abcef-gh + + or, run: + + $ gcloud scc iac-validation-reports describe abcef-gh \ + --organization=123 --location=global + +POSITIONAL ARGUMENTS + Report resource - IAC Validation report to be described. For example + organizations/123/locations/global/reports/abcef-gh. The arguments in this + group can be used to specify the attributes of this resource. + + This must be specified. + + REPORT + ID of the report or fully qualified identifier for the report. + + To set the report attribute: + ▸ provide the argument report on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + ID of the location where the resource exists (for example, global). + + To set the location attribute: + ▸ provide the argument report on the command line with a fully + specified name; + ▸ provide the argument --location on the command line. + + --organization=ORGANIZATION + ID of the organization which is the parent of the resource. + + To set the organization attribute: + ▸ provide the argument report on the command line with a fully + specified name; + ▸ provide the argument --organization on the command line. + +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. + +API REFERENCE + This command uses the securityposture/v1 API. The full documentation for + this API can be found at: https://cloud.google.com/security-command-center + +NOTES + This variant is also available: + + $ gcloud alpha scc iac-validation-reports describe + diff --git a/gcloud/scc/iac-validation-reports/help b/gcloud/scc/iac-validation-reports/help index b0e850e39..19aa9f233 100644 --- a/gcloud/scc/iac-validation-reports/help +++ b/gcloud/scc/iac-validation-reports/help @@ -19,6 +19,13 @@ COMMANDS create Create a Cloud Security Command Center (SCC) IaC Validation Report. + describe + Describe a Cloud Security Command Center (SCC) IaC Validation Report. + + list + Lists all the Cloud Security Command Center (SCC) IaC validation + reports for an organization. + NOTES This variant is also available: diff --git a/gcloud/scc/iac-validation-reports/list b/gcloud/scc/iac-validation-reports/list new file mode 100644 index 000000000..dd75bc283 --- /dev/null +++ b/gcloud/scc/iac-validation-reports/list @@ -0,0 +1,68 @@ +NAME + gcloud scc iac-validation-reports list - lists all the Cloud Security + Command Center IaC validation reports for an organization + +SYNOPSIS + gcloud scc iac-validation-reports list PARENT [--filter=EXPRESSION] + [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Lists all the Cloud Security Command Center (SCC) IaC validation reports + for an organization. + +EXAMPLES + To list Cloud Security Command Center IaC validation reports for + organization 123 in the global location, run: + + $ gcloud scc iac-validation-reports list \ + organizations/123/locations/global/reports + +POSITIONAL ARGUMENTS + PARENT + Parent of IaC validation reports. Formatted as + organizations//locations//reports. + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + +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. + +API REFERENCE + This command uses the securityposture/v1 API. The full documentation for + this API can be found at: https://cloud.google.com/security-command-center + +NOTES + This variant is also available: + + $ gcloud alpha scc iac-validation-reports list + diff --git a/gcloud/scc/muteconfigs/create b/gcloud/scc/muteconfigs/create index eb43d4909..e19a20c7b 100644 --- a/gcloud/scc/muteconfigs/create +++ b/gcloud/scc/muteconfigs/create @@ -4,7 +4,8 @@ NAME SYNOPSIS gcloud scc muteconfigs create MUTE_CONFIG [--description=DESCRIPTION] - [--filter=FILTER] [--location=LOCATION; default="global"] + [--expiry-time=EXPIRY_TIME] [--filter=FILTER] + [--location=LOCATION; default="global"] [--type=TYPE; default="static"] [--folder=FOLDER | --organization=ORGANIZATION | --project=PROJECT] [GCLOUD_WIDE_FLAG ...] @@ -48,6 +49,12 @@ FLAGS --description=DESCRIPTION The text that will be used to describe a mute configuration. + --expiry-time=EXPIRY_TIME + The expiry of the mute config. Only applicable for dynamic configs. If + the expiry is set, when the config expires, it is removed from all + findings. See $ gcloud topic datetimes for information on supported + time formats. + --filter=FILTER The filter string which will applied to findings muted by a mute configuration. @@ -63,6 +70,10 @@ FLAGS location that is specified when data residency controls are enabled for Security Command Center. + --type=TYPE; default="static" + The mute configuration type. Immutable after creation. TYPE must be one + of: static, dynamic. + At most one of these can be specified: --folder=FOLDER diff --git a/gcloud/scc/muteconfigs/update b/gcloud/scc/muteconfigs/update index 3af1ec001..e2252b174 100644 --- a/gcloud/scc/muteconfigs/update +++ b/gcloud/scc/muteconfigs/update @@ -4,8 +4,8 @@ NAME SYNOPSIS gcloud scc muteconfigs update MUTE_CONFIG [--description=DESCRIPTION] - [--filter=FILTER] [--location=LOCATION; default="global"] - [--update-mask=UPDATE_MASK] + [--expiry-time=EXPIRY_TIME] [--filter=FILTER] + [--location=LOCATION; default="global"] [--update-mask=UPDATE_MASK] [--folder=FOLDER | --organization=ORGANIZATION | --project=PROJECT] [GCLOUD_WIDE_FLAG ...] @@ -49,6 +49,12 @@ FLAGS --description=DESCRIPTION The text that will be used to describe a mute configuration. + --expiry-time=EXPIRY_TIME + The expiry of the mute config. Only applicable for dynamic configs. If + the expiry is set, when the config expires, it is removed from all + findings. See $ gcloud topic datetimes for information on supported + time formats. + --filter=FILTER The filter string which will applied to findings muted by a mute configuration. diff --git a/gcloud/sql/instances/help b/gcloud/sql/instances/help index ac786ccf2..84dd39f4d 100644 --- a/gcloud/sql/instances/help +++ b/gcloud/sql/instances/help @@ -69,6 +69,9 @@ COMMANDS restore-backup Restores a backup of a Cloud SQL instance. + switchover + Switches over a Cloud SQL instance to one of its replicas. + NOTES These variants are also available: diff --git a/gcloud/sql/instances/switchover b/gcloud/sql/instances/switchover new file mode 100644 index 000000000..0edd9b540 --- /dev/null +++ b/gcloud/sql/instances/switchover @@ -0,0 +1,46 @@ +NAME + gcloud sql instances switchover - switches over a Cloud SQL instance to one + of its replicas + +SYNOPSIS + gcloud sql instances switchover REPLICA [--async] [--db-timeout=DB_TIMEOUT] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Switches over a Cloud SQL instance to one of its replicas. Only supported + on Cloud SQL for SQL Server and MySQL instances. + +EXAMPLES + To switch over an instance to its replica called replica-instance: + + $ gcloud sql instances switchover replica-instance + +POSITIONAL ARGUMENTS + REPLICA + Cloud SQL replica ID. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --db-timeout=DB_TIMEOUT + (MySQL only) Cloud SQL instance operations timeout, which is the sum of + all database operations. Default value is 10 minutes and can be + modified to a maximum value of 24h. + +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 sql instances switchover + + $ gcloud beta sql instances switchover +