diff --git a/gcloud/_version b/gcloud/_version index 72e3a7790..15b615ad0 100644 --- a/gcloud/_version +++ b/gcloud/_version @@ -1,7 +1,8 @@ -Google Cloud SDK 402.0.0 -alpha 2022.09.12 -beta 2022.09.12 -bq 2.0.75 -core 2022.09.12 +Google Cloud SDK 403.0.0 +alpha 2022.09.20 +beta 2022.09.20 +bq 2.0.77 +bundled-python3-unix 3.9.12 +core 2022.09.20 gcloud-crc32c 1.0.0 gsutil 5.13 diff --git a/gcloud/alpha/ai/indexes/help b/gcloud/alpha/ai/indexes/help index be0c61a18..96948fa83 100644 --- a/gcloud/alpha/ai/indexes/help +++ b/gcloud/alpha/ai/indexes/help @@ -27,9 +27,15 @@ COMMANDS list (ALPHA) Lists the indexes of the given project and region. + remove-datapoints + (ALPHA) Remove data points from the specified index. + update (ALPHA) Update an Vertex AI index. + upsert-datapoints + (ALPHA) Upsert data points into the specified index. + 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/ai/indexes/remove-datapoints b/gcloud/alpha/ai/indexes/remove-datapoints new file mode 100644 index 000000000..01875eb5a --- /dev/null +++ b/gcloud/alpha/ai/indexes/remove-datapoints @@ -0,0 +1,76 @@ +NAME + gcloud alpha ai indexes remove-datapoints - remove data points from the + specified index + +SYNOPSIS + gcloud alpha ai indexes remove-datapoints (INDEX : --region=REGION) + (--datapoint-ids=[DATAPOINT_IDS,...] + | --datapoints-from-file=DATAPOINTS_FROM_FILE) [GCLOUD_WIDE_FLAG ...] + +EXAMPLES + To remove datapoints from an index '123', run: + + $ gcloud alpha ai indexes remove-datapoints 123 \ + --datapoint-ids=example1,example2 --project=example \ + --region=us-central1 + + Or put datapoint ids in a json file and run: + + $ gcloud alpha ai indexes remove-datapoints 123 \ + --datapoints-from-file=example.json --project=example \ + --region=us-central1 + +POSITIONAL ARGUMENTS + Index resource - Index to remove data points from. 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 index 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. + + INDEX + ID of the index or fully qualified identifier for the index. To set + the name attribute: + ▸ provide the argument index on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --region=REGION + Cloud region for the index. To set the region attribute: + ▸ provide the argument index on the command line with a fully + specified name; + ▸ provide the argument --region on the command line; + ▸ set the property ai/region; + ▸ choose one from the prompted list of available regions. + +REQUIRED FLAGS + Exactly one of these must be specified: + + --datapoint-ids=[DATAPOINT_IDS,...] + List of index datapoint ids to be removed from the index. + + --datapoints-from-file=DATAPOINTS_FROM_FILE + Path to a local JSON file that contains the data points that need to + be added to the index. + +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. This variant is also available: + + $ gcloud beta ai indexes remove-datapoints + diff --git a/gcloud/alpha/ai/indexes/upsert-datapoints b/gcloud/alpha/ai/indexes/upsert-datapoints new file mode 100644 index 000000000..9d34c4568 --- /dev/null +++ b/gcloud/alpha/ai/indexes/upsert-datapoints @@ -0,0 +1,64 @@ +NAME + gcloud alpha ai indexes upsert-datapoints - upsert data points into the + specified index + +SYNOPSIS + gcloud alpha ai indexes upsert-datapoints (INDEX : --region=REGION) + --datapoints-from-file=DATAPOINTS_FROM_FILE [GCLOUD_WIDE_FLAG ...] + +EXAMPLES + To upsert datapoints into an index '123', run: + + $ gcloud alpha ai indexes upsert-datapoints 123 \ + --datapoints-from-file=example.json --project=example \ + --region=us-central1 + +POSITIONAL ARGUMENTS + Index resource - Index to upsert data points from. 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 index 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. + + INDEX + ID of the index or fully qualified identifier for the index. To set + the name attribute: + ▸ provide the argument index on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --region=REGION + Cloud region for the index. To set the region attribute: + ▸ provide the argument index on the command line with a fully + specified name; + ▸ provide the argument --region on the command line; + ▸ set the property ai/region; + ▸ choose one from the prompted list of available regions. + +REQUIRED FLAGS + --datapoints-from-file=DATAPOINTS_FROM_FILE + Path to a local JSON file that contains the data points that need to be + added to the index. + +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. This variant is also available: + + $ gcloud beta ai indexes upsert-datapoints + diff --git a/gcloud/alpha/alloydb/clusters/create b/gcloud/alpha/alloydb/clusters/create index 0e89fd9fe..10ddfca2e 100644 --- a/gcloud/alpha/alloydb/clusters/create +++ b/gcloud/alpha/alloydb/clusters/create @@ -5,6 +5,13 @@ NAME SYNOPSIS gcloud alpha alloydb clusters create CLUSTER --password=PASSWORD --region=REGION [--async] [--network=NETWORK] + [--disable-automated-backup + | [--automated-backup-days-of-week=[DAYS_OF_WEEK,...] + --automated-backup-start-times=[START_TIMES,...] + : --automated-backup-window=TIMEOUT_PERIOD + [--automated-backup-encryption-key=AUTOMATED_BACKUP_ENCRYPTION_KEY + : --automated-backup-encryption-key-keyring=AUTOMATED_BACKUP_ENCRYPTION_KEY_KEYRING --automated-backup-encryption-key-location=AUTOMATED_BACKUP_ENCRYPTION_KEY_LOCATION --automated-backup-encryption-key-project=AUTOMATED_BACKUP_ENCRYPTION_KEY_PROJECT] --automated-backup-retention-count=RETENTION_COUNT | --automated-backup-retention-period=RETENTION_PERIOD]] + [--disable-pitr | --pitr-log-retention-window=RETENTION_PERIOD] [--kms-key=KMS_KEY : --kms-keyring=KMS_KEYRING --kms-location=KMS_LOCATION --kms-project=KMS_PROJECT] [GCLOUD_WIDE_FLAG ...] @@ -42,6 +49,102 @@ OPTIONAL FLAGS network, 'testsharednetwork', this would be of the form:--network=projects/testproject/global/networks/testsharednetwork + Automated backup policy. If unspecified, automated backups are enabled. + + At most one of these can be specified: + + --disable-automated-backup + Disables automated backups on the cluster. + + Enable automated backup policy. + + --automated-backup-days-of-week=[DAYS_OF_WEEK,...] + Comma-separated list of days of the week to perform a backup. At + least one day of the week must be provided. (e.g., + --automated-backup-days-of-week=MONDAY,WEDNESDAY,SUNDAY). + DAYS_OF_WEEK must be one of: MONDAY, TUESDAY, WEDNESDAY, THURSDAY, + FRIDAY, SATURDAY, SUNDAY. + + This flag argument must be specified if any of the other arguments + in this group are specified. + + --automated-backup-start-times=[START_TIMES,...] + Comma-separated list of times during the day to start a backup. At + least one start time must be provided. The start times are assumed + to be in UTC and required to be an exact hour in the format HH:00. + (e.g., --automated-backup-start-times=01:00,13:00) + + This flag argument must be specified if any of the other arguments + in this group are specified. + + --automated-backup-window=TIMEOUT_PERIOD + The length of the time window beginning at start time during which + a backup can be taken. If a backup does not succeed within this + time window, it will be canceled and considered failed. The backup + window must be at least 5 minutes long. There is no upper bound on + the window. If not set, it will default to 1 hour. + + Key resource - The Cloud KMS (Key Management Service) cryptokey that + will be used to protect the automated backups. The 'AlloyDB Service + Agent' service account must hold permission 'Cloud KMS CryptoKey + Encrypter/Decrypter'. The arguments in this group can be used to + specify the attributes of this resource. + + --automated-backup-encryption-key=AUTOMATED_BACKUP_ENCRYPTION_KEY + ID of the key or fully qualified identifier for the key. To set + the kms-key attribute: + ◇ provide the argument --automated-backup-encryption-key on the + command line. + + This flag argument must be specified if any of the other + arguments in this group are specified. + + --automated-backup-encryption-key-keyring=AUTOMATED_BACKUP_ENCRYPTION_KEY_KEYRING + The KMS keyring of the key. To set the kms-keyring attribute: + ◇ provide the argument --automated-backup-encryption-key on the + command line with a fully specified name; + ◇ provide the argument + --automated-backup-encryption-key-keyring on the command line. + + --automated-backup-encryption-key-location=AUTOMATED_BACKUP_ENCRYPTION_KEY_LOCATION + The Cloud location for the key. To set the kms-location + attribute: + ◇ provide the argument --automated-backup-encryption-key on the + command line with a fully specified name; + ◇ provide the argument + --automated-backup-encryption-key-location on the command line. + + --automated-backup-encryption-key-project=AUTOMATED_BACKUP_ENCRYPTION_KEY_PROJECT + The Cloud project for the key. To set the kms-project attribute: + ◇ provide the argument --automated-backup-encryption-key on the + command line with a fully specified name; + ◇ provide the argument + --automated-backup-encryption-key-project on the command line; + ◇ set the property core/project. + + Retention policy. If no retention policy is provided, all automated + backups will be retained. + + At most one of these can be specified: + + --automated-backup-retention-count=RETENTION_COUNT + Number of most recent successful backups retained. + + --automated-backup-retention-period=RETENTION_PERIOD + Retention period of the backup relative to creation time. See $ + gcloud topic datetimes for information on duration formats. + + PITR configuration. + + At most one of these can be specified: + + --disable-pitr + Disables PITR on the cluster. + + --pitr-log-retention-window=RETENTION_PERIOD + Retention window of the log files saved to support PITR. See $ gcloud + topic datetimes for information on absolute duration formats. + Key resource - The Cloud KMS (Key Management Service) cryptokey that will be used to protect the cluster. The 'AlloyDB Service Agent' service account must hold permission 'Cloud KMS CryptoKey Encrypter/Decrypter'. diff --git a/gcloud/alpha/compute/disks/create b/gcloud/alpha/compute/disks/create index 62e20031f..7f564629b 100644 --- a/gcloud/alpha/compute/disks/create +++ b/gcloud/alpha/compute/disks/create @@ -8,8 +8,9 @@ SYNOPSIS [--guest-os-features=[GUEST_OS_FEATURE,...]] [--interface=INTERFACE] [--labels=[KEY=VALUE,...]] [--licenses=[LICENSE,...]] [--multi-writer] [--physical-block-size=PHYSICAL_BLOCK_SIZE; default="4096"] - [--provisioned-iops=PROVISIONED_IOPS] [--replica-zones=ZONE,ZONE] - [--no-require-csek-key-create] + [--provisioned-iops=PROVISIONED_IOPS] + [--provisioned-throughput=PROVISIONED_THROUGHPUT] + [--replica-zones=ZONE,ZONE] [--no-require-csek-key-create] [--resource-policies=[RESOURCE_POLICY,...]] [--size=SIZE] [--type=TYPE] [--user-licenses=[LICENSE,...]] [--image-family-scope=IMAGE_FAMILY_SCOPE @@ -125,6 +126,10 @@ FLAGS between 10000 and 120000. If not specified, the default value is 100000. + --provisioned-throughput=PROVISIONED_THROUGHPUT + Provisioned throughput of disk to create. The throughput unit is MB per + sec. Only for use with disks of type hyperdisk-throughput. + --replica-zones=ZONE,ZONE A comma-separated list of exactly 2 zones that a regional disk will be replicated to. Required when creating regional disk. The zones must be diff --git a/gcloud/alpha/compute/disks/update b/gcloud/alpha/compute/disks/update index 610f8b2a2..153b8b21a 100644 --- a/gcloud/alpha/compute/disks/update +++ b/gcloud/alpha/compute/disks/update @@ -3,6 +3,8 @@ NAME SYNOPSIS gcloud alpha compute disks update DISK_NAME + [--provisioned-iops=PROVISIONED_IOPS] + [--provisioned-throughput=PROVISIONED_THROUGHPUT] [--update-labels=[KEY=VALUE,...]] [--clear-architecture | --update-architecture=UPDATE_ARCHITECTURE] [--clear-labels | --remove-labels=[KEY,...]] @@ -38,6 +40,14 @@ POSITIONAL ARGUMENTS Name of the disk to update. FLAGS + --provisioned-iops=PROVISIONED_IOPS + Provisioned IOPS of disk to update. Only for use with disks of type + hyperdisk-extreme. + + --provisioned-throughput=PROVISIONED_THROUGHPUT + Provisioned throughput of disk to update. The throughput unit is MB per + sec. Only for use with disks of type hyperdisk-throughput + --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. diff --git a/gcloud/alpha/compute/help b/gcloud/alpha/compute/help index 4cd9aa8a5..476e7943e 100644 --- a/gcloud/alpha/compute/help +++ b/gcloud/alpha/compute/help @@ -136,6 +136,9 @@ GROUPS public-delegated-prefixes (ALPHA) Manage public delegated prefix resources. + queued-resources + (ALPHA) Manage queued resources. + regions (ALPHA) List Compute Engine regions. diff --git a/gcloud/alpha/compute/queued-resources/cancel b/gcloud/alpha/compute/queued-resources/cancel new file mode 100644 index 000000000..a9c2596cc --- /dev/null +++ b/gcloud/alpha/compute/queued-resources/cancel @@ -0,0 +1,59 @@ +NAME + gcloud alpha compute queued-resources cancel - cancel Compute Engine queued + resources + +SYNOPSIS + gcloud alpha compute queued-resources cancel NAME [NAME ...] [--zone=ZONE] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) gcloud alpha compute queued-resources cancel cancels one or more + Compute Engine queued resources. + +EXAMPLES + To cancel Compute Engine queued resources with the names + 'queued-resource-1' and 'queued-resource-2', run: + + $ gcloud alpha compute queued-resources cancel queued-resource-1 \ + queued-resource-2 + +POSITIONAL ARGUMENTS + NAME [NAME ...] + Names of the queued resources to cancel. + +FLAGS + --zone=ZONE + Zone of the queued resources to cancel. If not specified and the + compute/zone property isn't set, you might be prompted to select a zone + (interactive mode only). + + To avoid prompting when this flag is omitted, you can set the + compute/zone property: + + $ gcloud config set compute/zone ZONE + + A list of zones can be fetched by running: + + $ gcloud compute zones list + + To unset the property, run: + + $ gcloud config unset compute/zone + + Alternatively, the zone can be stored in the environment variable + CLOUDSDK_COMPUTE_ZONE. + +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/compute/queued-resources/create b/gcloud/alpha/compute/queued-resources/create new file mode 100644 index 000000000..36a8c9d5e --- /dev/null +++ b/gcloud/alpha/compute/queued-resources/create @@ -0,0 +1,998 @@ +NAME + gcloud alpha compute queued-resources create - create a Compute Engine + queued resource + +SYNOPSIS + gcloud alpha compute queued-resources create NAME + (--name-pattern=NAME_PATTERN | --predefined-names=[INSTANCE_NAME,...]) + (--valid-until-duration=VALID_UNTIL_DURATION + | --valid-until-time=VALID_UNTIL_TIME) + [--accelerator=[count=COUNT],[type=TYPE]] [--no-address] [--async] + [--no-boot-disk-auto-delete] + [--boot-disk-device-name=BOOT_DISK_DEVICE_NAME] + [--boot-disk-provisioned-iops=BOOT_DISK_PROVISIONED_IOPS] + [--boot-disk-size=BOOT_DISK_SIZE] [--boot-disk-type=BOOT_DISK_TYPE] + [--can-ip-forward] [--confidential-compute] [--count=COUNT] + [--create-disk=[PROPERTY=VALUE,...]] [--description=DESCRIPTION] + [--disk=[boot=BOOT], + [device-name=DEVICE-NAME],[name=NAME],[scope=SCOPE]] + [--enable-display-device] [--[no-]enable-nested-virtualization] + [--[no-]enable-uefi-networking] [--erase-windows-vss-signature] + [--host-error-timeout-seconds=HOST_ERROR_TIMEOUT_SECONDS] + [--instance-termination-action=INSTANCE_TERMINATION_ACTION] + [--labels=[KEY=VALUE,...]] + [--local-ssd=[device-name=DEVICE-NAME], + [interface=INTERFACE],[size=SIZE]] + [--location-policy=[ZONE=POLICY,...]] [--machine-type=MACHINE_TYPE] + [--max-run-duration=MAX_RUN_DURATION] + [--metadata=KEY=VALUE,[KEY=VALUE,...]] + [--metadata-from-file=KEY=LOCAL_FILE_PATH,[...]] + [--min-count=MIN_COUNT] [--min-cpu-platform=PLATFORM] + [--min-node-cpu=MIN_NODE_CPU] [--network=NETWORK] + [--network-interface=[PROPERTY=VALUE,...]] + [--network-performance-configs=[PROPERTY=VALUE,...]] + [--network-tier=NETWORK_TIER] [--numa-node-count=NUMA_NODE_COUNT] + [--post-key-revocation-action-type=POLICY] [--preemptible] + [--provisioning-model=PROVISIONING_MODEL] + [--resource-manager-tags=[KEY=VALUE,...]] + [--resource-policies=[RESOURCE_POLICY,...]] [--no-restart-on-failure] + [--secure-tags=SECURE_TAG,[SECURE_TAG,...]] + [--shielded-integrity-monitoring] [--shielded-secure-boot] + [--shielded-vtpm] [--source-instance-template=SOURCE_INSTANCE_TEMPLATE] + [--subnet=SUBNET] [--tags=TAG,[TAG,...]] + [--target-distribution-shape=SHAPE] + [--termination-time=TERMINATION_TIME] + [--threads-per-core=THREADS_PER_CORE] + [--visible-core-count=VISIBLE_CORE_COUNT] [--zone=ZONE] + [--boot-disk-kms-key=BOOT_DISK_KMS_KEY + : --boot-disk-kms-keyring=BOOT_DISK_KMS_KEYRING + --boot-disk-kms-location=BOOT_DISK_KMS_LOCATION + --boot-disk-kms-project=BOOT_DISK_KMS_PROJECT] + [--custom-cpu=CUSTOM_CPU --custom-memory=CUSTOM_MEMORY + : --custom-extensions --custom-vm-type=CUSTOM_VM_TYPE] + [--image-project=IMAGE_PROJECT --image=IMAGE + | --image-family=IMAGE_FAMILY | --source-snapshot=SOURCE_SNAPSHOT] + [--maintenance-policy=MAINTENANCE_POLICY + | --on-host-maintenance=MAINTENANCE_POLICY] + [--public-dns | --no-public-dns] + [--reservation=RESERVATION + --reservation-affinity=RESERVATION_AFFINITY; default="any"] + [--scopes=[SCOPE,...] | --no-scopes] + [--service-account=SERVICE_ACCOUNT | --no-service-account] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Create a Compute Engine queued resource. + +EXAMPLES + To create a queued resource, run: + + $ gcloud alpha compute queued-resources create queued-resource-1 \ + --count=1 --name-pattern=instance-# --valid-until-duration=7d \ + --zone=us-central1-a + +POSITIONAL ARGUMENTS + NAME + Name of the queued resource to create. + +REQUIRED FLAGS + Exactly one of these must be specified: + + --name-pattern=NAME_PATTERN + Name pattern for generating instance names. Specify a pattern with a + single sequence of hash (#) characters that will be replaced with + generated sequential numbers of instances. E.g. name pattern of + 'instance-###' will generate instance names 'instance-001', + 'instance-002', and so on, until the number of virtual machines + specified using --count is reached. If instances matching name + pattern exist, the new instances will be assigned names to avoid + clashing with the existing ones. E.g. if there exists instance-123, + the new instances will start at instance-124 and increment from + there. + + --predefined-names=[INSTANCE_NAME,...] + List of predefined names for the Compute Engine virtual machines + being created. If --count is specified alongside this flag, provided + count must equal the amount of names provided to this flag. If + --count is not specified, the number of virtual machines created will + equal the number of names provided. + + Exactly one of these must be specified: + + --valid-until-duration=VALID_UNTIL_DURATION + Relative deadline for waiting for capacity. + + --valid-until-time=VALID_UNTIL_TIME + Absolute deadline for waiting for capacity in RFC3339 text format. + +OPTIONAL FLAGS + --accelerator=[count=COUNT],[type=TYPE] + Attaches accelerators (e.g. GPUs) to the instances. + + type + The specific type (e.g. nvidia-tesla-k80 for nVidia Tesla K80) of + accelerator to attach to the instances. Use 'gcloud compute + accelerator-types list' to learn about all available accelerator + types. + + count + Number of accelerators to attach to each instance. The default + value is 1. + + --no-address + If provided, the instances are not assigned external IP addresses. To + pull container images, you must configure private Google access if + using Container Registry or configure Cloud NAT for instances to access + container images directly. For more information, see: + ◆ https://cloud.google.com/vpc/docs/configure-private-google-access + ◆ https://cloud.google.com/nat/docs/using-nat + + --async + Return immediately, without waiting for the operation in progress to + complete. + + --boot-disk-auto-delete + Automatically delete boot disks when their instances are deleted. + Enabled by default, use --no-boot-disk-auto-delete to disable. + + --boot-disk-device-name=BOOT_DISK_DEVICE_NAME + The name the guest operating system will see for the boot disk. This + option can only be specified if a new boot disk is being created (as + opposed to mounting an existing persistent disk). + + --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 + between 10,000 and 120,000. + + --boot-disk-size=BOOT_DISK_SIZE + The size of the boot disk. This option can only be specified if a new + boot disk is being created (as opposed to mounting an existing + persistent disk). The value must be a whole number followed by a size + unit of KB for kilobyte, MB for megabyte, GB for gigabyte, or TB for + terabyte. For example, 10GB will produce a 10 gigabyte disk. The + minimum size a boot disk can have is 10 GB. Disk size must be a + multiple of 1 GB. Limit boot disk size to 2 TB to account for MBR + partition table limitations. Default size unit is GB. + + --boot-disk-type=BOOT_DISK_TYPE + The type of the boot disk. This option can only be specified if a new + boot disk is being created (as opposed to mounting an existing + persistent disk). To get a list of available disk types, run $ gcloud + compute disk-types list. + + --can-ip-forward + If provided, allows the instances to send and receive packets with + non-matching destination or source IP addresses. + + --confidential-compute + The instance boots with Confidential Computing enabled. Confidential + Computing is based on Secure Encrypted Virtualization (SEV), an AMD + virtualization feature for running confidential instances. + + --count=COUNT + Number of Compute Engine virtual machines to create. If specified, and + --predefined-names is specified, count must equal the amount of names + provided to --predefined-names. If not specified, the number of virtual + machines created will equal the number of names provided to + --predefined-names. + + --create-disk=[PROPERTY=VALUE,...] + Creates and attaches persistent disks to the instances. + + name + Specifies the name of the disk. This option cannot be specified if + more than one instance is being created. + + description + Optional textual description for the disk being created. + + mode + Specifies the mode of the disk. Supported options are ro for + read-only and rw for read-write. If omitted, rw is used as a + default. + + image + Specifies the name of the image that the disk will be initialized + with. A new disk will be created based on the given image. To view + a list of public images and projects, run $ gcloud compute images + list. It is best practice to use image when a specific version of + an image is needed. If both image and image-family flags are + omitted a blank disk will be created. + + image-family + The image family for the operating system that the boot disk will + be initialized with. Compute Engine offers multiple Linux + distributions, some of which are available as both regular and + Shielded VM images. When a family is specified instead of an image, + the latest non-deprecated image associated with that family is + used. It is best practice to use --image-family when the latest + version of an image is needed. + + image-project + The Google Cloud project against which all image and image family + references will be resolved. It is best practice to define + image-project. A full list of available image projects can be + generated by running gcloud compute images list. + + ▸ If specifying one of our public images, image-project must be + provided. + ▸ If there are several of the same image-family value in multiple + projects, image-project must be specified to clarify the image to + be used. + ▸ If not specified and either image or image-family is provided, + the current default project is used. + + size + The size of the disk. The value must be a whole number followed by + a size unit of KB for kilobyte, MB for megabyte, GB for gigabyte, + or TB for terabyte. For example, 10GB will produce a 10 gigabyte + disk. Disk size must be a multiple of 1 GB. If not specified, the + default image size will be used for the new disk. + + type + The type of the disk. To get a list of available disk types, run $ + gcloud compute disk-types list. The default disk type is + pd-standard. + + device-name + An optional name that indicates the disk name the guest operating + system will see. If omitted, a device name of the form + persistent-disk-N will be used. + + 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 between 10,000 and 120,000. + + disk-resource-policy + Resource policy to apply to the disk. Specify a full or partial + URL. For example: + ▸ https://www.googleapis.com/compute/v1/projects/my-project/regions/us-central1/resourcePolicies/my-resource-policy + ▸ projects/my-project/regions/us-central1/resourcePolicies/my-resource-policy + + For more information, see the following docs: + ▸ https://cloud.google.com/sdk/gcloud/reference/beta/compute/resource-policies/ + ▸ https://cloud.google.com/compute/docs/disks/scheduled-snapshots + + auto-delete + If yes, this persistent disk will be automatically deleted when the + instance is deleted. However, if the disk is later detached from + the instance, this option won't apply. The default value for this + is yes. + + architecture + Specifies the architecture or processor type that this disk can + support. For available processor types on Compute Engine, see + https://cloud.google.com/compute/docs/cpu-platforms. + + 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 + default value for this is no. + + kms-key + Fully qualified Cloud KMS cryptokey name that will protect the + disk. + + This can either be the fully qualified path or the name. + + The fully qualified Cloud KMS cryptokey name format is: + projects//locations//keyRings// + cryptoKeys/. + + If the value is not fully qualified then kms-location, kms-keyring, + and optionally kms-project are required. + + See + https://cloud.google.com/compute/docs/disks/customer-managed-encryption + for more details. + + kms-project + Project that contains the Cloud KMS cryptokey that will protect the + disk. + + If the project is not specified then the project where the disk is + being created will be used. + + If this flag is set then key-location, kms-keyring, and kms-key are + required. + + See + https://cloud.google.com/compute/docs/disks/customer-managed-encryption + for more details. + + kms-location + Location of the Cloud KMS cryptokey to be used for protecting the + disk. + + All Cloud KMS cryptokeys are reside in a 'location'. To get a list + of possible locations run 'gcloud kms locations list'. If this flag + is set then kms-keyring and kms-key are required. See + https://cloud.google.com/compute/docs/disks/customer-managed-encryption + for more details. + + kms-keyring + The keyring which contains the Cloud KMS cryptokey that will + protect the disk. + + If this flag is set then kms-location and kms-key are required. + + See + https://cloud.google.com/compute/docs/disks/customer-managed-encryption + for more details. + + source-snapshot + The source disk snapshot that will be used to create the disk. You + can provide this as a full URL to the snapshot or just the snapshot + name. For example, the following are valid values: + + ▸ https://compute.googleapis.com/compute/v1/projects/myproject/global/snapshots/snapshot + ▸ snapshot + + image-csek-required + Specifies the name of the CSK protected image that the disk will be + initialized with. A new disk will be created based on the given + image. To view a list of public images and projects, run $ gcloud + compute images list. It is best practice to use image when a + specific version of an image is needed. If both image and + image-family flags are omitted a blank disk will be created. Must + be specified with image-csek-key-file. + + image-csek-key-file + Path to a Customer-Supplied Encryption Key (CSEK) key file for the + image. Must be specified with image-csek-required. + + --description=DESCRIPTION + Specifies a textual description of the instances. + + --disk=[boot=BOOT],[device-name=DEVICE-NAME],[name=NAME],[scope=SCOPE] + Attaches persistent disks to the instances. The disks specified must + already exist. + + name + The disk to attach to the instances. + + boot + If yes, indicates that this is a boot disk. The virtual machines + will use the first partition of the disk for their root file + systems. The default value for this is no. + + device-name + An optional name that indicates the disk name the guest operating + system will see. If omitted, a device name of the form + persistent-disk-N will be used. + + scope + Can be zonal or regional. If zonal, the disk is interpreted as a + zonal disk in the same zone as the instance (default). If regional, + the disk is interpreted as a regional disk in the same region as + the instance. The default value for this is zonal. + + --enable-display-device + Enable a display device on VM instances. Disabled by default. + + --[no-]enable-nested-virtualization + If set to true, enables nested virtualization for the instance. Use + --enable-nested-virtualization to enable and + --no-enable-nested-virtualization to disable. + + --[no-]enable-uefi-networking + If set to true, enables UEFI networking for the instance creation. Use + --enable-uefi-networking to enable and --no-enable-uefi-networking to + disable. + + --erase-windows-vss-signature + Specifies whether the disk restored from source snapshots or source + machine image should erase Windows specific VSS signature. See + https://cloud.google.com/sdk/gcloud/reference/compute/disks/snapshot#--guest-flush + + --host-error-timeout-seconds=HOST_ERROR_TIMEOUT_SECONDS + The timeout in seconds for host error detection. The value must be set + with 30 second increments, with a range of 90 to 330 seconds. If unset, + the default behavior of the host error recovery is used. + + --instance-termination-action=INSTANCE_TERMINATION_ACTION + Specifies the termination action that will be taken upon VM preemption. + INSTANCE_TERMINATION_ACTION must be one of: + + DELETE + Permanently delete the VM. + STOP + Default. Stop the VM without preserving memory. The VM can be + restarted later. + + --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. + + --local-ssd=[device-name=DEVICE-NAME],[interface=INTERFACE],[size=SIZE] + Attaches a local SSD to the instances. + + This flag is currently in alpha and beta versions only and might change + without notice. + + device-name + Optional. A name that indicates the disk name the guest operating + system will see. Can only be specified if interface is SCSI. If + omitted, a device name of the form local-ssd-N will be used. + + interface + Optional. The kind of disk interface exposed to the VM for this + SSD. Valid values are SCSI and NVME. SCSI is the default and is + supported by more guest operating systems. NVME might provide + higher performance. + + size + Optional. The only valid value is 375GB. Specify the --local-ssd + flag multiple times if you need multiple 375GB local SSD + partitions. You can specify a maximum of 24 local SSDs for a + maximum of 9TB attached to an instance. + + --location-policy=[ZONE=POLICY,...] + Policy for which zones to include or exclude during bulk instance + creation within a region. Policy is defined as a list of key-value + pairs, with the key being the zone name, and value being the applied + policy. Available policies are allow and deny. Default for zones left + unspecified is allow. + + Example: + + gcloud compute instances bulk create --name-pattern=example-### + --count=5 --region=us-east1 + --location-policy=us-east1-b=allow,us-east1-c=deny + + --machine-type=MACHINE_TYPE + Specifies the machine type used for the instances. To get a list of + available machine types, run 'gcloud compute machine-types list'. If + unspecified, the default type is n1-standard-1. + + --max-run-duration=MAX_RUN_DURATION + Limits how long this VM instance can run, specified as a duration + relative to the VM instance's most-recent start time. Format the + duration, MAX_RUN_DURATION, similar to T1h2m3s where you can specify + the number of hours, minutes, and seconds using h, m, and s + respectively. Alternatively, to specify a timestamp, use + --termination-time instead. + + If neither --max-run-duration nor --termination-time is specified + (default), the VM instance runs until prompted by a user action or + system event. If either is specified, the VM instance will be + terminated using the action specified by --instance-termination-action. + For --max-run-duration, the VM instance is terminated whenever the VM's + current runtime reaches MAX_RUN_DURATION; the current runtime is reset + to zero any time the VM instance is stopped and started again. + + --metadata=KEY=VALUE,[KEY=VALUE,...] + Metadata to be made available to the guest operating system running on + the instances. Each metadata entry is a key/value pair separated by an + equals sign. Each metadata key must be unique and have a max of 128 + bytes in length. Each value must have a max of 256 KB in length. + Multiple arguments can be passed to this flag, e.g., --metadata + key-1=value-1,key-2=value-2,key-3=value-3. The combined total size for + all metadata entries is 512 KB. + + In images that have Compute Engine tools installed on them, such as the + official images (https://cloud.google.com/compute/docs/images), the + following metadata keys have special meanings: + + startup-script + Specifies a script that will be executed by the instances once they + start running. For convenience, --metadata-from-file can be used to + pull the value from a file. + + startup-script-url + Same as startup-script except that the script contents are pulled + from a publicly-accessible location on the web. + + For startup scripts on Windows instances, the following metadata keys + have special meanings: windows-startup-script-url, + windows-startup-script-cmd, windows-startup-script-bat, + windows-startup-script-ps1, sysprep-specialize-script-url, + sysprep-specialize-script-cmd, sysprep-specialize-script-bat, and + sysprep-specialize-script-ps1. For more information, see Running + startup scripts (https://cloud.google.com/compute/docs/startupscript). + + --metadata-from-file=KEY=LOCAL_FILE_PATH,[...] + Same as --metadata except that the value for the entry will be read + from a local file. This is useful for values that are too large such as + startup-script contents. + + --min-count=MIN_COUNT + The minimum number of Compute Engine virtual machines that must be + successfully created for the operation to be considered a success. If + the operation successfully creates as many virtual machines as + specified here they will be persisted, otherwise the operation rolls + back and deletes all created virtual machines. If not specified, this + value is equal to --count. + + --min-cpu-platform=PLATFORM + When specified, the VM will be scheduled on host with specified CPU + architecture or a newer one. To list available CPU platforms in given + zone, run: + + $ gcloud alpha compute zones describe ZONE \ + --format="value(availableCpuPlatforms)" + + Default setting is "AUTOMATIC". + + CPU platform selection is available only in selected zones. + + You can find more information on-line: + https://cloud.google.com/compute/docs/instances/specify-min-cpu-platform + + --min-node-cpu=MIN_NODE_CPU + Minimum number of virtual CPUs this instance will consume when running + on a sole-tenant node. + + --network=NETWORK + Specifies the network that the VM instances are a part of. If --subnet + is also specified, subnet must be a subnetwork of the network specified + by this --network flag. If neither is specified, the default network is + used. + + --network-interface=[PROPERTY=VALUE,...] + Adds a network interface to the instance. Mutually exclusive with any + of these flags: --network, --network-tier, --subnet. This flag can be + repeated to specify multiple network interfaces. + + network + Specifies the network that the interface will be part of. If subnet + is also specified it must be subnetwork of this network. If neither + is specified, this defaults to the "default" network. + + network-tier + Specifies the network tier of the interface. NETWORK_TIER must be + one of: PREMIUM, STANDARD. The default value is PREMIUM. + + subnet + Specifies the subnet that the interface will be part of. If network + key is also specified this must be a subnetwork of the specified + network. + + nic-type + Specifies the Network Interface Controller (NIC) type for the + interface. NIC_TYPE must be one of: GVNIC, VIRTIO_NET. + + --network-performance-configs=[PROPERTY=VALUE,...] + Configures network performance settings for the instance. If this flag + is not specified, the instance will be created with its default network + performance configuration. + + total-egress-bandwidth-tier + Total egress bandwidth is the available outbound bandwidth from a + VM, regardless of whether the traffic is going to internal IP or + external IP destinations. The following tier values are allowed: + [DEFAULT,TIER_1] + + --network-tier=NETWORK_TIER + Specifies the network tier that will be used to configure the instance. + NETWORK_TIER must be one of: PREMIUM, STANDARD, FIXED_STANDARD. The + default value is PREMIUM. + + --numa-node-count=NUMA_NODE_COUNT + The number of virtual NUMA nodes for the instance. Valid values are: 0, + 1, 2, 4 or 8. Setting NUMA node count to 0 means using the default + setting. + + --post-key-revocation-action-type=POLICY + Specifies the behavior of the instance when the KMS key of one of its + attached disks is revoked. The default is noop. POLICY must be one of: + + noop + No operation is performed. + shutdown + The instance is shut down when the KMS key of one of its attached + disks is revoked. + + --preemptible + If provided, instances will be preemptible and time-limited. Instances + might be preempted to free up resources for standard VM instances, and + will only be able to run for a limited amount of time. Preemptible + instances can not be restarted and will not migrate. + + --provisioning-model=PROVISIONING_MODEL + Specifies provisioning model, which determines price, obtainability, + and runtime for the VM instance. PROVISIONING_MODEL must be one of: + + SPOT + Spot VMs are spare capacity; Spot VMs are discounted to have much + lower prices than standard VMs but have no guaranteed runtime. Spot + VMs are the new version of preemptible VM instances, except Spot + VMs do not have a 24-hour maximum runtime. + STANDARD + Default. Standard provisioning model for VM instances, which has + user-controlled runtime but no Spot discounts. + + --resource-manager-tags=[KEY=VALUE,...] + Specifies a list of resource manager tags to apply to the instance. + + --resource-policies=[RESOURCE_POLICY,...] + A list of resource policy names to be added to the instance. The + policies must exist in the same region as the instance. + + --restart-on-failure + The instances will be restarted if they are terminated by Compute + Engine. This does not affect terminations performed by the user. + Enabled by default, use --no-restart-on-failure to disable. + + --secure-tags=SECURE_TAG,[SECURE_TAG,...] + Specifies a list of secure tags to apply to the instance. These tags + allow network firewall rules and routes to be applied to specified VM + instances. See gcloud compute network firewall-policies rules create(1) + for more details. + + --shielded-integrity-monitoring + Enables monitoring and attestation of the boot integrity of the + instance. The attestation is performed against the integrity policy + baseline. This baseline is initially derived from the implicitly + trusted boot image when the instance is created. This baseline can be + updated by using gcloud compute instances update + --shielded-learn-integrity-policy. On Shielded VM instances, integrity + monitoring is enabled by default. For information about how to modify + Shielded VM options, see + https://cloud.google.com/compute/docs/instances/modifying-shielded-vm. + For information about monitoring integrity on Shielded VM instances, + see + https://cloud.google.com/compute/docs/instances/integrity-monitoring." + + --shielded-secure-boot + The instance boots with secure boot enabled. On Shielded VM instances, + Secure Boot is not enabled by default. For information about how to + modify Shielded VM options, see + https://cloud.google.com/compute/docs/instances/modifying-shielded-vm. + + --shielded-vtpm + The instance boots with the TPM (Trusted Platform Module) enabled. A + TPM is a hardware module that can be used for different security + operations such as remote attestation, encryption, and sealing of keys. + On Shielded VM instances, vTPM is enabled by default. For information + about how to modify Shielded VM options, see + https://cloud.google.com/compute/docs/instances/modifying-shielded-vm. + + --source-instance-template=SOURCE_INSTANCE_TEMPLATE + The name of the instance template that the instance will be created + from. Users can override fields by specifying other flags. + + --subnet=SUBNET + Specifies the subnet that the VM instances are a part of. If --network + is also specified, subnet must be a subnetwork of the network specified + by the --network flag. + + --tags=TAG,[TAG,...] + Specifies a list of tags to apply to the instance. These tags allow + network firewall rules and routes to be applied to specified VM + instances. See gcloud compute firewall-rules create(1) for more + details. + + To read more about configuring network tags, read this guide: + https://cloud.google.com/vpc/docs/add-remove-network-tags + + To list instances with their respective status and tags, run: + + $ gcloud compute instances list \ + --format='table(name,status,tags.list())' + + To list instances tagged with a specific tag, tag1, run: + + $ gcloud compute instances list --filter='tags:tag1' + + --target-distribution-shape=SHAPE + Specifies whether and how to distribute VMs across multiple zones in a + region or to enforce placement of VMs in a single zone. The default + shape is ANY_SINGLE_ZONE. SHAPE must be one of: + + ANY + Allows creating VMs in multiple zones if one zone cannot + accommodate all the requested VMs. The resulting distribution + shapes can vary. + ANY_SINGLE_ZONE + Enforces VM placement in one allowed zone. Use this to avoid + cross-zone network egress or to reduce network latency. This is the + default value. + BALANCED + Allows distribution of VMs in zones where resources are available + while distributing VMs as evenly as possible across selected zones + to minimize the impact of zonal failures. Recommended for highly + available serving or batch workloads. + + --termination-time=TERMINATION_TIME + Limits how long this VM instance can run, specified as a time. Format + the time, TERMINATION_TIME, as a RFC 3339 timestamp. Alternatively, to + specify a duration, use --max-run-duration instead. + + If neither --termination-time nor --max-run-duration is specified + (default), the VM instance runs until prompted by a user action or + system event. If either is specified, the VM instance will be + terminated using the action specified by --instance-termination-action. + For --termination-time, the VM instance is terminated only during the + specified time. + + --threads-per-core=THREADS_PER_CORE + The number of visible threads per physical core. To disable + simultaneous multithreading (SMT) set this to 1. Valid values are: 1 or + 2. + + For more information about configuring SMT, see: + https://cloud.google.com/compute/docs/instances/configuring-simultaneous-multithreading. + + --visible-core-count=VISIBLE_CORE_COUNT + The number of physical cores to expose to the instance's guest + operating system. The number of virtual CPUs visible to the instance's + guest operating system is this number of cores multiplied by the + instance's count of visible threads per physical core. + + --zone=ZONE + Zone of the queued resource to create. If not specified and the + compute/zone property isn't set, you might be prompted to select a zone + (interactive mode only). + + To avoid prompting when this flag is omitted, you can set the + compute/zone property: + + $ gcloud config set compute/zone ZONE + + A list of zones can be fetched by running: + + $ gcloud compute zones list + + To unset the property, run: + + $ gcloud config unset compute/zone + + Alternatively, the zone can be stored in the environment variable + CLOUDSDK_COMPUTE_ZONE. + + Key resource - The Cloud KMS (Key Management Service) cryptokey that will + be used to protect the disk. The arguments in this group can be used to + specify the attributes of this resource. + + --boot-disk-kms-key=BOOT_DISK_KMS_KEY + ID of the key or fully qualified identifier for the key. To set the + kms-key attribute: + ▸ provide the argument --boot-disk-kms-key on the command line. + + This flag argument must be specified if any of the other arguments in + this group are specified. + + --boot-disk-kms-keyring=BOOT_DISK_KMS_KEYRING + The KMS keyring of the key. To set the kms-keyring attribute: + ▸ provide the argument --boot-disk-kms-key on the command line with + a fully specified name; + ▸ provide the argument --boot-disk-kms-keyring on the command line. + + --boot-disk-kms-location=BOOT_DISK_KMS_LOCATION + The Cloud location for the key. To set the kms-location attribute: + ▸ provide the argument --boot-disk-kms-key on the command line with + a fully specified name; + ▸ provide the argument --boot-disk-kms-location on the command + line. + + --boot-disk-kms-project=BOOT_DISK_KMS_PROJECT + The Cloud project for the key. To set the kms-project attribute: + ▸ provide the argument --boot-disk-kms-key on the command line with + a fully specified name; + ▸ provide the argument --boot-disk-kms-project on the command line; + ▸ set the property core/project. + + Custom machine type extensions. + + --custom-cpu=CUSTOM_CPU + A whole number value specifying the number of cores that are needed + in the custom machine type. + + For some machine types, shared-core values can also be used. For + example, for E2 machine types, you can specify micro, small, or + medium. + + This flag argument must be specified if any of the other arguments in + this group are specified. + + --custom-memory=CUSTOM_MEMORY + A whole number value indicating how much memory is desired in the + custom machine type. A size unit should be provided (eg. 3072MB or + 9GB) - if no units are specified, GB is assumed. + + This flag argument must be specified if any of the other arguments in + this group are specified. + + --custom-extensions + Use the extended custom machine type. + + --custom-vm-type=CUSTOM_VM_TYPE + Specifies VM type. n1 - VMs with CPU platforms Skylake and older, n2 + - VMs with CPU platform Cascade Lake. n2 offers flexible sizing from + 2 to 80 vCPUs, and 1 to 640GBs of memory. It also features a number + of performance enhancements including exposing a more accurate NUMA + topology to the guest OS. The default is n1. + + --image-project=IMAGE_PROJECT + The Google Cloud project against which all image and image family + references will be resolved. It is best practice to define + image-project. A full list of available projects can be generated by + running gcloud projects list. + ◆ If specifying one of our public images, image-project must be + provided. + ◆ If there are several of the same image-family value in multiple + projects, image-project must be specified to clarify the image to be + used. + ◆ If not specified and either image or image-family is provided, the + current default project is used. + + At most one of these can be specified: + + --image=IMAGE + Specifies the boot image for the instances. For each instance, a new + boot disk will be created from the given image. Each boot disk will + have the same name as the instance. To view a list of public images + and projects, run $ gcloud compute images list. It is best practice + to use --image when a specific version of an image is needed. + + When using this option, --boot-disk-device-name and --boot-disk-size + can be used to override the boot disk's device name and size, + respectively. + + --image-family=IMAGE_FAMILY + The image family for the operating system that the boot disk will be + initialized with. Compute Engine offers multiple Linux distributions, + some of which are available as both regular and Shielded VM images. + When a family is specified instead of an image, the latest + non-deprecated image associated with that family is used. It is best + practice to use --image-family when the latest version of an image is + needed. + + By default, debian-11 is assumed for this flag. + + --source-snapshot=SOURCE_SNAPSHOT + The name of the source disk snapshot that the instance boot disk will + be created from. You can provide this as a full URL to the snapshot + or just the snapshot name. For example, the following are valid + values: + + ▸ https://compute.googleapis.com/compute/v1/projects/myproject/global/snapshots/snapshot + ▸ snapshot + + Maintenance Behavior. + + At most one of these can be specified: + + --maintenance-policy=MAINTENANCE_POLICY + (DEPRECATED) Specifies the behavior of the VMs when their host + machines undergo maintenance. The default is MIGRATE. For more + information, see + https://cloud.google.com/compute/docs/instances/host-maintenance-options. + + The --maintenance-policy flag is now deprecated. Please use + --on-host-maintenance instead. MAINTENANCE_POLICY must be one of: + + MIGRATE + The instances should be migrated to a new host. This will + temporarily impact the performance of instances during a + migration event. + TERMINATE + The instances should be terminated. + + --on-host-maintenance=MAINTENANCE_POLICY + Specifies the behavior of the VMs when their host machines undergo + maintenance. The default is MIGRATE. For more information, see + https://cloud.google.com/compute/docs/instances/host-maintenance-options. + MAINTENANCE_POLICY must be one of: + + MIGRATE + The instances should be migrated to a new host. This will + temporarily impact the performance of instances during a + migration event. + TERMINATE + The instances should be terminated. + + At most one of these can be specified: + + --public-dns + Assigns a public DNS name to the instance. + + --no-public-dns + If provided, the instance will not be assigned a public DNS name. + + Specifies the reservation for the instance. + + --reservation=RESERVATION + The name of the reservation, required when + --reservation-affinity=specific. + + --reservation-affinity=RESERVATION_AFFINITY; default="any" + The type of reservation for the instance. RESERVATION_AFFINITY must + be one of: any, none, specific. + + At most one of these can be specified: + + --scopes=[SCOPE,...] + If not provided, the instance will be assigned the default scopes, + described below. However, if neither --scopes nor --no-scopes are + specified and the project has no default service account, then the + instance will be created with no scopes. Note that the level of + access that a service account has is determined by a combination of + access scopes and IAM roles so you must configure both access scopes + and IAM roles for the service account to work properly. + + SCOPE can be either the full URI of the scope or an alias. Default + scopes are assigned to all instances. Available aliases are: + + Alias URI + bigquery https://www.googleapis.com/auth/bigquery + cloud-platform https://www.googleapis.com/auth/cloud-platform + cloud-source-repos https://www.googleapis.com/auth/source.full_control + cloud-source-repos-ro https://www.googleapis.com/auth/source.read_only + compute-ro https://www.googleapis.com/auth/compute.readonly + compute-rw https://www.googleapis.com/auth/compute + datastore https://www.googleapis.com/auth/datastore + default https://www.googleapis.com/auth/devstorage.read_only + https://www.googleapis.com/auth/logging.write + https://www.googleapis.com/auth/monitoring.write + https://www.googleapis.com/auth/pubsub + https://www.googleapis.com/auth/service.management.readonly + https://www.googleapis.com/auth/servicecontrol + https://www.googleapis.com/auth/trace.append + gke-default https://www.googleapis.com/auth/devstorage.read_only + https://www.googleapis.com/auth/logging.write + https://www.googleapis.com/auth/monitoring + https://www.googleapis.com/auth/service.management.readonly + https://www.googleapis.com/auth/servicecontrol + https://www.googleapis.com/auth/trace.append + logging-write https://www.googleapis.com/auth/logging.write + monitoring https://www.googleapis.com/auth/monitoring + monitoring-read https://www.googleapis.com/auth/monitoring.read + monitoring-write https://www.googleapis.com/auth/monitoring.write + pubsub https://www.googleapis.com/auth/pubsub + service-control https://www.googleapis.com/auth/servicecontrol + service-management https://www.googleapis.com/auth/service.management.readonly + sql (deprecated) https://www.googleapis.com/auth/sqlservice + sql-admin https://www.googleapis.com/auth/sqlservice.admin + storage-full https://www.googleapis.com/auth/devstorage.full_control + storage-ro https://www.googleapis.com/auth/devstorage.read_only + storage-rw https://www.googleapis.com/auth/devstorage.read_write + taskqueue https://www.googleapis.com/auth/taskqueue + trace https://www.googleapis.com/auth/trace.append + userinfo-email https://www.googleapis.com/auth/userinfo.email + + DEPRECATION WARNING: https://www.googleapis.com/auth/sqlservice + account scope and sql alias do not provide SQL instance management + capabilities and have been deprecated. Please, use + https://www.googleapis.com/auth/sqlservice.admin or sql-admin to + manage your Google SQL Service instances. + + --no-scopes + Create instance without scopes + + At most one of these can be specified: + + --service-account=SERVICE_ACCOUNT + A service account is an identity attached to the instance. Its access + tokens can be accessed through the instance metadata server and are + used to authenticate applications on the instance. The account can be + set using an email address corresponding to the required service + account. + + If not provided, the instance will use the project's default service + account. + + --no-service-account + Create instance without service account + +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/compute/queued-resources/delete b/gcloud/alpha/compute/queued-resources/delete new file mode 100644 index 000000000..421e477e4 --- /dev/null +++ b/gcloud/alpha/compute/queued-resources/delete @@ -0,0 +1,59 @@ +NAME + gcloud alpha compute queued-resources delete - delete Compute Engine queued + resources + +SYNOPSIS + gcloud alpha compute queued-resources delete NAME [NAME ...] [--zone=ZONE] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) gcloud alpha compute queued-resources delete deletes one or more + Compute Engine queued resources. + +EXAMPLES + To delete Compute Engine queued resources with the names + 'queued-resource-1' and 'queued-resource-2', run: + + $ gcloud alpha compute queued-resources delete queued-resource-1 \ + queued-resource-2 + +POSITIONAL ARGUMENTS + NAME [NAME ...] + Names of the queued resources to delete. + +FLAGS + --zone=ZONE + Zone of the queued resources to delete. If not specified and the + compute/zone property isn't set, you might be prompted to select a zone + (interactive mode only). + + To avoid prompting when this flag is omitted, you can set the + compute/zone property: + + $ gcloud config set compute/zone ZONE + + A list of zones can be fetched by running: + + $ gcloud compute zones list + + To unset the property, run: + + $ gcloud config unset compute/zone + + Alternatively, the zone can be stored in the environment variable + CLOUDSDK_COMPUTE_ZONE. + +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/compute/queued-resources/describe b/gcloud/alpha/compute/queued-resources/describe new file mode 100644 index 000000000..4d36aada9 --- /dev/null +++ b/gcloud/alpha/compute/queued-resources/describe @@ -0,0 +1,58 @@ +NAME + gcloud alpha compute queued-resources describe - describe a Compute Engine + queued resource + +SYNOPSIS + gcloud alpha compute queued-resources describe NAME [--zone=ZONE] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) gcloud alpha compute queued-resources describe describes a Compute + Engine queued resource. + +EXAMPLES + To describe a Compute Engine queued resource with the name + 'queued-resource-1', run: + + $ gcloud alpha compute queued-resources describe queued-resource-1 + +POSITIONAL ARGUMENTS + NAME + Name of the queued resource to describe. + +FLAGS + --zone=ZONE + Zone of the queued resource to describe. If not specified and the + compute/zone property isn't set, you might be prompted to select a zone + (interactive mode only). + + To avoid prompting when this flag is omitted, you can set the + compute/zone property: + + $ gcloud config set compute/zone ZONE + + A list of zones can be fetched by running: + + $ gcloud compute zones list + + To unset the property, run: + + $ gcloud config unset compute/zone + + Alternatively, the zone can be stored in the environment variable + CLOUDSDK_COMPUTE_ZONE. + +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/compute/queued-resources/help b/gcloud/alpha/compute/queued-resources/help new file mode 100644 index 000000000..aab7d75a0 --- /dev/null +++ b/gcloud/alpha/compute/queued-resources/help @@ -0,0 +1,38 @@ +NAME + gcloud alpha compute queued-resources - manage queued resources + +SYNOPSIS + gcloud alpha compute queued-resources COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Manage queued resources. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + cancel + (ALPHA) Cancel Compute Engine queued resources. + + create + (ALPHA) Create a Compute Engine queued resource. + + delete + (ALPHA) Delete Compute Engine queued resources. + + describe + (ALPHA) Describe a Compute Engine queued resource. + + list + (ALPHA) List Compute Engine queued resources. + +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/compute/queued-resources/list b/gcloud/alpha/compute/queued-resources/list new file mode 100644 index 000000000..69af63178 --- /dev/null +++ b/gcloud/alpha/compute/queued-resources/list @@ -0,0 +1,76 @@ +NAME + gcloud alpha compute queued-resources list - list Compute Engine queued + resources + +SYNOPSIS + gcloud alpha compute queued-resources list --zones=ZONE,[ZONE,...] + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) gcloud alpha compute queued-resources list displays all Compute + Engine queued resources in a project in given zones. + +EXAMPLES + To list all queued resources in a project in table form in specified zones, + run: + + $ gcloud alpha compute queued-resources list \ + --zones=us-central1-a,us-central1-b + + To list the URIs of all queued resources in a project in specified zones, + run: + + $ gcloud alpha compute queued-resources list \ + --zones=us-central1-a,us-central1-b --uri + +REQUIRED FLAGS + --zones=ZONE,[ZONE,...] + Only resources from the given zones are queried. + +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. + + --uri + Print a list of resource URIs instead of the default output, and change + the command output to a list of URIs. If this flag is used with + --format, the formatting is applied on this URI list. To display URIs + alongside other keys instead, use the uri() transform. + +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/compute/tpus/tpu-vm/create b/gcloud/alpha/compute/tpus/tpu-vm/create index 6258081d5..709bac182 100644 --- a/gcloud/alpha/compute/tpus/tpu-vm/create +++ b/gcloud/alpha/compute/tpus/tpu-vm/create @@ -193,7 +193,7 @@ OPTIONAL FLAGS in this group are specified. --type=TYPE - Type of TPU. TYPE must be one of: type-unspecified, v2, v3, v4. + Type of TPU. TYPE must be one of: v2, v3, v4. This flag argument must be specified if any of the other arguments in this group are specified. diff --git a/gcloud/alpha/database-migration/migration-jobs/create b/gcloud/alpha/database-migration/migration-jobs/create index b49278f3f..009323122 100644 --- a/gcloud/alpha/database-migration/migration-jobs/create +++ b/gcloud/alpha/database-migration/migration-jobs/create @@ -70,7 +70,7 @@ POSITIONAL ARGUMENTS REQUIRED FLAGS Connection profile resource - ID of the destination connection profile, - representing thedestination database. This represents a Cloud resource. + representing the destination database. 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 --destination on the command line with a fully diff --git a/gcloud/alpha/database-migration/migration-jobs/update b/gcloud/alpha/database-migration/migration-jobs/update index 405832fc0..bea588d89 100644 --- a/gcloud/alpha/database-migration/migration-jobs/update +++ b/gcloud/alpha/database-migration/migration-jobs/update @@ -59,7 +59,7 @@ POSITIONAL ARGUMENTS FLAGS Connection profile resource - ID of the destination connection profile, - representing thedestination database. This represents a Cloud resource. + representing the destination database. 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 --destination on the command line with a fully diff --git a/gcloud/alpha/deploy/releases/create b/gcloud/alpha/deploy/releases/create index 99716afe9..ad3f97951 100644 --- a/gcloud/alpha/deploy/releases/create +++ b/gcloud/alpha/deploy/releases/create @@ -12,6 +12,7 @@ SYNOPSIS [--build-artifacts=BUILD_ARTIFACTS | --images=[NAME=TAG,...]] [--disable-initial-rollout | --enable-initial-rollout] [--from-k8s-manifest=FROM_K8S_MANIFEST + | --from-run-manifest=FROM_RUN_MANIFEST | --skaffold-file=SKAFFOLD_FILE --source=SOURCE; default="."] [GCLOUD_WIDE_FLAG ...] @@ -168,6 +169,13 @@ FLAGS Storage source staging directory (see --gcs-source-staging-dir flag) after the release is complete. + --from-run-manifest=FROM_RUN_MANIFEST + The path to a Cloud Run manifest, which Cloud Deploy will use to + generate a skaffold.yaml file for you (for example, + foo/bar/service.yaml). The generated Skaffold file will be available + in the Google Cloud Storage source staging directory (see + --gcs-source-staging-dir flag) after the release is complete. + --skaffold-file=SKAFFOLD_FILE Path of the skaffold file absolute or relative to the source directory. diff --git a/gcloud/alpha/deploy/targets/help b/gcloud/alpha/deploy/targets/help index 9e307069f..cdb604729 100644 --- a/gcloud/alpha/deploy/targets/help +++ b/gcloud/alpha/deploy/targets/help @@ -36,7 +36,7 @@ COMMANDS (ALPHA) List Cloud Deploy targets. redeploy - (ALPHA) Redeploy the last rollout to a target. + (ALPHA) Redeploy the last release to a target. remove-iam-policy-binding (ALPHA) Remove an IAM policy binding for a Cloud Deploy target. diff --git a/gcloud/alpha/deploy/targets/redeploy b/gcloud/alpha/deploy/targets/redeploy index 8a036bf7f..2b0bb36e9 100644 --- a/gcloud/alpha/deploy/targets/redeploy +++ b/gcloud/alpha/deploy/targets/redeploy @@ -1,5 +1,5 @@ NAME - gcloud alpha deploy targets redeploy - redeploy the last rollout to a + gcloud alpha deploy targets redeploy - redeploy the last release to a target SYNOPSIS diff --git a/gcloud/alpha/dns/managed-zones/create b/gcloud/alpha/dns/managed-zones/create index f64a3d5ed..5912eaad3 100644 --- a/gcloud/alpha/dns/managed-zones/create +++ b/gcloud/alpha/dns/managed-zones/create @@ -31,11 +31,11 @@ EXAMPLES --description="Signed Zone" --dns-name=myzone.example \ --dnssec-state=on - To create a zonal managed-zone scoped to a GKE Cluster in us-east1-a, run: + To create a zonal managed-zone scoped to a GKE Cluster in us-east1-a, run: $ gcloud alpha dns managed-zones create my-zonal-zone \ --description="Signed Zone" --dns-name=cluster.local \ - --visibiilty=private --gkeclusters=cluster1 \ + --visibility=private --gkeclusters=cluster1 \ --location=us-east1-a POSITIONAL ARGUMENTS @@ -91,8 +91,9 @@ OPTIONAL FLAGS numbers. --location=LOCATION - Specifies the desired service location the request is sent to. Default - to Cloud DNS global service. + Specifies the desired service location the request is sent to. Defaults + to Cloud DNS global service. Use --location=global if you want to + target the global service. --[no-]log-dns-queries Specifies whether to enable query logging. Defaults to False. Use diff --git a/gcloud/alpha/dns/managed-zones/delete b/gcloud/alpha/dns/managed-zones/delete index d800595ba..0803cdf5d 100644 --- a/gcloud/alpha/dns/managed-zones/delete +++ b/gcloud/alpha/dns/managed-zones/delete @@ -25,8 +25,9 @@ POSITIONAL ARGUMENTS FLAGS --location=LOCATION - Specifies the desired service location the request is sent to. Default - to Cloud DNS global service. + Specifies the desired service location the request is sent to. Defaults + to Cloud DNS global service. Use --location=global if you want to + target the global service. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/alpha/dns/managed-zones/describe b/gcloud/alpha/dns/managed-zones/describe index b7de79062..7dff77e89 100644 --- a/gcloud/alpha/dns/managed-zones/describe +++ b/gcloud/alpha/dns/managed-zones/describe @@ -14,7 +14,8 @@ EXAMPLES $ gcloud alpha dns managed-zones describe my-zone - To display the details of a zonal managed-zone in us-east1-c, run: + To display the details of a zonal managed-zone in Zonal Cloud DNS service + in us-east1-c, run: $ gcloud alpha dns managed-zones describe my-zone \ --location=us-east1-c @@ -38,8 +39,9 @@ POSITIONAL ARGUMENTS FLAGS --location=LOCATION - Specifies the desired service location the request is sent to. Default - to Cloud DNS global service. + Specifies the desired service location the request is sent to. Defaults + to Cloud DNS global service. Use --location=global if you want to + target the global service. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/alpha/dns/managed-zones/list b/gcloud/alpha/dns/managed-zones/list index b6a2d42f6..e403e8934 100644 --- a/gcloud/alpha/dns/managed-zones/list +++ b/gcloud/alpha/dns/managed-zones/list @@ -26,8 +26,9 @@ EXAMPLES FLAGS --location=LOCATION - Specifies the desired service location the request is sent to. Default - to Cloud DNS global service. + Specifies the desired service location the request is sent to. Defaults + to Cloud DNS global service. Use --location=global if you want to + target the global service. LIST COMMAND FLAGS --filter=EXPRESSION diff --git a/gcloud/alpha/dns/managed-zones/update b/gcloud/alpha/dns/managed-zones/update index eb62e0acb..62cd79fc2 100644 --- a/gcloud/alpha/dns/managed-zones/update +++ b/gcloud/alpha/dns/managed-zones/update @@ -26,6 +26,11 @@ EXAMPLES $ gcloud alpha dns managed-zones update my-zone \ --description="Hello, world!" + To change the description of a zonal managed-zone in us-east1-a, run: + + $ gcloud alpha dns managed-zones update my-zone \ + --description="Hello, world!" --location=us-east1-a + POSITIONAL ARGUMENTS Zone resource - The name of the managed-zone to be updated. This represents a Cloud resource. (NOTE) Some attributes are not given @@ -84,8 +89,9 @@ FLAGS Length of the key-signing key in bits. Requires DNSSEC enabled. --location=LOCATION - Specifies the desired service location the request is sent to. Default - to Cloud DNS global service. + Specifies the desired service location the request is sent to. Defaults + to Cloud DNS global service. Use --location=global if you want to + target the global service. --[no-]log-dns-queries Specifies whether to enable query logging. Defaults to False. Use diff --git a/gcloud/alpha/dns/record-sets/create b/gcloud/alpha/dns/record-sets/create index 1aa8992a0..eae980bc9 100644 --- a/gcloud/alpha/dns/record-sets/create +++ b/gcloud/alpha/dns/record-sets/create @@ -165,8 +165,9 @@ REQUIRED FLAGS OPTIONAL FLAGS --location=LOCATION - Specifies the desired service location the request is sent to. Default - to Cloud DNS global service. + Specifies the desired service location the request is sent to. Defaults + to Cloud DNS global service. Use --location=global if you want to + target the global service. --ttl=TTL TTL (time to live) for the record-set. diff --git a/gcloud/alpha/dns/record-sets/delete b/gcloud/alpha/dns/record-sets/delete index dfd1d3a14..1a0d20ae5 100644 --- a/gcloud/alpha/dns/record-sets/delete +++ b/gcloud/alpha/dns/record-sets/delete @@ -29,8 +29,9 @@ REQUIRED FLAGS OPTIONAL FLAGS --location=LOCATION - Specifies the desired service location the request is sent to. Default - to Cloud DNS global service. + Specifies the desired service location the request is sent to. Defaults + to Cloud DNS global service. Use --location=global if you want to + target the global service. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/alpha/dns/record-sets/describe b/gcloud/alpha/dns/record-sets/describe index dbd879cf1..efff288d3 100644 --- a/gcloud/alpha/dns/record-sets/describe +++ b/gcloud/alpha/dns/record-sets/describe @@ -30,8 +30,9 @@ REQUIRED FLAGS OPTIONAL FLAGS --location=LOCATION - Specifies the desired service location the request is sent to. Default - to Cloud DNS global service. + Specifies the desired service location the request is sent to. Defaults + to Cloud DNS global service. Use --location=global if you want to + target the global service. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/alpha/dns/record-sets/export b/gcloud/alpha/dns/record-sets/export index b9eb5c064..74429b19b 100644 --- a/gcloud/alpha/dns/record-sets/export +++ b/gcloud/alpha/dns/record-sets/export @@ -36,8 +36,9 @@ REQUIRED FLAGS OPTIONAL FLAGS --location=LOCATION - Specifies the desired service location the request is sent to. Default - to Cloud DNS global service. + Specifies the desired service location the request is sent to. Defaults + to Cloud DNS global service. Use --location=global if you want to + target the global service. --zone-file-format Indicates that records-file should be in the zone file format. When diff --git a/gcloud/alpha/dns/record-sets/import b/gcloud/alpha/dns/record-sets/import index f66ee2f76..8bb4cfb97 100644 --- a/gcloud/alpha/dns/record-sets/import +++ b/gcloud/alpha/dns/record-sets/import @@ -50,8 +50,9 @@ OPTIONAL FLAGS importing the record-sets in the records-file. --location=LOCATION - Specifies the desired service location the request is sent to. Default - to Cloud DNS global service. + Specifies the desired service location the request is sent to. Defaults + to Cloud DNS global service. Use --location=global if you want to + target the global service. --replace-origin-ns Indicates that NS records for the origin of a zone should be imported diff --git a/gcloud/alpha/dns/record-sets/list b/gcloud/alpha/dns/record-sets/list index 6209d47fd..9769c0b24 100644 --- a/gcloud/alpha/dns/record-sets/list +++ b/gcloud/alpha/dns/record-sets/list @@ -37,8 +37,9 @@ REQUIRED FLAGS FLAGS --location=LOCATION - Specifies the desired service location the request is sent to. Default - to Cloud DNS global service. + Specifies the desired service location the request is sent to. Defaults + to Cloud DNS global service. Use --location=global if you want to + target the global service. --name=NAME Only list record-sets with this exact domain name. diff --git a/gcloud/alpha/dns/record-sets/update b/gcloud/alpha/dns/record-sets/update index 52eb6a2ea..b274239b2 100644 --- a/gcloud/alpha/dns/record-sets/update +++ b/gcloud/alpha/dns/record-sets/update @@ -26,8 +26,8 @@ EXAMPLES --rrdatas=1.2.3.4,9.8.7.6 --type=A --ttl=60 --zone=my_zone To update a record-set with dnsName foo.bar.com., record type A to have - rrdata [1.2.3.4, 9.8.7.6] and ttl 60 in my_zone that locates in us-east1-a, - run: + rrdata [1.2.3.4, 9.8.7.6] and ttl 60 in my_zone that is located in + us-east1-a, run: $ gcloud alpha dns record-sets update foo.bar.com. \ --rrdatas=1.2.3.4,9.8.7.6 --type=A --ttl=60 --zone=my_zone \ @@ -132,8 +132,9 @@ REQUIRED FLAGS OPTIONAL FLAGS --location=LOCATION - Specifies the desired service location the request is sent to. Default - to Cloud DNS global service. + Specifies the desired service location the request is sent to. Defaults + to Cloud DNS global service. Use --location=global if you want to + target the global service. --ttl=TTL TTL (time to live) for the record-set. diff --git a/gcloud/alpha/dns/response-policies/create b/gcloud/alpha/dns/response-policies/create index b4f3d445a..51448acfc 100644 --- a/gcloud/alpha/dns/response-policies/create +++ b/gcloud/alpha/dns/response-policies/create @@ -54,8 +54,9 @@ OPTIONAL FLAGS response policy. --location=LOCATION - Specifies the desired service location the request is sent to. Default - to Cloud DNS global service. + Specifies the desired service location the request is sent to. Defaults + to Cloud DNS global service. Use --location=global if you want to + target the global service. --networks=[NETWORKS,...] The comma-separated list of network names to associate with the diff --git a/gcloud/alpha/dns/response-policies/delete b/gcloud/alpha/dns/response-policies/delete index 9c3f78a37..52dc6ed4b 100644 --- a/gcloud/alpha/dns/response-policies/delete +++ b/gcloud/alpha/dns/response-policies/delete @@ -32,8 +32,9 @@ POSITIONAL ARGUMENTS FLAGS --location=LOCATION - Specifies the desired service location the request is sent to. Default - to Cloud DNS global service. + Specifies the desired service location the request is sent to. Defaults + to Cloud DNS global service. Use --location=global if you want to + target the global service. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/alpha/dns/response-policies/describe b/gcloud/alpha/dns/response-policies/describe index 69f497a15..d103b9c9a 100644 --- a/gcloud/alpha/dns/response-policies/describe +++ b/gcloud/alpha/dns/response-policies/describe @@ -32,8 +32,9 @@ POSITIONAL ARGUMENTS FLAGS --location=LOCATION - Specifies the desired service location the request is sent to. Default - to Cloud DNS global service. + Specifies the desired service location the request is sent to. Defaults + to Cloud DNS global service. Use --location=global if you want to + target the global service. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/alpha/dns/response-policies/list b/gcloud/alpha/dns/response-policies/list index aab7eb0dd..db56e58d8 100644 --- a/gcloud/alpha/dns/response-policies/list +++ b/gcloud/alpha/dns/response-policies/list @@ -14,8 +14,9 @@ EXAMPLES FLAGS --location=LOCATION - Specifies the desired service location the request is sent to. Default - to Cloud DNS global service. + Specifies the desired service location the request is sent to. Defaults + to Cloud DNS global service. Use --location=global if you want to + target the global service. LIST COMMAND FLAGS --filter=EXPRESSION diff --git a/gcloud/alpha/dns/response-policies/rules/create b/gcloud/alpha/dns/response-policies/rules/create index aa59900bc..3e2a01308 100644 --- a/gcloud/alpha/dns/response-policies/rules/create +++ b/gcloud/alpha/dns/response-policies/rules/create @@ -91,8 +91,9 @@ OPTIONAL FLAGS The list of datas for this record, split by "|". --location=LOCATION - Specifies the desired service location the request is sent to. Default - to Cloud DNS global service. + Specifies the desired service location the request is sent to. Defaults + to Cloud DNS global service. Use --location=global if you want to + target the global service. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/alpha/dns/response-policies/rules/delete b/gcloud/alpha/dns/response-policies/rules/delete index 264fe5422..f78ecf4c9 100644 --- a/gcloud/alpha/dns/response-policies/rules/delete +++ b/gcloud/alpha/dns/response-policies/rules/delete @@ -41,8 +41,9 @@ POSITIONAL ARGUMENTS FLAGS --location=LOCATION - Specifies the desired service location the request is sent to. Default - to Cloud DNS global service. + Specifies the desired service location the request is sent to. Defaults + to Cloud DNS global service. Use --location=global if you want to + target the global service. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/alpha/dns/response-policies/rules/describe b/gcloud/alpha/dns/response-policies/rules/describe index 77188c685..5031cfa4a 100644 --- a/gcloud/alpha/dns/response-policies/rules/describe +++ b/gcloud/alpha/dns/response-policies/rules/describe @@ -41,8 +41,9 @@ POSITIONAL ARGUMENTS FLAGS --location=LOCATION - Specifies the desired service location the request is sent to. Default - to Cloud DNS global service. + Specifies the desired service location the request is sent to. Defaults + to Cloud DNS global service. Use --location=global if you want to + target the global service. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/alpha/dns/response-policies/rules/list b/gcloud/alpha/dns/response-policies/rules/list index d09d9b1f6..9561e8183 100644 --- a/gcloud/alpha/dns/response-policies/rules/list +++ b/gcloud/alpha/dns/response-policies/rules/list @@ -30,8 +30,9 @@ POSITIONAL ARGUMENTS FLAGS --location=LOCATION - Specifies the desired service location the request is sent to. Default - to Cloud DNS global service. + Specifies the desired service location the request is sent to. Defaults + to Cloud DNS global service. Use --location=global if you want to + target the global service. LIST COMMAND FLAGS --filter=EXPRESSION diff --git a/gcloud/alpha/dns/response-policies/rules/update b/gcloud/alpha/dns/response-policies/rules/update index 3b2f56c30..5d18910c0 100644 --- a/gcloud/alpha/dns/response-policies/rules/update +++ b/gcloud/alpha/dns/response-policies/rules/update @@ -89,8 +89,9 @@ FLAGS The list of datas for this record, split by "|". --location=LOCATION - Specifies the desired service location the request is sent to. Default - to Cloud DNS global service. + Specifies the desired service location the request is sent to. Defaults + to Cloud DNS global service. Use --location=global if you want to + target the global service. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/alpha/dns/response-policies/update b/gcloud/alpha/dns/response-policies/update index 56a45b2b6..17307ecde 100644 --- a/gcloud/alpha/dns/response-policies/update +++ b/gcloud/alpha/dns/response-policies/update @@ -54,8 +54,9 @@ FLAGS response policy. --location=LOCATION - Specifies the desired service location the request is sent to. Default - to Cloud DNS global service. + Specifies the desired service location the request is sent to. Defaults + to Cloud DNS global service. Use --location=global if you want to + target the global service. --networks=[NETWORKS,...] The comma-separated list of network names to associate with the diff --git a/gcloud/alpha/edge-cloud/networking/interconnects/attachments/dedicated/create b/gcloud/alpha/edge-cloud/networking/interconnects/attachments/dedicated/create index 385cca6f0..e5bb05cb8 100644 --- a/gcloud/alpha/edge-cloud/networking/interconnects/attachments/dedicated/create +++ b/gcloud/alpha/edge-cloud/networking/interconnects/attachments/dedicated/create @@ -6,9 +6,9 @@ NAME SYNOPSIS gcloud alpha edge-cloud networking interconnects attachments dedicated create (INTERCONNECT_ATTACHMENT : --location=LOCATION --zone=ZONE) - --interconnect=INTERCONNECT --router=ROUTER --vlan-id=VLAN_ID [--async] - [--description=DESCRIPTION] [--labels=[KEY=VALUE,...]] [--mtu=MTU] - [GCLOUD_WIDE_FLAG ...] + --interconnect=INTERCONNECT --router=ROUTER [--async] + [--description=DESCRIPTION] [--labels=[KEY=VALUE,...]] + [--mtu=MTU; default=1500] [--vlan-id=VLAN_ID] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Create a new dedicated Distributed Cloud Edge Network interconnect @@ -66,9 +66,6 @@ REQUIRED FLAGS --router=ROUTER The router to use for dynamic routing. - --vlan-id=VLAN_ID - The ID of the vlan to tag the subnetwork. - OPTIONAL FLAGS --async Return immediately, without waiting for the operation in progress to @@ -85,11 +82,14 @@ OPTIONAL FLAGS contain only hyphens (-), underscores (_), lowercase characters, and numbers. - --mtu=MTU + --mtu=MTU; default=1500 Maximum transmission unit (MTU) is the size of the largest IP packet that can be transmitted on this attachment. Default value is 1500 bytes, and the valid values are 1500 and 9000. + --vlan-id=VLAN_ID + The ID of the vlan to tag the subnetwork. Default value is 0. + 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/edge-cloud/networking/routers/create b/gcloud/alpha/edge-cloud/networking/routers/create index 6cbeec30f..28e14eb3d 100644 --- a/gcloud/alpha/edge-cloud/networking/routers/create +++ b/gcloud/alpha/edge-cloud/networking/routers/create @@ -17,8 +17,7 @@ EXAMPLES $ gcloud alpha edge-cloud networking routers create my-router \ --network=my-network --location=us-central1 \ - --zone=us-central1-edge-den1 --asn=65555 \ - --keepalive-interval-in-seconds=20 + --zone=us-central1-edge-den1 --asn=65555 POSITIONAL ARGUMENTS Router resource - Distributed Cloud Edge Network router to create. The diff --git a/gcloud/alpha/edge-cloud/networking/routers/help b/gcloud/alpha/edge-cloud/networking/routers/help index 436f3a39d..61e519df7 100644 --- a/gcloud/alpha/edge-cloud/networking/routers/help +++ b/gcloud/alpha/edge-cloud/networking/routers/help @@ -43,8 +43,7 @@ COMMANDS Network router. remove-interface - (ALPHA) remove a list of interfaces on a Distributed Cloud Edge Network - router. + (ALPHA) remove an interface on a Distributed Cloud Edge Network router. update (ALPHA) Update a Distributed Cloud Edge Network router. diff --git a/gcloud/alpha/edge-cloud/networking/routers/remove-interface b/gcloud/alpha/edge-cloud/networking/routers/remove-interface index 9b6ee9d4a..22f7b0b8b 100644 --- a/gcloud/alpha/edge-cloud/networking/routers/remove-interface +++ b/gcloud/alpha/edge-cloud/networking/routers/remove-interface @@ -1,27 +1,28 @@ NAME - gcloud alpha edge-cloud networking routers remove-interface - remove a list - of interfaces on a Distributed Cloud Edge Network router + gcloud alpha edge-cloud networking routers remove-interface - remove an + interface on a Distributed Cloud Edge Network router SYNOPSIS gcloud alpha edge-cloud networking routers remove-interface (ROUTER : --location=LOCATION --zone=ZONE) - --interface-names=[INTERFACE_NAME,...] [--async] [GCLOUD_WIDE_FLAG ...] + (--interface-name=INTERFACE_NAME + | --interface-names=[INTERFACE_NAME,...]) [--async] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) Remove a list of interfaces on a Distributed Cloud Edge Network - router. + (ALPHA) Remove an interface on a Distributed Cloud Edge Network router. EXAMPLES - To remove a list of interfaces contains 'my-int-r1' on Distributed Cloud - Edge Network router 'my-router' in edge zone 'us-central1-edge-den1' , run: + To remove the interface 'my-int-r1' on Distributed Cloud Edge Network + router 'my-router' in edge zone 'us-central1-edge-den1' , run: $ gcloud alpha edge-cloud networking routers remove-interface \ - my-router --interface-names=my-int-r1 --location=us-central1 \ + my-router --interface-name=my-int-r1 --location=us-central1 \ --zone=us-central1-edge-den1 POSITIONAL ARGUMENTS - Router resource - The router from which we remove a list of interfaces. - The arguments in this group can be used to specify the attributes of this + Router resource - The router from which we remove an interface. 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 router on the command line with a fully @@ -52,8 +53,13 @@ POSITIONAL ARGUMENTS ▸ provide the argument --zone on the command line. REQUIRED FLAGS - --interface-names=[INTERFACE_NAME,...] - The list of names for interfaces being removed. + Exactly one of these must be specified: + + --interface-name=INTERFACE_NAME + The name of the interface being removed. + + --interface-names=[INTERFACE_NAME,...] + The list of names for interfaces being removed. OPTIONAL FLAGS --async diff --git a/gcloud/alpha/network-connectivity/internal-ranges/create b/gcloud/alpha/network-connectivity/internal-ranges/create index ee86b8258..0a05621d8 100644 --- a/gcloud/alpha/network-connectivity/internal-ranges/create +++ b/gcloud/alpha/network-connectivity/internal-ranges/create @@ -8,7 +8,7 @@ SYNOPSIS (--ip-cidr-range=IP_CIDR_RANGE | [--prefix-length=PREFIX_LENGTH : --target-cidr-range=[TARGET_CIDR_RANGE,...]]) [--async] [--description=DESCRIPTION] [--labels=KEY=VALUE] - [--peering=PEERING; default="for-self"] + [--overlaps=[OVERLAPS,...]] [--peering=PEERING; default="for-self"] [--usage=USAGE; default="for-vpc"] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -101,6 +101,14 @@ OPTIONAL FLAGS --labels=KEY=VALUE List of label KEY=VALUE pairs to add. + --overlaps=[OVERLAPS,...] + Overlap specifications for the range being created. OVERLAPS must be + (currently only one value is supported): + + overlap-route-range + Allows for creation or existence of routes that have a more + specific destination than the created range. + --peering=PEERING; default="for-self" The type of peering set for the internal range. PEERING must be one of: diff --git a/gcloud/alpha/run/deploy b/gcloud/alpha/run/deploy index ed100869e..12d742ea8 100644 --- a/gcloud/alpha/run/deploy +++ b/gcloud/alpha/run/deploy @@ -32,8 +32,9 @@ SYNOPSIS | --remove-cloudsql-instances=[CLOUDSQL-INSTANCES,...] | --set-cloudsql-instances=[CLOUDSQL-INSTANCES,...] --binary-authorization=POLICY - | --clear-binary-authorization --clear-key - | --key=KEY --clear-post-key-revocation-action-type + | --clear-binary-authorization --clear-encryption-key-shutdown-hours + | --encryption-key-shutdown-hours=ENCRYPTION_KEY_SHUTDOWN_HOURS + --clear-key | --key=KEY --clear-post-key-revocation-action-type | --post-key-revocation-action-type=POST_KEY_REVOCATION_ACTION_TYPE] [--region=REGION | --cluster=CLUSTER --cluster-location=CLUSTER_LOCATION @@ -454,6 +455,15 @@ FLAGS --clear-binary-authorization Remove any previously set Binary Authorization policy. + At most one of these can be specified: + + --clear-encryption-key-shutdown-hours + Remove any previously set CMEK key shutdown hours setting. + + --encryption-key-shutdown-hours=ENCRYPTION_KEY_SHUTDOWN_HOURS + The number of hours to wait before an automatic shutdown server + after CMEK key revocation is detected. + At most one of these can be specified: --clear-key diff --git a/gcloud/alpha/run/services/update b/gcloud/alpha/run/services/update index c21014f53..cf045b92d 100644 --- a/gcloud/alpha/run/services/update +++ b/gcloud/alpha/run/services/update @@ -20,8 +20,9 @@ SYNOPSIS | --remove-cloudsql-instances=[CLOUDSQL-INSTANCES,...] | --set-cloudsql-instances=[CLOUDSQL-INSTANCES,...] --binary-authorization=POLICY - | --clear-binary-authorization --clear-key - | --key=KEY --clear-post-key-revocation-action-type + | --clear-binary-authorization --clear-encryption-key-shutdown-hours + | --encryption-key-shutdown-hours=ENCRYPTION_KEY_SHUTDOWN_HOURS + --clear-key | --key=KEY --clear-post-key-revocation-action-type | --post-key-revocation-action-type=POST_KEY_REVOCATION_ACTION_TYPE] [--clear-env-vars | --env-vars-file=FILE_PATH | --set-env-vars=[KEY=VALUE,...] @@ -286,6 +287,15 @@ FLAGS --clear-binary-authorization Remove any previously set Binary Authorization policy. + At most one of these can be specified: + + --clear-encryption-key-shutdown-hours + Remove any previously set CMEK key shutdown hours setting. + + --encryption-key-shutdown-hours=ENCRYPTION_KEY_SHUTDOWN_HOURS + The number of hours to wait before an automatic shutdown server + after CMEK key revocation is detected. + At most one of these can be specified: --clear-key diff --git a/gcloud/alpha/spanner/databases/create b/gcloud/alpha/spanner/databases/create index 9d26fac22..f90d720f8 100644 --- a/gcloud/alpha/spanner/databases/create +++ b/gcloud/alpha/spanner/databases/create @@ -80,7 +80,8 @@ FLAGS is an error in any statement, the database is not created. This option is not supported for the PostgreSQL dialect. Full DDL specification is at https://cloud.google.com/spanner/docs/data-definition-language. If - --ddl_file is set, --ddl is ignored. + --ddl_file is set, --ddl is ignored. One line comments starting with -- + are ignored. Key resource - Cloud KMS key to be used to create the Cloud Spanner database. The arguments in this group can be used to specify the diff --git a/gcloud/alpha/spanner/databases/ddl/update b/gcloud/alpha/spanner/databases/ddl/update index ae7dec413..4a32978b2 100644 --- a/gcloud/alpha/spanner/databases/ddl/update +++ b/gcloud/alpha/spanner/databases/ddl/update @@ -58,7 +58,8 @@ FLAGS Path of a file containing semi-colon separated DDL (data definition language) statements to run inside the database. If a statement fails, all subsequent statements in the batch are automatically cancelled. If - --ddl_file is set, --ddl is ignored. + --ddl_file is set, --ddl is ignored. One line comments starting with -- + are ignored. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/alpha/spanner/samples/run b/gcloud/alpha/spanner/samples/run index 5a128f4a8..76d77338f 100644 --- a/gcloud/alpha/spanner/samples/run +++ b/gcloud/alpha/spanner/samples/run @@ -4,7 +4,8 @@ NAME SYNOPSIS gcloud alpha spanner samples run APPNAME --instance-id=INSTANCE_ID [--no-cleanup] [--database-id=DATABASE_ID] - [--duration=DURATION; default="1h"] [GCLOUD_WIDE_FLAG ...] + [--duration=DURATION; default="1h"] [--skip-init] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Each Cloud Spanner sample application includes a backend gRPC @@ -44,6 +45,9 @@ OPTIONAL FLAGS Duration of time allowed to run the sample app before stopping the service. + --skip-init + Use an existing database instead of creating a new one. + 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/beta/ai/indexes/help b/gcloud/beta/ai/indexes/help index b3c8035e9..3d397739d 100644 --- a/gcloud/beta/ai/indexes/help +++ b/gcloud/beta/ai/indexes/help @@ -27,9 +27,15 @@ COMMANDS list (BETA) Lists the indexes of the given project and region. + remove-datapoints + (BETA) Remove data points from the specified index. + update (BETA) Update an Vertex AI index. + upsert-datapoints + (BETA) Upsert data points into the specified index. + NOTES This command is currently in beta and might change without notice. These variants are also available: diff --git a/gcloud/beta/ai/indexes/remove-datapoints b/gcloud/beta/ai/indexes/remove-datapoints new file mode 100644 index 000000000..dd8c62a74 --- /dev/null +++ b/gcloud/beta/ai/indexes/remove-datapoints @@ -0,0 +1,74 @@ +NAME + gcloud beta ai indexes remove-datapoints - remove data points from the + specified index + +SYNOPSIS + gcloud beta ai indexes remove-datapoints (INDEX : --region=REGION) + (--datapoint-ids=[DATAPOINT_IDS,...] + | --datapoints-from-file=DATAPOINTS_FROM_FILE) [GCLOUD_WIDE_FLAG ...] + +EXAMPLES + To remove datapoints from an index '123', run: + + $ gcloud beta ai indexes remove-datapoints 123 \ + --datapoint-ids=example1,example2 --project=example \ + --region=us-central1 + + Or put datapoint ids in a json file and run: + + $ gcloud beta ai indexes remove-datapoints 123 \ + --datapoints-from-file=example.json --project=example \ + --region=us-central1 + +POSITIONAL ARGUMENTS + Index resource - Index to remove data points from. 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 index 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. + + INDEX + ID of the index or fully qualified identifier for the index. To set + the name attribute: + ▸ provide the argument index on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --region=REGION + Cloud region for the index. To set the region attribute: + ▸ provide the argument index on the command line with a fully + specified name; + ▸ provide the argument --region on the command line; + ▸ set the property ai/region; + ▸ choose one from the prompted list of available regions. + +REQUIRED FLAGS + Exactly one of these must be specified: + + --datapoint-ids=[DATAPOINT_IDS,...] + List of index datapoint ids to be removed from the index. + + --datapoints-from-file=DATAPOINTS_FROM_FILE + Path to a local JSON file that contains the data points that need to + be added to the index. + +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 beta and might change without notice. This + variant is also available: + + $ gcloud alpha ai indexes remove-datapoints + diff --git a/gcloud/beta/ai/indexes/upsert-datapoints b/gcloud/beta/ai/indexes/upsert-datapoints new file mode 100644 index 000000000..dd7a70bc6 --- /dev/null +++ b/gcloud/beta/ai/indexes/upsert-datapoints @@ -0,0 +1,62 @@ +NAME + gcloud beta ai indexes upsert-datapoints - upsert data points into the + specified index + +SYNOPSIS + gcloud beta ai indexes upsert-datapoints (INDEX : --region=REGION) + --datapoints-from-file=DATAPOINTS_FROM_FILE [GCLOUD_WIDE_FLAG ...] + +EXAMPLES + To upsert datapoints into an index '123', run: + + $ gcloud beta ai indexes upsert-datapoints 123 \ + --datapoints-from-file=example.json --project=example \ + --region=us-central1 + +POSITIONAL ARGUMENTS + Index resource - Index to upsert data points from. 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 index 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. + + INDEX + ID of the index or fully qualified identifier for the index. To set + the name attribute: + ▸ provide the argument index on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --region=REGION + Cloud region for the index. To set the region attribute: + ▸ provide the argument index on the command line with a fully + specified name; + ▸ provide the argument --region on the command line; + ▸ set the property ai/region; + ▸ choose one from the prompted list of available regions. + +REQUIRED FLAGS + --datapoints-from-file=DATAPOINTS_FROM_FILE + Path to a local JSON file that contains the data points that need to be + added to the index. + +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 beta and might change without notice. This + variant is also available: + + $ gcloud alpha ai indexes upsert-datapoints + diff --git a/gcloud/beta/alloydb/clusters/create b/gcloud/beta/alloydb/clusters/create index 0bec93a09..bb7db0111 100644 --- a/gcloud/beta/alloydb/clusters/create +++ b/gcloud/beta/alloydb/clusters/create @@ -5,6 +5,13 @@ NAME SYNOPSIS gcloud beta alloydb clusters create CLUSTER --password=PASSWORD --region=REGION [--async] [--network=NETWORK] + [--disable-automated-backup + | [--automated-backup-days-of-week=[DAYS_OF_WEEK,...] + --automated-backup-start-times=[START_TIMES,...] + : --automated-backup-window=TIMEOUT_PERIOD + [--automated-backup-encryption-key=AUTOMATED_BACKUP_ENCRYPTION_KEY + : --automated-backup-encryption-key-keyring=AUTOMATED_BACKUP_ENCRYPTION_KEY_KEYRING --automated-backup-encryption-key-location=AUTOMATED_BACKUP_ENCRYPTION_KEY_LOCATION --automated-backup-encryption-key-project=AUTOMATED_BACKUP_ENCRYPTION_KEY_PROJECT] --automated-backup-retention-count=RETENTION_COUNT | --automated-backup-retention-period=RETENTION_PERIOD]] + [--disable-pitr | --pitr-log-retention-window=RETENTION_PERIOD] [--kms-key=KMS_KEY : --kms-keyring=KMS_KEYRING --kms-location=KMS_LOCATION --kms-project=KMS_PROJECT] [GCLOUD_WIDE_FLAG ...] @@ -42,6 +49,102 @@ OPTIONAL FLAGS network, 'testsharednetwork', this would be of the form:--network=projects/testproject/global/networks/testsharednetwork + Automated backup policy. If unspecified, automated backups are enabled. + + At most one of these can be specified: + + --disable-automated-backup + Disables automated backups on the cluster. + + Enable automated backup policy. + + --automated-backup-days-of-week=[DAYS_OF_WEEK,...] + Comma-separated list of days of the week to perform a backup. At + least one day of the week must be provided. (e.g., + --automated-backup-days-of-week=MONDAY,WEDNESDAY,SUNDAY). + DAYS_OF_WEEK must be one of: MONDAY, TUESDAY, WEDNESDAY, THURSDAY, + FRIDAY, SATURDAY, SUNDAY. + + This flag argument must be specified if any of the other arguments + in this group are specified. + + --automated-backup-start-times=[START_TIMES,...] + Comma-separated list of times during the day to start a backup. At + least one start time must be provided. The start times are assumed + to be in UTC and required to be an exact hour in the format HH:00. + (e.g., --automated-backup-start-times=01:00,13:00) + + This flag argument must be specified if any of the other arguments + in this group are specified. + + --automated-backup-window=TIMEOUT_PERIOD + The length of the time window beginning at start time during which + a backup can be taken. If a backup does not succeed within this + time window, it will be canceled and considered failed. The backup + window must be at least 5 minutes long. There is no upper bound on + the window. If not set, it will default to 1 hour. + + Key resource - The Cloud KMS (Key Management Service) cryptokey that + will be used to protect the automated backups. The 'AlloyDB Service + Agent' service account must hold permission 'Cloud KMS CryptoKey + Encrypter/Decrypter'. The arguments in this group can be used to + specify the attributes of this resource. + + --automated-backup-encryption-key=AUTOMATED_BACKUP_ENCRYPTION_KEY + ID of the key or fully qualified identifier for the key. To set + the kms-key attribute: + ◇ provide the argument --automated-backup-encryption-key on the + command line. + + This flag argument must be specified if any of the other + arguments in this group are specified. + + --automated-backup-encryption-key-keyring=AUTOMATED_BACKUP_ENCRYPTION_KEY_KEYRING + The KMS keyring of the key. To set the kms-keyring attribute: + ◇ provide the argument --automated-backup-encryption-key on the + command line with a fully specified name; + ◇ provide the argument + --automated-backup-encryption-key-keyring on the command line. + + --automated-backup-encryption-key-location=AUTOMATED_BACKUP_ENCRYPTION_KEY_LOCATION + The Cloud location for the key. To set the kms-location + attribute: + ◇ provide the argument --automated-backup-encryption-key on the + command line with a fully specified name; + ◇ provide the argument + --automated-backup-encryption-key-location on the command line. + + --automated-backup-encryption-key-project=AUTOMATED_BACKUP_ENCRYPTION_KEY_PROJECT + The Cloud project for the key. To set the kms-project attribute: + ◇ provide the argument --automated-backup-encryption-key on the + command line with a fully specified name; + ◇ provide the argument + --automated-backup-encryption-key-project on the command line; + ◇ set the property core/project. + + Retention policy. If no retention policy is provided, all automated + backups will be retained. + + At most one of these can be specified: + + --automated-backup-retention-count=RETENTION_COUNT + Number of most recent successful backups retained. + + --automated-backup-retention-period=RETENTION_PERIOD + Retention period of the backup relative to creation time. See $ + gcloud topic datetimes for information on duration formats. + + PITR configuration. + + At most one of these can be specified: + + --disable-pitr + Disables PITR on the cluster. + + --pitr-log-retention-window=RETENTION_PERIOD + Retention window of the log files saved to support PITR. See $ gcloud + topic datetimes for information on absolute duration formats. + Key resource - The Cloud KMS (Key Management Service) cryptokey that will be used to protect the cluster. The 'AlloyDB Service Agent' service account must hold permission 'Cloud KMS CryptoKey Encrypter/Decrypter'. diff --git a/gcloud/beta/deploy/releases/create b/gcloud/beta/deploy/releases/create index fc5820119..55688e1b9 100644 --- a/gcloud/beta/deploy/releases/create +++ b/gcloud/beta/deploy/releases/create @@ -12,6 +12,7 @@ SYNOPSIS [--build-artifacts=BUILD_ARTIFACTS | --images=[NAME=TAG,...]] [--disable-initial-rollout | --enable-initial-rollout] [--from-k8s-manifest=FROM_K8S_MANIFEST + | --from-run-manifest=FROM_RUN_MANIFEST | --skaffold-file=SKAFFOLD_FILE --source=SOURCE; default="."] [GCLOUD_WIDE_FLAG ...] @@ -168,6 +169,13 @@ FLAGS Storage source staging directory (see --gcs-source-staging-dir flag) after the release is complete. + --from-run-manifest=FROM_RUN_MANIFEST + The path to a Cloud Run manifest, which Cloud Deploy will use to + generate a skaffold.yaml file for you (for example, + foo/bar/service.yaml). The generated Skaffold file will be available + in the Google Cloud Storage source staging directory (see + --gcs-source-staging-dir flag) after the release is complete. + --skaffold-file=SKAFFOLD_FILE Path of the skaffold file absolute or relative to the source directory. diff --git a/gcloud/beta/deploy/targets/help b/gcloud/beta/deploy/targets/help index 120df286c..debd90e84 100644 --- a/gcloud/beta/deploy/targets/help +++ b/gcloud/beta/deploy/targets/help @@ -36,7 +36,7 @@ COMMANDS (BETA) List Cloud Deploy targets. redeploy - (BETA) Redeploy the last rollout to a target. + (BETA) Redeploy the last release to a target. remove-iam-policy-binding (BETA) Remove an IAM policy binding for a Cloud Deploy target. diff --git a/gcloud/beta/deploy/targets/redeploy b/gcloud/beta/deploy/targets/redeploy index 617b0d25c..f172723ff 100644 --- a/gcloud/beta/deploy/targets/redeploy +++ b/gcloud/beta/deploy/targets/redeploy @@ -1,5 +1,5 @@ NAME - gcloud beta deploy targets redeploy - redeploy the last rollout to a target + gcloud beta deploy targets redeploy - redeploy the last release to a target SYNOPSIS gcloud beta deploy targets redeploy (TARGET : --region=REGION) diff --git a/gcloud/beta/dns/managed-zones/create b/gcloud/beta/dns/managed-zones/create index c1b7e1ee5..8008e573a 100644 --- a/gcloud/beta/dns/managed-zones/create +++ b/gcloud/beta/dns/managed-zones/create @@ -23,19 +23,19 @@ EXAMPLES To create a managed-zone, run: $ gcloud beta dns managed-zones create my-zone \ - --dns-name my.zone.com. --description "My zone!" + --dns-name=my.zone.com. --description="My zone!" To create a managed-zone with DNSSEC, run: $ gcloud beta dns managed-zones create my-zone-2 \ - --description "Signed Zone" --dns-name myzone.example \ + --description="Signed Zone" --dns-name=myzone.example \ --dnssec-state=on To create a zonal managed-zone scoped to a GKE Cluster in us-east1-a, run: $ gcloud beta dns managed-zones create my-zonal-zone \ - --description "Signed Zone" --dns-name=cluster.local \ - --visibiilty=private --gkeclusters=cluster1 \ + --description="Signed Zone" --dns-name=cluster.local \ + --visibility=private --gkeclusters=cluster1 \ --location=us-east1-a POSITIONAL ARGUMENTS @@ -91,8 +91,9 @@ OPTIONAL FLAGS numbers. --location=LOCATION - Specifies the desired service location the request is sent to. Default - to Cloud DNS global service. + Specifies the desired service location the request is sent to. Defaults + to Cloud DNS global service. Use --location=global if you want to + target the global service. --[no-]log-dns-queries Specifies whether to enable query logging. Defaults to False. Use diff --git a/gcloud/beta/dns/managed-zones/delete b/gcloud/beta/dns/managed-zones/delete index 7bfded5e9..6c36f070b 100644 --- a/gcloud/beta/dns/managed-zones/delete +++ b/gcloud/beta/dns/managed-zones/delete @@ -25,8 +25,9 @@ POSITIONAL ARGUMENTS FLAGS --location=LOCATION - Specifies the desired service location the request is sent to. Default - to Cloud DNS global service. + Specifies the desired service location the request is sent to. Defaults + to Cloud DNS global service. Use --location=global if you want to + target the global service. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/beta/dns/managed-zones/describe b/gcloud/beta/dns/managed-zones/describe index 1101e5e72..d825c3f1b 100644 --- a/gcloud/beta/dns/managed-zones/describe +++ b/gcloud/beta/dns/managed-zones/describe @@ -39,8 +39,9 @@ POSITIONAL ARGUMENTS FLAGS --location=LOCATION - Specifies the desired service location the request is sent to. Default - to Cloud DNS global service. + Specifies the desired service location the request is sent to. Defaults + to Cloud DNS global service. Use --location=global if you want to + target the global service. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/beta/dns/managed-zones/list b/gcloud/beta/dns/managed-zones/list index f191e0cb5..83beb7158 100644 --- a/gcloud/beta/dns/managed-zones/list +++ b/gcloud/beta/dns/managed-zones/list @@ -26,8 +26,9 @@ EXAMPLES FLAGS --location=LOCATION - Specifies the desired service location the request is sent to. Default - to Cloud DNS global service. + Specifies the desired service location the request is sent to. Defaults + to Cloud DNS global service. Use --location=global if you want to + target the global service. LIST COMMAND FLAGS --filter=EXPRESSION diff --git a/gcloud/beta/dns/managed-zones/update b/gcloud/beta/dns/managed-zones/update index 849bc9599..92e1a2b00 100644 --- a/gcloud/beta/dns/managed-zones/update +++ b/gcloud/beta/dns/managed-zones/update @@ -89,8 +89,9 @@ FLAGS Length of the key-signing key in bits. Requires DNSSEC enabled. --location=LOCATION - Specifies the desired service location the request is sent to. Default - to Cloud DNS global service. + Specifies the desired service location the request is sent to. Defaults + to Cloud DNS global service. Use --location=global if you want to + target the global service. --[no-]log-dns-queries Specifies whether to enable query logging. Defaults to False. Use diff --git a/gcloud/beta/dns/record-sets/create b/gcloud/beta/dns/record-sets/create index f321a4a96..2b2ca60c3 100644 --- a/gcloud/beta/dns/record-sets/create +++ b/gcloud/beta/dns/record-sets/create @@ -164,8 +164,9 @@ REQUIRED FLAGS OPTIONAL FLAGS --location=LOCATION - Specifies the desired service location the request is sent to. Default - to Cloud DNS global service. + Specifies the desired service location the request is sent to. Defaults + to Cloud DNS global service. Use --location=global if you want to + target the global service. --ttl=TTL TTL (time to live) for the record-set. diff --git a/gcloud/beta/dns/record-sets/delete b/gcloud/beta/dns/record-sets/delete index b51a27032..e502366c3 100644 --- a/gcloud/beta/dns/record-sets/delete +++ b/gcloud/beta/dns/record-sets/delete @@ -29,8 +29,9 @@ REQUIRED FLAGS OPTIONAL FLAGS --location=LOCATION - Specifies the desired service location the request is sent to. Default - to Cloud DNS global service. + Specifies the desired service location the request is sent to. Defaults + to Cloud DNS global service. Use --location=global if you want to + target the global service. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/beta/dns/record-sets/describe b/gcloud/beta/dns/record-sets/describe index 0b0bb4bdc..181e17d84 100644 --- a/gcloud/beta/dns/record-sets/describe +++ b/gcloud/beta/dns/record-sets/describe @@ -30,8 +30,9 @@ REQUIRED FLAGS OPTIONAL FLAGS --location=LOCATION - Specifies the desired service location the request is sent to. Default - to Cloud DNS global service. + Specifies the desired service location the request is sent to. Defaults + to Cloud DNS global service. Use --location=global if you want to + target the global service. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/beta/dns/record-sets/export b/gcloud/beta/dns/record-sets/export index 56b267eb0..690c19de9 100644 --- a/gcloud/beta/dns/record-sets/export +++ b/gcloud/beta/dns/record-sets/export @@ -36,8 +36,9 @@ REQUIRED FLAGS OPTIONAL FLAGS --location=LOCATION - Specifies the desired service location the request is sent to. Default - to Cloud DNS global service. + Specifies the desired service location the request is sent to. Defaults + to Cloud DNS global service. Use --location=global if you want to + target the global service. --zone-file-format Indicates that records-file should be in the zone file format. When diff --git a/gcloud/beta/dns/record-sets/import b/gcloud/beta/dns/record-sets/import index cffbe3bfb..bf6086df2 100644 --- a/gcloud/beta/dns/record-sets/import +++ b/gcloud/beta/dns/record-sets/import @@ -50,8 +50,9 @@ OPTIONAL FLAGS importing the record-sets in the records-file. --location=LOCATION - Specifies the desired service location the request is sent to. Default - to Cloud DNS global service. + Specifies the desired service location the request is sent to. Defaults + to Cloud DNS global service. Use --location=global if you want to + target the global service. --replace-origin-ns Indicates that NS records for the origin of a zone should be imported diff --git a/gcloud/beta/dns/record-sets/list b/gcloud/beta/dns/record-sets/list index 6c79f36d2..1487dbf0b 100644 --- a/gcloud/beta/dns/record-sets/list +++ b/gcloud/beta/dns/record-sets/list @@ -37,8 +37,9 @@ REQUIRED FLAGS FLAGS --location=LOCATION - Specifies the desired service location the request is sent to. Default - to Cloud DNS global service. + Specifies the desired service location the request is sent to. Defaults + to Cloud DNS global service. Use --location=global if you want to + target the global service. --name=NAME Only list record-sets with this exact domain name. diff --git a/gcloud/beta/dns/record-sets/update b/gcloud/beta/dns/record-sets/update index cf35fb64f..956594eaa 100644 --- a/gcloud/beta/dns/record-sets/update +++ b/gcloud/beta/dns/record-sets/update @@ -25,8 +25,8 @@ EXAMPLES --rrdatas=1.2.3.4,9.8.7.6 --type=A --ttl=60 --zone=my_zone To update a record-set with dnsName foo.bar.com., record type A to have - rrdata [1.2.3.4, 9.8.7.6] and ttl 60 in my_zone that locates in us-east1-a, - run: + rrdata [1.2.3.4, 9.8.7.6] and ttl 60 in my_zone that is located in + us-east1-a, run: $ gcloud beta dns record-sets update foo.bar.com. \ --rrdatas=1.2.3.4,9.8.7.6 --type=A --ttl=60 --zone=my_zone \ @@ -131,8 +131,9 @@ REQUIRED FLAGS OPTIONAL FLAGS --location=LOCATION - Specifies the desired service location the request is sent to. Default - to Cloud DNS global service. + Specifies the desired service location the request is sent to. Defaults + to Cloud DNS global service. Use --location=global if you want to + target the global service. --ttl=TTL TTL (time to live) for the record-set. diff --git a/gcloud/beta/dns/response-policies/create b/gcloud/beta/dns/response-policies/create index 16534b6b8..49fb16227 100644 --- a/gcloud/beta/dns/response-policies/create +++ b/gcloud/beta/dns/response-policies/create @@ -54,8 +54,9 @@ OPTIONAL FLAGS response policy. --location=LOCATION - Specifies the desired service location the request is sent to. Default - to Cloud DNS global service. + Specifies the desired service location the request is sent to. Defaults + to Cloud DNS global service. Use --location=global if you want to + target the global service. --networks=[NETWORKS,...] The comma-separated list of network names to associate with the diff --git a/gcloud/beta/dns/response-policies/delete b/gcloud/beta/dns/response-policies/delete index 580db63f5..257b1fd5a 100644 --- a/gcloud/beta/dns/response-policies/delete +++ b/gcloud/beta/dns/response-policies/delete @@ -32,8 +32,9 @@ POSITIONAL ARGUMENTS FLAGS --location=LOCATION - Specifies the desired service location the request is sent to. Default - to Cloud DNS global service. + Specifies the desired service location the request is sent to. Defaults + to Cloud DNS global service. Use --location=global if you want to + target the global service. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/beta/dns/response-policies/describe b/gcloud/beta/dns/response-policies/describe index 5d2a3dd89..4aa76aa70 100644 --- a/gcloud/beta/dns/response-policies/describe +++ b/gcloud/beta/dns/response-policies/describe @@ -32,8 +32,9 @@ POSITIONAL ARGUMENTS FLAGS --location=LOCATION - Specifies the desired service location the request is sent to. Default - to Cloud DNS global service. + Specifies the desired service location the request is sent to. Defaults + to Cloud DNS global service. Use --location=global if you want to + target the global service. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/beta/dns/response-policies/list b/gcloud/beta/dns/response-policies/list index 9df9fd4c9..1ad320244 100644 --- a/gcloud/beta/dns/response-policies/list +++ b/gcloud/beta/dns/response-policies/list @@ -14,8 +14,9 @@ EXAMPLES FLAGS --location=LOCATION - Specifies the desired service location the request is sent to. Default - to Cloud DNS global service. + Specifies the desired service location the request is sent to. Defaults + to Cloud DNS global service. Use --location=global if you want to + target the global service. LIST COMMAND FLAGS --filter=EXPRESSION diff --git a/gcloud/beta/dns/response-policies/rules/create b/gcloud/beta/dns/response-policies/rules/create index f6dcddbf9..c84003bf9 100644 --- a/gcloud/beta/dns/response-policies/rules/create +++ b/gcloud/beta/dns/response-policies/rules/create @@ -91,8 +91,9 @@ OPTIONAL FLAGS The list of datas for this record, split by "|". --location=LOCATION - Specifies the desired service location the request is sent to. Default - to Cloud DNS global service. + Specifies the desired service location the request is sent to. Defaults + to Cloud DNS global service. Use --location=global if you want to + target the global service. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/beta/dns/response-policies/rules/delete b/gcloud/beta/dns/response-policies/rules/delete index 57bf80eb5..b0382e70d 100644 --- a/gcloud/beta/dns/response-policies/rules/delete +++ b/gcloud/beta/dns/response-policies/rules/delete @@ -41,8 +41,9 @@ POSITIONAL ARGUMENTS FLAGS --location=LOCATION - Specifies the desired service location the request is sent to. Default - to Cloud DNS global service. + Specifies the desired service location the request is sent to. Defaults + to Cloud DNS global service. Use --location=global if you want to + target the global service. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/beta/dns/response-policies/rules/describe b/gcloud/beta/dns/response-policies/rules/describe index 6fc214dfc..84dbd0a65 100644 --- a/gcloud/beta/dns/response-policies/rules/describe +++ b/gcloud/beta/dns/response-policies/rules/describe @@ -41,8 +41,9 @@ POSITIONAL ARGUMENTS FLAGS --location=LOCATION - Specifies the desired service location the request is sent to. Default - to Cloud DNS global service. + Specifies the desired service location the request is sent to. Defaults + to Cloud DNS global service. Use --location=global if you want to + target the global service. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/beta/dns/response-policies/rules/list b/gcloud/beta/dns/response-policies/rules/list index 476b52489..26090a0fe 100644 --- a/gcloud/beta/dns/response-policies/rules/list +++ b/gcloud/beta/dns/response-policies/rules/list @@ -30,8 +30,9 @@ POSITIONAL ARGUMENTS FLAGS --location=LOCATION - Specifies the desired service location the request is sent to. Default - to Cloud DNS global service. + Specifies the desired service location the request is sent to. Defaults + to Cloud DNS global service. Use --location=global if you want to + target the global service. LIST COMMAND FLAGS --filter=EXPRESSION diff --git a/gcloud/beta/dns/response-policies/rules/update b/gcloud/beta/dns/response-policies/rules/update index 9d4b37cbe..c55f090ab 100644 --- a/gcloud/beta/dns/response-policies/rules/update +++ b/gcloud/beta/dns/response-policies/rules/update @@ -89,8 +89,9 @@ FLAGS The list of datas for this record, split by "|". --location=LOCATION - Specifies the desired service location the request is sent to. Default - to Cloud DNS global service. + Specifies the desired service location the request is sent to. Defaults + to Cloud DNS global service. Use --location=global if you want to + target the global service. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/beta/dns/response-policies/update b/gcloud/beta/dns/response-policies/update index 422ba5645..9c3a9a9a2 100644 --- a/gcloud/beta/dns/response-policies/update +++ b/gcloud/beta/dns/response-policies/update @@ -54,8 +54,9 @@ FLAGS response policy. --location=LOCATION - Specifies the desired service location the request is sent to. Default - to Cloud DNS global service. + Specifies the desired service location the request is sent to. Defaults + to Cloud DNS global service. Use --location=global if you want to + target the global service. --networks=[NETWORKS,...] The comma-separated list of network names to associate with the diff --git a/gcloud/beta/run/deploy b/gcloud/beta/run/deploy index 53833e2a0..a0a836d87 100644 --- a/gcloud/beta/run/deploy +++ b/gcloud/beta/run/deploy @@ -32,8 +32,9 @@ SYNOPSIS | --remove-cloudsql-instances=[CLOUDSQL-INSTANCES,...] | --set-cloudsql-instances=[CLOUDSQL-INSTANCES,...] --binary-authorization=POLICY - | --clear-binary-authorization --clear-key - | --key=KEY --clear-post-key-revocation-action-type + | --clear-binary-authorization --clear-encryption-key-shutdown-hours + | --encryption-key-shutdown-hours=ENCRYPTION_KEY_SHUTDOWN_HOURS + --clear-key | --key=KEY --clear-post-key-revocation-action-type | --post-key-revocation-action-type=POST_KEY_REVOCATION_ACTION_TYPE] [--region=REGION | --cluster=CLUSTER --cluster-location=CLUSTER_LOCATION @@ -454,6 +455,15 @@ FLAGS --clear-binary-authorization Remove any previously set Binary Authorization policy. + At most one of these can be specified: + + --clear-encryption-key-shutdown-hours + Remove any previously set CMEK key shutdown hours setting. + + --encryption-key-shutdown-hours=ENCRYPTION_KEY_SHUTDOWN_HOURS + The number of hours to wait before an automatic shutdown server + after CMEK key revocation is detected. + At most one of these can be specified: --clear-key diff --git a/gcloud/beta/run/services/update b/gcloud/beta/run/services/update index c4098ced9..e0fec3130 100644 --- a/gcloud/beta/run/services/update +++ b/gcloud/beta/run/services/update @@ -20,8 +20,9 @@ SYNOPSIS | --remove-cloudsql-instances=[CLOUDSQL-INSTANCES,...] | --set-cloudsql-instances=[CLOUDSQL-INSTANCES,...] --binary-authorization=POLICY - | --clear-binary-authorization --clear-key - | --key=KEY --clear-post-key-revocation-action-type + | --clear-binary-authorization --clear-encryption-key-shutdown-hours + | --encryption-key-shutdown-hours=ENCRYPTION_KEY_SHUTDOWN_HOURS + --clear-key | --key=KEY --clear-post-key-revocation-action-type | --post-key-revocation-action-type=POST_KEY_REVOCATION_ACTION_TYPE] [--clear-env-vars | --env-vars-file=FILE_PATH | --set-env-vars=[KEY=VALUE,...] @@ -286,6 +287,15 @@ FLAGS --clear-binary-authorization Remove any previously set Binary Authorization policy. + At most one of these can be specified: + + --clear-encryption-key-shutdown-hours + Remove any previously set CMEK key shutdown hours setting. + + --encryption-key-shutdown-hours=ENCRYPTION_KEY_SHUTDOWN_HOURS + The number of hours to wait before an automatic shutdown server + after CMEK key revocation is detected. + At most one of these can be specified: --clear-key diff --git a/gcloud/beta/spanner/databases/create b/gcloud/beta/spanner/databases/create index edf0a9946..8de1e41b4 100644 --- a/gcloud/beta/spanner/databases/create +++ b/gcloud/beta/spanner/databases/create @@ -80,7 +80,8 @@ FLAGS is an error in any statement, the database is not created. This option is not supported for the PostgreSQL dialect. Full DDL specification is at https://cloud.google.com/spanner/docs/data-definition-language. If - --ddl_file is set, --ddl is ignored. + --ddl_file is set, --ddl is ignored. One line comments starting with -- + are ignored. Key resource - Cloud KMS key to be used to create the Cloud Spanner database. The arguments in this group can be used to specify the diff --git a/gcloud/beta/spanner/databases/ddl/update b/gcloud/beta/spanner/databases/ddl/update index ae96491c3..8fafb24fa 100644 --- a/gcloud/beta/spanner/databases/ddl/update +++ b/gcloud/beta/spanner/databases/ddl/update @@ -58,7 +58,8 @@ FLAGS Path of a file containing semi-colon separated DDL (data definition language) statements to run inside the database. If a statement fails, all subsequent statements in the batch are automatically cancelled. If - --ddl_file is set, --ddl is ignored. + --ddl_file is set, --ddl is ignored. One line comments starting with -- + are ignored. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/compute/backend-buckets/create b/gcloud/compute/backend-buckets/create index e040fbd3d..91c7cc289 100644 --- a/gcloud/compute/backend-buckets/create +++ b/gcloud/compute/backend-buckets/create @@ -8,6 +8,7 @@ SYNOPSIS [--cache-key-include-http-header=[HEADER_FIELD_NAME,...]] [--cache-key-query-string-whitelist=[QUERY_STRING,...]] [--cache-mode=CACHE_MODE] [--client-ttl=CLIENT_TTL] + [--compression-mode=COMPRESSION_MODE] [--custom-response-header=CUSTOM_RESPONSE_HEADER] [--default-ttl=DEFAULT_TTL] [--description=DESCRIPTION] [--[no-]enable-cdn] [--max-ttl=MAX_TTL] [--[no-]negative-caching] @@ -107,6 +108,16 @@ OPTIONAL FLAGS When the cache mode is set to "USE_ORIGIN_HEADERS", you must omit this field. + --compression-mode=COMPRESSION_MODE + Compress text responses using Brotli or gzip compression, based on the + client's Accept-Encoding header. Two modes are supported: AUTOMATIC + (recommended) - automatically uses the best compression based on the + Accept-Encoding header sent by the client. In most cases, this will + result in Brotli compression being favored. DISABLED - disables + compression. Existing compressed responses cached by Cloud CDN will not + be served to clients. COMPRESSION_MODE must be one of: DISABLED, + AUTOMATIC. + --custom-response-header=CUSTOM_RESPONSE_HEADER Custom headers that the external HTTP(S) load balancer adds to proxied responses. For the list of headers, see Creating custom headers diff --git a/gcloud/compute/backend-buckets/update b/gcloud/compute/backend-buckets/update index 9c62582e4..7d3e3ecac 100644 --- a/gcloud/compute/backend-buckets/update +++ b/gcloud/compute/backend-buckets/update @@ -5,7 +5,8 @@ SYNOPSIS gcloud compute backend-buckets update BACKEND_BUCKET_NAME [--cache-key-include-http-header=[HEADER_FIELD_NAME,...]] [--cache-key-query-string-whitelist=[QUERY_STRING,...]] - [--cache-mode=CACHE_MODE] [--description=DESCRIPTION] + [--cache-mode=CACHE_MODE] [--compression-mode=COMPRESSION_MODE] + [--description=DESCRIPTION] [--edge-security-policy=EDGE_SECURITY_POLICY] [--[no-]enable-cdn] [--gcs-bucket-name=GCS_BUCKET_NAME] [--[no-]request-coalescing] [--signed-url-cache-max-age=SIGNED_URL_CACHE_MAX_AGE] @@ -60,6 +61,16 @@ FLAGS require a full trip to the origin on every request, potentially impacting performance and increasing load on the origin server. + --compression-mode=COMPRESSION_MODE + Compress text responses using Brotli or gzip compression, based on the + client's Accept-Encoding header. Two modes are supported: AUTOMATIC + (recommended) - automatically uses the best compression based on the + Accept-Encoding header sent by the client. In most cases, this will + result in Brotli compression being favored. DISABLED - disables + compression. Existing compressed responses cached by Cloud CDN will not + be served to clients. COMPRESSION_MODE must be one of: DISABLED, + AUTOMATIC. + --description=DESCRIPTION An optional, textual description for the backend bucket. diff --git a/gcloud/compute/backend-services/create b/gcloud/compute/backend-services/create index 1f5024298..4995085cb 100644 --- a/gcloud/compute/backend-services/create +++ b/gcloud/compute/backend-services/create @@ -10,7 +10,7 @@ SYNOPSIS [--cache-key-include-named-cookie=[NAMED_COOKIE,...]] [--no-cache-key-include-protocol] [--no-cache-key-include-query-string] [--cache-mode=CACHE_MODE] [--client-ttl=CLIENT_TTL] - [--connection-drain-on-failover] + [--compression-mode=COMPRESSION_MODE] [--connection-drain-on-failover] [--connection-draining-timeout=CONNECTION_DRAINING_TIMEOUT] [--connection-persistence-on-unhealthy-backends=CONNECTION_PERSISTENCE_ON_UNHEALTHY_BACKENDS] [--custom-request-header=CUSTOM_REQUEST_HEADER] @@ -161,6 +161,16 @@ FLAGS When the cache mode is set to "USE_ORIGIN_HEADERS", you must omit this field. + --compression-mode=COMPRESSION_MODE + Compress text responses using Brotli or gzip compression, based on the + client's Accept-Encoding header. Two modes are supported: AUTOMATIC + (recommended) - automatically uses the best compression based on the + Accept-Encoding header sent by the client. In most cases, this will + result in Brotli compression being favored. DISABLED - disables + compression. Existing compressed responses cached by Cloud CDN will not + be served to clients. COMPRESSION_MODE must be one of: DISABLED, + AUTOMATIC. + --connection-drain-on-failover Connection drain is enabled by default and on failover or failback connections will be drained. If connection drain is disabled, the diff --git a/gcloud/compute/backend-services/update b/gcloud/compute/backend-services/update index 0bbe4a46f..8aaaa636a 100644 --- a/gcloud/compute/backend-services/update +++ b/gcloud/compute/backend-services/update @@ -7,7 +7,8 @@ SYNOPSIS [--cache-key-include-http-header=[HEADER_FIELD_NAME,...]] [--cache-key-include-named-cookie=[NAMED_COOKIE,...]] [--cache-key-include-protocol] [--cache-key-include-query-string] - [--cache-mode=CACHE_MODE] [--connection-drain-on-failover] + [--cache-mode=CACHE_MODE] [--compression-mode=COMPRESSION_MODE] + [--connection-drain-on-failover] [--connection-draining-timeout=CONNECTION_DRAINING_TIMEOUT] [--connection-persistence-on-unhealthy-backends=CONNECTION_PERSISTENCE_ON_UNHEALTHY_BACKENDS] [--description=DESCRIPTION] [--drop-traffic-if-unhealthy] @@ -109,6 +110,16 @@ FLAGS require a full trip to the origin on every request, potentially impacting performance and increasing load on the origin server. + --compression-mode=COMPRESSION_MODE + Compress text responses using Brotli or gzip compression, based on the + client's Accept-Encoding header. Two modes are supported: AUTOMATIC + (recommended) - automatically uses the best compression based on the + Accept-Encoding header sent by the client. In most cases, this will + result in Brotli compression being favored. DISABLED - disables + compression. Existing compressed responses cached by Cloud CDN will not + be served to clients. COMPRESSION_MODE must be one of: DISABLED, + AUTOMATIC. + --connection-drain-on-failover Connection drain is enabled by default and on failover or failback connections will be drained. If connection drain is disabled, the diff --git a/gcloud/compute/instance-templates/create b/gcloud/compute/instance-templates/create index 4d5b46e19..abae29b5c 100644 --- a/gcloud/compute/instance-templates/create +++ b/gcloud/compute/instance-templates/create @@ -35,6 +35,7 @@ SYNOPSIS [--source-instance-zone=SOURCE_INSTANCE_ZONE] [--stack-type=STACK_TYPE] [--subnet=SUBNET] [--tags=TAG,[TAG,...]] [--threads-per-core=THREADS_PER_CORE] + [--visible-core-count=VISIBLE_CORE_COUNT] [--address=ADDRESS | --no-address] [--boot-disk-kms-key=BOOT_DISK_KMS_KEY : --boot-disk-kms-keyring=BOOT_DISK_KMS_KEYRING @@ -696,6 +697,12 @@ FLAGS For more information about configuring SMT, see: https://cloud.google.com/compute/docs/instances/configuring-simultaneous-multithreading. + --visible-core-count=VISIBLE_CORE_COUNT + The number of physical cores to expose to the instance's guest + operating system. The number of virtual CPUs visible to the instance's + guest operating system is this number of cores multiplied by the + instance's count of visible threads per physical core. + At most one of these can be specified: --address=ADDRESS diff --git a/gcloud/compute/instances/bulk/create b/gcloud/compute/instances/bulk/create index a3f1f284b..cbd3b1f62 100644 --- a/gcloud/compute/instances/bulk/create +++ b/gcloud/compute/instances/bulk/create @@ -37,6 +37,7 @@ SYNOPSIS [--subnet=SUBNET] [--tags=TAG,[TAG,...]] [--target-distribution-shape=SHAPE] [--threads-per-core=THREADS_PER_CORE] + [--visible-core-count=VISIBLE_CORE_COUNT] [--boot-disk-kms-key=BOOT_DISK_KMS_KEY : --boot-disk-kms-keyring=BOOT_DISK_KMS_KEYRING --boot-disk-kms-location=BOOT_DISK_KMS_LOCATION @@ -672,6 +673,12 @@ OPTIONAL FLAGS For more information about configuring SMT, see: https://cloud.google.com/compute/docs/instances/configuring-simultaneous-multithreading. + --visible-core-count=VISIBLE_CORE_COUNT + The number of physical cores to expose to the instance's guest + operating system. The number of virtual CPUs visible to the instance's + guest operating system is this number of cores multiplied by the + instance's count of visible threads per physical core. + Key resource - The Cloud KMS (Key Management Service) cryptokey that will be used to protect the disk. The arguments in this group can be used to specify the attributes of this resource. diff --git a/gcloud/compute/instances/create b/gcloud/compute/instances/create index c36a23025..89bc6df96 100644 --- a/gcloud/compute/instances/create +++ b/gcloud/compute/instances/create @@ -38,7 +38,8 @@ SYNOPSIS [--shielded-integrity-monitoring] [--shielded-secure-boot] [--shielded-vtpm] [--source-instance-template=SOURCE_INSTANCE_TEMPLATE] [--stack-type=STACK_TYPE] [--subnet=SUBNET] [--tags=TAG,[TAG,...]] - [--threads-per-core=THREADS_PER_CORE] [--zone=ZONE] + [--threads-per-core=THREADS_PER_CORE] + [--visible-core-count=VISIBLE_CORE_COUNT] [--zone=ZONE] [--address=ADDRESS | --no-address] [--boot-disk-kms-key=BOOT_DISK_KMS_KEY : --boot-disk-kms-keyring=BOOT_DISK_KMS_KEYRING @@ -756,6 +757,12 @@ FLAGS For more information about configuring SMT, see: https://cloud.google.com/compute/docs/instances/configuring-simultaneous-multithreading. + --visible-core-count=VISIBLE_CORE_COUNT + The number of physical cores to expose to the instance's guest + operating system. The number of virtual CPUs visible to the instance's + guest operating system is this number of cores multiplied by the + instance's count of visible threads per physical core. + --zone=ZONE Zone of the instances to create. If not specified and the compute/zone property isn't set, you might be prompted to select a zone (interactive diff --git a/gcloud/compute/instances/create-with-container b/gcloud/compute/instances/create-with-container index a0a29e36b..b34c937a6 100644 --- a/gcloud/compute/instances/create-with-container +++ b/gcloud/compute/instances/create-with-container @@ -41,7 +41,8 @@ SYNOPSIS [--shielded-integrity-monitoring] [--shielded-secure-boot] [--shielded-vtpm] [--source-instance-template=SOURCE_INSTANCE_TEMPLATE] [--subnet=SUBNET] [--tags=TAG,[TAG,...]] - [--threads-per-core=THREADS_PER_CORE] [--zone=ZONE] + [--threads-per-core=THREADS_PER_CORE] + [--visible-core-count=VISIBLE_CORE_COUNT] [--zone=ZONE] [--address=ADDRESS | --no-address] [--custom-cpu=CUSTOM_CPU --custom-memory=CUSTOM_MEMORY : --custom-extensions --custom-vm-type=CUSTOM_VM_TYPE] @@ -666,6 +667,12 @@ FLAGS For more information about configuring SMT, see: https://cloud.google.com/compute/docs/instances/configuring-simultaneous-multithreading. + --visible-core-count=VISIBLE_CORE_COUNT + The number of physical cores to expose to the instance's guest + operating system. The number of virtual CPUs visible to the instance's + guest operating system is this number of cores multiplied by the + instance's count of visible threads per physical core. + --zone=ZONE Zone of the instances to create. If not specified, you might be prompted to select a zone (interactive mode only). gcloud attempts to diff --git a/gcloud/database-migration/migration-jobs/create b/gcloud/database-migration/migration-jobs/create index fb1ae82e9..1031ead95 100644 --- a/gcloud/database-migration/migration-jobs/create +++ b/gcloud/database-migration/migration-jobs/create @@ -69,7 +69,7 @@ POSITIONAL ARGUMENTS REQUIRED FLAGS Connection profile resource - ID of the destination connection profile, - representing thedestination database. This represents a Cloud resource. + representing the destination database. 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 --destination on the command line with a fully diff --git a/gcloud/database-migration/migration-jobs/update b/gcloud/database-migration/migration-jobs/update index a555ddca8..25a939abe 100644 --- a/gcloud/database-migration/migration-jobs/update +++ b/gcloud/database-migration/migration-jobs/update @@ -58,7 +58,7 @@ POSITIONAL ARGUMENTS FLAGS Connection profile resource - ID of the destination connection profile, - representing thedestination database. This represents a Cloud resource. + representing the destination database. 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 --destination on the command line with a fully diff --git a/gcloud/deploy/releases/create b/gcloud/deploy/releases/create index 3758248d3..fe55a919a 100644 --- a/gcloud/deploy/releases/create +++ b/gcloud/deploy/releases/create @@ -12,6 +12,7 @@ SYNOPSIS [--build-artifacts=BUILD_ARTIFACTS | --images=[NAME=TAG,...]] [--disable-initial-rollout | --enable-initial-rollout] [--from-k8s-manifest=FROM_K8S_MANIFEST + | --from-run-manifest=FROM_RUN_MANIFEST | --skaffold-file=SKAFFOLD_FILE --source=SOURCE; default="."] [GCLOUD_WIDE_FLAG ...] @@ -167,6 +168,13 @@ FLAGS Storage source staging directory (see --gcs-source-staging-dir flag) after the release is complete. + --from-run-manifest=FROM_RUN_MANIFEST + The path to a Cloud Run manifest, which Cloud Deploy will use to + generate a skaffold.yaml file for you (for example, + foo/bar/service.yaml). The generated Skaffold file will be available + in the Google Cloud Storage source staging directory (see + --gcs-source-staging-dir flag) after the release is complete. + --skaffold-file=SKAFFOLD_FILE Path of the skaffold file absolute or relative to the source directory. diff --git a/gcloud/deploy/targets/help b/gcloud/deploy/targets/help index f775d57fa..4c06f32b5 100644 --- a/gcloud/deploy/targets/help +++ b/gcloud/deploy/targets/help @@ -36,7 +36,7 @@ COMMANDS List Cloud Deploy targets. redeploy - Redeploy the last rollout to a target. + Redeploy the last release to a target. remove-iam-policy-binding Remove an IAM policy binding for a Cloud Deploy target. diff --git a/gcloud/deploy/targets/redeploy b/gcloud/deploy/targets/redeploy index ff6cef3fc..82834a92c 100644 --- a/gcloud/deploy/targets/redeploy +++ b/gcloud/deploy/targets/redeploy @@ -1,5 +1,5 @@ NAME - gcloud deploy targets redeploy - redeploy the last rollout to a target + gcloud deploy targets redeploy - redeploy the last release to a target SYNOPSIS gcloud deploy targets redeploy (TARGET : --region=REGION) diff --git a/gcloud/dns/managed-zones/create b/gcloud/dns/managed-zones/create index ca042cf97..c94ebbba5 100644 --- a/gcloud/dns/managed-zones/create +++ b/gcloud/dns/managed-zones/create @@ -5,8 +5,9 @@ SYNOPSIS gcloud dns managed-zones create ZONE_NAME --description=DESCRIPTION --dns-name=DNS_NAME [--denial-of-existence=DENIAL_OF_EXISTENCE] [--dnssec-state=DNSSEC_STATE] [--forwarding-targets=[IP_ADDRESSES,...]] - [--ksk-algorithm=KSK_ALGORITHM] [--ksk-key-length=KSK_KEY_LENGTH] - [--labels=[KEY=VALUE,...]] [--[no-]log-dns-queries] + [--gkeclusters=[GKECLUSTERS,...]] [--ksk-algorithm=KSK_ALGORITHM] + [--ksk-key-length=KSK_KEY_LENGTH] [--labels=[KEY=VALUE,...]] + [--location=LOCATION] [--[no-]log-dns-queries] [--managed-reverse-lookup] [--networks=[NETWORK,...]] [--private-forwarding-targets=[IP_ADDRESSES,...]] [--service-directory-namespace=SERVICE_DIRECTORY_NAMESPACE] @@ -21,8 +22,21 @@ DESCRIPTION EXAMPLES To create a managed-zone, run: - $ gcloud dns managed-zones create my-zone --dns-name my.zone.com. \ - --description "My zone!" + $ gcloud dns managed-zones create my-zone --dns-name=my.zone.com. \ + --description="My zone!" + + To create a managed-zone with DNSSEC, run: + + $ gcloud dns managed-zones create my-zone-2 \ + --description="Signed Zone" --dns-name=myzone.example \ + --dnssec-state=on + + To create a zonal managed-zone scoped to a GKE Cluster in us-east1-a, run: + + $ gcloud dns managed-zones create my-zonal-zone \ + --description="Signed Zone" --dns-name=cluster.local \ + --visibility=private --gkeclusters=cluster1 \ + --location=us-east1-a POSITIONAL ARGUMENTS ZONE_NAME @@ -56,6 +70,10 @@ OPTIONAL FLAGS addresses will forward to the target through the Internet. RFC1918 addresses will forward through the VPC. + --gkeclusters=[GKECLUSTERS,...] + List of GKE clusters that the zone should be visible in if the zone + visibility is [private]. + --ksk-algorithm=KSK_ALGORITHM String mnemonic specifying the DNSSEC algorithm of the key-signing key. Requires DNSSEC enabled. KSK_ALGORITHM must be one of: ecdsap256sha256, @@ -72,6 +90,11 @@ OPTIONAL FLAGS contain only hyphens (-), underscores (_), lowercase characters, and numbers. + --location=LOCATION + Specifies the desired service location the request is sent to. Defaults + to Cloud DNS global service. Use --location=global if you want to + target the global service. + --[no-]log-dns-queries Specifies whether to enable query logging. Defaults to False. Use --log-dns-queries to enable and --no-log-dns-queries to disable. diff --git a/gcloud/dns/managed-zones/delete b/gcloud/dns/managed-zones/delete index e2d80532d..8f738b341 100644 --- a/gcloud/dns/managed-zones/delete +++ b/gcloud/dns/managed-zones/delete @@ -2,7 +2,8 @@ NAME gcloud dns managed-zones delete - delete an empty Cloud DNS managed-zone SYNOPSIS - gcloud dns managed-zones delete ZONE_NAME [GCLOUD_WIDE_FLAG ...] + gcloud dns managed-zones delete ZONE_NAME [--location=LOCATION] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION This command deletes an empty Cloud DNS managed-zone. An empty managed-zone @@ -13,10 +14,20 @@ EXAMPLES $ gcloud dns managed-zones delete my-zone + To delete an empty zonal managed-zone in us-east1-c, run: + + $ gcloud dns managed-zones delete my-zone --location=us-east1-c + POSITIONAL ARGUMENTS ZONE_NAME The name of the empty managed-zone to be deleted. +FLAGS + --location=LOCATION + Specifies the desired service location the request is sent to. Defaults + to Cloud DNS global service. Use --location=global if you want to + target the global service. + 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/dns/managed-zones/describe b/gcloud/dns/managed-zones/describe index 9b4013ef1..d018eabef 100644 --- a/gcloud/dns/managed-zones/describe +++ b/gcloud/dns/managed-zones/describe @@ -3,7 +3,8 @@ NAME managed-zone SYNOPSIS - gcloud dns managed-zones describe ZONE [GCLOUD_WIDE_FLAG ...] + gcloud dns managed-zones describe ZONE [--location=LOCATION] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION This command displays the details of the specified managed-zone. @@ -13,6 +14,11 @@ EXAMPLES $ gcloud dns managed-zones describe my-zone + To display the details of a zonal managed-zone in Zonal Cloud DNS service + in us-east1-c, run: + + $ gcloud dns managed-zones describe my-zone --location=us-east1-c + POSITIONAL ARGUMENTS Zone resource - The name of the managed-zone to be described. This represents a Cloud resource. (NOTE) Some attributes are not given @@ -30,6 +36,12 @@ POSITIONAL ARGUMENTS zone attribute: ▸ provide the argument zone on the command line. +FLAGS + --location=LOCATION + Specifies the desired service location the request is sent to. Defaults + to Cloud DNS global service. Use --location=global if you want to + target the global service. + 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/dns/managed-zones/list b/gcloud/dns/managed-zones/list index 66c9ea9b4..d4b373dbc 100644 --- a/gcloud/dns/managed-zones/list +++ b/gcloud/dns/managed-zones/list @@ -2,8 +2,8 @@ NAME gcloud dns managed-zones list - view the list of all your managed-zones SYNOPSIS - gcloud dns managed-zones list [--filter=EXPRESSION] [--limit=LIMIT] - [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + gcloud dns managed-zones list [--location=LOCATION] [--filter=EXPRESSION] + [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -18,6 +18,17 @@ EXAMPLES $ gcloud dns managed-zones list --limit=10 + To see the list of all managed-zones in a Zonal Cloud DNS service in + us-east1-c, run: + + $ gcloud dns managed-zones list --location=us-east1-c + +FLAGS + --location=LOCATION + Specifies the desired service location the request is sent to. Defaults + to Cloud DNS global service. Use --location=global if you want to + target the global service. + LIST COMMAND FLAGS --filter=EXPRESSION Apply a Boolean filter EXPRESSION to each resource item to be listed. diff --git a/gcloud/dns/managed-zones/update b/gcloud/dns/managed-zones/update index 5316a1308..8af2574c6 100644 --- a/gcloud/dns/managed-zones/update +++ b/gcloud/dns/managed-zones/update @@ -5,7 +5,8 @@ SYNOPSIS gcloud dns managed-zones update ZONE [--async] [--denial-of-existence=DENIAL_OF_EXISTENCE] [--description=DESCRIPTION] [--dnssec-state=DNSSEC_STATE] [--forwarding-targets=[IP_ADDRESSES,...]] - [--ksk-algorithm=KSK_ALGORITHM] [--ksk-key-length=KSK_KEY_LENGTH] + [--gkeclusters=[GKECLUSTERS,...]] [--ksk-algorithm=KSK_ALGORITHM] + [--ksk-key-length=KSK_KEY_LENGTH] [--location=LOCATION] [--[no-]log-dns-queries] [--managed-reverse-lookup] [--networks=[NETWORK,...]] [--private-forwarding-targets=[IP_ADDRESSES,...]] @@ -24,6 +25,11 @@ EXAMPLES $ gcloud dns managed-zones update my-zone \ --description="Hello, world!" + To change the description of a zonal managed-zone in us-east1-a, run: + + $ gcloud dns managed-zones update my-zone \ + --description="Hello, world!" --location=us-east1-a + POSITIONAL ARGUMENTS Zone resource - The name of the managed-zone to be updated. This represents a Cloud resource. (NOTE) Some attributes are not given @@ -69,6 +75,10 @@ FLAGS addresses will forward to the target through the Internet. RFC1918 addresses will forward through the VPC. + --gkeclusters=[GKECLUSTERS,...] + List of GKE clusters that the zone should be visible in if the zone + visibility is [private]. + --ksk-algorithm=KSK_ALGORITHM String mnemonic specifying the DNSSEC algorithm of the key-signing key. Requires DNSSEC enabled. KSK_ALGORITHM must be one of: ecdsap256sha256, @@ -77,6 +87,11 @@ FLAGS --ksk-key-length=KSK_KEY_LENGTH Length of the key-signing key in bits. Requires DNSSEC enabled. + --location=LOCATION + Specifies the desired service location the request is sent to. Defaults + to Cloud DNS global service. Use --location=global if you want to + target the global service. + --[no-]log-dns-queries Specifies whether to enable query logging. Defaults to False. Use --log-dns-queries to enable and --no-log-dns-queries to disable. diff --git a/gcloud/dns/record-sets/create b/gcloud/dns/record-sets/create index 8e0ac78fd..94c57239c 100644 --- a/gcloud/dns/record-sets/create +++ b/gcloud/dns/record-sets/create @@ -9,8 +9,8 @@ SYNOPSIS --routing-policy-backup-data-type=ROUTING_POLICY_BACKUP_DATA_TYPE --routing-policy-primary-data=ROUTING_POLICY_PRIMARY_DATA : --backup-data-trickle-ratio=BACKUP_DATA_TRICKLE_RATIO]) - : --enable-geo-fencing --enable-health-checking]) [--ttl=TTL] - [GCLOUD_WIDE_FLAG ...] + : --enable-geo-fencing --enable-health-checking]) + [--location=LOCATION] [--ttl=TTL] [GCLOUD_WIDE_FLAG ...] DESCRIPTION This command creates a record-set contained within the specified @@ -24,12 +24,12 @@ EXAMPLES --rrdatas=1.2.3.4,9.8.7.6 --type=A --ttl=60 --zone=my_zone To create a geo routed record-set with dnsName foo.bar.com., record type A, - routing-policy-data "us-centra1=1.2.3.4,2.3.4.5;us-west1=3.4.5.6,9.8.7.6" + routing_policy_data "us-centra1=1.2.3.4,2.3.4.5;us-west1=3.4.5.6,9.8.7.6" and ttl 60 in my_zone. $ gcloud dns record-sets create foo.bar.com. \ - --routing-policy-data="us-centra1=1.2.3.4,2.3.4.5;us-west1=3.4.5\ - .6,9.8.7.6" --routing-policy-type=GEO --type=A --ttl=60 \ + --routing_policy_data="us-centra1=1.2.3.4,2.3.4.5;us-west1=3.4.5\ + .6,9.8.7.6" --routing_policy_type=GEO --type=A --ttl=60 \ --zone=my_zone --location=us-east1-a To create a record-set with dnsName foo.bar.com., record type A, rrdata @@ -45,7 +45,7 @@ EXAMPLES traffic ratio of 10% to the backup data, and ttl 60 in my_zone. $ gcloud dns record-sets create foo.bar.com. --type=A --ttl=60 \ - --zone=routing-policy-test --routing-policy-type=FAILOVER \ + --zone=routing-policy-test --routing_policy_type=FAILOVER \ --routing-policy-primary-data='config1' \ --routing-policy-backup-data-type=GEO \ --routing-policy-backup-data='us-centra1=1.2.3.4,2.3.4.5;us-west\ @@ -58,8 +58,8 @@ EXAMPLES my_zone. $ gcloud dns record-sets create foo.bar.com. --type=A --ttl=60 \ - --zone=routing-policy-test --routing-policy-type=GEO \ - --routing-policy-data='us-centra1=config1,config2;us-west1=3.4.5\ + --zone=routing-policy-test --routing_policy_type=GEO \ + --routing_policy_data='us-centra1=config1,config2;us-west1=3.4.5\ .6,9.8.7.6' --enable-health-checking --enable-geo-fencing \ --zone=my_zone @@ -161,6 +161,11 @@ REQUIRED FLAGS targets even when the primary targets are healthy. OPTIONAL FLAGS + --location=LOCATION + Specifies the desired service location the request is sent to. Defaults + to Cloud DNS global service. Use --location=global if you want to + target the global service. + --ttl=TTL TTL (time to live) for the record-set. diff --git a/gcloud/dns/record-sets/delete b/gcloud/dns/record-sets/delete index d89325776..476a45130 100644 --- a/gcloud/dns/record-sets/delete +++ b/gcloud/dns/record-sets/delete @@ -3,7 +3,7 @@ NAME SYNOPSIS gcloud dns record-sets delete DNS_NAME --type=TYPE --zone=ZONE, -z ZONE - [GCLOUD_WIDE_FLAG ...] + [--location=LOCATION] [GCLOUD_WIDE_FLAG ...] DESCRIPTION This command deletes a record-set contained within the specified @@ -26,6 +26,12 @@ REQUIRED FLAGS --zone=ZONE, -z ZONE Name of the managed zone whose record sets you want to manage. +OPTIONAL FLAGS + --location=LOCATION + Specifies the desired service location the request is sent to. Defaults + to Cloud DNS global service. Use --location=global if you want to + target the global service. + 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/dns/record-sets/describe b/gcloud/dns/record-sets/describe index c0b35f0db..8f4002ec4 100644 --- a/gcloud/dns/record-sets/describe +++ b/gcloud/dns/record-sets/describe @@ -3,7 +3,7 @@ NAME SYNOPSIS gcloud dns record-sets describe DNS_NAME --type=TYPE --zone=ZONE, -z ZONE - [GCLOUD_WIDE_FLAG ...] + [--location=LOCATION] [GCLOUD_WIDE_FLAG ...] DESCRIPTION This command describes a record-set contained within the specified @@ -27,6 +27,12 @@ REQUIRED FLAGS --zone=ZONE, -z ZONE Name of the managed zone whose record sets you want to manage. +OPTIONAL FLAGS + --location=LOCATION + Specifies the desired service location the request is sent to. Defaults + to Cloud DNS global service. Use --location=global if you want to + target the global service. + 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/dns/record-sets/export b/gcloud/dns/record-sets/export index 2575c07b1..ec5aee253 100644 --- a/gcloud/dns/record-sets/export +++ b/gcloud/dns/record-sets/export @@ -3,7 +3,7 @@ NAME SYNOPSIS gcloud dns record-sets export RECORDS_FILE --zone=ZONE, -z ZONE - [--zone-file-format] [GCLOUD_WIDE_FLAG ...] + [--location=LOCATION] [--zone-file-format] [GCLOUD_WIDE_FLAG ...] DESCRIPTION This command exports the record-sets contained within the specified @@ -34,6 +34,11 @@ REQUIRED FLAGS Name of the managed zone whose record sets you want to manage. OPTIONAL FLAGS + --location=LOCATION + Specifies the desired service location the request is sent to. Defaults + to Cloud DNS global service. Use --location=global if you want to + target the global service. + --zone-file-format Indicates that records-file should be in the zone file format. When using this flag, expect the record-set to be exported to a BIND zone diff --git a/gcloud/dns/record-sets/import b/gcloud/dns/record-sets/import index 7f63951a0..a96f81875 100644 --- a/gcloud/dns/record-sets/import +++ b/gcloud/dns/record-sets/import @@ -3,8 +3,8 @@ NAME SYNOPSIS gcloud dns record-sets import RECORDS_FILE --zone=ZONE, -z ZONE - [--delete-all-existing] [--replace-origin-ns] [--zone-file-format] - [GCLOUD_WIDE_FLAG ...] + [--delete-all-existing] [--location=LOCATION] [--replace-origin-ns] + [--zone-file-format] [GCLOUD_WIDE_FLAG ...] DESCRIPTION This command imports record-sets contained within the specified record-sets @@ -47,6 +47,11 @@ OPTIONAL FLAGS Indicates that all existing record-sets should be deleted before importing the record-sets in the records-file. + --location=LOCATION + Specifies the desired service location the request is sent to. Defaults + to Cloud DNS global service. Use --location=global if you want to + target the global service. + --replace-origin-ns Indicates that NS records for the origin of a zone should be imported if defined diff --git a/gcloud/dns/record-sets/list b/gcloud/dns/record-sets/list index c253bfc8b..ae7656910 100644 --- a/gcloud/dns/record-sets/list +++ b/gcloud/dns/record-sets/list @@ -3,7 +3,7 @@ NAME managed-zone SYNOPSIS - gcloud dns record-sets list --zone=ZONE, -z ZONE + gcloud dns record-sets list --zone=ZONE, -z ZONE [--location=LOCATION] [--name=NAME : --type=TYPE] [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] @@ -35,6 +35,11 @@ REQUIRED FLAGS Name of the managed zone whose record sets you want to manage. FLAGS + --location=LOCATION + Specifies the desired service location the request is sent to. Defaults + to Cloud DNS global service. Use --location=global if you want to + target the global service. + --name=NAME Only list record-sets with this exact domain name. diff --git a/gcloud/dns/record-sets/update b/gcloud/dns/record-sets/update index d565f920d..3a6ea4e4f 100644 --- a/gcloud/dns/record-sets/update +++ b/gcloud/dns/record-sets/update @@ -9,8 +9,8 @@ SYNOPSIS --routing-policy-backup-data-type=ROUTING_POLICY_BACKUP_DATA_TYPE --routing-policy-primary-data=ROUTING_POLICY_PRIMARY_DATA : --backup-data-trickle-ratio=BACKUP_DATA_TRICKLE_RATIO]) - : --enable-geo-fencing --enable-health-checking]) [--ttl=TTL] - [GCLOUD_WIDE_FLAG ...] + : --enable-geo-fencing --enable-health-checking]) + [--location=LOCATION] [--ttl=TTL] [GCLOUD_WIDE_FLAG ...] DESCRIPTION This command updates a record-set contained within the specified @@ -23,6 +23,14 @@ EXAMPLES $ gcloud dns record-sets update foo.bar.com. \ --rrdatas=1.2.3.4,9.8.7.6 --type=A --ttl=60 --zone=my_zone + To update a record-set with dnsName foo.bar.com., record type A to have + rrdata [1.2.3.4, 9.8.7.6] and ttl 60 in my_zone that is located in + us-east1-a, run: + + $ gcloud dns record-sets update foo.bar.com. \ + --rrdatas=1.2.3.4,9.8.7.6 --type=A --ttl=60 --zone=my_zone \ + --location=us-east1-a + POSITIONAL ARGUMENTS DNS_NAME DNS or domain name of the record-set. @@ -121,6 +129,11 @@ REQUIRED FLAGS targets even when the primary targets are healthy. OPTIONAL FLAGS + --location=LOCATION + Specifies the desired service location the request is sent to. Defaults + to Cloud DNS global service. Use --location=global if you want to + target the global service. + --ttl=TTL TTL (time to live) for the record-set. diff --git a/gcloud/dns/response-policies/create b/gcloud/dns/response-policies/create index b7795cdf1..365a5a274 100644 --- a/gcloud/dns/response-policies/create +++ b/gcloud/dns/response-policies/create @@ -4,7 +4,8 @@ NAME SYNOPSIS gcloud dns response-policies create RESPONSE_POLICIES - --description=DESCRIPTION [--networks=[NETWORKS,...]] + --description=DESCRIPTION [--gkeclusters=[GKECLUSTERS,...]] + [--location=LOCATION] [--networks=[NETWORKS,...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -48,6 +49,15 @@ REQUIRED FLAGS A description of the response policy. OPTIONAL FLAGS + --gkeclusters=[GKECLUSTERS,...] + The comma-separated list of GKE cluster names to associate with the + response policy. + + --location=LOCATION + Specifies the desired service location the request is sent to. Defaults + to Cloud DNS global service. Use --location=global if you want to + target the global service. + --networks=[NETWORKS,...] The comma-separated list of network names to associate with the response policy. diff --git a/gcloud/dns/response-policies/delete b/gcloud/dns/response-policies/delete index a8134bbec..181408734 100644 --- a/gcloud/dns/response-policies/delete +++ b/gcloud/dns/response-policies/delete @@ -2,7 +2,7 @@ NAME gcloud dns response-policies delete - deletes a Cloud DNS response policy SYNOPSIS - gcloud dns response-policies delete RESPONSE_POLICIES + gcloud dns response-policies delete RESPONSE_POLICIES [--location=LOCATION] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -29,6 +29,12 @@ POSITIONAL ARGUMENTS response_policy. To set the response-policy attribute: ▸ provide the argument response_policies on the command line. +FLAGS + --location=LOCATION + Specifies the desired service location the request is sent to. Defaults + to Cloud DNS global service. Use --location=global if you want to + target the global service. + 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/dns/response-policies/describe b/gcloud/dns/response-policies/describe index 82ece8b5f..18b60c2ad 100644 --- a/gcloud/dns/response-policies/describe +++ b/gcloud/dns/response-policies/describe @@ -4,7 +4,7 @@ NAME SYNOPSIS gcloud dns response-policies describe RESPONSE_POLICIES - [GCLOUD_WIDE_FLAG ...] + [--location=LOCATION] [GCLOUD_WIDE_FLAG ...] DESCRIPTION This command describes details of a Cloud DNS response policy. @@ -30,6 +30,12 @@ POSITIONAL ARGUMENTS response_policy. To set the response-policy attribute: ▸ provide the argument response_policies on the command line. +FLAGS + --location=LOCATION + Specifies the desired service location the request is sent to. Defaults + to Cloud DNS global service. Use --location=global if you want to + target the global service. + 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/dns/response-policies/list b/gcloud/dns/response-policies/list index ed4b41d38..0f99bb797 100644 --- a/gcloud/dns/response-policies/list +++ b/gcloud/dns/response-policies/list @@ -3,15 +3,21 @@ NAME response policies in a given project SYNOPSIS - gcloud dns response-policies list [--filter=EXPRESSION] [--limit=LIMIT] - [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] - [GCLOUD_WIDE_FLAG ...] + gcloud dns response-policies list [--location=LOCATION] + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] EXAMPLES To list response policies in Global Cloud DNS server (default), run: $ gcloud dns response-policies list +FLAGS + --location=LOCATION + Specifies the desired service location the request is sent to. Defaults + to Cloud DNS global service. Use --location=global if you want to + target the global service. + LIST COMMAND FLAGS --filter=EXPRESSION Apply a Boolean filter EXPRESSION to each resource item to be listed. diff --git a/gcloud/dns/response-policies/rules/create b/gcloud/dns/response-policies/rules/create index 412b3a509..3b05479d6 100644 --- a/gcloud/dns/response-policies/rules/create +++ b/gcloud/dns/response-policies/rules/create @@ -6,7 +6,8 @@ SYNOPSIS gcloud dns response-policies rules create (RESPONSE_POLICY_RULE : --response-policy=RESPONSE_POLICY) --dns-name=DNS_NAME [--behavior=BEHAVIOR] - [--local-data=[LOCAL_DATA,...]] [GCLOUD_WIDE_FLAG ...] + [--local-data=[LOCAL_DATA,...]] [--location=LOCATION] + [GCLOUD_WIDE_FLAG ...] EXAMPLES To create a new response policy rule with local data rrsets, run: @@ -89,6 +90,11 @@ OPTIONAL FLAGS rrdatas The list of datas for this record, split by "|". + --location=LOCATION + Specifies the desired service location the request is sent to. Defaults + to Cloud DNS global service. Use --location=global if you want to + target the global service. + 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/dns/response-policies/rules/delete b/gcloud/dns/response-policies/rules/delete index 091931844..f410193e1 100644 --- a/gcloud/dns/response-policies/rules/delete +++ b/gcloud/dns/response-policies/rules/delete @@ -5,7 +5,7 @@ NAME SYNOPSIS gcloud dns response-policies rules delete (RESPONSE_POLICY_RULE : --response-policy=RESPONSE_POLICY) - [GCLOUD_WIDE_FLAG ...] + [--location=LOCATION] [GCLOUD_WIDE_FLAG ...] EXAMPLES To delete a response policy rule, run: @@ -39,6 +39,12 @@ POSITIONAL ARGUMENTS with a fully specified name; ▸ provide the argument --response-policy on the command line. +FLAGS + --location=LOCATION + Specifies the desired service location the request is sent to. Defaults + to Cloud DNS global service. Use --location=global if you want to + target the global service. + 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/dns/response-policies/rules/describe b/gcloud/dns/response-policies/rules/describe index 5feb5f506..fc63cd445 100644 --- a/gcloud/dns/response-policies/rules/describe +++ b/gcloud/dns/response-policies/rules/describe @@ -5,7 +5,7 @@ NAME SYNOPSIS gcloud dns response-policies rules describe (RESPONSE_POLICY_RULE : --response-policy=RESPONSE_POLICY) - [GCLOUD_WIDE_FLAG ...] + [--location=LOCATION] [GCLOUD_WIDE_FLAG ...] EXAMPLES To show details about a response policy rule, run: @@ -39,6 +39,12 @@ POSITIONAL ARGUMENTS with a fully specified name; ▸ provide the argument --response-policy on the command line. +FLAGS + --location=LOCATION + Specifies the desired service location the request is sent to. Defaults + to Cloud DNS global service. Use --location=global if you want to + target the global service. + 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/dns/response-policies/rules/list b/gcloud/dns/response-policies/rules/list index 03343da61..d114b9896 100644 --- a/gcloud/dns/response-policies/rules/list +++ b/gcloud/dns/response-policies/rules/list @@ -4,8 +4,9 @@ NAME SYNOPSIS gcloud dns response-policies rules list RESPONSE_POLICIES - [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] - [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + [--location=LOCATION] [--filter=EXPRESSION] [--limit=LIMIT] + [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [GCLOUD_WIDE_FLAG ...] EXAMPLES To list response policie rules in Global Cloud DNS server (default), run: @@ -27,6 +28,12 @@ POSITIONAL ARGUMENTS response_policy. To set the response-policy attribute: ▸ provide the argument response_policies on the command line. +FLAGS + --location=LOCATION + Specifies the desired service location the request is sent to. Defaults + to Cloud DNS global service. Use --location=global if you want to + target the global service. + LIST COMMAND FLAGS --filter=EXPRESSION Apply a Boolean filter EXPRESSION to each resource item to be listed. diff --git a/gcloud/dns/response-policies/rules/update b/gcloud/dns/response-policies/rules/update index 22bfef00d..6f143b9f9 100644 --- a/gcloud/dns/response-policies/rules/update +++ b/gcloud/dns/response-policies/rules/update @@ -6,7 +6,8 @@ SYNOPSIS gcloud dns response-policies rules update (RESPONSE_POLICY_RULE : --response-policy=RESPONSE_POLICY) [--behavior=BEHAVIOR] [--dns-name=DNS_NAME] - [--local-data=[LOCAL_DATA,...]] [GCLOUD_WIDE_FLAG ...] + [--local-data=[LOCAL_DATA,...]] [--location=LOCATION] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION This command updates a new Cloud DNS response policy rule. @@ -87,6 +88,11 @@ FLAGS rrdatas The list of datas for this record, split by "|". + --location=LOCATION + Specifies the desired service location the request is sent to. Defaults + to Cloud DNS global service. Use --location=global if you want to + target the global service. + 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/dns/response-policies/update b/gcloud/dns/response-policies/update index 3e0cbaa86..bc0919abf 100644 --- a/gcloud/dns/response-policies/update +++ b/gcloud/dns/response-policies/update @@ -3,7 +3,8 @@ NAME SYNOPSIS gcloud dns response-policies update RESPONSE_POLICIES - [--description=DESCRIPTION] [--networks=[NETWORKS,...]] + [--description=DESCRIPTION] [--gkeclusters=[GKECLUSTERS,...]] + [--location=LOCATION] [--networks=[NETWORKS,...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -47,6 +48,15 @@ FLAGS --description=DESCRIPTION A description of the response policy. + --gkeclusters=[GKECLUSTERS,...] + The comma-separated list of GKE cluster names to associate with the + response policy. + + --location=LOCATION + Specifies the desired service location the request is sent to. Defaults + to Cloud DNS global service. Use --location=global if you want to + target the global service. + --networks=[NETWORKS,...] The comma-separated list of network names to associate with the response policy. diff --git a/gcloud/spanner/databases/create b/gcloud/spanner/databases/create index 8a562b559..59522042f 100644 --- a/gcloud/spanner/databases/create +++ b/gcloud/spanner/databases/create @@ -77,7 +77,8 @@ FLAGS is an error in any statement, the database is not created. This option is not supported for the PostgreSQL dialect. Full DDL specification is at https://cloud.google.com/spanner/docs/data-definition-language. If - --ddl_file is set, --ddl is ignored. + --ddl_file is set, --ddl is ignored. One line comments starting with -- + are ignored. Key resource - Cloud KMS key to be used to create the Cloud Spanner database. The arguments in this group can be used to specify the diff --git a/gcloud/spanner/databases/ddl/update b/gcloud/spanner/databases/ddl/update index f557f57fb..7cbdec087 100644 --- a/gcloud/spanner/databases/ddl/update +++ b/gcloud/spanner/databases/ddl/update @@ -58,7 +58,8 @@ FLAGS Path of a file containing semi-colon separated DDL (data definition language) statements to run inside the database. If a statement fails, all subsequent statements in the batch are automatically cancelled. If - --ddl_file is set, --ddl is ignored. + --ddl_file is set, --ddl is ignored. One line comments starting with -- + are ignored. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account,