From 54eca12593b92b0639ee9b29a070e11179baceea Mon Sep 17 00:00:00 2001 From: Automated Date: Wed, 20 Sep 2023 10:45:25 +0000 Subject: [PATCH] gcloud: Wed Sep 20 10:45:25 UTC 2023 --- gcloud/_version | 8 +- gcloud/alpha/compute/backend-services/help | 3 + .../backend-services/list-usable} | 47 +- .../alpha/compute/instance-templates/create | 22 +- gcloud/alpha/compute/instances/bulk/create | 22 +- gcloud/alpha/compute/instances/create | 22 +- gcloud/alpha/compute/networks/subnets/create | 4 +- gcloud/alpha/compute/queued-resources/create | 22 +- gcloud/alpha/compute/security-policies/update | 4 +- gcloud/alpha/compute/tpus/tpu-vm/update | 4 +- gcloud/alpha/config/get | 20 + gcloud/alpha/config/help | 20 + gcloud/alpha/config/list | 20 + gcloud/alpha/config/set | 20 + gcloud/alpha/config/unset | 20 + .../binauthz/attestations/sign-and-create | 9 + gcloud/alpha/container/clusters/create | 12 +- gcloud/alpha/container/clusters/create-auto | 8 +- gcloud/alpha/container/fleet/help | 4 - .../alpha/container/fleet/namespaces/create | 67 --- .../alpha/container/fleet/namespaces/delete | 43 -- .../alpha/container/fleet/namespaces/describe | 45 -- .../fleet/namespaces/get-credentials | 60 --- gcloud/alpha/container/fleet/namespaces/help | 60 --- gcloud/alpha/container/fleet/namespaces/list | 71 --- .../fleet/namespaces/rbacrolebindings/create | 97 ---- .../fleet/namespaces/rbacrolebindings/delete | 78 ---- .../namespaces/rbacrolebindings/describe | 78 ---- .../fleet/namespaces/rbacrolebindings/help | 48 -- .../fleet/namespaces/rbacrolebindings/update | 97 ---- .../alpha/container/fleet/namespaces/update | 66 --- gcloud/alpha/container/hub/help | 4 - gcloud/alpha/container/hub/namespaces/create | 67 --- gcloud/alpha/container/hub/namespaces/delete | 43 -- .../alpha/container/hub/namespaces/describe | 43 -- .../container/hub/namespaces/get-credentials | 60 --- gcloud/alpha/container/hub/namespaces/help | 60 --- gcloud/alpha/container/hub/namespaces/list | 71 --- .../hub/namespaces/rbacrolebindings/create | 97 ---- .../hub/namespaces/rbacrolebindings/delete | 78 ---- .../hub/namespaces/rbacrolebindings/describe | 78 ---- .../hub/namespaces/rbacrolebindings/help | 48 -- .../hub/namespaces/rbacrolebindings/list | 74 ---- .../hub/namespaces/rbacrolebindings/update | 97 ---- gcloud/alpha/container/hub/namespaces/update | 66 --- gcloud/alpha/container/node-pools/create | 12 +- gcloud/alpha/container/vmware/clusters/create | 30 ++ .../connection-profiles/create/cloudsql | 2 +- .../connection-profiles/create/mysql | 6 +- .../connection-profiles/update | 6 +- gcloud/alpha/dataproc/clusters/create | 7 + .../workflow-templates/set-managed-cluster | 7 + gcloud/alpha/functions/deploy | 4 +- .../iam/workforce-pools/providers/create-oidc | 26 +- .../iam/workforce-pools/providers/update-oidc | 25 +- gcloud/alpha/looker/instances/create | 2 +- gcloud/alpha/looker/instances/delete | 2 +- gcloud/alpha/looker/instances/describe | 2 +- gcloud/alpha/looker/instances/list | 2 +- gcloud/alpha/looker/instances/restart | 2 +- gcloud/alpha/looker/instances/update | 2 +- gcloud/alpha/looker/operations/cancel | 2 +- gcloud/alpha/looker/operations/describe | 2 +- gcloud/alpha/looker/operations/list | 2 +- gcloud/alpha/memcache/instances/create | 4 +- gcloud/alpha/memcache/instances/help | 3 + gcloud/alpha/memcache/instances/upgrade | 86 ++++ .../service-lb-policies/create | 9 + .../service-lb-policies/update | 9 + gcloud/alpha/projects/update | 6 + gcloud/alpha/run/deploy | 416 +++++++++--------- .../alpha/run/services/add-iam-policy-binding | 39 ++ .../run/services/remove-iam-policy-binding | 43 ++ gcloud/alpha/run/services/update | 381 ++++++++-------- gcloud/alpha/services/help | 19 - gcloud/alpha/services/list | 76 ---- gcloud/artifacts/vulnerabilities/help | 2 +- gcloud/artifacts/vulnerabilities/load-vex | 7 +- gcloud/beta/compute/backend-services/help | 3 + .../backend-services/list-usable} | 47 +- gcloud/beta/compute/instance-templates/create | 22 +- gcloud/beta/compute/instances/bulk/create | 22 +- gcloud/beta/compute/instances/create | 22 +- gcloud/beta/compute/networks/subnets/create | 4 +- gcloud/beta/compute/security-policies/update | 4 +- gcloud/beta/config/get | 20 + gcloud/beta/config/help | 20 + gcloud/beta/config/list | 20 + gcloud/beta/config/set | 20 + gcloud/beta/config/unset | 20 + .../binauthz/attestations/sign-and-create | 9 + gcloud/beta/container/clusters/create | 12 +- gcloud/beta/container/clusters/create-auto | 8 +- gcloud/beta/container/fleet/help | 4 - gcloud/beta/container/fleet/namespaces/create | 65 --- gcloud/beta/container/fleet/namespaces/delete | 41 -- .../beta/container/fleet/namespaces/describe | 41 -- .../fleet/namespaces/get-credentials | 58 --- gcloud/beta/container/fleet/namespaces/help | 58 --- gcloud/beta/container/fleet/namespaces/list | 69 --- .../fleet/namespaces/rbacrolebindings/create | 95 ---- .../fleet/namespaces/rbacrolebindings/delete | 76 ---- .../namespaces/rbacrolebindings/describe | 76 ---- .../fleet/namespaces/rbacrolebindings/help | 46 -- .../fleet/namespaces/rbacrolebindings/update | 95 ---- gcloud/beta/container/fleet/namespaces/update | 64 --- gcloud/beta/container/hub/help | 4 - gcloud/beta/container/hub/namespaces/create | 65 --- gcloud/beta/container/hub/namespaces/delete | 41 -- gcloud/beta/container/hub/namespaces/describe | 41 -- .../container/hub/namespaces/get-credentials | 58 --- gcloud/beta/container/hub/namespaces/help | 57 --- gcloud/beta/container/hub/namespaces/list | 69 --- .../hub/namespaces/rbacrolebindings/create | 95 ---- .../hub/namespaces/rbacrolebindings/delete | 76 ---- .../hub/namespaces/rbacrolebindings/describe | 76 ---- .../hub/namespaces/rbacrolebindings/help | 46 -- .../hub/namespaces/rbacrolebindings/list | 72 --- .../hub/namespaces/rbacrolebindings/update | 95 ---- gcloud/beta/container/hub/namespaces/update | 64 --- gcloud/beta/container/node-pools/create | 12 +- gcloud/beta/container/vmware/clusters/create | 30 ++ gcloud/beta/dataproc/clusters/create | 10 +- .../workflow-templates/set-managed-cluster | 10 +- gcloud/beta/datastream/streams/create | 72 ++- gcloud/beta/datastream/streams/update | 72 ++- gcloud/beta/functions/deploy | 4 +- .../iam/workforce-pools/providers/create-oidc | 26 +- .../iam/workforce-pools/providers/update-oidc | 25 +- gcloud/beta/memcache/instances/create | 4 +- gcloud/beta/memcache/instances/help | 3 + gcloud/beta/memcache/instances/upgrade | 84 ++++ .../service-lb-policies/create | 9 + .../service-lb-policies/update | 9 + gcloud/beta/secrets/delete | 2 +- gcloud/beta/services/list | 22 +- gcloud/compute/instance-templates/create | 9 +- gcloud/compute/instances/bulk/create | 9 +- gcloud/compute/instances/create | 9 +- gcloud/compute/networks/subnets/create | 8 +- gcloud/compute/security-policies/update | 4 +- gcloud/compute/tpus/tpu-vm/help | 3 + gcloud/compute/tpus/tpu-vm/update | 76 ++++ gcloud/config/get | 20 + gcloud/config/help | 20 + gcloud/config/list | 20 + gcloud/config/set | 20 + gcloud/config/unset | 20 + gcloud/container/clusters/create | 8 +- gcloud/container/clusters/create-auto | 7 +- gcloud/container/node-pools/create | 8 +- .../connection-profiles/create/cloudsql | 2 +- .../connection-profiles/create/mysql | 6 +- .../connection-profiles/create/oracle | 9 +- .../connection-profiles/create/postgresql | 6 +- .../connection-profiles/update | 6 +- gcloud/dataproc/clusters/create | 10 +- .../workflow-templates/set-managed-cluster | 10 +- gcloud/datastream/streams/create | 72 ++- gcloud/datastream/streams/update | 72 ++- gcloud/functions/deploy | 4 +- .../iam/workforce-pools/providers/create-oidc | 26 +- .../iam/workforce-pools/providers/update-oidc | 25 +- gcloud/looker/instances/create | 2 +- gcloud/looker/instances/delete | 2 +- gcloud/looker/instances/describe | 2 +- gcloud/looker/instances/list | 2 +- gcloud/looker/instances/restart | 2 +- gcloud/looker/instances/update | 2 +- gcloud/looker/operations/cancel | 2 +- gcloud/looker/operations/describe | 2 +- gcloud/looker/operations/list | 2 +- gcloud/memcache/instances/create | 4 +- gcloud/memcache/instances/help | 3 + gcloud/memcache/instances/upgrade | 83 ++++ gcloud/network-connectivity/hubs/accept-spoke | 59 +++ gcloud/network-connectivity/hubs/help | 6 + gcloud/network-connectivity/hubs/reject-spoke | 64 +++ gcloud/network-connectivity/spokes/accept | 5 + gcloud/network-connectivity/spokes/help | 4 +- gcloud/network-connectivity/spokes/reject | 5 + gcloud/secrets/delete | 2 +- gcloud/services/list | 20 +- 183 files changed, 2246 insertions(+), 4040 deletions(-) rename gcloud/alpha/{container/fleet/namespaces/rbacrolebindings/list => compute/backend-services/list-usable} (61%) delete mode 100644 gcloud/alpha/container/fleet/namespaces/create delete mode 100644 gcloud/alpha/container/fleet/namespaces/delete delete mode 100644 gcloud/alpha/container/fleet/namespaces/describe delete mode 100644 gcloud/alpha/container/fleet/namespaces/get-credentials delete mode 100644 gcloud/alpha/container/fleet/namespaces/help delete mode 100644 gcloud/alpha/container/fleet/namespaces/list delete mode 100644 gcloud/alpha/container/fleet/namespaces/rbacrolebindings/create delete mode 100644 gcloud/alpha/container/fleet/namespaces/rbacrolebindings/delete delete mode 100644 gcloud/alpha/container/fleet/namespaces/rbacrolebindings/describe delete mode 100644 gcloud/alpha/container/fleet/namespaces/rbacrolebindings/help delete mode 100644 gcloud/alpha/container/fleet/namespaces/rbacrolebindings/update delete mode 100644 gcloud/alpha/container/fleet/namespaces/update delete mode 100644 gcloud/alpha/container/hub/namespaces/create delete mode 100644 gcloud/alpha/container/hub/namespaces/delete delete mode 100644 gcloud/alpha/container/hub/namespaces/describe delete mode 100644 gcloud/alpha/container/hub/namespaces/get-credentials delete mode 100644 gcloud/alpha/container/hub/namespaces/help delete mode 100644 gcloud/alpha/container/hub/namespaces/list delete mode 100644 gcloud/alpha/container/hub/namespaces/rbacrolebindings/create delete mode 100644 gcloud/alpha/container/hub/namespaces/rbacrolebindings/delete delete mode 100644 gcloud/alpha/container/hub/namespaces/rbacrolebindings/describe delete mode 100644 gcloud/alpha/container/hub/namespaces/rbacrolebindings/help delete mode 100644 gcloud/alpha/container/hub/namespaces/rbacrolebindings/list delete mode 100644 gcloud/alpha/container/hub/namespaces/rbacrolebindings/update delete mode 100644 gcloud/alpha/container/hub/namespaces/update create mode 100644 gcloud/alpha/memcache/instances/upgrade delete mode 100644 gcloud/alpha/services/list rename gcloud/beta/{container/fleet/namespaces/rbacrolebindings/list => compute/backend-services/list-usable} (59%) delete mode 100644 gcloud/beta/container/fleet/namespaces/create delete mode 100644 gcloud/beta/container/fleet/namespaces/delete delete mode 100644 gcloud/beta/container/fleet/namespaces/describe delete mode 100644 gcloud/beta/container/fleet/namespaces/get-credentials delete mode 100644 gcloud/beta/container/fleet/namespaces/help delete mode 100644 gcloud/beta/container/fleet/namespaces/list delete mode 100644 gcloud/beta/container/fleet/namespaces/rbacrolebindings/create delete mode 100644 gcloud/beta/container/fleet/namespaces/rbacrolebindings/delete delete mode 100644 gcloud/beta/container/fleet/namespaces/rbacrolebindings/describe delete mode 100644 gcloud/beta/container/fleet/namespaces/rbacrolebindings/help delete mode 100644 gcloud/beta/container/fleet/namespaces/rbacrolebindings/update delete mode 100644 gcloud/beta/container/fleet/namespaces/update delete mode 100644 gcloud/beta/container/hub/namespaces/create delete mode 100644 gcloud/beta/container/hub/namespaces/delete delete mode 100644 gcloud/beta/container/hub/namespaces/describe delete mode 100644 gcloud/beta/container/hub/namespaces/get-credentials delete mode 100644 gcloud/beta/container/hub/namespaces/help delete mode 100644 gcloud/beta/container/hub/namespaces/list delete mode 100644 gcloud/beta/container/hub/namespaces/rbacrolebindings/create delete mode 100644 gcloud/beta/container/hub/namespaces/rbacrolebindings/delete delete mode 100644 gcloud/beta/container/hub/namespaces/rbacrolebindings/describe delete mode 100644 gcloud/beta/container/hub/namespaces/rbacrolebindings/help delete mode 100644 gcloud/beta/container/hub/namespaces/rbacrolebindings/list delete mode 100644 gcloud/beta/container/hub/namespaces/rbacrolebindings/update delete mode 100644 gcloud/beta/container/hub/namespaces/update create mode 100644 gcloud/beta/memcache/instances/upgrade create mode 100644 gcloud/compute/tpus/tpu-vm/update create mode 100644 gcloud/memcache/instances/upgrade create mode 100644 gcloud/network-connectivity/hubs/accept-spoke create mode 100644 gcloud/network-connectivity/hubs/reject-spoke diff --git a/gcloud/_version b/gcloud/_version index 0421bb579..aed174da8 100644 --- a/gcloud/_version +++ b/gcloud/_version @@ -1,8 +1,8 @@ -Google Cloud SDK 446.0.1 -alpha 2023.09.13 -beta 2023.09.13 +Google Cloud SDK 447.0.0 +alpha 2023.09.15 +beta 2023.09.15 bq 2.0.98 bundled-python3-unix 3.9.16 -core 2023.09.13 +core 2023.09.15 gcloud-crc32c 1.0.0 gsutil 5.25 diff --git a/gcloud/alpha/compute/backend-services/help b/gcloud/alpha/compute/backend-services/help index 46cdb2eda..4d40dc89f 100644 --- a/gcloud/alpha/compute/backend-services/help +++ b/gcloud/alpha/compute/backend-services/help @@ -67,6 +67,9 @@ COMMANDS list (ALPHA) List Google Compute Engine backend services. + list-usable + (ALPHA) List usable backend services. + remove-backend (ALPHA) Remove a backend from a backend service. diff --git a/gcloud/alpha/container/fleet/namespaces/rbacrolebindings/list b/gcloud/alpha/compute/backend-services/list-usable similarity index 61% rename from gcloud/alpha/container/fleet/namespaces/rbacrolebindings/list rename to gcloud/alpha/compute/backend-services/list-usable index 66f9f0be5..445d228af 100644 --- a/gcloud/alpha/container/fleet/namespaces/rbacrolebindings/list +++ b/gcloud/alpha/compute/backend-services/list-usable @@ -1,28 +1,45 @@ NAME - gcloud alpha container fleet namespaces rbacrolebindings list - list RBAC - RoleBindings in a fleet namespace + gcloud alpha compute backend-services list-usable - list usable backend + services SYNOPSIS - gcloud alpha container fleet namespaces rbacrolebindings list - --namespace=NAMESPACE [--filter=EXPRESSION] [--limit=LIMIT] + gcloud alpha compute backend-services list-usable [BACKEND_SERVICE_NAME] + [--global | --region=REGION] [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) This command can fail for the following reasons: - ▪ The namespace specified does not exist. - ▪ The user does not have access to the specified namespace. + (ALPHA) $ gcloud alpha compute backend-services list-usable retrieves the + list of backend service resources in the specified project for which you + have compute.backendService.get and compute.backendService.use permissions. + This command is useful when you're creating load balancers in a Shared VPC + environment and you want to use cross-project service referencing + (https://cloud.google.com/load-balancing/docs/https#cross-project). You can + use this command to find out which backend services in other projects are + available to you for referencing. EXAMPLES - The following command lists RBAC RoleBindings in namespace NAMESPACE in - project PROJECT_ID: + To list all global backend services in a project, run: - $ gcloud alpha container fleet namespaces rbacrolebindings list \ - --namespace=NAMESPACE --project=PROJECT_ID + $ gcloud alpha compute backend-services list-usable --global -REQUIRED FLAGS - --namespace=NAMESPACE - Name of the fleet namespace to list RBAC RoleBindings from. + To list all backend services in a region, run: + + $ gcloud alpha compute backend-services list-usable --region=REGION + +POSITIONAL ARGUMENTS + [BACKEND_SERVICE_NAME] + Name of the backend service to operate on. + +FLAGS + At most one of these can be specified: + + --global + If set, the backend service is global. + + --region=REGION + Region of the backend service to operate on. Overrides the default + compute/region property value for this command invocation. LIST COMMAND FLAGS --filter=EXPRESSION @@ -70,5 +87,5 @@ NOTES project, you might be trying to access an API with an invitation-only early access allowlist. This variant is also available: - $ gcloud beta container fleet namespaces rbacrolebindings list + $ gcloud beta compute backend-services list-usable diff --git a/gcloud/alpha/compute/instance-templates/create b/gcloud/alpha/compute/instance-templates/create index bc5f61b68..4ecb99c84 100644 --- a/gcloud/alpha/compute/instance-templates/create +++ b/gcloud/alpha/compute/instance-templates/create @@ -1112,12 +1112,28 @@ FLAGS Specifies the reservation for instances created from this template. --reservation=RESERVATION - The name of the reservation, required when - --reservation-affinity=specific. + The name of the reservation, required when --reservation-affinity is + one of: specific, specific-then-any-reservation or + specific-then-no-reservation. --reservation-affinity=RESERVATION_AFFINITY; default="any" The type of reservation for instances created from this template. - RESERVATION_AFFINITY must be one of: any, none, specific. + RESERVATION_AFFINITY must be one of: + + any + Consume any available, matching reservation. + none + Do not consume from any reserved capacity. + specific + Must consume from a specific reservation. + specific-then-any-reservation + Prefer to consume from a specific reservation, but still consume + any available matching reservation if the specified reservation + is not available or exhausted. + specific-then-no-reservation + Prefer to consume from a specific reservation, but still consume + from the on-demand pool if the specified reservation is not + available or exhausted. At most one of these can be specified: diff --git a/gcloud/alpha/compute/instances/bulk/create b/gcloud/alpha/compute/instances/bulk/create index d05cc5b28..99cdfb63b 100644 --- a/gcloud/alpha/compute/instances/bulk/create +++ b/gcloud/alpha/compute/instances/bulk/create @@ -1013,12 +1013,28 @@ OPTIONAL FLAGS Specifies the reservation for the instance. --reservation=RESERVATION - The name of the reservation, required when - --reservation-affinity=specific. + The name of the reservation, required when --reservation-affinity is + one of: specific, specific-then-any-reservation or + specific-then-no-reservation. --reservation-affinity=RESERVATION_AFFINITY; default="any" The type of reservation for the instance. RESERVATION_AFFINITY must - be one of: any, none, specific. + be one of: + + any + Consume any available, matching reservation. + none + Do not consume from any reserved capacity. + specific + Must consume from a specific reservation. + specific-then-any-reservation + Prefer to consume from a specific reservation, but still consume + any available matching reservation if the specified reservation + is not available or exhausted. + specific-then-no-reservation + Prefer to consume from a specific reservation, but still consume + from the on-demand pool if the specified reservation is not + available or exhausted. At most one of these can be specified: diff --git a/gcloud/alpha/compute/instances/create b/gcloud/alpha/compute/instances/create index 7b1b59b9e..1eee49eec 100644 --- a/gcloud/alpha/compute/instances/create +++ b/gcloud/alpha/compute/instances/create @@ -1387,12 +1387,28 @@ FLAGS Specifies the reservation for the instance. --reservation=RESERVATION - The name of the reservation, required when - --reservation-affinity=specific. + The name of the reservation, required when --reservation-affinity is + one of: specific, specific-then-any-reservation or + specific-then-no-reservation. --reservation-affinity=RESERVATION_AFFINITY; default="any" The type of reservation for the instance. RESERVATION_AFFINITY must - be one of: any, none, specific. + be one of: + + any + Consume any available, matching reservation. + none + Do not consume from any reserved capacity. + specific + Must consume from a specific reservation. + specific-then-any-reservation + Prefer to consume from a specific reservation, but still consume + any available matching reservation if the specified reservation + is not available or exhausted. + specific-then-no-reservation + Prefer to consume from a specific reservation, but still consume + from the on-demand pool if the specified reservation is not + available or exhausted. At most one of these can be specified: diff --git a/gcloud/alpha/compute/networks/subnets/create b/gcloud/alpha/compute/networks/subnets/create index 73520d5f4..884cd3beb 100644 --- a/gcloud/alpha/compute/networks/subnets/create +++ b/gcloud/alpha/compute/networks/subnets/create @@ -136,7 +136,7 @@ OPTIONAL FLAGS Reserved for Aggregate Ranges used for aggregating private subnetworks. GLOBAL_MANAGED_PROXY - Reserved for Global HTTP(S) Load Balancing. + Reserved for Global Envoy-based Load Balancing. INTERNAL_HTTPS_LOAD_BALANCER Reserved for Internal HTTP(S) Load Balancing. PRIVATE @@ -146,7 +146,7 @@ OPTIONAL FLAGS PRIVATE_SERVICE_CONNECT Reserved for Private Service Connect Internal Load Balancing. REGIONAL_MANAGED_PROXY - Reserved for Regional HTTP(S) Load Balancing. + Reserved for Regional Envoy-based Load Balancing. --range=RANGE The IP space allocated to this subnetwork in CIDR format. diff --git a/gcloud/alpha/compute/queued-resources/create b/gcloud/alpha/compute/queued-resources/create index 4949dd56b..722562866 100644 --- a/gcloud/alpha/compute/queued-resources/create +++ b/gcloud/alpha/compute/queued-resources/create @@ -1003,12 +1003,28 @@ OPTIONAL FLAGS Specifies the reservation for the instance. --reservation=RESERVATION - The name of the reservation, required when - --reservation-affinity=specific. + The name of the reservation, required when --reservation-affinity is + one of: specific, specific-then-any-reservation or + specific-then-no-reservation. --reservation-affinity=RESERVATION_AFFINITY; default="any" The type of reservation for the instance. RESERVATION_AFFINITY must - be one of: any, none, specific. + be one of: + + any + Consume any available, matching reservation. + none + Do not consume from any reserved capacity. + specific + Must consume from a specific reservation. + specific-then-any-reservation + Prefer to consume from a specific reservation, but still consume + any available matching reservation if the specified reservation + is not available or exhausted. + specific-then-no-reservation + Prefer to consume from a specific reservation, but still consume + from the on-demand pool if the specified reservation is not + available or exhausted. At most one of these can be specified: diff --git a/gcloud/alpha/compute/security-policies/update b/gcloud/alpha/compute/security-policies/update index 3f43c7a25..52b7c4523 100644 --- a/gcloud/alpha/compute/security-policies/update +++ b/gcloud/alpha/compute/security-policies/update @@ -57,8 +57,8 @@ FLAGS --json-parsing=JSON_PARSING The JSON parsing behavior for this rule. Must be one of the following - values: [DISABLED, STANDARD]. JSON_PARSING must be one of: DISABLED, - STANDARD. + values: [DISABLED, STANDARD, STANDARD_WITH_GRAPHQL]. JSON_PARSING must + be one of: DISABLED, STANDARD, STANDARD_WITH_GRAPHQL. --layer7-ddos-defense-auto-deploy-confidence-threshold=LAYER7_DDOS_DEFENSE_AUTO_DEPLOY_CONFIDENCE_THRESHOLD Confidence threshold above which Adaptive Protection's auto-deploy diff --git a/gcloud/alpha/compute/tpus/tpu-vm/update b/gcloud/alpha/compute/tpus/tpu-vm/update index 4ba9fc397..d8766a335 100644 --- a/gcloud/alpha/compute/tpus/tpu-vm/update +++ b/gcloud/alpha/compute/tpus/tpu-vm/update @@ -222,5 +222,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 compute tpus tpu-vm update diff --git a/gcloud/alpha/config/get b/gcloud/alpha/config/get index b65dd69e0..a49b8d089 100644 --- a/gcloud/alpha/config/get +++ b/gcloud/alpha/config/get @@ -1266,6 +1266,26 @@ AVAILABLE PROPERTIES the default storage class and retention period for the destination bucket meet the criteria for parallel composite upload. + parallel_composite_upload_component_prefix + The prefix used when naming temporary components created by + composite uploads. If the prefix begins with a /, the temporary + components are uploaded relative to the bucket name. If the prefix + does not begin with a /, the temporary components are uploaded + relative to the prefix portion of the destination object name. For + example, consider an upload that will create a final object named + gs://bucket/dir1/dir2/object. Using a prefix of /prefix means + temporary components use names like + gs://bucket/prefix/COMPONENT_NAME. Using a prefix of prefix means + temporary components use names like + gs://bucket/dir1/dir2/prefix/COMPONENT_NAME. Note that this can + complicate cleaning up temporary components, as they will not all + share a common prefix. If this property is not specified, gcloud + storage uses the prefix + /gcloud/tmp/parallel_composite_uploads/see_gcloud_storage_cp_help_for_details/. + If a chosen prefix results in temporary component names longer than + the maximum length Cloud Storage allows, gcloud storage performs a + non-composite upload. + parallel_composite_upload_component_size Specifies the ideal size of a component in bytes, which will act as an upper bound to the size of the components if ceil(file_size / diff --git a/gcloud/alpha/config/help b/gcloud/alpha/config/help index 05cd0d215..3c1347e92 100644 --- a/gcloud/alpha/config/help +++ b/gcloud/alpha/config/help @@ -1298,6 +1298,26 @@ AVAILABLE PROPERTIES the default storage class and retention period for the destination bucket meet the criteria for parallel composite upload. + parallel_composite_upload_component_prefix + The prefix used when naming temporary components created by + composite uploads. If the prefix begins with a /, the temporary + components are uploaded relative to the bucket name. If the prefix + does not begin with a /, the temporary components are uploaded + relative to the prefix portion of the destination object name. For + example, consider an upload that will create a final object named + gs://bucket/dir1/dir2/object. Using a prefix of /prefix means + temporary components use names like + gs://bucket/prefix/COMPONENT_NAME. Using a prefix of prefix means + temporary components use names like + gs://bucket/dir1/dir2/prefix/COMPONENT_NAME. Note that this can + complicate cleaning up temporary components, as they will not all + share a common prefix. If this property is not specified, gcloud + storage uses the prefix + /gcloud/tmp/parallel_composite_uploads/see_gcloud_storage_cp_help_for_details/. + If a chosen prefix results in temporary component names longer than + the maximum length Cloud Storage allows, gcloud storage performs a + non-composite upload. + parallel_composite_upload_component_size Specifies the ideal size of a component in bytes, which will act as an upper bound to the size of the components if ceil(file_size / diff --git a/gcloud/alpha/config/list b/gcloud/alpha/config/list index 652d602c1..8745172b9 100644 --- a/gcloud/alpha/config/list +++ b/gcloud/alpha/config/list @@ -1310,6 +1310,26 @@ AVAILABLE PROPERTIES the default storage class and retention period for the destination bucket meet the criteria for parallel composite upload. + parallel_composite_upload_component_prefix + The prefix used when naming temporary components created by + composite uploads. If the prefix begins with a /, the temporary + components are uploaded relative to the bucket name. If the prefix + does not begin with a /, the temporary components are uploaded + relative to the prefix portion of the destination object name. For + example, consider an upload that will create a final object named + gs://bucket/dir1/dir2/object. Using a prefix of /prefix means + temporary components use names like + gs://bucket/prefix/COMPONENT_NAME. Using a prefix of prefix means + temporary components use names like + gs://bucket/dir1/dir2/prefix/COMPONENT_NAME. Note that this can + complicate cleaning up temporary components, as they will not all + share a common prefix. If this property is not specified, gcloud + storage uses the prefix + /gcloud/tmp/parallel_composite_uploads/see_gcloud_storage_cp_help_for_details/. + If a chosen prefix results in temporary component names longer than + the maximum length Cloud Storage allows, gcloud storage performs a + non-composite upload. + parallel_composite_upload_component_size Specifies the ideal size of a component in bytes, which will act as an upper bound to the size of the components if ceil(file_size / diff --git a/gcloud/alpha/config/set b/gcloud/alpha/config/set index 3d10805df..8a91f2230 100644 --- a/gcloud/alpha/config/set +++ b/gcloud/alpha/config/set @@ -1313,6 +1313,26 @@ AVAILABLE PROPERTIES the default storage class and retention period for the destination bucket meet the criteria for parallel composite upload. + parallel_composite_upload_component_prefix + The prefix used when naming temporary components created by + composite uploads. If the prefix begins with a /, the temporary + components are uploaded relative to the bucket name. If the prefix + does not begin with a /, the temporary components are uploaded + relative to the prefix portion of the destination object name. For + example, consider an upload that will create a final object named + gs://bucket/dir1/dir2/object. Using a prefix of /prefix means + temporary components use names like + gs://bucket/prefix/COMPONENT_NAME. Using a prefix of prefix means + temporary components use names like + gs://bucket/dir1/dir2/prefix/COMPONENT_NAME. Note that this can + complicate cleaning up temporary components, as they will not all + share a common prefix. If this property is not specified, gcloud + storage uses the prefix + /gcloud/tmp/parallel_composite_uploads/see_gcloud_storage_cp_help_for_details/. + If a chosen prefix results in temporary component names longer than + the maximum length Cloud Storage allows, gcloud storage performs a + non-composite upload. + parallel_composite_upload_component_size Specifies the ideal size of a component in bytes, which will act as an upper bound to the size of the components if ceil(file_size / diff --git a/gcloud/alpha/config/unset b/gcloud/alpha/config/unset index bf8371b32..613fd2f4f 100644 --- a/gcloud/alpha/config/unset +++ b/gcloud/alpha/config/unset @@ -1274,6 +1274,26 @@ AVAILABLE PROPERTIES the default storage class and retention period for the destination bucket meet the criteria for parallel composite upload. + parallel_composite_upload_component_prefix + The prefix used when naming temporary components created by + composite uploads. If the prefix begins with a /, the temporary + components are uploaded relative to the bucket name. If the prefix + does not begin with a /, the temporary components are uploaded + relative to the prefix portion of the destination object name. For + example, consider an upload that will create a final object named + gs://bucket/dir1/dir2/object. Using a prefix of /prefix means + temporary components use names like + gs://bucket/prefix/COMPONENT_NAME. Using a prefix of prefix means + temporary components use names like + gs://bucket/dir1/dir2/prefix/COMPONENT_NAME. Note that this can + complicate cleaning up temporary components, as they will not all + share a common prefix. If this property is not specified, gcloud + storage uses the prefix + /gcloud/tmp/parallel_composite_uploads/see_gcloud_storage_cp_help_for_details/. + If a chosen prefix results in temporary component names longer than + the maximum length Cloud Storage allows, gcloud storage performs a + non-composite upload. + parallel_composite_upload_component_size Specifies the ideal size of a component in bytes, which will act as an upper bound to the size of the components if ceil(file_size / diff --git a/gcloud/alpha/container/binauthz/attestations/sign-and-create b/gcloud/alpha/container/binauthz/attestations/sign-and-create index af20a0d69..b1bb00f96 100644 --- a/gcloud/alpha/container/binauthz/attestations/sign-and-create +++ b/gcloud/alpha/container/binauthz/attestations/sign-and-create @@ -10,6 +10,9 @@ SYNOPSIS --keyversion-keyring=KEYVERSION_KEYRING --keyversion-location=KEYVERSION_LOCATION --keyversion-project=KEYVERSION_PROJECT) + [--dsse-type=DSSE_TYPE; + default="application/vnd.dev.cosign.simplesigning.v1+json"] + [--pae-encode-payload] [--public-key-id-override=PUBLIC_KEY_ID_OVERRIDE] [--validate] [GCLOUD_WIDE_FLAG ...] @@ -117,6 +120,12 @@ REQUIRED FLAGS ▸ set the property core/project. OPTIONAL FLAGS + --dsse-type=DSSE_TYPE; default="application/vnd.dev.cosign.simplesigning.v1+json" + DSSE type used for pae encoding. + + --pae-encode-payload + Whether to pae-encode the payload before signing. + --public-key-id-override=PUBLIC_KEY_ID_OVERRIDE If provided, the ID of the public key that will be used to verify the Attestation instead of the default generated one. This ID should match diff --git a/gcloud/alpha/container/clusters/create b/gcloud/alpha/container/clusters/create index e25a1d0ed..8514e2908 100644 --- a/gcloud/alpha/container/clusters/create +++ b/gcloud/alpha/container/clusters/create @@ -106,9 +106,9 @@ SYNOPSIS [--enable-private-endpoint --enable-private-nodes --master-ipv4-cidr=MASTER_IPV4_CIDR --private-cluster] [--enable-tpu --enable-tpu-service-networking | --tpu-ipv4-cidr=CIDR] - [--ephemeral-storage=[local-ssd-count=LOCAL-SSD-COUNT] - | --ephemeral-storage-local-ssd=[count=COUNT] - | --local-nvme-ssd-block=[count=COUNT] + [--ephemeral-storage[=[local-ssd-count=LOCAL-SSD-COUNT]] + | --ephemeral-storage-local-ssd[=[count=COUNT]] + | --local-nvme-ssd-block[=[count=COUNT]] | --local-ssd-count=LOCAL_SSD_COUNT | --local-ssd-volumes=[[count=COUNT], [type=TYPE],[format=FORMAT],...]] @@ -1765,7 +1765,7 @@ FLAGS At most one of these can be specified: - --ephemeral-storage=[local-ssd-count=LOCAL-SSD-COUNT] + --ephemeral-storage[=[local-ssd-count=LOCAL-SSD-COUNT]] Parameters for the ephemeral storage filesystem. If unspecified, ephemeral storage is backed by the boot disk. @@ -1782,7 +1782,7 @@ FLAGS See https://cloud.google.com/compute/docs/disks/local-ssd for more information. - --ephemeral-storage-local-ssd=[count=COUNT] + --ephemeral-storage-local-ssd[=[count=COUNT]] Parameters for the ephemeral storage filesystem. If unspecified, ephemeral storage is backed by the boot disk. @@ -1798,7 +1798,7 @@ FLAGS See https://cloud.google.com/compute/docs/disks/local-ssd for more information. - --local-nvme-ssd-block=[count=COUNT] + --local-nvme-ssd-block[=[count=COUNT]] Adds the requested local SSDs on all nodes in default node pool(s) in the new cluster. diff --git a/gcloud/alpha/container/clusters/create-auto b/gcloud/alpha/container/clusters/create-auto index fa56d46ae..dabb47c08 100644 --- a/gcloud/alpha/container/clusters/create-auto +++ b/gcloud/alpha/container/clusters/create-auto @@ -12,7 +12,8 @@ SYNOPSIS [--create-subnetwork=[KEY=VALUE,...]] [--database-encryption-key=DATABASE_ENCRYPTION_KEY] [--dataplane-v2-observability-mode=DATAPLANE_V2_OBSERVABILITY_MODE] - [--enable-fleet] [--enable-google-cloud-access] + [--enable-backup-restore] [--enable-fleet] + [--enable-google-cloud-access] [--enable-kubernetes-unstable-apis=API,[API,...]] [--enable-master-global-access] [--fleet-project=PROJECT_ID_OR_NUMBER] [--logging=[COMPONENT,...]] [--monitoring=[COMPONENT,...]] @@ -185,6 +186,11 @@ FLAGS Makes Advanced Datapath Observability available from the VPC network. + --enable-backup-restore + Enable the Backup for GKE add-on. This add-on is disabled by default. + To learn more, see the Backup for GKE overview: + https://cloud.google.com/kubernetes-engine/docs/add-on/backup-for-gke/concepts/backup-for-gke. + --enable-fleet Set cluster project as the fleet host project. This will register the cluster to the same project. To register the cluster to a fleet in a diff --git a/gcloud/alpha/container/fleet/help b/gcloud/alpha/container/fleet/help index 15474f385..392667649 100644 --- a/gcloud/alpha/container/fleet/help +++ b/gcloud/alpha/container/fleet/help @@ -76,10 +76,6 @@ GROUPS multi-cluster-services (ALPHA) Manage Multi-cluster Services Feature. - namespaces - (ALPHA) Fleet namespaces are the fleet equivalent of k8s cluster - namespaces. - operations (ALPHA) Manage Anthos fleet long-running operations. diff --git a/gcloud/alpha/container/fleet/namespaces/create b/gcloud/alpha/container/fleet/namespaces/create deleted file mode 100644 index 8b2b85cc5..000000000 --- a/gcloud/alpha/container/fleet/namespaces/create +++ /dev/null @@ -1,67 +0,0 @@ -NAME - gcloud alpha container fleet namespaces create - create a fleet namespace - -SYNOPSIS - gcloud alpha container fleet namespaces create NAME [--scope=SCOPE] - [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (ALPHA) This command can fail for the following reasons: - ▪ The project specified does not exist. - ▪ The project has a fleet namespace with the same name. - ▪ The caller does not have permission to access the given project. - -EXAMPLES - To create a fleet namespace with name NAMESPACE in the active project, run: - - $ gcloud alpha container fleet namespaces create NAMESPACE - - To create a fleet namespace in fleet scope SCOPE in project PROJECT_ID with - name NAMESPACE, run: - - $ gcloud alpha container fleet namespaces create NAMESPACE \ - --scope=SCOPE --project=PROJECT_ID - -POSITIONAL ARGUMENTS - NAME - Name of the fleet namespace to be created. Must comply with RFC 1123 - (up to 63 characters, alphanumeric and '-') - -FLAGS - Scope resource - The group of arguments defining the Fleet Scope. 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 --scope on the command line with a fully - specified name; - ◆ provide the argument --project on the command line; - ◆ set the property core/project. - - To set the location attribute: - ◆ provide the argument --scope on the command line with a fully - specified name; - ◆ global is the only supported location. - - --scope=SCOPE - ID of the scope or fully qualified identifier for the scope. - - To set the scope attribute: - ▸ provide the argument --scope on the command line. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --configuration, --flags-file, --flatten, --format, - --help, --impersonate-service-account, --log-http, --project, --quiet, - --trace-token, --user-output-enabled, --verbosity. - - Run $ gcloud help for details. - -NOTES - This command is currently in 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 container fleet namespaces create - diff --git a/gcloud/alpha/container/fleet/namespaces/delete b/gcloud/alpha/container/fleet/namespaces/delete deleted file mode 100644 index adc391048..000000000 --- a/gcloud/alpha/container/fleet/namespaces/delete +++ /dev/null @@ -1,43 +0,0 @@ -NAME - gcloud alpha container fleet namespaces delete - delete a fleet namespace - -SYNOPSIS - gcloud alpha container fleet namespaces delete NAME [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (ALPHA) This command can fail for the following reasons: - ▪ The project specified does not exist. - ▪ The namespace specified does not exist. - ▪ The caller does not have permission to access the given project or - namespace. - -EXAMPLES - To delete fleet namespace NAMESPACE in the active project: - - $ gcloud alpha container fleet namespaces delete NAMESPACE - - To delete fleet namespace NAMESPACE in project PROJECT_ID: - - $ gcloud alpha container fleet namespaces delete NAMESPACE \ - --project=PROJECT_ID - -POSITIONAL ARGUMENTS - NAME - Name of the fleet namespace to be deleted. - -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 container fleet namespaces delete - diff --git a/gcloud/alpha/container/fleet/namespaces/describe b/gcloud/alpha/container/fleet/namespaces/describe deleted file mode 100644 index f61916da7..000000000 --- a/gcloud/alpha/container/fleet/namespaces/describe +++ /dev/null @@ -1,45 +0,0 @@ -NAME - gcloud alpha container fleet namespaces describe - show fleet namespace - info - -SYNOPSIS - gcloud alpha container fleet namespaces describe NAME - [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (ALPHA) This command can fail for the following reasons: - ▪ The project specified does not exist. - ▪ The namespace specified does not exist in the project. - ▪ The caller does not have permission to access the project or - namespace. - -EXAMPLES - To print metadata for the namespace NAMESPACE in the active project, run: - - $ gcloud alpha container fleet namespaces describe NAMESPACE - - To print metadata for the namespace NAMESPACE in project PROJECT_ID, run: - - $ gcloud alpha container fleet namespaces describe NAMESPACE \ - --project=PROJECT_ID - -POSITIONAL ARGUMENTS - NAME - Name of the fleet namespace to be described. - -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 container fleet namespaces describe - diff --git a/gcloud/alpha/container/fleet/namespaces/get-credentials b/gcloud/alpha/container/fleet/namespaces/get-credentials deleted file mode 100644 index 989d7b764..000000000 --- a/gcloud/alpha/container/fleet/namespaces/get-credentials +++ /dev/null @@ -1,60 +0,0 @@ -NAME - gcloud alpha container fleet namespaces get-credentials - fetch credentials - for a membership with a particular namespace - -SYNOPSIS - gcloud alpha container fleet namespaces get-credentials NAMESPACE - [--membership=MEMBERSHIP] [--membership-location=MEMBERSHIP_LOCATION] - [--set-namespace-in-config=SET_NAMESPACE_IN_CONFIG] - [GCLOUD_WIDE_FLAG ...] - -EXAMPLES - Get the Connect Gateway kubeconfig for global membership MEMBERSHIP, using - namespace NAMESPACE in the config: - - $ gcloud alpha container fleet namespaces get-credentials \ - NAMESPACE --membership=MEMBERSHIP --membership-location=global \ - --set-namespace-in-config=true - - Get the Connect Gateway kubeconfig for global membership MEMBERSHIP: - - $ gcloud alpha container fleet namespaces get-credentials \ - NAMESPACE --membership=MEMBERSHIP --membership-location=global - -POSITIONAL ARGUMENTS - NAMESPACE - Name of the namespace for which to get access to memberships. - -FLAGS - --membership=MEMBERSHIP - Membership ID to get credentials from. If not provided, a prompt will - offer a list of memberships in the fleet. - - --membership-location=MEMBERSHIP_LOCATION - The location of the membership resource, e.g. us-central1. If not - specified, defaults to global. - - --set-namespace-in-config=SET_NAMESPACE_IN_CONFIG - If true, the default namespace for the context in the generated - kubeconfig will be set to the Fleet namespace (i.e. the name given as - the positional argument in this command). - - Otherwise, no default namespace will be set, functioning the same as - gcloud container fleet memberships get-credentials. - -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 container fleet namespaces get-credentials - diff --git a/gcloud/alpha/container/fleet/namespaces/help b/gcloud/alpha/container/fleet/namespaces/help deleted file mode 100644 index 893d3e083..000000000 --- a/gcloud/alpha/container/fleet/namespaces/help +++ /dev/null @@ -1,60 +0,0 @@ -NAME - gcloud alpha container fleet namespaces - fleet namespaces are the fleet - equivalent of k8s cluster namespaces - -SYNOPSIS - gcloud alpha container fleet namespaces GROUP | COMMAND - [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (ALPHA) This command group allows for manipulation of fleet namespaces. - -EXAMPLES - Manage fleet namespaces: - - $ gcloud alpha container fleet namespaces --help - - Manage RBAC RoleBindings in a fleet namespace: - - $ gcloud alpha container fleet namespaces rbacrolebindings --help - -GCLOUD WIDE FLAGS - These flags are available to all commands: --help. - - Run $ gcloud help for details. - -GROUPS - GROUP is one of the following: - - rbacrolebindings - (ALPHA) Fleet namespace RBAC RoleBindings for permissions. - -COMMANDS - COMMAND is one of the following: - - create - (ALPHA) Create a fleet namespace. - - delete - (ALPHA) Delete a fleet namespace. - - describe - (ALPHA) Show fleet namespace info. - - get-credentials - (ALPHA) Fetch credentials for a membership with a particular namespace. - - list - (ALPHA) List fleet namespaces in a project. - - update - (ALPHA) Update a fleet namespace. - -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 container fleet namespaces - diff --git a/gcloud/alpha/container/fleet/namespaces/list b/gcloud/alpha/container/fleet/namespaces/list deleted file mode 100644 index f18c8aab7..000000000 --- a/gcloud/alpha/container/fleet/namespaces/list +++ /dev/null @@ -1,71 +0,0 @@ -NAME - gcloud alpha container fleet namespaces list - list fleet namespaces in a - project - -SYNOPSIS - gcloud alpha container fleet namespaces list [--filter=EXPRESSION] - [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] - [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (ALPHA) This command can fail for the following reasons: - ▪ The project specified does not exist. - ▪ The user does not have access to the project specified. - -EXAMPLES - The following command lists namespaces in the active project: - - $ gcloud alpha container fleet namespaces list - - The following command lists namespaces in project PROJECT_ID: - - $ gcloud alpha container fleet namespaces list --project=PROJECT_ID - -LIST COMMAND FLAGS - --filter=EXPRESSION - Apply a Boolean filter EXPRESSION to each resource item to be listed. - If the expression evaluates True, then that item is listed. For more - details and examples of filter expressions, run $ gcloud topic filters. - This flag interacts with other flags that are applied in this order: - --flatten, --sort-by, --filter, --limit. - - --limit=LIMIT - Maximum number of resources to list. The default is unlimited. This - flag interacts with other flags that are applied in this order: - --flatten, --sort-by, --filter, --limit. - - --page-size=PAGE_SIZE - Some services group resource list output into pages. This flag - specifies the maximum number of resources per page. The default is - determined by the service if it supports paging, otherwise it is - unlimited (no paging). Paging may be applied before or after --filter - and --limit depending on the service. - - --sort-by=[FIELD,...] - Comma-separated list of resource field key names to sort by. The - default order is ascending. Prefix a field with ``~'' for descending - order on that field. This flag interacts with other flags that are - applied in this order: --flatten, --sort-by, --filter, --limit. - - --uri - Print a list of resource URIs instead of the default output, and change - the command output to a list of URIs. If this flag is used with - --format, the formatting is applied on this URI list. To display URIs - alongside other keys instead, use the uri() transform. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --configuration, --flags-file, --flatten, --format, - --help, --impersonate-service-account, --log-http, --project, --quiet, - --trace-token, --user-output-enabled, --verbosity. - - Run $ gcloud help for details. - -NOTES - This command is currently in alpha and might change without notice. If this - command fails with API permission errors despite specifying the correct - project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: - - $ gcloud beta container fleet namespaces list - diff --git a/gcloud/alpha/container/fleet/namespaces/rbacrolebindings/create b/gcloud/alpha/container/fleet/namespaces/rbacrolebindings/create deleted file mode 100644 index 7a9ebbecc..000000000 --- a/gcloud/alpha/container/fleet/namespaces/rbacrolebindings/create +++ /dev/null @@ -1,97 +0,0 @@ -NAME - gcloud alpha container fleet namespaces rbacrolebindings create - create an - RBAC RoleBinding - -SYNOPSIS - gcloud alpha container fleet namespaces rbacrolebindings create - (NAME : --location=LOCATION --namespace=NAMESPACE) --role=ROLE - (--group=GROUP | --user=USER) [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (ALPHA) This command can fail for the following reasons: - ▪ The RBAC RoleBinding already exists. - ▪ The caller does not have permission to access the given namespace. - -EXAMPLES - To create an admin RBAC RoleBinding RBRB in namespace NAMESPACE for user - person@google.com, run: - - $ gcloud alpha container fleet namespaces rbacrolebindings create \ - RBRB --namespace=NAMESPACE --role=admin --user=person@google.com - - To create a viewer RBAC RoleBinding RBRB in namespace NAMESPACE for group - people@google.com, run: - - $ gcloud alpha container fleet namespaces rbacrolebindings create \ - RBRB --namespace=NAMESPACE --role=viewer \ - --group=people@google.com - -POSITIONAL ARGUMENTS - Rbacrolebinding resource - The group of arguments defining an - RBACRoleBinding. 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 NAME 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. - - NAME - ID of the rbacrolebinding or fully qualified identifier for the - rbacrolebinding. - - To set the rbacrolebinding attribute: - ▸ provide the argument NAME on the command line. - - This positional argument must be specified if any of the other - arguments in this group are specified. - - --location=LOCATION - Location for the rbacrolebinding. - - To set the location attribute: - ▸ provide the argument NAME on the command line with a fully - specified name; - ▸ provide the argument --location on the command line; - ▸ set the property gkehub/location. - - --namespace=NAMESPACE - Name of the rbacrolebinding. - - To set the namespace attribute: - ▸ provide the argument NAME on the command line with a fully - specified name; - ▸ provide the argument --namespace on the command line. - -REQUIRED FLAGS - --role=ROLE - Role to assign. ROLE must be one of: admin, edit, view. - - Exactly one of these must be specified: - - --group=GROUP - Group for the RoleBinding. - - --user=USER - User for the RoleBinding. - -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 container fleet namespaces rbacrolebindings create - diff --git a/gcloud/alpha/container/fleet/namespaces/rbacrolebindings/delete b/gcloud/alpha/container/fleet/namespaces/rbacrolebindings/delete deleted file mode 100644 index d08d3956c..000000000 --- a/gcloud/alpha/container/fleet/namespaces/rbacrolebindings/delete +++ /dev/null @@ -1,78 +0,0 @@ -NAME - gcloud alpha container fleet namespaces rbacrolebindings delete - delete a - fleet namespace RBAC RoleBinding - -SYNOPSIS - gcloud alpha container fleet namespaces rbacrolebindings delete - (NAME : --location=LOCATION --namespace=NAMESPACE) - [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (ALPHA) This command can fail for the following reasons: - ▪ The RoleBinding specified does not exist. - ▪ The caller does not have permission to access the given RoleBinding. - -EXAMPLES - To delete RBAC RoleBinding RBRB in namespace NAMESPACE in the active - project: - - $ gcloud alpha container fleet namespaces rbacrolebindings delete \ - RBRB --namespace=NAMESPACE - -POSITIONAL ARGUMENTS - Rbacrolebinding resource - The group of arguments defining an - RBACRoleBinding. 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 NAME 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. - - NAME - ID of the rbacrolebinding or fully qualified identifier for the - rbacrolebinding. - - To set the rbacrolebinding attribute: - ▸ provide the argument NAME on the command line. - - This positional argument must be specified if any of the other - arguments in this group are specified. - - --location=LOCATION - Location for the rbacrolebinding. - - To set the location attribute: - ▸ provide the argument NAME on the command line with a fully - specified name; - ▸ provide the argument --location on the command line; - ▸ set the property gkehub/location. - - --namespace=NAMESPACE - Name of the rbacrolebinding. - - To set the namespace attribute: - ▸ provide the argument NAME on the command line with a fully - specified name; - ▸ provide the argument --namespace on the command line. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --configuration, --flags-file, --flatten, --format, - --help, --impersonate-service-account, --log-http, --project, --quiet, - --trace-token, --user-output-enabled, --verbosity. - - Run $ gcloud help for details. - -NOTES - This command is currently in 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 container fleet namespaces rbacrolebindings delete - diff --git a/gcloud/alpha/container/fleet/namespaces/rbacrolebindings/describe b/gcloud/alpha/container/fleet/namespaces/rbacrolebindings/describe deleted file mode 100644 index 70ccc2e0e..000000000 --- a/gcloud/alpha/container/fleet/namespaces/rbacrolebindings/describe +++ /dev/null @@ -1,78 +0,0 @@ -NAME - gcloud alpha container fleet namespaces rbacrolebindings describe - show - fleet namespace RBAC RoleBinding information - -SYNOPSIS - gcloud alpha container fleet namespaces rbacrolebindings describe - (NAME : --location=LOCATION --namespace=NAMESPACE) - [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (ALPHA) This command can fail for the following reasons: - ▪ The RoleBinding specified does not exist in the project. - ▪ The caller does not have permission to access the RoleBinding. - -EXAMPLES - To print metadata for RBAC RoleBinding RBRB in the namespace NAMESPACE, - run: - - $ gcloud alpha container fleet namespaces rbacrolebindings \ - describe RBRB --namespace=NAMESPACE - -POSITIONAL ARGUMENTS - Rbacrolebinding resource - The group of arguments defining an - RBACRoleBinding. 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 NAME 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. - - NAME - ID of the rbacrolebinding or fully qualified identifier for the - rbacrolebinding. - - To set the rbacrolebinding attribute: - ▸ provide the argument NAME on the command line. - - This positional argument must be specified if any of the other - arguments in this group are specified. - - --location=LOCATION - Location for the rbacrolebinding. - - To set the location attribute: - ▸ provide the argument NAME on the command line with a fully - specified name; - ▸ provide the argument --location on the command line; - ▸ set the property gkehub/location. - - --namespace=NAMESPACE - Name of the rbacrolebinding. - - To set the namespace attribute: - ▸ provide the argument NAME on the command line with a fully - specified name; - ▸ provide the argument --namespace on the command line. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --configuration, --flags-file, --flatten, --format, - --help, --impersonate-service-account, --log-http, --project, --quiet, - --trace-token, --user-output-enabled, --verbosity. - - Run $ gcloud help for details. - -NOTES - This command is currently in 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 container fleet namespaces rbacrolebindings describe - diff --git a/gcloud/alpha/container/fleet/namespaces/rbacrolebindings/help b/gcloud/alpha/container/fleet/namespaces/rbacrolebindings/help deleted file mode 100644 index 24731691a..000000000 --- a/gcloud/alpha/container/fleet/namespaces/rbacrolebindings/help +++ /dev/null @@ -1,48 +0,0 @@ -NAME - gcloud alpha container fleet namespaces rbacrolebindings - fleet namespace - RBAC RoleBindings for permissions - -SYNOPSIS - gcloud alpha container fleet namespaces rbacrolebindings COMMAND - [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (ALPHA) This command group allows for manipulation of fleet namespace RBAC - RoleBindings. - -EXAMPLES - Manage RBAC RoleBindings: - - $ gcloud alpha container fleet namespaces rbacrolebindings --help - -GCLOUD WIDE FLAGS - These flags are available to all commands: --help. - - Run $ gcloud help for details. - -COMMANDS - COMMAND is one of the following: - - create - (ALPHA) Create an RBAC RoleBinding. - - delete - (ALPHA) Delete a fleet namespace RBAC RoleBinding. - - describe - (ALPHA) Show fleet namespace RBAC RoleBinding information. - - list - (ALPHA) List RBAC RoleBindings in a fleet namespace. - - update - (ALPHA) Update a fleet namespace RBAC RoleBinding. - -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 container fleet namespaces rbacrolebindings - diff --git a/gcloud/alpha/container/fleet/namespaces/rbacrolebindings/update b/gcloud/alpha/container/fleet/namespaces/rbacrolebindings/update deleted file mode 100644 index 586791567..000000000 --- a/gcloud/alpha/container/fleet/namespaces/rbacrolebindings/update +++ /dev/null @@ -1,97 +0,0 @@ -NAME - gcloud alpha container fleet namespaces rbacrolebindings update - update a - fleet namespace RBAC RoleBinding - -SYNOPSIS - gcloud alpha container fleet namespaces rbacrolebindings update - (NAME : --location=LOCATION --namespace=NAMESPACE) [--role=ROLE] - [--group=GROUP | --user=USER] [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (ALPHA) This command can fail for the following reasons: - ▪ The RoleBinding does not exist in the project. - ▪ The caller does not have permission to access the RoleBinding. - -EXAMPLES - To update the RBAC RoleBinding RBRB in namespace NAMESPACE in the active - project to the viewer role: - - $ gcloud alpha container fleet namespaces rbacrolebindings update \ - RBRB --namespace=NAMESPACE --role=viewer - - To update the RBAC RoleBinding RBRB in namespace NAMESPACE in the active - project to the user someone@google.com: - - $ gcloud alpha container fleet namespaces rbacrolebindings update \ - RBRB --namespace=NAMESPACE --user=someone@google.com - -POSITIONAL ARGUMENTS - Rbacrolebinding resource - The group of arguments defining an - RBACRoleBinding. 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 NAME 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. - - NAME - ID of the rbacrolebinding or fully qualified identifier for the - rbacrolebinding. - - To set the rbacrolebinding attribute: - ▸ provide the argument NAME on the command line. - - This positional argument must be specified if any of the other - arguments in this group are specified. - - --location=LOCATION - Location for the rbacrolebinding. - - To set the location attribute: - ▸ provide the argument NAME on the command line with a fully - specified name; - ▸ provide the argument --location on the command line; - ▸ set the property gkehub/location. - - --namespace=NAMESPACE - Name of the rbacrolebinding. - - To set the namespace attribute: - ▸ provide the argument NAME on the command line with a fully - specified name; - ▸ provide the argument --namespace on the command line. - -FLAGS - --role=ROLE - Role for the RBACRoleBinding to update to. ROLE must be one of: admin, - edit, view. - - At most one of these can be specified: - - --group=GROUP - Group for the RBACRoleBinding to update to. - - --user=USER - User for the RBACRoleBinding to update to. - -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 container fleet namespaces rbacrolebindings update - diff --git a/gcloud/alpha/container/fleet/namespaces/update b/gcloud/alpha/container/fleet/namespaces/update deleted file mode 100644 index 327d68c3e..000000000 --- a/gcloud/alpha/container/fleet/namespaces/update +++ /dev/null @@ -1,66 +0,0 @@ -NAME - gcloud alpha container fleet namespaces update - update a fleet namespace - -SYNOPSIS - gcloud alpha container fleet namespaces update NAME [--scope=SCOPE] - [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (ALPHA) This command can fail for the following reasons: - ▪ The project specified does not exist. - ▪ The fleet namespace does not exist in the project. - ▪ The caller does not have permission to access the project or - namespace. - -EXAMPLES - To update the namespace NAMESPACE in the active project: - - $ gcloud alpha container fleet namespaces update NAMESPACE - - To update the namespace NAMESPACE in project PROJECT_ID: - - $ gcloud alpha container fleet namespaces update NAMESPACE \ - --project=PROJECT_ID - -POSITIONAL ARGUMENTS - NAME - Name of the namespace to be updated. - -FLAGS - Scope resource - The group of arguments defining the Fleet Scope. 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 --scope on the command line with a fully - specified name; - ◆ provide the argument --project on the command line; - ◆ set the property core/project. - - To set the location attribute: - ◆ provide the argument --scope on the command line with a fully - specified name; - ◆ global is the only supported location. - - --scope=SCOPE - ID of the scope or fully qualified identifier for the scope. - - To set the scope attribute: - ▸ provide the argument --scope on the command line. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --configuration, --flags-file, --flatten, --format, - --help, --impersonate-service-account, --log-http, --project, --quiet, - --trace-token, --user-output-enabled, --verbosity. - - Run $ gcloud help for details. - -NOTES - This command is currently in 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 container fleet namespaces update - diff --git a/gcloud/alpha/container/hub/help b/gcloud/alpha/container/hub/help index 8546cf144..f37e5978c 100644 --- a/gcloud/alpha/container/hub/help +++ b/gcloud/alpha/container/hub/help @@ -76,10 +76,6 @@ GROUPS multi-cluster-services (ALPHA) Manage Multi-cluster Services Feature. - namespaces - (ALPHA) Fleet namespaces are the fleet equivalent of k8s cluster - namespaces. - operations (ALPHA) Manage Anthos fleet long-running operations. diff --git a/gcloud/alpha/container/hub/namespaces/create b/gcloud/alpha/container/hub/namespaces/create deleted file mode 100644 index 91e7d0464..000000000 --- a/gcloud/alpha/container/hub/namespaces/create +++ /dev/null @@ -1,67 +0,0 @@ -NAME - gcloud alpha container hub namespaces create - create a fleet namespace - -SYNOPSIS - gcloud alpha container hub namespaces create NAME [--scope=SCOPE] - [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (ALPHA) This command can fail for the following reasons: - ▪ The project specified does not exist. - ▪ The project has a fleet namespace with the same name. - ▪ The caller does not have permission to access the given project. - -EXAMPLES - To create a fleet namespace with name NAMESPACE in the active project, run: - - $ gcloud alpha container hub namespaces create NAMESPACE - - To create a fleet namespace in fleet scope SCOPE in project PROJECT_ID with - name NAMESPACE, run: - - $ gcloud alpha container hub namespaces create NAMESPACE \ - --scope=SCOPE --project=PROJECT_ID - -POSITIONAL ARGUMENTS - NAME - Name of the fleet namespace to be created. Must comply with RFC 1123 - (up to 63 characters, alphanumeric and '-') - -FLAGS - Scope resource - The group of arguments defining the Fleet Scope. 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 --scope on the command line with a fully - specified name; - ◆ provide the argument --project on the command line; - ◆ set the property core/project. - - To set the location attribute: - ◆ provide the argument --scope on the command line with a fully - specified name; - ◆ global is the only supported location. - - --scope=SCOPE - ID of the scope or fully qualified identifier for the scope. - - To set the scope attribute: - ▸ provide the argument --scope on the command line. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --configuration, --flags-file, --flatten, --format, - --help, --impersonate-service-account, --log-http, --project, --quiet, - --trace-token, --user-output-enabled, --verbosity. - - Run $ gcloud help for details. - -NOTES - This command is currently in 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 container hub namespaces create - diff --git a/gcloud/alpha/container/hub/namespaces/delete b/gcloud/alpha/container/hub/namespaces/delete deleted file mode 100644 index 9e60f6485..000000000 --- a/gcloud/alpha/container/hub/namespaces/delete +++ /dev/null @@ -1,43 +0,0 @@ -NAME - gcloud alpha container hub namespaces delete - delete a fleet namespace - -SYNOPSIS - gcloud alpha container hub namespaces delete NAME [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (ALPHA) This command can fail for the following reasons: - ▪ The project specified does not exist. - ▪ The namespace specified does not exist. - ▪ The caller does not have permission to access the given project or - namespace. - -EXAMPLES - To delete fleet namespace NAMESPACE in the active project: - - $ gcloud alpha container hub namespaces delete NAMESPACE - - To delete fleet namespace NAMESPACE in project PROJECT_ID: - - $ gcloud alpha container hub namespaces delete NAMESPACE \ - --project=PROJECT_ID - -POSITIONAL ARGUMENTS - NAME - Name of the fleet namespace to be deleted. - -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 container hub namespaces delete - diff --git a/gcloud/alpha/container/hub/namespaces/describe b/gcloud/alpha/container/hub/namespaces/describe deleted file mode 100644 index d085301eb..000000000 --- a/gcloud/alpha/container/hub/namespaces/describe +++ /dev/null @@ -1,43 +0,0 @@ -NAME - gcloud alpha container hub namespaces describe - show fleet namespace info - -SYNOPSIS - gcloud alpha container hub namespaces describe NAME [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (ALPHA) This command can fail for the following reasons: - ▪ The project specified does not exist. - ▪ The namespace specified does not exist in the project. - ▪ The caller does not have permission to access the project or - namespace. - -EXAMPLES - To print metadata for the namespace NAMESPACE in the active project, run: - - $ gcloud alpha container hub namespaces describe NAMESPACE - - To print metadata for the namespace NAMESPACE in project PROJECT_ID, run: - - $ gcloud alpha container hub namespaces describe NAMESPACE \ - --project=PROJECT_ID - -POSITIONAL ARGUMENTS - NAME - Name of the fleet namespace to be described. - -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 container hub namespaces describe - diff --git a/gcloud/alpha/container/hub/namespaces/get-credentials b/gcloud/alpha/container/hub/namespaces/get-credentials deleted file mode 100644 index abf049181..000000000 --- a/gcloud/alpha/container/hub/namespaces/get-credentials +++ /dev/null @@ -1,60 +0,0 @@ -NAME - gcloud alpha container hub namespaces get-credentials - fetch credentials - for a membership with a particular namespace - -SYNOPSIS - gcloud alpha container hub namespaces get-credentials NAMESPACE - [--membership=MEMBERSHIP] [--membership-location=MEMBERSHIP_LOCATION] - [--set-namespace-in-config=SET_NAMESPACE_IN_CONFIG] - [GCLOUD_WIDE_FLAG ...] - -EXAMPLES - Get the Connect Gateway kubeconfig for global membership MEMBERSHIP, using - namespace NAMESPACE in the config: - - $ gcloud alpha container hub namespaces get-credentials NAMESPACE \ - --membership=MEMBERSHIP --membership-location=global \ - --set-namespace-in-config=true - - Get the Connect Gateway kubeconfig for global membership MEMBERSHIP: - - $ gcloud alpha container hub namespaces get-credentials NAMESPACE \ - --membership=MEMBERSHIP --membership-location=global - -POSITIONAL ARGUMENTS - NAMESPACE - Name of the namespace for which to get access to memberships. - -FLAGS - --membership=MEMBERSHIP - Membership ID to get credentials from. If not provided, a prompt will - offer a list of memberships in the fleet. - - --membership-location=MEMBERSHIP_LOCATION - The location of the membership resource, e.g. us-central1. If not - specified, defaults to global. - - --set-namespace-in-config=SET_NAMESPACE_IN_CONFIG - If true, the default namespace for the context in the generated - kubeconfig will be set to the Fleet namespace (i.e. the name given as - the positional argument in this command). - - Otherwise, no default namespace will be set, functioning the same as - gcloud container fleet memberships get-credentials. - -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 container hub namespaces get-credentials - diff --git a/gcloud/alpha/container/hub/namespaces/help b/gcloud/alpha/container/hub/namespaces/help deleted file mode 100644 index bb143e807..000000000 --- a/gcloud/alpha/container/hub/namespaces/help +++ /dev/null @@ -1,60 +0,0 @@ -NAME - gcloud alpha container hub namespaces - fleet namespaces are the fleet - equivalent of k8s cluster namespaces - -SYNOPSIS - gcloud alpha container hub namespaces GROUP | COMMAND - [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (ALPHA) This command group allows for manipulation of fleet namespaces. - -EXAMPLES - Manage fleet namespaces: - - $ gcloud alpha container hub namespaces --help - - Manage RBAC RoleBindings in a fleet namespace: - - $ gcloud alpha container hub namespaces rbacrolebindings --help - -GCLOUD WIDE FLAGS - These flags are available to all commands: --help. - - Run $ gcloud help for details. - -GROUPS - GROUP is one of the following: - - rbacrolebindings - (ALPHA) Fleet namespace RBAC RoleBindings for permissions. - -COMMANDS - COMMAND is one of the following: - - create - (ALPHA) Create a fleet namespace. - - delete - (ALPHA) Delete a fleet namespace. - - describe - (ALPHA) Show fleet namespace info. - - get-credentials - (ALPHA) Fetch credentials for a membership with a particular namespace. - - list - (ALPHA) List fleet namespaces in a project. - - update - (ALPHA) Update a fleet namespace. - -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 container hub namespaces - diff --git a/gcloud/alpha/container/hub/namespaces/list b/gcloud/alpha/container/hub/namespaces/list deleted file mode 100644 index 0306abc95..000000000 --- a/gcloud/alpha/container/hub/namespaces/list +++ /dev/null @@ -1,71 +0,0 @@ -NAME - gcloud alpha container hub namespaces list - list fleet namespaces in a - project - -SYNOPSIS - gcloud alpha container hub namespaces list [--filter=EXPRESSION] - [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] - [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (ALPHA) This command can fail for the following reasons: - ▪ The project specified does not exist. - ▪ The user does not have access to the project specified. - -EXAMPLES - The following command lists namespaces in the active project: - - $ gcloud alpha container hub namespaces list - - The following command lists namespaces in project PROJECT_ID: - - $ gcloud alpha container hub namespaces list --project=PROJECT_ID - -LIST COMMAND FLAGS - --filter=EXPRESSION - Apply a Boolean filter EXPRESSION to each resource item to be listed. - If the expression evaluates True, then that item is listed. For more - details and examples of filter expressions, run $ gcloud topic filters. - This flag interacts with other flags that are applied in this order: - --flatten, --sort-by, --filter, --limit. - - --limit=LIMIT - Maximum number of resources to list. The default is unlimited. This - flag interacts with other flags that are applied in this order: - --flatten, --sort-by, --filter, --limit. - - --page-size=PAGE_SIZE - Some services group resource list output into pages. This flag - specifies the maximum number of resources per page. The default is - determined by the service if it supports paging, otherwise it is - unlimited (no paging). Paging may be applied before or after --filter - and --limit depending on the service. - - --sort-by=[FIELD,...] - Comma-separated list of resource field key names to sort by. The - default order is ascending. Prefix a field with ``~'' for descending - order on that field. This flag interacts with other flags that are - applied in this order: --flatten, --sort-by, --filter, --limit. - - --uri - Print a list of resource URIs instead of the default output, and change - the command output to a list of URIs. If this flag is used with - --format, the formatting is applied on this URI list. To display URIs - alongside other keys instead, use the uri() transform. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --configuration, --flags-file, --flatten, --format, - --help, --impersonate-service-account, --log-http, --project, --quiet, - --trace-token, --user-output-enabled, --verbosity. - - Run $ gcloud help for details. - -NOTES - This command is currently in alpha and might change without notice. If this - command fails with API permission errors despite specifying the correct - project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: - - $ gcloud beta container hub namespaces list - diff --git a/gcloud/alpha/container/hub/namespaces/rbacrolebindings/create b/gcloud/alpha/container/hub/namespaces/rbacrolebindings/create deleted file mode 100644 index c102cb88b..000000000 --- a/gcloud/alpha/container/hub/namespaces/rbacrolebindings/create +++ /dev/null @@ -1,97 +0,0 @@ -NAME - gcloud alpha container hub namespaces rbacrolebindings create - create an - RBAC RoleBinding - -SYNOPSIS - gcloud alpha container hub namespaces rbacrolebindings create - (NAME : --location=LOCATION --namespace=NAMESPACE) --role=ROLE - (--group=GROUP | --user=USER) [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (ALPHA) This command can fail for the following reasons: - ▪ The RBAC RoleBinding already exists. - ▪ The caller does not have permission to access the given namespace. - -EXAMPLES - To create an admin RBAC RoleBinding RBRB in namespace NAMESPACE for user - person@google.com, run: - - $ gcloud alpha container hub namespaces rbacrolebindings create \ - RBRB --namespace=NAMESPACE --role=admin --user=person@google.com - - To create a viewer RBAC RoleBinding RBRB in namespace NAMESPACE for group - people@google.com, run: - - $ gcloud alpha container hub namespaces rbacrolebindings create \ - RBRB --namespace=NAMESPACE --role=viewer \ - --group=people@google.com - -POSITIONAL ARGUMENTS - Rbacrolebinding resource - The group of arguments defining an - RBACRoleBinding. 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 NAME 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. - - NAME - ID of the rbacrolebinding or fully qualified identifier for the - rbacrolebinding. - - To set the rbacrolebinding attribute: - ▸ provide the argument NAME on the command line. - - This positional argument must be specified if any of the other - arguments in this group are specified. - - --location=LOCATION - Location for the rbacrolebinding. - - To set the location attribute: - ▸ provide the argument NAME on the command line with a fully - specified name; - ▸ provide the argument --location on the command line; - ▸ set the property gkehub/location. - - --namespace=NAMESPACE - Name of the rbacrolebinding. - - To set the namespace attribute: - ▸ provide the argument NAME on the command line with a fully - specified name; - ▸ provide the argument --namespace on the command line. - -REQUIRED FLAGS - --role=ROLE - Role to assign. ROLE must be one of: admin, edit, view. - - Exactly one of these must be specified: - - --group=GROUP - Group for the RoleBinding. - - --user=USER - User for the RoleBinding. - -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 container hub namespaces rbacrolebindings create - diff --git a/gcloud/alpha/container/hub/namespaces/rbacrolebindings/delete b/gcloud/alpha/container/hub/namespaces/rbacrolebindings/delete deleted file mode 100644 index f629a52a4..000000000 --- a/gcloud/alpha/container/hub/namespaces/rbacrolebindings/delete +++ /dev/null @@ -1,78 +0,0 @@ -NAME - gcloud alpha container hub namespaces rbacrolebindings delete - delete a - fleet namespace RBAC RoleBinding - -SYNOPSIS - gcloud alpha container hub namespaces rbacrolebindings delete - (NAME : --location=LOCATION --namespace=NAMESPACE) - [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (ALPHA) This command can fail for the following reasons: - ▪ The RoleBinding specified does not exist. - ▪ The caller does not have permission to access the given RoleBinding. - -EXAMPLES - To delete RBAC RoleBinding RBRB in namespace NAMESPACE in the active - project: - - $ gcloud alpha container hub namespaces rbacrolebindings delete \ - RBRB --namespace=NAMESPACE - -POSITIONAL ARGUMENTS - Rbacrolebinding resource - The group of arguments defining an - RBACRoleBinding. 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 NAME 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. - - NAME - ID of the rbacrolebinding or fully qualified identifier for the - rbacrolebinding. - - To set the rbacrolebinding attribute: - ▸ provide the argument NAME on the command line. - - This positional argument must be specified if any of the other - arguments in this group are specified. - - --location=LOCATION - Location for the rbacrolebinding. - - To set the location attribute: - ▸ provide the argument NAME on the command line with a fully - specified name; - ▸ provide the argument --location on the command line; - ▸ set the property gkehub/location. - - --namespace=NAMESPACE - Name of the rbacrolebinding. - - To set the namespace attribute: - ▸ provide the argument NAME on the command line with a fully - specified name; - ▸ provide the argument --namespace on the command line. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --configuration, --flags-file, --flatten, --format, - --help, --impersonate-service-account, --log-http, --project, --quiet, - --trace-token, --user-output-enabled, --verbosity. - - Run $ gcloud help for details. - -NOTES - This command is currently in 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 container hub namespaces rbacrolebindings delete - diff --git a/gcloud/alpha/container/hub/namespaces/rbacrolebindings/describe b/gcloud/alpha/container/hub/namespaces/rbacrolebindings/describe deleted file mode 100644 index a80da10c3..000000000 --- a/gcloud/alpha/container/hub/namespaces/rbacrolebindings/describe +++ /dev/null @@ -1,78 +0,0 @@ -NAME - gcloud alpha container hub namespaces rbacrolebindings describe - show - fleet namespace RBAC RoleBinding information - -SYNOPSIS - gcloud alpha container hub namespaces rbacrolebindings describe - (NAME : --location=LOCATION --namespace=NAMESPACE) - [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (ALPHA) This command can fail for the following reasons: - ▪ The RoleBinding specified does not exist in the project. - ▪ The caller does not have permission to access the RoleBinding. - -EXAMPLES - To print metadata for RBAC RoleBinding RBRB in the namespace NAMESPACE, - run: - - $ gcloud alpha container hub namespaces rbacrolebindings describe \ - RBRB --namespace=NAMESPACE - -POSITIONAL ARGUMENTS - Rbacrolebinding resource - The group of arguments defining an - RBACRoleBinding. 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 NAME 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. - - NAME - ID of the rbacrolebinding or fully qualified identifier for the - rbacrolebinding. - - To set the rbacrolebinding attribute: - ▸ provide the argument NAME on the command line. - - This positional argument must be specified if any of the other - arguments in this group are specified. - - --location=LOCATION - Location for the rbacrolebinding. - - To set the location attribute: - ▸ provide the argument NAME on the command line with a fully - specified name; - ▸ provide the argument --location on the command line; - ▸ set the property gkehub/location. - - --namespace=NAMESPACE - Name of the rbacrolebinding. - - To set the namespace attribute: - ▸ provide the argument NAME on the command line with a fully - specified name; - ▸ provide the argument --namespace on the command line. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --configuration, --flags-file, --flatten, --format, - --help, --impersonate-service-account, --log-http, --project, --quiet, - --trace-token, --user-output-enabled, --verbosity. - - Run $ gcloud help for details. - -NOTES - This command is currently in 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 container hub namespaces rbacrolebindings describe - diff --git a/gcloud/alpha/container/hub/namespaces/rbacrolebindings/help b/gcloud/alpha/container/hub/namespaces/rbacrolebindings/help deleted file mode 100644 index a604dd124..000000000 --- a/gcloud/alpha/container/hub/namespaces/rbacrolebindings/help +++ /dev/null @@ -1,48 +0,0 @@ -NAME - gcloud alpha container hub namespaces rbacrolebindings - fleet namespace - RBAC RoleBindings for permissions - -SYNOPSIS - gcloud alpha container hub namespaces rbacrolebindings COMMAND - [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (ALPHA) This command group allows for manipulation of fleet namespace RBAC - RoleBindings. - -EXAMPLES - Manage RBAC RoleBindings: - - $ gcloud alpha container hub namespaces rbacrolebindings --help - -GCLOUD WIDE FLAGS - These flags are available to all commands: --help. - - Run $ gcloud help for details. - -COMMANDS - COMMAND is one of the following: - - create - (ALPHA) Create an RBAC RoleBinding. - - delete - (ALPHA) Delete a fleet namespace RBAC RoleBinding. - - describe - (ALPHA) Show fleet namespace RBAC RoleBinding information. - - list - (ALPHA) List RBAC RoleBindings in a fleet namespace. - - update - (ALPHA) Update a fleet namespace RBAC RoleBinding. - -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 container hub namespaces rbacrolebindings - diff --git a/gcloud/alpha/container/hub/namespaces/rbacrolebindings/list b/gcloud/alpha/container/hub/namespaces/rbacrolebindings/list deleted file mode 100644 index c3a898b16..000000000 --- a/gcloud/alpha/container/hub/namespaces/rbacrolebindings/list +++ /dev/null @@ -1,74 +0,0 @@ -NAME - gcloud alpha container hub namespaces rbacrolebindings list - list RBAC - RoleBindings in a fleet namespace - -SYNOPSIS - gcloud alpha container hub namespaces rbacrolebindings list - --namespace=NAMESPACE [--filter=EXPRESSION] [--limit=LIMIT] - [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] - [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (ALPHA) This command can fail for the following reasons: - ▪ The namespace specified does not exist. - ▪ The user does not have access to the specified namespace. - -EXAMPLES - The following command lists RBAC RoleBindings in namespace NAMESPACE in - project PROJECT_ID: - - $ gcloud alpha container hub namespaces rbacrolebindings list \ - --namespace=NAMESPACE --project=PROJECT_ID - -REQUIRED FLAGS - --namespace=NAMESPACE - Name of the fleet namespace to list RBAC RoleBindings from. - -LIST COMMAND FLAGS - --filter=EXPRESSION - Apply a Boolean filter EXPRESSION to each resource item to be listed. - If the expression evaluates True, then that item is listed. For more - details and examples of filter expressions, run $ gcloud topic filters. - This flag interacts with other flags that are applied in this order: - --flatten, --sort-by, --filter, --limit. - - --limit=LIMIT - Maximum number of resources to list. The default is unlimited. This - flag interacts with other flags that are applied in this order: - --flatten, --sort-by, --filter, --limit. - - --page-size=PAGE_SIZE - Some services group resource list output into pages. This flag - specifies the maximum number of resources per page. The default is - determined by the service if it supports paging, otherwise it is - unlimited (no paging). Paging may be applied before or after --filter - and --limit depending on the service. - - --sort-by=[FIELD,...] - Comma-separated list of resource field key names to sort by. The - default order is ascending. Prefix a field with ``~'' for descending - order on that field. This flag interacts with other flags that are - applied in this order: --flatten, --sort-by, --filter, --limit. - - --uri - Print a list of resource URIs instead of the default output, and change - the command output to a list of URIs. If this flag is used with - --format, the formatting is applied on this URI list. To display URIs - alongside other keys instead, use the uri() transform. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --configuration, --flags-file, --flatten, --format, - --help, --impersonate-service-account, --log-http, --project, --quiet, - --trace-token, --user-output-enabled, --verbosity. - - Run $ gcloud help for details. - -NOTES - This command is currently in alpha and might change without notice. If this - command fails with API permission errors despite specifying the correct - project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: - - $ gcloud beta container hub namespaces rbacrolebindings list - diff --git a/gcloud/alpha/container/hub/namespaces/rbacrolebindings/update b/gcloud/alpha/container/hub/namespaces/rbacrolebindings/update deleted file mode 100644 index 57cb2cf2f..000000000 --- a/gcloud/alpha/container/hub/namespaces/rbacrolebindings/update +++ /dev/null @@ -1,97 +0,0 @@ -NAME - gcloud alpha container hub namespaces rbacrolebindings update - update a - fleet namespace RBAC RoleBinding - -SYNOPSIS - gcloud alpha container hub namespaces rbacrolebindings update - (NAME : --location=LOCATION --namespace=NAMESPACE) [--role=ROLE] - [--group=GROUP | --user=USER] [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (ALPHA) This command can fail for the following reasons: - ▪ The RoleBinding does not exist in the project. - ▪ The caller does not have permission to access the RoleBinding. - -EXAMPLES - To update the RBAC RoleBinding RBRB in namespace NAMESPACE in the active - project to the viewer role: - - $ gcloud alpha container hub namespaces rbacrolebindings update \ - RBRB --namespace=NAMESPACE --role=viewer - - To update the RBAC RoleBinding RBRB in namespace NAMESPACE in the active - project to the user someone@google.com: - - $ gcloud alpha container hub namespaces rbacrolebindings update \ - RBRB --namespace=NAMESPACE --user=someone@google.com - -POSITIONAL ARGUMENTS - Rbacrolebinding resource - The group of arguments defining an - RBACRoleBinding. 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 NAME 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. - - NAME - ID of the rbacrolebinding or fully qualified identifier for the - rbacrolebinding. - - To set the rbacrolebinding attribute: - ▸ provide the argument NAME on the command line. - - This positional argument must be specified if any of the other - arguments in this group are specified. - - --location=LOCATION - Location for the rbacrolebinding. - - To set the location attribute: - ▸ provide the argument NAME on the command line with a fully - specified name; - ▸ provide the argument --location on the command line; - ▸ set the property gkehub/location. - - --namespace=NAMESPACE - Name of the rbacrolebinding. - - To set the namespace attribute: - ▸ provide the argument NAME on the command line with a fully - specified name; - ▸ provide the argument --namespace on the command line. - -FLAGS - --role=ROLE - Role for the RBACRoleBinding to update to. ROLE must be one of: admin, - edit, view. - - At most one of these can be specified: - - --group=GROUP - Group for the RBACRoleBinding to update to. - - --user=USER - User for the RBACRoleBinding to update to. - -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 container hub namespaces rbacrolebindings update - diff --git a/gcloud/alpha/container/hub/namespaces/update b/gcloud/alpha/container/hub/namespaces/update deleted file mode 100644 index d93409e6d..000000000 --- a/gcloud/alpha/container/hub/namespaces/update +++ /dev/null @@ -1,66 +0,0 @@ -NAME - gcloud alpha container hub namespaces update - update a fleet namespace - -SYNOPSIS - gcloud alpha container hub namespaces update NAME [--scope=SCOPE] - [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (ALPHA) This command can fail for the following reasons: - ▪ The project specified does not exist. - ▪ The fleet namespace does not exist in the project. - ▪ The caller does not have permission to access the project or - namespace. - -EXAMPLES - To update the namespace NAMESPACE in the active project: - - $ gcloud alpha container hub namespaces update NAMESPACE - - To update the namespace NAMESPACE in project PROJECT_ID: - - $ gcloud alpha container hub namespaces update NAMESPACE \ - --project=PROJECT_ID - -POSITIONAL ARGUMENTS - NAME - Name of the namespace to be updated. - -FLAGS - Scope resource - The group of arguments defining the Fleet Scope. 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 --scope on the command line with a fully - specified name; - ◆ provide the argument --project on the command line; - ◆ set the property core/project. - - To set the location attribute: - ◆ provide the argument --scope on the command line with a fully - specified name; - ◆ global is the only supported location. - - --scope=SCOPE - ID of the scope or fully qualified identifier for the scope. - - To set the scope attribute: - ▸ provide the argument --scope on the command line. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --configuration, --flags-file, --flatten, --format, - --help, --impersonate-service-account, --log-http, --project, --quiet, - --trace-token, --user-output-enabled, --verbosity. - - Run $ gcloud help for details. - -NOTES - This command is currently in 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 container hub namespaces update - diff --git a/gcloud/alpha/container/node-pools/create b/gcloud/alpha/container/node-pools/create index 9bc986b0a..63f648efd 100644 --- a/gcloud/alpha/container/node-pools/create +++ b/gcloud/alpha/container/node-pools/create @@ -54,9 +54,9 @@ SYNOPSIS --total-max-nodes=TOTAL_MAX_NODES --total-min-nodes=TOTAL_MIN_NODES] [--enable-best-effort-provision --min-provision-nodes=MIN_PROVISION_NODES] - [--ephemeral-storage=[local-ssd-count=LOCAL-SSD-COUNT] - | --ephemeral-storage-local-ssd=[count=COUNT] - | --local-nvme-ssd-block=[count=COUNT] + [--ephemeral-storage[=[local-ssd-count=LOCAL-SSD-COUNT]] + | --ephemeral-storage-local-ssd[=[count=COUNT]] + | --local-nvme-ssd-block[=[count=COUNT]] | --local-ssd-count=LOCAL_SSD_COUNT | --local-ssd-volumes=[[count=COUNT], [type=TYPE],[format=FORMAT],...]] @@ -838,7 +838,7 @@ FLAGS At most one of these can be specified: - --ephemeral-storage=[local-ssd-count=LOCAL-SSD-COUNT] + --ephemeral-storage[=[local-ssd-count=LOCAL-SSD-COUNT]] Parameters for the ephemeral storage filesystem. If unspecified, ephemeral storage is backed by the boot disk. @@ -855,7 +855,7 @@ FLAGS See https://cloud.google.com/compute/docs/disks/local-ssd for more information. - --ephemeral-storage-local-ssd=[count=COUNT] + --ephemeral-storage-local-ssd[=[count=COUNT]] Parameters for the ephemeral storage filesystem. If unspecified, ephemeral storage is backed by the boot disk. @@ -871,7 +871,7 @@ FLAGS See https://cloud.google.com/compute/docs/disks/local-ssd for more information. - --local-nvme-ssd-block=[count=COUNT] + --local-nvme-ssd-block[=[count=COUNT]] Adds the requested local SSDs on all nodes in default node pool(s) in the new cluster. diff --git a/gcloud/alpha/container/vmware/clusters/create b/gcloud/alpha/container/vmware/clusters/create index 1e68824f5..7b9b8f008 100644 --- a/gcloud/alpha/container/vmware/clusters/create +++ b/gcloud/alpha/container/vmware/clusters/create @@ -34,6 +34,12 @@ SYNOPSIS [--cpus=CPUS --enable-auto-resize --memory=MEMORY --replicas=REPLICAS] [--disable-control-plane-v2 | --enable-control-plane-v2] [--enable-advanced-networking --enable-dataplane-v2] + [--vcenter-ca-cert-data=VCENTER_CA_CERT_DATA + --vcenter-cluster=VCENTER_CLUSTER + --vcenter-datacenter=VCENTER_DATACENTER + --vcenter-datastore=VCENTER_DATASTORE --vcenter-folder=VCENTER_FOLDER + --vcenter-resource-pool=VCENTER_RESOURCE_POOL + --vcenter-storage-policy-name=VCENTER_STORAGE_POLICY_NAME] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -378,6 +384,30 @@ OPTIONAL FLAGS --enable-dataplane-v2 If set, enables Dataplane V2. + vCenter configurations for the cluster. If not specified, it is inherited + from the admin cluster. + + --vcenter-ca-cert-data=VCENTER_CA_CERT_DATA + Name of the vCenter CA certificate public key for SSL verification. + + --vcenter-cluster=VCENTER_CLUSTER + Name of the vCenter cluster for the user cluster. + + --vcenter-datacenter=VCENTER_DATACENTER + Name of the vCenter datacenter for the user cluster. + + --vcenter-datastore=VCENTER_DATASTORE + Name of the vCenter datastore for the user cluster. + + --vcenter-folder=VCENTER_FOLDER + Name of the vCenter folder for the user cluster. + + --vcenter-resource-pool=VCENTER_RESOURCE_POOL + Name of the vCenter resource pool for the user cluster. + + --vcenter-storage-policy-name=VCENTER_STORAGE_POLICY_NAME + Name of the vCenter storage policy for the user cluster. + 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/database-migration/connection-profiles/create/cloudsql b/gcloud/alpha/database-migration/connection-profiles/create/cloudsql index e754f8cd1..46e609e8a 100644 --- a/gcloud/alpha/database-migration/connection-profiles/create/cloudsql +++ b/gcloud/alpha/database-migration/connection-profiles/create/cloudsql @@ -76,7 +76,7 @@ REQUIRED FLAGS --database-version=DATABASE_VERSION Database engine type and version. DATABASE_VERSION must be one of: MYSQL_5_7, MYSQL_5_6, MYSQL_8_0, POSTGRES_9_6, POSTGRES_10, - POSTGRES_11, POSTGRES_12, POSTGRES_13, POSTGRES_14. + POSTGRES_11, POSTGRES_12, POSTGRES_13, POSTGRES_14, POSTGRES_15. Connection profile resource - Database Migration Service source connection profile ID. This represents a Cloud resource. (NOTE) Some attributes are diff --git a/gcloud/alpha/database-migration/connection-profiles/create/mysql b/gcloud/alpha/database-migration/connection-profiles/create/mysql index 0c17cf33f..0af94d0e9 100644 --- a/gcloud/alpha/database-migration/connection-profiles/create/mysql +++ b/gcloud/alpha/database-migration/connection-profiles/create/mysql @@ -88,9 +88,9 @@ FLAGS --ca-certificate=CA_CERTIFICATE x509 PEM-encoded certificate of the CA that signed the database - server's certificate. The replica will use this certificate to verify - it's connecting to the correct host. Database Migration Service - encrypts the value when storing it. + server's certificate. Database Migration Service will use this + certificate to verify it's connecting to the correct host. Database + Migration Service encrypts the value when storing it. --certificate=CERTIFICATE x509 PEM-encoded certificate that will be used by the replica to diff --git a/gcloud/alpha/database-migration/connection-profiles/update b/gcloud/alpha/database-migration/connection-profiles/update index 57458e9c7..291808043 100644 --- a/gcloud/alpha/database-migration/connection-profiles/update +++ b/gcloud/alpha/database-migration/connection-profiles/update @@ -63,9 +63,9 @@ POSITIONAL ARGUMENTS FLAGS --ca-certificate=CA_CERTIFICATE x509 PEM-encoded certificate of the CA that signed the database - server's certificate. The replica will use this certificate to verify - it's connecting to the correct host. Database Migration Service - encrypts the value when storing it. + server's certificate. Database Migration Service will use this + certificate to verify it's connecting to the correct host. Database + Migration Service encrypts the value when storing it. --certificate=CERTIFICATE x509 PEM-encoded certificate that will be used by the replica to diff --git a/gcloud/alpha/dataproc/clusters/create b/gcloud/alpha/dataproc/clusters/create index a10d046d1..4ad3da2f6 100644 --- a/gcloud/alpha/dataproc/clusters/create +++ b/gcloud/alpha/dataproc/clusters/create @@ -35,6 +35,8 @@ SYNOPSIS [--secondary-worker-boot-disk-size=SECONDARY_WORKER_BOOT_DISK_SIZE] [--secondary-worker-boot-disk-type=SECONDARY_WORKER_BOOT_DISK_TYPE] [--secondary-worker-local-ssd-interface=SECONDARY_WORKER_LOCAL_SSD_INTERFACE] + [--secondary-worker-machine-types=type=MACHINE_TYPE[, + type=MACHINE_TYPE...][,rank=RANK]] [--secondary-worker-standard-capacity-base=SECONDARY_WORKER_STANDARD_CAPACITY_BASE] [--shielded-integrity-monitoring] [--shielded-secure-boot] [--shielded-vtpm] [--temp-bucket=TEMP_BUCKET] @@ -356,6 +358,11 @@ FLAGS Interface to use to attach local SSDs to each secondary worker in a cluster. + --secondary-worker-machine-types=type=MACHINE_TYPE[,type=MACHINE_TYPE...][,rank=RANK] + Types of machines with optional rank for secondary workers to use. + Defaults to server-specified.eg. + --secondary-worker-machine-types="type=e2-standard-8,type=t2d-standard-8,rank=0" + --secondary-worker-standard-capacity-base=SECONDARY_WORKER_STANDARD_CAPACITY_BASE The number of standard VMs in the Spot and Standard Mix feature. diff --git a/gcloud/alpha/dataproc/workflow-templates/set-managed-cluster b/gcloud/alpha/dataproc/workflow-templates/set-managed-cluster index 17c7953d4..8b49567f3 100644 --- a/gcloud/alpha/dataproc/workflow-templates/set-managed-cluster +++ b/gcloud/alpha/dataproc/workflow-templates/set-managed-cluster @@ -28,6 +28,8 @@ SYNOPSIS [--secondary-worker-boot-disk-size=SECONDARY_WORKER_BOOT_DISK_SIZE] [--secondary-worker-boot-disk-type=SECONDARY_WORKER_BOOT_DISK_TYPE] [--secondary-worker-local-ssd-interface=SECONDARY_WORKER_LOCAL_SSD_INTERFACE] + [--secondary-worker-machine-types=type=MACHINE_TYPE[, + type=MACHINE_TYPE...][,rank=RANK]] [--secondary-worker-standard-capacity-base=SECONDARY_WORKER_STANDARD_CAPACITY_BASE] [--shielded-integrity-monitoring] [--shielded-secure-boot] [--shielded-vtpm] [--temp-bucket=TEMP_BUCKET] @@ -288,6 +290,11 @@ FLAGS Interface to use to attach local SSDs to each secondary worker in a cluster. + --secondary-worker-machine-types=type=MACHINE_TYPE[,type=MACHINE_TYPE...][,rank=RANK] + Types of machines with optional rank for secondary workers to use. + Defaults to server-specified.eg. + --secondary-worker-machine-types="type=e2-standard-8,type=t2d-standard-8,rank=0" + --secondary-worker-standard-capacity-base=SECONDARY_WORKER_STANDARD_CAPACITY_BASE The number of standard VMs in the Spot and Standard Mix feature. diff --git a/gcloud/alpha/functions/deploy b/gcloud/alpha/functions/deploy index 13353c7a8..60c6c6a25 100644 --- a/gcloud/alpha/functions/deploy +++ b/gcloud/alpha/functions/deploy @@ -636,8 +636,8 @@ FLAGS The provided attribute/value pair will be used with the match-path-pattern operator to configure the trigger, see https://cloud.google.com/eventarc/docs/reference/rest/v1/projects.locations.triggers#eventfilter - and http://cloud/eventarc/docs/path-patterns for more details about - on how to construct path patterns. + and https://cloud.google.com/eventarc/docs/path-patterns for more + details about on how to construct path patterns. For example, to filter on events for Compute Engine VMs in a given zone: diff --git a/gcloud/alpha/iam/workforce-pools/providers/create-oidc b/gcloud/alpha/iam/workforce-pools/providers/create-oidc index fa199546f..8eb3c8a34 100644 --- a/gcloud/alpha/iam/workforce-pools/providers/create-oidc +++ b/gcloud/alpha/iam/workforce-pools/providers/create-oidc @@ -12,7 +12,8 @@ SYNOPSIS : --web-sso-additional-scopes=[WEB_SSO_ADDITIONAL_SCOPES,...]) [--async] [--attribute-condition=ATTRIBUTE_CONDITION] [--client-secret-value=CLIENT_SECRET_VALUE] [--description=DESCRIPTION] - [--disabled] [--display-name=DISPLAY_NAME] [GCLOUD_WIDE_FLAG ...] + [--disabled] [--display-name=DISPLAY_NAME] + [--jwk-json-path=JWK_JSON_PATH] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Create a new OIDC workforce pool provider. @@ -33,7 +34,8 @@ EXAMPLES --issuer-uri="https://test-idp.com" \ --web-sso-response-type="code" \ --web-sso-assertion-claims-behavior="merge-user-info-over-id-tok\ - en-claims" --web-sso-additional-scopes="groups,photos" + en-claims" --web-sso-additional-scopes="groups,photos" \ + --jwk-json-path="path/to/jwk.json" POSITIONAL ARGUMENTS Workforce pool provider resource - The workforce pool provider to create. @@ -244,6 +246,26 @@ OPTIONAL FLAGS A display name for the workforce pool provider. Cannot exceed 32 characters in length. + --jwk-json-path=JWK_JSON_PATH + Optional file containing JSON Web Key (JWK) public keys. The file + format must follow JWK specifications + (https://www.rfc-editor.org/rfc/rfc7517#section-4). Example file + format: { + "keys": [ + { + "kty": "RSA/EC", + "alg": "", + "use": "sig", + "kid": "", + "n": "", + "e": "", + "x": "", + "y": "", + "crv": "" + } + ] + } + 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/iam/workforce-pools/providers/update-oidc b/gcloud/alpha/iam/workforce-pools/providers/update-oidc index db4c88ae3..d80328983 100644 --- a/gcloud/alpha/iam/workforce-pools/providers/update-oidc +++ b/gcloud/alpha/iam/workforce-pools/providers/update-oidc @@ -8,7 +8,7 @@ SYNOPSIS [--async] [--attribute-condition=ATTRIBUTE_CONDITION] [--attribute-mapping=[KEY=VALUE,...]] [--client-id=CLIENT_ID] [--description=DESCRIPTION] [--disabled] [--display-name=DISPLAY_NAME] - [--issuer-uri=ISSUER_URI] + [--issuer-uri=ISSUER_URI] [--jwk-json-path=JWK_JSON_PATH] [--web-sso-additional-scopes=[WEB_SSO_ADDITIONAL_SCOPES,...]] [--web-sso-assertion-claims-behavior=WEB_SSO_ASSERTION_CLAIMS_BEHAVIOR] [--web-sso-response-type=WEB_SSO_RESPONSE_TYPE] @@ -34,7 +34,8 @@ EXAMPLES --issuer-uri="https://test-idp.com" \ --web-sso-response-type="code" \ --web-sso-assertion-claims-behavior="merge-user-info-over-id-tok\ - en-claims" --web-sso-additional-scopes="groups,photos" + en-claims" --web-sso-additional-scopes="groups,photos" \ + --jwk-json-path="path/to/jwk.json" POSITIONAL ARGUMENTS Workforce pool provider resource - The workforce pool provider to update. @@ -195,6 +196,26 @@ FLAGS --issuer-uri=ISSUER_URI The OIDC issuer URI. Must be a valid URI using the 'https' scheme. + --jwk-json-path=JWK_JSON_PATH + Optional file containing JSON Web Key (JWK) public keys. The file + format must follow JWK specifications + (https://www.rfc-editor.org/rfc/rfc7517#section-4). Example file + format: { + "keys": [ + { + "kty": "RSA/EC", + "alg": "", + "use": "sig", + "kid": "", + "n": "", + "e": "", + "x": "", + "y": "", + "crv": "" + } + ] + } + --web-sso-additional-scopes=[WEB_SSO_ADDITIONAL_SCOPES,...] Additional scopes to request for the OIDC authentication on top of scopes requested by default. By default, the openid, profile and email diff --git a/gcloud/alpha/looker/instances/create b/gcloud/alpha/looker/instances/create index 3eba18746..c17cf1a88 100644 --- a/gcloud/alpha/looker/instances/create +++ b/gcloud/alpha/looker/instances/create @@ -210,7 +210,7 @@ GCLOUD WIDE FLAGS API REFERENCE This command uses the looker/v1alpha1 API. The full documentation for this - API can be found at: https://looker.com/ + API can be found at: https://cloud.google.com/looker/docs/reference/rest/ NOTES This command is currently in alpha and might change without notice. If this diff --git a/gcloud/alpha/looker/instances/delete b/gcloud/alpha/looker/instances/delete index 2054a1c77..944db1da0 100644 --- a/gcloud/alpha/looker/instances/delete +++ b/gcloud/alpha/looker/instances/delete @@ -70,7 +70,7 @@ GCLOUD WIDE FLAGS API REFERENCE This command uses the looker/v1alpha1 API. The full documentation for this - API can be found at: https://looker.com/ + API can be found at: https://cloud.google.com/looker/docs/reference/rest/ NOTES This command is currently in alpha and might change without notice. If this diff --git a/gcloud/alpha/looker/instances/describe b/gcloud/alpha/looker/instances/describe index ba32a7bcb..fcaf895c2 100644 --- a/gcloud/alpha/looker/instances/describe +++ b/gcloud/alpha/looker/instances/describe @@ -65,7 +65,7 @@ GCLOUD WIDE FLAGS API REFERENCE This command uses the looker/v1alpha1 API. The full documentation for this - API can be found at: https://looker.com/ + API can be found at: https://cloud.google.com/looker/docs/reference/rest/ NOTES This command is currently in alpha and might change without notice. If this diff --git a/gcloud/alpha/looker/instances/list b/gcloud/alpha/looker/instances/list index ff3162955..a5c597467 100644 --- a/gcloud/alpha/looker/instances/list +++ b/gcloud/alpha/looker/instances/list @@ -77,7 +77,7 @@ GCLOUD WIDE FLAGS API REFERENCE This command uses the looker/v1alpha1 API. The full documentation for this - API can be found at: https://looker.com/ + API can be found at: https://cloud.google.com/looker/docs/reference/rest/ NOTES This command is currently in alpha and might change without notice. If this diff --git a/gcloud/alpha/looker/instances/restart b/gcloud/alpha/looker/instances/restart index bc7b0c8ea..182fc1e96 100644 --- a/gcloud/alpha/looker/instances/restart +++ b/gcloud/alpha/looker/instances/restart @@ -67,7 +67,7 @@ GCLOUD WIDE FLAGS API REFERENCE This command uses the looker/v1alpha1 API. The full documentation for this - API can be found at: https://looker.com/ + API can be found at: https://cloud.google.com/looker/docs/reference/rest/ NOTES This command is currently in alpha and might change without notice. If this diff --git a/gcloud/alpha/looker/instances/update b/gcloud/alpha/looker/instances/update index b947f6be8..854e86b06 100644 --- a/gcloud/alpha/looker/instances/update +++ b/gcloud/alpha/looker/instances/update @@ -186,7 +186,7 @@ GCLOUD WIDE FLAGS API REFERENCE This command uses the looker/v1alpha1 API. The full documentation for this - API can be found at: https://looker.com/ + API can be found at: https://cloud.google.com/looker/docs/reference/rest/ NOTES This command is currently in alpha and might change without notice. If this diff --git a/gcloud/alpha/looker/operations/cancel b/gcloud/alpha/looker/operations/cancel index ff0f73dd2..8d2d87f3f 100644 --- a/gcloud/alpha/looker/operations/cancel +++ b/gcloud/alpha/looker/operations/cancel @@ -58,7 +58,7 @@ GCLOUD WIDE FLAGS API REFERENCE This command uses the looker/v1alpha1 API. The full documentation for this - API can be found at: https://looker.com/ + API can be found at: https://cloud.google.com/looker/docs/reference/rest/ NOTES This command is currently in alpha and might change without notice. If this diff --git a/gcloud/alpha/looker/operations/describe b/gcloud/alpha/looker/operations/describe index 97cd4fc06..8265641ac 100644 --- a/gcloud/alpha/looker/operations/describe +++ b/gcloud/alpha/looker/operations/describe @@ -64,7 +64,7 @@ GCLOUD WIDE FLAGS API REFERENCE This command uses the looker/v1alpha1 API. The full documentation for this - API can be found at: https://looker.com/ + API can be found at: https://cloud.google.com/looker/docs/reference/rest/ NOTES This command is currently in alpha and might change without notice. If this diff --git a/gcloud/alpha/looker/operations/list b/gcloud/alpha/looker/operations/list index 0694e2149..f043fc47e 100644 --- a/gcloud/alpha/looker/operations/list +++ b/gcloud/alpha/looker/operations/list @@ -77,7 +77,7 @@ GCLOUD WIDE FLAGS API REFERENCE This command uses the looker/v1alpha1 API. The full documentation for this - API can be found at: https://looker.com/ + API can be found at: https://cloud.google.com/looker/docs/reference/rest/ NOTES This command is currently in alpha and might change without notice. If this diff --git a/gcloud/alpha/memcache/instances/create b/gcloud/alpha/memcache/instances/create index 04f7a8fbe..a7bbc4ffb 100644 --- a/gcloud/alpha/memcache/instances/create +++ b/gcloud/alpha/memcache/instances/create @@ -108,10 +108,12 @@ OPTIONAL FLAGS --memcached-version=MEMCACHED_VERSION Optional major version of Memcached software to use with the instance. If not provided, default of "1.5" will be used. MEMCACHED_VERSION must - be (only one value is supported): + be one of: 1.5 Memcached major version 1.5 + 1.6.15 + Memcached version 1.6.15 --parameters=KEY=VALUE User defined parameters to apply to the memcached process on each node. diff --git a/gcloud/alpha/memcache/instances/help b/gcloud/alpha/memcache/instances/help index ed0ac4cdf..e657aca35 100644 --- a/gcloud/alpha/memcache/instances/help +++ b/gcloud/alpha/memcache/instances/help @@ -48,6 +48,9 @@ COMMANDS update (ALPHA) Update a Memorystore Memcached instance. + upgrade + (ALPHA) Upgrade memcache instance to a newer memcached version. + 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/memcache/instances/upgrade b/gcloud/alpha/memcache/instances/upgrade new file mode 100644 index 000000000..a166f2f9e --- /dev/null +++ b/gcloud/alpha/memcache/instances/upgrade @@ -0,0 +1,86 @@ +NAME + gcloud alpha memcache instances upgrade - upgrade memcache instance to a + newer memcached version + +SYNOPSIS + gcloud alpha memcache instances upgrade (INSTANCE : --region=REGION) + --memcached-version=MEMCACHED_VERSION [--async] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Upgrade memcahce instance to a newer memcached version. + +EXAMPLES + To upgrade memcache version of an instance with the name + 'my-memcache-instance' in region 'us-central-1' to MEMCACHE_1_6_15 + + $ gcloud alpha memcache instances upgrade my-memcache-instance \ + --region=us-central1 --memcached-version="1.6.15" + +POSITIONAL ARGUMENTS + Instance resource - Arguments and flags that specify the Memorystore for + Memcached instance you want to upgrade. The arguments in this group can be + used to specify the attributes of this resource. (NOTE) Some attributes + are not given arguments in this group but can be set in other ways. + + To set the project attribute: + ◆ provide the argument instance on the command line with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + INSTANCE + ID of the instance or fully qualified identifier for the instance. + + To set the instance attribute: + ▸ provide the argument instance on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --region=REGION + The name of the Memcached region of the instance. Overrides the + default memcache/region property value for this command invocation. + + To set the region attribute: + ▸ provide the argument instance on the command line with a fully + specified name; + ▸ provide the argument --region on the command line; + ▸ set the property memcache/region. + +REQUIRED FLAGS + --memcached-version=MEMCACHED_VERSION + Memcached engine version to which instance should be upgraded to. + MEMCACHED_VERSION must be (only one value is supported): + + 1.6.15 + Memcached engine version 1.6.15 + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the memcache/v1beta2 API. The full documentation for this + API can be found at: https://cloud.google.com/memorystore/ + +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 memcache instances upgrade + + $ gcloud beta memcache instances upgrade + diff --git a/gcloud/alpha/network-services/service-lb-policies/create b/gcloud/alpha/network-services/service-lb-policies/create index b96939d0f..8038ece01 100644 --- a/gcloud/alpha/network-services/service-lb-policies/create +++ b/gcloud/alpha/network-services/service-lb-policies/create @@ -6,6 +6,7 @@ SYNOPSIS gcloud alpha network-services service-lb-policies create (SERVICE_LB_POLICY : --location=LOCATION) [--async] [--auto-capacity-drain] [--description=DESCRIPTION] + [--failover-health-threshold=FAILOVER_HEALTH_THRESHOLD] [--load-balancing-algorithm=LOAD_BALANCING_ALGORITHM; default="waterfall-by-region"] [GCLOUD_WIDE_FLAG ...] @@ -68,6 +69,14 @@ FLAGS --description=DESCRIPTION The description for the service LB policy. + --failover-health-threshold=FAILOVER_HEALTH_THRESHOLD + The percentage threshold that a load balancer will begin to send + traffic to failover backends. If the percentage of endpoints in a + MIG/NEG is smaller than this value, traffic would be sent to failover + backends if possible. This field should be set to a value between 1 and + 99. The default value is 50 for Global external HTTP(S) load balancer + (classic) and Proxyless service mesh, and 70 for others. + --load-balancing-algorithm=LOAD_BALANCING_ALGORITHM; default="waterfall-by-region" The global load balancing algorithm to be used. LOAD_BALANCING_ALGORITHM must be one of: diff --git a/gcloud/alpha/network-services/service-lb-policies/update b/gcloud/alpha/network-services/service-lb-policies/update index 620b985b7..256075c49 100644 --- a/gcloud/alpha/network-services/service-lb-policies/update +++ b/gcloud/alpha/network-services/service-lb-policies/update @@ -6,6 +6,7 @@ SYNOPSIS gcloud alpha network-services service-lb-policies update (SERVICE_LB_POLICY : --location=LOCATION) [--async] [--auto-capacity-drain] [--description=DESCRIPTION] + [--failover-health-threshold=FAILOVER_HEALTH_THRESHOLD] [--load-balancing-algorithm=LOAD_BALANCING_ALGORITHM; default="waterfall-by-region"] [GCLOUD_WIDE_FLAG ...] @@ -67,6 +68,14 @@ FLAGS --description=DESCRIPTION The description for the service LB policy. + --failover-health-threshold=FAILOVER_HEALTH_THRESHOLD + The percentage threshold that a load balancer will begin to send + traffic to failover backends. If the percentage of endpoints in a + MIG/NEG is smaller than this value, traffic would be sent to failover + backends if possible. This field should be set to a value between 1 and + 99. The default value is 50 for Global external HTTP(S) load balancer + (classic) and Proxyless service mesh, and 70 for others. + --load-balancing-algorithm=LOAD_BALANCING_ALGORITHM; default="waterfall-by-region" The global load balancing algorithm to be used. LOAD_BALANCING_ALGORITHM must be one of: diff --git a/gcloud/alpha/projects/update b/gcloud/alpha/projects/update index 35aea50e8..407454028 100644 --- a/gcloud/alpha/projects/update +++ b/gcloud/alpha/projects/update @@ -21,6 +21,12 @@ EXAMPLES $ gcloud alpha projects update example-foo-bar-1 \ --name="Foo Bar & Grill" --remove-labels=dive + The following command updates a project with the ID example-foo-bar-1 to + have labels foo and bar with values of abc and def, respectively: + + $ gcloud alpha projects update example-foo-bar-1 \ + --update-labels="foo=abc,bar=def" + POSITIONAL ARGUMENTS PROJECT_ID_OR_NUMBER ID or number for the project you want to update. diff --git a/gcloud/alpha/run/deploy b/gcloud/alpha/run/deploy index ac4b04f3f..829b87be2 100644 --- a/gcloud/alpha/run/deploy +++ b/gcloud/alpha/run/deploy @@ -26,22 +26,22 @@ SYNOPSIS --add-custom-audiences=[CUSTOM-AUDIENCES,...] | --clear-custom-audiences | --remove-custom-audiences=[CUSTOM-AUDIENCES,...] - | --set-custom-audiences=[CUSTOM-AUDIENCES,...] - --binary-authorization=POLICY - | --clear-binary-authorization --clear-encryption-key-shutdown-hours - | --encryption-key-shutdown-hours=ENCRYPTION_KEY_SHUTDOWN_HOURS - --clear-key | --key=KEY --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 - --container=CONTAINER | --args=[ARG,...] --command=[COMMAND,...] - --cpu=CPU + | --set-custom-audiences=[CUSTOM-AUDIENCES,...] --args=[ARG,...] + --command=[COMMAND,...] --cpu=CPU --memory=MEMORY --port=PORT --[no-]use-http2 --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] + --update-secrets=[KEY=VALUE,...] --image=IMAGE | --source=SOURCE + | --container=CONTAINER + --remove-containers=[CONTAINERS,...] --binary-authorization=POLICY + | --clear-binary-authorization --clear-encryption-key-shutdown-hours + | --encryption-key-shutdown-hours=ENCRYPTION_KEY_SHUTDOWN_HOURS + --clear-key | --key=KEY --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] [--region=REGION | --cluster=CLUSTER --cluster-location=CLUSTER_LOCATION | --context=CONTEXT --kubeconfig=KUBECONFIG] [GCLOUD_WIDE_FLAG ...] @@ -378,80 +378,6 @@ FLAGS Completely replace the current custom audiences with the given values. - 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-network - Disconnect this Cloud Run service from the VPC network it is - connected to. - - Direct VPC egress setting flags group. - - --network=NETWORK - The VPC network that the Cloud Run service 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 service 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 - service. - - --network-tags=[TAG,...] - Applies the given Compute Engine tags (comma separated) to the - Cloud Run service. 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. - Container Flags If the --container flag is not specified, container flags apply to the @@ -464,130 +390,205 @@ FLAGS $ gcloud alpha run deploy --container=A --image=IMAGE-A \ --container=B --image=IMAGE-B - --container=CONTAINER - Specifies a container by name. The following container flags - apply to the specified container. + If the --container or --remove-containers flag is specified the following + arguments may only be specified after a --container flag. - If the --container flag is specified the following arguments may only be - specified after a --container flag. + --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. - --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. + --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. - --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. - --cpu=CPU - Set a CPU limit in Kubernetes cpu units. + Cloud Run (fully managed) supports values 1, 2 and 4. For Cloud + Run (fully managed), 4 cpus also requires a minimum 2Gi --memory + value. Examples 2, 2.0, 2000m - Cloud Run (fully managed) supports values 1, 2 and 4. For - Cloud Run (fully managed), 4 cpus also requires a minimum 2Gi - --memory value. Examples 2, 2.0, 2000m + Cloud Run for Anthos and Knative-compatible Kubernetes clusters + support fractional values. Examples .5, 500m, 2 - Cloud Run for Anthos and Knative-compatible Kubernetes - clusters support fractional values. Examples .5, 500m, 2 + --memory=MEMORY + Set a memory limit. Ex: 1024Mi, 4Gi. - --memory=MEMORY - Set a memory limit. Ex: 1024Mi, 4Gi. + --port=PORT + Container port to receive requests at. Also sets the $PORT + environment variable. Must be a number between 1 and 65535, + inclusive. To unset this field, pass the special value + "default". If updating an existing service with a TCP startup + probe pointing to the previous container port, this will also + update the probe port. - --port=PORT - Container port to receive requests at. Also sets the $PORT - environment variable. Must be a number between 1 and 65535, - inclusive. To unset this field, pass the special value - "default". If updating an existing service with a TCP startup - probe pointing to the previous container port, this will also - update the probe port. + --[no-]use-http2 + Whether to use HTTP/2 for connections to the service. Use + --use-http2 to enable and --no-use-http2 to disable. - --[no-]use-http2 - Whether to use HTTP/2 for connections to the service. Use - --use-http2 to enable and --no-use-http2 to disable. + At most one of these can be specified: - At most one of these can be specified: + --clear-env-vars + Remove all environment variables. - --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: - --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" - 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. - --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. - 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. - --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. - --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'. - 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: - At most one of these can be specified: + --clear-secrets + Remove all secrets. - --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. - --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. - 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. - --remove-secrets=[KEY,...] - List of secrets to be removed. + --update-secrets=[KEY=VALUE,...] + List of key-value pairs to set as secrets. - --update-secrets=[KEY=VALUE,...] - List of key-value pairs to set as secrets. + At most one of these can be specified: - At most one of these can be specified: + --image=IMAGE + Name of the container image to deploy (e.g. + gcr.io/cloudrun/hello:latest). - --image=IMAGE - Name of the container image to deploy (e.g. - gcr.io/cloudrun/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. - --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. + --container=CONTAINER + Specifies a container by name. The following container flags apply + to the specified container. + + --remove-containers=[CONTAINERS,...] + List of containers to remove. + + 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-network + Disconnect this Cloud Run service from the VPC network it is + connected to. + + Direct VPC egress setting flags group. + + --network=NETWORK + The VPC network that the Cloud Run service 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 service 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 + service. + + --network-tags=[TAG,...] + Applies the given Compute Engine tags (comma separated) to the + Cloud Run service. 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. Arguments to locate resources, depending on the platform used. @@ -609,35 +610,36 @@ FLAGS but can be set in other ways. To set the project attribute: - ▫ provide the argument --cluster on the command line with a fully - specified name; - ▫ set the property run/cluster with a fully specified name; - ▫ specify the cluster from a list of available clusters with a - fully specified name; - ▫ provide the argument --project on the command line; - ▫ set the property core/project. + ▸ provide the argument --cluster on the command line with a fully + specified name; + ▸ set the property run/cluster with a fully specified name; + ▸ specify the cluster from a list of available clusters with a fully + specified name; + ▸ provide the argument --project on the command line; + ▸ set the property core/project. - --cluster=CLUSTER - ID of the cluster or fully qualified identifier for the cluster. + --cluster=CLUSTER + ID of the cluster or fully qualified identifier for the + cluster. - To set the cluster attribute: - ◇ provide the argument --cluster on the command line; - ◇ set the property run/cluster; - ◇ specify the cluster from a list of available clusters. + To set the cluster attribute: + ▫ provide the argument --cluster on the command line; + ▫ set the property run/cluster; + ▫ specify the cluster from a list of available clusters. - --cluster-location=CLUSTER_LOCATION - Zone in which the cluster is located. Alternatively, set the - property [run/cluster_location]. + --cluster-location=CLUSTER_LOCATION + Zone in which the cluster is located. Alternatively, set the + property [run/cluster_location]. - To set the location attribute: - ◇ provide the argument --cluster on the command line with a - fully specified name; - ◇ set the property run/cluster with a fully specified name; - ◇ specify the cluster from a list of available clusters with a - fully specified name; - ◇ provide the argument --cluster-location on the command line; - ◇ set the property run/cluster_location; - ◇ specify the cluster location from a list of available zones. + To set the location attribute: + ▫ provide the argument --cluster on the command line with a + fully specified name; + ▫ set the property run/cluster with a fully specified name; + ▫ specify the cluster from a list of available clusters with a + fully specified name; + ▫ provide the argument --cluster-location on the command line; + ▫ set the property run/cluster_location; + ▫ specify the cluster location from a list of available zones. Only applicable if connecting to Cloud Run for Anthos deployed on VMware. Specify --platform=kubernetes to use: diff --git a/gcloud/alpha/run/services/add-iam-policy-binding b/gcloud/alpha/run/services/add-iam-policy-binding index 246758b97..dee5dfa1c 100644 --- a/gcloud/alpha/run/services/add-iam-policy-binding +++ b/gcloud/alpha/run/services/add-iam-policy-binding @@ -5,6 +5,8 @@ NAME SYNOPSIS gcloud alpha run services add-iam-policy-binding SERVICE --member=PRINCIPAL --role=ROLE [--platform=PLATFORM; default="managed"] + [--condition=[KEY=VALUE,...] + | --condition-from-file=CONDITION_FROM_FILE] [--region=REGION | --cluster=CLUSTER --cluster-location=CLUSTER_LOCATION | --context=CONTEXT --kubeconfig=KUBECONFIG] [GCLOUD_WIDE_FLAG ...] @@ -90,6 +92,43 @@ OPTIONAL FLAGS --kubeconfig and --context flags to specify a kubeconfig file and the context for connecting. + At most one of these can be specified: + + --condition=[KEY=VALUE,...] + A condition to include in the binding. When the condition is + explicitly specified as None (--condition=None), a binding without a + condition is added. When the condition is specified and is not None, + --role cannot be a basic role. Basic roles are roles/editor, + roles/owner, and roles/viewer. For more on conditions, refer to the + conditions overview guide: + https://cloud.google.com/iam/docs/conditions-overview + + When using the --condition flag, include the following key-value + pairs: + + expression + (Required) Condition expression that evaluates to True or False. + This uses a subset of Common Expression Language syntax. + + If the condition expression includes a comma, use a different + delimiter to separate the key-value pairs. Specify the delimiter + before listing the key-value pairs. For example, to specify a + colon (:) as the delimiter, do the following: + --condition=^:^title=TITLE:expression=EXPRESSION. For more + information, see + https://cloud.google.com/sdk/gcloud/reference/topic/escaping. + + title + (Required) A short string describing the purpose of the + expression. + + description + (Optional) Additional description for the expression. + + --condition-from-file=CONDITION_FROM_FILE + Path to a local JSON or YAML file that defines the condition. To see + available fields, see the help for --condition. + Arguments to locate resources, depending on the platform used. At most one of these can be specified: diff --git a/gcloud/alpha/run/services/remove-iam-policy-binding b/gcloud/alpha/run/services/remove-iam-policy-binding index 90fb45fc8..da596d614 100644 --- a/gcloud/alpha/run/services/remove-iam-policy-binding +++ b/gcloud/alpha/run/services/remove-iam-policy-binding @@ -5,6 +5,8 @@ NAME SYNOPSIS gcloud alpha run services remove-iam-policy-binding SERVICE --member=PRINCIPAL --role=ROLE [--platform=PLATFORM; default="managed"] + [--all | --condition=[KEY=VALUE,...] + | --condition-from-file=CONDITION_FROM_FILE] [--region=REGION | --cluster=CLUSTER --cluster-location=CLUSTER_LOCATION | --context=CONTEXT --kubeconfig=KUBECONFIG] [GCLOUD_WIDE_FLAG ...] @@ -91,6 +93,47 @@ OPTIONAL FLAGS --kubeconfig and --context flags to specify a kubeconfig file and the context for connecting. + At most one of these can be specified: + + --all + Remove all bindings with this role and principal, irrespective of any + conditions. + + --condition=[KEY=VALUE,...] + The condition of the binding that you want to remove. When the + condition is explicitly specified as None (--condition=None), a + binding without a condition is removed. Otherwise, only a binding + with a condition that exactly matches the specified condition + (including the optional description) is removed. For more on + conditions, refer to the conditions overview guide: + https://cloud.google.com/iam/docs/conditions-overview + + When using the --condition flag, include the following key-value + pairs: + + expression + (Required) Condition expression that evaluates to True or False. + This uses a subset of Common Expression Language syntax. + + If the condition expression includes a comma, use a different + delimiter to separate the key-value pairs. Specify the delimiter + before listing the key-value pairs. For example, to specify a + colon (:) as the delimiter, do the following: + --condition=^:^title=TITLE:expression=EXPRESSION. For more + information, see + https://cloud.google.com/sdk/gcloud/reference/topic/escaping. + + title + (Required) A short string describing the purpose of the + expression. + + description + (Optional) Additional description for the expression. + + --condition-from-file=CONDITION_FROM_FILE + Path to a local JSON or YAML file that defines the condition. To see + available fields, see the help for --condition. + Arguments to locate resources, depending on the platform used. At most one of these can be specified: diff --git a/gcloud/alpha/run/services/update b/gcloud/alpha/run/services/update index 6a2fa6813..141528467 100644 --- a/gcloud/alpha/run/services/update +++ b/gcloud/alpha/run/services/update @@ -22,22 +22,22 @@ SYNOPSIS --add-custom-audiences=[CUSTOM-AUDIENCES,...] | --clear-custom-audiences | --remove-custom-audiences=[CUSTOM-AUDIENCES,...] - | --set-custom-audiences=[CUSTOM-AUDIENCES,...] - --binary-authorization=POLICY - | --clear-binary-authorization --clear-encryption-key-shutdown-hours - | --encryption-key-shutdown-hours=ENCRYPTION_KEY_SHUTDOWN_HOURS - --clear-key | --key=KEY --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 - --container=CONTAINER | --args=[ARG,...] --command=[COMMAND,...] - --cpu=CPU --image=IMAGE + | --set-custom-audiences=[CUSTOM-AUDIENCES,...] --args=[ARG,...] + --command=[COMMAND,...] --cpu=CPU --image=IMAGE --memory=MEMORY --port=PORT --[no-]use-http2 --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,...]] + | --remove-secrets=[KEY,...] --update-secrets=[KEY=VALUE,...] + | --container=CONTAINER + --remove-containers=[CONTAINERS,...] --binary-authorization=POLICY + | --clear-binary-authorization --clear-encryption-key-shutdown-hours + | --encryption-key-shutdown-hours=ENCRYPTION_KEY_SHUTDOWN_HOURS + --clear-key | --key=KEY --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] [--clear-labels | --remove-labels=[KEY,...] --labels=[KEY=VALUE,...] | --update-labels=[KEY=VALUE,...]] [--connectivity=CONNECTIVITY --clear-config-maps @@ -283,80 +283,6 @@ FLAGS Completely replace the current custom audiences with the given values. - 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-network - Disconnect this Cloud Run service from the VPC network it is - connected to. - - Direct VPC egress setting flags group. - - --network=NETWORK - The VPC network that the Cloud Run service 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 service 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 - service. - - --network-tags=[TAG,...] - Applies the given Compute Engine tags (comma separated) to the - Cloud Run service. 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. - Container Flags If the --container flag is not specified, container flags apply to the @@ -369,110 +295,186 @@ FLAGS $ gcloud alpha run services update --container=A --image=IMAGE-A \ --container=B --image=IMAGE-B - --container=CONTAINER - Specifies a container by name. The following container flags - apply to the specified container. + If the --container or --remove-containers flag is specified the following + arguments may only be specified after a --container flag. - If the --container flag is specified the following arguments may only be - specified after a --container flag. + --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. - --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. + --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. - --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. - --cpu=CPU - Set a CPU limit in Kubernetes cpu units. + Cloud Run (fully managed) supports values 1, 2 and 4. For Cloud + Run (fully managed), 4 cpus also requires a minimum 2Gi --memory + value. Examples 2, 2.0, 2000m - Cloud Run (fully managed) supports values 1, 2 and 4. For - Cloud Run (fully managed), 4 cpus also requires a minimum 2Gi - --memory value. Examples 2, 2.0, 2000m + Cloud Run for Anthos and Knative-compatible Kubernetes clusters + support fractional values. Examples .5, 500m, 2 - Cloud Run for Anthos and Knative-compatible Kubernetes - clusters support fractional values. Examples .5, 500m, 2 + --image=IMAGE + Name of the container image to deploy (e.g. + gcr.io/cloudrun/hello:latest). - --image=IMAGE - Name of the container image to deploy (e.g. - gcr.io/cloudrun/hello:latest). + --memory=MEMORY + Set a memory limit. Ex: 1024Mi, 4Gi. - --memory=MEMORY - Set a memory limit. Ex: 1024Mi, 4Gi. + --port=PORT + Container port to receive requests at. Also sets the $PORT + environment variable. Must be a number between 1 and 65535, + inclusive. To unset this field, pass the special value + "default". If updating an existing service with a TCP startup + probe pointing to the previous container port, this will also + update the probe port. - --port=PORT - Container port to receive requests at. Also sets the $PORT - environment variable. Must be a number between 1 and 65535, - inclusive. To unset this field, pass the special value - "default". If updating an existing service with a TCP startup - probe pointing to the previous container port, this will also - update the probe port. + --[no-]use-http2 + Whether to use HTTP/2 for connections to the service. Use + --use-http2 to enable and --no-use-http2 to disable. - --[no-]use-http2 - Whether to use HTTP/2 for connections to the service. Use - --use-http2 to enable and --no-use-http2 to disable. + At most one of these can be specified: - At most one of these can be specified: + --clear-env-vars + Remove all environment variables. - --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: - --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" - 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. - --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. - 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. - --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. - --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'. - 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: - At most one of these can be specified: + --clear-secrets + Remove all secrets. - --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. - --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. - 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. - --remove-secrets=[KEY,...] - List of secrets to be removed. + --update-secrets=[KEY=VALUE,...] + List of key-value pairs to set as secrets. - --update-secrets=[KEY=VALUE,...] - List of key-value pairs to set as secrets. + --container=CONTAINER + Specifies a container by name. The following container flags apply + to the specified container. + + --remove-containers=[CONTAINERS,...] + List of containers to remove. + + 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-network + Disconnect this Cloud Run service from the VPC network it is + connected to. + + Direct VPC egress setting flags group. + + --network=NETWORK + The VPC network that the Cloud Run service 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 service 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 + service. + + --network-tags=[TAG,...] + Applies the given Compute Engine tags (comma separated) to the + Cloud Run service. 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. At most one of these can be specified: @@ -575,35 +577,36 @@ FLAGS but can be set in other ways. To set the project attribute: - ▫ provide the argument --cluster on the command line with a fully - specified name; - ▫ set the property run/cluster with a fully specified name; - ▫ specify the cluster from a list of available clusters with a - fully specified name; - ▫ provide the argument --project on the command line; - ▫ set the property core/project. + ▸ provide the argument --cluster on the command line with a fully + specified name; + ▸ set the property run/cluster with a fully specified name; + ▸ specify the cluster from a list of available clusters with a fully + specified name; + ▸ provide the argument --project on the command line; + ▸ set the property core/project. - --cluster=CLUSTER - ID of the cluster or fully qualified identifier for the cluster. + --cluster=CLUSTER + ID of the cluster or fully qualified identifier for the + cluster. - To set the cluster attribute: - ◇ provide the argument --cluster on the command line; - ◇ set the property run/cluster; - ◇ specify the cluster from a list of available clusters. + To set the cluster attribute: + ▫ provide the argument --cluster on the command line; + ▫ set the property run/cluster; + ▫ specify the cluster from a list of available clusters. - --cluster-location=CLUSTER_LOCATION - Zone in which the cluster is located. Alternatively, set the - property [run/cluster_location]. + --cluster-location=CLUSTER_LOCATION + Zone in which the cluster is located. Alternatively, set the + property [run/cluster_location]. - To set the location attribute: - ◇ provide the argument --cluster on the command line with a - fully specified name; - ◇ set the property run/cluster with a fully specified name; - ◇ specify the cluster from a list of available clusters with a - fully specified name; - ◇ provide the argument --cluster-location on the command line; - ◇ set the property run/cluster_location; - ◇ specify the cluster location from a list of available zones. + To set the location attribute: + ▫ provide the argument --cluster on the command line with a + fully specified name; + ▫ set the property run/cluster with a fully specified name; + ▫ specify the cluster from a list of available clusters with a + fully specified name; + ▫ provide the argument --cluster-location on the command line; + ▫ set the property run/cluster_location; + ▫ specify the cluster location from a list of available zones. Only applicable if connecting to Cloud Run for Anthos deployed on VMware. Specify --platform=kubernetes to use: diff --git a/gcloud/alpha/services/help b/gcloud/alpha/services/help index f08b3514a..bd305f313 100644 --- a/gcloud/alpha/services/help +++ b/gcloud/alpha/services/help @@ -8,19 +8,6 @@ DESCRIPTION (ALPHA) The gcloud services command group lets you manage your project's access to services provided by Google and third parties. -EXAMPLES - To see how to enable a service, run: - - $ gcloud alpha services enable --help - - To see how to list services, run: - - $ gcloud alpha services list --help - - To see how to disable a service, run: - - $ gcloud alpha services disable --help - GCLOUD WIDE FLAGS These flags are available to all commands: --help. @@ -47,12 +34,6 @@ GROUPS vpc-peerings (ALPHA) VPC Peerings to various services. -COMMANDS - COMMAND is one of the following: - - list - (ALPHA) List services for a project. - 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/services/list b/gcloud/alpha/services/list deleted file mode 100644 index 611fd376d..000000000 --- a/gcloud/alpha/services/list +++ /dev/null @@ -1,76 +0,0 @@ -NAME - gcloud alpha services list - list services for a project - -SYNOPSIS - gcloud alpha services list [--available | --enabled] [--filter=EXPRESSION] - [--limit=LIMIT] [--page-size=PAGE_SIZE; default=200] - [--sort-by=[FIELD,...]] [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (ALPHA) This command lists the services that are enabled or available to be - enabled by a project. You can choose the mode in which the command will - list services by using exactly one of the --enabled or --available flags. - --enabled is the default. - -EXAMPLES - To list the services the current project has enabled for consumption, run: - - $ gcloud alpha services list --enabled - - To list the services the current project can enable for consumption, run: - - $ gcloud alpha services list --available - -FLAGS - At most one of these can be specified: - - --available - Return the services available to the project to enable. This list - will include any services that the project has already enabled. - - --enabled - (DEFAULT) Return the services which the project has enabled. - -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; default=200 - Some services group resource list output into pages. This flag - specifies the maximum number of resources per page. The default is 200. - 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. - -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 services list - - $ gcloud beta services list - diff --git a/gcloud/artifacts/vulnerabilities/help b/gcloud/artifacts/vulnerabilities/help index be563ec5b..70c8c16f5 100644 --- a/gcloud/artifacts/vulnerabilities/help +++ b/gcloud/artifacts/vulnerabilities/help @@ -20,4 +20,4 @@ COMMANDS --format=json. load-vex - Load VEX data from a file. + Load VEX data from a CSAF file into Artifact Analysis. diff --git a/gcloud/artifacts/vulnerabilities/load-vex b/gcloud/artifacts/vulnerabilities/load-vex index d754920b0..eb540f057 100644 --- a/gcloud/artifacts/vulnerabilities/load-vex +++ b/gcloud/artifacts/vulnerabilities/load-vex @@ -1,12 +1,15 @@ NAME - gcloud artifacts vulnerabilities load-vex - load VEX data from a file + gcloud artifacts vulnerabilities load-vex - load VEX data from a CSAF file + into Artifact Analysis SYNOPSIS gcloud artifacts vulnerabilities load-vex --source=SOURCE --uri=URI [--project=PROJECT] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - Load VEX data from a file. + Command loads VEX data from a Common Security Advisory Framework (CSAF) + file into Artifact Analysis as VulnerabilityAssessment Notes. VEX data + tells Artifact Analysis whether vulnerabilities are relevant and how. EXAMPLES To load a CSAF security advisory file given an artifact in Artifact diff --git a/gcloud/beta/compute/backend-services/help b/gcloud/beta/compute/backend-services/help index d9cc5e0c7..5113c8105 100644 --- a/gcloud/beta/compute/backend-services/help +++ b/gcloud/beta/compute/backend-services/help @@ -67,6 +67,9 @@ COMMANDS list (BETA) List Google Compute Engine backend services. + list-usable + (BETA) List usable backend services. + remove-backend (BETA) Remove a backend from a backend service. diff --git a/gcloud/beta/container/fleet/namespaces/rbacrolebindings/list b/gcloud/beta/compute/backend-services/list-usable similarity index 59% rename from gcloud/beta/container/fleet/namespaces/rbacrolebindings/list rename to gcloud/beta/compute/backend-services/list-usable index 68142ebe8..67dd88a79 100644 --- a/gcloud/beta/container/fleet/namespaces/rbacrolebindings/list +++ b/gcloud/beta/compute/backend-services/list-usable @@ -1,28 +1,45 @@ NAME - gcloud beta container fleet namespaces rbacrolebindings list - list RBAC - RoleBindings in a fleet namespace + gcloud beta compute backend-services list-usable - list usable backend + services SYNOPSIS - gcloud beta container fleet namespaces rbacrolebindings list - --namespace=NAMESPACE [--filter=EXPRESSION] [--limit=LIMIT] + gcloud beta compute backend-services list-usable [BACKEND_SERVICE_NAME] + [--global | --region=REGION] [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) This command can fail for the following reasons: - ▪ The namespace specified does not exist. - ▪ The user does not have access to the specified namespace. + (BETA) $ gcloud beta compute backend-services list-usable retrieves the + list of backend service resources in the specified project for which you + have compute.backendService.get and compute.backendService.use permissions. + This command is useful when you're creating load balancers in a Shared VPC + environment and you want to use cross-project service referencing + (https://cloud.google.com/load-balancing/docs/https#cross-project). You can + use this command to find out which backend services in other projects are + available to you for referencing. EXAMPLES - The following command lists RBAC RoleBindings in namespace NAMESPACE in - project PROJECT_ID: + To list all global backend services in a project, run: - $ gcloud beta container fleet namespaces rbacrolebindings list \ - --namespace=NAMESPACE --project=PROJECT_ID + $ gcloud beta compute backend-services list-usable --global -REQUIRED FLAGS - --namespace=NAMESPACE - Name of the fleet namespace to list RBAC RoleBindings from. + To list all backend services in a region, run: + + $ gcloud beta compute backend-services list-usable --region=REGION + +POSITIONAL ARGUMENTS + [BACKEND_SERVICE_NAME] + Name of the backend service to operate on. + +FLAGS + At most one of these can be specified: + + --global + If set, the backend service is global. + + --region=REGION + Region of the backend service to operate on. Overrides the default + compute/region property value for this command invocation. LIST COMMAND FLAGS --filter=EXPRESSION @@ -68,5 +85,5 @@ NOTES This command is currently in beta and might change without notice. This variant is also available: - $ gcloud alpha container fleet namespaces rbacrolebindings list + $ gcloud alpha compute backend-services list-usable diff --git a/gcloud/beta/compute/instance-templates/create b/gcloud/beta/compute/instance-templates/create index dd4c23595..d597a4bba 100644 --- a/gcloud/beta/compute/instance-templates/create +++ b/gcloud/beta/compute/instance-templates/create @@ -1014,12 +1014,28 @@ FLAGS Specifies the reservation for instances created from this template. --reservation=RESERVATION - The name of the reservation, required when - --reservation-affinity=specific. + The name of the reservation, required when --reservation-affinity is + one of: specific, specific-then-any-reservation or + specific-then-no-reservation. --reservation-affinity=RESERVATION_AFFINITY; default="any" The type of reservation for instances created from this template. - RESERVATION_AFFINITY must be one of: any, none, specific. + RESERVATION_AFFINITY must be one of: + + any + Consume any available, matching reservation. + none + Do not consume from any reserved capacity. + specific + Must consume from a specific reservation. + specific-then-any-reservation + Prefer to consume from a specific reservation, but still consume + any available matching reservation if the specified reservation + is not available or exhausted. + specific-then-no-reservation + Prefer to consume from a specific reservation, but still consume + from the on-demand pool if the specified reservation is not + available or exhausted. At most one of these can be specified: diff --git a/gcloud/beta/compute/instances/bulk/create b/gcloud/beta/compute/instances/bulk/create index 771a331ba..36b3b7d69 100644 --- a/gcloud/beta/compute/instances/bulk/create +++ b/gcloud/beta/compute/instances/bulk/create @@ -946,12 +946,28 @@ OPTIONAL FLAGS Specifies the reservation for the instance. --reservation=RESERVATION - The name of the reservation, required when - --reservation-affinity=specific. + The name of the reservation, required when --reservation-affinity is + one of: specific, specific-then-any-reservation or + specific-then-no-reservation. --reservation-affinity=RESERVATION_AFFINITY; default="any" The type of reservation for the instance. RESERVATION_AFFINITY must - be one of: any, none, specific. + be one of: + + any + Consume any available, matching reservation. + none + Do not consume from any reserved capacity. + specific + Must consume from a specific reservation. + specific-then-any-reservation + Prefer to consume from a specific reservation, but still consume + any available matching reservation if the specified reservation + is not available or exhausted. + specific-then-no-reservation + Prefer to consume from a specific reservation, but still consume + from the on-demand pool if the specified reservation is not + available or exhausted. At most one of these can be specified: diff --git a/gcloud/beta/compute/instances/create b/gcloud/beta/compute/instances/create index 0cdd2f041..10278cb15 100644 --- a/gcloud/beta/compute/instances/create +++ b/gcloud/beta/compute/instances/create @@ -1165,12 +1165,28 @@ FLAGS Specifies the reservation for the instance. --reservation=RESERVATION - The name of the reservation, required when - --reservation-affinity=specific. + The name of the reservation, required when --reservation-affinity is + one of: specific, specific-then-any-reservation or + specific-then-no-reservation. --reservation-affinity=RESERVATION_AFFINITY; default="any" The type of reservation for the instance. RESERVATION_AFFINITY must - be one of: any, none, specific. + be one of: + + any + Consume any available, matching reservation. + none + Do not consume from any reserved capacity. + specific + Must consume from a specific reservation. + specific-then-any-reservation + Prefer to consume from a specific reservation, but still consume + any available matching reservation if the specified reservation + is not available or exhausted. + specific-then-no-reservation + Prefer to consume from a specific reservation, but still consume + from the on-demand pool if the specified reservation is not + available or exhausted. At most one of these can be specified: diff --git a/gcloud/beta/compute/networks/subnets/create b/gcloud/beta/compute/networks/subnets/create index 9ea183269..3eb94557b 100644 --- a/gcloud/beta/compute/networks/subnets/create +++ b/gcloud/beta/compute/networks/subnets/create @@ -102,7 +102,7 @@ OPTIONAL FLAGS The purpose of this subnetwork. PURPOSE must be one of: GLOBAL_MANAGED_PROXY - Reserved for Global HTTP(S) Load Balancing. + Reserved for Global Envoy-based Load Balancing. INTERNAL_HTTPS_LOAD_BALANCER Reserved for Internal HTTP(S) Load Balancing. PRIVATE @@ -112,7 +112,7 @@ OPTIONAL FLAGS PRIVATE_SERVICE_CONNECT Reserved for Private Service Connect Internal Load Balancing. REGIONAL_MANAGED_PROXY - Reserved for Regional HTTP(S) Load Balancing. + Reserved for Regional Envoy-based Load Balancing. --range=RANGE The IP space allocated to this subnetwork in CIDR format. diff --git a/gcloud/beta/compute/security-policies/update b/gcloud/beta/compute/security-policies/update index 4e54ceef5..d3018caf8 100644 --- a/gcloud/beta/compute/security-policies/update +++ b/gcloud/beta/compute/security-policies/update @@ -48,8 +48,8 @@ FLAGS --json-parsing=JSON_PARSING The JSON parsing behavior for this rule. Must be one of the following - values: [DISABLED, STANDARD]. JSON_PARSING must be one of: DISABLED, - STANDARD. + values: [DISABLED, STANDARD, STANDARD_WITH_GRAPHQL]. JSON_PARSING must + be one of: DISABLED, STANDARD, STANDARD_WITH_GRAPHQL. --layer7-ddos-defense-auto-deploy-confidence-threshold=LAYER7_DDOS_DEFENSE_AUTO_DEPLOY_CONFIDENCE_THRESHOLD Confidence threshold above which Adaptive Protection's auto-deploy diff --git a/gcloud/beta/config/get b/gcloud/beta/config/get index 778569dee..ecc56c106 100644 --- a/gcloud/beta/config/get +++ b/gcloud/beta/config/get @@ -1266,6 +1266,26 @@ AVAILABLE PROPERTIES the default storage class and retention period for the destination bucket meet the criteria for parallel composite upload. + parallel_composite_upload_component_prefix + The prefix used when naming temporary components created by + composite uploads. If the prefix begins with a /, the temporary + components are uploaded relative to the bucket name. If the prefix + does not begin with a /, the temporary components are uploaded + relative to the prefix portion of the destination object name. For + example, consider an upload that will create a final object named + gs://bucket/dir1/dir2/object. Using a prefix of /prefix means + temporary components use names like + gs://bucket/prefix/COMPONENT_NAME. Using a prefix of prefix means + temporary components use names like + gs://bucket/dir1/dir2/prefix/COMPONENT_NAME. Note that this can + complicate cleaning up temporary components, as they will not all + share a common prefix. If this property is not specified, gcloud + storage uses the prefix + /gcloud/tmp/parallel_composite_uploads/see_gcloud_storage_cp_help_for_details/. + If a chosen prefix results in temporary component names longer than + the maximum length Cloud Storage allows, gcloud storage performs a + non-composite upload. + parallel_composite_upload_component_size Specifies the ideal size of a component in bytes, which will act as an upper bound to the size of the components if ceil(file_size / diff --git a/gcloud/beta/config/help b/gcloud/beta/config/help index 6d80452b5..55d1068a9 100644 --- a/gcloud/beta/config/help +++ b/gcloud/beta/config/help @@ -1298,6 +1298,26 @@ AVAILABLE PROPERTIES the default storage class and retention period for the destination bucket meet the criteria for parallel composite upload. + parallel_composite_upload_component_prefix + The prefix used when naming temporary components created by + composite uploads. If the prefix begins with a /, the temporary + components are uploaded relative to the bucket name. If the prefix + does not begin with a /, the temporary components are uploaded + relative to the prefix portion of the destination object name. For + example, consider an upload that will create a final object named + gs://bucket/dir1/dir2/object. Using a prefix of /prefix means + temporary components use names like + gs://bucket/prefix/COMPONENT_NAME. Using a prefix of prefix means + temporary components use names like + gs://bucket/dir1/dir2/prefix/COMPONENT_NAME. Note that this can + complicate cleaning up temporary components, as they will not all + share a common prefix. If this property is not specified, gcloud + storage uses the prefix + /gcloud/tmp/parallel_composite_uploads/see_gcloud_storage_cp_help_for_details/. + If a chosen prefix results in temporary component names longer than + the maximum length Cloud Storage allows, gcloud storage performs a + non-composite upload. + parallel_composite_upload_component_size Specifies the ideal size of a component in bytes, which will act as an upper bound to the size of the components if ceil(file_size / diff --git a/gcloud/beta/config/list b/gcloud/beta/config/list index 00a062bf6..a644450e9 100644 --- a/gcloud/beta/config/list +++ b/gcloud/beta/config/list @@ -1310,6 +1310,26 @@ AVAILABLE PROPERTIES the default storage class and retention period for the destination bucket meet the criteria for parallel composite upload. + parallel_composite_upload_component_prefix + The prefix used when naming temporary components created by + composite uploads. If the prefix begins with a /, the temporary + components are uploaded relative to the bucket name. If the prefix + does not begin with a /, the temporary components are uploaded + relative to the prefix portion of the destination object name. For + example, consider an upload that will create a final object named + gs://bucket/dir1/dir2/object. Using a prefix of /prefix means + temporary components use names like + gs://bucket/prefix/COMPONENT_NAME. Using a prefix of prefix means + temporary components use names like + gs://bucket/dir1/dir2/prefix/COMPONENT_NAME. Note that this can + complicate cleaning up temporary components, as they will not all + share a common prefix. If this property is not specified, gcloud + storage uses the prefix + /gcloud/tmp/parallel_composite_uploads/see_gcloud_storage_cp_help_for_details/. + If a chosen prefix results in temporary component names longer than + the maximum length Cloud Storage allows, gcloud storage performs a + non-composite upload. + parallel_composite_upload_component_size Specifies the ideal size of a component in bytes, which will act as an upper bound to the size of the components if ceil(file_size / diff --git a/gcloud/beta/config/set b/gcloud/beta/config/set index 725e4243d..79207b2eb 100644 --- a/gcloud/beta/config/set +++ b/gcloud/beta/config/set @@ -1313,6 +1313,26 @@ AVAILABLE PROPERTIES the default storage class and retention period for the destination bucket meet the criteria for parallel composite upload. + parallel_composite_upload_component_prefix + The prefix used when naming temporary components created by + composite uploads. If the prefix begins with a /, the temporary + components are uploaded relative to the bucket name. If the prefix + does not begin with a /, the temporary components are uploaded + relative to the prefix portion of the destination object name. For + example, consider an upload that will create a final object named + gs://bucket/dir1/dir2/object. Using a prefix of /prefix means + temporary components use names like + gs://bucket/prefix/COMPONENT_NAME. Using a prefix of prefix means + temporary components use names like + gs://bucket/dir1/dir2/prefix/COMPONENT_NAME. Note that this can + complicate cleaning up temporary components, as they will not all + share a common prefix. If this property is not specified, gcloud + storage uses the prefix + /gcloud/tmp/parallel_composite_uploads/see_gcloud_storage_cp_help_for_details/. + If a chosen prefix results in temporary component names longer than + the maximum length Cloud Storage allows, gcloud storage performs a + non-composite upload. + parallel_composite_upload_component_size Specifies the ideal size of a component in bytes, which will act as an upper bound to the size of the components if ceil(file_size / diff --git a/gcloud/beta/config/unset b/gcloud/beta/config/unset index cece31ec3..5b10dab04 100644 --- a/gcloud/beta/config/unset +++ b/gcloud/beta/config/unset @@ -1274,6 +1274,26 @@ AVAILABLE PROPERTIES the default storage class and retention period for the destination bucket meet the criteria for parallel composite upload. + parallel_composite_upload_component_prefix + The prefix used when naming temporary components created by + composite uploads. If the prefix begins with a /, the temporary + components are uploaded relative to the bucket name. If the prefix + does not begin with a /, the temporary components are uploaded + relative to the prefix portion of the destination object name. For + example, consider an upload that will create a final object named + gs://bucket/dir1/dir2/object. Using a prefix of /prefix means + temporary components use names like + gs://bucket/prefix/COMPONENT_NAME. Using a prefix of prefix means + temporary components use names like + gs://bucket/dir1/dir2/prefix/COMPONENT_NAME. Note that this can + complicate cleaning up temporary components, as they will not all + share a common prefix. If this property is not specified, gcloud + storage uses the prefix + /gcloud/tmp/parallel_composite_uploads/see_gcloud_storage_cp_help_for_details/. + If a chosen prefix results in temporary component names longer than + the maximum length Cloud Storage allows, gcloud storage performs a + non-composite upload. + parallel_composite_upload_component_size Specifies the ideal size of a component in bytes, which will act as an upper bound to the size of the components if ceil(file_size / diff --git a/gcloud/beta/container/binauthz/attestations/sign-and-create b/gcloud/beta/container/binauthz/attestations/sign-and-create index 2be59774b..d71afa708 100644 --- a/gcloud/beta/container/binauthz/attestations/sign-and-create +++ b/gcloud/beta/container/binauthz/attestations/sign-and-create @@ -10,6 +10,9 @@ SYNOPSIS --keyversion-keyring=KEYVERSION_KEYRING --keyversion-location=KEYVERSION_LOCATION --keyversion-project=KEYVERSION_PROJECT) + [--dsse-type=DSSE_TYPE; + default="application/vnd.dev.cosign.simplesigning.v1+json"] + [--pae-encode-payload] [--public-key-id-override=PUBLIC_KEY_ID_OVERRIDE] [--validate] [GCLOUD_WIDE_FLAG ...] @@ -117,6 +120,12 @@ REQUIRED FLAGS ▸ set the property core/project. OPTIONAL FLAGS + --dsse-type=DSSE_TYPE; default="application/vnd.dev.cosign.simplesigning.v1+json" + DSSE type used for pae encoding. + + --pae-encode-payload + Whether to pae-encode the payload before signing. + --public-key-id-override=PUBLIC_KEY_ID_OVERRIDE If provided, the ID of the public key that will be used to verify the Attestation instead of the default generated one. This ID should match diff --git a/gcloud/beta/container/clusters/create b/gcloud/beta/container/clusters/create index 4fad1251c..9b3d75fee 100644 --- a/gcloud/beta/container/clusters/create +++ b/gcloud/beta/container/clusters/create @@ -105,9 +105,9 @@ SYNOPSIS [--enable-private-endpoint --enable-private-nodes --master-ipv4-cidr=MASTER_IPV4_CIDR --private-cluster] [--enable-tpu --enable-tpu-service-networking | --tpu-ipv4-cidr=CIDR] - [--ephemeral-storage=[local-ssd-count=LOCAL-SSD-COUNT] - | --ephemeral-storage-local-ssd=[count=COUNT] - | --local-nvme-ssd-block=[count=COUNT] + [--ephemeral-storage[=[local-ssd-count=LOCAL-SSD-COUNT]] + | --ephemeral-storage-local-ssd[=[count=COUNT]] + | --local-nvme-ssd-block[=[count=COUNT]] | --local-ssd-count=LOCAL_SSD_COUNT] [--location=LOCATION | --region=REGION | --zone=ZONE, -z ZONE] [--maintenance-window=START_TIME | --maintenance-window-end=TIME_STAMP @@ -1732,7 +1732,7 @@ FLAGS At most one of these can be specified: - --ephemeral-storage=[local-ssd-count=LOCAL-SSD-COUNT] + --ephemeral-storage[=[local-ssd-count=LOCAL-SSD-COUNT]] Parameters for the ephemeral storage filesystem. If unspecified, ephemeral storage is backed by the boot disk. @@ -1749,7 +1749,7 @@ FLAGS See https://cloud.google.com/compute/docs/disks/local-ssd for more information. - --ephemeral-storage-local-ssd=[count=COUNT] + --ephemeral-storage-local-ssd[=[count=COUNT]] Parameters for the ephemeral storage filesystem. If unspecified, ephemeral storage is backed by the boot disk. @@ -1765,7 +1765,7 @@ FLAGS See https://cloud.google.com/compute/docs/disks/local-ssd for more information. - --local-nvme-ssd-block=[count=COUNT] + --local-nvme-ssd-block[=[count=COUNT]] Adds the requested local SSDs on all nodes in default node pool(s) in the new cluster. diff --git a/gcloud/beta/container/clusters/create-auto b/gcloud/beta/container/clusters/create-auto index ab51bcfa2..1eb4e4aa1 100644 --- a/gcloud/beta/container/clusters/create-auto +++ b/gcloud/beta/container/clusters/create-auto @@ -12,7 +12,8 @@ SYNOPSIS [--create-subnetwork=[KEY=VALUE,...]] [--database-encryption-key=DATABASE_ENCRYPTION_KEY] [--dataplane-v2-observability-mode=DATAPLANE_V2_OBSERVABILITY_MODE] - [--enable-fleet] [--enable-google-cloud-access] + [--enable-backup-restore] [--enable-fleet] + [--enable-google-cloud-access] [--enable-kubernetes-unstable-apis=API,[API,...]] [--enable-master-global-access] [--fleet-project=PROJECT_ID_OR_NUMBER] [--logging=[COMPONENT,...]] [--monitoring=[COMPONENT,...]] @@ -185,6 +186,11 @@ FLAGS Makes Advanced Datapath Observability available from the VPC network. + --enable-backup-restore + Enable the Backup for GKE add-on. This add-on is disabled by default. + To learn more, see the Backup for GKE overview: + https://cloud.google.com/kubernetes-engine/docs/add-on/backup-for-gke/concepts/backup-for-gke. + --enable-fleet Set cluster project as the fleet host project. This will register the cluster to the same project. To register the cluster to a fleet in a diff --git a/gcloud/beta/container/fleet/help b/gcloud/beta/container/fleet/help index 592796079..e7edd223a 100644 --- a/gcloud/beta/container/fleet/help +++ b/gcloud/beta/container/fleet/help @@ -73,10 +73,6 @@ GROUPS multi-cluster-services (BETA) Manage Multi-cluster Services Feature. - namespaces - (BETA) Fleet namespaces are the fleet equivalent of k8s cluster - namespaces. - scopes (BETA) Manage scopes of all your GKE fleets. diff --git a/gcloud/beta/container/fleet/namespaces/create b/gcloud/beta/container/fleet/namespaces/create deleted file mode 100644 index c6a589778..000000000 --- a/gcloud/beta/container/fleet/namespaces/create +++ /dev/null @@ -1,65 +0,0 @@ -NAME - gcloud beta container fleet namespaces create - create a fleet namespace - -SYNOPSIS - gcloud beta container fleet namespaces create NAME [--scope=SCOPE] - [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (BETA) This command can fail for the following reasons: - ▪ The project specified does not exist. - ▪ The project has a fleet namespace with the same name. - ▪ The caller does not have permission to access the given project. - -EXAMPLES - To create a fleet namespace with name NAMESPACE in the active project, run: - - $ gcloud beta container fleet namespaces create NAMESPACE - - To create a fleet namespace in fleet scope SCOPE in project PROJECT_ID with - name NAMESPACE, run: - - $ gcloud beta container fleet namespaces create NAMESPACE \ - --scope=SCOPE --project=PROJECT_ID - -POSITIONAL ARGUMENTS - NAME - Name of the fleet namespace to be created. Must comply with RFC 1123 - (up to 63 characters, alphanumeric and '-') - -FLAGS - Scope resource - The group of arguments defining the Fleet Scope. 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 --scope on the command line with a fully - specified name; - ◆ provide the argument --project on the command line; - ◆ set the property core/project. - - To set the location attribute: - ◆ provide the argument --scope on the command line with a fully - specified name; - ◆ global is the only supported location. - - --scope=SCOPE - ID of the scope or fully qualified identifier for the scope. - - To set the scope attribute: - ▸ provide the argument --scope on the command line. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --configuration, --flags-file, --flatten, --format, - --help, --impersonate-service-account, --log-http, --project, --quiet, - --trace-token, --user-output-enabled, --verbosity. - - Run $ gcloud help for details. - -NOTES - This command is currently in beta and might change without notice. This - variant is also available: - - $ gcloud alpha container fleet namespaces create - diff --git a/gcloud/beta/container/fleet/namespaces/delete b/gcloud/beta/container/fleet/namespaces/delete deleted file mode 100644 index f4298cde0..000000000 --- a/gcloud/beta/container/fleet/namespaces/delete +++ /dev/null @@ -1,41 +0,0 @@ -NAME - gcloud beta container fleet namespaces delete - delete a fleet namespace - -SYNOPSIS - gcloud beta container fleet namespaces delete NAME [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (BETA) This command can fail for the following reasons: - ▪ The project specified does not exist. - ▪ The namespace specified does not exist. - ▪ The caller does not have permission to access the given project or - namespace. - -EXAMPLES - To delete fleet namespace NAMESPACE in the active project: - - $ gcloud beta container fleet namespaces delete NAMESPACE - - To delete fleet namespace NAMESPACE in project PROJECT_ID: - - $ gcloud beta container fleet namespaces delete NAMESPACE \ - --project=PROJECT_ID - -POSITIONAL ARGUMENTS - NAME - Name of the fleet namespace to be deleted. - -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 container fleet namespaces delete - diff --git a/gcloud/beta/container/fleet/namespaces/describe b/gcloud/beta/container/fleet/namespaces/describe deleted file mode 100644 index bff13d62c..000000000 --- a/gcloud/beta/container/fleet/namespaces/describe +++ /dev/null @@ -1,41 +0,0 @@ -NAME - gcloud beta container fleet namespaces describe - show fleet namespace info - -SYNOPSIS - gcloud beta container fleet namespaces describe NAME [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (BETA) This command can fail for the following reasons: - ▪ The project specified does not exist. - ▪ The namespace specified does not exist in the project. - ▪ The caller does not have permission to access the project or - namespace. - -EXAMPLES - To print metadata for the namespace NAMESPACE in the active project, run: - - $ gcloud beta container fleet namespaces describe NAMESPACE - - To print metadata for the namespace NAMESPACE in project PROJECT_ID, run: - - $ gcloud beta container fleet namespaces describe NAMESPACE \ - --project=PROJECT_ID - -POSITIONAL ARGUMENTS - NAME - Name of the fleet namespace to be described. - -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 container fleet namespaces describe - diff --git a/gcloud/beta/container/fleet/namespaces/get-credentials b/gcloud/beta/container/fleet/namespaces/get-credentials deleted file mode 100644 index 5c23d6740..000000000 --- a/gcloud/beta/container/fleet/namespaces/get-credentials +++ /dev/null @@ -1,58 +0,0 @@ -NAME - gcloud beta container fleet namespaces get-credentials - fetch credentials - for a membership with a particular namespace - -SYNOPSIS - gcloud beta container fleet namespaces get-credentials NAMESPACE - [--membership=MEMBERSHIP] [--membership-location=MEMBERSHIP_LOCATION] - [--set-namespace-in-config=SET_NAMESPACE_IN_CONFIG] - [GCLOUD_WIDE_FLAG ...] - -EXAMPLES - Get the Connect Gateway kubeconfig for global membership MEMBERSHIP, using - namespace NAMESPACE in the config: - - $ gcloud beta container fleet namespaces get-credentials NAMESPACE \ - --membership=MEMBERSHIP --membership-location=global \ - --set-namespace-in-config=true - - Get the Connect Gateway kubeconfig for global membership MEMBERSHIP: - - $ gcloud beta container fleet namespaces get-credentials NAMESPACE \ - --membership=MEMBERSHIP --membership-location=global - -POSITIONAL ARGUMENTS - NAMESPACE - Name of the namespace for which to get access to memberships. - -FLAGS - --membership=MEMBERSHIP - Membership ID to get credentials from. If not provided, a prompt will - offer a list of memberships in the fleet. - - --membership-location=MEMBERSHIP_LOCATION - The location of the membership resource, e.g. us-central1. If not - specified, defaults to global. - - --set-namespace-in-config=SET_NAMESPACE_IN_CONFIG - If true, the default namespace for the context in the generated - kubeconfig will be set to the Fleet namespace (i.e. the name given as - the positional argument in this command). - - Otherwise, no default namespace will be set, functioning the same as - gcloud container fleet memberships get-credentials. - -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 container fleet namespaces get-credentials - diff --git a/gcloud/beta/container/fleet/namespaces/help b/gcloud/beta/container/fleet/namespaces/help deleted file mode 100644 index 83ff7f125..000000000 --- a/gcloud/beta/container/fleet/namespaces/help +++ /dev/null @@ -1,58 +0,0 @@ -NAME - gcloud beta container fleet namespaces - fleet namespaces are the fleet - equivalent of k8s cluster namespaces - -SYNOPSIS - gcloud beta container fleet namespaces GROUP | COMMAND - [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (BETA) This command group allows for manipulation of fleet namespaces. - -EXAMPLES - Manage fleet namespaces: - - $ gcloud beta container fleet namespaces --help - - Manage RBAC RoleBindings in a fleet namespace: - - $ gcloud beta container fleet namespaces rbacrolebindings --help - -GCLOUD WIDE FLAGS - These flags are available to all commands: --help. - - Run $ gcloud help for details. - -GROUPS - GROUP is one of the following: - - rbacrolebindings - (BETA) Fleet namespace RBAC RoleBindings for permissions. - -COMMANDS - COMMAND is one of the following: - - create - (BETA) Create a fleet namespace. - - delete - (BETA) Delete a fleet namespace. - - describe - (BETA) Show fleet namespace info. - - get-credentials - (BETA) Fetch credentials for a membership with a particular namespace. - - list - (BETA) List fleet namespaces in a project. - - update - (BETA) Update a fleet namespace. - -NOTES - This command is currently in beta and might change without notice. This - variant is also available: - - $ gcloud alpha container fleet namespaces - diff --git a/gcloud/beta/container/fleet/namespaces/list b/gcloud/beta/container/fleet/namespaces/list deleted file mode 100644 index 8204e8f47..000000000 --- a/gcloud/beta/container/fleet/namespaces/list +++ /dev/null @@ -1,69 +0,0 @@ -NAME - gcloud beta container fleet namespaces list - list fleet namespaces in a - project - -SYNOPSIS - gcloud beta container fleet namespaces list [--filter=EXPRESSION] - [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] - [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (BETA) This command can fail for the following reasons: - ▪ The project specified does not exist. - ▪ The user does not have access to the project specified. - -EXAMPLES - The following command lists namespaces in the active project: - - $ gcloud beta container fleet namespaces list - - The following command lists namespaces in project PROJECT_ID: - - $ gcloud beta container fleet namespaces list --project=PROJECT_ID - -LIST COMMAND FLAGS - --filter=EXPRESSION - Apply a Boolean filter EXPRESSION to each resource item to be listed. - If the expression evaluates True, then that item is listed. For more - details and examples of filter expressions, run $ gcloud topic filters. - This flag interacts with other flags that are applied in this order: - --flatten, --sort-by, --filter, --limit. - - --limit=LIMIT - Maximum number of resources to list. The default is unlimited. This - flag interacts with other flags that are applied in this order: - --flatten, --sort-by, --filter, --limit. - - --page-size=PAGE_SIZE - Some services group resource list output into pages. This flag - specifies the maximum number of resources per page. The default is - determined by the service if it supports paging, otherwise it is - unlimited (no paging). Paging may be applied before or after --filter - and --limit depending on the service. - - --sort-by=[FIELD,...] - Comma-separated list of resource field key names to sort by. The - default order is ascending. Prefix a field with ``~'' for descending - order on that field. This flag interacts with other flags that are - applied in this order: --flatten, --sort-by, --filter, --limit. - - --uri - Print a list of resource URIs instead of the default output, and change - the command output to a list of URIs. If this flag is used with - --format, the formatting is applied on this URI list. To display URIs - alongside other keys instead, use the uri() transform. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --configuration, --flags-file, --flatten, --format, - --help, --impersonate-service-account, --log-http, --project, --quiet, - --trace-token, --user-output-enabled, --verbosity. - - Run $ gcloud help for details. - -NOTES - This command is currently in beta and might change without notice. This - variant is also available: - - $ gcloud alpha container fleet namespaces list - diff --git a/gcloud/beta/container/fleet/namespaces/rbacrolebindings/create b/gcloud/beta/container/fleet/namespaces/rbacrolebindings/create deleted file mode 100644 index 941f25bd9..000000000 --- a/gcloud/beta/container/fleet/namespaces/rbacrolebindings/create +++ /dev/null @@ -1,95 +0,0 @@ -NAME - gcloud beta container fleet namespaces rbacrolebindings create - create an - RBAC RoleBinding - -SYNOPSIS - gcloud beta container fleet namespaces rbacrolebindings create - (NAME : --location=LOCATION --namespace=NAMESPACE) --role=ROLE - (--group=GROUP | --user=USER) [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (BETA) This command can fail for the following reasons: - ▪ The RBAC RoleBinding already exists. - ▪ The caller does not have permission to access the given namespace. - -EXAMPLES - To create an admin RBAC RoleBinding RBRB in namespace NAMESPACE for user - person@google.com, run: - - $ gcloud beta container fleet namespaces rbacrolebindings create \ - RBRB --namespace=NAMESPACE --role=admin --user=person@google.com - - To create a viewer RBAC RoleBinding RBRB in namespace NAMESPACE for group - people@google.com, run: - - $ gcloud beta container fleet namespaces rbacrolebindings create \ - RBRB --namespace=NAMESPACE --role=viewer \ - --group=people@google.com - -POSITIONAL ARGUMENTS - Rbacrolebinding resource - The group of arguments defining an - RBACRoleBinding. 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 NAME 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. - - NAME - ID of the rbacrolebinding or fully qualified identifier for the - rbacrolebinding. - - To set the rbacrolebinding attribute: - ▸ provide the argument NAME on the command line. - - This positional argument must be specified if any of the other - arguments in this group are specified. - - --location=LOCATION - Location for the rbacrolebinding. - - To set the location attribute: - ▸ provide the argument NAME on the command line with a fully - specified name; - ▸ provide the argument --location on the command line; - ▸ set the property gkehub/location. - - --namespace=NAMESPACE - Name of the rbacrolebinding. - - To set the namespace attribute: - ▸ provide the argument NAME on the command line with a fully - specified name; - ▸ provide the argument --namespace on the command line. - -REQUIRED FLAGS - --role=ROLE - Role to assign. ROLE must be one of: admin, edit, view. - - Exactly one of these must be specified: - - --group=GROUP - Group for the RoleBinding. - - --user=USER - User for the RoleBinding. - -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 container fleet namespaces rbacrolebindings create - diff --git a/gcloud/beta/container/fleet/namespaces/rbacrolebindings/delete b/gcloud/beta/container/fleet/namespaces/rbacrolebindings/delete deleted file mode 100644 index 0dfe2503a..000000000 --- a/gcloud/beta/container/fleet/namespaces/rbacrolebindings/delete +++ /dev/null @@ -1,76 +0,0 @@ -NAME - gcloud beta container fleet namespaces rbacrolebindings delete - delete a - fleet namespace RBAC RoleBinding - -SYNOPSIS - gcloud beta container fleet namespaces rbacrolebindings delete - (NAME : --location=LOCATION --namespace=NAMESPACE) - [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (BETA) This command can fail for the following reasons: - ▪ The RoleBinding specified does not exist. - ▪ The caller does not have permission to access the given RoleBinding. - -EXAMPLES - To delete RBAC RoleBinding RBRB in namespace NAMESPACE in the active - project: - - $ gcloud beta container fleet namespaces rbacrolebindings delete \ - RBRB --namespace=NAMESPACE - -POSITIONAL ARGUMENTS - Rbacrolebinding resource - The group of arguments defining an - RBACRoleBinding. 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 NAME 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. - - NAME - ID of the rbacrolebinding or fully qualified identifier for the - rbacrolebinding. - - To set the rbacrolebinding attribute: - ▸ provide the argument NAME on the command line. - - This positional argument must be specified if any of the other - arguments in this group are specified. - - --location=LOCATION - Location for the rbacrolebinding. - - To set the location attribute: - ▸ provide the argument NAME on the command line with a fully - specified name; - ▸ provide the argument --location on the command line; - ▸ set the property gkehub/location. - - --namespace=NAMESPACE - Name of the rbacrolebinding. - - To set the namespace attribute: - ▸ provide the argument NAME on the command line with a fully - specified name; - ▸ provide the argument --namespace on the command line. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --configuration, --flags-file, --flatten, --format, - --help, --impersonate-service-account, --log-http, --project, --quiet, - --trace-token, --user-output-enabled, --verbosity. - - Run $ gcloud help for details. - -NOTES - This command is currently in beta and might change without notice. This - variant is also available: - - $ gcloud alpha container fleet namespaces rbacrolebindings delete - diff --git a/gcloud/beta/container/fleet/namespaces/rbacrolebindings/describe b/gcloud/beta/container/fleet/namespaces/rbacrolebindings/describe deleted file mode 100644 index 3230dda4c..000000000 --- a/gcloud/beta/container/fleet/namespaces/rbacrolebindings/describe +++ /dev/null @@ -1,76 +0,0 @@ -NAME - gcloud beta container fleet namespaces rbacrolebindings describe - show - fleet namespace RBAC RoleBinding information - -SYNOPSIS - gcloud beta container fleet namespaces rbacrolebindings describe - (NAME : --location=LOCATION --namespace=NAMESPACE) - [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (BETA) This command can fail for the following reasons: - ▪ The RoleBinding specified does not exist in the project. - ▪ The caller does not have permission to access the RoleBinding. - -EXAMPLES - To print metadata for RBAC RoleBinding RBRB in the namespace NAMESPACE, - run: - - $ gcloud beta container fleet namespaces rbacrolebindings describe \ - RBRB --namespace=NAMESPACE - -POSITIONAL ARGUMENTS - Rbacrolebinding resource - The group of arguments defining an - RBACRoleBinding. 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 NAME 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. - - NAME - ID of the rbacrolebinding or fully qualified identifier for the - rbacrolebinding. - - To set the rbacrolebinding attribute: - ▸ provide the argument NAME on the command line. - - This positional argument must be specified if any of the other - arguments in this group are specified. - - --location=LOCATION - Location for the rbacrolebinding. - - To set the location attribute: - ▸ provide the argument NAME on the command line with a fully - specified name; - ▸ provide the argument --location on the command line; - ▸ set the property gkehub/location. - - --namespace=NAMESPACE - Name of the rbacrolebinding. - - To set the namespace attribute: - ▸ provide the argument NAME on the command line with a fully - specified name; - ▸ provide the argument --namespace on the command line. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --configuration, --flags-file, --flatten, --format, - --help, --impersonate-service-account, --log-http, --project, --quiet, - --trace-token, --user-output-enabled, --verbosity. - - Run $ gcloud help for details. - -NOTES - This command is currently in beta and might change without notice. This - variant is also available: - - $ gcloud alpha container fleet namespaces rbacrolebindings describe - diff --git a/gcloud/beta/container/fleet/namespaces/rbacrolebindings/help b/gcloud/beta/container/fleet/namespaces/rbacrolebindings/help deleted file mode 100644 index 1548af286..000000000 --- a/gcloud/beta/container/fleet/namespaces/rbacrolebindings/help +++ /dev/null @@ -1,46 +0,0 @@ -NAME - gcloud beta container fleet namespaces rbacrolebindings - fleet namespace - RBAC RoleBindings for permissions - -SYNOPSIS - gcloud beta container fleet namespaces rbacrolebindings COMMAND - [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (BETA) This command group allows for manipulation of fleet namespace RBAC - RoleBindings. - -EXAMPLES - Manage RBAC RoleBindings: - - $ gcloud beta container fleet namespaces rbacrolebindings --help - -GCLOUD WIDE FLAGS - These flags are available to all commands: --help. - - Run $ gcloud help for details. - -COMMANDS - COMMAND is one of the following: - - create - (BETA) Create an RBAC RoleBinding. - - delete - (BETA) Delete a fleet namespace RBAC RoleBinding. - - describe - (BETA) Show fleet namespace RBAC RoleBinding information. - - list - (BETA) List RBAC RoleBindings in a fleet namespace. - - update - (BETA) Update a fleet namespace RBAC RoleBinding. - -NOTES - This command is currently in beta and might change without notice. This - variant is also available: - - $ gcloud alpha container fleet namespaces rbacrolebindings - diff --git a/gcloud/beta/container/fleet/namespaces/rbacrolebindings/update b/gcloud/beta/container/fleet/namespaces/rbacrolebindings/update deleted file mode 100644 index b7be7ff96..000000000 --- a/gcloud/beta/container/fleet/namespaces/rbacrolebindings/update +++ /dev/null @@ -1,95 +0,0 @@ -NAME - gcloud beta container fleet namespaces rbacrolebindings update - update a - fleet namespace RBAC RoleBinding - -SYNOPSIS - gcloud beta container fleet namespaces rbacrolebindings update - (NAME : --location=LOCATION --namespace=NAMESPACE) [--role=ROLE] - [--group=GROUP | --user=USER] [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (BETA) This command can fail for the following reasons: - ▪ The RoleBinding does not exist in the project. - ▪ The caller does not have permission to access the RoleBinding. - -EXAMPLES - To update the RBAC RoleBinding RBRB in namespace NAMESPACE in the active - project to the viewer role: - - $ gcloud beta container fleet namespaces rbacrolebindings update \ - RBRB --namespace=NAMESPACE --role=viewer - - To update the RBAC RoleBinding RBRB in namespace NAMESPACE in the active - project to the user someone@google.com: - - $ gcloud beta container fleet namespaces rbacrolebindings update \ - RBRB --namespace=NAMESPACE --user=someone@google.com - -POSITIONAL ARGUMENTS - Rbacrolebinding resource - The group of arguments defining an - RBACRoleBinding. 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 NAME 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. - - NAME - ID of the rbacrolebinding or fully qualified identifier for the - rbacrolebinding. - - To set the rbacrolebinding attribute: - ▸ provide the argument NAME on the command line. - - This positional argument must be specified if any of the other - arguments in this group are specified. - - --location=LOCATION - Location for the rbacrolebinding. - - To set the location attribute: - ▸ provide the argument NAME on the command line with a fully - specified name; - ▸ provide the argument --location on the command line; - ▸ set the property gkehub/location. - - --namespace=NAMESPACE - Name of the rbacrolebinding. - - To set the namespace attribute: - ▸ provide the argument NAME on the command line with a fully - specified name; - ▸ provide the argument --namespace on the command line. - -FLAGS - --role=ROLE - Role for the RBACRoleBinding to update to. ROLE must be one of: admin, - edit, view. - - At most one of these can be specified: - - --group=GROUP - Group for the RBACRoleBinding to update to. - - --user=USER - User for the RBACRoleBinding to update to. - -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 container fleet namespaces rbacrolebindings update - diff --git a/gcloud/beta/container/fleet/namespaces/update b/gcloud/beta/container/fleet/namespaces/update deleted file mode 100644 index d77a5461b..000000000 --- a/gcloud/beta/container/fleet/namespaces/update +++ /dev/null @@ -1,64 +0,0 @@ -NAME - gcloud beta container fleet namespaces update - update a fleet namespace - -SYNOPSIS - gcloud beta container fleet namespaces update NAME [--scope=SCOPE] - [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (BETA) This command can fail for the following reasons: - ▪ The project specified does not exist. - ▪ The fleet namespace does not exist in the project. - ▪ The caller does not have permission to access the project or - namespace. - -EXAMPLES - To update the namespace NAMESPACE in the active project: - - $ gcloud beta container fleet namespaces update NAMESPACE - - To update the namespace NAMESPACE in project PROJECT_ID: - - $ gcloud beta container fleet namespaces update NAMESPACE \ - --project=PROJECT_ID - -POSITIONAL ARGUMENTS - NAME - Name of the namespace to be updated. - -FLAGS - Scope resource - The group of arguments defining the Fleet Scope. 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 --scope on the command line with a fully - specified name; - ◆ provide the argument --project on the command line; - ◆ set the property core/project. - - To set the location attribute: - ◆ provide the argument --scope on the command line with a fully - specified name; - ◆ global is the only supported location. - - --scope=SCOPE - ID of the scope or fully qualified identifier for the scope. - - To set the scope attribute: - ▸ provide the argument --scope on the command line. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --configuration, --flags-file, --flatten, --format, - --help, --impersonate-service-account, --log-http, --project, --quiet, - --trace-token, --user-output-enabled, --verbosity. - - Run $ gcloud help for details. - -NOTES - This command is currently in beta and might change without notice. This - variant is also available: - - $ gcloud alpha container fleet namespaces update - diff --git a/gcloud/beta/container/hub/help b/gcloud/beta/container/hub/help index 58d595af3..296973feb 100644 --- a/gcloud/beta/container/hub/help +++ b/gcloud/beta/container/hub/help @@ -73,10 +73,6 @@ GROUPS multi-cluster-services (BETA) Manage Multi-cluster Services Feature. - namespaces - (BETA) Fleet namespaces are the fleet equivalent of k8s cluster - namespaces. - scopes (BETA) Manage scopes of all your GKE fleets. diff --git a/gcloud/beta/container/hub/namespaces/create b/gcloud/beta/container/hub/namespaces/create deleted file mode 100644 index c2b54afbb..000000000 --- a/gcloud/beta/container/hub/namespaces/create +++ /dev/null @@ -1,65 +0,0 @@ -NAME - gcloud beta container hub namespaces create - create a fleet namespace - -SYNOPSIS - gcloud beta container hub namespaces create NAME [--scope=SCOPE] - [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (BETA) This command can fail for the following reasons: - ▪ The project specified does not exist. - ▪ The project has a fleet namespace with the same name. - ▪ The caller does not have permission to access the given project. - -EXAMPLES - To create a fleet namespace with name NAMESPACE in the active project, run: - - $ gcloud beta container hub namespaces create NAMESPACE - - To create a fleet namespace in fleet scope SCOPE in project PROJECT_ID with - name NAMESPACE, run: - - $ gcloud beta container hub namespaces create NAMESPACE \ - --scope=SCOPE --project=PROJECT_ID - -POSITIONAL ARGUMENTS - NAME - Name of the fleet namespace to be created. Must comply with RFC 1123 - (up to 63 characters, alphanumeric and '-') - -FLAGS - Scope resource - The group of arguments defining the Fleet Scope. 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 --scope on the command line with a fully - specified name; - ◆ provide the argument --project on the command line; - ◆ set the property core/project. - - To set the location attribute: - ◆ provide the argument --scope on the command line with a fully - specified name; - ◆ global is the only supported location. - - --scope=SCOPE - ID of the scope or fully qualified identifier for the scope. - - To set the scope attribute: - ▸ provide the argument --scope on the command line. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --configuration, --flags-file, --flatten, --format, - --help, --impersonate-service-account, --log-http, --project, --quiet, - --trace-token, --user-output-enabled, --verbosity. - - Run $ gcloud help for details. - -NOTES - This command is currently in beta and might change without notice. This - variant is also available: - - $ gcloud alpha container hub namespaces create - diff --git a/gcloud/beta/container/hub/namespaces/delete b/gcloud/beta/container/hub/namespaces/delete deleted file mode 100644 index f17b38036..000000000 --- a/gcloud/beta/container/hub/namespaces/delete +++ /dev/null @@ -1,41 +0,0 @@ -NAME - gcloud beta container hub namespaces delete - delete a fleet namespace - -SYNOPSIS - gcloud beta container hub namespaces delete NAME [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (BETA) This command can fail for the following reasons: - ▪ The project specified does not exist. - ▪ The namespace specified does not exist. - ▪ The caller does not have permission to access the given project or - namespace. - -EXAMPLES - To delete fleet namespace NAMESPACE in the active project: - - $ gcloud beta container hub namespaces delete NAMESPACE - - To delete fleet namespace NAMESPACE in project PROJECT_ID: - - $ gcloud beta container hub namespaces delete NAMESPACE \ - --project=PROJECT_ID - -POSITIONAL ARGUMENTS - NAME - Name of the fleet namespace to be deleted. - -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 container hub namespaces delete - diff --git a/gcloud/beta/container/hub/namespaces/describe b/gcloud/beta/container/hub/namespaces/describe deleted file mode 100644 index 1cf55fab7..000000000 --- a/gcloud/beta/container/hub/namespaces/describe +++ /dev/null @@ -1,41 +0,0 @@ -NAME - gcloud beta container hub namespaces describe - show fleet namespace info - -SYNOPSIS - gcloud beta container hub namespaces describe NAME [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (BETA) This command can fail for the following reasons: - ▪ The project specified does not exist. - ▪ The namespace specified does not exist in the project. - ▪ The caller does not have permission to access the project or - namespace. - -EXAMPLES - To print metadata for the namespace NAMESPACE in the active project, run: - - $ gcloud beta container hub namespaces describe NAMESPACE - - To print metadata for the namespace NAMESPACE in project PROJECT_ID, run: - - $ gcloud beta container hub namespaces describe NAMESPACE \ - --project=PROJECT_ID - -POSITIONAL ARGUMENTS - NAME - Name of the fleet namespace to be described. - -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 container hub namespaces describe - diff --git a/gcloud/beta/container/hub/namespaces/get-credentials b/gcloud/beta/container/hub/namespaces/get-credentials deleted file mode 100644 index 155f55b7a..000000000 --- a/gcloud/beta/container/hub/namespaces/get-credentials +++ /dev/null @@ -1,58 +0,0 @@ -NAME - gcloud beta container hub namespaces get-credentials - fetch credentials - for a membership with a particular namespace - -SYNOPSIS - gcloud beta container hub namespaces get-credentials NAMESPACE - [--membership=MEMBERSHIP] [--membership-location=MEMBERSHIP_LOCATION] - [--set-namespace-in-config=SET_NAMESPACE_IN_CONFIG] - [GCLOUD_WIDE_FLAG ...] - -EXAMPLES - Get the Connect Gateway kubeconfig for global membership MEMBERSHIP, using - namespace NAMESPACE in the config: - - $ gcloud beta container hub namespaces get-credentials NAMESPACE \ - --membership=MEMBERSHIP --membership-location=global \ - --set-namespace-in-config=true - - Get the Connect Gateway kubeconfig for global membership MEMBERSHIP: - - $ gcloud beta container hub namespaces get-credentials NAMESPACE \ - --membership=MEMBERSHIP --membership-location=global - -POSITIONAL ARGUMENTS - NAMESPACE - Name of the namespace for which to get access to memberships. - -FLAGS - --membership=MEMBERSHIP - Membership ID to get credentials from. If not provided, a prompt will - offer a list of memberships in the fleet. - - --membership-location=MEMBERSHIP_LOCATION - The location of the membership resource, e.g. us-central1. If not - specified, defaults to global. - - --set-namespace-in-config=SET_NAMESPACE_IN_CONFIG - If true, the default namespace for the context in the generated - kubeconfig will be set to the Fleet namespace (i.e. the name given as - the positional argument in this command). - - Otherwise, no default namespace will be set, functioning the same as - gcloud container fleet memberships get-credentials. - -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 container hub namespaces get-credentials - diff --git a/gcloud/beta/container/hub/namespaces/help b/gcloud/beta/container/hub/namespaces/help deleted file mode 100644 index 6d823cc86..000000000 --- a/gcloud/beta/container/hub/namespaces/help +++ /dev/null @@ -1,57 +0,0 @@ -NAME - gcloud beta container hub namespaces - fleet namespaces are the fleet - equivalent of k8s cluster namespaces - -SYNOPSIS - gcloud beta container hub namespaces GROUP | COMMAND [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (BETA) This command group allows for manipulation of fleet namespaces. - -EXAMPLES - Manage fleet namespaces: - - $ gcloud beta container hub namespaces --help - - Manage RBAC RoleBindings in a fleet namespace: - - $ gcloud beta container hub namespaces rbacrolebindings --help - -GCLOUD WIDE FLAGS - These flags are available to all commands: --help. - - Run $ gcloud help for details. - -GROUPS - GROUP is one of the following: - - rbacrolebindings - (BETA) Fleet namespace RBAC RoleBindings for permissions. - -COMMANDS - COMMAND is one of the following: - - create - (BETA) Create a fleet namespace. - - delete - (BETA) Delete a fleet namespace. - - describe - (BETA) Show fleet namespace info. - - get-credentials - (BETA) Fetch credentials for a membership with a particular namespace. - - list - (BETA) List fleet namespaces in a project. - - update - (BETA) Update a fleet namespace. - -NOTES - This command is currently in beta and might change without notice. This - variant is also available: - - $ gcloud alpha container hub namespaces - diff --git a/gcloud/beta/container/hub/namespaces/list b/gcloud/beta/container/hub/namespaces/list deleted file mode 100644 index 272100050..000000000 --- a/gcloud/beta/container/hub/namespaces/list +++ /dev/null @@ -1,69 +0,0 @@ -NAME - gcloud beta container hub namespaces list - list fleet namespaces in a - project - -SYNOPSIS - gcloud beta container hub namespaces list [--filter=EXPRESSION] - [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] - [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (BETA) This command can fail for the following reasons: - ▪ The project specified does not exist. - ▪ The user does not have access to the project specified. - -EXAMPLES - The following command lists namespaces in the active project: - - $ gcloud beta container hub namespaces list - - The following command lists namespaces in project PROJECT_ID: - - $ gcloud beta container hub namespaces list --project=PROJECT_ID - -LIST COMMAND FLAGS - --filter=EXPRESSION - Apply a Boolean filter EXPRESSION to each resource item to be listed. - If the expression evaluates True, then that item is listed. For more - details and examples of filter expressions, run $ gcloud topic filters. - This flag interacts with other flags that are applied in this order: - --flatten, --sort-by, --filter, --limit. - - --limit=LIMIT - Maximum number of resources to list. The default is unlimited. This - flag interacts with other flags that are applied in this order: - --flatten, --sort-by, --filter, --limit. - - --page-size=PAGE_SIZE - Some services group resource list output into pages. This flag - specifies the maximum number of resources per page. The default is - determined by the service if it supports paging, otherwise it is - unlimited (no paging). Paging may be applied before or after --filter - and --limit depending on the service. - - --sort-by=[FIELD,...] - Comma-separated list of resource field key names to sort by. The - default order is ascending. Prefix a field with ``~'' for descending - order on that field. This flag interacts with other flags that are - applied in this order: --flatten, --sort-by, --filter, --limit. - - --uri - Print a list of resource URIs instead of the default output, and change - the command output to a list of URIs. If this flag is used with - --format, the formatting is applied on this URI list. To display URIs - alongside other keys instead, use the uri() transform. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --configuration, --flags-file, --flatten, --format, - --help, --impersonate-service-account, --log-http, --project, --quiet, - --trace-token, --user-output-enabled, --verbosity. - - Run $ gcloud help for details. - -NOTES - This command is currently in beta and might change without notice. This - variant is also available: - - $ gcloud alpha container hub namespaces list - diff --git a/gcloud/beta/container/hub/namespaces/rbacrolebindings/create b/gcloud/beta/container/hub/namespaces/rbacrolebindings/create deleted file mode 100644 index 8f44f351d..000000000 --- a/gcloud/beta/container/hub/namespaces/rbacrolebindings/create +++ /dev/null @@ -1,95 +0,0 @@ -NAME - gcloud beta container hub namespaces rbacrolebindings create - create an - RBAC RoleBinding - -SYNOPSIS - gcloud beta container hub namespaces rbacrolebindings create - (NAME : --location=LOCATION --namespace=NAMESPACE) --role=ROLE - (--group=GROUP | --user=USER) [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (BETA) This command can fail for the following reasons: - ▪ The RBAC RoleBinding already exists. - ▪ The caller does not have permission to access the given namespace. - -EXAMPLES - To create an admin RBAC RoleBinding RBRB in namespace NAMESPACE for user - person@google.com, run: - - $ gcloud beta container hub namespaces rbacrolebindings create \ - RBRB --namespace=NAMESPACE --role=admin --user=person@google.com - - To create a viewer RBAC RoleBinding RBRB in namespace NAMESPACE for group - people@google.com, run: - - $ gcloud beta container hub namespaces rbacrolebindings create \ - RBRB --namespace=NAMESPACE --role=viewer \ - --group=people@google.com - -POSITIONAL ARGUMENTS - Rbacrolebinding resource - The group of arguments defining an - RBACRoleBinding. 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 NAME 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. - - NAME - ID of the rbacrolebinding or fully qualified identifier for the - rbacrolebinding. - - To set the rbacrolebinding attribute: - ▸ provide the argument NAME on the command line. - - This positional argument must be specified if any of the other - arguments in this group are specified. - - --location=LOCATION - Location for the rbacrolebinding. - - To set the location attribute: - ▸ provide the argument NAME on the command line with a fully - specified name; - ▸ provide the argument --location on the command line; - ▸ set the property gkehub/location. - - --namespace=NAMESPACE - Name of the rbacrolebinding. - - To set the namespace attribute: - ▸ provide the argument NAME on the command line with a fully - specified name; - ▸ provide the argument --namespace on the command line. - -REQUIRED FLAGS - --role=ROLE - Role to assign. ROLE must be one of: admin, edit, view. - - Exactly one of these must be specified: - - --group=GROUP - Group for the RoleBinding. - - --user=USER - User for the RoleBinding. - -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 container hub namespaces rbacrolebindings create - diff --git a/gcloud/beta/container/hub/namespaces/rbacrolebindings/delete b/gcloud/beta/container/hub/namespaces/rbacrolebindings/delete deleted file mode 100644 index ec498506a..000000000 --- a/gcloud/beta/container/hub/namespaces/rbacrolebindings/delete +++ /dev/null @@ -1,76 +0,0 @@ -NAME - gcloud beta container hub namespaces rbacrolebindings delete - delete a - fleet namespace RBAC RoleBinding - -SYNOPSIS - gcloud beta container hub namespaces rbacrolebindings delete - (NAME : --location=LOCATION --namespace=NAMESPACE) - [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (BETA) This command can fail for the following reasons: - ▪ The RoleBinding specified does not exist. - ▪ The caller does not have permission to access the given RoleBinding. - -EXAMPLES - To delete RBAC RoleBinding RBRB in namespace NAMESPACE in the active - project: - - $ gcloud beta container hub namespaces rbacrolebindings delete \ - RBRB --namespace=NAMESPACE - -POSITIONAL ARGUMENTS - Rbacrolebinding resource - The group of arguments defining an - RBACRoleBinding. 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 NAME 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. - - NAME - ID of the rbacrolebinding or fully qualified identifier for the - rbacrolebinding. - - To set the rbacrolebinding attribute: - ▸ provide the argument NAME on the command line. - - This positional argument must be specified if any of the other - arguments in this group are specified. - - --location=LOCATION - Location for the rbacrolebinding. - - To set the location attribute: - ▸ provide the argument NAME on the command line with a fully - specified name; - ▸ provide the argument --location on the command line; - ▸ set the property gkehub/location. - - --namespace=NAMESPACE - Name of the rbacrolebinding. - - To set the namespace attribute: - ▸ provide the argument NAME on the command line with a fully - specified name; - ▸ provide the argument --namespace on the command line. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --configuration, --flags-file, --flatten, --format, - --help, --impersonate-service-account, --log-http, --project, --quiet, - --trace-token, --user-output-enabled, --verbosity. - - Run $ gcloud help for details. - -NOTES - This command is currently in beta and might change without notice. This - variant is also available: - - $ gcloud alpha container hub namespaces rbacrolebindings delete - diff --git a/gcloud/beta/container/hub/namespaces/rbacrolebindings/describe b/gcloud/beta/container/hub/namespaces/rbacrolebindings/describe deleted file mode 100644 index f2ffc6982..000000000 --- a/gcloud/beta/container/hub/namespaces/rbacrolebindings/describe +++ /dev/null @@ -1,76 +0,0 @@ -NAME - gcloud beta container hub namespaces rbacrolebindings describe - show fleet - namespace RBAC RoleBinding information - -SYNOPSIS - gcloud beta container hub namespaces rbacrolebindings describe - (NAME : --location=LOCATION --namespace=NAMESPACE) - [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (BETA) This command can fail for the following reasons: - ▪ The RoleBinding specified does not exist in the project. - ▪ The caller does not have permission to access the RoleBinding. - -EXAMPLES - To print metadata for RBAC RoleBinding RBRB in the namespace NAMESPACE, - run: - - $ gcloud beta container hub namespaces rbacrolebindings describe \ - RBRB --namespace=NAMESPACE - -POSITIONAL ARGUMENTS - Rbacrolebinding resource - The group of arguments defining an - RBACRoleBinding. 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 NAME 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. - - NAME - ID of the rbacrolebinding or fully qualified identifier for the - rbacrolebinding. - - To set the rbacrolebinding attribute: - ▸ provide the argument NAME on the command line. - - This positional argument must be specified if any of the other - arguments in this group are specified. - - --location=LOCATION - Location for the rbacrolebinding. - - To set the location attribute: - ▸ provide the argument NAME on the command line with a fully - specified name; - ▸ provide the argument --location on the command line; - ▸ set the property gkehub/location. - - --namespace=NAMESPACE - Name of the rbacrolebinding. - - To set the namespace attribute: - ▸ provide the argument NAME on the command line with a fully - specified name; - ▸ provide the argument --namespace on the command line. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --configuration, --flags-file, --flatten, --format, - --help, --impersonate-service-account, --log-http, --project, --quiet, - --trace-token, --user-output-enabled, --verbosity. - - Run $ gcloud help for details. - -NOTES - This command is currently in beta and might change without notice. This - variant is also available: - - $ gcloud alpha container hub namespaces rbacrolebindings describe - diff --git a/gcloud/beta/container/hub/namespaces/rbacrolebindings/help b/gcloud/beta/container/hub/namespaces/rbacrolebindings/help deleted file mode 100644 index b60a25f30..000000000 --- a/gcloud/beta/container/hub/namespaces/rbacrolebindings/help +++ /dev/null @@ -1,46 +0,0 @@ -NAME - gcloud beta container hub namespaces rbacrolebindings - fleet namespace - RBAC RoleBindings for permissions - -SYNOPSIS - gcloud beta container hub namespaces rbacrolebindings COMMAND - [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (BETA) This command group allows for manipulation of fleet namespace RBAC - RoleBindings. - -EXAMPLES - Manage RBAC RoleBindings: - - $ gcloud beta container hub namespaces rbacrolebindings --help - -GCLOUD WIDE FLAGS - These flags are available to all commands: --help. - - Run $ gcloud help for details. - -COMMANDS - COMMAND is one of the following: - - create - (BETA) Create an RBAC RoleBinding. - - delete - (BETA) Delete a fleet namespace RBAC RoleBinding. - - describe - (BETA) Show fleet namespace RBAC RoleBinding information. - - list - (BETA) List RBAC RoleBindings in a fleet namespace. - - update - (BETA) Update a fleet namespace RBAC RoleBinding. - -NOTES - This command is currently in beta and might change without notice. This - variant is also available: - - $ gcloud alpha container hub namespaces rbacrolebindings - diff --git a/gcloud/beta/container/hub/namespaces/rbacrolebindings/list b/gcloud/beta/container/hub/namespaces/rbacrolebindings/list deleted file mode 100644 index 6381384ae..000000000 --- a/gcloud/beta/container/hub/namespaces/rbacrolebindings/list +++ /dev/null @@ -1,72 +0,0 @@ -NAME - gcloud beta container hub namespaces rbacrolebindings list - list RBAC - RoleBindings in a fleet namespace - -SYNOPSIS - gcloud beta container hub namespaces rbacrolebindings list - --namespace=NAMESPACE [--filter=EXPRESSION] [--limit=LIMIT] - [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] - [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (BETA) This command can fail for the following reasons: - ▪ The namespace specified does not exist. - ▪ The user does not have access to the specified namespace. - -EXAMPLES - The following command lists RBAC RoleBindings in namespace NAMESPACE in - project PROJECT_ID: - - $ gcloud beta container hub namespaces rbacrolebindings list \ - --namespace=NAMESPACE --project=PROJECT_ID - -REQUIRED FLAGS - --namespace=NAMESPACE - Name of the fleet namespace to list RBAC RoleBindings from. - -LIST COMMAND FLAGS - --filter=EXPRESSION - Apply a Boolean filter EXPRESSION to each resource item to be listed. - If the expression evaluates True, then that item is listed. For more - details and examples of filter expressions, run $ gcloud topic filters. - This flag interacts with other flags that are applied in this order: - --flatten, --sort-by, --filter, --limit. - - --limit=LIMIT - Maximum number of resources to list. The default is unlimited. This - flag interacts with other flags that are applied in this order: - --flatten, --sort-by, --filter, --limit. - - --page-size=PAGE_SIZE - Some services group resource list output into pages. This flag - specifies the maximum number of resources per page. The default is - determined by the service if it supports paging, otherwise it is - unlimited (no paging). Paging may be applied before or after --filter - and --limit depending on the service. - - --sort-by=[FIELD,...] - Comma-separated list of resource field key names to sort by. The - default order is ascending. Prefix a field with ``~'' for descending - order on that field. This flag interacts with other flags that are - applied in this order: --flatten, --sort-by, --filter, --limit. - - --uri - Print a list of resource URIs instead of the default output, and change - the command output to a list of URIs. If this flag is used with - --format, the formatting is applied on this URI list. To display URIs - alongside other keys instead, use the uri() transform. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --configuration, --flags-file, --flatten, --format, - --help, --impersonate-service-account, --log-http, --project, --quiet, - --trace-token, --user-output-enabled, --verbosity. - - Run $ gcloud help for details. - -NOTES - This command is currently in beta and might change without notice. This - variant is also available: - - $ gcloud alpha container hub namespaces rbacrolebindings list - diff --git a/gcloud/beta/container/hub/namespaces/rbacrolebindings/update b/gcloud/beta/container/hub/namespaces/rbacrolebindings/update deleted file mode 100644 index d9033e54a..000000000 --- a/gcloud/beta/container/hub/namespaces/rbacrolebindings/update +++ /dev/null @@ -1,95 +0,0 @@ -NAME - gcloud beta container hub namespaces rbacrolebindings update - update a - fleet namespace RBAC RoleBinding - -SYNOPSIS - gcloud beta container hub namespaces rbacrolebindings update - (NAME : --location=LOCATION --namespace=NAMESPACE) [--role=ROLE] - [--group=GROUP | --user=USER] [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (BETA) This command can fail for the following reasons: - ▪ The RoleBinding does not exist in the project. - ▪ The caller does not have permission to access the RoleBinding. - -EXAMPLES - To update the RBAC RoleBinding RBRB in namespace NAMESPACE in the active - project to the viewer role: - - $ gcloud beta container hub namespaces rbacrolebindings update \ - RBRB --namespace=NAMESPACE --role=viewer - - To update the RBAC RoleBinding RBRB in namespace NAMESPACE in the active - project to the user someone@google.com: - - $ gcloud beta container hub namespaces rbacrolebindings update \ - RBRB --namespace=NAMESPACE --user=someone@google.com - -POSITIONAL ARGUMENTS - Rbacrolebinding resource - The group of arguments defining an - RBACRoleBinding. 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 NAME 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. - - NAME - ID of the rbacrolebinding or fully qualified identifier for the - rbacrolebinding. - - To set the rbacrolebinding attribute: - ▸ provide the argument NAME on the command line. - - This positional argument must be specified if any of the other - arguments in this group are specified. - - --location=LOCATION - Location for the rbacrolebinding. - - To set the location attribute: - ▸ provide the argument NAME on the command line with a fully - specified name; - ▸ provide the argument --location on the command line; - ▸ set the property gkehub/location. - - --namespace=NAMESPACE - Name of the rbacrolebinding. - - To set the namespace attribute: - ▸ provide the argument NAME on the command line with a fully - specified name; - ▸ provide the argument --namespace on the command line. - -FLAGS - --role=ROLE - Role for the RBACRoleBinding to update to. ROLE must be one of: admin, - edit, view. - - At most one of these can be specified: - - --group=GROUP - Group for the RBACRoleBinding to update to. - - --user=USER - User for the RBACRoleBinding to update to. - -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 container hub namespaces rbacrolebindings update - diff --git a/gcloud/beta/container/hub/namespaces/update b/gcloud/beta/container/hub/namespaces/update deleted file mode 100644 index 9d4bae69a..000000000 --- a/gcloud/beta/container/hub/namespaces/update +++ /dev/null @@ -1,64 +0,0 @@ -NAME - gcloud beta container hub namespaces update - update a fleet namespace - -SYNOPSIS - gcloud beta container hub namespaces update NAME [--scope=SCOPE] - [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (BETA) This command can fail for the following reasons: - ▪ The project specified does not exist. - ▪ The fleet namespace does not exist in the project. - ▪ The caller does not have permission to access the project or - namespace. - -EXAMPLES - To update the namespace NAMESPACE in the active project: - - $ gcloud beta container hub namespaces update NAMESPACE - - To update the namespace NAMESPACE in project PROJECT_ID: - - $ gcloud beta container hub namespaces update NAMESPACE \ - --project=PROJECT_ID - -POSITIONAL ARGUMENTS - NAME - Name of the namespace to be updated. - -FLAGS - Scope resource - The group of arguments defining the Fleet Scope. 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 --scope on the command line with a fully - specified name; - ◆ provide the argument --project on the command line; - ◆ set the property core/project. - - To set the location attribute: - ◆ provide the argument --scope on the command line with a fully - specified name; - ◆ global is the only supported location. - - --scope=SCOPE - ID of the scope or fully qualified identifier for the scope. - - To set the scope attribute: - ▸ provide the argument --scope on the command line. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --configuration, --flags-file, --flatten, --format, - --help, --impersonate-service-account, --log-http, --project, --quiet, - --trace-token, --user-output-enabled, --verbosity. - - Run $ gcloud help for details. - -NOTES - This command is currently in beta and might change without notice. This - variant is also available: - - $ gcloud alpha container hub namespaces update - diff --git a/gcloud/beta/container/node-pools/create b/gcloud/beta/container/node-pools/create index 9d6786e87..73e881a65 100644 --- a/gcloud/beta/container/node-pools/create +++ b/gcloud/beta/container/node-pools/create @@ -53,9 +53,9 @@ SYNOPSIS --total-max-nodes=TOTAL_MAX_NODES --total-min-nodes=TOTAL_MIN_NODES] [--enable-best-effort-provision --min-provision-nodes=MIN_PROVISION_NODES] - [--ephemeral-storage=[local-ssd-count=LOCAL-SSD-COUNT] - | --ephemeral-storage-local-ssd=[count=COUNT] - | --local-nvme-ssd-block=[count=COUNT] + [--ephemeral-storage[=[local-ssd-count=LOCAL-SSD-COUNT]] + | --ephemeral-storage-local-ssd[=[count=COUNT]] + | --local-nvme-ssd-block[=[count=COUNT]] | --local-ssd-count=LOCAL_SSD_COUNT] [--location=LOCATION | --region=REGION | --zone=ZONE, -z ZONE] [--reservation=RESERVATION --reservation-affinity=RESERVATION_AFFINITY] @@ -820,7 +820,7 @@ FLAGS At most one of these can be specified: - --ephemeral-storage=[local-ssd-count=LOCAL-SSD-COUNT] + --ephemeral-storage[=[local-ssd-count=LOCAL-SSD-COUNT]] Parameters for the ephemeral storage filesystem. If unspecified, ephemeral storage is backed by the boot disk. @@ -837,7 +837,7 @@ FLAGS See https://cloud.google.com/compute/docs/disks/local-ssd for more information. - --ephemeral-storage-local-ssd=[count=COUNT] + --ephemeral-storage-local-ssd[=[count=COUNT]] Parameters for the ephemeral storage filesystem. If unspecified, ephemeral storage is backed by the boot disk. @@ -853,7 +853,7 @@ FLAGS See https://cloud.google.com/compute/docs/disks/local-ssd for more information. - --local-nvme-ssd-block=[count=COUNT] + --local-nvme-ssd-block[=[count=COUNT]] Adds the requested local SSDs on all nodes in default node pool(s) in the new cluster. diff --git a/gcloud/beta/container/vmware/clusters/create b/gcloud/beta/container/vmware/clusters/create index e17b89ae6..5dc1e3151 100644 --- a/gcloud/beta/container/vmware/clusters/create +++ b/gcloud/beta/container/vmware/clusters/create @@ -33,6 +33,12 @@ SYNOPSIS [--cpus=CPUS --enable-auto-resize --memory=MEMORY --replicas=REPLICAS] [--disable-control-plane-v2 | --enable-control-plane-v2] [--enable-advanced-networking --enable-dataplane-v2] + [--vcenter-ca-cert-data=VCENTER_CA_CERT_DATA + --vcenter-cluster=VCENTER_CLUSTER + --vcenter-datacenter=VCENTER_DATACENTER + --vcenter-datastore=VCENTER_DATASTORE --vcenter-folder=VCENTER_FOLDER + --vcenter-resource-pool=VCENTER_RESOURCE_POOL + --vcenter-storage-policy-name=VCENTER_STORAGE_POLICY_NAME] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -359,6 +365,30 @@ OPTIONAL FLAGS --enable-dataplane-v2 If set, enables Dataplane V2. + vCenter configurations for the cluster. If not specified, it is inherited + from the admin cluster. + + --vcenter-ca-cert-data=VCENTER_CA_CERT_DATA + Name of the vCenter CA certificate public key for SSL verification. + + --vcenter-cluster=VCENTER_CLUSTER + Name of the vCenter cluster for the user cluster. + + --vcenter-datacenter=VCENTER_DATACENTER + Name of the vCenter datacenter for the user cluster. + + --vcenter-datastore=VCENTER_DATASTORE + Name of the vCenter datastore for the user cluster. + + --vcenter-folder=VCENTER_FOLDER + Name of the vCenter folder for the user cluster. + + --vcenter-resource-pool=VCENTER_RESOURCE_POOL + Name of the vCenter resource pool for the user cluster. + + --vcenter-storage-policy-name=VCENTER_STORAGE_POLICY_NAME + Name of the vCenter storage policy for the user cluster. + 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/dataproc/clusters/create b/gcloud/beta/dataproc/clusters/create index 16009fb15..0b8c220d7 100644 --- a/gcloud/beta/dataproc/clusters/create +++ b/gcloud/beta/dataproc/clusters/create @@ -35,8 +35,9 @@ SYNOPSIS [--secondary-worker-boot-disk-size=SECONDARY_WORKER_BOOT_DISK_SIZE] [--secondary-worker-boot-disk-type=SECONDARY_WORKER_BOOT_DISK_TYPE] [--secondary-worker-local-ssd-interface=SECONDARY_WORKER_LOCAL_SSD_INTERFACE] - [--shielded-integrity-monitoring] [--shielded-secure-boot] - [--shielded-vtpm] [--temp-bucket=TEMP_BUCKET] + [--secondary-worker-machine-types=type=MACHINE_TYPE[, + type=MACHINE_TYPE...][,rank=RANK]] [--shielded-integrity-monitoring] + [--shielded-secure-boot] [--shielded-vtpm] [--temp-bucket=TEMP_BUCKET] [--worker-accelerator=[type=TYPE,[count=COUNT],...]] [--worker-boot-disk-size=WORKER_BOOT_DISK_SIZE] [--worker-boot-disk-type=WORKER_BOOT_DISK_TYPE] @@ -355,6 +356,11 @@ FLAGS Interface to use to attach local SSDs to each secondary worker in a cluster. + --secondary-worker-machine-types=type=MACHINE_TYPE[,type=MACHINE_TYPE...][,rank=RANK] + Types of machines with optional rank for secondary workers to use. + Defaults to server-specified.eg. + --secondary-worker-machine-types="type=e2-standard-8,type=t2d-standard-8,rank=0" + --shielded-integrity-monitoring Enables monitoring and attestation of the boot integrity of the cluster's VMs. vTPM (virtual Trusted Platform Module) must also be diff --git a/gcloud/beta/dataproc/workflow-templates/set-managed-cluster b/gcloud/beta/dataproc/workflow-templates/set-managed-cluster index 903b4e11d..83be2cd90 100644 --- a/gcloud/beta/dataproc/workflow-templates/set-managed-cluster +++ b/gcloud/beta/dataproc/workflow-templates/set-managed-cluster @@ -28,8 +28,9 @@ SYNOPSIS [--secondary-worker-boot-disk-size=SECONDARY_WORKER_BOOT_DISK_SIZE] [--secondary-worker-boot-disk-type=SECONDARY_WORKER_BOOT_DISK_TYPE] [--secondary-worker-local-ssd-interface=SECONDARY_WORKER_LOCAL_SSD_INTERFACE] - [--shielded-integrity-monitoring] [--shielded-secure-boot] - [--shielded-vtpm] [--temp-bucket=TEMP_BUCKET] + [--secondary-worker-machine-types=type=MACHINE_TYPE[, + type=MACHINE_TYPE...][,rank=RANK]] [--shielded-integrity-monitoring] + [--shielded-secure-boot] [--shielded-vtpm] [--temp-bucket=TEMP_BUCKET] [--worker-accelerator=[type=TYPE,[count=COUNT],...]] [--worker-boot-disk-size=WORKER_BOOT_DISK_SIZE] [--worker-boot-disk-type=WORKER_BOOT_DISK_TYPE] @@ -287,6 +288,11 @@ FLAGS Interface to use to attach local SSDs to each secondary worker in a cluster. + --secondary-worker-machine-types=type=MACHINE_TYPE[,type=MACHINE_TYPE...][,rank=RANK] + Types of machines with optional rank for secondary workers to use. + Defaults to server-specified.eg. + --secondary-worker-machine-types="type=e2-standard-8,type=t2d-standard-8,rank=0" + --shielded-integrity-monitoring Enables monitoring and attestation of the boot integrity of the cluster's VMs. vTPM (virtual Trusted Platform Module) must also be diff --git a/gcloud/beta/datastream/streams/create b/gcloud/beta/datastream/streams/create index f771693ab..e3ee449b3 100644 --- a/gcloud/beta/datastream/streams/create +++ b/gcloud/beta/datastream/streams/create @@ -91,13 +91,79 @@ REQUIRED FLAGS At most one of these can be specified: --mysql-excluded-objects=MYSQL_EXCLUDED_OBJECTS - MySQL data source objects to avoid backfilling. + Path to a YAML (or JSON) file containing the MySQL data sources to + avoid backfilling. + + The JSON file is formatted as follows, with camelCase field naming: + + { + "mysqlDatabases": [ + { + "database":"sample_database", + "mysqlTables": [ + { + "table": "sample_table", + "mysqlColumns": [ + { + "column": "sample_column", + } + ] + } + ] + } + ] + } + } --oracle-excluded-objects=ORACLE_EXCLUDED_OBJECTS - Oracle data source objects to avoid backfilling. + Path to a YAML (or JSON) file containing the Oracle data sources to + avoid backfilling. + + The JSON file is formatted as follows, with camelCase field naming: + + { + "oracleSchemas": [ + { + "schema": "SAMPLE", + "oracleTables": [ + { + "table": "SAMPLE_TABLE", + "oracleColumns": [ + { + "column": "COL", + } + ] + } + ] + } + ] + } + } --postgresql-excluded-objects=POSTGRESQL_EXCLUDED_OBJECTS - PostgreSQL data source objects to avoid backfilling. + Path to a YAML (or JSON) file containing the PostgreSQL data + sources to avoid backfilling. + + The JSON file is formatted as follows, with camelCase field naming: + + { + "postgresqlSchemas": [ + { + "schema": "SAMPLE", + "postgresqlTables": [ + { + "table": "SAMPLE_TABLE", + "postgresqlColumns": [ + { + "column": "COL", + } + ] + } + ] + } + ] + } + } This must be specified. diff --git a/gcloud/beta/datastream/streams/update b/gcloud/beta/datastream/streams/update index 9d1034b5e..edcdf3b6f 100644 --- a/gcloud/beta/datastream/streams/update +++ b/gcloud/beta/datastream/streams/update @@ -112,13 +112,79 @@ FLAGS At most one of these can be specified: --mysql-excluded-objects=MYSQL_EXCLUDED_OBJECTS - MySQL data source objects to avoid backfilling. + Path to a YAML (or JSON) file containing the MySQL data sources to + avoid backfilling. + + The JSON file is formatted as follows, with camelCase field naming: + + { + "mysqlDatabases": [ + { + "database":"sample_database", + "mysqlTables": [ + { + "table": "sample_table", + "mysqlColumns": [ + { + "column": "sample_column", + } + ] + } + ] + } + ] + } + } --oracle-excluded-objects=ORACLE_EXCLUDED_OBJECTS - Oracle data source objects to avoid backfilling. + Path to a YAML (or JSON) file containing the Oracle data sources to + avoid backfilling. + + The JSON file is formatted as follows, with camelCase field naming: + + { + "oracleSchemas": [ + { + "schema": "SAMPLE", + "oracleTables": [ + { + "table": "SAMPLE_TABLE", + "oracleColumns": [ + { + "column": "COL", + } + ] + } + ] + } + ] + } + } --postgresql-excluded-objects=POSTGRESQL_EXCLUDED_OBJECTS - PostgreSQL data source objects to avoid backfilling. + Path to a YAML (or JSON) file containing the PostgreSQL data + sources to avoid backfilling. + + The JSON file is formatted as follows, with camelCase field naming: + + { + "postgresqlSchemas": [ + { + "schema": "SAMPLE", + "postgresqlTables": [ + { + "table": "SAMPLE_TABLE", + "postgresqlColumns": [ + { + "column": "COL", + } + ] + } + ] + } + ] + } + } At most one of these can be specified: diff --git a/gcloud/beta/functions/deploy b/gcloud/beta/functions/deploy index 01520d5ff..d24834166 100644 --- a/gcloud/beta/functions/deploy +++ b/gcloud/beta/functions/deploy @@ -632,8 +632,8 @@ FLAGS The provided attribute/value pair will be used with the match-path-pattern operator to configure the trigger, see https://cloud.google.com/eventarc/docs/reference/rest/v1/projects.locations.triggers#eventfilter - and http://cloud/eventarc/docs/path-patterns for more details about - on how to construct path patterns. + and https://cloud.google.com/eventarc/docs/path-patterns for more + details about on how to construct path patterns. For example, to filter on events for Compute Engine VMs in a given zone: diff --git a/gcloud/beta/iam/workforce-pools/providers/create-oidc b/gcloud/beta/iam/workforce-pools/providers/create-oidc index 5488c0639..709c3d809 100644 --- a/gcloud/beta/iam/workforce-pools/providers/create-oidc +++ b/gcloud/beta/iam/workforce-pools/providers/create-oidc @@ -12,7 +12,8 @@ SYNOPSIS : --web-sso-additional-scopes=[WEB_SSO_ADDITIONAL_SCOPES,...]) [--async] [--attribute-condition=ATTRIBUTE_CONDITION] [--client-secret-value=CLIENT_SECRET_VALUE] [--description=DESCRIPTION] - [--disabled] [--display-name=DISPLAY_NAME] [GCLOUD_WIDE_FLAG ...] + [--disabled] [--display-name=DISPLAY_NAME] + [--jwk-json-path=JWK_JSON_PATH] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) Create a new OIDC workforce pool provider. @@ -33,7 +34,8 @@ EXAMPLES --issuer-uri="https://test-idp.com" \ --web-sso-response-type="code" \ --web-sso-assertion-claims-behavior="merge-user-info-over-id-tok\ - en-claims" --web-sso-additional-scopes="groups,photos" + en-claims" --web-sso-additional-scopes="groups,photos" \ + --jwk-json-path="path/to/jwk.json" POSITIONAL ARGUMENTS Workforce pool provider resource - The workforce pool provider to create. @@ -244,6 +246,26 @@ OPTIONAL FLAGS A display name for the workforce pool provider. Cannot exceed 32 characters in length. + --jwk-json-path=JWK_JSON_PATH + Optional file containing JSON Web Key (JWK) public keys. The file + format must follow JWK specifications + (https://www.rfc-editor.org/rfc/rfc7517#section-4). Example file + format: { + "keys": [ + { + "kty": "RSA/EC", + "alg": "", + "use": "sig", + "kid": "", + "n": "", + "e": "", + "x": "", + "y": "", + "crv": "" + } + ] + } + 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/iam/workforce-pools/providers/update-oidc b/gcloud/beta/iam/workforce-pools/providers/update-oidc index 94f6716d8..ca137be0b 100644 --- a/gcloud/beta/iam/workforce-pools/providers/update-oidc +++ b/gcloud/beta/iam/workforce-pools/providers/update-oidc @@ -8,7 +8,7 @@ SYNOPSIS [--async] [--attribute-condition=ATTRIBUTE_CONDITION] [--attribute-mapping=[KEY=VALUE,...]] [--client-id=CLIENT_ID] [--description=DESCRIPTION] [--disabled] [--display-name=DISPLAY_NAME] - [--issuer-uri=ISSUER_URI] + [--issuer-uri=ISSUER_URI] [--jwk-json-path=JWK_JSON_PATH] [--web-sso-additional-scopes=[WEB_SSO_ADDITIONAL_SCOPES,...]] [--web-sso-assertion-claims-behavior=WEB_SSO_ASSERTION_CLAIMS_BEHAVIOR] [--web-sso-response-type=WEB_SSO_RESPONSE_TYPE] @@ -34,7 +34,8 @@ EXAMPLES --issuer-uri="https://test-idp.com" \ --web-sso-response-type="code" \ --web-sso-assertion-claims-behavior="merge-user-info-over-id-tok\ - en-claims" --web-sso-additional-scopes="groups,photos" + en-claims" --web-sso-additional-scopes="groups,photos" \ + --jwk-json-path="path/to/jwk.json" POSITIONAL ARGUMENTS Workforce pool provider resource - The workforce pool provider to update. @@ -195,6 +196,26 @@ FLAGS --issuer-uri=ISSUER_URI The OIDC issuer URI. Must be a valid URI using the 'https' scheme. + --jwk-json-path=JWK_JSON_PATH + Optional file containing JSON Web Key (JWK) public keys. The file + format must follow JWK specifications + (https://www.rfc-editor.org/rfc/rfc7517#section-4). Example file + format: { + "keys": [ + { + "kty": "RSA/EC", + "alg": "", + "use": "sig", + "kid": "", + "n": "", + "e": "", + "x": "", + "y": "", + "crv": "" + } + ] + } + --web-sso-additional-scopes=[WEB_SSO_ADDITIONAL_SCOPES,...] Additional scopes to request for the OIDC authentication on top of scopes requested by default. By default, the openid, profile and email diff --git a/gcloud/beta/memcache/instances/create b/gcloud/beta/memcache/instances/create index 7f40305f4..752846866 100644 --- a/gcloud/beta/memcache/instances/create +++ b/gcloud/beta/memcache/instances/create @@ -108,10 +108,12 @@ OPTIONAL FLAGS --memcached-version=MEMCACHED_VERSION Optional major version of Memcached software to use with the instance. If not provided, default of "1.5" will be used. MEMCACHED_VERSION must - be (only one value is supported): + be one of: 1.5 Memcached major version 1.5 + 1.6.15 + Memcached version 1.6.15 --parameters=KEY=VALUE User defined parameters to apply to the memcached process on each node. diff --git a/gcloud/beta/memcache/instances/help b/gcloud/beta/memcache/instances/help index 016aa69c5..95935ebeb 100644 --- a/gcloud/beta/memcache/instances/help +++ b/gcloud/beta/memcache/instances/help @@ -42,6 +42,9 @@ COMMANDS update (BETA) Update a Memorystore Memcached instance. + upgrade + (BETA) Upgrade memcache instance to a newer memcached version. + NOTES This command is currently in beta and might change without notice. These variants are also available: diff --git a/gcloud/beta/memcache/instances/upgrade b/gcloud/beta/memcache/instances/upgrade new file mode 100644 index 000000000..62ea5473e --- /dev/null +++ b/gcloud/beta/memcache/instances/upgrade @@ -0,0 +1,84 @@ +NAME + gcloud beta memcache instances upgrade - upgrade memcache instance to a + newer memcached version + +SYNOPSIS + gcloud beta memcache instances upgrade (INSTANCE : --region=REGION) + --memcached-version=MEMCACHED_VERSION [--async] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Upgrade memcahce instance to a newer memcached version. + +EXAMPLES + To upgrade memcache version of an instance with the name + 'my-memcache-instance' in region 'us-central-1' to MEMCACHE_1_6_15 + + $ gcloud beta memcache instances upgrade my-memcache-instance \ + --region=us-central1 --memcached-version="1.6.15" + +POSITIONAL ARGUMENTS + Instance resource - Arguments and flags that specify the Memorystore for + Memcached instance you want to upgrade. The arguments in this group can be + used to specify the attributes of this resource. (NOTE) Some attributes + are not given arguments in this group but can be set in other ways. + + To set the project attribute: + ◆ provide the argument instance on the command line with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + INSTANCE + ID of the instance or fully qualified identifier for the instance. + + To set the instance attribute: + ▸ provide the argument instance on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --region=REGION + The name of the Memcached region of the instance. Overrides the + default memcache/region property value for this command invocation. + + To set the region attribute: + ▸ provide the argument instance on the command line with a fully + specified name; + ▸ provide the argument --region on the command line; + ▸ set the property memcache/region. + +REQUIRED FLAGS + --memcached-version=MEMCACHED_VERSION + Memcached engine version to which instance should be upgraded to. + MEMCACHED_VERSION must be (only one value is supported): + + 1.6.15 + Memcached engine version 1.6.15 + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the memcache/v1beta2 API. The full documentation for this + API can be found at: https://cloud.google.com/memorystore/ + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud memcache instances upgrade + + $ gcloud alpha memcache instances upgrade + diff --git a/gcloud/beta/network-services/service-lb-policies/create b/gcloud/beta/network-services/service-lb-policies/create index 53c38b9d0..f90f05f3b 100644 --- a/gcloud/beta/network-services/service-lb-policies/create +++ b/gcloud/beta/network-services/service-lb-policies/create @@ -6,6 +6,7 @@ SYNOPSIS gcloud beta network-services service-lb-policies create (SERVICE_LB_POLICY : --location=LOCATION) [--async] [--auto-capacity-drain] [--description=DESCRIPTION] + [--failover-health-threshold=FAILOVER_HEALTH_THRESHOLD] [--load-balancing-algorithm=LOAD_BALANCING_ALGORITHM; default="waterfall-by-region"] [GCLOUD_WIDE_FLAG ...] @@ -68,6 +69,14 @@ FLAGS --description=DESCRIPTION The description for the service LB policy. + --failover-health-threshold=FAILOVER_HEALTH_THRESHOLD + The percentage threshold that a load balancer will begin to send + traffic to failover backends. If the percentage of endpoints in a + MIG/NEG is smaller than this value, traffic would be sent to failover + backends if possible. This field should be set to a value between 1 and + 99. The default value is 50 for Global external HTTP(S) load balancer + (classic) and Proxyless service mesh, and 70 for others. + --load-balancing-algorithm=LOAD_BALANCING_ALGORITHM; default="waterfall-by-region" The global load balancing algorithm to be used. LOAD_BALANCING_ALGORITHM must be one of: diff --git a/gcloud/beta/network-services/service-lb-policies/update b/gcloud/beta/network-services/service-lb-policies/update index 599c7a837..0f9d10686 100644 --- a/gcloud/beta/network-services/service-lb-policies/update +++ b/gcloud/beta/network-services/service-lb-policies/update @@ -6,6 +6,7 @@ SYNOPSIS gcloud beta network-services service-lb-policies update (SERVICE_LB_POLICY : --location=LOCATION) [--async] [--auto-capacity-drain] [--description=DESCRIPTION] + [--failover-health-threshold=FAILOVER_HEALTH_THRESHOLD] [--load-balancing-algorithm=LOAD_BALANCING_ALGORITHM; default="waterfall-by-region"] [GCLOUD_WIDE_FLAG ...] @@ -67,6 +68,14 @@ FLAGS --description=DESCRIPTION The description for the service LB policy. + --failover-health-threshold=FAILOVER_HEALTH_THRESHOLD + The percentage threshold that a load balancer will begin to send + traffic to failover backends. If the percentage of endpoints in a + MIG/NEG is smaller than this value, traffic would be sent to failover + backends if possible. This field should be set to a value between 1 and + 99. The default value is 50 for Global external HTTP(S) load balancer + (classic) and Proxyless service mesh, and 70 for others. + --load-balancing-algorithm=LOAD_BALANCING_ALGORITHM; default="waterfall-by-region" The global load balancing algorithm to be used. LOAD_BALANCING_ALGORITHM must be one of: diff --git a/gcloud/beta/secrets/delete b/gcloud/beta/secrets/delete index c08a55582..8143734e0 100644 --- a/gcloud/beta/secrets/delete +++ b/gcloud/beta/secrets/delete @@ -6,7 +6,7 @@ SYNOPSIS DESCRIPTION (BETA) Delete a secret and destroy all secret versions. This action is - irreversable. If the given secret does not exist, this command will + irreversible. If the given secret does not exist, this command will succeed, but the operation will be a no-op. EXAMPLES diff --git a/gcloud/beta/services/list b/gcloud/beta/services/list index 70aa41d1d..825b6df81 100644 --- a/gcloud/beta/services/list +++ b/gcloud/beta/services/list @@ -13,14 +13,26 @@ DESCRIPTION --enabled is the default. EXAMPLES - To list the services the current project has enabled for consumption, run: + To list the services for the current project has enabled for consumption, + run: $ gcloud beta services list --enabled - To list the services the current project can enable for consumption, run: + To list the services for the current project can enable for consumption, + run: $ gcloud beta services list --available + To list the services for project my-project has enabled for consumption, + run: + + $ gcloud beta services list --enabled --project=my-project + + To list the services the project my-project can enable for consumption, + run: + + $ gcloud beta services list --available --project=my-project + FLAGS At most one of these can be specified: @@ -65,10 +77,8 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. NOTES - This command is currently in beta and might change without notice. These - variants are also available: + This command is currently in beta and might change without notice. This + variant is also available: $ gcloud services list - $ gcloud alpha services list - diff --git a/gcloud/compute/instance-templates/create b/gcloud/compute/instance-templates/create index 89d6d0687..6a22742f4 100644 --- a/gcloud/compute/instance-templates/create +++ b/gcloud/compute/instance-templates/create @@ -927,7 +927,14 @@ FLAGS --reservation-affinity=RESERVATION_AFFINITY; default="any" The type of reservation for instances created from this template. - RESERVATION_AFFINITY must be one of: any, none, specific. + RESERVATION_AFFINITY must be one of: + + any + Consume any available, matching reservation. + none + Do not consume from any reserved capacity. + specific + Must consume from a specific reservation. At most one of these can be specified: diff --git a/gcloud/compute/instances/bulk/create b/gcloud/compute/instances/bulk/create index 929afd500..28fda2b90 100644 --- a/gcloud/compute/instances/bulk/create +++ b/gcloud/compute/instances/bulk/create @@ -895,7 +895,14 @@ OPTIONAL FLAGS --reservation-affinity=RESERVATION_AFFINITY; default="any" The type of reservation for the instance. RESERVATION_AFFINITY must - be one of: any, none, specific. + be one of: + + any + Consume any available, matching reservation. + none + Do not consume from any reserved capacity. + specific + Must consume from a specific reservation. At most one of these can be specified: diff --git a/gcloud/compute/instances/create b/gcloud/compute/instances/create index bbc1d0108..629f722f0 100644 --- a/gcloud/compute/instances/create +++ b/gcloud/compute/instances/create @@ -1105,7 +1105,14 @@ FLAGS --reservation-affinity=RESERVATION_AFFINITY; default="any" The type of reservation for the instance. RESERVATION_AFFINITY must - be one of: any, none, specific. + be one of: + + any + Consume any available, matching reservation. + none + Do not consume from any reserved capacity. + specific + Must consume from a specific reservation. At most one of these can be specified: diff --git a/gcloud/compute/networks/subnets/create b/gcloud/compute/networks/subnets/create index 97b6c7dfe..80b8b9ee6 100644 --- a/gcloud/compute/networks/subnets/create +++ b/gcloud/compute/networks/subnets/create @@ -102,6 +102,8 @@ OPTIONAL FLAGS --purpose=PURPOSE The purpose of this subnetwork. PURPOSE must be one of: + GLOBAL_MANAGED_PROXY + Reserved for Global Envoy-based Load Balancing. INTERNAL_HTTPS_LOAD_BALANCER Reserved for Internal HTTP(S) Load Balancing. PRIVATE @@ -109,7 +111,7 @@ OPTIONAL FLAGS PRIVATE_SERVICE_CONNECT Reserved for Private Service Connect Internal Load Balancing. REGIONAL_MANAGED_PROXY - Reserved for Regional HTTP(S) Load Balancing. + Reserved for Regional Envoy-based Load Balancing. --region=REGION Region of the subnetwork to create. If not specified, you might be @@ -133,8 +135,8 @@ OPTIONAL FLAGS --role=ROLE The role of subnetwork. This field is required when the purpose is set - to REGIONAL_MANAGED_PROXY or INTERNAL_HTTPS_LOAD_BALANCER. ROLE must be - one of: + to GLOBAL_MANAGED_PROXY, REGIONAL_MANAGED_PROXY or + INTERNAL_HTTPS_LOAD_BALANCER. ROLE must be one of: ACTIVE The ACTIVE subnet that is currently used. diff --git a/gcloud/compute/security-policies/update b/gcloud/compute/security-policies/update index b9ae8e611..fdc1d7060 100644 --- a/gcloud/compute/security-policies/update +++ b/gcloud/compute/security-policies/update @@ -43,8 +43,8 @@ FLAGS --json-parsing=JSON_PARSING The JSON parsing behavior for this rule. Must be one of the following - values: [DISABLED, STANDARD]. JSON_PARSING must be one of: DISABLED, - STANDARD. + values: [DISABLED, STANDARD, STANDARD_WITH_GRAPHQL]. JSON_PARSING must + be one of: DISABLED, STANDARD, STANDARD_WITH_GRAPHQL. --layer7-ddos-defense-rule-visibility=VISIBILITY_TYPE The visibility type indicates whether the rules are opaque or diff --git a/gcloud/compute/tpus/tpu-vm/help b/gcloud/compute/tpus/tpu-vm/help index 3175b2b0f..09667d047 100644 --- a/gcloud/compute/tpus/tpu-vm/help +++ b/gcloud/compute/tpus/tpu-vm/help @@ -54,6 +54,9 @@ COMMANDS stop Stop a Cloud TPU VM node. + update + Update a Cloud TPU VM node. + NOTES This variant is also available: diff --git a/gcloud/compute/tpus/tpu-vm/update b/gcloud/compute/tpus/tpu-vm/update new file mode 100644 index 000000000..17c8ae0ce --- /dev/null +++ b/gcloud/compute/tpus/tpu-vm/update @@ -0,0 +1,76 @@ +NAME + gcloud compute tpus tpu-vm update - update a Cloud TPU VM node + +SYNOPSIS + gcloud compute tpus tpu-vm update (TPU : --zone=ZONE) [--async] + [--description=DESCRIPTION] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Update a Cloud TPU VM node. + +EXAMPLES + To modify a TPU VM node with ID my-tpu in the default user project and + compute/zone by updating the description to "A new description", run: + + $ gcloud compute tpus tpu-vm update my-tpu \ + --description="A new description" + +POSITIONAL ARGUMENTS + Tpu resource - Name of the Cloud TPU VM node to update. The arguments in + this group can be used to specify the attributes of this resource. (NOTE) + Some attributes are not given arguments in this group but can be set in + other ways. + + To set the project attribute: + ◆ provide the argument tpu 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. + + TPU + ID of the tpu or fully qualified identifier for the tpu. + + To set the tpu attribute: + ▸ provide the argument tpu on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --zone=ZONE + Zone of the Cloud TPU. + + If not specified, will use default compute/zone. + + To set the zone attribute: + ▸ provide the argument tpu on the command line with a fully + specified name; + ▸ provide the argument --zone on the command line; + ▸ set the property compute/zone. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --description=DESCRIPTION + Text description of the TPU. + +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 tpu/v2 API. The full documentation for this API can + be found at: https://cloud.google.com/tpu/ + +NOTES + This variant is also available: + + $ gcloud alpha compute tpus tpu-vm update + diff --git a/gcloud/config/get b/gcloud/config/get index 8cf049d2a..354698f49 100644 --- a/gcloud/config/get +++ b/gcloud/config/get @@ -1266,6 +1266,26 @@ AVAILABLE PROPERTIES the default storage class and retention period for the destination bucket meet the criteria for parallel composite upload. + parallel_composite_upload_component_prefix + The prefix used when naming temporary components created by + composite uploads. If the prefix begins with a /, the temporary + components are uploaded relative to the bucket name. If the prefix + does not begin with a /, the temporary components are uploaded + relative to the prefix portion of the destination object name. For + example, consider an upload that will create a final object named + gs://bucket/dir1/dir2/object. Using a prefix of /prefix means + temporary components use names like + gs://bucket/prefix/COMPONENT_NAME. Using a prefix of prefix means + temporary components use names like + gs://bucket/dir1/dir2/prefix/COMPONENT_NAME. Note that this can + complicate cleaning up temporary components, as they will not all + share a common prefix. If this property is not specified, gcloud + storage uses the prefix + /gcloud/tmp/parallel_composite_uploads/see_gcloud_storage_cp_help_for_details/. + If a chosen prefix results in temporary component names longer than + the maximum length Cloud Storage allows, gcloud storage performs a + non-composite upload. + parallel_composite_upload_component_size Specifies the ideal size of a component in bytes, which will act as an upper bound to the size of the components if ceil(file_size / diff --git a/gcloud/config/help b/gcloud/config/help index b398240e9..62f138468 100644 --- a/gcloud/config/help +++ b/gcloud/config/help @@ -1298,6 +1298,26 @@ AVAILABLE PROPERTIES the default storage class and retention period for the destination bucket meet the criteria for parallel composite upload. + parallel_composite_upload_component_prefix + The prefix used when naming temporary components created by + composite uploads. If the prefix begins with a /, the temporary + components are uploaded relative to the bucket name. If the prefix + does not begin with a /, the temporary components are uploaded + relative to the prefix portion of the destination object name. For + example, consider an upload that will create a final object named + gs://bucket/dir1/dir2/object. Using a prefix of /prefix means + temporary components use names like + gs://bucket/prefix/COMPONENT_NAME. Using a prefix of prefix means + temporary components use names like + gs://bucket/dir1/dir2/prefix/COMPONENT_NAME. Note that this can + complicate cleaning up temporary components, as they will not all + share a common prefix. If this property is not specified, gcloud + storage uses the prefix + /gcloud/tmp/parallel_composite_uploads/see_gcloud_storage_cp_help_for_details/. + If a chosen prefix results in temporary component names longer than + the maximum length Cloud Storage allows, gcloud storage performs a + non-composite upload. + parallel_composite_upload_component_size Specifies the ideal size of a component in bytes, which will act as an upper bound to the size of the components if ceil(file_size / diff --git a/gcloud/config/list b/gcloud/config/list index 985116cbb..f0e190ef8 100644 --- a/gcloud/config/list +++ b/gcloud/config/list @@ -1310,6 +1310,26 @@ AVAILABLE PROPERTIES the default storage class and retention period for the destination bucket meet the criteria for parallel composite upload. + parallel_composite_upload_component_prefix + The prefix used when naming temporary components created by + composite uploads. If the prefix begins with a /, the temporary + components are uploaded relative to the bucket name. If the prefix + does not begin with a /, the temporary components are uploaded + relative to the prefix portion of the destination object name. For + example, consider an upload that will create a final object named + gs://bucket/dir1/dir2/object. Using a prefix of /prefix means + temporary components use names like + gs://bucket/prefix/COMPONENT_NAME. Using a prefix of prefix means + temporary components use names like + gs://bucket/dir1/dir2/prefix/COMPONENT_NAME. Note that this can + complicate cleaning up temporary components, as they will not all + share a common prefix. If this property is not specified, gcloud + storage uses the prefix + /gcloud/tmp/parallel_composite_uploads/see_gcloud_storage_cp_help_for_details/. + If a chosen prefix results in temporary component names longer than + the maximum length Cloud Storage allows, gcloud storage performs a + non-composite upload. + parallel_composite_upload_component_size Specifies the ideal size of a component in bytes, which will act as an upper bound to the size of the components if ceil(file_size / diff --git a/gcloud/config/set b/gcloud/config/set index cf73165db..54b2f08e6 100644 --- a/gcloud/config/set +++ b/gcloud/config/set @@ -1313,6 +1313,26 @@ AVAILABLE PROPERTIES the default storage class and retention period for the destination bucket meet the criteria for parallel composite upload. + parallel_composite_upload_component_prefix + The prefix used when naming temporary components created by + composite uploads. If the prefix begins with a /, the temporary + components are uploaded relative to the bucket name. If the prefix + does not begin with a /, the temporary components are uploaded + relative to the prefix portion of the destination object name. For + example, consider an upload that will create a final object named + gs://bucket/dir1/dir2/object. Using a prefix of /prefix means + temporary components use names like + gs://bucket/prefix/COMPONENT_NAME. Using a prefix of prefix means + temporary components use names like + gs://bucket/dir1/dir2/prefix/COMPONENT_NAME. Note that this can + complicate cleaning up temporary components, as they will not all + share a common prefix. If this property is not specified, gcloud + storage uses the prefix + /gcloud/tmp/parallel_composite_uploads/see_gcloud_storage_cp_help_for_details/. + If a chosen prefix results in temporary component names longer than + the maximum length Cloud Storage allows, gcloud storage performs a + non-composite upload. + parallel_composite_upload_component_size Specifies the ideal size of a component in bytes, which will act as an upper bound to the size of the components if ceil(file_size / diff --git a/gcloud/config/unset b/gcloud/config/unset index 0a0d59055..9909cf2c2 100644 --- a/gcloud/config/unset +++ b/gcloud/config/unset @@ -1274,6 +1274,26 @@ AVAILABLE PROPERTIES the default storage class and retention period for the destination bucket meet the criteria for parallel composite upload. + parallel_composite_upload_component_prefix + The prefix used when naming temporary components created by + composite uploads. If the prefix begins with a /, the temporary + components are uploaded relative to the bucket name. If the prefix + does not begin with a /, the temporary components are uploaded + relative to the prefix portion of the destination object name. For + example, consider an upload that will create a final object named + gs://bucket/dir1/dir2/object. Using a prefix of /prefix means + temporary components use names like + gs://bucket/prefix/COMPONENT_NAME. Using a prefix of prefix means + temporary components use names like + gs://bucket/dir1/dir2/prefix/COMPONENT_NAME. Note that this can + complicate cleaning up temporary components, as they will not all + share a common prefix. If this property is not specified, gcloud + storage uses the prefix + /gcloud/tmp/parallel_composite_uploads/see_gcloud_storage_cp_help_for_details/. + If a chosen prefix results in temporary component names longer than + the maximum length Cloud Storage allows, gcloud storage performs a + non-composite upload. + parallel_composite_upload_component_size Specifies the ideal size of a component in bytes, which will act as an upper bound to the size of the components if ceil(file_size / diff --git a/gcloud/container/clusters/create b/gcloud/container/clusters/create index 63b35e887..712496e9d 100644 --- a/gcloud/container/clusters/create +++ b/gcloud/container/clusters/create @@ -99,8 +99,8 @@ SYNOPSIS [--enable-private-endpoint --enable-private-nodes --master-ipv4-cidr=MASTER_IPV4_CIDR] [--enable-tpu --tpu-ipv4-cidr=CIDR] - [--ephemeral-storage-local-ssd=[count=COUNT] - | --local-nvme-ssd-block=[count=COUNT] + [--ephemeral-storage-local-ssd[=[count=COUNT]] + | --local-nvme-ssd-block[=[count=COUNT]] | --local-ssd-count=LOCAL_SSD_COUNT] [--location=LOCATION | --region=REGION | --zone=ZONE, -z ZONE] [--maintenance-window=START_TIME | --maintenance-window-end=TIME_STAMP @@ -1589,7 +1589,7 @@ FLAGS At most one of these can be specified: - --ephemeral-storage-local-ssd=[count=COUNT] + --ephemeral-storage-local-ssd[=[count=COUNT]] Parameters for the ephemeral storage filesystem. If unspecified, ephemeral storage is backed by the boot disk. @@ -1605,7 +1605,7 @@ FLAGS See https://cloud.google.com/compute/docs/disks/local-ssd for more information. - --local-nvme-ssd-block=[count=COUNT] + --local-nvme-ssd-block[=[count=COUNT]] Adds the requested local SSDs on all nodes in default node pool(s) in the new cluster. diff --git a/gcloud/container/clusters/create-auto b/gcloud/container/clusters/create-auto index 802ae7c7d..432279fba 100644 --- a/gcloud/container/clusters/create-auto +++ b/gcloud/container/clusters/create-auto @@ -13,7 +13,7 @@ SYNOPSIS [--create-subnetwork=[KEY=VALUE,...]] [--database-encryption-key=DATABASE_ENCRYPTION_KEY] [--dataplane-v2-observability-mode=DATAPLANE_V2_OBSERVABILITY_MODE] - [--enable-google-cloud-access] + [--enable-backup-restore] [--enable-google-cloud-access] [--enable-kubernetes-unstable-apis=API,[API,...]] [--enable-master-global-access] [--logging=[COMPONENT,...]] [--monitoring=[COMPONENT,...]] [--network=NETWORK] @@ -190,6 +190,11 @@ FLAGS Makes Advanced Datapath Observability available from the VPC network. + --enable-backup-restore + Enable the Backup for GKE add-on. This add-on is disabled by default. + To learn more, see the Backup for GKE overview: + https://cloud.google.com/kubernetes-engine/docs/add-on/backup-for-gke/concepts/backup-for-gke. + --enable-google-cloud-access When you enable Google Cloud Access, any public IP addresses owned by Google Cloud can reach the public control plane endpoint of your diff --git a/gcloud/container/node-pools/create b/gcloud/container/node-pools/create index 40a4e09bd..a4d856e73 100644 --- a/gcloud/container/node-pools/create +++ b/gcloud/container/node-pools/create @@ -53,8 +53,8 @@ SYNOPSIS --total-max-nodes=TOTAL_MAX_NODES --total-min-nodes=TOTAL_MIN_NODES] [--enable-best-effort-provision --min-provision-nodes=MIN_PROVISION_NODES] - [--ephemeral-storage-local-ssd=[count=COUNT] - | --local-nvme-ssd-block=[count=COUNT] + [--ephemeral-storage-local-ssd[=[count=COUNT]] + | --local-nvme-ssd-block[=[count=COUNT]] | --local-ssd-count=LOCAL_SSD_COUNT] [--location=LOCATION | --region=REGION | --zone=ZONE, -z ZONE] [--reservation=RESERVATION --reservation-affinity=RESERVATION_AFFINITY] @@ -796,7 +796,7 @@ FLAGS At most one of these can be specified: - --ephemeral-storage-local-ssd=[count=COUNT] + --ephemeral-storage-local-ssd[=[count=COUNT]] Parameters for the ephemeral storage filesystem. If unspecified, ephemeral storage is backed by the boot disk. @@ -812,7 +812,7 @@ FLAGS See https://cloud.google.com/compute/docs/disks/local-ssd for more information. - --local-nvme-ssd-block=[count=COUNT] + --local-nvme-ssd-block[=[count=COUNT]] Adds the requested local SSDs on all nodes in default node pool(s) in the new cluster. diff --git a/gcloud/database-migration/connection-profiles/create/cloudsql b/gcloud/database-migration/connection-profiles/create/cloudsql index f702e93f5..a49bfb86c 100644 --- a/gcloud/database-migration/connection-profiles/create/cloudsql +++ b/gcloud/database-migration/connection-profiles/create/cloudsql @@ -78,7 +78,7 @@ REQUIRED FLAGS --database-version=DATABASE_VERSION Database engine type and version. DATABASE_VERSION must be one of: MYSQL_5_7, MYSQL_5_6, MYSQL_8_0, POSTGRES_9_6, POSTGRES_10, - POSTGRES_11, POSTGRES_12, POSTGRES_13, POSTGRES_14. + POSTGRES_11, POSTGRES_12, POSTGRES_13, POSTGRES_14, POSTGRES_15. Connection profile resource - Database Migration Service source connection profile ID. This represents a Cloud resource. (NOTE) Some attributes are diff --git a/gcloud/database-migration/connection-profiles/create/mysql b/gcloud/database-migration/connection-profiles/create/mysql index 6af13cd9a..6340ecd0f 100644 --- a/gcloud/database-migration/connection-profiles/create/mysql +++ b/gcloud/database-migration/connection-profiles/create/mysql @@ -88,9 +88,9 @@ FLAGS --ca-certificate=CA_CERTIFICATE x509 PEM-encoded certificate of the CA that signed the database - server's certificate. The replica will use this certificate to verify - it's connecting to the correct host. Database Migration Service - encrypts the value when storing it. + server's certificate. Database Migration Service will use this + certificate to verify it's connecting to the correct host. Database + Migration Service encrypts the value when storing it. --client-certificate=CLIENT_CERTIFICATE x509 PEM-encoded certificate that will be used by the replica to diff --git a/gcloud/database-migration/connection-profiles/create/oracle b/gcloud/database-migration/connection-profiles/create/oracle index a994dc3dc..cde35b2cd 100644 --- a/gcloud/database-migration/connection-profiles/create/oracle +++ b/gcloud/database-migration/connection-profiles/create/oracle @@ -7,7 +7,8 @@ SYNOPSIS (CONNECTION_PROFILE : --region=REGION) --database-service=DATABASE_SERVICE --host=HOST --port=PORT --username=USERNAME (--password=PASSWORD | --prompt-for-password) - [--no-async] [--display-name=DISPLAY_NAME] [--labels=[KEY=VALUE,...]] + [--no-async] [--ca-certificate=CA_CERTIFICATE] + [--display-name=DISPLAY_NAME] [--labels=[KEY=VALUE,...]] [--private-connection=PRIVATE_CONNECTION | --static-ip-connectivity | [--forward-ssh-hostname=FORWARD_SSH_HOSTNAME --forward-ssh-username=FORWARD_SSH_USERNAME @@ -90,6 +91,12 @@ OPTIONAL FLAGS --no-async Waits for the operation in progress to complete before returning. + --ca-certificate=CA_CERTIFICATE + x509 PEM-encoded certificate of the CA that signed the database + server's certificate. Database Migration Service will use this + certificate to verify it's connecting to the correct host. Database + Migration Service encrypts the value when storing it. + --display-name=DISPLAY_NAME A user-friendly name for the connection profile. The display name can include letters, numbers, spaces, and hyphens, and must start with a diff --git a/gcloud/database-migration/connection-profiles/create/postgresql b/gcloud/database-migration/connection-profiles/create/postgresql index fb03450c0..5a7d0bc27 100644 --- a/gcloud/database-migration/connection-profiles/create/postgresql +++ b/gcloud/database-migration/connection-profiles/create/postgresql @@ -86,9 +86,9 @@ FLAGS --ca-certificate=CA_CERTIFICATE x509 PEM-encoded certificate of the CA that signed the database - server's certificate. The replica will use this certificate to verify - it's connecting to the correct host. Database Migration Service - encrypts the value when storing it. + server's certificate. Database Migration Service will use this + certificate to verify it's connecting to the correct host. Database + Migration Service encrypts the value when storing it. --client-certificate=CLIENT_CERTIFICATE x509 PEM-encoded certificate that will be used by the replica to diff --git a/gcloud/database-migration/connection-profiles/update b/gcloud/database-migration/connection-profiles/update index 24d05a6de..044205e9a 100644 --- a/gcloud/database-migration/connection-profiles/update +++ b/gcloud/database-migration/connection-profiles/update @@ -64,9 +64,9 @@ POSITIONAL ARGUMENTS FLAGS --ca-certificate=CA_CERTIFICATE x509 PEM-encoded certificate of the CA that signed the database - server's certificate. The replica will use this certificate to verify - it's connecting to the correct host. Database Migration Service - encrypts the value when storing it. + server's certificate. Database Migration Service will use this + certificate to verify it's connecting to the correct host. Database + Migration Service encrypts the value when storing it. --client-certificate=CLIENT_CERTIFICATE x509 PEM-encoded certificate that will be used by the replica to diff --git a/gcloud/dataproc/clusters/create b/gcloud/dataproc/clusters/create index b9c1bcdc6..178c47a63 100644 --- a/gcloud/dataproc/clusters/create +++ b/gcloud/dataproc/clusters/create @@ -37,8 +37,9 @@ SYNOPSIS [--secondary-worker-boot-disk-size=SECONDARY_WORKER_BOOT_DISK_SIZE] [--secondary-worker-boot-disk-type=SECONDARY_WORKER_BOOT_DISK_TYPE] [--secondary-worker-local-ssd-interface=SECONDARY_WORKER_LOCAL_SSD_INTERFACE] - [--shielded-integrity-monitoring] [--shielded-secure-boot] - [--shielded-vtpm] [--temp-bucket=TEMP_BUCKET] + [--secondary-worker-machine-types=type=MACHINE_TYPE[, + type=MACHINE_TYPE...][,rank=RANK]] [--shielded-integrity-monitoring] + [--shielded-secure-boot] [--shielded-vtpm] [--temp-bucket=TEMP_BUCKET] [--worker-accelerator=[type=TYPE,[count=COUNT],...]] [--worker-boot-disk-size=WORKER_BOOT_DISK_SIZE] [--worker-boot-disk-type=WORKER_BOOT_DISK_TYPE] @@ -380,6 +381,11 @@ FLAGS Interface to use to attach local SSDs to each secondary worker in a cluster. + --secondary-worker-machine-types=type=MACHINE_TYPE[,type=MACHINE_TYPE...][,rank=RANK] + Types of machines with optional rank for secondary workers to use. + Defaults to server-specified.eg. + --secondary-worker-machine-types="type=e2-standard-8,type=t2d-standard-8,rank=0" + --shielded-integrity-monitoring Enables monitoring and attestation of the boot integrity of the cluster's VMs. vTPM (virtual Trusted Platform Module) must also be diff --git a/gcloud/dataproc/workflow-templates/set-managed-cluster b/gcloud/dataproc/workflow-templates/set-managed-cluster index a96d1a3fc..1d56dbdcd 100644 --- a/gcloud/dataproc/workflow-templates/set-managed-cluster +++ b/gcloud/dataproc/workflow-templates/set-managed-cluster @@ -28,8 +28,9 @@ SYNOPSIS [--secondary-worker-boot-disk-size=SECONDARY_WORKER_BOOT_DISK_SIZE] [--secondary-worker-boot-disk-type=SECONDARY_WORKER_BOOT_DISK_TYPE] [--secondary-worker-local-ssd-interface=SECONDARY_WORKER_LOCAL_SSD_INTERFACE] - [--shielded-integrity-monitoring] [--shielded-secure-boot] - [--shielded-vtpm] [--temp-bucket=TEMP_BUCKET] + [--secondary-worker-machine-types=type=MACHINE_TYPE[, + type=MACHINE_TYPE...][,rank=RANK]] [--shielded-integrity-monitoring] + [--shielded-secure-boot] [--shielded-vtpm] [--temp-bucket=TEMP_BUCKET] [--worker-accelerator=[type=TYPE,[count=COUNT],...]] [--worker-boot-disk-size=WORKER_BOOT_DISK_SIZE] [--worker-boot-disk-type=WORKER_BOOT_DISK_TYPE] @@ -300,6 +301,11 @@ FLAGS Interface to use to attach local SSDs to each secondary worker in a cluster. + --secondary-worker-machine-types=type=MACHINE_TYPE[,type=MACHINE_TYPE...][,rank=RANK] + Types of machines with optional rank for secondary workers to use. + Defaults to server-specified.eg. + --secondary-worker-machine-types="type=e2-standard-8,type=t2d-standard-8,rank=0" + --shielded-integrity-monitoring Enables monitoring and attestation of the boot integrity of the cluster's VMs. vTPM (virtual Trusted Platform Module) must also be diff --git a/gcloud/datastream/streams/create b/gcloud/datastream/streams/create index d7a220a72..d9b6b982f 100644 --- a/gcloud/datastream/streams/create +++ b/gcloud/datastream/streams/create @@ -106,13 +106,79 @@ REQUIRED FLAGS At most one of these can be specified: --mysql-excluded-objects=MYSQL_EXCLUDED_OBJECTS - MySQL data source objects to avoid backfilling. + Path to a YAML (or JSON) file containing the MySQL data sources to + avoid backfilling. + + The JSON file is formatted as follows, with camelCase field naming: + + { + "mysqlDatabases": [ + { + "database":"sample_database", + "mysqlTables": [ + { + "table": "sample_table", + "mysqlColumns": [ + { + "column": "sample_column", + } + ] + } + ] + } + ] + } + } --oracle-excluded-objects=ORACLE_EXCLUDED_OBJECTS - Oracle data source objects to avoid backfilling. + Path to a YAML (or JSON) file containing the Oracle data sources to + avoid backfilling. + + The JSON file is formatted as follows, with camelCase field naming: + + { + "oracleSchemas": [ + { + "schema": "SAMPLE", + "oracleTables": [ + { + "table": "SAMPLE_TABLE", + "oracleColumns": [ + { + "column": "COL", + } + ] + } + ] + } + ] + } + } --postgresql-excluded-objects=POSTGRESQL_EXCLUDED_OBJECTS - PostgreSQL data source objects to avoid backfilling. + Path to a YAML (or JSON) file containing the PostgreSQL data + sources to avoid backfilling. + + The JSON file is formatted as follows, with camelCase field naming: + + { + "postgresqlSchemas": [ + { + "schema": "SAMPLE", + "postgresqlTables": [ + { + "table": "SAMPLE_TABLE", + "postgresqlColumns": [ + { + "column": "COL", + } + ] + } + ] + } + ] + } + } This must be specified. diff --git a/gcloud/datastream/streams/update b/gcloud/datastream/streams/update index 5b002c498..03cb23a22 100644 --- a/gcloud/datastream/streams/update +++ b/gcloud/datastream/streams/update @@ -108,13 +108,79 @@ FLAGS At most one of these can be specified: --mysql-excluded-objects=MYSQL_EXCLUDED_OBJECTS - MySQL data source objects to avoid backfilling. + Path to a YAML (or JSON) file containing the MySQL data sources to + avoid backfilling. + + The JSON file is formatted as follows, with camelCase field naming: + + { + "mysqlDatabases": [ + { + "database":"sample_database", + "mysqlTables": [ + { + "table": "sample_table", + "mysqlColumns": [ + { + "column": "sample_column", + } + ] + } + ] + } + ] + } + } --oracle-excluded-objects=ORACLE_EXCLUDED_OBJECTS - Oracle data source objects to avoid backfilling. + Path to a YAML (or JSON) file containing the Oracle data sources to + avoid backfilling. + + The JSON file is formatted as follows, with camelCase field naming: + + { + "oracleSchemas": [ + { + "schema": "SAMPLE", + "oracleTables": [ + { + "table": "SAMPLE_TABLE", + "oracleColumns": [ + { + "column": "COL", + } + ] + } + ] + } + ] + } + } --postgresql-excluded-objects=POSTGRESQL_EXCLUDED_OBJECTS - PostgreSQL data source objects to avoid backfilling. + Path to a YAML (or JSON) file containing the PostgreSQL data + sources to avoid backfilling. + + The JSON file is formatted as follows, with camelCase field naming: + + { + "postgresqlSchemas": [ + { + "schema": "SAMPLE", + "postgresqlTables": [ + { + "table": "SAMPLE_TABLE", + "postgresqlColumns": [ + { + "column": "COL", + } + ] + } + ] + } + ] + } + } At most one of these can be specified: diff --git a/gcloud/functions/deploy b/gcloud/functions/deploy index c4adf6ab7..03554d738 100644 --- a/gcloud/functions/deploy +++ b/gcloud/functions/deploy @@ -610,8 +610,8 @@ FLAGS The provided attribute/value pair will be used with the match-path-pattern operator to configure the trigger, see https://cloud.google.com/eventarc/docs/reference/rest/v1/projects.locations.triggers#eventfilter - and http://cloud/eventarc/docs/path-patterns for more details about - on how to construct path patterns. + and https://cloud.google.com/eventarc/docs/path-patterns for more + details about on how to construct path patterns. For example, to filter on events for Compute Engine VMs in a given zone: diff --git a/gcloud/iam/workforce-pools/providers/create-oidc b/gcloud/iam/workforce-pools/providers/create-oidc index 133756ec7..3a8420886 100644 --- a/gcloud/iam/workforce-pools/providers/create-oidc +++ b/gcloud/iam/workforce-pools/providers/create-oidc @@ -12,7 +12,8 @@ SYNOPSIS : --web-sso-additional-scopes=[WEB_SSO_ADDITIONAL_SCOPES,...]) [--async] [--attribute-condition=ATTRIBUTE_CONDITION] [--client-secret-value=CLIENT_SECRET_VALUE] [--description=DESCRIPTION] - [--disabled] [--display-name=DISPLAY_NAME] [GCLOUD_WIDE_FLAG ...] + [--disabled] [--display-name=DISPLAY_NAME] + [--jwk-json-path=JWK_JSON_PATH] [GCLOUD_WIDE_FLAG ...] DESCRIPTION Create a new OIDC workforce pool provider. @@ -33,7 +34,8 @@ EXAMPLES --issuer-uri="https://test-idp.com" \ --web-sso-response-type="code" \ --web-sso-assertion-claims-behavior="merge-user-info-over-id-tok\ - en-claims" --web-sso-additional-scopes="groups,photos" + en-claims" --web-sso-additional-scopes="groups,photos" \ + --jwk-json-path="path/to/jwk.json" POSITIONAL ARGUMENTS Workforce pool provider resource - The workforce pool provider to create. @@ -244,6 +246,26 @@ OPTIONAL FLAGS A display name for the workforce pool provider. Cannot exceed 32 characters in length. + --jwk-json-path=JWK_JSON_PATH + Optional file containing JSON Web Key (JWK) public keys. The file + format must follow JWK specifications + (https://www.rfc-editor.org/rfc/rfc7517#section-4). Example file + format: { + "keys": [ + { + "kty": "RSA/EC", + "alg": "", + "use": "sig", + "kid": "", + "n": "", + "e": "", + "x": "", + "y": "", + "crv": "" + } + ] + } + 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/iam/workforce-pools/providers/update-oidc b/gcloud/iam/workforce-pools/providers/update-oidc index 4927ef66d..596bc671f 100644 --- a/gcloud/iam/workforce-pools/providers/update-oidc +++ b/gcloud/iam/workforce-pools/providers/update-oidc @@ -8,7 +8,7 @@ SYNOPSIS [--async] [--attribute-condition=ATTRIBUTE_CONDITION] [--attribute-mapping=[KEY=VALUE,...]] [--client-id=CLIENT_ID] [--description=DESCRIPTION] [--disabled] [--display-name=DISPLAY_NAME] - [--issuer-uri=ISSUER_URI] + [--issuer-uri=ISSUER_URI] [--jwk-json-path=JWK_JSON_PATH] [--web-sso-additional-scopes=[WEB_SSO_ADDITIONAL_SCOPES,...]] [--web-sso-assertion-claims-behavior=WEB_SSO_ASSERTION_CLAIMS_BEHAVIOR] [--web-sso-response-type=WEB_SSO_RESPONSE_TYPE] @@ -34,7 +34,8 @@ EXAMPLES --issuer-uri="https://test-idp.com" \ --web-sso-response-type="code" \ --web-sso-assertion-claims-behavior="merge-user-info-over-id-tok\ - en-claims" --web-sso-additional-scopes="groups,photos" + en-claims" --web-sso-additional-scopes="groups,photos" \ + --jwk-json-path="path/to/jwk.json" POSITIONAL ARGUMENTS Workforce pool provider resource - The workforce pool provider to update. @@ -195,6 +196,26 @@ FLAGS --issuer-uri=ISSUER_URI The OIDC issuer URI. Must be a valid URI using the 'https' scheme. + --jwk-json-path=JWK_JSON_PATH + Optional file containing JSON Web Key (JWK) public keys. The file + format must follow JWK specifications + (https://www.rfc-editor.org/rfc/rfc7517#section-4). Example file + format: { + "keys": [ + { + "kty": "RSA/EC", + "alg": "", + "use": "sig", + "kid": "", + "n": "", + "e": "", + "x": "", + "y": "", + "crv": "" + } + ] + } + --web-sso-additional-scopes=[WEB_SSO_ADDITIONAL_SCOPES,...] Additional scopes to request for the OIDC authentication on top of scopes requested by default. By default, the openid, profile and email diff --git a/gcloud/looker/instances/create b/gcloud/looker/instances/create index 9f09a8b7d..5e46537d3 100644 --- a/gcloud/looker/instances/create +++ b/gcloud/looker/instances/create @@ -213,7 +213,7 @@ GCLOUD WIDE FLAGS API REFERENCE This command uses the looker/v1 API. The full documentation for this API - can be found at: https://looker.com/ + can be found at: https://cloud.google.com/looker/docs/reference/rest/ NOTES This variant is also available: diff --git a/gcloud/looker/instances/delete b/gcloud/looker/instances/delete index 926279014..311617943 100644 --- a/gcloud/looker/instances/delete +++ b/gcloud/looker/instances/delete @@ -70,7 +70,7 @@ GCLOUD WIDE FLAGS API REFERENCE This command uses the looker/v1 API. The full documentation for this API - can be found at: https://looker.com/ + can be found at: https://cloud.google.com/looker/docs/reference/rest/ NOTES This variant is also available: diff --git a/gcloud/looker/instances/describe b/gcloud/looker/instances/describe index 669a2280c..2dd43f20e 100644 --- a/gcloud/looker/instances/describe +++ b/gcloud/looker/instances/describe @@ -65,7 +65,7 @@ GCLOUD WIDE FLAGS API REFERENCE This command uses the looker/v1 API. The full documentation for this API - can be found at: https://looker.com/ + can be found at: https://cloud.google.com/looker/docs/reference/rest/ NOTES This variant is also available: diff --git a/gcloud/looker/instances/list b/gcloud/looker/instances/list index 0d07a28d9..43d5e5e9b 100644 --- a/gcloud/looker/instances/list +++ b/gcloud/looker/instances/list @@ -77,7 +77,7 @@ GCLOUD WIDE FLAGS API REFERENCE This command uses the looker/v1 API. The full documentation for this API - can be found at: https://looker.com/ + can be found at: https://cloud.google.com/looker/docs/reference/rest/ NOTES This variant is also available: diff --git a/gcloud/looker/instances/restart b/gcloud/looker/instances/restart index 9715a58f5..9ec2d8a62 100644 --- a/gcloud/looker/instances/restart +++ b/gcloud/looker/instances/restart @@ -67,7 +67,7 @@ GCLOUD WIDE FLAGS API REFERENCE This command uses the looker/v1 API. The full documentation for this API - can be found at: https://looker.com/ + can be found at: https://cloud.google.com/looker/docs/reference/rest/ NOTES This variant is also available: diff --git a/gcloud/looker/instances/update b/gcloud/looker/instances/update index 0a6c0a072..9b15ea1d6 100644 --- a/gcloud/looker/instances/update +++ b/gcloud/looker/instances/update @@ -185,7 +185,7 @@ GCLOUD WIDE FLAGS API REFERENCE This command uses the looker/v1 API. The full documentation for this API - can be found at: https://looker.com/ + can be found at: https://cloud.google.com/looker/docs/reference/rest/ NOTES This variant is also available: diff --git a/gcloud/looker/operations/cancel b/gcloud/looker/operations/cancel index 5d5fbbd26..817c767a5 100644 --- a/gcloud/looker/operations/cancel +++ b/gcloud/looker/operations/cancel @@ -58,7 +58,7 @@ GCLOUD WIDE FLAGS API REFERENCE This command uses the looker/v1 API. The full documentation for this API - can be found at: https://looker.com/ + can be found at: https://cloud.google.com/looker/docs/reference/rest/ NOTES This variant is also available: diff --git a/gcloud/looker/operations/describe b/gcloud/looker/operations/describe index a409068cf..5fa1e9158 100644 --- a/gcloud/looker/operations/describe +++ b/gcloud/looker/operations/describe @@ -63,7 +63,7 @@ GCLOUD WIDE FLAGS API REFERENCE This command uses the looker/v1 API. The full documentation for this API - can be found at: https://looker.com/ + can be found at: https://cloud.google.com/looker/docs/reference/rest/ NOTES This variant is also available: diff --git a/gcloud/looker/operations/list b/gcloud/looker/operations/list index 9b38c53cd..773702482 100644 --- a/gcloud/looker/operations/list +++ b/gcloud/looker/operations/list @@ -77,7 +77,7 @@ GCLOUD WIDE FLAGS API REFERENCE This command uses the looker/v1 API. The full documentation for this API - can be found at: https://looker.com/ + can be found at: https://cloud.google.com/looker/docs/reference/rest/ NOTES This variant is also available: diff --git a/gcloud/memcache/instances/create b/gcloud/memcache/instances/create index 50d0a3d52..14c33aaf1 100644 --- a/gcloud/memcache/instances/create +++ b/gcloud/memcache/instances/create @@ -107,10 +107,12 @@ OPTIONAL FLAGS --memcached-version=MEMCACHED_VERSION Optional major version of Memcached software to use with the instance. If not provided, default of "1.5" will be used. MEMCACHED_VERSION must - be (only one value is supported): + be one of: 1.5 Memcached major version 1.5 + 1.6.15 + Memcached version 1.6.15 --parameters=KEY=VALUE User defined parameters to apply to the memcached process on each node. diff --git a/gcloud/memcache/instances/help b/gcloud/memcache/instances/help index b3e07c64d..0a1a0f4ac 100644 --- a/gcloud/memcache/instances/help +++ b/gcloud/memcache/instances/help @@ -36,6 +36,9 @@ COMMANDS update Update a Memorystore Memcached instance. + upgrade + Upgrade memcache instance to a newer memcached version. + NOTES These variants are also available: diff --git a/gcloud/memcache/instances/upgrade b/gcloud/memcache/instances/upgrade new file mode 100644 index 000000000..0b8c17f74 --- /dev/null +++ b/gcloud/memcache/instances/upgrade @@ -0,0 +1,83 @@ +NAME + gcloud memcache instances upgrade - upgrade memcache instance to a newer + memcached version + +SYNOPSIS + gcloud memcache instances upgrade (INSTANCE : --region=REGION) + --memcached-version=MEMCACHED_VERSION [--async] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Upgrade memcahce instance to a newer memcached version. + +EXAMPLES + To upgrade memcache version of an instance with the name + 'my-memcache-instance' in region 'us-central-1' to MEMCACHE_1_6_15 + + $ gcloud memcache instances upgrade my-memcache-instance \ + --region=us-central1 --memcached-version="1.6.15" + +POSITIONAL ARGUMENTS + Instance resource - Arguments and flags that specify the Memorystore for + Memcached instance you want to upgrade. The arguments in this group can be + used to specify the attributes of this resource. (NOTE) Some attributes + are not given arguments in this group but can be set in other ways. + + To set the project attribute: + ◆ provide the argument instance on the command line with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + INSTANCE + ID of the instance or fully qualified identifier for the instance. + + To set the instance attribute: + ▸ provide the argument instance on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --region=REGION + The name of the Memcached region of the instance. Overrides the + default memcache/region property value for this command invocation. + + To set the region attribute: + ▸ provide the argument instance on the command line with a fully + specified name; + ▸ provide the argument --region on the command line; + ▸ set the property memcache/region. + +REQUIRED FLAGS + --memcached-version=MEMCACHED_VERSION + Memcached engine version to which instance should be upgraded to. + MEMCACHED_VERSION must be (only one value is supported): + + 1.6.15 + Memcached engine version 1.6.15 + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the memcache/v1 API. The full documentation for this API + can be found at: https://cloud.google.com/memorystore/ + +NOTES + These variants are also available: + + $ gcloud alpha memcache instances upgrade + + $ gcloud beta memcache instances upgrade + diff --git a/gcloud/network-connectivity/hubs/accept-spoke b/gcloud/network-connectivity/hubs/accept-spoke new file mode 100644 index 000000000..094fd6f95 --- /dev/null +++ b/gcloud/network-connectivity/hubs/accept-spoke @@ -0,0 +1,59 @@ +NAME + gcloud network-connectivity hubs accept-spoke - accept a spoke into a hub + +SYNOPSIS + gcloud network-connectivity hubs accept-spoke HUB --spoke=SPOKE [--async] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Accept a proposed or previously rejected VPC spoke. By accepting a spoke, + you permit connectivity between the associated VPC network and other VPC + networks that are attached to the same hub. + +EXAMPLES + To accept a spoke named my-spoke into a hub named my-hub, run: + + $ gcloud network-connectivity hubs accept-spoke my-hub \ + --spoke="https://www.googleapis.com/networkconnectivity/v1/proje\ + cts/spoke-project/locations/global/hubs/my-spoke" + +POSITIONAL ARGUMENTS + Hub resource - Name of the hub to accept the spoke into. 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 hub 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. + + HUB + ID of the hub or fully qualified identifier for the hub. + + To set the hub attribute: + ▸ provide the argument hub on the command line. + +REQUIRED FLAGS + --spoke=SPOKE + URI of the spoke to accept + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the networkconnectivity/v1 API. The full documentation + for this API can be found at: + https://cloud.google.com/network-connectivity/docs/reference/networkconnectivity/rest diff --git a/gcloud/network-connectivity/hubs/help b/gcloud/network-connectivity/hubs/help index 31d273a5e..c040c6914 100644 --- a/gcloud/network-connectivity/hubs/help +++ b/gcloud/network-connectivity/hubs/help @@ -24,6 +24,9 @@ GROUPS COMMANDS COMMAND is one of the following: + accept-spoke + Accept a spoke into a hub. + add-iam-policy-binding Add an IAM policy binding to the IAM policy of a hub resource. @@ -45,6 +48,9 @@ COMMANDS list-spokes List hub spokes. + reject-spoke + Reject a spoke from a hub. + remove-iam-policy-binding Remove an IAM policy binding from the IAM policy of a hub resource. diff --git a/gcloud/network-connectivity/hubs/reject-spoke b/gcloud/network-connectivity/hubs/reject-spoke new file mode 100644 index 000000000..4d65ae170 --- /dev/null +++ b/gcloud/network-connectivity/hubs/reject-spoke @@ -0,0 +1,64 @@ +NAME + gcloud network-connectivity hubs reject-spoke - reject a spoke from a hub + +SYNOPSIS + gcloud network-connectivity hubs reject-spoke HUB --spoke=SPOKE [--async] + [--details=DETAILS] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Reject a VPC spoke. By rejecting a spoke, you prevent or remove + connectivity between the associated VPC network and any other VPC networks + that are attached to the same hub. + +EXAMPLES + To reject a spoke named my-spoke from a hub named my-hub with reason + my-reason, run: + + $ gcloud network-connectivity hubs reject-spoke my-hub \ + --spoke="https://www.googleapis.com/networkconnectivity/v1/proje\ + cts/spoke-project/locations/global/hubs/my-spoke" \ + --details=my-reason + +POSITIONAL ARGUMENTS + Hub resource - Name of the hub to reject the spoke from. 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 hub 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. + + HUB + ID of the hub or fully qualified identifier for the hub. + + To set the hub attribute: + ▸ provide the argument hub on the command line. + +REQUIRED FLAGS + --spoke=SPOKE + URI of the spoke to reject + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --details=DETAILS + Additional details behind the rejection + +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 networkconnectivity/v1 API. The full documentation + for this API can be found at: + https://cloud.google.com/network-connectivity/docs/reference/networkconnectivity/rest diff --git a/gcloud/network-connectivity/spokes/accept b/gcloud/network-connectivity/spokes/accept index 76e80ba83..27e0fc2da 100644 --- a/gcloud/network-connectivity/spokes/accept +++ b/gcloud/network-connectivity/spokes/accept @@ -6,6 +6,11 @@ SYNOPSIS [GCLOUD_WIDE_FLAG ...] DESCRIPTION + (DEPRECATED) Accept a spoke. + + This command is deprecated. Please use gcloud network-connectivity hubs + accept-spoke instead. + Accept a proposed or previously rejected VPC spoke. By accepting a spoke, you permit connectivity between the associated VPC network and other VPC networks that are attached to the same hub. diff --git a/gcloud/network-connectivity/spokes/help b/gcloud/network-connectivity/spokes/help index 2471bd71e..b57fc60da 100644 --- a/gcloud/network-connectivity/spokes/help +++ b/gcloud/network-connectivity/spokes/help @@ -32,7 +32,7 @@ COMMANDS COMMAND is one of the following: accept - Accept a spoke. + (DEPRECATED) Accept a spoke. delete Delete a spoke. @@ -44,7 +44,7 @@ COMMANDS List spokes. reject - Reject a spoke. + (DEPRECATED) Reject a spoke. NOTES This variant is also available: diff --git a/gcloud/network-connectivity/spokes/reject b/gcloud/network-connectivity/spokes/reject index 7b1b077d0..2ac611cc7 100644 --- a/gcloud/network-connectivity/spokes/reject +++ b/gcloud/network-connectivity/spokes/reject @@ -6,6 +6,11 @@ SYNOPSIS [--details=DETAILS] [--global] [GCLOUD_WIDE_FLAG ...] DESCRIPTION + (DEPRECATED) Reject a spoke. + + This command is deprecated. Please use gcloud network-connectivity hubs + reject-spoke instead. + Reject a VPC spoke. By rejecting a spoke, you prevent or remove connectivity between the associated VPC network and any other VPC networks that are attached to the same hub. diff --git a/gcloud/secrets/delete b/gcloud/secrets/delete index 029f3e032..39b61b678 100644 --- a/gcloud/secrets/delete +++ b/gcloud/secrets/delete @@ -6,7 +6,7 @@ SYNOPSIS DESCRIPTION Delete a secret and destroy all secret versions. This action is - irreversable. If the given secret does not exist, this command will + irreversible. If the given secret does not exist, this command will succeed, but the operation will be a no-op. EXAMPLES diff --git a/gcloud/services/list b/gcloud/services/list index f415e3316..e8aec67ad 100644 --- a/gcloud/services/list +++ b/gcloud/services/list @@ -13,14 +13,26 @@ DESCRIPTION --enabled is the default. EXAMPLES - To list the services the current project has enabled for consumption, run: + To list the services for the current project has enabled for consumption, + run: $ gcloud services list --enabled - To list the services the current project can enable for consumption, run: + To list the services for the current project can enable for consumption, + run: $ gcloud services list --available + To list the services for project my-project has enabled for consumption, + run: + + $ gcloud services list --enabled --project=my-project + + To list the services the project my-project can enable for consumption, + run: + + $ gcloud services list --available --project=my-project + FLAGS At most one of these can be specified: @@ -65,9 +77,7 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. NOTES - These variants are also available: - - $ gcloud alpha services list + This variant is also available: $ gcloud beta services list