From 4ade1b44cc0e8061a2d3885d0f15fd1e5cfdfc1e Mon Sep 17 00:00:00 2001 From: Automated Date: Wed, 27 Mar 2024 09:52:07 +0000 Subject: [PATCH] gcloud: Wed Mar 27 09:52:07 UTC 2024 --- gcloud/_version | 10 +- gcloud/ai/endpoints/deploy-model | 6 +- gcloud/alloydb/clusters/create-secondary | 58 ++++++ gcloud/alpha/ai/help | 3 + gcloud/alpha/ai/persistent-resources/create | 196 ++++++++++++++++++ gcloud/alpha/ai/persistent-resources/delete | 69 ++++++ gcloud/alpha/ai/persistent-resources/describe | 65 ++++++ gcloud/alpha/ai/persistent-resources/help | 39 ++++ gcloud/alpha/ai/persistent-resources/list | 86 ++++++++ .../alpha/alloydb/clusters/create-secondary | 58 ++++++ .../authorized-views/add-iam-policy-binding | 161 ++++++++++++++ gcloud/alpha/bigtable/authorized-views/create | 115 ++++++++++ gcloud/alpha/bigtable/authorized-views/delete | 81 ++++++++ .../alpha/bigtable/authorized-views/describe | 81 ++++++++ .../bigtable/authorized-views/get-iam-policy | 111 ++++++++++ gcloud/alpha/bigtable/authorized-views/help | 56 +++++ gcloud/alpha/bigtable/authorized-views/list | 105 ++++++++++ .../remove-iam-policy-binding | 166 +++++++++++++++ .../bigtable/authorized-views/set-iam-policy | 92 ++++++++ gcloud/alpha/bigtable/authorized-views/update | 132 ++++++++++++ gcloud/alpha/bigtable/help | 3 + gcloud/alpha/builds/submit | 8 +- gcloud/alpha/composer/environments/create | 58 +++++- gcloud/alpha/composer/environments/run | 2 +- gcloud/alpha/composer/environments/update | 90 +++++++- gcloud/alpha/compute/commitments/create | 7 +- .../compute/instance-groups/managed/create | 4 +- gcloud/alpha/compute/instances/bulk/create | 10 +- gcloud/alpha/compute/queued-resources/create | 10 +- .../alpha/compute/service-attachments/create | 22 +- .../alpha/compute/service-attachments/update | 22 +- .../compute/tpus/queued-resources/delete | 6 +- gcloud/alpha/firestore/databases/create | 20 +- gcloud/alpha/logging/sinks/create | 7 +- gcloud/alpha/logging/sinks/list | 7 +- gcloud/alpha/logging/sinks/update | 11 +- gcloud/alpha/redis/clusters/create | 56 ++++- gcloud/alpha/redis/clusters/update | 58 +++++- gcloud/alpha/spanner/operations/cancel | 9 +- gcloud/alpha/spanner/operations/help | 5 +- gcloud/alpha/spanner/operations/list | 19 +- gcloud/alpha/sql/instances/create | 9 +- gcloud/alpha/sql/instances/patch | 6 + .../managed-folders/add-iam-policy-binding | 4 +- gcloud/alpha/storage/managed-folders/create | 4 +- gcloud/alpha/storage/managed-folders/delete | 4 +- gcloud/alpha/storage/managed-folders/describe | 4 +- .../storage/managed-folders/get-iam-policy | 4 +- gcloud/alpha/storage/managed-folders/help | 4 +- gcloud/alpha/storage/managed-folders/list | 4 +- .../managed-folders/remove-iam-policy-binding | 4 +- .../storage/managed-folders/set-iam-policy | 4 +- gcloud/alpha/workstations/configs/create | 40 ++++ gcloud/alpha/workstations/configs/update | 41 +++- gcloud/alpha/workstations/start | 9 +- gcloud/beta/ai/persistent-resources/create | 5 +- gcloud/beta/ai/persistent-resources/delete | 5 +- gcloud/beta/ai/persistent-resources/describe | 5 +- gcloud/beta/ai/persistent-resources/help | 5 +- gcloud/beta/ai/persistent-resources/list | 5 +- gcloud/beta/alloydb/clusters/create-secondary | 58 ++++++ .../authorized-views/add-iam-policy-binding | 159 ++++++++++++++ gcloud/beta/bigtable/authorized-views/create | 113 ++++++++++ gcloud/beta/bigtable/authorized-views/delete | 79 +++++++ .../beta/bigtable/authorized-views/describe | 79 +++++++ .../bigtable/authorized-views/get-iam-policy | 109 ++++++++++ gcloud/beta/bigtable/authorized-views/help | 54 +++++ gcloud/beta/bigtable/authorized-views/list | 103 +++++++++ .../remove-iam-policy-binding | 164 +++++++++++++++ .../bigtable/authorized-views/set-iam-policy | 90 ++++++++ gcloud/beta/bigtable/authorized-views/update | 130 ++++++++++++ gcloud/beta/bigtable/help | 3 + gcloud/beta/builds/submit | 8 +- gcloud/beta/composer/environments/create | 58 +++++- gcloud/beta/composer/environments/run | 2 +- gcloud/beta/composer/environments/update | 90 +++++++- gcloud/beta/compute/images/list | 14 +- .../compute/instance-groups/managed/create | 7 + gcloud/beta/compute/instances/bulk/create | 9 +- gcloud/beta/logging/sinks/create | 7 +- gcloud/beta/logging/sinks/list | 7 +- gcloud/beta/logging/sinks/update | 11 +- gcloud/beta/redis/clusters/create | 56 ++++- gcloud/beta/redis/clusters/update | 58 +++++- gcloud/beta/secrets/add-iam-policy-binding | 33 +-- gcloud/beta/secrets/create | 41 +--- gcloud/beta/secrets/delete | 32 +-- gcloud/beta/secrets/describe | 32 +-- gcloud/beta/secrets/get-iam-policy | 35 +--- gcloud/beta/secrets/remove-iam-policy-binding | 33 +-- gcloud/beta/secrets/set-iam-policy | 33 +-- gcloud/beta/secrets/update | 31 +-- gcloud/beta/secrets/versions/access | 35 ++-- gcloud/beta/secrets/versions/add | 33 +-- gcloud/beta/secrets/versions/destroy | 30 +-- gcloud/beta/secrets/versions/disable | 30 +-- gcloud/beta/secrets/versions/enable | 36 ++-- gcloud/beta/secrets/versions/list | 36 +--- gcloud/beta/spanner/operations/help | 3 +- gcloud/beta/spanner/operations/list | 6 +- gcloud/beta/sql/instances/create | 9 +- gcloud/beta/sql/instances/patch | 6 + gcloud/beta/workstations/configs/create | 40 ++++ gcloud/beta/workstations/configs/update | 41 +++- gcloud/beta/workstations/start | 9 +- .../authorized-views/add-iam-policy-binding | 158 ++++++++++++++ gcloud/bigtable/authorized-views/create | 112 ++++++++++ gcloud/bigtable/authorized-views/delete | 78 +++++++ gcloud/bigtable/authorized-views/describe | 78 +++++++ .../bigtable/authorized-views/get-iam-policy | 108 ++++++++++ gcloud/bigtable/authorized-views/help | 51 +++++ gcloud/bigtable/authorized-views/list | 101 +++++++++ .../remove-iam-policy-binding | 163 +++++++++++++++ .../bigtable/authorized-views/set-iam-policy | 89 ++++++++ gcloud/bigtable/authorized-views/update | 129 ++++++++++++ gcloud/bigtable/help | 3 + gcloud/builds/submit | 8 +- gcloud/composer/environments/run | 2 +- gcloud/composer/environments/update | 5 + gcloud/compute/instances/bulk/create | 9 +- gcloud/compute/tpus/queued-resources/delete | 8 +- gcloud/logging/sinks/create | 7 +- gcloud/logging/sinks/list | 7 +- gcloud/logging/sinks/update | 11 +- gcloud/redis/clusters/create | 55 ++++- gcloud/redis/clusters/update | 58 +++++- gcloud/redis/instances/create | 2 + gcloud/redis/instances/upgrade | 2 + gcloud/spanner/operations/help | 3 +- gcloud/spanner/operations/list | 6 +- gcloud/sql/instances/create | 9 +- gcloud/sql/instances/patch | 6 + gcloud/storage/cp | 8 +- gcloud/storage/help | 3 + .../managed-folders/add-iam-policy-binding | 111 ++++++++++ gcloud/storage/managed-folders/create | 40 ++++ gcloud/storage/managed-folders/delete | 47 +++++ gcloud/storage/managed-folders/describe | 44 ++++ gcloud/storage/managed-folders/get-iam-policy | 41 ++++ gcloud/storage/managed-folders/help | 46 ++++ gcloud/storage/managed-folders/list | 77 +++++++ .../managed-folders/remove-iam-policy-binding | 106 ++++++++++ gcloud/storage/managed-folders/set-iam-policy | 56 +++++ gcloud/storage/mv | 8 +- gcloud/storage/rm | 7 +- gcloud/storage/rsync | 11 +- gcloud/workstations/configs/create | 16 ++ gcloud/workstations/configs/update | 16 ++ 148 files changed, 5765 insertions(+), 482 deletions(-) create mode 100644 gcloud/alpha/ai/persistent-resources/create create mode 100644 gcloud/alpha/ai/persistent-resources/delete create mode 100644 gcloud/alpha/ai/persistent-resources/describe create mode 100644 gcloud/alpha/ai/persistent-resources/help create mode 100644 gcloud/alpha/ai/persistent-resources/list create mode 100644 gcloud/alpha/bigtable/authorized-views/add-iam-policy-binding create mode 100644 gcloud/alpha/bigtable/authorized-views/create create mode 100644 gcloud/alpha/bigtable/authorized-views/delete create mode 100644 gcloud/alpha/bigtable/authorized-views/describe create mode 100644 gcloud/alpha/bigtable/authorized-views/get-iam-policy create mode 100644 gcloud/alpha/bigtable/authorized-views/help create mode 100644 gcloud/alpha/bigtable/authorized-views/list create mode 100644 gcloud/alpha/bigtable/authorized-views/remove-iam-policy-binding create mode 100644 gcloud/alpha/bigtable/authorized-views/set-iam-policy create mode 100644 gcloud/alpha/bigtable/authorized-views/update create mode 100644 gcloud/beta/bigtable/authorized-views/add-iam-policy-binding create mode 100644 gcloud/beta/bigtable/authorized-views/create create mode 100644 gcloud/beta/bigtable/authorized-views/delete create mode 100644 gcloud/beta/bigtable/authorized-views/describe create mode 100644 gcloud/beta/bigtable/authorized-views/get-iam-policy create mode 100644 gcloud/beta/bigtable/authorized-views/help create mode 100644 gcloud/beta/bigtable/authorized-views/list create mode 100644 gcloud/beta/bigtable/authorized-views/remove-iam-policy-binding create mode 100644 gcloud/beta/bigtable/authorized-views/set-iam-policy create mode 100644 gcloud/beta/bigtable/authorized-views/update create mode 100644 gcloud/bigtable/authorized-views/add-iam-policy-binding create mode 100644 gcloud/bigtable/authorized-views/create create mode 100644 gcloud/bigtable/authorized-views/delete create mode 100644 gcloud/bigtable/authorized-views/describe create mode 100644 gcloud/bigtable/authorized-views/get-iam-policy create mode 100644 gcloud/bigtable/authorized-views/help create mode 100644 gcloud/bigtable/authorized-views/list create mode 100644 gcloud/bigtable/authorized-views/remove-iam-policy-binding create mode 100644 gcloud/bigtable/authorized-views/set-iam-policy create mode 100644 gcloud/bigtable/authorized-views/update create mode 100644 gcloud/storage/managed-folders/add-iam-policy-binding create mode 100644 gcloud/storage/managed-folders/create create mode 100644 gcloud/storage/managed-folders/delete create mode 100644 gcloud/storage/managed-folders/describe create mode 100644 gcloud/storage/managed-folders/get-iam-policy create mode 100644 gcloud/storage/managed-folders/help create mode 100644 gcloud/storage/managed-folders/list create mode 100644 gcloud/storage/managed-folders/remove-iam-policy-binding create mode 100644 gcloud/storage/managed-folders/set-iam-policy diff --git a/gcloud/_version b/gcloud/_version index 3980e963a..66a974f1e 100644 --- a/gcloud/_version +++ b/gcloud/_version @@ -1,8 +1,8 @@ -Google Cloud SDK 469.0.0 -alpha 2024.03.15 -beta 2024.03.15 -bq 2.1.1 +Google Cloud SDK 470.0.0 +alpha 2024.03.22 +beta 2024.03.22 +bq 2.1.2 bundled-python3-unix 3.11.8 -core 2024.03.15 +core 2024.03.22 gcloud-crc32c 1.0.0 gsutil 5.27 diff --git a/gcloud/ai/endpoints/deploy-model b/gcloud/ai/endpoints/deploy-model index 037529fcb..bec854795 100644 --- a/gcloud/ai/endpoints/deploy-model +++ b/gcloud/ai/endpoints/deploy-model @@ -70,9 +70,9 @@ OPTIONAL FLAGS type The type of the accelerator. Choices are 'nvidia-a100-80gb', - 'nvidia-l4', 'nvidia-tesla-a100', 'nvidia-tesla-k80', - 'nvidia-tesla-p100', 'nvidia-tesla-p4', 'nvidia-tesla-t4', - 'nvidia-tesla-v100'. + 'nvidia-h100-80gb', 'nvidia-l4', 'nvidia-tesla-a100', + 'nvidia-tesla-k80', 'nvidia-tesla-p100', 'nvidia-tesla-p4', + 'nvidia-tesla-t4', 'nvidia-tesla-v100'. count The number of accelerators to attach to each machine running the diff --git a/gcloud/alloydb/clusters/create-secondary b/gcloud/alloydb/clusters/create-secondary index 2aa18ade4..3d57e0e93 100644 --- a/gcloud/alloydb/clusters/create-secondary +++ b/gcloud/alloydb/clusters/create-secondary @@ -6,6 +6,10 @@ SYNOPSIS gcloud alloydb clusters create-secondary CLUSTER --primary-cluster=PRIMARY_CLUSTER --region=REGION [--allocated-ip-range-name=ALLOCATED_IP_RANGE_NAME] [--async] + [--continuous-backup-recovery-window-days=RECOVERY_PERIOD + --enable-continuous-backup + [--continuous-backup-encryption-key=CONTINUOUS_BACKUP_ENCRYPTION_KEY + : --continuous-backup-encryption-key-keyring=CONTINUOUS_BACKUP_ENCRYPTION_KEY_KEYRING --continuous-backup-encryption-key-location=CONTINUOUS_BACKUP_ENCRYPTION_KEY_LOCATION --continuous-backup-encryption-key-project=CONTINUOUS_BACKUP_ENCRYPTION_KEY_PROJECT]] [--kms-key=KMS_KEY : --kms-keyring=KMS_KEYRING --kms-location=KMS_LOCATION --kms-project=KMS_PROJECT] [GCLOUD_WIDE_FLAG ...] @@ -46,6 +50,60 @@ OPTIONAL FLAGS Return immediately, without waiting for the operation in progress to complete. + Continuous Backup configuration. If unspecified, continuous backups are + copied from the associated primary cluster. + + --continuous-backup-recovery-window-days=RECOVERY_PERIOD + Recovery window of the log files and backups saved to support + Continuous Backups. + + --enable-continuous-backup + Enables Continuous Backups on the cluster. + + Key resource - The Cloud KMS (Key Management Service) cryptokey that + will be used to protect the continuous backup. The 'AlloyDB Service + Agent's service account must hold permission 'Cloud KMS CryptoKey + Encrypter/Decrypter'. The arguments in this group can be used to specify + the attributes of this resource. + + --continuous-backup-encryption-key=CONTINUOUS_BACKUP_ENCRYPTION_KEY + ID of the key or fully qualified identifier for the key. + + To set the kms-key attribute: + ▫ provide the argument --continuous-backup-encryption-key on the + command line. + + This flag argument must be specified if any of the other arguments + in this group are specified. + + --continuous-backup-encryption-key-keyring=CONTINUOUS_BACKUP_ENCRYPTION_KEY_KEYRING + The KMS keyring of the key. + + To set the kms-keyring attribute: + ▫ provide the argument --continuous-backup-encryption-key on the + command line with a fully specified name; + ▫ provide the argument --continuous-backup-encryption-key-keyring + on the command line. + + --continuous-backup-encryption-key-location=CONTINUOUS_BACKUP_ENCRYPTION_KEY_LOCATION + The Google Cloud location for the key. + + To set the kms-location attribute: + ▫ provide the argument --continuous-backup-encryption-key on the + command line with a fully specified name; + ▫ provide the argument + --continuous-backup-encryption-key-location on the command line. + + --continuous-backup-encryption-key-project=CONTINUOUS_BACKUP_ENCRYPTION_KEY_PROJECT + The Google Cloud project for the key. + + To set the kms-project attribute: + ▫ provide the argument --continuous-backup-encryption-key on the + command line with a fully specified name; + ▫ provide the argument --continuous-backup-encryption-key-project + on the command line; + ▫ set the property core/project. + Key resource - The Cloud KMS (Key Management Service) cryptokey that will be used to protect the cluster. The 'AlloyDB Service Agent' service account must hold permission 'Cloud KMS CryptoKey Encrypter/Decrypter'. diff --git a/gcloud/alpha/ai/help b/gcloud/alpha/ai/help index 2a6eb3b13..ce00c1f47 100644 --- a/gcloud/alpha/ai/help +++ b/gcloud/alpha/ai/help @@ -39,6 +39,9 @@ GROUPS operations (ALPHA) Manage Vertex AI operations. + persistent-resources + (ALPHA) Create and manage Vertex AI Persistent Resources. + tensorboard-experiments (ALPHA) Manage Vertex AI Tensorboard experiments. diff --git a/gcloud/alpha/ai/persistent-resources/create b/gcloud/alpha/ai/persistent-resources/create new file mode 100644 index 000000000..958a08862 --- /dev/null +++ b/gcloud/alpha/ai/persistent-resources/create @@ -0,0 +1,196 @@ +NAME + gcloud alpha ai persistent-resources create - create a new persistent + resource + +SYNOPSIS + gcloud alpha ai persistent-resources create + --persistent-resource-id=PERSISTENT_RESOURCE_ID + (--config=CONFIG --resource-pool-spec=[RESOURCE_POOL_SPEC,...]) + [--display-name=DISPLAY_NAME] [--enable-custom-service-account] + [--labels=[KEY=VALUE,...]] [--network=NETWORK] [--region=REGION] + [--kms-key=KMS_KEY : --kms-keyring=KMS_KEYRING + --kms-location=KMS_LOCATION --kms-project=KMS_PROJECT] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) This command will create a persistent resource on the users project + to use with Vertex AI custom training jobs. Persistent resources remain + active until they are deleted by the user. + +EXAMPLES + To create a PersistentResource under project example in region us-central1, + run: + + $ gcloud alpha ai persistent-resources create --region=us-central1 \ + --project=example \ + --resource-pool-spec=replica-count=1,\ + machine-type='n1-standard-4' --display-name=example-resource + +REQUIRED FLAGS + --persistent-resource-id=PERSISTENT_RESOURCE_ID + User-specified ID of the Persistent Resource. + + resource pool specification. + + At least one of these must be specified: + + --config=CONFIG + Path to the Persistent Resource configuration file. This file should + be a YAML document containing a list of ResourcePool If an option is + specified both in the configuration file **and** via command-line + arguments, the command-line arguments override the configuration + file. Note that keys with underscore are invalid. + + Example(YAML): + + resourcePoolSpecs: + machineSpec: + machineType: n1-standard-4 + replicaCount: 1 + + --resource-pool-spec=[RESOURCE_POOL_SPEC,...] + Defines a resource pool to be created in the Persistent Resource. You + can include multiple resource pool specs in order to create a + Persistent Resource with multiple resource pools. + + The spec can contain the following fields: + + machine-type + (Required): The type of the machine. see + https://cloud.google.com/vertex-ai/docs/training/configure-compute#machine-types + for supported types. This field corresponds to the + machineSpec.machineType field in ResourcePool API message. + replica-count + (Required if autoscaling not enabled) The number of replicas to + use when creating this resource pool. This field corresponds to + the replicaCount field in 'ResourcePool' API message. + min-replica-count + (Optional) The minimum number of replicas that autoscaling will + down-size to for this resource pool. Both min-replica-count and + max-replica-count are required to enable autoscaling on this + resource pool. The value for this parameter must be at least 1. + max-replica-count + (Optional) The maximum number of replicas that autoscaling will + create for this resource pool. Both min-replica-count and + max-replica-count are required to enable autoscaling on this + resource pool. The maximum value for this parameter is 1000. + accelerator-type + (Optional) The type of GPU to attach to the machines. see + https://cloud.google.com/vertex-ai/docs/training/configure-compute#specifying_gpus + for more requirements. This field corresponds to the + machineSpec.acceleratorType field in ResourcePool API message. + accelerator-count + (Required with accelerator-type) The number of GPUs for each VM + in the resource pool to use. The default the value if 1. This + field corresponds to the machineSpec.acceleratorCount field in + ResourcePool API message. + disk-type + (Optional) The type of disk to use for each machine's boot disk + in the resource pool. The default is pd-standard. This field + corresponds to the diskSpec.bootDiskType field in ResourcePool + API message. + disk-size + (Optional) The disk size in Gb for each machine's boot disk in + the resource pool. The default is 100. This field corresponds to + the diskSpec.bootDiskSizeGb field in ResourcePool API message. + + Example: --worker-pool-spec=replica-count=1,machine-type=n1-highmem-2 + +OPTIONAL FLAGS + --display-name=DISPLAY_NAME + Display name of the Persistent Resource. + + --enable-custom-service-account + Whether or not to use a custom user-managed service account with this + Persistent Resource. + + --labels=[KEY=VALUE,...] + List of label KEY=VALUE pairs to add. + + Keys must start with a lowercase character and contain only hyphens + (-), underscores (_), lowercase characters, and numbers. Values must + contain only hyphens (-), underscores (_), lowercase characters, and + numbers. + + --network=NETWORK + Full name of the Google Compute Engine network to which the Job is + peered with. Private services access must already have been configured. + If unspecified, the Job is not peered with any network. + + Region resource - Cloud region to create a Persistent Resource. This + represents a Cloud resource. (NOTE) Some attributes are not given + arguments in this group but can be set in other ways. + + To set the project attribute: + ◆ provide the argument --region on the command line with a fully + specified name; + ◆ set the property ai/region with a fully specified name; + ◆ choose one from the prompted list of available regions with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + --region=REGION + ID of the region or fully qualified identifier for the region. + + To set the region attribute: + ▸ provide the argument --region on the command line; + ▸ set the property ai/region; + ▸ choose one from the prompted list of available regions. + + Key resource - The Cloud KMS (Key Management Service) cryptokey that will + be used to protect the persistent resource. The 'Vertex AI Service Agent' + service account must hold permission 'Cloud KMS CryptoKey + Encrypter/Decrypter'. The arguments in this group can be used to specify + the attributes of this resource. + + --kms-key=KMS_KEY + ID of the key or fully qualified identifier for the key. + + To set the kms-key attribute: + ▸ provide the argument --kms-key on the command line. + + This flag argument must be specified if any of the other arguments in + this group are specified. + + --kms-keyring=KMS_KEYRING + The KMS keyring of the key. + + To set the kms-keyring attribute: + ▸ provide the argument --kms-key on the command line with a fully + specified name; + ▸ provide the argument --kms-keyring on the command line. + + --kms-location=KMS_LOCATION + The Google Cloud location for the key. + + To set the kms-location attribute: + ▸ provide the argument --kms-key on the command line with a fully + specified name; + ▸ provide the argument --kms-location on the command line. + + --kms-project=KMS_PROJECT + The Google Cloud project for the key. + + To set the kms-project attribute: + ▸ provide the argument --kms-key on the command line with a fully + specified name; + ▸ provide the argument --kms-project on the command line; + ▸ set the property core/project. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud beta ai persistent-resources create + diff --git a/gcloud/alpha/ai/persistent-resources/delete b/gcloud/alpha/ai/persistent-resources/delete new file mode 100644 index 000000000..9956dac46 --- /dev/null +++ b/gcloud/alpha/ai/persistent-resources/delete @@ -0,0 +1,69 @@ +NAME + gcloud alpha ai persistent-resources delete - delete an active Persistent + Resource + +SYNOPSIS + gcloud alpha ai persistent-resources delete + (PERSISTENT_RESOURCE : --region=REGION) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) If the Persistent Resource is not in the active state, the command + will not perform any operation. + +EXAMPLES + To delete a persistent resource 123 under project example in region + us-central1, run: + + $ gcloud alpha ai persistent-resources delete 123 \ + --project=example --region=us-central1 + +POSITIONAL ARGUMENTS + Persistent resource resource - The persistent resource to delete. 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 persistent_resource 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. + + PERSISTENT_RESOURCE + ID of the persistent resource or fully qualified identifier for the + persistent resource. + + To set the name attribute: + ▸ provide the argument persistent_resource on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --region=REGION + Cloud region for the persistent resource. + + To set the region attribute: + ▸ provide the argument persistent_resource on the command line with + a fully specified name; + ▸ provide the argument --region on the command line; + ▸ set the property ai/region; + ▸ choose one from the prompted list of available regions. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud beta ai persistent-resources delete + diff --git a/gcloud/alpha/ai/persistent-resources/describe b/gcloud/alpha/ai/persistent-resources/describe new file mode 100644 index 000000000..65a206a9d --- /dev/null +++ b/gcloud/alpha/ai/persistent-resources/describe @@ -0,0 +1,65 @@ +NAME + gcloud alpha ai persistent-resources describe - get detailed information + about a PersistentResource with a given id + +SYNOPSIS + gcloud alpha ai persistent-resources describe + (PERSISTENT_RESOURCE : --region=REGION) [GCLOUD_WIDE_FLAG ...] + +EXAMPLES + To get the persistent resource with the PersistentResource id 123 under + project example in region us-central1, run: + + $ gcloud alpha ai persistent-resources describe 123 \ + --project=example --region=us-central1 + +POSITIONAL ARGUMENTS + Persistent resource resource - The persistent resource to describe. 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 persistent_resource 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. + + PERSISTENT_RESOURCE + ID of the persistent resource or fully qualified identifier for the + persistent resource. + + To set the name attribute: + ▸ provide the argument persistent_resource on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --region=REGION + Cloud region for the persistent resource. + + To set the region attribute: + ▸ provide the argument persistent_resource on the command line with + a fully specified name; + ▸ provide the argument --region on the command line; + ▸ set the property ai/region; + ▸ choose one from the prompted list of available regions. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud beta ai persistent-resources describe + diff --git a/gcloud/alpha/ai/persistent-resources/help b/gcloud/alpha/ai/persistent-resources/help new file mode 100644 index 000000000..d0038a351 --- /dev/null +++ b/gcloud/alpha/ai/persistent-resources/help @@ -0,0 +1,39 @@ +NAME + gcloud alpha ai persistent-resources - create and manage Vertex AI + Persistent Resources + +SYNOPSIS + gcloud alpha ai persistent-resources COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Create and manage Vertex AI Persistent Resources. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + create + (ALPHA) Create a new persistent resource. + + delete + (ALPHA) Delete an active Persistent Resource. + + describe + (ALPHA) Get detailed information about a PersistentResource with a + given id. + + list + (ALPHA) Lists the active persistent resources. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud beta ai persistent-resources + diff --git a/gcloud/alpha/ai/persistent-resources/list b/gcloud/alpha/ai/persistent-resources/list new file mode 100644 index 000000000..3eab6fe75 --- /dev/null +++ b/gcloud/alpha/ai/persistent-resources/list @@ -0,0 +1,86 @@ +NAME + gcloud alpha ai persistent-resources list - lists the active persistent + resources + +SYNOPSIS + gcloud alpha ai persistent-resources list [--region=REGION] + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + +EXAMPLES + To list the persistent resources of project example in region us-central1, + run: + + $ gcloud alpha ai persistent-resources list --project=example \ + --region=us-central1 + +FLAGS + Region resource - Cloud region to list persistent resources. This + represents a Cloud resource. (NOTE) Some attributes are not given + arguments in this group but can be set in other ways. + + To set the project attribute: + ◆ provide the argument --region on the command line with a fully + specified name; + ◆ set the property ai/region with a fully specified name; + ◆ choose one from the prompted list of available regions with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + --region=REGION + ID of the region or fully qualified identifier for the region. + + To set the region attribute: + ▸ provide the argument --region on the command line; + ▸ set the property ai/region; + ▸ choose one from the prompted list of available regions. + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + + --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 ai persistent-resources list + diff --git a/gcloud/alpha/alloydb/clusters/create-secondary b/gcloud/alpha/alloydb/clusters/create-secondary index beb1bce0b..4a4e80899 100644 --- a/gcloud/alpha/alloydb/clusters/create-secondary +++ b/gcloud/alpha/alloydb/clusters/create-secondary @@ -6,6 +6,10 @@ SYNOPSIS gcloud alpha alloydb clusters create-secondary CLUSTER --primary-cluster=PRIMARY_CLUSTER --region=REGION [--allocated-ip-range-name=ALLOCATED_IP_RANGE_NAME] [--async] + [--continuous-backup-recovery-window-days=RECOVERY_PERIOD + --enable-continuous-backup + [--continuous-backup-encryption-key=CONTINUOUS_BACKUP_ENCRYPTION_KEY + : --continuous-backup-encryption-key-keyring=CONTINUOUS_BACKUP_ENCRYPTION_KEY_KEYRING --continuous-backup-encryption-key-location=CONTINUOUS_BACKUP_ENCRYPTION_KEY_LOCATION --continuous-backup-encryption-key-project=CONTINUOUS_BACKUP_ENCRYPTION_KEY_PROJECT]] [--kms-key=KMS_KEY : --kms-keyring=KMS_KEYRING --kms-location=KMS_LOCATION --kms-project=KMS_PROJECT] [GCLOUD_WIDE_FLAG ...] @@ -46,6 +50,60 @@ OPTIONAL FLAGS Return immediately, without waiting for the operation in progress to complete. + Continuous Backup configuration. If unspecified, continuous backups are + copied from the associated primary cluster. + + --continuous-backup-recovery-window-days=RECOVERY_PERIOD + Recovery window of the log files and backups saved to support + Continuous Backups. + + --enable-continuous-backup + Enables Continuous Backups on the cluster. + + Key resource - The Cloud KMS (Key Management Service) cryptokey that + will be used to protect the continuous backup. The 'AlloyDB Service + Agent's service account must hold permission 'Cloud KMS CryptoKey + Encrypter/Decrypter'. The arguments in this group can be used to specify + the attributes of this resource. + + --continuous-backup-encryption-key=CONTINUOUS_BACKUP_ENCRYPTION_KEY + ID of the key or fully qualified identifier for the key. + + To set the kms-key attribute: + ▫ provide the argument --continuous-backup-encryption-key on the + command line. + + This flag argument must be specified if any of the other arguments + in this group are specified. + + --continuous-backup-encryption-key-keyring=CONTINUOUS_BACKUP_ENCRYPTION_KEY_KEYRING + The KMS keyring of the key. + + To set the kms-keyring attribute: + ▫ provide the argument --continuous-backup-encryption-key on the + command line with a fully specified name; + ▫ provide the argument --continuous-backup-encryption-key-keyring + on the command line. + + --continuous-backup-encryption-key-location=CONTINUOUS_BACKUP_ENCRYPTION_KEY_LOCATION + The Google Cloud location for the key. + + To set the kms-location attribute: + ▫ provide the argument --continuous-backup-encryption-key on the + command line with a fully specified name; + ▫ provide the argument + --continuous-backup-encryption-key-location on the command line. + + --continuous-backup-encryption-key-project=CONTINUOUS_BACKUP_ENCRYPTION_KEY_PROJECT + The Google Cloud project for the key. + + To set the kms-project attribute: + ▫ provide the argument --continuous-backup-encryption-key on the + command line with a fully specified name; + ▫ provide the argument --continuous-backup-encryption-key-project + on the command line; + ▫ set the property core/project. + Key resource - The Cloud KMS (Key Management Service) cryptokey that will be used to protect the cluster. The 'AlloyDB Service Agent' service account must hold permission 'Cloud KMS CryptoKey Encrypter/Decrypter'. diff --git a/gcloud/alpha/bigtable/authorized-views/add-iam-policy-binding b/gcloud/alpha/bigtable/authorized-views/add-iam-policy-binding new file mode 100644 index 000000000..6390f7b97 --- /dev/null +++ b/gcloud/alpha/bigtable/authorized-views/add-iam-policy-binding @@ -0,0 +1,161 @@ +NAME + gcloud alpha bigtable authorized-views add-iam-policy-binding - add an IAM + policy binding to a Cloud Bigtable authorized view + +SYNOPSIS + gcloud alpha bigtable authorized-views add-iam-policy-binding + (AUTHORIZED_VIEW : --instance=INSTANCE --table=TABLE) + --member=PRINCIPAL --role=ROLE + [--condition=[KEY=VALUE,...] + | --condition-from-file=CONDITION_FROM_FILE] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Add an IAM policy binding to a Cloud Bigtable authorized view. One + binding consists of a member, a role, and an optional condition. + +EXAMPLES + To add an IAM policy binding for the role of 'roles/editor' for the user + 'test-user@gmail.com' with authorized view 'my-authorized-view' in instance + 'my-instance' and table 'my-table', run: + + $ gcloud alpha bigtable authorized-views add-iam-policy-binding \ + my-authorized-view --instance='my-instance' --table='my-table' \ + --member='user:test-user@gmail.com' --role='roles/editor' + + To add an IAM policy binding which expires at the end of the year 2020 for + the role of 'roles/bigtable.admin' and the user 'test-user@gmail.com' with + authorized view 'my-authorized-view' in instance 'my-instance' and table + 'my-table', run: + + $ gcloud alpha bigtable authorized-views add-iam-policy-binding \ + my-authorized-view --instance='my-instance' --table='my-table' \ + --member='user:test-user@gmail.com' \ + --role='roles/bigtable.admin' \ + --condition='expression=request.time < + timestamp("2021-01-01T00:00:00Z"),title=expires_end_of_2020,descrip\ + tion=Expires at midnight on 2020-12-31' + + See https://cloud.google.com/iam/docs/managing-policies for details of + policy role and member types. + +POSITIONAL ARGUMENTS + Authorized view resource - Cloud Bigtable authorized view to add the IAM + policy binding to. 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 authorized_view 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. + + AUTHORIZED_VIEW + ID of the authorized-view or fully qualified identifier for the + authorized-view. + + To set the authorized_view attribute: + ▸ provide the argument authorized_view on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --instance=INSTANCE + Name of the Cloud Bigtable instance. + + To set the instance attribute: + ▸ provide the argument authorized_view on the command line with a + fully specified name; + ▸ provide the argument --instance on the command line. + + --table=TABLE + Name of the Cloud Bigtable table. + + To set the table attribute: + ▸ provide the argument authorized_view on the command line with a + fully specified name; + ▸ provide the argument --table on the command line. + +REQUIRED FLAGS + --member=PRINCIPAL + The principal to add the binding for. Should be of the form + user|group|serviceAccount:email or domain:domain. + + Examples: user:test-user@gmail.com, group:admins@example.com, + serviceAccount:test123@example.domain.com, or + domain:example.domain.com. + + Some resources also accept the following special values: + ◆ allUsers - Special identifier that represents anyone who is on the + internet, with or without a Google account. + ◆ allAuthenticatedUsers - Special identifier that represents anyone + who is authenticated with a Google account or a service account. + + --role=ROLE + Role name to assign to the principal. The role name is the complete + path of a predefined role, such as roles/logging.viewer, or the role ID + for a custom role, such as + organizations/{ORGANIZATION_ID}/roles/logging.viewer. + +OPTIONAL FLAGS + At most one of these can be specified: + + --condition=[KEY=VALUE,...] + A condition to include in the binding. When the condition is + explicitly specified as None (--condition=None), a binding without a + condition is added. When the condition is specified and is not None, + --role cannot be a basic role. Basic roles are roles/editor, + roles/owner, and roles/viewer. For more on conditions, refer to the + conditions overview guide: + https://cloud.google.com/iam/docs/conditions-overview + + When using the --condition flag, include the following key-value + pairs: + + expression + (Required) Condition expression that evaluates to True or False. + This uses a subset of Common Expression Language syntax. + + If the condition expression includes a comma, use a different + delimiter to separate the key-value pairs. Specify the delimiter + before listing the key-value pairs. For example, to specify a + colon (:) as the delimiter, do the following: + --condition=^:^title=TITLE:expression=EXPRESSION. For more + information, see + https://cloud.google.com/sdk/gcloud/reference/topic/escaping. + + title + (Required) A short string describing the purpose of the + expression. + + description + (Optional) Additional description for the expression. + + --condition-from-file=CONDITION_FROM_FILE + Path to a local JSON or YAML file that defines the condition. To see + available fields, see the help for --condition. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the bigtableadmin/v2 API. The full documentation for this + API can be found at: https://cloud.google.com/bigtable/ + +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. These variants are also available: + + $ gcloud bigtable authorized-views add-iam-policy-binding + + $ gcloud beta bigtable authorized-views add-iam-policy-binding + diff --git a/gcloud/alpha/bigtable/authorized-views/create b/gcloud/alpha/bigtable/authorized-views/create new file mode 100644 index 000000000..8cf798371 --- /dev/null +++ b/gcloud/alpha/bigtable/authorized-views/create @@ -0,0 +1,115 @@ +NAME + gcloud alpha bigtable authorized-views create - create a new Cloud Bigtable + authorized view + +SYNOPSIS + gcloud alpha bigtable authorized-views create + (AUTHORIZED_VIEW : --instance=INSTANCE --table=TABLE) [--async] + [--definition-file=DEFINITION_FILE] [--pre-encoded] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Create a new Cloud Bigtable authorized view. + +EXAMPLES + To create an authorized view 'my-authorized-view' in instance 'my-instance' + and table 'my-table', using the definition file 'authorized_view.json': + + $ gcloud alpha bigtable authorized-views create my-authorized-view \ + --instance=test-instance --table=test-table \ + --definition-file=authorized_view.json + + To create an authorized view 'my-authorized-view' in instance 'my-instance' + and table 'my-table', using the pre-encoded definition file + 'authorized_view_pre_encoded.json': + + $ gcloud alpha bigtable authorized-views create my-authorized-view \ + --instance=test-instance --table=test-table \ + --definition-file=authorized_view_pre_encoded.json --pre-encoded + +POSITIONAL ARGUMENTS + Authorized view resource - Cloud Bigtable authorized view to create. 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 authorized_view 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. + + AUTHORIZED_VIEW + ID of the authorized-view or fully qualified identifier for the + authorized-view. + + To set the authorized_view attribute: + ▸ provide the argument authorized_view on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --instance=INSTANCE + Name of the Cloud Bigtable instance. + + To set the instance attribute: + ▸ provide the argument authorized_view on the command line with a + fully specified name; + ▸ provide the argument --instance on the command line. + + --table=TABLE + Name of the Cloud Bigtable table. + + To set the table attribute: + ▸ provide the argument authorized_view on the command line with a + fully specified name; + ▸ provide the argument --table on the command line. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --definition-file=DEFINITION_FILE + Path to a JSON or YAML file containing a valid authorized view + protobuf. + + The 'name' field is ignored. The name is deduced from the other command + line arguments. + + Example: { "subsetView": { "rowPrefixes": ["store1#"], "familySubsets": + { "column_family_name": { "qualifiers":["address"], + "qualifierPrefixes":["tel"] } } }, "deletionProtection": true } + + --pre-encoded + By default, Base64 encoding is applied to all binary fields + ("rowPrefixes", "qualifiers" and "qualifierPrefixes") in the JSON or + YAML definition file. + + Use this to indicate that all binary fields are already Base64-encoded + and should be used directly. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the bigtableadmin/v2 API. The full documentation for this + API can be found at: https://cloud.google.com/bigtable/ + +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. These variants are also available: + + $ gcloud bigtable authorized-views create + + $ gcloud beta bigtable authorized-views create + diff --git a/gcloud/alpha/bigtable/authorized-views/delete b/gcloud/alpha/bigtable/authorized-views/delete new file mode 100644 index 000000000..ab4143043 --- /dev/null +++ b/gcloud/alpha/bigtable/authorized-views/delete @@ -0,0 +1,81 @@ +NAME + gcloud alpha bigtable authorized-views delete - delete a Cloud Bigtable + authorized view + +SYNOPSIS + gcloud alpha bigtable authorized-views delete + (AUTHORIZED_VIEW : --instance=INSTANCE --table=TABLE) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Delete new Cloud Bigtable authorized view. + +EXAMPLES + To delete the authorized view 'my-authorized-view' in instance + 'my-instance' and table 'my-table': + + $ gcloud alpha bigtable authorized-views delete my-authorized-view \ + --instance=test-instance --table=test-table + +POSITIONAL ARGUMENTS + Authorized view resource - Cloud Bigtable authorized view to delete. 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 authorized_view 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. + + AUTHORIZED_VIEW + ID of the authorized-view or fully qualified identifier for the + authorized-view. + + To set the authorized_view attribute: + ▸ provide the argument authorized_view on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --instance=INSTANCE + Name of the Cloud Bigtable instance. + + To set the instance attribute: + ▸ provide the argument authorized_view on the command line with a + fully specified name; + ▸ provide the argument --instance on the command line. + + --table=TABLE + Name of the Cloud Bigtable table. + + To set the table attribute: + ▸ provide the argument authorized_view on the command line with a + fully specified name; + ▸ provide the argument --table on the command line. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the bigtableadmin/v2 API. The full documentation for this + API can be found at: https://cloud.google.com/bigtable/ + +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. These variants are also available: + + $ gcloud bigtable authorized-views delete + + $ gcloud beta bigtable authorized-views delete + diff --git a/gcloud/alpha/bigtable/authorized-views/describe b/gcloud/alpha/bigtable/authorized-views/describe new file mode 100644 index 000000000..132af2d80 --- /dev/null +++ b/gcloud/alpha/bigtable/authorized-views/describe @@ -0,0 +1,81 @@ +NAME + gcloud alpha bigtable authorized-views describe - describe a Cloud Bigtable + authorized view + +SYNOPSIS + gcloud alpha bigtable authorized-views describe + (AUTHORIZED_VIEW : --instance=INSTANCE --table=TABLE) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Describe a Cloud Bigtable authorized view. + +EXAMPLES + To describe the authorized view 'my-authorized-view' in instance + 'my-instance' and table 'my-table': + + $ gcloud alpha bigtable authorized-views describe \ + my-authorized-view --instance=test-instance --table=test-table + +POSITIONAL ARGUMENTS + Authorized view resource - Cloud Bigtable authorized view to describe. 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 authorized_view 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. + + AUTHORIZED_VIEW + ID of the authorized-view or fully qualified identifier for the + authorized-view. + + To set the authorized_view attribute: + ▸ provide the argument authorized_view on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --instance=INSTANCE + Name of the Cloud Bigtable instance. + + To set the instance attribute: + ▸ provide the argument authorized_view on the command line with a + fully specified name; + ▸ provide the argument --instance on the command line. + + --table=TABLE + Name of the Cloud Bigtable table. + + To set the table attribute: + ▸ provide the argument authorized_view on the command line with a + fully specified name; + ▸ provide the argument --table on the command line. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the bigtableadmin/v2 API. The full documentation for this + API can be found at: https://cloud.google.com/bigtable/ + +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. These variants are also available: + + $ gcloud bigtable authorized-views describe + + $ gcloud beta bigtable authorized-views describe + diff --git a/gcloud/alpha/bigtable/authorized-views/get-iam-policy b/gcloud/alpha/bigtable/authorized-views/get-iam-policy new file mode 100644 index 000000000..a489068b0 --- /dev/null +++ b/gcloud/alpha/bigtable/authorized-views/get-iam-policy @@ -0,0 +1,111 @@ +NAME + gcloud alpha bigtable authorized-views get-iam-policy - get an IAM policy + on a Cloud Bigtable authorized view + +SYNOPSIS + gcloud alpha bigtable authorized-views get-iam-policy + (AUTHORIZED_VIEW : --instance=INSTANCE --table=TABLE) + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Get an IAM policy on a Cloud Bigtable authorized view. + +EXAMPLES + To get the IAM policy on the authorized view 'my-authorized-view' in + instance 'my-instance' and table 'my-table', run: + + $ gcloud alpha bigtable authorized-views get-iam-policy \ + my-authorized-view --instance='my-instance' --table='my-table' + + See https://cloud.google.com/iam/docs/managing-policies for more + information. + +POSITIONAL ARGUMENTS + Authorized view resource - Cloud Bigtable authorized view to get the IAM + policy for. 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 authorized_view 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. + + AUTHORIZED_VIEW + ID of the authorized-view or fully qualified identifier for the + authorized-view. + + To set the authorized_view attribute: + ▸ provide the argument authorized_view on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --instance=INSTANCE + Name of the Cloud Bigtable instance. + + To set the instance attribute: + ▸ provide the argument authorized_view on the command line with a + fully specified name; + ▸ provide the argument --instance on the command line. + + --table=TABLE + Name of the Cloud Bigtable table. + + To set the table attribute: + ▸ provide the argument authorized_view on the command line with a + fully specified name; + ▸ provide the argument --table on the command line. + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the bigtableadmin/v2 API. The full documentation for this + API can be found at: https://cloud.google.com/bigtable/ + +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. These variants are also available: + + $ gcloud bigtable authorized-views get-iam-policy + + $ gcloud beta bigtable authorized-views get-iam-policy + diff --git a/gcloud/alpha/bigtable/authorized-views/help b/gcloud/alpha/bigtable/authorized-views/help new file mode 100644 index 000000000..99b0e7fde --- /dev/null +++ b/gcloud/alpha/bigtable/authorized-views/help @@ -0,0 +1,56 @@ +NAME + gcloud alpha bigtable authorized-views - manage Cloud Bigtable Authorized + Views + +SYNOPSIS + gcloud alpha bigtable authorized-views COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Manage Cloud Bigtable Authorized Views. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + add-iam-policy-binding + (ALPHA) Add an IAM policy binding to a Cloud Bigtable authorized view. + + create + (ALPHA) Create a new Cloud Bigtable authorized view. + + delete + (ALPHA) Delete a Cloud Bigtable authorized view. + + describe + (ALPHA) Describe a Cloud Bigtable authorized view. + + get-iam-policy + (ALPHA) Get an IAM policy on a Cloud Bigtable authorized view. + + list + (ALPHA) List all authorized views of a Cloud Bigtable table. + + remove-iam-policy-binding + (ALPHA) Remove an IAM policy binding from a Cloud Bigtable authorized + view. + + set-iam-policy + (ALPHA) Set an IAM policy on a Cloud Bigtable authorized view. + + update + (ALPHA) Update an existing Cloud Bigtable authorized view. + +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. These variants are also available: + + $ gcloud bigtable authorized-views + + $ gcloud beta bigtable authorized-views + diff --git a/gcloud/alpha/bigtable/authorized-views/list b/gcloud/alpha/bigtable/authorized-views/list new file mode 100644 index 000000000..3453b043e --- /dev/null +++ b/gcloud/alpha/bigtable/authorized-views/list @@ -0,0 +1,105 @@ +NAME + gcloud alpha bigtable authorized-views list - list all authorized views of + a Cloud Bigtable table + +SYNOPSIS + gcloud alpha bigtable authorized-views list + (--table=TABLE : --instance=INSTANCE) [--filter=EXPRESSION] + [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) List all authorized views of a Cloud Bigtable table. + +EXAMPLES + To list the authorized views in instance 'my-instance' and table + 'my-table': + + $ gcloud alpha bigtable authorized-views list \ + --instance=test-instance --table=test-table + +REQUIRED FLAGS + Table resource - Cloud Bigtable table for which to list all authorized + views. 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 --table 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. + + --table=TABLE + ID of the table or fully qualified identifier for the table. + + To set the table attribute: + ▸ provide the argument --table on the command line. + + This flag argument must be specified if any of the other arguments in + this group are specified. + + --instance=INSTANCE + Name of the Cloud Bigtable instance. + + To set the instance attribute: + ▸ provide the argument --table on the command line with a fully + specified name; + ▸ provide the argument --instance on the command line. + +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. + +API REFERENCE + This command uses the bigtableadmin/v2 API. The full documentation for this + API can be found at: https://cloud.google.com/bigtable/ + +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. These variants are also available: + + $ gcloud bigtable authorized-views list + + $ gcloud beta bigtable authorized-views list + diff --git a/gcloud/alpha/bigtable/authorized-views/remove-iam-policy-binding b/gcloud/alpha/bigtable/authorized-views/remove-iam-policy-binding new file mode 100644 index 000000000..a5673bf02 --- /dev/null +++ b/gcloud/alpha/bigtable/authorized-views/remove-iam-policy-binding @@ -0,0 +1,166 @@ +NAME + gcloud alpha bigtable authorized-views remove-iam-policy-binding - remove + an IAM policy binding from a Cloud Bigtable authorized view + +SYNOPSIS + gcloud alpha bigtable authorized-views remove-iam-policy-binding + (AUTHORIZED_VIEW : --instance=INSTANCE --table=TABLE) + --member=PRINCIPAL --role=ROLE + [--all | --condition=[KEY=VALUE,...] + | --condition-from-file=CONDITION_FROM_FILE] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Remove an IAM policy binding from a Cloud Bigtable authorized view. + One binding consists of a member, a role, and an optional condition. + +EXAMPLES + To remove an IAM policy binding for the role of 'roles/editor' for the user + 'test-user@gmail.com' with authorized view 'my-authorized-view' in instance + 'my-instance' and table 'my-table', run: + + $ gcloud alpha bigtable authorized-views remove-iam-policy-binding \ + my-authorized-view --instance='my-instance' --table='my-table' \ + --member='user:test-user@gmail.com' --role='roles/editor' + + To remove an IAM policy binding which expires at the end of the year 2020 + for the role of 'roles/bigtable.admin' and the user 'test-user@gmail.com' + with authorized view 'my-authorized-view' in instance 'my-instance' and + cluster 'my-cluster', run: + + $ gcloud alpha bigtable authorized-views remove-iam-policy-binding \ + my-authorized-view --instance='my-instance' --table='my-table' \ + --member='user:test-user@gmail.com' \ + --role='roles/bigtable.admin' \ + --condition='expression=request.time < + timestamp("2021-01-01T00:00:00Z"),title=expires_end_of_2020,descrip\ + tion=Expires at midnight on 2020-12-31' + + See https://cloud.google.com/iam/docs/managing-policies for details of + policy role and member types. + +POSITIONAL ARGUMENTS + Authorized view resource - Cloud Bigtable authorized view to remove the + IAM policy binding from. The arguments in this group can be used to + specify the attributes of this resource. (NOTE) Some attributes are not + given arguments in this group but can be set in other ways. + + To set the project attribute: + ◆ provide the argument authorized_view 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. + + AUTHORIZED_VIEW + ID of the authorized-view or fully qualified identifier for the + authorized-view. + + To set the authorized_view attribute: + ▸ provide the argument authorized_view on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --instance=INSTANCE + Name of the Cloud Bigtable instance. + + To set the instance attribute: + ▸ provide the argument authorized_view on the command line with a + fully specified name; + ▸ provide the argument --instance on the command line. + + --table=TABLE + Name of the Cloud Bigtable table. + + To set the table attribute: + ▸ provide the argument authorized_view on the command line with a + fully specified name; + ▸ provide the argument --table on the command line. + +REQUIRED FLAGS + --member=PRINCIPAL + The principal to remove the binding for. Should be of the form + user|group|serviceAccount:email or domain:domain. + + Examples: user:test-user@gmail.com, group:admins@example.com, + serviceAccount:test123@example.domain.com, or + domain:example.domain.com. + + Deleted principals have an additional deleted: prefix and a ?uid=UID + suffix, where UID is a unique identifier for the principal. Example: + deleted:user:test-user@gmail.com?uid=123456789012345678901. + + Some resources also accept the following special values: + ◆ allUsers - Special identifier that represents anyone who is on the + internet, with or without a Google account. + ◆ allAuthenticatedUsers - Special identifier that represents anyone + who is authenticated with a Google account or a service account. + + --role=ROLE + The role to remove the principal from. + +OPTIONAL FLAGS + At most one of these can be specified: + + --all + Remove all bindings with this role and principal, irrespective of any + conditions. + + --condition=[KEY=VALUE,...] + The condition of the binding that you want to remove. When the + condition is explicitly specified as None (--condition=None), a + binding without a condition is removed. Otherwise, only a binding + with a condition that exactly matches the specified condition + (including the optional description) is removed. For more on + conditions, refer to the conditions overview guide: + https://cloud.google.com/iam/docs/conditions-overview + + When using the --condition flag, include the following key-value + pairs: + + expression + (Required) Condition expression that evaluates to True or False. + This uses a subset of Common Expression Language syntax. + + If the condition expression includes a comma, use a different + delimiter to separate the key-value pairs. Specify the delimiter + before listing the key-value pairs. For example, to specify a + colon (:) as the delimiter, do the following: + --condition=^:^title=TITLE:expression=EXPRESSION. For more + information, see + https://cloud.google.com/sdk/gcloud/reference/topic/escaping. + + title + (Required) A short string describing the purpose of the + expression. + + description + (Optional) Additional description for the expression. + + --condition-from-file=CONDITION_FROM_FILE + Path to a local JSON or YAML file that defines the condition. To see + available fields, see the help for --condition. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the bigtableadmin/v2 API. The full documentation for this + API can be found at: https://cloud.google.com/bigtable/ + +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. These variants are also available: + + $ gcloud bigtable authorized-views remove-iam-policy-binding + + $ gcloud beta bigtable authorized-views remove-iam-policy-binding + diff --git a/gcloud/alpha/bigtable/authorized-views/set-iam-policy b/gcloud/alpha/bigtable/authorized-views/set-iam-policy new file mode 100644 index 000000000..d1056b2fe --- /dev/null +++ b/gcloud/alpha/bigtable/authorized-views/set-iam-policy @@ -0,0 +1,92 @@ +NAME + gcloud alpha bigtable authorized-views set-iam-policy - set an IAM policy + on a Cloud Bigtable authorized view + +SYNOPSIS + gcloud alpha bigtable authorized-views set-iam-policy + (AUTHORIZED_VIEW : --instance=INSTANCE --table=TABLE) POLICY_FILE + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Set an IAM policy on a Cloud Bigtable authorized view. + +EXAMPLES + To set the IAM policy from file 'my-policy' on the authorized view + 'my-authorized-view' in instance 'my-instance' and table 'my-table', run: + + $ gcloud alpha bigtable authorized-views set-iam-policy \ + my-authorized-view --instance='my-instance' --table='my-table' \ + my-policy + + See https://cloud.google.com/iam/docs/managing-policies for more + information. + +POSITIONAL ARGUMENTS + Authorized view resource - Cloud Bigtable authorized view to set the IAM + policy 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 authorized_view 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. + + AUTHORIZED_VIEW + ID of the authorized-view or fully qualified identifier for the + authorized-view. + + To set the authorized_view attribute: + ▸ provide the argument authorized_view on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --instance=INSTANCE + Name of the Cloud Bigtable instance. + + To set the instance attribute: + ▸ provide the argument authorized_view on the command line with a + fully specified name; + ▸ provide the argument --instance on the command line. + + --table=TABLE + Name of the Cloud Bigtable table. + + To set the table attribute: + ▸ provide the argument authorized_view on the command line with a + fully specified name; + ▸ provide the argument --table on the command line. + + POLICY_FILE + Path to a local JSON or YAML formatted file containing a valid policy. + + The output of the get-iam-policy command is a valid file, as is any + JSON or YAML file conforming to the structure of a Policy + (https://cloud.google.com/iam/reference/rest/v1/Policy). + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the bigtableadmin/v2 API. The full documentation for this + API can be found at: https://cloud.google.com/bigtable/ + +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. These variants are also available: + + $ gcloud bigtable authorized-views set-iam-policy + + $ gcloud beta bigtable authorized-views set-iam-policy + diff --git a/gcloud/alpha/bigtable/authorized-views/update b/gcloud/alpha/bigtable/authorized-views/update new file mode 100644 index 000000000..0bbcf0628 --- /dev/null +++ b/gcloud/alpha/bigtable/authorized-views/update @@ -0,0 +1,132 @@ +NAME + gcloud alpha bigtable authorized-views update - update an existing Cloud + Bigtable authorized view + +SYNOPSIS + gcloud alpha bigtable authorized-views update + (AUTHORIZED_VIEW : --instance=INSTANCE --table=TABLE) [--async] + [--definition-file=DEFINITION_FILE] [--ignore-warnings] + [--no-interactive] [--pre-encoded] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Update an existing Cloud Bigtable authorized view. + +EXAMPLES + To update the authorized view 'my-authorized-view' in instance + 'my-instance' and table 'my-table', using the definition file + 'authorized_view.json': + + $ gcloud alpha bigtable authorized-views update my-authorized-view \ + --instance=test-instance --table=test-table \ + --definition-file=authorized_view.json + + To update the authorized view 'my-authorized-view' in instance + 'my-instance' and table 'my-table', using the pre-encoded definition file + 'authorized_view_pre_encoded.json': + + $ gcloud alpha bigtable authorized-views update my-authorized-view \ + --instance=test-instance --table=test-table \ + --definition-file=authorized_view_pre_encoded.json --pre-encoded + + To update the authorized view 'my-authorized-view' in instance + 'my-instance' and table 'my-table', using the definition file + 'authorized_view.json' and skip the prompt to proceed or cancel the update: + + $ gcloud alpha bigtable authorized-views update my-authorized-view \ + --instance=test-instance --table=test-table \ + --definition-file=authorized_view.json --no-interactive + +POSITIONAL ARGUMENTS + Authorized view resource - Cloud Bigtable authorized view to update. 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 authorized_view 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. + + AUTHORIZED_VIEW + ID of the authorized-view or fully qualified identifier for the + authorized-view. + + To set the authorized_view attribute: + ▸ provide the argument authorized_view on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --instance=INSTANCE + Name of the Cloud Bigtable instance. + + To set the instance attribute: + ▸ provide the argument authorized_view on the command line with a + fully specified name; + ▸ provide the argument --instance on the command line. + + --table=TABLE + Name of the Cloud Bigtable table. + + To set the table attribute: + ▸ provide the argument authorized_view on the command line with a + fully specified name; + ▸ provide the argument --table on the command line. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --definition-file=DEFINITION_FILE + Path to a JSON or YAML file containing a valid authorized view + protobuf. + + The 'name' field is ignored. The name is deduced from the other command + line arguments. + + Example: { "subsetView": { "rowPrefixes": ["store1"], "familySubsets": + { "column_family_name": { "qualifiers":["address"], + "qualifierPrefixes":["tel"] } } }, "deletionProtection": true } + + --ignore-warnings + If true, changes that make the authorized view more restrictive are + allowed. + + --interactive + If provided, a diff is displayed with a prompt to proceed or cancel the + update. Enabled by default, use --no-interactive to disable. + + --pre-encoded + By default, Base64 encoding is applied to all binary fields + ("rowPrefixes", "qualifiers" and "qualifierPrefixes") in the JSON or + YAML definition file. + + Use this to indicate that all binary fields are already Base64-encoded + and should be used directly. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the bigtableadmin/v2 API. The full documentation for this + API can be found at: https://cloud.google.com/bigtable/ + +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. These variants are also available: + + $ gcloud bigtable authorized-views update + + $ gcloud beta bigtable authorized-views update + diff --git a/gcloud/alpha/bigtable/help b/gcloud/alpha/bigtable/help index f7b044f15..4e8d3f794 100644 --- a/gcloud/alpha/bigtable/help +++ b/gcloud/alpha/bigtable/help @@ -18,6 +18,9 @@ GROUPS app-profiles (ALPHA) Manage Cloud Bigtable app profiles. + authorized-views + (ALPHA) Manage Cloud Bigtable Authorized Views. + backups (ALPHA) Manage Cloud Bigtable backups. diff --git a/gcloud/alpha/builds/submit b/gcloud/alpha/builds/submit index 0969efd60..d66f64a15 100644 --- a/gcloud/alpha/builds/submit +++ b/gcloud/alpha/builds/submit @@ -9,8 +9,8 @@ SYNOPSIS [--git-source-dir=GIT_SOURCE_DIR] [--git-source-revision=GIT_SOURCE_REVISION] [--ignore-file=IGNORE_FILE] [--machine-type=MACHINE_TYPE] [--region=REGION] [--revision=REVISION] - [--substitutions=[KEY=VALUE,...]] [--suppress-logs] [--timeout=TIMEOUT] - [--worker-pool=WORKER_POOL] + [--service-account=SERVICE_ACCOUNT] [--substitutions=[KEY=VALUE,...]] + [--suppress-logs] [--timeout=TIMEOUT] [--worker-pool=WORKER_POOL] [--config=CONFIG; default="cloudbuild.yaml" | --pack=[builder=BUILDER],[env=ENV],[image=IMAGE] | --tag=TAG, -t TAG] [GCLOUD_WIDE_FLAG ...] @@ -161,6 +161,10 @@ FLAGS https://git-scm.com/docs/gitrevisions#_specifying_revisions. For information on git fetch, see https://git-scm.com/docs/git-fetch. + --service-account=SERVICE_ACCOUNT + The service account to use with this build. If unset, the default + service account will be used. + --substitutions=[KEY=VALUE,...] Parameters to be substituted in the build specification. diff --git a/gcloud/alpha/composer/environments/create b/gcloud/alpha/composer/environments/create index f8e9454ba..8e2891c97 100644 --- a/gcloud/alpha/composer/environments/create +++ b/gcloud/alpha/composer/environments/create @@ -7,13 +7,15 @@ SYNOPSIS (ENVIRONMENT : --location=LOCATION) [--airflow-configs=[KEY=VALUE,...]] [--async] [--cloud-sql-machine-type=CLOUD_SQL_MACHINE_TYPE] [--cloud-sql-preferred-zone=CLOUD_SQL_PREFERRED_ZONE] + [--composer-internal-ipv4-cidr-block=COMPOSER_INTERNAL_IPV4_CIDR_BLOCK] [--disable-logs-in-cloud-logging-only] [--disk-size=DISK_SIZE] [--enable-high-resilience] [--enable-logs-in-cloud-logging-only] [--env-variables=[NAME=VALUE,...]] [--environment-size=ENVIRONMENT_SIZE] [--labels=[KEY=VALUE,...]] - [--machine-type=MACHINE_TYPE] [--node-count=NODE_COUNT] - [--oauth-scopes=[SCOPE,...]] [--python-version=PYTHON_VERSION] - [--service-account=SERVICE_ACCOUNT] [--storage-bucket=STORAGE_BUCKET] + [--machine-type=MACHINE_TYPE] [--network-attachment=NETWORK_ATTACHMENT] + [--node-count=NODE_COUNT] [--oauth-scopes=[SCOPE,...]] + [--python-version=PYTHON_VERSION] [--service-account=SERVICE_ACCOUNT] + [--storage-bucket=STORAGE_BUCKET] [--support-web-server-plugins] [--tags=[TAG,...]] [--web-server-machine-type=WEB_SERVER_MACHINE_TYPE] [--zone=ZONE] [--airflow-version=AIRFLOW_VERSION | --image-version=IMAGE_VERSION] @@ -30,8 +32,13 @@ SYNOPSIS --max-pods-per-node=MAX_PODS_PER_NODE --services-ipv4-cidr=SERVICES_IPV4_CIDR --services-secondary-range-name=SERVICES_SECONDARY_RANGE_NAME] + [--dag-processor-count=DAG_PROCESSOR_COUNT + --dag-processor-cpu=DAG_PROCESSOR_CPU + --dag-processor-memory=DAG_PROCESSOR_MEMORY + --dag-processor-storage=DAG_PROCESSOR_STORAGE] [--disable-cloud-data-lineage-integration | --enable-cloud-data-lineage-integration] + [--disable-private-builds-only | --enable-private-builds-only] [--enable-master-authorized-networks --master-authorized-networks=[NETWORK,...]] [--enable-scheduled-snapshot-creation @@ -128,6 +135,11 @@ FLAGS --cloud-sql-preferred-zone=CLOUD_SQL_PREFERRED_ZONE Select cloud sql preferred zone, supported for Composer 2 Environments. + --composer-internal-ipv4-cidr-block=COMPOSER_INTERNAL_IPV4_CIDR_BLOCK + The IP range in CIDR notation to use internally by Cloud Composer. This + should have a netmask length of 20. Can be specified for Composer 3 or + greater. + --disable-logs-in-cloud-logging-only Disable logs in cloud logging only, supported for Composer 2 Environments. @@ -171,6 +183,10 @@ FLAGS (https://cloud.google.com/compute/docs/machine-types) to use for nodes. For example --machine-type=n1-standard-1. + --network-attachment=NETWORK_ATTACHMENT + Cloud Composer Network Attachment, which provides connectivity with a + user's VPC network, supported in Composer 3 environments or greater. + --node-count=NODE_COUNT The number of nodes to create to run the environment. @@ -198,6 +214,10 @@ FLAGS Name of an exisiting Cloud Storage bucket to be used by the environment. Supported only for Composer 2.4.X and above. + --support-web-server-plugins + Enable the support for web server plugins, supported in Composer 3 or + greater. + --tags=[TAG,...] The set of instance tags applied to all node VMs. Tags are used to identify valid sources or targets for network firewalls. Each tag @@ -385,6 +405,27 @@ FLAGS When used with Composer 1.x, cannot be specified unless --enable-ip-alias is also specified. + Group of arguments for setting dag processor settings in Composer 3 or + greater. + + --dag-processor-count=DAG_PROCESSOR_COUNT + Number of dag processors, supported in Composer 3 environments or + greater. + + --dag-processor-cpu=DAG_PROCESSOR_CPU + CPU allocated to Airflow dag processor, supported in Composer 3 + environments or greater. + + --dag-processor-memory=DAG_PROCESSOR_MEMORY + Memory allocated to Airflow dag processor, ex. 1GB, 3GB, 2. If units + are not provided, defaults to GB, supported in Composer 3 + environments or greater. + + --dag-processor-storage=DAG_PROCESSOR_STORAGE + Storage allocated to Airflow dag processor, ex. 600MB, 3GB, 2. If + units are not provided, defaults to GB, supported in Composer 3 + environments or greater. + At most one of these can be specified: --disable-cloud-data-lineage-integration @@ -395,6 +436,17 @@ FLAGS Enable Cloud Data Lineage integration, supported for Composer 2 Environments. + At most one of these can be specified: + + --disable-private-builds-only + Builds performed during operations that install Python packages have + an access to the internet supported in Composer 3 or greater. + + --enable-private-builds-only + Builds performed during operations that install Python packages have + only private connectivity to Google services, supported in Composer 3 + or greater. + Master Authorized Networks configuration --enable-master-authorized-networks diff --git a/gcloud/alpha/composer/environments/run b/gcloud/alpha/composer/environments/run index bddf79418..5d63b8bef 100644 --- a/gcloud/alpha/composer/environments/run +++ b/gcloud/alpha/composer/environments/run @@ -98,7 +98,7 @@ POSITIONAL ARGUMENTS [SUBCOMMAND_NESTED] Additional subcommand in case it is nested. The following is a list of allowed nested subcommands: - ◆ db: check + ◆ db: check, trim ◆ all other subcommands: all nested subcommands are allowed [-- CMD_ARGS ...] diff --git a/gcloud/alpha/composer/environments/update b/gcloud/alpha/composer/environments/update index 004a4c530..496e70c8c 100644 --- a/gcloud/alpha/composer/environments/update +++ b/gcloud/alpha/composer/environments/update @@ -7,10 +7,13 @@ SYNOPSIS (ENVIRONMENT : --location=LOCATION) (--cloud-sql-machine-type=CLOUD_SQL_MACHINE_TYPE | --disable-high-resilience | --disable-logs-in-cloud-logging-only - | --enable-high-resilience | --enable-logs-in-cloud-logging-only + | --disable-private-environment | --enable-high-resilience + | --enable-logs-in-cloud-logging-only | --enable-private-environment | --environment-size=ENVIRONMENT_SIZE | --node-count=NODE_COUNT + | --support-web-server-plugins | --web-server-machine-type=WEB_SERVER_MACHINE_TYPE | --airflow-version=AIRFLOW_VERSION | --image-version=IMAGE_VERSION + | --clear-maintenance-window | --maintenance-window-end=MAINTENANCE_WINDOW_END --maintenance-window-recurrence=MAINTENANCE_WINDOW_RECURRENCE --maintenance-window-start=MAINTENANCE_WINDOW_START @@ -19,19 +22,26 @@ SYNOPSIS | --disable-master-authorized-networks --enable-master-authorized-networks --master-authorized-networks=[NETWORK,...] + | --disable-private-builds-only | --enable-private-builds-only | --disable-scheduled-snapshot-creation | --enable-scheduled-snapshot-creation --snapshot-creation-schedule=SNAPSHOT_CREATION_SCHEDULE --snapshot-location=SNAPSHOT_LOCATION --snapshot-schedule-timezone=SNAPSHOT_SCHEDULE_TIMEZONE + | --disable-vpc-connectivity + | --network-attachment=NETWORK_ATTACHMENT + | [--network=NETWORK : --subnetwork=SUBNETWORK] | --max-workers=MAX_WORKERS --min-workers=MIN_WORKERS --scheduler-count=SCHEDULER_COUNT --scheduler-cpu=SCHEDULER_CPU --scheduler-memory=SCHEDULER_MEMORY --scheduler-storage=SCHEDULER_STORAGE --web-server-cpu=WEB_SERVER_CPU --web-server-memory=WEB_SERVER_MEMORY --web-server-storage=WEB_SERVER_STORAGE --worker-cpu=WORKER_CPU - --worker-memory=WORKER_MEMORY - --worker-storage=WORKER_STORAGE --disable-triggerer + --worker-memory=WORKER_MEMORY --worker-storage=WORKER_STORAGE + --dag-processor-count=DAG_PROCESSOR_COUNT + --dag-processor-cpu=DAG_PROCESSOR_CPU + --dag-processor-memory=DAG_PROCESSOR_MEMORY + --dag-processor-storage=DAG_PROCESSOR_STORAGE --disable-triggerer | --enable-triggerer --triggerer-count=TRIGGERER_COUNT --triggerer-cpu=TRIGGERER_CPU --triggerer-memory=TRIGGERER_MEMORY | --update-airflow-configs=[KEY=VALUE,...] --clear-airflow-configs @@ -108,6 +118,10 @@ REQUIRED FLAGS Disable logs in cloud logging only, supported for Composer 2 Environments. + --disable-private-environment + Enable internet connection from any Composer component, supported in + Composer 3 environments or greater. + --enable-high-resilience Enable high resilience, supported for Composer 2 Environments. @@ -115,6 +129,10 @@ REQUIRED FLAGS Enable logs in cloud logging only, supported for Composer 2 Environments. + --enable-private-environment + Disable internet connection from any Composer component, supported in + Composer 3 environments or greater. + --environment-size=ENVIRONMENT_SIZE Size of the environment. Unspecified means that the default option will be chosen. ENVIRONMENT_SIZE must be one of: large, medium, @@ -123,6 +141,10 @@ REQUIRED FLAGS --node-count=NODE_COUNT The new number of nodes running the environment. Must be >= 3. + --support-web-server-plugins + Enable the support for web server plugins, supported in Composer 3 or + greater. + --web-server-machine-type=WEB_SERVER_MACHINE_TYPE machine type used by the Airflow web server. The list of available machine types is available here: @@ -169,6 +191,10 @@ REQUIRED FLAGS At most one of these can be specified: + --clear-maintenance-window + Clears the maintenance window settings. Can be specified for + Composer 3 or greater. + Group of arguments for setting the maintenance window value. --maintenance-window-end=MAINTENANCE_WINDOW_END @@ -233,6 +259,17 @@ REQUIRED FLAGS Cannot be specified unless --enable-master-authorized-networks is also specified. + At most one of these can be specified: + + --disable-private-builds-only + Builds performed during operations that install Python packages + have an access to the internet supported in Composer 3 or greater. + + --enable-private-builds-only + Builds performed during operations that install Python packages + have only private connectivity to Google services, supported in + Composer 3 or greater. + Group of arguments used during update of scheduled snapshots settings in Composer 2.0.32 or greater. @@ -276,6 +313,32 @@ REQUIRED FLAGS This flag argument must be specified if any of the other arguments in this group are specified. + At most one of these can be specified: + + --disable-vpc-connectivity + Disable connectivity with a user's VPC network, supported in + Composer 3 environments or greater. + + --network-attachment=NETWORK_ATTACHMENT + Cloud Composer Network Attachment, which provides connectivity with + a user's VPC network, supported in Composer 3 environments or + greater. + + Virtual Private Cloud networking + + --network=NETWORK + The Compute Engine Network to which the environment will be + connected. If a 'Custom Subnet Network' is provided, --subnetwork + must be specified as well. + + This flag argument must be specified if any of the other + arguments in this group are specified. + + --subnetwork=SUBNETWORK + The Compute Engine subnetwork + (https://cloud.google.com/compute/docs/subnetworks) to which the + environment will be connected. + Group of arguments for setting workloads configuration in Composer 2.X or greater (--scheduler-count flag is available for Composer 1.X as well). @@ -323,6 +386,27 @@ REQUIRED FLAGS Storage allocated to Airflow worker, ex. 600MB, 3GB, 2. If units are not provided, defaults to GB. + Group of arguments for setting dag processor settings in Composer 3 or + greater. + + --dag-processor-count=DAG_PROCESSOR_COUNT + Number of dag processors, supported in Composer 3 environments or + greater. + + --dag-processor-cpu=DAG_PROCESSOR_CPU + CPU allocated to Airflow dag processor, supported in Composer 3 + environments or greater. + + --dag-processor-memory=DAG_PROCESSOR_MEMORY + Memory allocated to Airflow dag processor, ex. 1GB, 3GB, 2. If + units are not provided, defaults to GB, supported in Composer 3 + environments or greater. + + --dag-processor-storage=DAG_PROCESSOR_STORAGE + Storage allocated to Airflow dag processor, ex. 600MB, 3GB, 2. If + units are not provided, defaults to GB, supported in Composer 3 + environments or greater. + Group of arguments for setting triggerer settings in Composer 2.0.31 or greater. diff --git a/gcloud/alpha/compute/commitments/create b/gcloud/alpha/compute/commitments/create index 6363488e4..b2059476f 100644 --- a/gcloud/alpha/compute/commitments/create +++ b/gcloud/alpha/compute/commitments/create @@ -100,9 +100,10 @@ OPTIONAL FLAGS --type=TYPE; default="general-purpose" Type of commitment. memory-optimized indicates that the commitment is for memory-optimized VMs. TYPE must be one of: accelerator-optimized, - accelerator-optimized-a3, compute-optimized, compute-optimized-c2d, - compute-optimized-c3, compute-optimized-c3d, compute-optimized-h3, - general-purpose, general-purpose-e2, general-purpose-n2, + accelerator-optimized-a3, accelerator-optimized-a3-mega, + compute-optimized, compute-optimized-c2d, compute-optimized-c3, + compute-optimized-c3d, compute-optimized-h3, general-purpose, + general-purpose-c4, general-purpose-e2, general-purpose-n2, general-purpose-n2d, general-purpose-n4, general-purpose-t2d, graphics-optimized, memory-optimized, memory-optimized-m3, storage-optimized-z3. diff --git a/gcloud/alpha/compute/instance-groups/managed/create b/gcloud/alpha/compute/instance-groups/managed/create index 76eb0427d..5b363aff3 100644 --- a/gcloud/alpha/compute/instance-groups/managed/create +++ b/gcloud/alpha/compute/instance-groups/managed/create @@ -158,7 +158,9 @@ OPTIONAL FLAGS --resource-manager-tags=[KEY=VALUE,...] Specifies a list of resource manager tags to apply to the managed - instance group. + instance group. A resource manager tag is a key-value pair. You can + attach exactly one value to a MIG for a given key. A MIG can have a + maximum of 50 key-value pairs attached. --standby-policy-initial-delay=STANDBY_POLICY_INITIAL_DELAY Specifies the number of seconds that the MIG should wait before diff --git a/gcloud/alpha/compute/instances/bulk/create b/gcloud/alpha/compute/instances/bulk/create index fb6ed9101..220a4f601 100644 --- a/gcloud/alpha/compute/instances/bulk/create +++ b/gcloud/alpha/compute/instances/bulk/create @@ -613,8 +613,9 @@ OPTIONAL FLAGS --network-interface=[PROPERTY=VALUE,...] Adds a network interface to the instance. Mutually exclusive with any - of these flags: --network, --network-tier, --subnet. This flag can be - repeated to specify multiple network interfaces. + of these flags: --network, --network-tier, --no-address, --subnet, + --stack-type. This flag can be repeated to specify multiple network + interfaces. network Specifies the network that the interface will be part of. If subnet @@ -645,6 +646,11 @@ OPTIONAL FLAGS https://cloud.google.com/compute/docs/network-bandwidth#rx-tx for more details. + stack-type + Specifies whether IPv6 is enabled on the interface. STACK_TYPE must + be one of: IPV4_ONLY, IPV4_IPV6, IPV6_ONLY. The default value is + IPV4_ONLY. + --network-performance-configs=[PROPERTY=VALUE,...] Configures network performance settings for the instance. If this flag is not specified, the instance will be created with its default network diff --git a/gcloud/alpha/compute/queued-resources/create b/gcloud/alpha/compute/queued-resources/create index 5c9bd358b..f46de81a9 100644 --- a/gcloud/alpha/compute/queued-resources/create +++ b/gcloud/alpha/compute/queued-resources/create @@ -586,8 +586,9 @@ OPTIONAL FLAGS --network-interface=[PROPERTY=VALUE,...] Adds a network interface to the instance. Mutually exclusive with any - of these flags: --network, --network-tier, --subnet. This flag can be - repeated to specify multiple network interfaces. + of these flags: --network, --network-tier, --no-address, --subnet, + --stack-type. This flag can be repeated to specify multiple network + interfaces. network Specifies the network that the interface will be part of. If subnet @@ -618,6 +619,11 @@ OPTIONAL FLAGS https://cloud.google.com/compute/docs/network-bandwidth#rx-tx for more details. + stack-type + Specifies whether IPv6 is enabled on the interface. STACK_TYPE must + be one of: IPV4_ONLY, IPV4_IPV6, IPV6_ONLY. The default value is + IPV4_ONLY. + --network-performance-configs=[PROPERTY=VALUE,...] Configures network performance settings for the instance. If this flag is not specified, the instance will be created with its default network diff --git a/gcloud/alpha/compute/service-attachments/create b/gcloud/alpha/compute/service-attachments/create index e3dc95db7..776e222d1 100644 --- a/gcloud/alpha/compute/service-attachments/create +++ b/gcloud/alpha/compute/service-attachments/create @@ -129,17 +129,19 @@ OPTIONAL FLAGS CLOUDSDK_COMPUTE_REGION. --propagated-connection-limit=PROPAGATED_CONNECTION_LIMIT - Per-consumer limit on the number of consumer Network Connectivity - Center spokes that Private Service Connect connectivity can be - propagated to. This flag lets a producer limit how many propagated - Private Service Connect connections can be established by a single - consumer to the producer's service attachment. + The number of consumer spokes that connected Private Service Connect + endpoints can be propagated to through Network Connectivity Center. + This limit lets the service producer limit how many propagated Private + Service Connect connections can be established to this service + attachment from a single consumer. - If the service attachment connection preference is set to - ACCEPT_AUTOMATIC or the accept and reject lists are project-based, then - this limit is scoped per consumer project. If the service attachment - accept and reject lists are network-based, then this limit is scoped to - the consumer network where the endpoint is deployed. + If the connection preference of the service attachment is + ACCEPT_MANUAL, the limit applies to each project or network that is + listed in the consumer accept list. If the connection preference of the + service attachment is ACCEPT_AUTOMATIC, the limit applies to each + project that contains a connected endpoint. + + If unspecified, the default propagated connection limit is 250. --reconcile-connections Determines whether to apply changes to consumer accept or reject lists diff --git a/gcloud/alpha/compute/service-attachments/update b/gcloud/alpha/compute/service-attachments/update index fe68d1449..c113c9812 100644 --- a/gcloud/alpha/compute/service-attachments/update +++ b/gcloud/alpha/compute/service-attachments/update @@ -95,17 +95,19 @@ FLAGS compute/region property value for this command invocation. --propagated-connection-limit=PROPAGATED_CONNECTION_LIMIT - Per-consumer limit on the number of consumer Network Connectivity - Center spokes that Private Service Connect connectivity can be - propagated to. This flag lets a producer limit how many propagated - Private Service Connect connections can be established by a single - consumer to the producer's service attachment. + The number of consumer spokes that connected Private Service Connect + endpoints can be propagated to through Network Connectivity Center. + This limit lets the service producer limit how many propagated Private + Service Connect connections can be established to this service + attachment from a single consumer. - If the service attachment connection preference is set to - ACCEPT_AUTOMATIC or the accept and reject lists are project-based, then - this limit is scoped per consumer project. If the service attachment - accept and reject lists are network-based, then this limit is scoped to - the consumer network where the endpoint is deployed. + If the connection preference of the service attachment is + ACCEPT_MANUAL, the limit applies to each project or network that is + listed in the consumer accept list. If the connection preference of the + service attachment is ACCEPT_AUTOMATIC, the limit applies to each + project that contains a connected endpoint. + + If unspecified, the default propagated connection limit is 250. --[no-]reconcile-connections Determines whether to apply changes to consumer accept or reject lists diff --git a/gcloud/alpha/compute/tpus/queued-resources/delete b/gcloud/alpha/compute/tpus/queued-resources/delete index 494def5aa..a48a5390c 100644 --- a/gcloud/alpha/compute/tpus/queued-resources/delete +++ b/gcloud/alpha/compute/tpus/queued-resources/delete @@ -15,11 +15,11 @@ DESCRIPTION $ gcloud alpha compute tpus queued-resources list EXAMPLES - To delete a Queued Resource in zone us-central1-b and project my-project, - run: + To delete a Queued Resource with ID my-queued-resource in zone + us-central1-b and project my-project, run: $ gcloud alpha compute tpus queued-resources delete \ - --zone=us-central1-b --project=my-project + my-queued-resource --zone=us-central1-b --project=my-project POSITIONAL ARGUMENTS Queued resource resource - The Queued Resource you want to delete. The diff --git a/gcloud/alpha/firestore/databases/create b/gcloud/alpha/firestore/databases/create index 8caceaafd..81d1956a6 100644 --- a/gcloud/alpha/firestore/databases/create +++ b/gcloud/alpha/firestore/databases/create @@ -5,8 +5,8 @@ NAME SYNOPSIS gcloud alpha firestore databases create --location=LOCATION [--database=DATABASE; default="(default)"] [--delete-protection] - [--enable-pitr] [--type=TYPE; default="firestore-native"] - [GCLOUD_WIDE_FLAG ...] + [--enable-pitr] [--kms-key-name=KMS_KEY_NAME] + [--type=TYPE; default="firestore-native"] [GCLOUD_WIDE_FLAG ...] EXAMPLES To create a Firestore Native database in nam5. @@ -71,6 +71,22 @@ OPTIONAL FLAGS If set to true, PITR on the new database will be enabled. By default, this feature is not enabled. + --kms-key-name=KMS_KEY_NAME + The resource ID of a Cloud KMS key. If set, the database created will + be a Customer-managed Encryption Key (CMEK) database encrypted with + this key. This feature is allowlist only in initial launch. + + Only the key in the same location as this database is allowed to be + used for encryption. + + For Firestore's nam5 multi-region, this corresponds to Cloud KMS + location us. For Firestore's eur3 multi-region, this corresponds to + Cloud KMS location europe. See https://cloud.google.com/kms/docs/locations. + + This value should be the KMS key resource ID in the format of + `projects/{project_id}/locations/{kms_location}/keyRings/{key_ring}/cryptoKeys/{crypto_key}`. + How to retrive this resource ID is listed at https://cloud.google.com/kms/docs/getting-resource-ids#getting_the_id_for_a_key_and_version. + --type=TYPE; default="firestore-native" The type of the database. TYPE must be one of: firestore-native, datastore-mode. diff --git a/gcloud/alpha/logging/sinks/create b/gcloud/alpha/logging/sinks/create index 969d6012c..a176642de 100644 --- a/gcloud/alpha/logging/sinks/create +++ b/gcloud/alpha/logging/sinks/create @@ -7,7 +7,8 @@ SYNOPSIS [--description=DESCRIPTION] [--disabled] [--exclusion=[description=DESCRIPTION], [disabled=DISABLED],[filter=FILTER],[name=NAME]] [--include-children] - [--log-filter=LOG_FILTER] [--use-partitioned-tables] + [--intercept-children] [--log-filter=LOG_FILTER] + [--use-partitioned-tables] [--billing-account=BILLING_ACCOUNT_ID | --folder=FOLDER_ID | --organization=ORGANIZATION_ID | --project=PROJECT_ID] [GCLOUD_WIDE_FLAG ...] @@ -113,6 +114,10 @@ FLAGS Whether to export logs from all child projects and folders. Only applies to sinks for organizations and folders. + --intercept-children + Whether to intercept logs from all child projects and folders. Only + applies to sinks for organizations and folders. + --log-filter=LOG_FILTER A filter expression for the sink. If present, the filter specifies which log entries to export. diff --git a/gcloud/alpha/logging/sinks/list b/gcloud/alpha/logging/sinks/list index e52a1aab2..510606bb6 100644 --- a/gcloud/alpha/logging/sinks/list +++ b/gcloud/alpha/logging/sinks/list @@ -2,7 +2,7 @@ NAME gcloud alpha logging sinks list - list the defined sinks SYNOPSIS - gcloud alpha logging sinks list + gcloud alpha logging sinks list [--sink-filter=SINK_FILTER] [--billing-account=BILLING_ACCOUNT_ID | --folder=FOLDER_ID | --organization=ORGANIZATION_ID | --project=PROJECT_ID] [--filter=EXPRESSION] [--limit=LIMIT] [--sort-by=[FIELD,...]] @@ -17,6 +17,11 @@ EXAMPLES $ gcloud alpha logging sinks list --limit=10 FLAGS + --sink-filter=SINK_FILTER + A filter expression passed to the Logging API to constrain the sinks + returned. For information on accepted values, see + https://cloud.google.com/logging/docs/reference/v2/rpc/google.logging.v2#listsinksrequest + At most one of these can be specified: --billing-account=BILLING_ACCOUNT_ID diff --git a/gcloud/alpha/logging/sinks/update b/gcloud/alpha/logging/sinks/update index fe2aeec9f..13c05faf5 100644 --- a/gcloud/alpha/logging/sinks/update +++ b/gcloud/alpha/logging/sinks/update @@ -6,7 +6,8 @@ SYNOPSIS [--add-exclusion=[description=DESCRIPTION], [disabled=DISABLED],[filter=FILTER],[name=NAME]] [--clear-exclusions] [--custom-writer-identity=SERVICE_ACCOUNT_EMAIL] - [--description=DESCRIPTION] [--disabled] [--log-filter=LOG_FILTER] + [--description=DESCRIPTION] [--disabled] [--include-children] + [--intercept-children] [--log-filter=LOG_FILTER] [--remove-exclusions=[EXCLUSION ID,...]] [--update-exclusion=[description=DESCRIPTION], [disabled=DISABLED],[filter=FILTER],[name=NAME]] @@ -79,6 +80,14 @@ FLAGS destination. Specify --no-disabled to enable a disabled sink. If this flag is not specified, the value will not be updated. + --include-children + Whether to export logs from all child projects and folders. Only + applies to sinks for organizations and folders. + + --intercept-children + Whether to intercept logs from all child projects and folders. Only + applies to sinks for organizations and folders. + --log-filter=LOG_FILTER A new filter expression for the sink. If omitted, the sink's existing filter (if any) is unchanged. diff --git a/gcloud/alpha/redis/clusters/create b/gcloud/alpha/redis/clusters/create index d31bbc603..8fa697529 100644 --- a/gcloud/alpha/redis/clusters/create +++ b/gcloud/alpha/redis/clusters/create @@ -4,8 +4,12 @@ NAME SYNOPSIS gcloud alpha redis clusters create (CLUSTER : --region=REGION) - --network=NETWORK --shard-count=SHARD_COUNT [--async] - [--auth-mode=AUTH_MODE] [--replica-count=REPLICA_COUNT] + --network=NETWORK --shard-count=SHARD_COUNT + [--aof-append-fsync=AOF_APPEND_FSYNC] [--async] [--auth-mode=AUTH_MODE] + [--persistence-mode=PERSISTENCE_MODE] + [--rdb-snapshot-period=RDB_SNAPSHOT_PERIOD] + [--rdb-snapshot-start-time=RDB_SNAPSHOT_START_TIME] + [--redis-config=[KEY=VALUE,...]] [--replica-count=REPLICA_COUNT] [--transit-encryption-mode=TRANSIT_ENCRYPTION_MODE] [--zone=ZONE] [--zone-distribution-mode=ZONE_DISTRIBUTION_MODE] [GCLOUD_WIDE_FLAG ...] @@ -84,6 +88,18 @@ REQUIRED FLAGS The shard count of the cluster. OPTIONAL FLAGS + --aof-append-fsync=AOF_APPEND_FSYNC + Fsync configuration. AOF_APPEND_FSYNC must be one of: + + always + Redis explicitly calls fsync for every write command. + + everysec + (default) Redis explicitly calls fsync every second. + + no + Redis will not explicitly call fsync. + --async Return immediately, without waiting for the operation in progress to complete. @@ -98,6 +114,42 @@ OPTIONAL FLAGS iam-auth IAM basic authorization is enabled for the cluster. + --persistence-mode=PERSISTENCE_MODE + Operation mode for persistence. PERSISTENCE_MODE must be one of: + + aof + AOF-based persistence + disabled + Persistence mode is disabled + rdb + RDB-based persistence + + --rdb-snapshot-period=RDB_SNAPSHOT_PERIOD + Attempted period between RDB snapshots. RDB_SNAPSHOT_PERIOD must be one + of: + + 12h + 12 hours + 1h + 1 hour + 24h + (default) 24 hours + 6h + 6 hours + + --rdb-snapshot-start-time=RDB_SNAPSHOT_START_TIME + Date and time of the first snapshot in the ISO 1801 format, and + alignment time for future snapshots. For example, 2024-01-01T01:00:00Z. + If not specified, the current time will be used. + + --redis-config=[KEY=VALUE,...] + A list of Redis config KEY=VALUE pairs to set on the Redis Cluster + according to http://redis.io/topics/config. Currently the supported + Redis configs are: + + maxmemory-clients, maxmemory, maxmemory-policy, notify-keyspace-events, + slowlog-log-slower-than, maxclients. + --replica-count=REPLICA_COUNT The replica count of each shard. diff --git a/gcloud/alpha/redis/clusters/update b/gcloud/alpha/redis/clusters/update index 5742dd1ee..4a611c2c1 100644 --- a/gcloud/alpha/redis/clusters/update +++ b/gcloud/alpha/redis/clusters/update @@ -3,8 +3,13 @@ NAME instance SYNOPSIS - gcloud alpha redis clusters update (CLUSTER : --region=REGION) [--async] - [--replica-count=REPLICA_COUNT] [--shard-count=SHARD_COUNT] + gcloud alpha redis clusters update (CLUSTER : --region=REGION) + [--aof-append-fsync=AOF_APPEND_FSYNC] [--async] + [--persistence-mode=PERSISTENCE_MODE] + [--rdb-snapshot-period=RDB_SNAPSHOT_PERIOD] + [--rdb-snapshot-start-time=RDB_SNAPSHOT_START_TIME] + [--remove-redis-config=[KEY,...]] [--replica-count=REPLICA_COUNT] + [--shard-count=SHARD_COUNT] [--update-redis-config=KEY=VALUE] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -56,16 +61,65 @@ POSITIONAL ARGUMENTS ▸ set the property redis/region. FLAGS + --aof-append-fsync=AOF_APPEND_FSYNC + Fsync configuration. AOF_APPEND_FSYNC must be one of: + + always + Redis explicitly calls fsync for every write command. + + everysec + (default) Redis explicitly calls fsync every second. + + no + Redis will not explicitly call fsync. + --async Return immediately, without waiting for the operation in progress to complete. + --persistence-mode=PERSISTENCE_MODE + Operation mode for persistence. PERSISTENCE_MODE must be one of: + + aof + AOF-based persistence + disabled + Persistence mode is disabled + rdb + RDB-based persistence + + --rdb-snapshot-period=RDB_SNAPSHOT_PERIOD + Attempted period between RDB snapshots. RDB_SNAPSHOT_PERIOD must be one + of: + + 12h + 12 hours + 1h + 1 hour + 24h + (default) 24 hours + 6h + 6 hours + + --rdb-snapshot-start-time=RDB_SNAPSHOT_START_TIME + Date and time of the first snapshot in the ISO 1801 format, and + alignment time for future snapshots. For example, 2024-01-01T01:00:00Z. + If not specified, the current time will be used. + + --remove-redis-config=[KEY,...] + A list of Redis Cluster config parameters to remove. Removing a + non-existent config parameter is silently ignored. + --replica-count=REPLICA_COUNT The replica count of each shard. --shard-count=SHARD_COUNT The shard count of the cluster. + --update-redis-config=KEY=VALUE + A list of Redis Cluster config KEY=VALUE pairs to update. If a config + parameter is already set, its value is modified; otherwise a new Redis + config parameter is added. + 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/spanner/operations/cancel b/gcloud/alpha/spanner/operations/cancel index 00df74d06..6cdb8b444 100644 --- a/gcloud/alpha/spanner/operations/cancel +++ b/gcloud/alpha/spanner/operations/cancel @@ -1,5 +1,6 @@ NAME gcloud alpha spanner operations cancel - cancel a Cloud Spanner operation + with ALPHA features SYNOPSIS gcloud alpha spanner operations cancel OPERATION-ID @@ -7,7 +8,7 @@ SYNOPSIS [--backup=BACKUP] [--database=DATABASE] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) Cancel a Cloud Spanner operation. + (ALPHA) Cancel a Cloud Spanner operation with ALPHA features. EXAMPLES To cancel an instance operation with ID auto_12345, run: @@ -25,6 +26,12 @@ EXAMPLES $ gcloud alpha spanner operations cancel _auto_12345 \ --instance=my-instance-id --backup=my-backup-id + To cancel a Cloud Spanner instance partition operation with ID auto_12345, + run: + + $ gcloud alpha spanner operations cancel auto_12345 \ + --instance=my-instance-id --instance-partition=my-partition-id + POSITIONAL ARGUMENTS OPERATION-ID ID of the operation diff --git a/gcloud/alpha/spanner/operations/help b/gcloud/alpha/spanner/operations/help index ca3db6391..5b40175d9 100644 --- a/gcloud/alpha/spanner/operations/help +++ b/gcloud/alpha/spanner/operations/help @@ -16,14 +16,13 @@ COMMANDS COMMAND is one of the following: cancel - (ALPHA) Cancel a Cloud Spanner operation. + (ALPHA) Cancel a Cloud Spanner operation with ALPHA features. describe (ALPHA) Describe a Cloud Spanner operation. list - (ALPHA) List the Cloud Spanner operations on the given instance or - database or instance configuration. + (ALPHA) List the Cloud Spanner operations with ALPHA features. NOTES This command is currently in alpha and might change without notice. If this diff --git a/gcloud/alpha/spanner/operations/list b/gcloud/alpha/spanner/operations/list index 3824156f0..c301dc1d6 100644 --- a/gcloud/alpha/spanner/operations/list +++ b/gcloud/alpha/spanner/operations/list @@ -1,6 +1,6 @@ NAME - gcloud alpha spanner operations list - list the Cloud Spanner operations on - the given instance or database or instance configuration + gcloud alpha spanner operations list - list the Cloud Spanner operations + with ALPHA features SYNOPSIS gcloud alpha spanner operations list @@ -10,8 +10,7 @@ SYNOPSIS [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) List the Cloud Spanner operations on the given instance or database - or instance configuration. + (ALPHA) List the Cloud Spanner operations with ALPHA features. EXAMPLES To list Cloud Spanner instance operations for an instance, run: @@ -44,6 +43,12 @@ EXAMPLES $ gcloud alpha spanner operations list --instance=my-instance-id \ --backup=my-backup-id --type=BACKUP + To list Cloud Spanner instance partition operations for an instance + partition, run: + + $ gcloud alpha spanner operations list --instance=my-instance-id \ + --instance-partition=my-partition-id --type=INSTANCE_PARTITION + REQUIRED FLAGS Exactly one of these must be specified: @@ -101,6 +106,12 @@ FLAGS INSTANCE_CONFIG_UPDATE Instance configuration update operations are returned for the given instance configuration (--instance-config). + INSTANCE_PARTITION + If only the instance is specified (--instance), returns all + instance partition operations associated with instance partitions + in the instance. When an instance partition is specified + (--instance-partition), only the instance partition operations for + the given instance partition are returned. LIST COMMAND FLAGS --filter=EXPRESSION diff --git a/gcloud/alpha/sql/instances/create b/gcloud/alpha/sql/instances/create index 152e7bf58..d158ff553 100644 --- a/gcloud/alpha/sql/instances/create +++ b/gcloud/alpha/sql/instances/create @@ -21,8 +21,8 @@ SYNOPSIS [--deny-maintenance-period-start-date=DENY_MAINTENANCE_PERIOD_START_DATE] [--deny-maintenance-period-time=DENY_MAINTENANCE_PERIOD_TIME] [--edition=EDITION] [--enable-bin-log] [--enable-data-cache] - [--enable-google-private-path] [--enable-password-policy] - [--enable-point-in-time-recovery] + [--[no-]enable-google-ml-integration] [--enable-google-private-path] + [--enable-password-policy] [--enable-point-in-time-recovery] [--failover-replica-name=FAILOVER_REPLICA_NAME] [--[no-]insights-config-query-insights-enabled] [--insights-config-query-plans-per-minute=INSIGHTS_CONFIG_QUERY_PLANS_PER_MINUTE] @@ -239,6 +239,11 @@ FLAGS Enable use of data cache for accelerated read performance. This flag is only available for Enterprise_Plus edition instances. + --[no-]enable-google-ml-integration + Enable Vertex AI integration for Google Cloud SQL. Currently, only + PostgreSQL is supported. Use --enable-google-ml-integration to enable + and --no-enable-google-ml-integration to disable. + --enable-google-private-path Enable a private path for Google Cloud services. This flag specifies whether the instance is accessible to internal Google Cloud services diff --git a/gcloud/alpha/sql/instances/patch b/gcloud/alpha/sql/instances/patch index df506621f..6496bdd04 100644 --- a/gcloud/alpha/sql/instances/patch +++ b/gcloud/alpha/sql/instances/patch @@ -18,6 +18,7 @@ SYNOPSIS [--deny-maintenance-period-time=DENY_MAINTENANCE_PERIOD_TIME] [--diff] [--edition=EDITION] [--[no-]enable-bin-log] [--enable-data-cache] [--[no-]enable-database-replication] + [--[no-]enable-google-ml-integration] [--[no-]enable-google-private-path] [--enable-password-policy] [--enable-point-in-time-recovery] [--follow-gae-app=FOLLOW_GAE_APP] [--[no-]insights-config-query-insights-enabled] @@ -183,6 +184,11 @@ FLAGS --enable-database-replication to enable and --no-enable-database-replication to disable. + --[no-]enable-google-ml-integration + Enable Vertex AI integration for Google Cloud SQL. Currently, only + PostgreSQL is supported. Use --enable-google-ml-integration to enable + and --no-enable-google-ml-integration to disable. + --[no-]enable-google-private-path Enable a private path for Google Cloud services. This flag specifies whether the instance is accessible to internal Google Cloud services diff --git a/gcloud/alpha/storage/managed-folders/add-iam-policy-binding b/gcloud/alpha/storage/managed-folders/add-iam-policy-binding index e5de6ccb7..f07c8d010 100644 --- a/gcloud/alpha/storage/managed-folders/add-iam-policy-binding +++ b/gcloud/alpha/storage/managed-folders/add-iam-policy-binding @@ -108,5 +108,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 storage managed-folders add-iam-policy-binding diff --git a/gcloud/alpha/storage/managed-folders/create b/gcloud/alpha/storage/managed-folders/create index 4f4eb6bcc..3c46d3ce8 100644 --- a/gcloud/alpha/storage/managed-folders/create +++ b/gcloud/alpha/storage/managed-folders/create @@ -37,5 +37,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 storage managed-folders create diff --git a/gcloud/alpha/storage/managed-folders/delete b/gcloud/alpha/storage/managed-folders/delete index 9bb186d7c..67c467fec 100644 --- a/gcloud/alpha/storage/managed-folders/delete +++ b/gcloud/alpha/storage/managed-folders/delete @@ -44,5 +44,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 storage managed-folders delete diff --git a/gcloud/alpha/storage/managed-folders/describe b/gcloud/alpha/storage/managed-folders/describe index 576b76664..213271ac7 100644 --- a/gcloud/alpha/storage/managed-folders/describe +++ b/gcloud/alpha/storage/managed-folders/describe @@ -42,5 +42,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 storage managed-folders describe diff --git a/gcloud/alpha/storage/managed-folders/get-iam-policy b/gcloud/alpha/storage/managed-folders/get-iam-policy index b41c230b3..cbbbaed7a 100644 --- a/gcloud/alpha/storage/managed-folders/get-iam-policy +++ b/gcloud/alpha/storage/managed-folders/get-iam-policy @@ -39,5 +39,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 storage managed-folders get-iam-policy diff --git a/gcloud/alpha/storage/managed-folders/help b/gcloud/alpha/storage/managed-folders/help index 9ca7c5f50..96642af87 100644 --- a/gcloud/alpha/storage/managed-folders/help +++ b/gcloud/alpha/storage/managed-folders/help @@ -43,5 +43,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 storage managed-folders diff --git a/gcloud/alpha/storage/managed-folders/list b/gcloud/alpha/storage/managed-folders/list index c5dc5fdb5..cef3be0f9 100644 --- a/gcloud/alpha/storage/managed-folders/list +++ b/gcloud/alpha/storage/managed-folders/list @@ -74,5 +74,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 storage managed-folders list diff --git a/gcloud/alpha/storage/managed-folders/remove-iam-policy-binding b/gcloud/alpha/storage/managed-folders/remove-iam-policy-binding index 14ea663c3..71a087fe9 100644 --- a/gcloud/alpha/storage/managed-folders/remove-iam-policy-binding +++ b/gcloud/alpha/storage/managed-folders/remove-iam-policy-binding @@ -103,5 +103,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 storage managed-folders remove-iam-policy-binding diff --git a/gcloud/alpha/storage/managed-folders/set-iam-policy b/gcloud/alpha/storage/managed-folders/set-iam-policy index 2402c81d4..65f770602 100644 --- a/gcloud/alpha/storage/managed-folders/set-iam-policy +++ b/gcloud/alpha/storage/managed-folders/set-iam-policy @@ -54,5 +54,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 storage managed-folders set-iam-policy diff --git a/gcloud/alpha/workstations/configs/create b/gcloud/alpha/workstations/configs/create index f85fcb0a9..13d203723 100644 --- a/gcloud/alpha/workstations/configs/create +++ b/gcloud/alpha/workstations/configs/create @@ -5,6 +5,7 @@ NAME SYNOPSIS gcloud alpha workstations configs create (CONFIG : --cluster=CLUSTER --region=REGION) [--async] + [--boost-config=[BOOST_CONFIG,...]] [--boot-disk-size=BOOT_DISK_SIZE; default=50] [--container-args=[CONTAINER_ARGS,...]] [--container-command=[CONTAINER_COMMAND,...]] @@ -104,6 +105,43 @@ FLAGS Return immediately, without waiting for the operation in progress to complete. + --boost-config=[BOOST_CONFIG,...] + Boost Configuration(s) that workstations running with this + configuration can boost up to. This includes id (required), + machine-type, accelerator-type, and accelerator-count. + + Example: + + $ gcloud alpha workstations configs create \ + --boost-config=id=boost1,machine-type=n1-standard-4,\ + accelerator-type=nvidia-tesla-t4,accelerator-count=1 + + Sets boost_config value. + + accelerator-count + Sets accelerator-count value. + + accelerator-type + Sets accelerator-type value. + + id + Required, Sets id value. + + machine-type + Sets machine-type value. + + Shorthand Example: + + --boost-config=accelerator-count=int,accelerator-type=string,id=string,machine-type=string + + JSON Example: + + --boost-config='{"accelerator-count": int, "accelerator-type": "string", "id": "string", "machine-type": "string"}' + + File Example: + + --boost-config=path_to_file.(yaml|json) + --boot-disk-size=BOOT_DISK_SIZE; default=50 Size of the boot disk in GB. @@ -281,6 +319,8 @@ FLAGS CLion codeoss Code OSS + codeoss-cuda + Code OSS + CUDA toolkit goland GoLand intellij diff --git a/gcloud/alpha/workstations/configs/update b/gcloud/alpha/workstations/configs/update index d80e56e3d..610c4c44b 100644 --- a/gcloud/alpha/workstations/configs/update +++ b/gcloud/alpha/workstations/configs/update @@ -5,7 +5,7 @@ NAME SYNOPSIS gcloud alpha workstations configs update (CONFIG : --cluster=CLUSTER --region=REGION) [--async] - [--boot-disk-size=BOOT_DISK_SIZE] + [--boost-config=[BOOST_CONFIG,...]] [--boot-disk-size=BOOT_DISK_SIZE] [--container-args=[CONTAINER_ARGS,...]] [--container-command=[CONTAINER_COMMAND,...]] [--container-env=[CONTAINER_ENV,...]] @@ -92,6 +92,43 @@ FLAGS Return immediately, without waiting for the operation in progress to complete. + --boost-config=[BOOST_CONFIG,...] + Boost Configuration(s) that workstations running with this + configuration can boost up to. This includes id (required), + machine-type, accelerator-type, and accelerator-count. + + Example: + + $ gcloud alpha workstations configs update \ + --boost-config=id=boost1,machine-type=n1-standard-4,\ + accelerator-type=nvidia-tesla-t4,accelerator-count=1 + + Sets boost_config value. + + accelerator-count + Sets accelerator-count value. + + accelerator-type + Sets accelerator-type value. + + id + Required, Sets id value. + + machine-type + Sets machine-type value. + + Shorthand Example: + + --boost-config=accelerator-count=int,accelerator-type=string,id=string,machine-type=string + + JSON Example: + + --boost-config='{"accelerator-count": int, "accelerator-type": "string", "id": "string", "machine-type": "string"}' + + File Example: + + --boost-config=path_to_file.(yaml|json) + --boot-disk-size=BOOT_DISK_SIZE Size of the boot disk in GB. @@ -230,6 +267,8 @@ FLAGS CLion codeoss Code OSS + codeoss-cuda + Code OSS + CUDA toolkit goland GoLand intellij diff --git a/gcloud/alpha/workstations/start b/gcloud/alpha/workstations/start index de4900a53..2c7edbcdc 100644 --- a/gcloud/alpha/workstations/start +++ b/gcloud/alpha/workstations/start @@ -4,7 +4,7 @@ NAME SYNOPSIS gcloud alpha workstations start (WORKSTATION : --cluster=CLUSTER --config=CONFIG --region=REGION) - [--async] [GCLOUD_WIDE_FLAG ...] + [--async] [--boost=BOOST] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Start a workstation. @@ -70,6 +70,13 @@ FLAGS Return immediately, without waiting for the operation in progress to complete. + --boost=BOOST + Id of a boost configuration to start a workstations with. + + Example: + + $ gcloud alpha workstations start --boost=boost1 + GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, diff --git a/gcloud/beta/ai/persistent-resources/create b/gcloud/beta/ai/persistent-resources/create index 90ee6ac98..51b5fff67 100644 --- a/gcloud/beta/ai/persistent-resources/create +++ b/gcloud/beta/ai/persistent-resources/create @@ -187,5 +187,8 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. NOTES - This command is currently in beta and might change without notice. + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha ai persistent-resources create diff --git a/gcloud/beta/ai/persistent-resources/delete b/gcloud/beta/ai/persistent-resources/delete index 3887d3735..300d9a5cd 100644 --- a/gcloud/beta/ai/persistent-resources/delete +++ b/gcloud/beta/ai/persistent-resources/delete @@ -60,5 +60,8 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. NOTES - This command is currently in beta and might change without notice. + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha ai persistent-resources delete diff --git a/gcloud/beta/ai/persistent-resources/describe b/gcloud/beta/ai/persistent-resources/describe index 1a937238e..419fd2157 100644 --- a/gcloud/beta/ai/persistent-resources/describe +++ b/gcloud/beta/ai/persistent-resources/describe @@ -56,5 +56,8 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. NOTES - This command is currently in beta and might change without notice. + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha ai persistent-resources describe diff --git a/gcloud/beta/ai/persistent-resources/help b/gcloud/beta/ai/persistent-resources/help index 8595c156d..88b8b3aca 100644 --- a/gcloud/beta/ai/persistent-resources/help +++ b/gcloud/beta/ai/persistent-resources/help @@ -30,5 +30,8 @@ COMMANDS (BETA) Lists the active persistent resources. NOTES - This command is currently in beta and might change without notice. + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha ai persistent-resources diff --git a/gcloud/beta/ai/persistent-resources/list b/gcloud/beta/ai/persistent-resources/list index 563d6727c..8d352e77f 100644 --- a/gcloud/beta/ai/persistent-resources/list +++ b/gcloud/beta/ai/persistent-resources/list @@ -77,5 +77,8 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. NOTES - This command is currently in beta and might change without notice. + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha ai persistent-resources list diff --git a/gcloud/beta/alloydb/clusters/create-secondary b/gcloud/beta/alloydb/clusters/create-secondary index 86f0e7c1b..4e9f6fa66 100644 --- a/gcloud/beta/alloydb/clusters/create-secondary +++ b/gcloud/beta/alloydb/clusters/create-secondary @@ -6,6 +6,10 @@ SYNOPSIS gcloud beta alloydb clusters create-secondary CLUSTER --primary-cluster=PRIMARY_CLUSTER --region=REGION [--allocated-ip-range-name=ALLOCATED_IP_RANGE_NAME] [--async] + [--continuous-backup-recovery-window-days=RECOVERY_PERIOD + --enable-continuous-backup + [--continuous-backup-encryption-key=CONTINUOUS_BACKUP_ENCRYPTION_KEY + : --continuous-backup-encryption-key-keyring=CONTINUOUS_BACKUP_ENCRYPTION_KEY_KEYRING --continuous-backup-encryption-key-location=CONTINUOUS_BACKUP_ENCRYPTION_KEY_LOCATION --continuous-backup-encryption-key-project=CONTINUOUS_BACKUP_ENCRYPTION_KEY_PROJECT]] [--kms-key=KMS_KEY : --kms-keyring=KMS_KEYRING --kms-location=KMS_LOCATION --kms-project=KMS_PROJECT] [GCLOUD_WIDE_FLAG ...] @@ -46,6 +50,60 @@ OPTIONAL FLAGS Return immediately, without waiting for the operation in progress to complete. + Continuous Backup configuration. If unspecified, continuous backups are + copied from the associated primary cluster. + + --continuous-backup-recovery-window-days=RECOVERY_PERIOD + Recovery window of the log files and backups saved to support + Continuous Backups. + + --enable-continuous-backup + Enables Continuous Backups on the cluster. + + Key resource - The Cloud KMS (Key Management Service) cryptokey that + will be used to protect the continuous backup. The 'AlloyDB Service + Agent's service account must hold permission 'Cloud KMS CryptoKey + Encrypter/Decrypter'. The arguments in this group can be used to specify + the attributes of this resource. + + --continuous-backup-encryption-key=CONTINUOUS_BACKUP_ENCRYPTION_KEY + ID of the key or fully qualified identifier for the key. + + To set the kms-key attribute: + ▫ provide the argument --continuous-backup-encryption-key on the + command line. + + This flag argument must be specified if any of the other arguments + in this group are specified. + + --continuous-backup-encryption-key-keyring=CONTINUOUS_BACKUP_ENCRYPTION_KEY_KEYRING + The KMS keyring of the key. + + To set the kms-keyring attribute: + ▫ provide the argument --continuous-backup-encryption-key on the + command line with a fully specified name; + ▫ provide the argument --continuous-backup-encryption-key-keyring + on the command line. + + --continuous-backup-encryption-key-location=CONTINUOUS_BACKUP_ENCRYPTION_KEY_LOCATION + The Google Cloud location for the key. + + To set the kms-location attribute: + ▫ provide the argument --continuous-backup-encryption-key on the + command line with a fully specified name; + ▫ provide the argument + --continuous-backup-encryption-key-location on the command line. + + --continuous-backup-encryption-key-project=CONTINUOUS_BACKUP_ENCRYPTION_KEY_PROJECT + The Google Cloud project for the key. + + To set the kms-project attribute: + ▫ provide the argument --continuous-backup-encryption-key on the + command line with a fully specified name; + ▫ provide the argument --continuous-backup-encryption-key-project + on the command line; + ▫ set the property core/project. + Key resource - The Cloud KMS (Key Management Service) cryptokey that will be used to protect the cluster. The 'AlloyDB Service Agent' service account must hold permission 'Cloud KMS CryptoKey Encrypter/Decrypter'. diff --git a/gcloud/beta/bigtable/authorized-views/add-iam-policy-binding b/gcloud/beta/bigtable/authorized-views/add-iam-policy-binding new file mode 100644 index 000000000..07ea8eddd --- /dev/null +++ b/gcloud/beta/bigtable/authorized-views/add-iam-policy-binding @@ -0,0 +1,159 @@ +NAME + gcloud beta bigtable authorized-views add-iam-policy-binding - add an IAM + policy binding to a Cloud Bigtable authorized view + +SYNOPSIS + gcloud beta bigtable authorized-views add-iam-policy-binding + (AUTHORIZED_VIEW : --instance=INSTANCE --table=TABLE) + --member=PRINCIPAL --role=ROLE + [--condition=[KEY=VALUE,...] + | --condition-from-file=CONDITION_FROM_FILE] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Add an IAM policy binding to a Cloud Bigtable authorized view. One + binding consists of a member, a role, and an optional condition. + +EXAMPLES + To add an IAM policy binding for the role of 'roles/editor' for the user + 'test-user@gmail.com' with authorized view 'my-authorized-view' in instance + 'my-instance' and table 'my-table', run: + + $ gcloud beta bigtable authorized-views add-iam-policy-binding \ + my-authorized-view --instance='my-instance' --table='my-table' \ + --member='user:test-user@gmail.com' --role='roles/editor' + + To add an IAM policy binding which expires at the end of the year 2020 for + the role of 'roles/bigtable.admin' and the user 'test-user@gmail.com' with + authorized view 'my-authorized-view' in instance 'my-instance' and table + 'my-table', run: + + $ gcloud beta bigtable authorized-views add-iam-policy-binding \ + my-authorized-view --instance='my-instance' --table='my-table' \ + --member='user:test-user@gmail.com' \ + --role='roles/bigtable.admin' \ + --condition='expression=request.time < + timestamp("2021-01-01T00:00:00Z"),title=expires_end_of_2020,descrip\ + tion=Expires at midnight on 2020-12-31' + + See https://cloud.google.com/iam/docs/managing-policies for details of + policy role and member types. + +POSITIONAL ARGUMENTS + Authorized view resource - Cloud Bigtable authorized view to add the IAM + policy binding to. 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 authorized_view 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. + + AUTHORIZED_VIEW + ID of the authorized-view or fully qualified identifier for the + authorized-view. + + To set the authorized_view attribute: + ▸ provide the argument authorized_view on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --instance=INSTANCE + Name of the Cloud Bigtable instance. + + To set the instance attribute: + ▸ provide the argument authorized_view on the command line with a + fully specified name; + ▸ provide the argument --instance on the command line. + + --table=TABLE + Name of the Cloud Bigtable table. + + To set the table attribute: + ▸ provide the argument authorized_view on the command line with a + fully specified name; + ▸ provide the argument --table on the command line. + +REQUIRED FLAGS + --member=PRINCIPAL + The principal to add the binding for. Should be of the form + user|group|serviceAccount:email or domain:domain. + + Examples: user:test-user@gmail.com, group:admins@example.com, + serviceAccount:test123@example.domain.com, or + domain:example.domain.com. + + Some resources also accept the following special values: + ◆ allUsers - Special identifier that represents anyone who is on the + internet, with or without a Google account. + ◆ allAuthenticatedUsers - Special identifier that represents anyone + who is authenticated with a Google account or a service account. + + --role=ROLE + Role name to assign to the principal. The role name is the complete + path of a predefined role, such as roles/logging.viewer, or the role ID + for a custom role, such as + organizations/{ORGANIZATION_ID}/roles/logging.viewer. + +OPTIONAL FLAGS + At most one of these can be specified: + + --condition=[KEY=VALUE,...] + A condition to include in the binding. When the condition is + explicitly specified as None (--condition=None), a binding without a + condition is added. When the condition is specified and is not None, + --role cannot be a basic role. Basic roles are roles/editor, + roles/owner, and roles/viewer. For more on conditions, refer to the + conditions overview guide: + https://cloud.google.com/iam/docs/conditions-overview + + When using the --condition flag, include the following key-value + pairs: + + expression + (Required) Condition expression that evaluates to True or False. + This uses a subset of Common Expression Language syntax. + + If the condition expression includes a comma, use a different + delimiter to separate the key-value pairs. Specify the delimiter + before listing the key-value pairs. For example, to specify a + colon (:) as the delimiter, do the following: + --condition=^:^title=TITLE:expression=EXPRESSION. For more + information, see + https://cloud.google.com/sdk/gcloud/reference/topic/escaping. + + title + (Required) A short string describing the purpose of the + expression. + + description + (Optional) Additional description for the expression. + + --condition-from-file=CONDITION_FROM_FILE + Path to a local JSON or YAML file that defines the condition. To see + available fields, see the help for --condition. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the bigtableadmin/v2 API. The full documentation for this + API can be found at: https://cloud.google.com/bigtable/ + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud bigtable authorized-views add-iam-policy-binding + + $ gcloud alpha bigtable authorized-views add-iam-policy-binding + diff --git a/gcloud/beta/bigtable/authorized-views/create b/gcloud/beta/bigtable/authorized-views/create new file mode 100644 index 000000000..10d04705f --- /dev/null +++ b/gcloud/beta/bigtable/authorized-views/create @@ -0,0 +1,113 @@ +NAME + gcloud beta bigtable authorized-views create - create a new Cloud Bigtable + authorized view + +SYNOPSIS + gcloud beta bigtable authorized-views create + (AUTHORIZED_VIEW : --instance=INSTANCE --table=TABLE) [--async] + [--definition-file=DEFINITION_FILE] [--pre-encoded] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Create a new Cloud Bigtable authorized view. + +EXAMPLES + To create an authorized view 'my-authorized-view' in instance 'my-instance' + and table 'my-table', using the definition file 'authorized_view.json': + + $ gcloud beta bigtable authorized-views create my-authorized-view \ + --instance=test-instance --table=test-table \ + --definition-file=authorized_view.json + + To create an authorized view 'my-authorized-view' in instance 'my-instance' + and table 'my-table', using the pre-encoded definition file + 'authorized_view_pre_encoded.json': + + $ gcloud beta bigtable authorized-views create my-authorized-view \ + --instance=test-instance --table=test-table \ + --definition-file=authorized_view_pre_encoded.json --pre-encoded + +POSITIONAL ARGUMENTS + Authorized view resource - Cloud Bigtable authorized view to create. 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 authorized_view 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. + + AUTHORIZED_VIEW + ID of the authorized-view or fully qualified identifier for the + authorized-view. + + To set the authorized_view attribute: + ▸ provide the argument authorized_view on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --instance=INSTANCE + Name of the Cloud Bigtable instance. + + To set the instance attribute: + ▸ provide the argument authorized_view on the command line with a + fully specified name; + ▸ provide the argument --instance on the command line. + + --table=TABLE + Name of the Cloud Bigtable table. + + To set the table attribute: + ▸ provide the argument authorized_view on the command line with a + fully specified name; + ▸ provide the argument --table on the command line. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --definition-file=DEFINITION_FILE + Path to a JSON or YAML file containing a valid authorized view + protobuf. + + The 'name' field is ignored. The name is deduced from the other command + line arguments. + + Example: { "subsetView": { "rowPrefixes": ["store1#"], "familySubsets": + { "column_family_name": { "qualifiers":["address"], + "qualifierPrefixes":["tel"] } } }, "deletionProtection": true } + + --pre-encoded + By default, Base64 encoding is applied to all binary fields + ("rowPrefixes", "qualifiers" and "qualifierPrefixes") in the JSON or + YAML definition file. + + Use this to indicate that all binary fields are already Base64-encoded + and should be used directly. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the bigtableadmin/v2 API. The full documentation for this + API can be found at: https://cloud.google.com/bigtable/ + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud bigtable authorized-views create + + $ gcloud alpha bigtable authorized-views create + diff --git a/gcloud/beta/bigtable/authorized-views/delete b/gcloud/beta/bigtable/authorized-views/delete new file mode 100644 index 000000000..a55b1c983 --- /dev/null +++ b/gcloud/beta/bigtable/authorized-views/delete @@ -0,0 +1,79 @@ +NAME + gcloud beta bigtable authorized-views delete - delete a Cloud Bigtable + authorized view + +SYNOPSIS + gcloud beta bigtable authorized-views delete + (AUTHORIZED_VIEW : --instance=INSTANCE --table=TABLE) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Delete new Cloud Bigtable authorized view. + +EXAMPLES + To delete the authorized view 'my-authorized-view' in instance + 'my-instance' and table 'my-table': + + $ gcloud beta bigtable authorized-views delete my-authorized-view \ + --instance=test-instance --table=test-table + +POSITIONAL ARGUMENTS + Authorized view resource - Cloud Bigtable authorized view to delete. 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 authorized_view 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. + + AUTHORIZED_VIEW + ID of the authorized-view or fully qualified identifier for the + authorized-view. + + To set the authorized_view attribute: + ▸ provide the argument authorized_view on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --instance=INSTANCE + Name of the Cloud Bigtable instance. + + To set the instance attribute: + ▸ provide the argument authorized_view on the command line with a + fully specified name; + ▸ provide the argument --instance on the command line. + + --table=TABLE + Name of the Cloud Bigtable table. + + To set the table attribute: + ▸ provide the argument authorized_view on the command line with a + fully specified name; + ▸ provide the argument --table on the command line. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the bigtableadmin/v2 API. The full documentation for this + API can be found at: https://cloud.google.com/bigtable/ + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud bigtable authorized-views delete + + $ gcloud alpha bigtable authorized-views delete + diff --git a/gcloud/beta/bigtable/authorized-views/describe b/gcloud/beta/bigtable/authorized-views/describe new file mode 100644 index 000000000..4c8a7827b --- /dev/null +++ b/gcloud/beta/bigtable/authorized-views/describe @@ -0,0 +1,79 @@ +NAME + gcloud beta bigtable authorized-views describe - describe a Cloud Bigtable + authorized view + +SYNOPSIS + gcloud beta bigtable authorized-views describe + (AUTHORIZED_VIEW : --instance=INSTANCE --table=TABLE) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Describe a Cloud Bigtable authorized view. + +EXAMPLES + To describe the authorized view 'my-authorized-view' in instance + 'my-instance' and table 'my-table': + + $ gcloud beta bigtable authorized-views describe \ + my-authorized-view --instance=test-instance --table=test-table + +POSITIONAL ARGUMENTS + Authorized view resource - Cloud Bigtable authorized view to describe. 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 authorized_view 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. + + AUTHORIZED_VIEW + ID of the authorized-view or fully qualified identifier for the + authorized-view. + + To set the authorized_view attribute: + ▸ provide the argument authorized_view on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --instance=INSTANCE + Name of the Cloud Bigtable instance. + + To set the instance attribute: + ▸ provide the argument authorized_view on the command line with a + fully specified name; + ▸ provide the argument --instance on the command line. + + --table=TABLE + Name of the Cloud Bigtable table. + + To set the table attribute: + ▸ provide the argument authorized_view on the command line with a + fully specified name; + ▸ provide the argument --table on the command line. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the bigtableadmin/v2 API. The full documentation for this + API can be found at: https://cloud.google.com/bigtable/ + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud bigtable authorized-views describe + + $ gcloud alpha bigtable authorized-views describe + diff --git a/gcloud/beta/bigtable/authorized-views/get-iam-policy b/gcloud/beta/bigtable/authorized-views/get-iam-policy new file mode 100644 index 000000000..b164314c0 --- /dev/null +++ b/gcloud/beta/bigtable/authorized-views/get-iam-policy @@ -0,0 +1,109 @@ +NAME + gcloud beta bigtable authorized-views get-iam-policy - get an IAM policy on + a Cloud Bigtable authorized view + +SYNOPSIS + gcloud beta bigtable authorized-views get-iam-policy + (AUTHORIZED_VIEW : --instance=INSTANCE --table=TABLE) + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Get an IAM policy on a Cloud Bigtable authorized view. + +EXAMPLES + To get the IAM policy on the authorized view 'my-authorized-view' in + instance 'my-instance' and table 'my-table', run: + + $ gcloud beta bigtable authorized-views get-iam-policy \ + my-authorized-view --instance='my-instance' --table='my-table' + + See https://cloud.google.com/iam/docs/managing-policies for more + information. + +POSITIONAL ARGUMENTS + Authorized view resource - Cloud Bigtable authorized view to get the IAM + policy for. 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 authorized_view 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. + + AUTHORIZED_VIEW + ID of the authorized-view or fully qualified identifier for the + authorized-view. + + To set the authorized_view attribute: + ▸ provide the argument authorized_view on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --instance=INSTANCE + Name of the Cloud Bigtable instance. + + To set the instance attribute: + ▸ provide the argument authorized_view on the command line with a + fully specified name; + ▸ provide the argument --instance on the command line. + + --table=TABLE + Name of the Cloud Bigtable table. + + To set the table attribute: + ▸ provide the argument authorized_view on the command line with a + fully specified name; + ▸ provide the argument --table on the command line. + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the bigtableadmin/v2 API. The full documentation for this + API can be found at: https://cloud.google.com/bigtable/ + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud bigtable authorized-views get-iam-policy + + $ gcloud alpha bigtable authorized-views get-iam-policy + diff --git a/gcloud/beta/bigtable/authorized-views/help b/gcloud/beta/bigtable/authorized-views/help new file mode 100644 index 000000000..0d8322c31 --- /dev/null +++ b/gcloud/beta/bigtable/authorized-views/help @@ -0,0 +1,54 @@ +NAME + gcloud beta bigtable authorized-views - manage Cloud Bigtable Authorized + Views + +SYNOPSIS + gcloud beta bigtable authorized-views COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Manage Cloud Bigtable Authorized Views. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + add-iam-policy-binding + (BETA) Add an IAM policy binding to a Cloud Bigtable authorized view. + + create + (BETA) Create a new Cloud Bigtable authorized view. + + delete + (BETA) Delete a Cloud Bigtable authorized view. + + describe + (BETA) Describe a Cloud Bigtable authorized view. + + get-iam-policy + (BETA) Get an IAM policy on a Cloud Bigtable authorized view. + + list + (BETA) List all authorized views of a Cloud Bigtable table. + + remove-iam-policy-binding + (BETA) Remove an IAM policy binding from a Cloud Bigtable authorized + view. + + set-iam-policy + (BETA) Set an IAM policy on a Cloud Bigtable authorized view. + + update + (BETA) Update an existing Cloud Bigtable authorized view. + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud bigtable authorized-views + + $ gcloud alpha bigtable authorized-views + diff --git a/gcloud/beta/bigtable/authorized-views/list b/gcloud/beta/bigtable/authorized-views/list new file mode 100644 index 000000000..e46b50c0e --- /dev/null +++ b/gcloud/beta/bigtable/authorized-views/list @@ -0,0 +1,103 @@ +NAME + gcloud beta bigtable authorized-views list - list all authorized views of a + Cloud Bigtable table + +SYNOPSIS + gcloud beta bigtable authorized-views list + (--table=TABLE : --instance=INSTANCE) [--filter=EXPRESSION] + [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) List all authorized views of a Cloud Bigtable table. + +EXAMPLES + To list the authorized views in instance 'my-instance' and table + 'my-table': + + $ gcloud beta bigtable authorized-views list \ + --instance=test-instance --table=test-table + +REQUIRED FLAGS + Table resource - Cloud Bigtable table for which to list all authorized + views. 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 --table 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. + + --table=TABLE + ID of the table or fully qualified identifier for the table. + + To set the table attribute: + ▸ provide the argument --table on the command line. + + This flag argument must be specified if any of the other arguments in + this group are specified. + + --instance=INSTANCE + Name of the Cloud Bigtable instance. + + To set the instance attribute: + ▸ provide the argument --table on the command line with a fully + specified name; + ▸ provide the argument --instance on the command line. + +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. + +API REFERENCE + This command uses the bigtableadmin/v2 API. The full documentation for this + API can be found at: https://cloud.google.com/bigtable/ + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud bigtable authorized-views list + + $ gcloud alpha bigtable authorized-views list + diff --git a/gcloud/beta/bigtable/authorized-views/remove-iam-policy-binding b/gcloud/beta/bigtable/authorized-views/remove-iam-policy-binding new file mode 100644 index 000000000..8dec173c2 --- /dev/null +++ b/gcloud/beta/bigtable/authorized-views/remove-iam-policy-binding @@ -0,0 +1,164 @@ +NAME + gcloud beta bigtable authorized-views remove-iam-policy-binding - remove an + IAM policy binding from a Cloud Bigtable authorized view + +SYNOPSIS + gcloud beta bigtable authorized-views remove-iam-policy-binding + (AUTHORIZED_VIEW : --instance=INSTANCE --table=TABLE) + --member=PRINCIPAL --role=ROLE + [--all | --condition=[KEY=VALUE,...] + | --condition-from-file=CONDITION_FROM_FILE] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Remove an IAM policy binding from a Cloud Bigtable authorized view. + One binding consists of a member, a role, and an optional condition. + +EXAMPLES + To remove an IAM policy binding for the role of 'roles/editor' for the user + 'test-user@gmail.com' with authorized view 'my-authorized-view' in instance + 'my-instance' and table 'my-table', run: + + $ gcloud beta bigtable authorized-views remove-iam-policy-binding \ + my-authorized-view --instance='my-instance' --table='my-table' \ + --member='user:test-user@gmail.com' --role='roles/editor' + + To remove an IAM policy binding which expires at the end of the year 2020 + for the role of 'roles/bigtable.admin' and the user 'test-user@gmail.com' + with authorized view 'my-authorized-view' in instance 'my-instance' and + cluster 'my-cluster', run: + + $ gcloud beta bigtable authorized-views remove-iam-policy-binding \ + my-authorized-view --instance='my-instance' --table='my-table' \ + --member='user:test-user@gmail.com' \ + --role='roles/bigtable.admin' \ + --condition='expression=request.time < + timestamp("2021-01-01T00:00:00Z"),title=expires_end_of_2020,descrip\ + tion=Expires at midnight on 2020-12-31' + + See https://cloud.google.com/iam/docs/managing-policies for details of + policy role and member types. + +POSITIONAL ARGUMENTS + Authorized view resource - Cloud Bigtable authorized view to remove the + IAM policy binding from. The arguments in this group can be used to + specify the attributes of this resource. (NOTE) Some attributes are not + given arguments in this group but can be set in other ways. + + To set the project attribute: + ◆ provide the argument authorized_view 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. + + AUTHORIZED_VIEW + ID of the authorized-view or fully qualified identifier for the + authorized-view. + + To set the authorized_view attribute: + ▸ provide the argument authorized_view on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --instance=INSTANCE + Name of the Cloud Bigtable instance. + + To set the instance attribute: + ▸ provide the argument authorized_view on the command line with a + fully specified name; + ▸ provide the argument --instance on the command line. + + --table=TABLE + Name of the Cloud Bigtable table. + + To set the table attribute: + ▸ provide the argument authorized_view on the command line with a + fully specified name; + ▸ provide the argument --table on the command line. + +REQUIRED FLAGS + --member=PRINCIPAL + The principal to remove the binding for. Should be of the form + user|group|serviceAccount:email or domain:domain. + + Examples: user:test-user@gmail.com, group:admins@example.com, + serviceAccount:test123@example.domain.com, or + domain:example.domain.com. + + Deleted principals have an additional deleted: prefix and a ?uid=UID + suffix, where UID is a unique identifier for the principal. Example: + deleted:user:test-user@gmail.com?uid=123456789012345678901. + + Some resources also accept the following special values: + ◆ allUsers - Special identifier that represents anyone who is on the + internet, with or without a Google account. + ◆ allAuthenticatedUsers - Special identifier that represents anyone + who is authenticated with a Google account or a service account. + + --role=ROLE + The role to remove the principal from. + +OPTIONAL FLAGS + At most one of these can be specified: + + --all + Remove all bindings with this role and principal, irrespective of any + conditions. + + --condition=[KEY=VALUE,...] + The condition of the binding that you want to remove. When the + condition is explicitly specified as None (--condition=None), a + binding without a condition is removed. Otherwise, only a binding + with a condition that exactly matches the specified condition + (including the optional description) is removed. For more on + conditions, refer to the conditions overview guide: + https://cloud.google.com/iam/docs/conditions-overview + + When using the --condition flag, include the following key-value + pairs: + + expression + (Required) Condition expression that evaluates to True or False. + This uses a subset of Common Expression Language syntax. + + If the condition expression includes a comma, use a different + delimiter to separate the key-value pairs. Specify the delimiter + before listing the key-value pairs. For example, to specify a + colon (:) as the delimiter, do the following: + --condition=^:^title=TITLE:expression=EXPRESSION. For more + information, see + https://cloud.google.com/sdk/gcloud/reference/topic/escaping. + + title + (Required) A short string describing the purpose of the + expression. + + description + (Optional) Additional description for the expression. + + --condition-from-file=CONDITION_FROM_FILE + Path to a local JSON or YAML file that defines the condition. To see + available fields, see the help for --condition. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the bigtableadmin/v2 API. The full documentation for this + API can be found at: https://cloud.google.com/bigtable/ + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud bigtable authorized-views remove-iam-policy-binding + + $ gcloud alpha bigtable authorized-views remove-iam-policy-binding + diff --git a/gcloud/beta/bigtable/authorized-views/set-iam-policy b/gcloud/beta/bigtable/authorized-views/set-iam-policy new file mode 100644 index 000000000..f977663de --- /dev/null +++ b/gcloud/beta/bigtable/authorized-views/set-iam-policy @@ -0,0 +1,90 @@ +NAME + gcloud beta bigtable authorized-views set-iam-policy - set an IAM policy on + a Cloud Bigtable authorized view + +SYNOPSIS + gcloud beta bigtable authorized-views set-iam-policy + (AUTHORIZED_VIEW : --instance=INSTANCE --table=TABLE) POLICY_FILE + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Set an IAM policy on a Cloud Bigtable authorized view. + +EXAMPLES + To set the IAM policy from file 'my-policy' on the authorized view + 'my-authorized-view' in instance 'my-instance' and table 'my-table', run: + + $ gcloud beta bigtable authorized-views set-iam-policy \ + my-authorized-view --instance='my-instance' --table='my-table' \ + my-policy + + See https://cloud.google.com/iam/docs/managing-policies for more + information. + +POSITIONAL ARGUMENTS + Authorized view resource - Cloud Bigtable authorized view to set the IAM + policy 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 authorized_view 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. + + AUTHORIZED_VIEW + ID of the authorized-view or fully qualified identifier for the + authorized-view. + + To set the authorized_view attribute: + ▸ provide the argument authorized_view on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --instance=INSTANCE + Name of the Cloud Bigtable instance. + + To set the instance attribute: + ▸ provide the argument authorized_view on the command line with a + fully specified name; + ▸ provide the argument --instance on the command line. + + --table=TABLE + Name of the Cloud Bigtable table. + + To set the table attribute: + ▸ provide the argument authorized_view on the command line with a + fully specified name; + ▸ provide the argument --table on the command line. + + POLICY_FILE + Path to a local JSON or YAML formatted file containing a valid policy. + + The output of the get-iam-policy command is a valid file, as is any + JSON or YAML file conforming to the structure of a Policy + (https://cloud.google.com/iam/reference/rest/v1/Policy). + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the bigtableadmin/v2 API. The full documentation for this + API can be found at: https://cloud.google.com/bigtable/ + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud bigtable authorized-views set-iam-policy + + $ gcloud alpha bigtable authorized-views set-iam-policy + diff --git a/gcloud/beta/bigtable/authorized-views/update b/gcloud/beta/bigtable/authorized-views/update new file mode 100644 index 000000000..f4d228a43 --- /dev/null +++ b/gcloud/beta/bigtable/authorized-views/update @@ -0,0 +1,130 @@ +NAME + gcloud beta bigtable authorized-views update - update an existing Cloud + Bigtable authorized view + +SYNOPSIS + gcloud beta bigtable authorized-views update + (AUTHORIZED_VIEW : --instance=INSTANCE --table=TABLE) [--async] + [--definition-file=DEFINITION_FILE] [--ignore-warnings] + [--no-interactive] [--pre-encoded] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Update an existing Cloud Bigtable authorized view. + +EXAMPLES + To update the authorized view 'my-authorized-view' in instance + 'my-instance' and table 'my-table', using the definition file + 'authorized_view.json': + + $ gcloud beta bigtable authorized-views update my-authorized-view \ + --instance=test-instance --table=test-table \ + --definition-file=authorized_view.json + + To update the authorized view 'my-authorized-view' in instance + 'my-instance' and table 'my-table', using the pre-encoded definition file + 'authorized_view_pre_encoded.json': + + $ gcloud beta bigtable authorized-views update my-authorized-view \ + --instance=test-instance --table=test-table \ + --definition-file=authorized_view_pre_encoded.json --pre-encoded + + To update the authorized view 'my-authorized-view' in instance + 'my-instance' and table 'my-table', using the definition file + 'authorized_view.json' and skip the prompt to proceed or cancel the update: + + $ gcloud beta bigtable authorized-views update my-authorized-view \ + --instance=test-instance --table=test-table \ + --definition-file=authorized_view.json --no-interactive + +POSITIONAL ARGUMENTS + Authorized view resource - Cloud Bigtable authorized view to update. 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 authorized_view 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. + + AUTHORIZED_VIEW + ID of the authorized-view or fully qualified identifier for the + authorized-view. + + To set the authorized_view attribute: + ▸ provide the argument authorized_view on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --instance=INSTANCE + Name of the Cloud Bigtable instance. + + To set the instance attribute: + ▸ provide the argument authorized_view on the command line with a + fully specified name; + ▸ provide the argument --instance on the command line. + + --table=TABLE + Name of the Cloud Bigtable table. + + To set the table attribute: + ▸ provide the argument authorized_view on the command line with a + fully specified name; + ▸ provide the argument --table on the command line. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --definition-file=DEFINITION_FILE + Path to a JSON or YAML file containing a valid authorized view + protobuf. + + The 'name' field is ignored. The name is deduced from the other command + line arguments. + + Example: { "subsetView": { "rowPrefixes": ["store1"], "familySubsets": + { "column_family_name": { "qualifiers":["address"], + "qualifierPrefixes":["tel"] } } }, "deletionProtection": true } + + --ignore-warnings + If true, changes that make the authorized view more restrictive are + allowed. + + --interactive + If provided, a diff is displayed with a prompt to proceed or cancel the + update. Enabled by default, use --no-interactive to disable. + + --pre-encoded + By default, Base64 encoding is applied to all binary fields + ("rowPrefixes", "qualifiers" and "qualifierPrefixes") in the JSON or + YAML definition file. + + Use this to indicate that all binary fields are already Base64-encoded + and should be used directly. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the bigtableadmin/v2 API. The full documentation for this + API can be found at: https://cloud.google.com/bigtable/ + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud bigtable authorized-views update + + $ gcloud alpha bigtable authorized-views update + diff --git a/gcloud/beta/bigtable/help b/gcloud/beta/bigtable/help index a51504ef1..285341f63 100644 --- a/gcloud/beta/bigtable/help +++ b/gcloud/beta/bigtable/help @@ -18,6 +18,9 @@ GROUPS app-profiles (BETA) Manage Cloud Bigtable app profiles. + authorized-views + (BETA) Manage Cloud Bigtable Authorized Views. + backups (BETA) Manage Cloud Bigtable backups. diff --git a/gcloud/beta/builds/submit b/gcloud/beta/builds/submit index fd7e7203f..ce1396902 100644 --- a/gcloud/beta/builds/submit +++ b/gcloud/beta/builds/submit @@ -9,8 +9,8 @@ SYNOPSIS [--git-source-dir=GIT_SOURCE_DIR] [--git-source-revision=GIT_SOURCE_REVISION] [--ignore-file=IGNORE_FILE] [--machine-type=MACHINE_TYPE] [--region=REGION] [--revision=REVISION] - [--substitutions=[KEY=VALUE,...]] [--suppress-logs] [--timeout=TIMEOUT] - [--worker-pool=WORKER_POOL] + [--service-account=SERVICE_ACCOUNT] [--substitutions=[KEY=VALUE,...]] + [--suppress-logs] [--timeout=TIMEOUT] [--worker-pool=WORKER_POOL] [--config=CONFIG; default="cloudbuild.yaml" | --pack=[builder=BUILDER],[env=ENV],[image=IMAGE] | --tag=TAG, -t TAG] [GCLOUD_WIDE_FLAG ...] @@ -161,6 +161,10 @@ FLAGS https://git-scm.com/docs/gitrevisions#_specifying_revisions. For information on git fetch, see https://git-scm.com/docs/git-fetch. + --service-account=SERVICE_ACCOUNT + The service account to use with this build. If unset, the default + service account will be used. + --substitutions=[KEY=VALUE,...] Parameters to be substituted in the build specification. diff --git a/gcloud/beta/composer/environments/create b/gcloud/beta/composer/environments/create index 42c065e29..f78c13f47 100644 --- a/gcloud/beta/composer/environments/create +++ b/gcloud/beta/composer/environments/create @@ -7,13 +7,15 @@ SYNOPSIS (ENVIRONMENT : --location=LOCATION) [--airflow-configs=[KEY=VALUE,...]] [--async] [--cloud-sql-machine-type=CLOUD_SQL_MACHINE_TYPE] [--cloud-sql-preferred-zone=CLOUD_SQL_PREFERRED_ZONE] + [--composer-internal-ipv4-cidr-block=COMPOSER_INTERNAL_IPV4_CIDR_BLOCK] [--disable-logs-in-cloud-logging-only] [--disk-size=DISK_SIZE] [--enable-high-resilience] [--enable-logs-in-cloud-logging-only] [--env-variables=[NAME=VALUE,...]] [--environment-size=ENVIRONMENT_SIZE] [--labels=[KEY=VALUE,...]] - [--machine-type=MACHINE_TYPE] [--node-count=NODE_COUNT] - [--oauth-scopes=[SCOPE,...]] [--python-version=PYTHON_VERSION] - [--service-account=SERVICE_ACCOUNT] [--storage-bucket=STORAGE_BUCKET] + [--machine-type=MACHINE_TYPE] [--network-attachment=NETWORK_ATTACHMENT] + [--node-count=NODE_COUNT] [--oauth-scopes=[SCOPE,...]] + [--python-version=PYTHON_VERSION] [--service-account=SERVICE_ACCOUNT] + [--storage-bucket=STORAGE_BUCKET] [--support-web-server-plugins] [--tags=[TAG,...]] [--web-server-machine-type=WEB_SERVER_MACHINE_TYPE] [--zone=ZONE] [--airflow-version=AIRFLOW_VERSION | --image-version=IMAGE_VERSION] @@ -30,8 +32,13 @@ SYNOPSIS --max-pods-per-node=MAX_PODS_PER_NODE --services-ipv4-cidr=SERVICES_IPV4_CIDR --services-secondary-range-name=SERVICES_SECONDARY_RANGE_NAME] + [--dag-processor-count=DAG_PROCESSOR_COUNT + --dag-processor-cpu=DAG_PROCESSOR_CPU + --dag-processor-memory=DAG_PROCESSOR_MEMORY + --dag-processor-storage=DAG_PROCESSOR_STORAGE] [--disable-cloud-data-lineage-integration | --enable-cloud-data-lineage-integration] + [--disable-private-builds-only | --enable-private-builds-only] [--enable-master-authorized-networks --master-authorized-networks=[NETWORK,...]] [--enable-scheduled-snapshot-creation @@ -128,6 +135,11 @@ FLAGS --cloud-sql-preferred-zone=CLOUD_SQL_PREFERRED_ZONE Select cloud sql preferred zone, supported for Composer 2 Environments. + --composer-internal-ipv4-cidr-block=COMPOSER_INTERNAL_IPV4_CIDR_BLOCK + The IP range in CIDR notation to use internally by Cloud Composer. This + should have a netmask length of 20. Can be specified for Composer 3 or + greater. + --disable-logs-in-cloud-logging-only Disable logs in cloud logging only, supported for Composer 2 Environments. @@ -171,6 +183,10 @@ FLAGS (https://cloud.google.com/compute/docs/machine-types) to use for nodes. For example --machine-type=n1-standard-1. + --network-attachment=NETWORK_ATTACHMENT + Cloud Composer Network Attachment, which provides connectivity with a + user's VPC network, supported in Composer 3 environments or greater. + --node-count=NODE_COUNT The number of nodes to create to run the environment. @@ -198,6 +214,10 @@ FLAGS Name of an exisiting Cloud Storage bucket to be used by the environment. Supported only for Composer 2.4.X and above. + --support-web-server-plugins + Enable the support for web server plugins, supported in Composer 3 or + greater. + --tags=[TAG,...] The set of instance tags applied to all node VMs. Tags are used to identify valid sources or targets for network firewalls. Each tag @@ -385,6 +405,27 @@ FLAGS When used with Composer 1.x, cannot be specified unless --enable-ip-alias is also specified. + Group of arguments for setting dag processor settings in Composer 3 or + greater. + + --dag-processor-count=DAG_PROCESSOR_COUNT + Number of dag processors, supported in Composer 3 environments or + greater. + + --dag-processor-cpu=DAG_PROCESSOR_CPU + CPU allocated to Airflow dag processor, supported in Composer 3 + environments or greater. + + --dag-processor-memory=DAG_PROCESSOR_MEMORY + Memory allocated to Airflow dag processor, ex. 1GB, 3GB, 2. If units + are not provided, defaults to GB, supported in Composer 3 + environments or greater. + + --dag-processor-storage=DAG_PROCESSOR_STORAGE + Storage allocated to Airflow dag processor, ex. 600MB, 3GB, 2. If + units are not provided, defaults to GB, supported in Composer 3 + environments or greater. + At most one of these can be specified: --disable-cloud-data-lineage-integration @@ -395,6 +436,17 @@ FLAGS Enable Cloud Data Lineage integration, supported for Composer 2 Environments. + At most one of these can be specified: + + --disable-private-builds-only + Builds performed during operations that install Python packages have + an access to the internet supported in Composer 3 or greater. + + --enable-private-builds-only + Builds performed during operations that install Python packages have + only private connectivity to Google services, supported in Composer 3 + or greater. + Master Authorized Networks configuration --enable-master-authorized-networks diff --git a/gcloud/beta/composer/environments/run b/gcloud/beta/composer/environments/run index d2e23b068..eb6a4c9b0 100644 --- a/gcloud/beta/composer/environments/run +++ b/gcloud/beta/composer/environments/run @@ -98,7 +98,7 @@ POSITIONAL ARGUMENTS [SUBCOMMAND_NESTED] Additional subcommand in case it is nested. The following is a list of allowed nested subcommands: - ◆ db: check + ◆ db: check, trim ◆ all other subcommands: all nested subcommands are allowed [-- CMD_ARGS ...] diff --git a/gcloud/beta/composer/environments/update b/gcloud/beta/composer/environments/update index 073d72139..62f2dcf42 100644 --- a/gcloud/beta/composer/environments/update +++ b/gcloud/beta/composer/environments/update @@ -7,10 +7,13 @@ SYNOPSIS (ENVIRONMENT : --location=LOCATION) (--cloud-sql-machine-type=CLOUD_SQL_MACHINE_TYPE | --disable-high-resilience | --disable-logs-in-cloud-logging-only - | --enable-high-resilience | --enable-logs-in-cloud-logging-only + | --disable-private-environment | --enable-high-resilience + | --enable-logs-in-cloud-logging-only | --enable-private-environment | --environment-size=ENVIRONMENT_SIZE | --node-count=NODE_COUNT + | --support-web-server-plugins | --web-server-machine-type=WEB_SERVER_MACHINE_TYPE | --airflow-version=AIRFLOW_VERSION | --image-version=IMAGE_VERSION + | --clear-maintenance-window | --maintenance-window-end=MAINTENANCE_WINDOW_END --maintenance-window-recurrence=MAINTENANCE_WINDOW_RECURRENCE --maintenance-window-start=MAINTENANCE_WINDOW_START @@ -19,19 +22,26 @@ SYNOPSIS | --disable-master-authorized-networks --enable-master-authorized-networks --master-authorized-networks=[NETWORK,...] + | --disable-private-builds-only | --enable-private-builds-only | --disable-scheduled-snapshot-creation | --enable-scheduled-snapshot-creation --snapshot-creation-schedule=SNAPSHOT_CREATION_SCHEDULE --snapshot-location=SNAPSHOT_LOCATION --snapshot-schedule-timezone=SNAPSHOT_SCHEDULE_TIMEZONE + | --disable-vpc-connectivity + | --network-attachment=NETWORK_ATTACHMENT + | [--network=NETWORK : --subnetwork=SUBNETWORK] | --max-workers=MAX_WORKERS --min-workers=MIN_WORKERS --scheduler-count=SCHEDULER_COUNT --scheduler-cpu=SCHEDULER_CPU --scheduler-memory=SCHEDULER_MEMORY --scheduler-storage=SCHEDULER_STORAGE --web-server-cpu=WEB_SERVER_CPU --web-server-memory=WEB_SERVER_MEMORY --web-server-storage=WEB_SERVER_STORAGE --worker-cpu=WORKER_CPU - --worker-memory=WORKER_MEMORY - --worker-storage=WORKER_STORAGE --disable-triggerer + --worker-memory=WORKER_MEMORY --worker-storage=WORKER_STORAGE + --dag-processor-count=DAG_PROCESSOR_COUNT + --dag-processor-cpu=DAG_PROCESSOR_CPU + --dag-processor-memory=DAG_PROCESSOR_MEMORY + --dag-processor-storage=DAG_PROCESSOR_STORAGE --disable-triggerer | --enable-triggerer --triggerer-count=TRIGGERER_COUNT --triggerer-cpu=TRIGGERER_CPU --triggerer-memory=TRIGGERER_MEMORY | --update-airflow-configs=[KEY=VALUE,...] --clear-airflow-configs @@ -108,6 +118,10 @@ REQUIRED FLAGS Disable logs in cloud logging only, supported for Composer 2 Environments. + --disable-private-environment + Enable internet connection from any Composer component, supported in + Composer 3 environments or greater. + --enable-high-resilience Enable high resilience, supported for Composer 2 Environments. @@ -115,6 +129,10 @@ REQUIRED FLAGS Enable logs in cloud logging only, supported for Composer 2 Environments. + --enable-private-environment + Disable internet connection from any Composer component, supported in + Composer 3 environments or greater. + --environment-size=ENVIRONMENT_SIZE Size of the environment. Unspecified means that the default option will be chosen. ENVIRONMENT_SIZE must be one of: large, medium, @@ -123,6 +141,10 @@ REQUIRED FLAGS --node-count=NODE_COUNT The new number of nodes running the environment. Must be >= 3. + --support-web-server-plugins + Enable the support for web server plugins, supported in Composer 3 or + greater. + --web-server-machine-type=WEB_SERVER_MACHINE_TYPE machine type used by the Airflow web server. The list of available machine types is available here: @@ -169,6 +191,10 @@ REQUIRED FLAGS At most one of these can be specified: + --clear-maintenance-window + Clears the maintenance window settings. Can be specified for + Composer 3 or greater. + Group of arguments for setting the maintenance window value. --maintenance-window-end=MAINTENANCE_WINDOW_END @@ -233,6 +259,17 @@ REQUIRED FLAGS Cannot be specified unless --enable-master-authorized-networks is also specified. + At most one of these can be specified: + + --disable-private-builds-only + Builds performed during operations that install Python packages + have an access to the internet supported in Composer 3 or greater. + + --enable-private-builds-only + Builds performed during operations that install Python packages + have only private connectivity to Google services, supported in + Composer 3 or greater. + Group of arguments used during update of scheduled snapshots settings in Composer 2.0.32 or greater. @@ -276,6 +313,32 @@ REQUIRED FLAGS This flag argument must be specified if any of the other arguments in this group are specified. + At most one of these can be specified: + + --disable-vpc-connectivity + Disable connectivity with a user's VPC network, supported in + Composer 3 environments or greater. + + --network-attachment=NETWORK_ATTACHMENT + Cloud Composer Network Attachment, which provides connectivity with + a user's VPC network, supported in Composer 3 environments or + greater. + + Virtual Private Cloud networking + + --network=NETWORK + The Compute Engine Network to which the environment will be + connected. If a 'Custom Subnet Network' is provided, --subnetwork + must be specified as well. + + This flag argument must be specified if any of the other + arguments in this group are specified. + + --subnetwork=SUBNETWORK + The Compute Engine subnetwork + (https://cloud.google.com/compute/docs/subnetworks) to which the + environment will be connected. + Group of arguments for setting workloads configuration in Composer 2.X or greater (--scheduler-count flag is available for Composer 1.X as well). @@ -323,6 +386,27 @@ REQUIRED FLAGS Storage allocated to Airflow worker, ex. 600MB, 3GB, 2. If units are not provided, defaults to GB. + Group of arguments for setting dag processor settings in Composer 3 or + greater. + + --dag-processor-count=DAG_PROCESSOR_COUNT + Number of dag processors, supported in Composer 3 environments or + greater. + + --dag-processor-cpu=DAG_PROCESSOR_CPU + CPU allocated to Airflow dag processor, supported in Composer 3 + environments or greater. + + --dag-processor-memory=DAG_PROCESSOR_MEMORY + Memory allocated to Airflow dag processor, ex. 1GB, 3GB, 2. If + units are not provided, defaults to GB, supported in Composer 3 + environments or greater. + + --dag-processor-storage=DAG_PROCESSOR_STORAGE + Storage allocated to Airflow dag processor, ex. 600MB, 3GB, 2. If + units are not provided, defaults to GB, supported in Composer 3 + environments or greater. + Group of arguments for setting triggerer settings in Composer 2.0.31 or greater. diff --git a/gcloud/beta/compute/images/list b/gcloud/beta/compute/images/list index e44a62c32..98f5851d4 100644 --- a/gcloud/beta/compute/images/list +++ b/gcloud/beta/compute/images/list @@ -2,10 +2,11 @@ NAME gcloud beta compute images list - list Google Compute Engine images SYNOPSIS - gcloud beta compute images list [NAME ...] [--preview-images] - [--regexp=REGEXP, -r REGEXP] [--show-deprecated] [--no-standard-images] - [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] - [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + gcloud beta compute images list [NAME ...] [--image-zone=IMAGE_ZONE] + [--preview-images] [--regexp=REGEXP, -r REGEXP] [--show-deprecated] + [--no-standard-images] [--filter=EXPRESSION] [--limit=LIMIT] + [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) gcloud beta compute images list displays all Google Compute Engine @@ -35,6 +36,11 @@ POSITIONAL ARGUMENTS instead. FLAGS + --image-zone=IMAGE_ZONE + Zone to query. Returns the latest image available in the image family, + for the specified zone. If not specified, returns the latest globally + available image. + --preview-images Show images that are in limited preview. The preview image projects are: (none) diff --git a/gcloud/beta/compute/instance-groups/managed/create b/gcloud/beta/compute/instance-groups/managed/create index b842d10f0..5c1484d89 100644 --- a/gcloud/beta/compute/instance-groups/managed/create +++ b/gcloud/beta/compute/instance-groups/managed/create @@ -9,6 +9,7 @@ SYNOPSIS [--description=DESCRIPTION] [--[no-]force-update-on-repair] [--initial-delay=INITIAL_DELAY] [--instance-redistribution-type=TYPE] [--list-managed-instances-results=MODE] + [--resource-manager-tags=[KEY=VALUE,...]] [--standby-policy-initial-delay=STANDBY_POLICY_INITIAL_DELAY] [--standby-policy-mode=STANDBY_POLICY_MODE] [--stateful-disk=[auto-delete=AUTO-DELETE],[device-name=DEVICE-NAME]] @@ -143,6 +144,12 @@ OPTIONAL FLAGS Pagination is enabled for the group's listManagedInstances API method. maxResults and pageToken query parameters are respected. + --resource-manager-tags=[KEY=VALUE,...] + Specifies a list of resource manager tags to apply to the managed + instance group. A resource manager tag is a key-value pair. You can + attach exactly one value to a MIG for a given key. A MIG can have a + maximum of 50 key-value pairs attached. + --standby-policy-initial-delay=STANDBY_POLICY_INITIAL_DELAY Specifies the number of seconds that the MIG should wait before suspending or stopping a VM. The initial delay gives the initialization diff --git a/gcloud/beta/compute/instances/bulk/create b/gcloud/beta/compute/instances/bulk/create index 7ca1dbc01..563e82dd1 100644 --- a/gcloud/beta/compute/instances/bulk/create +++ b/gcloud/beta/compute/instances/bulk/create @@ -589,8 +589,9 @@ OPTIONAL FLAGS --network-interface=[PROPERTY=VALUE,...] Adds a network interface to the instance. Mutually exclusive with any - of these flags: --network, --network-tier, --subnet. This flag can be - repeated to specify multiple network interfaces. + of these flags: --network, --network-tier, --no-address, --subnet, + --stack-type. This flag can be repeated to specify multiple network + interfaces. network Specifies the network that the interface will be part of. If subnet @@ -610,6 +611,10 @@ OPTIONAL FLAGS Specifies the Network Interface Controller (NIC) type for the interface. NIC_TYPE must be one of: GVNIC, VIRTIO_NET. + no-address + If specified the interface will have no external IP. If not + specified instances will get ephemeral IPs. + queue-count Specifies the networking queue count for this interface. Both Rx and Tx queues will be set to this number. If it's not specified, a diff --git a/gcloud/beta/logging/sinks/create b/gcloud/beta/logging/sinks/create index 15ba668c9..d583a7c21 100644 --- a/gcloud/beta/logging/sinks/create +++ b/gcloud/beta/logging/sinks/create @@ -7,7 +7,8 @@ SYNOPSIS [--description=DESCRIPTION] [--disabled] [--exclusion=[description=DESCRIPTION], [disabled=DISABLED],[filter=FILTER],[name=NAME]] [--include-children] - [--log-filter=LOG_FILTER] [--use-partitioned-tables] + [--intercept-children] [--log-filter=LOG_FILTER] + [--use-partitioned-tables] [--billing-account=BILLING_ACCOUNT_ID | --folder=FOLDER_ID | --organization=ORGANIZATION_ID | --project=PROJECT_ID] [GCLOUD_WIDE_FLAG ...] @@ -113,6 +114,10 @@ FLAGS Whether to export logs from all child projects and folders. Only applies to sinks for organizations and folders. + --intercept-children + Whether to intercept logs from all child projects and folders. Only + applies to sinks for organizations and folders. + --log-filter=LOG_FILTER A filter expression for the sink. If present, the filter specifies which log entries to export. diff --git a/gcloud/beta/logging/sinks/list b/gcloud/beta/logging/sinks/list index 9a0c6386a..465dcc8d4 100644 --- a/gcloud/beta/logging/sinks/list +++ b/gcloud/beta/logging/sinks/list @@ -2,7 +2,7 @@ NAME gcloud beta logging sinks list - list the defined sinks SYNOPSIS - gcloud beta logging sinks list + gcloud beta logging sinks list [--sink-filter=SINK_FILTER] [--billing-account=BILLING_ACCOUNT_ID | --folder=FOLDER_ID | --organization=ORGANIZATION_ID | --project=PROJECT_ID] [--filter=EXPRESSION] [--limit=LIMIT] [--sort-by=[FIELD,...]] @@ -17,6 +17,11 @@ EXAMPLES $ gcloud beta logging sinks list --limit=10 FLAGS + --sink-filter=SINK_FILTER + A filter expression passed to the Logging API to constrain the sinks + returned. For information on accepted values, see + https://cloud.google.com/logging/docs/reference/v2/rpc/google.logging.v2#listsinksrequest + At most one of these can be specified: --billing-account=BILLING_ACCOUNT_ID diff --git a/gcloud/beta/logging/sinks/update b/gcloud/beta/logging/sinks/update index ba4ce50cc..e38191d3d 100644 --- a/gcloud/beta/logging/sinks/update +++ b/gcloud/beta/logging/sinks/update @@ -6,7 +6,8 @@ SYNOPSIS [--add-exclusion=[description=DESCRIPTION], [disabled=DISABLED],[filter=FILTER],[name=NAME]] [--clear-exclusions] [--custom-writer-identity=SERVICE_ACCOUNT_EMAIL] - [--description=DESCRIPTION] [--disabled] [--log-filter=LOG_FILTER] + [--description=DESCRIPTION] [--disabled] [--include-children] + [--intercept-children] [--log-filter=LOG_FILTER] [--remove-exclusions=[EXCLUSION ID,...]] [--update-exclusion=[description=DESCRIPTION], [disabled=DISABLED],[filter=FILTER],[name=NAME]] @@ -79,6 +80,14 @@ FLAGS destination. Specify --no-disabled to enable a disabled sink. If this flag is not specified, the value will not be updated. + --include-children + Whether to export logs from all child projects and folders. Only + applies to sinks for organizations and folders. + + --intercept-children + Whether to intercept logs from all child projects and folders. Only + applies to sinks for organizations and folders. + --log-filter=LOG_FILTER A new filter expression for the sink. If omitted, the sink's existing filter (if any) is unchanged. diff --git a/gcloud/beta/redis/clusters/create b/gcloud/beta/redis/clusters/create index 8bf73996b..ff3911656 100644 --- a/gcloud/beta/redis/clusters/create +++ b/gcloud/beta/redis/clusters/create @@ -4,8 +4,12 @@ NAME SYNOPSIS gcloud beta redis clusters create (CLUSTER : --region=REGION) - --network=NETWORK --shard-count=SHARD_COUNT [--async] - [--auth-mode=AUTH_MODE] [--replica-count=REPLICA_COUNT] + --network=NETWORK --shard-count=SHARD_COUNT + [--aof-append-fsync=AOF_APPEND_FSYNC] [--async] [--auth-mode=AUTH_MODE] + [--persistence-mode=PERSISTENCE_MODE] + [--rdb-snapshot-period=RDB_SNAPSHOT_PERIOD] + [--rdb-snapshot-start-time=RDB_SNAPSHOT_START_TIME] + [--redis-config=[KEY=VALUE,...]] [--replica-count=REPLICA_COUNT] [--transit-encryption-mode=TRANSIT_ENCRYPTION_MODE] [--zone=ZONE] [--zone-distribution-mode=ZONE_DISTRIBUTION_MODE] [GCLOUD_WIDE_FLAG ...] @@ -84,6 +88,18 @@ REQUIRED FLAGS The shard count of the cluster. OPTIONAL FLAGS + --aof-append-fsync=AOF_APPEND_FSYNC + Fsync configuration. AOF_APPEND_FSYNC must be one of: + + always + Redis explicitly calls fsync for every write command. + + everysec + (default) Redis explicitly calls fsync every second. + + no + Redis will not explicitly call fsync. + --async Return immediately, without waiting for the operation in progress to complete. @@ -98,6 +114,42 @@ OPTIONAL FLAGS iam-auth IAM basic authorization is enabled for the cluster. + --persistence-mode=PERSISTENCE_MODE + Operation mode for persistence. PERSISTENCE_MODE must be one of: + + aof + AOF-based persistence + disabled + Persistence mode is disabled + rdb + RDB-based persistence + + --rdb-snapshot-period=RDB_SNAPSHOT_PERIOD + Attempted period between RDB snapshots. RDB_SNAPSHOT_PERIOD must be one + of: + + 12h + 12 hours + 1h + 1 hour + 24h + (default) 24 hours + 6h + 6 hours + + --rdb-snapshot-start-time=RDB_SNAPSHOT_START_TIME + Date and time of the first snapshot in the ISO 1801 format, and + alignment time for future snapshots. For example, 2024-01-01T01:00:00Z. + If not specified, the current time will be used. + + --redis-config=[KEY=VALUE,...] + A list of Redis config KEY=VALUE pairs to set on the Redis Cluster + according to http://redis.io/topics/config. Currently the supported + Redis configs are: + + maxmemory-clients, maxmemory, maxmemory-policy, notify-keyspace-events, + slowlog-log-slower-than, maxclients. + --replica-count=REPLICA_COUNT The replica count of each shard. diff --git a/gcloud/beta/redis/clusters/update b/gcloud/beta/redis/clusters/update index 3340c8634..fd405f038 100644 --- a/gcloud/beta/redis/clusters/update +++ b/gcloud/beta/redis/clusters/update @@ -3,8 +3,13 @@ NAME instance SYNOPSIS - gcloud beta redis clusters update (CLUSTER : --region=REGION) [--async] - [--replica-count=REPLICA_COUNT] [--shard-count=SHARD_COUNT] + gcloud beta redis clusters update (CLUSTER : --region=REGION) + [--aof-append-fsync=AOF_APPEND_FSYNC] [--async] + [--persistence-mode=PERSISTENCE_MODE] + [--rdb-snapshot-period=RDB_SNAPSHOT_PERIOD] + [--rdb-snapshot-start-time=RDB_SNAPSHOT_START_TIME] + [--remove-redis-config=[KEY,...]] [--replica-count=REPLICA_COUNT] + [--shard-count=SHARD_COUNT] [--update-redis-config=KEY=VALUE] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -56,16 +61,65 @@ POSITIONAL ARGUMENTS ▸ set the property redis/region. FLAGS + --aof-append-fsync=AOF_APPEND_FSYNC + Fsync configuration. AOF_APPEND_FSYNC must be one of: + + always + Redis explicitly calls fsync for every write command. + + everysec + (default) Redis explicitly calls fsync every second. + + no + Redis will not explicitly call fsync. + --async Return immediately, without waiting for the operation in progress to complete. + --persistence-mode=PERSISTENCE_MODE + Operation mode for persistence. PERSISTENCE_MODE must be one of: + + aof + AOF-based persistence + disabled + Persistence mode is disabled + rdb + RDB-based persistence + + --rdb-snapshot-period=RDB_SNAPSHOT_PERIOD + Attempted period between RDB snapshots. RDB_SNAPSHOT_PERIOD must be one + of: + + 12h + 12 hours + 1h + 1 hour + 24h + (default) 24 hours + 6h + 6 hours + + --rdb-snapshot-start-time=RDB_SNAPSHOT_START_TIME + Date and time of the first snapshot in the ISO 1801 format, and + alignment time for future snapshots. For example, 2024-01-01T01:00:00Z. + If not specified, the current time will be used. + + --remove-redis-config=[KEY,...] + A list of Redis Cluster config parameters to remove. Removing a + non-existent config parameter is silently ignored. + --replica-count=REPLICA_COUNT The replica count of each shard. --shard-count=SHARD_COUNT The shard count of the cluster. + --update-redis-config=KEY=VALUE + A list of Redis Cluster config KEY=VALUE pairs to update. If a config + parameter is already set, its value is modified; otherwise a new Redis + config parameter is added. + 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/secrets/add-iam-policy-binding b/gcloud/beta/secrets/add-iam-policy-binding index ea4db1393..0ca8e060c 100644 --- a/gcloud/beta/secrets/add-iam-policy-binding +++ b/gcloud/beta/secrets/add-iam-policy-binding @@ -3,8 +3,8 @@ NAME secret resource SYNOPSIS - gcloud beta secrets add-iam-policy-binding (SECRET : --location=LOCATION) - --member=PRINCIPAL --role=ROLE + gcloud beta secrets add-iam-policy-binding SECRET --member=PRINCIPAL + --role=ROLE [--condition=[KEY=VALUE,...] | --condition-from-file=CONDITION_FROM_FILE] [GCLOUD_WIDE_FLAG ...] @@ -24,38 +24,23 @@ EXAMPLES policy role and member types. POSITIONAL ARGUMENTS - Global or regional secret resource - create a secret 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. + Secret resource - The secret to add iam policy. This represents a Cloud + resource. (NOTE) Some attributes are not given arguments in this group but + can be set in other ways. To set the project attribute: - ◆ provide the argument secret on the command line with a fully + ◆ provide the argument SECRET on the command line with a fully specified name; ◆ provide the argument --project on the command line; - ◆ set the property core/project. This resource can be one of the - following types: [secret, regional secret]. + ◆ set the property core/project. This must be specified. SECRET - ID of the global or regional secret or fully qualified identifier for - the global or regional secret. + ID of the secret or fully qualified identifier for the secret. To set the secret attribute: - ▸ provide the argument secret on the command line. - - This positional argument must be specified if any of the other - arguments in this group are specified. - - --location=LOCATION - [EXPERIMENTAL] The location of the global or regional secret. - - To set the location attribute: - ▸ provide the argument secret on the command line with a fully - specified name; - ▸ provide the argument --location on the command line. Must be - specified for resource of type [regional secret]. + ▸ provide the argument SECRET on the command line. REQUIRED FLAGS --member=PRINCIPAL diff --git a/gcloud/beta/secrets/create b/gcloud/beta/secrets/create index e504aaab8..edd3996d7 100644 --- a/gcloud/beta/secrets/create +++ b/gcloud/beta/secrets/create @@ -2,11 +2,9 @@ NAME gcloud beta secrets create - create a new secret SYNOPSIS - gcloud beta secrets create (SECRET : --location=LOCATION) - [--data-file=PATH] [--labels=[KEY=VALUE,...]] - [--regional-kms-key-name=KMS-KEY-NAME] - [--set-annotations=[KEY=VALUE,...]] [--topics=[TOPICS,...]] - [--version-destroy-ttl=VERSION-DESTROY-TTL] + gcloud beta secrets create SECRET [--data-file=PATH] + [--labels=[KEY=VALUE,...]] [--set-annotations=[KEY=VALUE,...]] + [--topics=[TOPICS,...]] [--version-destroy-ttl=VERSION-DESTROY-TTL] [--expire-time=EXPIRE-TIME | --ttl=TTL] [--next-rotation-time=NEXT_ROTATION_TIME --rotation-period=ROTATION_PERIOD] @@ -80,38 +78,23 @@ EXAMPLES $ gcloud beta secrets create my-secret --version-destroy-ttl="86400s" POSITIONAL ARGUMENTS - Global or regional secret resource - create a secret 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. + Secret resource - The secret to create. This represents a Cloud resource. + (NOTE) Some attributes are not given arguments in this group but can be + set in other ways. To set the project attribute: - ◆ provide the argument secret on the command line with a fully + ◆ provide the argument SECRET on the command line with a fully specified name; ◆ provide the argument --project on the command line; - ◆ set the property core/project. This resource can be one of the - following types: [secret, regional secret]. + ◆ set the property core/project. This must be specified. SECRET - ID of the global or regional secret or fully qualified identifier for - the global or regional secret. + ID of the secret or fully qualified identifier for the secret. To set the secret attribute: - ▸ provide the argument secret on the command line. - - This positional argument must be specified if any of the other - arguments in this group are specified. - - --location=LOCATION - [EXPERIMENTAL] The location of the global or regional secret. - - To set the location attribute: - ▸ provide the argument secret on the command line with a fully - specified name; - ▸ provide the argument --location on the command line. Must be - specified for resource of type [regional secret]. + ▸ provide the argument SECRET on the command line. FLAGS --data-file=PATH @@ -126,10 +109,6 @@ FLAGS contain only hyphens (-), underscores (_), lowercase characters, and numbers. - --regional-kms-key-name=KMS-KEY-NAME - Regional KMS key with which to encrypt and decrypt the secret. Only - valid for regional secrets. - Annotations --set-annotations=[KEY=VALUE,...] diff --git a/gcloud/beta/secrets/delete b/gcloud/beta/secrets/delete index b9e3fb7b6..8143734e0 100644 --- a/gcloud/beta/secrets/delete +++ b/gcloud/beta/secrets/delete @@ -2,8 +2,7 @@ NAME gcloud beta secrets delete - delete a secret SYNOPSIS - gcloud beta secrets delete (SECRET : --location=LOCATION) [--etag=ETAG] - [GCLOUD_WIDE_FLAG ...] + gcloud beta secrets delete SECRET [--etag=ETAG] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) Delete a secret and destroy all secret versions. This action is @@ -20,38 +19,23 @@ EXAMPLES $ gcloud beta secrets delete my-secret --etag=\"123\" POSITIONAL ARGUMENTS - Global or regional secret resource - to delete 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. + Secret resource - The secret to delete. This represents a Cloud resource. + (NOTE) Some attributes are not given arguments in this group but can be + set in other ways. To set the project attribute: - ◆ provide the argument secret on the command line with a fully + ◆ provide the argument SECRET on the command line with a fully specified name; ◆ provide the argument --project on the command line; - ◆ set the property core/project. This resource can be one of the - following types: [secret, regional secret]. + ◆ set the property core/project. This must be specified. SECRET - ID of the global or regional secret or fully qualified identifier for - the global or regional secret. + ID of the secret or fully qualified identifier for the secret. To set the secret attribute: - ▸ provide the argument secret on the command line. - - This positional argument must be specified if any of the other - arguments in this group are specified. - - --location=LOCATION - [EXPERIMENTAL] The location of the global or regional secret. - - To set the location attribute: - ▸ provide the argument secret on the command line with a fully - specified name; - ▸ provide the argument --location on the command line. Must be - specified for resource of type [regional secret]. + ▸ provide the argument SECRET on the command line. FLAGS --etag=ETAG diff --git a/gcloud/beta/secrets/describe b/gcloud/beta/secrets/describe index e90c36a32..baf728e78 100644 --- a/gcloud/beta/secrets/describe +++ b/gcloud/beta/secrets/describe @@ -2,8 +2,7 @@ NAME gcloud beta secrets describe - describe a secret's metadata SYNOPSIS - gcloud beta secrets describe (SECRET : --location=LOCATION) - [GCLOUD_WIDE_FLAG ...] + gcloud beta secrets describe SECRET [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) Describe a secret's metadata. @@ -14,38 +13,23 @@ EXAMPLES $ gcloud beta secrets describe my-secret POSITIONAL ARGUMENTS - Global or regional secret resource - to describe 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. + Secret resource - The secret to describe. This represents a Cloud + resource. (NOTE) Some attributes are not given arguments in this group but + can be set in other ways. To set the project attribute: - ◆ provide the argument secret on the command line with a fully + ◆ provide the argument SECRET on the command line with a fully specified name; ◆ provide the argument --project on the command line; - ◆ set the property core/project. This resource can be one of the - following types: [secret, regional secret]. + ◆ set the property core/project. This must be specified. SECRET - ID of the global or regional secret or fully qualified identifier for - the global or regional secret. + ID of the secret or fully qualified identifier for the secret. To set the secret attribute: - ▸ provide the argument secret on the command line. - - This positional argument must be specified if any of the other - arguments in this group are specified. - - --location=LOCATION - [EXPERIMENTAL] The location of the global or regional secret. - - To set the location attribute: - ▸ provide the argument secret on the command line with a fully - specified name; - ▸ provide the argument --location on the command line. Must be - specified for resource of type [regional secret]. + ▸ provide the argument SECRET on the command line. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/beta/secrets/get-iam-policy b/gcloud/beta/secrets/get-iam-policy index 772779302..af2a50854 100644 --- a/gcloud/beta/secrets/get-iam-policy +++ b/gcloud/beta/secrets/get-iam-policy @@ -2,9 +2,9 @@ NAME gcloud beta secrets get-iam-policy - get the IAM policy of a secret SYNOPSIS - gcloud beta secrets get-iam-policy (SECRET : --location=LOCATION) - [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] - [--sort-by=[FIELD,...]] [GCLOUD_WIDE_FLAG ...] + gcloud beta secrets get-iam-policy SECRET [--filter=EXPRESSION] + [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) Gets the IAM policy for the given secret. @@ -17,38 +17,23 @@ EXAMPLES $ gcloud beta secrets get-iam-policy my-secret [--location=] POSITIONAL ARGUMENTS - Global or regional secret resource - create a secret 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. + Secret resource - The secret to get iam policy. This represents a Cloud + resource. (NOTE) Some attributes are not given arguments in this group but + can be set in other ways. To set the project attribute: - ◆ provide the argument secret on the command line with a fully + ◆ provide the argument SECRET on the command line with a fully specified name; ◆ provide the argument --project on the command line; - ◆ set the property core/project. This resource can be one of the - following types: [secret, regional secret]. + ◆ set the property core/project. This must be specified. SECRET - ID of the global or regional secret or fully qualified identifier for - the global or regional secret. + ID of the secret or fully qualified identifier for the secret. To set the secret attribute: - ▸ provide the argument secret on the command line. - - This positional argument must be specified if any of the other - arguments in this group are specified. - - --location=LOCATION - [EXPERIMENTAL] The location of the global or regional secret. - - To set the location attribute: - ▸ provide the argument secret on the command line with a fully - specified name; - ▸ provide the argument --location on the command line. Must be - specified for resource of type [regional secret]. + ▸ provide the argument SECRET on the command line. LIST COMMAND FLAGS --filter=EXPRESSION diff --git a/gcloud/beta/secrets/remove-iam-policy-binding b/gcloud/beta/secrets/remove-iam-policy-binding index ae4910aa7..0d6304a20 100644 --- a/gcloud/beta/secrets/remove-iam-policy-binding +++ b/gcloud/beta/secrets/remove-iam-policy-binding @@ -3,8 +3,8 @@ NAME of a secret resource SYNOPSIS - gcloud beta secrets remove-iam-policy-binding - (SECRET : --location=LOCATION) --member=PRINCIPAL --role=ROLE + gcloud beta secrets remove-iam-policy-binding SECRET --member=PRINCIPAL + --role=ROLE [--all | --condition=[KEY=VALUE,...] | --condition-from-file=CONDITION_FROM_FILE] [GCLOUD_WIDE_FLAG ...] @@ -19,38 +19,23 @@ EXAMPLES --member='user:test-user@gmail.com' --role='roles/viewer' POSITIONAL ARGUMENTS - Global or regional secret resource - create a secret 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. + Secret resource - The secret to remove iam policy. This represents a Cloud + resource. (NOTE) Some attributes are not given arguments in this group but + can be set in other ways. To set the project attribute: - ◆ provide the argument secret on the command line with a fully + ◆ provide the argument SECRET on the command line with a fully specified name; ◆ provide the argument --project on the command line; - ◆ set the property core/project. This resource can be one of the - following types: [secret, regional secret]. + ◆ set the property core/project. This must be specified. SECRET - ID of the global or regional secret or fully qualified identifier for - the global or regional secret. + ID of the secret or fully qualified identifier for the secret. To set the secret attribute: - ▸ provide the argument secret on the command line. - - This positional argument must be specified if any of the other - arguments in this group are specified. - - --location=LOCATION - [EXPERIMENTAL] The location of the global or regional secret. - - To set the location attribute: - ▸ provide the argument secret on the command line with a fully - specified name; - ▸ provide the argument --location on the command line. Must be - specified for resource of type [regional secret]. + ▸ provide the argument SECRET on the command line. REQUIRED FLAGS --member=PRINCIPAL diff --git a/gcloud/beta/secrets/set-iam-policy b/gcloud/beta/secrets/set-iam-policy index 292d8ff7e..0f785be71 100644 --- a/gcloud/beta/secrets/set-iam-policy +++ b/gcloud/beta/secrets/set-iam-policy @@ -2,8 +2,8 @@ NAME gcloud beta secrets set-iam-policy - set the IAM policy for a secret SYNOPSIS - gcloud beta secrets set-iam-policy (SECRET : --location=LOCATION) - POLICY_FILE [GCLOUD_WIDE_FLAG ...] + gcloud beta secrets set-iam-policy SECRET POLICY_FILE + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) Sets the IAM policy for the given secret. @@ -16,38 +16,23 @@ EXAMPLES $ gcloud beta secrets set-iam-policy my-secret [--location=] POSITIONAL ARGUMENTS - Global or regional secret resource - create a secret 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. + Secret resource - The secret to set iam policy. This represents a Cloud + resource. (NOTE) Some attributes are not given arguments in this group but + can be set in other ways. To set the project attribute: - ◆ provide the argument secret on the command line with a fully + ◆ provide the argument SECRET on the command line with a fully specified name; ◆ provide the argument --project on the command line; - ◆ set the property core/project. This resource can be one of the - following types: [secret, regional secret]. + ◆ set the property core/project. This must be specified. SECRET - ID of the global or regional secret or fully qualified identifier for - the global or regional secret. + ID of the secret or fully qualified identifier for the secret. To set the secret attribute: - ▸ provide the argument secret on the command line. - - This positional argument must be specified if any of the other - arguments in this group are specified. - - --location=LOCATION - [EXPERIMENTAL] The location of the global or regional secret. - - To set the location attribute: - ▸ provide the argument secret on the command line with a fully - specified name; - ▸ provide the argument --location on the command line. Must be - specified for resource of type [regional secret]. + ▸ provide the argument SECRET on the command line. POLICY_FILE Path to a local JSON or YAML formatted file containing a valid policy. diff --git a/gcloud/beta/secrets/update b/gcloud/beta/secrets/update index ff51b108c..96c34486d 100644 --- a/gcloud/beta/secrets/update +++ b/gcloud/beta/secrets/update @@ -2,7 +2,7 @@ NAME gcloud beta secrets update - update a secret's metadata SYNOPSIS - gcloud beta secrets update (SECRET : --location=LOCATION) [--etag=ETAG] + gcloud beta secrets update SECRET [--etag=ETAG] [--update-labels=[KEY=VALUE,...]] [--add-topics=[ADD-TOPICS,...] | --clear-topics | --remove-topics=[REMOVE-TOPICS,...]] @@ -73,38 +73,23 @@ EXAMPLES $ gcloud beta secrets update my-secret --remove-version-destroy-ttl POSITIONAL ARGUMENTS - Global or regional secret resource - to update 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. + Secret resource - The secret to update. This represents a Cloud resource. + (NOTE) Some attributes are not given arguments in this group but can be + set in other ways. To set the project attribute: - ◆ provide the argument secret on the command line with a fully + ◆ provide the argument SECRET on the command line with a fully specified name; ◆ provide the argument --project on the command line; - ◆ set the property core/project. This resource can be one of the - following types: [secret, regional secret]. + ◆ set the property core/project. This must be specified. SECRET - ID of the global or regional secret or fully qualified identifier for - the global or regional secret. + ID of the secret or fully qualified identifier for the secret. To set the secret attribute: - ▸ provide the argument secret on the command line. - - This positional argument must be specified if any of the other - arguments in this group are specified. - - --location=LOCATION - [EXPERIMENTAL] The location of the global or regional secret. - - To set the location attribute: - ▸ provide the argument secret on the command line with a fully - specified name; - ▸ provide the argument --location on the command line. Must be - specified for resource of type [regional secret]. + ▸ provide the argument SECRET on the command line. FLAGS --etag=ETAG diff --git a/gcloud/beta/secrets/versions/access b/gcloud/beta/secrets/versions/access index 512d1b856..0ef4a748d 100644 --- a/gcloud/beta/secrets/versions/access +++ b/gcloud/beta/secrets/versions/access @@ -2,8 +2,7 @@ NAME gcloud beta secrets versions access - access a secret version's data SYNOPSIS - gcloud beta secrets versions access - (VERSION : --location=LOCATION --secret=SECRET) + gcloud beta secrets versions access (VERSION : --secret=SECRET) [--out-file=OUT-FILE-PATH] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -29,44 +28,34 @@ EXAMPLES --format='get(payload.data)' | tr '_-' '/+' | base64 -d POSITIONAL ARGUMENTS - Global or regional secret version resource - to access 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. + Version resource - Numeric secret version to access or a configured alias + (including 'latest' to use the latest version). 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 version on the command line with a fully + ◆ provide the argument VERSION on the command line with a fully specified name; ◆ provide the argument --project on the command line; - ◆ set the property core/project. This resource can be one of the - following types: [version, regional version]. + ◆ set the property core/project. This must be specified. VERSION - ID of the global or regional secret version or fully qualified - identifier for the global or regional secret version. + ID of the version or fully qualified identifier for the version. To set the version attribute: - ▸ provide the argument version on the command line. + ▸ provide the argument VERSION on the command line. This positional argument must be specified if any of the other arguments in this group are specified. - --location=LOCATION - [EXPERIMENTAL] The location of the global or regional secret version. - - To set the location attribute: - ▸ provide the argument version on the command line with a fully - specified name; - ▸ provide the argument --location on the command line. Must be - specified for resource of type [regional version]. - --secret=SECRET - The secret of the global or regional secret version. + The secret of the version. To set the secret attribute: - ▸ provide the argument version on the command line with a fully + ▸ provide the argument VERSION on the command line with a fully specified name; ▸ provide the argument --secret on the command line. diff --git a/gcloud/beta/secrets/versions/add b/gcloud/beta/secrets/versions/add index ded0b3b55..a0dcb4e40 100644 --- a/gcloud/beta/secrets/versions/add +++ b/gcloud/beta/secrets/versions/add @@ -3,8 +3,8 @@ NAME secret SYNOPSIS - gcloud beta secrets versions add (SECRET : --location=LOCATION) - --data-file=PATH [GCLOUD_WIDE_FLAG ...] + gcloud beta secrets versions add SECRET --data-file=PATH + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) Create a new version of an existing secret with the provided data. @@ -30,38 +30,23 @@ EXAMPLES $ gcloud beta secrets versions add my-secret --data-file=/tmp/secret POSITIONAL ARGUMENTS - Global or regional secret resource - to create 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. + Secret resource - The secret to create. This represents a Cloud resource. + (NOTE) Some attributes are not given arguments in this group but can be + set in other ways. To set the project attribute: - ◆ provide the argument secret on the command line with a fully + ◆ provide the argument SECRET on the command line with a fully specified name; ◆ provide the argument --project on the command line; - ◆ set the property core/project. This resource can be one of the - following types: [secret, regional secret]. + ◆ set the property core/project. This must be specified. SECRET - ID of the global or regional secret or fully qualified identifier for - the global or regional secret. + ID of the secret or fully qualified identifier for the secret. To set the secret attribute: - ▸ provide the argument secret on the command line. - - This positional argument must be specified if any of the other - arguments in this group are specified. - - --location=LOCATION - [EXPERIMENTAL] The location of the global or regional secret. - - To set the location attribute: - ▸ provide the argument secret on the command line with a fully - specified name; - ▸ provide the argument --location on the command line. Must be - specified for resource of type [regional secret]. + ▸ provide the argument SECRET on the command line. REQUIRED FLAGS --data-file=PATH diff --git a/gcloud/beta/secrets/versions/destroy b/gcloud/beta/secrets/versions/destroy index 8bfaf3ca0..556582e1f 100644 --- a/gcloud/beta/secrets/versions/destroy +++ b/gcloud/beta/secrets/versions/destroy @@ -3,9 +3,8 @@ NAME and secret data SYNOPSIS - gcloud beta secrets versions destroy - (VERSION : --location=LOCATION --secret=SECRET) [--etag=ETAG] - [GCLOUD_WIDE_FLAG ...] + gcloud beta secrets versions destroy (VERSION : --secret=SECRET) + [--etag=ETAG] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) Destroy a secret version's metadata and secret data. This action is @@ -22,44 +21,33 @@ EXAMPLES --etag=\"123\" POSITIONAL ARGUMENTS - Global or regional secret version resource - to destroy The arguments in + Version resource - Numeric secret version to destroy. 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 version on the command line with a fully + ◆ provide the argument VERSION on the command line with a fully specified name; ◆ provide the argument --project on the command line; - ◆ set the property core/project. This resource can be one of the - following types: [version, regional version]. + ◆ set the property core/project. This must be specified. VERSION - ID of the global or regional secret version or fully qualified - identifier for the global or regional secret version. + ID of the version or fully qualified identifier for the version. To set the version attribute: - ▸ provide the argument version on the command line. + ▸ provide the argument VERSION on the command line. This positional argument must be specified if any of the other arguments in this group are specified. - --location=LOCATION - [EXPERIMENTAL] The location of the global or regional secret version. - - To set the location attribute: - ▸ provide the argument version on the command line with a fully - specified name; - ▸ provide the argument --location on the command line. Must be - specified for resource of type [regional version]. - --secret=SECRET - The secret of the global or regional secret version. + The secret of the version. To set the secret attribute: - ▸ provide the argument version on the command line with a fully + ▸ provide the argument VERSION on the command line with a fully specified name; ▸ provide the argument --secret on the command line. diff --git a/gcloud/beta/secrets/versions/disable b/gcloud/beta/secrets/versions/disable index bfd92a4e3..18e93e372 100644 --- a/gcloud/beta/secrets/versions/disable +++ b/gcloud/beta/secrets/versions/disable @@ -3,9 +3,8 @@ NAME secret SYNOPSIS - gcloud beta secrets versions disable - (VERSION : --location=LOCATION --secret=SECRET) [--etag=ETAG] - [GCLOUD_WIDE_FLAG ...] + gcloud beta secrets versions disable (VERSION : --secret=SECRET) + [--etag=ETAG] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) Disable the version of the provided secret. It can be re-enabled @@ -22,44 +21,33 @@ EXAMPLES --etag=\"123\" POSITIONAL ARGUMENTS - Global or regional secret version resource - to disable The arguments in + Version resource - Numeric secret version to disable. 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 version on the command line with a fully + ◆ provide the argument VERSION on the command line with a fully specified name; ◆ provide the argument --project on the command line; - ◆ set the property core/project. This resource can be one of the - following types: [version, regional version]. + ◆ set the property core/project. This must be specified. VERSION - ID of the global or regional secret version or fully qualified - identifier for the global or regional secret version. + ID of the version or fully qualified identifier for the version. To set the version attribute: - ▸ provide the argument version on the command line. + ▸ provide the argument VERSION on the command line. This positional argument must be specified if any of the other arguments in this group are specified. - --location=LOCATION - [EXPERIMENTAL] The location of the global or regional secret version. - - To set the location attribute: - ▸ provide the argument version on the command line with a fully - specified name; - ▸ provide the argument --location on the command line. Must be - specified for resource of type [regional version]. - --secret=SECRET - The secret of the global or regional secret version. + The secret of the version. To set the secret attribute: - ▸ provide the argument version on the command line with a fully + ▸ provide the argument VERSION on the command line with a fully specified name; ▸ provide the argument --secret on the command line. diff --git a/gcloud/beta/secrets/versions/enable b/gcloud/beta/secrets/versions/enable index ccdd6e2b5..7742f3b82 100644 --- a/gcloud/beta/secrets/versions/enable +++ b/gcloud/beta/secrets/versions/enable @@ -3,9 +3,8 @@ NAME secret SYNOPSIS - gcloud beta secrets versions enable - (VERSION : --location=LOCATION --secret=SECRET) [--etag=ETAG] - [GCLOUD_WIDE_FLAG ...] + gcloud beta secrets versions enable (VERSION : --secret=SECRET) + [--etag=ETAG] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) Enable the version of the provided secret. It can be disabled with @@ -22,44 +21,33 @@ EXAMPLES --etag=\"123\" POSITIONAL ARGUMENTS - Global or regional secret version resource - to enable 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. + Version resource - Numeric secret version to enable. 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 version on the command line with a fully + ◆ provide the argument VERSION on the command line with a fully specified name; ◆ provide the argument --project on the command line; - ◆ set the property core/project. This resource can be one of the - following types: [version, regional version]. + ◆ set the property core/project. This must be specified. VERSION - ID of the global or regional secret version or fully qualified - identifier for the global or regional secret version. + ID of the version or fully qualified identifier for the version. To set the version attribute: - ▸ provide the argument version on the command line. + ▸ provide the argument VERSION on the command line. This positional argument must be specified if any of the other arguments in this group are specified. - --location=LOCATION - [EXPERIMENTAL] The location of the global or regional secret version. - - To set the location attribute: - ▸ provide the argument version on the command line with a fully - specified name; - ▸ provide the argument --location on the command line. Must be - specified for resource of type [regional version]. - --secret=SECRET - The secret of the global or regional secret version. + The secret of the version. To set the secret attribute: - ▸ provide the argument version on the command line with a fully + ▸ provide the argument VERSION on the command line with a fully specified name; ▸ provide the argument --secret on the command line. diff --git a/gcloud/beta/secrets/versions/list b/gcloud/beta/secrets/versions/list index db716ea87..f5bb6b6eb 100644 --- a/gcloud/beta/secrets/versions/list +++ b/gcloud/beta/secrets/versions/list @@ -2,10 +2,9 @@ NAME gcloud beta secrets versions list - list all versions for a secret SYNOPSIS - gcloud beta secrets versions list (SECRET : --location=LOCATION) - [--filter=EXPRESSION] [--limit=LIMIT] - [--page-size=PAGE_SIZE; default=100] [--sort-by=[FIELD,...]] [--uri] - [GCLOUD_WIDE_FLAG ...] + gcloud beta secrets versions list SECRET [--filter=EXPRESSION] + [--limit=LIMIT] [--page-size=PAGE_SIZE; default=100] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) List all versions and their status (For example: @@ -17,38 +16,23 @@ EXAMPLES $ gcloud beta secrets versions list my-secret POSITIONAL ARGUMENTS - Global or regional secret resource - from which to list versions 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. + Secret resource - The secret from which to list versions. This represents + a Cloud resource. (NOTE) Some attributes are not given arguments in this + group but can be set in other ways. To set the project attribute: - ◆ provide the argument secret on the command line with a fully + ◆ provide the argument SECRET on the command line with a fully specified name; ◆ provide the argument --project on the command line; - ◆ set the property core/project. This resource can be one of the - following types: [secret, regional secret]. + ◆ set the property core/project. This must be specified. SECRET - ID of the global or regional secret or fully qualified identifier for - the global or regional secret. + ID of the secret or fully qualified identifier for the secret. To set the secret attribute: - ▸ provide the argument secret on the command line. - - This positional argument must be specified if any of the other - arguments in this group are specified. - - --location=LOCATION - [EXPERIMENTAL] The location of the global or regional secret. - - To set the location attribute: - ▸ provide the argument secret on the command line with a fully - specified name; - ▸ provide the argument --location on the command line. Must be - specified for resource of type [regional secret]. + ▸ provide the argument SECRET on the command line. LIST COMMAND FLAGS --filter=EXPRESSION diff --git a/gcloud/beta/spanner/operations/help b/gcloud/beta/spanner/operations/help index 6d4ebcbd5..15b71e09f 100644 --- a/gcloud/beta/spanner/operations/help +++ b/gcloud/beta/spanner/operations/help @@ -22,8 +22,7 @@ COMMANDS (BETA) Describe a Cloud Spanner operation. list - (BETA) List the Cloud Spanner operations on the given instance or - database or instance configuration. + (BETA) List the Cloud Spanner operations. NOTES This command is currently in beta and might change without notice. These diff --git a/gcloud/beta/spanner/operations/list b/gcloud/beta/spanner/operations/list index 536526e65..2ed6b9ae0 100644 --- a/gcloud/beta/spanner/operations/list +++ b/gcloud/beta/spanner/operations/list @@ -1,6 +1,5 @@ NAME - gcloud beta spanner operations list - list the Cloud Spanner operations on - the given instance or database or instance configuration + gcloud beta spanner operations list - list the Cloud Spanner operations SYNOPSIS gcloud beta spanner operations list @@ -10,8 +9,7 @@ SYNOPSIS [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) List the Cloud Spanner operations on the given instance or database - or instance configuration. + (BETA) List the Cloud Spanner operations. EXAMPLES To list Cloud Spanner instance operations for an instance, run: diff --git a/gcloud/beta/sql/instances/create b/gcloud/beta/sql/instances/create index c33b71766..1311157d6 100644 --- a/gcloud/beta/sql/instances/create +++ b/gcloud/beta/sql/instances/create @@ -21,8 +21,8 @@ SYNOPSIS [--deny-maintenance-period-start-date=DENY_MAINTENANCE_PERIOD_START_DATE] [--deny-maintenance-period-time=DENY_MAINTENANCE_PERIOD_TIME] [--edition=EDITION] [--enable-bin-log] [--enable-data-cache] - [--enable-google-private-path] [--enable-password-policy] - [--enable-point-in-time-recovery] + [--[no-]enable-google-ml-integration] [--enable-google-private-path] + [--enable-password-policy] [--enable-point-in-time-recovery] [--failover-replica-name=FAILOVER_REPLICA_NAME] [--[no-]insights-config-query-insights-enabled] [--insights-config-query-plans-per-minute=INSIGHTS_CONFIG_QUERY_PLANS_PER_MINUTE] @@ -239,6 +239,11 @@ FLAGS Enable use of data cache for accelerated read performance. This flag is only available for Enterprise_Plus edition instances. + --[no-]enable-google-ml-integration + Enable Vertex AI integration for Google Cloud SQL. Currently, only + PostgreSQL is supported. Use --enable-google-ml-integration to enable + and --no-enable-google-ml-integration to disable. + --enable-google-private-path Enable a private path for Google Cloud services. This flag specifies whether the instance is accessible to internal Google Cloud services diff --git a/gcloud/beta/sql/instances/patch b/gcloud/beta/sql/instances/patch index b47e8b3ef..344eb0643 100644 --- a/gcloud/beta/sql/instances/patch +++ b/gcloud/beta/sql/instances/patch @@ -18,6 +18,7 @@ SYNOPSIS [--deny-maintenance-period-time=DENY_MAINTENANCE_PERIOD_TIME] [--diff] [--edition=EDITION] [--[no-]enable-bin-log] [--enable-data-cache] [--[no-]enable-database-replication] + [--[no-]enable-google-ml-integration] [--[no-]enable-google-private-path] [--enable-password-policy] [--enable-point-in-time-recovery] [--follow-gae-app=FOLLOW_GAE_APP] [--[no-]insights-config-query-insights-enabled] @@ -183,6 +184,11 @@ FLAGS --enable-database-replication to enable and --no-enable-database-replication to disable. + --[no-]enable-google-ml-integration + Enable Vertex AI integration for Google Cloud SQL. Currently, only + PostgreSQL is supported. Use --enable-google-ml-integration to enable + and --no-enable-google-ml-integration to disable. + --[no-]enable-google-private-path Enable a private path for Google Cloud services. This flag specifies whether the instance is accessible to internal Google Cloud services diff --git a/gcloud/beta/workstations/configs/create b/gcloud/beta/workstations/configs/create index 5b642995b..892d7b53c 100644 --- a/gcloud/beta/workstations/configs/create +++ b/gcloud/beta/workstations/configs/create @@ -5,6 +5,7 @@ NAME SYNOPSIS gcloud beta workstations configs create (CONFIG : --cluster=CLUSTER --region=REGION) [--async] + [--boost-config=[BOOST_CONFIG,...]] [--boot-disk-size=BOOT_DISK_SIZE; default=50] [--container-args=[CONTAINER_ARGS,...]] [--container-command=[CONTAINER_COMMAND,...]] @@ -104,6 +105,43 @@ FLAGS Return immediately, without waiting for the operation in progress to complete. + --boost-config=[BOOST_CONFIG,...] + Boost Configuration(s) that workstations running with this + configuration can boost up to. This includes id (required), + machine-type, accelerator-type, and accelerator-count. + + Example: + + $ gcloud beta workstations configs create \ + --boost-config=id=boost1,machine-type=n1-standard-4,\ + accelerator-type=nvidia-tesla-t4,accelerator-count=1 + + Sets boost_config value. + + accelerator-count + Sets accelerator-count value. + + accelerator-type + Sets accelerator-type value. + + id + Required, Sets id value. + + machine-type + Sets machine-type value. + + Shorthand Example: + + --boost-config=accelerator-count=int,accelerator-type=string,id=string,machine-type=string + + JSON Example: + + --boost-config='{"accelerator-count": int, "accelerator-type": "string", "id": "string", "machine-type": "string"}' + + File Example: + + --boost-config=path_to_file.(yaml|json) + --boot-disk-size=BOOT_DISK_SIZE; default=50 Size of the boot disk in GB. @@ -281,6 +319,8 @@ FLAGS CLion codeoss Code OSS + codeoss-cuda + Code OSS + CUDA toolkit goland GoLand intellij diff --git a/gcloud/beta/workstations/configs/update b/gcloud/beta/workstations/configs/update index 7ba23e610..bf3a8f609 100644 --- a/gcloud/beta/workstations/configs/update +++ b/gcloud/beta/workstations/configs/update @@ -5,7 +5,7 @@ NAME SYNOPSIS gcloud beta workstations configs update (CONFIG : --cluster=CLUSTER --region=REGION) [--async] - [--boot-disk-size=BOOT_DISK_SIZE] + [--boost-config=[BOOST_CONFIG,...]] [--boot-disk-size=BOOT_DISK_SIZE] [--container-args=[CONTAINER_ARGS,...]] [--container-command=[CONTAINER_COMMAND,...]] [--container-env=[CONTAINER_ENV,...]] @@ -92,6 +92,43 @@ FLAGS Return immediately, without waiting for the operation in progress to complete. + --boost-config=[BOOST_CONFIG,...] + Boost Configuration(s) that workstations running with this + configuration can boost up to. This includes id (required), + machine-type, accelerator-type, and accelerator-count. + + Example: + + $ gcloud beta workstations configs update \ + --boost-config=id=boost1,machine-type=n1-standard-4,\ + accelerator-type=nvidia-tesla-t4,accelerator-count=1 + + Sets boost_config value. + + accelerator-count + Sets accelerator-count value. + + accelerator-type + Sets accelerator-type value. + + id + Required, Sets id value. + + machine-type + Sets machine-type value. + + Shorthand Example: + + --boost-config=accelerator-count=int,accelerator-type=string,id=string,machine-type=string + + JSON Example: + + --boost-config='{"accelerator-count": int, "accelerator-type": "string", "id": "string", "machine-type": "string"}' + + File Example: + + --boost-config=path_to_file.(yaml|json) + --boot-disk-size=BOOT_DISK_SIZE Size of the boot disk in GB. @@ -230,6 +267,8 @@ FLAGS CLion codeoss Code OSS + codeoss-cuda + Code OSS + CUDA toolkit goland GoLand intellij diff --git a/gcloud/beta/workstations/start b/gcloud/beta/workstations/start index 512fa2150..b61645598 100644 --- a/gcloud/beta/workstations/start +++ b/gcloud/beta/workstations/start @@ -4,7 +4,7 @@ NAME SYNOPSIS gcloud beta workstations start (WORKSTATION : --cluster=CLUSTER --config=CONFIG --region=REGION) - [--async] [GCLOUD_WIDE_FLAG ...] + [--async] [--boost=BOOST] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) Start a workstation. @@ -70,6 +70,13 @@ FLAGS Return immediately, without waiting for the operation in progress to complete. + --boost=BOOST + Id of a boost configuration to start a workstations with. + + Example: + + $ gcloud beta workstations start --boost=boost1 + 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/bigtable/authorized-views/add-iam-policy-binding b/gcloud/bigtable/authorized-views/add-iam-policy-binding new file mode 100644 index 000000000..a9d8d80f9 --- /dev/null +++ b/gcloud/bigtable/authorized-views/add-iam-policy-binding @@ -0,0 +1,158 @@ +NAME + gcloud bigtable authorized-views add-iam-policy-binding - add an IAM policy + binding to a Cloud Bigtable authorized view + +SYNOPSIS + gcloud bigtable authorized-views add-iam-policy-binding + (AUTHORIZED_VIEW : --instance=INSTANCE --table=TABLE) + --member=PRINCIPAL --role=ROLE + [--condition=[KEY=VALUE,...] + | --condition-from-file=CONDITION_FROM_FILE] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Add an IAM policy binding to a Cloud Bigtable authorized view. One binding + consists of a member, a role, and an optional condition. + +EXAMPLES + To add an IAM policy binding for the role of 'roles/editor' for the user + 'test-user@gmail.com' with authorized view 'my-authorized-view' in instance + 'my-instance' and table 'my-table', run: + + $ gcloud bigtable authorized-views add-iam-policy-binding \ + my-authorized-view --instance='my-instance' --table='my-table' \ + --member='user:test-user@gmail.com' --role='roles/editor' + + To add an IAM policy binding which expires at the end of the year 2020 for + the role of 'roles/bigtable.admin' and the user 'test-user@gmail.com' with + authorized view 'my-authorized-view' in instance 'my-instance' and table + 'my-table', run: + + $ gcloud bigtable authorized-views add-iam-policy-binding \ + my-authorized-view --instance='my-instance' --table='my-table' \ + --member='user:test-user@gmail.com' \ + --role='roles/bigtable.admin' \ + --condition='expression=request.time < + timestamp("2021-01-01T00:00:00Z"),title=expires_end_of_2020,descrip\ + tion=Expires at midnight on 2020-12-31' + + See https://cloud.google.com/iam/docs/managing-policies for details of + policy role and member types. + +POSITIONAL ARGUMENTS + Authorized view resource - Cloud Bigtable authorized view to add the IAM + policy binding to. 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 authorized_view 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. + + AUTHORIZED_VIEW + ID of the authorized-view or fully qualified identifier for the + authorized-view. + + To set the authorized_view attribute: + ▸ provide the argument authorized_view on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --instance=INSTANCE + Name of the Cloud Bigtable instance. + + To set the instance attribute: + ▸ provide the argument authorized_view on the command line with a + fully specified name; + ▸ provide the argument --instance on the command line. + + --table=TABLE + Name of the Cloud Bigtable table. + + To set the table attribute: + ▸ provide the argument authorized_view on the command line with a + fully specified name; + ▸ provide the argument --table on the command line. + +REQUIRED FLAGS + --member=PRINCIPAL + The principal to add the binding for. Should be of the form + user|group|serviceAccount:email or domain:domain. + + Examples: user:test-user@gmail.com, group:admins@example.com, + serviceAccount:test123@example.domain.com, or + domain:example.domain.com. + + Some resources also accept the following special values: + ◆ allUsers - Special identifier that represents anyone who is on the + internet, with or without a Google account. + ◆ allAuthenticatedUsers - Special identifier that represents anyone + who is authenticated with a Google account or a service account. + + --role=ROLE + Role name to assign to the principal. The role name is the complete + path of a predefined role, such as roles/logging.viewer, or the role ID + for a custom role, such as + organizations/{ORGANIZATION_ID}/roles/logging.viewer. + +OPTIONAL FLAGS + At most one of these can be specified: + + --condition=[KEY=VALUE,...] + A condition to include in the binding. When the condition is + explicitly specified as None (--condition=None), a binding without a + condition is added. When the condition is specified and is not None, + --role cannot be a basic role. Basic roles are roles/editor, + roles/owner, and roles/viewer. For more on conditions, refer to the + conditions overview guide: + https://cloud.google.com/iam/docs/conditions-overview + + When using the --condition flag, include the following key-value + pairs: + + expression + (Required) Condition expression that evaluates to True or False. + This uses a subset of Common Expression Language syntax. + + If the condition expression includes a comma, use a different + delimiter to separate the key-value pairs. Specify the delimiter + before listing the key-value pairs. For example, to specify a + colon (:) as the delimiter, do the following: + --condition=^:^title=TITLE:expression=EXPRESSION. For more + information, see + https://cloud.google.com/sdk/gcloud/reference/topic/escaping. + + title + (Required) A short string describing the purpose of the + expression. + + description + (Optional) Additional description for the expression. + + --condition-from-file=CONDITION_FROM_FILE + Path to a local JSON or YAML file that defines the condition. To see + available fields, see the help for --condition. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the bigtableadmin/v2 API. The full documentation for this + API can be found at: https://cloud.google.com/bigtable/ + +NOTES + These variants are also available: + + $ gcloud alpha bigtable authorized-views add-iam-policy-binding + + $ gcloud beta bigtable authorized-views add-iam-policy-binding + diff --git a/gcloud/bigtable/authorized-views/create b/gcloud/bigtable/authorized-views/create new file mode 100644 index 000000000..6357a5dd4 --- /dev/null +++ b/gcloud/bigtable/authorized-views/create @@ -0,0 +1,112 @@ +NAME + gcloud bigtable authorized-views create - create a new Cloud Bigtable + authorized view + +SYNOPSIS + gcloud bigtable authorized-views create + (AUTHORIZED_VIEW : --instance=INSTANCE --table=TABLE) [--async] + [--definition-file=DEFINITION_FILE] [--pre-encoded] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Create a new Cloud Bigtable authorized view. + +EXAMPLES + To create an authorized view 'my-authorized-view' in instance 'my-instance' + and table 'my-table', using the definition file 'authorized_view.json': + + $ gcloud bigtable authorized-views create my-authorized-view \ + --instance=test-instance --table=test-table \ + --definition-file=authorized_view.json + + To create an authorized view 'my-authorized-view' in instance 'my-instance' + and table 'my-table', using the pre-encoded definition file + 'authorized_view_pre_encoded.json': + + $ gcloud bigtable authorized-views create my-authorized-view \ + --instance=test-instance --table=test-table \ + --definition-file=authorized_view_pre_encoded.json --pre-encoded + +POSITIONAL ARGUMENTS + Authorized view resource - Cloud Bigtable authorized view to create. 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 authorized_view 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. + + AUTHORIZED_VIEW + ID of the authorized-view or fully qualified identifier for the + authorized-view. + + To set the authorized_view attribute: + ▸ provide the argument authorized_view on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --instance=INSTANCE + Name of the Cloud Bigtable instance. + + To set the instance attribute: + ▸ provide the argument authorized_view on the command line with a + fully specified name; + ▸ provide the argument --instance on the command line. + + --table=TABLE + Name of the Cloud Bigtable table. + + To set the table attribute: + ▸ provide the argument authorized_view on the command line with a + fully specified name; + ▸ provide the argument --table on the command line. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --definition-file=DEFINITION_FILE + Path to a JSON or YAML file containing a valid authorized view + protobuf. + + The 'name' field is ignored. The name is deduced from the other command + line arguments. + + Example: { "subsetView": { "rowPrefixes": ["store1#"], "familySubsets": + { "column_family_name": { "qualifiers":["address"], + "qualifierPrefixes":["tel"] } } }, "deletionProtection": true } + + --pre-encoded + By default, Base64 encoding is applied to all binary fields + ("rowPrefixes", "qualifiers" and "qualifierPrefixes") in the JSON or + YAML definition file. + + Use this to indicate that all binary fields are already Base64-encoded + and should be used directly. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the bigtableadmin/v2 API. The full documentation for this + API can be found at: https://cloud.google.com/bigtable/ + +NOTES + These variants are also available: + + $ gcloud alpha bigtable authorized-views create + + $ gcloud beta bigtable authorized-views create + diff --git a/gcloud/bigtable/authorized-views/delete b/gcloud/bigtable/authorized-views/delete new file mode 100644 index 000000000..11d8b9a8c --- /dev/null +++ b/gcloud/bigtable/authorized-views/delete @@ -0,0 +1,78 @@ +NAME + gcloud bigtable authorized-views delete - delete a Cloud Bigtable + authorized view + +SYNOPSIS + gcloud bigtable authorized-views delete + (AUTHORIZED_VIEW : --instance=INSTANCE --table=TABLE) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Delete new Cloud Bigtable authorized view. + +EXAMPLES + To delete the authorized view 'my-authorized-view' in instance + 'my-instance' and table 'my-table': + + $ gcloud bigtable authorized-views delete my-authorized-view \ + --instance=test-instance --table=test-table + +POSITIONAL ARGUMENTS + Authorized view resource - Cloud Bigtable authorized view to delete. 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 authorized_view 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. + + AUTHORIZED_VIEW + ID of the authorized-view or fully qualified identifier for the + authorized-view. + + To set the authorized_view attribute: + ▸ provide the argument authorized_view on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --instance=INSTANCE + Name of the Cloud Bigtable instance. + + To set the instance attribute: + ▸ provide the argument authorized_view on the command line with a + fully specified name; + ▸ provide the argument --instance on the command line. + + --table=TABLE + Name of the Cloud Bigtable table. + + To set the table attribute: + ▸ provide the argument authorized_view on the command line with a + fully specified name; + ▸ provide the argument --table on the command line. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the bigtableadmin/v2 API. The full documentation for this + API can be found at: https://cloud.google.com/bigtable/ + +NOTES + These variants are also available: + + $ gcloud alpha bigtable authorized-views delete + + $ gcloud beta bigtable authorized-views delete + diff --git a/gcloud/bigtable/authorized-views/describe b/gcloud/bigtable/authorized-views/describe new file mode 100644 index 000000000..5b4f3532c --- /dev/null +++ b/gcloud/bigtable/authorized-views/describe @@ -0,0 +1,78 @@ +NAME + gcloud bigtable authorized-views describe - describe a Cloud Bigtable + authorized view + +SYNOPSIS + gcloud bigtable authorized-views describe + (AUTHORIZED_VIEW : --instance=INSTANCE --table=TABLE) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Describe a Cloud Bigtable authorized view. + +EXAMPLES + To describe the authorized view 'my-authorized-view' in instance + 'my-instance' and table 'my-table': + + $ gcloud bigtable authorized-views describe my-authorized-view \ + --instance=test-instance --table=test-table + +POSITIONAL ARGUMENTS + Authorized view resource - Cloud Bigtable authorized view to describe. 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 authorized_view 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. + + AUTHORIZED_VIEW + ID of the authorized-view or fully qualified identifier for the + authorized-view. + + To set the authorized_view attribute: + ▸ provide the argument authorized_view on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --instance=INSTANCE + Name of the Cloud Bigtable instance. + + To set the instance attribute: + ▸ provide the argument authorized_view on the command line with a + fully specified name; + ▸ provide the argument --instance on the command line. + + --table=TABLE + Name of the Cloud Bigtable table. + + To set the table attribute: + ▸ provide the argument authorized_view on the command line with a + fully specified name; + ▸ provide the argument --table on the command line. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the bigtableadmin/v2 API. The full documentation for this + API can be found at: https://cloud.google.com/bigtable/ + +NOTES + These variants are also available: + + $ gcloud alpha bigtable authorized-views describe + + $ gcloud beta bigtable authorized-views describe + diff --git a/gcloud/bigtable/authorized-views/get-iam-policy b/gcloud/bigtable/authorized-views/get-iam-policy new file mode 100644 index 000000000..d15bf1052 --- /dev/null +++ b/gcloud/bigtable/authorized-views/get-iam-policy @@ -0,0 +1,108 @@ +NAME + gcloud bigtable authorized-views get-iam-policy - get an IAM policy on a + Cloud Bigtable authorized view + +SYNOPSIS + gcloud bigtable authorized-views get-iam-policy + (AUTHORIZED_VIEW : --instance=INSTANCE --table=TABLE) + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Get an IAM policy on a Cloud Bigtable authorized view. + +EXAMPLES + To get the IAM policy on the authorized view 'my-authorized-view' in + instance 'my-instance' and table 'my-table', run: + + $ gcloud bigtable authorized-views get-iam-policy \ + my-authorized-view --instance='my-instance' --table='my-table' + + See https://cloud.google.com/iam/docs/managing-policies for more + information. + +POSITIONAL ARGUMENTS + Authorized view resource - Cloud Bigtable authorized view to get the IAM + policy for. 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 authorized_view 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. + + AUTHORIZED_VIEW + ID of the authorized-view or fully qualified identifier for the + authorized-view. + + To set the authorized_view attribute: + ▸ provide the argument authorized_view on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --instance=INSTANCE + Name of the Cloud Bigtable instance. + + To set the instance attribute: + ▸ provide the argument authorized_view on the command line with a + fully specified name; + ▸ provide the argument --instance on the command line. + + --table=TABLE + Name of the Cloud Bigtable table. + + To set the table attribute: + ▸ provide the argument authorized_view on the command line with a + fully specified name; + ▸ provide the argument --table on the command line. + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the bigtableadmin/v2 API. The full documentation for this + API can be found at: https://cloud.google.com/bigtable/ + +NOTES + These variants are also available: + + $ gcloud alpha bigtable authorized-views get-iam-policy + + $ gcloud beta bigtable authorized-views get-iam-policy + diff --git a/gcloud/bigtable/authorized-views/help b/gcloud/bigtable/authorized-views/help new file mode 100644 index 000000000..5d4d9a104 --- /dev/null +++ b/gcloud/bigtable/authorized-views/help @@ -0,0 +1,51 @@ +NAME + gcloud bigtable authorized-views - manage Cloud Bigtable Authorized Views + +SYNOPSIS + gcloud bigtable authorized-views COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Manage Cloud Bigtable Authorized Views. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + add-iam-policy-binding + Add an IAM policy binding to a Cloud Bigtable authorized view. + + create + Create a new Cloud Bigtable authorized view. + + delete + Delete a Cloud Bigtable authorized view. + + describe + Describe a Cloud Bigtable authorized view. + + get-iam-policy + Get an IAM policy on a Cloud Bigtable authorized view. + + list + List all authorized views of a Cloud Bigtable table. + + remove-iam-policy-binding + Remove an IAM policy binding from a Cloud Bigtable authorized view. + + set-iam-policy + Set an IAM policy on a Cloud Bigtable authorized view. + + update + Update an existing Cloud Bigtable authorized view. + +NOTES + These variants are also available: + + $ gcloud alpha bigtable authorized-views + + $ gcloud beta bigtable authorized-views + diff --git a/gcloud/bigtable/authorized-views/list b/gcloud/bigtable/authorized-views/list new file mode 100644 index 000000000..7d207d381 --- /dev/null +++ b/gcloud/bigtable/authorized-views/list @@ -0,0 +1,101 @@ +NAME + gcloud bigtable authorized-views list - list all authorized views of a + Cloud Bigtable table + +SYNOPSIS + gcloud bigtable authorized-views list (--table=TABLE : --instance=INSTANCE) + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + List all authorized views of a Cloud Bigtable table. + +EXAMPLES + To list the authorized views in instance 'my-instance' and table + 'my-table': + + $ gcloud bigtable authorized-views list --instance=test-instance \ + --table=test-table + +REQUIRED FLAGS + Table resource - Cloud Bigtable table for which to list all authorized + views. 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 --table 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. + + --table=TABLE + ID of the table or fully qualified identifier for the table. + + To set the table attribute: + ▸ provide the argument --table on the command line. + + This flag argument must be specified if any of the other arguments in + this group are specified. + + --instance=INSTANCE + Name of the Cloud Bigtable instance. + + To set the instance attribute: + ▸ provide the argument --table on the command line with a fully + specified name; + ▸ provide the argument --instance on the command line. + +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. + +API REFERENCE + This command uses the bigtableadmin/v2 API. The full documentation for this + API can be found at: https://cloud.google.com/bigtable/ + +NOTES + These variants are also available: + + $ gcloud alpha bigtable authorized-views list + + $ gcloud beta bigtable authorized-views list + diff --git a/gcloud/bigtable/authorized-views/remove-iam-policy-binding b/gcloud/bigtable/authorized-views/remove-iam-policy-binding new file mode 100644 index 000000000..a2d62dbdc --- /dev/null +++ b/gcloud/bigtable/authorized-views/remove-iam-policy-binding @@ -0,0 +1,163 @@ +NAME + gcloud bigtable authorized-views remove-iam-policy-binding - remove an IAM + policy binding from a Cloud Bigtable authorized view + +SYNOPSIS + gcloud bigtable authorized-views remove-iam-policy-binding + (AUTHORIZED_VIEW : --instance=INSTANCE --table=TABLE) + --member=PRINCIPAL --role=ROLE + [--all | --condition=[KEY=VALUE,...] + | --condition-from-file=CONDITION_FROM_FILE] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Remove an IAM policy binding from a Cloud Bigtable authorized view. One + binding consists of a member, a role, and an optional condition. + +EXAMPLES + To remove an IAM policy binding for the role of 'roles/editor' for the user + 'test-user@gmail.com' with authorized view 'my-authorized-view' in instance + 'my-instance' and table 'my-table', run: + + $ gcloud bigtable authorized-views remove-iam-policy-binding \ + my-authorized-view --instance='my-instance' --table='my-table' \ + --member='user:test-user@gmail.com' --role='roles/editor' + + To remove an IAM policy binding which expires at the end of the year 2020 + for the role of 'roles/bigtable.admin' and the user 'test-user@gmail.com' + with authorized view 'my-authorized-view' in instance 'my-instance' and + cluster 'my-cluster', run: + + $ gcloud bigtable authorized-views remove-iam-policy-binding \ + my-authorized-view --instance='my-instance' --table='my-table' \ + --member='user:test-user@gmail.com' \ + --role='roles/bigtable.admin' \ + --condition='expression=request.time < + timestamp("2021-01-01T00:00:00Z"),title=expires_end_of_2020,descrip\ + tion=Expires at midnight on 2020-12-31' + + See https://cloud.google.com/iam/docs/managing-policies for details of + policy role and member types. + +POSITIONAL ARGUMENTS + Authorized view resource - Cloud Bigtable authorized view to remove the + IAM policy binding from. The arguments in this group can be used to + specify the attributes of this resource. (NOTE) Some attributes are not + given arguments in this group but can be set in other ways. + + To set the project attribute: + ◆ provide the argument authorized_view 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. + + AUTHORIZED_VIEW + ID of the authorized-view or fully qualified identifier for the + authorized-view. + + To set the authorized_view attribute: + ▸ provide the argument authorized_view on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --instance=INSTANCE + Name of the Cloud Bigtable instance. + + To set the instance attribute: + ▸ provide the argument authorized_view on the command line with a + fully specified name; + ▸ provide the argument --instance on the command line. + + --table=TABLE + Name of the Cloud Bigtable table. + + To set the table attribute: + ▸ provide the argument authorized_view on the command line with a + fully specified name; + ▸ provide the argument --table on the command line. + +REQUIRED FLAGS + --member=PRINCIPAL + The principal to remove the binding for. Should be of the form + user|group|serviceAccount:email or domain:domain. + + Examples: user:test-user@gmail.com, group:admins@example.com, + serviceAccount:test123@example.domain.com, or + domain:example.domain.com. + + Deleted principals have an additional deleted: prefix and a ?uid=UID + suffix, where UID is a unique identifier for the principal. Example: + deleted:user:test-user@gmail.com?uid=123456789012345678901. + + Some resources also accept the following special values: + ◆ allUsers - Special identifier that represents anyone who is on the + internet, with or without a Google account. + ◆ allAuthenticatedUsers - Special identifier that represents anyone + who is authenticated with a Google account or a service account. + + --role=ROLE + The role to remove the principal from. + +OPTIONAL FLAGS + At most one of these can be specified: + + --all + Remove all bindings with this role and principal, irrespective of any + conditions. + + --condition=[KEY=VALUE,...] + The condition of the binding that you want to remove. When the + condition is explicitly specified as None (--condition=None), a + binding without a condition is removed. Otherwise, only a binding + with a condition that exactly matches the specified condition + (including the optional description) is removed. For more on + conditions, refer to the conditions overview guide: + https://cloud.google.com/iam/docs/conditions-overview + + When using the --condition flag, include the following key-value + pairs: + + expression + (Required) Condition expression that evaluates to True or False. + This uses a subset of Common Expression Language syntax. + + If the condition expression includes a comma, use a different + delimiter to separate the key-value pairs. Specify the delimiter + before listing the key-value pairs. For example, to specify a + colon (:) as the delimiter, do the following: + --condition=^:^title=TITLE:expression=EXPRESSION. For more + information, see + https://cloud.google.com/sdk/gcloud/reference/topic/escaping. + + title + (Required) A short string describing the purpose of the + expression. + + description + (Optional) Additional description for the expression. + + --condition-from-file=CONDITION_FROM_FILE + Path to a local JSON or YAML file that defines the condition. To see + available fields, see the help for --condition. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the bigtableadmin/v2 API. The full documentation for this + API can be found at: https://cloud.google.com/bigtable/ + +NOTES + These variants are also available: + + $ gcloud alpha bigtable authorized-views remove-iam-policy-binding + + $ gcloud beta bigtable authorized-views remove-iam-policy-binding + diff --git a/gcloud/bigtable/authorized-views/set-iam-policy b/gcloud/bigtable/authorized-views/set-iam-policy new file mode 100644 index 000000000..abcdb7d28 --- /dev/null +++ b/gcloud/bigtable/authorized-views/set-iam-policy @@ -0,0 +1,89 @@ +NAME + gcloud bigtable authorized-views set-iam-policy - set an IAM policy on a + Cloud Bigtable authorized view + +SYNOPSIS + gcloud bigtable authorized-views set-iam-policy + (AUTHORIZED_VIEW : --instance=INSTANCE --table=TABLE) POLICY_FILE + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Set an IAM policy on a Cloud Bigtable authorized view. + +EXAMPLES + To set the IAM policy from file 'my-policy' on the authorized view + 'my-authorized-view' in instance 'my-instance' and table 'my-table', run: + + $ gcloud bigtable authorized-views set-iam-policy \ + my-authorized-view --instance='my-instance' --table='my-table' \ + my-policy + + See https://cloud.google.com/iam/docs/managing-policies for more + information. + +POSITIONAL ARGUMENTS + Authorized view resource - Cloud Bigtable authorized view to set the IAM + policy 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 authorized_view 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. + + AUTHORIZED_VIEW + ID of the authorized-view or fully qualified identifier for the + authorized-view. + + To set the authorized_view attribute: + ▸ provide the argument authorized_view on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --instance=INSTANCE + Name of the Cloud Bigtable instance. + + To set the instance attribute: + ▸ provide the argument authorized_view on the command line with a + fully specified name; + ▸ provide the argument --instance on the command line. + + --table=TABLE + Name of the Cloud Bigtable table. + + To set the table attribute: + ▸ provide the argument authorized_view on the command line with a + fully specified name; + ▸ provide the argument --table on the command line. + + POLICY_FILE + Path to a local JSON or YAML formatted file containing a valid policy. + + The output of the get-iam-policy command is a valid file, as is any + JSON or YAML file conforming to the structure of a Policy + (https://cloud.google.com/iam/reference/rest/v1/Policy). + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the bigtableadmin/v2 API. The full documentation for this + API can be found at: https://cloud.google.com/bigtable/ + +NOTES + These variants are also available: + + $ gcloud alpha bigtable authorized-views set-iam-policy + + $ gcloud beta bigtable authorized-views set-iam-policy + diff --git a/gcloud/bigtable/authorized-views/update b/gcloud/bigtable/authorized-views/update new file mode 100644 index 000000000..83f51c0b3 --- /dev/null +++ b/gcloud/bigtable/authorized-views/update @@ -0,0 +1,129 @@ +NAME + gcloud bigtable authorized-views update - update an existing Cloud Bigtable + authorized view + +SYNOPSIS + gcloud bigtable authorized-views update + (AUTHORIZED_VIEW : --instance=INSTANCE --table=TABLE) [--async] + [--definition-file=DEFINITION_FILE] [--ignore-warnings] + [--no-interactive] [--pre-encoded] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Update an existing Cloud Bigtable authorized view. + +EXAMPLES + To update the authorized view 'my-authorized-view' in instance + 'my-instance' and table 'my-table', using the definition file + 'authorized_view.json': + + $ gcloud bigtable authorized-views update my-authorized-view \ + --instance=test-instance --table=test-table \ + --definition-file=authorized_view.json + + To update the authorized view 'my-authorized-view' in instance + 'my-instance' and table 'my-table', using the pre-encoded definition file + 'authorized_view_pre_encoded.json': + + $ gcloud bigtable authorized-views update my-authorized-view \ + --instance=test-instance --table=test-table \ + --definition-file=authorized_view_pre_encoded.json --pre-encoded + + To update the authorized view 'my-authorized-view' in instance + 'my-instance' and table 'my-table', using the definition file + 'authorized_view.json' and skip the prompt to proceed or cancel the update: + + $ gcloud bigtable authorized-views update my-authorized-view \ + --instance=test-instance --table=test-table \ + --definition-file=authorized_view.json --no-interactive + +POSITIONAL ARGUMENTS + Authorized view resource - Cloud Bigtable authorized view to update. 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 authorized_view 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. + + AUTHORIZED_VIEW + ID of the authorized-view or fully qualified identifier for the + authorized-view. + + To set the authorized_view attribute: + ▸ provide the argument authorized_view on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --instance=INSTANCE + Name of the Cloud Bigtable instance. + + To set the instance attribute: + ▸ provide the argument authorized_view on the command line with a + fully specified name; + ▸ provide the argument --instance on the command line. + + --table=TABLE + Name of the Cloud Bigtable table. + + To set the table attribute: + ▸ provide the argument authorized_view on the command line with a + fully specified name; + ▸ provide the argument --table on the command line. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --definition-file=DEFINITION_FILE + Path to a JSON or YAML file containing a valid authorized view + protobuf. + + The 'name' field is ignored. The name is deduced from the other command + line arguments. + + Example: { "subsetView": { "rowPrefixes": ["store1"], "familySubsets": + { "column_family_name": { "qualifiers":["address"], + "qualifierPrefixes":["tel"] } } }, "deletionProtection": true } + + --ignore-warnings + If true, changes that make the authorized view more restrictive are + allowed. + + --interactive + If provided, a diff is displayed with a prompt to proceed or cancel the + update. Enabled by default, use --no-interactive to disable. + + --pre-encoded + By default, Base64 encoding is applied to all binary fields + ("rowPrefixes", "qualifiers" and "qualifierPrefixes") in the JSON or + YAML definition file. + + Use this to indicate that all binary fields are already Base64-encoded + and should be used directly. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the bigtableadmin/v2 API. The full documentation for this + API can be found at: https://cloud.google.com/bigtable/ + +NOTES + These variants are also available: + + $ gcloud alpha bigtable authorized-views update + + $ gcloud beta bigtable authorized-views update + diff --git a/gcloud/bigtable/help b/gcloud/bigtable/help index 55c476941..4f57ae970 100644 --- a/gcloud/bigtable/help +++ b/gcloud/bigtable/help @@ -18,6 +18,9 @@ GROUPS app-profiles Manage Cloud Bigtable app profiles. + authorized-views + Manage Cloud Bigtable Authorized Views. + backups Manage Cloud Bigtable backups. diff --git a/gcloud/builds/submit b/gcloud/builds/submit index b306fb3b6..f09fb6cf9 100644 --- a/gcloud/builds/submit +++ b/gcloud/builds/submit @@ -9,8 +9,8 @@ SYNOPSIS [--git-source-dir=GIT_SOURCE_DIR] [--git-source-revision=GIT_SOURCE_REVISION] [--ignore-file=IGNORE_FILE] [--machine-type=MACHINE_TYPE] [--region=REGION] [--revision=REVISION] - [--substitutions=[KEY=VALUE,...]] [--suppress-logs] [--timeout=TIMEOUT] - [--worker-pool=WORKER_POOL] + [--service-account=SERVICE_ACCOUNT] [--substitutions=[KEY=VALUE,...]] + [--suppress-logs] [--timeout=TIMEOUT] [--worker-pool=WORKER_POOL] [--config=CONFIG; default="cloudbuild.yaml" | --pack=[builder=BUILDER],[env=ENV],[image=IMAGE] | --tag=TAG, -t TAG] [GCLOUD_WIDE_FLAG ...] @@ -161,6 +161,10 @@ FLAGS https://git-scm.com/docs/gitrevisions#_specifying_revisions. For information on git fetch, see https://git-scm.com/docs/git-fetch. + --service-account=SERVICE_ACCOUNT + The service account to use with this build. If unset, the default + service account will be used. + --substitutions=[KEY=VALUE,...] Parameters to be substituted in the build specification. diff --git a/gcloud/composer/environments/run b/gcloud/composer/environments/run index a5a862b3c..09fd65177 100644 --- a/gcloud/composer/environments/run +++ b/gcloud/composer/environments/run @@ -97,7 +97,7 @@ POSITIONAL ARGUMENTS [SUBCOMMAND_NESTED] Additional subcommand in case it is nested. The following is a list of allowed nested subcommands: - ◆ db: check + ◆ db: check, trim ◆ all other subcommands: all nested subcommands are allowed [-- CMD_ARGS ...] diff --git a/gcloud/composer/environments/update b/gcloud/composer/environments/update index e444bb323..445b19b17 100644 --- a/gcloud/composer/environments/update +++ b/gcloud/composer/environments/update @@ -9,6 +9,7 @@ SYNOPSIS | --enable-high-resilience | --enable-logs-in-cloud-logging-only | --environment-size=ENVIRONMENT_SIZE | --node-count=NODE_COUNT | --web-server-machine-type=WEB_SERVER_MACHINE_TYPE + | --clear-maintenance-window | --maintenance-window-end=MAINTENANCE_WINDOW_END --maintenance-window-recurrence=MAINTENANCE_WINDOW_RECURRENCE --maintenance-window-start=MAINTENANCE_WINDOW_START @@ -131,6 +132,10 @@ REQUIRED FLAGS At most one of these can be specified: + --clear-maintenance-window + Clears the maintenance window settings. Can be specified for + Composer 3 or greater. + Group of arguments for setting the maintenance window value. --maintenance-window-end=MAINTENANCE_WINDOW_END diff --git a/gcloud/compute/instances/bulk/create b/gcloud/compute/instances/bulk/create index 97f818bda..30b83595b 100644 --- a/gcloud/compute/instances/bulk/create +++ b/gcloud/compute/instances/bulk/create @@ -559,8 +559,9 @@ OPTIONAL FLAGS --network-interface=[PROPERTY=VALUE,...] Adds a network interface to the instance. Mutually exclusive with any - of these flags: --network, --network-tier, --subnet. This flag can be - repeated to specify multiple network interfaces. + of these flags: --network, --network-tier, --no-address, --subnet, + --stack-type. This flag can be repeated to specify multiple network + interfaces. network Specifies the network that the interface will be part of. If subnet @@ -580,6 +581,10 @@ OPTIONAL FLAGS Specifies the Network Interface Controller (NIC) type for the interface. NIC_TYPE must be one of: GVNIC, VIRTIO_NET. + no-address + If specified the interface will have no external IP. If not + specified instances will get ephemeral IPs. + queue-count Specifies the networking queue count for this interface. Both Rx and Tx queues will be set to this number. If it's not specified, a diff --git a/gcloud/compute/tpus/queued-resources/delete b/gcloud/compute/tpus/queued-resources/delete index 34802889c..735e1d5b3 100644 --- a/gcloud/compute/tpus/queued-resources/delete +++ b/gcloud/compute/tpus/queued-resources/delete @@ -13,11 +13,11 @@ DESCRIPTION $ gcloud compute tpus queued-resources list EXAMPLES - To delete a Queued Resource in zone us-central1-b and project my-project, - run: + To delete a Queued Resource with ID my-queued-resource in zone + us-central1-b and project my-project, run: - $ gcloud compute tpus queued-resources delete --zone=us-central1-b \ - --project=my-project + $ gcloud compute tpus queued-resources delete my-queued-resource \ + --zone=us-central1-b --project=my-project POSITIONAL ARGUMENTS Queued resource resource - The Queued Resource you want to delete. The diff --git a/gcloud/logging/sinks/create b/gcloud/logging/sinks/create index 36a7d033c..0a31051d4 100644 --- a/gcloud/logging/sinks/create +++ b/gcloud/logging/sinks/create @@ -7,7 +7,8 @@ SYNOPSIS [--description=DESCRIPTION] [--disabled] [--exclusion=[description=DESCRIPTION], [disabled=DISABLED],[filter=FILTER],[name=NAME]] [--include-children] - [--log-filter=LOG_FILTER] [--use-partitioned-tables] + [--intercept-children] [--log-filter=LOG_FILTER] + [--use-partitioned-tables] [--billing-account=BILLING_ACCOUNT_ID | --folder=FOLDER_ID | --organization=ORGANIZATION_ID | --project=PROJECT_ID] [GCLOUD_WIDE_FLAG ...] @@ -113,6 +114,10 @@ FLAGS Whether to export logs from all child projects and folders. Only applies to sinks for organizations and folders. + --intercept-children + Whether to intercept logs from all child projects and folders. Only + applies to sinks for organizations and folders. + --log-filter=LOG_FILTER A filter expression for the sink. If present, the filter specifies which log entries to export. diff --git a/gcloud/logging/sinks/list b/gcloud/logging/sinks/list index 1f69da408..533308cc4 100644 --- a/gcloud/logging/sinks/list +++ b/gcloud/logging/sinks/list @@ -2,7 +2,7 @@ NAME gcloud logging sinks list - list the defined sinks SYNOPSIS - gcloud logging sinks list + gcloud logging sinks list [--sink-filter=SINK_FILTER] [--billing-account=BILLING_ACCOUNT_ID | --folder=FOLDER_ID | --organization=ORGANIZATION_ID | --project=PROJECT_ID] [--filter=EXPRESSION] [--limit=LIMIT] [--sort-by=[FIELD,...]] @@ -17,6 +17,11 @@ EXAMPLES $ gcloud logging sinks list --limit=10 FLAGS + --sink-filter=SINK_FILTER + A filter expression passed to the Logging API to constrain the sinks + returned. For information on accepted values, see + https://cloud.google.com/logging/docs/reference/v2/rpc/google.logging.v2#listsinksrequest + At most one of these can be specified: --billing-account=BILLING_ACCOUNT_ID diff --git a/gcloud/logging/sinks/update b/gcloud/logging/sinks/update index 04eb55208..5105f4625 100644 --- a/gcloud/logging/sinks/update +++ b/gcloud/logging/sinks/update @@ -6,7 +6,8 @@ SYNOPSIS [--add-exclusion=[description=DESCRIPTION], [disabled=DISABLED],[filter=FILTER],[name=NAME]] [--clear-exclusions] [--custom-writer-identity=SERVICE_ACCOUNT_EMAIL] - [--description=DESCRIPTION] [--disabled] [--log-filter=LOG_FILTER] + [--description=DESCRIPTION] [--disabled] [--include-children] + [--intercept-children] [--log-filter=LOG_FILTER] [--remove-exclusions=[EXCLUSION ID,...]] [--update-exclusion=[description=DESCRIPTION], [disabled=DISABLED],[filter=FILTER],[name=NAME]] @@ -78,6 +79,14 @@ FLAGS destination. Specify --no-disabled to enable a disabled sink. If this flag is not specified, the value will not be updated. + --include-children + Whether to export logs from all child projects and folders. Only + applies to sinks for organizations and folders. + + --intercept-children + Whether to intercept logs from all child projects and folders. Only + applies to sinks for organizations and folders. + --log-filter=LOG_FILTER A new filter expression for the sink. If omitted, the sink's existing filter (if any) is unchanged. diff --git a/gcloud/redis/clusters/create b/gcloud/redis/clusters/create index 70fec7075..d7f522635 100644 --- a/gcloud/redis/clusters/create +++ b/gcloud/redis/clusters/create @@ -4,8 +4,11 @@ NAME SYNOPSIS gcloud redis clusters create (CLUSTER : --region=REGION) --network=NETWORK - --shard-count=SHARD_COUNT [--async] [--auth-mode=AUTH_MODE] - [--replica-count=REPLICA_COUNT] + --shard-count=SHARD_COUNT [--aof-append-fsync=AOF_APPEND_FSYNC] + [--async] [--auth-mode=AUTH_MODE] [--persistence-mode=PERSISTENCE_MODE] + [--rdb-snapshot-period=RDB_SNAPSHOT_PERIOD] + [--rdb-snapshot-start-time=RDB_SNAPSHOT_START_TIME] + [--redis-config=[KEY=VALUE,...]] [--replica-count=REPLICA_COUNT] [--transit-encryption-mode=TRANSIT_ENCRYPTION_MODE] [GCLOUD_WIDE_FLAG ...] @@ -83,6 +86,18 @@ REQUIRED FLAGS The shard count of the cluster. OPTIONAL FLAGS + --aof-append-fsync=AOF_APPEND_FSYNC + Fsync configuration. AOF_APPEND_FSYNC must be one of: + + always + Redis explicitly calls fsync for every write command. + + everysec + (default) Redis explicitly calls fsync every second. + + no + Redis will not explicitly call fsync. + --async Return immediately, without waiting for the operation in progress to complete. @@ -97,6 +112,42 @@ OPTIONAL FLAGS iam-auth IAM basic authorization is enabled for the cluster. + --persistence-mode=PERSISTENCE_MODE + Operation mode for persistence. PERSISTENCE_MODE must be one of: + + aof + AOF-based persistence + disabled + Persistence mode is disabled + rdb + RDB-based persistence + + --rdb-snapshot-period=RDB_SNAPSHOT_PERIOD + Attempted period between RDB snapshots. RDB_SNAPSHOT_PERIOD must be one + of: + + 12h + 12 hours + 1h + 1 hour + 24h + (default) 24 hours + 6h + 6 hours + + --rdb-snapshot-start-time=RDB_SNAPSHOT_START_TIME + Date and time of the first snapshot in the ISO 1801 format, and + alignment time for future snapshots. For example, 2024-01-01T01:00:00Z. + If not specified, the current time will be used. + + --redis-config=[KEY=VALUE,...] + A list of Redis config KEY=VALUE pairs to set on the Redis Cluster + according to http://redis.io/topics/config. Currently the supported + Redis configs are: + + maxmemory-clients, maxmemory, maxmemory-policy, notify-keyspace-events, + slowlog-log-slower-than, maxclients. + --replica-count=REPLICA_COUNT The replica count of each shard. diff --git a/gcloud/redis/clusters/update b/gcloud/redis/clusters/update index 79a3dfbbf..f000b4e16 100644 --- a/gcloud/redis/clusters/update +++ b/gcloud/redis/clusters/update @@ -3,8 +3,13 @@ NAME instance SYNOPSIS - gcloud redis clusters update (CLUSTER : --region=REGION) [--async] - [--replica-count=REPLICA_COUNT] [--shard-count=SHARD_COUNT] + gcloud redis clusters update (CLUSTER : --region=REGION) + [--aof-append-fsync=AOF_APPEND_FSYNC] [--async] + [--persistence-mode=PERSISTENCE_MODE] + [--rdb-snapshot-period=RDB_SNAPSHOT_PERIOD] + [--rdb-snapshot-start-time=RDB_SNAPSHOT_START_TIME] + [--remove-redis-config=[KEY,...]] [--replica-count=REPLICA_COUNT] + [--shard-count=SHARD_COUNT] [--update-redis-config=KEY=VALUE] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -55,16 +60,65 @@ POSITIONAL ARGUMENTS ▸ set the property redis/region. FLAGS + --aof-append-fsync=AOF_APPEND_FSYNC + Fsync configuration. AOF_APPEND_FSYNC must be one of: + + always + Redis explicitly calls fsync for every write command. + + everysec + (default) Redis explicitly calls fsync every second. + + no + Redis will not explicitly call fsync. + --async Return immediately, without waiting for the operation in progress to complete. + --persistence-mode=PERSISTENCE_MODE + Operation mode for persistence. PERSISTENCE_MODE must be one of: + + aof + AOF-based persistence + disabled + Persistence mode is disabled + rdb + RDB-based persistence + + --rdb-snapshot-period=RDB_SNAPSHOT_PERIOD + Attempted period between RDB snapshots. RDB_SNAPSHOT_PERIOD must be one + of: + + 12h + 12 hours + 1h + 1 hour + 24h + (default) 24 hours + 6h + 6 hours + + --rdb-snapshot-start-time=RDB_SNAPSHOT_START_TIME + Date and time of the first snapshot in the ISO 1801 format, and + alignment time for future snapshots. For example, 2024-01-01T01:00:00Z. + If not specified, the current time will be used. + + --remove-redis-config=[KEY,...] + A list of Redis Cluster config parameters to remove. Removing a + non-existent config parameter is silently ignored. + --replica-count=REPLICA_COUNT The replica count of each shard. --shard-count=SHARD_COUNT The shard count of the cluster. + --update-redis-config=KEY=VALUE + A list of Redis Cluster config KEY=VALUE pairs to update. If a config + parameter is already set, its value is modified; otherwise a new Redis + config parameter is added. + 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/redis/instances/create b/gcloud/redis/instances/create index f98e5851c..7837c4ab0 100644 --- a/gcloud/redis/instances/create +++ b/gcloud/redis/instances/create @@ -184,6 +184,8 @@ FLAGS Redis 6.x compatibility redis_7_0 Redis 7.0 compatibility + redis_7_2 + Redis 7.2 compatibility --replica-count=REPLICA_COUNT The replica count of the instance. diff --git a/gcloud/redis/instances/upgrade b/gcloud/redis/instances/upgrade index 7e782a8e8..d7fc10243 100644 --- a/gcloud/redis/instances/upgrade +++ b/gcloud/redis/instances/upgrade @@ -64,6 +64,8 @@ REQUIRED FLAGS Redis 6.x compatibility redis_7_0 Redis 7.0 compatibility + redis_7_2 + Redis 7.2 compatibility OPTIONAL FLAGS --async diff --git a/gcloud/spanner/operations/help b/gcloud/spanner/operations/help index d6ecff086..4c1cfbe63 100644 --- a/gcloud/spanner/operations/help +++ b/gcloud/spanner/operations/help @@ -22,8 +22,7 @@ COMMANDS Describe a Cloud Spanner operation. list - List the Cloud Spanner operations on the given instance or database or - instance configuration. + List the Cloud Spanner operations. NOTES These variants are also available: diff --git a/gcloud/spanner/operations/list b/gcloud/spanner/operations/list index 74dc3b515..7f21e0826 100644 --- a/gcloud/spanner/operations/list +++ b/gcloud/spanner/operations/list @@ -1,6 +1,5 @@ NAME - gcloud spanner operations list - list the Cloud Spanner operations on the - given instance or database or instance configuration + gcloud spanner operations list - list the Cloud Spanner operations SYNOPSIS gcloud spanner operations list @@ -10,8 +9,7 @@ SYNOPSIS [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - List the Cloud Spanner operations on the given instance or database or - instance configuration. + List the Cloud Spanner operations. EXAMPLES To list Cloud Spanner instance operations for an instance, run: diff --git a/gcloud/sql/instances/create b/gcloud/sql/instances/create index 281e7bb36..8dd1e7fed 100644 --- a/gcloud/sql/instances/create +++ b/gcloud/sql/instances/create @@ -20,8 +20,8 @@ SYNOPSIS [--deny-maintenance-period-start-date=DENY_MAINTENANCE_PERIOD_START_DATE] [--deny-maintenance-period-time=DENY_MAINTENANCE_PERIOD_TIME] [--edition=EDITION] [--enable-bin-log] [--enable-data-cache] - [--enable-google-private-path] [--enable-password-policy] - [--enable-point-in-time-recovery] + [--[no-]enable-google-ml-integration] [--enable-google-private-path] + [--enable-password-policy] [--enable-point-in-time-recovery] [--failover-replica-name=FAILOVER_REPLICA_NAME] [--[no-]insights-config-query-insights-enabled] [--insights-config-query-plans-per-minute=INSIGHTS_CONFIG_QUERY_PLANS_PER_MINUTE] @@ -231,6 +231,11 @@ FLAGS Enable use of data cache for accelerated read performance. This flag is only available for Enterprise_Plus edition instances. + --[no-]enable-google-ml-integration + Enable Vertex AI integration for Google Cloud SQL. Currently, only + PostgreSQL is supported. Use --enable-google-ml-integration to enable + and --no-enable-google-ml-integration to disable. + --enable-google-private-path Enable a private path for Google Cloud services. This flag specifies whether the instance is accessible to internal Google Cloud services diff --git a/gcloud/sql/instances/patch b/gcloud/sql/instances/patch index 5eabb8205..51813f942 100644 --- a/gcloud/sql/instances/patch +++ b/gcloud/sql/instances/patch @@ -15,6 +15,7 @@ SYNOPSIS [--deny-maintenance-period-time=DENY_MAINTENANCE_PERIOD_TIME] [--diff] [--edition=EDITION] [--[no-]enable-bin-log] [--enable-data-cache] [--[no-]enable-database-replication] + [--[no-]enable-google-ml-integration] [--[no-]enable-google-private-path] [--enable-password-policy] [--enable-point-in-time-recovery] [--follow-gae-app=FOLLOW_GAE_APP] [--[no-]insights-config-query-insights-enabled] @@ -180,6 +181,11 @@ FLAGS --enable-database-replication to enable and --no-enable-database-replication to disable. + --[no-]enable-google-ml-integration + Enable Vertex AI integration for Google Cloud SQL. Currently, only + PostgreSQL is supported. Use --enable-google-ml-integration to enable + and --no-enable-google-ml-integration to disable. + --[no-]enable-google-private-path Enable a private path for Google Cloud services. This flag specifies whether the instance is accessible to internal Google Cloud services diff --git a/gcloud/storage/cp b/gcloud/storage/cp index 947257cf2..1c5da9eda 100644 --- a/gcloud/storage/cp +++ b/gcloud/storage/cp @@ -5,7 +5,7 @@ SYNOPSIS gcloud storage cp [SOURCE ...] DESTINATION [--additional-headers=HEADER=VALUE] [--all-versions, -A] [--no-clobber, -n] [--content-md5=MD5_DIGEST] [--continue-on-error, -c] - [--daisy-chain, -D] [--do-not-decompress] + [--daisy-chain, -D] [--do-not-decompress] [--include-managed-folders] [--manifest-path=MANIFEST_PATH, -L MANIFEST_PATH] [--preserve-posix, -P] [--print-created-message, -v] [--read-paths-from-stdin, -I] [--recursive, -R, -r] @@ -121,6 +121,12 @@ FLAGS --do-not-decompress Do not automatically decompress downloaded gzip files. + --include-managed-folders + Includes managed folders in command operations. For transfers, gcloud + storage will set up managed folders in the destination with the same + IAM policy bindings as the source. Managed folders are only included + with recursive cloud-to-cloud transfers. + --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 diff --git a/gcloud/storage/help b/gcloud/storage/help index e1c2c43f5..2de832a31 100644 --- a/gcloud/storage/help +++ b/gcloud/storage/help @@ -29,6 +29,9 @@ GROUPS insights Manage Cloud Storage inventory reports. + managed-folders + Manage Cloud Storage managed folders. + objects Manage Cloud Storage objects. diff --git a/gcloud/storage/managed-folders/add-iam-policy-binding b/gcloud/storage/managed-folders/add-iam-policy-binding new file mode 100644 index 000000000..f874c2b28 --- /dev/null +++ b/gcloud/storage/managed-folders/add-iam-policy-binding @@ -0,0 +1,111 @@ +NAME + gcloud storage managed-folders add-iam-policy-binding - add an IAM policy + binding to a managed folder + +SYNOPSIS + gcloud storage managed-folders add-iam-policy-binding URL + --member=PRINCIPAL --role=ROLE + [--condition=[KEY=VALUE,...] + | --condition-from-file=CONDITION_FROM_FILE] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Add an IAM policy binding to a managed folder. For more information, see + Cloud Identity and Access Management + (https://cloud.google.com/storage/docs/access-control/iam). + +EXAMPLES + To grant a single role to a single principal for a managed folder + managed-folder in a bucket bucket: + + $ gcloud storage managed-folders add-iam-policy-binding \ + gs://bucket/managed-folder --member=user:john.doe@example.com \ + --role=roles/storage.objectCreator + + To make objects in gs://bucket/managed-folder publicly readable: + + $ gcloud storage managed-folders add-iam-policy-binding \ + gs://bucket/managed-folder --member=allUsers \ + --role=roles/storage.objectViewer + + To specify a custom role for a principal on gs://bucket/managed-folder: + + $ gcloud storage managed-folders add-iam-policy-binding \ + gs://bucket/managed-folder --member=user:john.doe@example.com \ + --role=roles/customRoleName + +POSITIONAL ARGUMENTS + URL + URL of the managed folder to add IAM policy binding to. + +REQUIRED FLAGS + --member=PRINCIPAL + The principal to add the binding for. Should be of the form + user|group|serviceAccount:email or domain:domain. + + Examples: user:test-user@gmail.com, group:admins@example.com, + serviceAccount:test123@example.domain.com, or + domain:example.domain.com. + + Some resources also accept the following special values: + ◆ allUsers - Special identifier that represents anyone who is on the + internet, with or without a Google account. + ◆ allAuthenticatedUsers - Special identifier that represents anyone + who is authenticated with a Google account or a service account. + + --role=ROLE + Role name to assign to the principal. The role name is the complete + path of a predefined role, such as roles/logging.viewer, or the role ID + for a custom role, such as + organizations/{ORGANIZATION_ID}/roles/logging.viewer. + +OPTIONAL FLAGS + At most one of these can be specified: + + --condition=[KEY=VALUE,...] + A condition to include in the binding. When the condition is + explicitly specified as None (--condition=None), a binding without a + condition is added. When the condition is specified and is not None, + --role cannot be a basic role. Basic roles are roles/editor, + roles/owner, and roles/viewer. For more on conditions, refer to the + conditions overview guide: + https://cloud.google.com/iam/docs/conditions-overview + + When using the --condition flag, include the following key-value + pairs: + + expression + (Required) Condition expression that evaluates to True or False. + This uses a subset of Common Expression Language syntax. + + If the condition expression includes a comma, use a different + delimiter to separate the key-value pairs. Specify the delimiter + before listing the key-value pairs. For example, to specify a + colon (:) as the delimiter, do the following: + --condition=^:^title=TITLE:expression=EXPRESSION. For more + information, see + https://cloud.google.com/sdk/gcloud/reference/topic/escaping. + + title + (Required) A short string describing the purpose of the + expression. + + description + (Optional) Additional description for the expression. + + --condition-from-file=CONDITION_FROM_FILE + Path to a local JSON or YAML file that defines the condition. To see + available fields, see the help for --condition. + +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 variant is also available: + + $ gcloud alpha storage managed-folders add-iam-policy-binding + diff --git a/gcloud/storage/managed-folders/create b/gcloud/storage/managed-folders/create new file mode 100644 index 000000000..56c1e3b2c --- /dev/null +++ b/gcloud/storage/managed-folders/create @@ -0,0 +1,40 @@ +NAME + gcloud storage managed-folders create - create managed folders + +SYNOPSIS + gcloud storage managed-folders create URL [URL ...] + [--additional-headers=HEADER=VALUE] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Create managed folders. + +EXAMPLES + The following command creates a managed folder called folder/ in a bucket + named my-bucket: + + $ gcloud storage managed-folders create gs://my-bucket/folder/ + +POSITIONAL ARGUMENTS + URL [URL ...] + The URLs of the folders to create. + +FLAGS + --additional-headers=HEADER=VALUE + Includes arbitrary headers in storage API calls. Accepts a comma + separated list of key=value pairs, e.g. header1=value1,header2=value2. + Overrides the default storage/additional_headers property value for + this command invocation. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This variant is also available: + + $ gcloud alpha storage managed-folders create + diff --git a/gcloud/storage/managed-folders/delete b/gcloud/storage/managed-folders/delete new file mode 100644 index 000000000..938acf390 --- /dev/null +++ b/gcloud/storage/managed-folders/delete @@ -0,0 +1,47 @@ +NAME + gcloud storage managed-folders delete - delete managed folders + +SYNOPSIS + gcloud storage managed-folders delete URL [URL ...] + [--additional-headers=HEADER=VALUE] [--continue-on-error, -c] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Delete managed folders. + +EXAMPLES + The following command deletes a managed folder named folder in a bucket + called my-bucket: + + $ gcloud storage managed-folders delete gs://my-bucket/folder/ + +POSITIONAL ARGUMENTS + URL [URL ...] + The URLs of the managed folders to delete. + +FLAGS + --additional-headers=HEADER=VALUE + Includes arbitrary headers in storage API calls. Accepts a comma + separated list of key=value pairs, e.g. header1=value1,header2=value2. + Overrides the default storage/additional_headers property value for + this command invocation. + + --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. + +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 variant is also available: + + $ gcloud alpha storage managed-folders delete + diff --git a/gcloud/storage/managed-folders/describe b/gcloud/storage/managed-folders/describe new file mode 100644 index 000000000..12dc4da60 --- /dev/null +++ b/gcloud/storage/managed-folders/describe @@ -0,0 +1,44 @@ +NAME + gcloud storage managed-folders describe - describe managed folders + +SYNOPSIS + gcloud storage managed-folders describe URL + [--additional-headers=HEADER=VALUE] [--raw] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Describe managed folders. + +EXAMPLES + The following command shows information about a managed folder named folder + in a bucket called my-bucket: + + $ gcloud storage managed-folders describe gs://my-bucket/folder/ + +POSITIONAL ARGUMENTS + URL + The URL of the managed folder to describe. + +FLAGS + --additional-headers=HEADER=VALUE + Includes arbitrary headers in storage API calls. Accepts a comma + separated list of key=value pairs, e.g. header1=value1,header2=value2. + Overrides the default storage/additional_headers property value for + this command invocation. + + --raw + Shows metadata in the format returned by the API instead of + standardizing it. + +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 variant is also available: + + $ gcloud alpha storage managed-folders describe + diff --git a/gcloud/storage/managed-folders/get-iam-policy b/gcloud/storage/managed-folders/get-iam-policy new file mode 100644 index 000000000..4b06434fb --- /dev/null +++ b/gcloud/storage/managed-folders/get-iam-policy @@ -0,0 +1,41 @@ +NAME + gcloud storage managed-folders get-iam-policy - get the IAM policy for a + managed folder + +SYNOPSIS + gcloud storage managed-folders get-iam-policy URL [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Get the IAM policy for a managed folder. For more information, see Cloud + Identity and Access Management + (https://cloud.google.com/storage/docs/access-control/iam). + +EXAMPLES + To get the IAM policy for a managed folder managed-folder in a bucket + bucket: + + $ gcloud storage managed-folders get-iam-policy \ + gs://bucket/managed-folder/ + + To output the IAM policy for gs://bucket/managed-folder to a file: + + $ gcloud storage managed-folders get-iam-policy \ + gs://bucket/managed-folder/ > policy.txt + +POSITIONAL ARGUMENTS + URL + URL of the managed folder to get the IAM policy of. + +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 variant is also available: + + $ gcloud alpha storage managed-folders get-iam-policy + diff --git a/gcloud/storage/managed-folders/help b/gcloud/storage/managed-folders/help new file mode 100644 index 000000000..81a13a037 --- /dev/null +++ b/gcloud/storage/managed-folders/help @@ -0,0 +1,46 @@ +NAME + gcloud storage managed-folders - manage Cloud Storage managed folders + +SYNOPSIS + gcloud storage managed-folders COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Manage Cloud Storage managed folders. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + add-iam-policy-binding + Add an IAM policy binding to a managed folder. + + create + Create managed folders. + + delete + Delete managed folders. + + describe + Describe managed folders. + + get-iam-policy + Get the IAM policy for a managed folder. + + list + List managed folders. + + remove-iam-policy-binding + Remove an IAM policy binding from a managed folder. + + set-iam-policy + Set the IAM policy for a managed folder. + +NOTES + This variant is also available: + + $ gcloud alpha storage managed-folders + diff --git a/gcloud/storage/managed-folders/list b/gcloud/storage/managed-folders/list new file mode 100644 index 000000000..2eeb30a87 --- /dev/null +++ b/gcloud/storage/managed-folders/list @@ -0,0 +1,77 @@ +NAME + gcloud storage managed-folders list - list managed folders + +SYNOPSIS + gcloud storage managed-folders list URL [URL ...] + [--additional-headers=HEADER=VALUE] [--raw] [--filter=EXPRESSION] + [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + List managed folders. + +EXAMPLES + The following command lists all managed folders in a bucket: + + $ gcloud storage managed-folders list gs://my-bucket/ + +POSITIONAL ARGUMENTS + URL [URL ...] + The URLs of the resources to list. + +FLAGS + --additional-headers=HEADER=VALUE + Includes arbitrary headers in storage API calls. Accepts a comma + separated list of key=value pairs, e.g. header1=value1,header2=value2. + Overrides the default storage/additional_headers property value for + this command invocation. + + --raw + Shows metadata in the format returned by the API instead of + standardizing it. + +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 variant is also available: + + $ gcloud alpha storage managed-folders list + diff --git a/gcloud/storage/managed-folders/remove-iam-policy-binding b/gcloud/storage/managed-folders/remove-iam-policy-binding new file mode 100644 index 000000000..2aa7ea0c3 --- /dev/null +++ b/gcloud/storage/managed-folders/remove-iam-policy-binding @@ -0,0 +1,106 @@ +NAME + gcloud storage managed-folders remove-iam-policy-binding - remove an IAM + policy binding from a managed folder + +SYNOPSIS + gcloud storage managed-folders remove-iam-policy-binding URL + --member=PRINCIPAL --role=ROLE + [--all | --condition=[KEY=VALUE,...] + | --condition-from-file=CONDITION_FROM_FILE] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Remove a policy binding from the IAM policy of a managed folder, given a + managed folder URL and the binding. For more information, see Cloud + Identity and Access Management + (https://cloud.google.com/storage/docs/access-control/iam). + +EXAMPLES + To remove an IAM policy binding from the role of + roles/storage.objectCreator for the user john.doe@example.com on a managed + folder managed-folder in a bucket bucket: + + $ gcloud storage managed-folders remove-iam-policy-binding \ + gs://bucket/managed-folder --member=user:john.doe@example.com \ + --role=roles/storage.objectCreator + +POSITIONAL ARGUMENTS + URL + URL of managed folder to remove IAM policy binding from. + +REQUIRED FLAGS + --member=PRINCIPAL + The principal to remove the binding for. Should be of the form + user|group|serviceAccount:email or domain:domain. + + Examples: user:test-user@gmail.com, group:admins@example.com, + serviceAccount:test123@example.domain.com, or + domain:example.domain.com. + + Deleted principals have an additional deleted: prefix and a ?uid=UID + suffix, where UID is a unique identifier for the principal. Example: + deleted:user:test-user@gmail.com?uid=123456789012345678901. + + Some resources also accept the following special values: + ◆ allUsers - Special identifier that represents anyone who is on the + internet, with or without a Google account. + ◆ allAuthenticatedUsers - Special identifier that represents anyone + who is authenticated with a Google account or a service account. + + --role=ROLE + The role to remove the principal from. + +OPTIONAL FLAGS + At most one of these can be specified: + + --all + Remove all bindings with this role and principal, irrespective of any + conditions. + + --condition=[KEY=VALUE,...] + The condition of the binding that you want to remove. When the + condition is explicitly specified as None (--condition=None), a + binding without a condition is removed. Otherwise, only a binding + with a condition that exactly matches the specified condition + (including the optional description) is removed. For more on + conditions, refer to the conditions overview guide: + https://cloud.google.com/iam/docs/conditions-overview + + When using the --condition flag, include the following key-value + pairs: + + expression + (Required) Condition expression that evaluates to True or False. + This uses a subset of Common Expression Language syntax. + + If the condition expression includes a comma, use a different + delimiter to separate the key-value pairs. Specify the delimiter + before listing the key-value pairs. For example, to specify a + colon (:) as the delimiter, do the following: + --condition=^:^title=TITLE:expression=EXPRESSION. For more + information, see + https://cloud.google.com/sdk/gcloud/reference/topic/escaping. + + title + (Required) A short string describing the purpose of the + expression. + + description + (Optional) Additional description for the expression. + + --condition-from-file=CONDITION_FROM_FILE + Path to a local JSON or YAML file that defines the condition. To see + available fields, see the help for --condition. + +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 variant is also available: + + $ gcloud alpha storage managed-folders remove-iam-policy-binding + diff --git a/gcloud/storage/managed-folders/set-iam-policy b/gcloud/storage/managed-folders/set-iam-policy new file mode 100644 index 000000000..da62fe7bf --- /dev/null +++ b/gcloud/storage/managed-folders/set-iam-policy @@ -0,0 +1,56 @@ +NAME + gcloud storage managed-folders set-iam-policy - set the IAM policy for a + managed folder + +SYNOPSIS + gcloud storage managed-folders set-iam-policy URLS [URLS ...] POLICY_FILE + [--continue-on-error, -c] [--etag=ETAG, -e ETAG] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Set the IAM policy for a managed folder. For more information, see Cloud + Identity and Access Management + (https://cloud.google.com/storage/docs/access-control/iam). + +EXAMPLES + To set the IAM policy in POLICY-FILE on a managed folder managed-folder in + a bucket bucket: + + $ gcloud storage managed-folders set-iam-policy \ + gs://bucket/managed-folder POLICY-FILE + +POSITIONAL ARGUMENTS + URLS [URLS ...] + URLs for managed folders to apply the IAM policy to. + + POLICY_FILE + Path to a local JSON or YAML formatted file containing a valid policy. + + The output of the get-iam-policy command is a valid file, as is any + JSON or YAML file conforming to the structure of a Policy + (https://cloud.google.com/iam/reference/rest/v1/Policy). + +FLAGS + --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. + + --etag=ETAG, -e ETAG + Custom etag to set on IAM policy. API will reject etags that do not + match this value, making it useful as a precondition during concurrent + operations. + +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 variant is also available: + + $ gcloud alpha storage managed-folders set-iam-policy + diff --git a/gcloud/storage/mv b/gcloud/storage/mv index bb3687142..c88cde25f 100644 --- a/gcloud/storage/mv +++ b/gcloud/storage/mv @@ -5,7 +5,7 @@ SYNOPSIS gcloud storage mv [SOURCE ...] DESTINATION [--additional-headers=HEADER=VALUE] [--all-versions, -A] [--no-clobber, -n] [--content-md5=MD5_DIGEST] [--continue-on-error, -c] - [--daisy-chain, -D] [--do-not-decompress] + [--daisy-chain, -D] [--do-not-decompress] [--include-managed-folders] [--manifest-path=MANIFEST_PATH, -L MANIFEST_PATH] [--preserve-posix, -P] [--print-created-message, -v] [--read-paths-from-stdin, -I] [--skip-unsupported, -U] @@ -130,6 +130,12 @@ FLAGS --do-not-decompress Do not automatically decompress downloaded gzip files. + --include-managed-folders + Includes managed folders in command operations. For transfers, gcloud + storage will set up managed folders in the destination with the same + IAM policy bindings as the source. Managed folders are only included + with recursive cloud-to-cloud transfers. + --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 diff --git a/gcloud/storage/rm b/gcloud/storage/rm index b407c49b2..bc5655484 100644 --- a/gcloud/storage/rm +++ b/gcloud/storage/rm @@ -4,7 +4,8 @@ NAME SYNOPSIS gcloud storage rm [URLS ...] [--additional-headers=HEADER=VALUE] [--all-versions, -a] [--continue-on-error, -c] - [--read-paths-from-stdin, -I] [--recursive, -R, -r] + [--exclude-managed-folders] [--read-paths-from-stdin, -I] + [--recursive, -R, -r] [--if-generation-match=GENERATION --if-metageneration-match=METAGENERATION] [GCLOUD_WIDE_FLAG ...] @@ -68,6 +69,10 @@ FLAGS flag takes effect only in sequential execution mode (i.e. processor and thread count are set to 1). Parallelism is default. + --exclude-managed-folders + Excludes managed folders from command operations. By default gcloud + storage includes managed folders in recursive removals. + --read-paths-from-stdin, -I Read the list of URLs from stdin. diff --git a/gcloud/storage/rsync b/gcloud/storage/rsync index 5f406ad36..a4984fcd4 100644 --- a/gcloud/storage/rsync +++ b/gcloud/storage/rsync @@ -10,8 +10,9 @@ SYNOPSIS [--dry-run] [--exclude=[REGEX,...], -x [REGEX,...]] [--gzip-in-flight=[FILE_EXTENSIONS,...], -j [FILE_EXTENSIONS,...]] [--gzip-in-flight-all, -J] [--no-ignore-symlinks] - [--preserve-posix, -P] [--recursive, -R, -r] - [--skip-if-dest-has-newer-mtime, -u] [--skip-unsupported, -U] + [--include-managed-folders] [--preserve-posix, -P] + [--recursive, -R, -r] [--skip-if-dest-has-newer-mtime, -u] + [--skip-unsupported, -U] [--decryption-keys=[DECRYPTION_KEY,...] --encryption-key=ENCRYPTION_KEY] [--cache-control=CACHE_CONTROL @@ -179,6 +180,12 @@ FLAGS Ignore file symlinks instead of copying what they point to. Enabled by default, use --no-ignore-symlinks to disable. + --include-managed-folders + Includes managed folders in command operations. For transfers, gcloud + storage will set up managed folders in the destination with the same + IAM policy bindings as the source. Managed folders are only included + with recursive cloud-to-cloud transfers. + --preserve-posix, -P Causes POSIX attributes to be preserved when objects are copied. With this feature enabled, gcloud storage will copy several fields provided diff --git a/gcloud/workstations/configs/create b/gcloud/workstations/configs/create index db1e7d3b7..0e83b7b67 100644 --- a/gcloud/workstations/configs/create +++ b/gcloud/workstations/configs/create @@ -26,6 +26,8 @@ SYNOPSIS [--service-account-scopes=[SERVICE_ACCOUNT_SCOPES,...]] [--shielded-integrity-monitoring] [--shielded-secure-boot] [--shielded-vtpm] + [--accelerator-count=ACCELERATOR_COUNT + : --accelerator-type=ACCELERATOR_TYPE] [--container-custom-image=CONTAINER_CUSTOM_IMAGE | --container-predefined-image=CONTAINER_PREDEFINED_IMAGE; default="codeoss"] @@ -247,6 +249,18 @@ FLAGS --shielded-vtpm Default value is false. If set, instances will have vTPM enabled. + Accelerator settings + + --accelerator-count=ACCELERATOR_COUNT + The number of accelerator cards exposed to the instance. + + This flag argument must be specified if any of the other arguments in + this group are specified. + + --accelerator-type=ACCELERATOR_TYPE + The type of accelerator resource to attach to the instance, for + example, "nvidia-tesla-p100". + At most one of these can be specified: --container-custom-image=CONTAINER_CUSTOM_IMAGE @@ -265,6 +279,8 @@ FLAGS CLion codeoss Code OSS + codeoss-cuda + Code OSS + CUDA toolkit goland GoLand intellij diff --git a/gcloud/workstations/configs/update b/gcloud/workstations/configs/update index 95e9e457b..96036d32d 100644 --- a/gcloud/workstations/configs/update +++ b/gcloud/workstations/configs/update @@ -19,6 +19,8 @@ SYNOPSIS [--service-account-scopes=[SERVICE_ACCOUNT_SCOPES,...]] [--shielded-integrity-monitoring] [--shielded-secure-boot] [--shielded-vtpm] + [--accelerator-count=ACCELERATOR_COUNT + : --accelerator-type=ACCELERATOR_TYPE] [--container-custom-image=CONTAINER_CUSTOM_IMAGE | --container-predefined-image=CONTAINER_PREDEFINED_IMAGE] [--disable-ssh-to-vm | --enable-ssh-to-vm] @@ -196,6 +198,18 @@ FLAGS --shielded-vtpm Default value is false. If set, instances will have vTPM enabled. + Accelerator settings + + --accelerator-count=ACCELERATOR_COUNT + The number of accelerator cards exposed to the instance. + + This flag argument must be specified if any of the other arguments in + this group are specified. + + --accelerator-type=ACCELERATOR_TYPE + The type of accelerator resource to attach to the instance, for + example, "nvidia-tesla-p100". + At most one of these can be specified: --container-custom-image=CONTAINER_CUSTOM_IMAGE @@ -214,6 +228,8 @@ FLAGS CLion codeoss Code OSS + codeoss-cuda + Code OSS + CUDA toolkit goland GoLand intellij