From a459a88a5f1044aefd25c18c8535ade4ecaece01 Mon Sep 17 00:00:00 2001 From: Automated Date: Wed, 12 Mar 2025 10:54:38 +0000 Subject: [PATCH] gcloud: Wed Mar 12 10:54:38 UTC 2025 --- gcloud/_version | 8 +- gcloud/alpha/ai/endpoints/deploy-model | 5 + gcloud/alpha/app/update | 11 +- gcloud/alpha/bq/migration-workflows/create | 43 ++ gcloud/alpha/bq/migration-workflows/help | 3 + gcloud/alpha/compute/backend-services/create | 40 ++ gcloud/alpha/compute/backend-services/update | 40 ++ gcloud/alpha/compute/commitments/create | 18 +- gcloud/alpha/compute/disk-settings/describe | 38 ++ gcloud/alpha/compute/disk-settings/help | 13 +- gcloud/alpha/compute/disk-settings/update | 67 +++ gcloud/alpha/compute/disks/help | 5 + .../disks/wait-for-replication-catchup | 96 ++++ .../compute/instance-groups/managed/create | 3 + .../compute/instance-groups/managed/update | 3 + .../interconnects/attachments/partner/create | 24 + .../interconnects/attachments/partner/update | 12 + .../compute/tpus/queued-resources/create | 19 +- gcloud/alpha/compute/tpus/tpu-vm/create | 17 +- gcloud/alpha/compute/tpus/tpu-vm/update | 117 +++-- .../developer-connect/connections/create | 11 +- .../connections/git-repository-links/delete | 2 +- .../developer-connect/connections/update | 40 +- .../edge-cloud/container/clusters/update | 5 + gcloud/alpha/iap/settings/get | 10 +- gcloud/alpha/iap/settings/set | 10 +- gcloud/alpha/iap/web/add-iam-policy-binding | 4 +- gcloud/alpha/iap/web/get-iam-policy | 4 +- .../alpha/iap/web/remove-iam-policy-binding | 4 +- gcloud/alpha/iap/web/set-iam-policy | 4 +- gcloud/alpha/managed-kafka/help | 3 + .../alpha/managed-kafka/operations/describe | 75 +++ gcloud/alpha/managed-kafka/operations/help | 35 ++ .../workers => managed-kafka/operations}/list | 58 ++- gcloud/alpha/netapp/storage-pools/create | 16 +- gcloud/alpha/netapp/storage-pools/update | 10 +- .../multicast-group-ranges/create | 11 +- .../multicast-group-ranges/help | 3 + .../multicast-group-ranges/update | 145 ++++++ gcloud/alpha/pubsub/message-transforms/help | 2 +- gcloud/alpha/pubsub/message-transforms/test | 4 +- gcloud/alpha/run/deploy | 8 +- gcloud/alpha/run/help | 3 - gcloud/alpha/run/jobs/create | 3 + gcloud/alpha/run/jobs/deploy | 3 + gcloud/alpha/run/jobs/execute | 3 + gcloud/alpha/run/jobs/update | 3 + gcloud/alpha/run/multi-region-services/update | 3 + gcloud/alpha/run/services/update | 3 + gcloud/alpha/run/worker-pools/deploy | 3 + gcloud/alpha/run/worker-pools/update | 3 + gcloud/alpha/run/workers/delete | 58 --- gcloud/alpha/run/workers/deploy | 483 ----------------- gcloud/alpha/run/workers/describe | 62 --- gcloud/alpha/run/workers/help | 60 --- gcloud/alpha/run/workers/revisions/delete | 68 --- gcloud/alpha/run/workers/revisions/describe | 66 --- gcloud/alpha/run/workers/revisions/help | 45 -- gcloud/alpha/run/workers/update | 488 ------------------ .../alpha/run/workers/update-instance-split | 122 ----- gcloud/alpha/scc/manage/services/describe | 2 + gcloud/alpha/scc/manage/services/update | 2 + .../storage/buckets/anywhere-caches/create | 4 +- .../storage/buckets/anywhere-caches/describe | 4 +- .../storage/buckets/anywhere-caches/disable | 4 +- .../storage/buckets/anywhere-caches/help | 4 +- .../storage/buckets/anywhere-caches/list | 4 +- .../storage/buckets/anywhere-caches/pause | 4 +- .../storage/buckets/anywhere-caches/resume | 4 +- .../storage/buckets/anywhere-caches/update | 4 +- gcloud/app/create | 10 +- gcloud/app/update | 11 +- gcloud/artifacts/docker/upgrade/migrate | 29 +- gcloud/artifacts/repositories/create | 7 +- gcloud/beta/ai/endpoints/deploy-model | 5 + gcloud/beta/app/create | 11 +- gcloud/beta/app/update | 11 +- gcloud/beta/compute/disk-settings/describe | 36 ++ gcloud/beta/compute/disk-settings/help | 32 ++ gcloud/beta/compute/disk-settings/update | 65 +++ gcloud/beta/compute/disks/create | 11 + .../beta/compute/future-reservations/create | 46 +- gcloud/beta/compute/help | 3 + .../beta/compute/snapshot-settings/describe | 7 +- gcloud/beta/compute/snapshot-settings/update | 19 +- gcloud/beta/compute/snapshots/add-labels | 13 +- gcloud/beta/compute/snapshots/create | 54 ++ gcloud/beta/compute/snapshots/delete | 15 +- gcloud/beta/compute/snapshots/describe | 13 +- gcloud/beta/compute/snapshots/list | 14 +- gcloud/beta/compute/snapshots/remove-labels | 13 +- gcloud/beta/compute/snapshots/update | 15 +- gcloud/beta/dataflow/flex-template/build | 3 +- gcloud/beta/dataflow/flex-template/run | 3 +- gcloud/beta/dataproc/batches/submit/help | 6 - .../beta/developer-connect/connections/create | 11 +- .../connections/git-repository-links/delete | 2 +- .../beta/developer-connect/connections/update | 40 +- .../beta/filestore/instances/promote-replica | 30 +- gcloud/beta/iap/settings/get | 10 +- gcloud/beta/iap/settings/set | 10 +- gcloud/beta/iap/web/add-iam-policy-binding | 12 +- gcloud/beta/iap/web/get-iam-policy | 12 +- gcloud/beta/iap/web/remove-iam-policy-binding | 12 +- gcloud/beta/iap/web/set-iam-policy | 12 +- gcloud/beta/managed-kafka/help | 3 + gcloud/beta/managed-kafka/operations/describe | 73 +++ gcloud/beta/managed-kafka/operations/help | 33 ++ gcloud/beta/managed-kafka/operations/list | 87 ++++ gcloud/beta/netapp/storage-pools/create | 16 +- gcloud/beta/netapp/storage-pools/update | 10 +- .../multicast-group-ranges/create | 11 +- .../multicast-group-ranges/help | 3 + .../multicast-group-ranges/update | 143 +++++ gcloud/beta/policy-intelligence/help | 28 + gcloud/beta/policy-intelligence/simulate/help | 25 + .../policy-intelligence/simulate/orgpolicy | 66 +++ gcloud/beta/run/deploy | 8 +- gcloud/beta/run/jobs/create | 3 + gcloud/beta/run/jobs/deploy | 3 + gcloud/beta/run/jobs/execute | 3 + gcloud/beta/run/jobs/update | 3 + gcloud/beta/run/multi-region-services/update | 3 + gcloud/beta/run/services/update | 3 + gcloud/compute/commitments/create | 5 +- gcloud/compute/reservations/create | 13 +- gcloud/compute/reservations/update | 15 +- gcloud/dataflow/flex-template/build | 3 +- gcloud/dataflow/flex-template/run | 3 +- gcloud/dataproc/batches/submit/help | 6 - gcloud/developer-connect/connections/create | 11 +- .../connections/git-repository-links/delete | 2 +- gcloud/developer-connect/connections/update | 40 +- gcloud/filestore/instances/promote-replica | 27 +- gcloud/managed-kafka/help | 3 + gcloud/managed-kafka/operations/describe | 72 +++ gcloud/managed-kafka/operations/help | 32 ++ gcloud/managed-kafka/operations/list | 85 +++ gcloud/policy-intelligence/help | 6 + gcloud/run/deploy | 8 +- gcloud/run/services/update | 3 + gcloud/scc/manage/services/describe | 2 + gcloud/scc/manage/services/update | 2 + gcloud/storage/buckets/anywhere-caches/create | 64 +++ .../storage/buckets/anywhere-caches/describe | 41 ++ .../storage/buckets/anywhere-caches/disable | 44 ++ gcloud/storage/buckets/anywhere-caches/help | 44 ++ .../buckets/anywhere-caches}/list | 30 +- gcloud/storage/buckets/anywhere-caches/pause | 36 ++ gcloud/storage/buckets/anywhere-caches/resume | 38 ++ gcloud/storage/buckets/anywhere-caches/update | 56 ++ gcloud/storage/buckets/help | 3 + 152 files changed, 2634 insertions(+), 1748 deletions(-) create mode 100644 gcloud/alpha/bq/migration-workflows/create create mode 100644 gcloud/alpha/compute/disk-settings/describe create mode 100644 gcloud/alpha/compute/disk-settings/update create mode 100644 gcloud/alpha/compute/disks/wait-for-replication-catchup create mode 100644 gcloud/alpha/managed-kafka/operations/describe create mode 100644 gcloud/alpha/managed-kafka/operations/help rename gcloud/alpha/{run/workers => managed-kafka/operations}/list (52%) create mode 100644 gcloud/alpha/network-services/multicast-group-ranges/update delete mode 100644 gcloud/alpha/run/workers/delete delete mode 100644 gcloud/alpha/run/workers/deploy delete mode 100644 gcloud/alpha/run/workers/describe delete mode 100644 gcloud/alpha/run/workers/help delete mode 100644 gcloud/alpha/run/workers/revisions/delete delete mode 100644 gcloud/alpha/run/workers/revisions/describe delete mode 100644 gcloud/alpha/run/workers/revisions/help delete mode 100644 gcloud/alpha/run/workers/update delete mode 100644 gcloud/alpha/run/workers/update-instance-split create mode 100644 gcloud/beta/compute/disk-settings/describe create mode 100644 gcloud/beta/compute/disk-settings/help create mode 100644 gcloud/beta/compute/disk-settings/update create mode 100644 gcloud/beta/managed-kafka/operations/describe create mode 100644 gcloud/beta/managed-kafka/operations/help create mode 100644 gcloud/beta/managed-kafka/operations/list create mode 100644 gcloud/beta/network-services/multicast-group-ranges/update create mode 100644 gcloud/beta/policy-intelligence/help create mode 100644 gcloud/beta/policy-intelligence/simulate/help create mode 100644 gcloud/beta/policy-intelligence/simulate/orgpolicy create mode 100644 gcloud/managed-kafka/operations/describe create mode 100644 gcloud/managed-kafka/operations/help create mode 100644 gcloud/managed-kafka/operations/list create mode 100644 gcloud/storage/buckets/anywhere-caches/create create mode 100644 gcloud/storage/buckets/anywhere-caches/describe create mode 100644 gcloud/storage/buckets/anywhere-caches/disable create mode 100644 gcloud/storage/buckets/anywhere-caches/help rename gcloud/{alpha/run/workers/revisions => storage/buckets/anywhere-caches}/list (75%) create mode 100644 gcloud/storage/buckets/anywhere-caches/pause create mode 100644 gcloud/storage/buckets/anywhere-caches/resume create mode 100644 gcloud/storage/buckets/anywhere-caches/update diff --git a/gcloud/_version b/gcloud/_version index d20778e32..e0fb69340 100644 --- a/gcloud/_version +++ b/gcloud/_version @@ -1,8 +1,8 @@ -Google Cloud SDK 513.0.0 -alpha 2025.02.28 -beta 2025.02.28 +Google Cloud SDK 514.0.0 +alpha 2025.03.07 +beta 2025.03.07 bq 2.1.14 bundled-python3-unix 3.12.8 -core 2025.02.28 +core 2025.03.07 gcloud-crc32c 1.0.0 gsutil 5.33 diff --git a/gcloud/alpha/ai/endpoints/deploy-model b/gcloud/alpha/ai/endpoints/deploy-model index 863d9a7ba..42019339a 100644 --- a/gcloud/alpha/ai/endpoints/deploy-model +++ b/gcloud/alpha/ai/endpoints/deploy-model @@ -11,6 +11,7 @@ SYNOPSIS [--enable-container-logging] [--machine-type=MACHINE_TYPE] [--max-replica-count=MAX_REPLICA_COUNT] [--min-replica-count=MIN_REPLICA_COUNT] + [--multihost-gpu-node-count=MULTIHOST_GPU_NODE_COUNT] [--reservation-affinity=[key=KEY], [reservation-affinity-type=RESERVATION-AFFINITY-TYPE], [values=VALUES]] [--service-account=SERVICE_ACCOUNT] [--spot] @@ -133,6 +134,10 @@ OPTIONAL FLAGS If not specified and the uploaded models use dedicated resources, the default value is 1. + --multihost-gpu-node-count=MULTIHOST_GPU_NODE_COUNT + The number of nodes per replica for multihost GPU deployments. Required + for multihost GPU deployments. + --reservation-affinity=[key=KEY],[reservation-affinity-type=RESERVATION-AFFINITY-TYPE],[values=VALUES] A ReservationAffinity can be used to configure a Vertex AI resource (e.g., a DeployedModel) to draw its Compute Engine resources from a diff --git a/gcloud/alpha/app/update b/gcloud/alpha/app/update index b365d6cd7..995193176 100644 --- a/gcloud/alpha/app/update +++ b/gcloud/alpha/app/update @@ -3,7 +3,8 @@ NAME SYNOPSIS gcloud alpha app update [--service-account=SERVICE_ACCOUNT] - [--[no-]split-health-checks] [GCLOUD_WIDE_FLAG ...] + [--[no-]split-health-checks] [--ssl-policy=SSL_POLICY] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) This command is used to update settings on an app engine @@ -18,6 +19,10 @@ EXAMPLES $ gcloud alpha app update --service-account=SERVICE_ACCOUNT + To update the app-level minimum SSL policy of the application: + + $ gcloud alpha app update --ssl-policy=TLS_VERSION_1_2 + FLAGS --service-account=SERVICE_ACCOUNT The app-level default service account to update the app with. @@ -27,6 +32,10 @@ FLAGS --split-health-checks to enable and --no-split-health-checks to disable. + --ssl-policy=SSL_POLICY + The app-level SSL policy to update the app with. SSL_POLICY must be one + of: TLS_VERSION_1_0, TLS_VERSION_1_2. + GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, diff --git a/gcloud/alpha/bq/migration-workflows/create b/gcloud/alpha/bq/migration-workflows/create new file mode 100644 index 000000000..2756e4391 --- /dev/null +++ b/gcloud/alpha/bq/migration-workflows/create @@ -0,0 +1,43 @@ +NAME + gcloud alpha bq migration-workflows create - create migrationWorkflows + +SYNOPSIS + gcloud alpha bq migration-workflows create --config-file=CONFIG_FILE + --location=LOCATION [--async] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Create a migrationWorkflow + +EXAMPLES + To create a migration workflow in US synchronously based on a config file, + run: + + $ gcloud alpha bq migration-workflows create --location=US \ + --config-file=config_file.yaml --no-async + +REQUIRED FLAGS + --config-file=CONFIG_FILE + The path to the migration workflows config file. + + --location=LOCATION + The location of the migration workflow. + +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. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/bq/migration-workflows/help b/gcloud/alpha/bq/migration-workflows/help index 47f6c37d2..e49c91b12 100644 --- a/gcloud/alpha/bq/migration-workflows/help +++ b/gcloud/alpha/bq/migration-workflows/help @@ -15,6 +15,9 @@ GCLOUD WIDE FLAGS COMMANDS COMMAND is one of the following: + create + (ALPHA) create migrationWorkflows. + delete (ALPHA) Delete migrationWorkflows. diff --git a/gcloud/alpha/compute/backend-services/create b/gcloud/alpha/compute/backend-services/create index 0be981aa6..c80c6eff2 100644 --- a/gcloud/alpha/compute/backend-services/create +++ b/gcloud/alpha/compute/backend-services/create @@ -43,6 +43,8 @@ SYNOPSIS [--subsetting-policy=SUBSETTING_POLICY; default="NONE"] [--subsetting-subset-size=SUBSETTING_SUBSET_SIZE] [--timeout=TIMEOUT; default="30s"] [--tracking-mode=TRACKING_MODE] + [--zonal-affinity-spillover=ZONAL_AFFINITY_SPILLOVER] + [--zonal-affinity-spillover-ratio=ZONAL_AFFINITY_SPILLOVER_RATIO] [--cache-key-query-string-blacklist=[QUERY_STRING,...] | --cache-key-query-string-whitelist=QUERY_STRING,[...]] [--custom-metrics=[CUSTOM_METRICS,...] @@ -743,6 +745,44 @@ FLAGS (https://cloud.google.com/load-balancing/docs/network/networklb-backend-service#tracking-mode). TRACKING_MODE must be one of: PER_CONNECTION, PER_SESSION. + --zonal-affinity-spillover=ZONAL_AFFINITY_SPILLOVER + Specifies whether zonal affinity is enabled or not. + + Can only be set if load balancing scheme is INTERNAL, + + The possible values are: + + ZONAL_AFFINITY_DISABLED + Zonal Affinity is disabled. The load balancer distributes new + connections to all healthy backend endpoints across all zones. + + ZONAL_AFFINITY_STAY_WITHIN_ZONE + Zonal Affinity is enabled. The load balancer distributes new + connections to all healthy backend endpoints in the local zone only. + If there are no healthy backend endpoints in the local zone, the load + balancer distributes new connections to all backend endpoints in the + local zone. + + ZONAL_AFFINITY_SPILL_CROSS_ZONE + Zonal Affinity is enabled. The load balancer distributes new + connections to all healthy backend endpoints in the local zone only. + If there aren't enough healthy backend endpoints in the local zone, + the load balancer distributes new connections to all healthy backend + endpoints across all zones. + + ZONAL_AFFINITY_SPILLOVER must be one of: ZONAL_AFFINITY_DISABLED, + ZONAL_AFFINITY_STAY_WITHIN_ZONE, ZONAL_AFFINITY_SPILL_CROSS_ZONE. + + --zonal-affinity-spillover-ratio=ZONAL_AFFINITY_SPILLOVER_RATIO + The value of the field must be in [0, 1]. When the ratio of the count + of healthy backend endpoints in a zone to the count of backend + endpoints in that same zone is equal to or above this threshold, the + load balancer distributes new connections to all healthy endpoints in + the local zone only. When the ratio of the count of healthy backend + endpoints in a zone to the count of backend endpoints in that same zone + is below this threshold, the load balancer distributes all new + connections to all healthy endpoints across all zones. + At most one of these can be specified: --cache-key-query-string-blacklist=[QUERY_STRING,...] diff --git a/gcloud/alpha/compute/backend-services/update b/gcloud/alpha/compute/backend-services/update index 63b0f4f61..e7b97c876 100644 --- a/gcloud/alpha/compute/backend-services/update +++ b/gcloud/alpha/compute/backend-services/update @@ -37,6 +37,8 @@ SYNOPSIS [--subsetting-policy=SUBSETTING_POLICY; default="NONE"] [--subsetting-subset-size=SUBSETTING_SUBSET_SIZE] [--timeout=TIMEOUT] [--tracking-mode=TRACKING_MODE] + [--zonal-affinity-spillover=ZONAL_AFFINITY_SPILLOVER] + [--zonal-affinity-spillover-ratio=ZONAL_AFFINITY_SPILLOVER_RATIO] [--bypass-cache-on-request-headers=BYPASS_CACHE_ON_REQUEST_HEADERS | --no-bypass-cache-on-request-headers] [--cache-key-query-string-blacklist=[QUERY_STRING,...] @@ -556,6 +558,44 @@ FLAGS (https://cloud.google.com/load-balancing/docs/network/networklb-backend-service#tracking-mode). TRACKING_MODE must be one of: PER_CONNECTION, PER_SESSION. + --zonal-affinity-spillover=ZONAL_AFFINITY_SPILLOVER + Specifies whether zonal affinity is enabled or not. + + Can only be set if load balancing scheme is INTERNAL, + + The possible values are: + + ZONAL_AFFINITY_DISABLED + Zonal Affinity is disabled. The load balancer distributes new + connections to all healthy backend endpoints across all zones. + + ZONAL_AFFINITY_STAY_WITHIN_ZONE + Zonal Affinity is enabled. The load balancer distributes new + connections to all healthy backend endpoints in the local zone only. + If there are no healthy backend endpoints in the local zone, the load + balancer distributes new connections to all backend endpoints in the + local zone. + + ZONAL_AFFINITY_SPILL_CROSS_ZONE + Zonal Affinity is enabled. The load balancer distributes new + connections to all healthy backend endpoints in the local zone only. + If there aren't enough healthy backend endpoints in the local zone, + the load balancer distributes new connections to all healthy backend + endpoints across all zones. + + ZONAL_AFFINITY_SPILLOVER must be one of: ZONAL_AFFINITY_DISABLED, + ZONAL_AFFINITY_STAY_WITHIN_ZONE, ZONAL_AFFINITY_SPILL_CROSS_ZONE. + + --zonal-affinity-spillover-ratio=ZONAL_AFFINITY_SPILLOVER_RATIO + The value of the field must be in [0, 1]. When the ratio of the count + of healthy backend endpoints in a zone to the count of backend + endpoints in that same zone is equal to or above this threshold, the + load balancer distributes new connections to all healthy endpoints in + the local zone only. When the ratio of the count of healthy backend + endpoints in a zone to the count of backend endpoints in that same zone + is below this threshold, the load balancer distributes all new + connections to all healthy endpoints across all zones. + At most one of these can be specified: --bypass-cache-on-request-headers=BYPASS_CACHE_ON_REQUEST_HEADERS diff --git a/gcloud/alpha/compute/commitments/create b/gcloud/alpha/compute/commitments/create index 3ce16632a..3831100a9 100644 --- a/gcloud/alpha/compute/commitments/create +++ b/gcloud/alpha/compute/commitments/create @@ -107,15 +107,15 @@ OPTIONAL FLAGS Type of commitment. memory-optimized indicates that the commitment is for memory-optimized VMs. TYPE must be one of: accelerator-optimized, accelerator-optimized-a3, accelerator-optimized-a3-mega, - accelerator-optimized-a3-ultra, compute-optimized, - compute-optimized-c2d, compute-optimized-c3, compute-optimized-c3d, - compute-optimized-h3, general-purpose, general-purpose-c4, - general-purpose-c4a, general-purpose-e2, general-purpose-n2, - general-purpose-n2d, general-purpose-n4, general-purpose-t2d, - graphics-optimized, memory-optimized, memory-optimized-m3, - memory-optimized-m4, memory-optimized-x4, memory-optimized-x4-16tb, - memory-optimized-x4-24tb, memory-optimized-x4-32tb, - storage-optimized-z3. + accelerator-optimized-a3-ultra, accelerator-optimized-a4, + compute-optimized, compute-optimized-c2d, compute-optimized-c3, + compute-optimized-c3d, compute-optimized-h3, general-purpose, + general-purpose-c4, general-purpose-c4a, general-purpose-e2, + general-purpose-n2, general-purpose-n2d, general-purpose-n4, + general-purpose-t2d, graphics-optimized, memory-optimized, + memory-optimized-m3, memory-optimized-m4, memory-optimized-x4, + memory-optimized-x4-16tb, memory-optimized-x4-24tb, + memory-optimized-x4-32tb, storage-optimized-z3. Manage the reservations to be created with the commitment. diff --git a/gcloud/alpha/compute/disk-settings/describe b/gcloud/alpha/compute/disk-settings/describe new file mode 100644 index 000000000..5910ff642 --- /dev/null +++ b/gcloud/alpha/compute/disk-settings/describe @@ -0,0 +1,38 @@ +NAME + gcloud alpha compute disk-settings describe - describe a Google Compute + Engine disk setting + +SYNOPSIS + gcloud alpha compute disk-settings describe (--region=REGION | --zone=ZONE) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Describe a Google Compute Engine disk setting. + +REQUIRED FLAGS + Scope for disk settings. + + Exactly one of these must be specified: + + --region=REGION + region for disk settings + + --zone=ZONE + Zone for disk settings + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud beta compute disk-settings describe + diff --git a/gcloud/alpha/compute/disk-settings/help b/gcloud/alpha/compute/disk-settings/help index 79e0164ac..b4289eee6 100644 --- a/gcloud/alpha/compute/disk-settings/help +++ b/gcloud/alpha/compute/disk-settings/help @@ -15,9 +15,20 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. +COMMANDS + COMMAND is one of the following: + + describe + (ALPHA) Describe a Google Compute Engine disk setting. + + update + (ALPHA) Update disk settings. + NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. + access allowlist. This variant is also available: + + $ gcloud beta compute disk-settings diff --git a/gcloud/alpha/compute/disk-settings/update b/gcloud/alpha/compute/disk-settings/update new file mode 100644 index 000000000..1cbeb3911 --- /dev/null +++ b/gcloud/alpha/compute/disk-settings/update @@ -0,0 +1,67 @@ +NAME + gcloud alpha compute disk-settings update - update disk settings + +SYNOPSIS + gcloud alpha compute disk-settings update (--region=REGION | --zone=ZONE) + [--access-location-policy=ACCESS_LOCATION_POLICY] + [--add-access-locations=[ADD_ACCESS_LOCATIONS,...]] + [--remove-access-locations=[REMOVE_ACCESS_LOCATIONS,...]] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Update disk settings. + +EXAMPLES + To update the disk settings in zone us-west1-a, add the access location + ``us-central1 `` and remove the access location ``us-central2`` in the + project my-gcp-project, run: + + $ gcloud alpha compute disk-settings update \ + --add-access-locations=us-central1 \ + --remove-access-locations=us-central2 --project=my-gcp-project \ + --zone=us-west1-a + +REQUIRED FLAGS + Scope for disk settings. + + Exactly one of these must be specified: + + --region=REGION + region for disk settings + + --zone=ZONE + Zone for disk settings + +OPTIONAL FLAGS + --access-location-policy=ACCESS_LOCATION_POLICY + The access location policy for disk settings. ACCESS_LOCATION_POLICY + must be one of: + + all-regions + All regions will be allowed to access the source disk. + specific-regions + Only the specified regions will be allowed to access the source + disk. + + --add-access-locations=[ADD_ACCESS_LOCATIONS,...] + Access locations to add to disk settings + + --remove-access-locations=[REMOVE_ACCESS_LOCATIONS,...] + Access locations to remove from disk settings + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud beta compute disk-settings update + diff --git a/gcloud/alpha/compute/disks/help b/gcloud/alpha/compute/disks/help index 3b4c63fce..998c5859f 100644 --- a/gcloud/alpha/compute/disks/help +++ b/gcloud/alpha/compute/disks/help @@ -97,6 +97,11 @@ COMMANDS update (ALPHA) Update a Compute Engine persistent disk. + wait-for-replication-catchup + (ALPHA) Provides the operation id for the asynchronous replication of a + Compute Engine persistent disk-pair that can be used to wait for the + replication to catch up. + NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct diff --git a/gcloud/alpha/compute/disks/wait-for-replication-catchup b/gcloud/alpha/compute/disks/wait-for-replication-catchup new file mode 100644 index 000000000..3661ce9e0 --- /dev/null +++ b/gcloud/alpha/compute/disks/wait-for-replication-catchup @@ -0,0 +1,96 @@ +NAME + gcloud alpha compute disks wait-for-replication-catchup - provides the + operation id for the asynchronous replication of a Compute Engine + persistent disk-pair that can be used to wait for the replication to + catch up + +SYNOPSIS + gcloud alpha compute disks wait-for-replication-catchup DISK_NAME + [--max-wait-duration=MAX_WAIT_DURATION] [--region=REGION | --zone=ZONE] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) gcloud alpha compute disks wait-for-replication-catchup fetches the + operation id that can be used to track the status of async replication for + a Compute Engine persistent disk-pair. The operation id can be used to wait + for the replication to catch up. This command can be invoked only on the + primary disk. + +EXAMPLES + Note: The max-wait-duration is optional. If not specified, the default + value would be picked up from the API. Wait for replication catchup can + only be invoked on the primary scope. To wait for the replication catchup + for the primary disk 'my-disk-1' in zone 'us-east1-a' under project + 'my-project1' to catch up with the secondary disk 'my-disk-2' in zone + 'us-west1-a' in any project, the following command can be used (with custom + wait duration of 20s): + + $ gcloud alpha compute disks wait-for-replication-catchup \ + my-disk-1 --zone=us-east1-a --project=my-project1 \ + --max-wait-duration=20s + +POSITIONAL ARGUMENTS + DISK_NAME + Name of the disk to operate on. + +FLAGS + --max-wait-duration=MAX_WAIT_DURATION + Maximum duration to wait for the replication catchup. + + At most one of these can be specified: + + --region=REGION + Region of the disk to operate on. If not specified, you might be + prompted to select a region (interactive mode only). + + To avoid prompting when this flag is omitted, you can set the + compute/region property: + + $ gcloud config set compute/region REGION + + A list of regions can be fetched by running: + + $ gcloud compute regions list + + To unset the property, run: + + $ gcloud config unset compute/region + + Alternatively, the region can be stored in the environment variable + CLOUDSDK_COMPUTE_REGION. + + --zone=ZONE + Zone of the disk to operate on. If not specified and the compute/zone + property isn't set, you might be prompted to select a zone + (interactive mode only). + + To avoid prompting when this flag is omitted, you can set the + compute/zone property: + + $ gcloud config set compute/zone ZONE + + A list of zones can be fetched by running: + + $ gcloud compute zones list + + To unset the property, run: + + $ gcloud config unset compute/zone + + Alternatively, the zone can be stored in the environment variable + CLOUDSDK_COMPUTE_ZONE. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/compute/instance-groups/managed/create b/gcloud/alpha/compute/instance-groups/managed/create index 3c8658094..69a7ef44c 100644 --- a/gcloud/alpha/compute/instance-groups/managed/create +++ b/gcloud/alpha/compute/instance-groups/managed/create @@ -108,6 +108,9 @@ OPTIONAL FLAGS (Default) MIG automatically repairs a failed VM by recreating it. do-nothing MIG does not repair a failed VM. + delete + MIG deletes a failed VM. Deleting the VM decreases the target size + of the MIG. --description=DESCRIPTION An optional description for this group. diff --git a/gcloud/alpha/compute/instance-groups/managed/update b/gcloud/alpha/compute/instance-groups/managed/update index bec4e2bf7..3a06a0f61 100644 --- a/gcloud/alpha/compute/instance-groups/managed/update +++ b/gcloud/alpha/compute/instance-groups/managed/update @@ -96,6 +96,9 @@ FLAGS (Default) MIG automatically repairs a failed VM by recreating it. do-nothing MIG does not repair a failed VM. + delete + MIG deletes a failed VM. Deleting the VM decreases the target size + of the MIG. --description=DESCRIPTION An optional description for this group. To clear the description, set diff --git a/gcloud/alpha/compute/interconnects/attachments/partner/create b/gcloud/alpha/compute/interconnects/attachments/partner/create index e3051d495..9444f65cf 100644 --- a/gcloud/alpha/compute/interconnects/attachments/partner/create +++ b/gcloud/alpha/compute/interconnects/attachments/partner/create @@ -5,6 +5,10 @@ NAME SYNOPSIS gcloud alpha compute interconnects attachments partner create NAME --edge-availability-domain=AVAILABILITY_DOMAIN --router=ROUTER + [--candidate-cloud-router-ip-address=CANDIDATE_CLOUD_ROUTER_IP_ADDRESS] + [--candidate-cloud-router-ipv6-address=CANDIDATE_CLOUD_ROUTER_IPV6_ADDRESS] + [--candidate-customer-router-ip-address=CANDIDATE_CUSTOMER_ROUTER_IP_ADDRESS] + [--candidate-customer-router-ipv6-address=CANDIDATE_CUSTOMER_ROUTER_IPV6_ADDRESS] [--description=DESCRIPTION] [--dry-run] [--enable-admin] [--encryption=ENCRYPTION] [--ipsec-internal-addresses=[ADDRESSES]] [--mtu=MTU] [--region=REGION] [--stack-type=STACK_TYPE] @@ -46,6 +50,26 @@ REQUIRED FLAGS The Google Cloud Router to use for dynamic routing. OPTIONAL FLAGS + --candidate-cloud-router-ip-address=CANDIDATE_CLOUD_ROUTER_IP_ADDRESS + Single IPv4 address + prefix length to be configured on the cloud + router interface for this interconnect attachment. Example: + 74.133.16.1/30 + + --candidate-cloud-router-ipv6-address=CANDIDATE_CLOUD_ROUTER_IPV6_ADDRESS + Single IPv6 address + prefix length to be configured on the cloud + router interface for this interconnect attachment. Example: + 2fff:eec0:3201:0:0:0:0:1/125 + + --candidate-customer-router-ip-address=CANDIDATE_CUSTOMER_ROUTER_IP_ADDRESS + Single IPv4 address + prefix length to be configured on the customer + router interface for this interconnect attachment. Example: + 74.133.16.2/30 + + --candidate-customer-router-ipv6-address=CANDIDATE_CUSTOMER_ROUTER_IPV6_ADDRESS + Single IPv6 address + prefix length to be configured on the customer + router interface for this interconnect attachment. Example: + 2fff:eec0:3201:0:0:0:0:2/125 + --description=DESCRIPTION Human-readable plain-text description of attachment. diff --git a/gcloud/alpha/compute/interconnects/attachments/partner/update b/gcloud/alpha/compute/interconnects/attachments/partner/update index d81f52ea6..ffecf7fe4 100644 --- a/gcloud/alpha/compute/interconnects/attachments/partner/update +++ b/gcloud/alpha/compute/interconnects/attachments/partner/update @@ -4,6 +4,8 @@ NAME SYNOPSIS gcloud alpha compute interconnects attachments partner update NAME + [--candidate-cloud-router-ipv6-address=CANDIDATE_CLOUD_ROUTER_IPV6_ADDRESS] + [--candidate-customer-router-ipv6-address=CANDIDATE_CUSTOMER_ROUTER_IPV6_ADDRESS] [--description=DESCRIPTION] [--enable-admin] [--mtu=MTU] [--region=REGION] [--stack-type=STACK_TYPE] [--update-labels=[KEY=VALUE,...]] @@ -20,6 +22,16 @@ POSITIONAL ARGUMENTS Name of the interconnect attachment to patch. FLAGS + --candidate-cloud-router-ipv6-address=CANDIDATE_CLOUD_ROUTER_IPV6_ADDRESS + Single IPv6 address + prefix length to be configured on the cloud + router interface for this interconnect attachment. Example: + 2fff:eec0:3201:0:0:0:0:1/125 + + --candidate-customer-router-ipv6-address=CANDIDATE_CUSTOMER_ROUTER_IPV6_ADDRESS + Single IPv6 address + prefix length to be configured on the customer + router interface for this interconnect attachment. Example: + 2fff:eec0:3201:0:0:0:0:2/125 + --description=DESCRIPTION Human-readable plain-text description of attachment. diff --git a/gcloud/alpha/compute/tpus/queued-resources/create b/gcloud/alpha/compute/tpus/queued-resources/create index 4a13d8e4d..2a274e757 100644 --- a/gcloud/alpha/compute/tpus/queued-resources/create +++ b/gcloud/alpha/compute/tpus/queued-resources/create @@ -11,10 +11,12 @@ SYNOPSIS [--autocheckpoint-enabled] [--best-effort] [--boot-disk=[KEY=VALUE,...]] [--data-disk=[mode=MODE],[source=SOURCE]] [--description=DESCRIPTION] [--guaranteed] [--labels=[KEY=VALUE,...]] - [--metadata=[KEY=VALUE,...]] [--metadata-from-file=[KEY=VALUE,...]] - [--range=RANGE] [--reserved] [--scopes=[SCOPES,...]] - [--service-account=SERVICE_ACCOUNT] [--shielded-secure-boot] [--spot] - [--tags=[TAGS,...]] [--valid-after-duration=VALID_AFTER_DURATION] + [--max-run-duration=MAX_RUN_DURATION] [--metadata=[KEY=VALUE,...]] + [--metadata-from-file=[KEY=VALUE,...]] + [--provisioning-model=PROVISIONING_MODEL] [--range=RANGE] [--reserved] + [--scopes=[SCOPES,...]] [--service-account=SERVICE_ACCOUNT] + [--shielded-secure-boot] [--spot] [--tags=[TAGS,...]] + [--valid-after-duration=VALID_AFTER_DURATION] [--valid-after-time=VALID_AFTER_TIME] [--valid-until-duration=VALID_UNTIL_DURATION] [--valid-until-time=VALID_UNTIL_TIME] @@ -206,6 +208,11 @@ OPTIONAL FLAGS Resource labels to represent user-provided metadata. See https://cloud.google.com/compute/docs/labeling-resources for details. + --max-run-duration=MAX_RUN_DURATION + A duration after which the resource will be terminated. Used with + flex-start. See $ gcloud topic datetimes for information on duration + formats. + --metadata=[KEY=VALUE,...] List of comma-separated metadata key-value pairs for the Cloud TPU VM node. Example: --metadata='key1=value1,key2=value2' @@ -214,6 +221,10 @@ OPTIONAL FLAGS Same as --metadata except the value for the entry will be read from a local file. Example: --metadata-from-file='key1=value1.txt' + --provisioning-model=PROVISIONING_MODEL + If provided, the resource will be provisioned with the specified + provisioning model. + --range=RANGE CIDR range for the TPU. diff --git a/gcloud/alpha/compute/tpus/tpu-vm/create b/gcloud/alpha/compute/tpus/tpu-vm/create index 2c9bd405b..f58c5195c 100644 --- a/gcloud/alpha/compute/tpus/tpu-vm/create +++ b/gcloud/alpha/compute/tpus/tpu-vm/create @@ -8,10 +8,10 @@ SYNOPSIS [--description=DESCRIPTION] [--internal-ips] [--labels=[KEY=VALUE,...]] [--metadata=[KEY=VALUE,...]] [--metadata-from-file=[KEY=VALUE,...]] [--network=NETWORK; default="default"] [--preemptible] - [--queue-count=QUEUE_COUNT] [--range=RANGE] [--reserved] - [--scopes=[SCOPES,...]] [--service-account=SERVICE_ACCOUNT] - [--shielded-secure-boot] [--spot] [--subnetwork=SUBNETWORK] - [--tags=[TAGS,...]] + [--queue-count=QUEUE_COUNT] [--range=RANGE] [--reservation=RESERVATION] + [--reserved] [--scopes=[SCOPES,...]] + [--service-account=SERVICE_ACCOUNT] [--shielded-secure-boot] [--spot] + [--subnetwork=SUBNETWORK] [--tags=[TAGS,...]] [--accelerator-type=ACCELERATOR_TYPE; default="v2-8" | --topology=TOPOLOGY --type=TYPE] [GCLOUD_WIDE_FLAG ...] @@ -173,6 +173,15 @@ OPTIONAL FLAGS network, or the provided network is peered with another network that is using that CIDR range. + --reservation=RESERVATION + The name of the reservation. This can either be the full name or just + the name. However, a full name is required if the reservation is not in + the default project. + + Full reservation name format is: + + projects//reservations/ + --reserved When specified, will attempt to create the TPU node under reservations made in the current project. The reservations can be made separately diff --git a/gcloud/alpha/compute/tpus/tpu-vm/update b/gcloud/alpha/compute/tpus/tpu-vm/update index 2e0f34fa5..dd459fa22 100644 --- a/gcloud/alpha/compute/tpus/tpu-vm/update +++ b/gcloud/alpha/compute/tpus/tpu-vm/update @@ -5,12 +5,13 @@ SYNOPSIS gcloud alpha compute tpus tpu-vm update (TPU : --zone=ZONE) [--add-tags=[TAGS,...]] [--async] [--description=DESCRIPTION] [--internal-ips] [--update-labels=[KEY=VALUE,...]] - [--attach-disk=[SOURCE=DATA_DISK,...] | --detach-disk=DATA_DISK] [--clear-labels | --remove-labels=[KEY,...]] [--clear-tags | --remove-tags=[TAG,...]] [--metadata-from-file=[KEY=VALUE,...] | --update-metadata=[KEY=VALUE,...] --clear-metadata - | --remove-metadata=[KEY,...]] [GCLOUD_WIDE_FLAG ...] + | --remove-metadata=[KEY,...]] + [--worker=[WORKER,...] --attach-disk=[SOURCE=DATA_DISK,...] + | --detach-disk=DATA_DISK] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Update a Cloud TPU VM node. @@ -100,45 +101,6 @@ FLAGS See https://cloud.google.com/compute/docs/labeling-resources for details. - At most one of these can be specified: - - --attach-disk=[SOURCE=DATA_DISK,...] - Attach a data disk to the TPU VM. For example, - - $ gcloud alpha compute tpus tpu-vm update example-tpu \ - --attach-disk \ - source=projects/my-project/zones/us-central1-c/disks/my-disk,\ - mode=read-only --zone=us-central1-c - - attaches the disk named - 'projects/my-project/zones/us-central1-c/disks/my-disk' to a TPU VM - named 'example-tpu' in read-only mode in zone us-central1-c. - - The following keys are allowed: - - source - Specify the full path to an existing disk. Required. The disk - must be in the same zone. - - mode - Specify the mode in which to attach this disk. Valid options are - 'read-write', 'read-only'. If not specified, the default is - 'read-write'. - - --detach-disk=DATA_DISK - Detach a data disk from the TPU VM. For example, - - This flag must be repeated to provide multiple data disks. For - example: - - $ gcloud alpha compute tpus tpu-vm update example-tpu \ - --detach-disk=projects/my-project/zones/us-central1-c/disks/\ - my-disk --zone=us-central1-c - - detaches the disk named - 'projects/my-project/zones/us-central1-c/disks/my-disk' from a TPU VM - named 'example-tpu' in zone us-central1-c. - At most one of these can be specified: --clear-labels @@ -212,6 +174,79 @@ FLAGS exist it is silently ignored. If --update-metadata is also specified then --update-metadata is applied first. + --worker=[WORKER,...] + List of worker IDs to apply attach/detach disk to. If not specified, + the update is applied to all workers. Only numeric values are allowed. + The only exception is 'all'. + + --attach-disk and --worker can be used to specify which workers to + attach the disk to. For example: + + $ gcloud alpha compute tpus tpu-vm update example-tpu \ + --attach-disk \ + source=projects/my-project/zones/us-central1-c/disks/my-disk,\ + mode=read-only --zone=us-central1-c + --worker=0,1 + + attaches the disk named + 'projects/my-project/zones/us-central1-c/disks/my-disk' to worker 0 and + 1 of a TPU VM named 'example-tpu' in read-only mode in zone + us-central1-c. if --worker is not specified or --worker=all is + specified, the disk is attached to all workers. + + --detach-disk and --worker can be used to specify which workers to + detach the disk from. For example: + + $ gcloud alpha compute tpus tpu-vm update example-tpu \ + --detach-disk=projects/my-project/zones/us-central1-c/disks/\ + my-disk --zone=us-central1-c + --worker=0,1 + + detaches the disk named + 'projects/my-project/zones/us-central1-c/disks/my-disk' from worker 0 + and 1 of a TPU VM named 'example-tpu' in zone us-central1-c. if + --worker is not specified or --worker=all is specified, the disk is + attached to all workers. + + At most one of these can be specified: + + --attach-disk=[SOURCE=DATA_DISK,...] + Attach a data disk to the TPU VM. For example, + + $ gcloud alpha compute tpus tpu-vm update example-tpu \ + --attach-disk \ + source=projects/my-project/zones/us-central1-c/disks/my-disk,\ + mode=read-only --zone=us-central1-c + + attaches the disk named + 'projects/my-project/zones/us-central1-c/disks/my-disk' to a TPU VM + named 'example-tpu' in read-only mode in zone us-central1-c. + + The following keys are allowed: + + source + Specify the full path to an existing disk. Required. The disk + must be in the same zone. + + mode + Specify the mode in which to attach this disk. Valid options are + 'read-write', 'read-only'. If not specified, the default is + 'read-write'. + + --detach-disk=DATA_DISK + Detach a data disk from the TPU VM. For example, + + This flag must be repeated to provide multiple data disks. For + example: + + $ gcloud alpha compute tpus tpu-vm update example-tpu \ + --detach-disk=projects/my-project/zones/us-central1-c/disks/\ + my-disk --zone=us-central1-c + + detaches the disk named + 'projects/my-project/zones/us-central1-c/disks/my-disk' from a TPU VM + named 'example-tpu' in zone us-central1-c. + GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, diff --git a/gcloud/alpha/developer-connect/connections/create b/gcloud/alpha/developer-connect/connections/create index 10f0bbae7..94a11b20c 100644 --- a/gcloud/alpha/developer-connect/connections/create +++ b/gcloud/alpha/developer-connect/connections/create @@ -5,9 +5,8 @@ NAME SYNOPSIS gcloud alpha developer-connect connections create CONNECTION [--annotations=[ANNOTATIONS,...]] [--async] [--disabled] [--etag=ETAG] - [--git-proxy-config-enabled] [--labels=[LABELS,...]] - [--location=LOCATION] [--namespace=NAMESPACE] [--request-id=REQUEST_ID] - [--secret=SECRET] [--validate-only] + [--labels=[LABELS,...]] [--location=LOCATION] [--namespace=NAMESPACE] + [--request-id=REQUEST_ID] [--secret=SECRET] [--validate-only] [--bitbucket-cloud-config-authorizer-credential-user-token-secret-version=BITBUCKET_CLOUD_CONFIG_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION --bitbucket-cloud-config-read-authorizer-credential-user-token-secret-version=BITBUCKET_CLOUD_CONFIG_READ_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION --bitbucket-cloud-config-webhook-secret-version=BITBUCKET_CLOUD_CONFIG_WEBHOOK_SECRET_VERSION --bitbucket-cloud-config-workspace=BITBUCKET_CLOUD_CONFIG_WORKSPACE | [--bitbucket-data-center-config-authorizer-credential-user-token-secret-version=BITBUCKET_DATA_CENTER_CONFIG_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION --bitbucket-data-center-config-host-uri=BITBUCKET_DATA_CENTER_CONFIG_HOST_URI --bitbucket-data-center-config-read-authorizer-credential-user-token-secret-version=BITBUCKET_DATA_CENTER_CONFIG_READ_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION --bitbucket-data-center-config-webhook-secret-version=BITBUCKET_DATA_CENTER_CONFIG_WEBHOOK_SECRET_VERSION : --bitbucket-data-center-config-service-directory=BITBUCKET_DATA_CENTER_CONFIG_SERVICE_DIRECTORY --bitbucket-data-center-config-ssl-ca-certificate=BITBUCKET_DATA_CENTER_CONFIG_SSL_CA_CERTIFICATE] | [--github-config-app=GITHUB_CONFIG_APP : --github-config-app-installation-id=GITHUB_CONFIG_APP_INSTALLATION_ID --github-config-authorizer-credential-oauth-token-secret-version=GITHUB_CONFIG_AUTHORIZER_CREDENTIAL_OAUTH_TOKEN_SECRET_VERSION] | [--github-enterprise-config-host-uri=GITHUB_ENTERPRISE_CONFIG_HOST_URI : --github-enterprise-config-app-id=GITHUB_ENTERPRISE_CONFIG_APP_ID --github-enterprise-config-app-installation-id=GITHUB_ENTERPRISE_CONFIG_APP_INSTALLATION_ID --github-enterprise-config-private-key-secret-version=GITHUB_ENTERPRISE_CONFIG_PRIVATE_KEY_SECRET_VERSION --github-enterprise-config-service-directory=GITHUB_ENTERPRISE_CONFIG_SERVICE_DIRECTORY --github-enterprise-config-ssl-ca-certificate=GITHUB_ENTERPRISE_CONFIG_SSL_CA_CERTIFICATE --github-enterprise-config-webhook-secret-version=GITHUB_ENTERPRISE_CONFIG_WEBHOOK_SECRET_VERSION] | --gitlab-config-authorizer-credential-user-token-secret-version=GITLAB_CONFIG_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION --gitlab-config-read-authorizer-credential-user-token-secret-version=GITLAB_CONFIG_READ_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION --gitlab-config-webhook-secret-version=GITLAB_CONFIG_WEBHOOK_SECRET_VERSION | [--gitlab-enterprise-config-authorizer-credential-user-token-secret-version=GITLAB_ENTERPRISE_CONFIG_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION --gitlab-enterprise-config-host-uri=GITLAB_ENTERPRISE_CONFIG_HOST_URI --gitlab-enterprise-config-read-authorizer-credential-user-token-secret-version=GITLAB_ENTERPRISE_CONFIG_READ_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION --gitlab-enterprise-config-webhook-secret-version=GITLAB_ENTERPRISE_CONFIG_WEBHOOK_SECRET_VERSION : --gitlab-enterprise-config-service-directory=GITLAB_ENTERPRISE_CONFIG_SERVICE_DIRECTORY --gitlab-enterprise-config-ssl-ca-certificate=GITLAB_ENTERPRISE_CONFIG_SSL_CA_CERTIFICATE]] [(--crypto-key-config-reference=CRYPTO_KEY_CONFIG_REFERENCE : --key-ring=KEY_RING)] [GCLOUD_WIDE_FLAG ...] @@ -87,12 +86,6 @@ FLAGS fields, and may be sent on update and delete requests to ensure the client has an up-to-date value before proceeding. - The git proxy configuration. - - --git-proxy-config-enabled - Setting this to true allows the git proxy to be used for performing - git operations on the repositories linked in the connection. - --labels=[LABELS,...] Labels as key value pairs. diff --git a/gcloud/alpha/developer-connect/connections/git-repository-links/delete b/gcloud/alpha/developer-connect/connections/git-repository-links/delete index 1d2439818..65d28ef0c 100644 --- a/gcloud/alpha/developer-connect/connections/git-repository-links/delete +++ b/gcloud/alpha/developer-connect/connections/git-repository-links/delete @@ -13,7 +13,7 @@ DESCRIPTION EXAMPLES To delete a git repository link my-git-repository-link in a connection - my-comection in location us-central1 run: + my-connection in location us-central1 run: $ gcloud alpha developer-connect connections git-repository-links \ delete my-git-repository-link --connection=my-connection \ --location=us-central1 diff --git a/gcloud/alpha/developer-connect/connections/update b/gcloud/alpha/developer-connect/connections/update index 4d0a1fabb..425f3bd42 100644 --- a/gcloud/alpha/developer-connect/connections/update +++ b/gcloud/alpha/developer-connect/connections/update @@ -10,10 +10,10 @@ SYNOPSIS [--annotations=[ANNOTATIONS,...] | --update-annotations=[UPDATE_ANNOTATIONS,...] --clear-annotations | --remove-annotations=[__REMOVE_ANNOTATIONS,...]] - [--bitbucket-cloud-config-authorizer-credential-user-token-secret-version=BITBUCKET_CLOUD_CONFIG_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION --bitbucket-cloud-config-read-authorizer-credential-user-token-secret-version=BITBUCKET_CLOUD_CONFIG_READ_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION --bitbucket-cloud-config-workspace=BITBUCKET_CLOUD_CONFIG_WORKSPACE | --bitbucket-data-center-config-authorizer-credential-user-token-secret-version=BITBUCKET_DATA_CENTER_CONFIG_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION --bitbucket-data-center-config-host-uri=BITBUCKET_DATA_CENTER_CONFIG_HOST_URI --bitbucket-data-center-config-read-authorizer-credential-user-token-secret-version=BITBUCKET_DATA_CENTER_CONFIG_READ_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION --bitbucket-data-center-config-service-directory=BITBUCKET_DATA_CENTER_CONFIG_SERVICE_DIRECTORY --bitbucket-data-center-config-ssl-ca-certificate=BITBUCKET_DATA_CENTER_CONFIG_SSL_CA_CERTIFICATE | --github-config-app-installation-id=GITHUB_CONFIG_APP_INSTALLATION_ID --github-config-authorizer-credential-oauth-token-secret-version=GITHUB_CONFIG_AUTHORIZER_CREDENTIAL_OAUTH_TOKEN_SECRET_VERSION | --github-enterprise-config-app-id=GITHUB_ENTERPRISE_CONFIG_APP_ID --github-enterprise-config-app-installation-id=GITHUB_ENTERPRISE_CONFIG_APP_INSTALLATION_ID --github-enterprise-config-host-uri=GITHUB_ENTERPRISE_CONFIG_HOST_URI --github-enterprise-config-service-directory=GITHUB_ENTERPRISE_CONFIG_SERVICE_DIRECTORY --github-enterprise-config-ssl-ca-certificate=GITHUB_ENTERPRISE_CONFIG_SSL_CA_CERTIFICATE --clear-github-enterprise-config-private-key-secret-version | --github-enterprise-config-private-key-secret-version=GITHUB_ENTERPRISE_CONFIG_PRIVATE_KEY_SECRET_VERSION --clear-github-enterprise-config-webhook-secret-version | --github-enterprise-config-webhook-secret-version=GITHUB_ENTERPRISE_CONFIG_WEBHOOK_SECRET_VERSION | --gitlab-config-authorizer-credential-user-token-secret-version=GITLAB_CONFIG_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION --gitlab-config-read-authorizer-credential-user-token-secret-version=GITLAB_CONFIG_READ_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION | --gitlab-enterprise-config-authorizer-credential-user-token-secret-version=GITLAB_ENTERPRISE_CONFIG_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION --gitlab-enterprise-config-host-uri=GITLAB_ENTERPRISE_CONFIG_HOST_URI --gitlab-enterprise-config-read-authorizer-credential-user-token-secret-version=GITLAB_ENTERPRISE_CONFIG_READ_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION --gitlab-enterprise-config-service-directory=GITLAB_ENTERPRISE_CONFIG_SERVICE_DIRECTORY --gitlab-enterprise-config-ssl-ca-certificate=GITLAB_ENTERPRISE_CONFIG_SSL_CA_CERTIFICATE] - [--clear-git-proxy-config --[no-]git-proxy-config-enabled] - [--crypto-key-config-reference=CRYPTO_KEY_CONFIG_REFERENCE - : --key-ring=KEY_RING] + [--bitbucket-cloud-config-authorizer-credential-user-token-secret-version=BITBUCKET_CLOUD_CONFIG_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION --bitbucket-cloud-config-read-authorizer-credential-user-token-secret-version=BITBUCKET_CLOUD_CONFIG_READ_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION --bitbucket-cloud-config-workspace=BITBUCKET_CLOUD_CONFIG_WORKSPACE --clear-bitbucket-cloud-config | --bitbucket-data-center-config-authorizer-credential-user-token-secret-version=BITBUCKET_DATA_CENTER_CONFIG_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION --bitbucket-data-center-config-host-uri=BITBUCKET_DATA_CENTER_CONFIG_HOST_URI --bitbucket-data-center-config-read-authorizer-credential-user-token-secret-version=BITBUCKET_DATA_CENTER_CONFIG_READ_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION --bitbucket-data-center-config-service-directory=BITBUCKET_DATA_CENTER_CONFIG_SERVICE_DIRECTORY --bitbucket-data-center-config-ssl-ca-certificate=BITBUCKET_DATA_CENTER_CONFIG_SSL_CA_CERTIFICATE --clear-bitbucket-data-center-config | --clear-github-config --github-config-app-installation-id=GITHUB_CONFIG_APP_INSTALLATION_ID --github-config-authorizer-credential-oauth-token-secret-version=GITHUB_CONFIG_AUTHORIZER_CREDENTIAL_OAUTH_TOKEN_SECRET_VERSION | --clear-github-enterprise-config --github-enterprise-config-app-id=GITHUB_ENTERPRISE_CONFIG_APP_ID --github-enterprise-config-app-installation-id=GITHUB_ENTERPRISE_CONFIG_APP_INSTALLATION_ID --github-enterprise-config-host-uri=GITHUB_ENTERPRISE_CONFIG_HOST_URI --github-enterprise-config-service-directory=GITHUB_ENTERPRISE_CONFIG_SERVICE_DIRECTORY --github-enterprise-config-ssl-ca-certificate=GITHUB_ENTERPRISE_CONFIG_SSL_CA_CERTIFICATE --clear-github-enterprise-config-private-key-secret-version | --github-enterprise-config-private-key-secret-version=GITHUB_ENTERPRISE_CONFIG_PRIVATE_KEY_SECRET_VERSION --clear-github-enterprise-config-webhook-secret-version | --github-enterprise-config-webhook-secret-version=GITHUB_ENTERPRISE_CONFIG_WEBHOOK_SECRET_VERSION | --clear-gitlab-config --gitlab-config-authorizer-credential-user-token-secret-version=GITLAB_CONFIG_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION --gitlab-config-read-authorizer-credential-user-token-secret-version=GITLAB_CONFIG_READ_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION | --clear-gitlab-enterprise-config --gitlab-enterprise-config-authorizer-credential-user-token-secret-version=GITLAB_ENTERPRISE_CONFIG_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION --gitlab-enterprise-config-host-uri=GITLAB_ENTERPRISE_CONFIG_HOST_URI --gitlab-enterprise-config-read-authorizer-credential-user-token-secret-version=GITLAB_ENTERPRISE_CONFIG_READ_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION --gitlab-enterprise-config-service-directory=GITLAB_ENTERPRISE_CONFIG_SERVICE_DIRECTORY --gitlab-enterprise-config-ssl-ca-certificate=GITLAB_ENTERPRISE_CONFIG_SSL_CA_CERTIFICATE] + [--clear-crypto-key-config + [--crypto-key-config-reference=CRYPTO_KEY_CONFIG_REFERENCE + : --key-ring=KEY_RING]] [--labels=[LABELS,...] | --update-labels=[UPDATE_LABELS,...] --clear-labels | --remove-labels=[__REMOVE_LABELS,...]] [GCLOUD_WIDE_FLAG ...] @@ -241,6 +241,9 @@ FLAGS The Bitbucket Cloud Workspace ID to be connected to Google Cloud Platform. + --clear-bitbucket-cloud-config + Set connection.bitbucketCloudConfig back to default value. + Configuration for connections to an instance of Bitbucket Data Center. Represents a personal access token that authorized the Connection, and @@ -348,8 +351,14 @@ FLAGS SSL certificate authority to trust when making requests to Bitbucket Data Center. + --clear-bitbucket-data-center-config + Set connection.bitbucketDataCenterConfig back to default value. + Configuration for connections to github.com. + --clear-github-config + Set connection.githubConfig back to default value. + --github-config-app-installation-id=GITHUB_CONFIG_APP_INSTALLATION_ID GitHub App installation id. @@ -386,6 +395,9 @@ FLAGS Configuration for connections to an instance of GitHub Enterprise. + --clear-github-enterprise-config + Set connection.githubEnterpriseConfig back to default value. + --github-enterprise-config-app-id=GITHUB_ENTERPRISE_CONFIG_APP_ID ID of the GitHub App created from the manifest. @@ -512,6 +524,9 @@ FLAGS Configuration for connections to gitlab.com. + --clear-gitlab-config + Set connection.gitlabConfig back to default value. + Represents a personal access token that authorized the Connection, and associated metadata. @@ -576,6 +591,9 @@ FLAGS Configuration for connections to an instance of GitLab Enterprise. + --clear-gitlab-enterprise-config + Set connection.gitlabEnterpriseConfig back to default value. + Represents a personal access token that authorized the Connection, and associated metadata. @@ -681,20 +699,12 @@ FLAGS SSL Certificate Authority certificate to use for requests to GitLab Enterprise instance. - The git proxy configuration. - - --clear-git-proxy-config - Set connection.gitProxyConfig back to default value. - - --[no-]git-proxy-config-enabled - Setting this to true allows the git proxy to be used for performing - git operations on the repositories linked in the connection. Use - --git-proxy-config-enabled to enable and - --no-git-proxy-config-enabled to disable. - The crypto key configuration. This field is used by the Customer-managed encryption keys (CMEK) feature. + --clear-crypto-key-config + Set connection.cryptoKeyConfig back to default value. + CryptoKey resource - The name of the key which is used to encrypt/decrypt customer data. For key in Cloud KMS, the key should be in the format of projects/*/locations/*/keyRings/*/cryptoKeys/*. The diff --git a/gcloud/alpha/edge-cloud/container/clusters/update b/gcloud/alpha/edge-cloud/container/clusters/update index e94835133..1b43dbf38 100644 --- a/gcloud/alpha/edge-cloud/container/clusters/update +++ b/gcloud/alpha/edge-cloud/container/clusters/update @@ -5,6 +5,7 @@ NAME SYNOPSIS gcloud alpha edge-cloud container clusters update (CLUSTER : --location=LOCATION) [--async] + [--container-default-runtime-class=CONTAINER_DEFAULT_RUNTIME_CLASS] [--offline-reboot-ttl=OFFLINE_REBOOT_TTL] [--release-channel=RELEASE_CHANNEL] [--clear-maintenance-window @@ -64,6 +65,10 @@ FLAGS Return immediately, without waiting for the operation in progress to complete. + --container-default-runtime-class=CONTAINER_DEFAULT_RUNTIME_CLASS + If set, use the specified default container runtime class for the + cluster. + --offline-reboot-ttl=OFFLINE_REBOOT_TTL Specifies the maximum duration a node can reboot offline (without connection to Google) and then rejoin its cluster to resume its diff --git a/gcloud/alpha/iap/settings/get b/gcloud/alpha/iap/settings/get index 137950159..f00048d4f 100644 --- a/gcloud/alpha/iap/settings/get +++ b/gcloud/alpha/iap/settings/get @@ -96,11 +96,11 @@ FLAGS scoped compute. Required when resource-type=cloud-run. --resource-type=RESOURCE_TYPE - Resource type of the IAP resource. --resource-type=cloud-run is private - priview feature and reach out to cloud-run team if you want to test it. - For Backend Services, you can use both compute and backend-services as - resource type. RESOURCE_TYPE must be one of: app-engine, iap_web, - compute, organization, folder, forwarding-rule, cloud-run, + Resource type of the IAP resource. For Backend Services, you can use + both compute and backend-services as resource type. + --resource-type=cloud-run is in private preview and reach out to IAP + team in case of any queries. RESOURCE_TYPE must be one of: app-engine, + iap_web, compute, organization, folder, forwarding-rule, cloud-run, backend-services. --service=SERVICE diff --git a/gcloud/alpha/iap/settings/set b/gcloud/alpha/iap/settings/set index fabc3a59c..02b829625 100644 --- a/gcloud/alpha/iap/settings/set +++ b/gcloud/alpha/iap/settings/set @@ -147,11 +147,11 @@ FLAGS scoped compute. Required when resource-type=cloud-run. --resource-type=RESOURCE_TYPE - Resource type of the IAP resource. --resource-type=cloud-run is private - priview feature and reach out to cloud-run team if you want to test it. - For Backend Services, you can use both compute and backend-services as - resource type. RESOURCE_TYPE must be one of: app-engine, iap_web, - compute, organization, folder, forwarding-rule, cloud-run, + Resource type of the IAP resource. For Backend Services, you can use + both compute and backend-services as resource type. + --resource-type=cloud-run is in private preview and reach out to IAP + team in case of any queries. RESOURCE_TYPE must be one of: app-engine, + iap_web, compute, organization, folder, forwarding-rule, cloud-run, backend-services. --service=SERVICE diff --git a/gcloud/alpha/iap/web/add-iam-policy-binding b/gcloud/alpha/iap/web/add-iam-policy-binding index 556b402e0..4be3cff6c 100644 --- a/gcloud/alpha/iap/web/add-iam-policy-binding +++ b/gcloud/alpha/iap/web/add-iam-policy-binding @@ -121,8 +121,8 @@ OPTIONAL FLAGS global backend-services. Required when resource-type=cloud-run. --resource-type=RESOURCE_TYPE - Resource type of the IAP resource. --resource-type=cloud-run is private - priview feature and reach out to cloud-run team if you want to test it. + Resource type of the IAP resource. --resource-type=cloud-run is in + private preview and reach out to IAP team in case of any queries. RESOURCE_TYPE must be one of: app-engine, backend-services, forwarding-rule, cloud-run. diff --git a/gcloud/alpha/iap/web/get-iam-policy b/gcloud/alpha/iap/web/get-iam-policy index dcd8547f6..be679c450 100644 --- a/gcloud/alpha/iap/web/get-iam-policy +++ b/gcloud/alpha/iap/web/get-iam-policy @@ -71,8 +71,8 @@ FLAGS global backend-services. Required when resource-type=cloud-run. --resource-type=RESOURCE_TYPE - Resource type of the IAP resource. --resource-type=cloud-run is private - priview feature and reach out to cloud-run team if you want to test it. + Resource type of the IAP resource. --resource-type=cloud-run is in + private preview and reach out to IAP team in case of any queries. RESOURCE_TYPE must be one of: app-engine, backend-services, forwarding-rule, cloud-run. diff --git a/gcloud/alpha/iap/web/remove-iam-policy-binding b/gcloud/alpha/iap/web/remove-iam-policy-binding index d020b9fab..75ebc6c12 100644 --- a/gcloud/alpha/iap/web/remove-iam-policy-binding +++ b/gcloud/alpha/iap/web/remove-iam-policy-binding @@ -138,8 +138,8 @@ OPTIONAL FLAGS global backend-services. Required when resource-type=cloud-run. --resource-type=RESOURCE_TYPE - Resource type of the IAP resource. --resource-type=cloud-run is private - priview feature and reach out to cloud-run team if you want to test it. + Resource type of the IAP resource. --resource-type=cloud-run is in + private preview and reach out to IAP team in case of any queries. RESOURCE_TYPE must be one of: app-engine, backend-services, forwarding-rule, cloud-run. diff --git a/gcloud/alpha/iap/web/set-iam-policy b/gcloud/alpha/iap/web/set-iam-policy index 09772f6f1..9d577d478 100644 --- a/gcloud/alpha/iap/web/set-iam-policy +++ b/gcloud/alpha/iap/web/set-iam-policy @@ -79,8 +79,8 @@ FLAGS global backend-services. Required when resource-type=cloud-run. --resource-type=RESOURCE_TYPE - Resource type of the IAP resource. --resource-type=cloud-run is private - priview feature and reach out to cloud-run team if you want to test it. + Resource type of the IAP resource. --resource-type=cloud-run is in + private preview and reach out to IAP team in case of any queries. RESOURCE_TYPE must be one of: app-engine, backend-services, forwarding-rule, cloud-run. diff --git a/gcloud/alpha/managed-kafka/help b/gcloud/alpha/managed-kafka/help index 7aa5a79e9..3c4797369 100644 --- a/gcloud/alpha/managed-kafka/help +++ b/gcloud/alpha/managed-kafka/help @@ -23,6 +23,9 @@ GROUPS consumer-groups (ALPHA) Administer Managed Service for Apache Kafka consumer groups. + operations + (ALPHA) View Managed Service for Apache Kafka operations. + topics (ALPHA) Administer Managed Service for Apache Kafka topics. diff --git a/gcloud/alpha/managed-kafka/operations/describe b/gcloud/alpha/managed-kafka/operations/describe new file mode 100644 index 000000000..6110e7920 --- /dev/null +++ b/gcloud/alpha/managed-kafka/operations/describe @@ -0,0 +1,75 @@ +NAME + gcloud alpha managed-kafka operations describe - describe a Managed Service + for Apache Kafka operation + +SYNOPSIS + gcloud alpha managed-kafka operations describe + (OPERATION : --location=LOCATION) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Describe a Managed Service for Apache Kafka operation. + +EXAMPLES + To describe an operation named myoperation located in us-central1, run the + following: + + $ gcloud alpha managed-kafka operations describe myoperation \ + --location=us-central1 + +POSITIONAL ARGUMENTS + Operation resource - Identifies the operation for details to be displayed. + 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 operation 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. + + OPERATION + ID of the operation or fully qualified identifier for the operation. + + To set the operation attribute: + ▸ provide the argument operation on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + ID of the location of the Managed Service for Apache Kafka resource. + See + https://cloud.google.com/managed-service-for-apache-kafka/docs/locations + for a list of supported locations. + + To set the location attribute: + ▸ provide the argument operation on the command line with a fully + specified name; + ▸ provide the argument --location 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 managedkafka/v1 API. The full documentation for this + API can be found at: + https://cloud.google.com/managed-service-for-apache-kafka/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. These variants are also available: + + $ gcloud managed-kafka operations describe + + $ gcloud beta managed-kafka operations describe + diff --git a/gcloud/alpha/managed-kafka/operations/help b/gcloud/alpha/managed-kafka/operations/help new file mode 100644 index 000000000..8c62306ca --- /dev/null +++ b/gcloud/alpha/managed-kafka/operations/help @@ -0,0 +1,35 @@ +NAME + gcloud alpha managed-kafka operations - view Managed Service for Apache + Kafka operations + +SYNOPSIS + gcloud alpha managed-kafka operations COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) View Managed Service for Apache Kafka operations. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + describe + (ALPHA) Describe a Managed Service for Apache Kafka operation. + + list + (ALPHA) List all Managed Service for Apache Kafka operations in a given + location. + +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 managed-kafka operations + + $ gcloud beta managed-kafka operations + diff --git a/gcloud/alpha/run/workers/list b/gcloud/alpha/managed-kafka/operations/list similarity index 52% rename from gcloud/alpha/run/workers/list rename to gcloud/alpha/managed-kafka/operations/list index 980532dbb..7a6c34b89 100644 --- a/gcloud/alpha/run/workers/list +++ b/gcloud/alpha/managed-kafka/operations/list @@ -1,23 +1,42 @@ NAME - gcloud alpha run workers list - list available workers + gcloud alpha managed-kafka operations list - list all Managed Service for + Apache Kafka operations in a given location SYNOPSIS - gcloud alpha run workers list [--region=REGION] [--filter=EXPRESSION] - [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] - [GCLOUD_WIDE_FLAG ...] + gcloud alpha managed-kafka operations list --location=LOCATION + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) List available workers. + (ALPHA) List all Managed Service for Apache Kafka operations in a given + location. To specify the maximum number of operations to list, use the + --limit flag. EXAMPLES - To list available workers: + To list all clusters in a given location, such as us-central1, run the + following: - $ gcloud alpha run workers list + $ gcloud alpha managed-kafka operations list --location=us-central1 -FLAGS - --region=REGION - Region in which the resource can be found. Alternatively, set the - property [run/region]. +REQUIRED FLAGS + Location resource - Identifies the region which contains all the + operations to be listed. 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; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + --location=LOCATION + ID of the location or fully qualified identifier for the location. + + To set the location attribute: + ▸ provide the argument --location on the command line. LIST COMMAND FLAGS --filter=EXPRESSION @@ -45,12 +64,6 @@ LIST COMMAND FLAGS 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, @@ -59,9 +72,18 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. +API REFERENCE + This command uses the managedkafka/v1 API. The full documentation for this + API can be found at: + https://cloud.google.com/managed-service-for-apache-kafka/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. + access allowlist. These variants are also available: + + $ gcloud managed-kafka operations list + + $ gcloud beta managed-kafka operations list diff --git a/gcloud/alpha/netapp/storage-pools/create b/gcloud/alpha/netapp/storage-pools/create index 27f7cdf1c..c7ed22749 100644 --- a/gcloud/alpha/netapp/storage-pools/create +++ b/gcloud/alpha/netapp/storage-pools/create @@ -8,9 +8,12 @@ SYNOPSIS --network=[name=NAME],[psa-range=PSA-RANGE] --service-level=SERVICE_LEVEL [--active-directory=ACTIVE_DIRECTORY] [--allow-auto-tiering=ALLOW_AUTO_TIERING] [--async] + [--custom-performance-enabled=CUSTOM_PERFORMANCE_ENABLED] [--description=DESCRIPTION] [--enable-ldap=ENABLE_LDAP] [--kms-config=KMS_CONFIG] [--labels=[KEY=VALUE,...]] - [--replica-zone=REPLICA_ZONE] [--zone=ZONE] [GCLOUD_WIDE_FLAG ...] + [--replica-zone=REPLICA_ZONE] [--total-iops=TOTAL_IOPS] + [--total-throughput=TOTAL_THROUGHPUT] [--zone=ZONE] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Creates a Storage Pool to contain Volumes with a specified Service @@ -145,6 +148,10 @@ OPTIONAL FLAGS Return immediately, without waiting for the operation in progress to complete. + --custom-performance-enabled=CUSTOM_PERFORMANCE_ENABLED + Boolean flag indicating whether Storage Pool is a custom performance + Storage Pool or not + --description=DESCRIPTION A description of the Cloud NetApp Storage Pool @@ -186,6 +193,13 @@ OPTIONAL FLAGS --replica-zone=REPLICA_ZONE String indicating replica zone for the Storage Pool + --total-iops=TOTAL_IOPS + Integer indicating total IOPS of the Storage Pool + + --total-throughput=TOTAL_THROUGHPUT + The total throughput of the Storage Pool in MiB/s or GiB/s units. If no + throughput unit is specified, MiB/s is assumed. + --zone=ZONE String indicating active zone of the Storage Pool diff --git a/gcloud/alpha/netapp/storage-pools/update b/gcloud/alpha/netapp/storage-pools/update index 6d1ea49f6..356daa107 100644 --- a/gcloud/alpha/netapp/storage-pools/update +++ b/gcloud/alpha/netapp/storage-pools/update @@ -8,7 +8,8 @@ SYNOPSIS [--active-directory=ACTIVE_DIRECTORY] [--allow-auto-tiering=ALLOW_AUTO_TIERING] [--async] [--capacity=CAPACITY] [--description=DESCRIPTION] - [--replica-zone=REPLICA_ZONE] [--update-labels=[KEY=VALUE,...]] + [--replica-zone=REPLICA_ZONE] [--total-iops=TOTAL_IOPS] + [--total-throughput=TOTAL_THROUGHPUT] [--update-labels=[KEY=VALUE,...]] [--zone=ZONE] [--clear-labels | --remove-labels=[KEY,...]] [GCLOUD_WIDE_FLAG ...] @@ -98,6 +99,13 @@ FLAGS --replica-zone=REPLICA_ZONE String indicating replica zone for the Storage Pool + --total-iops=TOTAL_IOPS + Integer indicating total IOPS of the Storage Pool + + --total-throughput=TOTAL_THROUGHPUT + The total throughput of the Storage Pool in MiB/s or GiB/s units. If no + throughput unit is specified, MiB/s is assumed. + --update-labels=[KEY=VALUE,...] List of label KEY=VALUE pairs to update. If a label exists, its value is modified. Otherwise, a new label is created. diff --git a/gcloud/alpha/network-services/multicast-group-ranges/create b/gcloud/alpha/network-services/multicast-group-ranges/create index a40d1282f..a2517a1af 100644 --- a/gcloud/alpha/network-services/multicast-group-ranges/create +++ b/gcloud/alpha/network-services/multicast-group-ranges/create @@ -8,9 +8,9 @@ SYNOPSIS --multicast-domain=MULTICAST_DOMAIN --reserved-internal-range=RESERVED_INTERNAL_RANGE [--async] [--consumer-accept-list=[CONSUMER_ACCEPT_LIST,...]] - [--description=DESCRIPTION] [--[no-]enable-logging] - [--labels=[KEY=VALUE,...]] [--require-explicit-accept] - [GCLOUD_WIDE_FLAG ...] + [--description=DESCRIPTION] [--distribution-scope=DISTRIBUTION_SCOPE] + [--[no-]enable-logging] [--labels=[KEY=VALUE,...]] + [--require-explicit-accept] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Create a multicast group range in the specified location of the @@ -76,6 +76,11 @@ OPTIONAL FLAGS --description=DESCRIPTION The description for the multicast group range. + --distribution-scope=DISTRIBUTION_SCOPE + Distribution scope of this multicast group range. DISTRIBUTION_SCOPE + must be one of: distribution-scope-unspecified, intra-region, + intra-zone. + --[no-]enable-logging Whether to enable logging for this multicast group range. Use --enable-logging to enable and --no-enable-logging to disable. diff --git a/gcloud/alpha/network-services/multicast-group-ranges/help b/gcloud/alpha/network-services/multicast-group-ranges/help index 09a2191f3..020b97066 100644 --- a/gcloud/alpha/network-services/multicast-group-ranges/help +++ b/gcloud/alpha/network-services/multicast-group-ranges/help @@ -29,6 +29,9 @@ COMMANDS list (ALPHA) List multicast group ranges. + update + (ALPHA) Update a multicast group range. + NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct diff --git a/gcloud/alpha/network-services/multicast-group-ranges/update b/gcloud/alpha/network-services/multicast-group-ranges/update new file mode 100644 index 000000000..608bbd841 --- /dev/null +++ b/gcloud/alpha/network-services/multicast-group-ranges/update @@ -0,0 +1,145 @@ +NAME + gcloud alpha network-services multicast-group-ranges update - update a + multicast group range + +SYNOPSIS + gcloud alpha network-services multicast-group-ranges update + (MULTICAST_GROUP_RANGE : --location=LOCATION) [--async] + [--description=DESCRIPTION] [--[no-]enable-logging] + [--[no-]require-explicit-accept] [--update-labels=[KEY=VALUE,...]] + [--clear-labels | --remove-labels=[KEY,...]] + [--consumer-accept-list=[CONSUMER_ACCEPT_LIST,...] + | --add-consumer-accept-list=[ADD_CONSUMER_ACCEPT_LIST,...] + --clear-consumer-accept-list + | --remove-consumer-accept-list=[REMOVE_CONSUMER_ACCEPT_LIST,...]] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Update a multicast group range in the specified location of the + current project. + +EXAMPLES + Update a multicast group range with the name 'my-multicast-group-range' and + location 'global'. + + $ gcloud alpha network-services multicast-group-ranges update \ + my-multicast-group-range --require-explicit-accept \ + --enable-logging --location=global + +POSITIONAL ARGUMENTS + Multicast group range resource - Name of the multicast group range to be + updated. The arguments in this group can be used to specify the attributes + of this resource. (NOTE) Some attributes are not given arguments in this + group but can be set in other ways. + + To set the project attribute: + ◆ provide the argument multicast_group_range 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. + + MULTICAST_GROUP_RANGE + ID of the multicast group range or fully qualified identifier for the + multicast group range. + + To set the multicast_group_range attribute: + ▸ provide the argument multicast_group_range 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 Id. + + To set the location attribute: + ▸ provide the argument multicast_group_range on the command line + with a fully specified name; + ▸ provide the argument --location on the command line. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --description=DESCRIPTION + The description for the multicast group range. + + --[no-]enable-logging + Whether to enable logging for this multicast group range. Use + --enable-logging to enable and --no-enable-logging to disable. + + --[no-]require-explicit-accept + Whether an empty consumer accept list will reject all consumer + projects. Use --require-explicit-accept to enable and + --no-require-explicit-accept to disable. + + --update-labels=[KEY=VALUE,...] + List of label KEY=VALUE pairs to update. If a label exists, its value + is modified. Otherwise, a new label is created. + + Keys must start with a lowercase character and contain only hyphens + (-), underscores (_), lowercase characters, and numbers. Values must + contain only hyphens (-), underscores (_), lowercase characters, and + numbers. + + At most one of these can be specified: + + --clear-labels + Remove all labels. If --update-labels is also specified then + --clear-labels is applied first. + + For example, to remove all labels: + + $ gcloud alpha network-services multicast-group-ranges update \ + --clear-labels + + To remove all existing labels and create two new labels, foo and baz: + + $ gcloud alpha network-services multicast-group-ranges update \ + --clear-labels --update-labels foo=bar,baz=qux + + --remove-labels=[KEY,...] + List of label keys to remove. If a label does not exist it is + silently ignored. If --update-labels is also specified then + --update-labels is applied first. + + Update consumer_accept_list. + + At most one of these can be specified: + + --consumer-accept-list=[CONSUMER_ACCEPT_LIST,...] + Set consumer_accept_list to new value. + + --add-consumer-accept-list=[ADD_CONSUMER_ACCEPT_LIST,...] + Add new value to consumer_accept_list list. + + At most one of these can be specified: + + --clear-consumer-accept-list + Clear consumer_accept_list value and set to empty list. + + --remove-consumer-accept-list=[REMOVE_CONSUMER_ACCEPT_LIST,...] + Remove existing value from consumer_accept_list list. + +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 networkservices/v1alpha1 API. The full documentation + for this API can be found at: https://cloud.google.com/networking + +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 network-services multicast-group-ranges update + diff --git a/gcloud/alpha/pubsub/message-transforms/help b/gcloud/alpha/pubsub/message-transforms/help index b0742708c..0df315b6d 100644 --- a/gcloud/alpha/pubsub/message-transforms/help +++ b/gcloud/alpha/pubsub/message-transforms/help @@ -17,7 +17,7 @@ COMMANDS COMMAND is one of the following: test - (ALPHA) Tests messages transforms against a given message. + (ALPHA) Tests message transforms against a given message. validate (ALPHA) Validates a message transform. diff --git a/gcloud/alpha/pubsub/message-transforms/test b/gcloud/alpha/pubsub/message-transforms/test index 71a8fcb91..e16d62162 100644 --- a/gcloud/alpha/pubsub/message-transforms/test +++ b/gcloud/alpha/pubsub/message-transforms/test @@ -1,5 +1,5 @@ NAME - gcloud alpha pubsub message-transforms test - tests messages transforms + gcloud alpha pubsub message-transforms test - tests message transforms against a given message SYNOPSIS @@ -11,7 +11,7 @@ SYNOPSIS [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) Tests messages transforms against a given message. + (ALPHA) Tests message transforms against a given message. REQUIRED FLAGS Message to test the message transforms against. diff --git a/gcloud/alpha/run/deploy b/gcloud/alpha/run/deploy index 27ea9e669..58d7126ff 100644 --- a/gcloud/alpha/run/deploy +++ b/gcloud/alpha/run/deploy @@ -145,6 +145,9 @@ FLAGS Specifies a container by name. Flags following --container will apply to the specified container. + Flags that are not container-specific must be specified before + --container. + --[no-]cpu-boost Whether to allocate extra CPU to containers on startup to reduce the perceived latency of a cold start request. Enabled by default when @@ -425,8 +428,9 @@ FLAGS Container Flags - The following flags apply to a single container. If the --container flag is specified these flags may only be - specified after a --container flag. Otherwise they will apply to the primary ingress container. + The following flags apply to a single container. If the --container flag is + specified these flags may only be specified after a --container flag. + Otherwise they will apply to the primary ingress container. --add-volume-mount=[volume=NAME,mount-path=MOUNT_PATH,...] Adds a mount to the current container. Must contain the keys diff --git a/gcloud/alpha/run/help b/gcloud/alpha/run/help index 020c74262..dd09775ba 100644 --- a/gcloud/alpha/run/help +++ b/gcloud/alpha/run/help @@ -44,9 +44,6 @@ GROUPS worker-pools (ALPHA) View and manage your Cloud Run worker pools. - workers - (ALPHA) View and manage your Cloud Run workers. - COMMANDS COMMAND is one of the following: diff --git a/gcloud/alpha/run/jobs/create b/gcloud/alpha/run/jobs/create index 25696ec08..5ebf48107 100644 --- a/gcloud/alpha/run/jobs/create +++ b/gcloud/alpha/run/jobs/create @@ -77,6 +77,9 @@ FLAGS Specifies a container by name. Flags following --container will apply to the specified container. + Flags that are not container-specific must be specified before + --container. + --gpu-type=GPU_TYPE The GPU type to use. diff --git a/gcloud/alpha/run/jobs/deploy b/gcloud/alpha/run/jobs/deploy index d20ae078c..8ec9237bd 100644 --- a/gcloud/alpha/run/jobs/deploy +++ b/gcloud/alpha/run/jobs/deploy @@ -78,6 +78,9 @@ FLAGS Specifies a container by name. Flags following --container will apply to the specified container. + Flags that are not container-specific must be specified before + --container. + --gpu-type=GPU_TYPE The GPU type to use. diff --git a/gcloud/alpha/run/jobs/execute b/gcloud/alpha/run/jobs/execute index c448a50f2..95e99719d 100644 --- a/gcloud/alpha/run/jobs/execute +++ b/gcloud/alpha/run/jobs/execute @@ -40,6 +40,9 @@ FLAGS Specifies a container by name. Flags following --container will apply to the specified container. + Flags that are not container-specific must be specified before + --container. + --region=REGION Region in which the resource can be found. Alternatively, set the property [run/region]. diff --git a/gcloud/alpha/run/jobs/update b/gcloud/alpha/run/jobs/update index 908f89878..f5a16fe13 100644 --- a/gcloud/alpha/run/jobs/update +++ b/gcloud/alpha/run/jobs/update @@ -77,6 +77,9 @@ FLAGS Specifies a container by name. Flags following --container will apply to the specified container. + Flags that are not container-specific must be specified before + --container. + --gpu-type=GPU_TYPE The GPU type to use. diff --git a/gcloud/alpha/run/multi-region-services/update b/gcloud/alpha/run/multi-region-services/update index 783417b6d..c45d03e1a 100644 --- a/gcloud/alpha/run/multi-region-services/update +++ b/gcloud/alpha/run/multi-region-services/update @@ -116,6 +116,9 @@ FLAGS Specifies a container by name. Flags following --container will apply to the specified container. + Flags that are not container-specific must be specified before + --container. + --[no-]cpu-boost Whether to allocate extra CPU to containers on startup to reduce the perceived latency of a cold start request. Enabled by default when diff --git a/gcloud/alpha/run/services/update b/gcloud/alpha/run/services/update index 87a79f4b4..079719d1d 100644 --- a/gcloud/alpha/run/services/update +++ b/gcloud/alpha/run/services/update @@ -116,6 +116,9 @@ FLAGS Specifies a container by name. Flags following --container will apply to the specified container. + Flags that are not container-specific must be specified before + --container. + --[no-]cpu-boost Whether to allocate extra CPU to containers on startup to reduce the perceived latency of a cold start request. Enabled by default when diff --git a/gcloud/alpha/run/worker-pools/deploy b/gcloud/alpha/run/worker-pools/deploy index d32b221e6..cba505e44 100644 --- a/gcloud/alpha/run/worker-pools/deploy +++ b/gcloud/alpha/run/worker-pools/deploy @@ -103,6 +103,9 @@ FLAGS Specifies a container by name. Flags following --container will apply to the specified container. + Flags that are not container-specific must be specified before + --container. + --description=DESCRIPTION Provides an optional, human-readable description of the service. diff --git a/gcloud/alpha/run/worker-pools/update b/gcloud/alpha/run/worker-pools/update index cd1082f2c..c8c6c772d 100644 --- a/gcloud/alpha/run/worker-pools/update +++ b/gcloud/alpha/run/worker-pools/update @@ -103,6 +103,9 @@ FLAGS Specifies a container by name. Flags following --container will apply to the specified container. + Flags that are not container-specific must be specified before + --container. + --description=DESCRIPTION Provides an optional, human-readable description of the service. diff --git a/gcloud/alpha/run/workers/delete b/gcloud/alpha/run/workers/delete deleted file mode 100644 index b7a2f84d3..000000000 --- a/gcloud/alpha/run/workers/delete +++ /dev/null @@ -1,58 +0,0 @@ -NAME - gcloud alpha run workers delete - delete a worker - -SYNOPSIS - gcloud alpha run workers delete WORKER [--[no-]async] [--region=REGION] - [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (ALPHA) Delete a worker. - -EXAMPLES - To delete a worker: - - $ gcloud alpha run workers delete - -POSITIONAL ARGUMENTS - Worker resource - Worker to delete. This represents a Cloud resource. - (NOTE) Some attributes are not given arguments in this group but can be - set in other ways. - - To set the project attribute: - ◆ provide the argument WORKER 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. - - WORKER - ID of the worker or fully qualified identifier for the worker. - - To set the worker attribute: - ▸ provide the argument WORKER on the command line. - -FLAGS - --[no-]async - Return immediately, without waiting for the operation in progress to - complete. Defaults to --no-async. Use --async to enable and --no-async - to disable. - - --region=REGION - Region in which the resource can be found. Alternatively, set the - property [run/region]. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --configuration, --flags-file, --flatten, --format, - --help, --impersonate-service-account, --log-http, --project, --quiet, - --trace-token, --user-output-enabled, --verbosity. - - Run $ gcloud help for details. - -NOTES - This command is currently in alpha and might change without notice. If this - command fails with API permission errors despite specifying the correct - project, you might be trying to access an API with an invitation-only early - access allowlist. - diff --git a/gcloud/alpha/run/workers/deploy b/gcloud/alpha/run/workers/deploy deleted file mode 100644 index e9a920628..000000000 --- a/gcloud/alpha/run/workers/deploy +++ /dev/null @@ -1,483 +0,0 @@ -NAME - gcloud alpha run workers deploy - create or update a Cloud Run worker - -SYNOPSIS - gcloud alpha run workers deploy [WORKER] [--async] - [--breakglass=JUSTIFICATION] [--description=DESCRIPTION] - [--max-instances=MAX_INSTANCES] [--max-surge=MAX_SURGE] - [--max-unavailable=MAX_UNAVAILABLE] [--mesh=MESH] - [--min-instances=MIN_INSTANCES] [--no-promote] [--region=REGION] - [--revision-suffix=REVISION_SUFFIX] [--scaling=SCALING] - [--service-account=SERVICE_ACCOUNT] [--vpc-egress=VPC_EGRESS] - [--add-cloudsql-instances=[CLOUDSQL-INSTANCES,...] - | --clear-cloudsql-instances - | --remove-cloudsql-instances=[CLOUDSQL-INSTANCES,...] - | --set-cloudsql-instances=[CLOUDSQL-INSTANCES,...]] - [--add-volume=[KEY=VALUE,...] - --clear-volumes --remove-volume=[VOLUME,...]] - [--add-volume-mount=[volume=NAME,mount-path=MOUNT_PATH,...] - --args=[ARG,...] --clear-volume-mounts --command=[COMMAND,...] - --cpu=CPU --memory=MEMORY - --remove-volume-mount=[MOUNT_PATH,...] --clear-env-vars - | --env-vars-file=FILE_PATH | --set-env-vars=[KEY=VALUE,...] - | --remove-env-vars=[KEY,...] - --update-env-vars=[KEY=VALUE,...] --clear-secrets - | --set-secrets=[KEY=VALUE,...] | --remove-secrets=[KEY,...] - --update-secrets=[KEY=VALUE,...] --image=IMAGE | --source=SOURCE] - [--binary-authorization=POLICY | --clear-binary-authorization] - [--clear-encryption-key-shutdown-hours - | --encryption-key-shutdown-hours=ENCRYPTION_KEY_SHUTDOWN_HOURS] - [--clear-key | --key=KEY] - [--clear-labels | --remove-labels=[KEY,...] --labels=[KEY=VALUE,...] - | --update-labels=[KEY=VALUE,...]] - [--clear-network - | --network=NETWORK --subnet=SUBNET --clear-network-tags - | --network-tags=[TAG,...]] - [--clear-post-key-revocation-action-type - | --post-key-revocation-action-type=POST_KEY_REVOCATION_ACTION_TYPE] - [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (ALPHA) Creates or updates a Cloud Run worker. - -EXAMPLES - To deploy a container to the worker my-backend on Cloud Run: - - $ gcloud alpha run workers deploy my-backend \ - --image=us-docker.pkg.dev/project/image - - You may also omit the worker name. Then a prompt will be displayed with a - suggested default value: - - $ gcloud alpha run workers deploy \ - --image=us-docker.pkg.dev/project/image - -POSITIONAL ARGUMENTS - Worker resource - Worker to deploy to. 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 WORKER on the command line with a fully - specified name; - ◆ specify the worker name from an interactive prompt with a fully - specified name; - ◆ provide the argument --project on the command line; - ◆ set the property core/project. - - [WORKER] - ID of the worker or fully qualified identifier for the worker. - - To set the worker attribute: - ▸ provide the argument WORKER on the command line; - ▸ specify the worker name from an interactive prompt. - -FLAGS - --async - Return immediately, without waiting for the operation in progress to - complete. - - --breakglass=JUSTIFICATION - Justification to bypass Binary Authorization policy constraints and - allow the operation. See - https://cloud.google.com/binary-authorization/docs/using-breakglass for - more information. Next update or deploy command will automatically - clear existing breakglass justification. - - --description=DESCRIPTION - Provides an optional, human-readable description of the service. - - --max-instances=MAX_INSTANCES - The maximum number of container instances for this Revision to run or - 'default' to remove. This setting is immutably set on each new Revision - and modifying its value will deploy another Revision. Consider using - --max to set the maximum number of instances across all revisions of - the Worker which may be modified dynamically. - - --max-surge=MAX_SURGE - A maximum percentage of instances that will be moved in each step of - instance split changes. Use "default" to unset the limit and use the - platform default. - - --max-unavailable=MAX_UNAVAILABLE - A maximum percentage of instances that may be unavailable during - instance split changes. Use "default" to unset the limit and use the - platform default. - - --mesh=MESH - Enables Cloud Service Mesh using the specified mesh resource name. Mesh - resource name must be in the format of - projects/PROJECT/locations/global/meshes/MESH_NAME or MESH_NAME. Will - default to the current project if only MESH_NAME is provided. - - --min-instances=MIN_INSTANCES - The minimum number of container instances to run for this Revision or - 'default' to remove. This setting is immutably set on each new Revision - and modifying its value will deploy a another Revision. Consider using - --min to set the minimum number of instances across all revisions of - the Worker which may be modified dynamically. - - --no-promote - True to avoid assign instances to the worker revision being deployed. - Setting this flag assigns any instances assigned to the LATEST revision - to the specific revision bound to LATEST before the deployment. The - effect is that the revision being deployed will not receive instance - split. - - After a deployment with this flag the LATEST revision will not receive - instances on future deployments. To restore assinging instances to the - LATEST revision by default, run the gcloud run workers - update-instance-split command with --to-latest. - - --region=REGION - Region in which the resource can be found. Alternatively, set the - property [run/region]. - - --revision-suffix=REVISION_SUFFIX - Specify the suffix of the revision name. Revision names always start - with the service name automatically. For example, specifying - [--revision-suffix=v1] for a service named 'helloworld', would lead to - a revision named 'helloworld-v1'. Set empty string to clear the suffix - and resume server-assigned naming. - - --scaling=SCALING - The scaling mode to use for this resource. Flag value could be either - "auto" for automatic scaling, or a positive integer to configure manual - scaling with the given integer as a fixed instance count. - - --service-account=SERVICE_ACCOUNT - the email address of an IAM service account associated with the - revision of the service. The service account represents the identity of - the running revision, and determines what permissions the revision has. - - --vpc-egress=VPC_EGRESS - Specify which of the outbound traffic to send through Direct VPC egress - or the VPC connector for this resource. This resource must have Direct - VPC egress enabled or a VPC connector to set this flag. VPC_EGRESS must - be one of: - - all - (DEPRECATED) Sends all outbound traffic through Direct VPC egress - or the VPC connector. Provides the same functionality as - 'all-traffic'. Prefer to use 'all-traffic' instead. - all-traffic - Sends all outbound traffic through Direct VPC egress or the VPC - connector. - private-ranges-only - Default option. Sends outbound traffic to private IP addresses (RFC - 1918 and Private Google Access IPs) through Direct VPC egress or - the VPC connector. - - Traffic to other Cloud Run services might require additional - configuration. See - https://cloud.google.com/run/docs/securing/private-networking#send_requests_to_other_services_and_services - for more information. - - These flags modify the Cloud SQL instances this Service connects to. You - can specify a name of a Cloud SQL instance if it's in the same project and - region as your Cloud Run service; otherwise specify - :: for the instance. - - At most one of these can be specified: - - --add-cloudsql-instances=[CLOUDSQL-INSTANCES,...] - Append the given values to the current Cloud SQL instances. - - --clear-cloudsql-instances - Empty the current Cloud SQL instances. - - --remove-cloudsql-instances=[CLOUDSQL-INSTANCES,...] - Remove the given values from the current Cloud SQL instances. - - --set-cloudsql-instances=[CLOUDSQL-INSTANCES,...] - Completely replace the current Cloud SQL instances with the given - values. - - --add-volume=[KEY=VALUE,...] - Adds a volume to the Cloud Run resource. To add more than one volume, - specify this flag multiple times. Volumes must have a name and type - key. Only certain values are supported for type. Depending on the - provided type, other keys will be required. The following types are - supported with the specified additional keys: - - cloud-storage: A volume representing a Cloud Storage bucket. This - volume type is mounted using Cloud Storage FUSE. See - https://cloud.google.com/storage/docs/gcs-fuse for the details and - limitations of this filesystem. Additional keys: - ◆ readonly: (optional) A boolean. If true, this volume will be - read-only from all mounts. - ◆ mount-options: (optional) A list of flags to pass to GCSFuse. Flags - should be specified without leading dashes and separated by - semicolons. - ◆ bucket: (optional) the name of the bucket to use as the source of - this volume. - ◆ dynamic-mounting: (optional) A boolean. If true, the volume will be - mounted dynamically. Note: You will either need to specify a bucket - or set dynamic-mounting to true, but not both. - - in-memory: An ephemeral volume that stores data in the instance's - memory. With this type of volume, data is not shared between instances - and all data will be lost when the instance it is on is terminated. - Additional keys: - ◆ size-limit: (optional) A quantity representing the maximum amount - of memory allocated to this volume, such as "512Mi" or "3G". Data - stored in an in-memory volume consumes the memory allocation of the - container that wrote the data. If size-limit is not specified, the - maximum size will be half the total memory limit of all containers. - - nfs: Represents a volume backed by an NFS server. Additional keys: - ◆ location: (required) The location of the NFS Server, in the form - SERVER:/PATH - ◆ readonly: (optional) A boolean. If true, this volume will be - read-only from all mounts. - - secret: Represents a secret stored in Secret Manager as a volume. - Additional keys: - ◆ secret: (required) The name of the secret in Secret Manager. Must - be a secret in the same project being deployed or be an alias mapped - in the run.googleapis.com/secrets annotation. - ◆ version: (required) The version of the secret to make available in - the volume. - ◆ path: (required) The relative path within the volume to mount that - version. - - --clear-volumes - Remove all existing volumes from the Cloud Run resource, including - volumes mounted as secrets - - --remove-volume=[VOLUME,...] - Removes volumes from the Cloud Run resource. - - Container Flags - - The following flags apply to the container. - - --add-volume-mount=[volume=NAME,mount-path=MOUNT_PATH,...] - Adds a mount to the current container. Must contain the keys - volume=NAME and mount-path=/PATH where NAME is the name of a volume - on this resource and PATH is the path within the container's - filesystem to mount this volume. - - --args=[ARG,...] - Comma-separated arguments passed to the command run by the - container image. If not specified and no '--command' is provided, - the container image's default Cmd is used. Otherwise, if not - specified, no arguments are passed. To reset this field to its - default, pass an empty string. - - --clear-volume-mounts - Remove all existing mounts from the current container. - - --command=[COMMAND,...] - Entrypoint for the container image. If not specified, the container - image's default Entrypoint is run. To reset this field to its - default, pass an empty string. - - --cpu=CPU - Set a CPU limit in Kubernetes cpu units. - - Cloud Run supports values fractional values below 1, 1, 2, 4, and - 8. Some CPU values requires a minimum Memory --memory value. - - --memory=MEMORY - Set a memory limit. Ex: 1024Mi, 4Gi. - - --remove-volume-mount=[MOUNT_PATH,...] - Removes the volume mounted at the specified path from the current - container. - - At most one of these can be specified: - - --clear-env-vars - Remove all environment variables. - - --env-vars-file=FILE_PATH - Path to a local YAML file with definitions for all environment - variables. All existing environment variables will be removed - before the new environment variables are added. Example YAML - content: - - KEY_1: "value1" - KEY_2: "value 2" - - --set-env-vars=[KEY=VALUE,...] - List of key-value pairs to set as environment variables. All - existing environment variables will be removed first. - - Only --update-env-vars and --remove-env-vars can be used together. - If both are specified, --remove-env-vars will be applied first. - - --remove-env-vars=[KEY,...] - List of environment variables to be removed. - - --update-env-vars=[KEY=VALUE,...] - List of key-value pairs to set as environment variables. - - Specify secrets to mount or provide as environment variables. Keys - starting with a forward slash '/' are mount paths. All other keys - correspond to environment variables. Values should be in the form - SECRET_NAME:SECRET_VERSION. For example: - '--update-secrets=/secrets/api/key=mysecret:latest,ENV=othersecret:1' - will mount a volume at '/secrets/api' containing a file 'key' with the - latest version of secret 'mysecret'. An environment variable named ENV - will also be created whose value is version 1 of secret 'othersecret'. - - At most one of these can be specified: - - --clear-secrets - Remove all secrets. - - --set-secrets=[KEY=VALUE,...] - List of key-value pairs to set as secrets. All existing secrets - will be removed first. - - Only --update-secrets and --remove-secrets can be used together. If - both are specified, --remove-secrets will be applied first. - - --remove-secrets=[KEY,...] - List of secrets to be removed. - - --update-secrets=[KEY=VALUE,...] - List of key-value pairs to set as secrets. - - At most one of these can be specified: - - --image=IMAGE - Name of the container image to deploy (e.g. - us-docker.pkg.dev/cloudrun/container/hello:latest). - - --source=SOURCE - The location of the source to build. If a Dockerfile is present - in the source code directory, it will be built using that - Dockerfile, otherwise it will use Google Cloud buildpacks. See - https://cloud.google.com/run/docs/deploying-source-code for more - details. The location can be a directory on a local disk or a - gzipped archive file (.tar.gz) in Google Cloud Storage. If the - source is a local directory, this command skips the files - specified in the --ignore-file. If --ignore-file is not - specified, use .gcloudignore file. If a .gcloudignore file is - absent and a .gitignore file is present in the local source - directory, gcloud will use a generated Git-compatible - .gcloudignore file that respects your .gitignored files. The - global .gitignore is not respected. For more information on - .gcloudignore, see gcloud topic gcloudignore. - - At most one of these can be specified: - - --binary-authorization=POLICY - Binary Authorization policy to check against. This must be set to - "default". - - --clear-binary-authorization - Remove any previously set Binary Authorization policy. - - At most one of these can be specified: - - --clear-encryption-key-shutdown-hours - Remove any previously set CMEK key shutdown hours setting. - - --encryption-key-shutdown-hours=ENCRYPTION_KEY_SHUTDOWN_HOURS - The number of hours to wait before an automatic shutdown server after - CMEK key revocation is detected. - - At most one of these can be specified: - - --clear-key - Remove any previously set CMEK key reference. - - --key=KEY - CMEK key reference to encrypt the container with. - - At most one of these can be specified: - - --clear-labels - Remove all labels. If --update-labels is also specified then - --clear-labels is applied first. - - For example, to remove all labels: - - $ gcloud alpha run workers deploy --clear-labels - - To remove all existing labels and create two new labels, foo and baz: - - $ gcloud alpha run workers deploy --clear-labels \ - --update-labels foo=bar,baz=qux - - --remove-labels=[KEY,...] - List of label keys to remove. If a label does not exist it is - silently ignored. If --update-labels is also specified then - --update-labels is applied first. - - At most one of these can be specified: - - --labels=[KEY=VALUE,...] - List of label KEY=VALUE pairs to add. - - An alias to --update-labels. - - --update-labels=[KEY=VALUE,...] - List of label KEY=VALUE pairs to update. If a label exists, its value - is modified. Otherwise, a new label is created. - - At most one of these can be specified: - - --clear-network - Disconnect this Cloud Run worker from the VPC network it is connected - to. - - Direct VPC egress setting flags group. - - --network=NETWORK - The VPC network that the Cloud Run worker will be able to send - traffic to. If --subnet is also specified, subnet must be a - subnetwork of the network specified by this --network flag. To - clear existing VPC network settings, use --clear-network. - - --subnet=SUBNET - The VPC subnetwork that the Cloud Run worker will get IPs from. The - subnetwork must be /26 or larger. If --network is also specified, - subnet must be a subnetwork of the network specified by the - --network flag. If --network is not specified, network will be - looked up from this subnetwork. To clear existing VPC network - settings, use --clear-network. - - At most one of these can be specified: - - --clear-network-tags - Clears all existing Compute Engine tags from the Cloud Run - worker. - - --network-tags=[TAG,...] - Applies the given Compute Engine tags (comma separated) to the - Cloud Run worker. To clear existing tags, use - --clear-network-tags. - - At most one of these can be specified: - - --clear-post-key-revocation-action-type - Remove any previously set post CMEK key revocation action type. - - --post-key-revocation-action-type=POST_KEY_REVOCATION_ACTION_TYPE - Action type after CMEK key revocation. - POST_KEY_REVOCATION_ACTION_TYPE must be one of: - - prevent-new - No new instances will be started after CMEK key revocation. - shut-down - No new instances will be started and the existing instances will - be shut down after CMEK key revocation. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --configuration, --flags-file, --flatten, --format, - --help, --impersonate-service-account, --log-http, --project, --quiet, - --trace-token, --user-output-enabled, --verbosity. - - Run $ gcloud help for details. - -NOTES - This command is currently in alpha and might change without notice. If this - command fails with API permission errors despite specifying the correct - project, you might be trying to access an API with an invitation-only early - access allowlist. - diff --git a/gcloud/alpha/run/workers/describe b/gcloud/alpha/run/workers/describe deleted file mode 100644 index 0663ac2f2..000000000 --- a/gcloud/alpha/run/workers/describe +++ /dev/null @@ -1,62 +0,0 @@ -NAME - gcloud alpha run workers describe - obtain details about a given worker - -SYNOPSIS - gcloud alpha run workers describe WORKER [--region=REGION] - [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (ALPHA) Obtain details about a given worker. - -EXAMPLES - To obtain details about a given worker: - - $ gcloud alpha run workers describe - - To get those details in the YAML format: - - $ gcloud alpha run workers describe --format=yaml - - To get them in YAML format suited to export (omitting metadata specific to - this deployment and status info): - - $ gcloud alpha run workers describe --format=export - -POSITIONAL ARGUMENTS - Worker resource - Worker to describe. This represents a Cloud resource. - (NOTE) Some attributes are not given arguments in this group but can be - set in other ways. - - To set the project attribute: - ◆ provide the argument WORKER 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. - - WORKER - ID of the worker or fully qualified identifier for the worker. - - To set the worker attribute: - ▸ provide the argument WORKER on the command line. - -FLAGS - --region=REGION - Region in which the resource can be found. Alternatively, set the - property [run/region]. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --configuration, --flags-file, --flatten, --format, - --help, --impersonate-service-account, --log-http, --project, --quiet, - --trace-token, --user-output-enabled, --verbosity. - - Run $ gcloud help for details. - -NOTES - This command is currently in alpha and might change without notice. If this - command fails with API permission errors despite specifying the correct - project, you might be trying to access an API with an invitation-only early - access allowlist. - diff --git a/gcloud/alpha/run/workers/help b/gcloud/alpha/run/workers/help deleted file mode 100644 index d8d897913..000000000 --- a/gcloud/alpha/run/workers/help +++ /dev/null @@ -1,60 +0,0 @@ -NAME - gcloud alpha run workers - view and manage your Cloud Run workers - -SYNOPSIS - gcloud alpha run workers GROUP | COMMAND [--region=REGION] - [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (ALPHA) This set of commands can be used to view and manage your Cloud Run - workers. - -EXAMPLES - To list your existing workers, run: - - $ gcloud alpha run workers list - -FLAGS - --region=REGION - Region in which the resource can be found. Alternatively, set the - property [run/region]. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --help. - - Run $ gcloud help for details. - -GROUPS - GROUP is one of the following: - - revisions - (ALPHA) View and manage your Cloud Run Workers revisions. - -COMMANDS - COMMAND is one of the following: - - delete - (ALPHA) Delete a worker. - - deploy - (ALPHA) Create or update a Cloud Run worker. - - describe - (ALPHA) Obtain details about a given worker. - - list - (ALPHA) List available workers. - - update - (ALPHA) Update Cloud Run environment variables and other configuration - settings. - - update-instance-split - (ALPHA) Adjust the instance assignments for a Cloud Run worker. - -NOTES - This command is currently in alpha and might change without notice. If this - command fails with API permission errors despite specifying the correct - project, you might be trying to access an API with an invitation-only early - access allowlist. - diff --git a/gcloud/alpha/run/workers/revisions/delete b/gcloud/alpha/run/workers/revisions/delete deleted file mode 100644 index 83c004d9b..000000000 --- a/gcloud/alpha/run/workers/revisions/delete +++ /dev/null @@ -1,68 +0,0 @@ -NAME - gcloud alpha run workers revisions delete - delete a worker revision - -SYNOPSIS - gcloud alpha run workers revisions delete - (REVISION : --namespace=NAMESPACE) [--async] [--region=REGION] - [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (ALPHA) Delete a worker revision. - -EXAMPLES - To delete a revision: - - $ gcloud alpha run workers revisions delete - -POSITIONAL ARGUMENTS - Revision resource - Worker revision to delete. The arguments in this group - can be used to specify the attributes of this resource. - - This must be specified. - - REVISION - ID of the revision or fully qualified identifier for the revision. - - To set the revision attribute: - ▸ provide the argument REVISION on the command line. - - This positional argument must be specified if any of the other - arguments in this group are specified. - - --namespace=NAMESPACE - Specific to Cloud Run for Anthos: Kubernetes namespace for the - revision. - - To set the namespace attribute: - ▸ provide the argument REVISION on the command line with a fully - specified name; - ▸ provide the argument --namespace on the command line; - ▸ set the property run/namespace; - ▸ For Cloud Run on Kubernetes Engine, defaults to "default". - Otherwise, defaults to project ID.; - ▸ provide the argument project on the command line; - ▸ set the property core/project. - -FLAGS - --async - Return immediately, without waiting for the operation in progress to - complete. - - --region=REGION - Region in which the resource can be found. Alternatively, set the - property [run/region]. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --configuration, --flags-file, --flatten, --format, - --help, --impersonate-service-account, --log-http, --project, --quiet, - --trace-token, --user-output-enabled, --verbosity. - - Run $ gcloud help for details. - -NOTES - This command is currently in alpha and might change without notice. If this - command fails with API permission errors despite specifying the correct - project, you might be trying to access an API with an invitation-only early - access allowlist. - diff --git a/gcloud/alpha/run/workers/revisions/describe b/gcloud/alpha/run/workers/revisions/describe deleted file mode 100644 index f4d306a9a..000000000 --- a/gcloud/alpha/run/workers/revisions/describe +++ /dev/null @@ -1,66 +0,0 @@ -NAME - gcloud alpha run workers revisions describe - obtain details about worker - revisions - -SYNOPSIS - gcloud alpha run workers revisions describe - (REVISION : --namespace=NAMESPACE) [--region=REGION] - [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (ALPHA) Obtain details about worker revisions. - -EXAMPLES - To describe a worker revision rev.1 in us-central1: - - $ gcloud alpha run workers revisions describe rev.1 \ - --region=us-central1 - -POSITIONAL ARGUMENTS - Revision resource - Worker revision to describe. The arguments in this - group can be used to specify the attributes of this resource. - - This must be specified. - - REVISION - ID of the revision or fully qualified identifier for the revision. - - To set the revision attribute: - ▸ provide the argument REVISION on the command line. - - This positional argument must be specified if any of the other - arguments in this group are specified. - - --namespace=NAMESPACE - Specific to Cloud Run for Anthos: Kubernetes namespace for the - revision. - - To set the namespace attribute: - ▸ provide the argument REVISION on the command line with a fully - specified name; - ▸ provide the argument --namespace on the command line; - ▸ set the property run/namespace; - ▸ For Cloud Run on Kubernetes Engine, defaults to "default". - Otherwise, defaults to project ID.; - ▸ provide the argument project on the command line; - ▸ set the property core/project. - -FLAGS - --region=REGION - Region in which the resource can be found. Alternatively, set the - property [run/region]. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --configuration, --flags-file, --flatten, --format, - --help, --impersonate-service-account, --log-http, --project, --quiet, - --trace-token, --user-output-enabled, --verbosity. - - Run $ gcloud help for details. - -NOTES - This command is currently in alpha and might change without notice. If this - command fails with API permission errors despite specifying the correct - project, you might be trying to access an API with an invitation-only early - access allowlist. - diff --git a/gcloud/alpha/run/workers/revisions/help b/gcloud/alpha/run/workers/revisions/help deleted file mode 100644 index 310e4d44b..000000000 --- a/gcloud/alpha/run/workers/revisions/help +++ /dev/null @@ -1,45 +0,0 @@ -NAME - gcloud alpha run workers revisions - view and manage your Cloud Run Workers - revisions - -SYNOPSIS - gcloud alpha run workers revisions COMMAND [--region=REGION] - [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (ALPHA) This set of commands can be used to view and manage your existing - Cloud Run Workers revisions. - -EXAMPLES - To list your existing worker revisions, run: - - $ gcloud alpha run workers revisions list - -FLAGS - --region=REGION - Region in which the resource can be found. Alternatively, set the - property [run/region]. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --help. - - Run $ gcloud help for details. - -COMMANDS - COMMAND is one of the following: - - delete - (ALPHA) Delete a worker revision. - - describe - (ALPHA) Obtain details about worker revisions. - - list - (ALPHA) List available worker revisions. - -NOTES - This command is currently in alpha and might change without notice. If this - command fails with API permission errors despite specifying the correct - project, you might be trying to access an API with an invitation-only early - access allowlist. - diff --git a/gcloud/alpha/run/workers/update b/gcloud/alpha/run/workers/update deleted file mode 100644 index f695bbcb0..000000000 --- a/gcloud/alpha/run/workers/update +++ /dev/null @@ -1,488 +0,0 @@ -NAME - gcloud alpha run workers update - update Cloud Run environment variables - and other configuration settings - -SYNOPSIS - gcloud alpha run workers update [WORKER] [--async] - [--breakglass=JUSTIFICATION] [--description=DESCRIPTION] - [--max-instances=MAX_INSTANCES] [--max-surge=MAX_SURGE] - [--max-unavailable=MAX_UNAVAILABLE] [--mesh=MESH] - [--min-instances=MIN_INSTANCES] [--no-promote] [--region=REGION] - [--revision-suffix=REVISION_SUFFIX] [--scaling=SCALING] - [--service-account=SERVICE_ACCOUNT] [--[no-]session-affinity] - [--vpc-egress=VPC_EGRESS] - [--add-cloudsql-instances=[CLOUDSQL-INSTANCES,...] - | --clear-cloudsql-instances - | --remove-cloudsql-instances=[CLOUDSQL-INSTANCES,...] - | --set-cloudsql-instances=[CLOUDSQL-INSTANCES,...]] - [--add-custom-audiences=[CUSTOM-AUDIENCES,...] - | --clear-custom-audiences - | --remove-custom-audiences=[CUSTOM-AUDIENCES,...] - | --set-custom-audiences=[CUSTOM-AUDIENCES,...]] - [--add-volume=[KEY=VALUE,...] - --clear-volumes --remove-volume=[VOLUME,...]] - [--add-volume-mount=[volume=NAME,mount-path=MOUNT_PATH,...] - --args=[ARG,...] --clear-volume-mounts --command=[COMMAND,...] - --cpu=CPU --image=IMAGE --memory=MEMORY - --remove-volume-mount=[MOUNT_PATH,...] --clear-env-vars - | --env-vars-file=FILE_PATH | --set-env-vars=[KEY=VALUE,...] - | --remove-env-vars=[KEY,...] - --update-env-vars=[KEY=VALUE,...] --clear-secrets - | --set-secrets=[KEY=VALUE,...] - | --remove-secrets=[KEY,...] --update-secrets=[KEY=VALUE,...]] - [--binary-authorization=POLICY | --clear-binary-authorization] - [--clear-encryption-key-shutdown-hours - | --encryption-key-shutdown-hours=ENCRYPTION_KEY_SHUTDOWN_HOURS] - [--clear-key | --key=KEY] - [--clear-labels | --remove-labels=[KEY,...] --labels=[KEY=VALUE,...] - | --update-labels=[KEY=VALUE,...]] - [--clear-network - | --network=NETWORK --subnet=SUBNET --clear-network-tags - | --network-tags=[TAG,...]] - [--clear-post-key-revocation-action-type - | --post-key-revocation-action-type=POST_KEY_REVOCATION_ACTION_TYPE] - [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (ALPHA) Update Cloud Run environment variables and other configuration - settings. - -EXAMPLES - To update one or more env vars: - - $ gcloud alpha run workers update myworker \ - --update-env-vars=KEY1=VALUE1,KEY2=VALUE2 - -POSITIONAL ARGUMENTS - Worker resource - Worker to deploy to. 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 WORKER on the command line with a fully - specified name; - ◆ specify the worker name from an interactive prompt with a fully - specified name; - ◆ provide the argument --project on the command line; - ◆ set the property core/project. - - [WORKER] - ID of the worker or fully qualified identifier for the worker. - - To set the worker attribute: - ▸ provide the argument WORKER on the command line; - ▸ specify the worker name from an interactive prompt. - -FLAGS - --async - Return immediately, without waiting for the operation in progress to - complete. - - --breakglass=JUSTIFICATION - Justification to bypass Binary Authorization policy constraints and - allow the operation. See - https://cloud.google.com/binary-authorization/docs/using-breakglass for - more information. Next update or deploy command will automatically - clear existing breakglass justification. - - --description=DESCRIPTION - Provides an optional, human-readable description of the service. - - --max-instances=MAX_INSTANCES - The maximum number of container instances for this Revision to run or - 'default' to remove. This setting is immutably set on each new Revision - and modifying its value will deploy another Revision. Consider using - --max to set the maximum number of instances across all revisions of - the Worker which may be modified dynamically. - - --max-surge=MAX_SURGE - A maximum percentage of instances that will be moved in each step of - instance split changes. Use "default" to unset the limit and use the - platform default. - - --max-unavailable=MAX_UNAVAILABLE - A maximum percentage of instances that may be unavailable during - instance split changes. Use "default" to unset the limit and use the - platform default. - - --mesh=MESH - Enables Cloud Service Mesh using the specified mesh resource name. Mesh - resource name must be in the format of - projects/PROJECT/locations/global/meshes/MESH_NAME or MESH_NAME. Will - default to the current project if only MESH_NAME is provided. - - --min-instances=MIN_INSTANCES - The minimum number of container instances to run for this Revision or - 'default' to remove. This setting is immutably set on each new Revision - and modifying its value will deploy a another Revision. Consider using - --min to set the minimum number of instances across all revisions of - the Worker which may be modified dynamically. - - --no-promote - True to avoid assign instances to the worker revision being deployed. - Setting this flag assigns any instances assigned to the LATEST revision - to the specific revision bound to LATEST before the deployment. The - effect is that the revision being deployed will not receive instance - split. - - After a deployment with this flag the LATEST revision will not receive - instances on future deployments. To restore assinging instances to the - LATEST revision by default, run the gcloud run workers - update-instance-split command with --to-latest. - - --region=REGION - Region in which the resource can be found. Alternatively, set the - property [run/region]. - - --revision-suffix=REVISION_SUFFIX - Specify the suffix of the revision name. Revision names always start - with the service name automatically. For example, specifying - [--revision-suffix=v1] for a service named 'helloworld', would lead to - a revision named 'helloworld-v1'. Set empty string to clear the suffix - and resume server-assigned naming. - - --scaling=SCALING - The scaling mode to use for this resource. Flag value could be either - "auto" for automatic scaling, or a positive integer to configure manual - scaling with the given integer as a fixed instance count. - - --service-account=SERVICE_ACCOUNT - the email address of an IAM service account associated with the - revision of the service. The service account represents the identity of - the running revision, and determines what permissions the revision has. - - --[no-]session-affinity - Whether to enable session affinity for connections to the service. Use - --session-affinity to enable and --no-session-affinity to disable. - - --vpc-egress=VPC_EGRESS - Specify which of the outbound traffic to send through Direct VPC egress - or the VPC connector for this resource. This resource must have Direct - VPC egress enabled or a VPC connector to set this flag. VPC_EGRESS must - be one of: - - all - (DEPRECATED) Sends all outbound traffic through Direct VPC egress - or the VPC connector. Provides the same functionality as - 'all-traffic'. Prefer to use 'all-traffic' instead. - all-traffic - Sends all outbound traffic through Direct VPC egress or the VPC - connector. - private-ranges-only - Default option. Sends outbound traffic to private IP addresses (RFC - 1918 and Private Google Access IPs) through Direct VPC egress or - the VPC connector. - - Traffic to other Cloud Run services might require additional - configuration. See - https://cloud.google.com/run/docs/securing/private-networking#send_requests_to_other_services_and_services - for more information. - - These flags modify the Cloud SQL instances this Service connects to. You - can specify a name of a Cloud SQL instance if it's in the same project and - region as your Cloud Run service; otherwise specify - :: for the instance. - - At most one of these can be specified: - - --add-cloudsql-instances=[CLOUDSQL-INSTANCES,...] - Append the given values to the current Cloud SQL instances. - - --clear-cloudsql-instances - Empty the current Cloud SQL instances. - - --remove-cloudsql-instances=[CLOUDSQL-INSTANCES,...] - Remove the given values from the current Cloud SQL instances. - - --set-cloudsql-instances=[CLOUDSQL-INSTANCES,...] - Completely replace the current Cloud SQL instances with the given - values. - - These flags modify the custom audiences that can be used in the audience - field of ID token for authenticated requests. - - At most one of these can be specified: - - --add-custom-audiences=[CUSTOM-AUDIENCES,...] - Append the given values to the current custom audiences. - - --clear-custom-audiences - Empty the current custom audiences. - - --remove-custom-audiences=[CUSTOM-AUDIENCES,...] - Remove the given values from the current custom audiences. - - --set-custom-audiences=[CUSTOM-AUDIENCES,...] - Completely replace the current custom audiences with the given - values. - - --add-volume=[KEY=VALUE,...] - Adds a volume to the Cloud Run resource. To add more than one volume, - specify this flag multiple times. Volumes must have a name and type - key. Only certain values are supported for type. Depending on the - provided type, other keys will be required. The following types are - supported with the specified additional keys: - - cloud-storage: A volume representing a Cloud Storage bucket. This - volume type is mounted using Cloud Storage FUSE. See - https://cloud.google.com/storage/docs/gcs-fuse for the details and - limitations of this filesystem. Additional keys: - ◆ readonly: (optional) A boolean. If true, this volume will be - read-only from all mounts. - ◆ mount-options: (optional) A list of flags to pass to GCSFuse. Flags - should be specified without leading dashes and separated by - semicolons. - ◆ bucket: (optional) the name of the bucket to use as the source of - this volume. - ◆ dynamic-mounting: (optional) A boolean. If true, the volume will be - mounted dynamically. Note: You will either need to specify a bucket - or set dynamic-mounting to true, but not both. - - in-memory: An ephemeral volume that stores data in the instance's - memory. With this type of volume, data is not shared between instances - and all data will be lost when the instance it is on is terminated. - Additional keys: - ◆ size-limit: (optional) A quantity representing the maximum amount - of memory allocated to this volume, such as "512Mi" or "3G". Data - stored in an in-memory volume consumes the memory allocation of the - container that wrote the data. If size-limit is not specified, the - maximum size will be half the total memory limit of all containers. - - nfs: Represents a volume backed by an NFS server. Additional keys: - ◆ location: (required) The location of the NFS Server, in the form - SERVER:/PATH - ◆ readonly: (optional) A boolean. If true, this volume will be - read-only from all mounts. - - secret: Represents a secret stored in Secret Manager as a volume. - Additional keys: - ◆ secret: (required) The name of the secret in Secret Manager. Must - be a secret in the same project being deployed or be an alias mapped - in the run.googleapis.com/secrets annotation. - ◆ version: (required) The version of the secret to make available in - the volume. - ◆ path: (required) The relative path within the volume to mount that - version. - - --clear-volumes - Remove all existing volumes from the Cloud Run resource, including - volumes mounted as secrets - - --remove-volume=[VOLUME,...] - Removes volumes from the Cloud Run resource. - - Container Flags - - The following flags apply to the container. - - --add-volume-mount=[volume=NAME,mount-path=MOUNT_PATH,...] - Adds a mount to the current container. Must contain the keys - volume=NAME and mount-path=/PATH where NAME is the name of a volume - on this resource and PATH is the path within the container's - filesystem to mount this volume. - - --args=[ARG,...] - Comma-separated arguments passed to the command run by the - container image. If not specified and no '--command' is provided, - the container image's default Cmd is used. Otherwise, if not - specified, no arguments are passed. To reset this field to its - default, pass an empty string. - - --clear-volume-mounts - Remove all existing mounts from the current container. - - --command=[COMMAND,...] - Entrypoint for the container image. If not specified, the container - image's default Entrypoint is run. To reset this field to its - default, pass an empty string. - - --cpu=CPU - Set a CPU limit in Kubernetes cpu units. - - Cloud Run supports values fractional values below 1, 1, 2, 4, and - 8. Some CPU values requires a minimum Memory --memory value. - - --image=IMAGE - Name of the container image to deploy (e.g. - us-docker.pkg.dev/cloudrun/container/hello:latest). - - --memory=MEMORY - Set a memory limit. Ex: 1024Mi, 4Gi. - - --remove-volume-mount=[MOUNT_PATH,...] - Removes the volume mounted at the specified path from the current - container. - - At most one of these can be specified: - - --clear-env-vars - Remove all environment variables. - - --env-vars-file=FILE_PATH - Path to a local YAML file with definitions for all environment - variables. All existing environment variables will be removed - before the new environment variables are added. Example YAML - content: - - KEY_1: "value1" - KEY_2: "value 2" - - --set-env-vars=[KEY=VALUE,...] - List of key-value pairs to set as environment variables. All - existing environment variables will be removed first. - - Only --update-env-vars and --remove-env-vars can be used together. - If both are specified, --remove-env-vars will be applied first. - - --remove-env-vars=[KEY,...] - List of environment variables to be removed. - - --update-env-vars=[KEY=VALUE,...] - List of key-value pairs to set as environment variables. - - Specify secrets to mount or provide as environment variables. Keys - starting with a forward slash '/' are mount paths. All other keys - correspond to environment variables. Values should be in the form - SECRET_NAME:SECRET_VERSION. For example: - '--update-secrets=/secrets/api/key=mysecret:latest,ENV=othersecret:1' - will mount a volume at '/secrets/api' containing a file 'key' with the - latest version of secret 'mysecret'. An environment variable named ENV - will also be created whose value is version 1 of secret 'othersecret'. - - At most one of these can be specified: - - --clear-secrets - Remove all secrets. - - --set-secrets=[KEY=VALUE,...] - List of key-value pairs to set as secrets. All existing secrets - will be removed first. - - Only --update-secrets and --remove-secrets can be used together. If - both are specified, --remove-secrets will be applied first. - - --remove-secrets=[KEY,...] - List of secrets to be removed. - - --update-secrets=[KEY=VALUE,...] - List of key-value pairs to set as secrets. - - At most one of these can be specified: - - --binary-authorization=POLICY - Binary Authorization policy to check against. This must be set to - "default". - - --clear-binary-authorization - Remove any previously set Binary Authorization policy. - - At most one of these can be specified: - - --clear-encryption-key-shutdown-hours - Remove any previously set CMEK key shutdown hours setting. - - --encryption-key-shutdown-hours=ENCRYPTION_KEY_SHUTDOWN_HOURS - The number of hours to wait before an automatic shutdown server after - CMEK key revocation is detected. - - At most one of these can be specified: - - --clear-key - Remove any previously set CMEK key reference. - - --key=KEY - CMEK key reference to encrypt the container with. - - At most one of these can be specified: - - --clear-labels - Remove all labels. If --update-labels is also specified then - --clear-labels is applied first. - - For example, to remove all labels: - - $ gcloud alpha run workers update --clear-labels - - To remove all existing labels and create two new labels, foo and baz: - - $ gcloud alpha run workers update --clear-labels \ - --update-labels foo=bar,baz=qux - - --remove-labels=[KEY,...] - List of label keys to remove. If a label does not exist it is - silently ignored. If --update-labels is also specified then - --update-labels is applied first. - - At most one of these can be specified: - - --labels=[KEY=VALUE,...] - List of label KEY=VALUE pairs to add. - - An alias to --update-labels. - - --update-labels=[KEY=VALUE,...] - List of label KEY=VALUE pairs to update. If a label exists, its value - is modified. Otherwise, a new label is created. - - At most one of these can be specified: - - --clear-network - Disconnect this Cloud Run worker from the VPC network it is connected - to. - - Direct VPC egress setting flags group. - - --network=NETWORK - The VPC network that the Cloud Run worker will be able to send - traffic to. If --subnet is also specified, subnet must be a - subnetwork of the network specified by this --network flag. To - clear existing VPC network settings, use --clear-network. - - --subnet=SUBNET - The VPC subnetwork that the Cloud Run worker will get IPs from. The - subnetwork must be /26 or larger. If --network is also specified, - subnet must be a subnetwork of the network specified by the - --network flag. If --network is not specified, network will be - looked up from this subnetwork. To clear existing VPC network - settings, use --clear-network. - - At most one of these can be specified: - - --clear-network-tags - Clears all existing Compute Engine tags from the Cloud Run - worker. - - --network-tags=[TAG,...] - Applies the given Compute Engine tags (comma separated) to the - Cloud Run worker. To clear existing tags, use - --clear-network-tags. - - At most one of these can be specified: - - --clear-post-key-revocation-action-type - Remove any previously set post CMEK key revocation action type. - - --post-key-revocation-action-type=POST_KEY_REVOCATION_ACTION_TYPE - Action type after CMEK key revocation. - POST_KEY_REVOCATION_ACTION_TYPE must be one of: - - prevent-new - No new instances will be started after CMEK key revocation. - shut-down - No new instances will be started and the existing instances will - be shut down after CMEK key revocation. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --configuration, --flags-file, --flatten, --format, - --help, --impersonate-service-account, --log-http, --project, --quiet, - --trace-token, --user-output-enabled, --verbosity. - - Run $ gcloud help for details. - -NOTES - This command is currently in alpha and might change without notice. If this - command fails with API permission errors despite specifying the correct - project, you might be trying to access an API with an invitation-only early - access allowlist. - diff --git a/gcloud/alpha/run/workers/update-instance-split b/gcloud/alpha/run/workers/update-instance-split deleted file mode 100644 index 03fc38168..000000000 --- a/gcloud/alpha/run/workers/update-instance-split +++ /dev/null @@ -1,122 +0,0 @@ -NAME - gcloud alpha run workers update-instance-split - adjust the instance - assignments for a Cloud Run worker - -SYNOPSIS - gcloud alpha run workers update-instance-split [WORKER] [--async] - [--breakglass=JUSTIFICATION] [--region=REGION] - [--to-latest | --to-revisions=[REVISION-NAME=PERCENTAGE,...]] - [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (ALPHA) Adjust the instance assignments for a Cloud Run worker. - -EXAMPLES - To assign 10% of instances to revision my-worker-s5sxn and 90% of instances - to revision my-worker-cp9kw run: - - $ gcloud alpha run workers update-instance-split my-worker \ - --to-revisions=my-worker-s5sxn=10,my-worker-cp9kw=90 - - To increase the instances to revision my-worker-s5sxn to 20% and by - reducing the instances to revision my-worker-cp9kw to 80% run: - - $ gcloud alpha run workers update-instance-split my-worker \ - --to-revisions=my-worker-s5sxn=20 - - To rollback to revision my-worker-cp9kw run: - - $ gcloud alpha run workers update-instance-split my-worker \ - --to-revisions=my-worker-cp9kw=100 - - To assign 100% of instances to the current or future LATEST revision run: - - $ gcloud alpha run workers update-instance-split my-worker \ - --to-latest - - You can also refer to the current or future LATEST revision in - --to-revisions by the string "LATEST". For example, to set 10% of instances - to always float to the latest revision: - - $ gcloud alpha run workers update-instance-split my-worker \ - --to-revisions=LATEST=10 - -POSITIONAL ARGUMENTS - Worker resource - Worker to update instance split of. 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 WORKER on the command line with a fully - specified name; - ◆ specify the worker name from an interactive prompt with a fully - specified name; - ◆ provide the argument --project on the command line; - ◆ set the property core/project. - - [WORKER] - ID of the worker or fully qualified identifier for the worker. - - To set the worker attribute: - ▸ provide the argument WORKER on the command line; - ▸ specify the worker name from an interactive prompt. - -FLAGS - --async - Return immediately, without waiting for the operation in progress to - complete. - - --breakglass=JUSTIFICATION - Justification to bypass Binary Authorization policy constraints and - allow the operation. See - https://cloud.google.com/binary-authorization/docs/using-breakglass for - more information. Next update or deploy command will automatically - clear existing breakglass justification. - - --region=REGION - Region in which the resource can be found. Alternatively, set the - property [run/region]. - - At most one of these can be specified: - - --to-latest - True to assign 100 percent of instances to the 'latest' revision of - this service. Note that when a new revision is created, it will - become the 'latest' and instances will be fully assigned to it unless - configured otherwise using --[no-]promote flag. Defaults to False. - Synonymous with '--to-revisions=LATEST=100'. - - --to-revisions=[REVISION-NAME=PERCENTAGE,...] - Comma separated list of instance assignments in the form - REVISION-NAME=PERCENTAGE. REVISION-NAME must be the name for a - revision for the worker as returned by 'gcloud run workers revisions - list --worker=WORKER' . PERCENTAGE must be an integer percentage - between 0 and 100 inclusive. Ex worker-nw9hs=10,worker-nw9hs=20 Up to - 100 percent of instances may be assigned. If the total of 100 percent - of instances is assigned, the Worker instance split is updated as - specified. If under 100 percent of instance split is assigned, the - Worker instance split is updated as specified for revisions with - assignments and instance split is scaled up or down proportionally as - needed for revision that are currently serving workload but that do - not have new assignments. For example assume revision-1 is serving 40 - percent of workload and revision-2 is serving 60 percent. If - revision-1 is assigned 45 percent of instances and no assignment is - made for revision-2, the worker is updated with revsion-1 assigned 45 - percent of instances and revision-2 scaled down to 55 percent. You - can use "LATEST" as a special revision name to always put the given - percentage of instance split on the latest ready revision. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --configuration, --flags-file, --flatten, --format, - --help, --impersonate-service-account, --log-http, --project, --quiet, - --trace-token, --user-output-enabled, --verbosity. - - Run $ gcloud help for details. - -NOTES - This command is currently in alpha and might change without notice. If this - command fails with API permission errors despite specifying the correct - project, you might be trying to access an API with an invitation-only early - access allowlist. - diff --git a/gcloud/alpha/scc/manage/services/describe b/gcloud/alpha/scc/manage/services/describe index f6d38def9..acab57564 100644 --- a/gcloud/alpha/scc/manage/services/describe +++ b/gcloud/alpha/scc/manage/services/describe @@ -60,6 +60,8 @@ POSITIONAL ARGUMENTS ◆ web-security-scanner (can be abbreviated as wss) + ◆ vm-threat-detection-aws (can be abbreviated as vmtd-aws) + REQUIRED FLAGS Exactly one of these must be specified: diff --git a/gcloud/alpha/scc/manage/services/update b/gcloud/alpha/scc/manage/services/update index 2f7f3ea4f..6081388c1 100644 --- a/gcloud/alpha/scc/manage/services/update +++ b/gcloud/alpha/scc/manage/services/update @@ -52,6 +52,8 @@ POSITIONAL ARGUMENTS ◆ web-security-scanner (can be abbreviated as wss) + ◆ vm-threat-detection-aws (can be abbreviated as vmtd-aws) + REQUIRED FLAGS At least one of these must be specified: diff --git a/gcloud/alpha/storage/buckets/anywhere-caches/create b/gcloud/alpha/storage/buckets/anywhere-caches/create index bf7d138fe..09d2ff664 100644 --- a/gcloud/alpha/storage/buckets/anywhere-caches/create +++ b/gcloud/alpha/storage/buckets/anywhere-caches/create @@ -62,5 +62,7 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. + access allowlist. This variant is also available: + + $ gcloud storage buckets anywhere-caches create diff --git a/gcloud/alpha/storage/buckets/anywhere-caches/describe b/gcloud/alpha/storage/buckets/anywhere-caches/describe index 1455cf242..bf02ba8f9 100644 --- a/gcloud/alpha/storage/buckets/anywhere-caches/describe +++ b/gcloud/alpha/storage/buckets/anywhere-caches/describe @@ -38,5 +38,7 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. + access allowlist. This variant is also available: + + $ gcloud storage buckets anywhere-caches describe diff --git a/gcloud/alpha/storage/buckets/anywhere-caches/disable b/gcloud/alpha/storage/buckets/anywhere-caches/disable index 92a8e5512..8d3ffc78b 100644 --- a/gcloud/alpha/storage/buckets/anywhere-caches/disable +++ b/gcloud/alpha/storage/buckets/anywhere-caches/disable @@ -41,5 +41,7 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. + access allowlist. This variant is also available: + + $ gcloud storage buckets anywhere-caches disable diff --git a/gcloud/alpha/storage/buckets/anywhere-caches/help b/gcloud/alpha/storage/buckets/anywhere-caches/help index 680ac926a..58fbe61e3 100644 --- a/gcloud/alpha/storage/buckets/anywhere-caches/help +++ b/gcloud/alpha/storage/buckets/anywhere-caches/help @@ -41,5 +41,7 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. + access allowlist. This variant is also available: + + $ gcloud storage buckets anywhere-caches diff --git a/gcloud/alpha/storage/buckets/anywhere-caches/list b/gcloud/alpha/storage/buckets/anywhere-caches/list index b9c6168c3..6a7a6a9f3 100644 --- a/gcloud/alpha/storage/buckets/anywhere-caches/list +++ b/gcloud/alpha/storage/buckets/anywhere-caches/list @@ -70,5 +70,7 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. + access allowlist. This variant is also available: + + $ gcloud storage buckets anywhere-caches list diff --git a/gcloud/alpha/storage/buckets/anywhere-caches/pause b/gcloud/alpha/storage/buckets/anywhere-caches/pause index 7f4de8e2f..b0d691e78 100644 --- a/gcloud/alpha/storage/buckets/anywhere-caches/pause +++ b/gcloud/alpha/storage/buckets/anywhere-caches/pause @@ -35,5 +35,7 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. + access allowlist. This variant is also available: + + $ gcloud storage buckets anywhere-caches pause diff --git a/gcloud/alpha/storage/buckets/anywhere-caches/resume b/gcloud/alpha/storage/buckets/anywhere-caches/resume index 8064a1bec..624caecd6 100644 --- a/gcloud/alpha/storage/buckets/anywhere-caches/resume +++ b/gcloud/alpha/storage/buckets/anywhere-caches/resume @@ -36,5 +36,7 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. + access allowlist. This variant is also available: + + $ gcloud storage buckets anywhere-caches resume diff --git a/gcloud/alpha/storage/buckets/anywhere-caches/update b/gcloud/alpha/storage/buckets/anywhere-caches/update index a6210996e..c48c18a94 100644 --- a/gcloud/alpha/storage/buckets/anywhere-caches/update +++ b/gcloud/alpha/storage/buckets/anywhere-caches/update @@ -53,5 +53,7 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. + access allowlist. This variant is also available: + + $ gcloud storage buckets anywhere-caches update diff --git a/gcloud/app/create b/gcloud/app/create index d4c319fd5..2fc42e101 100644 --- a/gcloud/app/create +++ b/gcloud/app/create @@ -4,7 +4,7 @@ NAME SYNOPSIS gcloud app create [--region=REGION] [--service-account=SERVICE_ACCOUNT] - [GCLOUD_WIDE_FLAG ...] + [--ssl-policy=SSL_POLICY] [GCLOUD_WIDE_FLAG ...] DESCRIPTION Create an App Engine app within the current Google Cloud Project. @@ -22,6 +22,10 @@ EXAMPLES $ gcloud app create --service-account=SERVICE_ACCOUNT + To create an app with minimum SSL policy allowing TLS 1.2 and above, run: + + $ gcloud app create --ssl-policy=TLS_VERSION_1_2 + FLAGS --region=REGION The region to create the app within. Use gcloud app regions list to @@ -37,6 +41,10 @@ FLAGS https://cloud.google.com/appengine/docs/standard/python3/service-account outlines the limitation of that service account. + --ssl-policy=SSL_POLICY + The app-level SSL policy to create the app with. SSL_POLICY must be one + of: TLS_VERSION_1_0, TLS_VERSION_1_2. + 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/app/update b/gcloud/app/update index f3c0ca3f4..62d1f1555 100644 --- a/gcloud/app/update +++ b/gcloud/app/update @@ -3,7 +3,8 @@ NAME SYNOPSIS gcloud app update [--service-account=SERVICE_ACCOUNT] - [--[no-]split-health-checks] [GCLOUD_WIDE_FLAG ...] + [--[no-]split-health-checks] [--ssl-policy=SSL_POLICY] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION This command is used to update settings on an app engine application. @@ -17,6 +18,10 @@ EXAMPLES $ gcloud app update --service-account=SERVICE_ACCOUNT + To update the app-level minimum SSL policy of the application: + + $ gcloud app update --ssl-policy=TLS_VERSION_1_2 + FLAGS --service-account=SERVICE_ACCOUNT The app-level default service account to update the app with. @@ -26,6 +31,10 @@ FLAGS --split-health-checks to enable and --no-split-health-checks to disable. + --ssl-policy=SSL_POLICY + The app-level SSL policy to update the app with. SSL_POLICY must be one + of: TLS_VERSION_1_0, TLS_VERSION_1_2. + 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/artifacts/docker/upgrade/migrate b/gcloud/artifacts/docker/upgrade/migrate index ff137eae1..b055d5493 100644 --- a/gcloud/artifacts/docker/upgrade/migrate +++ b/gcloud/artifacts/docker/upgrade/migrate @@ -5,10 +5,13 @@ NAME SYNOPSIS gcloud artifacts docker upgrade migrate [--canary-reads=PERCENT] [--copy-only] [--from-gcr=GCR_HOST/PROJECT_ID] - [--last-uploaded-versions=N] [--max-threads=MAX_THREADS; default=8] + [--input-iam-policy-dir=DIRECTORY] [--last-uploaded-versions=N] + [--max-threads=MAX_THREADS; default=8] + [--output-iam-policy-dir=DIRECTORY] [--pkg-dev-location=PKG_DEV_LOCATION] [--projects=PROJECTS] - [--recent-images=NUM_DAYS] [--skip-iam-update] - [--to-pkg-dev=PROJECT_ID/REPOSITORY_ID] [GCLOUD_WIDE_FLAG ...] + [--recent-images=NUM_DAYS] [--skip-iam-update] [--skip-pre-copy] + [--to-pkg-dev=PROJECT_ID/REPOSITORY_ID] [--no-use-analyze-iam] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION Migrate projects from Container Registry to Artifact Registry @@ -40,6 +43,10 @@ FLAGS Container Registry host + project to copy from. This flag is only used when migrating to pkg.dev repos. Example: gcr.io/my-project + --input-iam-policy-dir=DIRECTORY + During the IAM update step, the tool applies all iam policies in the + given directory. + --last-uploaded-versions=N Only copy the N most recently uploaded versions of each image. More than N images may be copied if new images are uploaded during @@ -49,6 +56,13 @@ FLAGS Max number of images to copy simultaneously. Consider quota usage when increasing this + --output-iam-policy-dir=DIRECTORY + Outputs Artifact Registry-equivalent bindings to this directory during + IAM update step and then exits the tool. After any neccesary + modifications are made, the tool can be rerun with + --input-iam-policy-dir to continue migration with the generated + bindings. + --pkg-dev-location=PKG_DEV_LOCATION The location of the pkg-dev repository you are migrating to. If not specified, migration is always done to the same multi-region as GCR. @@ -67,10 +81,19 @@ FLAGS Migrate without changing iam-policy. Users without Artifact Registry permissions will not have access to migrated images. + --skip-pre-copy + Skip the initial copy of recent images before enabling redirection. + --to-pkg-dev=PROJECT_ID/REPOSITORY_ID Artifact Registry pkg.dev project ID and repository ID to copy to. Example: my-project/my-repo + --use-analyze-iam + Use analyzeIAMPolicy to get IAM bindings. If false, tooling iterates + through IAM bindings itself, which is slower, but doesn't require + anlayzeIAMPolicy quota. Enabled by default, use --no-use-analyze-iam to + disable. + 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/artifacts/repositories/create b/gcloud/artifacts/repositories/create index 636634413..4d7b3e39e 100644 --- a/gcloud/artifacts/repositories/create +++ b/gcloud/artifacts/repositories/create @@ -10,7 +10,8 @@ SYNOPSIS [--mode=MODE; default="NONE"] [--remote-apt-repo=REMOTE_APT_REPO] [--remote-apt-repo-path=REMOTE_APT_REPO_PATH] [--remote-docker-repo=REMOTE_DOCKER_REPO] - [--remote-mvn-repo=REMOTE_MVN_REPO] [--remote-npm-repo=REMOTE_NPM_REPO] + [--remote-go-repo=REMOTE_GO_REPO] [--remote-mvn-repo=REMOTE_MVN_REPO] + [--remote-npm-repo=REMOTE_NPM_REPO] [--remote-password-secret-version=REMOTE_PASSWORD_SECRET_VERSION] [--remote-python-repo=REMOTE_PYTHON_REPO] [--remote-repo-config-desc=REMOTE_REPO_CONFIG_DESC] @@ -161,6 +162,10 @@ OPTIONAL FLAGS ◆ one of the following enums: [docker-hub]. ◆ an http/https custom registry uri (ex: https://my.docker.registry) + --remote-go-repo=REMOTE_GO_REPO + (Go only) Repo upstream for Go remote repository. + "https://proxy.golang.org/" is the only valid value. + --remote-mvn-repo=REMOTE_MVN_REPO (Maven only) Repo upstream for maven remote repository. REMOTE_MVN_REPO can be either: diff --git a/gcloud/beta/ai/endpoints/deploy-model b/gcloud/beta/ai/endpoints/deploy-model index 4def09703..8500a7eba 100644 --- a/gcloud/beta/ai/endpoints/deploy-model +++ b/gcloud/beta/ai/endpoints/deploy-model @@ -11,6 +11,7 @@ SYNOPSIS [--enable-container-logging] [--machine-type=MACHINE_TYPE] [--max-replica-count=MAX_REPLICA_COUNT] [--min-replica-count=MIN_REPLICA_COUNT] + [--multihost-gpu-node-count=MULTIHOST_GPU_NODE_COUNT] [--reservation-affinity=[key=KEY], [reservation-affinity-type=RESERVATION-AFFINITY-TYPE], [values=VALUES]] [--service-account=SERVICE_ACCOUNT] [--spot] @@ -133,6 +134,10 @@ OPTIONAL FLAGS If not specified and the uploaded models use dedicated resources, the default value is 1. + --multihost-gpu-node-count=MULTIHOST_GPU_NODE_COUNT + The number of nodes per replica for multihost GPU deployments. Required + for multihost GPU deployments. + --reservation-affinity=[key=KEY],[reservation-affinity-type=RESERVATION-AFFINITY-TYPE],[values=VALUES] A ReservationAffinity can be used to configure a Vertex AI resource (e.g., a DeployedModel) to draw its Compute Engine resources from a diff --git a/gcloud/beta/app/create b/gcloud/beta/app/create index a6ae1b703..dab54c4ff 100644 --- a/gcloud/beta/app/create +++ b/gcloud/beta/app/create @@ -4,7 +4,8 @@ NAME SYNOPSIS gcloud beta app create [--region=REGION] - [--service-account=SERVICE_ACCOUNT] [GCLOUD_WIDE_FLAG ...] + [--service-account=SERVICE_ACCOUNT] [--ssl-policy=SSL_POLICY] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) Create an App Engine app within the current Google Cloud Project. @@ -22,6 +23,10 @@ EXAMPLES $ gcloud beta app create --service-account=SERVICE_ACCOUNT + To create an app with minimum SSL policy allowing TLS 1.2 and above, run: + + $ gcloud beta app create --ssl-policy=TLS_VERSION_1_2 + FLAGS --region=REGION The region to create the app within. Use gcloud app regions list to @@ -37,6 +42,10 @@ FLAGS https://cloud.google.com/appengine/docs/standard/python3/service-account outlines the limitation of that service account. + --ssl-policy=SSL_POLICY + The app-level SSL policy to create the app with. SSL_POLICY must be one + of: TLS_VERSION_1_0, TLS_VERSION_1_2. + GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, diff --git a/gcloud/beta/app/update b/gcloud/beta/app/update index 4b5d280bf..80649123d 100644 --- a/gcloud/beta/app/update +++ b/gcloud/beta/app/update @@ -3,7 +3,8 @@ NAME SYNOPSIS gcloud beta app update [--service-account=SERVICE_ACCOUNT] - [--[no-]split-health-checks] [GCLOUD_WIDE_FLAG ...] + [--[no-]split-health-checks] [--ssl-policy=SSL_POLICY] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) This command is used to update settings on an app engine @@ -18,6 +19,10 @@ EXAMPLES $ gcloud beta app update --service-account=SERVICE_ACCOUNT + To update the app-level minimum SSL policy of the application: + + $ gcloud beta app update --ssl-policy=TLS_VERSION_1_2 + FLAGS --service-account=SERVICE_ACCOUNT The app-level default service account to update the app with. @@ -27,6 +32,10 @@ FLAGS --split-health-checks to enable and --no-split-health-checks to disable. + --ssl-policy=SSL_POLICY + The app-level SSL policy to update the app with. SSL_POLICY must be one + of: TLS_VERSION_1_0, TLS_VERSION_1_2. + GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, diff --git a/gcloud/beta/compute/disk-settings/describe b/gcloud/beta/compute/disk-settings/describe new file mode 100644 index 000000000..016d7b952 --- /dev/null +++ b/gcloud/beta/compute/disk-settings/describe @@ -0,0 +1,36 @@ +NAME + gcloud beta compute disk-settings describe - describe a Google Compute + Engine disk setting + +SYNOPSIS + gcloud beta compute disk-settings describe (--region=REGION | --zone=ZONE) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Describe a Google Compute Engine disk setting. + +REQUIRED FLAGS + Scope for disk settings. + + Exactly one of these must be specified: + + --region=REGION + region for disk settings + + --zone=ZONE + Zone for disk settings + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha compute disk-settings describe + diff --git a/gcloud/beta/compute/disk-settings/help b/gcloud/beta/compute/disk-settings/help new file mode 100644 index 000000000..03950d507 --- /dev/null +++ b/gcloud/beta/compute/disk-settings/help @@ -0,0 +1,32 @@ +NAME + gcloud beta compute disk-settings - read Compute Engine disk settings + +SYNOPSIS + gcloud beta compute disk-settings COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Disks settings allows the configuration of various disk-related + behavior. + + At this time, only the access location is allowed to be configured. + +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) Describe a Google Compute Engine disk setting. + + update + (BETA) Update disk settings. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha compute disk-settings + diff --git a/gcloud/beta/compute/disk-settings/update b/gcloud/beta/compute/disk-settings/update new file mode 100644 index 000000000..872006003 --- /dev/null +++ b/gcloud/beta/compute/disk-settings/update @@ -0,0 +1,65 @@ +NAME + gcloud beta compute disk-settings update - update disk settings + +SYNOPSIS + gcloud beta compute disk-settings update (--region=REGION | --zone=ZONE) + [--access-location-policy=ACCESS_LOCATION_POLICY] + [--add-access-locations=[ADD_ACCESS_LOCATIONS,...]] + [--remove-access-locations=[REMOVE_ACCESS_LOCATIONS,...]] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Update disk settings. + +EXAMPLES + To update the disk settings in zone us-west1-a, add the access location + ``us-central1 `` and remove the access location ``us-central2`` in the + project my-gcp-project, run: + + $ gcloud beta compute disk-settings update \ + --add-access-locations=us-central1 \ + --remove-access-locations=us-central2 --project=my-gcp-project \ + --zone=us-west1-a + +REQUIRED FLAGS + Scope for disk settings. + + Exactly one of these must be specified: + + --region=REGION + region for disk settings + + --zone=ZONE + Zone for disk settings + +OPTIONAL FLAGS + --access-location-policy=ACCESS_LOCATION_POLICY + The access location policy for disk settings. ACCESS_LOCATION_POLICY + must be one of: + + all-regions + All regions will be allowed to access the source disk. + specific-regions + Only the specified regions will be allowed to access the source + disk. + + --add-access-locations=[ADD_ACCESS_LOCATIONS,...] + Access locations to add to disk settings + + --remove-access-locations=[REMOVE_ACCESS_LOCATIONS,...] + Access locations to remove from disk settings + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha compute disk-settings update + diff --git a/gcloud/beta/compute/disks/create b/gcloud/beta/compute/disks/create index 0f5cd2044..2da296fca 100644 --- a/gcloud/beta/compute/disks/create +++ b/gcloud/beta/compute/disks/create @@ -15,6 +15,8 @@ SYNOPSIS [--replica-zones=ZONE,ZONE] [--no-require-csek-key-create] [--resource-policies=[RESOURCE_POLICY,...]] [--size=SIZE] [--storage-pool=STORAGE_POOL] [--type=TYPE] + [--global-source-snapshot + | --source-snapshot-region=SOURCE_SNAPSHOT_REGION] [--image-family-scope=IMAGE_FAMILY_SCOPE --image-project=IMAGE_PROJECT --image=IMAGE | --image-family=IMAGE_FAMILY | --primary-disk=PRIMARY_DISK @@ -184,6 +186,15 @@ FLAGS types, run gcloud compute disk-types list. The default disk type is pd-standard. + At most one of these can be specified: + + --global-source-snapshot + If set, the snapshot is global. + + --source-snapshot-region=SOURCE_SNAPSHOT_REGION + Region of the snapshot to operate on. Overrides the default + compute/region property value for this command invocation. + --image-family-scope=IMAGE_FAMILY_SCOPE Sets the scope for the --image-family flag. By default, when specifying an image family in a public image project, the zonal image family scope diff --git a/gcloud/beta/compute/future-reservations/create b/gcloud/beta/compute/future-reservations/create index 7bb3e4d1a..7f25f5433 100644 --- a/gcloud/beta/compute/future-reservations/create +++ b/gcloud/beta/compute/future-reservations/create @@ -9,11 +9,13 @@ SYNOPSIS | [--machine-type=MACHINE_TYPE : --accelerator=[count=COUNT],[type=TYPE] --local-ssd=[count=COUNT],[interface=INTERFACE],[size=SIZE] - --min-cpu-platform=MIN_CPU_PLATFORM]) + --min-cpu-platform=MIN_CPU_PLATFORM] | [--tpu-version=TPU_VERSION + : --chip-count=CHIP_COUNT --workload-type=WORKLOAD_TYPE]) (--start-time=START_TIME (--duration=DURATION | --end-time=END_TIME)) [--deployment-type=DEPLOYMENT_TYPE] [--description=DESCRIPTION] [--name-prefix=NAME_PREFIX] [--planning-status=PLANNING_STATUS] [--[no-]require-specific-reservation] + [--reservation-mode=RESERVATION_MODE] [--reservation-name=RESERVATION_NAME] [--scheduling-type=SCHEDULING_TYPE] [--total-count=TOTAL_COUNT] [--zone=ZONE] @@ -112,6 +114,35 @@ REQUIRED FLAGS --min-cpu-platform=MIN_CPU_PLATFORM Optional minimum CPU platform of the reservation to create. + You must define the version and number of TPUs to reserve. + + --tpu-version=TPU_VERSION + The version of Cloud TPU to reserve. TPU_VERSION must be one of: + + V5E + Cloud TPU v5e Lite + V5P + Cloud TPU v5p + V6E + Cloud TPU v6e + + This flag argument must be specified if any of the other arguments + in this group are specified. + + --chip-count=CHIP_COUNT + The number of chips to reserve. + + --workload-type=WORKLOAD_TYPE + The workload type of the TPU reservation. WORKLOAD_TYPE must be one + of: + + BATCH + Reserved resources will be optimized for BATCH workloads, such + as ML training. + SERVING + Reserved resources will be optimized for SERVING workloads, + such as ML inference + Manage the time specific properties for requesting future capacity This must be specified. @@ -180,6 +211,19 @@ OPTIONAL FLAGS the name of the future reservation. Use --require-specific-reservation to enable and --no-require-specific-reservation to disable. + --reservation-mode=RESERVATION_MODE + The mode of the reservation. RESERVATION_MODE must be one of: + + CALENDAR + This indicates to create a future reservation in calendar mode, + which is ideal for reserving GPU VMs. The auto-created reservations + for the future reservation are automatically deleted at the end of + the reservation period. + DEFAULT + This indicates to create a standard future reservation. If you want + to automatically delete the auto-created reservations, then you + must use the --auto-delete-auto-created-reservations flag. + --reservation-name=RESERVATION_NAME Name of reservations where the capacity is provisioned at the time of delivery of future reservations. If the reservation with the given name diff --git a/gcloud/beta/compute/help b/gcloud/beta/compute/help index 43fcab9ce..377722cdb 100644 --- a/gcloud/beta/compute/help +++ b/gcloud/beta/compute/help @@ -42,6 +42,9 @@ GROUPS diagnose (BETA) Debugging tools for Compute Engine virtual machine instances. + disk-settings + (BETA) Read Compute Engine disk settings. + disk-types (BETA) Read Compute Engine virtual disk types. diff --git a/gcloud/beta/compute/snapshot-settings/describe b/gcloud/beta/compute/snapshot-settings/describe index 35b0888f1..709d73b99 100644 --- a/gcloud/beta/compute/snapshot-settings/describe +++ b/gcloud/beta/compute/snapshot-settings/describe @@ -2,7 +2,8 @@ NAME gcloud beta compute snapshot-settings describe - describe snapshot settings SYNOPSIS - gcloud beta compute snapshot-settings describe [GCLOUD_WIDE_FLAG ...] + gcloud beta compute snapshot-settings describe [--region=REGION] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) Describe the snapshot settings of a project. @@ -12,6 +13,10 @@ EXAMPLES $ gcloud beta compute snapshot-settings describe --project=my-project +FLAGS + --region=REGION + region for regional snapshot settings + GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, diff --git a/gcloud/beta/compute/snapshot-settings/update b/gcloud/beta/compute/snapshot-settings/update index 6d39f164e..190b10acb 100644 --- a/gcloud/beta/compute/snapshot-settings/update +++ b/gcloud/beta/compute/snapshot-settings/update @@ -2,7 +2,11 @@ NAME gcloud beta compute snapshot-settings update - update snapshot settings SYNOPSIS - gcloud beta compute snapshot-settings update [--async] + gcloud beta compute snapshot-settings update + [--access-location-policy=ACCESS_LOCATION_POLICY] + [--add-access-locations=[ADD_ACCESS_LOCATIONS,...]] [--async] + [--region=REGION] + [--remove-access-locations=[REMOVE_ACCESS_LOCATIONS,...]] [--storage-location-names=[STORAGE_LOCATION_NAMES,...]] [--storage-location-policy=STORAGE_LOCATION_POLICY] [GCLOUD_WIDE_FLAG ...] @@ -31,10 +35,23 @@ EXAMPLES --storage-location-names=us-west1 FLAGS + --access-location-policy=ACCESS_LOCATION_POLICY + The access location policy. ACCESS_LOCATION_POLICY must be one of: + all-regions, specific-regions. + + --add-access-locations=[ADD_ACCESS_LOCATIONS,...] + Access locations to add to snapshot settings + --async Return immediately, without waiting for the operation in progress to complete. + --region=REGION + region for regional snapshot settings + + --remove-access-locations=[REMOVE_ACCESS_LOCATIONS,...] + Access locations to remove from snapshot settings + --storage-location-names=[STORAGE_LOCATION_NAMES,...] The custom storage location that you specify for the project's snapshots. You can specify only a single location. Use this flag only diff --git a/gcloud/beta/compute/snapshots/add-labels b/gcloud/beta/compute/snapshots/add-labels index 3bdc13645..5dca1858e 100644 --- a/gcloud/beta/compute/snapshots/add-labels +++ b/gcloud/beta/compute/snapshots/add-labels @@ -4,7 +4,8 @@ NAME SYNOPSIS gcloud beta compute snapshots add-labels SNAPSHOT_NAME - --labels=[KEY=VALUE,...] [GCLOUD_WIDE_FLAG ...] + --labels=[KEY=VALUE,...] [--global | --region=REGION] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) gcloud beta compute snapshots add-labels adds labels to a Google @@ -34,6 +35,16 @@ REQUIRED FLAGS --labels=[KEY=VALUE,...] A list of labels to add. +OPTIONAL FLAGS + At most one of these can be specified: + + --global + If set, the snapshot is global. + + --region=REGION + Region of the snapshot to operate on. Overrides the default + compute/region property value for this command invocation. + GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, diff --git a/gcloud/beta/compute/snapshots/create b/gcloud/beta/compute/snapshots/create index 5c653ffd0..644058786 100644 --- a/gcloud/beta/compute/snapshots/create +++ b/gcloud/beta/compute/snapshots/create @@ -11,6 +11,9 @@ SYNOPSIS [--source-disk-key-file=FILE] [--source-instant-snapshot=SOURCE_INSTANT_SNAPSHOT] [--source-instant-snapshot-key-file=FILE] [--storage-location=LOCATION] + [--global | --region=REGION] + [--kms-key=KMS_KEY : --kms-keyring=KMS_KEYRING + --kms-location=KMS_LOCATION --kms-project=KMS_PROJECT] [--source-disk-region=SOURCE_DISK_REGION | --source-disk-zone=SOURCE_DISK_ZONE] [--source-instant-snapshot-region=SOURCE_INSTANT_SNAPSHOT_REGION @@ -118,6 +121,57 @@ FLAGS snapshot content is to be stored. If absent, a nearby regional or multi-regional location is chosen automatically. + Scope for snapshot. + + At most one of these can be specified: + + --global + If set, the snapshot will be created in the global scope + + --region=REGION + If set, the snapshot will be created in the regional scope + + Key resource - The Cloud KMS (Key Management Service) cryptokey that will + be used to protect the snapshot. The 'Compute Engine 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; + ▸ provide the argument --region 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. + At most one of these can be specified: --source-disk-region=SOURCE_DISK_REGION diff --git a/gcloud/beta/compute/snapshots/delete b/gcloud/beta/compute/snapshots/delete index 32adc0a55..123d9d628 100644 --- a/gcloud/beta/compute/snapshots/delete +++ b/gcloud/beta/compute/snapshots/delete @@ -3,11 +3,10 @@ NAME SYNOPSIS gcloud beta compute snapshots delete SNAPSHOT_NAME [SNAPSHOT_NAME ...] - [GCLOUD_WIDE_FLAG ...] + [--global | --region=REGION] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) gcloud beta compute snapshots delete deletes one or more Compute - Engine snapshots. + (BETA) Delete Compute Engine snapshots. EXAMPLES To delete Compute Engine snapshots with the names 'snapshot-1' and @@ -28,6 +27,16 @@ POSITIONAL ARGUMENTS SNAPSHOT_NAME [SNAPSHOT_NAME ...] Names of the snapshots to delete. +FLAGS + At most one of these can be specified: + + --global + If set, the snapshots are global. + + --region=REGION + Region of the snapshots to delete. Overrides the default + compute/region property value for this command invocation. + GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, diff --git a/gcloud/beta/compute/snapshots/describe b/gcloud/beta/compute/snapshots/describe index 5eec0f49d..0b4be3987 100644 --- a/gcloud/beta/compute/snapshots/describe +++ b/gcloud/beta/compute/snapshots/describe @@ -2,7 +2,8 @@ NAME gcloud beta compute snapshots describe - describe a Compute Engine snapshot SYNOPSIS - gcloud beta compute snapshots describe SNAPSHOT_NAME [GCLOUD_WIDE_FLAG ...] + gcloud beta compute snapshots describe SNAPSHOT_NAME + [--global | --region=REGION] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) gcloud beta compute snapshots describe displays all data associated @@ -40,6 +41,16 @@ POSITIONAL ARGUMENTS SNAPSHOT_NAME Name of the snapshot to describe. +FLAGS + At most one of these can be specified: + + --global + If set, the snapshot is global. + + --region=REGION + Region of the snapshot to describe. Overrides the default + compute/region property value for this command invocation. + GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, diff --git a/gcloud/beta/compute/snapshots/list b/gcloud/beta/compute/snapshots/list index 738152b8a..8b919c54a 100644 --- a/gcloud/beta/compute/snapshots/list +++ b/gcloud/beta/compute/snapshots/list @@ -3,8 +3,9 @@ NAME SYNOPSIS gcloud beta compute snapshots list [NAME ...] [--regexp=REGEXP, -r REGEXP] - [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] - [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + [--global | --regions=[REGION,...]] [--filter=EXPRESSION] + [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) gcloud beta compute snapshots list displays all Google Compute @@ -35,6 +36,15 @@ FLAGS Flag --regexp is deprecated. Use --filter="name~'REGEXP'" instead. + At most one of these can be specified: + + --global + If provided, only global resources are shown. + + --regions=[REGION,...] + If provided, only regional resources are shown. If arguments are + provided, only resources from the given regions are shown. + LIST COMMAND FLAGS --filter=EXPRESSION Apply a Boolean filter EXPRESSION to each resource item to be listed. diff --git a/gcloud/beta/compute/snapshots/remove-labels b/gcloud/beta/compute/snapshots/remove-labels index 2e30415d5..d0bae185b 100644 --- a/gcloud/beta/compute/snapshots/remove-labels +++ b/gcloud/beta/compute/snapshots/remove-labels @@ -4,7 +4,8 @@ NAME SYNOPSIS gcloud beta compute snapshots remove-labels SNAPSHOT_NAME - (--all | --labels=KEY,[KEY,...]) [GCLOUD_WIDE_FLAG ...] + (--all | --labels=KEY,[KEY,...]) [--global | --region=REGION] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) gcloud beta compute snapshots remove-labels removes labels from a @@ -39,6 +40,16 @@ REQUIRED FLAGS --labels=KEY,[KEY,...] A comma-separated list of label keys to remove from the resource. +OPTIONAL FLAGS + At most one of these can be specified: + + --global + If set, the snapshot is global. + + --region=REGION + Region of the snapshot to operate on. Overrides the default + compute/region property value for this command invocation. + GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, diff --git a/gcloud/beta/compute/snapshots/update b/gcloud/beta/compute/snapshots/update index 78a7b2f5c..b70bd213a 100644 --- a/gcloud/beta/compute/snapshots/update +++ b/gcloud/beta/compute/snapshots/update @@ -4,11 +4,11 @@ NAME SYNOPSIS gcloud beta compute snapshots update SNAPSHOT_NAME [--update-labels=[KEY=VALUE,...]] - [--clear-labels | --remove-labels=[KEY,...]] [GCLOUD_WIDE_FLAG ...] + [--clear-labels | --remove-labels=[KEY,...]] + [--global | --region=REGION] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) gcloud beta compute snapshots update updates labels for a Compute - Engine snapshot. + (BETA) Update a Compute Engine snapshot. EXAMPLES To update labels k0 and k1 and remove labels with key k3, run: @@ -61,6 +61,15 @@ FLAGS silently ignored. If --update-labels is also specified then --update-labels is applied first. + At most one of these can be specified: + + --global + If set, the snapshot is global. + + --region=REGION + Region of the snapshot to update. Overrides the default + compute/region property value for this command invocation. + GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, diff --git a/gcloud/beta/dataflow/flex-template/build b/gcloud/beta/dataflow/flex-template/build index 10ac9e758..1c45ee13b 100644 --- a/gcloud/beta/dataflow/flex-template/build +++ b/gcloud/beta/dataflow/flex-template/build @@ -145,7 +145,8 @@ OPTIONAL FLAGS Default experiments to pass to the job. --additional-user-labels=[ADDITIONAL_USER_LABELS,...] - Default user labels to pass to the job. + Default user labels to pass to the job. Example: + --additional-user-labels='{"key1":"value1"}' --cloud-build-service-account=CLOUD_BUILD_SERVICE_ACCOUNT Service account to run the Cloud Build in the format diff --git a/gcloud/beta/dataflow/flex-template/run b/gcloud/beta/dataflow/flex-template/run index 9022adeab..7fd27c6f5 100644 --- a/gcloud/beta/dataflow/flex-template/run +++ b/gcloud/beta/dataflow/flex-template/run @@ -46,7 +46,8 @@ OPTIONAL FLAGS Additional experiments to pass to the job. --additional-user-labels=[ADDITIONAL_USER_LABELS,...] - Additional user labels to pass to the job. + Additional user labels to pass to the job. Example: + --additional-user-labels='{"key1":"value1"}' --dataflow-kms-key=DATAFLOW_KMS_KEY Cloud KMS key to protect the job resources. diff --git a/gcloud/beta/dataproc/batches/submit/help b/gcloud/beta/dataproc/batches/submit/help index f05fa956d..1a85c74a1 100644 --- a/gcloud/beta/dataproc/batches/submit/help +++ b/gcloud/beta/dataproc/batches/submit/help @@ -38,12 +38,6 @@ EXAMPLES 'my-sql-script.sql' --region='us-central1' \ --deps-bucket=gs://my-bucket --vars='variable=value' - To submit a Ray job, run: - - $ gcloud beta dataproc batches submit ray my-ray.py \ - --location='us-central1' --deps-bucket=gs://my-bucket -- ARG1 \ - ARG2 - FLAGS --async Return immediately without waiting for the operation in progress to diff --git a/gcloud/beta/developer-connect/connections/create b/gcloud/beta/developer-connect/connections/create index c5f946365..641dce5b9 100644 --- a/gcloud/beta/developer-connect/connections/create +++ b/gcloud/beta/developer-connect/connections/create @@ -5,9 +5,8 @@ NAME SYNOPSIS gcloud beta developer-connect connections create CONNECTION [--annotations=[ANNOTATIONS,...]] [--async] [--disabled] [--etag=ETAG] - [--git-proxy-config-enabled] [--labels=[LABELS,...]] - [--location=LOCATION] [--namespace=NAMESPACE] [--request-id=REQUEST_ID] - [--secret=SECRET] [--validate-only] + [--labels=[LABELS,...]] [--location=LOCATION] [--namespace=NAMESPACE] + [--request-id=REQUEST_ID] [--secret=SECRET] [--validate-only] [--bitbucket-cloud-config-authorizer-credential-user-token-secret-version=BITBUCKET_CLOUD_CONFIG_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION --bitbucket-cloud-config-read-authorizer-credential-user-token-secret-version=BITBUCKET_CLOUD_CONFIG_READ_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION --bitbucket-cloud-config-webhook-secret-version=BITBUCKET_CLOUD_CONFIG_WEBHOOK_SECRET_VERSION --bitbucket-cloud-config-workspace=BITBUCKET_CLOUD_CONFIG_WORKSPACE | [--bitbucket-data-center-config-authorizer-credential-user-token-secret-version=BITBUCKET_DATA_CENTER_CONFIG_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION --bitbucket-data-center-config-host-uri=BITBUCKET_DATA_CENTER_CONFIG_HOST_URI --bitbucket-data-center-config-read-authorizer-credential-user-token-secret-version=BITBUCKET_DATA_CENTER_CONFIG_READ_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION --bitbucket-data-center-config-webhook-secret-version=BITBUCKET_DATA_CENTER_CONFIG_WEBHOOK_SECRET_VERSION : --bitbucket-data-center-config-service-directory=BITBUCKET_DATA_CENTER_CONFIG_SERVICE_DIRECTORY --bitbucket-data-center-config-ssl-ca-certificate=BITBUCKET_DATA_CENTER_CONFIG_SSL_CA_CERTIFICATE] | [--github-config-app=GITHUB_CONFIG_APP : --github-config-app-installation-id=GITHUB_CONFIG_APP_INSTALLATION_ID --github-config-authorizer-credential-oauth-token-secret-version=GITHUB_CONFIG_AUTHORIZER_CREDENTIAL_OAUTH_TOKEN_SECRET_VERSION] | [--github-enterprise-config-host-uri=GITHUB_ENTERPRISE_CONFIG_HOST_URI : --github-enterprise-config-app-id=GITHUB_ENTERPRISE_CONFIG_APP_ID --github-enterprise-config-app-installation-id=GITHUB_ENTERPRISE_CONFIG_APP_INSTALLATION_ID --github-enterprise-config-private-key-secret-version=GITHUB_ENTERPRISE_CONFIG_PRIVATE_KEY_SECRET_VERSION --github-enterprise-config-service-directory=GITHUB_ENTERPRISE_CONFIG_SERVICE_DIRECTORY --github-enterprise-config-ssl-ca-certificate=GITHUB_ENTERPRISE_CONFIG_SSL_CA_CERTIFICATE --github-enterprise-config-webhook-secret-version=GITHUB_ENTERPRISE_CONFIG_WEBHOOK_SECRET_VERSION] | --gitlab-config-authorizer-credential-user-token-secret-version=GITLAB_CONFIG_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION --gitlab-config-read-authorizer-credential-user-token-secret-version=GITLAB_CONFIG_READ_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION --gitlab-config-webhook-secret-version=GITLAB_CONFIG_WEBHOOK_SECRET_VERSION | [--gitlab-enterprise-config-authorizer-credential-user-token-secret-version=GITLAB_ENTERPRISE_CONFIG_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION --gitlab-enterprise-config-host-uri=GITLAB_ENTERPRISE_CONFIG_HOST_URI --gitlab-enterprise-config-read-authorizer-credential-user-token-secret-version=GITLAB_ENTERPRISE_CONFIG_READ_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION --gitlab-enterprise-config-webhook-secret-version=GITLAB_ENTERPRISE_CONFIG_WEBHOOK_SECRET_VERSION : --gitlab-enterprise-config-service-directory=GITLAB_ENTERPRISE_CONFIG_SERVICE_DIRECTORY --gitlab-enterprise-config-ssl-ca-certificate=GITLAB_ENTERPRISE_CONFIG_SSL_CA_CERTIFICATE]] [(--crypto-key-config-reference=CRYPTO_KEY_CONFIG_REFERENCE : --key-ring=KEY_RING)] [GCLOUD_WIDE_FLAG ...] @@ -87,12 +86,6 @@ FLAGS fields, and may be sent on update and delete requests to ensure the client has an up-to-date value before proceeding. - The git proxy configuration. - - --git-proxy-config-enabled - Setting this to true allows the git proxy to be used for performing - git operations on the repositories linked in the connection. - --labels=[LABELS,...] Labels as key value pairs. diff --git a/gcloud/beta/developer-connect/connections/git-repository-links/delete b/gcloud/beta/developer-connect/connections/git-repository-links/delete index d2cec11dc..0e7bf6443 100644 --- a/gcloud/beta/developer-connect/connections/git-repository-links/delete +++ b/gcloud/beta/developer-connect/connections/git-repository-links/delete @@ -13,7 +13,7 @@ DESCRIPTION EXAMPLES To delete a git repository link my-git-repository-link in a connection - my-comection in location us-central1 run: + my-connection in location us-central1 run: $ gcloud beta developer-connect connections git-repository-links \ delete my-git-repository-link --connection=my-connection \ --location=us-central1 diff --git a/gcloud/beta/developer-connect/connections/update b/gcloud/beta/developer-connect/connections/update index 846ef70f4..a8e69d945 100644 --- a/gcloud/beta/developer-connect/connections/update +++ b/gcloud/beta/developer-connect/connections/update @@ -10,10 +10,10 @@ SYNOPSIS [--annotations=[ANNOTATIONS,...] | --update-annotations=[UPDATE_ANNOTATIONS,...] --clear-annotations | --remove-annotations=[__REMOVE_ANNOTATIONS,...]] - [--bitbucket-cloud-config-authorizer-credential-user-token-secret-version=BITBUCKET_CLOUD_CONFIG_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION --bitbucket-cloud-config-read-authorizer-credential-user-token-secret-version=BITBUCKET_CLOUD_CONFIG_READ_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION --bitbucket-cloud-config-workspace=BITBUCKET_CLOUD_CONFIG_WORKSPACE | --bitbucket-data-center-config-authorizer-credential-user-token-secret-version=BITBUCKET_DATA_CENTER_CONFIG_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION --bitbucket-data-center-config-host-uri=BITBUCKET_DATA_CENTER_CONFIG_HOST_URI --bitbucket-data-center-config-read-authorizer-credential-user-token-secret-version=BITBUCKET_DATA_CENTER_CONFIG_READ_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION --bitbucket-data-center-config-service-directory=BITBUCKET_DATA_CENTER_CONFIG_SERVICE_DIRECTORY --bitbucket-data-center-config-ssl-ca-certificate=BITBUCKET_DATA_CENTER_CONFIG_SSL_CA_CERTIFICATE | --github-config-app-installation-id=GITHUB_CONFIG_APP_INSTALLATION_ID --github-config-authorizer-credential-oauth-token-secret-version=GITHUB_CONFIG_AUTHORIZER_CREDENTIAL_OAUTH_TOKEN_SECRET_VERSION | --github-enterprise-config-app-id=GITHUB_ENTERPRISE_CONFIG_APP_ID --github-enterprise-config-app-installation-id=GITHUB_ENTERPRISE_CONFIG_APP_INSTALLATION_ID --github-enterprise-config-host-uri=GITHUB_ENTERPRISE_CONFIG_HOST_URI --github-enterprise-config-service-directory=GITHUB_ENTERPRISE_CONFIG_SERVICE_DIRECTORY --github-enterprise-config-ssl-ca-certificate=GITHUB_ENTERPRISE_CONFIG_SSL_CA_CERTIFICATE --clear-github-enterprise-config-private-key-secret-version | --github-enterprise-config-private-key-secret-version=GITHUB_ENTERPRISE_CONFIG_PRIVATE_KEY_SECRET_VERSION --clear-github-enterprise-config-webhook-secret-version | --github-enterprise-config-webhook-secret-version=GITHUB_ENTERPRISE_CONFIG_WEBHOOK_SECRET_VERSION | --gitlab-config-authorizer-credential-user-token-secret-version=GITLAB_CONFIG_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION --gitlab-config-read-authorizer-credential-user-token-secret-version=GITLAB_CONFIG_READ_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION | --gitlab-enterprise-config-authorizer-credential-user-token-secret-version=GITLAB_ENTERPRISE_CONFIG_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION --gitlab-enterprise-config-host-uri=GITLAB_ENTERPRISE_CONFIG_HOST_URI --gitlab-enterprise-config-read-authorizer-credential-user-token-secret-version=GITLAB_ENTERPRISE_CONFIG_READ_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION --gitlab-enterprise-config-service-directory=GITLAB_ENTERPRISE_CONFIG_SERVICE_DIRECTORY --gitlab-enterprise-config-ssl-ca-certificate=GITLAB_ENTERPRISE_CONFIG_SSL_CA_CERTIFICATE] - [--clear-git-proxy-config --[no-]git-proxy-config-enabled] - [--crypto-key-config-reference=CRYPTO_KEY_CONFIG_REFERENCE - : --key-ring=KEY_RING] + [--bitbucket-cloud-config-authorizer-credential-user-token-secret-version=BITBUCKET_CLOUD_CONFIG_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION --bitbucket-cloud-config-read-authorizer-credential-user-token-secret-version=BITBUCKET_CLOUD_CONFIG_READ_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION --bitbucket-cloud-config-workspace=BITBUCKET_CLOUD_CONFIG_WORKSPACE --clear-bitbucket-cloud-config | --bitbucket-data-center-config-authorizer-credential-user-token-secret-version=BITBUCKET_DATA_CENTER_CONFIG_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION --bitbucket-data-center-config-host-uri=BITBUCKET_DATA_CENTER_CONFIG_HOST_URI --bitbucket-data-center-config-read-authorizer-credential-user-token-secret-version=BITBUCKET_DATA_CENTER_CONFIG_READ_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION --bitbucket-data-center-config-service-directory=BITBUCKET_DATA_CENTER_CONFIG_SERVICE_DIRECTORY --bitbucket-data-center-config-ssl-ca-certificate=BITBUCKET_DATA_CENTER_CONFIG_SSL_CA_CERTIFICATE --clear-bitbucket-data-center-config | --clear-github-config --github-config-app-installation-id=GITHUB_CONFIG_APP_INSTALLATION_ID --github-config-authorizer-credential-oauth-token-secret-version=GITHUB_CONFIG_AUTHORIZER_CREDENTIAL_OAUTH_TOKEN_SECRET_VERSION | --clear-github-enterprise-config --github-enterprise-config-app-id=GITHUB_ENTERPRISE_CONFIG_APP_ID --github-enterprise-config-app-installation-id=GITHUB_ENTERPRISE_CONFIG_APP_INSTALLATION_ID --github-enterprise-config-host-uri=GITHUB_ENTERPRISE_CONFIG_HOST_URI --github-enterprise-config-service-directory=GITHUB_ENTERPRISE_CONFIG_SERVICE_DIRECTORY --github-enterprise-config-ssl-ca-certificate=GITHUB_ENTERPRISE_CONFIG_SSL_CA_CERTIFICATE --clear-github-enterprise-config-private-key-secret-version | --github-enterprise-config-private-key-secret-version=GITHUB_ENTERPRISE_CONFIG_PRIVATE_KEY_SECRET_VERSION --clear-github-enterprise-config-webhook-secret-version | --github-enterprise-config-webhook-secret-version=GITHUB_ENTERPRISE_CONFIG_WEBHOOK_SECRET_VERSION | --clear-gitlab-config --gitlab-config-authorizer-credential-user-token-secret-version=GITLAB_CONFIG_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION --gitlab-config-read-authorizer-credential-user-token-secret-version=GITLAB_CONFIG_READ_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION | --clear-gitlab-enterprise-config --gitlab-enterprise-config-authorizer-credential-user-token-secret-version=GITLAB_ENTERPRISE_CONFIG_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION --gitlab-enterprise-config-host-uri=GITLAB_ENTERPRISE_CONFIG_HOST_URI --gitlab-enterprise-config-read-authorizer-credential-user-token-secret-version=GITLAB_ENTERPRISE_CONFIG_READ_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION --gitlab-enterprise-config-service-directory=GITLAB_ENTERPRISE_CONFIG_SERVICE_DIRECTORY --gitlab-enterprise-config-ssl-ca-certificate=GITLAB_ENTERPRISE_CONFIG_SSL_CA_CERTIFICATE] + [--clear-crypto-key-config + [--crypto-key-config-reference=CRYPTO_KEY_CONFIG_REFERENCE + : --key-ring=KEY_RING]] [--labels=[LABELS,...] | --update-labels=[UPDATE_LABELS,...] --clear-labels | --remove-labels=[__REMOVE_LABELS,...]] [GCLOUD_WIDE_FLAG ...] @@ -241,6 +241,9 @@ FLAGS The Bitbucket Cloud Workspace ID to be connected to Google Cloud Platform. + --clear-bitbucket-cloud-config + Set connection.bitbucketCloudConfig back to default value. + Configuration for connections to an instance of Bitbucket Data Center. Represents a personal access token that authorized the Connection, and @@ -348,8 +351,14 @@ FLAGS SSL certificate authority to trust when making requests to Bitbucket Data Center. + --clear-bitbucket-data-center-config + Set connection.bitbucketDataCenterConfig back to default value. + Configuration for connections to github.com. + --clear-github-config + Set connection.githubConfig back to default value. + --github-config-app-installation-id=GITHUB_CONFIG_APP_INSTALLATION_ID GitHub App installation id. @@ -386,6 +395,9 @@ FLAGS Configuration for connections to an instance of GitHub Enterprise. + --clear-github-enterprise-config + Set connection.githubEnterpriseConfig back to default value. + --github-enterprise-config-app-id=GITHUB_ENTERPRISE_CONFIG_APP_ID ID of the GitHub App created from the manifest. @@ -512,6 +524,9 @@ FLAGS Configuration for connections to gitlab.com. + --clear-gitlab-config + Set connection.gitlabConfig back to default value. + Represents a personal access token that authorized the Connection, and associated metadata. @@ -576,6 +591,9 @@ FLAGS Configuration for connections to an instance of GitLab Enterprise. + --clear-gitlab-enterprise-config + Set connection.gitlabEnterpriseConfig back to default value. + Represents a personal access token that authorized the Connection, and associated metadata. @@ -681,20 +699,12 @@ FLAGS SSL Certificate Authority certificate to use for requests to GitLab Enterprise instance. - The git proxy configuration. - - --clear-git-proxy-config - Set connection.gitProxyConfig back to default value. - - --[no-]git-proxy-config-enabled - Setting this to true allows the git proxy to be used for performing - git operations on the repositories linked in the connection. Use - --git-proxy-config-enabled to enable and - --no-git-proxy-config-enabled to disable. - The crypto key configuration. This field is used by the Customer-managed encryption keys (CMEK) feature. + --clear-crypto-key-config + Set connection.cryptoKeyConfig back to default value. + CryptoKey resource - The name of the key which is used to encrypt/decrypt customer data. For key in Cloud KMS, the key should be in the format of projects/*/locations/*/keyRings/*/cryptoKeys/*. The diff --git a/gcloud/beta/filestore/instances/promote-replica b/gcloud/beta/filestore/instances/promote-replica index 2f1335b20..5c1df0b05 100644 --- a/gcloud/beta/filestore/instances/promote-replica +++ b/gcloud/beta/filestore/instances/promote-replica @@ -4,22 +4,39 @@ NAME SYNOPSIS gcloud beta filestore instances promote-replica (INSTANCE : --zone=ZONE) - [--async] [--location=LOCATION] [GCLOUD_WIDE_FLAG ...] + [--async] [--location=LOCATION] [--peer-instance=PEER_INSTANCE] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) Promote a Filestore standby replication instance to a regular - instance. + instance. This command can be called directly on the standby instance or on + the active instance with the standby peer instance parameter. When used on + the standby instance promotes the standby instance to a regular instance + even if the active instance is unavailable. When used on the active + instance detaches the standby instance from the active instance even if the + standby instance is unavailable. This command can fail for the following reasons: ▪ The target instance does not exist. ▪ The instance is not a standby replication member. + ▪ The instance is an active instance and the peer instance parameter is + missing or invalid. EXAMPLES - To promote an instance with the name my-instance that's located in + To promote a standby instance with the name my-replica-instance located in us-central1, run: - $ gcloud beta filestore instances promote-replica my-instance \ - --zone=us-central1 + $ gcloud beta filestore instances promote-replica \ + my-replica-instance --zone=us-central1 + + To promote a standby instance with the name my-replica-instance located in + us-central1, attached to the active peer instance my-active-instance + located in us-west1, run: + + $ gcloud beta filestore instances promote-replica \ + my-active-instance --zone=us-west1 \ + --peer-instance=projects/my-project/locations/us-central1/\ + instances/my-replica-instance POSITIONAL ARGUMENTS Instance resource - Arguments and flags that specify the Filestore @@ -62,6 +79,9 @@ FLAGS --location=LOCATION Location of the Filestore instance to promote. + --peer-instance=PEER_INSTANCE + The name of the standby peer instance to promote. + GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, diff --git a/gcloud/beta/iap/settings/get b/gcloud/beta/iap/settings/get index 638ed9880..cc27e9073 100644 --- a/gcloud/beta/iap/settings/get +++ b/gcloud/beta/iap/settings/get @@ -93,13 +93,15 @@ FLAGS --region=REGION Region name. Not applicable for app-engine. Required when resource-type=compute and regional scoped. Not applicable for global - scoped compute. + scoped compute. Required when resource-type=cloud-run. --resource-type=RESOURCE_TYPE Resource type of the IAP resource. For Backend Services, you can use - both compute and backend-services as resource type. RESOURCE_TYPE must - be one of: app-engine, iap_web, compute, organization, folder, - backend-services, forwarding-rule. + both compute and backend-services as resource type. + --resource-type=cloud-run is in private preview and reach out to IAP + team in case of any queries. RESOURCE_TYPE must be one of: app-engine, + iap_web, compute, organization, folder, forwarding-rule, cloud-run, + backend-services. --service=SERVICE Service name. Optional when resource-type is compute or app-engine. diff --git a/gcloud/beta/iap/settings/set b/gcloud/beta/iap/settings/set index 0cc7b238f..81e51e8e1 100644 --- a/gcloud/beta/iap/settings/set +++ b/gcloud/beta/iap/settings/set @@ -143,13 +143,15 @@ FLAGS --region=REGION Region name. Not applicable for app-engine. Required when resource-type=compute and regional scoped. Not applicable for global - scoped compute. + scoped compute. Required when resource-type=cloud-run. --resource-type=RESOURCE_TYPE Resource type of the IAP resource. For Backend Services, you can use - both compute and backend-services as resource type. RESOURCE_TYPE must - be one of: app-engine, iap_web, compute, organization, folder, - backend-services, forwarding-rule. + both compute and backend-services as resource type. + --resource-type=cloud-run is in private preview and reach out to IAP + team in case of any queries. RESOURCE_TYPE must be one of: app-engine, + iap_web, compute, organization, folder, forwarding-rule, cloud-run, + backend-services. --service=SERVICE Service name. Optional when resource-type is compute or app-engine. diff --git a/gcloud/beta/iap/web/add-iam-policy-binding b/gcloud/beta/iap/web/add-iam-policy-binding index 65b9e8045..b5059c2c4 100644 --- a/gcloud/beta/iap/web/add-iam-policy-binding +++ b/gcloud/beta/iap/web/add-iam-policy-binding @@ -116,13 +116,15 @@ OPTIONAL FLAGS relative path to a local file containing the value of condition. --region=REGION - Region name. Should only be specified with - --resource-type=backend-services if it is a regional scoped. Not - applicable for global scoped backend services. + Region name. Not applicable for resource-type=app-engine. Required when + resource-type=backend-services and regional scoped. Not applicable for + global backend-services. Required when resource-type=cloud-run. --resource-type=RESOURCE_TYPE - Resource type of the IAP resource. RESOURCE_TYPE must be one of: - app-engine, backend-services, forwarding-rule. + Resource type of the IAP resource. --resource-type=cloud-run is in + private preview and reach out to IAP team in case of any queries. + RESOURCE_TYPE must be one of: app-engine, backend-services, + forwarding-rule, cloud-run. --service=SERVICE Service name. diff --git a/gcloud/beta/iap/web/get-iam-policy b/gcloud/beta/iap/web/get-iam-policy index 490d877c6..566b95447 100644 --- a/gcloud/beta/iap/web/get-iam-policy +++ b/gcloud/beta/iap/web/get-iam-policy @@ -64,13 +64,15 @@ EXAMPLES FLAGS --region=REGION - Region name. Should only be specified with - --resource-type=backend-services if it is a regional scoped. Not - applicable for global scoped backend services. + Region name. Not applicable for resource-type=app-engine. Required when + resource-type=backend-services and regional scoped. Not applicable for + global backend-services. Required when resource-type=cloud-run. --resource-type=RESOURCE_TYPE - Resource type of the IAP resource. RESOURCE_TYPE must be one of: - app-engine, backend-services, forwarding-rule. + Resource type of the IAP resource. --resource-type=cloud-run is in + private preview and reach out to IAP team in case of any queries. + RESOURCE_TYPE must be one of: app-engine, backend-services, + forwarding-rule, cloud-run. --service=SERVICE Service name. diff --git a/gcloud/beta/iap/web/remove-iam-policy-binding b/gcloud/beta/iap/web/remove-iam-policy-binding index 2bf4f309e..7ec937074 100644 --- a/gcloud/beta/iap/web/remove-iam-policy-binding +++ b/gcloud/beta/iap/web/remove-iam-policy-binding @@ -133,13 +133,15 @@ OPTIONAL FLAGS relative path to a local file containing the value of condition. --region=REGION - Region name. Should only be specified with - --resource-type=backend-services if it is a regional scoped. Not - applicable for global scoped backend services. + Region name. Not applicable for resource-type=app-engine. Required when + resource-type=backend-services and regional scoped. Not applicable for + global backend-services. Required when resource-type=cloud-run. --resource-type=RESOURCE_TYPE - Resource type of the IAP resource. RESOURCE_TYPE must be one of: - app-engine, backend-services, forwarding-rule. + Resource type of the IAP resource. --resource-type=cloud-run is in + private preview and reach out to IAP team in case of any queries. + RESOURCE_TYPE must be one of: app-engine, backend-services, + forwarding-rule, cloud-run. --service=SERVICE Service name. diff --git a/gcloud/beta/iap/web/set-iam-policy b/gcloud/beta/iap/web/set-iam-policy index ed5e89e97..ebaed6380 100644 --- a/gcloud/beta/iap/web/set-iam-policy +++ b/gcloud/beta/iap/web/set-iam-policy @@ -73,13 +73,15 @@ POSITIONAL ARGUMENTS FLAGS --region=REGION - Region name. Should only be specified with - --resource-type=backend-services if it is a regional scoped. Not - applicable for global scoped backend services. + Region name. Not applicable for resource-type=app-engine. Required when + resource-type=backend-services and regional scoped. Not applicable for + global backend-services. Required when resource-type=cloud-run. --resource-type=RESOURCE_TYPE - Resource type of the IAP resource. RESOURCE_TYPE must be one of: - app-engine, backend-services, forwarding-rule. + Resource type of the IAP resource. --resource-type=cloud-run is in + private preview and reach out to IAP team in case of any queries. + RESOURCE_TYPE must be one of: app-engine, backend-services, + forwarding-rule, cloud-run. --service=SERVICE Service name. diff --git a/gcloud/beta/managed-kafka/help b/gcloud/beta/managed-kafka/help index 40f07f265..3bafd1f8a 100644 --- a/gcloud/beta/managed-kafka/help +++ b/gcloud/beta/managed-kafka/help @@ -23,6 +23,9 @@ GROUPS consumer-groups (BETA) Administer Managed Service for Apache Kafka consumer groups. + operations + (BETA) View Managed Service for Apache Kafka operations. + topics (BETA) Administer Managed Service for Apache Kafka topics. diff --git a/gcloud/beta/managed-kafka/operations/describe b/gcloud/beta/managed-kafka/operations/describe new file mode 100644 index 000000000..ffa2d84cc --- /dev/null +++ b/gcloud/beta/managed-kafka/operations/describe @@ -0,0 +1,73 @@ +NAME + gcloud beta managed-kafka operations describe - describe a Managed Service + for Apache Kafka operation + +SYNOPSIS + gcloud beta managed-kafka operations describe + (OPERATION : --location=LOCATION) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Describe a Managed Service for Apache Kafka operation. + +EXAMPLES + To describe an operation named myoperation located in us-central1, run the + following: + + $ gcloud beta managed-kafka operations describe myoperation \ + --location=us-central1 + +POSITIONAL ARGUMENTS + Operation resource - Identifies the operation for details to be displayed. + 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 operation 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. + + OPERATION + ID of the operation or fully qualified identifier for the operation. + + To set the operation attribute: + ▸ provide the argument operation on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + ID of the location of the Managed Service for Apache Kafka resource. + See + https://cloud.google.com/managed-service-for-apache-kafka/docs/locations + for a list of supported locations. + + To set the location attribute: + ▸ provide the argument operation on the command line with a fully + specified name; + ▸ provide the argument --location 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 managedkafka/v1 API. The full documentation for this + API can be found at: + https://cloud.google.com/managed-service-for-apache-kafka/docs + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud managed-kafka operations describe + + $ gcloud alpha managed-kafka operations describe + diff --git a/gcloud/beta/managed-kafka/operations/help b/gcloud/beta/managed-kafka/operations/help new file mode 100644 index 000000000..0e7023799 --- /dev/null +++ b/gcloud/beta/managed-kafka/operations/help @@ -0,0 +1,33 @@ +NAME + gcloud beta managed-kafka operations - view Managed Service for Apache + Kafka operations + +SYNOPSIS + gcloud beta managed-kafka operations COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) View Managed Service for Apache Kafka operations. + +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) Describe a Managed Service for Apache Kafka operation. + + list + (BETA) List all Managed Service for Apache Kafka operations in a given + location. + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud managed-kafka operations + + $ gcloud alpha managed-kafka operations + diff --git a/gcloud/beta/managed-kafka/operations/list b/gcloud/beta/managed-kafka/operations/list new file mode 100644 index 000000000..0e7ad43d9 --- /dev/null +++ b/gcloud/beta/managed-kafka/operations/list @@ -0,0 +1,87 @@ +NAME + gcloud beta managed-kafka operations list - list all Managed Service for + Apache Kafka operations in a given location + +SYNOPSIS + gcloud beta managed-kafka operations list --location=LOCATION + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) List all Managed Service for Apache Kafka operations in a given + location. To specify the maximum number of operations to list, use the + --limit flag. + +EXAMPLES + To list all clusters in a given location, such as us-central1, run the + following: + + $ gcloud beta managed-kafka operations list --location=us-central1 + +REQUIRED FLAGS + Location resource - Identifies the region which contains all the + operations to be listed. 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; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + --location=LOCATION + ID of the location or fully qualified identifier for the location. + + To set the location attribute: + ▸ provide the argument --location on the command line. + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the managedkafka/v1 API. The full documentation for this + API can be found at: + https://cloud.google.com/managed-service-for-apache-kafka/docs + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud managed-kafka operations list + + $ gcloud alpha managed-kafka operations list + diff --git a/gcloud/beta/netapp/storage-pools/create b/gcloud/beta/netapp/storage-pools/create index 51ad99c84..473969db2 100644 --- a/gcloud/beta/netapp/storage-pools/create +++ b/gcloud/beta/netapp/storage-pools/create @@ -8,9 +8,12 @@ SYNOPSIS --network=[name=NAME],[psa-range=PSA-RANGE] --service-level=SERVICE_LEVEL [--active-directory=ACTIVE_DIRECTORY] [--allow-auto-tiering=ALLOW_AUTO_TIERING] [--async] + [--custom-performance-enabled=CUSTOM_PERFORMANCE_ENABLED] [--description=DESCRIPTION] [--enable-ldap=ENABLE_LDAP] [--kms-config=KMS_CONFIG] [--labels=[KEY=VALUE,...]] - [--replica-zone=REPLICA_ZONE] [--zone=ZONE] [GCLOUD_WIDE_FLAG ...] + [--replica-zone=REPLICA_ZONE] [--total-iops=TOTAL_IOPS] + [--total-throughput=TOTAL_THROUGHPUT] [--zone=ZONE] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) Creates a Storage Pool to contain Volumes with a specified Service @@ -145,6 +148,10 @@ OPTIONAL FLAGS Return immediately, without waiting for the operation in progress to complete. + --custom-performance-enabled=CUSTOM_PERFORMANCE_ENABLED + Boolean flag indicating whether Storage Pool is a custom performance + Storage Pool or not + --description=DESCRIPTION A description of the Cloud NetApp Storage Pool @@ -186,6 +193,13 @@ OPTIONAL FLAGS --replica-zone=REPLICA_ZONE String indicating replica zone for the Storage Pool + --total-iops=TOTAL_IOPS + Integer indicating total IOPS of the Storage Pool + + --total-throughput=TOTAL_THROUGHPUT + The total throughput of the Storage Pool in MiB/s or GiB/s units. If no + throughput unit is specified, MiB/s is assumed. + --zone=ZONE String indicating active zone of the Storage Pool diff --git a/gcloud/beta/netapp/storage-pools/update b/gcloud/beta/netapp/storage-pools/update index 288e72a11..9498ddeee 100644 --- a/gcloud/beta/netapp/storage-pools/update +++ b/gcloud/beta/netapp/storage-pools/update @@ -8,7 +8,8 @@ SYNOPSIS [--active-directory=ACTIVE_DIRECTORY] [--allow-auto-tiering=ALLOW_AUTO_TIERING] [--async] [--capacity=CAPACITY] [--description=DESCRIPTION] - [--replica-zone=REPLICA_ZONE] [--update-labels=[KEY=VALUE,...]] + [--replica-zone=REPLICA_ZONE] [--total-iops=TOTAL_IOPS] + [--total-throughput=TOTAL_THROUGHPUT] [--update-labels=[KEY=VALUE,...]] [--zone=ZONE] [--clear-labels | --remove-labels=[KEY,...]] [GCLOUD_WIDE_FLAG ...] @@ -98,6 +99,13 @@ FLAGS --replica-zone=REPLICA_ZONE String indicating replica zone for the Storage Pool + --total-iops=TOTAL_IOPS + Integer indicating total IOPS of the Storage Pool + + --total-throughput=TOTAL_THROUGHPUT + The total throughput of the Storage Pool in MiB/s or GiB/s units. If no + throughput unit is specified, MiB/s is assumed. + --update-labels=[KEY=VALUE,...] List of label KEY=VALUE pairs to update. If a label exists, its value is modified. Otherwise, a new label is created. diff --git a/gcloud/beta/network-services/multicast-group-ranges/create b/gcloud/beta/network-services/multicast-group-ranges/create index fbfd597d5..de8f474cd 100644 --- a/gcloud/beta/network-services/multicast-group-ranges/create +++ b/gcloud/beta/network-services/multicast-group-ranges/create @@ -8,9 +8,9 @@ SYNOPSIS --multicast-domain=MULTICAST_DOMAIN --reserved-internal-range=RESERVED_INTERNAL_RANGE [--async] [--consumer-accept-list=[CONSUMER_ACCEPT_LIST,...]] - [--description=DESCRIPTION] [--[no-]enable-logging] - [--labels=[KEY=VALUE,...]] [--require-explicit-accept] - [GCLOUD_WIDE_FLAG ...] + [--description=DESCRIPTION] [--distribution-scope=DISTRIBUTION_SCOPE] + [--[no-]enable-logging] [--labels=[KEY=VALUE,...]] + [--require-explicit-accept] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) Create a multicast group range in the specified location of the @@ -76,6 +76,11 @@ OPTIONAL FLAGS --description=DESCRIPTION The description for the multicast group range. + --distribution-scope=DISTRIBUTION_SCOPE + Distribution scope of this multicast group range. DISTRIBUTION_SCOPE + must be one of: distribution-scope-unspecified, intra-region, + intra-zone. + --[no-]enable-logging Whether to enable logging for this multicast group range. Use --enable-logging to enable and --no-enable-logging to disable. diff --git a/gcloud/beta/network-services/multicast-group-ranges/help b/gcloud/beta/network-services/multicast-group-ranges/help index d89b39702..e6874d6fc 100644 --- a/gcloud/beta/network-services/multicast-group-ranges/help +++ b/gcloud/beta/network-services/multicast-group-ranges/help @@ -29,6 +29,9 @@ COMMANDS list (BETA) List multicast group ranges. + update + (BETA) Update a multicast group range. + NOTES This command is currently in beta and might change without notice. This variant is also available: diff --git a/gcloud/beta/network-services/multicast-group-ranges/update b/gcloud/beta/network-services/multicast-group-ranges/update new file mode 100644 index 000000000..c58e4669f --- /dev/null +++ b/gcloud/beta/network-services/multicast-group-ranges/update @@ -0,0 +1,143 @@ +NAME + gcloud beta network-services multicast-group-ranges update - update a + multicast group range + +SYNOPSIS + gcloud beta network-services multicast-group-ranges update + (MULTICAST_GROUP_RANGE : --location=LOCATION) [--async] + [--description=DESCRIPTION] [--[no-]enable-logging] + [--[no-]require-explicit-accept] [--update-labels=[KEY=VALUE,...]] + [--clear-labels | --remove-labels=[KEY,...]] + [--consumer-accept-list=[CONSUMER_ACCEPT_LIST,...] + | --add-consumer-accept-list=[ADD_CONSUMER_ACCEPT_LIST,...] + --clear-consumer-accept-list + | --remove-consumer-accept-list=[REMOVE_CONSUMER_ACCEPT_LIST,...]] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Update a multicast group range in the specified location of the + current project. + +EXAMPLES + Update a multicast group range with the name 'my-multicast-group-range' and + location 'global'. + + $ gcloud beta network-services multicast-group-ranges update \ + my-multicast-group-range --require-explicit-accept \ + --enable-logging --location=global + +POSITIONAL ARGUMENTS + Multicast group range resource - Name of the multicast group range to be + updated. The arguments in this group can be used to specify the attributes + of this resource. (NOTE) Some attributes are not given arguments in this + group but can be set in other ways. + + To set the project attribute: + ◆ provide the argument multicast_group_range 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. + + MULTICAST_GROUP_RANGE + ID of the multicast group range or fully qualified identifier for the + multicast group range. + + To set the multicast_group_range attribute: + ▸ provide the argument multicast_group_range 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 Id. + + To set the location attribute: + ▸ provide the argument multicast_group_range on the command line + with a fully specified name; + ▸ provide the argument --location on the command line. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --description=DESCRIPTION + The description for the multicast group range. + + --[no-]enable-logging + Whether to enable logging for this multicast group range. Use + --enable-logging to enable and --no-enable-logging to disable. + + --[no-]require-explicit-accept + Whether an empty consumer accept list will reject all consumer + projects. Use --require-explicit-accept to enable and + --no-require-explicit-accept to disable. + + --update-labels=[KEY=VALUE,...] + List of label KEY=VALUE pairs to update. If a label exists, its value + is modified. Otherwise, a new label is created. + + Keys must start with a lowercase character and contain only hyphens + (-), underscores (_), lowercase characters, and numbers. Values must + contain only hyphens (-), underscores (_), lowercase characters, and + numbers. + + At most one of these can be specified: + + --clear-labels + Remove all labels. If --update-labels is also specified then + --clear-labels is applied first. + + For example, to remove all labels: + + $ gcloud beta network-services multicast-group-ranges update \ + --clear-labels + + To remove all existing labels and create two new labels, foo and baz: + + $ gcloud beta network-services multicast-group-ranges update \ + --clear-labels --update-labels foo=bar,baz=qux + + --remove-labels=[KEY,...] + List of label keys to remove. If a label does not exist it is + silently ignored. If --update-labels is also specified then + --update-labels is applied first. + + Update consumer_accept_list. + + At most one of these can be specified: + + --consumer-accept-list=[CONSUMER_ACCEPT_LIST,...] + Set consumer_accept_list to new value. + + --add-consumer-accept-list=[ADD_CONSUMER_ACCEPT_LIST,...] + Add new value to consumer_accept_list list. + + At most one of these can be specified: + + --clear-consumer-accept-list + Clear consumer_accept_list value and set to empty list. + + --remove-consumer-accept-list=[REMOVE_CONSUMER_ACCEPT_LIST,...] + Remove existing value from consumer_accept_list list. + +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 networkservices/v1beta1 API. The full documentation + for this API can be found at: https://cloud.google.com/networking + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha network-services multicast-group-ranges update + diff --git a/gcloud/beta/policy-intelligence/help b/gcloud/beta/policy-intelligence/help new file mode 100644 index 000000000..2b692a911 --- /dev/null +++ b/gcloud/beta/policy-intelligence/help @@ -0,0 +1,28 @@ +NAME + gcloud beta policy-intelligence - a platform to help better understand, + use, and manage policies at scale + +SYNOPSIS + gcloud beta policy-intelligence GROUP | COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) A platform to help better understand, use, and manage policies at + scale. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +GROUPS + GROUP is one of the following: + + simulate + (BETA) Simulate changes to organization policies. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud policy-intelligence + diff --git a/gcloud/beta/policy-intelligence/simulate/help b/gcloud/beta/policy-intelligence/simulate/help new file mode 100644 index 000000000..d8e60d219 --- /dev/null +++ b/gcloud/beta/policy-intelligence/simulate/help @@ -0,0 +1,25 @@ +NAME + gcloud beta policy-intelligence simulate - simulate changes to organization + policies + +SYNOPSIS + gcloud beta policy-intelligence simulate COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Simulate changes to organization policies. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + orgpolicy + (BETA) Understand how changes to organization policies could affect + your resources. + +NOTES + This command is currently in beta and might change without notice. + diff --git a/gcloud/beta/policy-intelligence/simulate/orgpolicy b/gcloud/beta/policy-intelligence/simulate/orgpolicy new file mode 100644 index 000000000..d46a8eb78 --- /dev/null +++ b/gcloud/beta/policy-intelligence/simulate/orgpolicy @@ -0,0 +1,66 @@ +NAME + gcloud beta policy-intelligence simulate orgpolicy - understand how changes + to organization policies could affect your resources + +SYNOPSIS + gcloud beta policy-intelligence simulate orgpolicy + --organization=ORGANIZATION_ID + [--custom-constraints=[CUSTOM_CONSTRAINTS,...]] + [--policies=[POLICIES,...]] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Understand how changes to organization policies could affect your + resources. + +EXAMPLES + To simulate changes to custom constraints defined in + ./custom-constraint.json, run: + + $ gcloud beta policy-intelligence simulate orgpolicy \ + --organization=ORGANIZATION_ID \ + --custom-constraints=custom-constraint.json + + To simulate changes to organization policies defined in ./policy.json, run: + + $ gcloud beta policy-intelligence simulate orgpolicy \ + --organization=ORGANIZATION_ID --policies=policy.json + + To simulate changes to both custom constraints defined in + ./custom-constraint.json and organization policies defined in + ./policy.json, run: + + $ gcloud beta policy-intelligence simulate orgpolicy \ + --organization=ORGANIZATION_ID --policies=policy.json \ + --custom-constraints=custom-constraint.json + + See + https://cloud.google.com/policy-intelligence/docs/test-organization-policies + for more information about Policy Simulator for Organization Policy. + +REQUIRED FLAGS + --organization=ORGANIZATION_ID + Organization ID. + +OPTIONAL FLAGS + --custom-constraints=[CUSTOM_CONSTRAINTS,...] + Path to the JSON or YAML file that contains the custom constraints to + simulate. Multiple custom constraints can be simulated by providing + multiple, comma-separated paths. For example: + --custom-constraints=constraint1.json,constraint2.json + + --policies=[POLICIES,...] + Path to the JSON or YAML file that contains the organization policy to + simulate. Multiple policies can be simulated by providing multiple, + comma-separated paths. For example: --policies=p1.json,p2.json + +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/run/deploy b/gcloud/beta/run/deploy index ed1d0929c..249274b58 100644 --- a/gcloud/beta/run/deploy +++ b/gcloud/beta/run/deploy @@ -144,6 +144,9 @@ FLAGS Specifies a container by name. Flags following --container will apply to the specified container. + Flags that are not container-specific must be specified before + --container. + --[no-]cpu-boost Whether to allocate extra CPU to containers on startup to reduce the perceived latency of a cold start request. Enabled by default when @@ -390,8 +393,9 @@ FLAGS Container Flags - The following flags apply to a single container. If the --container flag is specified these flags may only be - specified after a --container flag. Otherwise they will apply to the primary ingress container. + The following flags apply to a single container. If the --container flag is + specified these flags may only be specified after a --container flag. + Otherwise they will apply to the primary ingress container. --add-volume-mount=[volume=NAME,mount-path=MOUNT_PATH,...] Adds a mount to the current container. Must contain the keys diff --git a/gcloud/beta/run/jobs/create b/gcloud/beta/run/jobs/create index bc539f6d5..8e107a619 100644 --- a/gcloud/beta/run/jobs/create +++ b/gcloud/beta/run/jobs/create @@ -75,6 +75,9 @@ FLAGS Specifies a container by name. Flags following --container will apply to the specified container. + Flags that are not container-specific must be specified before + --container. + --key=KEY CMEK key reference to encrypt the container with. diff --git a/gcloud/beta/run/jobs/deploy b/gcloud/beta/run/jobs/deploy index 5ff81815a..39e3ccfe1 100644 --- a/gcloud/beta/run/jobs/deploy +++ b/gcloud/beta/run/jobs/deploy @@ -77,6 +77,9 @@ FLAGS Specifies a container by name. Flags following --container will apply to the specified container. + Flags that are not container-specific must be specified before + --container. + --key=KEY CMEK key reference to encrypt the container with. diff --git a/gcloud/beta/run/jobs/execute b/gcloud/beta/run/jobs/execute index 2aad0c541..4afcbf94c 100644 --- a/gcloud/beta/run/jobs/execute +++ b/gcloud/beta/run/jobs/execute @@ -40,6 +40,9 @@ FLAGS Specifies a container by name. Flags following --container will apply to the specified container. + Flags that are not container-specific must be specified before + --container. + --region=REGION Region in which the resource can be found. Alternatively, set the property [run/region]. diff --git a/gcloud/beta/run/jobs/update b/gcloud/beta/run/jobs/update index 434ef2fe5..1eb485402 100644 --- a/gcloud/beta/run/jobs/update +++ b/gcloud/beta/run/jobs/update @@ -76,6 +76,9 @@ FLAGS Specifies a container by name. Flags following --container will apply to the specified container. + Flags that are not container-specific must be specified before + --container. + --key=KEY CMEK key reference to encrypt the container with. diff --git a/gcloud/beta/run/multi-region-services/update b/gcloud/beta/run/multi-region-services/update index af7c04c8b..f3def3d9f 100644 --- a/gcloud/beta/run/multi-region-services/update +++ b/gcloud/beta/run/multi-region-services/update @@ -115,6 +115,9 @@ FLAGS Specifies a container by name. Flags following --container will apply to the specified container. + Flags that are not container-specific must be specified before + --container. + --[no-]cpu-boost Whether to allocate extra CPU to containers on startup to reduce the perceived latency of a cold start request. Enabled by default when diff --git a/gcloud/beta/run/services/update b/gcloud/beta/run/services/update index 1fc437a95..37c405d39 100644 --- a/gcloud/beta/run/services/update +++ b/gcloud/beta/run/services/update @@ -115,6 +115,9 @@ FLAGS Specifies a container by name. Flags following --container will apply to the specified container. + Flags that are not container-specific must be specified before + --container. + --[no-]cpu-boost Whether to allocate extra CPU to containers on startup to reduce the perceived latency of a cold start request. Enabled by default when diff --git a/gcloud/compute/commitments/create b/gcloud/compute/commitments/create index bad6b47dc..a8e29ffd8 100644 --- a/gcloud/compute/commitments/create +++ b/gcloud/compute/commitments/create @@ -109,8 +109,9 @@ OPTIONAL FLAGS general-purpose-c4a, general-purpose-e2, general-purpose-n2, general-purpose-n2d, general-purpose-n4, general-purpose-t2d, graphics-optimized, memory-optimized, memory-optimized-m3, - memory-optimized-x4-16tb, memory-optimized-x4-24tb, - memory-optimized-x4-32tb, storage-optimized-z3. + memory-optimized-m4, memory-optimized-x4-16tb, + memory-optimized-x4-24tb, memory-optimized-x4-32tb, + storage-optimized-z3. Manage the reservations to be created with the commitment. diff --git a/gcloud/compute/reservations/create b/gcloud/compute/reservations/create index a22d8e88a..227039d00 100644 --- a/gcloud/compute/reservations/create +++ b/gcloud/compute/reservations/create @@ -10,7 +10,8 @@ SYNOPSIS --local-ssd=[interface=INTERFACE],[size=SIZE] --min-cpu-platform=MIN_CPU_PLATFORM]) : --require-specific-reservation --resource-policies=[KEY=VALUE,...]) - [--description=DESCRIPTION] [--zone=ZONE] + [--description=DESCRIPTION] + [--reservation-sharing-policy=RESERVATION_SHARING_POLICY] [--zone=ZONE] [--share-setting=SHARE_SETTING --share-with=SHARE_WITH,[SHARE_WITH,...]] [GCLOUD_WIDE_FLAG ...] @@ -114,6 +115,16 @@ OPTIONAL FLAGS --description=DESCRIPTION An optional description of the reservation to create. + --reservation-sharing-policy=RESERVATION_SHARING_POLICY + The reservation sharing policy to use for this reservation. + RESERVATION_SHARING_POLICY must be one of: + + ALLOW_ALL + The reservation can be shared with Google Cloud services. + DISALLOW_ALL + The reservation won't be shared with Google Cloud services. If you + omit this flag during creation, the default value is DISALLOW_ALL. + --zone=ZONE Zone of the reservation to create. If not specified and the compute/zone property isn't set, you might be prompted to select a zone diff --git a/gcloud/compute/reservations/update b/gcloud/compute/reservations/update index d6cf4961d..a89703475 100644 --- a/gcloud/compute/reservations/update +++ b/gcloud/compute/reservations/update @@ -4,8 +4,9 @@ NAME SYNOPSIS gcloud compute reservations update RESERVATION [--add-share-with=PROJECT,[PROJECT,...]] - [--remove-share-with=PROJECT,[PROJECT,...]] [--vm-count=VM_COUNT] - [--zone=ZONE] [GCLOUD_WIDE_FLAG ...] + [--remove-share-with=PROJECT,[PROJECT,...]] + [--reservation-sharing-policy=RESERVATION_SHARING_POLICY] + [--vm-count=VM_COUNT] [--zone=ZONE] [GCLOUD_WIDE_FLAG ...] DESCRIPTION Update Compute Engine reservations. @@ -48,6 +49,16 @@ FLAGS this reservation is shared with. List must contain project IDs or project numbers. + --reservation-sharing-policy=RESERVATION_SHARING_POLICY + The reservation sharing policy to use for this reservation. + RESERVATION_SHARING_POLICY must be one of: + + ALLOW_ALL + The reservation can be shared with Google Cloud services. + DISALLOW_ALL + The reservation won't be shared with Google Cloud services. If you + omit this flag during creation, the default value is DISALLOW_ALL. + --vm-count=VM_COUNT The number of VM instances that are allocated to this reservation. The value of this field must be an int in the range [1, 1000]. diff --git a/gcloud/dataflow/flex-template/build b/gcloud/dataflow/flex-template/build index a7787742a..8bb82320c 100644 --- a/gcloud/dataflow/flex-template/build +++ b/gcloud/dataflow/flex-template/build @@ -143,7 +143,8 @@ OPTIONAL FLAGS Default experiments to pass to the job. --additional-user-labels=[ADDITIONAL_USER_LABELS,...] - Default user labels to pass to the job. + Default user labels to pass to the job. Example: + --additional-user-labels='{"key1":"value1"}' --cloud-build-service-account=CLOUD_BUILD_SERVICE_ACCOUNT Service account to run the Cloud Build in the format diff --git a/gcloud/dataflow/flex-template/run b/gcloud/dataflow/flex-template/run index 095148681..ebd3189bb 100644 --- a/gcloud/dataflow/flex-template/run +++ b/gcloud/dataflow/flex-template/run @@ -46,7 +46,8 @@ OPTIONAL FLAGS Additional experiments to pass to the job. --additional-user-labels=[ADDITIONAL_USER_LABELS,...] - Additional user labels to pass to the job. + Additional user labels to pass to the job. Example: + --additional-user-labels='{"key1":"value1"}' --dataflow-kms-key=DATAFLOW_KMS_KEY Cloud KMS key to protect the job resources. diff --git a/gcloud/dataproc/batches/submit/help b/gcloud/dataproc/batches/submit/help index 7d9be4483..e3fe35646 100644 --- a/gcloud/dataproc/batches/submit/help +++ b/gcloud/dataproc/batches/submit/help @@ -38,12 +38,6 @@ EXAMPLES --region='us-central1' --deps-bucket=gs://my-bucket \ --vars='variable=value' - To submit a Ray job, run: - - $ gcloud dataproc batches submit ray my-ray.py \ - --location='us-central1' --deps-bucket=gs://my-bucket -- ARG1 \ - ARG2 - FLAGS --async Return immediately without waiting for the operation in progress to diff --git a/gcloud/developer-connect/connections/create b/gcloud/developer-connect/connections/create index 66a2999f7..1c2438454 100644 --- a/gcloud/developer-connect/connections/create +++ b/gcloud/developer-connect/connections/create @@ -4,9 +4,8 @@ NAME SYNOPSIS gcloud developer-connect connections create CONNECTION [--annotations=[ANNOTATIONS,...]] [--async] [--disabled] [--etag=ETAG] - [--git-proxy-config-enabled] [--labels=[LABELS,...]] - [--location=LOCATION] [--namespace=NAMESPACE] [--request-id=REQUEST_ID] - [--secret=SECRET] [--validate-only] + [--labels=[LABELS,...]] [--location=LOCATION] [--namespace=NAMESPACE] + [--request-id=REQUEST_ID] [--secret=SECRET] [--validate-only] [--bitbucket-cloud-config-authorizer-credential-user-token-secret-version=BITBUCKET_CLOUD_CONFIG_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION --bitbucket-cloud-config-read-authorizer-credential-user-token-secret-version=BITBUCKET_CLOUD_CONFIG_READ_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION --bitbucket-cloud-config-webhook-secret-version=BITBUCKET_CLOUD_CONFIG_WEBHOOK_SECRET_VERSION --bitbucket-cloud-config-workspace=BITBUCKET_CLOUD_CONFIG_WORKSPACE | [--bitbucket-data-center-config-authorizer-credential-user-token-secret-version=BITBUCKET_DATA_CENTER_CONFIG_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION --bitbucket-data-center-config-host-uri=BITBUCKET_DATA_CENTER_CONFIG_HOST_URI --bitbucket-data-center-config-read-authorizer-credential-user-token-secret-version=BITBUCKET_DATA_CENTER_CONFIG_READ_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION --bitbucket-data-center-config-webhook-secret-version=BITBUCKET_DATA_CENTER_CONFIG_WEBHOOK_SECRET_VERSION : --bitbucket-data-center-config-service-directory=BITBUCKET_DATA_CENTER_CONFIG_SERVICE_DIRECTORY --bitbucket-data-center-config-ssl-ca-certificate=BITBUCKET_DATA_CENTER_CONFIG_SSL_CA_CERTIFICATE] | [--github-config-app=GITHUB_CONFIG_APP : --github-config-app-installation-id=GITHUB_CONFIG_APP_INSTALLATION_ID --github-config-authorizer-credential-oauth-token-secret-version=GITHUB_CONFIG_AUTHORIZER_CREDENTIAL_OAUTH_TOKEN_SECRET_VERSION] | [--github-enterprise-config-host-uri=GITHUB_ENTERPRISE_CONFIG_HOST_URI : --github-enterprise-config-app-id=GITHUB_ENTERPRISE_CONFIG_APP_ID --github-enterprise-config-app-installation-id=GITHUB_ENTERPRISE_CONFIG_APP_INSTALLATION_ID --github-enterprise-config-private-key-secret-version=GITHUB_ENTERPRISE_CONFIG_PRIVATE_KEY_SECRET_VERSION --github-enterprise-config-service-directory=GITHUB_ENTERPRISE_CONFIG_SERVICE_DIRECTORY --github-enterprise-config-ssl-ca-certificate=GITHUB_ENTERPRISE_CONFIG_SSL_CA_CERTIFICATE --github-enterprise-config-webhook-secret-version=GITHUB_ENTERPRISE_CONFIG_WEBHOOK_SECRET_VERSION] | --gitlab-config-authorizer-credential-user-token-secret-version=GITLAB_CONFIG_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION --gitlab-config-read-authorizer-credential-user-token-secret-version=GITLAB_CONFIG_READ_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION --gitlab-config-webhook-secret-version=GITLAB_CONFIG_WEBHOOK_SECRET_VERSION | [--gitlab-enterprise-config-authorizer-credential-user-token-secret-version=GITLAB_ENTERPRISE_CONFIG_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION --gitlab-enterprise-config-host-uri=GITLAB_ENTERPRISE_CONFIG_HOST_URI --gitlab-enterprise-config-read-authorizer-credential-user-token-secret-version=GITLAB_ENTERPRISE_CONFIG_READ_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION --gitlab-enterprise-config-webhook-secret-version=GITLAB_ENTERPRISE_CONFIG_WEBHOOK_SECRET_VERSION : --gitlab-enterprise-config-service-directory=GITLAB_ENTERPRISE_CONFIG_SERVICE_DIRECTORY --gitlab-enterprise-config-ssl-ca-certificate=GITLAB_ENTERPRISE_CONFIG_SSL_CA_CERTIFICATE]] [(--crypto-key-config-reference=CRYPTO_KEY_CONFIG_REFERENCE : --key-ring=KEY_RING)] [GCLOUD_WIDE_FLAG ...] @@ -86,12 +85,6 @@ FLAGS fields, and may be sent on update and delete requests to ensure the client has an up-to-date value before proceeding. - The git proxy configuration. - - --git-proxy-config-enabled - Setting this to true allows the git proxy to be used for performing - git operations on the repositories linked in the connection. - --labels=[LABELS,...] Labels as key value pairs. diff --git a/gcloud/developer-connect/connections/git-repository-links/delete b/gcloud/developer-connect/connections/git-repository-links/delete index 27134e12f..de81d4eb8 100644 --- a/gcloud/developer-connect/connections/git-repository-links/delete +++ b/gcloud/developer-connect/connections/git-repository-links/delete @@ -13,7 +13,7 @@ DESCRIPTION EXAMPLES To delete a git repository link my-git-repository-link in a connection - my-comection in location us-central1 run: + my-connection in location us-central1 run: $ gcloud developer-connect connections git-repository-links delete \ my-git-repository-link --connection=my-connection \ diff --git a/gcloud/developer-connect/connections/update b/gcloud/developer-connect/connections/update index 355b601f7..0c8b555d3 100644 --- a/gcloud/developer-connect/connections/update +++ b/gcloud/developer-connect/connections/update @@ -10,10 +10,10 @@ SYNOPSIS [--annotations=[ANNOTATIONS,...] | --update-annotations=[UPDATE_ANNOTATIONS,...] --clear-annotations | --remove-annotations=[__REMOVE_ANNOTATIONS,...]] - [--bitbucket-cloud-config-authorizer-credential-user-token-secret-version=BITBUCKET_CLOUD_CONFIG_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION --bitbucket-cloud-config-read-authorizer-credential-user-token-secret-version=BITBUCKET_CLOUD_CONFIG_READ_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION --bitbucket-cloud-config-workspace=BITBUCKET_CLOUD_CONFIG_WORKSPACE | --bitbucket-data-center-config-authorizer-credential-user-token-secret-version=BITBUCKET_DATA_CENTER_CONFIG_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION --bitbucket-data-center-config-host-uri=BITBUCKET_DATA_CENTER_CONFIG_HOST_URI --bitbucket-data-center-config-read-authorizer-credential-user-token-secret-version=BITBUCKET_DATA_CENTER_CONFIG_READ_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION --bitbucket-data-center-config-service-directory=BITBUCKET_DATA_CENTER_CONFIG_SERVICE_DIRECTORY --bitbucket-data-center-config-ssl-ca-certificate=BITBUCKET_DATA_CENTER_CONFIG_SSL_CA_CERTIFICATE | --github-config-app-installation-id=GITHUB_CONFIG_APP_INSTALLATION_ID --github-config-authorizer-credential-oauth-token-secret-version=GITHUB_CONFIG_AUTHORIZER_CREDENTIAL_OAUTH_TOKEN_SECRET_VERSION | --github-enterprise-config-app-id=GITHUB_ENTERPRISE_CONFIG_APP_ID --github-enterprise-config-app-installation-id=GITHUB_ENTERPRISE_CONFIG_APP_INSTALLATION_ID --github-enterprise-config-host-uri=GITHUB_ENTERPRISE_CONFIG_HOST_URI --github-enterprise-config-service-directory=GITHUB_ENTERPRISE_CONFIG_SERVICE_DIRECTORY --github-enterprise-config-ssl-ca-certificate=GITHUB_ENTERPRISE_CONFIG_SSL_CA_CERTIFICATE --clear-github-enterprise-config-private-key-secret-version | --github-enterprise-config-private-key-secret-version=GITHUB_ENTERPRISE_CONFIG_PRIVATE_KEY_SECRET_VERSION --clear-github-enterprise-config-webhook-secret-version | --github-enterprise-config-webhook-secret-version=GITHUB_ENTERPRISE_CONFIG_WEBHOOK_SECRET_VERSION | --gitlab-config-authorizer-credential-user-token-secret-version=GITLAB_CONFIG_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION --gitlab-config-read-authorizer-credential-user-token-secret-version=GITLAB_CONFIG_READ_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION | --gitlab-enterprise-config-authorizer-credential-user-token-secret-version=GITLAB_ENTERPRISE_CONFIG_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION --gitlab-enterprise-config-host-uri=GITLAB_ENTERPRISE_CONFIG_HOST_URI --gitlab-enterprise-config-read-authorizer-credential-user-token-secret-version=GITLAB_ENTERPRISE_CONFIG_READ_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION --gitlab-enterprise-config-service-directory=GITLAB_ENTERPRISE_CONFIG_SERVICE_DIRECTORY --gitlab-enterprise-config-ssl-ca-certificate=GITLAB_ENTERPRISE_CONFIG_SSL_CA_CERTIFICATE] - [--clear-git-proxy-config --[no-]git-proxy-config-enabled] - [--crypto-key-config-reference=CRYPTO_KEY_CONFIG_REFERENCE - : --key-ring=KEY_RING] + [--bitbucket-cloud-config-authorizer-credential-user-token-secret-version=BITBUCKET_CLOUD_CONFIG_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION --bitbucket-cloud-config-read-authorizer-credential-user-token-secret-version=BITBUCKET_CLOUD_CONFIG_READ_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION --bitbucket-cloud-config-workspace=BITBUCKET_CLOUD_CONFIG_WORKSPACE --clear-bitbucket-cloud-config | --bitbucket-data-center-config-authorizer-credential-user-token-secret-version=BITBUCKET_DATA_CENTER_CONFIG_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION --bitbucket-data-center-config-host-uri=BITBUCKET_DATA_CENTER_CONFIG_HOST_URI --bitbucket-data-center-config-read-authorizer-credential-user-token-secret-version=BITBUCKET_DATA_CENTER_CONFIG_READ_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION --bitbucket-data-center-config-service-directory=BITBUCKET_DATA_CENTER_CONFIG_SERVICE_DIRECTORY --bitbucket-data-center-config-ssl-ca-certificate=BITBUCKET_DATA_CENTER_CONFIG_SSL_CA_CERTIFICATE --clear-bitbucket-data-center-config | --clear-github-config --github-config-app-installation-id=GITHUB_CONFIG_APP_INSTALLATION_ID --github-config-authorizer-credential-oauth-token-secret-version=GITHUB_CONFIG_AUTHORIZER_CREDENTIAL_OAUTH_TOKEN_SECRET_VERSION | --clear-github-enterprise-config --github-enterprise-config-app-id=GITHUB_ENTERPRISE_CONFIG_APP_ID --github-enterprise-config-app-installation-id=GITHUB_ENTERPRISE_CONFIG_APP_INSTALLATION_ID --github-enterprise-config-host-uri=GITHUB_ENTERPRISE_CONFIG_HOST_URI --github-enterprise-config-service-directory=GITHUB_ENTERPRISE_CONFIG_SERVICE_DIRECTORY --github-enterprise-config-ssl-ca-certificate=GITHUB_ENTERPRISE_CONFIG_SSL_CA_CERTIFICATE --clear-github-enterprise-config-private-key-secret-version | --github-enterprise-config-private-key-secret-version=GITHUB_ENTERPRISE_CONFIG_PRIVATE_KEY_SECRET_VERSION --clear-github-enterprise-config-webhook-secret-version | --github-enterprise-config-webhook-secret-version=GITHUB_ENTERPRISE_CONFIG_WEBHOOK_SECRET_VERSION | --clear-gitlab-config --gitlab-config-authorizer-credential-user-token-secret-version=GITLAB_CONFIG_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION --gitlab-config-read-authorizer-credential-user-token-secret-version=GITLAB_CONFIG_READ_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION | --clear-gitlab-enterprise-config --gitlab-enterprise-config-authorizer-credential-user-token-secret-version=GITLAB_ENTERPRISE_CONFIG_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION --gitlab-enterprise-config-host-uri=GITLAB_ENTERPRISE_CONFIG_HOST_URI --gitlab-enterprise-config-read-authorizer-credential-user-token-secret-version=GITLAB_ENTERPRISE_CONFIG_READ_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION --gitlab-enterprise-config-service-directory=GITLAB_ENTERPRISE_CONFIG_SERVICE_DIRECTORY --gitlab-enterprise-config-ssl-ca-certificate=GITLAB_ENTERPRISE_CONFIG_SSL_CA_CERTIFICATE] + [--clear-crypto-key-config + [--crypto-key-config-reference=CRYPTO_KEY_CONFIG_REFERENCE + : --key-ring=KEY_RING]] [--labels=[LABELS,...] | --update-labels=[UPDATE_LABELS,...] --clear-labels | --remove-labels=[__REMOVE_LABELS,...]] [GCLOUD_WIDE_FLAG ...] @@ -241,6 +241,9 @@ FLAGS The Bitbucket Cloud Workspace ID to be connected to Google Cloud Platform. + --clear-bitbucket-cloud-config + Set connection.bitbucketCloudConfig back to default value. + Configuration for connections to an instance of Bitbucket Data Center. Represents a personal access token that authorized the Connection, and @@ -348,8 +351,14 @@ FLAGS SSL certificate authority to trust when making requests to Bitbucket Data Center. + --clear-bitbucket-data-center-config + Set connection.bitbucketDataCenterConfig back to default value. + Configuration for connections to github.com. + --clear-github-config + Set connection.githubConfig back to default value. + --github-config-app-installation-id=GITHUB_CONFIG_APP_INSTALLATION_ID GitHub App installation id. @@ -386,6 +395,9 @@ FLAGS Configuration for connections to an instance of GitHub Enterprise. + --clear-github-enterprise-config + Set connection.githubEnterpriseConfig back to default value. + --github-enterprise-config-app-id=GITHUB_ENTERPRISE_CONFIG_APP_ID ID of the GitHub App created from the manifest. @@ -512,6 +524,9 @@ FLAGS Configuration for connections to gitlab.com. + --clear-gitlab-config + Set connection.gitlabConfig back to default value. + Represents a personal access token that authorized the Connection, and associated metadata. @@ -576,6 +591,9 @@ FLAGS Configuration for connections to an instance of GitLab Enterprise. + --clear-gitlab-enterprise-config + Set connection.gitlabEnterpriseConfig back to default value. + Represents a personal access token that authorized the Connection, and associated metadata. @@ -681,20 +699,12 @@ FLAGS SSL Certificate Authority certificate to use for requests to GitLab Enterprise instance. - The git proxy configuration. - - --clear-git-proxy-config - Set connection.gitProxyConfig back to default value. - - --[no-]git-proxy-config-enabled - Setting this to true allows the git proxy to be used for performing - git operations on the repositories linked in the connection. Use - --git-proxy-config-enabled to enable and - --no-git-proxy-config-enabled to disable. - The crypto key configuration. This field is used by the Customer-managed encryption keys (CMEK) feature. + --clear-crypto-key-config + Set connection.cryptoKeyConfig back to default value. + CryptoKey resource - The name of the key which is used to encrypt/decrypt customer data. For key in Cloud KMS, the key should be in the format of projects/*/locations/*/keyRings/*/cryptoKeys/*. The diff --git a/gcloud/filestore/instances/promote-replica b/gcloud/filestore/instances/promote-replica index eee0047a9..ca4cf4572 100644 --- a/gcloud/filestore/instances/promote-replica +++ b/gcloud/filestore/instances/promote-replica @@ -4,22 +4,40 @@ NAME SYNOPSIS gcloud filestore instances promote-replica (INSTANCE : --zone=ZONE) - [--async] [--location=LOCATION] [GCLOUD_WIDE_FLAG ...] + [--async] [--location=LOCATION] [--peer-instance=PEER_INSTANCE] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION Promote a Filestore standby replication instance to a regular instance. + This command can be called directly on the standby instance or on the + active instance with the standby peer instance parameter. When used on the + standby instance promotes the standby instance to a regular instance even + if the active instance is unavailable. When used on the active instance + detaches the standby instance from the active instance even if the standby + instance is unavailable. This command can fail for the following reasons: ▪ The target instance does not exist. ▪ The instance is not a standby replication member. + ▪ The instance is an active instance and the peer instance parameter is + missing or invalid. EXAMPLES - To promote an instance with the name my-instance that's located in + To promote a standby instance with the name my-replica-instance located in us-central1, run: - $ gcloud filestore instances promote-replica my-instance \ + $ gcloud filestore instances promote-replica my-replica-instance \ --zone=us-central1 + To promote a standby instance with the name my-replica-instance located in + us-central1, attached to the active peer instance my-active-instance + located in us-west1, run: + + $ gcloud filestore instances promote-replica my-active-instance \ + --zone=us-west1 \ + --peer-instance=projects/my-project/locations/us-central1/\ + instances/my-replica-instance + POSITIONAL ARGUMENTS Instance resource - Arguments and flags that specify the Filestore instance to promote. The arguments in this group can be used to specify @@ -61,6 +79,9 @@ FLAGS --location=LOCATION Location of the Filestore instance to promote. + --peer-instance=PEER_INSTANCE + The name of the standby peer instance to promote. + 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/managed-kafka/help b/gcloud/managed-kafka/help index 132417d33..e0633ab7f 100644 --- a/gcloud/managed-kafka/help +++ b/gcloud/managed-kafka/help @@ -23,6 +23,9 @@ GROUPS consumer-groups Administer Managed Service for Apache Kafka consumer groups. + operations + View Managed Service for Apache Kafka operations. + topics Administer Managed Service for Apache Kafka topics. diff --git a/gcloud/managed-kafka/operations/describe b/gcloud/managed-kafka/operations/describe new file mode 100644 index 000000000..8af579997 --- /dev/null +++ b/gcloud/managed-kafka/operations/describe @@ -0,0 +1,72 @@ +NAME + gcloud managed-kafka operations describe - describe a Managed Service for + Apache Kafka operation + +SYNOPSIS + gcloud managed-kafka operations describe (OPERATION : --location=LOCATION) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Describe a Managed Service for Apache Kafka operation. + +EXAMPLES + To describe an operation named myoperation located in us-central1, run the + following: + + $ gcloud managed-kafka operations describe myoperation \ + --location=us-central1 + +POSITIONAL ARGUMENTS + Operation resource - Identifies the operation for details to be displayed. + 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 operation 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. + + OPERATION + ID of the operation or fully qualified identifier for the operation. + + To set the operation attribute: + ▸ provide the argument operation on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + ID of the location of the Managed Service for Apache Kafka resource. + See + https://cloud.google.com/managed-service-for-apache-kafka/docs/locations + for a list of supported locations. + + To set the location attribute: + ▸ provide the argument operation on the command line with a fully + specified name; + ▸ provide the argument --location 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 managedkafka/v1 API. The full documentation for this + API can be found at: + https://cloud.google.com/managed-service-for-apache-kafka/docs + +NOTES + These variants are also available: + + $ gcloud alpha managed-kafka operations describe + + $ gcloud beta managed-kafka operations describe + diff --git a/gcloud/managed-kafka/operations/help b/gcloud/managed-kafka/operations/help new file mode 100644 index 000000000..64de4bde0 --- /dev/null +++ b/gcloud/managed-kafka/operations/help @@ -0,0 +1,32 @@ +NAME + gcloud managed-kafka operations - view Managed Service for Apache Kafka + operations + +SYNOPSIS + gcloud managed-kafka operations COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + View Managed Service for Apache Kafka operations. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + describe + Describe a Managed Service for Apache Kafka operation. + + list + List all Managed Service for Apache Kafka operations in a given + location. + +NOTES + These variants are also available: + + $ gcloud alpha managed-kafka operations + + $ gcloud beta managed-kafka operations + diff --git a/gcloud/managed-kafka/operations/list b/gcloud/managed-kafka/operations/list new file mode 100644 index 000000000..8f2d08c7d --- /dev/null +++ b/gcloud/managed-kafka/operations/list @@ -0,0 +1,85 @@ +NAME + gcloud managed-kafka operations list - list all Managed Service for Apache + Kafka operations in a given location + +SYNOPSIS + gcloud managed-kafka operations list --location=LOCATION + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + List all Managed Service for Apache Kafka operations in a given location. + To specify the maximum number of operations to list, use the --limit flag. + +EXAMPLES + To list all clusters in a given location, such as us-central1, run the + following: + + $ gcloud managed-kafka operations list --location=us-central1 + +REQUIRED FLAGS + Location resource - Identifies the region which contains all the + operations to be listed. 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; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + --location=LOCATION + ID of the location or fully qualified identifier for the location. + + To set the location attribute: + ▸ provide the argument --location on the command line. + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the managedkafka/v1 API. The full documentation for this + API can be found at: + https://cloud.google.com/managed-service-for-apache-kafka/docs + +NOTES + These variants are also available: + + $ gcloud alpha managed-kafka operations list + + $ gcloud beta managed-kafka operations list + diff --git a/gcloud/policy-intelligence/help b/gcloud/policy-intelligence/help index 27ba0fdaa..c586eb545 100644 --- a/gcloud/policy-intelligence/help +++ b/gcloud/policy-intelligence/help @@ -24,3 +24,9 @@ COMMANDS query-activity Query activities on cloud resource. + +NOTES + This variant is also available: + + $ gcloud beta policy-intelligence + diff --git a/gcloud/run/deploy b/gcloud/run/deploy index d3a328342..56550eb01 100644 --- a/gcloud/run/deploy +++ b/gcloud/run/deploy @@ -141,6 +141,9 @@ FLAGS Specifies a container by name. Flags following --container will apply to the specified container. + Flags that are not container-specific must be specified before + --container. + --[no-]cpu-boost Whether to allocate extra CPU to containers on startup to reduce the perceived latency of a cold start request. Enabled by default when @@ -357,8 +360,9 @@ FLAGS Container Flags - The following flags apply to a single container. If the --container flag is specified these flags may only be - specified after a --container flag. Otherwise they will apply to the primary ingress container. + The following flags apply to a single container. If the --container flag is + specified these flags may only be specified after a --container flag. + Otherwise they will apply to the primary ingress container. --add-volume-mount=[volume=NAME,mount-path=MOUNT_PATH,...] Adds a mount to the current container. Must contain the keys diff --git a/gcloud/run/services/update b/gcloud/run/services/update index 936b0b952..1a0700012 100644 --- a/gcloud/run/services/update +++ b/gcloud/run/services/update @@ -110,6 +110,9 @@ FLAGS Specifies a container by name. Flags following --container will apply to the specified container. + Flags that are not container-specific must be specified before + --container. + --[no-]cpu-boost Whether to allocate extra CPU to containers on startup to reduce the perceived latency of a cold start request. Enabled by default when diff --git a/gcloud/scc/manage/services/describe b/gcloud/scc/manage/services/describe index d36b09fe3..d02756a98 100644 --- a/gcloud/scc/manage/services/describe +++ b/gcloud/scc/manage/services/describe @@ -58,6 +58,8 @@ POSITIONAL ARGUMENTS ◆ web-security-scanner (can be abbreviated as wss) + ◆ vm-threat-detection-aws (can be abbreviated as vmtd-aws) + REQUIRED FLAGS Exactly one of these must be specified: diff --git a/gcloud/scc/manage/services/update b/gcloud/scc/manage/services/update index c90260305..fc394cbf4 100644 --- a/gcloud/scc/manage/services/update +++ b/gcloud/scc/manage/services/update @@ -52,6 +52,8 @@ POSITIONAL ARGUMENTS ◆ web-security-scanner (can be abbreviated as wss) + ◆ vm-threat-detection-aws (can be abbreviated as vmtd-aws) + REQUIRED FLAGS At least one of these must be specified: diff --git a/gcloud/storage/buckets/anywhere-caches/create b/gcloud/storage/buckets/anywhere-caches/create new file mode 100644 index 000000000..79f8de83a --- /dev/null +++ b/gcloud/storage/buckets/anywhere-caches/create @@ -0,0 +1,64 @@ +NAME + gcloud storage buckets anywhere-caches create - create Anywhere Cache + instances for a bucket + +SYNOPSIS + gcloud storage buckets anywhere-caches create URL ZONE [ZONE ...] + [--admission-policy=ADMISSION_POLICY] [--ttl=TTL] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Create Anywhere Cache instances. Only one cache instance per zone can be + created for each bucket. + +EXAMPLES + The following command creates an anywhere cache instance for bucket in + asia-south2-b zone: + + $ gcloud storage buckets anywhere-caches create gs://my-bucket \ + asia-south2-b + + The following command creates anywhere cache instances for bucket in + asia-south2-b, and asia-east1-a zone: + + $ gcloud storage buckets anywhere-caches create gs://my-bucket \ + asia-south2-b asia-east1-a + + The following command creates an anywhere cache instance for bucket in + asia-south2-b zone, with ttl for cache entry as 6 hours, and admission + policy as ADMIT_ON_SECOND_MISS: + + $ gcloud storage buckets anywhere-caches create gs://my-bucket \ + asia-south2-b --ttl=6h --admission-policy='ADMIT_ON_SECOND_MISS' + +POSITIONAL ARGUMENTS + URL + Specifies the URL of the bucket where the Anywhere Cache should be + created. + + ZONE [ZONE ...] + Specifies the name of the zonal locations where the Anywhere Cache + should be created. + +FLAGS + --admission-policy=ADMISSION_POLICY + The cache admission policy decides for each cache miss, whether to + insert the missed block or not. ADMISSION_POLICY must be one of: + ADMIT_ON_FIRST_MISS, ADMIT_ON_SECOND_MISS. + + --ttl=TTL + Cache entry time-to-live. Default to 24h if not provided. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This variant is also available: + + $ gcloud alpha storage buckets anywhere-caches create + diff --git a/gcloud/storage/buckets/anywhere-caches/describe b/gcloud/storage/buckets/anywhere-caches/describe new file mode 100644 index 000000000..3408b321a --- /dev/null +++ b/gcloud/storage/buckets/anywhere-caches/describe @@ -0,0 +1,41 @@ +NAME + gcloud storage buckets anywhere-caches describe - returns details of + Anywhere Cache instance of a bucket + +SYNOPSIS + gcloud storage buckets anywhere-caches describe ID [--raw] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Desribes a single Anywhere Cache instance if it exists. + +EXAMPLES + The following command describes the anywhere cache instance of bucket + my-bucket having anywhere_cache_id my-cache-id: + + $ gcloud storage buckets anywhere-caches describe \ + my-bucket/my-cache-id + +POSITIONAL ARGUMENTS + ID + Identifier for a Anywhere Cache instance. It is a combination of + bucket_name/anywhere_cache_id, For example : test-bucket/my-cache-id. + +FLAGS + --raw + Shows metadata in the format returned by the API instead of + standardizing it. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This variant is also available: + + $ gcloud alpha storage buckets anywhere-caches describe + diff --git a/gcloud/storage/buckets/anywhere-caches/disable b/gcloud/storage/buckets/anywhere-caches/disable new file mode 100644 index 000000000..3ea73a32c --- /dev/null +++ b/gcloud/storage/buckets/anywhere-caches/disable @@ -0,0 +1,44 @@ +NAME + gcloud storage buckets anywhere-caches disable - disable Anywhere Cache + instances + +SYNOPSIS + gcloud storage buckets anywhere-caches disable ID [ID ...] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Disables one or more Anywhere Cache instances. + + The cache instance will be set to DISABLED state. The existing entries can + be read from the cache but new entries will not be written to the cache. + The L4 SSD cache would not be deleted by the cache manager until the min + TTL (1h) has been reached (cache instance is kept for at least 1h). Google + Cloud Storage defines the min TTL which is applied to all cache instances. + Cach disablement could be canceled by using anywhere-caches resume command + before the instance is deleted. + +EXAMPLES + The following command disables the anywhere cache instance of bucket + my-bucket having anywhere_cache_id my-cache-id: + + $ gcloud storage buckets anywhere-caches disable \ + my-bucket/my-cache-id + +POSITIONAL ARGUMENTS + ID [ID ...] + Identifiers for a Anywhere Cache instance. They are combination of + bucket_name/anywhere_cache_id. For example : test-bucket/my-cache-id. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This variant is also available: + + $ gcloud alpha storage buckets anywhere-caches disable + diff --git a/gcloud/storage/buckets/anywhere-caches/help b/gcloud/storage/buckets/anywhere-caches/help new file mode 100644 index 000000000..a0e96e1f2 --- /dev/null +++ b/gcloud/storage/buckets/anywhere-caches/help @@ -0,0 +1,44 @@ +NAME + gcloud storage buckets anywhere-caches - manage Cloud Storage Anywhere + Caches + +SYNOPSIS + gcloud storage buckets anywhere-caches COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Manage Cloud Storage Anywhere Caches. + +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 Anywhere Cache instances for a bucket. + + describe + Returns details of Anywhere Cache instance of a bucket. + + disable + Disable Anywhere Cache instances. + + list + List all Anywhere Cache instances of a bucket. + + pause + Pause Anywhere Cache instances. + + resume + Resume Anywhere Cache instances. + + update + Update Anywhere Cache instances. + +NOTES + This variant is also available: + + $ gcloud alpha storage buckets anywhere-caches + diff --git a/gcloud/alpha/run/workers/revisions/list b/gcloud/storage/buckets/anywhere-caches/list similarity index 75% rename from gcloud/alpha/run/workers/revisions/list rename to gcloud/storage/buckets/anywhere-caches/list index 75c45bfe1..2e3e60c93 100644 --- a/gcloud/alpha/run/workers/revisions/list +++ b/gcloud/storage/buckets/anywhere-caches/list @@ -1,23 +1,30 @@ NAME - gcloud alpha run workers revisions list - list available worker revisions + gcloud storage buckets anywhere-caches list - list all Anywhere Cache + instances of a bucket SYNOPSIS - gcloud alpha run workers revisions list [--region=REGION] + gcloud storage buckets anywhere-caches list URL [--raw] [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) List available worker revisions. + List all cache instances of this bucket. EXAMPLES - To list all revisions for the provided worker: + The following command lists all anywhere cache instances of bucket + gs://my-bucket: - $ gcloud alpha run workers revisions list --worker=foo + $ gcloud storage buckets anywhere-caches list gs://my-bucket + +POSITIONAL ARGUMENTS + URL + Specifies the URL of the bucket for which anywhere cache instances + should be listed. FLAGS - --region=REGION - Region in which the resource can be found. Alternatively, set the - property [run/region]. + --raw + Shows metadata in the format returned by the API instead of + standardizing it. LIST COMMAND FLAGS --filter=EXPRESSION @@ -60,8 +67,7 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. NOTES - This command is currently in alpha and might change without notice. If this - command fails with API permission errors despite specifying the correct - project, you might be trying to access an API with an invitation-only early - access allowlist. + This variant is also available: + + $ gcloud alpha storage buckets anywhere-caches list diff --git a/gcloud/storage/buckets/anywhere-caches/pause b/gcloud/storage/buckets/anywhere-caches/pause new file mode 100644 index 000000000..20bb28a0e --- /dev/null +++ b/gcloud/storage/buckets/anywhere-caches/pause @@ -0,0 +1,36 @@ +NAME + gcloud storage buckets anywhere-caches pause - pause Anywhere Cache + instances + +SYNOPSIS + gcloud storage buckets anywhere-caches pause ID [ID ...] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + The pause operation can be used to stop the data ingestion of a cache + instance in RUNNING state (read-only cache) until the Resume is invoked. + +EXAMPLES + The following command pause the anywhere cache instance of bucket my-bucket + having anywhere_cache_id my-cache-id: + + $ gcloud storage buckets anywhere-caches pause my-bucket/my-cache-id + +POSITIONAL ARGUMENTS + ID [ID ...] + Identifiers for a Anywhere Cache instance. They are combination of + bucket_name/anywhere_cache_id. For example : test-bucket/my-cache-id. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This variant is also available: + + $ gcloud alpha storage buckets anywhere-caches pause + diff --git a/gcloud/storage/buckets/anywhere-caches/resume b/gcloud/storage/buckets/anywhere-caches/resume new file mode 100644 index 000000000..e57c61ec4 --- /dev/null +++ b/gcloud/storage/buckets/anywhere-caches/resume @@ -0,0 +1,38 @@ +NAME + gcloud storage buckets anywhere-caches resume - resume Anywhere Cache + instances + +SYNOPSIS + gcloud storage buckets anywhere-caches resume ID [ID ...] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Resume operation could be used to revert the Paused and Disabled state. + Once a paused/disabled cache is resumed, the cache will be set to + RUNNING/CREATING state: 1. RUNNING if the cache is active. 2. CREATING if + the cache is pending creation. + +EXAMPLES + The following command resume the anywhere cache instance of bucket + my-bucket having anywhere_cache_id my-cache-id: + + $ gcloud storage buckets anywhere-caches resume my-bucket/my-cache-id + +POSITIONAL ARGUMENTS + ID [ID ...] + Identifiers for a Anywhere Cache instance. They are combination of + bucket_name/anywhere_cache_id. For example : test-bucket/my-cache-id. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This variant is also available: + + $ gcloud alpha storage buckets anywhere-caches resume + diff --git a/gcloud/storage/buckets/anywhere-caches/update b/gcloud/storage/buckets/anywhere-caches/update new file mode 100644 index 000000000..5fbaab20c --- /dev/null +++ b/gcloud/storage/buckets/anywhere-caches/update @@ -0,0 +1,56 @@ +NAME + gcloud storage buckets anywhere-caches update - update Anywhere Cache + instances + +SYNOPSIS + gcloud storage buckets anywhere-caches update ID [ID ...] + [--admission-policy=ADMISSION_POLICY] [--ttl=TTL] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Update one or more Anywhere Cache instances. A cache instance can be + updated if its state is created or pending creation. + +EXAMPLES + The following command updates cache entry's ttl, and admisson policy of + anywhere cache instance in bucket my-bucket having anywhere_cache_id + my-cache-id: + + $ gcloud storage buckets anywhere-caches update \ + my-bucket/my-cache-id --ttl=6h \ + --admission-policy='ADMIT_ON_SECOND_MISS' + + The following command updates cache entry's ttl of anywhere cache instances + in bucket bucket-1 and bucket-2 having anywhere_cache_id my-cache-id-1, and + my-cache-id-2 respectively: + + $ gcloud storage buckets anywhere-caches update \ + bucket-1/my-cache-id-1 bucket-2/my-cache-id-2 --ttl=6h + +POSITIONAL ARGUMENTS + ID [ID ...] + Identifiers for a Anywhere Cache Instance.They are combination of + bucket_name/anywhere_cache_id. For example : test-bucket/my-cache-id. + +FLAGS + --admission-policy=ADMISSION_POLICY + The cache admission policy decides for each cache miss, whether to + insert the missed block or not. ADMISSION_POLICY must be one of: + ADMIT_ON_FIRST_MISS, ADMIT_ON_SECOND_MISS. + + --ttl=TTL + Cache entry time-to-live. Default to 24h if not provided. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This variant is also available: + + $ gcloud alpha storage buckets anywhere-caches update + diff --git a/gcloud/storage/buckets/help b/gcloud/storage/buckets/help index 76af3e5ba..0735f45f0 100644 --- a/gcloud/storage/buckets/help +++ b/gcloud/storage/buckets/help @@ -15,6 +15,9 @@ GCLOUD WIDE FLAGS GROUPS GROUP is one of the following: + anywhere-caches + Manage Cloud Storage Anywhere Caches. + notifications Manage Cloud Storage bucket notifications.