diff --git a/gcloud/_version b/gcloud/_version index 92da9dc0e..e4a10ac42 100644 --- a/gcloud/_version +++ b/gcloud/_version @@ -1,7 +1,7 @@ -Google Cloud SDK 399.0.0 -alpha 2022.08.19 -beta 2022.08.19 +Google Cloud SDK 400.0.0 +alpha 2022.08.26 +beta 2022.08.26 bq 2.0.75 -core 2022.08.19 +core 2022.08.26 gcloud-crc32c 1.0.0 gsutil 5.12 diff --git a/gcloud/alpha/ai/endpoints/deploy-model b/gcloud/alpha/ai/endpoints/deploy-model index b86053a70..719b4e4b0 100644 --- a/gcloud/alpha/ai/endpoints/deploy-model +++ b/gcloud/alpha/ai/endpoints/deploy-model @@ -12,7 +12,10 @@ SYNOPSIS [--max-replica-count=MAX_REPLICA_COUNT] [--min-replica-count=MIN_REPLICA_COUNT] [--service-account=SERVICE_ACCOUNT] - [--traffic-split=[DEPLOYED_MODEL_ID=VALUE,...]] [GCLOUD_WIDE_FLAG ...] + [--traffic-split=[DEPLOYED_MODEL_ID=VALUE,...]] + [--shared-resources=SHARED_RESOURCES + : --shared-resources-region=SHARED_RESOURCES_REGION] + [GCLOUD_WIDE_FLAG ...] EXAMPLES To deploy a model 456 to an endpoint 123 under project example in region @@ -130,6 +133,35 @@ OPTIONAL FLAGS --traffic-split=[DEPLOYED_MODEL_ID=VALUE,...] List of pairs of deployed model id and value to set as traffic split. + Deployment resource pool resource - The deployment resource pool to + co-host a model on. 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 --shared-resources on the command line with a + fully specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + --shared-resources=SHARED_RESOURCES + ID of the deployment_resource_pool or fully qualified identifier for + the deployment_resource_pool. To set the name attribute: + ▸ provide the argument --shared-resources on the command line. + + This flag argument must be specified if any of the other arguments in + this group are specified. + + --shared-resources-region=SHARED_RESOURCES_REGION + Cloud region for the deployment_resource_pool. To set the region + attribute: + ▸ provide the argument --shared-resources on the command line with + a fully specified name; + ▸ provide the argument --shared-resources-region on the command + line; + ▸ provide the argument --region on the command line; + ▸ set the property ai/region; + ▸ choose one from the prompted list of available regions. + GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, diff --git a/gcloud/alpha/asset/help b/gcloud/alpha/asset/help index e3be580fa..9ac4e846a 100644 --- a/gcloud/alpha/asset/help +++ b/gcloud/alpha/asset/help @@ -44,7 +44,7 @@ COMMANDS (ALPHA) List the Cloud assets. query - (ALPHA) Query the CloudAssets. + (ALPHA) Query the Cloud assets. NOTES This command is currently in alpha and might change without notice. If this diff --git a/gcloud/alpha/asset/query b/gcloud/alpha/asset/query index 217a6ca32..6b1cbb954 100644 --- a/gcloud/alpha/asset/query +++ b/gcloud/alpha/asset/query @@ -1,12 +1,16 @@ NAME - gcloud alpha asset query - query the CloudAssets + gcloud alpha asset query - query the Cloud assets SYNOPSIS gcloud alpha asset query (--folder=FOLDER_ID | --organization=ORGANIZATION_ID - | --project=PROJECT_ID) [--job-reference=JOB_REFERENCE] - [--page-size=PAGE_SIZE] [--page-token=PAGE_TOKEN] - [--statement=STATEMENT] [--timeout=TIMEOUT] [GCLOUD_WIDE_FLAG ...] + | --project=PROJECT_ID) + (--job-reference=JOB_REFERENCE | --statement=STATEMENT) + [--page-size=PAGE_SIZE] [--page-token=PAGE_TOKEN] [--timeout=TIMEOUT] + [--snapshot-time=SNAPSHOT_TIME + | [--start-time=START_TIME : --end-time=END_TIME]] + [--write-disposition=WRITE_DISPOSITION [--bigquery-table=BIGQUERY_TABLE + : --bigquery-dataset=BIGQUERY_DATASET]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Issue an analytical query on Cloud assets using BigQuery Standard @@ -47,26 +51,97 @@ REQUIRED FLAGS and billing. To specify a different project for quota and billing, use --billing-project or billing/quota_project property. -OPTIONAL FLAGS - --job-reference=JOB_REFERENCE - Reference to the query job, which is from the previous call. + The query or job reference of the query request. + Exactly one of these must be specified: + + --job-reference=JOB_REFERENCE + Reference to the query job, which is from the previous call. + + --statement=STATEMENT + A BigQuery Standard SQL compatible statement. If the query execution + finishes within timeout and there is no pagination, the full query + results will be returned. Otherwise, pass job_reference from previous + call as --job-referrence to obtain the full results. + +OPTIONAL FLAGS --page-size=PAGE_SIZE - The maximum number of rows to return in the results. Other than that, - one page is also limited to 10 MB. + The maximum number of rows to return in the results. One page is also + limited to 10 MB. --page-token=PAGE_TOKEN A page token received from previous call. - --statement=STATEMENT - A BigQuery Standard SQL compatible statement. If the query - executionfinishes within timeout and there is no pagination, the full - queryresults will be returned. Otherwise, pass job_reference from - previous call as --job-referrence to obtain the full results. - --timeout=TIMEOUT - Maximum amount of time that the client is willing to wait for the query - to complete. + Maximum amount of time that the client will wait for the query to + complete. + + Specifies what time period or point in time to query asset metadata at. + + At most one of these can be specified: + + --snapshot-time=SNAPSHOT_TIME + Timestamp to take a snapshot on assets. This can only be a current or + past time. If not specified, the current time will be used. Due to + delays in resource data collection and indexing, there is a volatile + window during which running the same query at different times may + return different results. See $ gcloud topic datetimes for + information on time formats. + + Specifies what time period or point in time to query asset metadata at. + + --start-time=START_TIME + Start time of the time window (inclusive) for the asset history. + Must be after the current time minus 35 days. See $ gcloud topic + datetimes for information on time formats. + + This flag argument must be specified if any of the other arguments + in this group are specified. + + --end-time=END_TIME + End time of the time window (exclusive) for the asset history. + Defaults to current time if not specified. See $ gcloud topic + datetimes for information on time formats. + + The BigQuery destination for query system. + + --write-disposition=WRITE_DISPOSITION + Specifies the action that occurs if the destination table or + partition already exists. WRITE_DISPOSITION must be one of: + + write-append + AIf the table or partition already exists, BigQuery appends the + data to the table or the latest partition. + write-empty + If the table already exists and contains data, an error is + returned. + write-truncate + If the table or partition already exists, BigQuery overwrites the + entire table or all the partition's data. + + Table resource - The bigquery-table for the export. 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 --bigquery-table on the command line with a + fully specified name; + ▸ provide the argument --project on the command line; + ▸ set the property core/project. + + --bigquery-table=BIGQUERY_TABLE + ID of the table or fully qualified identifier for the table. To set + the table attribute: + ▫ provide the argument --bigquery-table on the command line. + + This flag argument must be specified if any of the other arguments + in this group are specified. + + --bigquery-dataset=BIGQUERY_DATASET + The id of the BigQuery dataset. To set the bigquery-dataset + attribute: + ▫ provide the argument --bigquery-table on the command line with + a fully specified name; + ▫ provide the argument --bigquery-dataset on the command line. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, @@ -80,5 +155,7 @@ 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. + access allowlist. This variant is also available: + + $ gcloud beta asset query diff --git a/gcloud/alpha/batch/help b/gcloud/alpha/batch/help index bd1b9e7c0..6b07f0ea7 100644 --- a/gcloud/alpha/batch/help +++ b/gcloud/alpha/batch/help @@ -5,7 +5,15 @@ SYNOPSIS gcloud alpha batch GROUP [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) Manage Batch resources. + (ALPHA) The gcloud batch command group lets you submit Batch jobs and + manipulate Batch jobs and tasks. + + With Batch, you can utilize the fully managed service to schedule, queue, + and execute batch jobs on Google's infrastructure. + + For more information about Batch, see the Batch overview + (https://cloud.google.com/batch) and the Batch documentation + (https://cloud.google.com/batch/docs/). GCLOUD WIDE FLAGS These flags are available to all commands: --help. diff --git a/gcloud/alpha/batch/jobs/help b/gcloud/alpha/batch/jobs/help index 56b052c52..82701c183 100644 --- a/gcloud/alpha/batch/jobs/help +++ b/gcloud/alpha/batch/jobs/help @@ -5,7 +5,15 @@ SYNOPSIS gcloud alpha batch jobs COMMAND [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) Manage Batch job resources. + (ALPHA) The gcloud batch jobs command group lets you submit, describe, list + and delete Batch jobs. + + With Batch, you can utilize the fully managed service to schedule, queue, + and execute batch jobs on Google's infrastructure. + + For more information about Batch, see the Batch overview + (https://cloud.google.com/batch) and the Batch documentation + (https://cloud.google.com/batch/docs/). GCLOUD WIDE FLAGS These flags are available to all commands: --help. diff --git a/gcloud/alpha/batch/tasks/help b/gcloud/alpha/batch/tasks/help index 8253e670e..0335add8f 100644 --- a/gcloud/alpha/batch/tasks/help +++ b/gcloud/alpha/batch/tasks/help @@ -5,7 +5,15 @@ SYNOPSIS gcloud alpha batch tasks COMMAND [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) Manage Batch task resources. + (ALPHA) The gcloud batch tasks command group lets you describe and list + Batch tasks. + + With Batch, you can utilize the fully managed service to schedule, queue, + and execute batch jobs on Google's infrastructure. + + For more information about Batch, see the Batch overview + (https://cloud.google.com/batch) and the Batch documentation + (https://cloud.google.com/batch/docs/). GCLOUD WIDE FLAGS These flags are available to all commands: --help. diff --git a/gcloud/alpha/builds/triggers/create/bitbucketserver b/gcloud/alpha/builds/triggers/create/bitbucketserver index ce8a99c3d..f92312d7e 100644 --- a/gcloud/alpha/builds/triggers/create/bitbucketserver +++ b/gcloud/alpha/builds/triggers/create/bitbucketserver @@ -216,5 +216,7 @@ 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. + access allowlist. This variant is also available: + + $ gcloud beta builds triggers create bitbucketserver diff --git a/gcloud/alpha/builds/triggers/create/gitlab-enterprise b/gcloud/alpha/builds/triggers/create/gitlab-enterprise index e46bb92f5..cb0a709de 100644 --- a/gcloud/alpha/builds/triggers/create/gitlab-enterprise +++ b/gcloud/alpha/builds/triggers/create/gitlab-enterprise @@ -215,5 +215,7 @@ 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. + access allowlist. This variant is also available: + + $ gcloud beta builds triggers create gitlab-enterprise diff --git a/gcloud/alpha/builds/triggers/create/manual b/gcloud/alpha/builds/triggers/create/manual index a6cab8dec..dd2569381 100644 --- a/gcloud/alpha/builds/triggers/create/manual +++ b/gcloud/alpha/builds/triggers/create/manual @@ -157,5 +157,7 @@ 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. + access allowlist. This variant is also available: + + $ gcloud beta builds triggers create manual diff --git a/gcloud/alpha/builds/triggers/create/pubsub b/gcloud/alpha/builds/triggers/create/pubsub index 19a8f1aee..2787c7e33 100644 --- a/gcloud/alpha/builds/triggers/create/pubsub +++ b/gcloud/alpha/builds/triggers/create/pubsub @@ -167,5 +167,7 @@ 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. + access allowlist. This variant is also available: + + $ gcloud beta builds triggers create pubsub diff --git a/gcloud/alpha/builds/triggers/create/webhook b/gcloud/alpha/builds/triggers/create/webhook index 5d747e483..b8e096476 100644 --- a/gcloud/alpha/builds/triggers/create/webhook +++ b/gcloud/alpha/builds/triggers/create/webhook @@ -170,5 +170,7 @@ 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. + access allowlist. This variant is also available: + + $ gcloud beta builds triggers create webhook diff --git a/gcloud/alpha/compute/commitments/create b/gcloud/alpha/compute/commitments/create index 16543ade0..cdf7aa50d 100644 --- a/gcloud/alpha/compute/commitments/create +++ b/gcloud/alpha/compute/commitments/create @@ -163,10 +163,10 @@ OPTIONAL FLAGS The size of the local SSD in base-2 GB. --machine-type=MACHINE_TYPE - The type of machine (name only) which has a fixed number of vCPUs - and a fixed amount of memory. This also includes specifying - custom machine type following - custom-number_of_CPUs-amount_of_memory pattern, e.g. + The type of machine (name only) that has a fixed number of vCPUs + and a fixed amount of memory. You can also specify a custom + machine type by using the pattern + custom-number_of_CPUs-amount_of_memory-for example, custom-32-29440. --maintenance-interval=MAINTENANCE_INTERVAL diff --git a/gcloud/alpha/compute/firewall-rules/create b/gcloud/alpha/compute/firewall-rules/create index dc0867911..419f07f7f 100644 --- a/gcloud/alpha/compute/firewall-rules/create +++ b/gcloud/alpha/compute/firewall-rules/create @@ -103,9 +103,8 @@ OPTIONAL FLAGS --direction=DIRECTION If direction is NOT specified, then default is to apply on incoming - traffic. For incoming traffic, it is NOT supported to specify - destination-ranges; For outbound traffic, it is NOT supported to - specify source-ranges or source-tags. + traffic. For outbound traffic, it is NOT supported to specify + source-tags. For convenience, 'IN' can be used to represent ingress direction and 'OUT' can be used to represent egress direction. diff --git a/gcloud/alpha/compute/firewall-rules/migrate b/gcloud/alpha/compute/firewall-rules/migrate index 23d2e9cf0..999959305 100644 --- a/gcloud/alpha/compute/firewall-rules/migrate +++ b/gcloud/alpha/compute/firewall-rules/migrate @@ -6,8 +6,7 @@ SYNOPSIS gcloud alpha compute firewall-rules migrate --source-network=SOURCE_NETWORK (--export-tag-mapping | --target-firewall-policy=TARGET_FIREWALL_POLICY) - [--disable-logging] [--tag-mapping-file=TAG_MAPPING_FILE] - [GCLOUD_WIDE_FLAG ...] + [--tag-mapping-file=TAG_MAPPING_FILE] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) gcloud alpha compute firewall-rules migrate is used to create a new @@ -38,12 +37,9 @@ REQUIRED FLAGS result. OPTIONAL FLAGS - --disable-logging - If set, migration tool will not migrate logging config. This is a - workaround to use before Network Firewall Policies support logging. - --tag-mapping-file=TAG_MAPPING_FILE - Path to a JSON file with legacy to secure tag mapping. + Path to a JSON file with legacy tags and service accounts to secure + tags mapping. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/alpha/compute/future-reservations/create b/gcloud/alpha/compute/future-reservations/create index 2921e35df..3240b56df 100644 --- a/gcloud/alpha/compute/future-reservations/create +++ b/gcloud/alpha/compute/future-reservations/create @@ -5,11 +5,13 @@ NAME SYNOPSIS gcloud alpha compute future-reservations create FUTURE_RESERVATION --total-count=TOTAL_COUNT - (--machine-type=MACHINE_TYPE : --accelerator=[count=COUNT],[type=TYPE] + (--source-instance-template=SOURCE_INSTANCE_TEMPLATE + | [--machine-type=MACHINE_TYPE + : --accelerator=[count=COUNT],[type=TYPE] --local-ssd=[interface=INTERFACE],[size=SIZE] --maintenance-freeze-duration=MAINTENANCE_FREEZE_DURATION --maintenance-interval=MAINTENANCE_INTERVAL - --min-cpu-platform=MIN_CPU_PLATFORM) + --min-cpu-platform=MIN_CPU_PLATFORM]) (--start-time=START_TIME (--duration=DURATION | --end-time=END_TIME)) [--description=DESCRIPTION] [--name-prefix=NAME_PREFIX] [--planning-status=PLANNING_STATUS] [--zone=ZONE] @@ -37,60 +39,71 @@ REQUIRED FLAGS The total number of instances for which capacity assurance is requested at a future time period. - Manage the specific SKU reservation properties. + Manage the instance properties for the Specific SKU reservation. You must + either provide a source instance template or define the instance + properties. - This must be specified. + Exactly one of these must be specified: - --machine-type=MACHINE_TYPE - The type of machine (name only) which has a fixed number of vCPUs and - a fixed amount of memory. This also includes specifying custom - machine type following custom-number_of_CPUs-amount_of_memory - pattern, e.g. custom-32-29440. + --source-instance-template=SOURCE_INSTANCE_TEMPLATE + The url of the instance template that will be used to populate the + fields of the reservation. Instance properties can not be defined in + addition to source instance template. - This flag argument must be specified if any of the other arguments in - this group are specified. + Define individual instance properties for the specific SKU reservation. - --accelerator=[count=COUNT],[type=TYPE] - Manage the configuration of the type and number of accelerator cards - attached. - count - The number of accelerators to attach to each instance in the - reservation. - type - The specific type (e.g. nvidia-tesla-k80 for nVidia Tesla K80) of - accelerator to attach to instances in the reservation. Use gcloud - compute accelerator-types list to learn about all available - accelerator types. + --machine-type=MACHINE_TYPE + The type of machine (name only) that has a fixed number of vCPUs + and a fixed amount of memory. You can also specify a custom machine + type by using the pattern + custom-number_of_CPUs-amount_of_memory-for example, + custom-32-29440. - --local-ssd=[interface=INTERFACE],[size=SIZE] - Manage the size and the interface of local SSD to use. See - https://cloud.google.com/compute/docs/disks/local-ssd for more - information. - interface - 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 may provide higher - performance. - size - The size of the local SSD in base-2 GB. + This flag argument must be specified if any of the other arguments + in this group are specified. - --maintenance-freeze-duration=MAINTENANCE_FREEZE_DURATION - Specifies the amount of hours after instance creation where the - instance won't be scheduled for maintenance, e.g. 4h, 2d6h. See $ - gcloud topic datetimes for information on duration formats. + --accelerator=[count=COUNT],[type=TYPE] + Manage the configuration of the type and number of accelerator + cards attached. + count + The number of accelerators to attach to each instance in the + reservation. + type + The specific type (e.g. nvidia-tesla-k80 for nVidia Tesla K80) + of accelerator to attach to instances in the reservation. Use + gcloud compute accelerator-types list to learn about all + available accelerator types. - --maintenance-interval=MAINTENANCE_INTERVAL - Specifies how infrastructure upgrades should be applied to the VM. - MAINTENANCE_INTERVAL must be (currently only one value is supported): + --local-ssd=[interface=INTERFACE],[size=SIZE] + Manage the size and the interface of local SSD to use. See + https://cloud.google.com/compute/docs/disks/local-ssd for more + information. + interface + 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 may provide + higher performance. + size + The size of the local SSD in base-2 GB. - PERIODIC - VMs receive infrastructure and hypervisor updates on a periodic - basis, minimizing the number of maintenance operations (live - migrations or terminations) on an individual VM. Security updates - will still be applied as soon as they are available. + --maintenance-freeze-duration=MAINTENANCE_FREEZE_DURATION + Specifies the amount of hours after instance creation where the + instance won't be scheduled for maintenance, e.g. 4h, 2d6h. See $ + gcloud topic datetimes for information on duration formats. - --min-cpu-platform=MIN_CPU_PLATFORM - Optional minimum CPU platform of the reservation to create. + --maintenance-interval=MAINTENANCE_INTERVAL + Specifies how infrastructure upgrades should be applied to the VM. + MAINTENANCE_INTERVAL must be (currently only one value is + supported): + + PERIODIC + VMs receive infrastructure and hypervisor updates on a periodic + basis, minimizing the number of maintenance operations (live + migrations or terminations) on an individual VM. Security + updates will still be applied as soon as they are available. + + --min-cpu-platform=MIN_CPU_PLATFORM + Optional minimum CPU platform of the reservation to create. Manage the time specific properties for requesting future capacity diff --git a/gcloud/alpha/compute/future-reservations/update b/gcloud/alpha/compute/future-reservations/update index 8f8c01665..43cf89596 100644 --- a/gcloud/alpha/compute/future-reservations/update +++ b/gcloud/alpha/compute/future-reservations/update @@ -97,10 +97,10 @@ FLAGS The size of the local SSD in base-2 GB. --machine-type=MACHINE_TYPE - The type of machine (name only) which has a fixed number of vCPUs and - a fixed amount of memory. This also includes specifying custom - machine type following custom-number_of_CPUs-amount_of_memory - pattern, e.g. custom-32-29440. + The type of machine (name only) that has a fixed number of vCPUs and + a fixed amount of memory. You can also specify a custom machine type + by using the pattern custom-number_of_CPUs-amount_of_memory-for + example, custom-32-29440. --maintenance-interval=MAINTENANCE_INTERVAL Specifies how infrastructure upgrades should be applied to the VM. diff --git a/gcloud/alpha/compute/reservations/create b/gcloud/alpha/compute/reservations/create index 0d6e68b3c..1dd7b1995 100644 --- a/gcloud/alpha/compute/reservations/create +++ b/gcloud/alpha/compute/reservations/create @@ -4,13 +4,15 @@ NAME SYNOPSIS gcloud alpha compute reservations create RESERVATION - (--machine-type=MACHINE_TYPE --vm-count=VM_COUNT + (--vm-count=VM_COUNT + (--source-instance-template=SOURCE_INSTANCE_TEMPLATE + | [--machine-type=MACHINE_TYPE : --accelerator=[count=COUNT],[type=TYPE] --local-ssd=[interface=INTERFACE],[size=SIZE] --maintenance-freeze-duration=MAINTENANCE_FREEZE_DURATION --maintenance-interval=MAINTENANCE_INTERVAL - --min-cpu-platform=MIN_CPU_PLATFORM - --require-specific-reservation --resource-policies=[KEY=VALUE,...]) + --min-cpu-platform=MIN_CPU_PLATFORM]) + : --require-specific-reservation --resource-policies=[KEY=VALUE,...]) [--description=DESCRIPTION] [--zone=ZONE] [--share-setting=SHARE_SETTING --share-with=SHARE_WITH,[SHARE_WITH,...]] [GCLOUD_WIDE_FLAG ...] @@ -30,19 +32,10 @@ POSITIONAL ARGUMENTS Name of the reservation to create. REQUIRED FLAGS - Manage the specific SKU reservation properties. + Manage the SpecificSKU reservation properties. This must be specified. - --machine-type=MACHINE_TYPE - The type of machine (name only) which has a fixed number of vCPUs and - a fixed amount of memory. This also includes specifying custom - machine type following custom-number_of_CPUs-amount_of_memory - pattern, e.g. custom-32-29440. - - This flag argument must be specified if any of the other arguments in - this group are specified. - --vm-count=VM_COUNT The number of VM instances that are allocated to this reservation. The value of this field must be an int in the range [1, 1000]. @@ -50,48 +43,6 @@ REQUIRED FLAGS This flag argument must be specified if any of the other arguments in this group are specified. - --accelerator=[count=COUNT],[type=TYPE] - Manage the configuration of the type and number of accelerator cards - attached. - count - The number of accelerators to attach to each instance in the - reservation. - type - The specific type (e.g. nvidia-tesla-k80 for nVidia Tesla K80) of - accelerator to attach to instances in the reservation. Use gcloud - compute accelerator-types list to learn about all available - accelerator types. - - --local-ssd=[interface=INTERFACE],[size=SIZE] - Manage the size and the interface of local SSD to use. See - https://cloud.google.com/compute/docs/disks/local-ssd for more - information. - interface - 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 may provide higher - performance. - size - The size of the local SSD in base-2 GB. - - --maintenance-freeze-duration=MAINTENANCE_FREEZE_DURATION - Specifies the amount of hours after instance creation where the - instance won't be scheduled for maintenance, e.g. 4h, 2d6h. See $ - gcloud topic datetimes for information on duration formats. - - --maintenance-interval=MAINTENANCE_INTERVAL - Specifies how infrastructure upgrades should be applied to the VM. - MAINTENANCE_INTERVAL must be (currently only one value is supported): - - PERIODIC - VMs receive infrastructure and hypervisor updates on a periodic - basis, minimizing the number of maintenance operations (live - migrations or terminations) on an individual VM. Security updates - will still be applied as soon as they are available. - - --min-cpu-platform=MIN_CPU_PLATFORM - Optional minimum CPU platform of the reservation to create. - --require-specific-reservation Indicates whether the reservation can be consumed by VMs with "any reservation" defined. If enabled, then only VMs that target this @@ -102,6 +53,72 @@ REQUIRED FLAGS Specify if this is reservation with resource policy. If you omit this flag, no resource policy will be added to this reservation. + Manage the instance properties for the SpecificSKU reservation. + + Exactly one of these must be specified: + + --source-instance-template=SOURCE_INSTANCE_TEMPLATE + The url of the instance template that will be used to populate the + fields of the reservation. Instance properties can not be defined + in addition to source instance template. + + Define the individual instance properties for the SpecificSKU + reservation. + + --machine-type=MACHINE_TYPE + The type of machine (name only) that has a fixed number of vCPUs + and a fixed amount of memory. You can also specify a custom + machine type by using the pattern + custom-number_of_CPUs-amount_of_memory-for example, + custom-32-29440. + + This flag argument must be specified if any of the other + arguments in this group are specified. + + --accelerator=[count=COUNT],[type=TYPE] + Manage the configuration of the type and number of accelerator + cards attached. + count + The number of accelerators to attach to each instance in the + reservation. + type + The specific type (e.g. nvidia-tesla-k80 for nVidia Tesla + K80) of accelerator to attach to instances in the + reservation. Use gcloud compute accelerator-types list to + learn about all available accelerator types. + + --local-ssd=[interface=INTERFACE],[size=SIZE] + Manage the size and the interface of local SSD to use. See + https://cloud.google.com/compute/docs/disks/local-ssd for more + information. + interface + 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 may provide + higher performance. + size + The size of the local SSD in base-2 GB. + + --maintenance-freeze-duration=MAINTENANCE_FREEZE_DURATION + Specifies the amount of hours after instance creation where the + instance won't be scheduled for maintenance, e.g. 4h, 2d6h. See $ + gcloud topic datetimes for information on duration formats. + + --maintenance-interval=MAINTENANCE_INTERVAL + Specifies how infrastructure upgrades should be applied to the + VM. MAINTENANCE_INTERVAL must be (currently only one value is + supported): + + PERIODIC + VMs receive infrastructure and hypervisor updates on a + periodic basis, minimizing the number of maintenance + operations (live migrations or terminations) on an individual + VM. Security updates will still be applied as soon as they + are available. + + --min-cpu-platform=MIN_CPU_PLATFORM + Optional minimum CPU platform of the reservation to create. + OPTIONAL FLAGS --description=DESCRIPTION An optional description of the reservation to create. diff --git a/gcloud/alpha/compute/sole-tenancy/node-groups/help b/gcloud/alpha/compute/sole-tenancy/node-groups/help index 69f87b8c8..cfc1d482c 100644 --- a/gcloud/alpha/compute/sole-tenancy/node-groups/help +++ b/gcloud/alpha/compute/sole-tenancy/node-groups/help @@ -44,6 +44,9 @@ COMMANDS set-iam-policy (ALPHA) Set the IAM policy for a Compute Engine node group. + simulate-maintenance-event + (ALPHA) Simulate maintenance of a Compute Engine node group. + update (ALPHA) Update a Compute Engine node group. diff --git a/gcloud/alpha/compute/sole-tenancy/node-groups/simulate-maintenance-event b/gcloud/alpha/compute/sole-tenancy/node-groups/simulate-maintenance-event new file mode 100644 index 000000000..859356a9b --- /dev/null +++ b/gcloud/alpha/compute/sole-tenancy/node-groups/simulate-maintenance-event @@ -0,0 +1,66 @@ +NAME + gcloud alpha compute sole-tenancy node-groups simulate-maintenance-event - + simulate maintenance of a Compute Engine node group + +SYNOPSIS + gcloud alpha compute sole-tenancy node-groups simulate-maintenance-event + NAME [--async] [--nodes=[NODE,...]] [--zone=ZONE] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Simulate maintenance of a Compute Engine node group. + +EXAMPLES + To simulate maintenance of a node group, run: + + $ gcloud alpha compute sole-tenancy node-groups \ + simulate-maintenance-event my-node-group \ + --nodes=example-template + +POSITIONAL ARGUMENTS + NAME + Name of the node group to operate on. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --nodes=[NODE,...] + The names of the nodes to simulate maintenance event. + + --zone=ZONE + Zone of the node group to operate on. If not specified and the + compute/zone property isn't set, you might be prompted to select a zone + (interactive mode only). + + To avoid prompting when this flag is omitted, you can set the + compute/zone property: + + $ gcloud config set compute/zone ZONE + + A list of zones can be fetched by running: + + $ gcloud compute zones list + + To unset the property, run: + + $ gcloud config unset compute/zone + + Alternatively, the zone can be stored in the environment variable + CLOUDSDK_COMPUTE_ZONE. + +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/config/help b/gcloud/alpha/config/help index 186cb4f4c..227a65ff2 100644 --- a/gcloud/alpha/config/help +++ b/gcloud/alpha/config/help @@ -335,8 +335,8 @@ AVAILABLE PROPERTIES Overrides API endpoint for gcloud genomics command group. gkemulticloud - Overrides API endpoint for gcloud container aws and gcloud - container azure command groups. + Overrides API endpoint for gcloud container aws, gcloud container + azure and gcloud container attached command groups. healthcare Overrides API endpoint for gcloud healthcare command group. @@ -639,6 +639,10 @@ AVAILABLE PROPERTIES If True, use the cluster's client certificate to authenticate to the cluster API server. + container_attached + location + Default Google Cloud location to use for Attached clusters. + container_aws location Default Google Cloud location to use for Anthos clusters on AWS. diff --git a/gcloud/alpha/config/list b/gcloud/alpha/config/list index 42e707c26..9d4535660 100644 --- a/gcloud/alpha/config/list +++ b/gcloud/alpha/config/list @@ -344,8 +344,8 @@ AVAILABLE PROPERTIES Overrides API endpoint for gcloud genomics command group. gkemulticloud - Overrides API endpoint for gcloud container aws and gcloud - container azure command groups. + Overrides API endpoint for gcloud container aws, gcloud container + azure and gcloud container attached command groups. healthcare Overrides API endpoint for gcloud healthcare command group. @@ -648,6 +648,10 @@ AVAILABLE PROPERTIES If True, use the cluster's client certificate to authenticate to the cluster API server. + container_attached + location + Default Google Cloud location to use for Attached clusters. + container_aws location Default Google Cloud location to use for Anthos clusters on AWS. diff --git a/gcloud/alpha/config/set b/gcloud/alpha/config/set index 33c9a15e1..628f494c1 100644 --- a/gcloud/alpha/config/set +++ b/gcloud/alpha/config/set @@ -353,8 +353,8 @@ AVAILABLE PROPERTIES Overrides API endpoint for gcloud genomics command group. gkemulticloud - Overrides API endpoint for gcloud container aws and gcloud - container azure command groups. + Overrides API endpoint for gcloud container aws, gcloud container + azure and gcloud container attached command groups. healthcare Overrides API endpoint for gcloud healthcare command group. @@ -657,6 +657,10 @@ AVAILABLE PROPERTIES If True, use the cluster's client certificate to authenticate to the cluster API server. + container_attached + location + Default Google Cloud location to use for Attached clusters. + container_aws location Default Google Cloud location to use for Anthos clusters on AWS. diff --git a/gcloud/alpha/config/unset b/gcloud/alpha/config/unset index 70b3ae0a8..4a228ad51 100644 --- a/gcloud/alpha/config/unset +++ b/gcloud/alpha/config/unset @@ -314,8 +314,8 @@ AVAILABLE PROPERTIES Overrides API endpoint for gcloud genomics command group. gkemulticloud - Overrides API endpoint for gcloud container aws and gcloud - container azure command groups. + Overrides API endpoint for gcloud container aws, gcloud container + azure and gcloud container attached command groups. healthcare Overrides API endpoint for gcloud healthcare command group. @@ -618,6 +618,10 @@ AVAILABLE PROPERTIES If True, use the cluster's client certificate to authenticate to the cluster API server. + container_attached + location + Default Google Cloud location to use for Attached clusters. + container_aws location Default Google Cloud location to use for Anthos clusters on AWS. diff --git a/gcloud/alpha/container/aws/clusters/create b/gcloud/alpha/container/aws/clusters/create index 7ae067848..8d6c38fb0 100644 --- a/gcloud/alpha/container/aws/clusters/create +++ b/gcloud/alpha/container/aws/clusters/create @@ -12,8 +12,9 @@ SYNOPSIS --pod-address-cidr-blocks=POD_ADDRESS_CIDR_BLOCKS --role-arn=ROLE_ARN --service-address-cidr-blocks=SERVICE_ADDRESS_CIDR_BLOCKS --subnet-ids=[SUBNET_ID,...] --vpc-id=VPC_ID - [--admin-users=USER,[USER,...]] [--async] - [--instance-placement=INSTANCE_PLACEMENT] + [--admin-users=USER,[USER,...]] + [--annotations=ANNOTATION,[ANNOTATION,...]] [--async] + [--description=DESCRIPTION] [--instance-placement=INSTANCE_PLACEMENT] [--instance-type=INSTANCE_TYPE] [--logging=COMPONENT,[COMPONENT,...]] [--main-volume-iops=MAIN_VOLUME_IOPS] [--main-volume-kms-key-arn=MAIN_VOLUME_KMS_KEY_ARN] @@ -72,8 +73,7 @@ POSITIONAL ARGUMENTS ▸ provide the argument cluster on the command line with a fully specified name; ▸ provide the argument --location on the command line; - ▸ set the property container_aws/location; - ▸ set the property aws/location (deprecated). + ▸ set the property container_aws/location. REQUIRED FLAGS --aws-region=AWS_REGION @@ -118,10 +118,16 @@ OPTIONAL FLAGS Users that can perform operations as a cluster administrator. If not specified, the value of property core/account is used. + --annotations=ANNOTATION,[ANNOTATION,...] + Annotations for the cluster. + --async Return immediately, without waiting for the operation in progress to complete. + --description=DESCRIPTION + Description for the cluster. + --instance-placement=INSTANCE_PLACEMENT Type of the tenancy. INSTANCE_PLACEMENT must be one of: dedicated, default, host. diff --git a/gcloud/alpha/container/aws/clusters/delete b/gcloud/alpha/container/aws/clusters/delete index 3fb975f8c..814222f04 100644 --- a/gcloud/alpha/container/aws/clusters/delete +++ b/gcloud/alpha/container/aws/clusters/delete @@ -40,8 +40,7 @@ POSITIONAL ARGUMENTS ▸ provide the argument cluster on the command line with a fully specified name; ▸ provide the argument --location on the command line; - ▸ set the property container_aws/location; - ▸ set the property aws/location (deprecated). + ▸ set the property container_aws/location. FLAGS --async diff --git a/gcloud/alpha/container/aws/clusters/describe b/gcloud/alpha/container/aws/clusters/describe index d79cb1535..454112f3b 100644 --- a/gcloud/alpha/container/aws/clusters/describe +++ b/gcloud/alpha/container/aws/clusters/describe @@ -40,8 +40,7 @@ POSITIONAL ARGUMENTS ▸ provide the argument cluster on the command line with a fully specified name; ▸ provide the argument --location on the command line; - ▸ set the property container_aws/location; - ▸ set the property aws/location (deprecated). + ▸ set the property container_aws/location. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/alpha/container/aws/clusters/get-credentials b/gcloud/alpha/container/aws/clusters/get-credentials index 240d0dd87..13ee464f4 100644 --- a/gcloud/alpha/container/aws/clusters/get-credentials +++ b/gcloud/alpha/container/aws/clusters/get-credentials @@ -66,8 +66,7 @@ POSITIONAL ARGUMENTS ▸ provide the argument cluster on the command line with a fully specified name; ▸ provide the argument --location on the command line; - ▸ set the property container_aws/location; - ▸ set the property aws/location (deprecated). + ▸ set the property container_aws/location. FLAGS --private-endpoint diff --git a/gcloud/alpha/container/aws/clusters/list b/gcloud/alpha/container/aws/clusters/list index ceb0d6350..5089462d9 100644 --- a/gcloud/alpha/container/aws/clusters/list +++ b/gcloud/alpha/container/aws/clusters/list @@ -21,8 +21,6 @@ FLAGS ◆ provide the argument --location on the command line with a fully specified name; ◆ set the property container_aws/location with a fully specified name; - ◆ set the property aws/location (deprecated) with a fully specified - name; ◆ provide the argument --project on the command line; ◆ set the property core/project. @@ -30,8 +28,7 @@ FLAGS ID of the location or fully qualified identifier for the location. To set the location attribute: ▸ provide the argument --location on the command line; - ▸ set the property container_aws/location; - ▸ set the property aws/location (deprecated). + ▸ set the property container_aws/location. LIST COMMAND FLAGS --filter=EXPRESSION diff --git a/gcloud/alpha/container/aws/clusters/update b/gcloud/alpha/container/aws/clusters/update index f08fe0c21..a9643f5cc 100644 --- a/gcloud/alpha/container/aws/clusters/update +++ b/gcloud/alpha/container/aws/clusters/update @@ -55,8 +55,7 @@ POSITIONAL ARGUMENTS ▸ provide the argument cluster on the command line with a fully specified name; ▸ provide the argument --location on the command line; - ▸ set the property container_aws/location; - ▸ set the property aws/location (deprecated). + ▸ set the property container_aws/location. FLAGS --admin-users=USER,[USER,...] diff --git a/gcloud/alpha/container/aws/get-server-config b/gcloud/alpha/container/aws/get-server-config index 247b7aed3..6074b2158 100644 --- a/gcloud/alpha/container/aws/get-server-config +++ b/gcloud/alpha/container/aws/get-server-config @@ -23,8 +23,6 @@ FLAGS ◆ provide the argument --location on the command line with a fully specified name; ◆ set the property container_aws/location with a fully specified name; - ◆ set the property aws/location (deprecated) with a fully specified - name; ◆ provide the argument --project on the command line; ◆ set the property core/project. @@ -32,8 +30,7 @@ FLAGS ID of the location or fully qualified identifier for the location. To set the location attribute: ▸ provide the argument --location on the command line; - ▸ set the property container_aws/location; - ▸ set the property aws/location (deprecated). + ▸ set the property container_aws/location. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/alpha/container/aws/node-pools/create b/gcloud/alpha/container/aws/node-pools/create index a2f0ee574..07c328956 100644 --- a/gcloud/alpha/container/aws/node-pools/create +++ b/gcloud/alpha/container/aws/node-pools/create @@ -67,8 +67,7 @@ POSITIONAL ARGUMENTS ▸ provide the argument node_pool on the command line with a fully specified name; ▸ provide the argument --location on the command line; - ▸ set the property container_aws/location; - ▸ set the property aws/location (deprecated). + ▸ set the property container_aws/location. REQUIRED FLAGS --config-encryption-kms-key-arn=CONFIG_ENCRYPTION_KMS_KEY_ARN diff --git a/gcloud/alpha/container/aws/node-pools/delete b/gcloud/alpha/container/aws/node-pools/delete index 3d167b68d..260a43ed0 100644 --- a/gcloud/alpha/container/aws/node-pools/delete +++ b/gcloud/alpha/container/aws/node-pools/delete @@ -49,8 +49,7 @@ POSITIONAL ARGUMENTS ▸ provide the argument node_pool on the command line with a fully specified name; ▸ provide the argument --location on the command line; - ▸ set the property container_aws/location; - ▸ set the property aws/location (deprecated). + ▸ set the property container_aws/location. FLAGS --async diff --git a/gcloud/alpha/container/aws/node-pools/describe b/gcloud/alpha/container/aws/node-pools/describe index 56b9f3741..f9f767f43 100644 --- a/gcloud/alpha/container/aws/node-pools/describe +++ b/gcloud/alpha/container/aws/node-pools/describe @@ -49,8 +49,7 @@ POSITIONAL ARGUMENTS ▸ provide the argument node_pool on the command line with a fully specified name; ▸ provide the argument --location on the command line; - ▸ set the property container_aws/location; - ▸ set the property aws/location (deprecated). + ▸ set the property container_aws/location. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/alpha/container/aws/node-pools/list b/gcloud/alpha/container/aws/node-pools/list index e105531f3..07e75827e 100644 --- a/gcloud/alpha/container/aws/node-pools/list +++ b/gcloud/alpha/container/aws/node-pools/list @@ -43,8 +43,7 @@ REQUIRED FLAGS ▸ provide the argument --cluster on the command line with a fully specified name; ▸ provide the argument --location on the command line; - ▸ set the property container_aws/location; - ▸ set the property aws/location (deprecated). + ▸ set the property container_aws/location. LIST COMMAND FLAGS --filter=EXPRESSION diff --git a/gcloud/alpha/container/aws/node-pools/update b/gcloud/alpha/container/aws/node-pools/update index 8bd1fca27..302e40c9c 100644 --- a/gcloud/alpha/container/aws/node-pools/update +++ b/gcloud/alpha/container/aws/node-pools/update @@ -61,8 +61,7 @@ POSITIONAL ARGUMENTS ▸ provide the argument node_pool on the command line with a fully specified name; ▸ provide the argument --location on the command line; - ▸ set the property container_aws/location; - ▸ set the property aws/location (deprecated). + ▸ set the property container_aws/location. FLAGS --async diff --git a/gcloud/alpha/container/aws/operations/describe b/gcloud/alpha/container/aws/operations/describe index 359f94df4..ec5eb26dc 100644 --- a/gcloud/alpha/container/aws/operations/describe +++ b/gcloud/alpha/container/aws/operations/describe @@ -40,8 +40,7 @@ POSITIONAL ARGUMENTS ▸ provide the argument operation_id on the command line with a fully specified name; ▸ provide the argument --location on the command line; - ▸ set the property container_aws/location; - ▸ set the property aws/location (deprecated). + ▸ set the property container_aws/location. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/alpha/container/aws/operations/list b/gcloud/alpha/container/aws/operations/list index dbb4dba67..aaac1aa28 100644 --- a/gcloud/alpha/container/aws/operations/list +++ b/gcloud/alpha/container/aws/operations/list @@ -22,8 +22,6 @@ FLAGS ◆ provide the argument --location on the command line with a fully specified name; ◆ set the property container_aws/location with a fully specified name; - ◆ set the property aws/location (deprecated) with a fully specified - name; ◆ provide the argument --project on the command line; ◆ set the property core/project. @@ -31,8 +29,7 @@ FLAGS ID of the location or fully qualified identifier for the location. To set the location attribute: ▸ provide the argument --location on the command line; - ▸ set the property container_aws/location; - ▸ set the property aws/location (deprecated). + ▸ set the property container_aws/location. LIST COMMAND FLAGS --filter=EXPRESSION diff --git a/gcloud/alpha/container/aws/operations/wait b/gcloud/alpha/container/aws/operations/wait index 3b105ce1d..1519a681a 100644 --- a/gcloud/alpha/container/aws/operations/wait +++ b/gcloud/alpha/container/aws/operations/wait @@ -41,8 +41,7 @@ POSITIONAL ARGUMENTS ▸ provide the argument operation_id on the command line with a fully specified name; ▸ provide the argument --location on the command line; - ▸ set the property container_aws/location; - ▸ set the property aws/location (deprecated). + ▸ set the property container_aws/location. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/alpha/container/azure/clients/create b/gcloud/alpha/container/azure/clients/create index 62c081dd8..d6b629bd2 100644 --- a/gcloud/alpha/container/azure/clients/create +++ b/gcloud/alpha/container/azure/clients/create @@ -41,8 +41,7 @@ POSITIONAL ARGUMENTS ▸ provide the argument client on the command line with a fully specified name; ▸ provide the argument --location on the command line; - ▸ set the property container_azure/location; - ▸ set the property azure/location (deprecated). + ▸ set the property container_azure/location. REQUIRED FLAGS --application-id=APP_ID diff --git a/gcloud/alpha/container/azure/clients/delete b/gcloud/alpha/container/azure/clients/delete index 07ab2e107..abef33c59 100644 --- a/gcloud/alpha/container/azure/clients/delete +++ b/gcloud/alpha/container/azure/clients/delete @@ -39,8 +39,7 @@ POSITIONAL ARGUMENTS ▸ provide the argument client on the command line with a fully specified name; ▸ provide the argument --location on the command line; - ▸ set the property container_azure/location; - ▸ set the property azure/location (deprecated). + ▸ set the property container_azure/location. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/alpha/container/azure/clients/describe b/gcloud/alpha/container/azure/clients/describe index 486823a94..638864097 100644 --- a/gcloud/alpha/container/azure/clients/describe +++ b/gcloud/alpha/container/azure/clients/describe @@ -39,8 +39,7 @@ POSITIONAL ARGUMENTS ▸ provide the argument client on the command line with a fully specified name; ▸ provide the argument --location on the command line; - ▸ set the property container_azure/location; - ▸ set the property azure/location (deprecated). + ▸ set the property container_azure/location. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/alpha/container/azure/clients/get-public-cert b/gcloud/alpha/container/azure/clients/get-public-cert index d9d8f1928..e7e12b7d1 100644 --- a/gcloud/alpha/container/azure/clients/get-public-cert +++ b/gcloud/alpha/container/azure/clients/get-public-cert @@ -47,8 +47,7 @@ POSITIONAL ARGUMENTS ▸ provide the argument client on the command line with a fully specified name; ▸ provide the argument --location on the command line; - ▸ set the property container_azure/location; - ▸ set the property azure/location (deprecated). + ▸ set the property container_azure/location. FLAGS --output-file=OUTPUT_FILE diff --git a/gcloud/alpha/container/azure/clients/list b/gcloud/alpha/container/azure/clients/list index 6cb40bd7f..c2f4b4963 100644 --- a/gcloud/alpha/container/azure/clients/list +++ b/gcloud/alpha/container/azure/clients/list @@ -23,8 +23,6 @@ FLAGS specified name; ◆ set the property container_azure/location with a fully specified name; - ◆ set the property azure/location (deprecated) with a fully specified - name; ◆ provide the argument --project on the command line; ◆ set the property core/project. @@ -32,8 +30,7 @@ FLAGS ID of the location or fully qualified identifier for the location. To set the location attribute: ▸ provide the argument --location on the command line; - ▸ set the property container_azure/location; - ▸ set the property azure/location (deprecated). + ▸ set the property container_azure/location. LIST COMMAND FLAGS --filter=EXPRESSION diff --git a/gcloud/alpha/container/azure/clusters/create b/gcloud/alpha/container/azure/clusters/create index f8123bc1f..b922e7a42 100644 --- a/gcloud/alpha/container/azure/clusters/create +++ b/gcloud/alpha/container/azure/clusters/create @@ -65,8 +65,7 @@ POSITIONAL ARGUMENTS ▸ provide the argument cluster on the command line with a fully specified name; ▸ provide the argument --location on the command line; - ▸ set the property container_azure/location; - ▸ set the property azure/location (deprecated). + ▸ set the property container_azure/location. REQUIRED FLAGS --azure-region=AZURE_REGION @@ -84,8 +83,7 @@ REQUIRED FLAGS ◆ provide the argument --client on the command line with a fully specified name; ◆ provide the argument --location on the command line; - ◆ set the property container_azure/location; - ◆ set the property azure/location (deprecated). + ◆ set the property container_azure/location. This must be specified. diff --git a/gcloud/alpha/container/azure/clusters/delete b/gcloud/alpha/container/azure/clusters/delete index 4eb78a932..2c85e13e4 100644 --- a/gcloud/alpha/container/azure/clusters/delete +++ b/gcloud/alpha/container/azure/clusters/delete @@ -40,8 +40,7 @@ POSITIONAL ARGUMENTS ▸ provide the argument cluster on the command line with a fully specified name; ▸ provide the argument --location on the command line; - ▸ set the property container_azure/location; - ▸ set the property azure/location (deprecated). + ▸ set the property container_azure/location. FLAGS --async diff --git a/gcloud/alpha/container/azure/clusters/describe b/gcloud/alpha/container/azure/clusters/describe index 21771c49e..8587f6237 100644 --- a/gcloud/alpha/container/azure/clusters/describe +++ b/gcloud/alpha/container/azure/clusters/describe @@ -40,8 +40,7 @@ POSITIONAL ARGUMENTS ▸ provide the argument cluster on the command line with a fully specified name; ▸ provide the argument --location on the command line; - ▸ set the property container_azure/location; - ▸ set the property azure/location (deprecated). + ▸ set the property container_azure/location. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/alpha/container/azure/clusters/get-credentials b/gcloud/alpha/container/azure/clusters/get-credentials index b2f352426..13421730a 100644 --- a/gcloud/alpha/container/azure/clusters/get-credentials +++ b/gcloud/alpha/container/azure/clusters/get-credentials @@ -66,8 +66,7 @@ POSITIONAL ARGUMENTS ▸ provide the argument cluster on the command line with a fully specified name; ▸ provide the argument --location on the command line; - ▸ set the property container_azure/location; - ▸ set the property azure/location (deprecated). + ▸ set the property container_azure/location. FLAGS --private-endpoint diff --git a/gcloud/alpha/container/azure/clusters/list b/gcloud/alpha/container/azure/clusters/list index 9eb515bcc..9ad39f3e5 100644 --- a/gcloud/alpha/container/azure/clusters/list +++ b/gcloud/alpha/container/azure/clusters/list @@ -23,8 +23,6 @@ FLAGS specified name; ◆ set the property container_azure/location with a fully specified name; - ◆ set the property azure/location (deprecated) with a fully specified - name; ◆ provide the argument --project on the command line; ◆ set the property core/project. @@ -32,8 +30,7 @@ FLAGS ID of the location or fully qualified identifier for the location. To set the location attribute: ▸ provide the argument --location on the command line; - ▸ set the property container_azure/location; - ▸ set the property azure/location (deprecated). + ▸ set the property container_azure/location. LIST COMMAND FLAGS --filter=EXPRESSION diff --git a/gcloud/alpha/container/azure/clusters/update b/gcloud/alpha/container/azure/clusters/update index b1241a1be..8fa3c01f2 100644 --- a/gcloud/alpha/container/azure/clusters/update +++ b/gcloud/alpha/container/azure/clusters/update @@ -45,8 +45,7 @@ POSITIONAL ARGUMENTS ▸ provide the argument cluster on the command line with a fully specified name; ▸ provide the argument --location on the command line; - ▸ set the property container_azure/location; - ▸ set the property azure/location (deprecated). + ▸ set the property container_azure/location. FLAGS Client resource - Azure client to use for cluster update. This represents @@ -59,8 +58,7 @@ FLAGS ◆ provide the argument --client on the command line with a fully specified name; ◆ provide the argument --location on the command line; - ◆ set the property container_azure/location; - ◆ set the property azure/location (deprecated). + ◆ set the property container_azure/location. --client=CLIENT ID of the client or fully qualified identifier for the client. To set diff --git a/gcloud/alpha/container/azure/get-server-config b/gcloud/alpha/container/azure/get-server-config index a1b25ca90..f74b1c665 100644 --- a/gcloud/alpha/container/azure/get-server-config +++ b/gcloud/alpha/container/azure/get-server-config @@ -24,8 +24,6 @@ FLAGS specified name; ◆ set the property container_azure/location with a fully specified name; - ◆ set the property azure/location (deprecated) with a fully specified - name; ◆ provide the argument --project on the command line; ◆ set the property core/project. @@ -33,8 +31,7 @@ FLAGS ID of the location or fully qualified identifier for the location. To set the location attribute: ▸ provide the argument --location on the command line; - ▸ set the property container_azure/location; - ▸ set the property azure/location (deprecated). + ▸ set the property container_azure/location. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/alpha/container/azure/node-pools/create b/gcloud/alpha/container/azure/node-pools/create index e830217e3..27ed88651 100644 --- a/gcloud/alpha/container/azure/node-pools/create +++ b/gcloud/alpha/container/azure/node-pools/create @@ -63,8 +63,7 @@ POSITIONAL ARGUMENTS ▸ provide the argument node_pool on the command line with a fully specified name; ▸ provide the argument --location on the command line; - ▸ set the property container_azure/location; - ▸ set the property azure/location (deprecated). + ▸ set the property container_azure/location. REQUIRED FLAGS --node-version=NODE_VERSION diff --git a/gcloud/alpha/container/azure/node-pools/delete b/gcloud/alpha/container/azure/node-pools/delete index dbe76a8a3..5e61acfb5 100644 --- a/gcloud/alpha/container/azure/node-pools/delete +++ b/gcloud/alpha/container/azure/node-pools/delete @@ -49,8 +49,7 @@ POSITIONAL ARGUMENTS ▸ provide the argument node_pool on the command line with a fully specified name; ▸ provide the argument --location on the command line; - ▸ set the property container_azure/location; - ▸ set the property azure/location (deprecated). + ▸ set the property container_azure/location. FLAGS --async diff --git a/gcloud/alpha/container/azure/node-pools/describe b/gcloud/alpha/container/azure/node-pools/describe index fd2196afd..48e966416 100644 --- a/gcloud/alpha/container/azure/node-pools/describe +++ b/gcloud/alpha/container/azure/node-pools/describe @@ -49,8 +49,7 @@ POSITIONAL ARGUMENTS ▸ provide the argument node_pool on the command line with a fully specified name; ▸ provide the argument --location on the command line; - ▸ set the property container_azure/location; - ▸ set the property azure/location (deprecated). + ▸ set the property container_azure/location. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/alpha/container/azure/node-pools/list b/gcloud/alpha/container/azure/node-pools/list index 4904283bb..2798ced3e 100644 --- a/gcloud/alpha/container/azure/node-pools/list +++ b/gcloud/alpha/container/azure/node-pools/list @@ -43,8 +43,7 @@ REQUIRED FLAGS ▸ provide the argument --cluster on the command line with a fully specified name; ▸ provide the argument --location on the command line; - ▸ set the property container_azure/location; - ▸ set the property azure/location (deprecated). + ▸ set the property container_azure/location. LIST COMMAND FLAGS --filter=EXPRESSION diff --git a/gcloud/alpha/container/azure/node-pools/update b/gcloud/alpha/container/azure/node-pools/update index efceb4e2e..87863c6dc 100644 --- a/gcloud/alpha/container/azure/node-pools/update +++ b/gcloud/alpha/container/azure/node-pools/update @@ -52,8 +52,7 @@ POSITIONAL ARGUMENTS ▸ provide the argument node_pool on the command line with a fully specified name; ▸ provide the argument --location on the command line; - ▸ set the property container_azure/location; - ▸ set the property azure/location (deprecated). + ▸ set the property container_azure/location. FLAGS --async diff --git a/gcloud/alpha/container/azure/operations/describe b/gcloud/alpha/container/azure/operations/describe index 7242bf3b0..be9cd57b9 100644 --- a/gcloud/alpha/container/azure/operations/describe +++ b/gcloud/alpha/container/azure/operations/describe @@ -40,8 +40,7 @@ POSITIONAL ARGUMENTS ▸ provide the argument operation_id on the command line with a fully specified name; ▸ provide the argument --location on the command line; - ▸ set the property container_azure/location; - ▸ set the property azure/location (deprecated). + ▸ set the property container_azure/location. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/alpha/container/azure/operations/list b/gcloud/alpha/container/azure/operations/list index b9284efed..0fd120669 100644 --- a/gcloud/alpha/container/azure/operations/list +++ b/gcloud/alpha/container/azure/operations/list @@ -23,8 +23,6 @@ FLAGS specified name; ◆ set the property container_azure/location with a fully specified name; - ◆ set the property azure/location (deprecated) with a fully specified - name; ◆ provide the argument --project on the command line; ◆ set the property core/project. @@ -32,8 +30,7 @@ FLAGS ID of the location or fully qualified identifier for the location. To set the location attribute: ▸ provide the argument --location on the command line; - ▸ set the property container_azure/location; - ▸ set the property azure/location (deprecated). + ▸ set the property container_azure/location. LIST COMMAND FLAGS --filter=EXPRESSION diff --git a/gcloud/alpha/container/azure/operations/wait b/gcloud/alpha/container/azure/operations/wait index 4a3ea2fc3..3428f35c2 100644 --- a/gcloud/alpha/container/azure/operations/wait +++ b/gcloud/alpha/container/azure/operations/wait @@ -41,8 +41,7 @@ POSITIONAL ARGUMENTS ▸ provide the argument operation_id on the command line with a fully specified name; ▸ provide the argument --location on the command line; - ▸ set the property container_azure/location; - ▸ set the property azure/location (deprecated). + ▸ set the property container_azure/location. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/alpha/container/clusters/create b/gcloud/alpha/container/clusters/create index 40e87cc46..baa8cd3e6 100644 --- a/gcloud/alpha/container/clusters/create +++ b/gcloud/alpha/container/clusters/create @@ -38,6 +38,7 @@ SYNOPSIS [--ipv6-access-type=IPV6_ACCESS_TYPE] [--issue-client-certificate] [--istio-config=[auth=MTLS_PERMISSIVE,...]] [--labels=[KEY=VALUE,...]] [--linux-sysctls=KEY=VALUE,[KEY=VALUE,...]] [--logging=[COMPONENT,...]] + [--logging-variant=LOGGING_VARIANT] [--machine-type=MACHINE_TYPE, -m MACHINE_TYPE] [--max-nodes-per-pool=MAX_NODES_PER_POOL] [--max-pods-per-node=MAX_PODS_PER_NODE] @@ -613,6 +614,18 @@ FLAGS $ gcloud alpha container clusters create --logging=SYSTEM,WORKLOAD $ gcloud alpha container clusters create --logging=NONE + --logging-variant=LOGGING_VARIANT + Specifies the logging variant that will be deployed on all the nodes in + the cluster. Valid logging variants are MAX_THROUGHPUT, DEFAULT. If no + value is specified, DEFAULT is used. LOGGING_VARIANT must be one of: + + DEFAULT + 'DEFAULT' variant requests minimal resources but may not guarantee + high throughput. + MAX_THROUGHPUT + 'MAX_THROUGHPUT' variant requests more node resources and is able + to achieve logging throughput up to 10MB per sec. + --machine-type=MACHINE_TYPE, -m MACHINE_TYPE The type of machine to use for nodes. Defaults to e2-medium. The list of predefined machine types is available using the following command: @@ -1210,11 +1223,11 @@ FLAGS autoprovisioned node pool. Node Management settings are specified under the field - 'nodeManagement', which has the following fields: - enableAutoUpgrade: A boolean field that indicates if node - autoupgrade is enabled for autoprovisioned node pools. - enableAutoRepair: A boolean field that indicates if node autorepair - is enabled for autoprovisioned node pools. + 'management', which has the following fields: autoUpgrade: A + boolean field that indicates if node autoupgrade is enabled for + autoprovisioned node pools. autoRepair: A boolean field that + indicates if node autorepair is enabled for autoprovisioned node + pools. minCpuPlatform (deprecated): If specified, new autoprovisioned nodes will be scheduled on host with specified CPU architecture or diff --git a/gcloud/alpha/container/clusters/update b/gcloud/alpha/container/clusters/update index e900122f6..aed8a129b 100644 --- a/gcloud/alpha/container/clusters/update +++ b/gcloud/alpha/container/clusters/update @@ -20,7 +20,7 @@ SYNOPSIS | --enable-service-externalips | --enable-shielded-nodes | --enable-stackdriver-kubernetes | --enable-vertical-pod-autoscaling | --generate-password | --identity-provider=IDENTITY_PROVIDER - | --maintenance-window=START_TIME + | --logging-variant=LOGGING_VARIANT | --maintenance-window=START_TIME | --notification-config=[pubsub=ENABLED|DISABLED, pubsub-topic=TOPIC,...] | --private-ipv6-google-access-type=PRIVATE_IPV6_GOOGLE_ACCESS_TYPE @@ -318,6 +318,19 @@ REQUIRED FLAGS --identity-provider=IDENTITY_PROVIDER Enable 3P identity provider on the cluster. + --logging-variant=LOGGING_VARIANT + Specifies the logging variant that will be deployed on all the nodes + in the cluster. Valid logging variants are MAX_THROUGHPUT, DEFAULT. + If no value is specified, DEFAULT is used. LOGGING_VARIANT must be + one of: + + DEFAULT + 'DEFAULT' variant requests minimal resources but may not + guarantee high throughput. + MAX_THROUGHPUT + 'MAX_THROUGHPUT' variant requests more node resources and is able + to achieve logging throughput up to 10MB per sec. + --maintenance-window=START_TIME Set a time of day when you prefer maintenance to start on this cluster. For example: @@ -788,11 +801,11 @@ REQUIRED FLAGS the same time on each upgrade of an autoprovisioned node pool. Node Management settings are specified under the field - 'nodeManagement', which has the following fields: - enableAutoUpgrade: A boolean field that indicates if node - autoupgrade is enabled for autoprovisioned node pools. - enableAutoRepair: A boolean field that indicates if node - autorepair is enabled for autoprovisioned node pools. + 'management', which has the following fields: autoUpgrade: A + boolean field that indicates if node autoupgrade is enabled for + autoprovisioned node pools. autoRepair: A boolean field that + indicates if node autorepair is enabled for autoprovisioned node + pools. minCpuPlatform (deprecated): If specified, new autoprovisioned nodes will be scheduled on host with specified CPU architecture diff --git a/gcloud/alpha/container/node-pools/create b/gcloud/alpha/container/node-pools/create index 778ab6dac..c0fb0e3c9 100644 --- a/gcloud/alpha/container/node-pools/create +++ b/gcloud/alpha/container/node-pools/create @@ -15,6 +15,7 @@ SYNOPSIS [--enable-blue-green-upgrade] [--enable-confidential-nodes] [--enable-gvnic] [--enable-image-streaming] [--enable-surge-upgrade] [--image-type=IMAGE_TYPE] [--linux-sysctls=KEY=VALUE,[KEY=VALUE,...]] + [--logging-variant=LOGGING_VARIANT] [--machine-type=MACHINE_TYPE, -m MACHINE_TYPE] [--max-pods-per-node=MAX_PODS_PER_NODE] [--max-surge-upgrade=MAX_SURGE_UPGRADE; default=1] @@ -199,6 +200,20 @@ FLAGS --linux-sysctls="net.core.somaxconn=1024,net.ipv4.tcp_rmem=4096 \ 87380 6291456" + --logging-variant=LOGGING_VARIANT + Specifies the logging variant that will be deployed on all the nodes in + the node pool. If the node pool doesn't specify a logging variant, then + the logging variant specified for the cluster will be deployed on all + the nodes in the node pool. Valid logging variants are MAX_THROUGHPUT, + DEFAULT. LOGGING_VARIANT must be one of: + + DEFAULT + 'DEFAULT' variant requests minimal resources but may not guarantee + high throughput. + MAX_THROUGHPUT + 'MAX_THROUGHPUT' variant requests more node resources and is able + to achieve logging throughput up to 10MB per sec. + --machine-type=MACHINE_TYPE, -m MACHINE_TYPE The type of machine to use for nodes. Defaults to e2-medium. The list of predefined machine types is available using the following command: diff --git a/gcloud/alpha/container/node-pools/update b/gcloud/alpha/container/node-pools/update index 6c431b1b5..87050962b 100644 --- a/gcloud/alpha/container/node-pools/update +++ b/gcloud/alpha/container/node-pools/update @@ -5,7 +5,7 @@ NAME SYNOPSIS gcloud alpha container node-pools update NAME (--enable-confidential-nodes | --enable-gvnic - | --enable-image-streaming + | --enable-image-streaming | --logging-variant=LOGGING_VARIANT | --network-performance-configs=[PROPERTY=VALUE,...] | --node-labels=[NODE_LABEL,...] | --node-locations=ZONE,[ZONE,...] | --node-taints=[NODE_TAINT,...] @@ -54,6 +54,20 @@ REQUIRED FLAGS --enable-image-streaming Specifies whether to enable image streaming on node pool. + --logging-variant=LOGGING_VARIANT + Specifies the logging variant that will be deployed on all the nodes + in the node pool. If the node pool doesn't specify a logging variant, + then the logging variant specified for the cluster will be deployed + on all the nodes in the node pool. Valid logging variants are + MAX_THROUGHPUT, DEFAULT. LOGGING_VARIANT must be one of: + + DEFAULT + 'DEFAULT' variant requests minimal resources but may not + guarantee high throughput. + MAX_THROUGHPUT + 'MAX_THROUGHPUT' variant requests more node resources and is able + to achieve logging throughput up to 10MB per sec. + --network-performance-configs=[PROPERTY=VALUE,...] Configures network performance settings for the node pool. If this flag is not specified, the pool will be created with its default diff --git a/gcloud/alpha/dataproc/clusters/gke/create b/gcloud/alpha/dataproc/clusters/gke/create index 180b2bd36..3e0577539 100644 --- a/gcloud/alpha/dataproc/clusters/gke/create +++ b/gcloud/alpha/dataproc/clusters/gke/create @@ -129,8 +129,8 @@ OPTIONAL FLAGS components in. This namespace does not need to exist. --pools=[KEY=VALUE[;VALUE],...] - Each --pools flag represents a single GKE node pool associated with the - virtual cluster. It is comprised of a CSV in the form + Each --pools flag represents a GKE node pool associated with the + virtual cluster. It is a comma-separated list in the form KEY=VALUE[;VALUE], where certain keys may have multiple values. The following KEYs must be specified: @@ -140,36 +140,39 @@ OPTIONAL FLAGS ------ ---------------- ------------------------ ---------------------------------------------------------- name string `my-node-pool` Name of the node pool. - roles repeated string `default;spark-driver` Roles that this node pool should perform. Valid values are - `default`, `controller`, `spark-driver`, `spark-executor`. + roles repeated string `default;spark-driver` Roles that each node pool will perform. + [One Pool must have DEFAULT role] Valid values are + `default`, `controller`, `spark-driver`, `spark-executor`. ----------------------------------------------------------------------------------------------------------- The following KEYs may be specified: ---------------------------------------------------------------------------------------------------------------------------------------------------------------- - KEY Type Example Description + KEY Type Example Description --------------- ---------------- --------------------------------------------- --------------------------------------------------------------------------------- - machineType string `n1-standard-8` Compute Engine machine type to use. + machineType string `n1-standard-8` Compute Engine machine type to use. - preemptible boolean `false` If true, then this node pool uses preemptible VMs. - This cannot be true on the node pool with the `controllers` role - (or `default` role if `controllers` role is not specified). + preemptible boolean `false` If true, then this node pool uses preemptible VMs. + This Must be `false` for a node pool with the CONTROLLER role or + for a node pool with the DEFAULT role in no node pool has the CONTROLLER role. - localSsdCount int `2` The number of local SSDs to attach to each node. + localSsdCount int `2` The number of local SSDs to attach to each node. - accelerator repeated string `nvidia-tesla-a100=1` Accelerators to attach to each node. In the format NAME=COUNT. + localNvmeSsdCount int `2` The number of local NVMe SSDs to attach to each node. - minCpuPlatform string `Intel Skylake` Minimum CPU platform for each node. + accelerator repeated string `nvidia-tesla-a100=1` Accelerators to attach to each node, in NODE=COUNT format. - bootDiskKmsKey string `projects/project-id/locations/us-central1 The Customer Managed Encryption Key (CMEK) used to encrypt - /keyRings/keyRing-name/cryptoKeys/key-name` the boot disk attached to each node in the node pool. + minCpuPlatform string `Intel Skylake` Minimum CPU platform for each node. - locations repeated string `us-west1-a;us-west1-c` Zones within the location of the GKE cluster. - All `--pools` flags for a single Dataproc cluster must have identical locations. + bootDiskKmsKey string `projects/project-id/locations/us-central1 The Customer Managed Encryption Key (CMEK) used to encrypt + /keyRings/keyRing-name/cryptoKeys/key-name` the boot disk attached to each node in the node pool. - min int `0` Minimum number of nodes per zone that this node pool can scale down to. + locations repeated string `us-west1-a;us-west1-c` Zones within the location of the GKE cluster. + All `--pools` flags for a Dataproc cluster must have identical locations. - max int `10` Maximum number of nodes per zone that this node pool can scale up to. + min int `0` Minimum number of nodes per zone that this node pool can scale down to. + + max int `10` Maximum number of nodes per zone that this node pool can scale up to. ---------------------------------------------------------------------------------------------------------------------------------------------------------------- --properties=[PREFIX:PROPERTY=VALUE,...] diff --git a/gcloud/alpha/edge-cloud/networking/routers/help b/gcloud/alpha/edge-cloud/networking/routers/help index 89a82b5a7..436f3a39d 100644 --- a/gcloud/alpha/edge-cloud/networking/routers/help +++ b/gcloud/alpha/edge-cloud/networking/routers/help @@ -46,6 +46,9 @@ COMMANDS (ALPHA) remove a list of interfaces on a Distributed Cloud Edge Network router. + update + (ALPHA) Update a Distributed Cloud Edge Network router. + 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/edge-cloud/networking/routers/update b/gcloud/alpha/edge-cloud/networking/routers/update new file mode 100644 index 000000000..9670a10a6 --- /dev/null +++ b/gcloud/alpha/edge-cloud/networking/routers/update @@ -0,0 +1,110 @@ +NAME + gcloud alpha edge-cloud networking routers update - update a Distributed + Cloud Edge Network router + +SYNOPSIS + gcloud alpha edge-cloud networking routers update + (ROUTER : --location=LOCATION --zone=ZONE) [--async] + [--add-advertisement-ranges=ADD_ADVERTISEMENT_RANGES + | --remove-advertisement-ranges=REMOVE_ADVERTISEMENT_RANGES + | --set-advertisement-ranges=SET_ADVERTISEMENT_RANGES] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Update a Distributed Cloud Edge Network router. + + Note that update operations are not thread-safe, meaning that if more than + one user is updating a router at a time, there can be race conditions. + Please ensure that at most one update operation is being applied to a given + router at a time. + +EXAMPLES + To add a northbound route advertisement for destination range 8.8.0.0/16 + for Distributed Cloud Edge Network router 'my-router' in edge zone + 'us-central1-edge-den1' , run: + + $ gcloud alpha edge-cloud networking routers update my-router \ + --add-advertisement-ranges=8.8.0.0/16 --location=us-central1 \ + --zone=us-central1-edge-den1 + + To remove a northbound route advertisement for destination range 8.8.0.0/16 + for Distributed Cloud Edge Network router 'my-router' in edge zone + 'us-central1-edge-den1' , run: + + $ gcloud alpha edge-cloud networking routers update my-router \ + --remove-advertisement-ranges=8.8.0.0/16 \ + --location=us-central1 --zone=us-central1-edge-den1 + + To replace the set of route advertisements with just 8.8.0.0/16 and + 1.1.0.0/16, in Distributed Cloud Edge Network router 'my-router' in edge + zone 'us-central1-edge-den1' , run: + + $ gcloud alpha edge-cloud networking routers update my-router \ + --set-advertisement-ranges=8.8.0.0/16,1.1.0.0/16 \ + --location=us-central1 --zone=us-central1-edge-den1 + +POSITIONAL ARGUMENTS + Router resource - The router to be updated. 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 + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + ROUTER + ID of the router or fully qualified identifier for the router. To set + the router attribute: + ▸ provide the argument router on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + The Cloud location for the router. To set the location attribute: + ▸ provide the argument router on the command line with a fully + specified name; + ▸ provide the argument --location on the command line. + + --zone=ZONE + The zone of the router. To set the zone attribute: + ▸ provide the argument router on the command line with a fully + specified name; + ▸ provide the argument --zone on the command line. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + At most one of these can be specified: + + --add-advertisement-ranges=ADD_ADVERTISEMENT_RANGES + add the comma-separated list of CIDRs to the set of range + advertisements. + + --remove-advertisement-ranges=REMOVE_ADVERTISEMENT_RANGES + remove the comma-separated list of CIDRs from the set of range + advertisements. + + --set-advertisement-ranges=SET_ADVERTISEMENT_RANGES + replace the comma-separated list of CIDRs with the set of range + advertisements. + +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/spanner/databases/execute-sql b/gcloud/alpha/spanner/databases/execute-sql index 3dd3c35a7..7f195ef5d 100644 --- a/gcloud/alpha/spanner/databases/execute-sql +++ b/gcloud/alpha/spanner/databases/execute-sql @@ -4,7 +4,7 @@ NAME SYNOPSIS gcloud alpha spanner databases execute-sql (DATABASE : --instance=INSTANCE) - --sql=SQL [--enable-partitioned-dml] + --sql=SQL [--database-role=DATABASE_ROLE] [--enable-partitioned-dml] [--query-mode=QUERY_MODE; default="NORMAL"] [--timeout=TIMEOUT; default="10m"] [--read-timestamp=TIMESTAMP | --strong] [GCLOUD_WIDE_FLAG ...] @@ -54,6 +54,9 @@ REQUIRED FLAGS at https://cloud.google.com/spanner/docs/query-syntax OPTIONAL FLAGS + --database-role=DATABASE_ROLE + Database role user assumes while accessing the database. + --enable-partitioned-dml Execute DML statement using Partitioned DML diff --git a/gcloud/alpha/spanner/databases/help b/gcloud/alpha/spanner/databases/help index fd30e5141..72e5d434c 100644 --- a/gcloud/alpha/spanner/databases/help +++ b/gcloud/alpha/spanner/databases/help @@ -21,6 +21,9 @@ GROUPS ddl (ALPHA) Manage the DDL for Cloud Spanner databases. + roles + (ALPHA) Manage Cloud Spanner database roles. + sessions (ALPHA) Manage the sessions for Cloud Spanner databases. diff --git a/gcloud/alpha/spanner/databases/roles/help b/gcloud/alpha/spanner/databases/roles/help new file mode 100644 index 000000000..a4b2188ff --- /dev/null +++ b/gcloud/alpha/spanner/databases/roles/help @@ -0,0 +1,29 @@ +NAME + gcloud alpha spanner databases roles - manage Cloud Spanner database roles + +SYNOPSIS + gcloud alpha spanner databases roles COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Manage Cloud Spanner database roles. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + list + (ALPHA) List the Cloud Spanner database roles contained within the + given database. + +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 spanner databases roles + diff --git a/gcloud/alpha/spanner/databases/roles/list b/gcloud/alpha/spanner/databases/roles/list new file mode 100644 index 000000000..d95d9827b --- /dev/null +++ b/gcloud/alpha/spanner/databases/roles/list @@ -0,0 +1,96 @@ +NAME + gcloud alpha spanner databases roles list - list the Cloud Spanner database + roles contained within the given database + +SYNOPSIS + gcloud alpha spanner databases roles list + (--database=DATABASE : --instance=INSTANCE) [--filter=EXPRESSION] + [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) List the Cloud Spanner database roles contained within the given + database. + +EXAMPLES + To list the Cloud Spanner database roles in a database, run: + + $ gcloud alpha spanner databases roles list \ + --instance=my-instance-id --database=my-database-id + +REQUIRED FLAGS + Database resource - The Cloud Spanner database in which to list database + roles. 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 --database 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. + + --database=DATABASE + ID of the database or fully qualified identifier for the database. To + set the database attribute: + ▸ provide the argument --database on the command line. + + This flag argument must be specified if any of the other arguments in + this group are specified. + + --instance=INSTANCE + The Cloud Spanner instance for the database. To set the instance + attribute: + ▸ provide the argument --database on the command line with a fully + specified name; + ▸ provide the argument --instance on the command line; + ▸ set the property spanner/instance. + +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. This variant is also available: + + $ gcloud beta spanner databases roles list + diff --git a/gcloud/alpha/storage/cp b/gcloud/alpha/storage/cp index 49e25b937..3bb2d84d0 100644 --- a/gcloud/alpha/storage/cp +++ b/gcloud/alpha/storage/cp @@ -55,6 +55,18 @@ EXAMPLES $ gcloud alpha storage cp --recursive dir gs://my-bucket + Recursive listings are similar to adding ** to a query, except ** matches + only cloud objects and will not match prefixes. For example, the following + would not match gs://my-bucket/dir/log.txt + + $ gcloud alpha storage cp gs://my-bucket/**/dir dir + + ** retrieves a flat list of objects in a single API call. However, ** + matches folders for non-cloud queries. For example, a folder dir would be + copied in the following. + + $ gcloud alpha storage cp ~/Downloads/**/dir gs://my-bucket + POSITIONAL ARGUMENTS [SOURCE ...] The source path(s) to copy. diff --git a/gcloud/alpha/storage/help b/gcloud/alpha/storage/help index 180b72d3c..aa6e01ce8 100644 --- a/gcloud/alpha/storage/help +++ b/gcloud/alpha/storage/help @@ -38,6 +38,9 @@ COMMANDS ls (ALPHA) List Cloud Storage buckets and objects. + mv + (ALPHA) Moves or renames objects. + rm (ALPHA) Delete objects and buckets. diff --git a/gcloud/alpha/storage/ls b/gcloud/alpha/storage/ls index 9edf38de8..44dd059a6 100644 --- a/gcloud/alpha/storage/ls +++ b/gcloud/alpha/storage/ls @@ -45,8 +45,14 @@ EXAMPLES $ gcloud alpha storage ls gs://my-bucket/**/*.txt - Double-star expansion can not be combined with other expressions in a given - path segment and operates as a single star in that context. For example: + ** retrieves a flat list of objects in a single API call and will not match + prefixes. The following command would not match gs://my-bucket/dir/log.txt: + + $ gcloud alpha storage ls gs://my-bucket/**/dir + + Double-star expansion also can not be combined with other expressions in a + given path segment and operates as a single star in that context. For + example: gs://my-bucket/dir**/log.txt is treated as: @@ -59,8 +65,8 @@ EXAMPLES $ gcloud alpha storage ls --recursive gs://bucket - Recursive listings are similar to ``**'' except recursive listings include - line breaks and header formatting for each subdirectory. + Recursive listings are similar to ** except recursive listings include line + breaks and header formatting for each subdirectory. POSITIONAL ARGUMENTS [PATH ...] diff --git a/gcloud/alpha/storage/mv b/gcloud/alpha/storage/mv new file mode 100644 index 000000000..f855d2e32 --- /dev/null +++ b/gcloud/alpha/storage/mv @@ -0,0 +1,337 @@ +NAME + gcloud alpha storage mv - moves or renames objects + +SYNOPSIS + gcloud alpha storage mv [SOURCE ...] DESTINATION [--all-versions, -A] + [--cache-control=CACHE_CONTROL] [--no-clobber, -n] + [--content-disposition=CONTENT_DISPOSITION] + [--content-encoding=CONTENT_ENCODING] + [--content-language=CONTENT_LANGUAGE] [--content-md5=MD5_DIGEST] + [--content-type=CONTENT_TYPE] [--continue-on-error, -c] + [--custom-time=CUSTOM_TIME] [--daisy-chain, -D] + [--decryption-keys=[DECRYPTION_KEY,...]] [--do-not-decompress] + [--encryption-key=ENCRYPTION_KEY] [--ignore-symlinks] + [--manifest-path=MANIFEST_PATH, -L MANIFEST_PATH] + [--preserve-posix, -P] [--print-created-message, -v] + [--read-paths-from-stdin, -I] [--skip-unsupported, -U] + [--storage-class=STORAGE_CLASS, -s STORAGE_CLASS] + [--canned-acl=PREDEFINED_ACL, + --predefined-acl=PREDEFINED_ACL, -a PREDEFINED_ACL + | --preserve-acl, -p] + [--clear-custom-metadata + | --custom-metadata=[CUSTOM_METADATA_KEYS_AND_VALUES,...] + | --remove-custom-metadata=[METADATA_KEYS,...] + --update-custom-metadata=[CUSTOM_METADATA_KEYS_AND_VALUES,...]] + [--gzip-in-flight=[FILE_EXTENSIONS,...], -j [FILE_EXTENSIONS,...] + | --gzip-in-flight-all, -J + | --gzip-local=[FILE_EXTENSIONS,...], -z [FILE_EXTENSIONS,...] + | --gzip-local-all, -Z] + [--if-generation-match=GENERATION + --if-metageneration-match=METAGENERATION] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) The mv command allows you to move data between your local file + system and the cloud, move data within the cloud, and move data between + cloud storage providers + + Renaming Groups Of Objects + + You can use the mv command to rename all objects with a given prefix to + have a new prefix. For example, the following command renames all objects + under gs://my_bucket/oldprefix to be under gs://my_bucket/newprefix, + otherwise preserving the naming structure: + + $ gcloud alpha storage mv mv gs://my_bucket/oldprefix \ + gs://my_bucket/newprefix + + Note that when using mv to rename groups of objects with a common prefix, + you cannot specify the source URL using wildcards; you must spell out the + complete name. + + If you do a rename as specified above and you want to preserve ACLs. + + Non-Atomic Operation + + Unlike the case with many file systems, the mv command does not perform a + single atomic operation. Rather, it performs a copy from source to + destination followed by removing the source for each object. + + A consequence of this is that, in addition to normal network and operation + charges, if you move a Nearline Storage, Coldline Storage, or Archive + Storage object, deletion and data retrieval charges apply. See the + documentation for pricing details. + +EXAMPLES + To move all objects from a bucket to a local directory you could use: + + $ gcloud alpha storage mv gs://my_bucket/* dir + + Similarly, to move all objects from a local directory to a bucket you could + use: + + $ gcloud alpha storage mv ./dir gs://my_bucket + + The following command renames all objects under gs://my_bucket/oldprefix to + be under gs://my_bucket/newprefix, otherwise preserving the naming + structure: + + $ gcloud alpha storage mv gs://my_bucket/oldprefix \ + gs://my_bucket/newprefix + +POSITIONAL ARGUMENTS + [SOURCE ...] + The source path(s) to copy. + + DESTINATION + The destination path. + +FLAGS + --all-versions, -A + Copy all source versions from a source bucket or folder. If not set, + only the live version of each source object is copied. + + Note: This option is only useful when the destination bucket has Object + Versioning enabled. Additionally, the generation numbers of copied + versions do not necessarily match the order of the original generation + numbers. + + --cache-control=CACHE_CONTROL + How caches should handle requests and responses. + + --no-clobber, -n + Do not overwrite existing files or objects at the destination. Skipped + items will be printed. This option performs an additional GET request + for cloud objects before attempting an upload. + + --content-disposition=CONTENT_DISPOSITION + How content should be displayed. + + --content-encoding=CONTENT_ENCODING + How content is encoded (e.g. gzip). + + --content-language=CONTENT_LANGUAGE + Content's language (e.g. en signifies "English"). + + --content-md5=MD5_DIGEST + Manually specified MD5 hash digest for the contents of an uploaded + file. This flag cannot be used when uploading multiple files. The + custom digest is used by the cloud provider for validation. + + --content-type=CONTENT_TYPE + Type of data contained in the object (e.g. text/html). + + --continue-on-error, -c + If any operations are unsuccessful, the command will exit with a + non-zero exit status after completing the remaining operations. This + flag takes effect only in sequential execution mode (i.e. processor and + thread count are set to 1). Parallelism is default. + + --custom-time=CUSTOM_TIME + Custom time for Google Cloud Storage objects in RFC 3339 format. + + --daisy-chain, -D + Copy in "daisy chain" mode, which means copying an object by first + downloading it to the machine where the command is run, then uploading + it to the destination bucket. The default mode is a "copy in the + cloud," where data is copied without uploading or downloading. During a + copy in the cloud, a source composite object remains composite at its + destination. However, you can use daisy chain mode to change a + composite object into a non-composite object. Note: Daisy chain mode is + automatically used when copying between providers. + + --decryption-keys=[DECRYPTION_KEY,...] + A comma separated list of customer-supplied encryption keys (RFC 4648 + section 4 base64-encoded AES256 strings) that will be used to decrypt + Google Cloud Storage objects. Data encrypted with a customer-managed + encryption key (CMEK) is decrypted automatically, so CMEKs do not need + to be listed here. + + --do-not-decompress + Do not automatically decompress downloaded gzip files. + + --encryption-key=ENCRYPTION_KEY + The encryption key to use for encrypting target objects. The specified + encryption key can be a customer-supplied encryption key (An RFC 4648 + section 4 base64-encoded AES256 string), or a customer-managed + encryption key of the form + projects/{project}/locations/{location}/keyRings/ + {key-ring}/cryptoKeys/{crypto-key}. The specified key also acts as a + decryption key, which is useful when copying or moving encryted data to + a new location. Using this flag in an objects update command triggers a + rewrite of target objects. + + --ignore-symlinks + Ignore file symlinks instead of copying what they point to. Symlinks + pointing to directories will always be ignored. + + --manifest-path=MANIFEST_PATH, -L MANIFEST_PATH + Outputs a manifest log file with detailed information about each item + that was copied. This manifest contains the following information for + each item: + + ◆ Source path. + ◆ Destination path. + ◆ Source size. + ◆ Bytes transferred. + ◆ MD5 hash. + ◆ Transfer start time and date in UTC and ISO 8601 format. + ◆ Transfer completion time and date in UTC and ISO 8601 format. + ◆ Final result of the attempted transfer: OK, error, or skipped. + ◆ Details, if any. + + If the manifest file already exists, gcloud storage appends log items + to the existing file. + + Objects that are marked as "OK" or "skipped" in the existing manifest + file are not retried by future commands. Objects marked as "error" are + retried. + + --preserve-posix, -P + Causes POSIX attributes to be preserved when objects are copied. With + this feature enabled, gcloud storage will copy several fields provided + by the stat command: access time, modification time, owner UID, owner + group GID, and the mode (permissions) of the file. + + For uploads, these attributes are read off of local files and stored in + the cloud as custom metadata. For downloads, custom cloud metadata is + set as POSIX attributes on files after they are downloaded. + + On Windows, this flag will only set and restore access time and + modification time because Windows doesn't have a notion of POSIX UID, + GID, and mode. + + --print-created-message, -v + Prints the version-specific URL for each copied object. + + --read-paths-from-stdin, -I + Read the list of resources to copy from stdin. No need to enter a + source argument if this flag is present. Example: "storage cp -I + gs://bucket/destination" Note: To copy the contents of one file + directly from stdin, use "-" as the source argument without the "-I" + flag. + + --skip-unsupported, -U + Skip objects with unsupported object types.Currently, the only + unsupported category is Amazon S3 objects with the GLACIER storage + class. + + --storage-class=STORAGE_CLASS, -s STORAGE_CLASS + Specify the storage class of the destination object. If not specified, + the default storage class of the destination bucket is used. This + option is not valid for copying to non-cloud destinations. + + At most one of these can be specified: + + --canned-acl=PREDEFINED_ACL, --predefined-acl=PREDEFINED_ACL, -a PREDEFINED_ACL + Applies predefined, or "canned," ACLs to a copied object. See docs + for a list of predefined ACL constants: + https://cloud.google.com/storage/docs/access-control/lists#predefined-acl + + --preserve-acl, -p + Preserves ACLs when copying in the cloud. This option is Google Cloud + Storage-only, and you need OWNER access to all copied objects. If all + objects in the destination bucket should have the same ACL, you can + also set a default object ACL on that bucket instead of using this + flag. + + At most one of these can be specified: + + --clear-custom-metadata + Clears all custom metadata on objects. When used with + --preserve-posix, POSIX attributes will still be stored in custom + metadata. + + --custom-metadata=[CUSTOM_METADATA_KEYS_AND_VALUES,...] + Sets custom metadata on objects. When used with --preserve-posix, + POSIX attributes are also stored in custom metadata. + + Flags that preserve unspecified existing metadata cannot be used with + --custom-metadata or --clear-custom-metadata, but can be specified + together: + + --remove-custom-metadata=[METADATA_KEYS,...] + Removes individual custom metadata keys from objects. This flag can + be used with --update-custom-metadata. When used with + --preserve-posix, POSIX attributes specified by this flag are not + preserved. + + --update-custom-metadata=[CUSTOM_METADATA_KEYS_AND_VALUES,...] + Adds or sets individual custom metadata key value pairs on objects. + Existing custom metadata not specified with this flag is not + changed. This flag can be used with --remove-custom-metadata. When + keys overlap with those provided by --preserve-posix, values + specified by this flag are used. + + At most one of these can be specified: + + --gzip-in-flight=[FILE_EXTENSIONS,...], -j [FILE_EXTENSIONS,...] + Applies gzip transport encoding to any file upload whose extension + matches the input extension list. This is useful when uploading files + with compressible content such as .js, .css, or .html files. This + also saves network bandwidth while leaving the data uncompressed in + Cloud Storage. + + When you specify the --gzip-in-flight option, files being uploaded + are compressed in-memory and on-the-wire only. Both the local files + and Cloud Storage objects remain uncompressed. The uploaded objects + retain the Content-Type and name of the original files. + + --gzip-in-flight-all, -J + Applies gzip transport encoding to file uploads. This option works + like the --gzip-in-flight option described above, but it applies to + all uploaded files, regardless of extension. + + CAUTION: If some of the source files don't compress well, such as + binary data, using this option may result in longer uploads. + + --gzip-local=[FILE_EXTENSIONS,...], -z [FILE_EXTENSIONS,...] + Applies gzip content encoding to any file upload whose extension + matches the input extension list. This is useful when uploading files + with compressible content such as .js, .css, or .html files. This + saves network bandwidth and space in Cloud Storage. + + When you specify the --gzip-local option, the data from files is + compressed before it is uploaded, but the original files are left + uncompressed on the local disk. The uploaded objects retain the + Content-Type and name of the original files. However, the + Content-Encoding metadata is set to gzip and the Cache-Control + metadata set to no-transform. The data remains compressed on Cloud + Storage servers and will not be decompressed on download by gcloud + stroage because of the no-transform field. + + Since the local gzip option compresses data prior to upload, it is + not subject to the same compression buffer bottleneck of the + in-flight gzip option. + + --gzip-local-all, -Z + Applies gzip content encoding to file uploads. This option works like + the --gzip-local option described above, but it applies to all + uploaded files, regardless of extension. + + CAUTION: If some of the source files don't compress well, such as + binary data, using this option may result in files taking up more + space in the cloud than they would if left uncompressed. + +PRECONDITION FLAGS + --if-generation-match=GENERATION + Execute only if the generation matches the generation of the requested + object. + + --if-metageneration-match=METAGENERATION + Execute only if the metageneration matches the metageneration of the + requested object. + +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/app/deploy b/gcloud/app/deploy index 1d1f2564f..f70fef36c 100644 --- a/gcloud/app/deploy +++ b/gcloud/app/deploy @@ -18,7 +18,7 @@ DESCRIPTION https://cloud.google.com/appengine/docs/standard/python/configuration-files or https://cloud.google.com/appengine/docs/flexible/python/configuration-files). - Note, for Java8 Standard apps or Java11 Standard apps using bundled + Note, for Java8 Standard apps or Java11/17 Standard apps using bundled services, you must add the path to the appengine-web.xml file inside the WEB-INF directory. gcloud app deploy skips files specified in the .gcloudignore file (see gcloud topic gcloudignore for more information). diff --git a/gcloud/beta/ai/endpoints/deploy-model b/gcloud/beta/ai/endpoints/deploy-model index 688fd9644..bc021ac9d 100644 --- a/gcloud/beta/ai/endpoints/deploy-model +++ b/gcloud/beta/ai/endpoints/deploy-model @@ -12,7 +12,10 @@ SYNOPSIS [--max-replica-count=MAX_REPLICA_COUNT] [--min-replica-count=MIN_REPLICA_COUNT] [--service-account=SERVICE_ACCOUNT] - [--traffic-split=[DEPLOYED_MODEL_ID=VALUE,...]] [GCLOUD_WIDE_FLAG ...] + [--traffic-split=[DEPLOYED_MODEL_ID=VALUE,...]] + [--shared-resources=SHARED_RESOURCES + : --shared-resources-region=SHARED_RESOURCES_REGION] + [GCLOUD_WIDE_FLAG ...] EXAMPLES To deploy a model 456 to an endpoint 123 under project example in region @@ -130,6 +133,35 @@ OPTIONAL FLAGS --traffic-split=[DEPLOYED_MODEL_ID=VALUE,...] List of pairs of deployed model id and value to set as traffic split. + Deployment resource pool resource - The deployment resource pool to + co-host a model on. 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 --shared-resources on the command line with a + fully specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + --shared-resources=SHARED_RESOURCES + ID of the deployment_resource_pool or fully qualified identifier for + the deployment_resource_pool. To set the name attribute: + ▸ provide the argument --shared-resources on the command line. + + This flag argument must be specified if any of the other arguments in + this group are specified. + + --shared-resources-region=SHARED_RESOURCES_REGION + Cloud region for the deployment_resource_pool. To set the region + attribute: + ▸ provide the argument --shared-resources on the command line with + a fully specified name; + ▸ provide the argument --shared-resources-region on the command + line; + ▸ provide the argument --region on the command line; + ▸ set the property ai/region; + ▸ choose one from the prompted list of available regions. + GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, diff --git a/gcloud/beta/app/deploy b/gcloud/beta/app/deploy index 02cd7398a..578a8f97d 100644 --- a/gcloud/beta/app/deploy +++ b/gcloud/beta/app/deploy @@ -18,7 +18,7 @@ DESCRIPTION https://cloud.google.com/appengine/docs/standard/python/configuration-files or https://cloud.google.com/appengine/docs/flexible/python/configuration-files). - Note, for Java8 Standard apps or Java11 Standard apps using bundled + Note, for Java8 Standard apps or Java11/17 Standard apps using bundled services, you must add the path to the appengine-web.xml file inside the WEB-INF directory. gcloud beta app deploy skips files specified in the .gcloudignore file (see gcloud topic gcloudignore for more information). diff --git a/gcloud/beta/asset/help b/gcloud/beta/asset/help index 0872bf807..82c0bc244 100644 --- a/gcloud/beta/asset/help +++ b/gcloud/beta/asset/help @@ -33,6 +33,9 @@ COMMANDS list (BETA) List the Cloud assets. + query + (BETA) Query the Cloud assets. + search-all-iam-policies (BETA) Searches all IAM policies within the specified accessible scope, such as a project, folder or organization. diff --git a/gcloud/beta/asset/query b/gcloud/beta/asset/query new file mode 100644 index 000000000..8d68aa5b8 --- /dev/null +++ b/gcloud/beta/asset/query @@ -0,0 +1,159 @@ +NAME + gcloud beta asset query - query the Cloud assets + +SYNOPSIS + gcloud beta asset query + (--folder=FOLDER_ID | --organization=ORGANIZATION_ID + | --project=PROJECT_ID) + (--job-reference=JOB_REFERENCE | --statement=STATEMENT) + [--page-size=PAGE_SIZE] [--page-token=PAGE_TOKEN] [--timeout=TIMEOUT] + [--snapshot-time=SNAPSHOT_TIME + | [--start-time=START_TIME : --end-time=END_TIME]] + [--write-disposition=WRITE_DISPOSITION [--bigquery-table=BIGQUERY_TABLE + : --bigquery-dataset=BIGQUERY_DATASET]] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Issue an analytical query on Cloud assets using BigQuery Standard + SQL compatible statement. + +EXAMPLES + To count the number of compute instance, run: + + $ gcloud beta asset query --project='test-project' \ + --statement='SELECT * FROM compute_googleapis_com_Instance' + + To see the query result of previous job, pass the job-reference from + previous response: + + $ gcloud beta asset query --project='test-project' \ + --job-reference= + +REQUIRED FLAGS + Exactly one of these must be specified: + + --folder=FOLDER_ID + The ID of the folder which is the root asset. + + --organization=ORGANIZATION_ID + The ID of the organization which is the root asset. + + --project=PROJECT_ID + The project which is the root asset. + + The Google Cloud project ID to use for this invocation. If omitted, + then the current project is assumed; the current project can be + listed using gcloud config list --format='text(core.project)' and can + be set using gcloud config set project PROJECTID. + + --project and its fallback core/project property play two roles in + the invocation. It specifies the project of the resource to operate + on. It also specifies the project for API enablement check, quota, + and billing. To specify a different project for quota and billing, + use --billing-project or billing/quota_project property. + + The query or job reference of the query request. + + Exactly one of these must be specified: + + --job-reference=JOB_REFERENCE + Reference to the query job, which is from the previous call. + + --statement=STATEMENT + A BigQuery Standard SQL compatible statement. If the query execution + finishes within timeout and there is no pagination, the full query + results will be returned. Otherwise, pass job_reference from previous + call as --job-referrence to obtain the full results. + +OPTIONAL FLAGS + --page-size=PAGE_SIZE + The maximum number of rows to return in the results. One page is also + limited to 10 MB. + + --page-token=PAGE_TOKEN + A page token received from previous call. + + --timeout=TIMEOUT + Maximum amount of time that the client will wait for the query to + complete. + + Specifies what time period or point in time to query asset metadata at. + + At most one of these can be specified: + + --snapshot-time=SNAPSHOT_TIME + Timestamp to take a snapshot on assets. This can only be a current or + past time. If not specified, the current time will be used. Due to + delays in resource data collection and indexing, there is a volatile + window during which running the same query at different times may + return different results. See $ gcloud topic datetimes for + information on time formats. + + Specifies what time period or point in time to query asset metadata at. + + --start-time=START_TIME + Start time of the time window (inclusive) for the asset history. + Must be after the current time minus 35 days. See $ gcloud topic + datetimes for information on time formats. + + This flag argument must be specified if any of the other arguments + in this group are specified. + + --end-time=END_TIME + End time of the time window (exclusive) for the asset history. + Defaults to current time if not specified. See $ gcloud topic + datetimes for information on time formats. + + The BigQuery destination for query system. + + --write-disposition=WRITE_DISPOSITION + Specifies the action that occurs if the destination table or + partition already exists. WRITE_DISPOSITION must be one of: + + write-append + AIf the table or partition already exists, BigQuery appends the + data to the table or the latest partition. + write-empty + If the table already exists and contains data, an error is + returned. + write-truncate + If the table or partition already exists, BigQuery overwrites the + entire table or all the partition's data. + + Table resource - The bigquery-table for the export. 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 --bigquery-table on the command line with a + fully specified name; + ▸ provide the argument --project on the command line; + ▸ set the property core/project. + + --bigquery-table=BIGQUERY_TABLE + ID of the table or fully qualified identifier for the table. To set + the table attribute: + ▫ provide the argument --bigquery-table on the command line. + + This flag argument must be specified if any of the other arguments + in this group are specified. + + --bigquery-dataset=BIGQUERY_DATASET + The id of the BigQuery dataset. To set the bigquery-dataset + attribute: + ▫ provide the argument --bigquery-table on the command line with + a fully specified name; + ▫ provide the argument --bigquery-dataset on the command line. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha asset query + diff --git a/gcloud/beta/batch/help b/gcloud/beta/batch/help index cb5614a2c..951e5cee1 100644 --- a/gcloud/beta/batch/help +++ b/gcloud/beta/batch/help @@ -5,7 +5,15 @@ SYNOPSIS gcloud beta batch GROUP [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) Manage Batch resources. + (BETA) The gcloud batch command group lets you submit Batch jobs and + manipulate Batch jobs and tasks. + + With Batch, you can utilize the fully managed service to schedule, queue, + and execute batch jobs on Google's infrastructure. + + For more information about Batch, see the Batch overview + (https://cloud.google.com/batch) and the Batch documentation + (https://cloud.google.com/batch/docs/). GCLOUD WIDE FLAGS These flags are available to all commands: --help. diff --git a/gcloud/beta/batch/jobs/help b/gcloud/beta/batch/jobs/help index c16366b29..c14225f52 100644 --- a/gcloud/beta/batch/jobs/help +++ b/gcloud/beta/batch/jobs/help @@ -5,7 +5,15 @@ SYNOPSIS gcloud beta batch jobs COMMAND [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) Manage Batch job resources. + (BETA) The gcloud batch jobs command group lets you submit, describe, list + and delete Batch jobs. + + With Batch, you can utilize the fully managed service to schedule, queue, + and execute batch jobs on Google's infrastructure. + + For more information about Batch, see the Batch overview + (https://cloud.google.com/batch) and the Batch documentation + (https://cloud.google.com/batch/docs/). GCLOUD WIDE FLAGS These flags are available to all commands: --help. diff --git a/gcloud/beta/batch/tasks/help b/gcloud/beta/batch/tasks/help index 560785d12..a20f9f28a 100644 --- a/gcloud/beta/batch/tasks/help +++ b/gcloud/beta/batch/tasks/help @@ -5,7 +5,15 @@ SYNOPSIS gcloud beta batch tasks COMMAND [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) Manage Batch task resources. + (BETA) The gcloud batch tasks command group lets you describe and list + Batch tasks. + + With Batch, you can utilize the fully managed service to schedule, queue, + and execute batch jobs on Google's infrastructure. + + For more information about Batch, see the Batch overview + (https://cloud.google.com/batch) and the Batch documentation + (https://cloud.google.com/batch/docs/). GCLOUD WIDE FLAGS These flags are available to all commands: --help. diff --git a/gcloud/beta/builds/triggers/create/bitbucketserver b/gcloud/beta/builds/triggers/create/bitbucketserver new file mode 100644 index 000000000..3c2380997 --- /dev/null +++ b/gcloud/beta/builds/triggers/create/bitbucketserver @@ -0,0 +1,220 @@ +NAME + gcloud beta builds triggers create bitbucketserver - create a build trigger + for a Bitbucket Server repository + +SYNOPSIS + gcloud beta builds triggers create bitbucketserver + (--trigger-config=PATH + | [--bitbucket-server-config-resource=BITBUCKET_SERVER_CONFIG_RESOURCE --project-key=PROJECT_KEY --repo-slug=REPO_SLUG (--branch-pattern=REGEX | --tag-pattern=REGEX | [--pull-request-pattern=REGEX : --comment-control=COMMENT_CONTROL; default=CommentControlValueValuesEnum(COMMENTS_ENABLED, + 1)]) (--build-config=PATH | --inline-config=PATH + | --dockerfile=DOCKERFILE --dockerfile-dir=DOCKERFILE_DIR; + default="/" --dockerfile-image=DOCKERFILE_IMAGE) + : --description=DESCRIPTION --ignored-files=[GLOB,...] + --included-files=[GLOB,...] --name=NAME --require-approval + --service-account=SERVICE_ACCOUNT --substitutions=[KEY=VALUE,...]]) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Create a build trigger for a Bitbucket Server repository. + +EXAMPLES + To create a push trigger for all branches: + + $ gcloud beta builds triggers create bitbucketserver \ + --name="my-trigger" \ + --service-account="projects/my-project/serviceAccounts/my-byosa@\ + my-project.iam.gserviceaccount.com" \ + --project-key="GoogleCloudPlatform" \ + --repo-slug="cloud-builders" \ + --bitbucket-server-config-resource="projects/1234/locations/glob\ + al/bitbucketServerConfigs/5678" --branch-pattern=".*" \ + --build-config="cloudbuild.yaml" + + To create a pull request trigger for main: + + $ gcloud beta builds triggers create bitbucketserver \ + --name="my-trigger" \ + --service-account="projects/my-project/serviceAccounts/my-byosa@\ + my-project.iam.gserviceaccount.com" \ + --project-key="GoogleCloudPlatform" \ + --repo-slug="cloud-builders" \ + --bitbucket-server-config-resource="projects/1234/locations/glob\ + al/bitbucketServerConfigs/5678" --pull-request-pattern="^main$" \ + --build-config="cloudbuild.yaml" + +REQUIRED FLAGS + Exactly one of these must be specified: + + --trigger-config=PATH + Path to Build Trigger config file (JSON or YAML format). For more + details, see + https://cloud.google.com/cloud-build/docs/api/reference/rest/v1/projects.triggers#BuildTrigger + + Flag based trigger configuration + + --bitbucket-server-config-resource=BITBUCKET_SERVER_CONFIG_RESOURCE + Bitbucket Server config resource name. + + This flag argument must be specified if any of the other arguments + in this group are specified. + + --project-key=PROJECT_KEY + Bitbucket Server project key. + + This flag argument must be specified if any of the other arguments + in this group are specified. + + --repo-slug=REPO_SLUG + Bitbucket Server repository slug. + + This flag argument must be specified if any of the other arguments + in this group are specified. + + --description=DESCRIPTION + Build trigger description. + + --ignored-files=[GLOB,...] + Glob filter. Changes only affecting ignored files won't trigger + builds. + + --included-files=[GLOB,...] + Glob filter. Changes affecting at least one included file will + trigger builds. + + --name=NAME + Build trigger name. + + --require-approval + Require manual approval for triggered builds. + + --service-account=SERVICE_ACCOUNT + The service account used for all user-controlled operations + including UpdateBuildTrigger, RunBuildTrigger, CreateBuild, and + CancelBuild. If no service account is set, then the standard Cloud + Build service account ([PROJECT_NUM]@system.gserviceaccount.com) is + used instead. Format: + projects/{PROJECT_ID}/serviceAccounts/{ACCOUNT_ID_OR_EMAIL}. + + --substitutions=[KEY=VALUE,...] + Parameters to be substituted in the build specification. + + For example (using some nonsensical substitution keys; all keys + must begin with an underscore): + + $ gcloud builds triggers create ... --config config.yaml + --substitutions _FAVORITE_COLOR=blue,_NUM_CANDIES=10 + + This will result in a build where every occurrence of + ${_FAVORITE_COLOR} in certain fields is replaced by "blue", and + similarly for ${_NUM_CANDIES} and "10". + + Only the following built-in variables can be specified with the + --substitutions flag: REPO_NAME, BRANCH_NAME, TAG_NAME, + REVISION_ID, COMMIT_SHA, SHORT_SHA. + + For more details, see: + https://cloud.google.com/cloud-build/docs/api/build-requests#substitutions + + Exactly one of these must be specified: + + --branch-pattern=REGEX + A regular expression specifying which git branches to match. + + This pattern is used as a regex search for any incoming pushes. + For example, --branch-pattern=foo will match "foo", "foobar", and + "barfoo". Events on a branch that does not match will be ignored. + + The syntax of the regular expressions accepted is the syntax + accepted by RE2 and described at + https://github.com/google/re2/wiki/Syntax. + + --tag-pattern=REGEX + A regular expression specifying which git tags to match. + + This pattern is used as a regex search for any incoming pushes. + For example, --tag-pattern=foo will match "foo", "foobar", and + "barfoo". Events on a tag that does not match will be ignored. + + The syntax of the regular expressions accepted is the syntax + accepted by RE2 and described at + https://github.com/google/re2/wiki/Syntax. + + Pull Request settings + + --pull-request-pattern=REGEX + Regular expression specifying which base git branch to match + for pull request events. + + This pattern is used as a regex search for the base branch (the + branch you are trying to merge into) for pull request updates. + For example, --pull-request-pattern=foo will match "foo", + "foobar", and "barfoo". + + The syntax of the regular expressions accepted is the syntax + accepted by RE2 and described at + https://github.com/google/re2/wiki/Syntax. + + This flag argument must be specified if any of the other + arguments in this group are specified. + + --comment-control=COMMENT_CONTROL; default=CommentControlValueValuesEnum(COMMENTS_ENABLED, 1) + Require a repository collaborator or owner to comment '/gcbrun' + on a pull request before running the build. + + Exactly one of these must be specified: + + Build file configuration flags + + --build-config=PATH + Path to a YAML or JSON file containing the build configuration + in the repository. + + For more details, see: + https://cloud.google.com/cloud-build/docs/build-config + + Build configuration file + + --inline-config=PATH + Local path to a YAML or JSON file containing a build + configuration. + + Dockerfile build configuration flags + + --dockerfile=DOCKERFILE + Path of Dockerfile to use for builds in the repository. + + If specified, a build config will be generated to run docker + build using the specified file. + + The filename is relative to the Dockerfile directory. + + --dockerfile-dir=DOCKERFILE_DIR; default="/" + Location of the directory containing the Dockerfile in the + repository. + + The directory will also be used as the Docker build context. + + --dockerfile-image=DOCKERFILE_IMAGE + Docker image name to build. + + If not specified, + gcr.io/PROJECT/github.com/REPO_OWNER/REPO_NAME:$COMMIT_SHA will + be used. + + Use a build configuration (cloudbuild.yaml) file for building + multiple images in a single trigger. + +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 builds triggers create bitbucketserver + diff --git a/gcloud/beta/builds/triggers/create/gitlab-enterprise b/gcloud/beta/builds/triggers/create/gitlab-enterprise new file mode 100644 index 000000000..4ffd04254 --- /dev/null +++ b/gcloud/beta/builds/triggers/create/gitlab-enterprise @@ -0,0 +1,219 @@ +NAME + gcloud beta builds triggers create gitlab-enterprise - create a build + trigger for a GitLab Enterprise repository + +SYNOPSIS + gcloud beta builds triggers create gitlab-enterprise + (--trigger-config=PATH + | [--gitlab-config-resource=GITLAB_CONFIG_RESOURCE + --project-namespace=PROJECT_NAMESPACE + --region=REGION (--branch-pattern=REGEX | --tag-pattern=REGEX + | [--pull-request-pattern=REGEX : --comment-control=COMMENT_CONTROL; + default=CommentControlValueValuesEnum(COMMENTS_ENABLED, + 1)]) (--build-config=PATH | --inline-config=PATH + | --dockerfile=DOCKERFILE --dockerfile-dir=DOCKERFILE_DIR; + default="/" --dockerfile-image=DOCKERFILE_IMAGE) + : --description=DESCRIPTION --ignored-files=[GLOB,...] + --included-files=[GLOB,...] --name=NAME --require-approval + --service-account=SERVICE_ACCOUNT --substitutions=[KEY=VALUE,...]]) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Create a build trigger for a GitLab Enterprise repository. + +EXAMPLES + To create a push trigger for all branches: + + $ gcloud beta builds triggers create gitlab-enterprise \ + --name="my-trigger" \ + --service-account="projects/my-project/serviceAccounts/my-byosa@\ + my-project.iam.gserviceaccount.com" \ + --project-namespace="cloud-builders" \ + --gitlab-config-resource="projects/1234/locations/global/gitLabC\ + onfigs/5678" --branch-pattern=".*" --build-config="cloudbuild.yaml" + + To create a pull request trigger for main: + + $ gcloud beta builds triggers create gitlab-enterprise \ + --name="my-trigger" \ + --service-account="projects/my-project/serviceAccounts/my-byosa@\ + my-project.iam.gserviceaccount.com" \ + --project-namespace="cloud-builders" \ + --gitlab-config-resource="projects/1234/locations/global/gitLabC\ + onfigs/5678" --pull-request-pattern="^main$" \ + --build-config="cloudbuild.yaml" + +REQUIRED FLAGS + Exactly one of these must be specified: + + --trigger-config=PATH + Path to Build Trigger config file (JSON or YAML format). For more + details, see + https://cloud.google.com/cloud-build/docs/api/reference/rest/v1/projects.triggers#BuildTrigger + + Flag based trigger configuration + + --gitlab-config-resource=GITLAB_CONFIG_RESOURCE + GitLab config resource name. + + This flag argument must be specified if any of the other arguments + in this group are specified. + + --project-namespace=PROJECT_NAMESPACE + GitLab project namespace. + + This flag argument must be specified if any of the other arguments + in this group are specified. + + --region=REGION + The region of the Cloud Build Service to use. Must be set to a + supported region name (e.g. us-central1). If unset, builds/region + is used. If builds/region is unset,region is set to "global". + + This flag argument must be specified if any of the other arguments + in this group are specified. + + --description=DESCRIPTION + Build trigger description. + + --ignored-files=[GLOB,...] + Glob filter. Changes only affecting ignored files won't trigger + builds. + + --included-files=[GLOB,...] + Glob filter. Changes affecting at least one included file will + trigger builds. + + --name=NAME + Build trigger name. + + --require-approval + Require manual approval for triggered builds. + + --service-account=SERVICE_ACCOUNT + The service account used for all user-controlled operations + including UpdateBuildTrigger, RunBuildTrigger, CreateBuild, and + CancelBuild. If no service account is set, then the standard Cloud + Build service account ([PROJECT_NUM]@system.gserviceaccount.com) is + used instead. Format: + projects/{PROJECT_ID}/serviceAccounts/{ACCOUNT_ID_OR_EMAIL}. + + --substitutions=[KEY=VALUE,...] + Parameters to be substituted in the build specification. + + For example (using some nonsensical substitution keys; all keys + must begin with an underscore): + + $ gcloud builds triggers create ... --config config.yaml + --substitutions _FAVORITE_COLOR=blue,_NUM_CANDIES=10 + + This will result in a build where every occurrence of + ${_FAVORITE_COLOR} in certain fields is replaced by "blue", and + similarly for ${_NUM_CANDIES} and "10". + + Only the following built-in variables can be specified with the + --substitutions flag: REPO_NAME, BRANCH_NAME, TAG_NAME, + REVISION_ID, COMMIT_SHA, SHORT_SHA. + + For more details, see: + https://cloud.google.com/cloud-build/docs/api/build-requests#substitutions + + Exactly one of these must be specified: + + --branch-pattern=REGEX + A regular expression specifying which git branches to match. + + This pattern is used as a regex search for any incoming pushes. + For example, --branch-pattern=foo will match "foo", "foobar", and + "barfoo". Events on a branch that does not match will be ignored. + + The syntax of the regular expressions accepted is the syntax + accepted by RE2 and described at + https://github.com/google/re2/wiki/Syntax. + + --tag-pattern=REGEX + A regular expression specifying which git tags to match. + + This pattern is used as a regex search for any incoming pushes. + For example, --tag-pattern=foo will match "foo", "foobar", and + "barfoo". Events on a tag that does not match will be ignored. + + The syntax of the regular expressions accepted is the syntax + accepted by RE2 and described at + https://github.com/google/re2/wiki/Syntax. + + Pull Request settings + + --pull-request-pattern=REGEX + Regular expression specifying which base git branch to match + for pull request events. + + This pattern is used as a regex search for the base branch (the + branch you are trying to merge into) for pull request updates. + For example, --pull-request-pattern=foo will match "foo", + "foobar", and "barfoo". + + The syntax of the regular expressions accepted is the syntax + accepted by RE2 and described at + https://github.com/google/re2/wiki/Syntax. + + This flag argument must be specified if any of the other + arguments in this group are specified. + + --comment-control=COMMENT_CONTROL; default=CommentControlValueValuesEnum(COMMENTS_ENABLED, 1) + Require a repository collaborator or owner to comment '/gcbrun' + on a pull request before running the build. + + Exactly one of these must be specified: + + --build-config=PATH + Path to a YAML or JSON file containing the build configuration in + the repository. + + For more details, see: + https://cloud.google.com/cloud-build/docs/build-config + + --inline-config=PATH + Local path to a YAML or JSON file containing a build + configuration. + + Dockerfile build configuration flags + + --dockerfile=DOCKERFILE + Path of Dockerfile to use for builds in the repository. + + If specified, a build config will be generated to run docker + build using the specified file. + + The filename is relative to the Dockerfile directory. + + --dockerfile-dir=DOCKERFILE_DIR; default="/" + Location of the directory containing the Dockerfile in the + repository. + + The directory will also be used as the Docker build context. + + --dockerfile-image=DOCKERFILE_IMAGE + Docker image name to build. + + If not specified, + gcr.io/PROJECT/github.com/REPO_OWNER/REPO_NAME:$COMMIT_SHA will + be used. + + Use a build configuration (cloudbuild.yaml) file for building + multiple images in a single trigger. + +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 builds triggers create gitlab-enterprise + diff --git a/gcloud/beta/builds/triggers/create/help b/gcloud/beta/builds/triggers/create/help index f009de8df..01a9550e3 100644 --- a/gcloud/beta/builds/triggers/create/help +++ b/gcloud/beta/builds/triggers/create/help @@ -16,12 +16,27 @@ GCLOUD WIDE FLAGS COMMANDS COMMAND is one of the following: + bitbucketserver + (BETA) Create a build trigger for a Bitbucket Server repository. + cloud-source-repositories (BETA) Create a build trigger from a Cloud Source Repository. github (BETA) Create a build trigger for a GitHub repository. + gitlab-enterprise + (BETA) Create a build trigger for a GitLab Enterprise repository. + + manual + (BETA) Create a build trigger with a manual trigger event. + + pubsub + (BETA) Create a build trigger with a Pub/Sub trigger event. + + webhook + (BETA) Create a build trigger with a Webhook trigger event. + NOTES This command is currently in beta and might change without notice. This variant is also available: diff --git a/gcloud/beta/builds/triggers/create/manual b/gcloud/beta/builds/triggers/create/manual new file mode 100644 index 000000000..dc04896d3 --- /dev/null +++ b/gcloud/beta/builds/triggers/create/manual @@ -0,0 +1,161 @@ +NAME + gcloud beta builds triggers create manual - create a build trigger with a + manual trigger event + +SYNOPSIS + gcloud beta builds triggers create manual + (--trigger-config=PATH | [(--build-config=PATH | --inline-config=PATH + | --dockerfile=DOCKERFILE --dockerfile-dir=DOCKERFILE_DIR; + default="/" --dockerfile-image=DOCKERFILE_IMAGE) + : --description=DESCRIPTION --name=NAME --require-approval + --service-account=SERVICE_ACCOUNT + --subscription-filter=SUBSCRIPTION_FILTER + --substitutions=[KEY=VALUE,...] + --repo=REPO --repo-type=REPO_TYPE (--branch=BRANCH | --tag=TAG)]) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Create a build trigger with a manual trigger event. + +EXAMPLES + To create a manual trigger that builds off branch my-branch in a GitHub + repository named my-repo: + + $ gcloud beta builds triggers create manual \ + --name=my-manual-trigger --build-config=cloudbuild.yaml \ + --repo=https://www.github.com/owner/repo --repo-type=GITHUB \ + --branch=my-branch + +REQUIRED FLAGS + Exactly one of these must be specified: + + --trigger-config=PATH + Path to Build Trigger config file (JSON or YAML format). For more + details, see + https://cloud.google.com/cloud-build/docs/api/reference/rest/v1/projects.triggers#BuildTrigger + + Flag based trigger configuration + + --description=DESCRIPTION + Build trigger description. + + --name=NAME + Build trigger name. + + --require-approval + Require manual approval for triggered builds. + + --service-account=SERVICE_ACCOUNT + The service account used for all user-controlled operations + including UpdateBuildTrigger, RunBuildTrigger, CreateBuild, and + CancelBuild. If no service account is set, then the standard Cloud + Build service account ([PROJECT_NUM]@system.gserviceaccount.com) is + used instead. Format: + projects/{PROJECT_ID}/serviceAccounts/{ACCOUNT_ID_OR_EMAIL}. + + --subscription-filter=SUBSCRIPTION_FILTER + CEL filter expression for the trigger. See + https://cloud.google.com/build/docs/filter-build-events-using-cel + for more details. + + --substitutions=[KEY=VALUE,...] + Parameters to be substituted in the build specification. + + For example (using some nonsensical substitution keys; all keys + must begin with an underscore): + + $ gcloud builds triggers create ... --config config.yaml + --substitutions _FAVORITE_COLOR=blue,_NUM_CANDIES=10 + + This will result in a build where every occurrence of + ${_FAVORITE_COLOR} in certain fields is replaced by "blue", and + similarly for ${_NUM_CANDIES} and "10". + + Only the following built-in variables can be specified with the + --substitutions flag: REPO_NAME, BRANCH_NAME, TAG_NAME, + REVISION_ID, COMMIT_SHA, SHORT_SHA. + + For more details, see: + https://cloud.google.com/cloud-build/docs/api/build-requests#substitutions + + Exactly one of these must be specified: + + Build file configuration flags + + --build-config=PATH + Path to a YAML or JSON file containing the build configuration + in the repository. + + For more details, see: + https://cloud.google.com/cloud-build/docs/build-config + + Build configuration file + + --inline-config=PATH + Local path to a YAML or JSON file containing a build + configuration. + + Dockerfile build configuration flags + + --dockerfile=DOCKERFILE + Path of Dockerfile to use for builds in the repository. + + If specified, a build config will be generated to run docker + build using the specified file. + + The filename is relative to the Dockerfile directory. + + --dockerfile-dir=DOCKERFILE_DIR; default="/" + Location of the directory containing the Dockerfile in the + repository. + + The directory will also be used as the Docker build context. + + --dockerfile-image=DOCKERFILE_IMAGE + Docker image name to build. + + If not specified, + gcr.io/PROJECT/github.com/REPO_OWNER/REPO_NAME:$COMMIT_SHA will + be used. + + Use a build configuration (cloudbuild.yaml) file for building + multiple images in a single trigger. + + Flags for repository information + + --repo=REPO + URI of the repository. Currently only HTTP URIs for GitHub and + Cloud Source Repositories are supported. + + This flag argument must be specified if any of the other + arguments in this group are specified. + + --repo-type=REPO_TYPE + Type of the repository. Currently only GitHub and Cloud Source + Repository types are supported. + + This flag argument must be specified if any of the other + arguments in this group are specified. + + Exactly one of these must be specified: + + --branch=BRANCH + Branch to build. + + --tag=TAG + Tag to build. + +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 builds triggers create manual + diff --git a/gcloud/beta/builds/triggers/create/pubsub b/gcloud/beta/builds/triggers/create/pubsub new file mode 100644 index 000000000..3edcd65ea --- /dev/null +++ b/gcloud/beta/builds/triggers/create/pubsub @@ -0,0 +1,171 @@ +NAME + gcloud beta builds triggers create pubsub - create a build trigger with a + Pub/Sub trigger event + +SYNOPSIS + gcloud beta builds triggers create pubsub + (--trigger-config=PATH | [--topic=TOPIC (--build-config=PATH + | --inline-config=PATH | --dockerfile=DOCKERFILE + --dockerfile-dir=DOCKERFILE_DIR; + default="/" --dockerfile-image=DOCKERFILE_IMAGE) + : --description=DESCRIPTION --name=NAME --require-approval + --service-account=SERVICE_ACCOUNT + --subscription-filter=SUBSCRIPTION_FILTER + --substitutions=[KEY=VALUE,...] + --repo=REPO --repo-type=REPO_TYPE (--branch=BRANCH | --tag=TAG)]) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Create a build trigger with a Pub/Sub trigger event. + +EXAMPLES + To create a Pub/Sub trigger that listens to topic my-topic and builds off + branch my-branch in a GitHub repository named my-repo: + + $ gcloud beta builds triggers create pubsub \ + --name=my-pubsub-trigger \ + --service-account="projects/my-project/serviceAccounts/my-byosa@\ + my-project.iam.gserviceaccount.com" \ + --topic=projects/my-project/topics/my-topic \ + --repo=https://www.github.com/owner/repo --repo-type=GITHUB \ + --branch=my-branch + +REQUIRED FLAGS + Exactly one of these must be specified: + + --trigger-config=PATH + Path to Build Trigger config file (JSON or YAML format). For more + details, see + https://cloud.google.com/cloud-build/docs/api/reference/rest/v1/projects.triggers#BuildTrigger + + Flag based trigger configuration + + --topic=TOPIC + The topic to which this trigger should subscribe. + + This flag argument must be specified if any of the other arguments + in this group are specified. + + --description=DESCRIPTION + Build trigger description. + + --name=NAME + Build trigger name. + + --require-approval + Require manual approval for triggered builds. + + --service-account=SERVICE_ACCOUNT + The service account used for all user-controlled operations + including UpdateBuildTrigger, RunBuildTrigger, CreateBuild, and + CancelBuild. If no service account is set, then the standard Cloud + Build service account ([PROJECT_NUM]@system.gserviceaccount.com) is + used instead. Format: + projects/{PROJECT_ID}/serviceAccounts/{ACCOUNT_ID_OR_EMAIL}. + + --subscription-filter=SUBSCRIPTION_FILTER + CEL filter expression for the trigger. See + https://cloud.google.com/build/docs/filter-build-events-using-cel + for more details. + + --substitutions=[KEY=VALUE,...] + Parameters to be substituted in the build specification. + + For example (using some nonsensical substitution keys; all keys + must begin with an underscore): + + $ gcloud builds triggers create ... --config config.yaml + --substitutions _FAVORITE_COLOR=blue,_NUM_CANDIES=10 + + This will result in a build where every occurrence of + ${_FAVORITE_COLOR} in certain fields is replaced by "blue", and + similarly for ${_NUM_CANDIES} and "10". + + Only the following built-in variables can be specified with the + --substitutions flag: REPO_NAME, BRANCH_NAME, TAG_NAME, + REVISION_ID, COMMIT_SHA, SHORT_SHA. + + For more details, see: + https://cloud.google.com/cloud-build/docs/api/build-requests#substitutions + + Exactly one of these must be specified: + + Build file configuration flags + + --build-config=PATH + Path to a YAML or JSON file containing the build configuration + in the repository. + + For more details, see: + https://cloud.google.com/cloud-build/docs/build-config + + Build configuration file + + --inline-config=PATH + Local path to a YAML or JSON file containing a build + configuration. + + Dockerfile build configuration flags + + --dockerfile=DOCKERFILE + Path of Dockerfile to use for builds in the repository. + + If specified, a build config will be generated to run docker + build using the specified file. + + The filename is relative to the Dockerfile directory. + + --dockerfile-dir=DOCKERFILE_DIR; default="/" + Location of the directory containing the Dockerfile in the + repository. + + The directory will also be used as the Docker build context. + + --dockerfile-image=DOCKERFILE_IMAGE + Docker image name to build. + + If not specified, + gcr.io/PROJECT/github.com/REPO_OWNER/REPO_NAME:$COMMIT_SHA will + be used. + + Use a build configuration (cloudbuild.yaml) file for building + multiple images in a single trigger. + + Flags for repository information + + --repo=REPO + URI of the repository. Currently only HTTP URIs for GitHub and + Cloud Source Repositories are supported. + + This flag argument must be specified if any of the other + arguments in this group are specified. + + --repo-type=REPO_TYPE + Type of the repository. Currently only GitHub and Cloud Source + Repository types are supported. + + This flag argument must be specified if any of the other + arguments in this group are specified. + + Exactly one of these must be specified: + + --branch=BRANCH + Branch to build. + + --tag=TAG + Tag to build. + +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 builds triggers create pubsub + diff --git a/gcloud/beta/builds/triggers/create/webhook b/gcloud/beta/builds/triggers/create/webhook new file mode 100644 index 000000000..d5a413afe --- /dev/null +++ b/gcloud/beta/builds/triggers/create/webhook @@ -0,0 +1,174 @@ +NAME + gcloud beta builds triggers create webhook - create a build trigger with a + Webhook trigger event + +SYNOPSIS + gcloud beta builds triggers create webhook + (--trigger-config=PATH | [--secret=SECRET (--build-config=PATH + | --inline-config=PATH | --dockerfile=DOCKERFILE + --dockerfile-dir=DOCKERFILE_DIR; + default="/" --dockerfile-image=DOCKERFILE_IMAGE) + : --description=DESCRIPTION --name=NAME --require-approval + --service-account=SERVICE_ACCOUNT + --subscription-filter=SUBSCRIPTION_FILTER + --substitutions=[KEY=VALUE,...] + --repo=REPO --repo-type=REPO_TYPE (--branch=BRANCH | --tag=TAG)]) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Create a build trigger with a Webhook trigger event. + +EXAMPLES + To create a Webhook trigger that requires secret + projects/my-project/secrets/my-secret/versions/2 and builds off branch + my-branch in a GitHub repository named my-repo: + + $ gcloud beta builds triggers create webhook \ + --name=my-webhook-trigger \ + --service-account="projects/my-project/serviceAccounts/my-byosa@\ + my-project.iam.gserviceaccount.com" \ + --secret=projects/my-project/secrets/my-secret/versions/2 \ + --repo=https://www.github.com/owner/repo --repo-type=GITHUB \ + --branch=my-branch + +REQUIRED FLAGS + Exactly one of these must be specified: + + --trigger-config=PATH + Path to Build Trigger config file (JSON or YAML format). For more + details, see + https://cloud.google.com/cloud-build/docs/api/reference/rest/v1/projects.triggers#BuildTrigger + + Flag based trigger configuration + + --secret=SECRET + The full path of the secret version required to validate webhook + requests against this trigger. For example, + projects/my-project/secrets/my-secret/versions/1. + + This flag argument must be specified if any of the other arguments + in this group are specified. + + --description=DESCRIPTION + Build trigger description. + + --name=NAME + Build trigger name. + + --require-approval + Require manual approval for triggered builds. + + --service-account=SERVICE_ACCOUNT + The service account used for all user-controlled operations + including UpdateBuildTrigger, RunBuildTrigger, CreateBuild, and + CancelBuild. If no service account is set, then the standard Cloud + Build service account ([PROJECT_NUM]@system.gserviceaccount.com) is + used instead. Format: + projects/{PROJECT_ID}/serviceAccounts/{ACCOUNT_ID_OR_EMAIL}. + + --subscription-filter=SUBSCRIPTION_FILTER + CEL filter expression for the trigger. See + https://cloud.google.com/build/docs/filter-build-events-using-cel + for more details. + + --substitutions=[KEY=VALUE,...] + Parameters to be substituted in the build specification. + + For example (using some nonsensical substitution keys; all keys + must begin with an underscore): + + $ gcloud builds triggers create ... --config config.yaml + --substitutions _FAVORITE_COLOR=blue,_NUM_CANDIES=10 + + This will result in a build where every occurrence of + ${_FAVORITE_COLOR} in certain fields is replaced by "blue", and + similarly for ${_NUM_CANDIES} and "10". + + Only the following built-in variables can be specified with the + --substitutions flag: REPO_NAME, BRANCH_NAME, TAG_NAME, + REVISION_ID, COMMIT_SHA, SHORT_SHA. + + For more details, see: + https://cloud.google.com/cloud-build/docs/api/build-requests#substitutions + + Exactly one of these must be specified: + + Build file configuration flags + + --build-config=PATH + Path to a YAML or JSON file containing the build configuration + in the repository. + + For more details, see: + https://cloud.google.com/cloud-build/docs/build-config + + Build configuration file + + --inline-config=PATH + Local path to a YAML or JSON file containing a build + configuration. + + Dockerfile build configuration flags + + --dockerfile=DOCKERFILE + Path of Dockerfile to use for builds in the repository. + + If specified, a build config will be generated to run docker + build using the specified file. + + The filename is relative to the Dockerfile directory. + + --dockerfile-dir=DOCKERFILE_DIR; default="/" + Location of the directory containing the Dockerfile in the + repository. + + The directory will also be used as the Docker build context. + + --dockerfile-image=DOCKERFILE_IMAGE + Docker image name to build. + + If not specified, + gcr.io/PROJECT/github.com/REPO_OWNER/REPO_NAME:$COMMIT_SHA will + be used. + + Use a build configuration (cloudbuild.yaml) file for building + multiple images in a single trigger. + + Flags for repository information + + --repo=REPO + URI of the repository. Currently only HTTP URIs for GitHub and + Cloud Source Repositories are supported. + + This flag argument must be specified if any of the other + arguments in this group are specified. + + --repo-type=REPO_TYPE + Type of the repository. Currently only GitHub and Cloud Source + Repository types are supported. + + This flag argument must be specified if any of the other + arguments in this group are specified. + + Exactly one of these must be specified: + + --branch=BRANCH + Branch to build. + + --tag=TAG + Tag to build. + +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 builds triggers create webhook + diff --git a/gcloud/beta/compute/commitments/create b/gcloud/beta/compute/commitments/create index 6c304c9bb..30218d1d9 100644 --- a/gcloud/beta/compute/commitments/create +++ b/gcloud/beta/compute/commitments/create @@ -155,10 +155,10 @@ OPTIONAL FLAGS The size of the local SSD in base-2 GB. --machine-type=MACHINE_TYPE - The type of machine (name only) which has a fixed number of vCPUs - and a fixed amount of memory. This also includes specifying - custom machine type following - custom-number_of_CPUs-amount_of_memory pattern, e.g. + The type of machine (name only) that has a fixed number of vCPUs + and a fixed amount of memory. You can also specify a custom + machine type by using the pattern + custom-number_of_CPUs-amount_of_memory-for example, custom-32-29440. --maintenance-interval=MAINTENANCE_INTERVAL diff --git a/gcloud/beta/compute/firewall-rules/create b/gcloud/beta/compute/firewall-rules/create index bdab12ad5..0c3674a79 100644 --- a/gcloud/beta/compute/firewall-rules/create +++ b/gcloud/beta/compute/firewall-rules/create @@ -103,9 +103,8 @@ OPTIONAL FLAGS --direction=DIRECTION If direction is NOT specified, then default is to apply on incoming - traffic. For incoming traffic, it is NOT supported to specify - destination-ranges; For outbound traffic, it is NOT supported to - specify source-ranges or source-tags. + traffic. For outbound traffic, it is NOT supported to specify + source-tags. For convenience, 'IN' can be used to represent ingress direction and 'OUT' can be used to represent egress direction. diff --git a/gcloud/beta/compute/reservations/create b/gcloud/beta/compute/reservations/create index 6037fae3a..7102e8194 100644 --- a/gcloud/beta/compute/reservations/create +++ b/gcloud/beta/compute/reservations/create @@ -4,11 +4,11 @@ NAME SYNOPSIS gcloud beta compute reservations create RESERVATION - (--machine-type=MACHINE_TYPE --vm-count=VM_COUNT + (--vm-count=VM_COUNT ([--machine-type=MACHINE_TYPE : --accelerator=[count=COUNT],[type=TYPE] --local-ssd=[interface=INTERFACE],[size=SIZE] - --min-cpu-platform=MIN_CPU_PLATFORM - --require-specific-reservation --resource-policies=[KEY=VALUE,...]) + --min-cpu-platform=MIN_CPU_PLATFORM]) + : --require-specific-reservation --resource-policies=[KEY=VALUE,...]) [--description=DESCRIPTION] [--zone=ZONE] [--share-setting=SHARE_SETTING --share-with=SHARE_WITH,[SHARE_WITH,...]] [GCLOUD_WIDE_FLAG ...] @@ -28,19 +28,10 @@ POSITIONAL ARGUMENTS Name of the reservation to create. REQUIRED FLAGS - Manage the specific SKU reservation properties. + Manage the SpecificSKU reservation properties. This must be specified. - --machine-type=MACHINE_TYPE - The type of machine (name only) which has a fixed number of vCPUs and - a fixed amount of memory. This also includes specifying custom - machine type following custom-number_of_CPUs-amount_of_memory - pattern, e.g. custom-32-29440. - - This flag argument must be specified if any of the other arguments in - this group are specified. - --vm-count=VM_COUNT The number of VM instances that are allocated to this reservation. The value of this field must be an int in the range [1, 1000]. @@ -48,33 +39,6 @@ REQUIRED FLAGS This flag argument must be specified if any of the other arguments in this group are specified. - --accelerator=[count=COUNT],[type=TYPE] - Manage the configuration of the type and number of accelerator cards - attached. - count - The number of accelerators to attach to each instance in the - reservation. - type - The specific type (e.g. nvidia-tesla-k80 for nVidia Tesla K80) of - accelerator to attach to instances in the reservation. Use gcloud - compute accelerator-types list to learn about all available - accelerator types. - - --local-ssd=[interface=INTERFACE],[size=SIZE] - Manage the size and the interface of local SSD to use. See - https://cloud.google.com/compute/docs/disks/local-ssd for more - information. - interface - 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 may provide higher - performance. - size - The size of the local SSD in base-2 GB. - - --min-cpu-platform=MIN_CPU_PLATFORM - Optional minimum CPU platform of the reservation to create. - --require-specific-reservation Indicates whether the reservation can be consumed by VMs with "any reservation" defined. If enabled, then only VMs that target this @@ -85,6 +49,50 @@ REQUIRED FLAGS Specify if this is reservation with resource policy. If you omit this flag, no resource policy will be added to this reservation. + Manage the instance properties for the SpecificSKU reservation. + + This must be specified. + + Define the individual instance properties for the SpecificSKU + reservation. + + --machine-type=MACHINE_TYPE + The type of machine (name only) that has a fixed number of vCPUs + and a fixed amount of memory. You can also specify a custom + machine type by using the pattern + custom-number_of_CPUs-amount_of_memory-for example, + custom-32-29440. + + This flag argument must be specified if any of the other + arguments in this group are specified. + + --accelerator=[count=COUNT],[type=TYPE] + Manage the configuration of the type and number of accelerator + cards attached. + count + The number of accelerators to attach to each instance in the + reservation. + type + The specific type (e.g. nvidia-tesla-k80 for nVidia Tesla + K80) of accelerator to attach to instances in the + reservation. Use gcloud compute accelerator-types list to + learn about all available accelerator types. + + --local-ssd=[interface=INTERFACE],[size=SIZE] + Manage the size and the interface of local SSD to use. See + https://cloud.google.com/compute/docs/disks/local-ssd for more + information. + interface + 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 may provide + higher performance. + size + The size of the local SSD in base-2 GB. + + --min-cpu-platform=MIN_CPU_PLATFORM + Optional minimum CPU platform of the reservation to create. + OPTIONAL FLAGS --description=DESCRIPTION An optional description of the reservation to create. diff --git a/gcloud/beta/config/get b/gcloud/beta/config/get index e62832075..9af9ad7e5 100644 --- a/gcloud/beta/config/get +++ b/gcloud/beta/config/get @@ -306,8 +306,8 @@ AVAILABLE PROPERTIES Overrides API endpoint for gcloud genomics command group. gkemulticloud - Overrides API endpoint for gcloud container aws and gcloud - container azure command groups. + Overrides API endpoint for gcloud container aws, gcloud container + azure and gcloud container attached command groups. healthcare Overrides API endpoint for gcloud healthcare command group. @@ -610,6 +610,10 @@ AVAILABLE PROPERTIES If True, use the cluster's client certificate to authenticate to the cluster API server. + container_attached + location + Default Google Cloud location to use for Attached clusters. + container_aws location Default Google Cloud location to use for Anthos clusters on AWS. diff --git a/gcloud/beta/config/help b/gcloud/beta/config/help index 417812259..fd1cf3b33 100644 --- a/gcloud/beta/config/help +++ b/gcloud/beta/config/help @@ -338,8 +338,8 @@ AVAILABLE PROPERTIES Overrides API endpoint for gcloud genomics command group. gkemulticloud - Overrides API endpoint for gcloud container aws and gcloud - container azure command groups. + Overrides API endpoint for gcloud container aws, gcloud container + azure and gcloud container attached command groups. healthcare Overrides API endpoint for gcloud healthcare command group. @@ -642,6 +642,10 @@ AVAILABLE PROPERTIES If True, use the cluster's client certificate to authenticate to the cluster API server. + container_attached + location + Default Google Cloud location to use for Attached clusters. + container_aws location Default Google Cloud location to use for Anthos clusters on AWS. diff --git a/gcloud/beta/config/list b/gcloud/beta/config/list index 92066cdf2..7b1de02e1 100644 --- a/gcloud/beta/config/list +++ b/gcloud/beta/config/list @@ -344,8 +344,8 @@ AVAILABLE PROPERTIES Overrides API endpoint for gcloud genomics command group. gkemulticloud - Overrides API endpoint for gcloud container aws and gcloud - container azure command groups. + Overrides API endpoint for gcloud container aws, gcloud container + azure and gcloud container attached command groups. healthcare Overrides API endpoint for gcloud healthcare command group. @@ -648,6 +648,10 @@ AVAILABLE PROPERTIES If True, use the cluster's client certificate to authenticate to the cluster API server. + container_attached + location + Default Google Cloud location to use for Attached clusters. + container_aws location Default Google Cloud location to use for Anthos clusters on AWS. diff --git a/gcloud/beta/config/set b/gcloud/beta/config/set index b74c7fc7e..e473355e8 100644 --- a/gcloud/beta/config/set +++ b/gcloud/beta/config/set @@ -353,8 +353,8 @@ AVAILABLE PROPERTIES Overrides API endpoint for gcloud genomics command group. gkemulticloud - Overrides API endpoint for gcloud container aws and gcloud - container azure command groups. + Overrides API endpoint for gcloud container aws, gcloud container + azure and gcloud container attached command groups. healthcare Overrides API endpoint for gcloud healthcare command group. @@ -657,6 +657,10 @@ AVAILABLE PROPERTIES If True, use the cluster's client certificate to authenticate to the cluster API server. + container_attached + location + Default Google Cloud location to use for Attached clusters. + container_aws location Default Google Cloud location to use for Anthos clusters on AWS. diff --git a/gcloud/beta/config/unset b/gcloud/beta/config/unset index 2d7187fa9..22c894275 100644 --- a/gcloud/beta/config/unset +++ b/gcloud/beta/config/unset @@ -314,8 +314,8 @@ AVAILABLE PROPERTIES Overrides API endpoint for gcloud genomics command group. gkemulticloud - Overrides API endpoint for gcloud container aws and gcloud - container azure command groups. + Overrides API endpoint for gcloud container aws, gcloud container + azure and gcloud container attached command groups. healthcare Overrides API endpoint for gcloud healthcare command group. @@ -618,6 +618,10 @@ AVAILABLE PROPERTIES If True, use the cluster's client certificate to authenticate to the cluster API server. + container_attached + location + Default Google Cloud location to use for Attached clusters. + container_aws location Default Google Cloud location to use for Anthos clusters on AWS. diff --git a/gcloud/beta/container/clusters/create b/gcloud/beta/container/clusters/create index 7c9ba0aaf..d3655f770 100644 --- a/gcloud/beta/container/clusters/create +++ b/gcloud/beta/container/clusters/create @@ -37,7 +37,7 @@ SYNOPSIS [--identity-provider=IDENTITY_PROVIDER] [--image-type=IMAGE_TYPE] [--ipv6-access-type=IPV6_ACCESS_TYPE] [--issue-client-certificate] [--istio-config=[auth=MTLS_PERMISSIVE,...]] [--labels=[KEY=VALUE,...]] - [--logging=[COMPONENT,...]] + [--logging=[COMPONENT,...]] [--logging-variant=LOGGING_VARIANT] [--machine-type=MACHINE_TYPE, -m MACHINE_TYPE] [--max-nodes-per-pool=MAX_NODES_PER_POOL] [--max-pods-per-node=MAX_PODS_PER_NODE] @@ -599,6 +599,18 @@ FLAGS $ gcloud beta container clusters create --logging=SYSTEM,WORKLOAD $ gcloud beta container clusters create --logging=NONE + --logging-variant=LOGGING_VARIANT + Specifies the logging variant that will be deployed on all the nodes in + the cluster. Valid logging variants are MAX_THROUGHPUT, DEFAULT. If no + value is specified, DEFAULT is used. LOGGING_VARIANT must be one of: + + DEFAULT + 'DEFAULT' variant requests minimal resources but may not guarantee + high throughput. + MAX_THROUGHPUT + 'MAX_THROUGHPUT' variant requests more node resources and is able + to achieve logging throughput up to 10MB per sec. + --machine-type=MACHINE_TYPE, -m MACHINE_TYPE The type of machine to use for nodes. Defaults to e2-medium. The list of predefined machine types is available using the following command: @@ -1181,11 +1193,11 @@ FLAGS autoprovisioned node pool. Node Management settings are specified under the field - 'nodeManagement', which has the following fields: - enableAutoUpgrade: A boolean field that indicates if node - autoupgrade is enabled for autoprovisioned node pools. - enableAutoRepair: A boolean field that indicates if node autorepair - is enabled for autoprovisioned node pools. + 'management', which has the following fields: autoUpgrade: A + boolean field that indicates if node autoupgrade is enabled for + autoprovisioned node pools. autoRepair: A boolean field that + indicates if node autorepair is enabled for autoprovisioned node + pools. minCpuPlatform (deprecated): If specified, new autoprovisioned nodes will be scheduled on host with specified CPU architecture or diff --git a/gcloud/beta/container/clusters/update b/gcloud/beta/container/clusters/update index 0ee8513b2..93ca53976 100644 --- a/gcloud/beta/container/clusters/update +++ b/gcloud/beta/container/clusters/update @@ -20,7 +20,7 @@ SYNOPSIS | --enable-service-externalips | --enable-shielded-nodes | --enable-stackdriver-kubernetes | --enable-vertical-pod-autoscaling | --generate-password | --identity-provider=IDENTITY_PROVIDER - | --maintenance-window=START_TIME + | --logging-variant=LOGGING_VARIANT | --maintenance-window=START_TIME | --notification-config=[pubsub=ENABLED|DISABLED, pubsub-topic=TOPIC,...] | --private-ipv6-google-access-type=PRIVATE_IPV6_GOOGLE_ACCESS_TYPE @@ -317,6 +317,19 @@ REQUIRED FLAGS --identity-provider=IDENTITY_PROVIDER Enable 3P identity provider on the cluster. + --logging-variant=LOGGING_VARIANT + Specifies the logging variant that will be deployed on all the nodes + in the cluster. Valid logging variants are MAX_THROUGHPUT, DEFAULT. + If no value is specified, DEFAULT is used. LOGGING_VARIANT must be + one of: + + DEFAULT + 'DEFAULT' variant requests minimal resources but may not + guarantee high throughput. + MAX_THROUGHPUT + 'MAX_THROUGHPUT' variant requests more node resources and is able + to achieve logging throughput up to 10MB per sec. + --maintenance-window=START_TIME Set a time of day when you prefer maintenance to start on this cluster. For example: @@ -776,11 +789,11 @@ REQUIRED FLAGS the same time on each upgrade of an autoprovisioned node pool. Node Management settings are specified under the field - 'nodeManagement', which has the following fields: - enableAutoUpgrade: A boolean field that indicates if node - autoupgrade is enabled for autoprovisioned node pools. - enableAutoRepair: A boolean field that indicates if node - autorepair is enabled for autoprovisioned node pools. + 'management', which has the following fields: autoUpgrade: A + boolean field that indicates if node autoupgrade is enabled for + autoprovisioned node pools. autoRepair: A boolean field that + indicates if node autorepair is enabled for autoprovisioned node + pools. minCpuPlatform (deprecated): If specified, new autoprovisioned nodes will be scheduled on host with specified CPU architecture diff --git a/gcloud/beta/container/node-pools/create b/gcloud/beta/container/node-pools/create index f55874e2a..929100e4d 100644 --- a/gcloud/beta/container/node-pools/create +++ b/gcloud/beta/container/node-pools/create @@ -14,7 +14,7 @@ SYNOPSIS [--enable-autorepair] [--no-enable-autoupgrade] [--enable-blue-green-upgrade] [--enable-confidential-nodes] [--enable-gvnic] [--enable-image-streaming] [--enable-surge-upgrade] - [--image-type=IMAGE_TYPE] + [--image-type=IMAGE_TYPE] [--logging-variant=LOGGING_VARIANT] [--machine-type=MACHINE_TYPE, -m MACHINE_TYPE] [--max-pods-per-node=MAX_PODS_PER_NODE] [--max-surge-upgrade=MAX_SURGE_UPGRADE; default=1] @@ -187,6 +187,20 @@ FLAGS $ gcloud container get-server-config + --logging-variant=LOGGING_VARIANT + Specifies the logging variant that will be deployed on all the nodes in + the node pool. If the node pool doesn't specify a logging variant, then + the logging variant specified for the cluster will be deployed on all + the nodes in the node pool. Valid logging variants are MAX_THROUGHPUT, + DEFAULT. LOGGING_VARIANT must be one of: + + DEFAULT + 'DEFAULT' variant requests minimal resources but may not guarantee + high throughput. + MAX_THROUGHPUT + 'MAX_THROUGHPUT' variant requests more node resources and is able + to achieve logging throughput up to 10MB per sec. + --machine-type=MACHINE_TYPE, -m MACHINE_TYPE The type of machine to use for nodes. Defaults to e2-medium. The list of predefined machine types is available using the following command: diff --git a/gcloud/beta/container/node-pools/update b/gcloud/beta/container/node-pools/update index 53c2c3b4c..0cadf08ea 100644 --- a/gcloud/beta/container/node-pools/update +++ b/gcloud/beta/container/node-pools/update @@ -5,7 +5,7 @@ NAME SYNOPSIS gcloud beta container node-pools update NAME (--enable-confidential-nodes | --enable-gvnic - | --enable-image-streaming + | --enable-image-streaming | --logging-variant=LOGGING_VARIANT | --network-performance-configs=[PROPERTY=VALUE,...] | --node-labels=[NODE_LABEL,...] | --node-locations=ZONE,[ZONE,...] | --node-taints=[NODE_TAINT,...] @@ -54,6 +54,20 @@ REQUIRED FLAGS --enable-image-streaming Specifies whether to enable image streaming on node pool. + --logging-variant=LOGGING_VARIANT + Specifies the logging variant that will be deployed on all the nodes + in the node pool. If the node pool doesn't specify a logging variant, + then the logging variant specified for the cluster will be deployed + on all the nodes in the node pool. Valid logging variants are + MAX_THROUGHPUT, DEFAULT. LOGGING_VARIANT must be one of: + + DEFAULT + 'DEFAULT' variant requests minimal resources but may not + guarantee high throughput. + MAX_THROUGHPUT + 'MAX_THROUGHPUT' variant requests more node resources and is able + to achieve logging throughput up to 10MB per sec. + --network-performance-configs=[PROPERTY=VALUE,...] Configures network performance settings for the node pool. If this flag is not specified, the pool will be created with its default diff --git a/gcloud/beta/dataproc/clusters/gke/create b/gcloud/beta/dataproc/clusters/gke/create index 37c80589e..298c9850c 100644 --- a/gcloud/beta/dataproc/clusters/gke/create +++ b/gcloud/beta/dataproc/clusters/gke/create @@ -129,7 +129,7 @@ OPTIONAL FLAGS components in. This namespace does not need to exist. --pools=[KEY=VALUE[;VALUE],...] - Each --pools flag represents a single GKE node pool associated with the + Each --pools flag represents a GKE node pool associated with the virtual cluster. It is comprised of a CSV in the form KEY=VALUE[;VALUE], where certain keys may have multiple values. @@ -147,29 +147,29 @@ OPTIONAL FLAGS The following KEYs may be specified: ---------------------------------------------------------------------------------------------------------------------------------------------------------------- - KEY Type Example Description + KEY Type Example Description --------------- ---------------- --------------------------------------------- --------------------------------------------------------------------------------- - machineType string `n1-standard-8` Compute Engine machine type to use. + machineType string `n1-standard-8` Compute Engine machine type to use. - preemptible boolean `false` If true, then this node pool uses preemptible VMs. - This cannot be true on the node pool with the `controllers` role - (or `default` role if `controllers` role is not specified). + preemptible boolean `false` If true, then this node pool uses preemptible VMs. + This cannot be true on the node pool with the `controllers` role + (or `default` role if `controllers` role is not specified). - localSsdCount int `2` The number of local SSDs to attach to each node. + localSsdCount int `2` The number of local SSDs to attach to each node. - accelerator repeated string `nvidia-tesla-a100=1` Accelerators to attach to each node. In the format NAME=COUNT. + accelerator repeated string `nvidia-tesla-a100=1` Accelerators to attach to each node. In the format NAME=COUNT. - minCpuPlatform string `Intel Skylake` Minimum CPU platform for each node. + minCpuPlatform string `Intel Skylake` Minimum CPU platform for each node. - bootDiskKmsKey string `projects/project-id/locations/us-central1 The Customer Managed Encryption Key (CMEK) used to encrypt - /keyRings/keyRing-name/cryptoKeys/key-name` the boot disk attached to each node in the node pool. + bootDiskKmsKey string `projects/project-id/locations/us-central1 The Customer Managed Encryption Key (CMEK) used to encrypt + /keyRings/keyRing-name/cryptoKeys/key-name` the boot disk attached to each node in the node pool. - locations repeated string `us-west1-a;us-west1-c` Zones within the location of the GKE cluster. - All `--pools` flags for a single Dataproc cluster must have identical locations. + locations repeated string `us-west1-a;us-west1-c` Zones within the location of the GKE cluster. + All `--pools` flags for a Dataproc cluster must have identical locations. - min int `0` Minimum number of nodes per zone that this node pool can scale down to. + min int `0` Minimum number of nodes per zone that this node pool can scale down to. - max int `10` Maximum number of nodes per zone that this node pool can scale up to. + max int `10` Maximum number of nodes per zone that this node pool can scale up to. ---------------------------------------------------------------------------------------------------------------------------------------------------------------- --properties=[PREFIX:PROPERTY=VALUE,...] diff --git a/gcloud/beta/secrets/create b/gcloud/beta/secrets/create index 5f0fbfb9f..18d2ae9da 100644 --- a/gcloud/beta/secrets/create +++ b/gcloud/beta/secrets/create @@ -3,8 +3,8 @@ NAME SYNOPSIS gcloud beta secrets create SECRET [--data-file=PATH] - [--labels=[KEY=VALUE,...]] [--topics=[TOPICS,...]] - [--expire-time=EXPIRE-TIME | --ttl=TTL] + [--labels=[KEY=VALUE,...]] [--set-annotations=[KEY=VALUE,...]] + [--topics=[TOPICS,...]] [--expire-time=EXPIRE-TIME | --ttl=TTL] [--next-rotation-time=NEXT_ROTATION_TIME --rotation-period=ROTATION_PERIOD] [--replication-policy-file=REPLICATION-POLICY-FILE @@ -101,6 +101,12 @@ FLAGS contain only hyphens (-), underscores (_), lowercase characters, and numbers. + Annotations + + --set-annotations=[KEY=VALUE,...] + List of key-value pairs to set as Annotations. All existing + Annotations will be removed first. + --topics=[TOPICS,...] List of Pub/Sub topics to configure on the secret. diff --git a/gcloud/beta/secrets/update b/gcloud/beta/secrets/update index 958517b9c..577439d54 100644 --- a/gcloud/beta/secrets/update +++ b/gcloud/beta/secrets/update @@ -6,6 +6,8 @@ SYNOPSIS [--update-labels=[KEY=VALUE,...]] [--add-topics=[ADD-TOPICS,...] | --clear-topics | --remove-topics=[REMOVE-TOPICS,...]] + [--clear-annotations | --remove-annotations=[KEY,...] + | --update-annotations=[KEY=VALUE,...]] [--clear-labels | --remove-labels=[KEY,...]] [--clear-version-aliases | --remove-version-aliases=[KEY,...] | --update-version-aliases=[KEY=VALUE,...]] @@ -105,6 +107,19 @@ FLAGS --remove-topics=[REMOVE-TOPICS,...] List of Pub/Sub topics to remove from the secret. + Annotations + + At most one of these can be specified: + + --clear-annotations + Remove all Annotations. + + --remove-annotations=[KEY,...] + List of Annotations to be removed. + + --update-annotations=[KEY=VALUE,...] + List of key-value pairs to set as Annotations. + At most one of these can be specified: --clear-labels diff --git a/gcloud/beta/secrets/versions/access b/gcloud/beta/secrets/versions/access index ead7363d0..8f2006fcb 100644 --- a/gcloud/beta/secrets/versions/access +++ b/gcloud/beta/secrets/versions/access @@ -3,7 +3,7 @@ NAME SYNOPSIS gcloud beta secrets versions access (VERSION : --secret=SECRET) - [GCLOUD_WIDE_FLAG ...] + [--out-file=OUT-FILE-PATH] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) Access the data for the specified secret version. @@ -14,7 +14,14 @@ EXAMPLES $ gcloud beta secrets versions access 123 --secret=my-secret Note: The output will be formatted as UTF-8 which can corrupt binary - secrets. To get the raw bytes, have Cloud SDK print the response as + secrets. + + To write raw bytes to a file use --out-file flag: + + $ gcloud beta secrets versions access 123 --secret=my-secret \ + --out-file=/tmp/secret + + To get the raw bytes, have Google Cloud CLI print the response as base64-encoded and decode: $ gcloud beta secrets versions access 123 --secret=my-secret \ @@ -47,6 +54,10 @@ POSITIONAL ARGUMENTS specified name; ▸ provide the argument --secret on the command line. +FLAGS + --out-file=OUT-FILE-PATH + File path to which secret data is written. + 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/spanner/databases/execute-sql b/gcloud/beta/spanner/databases/execute-sql index d4877a8be..af4804cea 100644 --- a/gcloud/beta/spanner/databases/execute-sql +++ b/gcloud/beta/spanner/databases/execute-sql @@ -4,7 +4,7 @@ NAME SYNOPSIS gcloud beta spanner databases execute-sql (DATABASE : --instance=INSTANCE) - --sql=SQL [--enable-partitioned-dml] + --sql=SQL [--database-role=DATABASE_ROLE] [--enable-partitioned-dml] [--query-mode=QUERY_MODE; default="NORMAL"] [--timeout=TIMEOUT; default="10m"] [--read-timestamp=TIMESTAMP | --strong] [GCLOUD_WIDE_FLAG ...] @@ -54,6 +54,9 @@ REQUIRED FLAGS at https://cloud.google.com/spanner/docs/query-syntax OPTIONAL FLAGS + --database-role=DATABASE_ROLE + Database role user assumes while accessing the database. + --enable-partitioned-dml Execute DML statement using Partitioned DML diff --git a/gcloud/beta/spanner/databases/help b/gcloud/beta/spanner/databases/help index 297b6a335..0414c1908 100644 --- a/gcloud/beta/spanner/databases/help +++ b/gcloud/beta/spanner/databases/help @@ -18,6 +18,9 @@ GROUPS ddl (BETA) Manage the DDL for Cloud Spanner databases. + roles + (BETA) Manage Cloud Spanner database roles. + sessions (BETA) Manage the sessions for Cloud Spanner databases. diff --git a/gcloud/beta/spanner/databases/roles/help b/gcloud/beta/spanner/databases/roles/help new file mode 100644 index 000000000..2339c3181 --- /dev/null +++ b/gcloud/beta/spanner/databases/roles/help @@ -0,0 +1,27 @@ +NAME + gcloud beta spanner databases roles - manage Cloud Spanner database roles + +SYNOPSIS + gcloud beta spanner databases roles COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Manage Cloud Spanner database roles. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + list + (BETA) List the Cloud Spanner database roles contained within the given + database. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha spanner databases roles + diff --git a/gcloud/beta/spanner/databases/roles/list b/gcloud/beta/spanner/databases/roles/list new file mode 100644 index 000000000..3b54b337b --- /dev/null +++ b/gcloud/beta/spanner/databases/roles/list @@ -0,0 +1,94 @@ +NAME + gcloud beta spanner databases roles list - list the Cloud Spanner database + roles contained within the given database + +SYNOPSIS + gcloud beta spanner databases roles list + (--database=DATABASE : --instance=INSTANCE) [--filter=EXPRESSION] + [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) List the Cloud Spanner database roles contained within the given + database. + +EXAMPLES + To list the Cloud Spanner database roles in a database, run: + + $ gcloud beta spanner databases roles list \ + --instance=my-instance-id --database=my-database-id + +REQUIRED FLAGS + Database resource - The Cloud Spanner database in which to list database + roles. 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 --database 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. + + --database=DATABASE + ID of the database or fully qualified identifier for the database. To + set the database attribute: + ▸ provide the argument --database on the command line. + + This flag argument must be specified if any of the other arguments in + this group are specified. + + --instance=INSTANCE + The Cloud Spanner instance for the database. To set the instance + attribute: + ▸ provide the argument --database on the command line with a fully + specified name; + ▸ provide the argument --instance on the command line; + ▸ set the property spanner/instance. + +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 beta and might change without notice. This + variant is also available: + + $ gcloud alpha spanner databases roles list + diff --git a/gcloud/compute/commitments/create b/gcloud/compute/commitments/create index bd32d17d2..bdafae9b7 100644 --- a/gcloud/compute/commitments/create +++ b/gcloud/compute/commitments/create @@ -153,10 +153,10 @@ OPTIONAL FLAGS The size of the local SSD in base-2 GB. --machine-type=MACHINE_TYPE - The type of machine (name only) which has a fixed number of vCPUs - and a fixed amount of memory. This also includes specifying - custom machine type following - custom-number_of_CPUs-amount_of_memory pattern, e.g. + The type of machine (name only) that has a fixed number of vCPUs + and a fixed amount of memory. You can also specify a custom + machine type by using the pattern + custom-number_of_CPUs-amount_of_memory-for example, custom-32-29440. --min-cpu-platform=MIN_CPU_PLATFORM diff --git a/gcloud/compute/firewall-rules/create b/gcloud/compute/firewall-rules/create index b83e832ae..05ce2947b 100644 --- a/gcloud/compute/firewall-rules/create +++ b/gcloud/compute/firewall-rules/create @@ -101,9 +101,8 @@ OPTIONAL FLAGS --direction=DIRECTION If direction is NOT specified, then default is to apply on incoming - traffic. For incoming traffic, it is NOT supported to specify - destination-ranges; For outbound traffic, it is NOT supported to - specify source-ranges or source-tags. + traffic. For outbound traffic, it is NOT supported to specify + source-tags. For convenience, 'IN' can be used to represent ingress direction and 'OUT' can be used to represent egress direction. diff --git a/gcloud/compute/reservations/create b/gcloud/compute/reservations/create index ea9400f6c..54b73ea9b 100644 --- a/gcloud/compute/reservations/create +++ b/gcloud/compute/reservations/create @@ -3,11 +3,12 @@ NAME SYNOPSIS gcloud compute reservations create RESERVATION - (--machine-type=MACHINE_TYPE --vm-count=VM_COUNT + (--vm-count=VM_COUNT ([--machine-type=MACHINE_TYPE : --accelerator=[count=COUNT],[type=TYPE] --local-ssd=[interface=INTERFACE],[size=SIZE] - --min-cpu-platform=MIN_CPU_PLATFORM --require-specific-reservation) - [--description=DESCRIPTION] [--zone=ZONE] + --min-cpu-platform=MIN_CPU_PLATFORM]) + : --require-specific-reservation) [--description=DESCRIPTION] + [--zone=ZONE] [--share-setting=SHARE_SETTING --share-with=SHARE_WITH,[SHARE_WITH,...]] [GCLOUD_WIDE_FLAG ...] @@ -26,19 +27,10 @@ POSITIONAL ARGUMENTS Name of the reservation to create. REQUIRED FLAGS - Manage the specific SKU reservation properties. + Manage the SpecificSKU reservation properties. This must be specified. - --machine-type=MACHINE_TYPE - The type of machine (name only) which has a fixed number of vCPUs and - a fixed amount of memory. This also includes specifying custom - machine type following custom-number_of_CPUs-amount_of_memory - pattern, e.g. custom-32-29440. - - This flag argument must be specified if any of the other arguments in - this group are specified. - --vm-count=VM_COUNT The number of VM instances that are allocated to this reservation. The value of this field must be an int in the range [1, 1000]. @@ -46,39 +38,56 @@ REQUIRED FLAGS This flag argument must be specified if any of the other arguments in this group are specified. - --accelerator=[count=COUNT],[type=TYPE] - Manage the configuration of the type and number of accelerator cards - attached. - count - The number of accelerators to attach to each instance in the - reservation. - type - The specific type (e.g. nvidia-tesla-k80 for nVidia Tesla K80) of - accelerator to attach to instances in the reservation. Use gcloud - compute accelerator-types list to learn about all available - accelerator types. - - --local-ssd=[interface=INTERFACE],[size=SIZE] - Manage the size and the interface of local SSD to use. See - https://cloud.google.com/compute/docs/disks/local-ssd for more - information. - interface - 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 may provide higher - performance. - size - The size of the local SSD in base-2 GB. - - --min-cpu-platform=MIN_CPU_PLATFORM - Optional minimum CPU platform of the reservation to create. - --require-specific-reservation Indicates whether the reservation can be consumed by VMs with "any reservation" defined. If enabled, then only VMs that target this reservation by name using --reservation-affinity=specific can consume from this reservation. + Manage the instance properties for the SpecificSKU reservation. + + This must be specified. + + Define the individual instance properties for the SpecificSKU + reservation. + + --machine-type=MACHINE_TYPE + The type of machine (name only) that has a fixed number of vCPUs + and a fixed amount of memory. You can also specify a custom + machine type by using the pattern + custom-number_of_CPUs-amount_of_memory-for example, + custom-32-29440. + + This flag argument must be specified if any of the other + arguments in this group are specified. + + --accelerator=[count=COUNT],[type=TYPE] + Manage the configuration of the type and number of accelerator + cards attached. + count + The number of accelerators to attach to each instance in the + reservation. + type + The specific type (e.g. nvidia-tesla-k80 for nVidia Tesla + K80) of accelerator to attach to instances in the + reservation. Use gcloud compute accelerator-types list to + learn about all available accelerator types. + + --local-ssd=[interface=INTERFACE],[size=SIZE] + Manage the size and the interface of local SSD to use. See + https://cloud.google.com/compute/docs/disks/local-ssd for more + information. + interface + 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 may provide + higher performance. + size + The size of the local SSD in base-2 GB. + + --min-cpu-platform=MIN_CPU_PLATFORM + Optional minimum CPU platform of the reservation to create. + OPTIONAL FLAGS --description=DESCRIPTION An optional description of the reservation to create. diff --git a/gcloud/config/get b/gcloud/config/get index 9fe9e04b4..1264632f9 100644 --- a/gcloud/config/get +++ b/gcloud/config/get @@ -306,8 +306,8 @@ AVAILABLE PROPERTIES Overrides API endpoint for gcloud genomics command group. gkemulticloud - Overrides API endpoint for gcloud container aws and gcloud - container azure command groups. + Overrides API endpoint for gcloud container aws, gcloud container + azure and gcloud container attached command groups. healthcare Overrides API endpoint for gcloud healthcare command group. @@ -610,6 +610,10 @@ AVAILABLE PROPERTIES If True, use the cluster's client certificate to authenticate to the cluster API server. + container_attached + location + Default Google Cloud location to use for Attached clusters. + container_aws location Default Google Cloud location to use for Anthos clusters on AWS. diff --git a/gcloud/config/help b/gcloud/config/help index 60926eee7..29f3403b4 100644 --- a/gcloud/config/help +++ b/gcloud/config/help @@ -338,8 +338,8 @@ AVAILABLE PROPERTIES Overrides API endpoint for gcloud genomics command group. gkemulticloud - Overrides API endpoint for gcloud container aws and gcloud - container azure command groups. + Overrides API endpoint for gcloud container aws, gcloud container + azure and gcloud container attached command groups. healthcare Overrides API endpoint for gcloud healthcare command group. @@ -642,6 +642,10 @@ AVAILABLE PROPERTIES If True, use the cluster's client certificate to authenticate to the cluster API server. + container_attached + location + Default Google Cloud location to use for Attached clusters. + container_aws location Default Google Cloud location to use for Anthos clusters on AWS. diff --git a/gcloud/config/list b/gcloud/config/list index 95061945b..0e24e4840 100644 --- a/gcloud/config/list +++ b/gcloud/config/list @@ -343,8 +343,8 @@ AVAILABLE PROPERTIES Overrides API endpoint for gcloud genomics command group. gkemulticloud - Overrides API endpoint for gcloud container aws and gcloud - container azure command groups. + Overrides API endpoint for gcloud container aws, gcloud container + azure and gcloud container attached command groups. healthcare Overrides API endpoint for gcloud healthcare command group. @@ -647,6 +647,10 @@ AVAILABLE PROPERTIES If True, use the cluster's client certificate to authenticate to the cluster API server. + container_attached + location + Default Google Cloud location to use for Attached clusters. + container_aws location Default Google Cloud location to use for Anthos clusters on AWS. diff --git a/gcloud/config/set b/gcloud/config/set index c2b243bb8..61b853cc1 100644 --- a/gcloud/config/set +++ b/gcloud/config/set @@ -353,8 +353,8 @@ AVAILABLE PROPERTIES Overrides API endpoint for gcloud genomics command group. gkemulticloud - Overrides API endpoint for gcloud container aws and gcloud - container azure command groups. + Overrides API endpoint for gcloud container aws, gcloud container + azure and gcloud container attached command groups. healthcare Overrides API endpoint for gcloud healthcare command group. @@ -657,6 +657,10 @@ AVAILABLE PROPERTIES If True, use the cluster's client certificate to authenticate to the cluster API server. + container_attached + location + Default Google Cloud location to use for Attached clusters. + container_aws location Default Google Cloud location to use for Anthos clusters on AWS. diff --git a/gcloud/config/unset b/gcloud/config/unset index 0fac80824..cb7dc3251 100644 --- a/gcloud/config/unset +++ b/gcloud/config/unset @@ -314,8 +314,8 @@ AVAILABLE PROPERTIES Overrides API endpoint for gcloud genomics command group. gkemulticloud - Overrides API endpoint for gcloud container aws and gcloud - container azure command groups. + Overrides API endpoint for gcloud container aws, gcloud container + azure and gcloud container attached command groups. healthcare Overrides API endpoint for gcloud healthcare command group. @@ -618,6 +618,10 @@ AVAILABLE PROPERTIES If True, use the cluster's client certificate to authenticate to the cluster API server. + container_attached + location + Default Google Cloud location to use for Attached clusters. + container_aws location Default Google Cloud location to use for Anthos clusters on AWS. diff --git a/gcloud/container/aws/clusters/create b/gcloud/container/aws/clusters/create index e8d60680d..9ba1c32bd 100644 --- a/gcloud/container/aws/clusters/create +++ b/gcloud/container/aws/clusters/create @@ -11,8 +11,10 @@ SYNOPSIS --pod-address-cidr-blocks=POD_ADDRESS_CIDR_BLOCKS --role-arn=ROLE_ARN --service-address-cidr-blocks=SERVICE_ADDRESS_CIDR_BLOCKS --subnet-ids=[SUBNET_ID,...] --vpc-id=VPC_ID - [--admin-users=USER,[USER,...]] [--async] - [--instance-type=INSTANCE_TYPE] [--main-volume-iops=MAIN_VOLUME_IOPS] + [--admin-users=USER,[USER,...]] + [--annotations=ANNOTATION,[ANNOTATION,...]] [--async] + [--description=DESCRIPTION] [--instance-type=INSTANCE_TYPE] + [--main-volume-iops=MAIN_VOLUME_IOPS] [--main-volume-kms-key-arn=MAIN_VOLUME_KMS_KEY_ARN] [--main-volume-size=MAIN_VOLUME_SIZE] [--main-volume-type=MAIN_VOLUME_TYPE] @@ -69,8 +71,7 @@ POSITIONAL ARGUMENTS ▸ provide the argument cluster on the command line with a fully specified name; ▸ provide the argument --location on the command line; - ▸ set the property container_aws/location; - ▸ set the property aws/location (deprecated). + ▸ set the property container_aws/location. REQUIRED FLAGS --aws-region=AWS_REGION @@ -115,10 +116,16 @@ OPTIONAL FLAGS Users that can perform operations as a cluster administrator. If not specified, the value of property core/account is used. + --annotations=ANNOTATION,[ANNOTATION,...] + Annotations for the cluster. + --async Return immediately, without waiting for the operation in progress to complete. + --description=DESCRIPTION + Description for the cluster. + --instance-type=INSTANCE_TYPE AWS EC2 instance type for the control plane's nodes. diff --git a/gcloud/container/aws/clusters/delete b/gcloud/container/aws/clusters/delete index d353d2add..b1f5f30ad 100644 --- a/gcloud/container/aws/clusters/delete +++ b/gcloud/container/aws/clusters/delete @@ -38,8 +38,7 @@ POSITIONAL ARGUMENTS ▸ provide the argument cluster on the command line with a fully specified name; ▸ provide the argument --location on the command line; - ▸ set the property container_aws/location; - ▸ set the property aws/location (deprecated). + ▸ set the property container_aws/location. FLAGS --async diff --git a/gcloud/container/aws/clusters/describe b/gcloud/container/aws/clusters/describe index f42a68649..2b77171b5 100644 --- a/gcloud/container/aws/clusters/describe +++ b/gcloud/container/aws/clusters/describe @@ -39,8 +39,7 @@ POSITIONAL ARGUMENTS ▸ provide the argument cluster on the command line with a fully specified name; ▸ provide the argument --location on the command line; - ▸ set the property container_aws/location; - ▸ set the property aws/location (deprecated). + ▸ set the property container_aws/location. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/container/aws/clusters/get-credentials b/gcloud/container/aws/clusters/get-credentials index 3b8460e94..b628e0697 100644 --- a/gcloud/container/aws/clusters/get-credentials +++ b/gcloud/container/aws/clusters/get-credentials @@ -66,8 +66,7 @@ POSITIONAL ARGUMENTS ▸ provide the argument cluster on the command line with a fully specified name; ▸ provide the argument --location on the command line; - ▸ set the property container_aws/location; - ▸ set the property aws/location (deprecated). + ▸ set the property container_aws/location. FLAGS --private-endpoint diff --git a/gcloud/container/aws/clusters/list b/gcloud/container/aws/clusters/list index 05624520b..ea8de3b87 100644 --- a/gcloud/container/aws/clusters/list +++ b/gcloud/container/aws/clusters/list @@ -21,8 +21,6 @@ FLAGS ◆ provide the argument --location on the command line with a fully specified name; ◆ set the property container_aws/location with a fully specified name; - ◆ set the property aws/location (deprecated) with a fully specified - name; ◆ provide the argument --project on the command line; ◆ set the property core/project. @@ -30,8 +28,7 @@ FLAGS ID of the location or fully qualified identifier for the location. To set the location attribute: ▸ provide the argument --location on the command line; - ▸ set the property container_aws/location; - ▸ set the property aws/location (deprecated). + ▸ set the property container_aws/location. LIST COMMAND FLAGS --filter=EXPRESSION diff --git a/gcloud/container/aws/clusters/update b/gcloud/container/aws/clusters/update index 730ca9ba7..105da4a84 100644 --- a/gcloud/container/aws/clusters/update +++ b/gcloud/container/aws/clusters/update @@ -54,8 +54,7 @@ POSITIONAL ARGUMENTS ▸ provide the argument cluster on the command line with a fully specified name; ▸ provide the argument --location on the command line; - ▸ set the property container_aws/location; - ▸ set the property aws/location (deprecated). + ▸ set the property container_aws/location. FLAGS --admin-users=USER,[USER,...] diff --git a/gcloud/container/aws/get-server-config b/gcloud/container/aws/get-server-config index 5d0b8a4ec..114aac85a 100644 --- a/gcloud/container/aws/get-server-config +++ b/gcloud/container/aws/get-server-config @@ -23,8 +23,6 @@ FLAGS ◆ provide the argument --location on the command line with a fully specified name; ◆ set the property container_aws/location with a fully specified name; - ◆ set the property aws/location (deprecated) with a fully specified - name; ◆ provide the argument --project on the command line; ◆ set the property core/project. @@ -32,8 +30,7 @@ FLAGS ID of the location or fully qualified identifier for the location. To set the location attribute: ▸ provide the argument --location on the command line; - ▸ set the property container_aws/location; - ▸ set the property aws/location (deprecated). + ▸ set the property container_aws/location. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/container/aws/node-pools/create b/gcloud/container/aws/node-pools/create index 8bb0fd893..31ed22017 100644 --- a/gcloud/container/aws/node-pools/create +++ b/gcloud/container/aws/node-pools/create @@ -66,8 +66,7 @@ POSITIONAL ARGUMENTS ▸ provide the argument node_pool on the command line with a fully specified name; ▸ provide the argument --location on the command line; - ▸ set the property container_aws/location; - ▸ set the property aws/location (deprecated). + ▸ set the property container_aws/location. REQUIRED FLAGS --config-encryption-kms-key-arn=CONFIG_ENCRYPTION_KMS_KEY_ARN diff --git a/gcloud/container/aws/node-pools/delete b/gcloud/container/aws/node-pools/delete index 01c2ff6f3..64a61929b 100644 --- a/gcloud/container/aws/node-pools/delete +++ b/gcloud/container/aws/node-pools/delete @@ -49,8 +49,7 @@ POSITIONAL ARGUMENTS ▸ provide the argument node_pool on the command line with a fully specified name; ▸ provide the argument --location on the command line; - ▸ set the property container_aws/location; - ▸ set the property aws/location (deprecated). + ▸ set the property container_aws/location. FLAGS --async diff --git a/gcloud/container/aws/node-pools/describe b/gcloud/container/aws/node-pools/describe index baf9159a1..bb40a9273 100644 --- a/gcloud/container/aws/node-pools/describe +++ b/gcloud/container/aws/node-pools/describe @@ -49,8 +49,7 @@ POSITIONAL ARGUMENTS ▸ provide the argument node_pool on the command line with a fully specified name; ▸ provide the argument --location on the command line; - ▸ set the property container_aws/location; - ▸ set the property aws/location (deprecated). + ▸ set the property container_aws/location. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/container/aws/node-pools/list b/gcloud/container/aws/node-pools/list index fcc665092..b6e8d9481 100644 --- a/gcloud/container/aws/node-pools/list +++ b/gcloud/container/aws/node-pools/list @@ -43,8 +43,7 @@ REQUIRED FLAGS ▸ provide the argument --cluster on the command line with a fully specified name; ▸ provide the argument --location on the command line; - ▸ set the property container_aws/location; - ▸ set the property aws/location (deprecated). + ▸ set the property container_aws/location. LIST COMMAND FLAGS --filter=EXPRESSION diff --git a/gcloud/container/aws/node-pools/update b/gcloud/container/aws/node-pools/update index d60746e43..510de798a 100644 --- a/gcloud/container/aws/node-pools/update +++ b/gcloud/container/aws/node-pools/update @@ -61,8 +61,7 @@ POSITIONAL ARGUMENTS ▸ provide the argument node_pool on the command line with a fully specified name; ▸ provide the argument --location on the command line; - ▸ set the property container_aws/location; - ▸ set the property aws/location (deprecated). + ▸ set the property container_aws/location. FLAGS --async diff --git a/gcloud/container/aws/operations/describe b/gcloud/container/aws/operations/describe index 731b0bc26..df0659b70 100644 --- a/gcloud/container/aws/operations/describe +++ b/gcloud/container/aws/operations/describe @@ -40,8 +40,7 @@ POSITIONAL ARGUMENTS ▸ provide the argument operation_id on the command line with a fully specified name; ▸ provide the argument --location on the command line; - ▸ set the property container_aws/location; - ▸ set the property aws/location (deprecated). + ▸ set the property container_aws/location. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/container/aws/operations/list b/gcloud/container/aws/operations/list index cdf01a84b..3c93735d2 100644 --- a/gcloud/container/aws/operations/list +++ b/gcloud/container/aws/operations/list @@ -22,8 +22,6 @@ FLAGS ◆ provide the argument --location on the command line with a fully specified name; ◆ set the property container_aws/location with a fully specified name; - ◆ set the property aws/location (deprecated) with a fully specified - name; ◆ provide the argument --project on the command line; ◆ set the property core/project. @@ -31,8 +29,7 @@ FLAGS ID of the location or fully qualified identifier for the location. To set the location attribute: ▸ provide the argument --location on the command line; - ▸ set the property container_aws/location; - ▸ set the property aws/location (deprecated). + ▸ set the property container_aws/location. LIST COMMAND FLAGS --filter=EXPRESSION diff --git a/gcloud/container/aws/operations/wait b/gcloud/container/aws/operations/wait index e0c7341e2..557630725 100644 --- a/gcloud/container/aws/operations/wait +++ b/gcloud/container/aws/operations/wait @@ -40,8 +40,7 @@ POSITIONAL ARGUMENTS ▸ provide the argument operation_id on the command line with a fully specified name; ▸ provide the argument --location on the command line; - ▸ set the property container_aws/location; - ▸ set the property aws/location (deprecated). + ▸ set the property container_aws/location. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/container/azure/clients/create b/gcloud/container/azure/clients/create index 7c4b337b8..9bdd1cb4e 100644 --- a/gcloud/container/azure/clients/create +++ b/gcloud/container/azure/clients/create @@ -41,8 +41,7 @@ POSITIONAL ARGUMENTS ▸ provide the argument client on the command line with a fully specified name; ▸ provide the argument --location on the command line; - ▸ set the property container_azure/location; - ▸ set the property azure/location (deprecated). + ▸ set the property container_azure/location. REQUIRED FLAGS --application-id=APP_ID diff --git a/gcloud/container/azure/clients/delete b/gcloud/container/azure/clients/delete index c53932252..9522cd5d1 100644 --- a/gcloud/container/azure/clients/delete +++ b/gcloud/container/azure/clients/delete @@ -38,8 +38,7 @@ POSITIONAL ARGUMENTS ▸ provide the argument client on the command line with a fully specified name; ▸ provide the argument --location on the command line; - ▸ set the property container_azure/location; - ▸ set the property azure/location (deprecated). + ▸ set the property container_azure/location. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/container/azure/clients/describe b/gcloud/container/azure/clients/describe index 3c7dda2a6..62644c1c5 100644 --- a/gcloud/container/azure/clients/describe +++ b/gcloud/container/azure/clients/describe @@ -39,8 +39,7 @@ POSITIONAL ARGUMENTS ▸ provide the argument client on the command line with a fully specified name; ▸ provide the argument --location on the command line; - ▸ set the property container_azure/location; - ▸ set the property azure/location (deprecated). + ▸ set the property container_azure/location. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/container/azure/clients/get-public-cert b/gcloud/container/azure/clients/get-public-cert index 791c9a5a0..68a2e2f38 100644 --- a/gcloud/container/azure/clients/get-public-cert +++ b/gcloud/container/azure/clients/get-public-cert @@ -47,8 +47,7 @@ POSITIONAL ARGUMENTS ▸ provide the argument client on the command line with a fully specified name; ▸ provide the argument --location on the command line; - ▸ set the property container_azure/location; - ▸ set the property azure/location (deprecated). + ▸ set the property container_azure/location. FLAGS --output-file=OUTPUT_FILE diff --git a/gcloud/container/azure/clients/list b/gcloud/container/azure/clients/list index 7f1a622e4..379943d3b 100644 --- a/gcloud/container/azure/clients/list +++ b/gcloud/container/azure/clients/list @@ -23,8 +23,6 @@ FLAGS specified name; ◆ set the property container_azure/location with a fully specified name; - ◆ set the property azure/location (deprecated) with a fully specified - name; ◆ provide the argument --project on the command line; ◆ set the property core/project. @@ -32,8 +30,7 @@ FLAGS ID of the location or fully qualified identifier for the location. To set the location attribute: ▸ provide the argument --location on the command line; - ▸ set the property container_azure/location; - ▸ set the property azure/location (deprecated). + ▸ set the property container_azure/location. LIST COMMAND FLAGS --filter=EXPRESSION diff --git a/gcloud/container/azure/clusters/create b/gcloud/container/azure/clusters/create index f197a026c..1c2bd842d 100644 --- a/gcloud/container/azure/clusters/create +++ b/gcloud/container/azure/clusters/create @@ -62,8 +62,7 @@ POSITIONAL ARGUMENTS ▸ provide the argument cluster on the command line with a fully specified name; ▸ provide the argument --location on the command line; - ▸ set the property container_azure/location; - ▸ set the property azure/location (deprecated). + ▸ set the property container_azure/location. REQUIRED FLAGS --azure-region=AZURE_REGION @@ -81,8 +80,7 @@ REQUIRED FLAGS ◆ provide the argument --client on the command line with a fully specified name; ◆ provide the argument --location on the command line; - ◆ set the property container_azure/location; - ◆ set the property azure/location (deprecated). + ◆ set the property container_azure/location. This must be specified. diff --git a/gcloud/container/azure/clusters/delete b/gcloud/container/azure/clusters/delete index c50f7ff7a..6cb911de2 100644 --- a/gcloud/container/azure/clusters/delete +++ b/gcloud/container/azure/clusters/delete @@ -39,8 +39,7 @@ POSITIONAL ARGUMENTS ▸ provide the argument cluster on the command line with a fully specified name; ▸ provide the argument --location on the command line; - ▸ set the property container_azure/location; - ▸ set the property azure/location (deprecated). + ▸ set the property container_azure/location. FLAGS --async diff --git a/gcloud/container/azure/clusters/describe b/gcloud/container/azure/clusters/describe index af1ac44e6..4b158132d 100644 --- a/gcloud/container/azure/clusters/describe +++ b/gcloud/container/azure/clusters/describe @@ -40,8 +40,7 @@ POSITIONAL ARGUMENTS ▸ provide the argument cluster on the command line with a fully specified name; ▸ provide the argument --location on the command line; - ▸ set the property container_azure/location; - ▸ set the property azure/location (deprecated). + ▸ set the property container_azure/location. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/container/azure/clusters/get-credentials b/gcloud/container/azure/clusters/get-credentials index 2083f6e9a..f809236da 100644 --- a/gcloud/container/azure/clusters/get-credentials +++ b/gcloud/container/azure/clusters/get-credentials @@ -66,8 +66,7 @@ POSITIONAL ARGUMENTS ▸ provide the argument cluster on the command line with a fully specified name; ▸ provide the argument --location on the command line; - ▸ set the property container_azure/location; - ▸ set the property azure/location (deprecated). + ▸ set the property container_azure/location. FLAGS --private-endpoint diff --git a/gcloud/container/azure/clusters/list b/gcloud/container/azure/clusters/list index 06a64052f..1b518229e 100644 --- a/gcloud/container/azure/clusters/list +++ b/gcloud/container/azure/clusters/list @@ -23,8 +23,6 @@ FLAGS specified name; ◆ set the property container_azure/location with a fully specified name; - ◆ set the property azure/location (deprecated) with a fully specified - name; ◆ provide the argument --project on the command line; ◆ set the property core/project. @@ -32,8 +30,7 @@ FLAGS ID of the location or fully qualified identifier for the location. To set the location attribute: ▸ provide the argument --location on the command line; - ▸ set the property container_azure/location; - ▸ set the property azure/location (deprecated). + ▸ set the property container_azure/location. LIST COMMAND FLAGS --filter=EXPRESSION diff --git a/gcloud/container/azure/clusters/update b/gcloud/container/azure/clusters/update index 6de1474c1..89dc586b8 100644 --- a/gcloud/container/azure/clusters/update +++ b/gcloud/container/azure/clusters/update @@ -42,8 +42,7 @@ POSITIONAL ARGUMENTS ▸ provide the argument cluster on the command line with a fully specified name; ▸ provide the argument --location on the command line; - ▸ set the property container_azure/location; - ▸ set the property azure/location (deprecated). + ▸ set the property container_azure/location. FLAGS Client resource - Azure client to use for cluster update. This represents @@ -56,8 +55,7 @@ FLAGS ◆ provide the argument --client on the command line with a fully specified name; ◆ provide the argument --location on the command line; - ◆ set the property container_azure/location; - ◆ set the property azure/location (deprecated). + ◆ set the property container_azure/location. --client=CLIENT ID of the client or fully qualified identifier for the client. To set diff --git a/gcloud/container/azure/get-server-config b/gcloud/container/azure/get-server-config index 6c071d59a..212caf7da 100644 --- a/gcloud/container/azure/get-server-config +++ b/gcloud/container/azure/get-server-config @@ -24,8 +24,6 @@ FLAGS specified name; ◆ set the property container_azure/location with a fully specified name; - ◆ set the property azure/location (deprecated) with a fully specified - name; ◆ provide the argument --project on the command line; ◆ set the property core/project. @@ -33,8 +31,7 @@ FLAGS ID of the location or fully qualified identifier for the location. To set the location attribute: ▸ provide the argument --location on the command line; - ▸ set the property container_azure/location; - ▸ set the property azure/location (deprecated). + ▸ set the property container_azure/location. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/container/azure/node-pools/create b/gcloud/container/azure/node-pools/create index b2e944ead..6c522837d 100644 --- a/gcloud/container/azure/node-pools/create +++ b/gcloud/container/azure/node-pools/create @@ -63,8 +63,7 @@ POSITIONAL ARGUMENTS ▸ provide the argument node_pool on the command line with a fully specified name; ▸ provide the argument --location on the command line; - ▸ set the property container_azure/location; - ▸ set the property azure/location (deprecated). + ▸ set the property container_azure/location. REQUIRED FLAGS --node-version=NODE_VERSION diff --git a/gcloud/container/azure/node-pools/delete b/gcloud/container/azure/node-pools/delete index 65c96ffa4..d7a203e34 100644 --- a/gcloud/container/azure/node-pools/delete +++ b/gcloud/container/azure/node-pools/delete @@ -49,8 +49,7 @@ POSITIONAL ARGUMENTS ▸ provide the argument node_pool on the command line with a fully specified name; ▸ provide the argument --location on the command line; - ▸ set the property container_azure/location; - ▸ set the property azure/location (deprecated). + ▸ set the property container_azure/location. FLAGS --async diff --git a/gcloud/container/azure/node-pools/describe b/gcloud/container/azure/node-pools/describe index 0b7f6ebf3..d664ffeb1 100644 --- a/gcloud/container/azure/node-pools/describe +++ b/gcloud/container/azure/node-pools/describe @@ -49,8 +49,7 @@ POSITIONAL ARGUMENTS ▸ provide the argument node_pool on the command line with a fully specified name; ▸ provide the argument --location on the command line; - ▸ set the property container_azure/location; - ▸ set the property azure/location (deprecated). + ▸ set the property container_azure/location. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/container/azure/node-pools/list b/gcloud/container/azure/node-pools/list index bdc2214c9..fc1cfd90d 100644 --- a/gcloud/container/azure/node-pools/list +++ b/gcloud/container/azure/node-pools/list @@ -43,8 +43,7 @@ REQUIRED FLAGS ▸ provide the argument --cluster on the command line with a fully specified name; ▸ provide the argument --location on the command line; - ▸ set the property container_azure/location; - ▸ set the property azure/location (deprecated). + ▸ set the property container_azure/location. LIST COMMAND FLAGS --filter=EXPRESSION diff --git a/gcloud/container/azure/node-pools/update b/gcloud/container/azure/node-pools/update index fd24ec9bc..920b3601c 100644 --- a/gcloud/container/azure/node-pools/update +++ b/gcloud/container/azure/node-pools/update @@ -52,8 +52,7 @@ POSITIONAL ARGUMENTS ▸ provide the argument node_pool on the command line with a fully specified name; ▸ provide the argument --location on the command line; - ▸ set the property container_azure/location; - ▸ set the property azure/location (deprecated). + ▸ set the property container_azure/location. FLAGS --async diff --git a/gcloud/container/azure/operations/describe b/gcloud/container/azure/operations/describe index 41a8a945f..906733e44 100644 --- a/gcloud/container/azure/operations/describe +++ b/gcloud/container/azure/operations/describe @@ -40,8 +40,7 @@ POSITIONAL ARGUMENTS ▸ provide the argument operation_id on the command line with a fully specified name; ▸ provide the argument --location on the command line; - ▸ set the property container_azure/location; - ▸ set the property azure/location (deprecated). + ▸ set the property container_azure/location. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/container/azure/operations/list b/gcloud/container/azure/operations/list index 94e937ed7..5ffce825f 100644 --- a/gcloud/container/azure/operations/list +++ b/gcloud/container/azure/operations/list @@ -23,8 +23,6 @@ FLAGS specified name; ◆ set the property container_azure/location with a fully specified name; - ◆ set the property azure/location (deprecated) with a fully specified - name; ◆ provide the argument --project on the command line; ◆ set the property core/project. @@ -32,8 +30,7 @@ FLAGS ID of the location or fully qualified identifier for the location. To set the location attribute: ▸ provide the argument --location on the command line; - ▸ set the property container_azure/location; - ▸ set the property azure/location (deprecated). + ▸ set the property container_azure/location. LIST COMMAND FLAGS --filter=EXPRESSION diff --git a/gcloud/container/azure/operations/wait b/gcloud/container/azure/operations/wait index a5d98e1d6..9e97c9214 100644 --- a/gcloud/container/azure/operations/wait +++ b/gcloud/container/azure/operations/wait @@ -40,8 +40,7 @@ POSITIONAL ARGUMENTS ▸ provide the argument operation_id on the command line with a fully specified name; ▸ provide the argument --location on the command line; - ▸ set the property container_azure/location; - ▸ set the property azure/location (deprecated). + ▸ set the property container_azure/location. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/container/clusters/create b/gcloud/container/clusters/create index fa094056f..3b723451b 100644 --- a/gcloud/container/clusters/create +++ b/gcloud/container/clusters/create @@ -31,7 +31,7 @@ SYNOPSIS [--enable-stackdriver-kubernetes] [--enable-vertical-pod-autoscaling] [--image-type=IMAGE_TYPE] [--issue-client-certificate] [--labels=[KEY=VALUE,...]] [--local-ssd-count=LOCAL_SSD_COUNT] - [--logging=[COMPONENT,...]] + [--logging=[COMPONENT,...]] [--logging-variant=LOGGING_VARIANT] [--machine-type=MACHINE_TYPE, -m MACHINE_TYPE] [--max-nodes-per-pool=MAX_NODES_PER_POOL] [--max-pods-per-node=MAX_PODS_PER_NODE] @@ -537,6 +537,18 @@ FLAGS $ gcloud container clusters create --logging=SYSTEM,WORKLOAD $ gcloud container clusters create --logging=NONE + --logging-variant=LOGGING_VARIANT + Specifies the logging variant that will be deployed on all the nodes in + the cluster. Valid logging variants are MAX_THROUGHPUT, DEFAULT. If no + value is specified, DEFAULT is used. LOGGING_VARIANT must be one of: + + DEFAULT + 'DEFAULT' variant requests minimal resources but may not guarantee + high throughput. + MAX_THROUGHPUT + 'MAX_THROUGHPUT' variant requests more node resources and is able + to achieve logging throughput up to 10MB per sec. + --machine-type=MACHINE_TYPE, -m MACHINE_TYPE The type of machine to use for nodes. Defaults to e2-medium. The list of predefined machine types is available using the following command: @@ -1055,11 +1067,11 @@ FLAGS autoprovisioned node pool. Node Management settings are specified under the field - 'nodeManagement', which has the following fields: - enableAutoUpgrade: A boolean field that indicates if node - autoupgrade is enabled for autoprovisioned node pools. - enableAutoRepair: A boolean field that indicates if node autorepair - is enabled for autoprovisioned node pools. + 'management', which has the following fields: autoUpgrade: A + boolean field that indicates if node autoupgrade is enabled for + autoprovisioned node pools. autoRepair: A boolean field that + indicates if node autorepair is enabled for autoprovisioned node + pools. minCpuPlatform (deprecated): If specified, new autoprovisioned nodes will be scheduled on host with specified CPU architecture or diff --git a/gcloud/container/clusters/update b/gcloud/container/clusters/update index 15b10d6f7..c393dfd2b 100644 --- a/gcloud/container/clusters/update +++ b/gcloud/container/clusters/update @@ -16,8 +16,8 @@ SYNOPSIS | --enable-master-global-access | --enable-network-policy | --enable-service-externalips | --enable-shielded-nodes | --enable-stackdriver-kubernetes | --enable-vertical-pod-autoscaling - | --generate-password | --maintenance-window=START_TIME - | --node-locations=ZONE,[ZONE,...] + | --generate-password | --logging-variant=LOGGING_VARIANT + | --maintenance-window=START_TIME | --node-locations=ZONE,[ZONE,...] | --notification-config=[pubsub=ENABLED|DISABLED, pubsub-topic=TOPIC,...] | --private-ipv6-google-access-type=PRIVATE_IPV6_GOOGLE_ACCESS_TYPE @@ -265,6 +265,19 @@ REQUIRED FLAGS Ask the server to generate a secure password and use that as the basic auth password, keeping the existing username. + --logging-variant=LOGGING_VARIANT + Specifies the logging variant that will be deployed on all the nodes + in the cluster. Valid logging variants are MAX_THROUGHPUT, DEFAULT. + If no value is specified, DEFAULT is used. LOGGING_VARIANT must be + one of: + + DEFAULT + 'DEFAULT' variant requests minimal resources but may not + guarantee high throughput. + MAX_THROUGHPUT + 'MAX_THROUGHPUT' variant requests more node resources and is able + to achieve logging throughput up to 10MB per sec. + --maintenance-window=START_TIME Set a time of day when you prefer maintenance to start on this cluster. For example: @@ -687,11 +700,11 @@ REQUIRED FLAGS the same time on each upgrade of an autoprovisioned node pool. Node Management settings are specified under the field - 'nodeManagement', which has the following fields: - enableAutoUpgrade: A boolean field that indicates if node - autoupgrade is enabled for autoprovisioned node pools. - enableAutoRepair: A boolean field that indicates if node - autorepair is enabled for autoprovisioned node pools. + 'management', which has the following fields: autoUpgrade: A + boolean field that indicates if node autoupgrade is enabled for + autoprovisioned node pools. autoRepair: A boolean field that + indicates if node autorepair is enabled for autoprovisioned node + pools. minCpuPlatform (deprecated): If specified, new autoprovisioned nodes will be scheduled on host with specified CPU architecture diff --git a/gcloud/container/node-pools/create b/gcloud/container/node-pools/create index 94c3648c7..d7f1d83ea 100644 --- a/gcloud/container/node-pools/create +++ b/gcloud/container/node-pools/create @@ -15,6 +15,7 @@ SYNOPSIS [--enable-confidential-nodes] [--enable-gvnic] [--enable-image-streaming] [--enable-surge-upgrade] [--image-type=IMAGE_TYPE] [--local-ssd-count=LOCAL_SSD_COUNT] + [--logging-variant=LOGGING_VARIANT] [--machine-type=MACHINE_TYPE, -m MACHINE_TYPE] [--max-pods-per-node=MAX_PODS_PER_NODE] [--max-surge-upgrade=MAX_SURGE_UPGRADE; default=1] @@ -191,6 +192,20 @@ FLAGS https://cloud.google.com/compute/docs/disks/local-ssd for more information. + --logging-variant=LOGGING_VARIANT + Specifies the logging variant that will be deployed on all the nodes in + the node pool. If the node pool doesn't specify a logging variant, then + the logging variant specified for the cluster will be deployed on all + the nodes in the node pool. Valid logging variants are MAX_THROUGHPUT, + DEFAULT. LOGGING_VARIANT must be one of: + + DEFAULT + 'DEFAULT' variant requests minimal resources but may not guarantee + high throughput. + MAX_THROUGHPUT + 'MAX_THROUGHPUT' variant requests more node resources and is able + to achieve logging throughput up to 10MB per sec. + --machine-type=MACHINE_TYPE, -m MACHINE_TYPE The type of machine to use for nodes. Defaults to e2-medium. The list of predefined machine types is available using the following command: diff --git a/gcloud/container/node-pools/update b/gcloud/container/node-pools/update index f1864d95f..e1336ab88 100644 --- a/gcloud/container/node-pools/update +++ b/gcloud/container/node-pools/update @@ -5,7 +5,7 @@ NAME SYNOPSIS gcloud container node-pools update NAME (--enable-confidential-nodes | --enable-gvnic - | --enable-image-streaming + | --enable-image-streaming | --logging-variant=LOGGING_VARIANT | --network-performance-configs=[PROPERTY=VALUE,...] | --node-labels=[NODE_LABEL,...] | --node-locations=ZONE,[ZONE,...] | --node-taints=[NODE_TAINT,...] @@ -54,6 +54,20 @@ REQUIRED FLAGS --enable-image-streaming Specifies whether to enable image streaming on node pool. + --logging-variant=LOGGING_VARIANT + Specifies the logging variant that will be deployed on all the nodes + in the node pool. If the node pool doesn't specify a logging variant, + then the logging variant specified for the cluster will be deployed + on all the nodes in the node pool. Valid logging variants are + MAX_THROUGHPUT, DEFAULT. LOGGING_VARIANT must be one of: + + DEFAULT + 'DEFAULT' variant requests minimal resources but may not + guarantee high throughput. + MAX_THROUGHPUT + 'MAX_THROUGHPUT' variant requests more node resources and is able + to achieve logging throughput up to 10MB per sec. + --network-performance-configs=[PROPERTY=VALUE,...] Configures network performance settings for the node pool. If this flag is not specified, the pool will be created with its default diff --git a/gcloud/dataproc/clusters/gke/create b/gcloud/dataproc/clusters/gke/create index da00276db..b0240cb17 100644 --- a/gcloud/dataproc/clusters/gke/create +++ b/gcloud/dataproc/clusters/gke/create @@ -128,7 +128,7 @@ OPTIONAL FLAGS components in. This namespace does not need to exist. --pools=[KEY=VALUE[;VALUE],...] - Each --pools flag represents a single GKE node pool associated with the + Each --pools flag represents a GKE node pool associated with the virtual cluster. It is comprised of a CSV in the form KEY=VALUE[;VALUE], where certain keys may have multiple values. @@ -146,29 +146,29 @@ OPTIONAL FLAGS The following KEYs may be specified: ---------------------------------------------------------------------------------------------------------------------------------------------------------------- - KEY Type Example Description + KEY Type Example Description --------------- ---------------- --------------------------------------------- --------------------------------------------------------------------------------- - machineType string `n1-standard-8` Compute Engine machine type to use. + machineType string `n1-standard-8` Compute Engine machine type to use. - preemptible boolean `false` If true, then this node pool uses preemptible VMs. - This cannot be true on the node pool with the `controllers` role - (or `default` role if `controllers` role is not specified). + preemptible boolean `false` If true, then this node pool uses preemptible VMs. + This cannot be true on the node pool with the `controllers` role + (or `default` role if `controllers` role is not specified). - localSsdCount int `2` The number of local SSDs to attach to each node. + localSsdCount int `2` The number of local SSDs to attach to each node. - accelerator repeated string `nvidia-tesla-a100=1` Accelerators to attach to each node. In the format NAME=COUNT. + accelerator repeated string `nvidia-tesla-a100=1` Accelerators to attach to each node. In the format NAME=COUNT. - minCpuPlatform string `Intel Skylake` Minimum CPU platform for each node. + minCpuPlatform string `Intel Skylake` Minimum CPU platform for each node. - bootDiskKmsKey string `projects/project-id/locations/us-central1 The Customer Managed Encryption Key (CMEK) used to encrypt - /keyRings/keyRing-name/cryptoKeys/key-name` the boot disk attached to each node in the node pool. + bootDiskKmsKey string `projects/project-id/locations/us-central1 The Customer Managed Encryption Key (CMEK) used to encrypt + /keyRings/keyRing-name/cryptoKeys/key-name` the boot disk attached to each node in the node pool. - locations repeated string `us-west1-a;us-west1-c` Zones within the location of the GKE cluster. - All `--pools` flags for a single Dataproc cluster must have identical locations. + locations repeated string `us-west1-a;us-west1-c` Zones within the location of the GKE cluster. + All `--pools` flags for a Dataproc cluster must have identical locations. - min int `0` Minimum number of nodes per zone that this node pool can scale down to. + min int `0` Minimum number of nodes per zone that this node pool can scale down to. - max int `10` Maximum number of nodes per zone that this node pool can scale up to. + max int `10` Maximum number of nodes per zone that this node pool can scale up to. ---------------------------------------------------------------------------------------------------------------------------------------------------------------- --properties=[PREFIX:PROPERTY=VALUE,...] diff --git a/gcloud/secrets/create b/gcloud/secrets/create index 1e31634da..438d7233f 100644 --- a/gcloud/secrets/create +++ b/gcloud/secrets/create @@ -3,7 +3,8 @@ NAME SYNOPSIS gcloud secrets create SECRET [--data-file=PATH] [--labels=[KEY=VALUE,...]] - [--topics=[TOPICS,...]] [--expire-time=EXPIRE-TIME | --ttl=TTL] + [--set-annotations=[KEY=VALUE,...]] [--topics=[TOPICS,...]] + [--expire-time=EXPIRE-TIME | --ttl=TTL] [--next-rotation-time=NEXT_ROTATION_TIME --rotation-period=ROTATION_PERIOD] [--replication-policy-file=REPLICATION-POLICY-FILE @@ -89,6 +90,12 @@ FLAGS contain only hyphens (-), underscores (_), lowercase characters, and numbers. + Annotations + + --set-annotations=[KEY=VALUE,...] + List of key-value pairs to set as Annotations. All existing + Annotations will be removed first. + --topics=[TOPICS,...] List of Pub/Sub topics to configure on the secret. diff --git a/gcloud/secrets/update b/gcloud/secrets/update index 409b3979c..f9004dc4e 100644 --- a/gcloud/secrets/update +++ b/gcloud/secrets/update @@ -6,6 +6,8 @@ SYNOPSIS [--update-labels=[KEY=VALUE,...]] [--add-topics=[ADD-TOPICS,...] | --clear-topics | --remove-topics=[REMOVE-TOPICS,...]] + [--clear-annotations | --remove-annotations=[KEY,...] + | --update-annotations=[KEY=VALUE,...]] [--clear-labels | --remove-labels=[KEY,...]] [--clear-version-aliases | --remove-version-aliases=[KEY,...] | --update-version-aliases=[KEY=VALUE,...]] @@ -92,6 +94,19 @@ FLAGS --remove-topics=[REMOVE-TOPICS,...] List of Pub/Sub topics to remove from the secret. + Annotations + + At most one of these can be specified: + + --clear-annotations + Remove all Annotations. + + --remove-annotations=[KEY,...] + List of Annotations to be removed. + + --update-annotations=[KEY=VALUE,...] + List of key-value pairs to set as Annotations. + At most one of these can be specified: --clear-labels diff --git a/gcloud/secrets/versions/access b/gcloud/secrets/versions/access index 791e8a449..3ef0fe78e 100644 --- a/gcloud/secrets/versions/access +++ b/gcloud/secrets/versions/access @@ -3,7 +3,7 @@ NAME SYNOPSIS gcloud secrets versions access (VERSION : --secret=SECRET) - [GCLOUD_WIDE_FLAG ...] + [--out-file=OUT-FILE-PATH] [GCLOUD_WIDE_FLAG ...] DESCRIPTION Access the data for the specified secret version. @@ -14,7 +14,14 @@ EXAMPLES $ gcloud secrets versions access 123 --secret=my-secret Note: The output will be formatted as UTF-8 which can corrupt binary - secrets. To get the raw bytes, have Google Cloud CLI print the response as + secrets. + + To write raw bytes to a file use --out-file flag: + + $ gcloud secrets versions access 123 --secret=my-secret \ + --out-file=/tmp/secret + + To get the raw bytes, have Google Cloud CLI print the response as base64-encoded and decode: $ gcloud secrets versions access 123 --secret=my-secret \ @@ -47,6 +54,10 @@ POSITIONAL ARGUMENTS specified name; ▸ provide the argument --secret on the command line. +FLAGS + --out-file=OUT-FILE-PATH + File path to which secret data is written. + GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format,