diff --git a/gcloud/_version b/gcloud/_version index 2677f1d82..206f14cef 100644 --- a/gcloud/_version +++ b/gcloud/_version @@ -1,8 +1,8 @@ -Google Cloud SDK 471.0.0 -alpha 2024.03.29 -beta 2024.03.29 -bq 2.1.3 +Google Cloud SDK 472.0.0 +alpha 2024.04.12 +beta 2024.04.12 +bq 2.1.4 bundled-python3-unix 3.11.8 -core 2024.03.29 +core 2024.04.12 gcloud-crc32c 1.0.0 gsutil 5.27 diff --git a/gcloud/ai-platform/models/add-iam-policy-binding b/gcloud/ai-platform/models/add-iam-policy-binding index f76f20f55..3209c8a23 100644 --- a/gcloud/ai-platform/models/add-iam-policy-binding +++ b/gcloud/ai-platform/models/add-iam-policy-binding @@ -10,21 +10,21 @@ DESCRIPTION Add IAM policy binding to a model. EXAMPLES - To add an IAM policy binding for the role of 'roles/ml.admin' for the user - 'test-user@gmail.com' on a model with identifier 'my_model', run: + To add an IAM policy binding for the role of roles/ml.admin for the user + test-user@gmail.com on a model with identifier my_model, run: $ gcloud ai-platform models add-iam-policy-binding my_model \ --member='user:test-user@gmail.com' --role='roles/ml.admin' - To add an IAM policy binding for the role of 'roles/ml.admin' to the - service account 'test-proj1@example.domain.com', run: + To add an IAM policy binding for the role of roles/ml.admin to the service + account test-proj1@example.domain.com, run: $ gcloud ai-platform models add-iam-policy-binding my_model \ --member='serviceAccount:test-proj1@example.domain.com' \ --role='roles/ml.admin' - To add an IAM policy binding for the role of 'roles/ml.admin' for all - authenticated users on a model with identifier 'my_model', run: + To add an IAM policy binding for the role of roles/ml.admin for all + authenticated users on a model with identifier my_model, run: $ gcloud ai-platform models add-iam-policy-binding my_model \ --member='allAuthenticatedUsers' --role='roles/ml.admin' diff --git a/gcloud/ai-platform/models/remove-iam-policy-binding b/gcloud/ai-platform/models/remove-iam-policy-binding index ada6ea8f7..c54e07270 100644 --- a/gcloud/ai-platform/models/remove-iam-policy-binding +++ b/gcloud/ai-platform/models/remove-iam-policy-binding @@ -12,14 +12,14 @@ DESCRIPTION get-iam-policy for examples of how to specify a model resource. EXAMPLES - To remove an IAM policy binding for the role of 'roles/ml.admin' for the - user 'test-user@gmail.com' on model with identifier 'my_model', run: + To remove an IAM policy binding for the role of roles/ml.admin for the user + test-user@gmail.com on model with identifier my_model, run: $ gcloud ai-platform models remove-iam-policy-binding my_model \ --member='user:test-user@gmail.com' --role='roles/ml.admin' - To remove an IAM policy binding for the role of 'roles/ml.admin' from all - authenticated users on model 'my_model', run: + To remove an IAM policy binding for the role of roles/ml.admin from all + authenticated users on model my_model, run: $ gcloud ai-platform models remove-iam-policy-binding my_model \ --member='allAuthenticatedUsers' --role='roles/ml.admin' diff --git a/gcloud/ai/custom-jobs/create b/gcloud/ai/custom-jobs/create index a17af2a95..177835f94 100644 --- a/gcloud/ai/custom-jobs/create +++ b/gcloud/ai/custom-jobs/create @@ -7,6 +7,7 @@ SYNOPSIS [--args=[ARG,...]] [--command=[COMMAND,...]] [--enable-dashboard-access] [--enable-web-access] [--labels=[KEY=VALUE,...]] [--network=NETWORK] + [--persistent-resource-id=PERSISTENT_RESOURCE_ID] [--python-package-uris=[PYTHON_PACKAGE_URIS,...]] [--region=REGION] [--service-account=SERVICE_ACCOUNT] [--kms-key=KMS_KEY : --kms-keyring=KMS_KEYRING @@ -193,6 +194,15 @@ OPTIONAL FLAGS peered with. Private services access must already have been configured. If unspecified, the Job is not peered with any network. + --persistent-resource-id=PERSISTENT_RESOURCE_ID + The name of the persistent resource from the same project and region on + which to run this custom job. + + If this is specified, the job will be run on existing machines held by + the PersistentResource instead of on-demand short-lived machines. The + network and CMEK configs on the job should be consistent with those on + the PersistentResource, otherwise, the job will be rejected. + --python-package-uris=[PYTHON_PACKAGE_URIS,...] The common Python package URIs to be used for training with a pre-built container image. e.g. --python-package-uri=path1,path2 If you are using diff --git a/gcloud/ai/help b/gcloud/ai/help index 6667fa954..dfea8b24b 100644 --- a/gcloud/ai/help +++ b/gcloud/ai/help @@ -39,6 +39,9 @@ GROUPS operations Manage Vertex AI operations. + persistent-resources + Create and manage Vertex AI persistent resources. + tensorboards Manage Vertex AI Tensorboards. diff --git a/gcloud/ai/persistent-resources/create b/gcloud/ai/persistent-resources/create new file mode 100644 index 000000000..235b6b45c --- /dev/null +++ b/gcloud/ai/persistent-resources/create @@ -0,0 +1,194 @@ +NAME + gcloud ai persistent-resources create - create a new persistent resource + +SYNOPSIS + gcloud 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 + 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 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 + These variants are also available: + + $ gcloud alpha ai persistent-resources create + + $ gcloud beta ai persistent-resources create + diff --git a/gcloud/ai/persistent-resources/delete b/gcloud/ai/persistent-resources/delete new file mode 100644 index 000000000..01529d3c6 --- /dev/null +++ b/gcloud/ai/persistent-resources/delete @@ -0,0 +1,68 @@ +NAME + gcloud ai persistent-resources delete - delete an active Persistent + Resource + +SYNOPSIS + gcloud ai persistent-resources delete + (PERSISTENT_RESOURCE : --region=REGION) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + 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 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 + These variants are also available: + + $ gcloud alpha ai persistent-resources delete + + $ gcloud beta ai persistent-resources delete + diff --git a/gcloud/ai/persistent-resources/describe b/gcloud/ai/persistent-resources/describe new file mode 100644 index 000000000..e089f65b7 --- /dev/null +++ b/gcloud/ai/persistent-resources/describe @@ -0,0 +1,64 @@ +NAME + gcloud ai persistent-resources describe - get detailed information about a + PersistentResource with a given id + +SYNOPSIS + gcloud 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 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 + These variants are also available: + + $ gcloud alpha ai persistent-resources describe + + $ gcloud beta ai persistent-resources describe + diff --git a/gcloud/ai/persistent-resources/help b/gcloud/ai/persistent-resources/help new file mode 100644 index 000000000..f6d9d4783 --- /dev/null +++ b/gcloud/ai/persistent-resources/help @@ -0,0 +1,40 @@ +NAME + gcloud ai persistent-resources - create and manage Vertex AI persistent + resources + +SYNOPSIS + gcloud ai persistent-resources COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + 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 + Create a new persistent resource. + + delete + Delete an active Persistent Resource. + + describe + Get detailed information about a PersistentResource with a given id. + + list + Lists the active persistent resources. + + reboot + Reboot a Persistent Resource. + +NOTES + These variants are also available: + + $ gcloud alpha ai persistent-resources + + $ gcloud beta ai persistent-resources + diff --git a/gcloud/beta/eventarc/locations/list b/gcloud/ai/persistent-resources/list similarity index 57% rename from gcloud/beta/eventarc/locations/list rename to gcloud/ai/persistent-resources/list index 2064c4050..aed3db78f 100644 --- a/gcloud/beta/eventarc/locations/list +++ b/gcloud/ai/persistent-resources/list @@ -1,24 +1,39 @@ NAME - gcloud beta eventarc locations list - list locations available for Eventarc + gcloud ai persistent-resources list - lists the active persistent resources SYNOPSIS - gcloud beta eventarc locations list [--filter=EXPRESSION] [--limit=LIMIT] - [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + gcloud ai persistent-resources list [--region=REGION] [--filter=EXPRESSION] + [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] -DESCRIPTION - (BETA) (DEPRECATED) This command is deprecated. Please use gcloud eventarc - locations list instead. - - (BETA) (DEPRECATED) List locations available for Eventarc. - - This command is deprecated. Please use gcloud eventarc locations list - instead. - EXAMPLES - To list all locations, run: + To list the persistent resources of project example in region us-central1, + run: - $ gcloud beta eventarc locations list + $ gcloud 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 @@ -61,8 +76,9 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. NOTES - This command is currently in beta and might change without notice. This - variant is also available: + These variants are also available: - $ gcloud eventarc locations list + $ gcloud alpha ai persistent-resources list + + $ gcloud beta ai persistent-resources list diff --git a/gcloud/ai/persistent-resources/reboot b/gcloud/ai/persistent-resources/reboot new file mode 100644 index 000000000..c2e71f95c --- /dev/null +++ b/gcloud/ai/persistent-resources/reboot @@ -0,0 +1,63 @@ +NAME + gcloud ai persistent-resources reboot - reboot a Persistent Resource + +SYNOPSIS + gcloud ai persistent-resources reboot + (PERSISTENT_RESOURCE : --region=REGION) [GCLOUD_WIDE_FLAG ...] + +EXAMPLES + To reboot a persistent resource 123 under project example in region + us-central1, run: + + $ gcloud ai persistent-resources reboot 123 --project=example \ + --region=us-central1 + +POSITIONAL ARGUMENTS + Persistent resource resource - The persistent resource to reboot. 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 + These variants are also available: + + $ gcloud alpha ai persistent-resources reboot + + $ gcloud beta ai persistent-resources reboot + diff --git a/gcloud/alloydb/clusters/create b/gcloud/alloydb/clusters/create index 06de3139e..a992fa492 100644 --- a/gcloud/alloydb/clusters/create +++ b/gcloud/alloydb/clusters/create @@ -5,7 +5,8 @@ NAME SYNOPSIS gcloud alloydb clusters create CLUSTER --password=PASSWORD --region=REGION [--allocated-ip-range-name=ALLOCATED_IP_RANGE_NAME] [--async] - [--database-version=DATABASE_VERSION] [--network=NETWORK] + [--database-version=DATABASE_VERSION] + [--enable-private-service-connect] [--network=NETWORK] [--continuous-backup-recovery-window-days=RECOVERY_PERIOD --enable-continuous-backup [--continuous-backup-encryption-key=CONTINUOUS_BACKUP_ENCRYPTION_KEY @@ -58,6 +59,9 @@ OPTIONAL FLAGS Database version of the cluster. DATABASE_VERSION must be one of: POSTGRES_14, POSTGRES_15. + --enable-private-service-connect + Enable Private Service Connect (PSC) connectivity for the cluster. + --network=NETWORK Network in the current project that the instance will be part of. To specify using a network with a shared VPC, use the full URL of the diff --git a/gcloud/alloydb/clusters/restore b/gcloud/alloydb/clusters/restore index 9e987632b..87a78e04e 100644 --- a/gcloud/alloydb/clusters/restore +++ b/gcloud/alloydb/clusters/restore @@ -7,7 +7,7 @@ SYNOPSIS (--backup=BACKUP | --point-in-time=POINT_IN_TIME --source-cluster=SOURCE_CLUSTER) [--allocated-ip-range-name=ALLOCATED_IP_RANGE_NAME] [--async] - [--network=NETWORK] + [--enable-private-service-connect] [--network=NETWORK] [--kms-key=KMS_KEY : --kms-keyring=KMS_KEYRING --kms-location=KMS_LOCATION --kms-project=KMS_PROJECT] [GCLOUD_WIDE_FLAG ...] @@ -81,6 +81,9 @@ OPTIONAL FLAGS Return immediately, without waiting for the operation in progress to complete. + --enable-private-service-connect + Enable Private Service Connect (PSC) connectivity for the cluster. + --network=NETWORK Network in the current project that the instance will be part of. To specify using a network with a shared VPC, use the full URL of the diff --git a/gcloud/alloydb/clusters/update b/gcloud/alloydb/clusters/update index a355efaf0..1a2c835e0 100644 --- a/gcloud/alloydb/clusters/update +++ b/gcloud/alloydb/clusters/update @@ -5,11 +5,11 @@ NAME SYNOPSIS gcloud alloydb clusters update CLUSTER --region=REGION [--async] [--clear-automated-backup | --disable-automated-backup - | [--automated-backup-days-of-week=[DAYS_OF_WEEK,...] + | --automated-backup-days-of-week=[DAYS_OF_WEEK,...] --automated-backup-start-times=[START_TIMES,...] - : --automated-backup-window=TIMEOUT_PERIOD + --automated-backup-window=TIMEOUT_PERIOD [--automated-backup-encryption-key=AUTOMATED_BACKUP_ENCRYPTION_KEY - : --automated-backup-encryption-key-keyring=AUTOMATED_BACKUP_ENCRYPTION_KEY_KEYRING --automated-backup-encryption-key-location=AUTOMATED_BACKUP_ENCRYPTION_KEY_LOCATION --automated-backup-encryption-key-project=AUTOMATED_BACKUP_ENCRYPTION_KEY_PROJECT] --automated-backup-retention-count=RETENTION_COUNT | --automated-backup-retention-period=RETENTION_PERIOD]] + : --automated-backup-encryption-key-keyring=AUTOMATED_BACKUP_ENCRYPTION_KEY_KEYRING --automated-backup-encryption-key-location=AUTOMATED_BACKUP_ENCRYPTION_KEY_LOCATION --automated-backup-encryption-key-project=AUTOMATED_BACKUP_ENCRYPTION_KEY_PROJECT] --automated-backup-retention-count=RETENTION_COUNT | --automated-backup-retention-period=RETENTION_PERIOD] [--continuous-backup-recovery-window-days=RECOVERY_PERIOD --enable-continuous-backup --clear-continuous-backup-encryption-key | [--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]] @@ -60,18 +60,12 @@ OPTIONAL FLAGS DAYS_OF_WEEK must be one of: MONDAY, TUESDAY, WEDNESDAY, THURSDAY, FRIDAY, SATURDAY, SUNDAY. - This flag argument must be specified if any of the other arguments - in this group are specified. - --automated-backup-start-times=[START_TIMES,...] Comma-separated list of times during the day to start a backup. At least one start time must be provided. The start times are assumed to be in UTC and required to be an exact hour in the format HH:00. (e.g., --automated-backup-start-times=01:00,13:00) - This flag argument must be specified if any of the other arguments - in this group are specified. - --automated-backup-window=TIMEOUT_PERIOD The length of the time window beginning at start time during which a backup can be taken. If a backup does not succeed within this diff --git a/gcloud/alloydb/instances/create b/gcloud/alloydb/instances/create index 3df496f39..10e07bffd 100644 --- a/gcloud/alloydb/instances/create +++ b/gcloud/alloydb/instances/create @@ -5,6 +5,7 @@ NAME SYNOPSIS gcloud alloydb instances create INSTANCE --cluster=CLUSTER --cpu-count=CPU_COUNT --instance-type=INSTANCE_TYPE --region=REGION + [--allowed-psc-projects=[ALLOWED_PSC_PROJECTS,...]] [--assign-inbound-public-ip=ASSIGN_INBOUND_PUBLIC_IP] [--async] [--availability-type=AVAILABILITY_TYPE] [--database-flags=FLAG=VALUE,[FLAG=VALUE,...]] @@ -62,6 +63,12 @@ REQUIRED FLAGS regions at https://cloud.google.com/sql/docs/instance-locations. OPTIONAL FLAGS + --allowed-psc-projects=[ALLOWED_PSC_PROJECTS,...] + Comma-separated list of allowed consumer projects to create endpoints + for Private Service Connect (PSC) connectivity for the instance. Only + instances in PSC-enabled clusters are allowed to set this field.(e.g., + --allowed-psc-projects=project1,12345678,project2) + --assign-inbound-public-ip=ASSIGN_INBOUND_PUBLIC_IP Specify to enable or disable public IP on an instance. On instance creation only disabling public IP is allowed. If you want to enable diff --git a/gcloud/alloydb/instances/update b/gcloud/alloydb/instances/update index 1b93b1055..a84b4e98d 100644 --- a/gcloud/alloydb/instances/update +++ b/gcloud/alloydb/instances/update @@ -4,6 +4,7 @@ NAME SYNOPSIS gcloud alloydb instances update INSTANCE --cluster=CLUSTER --region=REGION + [--allowed-psc-projects=[ALLOWED_PSC_PROJECTS,...]] [--assign-inbound-public-ip=ASSIGN_INBOUND_PUBLIC_IP] [--async] [--authorized-external-networks=[AUTHORIZED_NETWORK,...]] [--availability-type=AVAILABILITY_TYPE] [--cpu-count=CPU_COUNT] @@ -39,6 +40,12 @@ REQUIRED FLAGS regions at https://cloud.google.com/sql/docs/instance-locations. OPTIONAL FLAGS + --allowed-psc-projects=[ALLOWED_PSC_PROJECTS,...] + Comma-separated list of allowed consumer projects to create endpoints + for Private Service Connect (PSC) connectivity for the instance. Only + instances in PSC-enabled clusters are allowed to set this field.(e.g., + --allowed-psc-projects=project1,12345678,project2) + --assign-inbound-public-ip=ASSIGN_INBOUND_PUBLIC_IP Specify to enable or disable public IP on an instance. ASSIGN_INBOUND_PUBLIC_IP must be one of: diff --git a/gcloud/alpha/ai-platform/models/add-iam-policy-binding b/gcloud/alpha/ai-platform/models/add-iam-policy-binding index bab6c59bf..12734af69 100644 --- a/gcloud/alpha/ai-platform/models/add-iam-policy-binding +++ b/gcloud/alpha/ai-platform/models/add-iam-policy-binding @@ -14,28 +14,28 @@ DESCRIPTION an optional condition. EXAMPLES - To add an IAM policy binding for the role of 'roles/ml.admin' for the user - 'test-user@gmail.com' on a model with identifier 'my_model', run: + To add an IAM policy binding for the role of roles/ml.admin for the user + test-user@gmail.com on a model with identifier my_model, run: $ gcloud alpha ai-platform models add-iam-policy-binding my_model \ --member='user:test-user@gmail.com' --role='roles/ml.admin' - To add an IAM policy binding for the role of 'roles/ml.admin' to the - service account 'test-proj1@example.domain.com', run: + To add an IAM policy binding for the role of roles/ml.admin to the service + account test-proj1@example.domain.com, run: $ gcloud alpha ai-platform models add-iam-policy-binding my_model \ --member='serviceAccount:test-proj1@example.domain.com' \ --role='roles/ml.admin' - To add an IAM policy binding for the role of 'roles/ml.admin' for all - authenticated users on a model with identifier 'my_model', run: + To add an IAM policy binding for the role of roles/ml.admin for all + authenticated users on a model with identifier my_model, run: $ gcloud alpha ai-platform models add-iam-policy-binding my_model \ --member='allAuthenticatedUsers' --role='roles/ml.admin' To add an IAM policy binding that expires at the end of the year 2018 for - the role of 'roles/ml.admin' and the user 'test-user@gmail.com' on a model - with identifier 'my_model', run: + the role of roles/ml.admin and the user test-user@gmail.com on a model with + identifier my_model, run: $ gcloud alpha ai-platform models add-iam-policy-binding my_model \ --member='user:test-user@gmail.com' --role='roles/ml.admin' \ diff --git a/gcloud/alpha/ai-platform/models/remove-iam-policy-binding b/gcloud/alpha/ai-platform/models/remove-iam-policy-binding index 0a99ab2b3..8a4bb41c7 100644 --- a/gcloud/alpha/ai-platform/models/remove-iam-policy-binding +++ b/gcloud/alpha/ai-platform/models/remove-iam-policy-binding @@ -15,15 +15,15 @@ DESCRIPTION specify a model resource. EXAMPLES - To remove an IAM policy binding for the role of 'roles/ml.admin' for the - user 'test-user@gmail.com' on model with identifier 'my_model', run: + To remove an IAM policy binding for the role of roles/ml.admin for the user + test-user@gmail.com on model with identifier my_model, run: $ gcloud alpha ai-platform models remove-iam-policy-binding \ my_model --member='user:test-user@gmail.com' \ --role='roles/ml.admin' - To remove an IAM policy binding for the role of 'roles/ml.admin' from all - authenticated users on model 'my_model', run: + To remove an IAM policy binding for the role of roles/ml.admin from all + authenticated users on model my_model, run: $ gcloud alpha ai-platform models remove-iam-policy-binding \ my_model --member='allAuthenticatedUsers' \ diff --git a/gcloud/alpha/ai/custom-jobs/create b/gcloud/alpha/ai/custom-jobs/create index 2e4ad4a84..7bc674233 100644 --- a/gcloud/alpha/ai/custom-jobs/create +++ b/gcloud/alpha/ai/custom-jobs/create @@ -7,6 +7,7 @@ SYNOPSIS [--args=[ARG,...]] [--command=[COMMAND,...]] [--enable-dashboard-access] [--enable-web-access] [--labels=[KEY=VALUE,...]] [--network=NETWORK] + [--persistent-resource-id=PERSISTENT_RESOURCE_ID] [--python-package-uris=[PYTHON_PACKAGE_URIS,...]] [--region=REGION] [--service-account=SERVICE_ACCOUNT] [--kms-key=KMS_KEY : --kms-keyring=KMS_KEYRING @@ -194,6 +195,15 @@ OPTIONAL FLAGS peered with. Private services access must already have been configured. If unspecified, the Job is not peered with any network. + --persistent-resource-id=PERSISTENT_RESOURCE_ID + The name of the persistent resource from the same project and region on + which to run this custom job. + + If this is specified, the job will be run on existing machines held by + the PersistentResource instead of on-demand short-lived machines. The + network and CMEK configs on the job should be consistent with those on + the PersistentResource, otherwise, the job will be rejected. + --python-package-uris=[PYTHON_PACKAGE_URIS,...] The common Python package URIs to be used for training with a pre-built container image. e.g. --python-package-uri=path1,path2 If you are using diff --git a/gcloud/alpha/ai/help b/gcloud/alpha/ai/help index ce00c1f47..ce321030a 100644 --- a/gcloud/alpha/ai/help +++ b/gcloud/alpha/ai/help @@ -40,7 +40,7 @@ GROUPS (ALPHA) Manage Vertex AI operations. persistent-resources - (ALPHA) Create and manage Vertex AI Persistent Resources. + (ALPHA) Create and manage Vertex AI rersistent 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 index 958a08862..6506a80e5 100644 --- a/gcloud/alpha/ai/persistent-resources/create +++ b/gcloud/alpha/ai/persistent-resources/create @@ -190,7 +190,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud ai persistent-resources create $ gcloud beta ai persistent-resources create diff --git a/gcloud/alpha/ai/persistent-resources/delete b/gcloud/alpha/ai/persistent-resources/delete index 9956dac46..39341977c 100644 --- a/gcloud/alpha/ai/persistent-resources/delete +++ b/gcloud/alpha/ai/persistent-resources/delete @@ -63,7 +63,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud ai persistent-resources delete $ gcloud beta ai persistent-resources delete diff --git a/gcloud/alpha/ai/persistent-resources/describe b/gcloud/alpha/ai/persistent-resources/describe index 65a206a9d..60c7261f8 100644 --- a/gcloud/alpha/ai/persistent-resources/describe +++ b/gcloud/alpha/ai/persistent-resources/describe @@ -59,7 +59,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud ai persistent-resources describe $ gcloud beta ai persistent-resources describe diff --git a/gcloud/alpha/ai/persistent-resources/help b/gcloud/alpha/ai/persistent-resources/help index d0038a351..7c97dd536 100644 --- a/gcloud/alpha/ai/persistent-resources/help +++ b/gcloud/alpha/ai/persistent-resources/help @@ -1,12 +1,12 @@ NAME gcloud alpha ai persistent-resources - create and manage Vertex AI - Persistent Resources + rersistent resources SYNOPSIS gcloud alpha ai persistent-resources COMMAND [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) Create and manage Vertex AI Persistent Resources. + (ALPHA) Create and manage Vertex AI rersistent resources. GCLOUD WIDE FLAGS These flags are available to all commands: --help. @@ -29,11 +29,16 @@ COMMANDS list (ALPHA) Lists the active persistent resources. + reboot + (ALPHA) Reboot an active Persistent Resource. + NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud ai persistent-resources $ gcloud beta ai persistent-resources diff --git a/gcloud/alpha/ai/persistent-resources/list b/gcloud/alpha/ai/persistent-resources/list index 3eab6fe75..2ef43d352 100644 --- a/gcloud/alpha/ai/persistent-resources/list +++ b/gcloud/alpha/ai/persistent-resources/list @@ -80,7 +80,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud ai persistent-resources list $ gcloud beta ai persistent-resources list diff --git a/gcloud/alpha/ai/persistent-resources/reboot b/gcloud/alpha/ai/persistent-resources/reboot new file mode 100644 index 000000000..376fc3397 --- /dev/null +++ b/gcloud/alpha/ai/persistent-resources/reboot @@ -0,0 +1,67 @@ +NAME + gcloud alpha ai persistent-resources reboot - reboot an active Persistent + Resource + +SYNOPSIS + gcloud alpha ai persistent-resources reboot + (PERSISTENT_RESOURCE : --region=REGION) [GCLOUD_WIDE_FLAG ...] + +EXAMPLES + To reboot a persistent resource 123 under project example in region + us-central1, run: + + $ gcloud alpha ai persistent-resources reboot 123 \ + --project=example --region=us-central1 + +POSITIONAL ARGUMENTS + Persistent resource resource - The persistent resource to reboot. 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. These variants are also available: + + $ gcloud ai persistent-resources reboot + + $ gcloud beta ai persistent-resources reboot + diff --git a/gcloud/alpha/alloydb/clusters/update b/gcloud/alpha/alloydb/clusters/update index 842e0dcef..c4ff43461 100644 --- a/gcloud/alpha/alloydb/clusters/update +++ b/gcloud/alpha/alloydb/clusters/update @@ -5,11 +5,11 @@ NAME SYNOPSIS gcloud alpha alloydb clusters update CLUSTER --region=REGION [--async] [--clear-automated-backup | --disable-automated-backup - | [--automated-backup-days-of-week=[DAYS_OF_WEEK,...] + | --automated-backup-days-of-week=[DAYS_OF_WEEK,...] --automated-backup-start-times=[START_TIMES,...] - : --automated-backup-window=TIMEOUT_PERIOD + --automated-backup-window=TIMEOUT_PERIOD [--automated-backup-encryption-key=AUTOMATED_BACKUP_ENCRYPTION_KEY - : --automated-backup-encryption-key-keyring=AUTOMATED_BACKUP_ENCRYPTION_KEY_KEYRING --automated-backup-encryption-key-location=AUTOMATED_BACKUP_ENCRYPTION_KEY_LOCATION --automated-backup-encryption-key-project=AUTOMATED_BACKUP_ENCRYPTION_KEY_PROJECT] --automated-backup-retention-count=RETENTION_COUNT | --automated-backup-retention-period=RETENTION_PERIOD]] + : --automated-backup-encryption-key-keyring=AUTOMATED_BACKUP_ENCRYPTION_KEY_KEYRING --automated-backup-encryption-key-location=AUTOMATED_BACKUP_ENCRYPTION_KEY_LOCATION --automated-backup-encryption-key-project=AUTOMATED_BACKUP_ENCRYPTION_KEY_PROJECT] --automated-backup-retention-count=RETENTION_COUNT | --automated-backup-retention-period=RETENTION_PERIOD] [--continuous-backup-recovery-window-days=RECOVERY_PERIOD --enable-continuous-backup --clear-continuous-backup-encryption-key | [--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]] @@ -60,18 +60,12 @@ OPTIONAL FLAGS DAYS_OF_WEEK must be one of: MONDAY, TUESDAY, WEDNESDAY, THURSDAY, FRIDAY, SATURDAY, SUNDAY. - This flag argument must be specified if any of the other arguments - in this group are specified. - --automated-backup-start-times=[START_TIMES,...] Comma-separated list of times during the day to start a backup. At least one start time must be provided. The start times are assumed to be in UTC and required to be an exact hour in the format HH:00. (e.g., --automated-backup-start-times=01:00,13:00) - This flag argument must be specified if any of the other arguments - in this group are specified. - --automated-backup-window=TIMEOUT_PERIOD The length of the time window beginning at start time during which a backup can be taken. If a backup does not succeed within this diff --git a/gcloud/alpha/backup-dr/management-servers/describe b/gcloud/alpha/backup-dr/management-servers/describe index 8edc3511f..d0df3ea90 100644 --- a/gcloud/alpha/backup-dr/management-servers/describe +++ b/gcloud/alpha/backup-dr/management-servers/describe @@ -17,8 +17,8 @@ EXAMPLES MANAGEMENT_SERVER POSITIONAL ARGUMENTS - ManagementServer resource - Name of the management server to describe. The - arguments in this group can be used to specify the attributes of this + Management server resource - Name of the management server 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. @@ -31,8 +31,8 @@ POSITIONAL ARGUMENTS This must be specified. MANAGEMENT_SERVER - ID of the managementServer or fully qualified identifier for the - managementServer. + ID of the management_server or fully qualified identifier for the + management_server. To set the management_server attribute: ▸ provide the argument management_server on the command line. diff --git a/gcloud/alpha/backup-dr/management-servers/list b/gcloud/alpha/backup-dr/management-servers/list index 6189c9612..6517bbcc8 100644 --- a/gcloud/alpha/backup-dr/management-servers/list +++ b/gcloud/alpha/backup-dr/management-servers/list @@ -29,7 +29,7 @@ FLAGS To set the project attribute: ◆ provide the argument --location on the command line with a fully specified name; - ◆ use default global location with a fully specified name; + ◆ default is all locations with a fully specified name; ◆ set the property core/project; ◆ provide the argument --project on the command line. @@ -38,7 +38,7 @@ FLAGS To set the location attribute: ▸ provide the argument --location on the command line; - ▸ use default global location . + ▸ default is all locations . LIST COMMAND FLAGS --filter=EXPRESSION diff --git a/gcloud/alpha/batch/tasks/list b/gcloud/alpha/batch/tasks/list index 5fc13201e..6cfc3d913 100644 --- a/gcloud/alpha/batch/tasks/list +++ b/gcloud/alpha/batch/tasks/list @@ -16,11 +16,11 @@ DESCRIPTION ▪ The active account does not have permission to access the given job EXAMPLES - To print all tasks in the group0 of job with name + To print all tasks in the job with name projects/foo/locations/us-central1/jobs/bar, run: $ gcloud alpha batch tasks list \ - projects/foo/locations/us-central1/jobs/bar + --job projects/foo/locations/us-central1/jobs/bar REQUIRED FLAGS Job resource - The Batch job resource. If not specified,the current diff --git a/gcloud/alpha/builds/submit b/gcloud/alpha/builds/submit index d66f64a15..285ba155e 100644 --- a/gcloud/alpha/builds/submit +++ b/gcloud/alpha/builds/submit @@ -8,9 +8,11 @@ SYNOPSIS [--gcs-source-staging-dir=GCS_SOURCE_STAGING_DIR] [--git-source-dir=GIT_SOURCE_DIR] [--git-source-revision=GIT_SOURCE_REVISION] [--ignore-file=IGNORE_FILE] - [--machine-type=MACHINE_TYPE] [--region=REGION] [--revision=REVISION] - [--service-account=SERVICE_ACCOUNT] [--substitutions=[KEY=VALUE,...]] - [--suppress-logs] [--timeout=TIMEOUT] [--worker-pool=WORKER_POOL] + [--machine-type=MACHINE_TYPE] + [--polling-interval=POLLING_INTERVAL; default=1] [--region=REGION] + [--revision=REVISION] [--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 ...] @@ -141,6 +143,9 @@ FLAGS Machine type used to run the build. MACHINE_TYPE must be one of: e2-highcpu-32, e2-highcpu-8, e2-medium, n1-highcpu-32, n1-highcpu-8. + --polling-interval=POLLING_INTERVAL; default=1 + Amount of time in seconds to wait between polling build status. + --region=REGION The region of the Cloud Build Service to use. Must be set to a supported region name (e.g. us-central1). If unset, builds/region, diff --git a/gcloud/alpha/certificate-manager/trust-configs/create b/gcloud/alpha/certificate-manager/trust-configs/create index 69a640293..8e1eb3910 100644 --- a/gcloud/alpha/certificate-manager/trust-configs/create +++ b/gcloud/alpha/certificate-manager/trust-configs/create @@ -4,8 +4,9 @@ NAME SYNOPSIS gcloud alpha certificate-manager trust-configs create (TRUST_CONFIG : --location=LOCATION) - --trust-store=[intermediate-cas=INTERMEDIATE-CAS], - [trust-anchors=TRUST-ANCHORS] [--async] [--description=DESCRIPTION] + (--allowlisted-certificates=[ALLOWLISTED_CERTIFICATES,...] + --trust-store=[intermediate-cas=INTERMEDIATE-CAS], + [trust-anchors=TRUST-ANCHORS]) [--async] [--description=DESCRIPTION] [--labels=[KEY=VALUE,...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -54,20 +55,33 @@ POSITIONAL ARGUMENTS ▸ default value of location is [global]. REQUIRED FLAGS - --trust-store=[intermediate-cas=INTERMEDIATE-CAS],[trust-anchors=TRUST-ANCHORS] - Trust Store with the given trust anchor and intermediate CA PEM-encoded - certificates. Certificates should be provided in files. For multiple - file names, separate them by a semicolon (';') and quote them ('"'). - One file can contain multiple certificates. Intermediate CAs are - optional. + At least one of these must be specified: - Examples: + --allowlisted-certificates=[ALLOWLISTED_CERTIFICATES,...] + Allowlisted PEM-encoded certificates. Certificates should be provided + in files. For multiple file names, separate them by a comma (','). + One file can contain multiple certificates. - Single files: --trust-store trust-anchors=ta.pem,intermediate-cas=ica.pem + Examples: - No intermediate CAs: --trust-store trust-anchors=ta.pem + Single file: --allowlisted-certificates=ac.pem - Multiple files: --trust-store trust-anchors="ta1.pem;ta2.pem",intermediate-cas="ica1.pem;ica2.pem" + Multiple files: --allowlisted-certificates=ac1.pem,ac2.pem + + --trust-store=[intermediate-cas=INTERMEDIATE-CAS],[trust-anchors=TRUST-ANCHORS] + Trust Store with the given trust anchor and intermediate CA + PEM-encoded certificates. Certificates should be provided in files. + For multiple file names, separate them by a semicolon (';') and quote + them ('"'). One file can contain multiple certificates. Intermediate + CAs are optional. + + Examples: + + Single files: --trust-store trust-anchors=ta.pem,intermediate-cas=ica.pem + + No intermediate CAs: --trust-store trust-anchors=ta.pem + + Multiple files: --trust-store trust-anchors="ta1.pem;ta2.pem",intermediate-cas="ica1.pem;ica2.pem" OPTIONAL FLAGS --async diff --git a/gcloud/alpha/certificate-manager/trust-configs/update b/gcloud/alpha/certificate-manager/trust-configs/update index 32127961a..4321c0e58 100644 --- a/gcloud/alpha/certificate-manager/trust-configs/update +++ b/gcloud/alpha/certificate-manager/trust-configs/update @@ -3,11 +3,15 @@ NAME SYNOPSIS gcloud alpha certificate-manager trust-configs update - (TRUST_CONFIG : --location=LOCATION) [--async] - [--description=DESCRIPTION] + (TRUST_CONFIG : --location=LOCATION) + [--add-allowlisted-certificates=[ADD_ALLOWLISTED_CERTIFICATES,...]] + [--async] [--description=DESCRIPTION] [--trust-store=[intermediate-cas=INTERMEDIATE-CAS], [trust-anchors=TRUST-ANCHORS]] [--update-labels=[KEY=VALUE,...]] - [--clear-labels | --remove-labels=[KEY,...]] [GCLOUD_WIDE_FLAG ...] + [--clear-allowlisted-certificates + | --remove-allowlisted-certificates=[REMOVE_ALLOWLISTED_CERTIFICATES, + ...]] [--clear-labels | --remove-labels=[KEY,...]] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Update a TrustConfig. @@ -56,6 +60,17 @@ POSITIONAL ARGUMENTS ▸ default value of location is [global]. FLAGS + --add-allowlisted-certificates=[ADD_ALLOWLISTED_CERTIFICATES,...] + Add allowlisted PEM-encoded certificates. Certificates should be + provided in files. For multiple file names, separate them by a comma + (','). One file can contain multiple certificates. + + Examples: + + Single file: --add-allowlisted-certificates=ac.pem + + Multiple files: --add-allowlisted-certificates=ac1.pem,ac2.pem + --async Return immediately, without waiting for the operation in progress to complete. @@ -87,6 +102,22 @@ FLAGS contain only hyphens (-), underscores (_), lowercase characters, and numbers. + At most one of these can be specified: + + --clear-allowlisted-certificates + Clear all allowlisted certificates. + + --remove-allowlisted-certificates=[REMOVE_ALLOWLISTED_CERTIFICATES,...] + Remove allowlisted PEM-encoded certificates. Certificates should be + provided in files. For multiple file names, separate them by a comma + (','). One file can contain multiple certificates. + + Examples: + + Single file: --remove-allowlisted-certificates=ac.pem + + Multiple files: --remove-allowlisted-certificates=ac1.pem,ac2.pem + At most one of these can be specified: --clear-labels diff --git a/gcloud/alpha/compute/service-attachments/create b/gcloud/alpha/compute/service-attachments/create index 776e222d1..c9ded0ea5 100644 --- a/gcloud/alpha/compute/service-attachments/create +++ b/gcloud/alpha/compute/service-attachments/create @@ -5,7 +5,8 @@ NAME SYNOPSIS gcloud alpha compute service-attachments create NAME --nat-subnets=NAT_SUBNETS,[NAT_SUBNETS,...] - --producer-forwarding-rule=PRODUCER_FORWARDING_RULE + (--producer-forwarding-rule=PRODUCER_FORWARDING_RULE + | --target-service=TARGET_SERVICE) [--connection-preference=CONNECTION_PREFERENCE; default="ACCEPT_AUTOMATIC"] [--consumer-accept-list=[PROJECT_OR_NETWORK=LIMIT,...]] @@ -51,8 +52,13 @@ REQUIRED FLAGS --nat-subnets=NAT_SUBNETS,[NAT_SUBNETS,...] The subnetworks provided by service producer to use for NAT - --producer-forwarding-rule=PRODUCER_FORWARDING_RULE - Target forwarding rule that receives forwarded traffic. + Exactly one of these must be specified: + + --producer-forwarding-rule=PRODUCER_FORWARDING_RULE + Target forwarding rule that receives forwarded traffic. + + --target-service=TARGET_SERVICE + URL of the target service that receives forwarded traffic. OPTIONAL FLAGS --connection-preference=CONNECTION_PREFERENCE; default="ACCEPT_AUTOMATIC" diff --git a/gcloud/alpha/compute/vpn-gateways/create b/gcloud/alpha/compute/vpn-gateways/create index 6c185657a..16efe4506 100644 --- a/gcloud/alpha/compute/vpn-gateways/create +++ b/gcloud/alpha/compute/vpn-gateways/create @@ -37,8 +37,9 @@ OPTIONAL FLAGS An optional, textual description for the VPN gateway. --gateway-ip-version=GATEWAY_IP_VERSION - The IP family of the gateway IPs for the HA-VPN gateway interfaces. If - not specified, IPV4 will be used. GATEWAY_IP_VERSION must be one of: + IP version of the HA VPN gateway. You must specify either IPv4 or IPv6. + If you do not specify this field, every HA VPN gateway interface will + be configured with an IPv4 address. GATEWAY_IP_VERSION must be one of: IPV4 Every HA-VPN gateway interface is configured with an IPv4 address. diff --git a/gcloud/alpha/config/get b/gcloud/alpha/config/get index 55c3b90d1..5acca824f 100644 --- a/gcloud/alpha/config/get +++ b/gcloud/alpha/config/get @@ -370,10 +370,6 @@ AVAILABLE PROPERTIES Overrides API endpoint for gcloud eventarc publish command group. Defaults to https://eventarcpublishing.googleapis.com/ - events - Overrides API endpoint for gcloud events command group. Defaults to - https://events.googleapis.com/ - faultinjectiontesting Overrides API endpoint for gcloud fault-injection command group. Defaults to https://faultinjectiontesting.googleapis.com/ diff --git a/gcloud/alpha/config/help b/gcloud/alpha/config/help index d0f0e1a3f..6638cf37d 100644 --- a/gcloud/alpha/config/help +++ b/gcloud/alpha/config/help @@ -402,10 +402,6 @@ AVAILABLE PROPERTIES Overrides API endpoint for gcloud eventarc publish command group. Defaults to https://eventarcpublishing.googleapis.com/ - events - Overrides API endpoint for gcloud events command group. Defaults to - https://events.googleapis.com/ - faultinjectiontesting Overrides API endpoint for gcloud fault-injection command group. Defaults to https://faultinjectiontesting.googleapis.com/ diff --git a/gcloud/alpha/config/list b/gcloud/alpha/config/list index cf36b52f8..6c8501a1e 100644 --- a/gcloud/alpha/config/list +++ b/gcloud/alpha/config/list @@ -414,10 +414,6 @@ AVAILABLE PROPERTIES Overrides API endpoint for gcloud eventarc publish command group. Defaults to https://eventarcpublishing.googleapis.com/ - events - Overrides API endpoint for gcloud events command group. Defaults to - https://events.googleapis.com/ - faultinjectiontesting Overrides API endpoint for gcloud fault-injection command group. Defaults to https://faultinjectiontesting.googleapis.com/ diff --git a/gcloud/alpha/config/set b/gcloud/alpha/config/set index ff4996a07..b86080627 100644 --- a/gcloud/alpha/config/set +++ b/gcloud/alpha/config/set @@ -417,10 +417,6 @@ AVAILABLE PROPERTIES Overrides API endpoint for gcloud eventarc publish command group. Defaults to https://eventarcpublishing.googleapis.com/ - events - Overrides API endpoint for gcloud events command group. Defaults to - https://events.googleapis.com/ - faultinjectiontesting Overrides API endpoint for gcloud fault-injection command group. Defaults to https://faultinjectiontesting.googleapis.com/ diff --git a/gcloud/alpha/config/unset b/gcloud/alpha/config/unset index 894c7ffd1..ed4e0c982 100644 --- a/gcloud/alpha/config/unset +++ b/gcloud/alpha/config/unset @@ -378,10 +378,6 @@ AVAILABLE PROPERTIES Overrides API endpoint for gcloud eventarc publish command group. Defaults to https://eventarcpublishing.googleapis.com/ - events - Overrides API endpoint for gcloud events command group. Defaults to - https://events.googleapis.com/ - faultinjectiontesting Overrides API endpoint for gcloud fault-injection command group. Defaults to https://faultinjectiontesting.googleapis.com/ diff --git a/gcloud/alpha/container/backup-restore/backup-plans/create b/gcloud/alpha/container/backup-restore/backup-plans/create index 0537ff35d..9290a8657 100644 --- a/gcloud/alpha/container/backup-restore/backup-plans/create +++ b/gcloud/alpha/container/backup-restore/backup-plans/create @@ -122,8 +122,9 @@ OPTIONAL FLAGS Number of days after which a backup produced via this plan is automatically deleted. - If not set (value is 0), backups are not automatically deleted. If set, - must be greater than the value for backup_delete_lock_days. + Must be less than or equal to 365 days. If not set (value is 0), + backups are not automatically deleted. If set, must be greater than the + value for backup_delete_lock_days. --locked If set, subsequent updates are not allowed to the backup plan's diff --git a/gcloud/alpha/container/backup-restore/backup-plans/update b/gcloud/alpha/container/backup-restore/backup-plans/update index ace9d1e31..614118129 100644 --- a/gcloud/alpha/container/backup-restore/backup-plans/update +++ b/gcloud/alpha/container/backup-restore/backup-plans/update @@ -118,8 +118,9 @@ FLAGS Number of days after which a backup produced via this plan is automatically deleted. - If not set (value is 0), backups are not automatically deleted. If set, - must be greater than the value for backup_delete_lock_days. + Must be less than or equal to 365 days. If not set (value is 0), + backups are not automatically deleted. If set, must be greater than the + value for backup_delete_lock_days. --locked If set, subsequent updates are not allowed to the backup plan's diff --git a/gcloud/alpha/domains/registrations/configure/contacts b/gcloud/alpha/domains/registrations/configure/contacts index d46949055..af9920734 100644 --- a/gcloud/alpha/domains/registrations/configure/contacts +++ b/gcloud/alpha/domains/registrations/configure/contacts @@ -16,6 +16,17 @@ DESCRIPTION the registrant before they take effect. In order to resend the email, execute this command again. + NOTE: Please consider carefully any changes to contact privacy settings + when changing from "redacted-contact-data" to "public-contact-data." There + may be a delay in reflecting updates you make to registrant contact + information such that any changes you make to contact privacy (including + from "redacted-contact-data" to "public-contact-data") will be applied + without delay but changes to registrant contact information may take a + limited time to be publicized. This means that changes to contact privacy + from "redacted-contact-data" to "public-contact-data" may make the previous + registrant contact data public until the modified registrant contact + details are published. + EXAMPLES To start an interactive flow to configure contact settings for example.com, run: diff --git a/gcloud/alpha/edge-cloud/container/clusters/create b/gcloud/alpha/edge-cloud/container/clusters/create index be7dfb1ff..16bc51827 100644 --- a/gcloud/alpha/edge-cloud/container/clusters/create +++ b/gcloud/alpha/edge-cloud/container/clusters/create @@ -13,6 +13,7 @@ SYNOPSIS [--control-plane-node-location=CONTROL_PLANE_NODE_LOCATION] [--control-plane-shared-deployment-policy=CONTROL_PLANE_SHARED_DEPLOYMENT_POLICY] [--default-max-pods-per-node=DEFAULT_MAX_PODS_PER_NODE] + [--external-lb-address-pools=EXTERNAL_LB_ADDRESS_POOLS] [--external-lb-ipv4-address-pools=[EXTERNAL_LB_IPV4_ADDRESS,...]] [--external-lb-ipv6-address-pools=[EXTERNAL_LB_IPV6_ADDRESS,...]] [--fleet-project=FLEET_PROJECT] [--labels=[KEY=VALUE,...]] @@ -120,6 +121,68 @@ FLAGS --default-max-pods-per-node=DEFAULT_MAX_PODS_PER_NODE The default maximum number of pods per node. + --external-lb-address-pools=EXTERNAL_LB_ADDRESS_POOLS + Path to a YAML/JSON file containing external load balancer pool + configuration. External load balancer pools are used for data plane + load balancing of local control plane clusters, with custom config such + as address pool name. Either --external-lb-ipv4-address-pools or + --external-lb-address-pools should be specified. Existing pools cannot + be updated after cluster creation; only adding new pools is allowed + currently. + + For example, + + { + + "externalLoadBalancerAddressPools": [ + + { + + "addressPool": "MyLoadBalancerPool", + + "ipv4Range": ["10.200.0.200-10.200.0.204","10.200.0.300/30"], + + "avoidBuggyIps": "false", + + "manualAssign": "true" + + } + + ] + + } + + address_pool + Optional. A name that identifies an address pool. If a name is not + specified, an auto-generated one will be used. + + ipv4_range + Mandatory. One or more ipv4 address range, each must be specified + as one of the following two types of values: + + 1. A IPv4 address range, for example, "10.0.0.1-10.0.0.10". A range that contains a single IP (e.g. "10.0.0.1-10.0.0.1") is allowed. + + 2. A IPv4 CIDR block, for example, "10.0.0.1/24" + + ipv6_range + Optional. One or more ipv6 address range, each must be specified as + one of the following two types of values: + + 1. A IPv6 address range, for example, "2001:db8::1-2001:db8::a". A range that contains a single IP (e.g. "2001:db8::1-2001:db8::1") is allowed. + + 2. A IPv6 CIDR block, for example, "2001:db8::/120" + + avoid_buggy_ips + Optional. If true, the pool omits IP addresses ending in .0 and + .255. Some network hardware drops traffic to these special + addresses. Its default value is false. + + manual_assign + Optional. If true, addresses in this pool are not automatically + assigned to Kubernetes Services. If true, an IP address in this + pool is used only when it is specified explicitly by a service. Its + default value is false. + --external-lb-ipv4-address-pools=[EXTERNAL_LB_IPV4_ADDRESS,...] IPv4 address pools that are used for data plane load balancing of local control plane clusters. Existing pools cannot be updated after cluster diff --git a/gcloud/alpha/edge-cloud/container/clusters/list b/gcloud/alpha/edge-cloud/container/clusters/list index 0fe18fe12..ab72cffb5 100644 --- a/gcloud/alpha/edge-cloud/container/clusters/list +++ b/gcloud/alpha/edge-cloud/container/clusters/list @@ -17,17 +17,16 @@ EXAMPLES --location=us-central1 FLAGS - Location resource - Parent Edge Container location to list all contained - Edge Container clusters. This represents a Cloud resource. (NOTE) Some - attributes are not given arguments in this group but can be set in other - ways. + Location resource - Edge Container location to list. 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 --location on the command line with a fully specified name; ◆ set the property edge_container/location with a fully specified name; - ◆ set the property core/project; - ◆ provide the argument --project on the command line. + ◆ provide the argument --project on the command line; + ◆ set the property core/project. --location=LOCATION ID of the location or fully qualified identifier for the location. diff --git a/gcloud/alpha/edge-cloud/container/clusters/update b/gcloud/alpha/edge-cloud/container/clusters/update index 49286f0b3..8c22f5e33 100644 --- a/gcloud/alpha/edge-cloud/container/clusters/update +++ b/gcloud/alpha/edge-cloud/container/clusters/update @@ -7,9 +7,7 @@ SYNOPSIS (CLUSTER : --location=LOCATION) [--async] [--release-channel=RELEASE_CHANNEL] [--clear-maintenance-window - | --maintenance-window-end=MAINTENANCE_WINDOW_END - --maintenance-window-recurrence=MAINTENANCE_WINDOW_RECURRENCE - --maintenance-window-start=MAINTENANCE_WINDOW_START] + | --remove-maintenance-exclusion-window=REMOVE_MAINTENANCE_EXCLUSION_WINDOW | --add-maintenance-exclusion-end=ADD_MAINTENANCE_EXCLUSION_END --add-maintenance-exclusion-name=ADD_MAINTENANCE_EXCLUSION_NAME --add-maintenance-exclusion-start=ADD_MAINTENANCE_EXCLUSION_START | --maintenance-window-end=MAINTENANCE_WINDOW_END --maintenance-window-recurrence=MAINTENANCE_WINDOW_RECURRENCE --maintenance-window-start=MAINTENANCE_WINDOW_START] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -71,7 +69,31 @@ FLAGS At most one of these can be specified: --clear-maintenance-window - If set, removes the maintenance window setting from the cluster. + If set, removes the maintenance window setting from the cluster. If + any exclusion windows exist, they must be removed beforehand as a + maintenance policy cannot exist without a maintenance window. + + --remove-maintenance-exclusion-window=REMOVE_MAINTENANCE_EXCLUSION_WINDOW + Name of the maintenance exclusion to remove. + + Add a maintenance exclusion window (all flags must be specified to add a + valid maintenance exclusion window). There can be a maximum of 3 + exclusion windows set at a given time. A maintenance exclusion window + cannot be added in the absence of a maintenance window. + + --add-maintenance-exclusion-end=ADD_MAINTENANCE_EXCLUSION_END + End time of the maintenance exclusion window in the RFC 3339 + (https://www.ietf.org/rfc/rfc3339.txt) format. E.g. + "2021-01-01T00:00:00Z" or "2021-01-01T00:00:00-05:00". + + --add-maintenance-exclusion-name=ADD_MAINTENANCE_EXCLUSION_NAME + Unique name (per cluster) of the maintenance exclusion window that + can be used to remove it. + + --add-maintenance-exclusion-start=ADD_MAINTENANCE_EXCLUSION_START + Start time of the maintenance exclusion window (can occur in the + past) in the RFC 3339 (https://www.ietf.org/rfc/rfc3339.txt) + format. E.g. "2021-01-01T00:00:00Z" or "2021-01-01T00:00:00-05:00". Updates cluster maintenance window setting (more than one flags can be specified from this group) diff --git a/gcloud/alpha/metastore/services/create b/gcloud/alpha/metastore/services/create index 73a16ebe4..b78aac7d7 100644 --- a/gcloud/alpha/metastore/services/create +++ b/gcloud/alpha/metastore/services/create @@ -4,7 +4,7 @@ NAME SYNOPSIS gcloud alpha metastore services create (SERVICE : --location=LOCATION) - [--async] [--data-catalog-sync] + [--async] [--autoscaling-enabled] [--data-catalog-sync] [--database-type=DATABASE_TYPE; default="mysql"] [--encryption-kms-key=ENCRYPTION_KMS_KEY] [--endpoint-protocol=ENDPOINT_PROTOCOL; default="thrift"] @@ -18,7 +18,8 @@ SYNOPSIS [--hive-metastore-configs=[KEY=VALUE,...] | --hive-metastore-configs-from-file=HIVE_METASTORE_CONFIGS_FROM_FILE] [--instance-size=INSTANCE_SIZE | --scaling-factor=SCALING_FACTOR - | --tier=TIER] + | --tier=TIER | --max-scaling-factor=MAX_SCALING_FACTOR + --min-scaling-factor=MIN_SCALING_FACTOR] [--kerberos-principal=KERBEROS_PRINCIPAL --keytab=KEYTAB --krb5-config=KRB5_CONFIG] [--maintenance-window-day=MAINTENANCE_WINDOW_DAY @@ -87,6 +88,16 @@ FLAGS Return immediately, without waiting for the operation in progress to complete. + --autoscaling-enabled + A boolean flag to determine whether Dataproc Metastore autoscaling + should be enabled, false if unspecified. + + The default minimum and maximum scaling factors are 0.1 and 6.0, + respectively. + + The minimum and maximum scaling factors can be specified using + --min-scaling-factor and --max-scaling-factor. + --data-catalog-sync A boolean flag to determine whether Dataproc Metastore metadata sync to Data Catalog should be enabled, false if unspecified. Mutually @@ -269,10 +280,8 @@ FLAGS Small instance size, maps to a scaling factor of 0.5. --scaling-factor=SCALING_FACTOR - The scaling factor of the service. This should be a float in the - range [0.1,6.0]. If the value is less than 1.0, then it should be a - multiple of 0.1. If the value is greater than 1.0, then it should be - a whole number. Float values should be formatted as x.y. + The scaling factor of the service. Can be one of [0.1, 0.2, 0.3, 0.4, + 0.5, 0.6, 0.7, 0.8, 0.9, 1.0, 2.0, 3.0, 4.0, 5.0, 6.0]. --tier=TIER The tier of the service. TIER must be one of: @@ -286,6 +295,18 @@ FLAGS sufficient scalability for enterprise-level Dataproc Metastore workloads. + The autoscaling configuration of the Dataproc Metastore instance. + + --max-scaling-factor=MAX_SCALING_FACTOR + The maximum scaling factor allowed by the autoscaler. Can be one of + [0.1, 0.2, 0.3, 0.4, 0.5, 0.6, 0.7, 0.8, 0.9, 1.0, 2.0, 3.0, 4.0, + 5.0, 6.0]. The default value is 6.0. + + --min-scaling-factor=MIN_SCALING_FACTOR + The minimum scaling factor allowed by the autoscaler. Can be one of + [0.1, 0.2, 0.3, 0.4, 0.5, 0.6, 0.7, 0.8, 0.9, 1.0, 2.0, 3.0, 4.0, + 5.0, 6.0]. The default value is 0.1. + Information used to configure the Hive metastore service as a service principal in a Kerberos realm. diff --git a/gcloud/alpha/metastore/services/help b/gcloud/alpha/metastore/services/help index fa05c299b..212f7f963 100644 --- a/gcloud/alpha/metastore/services/help +++ b/gcloud/alpha/metastore/services/help @@ -31,6 +31,9 @@ GROUPS (ALPHA) (DEPRECATED) Manage metadata imports under Dataproc Metastore services. + migrations + (ALPHA) Manage the migration to a Dataproc Metastore service. + COMMANDS COMMAND is one of the following: diff --git a/gcloud/alpha/metastore/services/migrations/cancel b/gcloud/alpha/metastore/services/migrations/cancel new file mode 100644 index 000000000..afa5b4beb --- /dev/null +++ b/gcloud/alpha/metastore/services/migrations/cancel @@ -0,0 +1,75 @@ +NAME + gcloud alpha metastore services migrations cancel - cancel the migration to + Dataproc Metastore service + +SYNOPSIS + gcloud alpha metastore services migrations cancel + (SERVICE : --location=LOCATION) [--async] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Cancel the migration to Dataproc Metastore service. + + If run asynchronously with --async, exits after printing the operation name + that can be used to poll the status of the migration operation via: + + gcloud metastore operations describe + +POSITIONAL ARGUMENTS + Service resource - The Dataproc Metastore service to cancel the migration + 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 service on the command line with a fully + specified name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + This must be specified. + + SERVICE + ID of the service or fully qualified identifier for the service. + + To set the service attribute: + ▸ provide the argument service on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + The location of the Dataproc Metastore service. + + If not specified, will use default metastore/location. + + To set the location attribute: + ▸ provide the argument service on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ set the property metastore/location. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + +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 metastore/v1alpha API. The full documentation for + this API can be found at: https://cloud.google.com/dataproc-metastore/docs + +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 metastore services migrations cancel + diff --git a/gcloud/alpha/metastore/services/migrations/complete b/gcloud/alpha/metastore/services/migrations/complete new file mode 100644 index 000000000..c653203e3 --- /dev/null +++ b/gcloud/alpha/metastore/services/migrations/complete @@ -0,0 +1,75 @@ +NAME + gcloud alpha metastore services migrations complete - complete the + migration to Dataproc Metastore service + +SYNOPSIS + gcloud alpha metastore services migrations complete + (SERVICE : --location=LOCATION) [--async] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Complete the migration to Dataproc Metastore service. + + If run asynchronously with --async, exits after printing the operation name + that can be used to poll the status of the migration operation via: + + gcloud metastore operations describe + +POSITIONAL ARGUMENTS + Service resource - The Dataproc Metastore service to complete the + migration 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 service on the command line with a fully + specified name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + This must be specified. + + SERVICE + ID of the service or fully qualified identifier for the service. + + To set the service attribute: + ▸ provide the argument service on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + The location of the Dataproc Metastore service. + + If not specified, will use default metastore/location. + + To set the location attribute: + ▸ provide the argument service on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ set the property metastore/location. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + +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 metastore/v1alpha API. The full documentation for + this API can be found at: https://cloud.google.com/dataproc-metastore/docs + +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 metastore services migrations complete + diff --git a/gcloud/alpha/metastore/services/migrations/delete b/gcloud/alpha/metastore/services/migrations/delete new file mode 100644 index 000000000..c2bcb0e48 --- /dev/null +++ b/gcloud/alpha/metastore/services/migrations/delete @@ -0,0 +1,88 @@ +NAME + gcloud alpha metastore services migrations delete - delete a migration + +SYNOPSIS + gcloud alpha metastore services migrations delete + (MIGRATION : --location=LOCATION --service=SERVICE) [--async] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Delete a migration. + + If run asynchronously with --async, exits after printing an operation name + that can be used to poll the status of the deletion via: + + gcloud metastore operations describe + +EXAMPLES + To delete a migration named my-migration for the service my-service, run: + + $ gcloud alpha metastore services migrations delete my-migration \ + --service=my-service + +POSITIONAL ARGUMENTS + Migration resource - Migration 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 migration on the command line with a fully + specified name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + This must be specified. + + MIGRATION + ID of the migration or fully qualified identifier for the migration. + + To set the migration attribute: + ▸ provide the argument migration on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + The location of the Dataproc Metastore service. + + If not specified, will use default metastore/location. + + To set the location attribute: + ▸ provide the argument migration on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ set the property metastore/location. + + --service=SERVICE + The identifier of the Dataproc Metastore service + + To set the service attribute: + ▸ provide the argument migration on the command line with a fully + specified name; + ▸ provide the argument --service on the command line. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + +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 metastore/v1alpha API. The full documentation for + this API can be found at: https://cloud.google.com/dataproc-metastore/docs + +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 metastore services migrations delete + diff --git a/gcloud/alpha/metastore/services/migrations/describe b/gcloud/alpha/metastore/services/migrations/describe new file mode 100644 index 000000000..b4be10f5a --- /dev/null +++ b/gcloud/alpha/metastore/services/migrations/describe @@ -0,0 +1,82 @@ +NAME + gcloud alpha metastore services migrations describe - describe a migration + +SYNOPSIS + gcloud alpha metastore services migrations describe + (MIGRATION : --location=LOCATION --service=SERVICE) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Describe a migration. + + Displays all details of a migration given a migration ID. + +EXAMPLES + To describe a migration with the ID my-migration under service my-service, + run: + + $ gcloud alpha metastore services migrations describe my-migration \ + --service=my-service + +POSITIONAL ARGUMENTS + Migration resource - Arguments and flags that specify the migration you + want 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 migration on the command line with a fully + specified name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + This must be specified. + + MIGRATION + ID of the migration or fully qualified identifier for the migration. + + To set the migration attribute: + ▸ provide the argument migration on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + The location of the Dataproc Metastore service. + + If not specified, will use default metastore/location. + + To set the location attribute: + ▸ provide the argument migration on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ set the property metastore/location. + + --service=SERVICE + The identifier of the Dataproc Metastore service + + To set the service attribute: + ▸ provide the argument migration on the command line with a fully + specified name; + ▸ provide the argument --service 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 metastore/v1alpha API. The full documentation for + this API can be found at: https://cloud.google.com/dataproc-metastore/docs + +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 metastore services migrations describe + diff --git a/gcloud/alpha/metastore/services/migrations/help b/gcloud/alpha/metastore/services/migrations/help new file mode 100644 index 000000000..3b7ba1a83 --- /dev/null +++ b/gcloud/alpha/metastore/services/migrations/help @@ -0,0 +1,44 @@ +NAME + gcloud alpha metastore services migrations - manage the migration to a + Dataproc Metastore service + +SYNOPSIS + gcloud alpha metastore services migrations COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Manage the migration to a Dataproc Metastore service. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + cancel + (ALPHA) Cancel the migration to Dataproc Metastore service. + + complete + (ALPHA) Complete the migration to Dataproc Metastore service. + + delete + (ALPHA) Delete a migration. + + describe + (ALPHA) Describe a migration. + + list + (ALPHA) List migrations for a Dataproc Metastore service. + + start + (ALPHA) Start the migration on a Dataproc Metastore service. + +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 metastore services migrations + diff --git a/gcloud/alpha/metastore/services/migrations/list b/gcloud/alpha/metastore/services/migrations/list new file mode 100644 index 000000000..4acbb584a --- /dev/null +++ b/gcloud/alpha/metastore/services/migrations/list @@ -0,0 +1,105 @@ +NAME + gcloud alpha metastore services migrations list - list migrations for a + Dataproc Metastore service + +SYNOPSIS + gcloud alpha metastore services migrations list + (--service=SERVICE : --location=LOCATION) [--filter=EXPRESSION] + [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Lists all migrations for the specified Dataproc Metastore service. + +EXAMPLES + To list all migrations for service my-service, run: + + $ gcloud alpha metastore services migrations list \ + --service=my-service + +REQUIRED FLAGS + Service resource - The service to list the migrations 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 --service on the command line with a fully + specified name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + This must be specified. + + --service=SERVICE + ID of the service or fully qualified identifier for the service. + + To set the service attribute: + ▸ provide the argument --service on the command line. + + This flag argument must be specified if any of the other arguments in + this group are specified. + + --location=LOCATION + The location of the Dataproc Metastore service. + + If not specified, will use default metastore/location. + + To set the location attribute: + ▸ provide the argument --service on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ set the property metastore/location. + +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 metastore/v1alpha API. The full documentation for + this API can be found at: https://cloud.google.com/dataproc-metastore/docs + +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 metastore services migrations list + diff --git a/gcloud/alpha/metastore/services/migrations/start b/gcloud/alpha/metastore/services/migrations/start new file mode 100644 index 000000000..e0f37d407 --- /dev/null +++ b/gcloud/alpha/metastore/services/migrations/start @@ -0,0 +1,224 @@ +NAME + gcloud alpha metastore services migrations start - start the migration on a + Dataproc Metastore service + +SYNOPSIS + gcloud alpha metastore services migrations start + (SERVICE : --location=LOCATION) + ((--cdc-password=CDC_PASSWORD --cdc-username=CDC_USERNAME + --reverse-proxy-subnet=REVERSE_PROXY_SUBNET + --subnet-ip-range=SUBNET_IP_RANGE --vpc-network=VPC_NETWORK + : --bucket=BUCKET --root-path=ROOT_PATH; default="/migration") + (--connection-password=CONNECTION_PASSWORD + --connection-username=CONNECTION_USERNAME + --hive-database-name=HIVE_DATABASE_NAME + --instance-connection-name=INSTANCE_CONNECTION_NAME + --ip-address=IP_ADDRESS + --nat-subnet=NAT_SUBNET --port=PORT --proxy-subnet=PROXY_SUBNET)) + [--async] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Start the migration on a Dataproc Metastore service. + + If run asynchronously with --async, exits after printing the operation name + that can be used to poll the status of the migration operation via: + + gcloud metastore operations describe + +POSITIONAL ARGUMENTS + Service resource - The Dataproc Metastore service to start the migration + 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 service on the command line with a fully + specified name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + This must be specified. + + SERVICE + ID of the service or fully qualified identifier for the service. + + To set the service attribute: + ▸ provide the argument service on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + The location of the Dataproc Metastore service. + + If not specified, will use default metastore/location. + + To set the location attribute: + ▸ provide the argument service on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ set the property metastore/location. + +REQUIRED FLAGS + Configuration information required by Dataproc Metastore to start the + migration. + + This must be specified. + + Configuration information specific to migrating from "Self-Managed Hive + Metastore on Google Cloud Platform with Cloud SQL as the backend + database" to a Dataproc Metastore service. + + Configuration information required to start the Change Data Capture + (CDC) streams from customer's Cloud SQL database to backend database + of Dataproc Metastore. + + This must be specified. + + --cdc-password=CDC_PASSWORD + The password for the user that Datastream service should use for + the MySQL connection. + + This flag argument must be specified if any of the other + arguments in this group are specified. + + --cdc-username=CDC_USERNAME + The username that the Datastream service should use for the MySQL + connection. + + This flag argument must be specified if any of the other + arguments in this group are specified. + + --reverse-proxy-subnet=REVERSE_PROXY_SUBNET + The URL of the subnetwork resource to create the VM instance + hosting the reverse proxy in. More context in + https://cloud.google.com/datastream/docs/private-connectivity#reverse-csql-proxy + The subnetwork should reside in the network provided in the + request that Datastream will peer to and should be in the same + region as Datastream, in the following format. + "projects/{project_id}/regions/{region_id}/subnetworks/{subnetwork_id}"" + + This flag argument must be specified if any of the other + arguments in this group are specified. + + --subnet-ip-range=SUBNET_IP_RANGE + A "/29" CIDR IP range for peering with datastream + + This flag argument must be specified if any of the other + arguments in this group are specified. + + --vpc-network=VPC_NETWORK + Fully qualified name of the Cloud SQL instance's VPC network or + the shared VPC network that Datastream will peer to, in the + following format: + "projects/{project_id}/locations/global/networks/{network_id}". + More context in + https://cloud.google.com/datastream/docs/network-connectivity-options#privateconnectivity + + This flag argument must be specified if any of the other + arguments in this group are specified. + + --bucket=BUCKET + The bucket to write the intermediate stream event data in. The + bucket name must be without any prefix like "gs://". This field + is optional. If not set, the Artifacts Cloud Storage bucket is + used. + + --root-path=ROOT_PATH; default="/migration" + The root path inside the Cloud Storage bucket. The stream event + data will be written to this path. The default value is + "/migration". + + Configuration information required for Dataproc Metastore to establish + customer database connection before the cutover phase of migration. + + This must be specified. + + --connection-password=CONNECTION_PASSWORD + The password for the user that Dataproc Metastore service should + use to connect to the database. + + This flag argument must be specified if any of the other + arguments in this group are specified. + + --connection-username=CONNECTION_USERNAME + The username that Dataproc Metastore service should use to + connect to the database. + + This flag argument must be specified if any of the other + arguments in this group are specified. + + --hive-database-name=HIVE_DATABASE_NAME + The name of the hive metastore database. + + This flag argument must be specified if any of the other + arguments in this group are specified. + + --instance-connection-name=INSTANCE_CONNECTION_NAME + The Cloud SQL database connection name, in the format, + "project_id:region:instance_name" + + This flag argument must be specified if any of the other + arguments in this group are specified. + + --ip-address=IP_ADDRESS + The private IP address of the Cloud SQL instance. + + This flag argument must be specified if any of the other + arguments in this group are specified. + + --nat-subnet=NAT_SUBNET + The relative resource name of the subnetwork to be used for + Private Service Connect. Note that this cannot be a regular + subnet and is used only for NAT. More context in + https://cloud.google.com/vpc/docs/about-vpc-hosted-services#psc-subnets. + This subnet is used to publish the SOCKS5 proxy service. The + subnet size must be at least /29 and it should reside in a + network through which the Cloud SQL instance is accessible. The + resource name should be in the format, + "projects/{project_id}/regions/{region_id}/subnetworks/{subnetwork_id}" + + This flag argument must be specified if any of the other + arguments in this group are specified. + + --port=PORT + The network port of the database. + + This flag argument must be specified if any of the other + arguments in this group are specified. + + --proxy-subnet=PROXY_SUBNET + The relative resource name of the subnetwork to deploy the SOCKS5 + proxy service in. The subnetwork should reside in a network + through which the Cloud SQL instance is accessible. The resource + name should be in the format, + "projects/{project_id}/regions/{region_id}/subnetworks/{subnetwork_id}" + + This flag argument must be specified if any of the other + arguments in this group are specified. + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + +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 metastore/v1alpha API. The full documentation for + this API can be found at: https://cloud.google.com/dataproc-metastore/docs + +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 metastore services migrations start + diff --git a/gcloud/alpha/metastore/services/update b/gcloud/alpha/metastore/services/update index ec0e06176..195b18967 100644 --- a/gcloud/alpha/metastore/services/update +++ b/gcloud/alpha/metastore/services/update @@ -4,11 +4,13 @@ NAME SYNOPSIS gcloud alpha metastore services update (SERVICE : --location=LOCATION) - [--async] [--data-catalog-sync] [--endpoint-protocol=ENDPOINT_PROTOCOL] - [--port=PORT] [--update-labels=[KEY=VALUE,...]] + [--async] [--autoscaling-enabled] [--data-catalog-sync] + [--endpoint-protocol=ENDPOINT_PROTOCOL] [--port=PORT] + [--update-labels=[KEY=VALUE,...]] [--clear-labels | --remove-labels=[KEY,...]] [--instance-size=INSTANCE_SIZE | --scaling-factor=SCALING_FACTOR - | --tier=TIER] + | --tier=TIER | --max-scaling-factor=MAX_SCALING_FACTOR + --min-scaling-factor=MIN_SCALING_FACTOR] [--kerberos-principal=KERBEROS_PRINCIPAL --keytab=KEYTAB --krb5-config=KRB5_CONFIG] [--maintenance-window-day=MAINTENANCE_WINDOW_DAY @@ -76,6 +78,16 @@ FLAGS Return immediately, without waiting for the operation in progress to complete. + --autoscaling-enabled + A boolean flag to determine whether Dataproc Metastore autoscaling + should be enabled, false if unspecified. + + The default minimum and maximum scaling factors are 0.1 and 6.0, + respectively. + + The minimum and maximum scaling factors can be specified using + --min-scaling-factor and --max-scaling-factor. + --data-catalog-sync Boolean flag to determine whether or not Dataproc Metastore metadata sync to Data Catalog is enabled, false if unspecified. Mutually @@ -147,10 +159,8 @@ FLAGS Small instance size, maps to a scaling factor of 0.5. --scaling-factor=SCALING_FACTOR - The scaling factor of the service. This should be a float in the - range [0.1,6.0]. If the value is less than 1.0, then it should be a - multiple of 0.1. If the value is greater than 1.0, then it should be - a whole number. + The scaling factor of the service. Can be one of [0.1, 0.2, 0.3, 0.4, + 0.5, 0.6, 0.7, 0.8, 0.9, 1.0, 2.0, 3.0, 4.0, 5.0, 6.0]. --tier=TIER The tier of the service. TIER must be one of: @@ -164,6 +174,18 @@ FLAGS sufficient scalability for enterprise-level Dataproc Metastore workloads. + The autoscaling configuration of the Dataproc Metastore instance. + + --max-scaling-factor=MAX_SCALING_FACTOR + The maximum scaling factor allowed by the autoscaler. Can be one of + [0.1, 0.2, 0.3, 0.4, 0.5, 0.6, 0.7, 0.8, 0.9, 1.0, 2.0, 3.0, 4.0, + 5.0, 6.0]. The default value is 6.0. + + --min-scaling-factor=MIN_SCALING_FACTOR + The minimum scaling factor allowed by the autoscaler. Can be one of + [0.1, 0.2, 0.3, 0.4, 0.5, 0.6, 0.7, 0.8, 0.9, 1.0, 2.0, 3.0, 4.0, + 5.0, 6.0]. The default value is 0.1. + Information used to configure the Hive metastore service as a service principal in a Kerberos realm. diff --git a/gcloud/alpha/ml-engine/models/add-iam-policy-binding b/gcloud/alpha/ml-engine/models/add-iam-policy-binding index 8082bbfef..edb197585 100644 --- a/gcloud/alpha/ml-engine/models/add-iam-policy-binding +++ b/gcloud/alpha/ml-engine/models/add-iam-policy-binding @@ -14,28 +14,28 @@ DESCRIPTION an optional condition. EXAMPLES - To add an IAM policy binding for the role of 'roles/ml.admin' for the user - 'test-user@gmail.com' on a model with identifier 'my_model', run: + To add an IAM policy binding for the role of roles/ml.admin for the user + test-user@gmail.com on a model with identifier my_model, run: $ gcloud alpha ml-engine models add-iam-policy-binding my_model \ --member='user:test-user@gmail.com' --role='roles/ml.admin' - To add an IAM policy binding for the role of 'roles/ml.admin' to the - service account 'test-proj1@example.domain.com', run: + To add an IAM policy binding for the role of roles/ml.admin to the service + account test-proj1@example.domain.com, run: $ gcloud alpha ml-engine models add-iam-policy-binding my_model \ --member='serviceAccount:test-proj1@example.domain.com' \ --role='roles/ml.admin' - To add an IAM policy binding for the role of 'roles/ml.admin' for all - authenticated users on a model with identifier 'my_model', run: + To add an IAM policy binding for the role of roles/ml.admin for all + authenticated users on a model with identifier my_model, run: $ gcloud alpha ml-engine models add-iam-policy-binding my_model \ --member='allAuthenticatedUsers' --role='roles/ml.admin' To add an IAM policy binding that expires at the end of the year 2018 for - the role of 'roles/ml.admin' and the user 'test-user@gmail.com' on a model - with identifier 'my_model', run: + the role of roles/ml.admin and the user test-user@gmail.com on a model with + identifier my_model, run: $ gcloud alpha ml-engine models add-iam-policy-binding my_model \ --member='user:test-user@gmail.com' --role='roles/ml.admin' \ diff --git a/gcloud/alpha/ml-engine/models/remove-iam-policy-binding b/gcloud/alpha/ml-engine/models/remove-iam-policy-binding index e42f738c5..f94f2e608 100644 --- a/gcloud/alpha/ml-engine/models/remove-iam-policy-binding +++ b/gcloud/alpha/ml-engine/models/remove-iam-policy-binding @@ -15,14 +15,14 @@ DESCRIPTION a model resource. EXAMPLES - To remove an IAM policy binding for the role of 'roles/ml.admin' for the - user 'test-user@gmail.com' on model with identifier 'my_model', run: + To remove an IAM policy binding for the role of roles/ml.admin for the user + test-user@gmail.com on model with identifier my_model, run: $ gcloud alpha ml-engine models remove-iam-policy-binding my_model \ --member='user:test-user@gmail.com' --role='roles/ml.admin' - To remove an IAM policy binding for the role of 'roles/ml.admin' from all - authenticated users on model 'my_model', run: + To remove an IAM policy binding for the role of roles/ml.admin from all + authenticated users on model my_model, run: $ gcloud alpha ml-engine models remove-iam-policy-binding my_model \ --member='allAuthenticatedUsers' --role='roles/ml.admin' diff --git a/gcloud/alpha/projects/add-iam-policy-binding b/gcloud/alpha/projects/add-iam-policy-binding index c45ddb244..99f90d924 100644 --- a/gcloud/alpha/projects/add-iam-policy-binding +++ b/gcloud/alpha/projects/add-iam-policy-binding @@ -14,17 +14,16 @@ DESCRIPTION an optional condition. EXAMPLES - To add an IAM policy binding for the role of 'roles/editor' for the user - 'test-user@gmail.com' on a project with identifier 'example-project-id-1', - run: + To add an IAM policy binding for the role of roles/editor for the user + test-user@gmail.com on a project with identifier example-project-id-1, run: $ gcloud alpha projects add-iam-policy-binding \ example-project-id-1 --member='user:test-user@gmail.com' \ --role='roles/editor' - To add an IAM policy binding for the role of 'roles/editor' to the service - account 'test-proj1@example.domain.com' on a project with identifier - 'example-project-id-1', run: + To add an IAM policy binding for the role of roles/editor to the service + account test-proj1@example.domain.com on a project with identifier + example-project-id-1, run: $ gcloud alpha projects add-iam-policy-binding \ example-project-id-1 \ @@ -32,8 +31,8 @@ EXAMPLES --role='roles/editor' To add an IAM policy binding that expires at the end of the year 2021 for - the role of 'roles/browser' and the user 'test-user@gmail.com' on a project - with identifier 'example-project-id-1', run: + the role of roles/browser and the user test-user@gmail.com on a project + with identifier example-project-id-1, run: $ gcloud alpha projects add-iam-policy-binding \ example-project-id-1 --member='user:test-user@gmail.com' \ diff --git a/gcloud/alpha/projects/create b/gcloud/alpha/projects/create index 39cff2d37..006d60185 100644 --- a/gcloud/alpha/projects/create +++ b/gcloud/alpha/projects/create @@ -66,7 +66,7 @@ FLAGS --tags=[KEY=VALUE,...] List of tags KEY=VALUE pairs to bind. Each item must be expressed as - "=". + =. Example: 123/environment=production,123/costCenter=marketing diff --git a/gcloud/alpha/projects/remove-iam-policy-binding b/gcloud/alpha/projects/remove-iam-policy-binding index fdbb25639..660ffdd61 100644 --- a/gcloud/alpha/projects/remove-iam-policy-binding +++ b/gcloud/alpha/projects/remove-iam-policy-binding @@ -14,27 +14,25 @@ DESCRIPTION optional condition. EXAMPLES - To remove an IAM policy binding for the role of 'roles/editor' for the user - 'test-user@gmail.com' on project with identifier 'example-project-id-1', - run: + To remove an IAM policy binding for the role of roles/editor for the user + test-user@gmail.com on project with identifier example-project-id-1, run: $ gcloud alpha projects remove-iam-policy-binding \ example-project-id-1 --member='user:test-user@gmail.com' \ --role='roles/editor' - To remove an IAM policy binding for the role of 'roles/editor' from all - authenticated users on project 'example-project-id-1', run: + To remove an IAM policy binding for the role of roles/editor from all + authenticated users on project example-project-id-1, run: $ gcloud alpha projects remove-iam-policy-binding \ example-project-id-1 --member='allAuthenticatedUsers' \ --role='roles/editor' To remove an IAM policy binding with a condition of - expression='request.time < timestamp("2019-01-01T00:00:00Z")', - title='expires_end_of_2018', and description='Expires at midnight on - 2018-12-31' for the role of 'roles/browser' for the user - 'test-user@gmail.com' on project with identifier 'example-project-id-1', - run: + expression='request.time < timestamp("2019-01-01T00:00:00Z"), + title='expires_end_of_2018', and description=Expires at midnight on + 2018-12-31 for the role of roles/browser for the user test-user@gmail.com + on project with identifier example-project-id-1, run: $ gcloud alpha projects remove-iam-policy-binding \ example-project-id-1 --member='user:test-user@gmail.com' \ @@ -44,8 +42,8 @@ EXAMPLES tion=Expires at midnight on 2018-12-31' To remove all IAM policy bindings regardless of the condition for the role - of 'roles/browser' and for the user 'test-user@gmail.com' on project with - identifier 'example-project-id-1', run: + of roles/browser and for the user test-user@gmail.com on project with + identifier example-project-id-1, run: $ gcloud alpha projects remove-iam-policy-binding \ example-project-id-1 --member='user:test-user@gmail.com' \ diff --git a/gcloud/alpha/projects/update b/gcloud/alpha/projects/update index 407454028..de4d0d63d 100644 --- a/gcloud/alpha/projects/update +++ b/gcloud/alpha/projects/update @@ -16,7 +16,7 @@ DESCRIPTION EXAMPLES The following command updates a project with the ID example-foo-bar-1 to - have the name "Foo Bar & Grill" and removes the label dive: + have the name Foo Bar & Grill and removes the label dive: $ gcloud alpha projects update example-foo-bar-1 \ --name="Foo Bar & Grill" --remove-labels=dive diff --git a/gcloud/alpha/resource-manager/folders/create b/gcloud/alpha/resource-manager/folders/create index d29fdb839..61786366d 100644 --- a/gcloud/alpha/resource-manager/folders/create +++ b/gcloud/alpha/resource-manager/folders/create @@ -39,7 +39,7 @@ OPTIONAL FLAGS --tags=[KEY=VALUE,...] List of tags KEY=VALUE pairs to bind. Each item must be expressed as - "=". + =. Example: 123/environment=production,123/costCenter=marketing diff --git a/gcloud/alpha/services/api-keys/create b/gcloud/alpha/services/api-keys/create index d0832af29..fd75dfe43 100644 --- a/gcloud/alpha/services/api-keys/create +++ b/gcloud/alpha/services/api-keys/create @@ -59,11 +59,9 @@ EXAMPLES The content of 'my-flags.yaml' is as following: - --api-target: - service: - - "foo.service.com" + service: "foo.service.com" - --api-target: - service: - - "bar.service.com" + service: "bar.service.com" methods: - "foomethod" - "barmethod" diff --git a/gcloud/alpha/spanner/instances/help b/gcloud/alpha/spanner/instances/help index cc8bd8162..f3de945c3 100644 --- a/gcloud/alpha/spanner/instances/help +++ b/gcloud/alpha/spanner/instances/help @@ -39,6 +39,10 @@ COMMANDS list (ALPHA) List the Cloud Spanner instances in this project. + move + (ALPHA) Move the Cloud Spanner instance to the specified instance + config. + remove-iam-policy-binding (ALPHA) Remove IAM policy binding of a Cloud Spanner instance. diff --git a/gcloud/alpha/spanner/instances/move b/gcloud/alpha/spanner/instances/move new file mode 100644 index 000000000..67210e8d5 --- /dev/null +++ b/gcloud/alpha/spanner/instances/move @@ -0,0 +1,42 @@ +NAME + gcloud alpha spanner instances move - move the Cloud Spanner instance to + the specified instance config + +SYNOPSIS + gcloud alpha spanner instances move INSTANCE --target-config=TARGET_CONFIG + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Move the Cloud Spanner instance to the specified instance config. + +EXAMPLES + To move the Cloud Spanner instance to the target instance configuration, + run: $ gcloud alpha spanner instances move my-instance-id \ + --target-config=nam3 + +POSITIONAL ARGUMENTS + INSTANCE + Cloud Spanner instance ID. + +REQUIRED FLAGS + --target-config=TARGET_CONFIG + Target Instance configuration to move the instances. + +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. These variants are also available: + + $ gcloud spanner instances move + + $ gcloud beta spanner instances move + diff --git a/gcloud/backup-dr/management-servers/describe b/gcloud/backup-dr/management-servers/describe index 9362904fd..836f02ac1 100644 --- a/gcloud/backup-dr/management-servers/describe +++ b/gcloud/backup-dr/management-servers/describe @@ -16,8 +16,8 @@ EXAMPLES $ gcloud backup-dr management-servers describe MANAGEMENT_SERVER POSITIONAL ARGUMENTS - ManagementServer resource - Name of the management server to describe. The - arguments in this group can be used to specify the attributes of this + Management server resource - Name of the management server 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. @@ -30,8 +30,8 @@ POSITIONAL ARGUMENTS This must be specified. MANAGEMENT_SERVER - ID of the managementServer or fully qualified identifier for the - managementServer. + ID of the management_server or fully qualified identifier for the + management_server. To set the management_server attribute: ▸ provide the argument management_server on the command line. diff --git a/gcloud/backup-dr/management-servers/list b/gcloud/backup-dr/management-servers/list index 825348e10..e6aa690e4 100644 --- a/gcloud/backup-dr/management-servers/list +++ b/gcloud/backup-dr/management-servers/list @@ -28,7 +28,7 @@ FLAGS To set the project attribute: ◆ provide the argument --location on the command line with a fully specified name; - ◆ use default global location with a fully specified name; + ◆ default is all locations with a fully specified name; ◆ set the property core/project; ◆ provide the argument --project on the command line. @@ -37,7 +37,7 @@ FLAGS To set the location attribute: ▸ provide the argument --location on the command line; - ▸ use default global location . + ▸ default is all locations . LIST COMMAND FLAGS --filter=EXPRESSION diff --git a/gcloud/batch/tasks/list b/gcloud/batch/tasks/list index fd2d08024..054d4abe7 100644 --- a/gcloud/batch/tasks/list +++ b/gcloud/batch/tasks/list @@ -16,10 +16,11 @@ DESCRIPTION ▪ The active account does not have permission to access the given job EXAMPLES - To print all tasks in the group0 of job with name + To print all tasks in the job with name projects/foo/locations/us-central1/jobs/bar, run: - $ gcloud batch tasks list projects/foo/locations/us-central1/jobs/bar + $ gcloud batch tasks list \ + --job projects/foo/locations/us-central1/jobs/bar REQUIRED FLAGS Job resource - The Batch job resource. If not specified,the current diff --git a/gcloud/beta/ai-platform/models/add-iam-policy-binding b/gcloud/beta/ai-platform/models/add-iam-policy-binding index 7dae4590a..b620b74b2 100644 --- a/gcloud/beta/ai-platform/models/add-iam-policy-binding +++ b/gcloud/beta/ai-platform/models/add-iam-policy-binding @@ -10,21 +10,21 @@ DESCRIPTION (BETA) Add IAM policy binding to a model. EXAMPLES - To add an IAM policy binding for the role of 'roles/ml.admin' for the user - 'test-user@gmail.com' on a model with identifier 'my_model', run: + To add an IAM policy binding for the role of roles/ml.admin for the user + test-user@gmail.com on a model with identifier my_model, run: $ gcloud beta ai-platform models add-iam-policy-binding my_model \ --member='user:test-user@gmail.com' --role='roles/ml.admin' - To add an IAM policy binding for the role of 'roles/ml.admin' to the - service account 'test-proj1@example.domain.com', run: + To add an IAM policy binding for the role of roles/ml.admin to the service + account test-proj1@example.domain.com, run: $ gcloud beta ai-platform models add-iam-policy-binding my_model \ --member='serviceAccount:test-proj1@example.domain.com' \ --role='roles/ml.admin' - To add an IAM policy binding for the role of 'roles/ml.admin' for all - authenticated users on a model with identifier 'my_model', run: + To add an IAM policy binding for the role of roles/ml.admin for all + authenticated users on a model with identifier my_model, run: $ gcloud beta ai-platform models add-iam-policy-binding my_model \ --member='allAuthenticatedUsers' --role='roles/ml.admin' diff --git a/gcloud/beta/ai-platform/models/remove-iam-policy-binding b/gcloud/beta/ai-platform/models/remove-iam-policy-binding index c4ceed768..4c7775fd2 100644 --- a/gcloud/beta/ai-platform/models/remove-iam-policy-binding +++ b/gcloud/beta/ai-platform/models/remove-iam-policy-binding @@ -13,15 +13,15 @@ DESCRIPTION resource. EXAMPLES - To remove an IAM policy binding for the role of 'roles/ml.admin' for the - user 'test-user@gmail.com' on model with identifier 'my_model', run: + To remove an IAM policy binding for the role of roles/ml.admin for the user + test-user@gmail.com on model with identifier my_model, run: $ gcloud beta ai-platform models remove-iam-policy-binding \ my_model --member='user:test-user@gmail.com' \ --role='roles/ml.admin' - To remove an IAM policy binding for the role of 'roles/ml.admin' from all - authenticated users on model 'my_model', run: + To remove an IAM policy binding for the role of roles/ml.admin from all + authenticated users on model my_model, run: $ gcloud beta ai-platform models remove-iam-policy-binding \ my_model --member='allAuthenticatedUsers' \ diff --git a/gcloud/beta/ai/custom-jobs/create b/gcloud/beta/ai/custom-jobs/create index 5b598aa0b..039308554 100644 --- a/gcloud/beta/ai/custom-jobs/create +++ b/gcloud/beta/ai/custom-jobs/create @@ -7,6 +7,7 @@ SYNOPSIS [--args=[ARG,...]] [--command=[COMMAND,...]] [--enable-dashboard-access] [--enable-web-access] [--labels=[KEY=VALUE,...]] [--network=NETWORK] + [--persistent-resource-id=PERSISTENT_RESOURCE_ID] [--python-package-uris=[PYTHON_PACKAGE_URIS,...]] [--region=REGION] [--service-account=SERVICE_ACCOUNT] [--kms-key=KMS_KEY : --kms-keyring=KMS_KEYRING @@ -194,6 +195,15 @@ OPTIONAL FLAGS peered with. Private services access must already have been configured. If unspecified, the Job is not peered with any network. + --persistent-resource-id=PERSISTENT_RESOURCE_ID + The name of the persistent resource from the same project and region on + which to run this custom job. + + If this is specified, the job will be run on existing machines held by + the PersistentResource instead of on-demand short-lived machines. The + network and CMEK configs on the job should be consistent with those on + the PersistentResource, otherwise, the job will be rejected. + --python-package-uris=[PYTHON_PACKAGE_URIS,...] The common Python package URIs to be used for training with a pre-built container image. e.g. --python-package-uri=path1,path2 If you are using diff --git a/gcloud/beta/ai/help b/gcloud/beta/ai/help index b5a2b66c9..2af005b14 100644 --- a/gcloud/beta/ai/help +++ b/gcloud/beta/ai/help @@ -40,7 +40,7 @@ GROUPS (BETA) Manage Vertex AI operations. persistent-resources - (BETA) Create and manage Vertex AI Persistent Resources. + (BETA) Create and manage Vertex AI rersistent resources. tensorboard-experiments (BETA) Manage Vertex AI Tensorboard experiments. diff --git a/gcloud/beta/ai/persistent-resources/create b/gcloud/beta/ai/persistent-resources/create index 51b5fff67..efd8b3f88 100644 --- a/gcloud/beta/ai/persistent-resources/create +++ b/gcloud/beta/ai/persistent-resources/create @@ -187,8 +187,10 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud ai persistent-resources create $ gcloud alpha ai persistent-resources create diff --git a/gcloud/beta/ai/persistent-resources/delete b/gcloud/beta/ai/persistent-resources/delete index 300d9a5cd..303ec2562 100644 --- a/gcloud/beta/ai/persistent-resources/delete +++ b/gcloud/beta/ai/persistent-resources/delete @@ -60,8 +60,10 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud ai persistent-resources delete $ gcloud alpha ai persistent-resources delete diff --git a/gcloud/beta/ai/persistent-resources/describe b/gcloud/beta/ai/persistent-resources/describe index 419fd2157..f88abc060 100644 --- a/gcloud/beta/ai/persistent-resources/describe +++ b/gcloud/beta/ai/persistent-resources/describe @@ -56,8 +56,10 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud ai persistent-resources describe $ gcloud alpha ai persistent-resources describe diff --git a/gcloud/beta/ai/persistent-resources/help b/gcloud/beta/ai/persistent-resources/help index 88b8b3aca..5fbb7ad83 100644 --- a/gcloud/beta/ai/persistent-resources/help +++ b/gcloud/beta/ai/persistent-resources/help @@ -1,12 +1,12 @@ NAME gcloud beta ai persistent-resources - create and manage Vertex AI - Persistent Resources + rersistent resources SYNOPSIS gcloud beta ai persistent-resources COMMAND [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) Create and manage Vertex AI Persistent Resources. + (BETA) Create and manage Vertex AI rersistent resources. GCLOUD WIDE FLAGS These flags are available to all commands: --help. @@ -29,9 +29,14 @@ COMMANDS list (BETA) Lists the active persistent resources. + reboot + (BETA) Reboot an active Persistent Resource. + NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud ai persistent-resources $ gcloud alpha ai persistent-resources diff --git a/gcloud/beta/ai/persistent-resources/list b/gcloud/beta/ai/persistent-resources/list index 8d352e77f..d946dc479 100644 --- a/gcloud/beta/ai/persistent-resources/list +++ b/gcloud/beta/ai/persistent-resources/list @@ -77,8 +77,10 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud ai persistent-resources list $ gcloud alpha ai persistent-resources list diff --git a/gcloud/beta/ai/persistent-resources/reboot b/gcloud/beta/ai/persistent-resources/reboot new file mode 100644 index 000000000..6413e89ee --- /dev/null +++ b/gcloud/beta/ai/persistent-resources/reboot @@ -0,0 +1,65 @@ +NAME + gcloud beta ai persistent-resources reboot - reboot an active Persistent + Resource + +SYNOPSIS + gcloud beta ai persistent-resources reboot + (PERSISTENT_RESOURCE : --region=REGION) [GCLOUD_WIDE_FLAG ...] + +EXAMPLES + To reboot a persistent resource 123 under project example in region + us-central1, run: + + $ gcloud beta ai persistent-resources reboot 123 --project=example \ + --region=us-central1 + +POSITIONAL ARGUMENTS + Persistent resource resource - The persistent resource to reboot. 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 beta and might change without notice. These + variants are also available: + + $ gcloud ai persistent-resources reboot + + $ gcloud alpha ai persistent-resources reboot + diff --git a/gcloud/beta/alloydb/clusters/create b/gcloud/beta/alloydb/clusters/create index dd0f9d9dd..7ce9fff0d 100644 --- a/gcloud/beta/alloydb/clusters/create +++ b/gcloud/beta/alloydb/clusters/create @@ -5,7 +5,8 @@ NAME SYNOPSIS gcloud beta alloydb clusters create CLUSTER --password=PASSWORD --region=REGION [--allocated-ip-range-name=ALLOCATED_IP_RANGE_NAME] - [--async] [--database-version=DATABASE_VERSION] [--network=NETWORK] + [--async] [--database-version=DATABASE_VERSION] + [--enable-private-service-connect] [--network=NETWORK] [--continuous-backup-recovery-window-days=RECOVERY_PERIOD --enable-continuous-backup [--continuous-backup-encryption-key=CONTINUOUS_BACKUP_ENCRYPTION_KEY @@ -58,6 +59,9 @@ OPTIONAL FLAGS Database version of the cluster. DATABASE_VERSION must be one of: POSTGRES_14, POSTGRES_15. + --enable-private-service-connect + Enable Private Service Connect (PSC) connectivity for the cluster. + --network=NETWORK Network in the current project that the instance will be part of. To specify using a network with a shared VPC, use the full URL of the diff --git a/gcloud/beta/alloydb/clusters/restore b/gcloud/beta/alloydb/clusters/restore index 3d5b211ec..d134e6212 100644 --- a/gcloud/beta/alloydb/clusters/restore +++ b/gcloud/beta/alloydb/clusters/restore @@ -7,7 +7,7 @@ SYNOPSIS (--backup=BACKUP | --point-in-time=POINT_IN_TIME --source-cluster=SOURCE_CLUSTER) [--allocated-ip-range-name=ALLOCATED_IP_RANGE_NAME] [--async] - [--network=NETWORK] + [--enable-private-service-connect] [--network=NETWORK] [--kms-key=KMS_KEY : --kms-keyring=KMS_KEYRING --kms-location=KMS_LOCATION --kms-project=KMS_PROJECT] [GCLOUD_WIDE_FLAG ...] @@ -81,6 +81,9 @@ OPTIONAL FLAGS Return immediately, without waiting for the operation in progress to complete. + --enable-private-service-connect + Enable Private Service Connect (PSC) connectivity for the cluster. + --network=NETWORK Network in the current project that the instance will be part of. To specify using a network with a shared VPC, use the full URL of the diff --git a/gcloud/beta/alloydb/clusters/update b/gcloud/beta/alloydb/clusters/update index 09fdc839e..0ecdab708 100644 --- a/gcloud/beta/alloydb/clusters/update +++ b/gcloud/beta/alloydb/clusters/update @@ -5,11 +5,11 @@ NAME SYNOPSIS gcloud beta alloydb clusters update CLUSTER --region=REGION [--async] [--clear-automated-backup | --disable-automated-backup - | [--automated-backup-days-of-week=[DAYS_OF_WEEK,...] + | --automated-backup-days-of-week=[DAYS_OF_WEEK,...] --automated-backup-start-times=[START_TIMES,...] - : --automated-backup-window=TIMEOUT_PERIOD + --automated-backup-window=TIMEOUT_PERIOD [--automated-backup-encryption-key=AUTOMATED_BACKUP_ENCRYPTION_KEY - : --automated-backup-encryption-key-keyring=AUTOMATED_BACKUP_ENCRYPTION_KEY_KEYRING --automated-backup-encryption-key-location=AUTOMATED_BACKUP_ENCRYPTION_KEY_LOCATION --automated-backup-encryption-key-project=AUTOMATED_BACKUP_ENCRYPTION_KEY_PROJECT] --automated-backup-retention-count=RETENTION_COUNT | --automated-backup-retention-period=RETENTION_PERIOD]] + : --automated-backup-encryption-key-keyring=AUTOMATED_BACKUP_ENCRYPTION_KEY_KEYRING --automated-backup-encryption-key-location=AUTOMATED_BACKUP_ENCRYPTION_KEY_LOCATION --automated-backup-encryption-key-project=AUTOMATED_BACKUP_ENCRYPTION_KEY_PROJECT] --automated-backup-retention-count=RETENTION_COUNT | --automated-backup-retention-period=RETENTION_PERIOD] [--continuous-backup-recovery-window-days=RECOVERY_PERIOD --enable-continuous-backup --clear-continuous-backup-encryption-key | [--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]] @@ -60,18 +60,12 @@ OPTIONAL FLAGS DAYS_OF_WEEK must be one of: MONDAY, TUESDAY, WEDNESDAY, THURSDAY, FRIDAY, SATURDAY, SUNDAY. - This flag argument must be specified if any of the other arguments - in this group are specified. - --automated-backup-start-times=[START_TIMES,...] Comma-separated list of times during the day to start a backup. At least one start time must be provided. The start times are assumed to be in UTC and required to be an exact hour in the format HH:00. (e.g., --automated-backup-start-times=01:00,13:00) - This flag argument must be specified if any of the other arguments - in this group are specified. - --automated-backup-window=TIMEOUT_PERIOD The length of the time window beginning at start time during which a backup can be taken. If a backup does not succeed within this diff --git a/gcloud/beta/alloydb/instances/create b/gcloud/beta/alloydb/instances/create index 832da2a43..c3e29cd2d 100644 --- a/gcloud/beta/alloydb/instances/create +++ b/gcloud/beta/alloydb/instances/create @@ -5,6 +5,7 @@ NAME SYNOPSIS gcloud beta alloydb instances create INSTANCE --cluster=CLUSTER --cpu-count=CPU_COUNT --instance-type=INSTANCE_TYPE --region=REGION + [--allowed-psc-projects=[ALLOWED_PSC_PROJECTS,...]] [--assign-inbound-public-ip=ASSIGN_INBOUND_PUBLIC_IP] [--async] [--availability-type=AVAILABILITY_TYPE] [--database-flags=FLAG=VALUE,[FLAG=VALUE,...]] @@ -63,6 +64,12 @@ REQUIRED FLAGS regions at https://cloud.google.com/sql/docs/instance-locations. OPTIONAL FLAGS + --allowed-psc-projects=[ALLOWED_PSC_PROJECTS,...] + Comma-separated list of allowed consumer projects to create endpoints + for Private Service Connect (PSC) connectivity for the instance. Only + instances in PSC-enabled clusters are allowed to set this field.(e.g., + --allowed-psc-projects=project1,12345678,project2) + --assign-inbound-public-ip=ASSIGN_INBOUND_PUBLIC_IP Specify to enable or disable public IP on an instance. On instance creation only disabling public IP is allowed. If you want to enable diff --git a/gcloud/beta/alloydb/instances/update b/gcloud/beta/alloydb/instances/update index acbc395c4..25e8068a0 100644 --- a/gcloud/beta/alloydb/instances/update +++ b/gcloud/beta/alloydb/instances/update @@ -4,8 +4,9 @@ NAME SYNOPSIS gcloud beta alloydb instances update INSTANCE --cluster=CLUSTER - --region=REGION [--assign-inbound-public-ip=ASSIGN_INBOUND_PUBLIC_IP] - [--async] [--authorized-external-networks=[AUTHORIZED_NETWORK,...]] + --region=REGION [--allowed-psc-projects=[ALLOWED_PSC_PROJECTS,...]] + [--assign-inbound-public-ip=ASSIGN_INBOUND_PUBLIC_IP] [--async] + [--authorized-external-networks=[AUTHORIZED_NETWORK,...]] [--availability-type=AVAILABILITY_TYPE] [--cpu-count=CPU_COUNT] [--database-flags=FLAG=VALUE,[FLAG=VALUE,...]] [--insights-config-query-plans-per-minute=INSIGHTS_CONFIG_QUERY_PLANS_PER_MINUTE] @@ -39,6 +40,12 @@ REQUIRED FLAGS regions at https://cloud.google.com/sql/docs/instance-locations. OPTIONAL FLAGS + --allowed-psc-projects=[ALLOWED_PSC_PROJECTS,...] + Comma-separated list of allowed consumer projects to create endpoints + for Private Service Connect (PSC) connectivity for the instance. Only + instances in PSC-enabled clusters are allowed to set this field.(e.g., + --allowed-psc-projects=project1,12345678,project2) + --assign-inbound-public-ip=ASSIGN_INBOUND_PUBLIC_IP Specify to enable or disable public IP on an instance. ASSIGN_INBOUND_PUBLIC_IP must be one of: diff --git a/gcloud/beta/backup-dr/management-servers/describe b/gcloud/beta/backup-dr/management-servers/describe index 2b829bb39..9421095a0 100644 --- a/gcloud/beta/backup-dr/management-servers/describe +++ b/gcloud/beta/backup-dr/management-servers/describe @@ -16,8 +16,8 @@ EXAMPLES $ gcloud beta backup-dr management-servers describe MANAGEMENT_SERVER POSITIONAL ARGUMENTS - ManagementServer resource - Name of the management server to describe. The - arguments in this group can be used to specify the attributes of this + Management server resource - Name of the management server 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. @@ -30,8 +30,8 @@ POSITIONAL ARGUMENTS This must be specified. MANAGEMENT_SERVER - ID of the managementServer or fully qualified identifier for the - managementServer. + ID of the management_server or fully qualified identifier for the + management_server. To set the management_server attribute: ▸ provide the argument management_server on the command line. diff --git a/gcloud/beta/backup-dr/management-servers/list b/gcloud/beta/backup-dr/management-servers/list index 8c7e93231..9328191fc 100644 --- a/gcloud/beta/backup-dr/management-servers/list +++ b/gcloud/beta/backup-dr/management-servers/list @@ -29,7 +29,7 @@ FLAGS To set the project attribute: ◆ provide the argument --location on the command line with a fully specified name; - ◆ use default global location with a fully specified name; + ◆ default is all locations with a fully specified name; ◆ set the property core/project; ◆ provide the argument --project on the command line. @@ -38,7 +38,7 @@ FLAGS To set the location attribute: ▸ provide the argument --location on the command line; - ▸ use default global location . + ▸ default is all locations . LIST COMMAND FLAGS --filter=EXPRESSION diff --git a/gcloud/beta/batch/tasks/list b/gcloud/beta/batch/tasks/list index 7a4a57db0..0213a73ad 100644 --- a/gcloud/beta/batch/tasks/list +++ b/gcloud/beta/batch/tasks/list @@ -16,11 +16,11 @@ DESCRIPTION ▪ The active account does not have permission to access the given job EXAMPLES - To print all tasks in the group0 of job with name + To print all tasks in the job with name projects/foo/locations/us-central1/jobs/bar, run: $ gcloud beta batch tasks list \ - projects/foo/locations/us-central1/jobs/bar + --job projects/foo/locations/us-central1/jobs/bar REQUIRED FLAGS Job resource - The Batch job resource. If not specified,the current diff --git a/gcloud/beta/builds/submit b/gcloud/beta/builds/submit index ce1396902..78a1b9571 100644 --- a/gcloud/beta/builds/submit +++ b/gcloud/beta/builds/submit @@ -8,9 +8,11 @@ SYNOPSIS [--gcs-source-staging-dir=GCS_SOURCE_STAGING_DIR] [--git-source-dir=GIT_SOURCE_DIR] [--git-source-revision=GIT_SOURCE_REVISION] [--ignore-file=IGNORE_FILE] - [--machine-type=MACHINE_TYPE] [--region=REGION] [--revision=REVISION] - [--service-account=SERVICE_ACCOUNT] [--substitutions=[KEY=VALUE,...]] - [--suppress-logs] [--timeout=TIMEOUT] [--worker-pool=WORKER_POOL] + [--machine-type=MACHINE_TYPE] + [--polling-interval=POLLING_INTERVAL; default=1] [--region=REGION] + [--revision=REVISION] [--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 ...] @@ -141,6 +143,9 @@ FLAGS Machine type used to run the build. MACHINE_TYPE must be one of: e2-highcpu-32, e2-highcpu-8, e2-medium, n1-highcpu-32, n1-highcpu-8. + --polling-interval=POLLING_INTERVAL; default=1 + Amount of time in seconds to wait between polling build status. + --region=REGION The region of the Cloud Build Service to use. Must be set to a supported region name (e.g. us-central1). If unset, builds/region, diff --git a/gcloud/beta/certificate-manager/trust-configs/create b/gcloud/beta/certificate-manager/trust-configs/create index dbc9ebdc2..aa97d0c36 100644 --- a/gcloud/beta/certificate-manager/trust-configs/create +++ b/gcloud/beta/certificate-manager/trust-configs/create @@ -4,8 +4,9 @@ NAME SYNOPSIS gcloud beta certificate-manager trust-configs create (TRUST_CONFIG : --location=LOCATION) - --trust-store=[intermediate-cas=INTERMEDIATE-CAS], - [trust-anchors=TRUST-ANCHORS] [--async] [--description=DESCRIPTION] + (--allowlisted-certificates=[ALLOWLISTED_CERTIFICATES,...] + --trust-store=[intermediate-cas=INTERMEDIATE-CAS], + [trust-anchors=TRUST-ANCHORS]) [--async] [--description=DESCRIPTION] [--labels=[KEY=VALUE,...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -54,20 +55,33 @@ POSITIONAL ARGUMENTS ▸ default value of location is [global]. REQUIRED FLAGS - --trust-store=[intermediate-cas=INTERMEDIATE-CAS],[trust-anchors=TRUST-ANCHORS] - Trust Store with the given trust anchor and intermediate CA PEM-encoded - certificates. Certificates should be provided in files. For multiple - file names, separate them by a semicolon (';') and quote them ('"'). - One file can contain multiple certificates. Intermediate CAs are - optional. + At least one of these must be specified: - Examples: + --allowlisted-certificates=[ALLOWLISTED_CERTIFICATES,...] + Allowlisted PEM-encoded certificates. Certificates should be provided + in files. For multiple file names, separate them by a comma (','). + One file can contain multiple certificates. - Single files: --trust-store trust-anchors=ta.pem,intermediate-cas=ica.pem + Examples: - No intermediate CAs: --trust-store trust-anchors=ta.pem + Single file: --allowlisted-certificates=ac.pem - Multiple files: --trust-store trust-anchors="ta1.pem;ta2.pem",intermediate-cas="ica1.pem;ica2.pem" + Multiple files: --allowlisted-certificates=ac1.pem,ac2.pem + + --trust-store=[intermediate-cas=INTERMEDIATE-CAS],[trust-anchors=TRUST-ANCHORS] + Trust Store with the given trust anchor and intermediate CA + PEM-encoded certificates. Certificates should be provided in files. + For multiple file names, separate them by a semicolon (';') and quote + them ('"'). One file can contain multiple certificates. Intermediate + CAs are optional. + + Examples: + + Single files: --trust-store trust-anchors=ta.pem,intermediate-cas=ica.pem + + No intermediate CAs: --trust-store trust-anchors=ta.pem + + Multiple files: --trust-store trust-anchors="ta1.pem;ta2.pem",intermediate-cas="ica1.pem;ica2.pem" OPTIONAL FLAGS --async diff --git a/gcloud/beta/certificate-manager/trust-configs/update b/gcloud/beta/certificate-manager/trust-configs/update index ccf793c98..e9faab5ec 100644 --- a/gcloud/beta/certificate-manager/trust-configs/update +++ b/gcloud/beta/certificate-manager/trust-configs/update @@ -3,11 +3,15 @@ NAME SYNOPSIS gcloud beta certificate-manager trust-configs update - (TRUST_CONFIG : --location=LOCATION) [--async] - [--description=DESCRIPTION] + (TRUST_CONFIG : --location=LOCATION) + [--add-allowlisted-certificates=[ADD_ALLOWLISTED_CERTIFICATES,...]] + [--async] [--description=DESCRIPTION] [--trust-store=[intermediate-cas=INTERMEDIATE-CAS], [trust-anchors=TRUST-ANCHORS]] [--update-labels=[KEY=VALUE,...]] - [--clear-labels | --remove-labels=[KEY,...]] [GCLOUD_WIDE_FLAG ...] + [--clear-allowlisted-certificates + | --remove-allowlisted-certificates=[REMOVE_ALLOWLISTED_CERTIFICATES, + ...]] [--clear-labels | --remove-labels=[KEY,...]] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) Update a TrustConfig. @@ -56,6 +60,17 @@ POSITIONAL ARGUMENTS ▸ default value of location is [global]. FLAGS + --add-allowlisted-certificates=[ADD_ALLOWLISTED_CERTIFICATES,...] + Add allowlisted PEM-encoded certificates. Certificates should be + provided in files. For multiple file names, separate them by a comma + (','). One file can contain multiple certificates. + + Examples: + + Single file: --add-allowlisted-certificates=ac.pem + + Multiple files: --add-allowlisted-certificates=ac1.pem,ac2.pem + --async Return immediately, without waiting for the operation in progress to complete. @@ -87,6 +102,22 @@ FLAGS contain only hyphens (-), underscores (_), lowercase characters, and numbers. + At most one of these can be specified: + + --clear-allowlisted-certificates + Clear all allowlisted certificates. + + --remove-allowlisted-certificates=[REMOVE_ALLOWLISTED_CERTIFICATES,...] + Remove allowlisted PEM-encoded certificates. Certificates should be + provided in files. For multiple file names, separate them by a comma + (','). One file can contain multiple certificates. + + Examples: + + Single file: --remove-allowlisted-certificates=ac.pem + + Multiple files: --remove-allowlisted-certificates=ac1.pem,ac2.pem + At most one of these can be specified: --clear-labels diff --git a/gcloud/beta/compute/service-attachments/create b/gcloud/beta/compute/service-attachments/create index 2776738c0..677e928f7 100644 --- a/gcloud/beta/compute/service-attachments/create +++ b/gcloud/beta/compute/service-attachments/create @@ -5,7 +5,8 @@ NAME SYNOPSIS gcloud beta compute service-attachments create NAME --nat-subnets=NAT_SUBNETS,[NAT_SUBNETS,...] - --producer-forwarding-rule=PRODUCER_FORWARDING_RULE + (--producer-forwarding-rule=PRODUCER_FORWARDING_RULE + | --target-service=TARGET_SERVICE) [--connection-preference=CONNECTION_PREFERENCE; default="ACCEPT_AUTOMATIC"] [--consumer-accept-list=[PROJECT_OR_NETWORK=LIMIT,...]] @@ -50,8 +51,13 @@ REQUIRED FLAGS --nat-subnets=NAT_SUBNETS,[NAT_SUBNETS,...] The subnetworks provided by service producer to use for NAT - --producer-forwarding-rule=PRODUCER_FORWARDING_RULE - Target forwarding rule that receives forwarded traffic. + Exactly one of these must be specified: + + --producer-forwarding-rule=PRODUCER_FORWARDING_RULE + Target forwarding rule that receives forwarded traffic. + + --target-service=TARGET_SERVICE + URL of the target service that receives forwarded traffic. OPTIONAL FLAGS --connection-preference=CONNECTION_PREFERENCE; default="ACCEPT_AUTOMATIC" diff --git a/gcloud/beta/compute/vpn-gateways/create b/gcloud/beta/compute/vpn-gateways/create index be760a056..c72eeccfe 100644 --- a/gcloud/beta/compute/vpn-gateways/create +++ b/gcloud/beta/compute/vpn-gateways/create @@ -37,8 +37,9 @@ OPTIONAL FLAGS An optional, textual description for the VPN gateway. --gateway-ip-version=GATEWAY_IP_VERSION - The IP family of the gateway IPs for the HA-VPN gateway interfaces. If - not specified, IPV4 will be used. GATEWAY_IP_VERSION must be one of: + IP version of the HA VPN gateway. You must specify either IPv4 or IPv6. + If you do not specify this field, every HA VPN gateway interface will + be configured with an IPv4 address. GATEWAY_IP_VERSION must be one of: IPV4 Every HA-VPN gateway interface is configured with an IPv4 address. diff --git a/gcloud/beta/config/get b/gcloud/beta/config/get index 7d286f8ea..68747d0e4 100644 --- a/gcloud/beta/config/get +++ b/gcloud/beta/config/get @@ -370,10 +370,6 @@ AVAILABLE PROPERTIES Overrides API endpoint for gcloud eventarc publish command group. Defaults to https://eventarcpublishing.googleapis.com/ - events - Overrides API endpoint for gcloud events command group. Defaults to - https://events.googleapis.com/ - faultinjectiontesting Overrides API endpoint for gcloud fault-injection command group. Defaults to https://faultinjectiontesting.googleapis.com/ diff --git a/gcloud/beta/config/help b/gcloud/beta/config/help index 793209a8c..24066c21e 100644 --- a/gcloud/beta/config/help +++ b/gcloud/beta/config/help @@ -402,10 +402,6 @@ AVAILABLE PROPERTIES Overrides API endpoint for gcloud eventarc publish command group. Defaults to https://eventarcpublishing.googleapis.com/ - events - Overrides API endpoint for gcloud events command group. Defaults to - https://events.googleapis.com/ - faultinjectiontesting Overrides API endpoint for gcloud fault-injection command group. Defaults to https://faultinjectiontesting.googleapis.com/ diff --git a/gcloud/beta/config/list b/gcloud/beta/config/list index 0909d4a6e..02d8f4a60 100644 --- a/gcloud/beta/config/list +++ b/gcloud/beta/config/list @@ -414,10 +414,6 @@ AVAILABLE PROPERTIES Overrides API endpoint for gcloud eventarc publish command group. Defaults to https://eventarcpublishing.googleapis.com/ - events - Overrides API endpoint for gcloud events command group. Defaults to - https://events.googleapis.com/ - faultinjectiontesting Overrides API endpoint for gcloud fault-injection command group. Defaults to https://faultinjectiontesting.googleapis.com/ diff --git a/gcloud/beta/config/set b/gcloud/beta/config/set index 4c458c70a..ce7e3b761 100644 --- a/gcloud/beta/config/set +++ b/gcloud/beta/config/set @@ -417,10 +417,6 @@ AVAILABLE PROPERTIES Overrides API endpoint for gcloud eventarc publish command group. Defaults to https://eventarcpublishing.googleapis.com/ - events - Overrides API endpoint for gcloud events command group. Defaults to - https://events.googleapis.com/ - faultinjectiontesting Overrides API endpoint for gcloud fault-injection command group. Defaults to https://faultinjectiontesting.googleapis.com/ diff --git a/gcloud/beta/config/unset b/gcloud/beta/config/unset index dfd28f98a..dea1b2ec4 100644 --- a/gcloud/beta/config/unset +++ b/gcloud/beta/config/unset @@ -378,10 +378,6 @@ AVAILABLE PROPERTIES Overrides API endpoint for gcloud eventarc publish command group. Defaults to https://eventarcpublishing.googleapis.com/ - events - Overrides API endpoint for gcloud events command group. Defaults to - https://events.googleapis.com/ - faultinjectiontesting Overrides API endpoint for gcloud fault-injection command group. Defaults to https://faultinjectiontesting.googleapis.com/ diff --git a/gcloud/beta/container/backup-restore/backup-plans/create b/gcloud/beta/container/backup-restore/backup-plans/create index 166e2bcbb..b3c34536c 100644 --- a/gcloud/beta/container/backup-restore/backup-plans/create +++ b/gcloud/beta/container/backup-restore/backup-plans/create @@ -122,8 +122,9 @@ OPTIONAL FLAGS Number of days after which a backup produced via this plan is automatically deleted. - If not set (value is 0), backups are not automatically deleted. If set, - must be greater than the value for backup_delete_lock_days. + Must be less than or equal to 365 days. If not set (value is 0), + backups are not automatically deleted. If set, must be greater than the + value for backup_delete_lock_days. --locked If set, subsequent updates are not allowed to the backup plan's diff --git a/gcloud/beta/container/backup-restore/backup-plans/update b/gcloud/beta/container/backup-restore/backup-plans/update index 13863e147..4eb0a6c1d 100644 --- a/gcloud/beta/container/backup-restore/backup-plans/update +++ b/gcloud/beta/container/backup-restore/backup-plans/update @@ -118,8 +118,9 @@ FLAGS Number of days after which a backup produced via this plan is automatically deleted. - If not set (value is 0), backups are not automatically deleted. If set, - must be greater than the value for backup_delete_lock_days. + Must be less than or equal to 365 days. If not set (value is 0), + backups are not automatically deleted. If set, must be greater than the + value for backup_delete_lock_days. --locked If set, subsequent updates are not allowed to the backup plan's diff --git a/gcloud/beta/domains/registrations/configure/contacts b/gcloud/beta/domains/registrations/configure/contacts index 9e74ded1e..49f1fb863 100644 --- a/gcloud/beta/domains/registrations/configure/contacts +++ b/gcloud/beta/domains/registrations/configure/contacts @@ -16,6 +16,17 @@ DESCRIPTION the registrant before they take effect. In order to resend the email, execute this command again. + NOTE: Please consider carefully any changes to contact privacy settings + when changing from "redacted-contact-data" to "public-contact-data." There + may be a delay in reflecting updates you make to registrant contact + information such that any changes you make to contact privacy (including + from "redacted-contact-data" to "public-contact-data") will be applied + without delay but changes to registrant contact information may take a + limited time to be publicized. This means that changes to contact privacy + from "redacted-contact-data" to "public-contact-data" may make the previous + registrant contact data public until the modified registrant contact + details are published. + EXAMPLES To start an interactive flow to configure contact settings for example.com, run: diff --git a/gcloud/beta/eventarc/attributes/help b/gcloud/beta/eventarc/attributes/help deleted file mode 100644 index 5add653c9..000000000 --- a/gcloud/beta/eventarc/attributes/help +++ /dev/null @@ -1,34 +0,0 @@ -NAME - gcloud beta eventarc attributes - explore CloudEvents attributes in - Eventarc - -SYNOPSIS - gcloud beta eventarc attributes GROUP [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (BETA) (DEPRECATED) Explore CloudEvents attributes in Eventarc. - - This command is deprecated. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --help. - - Run $ gcloud help for details. - -GROUPS - GROUP is one of the following: - - method-names - (BETA) (DEPRECATED) Explore values for the methodName CloudEvents - attribute. - - service-names - (BETA) (DEPRECATED) Explore values for the serviceName CloudEvents - attribute. - - types - (BETA) (DEPRECATED) Explore event types in Eventarc. - -NOTES - This command is currently in beta and might change without notice. - diff --git a/gcloud/beta/eventarc/attributes/method-names/help b/gcloud/beta/eventarc/attributes/method-names/help deleted file mode 100644 index daf1d379e..000000000 --- a/gcloud/beta/eventarc/attributes/method-names/help +++ /dev/null @@ -1,28 +0,0 @@ -NAME - gcloud beta eventarc attributes method-names - explore values for the - methodName CloudEvents attribute - -SYNOPSIS - gcloud beta eventarc attributes method-names COMMAND [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (BETA) (DEPRECATED) Explore values for the methodName CloudEvents - attribute. - - This command is deprecated. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --help. - - Run $ gcloud help for details. - -COMMANDS - COMMAND is one of the following: - - list - (BETA) (DEPRECATED) List values for the methodName CloudEvents - attribute. - -NOTES - This command is currently in beta and might change without notice. - diff --git a/gcloud/beta/eventarc/attributes/method-names/list b/gcloud/beta/eventarc/attributes/method-names/list deleted file mode 100644 index 362359af1..000000000 --- a/gcloud/beta/eventarc/attributes/method-names/list +++ /dev/null @@ -1,61 +0,0 @@ -NAME - gcloud beta eventarc attributes method-names list - list values for the - methodName CloudEvents attribute - -SYNOPSIS - gcloud beta eventarc attributes method-names list - --service-name=SERVICE_NAME --type=TYPE [--filter=EXPRESSION] - [--limit=LIMIT] [--sort-by=[FIELD,...]] [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (BETA) (DEPRECATED) This command is deprecated. - - (BETA) (DEPRECATED) List values for the methodName CloudEvents attribute. - - This command is deprecated. - -EXAMPLES - To list methodName values for event type google.cloud.audit.log.v1.written - and serviceName storage.googleapis.com, run: - - $ gcloud beta eventarc attributes method-names list \ - --type=google.cloud.audit.log.v1.written \ - --service-name=storage.googleapis.com - -REQUIRED FLAGS - --service-name=SERVICE_NAME - The value of the serviceName CloudEvents attribute. - - --type=TYPE - The event type. - -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. - - --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. - -NOTES - This command is currently in beta and might change without notice. - diff --git a/gcloud/beta/eventarc/attributes/service-names/help b/gcloud/beta/eventarc/attributes/service-names/help deleted file mode 100644 index d24484c02..000000000 --- a/gcloud/beta/eventarc/attributes/service-names/help +++ /dev/null @@ -1,29 +0,0 @@ -NAME - gcloud beta eventarc attributes service-names - explore values for the - serviceName CloudEvents attribute - -SYNOPSIS - gcloud beta eventarc attributes service-names COMMAND - [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (BETA) (DEPRECATED) Explore values for the serviceName CloudEvents - attribute. - - This command is deprecated. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --help. - - Run $ gcloud help for details. - -COMMANDS - COMMAND is one of the following: - - list - (BETA) (DEPRECATED) List values for the serviceName CloudEvents - attribute. - -NOTES - This command is currently in beta and might change without notice. - diff --git a/gcloud/beta/eventarc/attributes/service-names/list b/gcloud/beta/eventarc/attributes/service-names/list deleted file mode 100644 index 28f78ddad..000000000 --- a/gcloud/beta/eventarc/attributes/service-names/list +++ /dev/null @@ -1,57 +0,0 @@ -NAME - gcloud beta eventarc attributes service-names list - list values for the - serviceName CloudEvents attribute - -SYNOPSIS - gcloud beta eventarc attributes service-names list --type=TYPE - [--filter=EXPRESSION] [--limit=LIMIT] [--sort-by=[FIELD,...]] - [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (BETA) (DEPRECATED) This command is deprecated. - - (BETA) (DEPRECATED) List values for the serviceName CloudEvents attribute. - - This command is deprecated. - -EXAMPLES - To list serviceName values for event type - google.cloud.audit.log.v1.written, run: - - $ gcloud beta eventarc attributes service-names list \ - --type=google.cloud.audit.log.v1.written - -REQUIRED FLAGS - --type=TYPE - The event type. - -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. - - --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. - -NOTES - This command is currently in beta and might change without notice. - diff --git a/gcloud/beta/eventarc/attributes/types/describe b/gcloud/beta/eventarc/attributes/types/describe deleted file mode 100644 index 415f60c0e..000000000 --- a/gcloud/beta/eventarc/attributes/types/describe +++ /dev/null @@ -1,34 +0,0 @@ -NAME - gcloud beta eventarc attributes types describe - describe an event type - -SYNOPSIS - gcloud beta eventarc attributes types describe TYPE [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (BETA) (DEPRECATED) This command is deprecated. - - (BETA) (DEPRECATED) Describe an event type. - - This command is deprecated. - -EXAMPLES - To describe the google.cloud.audit.log.v1.written event type, run: - - $ gcloud beta eventarc attributes types describe \ - google.cloud.audit.log.v1.written - -POSITIONAL ARGUMENTS - TYPE - The event type to describe. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --configuration, --flags-file, --flatten, --format, - --help, --impersonate-service-account, --log-http, --project, --quiet, - --trace-token, --user-output-enabled, --verbosity. - - Run $ gcloud help for details. - -NOTES - This command is currently in beta and might change without notice. - diff --git a/gcloud/beta/eventarc/attributes/types/help b/gcloud/beta/eventarc/attributes/types/help deleted file mode 100644 index 698b9351c..000000000 --- a/gcloud/beta/eventarc/attributes/types/help +++ /dev/null @@ -1,28 +0,0 @@ -NAME - gcloud beta eventarc attributes types - explore event types in Eventarc - -SYNOPSIS - gcloud beta eventarc attributes types COMMAND [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (BETA) (DEPRECATED) Explore event types in Eventarc. - - This command is deprecated. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --help. - - Run $ gcloud help for details. - -COMMANDS - COMMAND is one of the following: - - describe - (BETA) (DEPRECATED) Describe an event type. - - list - (BETA) (DEPRECATED) List event types in Eventarc. - -NOTES - This command is currently in beta and might change without notice. - diff --git a/gcloud/beta/eventarc/attributes/types/list b/gcloud/beta/eventarc/attributes/types/list deleted file mode 100644 index ce77ed561..000000000 --- a/gcloud/beta/eventarc/attributes/types/list +++ /dev/null @@ -1,49 +0,0 @@ -NAME - gcloud beta eventarc attributes types list - list event types in Eventarc - -SYNOPSIS - gcloud beta eventarc attributes types list [--filter=EXPRESSION] - [--limit=LIMIT] [--sort-by=[FIELD,...]] [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (BETA) (DEPRECATED) This command is deprecated. - - (BETA) (DEPRECATED) List event types in Eventarc. - - This command is deprecated. - -EXAMPLES - To list all supported event types, run: - - $ gcloud beta eventarc attributes types list - -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. - - --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. - -NOTES - This command is currently in beta and might change without notice. - diff --git a/gcloud/beta/eventarc/help b/gcloud/beta/eventarc/help deleted file mode 100644 index bd4c1fa1c..000000000 --- a/gcloud/beta/eventarc/help +++ /dev/null @@ -1,34 +0,0 @@ -NAME - gcloud beta eventarc - manage Eventarc resources - -SYNOPSIS - gcloud beta eventarc GROUP [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (BETA) (DEPRECATED) Manage Eventarc resources. - - This command is deprecated. Please use gcloud eventarc instead. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --help. - - Run $ gcloud help for details. - -GROUPS - GROUP is one of the following: - - attributes - (BETA) (DEPRECATED) Explore CloudEvents attributes in Eventarc. - - locations - (BETA) (DEPRECATED) Explore locations available for Eventarc. - - triggers - (BETA) (DEPRECATED) Manage Eventarc triggers. - -NOTES - This command is currently in beta and might change without notice. This - variant is also available: - - $ gcloud eventarc - diff --git a/gcloud/beta/eventarc/locations/help b/gcloud/beta/eventarc/locations/help deleted file mode 100644 index fd678bff5..000000000 --- a/gcloud/beta/eventarc/locations/help +++ /dev/null @@ -1,28 +0,0 @@ -NAME - gcloud beta eventarc locations - explore locations available for Eventarc - -SYNOPSIS - gcloud beta eventarc locations COMMAND [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (BETA) (DEPRECATED) Explore locations available for Eventarc. - - This command is deprecated. Please use gcloud eventarc locations instead. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --help. - - Run $ gcloud help for details. - -COMMANDS - COMMAND is one of the following: - - list - (BETA) (DEPRECATED) List locations available for Eventarc. - -NOTES - This command is currently in beta and might change without notice. This - variant is also available: - - $ gcloud eventarc locations - diff --git a/gcloud/beta/eventarc/triggers/create b/gcloud/beta/eventarc/triggers/create deleted file mode 100644 index dfa7043fe..000000000 --- a/gcloud/beta/eventarc/triggers/create +++ /dev/null @@ -1,139 +0,0 @@ -NAME - gcloud beta eventarc triggers create - create an Eventarc trigger - -SYNOPSIS - gcloud beta eventarc triggers create (TRIGGER : --location=LOCATION) - --matching-criteria=[ATTRIBUTE=VALUE,...] - ([--destination-run-service=DESTINATION_RUN_SERVICE - : --destination-run-path=DESTINATION_RUN_PATH - --destination-run-region=DESTINATION_RUN_REGION]) [--async] - [--service-account=SERVICE_ACCOUNT] [--transport-topic=TRANSPORT_TOPIC] - [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (BETA) (DEPRECATED) This command is deprecated. Please use gcloud eventarc - triggers create instead. - - (BETA) (DEPRECATED) Create an Eventarc trigger. - - This command is deprecated. Please use gcloud eventarc triggers create - instead. - -EXAMPLES - To create a new trigger my-trigger for events of type - google.cloud.pubsub.topic.v1.messagePublished with destination Cloud Run - service my-service, run: - - $ gcloud beta eventarc triggers create my-trigger \ - --matching-criteria="type=google.cloud.pubsub.topic.v1.messagePu\ - blished" --destination-run-service=my-service - -POSITIONAL ARGUMENTS - Trigger resource - The trigger 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 trigger 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. - - TRIGGER - ID of the trigger or fully qualified identifier for the trigger. - - To set the trigger attribute: - ▸ provide the argument trigger on the command line. - - This positional argument must be specified if any of the other - arguments in this group are specified. - - --location=LOCATION - The location for the Eventarc trigger, which should be either global - or one of the supported regions. Alternatively, set the - [eventarc/location] property. - - To set the location attribute: - ▸ provide the argument trigger on the command line with a fully - specified name; - ▸ provide the argument --location on the command line; - ▸ set the property eventarc/location. - -REQUIRED FLAGS - --matching-criteria=[ATTRIBUTE=VALUE,...] - The criteria by which events are filtered for the trigger, specified as - a comma-separated list of CloudEvents attribute names and values. This - flag can also be repeated to add more criteria to the list. Only events - that match with this criteria will be sent to the destination. The - criteria must include the type attribute, as well as any other - attributes that are expected for the chosen type. - - Flags for specifying the destination to which events should be sent. - - This must be specified. - - Flags for specifying a Cloud Run fully-managed resource destination. - - --destination-run-service=DESTINATION_RUN_SERVICE - Name of the Cloud Run fully-managed service that receives the - events for the trigger. The service must be in the same project as - the trigger. - - This flag argument must be specified if any of the other arguments - in this group are specified. - - --destination-run-path=DESTINATION_RUN_PATH - Relative path on the destination Cloud Run service to which the - events for the trigger should be sent. Examples: /route, route, - route/subroute. - - --destination-run-region=DESTINATION_RUN_REGION - Region in which the destination Cloud Run service can be found. If - not specified, it is assumed that the service is in the same region - as the trigger. - -OPTIONAL FLAGS - --async - Return immediately, without waiting for the operation in progress to - complete. - - --service-account=SERVICE_ACCOUNT - The IAM service account email associated with the trigger. - - Pub/Sub topic resource - The Cloud Pub/Sub topic to use for the trigger's - transport intermediary. This feature is currently only available for - triggers of event type google.cloud.pubsub.topic.v1.messagePublished. The - topic must be in the same project as the trigger. If not specified, a - transport topic will be created. 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 --transport-topic on the command line with a - fully specified name; - ◆ provide the argument --project on the command line; - ◆ set the property core/project. - - --transport-topic=TRANSPORT_TOPIC - ID of the Pub/Sub topic or fully qualified identifier for the Pub/Sub - topic. - - To set the transport-topic attribute: - ▸ provide the argument --transport-topic on the command line. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --configuration, --flags-file, --flatten, --format, - --help, --impersonate-service-account, --log-http, --project, --quiet, - --trace-token, --user-output-enabled, --verbosity. - - Run $ gcloud help for details. - -NOTES - This command is currently in beta and might change without notice. This - variant is also available: - - $ gcloud eventarc triggers create - diff --git a/gcloud/beta/eventarc/triggers/delete b/gcloud/beta/eventarc/triggers/delete deleted file mode 100644 index 37f1977f3..000000000 --- a/gcloud/beta/eventarc/triggers/delete +++ /dev/null @@ -1,73 +0,0 @@ -NAME - gcloud beta eventarc triggers delete - delete an Eventarc trigger - -SYNOPSIS - gcloud beta eventarc triggers delete (TRIGGER : --location=LOCATION) - [--async] [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (BETA) (DEPRECATED) This command is deprecated. Please use gcloud eventarc - triggers delete instead. - - (BETA) (DEPRECATED) Delete an Eventarc trigger. - - This command is deprecated. Please use gcloud eventarc triggers delete - instead. - -EXAMPLES - To delete the trigger my-trigger, run: - - $ gcloud beta eventarc triggers delete my-trigger - -POSITIONAL ARGUMENTS - Trigger resource - The trigger 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 trigger 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. - - TRIGGER - ID of the trigger or fully qualified identifier for the trigger. - - To set the trigger attribute: - ▸ provide the argument trigger on the command line. - - This positional argument must be specified if any of the other - arguments in this group are specified. - - --location=LOCATION - The location for the Eventarc trigger, which should be either global - or one of the supported regions. Alternatively, set the - [eventarc/location] property. - - To set the location attribute: - ▸ provide the argument trigger on the command line with a fully - specified name; - ▸ provide the argument --location on the command line; - ▸ set the property eventarc/location. - -FLAGS - --async - Return immediately, without waiting for the operation in progress to - complete. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --configuration, --flags-file, --flatten, --format, - --help, --impersonate-service-account, --log-http, --project, --quiet, - --trace-token, --user-output-enabled, --verbosity. - - Run $ gcloud help for details. - -NOTES - This command is currently in beta and might change without notice. This - variant is also available: - - $ gcloud eventarc triggers delete - diff --git a/gcloud/beta/eventarc/triggers/describe b/gcloud/beta/eventarc/triggers/describe deleted file mode 100644 index e272146ac..000000000 --- a/gcloud/beta/eventarc/triggers/describe +++ /dev/null @@ -1,69 +0,0 @@ -NAME - gcloud beta eventarc triggers describe - describe an Eventarc trigger - -SYNOPSIS - gcloud beta eventarc triggers describe (TRIGGER : --location=LOCATION) - [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (BETA) (DEPRECATED) This command is deprecated. Please use gcloud eventarc - triggers describe instead. - - (BETA) (DEPRECATED) Describe an Eventarc trigger. - - This command is deprecated. Please use gcloud eventarc triggers describe - instead. - -EXAMPLES - To describe the trigger my-trigger, run: - - $ gcloud beta eventarc triggers describe my-trigger - -POSITIONAL ARGUMENTS - Trigger resource - The trigger 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 trigger 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. - - TRIGGER - ID of the trigger or fully qualified identifier for the trigger. - - To set the trigger attribute: - ▸ provide the argument trigger on the command line. - - This positional argument must be specified if any of the other - arguments in this group are specified. - - --location=LOCATION - The location for the Eventarc trigger, which should be either global - or one of the supported regions. Alternatively, set the - [eventarc/location] property. - - To set the location attribute: - ▸ provide the argument trigger on the command line with a fully - specified name; - ▸ provide the argument --location on the command line; - ▸ set the property eventarc/location. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --configuration, --flags-file, --flatten, --format, - --help, --impersonate-service-account, --log-http, --project, --quiet, - --trace-token, --user-output-enabled, --verbosity. - - Run $ gcloud help for details. - -NOTES - This command is currently in beta and might change without notice. This - variant is also available: - - $ gcloud eventarc triggers describe - diff --git a/gcloud/beta/eventarc/triggers/help b/gcloud/beta/eventarc/triggers/help deleted file mode 100644 index 6c141f617..000000000 --- a/gcloud/beta/eventarc/triggers/help +++ /dev/null @@ -1,40 +0,0 @@ -NAME - gcloud beta eventarc triggers - manage Eventarc triggers - -SYNOPSIS - gcloud beta eventarc triggers COMMAND [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (BETA) (DEPRECATED) Manage Eventarc triggers. - - This command is deprecated. Please use gcloud eventarc triggers instead. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --help. - - Run $ gcloud help for details. - -COMMANDS - COMMAND is one of the following: - - create - (BETA) (DEPRECATED) Create an Eventarc trigger. - - delete - (BETA) (DEPRECATED) Delete an Eventarc trigger. - - describe - (BETA) (DEPRECATED) Describe an Eventarc trigger. - - list - (BETA) (DEPRECATED) List Eventarc triggers. - - update - (BETA) (DEPRECATED) Update an Eventarc trigger. - -NOTES - This command is currently in beta and might change without notice. This - variant is also available: - - $ gcloud eventarc triggers - diff --git a/gcloud/beta/eventarc/triggers/update b/gcloud/beta/eventarc/triggers/update deleted file mode 100644 index 9a409c695..000000000 --- a/gcloud/beta/eventarc/triggers/update +++ /dev/null @@ -1,121 +0,0 @@ -NAME - gcloud beta eventarc triggers update - update an Eventarc trigger - -SYNOPSIS - gcloud beta eventarc triggers update (TRIGGER : --location=LOCATION) - [--async] [--matching-criteria=[ATTRIBUTE=VALUE,...]] - [--clear-service-account | --service-account=SERVICE_ACCOUNT] - [--destination-run-region=DESTINATION_RUN_REGION - --destination-run-service=DESTINATION_RUN_SERVICE - --clear-destination-run-path - | --destination-run-path=DESTINATION_RUN_PATH] [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (BETA) (DEPRECATED) This command is deprecated. Please use gcloud eventarc - triggers update instead. - - (BETA) (DEPRECATED) Update an Eventarc trigger. - - This command is deprecated. Please use gcloud eventarc triggers update - instead. - -EXAMPLES - To update the trigger my-trigger by setting its destination Cloud Run - service to my-service, run: - - $ gcloud beta eventarc triggers update my-trigger \ - --destination-run-service=my-service - -POSITIONAL ARGUMENTS - Trigger resource - The trigger 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 trigger 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. - - TRIGGER - ID of the trigger or fully qualified identifier for the trigger. - - To set the trigger attribute: - ▸ provide the argument trigger on the command line. - - This positional argument must be specified if any of the other - arguments in this group are specified. - - --location=LOCATION - The location for the Eventarc trigger, which should be either global - or one of the supported regions. Alternatively, set the - [eventarc/location] property. - - To set the location attribute: - ▸ provide the argument trigger on the command line with a fully - specified name; - ▸ provide the argument --location on the command line; - ▸ set the property eventarc/location. - -FLAGS - --async - Return immediately, without waiting for the operation in progress to - complete. - - --matching-criteria=[ATTRIBUTE=VALUE,...] - The criteria by which events are filtered for the trigger, specified as - a comma-separated list of CloudEvents attribute names and values. This - flag can also be repeated to add more criteria to the list. Only events - that match with this criteria will be sent to the destination. The - criteria must include the type attribute, as well as any other - attributes that are expected for the chosen type. - - At most one of these can be specified: - - --clear-service-account - Clear the IAM service account associated with the trigger. - - --service-account=SERVICE_ACCOUNT - The IAM service account email associated with the trigger. - - Flags for updating the destination to which events should be sent. - - Flags for updating a Cloud Run fully-managed resource destination. - - --destination-run-region=DESTINATION_RUN_REGION - Region in which the destination Cloud Run service can be found. If - not specified, it is assumed that the service is in the same region - as the trigger. - - --destination-run-service=DESTINATION_RUN_SERVICE - Name of the Cloud Run fully-managed service that receives the - events for the trigger. The service must be in the same project as - the trigger. - - At most one of these can be specified: - - --clear-destination-run-path - Clear the relative path on the destination Cloud Run service to - which the events for the trigger should be sent. - - --destination-run-path=DESTINATION_RUN_PATH - Relative path on the destination Cloud Run service to which the - events for the trigger should be sent. Examples: /route, route, - route/subroute. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --configuration, --flags-file, --flatten, --format, - --help, --impersonate-service-account, --log-http, --project, --quiet, - --trace-token, --user-output-enabled, --verbosity. - - Run $ gcloud help for details. - -NOTES - This command is currently in beta and might change without notice. This - variant is also available: - - $ gcloud eventarc triggers update - diff --git a/gcloud/beta/filestore/instances/revert b/gcloud/beta/filestore/instances/revert index c46178578..e27b0d55e 100644 --- a/gcloud/beta/filestore/instances/revert +++ b/gcloud/beta/filestore/instances/revert @@ -74,5 +74,8 @@ API REFERENCE can be found at: https://cloud.google.com/filestore/ 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 filestore instances revert diff --git a/gcloud/beta/metastore/services/create b/gcloud/beta/metastore/services/create index b47d7e184..36f920425 100644 --- a/gcloud/beta/metastore/services/create +++ b/gcloud/beta/metastore/services/create @@ -3,7 +3,7 @@ NAME SYNOPSIS gcloud beta metastore services create (SERVICE : --location=LOCATION) - [--async] [--data-catalog-sync] + [--async] [--autoscaling-enabled] [--data-catalog-sync] [--database-type=DATABASE_TYPE; default="mysql"] [--encryption-kms-key=ENCRYPTION_KMS_KEY] [--endpoint-protocol=ENDPOINT_PROTOCOL; default="thrift"] @@ -17,7 +17,8 @@ SYNOPSIS [--hive-metastore-configs=[KEY=VALUE,...] | --hive-metastore-configs-from-file=HIVE_METASTORE_CONFIGS_FROM_FILE] [--instance-size=INSTANCE_SIZE | --scaling-factor=SCALING_FACTOR - | --tier=TIER] + | --tier=TIER | --max-scaling-factor=MAX_SCALING_FACTOR + --min-scaling-factor=MIN_SCALING_FACTOR] [--kerberos-principal=KERBEROS_PRINCIPAL --keytab=KEYTAB --krb5-config=KRB5_CONFIG] [--maintenance-window-day=MAINTENANCE_WINDOW_DAY @@ -86,6 +87,16 @@ FLAGS Return immediately, without waiting for the operation in progress to complete. + --autoscaling-enabled + A boolean flag to determine whether Dataproc Metastore autoscaling + should be enabled, false if unspecified. + + The default minimum and maximum scaling factors are 0.1 and 6.0, + respectively. + + The minimum and maximum scaling factors can be specified using + --min-scaling-factor and --max-scaling-factor. + --data-catalog-sync A boolean flag to determine whether Dataproc Metastore metadata sync to Data Catalog should be enabled, false if unspecified. Mutually @@ -268,10 +279,8 @@ FLAGS Small instance size, maps to a scaling factor of 0.5. --scaling-factor=SCALING_FACTOR - The scaling factor of the service. This should be a float in the - range [0.1,6.0]. If the value is less than 1.0, then it should be a - multiple of 0.1. If the value is greater than 1.0, then it should be - a whole number. Float values should be formatted as x.y. + The scaling factor of the service. Can be one of [0.1, 0.2, 0.3, 0.4, + 0.5, 0.6, 0.7, 0.8, 0.9, 1.0, 2.0, 3.0, 4.0, 5.0, 6.0]. --tier=TIER The tier of the service. TIER must be one of: @@ -285,6 +294,18 @@ FLAGS sufficient scalability for enterprise-level Dataproc Metastore workloads. + The autoscaling configuration of the Dataproc Metastore instance. + + --max-scaling-factor=MAX_SCALING_FACTOR + The maximum scaling factor allowed by the autoscaler. Can be one of + [0.1, 0.2, 0.3, 0.4, 0.5, 0.6, 0.7, 0.8, 0.9, 1.0, 2.0, 3.0, 4.0, + 5.0, 6.0]. The default value is 6.0. + + --min-scaling-factor=MIN_SCALING_FACTOR + The minimum scaling factor allowed by the autoscaler. Can be one of + [0.1, 0.2, 0.3, 0.4, 0.5, 0.6, 0.7, 0.8, 0.9, 1.0, 2.0, 3.0, 4.0, + 5.0, 6.0]. The default value is 0.1. + Information used to configure the Hive metastore service as a service principal in a Kerberos realm. diff --git a/gcloud/beta/metastore/services/help b/gcloud/beta/metastore/services/help index 5061641e3..59e89eadf 100644 --- a/gcloud/beta/metastore/services/help +++ b/gcloud/beta/metastore/services/help @@ -31,6 +31,9 @@ GROUPS (BETA) (DEPRECATED) Manage metadata imports under Dataproc Metastore services. + migrations + (BETA) Manage the migration to a Dataproc Metastore service. + COMMANDS COMMAND is one of the following: diff --git a/gcloud/beta/metastore/services/migrations/cancel b/gcloud/beta/metastore/services/migrations/cancel new file mode 100644 index 000000000..f5890563a --- /dev/null +++ b/gcloud/beta/metastore/services/migrations/cancel @@ -0,0 +1,73 @@ +NAME + gcloud beta metastore services migrations cancel - cancel the migration to + Dataproc Metastore service + +SYNOPSIS + gcloud beta metastore services migrations cancel + (SERVICE : --location=LOCATION) [--async] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Cancel the migration to Dataproc Metastore service. + + If run asynchronously with --async, exits after printing the operation name + that can be used to poll the status of the migration operation via: + + gcloud metastore operations describe + +POSITIONAL ARGUMENTS + Service resource - The Dataproc Metastore service to cancel the migration + 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 service on the command line with a fully + specified name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + This must be specified. + + SERVICE + ID of the service or fully qualified identifier for the service. + + To set the service attribute: + ▸ provide the argument service on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + The location of the Dataproc Metastore service. + + If not specified, will use default metastore/location. + + To set the location attribute: + ▸ provide the argument service on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ set the property metastore/location. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + +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 metastore/v1beta API. The full documentation for this + API can be found at: https://cloud.google.com/dataproc-metastore/docs + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha metastore services migrations cancel + diff --git a/gcloud/beta/metastore/services/migrations/complete b/gcloud/beta/metastore/services/migrations/complete new file mode 100644 index 000000000..ffd227a50 --- /dev/null +++ b/gcloud/beta/metastore/services/migrations/complete @@ -0,0 +1,73 @@ +NAME + gcloud beta metastore services migrations complete - complete the migration + to Dataproc Metastore service + +SYNOPSIS + gcloud beta metastore services migrations complete + (SERVICE : --location=LOCATION) [--async] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Complete the migration to Dataproc Metastore service. + + If run asynchronously with --async, exits after printing the operation name + that can be used to poll the status of the migration operation via: + + gcloud metastore operations describe + +POSITIONAL ARGUMENTS + Service resource - The Dataproc Metastore service to complete the + migration 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 service on the command line with a fully + specified name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + This must be specified. + + SERVICE + ID of the service or fully qualified identifier for the service. + + To set the service attribute: + ▸ provide the argument service on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + The location of the Dataproc Metastore service. + + If not specified, will use default metastore/location. + + To set the location attribute: + ▸ provide the argument service on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ set the property metastore/location. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + +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 metastore/v1beta API. The full documentation for this + API can be found at: https://cloud.google.com/dataproc-metastore/docs + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha metastore services migrations complete + diff --git a/gcloud/beta/metastore/services/migrations/delete b/gcloud/beta/metastore/services/migrations/delete new file mode 100644 index 000000000..3b6115726 --- /dev/null +++ b/gcloud/beta/metastore/services/migrations/delete @@ -0,0 +1,86 @@ +NAME + gcloud beta metastore services migrations delete - delete a migration + +SYNOPSIS + gcloud beta metastore services migrations delete + (MIGRATION : --location=LOCATION --service=SERVICE) [--async] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Delete a migration. + + If run asynchronously with --async, exits after printing an operation name + that can be used to poll the status of the deletion via: + + gcloud metastore operations describe + +EXAMPLES + To delete a migration named my-migration for the service my-service, run: + + $ gcloud beta metastore services migrations delete my-migration \ + --service=my-service + +POSITIONAL ARGUMENTS + Migration resource - Migration 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 migration on the command line with a fully + specified name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + This must be specified. + + MIGRATION + ID of the migration or fully qualified identifier for the migration. + + To set the migration attribute: + ▸ provide the argument migration on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + The location of the Dataproc Metastore service. + + If not specified, will use default metastore/location. + + To set the location attribute: + ▸ provide the argument migration on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ set the property metastore/location. + + --service=SERVICE + The identifier of the Dataproc Metastore service + + To set the service attribute: + ▸ provide the argument migration on the command line with a fully + specified name; + ▸ provide the argument --service on the command line. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + +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 metastore/v1beta API. The full documentation for this + API can be found at: https://cloud.google.com/dataproc-metastore/docs + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha metastore services migrations delete + diff --git a/gcloud/beta/metastore/services/migrations/describe b/gcloud/beta/metastore/services/migrations/describe new file mode 100644 index 000000000..1ad78a600 --- /dev/null +++ b/gcloud/beta/metastore/services/migrations/describe @@ -0,0 +1,80 @@ +NAME + gcloud beta metastore services migrations describe - describe a migration + +SYNOPSIS + gcloud beta metastore services migrations describe + (MIGRATION : --location=LOCATION --service=SERVICE) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Describe a migration. + + Displays all details of a migration given a migration ID. + +EXAMPLES + To describe a migration with the ID my-migration under service my-service, + run: + + $ gcloud beta metastore services migrations describe my-migration \ + --service=my-service + +POSITIONAL ARGUMENTS + Migration resource - Arguments and flags that specify the migration you + want 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 migration on the command line with a fully + specified name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + This must be specified. + + MIGRATION + ID of the migration or fully qualified identifier for the migration. + + To set the migration attribute: + ▸ provide the argument migration on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + The location of the Dataproc Metastore service. + + If not specified, will use default metastore/location. + + To set the location attribute: + ▸ provide the argument migration on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ set the property metastore/location. + + --service=SERVICE + The identifier of the Dataproc Metastore service + + To set the service attribute: + ▸ provide the argument migration on the command line with a fully + specified name; + ▸ provide the argument --service 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 metastore/v1beta API. The full documentation for this + API can be found at: https://cloud.google.com/dataproc-metastore/docs + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha metastore services migrations describe + diff --git a/gcloud/beta/metastore/services/migrations/help b/gcloud/beta/metastore/services/migrations/help new file mode 100644 index 000000000..f705ad338 --- /dev/null +++ b/gcloud/beta/metastore/services/migrations/help @@ -0,0 +1,42 @@ +NAME + gcloud beta metastore services migrations - manage the migration to a + Dataproc Metastore service + +SYNOPSIS + gcloud beta metastore services migrations COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Manage the migration to a Dataproc Metastore service. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + cancel + (BETA) Cancel the migration to Dataproc Metastore service. + + complete + (BETA) Complete the migration to Dataproc Metastore service. + + delete + (BETA) Delete a migration. + + describe + (BETA) Describe a migration. + + list + (BETA) List migrations for a Dataproc Metastore service. + + start + (BETA) Start the migration on a Dataproc Metastore service. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha metastore services migrations + diff --git a/gcloud/beta/eventarc/triggers/list b/gcloud/beta/metastore/services/migrations/list similarity index 55% rename from gcloud/beta/eventarc/triggers/list rename to gcloud/beta/metastore/services/migrations/list index 1c9a1fb80..32b3fbf96 100644 --- a/gcloud/beta/eventarc/triggers/list +++ b/gcloud/beta/metastore/services/migrations/list @@ -1,55 +1,54 @@ NAME - gcloud beta eventarc triggers list - list Eventarc triggers + gcloud beta metastore services migrations list - list migrations for a + Dataproc Metastore service SYNOPSIS - gcloud beta eventarc triggers list [--location=LOCATION] - [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] - [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + gcloud beta metastore services migrations list + (--service=SERVICE : --location=LOCATION) [--filter=EXPRESSION] + [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) (DEPRECATED) This command is deprecated. Please use gcloud eventarc - triggers list instead. - - (BETA) (DEPRECATED) List Eventarc triggers. - - This command is deprecated. Please use gcloud eventarc triggers list - instead. + (BETA) Lists all migrations for the specified Dataproc Metastore service. EXAMPLES - To list all triggers in location us-central1, run: + To list all migrations for service my-service, run: - $ gcloud beta eventarc triggers list --location=us-central1 + $ gcloud beta metastore services migrations list --service=my-service - To list all triggers in all locations, run: - - $ gcloud beta eventarc triggers list --location=- - - or - - $ gcloud beta eventarc triggers list - -FLAGS - Location resource - The location for which to list triggers. This should - be either global or one of the supported regions. This represents a Cloud - resource. (NOTE) Some attributes are not given arguments in this group but - can be set in other ways. +REQUIRED FLAGS + Service resource - The service to list the migrations 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 --location on the command line with a fully + ◆ provide the argument --service on the command line with a fully specified name; - ◆ set the property eventarc/location with a fully specified name; - ◆ use '-' location to aggregate results for all Eventarc locations with - a fully specified name; - ◆ provide the argument --project on the command line; - ◆ set the property core/project. + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + This must be specified. + + --service=SERVICE + ID of the service or fully qualified identifier for the service. + + To set the service attribute: + ▸ provide the argument --service on the command line. + + This flag argument must be specified if any of the other arguments in + this group are specified. --location=LOCATION - ID of the location or fully qualified identifier for the location. + The location of the Dataproc Metastore service. + + If not specified, will use default metastore/location. To set the location attribute: + ▸ provide the argument --service on the command line with a fully + specified name; ▸ provide the argument --location on the command line; - ▸ set the property eventarc/location; - ▸ use '-' location to aggregate results for all Eventarc locations. + ▸ set the property metastore/location. LIST COMMAND FLAGS --filter=EXPRESSION @@ -91,9 +90,13 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. +API REFERENCE + This command uses the metastore/v1beta API. The full documentation for this + API can be found at: https://cloud.google.com/dataproc-metastore/docs + NOTES This command is currently in beta and might change without notice. This variant is also available: - $ gcloud eventarc triggers list + $ gcloud alpha metastore services migrations list diff --git a/gcloud/beta/metastore/services/migrations/start b/gcloud/beta/metastore/services/migrations/start new file mode 100644 index 000000000..541b4bda0 --- /dev/null +++ b/gcloud/beta/metastore/services/migrations/start @@ -0,0 +1,222 @@ +NAME + gcloud beta metastore services migrations start - start the migration on a + Dataproc Metastore service + +SYNOPSIS + gcloud beta metastore services migrations start + (SERVICE : --location=LOCATION) + ((--cdc-password=CDC_PASSWORD --cdc-username=CDC_USERNAME + --reverse-proxy-subnet=REVERSE_PROXY_SUBNET + --subnet-ip-range=SUBNET_IP_RANGE --vpc-network=VPC_NETWORK + : --bucket=BUCKET --root-path=ROOT_PATH; default="/migration") + (--connection-password=CONNECTION_PASSWORD + --connection-username=CONNECTION_USERNAME + --hive-database-name=HIVE_DATABASE_NAME + --instance-connection-name=INSTANCE_CONNECTION_NAME + --ip-address=IP_ADDRESS + --nat-subnet=NAT_SUBNET --port=PORT --proxy-subnet=PROXY_SUBNET)) + [--async] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Start the migration on a Dataproc Metastore service. + + If run asynchronously with --async, exits after printing the operation name + that can be used to poll the status of the migration operation via: + + gcloud metastore operations describe + +POSITIONAL ARGUMENTS + Service resource - The Dataproc Metastore service to start the migration + 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 service on the command line with a fully + specified name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + This must be specified. + + SERVICE + ID of the service or fully qualified identifier for the service. + + To set the service attribute: + ▸ provide the argument service on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + The location of the Dataproc Metastore service. + + If not specified, will use default metastore/location. + + To set the location attribute: + ▸ provide the argument service on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ set the property metastore/location. + +REQUIRED FLAGS + Configuration information required by Dataproc Metastore to start the + migration. + + This must be specified. + + Configuration information specific to migrating from "Self-Managed Hive + Metastore on Google Cloud Platform with Cloud SQL as the backend + database" to a Dataproc Metastore service. + + Configuration information required to start the Change Data Capture + (CDC) streams from customer's Cloud SQL database to backend database + of Dataproc Metastore. + + This must be specified. + + --cdc-password=CDC_PASSWORD + The password for the user that Datastream service should use for + the MySQL connection. + + This flag argument must be specified if any of the other + arguments in this group are specified. + + --cdc-username=CDC_USERNAME + The username that the Datastream service should use for the MySQL + connection. + + This flag argument must be specified if any of the other + arguments in this group are specified. + + --reverse-proxy-subnet=REVERSE_PROXY_SUBNET + The URL of the subnetwork resource to create the VM instance + hosting the reverse proxy in. More context in + https://cloud.google.com/datastream/docs/private-connectivity#reverse-csql-proxy + The subnetwork should reside in the network provided in the + request that Datastream will peer to and should be in the same + region as Datastream, in the following format. + "projects/{project_id}/regions/{region_id}/subnetworks/{subnetwork_id}"" + + This flag argument must be specified if any of the other + arguments in this group are specified. + + --subnet-ip-range=SUBNET_IP_RANGE + A "/29" CIDR IP range for peering with datastream + + This flag argument must be specified if any of the other + arguments in this group are specified. + + --vpc-network=VPC_NETWORK + Fully qualified name of the Cloud SQL instance's VPC network or + the shared VPC network that Datastream will peer to, in the + following format: + "projects/{project_id}/locations/global/networks/{network_id}". + More context in + https://cloud.google.com/datastream/docs/network-connectivity-options#privateconnectivity + + This flag argument must be specified if any of the other + arguments in this group are specified. + + --bucket=BUCKET + The bucket to write the intermediate stream event data in. The + bucket name must be without any prefix like "gs://". This field + is optional. If not set, the Artifacts Cloud Storage bucket is + used. + + --root-path=ROOT_PATH; default="/migration" + The root path inside the Cloud Storage bucket. The stream event + data will be written to this path. The default value is + "/migration". + + Configuration information required for Dataproc Metastore to establish + customer database connection before the cutover phase of migration. + + This must be specified. + + --connection-password=CONNECTION_PASSWORD + The password for the user that Dataproc Metastore service should + use to connect to the database. + + This flag argument must be specified if any of the other + arguments in this group are specified. + + --connection-username=CONNECTION_USERNAME + The username that Dataproc Metastore service should use to + connect to the database. + + This flag argument must be specified if any of the other + arguments in this group are specified. + + --hive-database-name=HIVE_DATABASE_NAME + The name of the hive metastore database. + + This flag argument must be specified if any of the other + arguments in this group are specified. + + --instance-connection-name=INSTANCE_CONNECTION_NAME + The Cloud SQL database connection name, in the format, + "project_id:region:instance_name" + + This flag argument must be specified if any of the other + arguments in this group are specified. + + --ip-address=IP_ADDRESS + The private IP address of the Cloud SQL instance. + + This flag argument must be specified if any of the other + arguments in this group are specified. + + --nat-subnet=NAT_SUBNET + The relative resource name of the subnetwork to be used for + Private Service Connect. Note that this cannot be a regular + subnet and is used only for NAT. More context in + https://cloud.google.com/vpc/docs/about-vpc-hosted-services#psc-subnets. + This subnet is used to publish the SOCKS5 proxy service. The + subnet size must be at least /29 and it should reside in a + network through which the Cloud SQL instance is accessible. The + resource name should be in the format, + "projects/{project_id}/regions/{region_id}/subnetworks/{subnetwork_id}" + + This flag argument must be specified if any of the other + arguments in this group are specified. + + --port=PORT + The network port of the database. + + This flag argument must be specified if any of the other + arguments in this group are specified. + + --proxy-subnet=PROXY_SUBNET + The relative resource name of the subnetwork to deploy the SOCKS5 + proxy service in. The subnetwork should reside in a network + through which the Cloud SQL instance is accessible. The resource + name should be in the format, + "projects/{project_id}/regions/{region_id}/subnetworks/{subnetwork_id}" + + This flag argument must be specified if any of the other + arguments in this group are specified. + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + +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 metastore/v1beta API. The full documentation for this + API can be found at: https://cloud.google.com/dataproc-metastore/docs + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha metastore services migrations start + diff --git a/gcloud/beta/metastore/services/update b/gcloud/beta/metastore/services/update index 831260b88..54ae824fc 100644 --- a/gcloud/beta/metastore/services/update +++ b/gcloud/beta/metastore/services/update @@ -3,11 +3,13 @@ NAME SYNOPSIS gcloud beta metastore services update (SERVICE : --location=LOCATION) - [--async] [--data-catalog-sync] [--endpoint-protocol=ENDPOINT_PROTOCOL] - [--port=PORT] [--update-labels=[KEY=VALUE,...]] + [--async] [--autoscaling-enabled] [--data-catalog-sync] + [--endpoint-protocol=ENDPOINT_PROTOCOL] [--port=PORT] + [--update-labels=[KEY=VALUE,...]] [--clear-labels | --remove-labels=[KEY,...]] [--instance-size=INSTANCE_SIZE | --scaling-factor=SCALING_FACTOR - | --tier=TIER] + | --tier=TIER | --max-scaling-factor=MAX_SCALING_FACTOR + --min-scaling-factor=MIN_SCALING_FACTOR] [--kerberos-principal=KERBEROS_PRINCIPAL --keytab=KEYTAB --krb5-config=KRB5_CONFIG] [--maintenance-window-day=MAINTENANCE_WINDOW_DAY @@ -75,6 +77,16 @@ FLAGS Return immediately, without waiting for the operation in progress to complete. + --autoscaling-enabled + A boolean flag to determine whether Dataproc Metastore autoscaling + should be enabled, false if unspecified. + + The default minimum and maximum scaling factors are 0.1 and 6.0, + respectively. + + The minimum and maximum scaling factors can be specified using + --min-scaling-factor and --max-scaling-factor. + --data-catalog-sync Boolean flag to determine whether or not Dataproc Metastore metadata sync to Data Catalog is enabled, false if unspecified. Mutually @@ -146,10 +158,8 @@ FLAGS Small instance size, maps to a scaling factor of 0.5. --scaling-factor=SCALING_FACTOR - The scaling factor of the service. This should be a float in the - range [0.1,6.0]. If the value is less than 1.0, then it should be a - multiple of 0.1. If the value is greater than 1.0, then it should be - a whole number. + The scaling factor of the service. Can be one of [0.1, 0.2, 0.3, 0.4, + 0.5, 0.6, 0.7, 0.8, 0.9, 1.0, 2.0, 3.0, 4.0, 5.0, 6.0]. --tier=TIER The tier of the service. TIER must be one of: @@ -163,6 +173,18 @@ FLAGS sufficient scalability for enterprise-level Dataproc Metastore workloads. + The autoscaling configuration of the Dataproc Metastore instance. + + --max-scaling-factor=MAX_SCALING_FACTOR + The maximum scaling factor allowed by the autoscaler. Can be one of + [0.1, 0.2, 0.3, 0.4, 0.5, 0.6, 0.7, 0.8, 0.9, 1.0, 2.0, 3.0, 4.0, + 5.0, 6.0]. The default value is 6.0. + + --min-scaling-factor=MIN_SCALING_FACTOR + The minimum scaling factor allowed by the autoscaler. Can be one of + [0.1, 0.2, 0.3, 0.4, 0.5, 0.6, 0.7, 0.8, 0.9, 1.0, 2.0, 3.0, 4.0, + 5.0, 6.0]. The default value is 0.1. + Information used to configure the Hive metastore service as a service principal in a Kerberos realm. diff --git a/gcloud/beta/ml-engine/models/add-iam-policy-binding b/gcloud/beta/ml-engine/models/add-iam-policy-binding index 19e509641..4b7766ed1 100644 --- a/gcloud/beta/ml-engine/models/add-iam-policy-binding +++ b/gcloud/beta/ml-engine/models/add-iam-policy-binding @@ -10,21 +10,21 @@ DESCRIPTION (BETA) Add IAM policy binding to a model. EXAMPLES - To add an IAM policy binding for the role of 'roles/ml.admin' for the user - 'test-user@gmail.com' on a model with identifier 'my_model', run: + To add an IAM policy binding for the role of roles/ml.admin for the user + test-user@gmail.com on a model with identifier my_model, run: $ gcloud beta ml-engine models add-iam-policy-binding my_model \ --member='user:test-user@gmail.com' --role='roles/ml.admin' - To add an IAM policy binding for the role of 'roles/ml.admin' to the - service account 'test-proj1@example.domain.com', run: + To add an IAM policy binding for the role of roles/ml.admin to the service + account test-proj1@example.domain.com, run: $ gcloud beta ml-engine models add-iam-policy-binding my_model \ --member='serviceAccount:test-proj1@example.domain.com' \ --role='roles/ml.admin' - To add an IAM policy binding for the role of 'roles/ml.admin' for all - authenticated users on a model with identifier 'my_model', run: + To add an IAM policy binding for the role of roles/ml.admin for all + authenticated users on a model with identifier my_model, run: $ gcloud beta ml-engine models add-iam-policy-binding my_model \ --member='allAuthenticatedUsers' --role='roles/ml.admin' diff --git a/gcloud/beta/ml-engine/models/remove-iam-policy-binding b/gcloud/beta/ml-engine/models/remove-iam-policy-binding index 0f4a56d3d..e9070e8e9 100644 --- a/gcloud/beta/ml-engine/models/remove-iam-policy-binding +++ b/gcloud/beta/ml-engine/models/remove-iam-policy-binding @@ -13,14 +13,14 @@ DESCRIPTION resource. EXAMPLES - To remove an IAM policy binding for the role of 'roles/ml.admin' for the - user 'test-user@gmail.com' on model with identifier 'my_model', run: + To remove an IAM policy binding for the role of roles/ml.admin for the user + test-user@gmail.com on model with identifier my_model, run: $ gcloud beta ml-engine models remove-iam-policy-binding my_model \ --member='user:test-user@gmail.com' --role='roles/ml.admin' - To remove an IAM policy binding for the role of 'roles/ml.admin' from all - authenticated users on model 'my_model', run: + To remove an IAM policy binding for the role of roles/ml.admin from all + authenticated users on model my_model, run: $ gcloud beta ml-engine models remove-iam-policy-binding my_model \ --member='allAuthenticatedUsers' --role='roles/ml.admin' diff --git a/gcloud/beta/projects/add-iam-policy-binding b/gcloud/beta/projects/add-iam-policy-binding index a3adca329..c5cf35787 100644 --- a/gcloud/beta/projects/add-iam-policy-binding +++ b/gcloud/beta/projects/add-iam-policy-binding @@ -14,24 +14,23 @@ DESCRIPTION an optional condition. EXAMPLES - To add an IAM policy binding for the role of 'roles/editor' for the user - 'test-user@gmail.com' on a project with identifier 'example-project-id-1', - run: + To add an IAM policy binding for the role of roles/editor for the user + test-user@gmail.com on a project with identifier example-project-id-1, run: $ gcloud beta projects add-iam-policy-binding example-project-id-1 \ --member='user:test-user@gmail.com' --role='roles/editor' - To add an IAM policy binding for the role of 'roles/editor' to the service - account 'test-proj1@example.domain.com' on a project with identifier - 'example-project-id-1', run: + To add an IAM policy binding for the role of roles/editor to the service + account test-proj1@example.domain.com on a project with identifier + example-project-id-1, run: $ gcloud beta projects add-iam-policy-binding example-project-id-1 \ --member='serviceAccount:test-proj1@example.domain.com' \ --role='roles/editor' To add an IAM policy binding that expires at the end of the year 2021 for - the role of 'roles/browser' and the user 'test-user@gmail.com' on a project - with identifier 'example-project-id-1', run: + the role of roles/browser and the user test-user@gmail.com on a project + with identifier example-project-id-1, run: $ gcloud beta projects add-iam-policy-binding example-project-id-1 \ --member='user:test-user@gmail.com' --role='roles/browser' \ diff --git a/gcloud/beta/projects/create b/gcloud/beta/projects/create index 1683e1f7e..d38414676 100644 --- a/gcloud/beta/projects/create +++ b/gcloud/beta/projects/create @@ -66,7 +66,7 @@ FLAGS --tags=[KEY=VALUE,...] List of tags KEY=VALUE pairs to bind. Each item must be expressed as - "=". + =. Example: 123/environment=production,123/costCenter=marketing diff --git a/gcloud/beta/projects/remove-iam-policy-binding b/gcloud/beta/projects/remove-iam-policy-binding index c499264b0..ba7ad1c97 100644 --- a/gcloud/beta/projects/remove-iam-policy-binding +++ b/gcloud/beta/projects/remove-iam-policy-binding @@ -14,27 +14,25 @@ DESCRIPTION optional condition. EXAMPLES - To remove an IAM policy binding for the role of 'roles/editor' for the user - 'test-user@gmail.com' on project with identifier 'example-project-id-1', - run: + To remove an IAM policy binding for the role of roles/editor for the user + test-user@gmail.com on project with identifier example-project-id-1, run: $ gcloud beta projects remove-iam-policy-binding \ example-project-id-1 --member='user:test-user@gmail.com' \ --role='roles/editor' - To remove an IAM policy binding for the role of 'roles/editor' from all - authenticated users on project 'example-project-id-1', run: + To remove an IAM policy binding for the role of roles/editor from all + authenticated users on project example-project-id-1, run: $ gcloud beta projects remove-iam-policy-binding \ example-project-id-1 --member='allAuthenticatedUsers' \ --role='roles/editor' To remove an IAM policy binding with a condition of - expression='request.time < timestamp("2019-01-01T00:00:00Z")', - title='expires_end_of_2018', and description='Expires at midnight on - 2018-12-31' for the role of 'roles/browser' for the user - 'test-user@gmail.com' on project with identifier 'example-project-id-1', - run: + expression='request.time < timestamp("2019-01-01T00:00:00Z"), + title='expires_end_of_2018', and description=Expires at midnight on + 2018-12-31 for the role of roles/browser for the user test-user@gmail.com + on project with identifier example-project-id-1, run: $ gcloud beta projects remove-iam-policy-binding \ example-project-id-1 --member='user:test-user@gmail.com' \ @@ -44,8 +42,8 @@ EXAMPLES tion=Expires at midnight on 2018-12-31' To remove all IAM policy bindings regardless of the condition for the role - of 'roles/browser' and for the user 'test-user@gmail.com' on project with - identifier 'example-project-id-1', run: + of roles/browser and for the user test-user@gmail.com on project with + identifier example-project-id-1, run: $ gcloud beta projects remove-iam-policy-binding \ example-project-id-1 --member='user:test-user@gmail.com' \ diff --git a/gcloud/beta/projects/update b/gcloud/beta/projects/update index 08e428296..b4279a7fa 100644 --- a/gcloud/beta/projects/update +++ b/gcloud/beta/projects/update @@ -14,7 +14,7 @@ DESCRIPTION EXAMPLES The following command updates a project with the ID example-foo-bar-1 to - have the name "Foo Bar & Grill": + have the name Foo Bar & Grill: $ gcloud beta projects update example-foo-bar-1 \ --name="Foo Bar & Grill" diff --git a/gcloud/beta/resource-manager/folders/create b/gcloud/beta/resource-manager/folders/create index 0c384a1fc..d2cb8571a 100644 --- a/gcloud/beta/resource-manager/folders/create +++ b/gcloud/beta/resource-manager/folders/create @@ -39,7 +39,7 @@ OPTIONAL FLAGS --tags=[KEY=VALUE,...] List of tags KEY=VALUE pairs to bind. Each item must be expressed as - "=". + =. Example: 123/environment=production,123/costCenter=marketing diff --git a/gcloud/beta/services/api-keys/create b/gcloud/beta/services/api-keys/create index 01451fec4..42a427b68 100644 --- a/gcloud/beta/services/api-keys/create +++ b/gcloud/beta/services/api-keys/create @@ -59,11 +59,9 @@ EXAMPLES The content of 'my-flags.yaml' is as following: - --api-target: - service: - - "foo.service.com" + service: "foo.service.com" - --api-target: - service: - - "bar.service.com" + service: "bar.service.com" methods: - "foomethod" - "barmethod" diff --git a/gcloud/beta/spanner/instances/help b/gcloud/beta/spanner/instances/help index 812a637c8..929265bb1 100644 --- a/gcloud/beta/spanner/instances/help +++ b/gcloud/beta/spanner/instances/help @@ -33,6 +33,10 @@ COMMANDS list (BETA) List the Cloud Spanner instances in this project. + move + (BETA) Move the Cloud Spanner instance to the specified instance + config. + remove-iam-policy-binding (BETA) Remove IAM policy binding of a Cloud Spanner instance. diff --git a/gcloud/beta/spanner/instances/move b/gcloud/beta/spanner/instances/move new file mode 100644 index 000000000..b2b0b8e77 --- /dev/null +++ b/gcloud/beta/spanner/instances/move @@ -0,0 +1,40 @@ +NAME + gcloud beta spanner instances move - move the Cloud Spanner instance to the + specified instance config + +SYNOPSIS + gcloud beta spanner instances move INSTANCE --target-config=TARGET_CONFIG + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Move the Cloud Spanner instance to the specified instance config. + +EXAMPLES + To move the Cloud Spanner instance to the target instance configuration, + run: $ gcloud beta spanner instances move my-instance-id \ + --target-config=nam3 + +POSITIONAL ARGUMENTS + INSTANCE + Cloud Spanner instance ID. + +REQUIRED FLAGS + --target-config=TARGET_CONFIG + Target Instance configuration to move the instances. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud spanner instances move + + $ gcloud alpha spanner instances move + diff --git a/gcloud/builds/submit b/gcloud/builds/submit index f09fb6cf9..d198881a7 100644 --- a/gcloud/builds/submit +++ b/gcloud/builds/submit @@ -8,9 +8,11 @@ SYNOPSIS [--gcs-source-staging-dir=GCS_SOURCE_STAGING_DIR] [--git-source-dir=GIT_SOURCE_DIR] [--git-source-revision=GIT_SOURCE_REVISION] [--ignore-file=IGNORE_FILE] - [--machine-type=MACHINE_TYPE] [--region=REGION] [--revision=REVISION] - [--service-account=SERVICE_ACCOUNT] [--substitutions=[KEY=VALUE,...]] - [--suppress-logs] [--timeout=TIMEOUT] [--worker-pool=WORKER_POOL] + [--machine-type=MACHINE_TYPE] + [--polling-interval=POLLING_INTERVAL; default=1] [--region=REGION] + [--revision=REVISION] [--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 ...] @@ -141,6 +143,9 @@ FLAGS Machine type used to run the build. MACHINE_TYPE must be one of: e2-highcpu-32, e2-highcpu-8, e2-medium, n1-highcpu-32, n1-highcpu-8. + --polling-interval=POLLING_INTERVAL; default=1 + Amount of time in seconds to wait between polling build status. + --region=REGION The region of the Cloud Build Service to use. Must be set to a supported region name (e.g. us-central1). If unset, builds/region, diff --git a/gcloud/certificate-manager/trust-configs/create b/gcloud/certificate-manager/trust-configs/create index 15be79e4f..974b87105 100644 --- a/gcloud/certificate-manager/trust-configs/create +++ b/gcloud/certificate-manager/trust-configs/create @@ -4,8 +4,9 @@ NAME SYNOPSIS gcloud certificate-manager trust-configs create (TRUST_CONFIG : --location=LOCATION) - --trust-store=[intermediate-cas=INTERMEDIATE-CAS], - [trust-anchors=TRUST-ANCHORS] [--async] [--description=DESCRIPTION] + (--allowlisted-certificates=[ALLOWLISTED_CERTIFICATES,...] + --trust-store=[intermediate-cas=INTERMEDIATE-CAS], + [trust-anchors=TRUST-ANCHORS]) [--async] [--description=DESCRIPTION] [--labels=[KEY=VALUE,...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -54,20 +55,33 @@ POSITIONAL ARGUMENTS ▸ default value of location is [global]. REQUIRED FLAGS - --trust-store=[intermediate-cas=INTERMEDIATE-CAS],[trust-anchors=TRUST-ANCHORS] - Trust Store with the given trust anchor and intermediate CA PEM-encoded - certificates. Certificates should be provided in files. For multiple - file names, separate them by a semicolon (';') and quote them ('"'). - One file can contain multiple certificates. Intermediate CAs are - optional. + At least one of these must be specified: - Examples: + --allowlisted-certificates=[ALLOWLISTED_CERTIFICATES,...] + Allowlisted PEM-encoded certificates. Certificates should be provided + in files. For multiple file names, separate them by a comma (','). + One file can contain multiple certificates. - Single files: --trust-store trust-anchors=ta.pem,intermediate-cas=ica.pem + Examples: - No intermediate CAs: --trust-store trust-anchors=ta.pem + Single file: --allowlisted-certificates=ac.pem - Multiple files: --trust-store trust-anchors="ta1.pem;ta2.pem",intermediate-cas="ica1.pem;ica2.pem" + Multiple files: --allowlisted-certificates=ac1.pem,ac2.pem + + --trust-store=[intermediate-cas=INTERMEDIATE-CAS],[trust-anchors=TRUST-ANCHORS] + Trust Store with the given trust anchor and intermediate CA + PEM-encoded certificates. Certificates should be provided in files. + For multiple file names, separate them by a semicolon (';') and quote + them ('"'). One file can contain multiple certificates. Intermediate + CAs are optional. + + Examples: + + Single files: --trust-store trust-anchors=ta.pem,intermediate-cas=ica.pem + + No intermediate CAs: --trust-store trust-anchors=ta.pem + + Multiple files: --trust-store trust-anchors="ta1.pem;ta2.pem",intermediate-cas="ica1.pem;ica2.pem" OPTIONAL FLAGS --async diff --git a/gcloud/certificate-manager/trust-configs/update b/gcloud/certificate-manager/trust-configs/update index 3efddabae..eddb89637 100644 --- a/gcloud/certificate-manager/trust-configs/update +++ b/gcloud/certificate-manager/trust-configs/update @@ -3,11 +3,15 @@ NAME SYNOPSIS gcloud certificate-manager trust-configs update - (TRUST_CONFIG : --location=LOCATION) [--async] - [--description=DESCRIPTION] + (TRUST_CONFIG : --location=LOCATION) + [--add-allowlisted-certificates=[ADD_ALLOWLISTED_CERTIFICATES,...]] + [--async] [--description=DESCRIPTION] [--trust-store=[intermediate-cas=INTERMEDIATE-CAS], [trust-anchors=TRUST-ANCHORS]] [--update-labels=[KEY=VALUE,...]] - [--clear-labels | --remove-labels=[KEY,...]] [GCLOUD_WIDE_FLAG ...] + [--clear-allowlisted-certificates + | --remove-allowlisted-certificates=[REMOVE_ALLOWLISTED_CERTIFICATES, + ...]] [--clear-labels | --remove-labels=[KEY,...]] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION Update a TrustConfig. @@ -56,6 +60,17 @@ POSITIONAL ARGUMENTS ▸ default value of location is [global]. FLAGS + --add-allowlisted-certificates=[ADD_ALLOWLISTED_CERTIFICATES,...] + Add allowlisted PEM-encoded certificates. Certificates should be + provided in files. For multiple file names, separate them by a comma + (','). One file can contain multiple certificates. + + Examples: + + Single file: --add-allowlisted-certificates=ac.pem + + Multiple files: --add-allowlisted-certificates=ac1.pem,ac2.pem + --async Return immediately, without waiting for the operation in progress to complete. @@ -87,6 +102,22 @@ FLAGS contain only hyphens (-), underscores (_), lowercase characters, and numbers. + At most one of these can be specified: + + --clear-allowlisted-certificates + Clear all allowlisted certificates. + + --remove-allowlisted-certificates=[REMOVE_ALLOWLISTED_CERTIFICATES,...] + Remove allowlisted PEM-encoded certificates. Certificates should be + provided in files. For multiple file names, separate them by a comma + (','). One file can contain multiple certificates. + + Examples: + + Single file: --remove-allowlisted-certificates=ac.pem + + Multiple files: --remove-allowlisted-certificates=ac1.pem,ac2.pem + At most one of these can be specified: --clear-labels diff --git a/gcloud/compute/external-vpn-gateways/create b/gcloud/compute/external-vpn-gateways/create index 5e6b4f656..447e9a634 100644 --- a/gcloud/compute/external-vpn-gateways/create +++ b/gcloud/compute/external-vpn-gateways/create @@ -38,15 +38,20 @@ REQUIRED FLAGS For example, to create an external VPN gateway with one interface: $ gcloud compute external-vpn-gateways create MY-EXTERNAL-GATEWAY \ - --interfaces 0=8.9.9.9 + --interfaces 0=192.0.2.0 To create an external VPN gateway with two interfaces: $ gcloud compute external-vpn-gateways create MY-EXTERNAL-GATEWAY \ --interfaces - 0=8.9.9.9,1=8.9.9.10 + 0=192.0.2.0,1=192.0.2.1 To create an external VPN gateway with four interfaces: $ gcloud compute external-vpn-gateways create MY-EXTERNAL-GATEWAY \ --interfaces - 0=8.9.9.9,1=8.9.9.10,2=8.9.9.11,3=8.9.9.12 + 0=192.0.2.0,1=192.0.2.1,2=192.0.2.3,3=192.0.2.4 + + To create an external VPN gateway with IPv6 addresses on four + interfaces: $ gcloud compute external-vpn-gateways create + MY-EXTERNAL-GATEWAY \ --interfaces \ + 0=2001:db8::1,1=2001:db8::2,2=2001:db8::3,3=2001:db8::4 Note that the redundancy type of the gateway will be automatically inferred based on the number of interfaces provided: diff --git a/gcloud/compute/service-attachments/create b/gcloud/compute/service-attachments/create index 5e80e908d..c53a2e55e 100644 --- a/gcloud/compute/service-attachments/create +++ b/gcloud/compute/service-attachments/create @@ -5,7 +5,8 @@ NAME SYNOPSIS gcloud compute service-attachments create NAME --nat-subnets=NAT_SUBNETS,[NAT_SUBNETS,...] - --producer-forwarding-rule=PRODUCER_FORWARDING_RULE + (--producer-forwarding-rule=PRODUCER_FORWARDING_RULE + | --target-service=TARGET_SERVICE) [--connection-preference=CONNECTION_PREFERENCE; default="ACCEPT_AUTOMATIC"] [--consumer-accept-list=[PROJECT_OR_NETWORK=LIMIT,...]] @@ -50,8 +51,13 @@ REQUIRED FLAGS --nat-subnets=NAT_SUBNETS,[NAT_SUBNETS,...] The subnetworks provided by service producer to use for NAT - --producer-forwarding-rule=PRODUCER_FORWARDING_RULE - Target forwarding rule that receives forwarded traffic. + Exactly one of these must be specified: + + --producer-forwarding-rule=PRODUCER_FORWARDING_RULE + Target forwarding rule that receives forwarded traffic. + + --target-service=TARGET_SERVICE + URL of the target service that receives forwarded traffic. OPTIONAL FLAGS --connection-preference=CONNECTION_PREFERENCE; default="ACCEPT_AUTOMATIC" diff --git a/gcloud/compute/vpn-gateways/create b/gcloud/compute/vpn-gateways/create index 9cc4c29be..5a4ec9b89 100644 --- a/gcloud/compute/vpn-gateways/create +++ b/gcloud/compute/vpn-gateways/create @@ -4,7 +4,7 @@ NAME SYNOPSIS gcloud compute vpn-gateways create NAME --network=NETWORK - [--description=DESCRIPTION] + [--description=DESCRIPTION] [--gateway-ip-version=GATEWAY_IP_VERSION] [--interconnect-attachments=[INTERCONNECT_ATTACHMENTS,...]] [--region=REGION] [--stack-type=STACK_TYPE] [GCLOUD_WIDE_FLAG ...] @@ -36,6 +36,16 @@ OPTIONAL FLAGS --description=DESCRIPTION An optional, textual description for the VPN gateway. + --gateway-ip-version=GATEWAY_IP_VERSION + IP version of the HA VPN gateway. You must specify either IPv4 or IPv6. + If you do not specify this field, every HA VPN gateway interface will + be configured with an IPv4 address. GATEWAY_IP_VERSION must be one of: + + IPV4 + Every HA-VPN gateway interface is configured with an IPv4 address. + IPV6 + Every HA-VPN gateway interface is configured with an IPv6 address. + --interconnect-attachments=[INTERCONNECT_ATTACHMENTS,...] Names of interconnect attachments (VLAN attachments) associated with the VPN gateway interfaces. You must specify this field when using a diff --git a/gcloud/config/get b/gcloud/config/get index 287c06bd0..61627d298 100644 --- a/gcloud/config/get +++ b/gcloud/config/get @@ -370,10 +370,6 @@ AVAILABLE PROPERTIES Overrides API endpoint for gcloud eventarc publish command group. Defaults to https://eventarcpublishing.googleapis.com/ - events - Overrides API endpoint for gcloud events command group. Defaults to - https://events.googleapis.com/ - faultinjectiontesting Overrides API endpoint for gcloud fault-injection command group. Defaults to https://faultinjectiontesting.googleapis.com/ diff --git a/gcloud/config/help b/gcloud/config/help index 9c7a5c803..d140f7a6a 100644 --- a/gcloud/config/help +++ b/gcloud/config/help @@ -402,10 +402,6 @@ AVAILABLE PROPERTIES Overrides API endpoint for gcloud eventarc publish command group. Defaults to https://eventarcpublishing.googleapis.com/ - events - Overrides API endpoint for gcloud events command group. Defaults to - https://events.googleapis.com/ - faultinjectiontesting Overrides API endpoint for gcloud fault-injection command group. Defaults to https://faultinjectiontesting.googleapis.com/ diff --git a/gcloud/config/list b/gcloud/config/list index 85df477e4..d5e77319b 100644 --- a/gcloud/config/list +++ b/gcloud/config/list @@ -414,10 +414,6 @@ AVAILABLE PROPERTIES Overrides API endpoint for gcloud eventarc publish command group. Defaults to https://eventarcpublishing.googleapis.com/ - events - Overrides API endpoint for gcloud events command group. Defaults to - https://events.googleapis.com/ - faultinjectiontesting Overrides API endpoint for gcloud fault-injection command group. Defaults to https://faultinjectiontesting.googleapis.com/ diff --git a/gcloud/config/set b/gcloud/config/set index 104cc229f..14ce1cbad 100644 --- a/gcloud/config/set +++ b/gcloud/config/set @@ -417,10 +417,6 @@ AVAILABLE PROPERTIES Overrides API endpoint for gcloud eventarc publish command group. Defaults to https://eventarcpublishing.googleapis.com/ - events - Overrides API endpoint for gcloud events command group. Defaults to - https://events.googleapis.com/ - faultinjectiontesting Overrides API endpoint for gcloud fault-injection command group. Defaults to https://faultinjectiontesting.googleapis.com/ diff --git a/gcloud/config/unset b/gcloud/config/unset index 86e86a323..1d98801fb 100644 --- a/gcloud/config/unset +++ b/gcloud/config/unset @@ -378,10 +378,6 @@ AVAILABLE PROPERTIES Overrides API endpoint for gcloud eventarc publish command group. Defaults to https://eventarcpublishing.googleapis.com/ - events - Overrides API endpoint for gcloud events command group. Defaults to - https://events.googleapis.com/ - faultinjectiontesting Overrides API endpoint for gcloud fault-injection command group. Defaults to https://faultinjectiontesting.googleapis.com/ diff --git a/gcloud/database-migration/migration-jobs/resume b/gcloud/database-migration/migration-jobs/resume index 24c03e4d2..5a13475a8 100644 --- a/gcloud/database-migration/migration-jobs/resume +++ b/gcloud/database-migration/migration-jobs/resume @@ -4,7 +4,8 @@ NAME SYNOPSIS gcloud database-migration migration-jobs resume - (MIGRATION_JOB : --region=REGION) [GCLOUD_WIDE_FLAG ...] + (MIGRATION_JOB : --region=REGION) [--skip-validation] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION Resume a Database Migration Service migration job. @@ -47,6 +48,11 @@ POSITIONAL ARGUMENTS fully specified name; ▸ provide the argument --region on the command line. +FLAGS + --skip-validation + Resume the migration job without running prior configuration + verification. + 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/domains/registrations/configure/contacts b/gcloud/domains/registrations/configure/contacts index 9f24a578c..0e1e25c43 100644 --- a/gcloud/domains/registrations/configure/contacts +++ b/gcloud/domains/registrations/configure/contacts @@ -16,6 +16,17 @@ DESCRIPTION the registrant before they take effect. In order to resend the email, execute this command again. + NOTE: Please consider carefully any changes to contact privacy settings + when changing from "redacted-contact-data" to "public-contact-data." There + may be a delay in reflecting updates you make to registrant contact + information such that any changes you make to contact privacy (including + from "redacted-contact-data" to "public-contact-data") will be applied + without delay but changes to registrant contact information may take a + limited time to be publicized. This means that changes to contact privacy + from "redacted-contact-data" to "public-contact-data" may make the previous + registrant contact data public until the modified registrant contact + details are published. + EXAMPLES To start an interactive flow to configure contact settings for example.com, run: diff --git a/gcloud/edge-cloud/container/clusters/update b/gcloud/edge-cloud/container/clusters/update index 4ac57737d..dca47143a 100644 --- a/gcloud/edge-cloud/container/clusters/update +++ b/gcloud/edge-cloud/container/clusters/update @@ -70,7 +70,9 @@ FLAGS At most one of these can be specified: --clear-maintenance-window - If set, removes the maintenance window setting from the cluster. + If set, removes the maintenance window setting from the cluster. If + any exclusion windows exist, they must be removed beforehand as a + maintenance policy cannot exist without a maintenance window. Updates cluster maintenance window setting (more than one flags can be specified from this group) diff --git a/gcloud/eventarc/help b/gcloud/eventarc/help index 0f2909079..356c21976 100644 --- a/gcloud/eventarc/help +++ b/gcloud/eventarc/help @@ -36,9 +36,3 @@ GROUPS triggers Manage Eventarc triggers. - -NOTES - This variant is also available: - - $ gcloud beta eventarc - diff --git a/gcloud/eventarc/locations/help b/gcloud/eventarc/locations/help index b283f91da..7d8fd7466 100644 --- a/gcloud/eventarc/locations/help +++ b/gcloud/eventarc/locations/help @@ -17,9 +17,3 @@ COMMANDS list List locations available for Eventarc. - -NOTES - This variant is also available: - - $ gcloud beta eventarc locations - diff --git a/gcloud/eventarc/locations/list b/gcloud/eventarc/locations/list index e0dacf4c2..ae26d0723 100644 --- a/gcloud/eventarc/locations/list +++ b/gcloud/eventarc/locations/list @@ -53,9 +53,3 @@ GCLOUD WIDE FLAGS --trace-token, --user-output-enabled, --verbosity. Run $ gcloud help for details. - -NOTES - This variant is also available: - - $ gcloud beta eventarc locations list - diff --git a/gcloud/eventarc/triggers/create b/gcloud/eventarc/triggers/create index 4504973c2..2c8310d67 100644 --- a/gcloud/eventarc/triggers/create +++ b/gcloud/eventarc/triggers/create @@ -214,9 +214,3 @@ GCLOUD WIDE FLAGS --trace-token, --user-output-enabled, --verbosity. Run $ gcloud help for details. - -NOTES - This variant is also available: - - $ gcloud beta eventarc triggers create - diff --git a/gcloud/eventarc/triggers/delete b/gcloud/eventarc/triggers/delete index 0ef9b2125..7f919bace 100644 --- a/gcloud/eventarc/triggers/delete +++ b/gcloud/eventarc/triggers/delete @@ -58,9 +58,3 @@ GCLOUD WIDE FLAGS --trace-token, --user-output-enabled, --verbosity. Run $ gcloud help for details. - -NOTES - This variant is also available: - - $ gcloud beta eventarc triggers delete - diff --git a/gcloud/eventarc/triggers/describe b/gcloud/eventarc/triggers/describe index 1c675dfd9..006c36024 100644 --- a/gcloud/eventarc/triggers/describe +++ b/gcloud/eventarc/triggers/describe @@ -54,9 +54,3 @@ GCLOUD WIDE FLAGS --trace-token, --user-output-enabled, --verbosity. Run $ gcloud help for details. - -NOTES - This variant is also available: - - $ gcloud beta eventarc triggers describe - diff --git a/gcloud/eventarc/triggers/help b/gcloud/eventarc/triggers/help index f42646237..3225c2f4b 100644 --- a/gcloud/eventarc/triggers/help +++ b/gcloud/eventarc/triggers/help @@ -29,9 +29,3 @@ COMMANDS update Update an Eventarc trigger. - -NOTES - This variant is also available: - - $ gcloud beta eventarc triggers - diff --git a/gcloud/eventarc/triggers/list b/gcloud/eventarc/triggers/list index dce2558c2..95c9a95d7 100644 --- a/gcloud/eventarc/triggers/list +++ b/gcloud/eventarc/triggers/list @@ -84,9 +84,3 @@ GCLOUD WIDE FLAGS --trace-token, --user-output-enabled, --verbosity. Run $ gcloud help for details. - -NOTES - This variant is also available: - - $ gcloud beta eventarc triggers list - diff --git a/gcloud/eventarc/triggers/update b/gcloud/eventarc/triggers/update index 7046fc96a..b6f10d123 100644 --- a/gcloud/eventarc/triggers/update +++ b/gcloud/eventarc/triggers/update @@ -149,9 +149,3 @@ GCLOUD WIDE FLAGS --trace-token, --user-output-enabled, --verbosity. Run $ gcloud help for details. - -NOTES - This variant is also available: - - $ gcloud beta eventarc triggers update - diff --git a/gcloud/filestore/instances/help b/gcloud/filestore/instances/help index 993d4f1e5..18d19393a 100644 --- a/gcloud/filestore/instances/help +++ b/gcloud/filestore/instances/help @@ -36,6 +36,9 @@ COMMANDS restore Restore a Filestore instance from a backup. + revert + Revert a Filestore instance. + update Update a Filestore instance. diff --git a/gcloud/filestore/instances/revert b/gcloud/filestore/instances/revert new file mode 100644 index 000000000..f800e009c --- /dev/null +++ b/gcloud/filestore/instances/revert @@ -0,0 +1,80 @@ +NAME + gcloud filestore instances revert - revert a Filestore instance + +SYNOPSIS + gcloud filestore instances revert (INSTANCE : --location=LOCATION) + --target-snapshot=TARGET_SNAPSHOT [--async] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Revert a Filestore instance to the target snapshot. + + This command can fail for the following reasons: + ▪ The target snapshot does not exist. + ▪ The active account does not have permission to revert the instance. + ▪ The service tier of the instance does not support the operation. + +EXAMPLES + To revert an instance with the name my-instance that's located in + us-central1 to the target snapshot named my-snapshot , run: + + $ gcloud filestore instances revert my-instance \ + --target-snapshot=my-snapshot --location=us-central1 + +POSITIONAL ARGUMENTS + Instance resource - Arguments and flags that specify the Filestore + instance to revert. 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 instance 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. + + INSTANCE + ID of the instance or fully qualified identifier for the instance. + + To set the instance attribute: + ▸ provide the argument instance on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + The location of the Filestore instance. + + To set the location attribute: + ▸ provide the argument instance on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ set the property filestore/location. + +REQUIRED FLAGS + --target-snapshot=TARGET_SNAPSHOT + Name of the Filestore snapshot to revert to. + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + +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 file/v1 API. The full documentation for this API can + be found at: https://cloud.google.com/filestore/ + +NOTES + This variant is also available: + + $ gcloud beta filestore instances revert + diff --git a/gcloud/infra-manager/deployments/apply b/gcloud/infra-manager/deployments/apply index 926f79dcd..09845f66b 100644 --- a/gcloud/infra-manager/deployments/apply +++ b/gcloud/infra-manager/deployments/apply @@ -202,8 +202,9 @@ FLAGS See gcloud topic gcloudignore for more information. --local-source=LOCAL_SOURCE - Local storage path where config files are stored. e.g. - ./path/to/blueprint + Local storage path where config files are stored. When using this + option, terraform config file referecnes outside this storage path is + not supported. e.g. ./path/to/blueprint Examples: diff --git a/gcloud/infra-manager/deployments/import-statefile b/gcloud/infra-manager/deployments/import-statefile index fef4dbab9..f1023e1d1 100644 --- a/gcloud/infra-manager/deployments/import-statefile +++ b/gcloud/infra-manager/deployments/import-statefile @@ -4,7 +4,7 @@ NAME SYNOPSIS gcloud infra-manager deployments import-statefile - (DEPLOYMENT : --location=LOCATION) --lock-id=LOCK_ID + (DEPLOYMENT : --location=LOCATION) --lock-id=LOCK_ID [--file=FILE] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -54,6 +54,12 @@ REQUIRED FLAGS --lock-id=LOCK_ID Lock ID of the lock file to verify person importing owns lock. +OPTIONAL FLAGS + --file=FILE + File path for importing statefile into a deployment. It specifies the + local file path of an existing Terraform statefile to directly upload + for a deployment. + 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/infra-manager/previews/create b/gcloud/infra-manager/previews/create index 2fc9cafb7..a8832a8f0 100644 --- a/gcloud/infra-manager/previews/create +++ b/gcloud/infra-manager/previews/create @@ -191,8 +191,9 @@ FLAGS See gcloud topic gcloudignore for more information. --local-source=LOCAL_SOURCE - Local storage path where config files are stored. e.g. - ./path/to/blueprint + Local storage path where config files are stored. When using this + option, terraform config file referecnes outside this storage path is + not supported. e.g. ./path/to/blueprint Examples: diff --git a/gcloud/metastore/services/create b/gcloud/metastore/services/create index f8d129f76..eef22af65 100644 --- a/gcloud/metastore/services/create +++ b/gcloud/metastore/services/create @@ -267,10 +267,8 @@ FLAGS Small instance size, maps to a scaling factor of 0.5. --scaling-factor=SCALING_FACTOR - The scaling factor of the service. This should be a float in the - range [0.1,6.0]. If the value is less than 1.0, then it should be a - multiple of 0.1. If the value is greater than 1.0, then it should be - a whole number. Float values should be formatted as x.y. + The scaling factor of the service. Can be one of [0.1, 0.2, 0.3, 0.4, + 0.5, 0.6, 0.7, 0.8, 0.9, 1.0, 2.0, 3.0, 4.0, 5.0, 6.0]. --tier=TIER The tier of the service. TIER must be one of: diff --git a/gcloud/metastore/services/update b/gcloud/metastore/services/update index b61041c0d..dbebcf824 100644 --- a/gcloud/metastore/services/update +++ b/gcloud/metastore/services/update @@ -146,10 +146,8 @@ FLAGS Small instance size, maps to a scaling factor of 0.5. --scaling-factor=SCALING_FACTOR - The scaling factor of the service. This should be a float in the - range [0.1,6.0]. If the value is less than 1.0, then it should be a - multiple of 0.1. If the value is greater than 1.0, then it should be - a whole number. + The scaling factor of the service. Can be one of [0.1, 0.2, 0.3, 0.4, + 0.5, 0.6, 0.7, 0.8, 0.9, 1.0, 2.0, 3.0, 4.0, 5.0, 6.0]. --tier=TIER The tier of the service. TIER must be one of: diff --git a/gcloud/ml-engine/models/add-iam-policy-binding b/gcloud/ml-engine/models/add-iam-policy-binding index f7e4ca8b0..716380a41 100644 --- a/gcloud/ml-engine/models/add-iam-policy-binding +++ b/gcloud/ml-engine/models/add-iam-policy-binding @@ -10,21 +10,21 @@ DESCRIPTION Add IAM policy binding to a model. EXAMPLES - To add an IAM policy binding for the role of 'roles/ml.admin' for the user - 'test-user@gmail.com' on a model with identifier 'my_model', run: + To add an IAM policy binding for the role of roles/ml.admin for the user + test-user@gmail.com on a model with identifier my_model, run: $ gcloud ml-engine models add-iam-policy-binding my_model \ --member='user:test-user@gmail.com' --role='roles/ml.admin' - To add an IAM policy binding for the role of 'roles/ml.admin' to the - service account 'test-proj1@example.domain.com', run: + To add an IAM policy binding for the role of roles/ml.admin to the service + account test-proj1@example.domain.com, run: $ gcloud ml-engine models add-iam-policy-binding my_model \ --member='serviceAccount:test-proj1@example.domain.com' \ --role='roles/ml.admin' - To add an IAM policy binding for the role of 'roles/ml.admin' for all - authenticated users on a model with identifier 'my_model', run: + To add an IAM policy binding for the role of roles/ml.admin for all + authenticated users on a model with identifier my_model, run: $ gcloud ml-engine models add-iam-policy-binding my_model \ --member='allAuthenticatedUsers' --role='roles/ml.admin' diff --git a/gcloud/ml-engine/models/remove-iam-policy-binding b/gcloud/ml-engine/models/remove-iam-policy-binding index 426ffee16..cba97c774 100644 --- a/gcloud/ml-engine/models/remove-iam-policy-binding +++ b/gcloud/ml-engine/models/remove-iam-policy-binding @@ -12,14 +12,14 @@ DESCRIPTION get-iam-policy for examples of how to specify a model resource. EXAMPLES - To remove an IAM policy binding for the role of 'roles/ml.admin' for the - user 'test-user@gmail.com' on model with identifier 'my_model', run: + To remove an IAM policy binding for the role of roles/ml.admin for the user + test-user@gmail.com on model with identifier my_model, run: $ gcloud ml-engine models remove-iam-policy-binding my_model \ --member='user:test-user@gmail.com' --role='roles/ml.admin' - To remove an IAM policy binding for the role of 'roles/ml.admin' from all - authenticated users on model 'my_model', run: + To remove an IAM policy binding for the role of roles/ml.admin from all + authenticated users on model my_model, run: $ gcloud ml-engine models remove-iam-policy-binding my_model \ --member='allAuthenticatedUsers' --role='roles/ml.admin' diff --git a/gcloud/projects/add-iam-policy-binding b/gcloud/projects/add-iam-policy-binding index 391b98b55..5f53447c4 100644 --- a/gcloud/projects/add-iam-policy-binding +++ b/gcloud/projects/add-iam-policy-binding @@ -14,24 +14,23 @@ DESCRIPTION condition. EXAMPLES - To add an IAM policy binding for the role of 'roles/editor' for the user - 'test-user@gmail.com' on a project with identifier 'example-project-id-1', - run: + To add an IAM policy binding for the role of roles/editor for the user + test-user@gmail.com on a project with identifier example-project-id-1, run: $ gcloud projects add-iam-policy-binding example-project-id-1 \ --member='user:test-user@gmail.com' --role='roles/editor' - To add an IAM policy binding for the role of 'roles/editor' to the service - account 'test-proj1@example.domain.com' on a project with identifier - 'example-project-id-1', run: + To add an IAM policy binding for the role of roles/editor to the service + account test-proj1@example.domain.com on a project with identifier + example-project-id-1, run: $ gcloud projects add-iam-policy-binding example-project-id-1 \ --member='serviceAccount:test-proj1@example.domain.com' \ --role='roles/editor' To add an IAM policy binding that expires at the end of the year 2021 for - the role of 'roles/browser' and the user 'test-user@gmail.com' on a project - with identifier 'example-project-id-1', run: + the role of roles/browser and the user test-user@gmail.com on a project + with identifier example-project-id-1, run: $ gcloud projects add-iam-policy-binding example-project-id-1 \ --member='user:test-user@gmail.com' --role='roles/browser' \ diff --git a/gcloud/projects/create b/gcloud/projects/create index 1243138e3..1a43683a4 100644 --- a/gcloud/projects/create +++ b/gcloud/projects/create @@ -66,7 +66,7 @@ FLAGS --tags=[KEY=VALUE,...] List of tags KEY=VALUE pairs to bind. Each item must be expressed as - "=". + =. Example: 123/environment=production,123/costCenter=marketing diff --git a/gcloud/projects/remove-iam-policy-binding b/gcloud/projects/remove-iam-policy-binding index 452386f00..01143b88e 100644 --- a/gcloud/projects/remove-iam-policy-binding +++ b/gcloud/projects/remove-iam-policy-binding @@ -14,25 +14,23 @@ DESCRIPTION condition. EXAMPLES - To remove an IAM policy binding for the role of 'roles/editor' for the user - 'test-user@gmail.com' on project with identifier 'example-project-id-1', - run: + To remove an IAM policy binding for the role of roles/editor for the user + test-user@gmail.com on project with identifier example-project-id-1, run: $ gcloud projects remove-iam-policy-binding example-project-id-1 \ --member='user:test-user@gmail.com' --role='roles/editor' - To remove an IAM policy binding for the role of 'roles/editor' from all - authenticated users on project 'example-project-id-1', run: + To remove an IAM policy binding for the role of roles/editor from all + authenticated users on project example-project-id-1, run: $ gcloud projects remove-iam-policy-binding example-project-id-1 \ --member='allAuthenticatedUsers' --role='roles/editor' To remove an IAM policy binding with a condition of expression='request.time < timestamp("2019-01-01T00:00:00Z")', - title='expires_end_of_2018', and description='Expires at midnight on - 2018-12-31' for the role of 'roles/browser' for the user - 'test-user@gmail.com' on project with identifier 'example-project-id-1', - run: + title='expires_end_of_2018', and description=Expires at midnight on + 2018-12-31 for the role of roles/browser for the user test-user@gmail.com + on project with identifier example-project-id-1, run: $ gcloud projects remove-iam-policy-binding example-project-id-1 \ --member='user:test-user@gmail.com' --role='roles/browser' \ @@ -41,8 +39,8 @@ EXAMPLES tion=Expires at midnight on 2018-12-31' To remove all IAM policy bindings regardless of the condition for the role - of 'roles/browser' and for the user 'test-user@gmail.com' on project with - identifier 'example-project-id-1', run: + of roles/browser and for the user test-user@gmail.com on project with + identifier example-project-id-1, run: $ gcloud projects remove-iam-policy-binding example-project-id-1 \ --member='user:test-user@gmail.com' --role='roles/browser' --all diff --git a/gcloud/projects/update b/gcloud/projects/update index a6ecf8b71..0e6e3f509 100644 --- a/gcloud/projects/update +++ b/gcloud/projects/update @@ -14,7 +14,7 @@ DESCRIPTION EXAMPLES The following command updates a project with the ID example-foo-bar-1 to - have the name "Foo Bar & Grill": + have the name Foo Bar & Grill: $ gcloud projects update example-foo-bar-1 --name="Foo Bar & Grill" diff --git a/gcloud/resource-manager/folders/create b/gcloud/resource-manager/folders/create index 83a6d797e..808d36726 100644 --- a/gcloud/resource-manager/folders/create +++ b/gcloud/resource-manager/folders/create @@ -39,7 +39,7 @@ OPTIONAL FLAGS --tags=[KEY=VALUE,...] List of tags KEY=VALUE pairs to bind. Each item must be expressed as - "=". + =. Example: 123/environment=production,123/costCenter=marketing diff --git a/gcloud/services/api-keys/create b/gcloud/services/api-keys/create index f1271f87b..105e5d652 100644 --- a/gcloud/services/api-keys/create +++ b/gcloud/services/api-keys/create @@ -59,11 +59,9 @@ EXAMPLES The content of 'my-flags.yaml' is as following: - --api-target: - service: - - "foo.service.com" + service: "foo.service.com" - --api-target: - service: - - "bar.service.com" + service: "bar.service.com" methods: - "foomethod" - "barmethod" diff --git a/gcloud/spanner/instances/help b/gcloud/spanner/instances/help index d7c4fb61d..42f6570ff 100644 --- a/gcloud/spanner/instances/help +++ b/gcloud/spanner/instances/help @@ -33,6 +33,9 @@ COMMANDS list List the Cloud Spanner instances in this project. + move + Move the Cloud Spanner instance to the specified instance config. + remove-iam-policy-binding Remove IAM policy binding of a Cloud Spanner instance. diff --git a/gcloud/spanner/instances/move b/gcloud/spanner/instances/move new file mode 100644 index 000000000..428e5bd1f --- /dev/null +++ b/gcloud/spanner/instances/move @@ -0,0 +1,38 @@ +NAME + gcloud spanner instances move - move the Cloud Spanner instance to the + specified instance config + +SYNOPSIS + gcloud spanner instances move INSTANCE --target-config=TARGET_CONFIG + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Move the Cloud Spanner instance to the specified instance config. + +EXAMPLES + To move the Cloud Spanner instance to the target instance configuration, + run: $ gcloud spanner instances move my-instance-id --target-config=nam3 + +POSITIONAL ARGUMENTS + INSTANCE + Cloud Spanner instance ID. + +REQUIRED FLAGS + --target-config=TARGET_CONFIG + Target Instance configuration to move the instances. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + These variants are also available: + + $ gcloud alpha spanner instances move + + $ gcloud beta spanner instances move + diff --git a/gcloud/workbench/instances/create b/gcloud/workbench/instances/create index c670f1c88..fbe54e97d 100644 --- a/gcloud/workbench/instances/create +++ b/gcloud/workbench/instances/create @@ -159,7 +159,7 @@ FLAGS NVIDIA_TESLA_K80, NVIDIA_TESLA_P100, NVIDIA_TESLA_V100, NVIDIA_TESLA_P4, NVIDIA_TESLA_T4, NVIDIA_TESLA_A100, NVIDIA_A100_80GB, NVIDIA_TESLA_T4_VWS, NVIDIA_TESLA_P100_VWS, - NVIDIA_TESLA_P4_VWS. + NVIDIA_TESLA_P4_VWS, NVIDIA_L4. Boot disk configurations. diff --git a/gcloud/workbench/instances/update b/gcloud/workbench/instances/update index 08425bd9a..d8dcc37ee 100644 --- a/gcloud/workbench/instances/update +++ b/gcloud/workbench/instances/update @@ -92,7 +92,7 @@ FLAGS NVIDIA_TESLA_K80, NVIDIA_TESLA_P100, NVIDIA_TESLA_V100, NVIDIA_TESLA_P4, NVIDIA_TESLA_T4, NVIDIA_TESLA_A100, NVIDIA_A100_80GB, NVIDIA_TESLA_T4_VWS, NVIDIA_TESLA_P100_VWS, - NVIDIA_TESLA_P4_VWS. + NVIDIA_TESLA_P4_VWS, NVIDIA_L4. GPU driver configurations.