From a990278fb32a3b8c59d563c916a0e0a6bc3c8f25 Mon Sep 17 00:00:00 2001 From: Automated Date: Thu, 14 Dec 2023 10:23:58 +0000 Subject: [PATCH] gcloud: Thu Dec 14 10:23:57 UTC 2023 --- gcloud/_version | 10 +- gcloud/ai/models/upload | 48 ++- gcloud/alloydb/clusters/restore | 13 +- gcloud/alpha/ai/models/upload | 48 ++- gcloud/alpha/alloydb/clusters/restore | 18 +- .../certificate-manager/trust-configs/help | 3 + .../certificate-manager/trust-configs/update | 132 ++++++ gcloud/alpha/composer/environments/create | 20 +- gcloud/alpha/compute/forwarding-rules/create | 10 +- .../alpha/compute/forwarding-rules/set-target | 10 +- .../compute/instances/create-with-container | 2 +- .../instances/ops-agents/policies/create | 1 + .../instances/ops-agents/policies/update | 1 + gcloud/alpha/compute/instances/set-name | 4 +- .../compute/network-endpoint-groups/update | 17 +- gcloud/alpha/compute/networks/create | 11 +- gcloud/alpha/compute/networks/update | 11 +- .../compute/public-advertised-prefixes/create | 4 +- .../compute/public-delegated-prefixes/create | 4 +- .../compute/security-policies/rules/create | 18 +- .../compute/security-policies/rules/update | 18 +- gcloud/alpha/compute/tpus/tpu-vm/create | 16 +- gcloud/alpha/config/get | 11 +- gcloud/alpha/config/help | 11 +- gcloud/alpha/config/list | 11 +- gcloud/alpha/config/set | 11 +- gcloud/alpha/config/unset | 11 +- gcloud/alpha/container/aws/node-pools/help | 3 + .../alpha/container/aws/node-pools/rollback | 84 ++++ gcloud/alpha/container/clusters/create | 46 +- gcloud/alpha/container/clusters/update | 62 +-- .../container/fleet/clusterupgrade/create | 12 +- .../container/fleet/clusterupgrade/describe | 6 +- .../alpha/container/fleet/clusterupgrade/help | 6 +- .../container/fleet/clusterupgrade/update | 12 +- gcloud/alpha/container/fleet/create | 8 +- gcloud/alpha/container/fleet/mesh/debug/help | 20 + gcloud/alpha/container/fleet/mesh/help | 8 +- gcloud/alpha/container/fleet/update | 8 +- .../alpha/container/hub/clusterupgrade/create | 12 +- .../container/hub/clusterupgrade/describe | 6 +- .../alpha/container/hub/clusterupgrade/help | 6 +- .../alpha/container/hub/clusterupgrade/update | 12 +- gcloud/alpha/container/hub/create | 8 +- gcloud/alpha/container/hub/mesh/debug/help | 20 + gcloud/alpha/container/hub/mesh/help | 8 +- gcloud/alpha/container/hub/update | 8 +- gcloud/alpha/container/node-pools/update | 6 +- gcloud/alpha/deploy/apply | 7 +- .../alpha/deploy/custom-target-types/delete | 78 ++++ .../alpha/deploy/custom-target-types/describe | 73 ++++ .../alpha/deploy/custom-target-types/export | 77 ++++ gcloud/alpha/deploy/custom-target-types/help | 41 ++ .../custom-target-types}/list | 44 +- gcloud/alpha/deploy/delete | 10 +- gcloud/alpha/deploy/help | 11 +- .../edge-cloud/networking/subnets/create | 16 +- gcloud/alpha/firestore/locations/describe | 36 ++ gcloud/alpha/firestore/locations/help | 3 + gcloud/alpha/functions/deploy | 5 + gcloud/alpha/infra-manager/deployments/apply | 250 ----------- gcloud/alpha/infra-manager/deployments/delete | 81 ---- .../alpha/infra-manager/deployments/describe | 69 --- .../infra-manager/deployments/export-lock | 67 --- .../deployments/export-statefile | 72 ---- gcloud/alpha/infra-manager/deployments/help | 52 --- .../deployments/import-statefile | 73 ---- gcloud/alpha/infra-manager/deployments/lock | 70 --- gcloud/alpha/infra-manager/deployments/unlock | 77 ---- gcloud/alpha/infra-manager/help | 34 -- gcloud/alpha/infra-manager/resources/describe | 88 ---- gcloud/alpha/infra-manager/resources/help | 32 -- gcloud/alpha/infra-manager/resources/list | 110 ----- gcloud/alpha/infra-manager/revisions/describe | 78 ---- .../infra-manager/revisions/export-statefile | 76 ---- gcloud/alpha/infra-manager/revisions/help | 34 -- gcloud/alpha/monitoring/uptime/create | 323 ++++++++++++++ gcloud/alpha/monitoring/uptime/delete | 55 +++ gcloud/alpha/monitoring/uptime/describe | 55 +++ gcloud/alpha/monitoring/uptime/help | 15 + .../list => monitoring/uptime/list-configs} | 54 +-- gcloud/alpha/monitoring/uptime/update | 397 ++++++++++++++++++ gcloud/alpha/run/deploy | 10 +- gcloud/alpha/run/services/update | 10 +- gcloud/alpha/services/api-keys/undelete | 4 +- gcloud/beta/ai/models/upload | 48 ++- gcloud/beta/alloydb/clusters/restore | 13 +- .../certificate-manager/trust-configs/help | 3 + .../certificate-manager/trust-configs/update | 129 ++++++ gcloud/beta/composer/environments/create | 20 +- gcloud/beta/compute/forwarding-rules/create | 10 +- .../beta/compute/forwarding-rules/set-target | 10 +- gcloud/beta/compute/instances/create | 2 +- .../compute/instances/create-with-container | 2 +- .../instances/ops-agents/policies/create | 1 + .../instances/ops-agents/policies/update | 1 + gcloud/beta/compute/instances/set-name | 6 +- .../compute/public-advertised-prefixes/create | 4 +- .../compute/public-delegated-prefixes/create | 4 +- .../compute/security-policies/rules/create | 18 +- .../compute/security-policies/rules/update | 18 +- gcloud/beta/config/get | 11 +- gcloud/beta/config/help | 11 +- gcloud/beta/config/list | 11 +- gcloud/beta/config/set | 11 +- gcloud/beta/config/unset | 11 +- gcloud/beta/container/clusters/create | 46 +- gcloud/beta/container/clusters/update | 62 +-- .../container/fleet/clusterupgrade/create | 95 +++++ .../container/fleet/clusterupgrade/describe | 48 +++ .../beta/container/fleet/clusterupgrade/help | 39 ++ .../container/fleet/clusterupgrade/update | 123 ++++++ gcloud/beta/container/fleet/create | 8 +- gcloud/beta/container/fleet/help | 3 + gcloud/beta/container/fleet/update | 8 +- .../beta/container/hub/clusterupgrade/create | 95 +++++ .../container/hub/clusterupgrade/describe | 48 +++ gcloud/beta/container/hub/clusterupgrade/help | 39 ++ .../beta/container/hub/clusterupgrade/update | 123 ++++++ gcloud/beta/container/hub/create | 8 +- gcloud/beta/container/hub/help | 3 + gcloud/beta/container/hub/update | 8 +- gcloud/beta/container/node-pools/update | 6 +- gcloud/beta/deploy/apply | 6 +- gcloud/beta/deploy/custom-target-types/delete | 75 ++++ .../beta/deploy/custom-target-types/describe | 71 ++++ gcloud/beta/deploy/custom-target-types/export | 74 ++++ gcloud/beta/deploy/custom-target-types/help | 39 ++ gcloud/beta/deploy/custom-target-types/list | 87 ++++ gcloud/beta/deploy/delete | 10 +- gcloud/beta/deploy/help | 10 +- gcloud/beta/functions/deploy | 5 + gcloud/beta/services/api-keys/undelete | 6 +- gcloud/certificate-manager/trust-configs/help | 3 + .../certificate-manager/trust-configs/update | 128 ++++++ gcloud/components/help | 3 +- gcloud/components/restore | 8 + gcloud/compute/forwarding-rules/create | 10 +- gcloud/compute/forwarding-rules/set-target | 10 +- gcloud/compute/instances/create | 2 +- .../compute/instances/create-with-container | 2 +- gcloud/compute/instances/help | 3 + gcloud/compute/instances/set-name | 67 +++ .../compute/public-advertised-prefixes/create | 4 +- .../compute/public-delegated-prefixes/create | 4 +- gcloud/compute/security-policies/rules/create | 32 +- gcloud/compute/security-policies/rules/update | 32 +- gcloud/config/get | 11 +- gcloud/config/help | 11 +- gcloud/config/list | 11 +- gcloud/config/set | 11 +- gcloud/config/unset | 11 +- gcloud/container/aws/node-pools/help | 3 + gcloud/container/aws/node-pools/rollback | 81 ++++ gcloud/container/clusters/create | 54 ++- gcloud/container/clusters/create-auto | 26 ++ gcloud/container/clusters/update | 34 ++ gcloud/container/fleet/clusterupgrade/create | 93 ++++ .../container/fleet/clusterupgrade/describe | 47 +++ gcloud/container/fleet/clusterupgrade/help | 34 ++ gcloud/container/fleet/clusterupgrade/update | 120 ++++++ gcloud/container/fleet/create | 8 +- gcloud/container/fleet/help | 3 + gcloud/container/fleet/update | 8 +- gcloud/container/hub/clusterupgrade/create | 93 ++++ gcloud/container/hub/clusterupgrade/describe | 47 +++ gcloud/container/hub/clusterupgrade/help | 34 ++ gcloud/container/hub/clusterupgrade/update | 120 ++++++ gcloud/container/hub/create | 8 +- gcloud/container/hub/help | 3 + gcloud/container/hub/update | 8 +- gcloud/container/node-pools/create | 26 +- gcloud/container/node-pools/update | 24 ++ gcloud/deploy/apply | 7 +- gcloud/deploy/custom-target-types/delete | 74 ++++ gcloud/deploy/custom-target-types/describe | 70 +++ gcloud/deploy/custom-target-types/export | 73 ++++ gcloud/deploy/custom-target-types/help | 37 ++ gcloud/deploy/custom-target-types/list | 86 ++++ gcloud/deploy/delete | 10 +- gcloud/deploy/help | 11 +- gcloud/edge-cloud/networking/subnets/create | 16 +- gcloud/functions/deploy | 5 + gcloud/infra-manager/deployments/apply | 6 - gcloud/infra-manager/deployments/delete | 6 - gcloud/infra-manager/deployments/describe | 6 - gcloud/infra-manager/deployments/export-lock | 6 - .../deployments/export-statefile | 6 - gcloud/infra-manager/deployments/help | 6 - .../deployments/import-statefile | 6 - gcloud/infra-manager/deployments/list | 6 - gcloud/infra-manager/deployments/lock | 6 - gcloud/infra-manager/deployments/unlock | 6 - gcloud/infra-manager/help | 6 - gcloud/infra-manager/resources/describe | 6 - gcloud/infra-manager/resources/help | 6 - gcloud/infra-manager/resources/list | 6 - gcloud/infra-manager/revisions/describe | 6 - .../infra-manager/revisions/export-statefile | 6 - gcloud/infra-manager/revisions/help | 6 - gcloud/infra-manager/revisions/list | 6 - gcloud/pubsub/subscriptions/create | 32 +- gcloud/pubsub/subscriptions/update | 30 +- gcloud/services/api-keys/help | 3 + gcloud/services/api-keys/undelete | 85 ++++ 205 files changed, 4929 insertions(+), 1866 deletions(-) create mode 100644 gcloud/alpha/certificate-manager/trust-configs/update create mode 100644 gcloud/alpha/container/aws/node-pools/rollback create mode 100644 gcloud/alpha/container/fleet/mesh/debug/help create mode 100644 gcloud/alpha/container/hub/mesh/debug/help create mode 100644 gcloud/alpha/deploy/custom-target-types/delete create mode 100644 gcloud/alpha/deploy/custom-target-types/describe create mode 100644 gcloud/alpha/deploy/custom-target-types/export create mode 100644 gcloud/alpha/deploy/custom-target-types/help rename gcloud/alpha/{infra-manager/deployments => deploy/custom-target-types}/list (66%) create mode 100644 gcloud/alpha/firestore/locations/describe delete mode 100644 gcloud/alpha/infra-manager/deployments/apply delete mode 100644 gcloud/alpha/infra-manager/deployments/delete delete mode 100644 gcloud/alpha/infra-manager/deployments/describe delete mode 100644 gcloud/alpha/infra-manager/deployments/export-lock delete mode 100644 gcloud/alpha/infra-manager/deployments/export-statefile delete mode 100644 gcloud/alpha/infra-manager/deployments/help delete mode 100644 gcloud/alpha/infra-manager/deployments/import-statefile delete mode 100644 gcloud/alpha/infra-manager/deployments/lock delete mode 100644 gcloud/alpha/infra-manager/deployments/unlock delete mode 100644 gcloud/alpha/infra-manager/help delete mode 100644 gcloud/alpha/infra-manager/resources/describe delete mode 100644 gcloud/alpha/infra-manager/resources/help delete mode 100644 gcloud/alpha/infra-manager/resources/list delete mode 100644 gcloud/alpha/infra-manager/revisions/describe delete mode 100644 gcloud/alpha/infra-manager/revisions/export-statefile delete mode 100644 gcloud/alpha/infra-manager/revisions/help create mode 100644 gcloud/alpha/monitoring/uptime/create create mode 100644 gcloud/alpha/monitoring/uptime/delete create mode 100644 gcloud/alpha/monitoring/uptime/describe rename gcloud/alpha/{infra-manager/revisions/list => monitoring/uptime/list-configs} (55%) create mode 100644 gcloud/alpha/monitoring/uptime/update create mode 100644 gcloud/beta/certificate-manager/trust-configs/update create mode 100644 gcloud/beta/container/fleet/clusterupgrade/create create mode 100644 gcloud/beta/container/fleet/clusterupgrade/describe create mode 100644 gcloud/beta/container/fleet/clusterupgrade/help create mode 100644 gcloud/beta/container/fleet/clusterupgrade/update create mode 100644 gcloud/beta/container/hub/clusterupgrade/create create mode 100644 gcloud/beta/container/hub/clusterupgrade/describe create mode 100644 gcloud/beta/container/hub/clusterupgrade/help create mode 100644 gcloud/beta/container/hub/clusterupgrade/update create mode 100644 gcloud/beta/deploy/custom-target-types/delete create mode 100644 gcloud/beta/deploy/custom-target-types/describe create mode 100644 gcloud/beta/deploy/custom-target-types/export create mode 100644 gcloud/beta/deploy/custom-target-types/help create mode 100644 gcloud/beta/deploy/custom-target-types/list create mode 100644 gcloud/certificate-manager/trust-configs/update create mode 100644 gcloud/compute/instances/set-name create mode 100644 gcloud/container/aws/node-pools/rollback create mode 100644 gcloud/container/fleet/clusterupgrade/create create mode 100644 gcloud/container/fleet/clusterupgrade/describe create mode 100644 gcloud/container/fleet/clusterupgrade/help create mode 100644 gcloud/container/fleet/clusterupgrade/update create mode 100644 gcloud/container/hub/clusterupgrade/create create mode 100644 gcloud/container/hub/clusterupgrade/describe create mode 100644 gcloud/container/hub/clusterupgrade/help create mode 100644 gcloud/container/hub/clusterupgrade/update create mode 100644 gcloud/deploy/custom-target-types/delete create mode 100644 gcloud/deploy/custom-target-types/describe create mode 100644 gcloud/deploy/custom-target-types/export create mode 100644 gcloud/deploy/custom-target-types/help create mode 100644 gcloud/deploy/custom-target-types/list create mode 100644 gcloud/services/api-keys/undelete diff --git a/gcloud/_version b/gcloud/_version index 7fc124e03..47c40cff6 100644 --- a/gcloud/_version +++ b/gcloud/_version @@ -1,8 +1,8 @@ -Google Cloud SDK 456.0.0 -alpha 2023.12.01 -beta 2023.12.01 -bq 2.0.99 +Google Cloud SDK 457.0.0 +alpha 2023.12.08 +beta 2023.12.08 +bq 2.0.100 bundled-python3-unix 3.11.6 -core 2023.12.01 +core 2023.12.08 gcloud-crc32c 1.0.0 gsutil 5.27 diff --git a/gcloud/ai/models/upload b/gcloud/ai/models/upload index 24c709e8a..e4a090e76 100644 --- a/gcloud/ai/models/upload +++ b/gcloud/ai/models/upload @@ -5,10 +5,19 @@ SYNOPSIS gcloud ai models upload --container-image-uri=CONTAINER_IMAGE_URI --display-name=DISPLAY_NAME [--artifact-uri=ARTIFACT_URI] [--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-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] [--description=DESCRIPTION] [--explanation-metadata-file=EXPLANATION_METADATA_FILE] [--explanation-method=EXPLANATION_METHOD] @@ -53,19 +62,54 @@ OPTIONAL FLAGS 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-ports=[PORT,...] - Container ports to receive requests at. Must be a number between 1 and - 65535, inclusive. + 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. + --description=DESCRIPTION Description of the model. diff --git a/gcloud/alloydb/clusters/restore b/gcloud/alloydb/clusters/restore index 792749c1f..9e987632b 100644 --- a/gcloud/alloydb/clusters/restore +++ b/gcloud/alloydb/clusters/restore @@ -42,12 +42,11 @@ REQUIRED FLAGS Exactly one of these must be specified: --backup=BACKUP - The AlloyDB backup to restore from. This must either be the full - backup name - (projects/myProject/locations/us-central1/backups/myBackup) or the - backup ID (myBackup). In the second case, the project and location - are assumed to be the same as the restored cluster that is being - created. + AlloyDB backup to restore from. This must either be the full backup + name (projects/myProject/locations/us-central1/backups/myBackup) or + the backup ID (myBackup). In the second case, the project and + location are assumed to be the same as the restored cluster that is + being created. Restore a cluster from a source cluster at a given point in time. @@ -59,7 +58,7 @@ REQUIRED FLAGS in this group are specified. --source-cluster=SOURCE_CLUSTER - The AlloyDB source cluster to restore from. This must either be the + AlloyDB source cluster to restore from. This must either be the full cluster name (projects/myProject/locations/us-central1/backups/myCluster) or the cluster ID (myCluster). In the second case, the project and diff --git a/gcloud/alpha/ai/models/upload b/gcloud/alpha/ai/models/upload index 1af18c7c3..fcb11ae04 100644 --- a/gcloud/alpha/ai/models/upload +++ b/gcloud/alpha/ai/models/upload @@ -5,10 +5,19 @@ SYNOPSIS gcloud alpha ai models upload --container-image-uri=CONTAINER_IMAGE_URI --display-name=DISPLAY_NAME [--artifact-uri=ARTIFACT_URI] [--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-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] [--description=DESCRIPTION] [--explanation-metadata-file=EXPLANATION_METADATA_FILE] [--explanation-method=EXPLANATION_METHOD] @@ -58,19 +67,54 @@ OPTIONAL FLAGS 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-ports=[PORT,...] - Container ports to receive requests at. Must be a number between 1 and - 65535, inclusive. + 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. + --description=DESCRIPTION Description of the model. diff --git a/gcloud/alpha/alloydb/clusters/restore b/gcloud/alpha/alloydb/clusters/restore index 0dcb6903e..864d5b2cc 100644 --- a/gcloud/alpha/alloydb/clusters/restore +++ b/gcloud/alpha/alloydb/clusters/restore @@ -7,7 +7,7 @@ SYNOPSIS (--backup=BACKUP | --point-in-time=POINT_IN_TIME --source-cluster=SOURCE_CLUSTER) [--allocated-ip-range-name=ALLOCATED_IP_RANGE_NAME] [--async] - [--network=NETWORK] + [--enable-private-services-connect] [--network=NETWORK] [--kms-key=KMS_KEY : --kms-keyring=KMS_KEYRING --kms-location=KMS_LOCATION --kms-project=KMS_PROJECT] [GCLOUD_WIDE_FLAG ...] @@ -42,12 +42,11 @@ REQUIRED FLAGS Exactly one of these must be specified: --backup=BACKUP - The AlloyDB backup to restore from. This must either be the full - backup name - (projects/myProject/locations/us-central1/backups/myBackup) or the - backup ID (myBackup). In the second case, the project and location - are assumed to be the same as the restored cluster that is being - created. + AlloyDB backup to restore from. This must either be the full backup + name (projects/myProject/locations/us-central1/backups/myBackup) or + the backup ID (myBackup). In the second case, the project and + location are assumed to be the same as the restored cluster that is + being created. Restore a cluster from a source cluster at a given point in time. @@ -59,7 +58,7 @@ REQUIRED FLAGS in this group are specified. --source-cluster=SOURCE_CLUSTER - The AlloyDB source cluster to restore from. This must either be the + AlloyDB source cluster to restore from. This must either be the full cluster name (projects/myProject/locations/us-central1/backups/myCluster) or the cluster ID (myCluster). In the second case, the project and @@ -82,6 +81,9 @@ OPTIONAL FLAGS Return immediately, without waiting for the operation in progress to complete. + --enable-private-services-connect + Enable Private Services Connect (PSC) connectivity for the cluster. + --network=NETWORK Network in the current project that the instance will be part of. To specify using a network with a shared VPC, use the full URL of the diff --git a/gcloud/alpha/certificate-manager/trust-configs/help b/gcloud/alpha/certificate-manager/trust-configs/help index 685681394..eba0c8edd 100644 --- a/gcloud/alpha/certificate-manager/trust-configs/help +++ b/gcloud/alpha/certificate-manager/trust-configs/help @@ -35,6 +35,9 @@ COMMANDS list (ALPHA) List all TrustConfigs in a project. + update + (ALPHA) Update TrustConfig. + 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/certificate-manager/trust-configs/update b/gcloud/alpha/certificate-manager/trust-configs/update new file mode 100644 index 000000000..32127961a --- /dev/null +++ b/gcloud/alpha/certificate-manager/trust-configs/update @@ -0,0 +1,132 @@ +NAME + gcloud alpha certificate-manager trust-configs update - update TrustConfig + +SYNOPSIS + gcloud alpha certificate-manager trust-configs update + (TRUST_CONFIG : --location=LOCATION) [--async] + [--description=DESCRIPTION] + [--trust-store=[intermediate-cas=INTERMEDIATE-CAS], + [trust-anchors=TRUST-ANCHORS]] [--update-labels=[KEY=VALUE,...]] + [--clear-labels | --remove-labels=[KEY,...]] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Update a TrustConfig. + +EXAMPLES + To update a TrustConfig, run: + + $ gcloud alpha certificate-manager trust-configs update \ + my-trust-config --description="updated description" \ + --trust-store=trust-anchors=ta.pem,\ + intermediate-cas="ica1.pem;ica2.pem" \ + --update-labels=my-key1=my-updated-value1 \ + --remove-labels=my-key2 + +POSITIONAL ARGUMENTS + TrustConfig resource - Name of the TrustConfig to update. The arguments in + this group can be used to specify the attributes of this resource. (NOTE) + Some attributes are not given arguments in this group but can be set in + other ways. + + To set the project attribute: + ◆ provide the argument trust_config on the command line with a fully + specified name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + This must be specified. + + TRUST_CONFIG + ID of the trustConfig or fully qualified identifier for the + trustConfig. + + To set the trust_config attribute: + ▸ provide the argument trust_config on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + Certificate Manager location. + + To set the location attribute: + ▸ provide the argument trust_config on the command line with a + fully specified name; + ▸ provide the argument --location on the command line; + ▸ default value of location is [global]. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --description=DESCRIPTION + Human-readable description of the resource. + + --trust-store=[intermediate-cas=INTERMEDIATE-CAS],[trust-anchors=TRUST-ANCHORS] + Trust Store with the given trust anchor and intermediate CA PEM-encoded + certificates. Certificates should be provided in files. For multiple + file names, separate them by a semicolon (';') and quote them ('"'). + One file can contain multiple certificates. Intermediate CAs are + optional. + + Examples: + + Single files: --trust-store trust-anchors=ta.pem,intermediate-cas=ica.pem + + No intermediate CAs: --trust-store trust-anchors=ta.pem + + Multiple files: --trust-store trust-anchors="ta1.pem;ta2.pem",intermediate-cas="ica1.pem;ica2.pem" + + --update-labels=[KEY=VALUE,...] + List of label KEY=VALUE pairs to update. If a label exists, its value + is modified. Otherwise, a new label is created. + + Keys must start with a lowercase character and contain only hyphens + (-), underscores (_), lowercase characters, and numbers. Values must + contain only hyphens (-), underscores (_), lowercase characters, and + numbers. + + At most one of these can be specified: + + --clear-labels + Remove all labels. If --update-labels is also specified then + --clear-labels is applied first. + + For example, to remove all labels: + + $ gcloud alpha certificate-manager trust-configs update \ + --clear-labels + + To remove all existing labels and create two new labels, foo and baz: + + $ gcloud alpha certificate-manager trust-configs update \ + --clear-labels --update-labels foo=bar,baz=qux + + --remove-labels=[KEY,...] + List of label keys to remove. If a label does not exist it is + silently ignored. If --update-labels is also specified then + --update-labels is applied first. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the certificatemanager/v1 API. The full documentation for + this API can be found at: https://cloud.google.com/certificate-manager + +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 certificate-manager trust-configs update + + $ gcloud beta certificate-manager trust-configs update + diff --git a/gcloud/alpha/composer/environments/create b/gcloud/alpha/composer/environments/create index cebb80477..50e697271 100644 --- a/gcloud/alpha/composer/environments/create +++ b/gcloud/alpha/composer/environments/create @@ -7,8 +7,8 @@ SYNOPSIS (ENVIRONMENT : --location=LOCATION) [--airflow-configs=[KEY=VALUE,...]] [--async] [--cloud-sql-machine-type=CLOUD_SQL_MACHINE_TYPE] [--cloud-sql-preferred-zone=CLOUD_SQL_PREFERRED_ZONE] - [--disk-size=DISK_SIZE] [--enable-cloud-data-lineage-integration] - [--enable-high-resilience] [--env-variables=[NAME=VALUE,...]] + [--disk-size=DISK_SIZE] [--enable-high-resilience] + [--env-variables=[NAME=VALUE,...]] [--environment-size=ENVIRONMENT_SIZE] [--labels=[KEY=VALUE,...]] [--machine-type=MACHINE_TYPE] [--node-count=NODE_COUNT] [--oauth-scopes=[SCOPE,...]] [--python-version=PYTHON_VERSION] @@ -29,6 +29,8 @@ SYNOPSIS --max-pods-per-node=MAX_PODS_PER_NODE --services-ipv4-cidr=SERVICES_IPV4_CIDR --services-secondary-range-name=SERVICES_SECONDARY_RANGE_NAME] + [--disable-cloud-data-lineage-integration + | --enable-cloud-data-lineage-integration] [--enable-master-authorized-networks --master-authorized-networks=[NETWORK,...]] [--enable-scheduled-snapshot-creation @@ -131,12 +133,6 @@ FLAGS multiple of gigabytes. Cannot be updated after the environment has been created. If units are not provided, defaults to GB. - Group of arguments for setting Cloud Data Lineage integration - configuration in Composer 2. - - --enable-cloud-data-lineage-integration - Enable Cloud Data Lineage integration. - --enable-high-resilience Enable high resilience, supported for Composer 2 Environments. @@ -380,6 +376,14 @@ FLAGS When used with Composer 1.x, cannot be specified unless --enable-ip-alias is also specified. + At most one of these can be specified: + + --disable-cloud-data-lineage-integration + Disable Cloud Data Lineage integration. + + --enable-cloud-data-lineage-integration + Enable Cloud Data Lineage integration. + Master Authorized Networks configuration --enable-master-authorized-networks diff --git a/gcloud/alpha/compute/forwarding-rules/create b/gcloud/alpha/compute/forwarding-rules/create index 7e8b53ac4..fce21536e 100644 --- a/gcloud/alpha/compute/forwarding-rules/create +++ b/gcloud/alpha/compute/forwarding-rules/create @@ -116,12 +116,14 @@ REQUIRED FLAGS Target gRPC proxy that receives the traffic. --target-http-proxy=TARGET_HTTP_PROXY - Target HTTP proxy that receives the traffic. Acceptable values for - --ports flag are: 80, 8080. + Target HTTP proxy that receives the traffic. For the acceptable + ports, see Port specifications + (https://cloud.google.com/load-balancing/docs/forwarding-rule-concepts#port_specifications). --target-https-proxy=TARGET_HTTPS_PROXY - Target HTTPS proxy that receives the traffic. Acceptable values for - --ports flag are: 443. + Target HTTPS proxy that receives the traffic. For the acceptable + ports, see Port specifications + (https://cloud.google.com/load-balancing/docs/forwarding-rule-concepts#port_specifications). --target-instance=TARGET_INSTANCE Name of the target instance that receives the traffic. The target diff --git a/gcloud/alpha/compute/forwarding-rules/set-target b/gcloud/alpha/compute/forwarding-rules/set-target index 268811851..70faa3b83 100644 --- a/gcloud/alpha/compute/forwarding-rules/set-target +++ b/gcloud/alpha/compute/forwarding-rules/set-target @@ -79,12 +79,14 @@ REQUIRED FLAGS Target gRPC proxy that receives the traffic. --target-http-proxy=TARGET_HTTP_PROXY - Target HTTP proxy that receives the traffic. Acceptable values for - --ports flag are: 80, 8080. + Target HTTP proxy that receives the traffic. For the acceptable + ports, see Port specifications + (https://cloud.google.com/load-balancing/docs/forwarding-rule-concepts#port_specifications). --target-https-proxy=TARGET_HTTPS_PROXY - Target HTTPS proxy that receives the traffic. Acceptable values for - --ports flag are: 443. + Target HTTPS proxy that receives the traffic. For the acceptable + ports, see Port specifications + (https://cloud.google.com/load-balancing/docs/forwarding-rule-concepts#port_specifications). --target-instance=TARGET_INSTANCE Name of the target instance that receives the traffic. The target diff --git a/gcloud/alpha/compute/instances/create-with-container b/gcloud/alpha/compute/instances/create-with-container index 9cb67a254..54f6d5029 100644 --- a/gcloud/alpha/compute/instances/create-with-container +++ b/gcloud/alpha/compute/instances/create-with-container @@ -742,7 +742,7 @@ FLAGS --source-instance-template=SOURCE_INSTANCE_TEMPLATE The name of the instance template that the instance will be created - from. + from. An instance template can be a global/regional resource. Users can also override machine type and labels. Values of other flags will be ignored and --source-instance-template will be used instead. diff --git a/gcloud/alpha/compute/instances/ops-agents/policies/create b/gcloud/alpha/compute/instances/ops-agents/policies/create index 30d3de0bc..32fa80256 100644 --- a/gcloud/alpha/compute/instances/ops-agents/policies/create +++ b/gcloud/alpha/compute/instances/ops-agents/policies/create @@ -247,6 +247,7 @@ REQUIRED FLAGS ubuntu 21.10 ubuntu 22.04 ubuntu 23.04 + ubuntu 23.10 windows 10.* windows 6.* diff --git a/gcloud/alpha/compute/instances/ops-agents/policies/update b/gcloud/alpha/compute/instances/ops-agents/policies/update index ca79821d0..ebe9d2a87 100644 --- a/gcloud/alpha/compute/instances/ops-agents/policies/update +++ b/gcloud/alpha/compute/instances/ops-agents/policies/update @@ -284,6 +284,7 @@ FLAGS ubuntu 21.10 ubuntu 22.04 ubuntu 23.04 + ubuntu 23.10 windows 10.* windows 6.* diff --git a/gcloud/alpha/compute/instances/set-name b/gcloud/alpha/compute/instances/set-name index b2c8de82d..ee09f7bad 100644 --- a/gcloud/alpha/compute/instances/set-name +++ b/gcloud/alpha/compute/instances/set-name @@ -63,7 +63,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud compute instances set-name $ gcloud beta compute instances set-name diff --git a/gcloud/alpha/compute/network-endpoint-groups/update b/gcloud/alpha/compute/network-endpoint-groups/update index 7f5997983..5bdecec24 100644 --- a/gcloud/alpha/compute/network-endpoint-groups/update +++ b/gcloud/alpha/compute/network-endpoint-groups/update @@ -4,10 +4,10 @@ NAME SYNOPSIS gcloud alpha compute network-endpoint-groups update NAME - (--add-endpoint=[fqdn=FQDN], - [instance=INSTANCE],[ip=IP],[ipv6=IPV6],[port=PORT] - | --remove-endpoint=[fqdn=FQDN], - [instance=INSTANCE],[ip=IP],[ipv6=IPV6],[port=PORT]) + (--add-endpoint=[client_port=CLIENT_PORT], + [fqdn=FQDN],[instance=INSTANCE],[ip=IP],[ipv6=IPV6],[port=PORT] + | --remove-endpoint=[client_port=CLIENT_PORT], + [fqdn=FQDN],[instance=INSTANCE],[ip=IP],[ipv6=IPV6],[port=PORT]) [--global | --region=REGION | --zone=ZONE] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -38,7 +38,7 @@ REQUIRED FLAGS Exactly one of these must be specified: - --add-endpoint=[fqdn=FQDN],[instance=INSTANCE],[ip=IP],[ipv6=IPV6],[port=PORT] + --add-endpoint=[client_port=CLIENT_PORT],[fqdn=FQDN],[instance=INSTANCE],[ip=IP],[ipv6=IPV6],[port=PORT] The network endpoint to add to the network endpoint group. Keys used depend on the endpoint type of the NEG. @@ -67,6 +67,9 @@ REQUIRED FLAGS *port* - Required endpoint port unless NEG default port is set. + *clientPort* - Required endpoint client port only for the port + mapping NEG. + internet-ip-port *ip* - Optional IPv4 address of the endpoint to attach. Must be @@ -126,7 +129,7 @@ REQUIRED FLAGS IP address must be the VM's network interface address. If not specified, the primary NIC address is used. - --remove-endpoint=[fqdn=FQDN],[instance=INSTANCE],[ip=IP],[ipv6=IPV6],[port=PORT] + --remove-endpoint=[client_port=CLIENT_PORT],[fqdn=FQDN],[instance=INSTANCE],[ip=IP],[ipv6=IPV6],[port=PORT] The network endpoint to detach from the network endpoint group. Keys used depend on the endpoint type of the NEG. @@ -144,6 +147,8 @@ REQUIRED FLAGS *port* - Optional port of the network endpoint to detach. + *clientPort* - Optional client port, only for port mapping NEGs. + internet-ip-port *ip* - Required IPv4 address of the network endpoint to detach. diff --git a/gcloud/alpha/compute/networks/create b/gcloud/alpha/compute/networks/create index 3e22b4156..acc392b3d 100644 --- a/gcloud/alpha/compute/networks/create +++ b/gcloud/alpha/compute/networks/create @@ -108,9 +108,16 @@ FLAGS or STANDARD. BGP_BEST_PATH_SELECTION_MODE must be one of: LEGACY - LEGACY mode (default) + Dynamic routes are ranked based on MED BGP attribute. When global + routing is enabled, MED of the routes received from other regions + is original MED plus region-to-region cost. STANDARD - STANDARD mode + Dynamic routes are ranked based on AS Path, Origin, Neighbor ASN + and MED BGP attributes. When global routing is enabled, + region-to-region cost is used as a tiebreaker. This mode offers + customizations to fine-tune BGP best path routing with additional + knobs like --bgp-bps-always-compare-med and + --bgp-bps-inter-region-cost --[no-]bgp-bps-always-compare-med Enables/disables the comparison of MED across routes with different diff --git a/gcloud/alpha/compute/networks/update b/gcloud/alpha/compute/networks/update index da2ef9cd2..896059dd4 100644 --- a/gcloud/alpha/compute/networks/update +++ b/gcloud/alpha/compute/networks/update @@ -64,9 +64,16 @@ FLAGS or STANDARD. BGP_BEST_PATH_SELECTION_MODE must be one of: LEGACY - LEGACY mode (default) + Dynamic routes are ranked based on MED BGP attribute. When global + routing is enabled, MED of the routes received from other regions + is original MED plus region-to-region cost. STANDARD - STANDARD mode + Dynamic routes are ranked based on AS Path, Origin, Neighbor ASN + and MED BGP attributes. When global routing is enabled, + region-to-region cost is used as a tiebreaker. This mode offers + customizations to fine-tune BGP best path routing with additional + knobs like --bgp-bps-always-compare-med and + --bgp-bps-inter-region-cost --[no-]bgp-bps-always-compare-med Enables/disables the comparison of MED across routes with different diff --git a/gcloud/alpha/compute/public-advertised-prefixes/create b/gcloud/alpha/compute/public-advertised-prefixes/create index 695a10994..df88ebd53 100644 --- a/gcloud/alpha/compute/public-advertised-prefixes/create +++ b/gcloud/alpha/compute/public-advertised-prefixes/create @@ -27,11 +27,11 @@ POSITIONAL ARGUMENTS REQUIRED FLAGS --dns-verification-ip=DNS_VERIFICATION_IP - IPv4 address to use for verification. It must be within the IPv4 range + IP address to use for verification. It must be within the IP range specified in --range. --range=RANGE - IPv4 range allocated to this public advertised prefix, in CIDR format. + IP range allocated to this public advertised prefix, in CIDR format. OPTIONAL FLAGS --description=DESCRIPTION diff --git a/gcloud/alpha/compute/public-delegated-prefixes/create b/gcloud/alpha/compute/public-delegated-prefixes/create index 19110f2b2..38394ed3a 100644 --- a/gcloud/alpha/compute/public-delegated-prefixes/create +++ b/gcloud/alpha/compute/public-delegated-prefixes/create @@ -23,8 +23,8 @@ POSITIONAL ARGUMENTS REQUIRED FLAGS --range=RANGE - IPv4 range from this public delegated prefix that should be delegated, - in CIDR format. It must be smaller than parent public advertised prefix + IP range from this public delegated prefix that should be delegated, in + CIDR format. It must be smaller than parent public advertised prefix range. Exactly one of these must be specified: diff --git a/gcloud/alpha/compute/security-policies/rules/create b/gcloud/alpha/compute/security-policies/rules/create index 19624b900..185f310aa 100644 --- a/gcloud/alpha/compute/security-policies/rules/create +++ b/gcloud/alpha/compute/security-policies/rules/create @@ -20,8 +20,8 @@ SYNOPSIS [--conform-action=CONFORM_ACTION] [--description=DESCRIPTION] [--enforce-on-key=ENFORCE_ON_KEY] [--enforce-on-key-configs=[[all],[ip],[xff-ip], - [http-cookie=HTTP_COOKIE], - [http-header=HTTP_HEADER],[http-path],[sni],[region-code]],[...]] + [http-cookie=HTTP_COOKIE],[http-header=HTTP_HEADER],[http-path], + [sni],[region-code],[tls-ja3-fingerprint],[user-ip]],[...]] [--enforce-on-key-name=ENFORCE_ON_KEY_NAME] [--exceed-action=EXCEED_ACTION] [--exceed-action-rpc-status-code=EXCEED_ACTION_RPC_STATUS_CODE] @@ -184,11 +184,16 @@ OPTIONAL FLAGS the TLS session of the HTTPS request ◆ region-code: key type takes the value of the region code from which the request originates + ◆ tls-ja3-fingerprint: key type takes the value of JA3 TLS/SSL + fingerprint if the client connects using HTTPS, HTTP/2 or HTTP/3 + ◆ user-ip: key type takes the IP address of the originating client, + which is resolved based on user-ip-request-headers configured with + the security policy ENFORCE_ON_KEY must be one of: ip, all, http-header, xff-ip, - http-cookie, http-path, sni, region-code. + http-cookie, http-path, sni, region-code, tls-ja3-fingerprint, user-ip. - --enforce-on-key-configs=[[all],[ip],[xff-ip],[http-cookie=HTTP_COOKIE],[http-header=HTTP_HEADER],[http-path],[sni],[region-code]],[...] + --enforce-on-key-configs=[[all],[ip],[xff-ip],[http-cookie=HTTP_COOKIE],[http-header=HTTP_HEADER],[http-path],[sni],[region-code],[tls-ja3-fingerprint],[user-ip]],[...] Specify up to 3 key type/name pairs to rate limit. Valid key types are: ◆ ip: each client IP address has this limit enforced separately @@ -204,6 +209,11 @@ OPTIONAL FLAGS the TLS session of the HTTPS request ◆ region-code: key type takes the value of the region code from which the request originates + ◆ tls-ja3-fingerprint: key type takes the value of JA3 TLS/SSL + fingerprint if the client connects using HTTPS, HTTP/2 or HTTP/3 + ◆ user-ip: key type takes the IP address of the originating client, + which is resolved based on user-ip-request-headers configured with + the security policy Key names are only applicable to the following key types: ◆ http-header: The name of the HTTP header whose value is taken as diff --git a/gcloud/alpha/compute/security-policies/rules/update b/gcloud/alpha/compute/security-policies/rules/update index 7a8fac946..4ff7851a8 100644 --- a/gcloud/alpha/compute/security-policies/rules/update +++ b/gcloud/alpha/compute/security-policies/rules/update @@ -10,8 +10,8 @@ SYNOPSIS [--conform-action=CONFORM_ACTION] [--description=DESCRIPTION] [--enforce-on-key=ENFORCE_ON_KEY] [--enforce-on-key-configs=[[all],[ip],[xff-ip], - [http-cookie=HTTP_COOKIE], - [http-header=HTTP_HEADER],[http-path],[sni],[region-code]],[...]] + [http-cookie=HTTP_COOKIE],[http-header=HTTP_HEADER],[http-path], + [sni],[region-code],[tls-ja3-fingerprint],[user-ip]],[...]] [--enforce-on-key-name=ENFORCE_ON_KEY_NAME] [--exceed-action=EXCEED_ACTION] [--exceed-action-rpc-status-code=EXCEED_ACTION_RPC_STATUS_CODE] @@ -134,11 +134,16 @@ FLAGS the TLS session of the HTTPS request ◆ region-code: key type takes the value of the region code from which the request originates + ◆ tls-ja3-fingerprint: key type takes the value of JA3 TLS/SSL + fingerprint if the client connects using HTTPS, HTTP/2 or HTTP/3 + ◆ user-ip: key type takes the IP address of the originating client, + which is resolved based on user-ip-request-headers configured with + the security policy ENFORCE_ON_KEY must be one of: ip, all, http-header, xff-ip, - http-cookie, http-path, sni, region-code. + http-cookie, http-path, sni, region-code, tls-ja3-fingerprint, user-ip. - --enforce-on-key-configs=[[all],[ip],[xff-ip],[http-cookie=HTTP_COOKIE],[http-header=HTTP_HEADER],[http-path],[sni],[region-code]],[...] + --enforce-on-key-configs=[[all],[ip],[xff-ip],[http-cookie=HTTP_COOKIE],[http-header=HTTP_HEADER],[http-path],[sni],[region-code],[tls-ja3-fingerprint],[user-ip]],[...] Specify up to 3 key type/name pairs to rate limit. Valid key types are: ◆ ip: each client IP address has this limit enforced separately @@ -154,6 +159,11 @@ FLAGS the TLS session of the HTTPS request ◆ region-code: key type takes the value of the region code from which the request originates + ◆ tls-ja3-fingerprint: key type takes the value of JA3 TLS/SSL + fingerprint if the client connects using HTTPS, HTTP/2 or HTTP/3 + ◆ user-ip: key type takes the IP address of the originating client, + which is resolved based on user-ip-request-headers configured with + the security policy Key names are only applicable to the following key types: ◆ http-header: The name of the HTTP header whose value is taken as diff --git a/gcloud/alpha/compute/tpus/tpu-vm/create b/gcloud/alpha/compute/tpus/tpu-vm/create index 7ad449bfd..b2767fa36 100644 --- a/gcloud/alpha/compute/tpus/tpu-vm/create +++ b/gcloud/alpha/compute/tpus/tpu-vm/create @@ -7,10 +7,11 @@ SYNOPSIS [--boot-disk=[KEY=VALUE,...]] [--data-disk=[mode=MODE],[source=SOURCE]] [--description=DESCRIPTION] [--internal-ips] [--labels=[KEY=VALUE,...]] [--metadata=[KEY=VALUE,...]] [--metadata-from-file=[KEY=VALUE,...]] - [--network=NETWORK; default="default"] [--preemptible] [--range=RANGE] - [--reserved] [--scopes=[SCOPES,...]] - [--service-account=SERVICE_ACCOUNT] [--shielded-secure-boot] [--spot] - [--subnetwork=SUBNETWORK] [--tags=[TAGS,...]] + [--network=NETWORK; default="default"] [--preemptible] + [--queue-count=QUEUE_COUNT] [--range=RANGE] [--reserved] + [--scopes=[SCOPES,...]] [--service-account=SERVICE_ACCOUNT] + [--shielded-secure-boot] [--spot] [--subnetwork=SUBNETWORK] + [--tags=[TAGS,...]] [--accelerator-type=ACCELERATOR_TYPE; default="v2-8" | --topology=TOPOLOGY --type=TYPE] [GCLOUD_WIDE_FLAG ...] @@ -155,6 +156,13 @@ OPTIONAL FLAGS Preemptible TPUs cannot be restarted. + --queue-count=QUEUE_COUNT + Specifies the networking queue count for TPU VM instances. Both Rx and + Tx queues will be set to this number. If it's not specified, a default + queue count will be assigned. For Virtio-net, each interface will get + min(floor(#vCPU / #vNIC), 32) queues. For gVNIC, each interface will + get min(floor(#vCPU / #vNIC / 2), 16) queues. + --range=RANGE CIDR Range for the TPU. diff --git a/gcloud/alpha/config/get b/gcloud/alpha/config/get index 245332eb6..23a6c5e39 100644 --- a/gcloud/alpha/config/get +++ b/gcloud/alpha/config/get @@ -298,6 +298,10 @@ AVAILABLE PROPERTIES Private Service Connect usage, see https://cloud.google.com/vpc/docs/configure-private-service-connect-apis#using-endpoints + config + Overrides API endpoint for gcloud infra-manager command group. + Defaults to https://config.googleapis.com/ + container Overrides API endpoint for gcloud container command group. Defaults to https://container.googleapis.com/ @@ -406,9 +410,6 @@ AVAILABLE PROPERTIES Overrides API endpoint for gcloud ids command group. Defaults to https://ids.googleapis.com/ - inframanager - Overrides API endpoint for gcloud infra-manager command group. - krmapihosting Overrides API endpoint for gcloud anthos config controller command group. Defaults to https://krmapihosting.googleapis.com/ @@ -572,6 +573,10 @@ AVAILABLE PROPERTIES Overrides API endpoint for gcloud ml vision command group. Defaults to https://vision.googleapis.com/ + vmmigration + Overrides API endpoint for gcloud migration vms command group. + Defaults to https://vmmigration.googleapis.com/ + vmwareengine Overrides API endpoint for gcloud vmware command group. Defaults to https://vmwareengine.googleapis.com/ diff --git a/gcloud/alpha/config/help b/gcloud/alpha/config/help index 393c381a7..8133262d3 100644 --- a/gcloud/alpha/config/help +++ b/gcloud/alpha/config/help @@ -330,6 +330,10 @@ AVAILABLE PROPERTIES Private Service Connect usage, see https://cloud.google.com/vpc/docs/configure-private-service-connect-apis#using-endpoints + config + Overrides API endpoint for gcloud infra-manager command group. + Defaults to https://config.googleapis.com/ + container Overrides API endpoint for gcloud container command group. Defaults to https://container.googleapis.com/ @@ -438,9 +442,6 @@ AVAILABLE PROPERTIES Overrides API endpoint for gcloud ids command group. Defaults to https://ids.googleapis.com/ - inframanager - Overrides API endpoint for gcloud infra-manager command group. - krmapihosting Overrides API endpoint for gcloud anthos config controller command group. Defaults to https://krmapihosting.googleapis.com/ @@ -604,6 +605,10 @@ AVAILABLE PROPERTIES Overrides API endpoint for gcloud ml vision command group. Defaults to https://vision.googleapis.com/ + vmmigration + Overrides API endpoint for gcloud migration vms command group. + Defaults to https://vmmigration.googleapis.com/ + vmwareengine Overrides API endpoint for gcloud vmware command group. Defaults to https://vmwareengine.googleapis.com/ diff --git a/gcloud/alpha/config/list b/gcloud/alpha/config/list index ac4ab31b3..6d73d9145 100644 --- a/gcloud/alpha/config/list +++ b/gcloud/alpha/config/list @@ -342,6 +342,10 @@ AVAILABLE PROPERTIES Private Service Connect usage, see https://cloud.google.com/vpc/docs/configure-private-service-connect-apis#using-endpoints + config + Overrides API endpoint for gcloud infra-manager command group. + Defaults to https://config.googleapis.com/ + container Overrides API endpoint for gcloud container command group. Defaults to https://container.googleapis.com/ @@ -450,9 +454,6 @@ AVAILABLE PROPERTIES Overrides API endpoint for gcloud ids command group. Defaults to https://ids.googleapis.com/ - inframanager - Overrides API endpoint for gcloud infra-manager command group. - krmapihosting Overrides API endpoint for gcloud anthos config controller command group. Defaults to https://krmapihosting.googleapis.com/ @@ -616,6 +617,10 @@ AVAILABLE PROPERTIES Overrides API endpoint for gcloud ml vision command group. Defaults to https://vision.googleapis.com/ + vmmigration + Overrides API endpoint for gcloud migration vms command group. + Defaults to https://vmmigration.googleapis.com/ + vmwareengine Overrides API endpoint for gcloud vmware command group. Defaults to https://vmwareengine.googleapis.com/ diff --git a/gcloud/alpha/config/set b/gcloud/alpha/config/set index 95212f302..28d65c999 100644 --- a/gcloud/alpha/config/set +++ b/gcloud/alpha/config/set @@ -345,6 +345,10 @@ AVAILABLE PROPERTIES Private Service Connect usage, see https://cloud.google.com/vpc/docs/configure-private-service-connect-apis#using-endpoints + config + Overrides API endpoint for gcloud infra-manager command group. + Defaults to https://config.googleapis.com/ + container Overrides API endpoint for gcloud container command group. Defaults to https://container.googleapis.com/ @@ -453,9 +457,6 @@ AVAILABLE PROPERTIES Overrides API endpoint for gcloud ids command group. Defaults to https://ids.googleapis.com/ - inframanager - Overrides API endpoint for gcloud infra-manager command group. - krmapihosting Overrides API endpoint for gcloud anthos config controller command group. Defaults to https://krmapihosting.googleapis.com/ @@ -619,6 +620,10 @@ AVAILABLE PROPERTIES Overrides API endpoint for gcloud ml vision command group. Defaults to https://vision.googleapis.com/ + vmmigration + Overrides API endpoint for gcloud migration vms command group. + Defaults to https://vmmigration.googleapis.com/ + vmwareengine Overrides API endpoint for gcloud vmware command group. Defaults to https://vmwareengine.googleapis.com/ diff --git a/gcloud/alpha/config/unset b/gcloud/alpha/config/unset index 011e64685..6b6ff6bb7 100644 --- a/gcloud/alpha/config/unset +++ b/gcloud/alpha/config/unset @@ -306,6 +306,10 @@ AVAILABLE PROPERTIES Private Service Connect usage, see https://cloud.google.com/vpc/docs/configure-private-service-connect-apis#using-endpoints + config + Overrides API endpoint for gcloud infra-manager command group. + Defaults to https://config.googleapis.com/ + container Overrides API endpoint for gcloud container command group. Defaults to https://container.googleapis.com/ @@ -414,9 +418,6 @@ AVAILABLE PROPERTIES Overrides API endpoint for gcloud ids command group. Defaults to https://ids.googleapis.com/ - inframanager - Overrides API endpoint for gcloud infra-manager command group. - krmapihosting Overrides API endpoint for gcloud anthos config controller command group. Defaults to https://krmapihosting.googleapis.com/ @@ -580,6 +581,10 @@ AVAILABLE PROPERTIES Overrides API endpoint for gcloud ml vision command group. Defaults to https://vision.googleapis.com/ + vmmigration + Overrides API endpoint for gcloud migration vms command group. + Defaults to https://vmmigration.googleapis.com/ + vmwareengine Overrides API endpoint for gcloud vmware command group. Defaults to https://vmwareengine.googleapis.com/ diff --git a/gcloud/alpha/container/aws/node-pools/help b/gcloud/alpha/container/aws/node-pools/help index a92dd8541..d4ab8e506 100644 --- a/gcloud/alpha/container/aws/node-pools/help +++ b/gcloud/alpha/container/aws/node-pools/help @@ -28,6 +28,9 @@ COMMANDS list (ALPHA) List node pools in an Anthos cluster on AWS. + rollback + (ALPHA) Rollback a node pool in an Anthos cluster on AWS. + update (ALPHA) Update a node pool in an Anthos cluster on AWS. diff --git a/gcloud/alpha/container/aws/node-pools/rollback b/gcloud/alpha/container/aws/node-pools/rollback new file mode 100644 index 000000000..9f2086838 --- /dev/null +++ b/gcloud/alpha/container/aws/node-pools/rollback @@ -0,0 +1,84 @@ +NAME + gcloud alpha container aws node-pools rollback - rollback a node pool in an + Anthos cluster on AWS + +SYNOPSIS + gcloud alpha container aws node-pools rollback + (NODE_POOL : --cluster=CLUSTER --location=LOCATION) [--async] + [--respect-pdb] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Rollback a node pool in an Anthos cluster on AWS. + +EXAMPLES + To roll back a canceled or failed update in node pool named my-node-pool in + a cluster named my-cluster managed in location us-west1, run: + + $ gcloud alpha container aws node-pools rollback my-node-pool \ + --cluster=my-cluster --location=us-west1 + +POSITIONAL ARGUMENTS + Node pool resource - node pool to rollback. 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 node_pool 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. + + NODE_POOL + ID of the node_pool or fully qualified identifier for the node_pool. + + To set the node_pool attribute: + ▸ provide the argument node_pool on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --cluster=CLUSTER + cluster of the node_pool. + + To set the cluster attribute: + ▸ provide the argument node_pool on the command line with a fully + specified name; + ▸ provide the argument --cluster on the command line. + + --location=LOCATION + Google Cloud location for the node_pool. + + To set the location attribute: + ▸ provide the argument node_pool on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ set the property container_aws/location. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --respect-pdb + Indicates whether the node pool rollback should respect pod disruption + budget. + +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 container aws node-pools rollback + diff --git a/gcloud/alpha/container/clusters/create b/gcloud/alpha/container/clusters/create index bb65e0634..af7c28eb4 100644 --- a/gcloud/alpha/container/clusters/create +++ b/gcloud/alpha/container/clusters/create @@ -73,11 +73,11 @@ SYNOPSIS [--workload-metadata=WORKLOAD_METADATA] [--workload-pool=WORKLOAD_POOL] [--workload-vulnerability-scanning=WORKLOAD_VULNERABILITY_SCANNING] [--additional-zones=ZONE,[ZONE,...] | --node-locations=ZONE,[ZONE,...]] - [--cluster-dns=CLUSTER_DNS --cluster-dns-domain=CLUSTER_DNS_DOMAIN - --cluster-dns-scope=CLUSTER_DNS_SCOPE] [--binauthz-policy-bindings=[name=BINAUTHZ_POLICY] --binauthz-evaluation-mode=BINAUTHZ_EVALUATION_MODE | --enable-binauthz] + [--cluster-dns=CLUSTER_DNS --cluster-dns-domain=CLUSTER_DNS_DOMAIN + --cluster-dns-scope=CLUSTER_DNS_SCOPE] [--dataplane-v2-observability-mode=DATAPLANE_V2_OBSERVABILITY_MODE | --disable-dataplane-v2-flow-observability | --enable-dataplane-v2-flow-observability] @@ -1343,6 +1343,27 @@ FLAGS --location us-central1-a \ --node-locations us-central1-a,us-central1-b + Flags for Binary Authorization: + + --binauthz-policy-bindings=[name=BINAUTHZ_POLICY] + The relative resource name of the Binary Authorization policy to + audit and/or enforce. GKE policies have the following format: + projects/{project_number}/platforms/gke/policies/{policy_id}. + + At most one of these can be specified: + + --binauthz-evaluation-mode=BINAUTHZ_EVALUATION_MODE + Enable Binary Authorization for this cluster. + BINAUTHZ_EVALUATION_MODE must be one of: disabled, policy-bindings, + policy-bindings-and-project-singleton-policy-enforce, + project-singleton-policy-enforce. + + --enable-binauthz + (DEPRECATED) Enable Binary Authorization for this cluster. + + The --enable-binauthz flag is deprecated. Please use + --binauthz-evaluation-mode instead. + ClusterDNS --cluster-dns=CLUSTER_DNS @@ -1372,27 +1393,6 @@ FLAGS vpc Configures the Cloud DNS zone to be private to the VPC Network. - Flags for Binary Authorization: - - --binauthz-policy-bindings=[name=BINAUTHZ_POLICY] - The relative resource name of the Binary Authorization policy to - audit and/or enforce. GKE policies have the following format: - projects/{project_number}/platforms/gke/policies/{policy_id}. - - At most one of these can be specified: - - --binauthz-evaluation-mode=BINAUTHZ_EVALUATION_MODE - Enable Binary Authorization for this cluster. - BINAUTHZ_EVALUATION_MODE must be one of: disabled, policy-bindings, - policy-bindings-and-project-singleton-policy-enforce, - project-singleton-policy-enforce. - - --enable-binauthz - (DEPRECATED) Enable Binary Authorization for this cluster. - - The --enable-binauthz flag is deprecated. Please use - --binauthz-evaluation-mode instead. - At most one of these can be specified: --dataplane-v2-observability-mode=DATAPLANE_V2_OBSERVABILITY_MODE diff --git a/gcloud/alpha/container/clusters/update b/gcloud/alpha/container/clusters/update index 460246c99..181a5afec 100644 --- a/gcloud/alpha/container/clusters/update +++ b/gcloud/alpha/container/clusters/update @@ -45,8 +45,6 @@ SYNOPSIS | --additional-pod-ipv4-ranges=NAME,[NAME,...] --remove-additional-pod-ipv4-ranges=NAME,[NAME,...] | --additional-zones=[ZONE,...] | --node-locations=ZONE,[ZONE,...] - | --cluster-dns=CLUSTER_DNS --cluster-dns-domain=CLUSTER_DNS_DOMAIN - --cluster-dns-scope=CLUSTER_DNS_SCOPE | --binauthz-policy-bindings=[name=BINAUTHZ_POLICY] --binauthz-evaluation-mode=BINAUTHZ_EVALUATION_MODE | --enable-binauthz | --clear-maintenance-window @@ -62,6 +60,8 @@ SYNOPSIS | --enable-network-egress-metering --enable-resource-consumption-metering --resource-usage-bigquery-dataset=RESOURCE_USAGE_BIGQUERY_DATASET + | --cluster-dns=CLUSTER_DNS --cluster-dns-domain=CLUSTER_DNS_DOMAIN + --cluster-dns-scope=CLUSTER_DNS_SCOPE | --dataplane-v2-observability-mode=DATAPLANE_V2_OBSERVABILITY_MODE | --disable-dataplane-v2-flow-observability | --enable-dataplane-v2-flow-observability @@ -759,35 +759,6 @@ REQUIRED FLAGS --location us-central1-a \ --node-locations us-central1-a,us-central1-b - ClusterDNS - - --cluster-dns=CLUSTER_DNS - DNS provider to use for this cluster. CLUSTER_DNS must be one of: - - clouddns - Selects Cloud DNS as the DNS provider for the cluster. - default - Selects the default DNS provider (kube-dns) for the cluster. - kubedns - Selects Kube DNS as the DNS provider for the cluster. - - --cluster-dns-domain=CLUSTER_DNS_DOMAIN - DNS domain for this cluster. The default value is cluster.local. - This is configurable when --cluster-dns=clouddns and - --cluster-dns-scope=vpc are set. The value must be a valid DNS - subdomain as defined in RFC 1123. - - --cluster-dns-scope=CLUSTER_DNS_SCOPE - DNS scope for the Cloud DNS zone created - valid only with - --cluster-dns=clouddns. Defaults to cluster. - - CLUSTER_DNS_SCOPE must be one of: - - cluster - Configures the Cloud DNS zone to be private to the cluster. - vpc - Configures the Cloud DNS zone to be private to the VPC Network. - Flags for Binary Authorization: --binauthz-policy-bindings=[name=BINAUTHZ_POLICY] @@ -946,6 +917,35 @@ REQUIRED FLAGS $ gcloud alpha container clusters update example-cluster \ --resource-usage-bigquery-dataset=example_bigquery_dataset_name + ClusterDNS + + --cluster-dns=CLUSTER_DNS + DNS provider to use for this cluster. CLUSTER_DNS must be one of: + + clouddns + Selects Cloud DNS as the DNS provider for the cluster. + default + Selects the default DNS provider (kube-dns) for the cluster. + kubedns + Selects Kube DNS as the DNS provider for the cluster. + + --cluster-dns-domain=CLUSTER_DNS_DOMAIN + DNS domain for this cluster. The default value is cluster.local. + This is configurable when --cluster-dns=clouddns and + --cluster-dns-scope=vpc are set. The value must be a valid DNS + subdomain as defined in RFC 1123. + + --cluster-dns-scope=CLUSTER_DNS_SCOPE + DNS scope for the Cloud DNS zone created - valid only with + --cluster-dns=clouddns. Defaults to cluster. + + CLUSTER_DNS_SCOPE must be one of: + + cluster + Configures the Cloud DNS zone to be private to the cluster. + vpc + Configures the Cloud DNS zone to be private to the VPC Network. + At most one of these can be specified: --dataplane-v2-observability-mode=DATAPLANE_V2_OBSERVABILITY_MODE diff --git a/gcloud/alpha/container/fleet/clusterupgrade/create b/gcloud/alpha/container/fleet/clusterupgrade/create index 555683682..e5ca99149 100644 --- a/gcloud/alpha/container/fleet/clusterupgrade/create +++ b/gcloud/alpha/container/fleet/clusterupgrade/create @@ -14,6 +14,12 @@ DESCRIPTION (ALPHA) Create the clusterupgrade feature for a fleet within a given project. +EXAMPLES + To create the clusterupgrade feature for the current fleet, run: + + $ gcloud alpha container fleet clusterupgrade create \ + --default-upgrade-soaking=DEFAULT_UPGRADE_SOAKING + FLAGS --default-upgrade-soaking=DEFAULT_UPGRADE_SOAKING Configures the default soaking duration for each upgrade propagating @@ -83,5 +89,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. + access allowlist. These variants are also available: + + $ gcloud container fleet clusterupgrade create + + $ gcloud beta container fleet clusterupgrade create diff --git a/gcloud/alpha/container/fleet/clusterupgrade/describe b/gcloud/alpha/container/fleet/clusterupgrade/describe index 32774b007..ae85a6834 100644 --- a/gcloud/alpha/container/fleet/clusterupgrade/describe +++ b/gcloud/alpha/container/fleet/clusterupgrade/describe @@ -42,5 +42,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. + access allowlist. These variants are also available: + + $ gcloud container fleet clusterupgrade describe + + $ gcloud beta container fleet clusterupgrade describe diff --git a/gcloud/alpha/container/fleet/clusterupgrade/help b/gcloud/alpha/container/fleet/clusterupgrade/help index cbaea02e7..1832bb683 100644 --- a/gcloud/alpha/container/fleet/clusterupgrade/help +++ b/gcloud/alpha/container/fleet/clusterupgrade/help @@ -33,5 +33,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. + access allowlist. These variants are also available: + + $ gcloud container fleet clusterupgrade + + $ gcloud beta container fleet clusterupgrade diff --git a/gcloud/alpha/container/fleet/clusterupgrade/update b/gcloud/alpha/container/fleet/clusterupgrade/update index 38af93cdf..0ff30c30e 100644 --- a/gcloud/alpha/container/fleet/clusterupgrade/update +++ b/gcloud/alpha/container/fleet/clusterupgrade/update @@ -15,6 +15,12 @@ DESCRIPTION (ALPHA) Update the clusterupgrade feature for a fleet within a given project. +EXAMPLES + To update the clusterupgrade feature for the current fleet, run: + + $ gcloud alpha container fleet clusterupgrade update \ + --default-upgrade-soaking=DEFAULT_UPGRADE_SOAKING + FLAGS --default-upgrade-soaking=DEFAULT_UPGRADE_SOAKING Configures the default soaking duration for each upgrade propagating @@ -111,5 +117,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. + access allowlist. These variants are also available: + + $ gcloud container fleet clusterupgrade update + + $ gcloud beta container fleet clusterupgrade update diff --git a/gcloud/alpha/container/fleet/create b/gcloud/alpha/container/fleet/create index bf5bb8d40..7162ee9b8 100644 --- a/gcloud/alpha/container/fleet/create +++ b/gcloud/alpha/container/fleet/create @@ -5,7 +5,7 @@ SYNOPSIS gcloud alpha container fleet create [--async] [--display-name=DISPLAY_NAME] [--labels=[KEY=VALUE,...]] [--binauthz-evaluation-mode=BINAUTHZ_EVALUATION_MODE - --binauthz-policy-bindings=[name=BINAUTHZ_POLICY,...] + --binauthz-policy-bindings=[name=BINAUTHZ_POLICY] --security-posture=SECURITY_POSTURE --workload-vulnerability-scanning=WORKLOAD_VULNERABILITY_SCANNING] [GCLOUD_WIDE_FLAG ...] @@ -50,11 +50,11 @@ FLAGS fleet, $ gcloud alpha container fleet create \ - --binauthz-evaluation-mode=POLICY_BINDINGS + --binauthz-evaluation-mode=policy-bindings - BINAUTHZ_EVALUATION_MODE must be one of: DISABLED, POLICY_BINDINGS. + BINAUTHZ_EVALUATION_MODE must be one of: disabled, policy-bindings. - --binauthz-policy-bindings=[name=BINAUTHZ_POLICY,...] + --binauthz-policy-bindings=[name=BINAUTHZ_POLICY] The relative resource name of the Binary Authorization policy to audit and/or enforce. GKE policies have the following format: projects/{project_number}/platforms/gke/policies/{policy_id}. diff --git a/gcloud/alpha/container/fleet/mesh/debug/help b/gcloud/alpha/container/fleet/mesh/debug/help new file mode 100644 index 000000000..abe33acc2 --- /dev/null +++ b/gcloud/alpha/container/fleet/mesh/debug/help @@ -0,0 +1,20 @@ +NAME + gcloud alpha container fleet mesh debug - debug Service Mesh memberships + +SYNOPSIS + gcloud alpha container fleet mesh debug COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Debug Service Mesh memberships. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + 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/container/fleet/mesh/help b/gcloud/alpha/container/fleet/mesh/help index fc0509666..7860400be 100644 --- a/gcloud/alpha/container/fleet/mesh/help +++ b/gcloud/alpha/container/fleet/mesh/help @@ -2,7 +2,7 @@ NAME gcloud alpha container fleet mesh - manage Service Mesh Feature SYNOPSIS - gcloud alpha container fleet mesh COMMAND [GCLOUD_WIDE_FLAG ...] + gcloud alpha container fleet mesh GROUP | COMMAND [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Manage Service Mesh Feature. @@ -12,6 +12,12 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. +GROUPS + GROUP is one of the following: + + debug + (ALPHA) Debug Service Mesh memberships. + COMMANDS COMMAND is one of the following: diff --git a/gcloud/alpha/container/fleet/update b/gcloud/alpha/container/fleet/update index a87a413ed..eeb01540f 100644 --- a/gcloud/alpha/container/fleet/update +++ b/gcloud/alpha/container/fleet/update @@ -5,7 +5,7 @@ SYNOPSIS gcloud alpha container fleet update [--async] [--display-name=DISPLAY_NAME] [--update-labels=[KEY=VALUE,...]] [--binauthz-evaluation-mode=BINAUTHZ_EVALUATION_MODE - --binauthz-policy-bindings=[name=BINAUTHZ_POLICY,...] + --binauthz-policy-bindings=[name=BINAUTHZ_POLICY] --security-posture=SECURITY_POSTURE --workload-vulnerability-scanning=WORKLOAD_VULNERABILITY_SCANNING] [--clear-labels | --remove-labels=[KEY,...]] [GCLOUD_WIDE_FLAG ...] @@ -51,11 +51,11 @@ FLAGS fleet, $ gcloud alpha container fleet update \ - --binauthz-evaluation-mode=POLICY_BINDINGS + --binauthz-evaluation-mode=policy-bindings - BINAUTHZ_EVALUATION_MODE must be one of: DISABLED, POLICY_BINDINGS. + BINAUTHZ_EVALUATION_MODE must be one of: disabled, policy-bindings. - --binauthz-policy-bindings=[name=BINAUTHZ_POLICY,...] + --binauthz-policy-bindings=[name=BINAUTHZ_POLICY] The relative resource name of the Binary Authorization policy to audit and/or enforce. GKE policies have the following format: projects/{project_number}/platforms/gke/policies/{policy_id}. diff --git a/gcloud/alpha/container/hub/clusterupgrade/create b/gcloud/alpha/container/hub/clusterupgrade/create index ed3f79b0d..e0651c8ba 100644 --- a/gcloud/alpha/container/hub/clusterupgrade/create +++ b/gcloud/alpha/container/hub/clusterupgrade/create @@ -14,6 +14,12 @@ DESCRIPTION (ALPHA) Create the clusterupgrade feature for a fleet within a given project. +EXAMPLES + To create the clusterupgrade feature for the current fleet, run: + + $ gcloud alpha container hub clusterupgrade create \ + --default-upgrade-soaking=DEFAULT_UPGRADE_SOAKING + FLAGS --default-upgrade-soaking=DEFAULT_UPGRADE_SOAKING Configures the default soaking duration for each upgrade propagating @@ -83,5 +89,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. + access allowlist. These variants are also available: + + $ gcloud container hub clusterupgrade create + + $ gcloud beta container hub clusterupgrade create diff --git a/gcloud/alpha/container/hub/clusterupgrade/describe b/gcloud/alpha/container/hub/clusterupgrade/describe index 3d2699d72..68baa2e30 100644 --- a/gcloud/alpha/container/hub/clusterupgrade/describe +++ b/gcloud/alpha/container/hub/clusterupgrade/describe @@ -42,5 +42,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. + access allowlist. These variants are also available: + + $ gcloud container hub clusterupgrade describe + + $ gcloud beta container hub clusterupgrade describe diff --git a/gcloud/alpha/container/hub/clusterupgrade/help b/gcloud/alpha/container/hub/clusterupgrade/help index 581adcd42..e49a360f0 100644 --- a/gcloud/alpha/container/hub/clusterupgrade/help +++ b/gcloud/alpha/container/hub/clusterupgrade/help @@ -33,5 +33,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. + access allowlist. These variants are also available: + + $ gcloud container hub clusterupgrade + + $ gcloud beta container hub clusterupgrade diff --git a/gcloud/alpha/container/hub/clusterupgrade/update b/gcloud/alpha/container/hub/clusterupgrade/update index 0ccf5d1a0..dc34b16ef 100644 --- a/gcloud/alpha/container/hub/clusterupgrade/update +++ b/gcloud/alpha/container/hub/clusterupgrade/update @@ -15,6 +15,12 @@ DESCRIPTION (ALPHA) Update the clusterupgrade feature for a fleet within a given project. +EXAMPLES + To update the clusterupgrade feature for the current fleet, run: + + $ gcloud alpha container hub clusterupgrade update \ + --default-upgrade-soaking=DEFAULT_UPGRADE_SOAKING + FLAGS --default-upgrade-soaking=DEFAULT_UPGRADE_SOAKING Configures the default soaking duration for each upgrade propagating @@ -111,5 +117,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. + access allowlist. These variants are also available: + + $ gcloud container hub clusterupgrade update + + $ gcloud beta container hub clusterupgrade update diff --git a/gcloud/alpha/container/hub/create b/gcloud/alpha/container/hub/create index 9d93496b1..2b492e646 100644 --- a/gcloud/alpha/container/hub/create +++ b/gcloud/alpha/container/hub/create @@ -5,7 +5,7 @@ SYNOPSIS gcloud alpha container hub create [--async] [--display-name=DISPLAY_NAME] [--labels=[KEY=VALUE,...]] [--binauthz-evaluation-mode=BINAUTHZ_EVALUATION_MODE - --binauthz-policy-bindings=[name=BINAUTHZ_POLICY,...] + --binauthz-policy-bindings=[name=BINAUTHZ_POLICY] --security-posture=SECURITY_POSTURE --workload-vulnerability-scanning=WORKLOAD_VULNERABILITY_SCANNING] [GCLOUD_WIDE_FLAG ...] @@ -50,11 +50,11 @@ FLAGS fleet, $ gcloud alpha container hub create \ - --binauthz-evaluation-mode=POLICY_BINDINGS + --binauthz-evaluation-mode=policy-bindings - BINAUTHZ_EVALUATION_MODE must be one of: DISABLED, POLICY_BINDINGS. + BINAUTHZ_EVALUATION_MODE must be one of: disabled, policy-bindings. - --binauthz-policy-bindings=[name=BINAUTHZ_POLICY,...] + --binauthz-policy-bindings=[name=BINAUTHZ_POLICY] The relative resource name of the Binary Authorization policy to audit and/or enforce. GKE policies have the following format: projects/{project_number}/platforms/gke/policies/{policy_id}. diff --git a/gcloud/alpha/container/hub/mesh/debug/help b/gcloud/alpha/container/hub/mesh/debug/help new file mode 100644 index 000000000..6335c68d7 --- /dev/null +++ b/gcloud/alpha/container/hub/mesh/debug/help @@ -0,0 +1,20 @@ +NAME + gcloud alpha container hub mesh debug - debug Service Mesh memberships + +SYNOPSIS + gcloud alpha container hub mesh debug COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Debug Service Mesh memberships. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + 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/container/hub/mesh/help b/gcloud/alpha/container/hub/mesh/help index f60098d82..02cd7face 100644 --- a/gcloud/alpha/container/hub/mesh/help +++ b/gcloud/alpha/container/hub/mesh/help @@ -2,7 +2,7 @@ NAME gcloud alpha container hub mesh - manage Service Mesh Feature SYNOPSIS - gcloud alpha container hub mesh COMMAND [GCLOUD_WIDE_FLAG ...] + gcloud alpha container hub mesh GROUP | COMMAND [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Manage Service Mesh Feature. @@ -12,6 +12,12 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. +GROUPS + GROUP is one of the following: + + debug + (ALPHA) Debug Service Mesh memberships. + COMMANDS COMMAND is one of the following: diff --git a/gcloud/alpha/container/hub/update b/gcloud/alpha/container/hub/update index 8c4cccf1d..3c311860e 100644 --- a/gcloud/alpha/container/hub/update +++ b/gcloud/alpha/container/hub/update @@ -5,7 +5,7 @@ SYNOPSIS gcloud alpha container hub update [--async] [--display-name=DISPLAY_NAME] [--update-labels=[KEY=VALUE,...]] [--binauthz-evaluation-mode=BINAUTHZ_EVALUATION_MODE - --binauthz-policy-bindings=[name=BINAUTHZ_POLICY,...] + --binauthz-policy-bindings=[name=BINAUTHZ_POLICY] --security-posture=SECURITY_POSTURE --workload-vulnerability-scanning=WORKLOAD_VULNERABILITY_SCANNING] [--clear-labels | --remove-labels=[KEY,...]] [GCLOUD_WIDE_FLAG ...] @@ -51,11 +51,11 @@ FLAGS fleet, $ gcloud alpha container hub update \ - --binauthz-evaluation-mode=POLICY_BINDINGS + --binauthz-evaluation-mode=policy-bindings - BINAUTHZ_EVALUATION_MODE must be one of: DISABLED, POLICY_BINDINGS. + BINAUTHZ_EVALUATION_MODE must be one of: disabled, policy-bindings. - --binauthz-policy-bindings=[name=BINAUTHZ_POLICY,...] + --binauthz-policy-bindings=[name=BINAUTHZ_POLICY] The relative resource name of the Binary Authorization policy to audit and/or enforce. GKE policies have the following format: projects/{project_number}/platforms/gke/policies/{policy_id}. diff --git a/gcloud/alpha/container/node-pools/update b/gcloud/alpha/container/node-pools/update index 079f3debe..b195c7ac6 100644 --- a/gcloud/alpha/container/node-pools/update +++ b/gcloud/alpha/container/node-pools/update @@ -149,9 +149,9 @@ REQUIRED FLAGS --resource-manager-tags=[KEY=VALUE,...] Replaces all the user specified resource manager tags on all nodes in - an existing standard or auto-provisioned node pool in a Standard - cluster with the given comma-separated resource manager tags that has - the GCE_FIREWALL purpose. + an existing node pool in a Standard cluster with the given + comma-separated resource manager tags that has the GCE_FIREWALL + purpose. Examples: diff --git a/gcloud/alpha/deploy/apply b/gcloud/alpha/deploy/apply index 1209be460..71c70a5b8 100644 --- a/gcloud/alpha/deploy/apply +++ b/gcloud/alpha/deploy/apply @@ -1,7 +1,7 @@ NAME gcloud alpha deploy apply - applies a yaml configuration containing - Delivery Pipeline(s), Target(s) and Automation(s) declarative - definitions + Delivery Pipeline(s), Target(s), Custom Target Type(s), and + Automation(s) declarative definitions SYNOPSIS gcloud alpha deploy apply --file=FILE [--region=REGION] @@ -9,7 +9,8 @@ SYNOPSIS DESCRIPTION (ALPHA) Applies a yaml configuration containing Delivery Pipeline(s), - Target(s) and Automation(s) declarative definitions. + Target(s), Custom Target Type(s), and Automation(s) declarative + definitions. EXAMPLES To apply a Cloud Deploy YAML file deploy.yaml: diff --git a/gcloud/alpha/deploy/custom-target-types/delete b/gcloud/alpha/deploy/custom-target-types/delete new file mode 100644 index 000000000..fcc4a8450 --- /dev/null +++ b/gcloud/alpha/deploy/custom-target-types/delete @@ -0,0 +1,78 @@ +NAME + gcloud alpha deploy custom-target-types delete - delete a custom target + type + +SYNOPSIS + gcloud alpha deploy custom-target-types delete + (CUSTOM_TARGET_TYPE : --region=REGION) [--async] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Delete a custom target type for a specified region. + +EXAMPLES + The following command will delete custom target type + test-custom-target-type, in region us-central1: + + $ gcloud alpha deploy custom-target-types delete \ + test-custom-target-type --region=us-central1 + +POSITIONAL ARGUMENTS + Custom target type resource - The name of the custom target type to + delete. The arguments in this group can be used to specify the attributes + of this resource. (NOTE) Some attributes are not given arguments in this + group but can be set in other ways. + + To set the project attribute: + ◆ provide the argument custom_target_type 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. + + CUSTOM_TARGET_TYPE + ID of the custom target type or fully qualified identifier for the + custom target type. + + To set the custom_target_type attribute: + ▸ provide the argument custom_target_type on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --region=REGION + Location of the custom target type. + + To set the region attribute: + ▸ provide the argument custom_target_type on the command line with + a fully specified name; + ▸ provide the argument --region on the command line; + ▸ set the property deploy/region. + +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 clouddeploy/v1 API. The full documentation for this + API can be found at: https://cloud.google.com/deploy/ + +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 deploy custom-target-types delete + + $ gcloud beta deploy custom-target-types delete + diff --git a/gcloud/alpha/deploy/custom-target-types/describe b/gcloud/alpha/deploy/custom-target-types/describe new file mode 100644 index 000000000..c536e5c82 --- /dev/null +++ b/gcloud/alpha/deploy/custom-target-types/describe @@ -0,0 +1,73 @@ +NAME + gcloud alpha deploy custom-target-types describe - show details for a + custom target type + +SYNOPSIS + gcloud alpha deploy custom-target-types describe + (CUSTOM_TARGET_TYPE : --region=REGION) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Show details for a specified custom target type. + +EXAMPLES + To show details about a custom target type test-custom-target-type in + region us-central, run: + + $ gcloud alpha deploy custom-target-types describe \ + test-custom-target-type --region=us-central1 + +POSITIONAL ARGUMENTS + Custom target type resource - The name of the custom target type you want + to describe. The arguments in this group can be used to specify the + attributes of this resource. (NOTE) Some attributes are not given + arguments in this group but can be set in other ways. + + To set the project attribute: + ◆ provide the argument custom_target_type 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. + + CUSTOM_TARGET_TYPE + ID of the custom target type or fully qualified identifier for the + custom target type. + + To set the custom_target_type attribute: + ▸ provide the argument custom_target_type on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --region=REGION + Location of the custom target type. + + To set the region attribute: + ▸ provide the argument custom_target_type on the command line with + a fully specified name; + ▸ provide the argument --region on the command line; + ▸ set the property deploy/region. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the clouddeploy/v1 API. The full documentation for this + API can be found at: https://cloud.google.com/deploy/ + +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 deploy custom-target-types describe + + $ gcloud beta deploy custom-target-types describe + diff --git a/gcloud/alpha/deploy/custom-target-types/export b/gcloud/alpha/deploy/custom-target-types/export new file mode 100644 index 000000000..068e07b63 --- /dev/null +++ b/gcloud/alpha/deploy/custom-target-types/export @@ -0,0 +1,77 @@ +NAME + gcloud alpha deploy custom-target-types export - returns the .yaml + definition of the specified custom target type + +SYNOPSIS + gcloud alpha deploy custom-target-types export + (CUSTOM_TARGET_TYPE : --region=REGION) [--destination=DESTINATION] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) The exported yaml definition can be applied by deploy apply + command. + +EXAMPLES + To return the .yaml definition of the custom target type + test-custom-target-type, in region us-central1, run: + + $ gcloud alpha deploy custom-target-types export \ + test-custom-target-type --region=us-central1 + +POSITIONAL ARGUMENTS + Custom target type resource - The name of the Custom Target Type. 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 custom_target_type 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. + + CUSTOM_TARGET_TYPE + ID of the custom_target_type or fully qualified identifier for the + custom_target_type. + + To set the custom_target_type attribute: + ▸ provide the argument custom_target_type on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --region=REGION + The Cloud region for the custom_target_type. Alternatively, set the + property [deploy/region]. + + To set the region attribute: + ▸ provide the argument custom_target_type on the command line with + a fully specified name; + ▸ provide the argument --region on the command line; + ▸ set the property deploy/region. + +FLAGS + --destination=DESTINATION + Path to a YAML file where the configuration will be exported. + Alternatively, you may omit this flag to write to standard output. + +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 deploy custom-target-types export + + $ gcloud beta deploy custom-target-types export + diff --git a/gcloud/alpha/deploy/custom-target-types/help b/gcloud/alpha/deploy/custom-target-types/help new file mode 100644 index 000000000..4ec03cce0 --- /dev/null +++ b/gcloud/alpha/deploy/custom-target-types/help @@ -0,0 +1,41 @@ +NAME + gcloud alpha deploy custom-target-types - create and manage Custom Target + Type resources for Cloud Deploy + +SYNOPSIS + gcloud alpha deploy custom-target-types COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Create and manage Custom Target Type resources for Cloud Deploy. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + delete + (ALPHA) Delete a custom target type. + + describe + (ALPHA) Show details for a custom target type. + + export + (ALPHA) Returns the .yaml definition of the specified custom target + type. + + list + (ALPHA) List the custom target types. + +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 deploy custom-target-types + + $ gcloud beta deploy custom-target-types + diff --git a/gcloud/alpha/infra-manager/deployments/list b/gcloud/alpha/deploy/custom-target-types/list similarity index 66% rename from gcloud/alpha/infra-manager/deployments/list rename to gcloud/alpha/deploy/custom-target-types/list index e909c10a1..5a0fb5c4e 100644 --- a/gcloud/alpha/infra-manager/deployments/list +++ b/gcloud/alpha/deploy/custom-target-types/list @@ -1,37 +1,37 @@ NAME - gcloud alpha infra-manager deployments list - list deployments + gcloud alpha deploy custom-target-types list - list the custom target types SYNOPSIS - gcloud alpha infra-manager deployments list --location=LOCATION + gcloud alpha deploy custom-target-types list [--region=REGION] [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) List deployments + (ALPHA) List the custom target types for a specified region. EXAMPLES - To list all deployments at location us-central1, run: + To list the custom target types in region us-central1, run: - $ gcloud alpha infra-manager deployments list --location=us-central1 + $ gcloud alpha deploy custom-target-types list --region=us-central1 -REQUIRED FLAGS - Location resource - Location to list deployments This represents a Cloud - resource. (NOTE) Some attributes are not given arguments in this group but - can be set in other ways. +FLAGS + Location resource - The region for which you want to list the custom + target types. 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 + ◆ provide the argument --region on the command line with a fully specified name; - ◆ set the property core/project; - ◆ provide the argument --project on the command line. + ◆ set the property deploy/region with a fully specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. - This must be specified. - - --location=LOCATION + --region=REGION ID of the location or fully qualified identifier for the location. - To set the location attribute: - ▸ provide the argument --location on the command line. + To set the region attribute: + ▸ provide the argument --region on the command line; + ▸ set the property deploy/region. LIST COMMAND FLAGS --filter=EXPRESSION @@ -74,14 +74,16 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. API REFERENCE - This command uses the config/v1 API. The full documentation for this API - can be found at: https://cloud.google.com/infrastructure-manager/docs + This command uses the clouddeploy/v1 API. The full documentation for this + API can be found at: https://cloud.google.com/deploy/ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: - $ gcloud infra-manager deployments list + $ gcloud deploy custom-target-types list + + $ gcloud beta deploy custom-target-types list diff --git a/gcloud/alpha/deploy/delete b/gcloud/alpha/deploy/delete index c84e8899f..25e968d8c 100644 --- a/gcloud/alpha/deploy/delete +++ b/gcloud/alpha/deploy/delete @@ -1,17 +1,17 @@ NAME - gcloud alpha deploy delete - deletes delivery pipeline(s) and target(s) in - a yaml configuration + gcloud alpha deploy delete - deletes Delivery Pipeline(s), Target(s), + Custom Target Type(s), and Automation(s) in a yaml configuration SYNOPSIS gcloud alpha deploy delete --file=FILE [--force] [--region=REGION] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) Deletes delivery pipeline(s) and target(s) in a yaml configuration. + (ALPHA) Deletes Delivery Pipeline(s), Target(s), Custom Target Type(s), and + Automation(s) in a yaml configuration. EXAMPLES - To delete the delivery pipeline(s) and target(s) in a Cloud Deploy YAML - file deploy.yaml: + To delete the resources in a Cloud Deploy YAML file deploy.yaml: $ gcloud alpha deploy delete --file=deploy.yaml --region=us-central1 diff --git a/gcloud/alpha/deploy/help b/gcloud/alpha/deploy/help index df64edd03..d2fb4e46e 100644 --- a/gcloud/alpha/deploy/help +++ b/gcloud/alpha/deploy/help @@ -21,6 +21,10 @@ GROUPS automations (ALPHA) Manages Automations resources for Cloud Deploy. + custom-target-types + (ALPHA) Create and manage Custom Target Type resources for Cloud + Deploy. + delivery-pipelines (ALPHA) Create and manage Delivery Pipeline resources for Cloud Deploy. @@ -41,11 +45,12 @@ COMMANDS apply (ALPHA) Applies a yaml configuration containing Delivery Pipeline(s), - Target(s) and Automation(s) declarative definitions. + Target(s), Custom Target Type(s), and Automation(s) declarative + definitions. delete - (ALPHA) Deletes delivery pipeline(s) and target(s) in a yaml - configuration. + (ALPHA) Deletes Delivery Pipeline(s), Target(s), Custom Target Type(s), + and Automation(s) in a yaml configuration. get-config (ALPHA) Get the Cloud Deploy config for the provided region and diff --git a/gcloud/alpha/edge-cloud/networking/subnets/create b/gcloud/alpha/edge-cloud/networking/subnets/create index d180b2bfd..3ab910af4 100644 --- a/gcloud/alpha/edge-cloud/networking/subnets/create +++ b/gcloud/alpha/edge-cloud/networking/subnets/create @@ -4,10 +4,10 @@ NAME SYNOPSIS gcloud alpha edge-cloud networking subnets create - (SUBNET : --location=LOCATION --zone=ZONE) - --ipv4-range=[IPV4_RANGE,...] --network=NETWORK [--async] - [--description=DESCRIPTION] [--ipv6-range=[IPV6_RANGE,...]] - [--labels=[KEY=VALUE,...]] [--vlan-id=VLAN_ID] [GCLOUD_WIDE_FLAG ...] + (SUBNET : --location=LOCATION --zone=ZONE) --network=NETWORK [--async] + [--description=DESCRIPTION] [--ipv4-range=[IPV4_RANGE,...]] + [--ipv6-range=[IPV6_RANGE,...]] [--labels=[KEY=VALUE,...]] + [--vlan-id=VLAN_ID] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Create a new Distributed Cloud Edge Network subnet. @@ -63,10 +63,6 @@ POSITIONAL ARGUMENTS ▸ provide the argument --zone on the command line. REQUIRED FLAGS - --ipv4-range=[IPV4_RANGE,...] - The ranges of ipv4 addresses that are owned by this subnetwork in CIDR - format. - --network=NETWORK The network that this subnetwork belongs to. @@ -78,6 +74,10 @@ OPTIONAL FLAGS --description=DESCRIPTION An optional, textual description for the subnet. + --ipv4-range=[IPV4_RANGE,...] + The ranges of ipv4 addresses that are owned by this subnetwork in CIDR + format. + --ipv6-range=[IPV6_RANGE,...] The ranges of ipv6 addresses that are owned by this subnetwork in CIDR format. diff --git a/gcloud/alpha/firestore/locations/describe b/gcloud/alpha/firestore/locations/describe new file mode 100644 index 000000000..565448806 --- /dev/null +++ b/gcloud/alpha/firestore/locations/describe @@ -0,0 +1,36 @@ +NAME + gcloud alpha firestore locations describe - describes a location available + to Google Cloud Firestore + +SYNOPSIS + gcloud alpha firestore locations describe --location=LOCATION + [GCLOUD_WIDE_FLAG ...] + +EXAMPLES + To describe a Firestore locations with us-east1. + + $ gcloud alpha firestore locations describe --location="us-east1" + +REQUIRED FLAGS + --location=LOCATION + The location to operate on. Available locations are listed at + https://cloud.google.com/firestore/docs/locations. + + For example, to operate on location us-east1: + + $ gcloud alpha firestore locations describe --location='us-east1' + +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/firestore/locations/help b/gcloud/alpha/firestore/locations/help index a77c2f29a..84d56a737 100644 --- a/gcloud/alpha/firestore/locations/help +++ b/gcloud/alpha/firestore/locations/help @@ -16,6 +16,9 @@ GCLOUD WIDE FLAGS COMMANDS COMMAND is one of the following: + describe + (ALPHA) Describes a location available to Google Cloud Firestore. + list (ALPHA) List locations available to Google Cloud Firestore. diff --git a/gcloud/alpha/functions/deploy b/gcloud/alpha/functions/deploy index 60c6c6a25..eca2a4e64 100644 --- a/gcloud/alpha/functions/deploy +++ b/gcloud/alpha/functions/deploy @@ -9,6 +9,7 @@ SYNOPSIS [--gen2] [--ignore-file=IGNORE_FILE] [--ingress-settings=INGRESS_SETTINGS] [--retry] [--run-service-account=RUN_SERVICE_ACCOUNT] [--runtime=RUNTIME] + [--runtime-update-policy=RUNTIME_UPDATE_POLICY] [--security-level=SECURITY_LEVEL; default="secure-always"] [--serve-all-traffic-latest-revision] [--service-account=SERVICE_ACCOUNT] [--source=SOURCE] @@ -168,6 +169,10 @@ FLAGS For a list of available runtimes, run gcloud functions runtimes list. + --runtime-update-policy=RUNTIME_UPDATE_POLICY + Runtime update policy for the 1st Gen function being deployed. The + option on-deploy is used by default. + --security-level=SECURITY_LEVEL; default="secure-always" Security level controls whether a function's URL supports HTTPS only or both HTTP and HTTPS. By default, secure-always will be used, meaning diff --git a/gcloud/alpha/infra-manager/deployments/apply b/gcloud/alpha/infra-manager/deployments/apply deleted file mode 100644 index 94aef452a..000000000 --- a/gcloud/alpha/infra-manager/deployments/apply +++ /dev/null @@ -1,250 +0,0 @@ -NAME - gcloud alpha infra-manager deployments apply - create or update a - deployment - -SYNOPSIS - gcloud alpha infra-manager deployments apply - (DEPLOYMENT : --location=LOCATION) - [--artifacts-gcs-bucket=ARTIFACTS_GCS_BUCKET] [--async] - [--import-existing-resources] [--labels=[KEY=VALUE,...]] - [--service-account=SERVICE_ACCOUNT] [--worker-pool=WORKER_POOL] - [--gcs-source=GCS_SOURCE | --git-source-directory=GIT_SOURCE_DIRECTORY - --git-source-ref=GIT_SOURCE_REF --git-source-repo=GIT_SOURCE_REPO - | --ignore-file=IGNORE_FILE - --local-source=LOCAL_SOURCE --input-values=[KEY=VALUE,...] - | --inputs-file=INPUTS_FILE] [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (ALPHA) This command updates a deployment when it already exists, otherwise - the deployment will be created. - -EXAMPLES - Create a deployment named my-deployment from a storage my-bucket: - - $ gcloud alpha infra-manager deployments apply \ - projects/p1/locations/us-central1/deployments/my-deployment \ - --gcs-source="gs://my-bucket" \ - --input-values="project=p1,region=us-central1" - - Create a deployment named my-deployment from git repo - "https://github.com/examples/repository.git", "staging/compute" folder, - "mainline" branch: - - $ gcloud alpha infra-manager deployments apply \ - projects/p1/locations/us-central1/deployments/my-deployment \ - --git-source-repo="https://github.com/examples/repository.git" \ - --git-source-directory="staging/compute" \ - --git-source-ref="mainline" - - Update a deployment's labels: - - $ gcloud alpha infra-manager deployments apply \ - projects/p1/locations/us-central1/deployments/my-deployment \ - --git-source-repo="https://github.com/examples/repository.git" \ - --git-source-directory="staging/compute" \ - --git-source-ref="mainline" --labels="env=prod,team=finance" - -POSITIONAL ARGUMENTS - Deployment resource - the deployment to create or update. The arguments in - this group can be used to specify the attributes of this resource. (NOTE) - Some attributes are not given arguments in this group but can be set in - other ways. - - To set the project attribute: - ◆ provide the argument DEPLOYMENT 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. - - DEPLOYMENT - ID of the deployment or fully qualified identifier for the - deployment. - - To set the deployment attribute: - ▸ provide the argument DEPLOYMENT on the command line. - - This positional argument must be specified if any of the other - arguments in this group are specified. - - --location=LOCATION - The Cloud location for the deployment. - - To set the location attribute: - ▸ provide the argument DEPLOYMENT on the command line with a fully - specified name; - ▸ provide the argument --location on the command line; - ▸ set the property infra-manager/location. - -FLAGS - --artifacts-gcs-bucket=ARTIFACTS_GCS_BUCKET - user-defined location of Cloud Build logs, artifacts, and Terraform - state files in Google Cloud Storage. Format: gs://{bucket}/{folder} A - default bucket will be bootstrapped if the field is not set or empty - - --async - Return immediately, without waiting for the operation in progress to - complete. - - --import-existing-resources - By default, Infrastructure Manager will return a failure when Terraform - encounters a 409 code (resource conflict error) during actuation. If - this flag is set to true, Infrastructure Manager will instead attempt - to automatically import the resource into the Terraform state (for - supported resource types) and continue actuation. - - --labels=[KEY=VALUE,...] - Labels to apply to the deployment. Existing values are overwritten. To - retain the existing labels on a deployment, do not specify this flag. - - Examples: - - Update labels for an existing deployment: - - $ gcloud alpha infra-manager deployments apply \ - projects/p1/location/us-central1/deployments/my-deployment \ - --gcs-source="gs://my-bucket" --labels="env=prod,team=finance" - - Clear labels for an existing deployment: - - $ gcloud alpha infra-manager deployments apply \ - projects/p1/location/us-central1/deployments/my-deployment \ - --gcs-source="gs://my-bucket" --labels="" - - Add a label to an existing deployment: - - First, fetch the current labels using the `describe` command, then follow the - preceding example for updating labels. - - --service-account=SERVICE_ACCOUNT - User-specified Service Account (SA) to be used as credential to manage - resources. Format: - projects/{projectID}/serviceAccounts/{serviceAccount} - - --worker-pool=WORKER_POOL - User-specified Worker Pool resource in which the Cloud Build jobwill - execute. Format: - projects/{project}/locations/{location}/workerPools/{workerPoolId} - - At most one of these can be specified: - - --gcs-source=GCS_SOURCE - URI of an object in Google Cloud Storage. e.g. gs://{bucket}/{object} - - Examples: - - Create a deployment from a storage my-bucket: - - $ gcloud alpha infra-manager deployments apply \ - projects/p1/location/us-central1/deployments/my-deployment \ - --gcs-source="gs://my-bucket" - - --git-source-directory=GIT_SOURCE_DIRECTORY - Subdirectory inside the repository. Example: 'staging/my-package' - - Use in conjunction with --git-source-repo and --git-source-ref - - Examples: - - Create a deployment from the - "https://github.com/examples/repository.git" repo, "staging/compute" - folder, "mainline" branch: - - $ gcloud alpha infra-manager deployments apply \ - projects/p1/location/us-central1/deployments/my-deployment \ - --git-source-repo="https://github.com/examples/repository.git" - --git-source-directory="staging/compute" --git-source-ref="mainline" - - --git-source-ref=GIT_SOURCE_REF - Subdirectory inside the repository. Example: 'staging/my-package' - - Use in conjunction with --git-source-repo and --git-source-directory - - Examples: - - Create a deployment from the - "https://github.com/examples/repository.git" repo, "staging/compute" - folder, "mainline" branch: - - $ gcloud alpha infra-manager deployments apply \ - projects/p1/location/us-central1/deployments/my-deployment \ - --git-source-repo="https://github.com/examples/repository.git" - --git-source-directory="staging/compute" --git-source-ref="mainline" - - --git-source-repo=GIT_SOURCE_REPO - Repository URL. Example: 'https://github.com/examples/repository.git' - - Use in conjunction with --git-source-directory and --git-source_ref - - Examples: - - Create a deployment from the - "https://github.com/examples/repository.git" repo, "staging/compute" - folder, "mainline" branch: - - $ gcloud alpha infra-manager deployments apply \ - projects/p1/location/us-central1/deployments/my-deployment \ - --git-source-repo="https://github.com/examples/repository.git" - --git-source-directory="staging/compute" --git-source-ref="mainline" - - --ignore-file=IGNORE_FILE - Override the .gcloudignore file and use the specified file instead. - See gcloud topic gcloudignore for more information. - - --local-source=LOCAL_SOURCE - Local storage path where config files are stored. e.g. - ./path/to/blueprint - - Examples: - - Create a deployment from a local storage path ./path/to/blueprint: - - $ gcloud alpha infra-manager deployments apply \ - projects/p1/location/us-central1/deployments/my-deployment \ - --local-source="./path/to/blueprint" - - At most one of these can be specified: - - --input-values=[KEY=VALUE,...] - Input variable values for the Terraform blueprint. It only accepts - (key, value) pairs where value is a scalar value. - - Examples: - - Pass input values on command line: - - $ gcloud alpha infra-manager deployments apply \ - projects/p1/location/us-central1/deployments/my-deployment \ - --gcs-source="gs://my-bucket" \ - --input-values=projects=p1,region=r - - --inputs-file=INPUTS_FILE - A .tfvars file containing terraform variable values. --inputs-file - flag is supported for python version 3.6 and above. - - Examples: - - Pass input values on the command line: - - $ gcloud alpha infra-manager deployments apply \ - projects/p1/location/us-central1/deployments/my-deployment \ - --gcs-source="gs://my-bucket" \ - --inputs-file=path-to-tfvar-file.tfvar - -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 infra-manager deployments apply - diff --git a/gcloud/alpha/infra-manager/deployments/delete b/gcloud/alpha/infra-manager/deployments/delete deleted file mode 100644 index 50e91b671..000000000 --- a/gcloud/alpha/infra-manager/deployments/delete +++ /dev/null @@ -1,81 +0,0 @@ -NAME - gcloud alpha infra-manager deployments delete - delete deployments - -SYNOPSIS - gcloud alpha infra-manager deployments delete - (DEPLOYMENT : --location=LOCATION) [--async] - [--delete-policy=DELETE_POLICY] [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (ALPHA) Delete a deployment - -EXAMPLES - To delete the deployment example-deployment at location us-central1, run: - - $ gcloud alpha infra-manager deployments delete \ - projects/example-project/locations/us-central1/deployments/\ - example-deployment - -POSITIONAL ARGUMENTS - Deployment resource - deployments TBD 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 deployment on the command line with a fully - specified name; - ◆ set the property core/project; - ◆ provide the argument --project on the command line. - - This must be specified. - - DEPLOYMENT - ID of the deployment or fully qualified identifier for the - deployment. - - To set the deployment attribute: - ▸ provide the argument deployment on the command line. - - This positional argument must be specified if any of the other - arguments in this group are specified. - - --location=LOCATION - locations TBD - - To set the location attribute: - ▸ provide the argument deployment 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. - - --delete-policy=DELETE_POLICY - Policy on how resources actuated by the deployment should be deleted. - The accepted values are DELETE, ABANDON. DELETE = Delete resources - actuated by the deployment. ABANDON = Abandon resources and only delete - deployment metadata. DELETE_POLICY must be one of: abandon, delete, - delete-policy-unspecified. - -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 config/v1 API. The full documentation for this API - can be found at: https://cloud.google.com/infrastructure-manager/docs - -NOTES - This command is currently in alpha and might change without notice. If this - command fails with API permission errors despite specifying the correct - project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: - - $ gcloud infra-manager deployments delete - diff --git a/gcloud/alpha/infra-manager/deployments/describe b/gcloud/alpha/infra-manager/deployments/describe deleted file mode 100644 index feb7bce75..000000000 --- a/gcloud/alpha/infra-manager/deployments/describe +++ /dev/null @@ -1,69 +0,0 @@ -NAME - gcloud alpha infra-manager deployments describe - describe deployments - -SYNOPSIS - gcloud alpha infra-manager deployments describe - (DEPLOYMENT : --location=LOCATION) [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (ALPHA) Describe a deployment - -EXAMPLES - To describe a deployment example-deployment in project p1 at location - us-central1, run: - - $ gcloud alpha infra-manager deployments describe \ - projects/p1/locations/us-central1/deployments/example-deployment - -POSITIONAL ARGUMENTS - Deployment resource - The deployment 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 deployment on the command line with a fully - specified name; - ◆ set the property core/project; - ◆ provide the argument --project on the command line. - - This must be specified. - - DEPLOYMENT - ID of the deployment or fully qualified identifier for the - deployment. - - To set the deployment attribute: - ▸ provide the argument deployment on the command line. - - This positional argument must be specified if any of the other - arguments in this group are specified. - - --location=LOCATION - locations TBD - - To set the location attribute: - ▸ provide the argument deployment 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 config/v1 API. The full documentation for this API - can be found at: https://cloud.google.com/infrastructure-manager/docs - -NOTES - This command is currently in alpha and might change without notice. If this - command fails with API permission errors despite specifying the correct - project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: - - $ gcloud infra-manager deployments describe - diff --git a/gcloud/alpha/infra-manager/deployments/export-lock b/gcloud/alpha/infra-manager/deployments/export-lock deleted file mode 100644 index ca92b6afc..000000000 --- a/gcloud/alpha/infra-manager/deployments/export-lock +++ /dev/null @@ -1,67 +0,0 @@ -NAME - gcloud alpha infra-manager deployments export-lock - exports lock info of a - deployment - -SYNOPSIS - gcloud alpha infra-manager deployments export-lock - (DEPLOYMENT : --location=LOCATION) [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (ALPHA) This command exports lock info of a deployment. - -EXAMPLES - Export lock info for deployment - projects/p1/locations/us-central1/deployments/my-deployment: - - $ gcloud alpha infra-manager deployments export-lock \ - projects/p1/locations/us-central1/deployments/my-deployment - -POSITIONAL ARGUMENTS - Deployment resource - the deployment to be used as parent. 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 DEPLOYMENT 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. - - DEPLOYMENT - ID of the deployment or fully qualified identifier for the - deployment. - - To set the deployment attribute: - ▸ provide the argument DEPLOYMENT on the command line. - - This positional argument must be specified if any of the other - arguments in this group are specified. - - --location=LOCATION - The Cloud location for the deployment. - - To set the location attribute: - ▸ provide the argument DEPLOYMENT on the command line with a fully - specified name; - ▸ provide the argument --location on the command line; - ▸ set the property infra-manager/location. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --configuration, --flags-file, --flatten, --format, - --help, --impersonate-service-account, --log-http, --project, --quiet, - --trace-token, --user-output-enabled, --verbosity. - - Run $ gcloud help for details. - -NOTES - This command is currently in 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 infra-manager deployments export-lock - diff --git a/gcloud/alpha/infra-manager/deployments/export-statefile b/gcloud/alpha/infra-manager/deployments/export-statefile deleted file mode 100644 index 81d7f97ec..000000000 --- a/gcloud/alpha/infra-manager/deployments/export-statefile +++ /dev/null @@ -1,72 +0,0 @@ -NAME - gcloud alpha infra-manager deployments export-statefile - export a - terraform state file - -SYNOPSIS - gcloud alpha infra-manager deployments export-statefile - (DEPLOYMENT : --location=LOCATION) [--draft] [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (ALPHA) This command generates a signed url to download a terraform state - file. - -EXAMPLES - Export state file for my-deployment: - - $ gcloud alpha infra-manager deployments export-statefile \ - projects/p1/locations/us-central1/deployments/my-deployment - -POSITIONAL ARGUMENTS - Deployment resource - the deployment to be used as parent. 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 DEPLOYMENT 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. - - DEPLOYMENT - ID of the deployment or fully qualified identifier for the - deployment. - - To set the deployment attribute: - ▸ provide the argument DEPLOYMENT on the command line. - - This positional argument must be specified if any of the other - arguments in this group are specified. - - --location=LOCATION - The Cloud location for the deployment. - - To set the location attribute: - ▸ provide the argument DEPLOYMENT on the command line with a fully - specified name; - ▸ provide the argument --location on the command line; - ▸ set the property infra-manager/location. - -FLAGS - --draft - If this flag is set to true, the exported deployment state file will be - the draft state - -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 infra-manager deployments export-statefile - diff --git a/gcloud/alpha/infra-manager/deployments/help b/gcloud/alpha/infra-manager/deployments/help deleted file mode 100644 index 13b31e99b..000000000 --- a/gcloud/alpha/infra-manager/deployments/help +++ /dev/null @@ -1,52 +0,0 @@ -NAME - gcloud alpha infra-manager deployments - manage Deployment resources - -SYNOPSIS - gcloud alpha infra-manager deployments COMMAND [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (ALPHA) Manage Deployment resources. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --help. - - Run $ gcloud help for details. - -COMMANDS - COMMAND is one of the following: - - apply - (ALPHA) Create or update a deployment. - - delete - (ALPHA) Delete deployments. - - describe - (ALPHA) Describe deployments. - - export-lock - (ALPHA) Exports lock info of a deployment. - - export-statefile - (ALPHA) Export a terraform state file. - - import-statefile - (ALPHA) Import a terraform state file. - - list - (ALPHA) List deployments. - - lock - (ALPHA) Locks the deployment. - - unlock - (ALPHA) Unlocks the deployment. - -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 infra-manager deployments - diff --git a/gcloud/alpha/infra-manager/deployments/import-statefile b/gcloud/alpha/infra-manager/deployments/import-statefile deleted file mode 100644 index 24e372b5e..000000000 --- a/gcloud/alpha/infra-manager/deployments/import-statefile +++ /dev/null @@ -1,73 +0,0 @@ -NAME - gcloud alpha infra-manager deployments import-statefile - import a - terraform state file - -SYNOPSIS - gcloud alpha infra-manager deployments import-statefile - (DEPLOYMENT : --location=LOCATION) --lock-id=LOCK_ID - [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (ALPHA) This command generates a signed url to upload a terraform state - file. - -EXAMPLES - Import state file for my-deployment with lock-id 1658343229583347: - - $ gcloud alpha infra-manager deployments import-statefile \ - projects/p1/locations/us-central1/deployments/my-deployment \ - --lock-id=1658343229583347 - -POSITIONAL ARGUMENTS - Deployment resource - the deployment to be used as parent. 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 DEPLOYMENT 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. - - DEPLOYMENT - ID of the deployment or fully qualified identifier for the - deployment. - - To set the deployment attribute: - ▸ provide the argument DEPLOYMENT on the command line. - - This positional argument must be specified if any of the other - arguments in this group are specified. - - --location=LOCATION - The Cloud location for the deployment. - - To set the location attribute: - ▸ provide the argument DEPLOYMENT on the command line with a fully - specified name; - ▸ provide the argument --location on the command line; - ▸ set the property infra-manager/location. - -REQUIRED FLAGS - --lock-id=LOCK_ID - Lock ID of the lock file to verify person importing owns lock. - -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 infra-manager deployments import-statefile - diff --git a/gcloud/alpha/infra-manager/deployments/lock b/gcloud/alpha/infra-manager/deployments/lock deleted file mode 100644 index 521a8a00b..000000000 --- a/gcloud/alpha/infra-manager/deployments/lock +++ /dev/null @@ -1,70 +0,0 @@ -NAME - gcloud alpha infra-manager deployments lock - locks the deployment - -SYNOPSIS - gcloud alpha infra-manager deployments lock - (DEPLOYMENT : --location=LOCATION) [--async] [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (ALPHA) This command locks the deployment and generates a lockId. - -EXAMPLES - Lock deployment my-deployment under project p1 and location us-central1: - - $ gcloud alpha infra-manager deployments lock \ - projects/p1/locations/us-central1/deployments/my-deployment - -POSITIONAL ARGUMENTS - Deployment resource - the deployment to be used as parent. 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 DEPLOYMENT 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. - - DEPLOYMENT - ID of the deployment or fully qualified identifier for the - deployment. - - To set the deployment attribute: - ▸ provide the argument DEPLOYMENT on the command line. - - This positional argument must be specified if any of the other - arguments in this group are specified. - - --location=LOCATION - The Cloud location for the deployment. - - To set the location attribute: - ▸ provide the argument DEPLOYMENT on the command line with a fully - specified name; - ▸ provide the argument --location on the command line; - ▸ set the property infra-manager/location. - -FLAGS - --async - Return immediately, without waiting for the operation in progress to - complete. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --configuration, --flags-file, --flatten, --format, - --help, --impersonate-service-account, --log-http, --project, --quiet, - --trace-token, --user-output-enabled, --verbosity. - - Run $ gcloud help for details. - -NOTES - This command is currently in 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 infra-manager deployments lock - diff --git a/gcloud/alpha/infra-manager/deployments/unlock b/gcloud/alpha/infra-manager/deployments/unlock deleted file mode 100644 index 409995d4c..000000000 --- a/gcloud/alpha/infra-manager/deployments/unlock +++ /dev/null @@ -1,77 +0,0 @@ -NAME - gcloud alpha infra-manager deployments unlock - unlocks the deployment - -SYNOPSIS - gcloud alpha infra-manager deployments unlock - (DEPLOYMENT : --location=LOCATION) --lock-id=LOCK_ID [--async] - [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (ALPHA) This command releases the lock on deployment. - -EXAMPLES - Unlock deployment my-deployment under project p1 and location us-central1 - with lock-id 1234: - - $ gcloud alpha infra-manager deployments unlock \ - projects/p1/locations/us-central1/deployments/my-deployment \ - --lock-id=1234 - -POSITIONAL ARGUMENTS - Deployment resource - the deployment to be used as parent. 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 DEPLOYMENT 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. - - DEPLOYMENT - ID of the deployment or fully qualified identifier for the - deployment. - - To set the deployment attribute: - ▸ provide the argument DEPLOYMENT on the command line. - - This positional argument must be specified if any of the other - arguments in this group are specified. - - --location=LOCATION - The Cloud location for the deployment. - - To set the location attribute: - ▸ provide the argument DEPLOYMENT on the command line with a fully - specified name; - ▸ provide the argument --location on the command line; - ▸ set the property infra-manager/location. - -REQUIRED FLAGS - --lock-id=LOCK_ID - Lock ID of the lock file to verify person importing owns lock. - -OPTIONAL FLAGS - --async - Return immediately, without waiting for the operation in progress to - complete. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --configuration, --flags-file, --flatten, --format, - --help, --impersonate-service-account, --log-http, --project, --quiet, - --trace-token, --user-output-enabled, --verbosity. - - Run $ gcloud help for details. - -NOTES - This command is currently in alpha and might change without notice. If this - command fails with API permission errors despite specifying the correct - project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: - - $ gcloud infra-manager deployments unlock - diff --git a/gcloud/alpha/infra-manager/help b/gcloud/alpha/infra-manager/help deleted file mode 100644 index 7001d1e66..000000000 --- a/gcloud/alpha/infra-manager/help +++ /dev/null @@ -1,34 +0,0 @@ -NAME - gcloud alpha infra-manager - manage Infra Manager resources - -SYNOPSIS - gcloud alpha infra-manager GROUP [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (ALPHA) Manage Infra Manager resources. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --help. - - Run $ gcloud help for details. - -GROUPS - GROUP is one of the following: - - deployments - (ALPHA) Manage Deployment resources. - - resources - (ALPHA) List or describe resources under a Revision. - - revisions - (ALPHA) Manage Revision resources. - -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 infra-manager - diff --git a/gcloud/alpha/infra-manager/resources/describe b/gcloud/alpha/infra-manager/resources/describe deleted file mode 100644 index c2fc6309e..000000000 --- a/gcloud/alpha/infra-manager/resources/describe +++ /dev/null @@ -1,88 +0,0 @@ -NAME - gcloud alpha infra-manager resources describe - describe resources - -SYNOPSIS - gcloud alpha infra-manager resources describe - (RESOURCE - : --deployment=DEPLOYMENT --location=LOCATION --revision=REVISION) - [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (ALPHA) Describe a resource - -EXAMPLES - To describe a resource compute-resource under revision - projects/p1/locations/us-central1/deployments/example-deployment/revisions/r-0, - run: - - $ gcloud alpha infra-manager resources describe \ - projects/p1/locations/us-central1/deployments/\ - example-deployment/revisions/r-0/resources/compute-resource - -POSITIONAL ARGUMENTS - Resource resource - The resource to describe The arguments in this group - can be used to specify the attributes of this resource. (NOTE) Some - attributes are not given arguments in this group but can be set in other - ways. - - To set the project attribute: - ◆ provide the argument resource on the command line with a fully - specified name; - ◆ set the property core/project; - ◆ provide the argument --project on the command line. - - This must be specified. - - RESOURCE - ID of the resource or fully qualified identifier for the resource. - - To set the resource attribute: - ▸ provide the argument resource on the command line. - - This positional argument must be specified if any of the other - arguments in this group are specified. - - --deployment=DEPLOYMENT - deployments TBD - - To set the deployment attribute: - ▸ provide the argument resource on the command line with a fully - specified name; - ▸ provide the argument --deployment on the command line. - - --location=LOCATION - locations TBD - - To set the location attribute: - ▸ provide the argument resource on the command line with a fully - specified name; - ▸ provide the argument --location on the command line. - - --revision=REVISION - revisions TBD - - To set the revision attribute: - ▸ provide the argument resource on the command line with a fully - specified name; - ▸ provide the argument --revision 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 config/v1 API. The full documentation for this API - can be found at: https://cloud.google.com/infrastructure-manager/docs - -NOTES - This command is currently in alpha and might change without notice. If this - command fails with API permission errors despite specifying the correct - project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: - - $ gcloud infra-manager resources describe - diff --git a/gcloud/alpha/infra-manager/resources/help b/gcloud/alpha/infra-manager/resources/help deleted file mode 100644 index 031385b6e..000000000 --- a/gcloud/alpha/infra-manager/resources/help +++ /dev/null @@ -1,32 +0,0 @@ -NAME - gcloud alpha infra-manager resources - list or describe resources under a - Revision - -SYNOPSIS - gcloud alpha infra-manager resources COMMAND [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (ALPHA) List or describe resources under a Revision. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --help. - - Run $ gcloud help for details. - -COMMANDS - COMMAND is one of the following: - - describe - (ALPHA) Describe resources. - - list - (ALPHA) List resources. - -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 infra-manager resources - diff --git a/gcloud/alpha/infra-manager/resources/list b/gcloud/alpha/infra-manager/resources/list deleted file mode 100644 index fbabd3ffd..000000000 --- a/gcloud/alpha/infra-manager/resources/list +++ /dev/null @@ -1,110 +0,0 @@ -NAME - gcloud alpha infra-manager resources list - list resources - -SYNOPSIS - gcloud alpha infra-manager resources list - (--revision=REVISION : --deployment=DEPLOYMENT --location=LOCATION) - [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] - [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (ALPHA) List resources for a deployment revision - -EXAMPLES - To list all resources for a deployment revision, - projects/p1/locations/l1/deployments/d1/revisions/r-0, run: - - $ gcloud alpha infra-manager resources list \ - --revision=projects/p1/locations/l1/deployments/d1/revisions/r-0 - -REQUIRED FLAGS - Revision resource - The deployment revision for which we want to list all - resources. 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 --revision on the command line with a fully - specified name; - ◆ set the property core/project; - ◆ provide the argument --project on the command line. - - This must be specified. - - --revision=REVISION - ID of the revision or fully qualified identifier for the revision. - - To set the revision attribute: - ▸ provide the argument --revision on the command line. - - This flag argument must be specified if any of the other arguments in - this group are specified. - - --deployment=DEPLOYMENT - deployments TBD - - To set the deployment attribute: - ▸ provide the argument --revision on the command line with a fully - specified name; - ▸ provide the argument --deployment on the command line. - - --location=LOCATION - locations TBD - - To set the location attribute: - ▸ provide the argument --revision 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. - - --uri - Print a list of resource URIs instead of the default output, and change - the command output to a list of URIs. If this flag is used with - --format, the formatting is applied on this URI list. To display URIs - alongside other keys instead, use the uri() transform. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --configuration, --flags-file, --flatten, --format, - --help, --impersonate-service-account, --log-http, --project, --quiet, - --trace-token, --user-output-enabled, --verbosity. - - Run $ gcloud help for details. - -API REFERENCE - This command uses the config/v1 API. The full documentation for this API - can be found at: https://cloud.google.com/infrastructure-manager/docs - -NOTES - This command is currently in alpha and might change without notice. If this - command fails with API permission errors despite specifying the correct - project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: - - $ gcloud infra-manager resources list - diff --git a/gcloud/alpha/infra-manager/revisions/describe b/gcloud/alpha/infra-manager/revisions/describe deleted file mode 100644 index 893a05ebc..000000000 --- a/gcloud/alpha/infra-manager/revisions/describe +++ /dev/null @@ -1,78 +0,0 @@ -NAME - gcloud alpha infra-manager revisions describe - describe revisions - -SYNOPSIS - gcloud alpha infra-manager revisions describe - (REVISION : --deployment=DEPLOYMENT --location=LOCATION) - [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (ALPHA) Describe a revision - -EXAMPLES - To describe the revision r-0 under deployment example-deployment at - location us-central1, run: - - $ gcloud alpha infra-manager revisions describe \ - projects/p1/locations/us-central1/deployments/\ - example-deployment/revisions/r-0 - -POSITIONAL ARGUMENTS - Revision resource - The revision 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 revision on the command line with a fully - specified name; - ◆ set the property core/project; - ◆ provide the argument --project on the command line. - - This must be specified. - - REVISION - ID of the revision or fully qualified identifier for the revision. - - To set the revision attribute: - ▸ provide the argument revision on the command line. - - This positional argument must be specified if any of the other - arguments in this group are specified. - - --deployment=DEPLOYMENT - deployments TBD - - To set the deployment attribute: - ▸ provide the argument revision on the command line with a fully - specified name; - ▸ provide the argument --deployment on the command line. - - --location=LOCATION - locations TBD - - To set the location attribute: - ▸ provide the argument revision 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 config/v1 API. The full documentation for this API - can be found at: https://cloud.google.com/infrastructure-manager/docs - -NOTES - This command is currently in alpha and might change without notice. If this - command fails with API permission errors despite specifying the correct - project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: - - $ gcloud infra-manager revisions describe - diff --git a/gcloud/alpha/infra-manager/revisions/export-statefile b/gcloud/alpha/infra-manager/revisions/export-statefile deleted file mode 100644 index edf3218c1..000000000 --- a/gcloud/alpha/infra-manager/revisions/export-statefile +++ /dev/null @@ -1,76 +0,0 @@ -NAME - gcloud alpha infra-manager revisions export-statefile - export a terraform - state file - -SYNOPSIS - gcloud alpha infra-manager revisions export-statefile - (REVISION : --deployment=DEPLOYMENT --location=LOCATION) - [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (ALPHA) This command generates a signed url to download a terraform state - file. - -EXAMPLES - Export state file for revision - projects/p1/locations/l1/deployments/d1/revisions/r-0: - - $ gcloud alpha infra-manager revisions export-statefile \ - projects/p1/locations/l1/deployments/d1/revisions/r-0 - -POSITIONAL ARGUMENTS - Revision resource - the revision to be used as parent. 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 REVISION 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. - - REVISION - ID of the revision or fully qualified identifier for the revision. - - To set the revision attribute: - ▸ provide the argument REVISION on the command line. - - This positional argument must be specified if any of the other - arguments in this group are specified. - - --deployment=DEPLOYMENT - The deployment for the revision. - - To set the deployment attribute: - ▸ provide the argument REVISION on the command line with a fully - specified name; - ▸ provide the argument --deployment on the command line. - - --location=LOCATION - The Cloud location for the revision. - - To set the location attribute: - ▸ provide the argument REVISION on the command line with a fully - specified name; - ▸ provide the argument --location on the command line; - ▸ set the property infra-manager/location. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --configuration, --flags-file, --flatten, --format, - --help, --impersonate-service-account, --log-http, --project, --quiet, - --trace-token, --user-output-enabled, --verbosity. - - Run $ gcloud help for details. - -NOTES - This command is currently in 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 infra-manager revisions export-statefile - diff --git a/gcloud/alpha/infra-manager/revisions/help b/gcloud/alpha/infra-manager/revisions/help deleted file mode 100644 index 9890d2947..000000000 --- a/gcloud/alpha/infra-manager/revisions/help +++ /dev/null @@ -1,34 +0,0 @@ -NAME - gcloud alpha infra-manager revisions - manage Revision resources - -SYNOPSIS - gcloud alpha infra-manager revisions COMMAND [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (ALPHA) Manage Revision resources. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --help. - - Run $ gcloud help for details. - -COMMANDS - COMMAND is one of the following: - - describe - (ALPHA) Describe revisions. - - export-statefile - (ALPHA) Export a terraform state file. - - list - (ALPHA) List revisions. - -NOTES - This command is currently in alpha and might change without notice. If this - command fails with API permission errors despite specifying the correct - project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: - - $ gcloud infra-manager revisions - diff --git a/gcloud/alpha/monitoring/uptime/create b/gcloud/alpha/monitoring/uptime/create new file mode 100644 index 000000000..a391cc9e8 --- /dev/null +++ b/gcloud/alpha/monitoring/uptime/create @@ -0,0 +1,323 @@ +NAME + gcloud alpha monitoring uptime create - create a new uptime check + +SYNOPSIS + gcloud alpha monitoring uptime create DISPLAY_NAME + (--synthetic-target=SYNTHETIC_TARGET + | [--group-id=GROUP_ID : --group-type=GROUP_TYPE] + | [--resource-labels=[KEY=VALUE,...] + : --resource-type=RESOURCE_TYPE]) + [--body=BODY --content-type=CONTENT_TYPE + --custom-content-type=CUSTOM_CONTENT_TYPE --headers=[KEY=VALUE,...] + --mask-headers=MASK_HEADERS --password=PASSWORD --path=PATH + --pings-count=PINGS_COUNT --port=PORT --protocol=PROTOCOL + --request-method=REQUEST_METHOD --username=USERNAME + --validate-ssl=VALIDATE_SSL --status-classes=[status-class,...] + | --status-codes=[status-code,...]] + [--matcher-content=MATCHER_CONTENT + : --matcher-type=MATCHER_TYPE [--json-path=JSON_PATH + : --json-path-matcher-type=JSON_PATH_MATCHER_TYPE]] + [--period=PERIOD --regions=[field,...] + --timeout=TIMEOUT --user-labels=[KEY=VALUE,...]] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Create a new uptime check. + + For information about the JSON/YAML format of an uptime check: + https://cloud.google.com/monitoring/api/ref_v3/rest/v3/projects.uptimeCheckConfigs + +EXAMPLES + To create an uptime check against an uptime_url, run: + + $ gcloud alpha monitoring uptime create DISPLAY_NAME \ + --resource-type=uptime-url \ + --resource-labels=host=google.com,project_id=PROJECT_ID + + To create a synthetic monitor, run: + + $ gcloud alpha monitoring uptime create fake_uptime_check \ + --synthetic-target=projects/PROJECT_ID/locations/REGION/\ + functions/FUNCTION_NAME + +POSITIONAL ARGUMENTS + DISPLAY_NAME + Display name for the Uptime Check. + +REQUIRED FLAGS + Uptime check resource + + Exactly one of these must be specified: + + --synthetic-target=SYNTHETIC_TARGET + The target of the Synthetic Monitor. This is the fully qualified + GCFv2 resource name. + + Monitored resource group + + --group-id=GROUP_ID + The group of resources being monitored. + + This flag argument must be specified if any of the other arguments + in this group are specified. + + --group-type=GROUP_TYPE + The resource type of the group members, defaults to "gce-instance". + GROUP_TYPE must be one of: + + aws-elb-load-balancer + Uptime Check against a group of Amazon ELB load balancers. + gce-instance + Uptime Check against a group of instances from Google Cloud or + Amazon Web Services. + + Monitored resource + + --resource-labels=[KEY=VALUE,...] + Values for all of the labels listed in the associated monitored + resource descriptor. See + https://cloud.google.com/monitoring/api/resources for more + information and allowed keys. + + This flag argument must be specified if any of the other arguments + in this group are specified. + + --resource-type=RESOURCE_TYPE + Type of monitored resource, defaults to "uptime-url". RESOURCE_TYPE + must be one of: + + aws-ec2-instance + Uptime Check against an AWS EC2 instance. + aws-elb-load-balancer + Uptime Check against an ElasticLoadBalancer. + cloud-run-revision + Uptime Check against a Cloud Run revision. + gae-app + Uptime Check against an App Engine module. + gce-instance + Uptime Check against a Compute Engine instance. + servicedirectory-service + Uptime Check against a Service Directory service. + uptime-url + Uptime Check against a URL. + +OPTIONAL FLAGS + Uptime check protocol settings + + --body=BODY + The request body associated with the HTTP POST request. Can only be + set if --protocol is "http" or "https". + + --content-type=CONTENT_TYPE + The content type header to use for the check, defaults to + "unspecified". Can only be set if --protocol is "http" or "https". + + CONTENT_TYPE must be one of: + + unspecified + Not specified + url-encoded + URL encoded + user-provided + User provided + + --custom-content-type=CUSTOM_CONTENT_TYPE + A user-provided content type header to use for the check. Can only be + set if --protocol is "http" or "https". + + --headers=[KEY=VALUE,...] + The list of headers to send as part of the Uptime Check request. Can + only be set if --protocol is "http" or "https". + + --mask-headers=MASK_HEADERS + Whether to encrypt the header information, defaults to "false". Can + only be set if --protocol is "http" or "https". + + --password=PASSWORD + The password to use when authenticating with the HTTP server. Can + only be set if --protocol is "http" or "https". + + --path=PATH + The path to the page against which to run the check, defaults to "/". + Can only be set if --protocol is "http" or "https". + + --pings-count=PINGS_COUNT + Number of ICMP pings to send alongside the request. + + --port=PORT + The port on the server against which to run the check. Defaults to + "80" when --protocol is "http". Defaults to "443" when --protocol is + "https". Required if --protocol is "tcp". + + --protocol=PROTOCOL + The protocol of the request, defaults to "http". PROTOCOL must be one + of: + + http + An HTTP check. + https + An HTTPS check. + tcp + A TCP check. + + --request-method=REQUEST_METHOD + The HTTP request method to use, defaults to "get". Can only be set if + --protocol is "http" or "https". + + REQUEST_METHOD must be one of: + + get + HTTP GET method + post + HTTP POST method + + --username=USERNAME + The username to use when authenticating with the HTTP server. Can + only be set if --protocol is "http" or "https". + + --validate-ssl=VALIDATE_SSL + Whether to include SSL certificate validation as a part of the Uptime + Check, defaults to "false". Can only be set if --protocol is "https". + + Uptime Status + + At most one of these can be specified: + + --status-classes=[status-class,...] + List of HTTP Status Classes. The Uptime Check will only pass if the + response code is contained in this list. Defaults to "2xx". Can + only be set if --protocol is "http" or "https". + + status-class must be one of: + + 1xx + Any response code from 100-199 inclusive + 2xx + Any response code from 200-299 inclusive + 3xx + Any response code from 300-399 inclusive + 4xx + Any response code from 400-499 inclusive + 5xx + Any response code from 500-599 inclusive + any + Any response code + + --status-codes=[status-code,...] + List of HTTP Status Codes. The Uptime Check will only pass if the + response code is present in this list. Can only be set if + --protocol is "http" or "https". + + Uptime matcher settings + + --matcher-content=MATCHER_CONTENT + String, regex or JSON content to match. + + This flag argument must be specified if any of the other arguments in + this group are specified. + + --matcher-type=MATCHER_TYPE + The type of content matcher that will be applied to the server + output, defaults to "contains-string". + + MATCHER_TYPE must be one of: + + contains-string + Response contains string + matches-json-path + Response matches at JSONPath + matches-regex + Response matches regex + not-contains-string + Response does not contain string + not-matches-json-path + Response does not match at JSONPath + not-matches-regex + Response does not match regex + + Uptime matcher settings for JSON responses + + --json-path=JSON_PATH + JSONPath within the response output pointing to the expected + content to match. Only used if matcher-type is "matches-json-path" + or "not-matches-json-path". + + This flag argument must be specified if any of the other arguments + in this group are specified. + + --json-path-matcher-type=JSON_PATH_MATCHER_TYPE + The type of JSONPath match that will be applied to the JSON output, + defaults to "exact-match". Only used if matcher-type is + "matches-json-path" or "not-matches-json-path". + + JSON_PATH_MATCHER_TYPE must be one of: + + exact-match + Response matches exact string at JSONPath + regex-match + Response matches regex at JSONPath + + Uptime check settings + + --period=PERIOD + How often, in minutes, the Uptime check is performed, defaults to + "1". PERIOD must be one of: + + 1 + One minute + 10 + Ten minutes + 15 + Fifteen minutes + 5 + Five minutes + + --regions=[field,...] + The list of regions from which the check will be run. At least 3 + regions must be selected. Defaults to all available regions. + + field must be one of: + + asia-pacific + asia-southeast1 + europe + europe-west1 + south-america + southamerica-east1 + usa-iowa + us-central1 + usa-oregon + us-west1 + usa-virginia + us-east4 + + --timeout=TIMEOUT + The maximum amount of time in seconds to wait for the request to + complete, defaults to "60". + + --user-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. + + If the uptime check was given as a JSON/YAML object from a string or + file, this flag will replace the labels value in the given uptime + check. + +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/monitoring/uptime/delete b/gcloud/alpha/monitoring/uptime/delete new file mode 100644 index 000000000..9cd6ddb32 --- /dev/null +++ b/gcloud/alpha/monitoring/uptime/delete @@ -0,0 +1,55 @@ +NAME + gcloud alpha monitoring uptime delete - delete an uptime check + +SYNOPSIS + gcloud alpha monitoring uptime delete CHECK_ID [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Delete an uptime check + +EXAMPLES + To delete an uptime check: + + $ gcloud alpha monitoring uptime delete check-id + + More information can be found at + https://cloud.google.com/monitoring/uptime-checks/manage#delete. + +POSITIONAL ARGUMENTS + Uptime check resource - The uptime check to delete. This represents a + Cloud resource. (NOTE) Some attributes are not given arguments in this + group but can be set in other ways. + + To set the project attribute: + ◆ provide the argument check_id 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. + + CHECK_ID + ID of the uptime_check or fully qualified identifier for the + uptime_check. + + To set the check_id attribute: + ▸ provide the argument check_id 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 monitoring/v3 API. The full documentation for this + API can be found at: https://cloud.google.com/monitoring/api/ + +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/monitoring/uptime/describe b/gcloud/alpha/monitoring/uptime/describe new file mode 100644 index 000000000..28a983338 --- /dev/null +++ b/gcloud/alpha/monitoring/uptime/describe @@ -0,0 +1,55 @@ +NAME + gcloud alpha monitoring uptime describe - describe an uptime check + +SYNOPSIS + gcloud alpha monitoring uptime describe CHECK_ID [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Describe an uptime check + +EXAMPLES + To describe an uptime check: + + $ gcloud alpha monitoring uptime describe + + More information can be found at + https://cloud.google.com/monitoring/uptime-checks/manage#get. + +POSITIONAL ARGUMENTS + Uptime check resource - The uptime check to describe. This represents a + Cloud resource. (NOTE) Some attributes are not given arguments in this + group but can be set in other ways. + + To set the project attribute: + ◆ provide the argument check_id 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. + + CHECK_ID + ID of the uptime_check or fully qualified identifier for the + uptime_check. + + To set the check_id attribute: + ▸ provide the argument check_id 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 monitoring/v3 API. The full documentation for this + API can be found at: https://cloud.google.com/monitoring/api/ + +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/monitoring/uptime/help b/gcloud/alpha/monitoring/uptime/help index 338646250..7f6856844 100644 --- a/gcloud/alpha/monitoring/uptime/help +++ b/gcloud/alpha/monitoring/uptime/help @@ -18,9 +18,24 @@ GCLOUD WIDE FLAGS COMMANDS COMMAND is one of the following: + create + (ALPHA) Create a new uptime check. + + delete + (ALPHA) Delete an uptime check. + + describe + (ALPHA) Describe an uptime check. + + list-configs + (ALPHA) List uptime checks. + list-ips (ALPHA) List uptime check egress ips. + update + (ALPHA) Update an existing uptime check. + 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/infra-manager/revisions/list b/gcloud/alpha/monitoring/uptime/list-configs similarity index 55% rename from gcloud/alpha/infra-manager/revisions/list rename to gcloud/alpha/monitoring/uptime/list-configs index 54bc7a1e4..90440bd43 100644 --- a/gcloud/alpha/infra-manager/revisions/list +++ b/gcloud/alpha/monitoring/uptime/list-configs @@ -1,53 +1,21 @@ NAME - gcloud alpha infra-manager revisions list - list revisions + gcloud alpha monitoring uptime list-configs - list uptime checks SYNOPSIS - gcloud alpha infra-manager revisions list - (--deployment=DEPLOYMENT : --location=LOCATION) [--filter=EXPRESSION] + gcloud alpha monitoring uptime list-configs [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) List revisions for a deployment + (ALPHA) List uptime checks. EXAMPLES - To list all revisions for deployment - projects/p1/locations/l1/deployments/d1, run: + To see all uptime checks: - $ gcloud alpha infra-manager revisions list \ - --deployment=projects/p1/locations/l1/deployments/d1 + $ gcloud alpha monitoring uptime list-configs -REQUIRED FLAGS - Deployment resource - The deployment for which we want to list all - revisions. 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 --deployment on the command line with a fully - specified name; - ◆ set the property core/project; - ◆ provide the argument --project on the command line. - - This must be specified. - - --deployment=DEPLOYMENT - ID of the deployment or fully qualified identifier for the - deployment. - - To set the deployment attribute: - ▸ provide the argument --deployment on the command line. - - This flag argument must be specified if any of the other arguments in - this group are specified. - - --location=LOCATION - locations TBD - - To set the location attribute: - ▸ provide the argument --deployment on the command line with a - fully specified name; - ▸ provide the argument --location on the command line. + More information can be found at + https://cloud.google.com/monitoring/uptime-checks/using-uptime-checks LIST COMMAND FLAGS --filter=EXPRESSION @@ -90,14 +58,12 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. API REFERENCE - This command uses the config/v1 API. The full documentation for this API - can be found at: https://cloud.google.com/infrastructure-manager/docs + This command uses the monitoring/v3 API. The full documentation for this + API can be found at: https://cloud.google.com/monitoring/api/ 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 infra-manager revisions list + access allowlist. diff --git a/gcloud/alpha/monitoring/uptime/update b/gcloud/alpha/monitoring/uptime/update new file mode 100644 index 000000000..baf749746 --- /dev/null +++ b/gcloud/alpha/monitoring/uptime/update @@ -0,0 +1,397 @@ +NAME + gcloud alpha monitoring uptime update - update an existing uptime check + +SYNOPSIS + gcloud alpha monitoring uptime update CHECK_ID + [--body=BODY --content-type=CONTENT_TYPE + --custom-content-type=CUSTOM_CONTENT_TYPE --mask-headers=MASK_HEADERS + --password=PASSWORD --path=PATH --pings-count=PINGS_COUNT --port=PORT + --request-method=REQUEST_METHOD --username=USERNAME + --validate-ssl=VALIDATE_SSL --add-status-classes=[status-class,...] + | --clear-status-classes=CLEAR_STATUS_CLASSES + | --remove-status-classes=[status-class,...] + | --set-status-classes=[status-class,...] + | --add-status-codes=[status-code,...] + | --clear-status-codes=CLEAR_STATUS_CODES + | --remove-status-codes=[status-code,...] + | --set-status-codes=[status-code,...] + --update-headers=[KEY=VALUE,...] --clear-headers=CLEAR_HEADERS + | --remove-headers=[KEY,...]] + [--display-name=DISPLAY_NAME + --period=PERIOD --timeout=TIMEOUT --add-regions=[region,...] + | --clear-regions=CLEAR_REGIONS | --remove-regions=[region,...] + | --set-regions=[region,...] + --update-user-labels=[KEY=VALUE,...] --clear-user-labels + | --remove-user-labels=[KEY,...]] + [--matcher-content=MATCHER_CONTENT + : --matcher-type=MATCHER_TYPE [--json-path=JSON_PATH + : --json-path-matcher-type=JSON_PATH_MATCHER_TYPE]] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Updates an existing uptime check. + + For information about the JSON/YAML format of an uptime check: + https://cloud.google.com/monitoring/api/ref_v3/rest/v3/projects.uptimeCheckConfigs + +POSITIONAL ARGUMENTS + Uptime Check resource - Name of the Uptime Check to be updated. 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 check_id 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. + + CHECK_ID + ID of the Uptime Check or fully qualified identifier for the Uptime + Check. + + To set the uptime_check attribute: + ▸ provide the argument check_id on the command line. + +FLAGS + Uptime check protocol settings + + --body=BODY + The request body associated with the HTTP POST request. Can only be + set if --protocol is "http" or "https". + + --content-type=CONTENT_TYPE + The content type header to use for the check, defaults to + "unspecified". Can only be set if --protocol is "http" or "https". + + CONTENT_TYPE must be one of: + + unspecified + Not specified + url-encoded + URL encoded + user-provided + User provided + + --custom-content-type=CUSTOM_CONTENT_TYPE + A user-provided content type header to use for the check. Can only be + set if --protocol is "http" or "https". + + --mask-headers=MASK_HEADERS + Whether to encrypt the header information, defaults to "false". Can + only be set if --protocol is "http" or "https". + + --password=PASSWORD + The password to use when authenticating with the HTTP server. Can + only be set if --protocol is "http" or "https". + + --path=PATH + The path to the page against which to run the check, defaults to "/". + Can only be set if --protocol is "http" or "https". + + --pings-count=PINGS_COUNT + Number of ICMP pings to send alongside the request. + + --port=PORT + The port on the server against which to run the check. Defaults to + "80" when --protocol is "http". Defaults to "443" when --protocol is + "https". Required if --protocol is "tcp". + + --request-method=REQUEST_METHOD + The HTTP request method to use, defaults to "get". Can only be set if + --protocol is "http" or "https". + + REQUEST_METHOD must be one of: + + get + HTTP GET method + post + HTTP POST method + + --username=USERNAME + The username to use when authenticating with the HTTP server. Can + only be set if --protocol is "http" or "https". + + --validate-ssl=VALIDATE_SSL + Whether to include SSL certificate validation as a part of the Uptime + Check, defaults to "false". Can only be set if --protocol is "https". + + Uptime Status + + At most one of these can be specified: + + Uptime Status Classes + + At most one of these can be specified: + + --add-status-classes=[status-class,...] + The list of HTTP Status Classes to add to the Uptime Check. + status-class must be one of: + + 1xx + Any response code from 100-199 inclusive + 2xx + Any response code from 200-299 inclusive + 3xx + Any response code from 300-399 inclusive + 4xx + Any response code from 400-499 inclusive + 5xx + Any response code from 500-599 inclusive + any + Any response code + + --clear-status-classes=CLEAR_STATUS_CLASSES + Clear all HTTP Status Classes on the Uptime Check. This will act + the same as if only "2xx" was selected. + + --remove-status-classes=[status-class,...] + The list of HTTP Status Classes to remove from the Uptime Check. + status-class must be one of: + + 1xx + Any response code from 100-199 inclusive + 2xx + Any response code from 200-299 inclusive + 3xx + Any response code from 300-399 inclusive + 4xx + Any response code from 400-499 inclusive + 5xx + Any response code from 500-599 inclusive + any + Any response code + + --set-status-classes=[status-class,...] + List of HTTP Status Classes. The Uptime Check will only pass if + the response code is contained in this list. + + status-class must be one of: + + 1xx + Any response code from 100-199 inclusive + 2xx + Any response code from 200-299 inclusive + 3xx + Any response code from 300-399 inclusive + 4xx + Any response code from 400-499 inclusive + 5xx + Any response code from 500-599 inclusive + any + Any response code + + Uptime Status Codes + + At most one of these can be specified: + + --add-status-codes=[status-code,...] + The list of HTTP Status Codes to add to the Uptime Check. + + --clear-status-codes=CLEAR_STATUS_CODES + Clear all HTTP Status Codes on the Uptime Check. This will act + the same as if only the "2xx" HTTP Status Class was selected. + + --remove-status-codes=[status-code,...] + The list of HTTP Status Codes to remove from the Uptime Check. + + --set-status-codes=[status-code,...] + List of HTTP Status Codes. The Uptime Check will only pass if the + response code is present in this list. + + Uptime Headers + + --update-headers=[KEY=VALUE,...] + The list of headers to add to the Uptime Check. Any existing + headers with matching "key" will be overridden by the provided + values. + + Uptime remove Headers + + At most one of these can be specified: + + --clear-headers=CLEAR_HEADERS + Clear all headers on the Uptime Check. + + --remove-headers=[KEY,...] + The list of header keys to remove from the Uptime Check. + + Uptime check settings + + --display-name=DISPLAY_NAME + The display name for the Uptime Check. + + --period=PERIOD + How often, in minutes, the Uptime check is performed, defaults to + "1". PERIOD must be one of: + + 1 + One minute + 10 + Ten minutes + 15 + Fifteen minutes + 5 + Five minutes + + --timeout=TIMEOUT + The maximum amount of time in seconds to wait for the request to + complete, defaults to "60". + + Uptime Selected Regions + + At most one of these can be specified: + + --add-regions=[region,...] + The list of regions to add to the Uptime Check. region must be one + of: + + asia-pacific + asia-southeast1 + europe + europe-west1 + south-america + southamerica-east1 + usa-iowa + us-central1 + usa-oregon + us-west1 + usa-virginia + us-east4 + + --clear-regions=CLEAR_REGIONS + Clear all regions on the Uptime Check. This will act the same as if + all available regions were selected. + + --remove-regions=[region,...] + The list of regions to remove from the Uptime Check. region must be + one of: + + asia-pacific + asia-southeast1 + europe + europe-west1 + south-america + southamerica-east1 + usa-iowa + us-central1 + usa-oregon + us-west1 + usa-virginia + us-east4 + + --set-regions=[region,...] + The list of regions from which the check will be run. At least 3 + regions must be selected. + + region must be one of: + + asia-pacific + asia-southeast1 + europe + europe-west1 + south-america + southamerica-east1 + usa-iowa + us-central1 + usa-oregon + us-west1 + usa-virginia + us-east4 + + uptime check + + --update-user-labels=[KEY=VALUE,...] + List of label KEY=VALUE pairs to update. If a label exists, its + value is modified. Otherwise, a new label is created. + + Keys must start with a lowercase character and contain only hyphens + (-), underscores (_), lowercase characters, and numbers. Values + must contain only hyphens (-), underscores (_), lowercase + characters, and numbers. + + At most one of these can be specified: + + --clear-user-labels + Remove all labels. If --update-user-labels is also specified then + --clear-user-labels is applied first. + + For example, to remove all labels: + + $ gcloud alpha monitoring uptime update --clear-user-labels + + To remove all existing labels and create two new labels, foo and + baz: + + $ gcloud alpha monitoring uptime update --clear-user-labels \ + --update-user-labels foo=bar,baz=qux + + --remove-user-labels=[KEY,...] + List of label keys to remove. If a label does not exist it is + silently ignored. If --update-user-labels is also specified then + --update-user-labels is applied first. + + Uptime matcher settings + + --matcher-content=MATCHER_CONTENT + String, regex or JSON content to match. + + This flag argument must be specified if any of the other arguments in + this group are specified. + + --matcher-type=MATCHER_TYPE + The type of content matcher that will be applied to the server + output, defaults to "contains-string". + + MATCHER_TYPE must be one of: + + contains-string + Response contains string + matches-json-path + Response matches at JSONPath + matches-regex + Response matches regex + not-contains-string + Response does not contain string + not-matches-json-path + Response does not match at JSONPath + not-matches-regex + Response does not match regex + + Uptime matcher settings for JSON responses + + --json-path=JSON_PATH + JSONPath within the response output pointing to the expected + content to match. Only used if matcher-type is "matches-json-path" + or "not-matches-json-path". + + This flag argument must be specified if any of the other arguments + in this group are specified. + + --json-path-matcher-type=JSON_PATH_MATCHER_TYPE + The type of JSONPath match that will be applied to the JSON output, + defaults to "exact-match". Only used if matcher-type is + "matches-json-path" or "not-matches-json-path". + + JSON_PATH_MATCHER_TYPE must be one of: + + exact-match + Response matches exact string at JSONPath + regex-match + Response matches regex at JSONPath + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/run/deploy b/gcloud/alpha/run/deploy index 7f015c004..f2ab12482 100644 --- a/gcloud/alpha/run/deploy +++ b/gcloud/alpha/run/deploy @@ -27,7 +27,8 @@ SYNOPSIS --clear-vpc-connector --[no-]cpu-boost --[no-]cpu-throttling --[no-]default-url --description=DESCRIPTION --execution-environment=EXECUTION_ENVIRONMENT - --remove-containers=[CONTAINER,...] --revision-suffix=REVISION_SUFFIX + --[no-]invoker-iam-check --remove-containers=[CONTAINER,...] + --revision-suffix=REVISION_SUFFIX --service-min-instances=SERVICE_MIN_INSTANCES --[no-]session-affinity --vpc-connector=VPC_CONNECTOR --vpc-egress=VPC_EGRESS --add-cloudsql-instances=[CLOUDSQL-INSTANCES,...] @@ -449,6 +450,13 @@ FLAGS gen2 Run the application in a second generation execution environment. + --[no-]invoker-iam-check + Indicates whether an IAM check should occur when invoking the + container. This is Enabled by default. It can only be disabled on + services with internal, and internal+load-balancer ingress settings. + Use --invoker-iam-check to enable and --no-invoker-iam-check to + disable. + --remove-containers=[CONTAINER,...] List of containers to remove. diff --git a/gcloud/alpha/run/services/update b/gcloud/alpha/run/services/update index 2b76530e2..9026b1a8e 100644 --- a/gcloud/alpha/run/services/update +++ b/gcloud/alpha/run/services/update @@ -22,7 +22,8 @@ SYNOPSIS [--breakglass=JUSTIFICATION --clear-vpc-connector --[no-]cpu-boost --[no-]cpu-throttling --[no-]default-url --description=DESCRIPTION --execution-environment=EXECUTION_ENVIRONMENT - --remove-containers=[CONTAINER,...] --revision-suffix=REVISION_SUFFIX + --[no-]invoker-iam-check --remove-containers=[CONTAINER,...] + --revision-suffix=REVISION_SUFFIX --service-min-instances=SERVICE_MIN_INSTANCES --[no-]session-affinity --vpc-connector=VPC_CONNECTOR --vpc-egress=VPC_EGRESS --add-cloudsql-instances=[CLOUDSQL-INSTANCES,...] @@ -333,6 +334,13 @@ FLAGS gen2 Run the application in a second generation execution environment. + --[no-]invoker-iam-check + Indicates whether an IAM check should occur when invoking the + container. This is Enabled by default. It can only be disabled on + services with internal, and internal+load-balancer ingress settings. + Use --invoker-iam-check to enable and --no-invoker-iam-check to + disable. + --remove-containers=[CONTAINER,...] List of containers to remove. diff --git a/gcloud/alpha/services/api-keys/undelete b/gcloud/alpha/services/api-keys/undelete index 49b4a9d22..00fc52db1 100644 --- a/gcloud/alpha/services/api-keys/undelete +++ b/gcloud/alpha/services/api-keys/undelete @@ -81,7 +81,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud services api-keys undelete $ gcloud beta services api-keys undelete diff --git a/gcloud/beta/ai/models/upload b/gcloud/beta/ai/models/upload index 7d498ce3b..e5c3d6b7f 100644 --- a/gcloud/beta/ai/models/upload +++ b/gcloud/beta/ai/models/upload @@ -5,10 +5,19 @@ SYNOPSIS gcloud beta ai models upload --container-image-uri=CONTAINER_IMAGE_URI --display-name=DISPLAY_NAME [--artifact-uri=ARTIFACT_URI] [--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-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] [--description=DESCRIPTION] [--explanation-metadata-file=EXPLANATION_METADATA_FILE] [--explanation-method=EXPLANATION_METHOD] @@ -58,19 +67,54 @@ OPTIONAL FLAGS 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-ports=[PORT,...] - Container ports to receive requests at. Must be a number between 1 and - 65535, inclusive. + 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. + --description=DESCRIPTION Description of the model. diff --git a/gcloud/beta/alloydb/clusters/restore b/gcloud/beta/alloydb/clusters/restore index 3fdc7884a..3d5b211ec 100644 --- a/gcloud/beta/alloydb/clusters/restore +++ b/gcloud/beta/alloydb/clusters/restore @@ -42,12 +42,11 @@ REQUIRED FLAGS Exactly one of these must be specified: --backup=BACKUP - The AlloyDB backup to restore from. This must either be the full - backup name - (projects/myProject/locations/us-central1/backups/myBackup) or the - backup ID (myBackup). In the second case, the project and location - are assumed to be the same as the restored cluster that is being - created. + AlloyDB backup to restore from. This must either be the full backup + name (projects/myProject/locations/us-central1/backups/myBackup) or + the backup ID (myBackup). In the second case, the project and + location are assumed to be the same as the restored cluster that is + being created. Restore a cluster from a source cluster at a given point in time. @@ -59,7 +58,7 @@ REQUIRED FLAGS in this group are specified. --source-cluster=SOURCE_CLUSTER - The AlloyDB source cluster to restore from. This must either be the + AlloyDB source cluster to restore from. This must either be the full cluster name (projects/myProject/locations/us-central1/backups/myCluster) or the cluster ID (myCluster). In the second case, the project and diff --git a/gcloud/beta/certificate-manager/trust-configs/help b/gcloud/beta/certificate-manager/trust-configs/help index 35d56de4b..0d574c964 100644 --- a/gcloud/beta/certificate-manager/trust-configs/help +++ b/gcloud/beta/certificate-manager/trust-configs/help @@ -35,6 +35,9 @@ COMMANDS list (BETA) List all TrustConfigs in a project. + update + (BETA) Update TrustConfig. + NOTES This command is currently in beta and might change without notice. These variants are also available: diff --git a/gcloud/beta/certificate-manager/trust-configs/update b/gcloud/beta/certificate-manager/trust-configs/update new file mode 100644 index 000000000..ccf793c98 --- /dev/null +++ b/gcloud/beta/certificate-manager/trust-configs/update @@ -0,0 +1,129 @@ +NAME + gcloud beta certificate-manager trust-configs update - update TrustConfig + +SYNOPSIS + gcloud beta certificate-manager trust-configs update + (TRUST_CONFIG : --location=LOCATION) [--async] + [--description=DESCRIPTION] + [--trust-store=[intermediate-cas=INTERMEDIATE-CAS], + [trust-anchors=TRUST-ANCHORS]] [--update-labels=[KEY=VALUE,...]] + [--clear-labels | --remove-labels=[KEY,...]] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Update a TrustConfig. + +EXAMPLES + To update a TrustConfig, run: + + $ gcloud beta certificate-manager trust-configs update \ + my-trust-config --description="updated description" \ + --trust-store=trust-anchors=ta.pem,\ + intermediate-cas="ica1.pem;ica2.pem" \ + --update-labels=my-key1=my-updated-value1 \ + --remove-labels=my-key2 + +POSITIONAL ARGUMENTS + TrustConfig resource - Name of the TrustConfig to update. The arguments in + this group can be used to specify the attributes of this resource. (NOTE) + Some attributes are not given arguments in this group but can be set in + other ways. + + To set the project attribute: + ◆ provide the argument trust_config on the command line with a fully + specified name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + This must be specified. + + TRUST_CONFIG + ID of the trustConfig or fully qualified identifier for the + trustConfig. + + To set the trust_config attribute: + ▸ provide the argument trust_config on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + Certificate Manager location. + + To set the location attribute: + ▸ provide the argument trust_config on the command line with a + fully specified name; + ▸ provide the argument --location on the command line; + ▸ default value of location is [global]. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --description=DESCRIPTION + Human-readable description of the resource. + + --trust-store=[intermediate-cas=INTERMEDIATE-CAS],[trust-anchors=TRUST-ANCHORS] + Trust Store with the given trust anchor and intermediate CA PEM-encoded + certificates. Certificates should be provided in files. For multiple + file names, separate them by a semicolon (';') and quote them ('"'). + One file can contain multiple certificates. Intermediate CAs are + optional. + + Examples: + + Single files: --trust-store trust-anchors=ta.pem,intermediate-cas=ica.pem + + No intermediate CAs: --trust-store trust-anchors=ta.pem + + Multiple files: --trust-store trust-anchors="ta1.pem;ta2.pem",intermediate-cas="ica1.pem;ica2.pem" + + --update-labels=[KEY=VALUE,...] + List of label KEY=VALUE pairs to update. If a label exists, its value + is modified. Otherwise, a new label is created. + + Keys must start with a lowercase character and contain only hyphens + (-), underscores (_), lowercase characters, and numbers. Values must + contain only hyphens (-), underscores (_), lowercase characters, and + numbers. + + At most one of these can be specified: + + --clear-labels + Remove all labels. If --update-labels is also specified then + --clear-labels is applied first. + + For example, to remove all labels: + + $ gcloud beta certificate-manager trust-configs update --clear-labels + + To remove all existing labels and create two new labels, foo and baz: + + $ gcloud beta certificate-manager trust-configs update \ + --clear-labels --update-labels foo=bar,baz=qux + + --remove-labels=[KEY,...] + List of label keys to remove. If a label does not exist it is + silently ignored. If --update-labels is also specified then + --update-labels is applied first. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the certificatemanager/v1 API. The full documentation for + this API can be found at: https://cloud.google.com/certificate-manager + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud certificate-manager trust-configs update + + $ gcloud alpha certificate-manager trust-configs update + diff --git a/gcloud/beta/composer/environments/create b/gcloud/beta/composer/environments/create index 4931ef4a5..def1e1fb8 100644 --- a/gcloud/beta/composer/environments/create +++ b/gcloud/beta/composer/environments/create @@ -7,8 +7,8 @@ SYNOPSIS (ENVIRONMENT : --location=LOCATION) [--airflow-configs=[KEY=VALUE,...]] [--async] [--cloud-sql-machine-type=CLOUD_SQL_MACHINE_TYPE] [--cloud-sql-preferred-zone=CLOUD_SQL_PREFERRED_ZONE] - [--disk-size=DISK_SIZE] [--enable-cloud-data-lineage-integration] - [--enable-high-resilience] [--env-variables=[NAME=VALUE,...]] + [--disk-size=DISK_SIZE] [--enable-high-resilience] + [--env-variables=[NAME=VALUE,...]] [--environment-size=ENVIRONMENT_SIZE] [--labels=[KEY=VALUE,...]] [--machine-type=MACHINE_TYPE] [--node-count=NODE_COUNT] [--oauth-scopes=[SCOPE,...]] [--python-version=PYTHON_VERSION] @@ -29,6 +29,8 @@ SYNOPSIS --max-pods-per-node=MAX_PODS_PER_NODE --services-ipv4-cidr=SERVICES_IPV4_CIDR --services-secondary-range-name=SERVICES_SECONDARY_RANGE_NAME] + [--disable-cloud-data-lineage-integration + | --enable-cloud-data-lineage-integration] [--enable-master-authorized-networks --master-authorized-networks=[NETWORK,...]] [--enable-scheduled-snapshot-creation @@ -131,12 +133,6 @@ FLAGS multiple of gigabytes. Cannot be updated after the environment has been created. If units are not provided, defaults to GB. - Group of arguments for setting Cloud Data Lineage integration - configuration in Composer 2. - - --enable-cloud-data-lineage-integration - Enable Cloud Data Lineage integration. - --enable-high-resilience Enable high resilience, supported for Composer 2 Environments. @@ -380,6 +376,14 @@ FLAGS When used with Composer 1.x, cannot be specified unless --enable-ip-alias is also specified. + At most one of these can be specified: + + --disable-cloud-data-lineage-integration + Disable Cloud Data Lineage integration. + + --enable-cloud-data-lineage-integration + Enable Cloud Data Lineage integration. + Master Authorized Networks configuration --enable-master-authorized-networks diff --git a/gcloud/beta/compute/forwarding-rules/create b/gcloud/beta/compute/forwarding-rules/create index b0013b427..52b8b32bb 100644 --- a/gcloud/beta/compute/forwarding-rules/create +++ b/gcloud/beta/compute/forwarding-rules/create @@ -114,12 +114,14 @@ REQUIRED FLAGS Target gRPC proxy that receives the traffic. --target-http-proxy=TARGET_HTTP_PROXY - Target HTTP proxy that receives the traffic. Acceptable values for - --ports flag are: 80, 8080. + Target HTTP proxy that receives the traffic. For the acceptable + ports, see Port specifications + (https://cloud.google.com/load-balancing/docs/forwarding-rule-concepts#port_specifications). --target-https-proxy=TARGET_HTTPS_PROXY - Target HTTPS proxy that receives the traffic. Acceptable values for - --ports flag are: 443. + Target HTTPS proxy that receives the traffic. For the acceptable + ports, see Port specifications + (https://cloud.google.com/load-balancing/docs/forwarding-rule-concepts#port_specifications). --target-instance=TARGET_INSTANCE Name of the target instance that receives the traffic. The target diff --git a/gcloud/beta/compute/forwarding-rules/set-target b/gcloud/beta/compute/forwarding-rules/set-target index 62341fa7e..a6ffc90c6 100644 --- a/gcloud/beta/compute/forwarding-rules/set-target +++ b/gcloud/beta/compute/forwarding-rules/set-target @@ -79,12 +79,14 @@ REQUIRED FLAGS Target gRPC proxy that receives the traffic. --target-http-proxy=TARGET_HTTP_PROXY - Target HTTP proxy that receives the traffic. Acceptable values for - --ports flag are: 80, 8080. + Target HTTP proxy that receives the traffic. For the acceptable + ports, see Port specifications + (https://cloud.google.com/load-balancing/docs/forwarding-rule-concepts#port_specifications). --target-https-proxy=TARGET_HTTPS_PROXY - Target HTTPS proxy that receives the traffic. Acceptable values for - --ports flag are: 443. + Target HTTPS proxy that receives the traffic. For the acceptable + ports, see Port specifications + (https://cloud.google.com/load-balancing/docs/forwarding-rule-concepts#port_specifications). --target-instance=TARGET_INSTANCE Name of the target instance that receives the traffic. The target diff --git a/gcloud/beta/compute/instances/create b/gcloud/beta/compute/instances/create index 65a11442f..1dfb9737c 100644 --- a/gcloud/beta/compute/instances/create +++ b/gcloud/beta/compute/instances/create @@ -840,7 +840,7 @@ FLAGS --source-instance-template=SOURCE_INSTANCE_TEMPLATE The name of the instance template that the instance will be created - from. + from. An instance template can be a global/regional resource. Users can also override machine type and labels. Values of other flags will be ignored and --source-instance-template will be used instead. diff --git a/gcloud/beta/compute/instances/create-with-container b/gcloud/beta/compute/instances/create-with-container index 86ed2e0fb..ead75ab34 100644 --- a/gcloud/beta/compute/instances/create-with-container +++ b/gcloud/beta/compute/instances/create-with-container @@ -695,7 +695,7 @@ FLAGS --source-instance-template=SOURCE_INSTANCE_TEMPLATE The name of the instance template that the instance will be created - from. + from. An instance template can be a global/regional resource. Users can also override machine type and labels. Values of other flags will be ignored and --source-instance-template will be used instead. diff --git a/gcloud/beta/compute/instances/ops-agents/policies/create b/gcloud/beta/compute/instances/ops-agents/policies/create index 0971afe67..955d4cd57 100644 --- a/gcloud/beta/compute/instances/ops-agents/policies/create +++ b/gcloud/beta/compute/instances/ops-agents/policies/create @@ -247,6 +247,7 @@ REQUIRED FLAGS ubuntu 21.10 ubuntu 22.04 ubuntu 23.04 + ubuntu 23.10 windows 10.* windows 6.* diff --git a/gcloud/beta/compute/instances/ops-agents/policies/update b/gcloud/beta/compute/instances/ops-agents/policies/update index d17e98fec..992b3fbaf 100644 --- a/gcloud/beta/compute/instances/ops-agents/policies/update +++ b/gcloud/beta/compute/instances/ops-agents/policies/update @@ -284,6 +284,7 @@ FLAGS ubuntu 21.10 ubuntu 22.04 ubuntu 23.04 + ubuntu 23.10 windows 10.* windows 6.* diff --git a/gcloud/beta/compute/instances/set-name b/gcloud/beta/compute/instances/set-name index 1fdb2614f..bfb6e406e 100644 --- a/gcloud/beta/compute/instances/set-name +++ b/gcloud/beta/compute/instances/set-name @@ -60,8 +60,10 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud compute instances set-name $ gcloud alpha compute instances set-name diff --git a/gcloud/beta/compute/public-advertised-prefixes/create b/gcloud/beta/compute/public-advertised-prefixes/create index c71d0c3dd..b00641c1c 100644 --- a/gcloud/beta/compute/public-advertised-prefixes/create +++ b/gcloud/beta/compute/public-advertised-prefixes/create @@ -20,11 +20,11 @@ POSITIONAL ARGUMENTS REQUIRED FLAGS --dns-verification-ip=DNS_VERIFICATION_IP - IPv4 address to use for verification. It must be within the IPv4 range + IP address to use for verification. It must be within the IP range specified in --range. --range=RANGE - IPv4 range allocated to this public advertised prefix, in CIDR format. + IP range allocated to this public advertised prefix, in CIDR format. OPTIONAL FLAGS --description=DESCRIPTION diff --git a/gcloud/beta/compute/public-delegated-prefixes/create b/gcloud/beta/compute/public-delegated-prefixes/create index 1d8e7474f..725ab719a 100644 --- a/gcloud/beta/compute/public-delegated-prefixes/create +++ b/gcloud/beta/compute/public-delegated-prefixes/create @@ -22,8 +22,8 @@ POSITIONAL ARGUMENTS REQUIRED FLAGS --range=RANGE - IPv4 range from this public delegated prefix that should be delegated, - in CIDR format. It must be smaller than parent public advertised prefix + IP range from this public delegated prefix that should be delegated, in + CIDR format. It must be smaller than parent public advertised prefix range. Exactly one of these must be specified: diff --git a/gcloud/beta/compute/security-policies/rules/create b/gcloud/beta/compute/security-policies/rules/create index ff5033945..4f258f619 100644 --- a/gcloud/beta/compute/security-policies/rules/create +++ b/gcloud/beta/compute/security-policies/rules/create @@ -19,8 +19,8 @@ SYNOPSIS [--conform-action=CONFORM_ACTION] [--description=DESCRIPTION] [--enforce-on-key=ENFORCE_ON_KEY] [--enforce-on-key-configs=[[all],[ip],[xff-ip], - [http-cookie=HTTP_COOKIE], - [http-header=HTTP_HEADER],[http-path],[sni],[region-code]],[...]] + [http-cookie=HTTP_COOKIE],[http-header=HTTP_HEADER],[http-path], + [sni],[region-code],[tls-ja3-fingerprint],[user-ip]],[...]] [--enforce-on-key-name=ENFORCE_ON_KEY_NAME] [--exceed-action=EXCEED_ACTION] [--exceed-redirect-target=EXCEED_REDIRECT_TARGET] @@ -177,11 +177,16 @@ OPTIONAL FLAGS the TLS session of the HTTPS request ◆ region-code: key type takes the value of the region code from which the request originates + ◆ tls-ja3-fingerprint: key type takes the value of JA3 TLS/SSL + fingerprint if the client connects using HTTPS, HTTP/2 or HTTP/3 + ◆ user-ip: key type takes the IP address of the originating client, + which is resolved based on user-ip-request-headers configured with + the security policy ENFORCE_ON_KEY must be one of: ip, all, http-header, xff-ip, - http-cookie, http-path, sni, region-code. + http-cookie, http-path, sni, region-code, tls-ja3-fingerprint, user-ip. - --enforce-on-key-configs=[[all],[ip],[xff-ip],[http-cookie=HTTP_COOKIE],[http-header=HTTP_HEADER],[http-path],[sni],[region-code]],[...] + --enforce-on-key-configs=[[all],[ip],[xff-ip],[http-cookie=HTTP_COOKIE],[http-header=HTTP_HEADER],[http-path],[sni],[region-code],[tls-ja3-fingerprint],[user-ip]],[...] Specify up to 3 key type/name pairs to rate limit. Valid key types are: ◆ ip: each client IP address has this limit enforced separately @@ -197,6 +202,11 @@ OPTIONAL FLAGS the TLS session of the HTTPS request ◆ region-code: key type takes the value of the region code from which the request originates + ◆ tls-ja3-fingerprint: key type takes the value of JA3 TLS/SSL + fingerprint if the client connects using HTTPS, HTTP/2 or HTTP/3 + ◆ user-ip: key type takes the IP address of the originating client, + which is resolved based on user-ip-request-headers configured with + the security policy Key names are only applicable to the following key types: ◆ http-header: The name of the HTTP header whose value is taken as diff --git a/gcloud/beta/compute/security-policies/rules/update b/gcloud/beta/compute/security-policies/rules/update index 098b5876b..b9c13e04d 100644 --- a/gcloud/beta/compute/security-policies/rules/update +++ b/gcloud/beta/compute/security-policies/rules/update @@ -10,8 +10,8 @@ SYNOPSIS [--conform-action=CONFORM_ACTION] [--description=DESCRIPTION] [--enforce-on-key=ENFORCE_ON_KEY] [--enforce-on-key-configs=[[all],[ip],[xff-ip], - [http-cookie=HTTP_COOKIE], - [http-header=HTTP_HEADER],[http-path],[sni],[region-code]],[...]] + [http-cookie=HTTP_COOKIE],[http-header=HTTP_HEADER],[http-path], + [sni],[region-code],[tls-ja3-fingerprint],[user-ip]],[...]] [--enforce-on-key-name=ENFORCE_ON_KEY_NAME] [--exceed-action=EXCEED_ACTION] [--exceed-redirect-target=EXCEED_REDIRECT_TARGET] @@ -128,11 +128,16 @@ FLAGS the TLS session of the HTTPS request ◆ region-code: key type takes the value of the region code from which the request originates + ◆ tls-ja3-fingerprint: key type takes the value of JA3 TLS/SSL + fingerprint if the client connects using HTTPS, HTTP/2 or HTTP/3 + ◆ user-ip: key type takes the IP address of the originating client, + which is resolved based on user-ip-request-headers configured with + the security policy ENFORCE_ON_KEY must be one of: ip, all, http-header, xff-ip, - http-cookie, http-path, sni, region-code. + http-cookie, http-path, sni, region-code, tls-ja3-fingerprint, user-ip. - --enforce-on-key-configs=[[all],[ip],[xff-ip],[http-cookie=HTTP_COOKIE],[http-header=HTTP_HEADER],[http-path],[sni],[region-code]],[...] + --enforce-on-key-configs=[[all],[ip],[xff-ip],[http-cookie=HTTP_COOKIE],[http-header=HTTP_HEADER],[http-path],[sni],[region-code],[tls-ja3-fingerprint],[user-ip]],[...] Specify up to 3 key type/name pairs to rate limit. Valid key types are: ◆ ip: each client IP address has this limit enforced separately @@ -148,6 +153,11 @@ FLAGS the TLS session of the HTTPS request ◆ region-code: key type takes the value of the region code from which the request originates + ◆ tls-ja3-fingerprint: key type takes the value of JA3 TLS/SSL + fingerprint if the client connects using HTTPS, HTTP/2 or HTTP/3 + ◆ user-ip: key type takes the IP address of the originating client, + which is resolved based on user-ip-request-headers configured with + the security policy Key names are only applicable to the following key types: ◆ http-header: The name of the HTTP header whose value is taken as diff --git a/gcloud/beta/config/get b/gcloud/beta/config/get index 39bb3244f..be285c2c2 100644 --- a/gcloud/beta/config/get +++ b/gcloud/beta/config/get @@ -298,6 +298,10 @@ AVAILABLE PROPERTIES Private Service Connect usage, see https://cloud.google.com/vpc/docs/configure-private-service-connect-apis#using-endpoints + config + Overrides API endpoint for gcloud infra-manager command group. + Defaults to https://config.googleapis.com/ + container Overrides API endpoint for gcloud container command group. Defaults to https://container.googleapis.com/ @@ -406,9 +410,6 @@ AVAILABLE PROPERTIES Overrides API endpoint for gcloud ids command group. Defaults to https://ids.googleapis.com/ - inframanager - Overrides API endpoint for gcloud infra-manager command group. - krmapihosting Overrides API endpoint for gcloud anthos config controller command group. Defaults to https://krmapihosting.googleapis.com/ @@ -572,6 +573,10 @@ AVAILABLE PROPERTIES Overrides API endpoint for gcloud ml vision command group. Defaults to https://vision.googleapis.com/ + vmmigration + Overrides API endpoint for gcloud migration vms command group. + Defaults to https://vmmigration.googleapis.com/ + vmwareengine Overrides API endpoint for gcloud vmware command group. Defaults to https://vmwareengine.googleapis.com/ diff --git a/gcloud/beta/config/help b/gcloud/beta/config/help index ab2305e05..3daf3c73a 100644 --- a/gcloud/beta/config/help +++ b/gcloud/beta/config/help @@ -330,6 +330,10 @@ AVAILABLE PROPERTIES Private Service Connect usage, see https://cloud.google.com/vpc/docs/configure-private-service-connect-apis#using-endpoints + config + Overrides API endpoint for gcloud infra-manager command group. + Defaults to https://config.googleapis.com/ + container Overrides API endpoint for gcloud container command group. Defaults to https://container.googleapis.com/ @@ -438,9 +442,6 @@ AVAILABLE PROPERTIES Overrides API endpoint for gcloud ids command group. Defaults to https://ids.googleapis.com/ - inframanager - Overrides API endpoint for gcloud infra-manager command group. - krmapihosting Overrides API endpoint for gcloud anthos config controller command group. Defaults to https://krmapihosting.googleapis.com/ @@ -604,6 +605,10 @@ AVAILABLE PROPERTIES Overrides API endpoint for gcloud ml vision command group. Defaults to https://vision.googleapis.com/ + vmmigration + Overrides API endpoint for gcloud migration vms command group. + Defaults to https://vmmigration.googleapis.com/ + vmwareengine Overrides API endpoint for gcloud vmware command group. Defaults to https://vmwareengine.googleapis.com/ diff --git a/gcloud/beta/config/list b/gcloud/beta/config/list index 56511eb3e..2fe4fc1d4 100644 --- a/gcloud/beta/config/list +++ b/gcloud/beta/config/list @@ -342,6 +342,10 @@ AVAILABLE PROPERTIES Private Service Connect usage, see https://cloud.google.com/vpc/docs/configure-private-service-connect-apis#using-endpoints + config + Overrides API endpoint for gcloud infra-manager command group. + Defaults to https://config.googleapis.com/ + container Overrides API endpoint for gcloud container command group. Defaults to https://container.googleapis.com/ @@ -450,9 +454,6 @@ AVAILABLE PROPERTIES Overrides API endpoint for gcloud ids command group. Defaults to https://ids.googleapis.com/ - inframanager - Overrides API endpoint for gcloud infra-manager command group. - krmapihosting Overrides API endpoint for gcloud anthos config controller command group. Defaults to https://krmapihosting.googleapis.com/ @@ -616,6 +617,10 @@ AVAILABLE PROPERTIES Overrides API endpoint for gcloud ml vision command group. Defaults to https://vision.googleapis.com/ + vmmigration + Overrides API endpoint for gcloud migration vms command group. + Defaults to https://vmmigration.googleapis.com/ + vmwareengine Overrides API endpoint for gcloud vmware command group. Defaults to https://vmwareengine.googleapis.com/ diff --git a/gcloud/beta/config/set b/gcloud/beta/config/set index 669499788..3ae64f393 100644 --- a/gcloud/beta/config/set +++ b/gcloud/beta/config/set @@ -345,6 +345,10 @@ AVAILABLE PROPERTIES Private Service Connect usage, see https://cloud.google.com/vpc/docs/configure-private-service-connect-apis#using-endpoints + config + Overrides API endpoint for gcloud infra-manager command group. + Defaults to https://config.googleapis.com/ + container Overrides API endpoint for gcloud container command group. Defaults to https://container.googleapis.com/ @@ -453,9 +457,6 @@ AVAILABLE PROPERTIES Overrides API endpoint for gcloud ids command group. Defaults to https://ids.googleapis.com/ - inframanager - Overrides API endpoint for gcloud infra-manager command group. - krmapihosting Overrides API endpoint for gcloud anthos config controller command group. Defaults to https://krmapihosting.googleapis.com/ @@ -619,6 +620,10 @@ AVAILABLE PROPERTIES Overrides API endpoint for gcloud ml vision command group. Defaults to https://vision.googleapis.com/ + vmmigration + Overrides API endpoint for gcloud migration vms command group. + Defaults to https://vmmigration.googleapis.com/ + vmwareengine Overrides API endpoint for gcloud vmware command group. Defaults to https://vmwareengine.googleapis.com/ diff --git a/gcloud/beta/config/unset b/gcloud/beta/config/unset index 8ebf5aed2..5c4aed3dc 100644 --- a/gcloud/beta/config/unset +++ b/gcloud/beta/config/unset @@ -306,6 +306,10 @@ AVAILABLE PROPERTIES Private Service Connect usage, see https://cloud.google.com/vpc/docs/configure-private-service-connect-apis#using-endpoints + config + Overrides API endpoint for gcloud infra-manager command group. + Defaults to https://config.googleapis.com/ + container Overrides API endpoint for gcloud container command group. Defaults to https://container.googleapis.com/ @@ -414,9 +418,6 @@ AVAILABLE PROPERTIES Overrides API endpoint for gcloud ids command group. Defaults to https://ids.googleapis.com/ - inframanager - Overrides API endpoint for gcloud infra-manager command group. - krmapihosting Overrides API endpoint for gcloud anthos config controller command group. Defaults to https://krmapihosting.googleapis.com/ @@ -580,6 +581,10 @@ AVAILABLE PROPERTIES Overrides API endpoint for gcloud ml vision command group. Defaults to https://vision.googleapis.com/ + vmmigration + Overrides API endpoint for gcloud migration vms command group. + Defaults to https://vmmigration.googleapis.com/ + vmwareengine Overrides API endpoint for gcloud vmware command group. Defaults to https://vmwareengine.googleapis.com/ diff --git a/gcloud/beta/container/clusters/create b/gcloud/beta/container/clusters/create index 872d09ea2..ddd337ac6 100644 --- a/gcloud/beta/container/clusters/create +++ b/gcloud/beta/container/clusters/create @@ -72,11 +72,11 @@ SYNOPSIS [--workload-metadata=WORKLOAD_METADATA] [--workload-pool=WORKLOAD_POOL] [--workload-vulnerability-scanning=WORKLOAD_VULNERABILITY_SCANNING] [--additional-zones=ZONE,[ZONE,...] | --node-locations=ZONE,[ZONE,...]] - [--cluster-dns=CLUSTER_DNS --cluster-dns-domain=CLUSTER_DNS_DOMAIN - --cluster-dns-scope=CLUSTER_DNS_SCOPE] [--binauthz-policy-bindings=[name=BINAUTHZ_POLICY] --binauthz-evaluation-mode=BINAUTHZ_EVALUATION_MODE | --enable-binauthz] + [--cluster-dns=CLUSTER_DNS --cluster-dns-domain=CLUSTER_DNS_DOMAIN + --cluster-dns-scope=CLUSTER_DNS_SCOPE] [--dataplane-v2-observability-mode=DATAPLANE_V2_OBSERVABILITY_MODE | --disable-dataplane-v2-flow-observability | --enable-dataplane-v2-flow-observability] @@ -1310,6 +1310,27 @@ FLAGS --location us-central1-a \ --node-locations us-central1-a,us-central1-b + Flags for Binary Authorization: + + --binauthz-policy-bindings=[name=BINAUTHZ_POLICY] + The relative resource name of the Binary Authorization policy to + audit and/or enforce. GKE policies have the following format: + projects/{project_number}/platforms/gke/policies/{policy_id}. + + At most one of these can be specified: + + --binauthz-evaluation-mode=BINAUTHZ_EVALUATION_MODE + Enable Binary Authorization for this cluster. + BINAUTHZ_EVALUATION_MODE must be one of: disabled, policy-bindings, + policy-bindings-and-project-singleton-policy-enforce, + project-singleton-policy-enforce. + + --enable-binauthz + (DEPRECATED) Enable Binary Authorization for this cluster. + + The --enable-binauthz flag is deprecated. Please use + --binauthz-evaluation-mode instead. + ClusterDNS --cluster-dns=CLUSTER_DNS @@ -1339,27 +1360,6 @@ FLAGS vpc Configures the Cloud DNS zone to be private to the VPC Network. - Flags for Binary Authorization: - - --binauthz-policy-bindings=[name=BINAUTHZ_POLICY] - The relative resource name of the Binary Authorization policy to - audit and/or enforce. GKE policies have the following format: - projects/{project_number}/platforms/gke/policies/{policy_id}. - - At most one of these can be specified: - - --binauthz-evaluation-mode=BINAUTHZ_EVALUATION_MODE - Enable Binary Authorization for this cluster. - BINAUTHZ_EVALUATION_MODE must be one of: disabled, policy-bindings, - policy-bindings-and-project-singleton-policy-enforce, - project-singleton-policy-enforce. - - --enable-binauthz - (DEPRECATED) Enable Binary Authorization for this cluster. - - The --enable-binauthz flag is deprecated. Please use - --binauthz-evaluation-mode instead. - At most one of these can be specified: --dataplane-v2-observability-mode=DATAPLANE_V2_OBSERVABILITY_MODE diff --git a/gcloud/beta/container/clusters/update b/gcloud/beta/container/clusters/update index e82679aa2..90515a452 100644 --- a/gcloud/beta/container/clusters/update +++ b/gcloud/beta/container/clusters/update @@ -44,8 +44,6 @@ SYNOPSIS | --additional-pod-ipv4-ranges=NAME,[NAME,...] --remove-additional-pod-ipv4-ranges=NAME,[NAME,...] | --additional-zones=[ZONE,...] | --node-locations=ZONE,[ZONE,...] - | --cluster-dns=CLUSTER_DNS --cluster-dns-domain=CLUSTER_DNS_DOMAIN - --cluster-dns-scope=CLUSTER_DNS_SCOPE | --binauthz-policy-bindings=[name=BINAUTHZ_POLICY] --binauthz-evaluation-mode=BINAUTHZ_EVALUATION_MODE | --enable-binauthz | --clear-maintenance-window @@ -61,6 +59,8 @@ SYNOPSIS | --enable-network-egress-metering --enable-resource-consumption-metering --resource-usage-bigquery-dataset=RESOURCE_USAGE_BIGQUERY_DATASET + | --cluster-dns=CLUSTER_DNS --cluster-dns-domain=CLUSTER_DNS_DOMAIN + --cluster-dns-scope=CLUSTER_DNS_SCOPE | --dataplane-v2-observability-mode=DATAPLANE_V2_OBSERVABILITY_MODE | --disable-dataplane-v2-flow-observability | --enable-dataplane-v2-flow-observability @@ -748,35 +748,6 @@ REQUIRED FLAGS --location us-central1-a \ --node-locations us-central1-a,us-central1-b - ClusterDNS - - --cluster-dns=CLUSTER_DNS - DNS provider to use for this cluster. CLUSTER_DNS must be one of: - - clouddns - Selects Cloud DNS as the DNS provider for the cluster. - default - Selects the default DNS provider (kube-dns) for the cluster. - kubedns - Selects Kube DNS as the DNS provider for the cluster. - - --cluster-dns-domain=CLUSTER_DNS_DOMAIN - DNS domain for this cluster. The default value is cluster.local. - This is configurable when --cluster-dns=clouddns and - --cluster-dns-scope=vpc are set. The value must be a valid DNS - subdomain as defined in RFC 1123. - - --cluster-dns-scope=CLUSTER_DNS_SCOPE - DNS scope for the Cloud DNS zone created - valid only with - --cluster-dns=clouddns. Defaults to cluster. - - CLUSTER_DNS_SCOPE must be one of: - - cluster - Configures the Cloud DNS zone to be private to the cluster. - vpc - Configures the Cloud DNS zone to be private to the VPC Network. - Flags for Binary Authorization: --binauthz-policy-bindings=[name=BINAUTHZ_POLICY] @@ -935,6 +906,35 @@ REQUIRED FLAGS $ gcloud beta container clusters update example-cluster \ --resource-usage-bigquery-dataset=example_bigquery_dataset_name + ClusterDNS + + --cluster-dns=CLUSTER_DNS + DNS provider to use for this cluster. CLUSTER_DNS must be one of: + + clouddns + Selects Cloud DNS as the DNS provider for the cluster. + default + Selects the default DNS provider (kube-dns) for the cluster. + kubedns + Selects Kube DNS as the DNS provider for the cluster. + + --cluster-dns-domain=CLUSTER_DNS_DOMAIN + DNS domain for this cluster. The default value is cluster.local. + This is configurable when --cluster-dns=clouddns and + --cluster-dns-scope=vpc are set. The value must be a valid DNS + subdomain as defined in RFC 1123. + + --cluster-dns-scope=CLUSTER_DNS_SCOPE + DNS scope for the Cloud DNS zone created - valid only with + --cluster-dns=clouddns. Defaults to cluster. + + CLUSTER_DNS_SCOPE must be one of: + + cluster + Configures the Cloud DNS zone to be private to the cluster. + vpc + Configures the Cloud DNS zone to be private to the VPC Network. + At most one of these can be specified: --dataplane-v2-observability-mode=DATAPLANE_V2_OBSERVABILITY_MODE diff --git a/gcloud/beta/container/fleet/clusterupgrade/create b/gcloud/beta/container/fleet/clusterupgrade/create new file mode 100644 index 000000000..1a097949b --- /dev/null +++ b/gcloud/beta/container/fleet/clusterupgrade/create @@ -0,0 +1,95 @@ +NAME + gcloud beta container fleet clusterupgrade create - create the + clusterupgrade feature for a fleet within a given project + +SYNOPSIS + gcloud beta container fleet clusterupgrade create + [--default-upgrade-soaking=DEFAULT_UPGRADE_SOAKING] + [--upstream-fleet=UPSTREAM_FLEET] + [--add-upgrade-soaking-override=ADD_UPGRADE_SOAKING_OVERRIDE + --upgrade-selector=[name=NAME],[version=VERSION]] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Create the clusterupgrade feature for a fleet within a given + project. + +EXAMPLES + To create the clusterupgrade feature for the current fleet, run: + + $ gcloud beta container fleet clusterupgrade create \ + --default-upgrade-soaking=DEFAULT_UPGRADE_SOAKING + +FLAGS + --default-upgrade-soaking=DEFAULT_UPGRADE_SOAKING + Configures the default soaking duration for each upgrade propagating + through the current fleet to become "COMPLETE". Soaking begins after + all clusters in the fleet are on the target version, or after 30 days + if all cluster upgrades are not complete. Once an upgrade state becomes + "COMPLETE", it will automatically be propagated to the downstream + fleet. Max is 30 days. + + To configure Rollout Sequencing for a fleet, this attribute must be + set. To do this while specifying a default soaking duration of 7 days, + run: + + $ gcloud beta container fleet clusterupgrade create \ + --default-upgrade-soaking=7d + + --upstream-fleet=UPSTREAM_FLEET + The upstream fleet. GKE will finish upgrades on the upstream fleet + before applying the same upgrades to the current fleet. + + To configure the upstream fleet, run: + + $ gcloud beta container fleet clusterupgrade create \ + --upstream-fleet={upstream_fleet} + + Upgrade soaking override. + + Defines a specific soaking time override for a particular upgrade + propagating through the current fleet that supercedes the default + soaking duration configured by `--default-upgrade-soaking`. + + To set an upgrade soaking override of 12 hours for the upgrade with + name, `k8s_control_plane`, and version, `1.23.1-gke.1000`, run: + + $ gcloud beta container fleet clusterupgrade create \ + --add-upgrade-soaking-override=12h \ + --upgrade-selector=name="k8s_control_plane",\ + version="1.23.1-gke.1000" + + --add-upgrade-soaking-override=ADD_UPGRADE_SOAKING_OVERRIDE + Overrides the soaking time for a particular upgrade name and version + propagating through the current fleet. Set soaking to 0 days to + bypass soaking and fast-forward the upgrade to the downstream fleet. + + See $ gcloud topic datetimes for information on duration formats. + + This flag argument must be specified if any of the other arguments in + this group are specified. + + --upgrade-selector=[name=NAME],[version=VERSION] + Name and version of the upgrade to be overridden where version is a + full GKE version. Currently, name can be either k8s_control_plane or + k8s_node. + + This flag argument must be specified if any of the other arguments in + this group are specified. + +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 container fleet clusterupgrade create + + $ gcloud alpha container fleet clusterupgrade create + diff --git a/gcloud/beta/container/fleet/clusterupgrade/describe b/gcloud/beta/container/fleet/clusterupgrade/describe new file mode 100644 index 000000000..828e73461 --- /dev/null +++ b/gcloud/beta/container/fleet/clusterupgrade/describe @@ -0,0 +1,48 @@ +NAME + gcloud beta container fleet clusterupgrade describe - describe the + clusterupgrade feature for a fleet within a given project + +SYNOPSIS + gcloud beta container fleet clusterupgrade describe + [--show-linked-cluster-upgrade] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Describe the Fleet clusterupgrade feature used for configuring + fleet-based rollout sequencing. + +EXAMPLES + To view the cluster upgrade feature information for the current fleet, run: + + $ gcloud beta container fleet clusterupgrade describe + +FLAGS + --show-linked-cluster-upgrade + Shows the cluster upgrade feature information for the current fleet as + well as information for all other fleets linked in the same rollout + sequence (provided that the caller has permission to view the upstream + and downstream fleets). This displays cluster upgrade information for + fleets in the current fleet's rollout sequence in order of furthest + upstream to downstream. + + To view the cluster upgrade feature information for the rollout + sequence containing the current fleet, run: + + $ gcloud beta container fleet clusterupgrade describe \ + --show-linked-cluster-upgrade + +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 container fleet clusterupgrade describe + + $ gcloud alpha container fleet clusterupgrade describe + diff --git a/gcloud/beta/container/fleet/clusterupgrade/help b/gcloud/beta/container/fleet/clusterupgrade/help new file mode 100644 index 000000000..a03589104 --- /dev/null +++ b/gcloud/beta/container/fleet/clusterupgrade/help @@ -0,0 +1,39 @@ +NAME + gcloud beta container fleet clusterupgrade - configure the Fleet + clusterupgrade feature + +SYNOPSIS + gcloud beta container fleet clusterupgrade COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) This fleet feature is used to configure fleet-based rollout + sequencing. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + create + (BETA) Create the clusterupgrade feature for a fleet within a given + project. + + describe + (BETA) Describe the clusterupgrade feature for a fleet within a given + project. + + update + (BETA) Update the clusterupgrade feature for a fleet within a given + project. + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud container fleet clusterupgrade + + $ gcloud alpha container fleet clusterupgrade + diff --git a/gcloud/beta/container/fleet/clusterupgrade/update b/gcloud/beta/container/fleet/clusterupgrade/update new file mode 100644 index 000000000..3f78cbec7 --- /dev/null +++ b/gcloud/beta/container/fleet/clusterupgrade/update @@ -0,0 +1,123 @@ +NAME + gcloud beta container fleet clusterupgrade update - update the + clusterupgrade feature for a fleet within a given project + +SYNOPSIS + gcloud beta container fleet clusterupgrade update + [--default-upgrade-soaking=DEFAULT_UPGRADE_SOAKING] + [--remove-upgrade-soaking-overrides + | --add-upgrade-soaking-override=ADD_UPGRADE_SOAKING_OVERRIDE + --upgrade-selector=[name=NAME],[version=VERSION]] + [--reset-upstream-fleet | --upstream-fleet=UPSTREAM_FLEET] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Update the clusterupgrade feature for a fleet within a given + project. + +EXAMPLES + To update the clusterupgrade feature for the current fleet, run: + + $ gcloud beta container fleet clusterupgrade update \ + --default-upgrade-soaking=DEFAULT_UPGRADE_SOAKING + +FLAGS + --default-upgrade-soaking=DEFAULT_UPGRADE_SOAKING + Configures the default soaking duration for each upgrade propagating + through the current fleet to become "COMPLETE". Soaking begins after + all clusters in the fleet are on the target version, or after 30 days + if all cluster upgrades are not complete. Once an upgrade state becomes + "COMPLETE", it will automatically be propagated to the downstream + fleet. Max is 30 days. + + To configure Rollout Sequencing for a fleet, this attribute must be + set. To do this while specifying a default soaking duration of 7 days, + run: + + $ gcloud beta container fleet clusterupgrade update \ + --default-upgrade-soaking=7d + + At most one of these can be specified: + + --remove-upgrade-soaking-overrides + Removes soaking time overrides for all upgrades propagating through + the current fleet. Consequently, all upgrades will follow the soak + time configured by --default-upgrade-soaking until new overrides are + configured with --add_upgrade_soaking_override and + --upgrade_selector. + + To remove all configured soaking time overrides, run: + + $ gcloud beta container fleet clusterupgrade update \ + --remove-upgrade-soaking-overrides + + Upgrade soaking override. + + Defines a specific soaking time override for a particular upgrade + propagating through the current fleet that supercedes the default + soaking duration configured by `--default-upgrade-soaking`. + + To set an upgrade soaking override of 12 hours for the upgrade with + name, `k8s_control_plane`, and version, `1.23.1-gke.1000`, run: + + $ gcloud beta container fleet clusterupgrade update \ + --add-upgrade-soaking-override=12h \ + --upgrade-selector=name="k8s_control_plane",\ + version="1.23.1-gke.1000" + + --add-upgrade-soaking-override=ADD_UPGRADE_SOAKING_OVERRIDE + Overrides the soaking time for a particular upgrade name and + version propagating through the current fleet. Set soaking to 0 + days to bypass soaking and fast-forward the upgrade to the + downstream fleet. + + See $ gcloud topic datetimes for information on duration formats. + + This flag argument must be specified if any of the other arguments + in this group are specified. + + --upgrade-selector=[name=NAME],[version=VERSION] + Name and version of the upgrade to be overridden where version is a + full GKE version. Currently, name can be either k8s_control_plane + or k8s_node. + + This flag argument must be specified if any of the other arguments + in this group are specified. + + At most one of these can be specified: + + --reset-upstream-fleet + Clears the relationship between the current fleet and its upstream + fleet in the rollout sequence. + + To remove the link between the current fleet and its upstream fleet, + run: + + $ gcloud beta container fleet clusterupgrade update \ + --reset-upstream-fleet + + --upstream-fleet=UPSTREAM_FLEET + The upstream fleet. GKE will finish upgrades on the upstream fleet + before applying the same upgrades to the current fleet. + + To configure the upstream fleet, run: + + $ gcloud beta container fleet clusterupgrade update \ + --upstream-fleet={upstream_fleet} + +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 container fleet clusterupgrade update + + $ gcloud alpha container fleet clusterupgrade update + diff --git a/gcloud/beta/container/fleet/create b/gcloud/beta/container/fleet/create index 89886232a..4586aa65d 100644 --- a/gcloud/beta/container/fleet/create +++ b/gcloud/beta/container/fleet/create @@ -5,7 +5,7 @@ SYNOPSIS gcloud beta container fleet create [--async] [--display-name=DISPLAY_NAME] [--labels=[KEY=VALUE,...]] [--binauthz-evaluation-mode=BINAUTHZ_EVALUATION_MODE - --binauthz-policy-bindings=[name=BINAUTHZ_POLICY,...] + --binauthz-policy-bindings=[name=BINAUTHZ_POLICY] --security-posture=SECURITY_POSTURE --workload-vulnerability-scanning=WORKLOAD_VULNERABILITY_SCANNING] [GCLOUD_WIDE_FLAG ...] @@ -50,11 +50,11 @@ FLAGS fleet, $ gcloud beta container fleet create \ - --binauthz-evaluation-mode=POLICY_BINDINGS + --binauthz-evaluation-mode=policy-bindings - BINAUTHZ_EVALUATION_MODE must be one of: DISABLED, POLICY_BINDINGS. + BINAUTHZ_EVALUATION_MODE must be one of: disabled, policy-bindings. - --binauthz-policy-bindings=[name=BINAUTHZ_POLICY,...] + --binauthz-policy-bindings=[name=BINAUTHZ_POLICY] The relative resource name of the Binary Authorization policy to audit and/or enforce. GKE policies have the following format: projects/{project_number}/platforms/gke/policies/{policy_id}. diff --git a/gcloud/beta/container/fleet/help b/gcloud/beta/container/fleet/help index 9e1b08915..de9076999 100644 --- a/gcloud/beta/container/fleet/help +++ b/gcloud/beta/container/fleet/help @@ -48,6 +48,9 @@ GROUPS cloudrun (BETA) Manage the CloudRun feature. + clusterupgrade + (BETA) Configure the Fleet clusterupgrade feature. + config-management (BETA) Manage Config Management Feature. diff --git a/gcloud/beta/container/fleet/update b/gcloud/beta/container/fleet/update index 4babbbc16..9b132b71d 100644 --- a/gcloud/beta/container/fleet/update +++ b/gcloud/beta/container/fleet/update @@ -5,7 +5,7 @@ SYNOPSIS gcloud beta container fleet update [--async] [--display-name=DISPLAY_NAME] [--update-labels=[KEY=VALUE,...]] [--binauthz-evaluation-mode=BINAUTHZ_EVALUATION_MODE - --binauthz-policy-bindings=[name=BINAUTHZ_POLICY,...] + --binauthz-policy-bindings=[name=BINAUTHZ_POLICY] --security-posture=SECURITY_POSTURE --workload-vulnerability-scanning=WORKLOAD_VULNERABILITY_SCANNING] [--clear-labels | --remove-labels=[KEY,...]] [GCLOUD_WIDE_FLAG ...] @@ -51,11 +51,11 @@ FLAGS fleet, $ gcloud beta container fleet update \ - --binauthz-evaluation-mode=POLICY_BINDINGS + --binauthz-evaluation-mode=policy-bindings - BINAUTHZ_EVALUATION_MODE must be one of: DISABLED, POLICY_BINDINGS. + BINAUTHZ_EVALUATION_MODE must be one of: disabled, policy-bindings. - --binauthz-policy-bindings=[name=BINAUTHZ_POLICY,...] + --binauthz-policy-bindings=[name=BINAUTHZ_POLICY] The relative resource name of the Binary Authorization policy to audit and/or enforce. GKE policies have the following format: projects/{project_number}/platforms/gke/policies/{policy_id}. diff --git a/gcloud/beta/container/hub/clusterupgrade/create b/gcloud/beta/container/hub/clusterupgrade/create new file mode 100644 index 000000000..c2af0865a --- /dev/null +++ b/gcloud/beta/container/hub/clusterupgrade/create @@ -0,0 +1,95 @@ +NAME + gcloud beta container hub clusterupgrade create - create the clusterupgrade + feature for a fleet within a given project + +SYNOPSIS + gcloud beta container hub clusterupgrade create + [--default-upgrade-soaking=DEFAULT_UPGRADE_SOAKING] + [--upstream-fleet=UPSTREAM_FLEET] + [--add-upgrade-soaking-override=ADD_UPGRADE_SOAKING_OVERRIDE + --upgrade-selector=[name=NAME],[version=VERSION]] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Create the clusterupgrade feature for a fleet within a given + project. + +EXAMPLES + To create the clusterupgrade feature for the current fleet, run: + + $ gcloud beta container hub clusterupgrade create \ + --default-upgrade-soaking=DEFAULT_UPGRADE_SOAKING + +FLAGS + --default-upgrade-soaking=DEFAULT_UPGRADE_SOAKING + Configures the default soaking duration for each upgrade propagating + through the current fleet to become "COMPLETE". Soaking begins after + all clusters in the fleet are on the target version, or after 30 days + if all cluster upgrades are not complete. Once an upgrade state becomes + "COMPLETE", it will automatically be propagated to the downstream + fleet. Max is 30 days. + + To configure Rollout Sequencing for a fleet, this attribute must be + set. To do this while specifying a default soaking duration of 7 days, + run: + + $ gcloud beta container hub clusterupgrade create \ + --default-upgrade-soaking=7d + + --upstream-fleet=UPSTREAM_FLEET + The upstream fleet. GKE will finish upgrades on the upstream fleet + before applying the same upgrades to the current fleet. + + To configure the upstream fleet, run: + + $ gcloud beta container hub clusterupgrade create \ + --upstream-fleet={upstream_fleet} + + Upgrade soaking override. + + Defines a specific soaking time override for a particular upgrade + propagating through the current fleet that supercedes the default + soaking duration configured by `--default-upgrade-soaking`. + + To set an upgrade soaking override of 12 hours for the upgrade with + name, `k8s_control_plane`, and version, `1.23.1-gke.1000`, run: + + $ gcloud beta container hub clusterupgrade create \ + --add-upgrade-soaking-override=12h \ + --upgrade-selector=name="k8s_control_plane",\ + version="1.23.1-gke.1000" + + --add-upgrade-soaking-override=ADD_UPGRADE_SOAKING_OVERRIDE + Overrides the soaking time for a particular upgrade name and version + propagating through the current fleet. Set soaking to 0 days to + bypass soaking and fast-forward the upgrade to the downstream fleet. + + See $ gcloud topic datetimes for information on duration formats. + + This flag argument must be specified if any of the other arguments in + this group are specified. + + --upgrade-selector=[name=NAME],[version=VERSION] + Name and version of the upgrade to be overridden where version is a + full GKE version. Currently, name can be either k8s_control_plane or + k8s_node. + + This flag argument must be specified if any of the other arguments in + this group are specified. + +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 container hub clusterupgrade create + + $ gcloud alpha container hub clusterupgrade create + diff --git a/gcloud/beta/container/hub/clusterupgrade/describe b/gcloud/beta/container/hub/clusterupgrade/describe new file mode 100644 index 000000000..19b607286 --- /dev/null +++ b/gcloud/beta/container/hub/clusterupgrade/describe @@ -0,0 +1,48 @@ +NAME + gcloud beta container hub clusterupgrade describe - describe the + clusterupgrade feature for a fleet within a given project + +SYNOPSIS + gcloud beta container hub clusterupgrade describe + [--show-linked-cluster-upgrade] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Describe the Fleet clusterupgrade feature used for configuring + fleet-based rollout sequencing. + +EXAMPLES + To view the cluster upgrade feature information for the current fleet, run: + + $ gcloud beta container hub clusterupgrade describe + +FLAGS + --show-linked-cluster-upgrade + Shows the cluster upgrade feature information for the current fleet as + well as information for all other fleets linked in the same rollout + sequence (provided that the caller has permission to view the upstream + and downstream fleets). This displays cluster upgrade information for + fleets in the current fleet's rollout sequence in order of furthest + upstream to downstream. + + To view the cluster upgrade feature information for the rollout + sequence containing the current fleet, run: + + $ gcloud beta container hub clusterupgrade describe \ + --show-linked-cluster-upgrade + +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 container hub clusterupgrade describe + + $ gcloud alpha container hub clusterupgrade describe + diff --git a/gcloud/beta/container/hub/clusterupgrade/help b/gcloud/beta/container/hub/clusterupgrade/help new file mode 100644 index 000000000..c5238a13c --- /dev/null +++ b/gcloud/beta/container/hub/clusterupgrade/help @@ -0,0 +1,39 @@ +NAME + gcloud beta container hub clusterupgrade - configure the Fleet + clusterupgrade feature + +SYNOPSIS + gcloud beta container hub clusterupgrade COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) This fleet feature is used to configure fleet-based rollout + sequencing. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + create + (BETA) Create the clusterupgrade feature for a fleet within a given + project. + + describe + (BETA) Describe the clusterupgrade feature for a fleet within a given + project. + + update + (BETA) Update the clusterupgrade feature for a fleet within a given + project. + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud container hub clusterupgrade + + $ gcloud alpha container hub clusterupgrade + diff --git a/gcloud/beta/container/hub/clusterupgrade/update b/gcloud/beta/container/hub/clusterupgrade/update new file mode 100644 index 000000000..2e7121d0f --- /dev/null +++ b/gcloud/beta/container/hub/clusterupgrade/update @@ -0,0 +1,123 @@ +NAME + gcloud beta container hub clusterupgrade update - update the clusterupgrade + feature for a fleet within a given project + +SYNOPSIS + gcloud beta container hub clusterupgrade update + [--default-upgrade-soaking=DEFAULT_UPGRADE_SOAKING] + [--remove-upgrade-soaking-overrides + | --add-upgrade-soaking-override=ADD_UPGRADE_SOAKING_OVERRIDE + --upgrade-selector=[name=NAME],[version=VERSION]] + [--reset-upstream-fleet | --upstream-fleet=UPSTREAM_FLEET] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Update the clusterupgrade feature for a fleet within a given + project. + +EXAMPLES + To update the clusterupgrade feature for the current fleet, run: + + $ gcloud beta container hub clusterupgrade update \ + --default-upgrade-soaking=DEFAULT_UPGRADE_SOAKING + +FLAGS + --default-upgrade-soaking=DEFAULT_UPGRADE_SOAKING + Configures the default soaking duration for each upgrade propagating + through the current fleet to become "COMPLETE". Soaking begins after + all clusters in the fleet are on the target version, or after 30 days + if all cluster upgrades are not complete. Once an upgrade state becomes + "COMPLETE", it will automatically be propagated to the downstream + fleet. Max is 30 days. + + To configure Rollout Sequencing for a fleet, this attribute must be + set. To do this while specifying a default soaking duration of 7 days, + run: + + $ gcloud beta container hub clusterupgrade update \ + --default-upgrade-soaking=7d + + At most one of these can be specified: + + --remove-upgrade-soaking-overrides + Removes soaking time overrides for all upgrades propagating through + the current fleet. Consequently, all upgrades will follow the soak + time configured by --default-upgrade-soaking until new overrides are + configured with --add_upgrade_soaking_override and + --upgrade_selector. + + To remove all configured soaking time overrides, run: + + $ gcloud beta container hub clusterupgrade update \ + --remove-upgrade-soaking-overrides + + Upgrade soaking override. + + Defines a specific soaking time override for a particular upgrade + propagating through the current fleet that supercedes the default + soaking duration configured by `--default-upgrade-soaking`. + + To set an upgrade soaking override of 12 hours for the upgrade with + name, `k8s_control_plane`, and version, `1.23.1-gke.1000`, run: + + $ gcloud beta container hub clusterupgrade update \ + --add-upgrade-soaking-override=12h \ + --upgrade-selector=name="k8s_control_plane",\ + version="1.23.1-gke.1000" + + --add-upgrade-soaking-override=ADD_UPGRADE_SOAKING_OVERRIDE + Overrides the soaking time for a particular upgrade name and + version propagating through the current fleet. Set soaking to 0 + days to bypass soaking and fast-forward the upgrade to the + downstream fleet. + + See $ gcloud topic datetimes for information on duration formats. + + This flag argument must be specified if any of the other arguments + in this group are specified. + + --upgrade-selector=[name=NAME],[version=VERSION] + Name and version of the upgrade to be overridden where version is a + full GKE version. Currently, name can be either k8s_control_plane + or k8s_node. + + This flag argument must be specified if any of the other arguments + in this group are specified. + + At most one of these can be specified: + + --reset-upstream-fleet + Clears the relationship between the current fleet and its upstream + fleet in the rollout sequence. + + To remove the link between the current fleet and its upstream fleet, + run: + + $ gcloud beta container hub clusterupgrade update \ + --reset-upstream-fleet + + --upstream-fleet=UPSTREAM_FLEET + The upstream fleet. GKE will finish upgrades on the upstream fleet + before applying the same upgrades to the current fleet. + + To configure the upstream fleet, run: + + $ gcloud beta container hub clusterupgrade update \ + --upstream-fleet={upstream_fleet} + +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 container hub clusterupgrade update + + $ gcloud alpha container hub clusterupgrade update + diff --git a/gcloud/beta/container/hub/create b/gcloud/beta/container/hub/create index ad5533279..f5b6821df 100644 --- a/gcloud/beta/container/hub/create +++ b/gcloud/beta/container/hub/create @@ -5,7 +5,7 @@ SYNOPSIS gcloud beta container hub create [--async] [--display-name=DISPLAY_NAME] [--labels=[KEY=VALUE,...]] [--binauthz-evaluation-mode=BINAUTHZ_EVALUATION_MODE - --binauthz-policy-bindings=[name=BINAUTHZ_POLICY,...] + --binauthz-policy-bindings=[name=BINAUTHZ_POLICY] --security-posture=SECURITY_POSTURE --workload-vulnerability-scanning=WORKLOAD_VULNERABILITY_SCANNING] [GCLOUD_WIDE_FLAG ...] @@ -50,11 +50,11 @@ FLAGS fleet, $ gcloud beta container hub create \ - --binauthz-evaluation-mode=POLICY_BINDINGS + --binauthz-evaluation-mode=policy-bindings - BINAUTHZ_EVALUATION_MODE must be one of: DISABLED, POLICY_BINDINGS. + BINAUTHZ_EVALUATION_MODE must be one of: disabled, policy-bindings. - --binauthz-policy-bindings=[name=BINAUTHZ_POLICY,...] + --binauthz-policy-bindings=[name=BINAUTHZ_POLICY] The relative resource name of the Binary Authorization policy to audit and/or enforce. GKE policies have the following format: projects/{project_number}/platforms/gke/policies/{policy_id}. diff --git a/gcloud/beta/container/hub/help b/gcloud/beta/container/hub/help index 67daefc15..d25dd8e36 100644 --- a/gcloud/beta/container/hub/help +++ b/gcloud/beta/container/hub/help @@ -48,6 +48,9 @@ GROUPS cloudrun (BETA) Manage the CloudRun feature. + clusterupgrade + (BETA) Configure the Fleet clusterupgrade feature. + config-management (BETA) Manage Config Management Feature. diff --git a/gcloud/beta/container/hub/update b/gcloud/beta/container/hub/update index 9ea42cc88..9d0b23460 100644 --- a/gcloud/beta/container/hub/update +++ b/gcloud/beta/container/hub/update @@ -5,7 +5,7 @@ SYNOPSIS gcloud beta container hub update [--async] [--display-name=DISPLAY_NAME] [--update-labels=[KEY=VALUE,...]] [--binauthz-evaluation-mode=BINAUTHZ_EVALUATION_MODE - --binauthz-policy-bindings=[name=BINAUTHZ_POLICY,...] + --binauthz-policy-bindings=[name=BINAUTHZ_POLICY] --security-posture=SECURITY_POSTURE --workload-vulnerability-scanning=WORKLOAD_VULNERABILITY_SCANNING] [--clear-labels | --remove-labels=[KEY,...]] [GCLOUD_WIDE_FLAG ...] @@ -51,11 +51,11 @@ FLAGS fleet, $ gcloud beta container hub update \ - --binauthz-evaluation-mode=POLICY_BINDINGS + --binauthz-evaluation-mode=policy-bindings - BINAUTHZ_EVALUATION_MODE must be one of: DISABLED, POLICY_BINDINGS. + BINAUTHZ_EVALUATION_MODE must be one of: disabled, policy-bindings. - --binauthz-policy-bindings=[name=BINAUTHZ_POLICY,...] + --binauthz-policy-bindings=[name=BINAUTHZ_POLICY] The relative resource name of the Binary Authorization policy to audit and/or enforce. GKE policies have the following format: projects/{project_number}/platforms/gke/policies/{policy_id}. diff --git a/gcloud/beta/container/node-pools/update b/gcloud/beta/container/node-pools/update index d6fdc83ac..4f6e9dd21 100644 --- a/gcloud/beta/container/node-pools/update +++ b/gcloud/beta/container/node-pools/update @@ -149,9 +149,9 @@ REQUIRED FLAGS --resource-manager-tags=[KEY=VALUE,...] Replaces all the user specified resource manager tags on all nodes in - an existing standard or auto-provisioned node pool in a Standard - cluster with the given comma-separated resource manager tags that has - the GCE_FIREWALL purpose. + an existing node pool in a Standard cluster with the given + comma-separated resource manager tags that has the GCE_FIREWALL + purpose. Examples: diff --git a/gcloud/beta/deploy/apply b/gcloud/beta/deploy/apply index 3f1920949..be719c0d2 100644 --- a/gcloud/beta/deploy/apply +++ b/gcloud/beta/deploy/apply @@ -1,6 +1,7 @@ NAME gcloud beta deploy apply - applies a yaml configuration containing Delivery - Pipeline(s), Target(s) and Automation(s) declarative definitions + Pipeline(s), Target(s), Custom Target Type(s), and Automation(s) + declarative definitions SYNOPSIS gcloud beta deploy apply --file=FILE [--region=REGION] @@ -8,7 +9,8 @@ SYNOPSIS DESCRIPTION (BETA) Applies a yaml configuration containing Delivery Pipeline(s), - Target(s) and Automation(s) declarative definitions. + Target(s), Custom Target Type(s), and Automation(s) declarative + definitions. EXAMPLES To apply a Cloud Deploy YAML file deploy.yaml: diff --git a/gcloud/beta/deploy/custom-target-types/delete b/gcloud/beta/deploy/custom-target-types/delete new file mode 100644 index 000000000..3d21d4764 --- /dev/null +++ b/gcloud/beta/deploy/custom-target-types/delete @@ -0,0 +1,75 @@ +NAME + gcloud beta deploy custom-target-types delete - delete a custom target type + +SYNOPSIS + gcloud beta deploy custom-target-types delete + (CUSTOM_TARGET_TYPE : --region=REGION) [--async] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Delete a custom target type for a specified region. + +EXAMPLES + The following command will delete custom target type + test-custom-target-type, in region us-central1: + + $ gcloud beta deploy custom-target-types delete \ + test-custom-target-type --region=us-central1 + +POSITIONAL ARGUMENTS + Custom target type resource - The name of the custom target type to + delete. The arguments in this group can be used to specify the attributes + of this resource. (NOTE) Some attributes are not given arguments in this + group but can be set in other ways. + + To set the project attribute: + ◆ provide the argument custom_target_type 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. + + CUSTOM_TARGET_TYPE + ID of the custom target type or fully qualified identifier for the + custom target type. + + To set the custom_target_type attribute: + ▸ provide the argument custom_target_type on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --region=REGION + Location of the custom target type. + + To set the region attribute: + ▸ provide the argument custom_target_type on the command line with + a fully specified name; + ▸ provide the argument --region on the command line; + ▸ set the property deploy/region. + +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 clouddeploy/v1 API. The full documentation for this + API can be found at: https://cloud.google.com/deploy/ + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud deploy custom-target-types delete + + $ gcloud alpha deploy custom-target-types delete + diff --git a/gcloud/beta/deploy/custom-target-types/describe b/gcloud/beta/deploy/custom-target-types/describe new file mode 100644 index 000000000..8331447a6 --- /dev/null +++ b/gcloud/beta/deploy/custom-target-types/describe @@ -0,0 +1,71 @@ +NAME + gcloud beta deploy custom-target-types describe - show details for a custom + target type + +SYNOPSIS + gcloud beta deploy custom-target-types describe + (CUSTOM_TARGET_TYPE : --region=REGION) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Show details for a specified custom target type. + +EXAMPLES + To show details about a custom target type test-custom-target-type in + region us-central, run: + + $ gcloud beta deploy custom-target-types describe \ + test-custom-target-type --region=us-central1 + +POSITIONAL ARGUMENTS + Custom target type resource - The name of the custom target type you want + to describe. The arguments in this group can be used to specify the + attributes of this resource. (NOTE) Some attributes are not given + arguments in this group but can be set in other ways. + + To set the project attribute: + ◆ provide the argument custom_target_type 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. + + CUSTOM_TARGET_TYPE + ID of the custom target type or fully qualified identifier for the + custom target type. + + To set the custom_target_type attribute: + ▸ provide the argument custom_target_type on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --region=REGION + Location of the custom target type. + + To set the region attribute: + ▸ provide the argument custom_target_type on the command line with + a fully specified name; + ▸ provide the argument --region on the command line; + ▸ set the property deploy/region. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the clouddeploy/v1 API. The full documentation for this + API can be found at: https://cloud.google.com/deploy/ + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud deploy custom-target-types describe + + $ gcloud alpha deploy custom-target-types describe + diff --git a/gcloud/beta/deploy/custom-target-types/export b/gcloud/beta/deploy/custom-target-types/export new file mode 100644 index 000000000..f3c2c6c37 --- /dev/null +++ b/gcloud/beta/deploy/custom-target-types/export @@ -0,0 +1,74 @@ +NAME + gcloud beta deploy custom-target-types export - returns the .yaml + definition of the specified custom target type + +SYNOPSIS + gcloud beta deploy custom-target-types export + (CUSTOM_TARGET_TYPE : --region=REGION) [--destination=DESTINATION] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) The exported yaml definition can be applied by deploy apply command. + +EXAMPLES + To return the .yaml definition of the custom target type + test-custom-target-type, in region us-central1, run: + + $ gcloud beta deploy custom-target-types export \ + test-custom-target-type --region=us-central1 + +POSITIONAL ARGUMENTS + Custom target type resource - The name of the Custom Target Type. 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 custom_target_type 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. + + CUSTOM_TARGET_TYPE + ID of the custom_target_type or fully qualified identifier for the + custom_target_type. + + To set the custom_target_type attribute: + ▸ provide the argument custom_target_type on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --region=REGION + The Cloud region for the custom_target_type. Alternatively, set the + property [deploy/region]. + + To set the region attribute: + ▸ provide the argument custom_target_type on the command line with + a fully specified name; + ▸ provide the argument --region on the command line; + ▸ set the property deploy/region. + +FLAGS + --destination=DESTINATION + Path to a YAML file where the configuration will be exported. + Alternatively, you may omit this flag to write to standard output. + +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 deploy custom-target-types export + + $ gcloud alpha deploy custom-target-types export + diff --git a/gcloud/beta/deploy/custom-target-types/help b/gcloud/beta/deploy/custom-target-types/help new file mode 100644 index 000000000..24a55e809 --- /dev/null +++ b/gcloud/beta/deploy/custom-target-types/help @@ -0,0 +1,39 @@ +NAME + gcloud beta deploy custom-target-types - create and manage Custom Target + Type resources for Cloud Deploy + +SYNOPSIS + gcloud beta deploy custom-target-types COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Create and manage Custom Target Type resources for Cloud Deploy. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + delete + (BETA) Delete a custom target type. + + describe + (BETA) Show details for a custom target type. + + export + (BETA) Returns the .yaml definition of the specified custom target + type. + + list + (BETA) List the custom target types. + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud deploy custom-target-types + + $ gcloud alpha deploy custom-target-types + diff --git a/gcloud/beta/deploy/custom-target-types/list b/gcloud/beta/deploy/custom-target-types/list new file mode 100644 index 000000000..cbc13b5fe --- /dev/null +++ b/gcloud/beta/deploy/custom-target-types/list @@ -0,0 +1,87 @@ +NAME + gcloud beta deploy custom-target-types list - list the custom target types + +SYNOPSIS + gcloud beta deploy custom-target-types list [--region=REGION] + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) List the custom target types for a specified region. + +EXAMPLES + To list the custom target types in region us-central1, run: + + $ gcloud beta deploy custom-target-types list --region=us-central1 + +FLAGS + Location resource - The region for which you want to list the custom + target types. 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 deploy/region with a fully specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + --region=REGION + ID of the location or fully qualified identifier for the location. + + To set the region attribute: + ▸ provide the argument --region on the command line; + ▸ set the property deploy/region. + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + + --uri + Print a list of resource URIs instead of the default output, and change + the command output to a list of URIs. If this flag is used with + --format, the formatting is applied on this URI list. To display URIs + alongside other keys instead, use the uri() transform. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the clouddeploy/v1 API. The full documentation for this + API can be found at: https://cloud.google.com/deploy/ + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud deploy custom-target-types list + + $ gcloud alpha deploy custom-target-types list + diff --git a/gcloud/beta/deploy/delete b/gcloud/beta/deploy/delete index 62d604404..bb9cf4fa1 100644 --- a/gcloud/beta/deploy/delete +++ b/gcloud/beta/deploy/delete @@ -1,17 +1,17 @@ NAME - gcloud beta deploy delete - deletes delivery pipeline(s) and target(s) in a - yaml configuration + gcloud beta deploy delete - deletes Delivery Pipeline(s), Target(s), Custom + Target Type(s), and Automation(s) in a yaml configuration SYNOPSIS gcloud beta deploy delete --file=FILE [--force] [--region=REGION] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) Deletes delivery pipeline(s) and target(s) in a yaml configuration. + (BETA) Deletes Delivery Pipeline(s), Target(s), Custom Target Type(s), and + Automation(s) in a yaml configuration. EXAMPLES - To delete the delivery pipeline(s) and target(s) in a Cloud Deploy YAML - file deploy.yaml: + To delete the resources in a Cloud Deploy YAML file deploy.yaml: $ gcloud beta deploy delete --file=deploy.yaml --region=us-central1 diff --git a/gcloud/beta/deploy/help b/gcloud/beta/deploy/help index 0c994c1c0..f382c22e3 100644 --- a/gcloud/beta/deploy/help +++ b/gcloud/beta/deploy/help @@ -21,6 +21,9 @@ GROUPS automations (BETA) Manages Automations resources for Cloud Deploy. + custom-target-types + (BETA) Create and manage Custom Target Type resources for Cloud Deploy. + delivery-pipelines (BETA) Create and manage Delivery Pipeline resources for Cloud Deploy. @@ -41,11 +44,12 @@ COMMANDS apply (BETA) Applies a yaml configuration containing Delivery Pipeline(s), - Target(s) and Automation(s) declarative definitions. + Target(s), Custom Target Type(s), and Automation(s) declarative + definitions. delete - (BETA) Deletes delivery pipeline(s) and target(s) in a yaml - configuration. + (BETA) Deletes Delivery Pipeline(s), Target(s), Custom Target Type(s), + and Automation(s) in a yaml configuration. get-config (BETA) Get the Cloud Deploy config for the provided region and project. diff --git a/gcloud/beta/functions/deploy b/gcloud/beta/functions/deploy index d24834166..d1edce294 100644 --- a/gcloud/beta/functions/deploy +++ b/gcloud/beta/functions/deploy @@ -8,6 +8,7 @@ SYNOPSIS [--entry-point=ENTRY_POINT] [--gen2] [--ignore-file=IGNORE_FILE] [--ingress-settings=INGRESS_SETTINGS] [--retry] [--run-service-account=RUN_SERVICE_ACCOUNT] [--runtime=RUNTIME] + [--runtime-update-policy=RUNTIME_UPDATE_POLICY] [--security-level=SECURITY_LEVEL; default="secure-always"] [--serve-all-traffic-latest-revision] [--service-account=SERVICE_ACCOUNT] [--source=SOURCE] @@ -164,6 +165,10 @@ FLAGS For a list of available runtimes, run gcloud functions runtimes list. + --runtime-update-policy=RUNTIME_UPDATE_POLICY + Runtime update policy for the 1st Gen function being deployed. The + option on-deploy is used by default. + --security-level=SECURITY_LEVEL; default="secure-always" Security level controls whether a function's URL supports HTTPS only or both HTTP and HTTPS. By default, secure-always will be used, meaning diff --git a/gcloud/beta/services/api-keys/undelete b/gcloud/beta/services/api-keys/undelete index 235f42c9d..926cdb18b 100644 --- a/gcloud/beta/services/api-keys/undelete +++ b/gcloud/beta/services/api-keys/undelete @@ -77,8 +77,10 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud services api-keys undelete $ gcloud alpha services api-keys undelete diff --git a/gcloud/certificate-manager/trust-configs/help b/gcloud/certificate-manager/trust-configs/help index 1c71cb1fb..a90337847 100644 --- a/gcloud/certificate-manager/trust-configs/help +++ b/gcloud/certificate-manager/trust-configs/help @@ -34,6 +34,9 @@ COMMANDS list List all TrustConfigs in a project. + update + Update TrustConfig. + NOTES These variants are also available: diff --git a/gcloud/certificate-manager/trust-configs/update b/gcloud/certificate-manager/trust-configs/update new file mode 100644 index 000000000..3efddabae --- /dev/null +++ b/gcloud/certificate-manager/trust-configs/update @@ -0,0 +1,128 @@ +NAME + gcloud certificate-manager trust-configs update - update TrustConfig + +SYNOPSIS + gcloud certificate-manager trust-configs update + (TRUST_CONFIG : --location=LOCATION) [--async] + [--description=DESCRIPTION] + [--trust-store=[intermediate-cas=INTERMEDIATE-CAS], + [trust-anchors=TRUST-ANCHORS]] [--update-labels=[KEY=VALUE,...]] + [--clear-labels | --remove-labels=[KEY,...]] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Update a TrustConfig. + +EXAMPLES + To update a TrustConfig, run: + + $ gcloud certificate-manager trust-configs update my-trust-config \ + --description="updated description" \ + --trust-store=trust-anchors=ta.pem,\ + intermediate-cas="ica1.pem;ica2.pem" \ + --update-labels=my-key1=my-updated-value1 \ + --remove-labels=my-key2 + +POSITIONAL ARGUMENTS + TrustConfig resource - Name of the TrustConfig to update. The arguments in + this group can be used to specify the attributes of this resource. (NOTE) + Some attributes are not given arguments in this group but can be set in + other ways. + + To set the project attribute: + ◆ provide the argument trust_config on the command line with a fully + specified name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + This must be specified. + + TRUST_CONFIG + ID of the trustConfig or fully qualified identifier for the + trustConfig. + + To set the trust_config attribute: + ▸ provide the argument trust_config on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + Certificate Manager location. + + To set the location attribute: + ▸ provide the argument trust_config on the command line with a + fully specified name; + ▸ provide the argument --location on the command line; + ▸ default value of location is [global]. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --description=DESCRIPTION + Human-readable description of the resource. + + --trust-store=[intermediate-cas=INTERMEDIATE-CAS],[trust-anchors=TRUST-ANCHORS] + Trust Store with the given trust anchor and intermediate CA PEM-encoded + certificates. Certificates should be provided in files. For multiple + file names, separate them by a semicolon (';') and quote them ('"'). + One file can contain multiple certificates. Intermediate CAs are + optional. + + Examples: + + Single files: --trust-store trust-anchors=ta.pem,intermediate-cas=ica.pem + + No intermediate CAs: --trust-store trust-anchors=ta.pem + + Multiple files: --trust-store trust-anchors="ta1.pem;ta2.pem",intermediate-cas="ica1.pem;ica2.pem" + + --update-labels=[KEY=VALUE,...] + List of label KEY=VALUE pairs to update. If a label exists, its value + is modified. Otherwise, a new label is created. + + Keys must start with a lowercase character and contain only hyphens + (-), underscores (_), lowercase characters, and numbers. Values must + contain only hyphens (-), underscores (_), lowercase characters, and + numbers. + + At most one of these can be specified: + + --clear-labels + Remove all labels. If --update-labels is also specified then + --clear-labels is applied first. + + For example, to remove all labels: + + $ gcloud certificate-manager trust-configs update --clear-labels + + To remove all existing labels and create two new labels, foo and baz: + + $ gcloud certificate-manager trust-configs update --clear-labels \ + --update-labels foo=bar,baz=qux + + --remove-labels=[KEY,...] + List of label keys to remove. If a label does not exist it is + silently ignored. If --update-labels is also specified then + --update-labels is applied first. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the certificatemanager/v1 API. The full documentation for + this API can be found at: https://cloud.google.com/certificate-manager + +NOTES + These variants are also available: + + $ gcloud alpha certificate-manager trust-configs update + + $ gcloud beta certificate-manager trust-configs update + diff --git a/gcloud/components/help b/gcloud/components/help index d6659b6e1..5a89f5501 100644 --- a/gcloud/components/help +++ b/gcloud/components/help @@ -67,7 +67,8 @@ COMMANDS Remove one or more installed components. restore - Restore the Google Cloud CLI installation to its previous state. + (DEPRECATED) Restore the Google Cloud CLI installation to its previous + state. update Update all of your installed components to the latest version. diff --git a/gcloud/components/restore b/gcloud/components/restore index 2c17fa088..7e40dc788 100644 --- a/gcloud/components/restore +++ b/gcloud/components/restore @@ -6,6 +6,14 @@ SYNOPSIS gcloud components restore [GCLOUD_WIDE_FLAG ...] DESCRIPTION + (DEPRECATED) Restore the Google Cloud CLI installation to its previous + state. + + This command is deprecated and will be modified in gcloud v468.0.0. To + restore your installation to a previous version, run "gcloud components + update --version=" or install the previous version + directly from https://cloud.google.com/sdk/docs/install. + This is an undo operation, which restores the Google Cloud CLI installation on the local workstation to the state it was in just before the most recent gcloud components update, gcloud components remove, or gcloud components diff --git a/gcloud/compute/forwarding-rules/create b/gcloud/compute/forwarding-rules/create index 9285c5d52..00d55b675 100644 --- a/gcloud/compute/forwarding-rules/create +++ b/gcloud/compute/forwarding-rules/create @@ -114,12 +114,14 @@ REQUIRED FLAGS Target gRPC proxy that receives the traffic. --target-http-proxy=TARGET_HTTP_PROXY - Target HTTP proxy that receives the traffic. Acceptable values for - --ports flag are: 80, 8080. + Target HTTP proxy that receives the traffic. For the acceptable + ports, see Port specifications + (https://cloud.google.com/load-balancing/docs/forwarding-rule-concepts#port_specifications). --target-https-proxy=TARGET_HTTPS_PROXY - Target HTTPS proxy that receives the traffic. Acceptable values for - --ports flag are: 443. + Target HTTPS proxy that receives the traffic. For the acceptable + ports, see Port specifications + (https://cloud.google.com/load-balancing/docs/forwarding-rule-concepts#port_specifications). --target-instance=TARGET_INSTANCE Name of the target instance that receives the traffic. The target diff --git a/gcloud/compute/forwarding-rules/set-target b/gcloud/compute/forwarding-rules/set-target index c7134eeec..51d68d2b7 100644 --- a/gcloud/compute/forwarding-rules/set-target +++ b/gcloud/compute/forwarding-rules/set-target @@ -79,12 +79,14 @@ REQUIRED FLAGS Target gRPC proxy that receives the traffic. --target-http-proxy=TARGET_HTTP_PROXY - Target HTTP proxy that receives the traffic. Acceptable values for - --ports flag are: 80, 8080. + Target HTTP proxy that receives the traffic. For the acceptable + ports, see Port specifications + (https://cloud.google.com/load-balancing/docs/forwarding-rule-concepts#port_specifications). --target-https-proxy=TARGET_HTTPS_PROXY - Target HTTPS proxy that receives the traffic. Acceptable values for - --ports flag are: 443. + Target HTTPS proxy that receives the traffic. For the acceptable + ports, see Port specifications + (https://cloud.google.com/load-balancing/docs/forwarding-rule-concepts#port_specifications). --target-instance=TARGET_INSTANCE Name of the target instance that receives the traffic. The target diff --git a/gcloud/compute/instances/create b/gcloud/compute/instances/create index 71fa007df..c47f3779a 100644 --- a/gcloud/compute/instances/create +++ b/gcloud/compute/instances/create @@ -794,7 +794,7 @@ FLAGS --source-instance-template=SOURCE_INSTANCE_TEMPLATE The name of the instance template that the instance will be created - from. + from. An instance template can be a global/regional resource. Users can also override machine type and labels. Values of other flags will be ignored and --source-instance-template will be used instead. diff --git a/gcloud/compute/instances/create-with-container b/gcloud/compute/instances/create-with-container index 1b2a042f5..5935f294a 100644 --- a/gcloud/compute/instances/create-with-container +++ b/gcloud/compute/instances/create-with-container @@ -670,7 +670,7 @@ FLAGS --source-instance-template=SOURCE_INSTANCE_TEMPLATE The name of the instance template that the instance will be created - from. + from. An instance template can be a global/regional resource. Users can also override machine type and labels. Values of other flags will be ignored and --source-instance-template will be used instead. diff --git a/gcloud/compute/instances/help b/gcloud/compute/instances/help index 1a4a4452c..0cfe11561 100644 --- a/gcloud/compute/instances/help +++ b/gcloud/compute/instances/help @@ -140,6 +140,9 @@ COMMANDS set-machine-type Set machine type for Compute Engine virtual machines. + set-name + Set the name of a Compute Engine virtual machine. + set-scheduling Set scheduling options for Compute Engine virtual machines. diff --git a/gcloud/compute/instances/set-name b/gcloud/compute/instances/set-name new file mode 100644 index 000000000..b6676b548 --- /dev/null +++ b/gcloud/compute/instances/set-name @@ -0,0 +1,67 @@ +NAME + gcloud compute instances set-name - set the name of a Compute Engine + virtual machine + +SYNOPSIS + gcloud compute instances set-name INSTANCE_NAME --new-name=NEW_NAME + [--zone=ZONE] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + gcloud compute instances set-name lets you change the name of a virtual + machine. + +EXAMPLES + To change the name of instance-1 to instance-2: + + $ gcloud compute instances set-name instance-1 --new-name=instance-2 + +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 + --new-name=NEW_NAME + Specifies the new name of the instance. + +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 set-name + + $ gcloud beta compute instances set-name + diff --git a/gcloud/compute/public-advertised-prefixes/create b/gcloud/compute/public-advertised-prefixes/create index da1ccbbe0..994ae8a54 100644 --- a/gcloud/compute/public-advertised-prefixes/create +++ b/gcloud/compute/public-advertised-prefixes/create @@ -20,11 +20,11 @@ POSITIONAL ARGUMENTS REQUIRED FLAGS --dns-verification-ip=DNS_VERIFICATION_IP - IPv4 address to use for verification. It must be within the IPv4 range + IP address to use for verification. It must be within the IP range specified in --range. --range=RANGE - IPv4 range allocated to this public advertised prefix, in CIDR format. + IP range allocated to this public advertised prefix, in CIDR format. OPTIONAL FLAGS --description=DESCRIPTION diff --git a/gcloud/compute/public-delegated-prefixes/create b/gcloud/compute/public-delegated-prefixes/create index cf0311107..1a62ad6fd 100644 --- a/gcloud/compute/public-delegated-prefixes/create +++ b/gcloud/compute/public-delegated-prefixes/create @@ -22,8 +22,8 @@ POSITIONAL ARGUMENTS REQUIRED FLAGS --range=RANGE - IPv4 range from this public delegated prefix that should be delegated, - in CIDR format. It must be smaller than parent public advertised prefix + IP range from this public delegated prefix that should be delegated, in + CIDR format. It must be smaller than parent public advertised prefix range. Exactly one of these must be specified: diff --git a/gcloud/compute/security-policies/rules/create b/gcloud/compute/security-policies/rules/create index 0ef08eddd..56856259f 100644 --- a/gcloud/compute/security-policies/rules/create +++ b/gcloud/compute/security-policies/rules/create @@ -19,14 +19,16 @@ SYNOPSIS [--conform-action=CONFORM_ACTION] [--description=DESCRIPTION] [--enforce-on-key=ENFORCE_ON_KEY] [--enforce-on-key-configs=[[all],[ip],[xff-ip], - [http-cookie=HTTP_COOKIE], - [http-header=HTTP_HEADER],[http-path],[sni],[region-code]],[...]] + [http-cookie=HTTP_COOKIE],[http-header=HTTP_HEADER],[http-path], + [sni],[region-code],[tls-ja3-fingerprint],[user-ip]],[...]] [--enforce-on-key-name=ENFORCE_ON_KEY_NAME] [--exceed-action=EXCEED_ACTION] [--exceed-redirect-target=EXCEED_REDIRECT_TARGET] [--exceed-redirect-type=EXCEED_REDIRECT_TYPE] [--preview] [--rate-limit-threshold-count=RATE_LIMIT_THRESHOLD_COUNT] [--rate-limit-threshold-interval-sec=RATE_LIMIT_THRESHOLD_INTERVAL_SEC] + [--recaptcha-action-site-keys=[SITE_KEY,...]] + [--recaptcha-session-site-keys=[SITE_KEY,...]] [--redirect-target=REDIRECT_TARGET] [--redirect-type=REDIRECT_TYPE] [--region=REGION] [--request-headers-to-add=[REQUEST_HEADERS_TO_ADD,...]] @@ -175,11 +177,16 @@ OPTIONAL FLAGS the TLS session of the HTTPS request ◆ region-code: key type takes the value of the region code from which the request originates + ◆ tls-ja3-fingerprint: key type takes the value of JA3 TLS/SSL + fingerprint if the client connects using HTTPS, HTTP/2 or HTTP/3 + ◆ user-ip: key type takes the IP address of the originating client, + which is resolved based on user-ip-request-headers configured with + the security policy ENFORCE_ON_KEY must be one of: ip, all, http-header, xff-ip, - http-cookie, http-path, sni, region-code. + http-cookie, http-path, sni, region-code, tls-ja3-fingerprint, user-ip. - --enforce-on-key-configs=[[all],[ip],[xff-ip],[http-cookie=HTTP_COOKIE],[http-header=HTTP_HEADER],[http-path],[sni],[region-code]],[...] + --enforce-on-key-configs=[[all],[ip],[xff-ip],[http-cookie=HTTP_COOKIE],[http-header=HTTP_HEADER],[http-path],[sni],[region-code],[tls-ja3-fingerprint],[user-ip]],[...] Specify up to 3 key type/name pairs to rate limit. Valid key types are: ◆ ip: each client IP address has this limit enforced separately @@ -195,6 +202,11 @@ OPTIONAL FLAGS the TLS session of the HTTPS request ◆ region-code: key type takes the value of the region code from which the request originates + ◆ tls-ja3-fingerprint: key type takes the value of JA3 TLS/SSL + fingerprint if the client connects using HTTPS, HTTP/2 or HTTP/3 + ◆ user-ip: key type takes the IP address of the originating client, + which is resolved based on user-ip-request-headers configured with + the security policy Key names are only applicable to the following key types: ◆ http-header: The name of the HTTP header whose value is taken as @@ -237,6 +249,18 @@ OPTIONAL FLAGS Interval over which the threshold for rate limiting requests is computed. + --recaptcha-action-site-keys=[SITE_KEY,...] + A comma-separated list of site keys to be used during the validation of + reCAPTCHA action-tokens. The provided site keys need to be created from + the reCAPTCHA API under the same project where the security policy is + created. + + --recaptcha-session-site-keys=[SITE_KEY,...] + A comma-separated list of site keys to be used during the validation of + reCAPTCHA session-tokens. The provided site keys need to be created + from the reCAPTCHA API under the same project where the security policy + is created. + --redirect-target=REDIRECT_TARGET URL target for the redirect action. Must be specified if the redirect type is external-302. Cannot be specified if the redirect type is diff --git a/gcloud/compute/security-policies/rules/update b/gcloud/compute/security-policies/rules/update index 255c8b762..521493bc3 100644 --- a/gcloud/compute/security-policies/rules/update +++ b/gcloud/compute/security-policies/rules/update @@ -10,14 +10,16 @@ SYNOPSIS [--conform-action=CONFORM_ACTION] [--description=DESCRIPTION] [--enforce-on-key=ENFORCE_ON_KEY] [--enforce-on-key-configs=[[all],[ip],[xff-ip], - [http-cookie=HTTP_COOKIE], - [http-header=HTTP_HEADER],[http-path],[sni],[region-code]],[...]] + [http-cookie=HTTP_COOKIE],[http-header=HTTP_HEADER],[http-path], + [sni],[region-code],[tls-ja3-fingerprint],[user-ip]],[...]] [--enforce-on-key-name=ENFORCE_ON_KEY_NAME] [--exceed-action=EXCEED_ACTION] [--exceed-redirect-target=EXCEED_REDIRECT_TARGET] [--exceed-redirect-type=EXCEED_REDIRECT_TYPE] [--preview] [--rate-limit-threshold-count=RATE_LIMIT_THRESHOLD_COUNT] [--rate-limit-threshold-interval-sec=RATE_LIMIT_THRESHOLD_INTERVAL_SEC] + [--recaptcha-action-site-keys=[SITE_KEY,...]] + [--recaptcha-session-site-keys=[SITE_KEY,...]] [--redirect-target=REDIRECT_TARGET] [--redirect-type=REDIRECT_TYPE] [--region=REGION] [--request-headers-to-add=[REQUEST_HEADERS_TO_ADD,...]] @@ -126,11 +128,16 @@ FLAGS the TLS session of the HTTPS request ◆ region-code: key type takes the value of the region code from which the request originates + ◆ tls-ja3-fingerprint: key type takes the value of JA3 TLS/SSL + fingerprint if the client connects using HTTPS, HTTP/2 or HTTP/3 + ◆ user-ip: key type takes the IP address of the originating client, + which is resolved based on user-ip-request-headers configured with + the security policy ENFORCE_ON_KEY must be one of: ip, all, http-header, xff-ip, - http-cookie, http-path, sni, region-code. + http-cookie, http-path, sni, region-code, tls-ja3-fingerprint, user-ip. - --enforce-on-key-configs=[[all],[ip],[xff-ip],[http-cookie=HTTP_COOKIE],[http-header=HTTP_HEADER],[http-path],[sni],[region-code]],[...] + --enforce-on-key-configs=[[all],[ip],[xff-ip],[http-cookie=HTTP_COOKIE],[http-header=HTTP_HEADER],[http-path],[sni],[region-code],[tls-ja3-fingerprint],[user-ip]],[...] Specify up to 3 key type/name pairs to rate limit. Valid key types are: ◆ ip: each client IP address has this limit enforced separately @@ -146,6 +153,11 @@ FLAGS the TLS session of the HTTPS request ◆ region-code: key type takes the value of the region code from which the request originates + ◆ tls-ja3-fingerprint: key type takes the value of JA3 TLS/SSL + fingerprint if the client connects using HTTPS, HTTP/2 or HTTP/3 + ◆ user-ip: key type takes the IP address of the originating client, + which is resolved based on user-ip-request-headers configured with + the security policy Key names are only applicable to the following key types: ◆ http-header: The name of the HTTP header whose value is taken as @@ -188,6 +200,18 @@ FLAGS Interval over which the threshold for rate limiting requests is computed. + --recaptcha-action-site-keys=[SITE_KEY,...] + A comma-separated list of site keys to be used during the validation of + reCAPTCHA action-tokens. The provided site keys need to be created from + the reCAPTCHA API under the same project where the security policy is + created. + + --recaptcha-session-site-keys=[SITE_KEY,...] + A comma-separated list of site keys to be used during the validation of + reCAPTCHA session-tokens. The provided site keys need to be created + from the reCAPTCHA API under the same project where the security policy + is created. + --redirect-target=REDIRECT_TARGET URL target for the redirect action. Must be specified if the redirect type is external-302. Cannot be specified if the redirect type is diff --git a/gcloud/config/get b/gcloud/config/get index b0bb3eb36..69e672027 100644 --- a/gcloud/config/get +++ b/gcloud/config/get @@ -298,6 +298,10 @@ AVAILABLE PROPERTIES Private Service Connect usage, see https://cloud.google.com/vpc/docs/configure-private-service-connect-apis#using-endpoints + config + Overrides API endpoint for gcloud infra-manager command group. + Defaults to https://config.googleapis.com/ + container Overrides API endpoint for gcloud container command group. Defaults to https://container.googleapis.com/ @@ -406,9 +410,6 @@ AVAILABLE PROPERTIES Overrides API endpoint for gcloud ids command group. Defaults to https://ids.googleapis.com/ - inframanager - Overrides API endpoint for gcloud infra-manager command group. - krmapihosting Overrides API endpoint for gcloud anthos config controller command group. Defaults to https://krmapihosting.googleapis.com/ @@ -572,6 +573,10 @@ AVAILABLE PROPERTIES Overrides API endpoint for gcloud ml vision command group. Defaults to https://vision.googleapis.com/ + vmmigration + Overrides API endpoint for gcloud migration vms command group. + Defaults to https://vmmigration.googleapis.com/ + vmwareengine Overrides API endpoint for gcloud vmware command group. Defaults to https://vmwareengine.googleapis.com/ diff --git a/gcloud/config/help b/gcloud/config/help index 6ffc195b1..3ce4453ab 100644 --- a/gcloud/config/help +++ b/gcloud/config/help @@ -330,6 +330,10 @@ AVAILABLE PROPERTIES Private Service Connect usage, see https://cloud.google.com/vpc/docs/configure-private-service-connect-apis#using-endpoints + config + Overrides API endpoint for gcloud infra-manager command group. + Defaults to https://config.googleapis.com/ + container Overrides API endpoint for gcloud container command group. Defaults to https://container.googleapis.com/ @@ -438,9 +442,6 @@ AVAILABLE PROPERTIES Overrides API endpoint for gcloud ids command group. Defaults to https://ids.googleapis.com/ - inframanager - Overrides API endpoint for gcloud infra-manager command group. - krmapihosting Overrides API endpoint for gcloud anthos config controller command group. Defaults to https://krmapihosting.googleapis.com/ @@ -604,6 +605,10 @@ AVAILABLE PROPERTIES Overrides API endpoint for gcloud ml vision command group. Defaults to https://vision.googleapis.com/ + vmmigration + Overrides API endpoint for gcloud migration vms command group. + Defaults to https://vmmigration.googleapis.com/ + vmwareengine Overrides API endpoint for gcloud vmware command group. Defaults to https://vmwareengine.googleapis.com/ diff --git a/gcloud/config/list b/gcloud/config/list index 1ac4e5327..1c12a1d65 100644 --- a/gcloud/config/list +++ b/gcloud/config/list @@ -342,6 +342,10 @@ AVAILABLE PROPERTIES Private Service Connect usage, see https://cloud.google.com/vpc/docs/configure-private-service-connect-apis#using-endpoints + config + Overrides API endpoint for gcloud infra-manager command group. + Defaults to https://config.googleapis.com/ + container Overrides API endpoint for gcloud container command group. Defaults to https://container.googleapis.com/ @@ -450,9 +454,6 @@ AVAILABLE PROPERTIES Overrides API endpoint for gcloud ids command group. Defaults to https://ids.googleapis.com/ - inframanager - Overrides API endpoint for gcloud infra-manager command group. - krmapihosting Overrides API endpoint for gcloud anthos config controller command group. Defaults to https://krmapihosting.googleapis.com/ @@ -616,6 +617,10 @@ AVAILABLE PROPERTIES Overrides API endpoint for gcloud ml vision command group. Defaults to https://vision.googleapis.com/ + vmmigration + Overrides API endpoint for gcloud migration vms command group. + Defaults to https://vmmigration.googleapis.com/ + vmwareengine Overrides API endpoint for gcloud vmware command group. Defaults to https://vmwareengine.googleapis.com/ diff --git a/gcloud/config/set b/gcloud/config/set index ae8522395..18c786e44 100644 --- a/gcloud/config/set +++ b/gcloud/config/set @@ -345,6 +345,10 @@ AVAILABLE PROPERTIES Private Service Connect usage, see https://cloud.google.com/vpc/docs/configure-private-service-connect-apis#using-endpoints + config + Overrides API endpoint for gcloud infra-manager command group. + Defaults to https://config.googleapis.com/ + container Overrides API endpoint for gcloud container command group. Defaults to https://container.googleapis.com/ @@ -453,9 +457,6 @@ AVAILABLE PROPERTIES Overrides API endpoint for gcloud ids command group. Defaults to https://ids.googleapis.com/ - inframanager - Overrides API endpoint for gcloud infra-manager command group. - krmapihosting Overrides API endpoint for gcloud anthos config controller command group. Defaults to https://krmapihosting.googleapis.com/ @@ -619,6 +620,10 @@ AVAILABLE PROPERTIES Overrides API endpoint for gcloud ml vision command group. Defaults to https://vision.googleapis.com/ + vmmigration + Overrides API endpoint for gcloud migration vms command group. + Defaults to https://vmmigration.googleapis.com/ + vmwareengine Overrides API endpoint for gcloud vmware command group. Defaults to https://vmwareengine.googleapis.com/ diff --git a/gcloud/config/unset b/gcloud/config/unset index 9cacaf9e6..0e8cce367 100644 --- a/gcloud/config/unset +++ b/gcloud/config/unset @@ -306,6 +306,10 @@ AVAILABLE PROPERTIES Private Service Connect usage, see https://cloud.google.com/vpc/docs/configure-private-service-connect-apis#using-endpoints + config + Overrides API endpoint for gcloud infra-manager command group. + Defaults to https://config.googleapis.com/ + container Overrides API endpoint for gcloud container command group. Defaults to https://container.googleapis.com/ @@ -414,9 +418,6 @@ AVAILABLE PROPERTIES Overrides API endpoint for gcloud ids command group. Defaults to https://ids.googleapis.com/ - inframanager - Overrides API endpoint for gcloud infra-manager command group. - krmapihosting Overrides API endpoint for gcloud anthos config controller command group. Defaults to https://krmapihosting.googleapis.com/ @@ -580,6 +581,10 @@ AVAILABLE PROPERTIES Overrides API endpoint for gcloud ml vision command group. Defaults to https://vision.googleapis.com/ + vmmigration + Overrides API endpoint for gcloud migration vms command group. + Defaults to https://vmmigration.googleapis.com/ + vmwareengine Overrides API endpoint for gcloud vmware command group. Defaults to https://vmwareengine.googleapis.com/ diff --git a/gcloud/container/aws/node-pools/help b/gcloud/container/aws/node-pools/help index 773f78a62..46f86ead1 100644 --- a/gcloud/container/aws/node-pools/help +++ b/gcloud/container/aws/node-pools/help @@ -28,6 +28,9 @@ COMMANDS list List node pools in an Anthos cluster on AWS. + rollback + Rollback a node pool in an Anthos cluster on AWS. + update Update a node pool in an Anthos cluster on AWS. diff --git a/gcloud/container/aws/node-pools/rollback b/gcloud/container/aws/node-pools/rollback new file mode 100644 index 000000000..ed90d241e --- /dev/null +++ b/gcloud/container/aws/node-pools/rollback @@ -0,0 +1,81 @@ +NAME + gcloud container aws node-pools rollback - rollback a node pool in an + Anthos cluster on AWS + +SYNOPSIS + gcloud container aws node-pools rollback + (NODE_POOL : --cluster=CLUSTER --location=LOCATION) [--async] + [--respect-pdb] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Rollback a node pool in an Anthos cluster on AWS. + +EXAMPLES + To roll back a canceled or failed update in node pool named my-node-pool in + a cluster named my-cluster managed in location us-west1, run: + + $ gcloud container aws node-pools rollback my-node-pool \ + --cluster=my-cluster --location=us-west1 + +POSITIONAL ARGUMENTS + Node pool resource - node pool to rollback. 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 node_pool 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. + + NODE_POOL + ID of the node_pool or fully qualified identifier for the node_pool. + + To set the node_pool attribute: + ▸ provide the argument node_pool on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --cluster=CLUSTER + cluster of the node_pool. + + To set the cluster attribute: + ▸ provide the argument node_pool on the command line with a fully + specified name; + ▸ provide the argument --cluster on the command line. + + --location=LOCATION + Google Cloud location for the node_pool. + + To set the location attribute: + ▸ provide the argument node_pool on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ set the property container_aws/location. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --respect-pdb + Indicates whether the node pool rollback should respect pod disruption + budget. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This variant is also available: + + $ gcloud alpha container aws node-pools rollback + diff --git a/gcloud/container/clusters/create b/gcloud/container/clusters/create index 667c61ea8..4668298bf 100644 --- a/gcloud/container/clusters/create +++ b/gcloud/container/clusters/create @@ -10,6 +10,7 @@ SYNOPSIS max-shared-clients-per-gpu=MAX_SHARED_CLIENTS_PER_GPU],...]] [--additional-zones=ZONE,[ZONE,...]] [--addons=[ADDON,...]] [--async] [--autoprovisioning-network-tags=TAGS,[TAGS,...]] + [--autoprovisioning-resource-manager-tags=[KEY=VALUE,...]] [--autoscaling-profile=AUTOSCALING_PROFILE] [--boot-disk-kms-key=BOOT_DISK_KMS_KEY] [--cloud-run-config=[load-balancer-type=EXTERNAL,...]] @@ -55,9 +56,9 @@ SYNOPSIS [--placement-policy=PLACEMENT_POLICY] [--placement-type=PLACEMENT_TYPE] [--preemptible] [--private-endpoint-subnetwork=NAME] [--private-ipv6-google-access-type=PRIVATE_IPV6_GOOGLE_ACCESS_TYPE] - [--release-channel=CHANNEL] [--security-group=SECURITY_GROUP] - [--security-posture=SECURITY_POSTURE] [--services-ipv4-cidr=CIDR] - [--services-secondary-range-name=NAME] + [--release-channel=CHANNEL] [--resource-manager-tags=[KEY=VALUE,...]] + [--security-group=SECURITY_GROUP] [--security-posture=SECURITY_POSTURE] + [--services-ipv4-cidr=CIDR] [--services-secondary-range-name=NAME] [--shielded-integrity-monitoring] [--shielded-secure-boot] [--spot] [--stack-type=STACK_TYPE] [--subnetwork=SUBNETWORK] [--system-config-from-file=SYSTEM_CONFIG_FROM_FILE] @@ -225,6 +226,31 @@ FLAGS https://cloud.google.com/sdk/gcloud/reference/compute/firewall-rules/create for examples. + --autoprovisioning-resource-manager-tags=[KEY=VALUE,...] + Applies the specified comma-separated resource manager tags that has + the GCE_FIREWALL purpose to all nodes in the new Autopilot cluster or + all auto-provisioned nodes in the new Standard cluster. + + Examples: + + $ gcloud container clusters create example-cluster \ + --autoprovisioning-resource-manager-tags=tagKeys/\ + 1234=tagValues/2345 + $ gcloud container clusters create example-cluster \ + --autoprovisioning-resource-manager-tags=my-project/key1=value1 + $ gcloud container clusters create example-cluster \ + --autoprovisioning-resource-manager-tags=12345/key1=value1,\ + 23456/key2=value2 + $ gcloud container clusters create example-cluster \ + --autoprovisioning-resource-manager-tags= + + All nodes in an Autopilot cluster or all auto-provisioned nodes in a + Standard cluster, including nodes that are resized or re-created, will + have the specified tags on the corresponding Instance object in the + Compute Engine API. You can reference these tags in network firewall + policy rules. For instructions, see + https://cloud.google.com/firewall/docs/use-tags-for-firewalls. + --autoscaling-profile=AUTOSCALING_PROFILE Set autoscaling behaviour, choices are 'optimize-utilization' and 'balanced'. Default is 'balanced'. @@ -954,6 +980,28 @@ FLAGS Clusters subscribed to 'stable' receive versions that are known to be stable and reliable in production. + --resource-manager-tags=[KEY=VALUE,...] + Applies the specified comma-separated resource manager tags that has + the GCE_FIREWALL purpose to all nodes in the new default node pool(s) + of a new cluster. + + Examples: + + $ gcloud container clusters create example-cluster \ + --resource-manager-tags=tagKeys/1234=tagValues/2345 + $ gcloud container clusters create example-cluster \ + --resource-manager-tags=my-project/key1=value1 + $ gcloud container clusters create example-cluster \ + --resource-manager-tags=12345/key1=value1,23456/key2=value2 + $ gcloud container clusters create example-cluster \ + --resource-manager-tags= + + All nodes, including nodes that are resized or re-created, will have + the specified tags on the corresponding Instance object in the Compute + Engine API. You can reference these tags in network firewall policy + rules. For instructions, see + https://cloud.google.com/firewall/docs/use-tags-for-firewalls. + --security-group=SECURITY_GROUP The name of the RBAC security group for use with Google security groups in Kubernetes RBAC diff --git a/gcloud/container/clusters/create-auto b/gcloud/container/clusters/create-auto index c68bf52fa..90826698b 100644 --- a/gcloud/container/clusters/create-auto +++ b/gcloud/container/clusters/create-auto @@ -5,6 +5,7 @@ NAME SYNOPSIS gcloud container clusters create-auto NAME [--async] [--autoprovisioning-network-tags=TAGS,[TAGS,...]] + [--autoprovisioning-resource-manager-tags=[KEY=VALUE,...]] [--binauthz-evaluation-mode=BINAUTHZ_EVALUATION_MODE] [--boot-disk-kms-key=BOOT_DISK_KMS_KEY] [--cluster-ipv4-cidr=CLUSTER_IPV4_CIDR] @@ -72,6 +73,31 @@ FLAGS https://cloud.google.com/sdk/gcloud/reference/compute/firewall-rules/create for examples. + --autoprovisioning-resource-manager-tags=[KEY=VALUE,...] + Applies the specified comma-separated resource manager tags that has + the GCE_FIREWALL purpose to all nodes in the new Autopilot cluster or + all auto-provisioned nodes in the new Standard cluster. + + Examples: + + $ gcloud container clusters create-auto example-cluster \ + --autoprovisioning-resource-manager-tags=tagKeys/\ + 1234=tagValues/2345 + $ gcloud container clusters create-auto example-cluster \ + --autoprovisioning-resource-manager-tags=my-project/key1=value1 + $ gcloud container clusters create-auto example-cluster \ + --autoprovisioning-resource-manager-tags=12345/key1=value1,\ + 23456/key2=value2 + $ gcloud container clusters create-auto example-cluster \ + --autoprovisioning-resource-manager-tags= + + All nodes in an Autopilot cluster or all auto-provisioned nodes in a + Standard cluster, including nodes that are resized or re-created, will + have the specified tags on the corresponding Instance object in the + Compute Engine API. You can reference these tags in network firewall + policy rules. For instructions, see + https://cloud.google.com/firewall/docs/use-tags-for-firewalls. + Flags for Binary Authorization: --binauthz-evaluation-mode=BINAUTHZ_EVALUATION_MODE diff --git a/gcloud/container/clusters/update b/gcloud/container/clusters/update index b212ec63e..a0211f302 100644 --- a/gcloud/container/clusters/update +++ b/gcloud/container/clusters/update @@ -5,6 +5,7 @@ NAME SYNOPSIS gcloud container clusters update NAME (--autoprovisioning-network-tags=[TAGS,...] + | --autoprovisioning-resource-manager-tags=[KEY=VALUE,...] | --autoscaling-profile=AUTOSCALING_PROFILE | --clear-fleet-project | --complete-credential-rotation | --complete-ip-rotation | --database-encryption-key=DATABASE_ENCRYPTION_KEY @@ -123,6 +124,39 @@ REQUIRED FLAGS https://cloud.google.com/sdk/gcloud/reference/compute/firewall-rules/create for examples. + --autoprovisioning-resource-manager-tags=[KEY=VALUE,...] + For an Autopilot cluster, the specified comma-separated resource + manager tags that has the GCP_FIREWALL purpose replace the existing + tags on all nodes in the cluster. + + For a Standard cluster, the specified comma-separated resource + manager tags that has the GCE_FIREWALL purpose are applied to all + nodes in the new newly created auto-provisioned node pools. Existing + auto-provisioned node pools retain the tags that they had before the + update. To update tags on an existing auto-provisioned node pool, use + the node pool level flag '--resource-manager-tags'. + + Examples: + + $ gcloud container clusters update example-cluster \ + --autoprovisioning-resource-manager-tags=tagKeys/\ + 1234=tagValues/2345 + $ gcloud container clusters update example-cluster \ + --autoprovisioning-resource-manager-tags=my-project/key1=value1 + $ gcloud container clusters update example-cluster \ + --autoprovisioning-resource-manager-tags=12345/key1=value1,\ + 23456/key2=value2 + $ gcloud container clusters update example-cluster \ + --autoprovisioning-resource-manager-tags= + + All nodes in an Autopilot cluster or all newly created + auto-provisioned nodes in a Standard cluster, including nodes that + are resized or re-created, will have the specified tags on the + corresponding Instance object in the Compute Engine API. You can + reference these tags in network firewall policy rules. For + instructions, see + https://cloud.google.com/firewall/docs/use-tags-for-firewalls. + --autoscaling-profile=AUTOSCALING_PROFILE Set autoscaling behaviour, choices are 'optimize-utilization' and 'balanced'. Default is 'balanced'. diff --git a/gcloud/container/fleet/clusterupgrade/create b/gcloud/container/fleet/clusterupgrade/create new file mode 100644 index 000000000..ae1654b07 --- /dev/null +++ b/gcloud/container/fleet/clusterupgrade/create @@ -0,0 +1,93 @@ +NAME + gcloud container fleet clusterupgrade create - create the clusterupgrade + feature for a fleet within a given project + +SYNOPSIS + gcloud container fleet clusterupgrade create + [--default-upgrade-soaking=DEFAULT_UPGRADE_SOAKING] + [--upstream-fleet=UPSTREAM_FLEET] + [--add-upgrade-soaking-override=ADD_UPGRADE_SOAKING_OVERRIDE + --upgrade-selector=[name=NAME],[version=VERSION]] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Create the clusterupgrade feature for a fleet within a given project. + +EXAMPLES + To create the clusterupgrade feature for the current fleet, run: + + $ gcloud container fleet clusterupgrade create \ + --default-upgrade-soaking=DEFAULT_UPGRADE_SOAKING + +FLAGS + --default-upgrade-soaking=DEFAULT_UPGRADE_SOAKING + Configures the default soaking duration for each upgrade propagating + through the current fleet to become "COMPLETE". Soaking begins after + all clusters in the fleet are on the target version, or after 30 days + if all cluster upgrades are not complete. Once an upgrade state becomes + "COMPLETE", it will automatically be propagated to the downstream + fleet. Max is 30 days. + + To configure Rollout Sequencing for a fleet, this attribute must be + set. To do this while specifying a default soaking duration of 7 days, + run: + + $ gcloud container fleet clusterupgrade create \ + --default-upgrade-soaking=7d + + --upstream-fleet=UPSTREAM_FLEET + The upstream fleet. GKE will finish upgrades on the upstream fleet + before applying the same upgrades to the current fleet. + + To configure the upstream fleet, run: + + $ gcloud container fleet clusterupgrade create \ + --upstream-fleet={upstream_fleet} + + Upgrade soaking override. + + Defines a specific soaking time override for a particular upgrade + propagating through the current fleet that supercedes the default + soaking duration configured by `--default-upgrade-soaking`. + + To set an upgrade soaking override of 12 hours for the upgrade with + name, `k8s_control_plane`, and version, `1.23.1-gke.1000`, run: + + $ gcloud container fleet clusterupgrade create \ + --add-upgrade-soaking-override=12h \ + --upgrade-selector=name="k8s_control_plane",\ + version="1.23.1-gke.1000" + + --add-upgrade-soaking-override=ADD_UPGRADE_SOAKING_OVERRIDE + Overrides the soaking time for a particular upgrade name and version + propagating through the current fleet. Set soaking to 0 days to + bypass soaking and fast-forward the upgrade to the downstream fleet. + + See $ gcloud topic datetimes for information on duration formats. + + This flag argument must be specified if any of the other arguments in + this group are specified. + + --upgrade-selector=[name=NAME],[version=VERSION] + Name and version of the upgrade to be overridden where version is a + full GKE version. Currently, name can be either k8s_control_plane or + k8s_node. + + This flag argument must be specified if any of the other arguments in + this group are specified. + +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 container fleet clusterupgrade create + + $ gcloud beta container fleet clusterupgrade create + diff --git a/gcloud/container/fleet/clusterupgrade/describe b/gcloud/container/fleet/clusterupgrade/describe new file mode 100644 index 000000000..222f20204 --- /dev/null +++ b/gcloud/container/fleet/clusterupgrade/describe @@ -0,0 +1,47 @@ +NAME + gcloud container fleet clusterupgrade describe - describe the + clusterupgrade feature for a fleet within a given project + +SYNOPSIS + gcloud container fleet clusterupgrade describe + [--show-linked-cluster-upgrade] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Describe the Fleet clusterupgrade feature used for configuring fleet-based + rollout sequencing. + +EXAMPLES + To view the cluster upgrade feature information for the current fleet, run: + + $ gcloud container fleet clusterupgrade describe + +FLAGS + --show-linked-cluster-upgrade + Shows the cluster upgrade feature information for the current fleet as + well as information for all other fleets linked in the same rollout + sequence (provided that the caller has permission to view the upstream + and downstream fleets). This displays cluster upgrade information for + fleets in the current fleet's rollout sequence in order of furthest + upstream to downstream. + + To view the cluster upgrade feature information for the rollout + sequence containing the current fleet, run: + + $ gcloud container fleet clusterupgrade describe \ + --show-linked-cluster-upgrade + +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 container fleet clusterupgrade describe + + $ gcloud beta container fleet clusterupgrade describe + diff --git a/gcloud/container/fleet/clusterupgrade/help b/gcloud/container/fleet/clusterupgrade/help new file mode 100644 index 000000000..895fdbbb1 --- /dev/null +++ b/gcloud/container/fleet/clusterupgrade/help @@ -0,0 +1,34 @@ +NAME + gcloud container fleet clusterupgrade - configure the Fleet clusterupgrade + feature + +SYNOPSIS + gcloud container fleet clusterupgrade COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + This fleet feature is used to configure fleet-based rollout sequencing. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + create + Create the clusterupgrade feature for a fleet within a given project. + + describe + Describe the clusterupgrade feature for a fleet within a given project. + + update + Update the clusterupgrade feature for a fleet within a given project. + +NOTES + These variants are also available: + + $ gcloud alpha container fleet clusterupgrade + + $ gcloud beta container fleet clusterupgrade + diff --git a/gcloud/container/fleet/clusterupgrade/update b/gcloud/container/fleet/clusterupgrade/update new file mode 100644 index 000000000..c71fadc6d --- /dev/null +++ b/gcloud/container/fleet/clusterupgrade/update @@ -0,0 +1,120 @@ +NAME + gcloud container fleet clusterupgrade update - update the clusterupgrade + feature for a fleet within a given project + +SYNOPSIS + gcloud container fleet clusterupgrade update + [--default-upgrade-soaking=DEFAULT_UPGRADE_SOAKING] + [--remove-upgrade-soaking-overrides + | --add-upgrade-soaking-override=ADD_UPGRADE_SOAKING_OVERRIDE + --upgrade-selector=[name=NAME],[version=VERSION]] + [--reset-upstream-fleet | --upstream-fleet=UPSTREAM_FLEET] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Update the clusterupgrade feature for a fleet within a given project. + +EXAMPLES + To update the clusterupgrade feature for the current fleet, run: + + $ gcloud container fleet clusterupgrade update \ + --default-upgrade-soaking=DEFAULT_UPGRADE_SOAKING + +FLAGS + --default-upgrade-soaking=DEFAULT_UPGRADE_SOAKING + Configures the default soaking duration for each upgrade propagating + through the current fleet to become "COMPLETE". Soaking begins after + all clusters in the fleet are on the target version, or after 30 days + if all cluster upgrades are not complete. Once an upgrade state becomes + "COMPLETE", it will automatically be propagated to the downstream + fleet. Max is 30 days. + + To configure Rollout Sequencing for a fleet, this attribute must be + set. To do this while specifying a default soaking duration of 7 days, + run: + + $ gcloud container fleet clusterupgrade update \ + --default-upgrade-soaking=7d + + At most one of these can be specified: + + --remove-upgrade-soaking-overrides + Removes soaking time overrides for all upgrades propagating through + the current fleet. Consequently, all upgrades will follow the soak + time configured by --default-upgrade-soaking until new overrides are + configured with --add_upgrade_soaking_override and + --upgrade_selector. + + To remove all configured soaking time overrides, run: + + $ gcloud container fleet clusterupgrade update \ + --remove-upgrade-soaking-overrides + + Upgrade soaking override. + + Defines a specific soaking time override for a particular upgrade + propagating through the current fleet that supercedes the default + soaking duration configured by `--default-upgrade-soaking`. + + To set an upgrade soaking override of 12 hours for the upgrade with + name, `k8s_control_plane`, and version, `1.23.1-gke.1000`, run: + + $ gcloud container fleet clusterupgrade update \ + --add-upgrade-soaking-override=12h \ + --upgrade-selector=name="k8s_control_plane",\ + version="1.23.1-gke.1000" + + --add-upgrade-soaking-override=ADD_UPGRADE_SOAKING_OVERRIDE + Overrides the soaking time for a particular upgrade name and + version propagating through the current fleet. Set soaking to 0 + days to bypass soaking and fast-forward the upgrade to the + downstream fleet. + + See $ gcloud topic datetimes for information on duration formats. + + This flag argument must be specified if any of the other arguments + in this group are specified. + + --upgrade-selector=[name=NAME],[version=VERSION] + Name and version of the upgrade to be overridden where version is a + full GKE version. Currently, name can be either k8s_control_plane + or k8s_node. + + This flag argument must be specified if any of the other arguments + in this group are specified. + + At most one of these can be specified: + + --reset-upstream-fleet + Clears the relationship between the current fleet and its upstream + fleet in the rollout sequence. + + To remove the link between the current fleet and its upstream fleet, + run: + + $ gcloud container fleet clusterupgrade update --reset-upstream-fleet + + --upstream-fleet=UPSTREAM_FLEET + The upstream fleet. GKE will finish upgrades on the upstream fleet + before applying the same upgrades to the current fleet. + + To configure the upstream fleet, run: + + $ gcloud container fleet clusterupgrade update \ + --upstream-fleet={upstream_fleet} + +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 container fleet clusterupgrade update + + $ gcloud beta container fleet clusterupgrade update + diff --git a/gcloud/container/fleet/create b/gcloud/container/fleet/create index e6fc51443..d4c7058ad 100644 --- a/gcloud/container/fleet/create +++ b/gcloud/container/fleet/create @@ -5,7 +5,7 @@ SYNOPSIS gcloud container fleet create [--async] [--display-name=DISPLAY_NAME] [--labels=[KEY=VALUE,...]] [--binauthz-evaluation-mode=BINAUTHZ_EVALUATION_MODE - --binauthz-policy-bindings=[name=BINAUTHZ_POLICY,...] + --binauthz-policy-bindings=[name=BINAUTHZ_POLICY] --security-posture=SECURITY_POSTURE --workload-vulnerability-scanning=WORKLOAD_VULNERABILITY_SCANNING] [GCLOUD_WIDE_FLAG ...] @@ -50,11 +50,11 @@ FLAGS fleet, $ gcloud container fleet create \ - --binauthz-evaluation-mode=POLICY_BINDINGS + --binauthz-evaluation-mode=policy-bindings - BINAUTHZ_EVALUATION_MODE must be one of: DISABLED, POLICY_BINDINGS. + BINAUTHZ_EVALUATION_MODE must be one of: disabled, policy-bindings. - --binauthz-policy-bindings=[name=BINAUTHZ_POLICY,...] + --binauthz-policy-bindings=[name=BINAUTHZ_POLICY] The relative resource name of the Binary Authorization policy to audit and/or enforce. GKE policies have the following format: projects/{project_number}/platforms/gke/policies/{policy_id}. diff --git a/gcloud/container/fleet/help b/gcloud/container/fleet/help index dad75f58b..c40737f94 100644 --- a/gcloud/container/fleet/help +++ b/gcloud/container/fleet/help @@ -48,6 +48,9 @@ GROUPS cloudrun Manage the CloudRun feature. + clusterupgrade + Configure the Fleet clusterupgrade feature. + dataplane-v2-encryption Manage Dataplane V2 Encryption Feature. diff --git a/gcloud/container/fleet/update b/gcloud/container/fleet/update index 1625cc1ad..e52530321 100644 --- a/gcloud/container/fleet/update +++ b/gcloud/container/fleet/update @@ -5,7 +5,7 @@ SYNOPSIS gcloud container fleet update [--async] [--display-name=DISPLAY_NAME] [--update-labels=[KEY=VALUE,...]] [--binauthz-evaluation-mode=BINAUTHZ_EVALUATION_MODE - --binauthz-policy-bindings=[name=BINAUTHZ_POLICY,...] + --binauthz-policy-bindings=[name=BINAUTHZ_POLICY] --security-posture=SECURITY_POSTURE --workload-vulnerability-scanning=WORKLOAD_VULNERABILITY_SCANNING] [--clear-labels | --remove-labels=[KEY,...]] [GCLOUD_WIDE_FLAG ...] @@ -51,11 +51,11 @@ FLAGS fleet, $ gcloud container fleet update \ - --binauthz-evaluation-mode=POLICY_BINDINGS + --binauthz-evaluation-mode=policy-bindings - BINAUTHZ_EVALUATION_MODE must be one of: DISABLED, POLICY_BINDINGS. + BINAUTHZ_EVALUATION_MODE must be one of: disabled, policy-bindings. - --binauthz-policy-bindings=[name=BINAUTHZ_POLICY,...] + --binauthz-policy-bindings=[name=BINAUTHZ_POLICY] The relative resource name of the Binary Authorization policy to audit and/or enforce. GKE policies have the following format: projects/{project_number}/platforms/gke/policies/{policy_id}. diff --git a/gcloud/container/hub/clusterupgrade/create b/gcloud/container/hub/clusterupgrade/create new file mode 100644 index 000000000..34e177d4f --- /dev/null +++ b/gcloud/container/hub/clusterupgrade/create @@ -0,0 +1,93 @@ +NAME + gcloud container hub clusterupgrade create - create the clusterupgrade + feature for a fleet within a given project + +SYNOPSIS + gcloud container hub clusterupgrade create + [--default-upgrade-soaking=DEFAULT_UPGRADE_SOAKING] + [--upstream-fleet=UPSTREAM_FLEET] + [--add-upgrade-soaking-override=ADD_UPGRADE_SOAKING_OVERRIDE + --upgrade-selector=[name=NAME],[version=VERSION]] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Create the clusterupgrade feature for a fleet within a given project. + +EXAMPLES + To create the clusterupgrade feature for the current fleet, run: + + $ gcloud container hub clusterupgrade create \ + --default-upgrade-soaking=DEFAULT_UPGRADE_SOAKING + +FLAGS + --default-upgrade-soaking=DEFAULT_UPGRADE_SOAKING + Configures the default soaking duration for each upgrade propagating + through the current fleet to become "COMPLETE". Soaking begins after + all clusters in the fleet are on the target version, or after 30 days + if all cluster upgrades are not complete. Once an upgrade state becomes + "COMPLETE", it will automatically be propagated to the downstream + fleet. Max is 30 days. + + To configure Rollout Sequencing for a fleet, this attribute must be + set. To do this while specifying a default soaking duration of 7 days, + run: + + $ gcloud container hub clusterupgrade create \ + --default-upgrade-soaking=7d + + --upstream-fleet=UPSTREAM_FLEET + The upstream fleet. GKE will finish upgrades on the upstream fleet + before applying the same upgrades to the current fleet. + + To configure the upstream fleet, run: + + $ gcloud container hub clusterupgrade create \ + --upstream-fleet={upstream_fleet} + + Upgrade soaking override. + + Defines a specific soaking time override for a particular upgrade + propagating through the current fleet that supercedes the default + soaking duration configured by `--default-upgrade-soaking`. + + To set an upgrade soaking override of 12 hours for the upgrade with + name, `k8s_control_plane`, and version, `1.23.1-gke.1000`, run: + + $ gcloud container hub clusterupgrade create \ + --add-upgrade-soaking-override=12h \ + --upgrade-selector=name="k8s_control_plane",\ + version="1.23.1-gke.1000" + + --add-upgrade-soaking-override=ADD_UPGRADE_SOAKING_OVERRIDE + Overrides the soaking time for a particular upgrade name and version + propagating through the current fleet. Set soaking to 0 days to + bypass soaking and fast-forward the upgrade to the downstream fleet. + + See $ gcloud topic datetimes for information on duration formats. + + This flag argument must be specified if any of the other arguments in + this group are specified. + + --upgrade-selector=[name=NAME],[version=VERSION] + Name and version of the upgrade to be overridden where version is a + full GKE version. Currently, name can be either k8s_control_plane or + k8s_node. + + This flag argument must be specified if any of the other arguments in + this group are specified. + +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 container hub clusterupgrade create + + $ gcloud beta container hub clusterupgrade create + diff --git a/gcloud/container/hub/clusterupgrade/describe b/gcloud/container/hub/clusterupgrade/describe new file mode 100644 index 000000000..9a2d3b3f2 --- /dev/null +++ b/gcloud/container/hub/clusterupgrade/describe @@ -0,0 +1,47 @@ +NAME + gcloud container hub clusterupgrade describe - describe the clusterupgrade + feature for a fleet within a given project + +SYNOPSIS + gcloud container hub clusterupgrade describe + [--show-linked-cluster-upgrade] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Describe the Fleet clusterupgrade feature used for configuring fleet-based + rollout sequencing. + +EXAMPLES + To view the cluster upgrade feature information for the current fleet, run: + + $ gcloud container hub clusterupgrade describe + +FLAGS + --show-linked-cluster-upgrade + Shows the cluster upgrade feature information for the current fleet as + well as information for all other fleets linked in the same rollout + sequence (provided that the caller has permission to view the upstream + and downstream fleets). This displays cluster upgrade information for + fleets in the current fleet's rollout sequence in order of furthest + upstream to downstream. + + To view the cluster upgrade feature information for the rollout + sequence containing the current fleet, run: + + $ gcloud container hub clusterupgrade describe \ + --show-linked-cluster-upgrade + +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 container hub clusterupgrade describe + + $ gcloud beta container hub clusterupgrade describe + diff --git a/gcloud/container/hub/clusterupgrade/help b/gcloud/container/hub/clusterupgrade/help new file mode 100644 index 000000000..94a470c5d --- /dev/null +++ b/gcloud/container/hub/clusterupgrade/help @@ -0,0 +1,34 @@ +NAME + gcloud container hub clusterupgrade - configure the Fleet clusterupgrade + feature + +SYNOPSIS + gcloud container hub clusterupgrade COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + This fleet feature is used to configure fleet-based rollout sequencing. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + create + Create the clusterupgrade feature for a fleet within a given project. + + describe + Describe the clusterupgrade feature for a fleet within a given project. + + update + Update the clusterupgrade feature for a fleet within a given project. + +NOTES + These variants are also available: + + $ gcloud alpha container hub clusterupgrade + + $ gcloud beta container hub clusterupgrade + diff --git a/gcloud/container/hub/clusterupgrade/update b/gcloud/container/hub/clusterupgrade/update new file mode 100644 index 000000000..bd7db3ad4 --- /dev/null +++ b/gcloud/container/hub/clusterupgrade/update @@ -0,0 +1,120 @@ +NAME + gcloud container hub clusterupgrade update - update the clusterupgrade + feature for a fleet within a given project + +SYNOPSIS + gcloud container hub clusterupgrade update + [--default-upgrade-soaking=DEFAULT_UPGRADE_SOAKING] + [--remove-upgrade-soaking-overrides + | --add-upgrade-soaking-override=ADD_UPGRADE_SOAKING_OVERRIDE + --upgrade-selector=[name=NAME],[version=VERSION]] + [--reset-upstream-fleet | --upstream-fleet=UPSTREAM_FLEET] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Update the clusterupgrade feature for a fleet within a given project. + +EXAMPLES + To update the clusterupgrade feature for the current fleet, run: + + $ gcloud container hub clusterupgrade update \ + --default-upgrade-soaking=DEFAULT_UPGRADE_SOAKING + +FLAGS + --default-upgrade-soaking=DEFAULT_UPGRADE_SOAKING + Configures the default soaking duration for each upgrade propagating + through the current fleet to become "COMPLETE". Soaking begins after + all clusters in the fleet are on the target version, or after 30 days + if all cluster upgrades are not complete. Once an upgrade state becomes + "COMPLETE", it will automatically be propagated to the downstream + fleet. Max is 30 days. + + To configure Rollout Sequencing for a fleet, this attribute must be + set. To do this while specifying a default soaking duration of 7 days, + run: + + $ gcloud container hub clusterupgrade update \ + --default-upgrade-soaking=7d + + At most one of these can be specified: + + --remove-upgrade-soaking-overrides + Removes soaking time overrides for all upgrades propagating through + the current fleet. Consequently, all upgrades will follow the soak + time configured by --default-upgrade-soaking until new overrides are + configured with --add_upgrade_soaking_override and + --upgrade_selector. + + To remove all configured soaking time overrides, run: + + $ gcloud container hub clusterupgrade update \ + --remove-upgrade-soaking-overrides + + Upgrade soaking override. + + Defines a specific soaking time override for a particular upgrade + propagating through the current fleet that supercedes the default + soaking duration configured by `--default-upgrade-soaking`. + + To set an upgrade soaking override of 12 hours for the upgrade with + name, `k8s_control_plane`, and version, `1.23.1-gke.1000`, run: + + $ gcloud container hub clusterupgrade update \ + --add-upgrade-soaking-override=12h \ + --upgrade-selector=name="k8s_control_plane",\ + version="1.23.1-gke.1000" + + --add-upgrade-soaking-override=ADD_UPGRADE_SOAKING_OVERRIDE + Overrides the soaking time for a particular upgrade name and + version propagating through the current fleet. Set soaking to 0 + days to bypass soaking and fast-forward the upgrade to the + downstream fleet. + + See $ gcloud topic datetimes for information on duration formats. + + This flag argument must be specified if any of the other arguments + in this group are specified. + + --upgrade-selector=[name=NAME],[version=VERSION] + Name and version of the upgrade to be overridden where version is a + full GKE version. Currently, name can be either k8s_control_plane + or k8s_node. + + This flag argument must be specified if any of the other arguments + in this group are specified. + + At most one of these can be specified: + + --reset-upstream-fleet + Clears the relationship between the current fleet and its upstream + fleet in the rollout sequence. + + To remove the link between the current fleet and its upstream fleet, + run: + + $ gcloud container hub clusterupgrade update --reset-upstream-fleet + + --upstream-fleet=UPSTREAM_FLEET + The upstream fleet. GKE will finish upgrades on the upstream fleet + before applying the same upgrades to the current fleet. + + To configure the upstream fleet, run: + + $ gcloud container hub clusterupgrade update \ + --upstream-fleet={upstream_fleet} + +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 container hub clusterupgrade update + + $ gcloud beta container hub clusterupgrade update + diff --git a/gcloud/container/hub/create b/gcloud/container/hub/create index 8038566e6..4d3c41d57 100644 --- a/gcloud/container/hub/create +++ b/gcloud/container/hub/create @@ -5,7 +5,7 @@ SYNOPSIS gcloud container hub create [--async] [--display-name=DISPLAY_NAME] [--labels=[KEY=VALUE,...]] [--binauthz-evaluation-mode=BINAUTHZ_EVALUATION_MODE - --binauthz-policy-bindings=[name=BINAUTHZ_POLICY,...] + --binauthz-policy-bindings=[name=BINAUTHZ_POLICY] --security-posture=SECURITY_POSTURE --workload-vulnerability-scanning=WORKLOAD_VULNERABILITY_SCANNING] [GCLOUD_WIDE_FLAG ...] @@ -50,11 +50,11 @@ FLAGS fleet, $ gcloud container hub create \ - --binauthz-evaluation-mode=POLICY_BINDINGS + --binauthz-evaluation-mode=policy-bindings - BINAUTHZ_EVALUATION_MODE must be one of: DISABLED, POLICY_BINDINGS. + BINAUTHZ_EVALUATION_MODE must be one of: disabled, policy-bindings. - --binauthz-policy-bindings=[name=BINAUTHZ_POLICY,...] + --binauthz-policy-bindings=[name=BINAUTHZ_POLICY] The relative resource name of the Binary Authorization policy to audit and/or enforce. GKE policies have the following format: projects/{project_number}/platforms/gke/policies/{policy_id}. diff --git a/gcloud/container/hub/help b/gcloud/container/hub/help index 78fe138d9..fbfed349e 100644 --- a/gcloud/container/hub/help +++ b/gcloud/container/hub/help @@ -48,6 +48,9 @@ GROUPS cloudrun Manage the CloudRun feature. + clusterupgrade + Configure the Fleet clusterupgrade feature. + dataplane-v2-encryption Manage Dataplane V2 Encryption Feature. diff --git a/gcloud/container/hub/update b/gcloud/container/hub/update index 226016610..eb3dcdde2 100644 --- a/gcloud/container/hub/update +++ b/gcloud/container/hub/update @@ -5,7 +5,7 @@ SYNOPSIS gcloud container hub update [--async] [--display-name=DISPLAY_NAME] [--update-labels=[KEY=VALUE,...]] [--binauthz-evaluation-mode=BINAUTHZ_EVALUATION_MODE - --binauthz-policy-bindings=[name=BINAUTHZ_POLICY,...] + --binauthz-policy-bindings=[name=BINAUTHZ_POLICY] --security-posture=SECURITY_POSTURE --workload-vulnerability-scanning=WORKLOAD_VULNERABILITY_SCANNING] [--clear-labels | --remove-labels=[KEY,...]] [GCLOUD_WIDE_FLAG ...] @@ -51,11 +51,11 @@ FLAGS fleet, $ gcloud container hub update \ - --binauthz-evaluation-mode=POLICY_BINDINGS + --binauthz-evaluation-mode=policy-bindings - BINAUTHZ_EVALUATION_MODE must be one of: DISABLED, POLICY_BINDINGS. + BINAUTHZ_EVALUATION_MODE must be one of: disabled, policy-bindings. - --binauthz-policy-bindings=[name=BINAUTHZ_POLICY,...] + --binauthz-policy-bindings=[name=BINAUTHZ_POLICY] The relative resource name of the Binary Authorization policy to audit and/or enforce. GKE policies have the following format: projects/{project_number}/platforms/gke/policies/{policy_id}. diff --git a/gcloud/container/node-pools/create b/gcloud/container/node-pools/create index 06a24c92c..cf1ddf8c6 100644 --- a/gcloud/container/node-pools/create +++ b/gcloud/container/node-pools/create @@ -36,8 +36,9 @@ SYNOPSIS [--node-taints=[NODE_TAINT,...]] [--node-version=NODE_VERSION] [--num-nodes=NUM_NODES; default=3] [--placement-policy=PLACEMENT_POLICY] [--placement-type=PLACEMENT_TYPE] - [--preemptible] [--sandbox=[type=TYPE]] - [--shielded-integrity-monitoring] [--shielded-secure-boot] + [--preemptible] [--resource-manager-tags=[KEY=VALUE,...]] + [--sandbox=[type=TYPE]] [--shielded-integrity-monitoring] + [--shielded-secure-boot] [--sole-tenant-node-affinity-file=SOLE_TENANT_NODE_AFFINITY_FILE] [--spot] [--standard-rollout-policy=[batch-node-count=BATCH_NODE_COUNT, @@ -511,6 +512,27 @@ FLAGS https://cloud.google.com/kubernetes-engine/docs/preemptible-vm for more information on how to use Preemptible VMs with Kubernetes Engine. + --resource-manager-tags=[KEY=VALUE,...] + Applies the specified comma-separated resource manager tags that has + the GCE_FIREWALL purpose to all nodes in the new node pool. + + Examples: + + $ gcloud container node-pools create example-node-pool \ + --resource-manager-tags=tagKeys/1234=tagValues/2345 + $ gcloud container node-pools create example-node-pool \ + --resource-manager-tags=my-project/key1=value1 + $ gcloud container node-pools create example-node-pool \ + --resource-manager-tags=12345/key1=value1,23456/key2=value2 + $ gcloud container node-pools create example-node-pool \ + --resource-manager-tags= + + All nodes, including nodes that are resized or re-created, will have + the specified tags on the corresponding Instance object in the Compute + Engine API. You can reference these tags in network firewall policy + rules. For instructions, see + https://cloud.google.com/firewall/docs/use-tags-for-firewalls. + --sandbox=[type=TYPE] Enables the requested sandbox on all nodes in the node pool. diff --git a/gcloud/container/node-pools/update b/gcloud/container/node-pools/update index bb95e3bbc..a22d1a9cc 100644 --- a/gcloud/container/node-pools/update +++ b/gcloud/container/node-pools/update @@ -10,6 +10,7 @@ SYNOPSIS | --network-performance-configs=[PROPERTY=VALUE,...] | --node-labels=[NODE_LABEL,...] | --node-locations=ZONE,[ZONE,...] | --node-taints=[NODE_TAINT,...] + | --resource-manager-tags=[KEY=VALUE,...] | --system-config-from-file=SYSTEM_CONFIG_FROM_FILE | --tags=[TAG,...] | --windows-os-version=WINDOWS_OS_VERSION | --workload-metadata=WORKLOAD_METADATA | --disk-size=DISK_SIZE @@ -147,6 +148,29 @@ REQUIRED FLAGS To read more about node-taints, see https://cloud.google.com/kubernetes-engine/docs/node-taints. + --resource-manager-tags=[KEY=VALUE,...] + Replaces all the user specified resource manager tags on all nodes in + an existing node pool in a Standard cluster with the given + comma-separated resource manager tags that has the GCE_FIREWALL + purpose. + + Examples: + + $ gcloud container node-pools update example-node-pool \ + --resource-manager-tags=tagKeys/1234=tagValues/2345 + $ gcloud container node-pools update example-node-pool \ + --resource-manager-tags=my-project/key1=value1 + $ gcloud container node-pools update example-node-pool \ + --resource-manager-tags=12345/key1=value1,23456/key2=value2 + $ gcloud container node-pools update example-node-pool \ + --resource-manager-tags= + + All nodes, including nodes that are resized or re-created, will have + the specified tags on the corresponding Instance object in the + Compute Engine API. You can reference these tags in network firewall + policy rules. For instructions, see + https://cloud.google.com/firewall/docs/use-tags-for-firewalls. + --system-config-from-file=SYSTEM_CONFIG_FROM_FILE Path of the YAML/JSON file that contains the node configuration, including Linux kernel parameters (sysctls) and kubelet configs. diff --git a/gcloud/deploy/apply b/gcloud/deploy/apply index ffb4bc2c0..00283a1df 100644 --- a/gcloud/deploy/apply +++ b/gcloud/deploy/apply @@ -1,13 +1,14 @@ NAME gcloud deploy apply - applies a yaml configuration containing Delivery - Pipeline(s), Target(s) and Automation(s) declarative definitions + Pipeline(s), Target(s), Custom Target Type(s), and Automation(s) + declarative definitions SYNOPSIS gcloud deploy apply --file=FILE [--region=REGION] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - Applies a yaml configuration containing Delivery Pipeline(s), Target(s) and - Automation(s) declarative definitions. + Applies a yaml configuration containing Delivery Pipeline(s), Target(s), + Custom Target Type(s), and Automation(s) declarative definitions. EXAMPLES To apply a Cloud Deploy YAML file deploy.yaml: diff --git a/gcloud/deploy/custom-target-types/delete b/gcloud/deploy/custom-target-types/delete new file mode 100644 index 000000000..7249b61e1 --- /dev/null +++ b/gcloud/deploy/custom-target-types/delete @@ -0,0 +1,74 @@ +NAME + gcloud deploy custom-target-types delete - delete a custom target type + +SYNOPSIS + gcloud deploy custom-target-types delete + (CUSTOM_TARGET_TYPE : --region=REGION) [--async] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Delete a custom target type for a specified region. + +EXAMPLES + The following command will delete custom target type + test-custom-target-type, in region us-central1: + + $ gcloud deploy custom-target-types delete test-custom-target-type \ + --region=us-central1 + +POSITIONAL ARGUMENTS + Custom target type resource - The name of the custom target type to + delete. The arguments in this group can be used to specify the attributes + of this resource. (NOTE) Some attributes are not given arguments in this + group but can be set in other ways. + + To set the project attribute: + ◆ provide the argument custom_target_type 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. + + CUSTOM_TARGET_TYPE + ID of the custom target type or fully qualified identifier for the + custom target type. + + To set the custom_target_type attribute: + ▸ provide the argument custom_target_type on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --region=REGION + Location of the custom target type. + + To set the region attribute: + ▸ provide the argument custom_target_type on the command line with + a fully specified name; + ▸ provide the argument --region on the command line; + ▸ set the property deploy/region. + +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 clouddeploy/v1 API. The full documentation for this + API can be found at: https://cloud.google.com/deploy/ + +NOTES + These variants are also available: + + $ gcloud alpha deploy custom-target-types delete + + $ gcloud beta deploy custom-target-types delete + diff --git a/gcloud/deploy/custom-target-types/describe b/gcloud/deploy/custom-target-types/describe new file mode 100644 index 000000000..c89549cd9 --- /dev/null +++ b/gcloud/deploy/custom-target-types/describe @@ -0,0 +1,70 @@ +NAME + gcloud deploy custom-target-types describe - show details for a custom + target type + +SYNOPSIS + gcloud deploy custom-target-types describe + (CUSTOM_TARGET_TYPE : --region=REGION) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Show details for a specified custom target type. + +EXAMPLES + To show details about a custom target type test-custom-target-type in + region us-central, run: + + $ gcloud deploy custom-target-types describe \ + test-custom-target-type --region=us-central1 + +POSITIONAL ARGUMENTS + Custom target type resource - The name of the custom target type you want + to describe. The arguments in this group can be used to specify the + attributes of this resource. (NOTE) Some attributes are not given + arguments in this group but can be set in other ways. + + To set the project attribute: + ◆ provide the argument custom_target_type 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. + + CUSTOM_TARGET_TYPE + ID of the custom target type or fully qualified identifier for the + custom target type. + + To set the custom_target_type attribute: + ▸ provide the argument custom_target_type on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --region=REGION + Location of the custom target type. + + To set the region attribute: + ▸ provide the argument custom_target_type on the command line with + a fully specified name; + ▸ provide the argument --region on the command line; + ▸ set the property deploy/region. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the clouddeploy/v1 API. The full documentation for this + API can be found at: https://cloud.google.com/deploy/ + +NOTES + These variants are also available: + + $ gcloud alpha deploy custom-target-types describe + + $ gcloud beta deploy custom-target-types describe + diff --git a/gcloud/deploy/custom-target-types/export b/gcloud/deploy/custom-target-types/export new file mode 100644 index 000000000..66bc5d53c --- /dev/null +++ b/gcloud/deploy/custom-target-types/export @@ -0,0 +1,73 @@ +NAME + gcloud deploy custom-target-types export - returns the .yaml definition of + the specified custom target type + +SYNOPSIS + gcloud deploy custom-target-types export + (CUSTOM_TARGET_TYPE : --region=REGION) [--destination=DESTINATION] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + The exported yaml definition can be applied by deploy apply command. + +EXAMPLES + To return the .yaml definition of the custom target type + test-custom-target-type, in region us-central1, run: + + $ gcloud deploy custom-target-types export test-custom-target-type \ + --region=us-central1 + +POSITIONAL ARGUMENTS + Custom target type resource - The name of the Custom Target Type. 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 custom_target_type 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. + + CUSTOM_TARGET_TYPE + ID of the custom_target_type or fully qualified identifier for the + custom_target_type. + + To set the custom_target_type attribute: + ▸ provide the argument custom_target_type on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --region=REGION + The Cloud region for the custom_target_type. Alternatively, set the + property [deploy/region]. + + To set the region attribute: + ▸ provide the argument custom_target_type on the command line with + a fully specified name; + ▸ provide the argument --region on the command line; + ▸ set the property deploy/region. + +FLAGS + --destination=DESTINATION + Path to a YAML file where the configuration will be exported. + Alternatively, you may omit this flag to write to standard output. + +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 deploy custom-target-types export + + $ gcloud beta deploy custom-target-types export + diff --git a/gcloud/deploy/custom-target-types/help b/gcloud/deploy/custom-target-types/help new file mode 100644 index 000000000..ecb03c1f4 --- /dev/null +++ b/gcloud/deploy/custom-target-types/help @@ -0,0 +1,37 @@ +NAME + gcloud deploy custom-target-types - create and manage Custom Target Type + resources for Cloud Deploy + +SYNOPSIS + gcloud deploy custom-target-types COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Create and manage Custom Target Type resources for Cloud Deploy. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + delete + Delete a custom target type. + + describe + Show details for a custom target type. + + export + Returns the .yaml definition of the specified custom target type. + + list + List the custom target types. + +NOTES + These variants are also available: + + $ gcloud alpha deploy custom-target-types + + $ gcloud beta deploy custom-target-types + diff --git a/gcloud/deploy/custom-target-types/list b/gcloud/deploy/custom-target-types/list new file mode 100644 index 000000000..60cd88f7f --- /dev/null +++ b/gcloud/deploy/custom-target-types/list @@ -0,0 +1,86 @@ +NAME + gcloud deploy custom-target-types list - list the custom target types + +SYNOPSIS + gcloud deploy custom-target-types list [--region=REGION] + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + List the custom target types for a specified region. + +EXAMPLES + To list the custom target types in region us-central1, run: + + $ gcloud deploy custom-target-types list --region=us-central1 + +FLAGS + Location resource - The region for which you want to list the custom + target types. 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 deploy/region with a fully specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + --region=REGION + ID of the location or fully qualified identifier for the location. + + To set the region attribute: + ▸ provide the argument --region on the command line; + ▸ set the property deploy/region. + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + + --uri + Print a list of resource URIs instead of the default output, and change + the command output to a list of URIs. If this flag is used with + --format, the formatting is applied on this URI list. To display URIs + alongside other keys instead, use the uri() transform. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the clouddeploy/v1 API. The full documentation for this + API can be found at: https://cloud.google.com/deploy/ + +NOTES + These variants are also available: + + $ gcloud alpha deploy custom-target-types list + + $ gcloud beta deploy custom-target-types list + diff --git a/gcloud/deploy/delete b/gcloud/deploy/delete index 74000581a..f38969f9a 100644 --- a/gcloud/deploy/delete +++ b/gcloud/deploy/delete @@ -1,17 +1,17 @@ NAME - gcloud deploy delete - deletes delivery pipeline(s) and target(s) in a yaml - configuration + gcloud deploy delete - deletes Delivery Pipeline(s), Target(s), Custom + Target Type(s), and Automation(s) in a yaml configuration SYNOPSIS gcloud deploy delete --file=FILE [--force] [--region=REGION] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - Deletes delivery pipeline(s) and target(s) in a yaml configuration. + Deletes Delivery Pipeline(s), Target(s), Custom Target Type(s), and + Automation(s) in a yaml configuration. EXAMPLES - To delete the delivery pipeline(s) and target(s) in a Cloud Deploy YAML - file deploy.yaml: + To delete the resources in a Cloud Deploy YAML file deploy.yaml: $ gcloud deploy delete --file=deploy.yaml --region=us-central1 diff --git a/gcloud/deploy/help b/gcloud/deploy/help index 1ddffcffb..222e01811 100644 --- a/gcloud/deploy/help +++ b/gcloud/deploy/help @@ -21,6 +21,9 @@ GROUPS automations Manages Automations resources for Cloud Deploy. + custom-target-types + Create and manage Custom Target Type resources for Cloud Deploy. + delivery-pipelines Create and manage Delivery Pipeline resources for Cloud Deploy. @@ -40,11 +43,13 @@ COMMANDS COMMAND is one of the following: apply - Applies a yaml configuration containing Delivery Pipeline(s), Target(s) - and Automation(s) declarative definitions. + Applies a yaml configuration containing Delivery Pipeline(s), + Target(s), Custom Target Type(s), and Automation(s) declarative + definitions. delete - Deletes delivery pipeline(s) and target(s) in a yaml configuration. + Deletes Delivery Pipeline(s), Target(s), Custom Target Type(s), and + Automation(s) in a yaml configuration. get-config Get the Cloud Deploy config for the provided region and project. diff --git a/gcloud/edge-cloud/networking/subnets/create b/gcloud/edge-cloud/networking/subnets/create index 0a9065a57..c2a052d3d 100644 --- a/gcloud/edge-cloud/networking/subnets/create +++ b/gcloud/edge-cloud/networking/subnets/create @@ -4,10 +4,10 @@ NAME SYNOPSIS gcloud edge-cloud networking subnets create - (SUBNET : --location=LOCATION --zone=ZONE) - --ipv4-range=[IPV4_RANGE,...] --network=NETWORK [--async] - [--description=DESCRIPTION] [--ipv6-range=[IPV6_RANGE,...]] - [--labels=[KEY=VALUE,...]] [--vlan-id=VLAN_ID] [GCLOUD_WIDE_FLAG ...] + (SUBNET : --location=LOCATION --zone=ZONE) --network=NETWORK [--async] + [--description=DESCRIPTION] [--ipv4-range=[IPV4_RANGE,...]] + [--ipv6-range=[IPV6_RANGE,...]] [--labels=[KEY=VALUE,...]] + [--vlan-id=VLAN_ID] [GCLOUD_WIDE_FLAG ...] DESCRIPTION Create a new Distributed Cloud Edge Network subnet. @@ -63,10 +63,6 @@ POSITIONAL ARGUMENTS ▸ provide the argument --zone on the command line. REQUIRED FLAGS - --ipv4-range=[IPV4_RANGE,...] - The ranges of ipv4 addresses that are owned by this subnetwork in CIDR - format. - --network=NETWORK The network that this subnetwork belongs to. @@ -78,6 +74,10 @@ OPTIONAL FLAGS --description=DESCRIPTION An optional, textual description for the subnet. + --ipv4-range=[IPV4_RANGE,...] + The ranges of ipv4 addresses that are owned by this subnetwork in CIDR + format. + --ipv6-range=[IPV6_RANGE,...] The ranges of ipv6 addresses that are owned by this subnetwork in CIDR format. diff --git a/gcloud/functions/deploy b/gcloud/functions/deploy index 743c821dc..887b8c4b5 100644 --- a/gcloud/functions/deploy +++ b/gcloud/functions/deploy @@ -8,6 +8,7 @@ SYNOPSIS [--entry-point=ENTRY_POINT] [--gen2] [--ignore-file=IGNORE_FILE] [--ingress-settings=INGRESS_SETTINGS] [--retry] [--run-service-account=RUN_SERVICE_ACCOUNT] [--runtime=RUNTIME] + [--runtime-update-policy=RUNTIME_UPDATE_POLICY] [--security-level=SECURITY_LEVEL; default="secure-always"] [--serve-all-traffic-latest-revision] [--service-account=SERVICE_ACCOUNT] [--source=SOURCE] @@ -164,6 +165,10 @@ FLAGS For a list of available runtimes, run gcloud functions runtimes list. + --runtime-update-policy=RUNTIME_UPDATE_POLICY + Runtime update policy for the 1st Gen function being deployed. The + option on-deploy is used by default. + --security-level=SECURITY_LEVEL; default="secure-always" Security level controls whether a function's URL supports HTTPS only or both HTTP and HTTPS. By default, secure-always will be used, meaning diff --git a/gcloud/infra-manager/deployments/apply b/gcloud/infra-manager/deployments/apply index 012e54477..7b445b3e7 100644 --- a/gcloud/infra-manager/deployments/apply +++ b/gcloud/infra-manager/deployments/apply @@ -237,9 +237,3 @@ GCLOUD WIDE FLAGS --trace-token, --user-output-enabled, --verbosity. Run $ gcloud help for details. - -NOTES - This variant is also available: - - $ gcloud alpha infra-manager deployments apply - diff --git a/gcloud/infra-manager/deployments/delete b/gcloud/infra-manager/deployments/delete index a0e31d5f4..5b275f145 100644 --- a/gcloud/infra-manager/deployments/delete +++ b/gcloud/infra-manager/deployments/delete @@ -69,9 +69,3 @@ GCLOUD WIDE FLAGS API REFERENCE This command uses the config/v1 API. The full documentation for this API can be found at: https://cloud.google.com/infrastructure-manager/docs - -NOTES - This variant is also available: - - $ gcloud alpha infra-manager deployments delete - diff --git a/gcloud/infra-manager/deployments/describe b/gcloud/infra-manager/deployments/describe index c72f1c50b..e34d34ec2 100644 --- a/gcloud/infra-manager/deployments/describe +++ b/gcloud/infra-manager/deployments/describe @@ -58,9 +58,3 @@ GCLOUD WIDE FLAGS API REFERENCE This command uses the config/v1 API. The full documentation for this API can be found at: https://cloud.google.com/infrastructure-manager/docs - -NOTES - This variant is also available: - - $ gcloud alpha infra-manager deployments describe - diff --git a/gcloud/infra-manager/deployments/export-lock b/gcloud/infra-manager/deployments/export-lock index 2b522a35a..6dcc28530 100644 --- a/gcloud/infra-manager/deployments/export-lock +++ b/gcloud/infra-manager/deployments/export-lock @@ -56,9 +56,3 @@ GCLOUD WIDE FLAGS --trace-token, --user-output-enabled, --verbosity. Run $ gcloud help for details. - -NOTES - This variant is also available: - - $ gcloud alpha infra-manager deployments export-lock - diff --git a/gcloud/infra-manager/deployments/export-statefile b/gcloud/infra-manager/deployments/export-statefile index ec3a1de5f..f8418ec3e 100644 --- a/gcloud/infra-manager/deployments/export-statefile +++ b/gcloud/infra-manager/deployments/export-statefile @@ -60,9 +60,3 @@ GCLOUD WIDE FLAGS --trace-token, --user-output-enabled, --verbosity. Run $ gcloud help for details. - -NOTES - This variant is also available: - - $ gcloud alpha infra-manager deployments export-statefile - diff --git a/gcloud/infra-manager/deployments/help b/gcloud/infra-manager/deployments/help index 017dde740..45b90ebc6 100644 --- a/gcloud/infra-manager/deployments/help +++ b/gcloud/infra-manager/deployments/help @@ -41,9 +41,3 @@ COMMANDS unlock Unlocks the deployment. - -NOTES - This variant is also available: - - $ gcloud alpha infra-manager deployments - diff --git a/gcloud/infra-manager/deployments/import-statefile b/gcloud/infra-manager/deployments/import-statefile index ac47800db..fef4dbab9 100644 --- a/gcloud/infra-manager/deployments/import-statefile +++ b/gcloud/infra-manager/deployments/import-statefile @@ -61,9 +61,3 @@ GCLOUD WIDE FLAGS --trace-token, --user-output-enabled, --verbosity. Run $ gcloud help for details. - -NOTES - This variant is also available: - - $ gcloud alpha infra-manager deployments import-statefile - diff --git a/gcloud/infra-manager/deployments/list b/gcloud/infra-manager/deployments/list index afd0eb60a..ffa3e283b 100644 --- a/gcloud/infra-manager/deployments/list +++ b/gcloud/infra-manager/deployments/list @@ -76,9 +76,3 @@ GCLOUD WIDE FLAGS API REFERENCE This command uses the config/v1 API. The full documentation for this API can be found at: https://cloud.google.com/infrastructure-manager/docs - -NOTES - This variant is also available: - - $ gcloud alpha infra-manager deployments list - diff --git a/gcloud/infra-manager/deployments/lock b/gcloud/infra-manager/deployments/lock index 7cbfb68bb..708c7c773 100644 --- a/gcloud/infra-manager/deployments/lock +++ b/gcloud/infra-manager/deployments/lock @@ -59,9 +59,3 @@ GCLOUD WIDE FLAGS --trace-token, --user-output-enabled, --verbosity. Run $ gcloud help for details. - -NOTES - This variant is also available: - - $ gcloud alpha infra-manager deployments lock - diff --git a/gcloud/infra-manager/deployments/unlock b/gcloud/infra-manager/deployments/unlock index 1a22311d3..6a74ce21c 100644 --- a/gcloud/infra-manager/deployments/unlock +++ b/gcloud/infra-manager/deployments/unlock @@ -65,9 +65,3 @@ GCLOUD WIDE FLAGS --trace-token, --user-output-enabled, --verbosity. Run $ gcloud help for details. - -NOTES - This variant is also available: - - $ gcloud alpha infra-manager deployments unlock - diff --git a/gcloud/infra-manager/help b/gcloud/infra-manager/help index 545b9bd70..ef010ee7f 100644 --- a/gcloud/infra-manager/help +++ b/gcloud/infra-manager/help @@ -23,9 +23,3 @@ GROUPS revisions Manage Revision resources. - -NOTES - This variant is also available: - - $ gcloud alpha infra-manager - diff --git a/gcloud/infra-manager/resources/describe b/gcloud/infra-manager/resources/describe index 547054576..be2abe2bb 100644 --- a/gcloud/infra-manager/resources/describe +++ b/gcloud/infra-manager/resources/describe @@ -77,9 +77,3 @@ GCLOUD WIDE FLAGS API REFERENCE This command uses the config/v1 API. The full documentation for this API can be found at: https://cloud.google.com/infrastructure-manager/docs - -NOTES - This variant is also available: - - $ gcloud alpha infra-manager resources describe - diff --git a/gcloud/infra-manager/resources/help b/gcloud/infra-manager/resources/help index e824edcb2..314c54822 100644 --- a/gcloud/infra-manager/resources/help +++ b/gcloud/infra-manager/resources/help @@ -21,9 +21,3 @@ COMMANDS list List resources. - -NOTES - This variant is also available: - - $ gcloud alpha infra-manager resources - diff --git a/gcloud/infra-manager/resources/list b/gcloud/infra-manager/resources/list index 724fb3a2a..43d2c068c 100644 --- a/gcloud/infra-manager/resources/list +++ b/gcloud/infra-manager/resources/list @@ -99,9 +99,3 @@ GCLOUD WIDE FLAGS API REFERENCE This command uses the config/v1 API. The full documentation for this API can be found at: https://cloud.google.com/infrastructure-manager/docs - -NOTES - This variant is also available: - - $ gcloud alpha infra-manager resources list - diff --git a/gcloud/infra-manager/revisions/describe b/gcloud/infra-manager/revisions/describe index 5579f83f6..12cce8f87 100644 --- a/gcloud/infra-manager/revisions/describe +++ b/gcloud/infra-manager/revisions/describe @@ -67,9 +67,3 @@ GCLOUD WIDE FLAGS API REFERENCE This command uses the config/v1 API. The full documentation for this API can be found at: https://cloud.google.com/infrastructure-manager/docs - -NOTES - This variant is also available: - - $ gcloud alpha infra-manager revisions describe - diff --git a/gcloud/infra-manager/revisions/export-statefile b/gcloud/infra-manager/revisions/export-statefile index 5b8eca764..4b2645740 100644 --- a/gcloud/infra-manager/revisions/export-statefile +++ b/gcloud/infra-manager/revisions/export-statefile @@ -64,9 +64,3 @@ GCLOUD WIDE FLAGS --trace-token, --user-output-enabled, --verbosity. Run $ gcloud help for details. - -NOTES - This variant is also available: - - $ gcloud alpha infra-manager revisions export-statefile - diff --git a/gcloud/infra-manager/revisions/help b/gcloud/infra-manager/revisions/help index ed06f21f4..979290711 100644 --- a/gcloud/infra-manager/revisions/help +++ b/gcloud/infra-manager/revisions/help @@ -23,9 +23,3 @@ COMMANDS list List revisions. - -NOTES - This variant is also available: - - $ gcloud alpha infra-manager revisions - diff --git a/gcloud/infra-manager/revisions/list b/gcloud/infra-manager/revisions/list index e3846572b..01dc09980 100644 --- a/gcloud/infra-manager/revisions/list +++ b/gcloud/infra-manager/revisions/list @@ -92,9 +92,3 @@ GCLOUD WIDE FLAGS API REFERENCE This command uses the config/v1 API. The full documentation for this API can be found at: https://cloud.google.com/infrastructure-manager/docs - -NOTES - This variant is also available: - - $ gcloud alpha infra-manager revisions list - diff --git a/gcloud/pubsub/subscriptions/create b/gcloud/pubsub/subscriptions/create index 6fed802d4..41f5334e3 100644 --- a/gcloud/pubsub/subscriptions/create +++ b/gcloud/pubsub/subscriptions/create @@ -13,8 +13,8 @@ SYNOPSIS [--push-auth-token-audience=OPTIONAL_AUDIENCE_OVERRIDE] [--push-endpoint=PUSH_ENDPOINT] [--retain-acked-messages] [[--bigquery-table=BIGQUERY_TABLE - : --drop-unknown-fields --use-topic-schema --write-metadata] - | [--cloud-storage-bucket=CLOUD_STORAGE_BUCKET + : --drop-unknown-fields --write-metadata --use-table-schema + | --use-topic-schema] | [--cloud-storage-bucket=CLOUD_STORAGE_BUCKET : --cloud-storage-file-prefix=CLOUD_STORAGE_FILE_PREFIX --cloud-storage-file-suffix=CLOUD_STORAGE_FILE_SUFFIX --cloud-storage-max-bytes=CLOUD_STORAGE_MAX_BYTES @@ -166,16 +166,10 @@ OPTIONAL FLAGS in this group are specified. --drop-unknown-fields - When --use-topic-schema is set, whether or not to ignore fields in - the topic schema that do not appear in the BigQuery schema. If - false, then the BigQuery schema must contain all fields that are - also present in the topic schema. Use --no-drop-unknown-fields to - disable this flag. - - --use-topic-schema - Whether or not to use the schema for the subscription's topic (if - it exists) when writing messages to BigQuery. Use - --no-use-topic-schema to disable this flag. + If either --use-topic-schema or --use-table-schema is set, whether + or not to ignore fields in the message that do not appear in the + BigQuery table schema. Use --no-drop-unknown-fields to disable this + flag. --write-metadata Whether or not to write message metadata including message ID, @@ -186,6 +180,20 @@ OPTIONAL FLAGS JSON object in the attributes column. Use --no-write-metadata to disable this flag. + At most one of these can be specified: + + --use-table-schema + Whether or not to use the BigQuery table schema when writing + messages to BigQuery. Use --no-use-table-schema to disable this + flag. + + --use-topic-schema + Whether or not to use the schema for the subscription's topic (if + it exists) when writing messages to BigQuery. If + --drop-unknown-fields is not set, then the BigQuery schema must + contain all fields that are present in the topic schema. Use + --no-use-topic-schema to disable this flag. + Cloud Storage Config Options. The Cloud Pub/Sub service account associated with the enclosing subscription's parent project (i.e., service-{project_number}@gcp-sa-pubsub.iam.gserviceaccount.com) must diff --git a/gcloud/pubsub/subscriptions/update b/gcloud/pubsub/subscriptions/update index a1a70bb04..50038c21c 100644 --- a/gcloud/pubsub/subscriptions/update +++ b/gcloud/pubsub/subscriptions/update @@ -12,8 +12,8 @@ SYNOPSIS [--push-endpoint=PUSH_ENDPOINT] [--retain-acked-messages] [--update-labels=[KEY=VALUE,...]] [--clear-bigquery-config | [--bigquery-table=BIGQUERY_TABLE - : --drop-unknown-fields --use-topic-schema --write-metadata] - | --clear-cloud-storage-config + : --drop-unknown-fields --write-metadata --use-table-schema + | --use-topic-schema] | --clear-cloud-storage-config | [--cloud-storage-bucket=CLOUD_STORAGE_BUCKET : --cloud-storage-file-prefix=CLOUD_STORAGE_FILE_PREFIX --cloud-storage-file-suffix=CLOUD_STORAGE_FILE_SUFFIX @@ -136,17 +136,11 @@ FLAGS arguments in this group are specified. --drop-unknown-fields - When --use-topic-schema is set, whether or not to ignore fields - in the topic schema that do not appear in the BigQuery schema. If - false, then the BigQuery schema must contain all fields that are - also present in the topic schema. Use --no-drop-unknown-fields to + If either --use-topic-schema or --use-table-schema is set, + whether or not to ignore fields in the message that do not appear + in the BigQuery table schema. Use --no-drop-unknown-fields to disable this flag. - --use-topic-schema - Whether or not to use the schema for the subscription's topic (if - it exists) when writing messages to BigQuery. Use - --no-use-topic-schema to disable this flag. - --write-metadata Whether or not to write message metadata including message ID, publish timestamp, ordering key, and attributes to BigQuery. The @@ -156,6 +150,20 @@ FLAGS JSON object in the attributes column. Use --no-write-metadata to disable this flag. + At most one of these can be specified: + + --use-table-schema + Whether or not to use the BigQuery table schema when writing + messages to BigQuery. Use --no-use-table-schema to disable this + flag. + + --use-topic-schema + Whether or not to use the schema for the subscription's topic + (if it exists) when writing messages to BigQuery. If + --drop-unknown-fields is not set, then the BigQuery schema must + contain all fields that are present in the topic schema. Use + --no-use-topic-schema to disable this flag. + At most one of these can be specified: --clear-cloud-storage-config diff --git a/gcloud/services/api-keys/help b/gcloud/services/api-keys/help index dcb1d3d77..f4c6ca732 100644 --- a/gcloud/services/api-keys/help +++ b/gcloud/services/api-keys/help @@ -33,6 +33,9 @@ COMMANDS lookup Look up resource name of a key string. + undelete + Undelete an API key. + update Update an API key's metadata. diff --git a/gcloud/services/api-keys/undelete b/gcloud/services/api-keys/undelete new file mode 100644 index 000000000..c89b829b9 --- /dev/null +++ b/gcloud/services/api-keys/undelete @@ -0,0 +1,85 @@ +NAME + gcloud services api-keys undelete - undelete an API key + +SYNOPSIS + gcloud services api-keys undelete + ([KEY : --location=LOCATION] --key-string=KEY_STRING) [--async] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + API Keys that are deleted will be retained in the system for 30 days. If a + key is still within this retention window, it can be undeleted with this + command. + +EXAMPLES + UnDelete an API Key (Key or key-string should be specified): + + To undelete with key 1234, run: + + $ gcloud services api-keys undelete 1234 + + To undelete with 1234 in project myproject using the fully qualified API + key name, run: + + $ gcloud services api-keys undelete \ + projects/myproject/locations/global/keys/1234 + + To undelete using a Key-string, run: + + $ gcloud services api-keys undelete --key-string='my-key-string' + +POSITIONAL ARGUMENTS + Exactly one of these must be specified: + + Key resource - The name of the key to undelete. 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 key on the command line with a fully specified + name; + ▸ provide the argument --project on the command line; + ▸ set the property core/project. + + KEY + ID of the key or fully qualified identifier for the key. + + To set the key attribute: + ▫ provide the argument key 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 key. + + To set the location attribute: + ▫ provide the argument key on the command line with a fully + specified name; + ▫ provide the argument --location on the command line; + ▫ location will default to global. + + --key-string=KEY_STRING + Key String of the key. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + These variants are also available: + + $ gcloud alpha services api-keys undelete + + $ gcloud beta services api-keys undelete +