From ed5fe34b64db704a932b6bf5b8629e4e7a5c2f66 Mon Sep 17 00:00:00 2001 From: Automated Date: Wed, 21 Aug 2024 09:39:51 +0000 Subject: [PATCH] gcloud: Wed Aug 21 09:39:51 UTC 2024 --- gcloud/_version | 8 +- gcloud/ai/endpoints/deploy-model | 15 +- gcloud/alpha/ai/endpoints/deploy-model | 16 +- .../blockchain-validator-configs/update | 4 +- .../firewall-policies/mirroring-rules/create | 4 +- .../firewall-policies/mirroring-rules/update | 4 +- .../alpha/compute/instance-templates/create | 2 +- .../instance-templates/create-with-container | 2 +- gcloud/alpha/compute/instances/bulk/create | 2 +- gcloud/alpha/compute/instances/create | 2 +- .../compute/instances/create-with-container | 2 +- .../mirroring-rules/create | 3 +- .../mirroring-rules/update | 3 +- gcloud/alpha/compute/networks/subnets/create | 2 + gcloud/alpha/compute/queued-resources/create | 2 +- gcloud/alpha/compute/reservations/create | 13 +- gcloud/alpha/compute/reservations/update | 11 + .../compute/resource-policies/update/help | 3 + .../update/instance-schedule | 91 +++++++ gcloud/alpha/compute/routers/nats/create | 68 ++++-- gcloud/alpha/compute/routers/nats/update | 71 ++++-- .../alpha/container/attached/clusters/import | 2 + .../container/attached/clusters/register | 2 + gcloud/alpha/container/clusters/create | 34 +-- gcloud/alpha/container/clusters/update | 20 +- .../container/fleet/config-management/help | 8 +- .../container/hub/config-management/help | 8 +- gcloud/alpha/container/node-pools/create | 8 +- gcloud/alpha/container/node-pools/update | 9 + gcloud/alpha/dataplex/entries/search | 2 +- gcloud/alpha/dataproc/clusters/create | 8 +- .../workflow-templates/set-managed-cluster | 6 +- .../developer-connect/connections/update | 4 +- gcloud/alpha/firestore/bulk-delete | 72 ++++++ gcloud/alpha/firestore/databases/restore | 15 +- gcloud/alpha/firestore/help | 5 + .../alpha/firestore/indexes/composite/create | 12 +- gcloud/alpha/managed-kafka/clusters/create | 12 +- gcloud/alpha/managed-kafka/clusters/delete | 12 +- gcloud/alpha/managed-kafka/clusters/describe | 12 +- gcloud/alpha/managed-kafka/clusters/help | 16 +- gcloud/alpha/managed-kafka/clusters/list | 4 +- gcloud/alpha/managed-kafka/clusters/update | 12 +- .../managed-kafka/consumer-groups/delete | 12 +- .../managed-kafka/consumer-groups/describe | 12 +- .../alpha/managed-kafka/consumer-groups/help | 16 +- .../alpha/managed-kafka/consumer-groups/list | 16 +- .../managed-kafka/consumer-groups/update | 12 +- gcloud/alpha/managed-kafka/help | 14 +- gcloud/alpha/managed-kafka/topics/create | 12 +- gcloud/alpha/managed-kafka/topics/delete | 12 +- gcloud/alpha/managed-kafka/topics/describe | 12 +- gcloud/alpha/managed-kafka/topics/help | 17 +- gcloud/alpha/managed-kafka/topics/list | 15 +- gcloud/alpha/managed-kafka/topics/update | 12 +- gcloud/alpha/network-security/help | 5 +- .../mirroring-deployments/help | 2 +- .../create | 172 +++++++++++++ .../delete | 91 +++++++ .../describe | 77 ++++++ .../help | 46 ++++ .../list | 101 ++++++++ .../update | 127 ++++++++++ gcloud/alpha/recommender/insights/help | 2 +- gcloud/alpha/recommender/insights/list | 41 +++- .../alpha/recommender/insights/mark-dismissed | 3 +- gcloud/alpha/recommender/recommendations/list | 37 ++- gcloud/alpha/run/deploy | 107 +++++++- gcloud/alpha/run/services/update | 16 +- gcloud/alpha/storage/diagnose | 171 +++++++++++++ gcloud/alpha/storage/help | 3 + gcloud/alpha/storage/objects/update | 11 +- gcloud/beta/ai/endpoints/deploy-model | 16 +- gcloud/beta/colab-enterprise/help | 23 ++ .../colab-enterprise/runtime-templates/create | 229 ++++++++++++++++++ .../colab-enterprise/runtime-templates/delete | 68 ++++++ .../runtime-templates/describe | 63 +++++ .../colab-enterprise/runtime-templates/help | 35 +++ .../colab-enterprise/runtime-templates/list | 83 +++++++ .../firewall-policies/mirroring-rules/create | 4 +- .../firewall-policies/mirroring-rules/update | 4 +- gcloud/beta/compute/instance-templates/create | 2 +- .../instance-templates/create-with-container | 2 +- gcloud/beta/compute/instances/bulk/create | 2 +- gcloud/beta/compute/instances/create | 2 +- .../compute/instances/create-with-container | 2 +- .../mirroring-rules/create | 3 +- .../mirroring-rules/update | 3 +- gcloud/beta/compute/reservations/create | 13 +- gcloud/beta/compute/reservations/update | 11 + .../compute/resource-policies/update/help | 3 + .../update/instance-schedule | 89 +++++++ gcloud/beta/container/clusters/create | 34 +-- gcloud/beta/container/clusters/update | 20 +- .../container/fleet/config-management/help | 8 +- .../beta/container/hub/config-management/help | 8 +- gcloud/beta/container/node-pools/create | 8 +- gcloud/beta/container/node-pools/update | 9 + gcloud/beta/dataproc/clusters/create | 8 +- .../workflow-templates/set-managed-cluster | 6 +- gcloud/beta/firestore/bulk-delete | 70 ++++++ gcloud/beta/firestore/help | 5 + .../beta/firestore/indexes/composite/create | 50 ++-- gcloud/beta/iam/policy-bindings/create | 57 +++-- gcloud/beta/iam/policy-bindings/delete | 21 +- gcloud/beta/iam/policy-bindings/describe | 15 +- gcloud/beta/iam/policy-bindings/list | 16 +- .../search-target-policy-bindings | 33 +-- gcloud/beta/iam/policy-bindings/update | 27 ++- .../principal-access-boundary-policies/create | 31 ++- .../principal-access-boundary-policies/delete | 6 +- .../principal-access-boundary-policies/update | 63 ++--- gcloud/beta/managed-kafka/clusters/create | 12 +- gcloud/beta/managed-kafka/clusters/delete | 12 +- gcloud/beta/managed-kafka/clusters/describe | 12 +- gcloud/beta/managed-kafka/clusters/help | 17 +- gcloud/beta/managed-kafka/clusters/list | 4 +- gcloud/beta/managed-kafka/clusters/update | 12 +- .../beta/managed-kafka/consumer-groups/delete | 12 +- .../managed-kafka/consumer-groups/describe | 12 +- .../beta/managed-kafka/consumer-groups/help | 16 +- .../beta/managed-kafka/consumer-groups/list | 12 +- .../beta/managed-kafka/consumer-groups/update | 12 +- gcloud/beta/managed-kafka/help | 14 +- gcloud/beta/managed-kafka/topics/create | 12 +- gcloud/beta/managed-kafka/topics/delete | 12 +- gcloud/beta/managed-kafka/topics/describe | 12 +- gcloud/beta/managed-kafka/topics/help | 17 +- gcloud/beta/managed-kafka/topics/list | 14 +- gcloud/beta/managed-kafka/topics/update | 12 +- gcloud/beta/network-security/help | 5 +- .../mirroring-deployments/help | 2 +- .../create | 170 +++++++++++++ .../delete | 89 +++++++ .../describe | 75 ++++++ .../help | 44 ++++ .../list | 99 ++++++++ .../update | 125 ++++++++++ gcloud/beta/run/deploy | 101 +++++++- gcloud/beta/services/disable | 7 +- gcloud/compute/instance-templates/create | 2 +- gcloud/compute/instances/bulk/create | 2 +- gcloud/compute/instances/create | 2 +- .../compute/instances/create-with-container | 2 +- gcloud/compute/resource-policies/update/help | 3 + .../update/instance-schedule | 87 +++++++ gcloud/container/attached/clusters/import | 1 + gcloud/container/attached/clusters/register | 1 + gcloud/container/clusters/create | 61 +++-- gcloud/container/clusters/create-auto | 22 +- gcloud/container/clusters/update | 34 ++- gcloud/container/node-pools/create | 16 +- gcloud/container/node-pools/update | 9 + gcloud/dataplex/entries/search | 2 +- gcloud/dataproc/clusters/create | 8 +- .../workflow-templates/set-managed-cluster | 6 +- gcloud/firestore/help | 2 + gcloud/firestore/indexes/composite/create | 50 ++-- gcloud/looker/instances/create | 15 ++ gcloud/looker/instances/update | 28 +++ gcloud/services/disable | 7 +- gcloud/storage/objects/update | 11 +- gcloud/workbench/instances/create | 7 +- 163 files changed, 3541 insertions(+), 717 deletions(-) create mode 100644 gcloud/alpha/compute/resource-policies/update/instance-schedule create mode 100644 gcloud/alpha/firestore/bulk-delete create mode 100644 gcloud/alpha/network-security/mirroring-endpoint-group-associations/create create mode 100644 gcloud/alpha/network-security/mirroring-endpoint-group-associations/delete create mode 100644 gcloud/alpha/network-security/mirroring-endpoint-group-associations/describe create mode 100644 gcloud/alpha/network-security/mirroring-endpoint-group-associations/help create mode 100644 gcloud/alpha/network-security/mirroring-endpoint-group-associations/list create mode 100644 gcloud/alpha/network-security/mirroring-endpoint-group-associations/update create mode 100644 gcloud/alpha/storage/diagnose create mode 100644 gcloud/beta/colab-enterprise/help create mode 100644 gcloud/beta/colab-enterprise/runtime-templates/create create mode 100644 gcloud/beta/colab-enterprise/runtime-templates/delete create mode 100644 gcloud/beta/colab-enterprise/runtime-templates/describe create mode 100644 gcloud/beta/colab-enterprise/runtime-templates/help create mode 100644 gcloud/beta/colab-enterprise/runtime-templates/list create mode 100644 gcloud/beta/compute/resource-policies/update/instance-schedule create mode 100644 gcloud/beta/firestore/bulk-delete create mode 100644 gcloud/beta/network-security/mirroring-endpoint-group-associations/create create mode 100644 gcloud/beta/network-security/mirroring-endpoint-group-associations/delete create mode 100644 gcloud/beta/network-security/mirroring-endpoint-group-associations/describe create mode 100644 gcloud/beta/network-security/mirroring-endpoint-group-associations/help create mode 100644 gcloud/beta/network-security/mirroring-endpoint-group-associations/list create mode 100644 gcloud/beta/network-security/mirroring-endpoint-group-associations/update create mode 100644 gcloud/compute/resource-policies/update/instance-schedule diff --git a/gcloud/_version b/gcloud/_version index 47e351f87..a18bcb4ff 100644 --- a/gcloud/_version +++ b/gcloud/_version @@ -1,8 +1,8 @@ -Google Cloud SDK 488.0.0 -alpha 2024.08.09 -beta 2024.08.09 +Google Cloud SDK 489.0.0 +alpha 2024.08.16 +beta 2024.08.16 bq 2.1.8 bundled-python3-unix 3.11.9 -core 2024.08.09 +core 2024.08.16 gcloud-crc32c 1.0.0 gsutil 5.30 diff --git a/gcloud/ai/endpoints/deploy-model b/gcloud/ai/endpoints/deploy-model index bec854795..b37333362 100644 --- a/gcloud/ai/endpoints/deploy-model +++ b/gcloud/ai/endpoints/deploy-model @@ -11,7 +11,9 @@ SYNOPSIS [--enable-access-logging] [--machine-type=MACHINE_TYPE] [--max-replica-count=MAX_REPLICA_COUNT] [--min-replica-count=MIN_REPLICA_COUNT] - [--service-account=SERVICE_ACCOUNT] + [--reservation-affinity=[key=KEY], + [reservation-affinity-type=RESERVATION-AFFINITY-TYPE], + [values=VALUES]] [--service-account=SERVICE_ACCOUNT] [--spot] [--traffic-split=[DEPLOYED_MODEL_ID=VALUE,...]] [GCLOUD_WIDE_FLAG ...] EXAMPLES @@ -129,12 +131,23 @@ OPTIONAL FLAGS If not specified and the uploaded models use dedicated resources, the default value is 1. + --reservation-affinity=[key=KEY],[reservation-affinity-type=RESERVATION-AFFINITY-TYPE],[values=VALUES] + A ReservationAffinity can be used to configure a Vertex AI resource + (e.g., a DeployedModel) to draw its Compute Engine resources from a + Shared Reservation, or exclusively from on-demand capacity. + --service-account=SERVICE_ACCOUNT Service account that the deployed model's container runs as. Specify the email address of the service account. If this service account is not specified, the container runs as a service account that doesn't have access to the resource project. + --spot + If true, online prediction access logs are sent to Cloud Logging. + + These logs are standard server access logs, containing information like + timestamp and latency for each prediction request. + --traffic-split=[DEPLOYED_MODEL_ID=VALUE,...] List of pairs of deployed model id and value to set as traffic split. diff --git a/gcloud/alpha/ai/endpoints/deploy-model b/gcloud/alpha/ai/endpoints/deploy-model index 52765c3e3..10cc37cb4 100644 --- a/gcloud/alpha/ai/endpoints/deploy-model +++ b/gcloud/alpha/ai/endpoints/deploy-model @@ -11,7 +11,10 @@ SYNOPSIS [--enable-container-logging] [--machine-type=MACHINE_TYPE] [--max-replica-count=MAX_REPLICA_COUNT] [--min-replica-count=MIN_REPLICA_COUNT] - [--service-account=SERVICE_ACCOUNT] [--tpu-topology=TPU_TOPOLOGY] + [--reservation-affinity=[key=KEY], + [reservation-affinity-type=RESERVATION-AFFINITY-TYPE], + [values=VALUES]] [--service-account=SERVICE_ACCOUNT] [--spot] + [--tpu-topology=TPU_TOPOLOGY] [--traffic-split=[DEPLOYED_MODEL_ID=VALUE,...]] [--shared-resources=SHARED_RESOURCES : --shared-resources-region=SHARED_RESOURCES_REGION] @@ -130,12 +133,23 @@ OPTIONAL FLAGS If not specified and the uploaded models use dedicated resources, the default value is 1. + --reservation-affinity=[key=KEY],[reservation-affinity-type=RESERVATION-AFFINITY-TYPE],[values=VALUES] + A ReservationAffinity can be used to configure a Vertex AI resource + (e.g., a DeployedModel) to draw its Compute Engine resources from a + Shared Reservation, or exclusively from on-demand capacity. + --service-account=SERVICE_ACCOUNT Service account that the deployed model's container runs as. Specify the email address of the service account. If this service account is not specified, the container runs as a service account that doesn't have access to the resource project. + --spot + If true, online prediction access logs are sent to Cloud Logging. + + These logs are standard server access logs, containing information like + timestamp and latency for each prediction request. + --tpu-topology=TPU_TOPOLOGY CloudTPU topology to use for this deployment. Required for multihost CloudTPU deployments: diff --git a/gcloud/alpha/blockchain-validator/blockchain-validator-configs/update b/gcloud/alpha/blockchain-validator/blockchain-validator-configs/update index 845f2a7c0..ee0bcf2a8 100644 --- a/gcloud/alpha/blockchain-validator/blockchain-validator-configs/update +++ b/gcloud/alpha/blockchain-validator/blockchain-validator-configs/update @@ -103,7 +103,7 @@ FLAGS At most one of these can be specified: --labels=[LABELS,...] - Set labels to new value. Labels as key value pairs + Set labels to new value. Labels as key value pairs. KEY Keys must start with a lowercase character and contain only @@ -126,7 +126,7 @@ FLAGS --labels=path_to_file.(yaml|json) --update-labels=[UPDATE_LABELS,...] - Update labels value or add key value pair. Labels as key value pairs + Update labels value or add key value pair. Labels as key value pairs. KEY Keys must start with a lowercase character and contain only diff --git a/gcloud/alpha/compute/firewall-policies/mirroring-rules/create b/gcloud/alpha/compute/firewall-policies/mirroring-rules/create index c015fe4a0..642ab2a11 100644 --- a/gcloud/alpha/compute/firewall-policies/mirroring-rules/create +++ b/gcloud/alpha/compute/firewall-policies/mirroring-rules/create @@ -63,8 +63,8 @@ OPTIONAL FLAGS set if FIREWALL_POLICY is short name. --security-profile-group=SECURITY_PROFILE_GROUP - An org-based security profile group to be used with - apply_security_profile_group action. Allowed formats are: a) + An org-based security profile group to be used with mirror action. + Allowed formats are: a) http(s):////organizations//locations/global/securityProfileGroups/ b) (//)/organizations//locations/global/securityProfileGroups/ diff --git a/gcloud/alpha/compute/firewall-policies/mirroring-rules/update b/gcloud/alpha/compute/firewall-policies/mirroring-rules/update index 6efdbb78d..81336103b 100644 --- a/gcloud/alpha/compute/firewall-policies/mirroring-rules/update +++ b/gcloud/alpha/compute/firewall-policies/mirroring-rules/update @@ -66,8 +66,8 @@ OPTIONAL FLAGS set if FIREWALL_POLICY is short name. --security-profile-group=SECURITY_PROFILE_GROUP - An org-based security profile group to be used with - apply_security_profile_group action. Allowed formats are: a) + An org-based security profile group to be used with mirror action. + Allowed formats are: a) http(s):////organizations//locations/global/securityProfileGroups/ b) (//)/organizations//locations/global/securityProfileGroups/ diff --git a/gcloud/alpha/compute/instance-templates/create b/gcloud/alpha/compute/instance-templates/create index b041adfc6..2665fe0a4 100644 --- a/gcloud/alpha/compute/instance-templates/create +++ b/gcloud/alpha/compute/instance-templates/create @@ -109,7 +109,7 @@ FLAGS Attaches accelerators (e.g. GPUs) to the instances. type - The specific type (e.g. nvidia-tesla-k80 for nVidia Tesla K80) of + The specific type (e.g. nvidia-tesla-t4 for NVIDIA T4) of accelerator to attach to the instances. Use 'gcloud compute accelerator-types list' to learn about all available accelerator types. diff --git a/gcloud/alpha/compute/instance-templates/create-with-container b/gcloud/alpha/compute/instance-templates/create-with-container index d42506501..adee71cf0 100644 --- a/gcloud/alpha/compute/instance-templates/create-with-container +++ b/gcloud/alpha/compute/instance-templates/create-with-container @@ -99,7 +99,7 @@ FLAGS Attaches accelerators (e.g. GPUs) to the instances. type - The specific type (e.g. nvidia-tesla-k80 for nVidia Tesla K80) of + The specific type (e.g. nvidia-tesla-t4 for NVIDIA T4) of accelerator to attach to the instances. Use 'gcloud compute accelerator-types list' to learn about all available accelerator types. diff --git a/gcloud/alpha/compute/instances/bulk/create b/gcloud/alpha/compute/instances/bulk/create index b2b09d9a5..661c53324 100644 --- a/gcloud/alpha/compute/instances/bulk/create +++ b/gcloud/alpha/compute/instances/bulk/create @@ -136,7 +136,7 @@ OPTIONAL FLAGS Attaches accelerators (e.g. GPUs) to the instances. type - The specific type (e.g. nvidia-tesla-k80 for nVidia Tesla K80) of + The specific type (e.g. nvidia-tesla-t4 for NVIDIA T4) of accelerator to attach to the instances. Use 'gcloud compute accelerator-types list' to learn about all available accelerator types. diff --git a/gcloud/alpha/compute/instances/create b/gcloud/alpha/compute/instances/create index 55bdda6e8..350a1cda7 100644 --- a/gcloud/alpha/compute/instances/create +++ b/gcloud/alpha/compute/instances/create @@ -163,7 +163,7 @@ FLAGS Attaches accelerators (e.g. GPUs) to the instances. type - The specific type (e.g. nvidia-tesla-k80 for nVidia Tesla K80) of + The specific type (e.g. nvidia-tesla-t4 for NVIDIA T4) of accelerator to attach to the instances. Use 'gcloud compute accelerator-types list' to learn about all available accelerator types. diff --git a/gcloud/alpha/compute/instances/create-with-container b/gcloud/alpha/compute/instances/create-with-container index 0d5165a1f..cbbe6dc39 100644 --- a/gcloud/alpha/compute/instances/create-with-container +++ b/gcloud/alpha/compute/instances/create-with-container @@ -115,7 +115,7 @@ FLAGS Attaches accelerators (e.g. GPUs) to the instances. type - The specific type (e.g. nvidia-tesla-k80 for nVidia Tesla K80) of + The specific type (e.g. nvidia-tesla-t4 for NVIDIA T4) of accelerator to attach to the instances. Use 'gcloud compute accelerator-types list' to learn about all available accelerator types. diff --git a/gcloud/alpha/compute/network-firewall-policies/mirroring-rules/create b/gcloud/alpha/compute/network-firewall-policies/mirroring-rules/create index 4467feef6..538c588e5 100644 --- a/gcloud/alpha/compute/network-firewall-policies/mirroring-rules/create +++ b/gcloud/alpha/compute/network-firewall-policies/mirroring-rules/create @@ -58,8 +58,7 @@ OPTIONAL FLAGS will apply. --security-profile-group=SECURITY_PROFILE_GROUP - A security profile group to be used with apply_security_profile_group - action. + A security profile group to be used with mirror action. --src-ip-ranges=[SRC_IP_RANGE,...] A list of IP address blocks that are allowed to make inbound diff --git a/gcloud/alpha/compute/network-firewall-policies/mirroring-rules/update b/gcloud/alpha/compute/network-firewall-policies/mirroring-rules/update index a87f9595d..9ea9d34ab 100644 --- a/gcloud/alpha/compute/network-firewall-policies/mirroring-rules/update +++ b/gcloud/alpha/compute/network-firewall-policies/mirroring-rules/update @@ -63,8 +63,7 @@ OPTIONAL FLAGS New priority for the rule to update. Valid in [0, 65535]. --security-profile-group=SECURITY_PROFILE_GROUP - A security profile group to be used with apply_security_profile_group - action. + A security profile group to be used with mirror action. --src-ip-ranges=[SRC_IP_RANGE,...] A list of IP address blocks that are allowed to make inbound diff --git a/gcloud/alpha/compute/networks/subnets/create b/gcloud/alpha/compute/networks/subnets/create index 89ed7b302..25e5ed100 100644 --- a/gcloud/alpha/compute/networks/subnets/create +++ b/gcloud/alpha/compute/networks/subnets/create @@ -135,6 +135,8 @@ OPTIONAL FLAGS AGGREGATE Reserved for Aggregate Ranges used for aggregating private subnetworks. + CUSTOM_HARDWARE_LINK + Reserved for Custom Hardware Link. GLOBAL_MANAGED_PROXY Reserved for Global Envoy-based Load Balancing. INTERNAL_HTTPS_LOAD_BALANCER diff --git a/gcloud/alpha/compute/queued-resources/create b/gcloud/alpha/compute/queued-resources/create index 4d3ee1f63..af8603015 100644 --- a/gcloud/alpha/compute/queued-resources/create +++ b/gcloud/alpha/compute/queued-resources/create @@ -120,7 +120,7 @@ OPTIONAL FLAGS Attaches accelerators (e.g. GPUs) to the instances. type - The specific type (e.g. nvidia-tesla-k80 for nVidia Tesla K80) of + The specific type (e.g. nvidia-tesla-t4 for NVIDIA T4) of accelerator to attach to the instances. Use 'gcloud compute accelerator-types list' to learn about all available accelerator types. diff --git a/gcloud/alpha/compute/reservations/create b/gcloud/alpha/compute/reservations/create index d4d3c5162..98a01ef39 100644 --- a/gcloud/alpha/compute/reservations/create +++ b/gcloud/alpha/compute/reservations/create @@ -13,7 +13,8 @@ SYNOPSIS --maintenance-interval=MAINTENANCE_INTERVAL --min-cpu-platform=MIN_CPU_PLATFORM]) : --require-specific-reservation --resource-policies=[KEY=VALUE,...]) - [--description=DESCRIPTION] [--zone=ZONE] + [--description=DESCRIPTION] + [--reservation-sharing-policy=RESERVATION_SHARING_POLICY] [--zone=ZONE] [--delete-after-duration=DELETE_AFTER_DURATION | --delete-at-time=DELETE_AT_TIME] [--share-setting=SHARE_SETTING @@ -146,6 +147,16 @@ OPTIONAL FLAGS --description=DESCRIPTION An optional description of the reservation to create. + --reservation-sharing-policy=RESERVATION_SHARING_POLICY + The reservation sharing policy to use for this reservation. + RESERVATION_SHARING_POLICY must be one of: + + ALLOW_ALL + The reservation can be shared with Google Cloud services. + DISALLOW_ALL + The reservation won't be shared with Google Cloud services. If you + omit this flag during creation, the default value is DISALLOW_ALL. + --zone=ZONE Zone of the reservation to create. If not specified and the compute/zone property isn't set, you might be prompted to select a zone diff --git a/gcloud/alpha/compute/reservations/update b/gcloud/alpha/compute/reservations/update index 8c9bba647..778d30845 100644 --- a/gcloud/alpha/compute/reservations/update +++ b/gcloud/alpha/compute/reservations/update @@ -6,6 +6,7 @@ SYNOPSIS gcloud alpha compute reservations update RESERVATION [--add-share-with=PROJECT,[PROJECT,...]] [--remove-share-with=PROJECT,[PROJECT,...]] + [--reservation-sharing-policy=RESERVATION_SHARING_POLICY] [--share-with=SHARE_WITH,[SHARE_WITH,...]] [--vm-count=VM_COUNT] [--zone=ZONE] [--delete-after-duration=DELETE_AFTER_DURATION @@ -59,6 +60,16 @@ FLAGS this reservation is shared with. List must contain project IDs or project numbers. + --reservation-sharing-policy=RESERVATION_SHARING_POLICY + The reservation sharing policy to use for this reservation. + RESERVATION_SHARING_POLICY must be one of: + + ALLOW_ALL + The reservation can be shared with Google Cloud services. + DISALLOW_ALL + The reservation won't be shared with Google Cloud services. If you + omit this flag during creation, the default value is DISALLOW_ALL. + --share-with=SHARE_WITH,[SHARE_WITH,...] If this reservation is shared (--share-setting is not local), provide a list of all of the specific projects that this reservation is shared diff --git a/gcloud/alpha/compute/resource-policies/update/help b/gcloud/alpha/compute/resource-policies/update/help index de3983f68..958c0e060 100644 --- a/gcloud/alpha/compute/resource-policies/update/help +++ b/gcloud/alpha/compute/resource-policies/update/help @@ -17,6 +17,9 @@ GCLOUD WIDE FLAGS COMMANDS COMMAND is one of the following: + instance-schedule + (ALPHA) Update a Compute Engine Instance Schedule Resource Policy. + snapshot-schedule (ALPHA) Update a Compute Engine Snapshot Schedule Resource Policy. diff --git a/gcloud/alpha/compute/resource-policies/update/instance-schedule b/gcloud/alpha/compute/resource-policies/update/instance-schedule new file mode 100644 index 000000000..36f72d4b4 --- /dev/null +++ b/gcloud/alpha/compute/resource-policies/update/instance-schedule @@ -0,0 +1,91 @@ +NAME + gcloud alpha compute resource-policies update instance-schedule - update a + Compute Engine Instance Schedule Resource Policy + +SYNOPSIS + gcloud alpha compute resource-policies update instance-schedule NAME + [--description=DESCRIPTION] [--end-date=END_DATE] + [--initiation-date=INITIATION_DATE] [--region=REGION] + [--timezone=TIMEZONE] [--vm-start-schedule=VM_START_SCHEDULE] + [--vm-stop-schedule=VM_STOP_SCHEDULE] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Update a Compute Engine Instance Schedule Resource Policy. + +EXAMPLES + To update an instance schedule resource policy with specified parameters: + + $ gcloud alpha compute resource-policies update instance-schedule \ + NAME --region=REGION --timezone=UTC \ + --vm-start-schedule="* 7 * * *" \ + --vm-stop-schedule="* 17 * * *" \ + --initiation-date=2025-05-01T00:00:00.000-07:00 \ + --end-date=2027-05-01T00:00:00.000-07:00 + +POSITIONAL ARGUMENTS + NAME + Name of the resource policy to operate on. + +FLAGS + --description=DESCRIPTION + An optional, textual description for the backend. + + --end-date=END_DATE + The expiration time of the schedule policy. The timestamp must be an + RFC3339 valid string. + + --initiation-date=INITIATION_DATE + The start time of the schedule policy. The timestamp must be an RFC3339 + valid string. + + --region=REGION + Region of the resource policy to operate on. If not specified, you + might be prompted to select a region (interactive mode only). + + To avoid prompting when this flag is omitted, you can set the + compute/region property: + + $ gcloud config set compute/region REGION + + A list of regions can be fetched by running: + + $ gcloud compute regions list + + To unset the property, run: + + $ gcloud config unset compute/region + + Alternatively, the region can be stored in the environment variable + CLOUDSDK_COMPUTE_REGION. + + --timezone=TIMEZONE + Timezone used in interpreting schedule. The value of this field must be + a time zone name from the tz database + http://en.wikipedia.org/wiki/Tz_database + + --vm-start-schedule=VM_START_SCHEDULE + Schedule for starting the instance, specified using standard CRON + format. + + --vm-stop-schedule=VM_STOP_SCHEDULE + Schedule for stopping the instance, specified using standard CRON + format. + +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 compute resource-policies update instance-schedule + + $ gcloud beta compute resource-policies update instance-schedule + diff --git a/gcloud/alpha/compute/routers/nats/create b/gcloud/alpha/compute/routers/nats/create index 51104ec0a..34bfeff5a 100644 --- a/gcloud/alpha/compute/routers/nats/create +++ b/gcloud/alpha/compute/routers/nats/create @@ -3,10 +3,7 @@ NAME router SYNOPSIS - gcloud alpha compute routers nats create NAME --router=ROUTER - (--nat-all-subnet-ip-ranges - | --nat-custom-subnet-ip-ranges=SUBNETWORK[:RANGE_NAME|:ALL],[...] - | --nat-primary-subnet-ip-ranges) [--async] + gcloud alpha compute routers nats create NAME --router=ROUTER [--async] [--auto-network-tier=AUTO_NETWORK_TIER] [--[no-]enable-dynamic-port-allocation] [--enable-endpoint-independent-mapping] [--enable-logging] @@ -20,6 +17,11 @@ SYNOPSIS [--type=TYPE] [--udp-idle-timeout=UDP_IDLE_TIMEOUT] [--auto-allocate-nat-external-ips | --nat-external-ip-pool=IP_ADDRESS,[IP_ADDRESS,...]] + [--nat-all-subnet-ip-ranges + | --nat-custom-subnet-ip-ranges=SUBNETWORK[:RANGE_NAME|:ALL],[...] + | --nat-primary-subnet-ip-ranges] + [--nat64-all-v6-subnet-ip-ranges + | --nat64-custom-v6-subnet-ip-ranges=SUBNETWORK,[SUBNETWORK,...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -57,28 +59,6 @@ REQUIRED FLAGS --router=ROUTER The Router to use for NAT. - Exactly one of these must be specified: - - --nat-all-subnet-ip-ranges - Allow all IP ranges of all subnetworks in the region, including - primary and secondary ranges, to use NAT. - - --nat-custom-subnet-ip-ranges=SUBNETWORK[:RANGE_NAME|:ALL],[...] - List of subnetwork primary and secondary IP ranges to be allowed to - use NAT. - - ▸ SUBNETWORK:ALL - specifying a subnetwork name with ALL includes - the primary range and all secondary ranges of the subnet. - ▸ SUBNETWORK - including a subnetwork name includes only the - primary subnet range of the subnetwork. - ▸ SUBNETWORK:RANGE_NAME - specifying a subnetwork and secondary - range name includes only that secondary range. It does not include - the primary range of the subnet. - - --nat-primary-subnet-ip-ranges - Allow only primary IP ranges of all subnetworks in the region to use - NAT. - OPTIONAL FLAGS --async Return immediately, without waiting for the operation in progress to @@ -241,6 +221,42 @@ OPTIONAL FLAGS --nat-external-ip-pool=IP_ADDRESS,[IP_ADDRESS,...] External IP Addresses to use for Cloud NAT + IPv4 subnetwork range options. If they are not specified, one of IPv6 + subnetwork range option has to be provided. + + At most one of these can be specified: + + --nat-all-subnet-ip-ranges + Allow all IP ranges of all subnetworks in the region, including + primary and secondary ranges, to use NAT. + + --nat-custom-subnet-ip-ranges=SUBNETWORK[:RANGE_NAME|:ALL],[...] + List of subnetwork primary and secondary IP ranges to be allowed to + use NAT. + + ▸ SUBNETWORK:ALL - specifying a subnetwork name with ALL includes + the primary range and all secondary ranges of the subnet. + ▸ SUBNETWORK - including a subnetwork name includes only the + primary subnet range of the subnetwork. + ▸ SUBNETWORK:RANGE_NAME - specifying a subnetwork and secondary + range name includes only that secondary range. It does not include + the primary range of the subnet. + + --nat-primary-subnet-ip-ranges + Allow only primary IP ranges of all subnetworks in the region to use + NAT. + + IPv6 subnetwork range options. If they are not specified, one of IPv4 + subnetwork range option has to be provided. + + At most one of these can be specified: + + --nat64-all-v6-subnet-ip-ranges + Allow all ip ranges of ipv6 subnetworks in the region to use NAT. + + --nat64-custom-v6-subnet-ip-ranges=SUBNETWORK,[SUBNETWORK,...] + List of ipv6 subnetworks to be allowed tp use NAT. + 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/compute/routers/nats/update b/gcloud/alpha/compute/routers/nats/update index fb606119f..2579572c3 100644 --- a/gcloud/alpha/compute/routers/nats/update +++ b/gcloud/alpha/compute/routers/nats/update @@ -15,6 +15,11 @@ SYNOPSIS [--clear-min-ports-per-vm | --min-ports-per-vm=MIN_PORTS_PER_VM] [--clear-nat-external-drain-ip-pool | --nat-external-drain-ip-pool=NAT_EXTERNAL_DRAIN_IP_POOL,[...]] + [--clear-nat-subnet-ip-ranges | --nat-all-subnet-ip-ranges + | --nat-custom-subnet-ip-ranges=SUBNETWORK[:RANGE_NAME|:ALL],[...] + | --nat-primary-subnet-ip-ranges] + [--clear-nat64-subnet-ip-ranges | --nat64-all-v6-subnet-ip-ranges + | --nat64-custom-v6-subnet-ip-ranges=SUBNETWORK,[SUBNETWORK,...]] [--clear-tcp-established-idle-timeout | --tcp-established-idle-timeout=TCP_ESTABLISHED_IDLE_TIMEOUT] [--clear-tcp-time-wait-timeout @@ -22,9 +27,7 @@ SYNOPSIS [--clear-tcp-transitory-idle-timeout | --tcp-transitory-idle-timeout=TCP_TRANSITORY_IDLE_TIMEOUT] [--clear-udp-idle-timeout | --udp-idle-timeout=UDP_IDLE_TIMEOUT] - [--nat-all-subnet-ip-ranges - | --nat-custom-subnet-ip-ranges=SUBNETWORK[:RANGE_NAME|:ALL],[...] - | --nat-primary-subnet-ip-ranges] [GCLOUD_WIDE_FLAG ...] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) gcloud alpha compute routers nats update is used to update a NAT in @@ -206,6 +209,46 @@ OPTIONAL FLAGS These IPs must be valid external IPs that have been used as NAT IPs + IPv4 subnetwork range options. + + At most one of these can be specified: + + --clear-nat-subnet-ip-ranges + Clear options related to the NAT's subnet ranges. + + --nat-all-subnet-ip-ranges + Allow all IP ranges of all subnetworks in the region, including + primary and secondary ranges, to use NAT. + + --nat-custom-subnet-ip-ranges=SUBNETWORK[:RANGE_NAME|:ALL],[...] + List of subnetwork primary and secondary IP ranges to be allowed to + use NAT. + + ▸ SUBNETWORK:ALL - specifying a subnetwork name with ALL includes + the primary range and all secondary ranges of the subnet. + ▸ SUBNETWORK - including a subnetwork name includes only the + primary subnet range of the subnetwork. + ▸ SUBNETWORK:RANGE_NAME - specifying a subnetwork and secondary + range name includes only that secondary range. It does not include + the primary range of the subnet. + + --nat-primary-subnet-ip-ranges + Allow only primary IP ranges of all subnetworks in the region to use + NAT. + + IPv6 subnetwork range options. + + At most one of these can be specified: + + --clear-nat64-subnet-ip-ranges + Clear options related to the NAT64's subnet ranges. + + --nat64-all-v6-subnet-ip-ranges + Allow all ip ranges of ipv6 subnetworks in the region to use NAT. + + --nat64-custom-v6-subnet-ip-ranges=SUBNETWORK,[SUBNETWORK,...] + List of ipv6 subnetworks to be allowed tp use NAT. + At most one of these can be specified: --clear-tcp-established-idle-timeout @@ -246,28 +289,6 @@ OPTIONAL FLAGS https://cloud.google.com/sdk/gcloud/reference/topic/datetimes for information on duration formats. - At most one of these can be specified: - - --nat-all-subnet-ip-ranges - Allow all IP ranges of all subnetworks in the region, including - primary and secondary ranges, to use NAT. - - --nat-custom-subnet-ip-ranges=SUBNETWORK[:RANGE_NAME|:ALL],[...] - List of subnetwork primary and secondary IP ranges to be allowed to - use NAT. - - ▸ SUBNETWORK:ALL - specifying a subnetwork name with ALL includes - the primary range and all secondary ranges of the subnet. - ▸ SUBNETWORK - including a subnetwork name includes only the - primary subnet range of the subnetwork. - ▸ SUBNETWORK:RANGE_NAME - specifying a subnetwork and secondary - range name includes only that secondary range. It does not include - the primary range of the subnet. - - --nat-primary-subnet-ip-ranges - Allow only primary IP ranges of all subnetworks in the region to use - NAT. - 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/container/attached/clusters/import b/gcloud/alpha/container/attached/clusters/import index 3701aea9f..c60d61c6c 100644 --- a/gcloud/alpha/container/attached/clusters/import +++ b/gcloud/alpha/container/attached/clusters/import @@ -34,6 +34,8 @@ REQUIRED FLAGS $ gcloud alpha container attached clusters import --distribution=aks $ gcloud alpha container attached clusters import --distribution=eks + $ gcloud alpha container attached clusters import \ + --distribution=generic --platform-version=PLATFORM_VERSION Platform version to use for the cluster. diff --git a/gcloud/alpha/container/attached/clusters/register b/gcloud/alpha/container/attached/clusters/register index 4f7600cf8..6f066540b 100644 --- a/gcloud/alpha/container/attached/clusters/register +++ b/gcloud/alpha/container/attached/clusters/register @@ -94,6 +94,8 @@ REQUIRED FLAGS --distribution=aks $ gcloud alpha container attached clusters register \ --distribution=eks + $ gcloud alpha container attached clusters register \ + --distribution=generic --fleet-project=FLEET_PROJECT ID or number of the Fleet host project where the cluster is registered. diff --git a/gcloud/alpha/container/clusters/create b/gcloud/alpha/container/clusters/create index cdcb5b2c3..1f7ce1998 100644 --- a/gcloud/alpha/container/clusters/create +++ b/gcloud/alpha/container/clusters/create @@ -158,10 +158,10 @@ FLAGS Attaches accelerators (e.g. GPUs) to all nodes. type - (Required) The specific type (e.g. nvidia-tesla-k80 for NVIDIA - Tesla K80) of accelerator to attach to the instances. Use gcloud - compute accelerator-types list to learn about all available - accelerator types. + (Required) The specific type (e.g. nvidia-tesla-t4 for NVIDIA T4) + of accelerator to attach to the instances. Use gcloud compute + accelerator-types list to learn about all available accelerator + types. count (Optional) The number of accelerators to attach to the instances. @@ -1601,11 +1601,11 @@ FLAGS Resource limits are specified in the field 'resourceLimits'. Each resource limits definition contains three fields: resourceType, maximum and minimum. Resource type can be "cpu", "memory" or an - accelerator (e.g. "nvidia-tesla-k80" for nVidia Tesla K80). Use - gcloud compute accelerator-types list to learn about available - accelerator types. Maximum is the maximum allowed amount with the - unit of the resource. Minimum is the minimum allowed amount with - the unit of the resource. + accelerator (e.g. "nvidia-tesla-t4" for NVIDIA T4). Use gcloud + compute accelerator-types list to learn about available accelerator + types. Maximum is the maximum allowed amount with the unit of the + resource. Minimum is the minimum allowed amount with the unit of + the resource. Identity default contains at most one of the below fields: serviceAccount: The Google Cloud Platform Service Account to be @@ -1787,10 +1787,10 @@ FLAGS GPUs) in cluster. type - (Required) The specific type (e.g. nvidia-tesla-k80 for - nVidia Tesla K80) of accelerator for which the limit is - set. Use gcloud compute accelerator-types list to learn - about all available accelerator types. + (Required) The specific type (e.g. nvidia-tesla-t4 for + NVIDIA T4) of accelerator for which the limit is set. Use + gcloud compute accelerator-types list to learn about all + available accelerator types. count (Required) The maximum number of accelerators to which the @@ -1805,10 +1805,10 @@ FLAGS isn't set. type - (Required) The specific type (e.g. nvidia-tesla-k80 for - nVidia Tesla K80) of accelerator for which the limit is - set. Use gcloud compute accelerator-types list to learn - about all available accelerator types. + (Required) The specific type (e.g. nvidia-tesla-t4 for + NVIDIA T4) of accelerator for which the limit is set. Use + gcloud compute accelerator-types list to learn about all + available accelerator types. count (Required) The minimum number of accelerators to which the diff --git a/gcloud/alpha/container/clusters/update b/gcloud/alpha/container/clusters/update index 4729963b2..9c4b1aaaf 100644 --- a/gcloud/alpha/container/clusters/update +++ b/gcloud/alpha/container/clusters/update @@ -1133,8 +1133,8 @@ REQUIRED FLAGS Resource limits are specified in the field 'resourceLimits'. Each resource limits definition contains three fields: resourceType, maximum and minimum. Resource type can be "cpu", "memory" or an - accelerator (e.g. "nvidia-tesla-k80" for nVidia Tesla K80). Use - gcloud compute accelerator-types list to learn about available + accelerator (e.g. "nvidia-tesla-t4" for NVIDIA T4). Use gcloud + compute accelerator-types list to learn about available accelerator types. Maximum is the maximum allowed amount with the unit of the resource. Minimum is the minimum allowed amount with the unit of the resource. @@ -1315,10 +1315,10 @@ REQUIRED FLAGS GPUs) in cluster. type - (Required) The specific type (e.g. nvidia-tesla-k80 for - nVidia Tesla K80) of accelerator for which the limit is - set. Use gcloud compute accelerator-types list to learn - about all available accelerator types. + (Required) The specific type (e.g. nvidia-tesla-t4 for + NVIDIA T4) of accelerator for which the limit is set. Use + gcloud compute accelerator-types list to learn about all + available accelerator types. count (Required) The maximum number of accelerators to which @@ -1333,10 +1333,10 @@ REQUIRED FLAGS it isn't set. type - (Required) The specific type (e.g. nvidia-tesla-k80 for - nVidia Tesla K80) of accelerator for which the limit is - set. Use gcloud compute accelerator-types list to learn - about all available accelerator types. + (Required) The specific type (e.g. nvidia-tesla-t4 for + NVIDIA T4) of accelerator for which the limit is set. Use + gcloud compute accelerator-types list to learn about all + available accelerator types. count (Required) The minimum number of accelerators to which diff --git a/gcloud/alpha/container/fleet/config-management/help b/gcloud/alpha/container/fleet/config-management/help index b48496351..5b6c06da9 100644 --- a/gcloud/alpha/container/fleet/config-management/help +++ b/gcloud/alpha/container/fleet/config-management/help @@ -7,10 +7,10 @@ SYNOPSIS [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) Manage Config Management Feature, which currently supports Config - Sync, Policy Controller, and Hierarchy Controller. Policy Controller users - should use the separate command group: gcloud container fleet - policycontroller. + (ALPHA) Manage Config Sync using the Config Management Feature. Policy + Controller users should use the separate command group: gcloud container + fleet policycontroller. Hierarchy Controller users should use + https://github.com/kubernetes-sigs/hierarchical-namespaces instead. GCLOUD WIDE FLAGS These flags are available to all commands: --help. diff --git a/gcloud/alpha/container/hub/config-management/help b/gcloud/alpha/container/hub/config-management/help index 7fa406ca0..4145ddd3c 100644 --- a/gcloud/alpha/container/hub/config-management/help +++ b/gcloud/alpha/container/hub/config-management/help @@ -6,10 +6,10 @@ SYNOPSIS gcloud alpha container hub config-management COMMAND [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) Manage Config Management Feature, which currently supports Config - Sync, Policy Controller, and Hierarchy Controller. Policy Controller users - should use the separate command group: gcloud container fleet - policycontroller. + (ALPHA) Manage Config Sync using the Config Management Feature. Policy + Controller users should use the separate command group: gcloud container + fleet policycontroller. Hierarchy Controller users should use + https://github.com/kubernetes-sigs/hierarchical-namespaces instead. GCLOUD WIDE FLAGS These flags are available to all commands: --help. diff --git a/gcloud/alpha/container/node-pools/create b/gcloud/alpha/container/node-pools/create index d8b720ef6..5ba0e3329 100644 --- a/gcloud/alpha/container/node-pools/create +++ b/gcloud/alpha/container/node-pools/create @@ -102,10 +102,10 @@ FLAGS Attaches accelerators (e.g. GPUs) to all nodes. type - (Required) The specific type (e.g. nvidia-tesla-k80 for NVIDIA - Tesla K80) of accelerator to attach to the instances. Use gcloud - compute accelerator-types list to learn about all available - accelerator types. + (Required) The specific type (e.g. nvidia-tesla-t4 for NVIDIA T4) + of accelerator to attach to the instances. Use gcloud compute + accelerator-types list to learn about all available accelerator + types. count (Optional) The number of accelerators to attach to the instances. diff --git a/gcloud/alpha/container/node-pools/update b/gcloud/alpha/container/node-pools/update index df3e52079..50760a760 100644 --- a/gcloud/alpha/container/node-pools/update +++ b/gcloud/alpha/container/node-pools/update @@ -13,6 +13,7 @@ SYNOPSIS | --node-labels=[NODE_LABEL,...] | --node-locations=ZONE,[ZONE,...] | --node-taints=[NODE_TAINT,...] | --resource-manager-tags=[KEY=VALUE,...] + | --storage-pools=STORAGE_POOL,[...] | --system-config-from-file=PATH_TO_FILE | --tags=[TAG,...] | --windows-os-version=WINDOWS_OS_VERSION | --workload-metadata=WORKLOAD_METADATA | --enable-blue-green-upgrade @@ -202,6 +203,14 @@ REQUIRED FLAGS policy rules. For instructions, see https://cloud.google.com/firewall/docs/use-tags-for-firewalls. + --storage-pools=STORAGE_POOL,[...] + A list of storage pools where the node pool's boot disks will be + provisioned. Replaces all the current storage pools of an existing + node pool, with the specified storage pools. + + STORAGE_POOL must be in the format + projects/project/zones/zone/storagePools/storagePool + --system-config-from-file=PATH_TO_FILE Path of the YAML/JSON file that contains the node configuration, including Linux kernel parameters (sysctls) and kubelet configs. diff --git a/gcloud/alpha/dataplex/entries/search b/gcloud/alpha/dataplex/entries/search index 20df11aa9..f8d808c9f 100644 --- a/gcloud/alpha/dataplex/entries/search +++ b/gcloud/alpha/dataplex/entries/search @@ -34,7 +34,7 @@ OPTIONAL FLAGS ◆ title [asc|desc], defaults to ascending if not specified. --page-size=PAGE_SIZE - Maximum number of resources per page. No more than 1000. + Maximum number of resources per page. No more than 500. --scope=SCOPE The scope under which the search should be operating. Should either be diff --git a/gcloud/alpha/dataproc/clusters/create b/gcloud/alpha/dataproc/clusters/create index df49b3dc8..fd1f9708e 100644 --- a/gcloud/alpha/dataproc/clusters/create +++ b/gcloud/alpha/dataproc/clusters/create @@ -140,7 +140,7 @@ FLAGS type The specific type of accelerator to attach to the instances, such - as nvidia-tesla-k80 for NVIDIA Tesla K80. Use gcloud compute + as nvidia-tesla-t4 for NVIDIA T4. Use gcloud compute accelerator-types list to display available accelerator types. count @@ -209,7 +209,7 @@ FLAGS type The specific type of accelerator to attach to the instances, such - as nvidia-tesla-k80 for NVIDIA Tesla K80. Use gcloud compute + as nvidia-tesla-t4 for NVIDIA T4. Use gcloud compute accelerator-types list to display available accelerator types. count @@ -336,7 +336,7 @@ FLAGS type The specific type of accelerator to attach to the instances, such - as nvidia-tesla-k80 for NVIDIA Tesla K80. Use gcloud compute + as nvidia-tesla-t4 for NVIDIA T4. Use gcloud compute accelerator-types list to display available accelerator types. count @@ -391,7 +391,7 @@ FLAGS type The specific type of accelerator to attach to the instances, such - as nvidia-tesla-k80 for NVIDIA Tesla K80. Use gcloud compute + as nvidia-tesla-t4 for NVIDIA T4. Use gcloud compute accelerator-types list to display available accelerator types. count diff --git a/gcloud/alpha/dataproc/workflow-templates/set-managed-cluster b/gcloud/alpha/dataproc/workflow-templates/set-managed-cluster index 116b8b337..33d53d395 100644 --- a/gcloud/alpha/dataproc/workflow-templates/set-managed-cluster +++ b/gcloud/alpha/dataproc/workflow-templates/set-managed-cluster @@ -149,7 +149,7 @@ FLAGS type The specific type of accelerator to attach to the instances, such - as nvidia-tesla-k80 for NVIDIA Tesla K80. Use gcloud compute + as nvidia-tesla-t4 for NVIDIA T4. Use gcloud compute accelerator-types list to display available accelerator types. count @@ -268,7 +268,7 @@ FLAGS type The specific type of accelerator to attach to the instances, such - as nvidia-tesla-k80 for NVIDIA Tesla K80. Use gcloud compute + as nvidia-tesla-t4 for NVIDIA T4. Use gcloud compute accelerator-types list to display available accelerator types. count @@ -323,7 +323,7 @@ FLAGS type The specific type of accelerator to attach to the instances, such - as nvidia-tesla-k80 for NVIDIA Tesla K80. Use gcloud compute + as nvidia-tesla-t4 for NVIDIA T4. Use gcloud compute accelerator-types list to display available accelerator types. count diff --git a/gcloud/alpha/developer-connect/connections/update b/gcloud/alpha/developer-connect/connections/update index 19637931d..79bc813fc 100644 --- a/gcloud/alpha/developer-connect/connections/update +++ b/gcloud/alpha/developer-connect/connections/update @@ -203,7 +203,7 @@ FLAGS At most one of these can be specified: --labels=[LABELS,...] - Set labels to new value. Labels as key value pairs + Set labels to new value. Labels as key value pairs. KEY Keys must start with a lowercase character and contain only @@ -226,7 +226,7 @@ FLAGS --labels=path_to_file.(yaml|json) --update-labels=[UPDATE_LABELS,...] - Update labels value or add key value pair. Labels as key value pairs + Update labels value or add key value pair. Labels as key value pairs. KEY Keys must start with a lowercase character and contain only diff --git a/gcloud/alpha/firestore/bulk-delete b/gcloud/alpha/firestore/bulk-delete new file mode 100644 index 000000000..054bbeb61 --- /dev/null +++ b/gcloud/alpha/firestore/bulk-delete @@ -0,0 +1,72 @@ +NAME + gcloud alpha firestore bulk-delete - bulk delete Cloud Firestore documents + +SYNOPSIS + gcloud alpha firestore bulk-delete [--async] + [--collection-ids=[COLLECTION_IDS,...]] + [--database=DATABASE; default="(default)"] + [--namespace-ids=[NAMESPACE_IDS,...]] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) bulk delete Cloud Firestore documents. + +EXAMPLES + To bulk delete a specific set of collections groups asynchronously, run: + + $ gcloud alpha firestore bulk-delete \ + --collection-ids='specific collection group1','specific + collection group2' --async + + To bulk delete all collection groups from certain namespace, run: + + $ gcloud alpha firestore bulk-delete \ + --namespace-ids='specific namespace id' + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --collection-ids=[COLLECTION_IDS,...] + List specifying which collections will be included in the operation. + When omitted, all collections are included. + + For example, to operate on only the customers and orders collections: + + $ gcloud alpha firestore bulk-delete \ + --collection-ids='customers','orders' + + --database=DATABASE; default="(default)" + The database to operate on. The default value is (default). + + For example, to operate on database foo: + + $ gcloud alpha firestore bulk-delete --database='foo' + + --namespace-ids=[NAMESPACE_IDS,...] + List specifying which namespaces will be included in the operation. + When omitted, all namespaces are included. + + This is only supported for Datastore Mode databases. + + For example, to operate on only the customers and orders namespaces: + + $ gcloud alpha firestore bulk-delete \ + --namespaces-ids='customers','orders' + +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 firestore bulk-delete + diff --git a/gcloud/alpha/firestore/databases/restore b/gcloud/alpha/firestore/databases/restore index ba71eec22..4c9f59288 100644 --- a/gcloud/alpha/firestore/databases/restore +++ b/gcloud/alpha/firestore/databases/restore @@ -53,29 +53,30 @@ REQUIRED FLAGS cf9f748a-7980-4703-b1a1-d1ffff591db0 OPTIONAL FLAGS - The encryption configuration of the restored database. If not specified, - the same encryption settings as the backup will be used. + The encryption configuration of the new database being created from the + backup. If not specified, the same encryption settings as the backup will + be used. - To restore to a CMEK-enabled database: + To create a CMEK-enabled database: $ gcloud alpha firestore databases restore \ --encryption-type=customer-managed-encryption \ --kms-key-name=projects/PROJECT_ID/locations/LOCATION_ID/\ keyRings/KEY_RING_ID/cryptoKeys/CRYPTO_KEY_ID - To restore to a Google-default-encrypted database: + To create a Google-default-encrypted database: $ gcloud alpha firestore databases restore \ --encryption-type=google-default-encryption - To restore to a database using the same encryption settings as the backup: + To create a database using the same encryption settings as the backup: $ gcloud alpha firestore databases restore \ - --encryption-type=backup-encryption + --encryption-type=use-source-encryption --encryption-type=ENCRYPTION_TYPE The encryption type of the destination database. ENCRYPTION_TYPE must - be one of: backup-encryption, customer-managed-encryption, + be one of: use-source-encryption, customer-managed-encryption, google-default-encryption. This flag argument must be specified if any of the other arguments in diff --git a/gcloud/alpha/firestore/help b/gcloud/alpha/firestore/help index 7c1b9dc52..db63fcca1 100644 --- a/gcloud/alpha/firestore/help +++ b/gcloud/alpha/firestore/help @@ -9,6 +9,8 @@ DESCRIPTION import -- Import data from Google Cloud Storage + bulk-delete -- Bulk delete documents from Cloud Firestore + indexes -- Manage your Cloud Firestore indexes operations -- Manage Long Running Operations for Cloud Firestore @@ -42,6 +44,9 @@ GROUPS COMMANDS COMMAND is one of the following: + bulk-delete + (ALPHA) bulk delete Cloud Firestore documents. + export (ALPHA) export Cloud Firestore documents to Google Cloud Storage. diff --git a/gcloud/alpha/firestore/indexes/composite/create b/gcloud/alpha/firestore/indexes/composite/create index 4f9f20b67..1a5f5f425 100644 --- a/gcloud/alpha/firestore/indexes/composite/create +++ b/gcloud/alpha/firestore/indexes/composite/create @@ -31,22 +31,24 @@ EXAMPLES REQUIRED FLAGS --field-config=[array-config=ARRAY-CONFIG],[field-path=FIELD-PATH],[order=ORDER],[vector-config=VECTOR-CONFIG] - Configuration for a field. Required, Configuration for a field. + Required, Configuration for an index field. array-config Specifies the configuration for an array field. The only valid - option is 'contains'. Exactly one of 'order' or 'array-config' must - be specified. + option is 'contains'. Exactly one of 'order', 'array-config', or + 'vector-config' must be specified. field-path Specifies the field path (e.g. 'address.city'). This is required. order Specifies the order. Valid options are 'ascending', 'descending'. - Exactly one of order or array-config must be specified. + Exactly one of 'order', 'array-config', or 'vector-config' must be + specified. vector-config - Specifies the vector config. + Specifies the configuration for a vector field. Exactly one of + 'order', 'array-config', or 'vector-config' must be specified. dimension Sets dimension value. diff --git a/gcloud/alpha/managed-kafka/clusters/create b/gcloud/alpha/managed-kafka/clusters/create index 6a3967b98..ecfe97d2f 100644 --- a/gcloud/alpha/managed-kafka/clusters/create +++ b/gcloud/alpha/managed-kafka/clusters/create @@ -1,6 +1,6 @@ NAME - gcloud alpha managed-kafka clusters create - create an Apache Kafka for - BigQuery cluster + gcloud alpha managed-kafka clusters create - create a Managed Service for + Apache Kafka cluster SYNOPSIS gcloud alpha managed-kafka clusters create (CLUSTER : --location=LOCATION) @@ -9,7 +9,7 @@ SYNOPSIS [--labels=[KEY=VALUE,...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) Create an Apache Kafka for BigQuery cluster. + (ALPHA) Create a Managed Service for Apache Kafka cluster. EXAMPLES To create a cluster, run the following: @@ -43,9 +43,9 @@ POSITIONAL ARGUMENTS arguments in this group are specified. --location=LOCATION - ID of the location of the Apache Kafka for BigQuery resource. See - https://cloud.google.com/managed-kafka/docs/locations for a list of - supported locations. + ID of the location of the Managed Service for Apache Kafka resource. + See https://cloud.google.com/managed-kafka/docs/locations for a list + of supported locations. To set the location attribute: ▸ provide the argument cluster on the command line with a fully diff --git a/gcloud/alpha/managed-kafka/clusters/delete b/gcloud/alpha/managed-kafka/clusters/delete index d9da483a6..7d959aeb7 100644 --- a/gcloud/alpha/managed-kafka/clusters/delete +++ b/gcloud/alpha/managed-kafka/clusters/delete @@ -1,13 +1,13 @@ NAME - gcloud alpha managed-kafka clusters delete - delete an Apache Kafka for - BigQuery cluster + gcloud alpha managed-kafka clusters delete - delete a Managed Service for + Apache Kafka cluster SYNOPSIS gcloud alpha managed-kafka clusters delete (CLUSTER : --location=LOCATION) [--async] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) Delete an Apache Kafka for BigQuery cluster. + (ALPHA) Delete a Managed Service for Apache Kafka cluster. EXAMPLES To delete a cluster named mycluster located in us-central1, run the @@ -40,9 +40,9 @@ POSITIONAL ARGUMENTS arguments in this group are specified. --location=LOCATION - ID of the location of the Apache Kafka for BigQuery resource. See - https://cloud.google.com/managed-kafka/docs/locations for a list of - supported locations. + ID of the location of the Managed Service for Apache Kafka resource. + See https://cloud.google.com/managed-kafka/docs/locations for a list + of supported locations. To set the location attribute: ▸ provide the argument cluster on the command line with a fully diff --git a/gcloud/alpha/managed-kafka/clusters/describe b/gcloud/alpha/managed-kafka/clusters/describe index 976c25981..280d3b738 100644 --- a/gcloud/alpha/managed-kafka/clusters/describe +++ b/gcloud/alpha/managed-kafka/clusters/describe @@ -1,13 +1,13 @@ NAME - gcloud alpha managed-kafka clusters describe - describe an Apache Kafka for - BigQuery cluster + gcloud alpha managed-kafka clusters describe - describe a Managed Service + for Apache Kafka cluster SYNOPSIS gcloud alpha managed-kafka clusters describe (CLUSTER : --location=LOCATION) [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) Describe an Apache Kafka for BigQuery cluster. + (ALPHA) Describe a Managed Service for Apache Kafka cluster. EXAMPLES To describe a cluster named mycluster located in us-central1, run the @@ -40,9 +40,9 @@ POSITIONAL ARGUMENTS arguments in this group are specified. --location=LOCATION - ID of the location of the Apache Kafka for BigQuery resource. See - https://cloud.google.com/managed-kafka/docs/locations for a list of - supported locations. + ID of the location of the Managed Service for Apache Kafka resource. + See https://cloud.google.com/managed-kafka/docs/locations for a list + of supported locations. To set the location attribute: ▸ provide the argument cluster on the command line with a fully diff --git a/gcloud/alpha/managed-kafka/clusters/help b/gcloud/alpha/managed-kafka/clusters/help index d5ada1547..ebbc2a75f 100644 --- a/gcloud/alpha/managed-kafka/clusters/help +++ b/gcloud/alpha/managed-kafka/clusters/help @@ -1,12 +1,12 @@ NAME - gcloud alpha managed-kafka clusters - administer Apache Kafka for BigQuery - clusters + gcloud alpha managed-kafka clusters - administer Managed Service for Apache + Kafka clusters SYNOPSIS gcloud alpha managed-kafka clusters COMMAND [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) Administer Apache Kafka for BigQuery clusters. + (ALPHA) Administer Managed Service for Apache Kafka clusters. GCLOUD WIDE FLAGS These flags are available to all commands: --help. @@ -17,20 +17,20 @@ COMMANDS COMMAND is one of the following: create - (ALPHA) Create an Apache Kafka for BigQuery cluster. + (ALPHA) Create a Managed Service for Apache Kafka cluster. delete - (ALPHA) Delete an Apache Kafka for BigQuery cluster. + (ALPHA) Delete a Managed Service for Apache Kafka cluster. describe - (ALPHA) Describe an Apache Kafka for BigQuery cluster. + (ALPHA) Describe a Managed Service for Apache Kafka cluster. list - (ALPHA) List all Apache Kafka for BigQuery clusters in a given + (ALPHA) List all Managed Service for Apache Kafka clusters in a given location. update - (ALPHA) Update an Apache Kafka for BigQuery cluster. + (ALPHA) Update a Managed Service for Apache Kafka cluster. NOTES This command is currently in alpha and might change without notice. If this diff --git a/gcloud/alpha/managed-kafka/clusters/list b/gcloud/alpha/managed-kafka/clusters/list index 10ee2ff45..bff418a45 100644 --- a/gcloud/alpha/managed-kafka/clusters/list +++ b/gcloud/alpha/managed-kafka/clusters/list @@ -1,6 +1,6 @@ NAME - gcloud alpha managed-kafka clusters list - list all Apache Kafka for - BigQuery clusters in a given location + gcloud alpha managed-kafka clusters list - list all Managed Service for + Apache Kafka clusters in a given location SYNOPSIS gcloud alpha managed-kafka clusters list --location=LOCATION diff --git a/gcloud/alpha/managed-kafka/clusters/update b/gcloud/alpha/managed-kafka/clusters/update index 639000d89..dfebde91a 100644 --- a/gcloud/alpha/managed-kafka/clusters/update +++ b/gcloud/alpha/managed-kafka/clusters/update @@ -1,6 +1,6 @@ NAME - gcloud alpha managed-kafka clusters update - update an Apache Kafka for - BigQuery cluster + gcloud alpha managed-kafka clusters update - update a Managed Service for + Apache Kafka cluster SYNOPSIS gcloud alpha managed-kafka clusters update (CLUSTER : --location=LOCATION) @@ -9,7 +9,7 @@ SYNOPSIS [--async] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) Update an Apache Kafka for BigQuery cluster. + (ALPHA) Update a Managed Service for Apache Kafka cluster. EXAMPLES To update an attribute in a cluster named mycluster located in us-central1, @@ -42,9 +42,9 @@ POSITIONAL ARGUMENTS arguments in this group are specified. --location=LOCATION - ID of the location of the Apache Kafka for BigQuery resource. See - https://cloud.google.com/managed-kafka/docs/locations for a list of - supported locations. + ID of the location of the Managed Service for Apache Kafka resource. + See https://cloud.google.com/managed-kafka/docs/locations for a list + of supported locations. To set the location attribute: ▸ provide the argument cluster on the command line with a fully diff --git a/gcloud/alpha/managed-kafka/consumer-groups/delete b/gcloud/alpha/managed-kafka/consumer-groups/delete index f461fb9fb..086c31172 100644 --- a/gcloud/alpha/managed-kafka/consumer-groups/delete +++ b/gcloud/alpha/managed-kafka/consumer-groups/delete @@ -1,6 +1,6 @@ NAME - gcloud alpha managed-kafka consumer-groups delete - delete an Apache Kafka - for BigQuery consumer group + gcloud alpha managed-kafka consumer-groups delete - delete a Managed + Service for Apache Kafka consumer group SYNOPSIS gcloud alpha managed-kafka consumer-groups delete @@ -8,7 +8,7 @@ SYNOPSIS [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) Delete an Apache Kafka for BigQuery consumer group. + (ALPHA) Delete a Managed Service for Apache Kafka consumer group. EXAMPLES To delete a consumer group in a cluster named mycluster located in @@ -50,9 +50,9 @@ POSITIONAL ARGUMENTS ▸ provide the argument --cluster on the command line. --location=LOCATION - ID of the location of the Apache Kafka for BigQuery resource. See - https://cloud.google.com/managed-kafka/docs/locations for a list of - supported locations. + ID of the location of the Managed Service for Apache Kafka resource. + See https://cloud.google.com/managed-kafka/docs/locations for a list + of supported locations. To set the location attribute: ▸ provide the argument consumer_group on the command line with a diff --git a/gcloud/alpha/managed-kafka/consumer-groups/describe b/gcloud/alpha/managed-kafka/consumer-groups/describe index d259a10f2..6657f4376 100644 --- a/gcloud/alpha/managed-kafka/consumer-groups/describe +++ b/gcloud/alpha/managed-kafka/consumer-groups/describe @@ -1,6 +1,6 @@ NAME - gcloud alpha managed-kafka consumer-groups describe - describe an Apache - Kafka for BigQuery consumer group + gcloud alpha managed-kafka consumer-groups describe - describe a Managed + Service for Apache Kafka consumer group SYNOPSIS gcloud alpha managed-kafka consumer-groups describe @@ -8,7 +8,7 @@ SYNOPSIS [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) Describe an Apache Kafka for BigQuery consumer group. + (ALPHA) Describe a Managed Service for Apache Kafka consumer group. EXAMPLES To describe a consumer group in a cluster named mycluster located in @@ -50,9 +50,9 @@ POSITIONAL ARGUMENTS ▸ provide the argument --cluster on the command line. --location=LOCATION - ID of the location of the Apache Kafka for BigQuery resource. See - https://cloud.google.com/managed-kafka/docs/locations for a list of - supported locations. + ID of the location of the Managed Service for Apache Kafka resource. + See https://cloud.google.com/managed-kafka/docs/locations for a list + of supported locations. To set the location attribute: ▸ provide the argument consumer_group on the command line with a diff --git a/gcloud/alpha/managed-kafka/consumer-groups/help b/gcloud/alpha/managed-kafka/consumer-groups/help index 837dbb70a..539f55738 100644 --- a/gcloud/alpha/managed-kafka/consumer-groups/help +++ b/gcloud/alpha/managed-kafka/consumer-groups/help @@ -1,12 +1,12 @@ NAME - gcloud alpha managed-kafka consumer-groups - administer Apache Kafka for - BigQuery consumer groups + gcloud alpha managed-kafka consumer-groups - administer Managed Service for + Apache Kafka consumer groups SYNOPSIS gcloud alpha managed-kafka consumer-groups COMMAND [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) Administer Apache Kafka for BigQuery consumer groups. + (ALPHA) Administer Managed Service for Apache Kafka consumer groups. GCLOUD WIDE FLAGS These flags are available to all commands: --help. @@ -17,17 +17,17 @@ COMMANDS COMMAND is one of the following: delete - (ALPHA) Delete an Apache Kafka for BigQuery consumer group. + (ALPHA) Delete a Managed Service for Apache Kafka consumer group. describe - (ALPHA) Describe an Apache Kafka for BigQuery consumer group. + (ALPHA) Describe a Managed Service for Apache Kafka consumer group. list - (ALPHA) List all Apache Kafka for BigQuery consumer groups in a given - cluster and location. + (ALPHA) List all Managed Service for Apache Kafka consumer groups in a + given cluster and location. update - (ALPHA) Update an Apache Kafka for BigQuery consumer group. + (ALPHA) Update a Managed Service for Apache Kafka consumer group. NOTES This command is currently in alpha and might change without notice. If this diff --git a/gcloud/alpha/managed-kafka/consumer-groups/list b/gcloud/alpha/managed-kafka/consumer-groups/list index 914b241a1..27e63ddbc 100644 --- a/gcloud/alpha/managed-kafka/consumer-groups/list +++ b/gcloud/alpha/managed-kafka/consumer-groups/list @@ -1,6 +1,6 @@ NAME - gcloud alpha managed-kafka consumer-groups list - list all Apache Kafka for - BigQuery consumer groups in a given cluster and location + gcloud alpha managed-kafka consumer-groups list - list all Managed Service + for Apache Kafka consumer groups in a given cluster and location SYNOPSIS gcloud alpha managed-kafka consumer-groups list @@ -8,9 +8,9 @@ SYNOPSIS [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) List all Apache Kafka for BigQuery consumer groups in a given - cluster and location. To specify the maximum number of consumer groups to - list, use the --limit flag. + (ALPHA) List all Managed Service for Apache Kafka consumer groups in a + given cluster and location. To specify the maximum number of consumer + groups to list, use the --limit flag. EXAMPLES To list all consumer groups in a cluster named mycluster located in @@ -43,9 +43,9 @@ POSITIONAL ARGUMENTS arguments in this group are specified. --location=LOCATION - ID of the location of the Apache Kafka for BigQuery resource. See - https://cloud.google.com/managed-kafka/docs/locations for a list of - supported locations. + ID of the location of the Managed Service for Apache Kafka resource. + See https://cloud.google.com/managed-kafka/docs/locations for a list + of supported locations. To set the location attribute: ▸ provide the argument cluster on the command line with a fully diff --git a/gcloud/alpha/managed-kafka/consumer-groups/update b/gcloud/alpha/managed-kafka/consumer-groups/update index 2d6984cb6..7e54897d8 100644 --- a/gcloud/alpha/managed-kafka/consumer-groups/update +++ b/gcloud/alpha/managed-kafka/consumer-groups/update @@ -1,6 +1,6 @@ NAME - gcloud alpha managed-kafka consumer-groups update - update an Apache Kafka - for BigQuery consumer group + gcloud alpha managed-kafka consumer-groups update - update a Managed + Service for Apache Kafka consumer group SYNOPSIS gcloud alpha managed-kafka consumer-groups update @@ -8,7 +8,7 @@ SYNOPSIS --topics-file=JSON|YAML|FILE [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) Update an Apache Kafka for BigQuery consumer group. + (ALPHA) Update a Managed Service for Apache Kafka consumer group. EXAMPLES To specify a file for updating the topics of a consumer group, run the @@ -60,9 +60,9 @@ POSITIONAL ARGUMENTS ▸ provide the argument --cluster on the command line. --location=LOCATION - ID of the location of the Apache Kafka for BigQuery resource. See - https://cloud.google.com/managed-kafka/docs/locations for a list of - supported locations. + ID of the location of the Managed Service for Apache Kafka resource. + See https://cloud.google.com/managed-kafka/docs/locations for a list + of supported locations. To set the location attribute: ▸ provide the argument consumer_group on the command line with a diff --git a/gcloud/alpha/managed-kafka/help b/gcloud/alpha/managed-kafka/help index 248adc695..5f8ab1e97 100644 --- a/gcloud/alpha/managed-kafka/help +++ b/gcloud/alpha/managed-kafka/help @@ -1,13 +1,13 @@ NAME - gcloud alpha managed-kafka - administer Apache Kafka for BigQuery clusters, - topics, and consumer groups + gcloud alpha managed-kafka - administer Managed Service for Apache Kafka + clusters, topics, and consumer groups SYNOPSIS gcloud alpha managed-kafka GROUP [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) Administer Apache Kafka for BigQuery clusters, topics, and consumer - groups. + (ALPHA) Administer Managed Service for Apache Kafka clusters, topics, and + consumer groups. GCLOUD WIDE FLAGS These flags are available to all commands: --help. @@ -18,13 +18,13 @@ GROUPS GROUP is one of the following: clusters - (ALPHA) Administer Apache Kafka for BigQuery clusters. + (ALPHA) Administer Managed Service for Apache Kafka clusters. consumer-groups - (ALPHA) Administer Apache Kafka for BigQuery consumer groups. + (ALPHA) Administer Managed Service for Apache Kafka consumer groups. topics - (ALPHA) Administer Apache Kafka for BigQuery topics. + (ALPHA) Administer Managed Service for Apache Kafka topics. NOTES This command is currently in alpha and might change without notice. If this diff --git a/gcloud/alpha/managed-kafka/topics/create b/gcloud/alpha/managed-kafka/topics/create index 661896f60..fd8011237 100644 --- a/gcloud/alpha/managed-kafka/topics/create +++ b/gcloud/alpha/managed-kafka/topics/create @@ -1,6 +1,6 @@ NAME - gcloud alpha managed-kafka topics create - create an Apache Kafka for - BigQuery topic + gcloud alpha managed-kafka topics create - create a Managed Service for + Apache Kafka topic SYNOPSIS gcloud alpha managed-kafka topics create @@ -9,7 +9,7 @@ SYNOPSIS [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) Create an Apache Kafka for BigQuery topic. + (ALPHA) Create a Managed Service for Apache Kafka topic. EXAMPLES To create a topic in a cluster named mycluster located in us-central1, run @@ -51,9 +51,9 @@ POSITIONAL ARGUMENTS ▸ provide the argument --cluster on the command line. --location=LOCATION - ID of the location of the Apache Kafka for BigQuery resource. See - https://cloud.google.com/managed-kafka/docs/locations for a list of - supported locations. + ID of the location of the Managed Service for Apache Kafka resource. + See https://cloud.google.com/managed-kafka/docs/locations for a list + of supported locations. To set the location attribute: ▸ provide the argument topic on the command line with a fully diff --git a/gcloud/alpha/managed-kafka/topics/delete b/gcloud/alpha/managed-kafka/topics/delete index b31023f0a..320e0f548 100644 --- a/gcloud/alpha/managed-kafka/topics/delete +++ b/gcloud/alpha/managed-kafka/topics/delete @@ -1,13 +1,13 @@ NAME - gcloud alpha managed-kafka topics delete - delete an Apache Kafka for - BigQuery topic + gcloud alpha managed-kafka topics delete - delete a Managed Service for + Apache Kafka topic SYNOPSIS gcloud alpha managed-kafka topics delete (TOPIC : --cluster=CLUSTER --location=LOCATION) [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) Delete an Apache Kafka for BigQuery topic. + (ALPHA) Delete a Managed Service for Apache Kafka topic. EXAMPLES To delete a topic in a cluster named mycluster located in us-central1, run @@ -48,9 +48,9 @@ POSITIONAL ARGUMENTS ▸ provide the argument --cluster on the command line. --location=LOCATION - ID of the location of the Apache Kafka for BigQuery resource. See - https://cloud.google.com/managed-kafka/docs/locations for a list of - supported locations. + ID of the location of the Managed Service for Apache Kafka resource. + See https://cloud.google.com/managed-kafka/docs/locations for a list + of supported locations. To set the location attribute: ▸ provide the argument topic on the command line with a fully diff --git a/gcloud/alpha/managed-kafka/topics/describe b/gcloud/alpha/managed-kafka/topics/describe index 8eb6ecfb4..ae1c607c3 100644 --- a/gcloud/alpha/managed-kafka/topics/describe +++ b/gcloud/alpha/managed-kafka/topics/describe @@ -1,13 +1,13 @@ NAME - gcloud alpha managed-kafka topics describe - describe an Apache Kafka for - BigQuery topic + gcloud alpha managed-kafka topics describe - describe a Managed Service for + Apache Kafka topic SYNOPSIS gcloud alpha managed-kafka topics describe (TOPIC : --cluster=CLUSTER --location=LOCATION) [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) Describe an Apache Kafka for BigQuery topic. + (ALPHA) Describe a Managed Service for Apache Kafka topic. EXAMPLES To describe a topic in a cluster named mycluster located in us-central1, @@ -48,9 +48,9 @@ POSITIONAL ARGUMENTS ▸ provide the argument --cluster on the command line. --location=LOCATION - ID of the location of the Apache Kafka for BigQuery resource. See - https://cloud.google.com/managed-kafka/docs/locations for a list of - supported locations. + ID of the location of the Managed Service for Apache Kafka resource. + See https://cloud.google.com/managed-kafka/docs/locations for a list + of supported locations. To set the location attribute: ▸ provide the argument topic on the command line with a fully diff --git a/gcloud/alpha/managed-kafka/topics/help b/gcloud/alpha/managed-kafka/topics/help index 695ca68bc..fa12cd07a 100644 --- a/gcloud/alpha/managed-kafka/topics/help +++ b/gcloud/alpha/managed-kafka/topics/help @@ -1,12 +1,12 @@ NAME - gcloud alpha managed-kafka topics - administer Apache Kafka for BigQuery - topics + gcloud alpha managed-kafka topics - administer Managed Service for Apache + Kafka topics SYNOPSIS gcloud alpha managed-kafka topics COMMAND [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) Administer Apache Kafka for BigQuery topics. + (ALPHA) Administer Managed Service for Apache Kafka topics. GCLOUD WIDE FLAGS These flags are available to all commands: --help. @@ -17,19 +17,20 @@ COMMANDS COMMAND is one of the following: create - (ALPHA) Create an Apache Kafka for BigQuery topic. + (ALPHA) Create a Managed Service for Apache Kafka topic. delete - (ALPHA) Delete an Apache Kafka for BigQuery topic. + (ALPHA) Delete a Managed Service for Apache Kafka topic. describe - (ALPHA) Describe an Apache Kafka for BigQuery topic. + (ALPHA) Describe a Managed Service for Apache Kafka topic. list - (ALPHA) List all Apache Kafka for BigQuery topics in a given cluster. + (ALPHA) List all Managed Service for Apache Kafka topics in a given + cluster. update - (ALPHA) Update an Apache Kafka for BigQuery topic. + (ALPHA) Update a Managed Service for Apache Kafka topic. NOTES This command is currently in alpha and might change without notice. If this diff --git a/gcloud/alpha/managed-kafka/topics/list b/gcloud/alpha/managed-kafka/topics/list index d13c8531b..b5f8d4732 100644 --- a/gcloud/alpha/managed-kafka/topics/list +++ b/gcloud/alpha/managed-kafka/topics/list @@ -1,6 +1,6 @@ NAME - gcloud alpha managed-kafka topics list - list all Apache Kafka for BigQuery - topics in a given cluster + gcloud alpha managed-kafka topics list - list all Managed Service for + Apache Kafka topics in a given cluster SYNOPSIS gcloud alpha managed-kafka topics list (CLUSTER : --location=LOCATION) @@ -8,8 +8,9 @@ SYNOPSIS [--sort-by=[FIELD,...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) List all Apache Kafka for BigQuery topics in a given cluster. To - specify the maximum number of topics to list, use the --limit flag. + (ALPHA) List all Managed Service for Apache Kafka topics in a given + cluster. To specify the maximum number of topics to list, use the --limit + flag. EXAMPLES To list all topics in a cluster named mycluster located in us-central1, run @@ -42,9 +43,9 @@ POSITIONAL ARGUMENTS arguments in this group are specified. --location=LOCATION - ID of the location of the Apache Kafka for BigQuery resource. See - https://cloud.google.com/managed-kafka/docs/locations for a list of - supported locations. + ID of the location of the Managed Service for Apache Kafka resource. + See https://cloud.google.com/managed-kafka/docs/locations for a list + of supported locations. To set the location attribute: ▸ provide the argument cluster on the command line with a fully diff --git a/gcloud/alpha/managed-kafka/topics/update b/gcloud/alpha/managed-kafka/topics/update index 8cde320fd..11e7a6648 100644 --- a/gcloud/alpha/managed-kafka/topics/update +++ b/gcloud/alpha/managed-kafka/topics/update @@ -1,6 +1,6 @@ NAME - gcloud alpha managed-kafka topics update - update an Apache Kafka for - BigQuery topic + gcloud alpha managed-kafka topics update - update a Managed Service for + Apache Kafka topic SYNOPSIS gcloud alpha managed-kafka topics update @@ -9,7 +9,7 @@ SYNOPSIS [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) Update an Apache Kafka for BigQuery topic. + (ALPHA) Update a Managed Service for Apache Kafka topic. EXAMPLES To update an attribute in a topic, such as the partitions, for a cluster @@ -50,9 +50,9 @@ POSITIONAL ARGUMENTS ▸ provide the argument --cluster on the command line. --location=LOCATION - ID of the location of the Apache Kafka for BigQuery resource. See - https://cloud.google.com/managed-kafka/docs/locations for a list of - supported locations. + ID of the location of the Managed Service for Apache Kafka resource. + See https://cloud.google.com/managed-kafka/docs/locations for a list + of supported locations. To set the location attribute: ▸ provide the argument topic on the command line with a fully diff --git a/gcloud/alpha/network-security/help b/gcloud/alpha/network-security/help index 6b3878e7f..ea1c613e0 100644 --- a/gcloud/alpha/network-security/help +++ b/gcloud/alpha/network-security/help @@ -37,7 +37,10 @@ GROUPS (ALPHA) Manage Mirroring Deployment Group resources. mirroring-deployments - (ALPHA) Manage Mirroing Deployment resources. + (ALPHA) Manage Mirroring Deployment resources. + + mirroring-endpoint-group-associations + (ALPHA) Manage Mirroring Endpoint Group Association resources. mirroring-endpoint-groups (ALPHA) Manage Mirroring Endpoint Group resources. diff --git a/gcloud/alpha/network-security/mirroring-deployments/help b/gcloud/alpha/network-security/mirroring-deployments/help index dac750d0a..0aef727e4 100644 --- a/gcloud/alpha/network-security/mirroring-deployments/help +++ b/gcloud/alpha/network-security/mirroring-deployments/help @@ -1,5 +1,5 @@ NAME - gcloud alpha network-security mirroring-deployments - manage Mirroing + gcloud alpha network-security mirroring-deployments - manage Mirroring Deployment resources SYNOPSIS diff --git a/gcloud/alpha/network-security/mirroring-endpoint-group-associations/create b/gcloud/alpha/network-security/mirroring-endpoint-group-associations/create new file mode 100644 index 000000000..228cccc64 --- /dev/null +++ b/gcloud/alpha/network-security/mirroring-endpoint-group-associations/create @@ -0,0 +1,172 @@ +NAME + gcloud alpha network-security mirroring-endpoint-group-associations create + - create a Mirroring Endpoint Group Association + +SYNOPSIS + gcloud alpha network-security mirroring-endpoint-group-associations create + (MIRRORING_ENDPOINT_GROUP_ASSOCIATION : --location=LOCATION) + --network=NETWORK + (--mirroring-endpoint-group=MIRRORING_ENDPOINT_GROUP + : --mirroring-endpoint-group-location=MIRRORING_ENDPOINT_GROUP_LOCATION) + [--async] [--labels=[KEY=VALUE,...]] + [--max-wait=MAX_WAIT; default="20m"] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Create a mirroring endpoint group association. Successful creation + of an association results in an association in ACTIVE state. Check the + progress of association creation by using gcloud network-security + mirroring-endpoint-group-associations list. + + For more examples, refer to the EXAMPLES section below. + +EXAMPLES + To create a mirroring endpoint group association called my-association, in + project ID my-project, run: + + $ gcloud alpha network-security \ mirroring-endpoint-group-associations create my-association \ + --project=my-project --location=global \ + --mirroring-endpoint-group=my-endpoint-group \ + --network=my-network + + OR + + $ gcloud alpha network-security \ mirroring-endpoint-group-associations create my-association \ + --project=my-project --location=global \ + --mirroring-endpoint-group=my-endpoint-group \ + --network=projects/my-project/global/networks/my-network + + OR + + $ gcloud alpha network-security \ mirroring-endpoint-group-associations create \ + projects/my-project/locations/global/\ + mirroringEndpointGroupAssociations/my-association \ + --mirroring-endpoint-group=projects/my-project/locations/\ + global/mirroringEndpointGroups/my-endpoint-group \ + --network=projects/my-project/global/networks/my-network + +POSITIONAL ARGUMENTS + Mirroring endpoint group association resource - Mirroring Endpoint Group + Association. 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 MIRRORING_ENDPOINT_GROUP_ASSOCIATION 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. + + MIRRORING_ENDPOINT_GROUP_ASSOCIATION + ID of the mirroring endpoint group association or fully qualified + identifier for the mirroring endpoint group association. + + To set the endpoint-group-association-id attribute: + ▸ provide the argument MIRRORING_ENDPOINT_GROUP_ASSOCIATION on the + command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + Location of the mirroring endpoint group association. + + To set the location attribute: + ▸ provide the argument MIRRORING_ENDPOINT_GROUP_ASSOCIATION on the + command line with a fully specified name; + ▸ provide the argument --location on the command line. + +REQUIRED FLAGS + Network resource - Mirroring Endpoint Group Association. 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 --network 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. + + --network=NETWORK + ID of the network or fully qualified identifier for the network. + + To set the network-name attribute: + ▸ provide the argument --network on the command line. + + Mirroring endpoint group resource - Mirroring Endpoint Group. 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 --mirroring-endpoint-group 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. + + --mirroring-endpoint-group=MIRRORING_ENDPOINT_GROUP + ID of the mirroring endpoint group or fully qualified identifier for + the mirroring endpoint group. + + To set the id attribute: + ▸ provide the argument --mirroring-endpoint-group on the command + line. + + This flag argument must be specified if any of the other arguments in + this group are specified. + + --mirroring-endpoint-group-location=MIRRORING_ENDPOINT_GROUP_LOCATION + Location of the mirroring endpoint group. + + To set the location attribute: + ▸ provide the argument --mirroring-endpoint-group on the command + line with a fully specified name; + ▸ provide the argument --mirroring-endpoint-group-location on the + command line; + ▸ provide the argument --location on the command line; + ▸ provide the argument + networksecurity.projects.locations.mirroringEndpointGroupAssociations + on the command line with a fully specified name. + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. The default is True. Enabled by default, use --no-async to + disable. + + --labels=[KEY=VALUE,...] + List of label KEY=VALUE pairs to add. + + Keys must start with a lowercase character and contain only hyphens + (-), underscores (_), lowercase characters, and numbers. Values must + contain only hyphens (-), underscores (_), lowercase characters, and + numbers. + + --max-wait=MAX_WAIT; default="20m" + Time to synchronously wait for the operation to complete, after which + the operation continues asynchronously. Ignored if --no-async isn't + specified. See $ gcloud topic datetimes for information on time + formats. + +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 network-security \ + mirroring-endpoint-group-associations create + diff --git a/gcloud/alpha/network-security/mirroring-endpoint-group-associations/delete b/gcloud/alpha/network-security/mirroring-endpoint-group-associations/delete new file mode 100644 index 000000000..0a5e71303 --- /dev/null +++ b/gcloud/alpha/network-security/mirroring-endpoint-group-associations/delete @@ -0,0 +1,91 @@ +NAME + gcloud alpha network-security mirroring-endpoint-group-associations delete + - delete a Mirroring Endpoint Group Association + +SYNOPSIS + gcloud alpha network-security mirroring-endpoint-group-associations delete + (MIRRORING_ENDPOINT_GROUP_ASSOCIATION : --location=LOCATION) [--async] + [--max-wait=MAX_WAIT; default="20m"] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Delete a mirroring endpoint group association. Check the progress + of deletion by using gcloud network-security + mirroring-endpoint-group-associations list. + + For more examples, refer to the EXAMPLES section below. + +EXAMPLES + To delete a mirroring endpoint group association called my-association, in + project ID my-project, run: + + $ gcloud alpha network-security \ mirroring-endpoint-group-associations delete my-association \ + --project=my-project --location=global + + OR + + $ gcloud alpha network-security \ mirroring-endpoint-group-associations delete \ + projects/my-project/locations/global/\ + mirroringEndpointGroupAssociations/my-association + +POSITIONAL ARGUMENTS + Mirroring endpoint group association resource - Mirroring Endpoint Group + Association. 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 MIRRORING_ENDPOINT_GROUP_ASSOCIATION 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. + + MIRRORING_ENDPOINT_GROUP_ASSOCIATION + ID of the mirroring endpoint group association or fully qualified + identifier for the mirroring endpoint group association. + + To set the endpoint-group-association-id attribute: + ▸ provide the argument MIRRORING_ENDPOINT_GROUP_ASSOCIATION on the + command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + Location of the mirroring endpoint group association. + + To set the location attribute: + ▸ provide the argument MIRRORING_ENDPOINT_GROUP_ASSOCIATION on the + command line with a fully specified name; + ▸ provide the argument --location on the command line. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. The default is True. Enabled by default, use --no-async to + disable. + + --max-wait=MAX_WAIT; default="20m" + Time to synchronously wait for the operation to complete, after which + the operation continues asynchronously. Ignored if --no-async isn't + specified. See $ gcloud topic datetimes for information on time + formats. + +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 network-security \ + mirroring-endpoint-group-associations delete + diff --git a/gcloud/alpha/network-security/mirroring-endpoint-group-associations/describe b/gcloud/alpha/network-security/mirroring-endpoint-group-associations/describe new file mode 100644 index 000000000..80b5cdb4a --- /dev/null +++ b/gcloud/alpha/network-security/mirroring-endpoint-group-associations/describe @@ -0,0 +1,77 @@ +NAME + gcloud alpha network-security mirroring-endpoint-group-associations + describe - describe a Mirroring Endpoint Group Association + +SYNOPSIS + gcloud alpha network-security mirroring-endpoint-group-associations + describe (MIRRORING_ENDPOINT_GROUP_ASSOCIATION : --location=LOCATION) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Describe a mirroring endpoint group association. + + For more examples, refer to the EXAMPLES section below. + +EXAMPLES + To get a description of a mirroring endpoint group association called + my-association in project my-project and location global, run: + + $ gcloud alpha network-security \ mirroring-endpoint-group-associations describe my-association \ + --project=my-project --location=global + + OR + + $ gcloud alpha network-security \ mirroring-endpoint-group-associations describe \ + projects/my-project/locations/global/\ + mirroringEndpointGroupAssociations/my-association + +POSITIONAL ARGUMENTS + Mirroring endpoint group association resource - Mirroring Endpoint Group + Association. 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 MIRRORING_ENDPOINT_GROUP_ASSOCIATION 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. + + MIRRORING_ENDPOINT_GROUP_ASSOCIATION + ID of the mirroring endpoint group association or fully qualified + identifier for the mirroring endpoint group association. + + To set the endpoint-group-association-id attribute: + ▸ provide the argument MIRRORING_ENDPOINT_GROUP_ASSOCIATION on the + command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + Location of the mirroring endpoint group association. + + To set the location attribute: + ▸ provide the argument MIRRORING_ENDPOINT_GROUP_ASSOCIATION on the + command line with a fully specified name; + ▸ provide the argument --location on the command line. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud beta network-security \ + mirroring-endpoint-group-associations describe + diff --git a/gcloud/alpha/network-security/mirroring-endpoint-group-associations/help b/gcloud/alpha/network-security/mirroring-endpoint-group-associations/help new file mode 100644 index 000000000..5f960ed16 --- /dev/null +++ b/gcloud/alpha/network-security/mirroring-endpoint-group-associations/help @@ -0,0 +1,46 @@ +NAME + gcloud alpha network-security mirroring-endpoint-group-associations - + manage Mirroring Endpoint Group Association resources + +SYNOPSIS + gcloud alpha network-security mirroring-endpoint-group-associations COMMAND + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) This class provides commands for managing MirroringEndpoint Group + Associations. + + Attributes: category (str): The category under which this command group + falls. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + create + (ALPHA) Create a Mirroring Endpoint Group Association. + + delete + (ALPHA) Delete a Mirroring Endpoint Group Association. + + describe + (ALPHA) Describe a Mirroring Endpoint Group Association. + + list + (ALPHA) List Mirroring Endpoint Group Associations. + + update + (ALPHA) Update a Mirroring Endpoint Group Association. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud beta network-security mirroring-endpoint-group-associations + diff --git a/gcloud/alpha/network-security/mirroring-endpoint-group-associations/list b/gcloud/alpha/network-security/mirroring-endpoint-group-associations/list new file mode 100644 index 000000000..c3f499429 --- /dev/null +++ b/gcloud/alpha/network-security/mirroring-endpoint-group-associations/list @@ -0,0 +1,101 @@ +NAME + gcloud alpha network-security mirroring-endpoint-group-associations list - + list Mirroring Endpoint Group Associations + +SYNOPSIS + gcloud alpha network-security mirroring-endpoint-group-associations list + [--location=LOCATION] [--filter=EXPRESSION] [--limit=LIMIT] + [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) List mirroring endpoint group associations. + + For more examples, refer to the EXAMPLES section below. + +EXAMPLES + To list mirroring endpoint group associations in project my-project and + location global, run: + + $ gcloud alpha network-security \ mirroring-endpoint-group-associations list \ + --project=my-project --location=global + + OR + + $ gcloud alpha network-security \ mirroring-endpoint-group-associations list --location=global + + OR + + $ gcloud alpha network-security \ mirroring-endpoint-group-associations list \ + --location=projects/my-project/locations/global + +FLAGS + Location resource - The location for a list operation This represents a + Cloud resource. (NOTE) Some attributes are not given arguments in this + group but can be set in other ways. + + To set the project attribute: + ◆ provide the argument --location on the command line with a fully + specified name; + ◆ Location of the Mirroring Endpoint Group Association. Defaults to + global with a fully specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + --location=LOCATION + ID of the location or fully qualified identifier for the location. + + To set the location attribute: + ▸ provide the argument --location on the command line; + ▸ Location of the Mirroring Endpoint Group Association. Defaults to + global. + +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 network-security \ + mirroring-endpoint-group-associations list + diff --git a/gcloud/alpha/network-security/mirroring-endpoint-group-associations/update b/gcloud/alpha/network-security/mirroring-endpoint-group-associations/update new file mode 100644 index 000000000..646025511 --- /dev/null +++ b/gcloud/alpha/network-security/mirroring-endpoint-group-associations/update @@ -0,0 +1,127 @@ +NAME + gcloud alpha network-security mirroring-endpoint-group-associations update + - update a Mirroring Endpoint Group Association + +SYNOPSIS + gcloud alpha network-security mirroring-endpoint-group-associations update + (MIRRORING_ENDPOINT_GROUP_ASSOCIATION : --location=LOCATION) [--async] + [--max-wait=MAX_WAIT; default="20m"] [--update-labels=[KEY=VALUE,...]] + [--clear-labels | --remove-labels=[KEY,...]] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Update a mirroring endpoint group association. Check the progress + of association update by using gcloud network-security + mirroring-endpoint-group-associations list. + + For examples refer to the EXAMPLES section below. + +EXAMPLES + To update labels k1 and k2, run: + + $ gcloud alpha network-security \ mirroring-endpoint-group-associations update my-association \ + --project=my-project --location=global \ + --update-labels=k1=v1,k2=v2 + + To remove labels k3 and k4, run: + + $ gcloud alpha network-security \ mirroring-endpoint-group-associations update my-association \ + --project=my-project --location=global --remove-labels=k3,k4 + + To clear all labels from the mirroring endpoint group association, run: + + $ gcloud alpha network-security \ mirroring-endpoint-group-associations update my-association \ + --project=my-project --location=global --clear-labels + +POSITIONAL ARGUMENTS + Mirroring endpoint group association resource - Mirroring Endpoint Group + Association. 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 MIRRORING_ENDPOINT_GROUP_ASSOCIATION 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. + + MIRRORING_ENDPOINT_GROUP_ASSOCIATION + ID of the mirroring endpoint group association or fully qualified + identifier for the mirroring endpoint group association. + + To set the endpoint-group-association-id attribute: + ▸ provide the argument MIRRORING_ENDPOINT_GROUP_ASSOCIATION on the + command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + Location of the mirroring endpoint group association. + + To set the location attribute: + ▸ provide the argument MIRRORING_ENDPOINT_GROUP_ASSOCIATION on the + command line with a fully specified name; + ▸ provide the argument --location on the command line. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. The default is True. Enabled by default, use --no-async to + disable. + + --max-wait=MAX_WAIT; default="20m" + Time to synchronously wait for the operation to complete, after which + the operation continues asynchronously. Ignored if --no-async isn't + specified. See $ gcloud topic datetimes for information on time + formats. + + --update-labels=[KEY=VALUE,...] + List of label KEY=VALUE pairs to update. If a label exists, its value + is modified. Otherwise, a new label is created. + + Keys must start with a lowercase character and contain only hyphens + (-), underscores (_), lowercase characters, and numbers. Values must + contain only hyphens (-), underscores (_), lowercase characters, and + numbers. + + At most one of these can be specified: + + --clear-labels + Remove all labels. If --update-labels is also specified then + --clear-labels is applied first. + + For example, to remove all labels: + + $ gcloud alpha network-security \ + mirroring-endpoint-group-associations update --clear-labels + + To remove all existing labels and create two new labels, foo and baz: + + $ gcloud alpha network-security \ + mirroring-endpoint-group-associations update --clear-labels \ + --update-labels foo=bar,baz=qux + + --remove-labels=[KEY,...] + List of label keys to remove. If a label does not exist it is + silently ignored. If --update-labels is also specified then + --update-labels is applied first. + +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 network-security \ + mirroring-endpoint-group-associations update + diff --git a/gcloud/alpha/recommender/insights/help b/gcloud/alpha/recommender/insights/help index 4c989f040..60f26a792 100644 --- a/gcloud/alpha/recommender/insights/help +++ b/gcloud/alpha/recommender/insights/help @@ -19,7 +19,7 @@ COMMANDS (ALPHA) Describe an insight. list - (ALPHA) List insights for a Google Cloud entity. + (ALPHA) List insights for Google Cloud resources. mark-accepted (ALPHA) Mark an insight's state as ACCEPTED. diff --git a/gcloud/alpha/recommender/insights/list b/gcloud/alpha/recommender/insights/list index 84fbca853..e161e9f65 100644 --- a/gcloud/alpha/recommender/insights/list +++ b/gcloud/alpha/recommender/insights/list @@ -1,23 +1,23 @@ NAME - gcloud alpha recommender insights list - list insights for a Google Cloud - entity + gcloud alpha recommender insights list - list insights for Google Cloud + resources SYNOPSIS gcloud alpha recommender insights list (--billing-account=BILLING_ACCOUNT | --folder=FOLDER_ID | --organization=ORGANIZATION_ID | --project=PROJECT_ID) - [--insight-type=INSIGHT_TYPE] [--location=LOCATION] + [--insight-type=INSIGHT_TYPE] [--location=LOCATION] [--[no-]recursive] [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) This command lists all insights for a given Google Cloud entity, - location, and insight type. If insight-type or location is not specified, - insights for all supported insight-types and locations are listed. - Supported insight-types can be found here: - https://cloud.google.com/recommender/docs/insights/insight-types. The - following Google Cloud entity types are supported: project, - billing_account, folder, and organization. + (ALPHA) This command lists all insights for the specified Google Cloud + resource, location, and insight type. If an insight type or location is not + specified, insights for all supported insight types or locations, + respectively, are listed. If the --recursive flag is set, insights for + child resources and projects are also listed. Supported insight types can + be found here: + https://cloud.google.com/recommender/docs/insights/insight-types. EXAMPLES To list all insights for a billing account: @@ -48,13 +48,30 @@ REQUIRED FLAGS FLAGS --insight-type=INSIGHT_TYPE - Insight type to list insights for. Supported insight-types can be found - here: https://cloud.google.com/recommender/docs/insights/insight-types + Insight type to list insights for. If no insight type is specified, + insights for all supported insight types are listed. Supported insight + types can be found here: + https://cloud.google.com/recommender/docs/insights/insight-types --location=LOCATION Location to list insights for. If no location is specified, insights for all supported locations are listed. + --[no-]recursive + In addition to listing the insights for the specified organization or + folder, recursively list all of the insights for the resource's child + resources, including their descendents (for example, a folder's + sub-folders), and for the resource's child projects. For example, when + using the --recursive flag and specifying an organization, the response + lists all of the insights associated with that organization, all of the + insights associated with that organization's folders and sub-folders, + and all of the insights associated with that organization's child + projects. The maximum number of resources (organization, folders, + projects, and descendant resources) that can be accessed at once with + the --recursive flag is 100. For a larger number of nested resources, + use BigQuery Export. Use --recursive to enable and --no-recursive to + disable. + LIST COMMAND FLAGS --filter=EXPRESSION Apply a Boolean filter EXPRESSION to each resource item to be listed. diff --git a/gcloud/alpha/recommender/insights/mark-dismissed b/gcloud/alpha/recommender/insights/mark-dismissed index bb5bca855..bbb7d7242 100644 --- a/gcloud/alpha/recommender/insights/mark-dismissed +++ b/gcloud/alpha/recommender/insights/mark-dismissed @@ -58,8 +58,7 @@ REQUIRED FLAGS OPTIONAL FLAGS --recommendation-change-type=Recommendation change type - Recommendation change type. Recommendation change type must be one of: - dismiss, leave_unchanged. + Recommendation change type must be one of: dismiss, leave_unchanged. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/alpha/recommender/recommendations/list b/gcloud/alpha/recommender/recommendations/list index d37c61848..976719d86 100644 --- a/gcloud/alpha/recommender/recommendations/list +++ b/gcloud/alpha/recommender/recommendations/list @@ -6,10 +6,9 @@ SYNOPSIS gcloud alpha recommender recommendations list (--billing-account=BILLING_ACCOUNT | --folder=FOLDER_ID | --organization=ORGANIZATION_ID | --project=PROJECT_ID) - [--location=LOCATION] [--recommender=RECOMMENDER] - [--recursive=BOOLEAN_VALUE] [--filter=EXPRESSION] [--limit=LIMIT] - [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] - [GCLOUD_WIDE_FLAG ...] + [--location=LOCATION] [--recommender=RECOMMENDER] [--[no-]recursive] + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) This command lists all recommendations for the specified Google @@ -56,21 +55,21 @@ FLAGS Supported recommenders can be found here: https://cloud.google.com/recommender/docs/recommenders - --recursive=BOOLEAN_VALUE - By default, --recursive is set to false and can be omitted. If - --recursive=true is used, in addition to listing the recommendations - for the specified organization or folder, recursively lists all of the - recommendations for the resource's child resources, including their - descendents (for example, a folder's sub-folders), and for the - resource's child projects. For example, when using the --recursive flag - and specifying an organization, the response lists all of the - recommendations associated with that organization, all of the - recommendations associated with that organization's folders and - sub-folders, and all of the recommendations associated with that - organization's child projects. The maximum number of resources - (organization, folders, projects, and descendant resources) that can be - accessed at once with the --recursive flag is 100. For a larger number - of nested resources, use BigQuery Export. + --[no-]recursive + In addition to listing the recommendations for the specified + organization or folder, recursively list all of the recommendations for + the resource's child resources, including their descendants (for + example, a folder's sub-folders), and for the resource's child + projects. For example, when using the --recursive flag and specifying + an organization, the response lists all of the recommendations + associated with that organization, all of the recommendations + associated with that organization's folders and sub-folders, and all of + the recommendations associated with that organization's child projects. + The maximum number of resources (organization, folders, projects, and + descendant resources) that can be accessed at once with the --recursive + flag is 100. For a larger number of nested resources, use BigQuery + Export. Use --recursive to enable and --no-recursive to disable. Use + --recursive to enable and --no-recursive to disable. LIST COMMAND FLAGS --filter=EXPRESSION diff --git a/gcloud/alpha/run/deploy b/gcloud/alpha/run/deploy index 6c4414bf3..f6d2a5e19 100644 --- a/gcloud/alpha/run/deploy +++ b/gcloud/alpha/run/deploy @@ -10,14 +10,23 @@ SYNOPSIS [--service-account=SERVICE_ACCOUNT] [--tag=TAG] [--timeout=TIMEOUT] [--no-traffic] [--add-volume-mount=[volume=NAME,mount-path=MOUNT_PATH,...] - --args=[ARG,...] --clear-volume-mounts --command=[COMMAND,...] + --args=[ARG,...] --[no-]automatic-updates --clear-volume-mounts --cpu=CPU --depends-on=[CONTAINER,...] --gpu=GPU --memory=MEMORY --port=PORT --remove-volume-mount=[MOUNT_PATH,...] - --[no-]use-http2 --clear-env-vars | --env-vars-file=FILE_PATH - | --set-env-vars=[KEY=VALUE,...] | --remove-env-vars=[KEY,...] + --[no-]use-http2 --base-image=BASE_IMAGE + | --clear-base-image --build-env-vars-file=FILE_PATH + | --clear-build-env-vars | --set-build-env-vars=[KEY=VALUE,...] + | --remove-build-env-vars=[KEY,...] + --update-build-env-vars=[KEY=VALUE,...] + --build-service-account=BUILD_SERVICE_ACCOUNT + | --clear-build-service-account --build-worker-pool=BUILD_WORKER_POOL + | --clear-build-worker-pool --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,...] --command=[COMMAND,...] + | --function=FUNCTION --image=IMAGE | --source=SOURCE] [--clear-labels | --remove-labels=[KEY,...] --labels=[KEY=VALUE,...] | --update-labels=[KEY=VALUE,...]] [--connectivity=CONNECTIVITY --clear-config-maps @@ -25,7 +34,7 @@ SYNOPSIS --update-config-maps=[KEY=VALUE,...]] [--[no-]allow-unauthenticated --breakglass=JUSTIFICATION --clear-vpc-connector --[no-]cpu-boost --[no-]cpu-throttling - --[no-]default-url --[no-]deploy-health-check + --[no-]default-url --delegate-builds --[no-]deploy-health-check --description=DESCRIPTION --execution-environment=EXECUTION_ENVIRONMENT --[no-]invoker-iam-check --max-surge=MAX_SURGE @@ -210,14 +219,14 @@ FLAGS specified, no arguments are passed. To reset this field to its default, pass an empty string. + --[no-]automatic-updates + Indicates whether automatic base image updates should be enabled + for an image built from source. Use --automatic-updates to enable + and --no-automatic-updates to disable. + --clear-volume-mounts Remove all existing mounts from the current container. - --command=[COMMAND,...] - Entrypoint for the container image. If not specified, the container - image's default Entrypoint is run. To reset this field to its - default, pass an empty string. - --cpu=CPU Set a CPU limit in Kubernetes cpu units. @@ -254,6 +263,69 @@ FLAGS 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: + + --base-image=BASE_IMAGE + Specifies the base image to be used for automatic base image + updates. When deploying from source using the Google Cloud + buildpacks, this flag will also override the base image used for + the application image. See + https://cloud.google.com/run/docs/deploying-source-code for more + details. + + --clear-base-image + Opts out of automatic base image updates. + + At most one of these can be specified: + + --build-env-vars-file=FILE_PATH + Path to a local YAML file with definitions for all build + environment variables. All existing build environment variables + will be removed before the new build environment variables are + added. Example YAML content: + + KEY_1: "value1" + KEY_2: "value 2" + + --clear-build-env-vars + Remove all build environment variables. + + --set-build-env-vars=[KEY=VALUE,...] + List of key-value pairs to set as build environment variables. + All existing build environment variables will be removed first. + + Only --update-build-env-vars and --remove-build-env-vars can be used + together. If both are specified, --remove-build-env-vars will be + applied first. + + --remove-build-env-vars=[KEY,...] + List of build environment variables to be removed. + + --update-build-env-vars=[KEY=VALUE,...] + List of key-value pairs to set as build environment variables. + + At most one of these can be specified: + + --build-service-account=BUILD_SERVICE_ACCOUNT + Specifies the service account to use to execute the build. + Applies only to source deploy builds using the Build API. + + --clear-build-service-account + Clears the Cloud Build service account field. + + At most one of these can be specified: + + --build-worker-pool=BUILD_WORKER_POOL + Name of the Cloud Build Custom Worker Pool that should be used to + build the function. The format of this field is + projects/${PROJECT}/locations/${LOCATION}/workerPools/${WORKERPOOL} + where ${PROJECT} is the project id and ${LOCATION} is the + location where the worker pool is defined and ${WORKERPOOL} is + the short name of the worker pool. + + --clear-build-worker-pool + Clears the Cloud Build Custom Worker Pool field. + At most one of these can be specified: --clear-env-vars @@ -308,6 +380,17 @@ FLAGS --update-secrets=[KEY=VALUE,...] List of key-value pairs to set as secrets. + At most one of these can be specified: + + --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. + + --function=FUNCTION + Specifies that the deployed object is a function. If a value is + provided, that value is used as the entrypoint. + At most one of these can be specified: --image=IMAGE @@ -446,6 +529,10 @@ FLAGS if not specified. Use --default-url to enable and --no-default-url to disable. + --delegate-builds + Specifies that the source deploy for run will use the Build API to + submit the build. + --[no-]deploy-health-check Schedules a single instance of the Revision and waits for it to pass its startup probe for the deployment to succeed. If disabled, the diff --git a/gcloud/alpha/run/services/update b/gcloud/alpha/run/services/update index 1b83a7213..843f969b6 100644 --- a/gcloud/alpha/run/services/update +++ b/gcloud/alpha/run/services/update @@ -14,7 +14,8 @@ SYNOPSIS --args=[ARG,...] --clear-volume-mounts --command=[COMMAND,...] --cpu=CPU --depends-on=[CONTAINER,...] --gpu=GPU --image=IMAGE --memory=MEMORY --port=PORT --remove-volume-mount=[MOUNT_PATH,...] - --[no-]use-http2 --clear-env-vars | --env-vars-file=FILE_PATH + --[no-]use-http2 --base-image=BASE_IMAGE + | --clear-base-image --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,...] @@ -249,6 +250,19 @@ FLAGS 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: + + --base-image=BASE_IMAGE + Specifies the base image to be used for automatic base image + updates. When deploying from source using the Google Cloud + buildpacks, this flag will also override the base image used for + the application image. See + https://cloud.google.com/run/docs/deploying-source-code for more + details. + + --clear-base-image + Opts out of automatic base image updates. + At most one of these can be specified: --clear-env-vars diff --git a/gcloud/alpha/storage/diagnose b/gcloud/alpha/storage/diagnose new file mode 100644 index 000000000..8c3a0b49d --- /dev/null +++ b/gcloud/alpha/storage/diagnose @@ -0,0 +1,171 @@ +NAME + gcloud alpha storage diagnose - diagnose Google Cloud Storage + +SYNOPSIS + gcloud alpha storage diagnose URL [--test-type=[TEST_TYPES,...]] + [--download-type=DOWNLOAD_TYPE; default=] + [--upload-type=UPLOAD_TYPE; default=] + [--process-count=PROCESS_COUNT] [--thread-count=THREAD_COUNT] + [--object-count=OBJECT_COUNT (--object-size=OBJECT_SIZE + | --object-sizes=[OBJECT_SIZES,...])] + [--export : --destination=DESTINATION] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) The diagnose command runs a series of diagnostic tests for common + gcloud storage issues. + + The URL argument must name an exisiting bucket for which the user already + has write permissions. Standard billing also applies. Several test + files/objects will be uploaded and downloaded to this bucket to gauge out + the performance metrics. All the temporary files will be deleted on + successfull completion of the command. + + By default, the command executes DOWNLOAD_THROUGHPUT, UPLOAD_THROUGHPUT and + LATENCY tests. Tests to execute can be overriden by using the --test-type + flag. Each test uses the command defaults or gcloud CLI configurations for + performing the operations. This command also provides a way to override + these values via means of different flags like --process-count, + --thread-count, --download-type, etc. + + The command outputs a diagnostic report with sytem information like free + memory, available CPU, average CPU load per test, disk counter deltas and + diagnostic information specific to individual tests on successful + completion. + +EXAMPLES + The following command runs the default diagnostic tests on my-bucket + bucket: + + $ gcloud alpha storage diagnose gs://my-bucket + + The following command runs only UPLOAD_THROUGHPUT and DOWNLOAD_THROUGHPUT + diagnostic tests: + + $ gcloud alpha storage diagnose gs://my-bucket \ + --test-type=[UPLOAD_THROUGHPUT,DOWNLOAD_THROUGHPUT] + + The following command runs the diagnostic tests using 10 objects of 1MiB + size each with 10 threads and 10 processes at max: + + $ gcloud alpha storage diagnose gs://my-bucket --no-of-objects=10 \ + --object-size=1MiB --process-count=10 --thread-count=10 + + The following command can be used to bundle and export the diagnostic + information to a user defined PATH destination: + + $ gcloud alpha storage diagnose gs://my-bucket --export \ + --destination= + +POSITIONAL ARGUMENTS + URL + Bucket URL to use for the diagnostic tests. + +FLAGS + --test-type=[TEST_TYPES,...] + Tests to run as part of this diagnosis. Following tests are supported: + + DOWNLOAD_THROUGHPUT: Upload objects to the specified bucket and record + the number of bytes transfered per second. + + UPLOAD_THROUGHPUT: Download objects from the specified bucket and + record the number of bytes transfered per second. + + LATENCY: Writes the objects, retrieves its metadata, reads the objects + and records latency of each operation. + + TEST_TYPES must be one of: DOWNLOAD_THROUGHPUT, LATENCY, + UPLOAD_THROUGHPUT. + + --download-type=DOWNLOAD_TYPE; default= + Download strategy to use for the DOWNLOAD_THROUGHPUT diagnostic test. + + STREAMING: Downloads the file in memory, does not use parallelism. + --process-count and --thread-count flag values will be ignored if + provided. + + SLICED: Performs a sliced download + (https://cloud.google.com/storage/docs/sliced-object-downloads) of + objects to a directory. Parallelism can be controlled via + --process-count and --thread-count flags. + + FILE: Download objects as files. Parallelism can be controlled via + --process-count and --thread-count flags. + + DOWNLOAD_TYPE must be one of: FILE, SLICED, STREAMING. + + --upload-type=UPLOAD_TYPE; default= + Upload strategy to use for the UPLOAD_THROUGHPUT diagnostic test. + + FILE: Uploads files to a bucket. Parallelism can be controlled via + --process-count and --thread-count flags. + + PARALLEL_COMPOSITE: Uploads files using a parallel composite strategy + (https://cloud.google.com/storage/docs/parallel-composite-uploads). + Parallelism can be controlled via --process-count and --thread-count + flags. + + STREAMING: Streams the data to the bucket, does not use parallelism. + --process-count and --thread-count flag values will be ignored if + provided. + + UPLOAD_TYPE must be one of: FILE, PARALLEL_COMPOSITE, STREAMING. + + --process-count=PROCESS_COUNT + Number of processes at max to use for each diagnostic test. + + --thread-count=THREAD_COUNT + Number of threads at max to use for each diagnostic test. + + Object properties: + + --object-count=OBJECT_COUNT + Number of objects to use for each diagnostic test. + + This flag argument must be specified if any of the other arguments in + this group are specified. + + Object size properties: + + Exactly one of these must be specified: + + --object-size=OBJECT_SIZE + Object size to use for the diagnostic tests. + + --object-sizes=[OBJECT_SIZES,...] + List of object sizes to use for the tests. Sizes should be provided + for each object specified using --object-count flag. + + Export diagnostic bundle. + + --export + Generate and export a diagnostic bundle. The following information + will be bundled and exported into a gzipped tarball (.tar.gz): + + ▸ Latest gcloud CLI logs. + ▸ Output of running the gcloud storage diagnose command. + ▸ Output of running the gcloud info --anonymize command. + + Note: This command generates a bundle containing system information + like disk counter detlas, CPU information and system configurations. + Please exercise caution while sharing. + + This flag argument must be specified if any of the other arguments in + this group are specified. + + --destination=DESTINATION + Destination file path where the diagnostic bundle will be exported. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/storage/help b/gcloud/alpha/storage/help index a13d330be..ee1dffe9a 100644 --- a/gcloud/alpha/storage/help +++ b/gcloud/alpha/storage/help @@ -50,6 +50,9 @@ COMMANDS cp (ALPHA) Upload, download, and copy Cloud Storage objects. + diagnose + (ALPHA) Diagnose Google Cloud Storage. + du (ALPHA) Displays the amount of space in bytes used by storage resources. diff --git a/gcloud/alpha/storage/objects/update b/gcloud/alpha/storage/objects/update index 4f8a53ca8..e871d05c5 100644 --- a/gcloud/alpha/storage/objects/update +++ b/gcloud/alpha/storage/objects/update @@ -39,13 +39,20 @@ EXAMPLES $ gcloud alpha storage objects update gs://bucket/my-object \ --custom-metadata=key1=value1,key2=value2 + One can use wildcards (https://cloud.google.com/storage/docs/wildcards) to + update multiple objects in a single command. for instance to update all + objects to have a custom-metadata key: + + $ gcloud alpha storage objects update gs://bucket/** \ + --custom-metadata=key1=value1,key2=value2 + Rewrite all JPEG images to the NEARLINE storage class: $ gcloud alpha storage objects update gs://bucket/*.jpg \ --storage-class=NEARLINE - You can also provide a precondition on an object's metageneration in - order to avoid potential race conditions: + You can also provide a precondition on an object's metageneration in order + to avoid potential race conditions: $ gcloud alpha storage objects update gs://bucket/*.jpg \ --storage-class=NEARLINE --if-metageneration-match=123456789 diff --git a/gcloud/beta/ai/endpoints/deploy-model b/gcloud/beta/ai/endpoints/deploy-model index 9cea3d7f8..9e25a4c2f 100644 --- a/gcloud/beta/ai/endpoints/deploy-model +++ b/gcloud/beta/ai/endpoints/deploy-model @@ -11,7 +11,10 @@ SYNOPSIS [--enable-container-logging] [--machine-type=MACHINE_TYPE] [--max-replica-count=MAX_REPLICA_COUNT] [--min-replica-count=MIN_REPLICA_COUNT] - [--service-account=SERVICE_ACCOUNT] [--tpu-topology=TPU_TOPOLOGY] + [--reservation-affinity=[key=KEY], + [reservation-affinity-type=RESERVATION-AFFINITY-TYPE], + [values=VALUES]] [--service-account=SERVICE_ACCOUNT] [--spot] + [--tpu-topology=TPU_TOPOLOGY] [--traffic-split=[DEPLOYED_MODEL_ID=VALUE,...]] [--shared-resources=SHARED_RESOURCES : --shared-resources-region=SHARED_RESOURCES_REGION] @@ -130,12 +133,23 @@ OPTIONAL FLAGS If not specified and the uploaded models use dedicated resources, the default value is 1. + --reservation-affinity=[key=KEY],[reservation-affinity-type=RESERVATION-AFFINITY-TYPE],[values=VALUES] + A ReservationAffinity can be used to configure a Vertex AI resource + (e.g., a DeployedModel) to draw its Compute Engine resources from a + Shared Reservation, or exclusively from on-demand capacity. + --service-account=SERVICE_ACCOUNT Service account that the deployed model's container runs as. Specify the email address of the service account. If this service account is not specified, the container runs as a service account that doesn't have access to the resource project. + --spot + If true, online prediction access logs are sent to Cloud Logging. + + These logs are standard server access logs, containing information like + timestamp and latency for each prediction request. + --tpu-topology=TPU_TOPOLOGY CloudTPU topology to use for this deployment. Required for multihost CloudTPU deployments: diff --git a/gcloud/beta/colab-enterprise/help b/gcloud/beta/colab-enterprise/help new file mode 100644 index 000000000..d5fa45886 --- /dev/null +++ b/gcloud/beta/colab-enterprise/help @@ -0,0 +1,23 @@ +NAME + gcloud beta colab-enterprise - colab Enterprise Command Group + +SYNOPSIS + gcloud beta colab-enterprise GROUP [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Colab Enterprise Command Group. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +GROUPS + GROUP is one of the following: + + runtime-templates + (BETA) Colab Enterprise Runtime Templates command group. + +NOTES + This command is currently in beta and might change without notice. + diff --git a/gcloud/beta/colab-enterprise/runtime-templates/create b/gcloud/beta/colab-enterprise/runtime-templates/create new file mode 100644 index 000000000..f485c6d7f --- /dev/null +++ b/gcloud/beta/colab-enterprise/runtime-templates/create @@ -0,0 +1,229 @@ +NAME + gcloud beta colab-enterprise runtime-templates create - creates a runtime + template + +SYNOPSIS + gcloud beta colab-enterprise runtime-templates create + --display-name=DISPLAY_NAME --region=REGION [--async] + [--runtime-template-id=RUNTIME_TEMPLATE_ID] + [--description=DESCRIPTION --no-enable-euc --enable-secure-boot + --idle-shutdown-timeout=IDLE_SHUTDOWN_TIMEOUT; default="3h" + --labels=[KEY=VALUE,...] --network-tags=[TAGS,...] + --accelerator-count=ACCELERATOR_COUNT + --accelerator-type=ACCELERATOR_TYPE --machine-type=MACHINE_TYPE; + default="e2-standard-4" --disk-size-gb=DISK_SIZE_GB; default=100 + --disk-type=DISK_TYPE; default="PD_STANDARD" [--kms-key=KMS_KEY + : --kms-keyring=KMS_KEYRING --kms-location=KMS_LOCATION + --kms-project=KMS_PROJECT] --no-enable-internet-access + --network=NETWORK [--subnetwork=SUBNETWORK + : --subnetwork-region=SUBNETWORK_REGION]] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Creates a Colab Enterprise runtime template, a VM configuration for + your notebook runtimes. + +EXAMPLES + To create a runtime template in region 'us-central1' with the display name + 'my-runtime-template', run: + + $ gcloud beta colab-enterprise runtime-templates create \ + --region=us-central1 --display-name=my-runtime-template + + To create a runtime template for a VM with machine type n1-standard-2 and + one NVIDIA_TESLA_V100 accelerator, run: + + $ gcloud beta colab-enterprise runtime-templates create \ + --machine-type=n1-standard-2 \ + --accelerator-type=NVIDIA_TESLA_V100 --accelerator-count=1 \ + --region=us-central1 --display-name=my-runtime-template + + To create a runtime template that disables end user credential access, run: + + $ gcloud beta colab-enterprise runtime-templates create \ + --no-enable-euc --region=us-central1 \ + --display-name=my-runtime-template + +REQUIRED FLAGS + --display-name=DISPLAY_NAME + The display name of the runtime template. + + Region resource - Cloud region to create runtime template. Please see + https://cloud.google.com/colab/docs/locations for a list of supported + regions. This represents a Cloud resource. (NOTE) Some attributes are not + given arguments in this group but can be set in other ways. + + To set the project attribute: + ◆ provide the argument --region on the command line with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + --region=REGION + ID of the region or fully qualified identifier for the region. + + To set the region attribute: + ▸ provide the argument --region on the command line. + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --runtime-template-id=RUNTIME_TEMPLATE_ID + The id of the runtime template. If not specified, a random id will be + generated. + + Configuration of the runtime template + + --description=DESCRIPTION + The description of the runtime template. + + --enable-euc + Enable end user credential access for the runtime. Enabled by + default, use --no-enable-euc to disable. + + --enable-secure-boot + Enables secure boot for the runtime. Disabled by default. + + --idle-shutdown-timeout=IDLE_SHUTDOWN_TIMEOUT; default="3h" + The duration after which the runtime is automatically shut down. An + input of 0s disables the idle shutdown feature, and a valid range is + [10m, 24h]. See '$ gcloud topic datetimes' for details on formatting + the input duration. + + --labels=[KEY=VALUE,...] + Add labels to identify and group the runtime template. + + --network-tags=[TAGS,...] + Applies the given Compute Engine tags to the runtime. + + The machine configuration of the runtime provisioned from this template. + + --accelerator-count=ACCELERATOR_COUNT + The number of accelerators used by the runtime. + + --accelerator-type=ACCELERATOR_TYPE + The type of hardware accelerator used by the runtime. If specified, + --accelerator-count must also be specified. ACCELERATOR_TYPE must + be one of: NVIDIA_TESLA_V100, NVIDIA_TESLA_T4, NVIDIA_TESLA_A100, + NVIDIA_A100_80GB, NVIDIA_L4. + + --machine-type=MACHINE_TYPE; default="e2-standard-4" + The Compute Engine machine type selected for the runtime. + + The configuration for the data disk of the runtime provisioned from this + template. + + --disk-size-gb=DISK_SIZE_GB; default=100 + The disk size of the runtime in GB. If specified, the --disk-type + must also be specified. The minimum size is 10GB and the maximum is + 65536GB. + + --disk-type=DISK_TYPE; default="PD_STANDARD" + The type of the persistent disk. DISK_TYPE must be one of: + PD_STANDARD, PD_SSD, PD_BALANCED, PD_EXTREME. + + Key resource - The Cloud KMS encryption key (customer-managed encryption + key) used to protect the runtime. The key must be in the same region as + the runtime. If not specified, Google-managed encryption keys will be + used. The arguments in this group can be used to specify the attributes + of this resource. + + --kms-key=KMS_KEY + ID of the key or fully qualified identifier for the key. + + To set the kms-key attribute: + ▫ provide the argument --kms-key on the command line. + + This flag argument must be specified if any of the other arguments + in this group are specified. + + --kms-keyring=KMS_KEYRING + KMS keyring id of the key. + + To set the kms-keyring attribute: + ▫ provide the argument --kms-key on the command line with a fully + specified name; + ▫ provide the argument --kms-keyring on the command line. + + --kms-location=KMS_LOCATION + Cloud location for the key. + + To set the kms-location attribute: + ▫ provide the argument --kms-key on the command line with a fully + specified name; + ▫ provide the argument --kms-location on the command line. + + --kms-project=KMS_PROJECT + Cloud project id for the key. + + To set the kms-project attribute: + ▫ provide the argument --kms-key on the command line with a fully + specified name; + ▫ provide the argument --kms-project on the command line. + + The network configuration for the runtime. + + --enable-internet-access + Enable public internet access for the runtime. Enabled by default, + use --no-enable-internet-access to disable. + + Network resource - The name of the VPC that this runtime is in. 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 --network on the command line with a fully + specified name; + ▫ provide the argument --project on the command line; + ▫ set the property core/project. + + --network=NETWORK + ID of the network or fully qualified identifier for the network. + + To set the network attribute: + ◇ provide the argument --network on the command line. + + Subnetwork resource - The name of the subnetwork that this runtime is + in. 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 --subnetwork on the command line with a + fully specified name; + ▫ provide the argument --project on the command line; + ▫ set the property core/project. + + --subnetwork=SUBNETWORK + ID of the subnetwork or fully qualified identifier for the + subnetwork. + + To set the subnetwork attribute: + ◇ provide the argument --subnetwork on the command line. + + This flag argument must be specified if any of the other + arguments in this group are specified. + + --subnetwork-region=SUBNETWORK_REGION + Google Cloud region of this subnetwork + https://cloud.google.com/compute/docs/regions-zones/#locations. + + To set the subnetwork-region attribute: + ◇ provide the argument --subnetwork on the command line with a + fully specified name; + ◇ provide the argument --subnetwork-region 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. + diff --git a/gcloud/beta/colab-enterprise/runtime-templates/delete b/gcloud/beta/colab-enterprise/runtime-templates/delete new file mode 100644 index 000000000..15c0bb718 --- /dev/null +++ b/gcloud/beta/colab-enterprise/runtime-templates/delete @@ -0,0 +1,68 @@ +NAME + gcloud beta colab-enterprise runtime-templates delete - deletes a runtime + template + +SYNOPSIS + gcloud beta colab-enterprise runtime-templates delete + (RUNTIME_TEMPLATE : --region=REGION) [--async] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Deletes a Colab Enterprise notebook runtime template. + +EXAMPLES + To delete a runtime template with id 'my-runtime-template' in region + 'us-central1', run: + + $ gcloud beta colab-enterprise runtime-templates delete \ + --my-runtime-template --region=us-central1 + +POSITIONAL ARGUMENTS + Runtime template resource - Unique name of the runtime template to delete. + This was optionally provided by setting --runtime-template-id in the + create runtime-template command, or was system-generated if unspecified. + 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 runtime_template 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. + + RUNTIME_TEMPLATE + ID of the runtime template or fully qualified identifier for the + runtime template. + + To set the name attribute: + ▸ provide the argument runtime_template on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --region=REGION + Cloud region for the runtime template. + + To set the region attribute: + ▸ provide the argument runtime_template on the command line with a + fully specified name; + ▸ provide the argument --region on the command line. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. + diff --git a/gcloud/beta/colab-enterprise/runtime-templates/describe b/gcloud/beta/colab-enterprise/runtime-templates/describe new file mode 100644 index 000000000..1c474557f --- /dev/null +++ b/gcloud/beta/colab-enterprise/runtime-templates/describe @@ -0,0 +1,63 @@ +NAME + gcloud beta colab-enterprise runtime-templates describe - describes a + runtime template + +SYNOPSIS + gcloud beta colab-enterprise runtime-templates describe + (RUNTIME_TEMPLATE : --region=REGION) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Describes a Colab Enterprise notebook runtime template. + +EXAMPLES + To describe a runtime template with id 'my-runtime-template' in region + 'us-central1', run: + + $ gcloud beta colab-enterprise runtime-templates describe \ + --my-runtime-template --region=us-central1 + +POSITIONAL ARGUMENTS + Runtime template resource - Unique name of the runtime template to + describe. This was optionally provided by setting --runtime-template-id in + the create runtime-template command, or was system-generated if + unspecified. 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 runtime_template 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. + + RUNTIME_TEMPLATE + ID of the runtime template or fully qualified identifier for the + runtime template. + + To set the name attribute: + ▸ provide the argument runtime_template on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --region=REGION + Cloud region for the runtime template. + + To set the region attribute: + ▸ provide the argument runtime_template on the command line with a + fully specified name; + ▸ provide the argument --region 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. + diff --git a/gcloud/beta/colab-enterprise/runtime-templates/help b/gcloud/beta/colab-enterprise/runtime-templates/help new file mode 100644 index 000000000..67db31d19 --- /dev/null +++ b/gcloud/beta/colab-enterprise/runtime-templates/help @@ -0,0 +1,35 @@ +NAME + gcloud beta colab-enterprise runtime-templates - colab Enterprise Runtime + Templates command group + +SYNOPSIS + gcloud beta colab-enterprise runtime-templates COMMAND + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) For more information about runtime templates, see + https://cloud.google.com/colab/docs/runtimes#runtime-templates + +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) Creates a runtime template. + + delete + (BETA) Deletes a runtime template. + + describe + (BETA) Describes a runtime template. + + list + (BETA) Lists your runtime templates. + +NOTES + This command is currently in beta and might change without notice. + diff --git a/gcloud/beta/colab-enterprise/runtime-templates/list b/gcloud/beta/colab-enterprise/runtime-templates/list new file mode 100644 index 000000000..2d1ccd3fd --- /dev/null +++ b/gcloud/beta/colab-enterprise/runtime-templates/list @@ -0,0 +1,83 @@ +NAME + gcloud beta colab-enterprise runtime-templates list - lists your runtime + templates + +SYNOPSIS + gcloud beta colab-enterprise runtime-templates list --region=REGION + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Lists your project's Colab Enterprise notebook runtime templates in + a given region. + +EXAMPLES + To list your runtime templates in region 'us-central1', run: + + $ gcloud beta colab-enterprise runtime-templates list \ + --region=us-central1 + +REQUIRED FLAGS + Region resource - Cloud region for which to list all runtime templates. + Please see https://cloud.google.com/colab/docs/locations for a list of + supported regions. This represents a Cloud resource. (NOTE) Some + attributes are not given arguments in this group but can be set in other + ways. + + To set the project attribute: + ◆ provide the argument --region on the command line with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + --region=REGION + ID of the region or fully qualified identifier for the region. + + To set the region attribute: + ▸ provide the argument --region on the command line. + +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. + diff --git a/gcloud/beta/compute/firewall-policies/mirroring-rules/create b/gcloud/beta/compute/firewall-policies/mirroring-rules/create index be5ce45ee..6a30b35bd 100644 --- a/gcloud/beta/compute/firewall-policies/mirroring-rules/create +++ b/gcloud/beta/compute/firewall-policies/mirroring-rules/create @@ -63,8 +63,8 @@ OPTIONAL FLAGS set if FIREWALL_POLICY is short name. --security-profile-group=SECURITY_PROFILE_GROUP - An org-based security profile group to be used with - apply_security_profile_group action. Allowed formats are: a) + An org-based security profile group to be used with mirror action. + Allowed formats are: a) http(s):////organizations//locations/global/securityProfileGroups/ b) (//)/organizations//locations/global/securityProfileGroups/ diff --git a/gcloud/beta/compute/firewall-policies/mirroring-rules/update b/gcloud/beta/compute/firewall-policies/mirroring-rules/update index b8dab9070..20bdedccf 100644 --- a/gcloud/beta/compute/firewall-policies/mirroring-rules/update +++ b/gcloud/beta/compute/firewall-policies/mirroring-rules/update @@ -66,8 +66,8 @@ OPTIONAL FLAGS set if FIREWALL_POLICY is short name. --security-profile-group=SECURITY_PROFILE_GROUP - An org-based security profile group to be used with - apply_security_profile_group action. Allowed formats are: a) + An org-based security profile group to be used with mirror action. + Allowed formats are: a) http(s):////organizations//locations/global/securityProfileGroups/ b) (//)/organizations//locations/global/securityProfileGroups/ diff --git a/gcloud/beta/compute/instance-templates/create b/gcloud/beta/compute/instance-templates/create index 1348b9e70..9240fc8ec 100644 --- a/gcloud/beta/compute/instance-templates/create +++ b/gcloud/beta/compute/instance-templates/create @@ -103,7 +103,7 @@ FLAGS Attaches accelerators (e.g. GPUs) to the instances. type - The specific type (e.g. nvidia-tesla-k80 for nVidia Tesla K80) of + The specific type (e.g. nvidia-tesla-t4 for NVIDIA T4) of accelerator to attach to the instances. Use 'gcloud compute accelerator-types list' to learn about all available accelerator types. diff --git a/gcloud/beta/compute/instance-templates/create-with-container b/gcloud/beta/compute/instance-templates/create-with-container index 2e341810e..3ba57962c 100644 --- a/gcloud/beta/compute/instance-templates/create-with-container +++ b/gcloud/beta/compute/instance-templates/create-with-container @@ -94,7 +94,7 @@ FLAGS Attaches accelerators (e.g. GPUs) to the instances. type - The specific type (e.g. nvidia-tesla-k80 for nVidia Tesla K80) of + The specific type (e.g. nvidia-tesla-t4 for NVIDIA T4) of accelerator to attach to the instances. Use 'gcloud compute accelerator-types list' to learn about all available accelerator types. diff --git a/gcloud/beta/compute/instances/bulk/create b/gcloud/beta/compute/instances/bulk/create index 9ac5d04b3..f3b41360d 100644 --- a/gcloud/beta/compute/instances/bulk/create +++ b/gcloud/beta/compute/instances/bulk/create @@ -133,7 +133,7 @@ OPTIONAL FLAGS Attaches accelerators (e.g. GPUs) to the instances. type - The specific type (e.g. nvidia-tesla-k80 for nVidia Tesla K80) of + The specific type (e.g. nvidia-tesla-t4 for NVIDIA T4) of accelerator to attach to the instances. Use 'gcloud compute accelerator-types list' to learn about all available accelerator types. diff --git a/gcloud/beta/compute/instances/create b/gcloud/beta/compute/instances/create index 61485ed75..b3f6dae0e 100644 --- a/gcloud/beta/compute/instances/create +++ b/gcloud/beta/compute/instances/create @@ -146,7 +146,7 @@ FLAGS Attaches accelerators (e.g. GPUs) to the instances. type - The specific type (e.g. nvidia-tesla-k80 for nVidia Tesla K80) of + The specific type (e.g. nvidia-tesla-t4 for NVIDIA T4) of accelerator to attach to the instances. Use 'gcloud compute accelerator-types list' to learn about all available accelerator types. diff --git a/gcloud/beta/compute/instances/create-with-container b/gcloud/beta/compute/instances/create-with-container index e652ad048..d73940974 100644 --- a/gcloud/beta/compute/instances/create-with-container +++ b/gcloud/beta/compute/instances/create-with-container @@ -109,7 +109,7 @@ FLAGS Attaches accelerators (e.g. GPUs) to the instances. type - The specific type (e.g. nvidia-tesla-k80 for nVidia Tesla K80) of + The specific type (e.g. nvidia-tesla-t4 for NVIDIA T4) of accelerator to attach to the instances. Use 'gcloud compute accelerator-types list' to learn about all available accelerator types. diff --git a/gcloud/beta/compute/network-firewall-policies/mirroring-rules/create b/gcloud/beta/compute/network-firewall-policies/mirroring-rules/create index 41454e84f..ed9ed4208 100644 --- a/gcloud/beta/compute/network-firewall-policies/mirroring-rules/create +++ b/gcloud/beta/compute/network-firewall-policies/mirroring-rules/create @@ -58,8 +58,7 @@ OPTIONAL FLAGS will apply. --security-profile-group=SECURITY_PROFILE_GROUP - A security profile group to be used with apply_security_profile_group - action. + A security profile group to be used with mirror action. --src-ip-ranges=[SRC_IP_RANGE,...] A list of IP address blocks that are allowed to make inbound diff --git a/gcloud/beta/compute/network-firewall-policies/mirroring-rules/update b/gcloud/beta/compute/network-firewall-policies/mirroring-rules/update index 674dc8524..f78990b1f 100644 --- a/gcloud/beta/compute/network-firewall-policies/mirroring-rules/update +++ b/gcloud/beta/compute/network-firewall-policies/mirroring-rules/update @@ -63,8 +63,7 @@ OPTIONAL FLAGS New priority for the rule to update. Valid in [0, 65535]. --security-profile-group=SECURITY_PROFILE_GROUP - A security profile group to be used with apply_security_profile_group - action. + A security profile group to be used with mirror action. --src-ip-ranges=[SRC_IP_RANGE,...] A list of IP address blocks that are allowed to make inbound diff --git a/gcloud/beta/compute/reservations/create b/gcloud/beta/compute/reservations/create index 0d959958e..91f8cf16f 100644 --- a/gcloud/beta/compute/reservations/create +++ b/gcloud/beta/compute/reservations/create @@ -11,7 +11,8 @@ SYNOPSIS --local-ssd=[interface=INTERFACE],[size=SIZE] --min-cpu-platform=MIN_CPU_PLATFORM]) : --require-specific-reservation --resource-policies=[KEY=VALUE,...]) - [--description=DESCRIPTION] [--zone=ZONE] + [--description=DESCRIPTION] + [--reservation-sharing-policy=RESERVATION_SHARING_POLICY] [--zone=ZONE] [--delete-after-duration=DELETE_AFTER_DURATION | --delete-at-time=DELETE_AT_TIME] [--share-setting=SHARE_SETTING @@ -118,6 +119,16 @@ OPTIONAL FLAGS --description=DESCRIPTION An optional description of the reservation to create. + --reservation-sharing-policy=RESERVATION_SHARING_POLICY + The reservation sharing policy to use for this reservation. + RESERVATION_SHARING_POLICY must be one of: + + ALLOW_ALL + The reservation can be shared with Google Cloud services. + DISALLOW_ALL + The reservation won't be shared with Google Cloud services. If you + omit this flag during creation, the default value is DISALLOW_ALL. + --zone=ZONE Zone of the reservation to create. If not specified and the compute/zone property isn't set, you might be prompted to select a zone diff --git a/gcloud/beta/compute/reservations/update b/gcloud/beta/compute/reservations/update index 1d3480fdb..eb6ac2db4 100644 --- a/gcloud/beta/compute/reservations/update +++ b/gcloud/beta/compute/reservations/update @@ -6,6 +6,7 @@ SYNOPSIS gcloud beta compute reservations update RESERVATION [--add-share-with=PROJECT,[PROJECT,...]] [--remove-share-with=PROJECT,[PROJECT,...]] + [--reservation-sharing-policy=RESERVATION_SHARING_POLICY] [--share-with=SHARE_WITH,[SHARE_WITH,...]] [--vm-count=VM_COUNT] [--zone=ZONE] [--delete-after-duration=DELETE_AFTER_DURATION @@ -59,6 +60,16 @@ FLAGS this reservation is shared with. List must contain project IDs or project numbers. + --reservation-sharing-policy=RESERVATION_SHARING_POLICY + The reservation sharing policy to use for this reservation. + RESERVATION_SHARING_POLICY must be one of: + + ALLOW_ALL + The reservation can be shared with Google Cloud services. + DISALLOW_ALL + The reservation won't be shared with Google Cloud services. If you + omit this flag during creation, the default value is DISALLOW_ALL. + --share-with=SHARE_WITH,[SHARE_WITH,...] If this reservation is shared (--share-setting is not local), provide a list of all of the specific projects that this reservation is shared diff --git a/gcloud/beta/compute/resource-policies/update/help b/gcloud/beta/compute/resource-policies/update/help index 9f5ba09b4..725cd3693 100644 --- a/gcloud/beta/compute/resource-policies/update/help +++ b/gcloud/beta/compute/resource-policies/update/help @@ -16,6 +16,9 @@ GCLOUD WIDE FLAGS COMMANDS COMMAND is one of the following: + instance-schedule + (BETA) Update a Compute Engine Instance Schedule Resource Policy. + snapshot-schedule (BETA) Update a Compute Engine Snapshot Schedule Resource Policy. diff --git a/gcloud/beta/compute/resource-policies/update/instance-schedule b/gcloud/beta/compute/resource-policies/update/instance-schedule new file mode 100644 index 000000000..11919d8af --- /dev/null +++ b/gcloud/beta/compute/resource-policies/update/instance-schedule @@ -0,0 +1,89 @@ +NAME + gcloud beta compute resource-policies update instance-schedule - update a + Compute Engine Instance Schedule Resource Policy + +SYNOPSIS + gcloud beta compute resource-policies update instance-schedule NAME + [--description=DESCRIPTION] [--end-date=END_DATE] + [--initiation-date=INITIATION_DATE] [--region=REGION] + [--timezone=TIMEZONE] [--vm-start-schedule=VM_START_SCHEDULE] + [--vm-stop-schedule=VM_STOP_SCHEDULE] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Update a Compute Engine Instance Schedule Resource Policy. + +EXAMPLES + To update an instance schedule resource policy with specified parameters: + + $ gcloud beta compute resource-policies update instance-schedule \ + NAME --region=REGION --timezone=UTC \ + --vm-start-schedule="* 7 * * *" \ + --vm-stop-schedule="* 17 * * *" \ + --initiation-date=2025-05-01T00:00:00.000-07:00 \ + --end-date=2027-05-01T00:00:00.000-07:00 + +POSITIONAL ARGUMENTS + NAME + Name of the resource policy to operate on. + +FLAGS + --description=DESCRIPTION + An optional, textual description for the backend. + + --end-date=END_DATE + The expiration time of the schedule policy. The timestamp must be an + RFC3339 valid string. + + --initiation-date=INITIATION_DATE + The start time of the schedule policy. The timestamp must be an RFC3339 + valid string. + + --region=REGION + Region of the resource policy to operate on. If not specified, you + might be prompted to select a region (interactive mode only). + + To avoid prompting when this flag is omitted, you can set the + compute/region property: + + $ gcloud config set compute/region REGION + + A list of regions can be fetched by running: + + $ gcloud compute regions list + + To unset the property, run: + + $ gcloud config unset compute/region + + Alternatively, the region can be stored in the environment variable + CLOUDSDK_COMPUTE_REGION. + + --timezone=TIMEZONE + Timezone used in interpreting schedule. The value of this field must be + a time zone name from the tz database + http://en.wikipedia.org/wiki/Tz_database + + --vm-start-schedule=VM_START_SCHEDULE + Schedule for starting the instance, specified using standard CRON + format. + + --vm-stop-schedule=VM_STOP_SCHEDULE + Schedule for stopping the instance, specified using standard CRON + format. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud compute resource-policies update instance-schedule + + $ gcloud alpha compute resource-policies update instance-schedule + diff --git a/gcloud/beta/container/clusters/create b/gcloud/beta/container/clusters/create index a54418fde..de78062b6 100644 --- a/gcloud/beta/container/clusters/create +++ b/gcloud/beta/container/clusters/create @@ -153,10 +153,10 @@ FLAGS Attaches accelerators (e.g. GPUs) to all nodes. type - (Required) The specific type (e.g. nvidia-tesla-k80 for NVIDIA - Tesla K80) of accelerator to attach to the instances. Use gcloud - compute accelerator-types list to learn about all available - accelerator types. + (Required) The specific type (e.g. nvidia-tesla-t4 for NVIDIA T4) + of accelerator to attach to the instances. Use gcloud compute + accelerator-types list to learn about all available accelerator + types. count (Optional) The number of accelerators to attach to the instances. @@ -1558,11 +1558,11 @@ FLAGS Resource limits are specified in the field 'resourceLimits'. Each resource limits definition contains three fields: resourceType, maximum and minimum. Resource type can be "cpu", "memory" or an - accelerator (e.g. "nvidia-tesla-k80" for nVidia Tesla K80). Use - gcloud compute accelerator-types list to learn about available - accelerator types. Maximum is the maximum allowed amount with the - unit of the resource. Minimum is the minimum allowed amount with - the unit of the resource. + accelerator (e.g. "nvidia-tesla-t4" for NVIDIA T4). Use gcloud + compute accelerator-types list to learn about available accelerator + types. Maximum is the maximum allowed amount with the unit of the + resource. Minimum is the minimum allowed amount with the unit of + the resource. Identity default contains at most one of the below fields: serviceAccount: The Google Cloud Platform Service Account to be @@ -1744,10 +1744,10 @@ FLAGS GPUs) in cluster. type - (Required) The specific type (e.g. nvidia-tesla-k80 for - nVidia Tesla K80) of accelerator for which the limit is - set. Use gcloud compute accelerator-types list to learn - about all available accelerator types. + (Required) The specific type (e.g. nvidia-tesla-t4 for + NVIDIA T4) of accelerator for which the limit is set. Use + gcloud compute accelerator-types list to learn about all + available accelerator types. count (Required) The maximum number of accelerators to which the @@ -1762,10 +1762,10 @@ FLAGS isn't set. type - (Required) The specific type (e.g. nvidia-tesla-k80 for - nVidia Tesla K80) of accelerator for which the limit is - set. Use gcloud compute accelerator-types list to learn - about all available accelerator types. + (Required) The specific type (e.g. nvidia-tesla-t4 for + NVIDIA T4) of accelerator for which the limit is set. Use + gcloud compute accelerator-types list to learn about all + available accelerator types. count (Required) The minimum number of accelerators to which the diff --git a/gcloud/beta/container/clusters/update b/gcloud/beta/container/clusters/update index 446b299d6..4aa5fb932 100644 --- a/gcloud/beta/container/clusters/update +++ b/gcloud/beta/container/clusters/update @@ -1112,8 +1112,8 @@ REQUIRED FLAGS Resource limits are specified in the field 'resourceLimits'. Each resource limits definition contains three fields: resourceType, maximum and minimum. Resource type can be "cpu", "memory" or an - accelerator (e.g. "nvidia-tesla-k80" for nVidia Tesla K80). Use - gcloud compute accelerator-types list to learn about available + accelerator (e.g. "nvidia-tesla-t4" for NVIDIA T4). Use gcloud + compute accelerator-types list to learn about available accelerator types. Maximum is the maximum allowed amount with the unit of the resource. Minimum is the minimum allowed amount with the unit of the resource. @@ -1294,10 +1294,10 @@ REQUIRED FLAGS GPUs) in cluster. type - (Required) The specific type (e.g. nvidia-tesla-k80 for - nVidia Tesla K80) of accelerator for which the limit is - set. Use gcloud compute accelerator-types list to learn - about all available accelerator types. + (Required) The specific type (e.g. nvidia-tesla-t4 for + NVIDIA T4) of accelerator for which the limit is set. Use + gcloud compute accelerator-types list to learn about all + available accelerator types. count (Required) The maximum number of accelerators to which @@ -1312,10 +1312,10 @@ REQUIRED FLAGS it isn't set. type - (Required) The specific type (e.g. nvidia-tesla-k80 for - nVidia Tesla K80) of accelerator for which the limit is - set. Use gcloud compute accelerator-types list to learn - about all available accelerator types. + (Required) The specific type (e.g. nvidia-tesla-t4 for + NVIDIA T4) of accelerator for which the limit is set. Use + gcloud compute accelerator-types list to learn about all + available accelerator types. count (Required) The minimum number of accelerators to which diff --git a/gcloud/beta/container/fleet/config-management/help b/gcloud/beta/container/fleet/config-management/help index c45de8ab6..923ec2f1b 100644 --- a/gcloud/beta/container/fleet/config-management/help +++ b/gcloud/beta/container/fleet/config-management/help @@ -7,10 +7,10 @@ SYNOPSIS [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) Manage Config Management Feature, which currently supports Config - Sync, Policy Controller, and Hierarchy Controller. Policy Controller users - should use the separate command group: gcloud container fleet - policycontroller. + (BETA) Manage Config Sync using the Config Management Feature. Policy + Controller users should use the separate command group: gcloud container + fleet policycontroller. Hierarchy Controller users should use + https://github.com/kubernetes-sigs/hierarchical-namespaces instead. GCLOUD WIDE FLAGS These flags are available to all commands: --help. diff --git a/gcloud/beta/container/hub/config-management/help b/gcloud/beta/container/hub/config-management/help index 64c1461cd..295e3298c 100644 --- a/gcloud/beta/container/hub/config-management/help +++ b/gcloud/beta/container/hub/config-management/help @@ -6,10 +6,10 @@ SYNOPSIS gcloud beta container hub config-management COMMAND [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) Manage Config Management Feature, which currently supports Config - Sync, Policy Controller, and Hierarchy Controller. Policy Controller users - should use the separate command group: gcloud container fleet - policycontroller. + (BETA) Manage Config Sync using the Config Management Feature. Policy + Controller users should use the separate command group: gcloud container + fleet policycontroller. Hierarchy Controller users should use + https://github.com/kubernetes-sigs/hierarchical-namespaces instead. GCLOUD WIDE FLAGS These flags are available to all commands: --help. diff --git a/gcloud/beta/container/node-pools/create b/gcloud/beta/container/node-pools/create index 9f3861674..ee9358680 100644 --- a/gcloud/beta/container/node-pools/create +++ b/gcloud/beta/container/node-pools/create @@ -99,10 +99,10 @@ FLAGS Attaches accelerators (e.g. GPUs) to all nodes. type - (Required) The specific type (e.g. nvidia-tesla-k80 for NVIDIA - Tesla K80) of accelerator to attach to the instances. Use gcloud - compute accelerator-types list to learn about all available - accelerator types. + (Required) The specific type (e.g. nvidia-tesla-t4 for NVIDIA T4) + of accelerator to attach to the instances. Use gcloud compute + accelerator-types list to learn about all available accelerator + types. count (Optional) The number of accelerators to attach to the instances. diff --git a/gcloud/beta/container/node-pools/update b/gcloud/beta/container/node-pools/update index 017ff5e10..696772380 100644 --- a/gcloud/beta/container/node-pools/update +++ b/gcloud/beta/container/node-pools/update @@ -13,6 +13,7 @@ SYNOPSIS | --node-labels=[NODE_LABEL,...] | --node-locations=ZONE,[ZONE,...] | --node-taints=[NODE_TAINT,...] | --resource-manager-tags=[KEY=VALUE,...] + | --storage-pools=STORAGE_POOL,[...] | --system-config-from-file=PATH_TO_FILE | --tags=[TAG,...] | --windows-os-version=WINDOWS_OS_VERSION | --workload-metadata=WORKLOAD_METADATA | --enable-blue-green-upgrade @@ -202,6 +203,14 @@ REQUIRED FLAGS policy rules. For instructions, see https://cloud.google.com/firewall/docs/use-tags-for-firewalls. + --storage-pools=STORAGE_POOL,[...] + A list of storage pools where the node pool's boot disks will be + provisioned. Replaces all the current storage pools of an existing + node pool, with the specified storage pools. + + STORAGE_POOL must be in the format + projects/project/zones/zone/storagePools/storagePool + --system-config-from-file=PATH_TO_FILE Path of the YAML/JSON file that contains the node configuration, including Linux kernel parameters (sysctls) and kubelet configs. diff --git a/gcloud/beta/dataproc/clusters/create b/gcloud/beta/dataproc/clusters/create index f1908d543..1b6dc6e58 100644 --- a/gcloud/beta/dataproc/clusters/create +++ b/gcloud/beta/dataproc/clusters/create @@ -138,7 +138,7 @@ FLAGS type The specific type of accelerator to attach to the instances, such - as nvidia-tesla-k80 for NVIDIA Tesla K80. Use gcloud compute + as nvidia-tesla-t4 for NVIDIA T4. Use gcloud compute accelerator-types list to display available accelerator types. count @@ -207,7 +207,7 @@ FLAGS type The specific type of accelerator to attach to the instances, such - as nvidia-tesla-k80 for NVIDIA Tesla K80. Use gcloud compute + as nvidia-tesla-t4 for NVIDIA T4. Use gcloud compute accelerator-types list to display available accelerator types. count @@ -334,7 +334,7 @@ FLAGS type The specific type of accelerator to attach to the instances, such - as nvidia-tesla-k80 for NVIDIA Tesla K80. Use gcloud compute + as nvidia-tesla-t4 for NVIDIA T4. Use gcloud compute accelerator-types list to display available accelerator types. count @@ -386,7 +386,7 @@ FLAGS type The specific type of accelerator to attach to the instances, such - as nvidia-tesla-k80 for NVIDIA Tesla K80. Use gcloud compute + as nvidia-tesla-t4 for NVIDIA T4. Use gcloud compute accelerator-types list to display available accelerator types. count diff --git a/gcloud/beta/dataproc/workflow-templates/set-managed-cluster b/gcloud/beta/dataproc/workflow-templates/set-managed-cluster index 111624788..0d0d1bbb7 100644 --- a/gcloud/beta/dataproc/workflow-templates/set-managed-cluster +++ b/gcloud/beta/dataproc/workflow-templates/set-managed-cluster @@ -147,7 +147,7 @@ FLAGS type The specific type of accelerator to attach to the instances, such - as nvidia-tesla-k80 for NVIDIA Tesla K80. Use gcloud compute + as nvidia-tesla-t4 for NVIDIA T4. Use gcloud compute accelerator-types list to display available accelerator types. count @@ -266,7 +266,7 @@ FLAGS type The specific type of accelerator to attach to the instances, such - as nvidia-tesla-k80 for NVIDIA Tesla K80. Use gcloud compute + as nvidia-tesla-t4 for NVIDIA T4. Use gcloud compute accelerator-types list to display available accelerator types. count @@ -318,7 +318,7 @@ FLAGS type The specific type of accelerator to attach to the instances, such - as nvidia-tesla-k80 for NVIDIA Tesla K80. Use gcloud compute + as nvidia-tesla-t4 for NVIDIA T4. Use gcloud compute accelerator-types list to display available accelerator types. count diff --git a/gcloud/beta/firestore/bulk-delete b/gcloud/beta/firestore/bulk-delete new file mode 100644 index 000000000..3d5c6fbe3 --- /dev/null +++ b/gcloud/beta/firestore/bulk-delete @@ -0,0 +1,70 @@ +NAME + gcloud beta firestore bulk-delete - bulk delete Cloud Firestore documents + +SYNOPSIS + gcloud beta firestore bulk-delete [--async] + [--collection-ids=[COLLECTION_IDS,...]] + [--database=DATABASE; default="(default)"] + [--namespace-ids=[NAMESPACE_IDS,...]] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) bulk delete Cloud Firestore documents. + +EXAMPLES + To bulk delete a specific set of collections groups asynchronously, run: + + $ gcloud beta firestore bulk-delete \ + --collection-ids='specific collection group1','specific + collection group2' --async + + To bulk delete all collection groups from certain namespace, run: + + $ gcloud beta firestore bulk-delete \ + --namespace-ids='specific namespace id' + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --collection-ids=[COLLECTION_IDS,...] + List specifying which collections will be included in the operation. + When omitted, all collections are included. + + For example, to operate on only the customers and orders collections: + + $ gcloud beta firestore bulk-delete \ + --collection-ids='customers','orders' + + --database=DATABASE; default="(default)" + The database to operate on. The default value is (default). + + For example, to operate on database foo: + + $ gcloud beta firestore bulk-delete --database='foo' + + --namespace-ids=[NAMESPACE_IDS,...] + List specifying which namespaces will be included in the operation. + When omitted, all namespaces are included. + + This is only supported for Datastore Mode databases. + + For example, to operate on only the customers and orders namespaces: + + $ gcloud beta firestore bulk-delete \ + --namespaces-ids='customers','orders' + +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 firestore bulk-delete + diff --git a/gcloud/beta/firestore/help b/gcloud/beta/firestore/help index 7b8a4b552..350c9f3ef 100644 --- a/gcloud/beta/firestore/help +++ b/gcloud/beta/firestore/help @@ -9,6 +9,8 @@ DESCRIPTION import -- Import data from Google Cloud Storage + bulk-delete -- Bulk delete documents from Cloud Firestore + indexes -- Manage your Cloud Firestore indexes operations -- Manage Long Running Operations for Cloud Firestore @@ -42,6 +44,9 @@ GROUPS COMMANDS COMMAND is one of the following: + bulk-delete + (BETA) bulk delete Cloud Firestore documents. + export (BETA) export Cloud Firestore documents to Google Cloud Storage. diff --git a/gcloud/beta/firestore/indexes/composite/create b/gcloud/beta/firestore/indexes/composite/create index a6ecfc9d3..245a391e7 100644 --- a/gcloud/beta/firestore/indexes/composite/create +++ b/gcloud/beta/firestore/indexes/composite/create @@ -5,7 +5,7 @@ NAME SYNOPSIS gcloud beta firestore indexes composite create --field-config=[array-config=ARRAY-CONFIG], - [field-path=FIELD-PATH],[order=ORDER] + [field-path=FIELD-PATH],[order=ORDER],[vector-config=VECTOR-CONFIG] (--collection-group=COLLECTION_GROUP : --database=DATABASE) [--api-scope=API_SCOPE; default="any-api"] [--async] [--query-scope=QUERY_SCOPE; default="collection"] @@ -30,31 +30,43 @@ EXAMPLES --field-config=field-path=timestamp,order=descending REQUIRED FLAGS - --field-config=[array-config=ARRAY-CONFIG],[field-path=FIELD-PATH],[order=ORDER] - Configuration for a field. + --field-config=[array-config=ARRAY-CONFIG],[field-path=FIELD-PATH],[order=ORDER],[vector-config=VECTOR-CONFIG] + Required, Configuration for an index field. - This flag must be repeated to provide the ordered list of field - configurations comprising the composite index. For example: - - $ gcloud beta firestore indexes composite create \ - --collection-group=Events \ - --field-config field-path=tags,array-config=contains \ - --field-config field-path=user_id,order=descending \ - --field-config field-path=timestamp,order=descending - - The following keys are allowed: + array-config + Specifies the configuration for an array field. The only valid + option is 'contains'. Exactly one of 'order', 'array-config', or + 'vector-config' must be specified. field-path Specifies the field path (e.g. 'address.city'). This is required. order - Specifies the order. Valid options are: 'ascending', 'descending'. - Exactly one of order or array-config must be specified. + Specifies the order. Valid options are 'ascending', 'descending'. + Exactly one of 'order', 'array-config', or 'vector-config' must be + specified. - array-config - Specifies the configuration for an array field. The only valid - option is 'contains'. Exactly one of 'order' or 'array-config' must - be specified. + vector-config + Specifies the configuration for a vector field. Exactly one of + 'order', 'array-config', or 'vector-config' must be specified. + + dimension + Sets dimension value. + + flat + Sets flat value. + + Shorthand Example: + + --field-config='array-config=string,field-path=string,order=string,vector-config={"dimension": int, "flat": {"string"}}' --field-config='array-config=string,field-path=string,order=string,vector-config={"dimension": int, "flat": {"string"}}' + + JSON Example: + + --field-config='[{"array-config": "string", "field-path": "string", "order": "string", "vector-config": {"dimension": int, "flat": {"string"}}}]' + + File Example: + + --field-config=path_to_file.(yaml|json) Collection group resource - Collection group of the index. The arguments in this group can be used to specify the attributes of this resource. diff --git a/gcloud/beta/iam/policy-bindings/create b/gcloud/beta/iam/policy-bindings/create index f72a69cac..f3032dbd6 100644 --- a/gcloud/beta/iam/policy-bindings/create +++ b/gcloud/beta/iam/policy-bindings/create @@ -28,18 +28,21 @@ EXAMPLES organizations/123 POSITIONAL ARGUMENTS - PolicyBinding resource - Identifier. The resource name of the policy - binding. The binding parent is the closest CRM resource (i.e., Project, - Folder or Organization) to the binding target. + PolicyBinding resource - Identifier. The name of the policy binding, in + the format + {binding_parent/locations/{location}/policyBindings/{policy_binding_id}. + The binding parent is the closest Resource Manager resource (i.e., + Project, Folder or Organization) to the binding target. Format: - projects/{project_id}/locations/{location}/policyBindings/{policy_binding_id} - projects/{project_number}/locations/{location}/policyBindings/{policy_binding_id} - folders/{folder_id}/locations/{location}/policyBindings/{policy_binding_id} - organizations/{organization_id}/locations/{location}/policyBindings/{policy_binding_id} - 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. + + ◆ projects/{project_id}/locations/{location}/policyBindings/{policy_binding_id} + ◆ projects/{project_number}/locations/{location}/policyBindings/{policy_binding_id} + ◆ folders/{folder_id}/locations/{location}/policyBindings/{policy_binding_id} + ◆ organizations/{organization_id}/locations/{location}/policyBindings/{policy_binding_id} + 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 policy_binding on the command line with a fully @@ -104,18 +107,20 @@ REQUIRED FLAGS --target-principal-set=TARGET_PRINCIPAL_SET Full Resource Name used for principal access boundary policy - bindings Examples: Organization: - "//cloudresourcemanager.googleapis.com/organizations/ORGANIZATION_ID" - Folder: "//cloudresourcemanager.googleapis.com/folders/FOLDER_ID" - Project: - "//cloudresourcemanager.googleapis.com/projects/PROJECT_NUMBER" - "//cloudresourcemanager.googleapis.com/projects/PROJECT_ID" - Workload Identity Pool: - "//iam.googleapis.com/projects/PROJECT_NUMBER/locations/LOCATION/workloadIdentityPools/WORKLOAD_POOL_ID" - Workforce Identity: - "//iam.googleapis.com/locations/global/workforcePools/WORKFORCE_POOL_ID" - Workspace Identity: - "//iam.googleapis.com/locations/global/workspace/WORKSPACE_ID" + bindings Examples: + + ▫ Organization: + //cloudresourcemanager.googleapis.com/organizations/ORGANIZATION_ID + ▫ Folder: //cloudresourcemanager.googleapis.com/folders/FOLDER_ID + ▫ Project: + ◇ //cloudresourcemanager.googleapis.com/projects/PROJECT_NUMBER + ◇ //cloudresourcemanager.googleapis.com/projects/PROJECT_ID + ▫ Workload Identity Pool: + //iam.googleapis.com/projects/PROJECT_NUMBER/locations/LOCATION/workloadIdentityPools/WORKLOAD_POOL_ID + ▫ Workforce Identity: + //iam.googleapis.com/locations/global/workforcePools/WORKFORCE_POOL_ID + ▫ Workspace Identity: + //iam.googleapis.com/locations/global/workspace/WORKSPACE_ID OPTIONAL FLAGS --annotations=[ANNOTATIONS,...] @@ -153,11 +158,11 @@ OPTIONAL FLAGS match the server's etag. --policy-kind=POLICY_KIND - The kind of the policy to attach in this binding: + The kind of the policy to attach in this binding. This field must be + one of the following: - + When the policy is empty, this field must be set. + When the policy - is set, this field + can be left empty and will be set to the policy - kind, or + must set to the input policy kind + ◆ Left empty (will be automatically set to the policy kind) + ◆ The input policy kind. POLICY_KIND must be (only one value is supported): diff --git a/gcloud/beta/iam/policy-bindings/delete b/gcloud/beta/iam/policy-bindings/delete index 9267dfa17..ce53325ed 100644 --- a/gcloud/beta/iam/policy-bindings/delete +++ b/gcloud/beta/iam/policy-bindings/delete @@ -5,7 +5,7 @@ SYNOPSIS gcloud beta iam policy-bindings delete (POLICY_BINDING : --folder=FOLDER --location=LOCATION --organization=ORGANIZATION) - [--async] [--etag=ETAG] [--validate-only] [GCLOUD_WIDE_FLAG ...] + [--async] [--etag=ETAG] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) Delete PolicyBinding instance. @@ -20,13 +20,14 @@ POSITIONAL ARGUMENTS PolicyBinding resource - The name of the policy binding to delete. Format: - projects/{project_id}/locations/{location}/policyBindings/{policy_binding_id} - projects/{project_number}/locations/{location}/policyBindings/{policy_binding_id} - folders/{folder_id}/locations/{location}/policyBindings/{policy_binding_id} - organizations/{organization_id}/locations/{location}/policyBindings/{policy_binding_id} - 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. + + ◆ projects/{project_id}/locations/{location}/policyBindings/{policy_binding_id} + ◆ projects/{project_number}/locations/{location}/policyBindings/{policy_binding_id} + ◆ folders/{folder_id}/locations/{location}/policyBindings/{policy_binding_id} + ◆ organizations/{organization_id}/locations/{location}/policyBindings/{policy_binding_id} + 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 policy_binding on the command line with a fully @@ -86,10 +87,6 @@ FLAGS The etag of the policy binding. If this is provided, it must match the server's etag. - --validate-only - If set, validate the request and preview the deletion, but do not - actually post it. - 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/policy-bindings/describe b/gcloud/beta/iam/policy-bindings/describe index fb1c32783..518373d61 100644 --- a/gcloud/beta/iam/policy-bindings/describe +++ b/gcloud/beta/iam/policy-bindings/describe @@ -21,13 +21,14 @@ POSITIONAL ARGUMENTS PolicyBinding resource - The name of the policy binding to retrieve. Format: - projects/{project_id}/locations/{location}/policyBindings/{policy_binding_id} - projects/{project_number}/locations/{location}/policyBindings/{policy_binding_id} - folders/{folder_id}/locations/{location}/policyBindings/{policy_binding_id} - organizations/{organization_id}/locations/{location}/policyBindings/{policy_binding_id} - 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. + + ◆ projects/{project_id}/locations/{location}/policyBindings/{policy_binding_id} + ◆ projects/{project_number}/locations/{location}/policyBindings/{policy_binding_id} + ◆ folders/{folder_id}/locations/{location}/policyBindings/{policy_binding_id} + ◆ organizations/{organization_id}/locations/{location}/policyBindings/{policy_binding_id} + 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 policy_binding on the command line with a fully diff --git a/gcloud/beta/iam/policy-bindings/list b/gcloud/beta/iam/policy-bindings/list index c7b11acc9..5a261cd4e 100644 --- a/gcloud/beta/iam/policy-bindings/list +++ b/gcloud/beta/iam/policy-bindings/list @@ -20,13 +20,15 @@ REQUIRED FLAGS Location resource - The parent resource, which owns the collection of policy bindings. - Format: projects/{project_id}/locations/{location} - projects/{project_number}/locations/{location} - folders/{folder_id}/locations/{location} - organizations/{organization_id}/locations/{location} 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. + Format: + + ◆ projects/{project_id}/locations/{location} + ◆ projects/{project_number}/locations/{location} + ◆ folders/{folder_id}/locations/{location} + ◆ organizations/{organization_id}/locations/{location} The arguments in + this group can be used to specify the attributes of this resource. + (NOTE) Some attributes are not given arguments in this group but can be + set in other ways. To set the project attribute: ◆ provide the argument --location on the command line with a fully diff --git a/gcloud/beta/iam/policy-bindings/search-target-policy-bindings b/gcloud/beta/iam/policy-bindings/search-target-policy-bindings index 9d3e4f06f..ca36a3acf 100644 --- a/gcloud/beta/iam/policy-bindings/search-target-policy-bindings +++ b/gcloud/beta/iam/policy-bindings/search-target-policy-bindings @@ -23,23 +23,28 @@ REQUIRED FLAGS --target=TARGET The target resource, which is bound to the policy in the binding. - Format: //iam.googleapis.com/locations/global/workforcePools/POOL_ID - //iam.googleapis.com/projects/PROJECT_NUMBER/locations/global/workloadIdentityPools/POOL_ID - //iam.googleapis.com/locations/global/workspace/WORKSPACE_ID - //cloudresourcemanager.googleapis.com/projects/{project_number} - //cloudresourcemanager.googleapis.com/folders/{folder_id} - //cloudresourcemanager.googleapis.com/organizations/{organization_id} + Format: + + ◆ //iam.googleapis.com/locations/global/workforcePools/POOL_ID + ◆ //iam.googleapis.com/projects/PROJECT_NUMBER/locations/global/workloadIdentityPools/POOL_ID + ◆ //iam.googleapis.com/locations/global/workspace/WORKSPACE_ID + ◆ //cloudresourcemanager.googleapis.com/projects/{project_number} + ◆ //cloudresourcemanager.googleapis.com/folders/{folder_id} + ◆ //cloudresourcemanager.googleapis.com/organizations/{organization_id} Location resource - The parent resource where this search will be - performed. This should be the nearest CRM resource to the target. + performed. This should be the nearest Resource Manager resource (project, + folder, or organization) to the target. - Format: projects/{project_id}/locations/{location} - projects/{project_number}/locations/{location} - folders/{folder_id}/locations/{location} - organizations/{organization_id}/locations/{location} 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. + Format: + + ◆ projects/{project_id}/locations/{location} + ◆ projects/{project_number}/locations/{location} + ◆ folders/{folder_id}/locations/{location} + ◆ organizations/{organization_id}/locations/{location} The arguments in + this group can be used to specify the attributes of this resource. + (NOTE) Some attributes are not given arguments in this group but can be + set in other ways. To set the project attribute: ◆ provide the argument --location on the command line with a fully diff --git a/gcloud/beta/iam/policy-bindings/update b/gcloud/beta/iam/policy-bindings/update index b9597d342..6366626fa 100644 --- a/gcloud/beta/iam/policy-bindings/update +++ b/gcloud/beta/iam/policy-bindings/update @@ -25,18 +25,21 @@ EXAMPLES --display-name=new-display-name POSITIONAL ARGUMENTS - PolicyBinding resource - Identifier. The resource name of the policy - binding. The binding parent is the closest CRM resource (i.e., Project, - Folder or Organization) to the binding target. + PolicyBinding resource - Identifier. The name of the policy binding, in + the format + {binding_parent/locations/{location}/policyBindings/{policy_binding_id}. + The binding parent is the closest Resource Manager resource (i.e., + Project, Folder or Organization) to the binding target. Format: - projects/{project_id}/locations/{location}/policyBindings/{policy_binding_id} - projects/{project_number}/locations/{location}/policyBindings/{policy_binding_id} - folders/{folder_id}/locations/{location}/policyBindings/{policy_binding_id} - organizations/{organization_id}/locations/{location}/policyBindings/{policy_binding_id} - 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. + + ◆ projects/{project_id}/locations/{location}/policyBindings/{policy_binding_id} + ◆ projects/{project_number}/locations/{location}/policyBindings/{policy_binding_id} + ◆ folders/{folder_id}/locations/{location}/policyBindings/{policy_binding_id} + ◆ organizations/{organization_id}/locations/{location}/policyBindings/{policy_binding_id} + 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 policy_binding on the command line with a fully @@ -107,7 +110,7 @@ FLAGS --annotations=[ANNOTATIONS,...] Set annotations to new value. User defined annotations. See https://google.aip.dev/148#annotations for more details such as - format and size limitations + format and size limitations. KEY Sets KEY value. @@ -130,7 +133,7 @@ FLAGS --update-annotations=[UPDATE_ANNOTATIONS,...] Update annotations value or add key value pair. User defined annotations. See https://google.aip.dev/148#annotations for more - details such as format and size limitations + details such as format and size limitations. KEY Sets KEY value. diff --git a/gcloud/beta/iam/principal-access-boundary-policies/create b/gcloud/beta/iam/principal-access-boundary-policies/create index 336dd4688..14011fab2 100644 --- a/gcloud/beta/iam/principal-access-boundary-policies/create +++ b/gcloud/beta/iam/principal-access-boundary-policies/create @@ -98,10 +98,8 @@ FLAGS Principal access boundary policy details --details-rules=[description=DESCRIPTION],[effect=EFFECT],[resources=RESOURCES] - A list of principal access boundary policy rules. The number of rules - in a policy is limited to 500. Required, A list of principal access - boundary policy rules. The number of rules in a policy is limited to - 500. + Required, A list of principal access boundary policy rules. The + number of rules in a policy is limited to 500. description The description of the principal access boundary policy rule. @@ -116,14 +114,15 @@ FLAGS the descendants are included. The number of resources in a policy is limited to 500 across all rules. - The following resource names are supported: - ▫ Organization, such as - "//cloudresourcemanager.googleapis.com/organizations/123". - ▫ Folder, such as - "//cloudresourcemanager.googleapis.com/folders/123". - ▫ Project, such as - "//cloudresourcemanager.googleapis.com/projects/123" or - "//cloudresourcemanager.googleapis.com/projects/my-project-id". + The following resource types are supported: + + ▫ Organizations, such as + //cloudresourcemanager.googleapis.com/organizations/123. + ▫ Folders, such as + //cloudresourcemanager.googleapis.com/folders/123. + ▫ Projects, such as + //cloudresourcemanager.googleapis.com/projects/123 or + //cloudresourcemanager.googleapis.com/projects/my-project-id. Shorthand Example: @@ -141,10 +140,10 @@ FLAGS this group are specified. --details-enforcement-version=DETAILS_ENFORCEMENT_VERSION - The version number that indicates which GCP services are included in - the enforcement (e.g. "latest", "1", ...). If empty, the PAB policy - version will be set to the current latest version, and this version - won't get updated when new versions are released. + The version number that indicates which Google Cloud services are + included in the enforcement (e.g. "latest", "1", ...). If empty, the + PAB policy version will be set to the current latest version, and + this version won't get updated when new versions are released. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/beta/iam/principal-access-boundary-policies/delete b/gcloud/beta/iam/principal-access-boundary-policies/delete index 36a690db1..2f8e81826 100644 --- a/gcloud/beta/iam/principal-access-boundary-policies/delete +++ b/gcloud/beta/iam/principal-access-boundary-policies/delete @@ -6,7 +6,7 @@ SYNOPSIS gcloud beta iam principal-access-boundary-policies delete (PRINCIPAL_ACCESS_BOUNDARY_POLICY : --location=LOCATION --organization=ORGANIZATION) [--async] - [--etag=ETAG] [--force] [--validate-only] [GCLOUD_WIDE_FLAG ...] + [--etag=ETAG] [--force] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) Delete PrincipalAccessBoundaryPolicy instance. @@ -68,10 +68,6 @@ FLAGS If set to true, the request will force the deletion of the Policy even if the Policy references PolicyBindings. - --validate-only - If set, validate the request and preview the deletion, but do not - actually post it. - 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/principal-access-boundary-policies/update b/gcloud/beta/iam/principal-access-boundary-policies/update index c96a19fd3..52fa0ebb1 100644 --- a/gcloud/beta/iam/principal-access-boundary-policies/update +++ b/gcloud/beta/iam/principal-access-boundary-policies/update @@ -86,7 +86,7 @@ FLAGS --annotations=[ANNOTATIONS,...] Set annotations to new value. User defined annotations. See https://google.aip.dev/148#annotations for more details such as - format and size limitations + format and size limitations. KEY Sets KEY value. @@ -109,7 +109,7 @@ FLAGS --update-annotations=[UPDATE_ANNOTATIONS,...] Update annotations value or add key value pair. User defined annotations. See https://google.aip.dev/148#annotations for more - details such as format and size limitations + details such as format and size limitations. KEY Sets KEY value. @@ -140,10 +140,10 @@ FLAGS Principal access boundary policy details --details-enforcement-version=DETAILS_ENFORCEMENT_VERSION - The version number that indicates which GCP services are included in - the enforcement (e.g. "latest", "1", ...). If empty, the PAB policy - version will be set to the current latest version, and this version - won't get updated when new versions are released. + The version number that indicates which Google Cloud services are + included in the enforcement (e.g. "latest", "1", ...). If empty, the + PAB policy version will be set to the current latest version, and + this version won't get updated when new versions are released. Update details_rules. @@ -166,14 +166,15 @@ FLAGS all the descendants are included. The number of resources in a policy is limited to 500 across all rules. - The following resource names are supported: - ◇ Organization, such as - "//cloudresourcemanager.googleapis.com/organizations/123". - ◇ Folder, such as - "//cloudresourcemanager.googleapis.com/folders/123". - ◇ Project, such as - "//cloudresourcemanager.googleapis.com/projects/123" or - "//cloudresourcemanager.googleapis.com/projects/my-project-id". + The following resource types are supported: + + ◇ Organizations, such as + //cloudresourcemanager.googleapis.com/organizations/123. + ◇ Folders, such as + //cloudresourcemanager.googleapis.com/folders/123. + ◇ Projects, such as + //cloudresourcemanager.googleapis.com/projects/123 or + //cloudresourcemanager.googleapis.com/projects/my-project-id. Shorthand Example: @@ -205,14 +206,15 @@ FLAGS all the descendants are included. The number of resources in a policy is limited to 500 across all rules. - The following resource names are supported: - ◇ Organization, such as - "//cloudresourcemanager.googleapis.com/organizations/123". - ◇ Folder, such as - "//cloudresourcemanager.googleapis.com/folders/123". - ◇ Project, such as - "//cloudresourcemanager.googleapis.com/projects/123" or - "//cloudresourcemanager.googleapis.com/projects/my-project-id". + The following resource types are supported: + + ◇ Organizations, such as + //cloudresourcemanager.googleapis.com/organizations/123. + ◇ Folders, such as + //cloudresourcemanager.googleapis.com/folders/123. + ◇ Projects, such as + //cloudresourcemanager.googleapis.com/projects/123 or + //cloudresourcemanager.googleapis.com/projects/my-project-id. Shorthand Example: @@ -249,14 +251,15 @@ FLAGS all the descendants are included. The number of resources in a policy is limited to 500 across all rules. - The following resource names are supported: - ▹ Organization, such as - "//cloudresourcemanager.googleapis.com/organizations/123". - ▹ Folder, such as - "//cloudresourcemanager.googleapis.com/folders/123". - ▹ Project, such as - "//cloudresourcemanager.googleapis.com/projects/123" or - "//cloudresourcemanager.googleapis.com/projects/my-project-id". + The following resource types are supported: + + ▹ Organizations, such as + //cloudresourcemanager.googleapis.com/organizations/123. + ▹ Folders, such as + //cloudresourcemanager.googleapis.com/folders/123. + ▹ Projects, such as + //cloudresourcemanager.googleapis.com/projects/123 or + //cloudresourcemanager.googleapis.com/projects/my-project-id. Shorthand Example: diff --git a/gcloud/beta/managed-kafka/clusters/create b/gcloud/beta/managed-kafka/clusters/create index 5ad80cf83..fa304e463 100644 --- a/gcloud/beta/managed-kafka/clusters/create +++ b/gcloud/beta/managed-kafka/clusters/create @@ -1,6 +1,6 @@ NAME - gcloud beta managed-kafka clusters create - create an Apache Kafka for - BigQuery cluster + gcloud beta managed-kafka clusters create - create a Managed Service for + Apache Kafka cluster SYNOPSIS gcloud beta managed-kafka clusters create (CLUSTER : --location=LOCATION) @@ -9,7 +9,7 @@ SYNOPSIS [--labels=[KEY=VALUE,...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) Create an Apache Kafka for BigQuery cluster. + (BETA) Create a Managed Service for Apache Kafka cluster. EXAMPLES To create a cluster, run the following: @@ -43,9 +43,9 @@ POSITIONAL ARGUMENTS arguments in this group are specified. --location=LOCATION - ID of the location of the Apache Kafka for BigQuery resource. See - https://cloud.google.com/managed-kafka/docs/locations for a list of - supported locations. + ID of the location of the Managed Service for Apache Kafka resource. + See https://cloud.google.com/managed-kafka/docs/locations for a list + of supported locations. To set the location attribute: ▸ provide the argument cluster on the command line with a fully diff --git a/gcloud/beta/managed-kafka/clusters/delete b/gcloud/beta/managed-kafka/clusters/delete index 3f67aace4..ddd5fef26 100644 --- a/gcloud/beta/managed-kafka/clusters/delete +++ b/gcloud/beta/managed-kafka/clusters/delete @@ -1,13 +1,13 @@ NAME - gcloud beta managed-kafka clusters delete - delete an Apache Kafka for - BigQuery cluster + gcloud beta managed-kafka clusters delete - delete a Managed Service for + Apache Kafka cluster SYNOPSIS gcloud beta managed-kafka clusters delete (CLUSTER : --location=LOCATION) [--async] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) Delete an Apache Kafka for BigQuery cluster. + (BETA) Delete a Managed Service for Apache Kafka cluster. EXAMPLES To delete a cluster named mycluster located in us-central1, run the @@ -40,9 +40,9 @@ POSITIONAL ARGUMENTS arguments in this group are specified. --location=LOCATION - ID of the location of the Apache Kafka for BigQuery resource. See - https://cloud.google.com/managed-kafka/docs/locations for a list of - supported locations. + ID of the location of the Managed Service for Apache Kafka resource. + See https://cloud.google.com/managed-kafka/docs/locations for a list + of supported locations. To set the location attribute: ▸ provide the argument cluster on the command line with a fully diff --git a/gcloud/beta/managed-kafka/clusters/describe b/gcloud/beta/managed-kafka/clusters/describe index 2b80f64e2..eeabc7789 100644 --- a/gcloud/beta/managed-kafka/clusters/describe +++ b/gcloud/beta/managed-kafka/clusters/describe @@ -1,13 +1,13 @@ NAME - gcloud beta managed-kafka clusters describe - describe an Apache Kafka for - BigQuery cluster + gcloud beta managed-kafka clusters describe - describe a Managed Service + for Apache Kafka cluster SYNOPSIS gcloud beta managed-kafka clusters describe (CLUSTER : --location=LOCATION) [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) Describe an Apache Kafka for BigQuery cluster. + (BETA) Describe a Managed Service for Apache Kafka cluster. EXAMPLES To describe a cluster named mycluster located in us-central1, run the @@ -40,9 +40,9 @@ POSITIONAL ARGUMENTS arguments in this group are specified. --location=LOCATION - ID of the location of the Apache Kafka for BigQuery resource. See - https://cloud.google.com/managed-kafka/docs/locations for a list of - supported locations. + ID of the location of the Managed Service for Apache Kafka resource. + See https://cloud.google.com/managed-kafka/docs/locations for a list + of supported locations. To set the location attribute: ▸ provide the argument cluster on the command line with a fully diff --git a/gcloud/beta/managed-kafka/clusters/help b/gcloud/beta/managed-kafka/clusters/help index 70122af25..6800d36e0 100644 --- a/gcloud/beta/managed-kafka/clusters/help +++ b/gcloud/beta/managed-kafka/clusters/help @@ -1,12 +1,12 @@ NAME - gcloud beta managed-kafka clusters - administer Apache Kafka for BigQuery - clusters + gcloud beta managed-kafka clusters - administer Managed Service for Apache + Kafka clusters SYNOPSIS gcloud beta managed-kafka clusters COMMAND [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) Administer Apache Kafka for BigQuery clusters. + (BETA) Administer Managed Service for Apache Kafka clusters. GCLOUD WIDE FLAGS These flags are available to all commands: --help. @@ -17,19 +17,20 @@ COMMANDS COMMAND is one of the following: create - (BETA) Create an Apache Kafka for BigQuery cluster. + (BETA) Create a Managed Service for Apache Kafka cluster. delete - (BETA) Delete an Apache Kafka for BigQuery cluster. + (BETA) Delete a Managed Service for Apache Kafka cluster. describe - (BETA) Describe an Apache Kafka for BigQuery cluster. + (BETA) Describe a Managed Service for Apache Kafka cluster. list - (BETA) List all Apache Kafka for BigQuery clusters in a given location. + (BETA) List all Managed Service for Apache Kafka clusters in a given + location. update - (BETA) Update an Apache Kafka for BigQuery cluster. + (BETA) Update a Managed Service for Apache Kafka cluster. NOTES This command is currently in beta and might change without notice. This diff --git a/gcloud/beta/managed-kafka/clusters/list b/gcloud/beta/managed-kafka/clusters/list index 790a05173..ea5f3b68e 100644 --- a/gcloud/beta/managed-kafka/clusters/list +++ b/gcloud/beta/managed-kafka/clusters/list @@ -1,6 +1,6 @@ NAME - gcloud beta managed-kafka clusters list - list all Apache Kafka for - BigQuery clusters in a given location + gcloud beta managed-kafka clusters list - list all Managed Service for + Apache Kafka clusters in a given location SYNOPSIS gcloud beta managed-kafka clusters list --location=LOCATION diff --git a/gcloud/beta/managed-kafka/clusters/update b/gcloud/beta/managed-kafka/clusters/update index ec38d71f6..c53fa406c 100644 --- a/gcloud/beta/managed-kafka/clusters/update +++ b/gcloud/beta/managed-kafka/clusters/update @@ -1,6 +1,6 @@ NAME - gcloud beta managed-kafka clusters update - update an Apache Kafka for - BigQuery cluster + gcloud beta managed-kafka clusters update - update a Managed Service for + Apache Kafka cluster SYNOPSIS gcloud beta managed-kafka clusters update (CLUSTER : --location=LOCATION) @@ -9,7 +9,7 @@ SYNOPSIS [--async] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) Update an Apache Kafka for BigQuery cluster. + (BETA) Update a Managed Service for Apache Kafka cluster. EXAMPLES To update an attribute in a cluster named mycluster located in us-central1, @@ -42,9 +42,9 @@ POSITIONAL ARGUMENTS arguments in this group are specified. --location=LOCATION - ID of the location of the Apache Kafka for BigQuery resource. See - https://cloud.google.com/managed-kafka/docs/locations for a list of - supported locations. + ID of the location of the Managed Service for Apache Kafka resource. + See https://cloud.google.com/managed-kafka/docs/locations for a list + of supported locations. To set the location attribute: ▸ provide the argument cluster on the command line with a fully diff --git a/gcloud/beta/managed-kafka/consumer-groups/delete b/gcloud/beta/managed-kafka/consumer-groups/delete index 47ba323d7..596db901c 100644 --- a/gcloud/beta/managed-kafka/consumer-groups/delete +++ b/gcloud/beta/managed-kafka/consumer-groups/delete @@ -1,6 +1,6 @@ NAME - gcloud beta managed-kafka consumer-groups delete - delete an Apache Kafka - for BigQuery consumer group + gcloud beta managed-kafka consumer-groups delete - delete a Managed Service + for Apache Kafka consumer group SYNOPSIS gcloud beta managed-kafka consumer-groups delete @@ -8,7 +8,7 @@ SYNOPSIS [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) Delete an Apache Kafka for BigQuery consumer group. + (BETA) Delete a Managed Service for Apache Kafka consumer group. EXAMPLES To delete a consumer group in a cluster named mycluster located in @@ -50,9 +50,9 @@ POSITIONAL ARGUMENTS ▸ provide the argument --cluster on the command line. --location=LOCATION - ID of the location of the Apache Kafka for BigQuery resource. See - https://cloud.google.com/managed-kafka/docs/locations for a list of - supported locations. + ID of the location of the Managed Service for Apache Kafka resource. + See https://cloud.google.com/managed-kafka/docs/locations for a list + of supported locations. To set the location attribute: ▸ provide the argument consumer_group on the command line with a diff --git a/gcloud/beta/managed-kafka/consumer-groups/describe b/gcloud/beta/managed-kafka/consumer-groups/describe index 03da2364c..665fa2d1c 100644 --- a/gcloud/beta/managed-kafka/consumer-groups/describe +++ b/gcloud/beta/managed-kafka/consumer-groups/describe @@ -1,6 +1,6 @@ NAME - gcloud beta managed-kafka consumer-groups describe - describe an Apache - Kafka for BigQuery consumer group + gcloud beta managed-kafka consumer-groups describe - describe a Managed + Service for Apache Kafka consumer group SYNOPSIS gcloud beta managed-kafka consumer-groups describe @@ -8,7 +8,7 @@ SYNOPSIS [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) Describe an Apache Kafka for BigQuery consumer group. + (BETA) Describe a Managed Service for Apache Kafka consumer group. EXAMPLES To describe a consumer group in a cluster named mycluster located in @@ -50,9 +50,9 @@ POSITIONAL ARGUMENTS ▸ provide the argument --cluster on the command line. --location=LOCATION - ID of the location of the Apache Kafka for BigQuery resource. See - https://cloud.google.com/managed-kafka/docs/locations for a list of - supported locations. + ID of the location of the Managed Service for Apache Kafka resource. + See https://cloud.google.com/managed-kafka/docs/locations for a list + of supported locations. To set the location attribute: ▸ provide the argument consumer_group on the command line with a diff --git a/gcloud/beta/managed-kafka/consumer-groups/help b/gcloud/beta/managed-kafka/consumer-groups/help index f3c8d5867..9e364b920 100644 --- a/gcloud/beta/managed-kafka/consumer-groups/help +++ b/gcloud/beta/managed-kafka/consumer-groups/help @@ -1,12 +1,12 @@ NAME - gcloud beta managed-kafka consumer-groups - administer Apache Kafka for - BigQuery consumer groups + gcloud beta managed-kafka consumer-groups - administer Managed Service for + Apache Kafka consumer groups SYNOPSIS gcloud beta managed-kafka consumer-groups COMMAND [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) Administer Apache Kafka for BigQuery consumer groups. + (BETA) Administer Managed Service for Apache Kafka consumer groups. GCLOUD WIDE FLAGS These flags are available to all commands: --help. @@ -17,17 +17,17 @@ COMMANDS COMMAND is one of the following: delete - (BETA) Delete an Apache Kafka for BigQuery consumer group. + (BETA) Delete a Managed Service for Apache Kafka consumer group. describe - (BETA) Describe an Apache Kafka for BigQuery consumer group. + (BETA) Describe a Managed Service for Apache Kafka consumer group. list - (BETA) List all Apache Kafka for BigQuery consumer groups in a given - cluster and location. + (BETA) List all Managed Service for Apache Kafka consumer groups in a + given cluster and location. update - (BETA) Update an Apache Kafka for BigQuery consumer group. + (BETA) Update a Managed Service for Apache Kafka consumer group. NOTES This command is currently in beta and might change without notice. This diff --git a/gcloud/beta/managed-kafka/consumer-groups/list b/gcloud/beta/managed-kafka/consumer-groups/list index 9330e7734..89d0e29c0 100644 --- a/gcloud/beta/managed-kafka/consumer-groups/list +++ b/gcloud/beta/managed-kafka/consumer-groups/list @@ -1,6 +1,6 @@ NAME - gcloud beta managed-kafka consumer-groups list - list all Apache Kafka for - BigQuery consumer groups in a given cluster and location + gcloud beta managed-kafka consumer-groups list - list all Managed Service + for Apache Kafka consumer groups in a given cluster and location SYNOPSIS gcloud beta managed-kafka consumer-groups list @@ -8,7 +8,7 @@ SYNOPSIS [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) List all Apache Kafka for BigQuery consumer groups in a given + (BETA) List all Managed Service for Apache Kafka consumer groups in a given cluster and location. To specify the maximum number of consumer groups to list, use the --limit flag. @@ -43,9 +43,9 @@ POSITIONAL ARGUMENTS arguments in this group are specified. --location=LOCATION - ID of the location of the Apache Kafka for BigQuery resource. See - https://cloud.google.com/managed-kafka/docs/locations for a list of - supported locations. + ID of the location of the Managed Service for Apache Kafka resource. + See https://cloud.google.com/managed-kafka/docs/locations for a list + of supported locations. To set the location attribute: ▸ provide the argument cluster on the command line with a fully diff --git a/gcloud/beta/managed-kafka/consumer-groups/update b/gcloud/beta/managed-kafka/consumer-groups/update index c96bb35b2..3d1c76f7d 100644 --- a/gcloud/beta/managed-kafka/consumer-groups/update +++ b/gcloud/beta/managed-kafka/consumer-groups/update @@ -1,6 +1,6 @@ NAME - gcloud beta managed-kafka consumer-groups update - update an Apache Kafka - for BigQuery consumer group + gcloud beta managed-kafka consumer-groups update - update a Managed Service + for Apache Kafka consumer group SYNOPSIS gcloud beta managed-kafka consumer-groups update @@ -8,7 +8,7 @@ SYNOPSIS --topics-file=JSON|YAML|FILE [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) Update an Apache Kafka for BigQuery consumer group. + (BETA) Update a Managed Service for Apache Kafka consumer group. EXAMPLES To specify a file for updating the topics of a consumer group, run the @@ -60,9 +60,9 @@ POSITIONAL ARGUMENTS ▸ provide the argument --cluster on the command line. --location=LOCATION - ID of the location of the Apache Kafka for BigQuery resource. See - https://cloud.google.com/managed-kafka/docs/locations for a list of - supported locations. + ID of the location of the Managed Service for Apache Kafka resource. + See https://cloud.google.com/managed-kafka/docs/locations for a list + of supported locations. To set the location attribute: ▸ provide the argument consumer_group on the command line with a diff --git a/gcloud/beta/managed-kafka/help b/gcloud/beta/managed-kafka/help index 07ed0d679..e24f78175 100644 --- a/gcloud/beta/managed-kafka/help +++ b/gcloud/beta/managed-kafka/help @@ -1,13 +1,13 @@ NAME - gcloud beta managed-kafka - administer Apache Kafka for BigQuery clusters, - topics, and consumer groups + gcloud beta managed-kafka - administer Managed Service for Apache Kafka + clusters, topics, and consumer groups SYNOPSIS gcloud beta managed-kafka GROUP [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) Administer Apache Kafka for BigQuery clusters, topics, and consumer - groups. + (BETA) Administer Managed Service for Apache Kafka clusters, topics, and + consumer groups. GCLOUD WIDE FLAGS These flags are available to all commands: --help. @@ -18,13 +18,13 @@ GROUPS GROUP is one of the following: clusters - (BETA) Administer Apache Kafka for BigQuery clusters. + (BETA) Administer Managed Service for Apache Kafka clusters. consumer-groups - (BETA) Administer Apache Kafka for BigQuery consumer groups. + (BETA) Administer Managed Service for Apache Kafka consumer groups. topics - (BETA) Administer Apache Kafka for BigQuery topics. + (BETA) Administer Managed Service for Apache Kafka topics. NOTES This command is currently in beta and might change without notice. This diff --git a/gcloud/beta/managed-kafka/topics/create b/gcloud/beta/managed-kafka/topics/create index a902a619b..b1a6f27af 100644 --- a/gcloud/beta/managed-kafka/topics/create +++ b/gcloud/beta/managed-kafka/topics/create @@ -1,6 +1,6 @@ NAME - gcloud beta managed-kafka topics create - create an Apache Kafka for - BigQuery topic + gcloud beta managed-kafka topics create - create a Managed Service for + Apache Kafka topic SYNOPSIS gcloud beta managed-kafka topics create @@ -9,7 +9,7 @@ SYNOPSIS [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) Create an Apache Kafka for BigQuery topic. + (BETA) Create a Managed Service for Apache Kafka topic. EXAMPLES To create a topic in a cluster named mycluster located in us-central1, run @@ -51,9 +51,9 @@ POSITIONAL ARGUMENTS ▸ provide the argument --cluster on the command line. --location=LOCATION - ID of the location of the Apache Kafka for BigQuery resource. See - https://cloud.google.com/managed-kafka/docs/locations for a list of - supported locations. + ID of the location of the Managed Service for Apache Kafka resource. + See https://cloud.google.com/managed-kafka/docs/locations for a list + of supported locations. To set the location attribute: ▸ provide the argument topic on the command line with a fully diff --git a/gcloud/beta/managed-kafka/topics/delete b/gcloud/beta/managed-kafka/topics/delete index c6f63c1e6..baad6e5a9 100644 --- a/gcloud/beta/managed-kafka/topics/delete +++ b/gcloud/beta/managed-kafka/topics/delete @@ -1,13 +1,13 @@ NAME - gcloud beta managed-kafka topics delete - delete an Apache Kafka for - BigQuery topic + gcloud beta managed-kafka topics delete - delete a Managed Service for + Apache Kafka topic SYNOPSIS gcloud beta managed-kafka topics delete (TOPIC : --cluster=CLUSTER --location=LOCATION) [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) Delete an Apache Kafka for BigQuery topic. + (BETA) Delete a Managed Service for Apache Kafka topic. EXAMPLES To delete a topic in a cluster named mycluster located in us-central1, run @@ -48,9 +48,9 @@ POSITIONAL ARGUMENTS ▸ provide the argument --cluster on the command line. --location=LOCATION - ID of the location of the Apache Kafka for BigQuery resource. See - https://cloud.google.com/managed-kafka/docs/locations for a list of - supported locations. + ID of the location of the Managed Service for Apache Kafka resource. + See https://cloud.google.com/managed-kafka/docs/locations for a list + of supported locations. To set the location attribute: ▸ provide the argument topic on the command line with a fully diff --git a/gcloud/beta/managed-kafka/topics/describe b/gcloud/beta/managed-kafka/topics/describe index 422a3ce3e..93d307fa4 100644 --- a/gcloud/beta/managed-kafka/topics/describe +++ b/gcloud/beta/managed-kafka/topics/describe @@ -1,13 +1,13 @@ NAME - gcloud beta managed-kafka topics describe - describe an Apache Kafka for - BigQuery topic + gcloud beta managed-kafka topics describe - describe a Managed Service for + Apache Kafka topic SYNOPSIS gcloud beta managed-kafka topics describe (TOPIC : --cluster=CLUSTER --location=LOCATION) [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) Describe an Apache Kafka for BigQuery topic. + (BETA) Describe a Managed Service for Apache Kafka topic. EXAMPLES To describe a topic in a cluster named mycluster located in us-central1, @@ -48,9 +48,9 @@ POSITIONAL ARGUMENTS ▸ provide the argument --cluster on the command line. --location=LOCATION - ID of the location of the Apache Kafka for BigQuery resource. See - https://cloud.google.com/managed-kafka/docs/locations for a list of - supported locations. + ID of the location of the Managed Service for Apache Kafka resource. + See https://cloud.google.com/managed-kafka/docs/locations for a list + of supported locations. To set the location attribute: ▸ provide the argument topic on the command line with a fully diff --git a/gcloud/beta/managed-kafka/topics/help b/gcloud/beta/managed-kafka/topics/help index 27d2967ee..171019311 100644 --- a/gcloud/beta/managed-kafka/topics/help +++ b/gcloud/beta/managed-kafka/topics/help @@ -1,12 +1,12 @@ NAME - gcloud beta managed-kafka topics - administer Apache Kafka for BigQuery - topics + gcloud beta managed-kafka topics - administer Managed Service for Apache + Kafka topics SYNOPSIS gcloud beta managed-kafka topics COMMAND [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) Administer Apache Kafka for BigQuery topics. + (BETA) Administer Managed Service for Apache Kafka topics. GCLOUD WIDE FLAGS These flags are available to all commands: --help. @@ -17,19 +17,20 @@ COMMANDS COMMAND is one of the following: create - (BETA) Create an Apache Kafka for BigQuery topic. + (BETA) Create a Managed Service for Apache Kafka topic. delete - (BETA) Delete an Apache Kafka for BigQuery topic. + (BETA) Delete a Managed Service for Apache Kafka topic. describe - (BETA) Describe an Apache Kafka for BigQuery topic. + (BETA) Describe a Managed Service for Apache Kafka topic. list - (BETA) List all Apache Kafka for BigQuery topics in a given cluster. + (BETA) List all Managed Service for Apache Kafka topics in a given + cluster. update - (BETA) Update an Apache Kafka for BigQuery topic. + (BETA) Update a Managed Service for Apache Kafka topic. NOTES This command is currently in beta and might change without notice. This diff --git a/gcloud/beta/managed-kafka/topics/list b/gcloud/beta/managed-kafka/topics/list index 9ea401e2f..95029bbb4 100644 --- a/gcloud/beta/managed-kafka/topics/list +++ b/gcloud/beta/managed-kafka/topics/list @@ -1,6 +1,6 @@ NAME - gcloud beta managed-kafka topics list - list all Apache Kafka for BigQuery - topics in a given cluster + gcloud beta managed-kafka topics list - list all Managed Service for Apache + Kafka topics in a given cluster SYNOPSIS gcloud beta managed-kafka topics list (CLUSTER : --location=LOCATION) @@ -8,8 +8,8 @@ SYNOPSIS [--sort-by=[FIELD,...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) List all Apache Kafka for BigQuery topics in a given cluster. To - specify the maximum number of topics to list, use the --limit flag. + (BETA) List all Managed Service for Apache Kafka topics in a given cluster. + To specify the maximum number of topics to list, use the --limit flag. EXAMPLES To list all topics in a cluster named mycluster located in us-central1, run @@ -42,9 +42,9 @@ POSITIONAL ARGUMENTS arguments in this group are specified. --location=LOCATION - ID of the location of the Apache Kafka for BigQuery resource. See - https://cloud.google.com/managed-kafka/docs/locations for a list of - supported locations. + ID of the location of the Managed Service for Apache Kafka resource. + See https://cloud.google.com/managed-kafka/docs/locations for a list + of supported locations. To set the location attribute: ▸ provide the argument cluster on the command line with a fully diff --git a/gcloud/beta/managed-kafka/topics/update b/gcloud/beta/managed-kafka/topics/update index 6df8cf47c..81181636c 100644 --- a/gcloud/beta/managed-kafka/topics/update +++ b/gcloud/beta/managed-kafka/topics/update @@ -1,6 +1,6 @@ NAME - gcloud beta managed-kafka topics update - update an Apache Kafka for - BigQuery topic + gcloud beta managed-kafka topics update - update a Managed Service for + Apache Kafka topic SYNOPSIS gcloud beta managed-kafka topics update @@ -9,7 +9,7 @@ SYNOPSIS [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) Update an Apache Kafka for BigQuery topic. + (BETA) Update a Managed Service for Apache Kafka topic. EXAMPLES To update an attribute in a topic, such as the partitions, for a cluster @@ -50,9 +50,9 @@ POSITIONAL ARGUMENTS ▸ provide the argument --cluster on the command line. --location=LOCATION - ID of the location of the Apache Kafka for BigQuery resource. See - https://cloud.google.com/managed-kafka/docs/locations for a list of - supported locations. + ID of the location of the Managed Service for Apache Kafka resource. + See https://cloud.google.com/managed-kafka/docs/locations for a list + of supported locations. To set the location attribute: ▸ provide the argument topic on the command line with a fully diff --git a/gcloud/beta/network-security/help b/gcloud/beta/network-security/help index 0c76dd4d8..13444e442 100644 --- a/gcloud/beta/network-security/help +++ b/gcloud/beta/network-security/help @@ -37,7 +37,10 @@ GROUPS (BETA) Manage Mirroring Deployment Group resources. mirroring-deployments - (BETA) Manage Mirroing Deployment resources. + (BETA) Manage Mirroring Deployment resources. + + mirroring-endpoint-group-associations + (BETA) Manage Mirroring Endpoint Group Association resources. mirroring-endpoint-groups (BETA) Manage Mirroring Endpoint Group resources. diff --git a/gcloud/beta/network-security/mirroring-deployments/help b/gcloud/beta/network-security/mirroring-deployments/help index 584d59a75..9856047b9 100644 --- a/gcloud/beta/network-security/mirroring-deployments/help +++ b/gcloud/beta/network-security/mirroring-deployments/help @@ -1,5 +1,5 @@ NAME - gcloud beta network-security mirroring-deployments - manage Mirroing + gcloud beta network-security mirroring-deployments - manage Mirroring Deployment resources SYNOPSIS diff --git a/gcloud/beta/network-security/mirroring-endpoint-group-associations/create b/gcloud/beta/network-security/mirroring-endpoint-group-associations/create new file mode 100644 index 000000000..63cd8ad98 --- /dev/null +++ b/gcloud/beta/network-security/mirroring-endpoint-group-associations/create @@ -0,0 +1,170 @@ +NAME + gcloud beta network-security mirroring-endpoint-group-associations create - + create a Mirroring Endpoint Group Association + +SYNOPSIS + gcloud beta network-security mirroring-endpoint-group-associations create + (MIRRORING_ENDPOINT_GROUP_ASSOCIATION : --location=LOCATION) + --network=NETWORK + (--mirroring-endpoint-group=MIRRORING_ENDPOINT_GROUP + : --mirroring-endpoint-group-location=MIRRORING_ENDPOINT_GROUP_LOCATION) + [--async] [--labels=[KEY=VALUE,...]] + [--max-wait=MAX_WAIT; default="20m"] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Create a mirroring endpoint group association. Successful creation + of an association results in an association in ACTIVE state. Check the + progress of association creation by using gcloud network-security + mirroring-endpoint-group-associations list. + + For more examples, refer to the EXAMPLES section below. + +EXAMPLES + To create a mirroring endpoint group association called my-association, in + project ID my-project, run: + + $ gcloud beta network-security \ mirroring-endpoint-group-associations create my-association \ + --project=my-project --location=global \ + --mirroring-endpoint-group=my-endpoint-group \ + --network=my-network + + OR + + $ gcloud beta network-security \ mirroring-endpoint-group-associations create my-association \ + --project=my-project --location=global \ + --mirroring-endpoint-group=my-endpoint-group \ + --network=projects/my-project/global/networks/my-network + + OR + + $ gcloud beta network-security \ mirroring-endpoint-group-associations create \ + projects/my-project/locations/global/\ + mirroringEndpointGroupAssociations/my-association \ + --mirroring-endpoint-group=projects/my-project/locations/\ + global/mirroringEndpointGroups/my-endpoint-group \ + --network=projects/my-project/global/networks/my-network + +POSITIONAL ARGUMENTS + Mirroring endpoint group association resource - Mirroring Endpoint Group + Association. 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 MIRRORING_ENDPOINT_GROUP_ASSOCIATION 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. + + MIRRORING_ENDPOINT_GROUP_ASSOCIATION + ID of the mirroring endpoint group association or fully qualified + identifier for the mirroring endpoint group association. + + To set the endpoint-group-association-id attribute: + ▸ provide the argument MIRRORING_ENDPOINT_GROUP_ASSOCIATION on the + command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + Location of the mirroring endpoint group association. + + To set the location attribute: + ▸ provide the argument MIRRORING_ENDPOINT_GROUP_ASSOCIATION on the + command line with a fully specified name; + ▸ provide the argument --location on the command line. + +REQUIRED FLAGS + Network resource - Mirroring Endpoint Group Association. 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 --network 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. + + --network=NETWORK + ID of the network or fully qualified identifier for the network. + + To set the network-name attribute: + ▸ provide the argument --network on the command line. + + Mirroring endpoint group resource - Mirroring Endpoint Group. 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 --mirroring-endpoint-group 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. + + --mirroring-endpoint-group=MIRRORING_ENDPOINT_GROUP + ID of the mirroring endpoint group or fully qualified identifier for + the mirroring endpoint group. + + To set the id attribute: + ▸ provide the argument --mirroring-endpoint-group on the command + line. + + This flag argument must be specified if any of the other arguments in + this group are specified. + + --mirroring-endpoint-group-location=MIRRORING_ENDPOINT_GROUP_LOCATION + Location of the mirroring endpoint group. + + To set the location attribute: + ▸ provide the argument --mirroring-endpoint-group on the command + line with a fully specified name; + ▸ provide the argument --mirroring-endpoint-group-location on the + command line; + ▸ provide the argument --location on the command line; + ▸ provide the argument + networksecurity.projects.locations.mirroringEndpointGroupAssociations + on the command line with a fully specified name. + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. The default is True. Enabled by default, use --no-async to + disable. + + --labels=[KEY=VALUE,...] + List of label KEY=VALUE pairs to add. + + Keys must start with a lowercase character and contain only hyphens + (-), underscores (_), lowercase characters, and numbers. Values must + contain only hyphens (-), underscores (_), lowercase characters, and + numbers. + + --max-wait=MAX_WAIT; default="20m" + Time to synchronously wait for the operation to complete, after which + the operation continues asynchronously. Ignored if --no-async isn't + specified. See $ gcloud topic datetimes for information on time + formats. + +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 network-security \ + mirroring-endpoint-group-associations create + diff --git a/gcloud/beta/network-security/mirroring-endpoint-group-associations/delete b/gcloud/beta/network-security/mirroring-endpoint-group-associations/delete new file mode 100644 index 000000000..852ecad97 --- /dev/null +++ b/gcloud/beta/network-security/mirroring-endpoint-group-associations/delete @@ -0,0 +1,89 @@ +NAME + gcloud beta network-security mirroring-endpoint-group-associations delete - + delete a Mirroring Endpoint Group Association + +SYNOPSIS + gcloud beta network-security mirroring-endpoint-group-associations delete + (MIRRORING_ENDPOINT_GROUP_ASSOCIATION : --location=LOCATION) [--async] + [--max-wait=MAX_WAIT; default="20m"] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Delete a mirroring endpoint group association. Check the progress of + deletion by using gcloud network-security + mirroring-endpoint-group-associations list. + + For more examples, refer to the EXAMPLES section below. + +EXAMPLES + To delete a mirroring endpoint group association called my-association, in + project ID my-project, run: + + $ gcloud beta network-security \ mirroring-endpoint-group-associations delete my-association \ + --project=my-project --location=global + + OR + + $ gcloud beta network-security \ mirroring-endpoint-group-associations delete \ + projects/my-project/locations/global/\ + mirroringEndpointGroupAssociations/my-association + +POSITIONAL ARGUMENTS + Mirroring endpoint group association resource - Mirroring Endpoint Group + Association. 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 MIRRORING_ENDPOINT_GROUP_ASSOCIATION 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. + + MIRRORING_ENDPOINT_GROUP_ASSOCIATION + ID of the mirroring endpoint group association or fully qualified + identifier for the mirroring endpoint group association. + + To set the endpoint-group-association-id attribute: + ▸ provide the argument MIRRORING_ENDPOINT_GROUP_ASSOCIATION on the + command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + Location of the mirroring endpoint group association. + + To set the location attribute: + ▸ provide the argument MIRRORING_ENDPOINT_GROUP_ASSOCIATION on the + command line with a fully specified name; + ▸ provide the argument --location on the command line. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. The default is True. Enabled by default, use --no-async to + disable. + + --max-wait=MAX_WAIT; default="20m" + Time to synchronously wait for the operation to complete, after which + the operation continues asynchronously. Ignored if --no-async isn't + specified. See $ gcloud topic datetimes for information on time + formats. + +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 network-security \ + mirroring-endpoint-group-associations delete + diff --git a/gcloud/beta/network-security/mirroring-endpoint-group-associations/describe b/gcloud/beta/network-security/mirroring-endpoint-group-associations/describe new file mode 100644 index 000000000..1639e1c2e --- /dev/null +++ b/gcloud/beta/network-security/mirroring-endpoint-group-associations/describe @@ -0,0 +1,75 @@ +NAME + gcloud beta network-security mirroring-endpoint-group-associations describe + - describe a Mirroring Endpoint Group Association + +SYNOPSIS + gcloud beta network-security mirroring-endpoint-group-associations describe + (MIRRORING_ENDPOINT_GROUP_ASSOCIATION : --location=LOCATION) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Describe a mirroring endpoint group association. + + For more examples, refer to the EXAMPLES section below. + +EXAMPLES + To get a description of a mirroring endpoint group association called + my-association in project my-project and location global, run: + + $ gcloud beta network-security \ mirroring-endpoint-group-associations describe my-association \ + --project=my-project --location=global + + OR + + $ gcloud beta network-security \ mirroring-endpoint-group-associations describe \ + projects/my-project/locations/global/\ + mirroringEndpointGroupAssociations/my-association + +POSITIONAL ARGUMENTS + Mirroring endpoint group association resource - Mirroring Endpoint Group + Association. 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 MIRRORING_ENDPOINT_GROUP_ASSOCIATION 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. + + MIRRORING_ENDPOINT_GROUP_ASSOCIATION + ID of the mirroring endpoint group association or fully qualified + identifier for the mirroring endpoint group association. + + To set the endpoint-group-association-id attribute: + ▸ provide the argument MIRRORING_ENDPOINT_GROUP_ASSOCIATION on the + command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + Location of the mirroring endpoint group association. + + To set the location attribute: + ▸ provide the argument MIRRORING_ENDPOINT_GROUP_ASSOCIATION on the + command line with a fully specified name; + ▸ provide the argument --location on the command line. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha network-security \ + mirroring-endpoint-group-associations describe + diff --git a/gcloud/beta/network-security/mirroring-endpoint-group-associations/help b/gcloud/beta/network-security/mirroring-endpoint-group-associations/help new file mode 100644 index 000000000..18d9b70d4 --- /dev/null +++ b/gcloud/beta/network-security/mirroring-endpoint-group-associations/help @@ -0,0 +1,44 @@ +NAME + gcloud beta network-security mirroring-endpoint-group-associations - manage + Mirroring Endpoint Group Association resources + +SYNOPSIS + gcloud beta network-security mirroring-endpoint-group-associations COMMAND + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) This class provides commands for managing MirroringEndpoint Group + Associations. + + Attributes: category (str): The category under which this command group + falls. + +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 a Mirroring Endpoint Group Association. + + delete + (BETA) Delete a Mirroring Endpoint Group Association. + + describe + (BETA) Describe a Mirroring Endpoint Group Association. + + list + (BETA) List Mirroring Endpoint Group Associations. + + update + (BETA) Update a Mirroring Endpoint Group Association. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha network-security mirroring-endpoint-group-associations + diff --git a/gcloud/beta/network-security/mirroring-endpoint-group-associations/list b/gcloud/beta/network-security/mirroring-endpoint-group-associations/list new file mode 100644 index 000000000..fe24fd831 --- /dev/null +++ b/gcloud/beta/network-security/mirroring-endpoint-group-associations/list @@ -0,0 +1,99 @@ +NAME + gcloud beta network-security mirroring-endpoint-group-associations list - + list Mirroring Endpoint Group Associations + +SYNOPSIS + gcloud beta network-security mirroring-endpoint-group-associations list + [--location=LOCATION] [--filter=EXPRESSION] [--limit=LIMIT] + [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) List mirroring endpoint group associations. + + For more examples, refer to the EXAMPLES section below. + +EXAMPLES + To list mirroring endpoint group associations in project my-project and + location global, run: + + $ gcloud beta network-security \ mirroring-endpoint-group-associations list \ + --project=my-project --location=global + + OR + + $ gcloud beta network-security \ mirroring-endpoint-group-associations list --location=global + + OR + + $ gcloud beta network-security \ mirroring-endpoint-group-associations list \ + --location=projects/my-project/locations/global + +FLAGS + Location resource - The location for a list operation This represents a + Cloud resource. (NOTE) Some attributes are not given arguments in this + group but can be set in other ways. + + To set the project attribute: + ◆ provide the argument --location on the command line with a fully + specified name; + ◆ Location of the Mirroring Endpoint Group Association. Defaults to + global with a fully specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + --location=LOCATION + ID of the location or fully qualified identifier for the location. + + To set the location attribute: + ▸ provide the argument --location on the command line; + ▸ Location of the Mirroring Endpoint Group Association. Defaults to + global. + +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 network-security \ + mirroring-endpoint-group-associations list + diff --git a/gcloud/beta/network-security/mirroring-endpoint-group-associations/update b/gcloud/beta/network-security/mirroring-endpoint-group-associations/update new file mode 100644 index 000000000..d50bfa3a4 --- /dev/null +++ b/gcloud/beta/network-security/mirroring-endpoint-group-associations/update @@ -0,0 +1,125 @@ +NAME + gcloud beta network-security mirroring-endpoint-group-associations update - + update a Mirroring Endpoint Group Association + +SYNOPSIS + gcloud beta network-security mirroring-endpoint-group-associations update + (MIRRORING_ENDPOINT_GROUP_ASSOCIATION : --location=LOCATION) [--async] + [--max-wait=MAX_WAIT; default="20m"] [--update-labels=[KEY=VALUE,...]] + [--clear-labels | --remove-labels=[KEY,...]] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Update a mirroring endpoint group association. Check the progress of + association update by using gcloud network-security + mirroring-endpoint-group-associations list. + + For examples refer to the EXAMPLES section below. + +EXAMPLES + To update labels k1 and k2, run: + + $ gcloud beta network-security \ mirroring-endpoint-group-associations update my-association \ + --project=my-project --location=global \ + --update-labels=k1=v1,k2=v2 + + To remove labels k3 and k4, run: + + $ gcloud beta network-security \ mirroring-endpoint-group-associations update my-association \ + --project=my-project --location=global --remove-labels=k3,k4 + + To clear all labels from the mirroring endpoint group association, run: + + $ gcloud beta network-security \ mirroring-endpoint-group-associations update my-association \ + --project=my-project --location=global --clear-labels + +POSITIONAL ARGUMENTS + Mirroring endpoint group association resource - Mirroring Endpoint Group + Association. 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 MIRRORING_ENDPOINT_GROUP_ASSOCIATION 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. + + MIRRORING_ENDPOINT_GROUP_ASSOCIATION + ID of the mirroring endpoint group association or fully qualified + identifier for the mirroring endpoint group association. + + To set the endpoint-group-association-id attribute: + ▸ provide the argument MIRRORING_ENDPOINT_GROUP_ASSOCIATION on the + command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + Location of the mirroring endpoint group association. + + To set the location attribute: + ▸ provide the argument MIRRORING_ENDPOINT_GROUP_ASSOCIATION on the + command line with a fully specified name; + ▸ provide the argument --location on the command line. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. The default is True. Enabled by default, use --no-async to + disable. + + --max-wait=MAX_WAIT; default="20m" + Time to synchronously wait for the operation to complete, after which + the operation continues asynchronously. Ignored if --no-async isn't + specified. See $ gcloud topic datetimes for information on time + formats. + + --update-labels=[KEY=VALUE,...] + List of label KEY=VALUE pairs to update. If a label exists, its value + is modified. Otherwise, a new label is created. + + Keys must start with a lowercase character and contain only hyphens + (-), underscores (_), lowercase characters, and numbers. Values must + contain only hyphens (-), underscores (_), lowercase characters, and + numbers. + + At most one of these can be specified: + + --clear-labels + Remove all labels. If --update-labels is also specified then + --clear-labels is applied first. + + For example, to remove all labels: + + $ gcloud beta network-security \ + mirroring-endpoint-group-associations update --clear-labels + + To remove all existing labels and create two new labels, foo and baz: + + $ gcloud beta network-security \ + mirroring-endpoint-group-associations update --clear-labels \ + --update-labels foo=bar,baz=qux + + --remove-labels=[KEY,...] + List of label keys to remove. If a label does not exist it is + silently ignored. If --update-labels is also specified then + --update-labels is applied first. + +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 network-security \ + mirroring-endpoint-group-associations update + diff --git a/gcloud/beta/run/deploy b/gcloud/beta/run/deploy index b0397444b..80edf32dc 100644 --- a/gcloud/beta/run/deploy +++ b/gcloud/beta/run/deploy @@ -10,14 +10,23 @@ SYNOPSIS [--service-account=SERVICE_ACCOUNT] [--tag=TAG] [--timeout=TIMEOUT] [--no-traffic] [--add-volume-mount=[volume=NAME,mount-path=MOUNT_PATH,...] - --args=[ARG,...] --clear-volume-mounts --command=[COMMAND,...] + --args=[ARG,...] --[no-]automatic-updates --clear-volume-mounts --cpu=CPU --depends-on=[CONTAINER,...] --gpu=GPU --memory=MEMORY --port=PORT --remove-volume-mount=[MOUNT_PATH,...] - --[no-]use-http2 --clear-env-vars | --env-vars-file=FILE_PATH - | --set-env-vars=[KEY=VALUE,...] | --remove-env-vars=[KEY,...] + --[no-]use-http2 --base-image=BASE_IMAGE + | --clear-base-image --build-env-vars-file=FILE_PATH + | --clear-build-env-vars | --set-build-env-vars=[KEY=VALUE,...] + | --remove-build-env-vars=[KEY,...] + --update-build-env-vars=[KEY=VALUE,...] + --build-service-account=BUILD_SERVICE_ACCOUNT + | --clear-build-service-account --build-worker-pool=BUILD_WORKER_POOL + | --clear-build-worker-pool --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,...] --command=[COMMAND,...] + | --function=FUNCTION --image=IMAGE | --source=SOURCE] [--clear-labels | --remove-labels=[KEY,...] --labels=[KEY=VALUE,...] | --update-labels=[KEY=VALUE,...]] [--connectivity=CONNECTIVITY --clear-config-maps @@ -208,14 +217,14 @@ FLAGS specified, no arguments are passed. To reset this field to its default, pass an empty string. + --[no-]automatic-updates + Indicates whether automatic base image updates should be enabled + for an image built from source. Use --automatic-updates to enable + and --no-automatic-updates to disable. + --clear-volume-mounts Remove all existing mounts from the current container. - --command=[COMMAND,...] - Entrypoint for the container image. If not specified, the container - image's default Entrypoint is run. To reset this field to its - default, pass an empty string. - --cpu=CPU Set a CPU limit in Kubernetes cpu units. @@ -252,6 +261,69 @@ FLAGS 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: + + --base-image=BASE_IMAGE + Specifies the base image to be used for automatic base image + updates. When deploying from source using the Google Cloud + buildpacks, this flag will also override the base image used for + the application image. See + https://cloud.google.com/run/docs/deploying-source-code for more + details. + + --clear-base-image + Opts out of automatic base image updates. + + At most one of these can be specified: + + --build-env-vars-file=FILE_PATH + Path to a local YAML file with definitions for all build + environment variables. All existing build environment variables + will be removed before the new build environment variables are + added. Example YAML content: + + KEY_1: "value1" + KEY_2: "value 2" + + --clear-build-env-vars + Remove all build environment variables. + + --set-build-env-vars=[KEY=VALUE,...] + List of key-value pairs to set as build environment variables. + All existing build environment variables will be removed first. + + Only --update-build-env-vars and --remove-build-env-vars can be used + together. If both are specified, --remove-build-env-vars will be + applied first. + + --remove-build-env-vars=[KEY,...] + List of build environment variables to be removed. + + --update-build-env-vars=[KEY=VALUE,...] + List of key-value pairs to set as build environment variables. + + At most one of these can be specified: + + --build-service-account=BUILD_SERVICE_ACCOUNT + Specifies the service account to use to execute the build. + Applies only to source deploy builds using the Build API. + + --clear-build-service-account + Clears the Cloud Build service account field. + + At most one of these can be specified: + + --build-worker-pool=BUILD_WORKER_POOL + Name of the Cloud Build Custom Worker Pool that should be used to + build the function. The format of this field is + projects/${PROJECT}/locations/${LOCATION}/workerPools/${WORKERPOOL} + where ${PROJECT} is the project id and ${LOCATION} is the + location where the worker pool is defined and ${WORKERPOOL} is + the short name of the worker pool. + + --clear-build-worker-pool + Clears the Cloud Build Custom Worker Pool field. + At most one of these can be specified: --clear-env-vars @@ -306,6 +378,17 @@ FLAGS --update-secrets=[KEY=VALUE,...] List of key-value pairs to set as secrets. + At most one of these can be specified: + + --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. + + --function=FUNCTION + Specifies that the deployed object is a function. If a value is + provided, that value is used as the entrypoint. + At most one of these can be specified: --image=IMAGE diff --git a/gcloud/beta/services/disable b/gcloud/beta/services/disable index 61faa781a..9db4b23a5 100644 --- a/gcloud/beta/services/disable +++ b/gcloud/beta/services/disable @@ -39,9 +39,10 @@ FLAGS --force If specified, the disable call will proceed even if there are enabled - services which depend on the service to be disabled. Forcing the call - means that the services which depend on the service to be disabled will - also be disabled. + services which depend on the service to be disabled or disable the + service used in last 30 days or was enabled in recent 3 days. Forcing + the call means that the services which depend on the service to be + disabled will also be disabled. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/compute/instance-templates/create b/gcloud/compute/instance-templates/create index 28c1f4765..0fbda04cc 100644 --- a/gcloud/compute/instance-templates/create +++ b/gcloud/compute/instance-templates/create @@ -92,7 +92,7 @@ FLAGS Attaches accelerators (e.g. GPUs) to the instances. type - The specific type (e.g. nvidia-tesla-k80 for nVidia Tesla K80) of + The specific type (e.g. nvidia-tesla-t4 for NVIDIA T4) of accelerator to attach to the instances. Use 'gcloud compute accelerator-types list' to learn about all available accelerator types. diff --git a/gcloud/compute/instances/bulk/create b/gcloud/compute/instances/bulk/create index 455f11510..fd1777ee2 100644 --- a/gcloud/compute/instances/bulk/create +++ b/gcloud/compute/instances/bulk/create @@ -130,7 +130,7 @@ OPTIONAL FLAGS Attaches accelerators (e.g. GPUs) to the instances. type - The specific type (e.g. nvidia-tesla-k80 for nVidia Tesla K80) of + The specific type (e.g. nvidia-tesla-t4 for NVIDIA T4) of accelerator to attach to the instances. Use 'gcloud compute accelerator-types list' to learn about all available accelerator types. diff --git a/gcloud/compute/instances/create b/gcloud/compute/instances/create index 9b14bb6ff..72739c9ad 100644 --- a/gcloud/compute/instances/create +++ b/gcloud/compute/instances/create @@ -143,7 +143,7 @@ FLAGS Attaches accelerators (e.g. GPUs) to the instances. type - The specific type (e.g. nvidia-tesla-k80 for nVidia Tesla K80) of + The specific type (e.g. nvidia-tesla-t4 for NVIDIA T4) of accelerator to attach to the instances. Use 'gcloud compute accelerator-types list' to learn about all available accelerator types. diff --git a/gcloud/compute/instances/create-with-container b/gcloud/compute/instances/create-with-container index 3abd231d3..cc4d94bc1 100644 --- a/gcloud/compute/instances/create-with-container +++ b/gcloud/compute/instances/create-with-container @@ -107,7 +107,7 @@ FLAGS Attaches accelerators (e.g. GPUs) to the instances. type - The specific type (e.g. nvidia-tesla-k80 for nVidia Tesla K80) of + The specific type (e.g. nvidia-tesla-t4 for NVIDIA T4) of accelerator to attach to the instances. Use 'gcloud compute accelerator-types list' to learn about all available accelerator types. diff --git a/gcloud/compute/resource-policies/update/help b/gcloud/compute/resource-policies/update/help index 5c7da19b1..9227da39d 100644 --- a/gcloud/compute/resource-policies/update/help +++ b/gcloud/compute/resource-policies/update/help @@ -16,6 +16,9 @@ GCLOUD WIDE FLAGS COMMANDS COMMAND is one of the following: + instance-schedule + Update a Compute Engine Instance Schedule Resource Policy. + snapshot-schedule Update a Compute Engine Snapshot Schedule Resource Policy. diff --git a/gcloud/compute/resource-policies/update/instance-schedule b/gcloud/compute/resource-policies/update/instance-schedule new file mode 100644 index 000000000..aaf5075ae --- /dev/null +++ b/gcloud/compute/resource-policies/update/instance-schedule @@ -0,0 +1,87 @@ +NAME + gcloud compute resource-policies update instance-schedule - update a + Compute Engine Instance Schedule Resource Policy + +SYNOPSIS + gcloud compute resource-policies update instance-schedule NAME + [--description=DESCRIPTION] [--end-date=END_DATE] + [--initiation-date=INITIATION_DATE] [--region=REGION] + [--timezone=TIMEZONE] [--vm-start-schedule=VM_START_SCHEDULE] + [--vm-stop-schedule=VM_STOP_SCHEDULE] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Update a Compute Engine Instance Schedule Resource Policy. + +EXAMPLES + To update an instance schedule resource policy with specified parameters: + + $ gcloud compute resource-policies update instance-schedule NAME \ + --region=REGION --timezone=UTC --vm-start-schedule="* 7 * * *" \ + --vm-stop-schedule="* 17 * * *" \ + --initiation-date=2025-05-01T00:00:00.000-07:00 \ + --end-date=2027-05-01T00:00:00.000-07:00 + +POSITIONAL ARGUMENTS + NAME + Name of the resource policy to operate on. + +FLAGS + --description=DESCRIPTION + An optional, textual description for the backend. + + --end-date=END_DATE + The expiration time of the schedule policy. The timestamp must be an + RFC3339 valid string. + + --initiation-date=INITIATION_DATE + The start time of the schedule policy. The timestamp must be an RFC3339 + valid string. + + --region=REGION + Region of the resource policy to operate on. If not specified, you + might be prompted to select a region (interactive mode only). + + To avoid prompting when this flag is omitted, you can set the + compute/region property: + + $ gcloud config set compute/region REGION + + A list of regions can be fetched by running: + + $ gcloud compute regions list + + To unset the property, run: + + $ gcloud config unset compute/region + + Alternatively, the region can be stored in the environment variable + CLOUDSDK_COMPUTE_REGION. + + --timezone=TIMEZONE + Timezone used in interpreting schedule. The value of this field must be + a time zone name from the tz database + http://en.wikipedia.org/wiki/Tz_database + + --vm-start-schedule=VM_START_SCHEDULE + Schedule for starting the instance, specified using standard CRON + format. + + --vm-stop-schedule=VM_STOP_SCHEDULE + Schedule for stopping the instance, specified using standard CRON + format. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + These variants are also available: + + $ gcloud alpha compute resource-policies update instance-schedule + + $ gcloud beta compute resource-policies update instance-schedule + diff --git a/gcloud/container/attached/clusters/import b/gcloud/container/attached/clusters/import index 9cf884968..4cd984768 100644 --- a/gcloud/container/attached/clusters/import +++ b/gcloud/container/attached/clusters/import @@ -34,6 +34,7 @@ REQUIRED FLAGS $ gcloud container attached clusters import --distribution=aks $ gcloud container attached clusters import --distribution=eks + $ gcloud container attached clusters import --distribution=generic --platform-version=PLATFORM_VERSION Platform version to use for the cluster. diff --git a/gcloud/container/attached/clusters/register b/gcloud/container/attached/clusters/register index 368f27565..c41261e28 100644 --- a/gcloud/container/attached/clusters/register +++ b/gcloud/container/attached/clusters/register @@ -91,6 +91,7 @@ REQUIRED FLAGS $ gcloud container attached clusters register --distribution=aks $ gcloud container attached clusters register --distribution=eks + $ gcloud container attached clusters register --distribution=generic --fleet-project=FLEET_PROJECT ID or number of the Fleet host project where the cluster is registered. diff --git a/gcloud/container/clusters/create b/gcloud/container/clusters/create index 820a01aaa..0468460c0 100644 --- a/gcloud/container/clusters/create +++ b/gcloud/container/clusters/create @@ -38,9 +38,9 @@ SYNOPSIS [--enable-managed-prometheus] [--enable-master-global-access] [--enable-multi-networking] [--enable-nested-virtualization] [--enable-network-policy] [--enable-ray-cluster-logging] - [--enable-ray-cluster-monitoring] [--enable-service-externalips] - [--enable-shielded-nodes] [--enable-stackdriver-kubernetes] - [--enable-vertical-pod-autoscaling] + [--enable-ray-cluster-monitoring] [--enable-secret-manager] + [--enable-service-externalips] [--enable-shielded-nodes] + [--enable-stackdriver-kubernetes] [--enable-vertical-pod-autoscaling] [--fleet-project=PROJECT_ID_OR_NUMBER] [--gateway-api=GATEWAY_API] [--image-type=IMAGE_TYPE] [--in-transit-encryption=IN_TRANSIT_ENCRYPTION] @@ -68,9 +68,9 @@ SYNOPSIS [--security-group=SECURITY_GROUP] [--security-posture=SECURITY_POSTURE] [--services-ipv4-cidr=CIDR] [--services-secondary-range-name=NAME] [--shielded-integrity-monitoring] [--shielded-secure-boot] [--spot] - [--stack-type=STACK_TYPE] [--subnetwork=SUBNETWORK] - [--system-config-from-file=PATH_TO_FILE] [--tags=TAG,[TAG,...]] - [--threads-per-core=THREADS_PER_CORE] + [--stack-type=STACK_TYPE] [--storage-pools=STORAGE_POOL,[...]] + [--subnetwork=SUBNETWORK] [--system-config-from-file=PATH_TO_FILE] + [--tags=TAG,[TAG,...]] [--threads-per-core=THREADS_PER_CORE] [--workload-metadata=WORKLOAD_METADATA] [--workload-pool=WORKLOAD_POOL] [--workload-vulnerability-scanning=WORKLOAD_VULNERABILITY_SCANNING] [--binauthz-evaluation-mode=BINAUTHZ_EVALUATION_MODE @@ -145,10 +145,10 @@ FLAGS Attaches accelerators (e.g. GPUs) to all nodes. type - (Required) The specific type (e.g. nvidia-tesla-k80 for NVIDIA - Tesla K80) of accelerator to attach to the instances. Use gcloud - compute accelerator-types list to learn about all available - accelerator types. + (Required) The specific type (e.g. nvidia-tesla-t4 for NVIDIA T4) + of accelerator to attach to the instances. Use gcloud compute + accelerator-types list to learn about all available accelerator + types. count (Optional) The number of accelerators to attach to the instances. @@ -620,6 +620,14 @@ FLAGS --enable-ray-cluster-monitoring Enable automatic metrics collection for Ray clusters. + --enable-secret-manager + Enables the Secret Manager CSI driver provider component. See + https://secrets-store-csi-driver.sigs.k8s.io/introduction + https://github.com/GoogleCloudPlatform/secrets-store-csi-driver-provider-gcp + + To disable in an existing cluster, explicitly set flag to + --no-enable-secret-manager + --enable-service-externalips Enables use of services with externalIPs field. @@ -1165,6 +1173,13 @@ FLAGS IP stack type of the node VMs. STACK_TYPE must be one of: ipv4, ipv4-ipv6. + --storage-pools=STORAGE_POOL,[...] + A list of storage pools where the cluster's boot disks will be + provisioned. + + STORAGE_POOL must be in the format + projects/project/zones/zone/storagePools/storagePool + --subnetwork=SUBNETWORK The Google Compute Engine subnetwork (https://cloud.google.com/compute/docs/subnetworks) to which the @@ -1419,11 +1434,11 @@ FLAGS Resource limits are specified in the field 'resourceLimits'. Each resource limits definition contains three fields: resourceType, maximum and minimum. Resource type can be "cpu", "memory" or an - accelerator (e.g. "nvidia-tesla-k80" for nVidia Tesla K80). Use - gcloud compute accelerator-types list to learn about available - accelerator types. Maximum is the maximum allowed amount with the - unit of the resource. Minimum is the minimum allowed amount with - the unit of the resource. + accelerator (e.g. "nvidia-tesla-t4" for NVIDIA T4). Use gcloud + compute accelerator-types list to learn about available accelerator + types. Maximum is the maximum allowed amount with the unit of the + resource. Minimum is the minimum allowed amount with the unit of + the resource. Identity default contains at most one of the below fields: serviceAccount: The Google Cloud Platform Service Account to be @@ -1605,10 +1620,10 @@ FLAGS GPUs) in cluster. type - (Required) The specific type (e.g. nvidia-tesla-k80 for - nVidia Tesla K80) of accelerator for which the limit is - set. Use gcloud compute accelerator-types list to learn - about all available accelerator types. + (Required) The specific type (e.g. nvidia-tesla-t4 for + NVIDIA T4) of accelerator for which the limit is set. Use + gcloud compute accelerator-types list to learn about all + available accelerator types. count (Required) The maximum number of accelerators to which the @@ -1623,10 +1638,10 @@ FLAGS isn't set. type - (Required) The specific type (e.g. nvidia-tesla-k80 for - nVidia Tesla K80) of accelerator for which the limit is - set. Use gcloud compute accelerator-types list to learn - about all available accelerator types. + (Required) The specific type (e.g. nvidia-tesla-t4 for + NVIDIA T4) of accelerator for which the limit is set. Use + gcloud compute accelerator-types list to learn about all + available accelerator types. count (Required) The minimum number of accelerators to which the diff --git a/gcloud/container/clusters/create-auto b/gcloud/container/clusters/create-auto index 3c5ad1ca4..14d53f610 100644 --- a/gcloud/container/clusters/create-auto +++ b/gcloud/container/clusters/create-auto @@ -20,13 +20,13 @@ SYNOPSIS [--enable-kubernetes-unstable-apis=API,[API,...]] [--enable-master-global-access] [--enable-ray-cluster-logging] [--enable-ray-cluster-monitoring] [--enable-ray-operator] - [--fleet-project=PROJECT_ID_OR_NUMBER] [--labels=[KEY=VALUE,...]] - [--logging=[COMPONENT,...]] [--monitoring=[COMPONENT,...]] - [--network=NETWORK] [--private-endpoint-subnetwork=NAME] - [--release-channel=[CHANNEL]] [--security-group=SECURITY_GROUP] - [--security-posture=SECURITY_POSTURE] [--services-ipv4-cidr=CIDR] - [--services-secondary-range-name=NAME] [--subnetwork=SUBNETWORK] - [--workload-policies=WORKLOAD_POLICIES] + [--enable-secret-manager] [--fleet-project=PROJECT_ID_OR_NUMBER] + [--labels=[KEY=VALUE,...]] [--logging=[COMPONENT,...]] + [--monitoring=[COMPONENT,...]] [--network=NETWORK] + [--private-endpoint-subnetwork=NAME] [--release-channel=[CHANNEL]] + [--security-group=SECURITY_GROUP] [--security-posture=SECURITY_POSTURE] + [--services-ipv4-cidr=CIDR] [--services-secondary-range-name=NAME] + [--subnetwork=SUBNETWORK] [--workload-policies=WORKLOAD_POLICIES] [--workload-vulnerability-scanning=WORKLOAD_VULNERABILITY_SCANNING] [--dataplane-v2-observability-mode=DATAPLANE_V2_OBSERVABILITY_MODE | --disable-dataplane-v2-flow-observability @@ -260,6 +260,14 @@ FLAGS --enable-ray-operator Enable the Ray Operator GKE add-on. This add-on is disabled by default. + --enable-secret-manager + Enables the Secret Manager CSI driver provider component. See + https://secrets-store-csi-driver.sigs.k8s.io/introduction + https://github.com/GoogleCloudPlatform/secrets-store-csi-driver-provider-gcp + + To disable in an existing cluster, explicitly set flag to + --no-enable-secret-manager + --fleet-project=PROJECT_ID_OR_NUMBER Sets fleet host project for the cluster. If specified, the current cluster will be registered as a fleet membership under the fleet host diff --git a/gcloud/container/clusters/update b/gcloud/container/clusters/update index 2620349bc..3d14d4473 100644 --- a/gcloud/container/clusters/update +++ b/gcloud/container/clusters/update @@ -24,9 +24,9 @@ SYNOPSIS | --enable-master-authorized-networks | --enable-master-global-access | --enable-multi-networking | --enable-network-policy | --enable-private-endpoint | --[no-]enable-ray-cluster-logging - | --[no-]enable-ray-cluster-monitoring | --enable-service-externalips - | --enable-shielded-nodes | --enable-stackdriver-kubernetes - | --enable-vertical-pod-autoscaling + | --[no-]enable-ray-cluster-monitoring | --enable-secret-manager + | --enable-service-externalips | --enable-shielded-nodes + | --enable-stackdriver-kubernetes | --enable-vertical-pod-autoscaling | --fleet-project=PROJECT_ID_OR_NUMBER | --gateway-api=GATEWAY_API | --generate-password | --in-transit-encryption=IN_TRANSIT_ENCRYPTION | --logging-variant=LOGGING_VARIANT | --maintenance-window=START_TIME @@ -388,6 +388,14 @@ REQUIRED FLAGS --enable-ray-cluster-monitoring to enable and --no-enable-ray-cluster-monitoring to disable. + --enable-secret-manager + Enables the Secret Manager CSI driver provider component. See + https://secrets-store-csi-driver.sigs.k8s.io/introduction + https://github.com/GoogleCloudPlatform/secrets-store-csi-driver-provider-gcp + + To disable in an existing cluster, explicitly set flag to + --no-enable-secret-manager + --enable-service-externalips Enables use of services with externalIPs field. @@ -1012,8 +1020,8 @@ REQUIRED FLAGS Resource limits are specified in the field 'resourceLimits'. Each resource limits definition contains three fields: resourceType, maximum and minimum. Resource type can be "cpu", "memory" or an - accelerator (e.g. "nvidia-tesla-k80" for nVidia Tesla K80). Use - gcloud compute accelerator-types list to learn about available + accelerator (e.g. "nvidia-tesla-t4" for NVIDIA T4). Use gcloud + compute accelerator-types list to learn about available accelerator types. Maximum is the maximum allowed amount with the unit of the resource. Minimum is the minimum allowed amount with the unit of the resource. @@ -1194,10 +1202,10 @@ REQUIRED FLAGS GPUs) in cluster. type - (Required) The specific type (e.g. nvidia-tesla-k80 for - nVidia Tesla K80) of accelerator for which the limit is - set. Use gcloud compute accelerator-types list to learn - about all available accelerator types. + (Required) The specific type (e.g. nvidia-tesla-t4 for + NVIDIA T4) of accelerator for which the limit is set. Use + gcloud compute accelerator-types list to learn about all + available accelerator types. count (Required) The maximum number of accelerators to which @@ -1212,10 +1220,10 @@ REQUIRED FLAGS it isn't set. type - (Required) The specific type (e.g. nvidia-tesla-k80 for - nVidia Tesla K80) of accelerator for which the limit is - set. Use gcloud compute accelerator-types list to learn - about all available accelerator types. + (Required) The specific type (e.g. nvidia-tesla-t4 for + NVIDIA T4) of accelerator for which the limit is set. Use + gcloud compute accelerator-types list to learn about all + available accelerator types. count (Required) The minimum number of accelerators to which diff --git a/gcloud/container/node-pools/create b/gcloud/container/node-pools/create index c03a8ccf4..cd76c8c34 100644 --- a/gcloud/container/node-pools/create +++ b/gcloud/container/node-pools/create @@ -48,6 +48,7 @@ SYNOPSIS [--standard-rollout-policy=[batch-node-count=BATCH_NODE_COUNT, batch-percent=BATCH_NODE_PERCENTAGE, batch-soak-duration=BATCH_SOAK_DURATION,...]] + [--storage-pools=STORAGE_POOL,[...]] [--system-config-from-file=PATH_TO_FILE] [--tags=TAG,[TAG,...]] [--threads-per-core=THREADS_PER_CORE] [--tpu-topology=TPU_TOPOLOGY] [--windows-os-version=WINDOWS_OS_VERSION] @@ -96,10 +97,10 @@ FLAGS Attaches accelerators (e.g. GPUs) to all nodes. type - (Required) The specific type (e.g. nvidia-tesla-k80 for NVIDIA - Tesla K80) of accelerator to attach to the instances. Use gcloud - compute accelerator-types list to learn about all available - accelerator types. + (Required) The specific type (e.g. nvidia-tesla-t4 for NVIDIA T4) + of accelerator to attach to the instances. Use gcloud compute + accelerator-types list to learn about all available accelerator + types. count (Optional) The number of accelerators to attach to the instances. @@ -646,6 +647,13 @@ FLAGS --standard-rollout-policy=batch-percent=0.3,\ batch-soak-duration=60s + --storage-pools=STORAGE_POOL,[...] + A list of storage pools where the node pool's boot disks will be + provisioned. + + STORAGE_POOL must be in the format + projects/project/zones/zone/storagePools/storagePool + --system-config-from-file=PATH_TO_FILE Path of the YAML/JSON file that contains the node configuration, including Linux kernel parameters (sysctls) and kubelet configs. diff --git a/gcloud/container/node-pools/update b/gcloud/container/node-pools/update index 4ecf1245f..e2886056e 100644 --- a/gcloud/container/node-pools/update +++ b/gcloud/container/node-pools/update @@ -13,6 +13,7 @@ SYNOPSIS | --node-labels=[NODE_LABEL,...] | --node-locations=ZONE,[ZONE,...] | --node-taints=[NODE_TAINT,...] | --resource-manager-tags=[KEY=VALUE,...] + | --storage-pools=STORAGE_POOL,[...] | --system-config-from-file=PATH_TO_FILE | --tags=[TAG,...] | --windows-os-version=WINDOWS_OS_VERSION | --workload-metadata=WORKLOAD_METADATA | --disk-size=DISK_SIZE @@ -203,6 +204,14 @@ REQUIRED FLAGS policy rules. For instructions, see https://cloud.google.com/firewall/docs/use-tags-for-firewalls. + --storage-pools=STORAGE_POOL,[...] + A list of storage pools where the node pool's boot disks will be + provisioned. Replaces all the current storage pools of an existing + node pool, with the specified storage pools. + + STORAGE_POOL must be in the format + projects/project/zones/zone/storagePools/storagePool + --system-config-from-file=PATH_TO_FILE Path of the YAML/JSON file that contains the node configuration, including Linux kernel parameters (sysctls) and kubelet configs. diff --git a/gcloud/dataplex/entries/search b/gcloud/dataplex/entries/search index 36cf7a345..3f1a0b1f2 100644 --- a/gcloud/dataplex/entries/search +++ b/gcloud/dataplex/entries/search @@ -34,7 +34,7 @@ OPTIONAL FLAGS ◆ title [asc|desc], defaults to ascending if not specified. --page-size=PAGE_SIZE - Maximum number of resources per page. No more than 1000. + Maximum number of resources per page. No more than 500. --scope=SCOPE The scope under which the search should be operating. Should either be diff --git a/gcloud/dataproc/clusters/create b/gcloud/dataproc/clusters/create index 21a41dfad..13bff5dec 100644 --- a/gcloud/dataproc/clusters/create +++ b/gcloud/dataproc/clusters/create @@ -162,7 +162,7 @@ FLAGS type The specific type of accelerator to attach to the instances, such - as nvidia-tesla-k80 for NVIDIA Tesla K80. Use gcloud compute + as nvidia-tesla-t4 for NVIDIA T4. Use gcloud compute accelerator-types list to display available accelerator types. count @@ -231,7 +231,7 @@ FLAGS type The specific type of accelerator to attach to the instances, such - as nvidia-tesla-k80 for NVIDIA Tesla K80. Use gcloud compute + as nvidia-tesla-t4 for NVIDIA T4. Use gcloud compute accelerator-types list to display available accelerator types. count @@ -358,7 +358,7 @@ FLAGS type The specific type of accelerator to attach to the instances, such - as nvidia-tesla-k80 for NVIDIA Tesla K80. Use gcloud compute + as nvidia-tesla-t4 for NVIDIA T4. Use gcloud compute accelerator-types list to display available accelerator types. count @@ -410,7 +410,7 @@ FLAGS type The specific type of accelerator to attach to the instances, such - as nvidia-tesla-k80 for NVIDIA Tesla K80. Use gcloud compute + as nvidia-tesla-t4 for NVIDIA T4. Use gcloud compute accelerator-types list to display available accelerator types. count diff --git a/gcloud/dataproc/workflow-templates/set-managed-cluster b/gcloud/dataproc/workflow-templates/set-managed-cluster index be66552e6..d51e8176c 100644 --- a/gcloud/dataproc/workflow-templates/set-managed-cluster +++ b/gcloud/dataproc/workflow-templates/set-managed-cluster @@ -161,7 +161,7 @@ FLAGS type The specific type of accelerator to attach to the instances, such - as nvidia-tesla-k80 for NVIDIA Tesla K80. Use gcloud compute + as nvidia-tesla-t4 for NVIDIA T4. Use gcloud compute accelerator-types list to display available accelerator types. count @@ -280,7 +280,7 @@ FLAGS type The specific type of accelerator to attach to the instances, such - as nvidia-tesla-k80 for NVIDIA Tesla K80. Use gcloud compute + as nvidia-tesla-t4 for NVIDIA T4. Use gcloud compute accelerator-types list to display available accelerator types. count @@ -332,7 +332,7 @@ FLAGS type The specific type of accelerator to attach to the instances, such - as nvidia-tesla-k80 for NVIDIA Tesla K80. Use gcloud compute + as nvidia-tesla-t4 for NVIDIA T4. Use gcloud compute accelerator-types list to display available accelerator types. count diff --git a/gcloud/firestore/help b/gcloud/firestore/help index 29b01ccd4..de581e6f8 100644 --- a/gcloud/firestore/help +++ b/gcloud/firestore/help @@ -9,6 +9,8 @@ DESCRIPTION import -- Import data from Google Cloud Storage + bulk-delete -- Bulk delete documents from Cloud Firestore + indexes -- Manage your Cloud Firestore indexes operations -- Manage Long Running Operations for Cloud Firestore diff --git a/gcloud/firestore/indexes/composite/create b/gcloud/firestore/indexes/composite/create index 8f4cefb7e..09ea1b601 100644 --- a/gcloud/firestore/indexes/composite/create +++ b/gcloud/firestore/indexes/composite/create @@ -4,7 +4,7 @@ NAME SYNOPSIS gcloud firestore indexes composite create --field-config=[array-config=ARRAY-CONFIG], - [field-path=FIELD-PATH],[order=ORDER] + [field-path=FIELD-PATH],[order=ORDER],[vector-config=VECTOR-CONFIG] (--collection-group=COLLECTION_GROUP : --database=DATABASE) [--api-scope=API_SCOPE; default="any-api"] [--async] [--query-scope=QUERY_SCOPE; default="collection"] @@ -29,31 +29,43 @@ EXAMPLES --field-config=field-path=timestamp,order=descending REQUIRED FLAGS - --field-config=[array-config=ARRAY-CONFIG],[field-path=FIELD-PATH],[order=ORDER] - Configuration for a field. + --field-config=[array-config=ARRAY-CONFIG],[field-path=FIELD-PATH],[order=ORDER],[vector-config=VECTOR-CONFIG] + Required, Configuration for an index field. - This flag must be repeated to provide the ordered list of field - configurations comprising the composite index. For example: - - $ gcloud firestore indexes composite create \ - --collection-group=Events \ - --field-config field-path=tags,array-config=contains \ - --field-config field-path=user_id,order=descending \ - --field-config field-path=timestamp,order=descending - - The following keys are allowed: + array-config + Specifies the configuration for an array field. The only valid + option is 'contains'. Exactly one of 'order', 'array-config', or + 'vector-config' must be specified. field-path Specifies the field path (e.g. 'address.city'). This is required. order - Specifies the order. Valid options are: 'ascending', 'descending'. - Exactly one of order or array-config must be specified. + Specifies the order. Valid options are 'ascending', 'descending'. + Exactly one of 'order', 'array-config', or 'vector-config' must be + specified. - array-config - Specifies the configuration for an array field. The only valid - option is 'contains'. Exactly one of 'order' or 'array-config' must - be specified. + vector-config + Specifies the configuration for a vector field. Exactly one of + 'order', 'array-config', or 'vector-config' must be specified. + + dimension + Sets dimension value. + + flat + Sets flat value. + + Shorthand Example: + + --field-config='array-config=string,field-path=string,order=string,vector-config={"dimension": int, "flat": {"string"}}' --field-config='array-config=string,field-path=string,order=string,vector-config={"dimension": int, "flat": {"string"}}' + + JSON Example: + + --field-config='[{"array-config": "string", "field-path": "string", "order": "string", "vector-config": {"dimension": int, "flat": {"string"}}}]' + + File Example: + + --field-config=path_to_file.(yaml|json) Collection group resource - Collection group of the index. The arguments in this group can be used to specify the attributes of this resource. diff --git a/gcloud/looker/instances/create b/gcloud/looker/instances/create index 5e46537d3..ba21a4f03 100644 --- a/gcloud/looker/instances/create +++ b/gcloud/looker/instances/create @@ -12,6 +12,7 @@ SYNOPSIS --deny-maintenance-period-start-date=DENY_MAINTENANCE_PERIOD_START_DATE --deny-maintenance-period-time=DENY_MAINTENANCE_PERIOD_TIME] [--maintenance-window-day=MAINTENANCE_WINDOW_DAY --maintenance-window-time=MAINTENANCE_WINDOW_TIME] + [--psc-enabled : --psc-allowed-vpcs=[PSC_ALLOWED_VPCS,...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -203,6 +204,20 @@ OPTIONAL FLAGS This flag argument must be specified if any of the other arguments in this group are specified. + Private Service Connect - Private Service Connect allows private + consumption of services across VPC networks that belong to different + groups, teams, projects, or organizations. + + --psc-enabled + This specifies whether Private Service Connect (PSC) is enabled on + the Looker instance. + + This flag argument must be specified if any of the other arguments in + this group are specified. + + --psc-allowed-vpcs=[PSC_ALLOWED_VPCS,...] + List of VPCs that are allowed ingress into the Looker instance. + 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/looker/instances/update b/gcloud/looker/instances/update index 647f0c835..6dbb8b364 100644 --- a/gcloud/looker/instances/update +++ b/gcloud/looker/instances/update @@ -10,6 +10,9 @@ SYNOPSIS [--add-developer-users=ADD_DEVELOPER_USERS --add-standard-users=ADD_STANDARD_USERS --add-viewer-users=ADD_VIEWER_USERS] + [--clear-psc-allowed-vpcs | --psc-allowed-vpcs=[PSC_ALLOWED_VPCS,...] + --clear-psc-service-attachments + | --psc-service-attachment=[attachment=ATTACHMENT],[domain=DOMAIN]] [--deny-maintenance-period-end-date=DENY_MAINTENANCE_PERIOD_END_DATE --deny-maintenance-period-start-date=DENY_MAINTENANCE_PERIOD_START_DATE --deny-maintenance-period-time=DENY_MAINTENANCE_PERIOD_TIME] [--maintenance-window-day=MAINTENANCE_WINDOW_DAY @@ -114,6 +117,31 @@ FLAGS --add-viewer-users=ADD_VIEWER_USERS Number of additional Viewer Users to allocate to the Looker Instance. + Private Service Connect - Private Service Connect allows private + consumption of services across VPC networks that belong to different + groups, teams, projects, or organizations. + + At most one of these can be specified: + + --clear-psc-allowed-vpcs + Remove all service attachments from the PSC config of the instance. + + --psc-allowed-vpcs=[PSC_ALLOWED_VPCS,...] + List of VPCs that are allowed ingress into the Looker instance. + + At most one of these can be specified: + + --clear-psc-service-attachments + Remove all service attachments from the PSC config of the instance. + + --psc-service-attachment=[attachment=ATTACHMENT],[domain=DOMAIN] + The service attachments asigned to the Private Service Connect + (PSC) config. This flag can be repeated. (Example: + --psc-service-attachment + domain="mydomain.com",attachment="projects/my-project/regions/us-east1/serviceAttachments/sa" + --psc-service-attachments + domain="mydomain.com",attachment="projects/my-project/regions/us-east1/serviceAttachments/sa") + Deny Maintanence Period - You must allow at least 48 hours of maintenance availability in a 60-day rolling window. Only contiguous availability windows of at least two hours are considered. When setting a maintenance diff --git a/gcloud/services/disable b/gcloud/services/disable index 5f89f429b..b3717eadd 100644 --- a/gcloud/services/disable +++ b/gcloud/services/disable @@ -38,9 +38,10 @@ FLAGS --force If specified, the disable call will proceed even if there are enabled - services which depend on the service to be disabled. Forcing the call - means that the services which depend on the service to be disabled will - also be disabled. + services which depend on the service to be disabled or disable the + service used in last 30 days or was enabled in recent 3 days. Forcing + the call means that the services which depend on the service to be + disabled will also be disabled. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/storage/objects/update b/gcloud/storage/objects/update index a4a5fe3fb..7864e08d5 100644 --- a/gcloud/storage/objects/update +++ b/gcloud/storage/objects/update @@ -38,13 +38,20 @@ EXAMPLES $ gcloud storage objects update gs://bucket/my-object \ --custom-metadata=key1=value1,key2=value2 + One can use wildcards (https://cloud.google.com/storage/docs/wildcards) to + update multiple objects in a single command. for instance to update all + objects to have a custom-metadata key: + + $ gcloud storage objects update gs://bucket/** \ + --custom-metadata=key1=value1,key2=value2 + Rewrite all JPEG images to the NEARLINE storage class: $ gcloud storage objects update gs://bucket/*.jpg \ --storage-class=NEARLINE - You can also provide a precondition on an object's metageneration in - order to avoid potential race conditions: + You can also provide a precondition on an object's metageneration in order + to avoid potential race conditions: $ gcloud storage objects update gs://bucket/*.jpg \ --storage-class=NEARLINE --if-metageneration-match=123456789 diff --git a/gcloud/workbench/instances/create b/gcloud/workbench/instances/create index 2acd29f0c..d4731232e 100644 --- a/gcloud/workbench/instances/create +++ b/gcloud/workbench/instances/create @@ -7,7 +7,7 @@ SYNOPSIS [--labels=[KEY=VALUE,...]] [--disable-public-ip --enable-ip-forwarding --machine-type=MACHINE_TYPE; default="n1-standard-4" - --metadata=[KEY=VALUE,...] + --metadata=[KEY=VALUE,...] --min-cpu-platform=MIN_CPU_PLATFORM --service-account-email=SERVICE_ACCOUNT_EMAIL --tags=[TAGS,...] --accelerator-core-count=ACCELERATOR_CORE_COUNT --accelerator-type=ACCELERATOR_TYPE @@ -139,6 +139,11 @@ FLAGS --metadata=[KEY=VALUE,...] Custom metadata to apply to this instance. + --min-cpu-platform=MIN_CPU_PLATFORM + The minimum CPU platform to use for this instance. The list of valid + values can be found in + https://cloud.google.com/compute/docs/instances/specify-min-cpu-platform#availablezones + The service account on this instance, giving access to other Google Cloud services. You can use any service account within the same project, but you must grant the service account user permission to use the