From e555fef0aac6f069c7a0792ee7e4c43ab82a8e5b Mon Sep 17 00:00:00 2001 From: Automated Date: Wed, 19 Mar 2025 10:42:21 +0000 Subject: [PATCH] gcloud: Wed Mar 19 10:42:21 UTC 2025 --- gcloud/_version | 8 +- gcloud/alloydb/instances/create | 22 +- gcloud/alloydb/instances/update | 22 +- gcloud/alpha/ai/endpoints/deploy-model | 7 +- gcloud/alpha/ai/endpoints/list | 14 +- gcloud/alpha/ai/help | 3 + gcloud/alpha/ai/model-garden/help | 29 ++ gcloud/alpha/ai/model-garden/models/deploy | 199 +++++++++++ gcloud/alpha/ai/model-garden/models/help | 35 ++ gcloud/alpha/ai/model-garden/models/list | 70 ++++ .../models/list-deployment-config | 70 ++++ gcloud/alpha/alloydb/instances/create | 22 +- gcloud/alpha/alloydb/instances/update | 22 +- .../certificate-manager/certificates/list | 5 +- .../dns-authorizations/list | 9 +- .../certificate-manager/issuance-configs/list | 7 +- .../certificate-manager/trust-configs/list | 9 +- gcloud/alpha/compute/disks/convert | 6 +- gcloud/alpha/compute/disks/update | 7 + .../alpha/compute/future-reservations/create | 3 +- .../alpha/compute/future-reservations/update | 10 +- .../managed/resize-requests/create | 17 +- gcloud/alpha/compute/instances/help | 3 + .../compute/instances/report-host-as-faulty | 83 +++++ gcloud/alpha/compute/interconnects/create | 2 + gcloud/alpha/compute/networks/subnets/create | 11 +- gcloud/alpha/compute/reservations/create | 3 +- gcloud/alpha/compute/reservations/update | 7 + .../resource-policies/create/group-placement | 10 +- .../compute/resource-policies/create/help | 3 + .../resource-policies/create/workload-policy | 93 +++++ .../compute/tpus/queued-resources/create | 3 +- gcloud/alpha/container/clusters/create | 26 +- gcloud/alpha/container/node-pools/create | 26 +- gcloud/alpha/container/node-pools/update | 23 +- gcloud/alpha/dataproc/clusters/create | 69 +++- gcloud/alpha/dataproc/clusters/update | 68 +++- .../workflow-templates/set-managed-cluster | 6 +- gcloud/alpha/iam/roles/undelete | 5 +- gcloud/alpha/iam/roles/update | 8 +- .../managed-kafka/connect-clusters/create | 148 ++++++++ .../managed-kafka/connect-clusters/delete | 78 +++++ .../managed-kafka/connect-clusters/describe | 73 ++++ .../alpha/managed-kafka/connect-clusters/help | 41 +++ .../alpha/managed-kafka/connect-clusters/list | 86 +++++ .../managed-kafka/connect-clusters/update | 175 ++++++++++ gcloud/alpha/managed-kafka/connectors/create | 106 ++++++ gcloud/alpha/managed-kafka/connectors/delete | 80 +++++ .../alpha/managed-kafka/connectors/describe | 80 +++++ gcloud/alpha/managed-kafka/connectors/help | 55 +++ gcloud/alpha/managed-kafka/connectors/list | 102 ++++++ gcloud/alpha/managed-kafka/connectors/pause | 80 +++++ gcloud/alpha/managed-kafka/connectors/restart | 80 +++++ gcloud/alpha/managed-kafka/connectors/resume | 81 +++++ gcloud/alpha/managed-kafka/connectors/stop | 80 +++++ gcloud/alpha/managed-kafka/connectors/update | 105 ++++++ gcloud/alpha/managed-kafka/help | 6 + gcloud/alpha/memorystore/instances/create | 153 +++++++- gcloud/alpha/memorystore/instances/help | 3 + .../instances/reschedule-maintenance | 94 +++++ gcloud/alpha/memorystore/instances/update | 329 ++++++++++++++++-- gcloud/alpha/run/deploy | 34 -- gcloud/alpha/run/multi-region-services/update | 93 +++-- gcloud/alpha/run/services/update | 34 -- gcloud/alpha/spanner/databases/execute-sql | 10 +- gcloud/alpha/sql/backups/restore | 10 + gcloud/alpha/sql/instances/create | 50 ++- gcloud/alpha/sql/instances/patch | 42 ++- gcloud/alpha/storage/help | 3 + .../storage/intelligence-configs/describe | 45 +++ .../storage/intelligence-configs/disable | 44 +++ .../alpha/storage/intelligence-configs/enable | 95 +++++ .../alpha/storage/intelligence-configs/help | 36 ++ .../alpha/storage/intelligence-configs/update | 109 ++++++ gcloud/artifacts/attachments/describe | 80 +++++ gcloud/artifacts/attachments/help | 3 + gcloud/beta/ai/endpoints/deploy-model | 7 +- gcloud/beta/ai/endpoints/list | 14 +- gcloud/beta/ai/help | 3 + gcloud/beta/ai/model-garden/help | 27 ++ gcloud/beta/ai/model-garden/models/deploy | 197 +++++++++++ gcloud/beta/ai/model-garden/models/help | 33 ++ gcloud/beta/ai/model-garden/models/list | 68 ++++ .../models/list-deployment-config | 68 ++++ gcloud/beta/alloydb/instances/create | 22 +- gcloud/beta/alloydb/instances/update | 22 +- .../certificate-manager/certificates/list | 5 +- .../dns-authorizations/list | 9 +- .../certificate-manager/issuance-configs/list | 7 +- .../certificate-manager/trust-configs/list | 9 +- gcloud/beta/compute/backend-services/create | 4 + gcloud/beta/compute/backend-services/update | 4 + gcloud/beta/compute/disks/convert | 6 +- .../beta/compute/future-reservations/create | 3 +- .../beta/compute/future-reservations/update | 3 +- gcloud/beta/compute/instances/help | 3 + .../compute/instances/report-host-as-faulty | 81 +++++ gcloud/beta/compute/networks/subnets/create | 7 +- gcloud/beta/compute/networks/subnets/update | 7 +- .../compute/public-delegated-prefixes/create | 3 +- .../delegated-sub-prefixes/create | 3 +- gcloud/beta/compute/reservations/create | 7 +- .../resource-policies/create/group-placement | 8 +- gcloud/beta/container/clusters/create | 26 +- gcloud/beta/container/node-pools/create | 26 +- gcloud/beta/container/node-pools/update | 23 +- gcloud/beta/dataproc/clusters/create | 69 +++- gcloud/beta/dataproc/clusters/update | 68 +++- .../workflow-templates/set-managed-cluster | 6 +- gcloud/beta/filestore/instances/create | 1 + gcloud/beta/filestore/instances/update | 6 + gcloud/beta/iam/roles/undelete | 5 +- gcloud/beta/iam/roles/update | 8 +- gcloud/beta/memorystore/instances/create | 153 +++++++- gcloud/beta/memorystore/instances/help | 3 + .../instances/reschedule-maintenance | 92 +++++ gcloud/beta/memorystore/instances/update | 329 ++++++++++++++++-- gcloud/beta/netapp/backup-vaults/create | 8 + .../hubs/accept-spoke-update | 72 ++++ gcloud/beta/network-connectivity/hubs/help | 6 + .../hubs/reject-spoke-update | 75 ++++ .../spokes/linked-producer-vpc-network/update | 9 +- .../spokes/linked-vpc-network/update | 9 +- gcloud/beta/run/deploy | 34 -- gcloud/beta/run/multi-region-services/update | 93 +++-- gcloud/beta/run/services/update | 34 -- gcloud/beta/spanner/databases/execute-sql | 10 +- gcloud/beta/sql/backups/restore | 10 + gcloud/beta/sql/instances/create | 50 ++- gcloud/beta/sql/instances/patch | 42 ++- gcloud/certificate-manager/certificates/list | 5 +- .../dns-authorizations/list | 9 +- .../certificate-manager/issuance-configs/list | 7 +- gcloud/certificate-manager/trust-configs/list | 9 +- gcloud/compute/disks/convert | 6 +- gcloud/compute/instances/help | 3 + .../compute/instances/report-host-as-faulty | 79 +++++ gcloud/compute/networks/subnets/create | 7 +- gcloud/compute/networks/subnets/update | 7 +- .../compute/public-delegated-prefixes/create | 3 +- .../delegated-sub-prefixes/create | 3 +- gcloud/compute/reservations/create | 7 +- gcloud/container/clusters/create | 28 +- gcloud/container/clusters/create-auto | 7 + gcloud/container/clusters/update | 9 +- gcloud/container/node-pools/create | 21 +- gcloud/container/node-pools/update | 23 +- gcloud/dataproc/clusters/create | 71 +++- gcloud/dataproc/clusters/update | 68 +++- .../workflow-templates/set-managed-cluster | 6 +- gcloud/filestore/instances/create | 3 +- gcloud/filestore/instances/update | 6 + gcloud/iam/roles/undelete | 5 +- gcloud/iam/roles/update | 4 +- gcloud/memorystore/instances/create | 153 +++++++- gcloud/memorystore/instances/help | 3 + .../instances/reschedule-maintenance | 87 +++++ gcloud/memorystore/instances/update | 329 ++++++++++++++++-- .../hubs/accept-spoke-update | 70 ++++ gcloud/network-connectivity/hubs/help | 6 + .../hubs/reject-spoke-update | 74 ++++ .../service-connection-policies/update | 30 +- .../spokes/linked-producer-vpc-network/update | 9 +- .../spokes/linked-vpc-network/update | 9 +- gcloud/run/deploy | 87 +++-- gcloud/run/services/update | 93 +++-- gcloud/spanner/databases/execute-sql | 10 +- gcloud/sql/backups/restore | 10 + gcloud/sql/instances/create | 36 +- gcloud/sql/instances/patch | 20 +- 170 files changed, 6428 insertions(+), 659 deletions(-) create mode 100644 gcloud/alpha/ai/model-garden/help create mode 100644 gcloud/alpha/ai/model-garden/models/deploy create mode 100644 gcloud/alpha/ai/model-garden/models/help create mode 100644 gcloud/alpha/ai/model-garden/models/list create mode 100644 gcloud/alpha/ai/model-garden/models/list-deployment-config create mode 100644 gcloud/alpha/compute/instances/report-host-as-faulty create mode 100644 gcloud/alpha/compute/resource-policies/create/workload-policy create mode 100644 gcloud/alpha/managed-kafka/connect-clusters/create create mode 100644 gcloud/alpha/managed-kafka/connect-clusters/delete create mode 100644 gcloud/alpha/managed-kafka/connect-clusters/describe create mode 100644 gcloud/alpha/managed-kafka/connect-clusters/help create mode 100644 gcloud/alpha/managed-kafka/connect-clusters/list create mode 100644 gcloud/alpha/managed-kafka/connect-clusters/update create mode 100644 gcloud/alpha/managed-kafka/connectors/create create mode 100644 gcloud/alpha/managed-kafka/connectors/delete create mode 100644 gcloud/alpha/managed-kafka/connectors/describe create mode 100644 gcloud/alpha/managed-kafka/connectors/help create mode 100644 gcloud/alpha/managed-kafka/connectors/list create mode 100644 gcloud/alpha/managed-kafka/connectors/pause create mode 100644 gcloud/alpha/managed-kafka/connectors/restart create mode 100644 gcloud/alpha/managed-kafka/connectors/resume create mode 100644 gcloud/alpha/managed-kafka/connectors/stop create mode 100644 gcloud/alpha/managed-kafka/connectors/update create mode 100644 gcloud/alpha/memorystore/instances/reschedule-maintenance create mode 100644 gcloud/alpha/storage/intelligence-configs/describe create mode 100644 gcloud/alpha/storage/intelligence-configs/disable create mode 100644 gcloud/alpha/storage/intelligence-configs/enable create mode 100644 gcloud/alpha/storage/intelligence-configs/help create mode 100644 gcloud/alpha/storage/intelligence-configs/update create mode 100644 gcloud/artifacts/attachments/describe create mode 100644 gcloud/beta/ai/model-garden/help create mode 100644 gcloud/beta/ai/model-garden/models/deploy create mode 100644 gcloud/beta/ai/model-garden/models/help create mode 100644 gcloud/beta/ai/model-garden/models/list create mode 100644 gcloud/beta/ai/model-garden/models/list-deployment-config create mode 100644 gcloud/beta/compute/instances/report-host-as-faulty create mode 100644 gcloud/beta/memorystore/instances/reschedule-maintenance create mode 100644 gcloud/beta/network-connectivity/hubs/accept-spoke-update create mode 100644 gcloud/beta/network-connectivity/hubs/reject-spoke-update create mode 100644 gcloud/compute/instances/report-host-as-faulty create mode 100644 gcloud/memorystore/instances/reschedule-maintenance create mode 100644 gcloud/network-connectivity/hubs/accept-spoke-update create mode 100644 gcloud/network-connectivity/hubs/reject-spoke-update diff --git a/gcloud/_version b/gcloud/_version index e0fb69340..c8e58b90b 100644 --- a/gcloud/_version +++ b/gcloud/_version @@ -1,8 +1,8 @@ -Google Cloud SDK 514.0.0 -alpha 2025.03.07 -beta 2025.03.07 +Google Cloud SDK 515.0.0 +alpha 2025.03.14 +beta 2025.03.14 bq 2.1.14 bundled-python3-unix 3.12.8 -core 2025.03.07 +core 2025.03.14 gcloud-crc32c 1.0.0 gsutil 5.33 diff --git a/gcloud/alloydb/instances/create b/gcloud/alloydb/instances/create index 8268fa20b..8c12faea3 100644 --- a/gcloud/alloydb/instances/create +++ b/gcloud/alloydb/instances/create @@ -14,7 +14,7 @@ SYNOPSIS [--insights-config-query-string-length=INSIGHTS_CONFIG_QUERY_STRING_LENGTH] [--[no-]insights-config-record-application-tags] [--[no-]insights-config-record-client-address] - [--[no-]outbound-public-ip] + [--machine-type=MACHINE_TYPE] [--[no-]outbound-public-ip] [--psc-network-attachment-uri=PSC_NETWORK_ATTACHMENT_URI] [--read-pool-node-count=READ_POOL_NODE_COUNT] [--[no-]require-connectors] @@ -45,9 +45,15 @@ REQUIRED FLAGS --cpu-count=CPU_COUNT Whole number value indicating how many vCPUs the machine should - contain. Each vCPU count corresponds to a N2 high-mem machine: - (https://cloud.google.com/compute/docs/general-purpose-machines#n2_machines). - CPU_COUNT must be one of: 1, 2, 4, 8, 16, 32, 64, 96, 128. + contain. If the instance does not have a machine-type, the vCPU count + will be used to determine the machine type where each vCPU corresponds + to an N2 high-mem machine: + (https://cloud.google.com/compute/docs/general-purpose-machines#n2_machine_types). + where CPU_COUNT can be one of: 2, 4, 8, 16, 32, 64, 96, 128. If the + instance has a machine-type, cpu-count must have the same value as the + vCPU count in the machine-type. Eg: if machine-type is + c4a-highmem-4-lssd, cpu-count must be 4. CPU_COUNT must be one of: 1, + 2, 4, 8, 16, 32, 48, 64, 72, 96, 128. --instance-type=INSTANCE_TYPE Specifies instance type. INSTANCE_TYPE must be one of: @@ -133,6 +139,14 @@ OPTIONAL FLAGS Use --insights-config-record-client-address to enable and --no-insights-config-record-client-address to disable. + --machine-type=MACHINE_TYPE + Specifies machine type for the instance. MACHINE_TYPE must be one of: + n2-highmem-2, n2-highmem-4, n2-highmem-8, n2-highmem-16, n2-highmem-32, + n2-highmem-64, n2-highmem-96, n2-highmem-128, c4a-highmem-1, + c4a-highmem-4-lssd, c4a-highmem-8-lssd, c4a-highmem-16-lssd, + c4a-highmem-32-lssd, c4a-highmem-48-lssd, c4a-highmem-64-lssd, + c4a-highmem-72-lssd. + --[no-]outbound-public-ip Add outbound Public IP connectivity to an AlloyDB instance. Use --outbound-public-ip to enable and --no-outbound-public-ip to disable. diff --git a/gcloud/alloydb/instances/update b/gcloud/alloydb/instances/update index cad637a80..11304c02a 100644 --- a/gcloud/alloydb/instances/update +++ b/gcloud/alloydb/instances/update @@ -14,7 +14,7 @@ SYNOPSIS [--insights-config-query-string-length=INSIGHTS_CONFIG_QUERY_STRING_LENGTH] [--[no-]insights-config-record-application-tags] [--[no-]insights-config-record-client-address] - [--[no-]outbound-public-ip] + [--machine-type=MACHINE_TYPE] [--[no-]outbound-public-ip] [--psc-network-attachment-uri=PSC_NETWORK_ATTACHMENT_URI] [--read-pool-node-count=READ_POOL_NODE_COUNT] [--[no-]require-connectors] [--ssl-mode=SSL_MODE] @@ -88,9 +88,15 @@ OPTIONAL FLAGS --cpu-count=CPU_COUNT Whole number value indicating how many vCPUs the machine should - contain. Each vCPU count corresponds to a N2 high-mem machine: - (https://cloud.google.com/compute/docs/general-purpose-machines#n2_machines). - CPU_COUNT must be one of: 1, 2, 4, 8, 16, 32, 64, 96, 128. + contain. If the instance does not have a machine-type, the vCPU count + will be used to determine the machine type where each vCPU corresponds + to an N2 high-mem machine: + (https://cloud.google.com/compute/docs/general-purpose-machines#n2_machine_types). + where CPU_COUNT can be one of: 2, 4, 8, 16, 32, 64, 96, 128. If the + instance has a machine-type, cpu-count must have the same value as the + vCPU count in the machine-type. Eg: if machine-type is + c4a-highmem-4-lssd, cpu-count must be 4. CPU_COUNT must be one of: 1, + 2, 4, 8, 16, 32, 48, 64, 72, 96, 128. --database-flags=FLAG=VALUE,[FLAG=VALUE,...] Comma-separated list of database flags to set on the instance. Use an @@ -121,6 +127,14 @@ OPTIONAL FLAGS Use --insights-config-record-client-address to enable and --no-insights-config-record-client-address to disable. + --machine-type=MACHINE_TYPE + Specifies machine type for the instance. MACHINE_TYPE must be one of: + n2-highmem-2, n2-highmem-4, n2-highmem-8, n2-highmem-16, n2-highmem-32, + n2-highmem-64, n2-highmem-96, n2-highmem-128, c4a-highmem-1, + c4a-highmem-4-lssd, c4a-highmem-8-lssd, c4a-highmem-16-lssd, + c4a-highmem-32-lssd, c4a-highmem-48-lssd, c4a-highmem-64-lssd, + c4a-highmem-72-lssd. + --[no-]outbound-public-ip Add outbound Public IP connectivity to an AlloyDB instance. Use --outbound-public-ip to enable and --no-outbound-public-ip to disable. diff --git a/gcloud/alpha/ai/endpoints/deploy-model b/gcloud/alpha/ai/endpoints/deploy-model index 42019339a..695fbcfa8 100644 --- a/gcloud/alpha/ai/endpoints/deploy-model +++ b/gcloud/alpha/ai/endpoints/deploy-model @@ -77,9 +77,10 @@ OPTIONAL FLAGS type The type of the accelerator. Choices are 'nvidia-a100-80gb', - 'nvidia-h100-80gb', 'nvidia-h100-mega-80gb', 'nvidia-l4', - 'nvidia-tesla-a100', 'nvidia-tesla-k80', 'nvidia-tesla-p100', - 'nvidia-tesla-p4', 'nvidia-tesla-t4', 'nvidia-tesla-v100'. + 'nvidia-h100-80gb', 'nvidia-h100-mega-80gb', 'nvidia-h200-141gb', + 'nvidia-l4', 'nvidia-tesla-a100', 'nvidia-tesla-k80', + 'nvidia-tesla-p100', 'nvidia-tesla-p4', 'nvidia-tesla-t4', + 'nvidia-tesla-v100'. count The number of accelerators to attach to each machine running the diff --git a/gcloud/alpha/ai/endpoints/list b/gcloud/alpha/ai/endpoints/list index 546acac60..b63544427 100644 --- a/gcloud/alpha/ai/endpoints/list +++ b/gcloud/alpha/ai/endpoints/list @@ -2,8 +2,9 @@ NAME gcloud alpha ai endpoints list - list existing Vertex AI endpoints SYNOPSIS - gcloud alpha ai endpoints list [--region=REGION] [--filter=EXPRESSION] - [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + gcloud alpha ai endpoints list [--list-model-garden-endpoints-only] + [--region=REGION] [--filter=EXPRESSION] [--limit=LIMIT] + [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] EXAMPLES @@ -12,7 +13,16 @@ EXAMPLES $ gcloud alpha ai endpoints list --project=example \ --region=us-central1 + To list the endpoints under project example in region us-central1 that are + created from Model Garden, run: + + $ gcloud alpha ai endpoints list --project=example \ + --region=us-central1 --list-model-garden-endpoints-only + FLAGS + --list-model-garden-endpoints-only + Whether to only list endpoints created from Model Garden. + Region resource - Cloud region to list endpoints. This represents a Cloud resource. (NOTE) Some attributes are not given arguments in this group but can be set in other ways. diff --git a/gcloud/alpha/ai/help b/gcloud/alpha/ai/help index ce321030a..ad74fe92d 100644 --- a/gcloud/alpha/ai/help +++ b/gcloud/alpha/ai/help @@ -30,6 +30,9 @@ GROUPS indexes (ALPHA) Manage Vertex AI indexes. + model-garden + (ALPHA) Interact with and manage resources in Vertex Model Garden. + model-monitoring-jobs (ALPHA) Manage Vertex AI model monitoring jobs. diff --git a/gcloud/alpha/ai/model-garden/help b/gcloud/alpha/ai/model-garden/help new file mode 100644 index 000000000..2aca0f266 --- /dev/null +++ b/gcloud/alpha/ai/model-garden/help @@ -0,0 +1,29 @@ +NAME + gcloud alpha ai model-garden - interact with and manage resources in Vertex + Model Garden + +SYNOPSIS + gcloud alpha ai model-garden GROUP [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Interact with and manage resources in Vertex Model Garden. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +GROUPS + GROUP is one of the following: + + models + (ALPHA) List and use Model Garden models. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud beta ai model-garden + diff --git a/gcloud/alpha/ai/model-garden/models/deploy b/gcloud/alpha/ai/model-garden/models/deploy new file mode 100644 index 000000000..a038faf52 --- /dev/null +++ b/gcloud/alpha/ai/model-garden/models/deploy @@ -0,0 +1,199 @@ +NAME + gcloud alpha ai model-garden models deploy - deploy a model in Model Garden + to a Vertex AI endpoint + +SYNOPSIS + gcloud alpha ai model-garden models deploy --model=MODEL + [--accelerator-type=ACCELERATOR_TYPE] [--accept-eula] [--asynchronous] + [--container-args=[ARG,...]] [--container-command=[COMMAND,...]] + [--container-deployment-timeout-seconds=CONTAINER_DEPLOYMENT_TIMEOUT_SECONDS] + [--container-env-vars=[KEY=VALUE,...]] + [--container-grpc-ports=[PORT,...]] + [--container-health-probe-exec=[HEALTH_PROBE_EXEC,...]] + [--container-health-probe-period-seconds=CONTAINER_HEALTH_PROBE_PERIOD_SECONDS] + [--container-health-probe-timeout-seconds=CONTAINER_HEALTH_PROBE_TIMEOUT_SECONDS] + [--container-health-route=CONTAINER_HEALTH_ROUTE] + [--container-image-uri=CONTAINER_IMAGE_URI] + [--container-ports=[PORT,...]] + [--container-predict-route=CONTAINER_PREDICT_ROUTE] + [--container-shared-memory-size-mb=CONTAINER_SHARED_MEMORY_SIZE_MB] + [--container-startup-probe-exec=[STARTUP_PROBE_EXEC,...]] + [--container-startup-probe-period-seconds=CONTAINER_STARTUP_PROBE_PERIOD_SECONDS] + [--container-startup-probe-timeout-seconds=CONTAINER_STARTUP_PROBE_TIMEOUT_SECONDS] + [--enable-fast-tryout] [--endpoint-display-name=ENDPOINT_DISPLAY_NAME] + [--hugging-face-access-token=HUGGING_FACE_ACCESS_TOKEN] + [--machine-type=MACHINE_TYPE] [--region=REGION] + [--reservation-affinity=[key=KEY], + [reservation-affinity-type=RESERVATION-AFFINITY-TYPE], + [values=VALUES]] [--spot] [--use-dedicated-endpoint] + [GCLOUD_WIDE_FLAG ...] + +EXAMPLES + To deploy a Model Garden model google/gemma2/gemma2-9b under project + example in region us-central1, run: + + $ gcloud ai model-garden models deploy \ + --model=google/gemma2@gemma-2-9b --project=example \ + --region=us-central1 + + To deploy a Hugging Face model meta-llama/Meta-Llama-3-8B under project + example in region us-central1, run: + + $ gcloud ai model-garden models deploy \ + --model=meta-llama/Meta-Llama-3-8B \ + --hugging-face-access-token={hf_token} --project=example \ + --region=us-central1 + +REQUIRED FLAGS + --model=MODEL + The model to be deployed. If it is a Model Garden model, it should be + in the format of {publisher_name}/{model_name}@{model_version_name}, + e.g. google/gemma2@gemma-2-2b. If it is a Hugging Face model, it should + be in the convention of Hugging Face models, e.g. + meta-llama/Meta-Llama-3-8B. + +OPTIONAL FLAGS + --accelerator-type=ACCELERATOR_TYPE + The accelerator type to serve the model. It should be a supported + accelerator type from the verified deployment configurations of the + model. Use gcloud ai model-garden models list-deployment-config to + check the supported accelerator types. + + --accept-eula + When set, the user accepts the End User License Agreement (EULA) of the + model. + + --asynchronous + If set to true, the command will terminate immediately and not keep + polling the operation status. + + --container-args=[ARG,...] + Comma-separated arguments passed to the command run by the container + image. If not specified and no --command is provided, the container + image's default command is used. + + --container-command=[COMMAND,...] + Entrypoint for the container image. If not specified, the container + image's default entrypoint is run. + + --container-deployment-timeout-seconds=CONTAINER_DEPLOYMENT_TIMEOUT_SECONDS + Deployment timeout in seconds. + + --container-env-vars=[KEY=VALUE,...] + List of key-value pairs to set as environment variables. + + --container-grpc-ports=[PORT,...] + Container ports to receive grpc requests at. Must be a number between 1 + and 65535, inclusive. + + --container-health-probe-exec=[HEALTH_PROBE_EXEC,...] + Exec specifies the action to take. Used by health probe. An example of + this argument would be ["cat", "/tmp/healthy"]. + + --container-health-probe-period-seconds=CONTAINER_HEALTH_PROBE_PERIOD_SECONDS + How often (in seconds) to perform the health probe. Default to 10 + seconds. Minimum value is 1. + + --container-health-probe-timeout-seconds=CONTAINER_HEALTH_PROBE_TIMEOUT_SECONDS + Number of seconds after which the health probe times out. Defaults to 1 + second. Minimum value is 1. + + --container-health-route=CONTAINER_HEALTH_ROUTE + HTTP path to send health checks to inside the container. + + --container-image-uri=CONTAINER_IMAGE_URI + URI of the Model serving container file in the Container Registry (e.g. + gcr.io/myproject/server:latest). + + --container-ports=[PORT,...] + Container ports to receive http requests at. Must be a number between 1 + and 65535, inclusive. + + --container-predict-route=CONTAINER_PREDICT_ROUTE + HTTP path to send prediction requests to inside the container. + + --container-shared-memory-size-mb=CONTAINER_SHARED_MEMORY_SIZE_MB + The amount of the VM memory to reserve as the shared memory for the + model in megabytes. + + --container-startup-probe-exec=[STARTUP_PROBE_EXEC,...] + Exec specifies the action to take. Used by startup probe. An example of + this argument would be ["cat", "/tmp/healthy"]. + + --container-startup-probe-period-seconds=CONTAINER_STARTUP_PROBE_PERIOD_SECONDS + How often (in seconds) to perform the startup probe. Default to 10 + seconds. Minimum value is 1. + + --container-startup-probe-timeout-seconds=CONTAINER_STARTUP_PROBE_TIMEOUT_SECONDS + Number of seconds after which the startup probe times out. Defaults to + 1 second. Minimum value is 1. + + --enable-fast-tryout + If True, model will be deployed using faster deployment path. Useful + for quick experiments. Not for production workloads. Only available for + most popular models with certain machine types. + + --endpoint-display-name=ENDPOINT_DISPLAY_NAME + Display name of the endpoint with the deployed model. + + --hugging-face-access-token=HUGGING_FACE_ACCESS_TOKEN + The access token from Hugging Face needed to read the model artifacts + of gated models. It is only needed when the Hugging Face model to + deploy is gated. + + --machine-type=MACHINE_TYPE + The machine type to deploy the model to. It should be a supported + machine type from the deployment configurations of the model. Use + gcloud ai model-garden models list-deployment-config to check the + supported machine types. + + Region resource - Cloud region to deploy the model. This represents a + Cloud resource. (NOTE) Some attributes are not given arguments in this + group but can be set in other ways. + + To set the project attribute: + ◆ provide the argument --region on the command line with a fully + specified name; + ◆ set the property ai/region with a fully specified name; + ◆ choose one from the prompted list of available regions with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + --region=REGION + ID of the region or fully qualified identifier for the region. + + To set the region attribute: + ▸ provide the argument --region on the command line; + ▸ set the property ai/region; + ▸ choose one from the prompted list of available regions. + + --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. + + --spot + If true, schedule the deployment workload on Spot VM. + + --use-dedicated-endpoint + If true, the endpoint will be exposed through a dedicated DNS. Your + request to the dedicated DNS will be isolated from other users' traffic + and will have better performance and reliability. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud beta ai model-garden models deploy + diff --git a/gcloud/alpha/ai/model-garden/models/help b/gcloud/alpha/ai/model-garden/models/help new file mode 100644 index 000000000..6c7d8ee3b --- /dev/null +++ b/gcloud/alpha/ai/model-garden/models/help @@ -0,0 +1,35 @@ +NAME + gcloud alpha ai model-garden models - list and use Model Garden models + +SYNOPSIS + gcloud alpha ai model-garden models COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) List and use Model Garden models. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + deploy + (ALPHA) Deploy a model in Model Garden to a Vertex AI endpoint. + + list + (ALPHA) List the publisher models in Model Garden. + + list-deployment-config + (ALPHA) List the machine specifications supported by and verified for a + model in Model Garden. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud beta ai model-garden models + diff --git a/gcloud/alpha/ai/model-garden/models/list b/gcloud/alpha/ai/model-garden/models/list new file mode 100644 index 000000000..633441782 --- /dev/null +++ b/gcloud/alpha/ai/model-garden/models/list @@ -0,0 +1,70 @@ +NAME + gcloud alpha ai model-garden models list - list the publisher models in + Model Garden + +SYNOPSIS + gcloud alpha ai model-garden models list + [--list-supported-hugging-face-models] [--model-filter=MODEL_FILTER] + [--filter=EXPRESSION] [--limit=LIMIT; default=1000] + [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) This command lists either all models in Model Garden or all Hugging + Face models supported by Model Garden. + + Note: Since the number of Hugging Face models is large, the default limit + is set to 500 with a page size of 100 when listing supported Hugging Face + models. To override the limit or page size, specify the --limit or + --page-size flags, respectively. To list all models in Model Garden, use + --limit=unlimited. + +FLAGS + --list-supported-hugging-face-models + Whether to only list supported Hugging Face models. + + --model-filter=MODEL_FILTER + Filter to apply to the model names or the display names of the list of + models. + +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; default=1000 + Maximum number of resources to list. The default is 1000. This flag + interacts with other flags that are applied in this order: --flatten, + --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud beta ai model-garden models list + diff --git a/gcloud/alpha/ai/model-garden/models/list-deployment-config b/gcloud/alpha/ai/model-garden/models/list-deployment-config new file mode 100644 index 000000000..57d1816bd --- /dev/null +++ b/gcloud/alpha/ai/model-garden/models/list-deployment-config @@ -0,0 +1,70 @@ +NAME + gcloud alpha ai model-garden models list-deployment-config - list the + machine specifications supported by and verified for a model in Model + Garden + +SYNOPSIS + gcloud alpha ai model-garden models list-deployment-config --model=MODEL + [--hugging-face-access-token=HUGGING_FACE_ACCESS_TOKEN] + [--filter=EXPRESSION] [--sort-by=[FIELD,...]] [GCLOUD_WIDE_FLAG ...] + +EXAMPLES + To list the supported machine specifications for google/gemma2@gemma-2-9b, + run: + + $ gcloud ai model-garden models list-deployment-config \ + --model=google/gemma2@gemma-2-9b + + To list the supported machine specifications for a Hugging Face model + meta-llama/Meta-Llama-3-8B, run: + + $ gcloud ai model-garden models list-deployment-config \ + --model=meta-llama/Meta-Llama-3-8B + +REQUIRED FLAGS + --model=MODEL + The model to be deployed. If it is a Model Garden model, it should be + in the format of {publisher_name}/{model_name}@{model_version_name}, + e.g. google/gemma2@gemma-2-2b. If it is a Hugging Face model, it should + be in the convention of Hugging Face models, e.g. + meta-llama/Meta-Llama-3-8B. + +FLAGS + --hugging-face-access-token=HUGGING_FACE_ACCESS_TOKEN + The access token from Hugging Face needed to read the model artifacts + of gated models in order to generate the deployment configs. It is only + needed when the Hugging Face model to deploy is gated and not verified + by Model Garden. You can use the gcloud ai alpha/beta model-garden + models list command to find out which ones are verified by Model + Garden. + +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. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud beta ai model-garden models list-deployment-config + diff --git a/gcloud/alpha/alloydb/instances/create b/gcloud/alpha/alloydb/instances/create index fa05fbc4e..09bdc8ccf 100644 --- a/gcloud/alpha/alloydb/instances/create +++ b/gcloud/alpha/alloydb/instances/create @@ -24,7 +24,7 @@ SYNOPSIS [--insights-config-query-string-length=INSIGHTS_CONFIG_QUERY_STRING_LENGTH] [--[no-]insights-config-record-application-tags] [--[no-]insights-config-record-client-address] - [--[no-]observability-config-enabled] + [--machine-type=MACHINE_TYPE] [--[no-]observability-config-enabled] [--observability-config-max-query-string-length=OBSERVABILITY_CONFIG_MAX_QUERY_STRING_LENGTH] [--[no-]observability-config-preserve-comments] [--observability-config-query-plans-per-minute=OBSERVABILITY_CONFIG_QUERY_PLANS_PER_MINUTE] @@ -62,9 +62,15 @@ REQUIRED FLAGS --cpu-count=CPU_COUNT Whole number value indicating how many vCPUs the machine should - contain. Each vCPU count corresponds to a N2 high-mem machine: - (https://cloud.google.com/compute/docs/general-purpose-machines#n2_machines). - CPU_COUNT must be one of: 1, 2, 4, 8, 16, 32, 64, 96, 128. + contain. If the instance does not have a machine-type, the vCPU count + will be used to determine the machine type where each vCPU corresponds + to an N2 high-mem machine: + (https://cloud.google.com/compute/docs/general-purpose-machines#n2_machine_types). + where CPU_COUNT can be one of: 2, 4, 8, 16, 32, 64, 96, 128. If the + instance has a machine-type, cpu-count must have the same value as the + vCPU count in the machine-type. Eg: if machine-type is + c4a-highmem-4-lssd, cpu-count must be 4. CPU_COUNT must be one of: 1, + 2, 4, 8, 16, 32, 48, 64, 72, 96, 128. --instance-type=INSTANCE_TYPE Specifies instance type. INSTANCE_TYPE must be one of: @@ -187,6 +193,14 @@ OPTIONAL FLAGS Use --insights-config-record-client-address to enable and --no-insights-config-record-client-address to disable. + --machine-type=MACHINE_TYPE + Specifies machine type for the instance. MACHINE_TYPE must be one of: + n2-highmem-2, n2-highmem-4, n2-highmem-8, n2-highmem-16, n2-highmem-32, + n2-highmem-64, n2-highmem-96, n2-highmem-128, c4a-highmem-1, + c4a-highmem-4-lssd, c4a-highmem-8-lssd, c4a-highmem-16-lssd, + c4a-highmem-32-lssd, c4a-highmem-48-lssd, c4a-highmem-64-lssd, + c4a-highmem-72-lssd. + --[no-]observability-config-enabled Enable enhanced query insights feature. Use --observability-config-enabled to enable and diff --git a/gcloud/alpha/alloydb/instances/update b/gcloud/alpha/alloydb/instances/update index 878174f31..3a49f2b7c 100644 --- a/gcloud/alpha/alloydb/instances/update +++ b/gcloud/alpha/alloydb/instances/update @@ -24,7 +24,7 @@ SYNOPSIS [--insights-config-query-string-length=INSIGHTS_CONFIG_QUERY_STRING_LENGTH] [--[no-]insights-config-record-application-tags] [--[no-]insights-config-record-client-address] - [--[no-]observability-config-enabled] + [--machine-type=MACHINE_TYPE] [--[no-]observability-config-enabled] [--observability-config-max-query-string-length=OBSERVABILITY_CONFIG_MAX_QUERY_STRING_LENGTH] [--[no-]observability-config-preserve-comments] [--observability-config-query-plans-per-minute=OBSERVABILITY_CONFIG_QUERY_PLANS_PER_MINUTE] @@ -136,9 +136,15 @@ OPTIONAL FLAGS --cpu-count=CPU_COUNT Whole number value indicating how many vCPUs the machine should - contain. Each vCPU count corresponds to a N2 high-mem machine: - (https://cloud.google.com/compute/docs/general-purpose-machines#n2_machines). - CPU_COUNT must be one of: 1, 2, 4, 8, 16, 32, 64, 96, 128. + contain. If the instance does not have a machine-type, the vCPU count + will be used to determine the machine type where each vCPU corresponds + to an N2 high-mem machine: + (https://cloud.google.com/compute/docs/general-purpose-machines#n2_machine_types). + where CPU_COUNT can be one of: 2, 4, 8, 16, 32, 64, 96, 128. If the + instance has a machine-type, cpu-count must have the same value as the + vCPU count in the machine-type. Eg: if machine-type is + c4a-highmem-4-lssd, cpu-count must be 4. CPU_COUNT must be one of: 1, + 2, 4, 8, 16, 32, 48, 64, 72, 96, 128. --database-flags=FLAG=VALUE,[FLAG=VALUE,...] Comma-separated list of database flags to set on the instance. Use an @@ -174,6 +180,14 @@ OPTIONAL FLAGS Use --insights-config-record-client-address to enable and --no-insights-config-record-client-address to disable. + --machine-type=MACHINE_TYPE + Specifies machine type for the instance. MACHINE_TYPE must be one of: + n2-highmem-2, n2-highmem-4, n2-highmem-8, n2-highmem-16, n2-highmem-32, + n2-highmem-64, n2-highmem-96, n2-highmem-128, c4a-highmem-1, + c4a-highmem-4-lssd, c4a-highmem-8-lssd, c4a-highmem-16-lssd, + c4a-highmem-32-lssd, c4a-highmem-48-lssd, c4a-highmem-64-lssd, + c4a-highmem-72-lssd. + --[no-]observability-config-enabled Enable enhanced query insights feature. Use --observability-config-enabled to enable and diff --git a/gcloud/alpha/certificate-manager/certificates/list b/gcloud/alpha/certificate-manager/certificates/list index 5ad22af8a..ba84610b2 100644 --- a/gcloud/alpha/certificate-manager/certificates/list +++ b/gcloud/alpha/certificate-manager/certificates/list @@ -22,7 +22,8 @@ FLAGS To set the project attribute: ◆ provide the argument --location on the command line with a fully specified name; - ◆ default value of location is [global] with a fully specified name; + ◆ if left empty, will use the wildcard '-' to list all locations with a + fully specified name; ◆ provide the argument --project on the command line; ◆ set the property core/project. @@ -31,7 +32,7 @@ FLAGS To set the location attribute: ▸ provide the argument --location on the command line; - ▸ default value of location is [global]. + ▸ if left empty, will use the wildcard '-' to list all locations. LIST COMMAND FLAGS --filter=EXPRESSION diff --git a/gcloud/alpha/certificate-manager/dns-authorizations/list b/gcloud/alpha/certificate-manager/dns-authorizations/list index 291b24579..babc1c012 100644 --- a/gcloud/alpha/certificate-manager/dns-authorizations/list +++ b/gcloud/alpha/certificate-manager/dns-authorizations/list @@ -17,14 +17,15 @@ EXAMPLES $ gcloud alpha certificate-manager dns-authorizations list FLAGS - Location resource - The location (defaults to global) of the resources. - This represents a Cloud resource. (NOTE) Some attributes are not given + Location resource - The location (defaults to '-') of the resources. This + represents a Cloud resource. (NOTE) Some attributes are not given arguments in this group but can be set in other ways. To set the project attribute: ◆ provide the argument --location on the command line with a fully specified name; - ◆ default value of location is [global] with a fully specified name; + ◆ if left empty, will use the wildcard '-' to list all locations with a + fully specified name; ◆ provide the argument --project on the command line; ◆ set the property core/project. @@ -33,7 +34,7 @@ FLAGS To set the location attribute: ▸ provide the argument --location on the command line; - ▸ default value of location is [global]. + ▸ if left empty, will use the wildcard '-' to list all locations. LIST COMMAND FLAGS --filter=EXPRESSION diff --git a/gcloud/alpha/certificate-manager/issuance-configs/list b/gcloud/alpha/certificate-manager/issuance-configs/list index db5a91b3f..76c9a41a1 100644 --- a/gcloud/alpha/certificate-manager/issuance-configs/list +++ b/gcloud/alpha/certificate-manager/issuance-configs/list @@ -17,14 +17,15 @@ EXAMPLES $ gcloud alpha certificate-manager issuance-configs list FLAGS - Location resource - Location (defaults to global) of the resources. This + Location resource - The location (defaults to '-') of the resources. This represents a Cloud resource. (NOTE) Some attributes are not given arguments in this group but can be set in other ways. To set the project attribute: ◆ provide the argument --location on the command line with a fully specified name; - ◆ default value of location is [global] with a fully specified name; + ◆ if left empty, will use the wildcard '-' to list all locations with a + fully specified name; ◆ provide the argument --project on the command line; ◆ set the property core/project. @@ -33,7 +34,7 @@ FLAGS To set the location attribute: ▸ provide the argument --location on the command line; - ▸ default value of location is [global]. + ▸ if left empty, will use the wildcard '-' to list all locations. LIST COMMAND FLAGS --filter=EXPRESSION diff --git a/gcloud/alpha/certificate-manager/trust-configs/list b/gcloud/alpha/certificate-manager/trust-configs/list index 387c3f4e9..77a562a90 100644 --- a/gcloud/alpha/certificate-manager/trust-configs/list +++ b/gcloud/alpha/certificate-manager/trust-configs/list @@ -16,14 +16,15 @@ EXAMPLES $ gcloud alpha certificate-manager trust-configs list FLAGS - Location resource - The location (defaults to global) of the resources. - This represents a Cloud resource. (NOTE) Some attributes are not given + Location resource - The location (defaults to '-') of the resources. This + represents a Cloud resource. (NOTE) Some attributes are not given arguments in this group but can be set in other ways. To set the project attribute: ◆ provide the argument --location on the command line with a fully specified name; - ◆ default value of location is [global] with a fully specified name; + ◆ if left empty, will use the wildcard '-' to list all locations with a + fully specified name; ◆ provide the argument --project on the command line; ◆ set the property core/project. @@ -32,7 +33,7 @@ FLAGS To set the location attribute: ▸ provide the argument --location on the command line; - ▸ default value of location is [global]. + ▸ if left empty, will use the wildcard '-' to list all locations. LIST COMMAND FLAGS --filter=EXPRESSION diff --git a/gcloud/alpha/compute/disks/convert b/gcloud/alpha/compute/disks/convert index 5f3a62a3e..137118121 100644 --- a/gcloud/alpha/compute/disks/convert +++ b/gcloud/alpha/compute/disks/convert @@ -18,11 +18,11 @@ DESCRIPTION https://cloud.google.com/sdk/gcloud/reference/compute/disks/convert. EXAMPLES - The following command converts a PD Standard disk to a Hyperdisk - Throughput: + The following command converts a Persistent Disk volume to a Hyperdisk + Balanced volume: $ gcloud alpha compute disks convert my-disk-1 --zone=ZONE \ - --target-disk-type=hyperdisk-throughput + --target-disk-type=hyperdisk-balanced POSITIONAL ARGUMENTS DISK_NAME diff --git a/gcloud/alpha/compute/disks/update b/gcloud/alpha/compute/disks/update index 7ab045c14..420d8b25d 100644 --- a/gcloud/alpha/compute/disks/update +++ b/gcloud/alpha/compute/disks/update @@ -3,6 +3,7 @@ NAME SYNOPSIS gcloud alpha compute disks update DISK_NAME [--access-mode=ACCESS_MODE] + [--add-guest-os-features=ADD_GUEST_OS_FEATURES] [--provisioned-iops=PROVISIONED_IOPS] [--provisioned-throughput=PROVISIONED_THROUGHPUT] [--size=SIZE] [--update-labels=[KEY=VALUE,...]] @@ -72,6 +73,12 @@ FLAGS used if omitted. ACCESS_MODE must be one of: READ_ONLY_MANY, READ_WRITE_MANY, READ_WRITE_SINGLE. + --add-guest-os-features=ADD_GUEST_OS_FEATURES + Specifies guest OS features to add to the disk. Refer to + https://cloud.google.com/compute/docs/images/create-custom#guest-os-features + for a list of available options. ADD_GUEST_OS_FEATURES must be (only + one value is supported): GVNIC. + --provisioned-iops=PROVISIONED_IOPS Provisioned IOPS of disk to update. Only for use with disks of type hyperdisk-extreme. diff --git a/gcloud/alpha/compute/future-reservations/create b/gcloud/alpha/compute/future-reservations/create index d3890eaf5..aa3f06288 100644 --- a/gcloud/alpha/compute/future-reservations/create +++ b/gcloud/alpha/compute/future-reservations/create @@ -111,7 +111,8 @@ REQUIRED FLAGS size The size of the local SSD in base-2 GB. count - The number of local SSD to use per VM. Default value is 1. + The number of local SSD to use per VM. If you don't specify + this argument, then the default value is 1. --maintenance-freeze-duration=MAINTENANCE_FREEZE_DURATION Specifies the amount of hours after instance creation where the diff --git a/gcloud/alpha/compute/future-reservations/update b/gcloud/alpha/compute/future-reservations/update index 249ed2f0d..77638cf02 100644 --- a/gcloud/alpha/compute/future-reservations/update +++ b/gcloud/alpha/compute/future-reservations/update @@ -6,6 +6,7 @@ SYNOPSIS gcloud alpha compute future-reservations update FUTURE_RESERVATION [--[no-]auto-delete-auto-created-reservations] [--deployment-type=DEPLOYMENT_TYPE] [--description=DESCRIPTION] + [--[no-]enable-emergent-maintenance] [--planning-status=PLANNING_STATUS] [--[no-]require-specific-reservation] [--reservation-name=RESERVATION_NAME] @@ -61,6 +62,12 @@ FLAGS --description=DESCRIPTION An optional description of the future reservation to create. + --[no-]enable-emergent-maintenance + Emergent maintenance flag for the reservation, which enrolls all the + underlying vms, hosts and SB infrastructure to receive emergent + maintenance notifications in advance. Use --enable-emergent-maintenance + to enable and --no-enable-emergent-maintenance to disable. + --planning-status=PLANNING_STATUS The planning status of the future reservation. The default value is DRAFT. While in DRAFT, any changes to the future reservation's @@ -265,7 +272,8 @@ FLAGS size The size of the local SSD in base-2 GB. count - The number of local SSD to use per VM. Default value is 1. + The number of local SSD to use per VM. If you don't specify + this argument, then the default value is 1. Manage the time specific properties for requesting future capacity diff --git a/gcloud/alpha/compute/instance-groups/managed/resize-requests/create b/gcloud/alpha/compute/instance-groups/managed/resize-requests/create index eeccbfdf3..b6ac1333a 100644 --- a/gcloud/alpha/compute/instance-groups/managed/resize-requests/create +++ b/gcloud/alpha/compute/instance-groups/managed/resize-requests/create @@ -4,7 +4,8 @@ NAME SYNOPSIS gcloud alpha compute instance-groups managed resize-requests create NAME - --resize-by=RESIZE_BY --resize-request=RESIZE_REQUEST_NAME + --resize-request=RESIZE_REQUEST_NAME + (--instances=INSTANCE,[INSTANCE,...] | --resize-by=RESIZE_BY) [--requested-run-duration=REQUESTED_RUN_DURATION] [--region=REGION | --zone=ZONE] [GCLOUD_WIDE_FLAG ...] @@ -24,12 +25,20 @@ POSITIONAL ARGUMENTS Name of the managed instance group to operate on. REQUIRED FLAGS - --resize-by=RESIZE_BY - The number of VMs to resize managed instance group by. - --resize-request=RESIZE_REQUEST_NAME The name of the resize request to create. + Exactly one of these must be specified: + + --instances=INSTANCE,[INSTANCE,...] + The names of instances to be created by this resize request. The + number of names specified determines the number of instances to + create. The group's target size will be increased by this number. + + --resize-by=RESIZE_BY + The number of instances to be created by this resize request. The + group's target size will be increased by this number. + OPTIONAL FLAGS --requested-run-duration=REQUESTED_RUN_DURATION The time you need the requested VMs to run before being automatically diff --git a/gcloud/alpha/compute/instances/help b/gcloud/alpha/compute/instances/help index e8ce7ce03..d8a6ebd3c 100644 --- a/gcloud/alpha/compute/instances/help +++ b/gcloud/alpha/compute/instances/help @@ -142,6 +142,9 @@ COMMANDS remove-tags (ALPHA) Remove tags from Compute Engine virtual machine instances. + report-host-as-faulty + (ALPHA) Report a host as faulty to start the repair process. + reset (ALPHA) Reset a virtual machine instance. diff --git a/gcloud/alpha/compute/instances/report-host-as-faulty b/gcloud/alpha/compute/instances/report-host-as-faulty new file mode 100644 index 000000000..648694922 --- /dev/null +++ b/gcloud/alpha/compute/instances/report-host-as-faulty @@ -0,0 +1,83 @@ +NAME + gcloud alpha compute instances report-host-as-faulty - report a host as + faulty to start the repair process + +SYNOPSIS + gcloud alpha compute instances report-host-as-faulty INSTANCE_NAME + --disruption-schedule=DISRUPTION_SCHEDULE + --fault-reasons=[behavior=BEHAVIOR],[description=DESCRIPTION] + [--zone=ZONE] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) gcloud alpha compute instances report-host-as-faulty is used to + report a host as faulty to start the repair process. + +EXAMPLES + To report a host as faulty for an instance named test-instance, run: + + $ gcloud alpha compute instances report-host-as-faulty \ + test-instance \ + --fault-reasons=behavior=SILENT_DATA_CORRUPTION,\ + description="affecting our ML job" --disruption-schedule=IMMEDIATE + +POSITIONAL ARGUMENTS + INSTANCE_NAME + Name of the instance to operate on. For details on valid instance + names, refer to the criteria documented under the field 'name' at: + https://cloud.google.com/compute/docs/reference/rest/v1/instances + +REQUIRED FLAGS + --disruption-schedule=DISRUPTION_SCHEDULE + Specifies the timing for initiating the fault reporting process. The + default value is ['IMMEDIATE'] which initiates the process right away. + DISRUPTION_SCHEDULE must be (only one value is supported): IMMEDIATE. + + --fault-reasons=[behavior=BEHAVIOR],[description=DESCRIPTION] + Specified and can include one or more of the following types: + ['BEHAVIOR_UNSPECIFIED', 'PERFORMANCE', 'SILENT_DATA_CORRUPTION', + 'UNRECOVERABLE_GPU_ERROR']. This helps categorize the nature of the + fault being reported. + +OPTIONAL FLAGS + --zone=ZONE + Zone of the instance to operate on. If not specified, you might be + prompted to select a zone (interactive mode only). gcloud attempts to + identify the appropriate zone by searching for resources in your + currently active project. If the zone cannot be determined, gcloud + prompts you for a selection with all available Google Cloud Platform + zones. + + To avoid prompting when this flag is omitted, the user can set the + compute/zone property: + + $ gcloud config set compute/zone ZONE + + A list of zones can be fetched by running: + + $ gcloud compute zones list + + To unset the property, run: + + $ gcloud config unset compute/zone + + Alternatively, the zone can be stored in the environment variable + CLOUDSDK_COMPUTE_ZONE. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. These variants are also available: + + $ gcloud compute instances report-host-as-faulty + + $ gcloud beta compute instances report-host-as-faulty + diff --git a/gcloud/alpha/compute/interconnects/create b/gcloud/alpha/compute/interconnects/create index 0aeeef022..96298d8ab 100644 --- a/gcloud/alpha/compute/interconnects/create +++ b/gcloud/alpha/compute/interconnects/create @@ -62,6 +62,8 @@ REQUIRED FLAGS 100Gbps Ethernet, LR Optics. LINK_TYPE_ETHERNET_10G_LR 10Gbps Ethernet, LR Optics. + LINK_TYPE_ETHERNET_400G_LR4 + 400Gbps Ethernet, LR4 Optics. --location=LOCATION The location for the interconnect. The locations can be listed by using diff --git a/gcloud/alpha/compute/networks/subnets/create b/gcloud/alpha/compute/networks/subnets/create index 927f9771d..d518cbf05 100644 --- a/gcloud/alpha/compute/networks/subnets/create +++ b/gcloud/alpha/compute/networks/subnets/create @@ -8,8 +8,9 @@ SYNOPSIS [--description=DESCRIPTION] [--enable-flow-logs] [--enable-private-ip-google-access] [--external-ipv6-prefix=EXTERNAL_IPV6_PREFIX] - [--flow-sampling=FLOW_SAMPLING] [--ip-collection=IP_COLLECTION] - [--ipv6-access-type=IPV6_ACCESS_TYPE] + [--flow-sampling=FLOW_SAMPLING] + [--internal-ipv6-prefix=INTERNAL_IPV6_PREFIX] + [--ip-collection=IP_COLLECTION] [--ipv6-access-type=IPV6_ACCESS_TYPE] [--logging-aggregation-interval=LOGGING_AGGREGATION_INTERVAL] [--logging-filter-expr=LOGGING_FILTER_EXPR] [--logging-flow-sampling=LOGGING_FLOW_SAMPLING] @@ -77,6 +78,12 @@ OPTIONAL FLAGS collected logs are reported and 0.0 means no logs are reported. Default is 0.5 which means half of all collected logs are reported. + --internal-ipv6-prefix=INTERNAL_IPV6_PREFIX + Set internal IPv6 prefix to be allocated for this subnetwork. When ULA + is enabled, the prefix will be ignored. + + For example, --internal-ipv6-prefix 2600:1901:0:0:0:0:0:0/64 + --ip-collection=IP_COLLECTION Resource reference to a public delegated prefix. The PublicDelegatedPrefix must be a sub-prefix in diff --git a/gcloud/alpha/compute/reservations/create b/gcloud/alpha/compute/reservations/create index 98a01ef39..21354e845 100644 --- a/gcloud/alpha/compute/reservations/create +++ b/gcloud/alpha/compute/reservations/create @@ -114,7 +114,8 @@ REQUIRED FLAGS size The size of the local SSD in base-2 GB. count - The number of local SSD to use per VM. Default value is 1. + The number of local SSD to use per VM. If you don't specify + this argument, then the default value is 1. --maintenance-freeze-duration=MAINTENANCE_FREEZE_DURATION Specifies the amount of hours after instance creation where the diff --git a/gcloud/alpha/compute/reservations/update b/gcloud/alpha/compute/reservations/update index 778d30845..f9d01a55a 100644 --- a/gcloud/alpha/compute/reservations/update +++ b/gcloud/alpha/compute/reservations/update @@ -5,6 +5,7 @@ NAME SYNOPSIS gcloud alpha compute reservations update RESERVATION [--add-share-with=PROJECT,[PROJECT,...]] + [--[no-]enable-emergent-maintenance] [--remove-share-with=PROJECT,[PROJECT,...]] [--reservation-sharing-policy=RESERVATION_SHARING_POLICY] [--share-with=SHARE_WITH,[SHARE_WITH,...]] [--vm-count=VM_COUNT] @@ -55,6 +56,12 @@ FLAGS reservation is shared with. List must contain project IDs or project numbers. + --[no-]enable-emergent-maintenance + The emergent maintenance flag for the reservation, which enrolls all + the underlying vms, hosts and SB infrastructure to receive emergent + maintenance notifications in advance. Use --enable-emergent-maintenance + to enable and --no-enable-emergent-maintenance to disable. + --remove-share-with=PROJECT,[PROJECT,...] A list of specific projects to remove from the list of projects that this reservation is shared with. List must contain project IDs or diff --git a/gcloud/alpha/compute/resource-policies/create/group-placement b/gcloud/alpha/compute/resource-policies/create/group-placement index f47b697c4..4b11a2ec6 100644 --- a/gcloud/alpha/compute/resource-policies/create/group-placement +++ b/gcloud/alpha/compute/resource-policies/create/group-placement @@ -6,9 +6,9 @@ SYNOPSIS gcloud alpha compute resource-policies create group-placement NAME [--availability-domain-count=AVAILABILITY_DOMAIN_COUNT] [--collocation=COLLOCATION] [--description=DESCRIPTION] - [--max-distance=MAX_DISTANCE] [--region=REGION] [--scope=SCOPE] - [--tpu-topology=TPU_TOPOLOGY] [--vm-count=VM_COUNT] - [GCLOUD_WIDE_FLAG ...] + [--gpu-topology=GPU_TOPOLOGY] [--max-distance=MAX_DISTANCE] + [--region=REGION] [--scope=SCOPE] [--tpu-topology=TPU_TOPOLOGY] + [--vm-count=VM_COUNT] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Create a Compute Engine Group Placement Resource Policy. @@ -43,6 +43,10 @@ FLAGS --description=DESCRIPTION An optional, textual description for the backend. + --gpu-topology=GPU_TOPOLOGY + Specifies the shape of the GPU slice, in slice based GPU families eg. + A4X. + --max-distance=MAX_DISTANCE Specifies the number of max logical switches between VMs. diff --git a/gcloud/alpha/compute/resource-policies/create/help b/gcloud/alpha/compute/resource-policies/create/help index 2a8b704b7..6ee3dcb5f 100644 --- a/gcloud/alpha/compute/resource-policies/create/help +++ b/gcloud/alpha/compute/resource-policies/create/help @@ -35,6 +35,9 @@ COMMANDS snapshot-schedule (ALPHA) Create a Compute Engine Snapshot Schedule Resource Policy. + workload-policy + (ALPHA) Create a Compute Engine workload resource policy. + NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct diff --git a/gcloud/alpha/compute/resource-policies/create/workload-policy b/gcloud/alpha/compute/resource-policies/create/workload-policy new file mode 100644 index 000000000..eb063dea8 --- /dev/null +++ b/gcloud/alpha/compute/resource-policies/create/workload-policy @@ -0,0 +1,93 @@ +NAME + gcloud alpha compute resource-policies create workload-policy - create a + Compute Engine workload resource policy + +SYNOPSIS + gcloud alpha compute resource-policies create workload-policy NAME + --type=TYPE [--description=DESCRIPTION] [--region=REGION] + [--accelerator-topology=ACCELERATOR_TOPOLOGY + | --max-topology-distance=MAX_TOPOLOGY_DISTANCE] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Create a Compute Engine workload resource policy. + +POSITIONAL ARGUMENTS + NAME + Name of the resource policy to operate on. + +REQUIRED FLAGS + --type=TYPE + Type of the workload policy defining the high-level intent of the + cluster. TYPE must be one of: + + HIGH_AVAILABILITY + For workloads that aim to be highly available. Common examples are + web / ML serving, or distributed database clusters. Compute Engine + spreads VMs at best-effort to improve reliability of the + distributed infrastructure. + HIGH_THROUGHPUT + For high throughput distributed workloads eg. HPC or ML training. + Compute Engine collocates VMs at best-effort to reduce network + latency between VMs. + +OPTIONAL FLAGS + --description=DESCRIPTION + An optional, textual description for the backend. + + --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. + + At most one of these can be specified: + + --accelerator-topology=ACCELERATOR_TOPOLOGY + Specifies the topology of placement and interconnection performance + required to create a slice of VMs with interconnected accelerators. + + --max-topology-distance=MAX_TOPOLOGY_DISTANCE + Specifies the topology of placement and interconnection network + performance of the group of VMs (MIG / Multi-MIGs). + MAX_TOPOLOGY_DISTANCE must be one of: + + BLOCK + VMs are placed within the same block of capacity with improved + latency compared to Cluster. + CLUSTER + VMs are placed within the same cluster of capacity with improved + latency between them. + SUBBLOCK + Tightest collocation of VMs that provides minimized network + latency. VMs are placed within the same rack of capacity with + improved latency compared to Block. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/compute/tpus/queued-resources/create b/gcloud/alpha/compute/tpus/queued-resources/create index 2a274e757..4777b16a1 100644 --- a/gcloud/alpha/compute/tpus/queued-resources/create +++ b/gcloud/alpha/compute/tpus/queued-resources/create @@ -223,7 +223,8 @@ OPTIONAL FLAGS --provisioning-model=PROVISIONING_MODEL If provided, the resource will be provisioned with the specified - provisioning model. + provisioning model. Currently only flex-start and reservation-bound are + supported. --range=RANGE CIDR range for the TPU. diff --git a/gcloud/alpha/container/clusters/create b/gcloud/alpha/container/clusters/create index d9581cfad..7b76cf839 100644 --- a/gcloud/alpha/container/clusters/create +++ b/gcloud/alpha/container/clusters/create @@ -22,6 +22,7 @@ SYNOPSIS [--cluster-version=CLUSTER_VERSION] [--containerd-config-from-file=PATH_TO_FILE] [--create-subnetwork=[KEY=VALUE,...]] + [--data-cache-count=DATA_CACHE_COUNT] [--database-encryption-key=DATABASE_ENCRYPTION_KEY] [--default-max-pods-per-node=DEFAULT_MAX_PODS_PER_NODE] [--disable-default-snat] [--disable-l4-lb-firewall-reconciliation] @@ -406,6 +407,10 @@ FLAGS Cannot be specified unless '--enable-ip-alias' option is also specified. Cannot be used in conjunction with '--subnetwork' option. + --data-cache-count=DATA_CACHE_COUNT + Specifies the number of local SSDs to be utilized for GKE Data Cache in + the cluster. + --database-encryption-key=DATABASE_ENCRYPTION_KEY Enable Database Encryption. @@ -1334,6 +1339,11 @@ FLAGS kubeletConfig: cpuManagerPolicy: static + memoryManager: + policy: Static + topologyManager: + policy: BestEffort + scope: pod linuxConfig: sysctl: net.core.somaxconn: '2048' @@ -1350,6 +1360,9 @@ FLAGS cpuCFSQuota true or false (enabled by default) cpuCFSQuotaPeriod interval (e.g., '100ms') + memoryManager specify memory manager policy + topologyManager specify topology manager policy + and scope podPidsLimit integer (The value must be greater than or equal to 1024 and less than 4194304.) @@ -1376,6 +1389,17 @@ FLAGS 'fs.mqueue.*', and 'net.*', and sysctls under the groups.) + KEY VALUE + policy either 'Static' or 'None' + + KEY VALUE + policy either 'none' or + 'best-effort' or + 'single-numa-node' or + 'restricted' + scope either 'pod' or + 'container' + List of supported sysctls in 'linuxConfig'. KEY VALUE @@ -1399,7 +1423,7 @@ FLAGS integer tuple net.ipv4.tcp_wmem Any positive integer tuple - net.ipv4.tcp_tw_reuse Must be {0, 1} + net.ipv4.tcp_tw_reuse Must be {0, 1, 2} net.netfilter.nf_conntrack_max Must be between [65536, 4194304] net.netfilter.nf_conntrack_buckets Must be between diff --git a/gcloud/alpha/container/node-pools/create b/gcloud/alpha/container/node-pools/create index bcffa879d..ae21e6015 100644 --- a/gcloud/alpha/container/node-pools/create +++ b/gcloud/alpha/container/node-pools/create @@ -16,6 +16,7 @@ SYNOPSIS [max-pods-per-node=NUM_PODS],...]] [--async] [--boot-disk-kms-key=BOOT_DISK_KMS_KEY] [--cluster=CLUSTER] [--containerd-config-from-file=PATH_TO_FILE] + [--data-cache-count=DATA_CACHE_COUNT] [--disable-pod-cidr-overprovision] [--disk-size=DISK_SIZE] [--disk-type=DISK_TYPE] [--enable-autoprovisioning] [--enable-autorepair] [--no-enable-autoupgrade] @@ -204,6 +205,10 @@ FLAGS Use a full or relative path to a local file containing the value of containerd_config. + --data-cache-count=DATA_CACHE_COUNT + Specifies the number of local SSDs to be utilized for GKE Data Cache in + the node pool. + --disable-pod-cidr-overprovision Disables pod cidr overprovision on nodes. Pod cidr overprovisioning is enabled by default. @@ -708,6 +713,11 @@ FLAGS kubeletConfig: cpuManagerPolicy: static + memoryManager: + policy: Static + topologyManager: + policy: BestEffort + scope: pod linuxConfig: sysctl: net.core.somaxconn: '2048' @@ -724,6 +734,9 @@ FLAGS cpuCFSQuota true or false (enabled by default) cpuCFSQuotaPeriod interval (e.g., '100ms') + memoryManager specify memory manager policy + topologyManager specify topology manager policy + and scope podPidsLimit integer (The value must be greater than or equal to 1024 and less than 4194304.) @@ -750,6 +763,17 @@ FLAGS 'fs.mqueue.*', and 'net.*', and sysctls under the groups.) + KEY VALUE + policy either 'Static' or 'None' + + KEY VALUE + policy either 'none' or + 'best-effort' or + 'single-numa-node' or + 'restricted' + scope either 'pod' or + 'container' + List of supported sysctls in 'linuxConfig'. KEY VALUE @@ -773,7 +797,7 @@ FLAGS integer tuple net.ipv4.tcp_wmem Any positive integer tuple - net.ipv4.tcp_tw_reuse Must be {0, 1} + net.ipv4.tcp_tw_reuse Must be {0, 1, 2} net.netfilter.nf_conntrack_max Must be between [65536, 4194304] net.netfilter.nf_conntrack_buckets Must be between diff --git a/gcloud/alpha/container/node-pools/update b/gcloud/alpha/container/node-pools/update index ccbbf36da..d65150634 100644 --- a/gcloud/alpha/container/node-pools/update +++ b/gcloud/alpha/container/node-pools/update @@ -275,6 +275,11 @@ REQUIRED FLAGS kubeletConfig: cpuManagerPolicy: static + memoryManager: + policy: Static + topologyManager: + policy: BestEffort + scope: pod linuxConfig: sysctl: net.core.somaxconn: '2048' @@ -291,6 +296,9 @@ REQUIRED FLAGS cpuCFSQuota true or false (enabled by default) cpuCFSQuotaPeriod interval (e.g., '100ms') + memoryManager specify memory manager policy + topologyManager specify topology manager policy + and scope podPidsLimit integer (The value must be greater than or equal to 1024 and less than 4194304.) @@ -320,6 +328,18 @@ REQUIRED FLAGS 'fs.mqueue.*', and 'net.*', and sysctls under the groups.) + KEY VALUE + policy either 'Static' or + 'None' + + KEY VALUE + policy either 'none' or + 'best-effort' or + 'single-numa-node' or + 'restricted' + scope either 'pod' or + 'container' + List of supported sysctls in 'linuxConfig'. KEY VALUE @@ -348,7 +368,8 @@ REQUIRED FLAGS integer tuple net.ipv4.tcp_wmem Any positive integer tuple - net.ipv4.tcp_tw_reuse Must be {0, 1} + net.ipv4.tcp_tw_reuse Must be {0, 1, + 2} net.netfilter.nf_conntrack_max Must be between [65536, 4194304] net.netfilter.nf_conntrack_buckets Must be between diff --git a/gcloud/alpha/dataproc/clusters/create b/gcloud/alpha/dataproc/clusters/create index 32b8dd77b..2399f7546 100644 --- a/gcloud/alpha/dataproc/clusters/create +++ b/gcloud/alpha/dataproc/clusters/create @@ -4,6 +4,7 @@ NAME SYNOPSIS gcloud alpha dataproc clusters create (CLUSTER : --region=REGION) [--async] [--autoscaling-policy=AUTOSCALING_POLICY] [--bucket=BUCKET] + [--cluster-type=TYPE] [--driver-pool-accelerator=[type=TYPE,[count=COUNT],...]] [--driver-pool-boot-disk-size=DRIVER_POOL_BOOT_DISK_SIZE] [--driver-pool-boot-disk-type=DRIVER_POOL_BOOT_DISK_TYPE] @@ -22,7 +23,7 @@ SYNOPSIS [--master-boot-disk-type=MASTER_BOOT_DISK_TYPE] [--master-local-ssd-interface=MASTER_LOCAL_SSD_INTERFACE] [--master-machine-type=MASTER_MACHINE_TYPE] - [--master-min-cpu-platform=PLATFORM] [--max-idle=MAX_IDLE] + [--master-min-cpu-platform=PLATFORM] [--min-secondary-worker-fraction=MIN_SECONDARY_WORKER_FRACTION] [--node-group=NODE_GROUP] [--num-driver-pool-local-ssds=NUM_DRIVER_POOL_LOCAL_SSDS] @@ -42,7 +43,8 @@ SYNOPSIS [--secondary-worker-standard-capacity-base=SECONDARY_WORKER_STANDARD_CAPACITY_BASE] [--secondary-worker-standard-capacity-percent-above-base=SECONDARY_WORKER_STANDARD_CAPACITY_PERCENT_ABOVE_BASE] [--shielded-integrity-monitoring] [--shielded-secure-boot] - [--shielded-vtpm] [--temp-bucket=TEMP_BUCKET] + [--shielded-vtpm] [--stop-max-idle=STOP_MAX_IDLE] + [--temp-bucket=TEMP_BUCKET] [--worker-accelerator=[type=TYPE,[count=COUNT],...]] [--worker-boot-disk-provisioned-iops=WORKER_BOOT_DISK_PROVISIONED_IOPS] [--worker-boot-disk-provisioned-throughput=WORKER_BOOT_DISK_PROVISIONED_THROUGHPUT] @@ -52,7 +54,10 @@ SYNOPSIS [--worker-min-cpu-platform=PLATFORM] [--zone=ZONE, -z ZONE] [--dataproc-metastore=DATAPROC_METASTORE | --bigquery-metastore --bigquery-metastore-database-location=BIGQUERY_METASTORE_DATABASE_LOCATION --bigquery-metastore-project-id=BIGQUERY_METASTORE_PROJECT_ID] - [--expiration-time=EXPIRATION_TIME | --max-age=MAX_AGE] + [--delete-expiration-time=DELETE_EXPIRATION_TIME + | --delete-max-age=DELETE_MAX_AGE | --expiration-time=EXPIRATION_TIME + | --max-age=MAX_AGE] + [--delete-max-idle=DELETE_MAX_IDLE | --max-idle=MAX_IDLE] [--gce-pd-kms-key=GCE_PD_KMS_KEY : --gce-pd-kms-key-keyring=GCE_PD_KMS_KEY_KEYRING --gce-pd-kms-key-location=GCE_PD_KMS_KEY_LOCATION @@ -73,6 +78,8 @@ SYNOPSIS --num-secondary-workers=NUM_SECONDARY_WORKERS --num-workers=NUM_WORKERS --secondary-worker-type=TYPE; default="preemptible"] + [--stop-expiration-time=STOP_EXPIRATION_TIME + | --stop-max-age=STOP_MAX_AGE] [--worker-machine-type=WORKER_MACHINE_TYPE | --worker-machine-types=type=MACHINE_TYPE[, type=MACHINE_TYPE...][,rank=RANK]] [GCLOUD_WIDE_FLAG ...] @@ -138,6 +145,10 @@ FLAGS dependencies, miscellaneous config files, and job driver console output when using this cluster. + --cluster-type=TYPE + The type of cluster. TYPE must be one of: standard, single-node, + zero-scale. + --driver-pool-accelerator=[type=TYPE,[count=COUNT],...] Attaches accelerators, such as GPUs, to the driver-pool instance(s). @@ -265,11 +276,6 @@ FLAGS which contains the list of available CPU platforms in the zone (see Availability of CPU platforms for more information). - --max-idle=MAX_IDLE - The duration before cluster is auto-deleted after last job completes, - such as "2h" or "1d". See $ gcloud topic datetimes for information on - duration formats. - --min-secondary-worker-fraction=MIN_SECONDARY_WORKER_FRACTION Minimum fraction of secondary worker nodes required to create the cluster. If it is not met, cluster creation will fail. Must be a @@ -415,6 +421,11 @@ FLAGS security operations, such as remote attestation, encryption, and sealing of keys. + --stop-max-idle=STOP_MAX_IDLE + The duration after the last job completes to auto-stop the cluster, + such as "2h" or "1d". See $ gcloud topic datetimes for information on + duration formats. + --temp-bucket=TEMP_BUCKET The Google Cloud Storage bucket to use by default to store ephemeral cluster and jobs data, such as Spark and MapReduce history files. @@ -501,15 +512,37 @@ FLAGS At most one of these can be specified: + --delete-expiration-time=DELETE_EXPIRATION_TIME + The time when the cluster will be auto-deleted, such as + "2017-08-29T18:52:51.142Z." See $ gcloud topic datetimes for + information on time formats. + + --delete-max-age=DELETE_MAX_AGE + The lifespan of the cluster, with auto-deletion upon completion, such + as "2h" or "1d". See $ gcloud topic datetimes for information on + duration formats. + --expiration-time=EXPIRATION_TIME - The time when cluster will be auto-deleted, such as + The time when the cluster will be auto-deleted, such as "2017-08-29T18:52:51.142Z." See $ gcloud topic datetimes for information on time formats. --max-age=MAX_AGE - The lifespan of the cluster before it is auto-deleted, such as "2h" - or "1d". See $ gcloud topic datetimes for information on duration - formats. + The lifespan of the cluster, with auto-deletion upon completion, such + as "2h" or "1d". See $ gcloud topic datetimes for information on + duration formats. + + At most one of these can be specified: + + --delete-max-idle=DELETE_MAX_IDLE + The duration after the last job completes to auto-delete the cluster, + such as "2h" or "1d". See $ gcloud topic datetimes for information on + duration formats. + + --max-idle=MAX_IDLE + The duration after the last job completes to autto-delete the + cluster, such as "2h" or "1d". See $ gcloud topic datetimes for + information on duration formats. Key resource - The Cloud KMS (Key Management Service) cryptokey that will be used to protect the cluster. The 'Compute Engine Service Agent' service @@ -917,6 +950,18 @@ FLAGS The type of the secondary worker group. TYPE must be one of: preemptible, non-preemptible, spot. + At most one of these can be specified: + + --stop-expiration-time=STOP_EXPIRATION_TIME + The time when the cluster will be auto-stopped, such as + "2017-08-29T18:52:51.142Z." See $ gcloud topic datetimes for + information on time formats. + + --stop-max-age=STOP_MAX_AGE + The lifespan of the cluster, with auto-stop upon completion, such as + "2h" or "1d". See $ gcloud topic datetimes for information on + duration formats. + At most one of these can be specified: --worker-machine-type=WORKER_MACHINE_TYPE diff --git a/gcloud/alpha/dataproc/clusters/update b/gcloud/alpha/dataproc/clusters/update index d1077be02..7f4d56dc6 100644 --- a/gcloud/alpha/dataproc/clusters/update +++ b/gcloud/alpha/dataproc/clusters/update @@ -12,8 +12,16 @@ SYNOPSIS [--update-labels=[KEY=VALUE,...]] [--autoscaling-policy=AUTOSCALING_POLICY | --disable-autoscaling] [--clear-labels | --remove-labels=[KEY,...]] - [--expiration-time=EXPIRATION_TIME | --max-age=MAX_AGE | --no-max-age] - [--max-idle=MAX_IDLE | --no-max-idle] [GCLOUD_WIDE_FLAG ...] + [--delete-expiration-time=DELETE_EXPIRATION_TIME + | --delete-max-age=DELETE_MAX_AGE | --no-delete-max-age + | --expiration-time=EXPIRATION_TIME | --max-age=MAX_AGE + | --no-max-age] + [--delete-max-idle=DELETE_MAX_IDLE | --no-delete-max-idle + | --max-idle=MAX_IDLE | --no-max-idle] + [--stop-expiration-time=STOP_EXPIRATION_TIME + | --stop-max-age=STOP_MAX_AGE | --no-stop-max-age] + [--stop-max-idle=STOP_MAX_IDLE | --no-stop-max-idle] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Update the number of worker nodes and/or the labels in a cluster. @@ -169,13 +177,27 @@ FLAGS At most one of these can be specified: + --delete-expiration-time=DELETE_EXPIRATION_TIME + The time when the cluster will be auto-deleted, such as + "2017-08-29T18:52:51.142Z". See $ gcloud topic datetimes for + information on time formats. + + --delete-max-age=DELETE_MAX_AGE + The lifespan of the cluster with auto-deletion upon completion, such + as "2h" or "1d". See $ gcloud topic datetimes for information on + duration formats. + + --no-delete-max-age + Cancels the cluster auto-deletion by maximum cluster age (configured + by --delete-max-age or --delete-expiration-time flags) + --expiration-time=EXPIRATION_TIME - The time when cluster will be auto-deleted, such as + The time when the cluster will be auto-deleted, such as "2017-08-29T18:52:51.142Z". See $ gcloud topic datetimes for information on time formats. --max-age=MAX_AGE - The lifespan of the cluster before it is auto-deleted, such as "2h" + The lifespan of the cluster, with auto-deletion upon completion, "2h" or "1d". See $ gcloud topic datetimes for information on duration formats. @@ -185,8 +207,17 @@ FLAGS At most one of these can be specified: + --delete-max-idle=DELETE_MAX_IDLE + The duration after the last job completes to auto-delete the cluster, + such as "2h" or "1d". See $ gcloud topic datetimes for information on + duration formats. + + --no-delete-max-idle + Cancels the cluster auto-deletion by cluster idle duration + (configured by --delete-max-idle flag) + --max-idle=MAX_IDLE - The duration before cluster is auto-deleted after last job finished, + The duration after the last job completes to auto-delete the cluster, such as "2h" or "1d". See $ gcloud topic datetimes for information on duration formats. @@ -194,6 +225,33 @@ FLAGS Cancels the cluster auto-deletion by cluster idle duration (configured by --max-idle flag) + At most one of these can be specified: + + --stop-expiration-time=STOP_EXPIRATION_TIME + The time when the cluster will be auto-stopped, such as + "2017-08-29T18:52:51.142Z". See $ gcloud topic datetimes for + information on time formats. + + --stop-max-age=STOP_MAX_AGE + The lifespan of the cluster, with auto-stop upon completion, such as + "2h" or "1d". See $ gcloud topic datetimes for information on + duration formats. + + --no-stop-max-age + Cancels the cluster auto-stop by maximum cluster age (configured by + --stop-max-age or --stop-expiration-time flags) + + At most one of these can be specified: + + --stop-max-idle=STOP_MAX_IDLE + The duration after the last job completes to auto-stop the cluster, + such as "2h" or "1d". See $ gcloud topic datetimes for information on + duration formats. + + --no-stop-max-idle + Cancels the cluster auto-stop by cluster idle duration (configured by + --stop-max-idle flag) + 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/dataproc/workflow-templates/set-managed-cluster b/gcloud/alpha/dataproc/workflow-templates/set-managed-cluster index 603038e78..a41e79861 100644 --- a/gcloud/alpha/dataproc/workflow-templates/set-managed-cluster +++ b/gcloud/alpha/dataproc/workflow-templates/set-managed-cluster @@ -5,7 +5,7 @@ NAME SYNOPSIS gcloud alpha dataproc workflow-templates set-managed-cluster (TEMPLATE : --region=REGION) [--autoscaling-policy=AUTOSCALING_POLICY] - [--bucket=BUCKET] [--cluster-name=CLUSTER_NAME] + [--bucket=BUCKET] [--cluster-name=CLUSTER_NAME] [--cluster-type=TYPE] [--enable-component-gateway] [--initialization-action-timeout=TIMEOUT; default="10m"] [--initialization-actions=CLOUD_STORAGE_URI,[...]] @@ -128,6 +128,10 @@ FLAGS The name of the managed dataproc cluster. If unspecified, the workflow template ID will be used. + --cluster-type=TYPE + The type of cluster. TYPE must be one of: standard, single-node, + zero-scale. + --enable-component-gateway Enable access to the web UIs of selected components on the cluster through the component gateway. diff --git a/gcloud/alpha/iam/roles/undelete b/gcloud/alpha/iam/roles/undelete index df5c9ed4e..c21fc14af 100644 --- a/gcloud/alpha/iam/roles/undelete +++ b/gcloud/alpha/iam/roles/undelete @@ -18,13 +18,12 @@ DESCRIPTION EXAMPLES To undelete the role ProjectUpdater of the organization 1234567, run: - $ gcloud alpha iam roles undelete roles/ProjectUpdater \ + $ gcloud alpha iam roles undelete ProjectUpdater \ --organization=1234567 To undelete the role ProjectUpdater of the project myproject, run: - $ gcloud alpha iam roles undelete roles/ProjectUpdater \ - --project=myproject + $ gcloud alpha iam roles undelete ProjectUpdater --project=myproject POSITIONAL ARGUMENTS ROLE_ID diff --git a/gcloud/alpha/iam/roles/update b/gcloud/alpha/iam/roles/update index fb06c3c47..955b647d1 100644 --- a/gcloud/alpha/iam/roles/update +++ b/gcloud/alpha/iam/roles/update @@ -15,13 +15,13 @@ DESCRIPTION EXAMPLES To update the role ProjectUpdater from a YAML file, run: - $ gcloud alpha iam roles update roles/ProjectUpdater \ - --organization=123 --file=role_file_path + $ gcloud alpha iam roles update ProjectUpdater --organization=123 \ + --file=role_file_path To update the role ProjectUpdater with flags, run: - $ gcloud alpha iam roles update roles/ProjectUpdater \ - --project=myproject --permissions=permission1,permission2 + $ gcloud alpha iam roles update ProjectUpdater --project=myproject \ + --permissions=permission1,permission2 POSITIONAL ARGUMENTS ROLE_ID diff --git a/gcloud/alpha/managed-kafka/connect-clusters/create b/gcloud/alpha/managed-kafka/connect-clusters/create new file mode 100644 index 000000000..05d75ed27 --- /dev/null +++ b/gcloud/alpha/managed-kafka/connect-clusters/create @@ -0,0 +1,148 @@ +NAME + gcloud alpha managed-kafka connect-clusters create - create a Managed + Service for Apache Kafka connect cluster + +SYNOPSIS + gcloud alpha managed-kafka connect-clusters create + (CONNECT_CLUSTER : --location=LOCATION) --cpu=CPU + --kafka-cluster=KAFKA_CLUSTER --memory=MEMORY + --primary-subnet=PRIMARY_SUBNET [--additional-subnet=ADDITIONAL_SUBNET] + [--async] [--dns-name=DNS_NAME] [--labels=[KEY=VALUE,...]] + [--secret=SECRET] + [--config-file=JSON|YAML|FILE | --configs=[KEY=VALUE,...]] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Create a Managed Service for Apache Kafka connect cluster. + +EXAMPLES + To create a connector cluster, run the following: + + $ gcloud alpha managed-kafka connect-clusters create \ + myconnectorCluster --location=us-central1 --cpu=3 \ + --memory=3GiB \ + --primary-subnet=projects/PROJECT_ID/regions/us-central1/\ + subnetworks/default --kafka-cluster=my-kafka-cluster OR \ + --kafka-cluster=projects/PROJECT_ID/locations/us-central1/\ + clusters/my-kafka-cluster + +POSITIONAL ARGUMENTS + Connect cluster resource - Identifies the connect_cluster that is created. + 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 connect_cluster 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. + + CONNECT_CLUSTER + ID of the connect_cluster or fully qualified identifier for the + connect_cluster. + + To set the connect_cluster attribute: + ▸ provide the argument connect_cluster on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + ID of the location of the Managed Service for Apache Kafka resource. + See + https://cloud.google.com/managed-service-for-apache-kafka/docs/locations + for a list of supported locations. + + To set the location attribute: + ▸ provide the argument connect_cluster on the command line with a + fully specified name; + ▸ provide the argument --location on the command line. + +REQUIRED FLAGS + --cpu=CPU + The number of vCPUs to provision for the cluster. The minimum is 3. + + --kafka-cluster=KAFKA_CLUSTER + The resource path of the Kafka cluster to connect to, or the name of + the Kafka cluster to connect to if the cluster is in the same project + as the Connect cluster. + + --memory=MEMORY + The memory to provision for the cluster in bytes. The value must be + between 1 GiB and 8 GiB per vCPU. Ex. 1024Mi, 4Gi. + + --primary-subnet=PRIMARY_SUBNET + VPC subnet to make available to the Kafka Connect cluster. Structured + like: projects/{project}/regions/{region}/subnetworks/{subnet_id}. The + primary subnet is used to create a Private Service Connect (PSC) + interface for the Kafka Connect workers. It must be located in the same + region as the Connect cluster. + +OPTIONAL FLAGS + --additional-subnet=ADDITIONAL_SUBNET + Additional subnet to make available to the Kafka Connect cluster. + Structured like: + projects/{project}/regions/{region}/subnetworks/{subnet_id}. + + --async + Return immediately, without waiting for the operation in progress to + complete. + + --dns-name=DNS_NAME + DNS domain name from the subnet's network to be made visible to the + Connect Cluster. + + --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. + + --secret=SECRET + Secrets to load into workers. Exact SecretVersions from Secret Manager + must be provided -- aliases are not supported. Up to 32 secrets may be + loaded into one cluster. Format: + projects//secrets//versions/ + + At most one of these can be specified: + + --config-file=JSON|YAML|FILE + The path to the JSON or YAML file containing the configuration that + are overridden from the cluster or connector defaults. This also + supports inline JSON or YAML. Sets config_file value. + + Input Example: + + --config-file=string + + File Example: + + --config-file=path_to_file.(yaml|json) + + --configs=[KEY=VALUE,...] + Configuration for the connect cluster that are overridden from the + cluster defaults. The key of the map is a Kafka topic property name, + for example: cleanup.policy=compact,compression.type=producer. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the managedkafka/v1 API. The full documentation for this + API can be found at: + https://cloud.google.com/managed-service-for-apache-kafka/docs + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/managed-kafka/connect-clusters/delete b/gcloud/alpha/managed-kafka/connect-clusters/delete new file mode 100644 index 000000000..1ef39240e --- /dev/null +++ b/gcloud/alpha/managed-kafka/connect-clusters/delete @@ -0,0 +1,78 @@ +NAME + gcloud alpha managed-kafka connect-clusters delete - delete a Managed + Service for Apache Kafka connect cluster + +SYNOPSIS + gcloud alpha managed-kafka connect-clusters delete + (CONNECT_CLUSTER : --location=LOCATION) [--async] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Delete a Managed Service for Apache Kafka connect cluster. + +EXAMPLES + To delete a connect cluster named myconnectcluster located in us-central1, + run the following: + + $ gcloud alpha managed-kafka connect-clusters delete \ + myconnectcluster --location=us-central1 + +POSITIONAL ARGUMENTS + Connect cluster resource - Identifies the cluster for deletion. 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 connect_cluster 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. + + CONNECT_CLUSTER + ID of the connect_cluster or fully qualified identifier for the + connect_cluster. + + To set the connect_cluster attribute: + ▸ provide the argument connect_cluster on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + ID of the location of the Managed Service for Apache Kafka resource. + See + https://cloud.google.com/managed-service-for-apache-kafka/docs/locations + for a list of supported locations. + + To set the location attribute: + ▸ provide the argument connect_cluster 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. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the managedkafka/v1 API. The full documentation for this + API can be found at: + https://cloud.google.com/managed-service-for-apache-kafka/docs + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/managed-kafka/connect-clusters/describe b/gcloud/alpha/managed-kafka/connect-clusters/describe new file mode 100644 index 000000000..c565eb4e5 --- /dev/null +++ b/gcloud/alpha/managed-kafka/connect-clusters/describe @@ -0,0 +1,73 @@ +NAME + gcloud alpha managed-kafka connect-clusters describe - describe a Managed + Service for Apache Kafka connect cluster + +SYNOPSIS + gcloud alpha managed-kafka connect-clusters describe + (CONNECT_CLUSTER : --location=LOCATION) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Describe a Managed Service for Apache Kafka for BigQuery connect + cluster. + +EXAMPLES + To describe a connect cluster named myconnectcluster located in + us-central1, run the following: + + $ gcloud alpha managed-kafka connect-clusters describe \ + myconnectcluster --location=us-central1 + +POSITIONAL ARGUMENTS + Connect cluster resource - Identifies the connect cluster. 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 connect_cluster 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. + + CONNECT_CLUSTER + ID of the connect_cluster or fully qualified identifier for the + connect_cluster. + + To set the connect_cluster attribute: + ▸ provide the argument connect_cluster on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + ID of the location of the Managed Service for Apache Kafka resource. + See + https://cloud.google.com/managed-service-for-apache-kafka/docs/locations + for a list of supported locations. + + To set the location attribute: + ▸ provide the argument connect_cluster on the command line with a + fully specified name; + ▸ provide the argument --location on the command line. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the managedkafka/v1 API. The full documentation for this + API can be found at: + https://cloud.google.com/managed-service-for-apache-kafka/docs + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/managed-kafka/connect-clusters/help b/gcloud/alpha/managed-kafka/connect-clusters/help new file mode 100644 index 000000000..0da29e37a --- /dev/null +++ b/gcloud/alpha/managed-kafka/connect-clusters/help @@ -0,0 +1,41 @@ +NAME + gcloud alpha managed-kafka connect-clusters - administer Managed Service + for Apache Kafka connect-clusters + +SYNOPSIS + gcloud alpha managed-kafka connect-clusters COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Administer Managed Service for Apache Kafka connect-clusters. + +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 Managed Service for Apache Kafka connect cluster. + + delete + (ALPHA) Delete a Managed Service for Apache Kafka connect cluster. + + describe + (ALPHA) Describe a Managed Service for Apache Kafka connect cluster. + + list + (ALPHA) List all Managed Service for Apache Kafka connect clusters in a + given location. + + update + (ALPHA) Update a Managed Service for Apache Kafka for BigQuery connect + cluster. + +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/managed-kafka/connect-clusters/list b/gcloud/alpha/managed-kafka/connect-clusters/list new file mode 100644 index 000000000..3daacabd6 --- /dev/null +++ b/gcloud/alpha/managed-kafka/connect-clusters/list @@ -0,0 +1,86 @@ +NAME + gcloud alpha managed-kafka connect-clusters list - list all Managed Service + for Apache Kafka connect clusters in a given location + +SYNOPSIS + gcloud alpha managed-kafka connect-clusters list --location=LOCATION + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) List all Managed Service for Apache Kafka connect clusters in a + given location. To specify the maximum number of clusters to list, use the + --limit flag. + +EXAMPLES + To list all connect clusters in a given location, such as us-central1, run + the following: + + $ gcloud alpha managed-kafka connect-clusters list \ + --location=us-central1 + +REQUIRED FLAGS + Location resource - Identifies the region which contains all the connector + clusters to be listed. This represents a Cloud resource. (NOTE) Some + attributes are not given arguments in this group but can be set in other + ways. + + To set the project attribute: + ◆ provide the argument --location on the command line with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + --location=LOCATION + ID of the location or fully qualified identifier for the location. + + To set the location attribute: + ▸ provide the argument --location on the command line. + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the managedkafka/v1 API. The full documentation for this + API can be found at: + https://cloud.google.com/managed-service-for-apache-kafka/docs + +NOTES + This command is currently in 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/managed-kafka/connect-clusters/update b/gcloud/alpha/managed-kafka/connect-clusters/update new file mode 100644 index 000000000..6e5559b72 --- /dev/null +++ b/gcloud/alpha/managed-kafka/connect-clusters/update @@ -0,0 +1,175 @@ +NAME + gcloud alpha managed-kafka connect-clusters update - update a Managed + Service for Apache Kafka for BigQuery connect cluster + +SYNOPSIS + gcloud alpha managed-kafka connect-clusters update + (CONNECT_CLUSTER : --location=LOCATION) + (--cpu=CPU --memory=MEMORY --clear-configs + | --config-file=JSON|YAML|FILE + | --configs=[KEY=VALUE,...] --clear-dns-names + | --dns-name=DNS_NAME --clear-labels + | --labels=[KEY=VALUE,...] --clear-secrets + | --secret=SECRET [--primary-subnet=PRIMARY_SUBNET + : --additional-subnet=ADDITIONAL_SUBNET]) [--async] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Update an Managed Service for Apache Kafka for BigQuery connect + cluster. + +EXAMPLES + To update a connect cluster, run the following: + + $ gcloud alpha managed-kafka connect-clusters update \ + myconnectorCluster --location=us-central1 \ + --configs=KEY1=VALUE1,KEY2=VALUE2... OR \ + --config-file=my-config-file.yaml --cpu=3 --memory=3GiB \ + --primary-subnet=projects/my-project/regions/us-central1/\ + subnetworks/default/1 \ + --additional-subnet=projects/my-project/regions/us-central1/\ + subnetworks/default/2 \ + --dns-name=bootstrap.myconnectorCluster.us-central1.managedkafka\ + .my-project.cloud.goog:9092 \ + --secret=projects/my-project/secrets/my-secret/versions/1 \ + --labels=KEY1=VALUE1,KEY2=VALUE2... + +POSITIONAL ARGUMENTS + Connect cluster resource - Identifies the connector cluster for which the + command runs. 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 connect_cluster 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. + + CONNECT_CLUSTER + ID of the connect_cluster or fully qualified identifier for the + connect_cluster. + + To set the connect_cluster attribute: + ▸ provide the argument connect_cluster on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + ID of the location of the Managed Service for Apache Kafka resource. + See + https://cloud.google.com/managed-service-for-apache-kafka/docs/locations + for a list of supported locations. + + To set the location attribute: + ▸ provide the argument connect_cluster on the command line with a + fully specified name; + ▸ provide the argument --location on the command line. + +REQUIRED FLAGS + At least one of these must be specified: + + --cpu=CPU + The number of vCPUs to provision for the cluster. The minimum is 3. + + --memory=MEMORY + The memory to provision for the cluster in bytes. The value must be + between 1 GiB and 8 GiB per vCPU. Ex. 1024Mi, 4Gi. + + At most one of these can be specified: + + --clear-configs + Remove all the configurations for the topic. + + --config-file=JSON|YAML|FILE + The path to the JSON or YAML file containing the configuration that + are overridden from the cluster or connector defaults. This also + supports inline JSON or YAML. Sets config_file value. + + Input Example: + + --config-file=string + + File Example: + + --config-file=path_to_file.(yaml|json) + + --configs=[KEY=VALUE,...] + Configuration for the connect cluster that are overridden from the + cluster defaults. The key of the map is a Kafka topic property + name, for example: + cleanup.policy=compact,compression.type=producer. + + At most one of these can be specified: + + --clear-dns-names + Remove all the DNS domain names for the connect cluster. + + --dns-name=DNS_NAME + DNS domain name from the subnet's network to be made visible to the + Connect Cluster. + + At most one of these can be specified: + + --clear-labels + Remove all the labels from the connect cluster. + + --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. + + At most one of these can be specified: + + --clear-secrets + Remove all the secrets from the connect cluster. + + --secret=SECRET + Secrets to load into workers. Exact SecretVersions from Secret + Manager must be provided -- aliases are not supported. Up to 32 + secrets may be loaded into one cluster. Format: + projects//secrets//versions/ + + --primary-subnet=PRIMARY_SUBNET + VPC subnet to make available to the Kafka Connect cluster. Structured + like: projects/{project}/regions/{region}/subnetworks/{subnet_id}. + The primary subnet is used to create a Private Service Connect (PSC) + interface for the Kafka Connect workers. It must be located in the + same region as the Connect cluster. + + This flag argument must be specified if any of the other arguments in + this group are specified. + + --additional-subnet=ADDITIONAL_SUBNET + Additional subnet to make available to the Kafka Connect cluster. + Structured like: + projects/{project}/regions/{region}/subnetworks/{subnet_id}. + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the managedkafka/v1 API. The full documentation for this + API can be found at: + https://cloud.google.com/managed-service-for-apache-kafka/docs + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/managed-kafka/connectors/create b/gcloud/alpha/managed-kafka/connectors/create new file mode 100644 index 000000000..1da2a73eb --- /dev/null +++ b/gcloud/alpha/managed-kafka/connectors/create @@ -0,0 +1,106 @@ +NAME + gcloud alpha managed-kafka connectors create - create a Managed Service for + Apache Kafka connector + +SYNOPSIS + gcloud alpha managed-kafka connectors create + (CONNECTOR : --connect_cluster=CONNECT_CLUSTER --location=LOCATION) + (--config-file=JSON|YAML|FILE | --configs=[KEY=VALUE,...]) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Create a Managed Service for Apache Kafka connector. + +EXAMPLES + To create a connector, run the following: + + $ gcloud alpha managed-kafka connectors create myconnector \ + --location=us-central1 --connect_cluster=mycluster \ + --configs=connector.class="com.google.pubsub.kafka.source.CloudP\ + ubSubSourceConnector",cps.subscription="my-subscription",... OR + $ gcloud alpha managed-kafka connectors create myconnector \ + --location=us-central1 --connect_cluster=mycluster \ + --config-file=my-config-file.yaml + +POSITIONAL ARGUMENTS + Connector resource - Identifies the connector for which the command runs. + 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 connector 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. + + CONNECTOR + ID of the connector or fully qualified identifier for the connector. + + To set the connector attribute: + ▸ provide the argument connector on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --connect_cluster=CONNECT_CLUSTER + The connect cluster name. + + To set the connect_cluster attribute: + ▸ provide the argument connector on the command line with a fully + specified name; + ▸ provide the argument --connect_cluster on the command line. + + --location=LOCATION + ID of the location of the Managed Service for Apache Kafka resource. + See + https://cloud.google.com/managed-service-for-apache-kafka/docs/locations + for a list of supported locations. + + To set the location attribute: + ▸ provide the argument connector on the command line with a fully + specified name; + ▸ provide the argument --location on the command line. + +REQUIRED FLAGS + Exactly one of these must be specified: + + --config-file=JSON|YAML|FILE + The path to the JSON or YAML file containing the configuration that + are overridden from the connector defaults. This also supports inline + JSON or YAML. Sets config_file value. + + Input Example: + + --config-file=string + + File Example: + + --config-file=path_to_file.(yaml|json) + + --configs=[KEY=VALUE,...] + Configuration for the connector that are overridden from the + connector defaults. The key of the map is a Kafka topic property + name, for example: cleanup.policy=compact,compression.type=producer. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the managedkafka/v1 API. The full documentation for this + API can be found at: + https://cloud.google.com/managed-service-for-apache-kafka/docs + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/managed-kafka/connectors/delete b/gcloud/alpha/managed-kafka/connectors/delete new file mode 100644 index 000000000..a8663d241 --- /dev/null +++ b/gcloud/alpha/managed-kafka/connectors/delete @@ -0,0 +1,80 @@ +NAME + gcloud alpha managed-kafka connectors delete - delete a Managed Service for + Apache Kafka connector + +SYNOPSIS + gcloud alpha managed-kafka connectors delete + (CONNECTOR : --connect_cluster=CONNECT_CLUSTER --location=LOCATION) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Delete a Managed Service for Apache Kafka connector. + +EXAMPLES + To delete a connector named myconnector located in us-central1, run the + following: + + $ gcloud alpha managed-kafka connectors delete myconnector \ + --location=us-central1 --connect_cluster=mycluster + +POSITIONAL ARGUMENTS + Connector resource - Identifies the cluster for deletion. 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 connector 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. + + CONNECTOR + ID of the connector or fully qualified identifier for the connector. + + To set the connector attribute: + ▸ provide the argument connector on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --connect_cluster=CONNECT_CLUSTER + The connect cluster name. + + To set the connect_cluster attribute: + ▸ provide the argument connector on the command line with a fully + specified name; + ▸ provide the argument --connect_cluster on the command line. + + --location=LOCATION + ID of the location of the Managed Service for Apache Kafka resource. + See + https://cloud.google.com/managed-service-for-apache-kafka/docs/locations + for a list of supported locations. + + To set the location attribute: + ▸ provide the argument connector on the command line with a fully + specified name; + ▸ provide the argument --location on the command line. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the managedkafka/v1 API. The full documentation for this + API can be found at: + https://cloud.google.com/managed-service-for-apache-kafka/docs + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/managed-kafka/connectors/describe b/gcloud/alpha/managed-kafka/connectors/describe new file mode 100644 index 000000000..f814603f1 --- /dev/null +++ b/gcloud/alpha/managed-kafka/connectors/describe @@ -0,0 +1,80 @@ +NAME + gcloud alpha managed-kafka connectors describe - describe a Managed Service + for Apache Kafka connector + +SYNOPSIS + gcloud alpha managed-kafka connectors describe + (CONNECTOR : --connect_cluster=CONNECT_CLUSTER --location=LOCATION) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Describe a Managed Service for Apache Kafka connector. + +EXAMPLES + To describe a connector named myconnector located in us-central1, run the + following: + + $ gcloud alpha managed-kafka connectors describe myconnector \ + --location=us-central1 --connect_cluster=mycluster + +POSITIONAL ARGUMENTS + Connector resource - Identifies the connector for details to be displayed. + The arguments in this group can be used to specify the attributes of this + resource. (NOTE) Some attributes are not given arguments in this group but + can be set in other ways. + + To set the project attribute: + ◆ provide the argument connector 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. + + CONNECTOR + ID of the connector or fully qualified identifier for the connector. + + To set the connector attribute: + ▸ provide the argument connector on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --connect_cluster=CONNECT_CLUSTER + The connect cluster name. + + To set the connect_cluster attribute: + ▸ provide the argument connector on the command line with a fully + specified name; + ▸ provide the argument --connect_cluster on the command line. + + --location=LOCATION + ID of the location of the Managed Service for Apache Kafka resource. + See + https://cloud.google.com/managed-service-for-apache-kafka/docs/locations + for a list of supported locations. + + To set the location attribute: + ▸ provide the argument connector on the command line with a fully + specified name; + ▸ provide the argument --location on the command line. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the managedkafka/v1 API. The full documentation for this + API can be found at: + https://cloud.google.com/managed-service-for-apache-kafka/docs + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/managed-kafka/connectors/help b/gcloud/alpha/managed-kafka/connectors/help new file mode 100644 index 000000000..dfdcc60d1 --- /dev/null +++ b/gcloud/alpha/managed-kafka/connectors/help @@ -0,0 +1,55 @@ +NAME + gcloud alpha managed-kafka connectors - administer Managed Service for + Apache Kafka connectors + +SYNOPSIS + gcloud alpha managed-kafka connectors COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Administer Managed Service for Apache Kafka connectors. + +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 Managed Service for Apache Kafka connector. + + delete + (ALPHA) Delete a Managed Service for Apache Kafka connector. + + describe + (ALPHA) Describe a Managed Service for Apache Kafka connector. + + list + (ALPHA) List all Managed Service for Apache Kafka connectors in a given + location. + + pause + (ALPHA) Pauses operation of a Managed Service for Apache Kafka + connector. + + restart + (ALPHA) Restarts a Managed Service for Apache Kafka connector. + + resume + (ALPHA) Resumes operation of a stopped Managed Service for Apache Kafka + connector. + + stop + (ALPHA) Stops operation of a Managed Service for Apache Kafka + connector. + + update + (ALPHA) Update a Managed Service for Apache Kafka connector. + +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/managed-kafka/connectors/list b/gcloud/alpha/managed-kafka/connectors/list new file mode 100644 index 000000000..e2fe79dee --- /dev/null +++ b/gcloud/alpha/managed-kafka/connectors/list @@ -0,0 +1,102 @@ +NAME + gcloud alpha managed-kafka connectors list - list all Managed Service for + Apache Kafka connectors in a given location + +SYNOPSIS + gcloud alpha managed-kafka connectors list + (--connect_cluster=CONNECT_CLUSTER : --location=LOCATION) + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) List all Managed Service for Apache Kafka connectors in a given + location. To specify the maximum number of connectors to list, use the + --limit flag. + +EXAMPLES + To list all Managed Service for Apache Kafka connectors in a given + location, such as us-central1, run the following: + + $ gcloud alpha managed-kafka connectors list \ + --location=us-central1 --connect_cluster=mycluster + +REQUIRED FLAGS + Connect cluster resource - Identifies the cluster which contains all the + connectors to be listed. 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 --connect_cluster 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. + + --connect_cluster=CONNECT_CLUSTER + ID of the connect_cluster or fully qualified identifier for the + connect_cluster. + + To set the connect_cluster attribute: + ▸ provide the argument --connect_cluster on the command line. + + This flag argument must be specified if any of the other arguments in + this group are specified. + + --location=LOCATION + ID of the location of the Managed Service for Apache Kafka resource. + See + https://cloud.google.com/managed-service-for-apache-kafka/docs/locations + for a list of supported locations. + + To set the location attribute: + ▸ provide the argument --connect_cluster on the command line with a + fully specified name; + ▸ provide the argument --location on the command line. + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the managedkafka/v1 API. The full documentation for this + API can be found at: + https://cloud.google.com/managed-service-for-apache-kafka/docs + +NOTES + This command is currently in 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/managed-kafka/connectors/pause b/gcloud/alpha/managed-kafka/connectors/pause new file mode 100644 index 000000000..22497fd31 --- /dev/null +++ b/gcloud/alpha/managed-kafka/connectors/pause @@ -0,0 +1,80 @@ +NAME + gcloud alpha managed-kafka connectors pause - pauses operation of a Managed + Service for Apache Kafka connector + +SYNOPSIS + gcloud alpha managed-kafka connectors pause + (CONNECTOR : --connect_cluster=CONNECT_CLUSTER --location=LOCATION) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Pauses operation of a Managed Service for Apache Kafka connector. + +EXAMPLES + To pause a connector named myconnector located in us-central1, run the + following: + + $ gcloud alpha managed-kafka connectors pause myconnector \ + --location=us-central1 --connect_cluster=mycluster + +POSITIONAL ARGUMENTS + Connector resource - Identifies the connector to pause. 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 connector 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. + + CONNECTOR + ID of the connector or fully qualified identifier for the connector. + + To set the connector attribute: + ▸ provide the argument connector on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --connect_cluster=CONNECT_CLUSTER + The connect cluster name. + + To set the connect_cluster attribute: + ▸ provide the argument connector on the command line with a fully + specified name; + ▸ provide the argument --connect_cluster on the command line. + + --location=LOCATION + ID of the location of the Managed Service for Apache Kafka resource. + See + https://cloud.google.com/managed-service-for-apache-kafka/docs/locations + for a list of supported locations. + + To set the location attribute: + ▸ provide the argument connector on the command line with a fully + specified name; + ▸ provide the argument --location on the command line. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the managedkafka/v1 API. The full documentation for this + API can be found at: + https://cloud.google.com/managed-service-for-apache-kafka/docs + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/managed-kafka/connectors/restart b/gcloud/alpha/managed-kafka/connectors/restart new file mode 100644 index 000000000..10dfc9177 --- /dev/null +++ b/gcloud/alpha/managed-kafka/connectors/restart @@ -0,0 +1,80 @@ +NAME + gcloud alpha managed-kafka connectors restart - restarts a Managed Service + for Apache Kafka connector + +SYNOPSIS + gcloud alpha managed-kafka connectors restart + (CONNECTOR : --connect_cluster=CONNECT_CLUSTER --location=LOCATION) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Restarts a Managed Service for Apache Kafka connector. + +EXAMPLES + To restart a connector named myconnector located in us-central1, run the + following: + + $ gcloud alpha managed-kafka connectors restart myconnector \ + --location=us-central1 --connect_cluster=mycluster + +POSITIONAL ARGUMENTS + Connector resource - Identifies the connector to restart. 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 connector 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. + + CONNECTOR + ID of the connector or fully qualified identifier for the connector. + + To set the connector attribute: + ▸ provide the argument connector on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --connect_cluster=CONNECT_CLUSTER + The connect cluster name. + + To set the connect_cluster attribute: + ▸ provide the argument connector on the command line with a fully + specified name; + ▸ provide the argument --connect_cluster on the command line. + + --location=LOCATION + ID of the location of the Managed Service for Apache Kafka resource. + See + https://cloud.google.com/managed-service-for-apache-kafka/docs/locations + for a list of supported locations. + + To set the location attribute: + ▸ provide the argument connector on the command line with a fully + specified name; + ▸ provide the argument --location on the command line. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the managedkafka/v1 API. The full documentation for this + API can be found at: + https://cloud.google.com/managed-service-for-apache-kafka/docs + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/managed-kafka/connectors/resume b/gcloud/alpha/managed-kafka/connectors/resume new file mode 100644 index 000000000..4b96cb854 --- /dev/null +++ b/gcloud/alpha/managed-kafka/connectors/resume @@ -0,0 +1,81 @@ +NAME + gcloud alpha managed-kafka connectors resume - resumes operation of a + stopped Managed Service for Apache Kafka connector + +SYNOPSIS + gcloud alpha managed-kafka connectors resume + (CONNECTOR : --connect_cluster=CONNECT_CLUSTER --location=LOCATION) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Resumes operation of a stopped Managed Service for Apache Kafka + connector. + +EXAMPLES + To resume a connector named myconnector located in us-central1, run the + following: + + $ gcloud alpha managed-kafka connectors resume myconnector \ + --location=us-central1 --connect_cluster=mycluster + +POSITIONAL ARGUMENTS + Connector resource - Identifies the connector to resume. 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 connector 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. + + CONNECTOR + ID of the connector or fully qualified identifier for the connector. + + To set the connector attribute: + ▸ provide the argument connector on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --connect_cluster=CONNECT_CLUSTER + The connect cluster name. + + To set the connect_cluster attribute: + ▸ provide the argument connector on the command line with a fully + specified name; + ▸ provide the argument --connect_cluster on the command line. + + --location=LOCATION + ID of the location of the Managed Service for Apache Kafka resource. + See + https://cloud.google.com/managed-service-for-apache-kafka/docs/locations + for a list of supported locations. + + To set the location attribute: + ▸ provide the argument connector on the command line with a fully + specified name; + ▸ provide the argument --location on the command line. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the managedkafka/v1 API. The full documentation for this + API can be found at: + https://cloud.google.com/managed-service-for-apache-kafka/docs + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/managed-kafka/connectors/stop b/gcloud/alpha/managed-kafka/connectors/stop new file mode 100644 index 000000000..063daab3e --- /dev/null +++ b/gcloud/alpha/managed-kafka/connectors/stop @@ -0,0 +1,80 @@ +NAME + gcloud alpha managed-kafka connectors stop - stops operation of a Managed + Service for Apache Kafka connector + +SYNOPSIS + gcloud alpha managed-kafka connectors stop + (CONNECTOR : --connect_cluster=CONNECT_CLUSTER --location=LOCATION) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Stops operation of a Managed Service for Apache Kafka connector. + +EXAMPLES + To stop a connector named myconnector located in us-central1, run the + following: + + $ gcloud alpha managed-kafka connectors stop myconnector \ + --location=us-central1 --connect_cluster=mycluster + +POSITIONAL ARGUMENTS + Connector resource - Identifies the connector to resume. 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 connector 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. + + CONNECTOR + ID of the connector or fully qualified identifier for the connector. + + To set the connector attribute: + ▸ provide the argument connector on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --connect_cluster=CONNECT_CLUSTER + The connect cluster name. + + To set the connect_cluster attribute: + ▸ provide the argument connector on the command line with a fully + specified name; + ▸ provide the argument --connect_cluster on the command line. + + --location=LOCATION + ID of the location of the Managed Service for Apache Kafka resource. + See + https://cloud.google.com/managed-service-for-apache-kafka/docs/locations + for a list of supported locations. + + To set the location attribute: + ▸ provide the argument connector on the command line with a fully + specified name; + ▸ provide the argument --location on the command line. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the managedkafka/v1 API. The full documentation for this + API can be found at: + https://cloud.google.com/managed-service-for-apache-kafka/docs + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/managed-kafka/connectors/update b/gcloud/alpha/managed-kafka/connectors/update new file mode 100644 index 000000000..ad45fbbe2 --- /dev/null +++ b/gcloud/alpha/managed-kafka/connectors/update @@ -0,0 +1,105 @@ +NAME + gcloud alpha managed-kafka connectors update - update a Managed Service for + Apache Kafka connector + +SYNOPSIS + gcloud alpha managed-kafka connectors update + (CONNECTOR : --connect_cluster=CONNECT_CLUSTER --location=LOCATION) + (--config-file=JSON|YAML|FILE | --configs=[KEY=VALUE,...]) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Update a Managed Service for Apache Kafka connector. + +EXAMPLES + To update a connector name myconnector, run the following: + + $ gcloud alpha managed-kafka connectors update myconnector \ + --location=us-central1 --configs=KEY1=VALUE1,KEY2=VALUE2... \ + --connect_cluster=mycluster OR + $ gcloud alpha managed-kafka connectors update myconnector \ + --location=us-central1 --config-file=my-config-file.yaml \ + --connect_cluster=mycluster + +POSITIONAL ARGUMENTS + Connector resource - Identifies the connector for which the command runs. + 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 connector 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. + + CONNECTOR + ID of the connector or fully qualified identifier for the connector. + + To set the connector attribute: + ▸ provide the argument connector on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --connect_cluster=CONNECT_CLUSTER + The connect cluster name. + + To set the connect_cluster attribute: + ▸ provide the argument connector on the command line with a fully + specified name; + ▸ provide the argument --connect_cluster on the command line. + + --location=LOCATION + ID of the location of the Managed Service for Apache Kafka resource. + See + https://cloud.google.com/managed-service-for-apache-kafka/docs/locations + for a list of supported locations. + + To set the location attribute: + ▸ provide the argument connector on the command line with a fully + specified name; + ▸ provide the argument --location on the command line. + +REQUIRED FLAGS + Exactly one of these must be specified: + + --config-file=JSON|YAML|FILE + The path to the JSON or YAML file containing the configuration that + are overridden from the connector defaults. This also supports inline + JSON or YAML. Sets config_file value. + + Input Example: + + --config-file=string + + File Example: + + --config-file=path_to_file.(yaml|json) + + --configs=[KEY=VALUE,...] + Configuration for the connector that are overridden from the + connector defaults. The key of the map is a Kafka topic property + name, for example: cleanup.policy=compact,compression.type=producer. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the managedkafka/v1 API. The full documentation for this + API can be found at: + https://cloud.google.com/managed-service-for-apache-kafka/docs + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/managed-kafka/help b/gcloud/alpha/managed-kafka/help index 3c4797369..dc593decc 100644 --- a/gcloud/alpha/managed-kafka/help +++ b/gcloud/alpha/managed-kafka/help @@ -20,6 +20,12 @@ GROUPS clusters (ALPHA) Administer Managed Service for Apache Kafka clusters. + connect-clusters + (ALPHA) Administer Managed Service for Apache Kafka connect-clusters. + + connectors + (ALPHA) Administer Managed Service for Apache Kafka connectors. + consumer-groups (ALPHA) Administer Managed Service for Apache Kafka consumer groups. diff --git a/gcloud/alpha/memorystore/instances/create b/gcloud/alpha/memorystore/instances/create index 2fa2a020e..64f0de240 100644 --- a/gcloud/alpha/memorystore/instances/create +++ b/gcloud/alpha/memorystore/instances/create @@ -2,13 +2,15 @@ NAME gcloud alpha memorystore instances create - create a Memorystore instance SYNOPSIS - gcloud alpha memorystore instances create (INSTANCE : --location=LOCATION) - [--async] [--async-instance-endpoints-deletion-enabled] + gcloud alpha memorystore instances create INSTANCE [--async] + [--async-instance-endpoints-deletion-enabled] [--authorization-mode=AUTHORIZATION_MODE] [--deletion-protection-enabled] [--endpoints=[connections=CONNECTIONS]] [--engine-configs=[ENGINE_CONFIGS,...]] - [--engine-version=ENGINE_VERSION] [--labels=[LABELS,...]] [--mode=MODE] - [--node-type=NODE_TYPE] [--ondemand-maintenance] + [--engine-version=ENGINE_VERSION] [--labels=[LABELS,...]] + [--location=LOCATION] + [--maintenance-policy-weekly-window=[day=DAY],[startTime=STARTTIME]] + [--mode=MODE] [--node-type=NODE_TYPE] [--ondemand-maintenance] [--psc-auto-connections=[network=NETWORK], [port=PORT],[projectId=PROJECTID]] [--replica-count=REPLICA_COUNT] [--request-id=REQUEST_ID] [--shard-count=SHARD_COUNT] @@ -17,6 +19,7 @@ SYNOPSIS --persistence-config-mode=PERSISTENCE_CONFIG_MODE --rdb-config-snapshot-period=RDB_CONFIG_SNAPSHOT_PERIOD --rdb-config-snapshot-start-time=RDB_CONFIG_SNAPSHOT_START_TIME] + [--cross-instance-replication-config-role=CROSS_INSTANCE_REPLICATION_CONFIG_ROLE : --cross-instance-replication-config-secondary-instances=[instance=INSTANCE] --primary-instance=PRIMARY_INSTANCE] [--zone-distribution-config=ZONE_DISTRIBUTION_CONFIG --zone-distribution-config-mode=ZONE_DISTRIBUTION_CONFIG_MODE] [GCLOUD_WIDE_FLAG ...] @@ -49,10 +52,9 @@ EXAMPLES POSITIONAL ARGUMENTS Instance resource - Identifier. Unique name of the instance. Format: - projects/{project}/locations/{location}/instances/{instance} 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}/locations/{location}/instances/{instance} 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 instance on the command line with a fully @@ -60,6 +62,11 @@ POSITIONAL ARGUMENTS ◆ provide the argument --project on the command line; ◆ set the property core/project. + To set the location attribute: + ◆ provide the argument instance on the command line with a fully + specified name; + ◆ provide the argument --location on the command line. + This must be specified. INSTANCE @@ -68,17 +75,6 @@ POSITIONAL ARGUMENTS To set the instance attribute: ▸ provide the argument instance on the command line. - This positional argument must be specified if any of the other - arguments in this group are specified. - - --location=LOCATION - The location id of the instance resource. - - To set the location attribute: - ▸ provide the argument instance on the command line with a fully - specified name; - ▸ provide the argument --location on the command line. - FLAGS --async Return immediately, without waiting for the operation in progress to @@ -188,6 +184,55 @@ FLAGS --labels=path_to_file.(yaml|json) + --location=LOCATION + For resources [instance], provides fallback value for resource location + attribute. When the resource's full URI path is not provided, location + will fallback to this flag value. + + Maintenance policy per instance. + + --maintenance-policy-weekly-window=[day=DAY],[startTime=STARTTIME] + Maintenance window that is applied to resources covered by this + policy. Minimum 1. For the current version, the maximum number of + weekly_window is expected to be one. + + day + Allows to define schedule that runs specified day of the week. + + startTime + Start time of the window in UTC. + + hours + Hours of a day in 24 hour format. Must be greater than or + equal to 0 and typically must be less than or equal to 23. An + API may choose to allow the value "24:00:00" for scenarios + like business closing time. + + minutes + Minutes of an hour. Must be greater than or equal to 0 and + less than or equal to 59. + + nanos + Fractions of seconds, in nanoseconds. Must be greater than or + equal to 0 and less than or equal to 999,999,999. + + seconds + Seconds of a minute. Must be greater than or equal to 0 and + typically must be less than or equal to 59. An API may allow + the value 60 if it allows leap-seconds. + + Shorthand Example: + + --maintenance-policy-weekly-window=day=string,startTime={hours=int,minutes=int,nanos=int,seconds=int} --maintenance-policy-weekly-window=day=string,startTime={hours=int,minutes=int,nanos=int,seconds=int} + + JSON Example: + + --maintenance-policy-weekly-window='[{"day": "string", "startTime": {"hours": int, "minutes": int, "nanos": int, "seconds": int}}]' + + File Example: + + --maintenance-policy-weekly-window=path_to_file.(yaml|json) + --mode=MODE The mode config for the instance. MODE must be one of: @@ -324,6 +369,76 @@ FLAGS future snapshots will be aligned. If not provided, the current time will be used. + Cross instance replication config. + + --cross-instance-replication-config-role=CROSS_INSTANCE_REPLICATION_CONFIG_ROLE + The role of the instance in cross instance replication. + CROSS_INSTANCE_REPLICATION_CONFIG_ROLE must be one of: + + none + This instance does not participate in cross instance replication. + It is an independent instance and does not replicate to or from + any other instances. + primary + A instance that allows both reads and writes. Any data written to + this instance is also replicated to the attached secondary + instances. + secondary + A instance that allows only reads and replicates data from a + primary instance. + + This flag argument must be specified if any of the other arguments in + this group are specified. + + --cross-instance-replication-config-secondary-instances=[instance=INSTANCE] + List of secondary instances that are replicating from this primary + instance. + + This field is only set for a primary instance. + + instance + The full resource path of the remote instance in the format: + projects//locations//instances/. + + Shorthand Example: + + --cross-instance-replication-config-secondary-instances=instance=string --cross-instance-replication-config-secondary-instances=instance=string + + JSON Example: + + --cross-instance-replication-config-secondary-instances='[{"instance": "string"}]' + + File Example: + + --cross-instance-replication-config-secondary-instances=path_to_file.(yaml|json) + + Details of the remote instance associated with this instance in a cross + instance replication setup. + + Instance resource - The full resource path of the remote instance in + the format: + projects//locations//instances/ 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 --primary-instance on the command line with + a fully specified name; + ▫ provide the argument --project on the command line; + ▫ set the property core/project. + + To set the location attribute: + ▫ provide the argument --primary-instance on the command line with + a fully specified name; + ▫ provide the argument --location on the command line. + + --primary-instance=PRIMARY_INSTANCE + ID of the instance or fully qualified identifier for the + instance. + + To set the instance attribute: + ◇ provide the argument --primary-instance on the command line. + Zone distribution configuration for allocation of instance resources. --zone-distribution-config=ZONE_DISTRIBUTION_CONFIG diff --git a/gcloud/alpha/memorystore/instances/help b/gcloud/alpha/memorystore/instances/help index e871d6ebe..bfa0be130 100644 --- a/gcloud/alpha/memorystore/instances/help +++ b/gcloud/alpha/memorystore/instances/help @@ -31,6 +31,9 @@ COMMANDS (ALPHA) List all Memorystore instances in a specified project and location. + reschedule-maintenance + (ALPHA) Reschedule maintenance window for an instance. + update (ALPHA) Update the configuration of a Memorystore instance. diff --git a/gcloud/alpha/memorystore/instances/reschedule-maintenance b/gcloud/alpha/memorystore/instances/reschedule-maintenance new file mode 100644 index 000000000..a14ca7477 --- /dev/null +++ b/gcloud/alpha/memorystore/instances/reschedule-maintenance @@ -0,0 +1,94 @@ +NAME + gcloud alpha memorystore instances reschedule-maintenance - reschedule + maintenance window for an instance + +SYNOPSIS + gcloud alpha memorystore instances reschedule-maintenance + (INSTANCE : --location=LOCATION) --reschedule-type=RESCHEDULE_TYPE + [--async] [--schedule-time=SCHEDULE_TIME] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Reschedule maintenance window for an instance. + +EXAMPLES + To reschedule maintenance window for an instance with the name my-instance + in region us-central-1 with immediate, run: + + $ gcloud alpha memorystore instances reschedule-maintenance \ + `my-instance` --project=my-project --location=us-central1 \ + --reschedule-type=IMMEDIATE + +POSITIONAL ARGUMENTS + Instance resource - Name of the instance to reschedule maintenance for: + projects/{project}/locations/{location_id}/instances/{instance} The + arguments in this group can be used to specify the attributes of this + resource. (NOTE) Some attributes are not given arguments in this group but + can be set in other ways. + + To set the project attribute: + ◆ provide the argument instance on the command line with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + INSTANCE + ID of the instance or fully qualified identifier for the instance. + + To set the instance attribute: + ▸ provide the argument instance on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + The location id of the instance resource. + + To set the location attribute: + ▸ provide the argument instance on the command line with a fully + specified name; + ▸ provide the argument --location on the command line. + +REQUIRED FLAGS + --reschedule-type=RESCHEDULE_TYPE + If reschedule type is SPECIFIC_TIME, schedule_time must be set. + RESCHEDULE_TYPE must be one of: + + immediate + If the user wants to schedule the maintenance to happen now. + specific-time + If the user wants to reschedule the maintenance to a specific time. + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --schedule-time=SCHEDULE_TIME + Timestamp when the maintenance shall be rescheduled to if + reschedule_type=SPECIFIC_TIME, in RFC 3339 format. Example: + 2012-11-15T16:19:00.094Z. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the memorystore/v1alpha API. The full documentation for + this API can be found at: https://cloud.google.com/memorystore/ + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. These variants are also available: + + $ gcloud memorystore instances reschedule-maintenance + + $ gcloud beta memorystore instances reschedule-maintenance + diff --git a/gcloud/alpha/memorystore/instances/update b/gcloud/alpha/memorystore/instances/update index 85b1c08fa..491654118 100644 --- a/gcloud/alpha/memorystore/instances/update +++ b/gcloud/alpha/memorystore/instances/update @@ -3,17 +3,25 @@ NAME Memorystore instance SYNOPSIS - gcloud alpha memorystore instances update (INSTANCE : --location=LOCATION) - [--async] [--[no-]async-instance-endpoints-deletion-enabled] + gcloud alpha memorystore instances update INSTANCE [--async] + [--[no-]async-instance-endpoints-deletion-enabled] [--[no-]deletion-protection-enabled] [--engine-version=ENGINE_VERSION] - [--mode=MODE] [--node-type=NODE_TYPE] [--[no-]ondemand-maintenance] - [--replica-count=REPLICA_COUNT] [--request-id=REQUEST_ID] - [--shard-count=SHARD_COUNT] + [--location=LOCATION] [--mode=MODE] [--node-type=NODE_TYPE] + [--[no-]ondemand-maintenance] [--replica-count=REPLICA_COUNT] + [--request-id=REQUEST_ID] [--shard-count=SHARD_COUNT] [--aof-config-append-fsync=AOF_CONFIG_APPEND_FSYNC --clear-persistence-config --persistence-config-mode=PERSISTENCE_CONFIG_MODE --rdb-config-snapshot-period=RDB_CONFIG_SNAPSHOT_PERIOD --rdb-config-snapshot-start-time=RDB_CONFIG_SNAPSHOT_START_TIME] + [--clear-cross-instance-replication-config + --cross-instance-replication-config-role=CROSS_INSTANCE_REPLICATION_CONFIG_ROLE --clear-primary-instance | --primary-instance=PRIMARY_INSTANCE --cross-instance-replication-config-secondary-instances=[instance=INSTANCE] | --add-cross-instance-replication-config-secondary-instances=[instance=INSTANCE] --clear-cross-instance-replication-config-secondary-instances | --remove-cross-instance-replication-config-secondary-instances=[instance=INSTANCE]] + [--clear-maintenance-policy + --maintenance-policy-weekly-window=[day=DAY],[startTime=STARTTIME] + | --add-maintenance-policy-weekly-window=[day=DAY], + [startTime=STARTTIME] --clear-maintenance-policy-weekly-window + | --remove-maintenance-policy-weekly-window=[day=DAY], + [startTime=STARTTIME]] [--endpoints=[connections=CONNECTIONS] | --add-endpoints=[connections=CONNECTIONS] --clear-endpoints | --remove-endpoints=[connections=CONNECTIONS]] @@ -44,10 +52,9 @@ EXAMPLES POSITIONAL ARGUMENTS Instance resource - Identifier. Unique name of the instance. Format: - projects/{project}/locations/{location}/instances/{instance} 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}/locations/{location}/instances/{instance} 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 instance on the command line with a fully @@ -55,6 +62,11 @@ POSITIONAL ARGUMENTS ◆ provide the argument --project on the command line; ◆ set the property core/project. + To set the location attribute: + ◆ provide the argument instance on the command line with a fully + specified name; + ◆ provide the argument --location on the command line. + This must be specified. INSTANCE @@ -63,17 +75,6 @@ POSITIONAL ARGUMENTS To set the instance attribute: ▸ provide the argument instance on the command line. - This positional argument must be specified if any of the other - arguments in this group are specified. - - --location=LOCATION - The location id of the instance resource. - - To set the location attribute: - ▸ provide the argument instance on the command line with a fully - specified name; - ▸ provide the argument --location on the command line. - FLAGS --async Return immediately, without waiting for the operation in progress to @@ -99,6 +100,11 @@ FLAGS --engine-version=ENGINE_VERSION Engine version of the instance. + --location=LOCATION + For resources [instance], provides fallback value for resource location + attribute. When the resource's full URI path is not provided, location + will fallback to this flag value. + --mode=MODE The mode config for the instance. MODE must be one of: @@ -203,6 +209,289 @@ FLAGS future snapshots will be aligned. If not provided, the current time will be used. + Cross instance replication config. + + --clear-cross-instance-replication-config + Set instance.crossInstanceReplicationConfig back to default value. + + --cross-instance-replication-config-role=CROSS_INSTANCE_REPLICATION_CONFIG_ROLE + The role of the instance in cross instance replication. + CROSS_INSTANCE_REPLICATION_CONFIG_ROLE must be one of: + + none + This instance does not participate in cross instance replication. + It is an independent instance and does not replicate to or from + any other instances. + primary + A instance that allows both reads and writes. Any data written to + this instance is also replicated to the attached secondary + instances. + secondary + A instance that allows only reads and replicates data from a + primary instance. + + Details of the remote instance associated with this instance in a cross + instance replication setup. + + Update primary_instance. + + At most one of these can be specified: + + --clear-primary-instance + Clear primary_instance value and set to null. + + Instance resource - Set primary_instance to new value. + + The full resource path of the remote instance in the format: + projects//locations//instances/ 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 --primary-instance on the command line + with a fully specified name; + ◇ provide the argument --project on the command line; + ◇ set the property core/project. + + To set the location attribute: + ◇ provide the argument --primary-instance on the command line + with a fully specified name; + ◇ provide the argument --location on the command line. + + --primary-instance=PRIMARY_INSTANCE + ID of the instance or fully qualified identifier for the + instance. + + To set the instance attribute: + ▹ provide the argument --primary-instance on the command + line. + + Update cross_instance_replication_config_secondary_instances. + + At most one of these can be specified: + + --cross-instance-replication-config-secondary-instances=[instance=INSTANCE] + Set cross_instance_replication_config_secondary_instances to new + value. List of secondary instances that are replicating from this + primary instance. + + This field is only set for a primary instance. + + instance + The full resource path of the remote instance in the format: + projects//locations//instances/. + + Shorthand Example: + + --cross-instance-replication-config-secondary-instances=instance=string --cross-instance-replication-config-secondary-instances=instance=string + + JSON Example: + + --cross-instance-replication-config-secondary-instances='[{"instance": "string"}]' + + File Example: + + --cross-instance-replication-config-secondary-instances=path_to_file.(yaml|json) + + --add-cross-instance-replication-config-secondary-instances=[instance=INSTANCE] + Add new value to + cross_instance_replication_config_secondary_instances list. List of + secondary instances that are replicating from this primary + instance. + + This field is only set for a primary instance. + + instance + The full resource path of the remote instance in the format: + projects//locations//instances/. + + Shorthand Example: + + --add-cross-instance-replication-config-secondary-instances=instance=string --add-cross-instance-replication-config-secondary-instances=instance=string + + JSON Example: + + --add-cross-instance-replication-config-secondary-instances='[{"instance": "string"}]' + + File Example: + + --add-cross-instance-replication-config-secondary-instances=path_to_file.(yaml|json) + + At most one of these can be specified: + + --clear-cross-instance-replication-config-secondary-instances + Clear cross_instance_replication_config_secondary_instances value + and set to empty list. + + --remove-cross-instance-replication-config-secondary-instances=[instance=INSTANCE] + Remove existing value from + cross_instance_replication_config_secondary_instances list. List + of secondary instances that are replicating from this primary + instance. + + This field is only set for a primary instance. + + instance + The full resource path of the remote instance in the format: + projects//locations//instances/. + + Shorthand Example: + + --remove-cross-instance-replication-config-secondary-instances=instance=string --remove-cross-instance-replication-config-secondary-instances=instance=string + + JSON Example: + + --remove-cross-instance-replication-config-secondary-instances='[{"instance": "string"}]' + + File Example: + + --remove-cross-instance-replication-config-secondary-instances=path_to_file.(yaml|json) + + Maintenance policy per instance. + + --clear-maintenance-policy + Set instance.maintenancePolicy back to default value. + + Update maintenance_policy_weekly_window. + + At most one of these can be specified: + + --maintenance-policy-weekly-window=[day=DAY],[startTime=STARTTIME] + Set maintenance_policy_weekly_window to new value. Maintenance + window that is applied to resources covered by this policy. Minimum + 1. For the current version, the maximum number of weekly_window is + expected to be one. + + day + Allows to define schedule that runs specified day of the week. + + startTime + Start time of the window in UTC. + + hours + Hours of a day in 24 hour format. Must be greater than or + equal to 0 and typically must be less than or equal to 23. + An API may choose to allow the value "24:00:00" for + scenarios like business closing time. + + minutes + Minutes of an hour. Must be greater than or equal to 0 and + less than or equal to 59. + + nanos + Fractions of seconds, in nanoseconds. Must be greater than + or equal to 0 and less than or equal to 999,999,999. + + seconds + Seconds of a minute. Must be greater than or equal to 0 and + typically must be less than or equal to 59. An API may + allow the value 60 if it allows leap-seconds. + + Shorthand Example: + + --maintenance-policy-weekly-window=day=string,startTime={hours=int,minutes=int,nanos=int,seconds=int} --maintenance-policy-weekly-window=day=string,startTime={hours=int,minutes=int,nanos=int,seconds=int} + + JSON Example: + + --maintenance-policy-weekly-window='[{"day": "string", "startTime": {"hours": int, "minutes": int, "nanos": int, "seconds": int}}]' + + File Example: + + --maintenance-policy-weekly-window=path_to_file.(yaml|json) + + --add-maintenance-policy-weekly-window=[day=DAY],[startTime=STARTTIME] + Add new value to maintenance_policy_weekly_window list. Maintenance + window that is applied to resources covered by this policy. Minimum + 1. For the current version, the maximum number of weekly_window is + expected to be one. + + day + Allows to define schedule that runs specified day of the week. + + startTime + Start time of the window in UTC. + + hours + Hours of a day in 24 hour format. Must be greater than or + equal to 0 and typically must be less than or equal to 23. + An API may choose to allow the value "24:00:00" for + scenarios like business closing time. + + minutes + Minutes of an hour. Must be greater than or equal to 0 and + less than or equal to 59. + + nanos + Fractions of seconds, in nanoseconds. Must be greater than + or equal to 0 and less than or equal to 999,999,999. + + seconds + Seconds of a minute. Must be greater than or equal to 0 and + typically must be less than or equal to 59. An API may + allow the value 60 if it allows leap-seconds. + + Shorthand Example: + + --add-maintenance-policy-weekly-window=day=string,startTime={hours=int,minutes=int,nanos=int,seconds=int} --add-maintenance-policy-weekly-window=day=string,startTime={hours=int,minutes=int,nanos=int,seconds=int} + + JSON Example: + + --add-maintenance-policy-weekly-window='[{"day": "string", "startTime": {"hours": int, "minutes": int, "nanos": int, "seconds": int}}]' + + File Example: + + --add-maintenance-policy-weekly-window=path_to_file.(yaml|json) + + At most one of these can be specified: + + --clear-maintenance-policy-weekly-window + Clear maintenance_policy_weekly_window value and set to empty + list. + + --remove-maintenance-policy-weekly-window=[day=DAY],[startTime=STARTTIME] + Remove existing value from maintenance_policy_weekly_window list. + Maintenance window that is applied to resources covered by this + policy. Minimum 1. For the current version, the maximum number of + weekly_window is expected to be one. + + day + Allows to define schedule that runs specified day of the + week. + + startTime + Start time of the window in UTC. + + hours + Hours of a day in 24 hour format. Must be greater than or + equal to 0 and typically must be less than or equal to + 23. An API may choose to allow the value "24:00:00" for + scenarios like business closing time. + + minutes + Minutes of an hour. Must be greater than or equal to 0 + and less than or equal to 59. + + nanos + Fractions of seconds, in nanoseconds. Must be greater + than or equal to 0 and less than or equal to 999,999,999. + + seconds + Seconds of a minute. Must be greater than or equal to 0 + and typically must be less than or equal to 59. An API + may allow the value 60 if it allows leap-seconds. + + Shorthand Example: + + --remove-maintenance-policy-weekly-window=day=string,startTime={hours=int,minutes=int,nanos=int,seconds=int} --remove-maintenance-policy-weekly-window=day=string,startTime={hours=int,minutes=int,nanos=int,seconds=int} + + JSON Example: + + --remove-maintenance-policy-weekly-window='[{"day": "string", "startTime": {"hours": int, "minutes": int, "nanos": int, "seconds": int}}]' + + File Example: + + --remove-maintenance-policy-weekly-window=path_to_file.(yaml|json) + Update endpoints. At most one of these can be specified: diff --git a/gcloud/alpha/run/deploy b/gcloud/alpha/run/deploy index 58d7126ff..4f231e527 100644 --- a/gcloud/alpha/run/deploy +++ b/gcloud/alpha/run/deploy @@ -49,9 +49,6 @@ SYNOPSIS --update-secrets=[KEY=VALUE,...] --command=[COMMAND,...] | --function=FUNCTION --image=IMAGE --source=SOURCE] [--binary-authorization=POLICY | --clear-binary-authorization] - [--clear-config-maps | --set-config-maps=[KEY=VALUE,...] - | --remove-config-maps=[KEY,...] - --update-config-maps=[KEY=VALUE,...]] [--clear-encryption-key-shutdown-hours | --encryption-key-shutdown-hours=ENCRYPTION_KEY_SHUTDOWN_HOURS] [--clear-key | --key=KEY] @@ -696,37 +693,6 @@ FLAGS --clear-binary-authorization Remove any previously set Binary Authorization policy. - Specify config map to mount or provide as environment variables. Keys - starting with a forward slash '/' are mount paths. All other keys - correspond to environment variables. The values associated with each of - these should be in the form CONFIG_MAP_NAME:KEY_IN_CONFIG_MAP; you may - omit the key within the config map to specify a mount of all keys within - the config map. For example: - '--update-config-maps=/my/path=myconfig,ENV=otherconfig:key.json' will - create a volume with config map 'myconfig' and mount that volume at - '/my/path'. Because no config map key was specified, all keys in - 'myconfig' will be included. An environment variable named ENV will also - be created whose value is the value of 'key.json' in 'otherconfig. Not - supported on the fully managed version of Cloud Run. - - At most one of these can be specified: - - --clear-config-maps - Remove all config-maps. - - --set-config-maps=[KEY=VALUE,...] - List of key-value pairs to set as config-maps. All existing - config-maps will be removed first. - - Only --update-config-maps and --remove-config-maps can be used together. - If both are specified, --remove-config-maps will be applied first. - - --remove-config-maps=[KEY,...] - List of config-maps to be removed. - - --update-config-maps=[KEY=VALUE,...] - List of key-value pairs to set as config-maps. - At most one of these can be specified: --clear-encryption-key-shutdown-hours diff --git a/gcloud/alpha/run/multi-region-services/update b/gcloud/alpha/run/multi-region-services/update index c45d03e1a..0adc9618c 100644 --- a/gcloud/alpha/run/multi-region-services/update +++ b/gcloud/alpha/run/multi-region-services/update @@ -32,17 +32,16 @@ SYNOPSIS --clear-volumes --remove-volume=[VOLUME,...]] [--add-volume-mount=[volume=NAME,mount-path=MOUNT_PATH,...] --args=[ARG,...] --clear-volume-mounts --command=[COMMAND,...] - --cpu=CPU --depends-on=[CONTAINER,...] --image=IMAGE --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,...] + --cpu=CPU --depends-on=[CONTAINER,...] --image=IMAGE + --liveness-probe=[KEY=VALUE,...] --memory=MEMORY --port=PORT + --remove-volume-mount=[MOUNT_PATH,...] + --startup-probe=[KEY=VALUE,...] --[no-]use-http2 --clear-env-vars + | --env-vars-file=FILE_PATH | --set-env-vars=[KEY=VALUE,...] + | --remove-env-vars=[KEY,...] --update-env-vars=[KEY=VALUE,...] --clear-secrets | --set-secrets=[KEY=VALUE,...] | --remove-secrets=[KEY,...] --update-secrets=[KEY=VALUE,...]] [--binary-authorization=POLICY | --clear-binary-authorization] - [--clear-config-maps | --set-config-maps=[KEY=VALUE,...] - | --remove-config-maps=[KEY,...] - --update-config-maps=[KEY=VALUE,...]] [--clear-encryption-key-shutdown-hours | --encryption-key-shutdown-hours=ENCRYPTION_KEY_SHUTDOWN_HOURS] [--clear-key | --key=KEY] @@ -391,6 +390,30 @@ FLAGS Name of the container image to deploy (e.g. us-docker.pkg.dev/cloudrun/container/hello:latest). + --liveness-probe=[KEY=VALUE,...] + Comma separated settings for liveness probe in the form KEY=VALUE. + Each key stands for a field of the probe described in + https://cloud.google.com/run/docs/reference/rest/v1/Container#Probe. + Currently supported keys are: + + + initialDelaySeconds: integer + + timeoutSeconds: integer + + periodSeconds: integer + + failureThreshold: integer + + httpGet.port: integer + + httpGet.path: string + + grpc.port: integer + + grpc.service: string + + For example, to set a probe with 10s timeout and HTTP probe + requests sent to 8080 port of the container: + + $ --liveness-probe=timeoutSeconds=10,httpGet.port=8080 + + To remove existing probe: + + $ --liveness-probe="" + --memory=MEMORY Set a memory limit. Ex: 1024Mi, 4Gi. @@ -406,6 +429,31 @@ FLAGS Removes the volume mounted at the specified path from the current container. + --startup-probe=[KEY=VALUE,...] + Comma separated settings for startup probe in the form KEY=VALUE. + Each key stands for a field of the probe described in + https://cloud.google.com/run/docs/reference/rest/v1/Container#Probe. + Currently supported keys are: + + + initialDelaySeconds: integer + + timeoutSeconds: integer + + periodSeconds: integer + + failureThreshold: integer + + httpGet.port: integer + + httpGet.path: string + + grpc.port: integer + + grpc.service: string + + tcpSocket.port: integer + + For example, to set a probe with 10s timeout and HTTP probe + requests sent to 8080 port of the container: + + $ --startup-probe=timeoutSeconds=10,httpGet.port=8080 + + To remove existing probe: + + $ --startup-probe="" + --[no-]use-http2 Whether to use HTTP/2 for connections to the service. Use --use-http2 to enable and --no-use-http2 to disable. @@ -473,37 +521,6 @@ FLAGS --clear-binary-authorization Remove any previously set Binary Authorization policy. - Specify config map to mount or provide as environment variables. Keys - starting with a forward slash '/' are mount paths. All other keys - correspond to environment variables. The values associated with each of - these should be in the form CONFIG_MAP_NAME:KEY_IN_CONFIG_MAP; you may - omit the key within the config map to specify a mount of all keys within - the config map. For example: - '--update-config-maps=/my/path=myconfig,ENV=otherconfig:key.json' will - create a volume with config map 'myconfig' and mount that volume at - '/my/path'. Because no config map key was specified, all keys in - 'myconfig' will be included. An environment variable named ENV will also - be created whose value is the value of 'key.json' in 'otherconfig. Not - supported on the fully managed version of Cloud Run. - - At most one of these can be specified: - - --clear-config-maps - Remove all config-maps. - - --set-config-maps=[KEY=VALUE,...] - List of key-value pairs to set as config-maps. All existing - config-maps will be removed first. - - Only --update-config-maps and --remove-config-maps can be used together. - If both are specified, --remove-config-maps will be applied first. - - --remove-config-maps=[KEY,...] - List of config-maps to be removed. - - --update-config-maps=[KEY=VALUE,...] - List of key-value pairs to set as config-maps. - At most one of these can be specified: --clear-encryption-key-shutdown-hours diff --git a/gcloud/alpha/run/services/update b/gcloud/alpha/run/services/update index 079719d1d..008bd198c 100644 --- a/gcloud/alpha/run/services/update +++ b/gcloud/alpha/run/services/update @@ -40,9 +40,6 @@ SYNOPSIS | --set-secrets=[KEY=VALUE,...] | --remove-secrets=[KEY,...] --update-secrets=[KEY=VALUE,...]] [--binary-authorization=POLICY | --clear-binary-authorization] - [--clear-config-maps | --set-config-maps=[KEY=VALUE,...] - | --remove-config-maps=[KEY,...] - --update-config-maps=[KEY=VALUE,...]] [--clear-encryption-key-shutdown-hours | --encryption-key-shutdown-hours=ENCRYPTION_KEY_SHUTDOWN_HOURS] [--clear-key | --key=KEY] @@ -567,37 +564,6 @@ FLAGS --clear-binary-authorization Remove any previously set Binary Authorization policy. - Specify config map to mount or provide as environment variables. Keys - starting with a forward slash '/' are mount paths. All other keys - correspond to environment variables. The values associated with each of - these should be in the form CONFIG_MAP_NAME:KEY_IN_CONFIG_MAP; you may - omit the key within the config map to specify a mount of all keys within - the config map. For example: - '--update-config-maps=/my/path=myconfig,ENV=otherconfig:key.json' will - create a volume with config map 'myconfig' and mount that volume at - '/my/path'. Because no config map key was specified, all keys in - 'myconfig' will be included. An environment variable named ENV will also - be created whose value is the value of 'key.json' in 'otherconfig. Not - supported on the fully managed version of Cloud Run. - - At most one of these can be specified: - - --clear-config-maps - Remove all config-maps. - - --set-config-maps=[KEY=VALUE,...] - List of key-value pairs to set as config-maps. All existing - config-maps will be removed first. - - Only --update-config-maps and --remove-config-maps can be used together. - If both are specified, --remove-config-maps will be applied first. - - --remove-config-maps=[KEY,...] - List of config-maps to be removed. - - --update-config-maps=[KEY=VALUE,...] - List of key-value pairs to set as config-maps. - At most one of these can be specified: --clear-encryption-key-shutdown-hours diff --git a/gcloud/alpha/spanner/databases/execute-sql b/gcloud/alpha/spanner/databases/execute-sql index 6f0e8674f..1b48ad917 100644 --- a/gcloud/alpha/spanner/databases/execute-sql +++ b/gcloud/alpha/spanner/databases/execute-sql @@ -78,8 +78,14 @@ OPTIONAL FLAGS Returns only the query plan, without any result rows or execution statistics information. PROFILE - Returns both the query plan and the execution statistics along with - the result rows. + Returns the query plan, overall execution statistics, + operator-level execution statistics, along with the result rows. + WITH_PLAN_AND_STATS + Returns the query plan, overall (but not operator-level) execution + statistics, along with the results. + WITH_STATS + Returns the overall (but not operator-level) execution statistics + along with the results. --timeout=TIMEOUT; default="10m" Maximum time to wait for the SQL query to complete. See $ gcloud topic diff --git a/gcloud/alpha/sql/backups/restore b/gcloud/alpha/sql/backups/restore index f8ca7b188..821019a00 100644 --- a/gcloud/alpha/sql/backups/restore +++ b/gcloud/alpha/sql/backups/restore @@ -34,6 +34,8 @@ SYNOPSIS [--retained-backups-count=RETAINED_BACKUPS_COUNT] [--retained-transaction-log-days=RETAINED_TRANSACTION_LOG_DAYS] [--ssl-mode=SSL_MODE] [--[no-]storage-auto-increase] + [--storage-provisioned-iops=STORAGE_PROVISIONED_IOPS] + [--storage-provisioned-throughput=STORAGE_PROVISIONED_THROUGHPUT] [--storage-size=STORAGE_SIZE] [--storage-type=STORAGE_TYPE] [--tier=TIER, -t TIER] [--time-zone=TIME_ZONE] [--timeout=TIMEOUT; default=3600] @@ -309,6 +311,14 @@ OPTIONAL FLAGS --storage-auto-increase to enable and --no-storage-auto-increase to disable. + --storage-provisioned-iops=STORAGE_PROVISIONED_IOPS + Indicates how many IOPS to provision for the data disk. This sets the + number of I/O operations per second that the disk can handle. + + --storage-provisioned-throughput=STORAGE_PROVISIONED_THROUGHPUT + Indicates how much throughput to provision for the data disk. This sets + the throughput in MB per second that the disk can handle. + --storage-size=STORAGE_SIZE Amount of storage allocated to the instance. Must be an integer number of GB. The default is 10GB. Information on storage limits can be found diff --git a/gcloud/alpha/sql/instances/create b/gcloud/alpha/sql/instances/create index 01c8c2a50..02d57c704 100644 --- a/gcloud/alpha/sql/instances/create +++ b/gcloud/alpha/sql/instances/create @@ -13,15 +13,18 @@ SYNOPSIS [--availability-type=AVAILABILITY_TYPE] [--no-backup] [--backup-location=BACKUP_LOCATION] [--backup-start-time=BACKUP_START_TIME] [--cascadable-replica] - [--collation=COLLATION] [--connector-enforcement=CONNECTOR_ENFORCEMENT] - [--cpu=CPU] [--custom-subject-alternative-names=DNS,[DNS,[DNS]]] + [--collation=COLLATION] + [--connection-pool-flags=FLAG=VALUE,[FLAG=VALUE,...]] + [--connector-enforcement=CONNECTOR_ENFORCEMENT] [--cpu=CPU] + [--custom-subject-alternative-names=DNS,[DNS,[DNS]]] [--database-flags=FLAG=VALUE,[FLAG=VALUE,...]] [--database-version=DATABASE_VERSION; default="MYSQL_8_0"] [--[no-]deletion-protection] [--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] - [--edition=EDITION] [--enable-bin-log] [--[no-]enable-data-cache] + [--edition=EDITION] [--enable-bin-log] + [--[no-]enable-connection-pooling] [--[no-]enable-data-cache] [--[no-]enable-dataplex-integration] [--[no-]enable-google-ml-integration] [--enable-google-private-path] [--enable-password-policy] [--enable-point-in-time-recovery] @@ -46,12 +49,15 @@ SYNOPSIS [--[no-]recreate-replicas-on-primary-crash] [--replica-type=REPLICA_TYPE] [--replication=REPLICATION] [--replication-lag-max-seconds-for-recreate=REPLICATION_LAG_MAX_SECONDS_FOR_RECREATE] - [--require-ssl] [--retained-backups-count=RETAINED_BACKUPS_COUNT] + [--require-ssl] [--[no-]retain-backups-on-delete] + [--retained-backups-count=RETAINED_BACKUPS_COUNT] [--retained-transaction-log-days=RETAINED_TRANSACTION_LOG_DAYS] [--root-password=ROOT_PASSWORD] [--server-ca-mode=SERVER_CA_MODE] [--server-ca-pool=SERVER_CA_POOL] [--ssl-mode=SSL_MODE] [--[no-]storage-auto-increase] [--storage-auto-increase-limit=STORAGE_AUTO_INCREASE_LIMIT] + [--storage-provisioned-iops=STORAGE_PROVISIONED_IOPS] + [--storage-provisioned-throughput=STORAGE_PROVISIONED_THROUGHPUT] [--storage-size=STORAGE_SIZE] [--storage-type=STORAGE_TYPE] [--tags=TAG=VALUE,[TAG=VALUE,...]] [--threads-per-core=THREADS_PER_CORE] [--tier=TIER, -t TIER] @@ -77,28 +83,28 @@ DESCRIPTION (ALPHA) Creates a new Cloud SQL instance. EXAMPLES - To create a MySQL 5.7 instance with ID prod-instance that has 2 CPUs, 4 GB + To create a MySQL 8.0 instance with ID prod-instance that has 2 CPUs, 4 GB of RAM, and is in the region us-central1 (a zone will be auto-assigned), where the 'root' user has its password set to password123, run: $ gcloud alpha sql instances create prod-instance \ - --database-version=MYSQL_5_7 --cpu=2 --memory=4GB \ + --database-version=MYSQL_8_0 --cpu=2 --memory=4GB \ --region=us-central1 --root-password=password123 - To create a Postgres 9.6 instance with ID prod-instance that has 2 CPUs, 8 + To create a Postgres 15 instance with ID prod-instance that has 2 CPUs, 8 GiB of RAM, and is in the zone us-central1-a, where the 'postgres' user has its password set to password123, run: $ gcloud alpha sql instances create prod-instance \ - --database-version=POSTGRES_9_6 --cpu=2 --memory=8GiB \ + --database-version=POSTGRES_15 --cpu=2 --memory=8GiB \ --zone=us-central1-a --root-password=password123 - To create a SQL Server 2017 Express instance with ID prod-instance that has + To create a SQL Server 2022 Express instance with ID prod-instance that has 2 CPUs, 3840MiB of RAM, and is in the zone us-central1-a, where the 'sqlserver' user has its password set to password123, run: $ gcloud alpha sql instances create prod-instance \ - --database-version=SQLSERVER_2017_EXPRESS --cpu=2 \ + --database-version=SQLSERVER_2022_EXPRESS --cpu=2 \ --memory=3840MiB --zone=us-central1-a \ --root-password=password123 @@ -185,6 +191,12 @@ FLAGS Cloud SQL server-level collation setting, which specifies the set of rules for comparing characters in a character set. + --connection-pool-flags=FLAG=VALUE,[FLAG=VALUE,...] + Comma-separated list of connection pool flags to set on the instance + connection pool. Use an equals sign to separate flag name and value. + View the Instance Resource API for allowed flags. (e.g., + --connection-pool-flags max_pool_size=1000,max_client_connections=2000) + --connector-enforcement=CONNECTOR_ENFORCEMENT Cloud SQL Connector enforcement mode. It determines how Cloud SQL Connectors are used in the connection. See the list of modes here @@ -250,6 +262,11 @@ FLAGS fraction of a second. Must have automatic backups enabled to use. Make sure storage can support at least 7 days of logs. + --[no-]enable-connection-pooling + Enable connection pooling for the instance. Use + --enable-connection-pooling to enable and + --no-enable-connection-pooling to disable. + --[no-]enable-data-cache Enable use of data cache for accelerated read performance. This flag is only available for Enterprise_Plus edition instances. Use @@ -449,6 +466,11 @@ FLAGS --require-ssl Specified if users connecting over IP must use SSL. + --[no-]retain-backups-on-delete + Retain automated/ondemand backups of the instance after the instance is + deleted. Use --retain-backups-on-delete to enable and + --no-retain-backups-on-delete to disable. + --retained-backups-count=RETAINED_BACKUPS_COUNT How many backups to keep. The valid range is between 1 and 365. Default value is 7 for Enterprise edition instances. For Enterprise_Plus, @@ -507,6 +529,14 @@ FLAGS increases to your capacity will stop once this limit has been reached. Default capacity is unlimited. + --storage-provisioned-iops=STORAGE_PROVISIONED_IOPS + Indicates how many IOPS to provision for the data disk. This sets the + number of I/O operations per second that the disk can handle. + + --storage-provisioned-throughput=STORAGE_PROVISIONED_THROUGHPUT + Indicates how much throughput to provision for the data disk. This sets + the throughput in MB per second that the disk can handle. + --storage-size=STORAGE_SIZE Amount of storage allocated to the instance. Must be an integer number of GB. The default is 10GB. Information on storage limits can be found diff --git a/gcloud/alpha/sql/instances/patch b/gcloud/alpha/sql/instances/patch index 66f7fd3d3..77129a282 100644 --- a/gcloud/alpha/sql/instances/patch +++ b/gcloud/alpha/sql/instances/patch @@ -17,7 +17,8 @@ SYNOPSIS [--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] [--diff] - [--edition=EDITION] [--[no-]enable-bin-log] [--[no-]enable-data-cache] + [--edition=EDITION] [--[no-]enable-bin-log] + [--[no-]enable-connection-pooling] [--[no-]enable-data-cache] [--[no-]enable-database-replication] [--[no-]enable-dataplex-integration] [--[no-]enable-google-ml-integration] @@ -46,9 +47,12 @@ SYNOPSIS [--[no-]recreate-replicas-on-primary-crash] [--remove-deny-maintenance-period] [--replication=REPLICATION] [--replication-lag-max-seconds-for-recreate=REPLICATION_LAG_MAX_SECONDS_FOR_RECREATE] - [--[no-]require-ssl] [--simulate-maintenance-event] - [--ssl-mode=SSL_MODE] [--[no-]storage-auto-increase] + [--[no-]require-ssl] [--[no-]retain-backups-on-delete] + [--simulate-maintenance-event] [--ssl-mode=SSL_MODE] + [--[no-]storage-auto-increase] [--storage-auto-increase-limit=STORAGE_AUTO_INCREASE_LIMIT] + [--storage-provisioned-iops=STORAGE_PROVISIONED_IOPS] + [--storage-provisioned-throughput=STORAGE_PROVISIONED_THROUGHPUT] [--storage-size=STORAGE_SIZE] [--switch-transaction-logs-to-cloud-storage] [--threads-per-core=THREADS_PER_CORE] [--tier=TIER, -t TIER] @@ -59,6 +63,8 @@ SYNOPSIS [--authorized-gae-apps=APP,[APP,...] | --clear-gae-apps] [--authorized-networks=NETWORK,[NETWORK,...] | --clear-authorized-networks] + [--clear-connection-pool-flags + | --connection-pool-flags=FLAG=VALUE,[FLAG=VALUE,...]] [--clear-custom-subject-alternative-names | --custom-subject-alternative-names=DNS,[DNS,[DNS]]] [--clear-database-flags | --database-flags=FLAG=VALUE,[FLAG=VALUE,...]] @@ -191,6 +197,11 @@ FLAGS sure storage can support at least 7 days of logs. Use --enable-bin-log to enable and --no-enable-bin-log to disable. + --[no-]enable-connection-pooling + Enable connection pooling for the instance. Use + --enable-connection-pooling to enable and + --no-enable-connection-pooling to disable. + --[no-]enable-data-cache Enable use of data cache for accelerated read performance. This flag is only available for Enterprise_Plus edition instances. Use @@ -386,6 +397,11 @@ FLAGS mysqld should default to 'REQUIRE X509' for users connecting over IP. Use --require-ssl to enable and --no-require-ssl to disable. + --[no-]retain-backups-on-delete + Retain automated/ondemand backups of the instance after the instance is + deleted. Use --retain-backups-on-delete to enable and + --no-retain-backups-on-delete to disable. + --simulate-maintenance-event Simulate a maintenance event without changing the version. Only applicable to instances that support near-zero downtime planned @@ -418,6 +434,14 @@ FLAGS increases to your capacity will stop once this limit has been reached. Default capacity is unlimited. + --storage-provisioned-iops=STORAGE_PROVISIONED_IOPS + Indicates how many IOPS to provision for the data disk. This sets the + number of I/O operations per second that the disk can handle. + + --storage-provisioned-throughput=STORAGE_PROVISIONED_THROUGHPUT + Indicates how much throughput to provision for the data disk. This sets + the throughput in MB per second that the disk can handle. + --storage-size=STORAGE_SIZE Amount of storage allocated to the instance. Must be an integer number of GB. The default is 10GB. Information on storage limits can be found @@ -496,6 +520,18 @@ FLAGS Clear the list of external networks that are allowed to connect to the instance. + At most one of these can be specified: + + --clear-connection-pool-flags + This will clear the connection pool flags set on the instance. + + --connection-pool-flags=FLAG=VALUE,[FLAG=VALUE,...] + Comma-separated list of connection pool flags to set on the instance + connection pool. Use an equals sign to separate flag name and value. + View the Instance Resource API for allowed flags. (e.g., + --connection-pool-flags + max_pool_size=1000,max_client_connections=2000) + At most one of these can be specified: --clear-custom-subject-alternative-names diff --git a/gcloud/alpha/storage/help b/gcloud/alpha/storage/help index 1a2c14dc0..7188b37b8 100644 --- a/gcloud/alpha/storage/help +++ b/gcloud/alpha/storage/help @@ -35,6 +35,9 @@ GROUPS insights (ALPHA) Manage Cloud Storage inventory reports. + intelligence-configs + (ALPHA) Manage Cloud Storage Intelligence Configurations. + managed-folders (ALPHA) Manage Cloud Storage managed folders. diff --git a/gcloud/alpha/storage/intelligence-configs/describe b/gcloud/alpha/storage/intelligence-configs/describe new file mode 100644 index 000000000..7a16e3c6c --- /dev/null +++ b/gcloud/alpha/storage/intelligence-configs/describe @@ -0,0 +1,45 @@ +NAME + gcloud alpha storage intelligence-configs describe - describes storage + intelligence configuration + +SYNOPSIS + gcloud alpha storage intelligence-configs describe + (--organization=ORGANIZATION | --project=PROJECT + | --sub-folder=SUB_FOLDER) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Describe storage intelligence config for the organization, + sub-folder or project. + +EXAMPLES + The following command describes storage intelligence config for the + sub-folder with id 123456. + + $gcloud alpha storage intelligence-configs describe --sub-folder=123456 + +REQUIRED FLAGS + Exactly one of these must be specified: + + --organization=ORGANIZATION + Specifies organization id for the storage intelligence config. + + --project=PROJECT + Specifies project for the storage intelligence config. + + --sub-folder=SUB_FOLDER + Specifies sub-folder id for the storage intelligence config. + +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/intelligence-configs/disable b/gcloud/alpha/storage/intelligence-configs/disable new file mode 100644 index 000000000..4c4e5307f --- /dev/null +++ b/gcloud/alpha/storage/intelligence-configs/disable @@ -0,0 +1,44 @@ +NAME + gcloud alpha storage intelligence-configs disable - disables storage + intelligence + +SYNOPSIS + gcloud alpha storage intelligence-configs disable + (--organization=ORGANIZATION | --project=PROJECT + | --sub-folder=SUB_FOLDER) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Disable storage intelligence for the organization, sub-folder or + project. + +EXAMPLES + The following command disables storage intelligence for the project. + + $gcloud alpha storage intelligence-configs disable --project=my-project + +REQUIRED FLAGS + Exactly one of these must be specified: + + --organization=ORGANIZATION + Specifies organization id for the storage intelligence config. + + --project=PROJECT + Specifies project for the storage intelligence config. + + --sub-folder=SUB_FOLDER + Specifies sub-folder id for the storage intelligence config. + +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/intelligence-configs/enable b/gcloud/alpha/storage/intelligence-configs/enable new file mode 100644 index 000000000..830c315a8 --- /dev/null +++ b/gcloud/alpha/storage/intelligence-configs/enable @@ -0,0 +1,95 @@ +NAME + gcloud alpha storage intelligence-configs enable - enables storage + intelligence + +SYNOPSIS + gcloud alpha storage intelligence-configs enable + (--organization=ORGANIZATION | --project=PROJECT + | --sub-folder=SUB_FOLDER) + [--exclude-locations=[EXCLUDE_LOCATIONS,...] + | --include-locations=[INCLUDE_LOCATIONS,...]] + [--exclude-bucket-id-regexes=[EXCLUDE_BUCKET_ID_REGEXES,...] + | --include-bucket-id-regexes=[INCLUDE_BUCKET_ID_REGEXES,...]] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Enable storage intelligence plan for the organization, sub-folder + or project along with filters. + +EXAMPLES + To remove buckets from the storage intelligence plan, Use the following + command with --exclude-bucket-id-regexes flag. to specify list of bucket id + regexes., + + $gcloud alpha storage intelligence-configs enable --organization=my-org --exclude-bucket-id-regexes="my-bucket-.*" + + To apply location based filters in the storage intelligence plan, Use + --include-locations or --exclude-locations flags to specify allowed list of + locations or excluded list of locations. The following command updates + storage intelligence plan of sub-folder 123456 with the specified list of + included locations., + + $gcloud alpha storage intelligence-configs enable --sub-folder=123456 --include-locations="us-east1","us-west1" + +REQUIRED FLAGS + Exactly one of these must be specified: + + --organization=ORGANIZATION + Specifies organization id for the storage intelligence config. + + --project=PROJECT + Specifies project for the storage intelligence config. + + --sub-folder=SUB_FOLDER + Specifies sub-folder id for the storage intelligence config. + +LOCATION FLAGS + At most one of these can be specified: + + --exclude-locations=[EXCLUDE_LOCATIONS,...] + Comma separated list of locations + (https://cloud.google.com/storage/docs/locations#available-locations) + to exclude in storage intelligence filter. To clear excluded + locations, provide flag with empty list. e.g --exclude-locations="" + or --exclude-locations= . + + --include-locations=[INCLUDE_LOCATIONS,...] + Comma separated list of locations + (https://cloud.google.com/storage/docs/locations#available-locations) + to include in storage intelligence filter. To clear included + locations, provide flag with empty list. e.g --include-locations="" + or --include-locations= . + +BUCKET_FILTER FLAGS + At most one of these can be specified: + + --exclude-bucket-id-regexes=[EXCLUDE_BUCKET_ID_REGEXES,...] + Sets filter for bucket id regexes to exclude. Accepts list of bucket + id regexes in comma separated format. If the regex contains special + characters that may have a specific meaning in the shell, escape them + using backslashes(\). To clear bucket id regexes list, provide flag + with an empty list. e.g --exclude-bucket-id-regexes="" or + --exclude-bucket-id-regexes= . + + --include-bucket-id-regexes=[INCLUDE_BUCKET_ID_REGEXES,...] + Sets filter for bucket id regexes to include. Accepts list of bucket + id regexes in comma separated format. If the regex contains special + characters that may have a specific meaning in the shell, escape them + using backslashes(\). To clear bucket id regexes list, provide flag + with empty list. e.g --include-bucket-id-regexes="" or + --include-bucket-id-regexes= . + +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/intelligence-configs/help b/gcloud/alpha/storage/intelligence-configs/help new file mode 100644 index 000000000..880dc850e --- /dev/null +++ b/gcloud/alpha/storage/intelligence-configs/help @@ -0,0 +1,36 @@ +NAME + gcloud alpha storage intelligence-configs - manage Cloud Storage + Intelligence Configurations + +SYNOPSIS + gcloud alpha storage intelligence-configs COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Manage Cloud Storage Intelligence Configurations. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + describe + (ALPHA) Describes storage intelligence configuration. + + disable + (ALPHA) Disables storage intelligence. + + enable + (ALPHA) Enables storage intelligence. + + update + (ALPHA) Updates storage intelligence configuration. + +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/intelligence-configs/update b/gcloud/alpha/storage/intelligence-configs/update new file mode 100644 index 000000000..92b332e8b --- /dev/null +++ b/gcloud/alpha/storage/intelligence-configs/update @@ -0,0 +1,109 @@ +NAME + gcloud alpha storage intelligence-configs update - updates storage + intelligence configuration + +SYNOPSIS + gcloud alpha storage intelligence-configs update + (--organization=ORGANIZATION | --project=PROJECT + | --sub-folder=SUB_FOLDER) + (--inherit-from-parent + | --exclude-bucket-id-regexes=[EXCLUDE_BUCKET_ID_REGEXES,...] + | --include-bucket-id-regexes=[INCLUDE_BUCKET_ID_REGEXES,...] + --exclude-locations=[EXCLUDE_LOCATIONS,...] + | --include-locations=[INCLUDE_LOCATIONS,...]) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Update storage intelligence configuration for the organization, + sub-folder or project. + +EXAMPLES + To limit buckets in the storage intelligence configuration, Use the + following command with --include-bucket-id-regexes flag. to specify list of + bucket ids and bucket id regexes., + + $gcloud alpha storage intelligence-configs update --organization=my-org --include-bucket-id-regexes=my-bucket-.* + + To apply location based filters in the storage intelligence configuration, + Use --include-locations or --exclude-locations flags to specify allowed + list of locations or excluded list of locations. The following command + updates storage intelligence configuration of sub-folder 123456 with the + specified list of excluded locations., + + $gcloud alpha storage intelligence-configs update --sub-folder=123456 --exclude-locations=us-east1,us-west1 + + The following command updates storage intelligence for the given project by + inheriting existing storage intelligence configuration from the + hierarchical parent resource., + + $gcloud alpha storage intelligence-configs update --project=my-project --inherit-from-parent + + To clear included locations from the project storage intelligence, Use the + following command., + + $gcloud alpha storage intelligence-configs update --project=my-project --include-locations= + +REQUIRED FLAGS + Exactly one of these must be specified: + + --organization=ORGANIZATION + Specifies organization id for the storage intelligence config. + + --project=PROJECT + Specifies project for the storage intelligence config. + + --sub-folder=SUB_FOLDER + Specifies sub-folder id for the storage intelligence config. + + Exactly one of these must be specified: + + --inherit-from-parent + Specifies storage intelligence config to be inherited from parent. + + At most one of these can be specified: + + --exclude-bucket-id-regexes=[EXCLUDE_BUCKET_ID_REGEXES,...] + Sets filter for bucket id regexes to exclude. Accepts list of + bucket id regexes in comma separated format. If the regex contains + special characters that may have a specific meaning in the shell, + escape them using backslashes(\). To clear bucket id regexes list, + provide flag with an empty list. e.g --exclude-bucket-id-regexes="" + or --exclude-bucket-id-regexes= . + + --include-bucket-id-regexes=[INCLUDE_BUCKET_ID_REGEXES,...] + Sets filter for bucket id regexes to include. Accepts list of + bucket id regexes in comma separated format. If the regex contains + special characters that may have a specific meaning in the shell, + escape them using backslashes(\). To clear bucket id regexes list, + provide flag with empty list. e.g --include-bucket-id-regexes="" or + --include-bucket-id-regexes= . + + At most one of these can be specified: + + --exclude-locations=[EXCLUDE_LOCATIONS,...] + Comma separated list of locations + (https://cloud.google.com/storage/docs/locations#available-locations) + to exclude in storage intelligence filter. To clear excluded + locations, provide flag with empty list. e.g --exclude-locations="" + or --exclude-locations= . + + --include-locations=[INCLUDE_LOCATIONS,...] + Comma separated list of locations + (https://cloud.google.com/storage/docs/locations#available-locations) + to include in storage intelligence filter. To clear included + locations, provide flag with empty list. e.g --include-locations="" + or --include-locations= . + +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/artifacts/attachments/describe b/gcloud/artifacts/attachments/describe new file mode 100644 index 000000000..5bf89764e --- /dev/null +++ b/gcloud/artifacts/attachments/describe @@ -0,0 +1,80 @@ +NAME + gcloud artifacts attachments describe - describe an Artifact Registry + attachment + +SYNOPSIS + gcloud artifacts attachments describe + (ATTACHMENT : --location=LOCATION --repository=REPOSITORY) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Describe an Artifact Registry attachment. + + This command can fail for the following reasons: + ▪ The specified attachment does not exist. + ▪ The active account does not have permission to view attachments. + +EXAMPLES + To describe an attachment named my-attachment under the current project, + repository, and location, run: + + $ gcloud artifacts attachments describe my-attachment + +POSITIONAL ARGUMENTS + Attachment resource - The Artifact Registry attachment to describe. The + arguments in this group can be used to specify the attributes of this + resource. (NOTE) Some attributes are not given arguments in this group but + can be set in other ways. + + To set the project attribute: + ◆ provide the argument attachment 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. + + ATTACHMENT + ID of the attachment or fully qualified identifier for the + attachment. + + To set the attachment attribute: + ▸ provide the argument attachment 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 attachment. Overrides the default artifacts/location + property value for this command invocation. To configure the default + location, use the command: gcloud config set artifacts/location. + + To set the location attribute: + ▸ provide the argument attachment on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ set the property artifacts/location. + + --repository=REPOSITORY + The repository associated with the attachment. Overrides the default + artifacts/repository property value for this command invocation. To + configure the default repository, use the command: gcloud config set + artifacts/repository. + + To set the repository attribute: + ▸ provide the argument attachment on the command line with a fully + specified name; + ▸ provide the argument --repository on the command line; + ▸ set the property artifacts/repository. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the artifactregistry/v1 API. The full documentation for + this API can be found at: https://cloud.google.com/artifacts/docs/ diff --git a/gcloud/artifacts/attachments/help b/gcloud/artifacts/attachments/help index 66d4b55b2..537f6ef08 100644 --- a/gcloud/artifacts/attachments/help +++ b/gcloud/artifacts/attachments/help @@ -29,6 +29,9 @@ COMMANDS delete Delete an Artifact Registry attachment. + describe + Describe an Artifact Registry attachment. + download Download an Artifact registry attachment from a repository. diff --git a/gcloud/beta/ai/endpoints/deploy-model b/gcloud/beta/ai/endpoints/deploy-model index 8500a7eba..5d9095ef6 100644 --- a/gcloud/beta/ai/endpoints/deploy-model +++ b/gcloud/beta/ai/endpoints/deploy-model @@ -77,9 +77,10 @@ OPTIONAL FLAGS type The type of the accelerator. Choices are 'nvidia-a100-80gb', - 'nvidia-h100-80gb', 'nvidia-h100-mega-80gb', 'nvidia-l4', - 'nvidia-tesla-a100', 'nvidia-tesla-k80', 'nvidia-tesla-p100', - 'nvidia-tesla-p4', 'nvidia-tesla-t4', 'nvidia-tesla-v100'. + 'nvidia-h100-80gb', 'nvidia-h100-mega-80gb', 'nvidia-h200-141gb', + 'nvidia-l4', 'nvidia-tesla-a100', 'nvidia-tesla-k80', + 'nvidia-tesla-p100', 'nvidia-tesla-p4', 'nvidia-tesla-t4', + 'nvidia-tesla-v100'. count The number of accelerators to attach to each machine running the diff --git a/gcloud/beta/ai/endpoints/list b/gcloud/beta/ai/endpoints/list index 44af8cfa2..f707f4762 100644 --- a/gcloud/beta/ai/endpoints/list +++ b/gcloud/beta/ai/endpoints/list @@ -2,8 +2,9 @@ NAME gcloud beta ai endpoints list - list existing Vertex AI endpoints SYNOPSIS - gcloud beta ai endpoints list [--region=REGION] [--filter=EXPRESSION] - [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + gcloud beta ai endpoints list [--list-model-garden-endpoints-only] + [--region=REGION] [--filter=EXPRESSION] [--limit=LIMIT] + [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] EXAMPLES @@ -12,7 +13,16 @@ EXAMPLES $ gcloud beta ai endpoints list --project=example \ --region=us-central1 + To list the endpoints under project example in region us-central1 that are + created from Model Garden, run: + + $ gcloud beta ai endpoints list --project=example \ + --region=us-central1 --list-model-garden-endpoints-only + FLAGS + --list-model-garden-endpoints-only + Whether to only list endpoints created from Model Garden. + Region resource - Cloud region to list endpoints. This represents a Cloud resource. (NOTE) Some attributes are not given arguments in this group but can be set in other ways. diff --git a/gcloud/beta/ai/help b/gcloud/beta/ai/help index 2af005b14..6988d6307 100644 --- a/gcloud/beta/ai/help +++ b/gcloud/beta/ai/help @@ -30,6 +30,9 @@ GROUPS indexes (BETA) Manage Vertex AI indexes. + model-garden + (BETA) Interact with and manage resources in Vertex Model Garden. + model-monitoring-jobs (BETA) Manage Vertex AI model monitoring jobs. diff --git a/gcloud/beta/ai/model-garden/help b/gcloud/beta/ai/model-garden/help new file mode 100644 index 000000000..c815c5603 --- /dev/null +++ b/gcloud/beta/ai/model-garden/help @@ -0,0 +1,27 @@ +NAME + gcloud beta ai model-garden - interact with and manage resources in Vertex + Model Garden + +SYNOPSIS + gcloud beta ai model-garden GROUP [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Interact with and manage resources in Vertex Model Garden. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +GROUPS + GROUP is one of the following: + + models + (BETA) List and use Model Garden models. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha ai model-garden + diff --git a/gcloud/beta/ai/model-garden/models/deploy b/gcloud/beta/ai/model-garden/models/deploy new file mode 100644 index 000000000..a6657f7aa --- /dev/null +++ b/gcloud/beta/ai/model-garden/models/deploy @@ -0,0 +1,197 @@ +NAME + gcloud beta ai model-garden models deploy - deploy a model in Model Garden + to a Vertex AI endpoint + +SYNOPSIS + gcloud beta ai model-garden models deploy --model=MODEL + [--accelerator-type=ACCELERATOR_TYPE] [--accept-eula] [--asynchronous] + [--container-args=[ARG,...]] [--container-command=[COMMAND,...]] + [--container-deployment-timeout-seconds=CONTAINER_DEPLOYMENT_TIMEOUT_SECONDS] + [--container-env-vars=[KEY=VALUE,...]] + [--container-grpc-ports=[PORT,...]] + [--container-health-probe-exec=[HEALTH_PROBE_EXEC,...]] + [--container-health-probe-period-seconds=CONTAINER_HEALTH_PROBE_PERIOD_SECONDS] + [--container-health-probe-timeout-seconds=CONTAINER_HEALTH_PROBE_TIMEOUT_SECONDS] + [--container-health-route=CONTAINER_HEALTH_ROUTE] + [--container-image-uri=CONTAINER_IMAGE_URI] + [--container-ports=[PORT,...]] + [--container-predict-route=CONTAINER_PREDICT_ROUTE] + [--container-shared-memory-size-mb=CONTAINER_SHARED_MEMORY_SIZE_MB] + [--container-startup-probe-exec=[STARTUP_PROBE_EXEC,...]] + [--container-startup-probe-period-seconds=CONTAINER_STARTUP_PROBE_PERIOD_SECONDS] + [--container-startup-probe-timeout-seconds=CONTAINER_STARTUP_PROBE_TIMEOUT_SECONDS] + [--enable-fast-tryout] [--endpoint-display-name=ENDPOINT_DISPLAY_NAME] + [--hugging-face-access-token=HUGGING_FACE_ACCESS_TOKEN] + [--machine-type=MACHINE_TYPE] [--region=REGION] + [--reservation-affinity=[key=KEY], + [reservation-affinity-type=RESERVATION-AFFINITY-TYPE], + [values=VALUES]] [--spot] [--use-dedicated-endpoint] + [GCLOUD_WIDE_FLAG ...] + +EXAMPLES + To deploy a Model Garden model google/gemma2/gemma2-9b under project + example in region us-central1, run: + + $ gcloud ai model-garden models deploy \ + --model=google/gemma2@gemma-2-9b --project=example \ + --region=us-central1 + + To deploy a Hugging Face model meta-llama/Meta-Llama-3-8B under project + example in region us-central1, run: + + $ gcloud ai model-garden models deploy \ + --model=meta-llama/Meta-Llama-3-8B \ + --hugging-face-access-token={hf_token} --project=example \ + --region=us-central1 + +REQUIRED FLAGS + --model=MODEL + The model to be deployed. If it is a Model Garden model, it should be + in the format of {publisher_name}/{model_name}@{model_version_name}, + e.g. google/gemma2@gemma-2-2b. If it is a Hugging Face model, it should + be in the convention of Hugging Face models, e.g. + meta-llama/Meta-Llama-3-8B. + +OPTIONAL FLAGS + --accelerator-type=ACCELERATOR_TYPE + The accelerator type to serve the model. It should be a supported + accelerator type from the verified deployment configurations of the + model. Use gcloud ai model-garden models list-deployment-config to + check the supported accelerator types. + + --accept-eula + When set, the user accepts the End User License Agreement (EULA) of the + model. + + --asynchronous + If set to true, the command will terminate immediately and not keep + polling the operation status. + + --container-args=[ARG,...] + Comma-separated arguments passed to the command run by the container + image. If not specified and no --command is provided, the container + image's default command is used. + + --container-command=[COMMAND,...] + Entrypoint for the container image. If not specified, the container + image's default entrypoint is run. + + --container-deployment-timeout-seconds=CONTAINER_DEPLOYMENT_TIMEOUT_SECONDS + Deployment timeout in seconds. + + --container-env-vars=[KEY=VALUE,...] + List of key-value pairs to set as environment variables. + + --container-grpc-ports=[PORT,...] + Container ports to receive grpc requests at. Must be a number between 1 + and 65535, inclusive. + + --container-health-probe-exec=[HEALTH_PROBE_EXEC,...] + Exec specifies the action to take. Used by health probe. An example of + this argument would be ["cat", "/tmp/healthy"]. + + --container-health-probe-period-seconds=CONTAINER_HEALTH_PROBE_PERIOD_SECONDS + How often (in seconds) to perform the health probe. Default to 10 + seconds. Minimum value is 1. + + --container-health-probe-timeout-seconds=CONTAINER_HEALTH_PROBE_TIMEOUT_SECONDS + Number of seconds after which the health probe times out. Defaults to 1 + second. Minimum value is 1. + + --container-health-route=CONTAINER_HEALTH_ROUTE + HTTP path to send health checks to inside the container. + + --container-image-uri=CONTAINER_IMAGE_URI + URI of the Model serving container file in the Container Registry (e.g. + gcr.io/myproject/server:latest). + + --container-ports=[PORT,...] + Container ports to receive http requests at. Must be a number between 1 + and 65535, inclusive. + + --container-predict-route=CONTAINER_PREDICT_ROUTE + HTTP path to send prediction requests to inside the container. + + --container-shared-memory-size-mb=CONTAINER_SHARED_MEMORY_SIZE_MB + The amount of the VM memory to reserve as the shared memory for the + model in megabytes. + + --container-startup-probe-exec=[STARTUP_PROBE_EXEC,...] + Exec specifies the action to take. Used by startup probe. An example of + this argument would be ["cat", "/tmp/healthy"]. + + --container-startup-probe-period-seconds=CONTAINER_STARTUP_PROBE_PERIOD_SECONDS + How often (in seconds) to perform the startup probe. Default to 10 + seconds. Minimum value is 1. + + --container-startup-probe-timeout-seconds=CONTAINER_STARTUP_PROBE_TIMEOUT_SECONDS + Number of seconds after which the startup probe times out. Defaults to + 1 second. Minimum value is 1. + + --enable-fast-tryout + If True, model will be deployed using faster deployment path. Useful + for quick experiments. Not for production workloads. Only available for + most popular models with certain machine types. + + --endpoint-display-name=ENDPOINT_DISPLAY_NAME + Display name of the endpoint with the deployed model. + + --hugging-face-access-token=HUGGING_FACE_ACCESS_TOKEN + The access token from Hugging Face needed to read the model artifacts + of gated models. It is only needed when the Hugging Face model to + deploy is gated. + + --machine-type=MACHINE_TYPE + The machine type to deploy the model to. It should be a supported + machine type from the deployment configurations of the model. Use + gcloud ai model-garden models list-deployment-config to check the + supported machine types. + + Region resource - Cloud region to deploy the model. This represents a + Cloud resource. (NOTE) Some attributes are not given arguments in this + group but can be set in other ways. + + To set the project attribute: + ◆ provide the argument --region on the command line with a fully + specified name; + ◆ set the property ai/region with a fully specified name; + ◆ choose one from the prompted list of available regions with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + --region=REGION + ID of the region or fully qualified identifier for the region. + + To set the region attribute: + ▸ provide the argument --region on the command line; + ▸ set the property ai/region; + ▸ choose one from the prompted list of available regions. + + --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. + + --spot + If true, schedule the deployment workload on Spot VM. + + --use-dedicated-endpoint + If true, the endpoint will be exposed through a dedicated DNS. Your + request to the dedicated DNS will be isolated from other users' traffic + and will have better performance and reliability. + +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 ai model-garden models deploy + diff --git a/gcloud/beta/ai/model-garden/models/help b/gcloud/beta/ai/model-garden/models/help new file mode 100644 index 000000000..20c232a9d --- /dev/null +++ b/gcloud/beta/ai/model-garden/models/help @@ -0,0 +1,33 @@ +NAME + gcloud beta ai model-garden models - list and use Model Garden models + +SYNOPSIS + gcloud beta ai model-garden models COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) List and use Model Garden models. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + deploy + (BETA) Deploy a model in Model Garden to a Vertex AI endpoint. + + list + (BETA) List the publisher models in Model Garden. + + list-deployment-config + (BETA) List the machine specifications supported by and verified for a + model in Model Garden. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha ai model-garden models + diff --git a/gcloud/beta/ai/model-garden/models/list b/gcloud/beta/ai/model-garden/models/list new file mode 100644 index 000000000..c422ed803 --- /dev/null +++ b/gcloud/beta/ai/model-garden/models/list @@ -0,0 +1,68 @@ +NAME + gcloud beta ai model-garden models list - list the publisher models in + Model Garden + +SYNOPSIS + gcloud beta ai model-garden models list + [--list-supported-hugging-face-models] [--model-filter=MODEL_FILTER] + [--filter=EXPRESSION] [--limit=LIMIT; default=1000] + [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) This command lists either all models in Model Garden or all Hugging + Face models supported by Model Garden. + + Note: Since the number of Hugging Face models is large, the default limit + is set to 500 with a page size of 100 when listing supported Hugging Face + models. To override the limit or page size, specify the --limit or + --page-size flags, respectively. To list all models in Model Garden, use + --limit=unlimited. + +FLAGS + --list-supported-hugging-face-models + Whether to only list supported Hugging Face models. + + --model-filter=MODEL_FILTER + Filter to apply to the model names or the display names of the list of + models. + +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; default=1000 + Maximum number of resources to list. The default is 1000. This flag + interacts with other flags that are applied in this order: --flatten, + --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha ai model-garden models list + diff --git a/gcloud/beta/ai/model-garden/models/list-deployment-config b/gcloud/beta/ai/model-garden/models/list-deployment-config new file mode 100644 index 000000000..a64d54b27 --- /dev/null +++ b/gcloud/beta/ai/model-garden/models/list-deployment-config @@ -0,0 +1,68 @@ +NAME + gcloud beta ai model-garden models list-deployment-config - list the + machine specifications supported by and verified for a model in Model + Garden + +SYNOPSIS + gcloud beta ai model-garden models list-deployment-config --model=MODEL + [--hugging-face-access-token=HUGGING_FACE_ACCESS_TOKEN] + [--filter=EXPRESSION] [--sort-by=[FIELD,...]] [GCLOUD_WIDE_FLAG ...] + +EXAMPLES + To list the supported machine specifications for google/gemma2@gemma-2-9b, + run: + + $ gcloud ai model-garden models list-deployment-config \ + --model=google/gemma2@gemma-2-9b + + To list the supported machine specifications for a Hugging Face model + meta-llama/Meta-Llama-3-8B, run: + + $ gcloud ai model-garden models list-deployment-config \ + --model=meta-llama/Meta-Llama-3-8B + +REQUIRED FLAGS + --model=MODEL + The model to be deployed. If it is a Model Garden model, it should be + in the format of {publisher_name}/{model_name}@{model_version_name}, + e.g. google/gemma2@gemma-2-2b. If it is a Hugging Face model, it should + be in the convention of Hugging Face models, e.g. + meta-llama/Meta-Llama-3-8B. + +FLAGS + --hugging-face-access-token=HUGGING_FACE_ACCESS_TOKEN + The access token from Hugging Face needed to read the model artifacts + of gated models in order to generate the deployment configs. It is only + needed when the Hugging Face model to deploy is gated and not verified + by Model Garden. You can use the gcloud ai alpha/beta model-garden + models list command to find out which ones are verified by Model + Garden. + +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. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha ai model-garden models list-deployment-config + diff --git a/gcloud/beta/alloydb/instances/create b/gcloud/beta/alloydb/instances/create index cc3009e6b..3a4f5c19a 100644 --- a/gcloud/beta/alloydb/instances/create +++ b/gcloud/beta/alloydb/instances/create @@ -14,7 +14,7 @@ SYNOPSIS [--insights-config-query-string-length=INSIGHTS_CONFIG_QUERY_STRING_LENGTH] [--[no-]insights-config-record-application-tags] [--[no-]insights-config-record-client-address] - [--[no-]observability-config-enabled] + [--machine-type=MACHINE_TYPE] [--[no-]observability-config-enabled] [--observability-config-max-query-string-length=OBSERVABILITY_CONFIG_MAX_QUERY_STRING_LENGTH] [--[no-]observability-config-preserve-comments] [--observability-config-query-plans-per-minute=OBSERVABILITY_CONFIG_QUERY_PLANS_PER_MINUTE] @@ -52,9 +52,15 @@ REQUIRED FLAGS --cpu-count=CPU_COUNT Whole number value indicating how many vCPUs the machine should - contain. Each vCPU count corresponds to a N2 high-mem machine: - (https://cloud.google.com/compute/docs/general-purpose-machines#n2_machines). - CPU_COUNT must be one of: 1, 2, 4, 8, 16, 32, 64, 96, 128. + contain. If the instance does not have a machine-type, the vCPU count + will be used to determine the machine type where each vCPU corresponds + to an N2 high-mem machine: + (https://cloud.google.com/compute/docs/general-purpose-machines#n2_machine_types). + where CPU_COUNT can be one of: 2, 4, 8, 16, 32, 64, 96, 128. If the + instance has a machine-type, cpu-count must have the same value as the + vCPU count in the machine-type. Eg: if machine-type is + c4a-highmem-4-lssd, cpu-count must be 4. CPU_COUNT must be one of: 1, + 2, 4, 8, 16, 32, 48, 64, 72, 96, 128. --instance-type=INSTANCE_TYPE Specifies instance type. INSTANCE_TYPE must be one of: @@ -140,6 +146,14 @@ OPTIONAL FLAGS Use --insights-config-record-client-address to enable and --no-insights-config-record-client-address to disable. + --machine-type=MACHINE_TYPE + Specifies machine type for the instance. MACHINE_TYPE must be one of: + n2-highmem-2, n2-highmem-4, n2-highmem-8, n2-highmem-16, n2-highmem-32, + n2-highmem-64, n2-highmem-96, n2-highmem-128, c4a-highmem-1, + c4a-highmem-4-lssd, c4a-highmem-8-lssd, c4a-highmem-16-lssd, + c4a-highmem-32-lssd, c4a-highmem-48-lssd, c4a-highmem-64-lssd, + c4a-highmem-72-lssd. + --[no-]observability-config-enabled Enable enhanced query insights feature. Use --observability-config-enabled to enable and diff --git a/gcloud/beta/alloydb/instances/update b/gcloud/beta/alloydb/instances/update index 2d15f6832..5f9586e0f 100644 --- a/gcloud/beta/alloydb/instances/update +++ b/gcloud/beta/alloydb/instances/update @@ -14,7 +14,7 @@ SYNOPSIS [--insights-config-query-string-length=INSIGHTS_CONFIG_QUERY_STRING_LENGTH] [--[no-]insights-config-record-application-tags] [--[no-]insights-config-record-client-address] - [--[no-]observability-config-enabled] + [--machine-type=MACHINE_TYPE] [--[no-]observability-config-enabled] [--observability-config-max-query-string-length=OBSERVABILITY_CONFIG_MAX_QUERY_STRING_LENGTH] [--[no-]observability-config-preserve-comments] [--observability-config-query-plans-per-minute=OBSERVABILITY_CONFIG_QUERY_PLANS_PER_MINUTE] @@ -94,9 +94,15 @@ OPTIONAL FLAGS --cpu-count=CPU_COUNT Whole number value indicating how many vCPUs the machine should - contain. Each vCPU count corresponds to a N2 high-mem machine: - (https://cloud.google.com/compute/docs/general-purpose-machines#n2_machines). - CPU_COUNT must be one of: 1, 2, 4, 8, 16, 32, 64, 96, 128. + contain. If the instance does not have a machine-type, the vCPU count + will be used to determine the machine type where each vCPU corresponds + to an N2 high-mem machine: + (https://cloud.google.com/compute/docs/general-purpose-machines#n2_machine_types). + where CPU_COUNT can be one of: 2, 4, 8, 16, 32, 64, 96, 128. If the + instance has a machine-type, cpu-count must have the same value as the + vCPU count in the machine-type. Eg: if machine-type is + c4a-highmem-4-lssd, cpu-count must be 4. CPU_COUNT must be one of: 1, + 2, 4, 8, 16, 32, 48, 64, 72, 96, 128. --database-flags=FLAG=VALUE,[FLAG=VALUE,...] Comma-separated list of database flags to set on the instance. Use an @@ -127,6 +133,14 @@ OPTIONAL FLAGS Use --insights-config-record-client-address to enable and --no-insights-config-record-client-address to disable. + --machine-type=MACHINE_TYPE + Specifies machine type for the instance. MACHINE_TYPE must be one of: + n2-highmem-2, n2-highmem-4, n2-highmem-8, n2-highmem-16, n2-highmem-32, + n2-highmem-64, n2-highmem-96, n2-highmem-128, c4a-highmem-1, + c4a-highmem-4-lssd, c4a-highmem-8-lssd, c4a-highmem-16-lssd, + c4a-highmem-32-lssd, c4a-highmem-48-lssd, c4a-highmem-64-lssd, + c4a-highmem-72-lssd. + --[no-]observability-config-enabled Enable enhanced query insights feature. Use --observability-config-enabled to enable and diff --git a/gcloud/beta/certificate-manager/certificates/list b/gcloud/beta/certificate-manager/certificates/list index e5c107cbd..d17e86190 100644 --- a/gcloud/beta/certificate-manager/certificates/list +++ b/gcloud/beta/certificate-manager/certificates/list @@ -22,7 +22,8 @@ FLAGS To set the project attribute: ◆ provide the argument --location on the command line with a fully specified name; - ◆ default value of location is [global] with a fully specified name; + ◆ if left empty, will use the wildcard '-' to list all locations with a + fully specified name; ◆ provide the argument --project on the command line; ◆ set the property core/project. @@ -31,7 +32,7 @@ FLAGS To set the location attribute: ▸ provide the argument --location on the command line; - ▸ default value of location is [global]. + ▸ if left empty, will use the wildcard '-' to list all locations. LIST COMMAND FLAGS --filter=EXPRESSION diff --git a/gcloud/beta/certificate-manager/dns-authorizations/list b/gcloud/beta/certificate-manager/dns-authorizations/list index 1c8cf5c48..db6908af8 100644 --- a/gcloud/beta/certificate-manager/dns-authorizations/list +++ b/gcloud/beta/certificate-manager/dns-authorizations/list @@ -17,14 +17,15 @@ EXAMPLES $ gcloud beta certificate-manager dns-authorizations list FLAGS - Location resource - The location (defaults to global) of the resources. - This represents a Cloud resource. (NOTE) Some attributes are not given + Location resource - The location (defaults to '-') of the resources. This + represents a Cloud resource. (NOTE) Some attributes are not given arguments in this group but can be set in other ways. To set the project attribute: ◆ provide the argument --location on the command line with a fully specified name; - ◆ default value of location is [global] with a fully specified name; + ◆ if left empty, will use the wildcard '-' to list all locations with a + fully specified name; ◆ provide the argument --project on the command line; ◆ set the property core/project. @@ -33,7 +34,7 @@ FLAGS To set the location attribute: ▸ provide the argument --location on the command line; - ▸ default value of location is [global]. + ▸ if left empty, will use the wildcard '-' to list all locations. LIST COMMAND FLAGS --filter=EXPRESSION diff --git a/gcloud/beta/certificate-manager/issuance-configs/list b/gcloud/beta/certificate-manager/issuance-configs/list index 2875488fb..247fd230e 100644 --- a/gcloud/beta/certificate-manager/issuance-configs/list +++ b/gcloud/beta/certificate-manager/issuance-configs/list @@ -16,14 +16,15 @@ EXAMPLES $ gcloud beta certificate-manager issuance-configs list FLAGS - Location resource - Location (defaults to global) of the resources. This + Location resource - The location (defaults to '-') of the resources. This represents a Cloud resource. (NOTE) Some attributes are not given arguments in this group but can be set in other ways. To set the project attribute: ◆ provide the argument --location on the command line with a fully specified name; - ◆ default value of location is [global] with a fully specified name; + ◆ if left empty, will use the wildcard '-' to list all locations with a + fully specified name; ◆ provide the argument --project on the command line; ◆ set the property core/project. @@ -32,7 +33,7 @@ FLAGS To set the location attribute: ▸ provide the argument --location on the command line; - ▸ default value of location is [global]. + ▸ if left empty, will use the wildcard '-' to list all locations. LIST COMMAND FLAGS --filter=EXPRESSION diff --git a/gcloud/beta/certificate-manager/trust-configs/list b/gcloud/beta/certificate-manager/trust-configs/list index e15fdafc0..c76f88d50 100644 --- a/gcloud/beta/certificate-manager/trust-configs/list +++ b/gcloud/beta/certificate-manager/trust-configs/list @@ -16,14 +16,15 @@ EXAMPLES $ gcloud beta certificate-manager trust-configs list FLAGS - Location resource - The location (defaults to global) of the resources. - This represents a Cloud resource. (NOTE) Some attributes are not given + Location resource - The location (defaults to '-') of the resources. This + represents a Cloud resource. (NOTE) Some attributes are not given arguments in this group but can be set in other ways. To set the project attribute: ◆ provide the argument --location on the command line with a fully specified name; - ◆ default value of location is [global] with a fully specified name; + ◆ if left empty, will use the wildcard '-' to list all locations with a + fully specified name; ◆ provide the argument --project on the command line; ◆ set the property core/project. @@ -32,7 +33,7 @@ FLAGS To set the location attribute: ▸ provide the argument --location on the command line; - ▸ default value of location is [global]. + ▸ if left empty, will use the wildcard '-' to list all locations. LIST COMMAND FLAGS --filter=EXPRESSION diff --git a/gcloud/beta/compute/backend-services/create b/gcloud/beta/compute/backend-services/create index 3e63bebec..2a5736251 100644 --- a/gcloud/beta/compute/backend-services/create +++ b/gcloud/beta/compute/backend-services/create @@ -27,6 +27,7 @@ SYNOPSIS oauth2-client-secret=OAUTH2-CLIENT-SECRET]] [--idle-timeout-sec=IDLE_TIMEOUT_SEC] [--ip-address-selection-policy=IP_ADDRESS_SELECTION_POLICY] + [--ip-port-dynamic-forwarding] [--load-balancing-scheme=LOAD_BALANCING_SCHEME; default="EXTERNAL"] [--locality-lb-policy=LOCALITY_LB_POLICY] [--logging-optional=LOGGING_OPTIONAL] @@ -377,6 +378,9 @@ FLAGS IP_ADDRESS_SELECTION_POLICY must be one of: IPV4_ONLY, PREFER_IPV6, IPV6_ONLY. + --ip-port-dynamic-forwarding + Enables Dynamic Forwarding in IpPort selection mode. + --load-balancing-scheme=LOAD_BALANCING_SCHEME; default="EXTERNAL" Specifies the load balancer type. Choose EXTERNAL for the classic Application Load Balancers, the external passthrough Network Load diff --git a/gcloud/beta/compute/backend-services/update b/gcloud/beta/compute/backend-services/update index 709c43b3b..2fede626d 100644 --- a/gcloud/beta/compute/backend-services/update +++ b/gcloud/beta/compute/backend-services/update @@ -24,6 +24,7 @@ SYNOPSIS oauth2-client-secret=OAUTH2-CLIENT-SECRET]] [--idle-timeout-sec=IDLE_TIMEOUT_SEC] [--ip-address-selection-policy=IP_ADDRESS_SELECTION_POLICY] + [--ip-port-dynamic-forwarding] [--load-balancing-scheme=LOAD_BALANCING_SCHEME] [--locality-lb-policy=LOCALITY_LB_POLICY] [--logging-optional=LOGGING_OPTIONAL] @@ -306,6 +307,9 @@ FLAGS IP_ADDRESS_SELECTION_POLICY must be one of: IPV4_ONLY, PREFER_IPV6, IPV6_ONLY. + --ip-port-dynamic-forwarding + Enables Dynamic Forwarding in IpPort selection mode. + --load-balancing-scheme=LOAD_BALANCING_SCHEME Only for the Global external ALB migration. diff --git a/gcloud/beta/compute/disks/convert b/gcloud/beta/compute/disks/convert index c58d670e6..13e9e094a 100644 --- a/gcloud/beta/compute/disks/convert +++ b/gcloud/beta/compute/disks/convert @@ -17,11 +17,11 @@ DESCRIPTION https://cloud.google.com/sdk/gcloud/reference/compute/disks/convert. EXAMPLES - The following command converts a PD Standard disk to a Hyperdisk - Throughput: + The following command converts a Persistent Disk volume to a Hyperdisk + Balanced volume: $ gcloud beta compute disks convert my-disk-1 --zone=ZONE \ - --target-disk-type=hyperdisk-throughput + --target-disk-type=hyperdisk-balanced POSITIONAL ARGUMENTS DISK_NAME diff --git a/gcloud/beta/compute/future-reservations/create b/gcloud/beta/compute/future-reservations/create index 7f25f5433..b144c4aa6 100644 --- a/gcloud/beta/compute/future-reservations/create +++ b/gcloud/beta/compute/future-reservations/create @@ -109,7 +109,8 @@ REQUIRED FLAGS size The size of the local SSD in base-2 GB. count - The number of local SSD to use per VM. Default value is 1. + The number of local SSD to use per VM. If you don't specify + this argument, then the default value is 1. --min-cpu-platform=MIN_CPU_PLATFORM Optional minimum CPU platform of the reservation to create. diff --git a/gcloud/beta/compute/future-reservations/update b/gcloud/beta/compute/future-reservations/update index 075d0181c..9db04c2be 100644 --- a/gcloud/beta/compute/future-reservations/update +++ b/gcloud/beta/compute/future-reservations/update @@ -245,7 +245,8 @@ FLAGS size The size of the local SSD in base-2 GB. count - The number of local SSD to use per VM. Default value is 1. + The number of local SSD to use per VM. If you don't specify + this argument, then the default value is 1. Manage the time specific properties for requesting future capacity diff --git a/gcloud/beta/compute/instances/help b/gcloud/beta/compute/instances/help index 53589daaf..131a2c94e 100644 --- a/gcloud/beta/compute/instances/help +++ b/gcloud/beta/compute/instances/help @@ -140,6 +140,9 @@ COMMANDS remove-tags (BETA) Remove tags from Compute Engine virtual machine instances. + report-host-as-faulty + (BETA) Report a host as faulty to start the repair process. + reset (BETA) Reset a virtual machine instance. diff --git a/gcloud/beta/compute/instances/report-host-as-faulty b/gcloud/beta/compute/instances/report-host-as-faulty new file mode 100644 index 000000000..d8078038d --- /dev/null +++ b/gcloud/beta/compute/instances/report-host-as-faulty @@ -0,0 +1,81 @@ +NAME + gcloud beta compute instances report-host-as-faulty - report a host as + faulty to start the repair process + +SYNOPSIS + gcloud beta compute instances report-host-as-faulty INSTANCE_NAME + --disruption-schedule=DISRUPTION_SCHEDULE + --fault-reasons=[behavior=BEHAVIOR],[description=DESCRIPTION] + [--zone=ZONE] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) gcloud beta compute instances report-host-as-faulty is used to + report a host as faulty to start the repair process. + +EXAMPLES + To report a host as faulty for an instance named test-instance, run: + + $ gcloud beta compute instances report-host-as-faulty \ + test-instance \ + --fault-reasons=behavior=SILENT_DATA_CORRUPTION,\ + description="affecting our ML job" --disruption-schedule=IMMEDIATE + +POSITIONAL ARGUMENTS + INSTANCE_NAME + Name of the instance to operate on. For details on valid instance + names, refer to the criteria documented under the field 'name' at: + https://cloud.google.com/compute/docs/reference/rest/v1/instances + +REQUIRED FLAGS + --disruption-schedule=DISRUPTION_SCHEDULE + Specifies the timing for initiating the fault reporting process. The + default value is ['IMMEDIATE'] which initiates the process right away. + DISRUPTION_SCHEDULE must be (only one value is supported): IMMEDIATE. + + --fault-reasons=[behavior=BEHAVIOR],[description=DESCRIPTION] + Specified and can include one or more of the following types: + ['BEHAVIOR_UNSPECIFIED', 'PERFORMANCE', 'SILENT_DATA_CORRUPTION', + 'UNRECOVERABLE_GPU_ERROR']. This helps categorize the nature of the + fault being reported. + +OPTIONAL FLAGS + --zone=ZONE + Zone of the instance to operate on. If not specified, you might be + prompted to select a zone (interactive mode only). gcloud attempts to + identify the appropriate zone by searching for resources in your + currently active project. If the zone cannot be determined, gcloud + prompts you for a selection with all available Google Cloud Platform + zones. + + To avoid prompting when this flag is omitted, the user can set the + compute/zone property: + + $ gcloud config set compute/zone ZONE + + A list of zones can be fetched by running: + + $ gcloud compute zones list + + To unset the property, run: + + $ gcloud config unset compute/zone + + Alternatively, the zone can be stored in the environment variable + CLOUDSDK_COMPUTE_ZONE. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud compute instances report-host-as-faulty + + $ gcloud alpha compute instances report-host-as-faulty + diff --git a/gcloud/beta/compute/networks/subnets/create b/gcloud/beta/compute/networks/subnets/create index 7a456b495..c048909cc 100644 --- a/gcloud/beta/compute/networks/subnets/create +++ b/gcloud/beta/compute/networks/subnets/create @@ -5,7 +5,7 @@ NAME SYNOPSIS gcloud beta compute networks subnets create NAME --network=NETWORK [--description=DESCRIPTION] [--enable-flow-logs] - [--enable-private-ip-google-access] + [--enable-private-ip-google-access] [--ip-collection=IP_COLLECTION] [--ipv6-access-type=IPV6_ACCESS_TYPE] [--logging-aggregation-interval=LOGGING_AGGREGATION_INTERVAL] [--logging-filter-expr=LOGGING_FILTER_EXPR] @@ -51,6 +51,11 @@ OPTIONAL FLAGS Enable/disable access to Google Cloud APIs from this subnet for instances without a public ip address. + --ip-collection=IP_COLLECTION + Resource reference to a public delegated prefix. The + PublicDelegatedPrefix must be a sub-prefix in + EXTERNAL_IPV6_SUBNETWORK_CREATION mode. + --ipv6-access-type=IPV6_ACCESS_TYPE IPv6 access type can be specified only when the subnet is created, or when the subnet is first updated to have a stack type of IPV4_IPV6. diff --git a/gcloud/beta/compute/networks/subnets/update b/gcloud/beta/compute/networks/subnets/update index 6d644ca3f..f5ea71e7b 100644 --- a/gcloud/beta/compute/networks/subnets/update +++ b/gcloud/beta/compute/networks/subnets/update @@ -6,7 +6,7 @@ SYNOPSIS gcloud beta compute networks subnets update NAME [--add-secondary-ranges-with-reserved-internal-range=RANGE_NAME=INTERNAL_RANGE_URL, [...]] [--drain-timeout=DRAIN_TIMEOUT; default="0s"] - [--ipv6-access-type=IPV6_ACCESS_TYPE] + [--ip-collection=IP_COLLECTION] [--ipv6-access-type=IPV6_ACCESS_TYPE] [--logging-aggregation-interval=LOGGING_AGGREGATION_INTERVAL] [--logging-filter-expr=LOGGING_FILTER_EXPR] [--logging-flow-sampling=LOGGING_FLOW_SAMPLING] @@ -57,6 +57,11 @@ FLAGS availability of proxies for load balancing. The drain timeout is only applicable when the [--role=ACTIVE] flag is being used. + --ip-collection=IP_COLLECTION + Resource reference to a public delegated prefix. The + PublicDelegatedPrefix must be a sub-prefix in + EXTERNAL_IPV6_SUBNETWORK_CREATION mode. + --ipv6-access-type=IPV6_ACCESS_TYPE IPv6 access type can be specified only when the subnet is created, or when the subnet is first updated to have a stack type of IPV4_IPV6. diff --git a/gcloud/beta/compute/public-delegated-prefixes/create b/gcloud/beta/compute/public-delegated-prefixes/create index 48363532e..4bd137a7b 100644 --- a/gcloud/beta/compute/public-delegated-prefixes/create +++ b/gcloud/beta/compute/public-delegated-prefixes/create @@ -48,7 +48,8 @@ OPTIONAL FLAGS --mode=MODE Specifies the mode of this IPv6 PDP. MODE must be one of: delegation, - external-ipv6-forwarding-rule-creation. + external-ipv6-forwarding-rule-creation, + external-ipv6-subnetwork-creation. At most one of these can be specified: diff --git a/gcloud/beta/compute/public-delegated-prefixes/delegated-sub-prefixes/create b/gcloud/beta/compute/public-delegated-prefixes/delegated-sub-prefixes/create index 079c01e91..aea2a4ebc 100644 --- a/gcloud/beta/compute/public-delegated-prefixes/delegated-sub-prefixes/create +++ b/gcloud/beta/compute/public-delegated-prefixes/delegated-sub-prefixes/create @@ -57,7 +57,8 @@ OPTIONAL FLAGS --mode=MODE Specifies the mode of this IPv6 PDP. MODE must be one of: delegation, - external-ipv6-forwarding-rule-creation. + external-ipv6-forwarding-rule-creation, + external-ipv6-subnetwork-creation. --range=RANGE IPv4 range from this public delegated prefix that should be delegated, diff --git a/gcloud/beta/compute/reservations/create b/gcloud/beta/compute/reservations/create index 91f8cf16f..8b9629857 100644 --- a/gcloud/beta/compute/reservations/create +++ b/gcloud/beta/compute/reservations/create @@ -8,7 +8,7 @@ SYNOPSIS (--source-instance-template=SOURCE_INSTANCE_TEMPLATE | [--machine-type=MACHINE_TYPE : --accelerator=[count=COUNT],[type=TYPE] - --local-ssd=[interface=INTERFACE],[size=SIZE] + --local-ssd=[count=COUNT],[interface=INTERFACE],[size=SIZE] --min-cpu-platform=MIN_CPU_PLATFORM]) : --require-specific-reservation --resource-policies=[KEY=VALUE,...]) [--description=DESCRIPTION] @@ -100,7 +100,7 @@ REQUIRED FLAGS reservation. Use gcloud compute accelerator-types list to learn about all available accelerator types. - --local-ssd=[interface=INTERFACE],[size=SIZE] + --local-ssd=[count=COUNT],[interface=INTERFACE],[size=SIZE] Manage the size and the interface of local SSD to use. See https://cloud.google.com/compute/docs/disks/local-ssd for more information. @@ -111,6 +111,9 @@ REQUIRED FLAGS higher performance. size The size of the local SSD in base-2 GB. + count + The number of local SSD to use per VM. If you don't specify + this argument, then the default value is 1. --min-cpu-platform=MIN_CPU_PLATFORM Optional minimum CPU platform of the reservation to create. diff --git a/gcloud/beta/compute/resource-policies/create/group-placement b/gcloud/beta/compute/resource-policies/create/group-placement index cb34af36b..02627c9c5 100644 --- a/gcloud/beta/compute/resource-policies/create/group-placement +++ b/gcloud/beta/compute/resource-policies/create/group-placement @@ -6,8 +6,8 @@ SYNOPSIS gcloud beta compute resource-policies create group-placement NAME [--availability-domain-count=AVAILABILITY_DOMAIN_COUNT] [--collocation=COLLOCATION] [--description=DESCRIPTION] - [--max-distance=MAX_DISTANCE] [--region=REGION] [--vm-count=VM_COUNT] - [GCLOUD_WIDE_FLAG ...] + [--gpu-topology=GPU_TOPOLOGY] [--max-distance=MAX_DISTANCE] + [--region=REGION] [--vm-count=VM_COUNT] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) Create a Compute Engine Group Placement Resource Policy. @@ -39,6 +39,10 @@ FLAGS --description=DESCRIPTION An optional, textual description for the backend. + --gpu-topology=GPU_TOPOLOGY + Specifies the shape of the GPU slice, in slice based GPU families eg. + A4X. + --max-distance=MAX_DISTANCE Specifies the number of max logical switches between VMs. diff --git a/gcloud/beta/container/clusters/create b/gcloud/beta/container/clusters/create index 5f4753f64..e721742d0 100644 --- a/gcloud/beta/container/clusters/create +++ b/gcloud/beta/container/clusters/create @@ -22,6 +22,7 @@ SYNOPSIS [--cluster-version=CLUSTER_VERSION] [--containerd-config-from-file=PATH_TO_FILE] [--create-subnetwork=[KEY=VALUE,...]] + [--data-cache-count=DATA_CACHE_COUNT] [--database-encryption-key=DATABASE_ENCRYPTION_KEY] [--default-max-pods-per-node=DEFAULT_MAX_PODS_PER_NODE] [--disable-default-snat] [--disable-l4-lb-firewall-reconciliation] @@ -400,6 +401,10 @@ FLAGS Cannot be specified unless '--enable-ip-alias' option is also specified. Cannot be used in conjunction with '--subnetwork' option. + --data-cache-count=DATA_CACHE_COUNT + Specifies the number of local SSDs to be utilized for GKE Data Cache in + the cluster. + --database-encryption-key=DATABASE_ENCRYPTION_KEY Enable Database Encryption. @@ -1299,6 +1304,11 @@ FLAGS kubeletConfig: cpuManagerPolicy: static + memoryManager: + policy: Static + topologyManager: + policy: BestEffort + scope: pod linuxConfig: sysctl: net.core.somaxconn: '2048' @@ -1315,6 +1325,9 @@ FLAGS cpuCFSQuota true or false (enabled by default) cpuCFSQuotaPeriod interval (e.g., '100ms') + memoryManager specify memory manager policy + topologyManager specify topology manager policy + and scope podPidsLimit integer (The value must be greater than or equal to 1024 and less than 4194304.) @@ -1341,6 +1354,17 @@ FLAGS 'fs.mqueue.*', and 'net.*', and sysctls under the groups.) + KEY VALUE + policy either 'Static' or 'None' + + KEY VALUE + policy either 'none' or + 'best-effort' or + 'single-numa-node' or + 'restricted' + scope either 'pod' or + 'container' + List of supported sysctls in 'linuxConfig'. KEY VALUE @@ -1364,7 +1388,7 @@ FLAGS integer tuple net.ipv4.tcp_wmem Any positive integer tuple - net.ipv4.tcp_tw_reuse Must be {0, 1} + net.ipv4.tcp_tw_reuse Must be {0, 1, 2} net.netfilter.nf_conntrack_max Must be between [65536, 4194304] net.netfilter.nf_conntrack_buckets Must be between diff --git a/gcloud/beta/container/node-pools/create b/gcloud/beta/container/node-pools/create index 107022fca..de705ee70 100644 --- a/gcloud/beta/container/node-pools/create +++ b/gcloud/beta/container/node-pools/create @@ -16,6 +16,7 @@ SYNOPSIS [max-pods-per-node=NUM_PODS],...]] [--async] [--boot-disk-kms-key=BOOT_DISK_KMS_KEY] [--cluster=CLUSTER] [--containerd-config-from-file=PATH_TO_FILE] + [--data-cache-count=DATA_CACHE_COUNT] [--disable-pod-cidr-overprovision] [--disk-size=DISK_SIZE] [--disk-type=DISK_TYPE] [--enable-autoprovisioning] [--enable-autorepair] [--no-enable-autoupgrade] @@ -201,6 +202,10 @@ FLAGS Use a full or relative path to a local file containing the value of containerd_config. + --data-cache-count=DATA_CACHE_COUNT + Specifies the number of local SSDs to be utilized for GKE Data Cache in + the node pool. + --disable-pod-cidr-overprovision Disables pod cidr overprovision on nodes. Pod cidr overprovisioning is enabled by default. @@ -690,6 +695,11 @@ FLAGS kubeletConfig: cpuManagerPolicy: static + memoryManager: + policy: Static + topologyManager: + policy: BestEffort + scope: pod linuxConfig: sysctl: net.core.somaxconn: '2048' @@ -706,6 +716,9 @@ FLAGS cpuCFSQuota true or false (enabled by default) cpuCFSQuotaPeriod interval (e.g., '100ms') + memoryManager specify memory manager policy + topologyManager specify topology manager policy + and scope podPidsLimit integer (The value must be greater than or equal to 1024 and less than 4194304.) @@ -732,6 +745,17 @@ FLAGS 'fs.mqueue.*', and 'net.*', and sysctls under the groups.) + KEY VALUE + policy either 'Static' or 'None' + + KEY VALUE + policy either 'none' or + 'best-effort' or + 'single-numa-node' or + 'restricted' + scope either 'pod' or + 'container' + List of supported sysctls in 'linuxConfig'. KEY VALUE @@ -755,7 +779,7 @@ FLAGS integer tuple net.ipv4.tcp_wmem Any positive integer tuple - net.ipv4.tcp_tw_reuse Must be {0, 1} + net.ipv4.tcp_tw_reuse Must be {0, 1, 2} net.netfilter.nf_conntrack_max Must be between [65536, 4194304] net.netfilter.nf_conntrack_buckets Must be between diff --git a/gcloud/beta/container/node-pools/update b/gcloud/beta/container/node-pools/update index 202573cf2..7cbad98de 100644 --- a/gcloud/beta/container/node-pools/update +++ b/gcloud/beta/container/node-pools/update @@ -275,6 +275,11 @@ REQUIRED FLAGS kubeletConfig: cpuManagerPolicy: static + memoryManager: + policy: Static + topologyManager: + policy: BestEffort + scope: pod linuxConfig: sysctl: net.core.somaxconn: '2048' @@ -291,6 +296,9 @@ REQUIRED FLAGS cpuCFSQuota true or false (enabled by default) cpuCFSQuotaPeriod interval (e.g., '100ms') + memoryManager specify memory manager policy + topologyManager specify topology manager policy + and scope podPidsLimit integer (The value must be greater than or equal to 1024 and less than 4194304.) @@ -320,6 +328,18 @@ REQUIRED FLAGS 'fs.mqueue.*', and 'net.*', and sysctls under the groups.) + KEY VALUE + policy either 'Static' or + 'None' + + KEY VALUE + policy either 'none' or + 'best-effort' or + 'single-numa-node' or + 'restricted' + scope either 'pod' or + 'container' + List of supported sysctls in 'linuxConfig'. KEY VALUE @@ -348,7 +368,8 @@ REQUIRED FLAGS integer tuple net.ipv4.tcp_wmem Any positive integer tuple - net.ipv4.tcp_tw_reuse Must be {0, 1} + net.ipv4.tcp_tw_reuse Must be {0, 1, + 2} net.netfilter.nf_conntrack_max Must be between [65536, 4194304] net.netfilter.nf_conntrack_buckets Must be between diff --git a/gcloud/beta/dataproc/clusters/create b/gcloud/beta/dataproc/clusters/create index ff0c54a9c..b161ecaad 100644 --- a/gcloud/beta/dataproc/clusters/create +++ b/gcloud/beta/dataproc/clusters/create @@ -4,6 +4,7 @@ NAME SYNOPSIS gcloud beta dataproc clusters create (CLUSTER : --region=REGION) [--async] [--autoscaling-policy=AUTOSCALING_POLICY] [--bucket=BUCKET] + [--cluster-type=TYPE] [--driver-pool-accelerator=[type=TYPE,[count=COUNT],...]] [--driver-pool-boot-disk-size=DRIVER_POOL_BOOT_DISK_SIZE] [--driver-pool-boot-disk-type=DRIVER_POOL_BOOT_DISK_TYPE] @@ -22,7 +23,7 @@ SYNOPSIS [--master-boot-disk-type=MASTER_BOOT_DISK_TYPE] [--master-local-ssd-interface=MASTER_LOCAL_SSD_INTERFACE] [--master-machine-type=MASTER_MACHINE_TYPE] - [--master-min-cpu-platform=PLATFORM] [--max-idle=MAX_IDLE] + [--master-min-cpu-platform=PLATFORM] [--min-secondary-worker-fraction=MIN_SECONDARY_WORKER_FRACTION] [--node-group=NODE_GROUP] [--num-driver-pool-local-ssds=NUM_DRIVER_POOL_LOCAL_SSDS] @@ -42,7 +43,8 @@ SYNOPSIS [--secondary-worker-standard-capacity-base=SECONDARY_WORKER_STANDARD_CAPACITY_BASE] [--secondary-worker-standard-capacity-percent-above-base=SECONDARY_WORKER_STANDARD_CAPACITY_PERCENT_ABOVE_BASE] [--shielded-integrity-monitoring] [--shielded-secure-boot] - [--shielded-vtpm] [--temp-bucket=TEMP_BUCKET] + [--shielded-vtpm] [--stop-max-idle=STOP_MAX_IDLE] + [--temp-bucket=TEMP_BUCKET] [--worker-accelerator=[type=TYPE,[count=COUNT],...]] [--worker-boot-disk-provisioned-iops=WORKER_BOOT_DISK_PROVISIONED_IOPS] [--worker-boot-disk-provisioned-throughput=WORKER_BOOT_DISK_PROVISIONED_THROUGHPUT] @@ -52,7 +54,10 @@ SYNOPSIS [--worker-min-cpu-platform=PLATFORM] [--zone=ZONE, -z ZONE] [--dataproc-metastore=DATAPROC_METASTORE | --bigquery-metastore --bigquery-metastore-database-location=BIGQUERY_METASTORE_DATABASE_LOCATION --bigquery-metastore-project-id=BIGQUERY_METASTORE_PROJECT_ID] - [--expiration-time=EXPIRATION_TIME | --max-age=MAX_AGE] + [--delete-expiration-time=DELETE_EXPIRATION_TIME + | --delete-max-age=DELETE_MAX_AGE | --expiration-time=EXPIRATION_TIME + | --max-age=MAX_AGE] + [--delete-max-idle=DELETE_MAX_IDLE | --max-idle=MAX_IDLE] [--gce-pd-kms-key=GCE_PD_KMS_KEY : --gce-pd-kms-key-keyring=GCE_PD_KMS_KEY_KEYRING --gce-pd-kms-key-location=GCE_PD_KMS_KEY_LOCATION @@ -73,6 +78,8 @@ SYNOPSIS --num-secondary-workers=NUM_SECONDARY_WORKERS --num-workers=NUM_WORKERS --secondary-worker-type=TYPE; default="preemptible"] + [--stop-expiration-time=STOP_EXPIRATION_TIME + | --stop-max-age=STOP_MAX_AGE] [--worker-machine-type=WORKER_MACHINE_TYPE | --worker-machine-types=type=MACHINE_TYPE[, type=MACHINE_TYPE...][,rank=RANK]] [GCLOUD_WIDE_FLAG ...] @@ -138,6 +145,10 @@ FLAGS dependencies, miscellaneous config files, and job driver console output when using this cluster. + --cluster-type=TYPE + The type of cluster. TYPE must be one of: standard, single-node, + zero-scale. + --driver-pool-accelerator=[type=TYPE,[count=COUNT],...] Attaches accelerators, such as GPUs, to the driver-pool instance(s). @@ -265,11 +276,6 @@ FLAGS which contains the list of available CPU platforms in the zone (see Availability of CPU platforms for more information). - --max-idle=MAX_IDLE - The duration before cluster is auto-deleted after last job completes, - such as "2h" or "1d". See $ gcloud topic datetimes for information on - duration formats. - --min-secondary-worker-fraction=MIN_SECONDARY_WORKER_FRACTION Minimum fraction of secondary worker nodes required to create the cluster. If it is not met, cluster creation will fail. Must be a @@ -415,6 +421,11 @@ FLAGS security operations, such as remote attestation, encryption, and sealing of keys. + --stop-max-idle=STOP_MAX_IDLE + The duration after the last job completes to auto-stop the cluster, + such as "2h" or "1d". See $ gcloud topic datetimes for information on + duration formats. + --temp-bucket=TEMP_BUCKET The Google Cloud Storage bucket to use by default to store ephemeral cluster and jobs data, such as Spark and MapReduce history files. @@ -501,15 +512,37 @@ FLAGS At most one of these can be specified: + --delete-expiration-time=DELETE_EXPIRATION_TIME + The time when the cluster will be auto-deleted, such as + "2017-08-29T18:52:51.142Z." See $ gcloud topic datetimes for + information on time formats. + + --delete-max-age=DELETE_MAX_AGE + The lifespan of the cluster, with auto-deletion upon completion, such + as "2h" or "1d". See $ gcloud topic datetimes for information on + duration formats. + --expiration-time=EXPIRATION_TIME - The time when cluster will be auto-deleted, such as + The time when the cluster will be auto-deleted, such as "2017-08-29T18:52:51.142Z." See $ gcloud topic datetimes for information on time formats. --max-age=MAX_AGE - The lifespan of the cluster before it is auto-deleted, such as "2h" - or "1d". See $ gcloud topic datetimes for information on duration - formats. + The lifespan of the cluster, with auto-deletion upon completion, such + as "2h" or "1d". See $ gcloud topic datetimes for information on + duration formats. + + At most one of these can be specified: + + --delete-max-idle=DELETE_MAX_IDLE + The duration after the last job completes to auto-delete the cluster, + such as "2h" or "1d". See $ gcloud topic datetimes for information on + duration formats. + + --max-idle=MAX_IDLE + The duration after the last job completes to autto-delete the + cluster, such as "2h" or "1d". See $ gcloud topic datetimes for + information on duration formats. Key resource - The Cloud KMS (Key Management Service) cryptokey that will be used to protect the cluster. The 'Compute Engine Service Agent' service @@ -917,6 +950,18 @@ FLAGS The type of the secondary worker group. TYPE must be one of: preemptible, non-preemptible, spot. + At most one of these can be specified: + + --stop-expiration-time=STOP_EXPIRATION_TIME + The time when the cluster will be auto-stopped, such as + "2017-08-29T18:52:51.142Z." See $ gcloud topic datetimes for + information on time formats. + + --stop-max-age=STOP_MAX_AGE + The lifespan of the cluster, with auto-stop upon completion, such as + "2h" or "1d". See $ gcloud topic datetimes for information on + duration formats. + At most one of these can be specified: --worker-machine-type=WORKER_MACHINE_TYPE diff --git a/gcloud/beta/dataproc/clusters/update b/gcloud/beta/dataproc/clusters/update index 85d7d5dd3..e7d4b5048 100644 --- a/gcloud/beta/dataproc/clusters/update +++ b/gcloud/beta/dataproc/clusters/update @@ -10,8 +10,16 @@ SYNOPSIS [--num-workers=NUM_WORKERS] [--update-labels=[KEY=VALUE,...]] [--autoscaling-policy=AUTOSCALING_POLICY | --disable-autoscaling] [--clear-labels | --remove-labels=[KEY,...]] - [--expiration-time=EXPIRATION_TIME | --max-age=MAX_AGE | --no-max-age] - [--max-idle=MAX_IDLE | --no-max-idle] [GCLOUD_WIDE_FLAG ...] + [--delete-expiration-time=DELETE_EXPIRATION_TIME + | --delete-max-age=DELETE_MAX_AGE | --no-delete-max-age + | --expiration-time=EXPIRATION_TIME | --max-age=MAX_AGE + | --no-max-age] + [--delete-max-idle=DELETE_MAX_IDLE | --no-delete-max-idle + | --max-idle=MAX_IDLE | --no-max-idle] + [--stop-expiration-time=STOP_EXPIRATION_TIME + | --stop-max-age=STOP_MAX_AGE | --no-stop-max-age] + [--stop-max-idle=STOP_MAX_IDLE | --no-stop-max-idle] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) Update the number of worker nodes and/or the labels in a cluster. @@ -164,13 +172,27 @@ FLAGS At most one of these can be specified: + --delete-expiration-time=DELETE_EXPIRATION_TIME + The time when the cluster will be auto-deleted, such as + "2017-08-29T18:52:51.142Z". See $ gcloud topic datetimes for + information on time formats. + + --delete-max-age=DELETE_MAX_AGE + The lifespan of the cluster with auto-deletion upon completion, such + as "2h" or "1d". See $ gcloud topic datetimes for information on + duration formats. + + --no-delete-max-age + Cancels the cluster auto-deletion by maximum cluster age (configured + by --delete-max-age or --delete-expiration-time flags) + --expiration-time=EXPIRATION_TIME - The time when cluster will be auto-deleted, such as + The time when the cluster will be auto-deleted, such as "2017-08-29T18:52:51.142Z". See $ gcloud topic datetimes for information on time formats. --max-age=MAX_AGE - The lifespan of the cluster before it is auto-deleted, such as "2h" + The lifespan of the cluster, with auto-deletion upon completion, "2h" or "1d". See $ gcloud topic datetimes for information on duration formats. @@ -180,8 +202,17 @@ FLAGS At most one of these can be specified: + --delete-max-idle=DELETE_MAX_IDLE + The duration after the last job completes to auto-delete the cluster, + such as "2h" or "1d". See $ gcloud topic datetimes for information on + duration formats. + + --no-delete-max-idle + Cancels the cluster auto-deletion by cluster idle duration + (configured by --delete-max-idle flag) + --max-idle=MAX_IDLE - The duration before cluster is auto-deleted after last job finished, + The duration after the last job completes to auto-delete the cluster, such as "2h" or "1d". See $ gcloud topic datetimes for information on duration formats. @@ -189,6 +220,33 @@ FLAGS Cancels the cluster auto-deletion by cluster idle duration (configured by --max-idle flag) + At most one of these can be specified: + + --stop-expiration-time=STOP_EXPIRATION_TIME + The time when the cluster will be auto-stopped, such as + "2017-08-29T18:52:51.142Z". See $ gcloud topic datetimes for + information on time formats. + + --stop-max-age=STOP_MAX_AGE + The lifespan of the cluster, with auto-stop upon completion, such as + "2h" or "1d". See $ gcloud topic datetimes for information on + duration formats. + + --no-stop-max-age + Cancels the cluster auto-stop by maximum cluster age (configured by + --stop-max-age or --stop-expiration-time flags) + + At most one of these can be specified: + + --stop-max-idle=STOP_MAX_IDLE + The duration after the last job completes to auto-stop the cluster, + such as "2h" or "1d". See $ gcloud topic datetimes for information on + duration formats. + + --no-stop-max-idle + Cancels the cluster auto-stop by cluster idle duration (configured by + --stop-max-idle flag) + GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, diff --git a/gcloud/beta/dataproc/workflow-templates/set-managed-cluster b/gcloud/beta/dataproc/workflow-templates/set-managed-cluster index 8339a81b8..544b5090d 100644 --- a/gcloud/beta/dataproc/workflow-templates/set-managed-cluster +++ b/gcloud/beta/dataproc/workflow-templates/set-managed-cluster @@ -5,7 +5,7 @@ NAME SYNOPSIS gcloud beta dataproc workflow-templates set-managed-cluster (TEMPLATE : --region=REGION) [--autoscaling-policy=AUTOSCALING_POLICY] - [--bucket=BUCKET] [--cluster-name=CLUSTER_NAME] + [--bucket=BUCKET] [--cluster-name=CLUSTER_NAME] [--cluster-type=TYPE] [--enable-component-gateway] [--initialization-action-timeout=TIMEOUT; default="10m"] [--initialization-actions=CLOUD_STORAGE_URI,[...]] @@ -128,6 +128,10 @@ FLAGS The name of the managed dataproc cluster. If unspecified, the workflow template ID will be used. + --cluster-type=TYPE + The type of cluster. TYPE must be one of: standard, single-node, + zero-scale. + --enable-component-gateway Enable access to the web UIs of selected components on the cluster through the component gateway. diff --git a/gcloud/beta/filestore/instances/create b/gcloud/beta/filestore/instances/create index c643a955f..d8358dc5e 100644 --- a/gcloud/beta/filestore/instances/create +++ b/gcloud/beta/filestore/instances/create @@ -35,6 +35,7 @@ EXAMPLES --network=name=NETWORK_NAME,\ reserved-ip-range=RESERVED_IP_RANGE,connect-mode=CONNECT_MODE,\ psc-endpoint-project=PSC_ENDPOINT_PROJECT --zone=ZONE \ + --performance=max-iops-per-tb=MAX-IOPS-PER-TB \ --kms-key=KMS-KEY --kms-keyring=KMS_KEYRING \ --kms-location=KMS_LOCATION --kms-project=KMS_PROJECT \ --managed-ad=domain=DOMAIN,computer=COMPUTER \ diff --git a/gcloud/beta/filestore/instances/update b/gcloud/beta/filestore/instances/update index 2e9471caf..d1d88b768 100644 --- a/gcloud/beta/filestore/instances/update +++ b/gcloud/beta/filestore/instances/update @@ -61,6 +61,12 @@ EXAMPLES $ gcloud beta filestore instances update NAME --project=PROJECT_ID \ --zone=ZONE --file-share=name=VOLUME_NAME,capacity=CAPACITY + The following command updates a Filestore instance named NAME to configure + the max-iops-per-tb to MAX-IOPS-PER-TB. + + $ gcloud beta filestore instances update NAME --project=PROJECT_ID \ + --zone=ZONE --performance=max-iops-per-tb=MAX-IOPS-PER-TB + POSITIONAL ARGUMENTS Instance resource - The instance to update. The arguments in this group can be used to specify the attributes of this resource. (NOTE) Some diff --git a/gcloud/beta/iam/roles/undelete b/gcloud/beta/iam/roles/undelete index 3eea7eae7..0a47b7c1f 100644 --- a/gcloud/beta/iam/roles/undelete +++ b/gcloud/beta/iam/roles/undelete @@ -18,13 +18,12 @@ DESCRIPTION EXAMPLES To undelete the role ProjectUpdater of the organization 1234567, run: - $ gcloud beta iam roles undelete roles/ProjectUpdater \ + $ gcloud beta iam roles undelete ProjectUpdater \ --organization=1234567 To undelete the role ProjectUpdater of the project myproject, run: - $ gcloud beta iam roles undelete roles/ProjectUpdater \ - --project=myproject + $ gcloud beta iam roles undelete ProjectUpdater --project=myproject POSITIONAL ARGUMENTS ROLE_ID diff --git a/gcloud/beta/iam/roles/update b/gcloud/beta/iam/roles/update index e1bace3bd..eb0f7c141 100644 --- a/gcloud/beta/iam/roles/update +++ b/gcloud/beta/iam/roles/update @@ -15,13 +15,13 @@ DESCRIPTION EXAMPLES To update the role ProjectUpdater from a YAML file, run: - $ gcloud beta iam roles update roles/ProjectUpdater \ - --organization=123 --file=role_file_path + $ gcloud beta iam roles update ProjectUpdater --organization=123 \ + --file=role_file_path To update the role ProjectUpdater with flags, run: - $ gcloud beta iam roles update roles/ProjectUpdater \ - --project=myproject --permissions=permission1,permission2 + $ gcloud beta iam roles update ProjectUpdater --project=myproject \ + --permissions=permission1,permission2 POSITIONAL ARGUMENTS ROLE_ID diff --git a/gcloud/beta/memorystore/instances/create b/gcloud/beta/memorystore/instances/create index 3366cd769..e1be0fef9 100644 --- a/gcloud/beta/memorystore/instances/create +++ b/gcloud/beta/memorystore/instances/create @@ -2,13 +2,15 @@ NAME gcloud beta memorystore instances create - create a Memorystore instance SYNOPSIS - gcloud beta memorystore instances create (INSTANCE : --location=LOCATION) - [--async] [--async-instance-endpoints-deletion-enabled] + gcloud beta memorystore instances create INSTANCE [--async] + [--async-instance-endpoints-deletion-enabled] [--authorization-mode=AUTHORIZATION_MODE] [--deletion-protection-enabled] [--endpoints=[connections=CONNECTIONS]] [--engine-configs=[ENGINE_CONFIGS,...]] - [--engine-version=ENGINE_VERSION] [--labels=[LABELS,...]] [--mode=MODE] - [--node-type=NODE_TYPE] [--ondemand-maintenance] + [--engine-version=ENGINE_VERSION] [--labels=[LABELS,...]] + [--location=LOCATION] + [--maintenance-policy-weekly-window=[day=DAY],[startTime=STARTTIME]] + [--mode=MODE] [--node-type=NODE_TYPE] [--ondemand-maintenance] [--psc-auto-connections=[network=NETWORK], [port=PORT],[projectId=PROJECTID]] [--replica-count=REPLICA_COUNT] [--request-id=REQUEST_ID] [--shard-count=SHARD_COUNT] @@ -17,6 +19,7 @@ SYNOPSIS --persistence-config-mode=PERSISTENCE_CONFIG_MODE --rdb-config-snapshot-period=RDB_CONFIG_SNAPSHOT_PERIOD --rdb-config-snapshot-start-time=RDB_CONFIG_SNAPSHOT_START_TIME] + [--cross-instance-replication-config-role=CROSS_INSTANCE_REPLICATION_CONFIG_ROLE : --cross-instance-replication-config-secondary-instances=[instance=INSTANCE] --primary-instance=PRIMARY_INSTANCE] [--zone-distribution-config=ZONE_DISTRIBUTION_CONFIG --zone-distribution-config-mode=ZONE_DISTRIBUTION_CONFIG_MODE] [GCLOUD_WIDE_FLAG ...] @@ -49,10 +52,9 @@ EXAMPLES POSITIONAL ARGUMENTS Instance resource - Identifier. Unique name of the instance. Format: - projects/{project}/locations/{location}/instances/{instance} 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}/locations/{location}/instances/{instance} 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 instance on the command line with a fully @@ -60,6 +62,11 @@ POSITIONAL ARGUMENTS ◆ provide the argument --project on the command line; ◆ set the property core/project. + To set the location attribute: + ◆ provide the argument instance on the command line with a fully + specified name; + ◆ provide the argument --location on the command line. + This must be specified. INSTANCE @@ -68,17 +75,6 @@ POSITIONAL ARGUMENTS To set the instance attribute: ▸ provide the argument instance on the command line. - This positional argument must be specified if any of the other - arguments in this group are specified. - - --location=LOCATION - The location id of the instance resource. - - To set the location attribute: - ▸ provide the argument instance on the command line with a fully - specified name; - ▸ provide the argument --location on the command line. - FLAGS --async Return immediately, without waiting for the operation in progress to @@ -188,6 +184,55 @@ FLAGS --labels=path_to_file.(yaml|json) + --location=LOCATION + For resources [instance], provides fallback value for resource location + attribute. When the resource's full URI path is not provided, location + will fallback to this flag value. + + Maintenance policy per instance. + + --maintenance-policy-weekly-window=[day=DAY],[startTime=STARTTIME] + Maintenance window that is applied to resources covered by this + policy. Minimum 1. For the current version, the maximum number of + weekly_window is expected to be one. + + day + Allows to define schedule that runs specified day of the week. + + startTime + Start time of the window in UTC. + + hours + Hours of a day in 24 hour format. Must be greater than or + equal to 0 and typically must be less than or equal to 23. An + API may choose to allow the value "24:00:00" for scenarios + like business closing time. + + minutes + Minutes of an hour. Must be greater than or equal to 0 and + less than or equal to 59. + + nanos + Fractions of seconds, in nanoseconds. Must be greater than or + equal to 0 and less than or equal to 999,999,999. + + seconds + Seconds of a minute. Must be greater than or equal to 0 and + typically must be less than or equal to 59. An API may allow + the value 60 if it allows leap-seconds. + + Shorthand Example: + + --maintenance-policy-weekly-window=day=string,startTime={hours=int,minutes=int,nanos=int,seconds=int} --maintenance-policy-weekly-window=day=string,startTime={hours=int,minutes=int,nanos=int,seconds=int} + + JSON Example: + + --maintenance-policy-weekly-window='[{"day": "string", "startTime": {"hours": int, "minutes": int, "nanos": int, "seconds": int}}]' + + File Example: + + --maintenance-policy-weekly-window=path_to_file.(yaml|json) + --mode=MODE The mode config for the instance. MODE must be one of: @@ -324,6 +369,76 @@ FLAGS future snapshots will be aligned. If not provided, the current time will be used. + Cross instance replication config. + + --cross-instance-replication-config-role=CROSS_INSTANCE_REPLICATION_CONFIG_ROLE + The role of the instance in cross instance replication. + CROSS_INSTANCE_REPLICATION_CONFIG_ROLE must be one of: + + none + This instance does not participate in cross instance replication. + It is an independent instance and does not replicate to or from + any other instances. + primary + A instance that allows both reads and writes. Any data written to + this instance is also replicated to the attached secondary + instances. + secondary + A instance that allows only reads and replicates data from a + primary instance. + + This flag argument must be specified if any of the other arguments in + this group are specified. + + --cross-instance-replication-config-secondary-instances=[instance=INSTANCE] + List of secondary instances that are replicating from this primary + instance. + + This field is only set for a primary instance. + + instance + The full resource path of the remote instance in the format: + projects//locations//instances/. + + Shorthand Example: + + --cross-instance-replication-config-secondary-instances=instance=string --cross-instance-replication-config-secondary-instances=instance=string + + JSON Example: + + --cross-instance-replication-config-secondary-instances='[{"instance": "string"}]' + + File Example: + + --cross-instance-replication-config-secondary-instances=path_to_file.(yaml|json) + + Details of the remote instance associated with this instance in a cross + instance replication setup. + + Instance resource - The full resource path of the remote instance in + the format: + projects//locations//instances/ 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 --primary-instance on the command line with + a fully specified name; + ▫ provide the argument --project on the command line; + ▫ set the property core/project. + + To set the location attribute: + ▫ provide the argument --primary-instance on the command line with + a fully specified name; + ▫ provide the argument --location on the command line. + + --primary-instance=PRIMARY_INSTANCE + ID of the instance or fully qualified identifier for the + instance. + + To set the instance attribute: + ◇ provide the argument --primary-instance on the command line. + Zone distribution configuration for allocation of instance resources. --zone-distribution-config=ZONE_DISTRIBUTION_CONFIG diff --git a/gcloud/beta/memorystore/instances/help b/gcloud/beta/memorystore/instances/help index 3512899ee..1fb88afee 100644 --- a/gcloud/beta/memorystore/instances/help +++ b/gcloud/beta/memorystore/instances/help @@ -31,6 +31,9 @@ COMMANDS (BETA) List all Memorystore instances in a specified project and location. + reschedule-maintenance + (BETA) Reschedule maintenance window for an instance. + update (BETA) Update the configuration of a Memorystore instance. diff --git a/gcloud/beta/memorystore/instances/reschedule-maintenance b/gcloud/beta/memorystore/instances/reschedule-maintenance new file mode 100644 index 000000000..2c0ece20d --- /dev/null +++ b/gcloud/beta/memorystore/instances/reschedule-maintenance @@ -0,0 +1,92 @@ +NAME + gcloud beta memorystore instances reschedule-maintenance - reschedule + maintenance window for an instance + +SYNOPSIS + gcloud beta memorystore instances reschedule-maintenance + (INSTANCE : --location=LOCATION) --reschedule-type=RESCHEDULE_TYPE + [--async] [--schedule-time=SCHEDULE_TIME] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Reschedule maintenance window for an instance. + +EXAMPLES + To reschedule maintenance window for an instance with the name my-instance + in region us-central-1 with immediate, run: + + $ gcloud beta memorystore instances reschedule-maintenance \ + `my-instance` --project=my-project --location=us-central1 \ + --reschedule-type=IMMEDIATE + +POSITIONAL ARGUMENTS + Instance resource - Name of the instance to reschedule maintenance for: + projects/{project}/locations/{location_id}/instances/{instance} The + arguments in this group can be used to specify the attributes of this + resource. (NOTE) Some attributes are not given arguments in this group but + can be set in other ways. + + To set the project attribute: + ◆ provide the argument instance on the command line with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + INSTANCE + ID of the instance or fully qualified identifier for the instance. + + To set the instance attribute: + ▸ provide the argument instance on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + The location id of the instance resource. + + To set the location attribute: + ▸ provide the argument instance on the command line with a fully + specified name; + ▸ provide the argument --location on the command line. + +REQUIRED FLAGS + --reschedule-type=RESCHEDULE_TYPE + If reschedule type is SPECIFIC_TIME, schedule_time must be set. + RESCHEDULE_TYPE must be one of: + + immediate + If the user wants to schedule the maintenance to happen now. + specific-time + If the user wants to reschedule the maintenance to a specific time. + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --schedule-time=SCHEDULE_TIME + Timestamp when the maintenance shall be rescheduled to if + reschedule_type=SPECIFIC_TIME, in RFC 3339 format. Example: + 2012-11-15T16:19:00.094Z. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the memorystore/v1beta API. The full documentation for + this API can be found at: https://cloud.google.com/memorystore/ + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud memorystore instances reschedule-maintenance + + $ gcloud alpha memorystore instances reschedule-maintenance + diff --git a/gcloud/beta/memorystore/instances/update b/gcloud/beta/memorystore/instances/update index 356703c36..0a09e05dd 100644 --- a/gcloud/beta/memorystore/instances/update +++ b/gcloud/beta/memorystore/instances/update @@ -3,17 +3,25 @@ NAME Memorystore instance SYNOPSIS - gcloud beta memorystore instances update (INSTANCE : --location=LOCATION) - [--async] [--[no-]async-instance-endpoints-deletion-enabled] + gcloud beta memorystore instances update INSTANCE [--async] + [--[no-]async-instance-endpoints-deletion-enabled] [--[no-]deletion-protection-enabled] [--engine-version=ENGINE_VERSION] - [--mode=MODE] [--node-type=NODE_TYPE] [--[no-]ondemand-maintenance] - [--replica-count=REPLICA_COUNT] [--request-id=REQUEST_ID] - [--shard-count=SHARD_COUNT] + [--location=LOCATION] [--mode=MODE] [--node-type=NODE_TYPE] + [--[no-]ondemand-maintenance] [--replica-count=REPLICA_COUNT] + [--request-id=REQUEST_ID] [--shard-count=SHARD_COUNT] [--aof-config-append-fsync=AOF_CONFIG_APPEND_FSYNC --clear-persistence-config --persistence-config-mode=PERSISTENCE_CONFIG_MODE --rdb-config-snapshot-period=RDB_CONFIG_SNAPSHOT_PERIOD --rdb-config-snapshot-start-time=RDB_CONFIG_SNAPSHOT_START_TIME] + [--clear-cross-instance-replication-config + --cross-instance-replication-config-role=CROSS_INSTANCE_REPLICATION_CONFIG_ROLE --clear-primary-instance | --primary-instance=PRIMARY_INSTANCE --cross-instance-replication-config-secondary-instances=[instance=INSTANCE] | --add-cross-instance-replication-config-secondary-instances=[instance=INSTANCE] --clear-cross-instance-replication-config-secondary-instances | --remove-cross-instance-replication-config-secondary-instances=[instance=INSTANCE]] + [--clear-maintenance-policy + --maintenance-policy-weekly-window=[day=DAY],[startTime=STARTTIME] + | --add-maintenance-policy-weekly-window=[day=DAY], + [startTime=STARTTIME] --clear-maintenance-policy-weekly-window + | --remove-maintenance-policy-weekly-window=[day=DAY], + [startTime=STARTTIME]] [--endpoints=[connections=CONNECTIONS] | --add-endpoints=[connections=CONNECTIONS] --clear-endpoints | --remove-endpoints=[connections=CONNECTIONS]] @@ -44,10 +52,9 @@ EXAMPLES POSITIONAL ARGUMENTS Instance resource - Identifier. Unique name of the instance. Format: - projects/{project}/locations/{location}/instances/{instance} 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}/locations/{location}/instances/{instance} 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 instance on the command line with a fully @@ -55,6 +62,11 @@ POSITIONAL ARGUMENTS ◆ provide the argument --project on the command line; ◆ set the property core/project. + To set the location attribute: + ◆ provide the argument instance on the command line with a fully + specified name; + ◆ provide the argument --location on the command line. + This must be specified. INSTANCE @@ -63,17 +75,6 @@ POSITIONAL ARGUMENTS To set the instance attribute: ▸ provide the argument instance on the command line. - This positional argument must be specified if any of the other - arguments in this group are specified. - - --location=LOCATION - The location id of the instance resource. - - To set the location attribute: - ▸ provide the argument instance on the command line with a fully - specified name; - ▸ provide the argument --location on the command line. - FLAGS --async Return immediately, without waiting for the operation in progress to @@ -99,6 +100,11 @@ FLAGS --engine-version=ENGINE_VERSION Engine version of the instance. + --location=LOCATION + For resources [instance], provides fallback value for resource location + attribute. When the resource's full URI path is not provided, location + will fallback to this flag value. + --mode=MODE The mode config for the instance. MODE must be one of: @@ -203,6 +209,289 @@ FLAGS future snapshots will be aligned. If not provided, the current time will be used. + Cross instance replication config. + + --clear-cross-instance-replication-config + Set instance.crossInstanceReplicationConfig back to default value. + + --cross-instance-replication-config-role=CROSS_INSTANCE_REPLICATION_CONFIG_ROLE + The role of the instance in cross instance replication. + CROSS_INSTANCE_REPLICATION_CONFIG_ROLE must be one of: + + none + This instance does not participate in cross instance replication. + It is an independent instance and does not replicate to or from + any other instances. + primary + A instance that allows both reads and writes. Any data written to + this instance is also replicated to the attached secondary + instances. + secondary + A instance that allows only reads and replicates data from a + primary instance. + + Details of the remote instance associated with this instance in a cross + instance replication setup. + + Update primary_instance. + + At most one of these can be specified: + + --clear-primary-instance + Clear primary_instance value and set to null. + + Instance resource - Set primary_instance to new value. + + The full resource path of the remote instance in the format: + projects//locations//instances/ 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 --primary-instance on the command line + with a fully specified name; + ◇ provide the argument --project on the command line; + ◇ set the property core/project. + + To set the location attribute: + ◇ provide the argument --primary-instance on the command line + with a fully specified name; + ◇ provide the argument --location on the command line. + + --primary-instance=PRIMARY_INSTANCE + ID of the instance or fully qualified identifier for the + instance. + + To set the instance attribute: + ▹ provide the argument --primary-instance on the command + line. + + Update cross_instance_replication_config_secondary_instances. + + At most one of these can be specified: + + --cross-instance-replication-config-secondary-instances=[instance=INSTANCE] + Set cross_instance_replication_config_secondary_instances to new + value. List of secondary instances that are replicating from this + primary instance. + + This field is only set for a primary instance. + + instance + The full resource path of the remote instance in the format: + projects//locations//instances/. + + Shorthand Example: + + --cross-instance-replication-config-secondary-instances=instance=string --cross-instance-replication-config-secondary-instances=instance=string + + JSON Example: + + --cross-instance-replication-config-secondary-instances='[{"instance": "string"}]' + + File Example: + + --cross-instance-replication-config-secondary-instances=path_to_file.(yaml|json) + + --add-cross-instance-replication-config-secondary-instances=[instance=INSTANCE] + Add new value to + cross_instance_replication_config_secondary_instances list. List of + secondary instances that are replicating from this primary + instance. + + This field is only set for a primary instance. + + instance + The full resource path of the remote instance in the format: + projects//locations//instances/. + + Shorthand Example: + + --add-cross-instance-replication-config-secondary-instances=instance=string --add-cross-instance-replication-config-secondary-instances=instance=string + + JSON Example: + + --add-cross-instance-replication-config-secondary-instances='[{"instance": "string"}]' + + File Example: + + --add-cross-instance-replication-config-secondary-instances=path_to_file.(yaml|json) + + At most one of these can be specified: + + --clear-cross-instance-replication-config-secondary-instances + Clear cross_instance_replication_config_secondary_instances value + and set to empty list. + + --remove-cross-instance-replication-config-secondary-instances=[instance=INSTANCE] + Remove existing value from + cross_instance_replication_config_secondary_instances list. List + of secondary instances that are replicating from this primary + instance. + + This field is only set for a primary instance. + + instance + The full resource path of the remote instance in the format: + projects//locations//instances/. + + Shorthand Example: + + --remove-cross-instance-replication-config-secondary-instances=instance=string --remove-cross-instance-replication-config-secondary-instances=instance=string + + JSON Example: + + --remove-cross-instance-replication-config-secondary-instances='[{"instance": "string"}]' + + File Example: + + --remove-cross-instance-replication-config-secondary-instances=path_to_file.(yaml|json) + + Maintenance policy per instance. + + --clear-maintenance-policy + Set instance.maintenancePolicy back to default value. + + Update maintenance_policy_weekly_window. + + At most one of these can be specified: + + --maintenance-policy-weekly-window=[day=DAY],[startTime=STARTTIME] + Set maintenance_policy_weekly_window to new value. Maintenance + window that is applied to resources covered by this policy. Minimum + 1. For the current version, the maximum number of weekly_window is + expected to be one. + + day + Allows to define schedule that runs specified day of the week. + + startTime + Start time of the window in UTC. + + hours + Hours of a day in 24 hour format. Must be greater than or + equal to 0 and typically must be less than or equal to 23. + An API may choose to allow the value "24:00:00" for + scenarios like business closing time. + + minutes + Minutes of an hour. Must be greater than or equal to 0 and + less than or equal to 59. + + nanos + Fractions of seconds, in nanoseconds. Must be greater than + or equal to 0 and less than or equal to 999,999,999. + + seconds + Seconds of a minute. Must be greater than or equal to 0 and + typically must be less than or equal to 59. An API may + allow the value 60 if it allows leap-seconds. + + Shorthand Example: + + --maintenance-policy-weekly-window=day=string,startTime={hours=int,minutes=int,nanos=int,seconds=int} --maintenance-policy-weekly-window=day=string,startTime={hours=int,minutes=int,nanos=int,seconds=int} + + JSON Example: + + --maintenance-policy-weekly-window='[{"day": "string", "startTime": {"hours": int, "minutes": int, "nanos": int, "seconds": int}}]' + + File Example: + + --maintenance-policy-weekly-window=path_to_file.(yaml|json) + + --add-maintenance-policy-weekly-window=[day=DAY],[startTime=STARTTIME] + Add new value to maintenance_policy_weekly_window list. Maintenance + window that is applied to resources covered by this policy. Minimum + 1. For the current version, the maximum number of weekly_window is + expected to be one. + + day + Allows to define schedule that runs specified day of the week. + + startTime + Start time of the window in UTC. + + hours + Hours of a day in 24 hour format. Must be greater than or + equal to 0 and typically must be less than or equal to 23. + An API may choose to allow the value "24:00:00" for + scenarios like business closing time. + + minutes + Minutes of an hour. Must be greater than or equal to 0 and + less than or equal to 59. + + nanos + Fractions of seconds, in nanoseconds. Must be greater than + or equal to 0 and less than or equal to 999,999,999. + + seconds + Seconds of a minute. Must be greater than or equal to 0 and + typically must be less than or equal to 59. An API may + allow the value 60 if it allows leap-seconds. + + Shorthand Example: + + --add-maintenance-policy-weekly-window=day=string,startTime={hours=int,minutes=int,nanos=int,seconds=int} --add-maintenance-policy-weekly-window=day=string,startTime={hours=int,minutes=int,nanos=int,seconds=int} + + JSON Example: + + --add-maintenance-policy-weekly-window='[{"day": "string", "startTime": {"hours": int, "minutes": int, "nanos": int, "seconds": int}}]' + + File Example: + + --add-maintenance-policy-weekly-window=path_to_file.(yaml|json) + + At most one of these can be specified: + + --clear-maintenance-policy-weekly-window + Clear maintenance_policy_weekly_window value and set to empty + list. + + --remove-maintenance-policy-weekly-window=[day=DAY],[startTime=STARTTIME] + Remove existing value from maintenance_policy_weekly_window list. + Maintenance window that is applied to resources covered by this + policy. Minimum 1. For the current version, the maximum number of + weekly_window is expected to be one. + + day + Allows to define schedule that runs specified day of the + week. + + startTime + Start time of the window in UTC. + + hours + Hours of a day in 24 hour format. Must be greater than or + equal to 0 and typically must be less than or equal to + 23. An API may choose to allow the value "24:00:00" for + scenarios like business closing time. + + minutes + Minutes of an hour. Must be greater than or equal to 0 + and less than or equal to 59. + + nanos + Fractions of seconds, in nanoseconds. Must be greater + than or equal to 0 and less than or equal to 999,999,999. + + seconds + Seconds of a minute. Must be greater than or equal to 0 + and typically must be less than or equal to 59. An API + may allow the value 60 if it allows leap-seconds. + + Shorthand Example: + + --remove-maintenance-policy-weekly-window=day=string,startTime={hours=int,minutes=int,nanos=int,seconds=int} --remove-maintenance-policy-weekly-window=day=string,startTime={hours=int,minutes=int,nanos=int,seconds=int} + + JSON Example: + + --remove-maintenance-policy-weekly-window='[{"day": "string", "startTime": {"hours": int, "minutes": int, "nanos": int, "seconds": int}}]' + + File Example: + + --remove-maintenance-policy-weekly-window=path_to_file.(yaml|json) + Update endpoints. At most one of these can be specified: diff --git a/gcloud/beta/netapp/backup-vaults/create b/gcloud/beta/netapp/backup-vaults/create index fea6d2ae3..46c308a7e 100644 --- a/gcloud/beta/netapp/backup-vaults/create +++ b/gcloud/beta/netapp/backup-vaults/create @@ -5,6 +5,7 @@ NAME SYNOPSIS gcloud beta netapp backup-vaults create (BACKUP_VAULT : --location=LOCATION) [--async] + [--backup-region=BACKUP_REGION] [--backup-vault-type=BACKUP_VAULT_TYPE] [--description=DESCRIPTION] [--labels=[KEY=VALUE,...]] [GCLOUD_WIDE_FLAG ...] @@ -56,6 +57,13 @@ FLAGS Return immediately, without waiting for the operation in progress to complete. + --backup-region=BACKUP_REGION + String indicating backup location for the Backup Vault + + --backup-vault-type=BACKUP_VAULT_TYPE + String indicating the type of backup vault. The supported values are: + 'IN_REGION','CROSS_REGION' + --description=DESCRIPTION A description of the Cloud NetApp Backup Vault diff --git a/gcloud/beta/network-connectivity/hubs/accept-spoke-update b/gcloud/beta/network-connectivity/hubs/accept-spoke-update new file mode 100644 index 000000000..28232c863 --- /dev/null +++ b/gcloud/beta/network-connectivity/hubs/accept-spoke-update @@ -0,0 +1,72 @@ +NAME + gcloud beta network-connectivity hubs accept-spoke-update - accept a + proposal to update a spoke in a hub + +SYNOPSIS + gcloud beta network-connectivity hubs accept-spoke-update HUB --spoke=SPOKE + --spoke-etag=SPOKE_ETAG [--async] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Accept a proposed or previously rejected VPC spoke update. By + accepting a spoke update, you permit updating connectivity between the + associated VPC network and other VPC networks that are attached to the same + hub. + +EXAMPLES + To accept updating a spoke named my-spoke with etag in a hub named my-hub, + run: + + $ gcloud beta network-connectivity hubs accept-spoke-update my-hub \ + --spoke="projects/spoke-project/locations/global/hubs/my-spoke" \ + --spoke-etag=etag + +POSITIONAL ARGUMENTS + Hub resource - Name of the hub to accept the spoke update. This represents + a Cloud resource. (NOTE) Some attributes are not given arguments in this + group but can be set in other ways. + + To set the project attribute: + ◆ provide the argument hub on the command line with a fully specified + name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + HUB + ID of the hub or fully qualified identifier for the hub. + + To set the hub attribute: + ▸ provide the argument hub on the command line. + +REQUIRED FLAGS + --spoke=SPOKE + URI of the spoke to accept update + + --spoke-etag=SPOKE_ETAG + Etag of the spoke to accept update + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the networkconnectivity/v1 API. The full documentation + for this API can be found at: + https://cloud.google.com/network-connectivity/docs/reference/networkconnectivity/rest + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud network-connectivity hubs accept-spoke-update + diff --git a/gcloud/beta/network-connectivity/hubs/help b/gcloud/beta/network-connectivity/hubs/help index 4fccc06b0..02f810e24 100644 --- a/gcloud/beta/network-connectivity/hubs/help +++ b/gcloud/beta/network-connectivity/hubs/help @@ -29,6 +29,9 @@ COMMANDS accept-spoke (BETA) Accept a spoke into a hub. + accept-spoke-update + (BETA) Accept a proposal to update a spoke in a hub. + add-iam-policy-binding (BETA) Add an IAM policy binding to the IAM policy of a hub resource. @@ -53,6 +56,9 @@ COMMANDS reject-spoke (BETA) Reject a spoke from a hub. + reject-spoke-update + (BETA) Reject a proposal to update a spoke in a hub. + remove-iam-policy-binding (BETA) Remove an IAM policy binding from the IAM policy of a hub resource. diff --git a/gcloud/beta/network-connectivity/hubs/reject-spoke-update b/gcloud/beta/network-connectivity/hubs/reject-spoke-update new file mode 100644 index 000000000..69f791ce3 --- /dev/null +++ b/gcloud/beta/network-connectivity/hubs/reject-spoke-update @@ -0,0 +1,75 @@ +NAME + gcloud beta network-connectivity hubs reject-spoke-update - reject a + proposal to update a spoke in a hub + +SYNOPSIS + gcloud beta network-connectivity hubs reject-spoke-update HUB --spoke=SPOKE + --spoke-etag=SPOKE_ETAG [--async] [--details=DETAILS] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Reject a VPC spoke update proposal. By rejecting a spoke update, you + prevent updating the connectivity between the associated VPC network and + any other VPC networks that are attached to the same hub. + +EXAMPLES + To reject updating a spoke named my-spoke with etag in a hub named my-hub + with reason my-reason, run: + + $ gcloud beta network-connectivity hubs reject-spoke-update my-hub \ + --spoke="projects/spoke-project/locations/global/hubs/my-spoke" \ + --spoke-etag=etag --details=my-reason + +POSITIONAL ARGUMENTS + Hub resource - Name of the hub to reject the spoke update. This represents + a Cloud resource. (NOTE) Some attributes are not given arguments in this + group but can be set in other ways. + + To set the project attribute: + ◆ provide the argument hub on the command line with a fully specified + name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + HUB + ID of the hub or fully qualified identifier for the hub. + + To set the hub attribute: + ▸ provide the argument hub on the command line. + +REQUIRED FLAGS + --spoke=SPOKE + URI of the spoke to reject update + + --spoke-etag=SPOKE_ETAG + Etag of the spoke to reject update + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --details=DETAILS + Additional details behind the rejection + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the networkconnectivity/v1 API. The full documentation + for this API can be found at: + https://cloud.google.com/network-connectivity/docs/reference/networkconnectivity/rest + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud network-connectivity hubs reject-spoke-update + diff --git a/gcloud/beta/network-connectivity/spokes/linked-producer-vpc-network/update b/gcloud/beta/network-connectivity/spokes/linked-producer-vpc-network/update index 726e0e321..687e4671a 100644 --- a/gcloud/beta/network-connectivity/spokes/linked-producer-vpc-network/update +++ b/gcloud/beta/network-connectivity/spokes/linked-producer-vpc-network/update @@ -4,7 +4,8 @@ NAME SYNOPSIS gcloud beta network-connectivity spokes linked-producer-vpc-network update - SPOKE [--async] [--description=DESCRIPTION] [--global] + SPOKE [--async] [--description=DESCRIPTION] + [--exclude-export-ranges=[CIDR_RANGE,...]] [--global] [--include-export-ranges=[CIDR_RANGE,...]] [--update-labels=[KEY=VALUE,...]] [--clear-labels | --remove-labels=[KEY,...]] [GCLOUD_WIDE_FLAG ...] @@ -51,12 +52,14 @@ FLAGS --description=DESCRIPTION New description of the spoke. + --exclude-export-ranges=[CIDR_RANGE,...] + New exclude export ranges of the spoke. + --global Indicates that the spoke is global. --include-export-ranges=[CIDR_RANGE,...] - Only allows adding ALL_IPV6_RANGES to include export ranges or removing - ALL_IPV6_RANGES from include export ranges. + New include export ranges of the spoke. --update-labels=[KEY=VALUE,...] List of label KEY=VALUE pairs to update. If a label exists, its value diff --git a/gcloud/beta/network-connectivity/spokes/linked-vpc-network/update b/gcloud/beta/network-connectivity/spokes/linked-vpc-network/update index 6b071d09e..dd307839d 100644 --- a/gcloud/beta/network-connectivity/spokes/linked-vpc-network/update +++ b/gcloud/beta/network-connectivity/spokes/linked-vpc-network/update @@ -4,7 +4,8 @@ NAME SYNOPSIS gcloud beta network-connectivity spokes linked-vpc-network update SPOKE - [--async] [--description=DESCRIPTION] [--global] + [--async] [--description=DESCRIPTION] + [--exclude-export-ranges=[CIDR_RANGE,...]] [--global] [--include-export-ranges=[CIDR_RANGE,...]] [--update-labels=[KEY=VALUE,...]] [--clear-labels | --remove-labels=[KEY,...]] [GCLOUD_WIDE_FLAG ...] @@ -50,12 +51,14 @@ FLAGS --description=DESCRIPTION New description of the spoke. + --exclude-export-ranges=[CIDR_RANGE,...] + New exclude export ranges of the spoke. + --global Indicates that the spoke is global. --include-export-ranges=[CIDR_RANGE,...] - Only allows adding ALL_IPV6_RANGES to include export ranges or removing - ALL_IPV6_RANGES from include export ranges. + New include export ranges of the spoke. --update-labels=[KEY=VALUE,...] List of label KEY=VALUE pairs to update. If a label exists, its value diff --git a/gcloud/beta/run/deploy b/gcloud/beta/run/deploy index 249274b58..71c584fa8 100644 --- a/gcloud/beta/run/deploy +++ b/gcloud/beta/run/deploy @@ -48,9 +48,6 @@ SYNOPSIS --update-secrets=[KEY=VALUE,...] --command=[COMMAND,...] | --function=FUNCTION --image=IMAGE --source=SOURCE] [--binary-authorization=POLICY | --clear-binary-authorization] - [--clear-config-maps | --set-config-maps=[KEY=VALUE,...] - | --remove-config-maps=[KEY,...] - --update-config-maps=[KEY=VALUE,...]] [--clear-encryption-key-shutdown-hours | --encryption-key-shutdown-hours=ENCRYPTION_KEY_SHUTDOWN_HOURS] [--clear-key | --key=KEY] @@ -661,37 +658,6 @@ FLAGS --clear-binary-authorization Remove any previously set Binary Authorization policy. - Specify config map to mount or provide as environment variables. Keys - starting with a forward slash '/' are mount paths. All other keys - correspond to environment variables. The values associated with each of - these should be in the form CONFIG_MAP_NAME:KEY_IN_CONFIG_MAP; you may - omit the key within the config map to specify a mount of all keys within - the config map. For example: - '--update-config-maps=/my/path=myconfig,ENV=otherconfig:key.json' will - create a volume with config map 'myconfig' and mount that volume at - '/my/path'. Because no config map key was specified, all keys in - 'myconfig' will be included. An environment variable named ENV will also - be created whose value is the value of 'key.json' in 'otherconfig. Not - supported on the fully managed version of Cloud Run. - - At most one of these can be specified: - - --clear-config-maps - Remove all config-maps. - - --set-config-maps=[KEY=VALUE,...] - List of key-value pairs to set as config-maps. All existing - config-maps will be removed first. - - Only --update-config-maps and --remove-config-maps can be used together. - If both are specified, --remove-config-maps will be applied first. - - --remove-config-maps=[KEY,...] - List of config-maps to be removed. - - --update-config-maps=[KEY=VALUE,...] - List of key-value pairs to set as config-maps. - At most one of these can be specified: --clear-encryption-key-shutdown-hours diff --git a/gcloud/beta/run/multi-region-services/update b/gcloud/beta/run/multi-region-services/update index f3def3d9f..fec08476a 100644 --- a/gcloud/beta/run/multi-region-services/update +++ b/gcloud/beta/run/multi-region-services/update @@ -31,17 +31,16 @@ SYNOPSIS --clear-volumes --remove-volume=[VOLUME,...]] [--add-volume-mount=[volume=NAME,mount-path=MOUNT_PATH,...] --args=[ARG,...] --clear-volume-mounts --command=[COMMAND,...] - --cpu=CPU --depends-on=[CONTAINER,...] --image=IMAGE --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,...] + --cpu=CPU --depends-on=[CONTAINER,...] --image=IMAGE + --liveness-probe=[KEY=VALUE,...] --memory=MEMORY --port=PORT + --remove-volume-mount=[MOUNT_PATH,...] + --startup-probe=[KEY=VALUE,...] --[no-]use-http2 --clear-env-vars + | --env-vars-file=FILE_PATH | --set-env-vars=[KEY=VALUE,...] + | --remove-env-vars=[KEY,...] --update-env-vars=[KEY=VALUE,...] --clear-secrets | --set-secrets=[KEY=VALUE,...] | --remove-secrets=[KEY,...] --update-secrets=[KEY=VALUE,...]] [--binary-authorization=POLICY | --clear-binary-authorization] - [--clear-config-maps | --set-config-maps=[KEY=VALUE,...] - | --remove-config-maps=[KEY,...] - --update-config-maps=[KEY=VALUE,...]] [--clear-encryption-key-shutdown-hours | --encryption-key-shutdown-hours=ENCRYPTION_KEY_SHUTDOWN_HOURS] [--clear-key | --key=KEY] @@ -370,6 +369,30 @@ FLAGS Name of the container image to deploy (e.g. us-docker.pkg.dev/cloudrun/container/hello:latest). + --liveness-probe=[KEY=VALUE,...] + Comma separated settings for liveness probe in the form KEY=VALUE. + Each key stands for a field of the probe described in + https://cloud.google.com/run/docs/reference/rest/v1/Container#Probe. + Currently supported keys are: + + + initialDelaySeconds: integer + + timeoutSeconds: integer + + periodSeconds: integer + + failureThreshold: integer + + httpGet.port: integer + + httpGet.path: string + + grpc.port: integer + + grpc.service: string + + For example, to set a probe with 10s timeout and HTTP probe + requests sent to 8080 port of the container: + + $ --liveness-probe=timeoutSeconds=10,httpGet.port=8080 + + To remove existing probe: + + $ --liveness-probe="" + --memory=MEMORY Set a memory limit. Ex: 1024Mi, 4Gi. @@ -385,6 +408,31 @@ FLAGS Removes the volume mounted at the specified path from the current container. + --startup-probe=[KEY=VALUE,...] + Comma separated settings for startup probe in the form KEY=VALUE. + Each key stands for a field of the probe described in + https://cloud.google.com/run/docs/reference/rest/v1/Container#Probe. + Currently supported keys are: + + + initialDelaySeconds: integer + + timeoutSeconds: integer + + periodSeconds: integer + + failureThreshold: integer + + httpGet.port: integer + + httpGet.path: string + + grpc.port: integer + + grpc.service: string + + tcpSocket.port: integer + + For example, to set a probe with 10s timeout and HTTP probe + requests sent to 8080 port of the container: + + $ --startup-probe=timeoutSeconds=10,httpGet.port=8080 + + To remove existing probe: + + $ --startup-probe="" + --[no-]use-http2 Whether to use HTTP/2 for connections to the service. Use --use-http2 to enable and --no-use-http2 to disable. @@ -452,37 +500,6 @@ FLAGS --clear-binary-authorization Remove any previously set Binary Authorization policy. - Specify config map to mount or provide as environment variables. Keys - starting with a forward slash '/' are mount paths. All other keys - correspond to environment variables. The values associated with each of - these should be in the form CONFIG_MAP_NAME:KEY_IN_CONFIG_MAP; you may - omit the key within the config map to specify a mount of all keys within - the config map. For example: - '--update-config-maps=/my/path=myconfig,ENV=otherconfig:key.json' will - create a volume with config map 'myconfig' and mount that volume at - '/my/path'. Because no config map key was specified, all keys in - 'myconfig' will be included. An environment variable named ENV will also - be created whose value is the value of 'key.json' in 'otherconfig. Not - supported on the fully managed version of Cloud Run. - - At most one of these can be specified: - - --clear-config-maps - Remove all config-maps. - - --set-config-maps=[KEY=VALUE,...] - List of key-value pairs to set as config-maps. All existing - config-maps will be removed first. - - Only --update-config-maps and --remove-config-maps can be used together. - If both are specified, --remove-config-maps will be applied first. - - --remove-config-maps=[KEY,...] - List of config-maps to be removed. - - --update-config-maps=[KEY=VALUE,...] - List of key-value pairs to set as config-maps. - At most one of these can be specified: --clear-encryption-key-shutdown-hours diff --git a/gcloud/beta/run/services/update b/gcloud/beta/run/services/update index 37c405d39..e5d3f35de 100644 --- a/gcloud/beta/run/services/update +++ b/gcloud/beta/run/services/update @@ -39,9 +39,6 @@ SYNOPSIS | --set-secrets=[KEY=VALUE,...] | --remove-secrets=[KEY,...] --update-secrets=[KEY=VALUE,...]] [--binary-authorization=POLICY | --clear-binary-authorization] - [--clear-config-maps | --set-config-maps=[KEY=VALUE,...] - | --remove-config-maps=[KEY,...] - --update-config-maps=[KEY=VALUE,...]] [--clear-encryption-key-shutdown-hours | --encryption-key-shutdown-hours=ENCRYPTION_KEY_SHUTDOWN_HOURS] [--clear-key | --key=KEY] @@ -533,37 +530,6 @@ FLAGS --clear-binary-authorization Remove any previously set Binary Authorization policy. - Specify config map to mount or provide as environment variables. Keys - starting with a forward slash '/' are mount paths. All other keys - correspond to environment variables. The values associated with each of - these should be in the form CONFIG_MAP_NAME:KEY_IN_CONFIG_MAP; you may - omit the key within the config map to specify a mount of all keys within - the config map. For example: - '--update-config-maps=/my/path=myconfig,ENV=otherconfig:key.json' will - create a volume with config map 'myconfig' and mount that volume at - '/my/path'. Because no config map key was specified, all keys in - 'myconfig' will be included. An environment variable named ENV will also - be created whose value is the value of 'key.json' in 'otherconfig. Not - supported on the fully managed version of Cloud Run. - - At most one of these can be specified: - - --clear-config-maps - Remove all config-maps. - - --set-config-maps=[KEY=VALUE,...] - List of key-value pairs to set as config-maps. All existing - config-maps will be removed first. - - Only --update-config-maps and --remove-config-maps can be used together. - If both are specified, --remove-config-maps will be applied first. - - --remove-config-maps=[KEY,...] - List of config-maps to be removed. - - --update-config-maps=[KEY=VALUE,...] - List of key-value pairs to set as config-maps. - At most one of these can be specified: --clear-encryption-key-shutdown-hours diff --git a/gcloud/beta/spanner/databases/execute-sql b/gcloud/beta/spanner/databases/execute-sql index 2bf5d2a0d..8d959197e 100644 --- a/gcloud/beta/spanner/databases/execute-sql +++ b/gcloud/beta/spanner/databases/execute-sql @@ -78,8 +78,14 @@ OPTIONAL FLAGS Returns only the query plan, without any result rows or execution statistics information. PROFILE - Returns both the query plan and the execution statistics along with - the result rows. + Returns the query plan, overall execution statistics, + operator-level execution statistics, along with the result rows. + WITH_PLAN_AND_STATS + Returns the query plan, overall (but not operator-level) execution + statistics, along with the results. + WITH_STATS + Returns the overall (but not operator-level) execution statistics + along with the results. --timeout=TIMEOUT; default="10m" Maximum time to wait for the SQL query to complete. See $ gcloud topic diff --git a/gcloud/beta/sql/backups/restore b/gcloud/beta/sql/backups/restore index 8ceddba91..02e315c35 100644 --- a/gcloud/beta/sql/backups/restore +++ b/gcloud/beta/sql/backups/restore @@ -33,6 +33,8 @@ SYNOPSIS [--retained-backups-count=RETAINED_BACKUPS_COUNT] [--retained-transaction-log-days=RETAINED_TRANSACTION_LOG_DAYS] [--ssl-mode=SSL_MODE] [--[no-]storage-auto-increase] + [--storage-provisioned-iops=STORAGE_PROVISIONED_IOPS] + [--storage-provisioned-throughput=STORAGE_PROVISIONED_THROUGHPUT] [--storage-size=STORAGE_SIZE] [--storage-type=STORAGE_TYPE] [--tier=TIER, -t TIER] [--time-zone=TIME_ZONE] [--timeout=TIMEOUT; default=3600] @@ -308,6 +310,14 @@ OPTIONAL FLAGS --storage-auto-increase to enable and --no-storage-auto-increase to disable. + --storage-provisioned-iops=STORAGE_PROVISIONED_IOPS + Indicates how many IOPS to provision for the data disk. This sets the + number of I/O operations per second that the disk can handle. + + --storage-provisioned-throughput=STORAGE_PROVISIONED_THROUGHPUT + Indicates how much throughput to provision for the data disk. This sets + the throughput in MB per second that the disk can handle. + --storage-size=STORAGE_SIZE Amount of storage allocated to the instance. Must be an integer number of GB. The default is 10GB. Information on storage limits can be found diff --git a/gcloud/beta/sql/instances/create b/gcloud/beta/sql/instances/create index b768ba064..9a51f6439 100644 --- a/gcloud/beta/sql/instances/create +++ b/gcloud/beta/sql/instances/create @@ -13,15 +13,18 @@ SYNOPSIS [--availability-type=AVAILABILITY_TYPE] [--no-backup] [--backup-location=BACKUP_LOCATION] [--backup-start-time=BACKUP_START_TIME] [--cascadable-replica] - [--collation=COLLATION] [--connector-enforcement=CONNECTOR_ENFORCEMENT] - [--cpu=CPU] [--custom-subject-alternative-names=DNS,[DNS,[DNS]]] + [--collation=COLLATION] + [--connection-pool-flags=FLAG=VALUE,[FLAG=VALUE,...]] + [--connector-enforcement=CONNECTOR_ENFORCEMENT] [--cpu=CPU] + [--custom-subject-alternative-names=DNS,[DNS,[DNS]]] [--database-flags=FLAG=VALUE,[FLAG=VALUE,...]] [--database-version=DATABASE_VERSION; default="MYSQL_8_0"] [--[no-]deletion-protection] [--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] - [--edition=EDITION] [--enable-bin-log] [--[no-]enable-data-cache] + [--edition=EDITION] [--enable-bin-log] + [--[no-]enable-connection-pooling] [--[no-]enable-data-cache] [--[no-]enable-dataplex-integration] [--[no-]enable-google-ml-integration] [--enable-google-private-path] [--enable-password-policy] [--enable-point-in-time-recovery] @@ -46,12 +49,15 @@ SYNOPSIS [--[no-]recreate-replicas-on-primary-crash] [--replica-type=REPLICA_TYPE] [--replication=REPLICATION] [--replication-lag-max-seconds-for-recreate=REPLICATION_LAG_MAX_SECONDS_FOR_RECREATE] - [--require-ssl] [--retained-backups-count=RETAINED_BACKUPS_COUNT] + [--require-ssl] [--[no-]retain-backups-on-delete] + [--retained-backups-count=RETAINED_BACKUPS_COUNT] [--retained-transaction-log-days=RETAINED_TRANSACTION_LOG_DAYS] [--root-password=ROOT_PASSWORD] [--server-ca-mode=SERVER_CA_MODE] [--server-ca-pool=SERVER_CA_POOL] [--ssl-mode=SSL_MODE] [--[no-]storage-auto-increase] [--storage-auto-increase-limit=STORAGE_AUTO_INCREASE_LIMIT] + [--storage-provisioned-iops=STORAGE_PROVISIONED_IOPS] + [--storage-provisioned-throughput=STORAGE_PROVISIONED_THROUGHPUT] [--storage-size=STORAGE_SIZE] [--storage-type=STORAGE_TYPE] [--tags=TAG=VALUE,[TAG=VALUE,...]] [--threads-per-core=THREADS_PER_CORE] [--tier=TIER, -t TIER] @@ -77,28 +83,28 @@ DESCRIPTION (BETA) Creates a new Cloud SQL instance. EXAMPLES - To create a MySQL 5.7 instance with ID prod-instance that has 2 CPUs, 4 GB + To create a MySQL 8.0 instance with ID prod-instance that has 2 CPUs, 4 GB of RAM, and is in the region us-central1 (a zone will be auto-assigned), where the 'root' user has its password set to password123, run: $ gcloud beta sql instances create prod-instance \ - --database-version=MYSQL_5_7 --cpu=2 --memory=4GB \ + --database-version=MYSQL_8_0 --cpu=2 --memory=4GB \ --region=us-central1 --root-password=password123 - To create a Postgres 9.6 instance with ID prod-instance that has 2 CPUs, 8 + To create a Postgres 15 instance with ID prod-instance that has 2 CPUs, 8 GiB of RAM, and is in the zone us-central1-a, where the 'postgres' user has its password set to password123, run: $ gcloud beta sql instances create prod-instance \ - --database-version=POSTGRES_9_6 --cpu=2 --memory=8GiB \ + --database-version=POSTGRES_15 --cpu=2 --memory=8GiB \ --zone=us-central1-a --root-password=password123 - To create a SQL Server 2017 Express instance with ID prod-instance that has + To create a SQL Server 2022 Express instance with ID prod-instance that has 2 CPUs, 3840MiB of RAM, and is in the zone us-central1-a, where the 'sqlserver' user has its password set to password123, run: $ gcloud beta sql instances create prod-instance \ - --database-version=SQLSERVER_2017_EXPRESS --cpu=2 \ + --database-version=SQLSERVER_2022_EXPRESS --cpu=2 \ --memory=3840MiB --zone=us-central1-a \ --root-password=password123 @@ -185,6 +191,12 @@ FLAGS Cloud SQL server-level collation setting, which specifies the set of rules for comparing characters in a character set. + --connection-pool-flags=FLAG=VALUE,[FLAG=VALUE,...] + Comma-separated list of connection pool flags to set on the instance + connection pool. Use an equals sign to separate flag name and value. + View the Instance Resource API for allowed flags. (e.g., + --connection-pool-flags max_pool_size=1000,max_client_connections=2000) + --connector-enforcement=CONNECTOR_ENFORCEMENT Cloud SQL Connector enforcement mode. It determines how Cloud SQL Connectors are used in the connection. See the list of modes here @@ -250,6 +262,11 @@ FLAGS fraction of a second. Must have automatic backups enabled to use. Make sure storage can support at least 7 days of logs. + --[no-]enable-connection-pooling + Enable connection pooling for the instance. Use + --enable-connection-pooling to enable and + --no-enable-connection-pooling to disable. + --[no-]enable-data-cache Enable use of data cache for accelerated read performance. This flag is only available for Enterprise_Plus edition instances. Use @@ -449,6 +466,11 @@ FLAGS --require-ssl Specified if users connecting over IP must use SSL. + --[no-]retain-backups-on-delete + Retain automated/ondemand backups of the instance after the instance is + deleted. Use --retain-backups-on-delete to enable and + --no-retain-backups-on-delete to disable. + --retained-backups-count=RETAINED_BACKUPS_COUNT How many backups to keep. The valid range is between 1 and 365. Default value is 7 for Enterprise edition instances. For Enterprise_Plus, @@ -507,6 +529,14 @@ FLAGS increases to your capacity will stop once this limit has been reached. Default capacity is unlimited. + --storage-provisioned-iops=STORAGE_PROVISIONED_IOPS + Indicates how many IOPS to provision for the data disk. This sets the + number of I/O operations per second that the disk can handle. + + --storage-provisioned-throughput=STORAGE_PROVISIONED_THROUGHPUT + Indicates how much throughput to provision for the data disk. This sets + the throughput in MB per second that the disk can handle. + --storage-size=STORAGE_SIZE Amount of storage allocated to the instance. Must be an integer number of GB. The default is 10GB. Information on storage limits can be found diff --git a/gcloud/beta/sql/instances/patch b/gcloud/beta/sql/instances/patch index 1cdd1cdd8..bce2d4b69 100644 --- a/gcloud/beta/sql/instances/patch +++ b/gcloud/beta/sql/instances/patch @@ -17,7 +17,8 @@ SYNOPSIS [--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] [--diff] - [--edition=EDITION] [--[no-]enable-bin-log] [--[no-]enable-data-cache] + [--edition=EDITION] [--[no-]enable-bin-log] + [--[no-]enable-connection-pooling] [--[no-]enable-data-cache] [--[no-]enable-database-replication] [--[no-]enable-dataplex-integration] [--[no-]enable-google-ml-integration] @@ -46,9 +47,12 @@ SYNOPSIS [--[no-]recreate-replicas-on-primary-crash] [--remove-deny-maintenance-period] [--replication=REPLICATION] [--replication-lag-max-seconds-for-recreate=REPLICATION_LAG_MAX_SECONDS_FOR_RECREATE] - [--[no-]require-ssl] [--simulate-maintenance-event] - [--ssl-mode=SSL_MODE] [--[no-]storage-auto-increase] + [--[no-]require-ssl] [--[no-]retain-backups-on-delete] + [--simulate-maintenance-event] [--ssl-mode=SSL_MODE] + [--[no-]storage-auto-increase] [--storage-auto-increase-limit=STORAGE_AUTO_INCREASE_LIMIT] + [--storage-provisioned-iops=STORAGE_PROVISIONED_IOPS] + [--storage-provisioned-throughput=STORAGE_PROVISIONED_THROUGHPUT] [--storage-size=STORAGE_SIZE] [--switch-transaction-logs-to-cloud-storage] [--threads-per-core=THREADS_PER_CORE] [--tier=TIER, -t TIER] @@ -59,6 +63,8 @@ SYNOPSIS [--authorized-gae-apps=APP,[APP,...] | --clear-gae-apps] [--authorized-networks=NETWORK,[NETWORK,...] | --clear-authorized-networks] + [--clear-connection-pool-flags + | --connection-pool-flags=FLAG=VALUE,[FLAG=VALUE,...]] [--clear-custom-subject-alternative-names | --custom-subject-alternative-names=DNS,[DNS,[DNS]]] [--clear-database-flags | --database-flags=FLAG=VALUE,[FLAG=VALUE,...]] @@ -191,6 +197,11 @@ FLAGS sure storage can support at least 7 days of logs. Use --enable-bin-log to enable and --no-enable-bin-log to disable. + --[no-]enable-connection-pooling + Enable connection pooling for the instance. Use + --enable-connection-pooling to enable and + --no-enable-connection-pooling to disable. + --[no-]enable-data-cache Enable use of data cache for accelerated read performance. This flag is only available for Enterprise_Plus edition instances. Use @@ -386,6 +397,11 @@ FLAGS mysqld should default to 'REQUIRE X509' for users connecting over IP. Use --require-ssl to enable and --no-require-ssl to disable. + --[no-]retain-backups-on-delete + Retain automated/ondemand backups of the instance after the instance is + deleted. Use --retain-backups-on-delete to enable and + --no-retain-backups-on-delete to disable. + --simulate-maintenance-event Simulate a maintenance event without changing the version. Only applicable to instances that support near-zero downtime planned @@ -418,6 +434,14 @@ FLAGS increases to your capacity will stop once this limit has been reached. Default capacity is unlimited. + --storage-provisioned-iops=STORAGE_PROVISIONED_IOPS + Indicates how many IOPS to provision for the data disk. This sets the + number of I/O operations per second that the disk can handle. + + --storage-provisioned-throughput=STORAGE_PROVISIONED_THROUGHPUT + Indicates how much throughput to provision for the data disk. This sets + the throughput in MB per second that the disk can handle. + --storage-size=STORAGE_SIZE Amount of storage allocated to the instance. Must be an integer number of GB. The default is 10GB. Information on storage limits can be found @@ -496,6 +520,18 @@ FLAGS Clear the list of external networks that are allowed to connect to the instance. + At most one of these can be specified: + + --clear-connection-pool-flags + This will clear the connection pool flags set on the instance. + + --connection-pool-flags=FLAG=VALUE,[FLAG=VALUE,...] + Comma-separated list of connection pool flags to set on the instance + connection pool. Use an equals sign to separate flag name and value. + View the Instance Resource API for allowed flags. (e.g., + --connection-pool-flags + max_pool_size=1000,max_client_connections=2000) + At most one of these can be specified: --clear-custom-subject-alternative-names diff --git a/gcloud/certificate-manager/certificates/list b/gcloud/certificate-manager/certificates/list index 41c79119d..d145622b8 100644 --- a/gcloud/certificate-manager/certificates/list +++ b/gcloud/certificate-manager/certificates/list @@ -22,7 +22,8 @@ FLAGS To set the project attribute: ◆ provide the argument --location on the command line with a fully specified name; - ◆ default value of location is [global] with a fully specified name; + ◆ if left empty, will use the wildcard '-' to list all locations with a + fully specified name; ◆ provide the argument --project on the command line; ◆ set the property core/project. @@ -31,7 +32,7 @@ FLAGS To set the location attribute: ▸ provide the argument --location on the command line; - ▸ default value of location is [global]. + ▸ if left empty, will use the wildcard '-' to list all locations. LIST COMMAND FLAGS --filter=EXPRESSION diff --git a/gcloud/certificate-manager/dns-authorizations/list b/gcloud/certificate-manager/dns-authorizations/list index 2292096c3..856dd5cf8 100644 --- a/gcloud/certificate-manager/dns-authorizations/list +++ b/gcloud/certificate-manager/dns-authorizations/list @@ -16,14 +16,15 @@ EXAMPLES $ gcloud certificate-manager dns-authorizations list FLAGS - Location resource - The location (defaults to global) of the resources. - This represents a Cloud resource. (NOTE) Some attributes are not given + Location resource - The location (defaults to '-') of the resources. This + represents a Cloud resource. (NOTE) Some attributes are not given arguments in this group but can be set in other ways. To set the project attribute: ◆ provide the argument --location on the command line with a fully specified name; - ◆ default value of location is [global] with a fully specified name; + ◆ if left empty, will use the wildcard '-' to list all locations with a + fully specified name; ◆ provide the argument --project on the command line; ◆ set the property core/project. @@ -32,7 +33,7 @@ FLAGS To set the location attribute: ▸ provide the argument --location on the command line; - ▸ default value of location is [global]. + ▸ if left empty, will use the wildcard '-' to list all locations. LIST COMMAND FLAGS --filter=EXPRESSION diff --git a/gcloud/certificate-manager/issuance-configs/list b/gcloud/certificate-manager/issuance-configs/list index 95f61186c..c00fd8125 100644 --- a/gcloud/certificate-manager/issuance-configs/list +++ b/gcloud/certificate-manager/issuance-configs/list @@ -16,14 +16,15 @@ EXAMPLES $ gcloud certificate-manager issuance-configs list FLAGS - Location resource - Location (defaults to global) of the resources. This + Location resource - The location (defaults to '-') of the resources. This represents a Cloud resource. (NOTE) Some attributes are not given arguments in this group but can be set in other ways. To set the project attribute: ◆ provide the argument --location on the command line with a fully specified name; - ◆ default value of location is [global] with a fully specified name; + ◆ if left empty, will use the wildcard '-' to list all locations with a + fully specified name; ◆ provide the argument --project on the command line; ◆ set the property core/project. @@ -32,7 +33,7 @@ FLAGS To set the location attribute: ▸ provide the argument --location on the command line; - ▸ default value of location is [global]. + ▸ if left empty, will use the wildcard '-' to list all locations. LIST COMMAND FLAGS --filter=EXPRESSION diff --git a/gcloud/certificate-manager/trust-configs/list b/gcloud/certificate-manager/trust-configs/list index 02b0f4687..7df3b617d 100644 --- a/gcloud/certificate-manager/trust-configs/list +++ b/gcloud/certificate-manager/trust-configs/list @@ -16,14 +16,15 @@ EXAMPLES $ gcloud certificate-manager trust-configs list FLAGS - Location resource - The location (defaults to global) of the resources. - This represents a Cloud resource. (NOTE) Some attributes are not given + Location resource - The location (defaults to '-') of the resources. This + represents a Cloud resource. (NOTE) Some attributes are not given arguments in this group but can be set in other ways. To set the project attribute: ◆ provide the argument --location on the command line with a fully specified name; - ◆ default value of location is [global] with a fully specified name; + ◆ if left empty, will use the wildcard '-' to list all locations with a + fully specified name; ◆ provide the argument --project on the command line; ◆ set the property core/project. @@ -32,7 +33,7 @@ FLAGS To set the location attribute: ▸ provide the argument --location on the command line; - ▸ default value of location is [global]. + ▸ if left empty, will use the wildcard '-' to list all locations. LIST COMMAND FLAGS --filter=EXPRESSION diff --git a/gcloud/compute/disks/convert b/gcloud/compute/disks/convert index 8593c5bbf..601d1470c 100644 --- a/gcloud/compute/disks/convert +++ b/gcloud/compute/disks/convert @@ -16,11 +16,11 @@ DESCRIPTION https://cloud.google.com/sdk/gcloud/reference/compute/disks/convert. EXAMPLES - The following command converts a PD Standard disk to a Hyperdisk - Throughput: + The following command converts a Persistent Disk volume to a Hyperdisk + Balanced volume: $ gcloud compute disks convert my-disk-1 --zone=ZONE \ - --target-disk-type=hyperdisk-throughput + --target-disk-type=hyperdisk-balanced POSITIONAL ARGUMENTS DISK_NAME diff --git a/gcloud/compute/instances/help b/gcloud/compute/instances/help index 9d81287fb..17ccb34ef 100644 --- a/gcloud/compute/instances/help +++ b/gcloud/compute/instances/help @@ -130,6 +130,9 @@ COMMANDS remove-tags Remove tags from Compute Engine virtual machine instances. + report-host-as-faulty + Report a host as faulty to start the repair process. + reset Reset a virtual machine instance. diff --git a/gcloud/compute/instances/report-host-as-faulty b/gcloud/compute/instances/report-host-as-faulty new file mode 100644 index 000000000..e3e138fc8 --- /dev/null +++ b/gcloud/compute/instances/report-host-as-faulty @@ -0,0 +1,79 @@ +NAME + gcloud compute instances report-host-as-faulty - report a host as faulty to + start the repair process + +SYNOPSIS + gcloud compute instances report-host-as-faulty INSTANCE_NAME + --disruption-schedule=DISRUPTION_SCHEDULE + --fault-reasons=[behavior=BEHAVIOR],[description=DESCRIPTION] + [--zone=ZONE] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + gcloud compute instances report-host-as-faulty is used to report a host as + faulty to start the repair process. + +EXAMPLES + To report a host as faulty for an instance named test-instance, run: + + $ gcloud compute instances report-host-as-faulty test-instance \ + --fault-reasons=behavior=SILENT_DATA_CORRUPTION,\ + description="affecting our ML job" --disruption-schedule=IMMEDIATE + +POSITIONAL ARGUMENTS + INSTANCE_NAME + Name of the instance to operate on. For details on valid instance + names, refer to the criteria documented under the field 'name' at: + https://cloud.google.com/compute/docs/reference/rest/v1/instances + +REQUIRED FLAGS + --disruption-schedule=DISRUPTION_SCHEDULE + Specifies the timing for initiating the fault reporting process. The + default value is ['IMMEDIATE'] which initiates the process right away. + DISRUPTION_SCHEDULE must be (only one value is supported): IMMEDIATE. + + --fault-reasons=[behavior=BEHAVIOR],[description=DESCRIPTION] + Specified and can include one or more of the following types: + ['BEHAVIOR_UNSPECIFIED', 'PERFORMANCE', 'SILENT_DATA_CORRUPTION', + 'UNRECOVERABLE_GPU_ERROR']. This helps categorize the nature of the + fault being reported. + +OPTIONAL FLAGS + --zone=ZONE + Zone of the instance to operate on. If not specified, you might be + prompted to select a zone (interactive mode only). gcloud attempts to + identify the appropriate zone by searching for resources in your + currently active project. If the zone cannot be determined, gcloud + prompts you for a selection with all available Google Cloud Platform + zones. + + To avoid prompting when this flag is omitted, the user can set the + compute/zone property: + + $ gcloud config set compute/zone ZONE + + A list of zones can be fetched by running: + + $ gcloud compute zones list + + To unset the property, run: + + $ gcloud config unset compute/zone + + Alternatively, the zone can be stored in the environment variable + CLOUDSDK_COMPUTE_ZONE. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + These variants are also available: + + $ gcloud alpha compute instances report-host-as-faulty + + $ gcloud beta compute instances report-host-as-faulty + diff --git a/gcloud/compute/networks/subnets/create b/gcloud/compute/networks/subnets/create index 96868374c..7c28529f0 100644 --- a/gcloud/compute/networks/subnets/create +++ b/gcloud/compute/networks/subnets/create @@ -5,7 +5,7 @@ NAME SYNOPSIS gcloud compute networks subnets create NAME --network=NETWORK [--description=DESCRIPTION] [--enable-flow-logs] - [--enable-private-ip-google-access] + [--enable-private-ip-google-access] [--ip-collection=IP_COLLECTION] [--ipv6-access-type=IPV6_ACCESS_TYPE] [--logging-aggregation-interval=LOGGING_AGGREGATION_INTERVAL] [--logging-filter-expr=LOGGING_FILTER_EXPR] @@ -51,6 +51,11 @@ OPTIONAL FLAGS Enable/disable access to Google Cloud APIs from this subnet for instances without a public ip address. + --ip-collection=IP_COLLECTION + Resource reference to a public delegated prefix. The + PublicDelegatedPrefix must be a sub-prefix in + EXTERNAL_IPV6_SUBNETWORK_CREATION mode. + --ipv6-access-type=IPV6_ACCESS_TYPE IPv6 access type can be specified only when the subnet is created, or when the subnet is first updated to have a stack type of IPV4_IPV6. diff --git a/gcloud/compute/networks/subnets/update b/gcloud/compute/networks/subnets/update index 1ac0f20fe..1cc3181c7 100644 --- a/gcloud/compute/networks/subnets/update +++ b/gcloud/compute/networks/subnets/update @@ -6,7 +6,7 @@ SYNOPSIS gcloud compute networks subnets update NAME [--add-secondary-ranges-with-reserved-internal-range=RANGE_NAME=INTERNAL_RANGE_URL, [...]] [--drain-timeout=DRAIN_TIMEOUT; default="0s"] - [--ipv6-access-type=IPV6_ACCESS_TYPE] + [--ip-collection=IP_COLLECTION] [--ipv6-access-type=IPV6_ACCESS_TYPE] [--logging-aggregation-interval=LOGGING_AGGREGATION_INTERVAL] [--logging-filter-expr=LOGGING_FILTER_EXPR] [--logging-flow-sampling=LOGGING_FLOW_SAMPLING] @@ -56,6 +56,11 @@ FLAGS availability of proxies for load balancing. The drain timeout is only applicable when the [--role=ACTIVE] flag is being used. + --ip-collection=IP_COLLECTION + Resource reference to a public delegated prefix. The + PublicDelegatedPrefix must be a sub-prefix in + EXTERNAL_IPV6_SUBNETWORK_CREATION mode. + --ipv6-access-type=IPV6_ACCESS_TYPE IPv6 access type can be specified only when the subnet is created, or when the subnet is first updated to have a stack type of IPV4_IPV6. diff --git a/gcloud/compute/public-delegated-prefixes/create b/gcloud/compute/public-delegated-prefixes/create index 1034c80f7..78fac71c8 100644 --- a/gcloud/compute/public-delegated-prefixes/create +++ b/gcloud/compute/public-delegated-prefixes/create @@ -48,7 +48,8 @@ OPTIONAL FLAGS --mode=MODE Specifies the mode of this IPv6 PDP. MODE must be one of: delegation, - external-ipv6-forwarding-rule-creation. + external-ipv6-forwarding-rule-creation, + external-ipv6-subnetwork-creation. At most one of these can be specified: diff --git a/gcloud/compute/public-delegated-prefixes/delegated-sub-prefixes/create b/gcloud/compute/public-delegated-prefixes/delegated-sub-prefixes/create index d813a3d77..7bf88a3b6 100644 --- a/gcloud/compute/public-delegated-prefixes/delegated-sub-prefixes/create +++ b/gcloud/compute/public-delegated-prefixes/delegated-sub-prefixes/create @@ -56,7 +56,8 @@ OPTIONAL FLAGS --mode=MODE Specifies the mode of this IPv6 PDP. MODE must be one of: delegation, - external-ipv6-forwarding-rule-creation. + external-ipv6-forwarding-rule-creation, + external-ipv6-subnetwork-creation. --range=RANGE IPv4 range from this public delegated prefix that should be delegated, diff --git a/gcloud/compute/reservations/create b/gcloud/compute/reservations/create index 227039d00..cf1da5b32 100644 --- a/gcloud/compute/reservations/create +++ b/gcloud/compute/reservations/create @@ -7,7 +7,7 @@ SYNOPSIS (--source-instance-template=SOURCE_INSTANCE_TEMPLATE | [--machine-type=MACHINE_TYPE : --accelerator=[count=COUNT],[type=TYPE] - --local-ssd=[interface=INTERFACE],[size=SIZE] + --local-ssd=[count=COUNT],[interface=INTERFACE],[size=SIZE] --min-cpu-platform=MIN_CPU_PLATFORM]) : --require-specific-reservation --resource-policies=[KEY=VALUE,...]) [--description=DESCRIPTION] @@ -96,7 +96,7 @@ REQUIRED FLAGS reservation. Use gcloud compute accelerator-types list to learn about all available accelerator types. - --local-ssd=[interface=INTERFACE],[size=SIZE] + --local-ssd=[count=COUNT],[interface=INTERFACE],[size=SIZE] Manage the size and the interface of local SSD to use. See https://cloud.google.com/compute/docs/disks/local-ssd for more information. @@ -107,6 +107,9 @@ REQUIRED FLAGS higher performance. size The size of the local SSD in base-2 GB. + count + The number of local SSD to use per VM. If you don't specify + this argument, then the default value is 1. --min-cpu-platform=MIN_CPU_PLATFORM Optional minimum CPU platform of the reservation to create. diff --git a/gcloud/container/clusters/create b/gcloud/container/clusters/create index 92c2935b1..a441ea045 100644 --- a/gcloud/container/clusters/create +++ b/gcloud/container/clusters/create @@ -9,6 +9,7 @@ SYNOPSIS gpu-sharing-strategy=GPU_SHARING_STRATEGY, max-shared-clients-per-gpu=MAX_SHARED_CLIENTS_PER_GPU],...]] [--additional-zones=ZONE,[ZONE,...]] [--addons=[ADDON,...]] [--async] + [--auto-monitoring-scope=AUTO_MONITORING_SCOPE] [--autoprovisioning-enable-insecure-kubelet-readonly-port] [--autoprovisioning-network-tags=TAGS,[TAGS,...]] [--autoprovisioning-resource-manager-tags=[KEY=VALUE,...]] @@ -231,6 +232,12 @@ FLAGS Return immediately, without waiting for the operation in progress to complete. + --auto-monitoring-scope=AUTO_MONITORING_SCOPE + Enables Auto-Monitoring for a specific scope within the cluster. ALL: + Enables Auto-Monitoring for all supported workloads within the cluster. + NONE: Disables Auto-Monitoring. AUTO_MONITORING_SCOPE must be one of: + ALL, NONE. + --autoprovisioning-enable-insecure-kubelet-readonly-port Enables the Kubelet's insecure read only port for Autoprovisioned Node Pools. @@ -1242,6 +1249,11 @@ FLAGS kubeletConfig: cpuManagerPolicy: static + memoryManager: + policy: Static + topologyManager: + policy: BestEffort + scope: pod linuxConfig: sysctl: net.core.somaxconn: '2048' @@ -1258,6 +1270,9 @@ FLAGS cpuCFSQuota true or false (enabled by default) cpuCFSQuotaPeriod interval (e.g., '100ms') + memoryManager specify memory manager policy + topologyManager specify topology manager policy + and scope podPidsLimit integer (The value must be greater than or equal to 1024 and less than 4194304.) @@ -1284,6 +1299,17 @@ FLAGS 'fs.mqueue.*', and 'net.*', and sysctls under the groups.) + KEY VALUE + policy either 'Static' or 'None' + + KEY VALUE + policy either 'none' or + 'best-effort' or + 'single-numa-node' or + 'restricted' + scope either 'pod' or + 'container' + List of supported sysctls in 'linuxConfig'. KEY VALUE @@ -1307,7 +1333,7 @@ FLAGS integer tuple net.ipv4.tcp_wmem Any positive integer tuple - net.ipv4.tcp_tw_reuse Must be {0, 1} + net.ipv4.tcp_tw_reuse Must be {0, 1, 2} net.netfilter.nf_conntrack_max Must be between [65536, 4194304] net.netfilter.nf_conntrack_buckets Must be between diff --git a/gcloud/container/clusters/create-auto b/gcloud/container/clusters/create-auto index 4ce7c30a9..bc8fa38e4 100644 --- a/gcloud/container/clusters/create-auto +++ b/gcloud/container/clusters/create-auto @@ -4,6 +4,7 @@ NAME SYNOPSIS gcloud container clusters create-auto NAME [--async] + [--auto-monitoring-scope=AUTO_MONITORING_SCOPE] [--autoprovisioning-enable-insecure-kubelet-readonly-port] [--autoprovisioning-network-tags=TAGS,[TAGS,...]] [--autoprovisioning-resource-manager-tags=[KEY=VALUE,...]] @@ -73,6 +74,12 @@ FLAGS Return immediately, without waiting for the operation in progress to complete. + --auto-monitoring-scope=AUTO_MONITORING_SCOPE + Enables Auto-Monitoring for a specific scope within the cluster. ALL: + Enables Auto-Monitoring for all supported workloads within the cluster. + NONE: Disables Auto-Monitoring. AUTO_MONITORING_SCOPE must be one of: + ALL, NONE. + --autoprovisioning-enable-insecure-kubelet-readonly-port Enables the Kubelet's insecure read only port for Autoprovisioned Node Pools. diff --git a/gcloud/container/clusters/update b/gcloud/container/clusters/update index d22acf737..e593b6870 100644 --- a/gcloud/container/clusters/update +++ b/gcloud/container/clusters/update @@ -49,7 +49,8 @@ SYNOPSIS | --workload-vulnerability-scanning=WORKLOAD_VULNERABILITY_SCANNING | --additional-pod-ipv4-ranges=NAME,[NAME,...] --remove-additional-pod-ipv4-ranges=NAME,[NAME,...] - | --logging=[COMPONENT,...] + | --auto-monitoring-scope=AUTO_MONITORING_SCOPE + --logging=[COMPONENT,...] --monitoring=[COMPONENT,...] --disable-managed-prometheus | --enable-managed-prometheus | --binauthz-evaluation-mode=BINAUTHZ_EVALUATION_MODE @@ -806,6 +807,12 @@ REQUIRED FLAGS $ gcloud container clusters update example-cluster \ --remove-additional-pod-ipv4-ranges=range1,range2 + --auto-monitoring-scope=AUTO_MONITORING_SCOPE + Enables Auto-Monitoring for a specific scope within the cluster. ALL: + Enables Auto-Monitoring for all supported workloads within the + cluster. NONE: Disables Auto-Monitoring. AUTO_MONITORING_SCOPE must + be one of: ALL, NONE. + --logging=[COMPONENT,...] Set the components that have logging enabled. Valid component values are: SYSTEM, WORKLOAD, API_SERVER, CONTROLLER_MANAGER, SCHEDULER, diff --git a/gcloud/container/node-pools/create b/gcloud/container/node-pools/create index 503df09a1..972133372 100644 --- a/gcloud/container/node-pools/create +++ b/gcloud/container/node-pools/create @@ -678,6 +678,11 @@ FLAGS kubeletConfig: cpuManagerPolicy: static + memoryManager: + policy: Static + topologyManager: + policy: BestEffort + scope: pod linuxConfig: sysctl: net.core.somaxconn: '2048' @@ -694,6 +699,9 @@ FLAGS cpuCFSQuota true or false (enabled by default) cpuCFSQuotaPeriod interval (e.g., '100ms') + memoryManager specify memory manager policy + topologyManager specify topology manager policy + and scope podPidsLimit integer (The value must be greater than or equal to 1024 and less than 4194304.) @@ -720,6 +728,17 @@ FLAGS 'fs.mqueue.*', and 'net.*', and sysctls under the groups.) + KEY VALUE + policy either 'Static' or 'None' + + KEY VALUE + policy either 'none' or + 'best-effort' or + 'single-numa-node' or + 'restricted' + scope either 'pod' or + 'container' + List of supported sysctls in 'linuxConfig'. KEY VALUE @@ -743,7 +762,7 @@ FLAGS integer tuple net.ipv4.tcp_wmem Any positive integer tuple - net.ipv4.tcp_tw_reuse Must be {0, 1} + net.ipv4.tcp_tw_reuse Must be {0, 1, 2} net.netfilter.nf_conntrack_max Must be between [65536, 4194304] net.netfilter.nf_conntrack_buckets Must be between diff --git a/gcloud/container/node-pools/update b/gcloud/container/node-pools/update index 794682ebe..fd9611afc 100644 --- a/gcloud/container/node-pools/update +++ b/gcloud/container/node-pools/update @@ -276,6 +276,11 @@ REQUIRED FLAGS kubeletConfig: cpuManagerPolicy: static + memoryManager: + policy: Static + topologyManager: + policy: BestEffort + scope: pod linuxConfig: sysctl: net.core.somaxconn: '2048' @@ -292,6 +297,9 @@ REQUIRED FLAGS cpuCFSQuota true or false (enabled by default) cpuCFSQuotaPeriod interval (e.g., '100ms') + memoryManager specify memory manager policy + topologyManager specify topology manager policy + and scope podPidsLimit integer (The value must be greater than or equal to 1024 and less than 4194304.) @@ -321,6 +329,18 @@ REQUIRED FLAGS 'fs.mqueue.*', and 'net.*', and sysctls under the groups.) + KEY VALUE + policy either 'Static' or + 'None' + + KEY VALUE + policy either 'none' or + 'best-effort' or + 'single-numa-node' or + 'restricted' + scope either 'pod' or + 'container' + List of supported sysctls in 'linuxConfig'. KEY VALUE @@ -349,7 +369,8 @@ REQUIRED FLAGS integer tuple net.ipv4.tcp_wmem Any positive integer tuple - net.ipv4.tcp_tw_reuse Must be {0, 1} + net.ipv4.tcp_tw_reuse Must be {0, 1, + 2} net.netfilter.nf_conntrack_max Must be between [65536, 4194304] net.netfilter.nf_conntrack_buckets Must be between diff --git a/gcloud/dataproc/clusters/create b/gcloud/dataproc/clusters/create index 8d1a52636..81955493b 100644 --- a/gcloud/dataproc/clusters/create +++ b/gcloud/dataproc/clusters/create @@ -5,7 +5,8 @@ SYNOPSIS gcloud dataproc clusters create (CLUSTER : --region=REGION) [--action-on-failed-primary-workers=ACTION_ON_FAILED_PRIMARY_WORKERS] [--async] [--autoscaling-policy=AUTOSCALING_POLICY] [--bucket=BUCKET] - [--confidential-compute] [--dataproc-metastore=DATAPROC_METASTORE] + [--cluster-type=TYPE] [--confidential-compute] + [--dataproc-metastore=DATAPROC_METASTORE] [--driver-pool-accelerator=[type=TYPE,[count=COUNT],...]] [--driver-pool-boot-disk-size=DRIVER_POOL_BOOT_DISK_SIZE] [--driver-pool-boot-disk-type=DRIVER_POOL_BOOT_DISK_TYPE] @@ -24,7 +25,7 @@ SYNOPSIS [--master-boot-disk-type=MASTER_BOOT_DISK_TYPE] [--master-local-ssd-interface=MASTER_LOCAL_SSD_INTERFACE] [--master-machine-type=MASTER_MACHINE_TYPE] - [--master-min-cpu-platform=PLATFORM] [--max-idle=MAX_IDLE] + [--master-min-cpu-platform=PLATFORM] [--min-secondary-worker-fraction=MIN_SECONDARY_WORKER_FRACTION] [--node-group=NODE_GROUP] [--num-driver-pool-local-ssds=NUM_DRIVER_POOL_LOCAL_SSDS] @@ -44,7 +45,8 @@ SYNOPSIS [--secondary-worker-standard-capacity-base=SECONDARY_WORKER_STANDARD_CAPACITY_BASE] [--secondary-worker-standard-capacity-percent-above-base=SECONDARY_WORKER_STANDARD_CAPACITY_PERCENT_ABOVE_BASE] [--shielded-integrity-monitoring] [--shielded-secure-boot] - [--shielded-vtpm] [--temp-bucket=TEMP_BUCKET] + [--shielded-vtpm] [--stop-max-idle=STOP_MAX_IDLE] + [--temp-bucket=TEMP_BUCKET] [--worker-accelerator=[type=TYPE,[count=COUNT],...]] [--worker-boot-disk-provisioned-iops=WORKER_BOOT_DISK_PROVISIONED_IOPS] [--worker-boot-disk-provisioned-throughput=WORKER_BOOT_DISK_PROVISIONED_THROUGHPUT] @@ -52,7 +54,10 @@ SYNOPSIS [--worker-boot-disk-type=WORKER_BOOT_DISK_TYPE] [--worker-local-ssd-interface=WORKER_LOCAL_SSD_INTERFACE] [--worker-min-cpu-platform=PLATFORM] [--zone=ZONE, -z ZONE] - [--expiration-time=EXPIRATION_TIME | --max-age=MAX_AGE] + [--delete-expiration-time=DELETE_EXPIRATION_TIME + | --delete-max-age=DELETE_MAX_AGE | --expiration-time=EXPIRATION_TIME + | --max-age=MAX_AGE] + [--delete-max-idle=DELETE_MAX_IDLE | --max-idle=MAX_IDLE] [--gce-pd-kms-key=GCE_PD_KMS_KEY : --gce-pd-kms-key-keyring=GCE_PD_KMS_KEY_KEYRING --gce-pd-kms-key-location=GCE_PD_KMS_KEY_LOCATION @@ -78,6 +83,8 @@ SYNOPSIS --num-secondary-workers=NUM_SECONDARY_WORKERS --num-workers=NUM_WORKERS --secondary-worker-type=TYPE; default="preemptible"] + [--stop-expiration-time=STOP_EXPIRATION_TIME + | --stop-max-age=STOP_MAX_AGE] [--worker-machine-type=WORKER_MACHINE_TYPE | --worker-machine-types=type=MACHINE_TYPE[, type=MACHINE_TYPE...][,rank=RANK]] [GCLOUD_WIDE_FLAG ...] @@ -153,6 +160,10 @@ FLAGS dependencies, miscellaneous config files, and job driver console output when using this cluster. + --cluster-type=TYPE + The type of cluster. TYPE must be one of: standard, single-node, + zero-scale. + --confidential-compute Enables Confidential VM. See https://cloud.google.com/compute/confidential-vm/docs for more @@ -293,11 +304,6 @@ FLAGS which contains the list of available CPU platforms in the zone (see Availability of CPU platforms for more information). - --max-idle=MAX_IDLE - The duration before cluster is auto-deleted after last job completes, - such as "2h" or "1d". See $ gcloud topic datetimes for information on - duration formats. - --min-secondary-worker-fraction=MIN_SECONDARY_WORKER_FRACTION Minimum fraction of secondary worker nodes required to create the cluster. If it is not met, cluster creation will fail. Must be a @@ -443,6 +449,11 @@ FLAGS security operations, such as remote attestation, encryption, and sealing of keys. + --stop-max-idle=STOP_MAX_IDLE + The duration after the last job completes to auto-stop the cluster, + such as "2h" or "1d". See $ gcloud topic datetimes for information on + duration formats. + --temp-bucket=TEMP_BUCKET The Google Cloud Storage bucket to use by default to store ephemeral cluster and jobs data, such as Spark and MapReduce history files. @@ -509,15 +520,37 @@ FLAGS At most one of these can be specified: + --delete-expiration-time=DELETE_EXPIRATION_TIME + The time when the cluster will be auto-deleted, such as + "2017-08-29T18:52:51.142Z." See $ gcloud topic datetimes for + information on time formats. + + --delete-max-age=DELETE_MAX_AGE + The lifespan of the cluster, with auto-deletion upon completion, such + as "2h" or "1d". See $ gcloud topic datetimes for information on + duration formats. + --expiration-time=EXPIRATION_TIME - The time when cluster will be auto-deleted, such as + The time when the cluster will be auto-deleted, such as "2017-08-29T18:52:51.142Z." See $ gcloud topic datetimes for information on time formats. --max-age=MAX_AGE - The lifespan of the cluster before it is auto-deleted, such as "2h" - or "1d". See $ gcloud topic datetimes for information on duration - formats. + The lifespan of the cluster, with auto-deletion upon completion, such + as "2h" or "1d". See $ gcloud topic datetimes for information on + duration formats. + + At most one of these can be specified: + + --delete-max-idle=DELETE_MAX_IDLE + The duration after the last job completes to auto-delete the cluster, + such as "2h" or "1d". See $ gcloud topic datetimes for information on + duration formats. + + --max-idle=MAX_IDLE + The duration after the last job completes to autto-delete the + cluster, such as "2h" or "1d". See $ gcloud topic datetimes for + information on duration formats. Key resource - The Cloud KMS (Key Management Service) cryptokey that will be used to protect the cluster. The 'Compute Engine Service Agent' service @@ -985,6 +1018,18 @@ FLAGS The type of the secondary worker group. TYPE must be one of: preemptible, non-preemptible, spot. + At most one of these can be specified: + + --stop-expiration-time=STOP_EXPIRATION_TIME + The time when the cluster will be auto-stopped, such as + "2017-08-29T18:52:51.142Z." See $ gcloud topic datetimes for + information on time formats. + + --stop-max-age=STOP_MAX_AGE + The lifespan of the cluster, with auto-stop upon completion, such as + "2h" or "1d". See $ gcloud topic datetimes for information on + duration formats. + At most one of these can be specified: --worker-machine-type=WORKER_MACHINE_TYPE diff --git a/gcloud/dataproc/clusters/update b/gcloud/dataproc/clusters/update index 6fb088648..f8443da4f 100644 --- a/gcloud/dataproc/clusters/update +++ b/gcloud/dataproc/clusters/update @@ -10,8 +10,16 @@ SYNOPSIS [--num-workers=NUM_WORKERS] [--update-labels=[KEY=VALUE,...]] [--autoscaling-policy=AUTOSCALING_POLICY | --disable-autoscaling] [--clear-labels | --remove-labels=[KEY,...]] - [--expiration-time=EXPIRATION_TIME | --max-age=MAX_AGE | --no-max-age] - [--max-idle=MAX_IDLE | --no-max-idle] [GCLOUD_WIDE_FLAG ...] + [--delete-expiration-time=DELETE_EXPIRATION_TIME + | --delete-max-age=DELETE_MAX_AGE | --no-delete-max-age + | --expiration-time=EXPIRATION_TIME | --max-age=MAX_AGE + | --no-max-age] + [--delete-max-idle=DELETE_MAX_IDLE | --no-delete-max-idle + | --max-idle=MAX_IDLE | --no-max-idle] + [--stop-expiration-time=STOP_EXPIRATION_TIME + | --stop-max-age=STOP_MAX_AGE | --no-stop-max-age] + [--stop-max-idle=STOP_MAX_IDLE | --no-stop-max-idle] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION Update the number of worker nodes and/or the labels in a cluster. @@ -164,13 +172,27 @@ FLAGS At most one of these can be specified: + --delete-expiration-time=DELETE_EXPIRATION_TIME + The time when the cluster will be auto-deleted, such as + "2017-08-29T18:52:51.142Z". See $ gcloud topic datetimes for + information on time formats. + + --delete-max-age=DELETE_MAX_AGE + The lifespan of the cluster with auto-deletion upon completion, such + as "2h" or "1d". See $ gcloud topic datetimes for information on + duration formats. + + --no-delete-max-age + Cancels the cluster auto-deletion by maximum cluster age (configured + by --delete-max-age or --delete-expiration-time flags) + --expiration-time=EXPIRATION_TIME - The time when cluster will be auto-deleted, such as + The time when the cluster will be auto-deleted, such as "2017-08-29T18:52:51.142Z". See $ gcloud topic datetimes for information on time formats. --max-age=MAX_AGE - The lifespan of the cluster before it is auto-deleted, such as "2h" + The lifespan of the cluster, with auto-deletion upon completion, "2h" or "1d". See $ gcloud topic datetimes for information on duration formats. @@ -180,8 +202,17 @@ FLAGS At most one of these can be specified: + --delete-max-idle=DELETE_MAX_IDLE + The duration after the last job completes to auto-delete the cluster, + such as "2h" or "1d". See $ gcloud topic datetimes for information on + duration formats. + + --no-delete-max-idle + Cancels the cluster auto-deletion by cluster idle duration + (configured by --delete-max-idle flag) + --max-idle=MAX_IDLE - The duration before cluster is auto-deleted after last job finished, + The duration after the last job completes to auto-delete the cluster, such as "2h" or "1d". See $ gcloud topic datetimes for information on duration formats. @@ -189,6 +220,33 @@ FLAGS Cancels the cluster auto-deletion by cluster idle duration (configured by --max-idle flag) + At most one of these can be specified: + + --stop-expiration-time=STOP_EXPIRATION_TIME + The time when the cluster will be auto-stopped, such as + "2017-08-29T18:52:51.142Z". See $ gcloud topic datetimes for + information on time formats. + + --stop-max-age=STOP_MAX_AGE + The lifespan of the cluster, with auto-stop upon completion, such as + "2h" or "1d". See $ gcloud topic datetimes for information on + duration formats. + + --no-stop-max-age + Cancels the cluster auto-stop by maximum cluster age (configured by + --stop-max-age or --stop-expiration-time flags) + + At most one of these can be specified: + + --stop-max-idle=STOP_MAX_IDLE + The duration after the last job completes to auto-stop the cluster, + such as "2h" or "1d". See $ gcloud topic datetimes for information on + duration formats. + + --no-stop-max-idle + Cancels the cluster auto-stop by cluster idle duration (configured by + --stop-max-idle flag) + 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/dataproc/workflow-templates/set-managed-cluster b/gcloud/dataproc/workflow-templates/set-managed-cluster index 2c4db9d24..6ac213c6c 100644 --- a/gcloud/dataproc/workflow-templates/set-managed-cluster +++ b/gcloud/dataproc/workflow-templates/set-managed-cluster @@ -5,7 +5,7 @@ NAME SYNOPSIS gcloud dataproc workflow-templates set-managed-cluster (TEMPLATE : --region=REGION) [--autoscaling-policy=AUTOSCALING_POLICY] - [--bucket=BUCKET] [--cluster-name=CLUSTER_NAME] + [--bucket=BUCKET] [--cluster-name=CLUSTER_NAME] [--cluster-type=TYPE] [--confidential-compute] [--dataproc-metastore=DATAPROC_METASTORE] [--enable-component-gateway] [--initialization-action-timeout=TIMEOUT; default="10m"] @@ -132,6 +132,10 @@ FLAGS The name of the managed dataproc cluster. If unspecified, the workflow template ID will be used. + --cluster-type=TYPE + The type of cluster. TYPE must be one of: standard, single-node, + zero-scale. + --confidential-compute Enables Confidential VM. See https://cloud.google.com/compute/confidential-vm/docs for more diff --git a/gcloud/filestore/instances/create b/gcloud/filestore/instances/create index d98957388..95e30805d 100644 --- a/gcloud/filestore/instances/create +++ b/gcloud/filestore/instances/create @@ -30,7 +30,8 @@ EXAMPLES --tier=TIER --file-share=name=VOLUME_NAME,capacity=CAPACITY \ --network=name=NETWORK_NAME,\ reserved-ip-range=RESERVED_IP_RANGE,connect-mode=CONNECT_MODE \ - --zone=ZONE --kms-key=KMS-KEY --kms-keyring=KMS_KEYRING \ + --zone=ZONE --performance=max-iops-per-tb=MAX-IOPS-PER-TB \ + --kms-key=KMS-KEY --kms-keyring=KMS_KEYRING \ --kms-location=KMS_LOCATION --kms-project=KMS_PROJECT \ --flags-file=FLAGS_FILE --source-instance=SOURCE_INSTANCE diff --git a/gcloud/filestore/instances/update b/gcloud/filestore/instances/update index 016d0dc1e..5ca45b361 100644 --- a/gcloud/filestore/instances/update +++ b/gcloud/filestore/instances/update @@ -59,6 +59,12 @@ EXAMPLES $ gcloud filestore instances update NAME --project=PROJECT_ID \ --zone=ZONE --file-share=name=VOLUME_NAME,capacity=CAPACITY + The following command updates a Filestore instance named NAME to configure + the max-iops-per-tb to MAX-IOPS-PER-TB. + + $ gcloud filestore instances update NAME --project=PROJECT_ID \ + --zone=ZONE --performance=max-iops-per-tb=MAX-IOPS-PER-TB + POSITIONAL ARGUMENTS Instance resource - The instance to update. The arguments in this group can be used to specify the attributes of this resource. (NOTE) Some diff --git a/gcloud/iam/roles/undelete b/gcloud/iam/roles/undelete index 15adc34fc..1b2f6dee0 100644 --- a/gcloud/iam/roles/undelete +++ b/gcloud/iam/roles/undelete @@ -18,12 +18,11 @@ DESCRIPTION EXAMPLES To undelete the role ProjectUpdater of the organization 1234567, run: - $ gcloud iam roles undelete roles/ProjectUpdater \ - --organization=1234567 + $ gcloud iam roles undelete ProjectUpdater --organization=1234567 To undelete the role ProjectUpdater of the project myproject, run: - $ gcloud iam roles undelete roles/ProjectUpdater --project=myproject + $ gcloud iam roles undelete ProjectUpdater --project=myproject POSITIONAL ARGUMENTS ROLE_ID diff --git a/gcloud/iam/roles/update b/gcloud/iam/roles/update index ede080a5e..5e6131adc 100644 --- a/gcloud/iam/roles/update +++ b/gcloud/iam/roles/update @@ -15,12 +15,12 @@ DESCRIPTION EXAMPLES To update the role ProjectUpdater from a YAML file, run: - $ gcloud iam roles update roles/ProjectUpdater --organization=123 \ + $ gcloud iam roles update ProjectUpdater --organization=123 \ --file=role_file_path To update the role ProjectUpdater with flags, run: - $ gcloud iam roles update roles/ProjectUpdater --project=myproject \ + $ gcloud iam roles update ProjectUpdater --project=myproject \ --permissions=permission1,permission2 POSITIONAL ARGUMENTS diff --git a/gcloud/memorystore/instances/create b/gcloud/memorystore/instances/create index ee2c20e62..8eaaf6754 100644 --- a/gcloud/memorystore/instances/create +++ b/gcloud/memorystore/instances/create @@ -2,13 +2,15 @@ NAME gcloud memorystore instances create - create a Memorystore instance SYNOPSIS - gcloud memorystore instances create (INSTANCE : --location=LOCATION) - [--async] [--async-instance-endpoints-deletion-enabled] + gcloud memorystore instances create INSTANCE [--async] + [--async-instance-endpoints-deletion-enabled] [--authorization-mode=AUTHORIZATION_MODE] [--deletion-protection-enabled] [--endpoints=[connections=CONNECTIONS]] [--engine-configs=[ENGINE_CONFIGS,...]] - [--engine-version=ENGINE_VERSION] [--labels=[LABELS,...]] [--mode=MODE] - [--node-type=NODE_TYPE] [--ondemand-maintenance] + [--engine-version=ENGINE_VERSION] [--labels=[LABELS,...]] + [--location=LOCATION] + [--maintenance-policy-weekly-window=[day=DAY],[startTime=STARTTIME]] + [--mode=MODE] [--node-type=NODE_TYPE] [--ondemand-maintenance] [--psc-auto-connections=[network=NETWORK], [port=PORT],[projectId=PROJECTID]] [--replica-count=REPLICA_COUNT] [--request-id=REQUEST_ID] [--shard-count=SHARD_COUNT] @@ -17,6 +19,7 @@ SYNOPSIS --persistence-config-mode=PERSISTENCE_CONFIG_MODE --rdb-config-snapshot-period=RDB_CONFIG_SNAPSHOT_PERIOD --rdb-config-snapshot-start-time=RDB_CONFIG_SNAPSHOT_START_TIME] + [--cross-instance-replication-config-role=CROSS_INSTANCE_REPLICATION_CONFIG_ROLE : --cross-instance-replication-config-secondary-instances=[instance=INSTANCE] --primary-instance=PRIMARY_INSTANCE] [--zone-distribution-config=ZONE_DISTRIBUTION_CONFIG --zone-distribution-config-mode=ZONE_DISTRIBUTION_CONFIG_MODE] [GCLOUD_WIDE_FLAG ...] @@ -49,10 +52,9 @@ EXAMPLES POSITIONAL ARGUMENTS Instance resource - Identifier. Unique name of the instance. Format: - projects/{project}/locations/{location}/instances/{instance} 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}/locations/{location}/instances/{instance} 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 instance on the command line with a fully @@ -60,6 +62,11 @@ POSITIONAL ARGUMENTS ◆ provide the argument --project on the command line; ◆ set the property core/project. + To set the location attribute: + ◆ provide the argument instance on the command line with a fully + specified name; + ◆ provide the argument --location on the command line. + This must be specified. INSTANCE @@ -68,17 +75,6 @@ POSITIONAL ARGUMENTS To set the instance attribute: ▸ provide the argument instance on the command line. - This positional argument must be specified if any of the other - arguments in this group are specified. - - --location=LOCATION - The location id of the instance resource. - - To set the location attribute: - ▸ provide the argument instance on the command line with a fully - specified name; - ▸ provide the argument --location on the command line. - FLAGS --async Return immediately, without waiting for the operation in progress to @@ -188,6 +184,55 @@ FLAGS --labels=path_to_file.(yaml|json) + --location=LOCATION + For resources [instance], provides fallback value for resource location + attribute. When the resource's full URI path is not provided, location + will fallback to this flag value. + + Maintenance policy per instance. + + --maintenance-policy-weekly-window=[day=DAY],[startTime=STARTTIME] + Maintenance window that is applied to resources covered by this + policy. Minimum 1. For the current version, the maximum number of + weekly_window is expected to be one. + + day + Allows to define schedule that runs specified day of the week. + + startTime + Start time of the window in UTC. + + hours + Hours of a day in 24 hour format. Must be greater than or + equal to 0 and typically must be less than or equal to 23. An + API may choose to allow the value "24:00:00" for scenarios + like business closing time. + + minutes + Minutes of an hour. Must be greater than or equal to 0 and + less than or equal to 59. + + nanos + Fractions of seconds, in nanoseconds. Must be greater than or + equal to 0 and less than or equal to 999,999,999. + + seconds + Seconds of a minute. Must be greater than or equal to 0 and + typically must be less than or equal to 59. An API may allow + the value 60 if it allows leap-seconds. + + Shorthand Example: + + --maintenance-policy-weekly-window=day=string,startTime={hours=int,minutes=int,nanos=int,seconds=int} --maintenance-policy-weekly-window=day=string,startTime={hours=int,minutes=int,nanos=int,seconds=int} + + JSON Example: + + --maintenance-policy-weekly-window='[{"day": "string", "startTime": {"hours": int, "minutes": int, "nanos": int, "seconds": int}}]' + + File Example: + + --maintenance-policy-weekly-window=path_to_file.(yaml|json) + --mode=MODE The mode config for the instance. MODE must be one of: @@ -324,6 +369,76 @@ FLAGS future snapshots will be aligned. If not provided, the current time will be used. + Cross instance replication config. + + --cross-instance-replication-config-role=CROSS_INSTANCE_REPLICATION_CONFIG_ROLE + The role of the instance in cross instance replication. + CROSS_INSTANCE_REPLICATION_CONFIG_ROLE must be one of: + + none + This instance does not participate in cross instance replication. + It is an independent instance and does not replicate to or from + any other instances. + primary + A instance that allows both reads and writes. Any data written to + this instance is also replicated to the attached secondary + instances. + secondary + A instance that allows only reads and replicates data from a + primary instance. + + This flag argument must be specified if any of the other arguments in + this group are specified. + + --cross-instance-replication-config-secondary-instances=[instance=INSTANCE] + List of secondary instances that are replicating from this primary + instance. + + This field is only set for a primary instance. + + instance + The full resource path of the remote instance in the format: + projects//locations//instances/. + + Shorthand Example: + + --cross-instance-replication-config-secondary-instances=instance=string --cross-instance-replication-config-secondary-instances=instance=string + + JSON Example: + + --cross-instance-replication-config-secondary-instances='[{"instance": "string"}]' + + File Example: + + --cross-instance-replication-config-secondary-instances=path_to_file.(yaml|json) + + Details of the remote instance associated with this instance in a cross + instance replication setup. + + Instance resource - The full resource path of the remote instance in + the format: + projects//locations//instances/ 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 --primary-instance on the command line with + a fully specified name; + ▫ provide the argument --project on the command line; + ▫ set the property core/project. + + To set the location attribute: + ▫ provide the argument --primary-instance on the command line with + a fully specified name; + ▫ provide the argument --location on the command line. + + --primary-instance=PRIMARY_INSTANCE + ID of the instance or fully qualified identifier for the + instance. + + To set the instance attribute: + ◇ provide the argument --primary-instance on the command line. + Zone distribution configuration for allocation of instance resources. --zone-distribution-config=ZONE_DISTRIBUTION_CONFIG diff --git a/gcloud/memorystore/instances/help b/gcloud/memorystore/instances/help index bf1c97393..a3bee50cf 100644 --- a/gcloud/memorystore/instances/help +++ b/gcloud/memorystore/instances/help @@ -30,6 +30,9 @@ COMMANDS list List all Memorystore instances in a specified project and location. + reschedule-maintenance + Reschedule maintenance window for an instance. + update Update the configuration of a Memorystore instance. diff --git a/gcloud/memorystore/instances/reschedule-maintenance b/gcloud/memorystore/instances/reschedule-maintenance new file mode 100644 index 000000000..d3c505207 --- /dev/null +++ b/gcloud/memorystore/instances/reschedule-maintenance @@ -0,0 +1,87 @@ +NAME + gcloud memorystore instances reschedule-maintenance - reschedule + maintenance window for an instance + +SYNOPSIS + gcloud memorystore instances reschedule-maintenance + (INSTANCE : --location=LOCATION) --reschedule-type=RESCHEDULE_TYPE + [--async] [--schedule-time=SCHEDULE_TIME] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Reschedule maintenance window for an instance. + +EXAMPLES + To reschedule maintenance window for an instance with the name my-instance + in region us-central-1 with immediate, run: + +POSITIONAL ARGUMENTS + Instance resource - Name of the instance to reschedule maintenance for: + projects/{project}/locations/{location_id}/instances/{instance} The + arguments in this group can be used to specify the attributes of this + resource. (NOTE) Some attributes are not given arguments in this group but + can be set in other ways. + + To set the project attribute: + ◆ provide the argument instance on the command line with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + INSTANCE + ID of the instance or fully qualified identifier for the instance. + + To set the instance attribute: + ▸ provide the argument instance on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + The location id of the instance resource. + + To set the location attribute: + ▸ provide the argument instance on the command line with a fully + specified name; + ▸ provide the argument --location on the command line. + +REQUIRED FLAGS + --reschedule-type=RESCHEDULE_TYPE + If reschedule type is SPECIFIC_TIME, schedule_time must be set. + RESCHEDULE_TYPE must be one of: + + immediate + If the user wants to schedule the maintenance to happen now. + specific-time + If the user wants to reschedule the maintenance to a specific time. + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --schedule-time=SCHEDULE_TIME + Timestamp when the maintenance shall be rescheduled to if + reschedule_type=SPECIFIC_TIME, in RFC 3339 format. Example: + 2012-11-15T16:19:00.094Z. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the memorystore/v1 API. The full documentation for this + API can be found at: https://cloud.google.com/memorystore/ + +NOTES + These variants are also available: + + $ gcloud alpha memorystore instances reschedule-maintenance + + $ gcloud beta memorystore instances reschedule-maintenance + diff --git a/gcloud/memorystore/instances/update b/gcloud/memorystore/instances/update index ae3bc5ea4..edde6dcef 100644 --- a/gcloud/memorystore/instances/update +++ b/gcloud/memorystore/instances/update @@ -3,17 +3,25 @@ NAME Memorystore instance SYNOPSIS - gcloud memorystore instances update (INSTANCE : --location=LOCATION) - [--async] [--[no-]async-instance-endpoints-deletion-enabled] + gcloud memorystore instances update INSTANCE [--async] + [--[no-]async-instance-endpoints-deletion-enabled] [--[no-]deletion-protection-enabled] [--engine-version=ENGINE_VERSION] - [--mode=MODE] [--node-type=NODE_TYPE] [--[no-]ondemand-maintenance] - [--replica-count=REPLICA_COUNT] [--request-id=REQUEST_ID] - [--shard-count=SHARD_COUNT] + [--location=LOCATION] [--mode=MODE] [--node-type=NODE_TYPE] + [--[no-]ondemand-maintenance] [--replica-count=REPLICA_COUNT] + [--request-id=REQUEST_ID] [--shard-count=SHARD_COUNT] [--aof-config-append-fsync=AOF_CONFIG_APPEND_FSYNC --clear-persistence-config --persistence-config-mode=PERSISTENCE_CONFIG_MODE --rdb-config-snapshot-period=RDB_CONFIG_SNAPSHOT_PERIOD --rdb-config-snapshot-start-time=RDB_CONFIG_SNAPSHOT_START_TIME] + [--clear-cross-instance-replication-config + --cross-instance-replication-config-role=CROSS_INSTANCE_REPLICATION_CONFIG_ROLE --clear-primary-instance | --primary-instance=PRIMARY_INSTANCE --cross-instance-replication-config-secondary-instances=[instance=INSTANCE] | --add-cross-instance-replication-config-secondary-instances=[instance=INSTANCE] --clear-cross-instance-replication-config-secondary-instances | --remove-cross-instance-replication-config-secondary-instances=[instance=INSTANCE]] + [--clear-maintenance-policy + --maintenance-policy-weekly-window=[day=DAY],[startTime=STARTTIME] + | --add-maintenance-policy-weekly-window=[day=DAY], + [startTime=STARTTIME] --clear-maintenance-policy-weekly-window + | --remove-maintenance-policy-weekly-window=[day=DAY], + [startTime=STARTTIME]] [--endpoints=[connections=CONNECTIONS] | --add-endpoints=[connections=CONNECTIONS] --clear-endpoints | --remove-endpoints=[connections=CONNECTIONS]] @@ -44,10 +52,9 @@ EXAMPLES POSITIONAL ARGUMENTS Instance resource - Identifier. Unique name of the instance. Format: - projects/{project}/locations/{location}/instances/{instance} 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}/locations/{location}/instances/{instance} 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 instance on the command line with a fully @@ -55,6 +62,11 @@ POSITIONAL ARGUMENTS ◆ provide the argument --project on the command line; ◆ set the property core/project. + To set the location attribute: + ◆ provide the argument instance on the command line with a fully + specified name; + ◆ provide the argument --location on the command line. + This must be specified. INSTANCE @@ -63,17 +75,6 @@ POSITIONAL ARGUMENTS To set the instance attribute: ▸ provide the argument instance on the command line. - This positional argument must be specified if any of the other - arguments in this group are specified. - - --location=LOCATION - The location id of the instance resource. - - To set the location attribute: - ▸ provide the argument instance on the command line with a fully - specified name; - ▸ provide the argument --location on the command line. - FLAGS --async Return immediately, without waiting for the operation in progress to @@ -99,6 +100,11 @@ FLAGS --engine-version=ENGINE_VERSION Engine version of the instance. + --location=LOCATION + For resources [instance], provides fallback value for resource location + attribute. When the resource's full URI path is not provided, location + will fallback to this flag value. + --mode=MODE The mode config for the instance. MODE must be one of: @@ -203,6 +209,289 @@ FLAGS future snapshots will be aligned. If not provided, the current time will be used. + Cross instance replication config. + + --clear-cross-instance-replication-config + Set instance.crossInstanceReplicationConfig back to default value. + + --cross-instance-replication-config-role=CROSS_INSTANCE_REPLICATION_CONFIG_ROLE + The role of the instance in cross instance replication. + CROSS_INSTANCE_REPLICATION_CONFIG_ROLE must be one of: + + none + This instance does not participate in cross instance replication. + It is an independent instance and does not replicate to or from + any other instances. + primary + A instance that allows both reads and writes. Any data written to + this instance is also replicated to the attached secondary + instances. + secondary + A instance that allows only reads and replicates data from a + primary instance. + + Details of the remote instance associated with this instance in a cross + instance replication setup. + + Update primary_instance. + + At most one of these can be specified: + + --clear-primary-instance + Clear primary_instance value and set to null. + + Instance resource - Set primary_instance to new value. + + The full resource path of the remote instance in the format: + projects//locations//instances/ 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 --primary-instance on the command line + with a fully specified name; + ◇ provide the argument --project on the command line; + ◇ set the property core/project. + + To set the location attribute: + ◇ provide the argument --primary-instance on the command line + with a fully specified name; + ◇ provide the argument --location on the command line. + + --primary-instance=PRIMARY_INSTANCE + ID of the instance or fully qualified identifier for the + instance. + + To set the instance attribute: + ▹ provide the argument --primary-instance on the command + line. + + Update cross_instance_replication_config_secondary_instances. + + At most one of these can be specified: + + --cross-instance-replication-config-secondary-instances=[instance=INSTANCE] + Set cross_instance_replication_config_secondary_instances to new + value. List of secondary instances that are replicating from this + primary instance. + + This field is only set for a primary instance. + + instance + The full resource path of the remote instance in the format: + projects//locations//instances/. + + Shorthand Example: + + --cross-instance-replication-config-secondary-instances=instance=string --cross-instance-replication-config-secondary-instances=instance=string + + JSON Example: + + --cross-instance-replication-config-secondary-instances='[{"instance": "string"}]' + + File Example: + + --cross-instance-replication-config-secondary-instances=path_to_file.(yaml|json) + + --add-cross-instance-replication-config-secondary-instances=[instance=INSTANCE] + Add new value to + cross_instance_replication_config_secondary_instances list. List of + secondary instances that are replicating from this primary + instance. + + This field is only set for a primary instance. + + instance + The full resource path of the remote instance in the format: + projects//locations//instances/. + + Shorthand Example: + + --add-cross-instance-replication-config-secondary-instances=instance=string --add-cross-instance-replication-config-secondary-instances=instance=string + + JSON Example: + + --add-cross-instance-replication-config-secondary-instances='[{"instance": "string"}]' + + File Example: + + --add-cross-instance-replication-config-secondary-instances=path_to_file.(yaml|json) + + At most one of these can be specified: + + --clear-cross-instance-replication-config-secondary-instances + Clear cross_instance_replication_config_secondary_instances value + and set to empty list. + + --remove-cross-instance-replication-config-secondary-instances=[instance=INSTANCE] + Remove existing value from + cross_instance_replication_config_secondary_instances list. List + of secondary instances that are replicating from this primary + instance. + + This field is only set for a primary instance. + + instance + The full resource path of the remote instance in the format: + projects//locations//instances/. + + Shorthand Example: + + --remove-cross-instance-replication-config-secondary-instances=instance=string --remove-cross-instance-replication-config-secondary-instances=instance=string + + JSON Example: + + --remove-cross-instance-replication-config-secondary-instances='[{"instance": "string"}]' + + File Example: + + --remove-cross-instance-replication-config-secondary-instances=path_to_file.(yaml|json) + + Maintenance policy per instance. + + --clear-maintenance-policy + Set instance.maintenancePolicy back to default value. + + Update maintenance_policy_weekly_window. + + At most one of these can be specified: + + --maintenance-policy-weekly-window=[day=DAY],[startTime=STARTTIME] + Set maintenance_policy_weekly_window to new value. Maintenance + window that is applied to resources covered by this policy. Minimum + 1. For the current version, the maximum number of weekly_window is + expected to be one. + + day + Allows to define schedule that runs specified day of the week. + + startTime + Start time of the window in UTC. + + hours + Hours of a day in 24 hour format. Must be greater than or + equal to 0 and typically must be less than or equal to 23. + An API may choose to allow the value "24:00:00" for + scenarios like business closing time. + + minutes + Minutes of an hour. Must be greater than or equal to 0 and + less than or equal to 59. + + nanos + Fractions of seconds, in nanoseconds. Must be greater than + or equal to 0 and less than or equal to 999,999,999. + + seconds + Seconds of a minute. Must be greater than or equal to 0 and + typically must be less than or equal to 59. An API may + allow the value 60 if it allows leap-seconds. + + Shorthand Example: + + --maintenance-policy-weekly-window=day=string,startTime={hours=int,minutes=int,nanos=int,seconds=int} --maintenance-policy-weekly-window=day=string,startTime={hours=int,minutes=int,nanos=int,seconds=int} + + JSON Example: + + --maintenance-policy-weekly-window='[{"day": "string", "startTime": {"hours": int, "minutes": int, "nanos": int, "seconds": int}}]' + + File Example: + + --maintenance-policy-weekly-window=path_to_file.(yaml|json) + + --add-maintenance-policy-weekly-window=[day=DAY],[startTime=STARTTIME] + Add new value to maintenance_policy_weekly_window list. Maintenance + window that is applied to resources covered by this policy. Minimum + 1. For the current version, the maximum number of weekly_window is + expected to be one. + + day + Allows to define schedule that runs specified day of the week. + + startTime + Start time of the window in UTC. + + hours + Hours of a day in 24 hour format. Must be greater than or + equal to 0 and typically must be less than or equal to 23. + An API may choose to allow the value "24:00:00" for + scenarios like business closing time. + + minutes + Minutes of an hour. Must be greater than or equal to 0 and + less than or equal to 59. + + nanos + Fractions of seconds, in nanoseconds. Must be greater than + or equal to 0 and less than or equal to 999,999,999. + + seconds + Seconds of a minute. Must be greater than or equal to 0 and + typically must be less than or equal to 59. An API may + allow the value 60 if it allows leap-seconds. + + Shorthand Example: + + --add-maintenance-policy-weekly-window=day=string,startTime={hours=int,minutes=int,nanos=int,seconds=int} --add-maintenance-policy-weekly-window=day=string,startTime={hours=int,minutes=int,nanos=int,seconds=int} + + JSON Example: + + --add-maintenance-policy-weekly-window='[{"day": "string", "startTime": {"hours": int, "minutes": int, "nanos": int, "seconds": int}}]' + + File Example: + + --add-maintenance-policy-weekly-window=path_to_file.(yaml|json) + + At most one of these can be specified: + + --clear-maintenance-policy-weekly-window + Clear maintenance_policy_weekly_window value and set to empty + list. + + --remove-maintenance-policy-weekly-window=[day=DAY],[startTime=STARTTIME] + Remove existing value from maintenance_policy_weekly_window list. + Maintenance window that is applied to resources covered by this + policy. Minimum 1. For the current version, the maximum number of + weekly_window is expected to be one. + + day + Allows to define schedule that runs specified day of the + week. + + startTime + Start time of the window in UTC. + + hours + Hours of a day in 24 hour format. Must be greater than or + equal to 0 and typically must be less than or equal to + 23. An API may choose to allow the value "24:00:00" for + scenarios like business closing time. + + minutes + Minutes of an hour. Must be greater than or equal to 0 + and less than or equal to 59. + + nanos + Fractions of seconds, in nanoseconds. Must be greater + than or equal to 0 and less than or equal to 999,999,999. + + seconds + Seconds of a minute. Must be greater than or equal to 0 + and typically must be less than or equal to 59. An API + may allow the value 60 if it allows leap-seconds. + + Shorthand Example: + + --remove-maintenance-policy-weekly-window=day=string,startTime={hours=int,minutes=int,nanos=int,seconds=int} --remove-maintenance-policy-weekly-window=day=string,startTime={hours=int,minutes=int,nanos=int,seconds=int} + + JSON Example: + + --remove-maintenance-policy-weekly-window='[{"day": "string", "startTime": {"hours": int, "minutes": int, "nanos": int, "seconds": int}}]' + + File Example: + + --remove-maintenance-policy-weekly-window=path_to_file.(yaml|json) + Update endpoints. At most one of these can be specified: diff --git a/gcloud/network-connectivity/hubs/accept-spoke-update b/gcloud/network-connectivity/hubs/accept-spoke-update new file mode 100644 index 000000000..3ea3ca010 --- /dev/null +++ b/gcloud/network-connectivity/hubs/accept-spoke-update @@ -0,0 +1,70 @@ +NAME + gcloud network-connectivity hubs accept-spoke-update - accept a proposal to + update a spoke in a hub + +SYNOPSIS + gcloud network-connectivity hubs accept-spoke-update HUB --spoke=SPOKE + --spoke-etag=SPOKE_ETAG [--async] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Accept a proposed or previously rejected VPC spoke update. By accepting a + spoke update, you permit updating connectivity between the associated VPC + network and other VPC networks that are attached to the same hub. + +EXAMPLES + To accept updating a spoke named my-spoke with etag in a hub named my-hub, + run: + + $ gcloud network-connectivity hubs accept-spoke-update my-hub \ + --spoke="projects/spoke-project/locations/global/hubs/my-spoke" \ + --spoke-etag=etag + +POSITIONAL ARGUMENTS + Hub resource - Name of the hub to accept the spoke update. This represents + a Cloud resource. (NOTE) Some attributes are not given arguments in this + group but can be set in other ways. + + To set the project attribute: + ◆ provide the argument hub on the command line with a fully specified + name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + HUB + ID of the hub or fully qualified identifier for the hub. + + To set the hub attribute: + ▸ provide the argument hub on the command line. + +REQUIRED FLAGS + --spoke=SPOKE + URI of the spoke to accept update + + --spoke-etag=SPOKE_ETAG + Etag of the spoke to accept update + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the networkconnectivity/v1 API. The full documentation + for this API can be found at: + https://cloud.google.com/network-connectivity/docs/reference/networkconnectivity/rest + +NOTES + This variant is also available: + + $ gcloud beta network-connectivity hubs accept-spoke-update + diff --git a/gcloud/network-connectivity/hubs/help b/gcloud/network-connectivity/hubs/help index 79820a786..60fcf548b 100644 --- a/gcloud/network-connectivity/hubs/help +++ b/gcloud/network-connectivity/hubs/help @@ -27,6 +27,9 @@ COMMANDS accept-spoke Accept a spoke into a hub. + accept-spoke-update + Accept a proposal to update a spoke in a hub. + add-iam-policy-binding Add an IAM policy binding to the IAM policy of a hub resource. @@ -54,6 +57,9 @@ COMMANDS reject-spoke Reject a spoke from a hub. + reject-spoke-update + Reject a proposal to update a spoke in a hub. + remove-iam-policy-binding Remove an IAM policy binding from the IAM policy of a hub resource. diff --git a/gcloud/network-connectivity/hubs/reject-spoke-update b/gcloud/network-connectivity/hubs/reject-spoke-update new file mode 100644 index 000000000..5f9d42d27 --- /dev/null +++ b/gcloud/network-connectivity/hubs/reject-spoke-update @@ -0,0 +1,74 @@ +NAME + gcloud network-connectivity hubs reject-spoke-update - reject a proposal to + update a spoke in a hub + +SYNOPSIS + gcloud network-connectivity hubs reject-spoke-update HUB --spoke=SPOKE + --spoke-etag=SPOKE_ETAG [--async] [--details=DETAILS] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Reject a VPC spoke update proposal. By rejecting a spoke update, you + prevent updating the connectivity between the associated VPC network and + any other VPC networks that are attached to the same hub. + +EXAMPLES + To reject updating a spoke named my-spoke with etag in a hub named my-hub + with reason my-reason, run: + + $ gcloud network-connectivity hubs reject-spoke-update my-hub \ + --spoke="projects/spoke-project/locations/global/hubs/my-spoke" \ + --spoke-etag=etag --details=my-reason + +POSITIONAL ARGUMENTS + Hub resource - Name of the hub to reject the spoke update. This represents + a Cloud resource. (NOTE) Some attributes are not given arguments in this + group but can be set in other ways. + + To set the project attribute: + ◆ provide the argument hub on the command line with a fully specified + name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + HUB + ID of the hub or fully qualified identifier for the hub. + + To set the hub attribute: + ▸ provide the argument hub on the command line. + +REQUIRED FLAGS + --spoke=SPOKE + URI of the spoke to reject update + + --spoke-etag=SPOKE_ETAG + Etag of the spoke to reject update + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --details=DETAILS + Additional details behind the rejection + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the networkconnectivity/v1 API. The full documentation + for this API can be found at: + https://cloud.google.com/network-connectivity/docs/reference/networkconnectivity/rest + +NOTES + This variant is also available: + + $ gcloud beta network-connectivity hubs reject-spoke-update + diff --git a/gcloud/network-connectivity/service-connection-policies/update b/gcloud/network-connectivity/service-connection-policies/update index 180802d2f..9fad1c2db 100644 --- a/gcloud/network-connectivity/service-connection-policies/update +++ b/gcloud/network-connectivity/service-connection-policies/update @@ -5,8 +5,11 @@ NAME SYNOPSIS gcloud network-connectivity service-connection-policies update SERVICE_CONNECTION_POLICY - (--subnets=[SUBNETS,...] : --psc-connection-limit=PSC_CONNECTION_LIMIT) - [--async] [--description=DESCRIPTION] [--labels=[KEY=VALUE,...]] + (--subnets=[SUBNETS,...] + : --allowed-google-producers-resource-hierarchy-level=[ALLOWED_GOOGLE_PRODUCERS_RESOURCE_HIERARCHY_LEVEL, + ...] --producer-instance-location=PRODUCER_INSTANCE_LOCATION + --psc-connection-limit=PSC_CONNECTION_LIMIT) [--async] + [--description=DESCRIPTION] [--labels=[KEY=VALUE,...]] [--region=REGION] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -18,7 +21,10 @@ EXAMPLES $ gcloud network-connectivity service-connection-policies update \ my-service-conn-policy --region=us-central1 \ - --psc-connection-limit=5 --subnets=my-subnet + --psc-connection-limit=5 --subnets=my-subnet \ + --producer-instance-location=custom-resource-hierarchy-levels \ + --allowed-google-producers-resource-hierarchy-level=projects/\ + my-project POSITIONAL ARGUMENTS Service connection policy resource - Name of the Service Connection Policy @@ -73,6 +79,24 @@ REQUIRED FLAGS To set the subnetwork attribute: ▫ provide the argument --subnets on the command line. + --allowed-google-producers-resource-hierarchy-level=[ALLOWED_GOOGLE_PRODUCERS_RESOURCE_HIERARCHY_LEVEL,...] + List of projects, folders, or orgs where the producer instance can be + located in the form "projects/123456789", folders/123456789", or + "organizations/123456789". + + --producer-instance-location=PRODUCER_INSTANCE_LOCATION + Option that determines where the producer instances can be located + for which connections can be created in the network controlled by + this policy. PRODUCER_INSTANCE_LOCATION must be one of: + + custom-resource-hierarchy-levels + The producer instance must be located in one of the values + provided in the allowed-google-producers-resource-hierarchy-level + flag. + none + The producer instance must be within the same project as this + connection policy. + --psc-connection-limit=PSC_CONNECTION_LIMIT Max number of PSC connections for this policy. diff --git a/gcloud/network-connectivity/spokes/linked-producer-vpc-network/update b/gcloud/network-connectivity/spokes/linked-producer-vpc-network/update index f38f2ef93..e9c5b9c7e 100644 --- a/gcloud/network-connectivity/spokes/linked-producer-vpc-network/update +++ b/gcloud/network-connectivity/spokes/linked-producer-vpc-network/update @@ -4,7 +4,8 @@ NAME SYNOPSIS gcloud network-connectivity spokes linked-producer-vpc-network update SPOKE - [--async] [--description=DESCRIPTION] [--global] + [--async] [--description=DESCRIPTION] + [--exclude-export-ranges=[CIDR_RANGE,...]] [--global] [--include-export-ranges=[CIDR_RANGE,...]] [--update-labels=[KEY=VALUE,...]] [--clear-labels | --remove-labels=[KEY,...]] [GCLOUD_WIDE_FLAG ...] @@ -50,12 +51,14 @@ FLAGS --description=DESCRIPTION New description of the spoke. + --exclude-export-ranges=[CIDR_RANGE,...] + New exclude export ranges of the spoke. + --global Indicates that the spoke is global. --include-export-ranges=[CIDR_RANGE,...] - Only allows adding ALL_IPV6_RANGES to include export ranges or removing - ALL_IPV6_RANGES from include export ranges. + New include export ranges of the spoke. --update-labels=[KEY=VALUE,...] List of label KEY=VALUE pairs to update. If a label exists, its value diff --git a/gcloud/network-connectivity/spokes/linked-vpc-network/update b/gcloud/network-connectivity/spokes/linked-vpc-network/update index 352882306..e33034f47 100644 --- a/gcloud/network-connectivity/spokes/linked-vpc-network/update +++ b/gcloud/network-connectivity/spokes/linked-vpc-network/update @@ -4,7 +4,8 @@ NAME SYNOPSIS gcloud network-connectivity spokes linked-vpc-network update SPOKE - [--async] [--description=DESCRIPTION] [--global] + [--async] [--description=DESCRIPTION] + [--exclude-export-ranges=[CIDR_RANGE,...]] [--global] [--include-export-ranges=[CIDR_RANGE,...]] [--update-labels=[KEY=VALUE,...]] [--clear-labels | --remove-labels=[KEY,...]] [GCLOUD_WIDE_FLAG ...] @@ -50,12 +51,14 @@ FLAGS --description=DESCRIPTION New description of the spoke. + --exclude-export-ranges=[CIDR_RANGE,...] + New exclude export ranges of the spoke. + --global Indicates that the spoke is global. --include-export-ranges=[CIDR_RANGE,...] - Only allows adding ALL_IPV6_RANGES to include export ranges or removing - ALL_IPV6_RANGES from include export ranges. + New include export ranges of the spoke. --update-labels=[KEY=VALUE,...] List of label KEY=VALUE pairs to update. If a label exists, its value diff --git a/gcloud/run/deploy b/gcloud/run/deploy index 56550eb01..0756f0743 100644 --- a/gcloud/run/deploy +++ b/gcloud/run/deploy @@ -28,8 +28,10 @@ SYNOPSIS --clear-volumes --remove-volume=[VOLUME,...]] [--add-volume-mount=[volume=NAME,mount-path=MOUNT_PATH,...] --args=[ARG,...] --[no-]automatic-updates --clear-volume-mounts - --cpu=CPU --depends-on=[CONTAINER,...] --memory=MEMORY --port=PORT + --cpu=CPU --depends-on=[CONTAINER,...] + --liveness-probe=[KEY=VALUE,...] --memory=MEMORY --port=PORT --remove-volume-mount=[MOUNT_PATH,...] + --startup-probe=[KEY=VALUE,...] --[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,...] @@ -45,9 +47,6 @@ SYNOPSIS --update-secrets=[KEY=VALUE,...] --command=[COMMAND,...] | --function=FUNCTION --image=IMAGE --source=SOURCE] [--binary-authorization=POLICY | --clear-binary-authorization] - [--clear-config-maps | --set-config-maps=[KEY=VALUE,...] - | --remove-config-maps=[KEY,...] - --update-config-maps=[KEY=VALUE,...]] [--clear-encryption-key-shutdown-hours | --encryption-key-shutdown-hours=ENCRYPTION_KEY_SHUTDOWN_HOURS] [--clear-key | --key=KEY] @@ -394,6 +393,30 @@ FLAGS --depends-on=[CONTAINER,...] List of container dependencies to add to the current container. + --liveness-probe=[KEY=VALUE,...] + Comma separated settings for liveness probe in the form KEY=VALUE. + Each key stands for a field of the probe described in + https://cloud.google.com/run/docs/reference/rest/v1/Container#Probe. + Currently supported keys are: + + + initialDelaySeconds: integer + + timeoutSeconds: integer + + periodSeconds: integer + + failureThreshold: integer + + httpGet.port: integer + + httpGet.path: string + + grpc.port: integer + + grpc.service: string + + For example, to set a probe with 10s timeout and HTTP probe + requests sent to 8080 port of the container: + + $ --liveness-probe=timeoutSeconds=10,httpGet.port=8080 + + To remove existing probe: + + $ --liveness-probe="" + --memory=MEMORY Set a memory limit. Ex: 1024Mi, 4Gi. @@ -409,6 +432,31 @@ FLAGS Removes the volume mounted at the specified path from the current container. + --startup-probe=[KEY=VALUE,...] + Comma separated settings for startup probe in the form KEY=VALUE. + Each key stands for a field of the probe described in + https://cloud.google.com/run/docs/reference/rest/v1/Container#Probe. + Currently supported keys are: + + + initialDelaySeconds: integer + + timeoutSeconds: integer + + periodSeconds: integer + + failureThreshold: integer + + httpGet.port: integer + + httpGet.path: string + + grpc.port: integer + + grpc.service: string + + tcpSocket.port: integer + + For example, to set a probe with 10s timeout and HTTP probe + requests sent to 8080 port of the container: + + $ --startup-probe=timeoutSeconds=10,httpGet.port=8080 + + To remove existing probe: + + $ --startup-probe="" + --[no-]use-http2 Whether to use HTTP/2 for connections to the service. Use --use-http2 to enable and --no-use-http2 to disable. @@ -575,37 +623,6 @@ FLAGS --clear-binary-authorization Remove any previously set Binary Authorization policy. - Specify config map to mount or provide as environment variables. Keys - starting with a forward slash '/' are mount paths. All other keys - correspond to environment variables. The values associated with each of - these should be in the form CONFIG_MAP_NAME:KEY_IN_CONFIG_MAP; you may - omit the key within the config map to specify a mount of all keys within - the config map. For example: - '--update-config-maps=/my/path=myconfig,ENV=otherconfig:key.json' will - create a volume with config map 'myconfig' and mount that volume at - '/my/path'. Because no config map key was specified, all keys in - 'myconfig' will be included. An environment variable named ENV will also - be created whose value is the value of 'key.json' in 'otherconfig. Not - supported on the fully managed version of Cloud Run. - - At most one of these can be specified: - - --clear-config-maps - Remove all config-maps. - - --set-config-maps=[KEY=VALUE,...] - List of key-value pairs to set as config-maps. All existing - config-maps will be removed first. - - Only --update-config-maps and --remove-config-maps can be used together. - If both are specified, --remove-config-maps will be applied first. - - --remove-config-maps=[KEY,...] - List of config-maps to be removed. - - --update-config-maps=[KEY=VALUE,...] - List of key-value pairs to set as config-maps. - At most one of these can be specified: --clear-encryption-key-shutdown-hours diff --git a/gcloud/run/services/update b/gcloud/run/services/update index 1a0700012..e50f035a0 100644 --- a/gcloud/run/services/update +++ b/gcloud/run/services/update @@ -27,17 +27,16 @@ SYNOPSIS --clear-volumes --remove-volume=[VOLUME,...]] [--add-volume-mount=[volume=NAME,mount-path=MOUNT_PATH,...] --args=[ARG,...] --clear-volume-mounts --command=[COMMAND,...] - --cpu=CPU --depends-on=[CONTAINER,...] --image=IMAGE --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,...] + --cpu=CPU --depends-on=[CONTAINER,...] --image=IMAGE + --liveness-probe=[KEY=VALUE,...] --memory=MEMORY --port=PORT + --remove-volume-mount=[MOUNT_PATH,...] + --startup-probe=[KEY=VALUE,...] --[no-]use-http2 --clear-env-vars + | --env-vars-file=FILE_PATH | --set-env-vars=[KEY=VALUE,...] + | --remove-env-vars=[KEY,...] --update-env-vars=[KEY=VALUE,...] --clear-secrets | --set-secrets=[KEY=VALUE,...] | --remove-secrets=[KEY,...] --update-secrets=[KEY=VALUE,...]] [--binary-authorization=POLICY | --clear-binary-authorization] - [--clear-config-maps | --set-config-maps=[KEY=VALUE,...] - | --remove-config-maps=[KEY,...] - --update-config-maps=[KEY=VALUE,...]] [--clear-encryption-key-shutdown-hours | --encryption-key-shutdown-hours=ENCRYPTION_KEY_SHUTDOWN_HOURS] [--clear-key | --key=KEY] @@ -363,6 +362,30 @@ FLAGS Name of the container image to deploy (e.g. us-docker.pkg.dev/cloudrun/container/hello:latest). + --liveness-probe=[KEY=VALUE,...] + Comma separated settings for liveness probe in the form KEY=VALUE. + Each key stands for a field of the probe described in + https://cloud.google.com/run/docs/reference/rest/v1/Container#Probe. + Currently supported keys are: + + + initialDelaySeconds: integer + + timeoutSeconds: integer + + periodSeconds: integer + + failureThreshold: integer + + httpGet.port: integer + + httpGet.path: string + + grpc.port: integer + + grpc.service: string + + For example, to set a probe with 10s timeout and HTTP probe + requests sent to 8080 port of the container: + + $ --liveness-probe=timeoutSeconds=10,httpGet.port=8080 + + To remove existing probe: + + $ --liveness-probe="" + --memory=MEMORY Set a memory limit. Ex: 1024Mi, 4Gi. @@ -378,6 +401,31 @@ FLAGS Removes the volume mounted at the specified path from the current container. + --startup-probe=[KEY=VALUE,...] + Comma separated settings for startup probe in the form KEY=VALUE. + Each key stands for a field of the probe described in + https://cloud.google.com/run/docs/reference/rest/v1/Container#Probe. + Currently supported keys are: + + + initialDelaySeconds: integer + + timeoutSeconds: integer + + periodSeconds: integer + + failureThreshold: integer + + httpGet.port: integer + + httpGet.path: string + + grpc.port: integer + + grpc.service: string + + tcpSocket.port: integer + + For example, to set a probe with 10s timeout and HTTP probe + requests sent to 8080 port of the container: + + $ --startup-probe=timeoutSeconds=10,httpGet.port=8080 + + To remove existing probe: + + $ --startup-probe="" + --[no-]use-http2 Whether to use HTTP/2 for connections to the service. Use --use-http2 to enable and --no-use-http2 to disable. @@ -445,37 +493,6 @@ FLAGS --clear-binary-authorization Remove any previously set Binary Authorization policy. - Specify config map to mount or provide as environment variables. Keys - starting with a forward slash '/' are mount paths. All other keys - correspond to environment variables. The values associated with each of - these should be in the form CONFIG_MAP_NAME:KEY_IN_CONFIG_MAP; you may - omit the key within the config map to specify a mount of all keys within - the config map. For example: - '--update-config-maps=/my/path=myconfig,ENV=otherconfig:key.json' will - create a volume with config map 'myconfig' and mount that volume at - '/my/path'. Because no config map key was specified, all keys in - 'myconfig' will be included. An environment variable named ENV will also - be created whose value is the value of 'key.json' in 'otherconfig. Not - supported on the fully managed version of Cloud Run. - - At most one of these can be specified: - - --clear-config-maps - Remove all config-maps. - - --set-config-maps=[KEY=VALUE,...] - List of key-value pairs to set as config-maps. All existing - config-maps will be removed first. - - Only --update-config-maps and --remove-config-maps can be used together. - If both are specified, --remove-config-maps will be applied first. - - --remove-config-maps=[KEY,...] - List of config-maps to be removed. - - --update-config-maps=[KEY=VALUE,...] - List of key-value pairs to set as config-maps. - At most one of these can be specified: --clear-encryption-key-shutdown-hours diff --git a/gcloud/spanner/databases/execute-sql b/gcloud/spanner/databases/execute-sql index a6f504056..4bb41096b 100644 --- a/gcloud/spanner/databases/execute-sql +++ b/gcloud/spanner/databases/execute-sql @@ -78,8 +78,14 @@ OPTIONAL FLAGS Returns only the query plan, without any result rows or execution statistics information. PROFILE - Returns both the query plan and the execution statistics along with - the result rows. + Returns the query plan, overall execution statistics, + operator-level execution statistics, along with the result rows. + WITH_PLAN_AND_STATS + Returns the query plan, overall (but not operator-level) execution + statistics, along with the results. + WITH_STATS + Returns the overall (but not operator-level) execution statistics + along with the results. --timeout=TIMEOUT; default="10m" Maximum time to wait for the SQL query to complete. See $ gcloud topic diff --git a/gcloud/sql/backups/restore b/gcloud/sql/backups/restore index bb22ba799..439399918 100644 --- a/gcloud/sql/backups/restore +++ b/gcloud/sql/backups/restore @@ -33,6 +33,8 @@ SYNOPSIS [--retained-backups-count=RETAINED_BACKUPS_COUNT] [--retained-transaction-log-days=RETAINED_TRANSACTION_LOG_DAYS] [--ssl-mode=SSL_MODE] [--[no-]storage-auto-increase] + [--storage-provisioned-iops=STORAGE_PROVISIONED_IOPS] + [--storage-provisioned-throughput=STORAGE_PROVISIONED_THROUGHPUT] [--storage-size=STORAGE_SIZE] [--storage-type=STORAGE_TYPE] [--tier=TIER, -t TIER] [--time-zone=TIME_ZONE] [--timeout=TIMEOUT; default=3600] @@ -308,6 +310,14 @@ OPTIONAL FLAGS --storage-auto-increase to enable and --no-storage-auto-increase to disable. + --storage-provisioned-iops=STORAGE_PROVISIONED_IOPS + Indicates how many IOPS to provision for the data disk. This sets the + number of I/O operations per second that the disk can handle. + + --storage-provisioned-throughput=STORAGE_PROVISIONED_THROUGHPUT + Indicates how much throughput to provision for the data disk. This sets + the throughput in MB per second that the disk can handle. + --storage-size=STORAGE_SIZE Amount of storage allocated to the instance. Must be an integer number of GB. The default is 10GB. Information on storage limits can be found diff --git a/gcloud/sql/instances/create b/gcloud/sql/instances/create index 4fbbcae76..001bc38d5 100644 --- a/gcloud/sql/instances/create +++ b/gcloud/sql/instances/create @@ -42,10 +42,14 @@ SYNOPSIS [--psc-auto-connections=[network=NETWORK],[project=PROJECT]] [--[no-]recreate-replicas-on-primary-crash] [--replica-type=REPLICA_TYPE] [--replication=REPLICATION] - [--require-ssl] [--retained-backups-count=RETAINED_BACKUPS_COUNT] + [--require-ssl] [--[no-]retain-backups-on-delete] + [--retained-backups-count=RETAINED_BACKUPS_COUNT] [--retained-transaction-log-days=RETAINED_TRANSACTION_LOG_DAYS] [--root-password=ROOT_PASSWORD] [--server-ca-mode=SERVER_CA_MODE] - [--ssl-mode=SSL_MODE] [--[no-]storage-auto-increase] + [--server-ca-pool=SERVER_CA_POOL] [--ssl-mode=SSL_MODE] + [--[no-]storage-auto-increase] + [--storage-provisioned-iops=STORAGE_PROVISIONED_IOPS] + [--storage-provisioned-throughput=STORAGE_PROVISIONED_THROUGHPUT] [--storage-size=STORAGE_SIZE] [--storage-type=STORAGE_TYPE] [--tags=TAG=VALUE,[TAG=VALUE,...]] [--threads-per-core=THREADS_PER_CORE] [--tier=TIER, -t TIER] @@ -63,28 +67,28 @@ DESCRIPTION Creates a new Cloud SQL instance. EXAMPLES - To create a MySQL 5.7 instance with ID prod-instance that has 2 CPUs, 4 GB + To create a MySQL 8.0 instance with ID prod-instance that has 2 CPUs, 4 GB of RAM, and is in the region us-central1 (a zone will be auto-assigned), where the 'root' user has its password set to password123, run: $ gcloud sql instances create prod-instance \ - --database-version=MYSQL_5_7 --cpu=2 --memory=4GB \ + --database-version=MYSQL_8_0 --cpu=2 --memory=4GB \ --region=us-central1 --root-password=password123 - To create a Postgres 9.6 instance with ID prod-instance that has 2 CPUs, 8 + To create a Postgres 15 instance with ID prod-instance that has 2 CPUs, 8 GiB of RAM, and is in the zone us-central1-a, where the 'postgres' user has its password set to password123, run: $ gcloud sql instances create prod-instance \ - --database-version=POSTGRES_9_6 --cpu=2 --memory=8GiB \ + --database-version=POSTGRES_15 --cpu=2 --memory=8GiB \ --zone=us-central1-a --root-password=password123 - To create a SQL Server 2017 Express instance with ID prod-instance that has + To create a SQL Server 2022 Express instance with ID prod-instance that has 2 CPUs, 3840MiB of RAM, and is in the zone us-central1-a, where the 'sqlserver' user has its password set to password123, run: $ gcloud sql instances create prod-instance \ - --database-version=SQLSERVER_2017_EXPRESS --cpu=2 \ + --database-version=SQLSERVER_2022_EXPRESS --cpu=2 \ --memory=3840MiB --zone=us-central1-a \ --root-password=password123 @@ -415,6 +419,11 @@ FLAGS --require-ssl Specified if users connecting over IP must use SSL. + --[no-]retain-backups-on-delete + Retain automated/ondemand backups of the instance after the instance is + deleted. Use --retain-backups-on-delete to enable and + --no-retain-backups-on-delete to disable. + --retained-backups-count=RETAINED_BACKUPS_COUNT How many backups to keep. The valid range is between 1 and 365. Default value is 7 for Enterprise edition instances. For Enterprise_Plus, @@ -443,6 +452,9 @@ FLAGS GOOGLE_MANAGED_INTERNAL_CA Google-managed self-signed internal CA. + --server-ca-pool=SERVER_CA_POOL + Set the server CA pool of the instance. + --ssl-mode=SSL_MODE Set the SSL mode of the instance. SSL_MODE must be one of: @@ -465,6 +477,14 @@ FLAGS --storage-auto-increase to enable and --no-storage-auto-increase to disable. + --storage-provisioned-iops=STORAGE_PROVISIONED_IOPS + Indicates how many IOPS to provision for the data disk. This sets the + number of I/O operations per second that the disk can handle. + + --storage-provisioned-throughput=STORAGE_PROVISIONED_THROUGHPUT + Indicates how much throughput to provision for the data disk. This sets + the throughput in MB per second that the disk can handle. + --storage-size=STORAGE_SIZE Amount of storage allocated to the instance. Must be an integer number of GB. The default is 10GB. Information on storage limits can be found diff --git a/gcloud/sql/instances/patch b/gcloud/sql/instances/patch index 034736ce1..bdaf2be40 100644 --- a/gcloud/sql/instances/patch +++ b/gcloud/sql/instances/patch @@ -41,8 +41,11 @@ SYNOPSIS [--pricing-plan=PRICING_PLAN, -p PRICING_PLAN] [--[no-]recreate-replicas-on-primary-crash] [--remove-deny-maintenance-period] [--replication=REPLICATION] - [--[no-]require-ssl] [--simulate-maintenance-event] - [--ssl-mode=SSL_MODE] [--[no-]storage-auto-increase] + [--[no-]require-ssl] [--[no-]retain-backups-on-delete] + [--simulate-maintenance-event] [--ssl-mode=SSL_MODE] + [--[no-]storage-auto-increase] + [--storage-provisioned-iops=STORAGE_PROVISIONED_IOPS] + [--storage-provisioned-throughput=STORAGE_PROVISIONED_THROUGHPUT] [--storage-size=STORAGE_SIZE] [--switch-transaction-logs-to-cloud-storage] [--threads-per-core=THREADS_PER_CORE] [--tier=TIER, -t TIER] @@ -366,6 +369,11 @@ FLAGS mysqld should default to 'REQUIRE X509' for users connecting over IP. Use --require-ssl to enable and --no-require-ssl to disable. + --[no-]retain-backups-on-delete + Retain automated/ondemand backups of the instance after the instance is + deleted. Use --retain-backups-on-delete to enable and + --no-retain-backups-on-delete to disable. + --simulate-maintenance-event Simulate a maintenance event without changing the version. Only applicable to instances that support near-zero downtime planned @@ -393,6 +401,14 @@ FLAGS --storage-auto-increase to enable and --no-storage-auto-increase to disable. + --storage-provisioned-iops=STORAGE_PROVISIONED_IOPS + Indicates how many IOPS to provision for the data disk. This sets the + number of I/O operations per second that the disk can handle. + + --storage-provisioned-throughput=STORAGE_PROVISIONED_THROUGHPUT + Indicates how much throughput to provision for the data disk. This sets + the throughput in MB per second that the disk can handle. + --storage-size=STORAGE_SIZE Amount of storage allocated to the instance. Must be an integer number of GB. The default is 10GB. Information on storage limits can be found