From 64e67b443ca6be006aa48b5e70914183685fb727 Mon Sep 17 00:00:00 2001 From: Automated Date: Thu, 20 Jul 2023 11:47:25 +0000 Subject: [PATCH] gcloud: Thu Jul 20 11:47:24 UTC 2023 --- gcloud/_version | 10 +- .../models/remove-iam-policy-binding | 2 +- .../models/remove-iam-policy-binding | 2 +- gcloud/alpha/assured/workloads/create | 5 + gcloud/alpha/bigtable/instances/tables/update | 2 +- gcloud/alpha/builds/triggers/help | 3 + .../builds/triggers/update/bitbucketserver | 255 +++++++++++ .../triggers/update/cloud-source-repositories | 229 ++++++++++ gcloud/alpha/builds/triggers/update/github | 270 ++++++++++++ gcloud/alpha/builds/triggers/update/gitlab | 254 +++++++++++ gcloud/alpha/builds/triggers/update/help | 49 +++ gcloud/alpha/builds/triggers/update/manual | 228 ++++++++++ gcloud/alpha/builds/triggers/update/pubsub | 245 +++++++++++ gcloud/alpha/builds/triggers/update/webhook | 247 +++++++++++ gcloud/alpha/compute/commitments/create | 10 +- .../compute/firewall-policies/rules/create | 8 +- .../compute/firewall-policies/rules/update | 8 +- gcloud/alpha/compute/instance-templates/list | 16 +- gcloud/alpha/compute/instances/list | 13 +- gcloud/alpha/compute/interconnects/create | 14 +- .../compute/interconnects/macsec/add-key | 4 +- .../compute/interconnects/macsec/get-config | 13 +- .../alpha/compute/interconnects/macsec/help | 8 +- .../compute/interconnects/macsec/remove-key | 12 +- .../alpha/compute/interconnects/macsec/update | 12 +- .../compute/interconnects/macsec/update-key | 55 +++ .../network-firewall-policies/rules/create | 7 + .../network-firewall-policies/rules/update | 7 + .../compute/os-config/guest-policies/create | 72 --- .../compute/os-config/guest-policies/delete | 63 --- .../compute/os-config/guest-policies/describe | 63 --- .../compute/os-config/guest-policies/help | 47 -- .../compute/os-config/guest-policies/lookup | 62 --- .../compute/os-config/guest-policies/update | 73 --- gcloud/alpha/compute/os-config/help | 10 - .../os-config/patch-deployments/create | 55 --- .../os-config/patch-deployments/delete | 56 --- .../os-config/patch-deployments/describe | 56 --- .../compute/os-config/patch-deployments/help | 50 --- .../compute/os-config/patch-deployments/pause | 56 --- .../os-config/patch-deployments/resume | 56 --- .../os-config/patch-deployments/update | 50 --- .../alpha/compute/os-config/patch-jobs/cancel | 50 --- .../compute/os-config/patch-jobs/describe | 50 --- .../compute/os-config/patch-jobs/execute | 414 ------------------ .../alpha/compute/os-config/patch-jobs/help | 43 -- .../alpha/compute/target-http-proxies/create | 4 +- .../alpha/compute/target-http-proxies/update | 2 +- .../alpha/compute/target-https-proxies/create | 4 +- .../alpha/compute/target-https-proxies/update | 2 +- gcloud/alpha/compute/tpus/tpu-vm/create | 2 +- gcloud/alpha/compute/tpus/tpu-vm/update | 7 +- gcloud/alpha/config/get | 4 + gcloud/alpha/config/help | 4 + gcloud/alpha/config/list | 4 + gcloud/alpha/config/set | 4 + gcloud/alpha/config/unset | 4 + gcloud/alpha/container/clusters/create | 50 ++- gcloud/alpha/container/clusters/create-auto | 45 +- gcloud/alpha/container/clusters/update | 55 ++- .../fleet/fleetobservability/describe | 35 ++ .../fleet/fleetobservability/disable | 39 ++ .../container/fleet/fleetobservability/enable | 34 ++ .../container/fleet/fleetobservability/help | 42 ++ .../container/fleet/fleetobservability/update | 62 +++ gcloud/alpha/container/fleet/help | 3 + .../container/hub/fleetobservability/describe | 35 ++ .../container/hub/fleetobservability/disable | 39 ++ .../container/hub/fleetobservability/enable | 33 ++ .../container/hub/fleetobservability/help | 42 ++ .../container/hub/fleetobservability/update | 62 +++ gcloud/alpha/container/hub/help | 3 + .../edge-cloud/container/get-server-config | 56 +++ gcloud/alpha/edge-cloud/container/help | 8 +- gcloud/alpha/firestore/databases/delete | 54 +++ gcloud/alpha/firestore/databases/help | 3 + gcloud/alpha/functions/deploy | 10 + .../iam/workforce-pools/providers/create-oidc | 20 +- .../iam/workforce-pools/providers/update-oidc | 15 +- gcloud/alpha/infra-manager/deployments/apply | 256 +++++++++++ gcloud/alpha/infra-manager/deployments/delete | 79 ++++ .../alpha/infra-manager/deployments/describe | 67 +++ gcloud/alpha/infra-manager/deployments/help | 35 ++ .../deployments/list} | 53 ++- gcloud/alpha/infra-manager/help | 29 ++ gcloud/alpha/infra-manager/revisions/describe | 76 ++++ gcloud/alpha/infra-manager/revisions/help | 29 ++ .../revisions}/list | 72 +-- gcloud/alpha/memcache/instances/create | 6 + .../models/remove-iam-policy-binding | 2 +- gcloud/alpha/monitoring/policies/help | 3 + gcloud/alpha/monitoring/policies/migrate | 40 ++ .../security-profile-groups/create | 13 +- .../security-profile-groups/delete | 9 +- .../security-profile-groups/describe | 8 +- .../security-profile-groups/list | 2 +- .../security-profile-groups/update | 10 +- .../threat-prevention/add-override | 4 +- .../threat-prevention/create | 5 +- .../threat-prevention/delete | 8 +- .../threat-prevention/delete-override | 4 +- .../security-profiles/threat-prevention/list | 2 +- .../threat-prevention/list-overrides | 4 +- .../threat-prevention/update-override | 4 +- .../alpha/projects/get-ancestors-iam-policy | 7 +- .../alpha/projects/remove-iam-policy-binding | 6 +- gcloud/alpha/scc/assets/describe | 9 +- gcloud/alpha/scc/assets/get-parent | 9 +- gcloud/alpha/scc/assets/get-project | 9 +- gcloud/alpha/scc/assets/group | 9 +- gcloud/alpha/scc/assets/help | 22 +- gcloud/alpha/scc/assets/list | 9 +- gcloud/alpha/scc/assets/list-marks | 9 +- gcloud/alpha/scc/assets/run-discovery | 14 +- gcloud/alpha/spanner/databases/execute-sql | 6 +- gcloud/alpha/sql/instances/create | 9 + gcloud/alpha/sql/instances/patch | 9 + gcloud/alpha/storage/buckets/describe | 6 +- gcloud/alpha/storage/buckets/list | 6 +- gcloud/alpha/storage/buckets/update | 4 +- gcloud/alpha/storage/du | 4 +- gcloud/alpha/storage/help | 3 + gcloud/alpha/storage/hmac/create | 39 ++ gcloud/alpha/storage/hmac/delete | 40 ++ gcloud/alpha/storage/hmac/describe | 40 ++ gcloud/alpha/storage/hmac/help | 40 ++ .../patch-jobs => storage/hmac}/list | 49 ++- gcloud/alpha/storage/hmac/update | 59 +++ gcloud/alpha/storage/objects/describe | 6 +- gcloud/alpha/storage/objects/list | 10 +- gcloud/alpha/storage/sign-url | 4 +- gcloud/assured/workloads/create | 5 + .../models/remove-iam-policy-binding | 2 +- gcloud/beta/assured/workloads/create | 5 + gcloud/beta/bigtable/instances/tables/create | 20 +- gcloud/beta/bigtable/instances/tables/update | 27 +- gcloud/beta/builds/triggers/help | 3 + .../builds/triggers/update/bitbucketserver | 253 +++++++++++ .../triggers/update/cloud-source-repositories | 227 ++++++++++ gcloud/beta/builds/triggers/update/github | 268 ++++++++++++ gcloud/beta/builds/triggers/update/gitlab | 252 +++++++++++ gcloud/beta/builds/triggers/update/help | 47 ++ gcloud/beta/builds/triggers/update/manual | 226 ++++++++++ gcloud/beta/builds/triggers/update/pubsub | 243 ++++++++++ gcloud/beta/builds/triggers/update/webhook | 245 +++++++++++ gcloud/beta/compute/instance-templates/create | 11 +- gcloud/beta/compute/instances/bulk/create | 7 + gcloud/beta/compute/instances/create | 11 +- .../compute/instances/create-with-container | 7 + gcloud/beta/compute/instances/set-scheduling | 7 + gcloud/beta/compute/interconnects/create | 14 +- gcloud/beta/compute/interconnects/help | 4 + .../beta/compute/interconnects/macsec/add-key | 53 +++ .../compute/interconnects/macsec/get-config | 40 ++ gcloud/beta/compute/interconnects/macsec/help | 43 ++ .../compute/interconnects/macsec/remove-key | 43 ++ .../beta/compute/interconnects/macsec/update | 53 +++ .../compute/interconnects/macsec/update-key | 53 +++ .../compute/os-config/guest-policies/create | 5 +- .../compute/os-config/guest-policies/delete | 5 +- .../compute/os-config/guest-policies/describe | 5 +- .../compute/os-config/guest-policies/help | 5 +- .../compute/os-config/guest-policies/list | 5 +- .../compute/os-config/guest-policies/lookup | 5 +- .../compute/os-config/guest-policies/update | 5 +- .../os-config/patch-deployments/create | 6 +- .../os-config/patch-deployments/delete | 6 +- .../os-config/patch-deployments/describe | 6 +- .../compute/os-config/patch-deployments/help | 6 +- .../compute/os-config/patch-deployments/list | 6 +- .../compute/os-config/patch-deployments/pause | 6 +- .../os-config/patch-deployments/resume | 6 +- .../os-config/patch-deployments/update | 6 +- .../beta/compute/os-config/patch-jobs/cancel | 6 +- .../compute/os-config/patch-jobs/describe | 6 +- .../beta/compute/os-config/patch-jobs/execute | 6 +- gcloud/beta/compute/os-config/patch-jobs/help | 6 +- gcloud/beta/compute/os-config/patch-jobs/list | 6 +- .../patch-jobs/list-instance-details | 6 +- .../beta/compute/target-http-proxies/create | 4 +- .../beta/compute/target-http-proxies/update | 2 +- .../beta/compute/target-https-proxies/create | 4 +- .../beta/compute/target-https-proxies/update | 2 +- gcloud/beta/config/get | 4 + gcloud/beta/config/help | 4 + gcloud/beta/config/list | 4 + gcloud/beta/config/set | 4 + gcloud/beta/config/unset | 4 + gcloud/beta/container/clusters/create | 50 ++- gcloud/beta/container/clusters/create-auto | 45 +- gcloud/beta/container/clusters/update | 55 ++- .../fleet/fleetobservability/describe | 33 ++ .../fleet/fleetobservability/disable | 37 ++ .../container/fleet/fleetobservability/enable | 32 ++ .../container/fleet/fleetobservability/help | 40 ++ .../container/fleet/fleetobservability/update | 60 +++ gcloud/beta/container/fleet/help | 3 + .../container/hub/fleetobservability/describe | 33 ++ .../container/hub/fleetobservability/disable | 37 ++ .../container/hub/fleetobservability/enable | 31 ++ .../container/hub/fleetobservability/help | 39 ++ .../container/hub/fleetobservability/update | 60 +++ gcloud/beta/container/hub/help | 3 + gcloud/beta/functions/deploy | 10 + .../iam/workforce-pools/providers/create-oidc | 20 +- .../iam/workforce-pools/providers/update-oidc | 15 +- gcloud/beta/memcache/instances/create | 6 + .../models/remove-iam-policy-binding | 2 +- .../firewall-endpoint-associations/create | 43 +- .../firewall-endpoint-associations/update | 50 ++- .../security-profile-groups/create | 13 +- .../security-profile-groups/delete | 9 +- .../security-profile-groups/describe | 8 +- .../security-profile-groups/list | 2 +- .../security-profile-groups/update | 10 +- .../threat-prevention/add-override | 4 +- .../threat-prevention/create | 5 +- .../threat-prevention/delete | 8 +- .../threat-prevention/delete-override | 4 +- .../security-profiles/threat-prevention/list | 2 +- .../threat-prevention/list-overrides | 4 +- .../threat-prevention/update-override | 4 +- gcloud/beta/projects/get-ancestors-iam-policy | 7 +- gcloud/beta/scc/assets/describe | 9 +- gcloud/beta/scc/assets/get-parent | 9 +- gcloud/beta/scc/assets/get-project | 9 +- gcloud/beta/scc/assets/group | 9 +- gcloud/beta/scc/assets/help | 27 +- gcloud/beta/scc/assets/list | 9 +- gcloud/beta/scc/assets/list-marks | 9 +- gcloud/beta/scc/assets/run-discovery | 11 +- gcloud/beta/spanner/databases/execute-sql | 6 +- gcloud/beta/sql/instances/create | 9 + gcloud/beta/sql/instances/patch | 9 + gcloud/bigtable/instances/tables/create | 20 +- gcloud/bigtable/instances/tables/update | 27 +- gcloud/builds/triggers/help | 3 + gcloud/builds/triggers/update/bitbucketserver | 251 +++++++++++ .../triggers/update/cloud-source-repositories | 225 ++++++++++ gcloud/builds/triggers/update/github | 267 +++++++++++ gcloud/builds/triggers/update/gitlab | 251 +++++++++++ gcloud/builds/triggers/update/help | 45 ++ gcloud/builds/triggers/update/manual | 225 ++++++++++ gcloud/builds/triggers/update/pubsub | 242 ++++++++++ gcloud/builds/triggers/update/webhook | 244 +++++++++++ .../os-config/patch-deployments/create | 4 +- .../os-config/patch-deployments/delete | 4 +- .../os-config/patch-deployments/describe | 4 +- .../compute/os-config/patch-deployments/help | 4 +- .../compute/os-config/patch-deployments/list | 4 +- .../compute/os-config/patch-deployments/pause | 4 +- .../os-config/patch-deployments/resume | 4 +- .../os-config/patch-deployments/update | 4 +- gcloud/compute/os-config/patch-jobs/cancel | 4 +- gcloud/compute/os-config/patch-jobs/describe | 4 +- gcloud/compute/os-config/patch-jobs/execute | 4 +- gcloud/compute/os-config/patch-jobs/help | 4 +- gcloud/compute/os-config/patch-jobs/list | 4 +- .../patch-jobs/list-instance-details | 4 +- gcloud/compute/routers/add-bgp-peer | 18 +- gcloud/compute/routers/update-bgp-peer | 40 +- gcloud/compute/target-http-proxies/create | 11 +- gcloud/compute/target-http-proxies/update | 15 + gcloud/compute/target-https-proxies/create | 8 + gcloud/compute/target-https-proxies/update | 15 + gcloud/compute/tpus/tpu-vm/create | 2 +- gcloud/config/get | 4 + gcloud/config/help | 4 + gcloud/config/list | 4 + gcloud/config/set | 4 + gcloud/config/unset | 4 + gcloud/container/clusters/create | 49 ++- gcloud/container/clusters/create-auto | 40 +- gcloud/container/clusters/get-credentials | 7 +- gcloud/container/clusters/update | 51 ++- .../fleet/fleetobservability/describe | 31 ++ .../fleet/fleetobservability/disable | 36 ++ .../container/fleet/fleetobservability/enable | 30 ++ .../container/fleet/fleetobservability/help | 37 ++ .../container/fleet/fleetobservability/update | 59 +++ gcloud/container/fleet/help | 3 + .../container/hub/fleetobservability/describe | 31 ++ .../container/hub/fleetobservability/disable | 36 ++ .../container/hub/fleetobservability/enable | 30 ++ gcloud/container/hub/fleetobservability/help | 37 ++ .../container/hub/fleetobservability/update | 59 +++ gcloud/container/hub/help | 3 + gcloud/functions/deploy | 10 + .../iam/workforce-pools/providers/create-oidc | 20 +- .../iam/workforce-pools/providers/update-oidc | 15 +- gcloud/memcache/instances/create | 6 + .../models/remove-iam-policy-binding | 2 +- gcloud/projects/get-ancestors-iam-policy | 7 +- gcloud/pubsub/subscriptions/create | 15 + .../pubsub/subscriptions/modify-push-config | 15 + gcloud/pubsub/subscriptions/update | 21 + gcloud/scc/assets/describe | 6 + gcloud/scc/assets/get-parent | 6 + gcloud/scc/assets/get-project | 6 + gcloud/scc/assets/group | 6 + gcloud/scc/assets/help | 18 +- gcloud/scc/assets/list | 6 + gcloud/scc/assets/list-marks | 6 + gcloud/scc/assets/run-discovery | 6 + gcloud/spanner/databases/execute-sql | 6 +- gcloud/sql/instances/create | 9 + gcloud/sql/instances/patch | 9 + gcloud/storage/buckets/describe | 6 +- gcloud/storage/buckets/list | 6 +- gcloud/storage/buckets/update | 4 +- gcloud/storage/du | 100 +++++ gcloud/storage/help | 9 + gcloud/storage/hmac/create | 35 ++ gcloud/storage/hmac/delete | 37 ++ gcloud/storage/hmac/describe | 37 ++ gcloud/storage/hmac/help | 37 ++ gcloud/storage/hmac/list | 80 ++++ gcloud/storage/hmac/update | 55 +++ gcloud/storage/objects/describe | 6 +- gcloud/storage/objects/list | 10 +- gcloud/storage/sign-url | 111 +++++ gcloud/vmware/private-clouds/clusters/update | 2 +- gcloud/workbench/help | 19 + gcloud/workbench/instances/help | 19 + .../instances}/list | 27 +- 325 files changed, 10090 insertions(+), 1806 deletions(-) create mode 100644 gcloud/alpha/builds/triggers/update/bitbucketserver create mode 100644 gcloud/alpha/builds/triggers/update/cloud-source-repositories create mode 100644 gcloud/alpha/builds/triggers/update/github create mode 100644 gcloud/alpha/builds/triggers/update/gitlab create mode 100644 gcloud/alpha/builds/triggers/update/help create mode 100644 gcloud/alpha/builds/triggers/update/manual create mode 100644 gcloud/alpha/builds/triggers/update/pubsub create mode 100644 gcloud/alpha/builds/triggers/update/webhook create mode 100644 gcloud/alpha/compute/interconnects/macsec/update-key delete mode 100644 gcloud/alpha/compute/os-config/guest-policies/create delete mode 100644 gcloud/alpha/compute/os-config/guest-policies/delete delete mode 100644 gcloud/alpha/compute/os-config/guest-policies/describe delete mode 100644 gcloud/alpha/compute/os-config/guest-policies/help delete mode 100644 gcloud/alpha/compute/os-config/guest-policies/lookup delete mode 100644 gcloud/alpha/compute/os-config/guest-policies/update delete mode 100644 gcloud/alpha/compute/os-config/patch-deployments/create delete mode 100644 gcloud/alpha/compute/os-config/patch-deployments/delete delete mode 100644 gcloud/alpha/compute/os-config/patch-deployments/describe delete mode 100644 gcloud/alpha/compute/os-config/patch-deployments/help delete mode 100644 gcloud/alpha/compute/os-config/patch-deployments/pause delete mode 100644 gcloud/alpha/compute/os-config/patch-deployments/resume delete mode 100644 gcloud/alpha/compute/os-config/patch-deployments/update delete mode 100644 gcloud/alpha/compute/os-config/patch-jobs/cancel delete mode 100644 gcloud/alpha/compute/os-config/patch-jobs/describe delete mode 100644 gcloud/alpha/compute/os-config/patch-jobs/execute delete mode 100644 gcloud/alpha/compute/os-config/patch-jobs/help create mode 100644 gcloud/alpha/container/fleet/fleetobservability/describe create mode 100644 gcloud/alpha/container/fleet/fleetobservability/disable create mode 100644 gcloud/alpha/container/fleet/fleetobservability/enable create mode 100644 gcloud/alpha/container/fleet/fleetobservability/help create mode 100644 gcloud/alpha/container/fleet/fleetobservability/update create mode 100644 gcloud/alpha/container/hub/fleetobservability/describe create mode 100644 gcloud/alpha/container/hub/fleetobservability/disable create mode 100644 gcloud/alpha/container/hub/fleetobservability/enable create mode 100644 gcloud/alpha/container/hub/fleetobservability/help create mode 100644 gcloud/alpha/container/hub/fleetobservability/update create mode 100644 gcloud/alpha/edge-cloud/container/get-server-config create mode 100644 gcloud/alpha/firestore/databases/delete create mode 100644 gcloud/alpha/infra-manager/deployments/apply create mode 100644 gcloud/alpha/infra-manager/deployments/delete create mode 100644 gcloud/alpha/infra-manager/deployments/describe create mode 100644 gcloud/alpha/infra-manager/deployments/help rename gcloud/alpha/{compute/os-config/patch-jobs/list-instance-details => infra-manager/deployments/list} (59%) create mode 100644 gcloud/alpha/infra-manager/help create mode 100644 gcloud/alpha/infra-manager/revisions/describe create mode 100644 gcloud/alpha/infra-manager/revisions/help rename gcloud/alpha/{compute/os-config/guest-policies => infra-manager/revisions}/list (54%) create mode 100644 gcloud/alpha/monitoring/policies/migrate create mode 100644 gcloud/alpha/storage/hmac/create create mode 100644 gcloud/alpha/storage/hmac/delete create mode 100644 gcloud/alpha/storage/hmac/describe create mode 100644 gcloud/alpha/storage/hmac/help rename gcloud/alpha/{compute/os-config/patch-jobs => storage/hmac}/list (60%) create mode 100644 gcloud/alpha/storage/hmac/update create mode 100644 gcloud/beta/builds/triggers/update/bitbucketserver create mode 100644 gcloud/beta/builds/triggers/update/cloud-source-repositories create mode 100644 gcloud/beta/builds/triggers/update/github create mode 100644 gcloud/beta/builds/triggers/update/gitlab create mode 100644 gcloud/beta/builds/triggers/update/help create mode 100644 gcloud/beta/builds/triggers/update/manual create mode 100644 gcloud/beta/builds/triggers/update/pubsub create mode 100644 gcloud/beta/builds/triggers/update/webhook create mode 100644 gcloud/beta/compute/interconnects/macsec/add-key create mode 100644 gcloud/beta/compute/interconnects/macsec/get-config create mode 100644 gcloud/beta/compute/interconnects/macsec/help create mode 100644 gcloud/beta/compute/interconnects/macsec/remove-key create mode 100644 gcloud/beta/compute/interconnects/macsec/update create mode 100644 gcloud/beta/compute/interconnects/macsec/update-key create mode 100644 gcloud/beta/container/fleet/fleetobservability/describe create mode 100644 gcloud/beta/container/fleet/fleetobservability/disable create mode 100644 gcloud/beta/container/fleet/fleetobservability/enable create mode 100644 gcloud/beta/container/fleet/fleetobservability/help create mode 100644 gcloud/beta/container/fleet/fleetobservability/update create mode 100644 gcloud/beta/container/hub/fleetobservability/describe create mode 100644 gcloud/beta/container/hub/fleetobservability/disable create mode 100644 gcloud/beta/container/hub/fleetobservability/enable create mode 100644 gcloud/beta/container/hub/fleetobservability/help create mode 100644 gcloud/beta/container/hub/fleetobservability/update create mode 100644 gcloud/builds/triggers/update/bitbucketserver create mode 100644 gcloud/builds/triggers/update/cloud-source-repositories create mode 100644 gcloud/builds/triggers/update/github create mode 100644 gcloud/builds/triggers/update/gitlab create mode 100644 gcloud/builds/triggers/update/help create mode 100644 gcloud/builds/triggers/update/manual create mode 100644 gcloud/builds/triggers/update/pubsub create mode 100644 gcloud/builds/triggers/update/webhook create mode 100644 gcloud/container/fleet/fleetobservability/describe create mode 100644 gcloud/container/fleet/fleetobservability/disable create mode 100644 gcloud/container/fleet/fleetobservability/enable create mode 100644 gcloud/container/fleet/fleetobservability/help create mode 100644 gcloud/container/fleet/fleetobservability/update create mode 100644 gcloud/container/hub/fleetobservability/describe create mode 100644 gcloud/container/hub/fleetobservability/disable create mode 100644 gcloud/container/hub/fleetobservability/enable create mode 100644 gcloud/container/hub/fleetobservability/help create mode 100644 gcloud/container/hub/fleetobservability/update create mode 100644 gcloud/storage/du create mode 100644 gcloud/storage/hmac/create create mode 100644 gcloud/storage/hmac/delete create mode 100644 gcloud/storage/hmac/describe create mode 100644 gcloud/storage/hmac/help create mode 100644 gcloud/storage/hmac/list create mode 100644 gcloud/storage/hmac/update create mode 100644 gcloud/storage/sign-url create mode 100644 gcloud/workbench/help create mode 100644 gcloud/workbench/instances/help rename gcloud/{alpha/compute/os-config/patch-deployments => workbench/instances}/list (73%) diff --git a/gcloud/_version b/gcloud/_version index aae989eac..23eb4d7ea 100644 --- a/gcloud/_version +++ b/gcloud/_version @@ -1,8 +1,8 @@ -Google Cloud SDK 438.0.0 -alpha 2023.07.07 -beta 2023.07.07 -bq 2.0.93 +Google Cloud SDK 439.0.0 +alpha 2023.07.14 +beta 2023.07.14 +bq 2.0.94 bundled-python3-unix 3.9.16 -core 2023.07.07 +core 2023.07.14 gcloud-crc32c 1.0.0 gsutil 5.25 diff --git a/gcloud/ai-platform/models/remove-iam-policy-binding b/gcloud/ai-platform/models/remove-iam-policy-binding index 7a1f35e7c..ada6ea8f7 100644 --- a/gcloud/ai-platform/models/remove-iam-policy-binding +++ b/gcloud/ai-platform/models/remove-iam-policy-binding @@ -25,7 +25,7 @@ EXAMPLES --member='allAuthenticatedUsers' --role='roles/ml.admin' See https://cloud.google.com/iam/docs/managing-policies for details of - policy role and principal types. + policy role and member types. POSITIONAL ARGUMENTS Model resource - The AI Platform model for which to remove IAM policy diff --git a/gcloud/alpha/ai-platform/models/remove-iam-policy-binding b/gcloud/alpha/ai-platform/models/remove-iam-policy-binding index 408576027..0a99ab2b3 100644 --- a/gcloud/alpha/ai-platform/models/remove-iam-policy-binding +++ b/gcloud/alpha/ai-platform/models/remove-iam-policy-binding @@ -30,7 +30,7 @@ EXAMPLES --role='roles/ml.admin' See https://cloud.google.com/iam/docs/managing-policies for details of - policy role and principal types. + policy role and member types. POSITIONAL ARGUMENTS Model resource - The AI Platform model for which to remove IAM policy diff --git a/gcloud/alpha/assured/workloads/create b/gcloud/alpha/assured/workloads/create index 49763171e..ae9bd323c 100644 --- a/gcloud/alpha/assured/workloads/create +++ b/gcloud/alpha/assured/workloads/create @@ -9,6 +9,7 @@ SYNOPSIS [--enable-sovereign-controls=ENABLE_SOVEREIGN_CONTROLS] [--external-identifier=EXTERNAL_IDENTIFIER] [--labels=[KEY=VALUE,...]] [--next-rotation-time=NEXT_ROTATION_TIME] [--partner=PARTNER] + [--partner-permissions=[KEY=VALUE,...]] [--provisioned-resources-parent=PROVISIONED_RESOURCES_PARENT] [--resource-settings=[KEY=VALUE,...]] [--rotation-period=ROTATION_PERIOD] [GCLOUD_WIDE_FLAG ...] @@ -86,6 +87,10 @@ OPTIONAL FLAGS partners. PARTNER must be one of: LOCAL_CONTROLS_BY_S3NS, SOVEREIGN_CONTROLS_BY_T_SYSTEMS. + --partner-permissions=[KEY=VALUE,...] + The partner permissions for the partner regime, for example, + data-logs-viewer=true/false + --provisioned-resources-parent=PROVISIONED_RESOURCES_PARENT The parent of the provisioned projects, for example, folders/{FOLDER_ID} diff --git a/gcloud/alpha/bigtable/instances/tables/update b/gcloud/alpha/bigtable/instances/tables/update index ebcc1c534..6a63ffd0d 100644 --- a/gcloud/alpha/bigtable/instances/tables/update +++ b/gcloud/alpha/bigtable/instances/tables/update @@ -83,7 +83,7 @@ FLAGS --clear-change-stream-retention-period This disables the change stream and eventually removes the change - stream data within your retention period. + stream data. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/alpha/builds/triggers/help b/gcloud/alpha/builds/triggers/help index 44cc822e8..caafaacca 100644 --- a/gcloud/alpha/builds/triggers/help +++ b/gcloud/alpha/builds/triggers/help @@ -22,6 +22,9 @@ GROUPS create (ALPHA) Create build triggers for Google Cloud Build. + update + (ALPHA) Update Triggers in Google Cloud Build. + COMMANDS COMMAND is one of the following: diff --git a/gcloud/alpha/builds/triggers/update/bitbucketserver b/gcloud/alpha/builds/triggers/update/bitbucketserver new file mode 100644 index 000000000..1e19112f5 --- /dev/null +++ b/gcloud/alpha/builds/triggers/update/bitbucketserver @@ -0,0 +1,255 @@ +NAME + gcloud alpha builds triggers update bitbucketserver - updates Bitbucket + Server trigger used by Google Cloud Build + +SYNOPSIS + gcloud alpha builds triggers update bitbucketserver + (TRIGGER : --region=REGION) + (--trigger-config=PATH + | --bitbucket-server-config-resource=BITBUCKET_SERVER_CONFIG_RESOURCE + --description=DESCRIPTION --ignored-files=[GLOB,...] + --included-files=[GLOB,...] --project-key=PROJECT_KEY + --repo-slug=REPO_SLUG --[no-]require-approval + --service-account=SERVICE_ACCOUNT --branch-pattern=REGEX + | --tag-pattern=REGEX | --comment-control=COMMENT_CONTROL; + default="COMMENTS_ENABLED" + --pull-request-pattern=REGEX --build-config=PATH + | --inline-config=PATH + | [--dockerfile=DOCKERFILE --dockerfile-image=DOCKERFILE_IMAGE + : --dockerfile-dir=DOCKERFILE_DIR] --clear-substitutions + | --remove-substitutions=[KEY,...] + | --update-substitutions=[KEY=VALUE,...]) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Updates Bitbucket Server trigger used by Google Cloud Build. + +EXAMPLES + To update the branch pattern of the trigger: + + $ gcloud alpha builds triggers update bitbucketserver my-trigger \ + --branch-pattern=".*" + + To update the build config of the trigger: + + $ gcloud alpha builds triggers update bitbucketserver my-trigger \ + --build-config="cloudbuild.yaml" + + To update the substitutions of the trigger: $ gcloud alpha builds triggers update bitbucketserver my-trigger \ + --update-substitutions=_REPO_NAME=my-repo,_BRANCH_NAME=master + +POSITIONAL ARGUMENTS + Trigger resource - Build Trigger. 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 TRIGGER 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. + + TRIGGER + ID of the trigger or fully qualified identifier for the trigger. + + To set the trigger attribute: + ▸ provide the argument TRIGGER 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 location for the trigger. + + To set the region attribute: + ▸ provide the argument TRIGGER on the command line with a fully + specified name; + ▸ provide the argument --region on the command line; + ▸ set the property builds/region. + +REQUIRED FLAGS + Exactly one of these must be specified: + + --trigger-config=PATH + Path to Build Trigger config file (JSON or YAML format). For more + details, see + https://cloud.google.com/cloud-build/docs/api/reference/rest/v1/projects.triggers#BuildTrigger + + Flag based trigger configuration + + --bitbucket-server-config-resource=BITBUCKET_SERVER_CONFIG_RESOURCE + Bitbucket Server config resource name. + + --description=DESCRIPTION + Build trigger description. + + --ignored-files=[GLOB,...] + Glob filter. Changes only affecting ignored files won't trigger + builds. + + --included-files=[GLOB,...] + Glob filter. Changes affecting at least one included file will + trigger builds. + + --project-key=PROJECT_KEY + Bitbucket Server project key. + + --repo-slug=REPO_SLUG + Bitbucket Server repository slug. + + --[no-]require-approval + Require manual approval for triggered builds. Use + --require-approval to enable and --no-require-approval to disable. + + --service-account=SERVICE_ACCOUNT + The service account used for all user-controlled operations + including UpdateBuildTrigger, RunBuildTrigger, CreateBuild, and + CancelBuild. If no service account is set, then the standard Cloud + Build service account ([PROJECT_NUM]@system.gserviceaccount.com) is + used instead. Format: + projects/{PROJECT_ID}/serviceAccounts/{ACCOUNT_ID_OR_EMAIL}. + + At most one of these can be specified: + + --branch-pattern=REGEX + A regular expression specifying which git branches to match. + + This pattern is used as a regular expression search for any + incoming pushes. For example, --branch-pattern=foo will match + "foo", "foobar", and "barfoo". Events on a branch that does not + match will be ignored. + + The syntax of the regular expressions accepted is the syntax + accepted by RE2 and described at + https://github.com/google/re2/wiki/Syntax. + + --tag-pattern=REGEX + A regular expression specifying which git tags to match. + + This pattern is used as a regular expression search for any + incoming pushes. For example, --tag-pattern=foo will match "foo", + "foobar", and "barfoo". Events on a tag that does not match will + be ignored. + + The syntax of the regular expressions accepted is the syntax + accepted by RE2 and described at + https://github.com/google/re2/wiki/Syntax. + + Pull Request settings + + --comment-control=COMMENT_CONTROL; default="COMMENTS_ENABLED" + Require a repository collaborator or owner to comment '/gcbrun' + on a pull request before running the build. COMMENT_CONTROL + must be one of: + + COMMENTS_DISABLED + Do not require comments on Pull Requests before builds are + triggered. + COMMENTS_ENABLED + Enforce that repository owners or collaborators must + comment on Pull Requests before builds are triggered. + COMMENTS_ENABLED_FOR_EXTERNAL_CONTRIBUTORS_ONLY + Enforce that repository owners or collaborators must + comment on external contributors' Pull Requests before + builds are triggered. + + --pull-request-pattern=REGEX + A regular expression specifying which base git branch to match + for pull request events. + + This pattern is used as a regular expression search for the + base branch (the branch you are trying to merge into) for pull + request updates. For example, --pull-request-pattern=foo will + match "foo", "foobar", and "barfoo". + + The syntax of the regular expressions accepted is the syntax + accepted by RE2 and described at + https://github.com/google/re2/wiki/Syntax. + + At most one of these can be specified: + + --build-config=PATH + Path to a YAML or JSON file containing the build configuration in + the repository. + + For more details, see: + https://cloud.google.com/cloud-build/docs/build-config + + --inline-config=PATH + Local path to a YAML or JSON file containing a build + configuration. + + Dockerfile build configuration flags + + --dockerfile=DOCKERFILE + Path of Dockerfile to use for builds in the repository. + + If specified, a build config will be generated to run docker + build using the specified file. + + The filename is relative to the Dockerfile directory. + + This flag argument must be specified if any of the other + arguments in this group are specified. + + --dockerfile-image=DOCKERFILE_IMAGE + Docker image name to build. + + This flag argument must be specified if any of the other + arguments in this group are specified. + + --dockerfile-dir=DOCKERFILE_DIR + Location of the directory containing the Dockerfile in the + repository. + + The directory will also be used as the Docker build context. + + At most one of these can be specified: + + --clear-substitutions + Clear existing substitutions. + + --remove-substitutions=[KEY,...] + Remove existing substitutions if present. + + --update-substitutions=[KEY=VALUE,...] + Update or add to existing substitutions. Substitutions are + parameters to be substituted or add in the build specification. + + For example (using some nonsensical substitution keys; all keys + must begin with an underscore): + + $ gcloud builds triggers update ... + --update-substitutions _FAVORITE_COLOR=blue,_NUM_CANDIES=10 + + This will add the provided substitutions to the existing + substitutions and results in a build where every occurrence of + ${_FAVORITE_COLOR} in certain fields is replaced by "blue", and + similarly for ${_NUM_CANDIES} and "10". + + Only the following built-in variables can be specified with the + --substitutions flag: REPO_NAME, BRANCH_NAME, TAG_NAME, + REVISION_ID, COMMIT_SHA, SHORT_SHA. + + For more details, see: + https://cloud.google.com/build/docs/build-config-file-schema#substitutions + +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 builds triggers update bitbucketserver + + $ gcloud beta builds triggers update bitbucketserver + diff --git a/gcloud/alpha/builds/triggers/update/cloud-source-repositories b/gcloud/alpha/builds/triggers/update/cloud-source-repositories new file mode 100644 index 000000000..3a2331fc1 --- /dev/null +++ b/gcloud/alpha/builds/triggers/update/cloud-source-repositories @@ -0,0 +1,229 @@ +NAME + gcloud alpha builds triggers update cloud-source-repositories - updates + Cloud Source Repositories trigger used by Google Cloud Build + +SYNOPSIS + gcloud alpha builds triggers update cloud-source-repositories + (TRIGGER : --region=REGION) + (--trigger-config=PATH | --description=DESCRIPTION + --ignored-files=[GLOB,...] --included-files=[GLOB,...] --repo=REPO + --[no-]require-approval + --service-account=SERVICE_ACCOUNT --branch-pattern=REGEX + | --tag-pattern=REGEX --build-config=PATH | --inline-config=PATH + | [--dockerfile=DOCKERFILE --dockerfile-image=DOCKERFILE_IMAGE + : --dockerfile-dir=DOCKERFILE_DIR] --clear-substitutions + | --remove-substitutions=[KEY,...] + | --update-substitutions=[KEY=VALUE,...]) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Updates Cloud Source Repositories trigger used by Google Cloud + Build. + +EXAMPLES + To update the branch pattern of the trigger: + + $ gcloud alpha builds triggers update cloud-source-repositories \ + my-trigger --branch-pattern=".*" + + To update the build config of the trigger: + + $ gcloud alpha builds triggers update cloud-source-repositories \ + my-trigger --build-config="cloudbuild.yaml" + + To update the substitutions of the trigger: + + $ gcloud alpha builds triggers update cloud-source-repositories \ + my-trigger \ + --update-substitutions=_REPO_NAME=my-repo,_BRANCH_NAME=master + +POSITIONAL ARGUMENTS + Trigger resource - Build Trigger. 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 TRIGGER 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. + + TRIGGER + ID of the trigger or fully qualified identifier for the trigger. + + To set the trigger attribute: + ▸ provide the argument TRIGGER 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 location for the trigger. + + To set the region attribute: + ▸ provide the argument TRIGGER on the command line with a fully + specified name; + ▸ provide the argument --region on the command line; + ▸ set the property builds/region. + +REQUIRED FLAGS + Exactly one of these must be specified: + + --trigger-config=PATH + Path to Build Trigger config file (JSON or YAML format). For more + details, see + https://cloud.google.com/cloud-build/docs/api/reference/rest/v1/projects.triggers#BuildTrigger + + Flag based trigger configuration + + --description=DESCRIPTION + Build trigger description. + + --ignored-files=[GLOB,...] + Glob filter. Changes only affecting ignored files won't trigger + builds. + + --included-files=[GLOB,...] + Glob filter. Changes affecting at least one included file will + trigger builds. + + Repo resource - Cloud Source Repository. 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 --repo on the command line with a fully + specified name; + ▫ set the property core/project. + + --repo=REPO + ID of the repo or fully qualified identifier for the repo. + + To set the repo attribute: + ◇ provide the argument --repo on the command line. + + --[no-]require-approval + Require manual approval for triggered builds. Use + --require-approval to enable and --no-require-approval to disable. + + --service-account=SERVICE_ACCOUNT + The service account used for all user-controlled operations + including UpdateBuildTrigger, RunBuildTrigger, CreateBuild, and + CancelBuild. If no service account is set, then the standard Cloud + Build service account ([PROJECT_NUM]@system.gserviceaccount.com) is + used instead. Format: + projects/{PROJECT_ID}/serviceAccounts/{ACCOUNT_ID_OR_EMAIL}. + + At most one of these can be specified: + + --branch-pattern=REGEX + A regular expression specifying which git branches to match. + + This pattern is used as a regular expression search for any + incoming pushes. For example, --branch-pattern=foo will match + "foo", "foobar", and "barfoo". Events on a branch that does not + match will be ignored. + + The syntax of the regular expressions accepted is the syntax + accepted by RE2 and described at + https://github.com/google/re2/wiki/Syntax. + + --tag-pattern=REGEX + A regular expression specifying which git tags to match. + + This pattern is used as a regular expression search for any + incoming pushes. For example, --tag-pattern=foo will match "foo", + "foobar", and "barfoo". Events on a tag that does not match will + be ignored. + + The syntax of the regular expressions accepted is the syntax + accepted by RE2 and described at + https://github.com/google/re2/wiki/Syntax. + + At most one of these can be specified: + + --build-config=PATH + Path to a YAML or JSON file containing the build configuration in + the repository. + + For more details, see: + https://cloud.google.com/cloud-build/docs/build-config + + --inline-config=PATH + Local path to a YAML or JSON file containing a build + configuration. + + Dockerfile build configuration flags + + --dockerfile=DOCKERFILE + Path of Dockerfile to use for builds in the repository. + + If specified, a build config will be generated to run docker + build using the specified file. + + The filename is relative to the Dockerfile directory. + + This flag argument must be specified if any of the other + arguments in this group are specified. + + --dockerfile-image=DOCKERFILE_IMAGE + Docker image name to build. + + This flag argument must be specified if any of the other + arguments in this group are specified. + + --dockerfile-dir=DOCKERFILE_DIR + Location of the directory containing the Dockerfile in the + repository. + + The directory will also be used as the Docker build context. + + At most one of these can be specified: + + --clear-substitutions + Clear existing substitutions. + + --remove-substitutions=[KEY,...] + Remove existing substitutions if present. + + --update-substitutions=[KEY=VALUE,...] + Update or add to existing substitutions. Substitutions are + parameters to be substituted or add in the build specification. + + For example (using some nonsensical substitution keys; all keys + must begin with an underscore): + + $ gcloud builds triggers update ... + --update-substitutions _FAVORITE_COLOR=blue,_NUM_CANDIES=10 + + This will add the provided substitutions to the existing + substitutions and results in a build where every occurrence of + ${_FAVORITE_COLOR} in certain fields is replaced by "blue", and + similarly for ${_NUM_CANDIES} and "10". + + Only the following built-in variables can be specified with the + --substitutions flag: REPO_NAME, BRANCH_NAME, TAG_NAME, + REVISION_ID, COMMIT_SHA, SHORT_SHA. + + For more details, see: + https://cloud.google.com/build/docs/build-config-file-schema#substitutions + +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 builds triggers update cloud-source-repositories + + $ gcloud beta builds triggers update cloud-source-repositories + diff --git a/gcloud/alpha/builds/triggers/update/github b/gcloud/alpha/builds/triggers/update/github new file mode 100644 index 000000000..fe74b1b32 --- /dev/null +++ b/gcloud/alpha/builds/triggers/update/github @@ -0,0 +1,270 @@ +NAME + gcloud alpha builds triggers update github - update GitHub trigger used by + Google Cloud Build + +SYNOPSIS + gcloud alpha builds triggers update github (TRIGGER : --region=REGION) + (--trigger-config=PATH | --description=DESCRIPTION + --ignored-files=[GLOB,...] --include-logs-with-status + --included-files=[GLOB,...] --[no-]require-approval + --service-account=SERVICE_ACCOUNT --branch-pattern=REGEX + | --tag-pattern=REGEX | --comment-control=COMMENT_CONTROL; + default="COMMENTS_ENABLED" + --pull-request-pattern=REGEX --build-config=PATH + | --inline-config=PATH + | [--dockerfile=DOCKERFILE --dockerfile-image=DOCKERFILE_IMAGE + : --dockerfile-dir=DOCKERFILE_DIR] --clear-substitutions + | --remove-substitutions=[KEY,...] + | --update-substitutions=[KEY=VALUE,...] --repository=REPOSITORY + | --enterprise-config=ENTERPRISE_CONFIG + --repo-name=REPO_NAME --repo-owner=REPO_OWNER) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Update GitHub trigger used by Google Cloud Build. + +EXAMPLES + To update the branch pattern of the trigger: + + $ gcloud alpha builds triggers update github my-trigger \ + --branch-pattern=".*" + + To update the build config of the trigger: + + $ gcloud alpha builds triggers update github my-trigger \ + --build-config="cloudbuild.yaml" + + To update the substitutions of the trigger: + + $ gcloud alpha builds triggers update github my-trigger \ + --update-substitutions=_REPO_NAME=my-repo,_BRANCH_NAME=master + +POSITIONAL ARGUMENTS + Trigger resource - Build Trigger. 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 TRIGGER 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. + + TRIGGER + ID of the trigger or fully qualified identifier for the trigger. + + To set the trigger attribute: + ▸ provide the argument TRIGGER 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 location for the trigger. + + To set the region attribute: + ▸ provide the argument TRIGGER on the command line with a fully + specified name; + ▸ provide the argument --region on the command line; + ▸ set the property builds/region. + +REQUIRED FLAGS + Exactly one of these must be specified: + + --trigger-config=PATH + Path to Build Trigger config file (JSON or YAML format). For more + details, see + https://cloud.google.com/cloud-build/docs/api/reference/rest/v1/projects.triggers#BuildTrigger + + Flag based trigger configuration + + --description=DESCRIPTION + Build trigger description. + + --ignored-files=[GLOB,...] + Glob filter. Changes only affecting ignored files won't trigger + builds. + + --include-logs-with-status + Build logs will be sent back to GitHub as part of the checkrun + result. + + --included-files=[GLOB,...] + Glob filter. Changes affecting at least one included file will + trigger builds. + + --[no-]require-approval + Require manual approval for triggered builds. Use + --require-approval to enable and --no-require-approval to disable. + + --service-account=SERVICE_ACCOUNT + The service account used for all user-controlled operations + including UpdateBuildTrigger, RunBuildTrigger, CreateBuild, and + CancelBuild. If no service account is set, then the standard Cloud + Build service account ([PROJECT_NUM]@system.gserviceaccount.com) is + used instead. Format: + projects/{PROJECT_ID}/serviceAccounts/{ACCOUNT_ID_OR_EMAIL}. + + At most one of these can be specified: + + --branch-pattern=REGEX + A regular expression specifying which git branches to match. + + This pattern is used as a regular expression search for any + incoming pushes. For example, --branch-pattern=foo will match + "foo", "foobar", and "barfoo". Events on a branch that does not + match will be ignored. + + The syntax of the regular expressions accepted is the syntax + accepted by RE2 and described at + https://github.com/google/re2/wiki/Syntax. + + --tag-pattern=REGEX + A regular expression specifying which git tags to match. + + This pattern is used as a regular expression search for any + incoming pushes. For example, --tag-pattern=foo will match "foo", + "foobar", and "barfoo". Events on a tag that does not match will + be ignored. + + The syntax of the regular expressions accepted is the syntax + accepted by RE2 and described at + https://github.com/google/re2/wiki/Syntax. + + Pull Request settings + + --comment-control=COMMENT_CONTROL; default="COMMENTS_ENABLED" + Require a repository collaborator or owner to comment '/gcbrun' + on a pull request before running the build. COMMENT_CONTROL + must be one of: + + COMMENTS_DISABLED + Do not require comments on Pull Requests before builds are + triggered. + COMMENTS_ENABLED + Enforce that repository owners or collaborators must + comment on Pull Requests before builds are triggered. + COMMENTS_ENABLED_FOR_EXTERNAL_CONTRIBUTORS_ONLY + Enforce that repository owners or collaborators must + comment on external contributors' Pull Requests before + builds are triggered. + + --pull-request-pattern=REGEX + A regular expression specifying which base git branch to match + for pull request events. + + This pattern is used as a regex search for the base branch (the + branch you are trying to merge into) for pull request updates. + For example, --pull-request-pattern=foo will match "foo", + "foobar", and "barfoo". + + The syntax of the regular expressions accepted is the syntax + accepted by RE2 and described at + https://github.com/google/re2/wiki/Syntax. + + At most one of these can be specified: + + --build-config=PATH + Path to a YAML or JSON file containing the build configuration in + the repository. + + For more details, see: + https://cloud.google.com/cloud-build/docs/build-config + + --inline-config=PATH + Local path to a YAML or JSON file containing a build + configuration. + + Dockerfile build configuration flags + + --dockerfile=DOCKERFILE + Path of Dockerfile to use for builds in the repository. + + If specified, a build config will be generated to run docker + build using the specified file. + + The filename is relative to the Dockerfile directory. + + This flag argument must be specified if any of the other + arguments in this group are specified. + + --dockerfile-image=DOCKERFILE_IMAGE + Docker image name to build. + + This flag argument must be specified if any of the other + arguments in this group are specified. + + --dockerfile-dir=DOCKERFILE_DIR + Location of the directory containing the Dockerfile in the + repository. + + The directory will also be used as the Docker build context. + + At most one of these can be specified: + + --clear-substitutions + Clear existing substitutions. + + --remove-substitutions=[KEY,...] + Remove existing substitutions if present. + + --update-substitutions=[KEY=VALUE,...] + Update or add to existing substitutions. Substitutions are + parameters to be substituted or add in the build specification. + + For example (using some nonsensical substitution keys; all keys + must begin with an underscore): + + $ gcloud builds triggers update ... + --update-substitutions _FAVORITE_COLOR=blue,_NUM_CANDIES=10 + + This will add the provided substitutions to the existing + substitutions and results in a build where every occurrence of + ${_FAVORITE_COLOR} in certain fields is replaced by "blue", and + similarly for ${_NUM_CANDIES} and "10". + + Only the following built-in variables can be specified with the + --substitutions flag: REPO_NAME, BRANCH_NAME, TAG_NAME, + REVISION_ID, COMMIT_SHA, SHORT_SHA. + + For more details, see: + https://cloud.google.com/build/docs/build-config-file-schema#substitutions + + At most one of these can be specified: + + --repository=REPOSITORY + Repository resource (2nd gen) to use, in the format + "projects/*/locations/*/connections/*/repositories/". + + --enterprise-config=ENTERPRISE_CONFIG + Resource name of the GitHub Enterprise config that should be + applied to this installation. + + For example: + "projects/{$project_id}/locations/{$location_id}/githubEnterpriseConfigs/{$config_id} + + --repo-name=REPO_NAME + Name of the GitHub Repository. + + --repo-owner=REPO_OWNER + Owner of the GitHub Repository. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +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 builds triggers update github + + $ gcloud beta builds triggers update github + diff --git a/gcloud/alpha/builds/triggers/update/gitlab b/gcloud/alpha/builds/triggers/update/gitlab new file mode 100644 index 000000000..874cf7f96 --- /dev/null +++ b/gcloud/alpha/builds/triggers/update/gitlab @@ -0,0 +1,254 @@ +NAME + gcloud alpha builds triggers update gitlab - updates GitLab trigger used by + Google Cloud Build + +SYNOPSIS + gcloud alpha builds triggers update gitlab (TRIGGER : --region=REGION) + (--trigger-config=PATH | --description=DESCRIPTION + --ignored-files=[GLOB,...] --included-files=[GLOB,...] + --repository=REPOSITORY --[no-]require-approval + --service-account=SERVICE_ACCOUNT --branch-pattern=REGEX + | --tag-pattern=REGEX | --comment-control=COMMENT_CONTROL + --pull-request-pattern=REGEX --build-config=PATH + | --inline-config=PATH + | [--dockerfile=DOCKERFILE --dockerfile-image=DOCKERFILE_IMAGE + : --dockerfile-dir=DOCKERFILE_DIR] --clear-substitutions + | --remove-substitutions=[KEY,...] + | --update-substitutions=[KEY=VALUE,...]) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Updates GitLab trigger used by Google Cloud Build. + +EXAMPLES + To update the branch pattern of the trigger: + + $ gcloud alpha builds triggers update gitlab my-trigger \ + --branch-pattern=".*" + + To update the build config of the trigger: + + $ gcloud alpha builds triggers update gitlab my-trigger \ + --build-config="cloudbuild.yaml" + + To update the substitutions of the trigger: + + $ gcloud alpha builds triggers update gitlab my-trigger \ + --update-substitutions=_REPO_NAME=my-repo,_BRANCH_NAME=master + + To update the 2nd-gen repository resource of the trigger: + + $ gcloud alpha builds triggers update gitlab my-trigger \ + --repository=projects/my-project/locations/us-west1/\ + connections/my-conn/repositories/my-repo + +POSITIONAL ARGUMENTS + Trigger resource - Build Trigger. 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 TRIGGER 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. + + TRIGGER + ID of the trigger or fully qualified identifier for the trigger. + + To set the trigger attribute: + ▸ provide the argument TRIGGER 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 location for the trigger. + + To set the region attribute: + ▸ provide the argument TRIGGER on the command line with a fully + specified name; + ▸ provide the argument --region on the command line; + ▸ set the property builds/region. + +REQUIRED FLAGS + Exactly one of these must be specified: + + --trigger-config=PATH + Path to Build Trigger config file (JSON or YAML format). For more + details, see + https://cloud.google.com/cloud-build/docs/api/reference/rest/v1/projects.triggers#BuildTrigger + + Flag based trigger configuration + + --description=DESCRIPTION + Build trigger description. + + --ignored-files=[GLOB,...] + Glob filter. Changes only affecting ignored files won't trigger + builds. + + --included-files=[GLOB,...] + Glob filter. Changes affecting at least one included file will + trigger builds. + + --repository=REPOSITORY + Repository resource (2nd gen) to use, in the format + "projects/*/locations/*/connections/*/repositories/". + + --[no-]require-approval + Require manual approval for triggered builds. Use + --require-approval to enable and --no-require-approval to disable. + + --service-account=SERVICE_ACCOUNT + The service account used for all user-controlled operations + including UpdateBuildTrigger, RunBuildTrigger, CreateBuild, and + CancelBuild. If no service account is set, then the standard Cloud + Build service account ([PROJECT_NUM]@system.gserviceaccount.com) is + used instead. Format: + projects/{PROJECT_ID}/serviceAccounts/{ACCOUNT_ID_OR_EMAIL}. + + At most one of these can be specified: + + --branch-pattern=REGEX + A regular expression specifying which git branches to match. + + This pattern is used as a regular expression search for any + incoming pushes. For example, --branch-pattern=foo will match + "foo", "foobar", and "barfoo". Events on a branch that does not + match will be ignored. + + The syntax of the regular expressions accepted is the syntax + accepted by RE2 and described at + https://github.com/google/re2/wiki/Syntax. + + --tag-pattern=REGEX + A regular expression specifying which git tags to match. + + This pattern is used as a regular expression search for any + incoming pushes. For example, --tag-pattern=foo will match "foo", + "foobar", and "barfoo". Events on a tag that does not match will + be ignored. + + The syntax of the regular expressions accepted is the syntax + accepted by RE2 and described at + https://github.com/google/re2/wiki/Syntax. + + Pull Request settings + + --comment-control=COMMENT_CONTROL + Require a repository collaborator or owner to comment '/gcbrun' + on a pull request before running the build. COMMENT_CONTROL + must be one of: + + COMMENTS_DISABLED + Do not require comments on Pull Requests before builds are + triggered. + COMMENTS_ENABLED + Enforce that repository owners or collaborators must + comment on Pull Requests before builds are triggered. + COMMENTS_ENABLED_FOR_EXTERNAL_CONTRIBUTORS_ONLY + Enforce that repository owners or collaborators must + comment on external contributors' Pull Requests before + builds are triggered. + + --pull-request-pattern=REGEX + A regular expression specifying which base git branch to match + for pull request events. + + This pattern is used as a regular expression search for the + base branch (the branch you are trying to merge into) for pull + request updates. For example, --pull-request-pattern=foo will + match "foo", "foobar", and "barfoo". + + The syntax of the regular expressions accepted is the syntax + accepted by RE2 and described at + https://github.com/google/re2/wiki/Syntax. + + At most one of these can be specified: + + --build-config=PATH + Path to a YAML or JSON file containing the build configuration in + the repository. + + For more details, see: + https://cloud.google.com/cloud-build/docs/build-config + + --inline-config=PATH + Local path to a YAML or JSON file containing a build + configuration. + + Dockerfile build configuration flags + + --dockerfile=DOCKERFILE + Path of Dockerfile to use for builds in the repository. + + If specified, a build config will be generated to run docker + build using the specified file. + + The filename is relative to the Dockerfile directory. + + This flag argument must be specified if any of the other + arguments in this group are specified. + + --dockerfile-image=DOCKERFILE_IMAGE + Docker image name to build. + + This flag argument must be specified if any of the other + arguments in this group are specified. + + --dockerfile-dir=DOCKERFILE_DIR + Location of the directory containing the Dockerfile in the + repository. + + The directory will also be used as the Docker build context. + + At most one of these can be specified: + + --clear-substitutions + Clear existing substitutions. + + --remove-substitutions=[KEY,...] + Remove existing substitutions if present. + + --update-substitutions=[KEY=VALUE,...] + Update or add to existing substitutions. Substitutions are + parameters to be substituted or add in the build specification. + + For example (using some nonsensical substitution keys; all keys + must begin with an underscore): + + $ gcloud builds triggers update ... + --update-substitutions _FAVORITE_COLOR=blue,_NUM_CANDIES=10 + + This will add the provided substitutions to the existing + substitutions and results in a build where every occurrence of + ${_FAVORITE_COLOR} in certain fields is replaced by "blue", and + similarly for ${_NUM_CANDIES} and "10". + + Only the following built-in variables can be specified with the + --substitutions flag: REPO_NAME, BRANCH_NAME, TAG_NAME, + REVISION_ID, COMMIT_SHA, SHORT_SHA. + + For more details, see: + https://cloud.google.com/build/docs/build-config-file-schema#substitutions + +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 builds triggers update gitlab + + $ gcloud beta builds triggers update gitlab + diff --git a/gcloud/alpha/builds/triggers/update/help b/gcloud/alpha/builds/triggers/update/help new file mode 100644 index 000000000..5f5bded8c --- /dev/null +++ b/gcloud/alpha/builds/triggers/update/help @@ -0,0 +1,49 @@ +NAME + gcloud alpha builds triggers update - update Triggers in Google Cloud Build + +SYNOPSIS + gcloud alpha builds triggers update COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Update Triggers in Google Cloud Build. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + bitbucketserver + (ALPHA) Updates Bitbucket Server trigger used by Google Cloud Build. + + cloud-source-repositories + (ALPHA) Updates Cloud Source Repositories trigger used by Google Cloud + Build. + + github + (ALPHA) Update GitHub trigger used by Google Cloud Build. + + gitlab + (ALPHA) Updates GitLab trigger used by Google Cloud Build. + + manual + (ALPHA) Updates a manual trigger used by Google Cloud Build. + + pubsub + (ALPHA) Update a Pub/Sub trigger used by Google Cloud Build. + + webhook + (ALPHA) Update a Webhook trigger used by Google Cloud Build. + +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 builds triggers update + + $ gcloud beta builds triggers update + diff --git a/gcloud/alpha/builds/triggers/update/manual b/gcloud/alpha/builds/triggers/update/manual new file mode 100644 index 000000000..5b0d322ae --- /dev/null +++ b/gcloud/alpha/builds/triggers/update/manual @@ -0,0 +1,228 @@ +NAME + gcloud alpha builds triggers update manual - updates a manual trigger used + by Google Cloud Build + +SYNOPSIS + gcloud alpha builds triggers update manual (TRIGGER : --region=REGION) + (--trigger-config=PATH | --description=DESCRIPTION + --[no-]require-approval + --service-account=SERVICE_ACCOUNT --clear-substitutions + | --remove-substitutions=[KEY,...] + | --update-substitutions=[KEY=VALUE,...] --inline-config=PATH + | [--dockerfile=DOCKERFILE : --dockerfile-dir=DOCKERFILE_DIR + --dockerfile-image=DOCKERFILE_IMAGE] + | --git-file-source-branch=GIT_FILE_SOURCE_BRANCH + | --git-file-source-tag=GIT_FILE_SOURCE_TAG + --git-file-source-github-enterprise-config=GIT_FILE_SOURCE_GITHUB_ENTERPRISE_CONFIG --git-file-source-path=PATH --git-file-source-repo-type=GIT_FILE_SOURCE_REPO_TYPE --git-file-source-uri=URL --source-to-build-branch=SOURCE_TO_BUILD_BRANCH | --source-to-build-tag=SOURCE_TO_BUILD_TAG --source-to-build-github-enterprise-config=SOURCE_TO_BUILD_GITHUB_ENTERPRISE_CONFIG --source-to-build-repo-type=SOURCE_TO_BUILD_REPO_TYPE --source-to-build-uri=SOURCE_TO_BUILD_URI) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Updates a manual trigger used by Google Cloud Build. + +EXAMPLES + To update the branch from which the trigger clones: + + $ gcloud alpha builds triggers update manual my-trigger \ + --source-to-build-branch=my-branch + +POSITIONAL ARGUMENTS + Trigger resource - Build Trigger. 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 TRIGGER 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. + + TRIGGER + ID of the trigger or fully qualified identifier for the trigger. + + To set the trigger attribute: + ▸ provide the argument TRIGGER 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 location for the trigger. + + To set the region attribute: + ▸ provide the argument TRIGGER on the command line with a fully + specified name; + ▸ provide the argument --region on the command line; + ▸ set the property builds/region. + +REQUIRED FLAGS + Exactly one of these must be specified: + + --trigger-config=PATH + Path to Build Trigger config file (JSON or YAML format). For more + details, see + https://cloud.google.com/cloud-build/docs/api/reference/rest/v1/projects.triggers#BuildTrigger + + Flag based trigger configuration + + --description=DESCRIPTION + Build trigger description. + + --[no-]require-approval + Require manual approval for triggered builds. Use + --require-approval to enable and --no-require-approval to disable. + + --service-account=SERVICE_ACCOUNT + The service account used for all user-controlled operations + including UpdateBuildTrigger, RunBuildTrigger, CreateBuild, and + CancelBuild. If no service account is set, then the standard Cloud + Build service account ([PROJECT_NUM]@system.gserviceaccount.com) is + used instead. Format: + projects/{PROJECT_ID}/serviceAccounts/{ACCOUNT_ID_OR_EMAIL}. + + At most one of these can be specified: + + --clear-substitutions + Clear existing substitutions. + + --remove-substitutions=[KEY,...] + Remove existing substitutions if present. + + --update-substitutions=[KEY=VALUE,...] + Update or add to existing substitutions. Substitutions are + parameters to be substituted or add in the build specification. + + For example (using some nonsensical substitution keys; all keys + must begin with an underscore): + + $ gcloud builds triggers update ... + --update-substitutions _FAVORITE_COLOR=blue,_NUM_CANDIES=10 + + This will add the provided substitutions to the existing + substitutions and results in a build where every occurrence of + ${_FAVORITE_COLOR} in certain fields is replaced by "blue", and + similarly for ${_NUM_CANDIES} and "10". + + Only the following built-in variables can be specified with the + --substitutions flag: REPO_NAME, BRANCH_NAME, TAG_NAME, + REVISION_ID, COMMIT_SHA, SHORT_SHA. + + For more details, see: + https://cloud.google.com/build/docs/build-config-file-schema#substitutions + + At most one of these can be specified: + + --inline-config=PATH + Local path to a YAML or JSON file containing a build + configuration. + + Dockerfile build configuration flags + + --dockerfile=DOCKERFILE + Path of Dockerfile to use for builds in the repository. + + If specified, a build config will be generated to run docker + build using the specified file. + + The filename is relative to the Dockerfile directory. + + This flag argument must be specified if any of the other + arguments in this group are specified. + + --dockerfile-dir=DOCKERFILE_DIR + Location of the directory containing the Dockerfile in the + repository. + + The directory will also be used as the Docker build context. + + --dockerfile-image=DOCKERFILE_IMAGE + Docker image name to build. + + If not specified, + gcr.io/PROJECT/github.com/REPO_OWNER/REPO_NAME:$COMMIT_SHA will + be used. + + Use a build configuration (cloudbuild.yaml) file for building + multiple images in a single trigger. + + Build file source flags + + At most one of these can be specified: + + --git-file-source-branch=GIT_FILE_SOURCE_BRANCH + The branch of the repository to clone when trigger is + invoked. + + --git-file-source-tag=GIT_FILE_SOURCE_TAG + The tag of the repository to clone when trigger is invoked. + + At most one of these can be specified: + + --git-file-source-github-enterprise-config=GIT_FILE_SOURCE_GITHUB_ENTERPRISE_CONFIG + The resource name of the GitHub Enterprise config that should + be applied to this source. + + --git-file-source-path=PATH + The file in the repository to clone when trigger is invoked. + + --git-file-source-repo-type=GIT_FILE_SOURCE_REPO_TYPE + The type of the repository to clone when trigger is invoked. + + This flag argument must be specified if any of the other + arguments in this group are specified. + + --git-file-source-uri=URL + The URI of the repository to clone when trigger is invoked. + + 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: + + --source-to-build-branch=SOURCE_TO_BUILD_BRANCH + Branch to build. + + --source-to-build-tag=SOURCE_TO_BUILD_TAG + Tag to build. + + At most one of these can be specified: + + --source-to-build-github-enterprise-config=SOURCE_TO_BUILD_GITHUB_ENTERPRISE_CONFIG + The resource name of the GitHub Enterprise config that should be + applied to this source (1st gen). Format: + projects/{project}/locations/{location}/githubEnterpriseConfigs/{id} + or projects/{project}/githubEnterpriseConfigs/{id} + + --source-to-build-repo-type=SOURCE_TO_BUILD_REPO_TYPE + Type of the repository (1st gen). Currently only GitHub and Cloud + Source Repository types are supported. + + This flag argument must be specified if any of the other + arguments in this group are specified. + + --source-to-build-uri=SOURCE_TO_BUILD_URI + The URI of the repository that should be applied to this source + (1st gen). + + 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 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 builds triggers update manual + + $ gcloud beta builds triggers update manual + diff --git a/gcloud/alpha/builds/triggers/update/pubsub b/gcloud/alpha/builds/triggers/update/pubsub new file mode 100644 index 000000000..18c9302eb --- /dev/null +++ b/gcloud/alpha/builds/triggers/update/pubsub @@ -0,0 +1,245 @@ +NAME + gcloud alpha builds triggers update pubsub - update a Pub/Sub trigger used + by Google Cloud Build + +SYNOPSIS + gcloud alpha builds triggers update pubsub (TRIGGER : --region=REGION) + (--trigger-config=PATH | --description=DESCRIPTION + --[no-]require-approval --service-account=SERVICE_ACCOUNT + --subscription-filter=SUBSCRIPTION_FILTER + --topic=TOPIC --clear-substitutions + | --remove-substitutions=[KEY,...] + | --update-substitutions=[KEY=VALUE,...] --inline-config=PATH + | [--dockerfile=DOCKERFILE : --dockerfile-dir=DOCKERFILE_DIR + --dockerfile-image=DOCKERFILE_IMAGE] + | --git-file-source-branch=GIT_FILE_SOURCE_BRANCH + | --git-file-source-tag=GIT_FILE_SOURCE_TAG + --git-file-source-github-enterprise-config=GIT_FILE_SOURCE_GITHUB_ENTERPRISE_CONFIG --git-file-source-path=PATH --git-file-source-repo-type=GIT_FILE_SOURCE_REPO_TYPE --git-file-source-uri=URL --source-to-build-branch=SOURCE_TO_BUILD_BRANCH | --source-to-build-tag=SOURCE_TO_BUILD_TAG --source-to-build-github-enterprise-config=SOURCE_TO_BUILD_GITHUB_ENTERPRISE_CONFIG --source-to-build-repo-type=SOURCE_TO_BUILD_REPO_TYPE --source-to-build-uri=SOURCE_TO_BUILD_URI) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Update a Pub/Sub trigger used by Google Cloud Build. + +EXAMPLES + To update the branch from which the trigger clones: + + $ gcloud alpha builds triggers update pubsub my-trigger \ + --source-to-build-branch=my-branch + + To update the topic: + + $ gcloud alpha builds triggers update pubsub my-trigger \ + --topic=projects/my-project/topics/my-topic + + To update the substitutions of the trigger: $ gcloud alpha builds triggers update pubsub my-trigger \ + --update-substitutions=_REPO_NAME=my-repo,_BRANCH_NAME=master + +POSITIONAL ARGUMENTS + Trigger resource - Build Trigger. 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 TRIGGER 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. + + TRIGGER + ID of the trigger or fully qualified identifier for the trigger. + + To set the trigger attribute: + ▸ provide the argument TRIGGER 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 location for the trigger. + + To set the region attribute: + ▸ provide the argument TRIGGER on the command line with a fully + specified name; + ▸ provide the argument --region on the command line; + ▸ set the property builds/region. + +REQUIRED FLAGS + Exactly one of these must be specified: + + --trigger-config=PATH + Path to Build Trigger config file (JSON or YAML format). For more + details, see + https://cloud.google.com/cloud-build/docs/api/reference/rest/v1/projects.triggers#BuildTrigger + + Flag based trigger configuration + + --description=DESCRIPTION + Build trigger description. + + --[no-]require-approval + Require manual approval for triggered builds. Use + --require-approval to enable and --no-require-approval to disable. + + --service-account=SERVICE_ACCOUNT + The service account used for all user-controlled operations + including UpdateBuildTrigger, RunBuildTrigger, CreateBuild, and + CancelBuild. If no service account is set, then the standard Cloud + Build service account ([PROJECT_NUM]@system.gserviceaccount.com) is + used instead. Format: + projects/{PROJECT_ID}/serviceAccounts/{ACCOUNT_ID_OR_EMAIL}. + + --subscription-filter=SUBSCRIPTION_FILTER + CEL filter expression for the trigger. See + https://cloud.google.com/build/docs/filter-build-events-using-cel + for more details. + + --topic=TOPIC + The topic to which this trigger should subscribe. + + At most one of these can be specified: + + --clear-substitutions + Clear existing substitutions. + + --remove-substitutions=[KEY,...] + Remove existing substitutions if present. + + --update-substitutions=[KEY=VALUE,...] + Update or add to existing substitutions. Substitutions are + parameters to be substituted or add in the build specification. + + For example (using some nonsensical substitution keys; all keys + must begin with an underscore): + + $ gcloud builds triggers update ... + --update-substitutions _FAVORITE_COLOR=blue,_NUM_CANDIES=10 + + This will add the provided substitutions to the existing + substitutions and results in a build where every occurrence of + ${_FAVORITE_COLOR} in certain fields is replaced by "blue", and + similarly for ${_NUM_CANDIES} and "10". + + Only the following built-in variables can be specified with the + --substitutions flag: REPO_NAME, BRANCH_NAME, TAG_NAME, + REVISION_ID, COMMIT_SHA, SHORT_SHA. + + For more details, see: + https://cloud.google.com/build/docs/build-config-file-schema#substitutions + + At most one of these can be specified: + + --inline-config=PATH + Local path to a YAML or JSON file containing a build + configuration. + + Dockerfile build configuration flags + + --dockerfile=DOCKERFILE + Path of Dockerfile to use for builds in the repository. + + If specified, a build config will be generated to run docker + build using the specified file. + + The filename is relative to the Dockerfile directory. + + This flag argument must be specified if any of the other + arguments in this group are specified. + + --dockerfile-dir=DOCKERFILE_DIR + Location of the directory containing the Dockerfile in the + repository. + + The directory will also be used as the Docker build context. + + --dockerfile-image=DOCKERFILE_IMAGE + Docker image name to build. + + If not specified, + gcr.io/PROJECT/github.com/REPO_OWNER/REPO_NAME:$COMMIT_SHA will + be used. + + Use a build configuration (cloudbuild.yaml) file for building + multiple images in a single trigger. + + Build file source flags + + At most one of these can be specified: + + --git-file-source-branch=GIT_FILE_SOURCE_BRANCH + The branch of the repository to clone when trigger is + invoked. + + --git-file-source-tag=GIT_FILE_SOURCE_TAG + The tag of the repository to clone when trigger is invoked. + + At most one of these can be specified: + + --git-file-source-github-enterprise-config=GIT_FILE_SOURCE_GITHUB_ENTERPRISE_CONFIG + The resource name of the GitHub Enterprise config that should + be applied to this source. + + --git-file-source-path=PATH + The file in the repository to clone when trigger is invoked. + + --git-file-source-repo-type=GIT_FILE_SOURCE_REPO_TYPE + The type of the repository to clone when trigger is invoked. + + This flag argument must be specified if any of the other + arguments in this group are specified. + + --git-file-source-uri=URL + The URI of the repository to clone when trigger is invoked. + + 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: + + --source-to-build-branch=SOURCE_TO_BUILD_BRANCH + Branch to build. + + --source-to-build-tag=SOURCE_TO_BUILD_TAG + Tag to build. + + At most one of these can be specified: + + --source-to-build-github-enterprise-config=SOURCE_TO_BUILD_GITHUB_ENTERPRISE_CONFIG + The resource name of the GitHub Enterprise config that should be + applied to this source (1st gen). Format: + projects/{project}/locations/{location}/githubEnterpriseConfigs/{id} + or projects/{project}/githubEnterpriseConfigs/{id} + + --source-to-build-repo-type=SOURCE_TO_BUILD_REPO_TYPE + Type of the repository (1st gen). Currently only GitHub and Cloud + Source Repository types are supported. + + This flag argument must be specified if any of the other + arguments in this group are specified. + + --source-to-build-uri=SOURCE_TO_BUILD_URI + The URI of the repository that should be applied to this source + (1st gen). + + 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 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 builds triggers update pubsub + + $ gcloud beta builds triggers update pubsub + diff --git a/gcloud/alpha/builds/triggers/update/webhook b/gcloud/alpha/builds/triggers/update/webhook new file mode 100644 index 000000000..23b42eb92 --- /dev/null +++ b/gcloud/alpha/builds/triggers/update/webhook @@ -0,0 +1,247 @@ +NAME + gcloud alpha builds triggers update webhook - update a Webhook trigger used + by Google Cloud Build + +SYNOPSIS + gcloud alpha builds triggers update webhook (TRIGGER : --region=REGION) + (--trigger-config=PATH | --description=DESCRIPTION + --[no-]require-approval --secret=SECRET + --service-account=SERVICE_ACCOUNT + --subscription-filter=SUBSCRIPTION_FILTER --clear-substitutions + | --remove-substitutions=[KEY,...] + | --update-substitutions=[KEY=VALUE,...] --inline-config=PATH + | [--dockerfile=DOCKERFILE : --dockerfile-dir=DOCKERFILE_DIR + --dockerfile-image=DOCKERFILE_IMAGE] + | --git-file-source-branch=GIT_FILE_SOURCE_BRANCH + | --git-file-source-tag=GIT_FILE_SOURCE_TAG + --git-file-source-github-enterprise-config=GIT_FILE_SOURCE_GITHUB_ENTERPRISE_CONFIG --git-file-source-path=PATH --git-file-source-repo-type=GIT_FILE_SOURCE_REPO_TYPE --git-file-source-uri=URL --source-to-build-branch=SOURCE_TO_BUILD_BRANCH | --source-to-build-tag=SOURCE_TO_BUILD_TAG --source-to-build-github-enterprise-config=SOURCE_TO_BUILD_GITHUB_ENTERPRISE_CONFIG --source-to-build-repo-type=SOURCE_TO_BUILD_REPO_TYPE --source-to-build-uri=SOURCE_TO_BUILD_URI) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Update a Webhook trigger used by Google Cloud Build. + +EXAMPLES + To update the branch from which the trigger clones: + + $ gcloud alpha builds triggers update webhook my-webhook-trigger \ + --source-to-build-branch=my-branch + + To update the webhook secret: + + $ gcloud alpha builds triggers update webhook my-webhook-trigger \ + --secret=projects/my-project/secrets/my-secret/versions/2 + + To update the substitutions of the trigger: $ gcloud alpha builds triggers update webhook my-trigger \ + --update-substitutions=_REPO_NAME=my-repo,_BRANCH_NAME=master + +POSITIONAL ARGUMENTS + Trigger resource - Build Trigger. 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 TRIGGER 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. + + TRIGGER + ID of the trigger or fully qualified identifier for the trigger. + + To set the trigger attribute: + ▸ provide the argument TRIGGER 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 location for the trigger. + + To set the region attribute: + ▸ provide the argument TRIGGER on the command line with a fully + specified name; + ▸ provide the argument --region on the command line; + ▸ set the property builds/region. + +REQUIRED FLAGS + Exactly one of these must be specified: + + --trigger-config=PATH + Path to Build Trigger config file (JSON or YAML format). For more + details, see + https://cloud.google.com/cloud-build/docs/api/reference/rest/v1/projects.triggers#BuildTrigger + + Flag based trigger configuration + + --description=DESCRIPTION + Build trigger description. + + --[no-]require-approval + Require manual approval for triggered builds. Use + --require-approval to enable and --no-require-approval to disable. + + --secret=SECRET + The full path of the secret version required to validate webhook + requests against this trigger. For example, + projects/my-project/secrets/my-secret/versions/1. + + --service-account=SERVICE_ACCOUNT + The service account used for all user-controlled operations + including UpdateBuildTrigger, RunBuildTrigger, CreateBuild, and + CancelBuild. If no service account is set, then the standard Cloud + Build service account ([PROJECT_NUM]@system.gserviceaccount.com) is + used instead. Format: + projects/{PROJECT_ID}/serviceAccounts/{ACCOUNT_ID_OR_EMAIL}. + + --subscription-filter=SUBSCRIPTION_FILTER + CEL filter expression for the trigger. See + https://cloud.google.com/build/docs/filter-build-events-using-cel + for more details. + + At most one of these can be specified: + + --clear-substitutions + Clear existing substitutions. + + --remove-substitutions=[KEY,...] + Remove existing substitutions if present. + + --update-substitutions=[KEY=VALUE,...] + Update or add to existing substitutions. Substitutions are + parameters to be substituted or add in the build specification. + + For example (using some nonsensical substitution keys; all keys + must begin with an underscore): + + $ gcloud builds triggers update ... + --update-substitutions _FAVORITE_COLOR=blue,_NUM_CANDIES=10 + + This will add the provided substitutions to the existing + substitutions and results in a build where every occurrence of + ${_FAVORITE_COLOR} in certain fields is replaced by "blue", and + similarly for ${_NUM_CANDIES} and "10". + + Only the following built-in variables can be specified with the + --substitutions flag: REPO_NAME, BRANCH_NAME, TAG_NAME, + REVISION_ID, COMMIT_SHA, SHORT_SHA. + + For more details, see: + https://cloud.google.com/build/docs/build-config-file-schema#substitutions + + At most one of these can be specified: + + --inline-config=PATH + Local path to a YAML or JSON file containing a build + configuration. + + Dockerfile build configuration flags + + --dockerfile=DOCKERFILE + Path of Dockerfile to use for builds in the repository. + + If specified, a build config will be generated to run docker + build using the specified file. + + The filename is relative to the Dockerfile directory. + + This flag argument must be specified if any of the other + arguments in this group are specified. + + --dockerfile-dir=DOCKERFILE_DIR + Location of the directory containing the Dockerfile in the + repository. + + The directory will also be used as the Docker build context. + + --dockerfile-image=DOCKERFILE_IMAGE + Docker image name to build. + + If not specified, + gcr.io/PROJECT/github.com/REPO_OWNER/REPO_NAME:$COMMIT_SHA will + be used. + + Use a build configuration (cloudbuild.yaml) file for building + multiple images in a single trigger. + + Build file source flags + + At most one of these can be specified: + + --git-file-source-branch=GIT_FILE_SOURCE_BRANCH + The branch of the repository to clone when trigger is + invoked. + + --git-file-source-tag=GIT_FILE_SOURCE_TAG + The tag of the repository to clone when trigger is invoked. + + At most one of these can be specified: + + --git-file-source-github-enterprise-config=GIT_FILE_SOURCE_GITHUB_ENTERPRISE_CONFIG + The resource name of the GitHub Enterprise config that should + be applied to this source. + + --git-file-source-path=PATH + The file in the repository to clone when trigger is invoked. + + --git-file-source-repo-type=GIT_FILE_SOURCE_REPO_TYPE + The type of the repository to clone when trigger is invoked. + + This flag argument must be specified if any of the other + arguments in this group are specified. + + --git-file-source-uri=URL + The URI of the repository to clone when trigger is invoked. + + 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: + + --source-to-build-branch=SOURCE_TO_BUILD_BRANCH + Branch to build. + + --source-to-build-tag=SOURCE_TO_BUILD_TAG + Tag to build. + + At most one of these can be specified: + + --source-to-build-github-enterprise-config=SOURCE_TO_BUILD_GITHUB_ENTERPRISE_CONFIG + The resource name of the GitHub Enterprise config that should be + applied to this source (1st gen). Format: + projects/{project}/locations/{location}/githubEnterpriseConfigs/{id} + or projects/{project}/githubEnterpriseConfigs/{id} + + --source-to-build-repo-type=SOURCE_TO_BUILD_REPO_TYPE + Type of the repository (1st gen). Currently only GitHub and Cloud + Source Repository types are supported. + + This flag argument must be specified if any of the other + arguments in this group are specified. + + --source-to-build-uri=SOURCE_TO_BUILD_URI + The URI of the repository that should be applied to this source + (1st gen). + + 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 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 builds triggers update webhook + + $ gcloud beta builds triggers update webhook + diff --git a/gcloud/alpha/compute/commitments/create b/gcloud/alpha/compute/commitments/create index 47793f65d..eb82c491a 100644 --- a/gcloud/alpha/compute/commitments/create +++ b/gcloud/alpha/compute/commitments/create @@ -98,11 +98,11 @@ OPTIONAL FLAGS --type=TYPE; default="general-purpose" Type of commitment. memory-optimized indicates that the commitment is for memory-optimized VMs. TYPE must be one of: accelerator-optimized, - compute-optimized, compute-optimized-c2d, compute-optimized-c3, - compute-optimized-c3d, compute-optimized-h3, general-purpose, - general-purpose-e2, general-purpose-n2, general-purpose-n2d, - general-purpose-t2d, graphics-optimized, memory-optimized, - memory-optimized-m3. + accelerator-optimized-a3, compute-optimized, compute-optimized-c2d, + compute-optimized-c3, compute-optimized-c3d, compute-optimized-h3, + general-purpose, general-purpose-e2, general-purpose-n2, + general-purpose-n2d, general-purpose-t2d, graphics-optimized, + memory-optimized, memory-optimized-m3. Manage the reservations to be created with the commitment. diff --git a/gcloud/alpha/compute/firewall-policies/rules/create b/gcloud/alpha/compute/firewall-policies/rules/create index 4a74424da..3b08e47bd 100644 --- a/gcloud/alpha/compute/firewall-policies/rules/create +++ b/gcloud/alpha/compute/firewall-policies/rules/create @@ -19,7 +19,7 @@ SYNOPSIS [--src-threat-intelligence=[SOURCE_THREAT_INTELLIGENCE_LISTS,...]] [--target-resources=[TARGET_RESOURCES,...]] [--target-service-accounts=[TARGET_SERVICE_ACCOUNTS,...]] - [GCLOUD_WIDE_FLAG ...] + [--[no-]tls-inspect] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) gcloud alpha compute firewall-policies rules create is used to @@ -131,6 +131,12 @@ OPTIONAL FLAGS --target-service-accounts=[TARGET_SERVICE_ACCOUNTS,...] List of target service accounts for the rule. + --[no-]tls-inspect + Use this flag to indicate whether TLS traffic should be inspected using + the TLS inspection policy when the security profile group is applied. + Default: no TLS inspection. Use --tls-inspect to enable and + --no-tls-inspect to disable. + GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, diff --git a/gcloud/alpha/compute/firewall-policies/rules/update b/gcloud/alpha/compute/firewall-policies/rules/update index 11e5033b4..8d03bd0d1 100644 --- a/gcloud/alpha/compute/firewall-policies/rules/update +++ b/gcloud/alpha/compute/firewall-policies/rules/update @@ -20,7 +20,7 @@ SYNOPSIS [--src-threat-intelligence=[SOURCE_THREAT_INTELLIGENCE_LISTS,...]] [--target-resources=[TARGET_RESOURCES,...]] [--target-service-accounts=[TARGET_SERVICE_ACCOUNTS,...]] - [GCLOUD_WIDE_FLAG ...] + [--[no-]tls-inspect] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) gcloud alpha compute firewall-policies rules update is used to @@ -136,6 +136,12 @@ OPTIONAL FLAGS --target-service-accounts=[TARGET_SERVICE_ACCOUNTS,...] List of target service accounts for the rule. + --[no-]tls-inspect + Use this flag to indicate whether TLS traffic should be inspected using + the TLS inspection policy when the security profile group is applied. + Default: no TLS inspection. Use --tls-inspect to enable and + --no-tls-inspect to disable. + GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, diff --git a/gcloud/alpha/compute/instance-templates/list b/gcloud/alpha/compute/instance-templates/list index 7316f8ae0..a164a28f2 100644 --- a/gcloud/alpha/compute/instance-templates/list +++ b/gcloud/alpha/compute/instance-templates/list @@ -4,9 +4,10 @@ NAME SYNOPSIS gcloud alpha compute instance-templates list [NAME ...] - [--regexp=REGEXP, -r REGEXP] [--global | --regions=[REGION,...]] - [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] - [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + [--regexp=REGEXP, -r REGEXP] [--view=VIEW] + [--global | --regions=[REGION,...]] [--filter=EXPRESSION] + [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) gcloud alpha compute instance-templates list displays all Google @@ -51,6 +52,15 @@ FLAGS Flag --regexp is deprecated. Use --filter="name~'REGEXP'" instead. + --view=VIEW + specify Instance view. VIEW must be one of: + + BASIC + Default view of instance, Including everything except Partner + Metadata. + FULL + Include everything in instance template + At most one of these can be specified: --global diff --git a/gcloud/alpha/compute/instances/list b/gcloud/alpha/compute/instances/list index 3cf0b16ab..da91a1cad 100644 --- a/gcloud/alpha/compute/instances/list +++ b/gcloud/alpha/compute/instances/list @@ -3,8 +3,8 @@ NAME SYNOPSIS gcloud alpha compute instances list [NAME ...] [--regexp=REGEXP, -r REGEXP] - [--zones=ZONE,[ZONE,...]] [--filter=EXPRESSION] [--limit=LIMIT] - [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [--view=VIEW] [--zones=ZONE,[ZONE,...]] [--filter=EXPRESSION] + [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -45,6 +45,15 @@ FLAGS Flag --regexp is deprecated. Use --filter="name~'REGEXP'" instead. + --view=VIEW + specify Instance view. VIEW must be one of: + + BASIC + Default view of instance, Including everything except Partner + Metadata. + FULL + Include everything in instance + --zones=ZONE,[ZONE,...] If provided, only resources from the given zones are queried. diff --git a/gcloud/alpha/compute/interconnects/create b/gcloud/alpha/compute/interconnects/create index 4185bb497..c2ccc5e83 100644 --- a/gcloud/alpha/compute/interconnects/create +++ b/gcloud/alpha/compute/interconnects/create @@ -8,7 +8,8 @@ SYNOPSIS --location=LOCATION --requested-link-count=REQUESTED_LINK_COUNT [--admin-enabled] [--customer-name=CUSTOMER_NAME] [--description=DESCRIPTION] [--noc-contact-email=NOC_CONTACT_EMAIL] - [--remote-location=REMOTE_LOCATION] [GCLOUD_WIDE_FLAG ...] + [--remote-location=REMOTE_LOCATION] + [--requested-features=[FEATURES,...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) gcloud alpha compute interconnects create is used to create @@ -96,6 +97,17 @@ OPTIONAL FLAGS remote-locations list command to find the appropriate remote location to use when creating a Cross-Cloud Interconnect. + --requested-features=[FEATURES,...] + List of features requested for this interconnect. FEATURES must be + (only one value is supported): + + MACSEC + If specified then the interconnect will be created on MACsec + capable hardware ports. If not specified, the default value is + false, which will allocate non-MACsec capable ports first if + available. This parameter can only be provided during interconnect + INSERT and cannot be changed using interconnect PATCH. + GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, diff --git a/gcloud/alpha/compute/interconnects/macsec/add-key b/gcloud/alpha/compute/interconnects/macsec/add-key index 69c8e0ab7..f57691fa2 100644 --- a/gcloud/alpha/compute/interconnects/macsec/add-key +++ b/gcloud/alpha/compute/interconnects/macsec/add-key @@ -49,5 +49,7 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. + access allowlist. This variant is also available: + + $ gcloud beta compute interconnects macsec add-key diff --git a/gcloud/alpha/compute/interconnects/macsec/get-config b/gcloud/alpha/compute/interconnects/macsec/get-config index 192814a88..674448b38 100644 --- a/gcloud/alpha/compute/interconnects/macsec/get-config +++ b/gcloud/alpha/compute/interconnects/macsec/get-config @@ -11,6 +11,15 @@ DESCRIPTION MACsec configuration data associated with Compute Engine interconnect in a project. + For an example, refer to the EXAMPLES section below. + +EXAMPLES + To displays all MACsec configuration data associated with Compute Engine + interconnect in a project, run: + + $ gcloud alpha compute interconnects macsec get-config \ + example-interconnect + POSITIONAL ARGUMENTS NAME Name of the interconnect to describe. @@ -27,5 +36,7 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. + access allowlist. This variant is also available: + + $ gcloud beta compute interconnects macsec get-config diff --git a/gcloud/alpha/compute/interconnects/macsec/help b/gcloud/alpha/compute/interconnects/macsec/help index a4c502ef6..5eae06965 100644 --- a/gcloud/alpha/compute/interconnects/macsec/help +++ b/gcloud/alpha/compute/interconnects/macsec/help @@ -31,9 +31,15 @@ COMMANDS update (ALPHA) Update a Compute Engine interconnect MACsec configuration. + update-key + (ALPHA) Update pre-shared key in a Compute Engine interconnect MACsec + configuration. + NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. + access allowlist. This variant is also available: + + $ gcloud beta compute interconnects macsec diff --git a/gcloud/alpha/compute/interconnects/macsec/remove-key b/gcloud/alpha/compute/interconnects/macsec/remove-key index 1e1fea349..fcf6b9f5a 100644 --- a/gcloud/alpha/compute/interconnects/macsec/remove-key +++ b/gcloud/alpha/compute/interconnects/macsec/remove-key @@ -10,6 +10,14 @@ DESCRIPTION (ALPHA) gcloud alpha compute interconnects macsec remove-key is used to remove pre-shared key from MACsec configuration of interconnect. + For an example, refer to the EXAMPLES section below. + +EXAMPLES + To remove a pre-shared key from MACsec configuration, run: + + $ gcloud alpha compute interconnects macsec remove-key \ + example-interconnect --key-name=default-key + POSITIONAL ARGUMENTS NAME Name of the interconnect to update. @@ -31,5 +39,7 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. + access allowlist. This variant is also available: + + $ gcloud beta compute interconnects macsec remove-key diff --git a/gcloud/alpha/compute/interconnects/macsec/update b/gcloud/alpha/compute/interconnects/macsec/update index 5871fba58..4699cbbe8 100644 --- a/gcloud/alpha/compute/interconnects/macsec/update +++ b/gcloud/alpha/compute/interconnects/macsec/update @@ -11,6 +11,14 @@ DESCRIPTION MACsec configuration of interconnect. An interconnect represents a single specific connection between Google and the customer. + For an example, refer to the EXAMPLES section below. + +EXAMPLES + To enable MACsec on an interconnect, run: + + $ gcloud alpha compute interconnects macsec update \ + example-interconnect --enabled + POSITIONAL ARGUMENTS NAME Name of the interconnect to update. @@ -41,5 +49,7 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. + access allowlist. This variant is also available: + + $ gcloud beta compute interconnects macsec update diff --git a/gcloud/alpha/compute/interconnects/macsec/update-key b/gcloud/alpha/compute/interconnects/macsec/update-key new file mode 100644 index 000000000..5139658df --- /dev/null +++ b/gcloud/alpha/compute/interconnects/macsec/update-key @@ -0,0 +1,55 @@ +NAME + gcloud alpha compute interconnects macsec update-key - update pre-shared + key in a Compute Engine interconnect MACsec configuration + +SYNOPSIS + gcloud alpha compute interconnects macsec update-key NAME + --key-name=KEY_NAME [--start-time=START_TIME] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) gcloud alpha compute interconnects macsec update-key is used to + update a pre-shared key in MACsec configuration of interconnect. + + For an example, refer to the EXAMPLES section below. + +EXAMPLES + To update a pre-shared key in MACsec configuration, run: + + $ gcloud alpha compute interconnects macsec update-key \ + example-interconnect --key-name=default-key \ + --start-time=2021-02-01T12:12:12Z + +POSITIONAL ARGUMENTS + NAME + Name of the interconnect to update. + +REQUIRED FLAGS + --key-name=KEY_NAME + A name of pre-shared key being added to MACsec configuration of the + interconnect. The name must be 1-63 characters long, and comply with + RFC1035. + +OPTIONAL FLAGS + --start-time=START_TIME + A RFC3339 timestamp on or after which the key is valid. startTime can + be in the future. If the keychain has a single key, --start-time can be + omitted. If the keychain has multiple keys, --start-time is mandatory + for each key. The start times of two consecutive keys must be at least + 6 hours apart. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud beta compute interconnects macsec update-key + diff --git a/gcloud/alpha/compute/network-firewall-policies/rules/create b/gcloud/alpha/compute/network-firewall-policies/rules/create index b58532ace..9096bed9e 100644 --- a/gcloud/alpha/compute/network-firewall-policies/rules/create +++ b/gcloud/alpha/compute/network-firewall-policies/rules/create @@ -20,6 +20,7 @@ SYNOPSIS [--src-threat-intelligence=[SOURCE_THREAT_INTELLIGENCE_LISTS,...]] [--target-secure-tags=[TARGET_SECURE_TAGS,...]] [--target-service-accounts=[TARGET_SERVICE_ACCOUNTS,...]] + [--[no-]tls-inspect] [--firewall-policy-region=FIREWALL_POLICY_REGION | --global-firewall-policy] [GCLOUD_WIDE_FLAG ...] @@ -148,6 +149,12 @@ OPTIONAL FLAGS --target-service-accounts=[TARGET_SERVICE_ACCOUNTS,...] List of target service accounts for the rule. + --[no-]tls-inspect + Use this flag to indicate whether TLS traffic should be inspected using + the TLS inspection policy when the security profile group is applied. + Default: no TLS inspection. Use --tls-inspect to enable and + --no-tls-inspect to disable. + At most one of these can be specified: --firewall-policy-region=FIREWALL_POLICY_REGION diff --git a/gcloud/alpha/compute/network-firewall-policies/rules/update b/gcloud/alpha/compute/network-firewall-policies/rules/update index 15ec05add..0fb1ba6be 100644 --- a/gcloud/alpha/compute/network-firewall-policies/rules/update +++ b/gcloud/alpha/compute/network-firewall-policies/rules/update @@ -20,6 +20,7 @@ SYNOPSIS [--src-threat-intelligence=[SOURCE_THREAT_INTELLIGENCE_LISTS,...]] [--target-secure-tags=[TARGET_SECURE_TAGS,...]] [--target-service-accounts=[TARGET_SERVICE_ACCOUNTS,...]] + [--[no-]tls-inspect] [--firewall-policy-region=FIREWALL_POLICY_REGION | --global-firewall-policy] [GCLOUD_WIDE_FLAG ...] @@ -144,6 +145,12 @@ OPTIONAL FLAGS --target-service-accounts=[TARGET_SERVICE_ACCOUNTS,...] List of target service accounts for the rule. + --[no-]tls-inspect + Use this flag to indicate whether TLS traffic should be inspected using + the TLS inspection policy when the security profile group is applied. + Default: no TLS inspection. Use --tls-inspect to enable and + --no-tls-inspect to disable. + At most one of these can be specified: --firewall-policy-region=FIREWALL_POLICY_REGION diff --git a/gcloud/alpha/compute/os-config/guest-policies/create b/gcloud/alpha/compute/os-config/guest-policies/create deleted file mode 100644 index ca069cf4f..000000000 --- a/gcloud/alpha/compute/os-config/guest-policies/create +++ /dev/null @@ -1,72 +0,0 @@ -NAME - gcloud alpha compute os-config guest-policies create - create a guest - policy for a project, a folder, or an organization - -SYNOPSIS - gcloud alpha compute os-config guest-policies create POLICY_ID --file=FILE - [--folder=FOLDER_ID | --organization=ORGANIZATION_ID - | --project=PROJECT_ID] [GCLOUD_WIDE_FLAG ...] - -EXAMPLES - To create a guest policy policy1 in the current project, run: - - $ gcloud alpha compute os-config guest-policies create policy1 \ - --file=path_to_config_file - - To create a guest policy policy1 in the organization 12345, run: - - $ gcloud alpha compute os-config guest-policies create policy1 \ - --file=path_to_config_file --organization=12345 - -POSITIONAL ARGUMENTS - POLICY_ID - Name of the guest policy to create. - - This name must contain only lowercase letters, numbers, and hyphens, - start with a letter, end with a number or a letter, be between 1-63 - characters, and unique within the project, folder, or organization. - -REQUIRED FLAGS - --file=FILE - The JSON or YAML file with the guest policy to create. - -OPTIONAL FLAGS - The scope of the guest policy. If a scope is not specified, the current - project is used as the default. - - At most one of these can be specified: - - --folder=FOLDER_ID - The folder of the guest policy to create. - - --organization=ORGANIZATION_ID - The organization of the guest policy to create. - - --project=PROJECT_ID - The project name to use. If a project name is not specified, then the - current project is used. The current project can be listed using - gcloud config list --format='text(core.project)' and can be set using - gcloud config set project PROJECTID. - - --project and its fallback core/project property play two roles. It - specifies the project of the resource to operate on, and also - specifies the project for API enablement check, quota, and billing. - To specify a different project for quota and billing, use - --billing-project or billing/quota_project property. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --configuration, --flags-file, --flatten, --format, - --help, --impersonate-service-account, --log-http, --project, --quiet, - --trace-token, --user-output-enabled, --verbosity. - - Run $ gcloud help for details. - -NOTES - This command is currently in alpha and might change without notice. If this - command fails with API permission errors despite specifying the correct - project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: - - $ gcloud beta compute os-config guest-policies create - diff --git a/gcloud/alpha/compute/os-config/guest-policies/delete b/gcloud/alpha/compute/os-config/guest-policies/delete deleted file mode 100644 index 96c57b90f..000000000 --- a/gcloud/alpha/compute/os-config/guest-policies/delete +++ /dev/null @@ -1,63 +0,0 @@ -NAME - gcloud alpha compute os-config guest-policies delete - delete the specified - guest policy - -SYNOPSIS - gcloud alpha compute os-config guest-policies delete POLICY_ID - [--folder=FOLDER_ID | --organization=ORGANIZATION_ID - | --project=PROJECT_ID] [GCLOUD_WIDE_FLAG ...] - -EXAMPLES - To delete the guest policy named policy1 in the current project, run: - - $ gcloud alpha compute os-config guest-policies delete policy1 - - To delete the guest policy named policy1 in the organization 12345, run: - - $ gcloud alpha compute os-config guest-policies delete policy1 \ - --organization=12345 - -POSITIONAL ARGUMENTS - POLICY_ID - Name of the guest policy to delete. - -FLAGS - The scope of the guest policy. If a scope is not specified, the current - project is used as the default. - - At most one of these can be specified: - - --folder=FOLDER_ID - The folder of the guest policy to delete. - - --organization=ORGANIZATION_ID - The organization of the guest policy to delete. - - --project=PROJECT_ID - The project name to use. If a project name is not specified, then the - current project is used. The current project can be listed using - gcloud config list --format='text(core.project)' and can be set using - gcloud config set project PROJECTID. - - --project and its fallback core/project property play two roles. It - specifies the project of the resource to operate on, and also - specifies the project for API enablement check, quota, and billing. - To specify a different project for quota and billing, use - --billing-project or billing/quota_project property. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --configuration, --flags-file, --flatten, --format, - --help, --impersonate-service-account, --log-http, --project, --quiet, - --trace-token, --user-output-enabled, --verbosity. - - Run $ gcloud help for details. - -NOTES - This command is currently in alpha and might change without notice. If this - command fails with API permission errors despite specifying the correct - project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: - - $ gcloud beta compute os-config guest-policies delete - diff --git a/gcloud/alpha/compute/os-config/guest-policies/describe b/gcloud/alpha/compute/os-config/guest-policies/describe deleted file mode 100644 index 8f2b9065e..000000000 --- a/gcloud/alpha/compute/os-config/guest-policies/describe +++ /dev/null @@ -1,63 +0,0 @@ -NAME - gcloud alpha compute os-config guest-policies describe - describe the - specified guest policy - -SYNOPSIS - gcloud alpha compute os-config guest-policies describe POLICY_ID - [--folder=FOLDER_ID | --organization=ORGANIZATION_ID - | --project=PROJECT_ID] [GCLOUD_WIDE_FLAG ...] - -EXAMPLES - To describe the guest policy policy1 in the current project, run: - - $ gcloud alpha compute os-config guest-policies describe policy1 - - To describe the guest policy policy1 in the organization 12345, run: - - $ gcloud alpha compute os-config guest-policies describe policy1 \ - --organization=12345 - -POSITIONAL ARGUMENTS - POLICY_ID - Name of the guest policy to describe. - -FLAGS - The scope of the guest policy. If a scope is not specified, the current - project is used as the default. - - At most one of these can be specified: - - --folder=FOLDER_ID - The folder of the guest policy to describe. - - --organization=ORGANIZATION_ID - The organization of the guest policy to describe. - - --project=PROJECT_ID - The project name to use. If a project name is not specified, then the - current project is used. The current project can be listed using - gcloud config list --format='text(core.project)' and can be set using - gcloud config set project PROJECTID. - - --project and its fallback core/project property play two roles. It - specifies the project of the resource to operate on, and also - specifies the project for API enablement check, quota, and billing. - To specify a different project for quota and billing, use - --billing-project or billing/quota_project property. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --configuration, --flags-file, --flatten, --format, - --help, --impersonate-service-account, --log-http, --project, --quiet, - --trace-token, --user-output-enabled, --verbosity. - - Run $ gcloud help for details. - -NOTES - This command is currently in alpha and might change without notice. If this - command fails with API permission errors despite specifying the correct - project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: - - $ gcloud beta compute os-config guest-policies describe - diff --git a/gcloud/alpha/compute/os-config/guest-policies/help b/gcloud/alpha/compute/os-config/guest-policies/help deleted file mode 100644 index feb320564..000000000 --- a/gcloud/alpha/compute/os-config/guest-policies/help +++ /dev/null @@ -1,47 +0,0 @@ -NAME - gcloud alpha compute os-config guest-policies - manage guest OS policies - for Compute Engine VM instances - -SYNOPSIS - gcloud alpha compute os-config guest-policies COMMAND - [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (ALPHA) Manage guest OS policies for Compute Engine VM instances. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --help. - - Run $ gcloud help for details. - -COMMANDS - COMMAND is one of the following: - - create - (ALPHA) Create a guest policy for a project, a folder, or an - organization. - - delete - (ALPHA) Delete the specified guest policy. - - describe - (ALPHA) Describe the specified guest policy. - - list - (ALPHA) List guest policies in a project, a folder, or an organization. - - lookup - (ALPHA) Display the guest policies that are applied to an instance. - - update - (ALPHA) Update the specified guest policy for a project, a folder, or - an organization. - -NOTES - This command is currently in alpha and might change without notice. If this - command fails with API permission errors despite specifying the correct - project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: - - $ gcloud beta compute os-config guest-policies - diff --git a/gcloud/alpha/compute/os-config/guest-policies/lookup b/gcloud/alpha/compute/os-config/guest-policies/lookup deleted file mode 100644 index 7bbe20e0a..000000000 --- a/gcloud/alpha/compute/os-config/guest-policies/lookup +++ /dev/null @@ -1,62 +0,0 @@ -NAME - gcloud alpha compute os-config guest-policies lookup - display the guest - policies that are applied to an instance - -SYNOPSIS - gcloud alpha compute os-config guest-policies lookup INSTANCE_NAME - [--zone=ZONE] [GCLOUD_WIDE_FLAG ...] - -EXAMPLES - To view all guest policies that are applied to an instance named - my-instance, run: - - $ gcloud alpha compute os-config guest-policies lookup my-instance - -POSITIONAL ARGUMENTS - INSTANCE_NAME - Name of the instance to look up guest policies for. 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 - -FLAGS - --zone=ZONE - Zone of the instance to look up guest policies for. If not specified, - you might be prompted to select a zone (interactive mode only). gcloud - attempts to identify the appropriate zone by searching for resources in - your currently active project. If the zone cannot be determined, gcloud - prompts you for a selection with all available Google Cloud Platform - zones. - - To avoid prompting when this flag is omitted, the user can set the - compute/zone property: - - $ gcloud config set compute/zone ZONE - - A list of zones can be fetched by running: - - $ gcloud compute zones list - - To unset the property, run: - - $ gcloud config unset compute/zone - - Alternatively, the zone can be stored in the environment variable - CLOUDSDK_COMPUTE_ZONE. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --configuration, --flags-file, --flatten, --format, - --help, --impersonate-service-account, --log-http, --project, --quiet, - --trace-token, --user-output-enabled, --verbosity. - - Run $ gcloud help for details. - -NOTES - This command is currently in alpha and might change without notice. If this - command fails with API permission errors despite specifying the correct - project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: - - $ gcloud beta compute os-config guest-policies lookup - diff --git a/gcloud/alpha/compute/os-config/guest-policies/update b/gcloud/alpha/compute/os-config/guest-policies/update deleted file mode 100644 index 5b9c8dadd..000000000 --- a/gcloud/alpha/compute/os-config/guest-policies/update +++ /dev/null @@ -1,73 +0,0 @@ -NAME - gcloud alpha compute os-config guest-policies update - update the specified - guest policy for a project, a folder, or an organization - -SYNOPSIS - gcloud alpha compute os-config guest-policies update POLICY_ID --file=FILE - [--folder=FOLDER_ID | --organization=ORGANIZATION_ID - | --project=PROJECT_ID] [GCLOUD_WIDE_FLAG ...] - -EXAMPLES - To update the guest policy policy1 in the project project1, run: - - $ gcloud alpha compute os-config guest-policies update policy1 \ - --file=path_to_config_file --project=project1 - - To update the guest policy policy1 in the organization 12345, run: - - $ gcloud alpha compute os-config guest-policies update policy1 \ - --file=path_to_config_file --organization=12345 - -POSITIONAL ARGUMENTS - POLICY_ID - Name of the guest policy to update. - -REQUIRED FLAGS - --file=FILE - The JSON or YAML file with the updated guest policy. - - If this file specifies an etag value, the update succeeds only if the - policy that is already in place has a matching etag value. If no etag - value is specified, the specifications in the updated policy file - replaces the existing policy. - -OPTIONAL FLAGS - The scope of the guest policy. If a scope is not specified, the current - project is used as the default. - - At most one of these can be specified: - - --folder=FOLDER_ID - The folder of the guest policy to update. - - --organization=ORGANIZATION_ID - The organization of the guest policy to update. - - --project=PROJECT_ID - The project name to use. If a project name is not specified, then the - current project is used. The current project can be listed using - gcloud config list --format='text(core.project)' and can be set using - gcloud config set project PROJECTID. - - --project and its fallback core/project property play two roles. It - specifies the project of the resource to operate on, and also - specifies the project for API enablement check, quota, and billing. - To specify a different project for quota and billing, use - --billing-project or billing/quota_project property. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --configuration, --flags-file, --flatten, --format, - --help, --impersonate-service-account, --log-http, --project, --quiet, - --trace-token, --user-output-enabled, --verbosity. - - Run $ gcloud help for details. - -NOTES - This command is currently in alpha and might change without notice. If this - command fails with API permission errors despite specifying the correct - project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: - - $ gcloud beta compute os-config guest-policies update - diff --git a/gcloud/alpha/compute/os-config/help b/gcloud/alpha/compute/os-config/help index 7eb52a0d6..f2b15fe17 100644 --- a/gcloud/alpha/compute/os-config/help +++ b/gcloud/alpha/compute/os-config/help @@ -16,9 +16,6 @@ GCLOUD WIDE FLAGS GROUPS GROUP is one of the following: - guest-policies - (ALPHA) Manage guest OS policies for Compute Engine VM instances. - instance-os-policies-compliances (ALPHA) Report compliance states for OS policies applied to a Compute Engine VM. @@ -32,13 +29,6 @@ GROUPS os-policy-assignments (ALPHA) Manage OS policy assignments. - patch-deployments - (ALPHA) Manage guest OS patch deployments for Compute Engine VM - instances. - - patch-jobs - (ALPHA) Manage OS patches for Compute Engine VMs. - vulnerability-reports (ALPHA) Display vulnerability reports for a Compute Engine VM. diff --git a/gcloud/alpha/compute/os-config/patch-deployments/create b/gcloud/alpha/compute/os-config/patch-deployments/create deleted file mode 100644 index 109ef495e..000000000 --- a/gcloud/alpha/compute/os-config/patch-deployments/create +++ /dev/null @@ -1,55 +0,0 @@ -NAME - gcloud alpha compute os-config patch-deployments create - create a patch - deployment for a project - -SYNOPSIS - gcloud alpha compute os-config patch-deployments create PATCH_DEPLOYMENT_ID - --file=FILE [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (ALPHA) gcloud alpha compute os-config patch-deployments create creates a - patch deployment in a project from a specified file. A patch deployment - triggers a patch job to run at specific time(s) according to a schedule, - and applies instance filters and other patch configurations to the patch - job at run time. Alternatively, to run a patch job on-demand, see $ gcloud - alpha compute os-config patch-jobs execute. - -EXAMPLES - To create a patch deployment patch-deployment-1 in the current project, - run: - - $ gcloud alpha compute os-config patch-deployments create \ - patch-deployment-1 --file=path_to_config_file - -POSITIONAL ARGUMENTS - PATCH_DEPLOYMENT_ID - Name of the patch deployment to create. - - This name must contain only lowercase letters, numbers, and hyphens, - start with a letter, end with a number or a letter, be between 1-63 - characters, and unique within the project. - -REQUIRED FLAGS - --file=FILE - The JSON or YAML file with the patch deployment to create. For - information about the patch deployment format, see - https://cloud.google.com/compute/docs/osconfig/rest/v1alpha2/projects.patchDeployments. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --configuration, --flags-file, --flatten, --format, - --help, --impersonate-service-account, --log-http, --project, --quiet, - --trace-token, --user-output-enabled, --verbosity. - - Run $ gcloud help for details. - -NOTES - This command is currently in alpha and might change without notice. If this - command fails with API permission errors despite specifying the correct - project, you might be trying to access an API with an invitation-only early - access allowlist. These variants are also available: - - $ gcloud compute os-config patch-deployments create - - $ gcloud beta compute os-config patch-deployments create - diff --git a/gcloud/alpha/compute/os-config/patch-deployments/delete b/gcloud/alpha/compute/os-config/patch-deployments/delete deleted file mode 100644 index d21773cf4..000000000 --- a/gcloud/alpha/compute/os-config/patch-deployments/delete +++ /dev/null @@ -1,56 +0,0 @@ -NAME - gcloud alpha compute os-config patch-deployments delete - delete the - specified patch deployment - -SYNOPSIS - gcloud alpha compute os-config patch-deployments delete PATCH_DEPLOYMENT - [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (ALPHA) Delete the specified patch deployment. - -EXAMPLES - To delete the patch deployment patch-deployment-1 in the current project, - run: - - $ gcloud alpha compute os-config patch-deployments delete \ - patch-deployment-1 - -POSITIONAL ARGUMENTS - Patch deployment resource - Patch deployment 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 patch_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. - - PATCH_DEPLOYMENT - ID of the patch_deployment or fully qualified identifier for the - patch_deployment. - - To set the patch_deployment attribute: - ▸ provide the argument patch_deployment on the command line. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --configuration, --flags-file, --flatten, --format, - --help, --impersonate-service-account, --log-http, --project, --quiet, - --trace-token, --user-output-enabled, --verbosity. - - Run $ gcloud help for details. - -NOTES - This command is currently in alpha and might change without notice. If this - command fails with API permission errors despite specifying the correct - project, you might be trying to access an API with an invitation-only early - access allowlist. These variants are also available: - - $ gcloud compute os-config patch-deployments delete - - $ gcloud beta compute os-config patch-deployments delete - diff --git a/gcloud/alpha/compute/os-config/patch-deployments/describe b/gcloud/alpha/compute/os-config/patch-deployments/describe deleted file mode 100644 index cfe639d65..000000000 --- a/gcloud/alpha/compute/os-config/patch-deployments/describe +++ /dev/null @@ -1,56 +0,0 @@ -NAME - gcloud alpha compute os-config patch-deployments describe - describe the - specified patch deployment - -SYNOPSIS - gcloud alpha compute os-config patch-deployments describe PATCH_DEPLOYMENT - [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (ALPHA) Describe the specified patch deployment. - -EXAMPLES - To check the status of the patch deployment patch-deployment-1 in the - current project, run: - - $ gcloud alpha compute os-config patch-deployments describe \ - patch-deployment-1 - -POSITIONAL ARGUMENTS - Patch deployment resource - Patch deployment 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 patch_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. - - PATCH_DEPLOYMENT - ID of the patch_deployment or fully qualified identifier for the - patch_deployment. - - To set the patch_deployment attribute: - ▸ provide the argument patch_deployment on the command line. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --configuration, --flags-file, --flatten, --format, - --help, --impersonate-service-account, --log-http, --project, --quiet, - --trace-token, --user-output-enabled, --verbosity. - - Run $ gcloud help for details. - -NOTES - This command is currently in alpha and might change without notice. If this - command fails with API permission errors despite specifying the correct - project, you might be trying to access an API with an invitation-only early - access allowlist. These variants are also available: - - $ gcloud compute os-config patch-deployments describe - - $ gcloud beta compute os-config patch-deployments describe - diff --git a/gcloud/alpha/compute/os-config/patch-deployments/help b/gcloud/alpha/compute/os-config/patch-deployments/help deleted file mode 100644 index 397d970b1..000000000 --- a/gcloud/alpha/compute/os-config/patch-deployments/help +++ /dev/null @@ -1,50 +0,0 @@ -NAME - gcloud alpha compute os-config patch-deployments - manage guest OS patch - deployments for Compute Engine VM instances - -SYNOPSIS - gcloud alpha compute os-config patch-deployments COMMAND - [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (ALPHA) Manage guest OS patch deployments for Compute Engine VM instances. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --help. - - Run $ gcloud help for details. - -COMMANDS - COMMAND is one of the following: - - create - (ALPHA) Create a patch deployment for a project. - - delete - (ALPHA) Delete the specified patch deployment. - - describe - (ALPHA) Describe the specified patch deployment. - - list - (ALPHA) List patch deployments in a project. - - pause - (ALPHA) Pause patch deployment in a project. - - resume - (ALPHA) Resume patch deployment in a project. - - update - (ALPHA) Update a patch deployment in a project. - -NOTES - This command is currently in alpha and might change without notice. If this - command fails with API permission errors despite specifying the correct - project, you might be trying to access an API with an invitation-only early - access allowlist. These variants are also available: - - $ gcloud compute os-config patch-deployments - - $ gcloud beta compute os-config patch-deployments - diff --git a/gcloud/alpha/compute/os-config/patch-deployments/pause b/gcloud/alpha/compute/os-config/patch-deployments/pause deleted file mode 100644 index fea1a1df4..000000000 --- a/gcloud/alpha/compute/os-config/patch-deployments/pause +++ /dev/null @@ -1,56 +0,0 @@ -NAME - gcloud alpha compute os-config patch-deployments pause - pause patch - deployment in a project - -SYNOPSIS - gcloud alpha compute os-config patch-deployments pause PATCH_DEPLOYMENT - [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (ALPHA) Pause patch deployment in a project. - -EXAMPLES - To pause the patch deployment patch-deployment-1 in the current project, - run: - - $ gcloud alpha compute os-config patch-deployments pause \ - patch-deployment-1 - -POSITIONAL ARGUMENTS - Patch deployment resource - Patch deployment to pause. 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 patch_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. - - PATCH_DEPLOYMENT - ID of the patch_deployment or fully qualified identifier for the - patch_deployment. - - To set the patch_deployment attribute: - ▸ provide the argument patch_deployment on the command line. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --configuration, --flags-file, --flatten, --format, - --help, --impersonate-service-account, --log-http, --project, --quiet, - --trace-token, --user-output-enabled, --verbosity. - - Run $ gcloud help for details. - -NOTES - This command is currently in alpha and might change without notice. If this - command fails with API permission errors despite specifying the correct - project, you might be trying to access an API with an invitation-only early - access allowlist. These variants are also available: - - $ gcloud compute os-config patch-deployments pause - - $ gcloud beta compute os-config patch-deployments pause - diff --git a/gcloud/alpha/compute/os-config/patch-deployments/resume b/gcloud/alpha/compute/os-config/patch-deployments/resume deleted file mode 100644 index 69777d6d3..000000000 --- a/gcloud/alpha/compute/os-config/patch-deployments/resume +++ /dev/null @@ -1,56 +0,0 @@ -NAME - gcloud alpha compute os-config patch-deployments resume - resume patch - deployment in a project - -SYNOPSIS - gcloud alpha compute os-config patch-deployments resume PATCH_DEPLOYMENT - [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (ALPHA) Resume patch deployment in a project. - -EXAMPLES - To resume the patch deployment patch-deployment-1 in the current project, - run: - - $ gcloud alpha compute os-config patch-deployments resume \ - patch-deployment-1 - -POSITIONAL ARGUMENTS - Patch deployment resource - Patch deployment to resume. 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 patch_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. - - PATCH_DEPLOYMENT - ID of the patch_deployment or fully qualified identifier for the - patch_deployment. - - To set the patch_deployment attribute: - ▸ provide the argument patch_deployment on the command line. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --configuration, --flags-file, --flatten, --format, - --help, --impersonate-service-account, --log-http, --project, --quiet, - --trace-token, --user-output-enabled, --verbosity. - - Run $ gcloud help for details. - -NOTES - This command is currently in alpha and might change without notice. If this - command fails with API permission errors despite specifying the correct - project, you might be trying to access an API with an invitation-only early - access allowlist. These variants are also available: - - $ gcloud compute os-config patch-deployments resume - - $ gcloud beta compute os-config patch-deployments resume - diff --git a/gcloud/alpha/compute/os-config/patch-deployments/update b/gcloud/alpha/compute/os-config/patch-deployments/update deleted file mode 100644 index ea6491fc2..000000000 --- a/gcloud/alpha/compute/os-config/patch-deployments/update +++ /dev/null @@ -1,50 +0,0 @@ -NAME - gcloud alpha compute os-config patch-deployments update - update a patch - deployment in a project - -SYNOPSIS - gcloud alpha compute os-config patch-deployments update PATCH_DEPLOYMENT_ID - --file=FILE [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (ALPHA) Updates a patch deployment in a project. To update the patch - deployment, you must specify a configuration file. - -EXAMPLES - To update a patch deployment patch-deployment-1 in the current project, - run: - - $ gcloud alpha compute os-config patch-deployments update \ - patch-deployment-1 --file=path_to_config_file - -POSITIONAL ARGUMENTS - PATCH_DEPLOYMENT_ID - Name of the patch deployment to update. - - To get a list of patch deployments that are available for update, run - the gcloud alpha compute os-config patch-deployments list command. - -REQUIRED FLAGS - --file=FILE - The JSON or YAML file with the patch deployment to update. For - information about the patch deployment format, see - https://cloud.google.com/compute/docs/osconfig/rest/v1alpha2/projects.patchDeployments. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --configuration, --flags-file, --flatten, --format, - --help, --impersonate-service-account, --log-http, --project, --quiet, - --trace-token, --user-output-enabled, --verbosity. - - Run $ gcloud help for details. - -NOTES - This command is currently in alpha and might change without notice. If this - command fails with API permission errors despite specifying the correct - project, you might be trying to access an API with an invitation-only early - access allowlist. These variants are also available: - - $ gcloud compute os-config patch-deployments update - - $ gcloud beta compute os-config patch-deployments update - diff --git a/gcloud/alpha/compute/os-config/patch-jobs/cancel b/gcloud/alpha/compute/os-config/patch-jobs/cancel deleted file mode 100644 index 246a5f4f8..000000000 --- a/gcloud/alpha/compute/os-config/patch-jobs/cancel +++ /dev/null @@ -1,50 +0,0 @@ -NAME - gcloud alpha compute os-config patch-jobs cancel - cancel a specific OS - patch job which must currently be active - -SYNOPSIS - gcloud alpha compute os-config patch-jobs cancel PATCH_JOB - [GCLOUD_WIDE_FLAG ...] - -EXAMPLES - To cancel the patch job job1, run: - - $ gcloud alpha compute os-config patch-jobs cancel job1 - -POSITIONAL ARGUMENTS - Patch job resource - Patch job to cancel. 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 patch_job 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. - - PATCH_JOB - ID of the patch_job or fully qualified identifier for the patch_job. - - To set the patch_job attribute: - ▸ provide the argument patch_job on the command line. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --configuration, --flags-file, --flatten, --format, - --help, --impersonate-service-account, --log-http, --project, --quiet, - --trace-token, --user-output-enabled, --verbosity. - - Run $ gcloud help for details. - -NOTES - This command is currently in alpha and might change without notice. If this - command fails with API permission errors despite specifying the correct - project, you might be trying to access an API with an invitation-only early - access allowlist. These variants are also available: - - $ gcloud compute os-config patch-jobs cancel - - $ gcloud beta compute os-config patch-jobs cancel - diff --git a/gcloud/alpha/compute/os-config/patch-jobs/describe b/gcloud/alpha/compute/os-config/patch-jobs/describe deleted file mode 100644 index 9d556e7e9..000000000 --- a/gcloud/alpha/compute/os-config/patch-jobs/describe +++ /dev/null @@ -1,50 +0,0 @@ -NAME - gcloud alpha compute os-config patch-jobs describe - describe a specified - OS patch job - -SYNOPSIS - gcloud alpha compute os-config patch-jobs describe PATCH_JOB - [GCLOUD_WIDE_FLAG ...] - -EXAMPLES - To check the status of the patch job job1, run: - - $ gcloud alpha compute os-config patch-jobs describe job1 - -POSITIONAL ARGUMENTS - Patch job resource - Patch job 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 patch_job 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. - - PATCH_JOB - ID of the patch_job or fully qualified identifier for the patch_job. - - To set the patch_job attribute: - ▸ provide the argument patch_job on the command line. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --configuration, --flags-file, --flatten, --format, - --help, --impersonate-service-account, --log-http, --project, --quiet, - --trace-token, --user-output-enabled, --verbosity. - - Run $ gcloud help for details. - -NOTES - This command is currently in alpha and might change without notice. If this - command fails with API permission errors despite specifying the correct - project, you might be trying to access an API with an invitation-only early - access allowlist. These variants are also available: - - $ gcloud compute os-config patch-jobs describe - - $ gcloud beta compute os-config patch-jobs describe - diff --git a/gcloud/alpha/compute/os-config/patch-jobs/execute b/gcloud/alpha/compute/os-config/patch-jobs/execute deleted file mode 100644 index 8e30f2ffb..000000000 --- a/gcloud/alpha/compute/os-config/patch-jobs/execute +++ /dev/null @@ -1,414 +0,0 @@ -NAME - gcloud alpha compute os-config patch-jobs execute - execute an OS patch on - the specified VM instances - -SYNOPSIS - gcloud alpha compute os-config patch-jobs execute - (--instance-filter=INSTANCE_FILTER | --instance-filter-all - | --instance-filter-group-labels=[KEY=VALUE,...] - --instance-filter-name-prefixes=[INSTANCE_FILTER_NAME_PREFIXES,...] - --instance-filter-names=[INSTANCE_FILTER_NAMES,...] - --instance-filter-zones=[INSTANCE_FILTER_ZONES,...]) [--async] - [--description=DESCRIPTION] [--display-name=DISPLAY_NAME] [--dry-run] - [--duration=DURATION] [--mig-instances-allowed] - [--reboot-config=REBOOT_CONFIG] [--retry] - [--apt-dist --apt-excludes=[APT_EXCLUDES,...] - | --apt-exclusive-packages=[APT_EXCLUSIVE_PACKAGES,...]] - [--post-patch-linux-executable=POST_PATCH_LINUX_EXECUTABLE - --post-patch-linux-success-codes=[POST_PATCH_LINUX_SUCCESS_CODES, - ...]] - [--post-patch-windows-executable=POST_PATCH_WINDOWS_EXECUTABLE - --post-patch-windows-success-codes=[POST_PATCH_WINDOWS_SUCCESS_CODES, - ...]] - [--pre-patch-linux-executable=PRE_PATCH_LINUX_EXECUTABLE - --pre-patch-linux-success-codes=[PRE_PATCH_LINUX_SUCCESS_CODES,...]] - [--pre-patch-windows-executable=PRE_PATCH_WINDOWS_EXECUTABLE - --pre-patch-windows-success-codes=[PRE_PATCH_WINDOWS_SUCCESS_CODES, - ...]] - [--rollout-mode=ROLLOUT_MODE - --rollout-disruption-budget=ROLLOUT_DISRUPTION_BUDGET - | --rollout-disruption-budget-percent=ROLLOUT_DISRUPTION_BUDGET_PERCENT] - [--windows-exclusive-patches=[WINDOWS_EXCLUSIVE_PATCHES,...] - | --windows-classifications=[WINDOWS_CLASSIFICATIONS,...] - --windows-excludes=[WINDOWS_EXCLUDES,...]] - [--yum-exclusive-packages=[YUM_EXCLUSIVE_PACKAGES,...] - | --yum-excludes=[YUM_EXCLUDES,...] --yum-minimal --yum-security] - [--zypper-exclusive-patches=[ZYPPER_EXCLUSIVE_PATCHES,...] - | --zypper-categories=[ZYPPER_CATEGORIES,...] - --zypper-excludes=[ZYPPER_EXCLUDES,...] - --zypper-severities=[ZYPPER_SEVERITIES,...] - --zypper-with-optional --zypper-with-update] [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (ALPHA) Execute an OS patch on the specified VM instances. - -EXAMPLES - To start a patch job named my patch job that patches all instances in the - current project, run: - - $ gcloud alpha compute os-config patch-jobs execute \ - --display-name="my patch job" --instance-filter-all - - To patch an instance named instance-1 in the us-east1-b zone, run: - - $ gcloud alpha compute os-config patch-jobs execute \ - --instance-filter-names="zones/us-east1-b/instances/instance-1" - - To patch all instances in the us-central1-b and europe-west1-d zones, run: - - $ gcloud alpha compute os-config patch-jobs execute \ - --instance-filter-zones="us-central1-b,europe-west1-d" - - To patch all instances where the env label is test and app label is web, - run: - - $ gcloud alpha compute os-config patch-jobs execute \ - --instance-filter-group-labels="env=test,app=web" - - To patch all instances where the env label is test and app label is web or - where the env label is staging and app label is web, run: - - $ gcloud alpha compute os-config patch-jobs execute \ - --instance-filter-group-labels="env=test,app=web" \ - --instance-filter-group-labels="env=staging,app=web" - - To apply security and critical patches to Windows instances with the prefix - windows- in the instance name, run: - - $ gcloud alpha compute os-config patch-jobs execute \ - --instance-filter-name-prefixes="windows-" \ - --windows-classifications=SECURITY,CRITICAL - - To update only KB4339284 on Windows instances with the prefix windows- in - the instance name, run: - - $ gcloud alpha compute os-config patch-jobs execute \ - --instance-filter-name-prefixes="windows-" \ - --windows-exclusive-patches=4339284 - - To patch all instances in the current project and specify scripts to run - pre-patch and post-patch, run: - - $ gcloud alpha compute os-config patch-jobs execute \ - --instance-filter-all \ - --pre-patch-linux-executable="/bin/script" \ - --pre-patch-linux-success-codes=0,200 \ - --pre-patch-windows-executable="C:\Users\user\script.ps1" \ - --post-patch-linux-executable="gs://my-bucket/linux-script#123" \ - --post-patch-windows-executable="gs://my-bucket/windows-script#678" - - To patch all instances zone-by-zone with no more than 50 percent of the - instances in the same zone disrupted at a given time, run: - - $ gcloud alpha compute os-config patch-jobs execute \ - --instance-filter-all --rollout-mode=zone-by-zone \ - --rollout-disruption-budget-percent=50 - -REQUIRED FLAGS - Filters for selecting which instances to patch: - - Exactly one of these must be specified: - - --instance-filter=INSTANCE_FILTER - (DEPRECATED) Filter expression for selecting the instances to patch. - Patching supports the same filter mechanisms as gcloud compute - instances list, allowing one to patch specific instances by name, - zone, label, or other criteria. - - --instance-filter is deprecated; use individual filter flags instead. See - the command help text for more details. - - --instance-filter-all - A filter that targets all instances in the project. - - Individual filters. The targeted instances must meet all criteria - specified. - - --instance-filter-group-labels=[KEY=VALUE,...] - A filter that represents a label set. Targeted instances must have - all specified labels in this set. For example, "env=prod and - app=web". - - This flag can be repeated. Targeted instances must have at least - one of these label sets. This allows targeting of disparate groups, - for example, "(env=prod and app=web) or (env=staging and app=web)". - - --instance-filter-name-prefixes=[INSTANCE_FILTER_NAME_PREFIXES,...] - A filter that targets instances whose name starts with one of these - prefixes. For example, "prod-". - - --instance-filter-names=[INSTANCE_FILTER_NAMES,...] - A filter that targets instances of any of the specified names. - Instances are specified by the URI in the form - "zones//instances/", - "projects//zones//instances/", or - "https://www.googleapis.com/compute/v1/projects//zones//instances/". - - --instance-filter-zones=[INSTANCE_FILTER_ZONES,...] - A filter that targets instances in any of the specified zones. - Leave empty to target instances in any zone. - -OPTIONAL FLAGS - --async - Return immediately, without waiting for the operation in progress to - complete. - - --description=DESCRIPTION - Textual description of the patch job. - - --display-name=DISPLAY_NAME - Display name for this patch job. This does not have to be unique. - - --dry-run - Whether to execute this patch job as a dry run. If this patch job is a - dry run, instances are contacted, but the patch is not run. - - --duration=DURATION - Total duration in which the patch job must complete. If the patch does - not complete in this time, the process times out. While some instances - might still be running the patch, they will not continue to work after - completing the current step. See $ gcloud topic datetimes for - information on specifying absolute time durations. - - If unspecified, the job stays active until all instances complete the - patch. - - --mig-instances-allowed - If set, patching of VMs that are part of a managed instance group (MIG) - is allowed. - - --reboot-config=REBOOT_CONFIG - Post-patch reboot settings. REBOOT_CONFIG must be one of: - - always - Always reboot the machine after the update completes. - default - The agent decides if a reboot is necessary by checking signals such - as registry keys or '/var/run/reboot-required'. - never - Never reboot the machine after the update completes. - - --retry - Specifies whether to attempt to retry, within the duration window, if - patching initially fails. If omitted, the agent uses its default retry - strategy. - - Settings for machines running Apt: - - --apt-dist - If specified, machines running Apt use the apt-get dist-upgrade - command; otherwise the apt-get upgrade command is used. - - At most one of these can be specified: - - --apt-excludes=[APT_EXCLUDES,...] - List of packages to exclude from update. - - --apt-exclusive-packages=[APT_EXCLUSIVE_PACKAGES,...] - An exclusive list of packages to be updated. These are the only - packages that will be updated. If these packages are not installed, - they will be ignored. - - Post-patch step settings for Linux machines: - - --post-patch-linux-executable=POST_PATCH_LINUX_EXECUTABLE - A set of commands to run on a Linux machine after an OS patch - completes. Commands must be supplied in a file. If the file contains - a shell script, include the shebang line. - - The path to the file must be supplied in one of the following - formats: - - An absolute path of the file on the local filesystem. - - A URI for a Google Cloud Storage object with a generation number. - - --post-patch-linux-success-codes=[POST_PATCH_LINUX_SUCCESS_CODES,...] - Additional exit codes that the executable can return to indicate a - successful run. The default exit code for success is 0. - - Post-patch step settings for Windows machines: - - --post-patch-windows-executable=POST_PATCH_WINDOWS_EXECUTABLE - A set of commands to run on a Windows machine after an OS patch - completes. Commands must be supplied in a file. If the file contains - a PowerShell script, include the .ps1 file extension. The PowerShell - script executes with flags -NonInteractive, -NoProfile, and - -ExecutionPolicy Bypass. - - The path to the file must be supplied in one of the following - formats: - - An absolute path of the file on the local filesystem. - - A URI for a Google Cloud Storage object with a generation number. - - --post-patch-windows-success-codes=[POST_PATCH_WINDOWS_SUCCESS_CODES,...] - Additional exit codes that the executable can return to indicate a - successful run. The default exit code for success is 0. - - Pre-patch step settings for Linux machines: - - --pre-patch-linux-executable=PRE_PATCH_LINUX_EXECUTABLE - A set of commands to run on a Linux machine before an OS patch - begins. Commands must be supplied in a file. If the file contains a - shell script, include the shebang line. - - The path to the file must be supplied in one of the following - formats: - - An absolute path of the file on the local filesystem. - - A URI for a Google Cloud Storage object with a generation number. - - --pre-patch-linux-success-codes=[PRE_PATCH_LINUX_SUCCESS_CODES,...] - Additional exit codes that the executable can return to indicate a - successful run. The default exit code for success is 0. - - Pre-patch step settings for Windows machines: - - --pre-patch-windows-executable=PRE_PATCH_WINDOWS_EXECUTABLE - A set of commands to run on a Windows machine before an OS patch - begins. Commands must be supplied in a file. If the file contains a - PowerShell script, include the .ps1 file extension. The PowerShell - script executes with flags -NonInteractive, -NoProfile, and - -ExecutionPolicy Bypass. - - The path to the file must be supplied in one of the following - formats: - - An absolute path of the file on the local filesystem. - - A URI for a Google Cloud Storage object with a generation number. - - --pre-patch-windows-success-codes=[PRE_PATCH_WINDOWS_SUCCESS_CODES,...] - Additional exit codes that the executable can return to indicate a - successful run. The default exit code for success is 0. - - Rollout configurations for this patch job: - - --rollout-mode=ROLLOUT_MODE - Mode of the rollout. ROLLOUT_MODE must be one of: - - concurrent-zones - Patches are applied to VMs in all zones at the same time. - zone-by-zone - Patches are applied one zone at a time. The patch job begins in - the region with the lowest number of targeted VMs. Within the - region, patching begins in the zone with the lowest number of - targeted VMs. If multiple regions (or zones within a region) have - the same number of targeted VMs, a tie-breaker is achieved by - sorting the regions or zones in alphabetical order. - - Disruption budget for this rollout. A running VM with an active agent is - considered disrupted if its patching operation fails anytime between the - time the agent is notified until the patch process completes. - - At most one of these can be specified: - - --rollout-disruption-budget=ROLLOUT_DISRUPTION_BUDGET - Number of VMs per zone to disrupt at any given moment. - - --rollout-disruption-budget-percent=ROLLOUT_DISRUPTION_BUDGET_PERCENT - Percentage of VMs per zone to disrupt at any given moment. The - number of VMs calculated from multiplying the percentage by the - total number of VMs in a zone is rounded up. - - Settings for machines running Windows: - - At most one of these can be specified: - - --windows-exclusive-patches=[WINDOWS_EXCLUSIVE_PATCHES,...] - An exclusive list of Knowledge Base (KB) IDs to be updated. These are - the only patches that will be updated. - - Windows patch options - - --windows-classifications=[WINDOWS_CLASSIFICATIONS,...] - List of classifications to use to restrict the Windows update. Only - patches of the given classifications are applied. If omitted, a - default Windows update is performed. For more information on - classifications, see: - https://support.microsoft.com/en-us/help/824684. - WINDOWS_CLASSIFICATIONS must be one of: critical, security, - definition, driver, feature-pack, service-pack, tool, - update-rollup, update. - - --windows-excludes=[WINDOWS_EXCLUDES,...] - Optional list of Knowledge Base (KB) IDs to exclude from the update - operation. - - Settings for machines running Yum: - - At most one of these can be specified: - - --yum-exclusive-packages=[YUM_EXCLUSIVE_PACKAGES,...] - An exclusive list of packages to be updated. These are the only - packages that will be updated. If these packages are not installed, - they will be ignored. - - Yum patch options - - --yum-excludes=[YUM_EXCLUDES,...] - Optional list of packages to exclude from updating. If this - argument is specified, machines running Yum exclude the given list - of packages using the Yum --exclude flag. - - --yum-minimal - If specified, machines running Yum use the command yum - update-minimal; otherwise the patch uses yum-update. - - --yum-security - If specified, machines running Yum append the --security flag to - the patch command. - - Settings for machines running Zypper: - - At most one of these can be specified: - - --zypper-exclusive-patches=[ZYPPER_EXCLUSIVE_PATCHES,...] - An exclusive list of patches to be updated. These are the only - patches that will be installed using the 'zypper patch - patch:' command. - - Zypper patch options - - --zypper-categories=[ZYPPER_CATEGORIES,...] - If specified, machines running Zypper install only patches with the - specified categories. Categories include security, recommended, and - feature. - - --zypper-excludes=[ZYPPER_EXCLUDES,...] - List of Zypper patches to exclude from the patch job. - - --zypper-severities=[ZYPPER_SEVERITIES,...] - If specified, machines running Zypper install only patch with the - specified severities. Severities include critical, important, - moderate, and low. - - --zypper-with-optional - If specified, machines running Zypper add the --with-optional flag - to zypper patch. - - --zypper-with-update - If specified, machines running Zypper add the --with-update flag to - zypper patch. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --configuration, --flags-file, --flatten, --format, - --help, --impersonate-service-account, --log-http, --project, --quiet, - --trace-token, --user-output-enabled, --verbosity. - - Run $ gcloud help for details. - -NOTES - This command is currently in alpha and might change without notice. If this - command fails with API permission errors despite specifying the correct - project, you might be trying to access an API with an invitation-only early - access allowlist. These variants are also available: - - $ gcloud compute os-config patch-jobs execute - - $ gcloud beta compute os-config patch-jobs execute - diff --git a/gcloud/alpha/compute/os-config/patch-jobs/help b/gcloud/alpha/compute/os-config/patch-jobs/help deleted file mode 100644 index 5175772a5..000000000 --- a/gcloud/alpha/compute/os-config/patch-jobs/help +++ /dev/null @@ -1,43 +0,0 @@ -NAME - gcloud alpha compute os-config patch-jobs - manage OS patches for Compute - Engine VMs - -SYNOPSIS - gcloud alpha compute os-config patch-jobs COMMAND [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (ALPHA) Manage OS patches for Compute Engine VMs. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --help. - - Run $ gcloud help for details. - -COMMANDS - COMMAND is one of the following: - - cancel - (ALPHA) Cancel a specific OS patch job which must currently be active. - - describe - (ALPHA) Describe a specified OS patch job. - - execute - (ALPHA) Execute an OS patch on the specified VM instances. - - list - (ALPHA) List ongoing and completed patch jobs. - - list-instance-details - (ALPHA) List the instance details for an OS patch job. - -NOTES - This command is currently in alpha and might change without notice. If this - command fails with API permission errors despite specifying the correct - project, you might be trying to access an API with an invitation-only early - access allowlist. These variants are also available: - - $ gcloud compute os-config patch-jobs - - $ gcloud beta compute os-config patch-jobs - diff --git a/gcloud/alpha/compute/target-http-proxies/create b/gcloud/alpha/compute/target-http-proxies/create index f2626165a..9e2659a44 100644 --- a/gcloud/alpha/compute/target-http-proxies/create +++ b/gcloud/alpha/compute/target-http-proxies/create @@ -54,8 +54,8 @@ OPTIONAL FLAGS Represents the maximum amount of time that a TCP connection can be idle between the (downstream) client and the target HTTP proxy. If an HTTP keepalive timeout is not specified, the default value is 610 seconds. - For global external HTTP(S) load balancer, the minimum allowed value is - 5 seconds and the maximum allowed value is 1200 seconds. + For global external Application load balancer, the minimum allowed + value is 5 seconds and the maximum allowed value is 1200 seconds. --proxy-bind This flag applies when the load_balancing_scheme of the associated diff --git a/gcloud/alpha/compute/target-http-proxies/update b/gcloud/alpha/compute/target-http-proxies/update index 68f3ae9ea..96aa31f0e 100644 --- a/gcloud/alpha/compute/target-http-proxies/update +++ b/gcloud/alpha/compute/target-http-proxies/update @@ -52,7 +52,7 @@ OPTIONAL FLAGS Represents the maximum amount of time that a TCP connection can be idle between the (downstream) client and the target HTTP proxy. If an HTTP keepalive timeout is not specified, the default value is 610 - seconds. For global external HTTP(S) load balancer, the minimum + seconds. For global external Application load balancer, the minimum allowed value is 5 seconds and the maximum allowed value is 1200 seconds. diff --git a/gcloud/alpha/compute/target-https-proxies/create b/gcloud/alpha/compute/target-https-proxies/create index cafc6c2f7..e25906de8 100644 --- a/gcloud/alpha/compute/target-https-proxies/create +++ b/gcloud/alpha/compute/target-https-proxies/create @@ -83,8 +83,8 @@ OPTIONAL FLAGS Represents the maximum amount of time that a TCP connection can be idle between the (downstream) client and the target HTTP proxy. If an HTTP keepalive timeout is not specified, the default value is 610 seconds. - For global external HTTP(S) load balancer, the minimum allowed value is - 5 seconds and the maximum allowed value is 1200 seconds. + For global external Application load balancer, the minimum allowed + value is 5 seconds and the maximum allowed value is 1200 seconds. --proxy-bind This flag applies when the load_balancing_scheme of the associated diff --git a/gcloud/alpha/compute/target-https-proxies/update b/gcloud/alpha/compute/target-https-proxies/update index da07b6a3d..533528e44 100644 --- a/gcloud/alpha/compute/target-https-proxies/update +++ b/gcloud/alpha/compute/target-https-proxies/update @@ -172,7 +172,7 @@ FLAGS Represents the maximum amount of time that a TCP connection can be idle between the (downstream) client and the target HTTP proxy. If an HTTP keepalive timeout is not specified, the default value is 610 - seconds. For global external HTTP(S) load balancer, the minimum + seconds. For global external Application load balancer, the minimum allowed value is 5 seconds and the maximum allowed value is 1200 seconds. diff --git a/gcloud/alpha/compute/tpus/tpu-vm/create b/gcloud/alpha/compute/tpus/tpu-vm/create index 4ffd7f58c..98d95ee3e 100644 --- a/gcloud/alpha/compute/tpus/tpu-vm/create +++ b/gcloud/alpha/compute/tpus/tpu-vm/create @@ -107,7 +107,7 @@ OPTIONAL FLAGS Text description of the TPU. --internal-ips - Indicates that the IP addresses for the node should be internal. The + Indicate that the IP addresses for the node should be internal. The default is that external IP addresses will be associated with the TPU workers. diff --git a/gcloud/alpha/compute/tpus/tpu-vm/update b/gcloud/alpha/compute/tpus/tpu-vm/update index 40345e255..8a78263f0 100644 --- a/gcloud/alpha/compute/tpus/tpu-vm/update +++ b/gcloud/alpha/compute/tpus/tpu-vm/update @@ -4,7 +4,7 @@ NAME SYNOPSIS gcloud alpha compute tpus tpu-vm update (TPU : --zone=ZONE) [--add-tags=[TAGS,...]] [--async] [--description=DESCRIPTION] - [--update-labels=[KEY=VALUE,...]] + [--internal-ips] [--update-labels=[KEY=VALUE,...]] [--clear-labels | --remove-labels=[KEY,...]] [--clear-tags | --remove-tags=[TAG,...]] [--metadata-from-file=[METADATA_FROM_FILE,...] @@ -82,6 +82,11 @@ FLAGS --description=DESCRIPTION Text description of the TPU. + --internal-ips + Indicate that the IP addresses for the node should be internal. The + default is that external IP addresses will be associated with the TPU + workers. + --update-labels=[KEY=VALUE,...] Resource labels to update that represent user-provided metadata. If a label exists, its value is modified. Otherwise, a new label is created. diff --git a/gcloud/alpha/config/get b/gcloud/alpha/config/get index e3cb27550..89009f60e 100644 --- a/gcloud/alpha/config/get +++ b/gcloud/alpha/config/get @@ -370,6 +370,10 @@ AVAILABLE PROPERTIES Overrides API endpoint for gcloud events command group. Defaults to https://events.googleapis.com/ + faultinjectiontesting + Overrides API endpoint for gcloud fault-injection command group. + Defaults to https://faultinjectiontesting.googleapis.com/ + file Overrides API endpoint for gcloud filestore command group. Defaults to https://file.googleapis.com/ diff --git a/gcloud/alpha/config/help b/gcloud/alpha/config/help index 80def35c7..87a1e00ce 100644 --- a/gcloud/alpha/config/help +++ b/gcloud/alpha/config/help @@ -402,6 +402,10 @@ AVAILABLE PROPERTIES Overrides API endpoint for gcloud events command group. Defaults to https://events.googleapis.com/ + faultinjectiontesting + Overrides API endpoint for gcloud fault-injection command group. + Defaults to https://faultinjectiontesting.googleapis.com/ + file Overrides API endpoint for gcloud filestore command group. Defaults to https://file.googleapis.com/ diff --git a/gcloud/alpha/config/list b/gcloud/alpha/config/list index f6c90ab59..f7e30a9e7 100644 --- a/gcloud/alpha/config/list +++ b/gcloud/alpha/config/list @@ -414,6 +414,10 @@ AVAILABLE PROPERTIES Overrides API endpoint for gcloud events command group. Defaults to https://events.googleapis.com/ + faultinjectiontesting + Overrides API endpoint for gcloud fault-injection command group. + Defaults to https://faultinjectiontesting.googleapis.com/ + file Overrides API endpoint for gcloud filestore command group. Defaults to https://file.googleapis.com/ diff --git a/gcloud/alpha/config/set b/gcloud/alpha/config/set index c0d9500df..acbadf1ac 100644 --- a/gcloud/alpha/config/set +++ b/gcloud/alpha/config/set @@ -417,6 +417,10 @@ AVAILABLE PROPERTIES Overrides API endpoint for gcloud events command group. Defaults to https://events.googleapis.com/ + faultinjectiontesting + Overrides API endpoint for gcloud fault-injection command group. + Defaults to https://faultinjectiontesting.googleapis.com/ + file Overrides API endpoint for gcloud filestore command group. Defaults to https://file.googleapis.com/ diff --git a/gcloud/alpha/config/unset b/gcloud/alpha/config/unset index 60673c511..df63d8913 100644 --- a/gcloud/alpha/config/unset +++ b/gcloud/alpha/config/unset @@ -378,6 +378,10 @@ AVAILABLE PROPERTIES Overrides API endpoint for gcloud events command group. Defaults to https://events.googleapis.com/ + faultinjectiontesting + Overrides API endpoint for gcloud fault-injection command group. + Defaults to https://faultinjectiontesting.googleapis.com/ + file Overrides API endpoint for gcloud filestore command group. Defaults to https://file.googleapis.com/ diff --git a/gcloud/alpha/container/clusters/create b/gcloud/alpha/container/clusters/create index 15578f111..bfe6ef6db 100644 --- a/gcloud/alpha/container/clusters/create +++ b/gcloud/alpha/container/clusters/create @@ -19,6 +19,7 @@ SYNOPSIS [--cluster-version=CLUSTER_VERSION] [--create-subnetwork=[KEY=VALUE,...]] [--database-encryption-key=DATABASE_ENCRYPTION_KEY] + [--dataplane-v2-observability-mode=DATAPLANE_V2_OBSERVABILITY_MODE] [--default-max-pods-per-node=DEFAULT_MAX_PODS_PER_NODE] [--disable-default-snat] [--disable-pod-cidr-overprovision] [--disk-size=DISK_SIZE] [--disk-type=DISK_TYPE] [--enable-autorepair] @@ -28,6 +29,7 @@ SYNOPSIS [--enable-dataplane-v2] [--enable-fleet] [--enable-fqdn-network-policy] [--enable-gke-oidc] [--enable-google-cloud-access] [--enable-gvnic] [--enable-identity-service] [--enable-image-streaming] + [--enable-insecure-kubelet-readonly-port] [--enable-intra-node-visibility] [--enable-ip-alias] [--enable-kubernetes-alpha] [--enable-kubernetes-unstable-apis=API,[API,...]] @@ -69,11 +71,12 @@ SYNOPSIS [--workload-metadata=WORKLOAD_METADATA] [--workload-pool=WORKLOAD_POOL] [--workload-vulnerability-scanning=WORKLOAD_VULNERABILITY_SCANNING] [--additional-zones=ZONE,[ZONE,...] | --node-locations=ZONE,[ZONE,...]] - [--binauthz-policy=BINAUTHZ_POLICY + [--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] + [--disable-dataplane-v2-metrics | --enable-dataplane-v2-metrics] [[--enable-autoprovisioning : --autoprovisioning-config-file=AUTOPROVISIONING_CONFIG_FILE | [--max-cpu=MAX_CPU --max-memory=MAX_MEMORY @@ -326,6 +329,35 @@ FLAGS For more information, see https://cloud.google.com/kubernetes-engine/docs/how-to/encrypting-secrets. + --dataplane-v2-observability-mode=DATAPLANE_V2_OBSERVABILITY_MODE + Select Advanced Datapath Observability mode for the cluster. Defaults + to DISABLED. + + Advanced Datapath Observability allows for a real-time view into + pod-to-pod traffic within your cluster. + + Examples: + + $ gcloud alpha container clusters create \ + --dataplane-v2-observability-mode=DISABLED + + $ gcloud alpha container clusters create \ + --dataplane-v2-observability-mode=INTERNAL_VPC_LB + + $ gcloud alpha container clusters create \ + --dataplane-v2-observability-mode=EXTERNAL_LB + + DATAPLANE_V2_OBSERVABILITY_MODE must be one of: + + DISABLED + Disables Advanced Datapath Observability. + EXTERNAL_LB + Makes Advanced Datapath Observability available to the external + network. + INTERNAL_VPC_LB + Makes Advanced Datapath Observability available from the VPC + network. + --default-max-pods-per-node=DEFAULT_MAX_PODS_PER_NODE The default max number of pods per node for node pools in the cluster. @@ -482,6 +514,12 @@ FLAGS --enable-image-streaming Specifies whether to enable image streaming on cluster. + --enable-insecure-kubelet-readonly-port + Enables the Kubelet's insecure Read Only Port. + + To disable in an existing cluster, explicitly set flag to + --no-enable-insecure-kubelet-readonly-port. + --enable-intra-node-visibility Enable Intra-node visibility for this cluster. @@ -1244,7 +1282,7 @@ FLAGS Flags for Binary Authorization: - --binauthz-policy=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}. @@ -1293,6 +1331,14 @@ FLAGS vpc Configures the Cloud DNS zone to be private to the VPC Network. + At most one of these can be specified: + + --disable-dataplane-v2-metrics + Stops exposing advanced datapath flow metrics on node port. + + --enable-dataplane-v2-metrics + Exposes advanced datapath flow metrics on node port. + Node autoprovisioning --enable-autoprovisioning diff --git a/gcloud/alpha/container/clusters/create-auto b/gcloud/alpha/container/clusters/create-auto index 0a733845b..398164435 100644 --- a/gcloud/alpha/container/clusters/create-auto +++ b/gcloud/alpha/container/clusters/create-auto @@ -10,8 +10,10 @@ SYNOPSIS [--cluster-secondary-range-name=NAME] [--cluster-version=CLUSTER_VERSION] [--create-subnetwork=[KEY=VALUE,...]] - [--database-encryption-key=DATABASE_ENCRYPTION_KEY] [--enable-fleet] - [--enable-google-cloud-access] + [--database-encryption-key=DATABASE_ENCRYPTION_KEY] + [--dataplane-v2-observability-mode=DATAPLANE_V2_OBSERVABILITY_MODE] + [--enable-fleet] [--enable-google-cloud-access] + [--enable-insecure-kubelet-readonly-port] [--enable-kubernetes-unstable-apis=API,[API,...]] [--enable-master-global-access] [--fleet-project=PROJECT_ID_OR_NUMBER] [--logging=[COMPONENT,...]] [--monitoring=[COMPONENT,...]] @@ -22,7 +24,7 @@ SYNOPSIS [--workload-policies=WORKLOAD_POLICIES] [--workload-vulnerability-scanning=WORKLOAD_VULNERABILITY_SCANNING] [--binauthz-evaluation-mode=BINAUTHZ_EVALUATION_MODE - --binauthz-policy=BINAUTHZ_POLICY] + --binauthz-policy-bindings=[name=BINAUTHZ_POLICY,...]] [--enable-master-authorized-networks --master-authorized-networks=NETWORK,[NETWORK,...]] [--enable-private-endpoint @@ -155,6 +157,35 @@ FLAGS For more information, see https://cloud.google.com/kubernetes-engine/docs/how-to/encrypting-secrets. + --dataplane-v2-observability-mode=DATAPLANE_V2_OBSERVABILITY_MODE + Select Advanced Datapath Observability mode for the cluster. Defaults + to DISABLED. + + Advanced Datapath Observability allows for a real-time view into + pod-to-pod traffic within your cluster. + + Examples: + + $ gcloud alpha container clusters create-auto \ + --dataplane-v2-observability-mode=DISABLED + + $ gcloud alpha container clusters create-auto \ + --dataplane-v2-observability-mode=INTERNAL_VPC_LB + + $ gcloud alpha container clusters create-auto \ + --dataplane-v2-observability-mode=EXTERNAL_LB + + DATAPLANE_V2_OBSERVABILITY_MODE must be one of: + + DISABLED + Disables Advanced Datapath Observability. + EXTERNAL_LB + Makes Advanced Datapath Observability available to the external + network. + INTERNAL_VPC_LB + Makes Advanced Datapath Observability available from the VPC + network. + --enable-fleet Set cluster project as the fleet host project. This will register the cluster to the same project. To register the cluster to a fleet in a @@ -166,6 +197,12 @@ FLAGS Google Cloud can reach the public control plane endpoint of your cluster. + --enable-insecure-kubelet-readonly-port + Enables the Kubelet's insecure Read Only Port. + + To disable in an existing cluster, explicitly set flag to + --no-enable-insecure-kubelet-readonly-port. + --enable-kubernetes-unstable-apis=API,[API,...] Enable Kubernetes beta API features on this cluster. Beta APIs are not expected to be production ready and should be avoided in @@ -342,7 +379,7 @@ FLAGS POLICY_BINDINGS_AND_PROJECT_SINGLETON_POLICY_ENFORCE, PROJECT_SINGLETON_POLICY_ENFORCE. - --binauthz-policy=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/clusters/update b/gcloud/alpha/container/clusters/update index e85bed33e..d960141d2 100644 --- a/gcloud/alpha/container/clusters/update +++ b/gcloud/alpha/container/clusters/update @@ -8,12 +8,14 @@ SYNOPSIS | --autoscaling-profile=AUTOSCALING_PROFILE | --clear-fleet-project | --complete-credential-rotation | --complete-ip-rotation | --database-encryption-key=DATABASE_ENCRYPTION_KEY + | --dataplane-v2-observability-mode=DATAPLANE_V2_OBSERVABILITY_MODE | --disable-database-encryption | --disable-default-snat | --disable-workload-identity | --enable-autoscaling | --enable-cost-allocation | --enable-fleet | --enable-fqdn-network-policy | --enable-gke-oidc | --enable-google-cloud-access | --enable-identity-service - | --enable-image-streaming | --enable-intra-node-visibility + | --enable-image-streaming | --enable-insecure-kubelet-readonly-port + | --enable-intra-node-visibility | --enable-kubernetes-unstable-apis=API,[API,...] | --enable-l4-ilb-subsetting | --enable-legacy-authorization | --enable-logging-monitoring-system-only @@ -42,7 +44,7 @@ SYNOPSIS | --additional-pod-ipv4-ranges=NAME,[NAME,...] --remove-additional-pod-ipv4-ranges=NAME,[NAME,...] | --additional-zones=[ZONE,...] | --node-locations=ZONE,[ZONE,...] - | --binauthz-policy=BINAUTHZ_POLICY + | --binauthz-policy-bindings=[name=BINAUTHZ_POLICY,...] --binauthz-evaluation-mode=BINAUTHZ_EVALUATION_MODE | --enable-binauthz | --clear-maintenance-window | --remove-maintenance-exclusion=NAME @@ -58,7 +60,9 @@ SYNOPSIS --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 | [--enable-autoprovisioning + --cluster-dns-scope=CLUSTER_DNS_SCOPE + | --disable-dataplane-v2-metrics | --enable-dataplane-v2-metrics + | [--enable-autoprovisioning : --autoprovisioning-config-file=AUTOPROVISIONING_CONFIG_FILE | --autoprovisioning-image-type=AUTOPROVISIONING_IMAGE_TYPE --autoprovisioning-locations=ZONE,[ZONE,...] @@ -164,6 +168,35 @@ REQUIRED FLAGS For more information, see https://cloud.google.com/kubernetes-engine/docs/how-to/encrypting-secrets. + --dataplane-v2-observability-mode=DATAPLANE_V2_OBSERVABILITY_MODE + Select Advanced Datapath Observability mode for the cluster. Defaults + to DISABLED. + + Advanced Datapath Observability allows for a real-time view into + pod-to-pod traffic within your cluster. + + Examples: + + $ gcloud alpha container clusters update \ + --dataplane-v2-observability-mode=DISABLED + + $ gcloud alpha container clusters update \ + --dataplane-v2-observability-mode=INTERNAL_VPC_LB + + $ gcloud alpha container clusters update \ + --dataplane-v2-observability-mode=EXTERNAL_LB + + DATAPLANE_V2_OBSERVABILITY_MODE must be one of: + + DISABLED + Disables Advanced Datapath Observability. + EXTERNAL_LB + Makes Advanced Datapath Observability available to the external + network. + INTERNAL_VPC_LB + Makes Advanced Datapath Observability available from the VPC + network. + --disable-database-encryption Disable database encryption. @@ -257,6 +290,12 @@ REQUIRED FLAGS --enable-image-streaming Specifies whether to enable image streaming on cluster. + --enable-insecure-kubelet-readonly-port + Enables the Kubelet's insecure Read Only Port. + + To disable in an existing cluster, explicitly set flag to + --no-enable-insecure-kubelet-readonly-port. + --enable-intra-node-visibility Enable Intra-node visibility for this cluster. @@ -701,7 +740,7 @@ REQUIRED FLAGS Flags for Binary Authorization: - --binauthz-policy=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}. @@ -886,6 +925,14 @@ REQUIRED FLAGS vpc Configures the Cloud DNS zone to be private to the VPC Network. + At most one of these can be specified: + + --disable-dataplane-v2-metrics + Stops exposing advanced datapath flow metrics on node port. + + --enable-dataplane-v2-metrics + Exposes advanced datapath flow metrics on node port. + Node autoprovisioning --enable-autoprovisioning diff --git a/gcloud/alpha/container/fleet/fleetobservability/describe b/gcloud/alpha/container/fleet/fleetobservability/describe new file mode 100644 index 000000000..e9c29e479 --- /dev/null +++ b/gcloud/alpha/container/fleet/fleetobservability/describe @@ -0,0 +1,35 @@ +NAME + gcloud alpha container fleet fleetobservability describe - describes the + status of the Fleet Observability Feature resource + +SYNOPSIS + gcloud alpha container fleet fleetobservability describe + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) This command gets the detailed status of the Fleet Observability + Feature in a fleet. + +EXAMPLES + To describe the Fleet Observability Feature, run: + + $ gcloud alpha container fleet fleetobservability describe + +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 container fleet fleetobservability describe + + $ gcloud beta container fleet fleetobservability describe + diff --git a/gcloud/alpha/container/fleet/fleetobservability/disable b/gcloud/alpha/container/fleet/fleetobservability/disable new file mode 100644 index 000000000..3e2d18a98 --- /dev/null +++ b/gcloud/alpha/container/fleet/fleetobservability/disable @@ -0,0 +1,39 @@ +NAME + gcloud alpha container fleet fleetobservability disable - disables the + Fleet Observability Feature + +SYNOPSIS + gcloud alpha container fleet fleetobservability disable [--force] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) This command disables Fleet Observability Feature in a fleet. + +EXAMPLES + To disable the Fleet Observability Feature, run: + + $ gcloud alpha container fleet fleetobservability disable + +FLAGS + --force + Disable this feature, even if it is currently in use. Force disablement + may result in unexpected behavior. + +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 container fleet fleetobservability disable + + $ gcloud beta container fleet fleetobservability disable + diff --git a/gcloud/alpha/container/fleet/fleetobservability/enable b/gcloud/alpha/container/fleet/fleetobservability/enable new file mode 100644 index 000000000..9fc9e6f45 --- /dev/null +++ b/gcloud/alpha/container/fleet/fleetobservability/enable @@ -0,0 +1,34 @@ +NAME + gcloud alpha container fleet fleetobservability enable - enables the Fleet + Observability Feature + +SYNOPSIS + gcloud alpha container fleet fleetobservability enable + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) This command enables Fleet Observability Feature in a fleet. + +EXAMPLES + To enable the Fleet Observability Feature, run: + + $ gcloud alpha container fleet fleetobservability enable + +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 container fleet fleetobservability enable + + $ gcloud beta container fleet fleetobservability enable + diff --git a/gcloud/alpha/container/fleet/fleetobservability/help b/gcloud/alpha/container/fleet/fleetobservability/help new file mode 100644 index 000000000..d7b0ac9b4 --- /dev/null +++ b/gcloud/alpha/container/fleet/fleetobservability/help @@ -0,0 +1,42 @@ +NAME + gcloud alpha container fleet fleetobservability - manage Fleet + Observability Feature + +SYNOPSIS + gcloud alpha container fleet fleetobservability COMMAND + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Manage Fleet Observability Feature. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + describe + (ALPHA) Describes the status of the Fleet Observability Feature + resource. + + disable + (ALPHA) Disables the Fleet Observability Feature. + + enable + (ALPHA) Enables the Fleet Observability Feature. + + update + (ALPHA) Updates the Fleet Observability Feature resource. + +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 container fleet fleetobservability + + $ gcloud beta container fleet fleetobservability + diff --git a/gcloud/alpha/container/fleet/fleetobservability/update b/gcloud/alpha/container/fleet/fleetobservability/update new file mode 100644 index 000000000..34c9a70df --- /dev/null +++ b/gcloud/alpha/container/fleet/fleetobservability/update @@ -0,0 +1,62 @@ +NAME + gcloud alpha container fleet fleetobservability update - updates the Fleet + Observability Feature resource + +SYNOPSIS + gcloud alpha container fleet fleetobservability update + [--logging-config=LOGGING_CONFIG] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) This command updates the Fleet Observability Feature in a fleet. + +EXAMPLES + To describe the Fleet Observability Feature, run: + + $ gcloud alpha container fleet fleetobservability update \ + --logging-config=LOGGING-CONFIG + +FLAGS + --logging-config=LOGGING_CONFIG + Path of the YAML(or JSON) file that contains the logging + configurations. + + The JSON file is formatted as follows, with camelCase field naming: + + { + "loggingConfig": { + "defaultConfig": { + "mode": "COPY" + }, + "fleetScopeLogsConfig": { + "mode": "MOVE" + } + } + } + + The YAML file is formatted as follows, with camelCase field naming: + + --- + loggingConfig: + defaultConfig: + mode: COPY + fleetScopeLogsConfig: + mode: MOVE + +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 container fleet fleetobservability update + + $ gcloud beta container fleet fleetobservability update + diff --git a/gcloud/alpha/container/fleet/help b/gcloud/alpha/container/fleet/help index f0dc0cf60..a373d6cc9 100644 --- a/gcloud/alpha/container/fleet/help +++ b/gcloud/alpha/container/fleet/help @@ -54,6 +54,9 @@ GROUPS features (ALPHA) Manage Hub Feature resources. + fleetobservability + (ALPHA) Manage Fleet Observability Feature. + identity-service (ALPHA) Manage Identity Service Feature. diff --git a/gcloud/alpha/container/hub/fleetobservability/describe b/gcloud/alpha/container/hub/fleetobservability/describe new file mode 100644 index 000000000..d3668d670 --- /dev/null +++ b/gcloud/alpha/container/hub/fleetobservability/describe @@ -0,0 +1,35 @@ +NAME + gcloud alpha container hub fleetobservability describe - describes the + status of the Fleet Observability Feature resource + +SYNOPSIS + gcloud alpha container hub fleetobservability describe + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) This command gets the detailed status of the Fleet Observability + Feature in a fleet. + +EXAMPLES + To describe the Fleet Observability Feature, run: + + $ gcloud alpha container hub fleetobservability describe + +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 container hub fleetobservability describe + + $ gcloud beta container hub fleetobservability describe + diff --git a/gcloud/alpha/container/hub/fleetobservability/disable b/gcloud/alpha/container/hub/fleetobservability/disable new file mode 100644 index 000000000..6ea6e7d9f --- /dev/null +++ b/gcloud/alpha/container/hub/fleetobservability/disable @@ -0,0 +1,39 @@ +NAME + gcloud alpha container hub fleetobservability disable - disables the Fleet + Observability Feature + +SYNOPSIS + gcloud alpha container hub fleetobservability disable [--force] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) This command disables Fleet Observability Feature in a fleet. + +EXAMPLES + To disable the Fleet Observability Feature, run: + + $ gcloud alpha container hub fleetobservability disable + +FLAGS + --force + Disable this feature, even if it is currently in use. Force disablement + may result in unexpected behavior. + +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 container hub fleetobservability disable + + $ gcloud beta container hub fleetobservability disable + diff --git a/gcloud/alpha/container/hub/fleetobservability/enable b/gcloud/alpha/container/hub/fleetobservability/enable new file mode 100644 index 000000000..4dde793c4 --- /dev/null +++ b/gcloud/alpha/container/hub/fleetobservability/enable @@ -0,0 +1,33 @@ +NAME + gcloud alpha container hub fleetobservability enable - enables the Fleet + Observability Feature + +SYNOPSIS + gcloud alpha container hub fleetobservability enable [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) This command enables Fleet Observability Feature in a fleet. + +EXAMPLES + To enable the Fleet Observability Feature, run: + + $ gcloud alpha container hub fleetobservability enable + +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 container hub fleetobservability enable + + $ gcloud beta container hub fleetobservability enable + diff --git a/gcloud/alpha/container/hub/fleetobservability/help b/gcloud/alpha/container/hub/fleetobservability/help new file mode 100644 index 000000000..fb1e643e3 --- /dev/null +++ b/gcloud/alpha/container/hub/fleetobservability/help @@ -0,0 +1,42 @@ +NAME + gcloud alpha container hub fleetobservability - manage Fleet Observability + Feature + +SYNOPSIS + gcloud alpha container hub fleetobservability COMMAND + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Manage Fleet Observability Feature. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + describe + (ALPHA) Describes the status of the Fleet Observability Feature + resource. + + disable + (ALPHA) Disables the Fleet Observability Feature. + + enable + (ALPHA) Enables the Fleet Observability Feature. + + update + (ALPHA) Updates the Fleet Observability Feature resource. + +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 container hub fleetobservability + + $ gcloud beta container hub fleetobservability + diff --git a/gcloud/alpha/container/hub/fleetobservability/update b/gcloud/alpha/container/hub/fleetobservability/update new file mode 100644 index 000000000..314ec595c --- /dev/null +++ b/gcloud/alpha/container/hub/fleetobservability/update @@ -0,0 +1,62 @@ +NAME + gcloud alpha container hub fleetobservability update - updates the Fleet + Observability Feature resource + +SYNOPSIS + gcloud alpha container hub fleetobservability update + [--logging-config=LOGGING_CONFIG] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) This command updates the Fleet Observability Feature in a fleet. + +EXAMPLES + To describe the Fleet Observability Feature, run: + + $ gcloud alpha container hub fleetobservability update \ + --logging-config=LOGGING-CONFIG + +FLAGS + --logging-config=LOGGING_CONFIG + Path of the YAML(or JSON) file that contains the logging + configurations. + + The JSON file is formatted as follows, with camelCase field naming: + + { + "loggingConfig": { + "defaultConfig": { + "mode": "COPY" + }, + "fleetScopeLogsConfig": { + "mode": "MOVE" + } + } + } + + The YAML file is formatted as follows, with camelCase field naming: + + --- + loggingConfig: + defaultConfig: + mode: COPY + fleetScopeLogsConfig: + mode: MOVE + +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 container hub fleetobservability update + + $ gcloud beta container hub fleetobservability update + diff --git a/gcloud/alpha/container/hub/help b/gcloud/alpha/container/hub/help index f1b42baef..7fb6b8a8e 100644 --- a/gcloud/alpha/container/hub/help +++ b/gcloud/alpha/container/hub/help @@ -54,6 +54,9 @@ GROUPS features (ALPHA) Manage Hub Feature resources. + fleetobservability + (ALPHA) Manage Fleet Observability Feature. + identity-service (ALPHA) Manage Identity Service Feature. diff --git a/gcloud/alpha/edge-cloud/container/get-server-config b/gcloud/alpha/edge-cloud/container/get-server-config new file mode 100644 index 000000000..9ef376873 --- /dev/null +++ b/gcloud/alpha/edge-cloud/container/get-server-config @@ -0,0 +1,56 @@ +NAME + gcloud alpha edge-cloud container get-server-config - get server config + +SYNOPSIS + gcloud alpha edge-cloud container get-server-config [--location=LOCATION] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) gcloud alpha edge-cloud container get-server-config gets the server + configuration for an Edge Container location. This configuration includes + the default cluster version, the supported cluster versions and version + configuration for each release channel. + +EXAMPLES + To get server config in region us-central1, run: + + $ gcloud alpha edge-cloud container get-server-config \ + --location=us-central1 + +FLAGS + Location resource - The location of the server configuration. This + represents a Cloud resource. (NOTE) Some attributes are not given + arguments in this group but can be set in other ways. + + To set the project attribute: + ◆ provide the argument --location on the command line with a fully + specified name; + ◆ set the property edge_container/location with a fully specified name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + --location=LOCATION + ID of the location or fully qualified identifier for the location. + + To set the location attribute: + ▸ provide the argument --location on the command line; + ▸ set the property edge_container/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. + +API REFERENCE + This command uses the edgecontainer/v1alpha API. The full documentation for + this API can be found at: https://cloud.google.com/edge-cloud + +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/edge-cloud/container/help b/gcloud/alpha/edge-cloud/container/help index 416ef92b1..aba95a2e7 100644 --- a/gcloud/alpha/edge-cloud/container/help +++ b/gcloud/alpha/edge-cloud/container/help @@ -2,7 +2,7 @@ NAME gcloud alpha edge-cloud container - manage Edge Container resources SYNOPSIS - gcloud alpha edge-cloud container GROUP [GCLOUD_WIDE_FLAG ...] + gcloud alpha edge-cloud container GROUP | COMMAND [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Manage Edge Container resources. @@ -34,6 +34,12 @@ GROUPS zones (ALPHA) Inspect Edge Container zones. +COMMANDS + COMMAND is one of the following: + + get-server-config + (ALPHA) Get server config. + 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/firestore/databases/delete b/gcloud/alpha/firestore/databases/delete new file mode 100644 index 000000000..40576eb33 --- /dev/null +++ b/gcloud/alpha/firestore/databases/delete @@ -0,0 +1,54 @@ +NAME + gcloud alpha firestore databases delete - delete a Google Cloud Firestore + database + +SYNOPSIS + gcloud alpha firestore databases delete --database=DATABASE + [--allow-missing] [--etag=ETAG] [GCLOUD_WIDE_FLAG ...] + +EXAMPLES + To delete a Firestore database test. + + $ gcloud alpha firestore databases delete --database=test + + To delete the Firestore (default) database. + + $ gcloud alpha firestore databases delete --database=(default) + + To delete a Firestore database test providing etag. + + $ gcloud alpha firestore databases delete --database=test --etag=etag + + To delete a Firestore database test and allow missing. + + $ gcloud alpha firestore databases delete --database=test \ + --allow-missing + +REQUIRED FLAGS + --database=DATABASE + The database to operate on. + +OPTIONAL FLAGS + --allow-missing + If set and the Database is not found, the request will succeed but no + action will be taken. + + --etag=ETAG + The current etag of the Database. If an etag is provided and does not + match the current etag of the database, deletion will be blocked and a + FAILED_PRECONDITION error will be returned. + +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/databases/help b/gcloud/alpha/firestore/databases/help index 25c8919d2..628cbe53b 100644 --- a/gcloud/alpha/firestore/databases/help +++ b/gcloud/alpha/firestore/databases/help @@ -19,6 +19,9 @@ COMMANDS create (ALPHA) Create a Google Cloud Firestore database via Firestore API. + delete + (ALPHA) Delete a Google Cloud Firestore database. + describe (ALPHA) Describes information about a Cloud Firestore database. diff --git a/gcloud/alpha/functions/deploy b/gcloud/alpha/functions/deploy index 85e87d5bc..fd12d2367 100644 --- a/gcloud/alpha/functions/deploy +++ b/gcloud/alpha/functions/deploy @@ -626,6 +626,16 @@ FLAGS argument or as multiple arguments. This is only relevant when --gen2 is provided. + The provided attribute/value pair will be used with the + match-path-pattern operator to configure the trigger, see + https://cloud.google.com/eventarc/docs/reference/rest/v1/projects.locations.triggers#eventfilter + and http://cloud/eventarc/docs/path-patterns for more details about + on how to construct path patterns. + + For example, to filter on events for Compute Engine VMs in a given + zone: + --trigger-event-filters-path-pattern=resourceName='/projects/*/zones/us-central1-a/instances/*' + GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, diff --git a/gcloud/alpha/iam/workforce-pools/providers/create-oidc b/gcloud/alpha/iam/workforce-pools/providers/create-oidc index d28d57c95..7b9adf013 100644 --- a/gcloud/alpha/iam/workforce-pools/providers/create-oidc +++ b/gcloud/alpha/iam/workforce-pools/providers/create-oidc @@ -8,8 +8,9 @@ SYNOPSIS --attribute-mapping=[ATTRIBUTE_MAPPING,...] --client-id=CLIENT_ID --issuer-uri=ISSUER_URI (--web-sso-assertion-claims-behavior=WEB_SSO_ASSERTION_CLAIMS_BEHAVIOR - --web-sso-response-type=WEB_SSO_RESPONSE_TYPE) [--async] - [--attribute-condition=ATTRIBUTE_CONDITION] + --web-sso-response-type=WEB_SSO_RESPONSE_TYPE + : --web-sso-additional-scopes=[WEB_SSO_ADDITIONAL_SCOPES,...]) + [--async] [--attribute-condition=ATTRIBUTE_CONDITION] [--client-secret-value=CLIENT_SECRET_VALUE] [--description=DESCRIPTION] [--disabled] [--display-name=DISPLAY_NAME] [GCLOUD_WIDE_FLAG ...] @@ -28,9 +29,11 @@ EXAMPLES --description="My workforce pool provider description." \ --disabled --attribute-mapping="google.subject=assertion.sub" \ --attribute-condition="true" --client-id="client-id" \ + --client-secret-value="client-secret" \ --issuer-uri="https://test-idp.com" \ - --web-sso-response-type=id-token \ - --web-sso-assertion-claims-behavior=only-id-token-claims + --web-sso-response-type="code" \ + --web-sso-assertion-claims-behavior="merge-user-info-over-id-tok\ + en-claims" --web-sso-additional-scopes="groups,photos" POSITIONAL ARGUMENTS Workforce pool provider resource - The workforce pool provider to create. @@ -182,6 +185,15 @@ REQUIRED FLAGS This flag argument must be specified if any of the other arguments in this group are specified. + --web-sso-additional-scopes=[WEB_SSO_ADDITIONAL_SCOPES,...] + Additional scopes to request for the OIDC authentication on top of + scopes requested by default. By default, the openid, profile and + email scopes that are supported by the identity provider are + requested. + + Each additional scope may be at most 256 characters. A maximum of 10 + additional scopes may be configured. + OPTIONAL FLAGS --async Return immediately, without waiting for the operation in progress to diff --git a/gcloud/alpha/iam/workforce-pools/providers/update-oidc b/gcloud/alpha/iam/workforce-pools/providers/update-oidc index 5ed1b5780..bc2e270b7 100644 --- a/gcloud/alpha/iam/workforce-pools/providers/update-oidc +++ b/gcloud/alpha/iam/workforce-pools/providers/update-oidc @@ -9,6 +9,7 @@ SYNOPSIS [--attribute-mapping=[ATTRIBUTE_MAPPING,...]] [--client-id=CLIENT_ID] [--description=DESCRIPTION] [--disabled] [--display-name=DISPLAY_NAME] [--issuer-uri=ISSUER_URI] + [--web-sso-additional-scopes=[WEB_SSO_ADDITIONAL_SCOPES,...]] [--web-sso-assertion-claims-behavior=WEB_SSO_ASSERTION_CLAIMS_BEHAVIOR] [--web-sso-response-type=WEB_SSO_RESPONSE_TYPE] [--clear-client-secret | --client-secret-value=CLIENT_SECRET_VALUE] @@ -29,9 +30,11 @@ EXAMPLES --description="My workforce pool provider description." \ --disabled --attribute-mapping="google.subject=assertion.sub" \ --attribute-condition="true" --client-id="client-id" \ + --client-secret-value="client-secret" \ --issuer-uri="https://test-idp.com" \ - --web-sso-response-type=id-token \ - --web-sso-assertion-claims-behavior=only-id-token-claims + --web-sso-response-type="code" \ + --web-sso-assertion-claims-behavior="merge-user-info-over-id-tok\ + en-claims" --web-sso-additional-scopes="groups,photos" POSITIONAL ARGUMENTS Workforce pool provider resource - The workforce pool provider to update. @@ -192,6 +195,14 @@ FLAGS --issuer-uri=ISSUER_URI The OIDC issuer URI. Must be a valid URI using the 'https' scheme. + --web-sso-additional-scopes=[WEB_SSO_ADDITIONAL_SCOPES,...] + Additional scopes to request for the OIDC authentication on top of + scopes requested by default. By default, the openid, profile and email + scopes that are supported by the identity provider are requested. + + Each additional scope may be at most 256 characters. A maximum of 10 + additional scopes may be configured. + --web-sso-assertion-claims-behavior=WEB_SSO_ASSERTION_CLAIMS_BEHAVIOR The behavior for how OIDC Claims are included in the assertion object used for attribute mapping and attribute condition. Use diff --git a/gcloud/alpha/infra-manager/deployments/apply b/gcloud/alpha/infra-manager/deployments/apply new file mode 100644 index 000000000..f5e7ffc04 --- /dev/null +++ b/gcloud/alpha/infra-manager/deployments/apply @@ -0,0 +1,256 @@ +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=IMPORT_EXISTING_RESOURCES] + [--labels=[KEY=VALUE,...]] [--service-account=SERVICE_ACCOUNT] + [--worker-pool=WORKER_POOL] + [--input-values=[KEY=VALUE,...] --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 --stage-bucket=STAGE_BUCKET] + [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/location/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/location/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/location/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 blueprints/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=IMPORT_EXISTING_RESOURCES + By default, Cloud Config Manager will return a failure when Terraform + encounters a 409 code (resource conflict error) during actuation. If + this flag is set to true, Cloud Config 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}The default Cloud + Build SA will be used initially if this field is not set. + + --worker-pool=WORKER_POOL + User-specified Worker Pool resource in which the Cloud Build jobwill + execute. Format: + projects/{project}/locations/{location}/workerPools/{workerPoolId} + + --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 + + 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" + + --stage-bucket=STAGE_BUCKET + Use in conjunction with --local-source to specify a destination + storage bucket for uploading local files. + + If unspecified, the bucket defaults to gs://PROJECT_NAME_blueprints. + Uploaded content will appear in the source object under a name + comprised of the timestamp and a UUID. The final output destination + looks like this: + gs://BUCKET/source/1615850562.234312-044e784992744951b0cd71c0b011edce/ + + Examples: + + Create a deployment from a local storage path ./path/to/blueprint and + stage-bucket gs://my-bucket: + + $ gcloud alpha infra-manager deployments apply \ + projects/p1/location/us-central1/deployments/my-deployment \ + --local-source="./path/to/blueprint" \ + --stage-bucket="gs://my-bucket" + +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/infra-manager/deployments/delete b/gcloud/alpha/infra-manager/deployments/delete new file mode 100644 index 000000000..66b107e95 --- /dev/null +++ b/gcloud/alpha/infra-manager/deployments/delete @@ -0,0 +1,79 @@ +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/v1alpha2 API. The full documentation for this + API can be found at: https://cloud.google.com/ + +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/infra-manager/deployments/describe b/gcloud/alpha/infra-manager/deployments/describe new file mode 100644 index 000000000..ebf8897e9 --- /dev/null +++ b/gcloud/alpha/infra-manager/deployments/describe @@ -0,0 +1,67 @@ +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/v1alpha2 API. The full documentation for this + API can be found at: https://cloud.google.com/ + +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/infra-manager/deployments/help b/gcloud/alpha/infra-manager/deployments/help new file mode 100644 index 000000000..f65351147 --- /dev/null +++ b/gcloud/alpha/infra-manager/deployments/help @@ -0,0 +1,35 @@ +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. + + list + (ALPHA) List deployments. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/compute/os-config/patch-jobs/list-instance-details b/gcloud/alpha/infra-manager/deployments/list similarity index 59% rename from gcloud/alpha/compute/os-config/patch-jobs/list-instance-details rename to gcloud/alpha/infra-manager/deployments/list index 3b1d1e695..59ea60b2f 100644 --- a/gcloud/alpha/compute/os-config/patch-jobs/list-instance-details +++ b/gcloud/alpha/infra-manager/deployments/list @@ -1,36 +1,37 @@ NAME - gcloud alpha compute os-config patch-jobs list-instance-details - list the - instance details for an OS patch job + gcloud alpha infra-manager deployments list - list deployments SYNOPSIS - gcloud alpha compute os-config patch-jobs list-instance-details PATCH_JOB + gcloud alpha infra-manager deployments list --location=LOCATION [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] - [--sort-by=[FIELD,...]] [GCLOUD_WIDE_FLAG ...] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) List deployments EXAMPLES - To list the instance details for each instance in the patch job job1, run: + To list all deployments at location us-central1, run: - $ gcloud alpha compute os-config patch-jobs list-instance-details \ - job1 + $ gcloud alpha infra-manager deployments list --location=us-central1 -POSITIONAL ARGUMENTS - Patch job resource - Patch job to list instance details. This represents a - Cloud resource. (NOTE) Some attributes are not given arguments in this - group but can be set in other ways. +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. To set the project attribute: - ◆ provide the argument patch_job on the command line with a fully + ◆ provide the argument --location on the command line with a fully specified name; - ◆ provide the argument --project on the command line; - ◆ set the property core/project. + ◆ set the property core/project; + ◆ provide the argument --project on the command line. This must be specified. - PATCH_JOB - ID of the patch_job or fully qualified identifier for the patch_job. + --location=LOCATION + ID of the location or fully qualified identifier for the location. - To set the patch_job attribute: - ▸ provide the argument patch_job on the command line. + To set the location attribute: + ▸ provide the argument --location on the command line. LIST COMMAND FLAGS --filter=EXPRESSION @@ -58,6 +59,12 @@ LIST COMMAND FLAGS order on that field. This flag interacts with other flags that are applied in this order: --flatten, --sort-by, --filter, --limit. + --uri + Print a list of resource URIs instead of the default output, and change + the command output to a list of URIs. If this flag is used with + --format, the formatting is applied on this URI list. To display URIs + alongside other keys instead, use the uri() transform. + GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, @@ -66,13 +73,13 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. +API REFERENCE + This command uses the config/v1alpha2 API. The full documentation for this + API can be found at: https://cloud.google.com/ + NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. These variants are also available: - - $ gcloud compute os-config patch-jobs list-instance-details - - $ gcloud beta compute os-config patch-jobs list-instance-details + access allowlist. diff --git a/gcloud/alpha/infra-manager/help b/gcloud/alpha/infra-manager/help new file mode 100644 index 000000000..2ad7f770b --- /dev/null +++ b/gcloud/alpha/infra-manager/help @@ -0,0 +1,29 @@ +NAME + gcloud alpha infra-manager - manage Config resources + +SYNOPSIS + gcloud alpha infra-manager GROUP [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Manage Config 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. + + 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. + diff --git a/gcloud/alpha/infra-manager/revisions/describe b/gcloud/alpha/infra-manager/revisions/describe new file mode 100644 index 000000000..05c178095 --- /dev/null +++ b/gcloud/alpha/infra-manager/revisions/describe @@ -0,0 +1,76 @@ +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/v1alpha2 API. The full documentation for this + API can be found at: https://cloud.google.com/ + +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/infra-manager/revisions/help b/gcloud/alpha/infra-manager/revisions/help new file mode 100644 index 000000000..2768e21b1 --- /dev/null +++ b/gcloud/alpha/infra-manager/revisions/help @@ -0,0 +1,29 @@ +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. + + 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. + diff --git a/gcloud/alpha/compute/os-config/guest-policies/list b/gcloud/alpha/infra-manager/revisions/list similarity index 54% rename from gcloud/alpha/compute/os-config/guest-policies/list rename to gcloud/alpha/infra-manager/revisions/list index d0d4c1ac4..d8fd12571 100644 --- a/gcloud/alpha/compute/os-config/guest-policies/list +++ b/gcloud/alpha/infra-manager/revisions/list @@ -1,47 +1,53 @@ NAME - gcloud alpha compute os-config guest-policies list - list guest policies in - a project, a folder, or an organization + gcloud alpha infra-manager revisions list - list revisions SYNOPSIS - gcloud alpha compute os-config guest-policies list - [--folder=FOLDER_ID | --organization=ORGANIZATION_ID - | --project=PROJECT_ID] [--filter=EXPRESSION] [--limit=LIMIT] - [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + gcloud alpha infra-manager revisions list + (--deployment=DEPLOYMENT : --location=LOCATION) [--filter=EXPRESSION] + [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] +DESCRIPTION + (ALPHA) List revisions for a deployment + EXAMPLES - To list guest policies in the current project, run: + To list all revisions for deployment + projects/p1/locations/l1/deployments/d1, run: - $ gcloud alpha compute os-config guest-policies list + $ gcloud alpha infra-manager revisions list \ + --deployment=projects/p1/locations/l1/deployments/d1 - To list guest policies in the organization 12345, run: +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. - $ gcloud alpha compute os-config guest-policies list \ - --organization=12345 + 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. -FLAGS - The scope of the guest policies. If a scope is not specified, the current - project is used as the default. + This must be specified. - At most one of these can be specified: + --deployment=DEPLOYMENT + ID of the deployment or fully qualified identifier for the + deployment. - --folder=FOLDER_ID - The folder of the guest policies to list. + To set the deployment attribute: + ▸ provide the argument --deployment on the command line. - --organization=ORGANIZATION_ID - The organization of the guest policies to list. + This flag argument must be specified if any of the other arguments in + this group are specified. - --project=PROJECT_ID - The project name to use. If a project name is not specified, then the - current project is used. The current project can be listed using - gcloud config list --format='text(core.project)' and can be set using - gcloud config set project PROJECTID. + --location=LOCATION + locations TBD - --project and its fallback core/project property play two roles. It - specifies the project of the resource to operate on, and also - specifies the project for API enablement check, quota, and billing. - To specify a different project for quota and billing, use - --billing-project or billing/quota_project property. + 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. LIST COMMAND FLAGS --filter=EXPRESSION @@ -83,11 +89,13 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. +API REFERENCE + This command uses the config/v1alpha2 API. The full documentation for this + API can be found at: https://cloud.google.com/ + NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: - - $ gcloud beta compute os-config guest-policies list + access allowlist. diff --git a/gcloud/alpha/memcache/instances/create b/gcloud/alpha/memcache/instances/create index fb7bff79d..3f5032298 100644 --- a/gcloud/alpha/memcache/instances/create +++ b/gcloud/alpha/memcache/instances/create @@ -11,6 +11,7 @@ SYNOPSIS [--maintenance-window-duration=MAINTENANCE_WINDOW_DURATION] [--maintenance-window-start-time=MAINTENANCE_WINDOW_START_TIME] [--memcached-version=MEMCACHED_VERSION] [--parameters=KEY=VALUE] + [--reserved-ip-range-id=[RESERVED_IP_RANGE_ID,...]] [--zones=[ZONES,...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -170,6 +171,11 @@ OPTIONAL FLAGS hash-algorithm This is an enum with accepted values of ["jenkins", "murmur3"]. + --reserved-ip-range-id=[RESERVED_IP_RANGE_ID,...] + Contains the name of allocated IP address ranges associated with the + private service access connection for example, "test-default" + associated with IP range 10.0.0.0/29. + --zones=[ZONES,...] List of zones for the memcache nodes. The nodes will be divided equally across the given zones up to --node-count value. If not provided, the diff --git a/gcloud/alpha/ml-engine/models/remove-iam-policy-binding b/gcloud/alpha/ml-engine/models/remove-iam-policy-binding index bc47a49bd..e42f738c5 100644 --- a/gcloud/alpha/ml-engine/models/remove-iam-policy-binding +++ b/gcloud/alpha/ml-engine/models/remove-iam-policy-binding @@ -28,7 +28,7 @@ EXAMPLES --member='allAuthenticatedUsers' --role='roles/ml.admin' See https://cloud.google.com/iam/docs/managing-policies for details of - policy role and principal types. + policy role and member types. POSITIONAL ARGUMENTS Model resource - The AI Platform model for which to remove IAM policy diff --git a/gcloud/alpha/monitoring/policies/help b/gcloud/alpha/monitoring/policies/help index b50fad0e1..f600d79d5 100644 --- a/gcloud/alpha/monitoring/policies/help +++ b/gcloud/alpha/monitoring/policies/help @@ -40,6 +40,9 @@ COMMANDS list (ALPHA) List alerting policies. + migrate + (ALPHA) Migrate a new alerting policy. + update (ALPHA) Updates an alerting policy. diff --git a/gcloud/alpha/monitoring/policies/migrate b/gcloud/alpha/monitoring/policies/migrate new file mode 100644 index 000000000..d79f065ba --- /dev/null +++ b/gcloud/alpha/monitoring/policies/migrate @@ -0,0 +1,40 @@ +NAME + gcloud alpha monitoring policies migrate - migrate a new alerting policy + +SYNOPSIS + gcloud alpha monitoring policies migrate + [--channels-from-prometheus-alertmanager-yaml=PROMETHEUS_ALERT_MANAGER_FILE_PATH --policies-from-prometheus-alert-rules-yaml=[PROMETHEUS_ALERT_RULE_FILE_PATHS, + ...]] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Creates a new alerting policies and/or notification channels based + on provided Prometheus files. The rules YAML file, which holds the alert + rules, must be specified as a file through the + --policies-from-prometheus-alert-rules-yaml flag. + +FLAGS + --channels-from-prometheus-alertmanager-yaml=PROMETHEUS_ALERT_MANAGER_FILE_PATH + Prometheus alert manager YAML file to be converted to Cloud Monitoring + notification channels. Specifying this flag with the + --policies-from-prometheus-alert-rules-yaml flag puts the newly created + notification channels into the translated Alert Policies' definition. + + --policies-from-prometheus-alert-rules-yaml=[PROMETHEUS_ALERT_RULE_FILE_PATHS,...] + One or more Prometheus alert rule YAML files (separated by commas if + multiple) to be converted to Cloud Alerting Policies. Example: + --policies-from-prometheus-alert-rules-yaml=rules_1.yaml,rules_2.yaml + +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/network-security/security-profile-groups/create b/gcloud/alpha/network-security/security-profile-groups/create index 4dee90a0e..9f655f405 100644 --- a/gcloud/alpha/network-security/security-profile-groups/create +++ b/gcloud/alpha/network-security/security-profile-groups/create @@ -13,10 +13,10 @@ DESCRIPTION (ALPHA) Create a new Security Profile Group with the given name. EXAMPLES - To create a Security Profile Group with the name my-security-profile-group - (Either a fully specified path or --location and --organization flags for - SPG should be specified), --threat-prevention-profile my-security-profile - and optional description as optional description, run: + To create a Security Profile Group with the name my-security-profile-group, + with a fully specified threat prevention profile using + --threat-prevention-profile flag and optional description as optional + description, run: $ gcloud alpha network-security security-profile-groups create \ my-security-profile-group --organization=1234 \ @@ -43,12 +43,13 @@ POSITIONAL ARGUMENTS arguments in this group are specified. --location=LOCATION - Location Id. + Location Id of the resource. To set the location attribute: ▸ provide the argument security_profile_group on the command line with a fully specified name; - ▸ provide the argument --location on the command line. + ▸ provide the argument --location on the command line; + ▸ use default global location . --organization=ORGANIZATION Organization number. diff --git a/gcloud/alpha/network-security/security-profile-groups/delete b/gcloud/alpha/network-security/security-profile-groups/delete index 10340af70..78abe138d 100644 --- a/gcloud/alpha/network-security/security-profile-groups/delete +++ b/gcloud/alpha/network-security/security-profile-groups/delete @@ -12,9 +12,7 @@ DESCRIPTION (ALPHA) Delete the specified Security Profile Group. EXAMPLES - To delete an Security Profile Group called my-security-profile-group - (Either a fully specified path or --location and --organization flags for - SPG should be specified) run: + To delete an Security Profile Group called my-security-profile-group run: $ gcloud alpha network-security security-profile-groups delete \ my-security-profile-group --organization=1234 --location=global @@ -37,12 +35,13 @@ POSITIONAL ARGUMENTS arguments in this group are specified. --location=LOCATION - Location Id. + Location Id of the resource. To set the location attribute: ▸ provide the argument security_profile_group on the command line with a fully specified name; - ▸ provide the argument --location on the command line. + ▸ provide the argument --location on the command line; + ▸ use default global location . --organization=ORGANIZATION Organization number. diff --git a/gcloud/alpha/network-security/security-profile-groups/describe b/gcloud/alpha/network-security/security-profile-groups/describe index a78ad8c96..1113de348 100644 --- a/gcloud/alpha/network-security/security-profile-groups/describe +++ b/gcloud/alpha/network-security/security-profile-groups/describe @@ -13,8 +13,7 @@ DESCRIPTION EXAMPLES To show details of a Security Profile Group named my-security-profile-group - (Either a fully specified path or --location and --organization flags for - SPG should be specified) run: + run: $ gcloud alpha network-security security-profile-groups describe \ my-security-profile-group --organization=1234 --location=global @@ -37,12 +36,13 @@ POSITIONAL ARGUMENTS arguments in this group are specified. --location=LOCATION - Location Id. + Location Id of the resource. To set the location attribute: ▸ provide the argument security_profile_group on the command line with a fully specified name; - ▸ provide the argument --location on the command line. + ▸ provide the argument --location on the command line; + ▸ use default global location . --organization=ORGANIZATION Organization number. diff --git a/gcloud/alpha/network-security/security-profile-groups/list b/gcloud/alpha/network-security/security-profile-groups/list index 3bcd567ad..192974f13 100644 --- a/gcloud/alpha/network-security/security-profile-groups/list +++ b/gcloud/alpha/network-security/security-profile-groups/list @@ -12,7 +12,7 @@ DESCRIPTION (ALPHA) List all Security Profile Groups in the specified location. EXAMPLES - To list Security Profile Groups in specifed location and organization, run: + To list Security Profile Groups in specifed location, run: $ gcloud alpha network-security security-profile-groups list \ --location=global diff --git a/gcloud/alpha/network-security/security-profile-groups/update b/gcloud/alpha/network-security/security-profile-groups/update index ee6c5250a..16e020227 100644 --- a/gcloud/alpha/network-security/security-profile-groups/update +++ b/gcloud/alpha/network-security/security-profile-groups/update @@ -14,9 +14,8 @@ DESCRIPTION (ALPHA) Update the details of a Security Profile Group. EXAMPLES - To update an SPG with new Threat prevention profile my-new-security-profile - (Either a fully specified path or --location and --organization flags for - SPG should be specified), run: + To update a Security Profile Group with new threat prevention profile + my-new-security-profile, run: $ gcloud alpha network-security security-profile-groups update \ my-security-profile-group --organization=1234 \ @@ -43,12 +42,13 @@ POSITIONAL ARGUMENTS arguments in this group are specified. --location=LOCATION - Location Id. + Location Id of the resource. To set the location attribute: ▸ provide the argument security_profile_group on the command line with a fully specified name; - ▸ provide the argument --location on the command line. + ▸ provide the argument --location on the command line; + ▸ use default global location . --organization=ORGANIZATION Organization number. diff --git a/gcloud/alpha/network-security/security-profiles/threat-prevention/add-override b/gcloud/alpha/network-security/security-profiles/threat-prevention/add-override index a5c77ab1f..c73bdd912 100644 --- a/gcloud/alpha/network-security/security-profiles/threat-prevention/add-override +++ b/gcloud/alpha/network-security/security-profiles/threat-prevention/add-override @@ -28,7 +28,7 @@ EXAMPLES my-security-profile is the name of the Security Profile in the format organizations/{organizationID}/locations/{location}/securityProfiles/ {security_profile_id} where organizationID is the organization ID to which - the changes should apply, location either global or region specified and + the changes should apply, location - global specified and security_profile_id the Security Profile Identifier POSITIONAL ARGUMENTS @@ -48,7 +48,7 @@ POSITIONAL ARGUMENTS arguments in this group are specified. --location=LOCATION - location of the security_profile Global|Region. + location of the security_profile - Global. To set the location attribute: ▸ provide the argument security_profile on the command line with a diff --git a/gcloud/alpha/network-security/security-profiles/threat-prevention/create b/gcloud/alpha/network-security/security-profiles/threat-prevention/create index c68b63cc6..3f2457734 100644 --- a/gcloud/alpha/network-security/security-profiles/threat-prevention/create +++ b/gcloud/alpha/network-security/security-profiles/threat-prevention/create @@ -11,8 +11,7 @@ DESCRIPTION (ALPHA) Create a new Security Profile with the given name. EXAMPLES - To create a Security Profile with the name my-security-profile which - includes location as global or region specifed and organization ID, + To create a Security Profile with the name my-security-profile and an optional description as New Security Profile, run: $ gcloud alpha network-security security-profiles \ @@ -36,7 +35,7 @@ POSITIONAL ARGUMENTS arguments in this group are specified. --location=LOCATION - location of the security_profile Global|Region. + location of the security_profile - Global. To set the location attribute: ▸ provide the argument security_profile on the command line with a diff --git a/gcloud/alpha/network-security/security-profiles/threat-prevention/delete b/gcloud/alpha/network-security/security-profiles/threat-prevention/delete index 1338bc6bc..101ef664a 100644 --- a/gcloud/alpha/network-security/security-profiles/threat-prevention/delete +++ b/gcloud/alpha/network-security/security-profiles/threat-prevention/delete @@ -11,8 +11,7 @@ DESCRIPTION (ALPHA) Delete the specified Security Profile. EXAMPLES - To delete a Security Profile called my-security-profile which includes - location as global or region specifed and organization ID, run: + To delete a Security Profile called my-security-profile run: $ gcloud alpha network-security security-profiles \ threat-prevention delete my-security-profile @@ -35,12 +34,13 @@ POSITIONAL ARGUMENTS arguments in this group are specified. --location=LOCATION - Location Id. + Location Id of the resource. To set the location attribute: ▸ provide the argument security_profile on the command line with a fully specified name; - ▸ provide the argument --location on the command line. + ▸ provide the argument --location on the command line; + ▸ use default global location . --organization=ORGANIZATION Organization number. diff --git a/gcloud/alpha/network-security/security-profiles/threat-prevention/delete-override b/gcloud/alpha/network-security/security-profiles/threat-prevention/delete-override index b2b3f25f5..1b5bddccd 100644 --- a/gcloud/alpha/network-security/security-profiles/threat-prevention/delete-override +++ b/gcloud/alpha/network-security/security-profiles/threat-prevention/delete-override @@ -27,7 +27,7 @@ EXAMPLES my-security-profile is the name of the Security Profile in the format organizations/{organizationID}/locations/{location}/securityProfiles/ {security_profile_id} where organizationID is the organization ID to which - the changes should apply, location either global or region specified and + the changes should apply, location - global specified and security_profile_id the Security Profile Identifier POSITIONAL ARGUMENTS @@ -47,7 +47,7 @@ POSITIONAL ARGUMENTS arguments in this group are specified. --location=LOCATION - location of the security_profile Global|Region. + location of the security_profile - Global. To set the location attribute: ▸ provide the argument security_profile on the command line with a diff --git a/gcloud/alpha/network-security/security-profiles/threat-prevention/list b/gcloud/alpha/network-security/security-profiles/threat-prevention/list index d210b2d23..e179f2a02 100644 --- a/gcloud/alpha/network-security/security-profiles/threat-prevention/list +++ b/gcloud/alpha/network-security/security-profiles/threat-prevention/list @@ -12,7 +12,7 @@ DESCRIPTION (ALPHA) List all Security Profiles in the specified location. EXAMPLES - To list Security Profiles in specifed location and organization, run: + To list Security Profiles in specifed location run: $ gcloud alpha network-security security-profiles \ threat-prevention list --location=global diff --git a/gcloud/alpha/network-security/security-profiles/threat-prevention/list-overrides b/gcloud/alpha/network-security/security-profiles/threat-prevention/list-overrides index ea7a64256..8e0b056de 100644 --- a/gcloud/alpha/network-security/security-profiles/threat-prevention/list-overrides +++ b/gcloud/alpha/network-security/security-profiles/threat-prevention/list-overrides @@ -23,7 +23,7 @@ EXAMPLES my-security-profile is the name of the Security Profile in the format organizations/{organizationID}/locations/{location}/securityProfiles/ {security_profile_id} where organizationID is the organization ID to which - the changes should apply, location either global or region specified and + the changes should apply, location - global specified and security_profile_id the Security Profile Identifier POSITIONAL ARGUMENTS @@ -43,7 +43,7 @@ POSITIONAL ARGUMENTS arguments in this group are specified. --location=LOCATION - location of the security_profile Global|Region. + location of the security_profile - Global. To set the location attribute: ▸ provide the argument security_profile on the command line with a diff --git a/gcloud/alpha/network-security/security-profiles/threat-prevention/update-override b/gcloud/alpha/network-security/security-profiles/threat-prevention/update-override index 7245e5bf0..89d7e80e5 100644 --- a/gcloud/alpha/network-security/security-profiles/threat-prevention/update-override +++ b/gcloud/alpha/network-security/security-profiles/threat-prevention/update-override @@ -28,7 +28,7 @@ EXAMPLES my-security-profile is the name of the Security Profile in the format organizations/{organizationID}/locations/{location}/securityProfiles/ {security_profile_id} where organizationID is the organization ID to which - the changes should apply, location either global or region specified and + the changes should apply, location - global specified and security_profile_id the Security Profile Identifier POSITIONAL ARGUMENTS @@ -48,7 +48,7 @@ POSITIONAL ARGUMENTS arguments in this group are specified. --location=LOCATION - location of the security_profile Global|Region. + location of the security_profile - Global. To set the location attribute: ▸ provide the argument security_profile on the command line with a diff --git a/gcloud/alpha/projects/get-ancestors-iam-policy b/gcloud/alpha/projects/get-ancestors-iam-policy index b6ff6176c..a27557531 100644 --- a/gcloud/alpha/projects/get-ancestors-iam-policy +++ b/gcloud/alpha/projects/get-ancestors-iam-policy @@ -18,14 +18,13 @@ EXAMPLES $ gcloud alpha projects get-ancestors-iam-policy example-project-id-1 POSITIONAL ARGUMENTS - Project id resource - ID for the project you want to get IAM policy for. - This represents a Cloud resource. + Project resource - ID for the project you want to get IAM policy for. This + represents a Cloud resource. This must be specified. PROJECT_ID - ID of the project_id or fully qualified identifier for the - project_id. + ID of the project or fully qualified identifier for the project. To set the project_id attribute: ▸ provide the argument project_id on the command line. diff --git a/gcloud/alpha/projects/remove-iam-policy-binding b/gcloud/alpha/projects/remove-iam-policy-binding index b9444d74b..5f60e79f9 100644 --- a/gcloud/alpha/projects/remove-iam-policy-binding +++ b/gcloud/alpha/projects/remove-iam-policy-binding @@ -9,7 +9,7 @@ SYNOPSIS | --condition-from-file=CONDITION_FROM_FILE] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) Removes a policy binding to the IAM policy of a project, given a + (ALPHA) Removes a policy binding from the IAM policy of a project, given a project ID and the binding. One binding consists of a member, a role and an optional condition. @@ -55,8 +55,8 @@ EXAMPLES policy role and member types. POSITIONAL ARGUMENTS - Project resource - The project to remove the IAM policy binding from. This - represents a Cloud resource. + Project resource - ID for the project you want to remove IAM policy + binding from. This represents a Cloud resource. This must be specified. diff --git a/gcloud/alpha/scc/assets/describe b/gcloud/alpha/scc/assets/describe index 634e4e08f..52fde5ac8 100644 --- a/gcloud/alpha/scc/assets/describe +++ b/gcloud/alpha/scc/assets/describe @@ -7,7 +7,14 @@ SYNOPSIS (--asset=ASSET | --resource-name=RESOURCE_NAME) [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) Describe an asset given its resource name or asset id. + (ALPHA) (DEPRECATED) Security Command Center Asset APIs are deprecated and + will be removed on or after June 26, 2024. Use Cloud Asset Inventory + instead (gcloud asset) + (https://cloud.google.com/sdk/gcloud/reference/asset). For more + information, see the deprecation notice at Assets Page + (https://cloud.google.com/security-command-center/docs/how-to-use-security-command-center#assets_page). + + Describe an asset given its resource name or asset id. EXAMPLES Describe an asset under organization 123456, given its full resource name diff --git a/gcloud/alpha/scc/assets/get-parent b/gcloud/alpha/scc/assets/get-parent index 045dd9302..fc4f682fc 100644 --- a/gcloud/alpha/scc/assets/get-parent +++ b/gcloud/alpha/scc/assets/get-parent @@ -7,7 +7,14 @@ SYNOPSIS (--asset=ASSET | --resource-name=RESOURCE_NAME) [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) Get the Parent for an asset given its resource name or asset id. + (ALPHA) (DEPRECATED) Security Command Center Asset APIs are deprecated and + will be removed on or after June 26, 2024. Use Cloud Asset Inventory + instead (gcloud asset) + (https://cloud.google.com/sdk/gcloud/reference/asset). For more + information, see the deprecation notice at Assets Page + (https://cloud.google.com/security-command-center/docs/how-to-use-security-command-center#assets_page). + + Get the Parent for an asset given its resource name or asset id. EXAMPLES Get parent's relative resource name given an asset's full resource name diff --git a/gcloud/alpha/scc/assets/get-project b/gcloud/alpha/scc/assets/get-project index fe61c744f..2796d0493 100644 --- a/gcloud/alpha/scc/assets/get-project +++ b/gcloud/alpha/scc/assets/get-project @@ -7,7 +7,14 @@ SYNOPSIS (--asset=ASSET | --resource-name=RESOURCE_NAME) [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) Get the Project for an asset given its resource name or asset id. + (ALPHA) (DEPRECATED) Security Command Center Asset APIs are deprecated and + will be removed on or after June 26, 2024. Use Cloud Asset Inventory + instead (gcloud asset) + (https://cloud.google.com/sdk/gcloud/reference/asset). For more + information, see the deprecation notice at Assets Page + (https://cloud.google.com/security-command-center/docs/how-to-use-security-command-center#assets_page). + + Get the Project for an asset given its resource name or asset id. EXAMPLES Get project id diff --git a/gcloud/alpha/scc/assets/group b/gcloud/alpha/scc/assets/group index 0e91777a7..b26d99db3 100644 --- a/gcloud/alpha/scc/assets/group +++ b/gcloud/alpha/scc/assets/group @@ -9,7 +9,14 @@ SYNOPSIS [--read-time=READ_TIME] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) Filter an organization's assets and groups them by their specified + (ALPHA) (DEPRECATED) Security Command Center Asset APIs are deprecated and + will be removed on or after June 26, 2024. Use Cloud Asset Inventory + instead (gcloud asset) + (https://cloud.google.com/sdk/gcloud/reference/asset). For more + information, see the deprecation notice at Assets Page + (https://cloud.google.com/security-command-center/docs/how-to-use-security-command-center#assets_page). + + Filter an organization's assets and groups them by their specified properties. EXAMPLES diff --git a/gcloud/alpha/scc/assets/help b/gcloud/alpha/scc/assets/help index 66847f352..1df4f430f 100644 --- a/gcloud/alpha/scc/assets/help +++ b/gcloud/alpha/scc/assets/help @@ -16,28 +16,30 @@ COMMANDS COMMAND is one of the following: describe - (ALPHA) Describe an asset given its resource name or asset id. + (ALPHA) (DEPRECATED) Describe an asset given its resource name or asset + id. get-parent - (ALPHA) Get the Parent for an asset given its resource name or asset - id. + (ALPHA) (DEPRECATED) Get the Parent for an asset given its resource + name or asset id. get-project - (ALPHA) Get the Project for an asset given its resource name or asset - id. + (ALPHA) (DEPRECATED) Get the Project for an asset given its resource + name or asset id. group - (ALPHA) Filter an organization's assets and groups them by their - specified properties. + (ALPHA) (DEPRECATED) Filter an organization's assets and groups them by + their specified properties. list - (ALPHA) List Cloud Security Command Center assets. + (ALPHA) (DEPRECATED) List Cloud Security Command Center assets. list-marks - (ALPHA) List an assets's security marks. + (ALPHA) (DEPRECATED) List an assets's security marks. run-discovery - (ALPHA) Scan an organization for new/modified/deleted assets. + (ALPHA) (DEPRECATED) Scan an organization for new/modified/deleted + assets. update-marks (ALPHA) Update Cloud Security Command Center asset's security marks. diff --git a/gcloud/alpha/scc/assets/list b/gcloud/alpha/scc/assets/list index 457fe7597..e317ed1e7 100644 --- a/gcloud/alpha/scc/assets/list +++ b/gcloud/alpha/scc/assets/list @@ -9,7 +9,14 @@ SYNOPSIS [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) List Cloud Security Command Center assets. + (ALPHA) (DEPRECATED) Security Command Center Asset APIs are deprecated and + will be removed on or after June 26, 2024. Use Cloud Asset Inventory + instead (gcloud asset) + (https://cloud.google.com/sdk/gcloud/reference/asset). For more + information, see the deprecation notice at Assets Page + (https://cloud.google.com/security-command-center/docs/how-to-use-security-command-center#assets_page). + + List Cloud Security Command Center assets. EXAMPLES List all assets under organization (123456) diff --git a/gcloud/alpha/scc/assets/list-marks b/gcloud/alpha/scc/assets/list-marks index f19717dba..a816d0712 100644 --- a/gcloud/alpha/scc/assets/list-marks +++ b/gcloud/alpha/scc/assets/list-marks @@ -8,7 +8,14 @@ SYNOPSIS [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) List an assets's security marks. + (ALPHA) (DEPRECATED) Security Command Center Asset APIs are deprecated and + will be removed on or after June 26, 2024. Use Cloud Asset Inventory + instead (gcloud asset) + (https://cloud.google.com/sdk/gcloud/reference/asset). For more + information, see the deprecation notice at Assets Page + (https://cloud.google.com/security-command-center/docs/how-to-use-security-command-center#assets_page). + + List an assets's security marks. EXAMPLES List all security marks for asset (8910) under organization (123456): diff --git a/gcloud/alpha/scc/assets/run-discovery b/gcloud/alpha/scc/assets/run-discovery index 273804a75..466542200 100644 --- a/gcloud/alpha/scc/assets/run-discovery +++ b/gcloud/alpha/scc/assets/run-discovery @@ -6,10 +6,16 @@ SYNOPSIS gcloud alpha scc assets run-discovery [ORGANIZATION] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) Scan an organization for new/modified/deleted assets. Note that - this API can only be called with limited frequency for an organization. If - it is called too frequently the caller will receive a TOO_MANY_REQUESTS - error. + (ALPHA) (DEPRECATED) Security Command Center Asset APIs are deprecated and + will be removed on or after June 26, 2024. Use Cloud Asset Inventory + instead (gcloud asset) + (https://cloud.google.com/sdk/gcloud/reference/asset). For more + information, see the deprecation notice at Assets Page + (https://cloud.google.com/security-command-center/docs/how-to-use-security-command-center#assets_page). + + Scan an organization for new/modified/deleted assets. Note that this API + can only be called with limited frequency for an organization. If it is + called too frequently the caller will receive a TOO_MANY_REQUESTS error. EXAMPLES Run new scan for organization (123456): diff --git a/gcloud/alpha/spanner/databases/execute-sql b/gcloud/alpha/spanner/databases/execute-sql index 37d6fc6d9..6f0e8674f 100644 --- a/gcloud/alpha/spanner/databases/execute-sql +++ b/gcloud/alpha/spanner/databases/execute-sql @@ -5,7 +5,7 @@ NAME SYNOPSIS gcloud alpha spanner databases execute-sql (DATABASE : --instance=INSTANCE) --sql=SQL [--database-role=DATABASE_ROLE] [--enable-partitioned-dml] - [--query-mode=QUERY_MODE; default="NORMAL"] + [--priority=PRIORITY] [--query-mode=QUERY_MODE; default="NORMAL"] [--timeout=TIMEOUT; default="10m"] [--read-timestamp=TIMESTAMP | --strong] [GCLOUD_WIDE_FLAG ...] @@ -64,6 +64,10 @@ OPTIONAL FLAGS --enable-partitioned-dml Execute DML statement using Partitioned DML + --priority=PRIORITY + The priority for the execute SQL request. PRIORITY must be one of: + high, low, medium, unspecified. + --query-mode=QUERY_MODE; default="NORMAL" Mode in which the query must be processed. QUERY_MODE must be one of: diff --git a/gcloud/alpha/sql/instances/create b/gcloud/alpha/sql/instances/create index 46a18614a..54af2de2b 100644 --- a/gcloud/alpha/sql/instances/create +++ b/gcloud/alpha/sql/instances/create @@ -41,6 +41,7 @@ SYNOPSIS [--password-policy-min-length=PASSWORD_POLICY_MIN_LENGTH] [--password-policy-password-change-interval=PASSWORD_POLICY_PASSWORD_CHANGE_INTERVAL] [--password-policy-reuse-interval=PASSWORD_POLICY_REUSE_INTERVAL] + [--[no-]recreate-replicas-on-primary-crash] [--replica-type=REPLICA_TYPE] [--replication=REPLICATION] [--require-ssl] [--retained-backups-count=RETAINED_BACKUPS_COUNT] [--retained-transaction-log-days=RETAINED_TRANSACTION_LOG_DAYS] @@ -360,6 +361,14 @@ FLAGS Number of previous passwords that cannot be reused. The valid range is 0 to 100. + --[no-]recreate-replicas-on-primary-crash + Allow/Disallow replica recreation when a primary MySQL instance + operating in reduced durability mode crashes. Not recreating the + replicas might lead to data inconsistencies between the primary and its + replicas. This setting is only applicable for MySQL instances and is + enabled by default. Use --recreate-replicas-on-primary-crash to enable + and --no-recreate-replicas-on-primary-crash to disable. + --replica-type=REPLICA_TYPE The type of replica to create. REPLICA_TYPE must be one of: READ, FAILOVER. diff --git a/gcloud/alpha/sql/instances/patch b/gcloud/alpha/sql/instances/patch index 6fc4f9445..780ad1596 100644 --- a/gcloud/alpha/sql/instances/patch +++ b/gcloud/alpha/sql/instances/patch @@ -37,6 +37,7 @@ SYNOPSIS [--password-policy-password-change-interval=PASSWORD_POLICY_PASSWORD_CHANGE_INTERVAL] [--password-policy-reuse-interval=PASSWORD_POLICY_REUSE_INTERVAL] [--pricing-plan=PRICING_PLAN, -p PRICING_PLAN] + [--[no-]recreate-replicas-on-primary-crash] [--remove-deny-maintenance-period] [--replication=REPLICATION] [--[no-]require-ssl] [--[no-]storage-auto-increase] [--storage-auto-increase-limit=STORAGE_AUTO_INCREASE_LIMIT] @@ -310,6 +311,14 @@ FLAGS First Generation instances only. The pricing plan for this instance. PRICING_PLAN must be one of: PER_USE, PACKAGE. + --[no-]recreate-replicas-on-primary-crash + Allow/Disallow replica recreation when a primary MySQL instance + operating in reduced durability mode crashes. Not recreating the + replicas might lead to data inconsistencies between the primary and its + replicas. This setting is only applicable for MySQL instances and is + enabled by default. Use --recreate-replicas-on-primary-crash to enable + and --no-recreate-replicas-on-primary-crash to disable. + --remove-deny-maintenance-period Removes the user-specified deny maintenance period. diff --git a/gcloud/alpha/storage/buckets/describe b/gcloud/alpha/storage/buckets/describe index dd3247697..73dcdb392 100644 --- a/gcloud/alpha/storage/buckets/describe +++ b/gcloud/alpha/storage/buckets/describe @@ -3,7 +3,7 @@ NAME SYNOPSIS gcloud alpha storage buckets describe URL - [--additional-headers=HEADER=VALUE] [GCLOUD_WIDE_FLAG ...] + [--additional-headers=HEADER=VALUE] [--raw] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Describe a Cloud Storage bucket. @@ -29,6 +29,10 @@ FLAGS Overrides the default storage/additional_headers property value for this command invocation. + --raw + Shows metadata in the format returned by the API instead of + standardizing it. + GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, diff --git a/gcloud/alpha/storage/buckets/list b/gcloud/alpha/storage/buckets/list index 0d43d8580..555fd5f11 100644 --- a/gcloud/alpha/storage/buckets/list +++ b/gcloud/alpha/storage/buckets/list @@ -3,7 +3,7 @@ NAME SYNOPSIS gcloud alpha storage buckets list [URLS ...] - [--additional-headers=HEADER=VALUE] [--filter=EXPRESSION] + [--additional-headers=HEADER=VALUE] [--raw] [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] @@ -34,6 +34,10 @@ FLAGS Overrides the default storage/additional_headers property value for this command invocation. + --raw + Shows metadata in the format returned by the API instead of + standardizing it. + LIST COMMAND FLAGS --filter=EXPRESSION Apply a Boolean filter EXPRESSION to each resource item to be listed. diff --git a/gcloud/alpha/storage/buckets/update b/gcloud/alpha/storage/buckets/update index 4d114c4af..70631a68a 100644 --- a/gcloud/alpha/storage/buckets/update +++ b/gcloud/alpha/storage/buckets/update @@ -220,7 +220,8 @@ FLAGS At most one of these can be specified: --clear-log-bucket - Clears logging bucket receiving the usage current bucket's data. + Clears logging bucket receiving the usage current bucket's data and + disables usage logging. --log-bucket=LOG_BUCKET Enables usage logging of the bucket, outputting log files to the @@ -239,6 +240,7 @@ FLAGS Specifies the object prefix for logging activity to the log bucket. The default prefix is the bucket name. All read and write activity to objects in the bucket will be logged for objects matching the prefix. + If usage logging is not enabled this flag will have no effect. At most one of these can be specified: diff --git a/gcloud/alpha/storage/du b/gcloud/alpha/storage/du index e2850f8ef..b722b2933 100644 --- a/gcloud/alpha/storage/du +++ b/gcloud/alpha/storage/du @@ -97,5 +97,7 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. + access allowlist. This variant is also available: + + $ gcloud storage du diff --git a/gcloud/alpha/storage/help b/gcloud/alpha/storage/help index 3db5f9d5e..93faa9346 100644 --- a/gcloud/alpha/storage/help +++ b/gcloud/alpha/storage/help @@ -23,6 +23,9 @@ GROUPS buckets (ALPHA) Manage Cloud Storage buckets. + hmac + (ALPHA) Manage Cloud Storage service account HMAC keys. + insights (ALPHA) Manage Cloud Storage inventory reports. diff --git a/gcloud/alpha/storage/hmac/create b/gcloud/alpha/storage/hmac/create new file mode 100644 index 000000000..ce24e3328 --- /dev/null +++ b/gcloud/alpha/storage/hmac/create @@ -0,0 +1,39 @@ +NAME + gcloud alpha storage hmac create - add a service account HMAC + +SYNOPSIS + gcloud alpha storage hmac create SERVICE_ACCOUNT [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) gcloud alpha storage hmac create command creates an HMAC key for + the specified service account. The secret key material is only available + upon creation, so be sure to store the returned secret along with the + access_id. + +EXAMPLES + To create an HMAC key for + test.service.account@test_project.iam.gserviceaccount.com: + + $ gcloud alpha storage hmac create \ + test.service.account@test_project.iam.gserviceaccount.com + +POSITIONAL ARGUMENTS + SERVICE_ACCOUNT + The service account email. + +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 storage hmac create + diff --git a/gcloud/alpha/storage/hmac/delete b/gcloud/alpha/storage/hmac/delete new file mode 100644 index 000000000..e3a7eae05 --- /dev/null +++ b/gcloud/alpha/storage/hmac/delete @@ -0,0 +1,40 @@ +NAME + gcloud alpha storage hmac delete - remove a service account HMAC + +SYNOPSIS + gcloud alpha storage hmac delete ACCESS_ID [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) gcloud alpha storage hmac delete permanently deletes the specified + HMAC key. Note that keys must be updated to be in the INACTIVE state before + they can be deleted. + +EXAMPLES + To delete a specific HMAC key: + + $ gcloud alpha storage hmac delete GOOG56JBMFZX6PMPTQ62VD2 + + To be prompted for HMAC keys to delete: + + $ gcloud alpha storage hmac delete + +POSITIONAL ARGUMENTS + ACCESS_ID + Access ID for HMAC key to delete. + +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 storage hmac delete + diff --git a/gcloud/alpha/storage/hmac/describe b/gcloud/alpha/storage/hmac/describe new file mode 100644 index 000000000..616199dba --- /dev/null +++ b/gcloud/alpha/storage/hmac/describe @@ -0,0 +1,40 @@ +NAME + gcloud alpha storage hmac describe - describes a service account HMAC key + +SYNOPSIS + gcloud alpha storage hmac describe ACCESS_ID [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) gcloud alpha storage hmac describe retrieves the specified HMAC + key's metadata. Note that there is no option to retrieve a key's secret + material after it has been created. + +EXAMPLES + The following command retrieves the HMAC key's metadata: + + $ gcloud alpha storage hmac describe GOOG56JBMFZX6PMPTQ62VD2 + + Note GOOG56JBMFZX6PMPTQ62VD2 is the ACCESS_ID of the HMAC key. + +POSITIONAL ARGUMENTS + ACCESS_ID + The Access ID + (https://cloud.google.com/storage/docs/authentication/hmackeys#overview) + of the HMAC key + +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 storage hmac describe + diff --git a/gcloud/alpha/storage/hmac/help b/gcloud/alpha/storage/hmac/help new file mode 100644 index 000000000..3aa84a70b --- /dev/null +++ b/gcloud/alpha/storage/hmac/help @@ -0,0 +1,40 @@ +NAME + gcloud alpha storage hmac - manage Cloud Storage service account HMAC keys + +SYNOPSIS + gcloud alpha storage hmac COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Manage Cloud Storage service account HMAC keys. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + create + (ALPHA) Add a service account HMAC. + + delete + (ALPHA) Remove a service account HMAC. + + describe + (ALPHA) Describes a service account HMAC key. + + list + (ALPHA) List service account HMAC keys. + + update + (ALPHA) Change the status of a service account HMAC. + +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 storage hmac + diff --git a/gcloud/alpha/compute/os-config/patch-jobs/list b/gcloud/alpha/storage/hmac/list similarity index 60% rename from gcloud/alpha/compute/os-config/patch-jobs/list rename to gcloud/alpha/storage/hmac/list index 7021f793a..99a714f1a 100644 --- a/gcloud/alpha/compute/os-config/patch-jobs/list +++ b/gcloud/alpha/storage/hmac/list @@ -1,16 +1,37 @@ NAME - gcloud alpha compute os-config patch-jobs list - list ongoing and completed - patch jobs + gcloud alpha storage hmac list - list service account HMAC keys SYNOPSIS - gcloud alpha compute os-config patch-jobs list [--filter=EXPRESSION] - [--limit=LIMIT; default=10] [--page-size=PAGE_SIZE] + gcloud alpha storage hmac list [--all, -a] [--long, -l] + [--service-account=SERVICE_ACCOUNT, -u SERVICE_ACCOUNT] + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] -EXAMPLES - To list patch jobs in the current project, run: +DESCRIPTION + (ALPHA) gcloud alpha storage hmac list lists the HMAC key metadata for keys + in the current project. - $ gcloud alpha compute os-config patch-jobs list +EXAMPLES + To show metadata for all keys, including recently deleted keys: + + $ gcloud alpha storage hmac list --all --long + + To list only HMAC keys belonging to the service account + test.sa@test.iam.gserviceaccount.com: + + $ gcloud alpha storage hmac list \ + --service-account=test.sa@test.iam.gserviceaccount.com + +FLAGS + --all, -a + Shows all keys, including recently deleted keys. + + --long, -l + Use long listing format, showing the full metadata for each key + excluding the secret. + + --service-account=SERVICE_ACCOUNT, -u SERVICE_ACCOUNT + Filter keys for the provided service account email. LIST COMMAND FLAGS --filter=EXPRESSION @@ -20,10 +41,10 @@ LIST COMMAND FLAGS This flag interacts with other flags that are applied in this order: --flatten, --sort-by, --filter, --limit. - --limit=LIMIT; default=10 - Maximum number of resources to list. The default is 10. 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 @@ -56,9 +77,7 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. These variants are also available: + access allowlist. This variant is also available: - $ gcloud compute os-config patch-jobs list - - $ gcloud beta compute os-config patch-jobs list + $ gcloud storage hmac list diff --git a/gcloud/alpha/storage/hmac/update b/gcloud/alpha/storage/hmac/update new file mode 100644 index 000000000..1f90fac75 --- /dev/null +++ b/gcloud/alpha/storage/hmac/update @@ -0,0 +1,59 @@ +NAME + gcloud alpha storage hmac update - change the status of a service account + HMAC + +SYNOPSIS + gcloud alpha storage hmac update ACCESS_ID (--activate | --deactivate) + [--etag=ETAG, -e ETAG] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) gcloud alpha storage hmac update sets the state of the specified + key. Valid state arguments are ACTIVE and INACTIVE. To set a key to state + DELETED, use gcloud alpha storage hmac delete on an INACTIVE key. If an + etag is set in the command, it will only succeed if the provided etag + matches the etag of the stored key. + +EXAMPLES + To activate an HMAC key: + + $ gcloud alpha storage hmac update GOOG56JBMFZX6PMPTQ62VD2 --activate + + To set the state of an HMAC key to INACTIVE provided its etag is M42da=: + + $ gcloud alpha storage hmac update GOOG56JBMFZX6PMPTQ62VD2 \ + --deactivate --etag=M42da= + +POSITIONAL ARGUMENTS + ACCESS_ID + Access ID for HMAC key to update. + +REQUIRED FLAGS + Exactly one of these must be specified: + + --activate + Sets the state of the specified key to ACTIVE. + + --deactivate + Sets the state of the specified key to INACTIVE. + +OPTIONAL FLAGS + --etag=ETAG, -e ETAG + If provided, the update will only be performed if the specified etag + matches the etag of the stored key. + +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 storage hmac update + diff --git a/gcloud/alpha/storage/objects/describe b/gcloud/alpha/storage/objects/describe index 9a4441277..d55497d58 100644 --- a/gcloud/alpha/storage/objects/describe +++ b/gcloud/alpha/storage/objects/describe @@ -4,7 +4,7 @@ NAME SYNOPSIS gcloud alpha storage objects describe URL [--additional-headers=HEADER=VALUE] [--fetch-encrypted-object-hashes] - [--decryption-keys=[DECRYPTION_KEY,...]] [GCLOUD_WIDE_FLAG ...] + [--raw] [--decryption-keys=[DECRYPTION_KEY,...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Describe a Cloud Storage object. @@ -37,6 +37,10 @@ FLAGS matching decryption key is present on the system, this flag retries the GET request with the key. + --raw + Shows metadata in the format returned by the API instead of + standardizing it. + ENCRYPTION FLAGS --decryption-keys=[DECRYPTION_KEY,...] A comma-separated list of customer-supplied encryption keys (RFC 4648 diff --git a/gcloud/alpha/storage/objects/list b/gcloud/alpha/storage/objects/list index 66c4de692..6bd85f861 100644 --- a/gcloud/alpha/storage/objects/list +++ b/gcloud/alpha/storage/objects/list @@ -4,9 +4,9 @@ NAME SYNOPSIS gcloud alpha storage objects list URLS [URLS ...] [--additional-headers=HEADER=VALUE] [--fetch-encrypted-object-hashes] - [--stat] [--decryption-keys=[DECRYPTION_KEY,...]] [--filter=EXPRESSION] - [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] - [GCLOUD_WIDE_FLAG ...] + [--raw] [--stat] [--decryption-keys=[DECRYPTION_KEY,...]] + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) List Cloud Storage objects. @@ -46,6 +46,10 @@ FLAGS encrypted object in order to fetch hashes. This can significantly increase the cost of the command. + --raw + Shows metadata in the format returned by the API instead of + standardizing it. + --stat Emulates gsutil stat-style behavior. Does not show past object versions and changes output format. diff --git a/gcloud/alpha/storage/sign-url b/gcloud/alpha/storage/sign-url index e355d718e..7efa8af7c 100644 --- a/gcloud/alpha/storage/sign-url +++ b/gcloud/alpha/storage/sign-url @@ -111,5 +111,7 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. + access allowlist. This variant is also available: + + $ gcloud storage sign-url diff --git a/gcloud/assured/workloads/create b/gcloud/assured/workloads/create index 6d0a26897..784d4323b 100644 --- a/gcloud/assured/workloads/create +++ b/gcloud/assured/workloads/create @@ -9,6 +9,7 @@ SYNOPSIS [--enable-sovereign-controls=ENABLE_SOVEREIGN_CONTROLS] [--external-identifier=EXTERNAL_IDENTIFIER] [--labels=[KEY=VALUE,...]] [--next-rotation-time=NEXT_ROTATION_TIME] [--partner=PARTNER] + [--partner-permissions=[KEY=VALUE,...]] [--provisioned-resources-parent=PROVISIONED_RESOURCES_PARENT] [--resource-settings=[KEY=VALUE,...]] [--rotation-period=ROTATION_PERIOD] [GCLOUD_WIDE_FLAG ...] @@ -86,6 +87,10 @@ OPTIONAL FLAGS partners. PARTNER must be one of: LOCAL_CONTROLS_BY_S3NS, SOVEREIGN_CONTROLS_BY_T_SYSTEMS. + --partner-permissions=[KEY=VALUE,...] + The partner permissions for the partner regime, for example, + data-logs-viewer=true/false + --provisioned-resources-parent=PROVISIONED_RESOURCES_PARENT The parent of the provisioned projects, for example, folders/{FOLDER_ID} diff --git a/gcloud/beta/ai-platform/models/remove-iam-policy-binding b/gcloud/beta/ai-platform/models/remove-iam-policy-binding index 31b154844..c4ceed768 100644 --- a/gcloud/beta/ai-platform/models/remove-iam-policy-binding +++ b/gcloud/beta/ai-platform/models/remove-iam-policy-binding @@ -28,7 +28,7 @@ EXAMPLES --role='roles/ml.admin' See https://cloud.google.com/iam/docs/managing-policies for details of - policy role and principal types. + policy role and member types. POSITIONAL ARGUMENTS Model resource - The AI Platform model for which to remove IAM policy diff --git a/gcloud/beta/assured/workloads/create b/gcloud/beta/assured/workloads/create index ea60d09c4..c482f362e 100644 --- a/gcloud/beta/assured/workloads/create +++ b/gcloud/beta/assured/workloads/create @@ -9,6 +9,7 @@ SYNOPSIS [--enable-sovereign-controls=ENABLE_SOVEREIGN_CONTROLS] [--external-identifier=EXTERNAL_IDENTIFIER] [--labels=[KEY=VALUE,...]] [--next-rotation-time=NEXT_ROTATION_TIME] [--partner=PARTNER] + [--partner-permissions=[KEY=VALUE,...]] [--provisioned-resources-parent=PROVISIONED_RESOURCES_PARENT] [--resource-settings=[KEY=VALUE,...]] [--rotation-period=ROTATION_PERIOD] [GCLOUD_WIDE_FLAG ...] @@ -86,6 +87,10 @@ OPTIONAL FLAGS partners. PARTNER must be one of: LOCAL_CONTROLS_BY_S3NS, SOVEREIGN_CONTROLS_BY_T_SYSTEMS. + --partner-permissions=[KEY=VALUE,...] + The partner permissions for the partner regime, for example, + data-logs-viewer=true/false + --provisioned-resources-parent=PROVISIONED_RESOURCES_PARENT The parent of the provisioned projects, for example, folders/{FOLDER_ID} diff --git a/gcloud/beta/bigtable/instances/tables/create b/gcloud/beta/bigtable/instances/tables/create index 71303eea5..394b9b96d 100644 --- a/gcloud/beta/bigtable/instances/tables/create +++ b/gcloud/beta/bigtable/instances/tables/create @@ -4,8 +4,9 @@ NAME SYNOPSIS gcloud beta bigtable instances tables create (TABLE : --instance=INSTANCE) - --column-families=[COLUMN_FAMILIES,...] [--deletion-protection] - [--splits=[SPLITS,...]] [GCLOUD_WIDE_FLAG ...] + --column-families=[COLUMN_FAMILIES,...] + [--change-stream-retention-period=CHANGE_STREAM_RETENTION_PERIOD] + [--deletion-protection] [--splits=[SPLITS,...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) Create a new Cloud Bigtable table. @@ -35,6 +36,15 @@ EXAMPLES --column-families="my-family-1:maxage=10d,my-family-2:maxversion\ s=5||maxage=5d" + To create a table my-table that has one column family my-family that lets + data expire after 10 days, and to enable a change stream for the table to + be kept for 7 days, run: + + $ gcloud beta bigtable instances tables create my-table \ + --instance=my-instance \ + --column-families="my-family:maxage=10d" \ + --change-stream-retention-period=7d + To create a deletion-protected table my-table in instance my-instance with a column family my-family, run: @@ -88,6 +98,12 @@ REQUIRED FLAGS "family_1,family_2:maxage=5d&&maxversions=2,family_3:maxage=10d||maxversions=5" OPTIONAL FLAGS + --change-stream-retention-period=CHANGE_STREAM_RETENTION_PERIOD + The length of time to retain change stream data for the table, in the + range of [1 day, 7 days]. Acceptable units are days (d), hours (h), + minutes (m), and seconds (s). Passing in a value for this option + enables a change stream for the table. Examples: 5d or 48h. + --deletion-protection Once specified, the table is deletion protected. diff --git a/gcloud/beta/bigtable/instances/tables/update b/gcloud/beta/bigtable/instances/tables/update index 250f5bf43..b214b0f37 100644 --- a/gcloud/beta/bigtable/instances/tables/update +++ b/gcloud/beta/bigtable/instances/tables/update @@ -4,7 +4,9 @@ NAME SYNOPSIS gcloud beta bigtable instances tables update (TABLE : --instance=INSTANCE) - [--async] [--deletion-protection] [GCLOUD_WIDE_FLAG ...] + [--async] [--deletion-protection] + [--change-stream-retention-period=CHANGE_STREAM_RETENTION_PERIOD + | --clear-change-stream-retention-period] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) Update an existing new Cloud Bigtable table with the specified @@ -21,6 +23,17 @@ EXAMPLES $ gcloud beta bigtable instances tables update my-table \ --instance=my-instance --no-deletion-protection + To enable a change stream with a retention period of 1 day, or to update + your table's change stream retention period to 1 day, run: + + $ gcloud beta bigtable instances tables update my-table \ + --instance=my-instance --change-stream-retention-period=1d + + To disable a change stream, run: + + $ gcloud beta bigtable instances tables update my-table \ + --instance=my-instance --clear-change-stream-retention-period + POSITIONAL ARGUMENTS Table resource - Cloud Bigtable table to update. The arguments in this group can be used to specify the attributes of this resource. (NOTE) Some @@ -60,6 +73,18 @@ FLAGS --deletion-protection Once specified, the table is deletion protected. + At most one of these can be specified: + + --change-stream-retention-period=CHANGE_STREAM_RETENTION_PERIOD + The length of time to retain change stream data for the table, in the + range of [1 day, 7 days]. Acceptable units are days (d), hours (h), + minutes (m), and seconds (s). If not already specified, enables a + change stream for the table. Examples: 5d or 48h. + + --clear-change-stream-retention-period + This disables the change stream and eventually removes the change + stream data. + GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, diff --git a/gcloud/beta/builds/triggers/help b/gcloud/beta/builds/triggers/help index 3d32ef067..c69f3272e 100644 --- a/gcloud/beta/builds/triggers/help +++ b/gcloud/beta/builds/triggers/help @@ -19,6 +19,9 @@ GROUPS create (BETA) Create build triggers for Google Cloud Build. + update + (BETA) Update Triggers in Google Cloud Build. + COMMANDS COMMAND is one of the following: diff --git a/gcloud/beta/builds/triggers/update/bitbucketserver b/gcloud/beta/builds/triggers/update/bitbucketserver new file mode 100644 index 000000000..5386de9f0 --- /dev/null +++ b/gcloud/beta/builds/triggers/update/bitbucketserver @@ -0,0 +1,253 @@ +NAME + gcloud beta builds triggers update bitbucketserver - updates Bitbucket + Server trigger used by Google Cloud Build + +SYNOPSIS + gcloud beta builds triggers update bitbucketserver + (TRIGGER : --region=REGION) + (--trigger-config=PATH + | --bitbucket-server-config-resource=BITBUCKET_SERVER_CONFIG_RESOURCE + --description=DESCRIPTION --ignored-files=[GLOB,...] + --included-files=[GLOB,...] --project-key=PROJECT_KEY + --repo-slug=REPO_SLUG --[no-]require-approval + --service-account=SERVICE_ACCOUNT --branch-pattern=REGEX + | --tag-pattern=REGEX | --comment-control=COMMENT_CONTROL; + default="COMMENTS_ENABLED" + --pull-request-pattern=REGEX --build-config=PATH + | --inline-config=PATH + | [--dockerfile=DOCKERFILE --dockerfile-image=DOCKERFILE_IMAGE + : --dockerfile-dir=DOCKERFILE_DIR] --clear-substitutions + | --remove-substitutions=[KEY,...] + | --update-substitutions=[KEY=VALUE,...]) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Updates Bitbucket Server trigger used by Google Cloud Build. + +EXAMPLES + To update the branch pattern of the trigger: + + $ gcloud beta builds triggers update bitbucketserver my-trigger \ + --branch-pattern=".*" + + To update the build config of the trigger: + + $ gcloud beta builds triggers update bitbucketserver my-trigger \ + --build-config="cloudbuild.yaml" + + To update the substitutions of the trigger: $ gcloud beta builds triggers update bitbucketserver my-trigger \ + --update-substitutions=_REPO_NAME=my-repo,_BRANCH_NAME=master + +POSITIONAL ARGUMENTS + Trigger resource - Build Trigger. 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 TRIGGER 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. + + TRIGGER + ID of the trigger or fully qualified identifier for the trigger. + + To set the trigger attribute: + ▸ provide the argument TRIGGER 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 location for the trigger. + + To set the region attribute: + ▸ provide the argument TRIGGER on the command line with a fully + specified name; + ▸ provide the argument --region on the command line; + ▸ set the property builds/region. + +REQUIRED FLAGS + Exactly one of these must be specified: + + --trigger-config=PATH + Path to Build Trigger config file (JSON or YAML format). For more + details, see + https://cloud.google.com/cloud-build/docs/api/reference/rest/v1/projects.triggers#BuildTrigger + + Flag based trigger configuration + + --bitbucket-server-config-resource=BITBUCKET_SERVER_CONFIG_RESOURCE + Bitbucket Server config resource name. + + --description=DESCRIPTION + Build trigger description. + + --ignored-files=[GLOB,...] + Glob filter. Changes only affecting ignored files won't trigger + builds. + + --included-files=[GLOB,...] + Glob filter. Changes affecting at least one included file will + trigger builds. + + --project-key=PROJECT_KEY + Bitbucket Server project key. + + --repo-slug=REPO_SLUG + Bitbucket Server repository slug. + + --[no-]require-approval + Require manual approval for triggered builds. Use + --require-approval to enable and --no-require-approval to disable. + + --service-account=SERVICE_ACCOUNT + The service account used for all user-controlled operations + including UpdateBuildTrigger, RunBuildTrigger, CreateBuild, and + CancelBuild. If no service account is set, then the standard Cloud + Build service account ([PROJECT_NUM]@system.gserviceaccount.com) is + used instead. Format: + projects/{PROJECT_ID}/serviceAccounts/{ACCOUNT_ID_OR_EMAIL}. + + At most one of these can be specified: + + --branch-pattern=REGEX + A regular expression specifying which git branches to match. + + This pattern is used as a regular expression search for any + incoming pushes. For example, --branch-pattern=foo will match + "foo", "foobar", and "barfoo". Events on a branch that does not + match will be ignored. + + The syntax of the regular expressions accepted is the syntax + accepted by RE2 and described at + https://github.com/google/re2/wiki/Syntax. + + --tag-pattern=REGEX + A regular expression specifying which git tags to match. + + This pattern is used as a regular expression search for any + incoming pushes. For example, --tag-pattern=foo will match "foo", + "foobar", and "barfoo". Events on a tag that does not match will + be ignored. + + The syntax of the regular expressions accepted is the syntax + accepted by RE2 and described at + https://github.com/google/re2/wiki/Syntax. + + Pull Request settings + + --comment-control=COMMENT_CONTROL; default="COMMENTS_ENABLED" + Require a repository collaborator or owner to comment '/gcbrun' + on a pull request before running the build. COMMENT_CONTROL + must be one of: + + COMMENTS_DISABLED + Do not require comments on Pull Requests before builds are + triggered. + COMMENTS_ENABLED + Enforce that repository owners or collaborators must + comment on Pull Requests before builds are triggered. + COMMENTS_ENABLED_FOR_EXTERNAL_CONTRIBUTORS_ONLY + Enforce that repository owners or collaborators must + comment on external contributors' Pull Requests before + builds are triggered. + + --pull-request-pattern=REGEX + A regular expression specifying which base git branch to match + for pull request events. + + This pattern is used as a regular expression search for the + base branch (the branch you are trying to merge into) for pull + request updates. For example, --pull-request-pattern=foo will + match "foo", "foobar", and "barfoo". + + The syntax of the regular expressions accepted is the syntax + accepted by RE2 and described at + https://github.com/google/re2/wiki/Syntax. + + At most one of these can be specified: + + --build-config=PATH + Path to a YAML or JSON file containing the build configuration in + the repository. + + For more details, see: + https://cloud.google.com/cloud-build/docs/build-config + + --inline-config=PATH + Local path to a YAML or JSON file containing a build + configuration. + + Dockerfile build configuration flags + + --dockerfile=DOCKERFILE + Path of Dockerfile to use for builds in the repository. + + If specified, a build config will be generated to run docker + build using the specified file. + + The filename is relative to the Dockerfile directory. + + This flag argument must be specified if any of the other + arguments in this group are specified. + + --dockerfile-image=DOCKERFILE_IMAGE + Docker image name to build. + + This flag argument must be specified if any of the other + arguments in this group are specified. + + --dockerfile-dir=DOCKERFILE_DIR + Location of the directory containing the Dockerfile in the + repository. + + The directory will also be used as the Docker build context. + + At most one of these can be specified: + + --clear-substitutions + Clear existing substitutions. + + --remove-substitutions=[KEY,...] + Remove existing substitutions if present. + + --update-substitutions=[KEY=VALUE,...] + Update or add to existing substitutions. Substitutions are + parameters to be substituted or add in the build specification. + + For example (using some nonsensical substitution keys; all keys + must begin with an underscore): + + $ gcloud builds triggers update ... + --update-substitutions _FAVORITE_COLOR=blue,_NUM_CANDIES=10 + + This will add the provided substitutions to the existing + substitutions and results in a build where every occurrence of + ${_FAVORITE_COLOR} in certain fields is replaced by "blue", and + similarly for ${_NUM_CANDIES} and "10". + + Only the following built-in variables can be specified with the + --substitutions flag: REPO_NAME, BRANCH_NAME, TAG_NAME, + REVISION_ID, COMMIT_SHA, SHORT_SHA. + + For more details, see: + https://cloud.google.com/build/docs/build-config-file-schema#substitutions + +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 builds triggers update bitbucketserver + + $ gcloud alpha builds triggers update bitbucketserver + diff --git a/gcloud/beta/builds/triggers/update/cloud-source-repositories b/gcloud/beta/builds/triggers/update/cloud-source-repositories new file mode 100644 index 000000000..9ac056882 --- /dev/null +++ b/gcloud/beta/builds/triggers/update/cloud-source-repositories @@ -0,0 +1,227 @@ +NAME + gcloud beta builds triggers update cloud-source-repositories - updates + Cloud Source Repositories trigger used by Google Cloud Build + +SYNOPSIS + gcloud beta builds triggers update cloud-source-repositories + (TRIGGER : --region=REGION) + (--trigger-config=PATH | --description=DESCRIPTION + --ignored-files=[GLOB,...] --included-files=[GLOB,...] --repo=REPO + --[no-]require-approval + --service-account=SERVICE_ACCOUNT --branch-pattern=REGEX + | --tag-pattern=REGEX --build-config=PATH | --inline-config=PATH + | [--dockerfile=DOCKERFILE --dockerfile-image=DOCKERFILE_IMAGE + : --dockerfile-dir=DOCKERFILE_DIR] --clear-substitutions + | --remove-substitutions=[KEY,...] + | --update-substitutions=[KEY=VALUE,...]) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Updates Cloud Source Repositories trigger used by Google Cloud + Build. + +EXAMPLES + To update the branch pattern of the trigger: + + $ gcloud beta builds triggers update cloud-source-repositories \ + my-trigger --branch-pattern=".*" + + To update the build config of the trigger: + + $ gcloud beta builds triggers update cloud-source-repositories \ + my-trigger --build-config="cloudbuild.yaml" + + To update the substitutions of the trigger: + + $ gcloud beta builds triggers update cloud-source-repositories \ + my-trigger \ + --update-substitutions=_REPO_NAME=my-repo,_BRANCH_NAME=master + +POSITIONAL ARGUMENTS + Trigger resource - Build Trigger. 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 TRIGGER 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. + + TRIGGER + ID of the trigger or fully qualified identifier for the trigger. + + To set the trigger attribute: + ▸ provide the argument TRIGGER 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 location for the trigger. + + To set the region attribute: + ▸ provide the argument TRIGGER on the command line with a fully + specified name; + ▸ provide the argument --region on the command line; + ▸ set the property builds/region. + +REQUIRED FLAGS + Exactly one of these must be specified: + + --trigger-config=PATH + Path to Build Trigger config file (JSON or YAML format). For more + details, see + https://cloud.google.com/cloud-build/docs/api/reference/rest/v1/projects.triggers#BuildTrigger + + Flag based trigger configuration + + --description=DESCRIPTION + Build trigger description. + + --ignored-files=[GLOB,...] + Glob filter. Changes only affecting ignored files won't trigger + builds. + + --included-files=[GLOB,...] + Glob filter. Changes affecting at least one included file will + trigger builds. + + Repo resource - Cloud Source Repository. 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 --repo on the command line with a fully + specified name; + ▫ set the property core/project. + + --repo=REPO + ID of the repo or fully qualified identifier for the repo. + + To set the repo attribute: + ◇ provide the argument --repo on the command line. + + --[no-]require-approval + Require manual approval for triggered builds. Use + --require-approval to enable and --no-require-approval to disable. + + --service-account=SERVICE_ACCOUNT + The service account used for all user-controlled operations + including UpdateBuildTrigger, RunBuildTrigger, CreateBuild, and + CancelBuild. If no service account is set, then the standard Cloud + Build service account ([PROJECT_NUM]@system.gserviceaccount.com) is + used instead. Format: + projects/{PROJECT_ID}/serviceAccounts/{ACCOUNT_ID_OR_EMAIL}. + + At most one of these can be specified: + + --branch-pattern=REGEX + A regular expression specifying which git branches to match. + + This pattern is used as a regular expression search for any + incoming pushes. For example, --branch-pattern=foo will match + "foo", "foobar", and "barfoo". Events on a branch that does not + match will be ignored. + + The syntax of the regular expressions accepted is the syntax + accepted by RE2 and described at + https://github.com/google/re2/wiki/Syntax. + + --tag-pattern=REGEX + A regular expression specifying which git tags to match. + + This pattern is used as a regular expression search for any + incoming pushes. For example, --tag-pattern=foo will match "foo", + "foobar", and "barfoo". Events on a tag that does not match will + be ignored. + + The syntax of the regular expressions accepted is the syntax + accepted by RE2 and described at + https://github.com/google/re2/wiki/Syntax. + + At most one of these can be specified: + + --build-config=PATH + Path to a YAML or JSON file containing the build configuration in + the repository. + + For more details, see: + https://cloud.google.com/cloud-build/docs/build-config + + --inline-config=PATH + Local path to a YAML or JSON file containing a build + configuration. + + Dockerfile build configuration flags + + --dockerfile=DOCKERFILE + Path of Dockerfile to use for builds in the repository. + + If specified, a build config will be generated to run docker + build using the specified file. + + The filename is relative to the Dockerfile directory. + + This flag argument must be specified if any of the other + arguments in this group are specified. + + --dockerfile-image=DOCKERFILE_IMAGE + Docker image name to build. + + This flag argument must be specified if any of the other + arguments in this group are specified. + + --dockerfile-dir=DOCKERFILE_DIR + Location of the directory containing the Dockerfile in the + repository. + + The directory will also be used as the Docker build context. + + At most one of these can be specified: + + --clear-substitutions + Clear existing substitutions. + + --remove-substitutions=[KEY,...] + Remove existing substitutions if present. + + --update-substitutions=[KEY=VALUE,...] + Update or add to existing substitutions. Substitutions are + parameters to be substituted or add in the build specification. + + For example (using some nonsensical substitution keys; all keys + must begin with an underscore): + + $ gcloud builds triggers update ... + --update-substitutions _FAVORITE_COLOR=blue,_NUM_CANDIES=10 + + This will add the provided substitutions to the existing + substitutions and results in a build where every occurrence of + ${_FAVORITE_COLOR} in certain fields is replaced by "blue", and + similarly for ${_NUM_CANDIES} and "10". + + Only the following built-in variables can be specified with the + --substitutions flag: REPO_NAME, BRANCH_NAME, TAG_NAME, + REVISION_ID, COMMIT_SHA, SHORT_SHA. + + For more details, see: + https://cloud.google.com/build/docs/build-config-file-schema#substitutions + +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 builds triggers update cloud-source-repositories + + $ gcloud alpha builds triggers update cloud-source-repositories + diff --git a/gcloud/beta/builds/triggers/update/github b/gcloud/beta/builds/triggers/update/github new file mode 100644 index 000000000..539b2f3d8 --- /dev/null +++ b/gcloud/beta/builds/triggers/update/github @@ -0,0 +1,268 @@ +NAME + gcloud beta builds triggers update github - update GitHub trigger used by + Google Cloud Build + +SYNOPSIS + gcloud beta builds triggers update github (TRIGGER : --region=REGION) + (--trigger-config=PATH | --description=DESCRIPTION + --ignored-files=[GLOB,...] --include-logs-with-status + --included-files=[GLOB,...] --[no-]require-approval + --service-account=SERVICE_ACCOUNT --branch-pattern=REGEX + | --tag-pattern=REGEX | --comment-control=COMMENT_CONTROL; + default="COMMENTS_ENABLED" + --pull-request-pattern=REGEX --build-config=PATH + | --inline-config=PATH + | [--dockerfile=DOCKERFILE --dockerfile-image=DOCKERFILE_IMAGE + : --dockerfile-dir=DOCKERFILE_DIR] --clear-substitutions + | --remove-substitutions=[KEY,...] + | --update-substitutions=[KEY=VALUE,...] --repository=REPOSITORY + | --enterprise-config=ENTERPRISE_CONFIG + --repo-name=REPO_NAME --repo-owner=REPO_OWNER) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Update GitHub trigger used by Google Cloud Build. + +EXAMPLES + To update the branch pattern of the trigger: + + $ gcloud beta builds triggers update github my-trigger \ + --branch-pattern=".*" + + To update the build config of the trigger: + + $ gcloud beta builds triggers update github my-trigger \ + --build-config="cloudbuild.yaml" + + To update the substitutions of the trigger: + + $ gcloud beta builds triggers update github my-trigger \ + --update-substitutions=_REPO_NAME=my-repo,_BRANCH_NAME=master + +POSITIONAL ARGUMENTS + Trigger resource - Build Trigger. 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 TRIGGER 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. + + TRIGGER + ID of the trigger or fully qualified identifier for the trigger. + + To set the trigger attribute: + ▸ provide the argument TRIGGER 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 location for the trigger. + + To set the region attribute: + ▸ provide the argument TRIGGER on the command line with a fully + specified name; + ▸ provide the argument --region on the command line; + ▸ set the property builds/region. + +REQUIRED FLAGS + Exactly one of these must be specified: + + --trigger-config=PATH + Path to Build Trigger config file (JSON or YAML format). For more + details, see + https://cloud.google.com/cloud-build/docs/api/reference/rest/v1/projects.triggers#BuildTrigger + + Flag based trigger configuration + + --description=DESCRIPTION + Build trigger description. + + --ignored-files=[GLOB,...] + Glob filter. Changes only affecting ignored files won't trigger + builds. + + --include-logs-with-status + Build logs will be sent back to GitHub as part of the checkrun + result. + + --included-files=[GLOB,...] + Glob filter. Changes affecting at least one included file will + trigger builds. + + --[no-]require-approval + Require manual approval for triggered builds. Use + --require-approval to enable and --no-require-approval to disable. + + --service-account=SERVICE_ACCOUNT + The service account used for all user-controlled operations + including UpdateBuildTrigger, RunBuildTrigger, CreateBuild, and + CancelBuild. If no service account is set, then the standard Cloud + Build service account ([PROJECT_NUM]@system.gserviceaccount.com) is + used instead. Format: + projects/{PROJECT_ID}/serviceAccounts/{ACCOUNT_ID_OR_EMAIL}. + + At most one of these can be specified: + + --branch-pattern=REGEX + A regular expression specifying which git branches to match. + + This pattern is used as a regular expression search for any + incoming pushes. For example, --branch-pattern=foo will match + "foo", "foobar", and "barfoo". Events on a branch that does not + match will be ignored. + + The syntax of the regular expressions accepted is the syntax + accepted by RE2 and described at + https://github.com/google/re2/wiki/Syntax. + + --tag-pattern=REGEX + A regular expression specifying which git tags to match. + + This pattern is used as a regular expression search for any + incoming pushes. For example, --tag-pattern=foo will match "foo", + "foobar", and "barfoo". Events on a tag that does not match will + be ignored. + + The syntax of the regular expressions accepted is the syntax + accepted by RE2 and described at + https://github.com/google/re2/wiki/Syntax. + + Pull Request settings + + --comment-control=COMMENT_CONTROL; default="COMMENTS_ENABLED" + Require a repository collaborator or owner to comment '/gcbrun' + on a pull request before running the build. COMMENT_CONTROL + must be one of: + + COMMENTS_DISABLED + Do not require comments on Pull Requests before builds are + triggered. + COMMENTS_ENABLED + Enforce that repository owners or collaborators must + comment on Pull Requests before builds are triggered. + COMMENTS_ENABLED_FOR_EXTERNAL_CONTRIBUTORS_ONLY + Enforce that repository owners or collaborators must + comment on external contributors' Pull Requests before + builds are triggered. + + --pull-request-pattern=REGEX + A regular expression specifying which base git branch to match + for pull request events. + + This pattern is used as a regex search for the base branch (the + branch you are trying to merge into) for pull request updates. + For example, --pull-request-pattern=foo will match "foo", + "foobar", and "barfoo". + + The syntax of the regular expressions accepted is the syntax + accepted by RE2 and described at + https://github.com/google/re2/wiki/Syntax. + + At most one of these can be specified: + + --build-config=PATH + Path to a YAML or JSON file containing the build configuration in + the repository. + + For more details, see: + https://cloud.google.com/cloud-build/docs/build-config + + --inline-config=PATH + Local path to a YAML or JSON file containing a build + configuration. + + Dockerfile build configuration flags + + --dockerfile=DOCKERFILE + Path of Dockerfile to use for builds in the repository. + + If specified, a build config will be generated to run docker + build using the specified file. + + The filename is relative to the Dockerfile directory. + + This flag argument must be specified if any of the other + arguments in this group are specified. + + --dockerfile-image=DOCKERFILE_IMAGE + Docker image name to build. + + This flag argument must be specified if any of the other + arguments in this group are specified. + + --dockerfile-dir=DOCKERFILE_DIR + Location of the directory containing the Dockerfile in the + repository. + + The directory will also be used as the Docker build context. + + At most one of these can be specified: + + --clear-substitutions + Clear existing substitutions. + + --remove-substitutions=[KEY,...] + Remove existing substitutions if present. + + --update-substitutions=[KEY=VALUE,...] + Update or add to existing substitutions. Substitutions are + parameters to be substituted or add in the build specification. + + For example (using some nonsensical substitution keys; all keys + must begin with an underscore): + + $ gcloud builds triggers update ... + --update-substitutions _FAVORITE_COLOR=blue,_NUM_CANDIES=10 + + This will add the provided substitutions to the existing + substitutions and results in a build where every occurrence of + ${_FAVORITE_COLOR} in certain fields is replaced by "blue", and + similarly for ${_NUM_CANDIES} and "10". + + Only the following built-in variables can be specified with the + --substitutions flag: REPO_NAME, BRANCH_NAME, TAG_NAME, + REVISION_ID, COMMIT_SHA, SHORT_SHA. + + For more details, see: + https://cloud.google.com/build/docs/build-config-file-schema#substitutions + + At most one of these can be specified: + + --repository=REPOSITORY + Repository resource (2nd gen) to use, in the format + "projects/*/locations/*/connections/*/repositories/". + + --enterprise-config=ENTERPRISE_CONFIG + Resource name of the GitHub Enterprise config that should be + applied to this installation. + + For example: + "projects/{$project_id}/locations/{$location_id}/githubEnterpriseConfigs/{$config_id} + + --repo-name=REPO_NAME + Name of the GitHub Repository. + + --repo-owner=REPO_OWNER + Owner of the GitHub Repository. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud builds triggers update github + + $ gcloud alpha builds triggers update github + diff --git a/gcloud/beta/builds/triggers/update/gitlab b/gcloud/beta/builds/triggers/update/gitlab new file mode 100644 index 000000000..6e122e903 --- /dev/null +++ b/gcloud/beta/builds/triggers/update/gitlab @@ -0,0 +1,252 @@ +NAME + gcloud beta builds triggers update gitlab - updates GitLab trigger used by + Google Cloud Build + +SYNOPSIS + gcloud beta builds triggers update gitlab (TRIGGER : --region=REGION) + (--trigger-config=PATH | --description=DESCRIPTION + --ignored-files=[GLOB,...] --included-files=[GLOB,...] + --repository=REPOSITORY --[no-]require-approval + --service-account=SERVICE_ACCOUNT --branch-pattern=REGEX + | --tag-pattern=REGEX | --comment-control=COMMENT_CONTROL + --pull-request-pattern=REGEX --build-config=PATH + | --inline-config=PATH + | [--dockerfile=DOCKERFILE --dockerfile-image=DOCKERFILE_IMAGE + : --dockerfile-dir=DOCKERFILE_DIR] --clear-substitutions + | --remove-substitutions=[KEY,...] + | --update-substitutions=[KEY=VALUE,...]) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Updates GitLab trigger used by Google Cloud Build. + +EXAMPLES + To update the branch pattern of the trigger: + + $ gcloud beta builds triggers update gitlab my-trigger \ + --branch-pattern=".*" + + To update the build config of the trigger: + + $ gcloud beta builds triggers update gitlab my-trigger \ + --build-config="cloudbuild.yaml" + + To update the substitutions of the trigger: + + $ gcloud beta builds triggers update gitlab my-trigger \ + --update-substitutions=_REPO_NAME=my-repo,_BRANCH_NAME=master + + To update the 2nd-gen repository resource of the trigger: + + $ gcloud beta builds triggers update gitlab my-trigger \ + --repository=projects/my-project/locations/us-west1/\ + connections/my-conn/repositories/my-repo + +POSITIONAL ARGUMENTS + Trigger resource - Build Trigger. 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 TRIGGER 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. + + TRIGGER + ID of the trigger or fully qualified identifier for the trigger. + + To set the trigger attribute: + ▸ provide the argument TRIGGER 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 location for the trigger. + + To set the region attribute: + ▸ provide the argument TRIGGER on the command line with a fully + specified name; + ▸ provide the argument --region on the command line; + ▸ set the property builds/region. + +REQUIRED FLAGS + Exactly one of these must be specified: + + --trigger-config=PATH + Path to Build Trigger config file (JSON or YAML format). For more + details, see + https://cloud.google.com/cloud-build/docs/api/reference/rest/v1/projects.triggers#BuildTrigger + + Flag based trigger configuration + + --description=DESCRIPTION + Build trigger description. + + --ignored-files=[GLOB,...] + Glob filter. Changes only affecting ignored files won't trigger + builds. + + --included-files=[GLOB,...] + Glob filter. Changes affecting at least one included file will + trigger builds. + + --repository=REPOSITORY + Repository resource (2nd gen) to use, in the format + "projects/*/locations/*/connections/*/repositories/". + + --[no-]require-approval + Require manual approval for triggered builds. Use + --require-approval to enable and --no-require-approval to disable. + + --service-account=SERVICE_ACCOUNT + The service account used for all user-controlled operations + including UpdateBuildTrigger, RunBuildTrigger, CreateBuild, and + CancelBuild. If no service account is set, then the standard Cloud + Build service account ([PROJECT_NUM]@system.gserviceaccount.com) is + used instead. Format: + projects/{PROJECT_ID}/serviceAccounts/{ACCOUNT_ID_OR_EMAIL}. + + At most one of these can be specified: + + --branch-pattern=REGEX + A regular expression specifying which git branches to match. + + This pattern is used as a regular expression search for any + incoming pushes. For example, --branch-pattern=foo will match + "foo", "foobar", and "barfoo". Events on a branch that does not + match will be ignored. + + The syntax of the regular expressions accepted is the syntax + accepted by RE2 and described at + https://github.com/google/re2/wiki/Syntax. + + --tag-pattern=REGEX + A regular expression specifying which git tags to match. + + This pattern is used as a regular expression search for any + incoming pushes. For example, --tag-pattern=foo will match "foo", + "foobar", and "barfoo". Events on a tag that does not match will + be ignored. + + The syntax of the regular expressions accepted is the syntax + accepted by RE2 and described at + https://github.com/google/re2/wiki/Syntax. + + Pull Request settings + + --comment-control=COMMENT_CONTROL + Require a repository collaborator or owner to comment '/gcbrun' + on a pull request before running the build. COMMENT_CONTROL + must be one of: + + COMMENTS_DISABLED + Do not require comments on Pull Requests before builds are + triggered. + COMMENTS_ENABLED + Enforce that repository owners or collaborators must + comment on Pull Requests before builds are triggered. + COMMENTS_ENABLED_FOR_EXTERNAL_CONTRIBUTORS_ONLY + Enforce that repository owners or collaborators must + comment on external contributors' Pull Requests before + builds are triggered. + + --pull-request-pattern=REGEX + A regular expression specifying which base git branch to match + for pull request events. + + This pattern is used as a regular expression search for the + base branch (the branch you are trying to merge into) for pull + request updates. For example, --pull-request-pattern=foo will + match "foo", "foobar", and "barfoo". + + The syntax of the regular expressions accepted is the syntax + accepted by RE2 and described at + https://github.com/google/re2/wiki/Syntax. + + At most one of these can be specified: + + --build-config=PATH + Path to a YAML or JSON file containing the build configuration in + the repository. + + For more details, see: + https://cloud.google.com/cloud-build/docs/build-config + + --inline-config=PATH + Local path to a YAML or JSON file containing a build + configuration. + + Dockerfile build configuration flags + + --dockerfile=DOCKERFILE + Path of Dockerfile to use for builds in the repository. + + If specified, a build config will be generated to run docker + build using the specified file. + + The filename is relative to the Dockerfile directory. + + This flag argument must be specified if any of the other + arguments in this group are specified. + + --dockerfile-image=DOCKERFILE_IMAGE + Docker image name to build. + + This flag argument must be specified if any of the other + arguments in this group are specified. + + --dockerfile-dir=DOCKERFILE_DIR + Location of the directory containing the Dockerfile in the + repository. + + The directory will also be used as the Docker build context. + + At most one of these can be specified: + + --clear-substitutions + Clear existing substitutions. + + --remove-substitutions=[KEY,...] + Remove existing substitutions if present. + + --update-substitutions=[KEY=VALUE,...] + Update or add to existing substitutions. Substitutions are + parameters to be substituted or add in the build specification. + + For example (using some nonsensical substitution keys; all keys + must begin with an underscore): + + $ gcloud builds triggers update ... + --update-substitutions _FAVORITE_COLOR=blue,_NUM_CANDIES=10 + + This will add the provided substitutions to the existing + substitutions and results in a build where every occurrence of + ${_FAVORITE_COLOR} in certain fields is replaced by "blue", and + similarly for ${_NUM_CANDIES} and "10". + + Only the following built-in variables can be specified with the + --substitutions flag: REPO_NAME, BRANCH_NAME, TAG_NAME, + REVISION_ID, COMMIT_SHA, SHORT_SHA. + + For more details, see: + https://cloud.google.com/build/docs/build-config-file-schema#substitutions + +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 builds triggers update gitlab + + $ gcloud alpha builds triggers update gitlab + diff --git a/gcloud/beta/builds/triggers/update/help b/gcloud/beta/builds/triggers/update/help new file mode 100644 index 000000000..f96ab796e --- /dev/null +++ b/gcloud/beta/builds/triggers/update/help @@ -0,0 +1,47 @@ +NAME + gcloud beta builds triggers update - update Triggers in Google Cloud Build + +SYNOPSIS + gcloud beta builds triggers update COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Update Triggers in Google Cloud Build. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + bitbucketserver + (BETA) Updates Bitbucket Server trigger used by Google Cloud Build. + + cloud-source-repositories + (BETA) Updates Cloud Source Repositories trigger used by Google Cloud + Build. + + github + (BETA) Update GitHub trigger used by Google Cloud Build. + + gitlab + (BETA) Updates GitLab trigger used by Google Cloud Build. + + manual + (BETA) Updates a manual trigger used by Google Cloud Build. + + pubsub + (BETA) Update a Pub/Sub trigger used by Google Cloud Build. + + webhook + (BETA) Update a Webhook trigger used by Google Cloud Build. + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud builds triggers update + + $ gcloud alpha builds triggers update + diff --git a/gcloud/beta/builds/triggers/update/manual b/gcloud/beta/builds/triggers/update/manual new file mode 100644 index 000000000..228ee6fc9 --- /dev/null +++ b/gcloud/beta/builds/triggers/update/manual @@ -0,0 +1,226 @@ +NAME + gcloud beta builds triggers update manual - updates a manual trigger used + by Google Cloud Build + +SYNOPSIS + gcloud beta builds triggers update manual (TRIGGER : --region=REGION) + (--trigger-config=PATH | --description=DESCRIPTION + --[no-]require-approval + --service-account=SERVICE_ACCOUNT --clear-substitutions + | --remove-substitutions=[KEY,...] + | --update-substitutions=[KEY=VALUE,...] --inline-config=PATH + | [--dockerfile=DOCKERFILE : --dockerfile-dir=DOCKERFILE_DIR + --dockerfile-image=DOCKERFILE_IMAGE] + | --git-file-source-branch=GIT_FILE_SOURCE_BRANCH + | --git-file-source-tag=GIT_FILE_SOURCE_TAG + --git-file-source-github-enterprise-config=GIT_FILE_SOURCE_GITHUB_ENTERPRISE_CONFIG --git-file-source-path=PATH --git-file-source-repo-type=GIT_FILE_SOURCE_REPO_TYPE --git-file-source-uri=URL --source-to-build-branch=SOURCE_TO_BUILD_BRANCH | --source-to-build-tag=SOURCE_TO_BUILD_TAG --source-to-build-github-enterprise-config=SOURCE_TO_BUILD_GITHUB_ENTERPRISE_CONFIG --source-to-build-repo-type=SOURCE_TO_BUILD_REPO_TYPE --source-to-build-uri=SOURCE_TO_BUILD_URI) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Updates a manual trigger used by Google Cloud Build. + +EXAMPLES + To update the branch from which the trigger clones: + + $ gcloud beta builds triggers update manual my-trigger \ + --source-to-build-branch=my-branch + +POSITIONAL ARGUMENTS + Trigger resource - Build Trigger. 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 TRIGGER 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. + + TRIGGER + ID of the trigger or fully qualified identifier for the trigger. + + To set the trigger attribute: + ▸ provide the argument TRIGGER 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 location for the trigger. + + To set the region attribute: + ▸ provide the argument TRIGGER on the command line with a fully + specified name; + ▸ provide the argument --region on the command line; + ▸ set the property builds/region. + +REQUIRED FLAGS + Exactly one of these must be specified: + + --trigger-config=PATH + Path to Build Trigger config file (JSON or YAML format). For more + details, see + https://cloud.google.com/cloud-build/docs/api/reference/rest/v1/projects.triggers#BuildTrigger + + Flag based trigger configuration + + --description=DESCRIPTION + Build trigger description. + + --[no-]require-approval + Require manual approval for triggered builds. Use + --require-approval to enable and --no-require-approval to disable. + + --service-account=SERVICE_ACCOUNT + The service account used for all user-controlled operations + including UpdateBuildTrigger, RunBuildTrigger, CreateBuild, and + CancelBuild. If no service account is set, then the standard Cloud + Build service account ([PROJECT_NUM]@system.gserviceaccount.com) is + used instead. Format: + projects/{PROJECT_ID}/serviceAccounts/{ACCOUNT_ID_OR_EMAIL}. + + At most one of these can be specified: + + --clear-substitutions + Clear existing substitutions. + + --remove-substitutions=[KEY,...] + Remove existing substitutions if present. + + --update-substitutions=[KEY=VALUE,...] + Update or add to existing substitutions. Substitutions are + parameters to be substituted or add in the build specification. + + For example (using some nonsensical substitution keys; all keys + must begin with an underscore): + + $ gcloud builds triggers update ... + --update-substitutions _FAVORITE_COLOR=blue,_NUM_CANDIES=10 + + This will add the provided substitutions to the existing + substitutions and results in a build where every occurrence of + ${_FAVORITE_COLOR} in certain fields is replaced by "blue", and + similarly for ${_NUM_CANDIES} and "10". + + Only the following built-in variables can be specified with the + --substitutions flag: REPO_NAME, BRANCH_NAME, TAG_NAME, + REVISION_ID, COMMIT_SHA, SHORT_SHA. + + For more details, see: + https://cloud.google.com/build/docs/build-config-file-schema#substitutions + + At most one of these can be specified: + + --inline-config=PATH + Local path to a YAML or JSON file containing a build + configuration. + + Dockerfile build configuration flags + + --dockerfile=DOCKERFILE + Path of Dockerfile to use for builds in the repository. + + If specified, a build config will be generated to run docker + build using the specified file. + + The filename is relative to the Dockerfile directory. + + This flag argument must be specified if any of the other + arguments in this group are specified. + + --dockerfile-dir=DOCKERFILE_DIR + Location of the directory containing the Dockerfile in the + repository. + + The directory will also be used as the Docker build context. + + --dockerfile-image=DOCKERFILE_IMAGE + Docker image name to build. + + If not specified, + gcr.io/PROJECT/github.com/REPO_OWNER/REPO_NAME:$COMMIT_SHA will + be used. + + Use a build configuration (cloudbuild.yaml) file for building + multiple images in a single trigger. + + Build file source flags + + At most one of these can be specified: + + --git-file-source-branch=GIT_FILE_SOURCE_BRANCH + The branch of the repository to clone when trigger is + invoked. + + --git-file-source-tag=GIT_FILE_SOURCE_TAG + The tag of the repository to clone when trigger is invoked. + + At most one of these can be specified: + + --git-file-source-github-enterprise-config=GIT_FILE_SOURCE_GITHUB_ENTERPRISE_CONFIG + The resource name of the GitHub Enterprise config that should + be applied to this source. + + --git-file-source-path=PATH + The file in the repository to clone when trigger is invoked. + + --git-file-source-repo-type=GIT_FILE_SOURCE_REPO_TYPE + The type of the repository to clone when trigger is invoked. + + This flag argument must be specified if any of the other + arguments in this group are specified. + + --git-file-source-uri=URL + The URI of the repository to clone when trigger is invoked. + + 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: + + --source-to-build-branch=SOURCE_TO_BUILD_BRANCH + Branch to build. + + --source-to-build-tag=SOURCE_TO_BUILD_TAG + Tag to build. + + At most one of these can be specified: + + --source-to-build-github-enterprise-config=SOURCE_TO_BUILD_GITHUB_ENTERPRISE_CONFIG + The resource name of the GitHub Enterprise config that should be + applied to this source (1st gen). Format: + projects/{project}/locations/{location}/githubEnterpriseConfigs/{id} + or projects/{project}/githubEnterpriseConfigs/{id} + + --source-to-build-repo-type=SOURCE_TO_BUILD_REPO_TYPE + Type of the repository (1st gen). Currently only GitHub and Cloud + Source Repository types are supported. + + This flag argument must be specified if any of the other + arguments in this group are specified. + + --source-to-build-uri=SOURCE_TO_BUILD_URI + The URI of the repository that should be applied to this source + (1st gen). + + 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 builds triggers update manual + + $ gcloud alpha builds triggers update manual + diff --git a/gcloud/beta/builds/triggers/update/pubsub b/gcloud/beta/builds/triggers/update/pubsub new file mode 100644 index 000000000..a25fe3d2c --- /dev/null +++ b/gcloud/beta/builds/triggers/update/pubsub @@ -0,0 +1,243 @@ +NAME + gcloud beta builds triggers update pubsub - update a Pub/Sub trigger used + by Google Cloud Build + +SYNOPSIS + gcloud beta builds triggers update pubsub (TRIGGER : --region=REGION) + (--trigger-config=PATH | --description=DESCRIPTION + --[no-]require-approval --service-account=SERVICE_ACCOUNT + --subscription-filter=SUBSCRIPTION_FILTER + --topic=TOPIC --clear-substitutions + | --remove-substitutions=[KEY,...] + | --update-substitutions=[KEY=VALUE,...] --inline-config=PATH + | [--dockerfile=DOCKERFILE : --dockerfile-dir=DOCKERFILE_DIR + --dockerfile-image=DOCKERFILE_IMAGE] + | --git-file-source-branch=GIT_FILE_SOURCE_BRANCH + | --git-file-source-tag=GIT_FILE_SOURCE_TAG + --git-file-source-github-enterprise-config=GIT_FILE_SOURCE_GITHUB_ENTERPRISE_CONFIG --git-file-source-path=PATH --git-file-source-repo-type=GIT_FILE_SOURCE_REPO_TYPE --git-file-source-uri=URL --source-to-build-branch=SOURCE_TO_BUILD_BRANCH | --source-to-build-tag=SOURCE_TO_BUILD_TAG --source-to-build-github-enterprise-config=SOURCE_TO_BUILD_GITHUB_ENTERPRISE_CONFIG --source-to-build-repo-type=SOURCE_TO_BUILD_REPO_TYPE --source-to-build-uri=SOURCE_TO_BUILD_URI) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Update a Pub/Sub trigger used by Google Cloud Build. + +EXAMPLES + To update the branch from which the trigger clones: + + $ gcloud beta builds triggers update pubsub my-trigger \ + --source-to-build-branch=my-branch + + To update the topic: + + $ gcloud beta builds triggers update pubsub my-trigger \ + --topic=projects/my-project/topics/my-topic + + To update the substitutions of the trigger: $ gcloud beta builds triggers update pubsub my-trigger \ + --update-substitutions=_REPO_NAME=my-repo,_BRANCH_NAME=master + +POSITIONAL ARGUMENTS + Trigger resource - Build Trigger. 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 TRIGGER 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. + + TRIGGER + ID of the trigger or fully qualified identifier for the trigger. + + To set the trigger attribute: + ▸ provide the argument TRIGGER 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 location for the trigger. + + To set the region attribute: + ▸ provide the argument TRIGGER on the command line with a fully + specified name; + ▸ provide the argument --region on the command line; + ▸ set the property builds/region. + +REQUIRED FLAGS + Exactly one of these must be specified: + + --trigger-config=PATH + Path to Build Trigger config file (JSON or YAML format). For more + details, see + https://cloud.google.com/cloud-build/docs/api/reference/rest/v1/projects.triggers#BuildTrigger + + Flag based trigger configuration + + --description=DESCRIPTION + Build trigger description. + + --[no-]require-approval + Require manual approval for triggered builds. Use + --require-approval to enable and --no-require-approval to disable. + + --service-account=SERVICE_ACCOUNT + The service account used for all user-controlled operations + including UpdateBuildTrigger, RunBuildTrigger, CreateBuild, and + CancelBuild. If no service account is set, then the standard Cloud + Build service account ([PROJECT_NUM]@system.gserviceaccount.com) is + used instead. Format: + projects/{PROJECT_ID}/serviceAccounts/{ACCOUNT_ID_OR_EMAIL}. + + --subscription-filter=SUBSCRIPTION_FILTER + CEL filter expression for the trigger. See + https://cloud.google.com/build/docs/filter-build-events-using-cel + for more details. + + --topic=TOPIC + The topic to which this trigger should subscribe. + + At most one of these can be specified: + + --clear-substitutions + Clear existing substitutions. + + --remove-substitutions=[KEY,...] + Remove existing substitutions if present. + + --update-substitutions=[KEY=VALUE,...] + Update or add to existing substitutions. Substitutions are + parameters to be substituted or add in the build specification. + + For example (using some nonsensical substitution keys; all keys + must begin with an underscore): + + $ gcloud builds triggers update ... + --update-substitutions _FAVORITE_COLOR=blue,_NUM_CANDIES=10 + + This will add the provided substitutions to the existing + substitutions and results in a build where every occurrence of + ${_FAVORITE_COLOR} in certain fields is replaced by "blue", and + similarly for ${_NUM_CANDIES} and "10". + + Only the following built-in variables can be specified with the + --substitutions flag: REPO_NAME, BRANCH_NAME, TAG_NAME, + REVISION_ID, COMMIT_SHA, SHORT_SHA. + + For more details, see: + https://cloud.google.com/build/docs/build-config-file-schema#substitutions + + At most one of these can be specified: + + --inline-config=PATH + Local path to a YAML or JSON file containing a build + configuration. + + Dockerfile build configuration flags + + --dockerfile=DOCKERFILE + Path of Dockerfile to use for builds in the repository. + + If specified, a build config will be generated to run docker + build using the specified file. + + The filename is relative to the Dockerfile directory. + + This flag argument must be specified if any of the other + arguments in this group are specified. + + --dockerfile-dir=DOCKERFILE_DIR + Location of the directory containing the Dockerfile in the + repository. + + The directory will also be used as the Docker build context. + + --dockerfile-image=DOCKERFILE_IMAGE + Docker image name to build. + + If not specified, + gcr.io/PROJECT/github.com/REPO_OWNER/REPO_NAME:$COMMIT_SHA will + be used. + + Use a build configuration (cloudbuild.yaml) file for building + multiple images in a single trigger. + + Build file source flags + + At most one of these can be specified: + + --git-file-source-branch=GIT_FILE_SOURCE_BRANCH + The branch of the repository to clone when trigger is + invoked. + + --git-file-source-tag=GIT_FILE_SOURCE_TAG + The tag of the repository to clone when trigger is invoked. + + At most one of these can be specified: + + --git-file-source-github-enterprise-config=GIT_FILE_SOURCE_GITHUB_ENTERPRISE_CONFIG + The resource name of the GitHub Enterprise config that should + be applied to this source. + + --git-file-source-path=PATH + The file in the repository to clone when trigger is invoked. + + --git-file-source-repo-type=GIT_FILE_SOURCE_REPO_TYPE + The type of the repository to clone when trigger is invoked. + + This flag argument must be specified if any of the other + arguments in this group are specified. + + --git-file-source-uri=URL + The URI of the repository to clone when trigger is invoked. + + 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: + + --source-to-build-branch=SOURCE_TO_BUILD_BRANCH + Branch to build. + + --source-to-build-tag=SOURCE_TO_BUILD_TAG + Tag to build. + + At most one of these can be specified: + + --source-to-build-github-enterprise-config=SOURCE_TO_BUILD_GITHUB_ENTERPRISE_CONFIG + The resource name of the GitHub Enterprise config that should be + applied to this source (1st gen). Format: + projects/{project}/locations/{location}/githubEnterpriseConfigs/{id} + or projects/{project}/githubEnterpriseConfigs/{id} + + --source-to-build-repo-type=SOURCE_TO_BUILD_REPO_TYPE + Type of the repository (1st gen). Currently only GitHub and Cloud + Source Repository types are supported. + + This flag argument must be specified if any of the other + arguments in this group are specified. + + --source-to-build-uri=SOURCE_TO_BUILD_URI + The URI of the repository that should be applied to this source + (1st gen). + + 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 builds triggers update pubsub + + $ gcloud alpha builds triggers update pubsub + diff --git a/gcloud/beta/builds/triggers/update/webhook b/gcloud/beta/builds/triggers/update/webhook new file mode 100644 index 000000000..01e417680 --- /dev/null +++ b/gcloud/beta/builds/triggers/update/webhook @@ -0,0 +1,245 @@ +NAME + gcloud beta builds triggers update webhook - update a Webhook trigger used + by Google Cloud Build + +SYNOPSIS + gcloud beta builds triggers update webhook (TRIGGER : --region=REGION) + (--trigger-config=PATH | --description=DESCRIPTION + --[no-]require-approval --secret=SECRET + --service-account=SERVICE_ACCOUNT + --subscription-filter=SUBSCRIPTION_FILTER --clear-substitutions + | --remove-substitutions=[KEY,...] + | --update-substitutions=[KEY=VALUE,...] --inline-config=PATH + | [--dockerfile=DOCKERFILE : --dockerfile-dir=DOCKERFILE_DIR + --dockerfile-image=DOCKERFILE_IMAGE] + | --git-file-source-branch=GIT_FILE_SOURCE_BRANCH + | --git-file-source-tag=GIT_FILE_SOURCE_TAG + --git-file-source-github-enterprise-config=GIT_FILE_SOURCE_GITHUB_ENTERPRISE_CONFIG --git-file-source-path=PATH --git-file-source-repo-type=GIT_FILE_SOURCE_REPO_TYPE --git-file-source-uri=URL --source-to-build-branch=SOURCE_TO_BUILD_BRANCH | --source-to-build-tag=SOURCE_TO_BUILD_TAG --source-to-build-github-enterprise-config=SOURCE_TO_BUILD_GITHUB_ENTERPRISE_CONFIG --source-to-build-repo-type=SOURCE_TO_BUILD_REPO_TYPE --source-to-build-uri=SOURCE_TO_BUILD_URI) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Update a Webhook trigger used by Google Cloud Build. + +EXAMPLES + To update the branch from which the trigger clones: + + $ gcloud beta builds triggers update webhook my-webhook-trigger \ + --source-to-build-branch=my-branch + + To update the webhook secret: + + $ gcloud beta builds triggers update webhook my-webhook-trigger \ + --secret=projects/my-project/secrets/my-secret/versions/2 + + To update the substitutions of the trigger: $ gcloud beta builds triggers update webhook my-trigger \ + --update-substitutions=_REPO_NAME=my-repo,_BRANCH_NAME=master + +POSITIONAL ARGUMENTS + Trigger resource - Build Trigger. 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 TRIGGER 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. + + TRIGGER + ID of the trigger or fully qualified identifier for the trigger. + + To set the trigger attribute: + ▸ provide the argument TRIGGER 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 location for the trigger. + + To set the region attribute: + ▸ provide the argument TRIGGER on the command line with a fully + specified name; + ▸ provide the argument --region on the command line; + ▸ set the property builds/region. + +REQUIRED FLAGS + Exactly one of these must be specified: + + --trigger-config=PATH + Path to Build Trigger config file (JSON or YAML format). For more + details, see + https://cloud.google.com/cloud-build/docs/api/reference/rest/v1/projects.triggers#BuildTrigger + + Flag based trigger configuration + + --description=DESCRIPTION + Build trigger description. + + --[no-]require-approval + Require manual approval for triggered builds. Use + --require-approval to enable and --no-require-approval to disable. + + --secret=SECRET + The full path of the secret version required to validate webhook + requests against this trigger. For example, + projects/my-project/secrets/my-secret/versions/1. + + --service-account=SERVICE_ACCOUNT + The service account used for all user-controlled operations + including UpdateBuildTrigger, RunBuildTrigger, CreateBuild, and + CancelBuild. If no service account is set, then the standard Cloud + Build service account ([PROJECT_NUM]@system.gserviceaccount.com) is + used instead. Format: + projects/{PROJECT_ID}/serviceAccounts/{ACCOUNT_ID_OR_EMAIL}. + + --subscription-filter=SUBSCRIPTION_FILTER + CEL filter expression for the trigger. See + https://cloud.google.com/build/docs/filter-build-events-using-cel + for more details. + + At most one of these can be specified: + + --clear-substitutions + Clear existing substitutions. + + --remove-substitutions=[KEY,...] + Remove existing substitutions if present. + + --update-substitutions=[KEY=VALUE,...] + Update or add to existing substitutions. Substitutions are + parameters to be substituted or add in the build specification. + + For example (using some nonsensical substitution keys; all keys + must begin with an underscore): + + $ gcloud builds triggers update ... + --update-substitutions _FAVORITE_COLOR=blue,_NUM_CANDIES=10 + + This will add the provided substitutions to the existing + substitutions and results in a build where every occurrence of + ${_FAVORITE_COLOR} in certain fields is replaced by "blue", and + similarly for ${_NUM_CANDIES} and "10". + + Only the following built-in variables can be specified with the + --substitutions flag: REPO_NAME, BRANCH_NAME, TAG_NAME, + REVISION_ID, COMMIT_SHA, SHORT_SHA. + + For more details, see: + https://cloud.google.com/build/docs/build-config-file-schema#substitutions + + At most one of these can be specified: + + --inline-config=PATH + Local path to a YAML or JSON file containing a build + configuration. + + Dockerfile build configuration flags + + --dockerfile=DOCKERFILE + Path of Dockerfile to use for builds in the repository. + + If specified, a build config will be generated to run docker + build using the specified file. + + The filename is relative to the Dockerfile directory. + + This flag argument must be specified if any of the other + arguments in this group are specified. + + --dockerfile-dir=DOCKERFILE_DIR + Location of the directory containing the Dockerfile in the + repository. + + The directory will also be used as the Docker build context. + + --dockerfile-image=DOCKERFILE_IMAGE + Docker image name to build. + + If not specified, + gcr.io/PROJECT/github.com/REPO_OWNER/REPO_NAME:$COMMIT_SHA will + be used. + + Use a build configuration (cloudbuild.yaml) file for building + multiple images in a single trigger. + + Build file source flags + + At most one of these can be specified: + + --git-file-source-branch=GIT_FILE_SOURCE_BRANCH + The branch of the repository to clone when trigger is + invoked. + + --git-file-source-tag=GIT_FILE_SOURCE_TAG + The tag of the repository to clone when trigger is invoked. + + At most one of these can be specified: + + --git-file-source-github-enterprise-config=GIT_FILE_SOURCE_GITHUB_ENTERPRISE_CONFIG + The resource name of the GitHub Enterprise config that should + be applied to this source. + + --git-file-source-path=PATH + The file in the repository to clone when trigger is invoked. + + --git-file-source-repo-type=GIT_FILE_SOURCE_REPO_TYPE + The type of the repository to clone when trigger is invoked. + + This flag argument must be specified if any of the other + arguments in this group are specified. + + --git-file-source-uri=URL + The URI of the repository to clone when trigger is invoked. + + 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: + + --source-to-build-branch=SOURCE_TO_BUILD_BRANCH + Branch to build. + + --source-to-build-tag=SOURCE_TO_BUILD_TAG + Tag to build. + + At most one of these can be specified: + + --source-to-build-github-enterprise-config=SOURCE_TO_BUILD_GITHUB_ENTERPRISE_CONFIG + The resource name of the GitHub Enterprise config that should be + applied to this source (1st gen). Format: + projects/{project}/locations/{location}/githubEnterpriseConfigs/{id} + or projects/{project}/githubEnterpriseConfigs/{id} + + --source-to-build-repo-type=SOURCE_TO_BUILD_REPO_TYPE + Type of the repository (1st gen). Currently only GitHub and Cloud + Source Repository types are supported. + + This flag argument must be specified if any of the other + arguments in this group are specified. + + --source-to-build-uri=SOURCE_TO_BUILD_URI + The URI of the repository that should be applied to this source + (1st gen). + + 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 builds triggers update webhook + + $ gcloud alpha builds triggers update webhook + diff --git a/gcloud/beta/compute/instance-templates/create b/gcloud/beta/compute/instance-templates/create index a5ad6e708..89d4e45b5 100644 --- a/gcloud/beta/compute/instance-templates/create +++ b/gcloud/beta/compute/instance-templates/create @@ -23,8 +23,9 @@ SYNOPSIS [--ipv6-network-tier=IPV6_NETWORK_TIER] [--key-revocation-action-type=POLICY] [--labels=[KEY=VALUE,...]] [--local-ssd=[device-name=DEVICE-NAME], - [interface=INTERFACE],[size=SIZE]] [--machine-type=MACHINE_TYPE] - [--maintenance-policy=MAINTENANCE_POLICY] + [interface=INTERFACE],[size=SIZE]] + [--local-ssd-recovery-timeout=LOCAL_SSD_RECOVERY_TIMEOUT] + [--machine-type=MACHINE_TYPE] [--maintenance-policy=MAINTENANCE_POLICY] [--max-run-duration=MAX_RUN_DURATION] [--mesh=[gke-cluster=GKE-CLUSTER],[workload=WORKLOAD]] [--metadata=KEY=VALUE,[KEY=VALUE,...]] @@ -449,6 +450,12 @@ FLAGS partitions. You can specify a maximum of 24 local SSDs for a maximum of 9TB attached to an instance. + --local-ssd-recovery-timeout=LOCAL_SSD_RECOVERY_TIMEOUT + Specifies the maximum amount of time a Local Ssd Vm should wait while + recovery of the Local Ssd state is attempted. Its value should be in + between 0 and 168 hours with hour granularity and the default value + being 1 hour. + --machine-type=MACHINE_TYPE Specifies the machine type used for the instances. To get a list of available machine types, run 'gcloud compute machine-types list'. If diff --git a/gcloud/beta/compute/instances/bulk/create b/gcloud/beta/compute/instances/bulk/create index 73fc26b75..820b1c719 100644 --- a/gcloud/beta/compute/instances/bulk/create +++ b/gcloud/beta/compute/instances/bulk/create @@ -22,6 +22,7 @@ SYNOPSIS [--labels=[KEY=VALUE,...]] [--local-ssd=[device-name=DEVICE-NAME], [interface=INTERFACE],[size=SIZE]] + [--local-ssd-recovery-timeout=LOCAL_SSD_RECOVERY_TIMEOUT] [--location-policy=[ZONE=POLICY,...]] [--machine-type=MACHINE_TYPE] [--max-count-per-zone=[ZONE=MAX_COUNT_PER_ZONE,...]] [--max-run-duration=MAX_RUN_DURATION] @@ -450,6 +451,12 @@ OPTIONAL FLAGS partitions. You can specify a maximum of 24 local SSDs for a maximum of 9TB attached to an instance. + --local-ssd-recovery-timeout=LOCAL_SSD_RECOVERY_TIMEOUT + Specifies the maximum amount of time a Local Ssd Vm should wait while + recovery of the Local Ssd state is attempted. Its value should be in + between 0 and 168 hours with hour granularity and the default value + being 1 hour. + --location-policy=[ZONE=POLICY,...] Policy for which zones to include or exclude during bulk instance creation within a region. Policy is defined as a list of key-value diff --git a/gcloud/beta/compute/instances/create b/gcloud/beta/compute/instances/create index 1dab67ad2..0a5e27de1 100644 --- a/gcloud/beta/compute/instances/create +++ b/gcloud/beta/compute/instances/create @@ -27,8 +27,9 @@ SYNOPSIS [--ipv6-public-ptr-domain=IPV6_PUBLIC_PTR_DOMAIN] [--key-revocation-action-type=POLICY] [--labels=[KEY=VALUE,...]] [--local-ssd=[device-name=DEVICE-NAME], - [interface=INTERFACE],[size=SIZE]] [--machine-type=MACHINE_TYPE] - [--maintenance-policy=MAINTENANCE_POLICY] + [interface=INTERFACE],[size=SIZE]] + [--local-ssd-recovery-timeout=LOCAL_SSD_RECOVERY_TIMEOUT] + [--machine-type=MACHINE_TYPE] [--maintenance-policy=MAINTENANCE_POLICY] [--max-run-duration=MAX_RUN_DURATION] [--metadata=KEY=VALUE,[KEY=VALUE,...]] [--metadata-from-file=KEY=LOCAL_FILE_PATH,[...]] @@ -530,6 +531,12 @@ FLAGS partitions. You can specify a maximum of 24 local SSDs for a maximum of 9TB attached to an instance. + --local-ssd-recovery-timeout=LOCAL_SSD_RECOVERY_TIMEOUT + Specifies the maximum amount of time a Local Ssd Vm should wait while + recovery of the Local Ssd state is attempted. Its value should be in + between 0 and 168 hours with hour granularity and the default value + being 1 hour. + --machine-type=MACHINE_TYPE Specifies the machine type used for the instances. To get a list of available machine types, run 'gcloud compute machine-types list'. If diff --git a/gcloud/beta/compute/instances/create-with-container b/gcloud/beta/compute/instances/create-with-container index e06993ec2..55059f599 100644 --- a/gcloud/beta/compute/instances/create-with-container +++ b/gcloud/beta/compute/instances/create-with-container @@ -32,6 +32,7 @@ SYNOPSIS [--instance-termination-action=INSTANCE_TERMINATION_ACTION] [--labels=[KEY=VALUE,...]] [--local-ssd=[device-name=DEVICE-NAME],[interface=INTERFACE]] + [--local-ssd-recovery-timeout=LOCAL_SSD_RECOVERY_TIMEOUT] [--machine-type=MACHINE_TYPE] [--maintenance-policy=MAINTENANCE_POLICY] [--metadata=KEY=VALUE,[KEY=VALUE,...]] [--metadata-from-file=KEY=LOCAL_FILE_PATH,[...]] @@ -463,6 +464,12 @@ FLAGS supported by more guest operating systems. NVME might provide higher performance. + --local-ssd-recovery-timeout=LOCAL_SSD_RECOVERY_TIMEOUT + Specifies the maximum amount of time a Local Ssd Vm should wait while + recovery of the Local Ssd state is attempted. Its value should be in + between 0 and 168 hours with hour granularity and the default value + being 1 hour. + --machine-type=MACHINE_TYPE Specifies the machine type used for the instances. To get a list of available machine types, run 'gcloud compute machine-types list'. If diff --git a/gcloud/beta/compute/instances/set-scheduling b/gcloud/beta/compute/instances/set-scheduling index ab75877de..ed72e3dc7 100644 --- a/gcloud/beta/compute/instances/set-scheduling +++ b/gcloud/beta/compute/instances/set-scheduling @@ -6,6 +6,7 @@ SYNOPSIS gcloud beta compute instances set-scheduling INSTANCE_NAME [--clear-min-node-cpu] [--host-error-timeout-seconds=HOST_ERROR_TIMEOUT_SECONDS] + [--local-ssd-recovery-timeout=LOCAL_SSD_RECOVERY_TIMEOUT] [--maintenance-policy=MAINTENANCE_POLICY] [--min-node-cpu=MIN_NODE_CPU] [--[no-]preemptible] [--provisioning-model=PROVISIONING_MODEL] [--[no-]restart-on-failure] [--zone=ZONE] @@ -45,6 +46,12 @@ FLAGS with 30 second increments, with a range of 90 to 330 seconds. If unset, the default behavior of the host error recovery is used. + --local-ssd-recovery-timeout=LOCAL_SSD_RECOVERY_TIMEOUT + Specifies the maximum amount of time a Local Ssd Vm should wait while + recovery of the Local Ssd state is attempted. Its value should be in + between 0 and 168 hours with hour granularity and the default value + being 1 hour. + --maintenance-policy=MAINTENANCE_POLICY Specifies the behavior of the VMs when their host machines undergo maintenance. The default is MIGRATE. For more information, see diff --git a/gcloud/beta/compute/interconnects/create b/gcloud/beta/compute/interconnects/create index 9c6869c77..d7919683f 100644 --- a/gcloud/beta/compute/interconnects/create +++ b/gcloud/beta/compute/interconnects/create @@ -8,7 +8,8 @@ SYNOPSIS --location=LOCATION --requested-link-count=REQUESTED_LINK_COUNT [--admin-enabled] [--customer-name=CUSTOMER_NAME] [--description=DESCRIPTION] [--noc-contact-email=NOC_CONTACT_EMAIL] - [--remote-location=REMOTE_LOCATION] [GCLOUD_WIDE_FLAG ...] + [--remote-location=REMOTE_LOCATION] + [--requested-features=[FEATURES,...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) gcloud beta compute interconnects create is used to create @@ -96,6 +97,17 @@ OPTIONAL FLAGS remote-locations list command to find the appropriate remote location to use when creating a Cross-Cloud Interconnect. + --requested-features=[FEATURES,...] + List of features requested for this interconnect. FEATURES must be + (only one value is supported): + + MACSEC + If specified then the interconnect will be created on MACsec + capable hardware ports. If not specified, the default value is + false, which will allocate non-MACsec capable ports first if + available. This parameter can only be provided during interconnect + INSERT and cannot be changed using interconnect PATCH. + GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, diff --git a/gcloud/beta/compute/interconnects/help b/gcloud/beta/compute/interconnects/help index d4fa9f0a8..6a1eda847 100644 --- a/gcloud/beta/compute/interconnects/help +++ b/gcloud/beta/compute/interconnects/help @@ -29,6 +29,10 @@ GROUPS locations (BETA) Read and manipulate Compute Engine interconnect locations. + macsec + (BETA) Read and manipulate Compute Engine interconnect MACsec + configuration. + remote-locations (BETA) Read and manipulate Google Compute Engine interconnect remote locations. diff --git a/gcloud/beta/compute/interconnects/macsec/add-key b/gcloud/beta/compute/interconnects/macsec/add-key new file mode 100644 index 000000000..7f21f1250 --- /dev/null +++ b/gcloud/beta/compute/interconnects/macsec/add-key @@ -0,0 +1,53 @@ +NAME + gcloud beta compute interconnects macsec add-key - add pre-shared key to a + Compute Engine interconnect MACsec configuration + +SYNOPSIS + gcloud beta compute interconnects macsec add-key NAME --key-name=KEY_NAME + [--start-time=START_TIME] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) gcloud beta compute interconnects macsec add-key is used to add a + pre-shared key to MACsec configuration of interconnect. + + For an example, refer to the EXAMPLES section below. + +EXAMPLES + To add a pre-shared key to MACsec configuration, run: + + $ gcloud beta compute interconnects macsec add-key \ + example-interconnect --key-name=default-key \ + --start-time=2021-02-01T12:12:12Z + +POSITIONAL ARGUMENTS + NAME + Name of the interconnect to update. + +REQUIRED FLAGS + --key-name=KEY_NAME + A name of pre-shared key being added to MACsec configuration of the + interconnect. The name must be 1-63 characters long, and comply with + RFC1035. + +OPTIONAL FLAGS + --start-time=START_TIME + A RFC3339 timestamp on or after which the key is valid. startTime can + be in the future. If the keychain has a single key, --start-time can be + omitted. If the keychain has multiple keys, --start-time is mandatory + for each key. The start times of two consecutive keys must be at least + 6 hours apart. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha compute interconnects macsec add-key + diff --git a/gcloud/beta/compute/interconnects/macsec/get-config b/gcloud/beta/compute/interconnects/macsec/get-config new file mode 100644 index 000000000..305f691ae --- /dev/null +++ b/gcloud/beta/compute/interconnects/macsec/get-config @@ -0,0 +1,40 @@ +NAME + gcloud beta compute interconnects macsec get-config - get MACsec + configuration of a Compute Engine interconnect + +SYNOPSIS + gcloud beta compute interconnects macsec get-config NAME + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) gcloud beta compute interconnects macsec get-config displays all + MACsec configuration data associated with Compute Engine interconnect in a + project. + + For an example, refer to the EXAMPLES section below. + +EXAMPLES + To displays all MACsec configuration data associated with Compute Engine + interconnect in a project, run: + + $ gcloud beta compute interconnects macsec get-config \ + example-interconnect + +POSITIONAL ARGUMENTS + NAME + Name of the interconnect to describe. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha compute interconnects macsec get-config + diff --git a/gcloud/beta/compute/interconnects/macsec/help b/gcloud/beta/compute/interconnects/macsec/help new file mode 100644 index 000000000..220fc277e --- /dev/null +++ b/gcloud/beta/compute/interconnects/macsec/help @@ -0,0 +1,43 @@ +NAME + gcloud beta compute interconnects macsec - read and manipulate Compute + Engine interconnect MACsec configuration + +SYNOPSIS + gcloud beta compute interconnects macsec COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Read and manipulate Compute Engine interconnect MACsec + configuration. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + add-key + (BETA) Add pre-shared key to a Compute Engine interconnect MACsec + configuration. + + get-config + (BETA) Get MACsec configuration of a Compute Engine interconnect. + + remove-key + (BETA) Remove pre-shared key from a Compute Engine interconnect MACsec + configuration. + + update + (BETA) Update a Compute Engine interconnect MACsec configuration. + + update-key + (BETA) Update pre-shared key in a Compute Engine interconnect MACsec + configuration. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha compute interconnects macsec + diff --git a/gcloud/beta/compute/interconnects/macsec/remove-key b/gcloud/beta/compute/interconnects/macsec/remove-key new file mode 100644 index 000000000..84129be94 --- /dev/null +++ b/gcloud/beta/compute/interconnects/macsec/remove-key @@ -0,0 +1,43 @@ +NAME + gcloud beta compute interconnects macsec remove-key - remove pre-shared key + from a Compute Engine interconnect MACsec configuration + +SYNOPSIS + gcloud beta compute interconnects macsec remove-key NAME + --key-name=KEY_NAME [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) gcloud beta compute interconnects macsec remove-key is used to + remove pre-shared key from MACsec configuration of interconnect. + + For an example, refer to the EXAMPLES section below. + +EXAMPLES + To remove a pre-shared key from MACsec configuration, run: + + $ gcloud beta compute interconnects macsec remove-key \ + example-interconnect --key-name=default-key + +POSITIONAL ARGUMENTS + NAME + Name of the interconnect to update. + +REQUIRED FLAGS + --key-name=KEY_NAME + The name of pre-shared key being removed from MACsec configuration of + the interconnect. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha compute interconnects macsec remove-key + diff --git a/gcloud/beta/compute/interconnects/macsec/update b/gcloud/beta/compute/interconnects/macsec/update new file mode 100644 index 000000000..9c5247092 --- /dev/null +++ b/gcloud/beta/compute/interconnects/macsec/update @@ -0,0 +1,53 @@ +NAME + gcloud beta compute interconnects macsec update - update a Compute Engine + interconnect MACsec configuration + +SYNOPSIS + gcloud beta compute interconnects macsec update NAME [--enabled] + [--fail-open] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) gcloud beta compute interconnects macsec update is used to update + MACsec configuration of interconnect. An interconnect represents a single + specific connection between Google and the customer. + + For an example, refer to the EXAMPLES section below. + +EXAMPLES + To enable MACsec on an interconnect, run: + + $ gcloud beta compute interconnects macsec update \ + example-interconnect --enabled + +POSITIONAL ARGUMENTS + NAME + Name of the interconnect to update. + +FLAGS + --enabled + Enable or disable MACsec on this Interconnect. MACsec enablement will + fail if the MACsec configuration is not specified. Use --no-enabled to + disable it. + + --fail-open + If enabled, the Interconnect will be configured with a should-secure + MACsec security policy, that allows the Google router to fallback to + cleartext traffic if the MKA session cannot be established. By default, + the Interconnect will be configured with a must-secure security policy + that drops all traffic if the MKA session cannot be established with + your router. Use --no-fail-open to disable it. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha compute interconnects macsec update + diff --git a/gcloud/beta/compute/interconnects/macsec/update-key b/gcloud/beta/compute/interconnects/macsec/update-key new file mode 100644 index 000000000..9a4e0a941 --- /dev/null +++ b/gcloud/beta/compute/interconnects/macsec/update-key @@ -0,0 +1,53 @@ +NAME + gcloud beta compute interconnects macsec update-key - update pre-shared key + in a Compute Engine interconnect MACsec configuration + +SYNOPSIS + gcloud beta compute interconnects macsec update-key NAME + --key-name=KEY_NAME [--start-time=START_TIME] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) gcloud beta compute interconnects macsec update-key is used to + update a pre-shared key in MACsec configuration of interconnect. + + For an example, refer to the EXAMPLES section below. + +EXAMPLES + To update a pre-shared key in MACsec configuration, run: + + $ gcloud beta compute interconnects macsec update-key \ + example-interconnect --key-name=default-key \ + --start-time=2021-02-01T12:12:12Z + +POSITIONAL ARGUMENTS + NAME + Name of the interconnect to update. + +REQUIRED FLAGS + --key-name=KEY_NAME + A name of pre-shared key being added to MACsec configuration of the + interconnect. The name must be 1-63 characters long, and comply with + RFC1035. + +OPTIONAL FLAGS + --start-time=START_TIME + A RFC3339 timestamp on or after which the key is valid. startTime can + be in the future. If the keychain has a single key, --start-time can be + omitted. If the keychain has multiple keys, --start-time is mandatory + for each key. The start times of two consecutive keys must be at least + 6 hours apart. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha compute interconnects macsec update-key + diff --git a/gcloud/beta/compute/os-config/guest-policies/create b/gcloud/beta/compute/os-config/guest-policies/create index ef94a80f4..620830489 100644 --- a/gcloud/beta/compute/os-config/guest-policies/create +++ b/gcloud/beta/compute/os-config/guest-policies/create @@ -35,8 +35,5 @@ 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: - - $ gcloud alpha compute os-config guest-policies create + This command is currently in beta and might change without notice. diff --git a/gcloud/beta/compute/os-config/guest-policies/delete b/gcloud/beta/compute/os-config/guest-policies/delete index ec933bece..cf83e1afb 100644 --- a/gcloud/beta/compute/os-config/guest-policies/delete +++ b/gcloud/beta/compute/os-config/guest-policies/delete @@ -24,8 +24,5 @@ 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: - - $ gcloud alpha compute os-config guest-policies delete + This command is currently in beta and might change without notice. diff --git a/gcloud/beta/compute/os-config/guest-policies/describe b/gcloud/beta/compute/os-config/guest-policies/describe index 869c795c8..86818b732 100644 --- a/gcloud/beta/compute/os-config/guest-policies/describe +++ b/gcloud/beta/compute/os-config/guest-policies/describe @@ -24,8 +24,5 @@ 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: - - $ gcloud alpha compute os-config guest-policies describe + This command is currently in beta and might change without notice. diff --git a/gcloud/beta/compute/os-config/guest-policies/help b/gcloud/beta/compute/os-config/guest-policies/help index c2525960a..ea8fdba23 100644 --- a/gcloud/beta/compute/os-config/guest-policies/help +++ b/gcloud/beta/compute/os-config/guest-policies/help @@ -35,8 +35,5 @@ COMMANDS (BETA) Update the specified guest policy for a project. NOTES - This command is currently in beta and might change without notice. This - variant is also available: - - $ gcloud alpha compute os-config guest-policies + This command is currently in beta and might change without notice. diff --git a/gcloud/beta/compute/os-config/guest-policies/list b/gcloud/beta/compute/os-config/guest-policies/list index 32b5911b6..19a161eec 100644 --- a/gcloud/beta/compute/os-config/guest-policies/list +++ b/gcloud/beta/compute/os-config/guest-policies/list @@ -53,8 +53,5 @@ 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: - - $ gcloud alpha compute os-config guest-policies list + This command is currently in beta and might change without notice. diff --git a/gcloud/beta/compute/os-config/guest-policies/lookup b/gcloud/beta/compute/os-config/guest-policies/lookup index 14afaad1e..a7a438ada 100644 --- a/gcloud/beta/compute/os-config/guest-policies/lookup +++ b/gcloud/beta/compute/os-config/guest-policies/lookup @@ -53,8 +53,5 @@ 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: - - $ gcloud alpha compute os-config guest-policies lookup + This command is currently in beta and might change without notice. diff --git a/gcloud/beta/compute/os-config/guest-policies/update b/gcloud/beta/compute/os-config/guest-policies/update index 9c7704444..a79f268b3 100644 --- a/gcloud/beta/compute/os-config/guest-policies/update +++ b/gcloud/beta/compute/os-config/guest-policies/update @@ -37,8 +37,5 @@ 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: - - $ gcloud alpha compute os-config guest-policies update + This command is currently in beta and might change without notice. diff --git a/gcloud/beta/compute/os-config/patch-deployments/create b/gcloud/beta/compute/os-config/patch-deployments/create index 97c749f18..94b9481f4 100644 --- a/gcloud/beta/compute/os-config/patch-deployments/create +++ b/gcloud/beta/compute/os-config/patch-deployments/create @@ -44,10 +44,8 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. NOTES - This command is currently in beta and might change without notice. These - variants are also available: + This command is currently in beta and might change without notice. This + variant is also available: $ gcloud compute os-config patch-deployments create - $ gcloud alpha compute os-config patch-deployments create - diff --git a/gcloud/beta/compute/os-config/patch-deployments/delete b/gcloud/beta/compute/os-config/patch-deployments/delete index 0b562a7b0..800eb693b 100644 --- a/gcloud/beta/compute/os-config/patch-deployments/delete +++ b/gcloud/beta/compute/os-config/patch-deployments/delete @@ -45,10 +45,8 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. NOTES - This command is currently in beta and might change without notice. These - variants are also available: + This command is currently in beta and might change without notice. This + variant is also available: $ gcloud compute os-config patch-deployments delete - $ gcloud alpha compute os-config patch-deployments delete - diff --git a/gcloud/beta/compute/os-config/patch-deployments/describe b/gcloud/beta/compute/os-config/patch-deployments/describe index e160e793a..8ccfd99ef 100644 --- a/gcloud/beta/compute/os-config/patch-deployments/describe +++ b/gcloud/beta/compute/os-config/patch-deployments/describe @@ -45,10 +45,8 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. NOTES - This command is currently in beta and might change without notice. These - variants are also available: + This command is currently in beta and might change without notice. This + variant is also available: $ gcloud compute os-config patch-deployments describe - $ gcloud alpha compute os-config patch-deployments describe - diff --git a/gcloud/beta/compute/os-config/patch-deployments/help b/gcloud/beta/compute/os-config/patch-deployments/help index 6ef219cf8..38ca344c1 100644 --- a/gcloud/beta/compute/os-config/patch-deployments/help +++ b/gcloud/beta/compute/os-config/patch-deployments/help @@ -39,10 +39,8 @@ COMMANDS (BETA) Update a patch deployment in a project. NOTES - This command is currently in beta and might change without notice. These - variants are also available: + This command is currently in beta and might change without notice. This + variant is also available: $ gcloud compute os-config patch-deployments - $ gcloud alpha compute os-config patch-deployments - diff --git a/gcloud/beta/compute/os-config/patch-deployments/list b/gcloud/beta/compute/os-config/patch-deployments/list index 667cd1142..d776b305b 100644 --- a/gcloud/beta/compute/os-config/patch-deployments/list +++ b/gcloud/beta/compute/os-config/patch-deployments/list @@ -56,10 +56,8 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. NOTES - This command is currently in beta and might change without notice. These - variants are also available: + This command is currently in beta and might change without notice. This + variant is also available: $ gcloud compute os-config patch-deployments list - $ gcloud alpha compute os-config patch-deployments list - diff --git a/gcloud/beta/compute/os-config/patch-deployments/pause b/gcloud/beta/compute/os-config/patch-deployments/pause index 127ec9848..c72757c34 100644 --- a/gcloud/beta/compute/os-config/patch-deployments/pause +++ b/gcloud/beta/compute/os-config/patch-deployments/pause @@ -45,10 +45,8 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. NOTES - This command is currently in beta and might change without notice. These - variants are also available: + This command is currently in beta and might change without notice. This + variant is also available: $ gcloud compute os-config patch-deployments pause - $ gcloud alpha compute os-config patch-deployments pause - diff --git a/gcloud/beta/compute/os-config/patch-deployments/resume b/gcloud/beta/compute/os-config/patch-deployments/resume index 3fb371614..1b4bdb87c 100644 --- a/gcloud/beta/compute/os-config/patch-deployments/resume +++ b/gcloud/beta/compute/os-config/patch-deployments/resume @@ -45,10 +45,8 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. NOTES - This command is currently in beta and might change without notice. These - variants are also available: + This command is currently in beta and might change without notice. This + variant is also available: $ gcloud compute os-config patch-deployments resume - $ gcloud alpha compute os-config patch-deployments resume - diff --git a/gcloud/beta/compute/os-config/patch-deployments/update b/gcloud/beta/compute/os-config/patch-deployments/update index b02414111..98c287f7c 100644 --- a/gcloud/beta/compute/os-config/patch-deployments/update +++ b/gcloud/beta/compute/os-config/patch-deployments/update @@ -39,10 +39,8 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. NOTES - This command is currently in beta and might change without notice. These - variants are also available: + This command is currently in beta and might change without notice. This + variant is also available: $ gcloud compute os-config patch-deployments update - $ gcloud alpha compute os-config patch-deployments update - diff --git a/gcloud/beta/compute/os-config/patch-jobs/cancel b/gcloud/beta/compute/os-config/patch-jobs/cancel index a02b4a542..ead585e88 100644 --- a/gcloud/beta/compute/os-config/patch-jobs/cancel +++ b/gcloud/beta/compute/os-config/patch-jobs/cancel @@ -39,10 +39,8 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. NOTES - This command is currently in beta and might change without notice. These - variants are also available: + This command is currently in beta and might change without notice. This + variant is also available: $ gcloud compute os-config patch-jobs cancel - $ gcloud alpha compute os-config patch-jobs cancel - diff --git a/gcloud/beta/compute/os-config/patch-jobs/describe b/gcloud/beta/compute/os-config/patch-jobs/describe index 8ecba35be..1364f779a 100644 --- a/gcloud/beta/compute/os-config/patch-jobs/describe +++ b/gcloud/beta/compute/os-config/patch-jobs/describe @@ -39,10 +39,8 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. NOTES - This command is currently in beta and might change without notice. These - variants are also available: + This command is currently in beta and might change without notice. This + variant is also available: $ gcloud compute os-config patch-jobs describe - $ gcloud alpha compute os-config patch-jobs describe - diff --git a/gcloud/beta/compute/os-config/patch-jobs/execute b/gcloud/beta/compute/os-config/patch-jobs/execute index 630562f95..f3e3c2fad 100644 --- a/gcloud/beta/compute/os-config/patch-jobs/execute +++ b/gcloud/beta/compute/os-config/patch-jobs/execute @@ -388,10 +388,8 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. NOTES - This command is currently in beta and might change without notice. These - variants are also available: + This command is currently in beta and might change without notice. This + variant is also available: $ gcloud compute os-config patch-jobs execute - $ gcloud alpha compute os-config patch-jobs execute - diff --git a/gcloud/beta/compute/os-config/patch-jobs/help b/gcloud/beta/compute/os-config/patch-jobs/help index 515c12e11..a4613f238 100644 --- a/gcloud/beta/compute/os-config/patch-jobs/help +++ b/gcloud/beta/compute/os-config/patch-jobs/help @@ -32,10 +32,8 @@ COMMANDS (BETA) List the instance details for an OS patch job. NOTES - This command is currently in beta and might change without notice. These - variants are also available: + This command is currently in beta and might change without notice. This + variant is also available: $ gcloud compute os-config patch-jobs - $ gcloud alpha compute os-config patch-jobs - diff --git a/gcloud/beta/compute/os-config/patch-jobs/list b/gcloud/beta/compute/os-config/patch-jobs/list index 0650127cc..eeccf7023 100644 --- a/gcloud/beta/compute/os-config/patch-jobs/list +++ b/gcloud/beta/compute/os-config/patch-jobs/list @@ -53,10 +53,8 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. NOTES - This command is currently in beta and might change without notice. These - variants are also available: + This command is currently in beta and might change without notice. This + variant is also available: $ gcloud compute os-config patch-jobs list - $ gcloud alpha compute os-config patch-jobs list - diff --git a/gcloud/beta/compute/os-config/patch-jobs/list-instance-details b/gcloud/beta/compute/os-config/patch-jobs/list-instance-details index a4507b769..a34064191 100644 --- a/gcloud/beta/compute/os-config/patch-jobs/list-instance-details +++ b/gcloud/beta/compute/os-config/patch-jobs/list-instance-details @@ -66,10 +66,8 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. NOTES - This command is currently in beta and might change without notice. These - variants are also available: + This command is currently in beta and might change without notice. This + variant is also available: $ gcloud compute os-config patch-jobs list-instance-details - $ gcloud alpha compute os-config patch-jobs list-instance-details - diff --git a/gcloud/beta/compute/target-http-proxies/create b/gcloud/beta/compute/target-http-proxies/create index 04a5965fe..420658d28 100644 --- a/gcloud/beta/compute/target-http-proxies/create +++ b/gcloud/beta/compute/target-http-proxies/create @@ -53,8 +53,8 @@ OPTIONAL FLAGS Represents the maximum amount of time that a TCP connection can be idle between the (downstream) client and the target HTTP proxy. If an HTTP keepalive timeout is not specified, the default value is 610 seconds. - For global external HTTP(S) load balancer, the minimum allowed value is - 5 seconds and the maximum allowed value is 1200 seconds. + For global external Application load balancer, the minimum allowed + value is 5 seconds and the maximum allowed value is 1200 seconds. At most one of these can be specified: diff --git a/gcloud/beta/compute/target-http-proxies/update b/gcloud/beta/compute/target-http-proxies/update index 18300a6b8..192e7cb98 100644 --- a/gcloud/beta/compute/target-http-proxies/update +++ b/gcloud/beta/compute/target-http-proxies/update @@ -50,7 +50,7 @@ OPTIONAL FLAGS Represents the maximum amount of time that a TCP connection can be idle between the (downstream) client and the target HTTP proxy. If an HTTP keepalive timeout is not specified, the default value is 610 - seconds. For global external HTTP(S) load balancer, the minimum + seconds. For global external Application load balancer, the minimum allowed value is 5 seconds and the maximum allowed value is 1200 seconds. diff --git a/gcloud/beta/compute/target-https-proxies/create b/gcloud/beta/compute/target-https-proxies/create index a471b7969..b309f625b 100644 --- a/gcloud/beta/compute/target-https-proxies/create +++ b/gcloud/beta/compute/target-https-proxies/create @@ -83,8 +83,8 @@ OPTIONAL FLAGS Represents the maximum amount of time that a TCP connection can be idle between the (downstream) client and the target HTTP proxy. If an HTTP keepalive timeout is not specified, the default value is 610 seconds. - For global external HTTP(S) load balancer, the minimum allowed value is - 5 seconds and the maximum allowed value is 1200 seconds. + For global external Application load balancer, the minimum allowed + value is 5 seconds and the maximum allowed value is 1200 seconds. --quic-override=QUIC_OVERRIDE; default="NONE" Controls whether load balancer may negotiate QUIC with clients. QUIC is diff --git a/gcloud/beta/compute/target-https-proxies/update b/gcloud/beta/compute/target-https-proxies/update index 1967204d0..d7d1d71e0 100644 --- a/gcloud/beta/compute/target-https-proxies/update +++ b/gcloud/beta/compute/target-https-proxies/update @@ -171,7 +171,7 @@ FLAGS Represents the maximum amount of time that a TCP connection can be idle between the (downstream) client and the target HTTP proxy. If an HTTP keepalive timeout is not specified, the default value is 610 - seconds. For global external HTTP(S) load balancer, the minimum + seconds. For global external Application load balancer, the minimum allowed value is 5 seconds and the maximum allowed value is 1200 seconds. diff --git a/gcloud/beta/config/get b/gcloud/beta/config/get index 753b538b4..2d775bad4 100644 --- a/gcloud/beta/config/get +++ b/gcloud/beta/config/get @@ -370,6 +370,10 @@ AVAILABLE PROPERTIES Overrides API endpoint for gcloud events command group. Defaults to https://events.googleapis.com/ + faultinjectiontesting + Overrides API endpoint for gcloud fault-injection command group. + Defaults to https://faultinjectiontesting.googleapis.com/ + file Overrides API endpoint for gcloud filestore command group. Defaults to https://file.googleapis.com/ diff --git a/gcloud/beta/config/help b/gcloud/beta/config/help index fd825e4fc..6bedeb88e 100644 --- a/gcloud/beta/config/help +++ b/gcloud/beta/config/help @@ -402,6 +402,10 @@ AVAILABLE PROPERTIES Overrides API endpoint for gcloud events command group. Defaults to https://events.googleapis.com/ + faultinjectiontesting + Overrides API endpoint for gcloud fault-injection command group. + Defaults to https://faultinjectiontesting.googleapis.com/ + file Overrides API endpoint for gcloud filestore command group. Defaults to https://file.googleapis.com/ diff --git a/gcloud/beta/config/list b/gcloud/beta/config/list index 89b6bef49..7965f512e 100644 --- a/gcloud/beta/config/list +++ b/gcloud/beta/config/list @@ -414,6 +414,10 @@ AVAILABLE PROPERTIES Overrides API endpoint for gcloud events command group. Defaults to https://events.googleapis.com/ + faultinjectiontesting + Overrides API endpoint for gcloud fault-injection command group. + Defaults to https://faultinjectiontesting.googleapis.com/ + file Overrides API endpoint for gcloud filestore command group. Defaults to https://file.googleapis.com/ diff --git a/gcloud/beta/config/set b/gcloud/beta/config/set index 04611d6d4..6ff209fab 100644 --- a/gcloud/beta/config/set +++ b/gcloud/beta/config/set @@ -417,6 +417,10 @@ AVAILABLE PROPERTIES Overrides API endpoint for gcloud events command group. Defaults to https://events.googleapis.com/ + faultinjectiontesting + Overrides API endpoint for gcloud fault-injection command group. + Defaults to https://faultinjectiontesting.googleapis.com/ + file Overrides API endpoint for gcloud filestore command group. Defaults to https://file.googleapis.com/ diff --git a/gcloud/beta/config/unset b/gcloud/beta/config/unset index 2ad34ab94..a374b04fb 100644 --- a/gcloud/beta/config/unset +++ b/gcloud/beta/config/unset @@ -378,6 +378,10 @@ AVAILABLE PROPERTIES Overrides API endpoint for gcloud events command group. Defaults to https://events.googleapis.com/ + faultinjectiontesting + Overrides API endpoint for gcloud fault-injection command group. + Defaults to https://faultinjectiontesting.googleapis.com/ + file Overrides API endpoint for gcloud filestore command group. Defaults to https://file.googleapis.com/ diff --git a/gcloud/beta/container/clusters/create b/gcloud/beta/container/clusters/create index 0732a5353..6125fcd42 100644 --- a/gcloud/beta/container/clusters/create +++ b/gcloud/beta/container/clusters/create @@ -19,6 +19,7 @@ SYNOPSIS [--cluster-version=CLUSTER_VERSION] [--create-subnetwork=[KEY=VALUE,...]] [--database-encryption-key=DATABASE_ENCRYPTION_KEY] + [--dataplane-v2-observability-mode=DATAPLANE_V2_OBSERVABILITY_MODE] [--default-max-pods-per-node=DEFAULT_MAX_PODS_PER_NODE] [--disable-default-snat] [--disable-pod-cidr-overprovision] [--disk-size=DISK_SIZE] [--disk-type=DISK_TYPE] [--enable-autorepair] @@ -28,6 +29,7 @@ SYNOPSIS [--enable-dataplane-v2] [--enable-fleet] [--enable-fqdn-network-policy] [--enable-gke-oidc] [--enable-google-cloud-access] [--enable-gvnic] [--enable-identity-service] [--enable-image-streaming] + [--enable-insecure-kubelet-readonly-port] [--enable-intra-node-visibility] [--enable-ip-alias] [--enable-kubernetes-alpha] [--enable-kubernetes-unstable-apis=API,[API,...]] @@ -67,11 +69,12 @@ SYNOPSIS [--workload-metadata=WORKLOAD_METADATA] [--workload-pool=WORKLOAD_POOL] [--workload-vulnerability-scanning=WORKLOAD_VULNERABILITY_SCANNING] [--additional-zones=ZONE,[ZONE,...] | --node-locations=ZONE,[ZONE,...]] - [--binauthz-policy=BINAUTHZ_POLICY + [--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] + [--disable-dataplane-v2-metrics | --enable-dataplane-v2-metrics] [[--enable-autoprovisioning : --autoprovisioning-config-file=AUTOPROVISIONING_CONFIG_FILE | [--max-cpu=MAX_CPU --max-memory=MAX_MEMORY @@ -321,6 +324,35 @@ FLAGS For more information, see https://cloud.google.com/kubernetes-engine/docs/how-to/encrypting-secrets. + --dataplane-v2-observability-mode=DATAPLANE_V2_OBSERVABILITY_MODE + Select Advanced Datapath Observability mode for the cluster. Defaults + to DISABLED. + + Advanced Datapath Observability allows for a real-time view into + pod-to-pod traffic within your cluster. + + Examples: + + $ gcloud beta container clusters create \ + --dataplane-v2-observability-mode=DISABLED + + $ gcloud beta container clusters create \ + --dataplane-v2-observability-mode=INTERNAL_VPC_LB + + $ gcloud beta container clusters create \ + --dataplane-v2-observability-mode=EXTERNAL_LB + + DATAPLANE_V2_OBSERVABILITY_MODE must be one of: + + DISABLED + Disables Advanced Datapath Observability. + EXTERNAL_LB + Makes Advanced Datapath Observability available to the external + network. + INTERNAL_VPC_LB + Makes Advanced Datapath Observability available from the VPC + network. + --default-max-pods-per-node=DEFAULT_MAX_PODS_PER_NODE The default max number of pods per node for node pools in the cluster. @@ -477,6 +509,12 @@ FLAGS --enable-image-streaming Specifies whether to enable image streaming on cluster. + --enable-insecure-kubelet-readonly-port + Enables the Kubelet's insecure Read Only Port. + + To disable in an existing cluster, explicitly set flag to + --no-enable-insecure-kubelet-readonly-port. + --enable-intra-node-visibility Enable Intra-node visibility for this cluster. @@ -1210,7 +1248,7 @@ FLAGS Flags for Binary Authorization: - --binauthz-policy=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}. @@ -1259,6 +1297,14 @@ FLAGS vpc Configures the Cloud DNS zone to be private to the VPC Network. + At most one of these can be specified: + + --disable-dataplane-v2-metrics + Stops exposing advanced datapath flow metrics on node port. + + --enable-dataplane-v2-metrics + Exposes advanced datapath flow metrics on node port. + Node autoprovisioning --enable-autoprovisioning diff --git a/gcloud/beta/container/clusters/create-auto b/gcloud/beta/container/clusters/create-auto index 5b739243a..662b16a70 100644 --- a/gcloud/beta/container/clusters/create-auto +++ b/gcloud/beta/container/clusters/create-auto @@ -10,8 +10,10 @@ SYNOPSIS [--cluster-secondary-range-name=NAME] [--cluster-version=CLUSTER_VERSION] [--create-subnetwork=[KEY=VALUE,...]] - [--database-encryption-key=DATABASE_ENCRYPTION_KEY] [--enable-fleet] - [--enable-google-cloud-access] + [--database-encryption-key=DATABASE_ENCRYPTION_KEY] + [--dataplane-v2-observability-mode=DATAPLANE_V2_OBSERVABILITY_MODE] + [--enable-fleet] [--enable-google-cloud-access] + [--enable-insecure-kubelet-readonly-port] [--enable-kubernetes-unstable-apis=API,[API,...]] [--enable-master-global-access] [--fleet-project=PROJECT_ID_OR_NUMBER] [--logging=[COMPONENT,...]] [--monitoring=[COMPONENT,...]] @@ -22,7 +24,7 @@ SYNOPSIS [--workload-policies=WORKLOAD_POLICIES] [--workload-vulnerability-scanning=WORKLOAD_VULNERABILITY_SCANNING] [--binauthz-evaluation-mode=BINAUTHZ_EVALUATION_MODE - --binauthz-policy=BINAUTHZ_POLICY] + --binauthz-policy-bindings=[name=BINAUTHZ_POLICY,...]] [--enable-master-authorized-networks --master-authorized-networks=NETWORK,[NETWORK,...]] [--enable-private-endpoint @@ -155,6 +157,35 @@ FLAGS For more information, see https://cloud.google.com/kubernetes-engine/docs/how-to/encrypting-secrets. + --dataplane-v2-observability-mode=DATAPLANE_V2_OBSERVABILITY_MODE + Select Advanced Datapath Observability mode for the cluster. Defaults + to DISABLED. + + Advanced Datapath Observability allows for a real-time view into + pod-to-pod traffic within your cluster. + + Examples: + + $ gcloud beta container clusters create-auto \ + --dataplane-v2-observability-mode=DISABLED + + $ gcloud beta container clusters create-auto \ + --dataplane-v2-observability-mode=INTERNAL_VPC_LB + + $ gcloud beta container clusters create-auto \ + --dataplane-v2-observability-mode=EXTERNAL_LB + + DATAPLANE_V2_OBSERVABILITY_MODE must be one of: + + DISABLED + Disables Advanced Datapath Observability. + EXTERNAL_LB + Makes Advanced Datapath Observability available to the external + network. + INTERNAL_VPC_LB + Makes Advanced Datapath Observability available from the VPC + network. + --enable-fleet Set cluster project as the fleet host project. This will register the cluster to the same project. To register the cluster to a fleet in a @@ -166,6 +197,12 @@ FLAGS Google Cloud can reach the public control plane endpoint of your cluster. + --enable-insecure-kubelet-readonly-port + Enables the Kubelet's insecure Read Only Port. + + To disable in an existing cluster, explicitly set flag to + --no-enable-insecure-kubelet-readonly-port. + --enable-kubernetes-unstable-apis=API,[API,...] Enable Kubernetes beta API features on this cluster. Beta APIs are not expected to be production ready and should be avoided in @@ -342,7 +379,7 @@ FLAGS POLICY_BINDINGS_AND_PROJECT_SINGLETON_POLICY_ENFORCE, PROJECT_SINGLETON_POLICY_ENFORCE. - --binauthz-policy=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/clusters/update b/gcloud/beta/container/clusters/update index 94f5e37c3..e30351933 100644 --- a/gcloud/beta/container/clusters/update +++ b/gcloud/beta/container/clusters/update @@ -8,12 +8,14 @@ SYNOPSIS | --autoscaling-profile=AUTOSCALING_PROFILE | --clear-fleet-project | --complete-credential-rotation | --complete-ip-rotation | --database-encryption-key=DATABASE_ENCRYPTION_KEY + | --dataplane-v2-observability-mode=DATAPLANE_V2_OBSERVABILITY_MODE | --disable-database-encryption | --disable-default-snat | --disable-workload-identity | --enable-autoscaling | --enable-cost-allocation | --enable-fleet | --enable-fqdn-network-policy | --enable-gke-oidc | --enable-google-cloud-access | --enable-identity-service - | --enable-image-streaming | --enable-intra-node-visibility + | --enable-image-streaming | --enable-insecure-kubelet-readonly-port + | --enable-intra-node-visibility | --enable-kubernetes-unstable-apis=API,[API,...] | --enable-l4-ilb-subsetting | --enable-legacy-authorization | --enable-logging-monitoring-system-only @@ -41,7 +43,7 @@ SYNOPSIS | --additional-pod-ipv4-ranges=NAME,[NAME,...] --remove-additional-pod-ipv4-ranges=NAME,[NAME,...] | --additional-zones=[ZONE,...] | --node-locations=ZONE,[ZONE,...] - | --binauthz-policy=BINAUTHZ_POLICY + | --binauthz-policy-bindings=[name=BINAUTHZ_POLICY,...] --binauthz-evaluation-mode=BINAUTHZ_EVALUATION_MODE | --enable-binauthz | --clear-maintenance-window | --remove-maintenance-exclusion=NAME @@ -57,7 +59,9 @@ SYNOPSIS --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 | [--enable-autoprovisioning + --cluster-dns-scope=CLUSTER_DNS_SCOPE + | --disable-dataplane-v2-metrics | --enable-dataplane-v2-metrics + | [--enable-autoprovisioning : --autoprovisioning-config-file=AUTOPROVISIONING_CONFIG_FILE | --autoprovisioning-image-type=AUTOPROVISIONING_IMAGE_TYPE --autoprovisioning-locations=ZONE,[ZONE,...] @@ -163,6 +167,35 @@ REQUIRED FLAGS For more information, see https://cloud.google.com/kubernetes-engine/docs/how-to/encrypting-secrets. + --dataplane-v2-observability-mode=DATAPLANE_V2_OBSERVABILITY_MODE + Select Advanced Datapath Observability mode for the cluster. Defaults + to DISABLED. + + Advanced Datapath Observability allows for a real-time view into + pod-to-pod traffic within your cluster. + + Examples: + + $ gcloud beta container clusters update \ + --dataplane-v2-observability-mode=DISABLED + + $ gcloud beta container clusters update \ + --dataplane-v2-observability-mode=INTERNAL_VPC_LB + + $ gcloud beta container clusters update \ + --dataplane-v2-observability-mode=EXTERNAL_LB + + DATAPLANE_V2_OBSERVABILITY_MODE must be one of: + + DISABLED + Disables Advanced Datapath Observability. + EXTERNAL_LB + Makes Advanced Datapath Observability available to the external + network. + INTERNAL_VPC_LB + Makes Advanced Datapath Observability available from the VPC + network. + --disable-database-encryption Disable database encryption. @@ -256,6 +289,12 @@ REQUIRED FLAGS --enable-image-streaming Specifies whether to enable image streaming on cluster. + --enable-insecure-kubelet-readonly-port + Enables the Kubelet's insecure Read Only Port. + + To disable in an existing cluster, explicitly set flag to + --no-enable-insecure-kubelet-readonly-port. + --enable-intra-node-visibility Enable Intra-node visibility for this cluster. @@ -690,7 +729,7 @@ REQUIRED FLAGS Flags for Binary Authorization: - --binauthz-policy=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}. @@ -875,6 +914,14 @@ REQUIRED FLAGS vpc Configures the Cloud DNS zone to be private to the VPC Network. + At most one of these can be specified: + + --disable-dataplane-v2-metrics + Stops exposing advanced datapath flow metrics on node port. + + --enable-dataplane-v2-metrics + Exposes advanced datapath flow metrics on node port. + Node autoprovisioning --enable-autoprovisioning diff --git a/gcloud/beta/container/fleet/fleetobservability/describe b/gcloud/beta/container/fleet/fleetobservability/describe new file mode 100644 index 000000000..dba2e68ef --- /dev/null +++ b/gcloud/beta/container/fleet/fleetobservability/describe @@ -0,0 +1,33 @@ +NAME + gcloud beta container fleet fleetobservability describe - describes the + status of the Fleet Observability Feature resource + +SYNOPSIS + gcloud beta container fleet fleetobservability describe + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) This command gets the detailed status of the Fleet Observability + Feature in a fleet. + +EXAMPLES + To describe the Fleet Observability Feature, run: + + $ gcloud beta container fleet fleetobservability describe + +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 fleetobservability describe + + $ gcloud alpha container fleet fleetobservability describe + diff --git a/gcloud/beta/container/fleet/fleetobservability/disable b/gcloud/beta/container/fleet/fleetobservability/disable new file mode 100644 index 000000000..a2335f0e2 --- /dev/null +++ b/gcloud/beta/container/fleet/fleetobservability/disable @@ -0,0 +1,37 @@ +NAME + gcloud beta container fleet fleetobservability disable - disables the Fleet + Observability Feature + +SYNOPSIS + gcloud beta container fleet fleetobservability disable [--force] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) This command disables Fleet Observability Feature in a fleet. + +EXAMPLES + To disable the Fleet Observability Feature, run: + + $ gcloud beta container fleet fleetobservability disable + +FLAGS + --force + Disable this feature, even if it is currently in use. Force disablement + may result in unexpected behavior. + +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 fleetobservability disable + + $ gcloud alpha container fleet fleetobservability disable + diff --git a/gcloud/beta/container/fleet/fleetobservability/enable b/gcloud/beta/container/fleet/fleetobservability/enable new file mode 100644 index 000000000..0f225d52d --- /dev/null +++ b/gcloud/beta/container/fleet/fleetobservability/enable @@ -0,0 +1,32 @@ +NAME + gcloud beta container fleet fleetobservability enable - enables the Fleet + Observability Feature + +SYNOPSIS + gcloud beta container fleet fleetobservability enable + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) This command enables Fleet Observability Feature in a fleet. + +EXAMPLES + To enable the Fleet Observability Feature, run: + + $ gcloud beta container fleet fleetobservability enable + +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 fleetobservability enable + + $ gcloud alpha container fleet fleetobservability enable + diff --git a/gcloud/beta/container/fleet/fleetobservability/help b/gcloud/beta/container/fleet/fleetobservability/help new file mode 100644 index 000000000..b27339b66 --- /dev/null +++ b/gcloud/beta/container/fleet/fleetobservability/help @@ -0,0 +1,40 @@ +NAME + gcloud beta container fleet fleetobservability - manage Fleet Observability + Feature + +SYNOPSIS + gcloud beta container fleet fleetobservability COMMAND + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Manage Fleet Observability Feature. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + describe + (BETA) Describes the status of the Fleet Observability Feature + resource. + + disable + (BETA) Disables the Fleet Observability Feature. + + enable + (BETA) Enables the Fleet Observability Feature. + + update + (BETA) Updates the Fleet Observability Feature resource. + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud container fleet fleetobservability + + $ gcloud alpha container fleet fleetobservability + diff --git a/gcloud/beta/container/fleet/fleetobservability/update b/gcloud/beta/container/fleet/fleetobservability/update new file mode 100644 index 000000000..12a04c65b --- /dev/null +++ b/gcloud/beta/container/fleet/fleetobservability/update @@ -0,0 +1,60 @@ +NAME + gcloud beta container fleet fleetobservability update - updates the Fleet + Observability Feature resource + +SYNOPSIS + gcloud beta container fleet fleetobservability update + [--logging-config=LOGGING_CONFIG] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) This command updates the Fleet Observability Feature in a fleet. + +EXAMPLES + To describe the Fleet Observability Feature, run: + + $ gcloud beta container fleet fleetobservability update \ + --logging-config=LOGGING-CONFIG + +FLAGS + --logging-config=LOGGING_CONFIG + Path of the YAML(or JSON) file that contains the logging + configurations. + + The JSON file is formatted as follows, with camelCase field naming: + + { + "loggingConfig": { + "defaultConfig": { + "mode": "COPY" + }, + "fleetScopeLogsConfig": { + "mode": "MOVE" + } + } + } + + The YAML file is formatted as follows, with camelCase field naming: + + --- + loggingConfig: + defaultConfig: + mode: COPY + fleetScopeLogsConfig: + mode: MOVE + +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 fleetobservability update + + $ gcloud alpha container fleet fleetobservability update + diff --git a/gcloud/beta/container/fleet/help b/gcloud/beta/container/fleet/help index 1c53e7bc8..4f391f441 100644 --- a/gcloud/beta/container/fleet/help +++ b/gcloud/beta/container/fleet/help @@ -54,6 +54,9 @@ GROUPS features (BETA) Manage Hub Feature resources. + fleetobservability + (BETA) Manage Fleet Observability Feature. + identity-service (BETA) Manage Identity Service Feature. diff --git a/gcloud/beta/container/hub/fleetobservability/describe b/gcloud/beta/container/hub/fleetobservability/describe new file mode 100644 index 000000000..e76c37ff4 --- /dev/null +++ b/gcloud/beta/container/hub/fleetobservability/describe @@ -0,0 +1,33 @@ +NAME + gcloud beta container hub fleetobservability describe - describes the + status of the Fleet Observability Feature resource + +SYNOPSIS + gcloud beta container hub fleetobservability describe + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) This command gets the detailed status of the Fleet Observability + Feature in a fleet. + +EXAMPLES + To describe the Fleet Observability Feature, run: + + $ gcloud beta container hub fleetobservability describe + +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 fleetobservability describe + + $ gcloud alpha container hub fleetobservability describe + diff --git a/gcloud/beta/container/hub/fleetobservability/disable b/gcloud/beta/container/hub/fleetobservability/disable new file mode 100644 index 000000000..fc552e3a8 --- /dev/null +++ b/gcloud/beta/container/hub/fleetobservability/disable @@ -0,0 +1,37 @@ +NAME + gcloud beta container hub fleetobservability disable - disables the Fleet + Observability Feature + +SYNOPSIS + gcloud beta container hub fleetobservability disable [--force] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) This command disables Fleet Observability Feature in a fleet. + +EXAMPLES + To disable the Fleet Observability Feature, run: + + $ gcloud beta container hub fleetobservability disable + +FLAGS + --force + Disable this feature, even if it is currently in use. Force disablement + may result in unexpected behavior. + +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 fleetobservability disable + + $ gcloud alpha container hub fleetobservability disable + diff --git a/gcloud/beta/container/hub/fleetobservability/enable b/gcloud/beta/container/hub/fleetobservability/enable new file mode 100644 index 000000000..34038da86 --- /dev/null +++ b/gcloud/beta/container/hub/fleetobservability/enable @@ -0,0 +1,31 @@ +NAME + gcloud beta container hub fleetobservability enable - enables the Fleet + Observability Feature + +SYNOPSIS + gcloud beta container hub fleetobservability enable [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) This command enables Fleet Observability Feature in a fleet. + +EXAMPLES + To enable the Fleet Observability Feature, run: + + $ gcloud beta container hub fleetobservability enable + +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 fleetobservability enable + + $ gcloud alpha container hub fleetobservability enable + diff --git a/gcloud/beta/container/hub/fleetobservability/help b/gcloud/beta/container/hub/fleetobservability/help new file mode 100644 index 000000000..2cc7959a5 --- /dev/null +++ b/gcloud/beta/container/hub/fleetobservability/help @@ -0,0 +1,39 @@ +NAME + gcloud beta container hub fleetobservability - manage Fleet Observability + Feature + +SYNOPSIS + gcloud beta container hub fleetobservability COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Manage Fleet Observability Feature. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + describe + (BETA) Describes the status of the Fleet Observability Feature + resource. + + disable + (BETA) Disables the Fleet Observability Feature. + + enable + (BETA) Enables the Fleet Observability Feature. + + update + (BETA) Updates the Fleet Observability Feature resource. + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud container hub fleetobservability + + $ gcloud alpha container hub fleetobservability + diff --git a/gcloud/beta/container/hub/fleetobservability/update b/gcloud/beta/container/hub/fleetobservability/update new file mode 100644 index 000000000..074a7a0f4 --- /dev/null +++ b/gcloud/beta/container/hub/fleetobservability/update @@ -0,0 +1,60 @@ +NAME + gcloud beta container hub fleetobservability update - updates the Fleet + Observability Feature resource + +SYNOPSIS + gcloud beta container hub fleetobservability update + [--logging-config=LOGGING_CONFIG] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) This command updates the Fleet Observability Feature in a fleet. + +EXAMPLES + To describe the Fleet Observability Feature, run: + + $ gcloud beta container hub fleetobservability update \ + --logging-config=LOGGING-CONFIG + +FLAGS + --logging-config=LOGGING_CONFIG + Path of the YAML(or JSON) file that contains the logging + configurations. + + The JSON file is formatted as follows, with camelCase field naming: + + { + "loggingConfig": { + "defaultConfig": { + "mode": "COPY" + }, + "fleetScopeLogsConfig": { + "mode": "MOVE" + } + } + } + + The YAML file is formatted as follows, with camelCase field naming: + + --- + loggingConfig: + defaultConfig: + mode: COPY + fleetScopeLogsConfig: + mode: MOVE + +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 fleetobservability update + + $ gcloud alpha container hub fleetobservability update + diff --git a/gcloud/beta/container/hub/help b/gcloud/beta/container/hub/help index 6523718f9..154eadd83 100644 --- a/gcloud/beta/container/hub/help +++ b/gcloud/beta/container/hub/help @@ -54,6 +54,9 @@ GROUPS features (BETA) Manage Hub Feature resources. + fleetobservability + (BETA) Manage Fleet Observability Feature. + identity-service (BETA) Manage Identity Service Feature. diff --git a/gcloud/beta/functions/deploy b/gcloud/beta/functions/deploy index 655f236ff..e77e5a623 100644 --- a/gcloud/beta/functions/deploy +++ b/gcloud/beta/functions/deploy @@ -622,6 +622,16 @@ FLAGS argument or as multiple arguments. This is only relevant when --gen2 is provided. + The provided attribute/value pair will be used with the + match-path-pattern operator to configure the trigger, see + https://cloud.google.com/eventarc/docs/reference/rest/v1/projects.locations.triggers#eventfilter + and http://cloud/eventarc/docs/path-patterns for more details about + on how to construct path patterns. + + For example, to filter on events for Compute Engine VMs in a given + zone: + --trigger-event-filters-path-pattern=resourceName='/projects/*/zones/us-central1-a/instances/*' + GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, diff --git a/gcloud/beta/iam/workforce-pools/providers/create-oidc b/gcloud/beta/iam/workforce-pools/providers/create-oidc index 483593287..82f11662c 100644 --- a/gcloud/beta/iam/workforce-pools/providers/create-oidc +++ b/gcloud/beta/iam/workforce-pools/providers/create-oidc @@ -8,8 +8,9 @@ SYNOPSIS --attribute-mapping=[ATTRIBUTE_MAPPING,...] --client-id=CLIENT_ID --issuer-uri=ISSUER_URI (--web-sso-assertion-claims-behavior=WEB_SSO_ASSERTION_CLAIMS_BEHAVIOR - --web-sso-response-type=WEB_SSO_RESPONSE_TYPE) [--async] - [--attribute-condition=ATTRIBUTE_CONDITION] + --web-sso-response-type=WEB_SSO_RESPONSE_TYPE + : --web-sso-additional-scopes=[WEB_SSO_ADDITIONAL_SCOPES,...]) + [--async] [--attribute-condition=ATTRIBUTE_CONDITION] [--client-secret-value=CLIENT_SECRET_VALUE] [--description=DESCRIPTION] [--disabled] [--display-name=DISPLAY_NAME] [GCLOUD_WIDE_FLAG ...] @@ -28,9 +29,11 @@ EXAMPLES --description="My workforce pool provider description." \ --disabled --attribute-mapping="google.subject=assertion.sub" \ --attribute-condition="true" --client-id="client-id" \ + --client-secret-value="client-secret" \ --issuer-uri="https://test-idp.com" \ - --web-sso-response-type=id-token \ - --web-sso-assertion-claims-behavior=only-id-token-claims + --web-sso-response-type="code" \ + --web-sso-assertion-claims-behavior="merge-user-info-over-id-tok\ + en-claims" --web-sso-additional-scopes="groups,photos" POSITIONAL ARGUMENTS Workforce pool provider resource - The workforce pool provider to create. @@ -182,6 +185,15 @@ REQUIRED FLAGS This flag argument must be specified if any of the other arguments in this group are specified. + --web-sso-additional-scopes=[WEB_SSO_ADDITIONAL_SCOPES,...] + Additional scopes to request for the OIDC authentication on top of + scopes requested by default. By default, the openid, profile and + email scopes that are supported by the identity provider are + requested. + + Each additional scope may be at most 256 characters. A maximum of 10 + additional scopes may be configured. + OPTIONAL FLAGS --async Return immediately, without waiting for the operation in progress to diff --git a/gcloud/beta/iam/workforce-pools/providers/update-oidc b/gcloud/beta/iam/workforce-pools/providers/update-oidc index b30eb3e01..494c85f08 100644 --- a/gcloud/beta/iam/workforce-pools/providers/update-oidc +++ b/gcloud/beta/iam/workforce-pools/providers/update-oidc @@ -9,6 +9,7 @@ SYNOPSIS [--attribute-mapping=[ATTRIBUTE_MAPPING,...]] [--client-id=CLIENT_ID] [--description=DESCRIPTION] [--disabled] [--display-name=DISPLAY_NAME] [--issuer-uri=ISSUER_URI] + [--web-sso-additional-scopes=[WEB_SSO_ADDITIONAL_SCOPES,...]] [--web-sso-assertion-claims-behavior=WEB_SSO_ASSERTION_CLAIMS_BEHAVIOR] [--web-sso-response-type=WEB_SSO_RESPONSE_TYPE] [--clear-client-secret | --client-secret-value=CLIENT_SECRET_VALUE] @@ -29,9 +30,11 @@ EXAMPLES --description="My workforce pool provider description." \ --disabled --attribute-mapping="google.subject=assertion.sub" \ --attribute-condition="true" --client-id="client-id" \ + --client-secret-value="client-secret" \ --issuer-uri="https://test-idp.com" \ - --web-sso-response-type=id-token \ - --web-sso-assertion-claims-behavior=only-id-token-claims + --web-sso-response-type="code" \ + --web-sso-assertion-claims-behavior="merge-user-info-over-id-tok\ + en-claims" --web-sso-additional-scopes="groups,photos" POSITIONAL ARGUMENTS Workforce pool provider resource - The workforce pool provider to update. @@ -192,6 +195,14 @@ FLAGS --issuer-uri=ISSUER_URI The OIDC issuer URI. Must be a valid URI using the 'https' scheme. + --web-sso-additional-scopes=[WEB_SSO_ADDITIONAL_SCOPES,...] + Additional scopes to request for the OIDC authentication on top of + scopes requested by default. By default, the openid, profile and email + scopes that are supported by the identity provider are requested. + + Each additional scope may be at most 256 characters. A maximum of 10 + additional scopes may be configured. + --web-sso-assertion-claims-behavior=WEB_SSO_ASSERTION_CLAIMS_BEHAVIOR The behavior for how OIDC Claims are included in the assertion object used for attribute mapping and attribute condition. Use diff --git a/gcloud/beta/memcache/instances/create b/gcloud/beta/memcache/instances/create index d426034dd..c51f7652d 100644 --- a/gcloud/beta/memcache/instances/create +++ b/gcloud/beta/memcache/instances/create @@ -11,6 +11,7 @@ SYNOPSIS [--maintenance-window-duration=MAINTENANCE_WINDOW_DURATION] [--maintenance-window-start-time=MAINTENANCE_WINDOW_START_TIME] [--memcached-version=MEMCACHED_VERSION] [--parameters=KEY=VALUE] + [--reserved-ip-range-id=[RESERVED_IP_RANGE_ID,...]] [--zones=[ZONES,...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -170,6 +171,11 @@ OPTIONAL FLAGS hash-algorithm This is an enum with accepted values of ["jenkins", "murmur3"]. + --reserved-ip-range-id=[RESERVED_IP_RANGE_ID,...] + Contains the name of allocated IP address ranges associated with the + private service access connection for example, "test-default" + associated with IP range 10.0.0.0/29. + --zones=[ZONES,...] List of zones for the memcache nodes. The nodes will be divided equally across the given zones up to --node-count value. If not provided, the diff --git a/gcloud/beta/ml-engine/models/remove-iam-policy-binding b/gcloud/beta/ml-engine/models/remove-iam-policy-binding index 55ef30056..0f4a56d3d 100644 --- a/gcloud/beta/ml-engine/models/remove-iam-policy-binding +++ b/gcloud/beta/ml-engine/models/remove-iam-policy-binding @@ -26,7 +26,7 @@ EXAMPLES --member='allAuthenticatedUsers' --role='roles/ml.admin' See https://cloud.google.com/iam/docs/managing-policies for details of - policy role and principal types. + policy role and member types. POSITIONAL ARGUMENTS Model resource - The AI Platform model for which to remove IAM policy diff --git a/gcloud/beta/network-security/firewall-endpoint-associations/create b/gcloud/beta/network-security/firewall-endpoint-associations/create index d285d6de4..3b6b6cb33 100644 --- a/gcloud/beta/network-security/firewall-endpoint-associations/create +++ b/gcloud/beta/network-security/firewall-endpoint-associations/create @@ -8,7 +8,11 @@ SYNOPSIS (--endpoint=ENDPOINT : --endpoint-zone=ENDPOINT_ZONE --organization=ORGANIZATION) [--async] [--labels=[KEY=VALUE,...]] - [--max-wait=MAX_WAIT; default="60m"] [GCLOUD_WIDE_FLAG ...] + [--max-wait=MAX_WAIT; default="60m"] + [--tls-inspection-policy=TLS_INSPECTION_POLICY + : --tls-inspection-policy-project=TLS_INSPECTION_POLICY_PROJECT + --tls-inspection-policy-region=TLS_INSPECTION_POLICY_REGION] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) Associate the specified network with the firewall endpoint. @@ -134,6 +138,43 @@ OPTIONAL FLAGS specified. See $ gcloud topic datetimes for information on time formats. + TLS Inspection Policy resource - Path to TLS Inspection Policy + configuration to use for intercepting TLS-encrypted traffic in this + network. The arguments in this group can be used to specify the attributes + of this resource. + + --tls-inspection-policy=TLS_INSPECTION_POLICY + ID of the TLS Inspection Policy or fully qualified identifier for the + TLS Inspection Policy. + + To set the tls_inspection_policy attribute: + ▸ provide the argument --tls-inspection-policy on the command line. + + This flag argument must be specified if any of the other arguments in + this group are specified. + + --tls-inspection-policy-project=TLS_INSPECTION_POLICY_PROJECT + Project of the TLS Inspection Policy. + + To set the tls-inspection-policy-project attribute: + ▸ provide the argument --tls-inspection-policy on the command line + with a fully specified name; + ▸ provide the argument --tls-inspection-policy-project on the + command line; + ▸ provide the argument --project on the command line; + ▸ provide the argument FIREWALL_ENDPOINT_ASSOCIATION on the command + line with a fully specified name. + + --tls-inspection-policy-region=TLS_INSPECTION_POLICY_REGION + Region of the TLS Inspection Policy. NOTE: TLS Inspection Policy + needs to be in the same region as Firewall Plus endpoint resource. + + To set the tls-inspection-policy-region attribute: + ▸ provide the argument --tls-inspection-policy on the command line + with a fully specified name; + ▸ provide the argument --tls-inspection-policy-region on the + command line. + GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, diff --git a/gcloud/beta/network-security/firewall-endpoint-associations/update b/gcloud/beta/network-security/firewall-endpoint-associations/update index b17faeaa8..ada71d5c5 100644 --- a/gcloud/beta/network-security/firewall-endpoint-associations/update +++ b/gcloud/beta/network-security/firewall-endpoint-associations/update @@ -6,7 +6,12 @@ SYNOPSIS gcloud beta network-security firewall-endpoint-associations update (FIREWALL_ENDPOINT_ASSOCIATION : --zone=ZONE) [--async] [--max-wait=MAX_WAIT; default="60m"] [--update-labels=[KEY=VALUE,...]] - [--clear-labels | --remove-labels=[KEY,...]] [GCLOUD_WIDE_FLAG ...] + [--clear-labels | --remove-labels=[KEY,...]] + [--no-tls-inspection-policy + | [--tls-inspection-policy=TLS_INSPECTION_POLICY + : --tls-inspection-policy-project=TLS_INSPECTION_POLICY_PROJECT + --tls-inspection-policy-region=TLS_INSPECTION_POLICY_REGION]] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) Update a firewall endpoint association. Check the progress of @@ -109,6 +114,49 @@ FLAGS silently ignored. If --update-labels is also specified then --update-labels is applied first. + At most one of these can be specified: + + --no-tls-inspection-policy + Remove TLS inspection policy from this association. + + TLS Inspection Policy resource - Path to TLS Inspection Policy + configuration to use for intercepting TLS-encrypted traffic in this + network. The arguments in this group can be used to specify the + attributes of this resource. + + --tls-inspection-policy=TLS_INSPECTION_POLICY + ID of the TLS Inspection Policy or fully qualified identifier for + the TLS Inspection Policy. + + To set the tls_inspection_policy attribute: + ▫ provide the argument --tls-inspection-policy on the command + line. + + This flag argument must be specified if any of the other arguments + in this group are specified. + + --tls-inspection-policy-project=TLS_INSPECTION_POLICY_PROJECT + Project of the TLS Inspection Policy. + + To set the tls-inspection-policy-project attribute: + ▫ provide the argument --tls-inspection-policy on the command + line with a fully specified name; + ▫ provide the argument --tls-inspection-policy-project on the + command line; + ▫ provide the argument --project on the command line; + ▫ provide the argument FIREWALL_ENDPOINT_ASSOCIATION on the + command line with a fully specified name. + + --tls-inspection-policy-region=TLS_INSPECTION_POLICY_REGION + Region of the TLS Inspection Policy. NOTE: TLS Inspection Policy + needs to be in the same region as Firewall Plus endpoint resource. + + To set the tls-inspection-policy-region attribute: + ▫ provide the argument --tls-inspection-policy on the command + line with a fully specified name; + ▫ provide the argument --tls-inspection-policy-region on the + command line. + GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, diff --git a/gcloud/beta/network-security/security-profile-groups/create b/gcloud/beta/network-security/security-profile-groups/create index 1c3af6f3e..8212245d8 100644 --- a/gcloud/beta/network-security/security-profile-groups/create +++ b/gcloud/beta/network-security/security-profile-groups/create @@ -13,10 +13,10 @@ DESCRIPTION (BETA) Create a new Security Profile Group with the given name. EXAMPLES - To create a Security Profile Group with the name my-security-profile-group - (Either a fully specified path or --location and --organization flags for - SPG should be specified), --threat-prevention-profile my-security-profile - and optional description as optional description, run: + To create a Security Profile Group with the name my-security-profile-group, + with a fully specified threat prevention profile using + --threat-prevention-profile flag and optional description as optional + description, run: $ gcloud beta network-security security-profile-groups create \ my-security-profile-group --organization=1234 \ @@ -43,12 +43,13 @@ POSITIONAL ARGUMENTS arguments in this group are specified. --location=LOCATION - Location Id. + Location Id of the resource. To set the location attribute: ▸ provide the argument security_profile_group on the command line with a fully specified name; - ▸ provide the argument --location on the command line. + ▸ provide the argument --location on the command line; + ▸ use default global location . --organization=ORGANIZATION Organization number. diff --git a/gcloud/beta/network-security/security-profile-groups/delete b/gcloud/beta/network-security/security-profile-groups/delete index 9b5cffdc6..6c48bb700 100644 --- a/gcloud/beta/network-security/security-profile-groups/delete +++ b/gcloud/beta/network-security/security-profile-groups/delete @@ -12,9 +12,7 @@ DESCRIPTION (BETA) Delete the specified Security Profile Group. EXAMPLES - To delete an Security Profile Group called my-security-profile-group - (Either a fully specified path or --location and --organization flags for - SPG should be specified) run: + To delete an Security Profile Group called my-security-profile-group run: $ gcloud beta network-security security-profile-groups delete \ my-security-profile-group --organization=1234 --location=global @@ -37,12 +35,13 @@ POSITIONAL ARGUMENTS arguments in this group are specified. --location=LOCATION - Location Id. + Location Id of the resource. To set the location attribute: ▸ provide the argument security_profile_group on the command line with a fully specified name; - ▸ provide the argument --location on the command line. + ▸ provide the argument --location on the command line; + ▸ use default global location . --organization=ORGANIZATION Organization number. diff --git a/gcloud/beta/network-security/security-profile-groups/describe b/gcloud/beta/network-security/security-profile-groups/describe index 0f1a8482f..3542081f6 100644 --- a/gcloud/beta/network-security/security-profile-groups/describe +++ b/gcloud/beta/network-security/security-profile-groups/describe @@ -13,8 +13,7 @@ DESCRIPTION EXAMPLES To show details of a Security Profile Group named my-security-profile-group - (Either a fully specified path or --location and --organization flags for - SPG should be specified) run: + run: $ gcloud beta network-security security-profile-groups describe \ my-security-profile-group --organization=1234 --location=global @@ -37,12 +36,13 @@ POSITIONAL ARGUMENTS arguments in this group are specified. --location=LOCATION - Location Id. + Location Id of the resource. To set the location attribute: ▸ provide the argument security_profile_group on the command line with a fully specified name; - ▸ provide the argument --location on the command line. + ▸ provide the argument --location on the command line; + ▸ use default global location . --organization=ORGANIZATION Organization number. diff --git a/gcloud/beta/network-security/security-profile-groups/list b/gcloud/beta/network-security/security-profile-groups/list index aa1376957..78c4bd106 100644 --- a/gcloud/beta/network-security/security-profile-groups/list +++ b/gcloud/beta/network-security/security-profile-groups/list @@ -12,7 +12,7 @@ DESCRIPTION (BETA) List all Security Profile Groups in the specified location. EXAMPLES - To list Security Profile Groups in specifed location and organization, run: + To list Security Profile Groups in specifed location, run: $ gcloud beta network-security security-profile-groups list \ --location=global diff --git a/gcloud/beta/network-security/security-profile-groups/update b/gcloud/beta/network-security/security-profile-groups/update index 3377ded4a..7142956ac 100644 --- a/gcloud/beta/network-security/security-profile-groups/update +++ b/gcloud/beta/network-security/security-profile-groups/update @@ -14,9 +14,8 @@ DESCRIPTION (BETA) Update the details of a Security Profile Group. EXAMPLES - To update an SPG with new Threat prevention profile my-new-security-profile - (Either a fully specified path or --location and --organization flags for - SPG should be specified), run: + To update a Security Profile Group with new threat prevention profile + my-new-security-profile, run: $ gcloud beta network-security security-profile-groups update \ my-security-profile-group --organization=1234 \ @@ -43,12 +42,13 @@ POSITIONAL ARGUMENTS arguments in this group are specified. --location=LOCATION - Location Id. + Location Id of the resource. To set the location attribute: ▸ provide the argument security_profile_group on the command line with a fully specified name; - ▸ provide the argument --location on the command line. + ▸ provide the argument --location on the command line; + ▸ use default global location . --organization=ORGANIZATION Organization number. diff --git a/gcloud/beta/network-security/security-profiles/threat-prevention/add-override b/gcloud/beta/network-security/security-profiles/threat-prevention/add-override index 8771848c1..47ed46be2 100644 --- a/gcloud/beta/network-security/security-profiles/threat-prevention/add-override +++ b/gcloud/beta/network-security/security-profiles/threat-prevention/add-override @@ -28,7 +28,7 @@ EXAMPLES my-security-profile is the name of the Security Profile in the format organizations/{organizationID}/locations/{location}/securityProfiles/ {security_profile_id} where organizationID is the organization ID to which - the changes should apply, location either global or region specified and + the changes should apply, location - global specified and security_profile_id the Security Profile Identifier POSITIONAL ARGUMENTS @@ -48,7 +48,7 @@ POSITIONAL ARGUMENTS arguments in this group are specified. --location=LOCATION - location of the security_profile Global|Region. + location of the security_profile - Global. To set the location attribute: ▸ provide the argument security_profile on the command line with a diff --git a/gcloud/beta/network-security/security-profiles/threat-prevention/create b/gcloud/beta/network-security/security-profiles/threat-prevention/create index 73a033bbf..073215f6a 100644 --- a/gcloud/beta/network-security/security-profiles/threat-prevention/create +++ b/gcloud/beta/network-security/security-profiles/threat-prevention/create @@ -11,8 +11,7 @@ DESCRIPTION (BETA) Create a new Security Profile with the given name. EXAMPLES - To create a Security Profile with the name my-security-profile which - includes location as global or region specifed and organization ID, + To create a Security Profile with the name my-security-profile and an optional description as New Security Profile, run: $ gcloud beta network-security security-profiles threat-prevention \ @@ -35,7 +34,7 @@ POSITIONAL ARGUMENTS arguments in this group are specified. --location=LOCATION - location of the security_profile Global|Region. + location of the security_profile - Global. To set the location attribute: ▸ provide the argument security_profile on the command line with a diff --git a/gcloud/beta/network-security/security-profiles/threat-prevention/delete b/gcloud/beta/network-security/security-profiles/threat-prevention/delete index dbe7a1a02..df2d9e881 100644 --- a/gcloud/beta/network-security/security-profiles/threat-prevention/delete +++ b/gcloud/beta/network-security/security-profiles/threat-prevention/delete @@ -11,8 +11,7 @@ DESCRIPTION (BETA) Delete the specified Security Profile. EXAMPLES - To delete a Security Profile called my-security-profile which includes - location as global or region specifed and organization ID, run: + To delete a Security Profile called my-security-profile run: $ gcloud beta network-security security-profiles threat-prevention \ delete my-security-profile @@ -35,12 +34,13 @@ POSITIONAL ARGUMENTS arguments in this group are specified. --location=LOCATION - Location Id. + Location Id of the resource. To set the location attribute: ▸ provide the argument security_profile on the command line with a fully specified name; - ▸ provide the argument --location on the command line. + ▸ provide the argument --location on the command line; + ▸ use default global location . --organization=ORGANIZATION Organization number. diff --git a/gcloud/beta/network-security/security-profiles/threat-prevention/delete-override b/gcloud/beta/network-security/security-profiles/threat-prevention/delete-override index 82192b7ce..3342fe1a4 100644 --- a/gcloud/beta/network-security/security-profiles/threat-prevention/delete-override +++ b/gcloud/beta/network-security/security-profiles/threat-prevention/delete-override @@ -26,7 +26,7 @@ EXAMPLES my-security-profile is the name of the Security Profile in the format organizations/{organizationID}/locations/{location}/securityProfiles/ {security_profile_id} where organizationID is the organization ID to which - the changes should apply, location either global or region specified and + the changes should apply, location - global specified and security_profile_id the Security Profile Identifier POSITIONAL ARGUMENTS @@ -46,7 +46,7 @@ POSITIONAL ARGUMENTS arguments in this group are specified. --location=LOCATION - location of the security_profile Global|Region. + location of the security_profile - Global. To set the location attribute: ▸ provide the argument security_profile on the command line with a diff --git a/gcloud/beta/network-security/security-profiles/threat-prevention/list b/gcloud/beta/network-security/security-profiles/threat-prevention/list index 36e0ad759..786e491f8 100644 --- a/gcloud/beta/network-security/security-profiles/threat-prevention/list +++ b/gcloud/beta/network-security/security-profiles/threat-prevention/list @@ -12,7 +12,7 @@ DESCRIPTION (BETA) List all Security Profiles in the specified location. EXAMPLES - To list Security Profiles in specifed location and organization, run: + To list Security Profiles in specifed location run: $ gcloud beta network-security security-profiles threat-prevention \ list --location=global diff --git a/gcloud/beta/network-security/security-profiles/threat-prevention/list-overrides b/gcloud/beta/network-security/security-profiles/threat-prevention/list-overrides index f099c1738..c2dda4758 100644 --- a/gcloud/beta/network-security/security-profiles/threat-prevention/list-overrides +++ b/gcloud/beta/network-security/security-profiles/threat-prevention/list-overrides @@ -23,7 +23,7 @@ EXAMPLES my-security-profile is the name of the Security Profile in the format organizations/{organizationID}/locations/{location}/securityProfiles/ {security_profile_id} where organizationID is the organization ID to which - the changes should apply, location either global or region specified and + the changes should apply, location - global specified and security_profile_id the Security Profile Identifier POSITIONAL ARGUMENTS @@ -43,7 +43,7 @@ POSITIONAL ARGUMENTS arguments in this group are specified. --location=LOCATION - location of the security_profile Global|Region. + location of the security_profile - Global. To set the location attribute: ▸ provide the argument security_profile on the command line with a diff --git a/gcloud/beta/network-security/security-profiles/threat-prevention/update-override b/gcloud/beta/network-security/security-profiles/threat-prevention/update-override index d349ed722..f856dadc9 100644 --- a/gcloud/beta/network-security/security-profiles/threat-prevention/update-override +++ b/gcloud/beta/network-security/security-profiles/threat-prevention/update-override @@ -28,7 +28,7 @@ EXAMPLES my-security-profile is the name of the Security Profile in the format organizations/{organizationID}/locations/{location}/securityProfiles/ {security_profile_id} where organizationID is the organization ID to which - the changes should apply, location either global or region specified and + the changes should apply, location - global specified and security_profile_id the Security Profile Identifier POSITIONAL ARGUMENTS @@ -48,7 +48,7 @@ POSITIONAL ARGUMENTS arguments in this group are specified. --location=LOCATION - location of the security_profile Global|Region. + location of the security_profile - Global. To set the location attribute: ▸ provide the argument security_profile on the command line with a diff --git a/gcloud/beta/projects/get-ancestors-iam-policy b/gcloud/beta/projects/get-ancestors-iam-policy index 97969e1a7..992dd8e62 100644 --- a/gcloud/beta/projects/get-ancestors-iam-policy +++ b/gcloud/beta/projects/get-ancestors-iam-policy @@ -18,14 +18,13 @@ EXAMPLES $ gcloud beta projects get-ancestors-iam-policy example-project-id-1 POSITIONAL ARGUMENTS - Project id resource - ID for the project you want to get IAM policy for. - This represents a Cloud resource. + Project resource - ID for the project you want to get IAM policy for. This + represents a Cloud resource. This must be specified. PROJECT_ID - ID of the project_id or fully qualified identifier for the - project_id. + ID of the project or fully qualified identifier for the project. To set the project_id attribute: ▸ provide the argument project_id on the command line. diff --git a/gcloud/beta/scc/assets/describe b/gcloud/beta/scc/assets/describe index 90c697b77..7183bd082 100644 --- a/gcloud/beta/scc/assets/describe +++ b/gcloud/beta/scc/assets/describe @@ -7,7 +7,14 @@ SYNOPSIS (--asset=ASSET | --resource-name=RESOURCE_NAME) [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) Describe an asset given its resource name or asset id. + (BETA) (DEPRECATED) Security Command Center Asset APIs are deprecated and + will be removed on or after June 26, 2024. Use Cloud Asset Inventory + instead (gcloud asset) + (https://cloud.google.com/sdk/gcloud/reference/asset). For more + information, see the deprecation notice at Assets Page + (https://cloud.google.com/security-command-center/docs/how-to-use-security-command-center#assets_page). + + Describe an asset given its resource name or asset id. EXAMPLES Describe an asset under organization 123456, given its full resource name diff --git a/gcloud/beta/scc/assets/get-parent b/gcloud/beta/scc/assets/get-parent index 8a22601a1..1f7ded231 100644 --- a/gcloud/beta/scc/assets/get-parent +++ b/gcloud/beta/scc/assets/get-parent @@ -7,7 +7,14 @@ SYNOPSIS (--asset=ASSET | --resource-name=RESOURCE_NAME) [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) Get the Parent for an asset given its resource name or asset id. + (BETA) (DEPRECATED) Security Command Center Asset APIs are deprecated and + will be removed on or after June 26, 2024. Use Cloud Asset Inventory + instead (gcloud asset) + (https://cloud.google.com/sdk/gcloud/reference/asset). For more + information, see the deprecation notice at Assets Page + (https://cloud.google.com/security-command-center/docs/how-to-use-security-command-center#assets_page). + + Get the Parent for an asset given its resource name or asset id. EXAMPLES Get parent's relative resource name given an asset's full resource name diff --git a/gcloud/beta/scc/assets/get-project b/gcloud/beta/scc/assets/get-project index 159cf8501..5f40ae6ec 100644 --- a/gcloud/beta/scc/assets/get-project +++ b/gcloud/beta/scc/assets/get-project @@ -7,7 +7,14 @@ SYNOPSIS (--asset=ASSET | --resource-name=RESOURCE_NAME) [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) Get the Project for an asset given its resource name or asset id. + (BETA) (DEPRECATED) Security Command Center Asset APIs are deprecated and + will be removed on or after June 26, 2024. Use Cloud Asset Inventory + instead (gcloud asset) + (https://cloud.google.com/sdk/gcloud/reference/asset). For more + information, see the deprecation notice at Assets Page + (https://cloud.google.com/security-command-center/docs/how-to-use-security-command-center#assets_page). + + Get the Project for an asset given its resource name or asset id. EXAMPLES Get project id diff --git a/gcloud/beta/scc/assets/group b/gcloud/beta/scc/assets/group index 9c4d67997..def3363e3 100644 --- a/gcloud/beta/scc/assets/group +++ b/gcloud/beta/scc/assets/group @@ -9,7 +9,14 @@ SYNOPSIS [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) Filter an organization's assets and groups them by their specified + (BETA) (DEPRECATED) Security Command Center Asset APIs are deprecated and + will be removed on or after June 26, 2024. Use Cloud Asset Inventory + instead (gcloud asset) + (https://cloud.google.com/sdk/gcloud/reference/asset). For more + information, see the deprecation notice at Assets Page + (https://cloud.google.com/security-command-center/docs/how-to-use-security-command-center#assets_page). + + Filter an organization's assets and groups them by their specified properties. EXAMPLES diff --git a/gcloud/beta/scc/assets/help b/gcloud/beta/scc/assets/help index 14ffba0b6..51d262501 100644 --- a/gcloud/beta/scc/assets/help +++ b/gcloud/beta/scc/assets/help @@ -16,27 +16,30 @@ COMMANDS COMMAND is one of the following: describe - (BETA) Describe an asset given its resource name or asset id. - - get-parent - (BETA) Get the Parent for an asset given its resource name or asset id. - - get-project - (BETA) Get the Project for an asset given its resource name or asset + (BETA) (DEPRECATED) Describe an asset given its resource name or asset id. + get-parent + (BETA) (DEPRECATED) Get the Parent for an asset given its resource name + or asset id. + + get-project + (BETA) (DEPRECATED) Get the Project for an asset given its resource + name or asset id. + group - (BETA) Filter an organization's assets and groups them by their - specified properties. + (BETA) (DEPRECATED) Filter an organization's assets and groups them by + their specified properties. list - (BETA) List Cloud Security Command Center assets. + (BETA) (DEPRECATED) List Cloud Security Command Center assets. list-marks - (BETA) List an assets's security marks. + (BETA) (DEPRECATED) List an assets's security marks. run-discovery - (BETA) Scan an organization for new/modified/deleted assets. + (BETA) (DEPRECATED) Scan an organization for new/modified/deleted + assets. update-marks (BETA) Update Cloud Security Command Center asset's security marks. diff --git a/gcloud/beta/scc/assets/list b/gcloud/beta/scc/assets/list index b783eef28..2476354de 100644 --- a/gcloud/beta/scc/assets/list +++ b/gcloud/beta/scc/assets/list @@ -9,7 +9,14 @@ SYNOPSIS [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) List Cloud Security Command Center assets. + (BETA) (DEPRECATED) Security Command Center Asset APIs are deprecated and + will be removed on or after June 26, 2024. Use Cloud Asset Inventory + instead (gcloud asset) + (https://cloud.google.com/sdk/gcloud/reference/asset). For more + information, see the deprecation notice at Assets Page + (https://cloud.google.com/security-command-center/docs/how-to-use-security-command-center#assets_page). + + List Cloud Security Command Center assets. EXAMPLES List all assets under organization (123456) diff --git a/gcloud/beta/scc/assets/list-marks b/gcloud/beta/scc/assets/list-marks index ed7a6ce81..c0e316404 100644 --- a/gcloud/beta/scc/assets/list-marks +++ b/gcloud/beta/scc/assets/list-marks @@ -8,7 +8,14 @@ SYNOPSIS [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) List an assets's security marks. + (BETA) (DEPRECATED) Security Command Center Asset APIs are deprecated and + will be removed on or after June 26, 2024. Use Cloud Asset Inventory + instead (gcloud asset) + (https://cloud.google.com/sdk/gcloud/reference/asset). For more + information, see the deprecation notice at Assets Page + (https://cloud.google.com/security-command-center/docs/how-to-use-security-command-center#assets_page). + + List an assets's security marks. EXAMPLES List all security marks for asset (8910) under organization (123456): diff --git a/gcloud/beta/scc/assets/run-discovery b/gcloud/beta/scc/assets/run-discovery index 624c92395..3b9b394fc 100644 --- a/gcloud/beta/scc/assets/run-discovery +++ b/gcloud/beta/scc/assets/run-discovery @@ -6,8 +6,15 @@ SYNOPSIS gcloud beta scc assets run-discovery [ORGANIZATION] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) Scan an organization for new/modified/deleted assets. Note that this - API can only be called with limited frequency for an organization. If it is + (BETA) (DEPRECATED) Security Command Center Asset APIs are deprecated and + will be removed on or after June 26, 2024. Use Cloud Asset Inventory + instead (gcloud asset) + (https://cloud.google.com/sdk/gcloud/reference/asset). For more + information, see the deprecation notice at Assets Page + (https://cloud.google.com/security-command-center/docs/how-to-use-security-command-center#assets_page). + + Scan an organization for new/modified/deleted assets. Note that this API + can only be called with limited frequency for an organization. If it is called too frequently the caller will receive a TOO_MANY_REQUESTS error. EXAMPLES diff --git a/gcloud/beta/spanner/databases/execute-sql b/gcloud/beta/spanner/databases/execute-sql index 65bd1bdca..2bf5d2a0d 100644 --- a/gcloud/beta/spanner/databases/execute-sql +++ b/gcloud/beta/spanner/databases/execute-sql @@ -5,7 +5,7 @@ NAME SYNOPSIS gcloud beta spanner databases execute-sql (DATABASE : --instance=INSTANCE) --sql=SQL [--database-role=DATABASE_ROLE] [--enable-partitioned-dml] - [--query-mode=QUERY_MODE; default="NORMAL"] + [--priority=PRIORITY] [--query-mode=QUERY_MODE; default="NORMAL"] [--timeout=TIMEOUT; default="10m"] [--read-timestamp=TIMESTAMP | --strong] [GCLOUD_WIDE_FLAG ...] @@ -64,6 +64,10 @@ OPTIONAL FLAGS --enable-partitioned-dml Execute DML statement using Partitioned DML + --priority=PRIORITY + The priority for the execute SQL request. PRIORITY must be one of: + high, low, medium, unspecified. + --query-mode=QUERY_MODE; default="NORMAL" Mode in which the query must be processed. QUERY_MODE must be one of: diff --git a/gcloud/beta/sql/instances/create b/gcloud/beta/sql/instances/create index fddc4f554..c9ccad99a 100644 --- a/gcloud/beta/sql/instances/create +++ b/gcloud/beta/sql/instances/create @@ -41,6 +41,7 @@ SYNOPSIS [--password-policy-min-length=PASSWORD_POLICY_MIN_LENGTH] [--password-policy-password-change-interval=PASSWORD_POLICY_PASSWORD_CHANGE_INTERVAL] [--password-policy-reuse-interval=PASSWORD_POLICY_REUSE_INTERVAL] + [--[no-]recreate-replicas-on-primary-crash] [--replica-type=REPLICA_TYPE] [--replication=REPLICATION] [--require-ssl] [--retained-backups-count=RETAINED_BACKUPS_COUNT] [--retained-transaction-log-days=RETAINED_TRANSACTION_LOG_DAYS] @@ -360,6 +361,14 @@ FLAGS Number of previous passwords that cannot be reused. The valid range is 0 to 100. + --[no-]recreate-replicas-on-primary-crash + Allow/Disallow replica recreation when a primary MySQL instance + operating in reduced durability mode crashes. Not recreating the + replicas might lead to data inconsistencies between the primary and its + replicas. This setting is only applicable for MySQL instances and is + enabled by default. Use --recreate-replicas-on-primary-crash to enable + and --no-recreate-replicas-on-primary-crash to disable. + --replica-type=REPLICA_TYPE The type of replica to create. REPLICA_TYPE must be one of: READ, FAILOVER. diff --git a/gcloud/beta/sql/instances/patch b/gcloud/beta/sql/instances/patch index 8a650aa44..209c9e48b 100644 --- a/gcloud/beta/sql/instances/patch +++ b/gcloud/beta/sql/instances/patch @@ -37,6 +37,7 @@ SYNOPSIS [--password-policy-password-change-interval=PASSWORD_POLICY_PASSWORD_CHANGE_INTERVAL] [--password-policy-reuse-interval=PASSWORD_POLICY_REUSE_INTERVAL] [--pricing-plan=PRICING_PLAN, -p PRICING_PLAN] + [--[no-]recreate-replicas-on-primary-crash] [--remove-deny-maintenance-period] [--replication=REPLICATION] [--[no-]require-ssl] [--[no-]storage-auto-increase] [--storage-auto-increase-limit=STORAGE_AUTO_INCREASE_LIMIT] @@ -310,6 +311,14 @@ FLAGS First Generation instances only. The pricing plan for this instance. PRICING_PLAN must be one of: PER_USE, PACKAGE. + --[no-]recreate-replicas-on-primary-crash + Allow/Disallow replica recreation when a primary MySQL instance + operating in reduced durability mode crashes. Not recreating the + replicas might lead to data inconsistencies between the primary and its + replicas. This setting is only applicable for MySQL instances and is + enabled by default. Use --recreate-replicas-on-primary-crash to enable + and --no-recreate-replicas-on-primary-crash to disable. + --remove-deny-maintenance-period Removes the user-specified deny maintenance period. diff --git a/gcloud/bigtable/instances/tables/create b/gcloud/bigtable/instances/tables/create index 7deff523f..95ec5fcef 100644 --- a/gcloud/bigtable/instances/tables/create +++ b/gcloud/bigtable/instances/tables/create @@ -3,8 +3,9 @@ NAME SYNOPSIS gcloud bigtable instances tables create (TABLE : --instance=INSTANCE) - --column-families=[COLUMN_FAMILIES,...] [--deletion-protection] - [--splits=[SPLITS,...]] [GCLOUD_WIDE_FLAG ...] + --column-families=[COLUMN_FAMILIES,...] + [--change-stream-retention-period=CHANGE_STREAM_RETENTION_PERIOD] + [--deletion-protection] [--splits=[SPLITS,...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION Create a new Cloud Bigtable table. @@ -34,6 +35,15 @@ EXAMPLES --column-families="my-family-1:maxage=10d,my-family-2:maxversion\ s=5||maxage=5d" + To create a table my-table that has one column family my-family that lets + data expire after 10 days, and to enable a change stream for the table to + be kept for 7 days, run: + + $ gcloud bigtable instances tables create my-table \ + --instance=my-instance \ + --column-families="my-family:maxage=10d" \ + --change-stream-retention-period=7d + To create a deletion-protected table my-table in instance my-instance with a column family my-family, run: @@ -87,6 +97,12 @@ REQUIRED FLAGS "family_1,family_2:maxage=5d&&maxversions=2,family_3:maxage=10d||maxversions=5" OPTIONAL FLAGS + --change-stream-retention-period=CHANGE_STREAM_RETENTION_PERIOD + The length of time to retain change stream data for the table, in the + range of [1 day, 7 days]. Acceptable units are days (d), hours (h), + minutes (m), and seconds (s). Passing in a value for this option + enables a change stream for the table. Examples: 5d or 48h. + --deletion-protection Once specified, the table is deletion protected. diff --git a/gcloud/bigtable/instances/tables/update b/gcloud/bigtable/instances/tables/update index 111457302..9678a0568 100644 --- a/gcloud/bigtable/instances/tables/update +++ b/gcloud/bigtable/instances/tables/update @@ -4,7 +4,9 @@ NAME SYNOPSIS gcloud bigtable instances tables update (TABLE : --instance=INSTANCE) - [--async] [--deletion-protection] [GCLOUD_WIDE_FLAG ...] + [--async] [--deletion-protection] + [--change-stream-retention-period=CHANGE_STREAM_RETENTION_PERIOD + | --clear-change-stream-retention-period] [GCLOUD_WIDE_FLAG ...] DESCRIPTION Update an existing new Cloud Bigtable table with the specified @@ -21,6 +23,17 @@ EXAMPLES $ gcloud bigtable instances tables update my-table \ --instance=my-instance --no-deletion-protection + To enable a change stream with a retention period of 1 day, or to update + your table's change stream retention period to 1 day, run: + + $ gcloud bigtable instances tables update my-table \ + --instance=my-instance --change-stream-retention-period=1d + + To disable a change stream, run: + + $ gcloud bigtable instances tables update my-table \ + --instance=my-instance --clear-change-stream-retention-period + POSITIONAL ARGUMENTS Table resource - Cloud Bigtable table to update. The arguments in this group can be used to specify the attributes of this resource. (NOTE) Some @@ -60,6 +73,18 @@ FLAGS --deletion-protection Once specified, the table is deletion protected. + At most one of these can be specified: + + --change-stream-retention-period=CHANGE_STREAM_RETENTION_PERIOD + The length of time to retain change stream data for the table, in the + range of [1 day, 7 days]. Acceptable units are days (d), hours (h), + minutes (m), and seconds (s). If not already specified, enables a + change stream for the table. Examples: 5d or 48h. + + --clear-change-stream-retention-period + This disables the change stream and eventually removes the change + stream data. + GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, diff --git a/gcloud/builds/triggers/help b/gcloud/builds/triggers/help index 820ce1416..cee86f819 100644 --- a/gcloud/builds/triggers/help +++ b/gcloud/builds/triggers/help @@ -19,6 +19,9 @@ GROUPS create Create build triggers for Google Cloud Build. + update + Update Triggers in Google Cloud Build. + COMMANDS COMMAND is one of the following: diff --git a/gcloud/builds/triggers/update/bitbucketserver b/gcloud/builds/triggers/update/bitbucketserver new file mode 100644 index 000000000..eaaa8db78 --- /dev/null +++ b/gcloud/builds/triggers/update/bitbucketserver @@ -0,0 +1,251 @@ +NAME + gcloud builds triggers update bitbucketserver - updates Bitbucket Server + trigger used by Google Cloud Build + +SYNOPSIS + gcloud builds triggers update bitbucketserver (TRIGGER : --region=REGION) + (--trigger-config=PATH + | --bitbucket-server-config-resource=BITBUCKET_SERVER_CONFIG_RESOURCE + --description=DESCRIPTION --ignored-files=[GLOB,...] + --included-files=[GLOB,...] --project-key=PROJECT_KEY + --repo-slug=REPO_SLUG --[no-]require-approval + --service-account=SERVICE_ACCOUNT --branch-pattern=REGEX + | --tag-pattern=REGEX | --comment-control=COMMENT_CONTROL; + default="COMMENTS_ENABLED" + --pull-request-pattern=REGEX --build-config=PATH + | --inline-config=PATH + | [--dockerfile=DOCKERFILE --dockerfile-image=DOCKERFILE_IMAGE + : --dockerfile-dir=DOCKERFILE_DIR] --clear-substitutions + | --remove-substitutions=[KEY,...] + | --update-substitutions=[KEY=VALUE,...]) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Updates Bitbucket Server trigger used by Google Cloud Build. + +EXAMPLES + To update the branch pattern of the trigger: + + $ gcloud builds triggers update bitbucketserver my-trigger \ + --branch-pattern=".*" + + To update the build config of the trigger: + + $ gcloud builds triggers update bitbucketserver my-trigger \ + --build-config="cloudbuild.yaml" + + To update the substitutions of the trigger: $ gcloud builds triggers update bitbucketserver my-trigger \ + --update-substitutions=_REPO_NAME=my-repo,_BRANCH_NAME=master + +POSITIONAL ARGUMENTS + Trigger resource - Build Trigger. 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 TRIGGER 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. + + TRIGGER + ID of the trigger or fully qualified identifier for the trigger. + + To set the trigger attribute: + ▸ provide the argument TRIGGER 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 location for the trigger. + + To set the region attribute: + ▸ provide the argument TRIGGER on the command line with a fully + specified name; + ▸ provide the argument --region on the command line; + ▸ set the property builds/region. + +REQUIRED FLAGS + Exactly one of these must be specified: + + --trigger-config=PATH + Path to Build Trigger config file (JSON or YAML format). For more + details, see + https://cloud.google.com/cloud-build/docs/api/reference/rest/v1/projects.triggers#BuildTrigger + + Flag based trigger configuration + + --bitbucket-server-config-resource=BITBUCKET_SERVER_CONFIG_RESOURCE + Bitbucket Server config resource name. + + --description=DESCRIPTION + Build trigger description. + + --ignored-files=[GLOB,...] + Glob filter. Changes only affecting ignored files won't trigger + builds. + + --included-files=[GLOB,...] + Glob filter. Changes affecting at least one included file will + trigger builds. + + --project-key=PROJECT_KEY + Bitbucket Server project key. + + --repo-slug=REPO_SLUG + Bitbucket Server repository slug. + + --[no-]require-approval + Require manual approval for triggered builds. Use + --require-approval to enable and --no-require-approval to disable. + + --service-account=SERVICE_ACCOUNT + The service account used for all user-controlled operations + including UpdateBuildTrigger, RunBuildTrigger, CreateBuild, and + CancelBuild. If no service account is set, then the standard Cloud + Build service account ([PROJECT_NUM]@system.gserviceaccount.com) is + used instead. Format: + projects/{PROJECT_ID}/serviceAccounts/{ACCOUNT_ID_OR_EMAIL}. + + At most one of these can be specified: + + --branch-pattern=REGEX + A regular expression specifying which git branches to match. + + This pattern is used as a regular expression search for any + incoming pushes. For example, --branch-pattern=foo will match + "foo", "foobar", and "barfoo". Events on a branch that does not + match will be ignored. + + The syntax of the regular expressions accepted is the syntax + accepted by RE2 and described at + https://github.com/google/re2/wiki/Syntax. + + --tag-pattern=REGEX + A regular expression specifying which git tags to match. + + This pattern is used as a regular expression search for any + incoming pushes. For example, --tag-pattern=foo will match "foo", + "foobar", and "barfoo". Events on a tag that does not match will + be ignored. + + The syntax of the regular expressions accepted is the syntax + accepted by RE2 and described at + https://github.com/google/re2/wiki/Syntax. + + Pull Request settings + + --comment-control=COMMENT_CONTROL; default="COMMENTS_ENABLED" + Require a repository collaborator or owner to comment '/gcbrun' + on a pull request before running the build. COMMENT_CONTROL + must be one of: + + COMMENTS_DISABLED + Do not require comments on Pull Requests before builds are + triggered. + COMMENTS_ENABLED + Enforce that repository owners or collaborators must + comment on Pull Requests before builds are triggered. + COMMENTS_ENABLED_FOR_EXTERNAL_CONTRIBUTORS_ONLY + Enforce that repository owners or collaborators must + comment on external contributors' Pull Requests before + builds are triggered. + + --pull-request-pattern=REGEX + A regular expression specifying which base git branch to match + for pull request events. + + This pattern is used as a regular expression search for the + base branch (the branch you are trying to merge into) for pull + request updates. For example, --pull-request-pattern=foo will + match "foo", "foobar", and "barfoo". + + The syntax of the regular expressions accepted is the syntax + accepted by RE2 and described at + https://github.com/google/re2/wiki/Syntax. + + At most one of these can be specified: + + --build-config=PATH + Path to a YAML or JSON file containing the build configuration in + the repository. + + For more details, see: + https://cloud.google.com/cloud-build/docs/build-config + + --inline-config=PATH + Local path to a YAML or JSON file containing a build + configuration. + + Dockerfile build configuration flags + + --dockerfile=DOCKERFILE + Path of Dockerfile to use for builds in the repository. + + If specified, a build config will be generated to run docker + build using the specified file. + + The filename is relative to the Dockerfile directory. + + This flag argument must be specified if any of the other + arguments in this group are specified. + + --dockerfile-image=DOCKERFILE_IMAGE + Docker image name to build. + + This flag argument must be specified if any of the other + arguments in this group are specified. + + --dockerfile-dir=DOCKERFILE_DIR + Location of the directory containing the Dockerfile in the + repository. + + The directory will also be used as the Docker build context. + + At most one of these can be specified: + + --clear-substitutions + Clear existing substitutions. + + --remove-substitutions=[KEY,...] + Remove existing substitutions if present. + + --update-substitutions=[KEY=VALUE,...] + Update or add to existing substitutions. Substitutions are + parameters to be substituted or add in the build specification. + + For example (using some nonsensical substitution keys; all keys + must begin with an underscore): + + $ gcloud builds triggers update ... + --update-substitutions _FAVORITE_COLOR=blue,_NUM_CANDIES=10 + + This will add the provided substitutions to the existing + substitutions and results in a build where every occurrence of + ${_FAVORITE_COLOR} in certain fields is replaced by "blue", and + similarly for ${_NUM_CANDIES} and "10". + + Only the following built-in variables can be specified with the + --substitutions flag: REPO_NAME, BRANCH_NAME, TAG_NAME, + REVISION_ID, COMMIT_SHA, SHORT_SHA. + + For more details, see: + https://cloud.google.com/build/docs/build-config-file-schema#substitutions + +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 builds triggers update bitbucketserver + + $ gcloud beta builds triggers update bitbucketserver + diff --git a/gcloud/builds/triggers/update/cloud-source-repositories b/gcloud/builds/triggers/update/cloud-source-repositories new file mode 100644 index 000000000..4eec0f6c1 --- /dev/null +++ b/gcloud/builds/triggers/update/cloud-source-repositories @@ -0,0 +1,225 @@ +NAME + gcloud builds triggers update cloud-source-repositories - updates Cloud + Source Repositories trigger used by Google Cloud Build + +SYNOPSIS + gcloud builds triggers update cloud-source-repositories + (TRIGGER : --region=REGION) + (--trigger-config=PATH | --description=DESCRIPTION + --ignored-files=[GLOB,...] --included-files=[GLOB,...] --repo=REPO + --[no-]require-approval + --service-account=SERVICE_ACCOUNT --branch-pattern=REGEX + | --tag-pattern=REGEX --build-config=PATH | --inline-config=PATH + | [--dockerfile=DOCKERFILE --dockerfile-image=DOCKERFILE_IMAGE + : --dockerfile-dir=DOCKERFILE_DIR] --clear-substitutions + | --remove-substitutions=[KEY,...] + | --update-substitutions=[KEY=VALUE,...]) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Updates Cloud Source Repositories trigger used by Google Cloud Build. + +EXAMPLES + To update the branch pattern of the trigger: + + $ gcloud builds triggers update cloud-source-repositories \ + my-trigger --branch-pattern=".*" + + To update the build config of the trigger: + + $ gcloud builds triggers update cloud-source-repositories \ + my-trigger --build-config="cloudbuild.yaml" + + To update the substitutions of the trigger: + + $ gcloud builds triggers update cloud-source-repositories \ + my-trigger \ + --update-substitutions=_REPO_NAME=my-repo,_BRANCH_NAME=master + +POSITIONAL ARGUMENTS + Trigger resource - Build Trigger. 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 TRIGGER 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. + + TRIGGER + ID of the trigger or fully qualified identifier for the trigger. + + To set the trigger attribute: + ▸ provide the argument TRIGGER 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 location for the trigger. + + To set the region attribute: + ▸ provide the argument TRIGGER on the command line with a fully + specified name; + ▸ provide the argument --region on the command line; + ▸ set the property builds/region. + +REQUIRED FLAGS + Exactly one of these must be specified: + + --trigger-config=PATH + Path to Build Trigger config file (JSON or YAML format). For more + details, see + https://cloud.google.com/cloud-build/docs/api/reference/rest/v1/projects.triggers#BuildTrigger + + Flag based trigger configuration + + --description=DESCRIPTION + Build trigger description. + + --ignored-files=[GLOB,...] + Glob filter. Changes only affecting ignored files won't trigger + builds. + + --included-files=[GLOB,...] + Glob filter. Changes affecting at least one included file will + trigger builds. + + Repo resource - Cloud Source Repository. 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 --repo on the command line with a fully + specified name; + ▫ set the property core/project. + + --repo=REPO + ID of the repo or fully qualified identifier for the repo. + + To set the repo attribute: + ◇ provide the argument --repo on the command line. + + --[no-]require-approval + Require manual approval for triggered builds. Use + --require-approval to enable and --no-require-approval to disable. + + --service-account=SERVICE_ACCOUNT + The service account used for all user-controlled operations + including UpdateBuildTrigger, RunBuildTrigger, CreateBuild, and + CancelBuild. If no service account is set, then the standard Cloud + Build service account ([PROJECT_NUM]@system.gserviceaccount.com) is + used instead. Format: + projects/{PROJECT_ID}/serviceAccounts/{ACCOUNT_ID_OR_EMAIL}. + + At most one of these can be specified: + + --branch-pattern=REGEX + A regular expression specifying which git branches to match. + + This pattern is used as a regular expression search for any + incoming pushes. For example, --branch-pattern=foo will match + "foo", "foobar", and "barfoo". Events on a branch that does not + match will be ignored. + + The syntax of the regular expressions accepted is the syntax + accepted by RE2 and described at + https://github.com/google/re2/wiki/Syntax. + + --tag-pattern=REGEX + A regular expression specifying which git tags to match. + + This pattern is used as a regular expression search for any + incoming pushes. For example, --tag-pattern=foo will match "foo", + "foobar", and "barfoo". Events on a tag that does not match will + be ignored. + + The syntax of the regular expressions accepted is the syntax + accepted by RE2 and described at + https://github.com/google/re2/wiki/Syntax. + + At most one of these can be specified: + + --build-config=PATH + Path to a YAML or JSON file containing the build configuration in + the repository. + + For more details, see: + https://cloud.google.com/cloud-build/docs/build-config + + --inline-config=PATH + Local path to a YAML or JSON file containing a build + configuration. + + Dockerfile build configuration flags + + --dockerfile=DOCKERFILE + Path of Dockerfile to use for builds in the repository. + + If specified, a build config will be generated to run docker + build using the specified file. + + The filename is relative to the Dockerfile directory. + + This flag argument must be specified if any of the other + arguments in this group are specified. + + --dockerfile-image=DOCKERFILE_IMAGE + Docker image name to build. + + This flag argument must be specified if any of the other + arguments in this group are specified. + + --dockerfile-dir=DOCKERFILE_DIR + Location of the directory containing the Dockerfile in the + repository. + + The directory will also be used as the Docker build context. + + At most one of these can be specified: + + --clear-substitutions + Clear existing substitutions. + + --remove-substitutions=[KEY,...] + Remove existing substitutions if present. + + --update-substitutions=[KEY=VALUE,...] + Update or add to existing substitutions. Substitutions are + parameters to be substituted or add in the build specification. + + For example (using some nonsensical substitution keys; all keys + must begin with an underscore): + + $ gcloud builds triggers update ... + --update-substitutions _FAVORITE_COLOR=blue,_NUM_CANDIES=10 + + This will add the provided substitutions to the existing + substitutions and results in a build where every occurrence of + ${_FAVORITE_COLOR} in certain fields is replaced by "blue", and + similarly for ${_NUM_CANDIES} and "10". + + Only the following built-in variables can be specified with the + --substitutions flag: REPO_NAME, BRANCH_NAME, TAG_NAME, + REVISION_ID, COMMIT_SHA, SHORT_SHA. + + For more details, see: + https://cloud.google.com/build/docs/build-config-file-schema#substitutions + +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 builds triggers update cloud-source-repositories + + $ gcloud beta builds triggers update cloud-source-repositories + diff --git a/gcloud/builds/triggers/update/github b/gcloud/builds/triggers/update/github new file mode 100644 index 000000000..8ed114851 --- /dev/null +++ b/gcloud/builds/triggers/update/github @@ -0,0 +1,267 @@ +NAME + gcloud builds triggers update github - update GitHub trigger used by Google + Cloud Build + +SYNOPSIS + gcloud builds triggers update github (TRIGGER : --region=REGION) + (--trigger-config=PATH | --description=DESCRIPTION + --ignored-files=[GLOB,...] --include-logs-with-status + --included-files=[GLOB,...] --[no-]require-approval + --service-account=SERVICE_ACCOUNT --branch-pattern=REGEX + | --tag-pattern=REGEX | --comment-control=COMMENT_CONTROL; + default="COMMENTS_ENABLED" + --pull-request-pattern=REGEX --build-config=PATH + | --inline-config=PATH + | [--dockerfile=DOCKERFILE --dockerfile-image=DOCKERFILE_IMAGE + : --dockerfile-dir=DOCKERFILE_DIR] --clear-substitutions + | --remove-substitutions=[KEY,...] + | --update-substitutions=[KEY=VALUE,...] --repository=REPOSITORY + | --enterprise-config=ENTERPRISE_CONFIG + --repo-name=REPO_NAME --repo-owner=REPO_OWNER) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Update GitHub trigger used by Google Cloud Build. + +EXAMPLES + To update the branch pattern of the trigger: + + $ gcloud builds triggers update github my-trigger \ + --branch-pattern=".*" + + To update the build config of the trigger: + + $ gcloud builds triggers update github my-trigger \ + --build-config="cloudbuild.yaml" + + To update the substitutions of the trigger: + + $ gcloud builds triggers update github my-trigger \ + --update-substitutions=_REPO_NAME=my-repo,_BRANCH_NAME=master + +POSITIONAL ARGUMENTS + Trigger resource - Build Trigger. 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 TRIGGER 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. + + TRIGGER + ID of the trigger or fully qualified identifier for the trigger. + + To set the trigger attribute: + ▸ provide the argument TRIGGER 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 location for the trigger. + + To set the region attribute: + ▸ provide the argument TRIGGER on the command line with a fully + specified name; + ▸ provide the argument --region on the command line; + ▸ set the property builds/region. + +REQUIRED FLAGS + Exactly one of these must be specified: + + --trigger-config=PATH + Path to Build Trigger config file (JSON or YAML format). For more + details, see + https://cloud.google.com/cloud-build/docs/api/reference/rest/v1/projects.triggers#BuildTrigger + + Flag based trigger configuration + + --description=DESCRIPTION + Build trigger description. + + --ignored-files=[GLOB,...] + Glob filter. Changes only affecting ignored files won't trigger + builds. + + --include-logs-with-status + Build logs will be sent back to GitHub as part of the checkrun + result. + + --included-files=[GLOB,...] + Glob filter. Changes affecting at least one included file will + trigger builds. + + --[no-]require-approval + Require manual approval for triggered builds. Use + --require-approval to enable and --no-require-approval to disable. + + --service-account=SERVICE_ACCOUNT + The service account used for all user-controlled operations + including UpdateBuildTrigger, RunBuildTrigger, CreateBuild, and + CancelBuild. If no service account is set, then the standard Cloud + Build service account ([PROJECT_NUM]@system.gserviceaccount.com) is + used instead. Format: + projects/{PROJECT_ID}/serviceAccounts/{ACCOUNT_ID_OR_EMAIL}. + + At most one of these can be specified: + + --branch-pattern=REGEX + A regular expression specifying which git branches to match. + + This pattern is used as a regular expression search for any + incoming pushes. For example, --branch-pattern=foo will match + "foo", "foobar", and "barfoo". Events on a branch that does not + match will be ignored. + + The syntax of the regular expressions accepted is the syntax + accepted by RE2 and described at + https://github.com/google/re2/wiki/Syntax. + + --tag-pattern=REGEX + A regular expression specifying which git tags to match. + + This pattern is used as a regular expression search for any + incoming pushes. For example, --tag-pattern=foo will match "foo", + "foobar", and "barfoo". Events on a tag that does not match will + be ignored. + + The syntax of the regular expressions accepted is the syntax + accepted by RE2 and described at + https://github.com/google/re2/wiki/Syntax. + + Pull Request settings + + --comment-control=COMMENT_CONTROL; default="COMMENTS_ENABLED" + Require a repository collaborator or owner to comment '/gcbrun' + on a pull request before running the build. COMMENT_CONTROL + must be one of: + + COMMENTS_DISABLED + Do not require comments on Pull Requests before builds are + triggered. + COMMENTS_ENABLED + Enforce that repository owners or collaborators must + comment on Pull Requests before builds are triggered. + COMMENTS_ENABLED_FOR_EXTERNAL_CONTRIBUTORS_ONLY + Enforce that repository owners or collaborators must + comment on external contributors' Pull Requests before + builds are triggered. + + --pull-request-pattern=REGEX + A regular expression specifying which base git branch to match + for pull request events. + + This pattern is used as a regex search for the base branch (the + branch you are trying to merge into) for pull request updates. + For example, --pull-request-pattern=foo will match "foo", + "foobar", and "barfoo". + + The syntax of the regular expressions accepted is the syntax + accepted by RE2 and described at + https://github.com/google/re2/wiki/Syntax. + + At most one of these can be specified: + + --build-config=PATH + Path to a YAML or JSON file containing the build configuration in + the repository. + + For more details, see: + https://cloud.google.com/cloud-build/docs/build-config + + --inline-config=PATH + Local path to a YAML or JSON file containing a build + configuration. + + Dockerfile build configuration flags + + --dockerfile=DOCKERFILE + Path of Dockerfile to use for builds in the repository. + + If specified, a build config will be generated to run docker + build using the specified file. + + The filename is relative to the Dockerfile directory. + + This flag argument must be specified if any of the other + arguments in this group are specified. + + --dockerfile-image=DOCKERFILE_IMAGE + Docker image name to build. + + This flag argument must be specified if any of the other + arguments in this group are specified. + + --dockerfile-dir=DOCKERFILE_DIR + Location of the directory containing the Dockerfile in the + repository. + + The directory will also be used as the Docker build context. + + At most one of these can be specified: + + --clear-substitutions + Clear existing substitutions. + + --remove-substitutions=[KEY,...] + Remove existing substitutions if present. + + --update-substitutions=[KEY=VALUE,...] + Update or add to existing substitutions. Substitutions are + parameters to be substituted or add in the build specification. + + For example (using some nonsensical substitution keys; all keys + must begin with an underscore): + + $ gcloud builds triggers update ... + --update-substitutions _FAVORITE_COLOR=blue,_NUM_CANDIES=10 + + This will add the provided substitutions to the existing + substitutions and results in a build where every occurrence of + ${_FAVORITE_COLOR} in certain fields is replaced by "blue", and + similarly for ${_NUM_CANDIES} and "10". + + Only the following built-in variables can be specified with the + --substitutions flag: REPO_NAME, BRANCH_NAME, TAG_NAME, + REVISION_ID, COMMIT_SHA, SHORT_SHA. + + For more details, see: + https://cloud.google.com/build/docs/build-config-file-schema#substitutions + + At most one of these can be specified: + + --repository=REPOSITORY + Repository resource (2nd gen) to use, in the format + "projects/*/locations/*/connections/*/repositories/". + + --enterprise-config=ENTERPRISE_CONFIG + Resource name of the GitHub Enterprise config that should be + applied to this installation. + + For example: + "projects/{$project_id}/locations/{$location_id}/githubEnterpriseConfigs/{$config_id} + + --repo-name=REPO_NAME + Name of the GitHub Repository. + + --repo-owner=REPO_OWNER + Owner of the GitHub Repository. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + These variants are also available: + + $ gcloud alpha builds triggers update github + + $ gcloud beta builds triggers update github + diff --git a/gcloud/builds/triggers/update/gitlab b/gcloud/builds/triggers/update/gitlab new file mode 100644 index 000000000..53022e526 --- /dev/null +++ b/gcloud/builds/triggers/update/gitlab @@ -0,0 +1,251 @@ +NAME + gcloud builds triggers update gitlab - updates GitLab trigger used by + Google Cloud Build + +SYNOPSIS + gcloud builds triggers update gitlab (TRIGGER : --region=REGION) + (--trigger-config=PATH | --description=DESCRIPTION + --ignored-files=[GLOB,...] --included-files=[GLOB,...] + --repository=REPOSITORY --[no-]require-approval + --service-account=SERVICE_ACCOUNT --branch-pattern=REGEX + | --tag-pattern=REGEX | --comment-control=COMMENT_CONTROL + --pull-request-pattern=REGEX --build-config=PATH + | --inline-config=PATH + | [--dockerfile=DOCKERFILE --dockerfile-image=DOCKERFILE_IMAGE + : --dockerfile-dir=DOCKERFILE_DIR] --clear-substitutions + | --remove-substitutions=[KEY,...] + | --update-substitutions=[KEY=VALUE,...]) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Updates GitLab trigger used by Google Cloud Build. + +EXAMPLES + To update the branch pattern of the trigger: + + $ gcloud builds triggers update gitlab my-trigger \ + --branch-pattern=".*" + + To update the build config of the trigger: + + $ gcloud builds triggers update gitlab my-trigger \ + --build-config="cloudbuild.yaml" + + To update the substitutions of the trigger: + + $ gcloud builds triggers update gitlab my-trigger \ + --update-substitutions=_REPO_NAME=my-repo,_BRANCH_NAME=master + + To update the 2nd-gen repository resource of the trigger: + + $ gcloud builds triggers update gitlab my-trigger \ + --repository=projects/my-project/locations/us-west1/\ + connections/my-conn/repositories/my-repo + +POSITIONAL ARGUMENTS + Trigger resource - Build Trigger. 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 TRIGGER 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. + + TRIGGER + ID of the trigger or fully qualified identifier for the trigger. + + To set the trigger attribute: + ▸ provide the argument TRIGGER 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 location for the trigger. + + To set the region attribute: + ▸ provide the argument TRIGGER on the command line with a fully + specified name; + ▸ provide the argument --region on the command line; + ▸ set the property builds/region. + +REQUIRED FLAGS + Exactly one of these must be specified: + + --trigger-config=PATH + Path to Build Trigger config file (JSON or YAML format). For more + details, see + https://cloud.google.com/cloud-build/docs/api/reference/rest/v1/projects.triggers#BuildTrigger + + Flag based trigger configuration + + --description=DESCRIPTION + Build trigger description. + + --ignored-files=[GLOB,...] + Glob filter. Changes only affecting ignored files won't trigger + builds. + + --included-files=[GLOB,...] + Glob filter. Changes affecting at least one included file will + trigger builds. + + --repository=REPOSITORY + Repository resource (2nd gen) to use, in the format + "projects/*/locations/*/connections/*/repositories/". + + --[no-]require-approval + Require manual approval for triggered builds. Use + --require-approval to enable and --no-require-approval to disable. + + --service-account=SERVICE_ACCOUNT + The service account used for all user-controlled operations + including UpdateBuildTrigger, RunBuildTrigger, CreateBuild, and + CancelBuild. If no service account is set, then the standard Cloud + Build service account ([PROJECT_NUM]@system.gserviceaccount.com) is + used instead. Format: + projects/{PROJECT_ID}/serviceAccounts/{ACCOUNT_ID_OR_EMAIL}. + + At most one of these can be specified: + + --branch-pattern=REGEX + A regular expression specifying which git branches to match. + + This pattern is used as a regular expression search for any + incoming pushes. For example, --branch-pattern=foo will match + "foo", "foobar", and "barfoo". Events on a branch that does not + match will be ignored. + + The syntax of the regular expressions accepted is the syntax + accepted by RE2 and described at + https://github.com/google/re2/wiki/Syntax. + + --tag-pattern=REGEX + A regular expression specifying which git tags to match. + + This pattern is used as a regular expression search for any + incoming pushes. For example, --tag-pattern=foo will match "foo", + "foobar", and "barfoo". Events on a tag that does not match will + be ignored. + + The syntax of the regular expressions accepted is the syntax + accepted by RE2 and described at + https://github.com/google/re2/wiki/Syntax. + + Pull Request settings + + --comment-control=COMMENT_CONTROL + Require a repository collaborator or owner to comment '/gcbrun' + on a pull request before running the build. COMMENT_CONTROL + must be one of: + + COMMENTS_DISABLED + Do not require comments on Pull Requests before builds are + triggered. + COMMENTS_ENABLED + Enforce that repository owners or collaborators must + comment on Pull Requests before builds are triggered. + COMMENTS_ENABLED_FOR_EXTERNAL_CONTRIBUTORS_ONLY + Enforce that repository owners or collaborators must + comment on external contributors' Pull Requests before + builds are triggered. + + --pull-request-pattern=REGEX + A regular expression specifying which base git branch to match + for pull request events. + + This pattern is used as a regular expression search for the + base branch (the branch you are trying to merge into) for pull + request updates. For example, --pull-request-pattern=foo will + match "foo", "foobar", and "barfoo". + + The syntax of the regular expressions accepted is the syntax + accepted by RE2 and described at + https://github.com/google/re2/wiki/Syntax. + + At most one of these can be specified: + + --build-config=PATH + Path to a YAML or JSON file containing the build configuration in + the repository. + + For more details, see: + https://cloud.google.com/cloud-build/docs/build-config + + --inline-config=PATH + Local path to a YAML or JSON file containing a build + configuration. + + Dockerfile build configuration flags + + --dockerfile=DOCKERFILE + Path of Dockerfile to use for builds in the repository. + + If specified, a build config will be generated to run docker + build using the specified file. + + The filename is relative to the Dockerfile directory. + + This flag argument must be specified if any of the other + arguments in this group are specified. + + --dockerfile-image=DOCKERFILE_IMAGE + Docker image name to build. + + This flag argument must be specified if any of the other + arguments in this group are specified. + + --dockerfile-dir=DOCKERFILE_DIR + Location of the directory containing the Dockerfile in the + repository. + + The directory will also be used as the Docker build context. + + At most one of these can be specified: + + --clear-substitutions + Clear existing substitutions. + + --remove-substitutions=[KEY,...] + Remove existing substitutions if present. + + --update-substitutions=[KEY=VALUE,...] + Update or add to existing substitutions. Substitutions are + parameters to be substituted or add in the build specification. + + For example (using some nonsensical substitution keys; all keys + must begin with an underscore): + + $ gcloud builds triggers update ... + --update-substitutions _FAVORITE_COLOR=blue,_NUM_CANDIES=10 + + This will add the provided substitutions to the existing + substitutions and results in a build where every occurrence of + ${_FAVORITE_COLOR} in certain fields is replaced by "blue", and + similarly for ${_NUM_CANDIES} and "10". + + Only the following built-in variables can be specified with the + --substitutions flag: REPO_NAME, BRANCH_NAME, TAG_NAME, + REVISION_ID, COMMIT_SHA, SHORT_SHA. + + For more details, see: + https://cloud.google.com/build/docs/build-config-file-schema#substitutions + +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 builds triggers update gitlab + + $ gcloud beta builds triggers update gitlab + diff --git a/gcloud/builds/triggers/update/help b/gcloud/builds/triggers/update/help new file mode 100644 index 000000000..64e5b8e97 --- /dev/null +++ b/gcloud/builds/triggers/update/help @@ -0,0 +1,45 @@ +NAME + gcloud builds triggers update - update Triggers in Google Cloud Build + +SYNOPSIS + gcloud builds triggers update COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Update Triggers in Google Cloud Build. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + bitbucketserver + Updates Bitbucket Server trigger used by Google Cloud Build. + + cloud-source-repositories + Updates Cloud Source Repositories trigger used by Google Cloud Build. + + github + Update GitHub trigger used by Google Cloud Build. + + gitlab + Updates GitLab trigger used by Google Cloud Build. + + manual + Updates a manual trigger used by Google Cloud Build. + + pubsub + Update a Pub/Sub trigger used by Google Cloud Build. + + webhook + Update a Webhook trigger used by Google Cloud Build. + +NOTES + These variants are also available: + + $ gcloud alpha builds triggers update + + $ gcloud beta builds triggers update + diff --git a/gcloud/builds/triggers/update/manual b/gcloud/builds/triggers/update/manual new file mode 100644 index 000000000..ccb5a8b47 --- /dev/null +++ b/gcloud/builds/triggers/update/manual @@ -0,0 +1,225 @@ +NAME + gcloud builds triggers update manual - updates a manual trigger used by + Google Cloud Build + +SYNOPSIS + gcloud builds triggers update manual (TRIGGER : --region=REGION) + (--trigger-config=PATH | --description=DESCRIPTION + --[no-]require-approval + --service-account=SERVICE_ACCOUNT --clear-substitutions + | --remove-substitutions=[KEY,...] + | --update-substitutions=[KEY=VALUE,...] --inline-config=PATH + | [--dockerfile=DOCKERFILE : --dockerfile-dir=DOCKERFILE_DIR + --dockerfile-image=DOCKERFILE_IMAGE] + | --git-file-source-branch=GIT_FILE_SOURCE_BRANCH + | --git-file-source-tag=GIT_FILE_SOURCE_TAG + --git-file-source-github-enterprise-config=GIT_FILE_SOURCE_GITHUB_ENTERPRISE_CONFIG --git-file-source-path=PATH --git-file-source-repo-type=GIT_FILE_SOURCE_REPO_TYPE --git-file-source-uri=URL --source-to-build-branch=SOURCE_TO_BUILD_BRANCH | --source-to-build-tag=SOURCE_TO_BUILD_TAG --source-to-build-github-enterprise-config=SOURCE_TO_BUILD_GITHUB_ENTERPRISE_CONFIG --source-to-build-repo-type=SOURCE_TO_BUILD_REPO_TYPE --source-to-build-uri=SOURCE_TO_BUILD_URI) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Updates a manual trigger used by Google Cloud Build. + +EXAMPLES + To update the branch from which the trigger clones: + + $ gcloud builds triggers update manual my-trigger \ + --source-to-build-branch=my-branch + +POSITIONAL ARGUMENTS + Trigger resource - Build Trigger. 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 TRIGGER 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. + + TRIGGER + ID of the trigger or fully qualified identifier for the trigger. + + To set the trigger attribute: + ▸ provide the argument TRIGGER 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 location for the trigger. + + To set the region attribute: + ▸ provide the argument TRIGGER on the command line with a fully + specified name; + ▸ provide the argument --region on the command line; + ▸ set the property builds/region. + +REQUIRED FLAGS + Exactly one of these must be specified: + + --trigger-config=PATH + Path to Build Trigger config file (JSON or YAML format). For more + details, see + https://cloud.google.com/cloud-build/docs/api/reference/rest/v1/projects.triggers#BuildTrigger + + Flag based trigger configuration + + --description=DESCRIPTION + Build trigger description. + + --[no-]require-approval + Require manual approval for triggered builds. Use + --require-approval to enable and --no-require-approval to disable. + + --service-account=SERVICE_ACCOUNT + The service account used for all user-controlled operations + including UpdateBuildTrigger, RunBuildTrigger, CreateBuild, and + CancelBuild. If no service account is set, then the standard Cloud + Build service account ([PROJECT_NUM]@system.gserviceaccount.com) is + used instead. Format: + projects/{PROJECT_ID}/serviceAccounts/{ACCOUNT_ID_OR_EMAIL}. + + At most one of these can be specified: + + --clear-substitutions + Clear existing substitutions. + + --remove-substitutions=[KEY,...] + Remove existing substitutions if present. + + --update-substitutions=[KEY=VALUE,...] + Update or add to existing substitutions. Substitutions are + parameters to be substituted or add in the build specification. + + For example (using some nonsensical substitution keys; all keys + must begin with an underscore): + + $ gcloud builds triggers update ... + --update-substitutions _FAVORITE_COLOR=blue,_NUM_CANDIES=10 + + This will add the provided substitutions to the existing + substitutions and results in a build where every occurrence of + ${_FAVORITE_COLOR} in certain fields is replaced by "blue", and + similarly for ${_NUM_CANDIES} and "10". + + Only the following built-in variables can be specified with the + --substitutions flag: REPO_NAME, BRANCH_NAME, TAG_NAME, + REVISION_ID, COMMIT_SHA, SHORT_SHA. + + For more details, see: + https://cloud.google.com/build/docs/build-config-file-schema#substitutions + + At most one of these can be specified: + + --inline-config=PATH + Local path to a YAML or JSON file containing a build + configuration. + + Dockerfile build configuration flags + + --dockerfile=DOCKERFILE + Path of Dockerfile to use for builds in the repository. + + If specified, a build config will be generated to run docker + build using the specified file. + + The filename is relative to the Dockerfile directory. + + This flag argument must be specified if any of the other + arguments in this group are specified. + + --dockerfile-dir=DOCKERFILE_DIR + Location of the directory containing the Dockerfile in the + repository. + + The directory will also be used as the Docker build context. + + --dockerfile-image=DOCKERFILE_IMAGE + Docker image name to build. + + If not specified, + gcr.io/PROJECT/github.com/REPO_OWNER/REPO_NAME:$COMMIT_SHA will + be used. + + Use a build configuration (cloudbuild.yaml) file for building + multiple images in a single trigger. + + Build file source flags + + At most one of these can be specified: + + --git-file-source-branch=GIT_FILE_SOURCE_BRANCH + The branch of the repository to clone when trigger is + invoked. + + --git-file-source-tag=GIT_FILE_SOURCE_TAG + The tag of the repository to clone when trigger is invoked. + + At most one of these can be specified: + + --git-file-source-github-enterprise-config=GIT_FILE_SOURCE_GITHUB_ENTERPRISE_CONFIG + The resource name of the GitHub Enterprise config that should + be applied to this source. + + --git-file-source-path=PATH + The file in the repository to clone when trigger is invoked. + + --git-file-source-repo-type=GIT_FILE_SOURCE_REPO_TYPE + The type of the repository to clone when trigger is invoked. + + This flag argument must be specified if any of the other + arguments in this group are specified. + + --git-file-source-uri=URL + The URI of the repository to clone when trigger is invoked. + + 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: + + --source-to-build-branch=SOURCE_TO_BUILD_BRANCH + Branch to build. + + --source-to-build-tag=SOURCE_TO_BUILD_TAG + Tag to build. + + At most one of these can be specified: + + --source-to-build-github-enterprise-config=SOURCE_TO_BUILD_GITHUB_ENTERPRISE_CONFIG + The resource name of the GitHub Enterprise config that should be + applied to this source (1st gen). Format: + projects/{project}/locations/{location}/githubEnterpriseConfigs/{id} + or projects/{project}/githubEnterpriseConfigs/{id} + + --source-to-build-repo-type=SOURCE_TO_BUILD_REPO_TYPE + Type of the repository (1st gen). Currently only GitHub and Cloud + Source Repository types are supported. + + This flag argument must be specified if any of the other + arguments in this group are specified. + + --source-to-build-uri=SOURCE_TO_BUILD_URI + The URI of the repository that should be applied to this source + (1st gen). + + 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 builds triggers update manual + + $ gcloud beta builds triggers update manual + diff --git a/gcloud/builds/triggers/update/pubsub b/gcloud/builds/triggers/update/pubsub new file mode 100644 index 000000000..4dc3ceb77 --- /dev/null +++ b/gcloud/builds/triggers/update/pubsub @@ -0,0 +1,242 @@ +NAME + gcloud builds triggers update pubsub - update a Pub/Sub trigger used by + Google Cloud Build + +SYNOPSIS + gcloud builds triggers update pubsub (TRIGGER : --region=REGION) + (--trigger-config=PATH | --description=DESCRIPTION + --[no-]require-approval --service-account=SERVICE_ACCOUNT + --subscription-filter=SUBSCRIPTION_FILTER + --topic=TOPIC --clear-substitutions + | --remove-substitutions=[KEY,...] + | --update-substitutions=[KEY=VALUE,...] --inline-config=PATH + | [--dockerfile=DOCKERFILE : --dockerfile-dir=DOCKERFILE_DIR + --dockerfile-image=DOCKERFILE_IMAGE] + | --git-file-source-branch=GIT_FILE_SOURCE_BRANCH + | --git-file-source-tag=GIT_FILE_SOURCE_TAG + --git-file-source-github-enterprise-config=GIT_FILE_SOURCE_GITHUB_ENTERPRISE_CONFIG --git-file-source-path=PATH --git-file-source-repo-type=GIT_FILE_SOURCE_REPO_TYPE --git-file-source-uri=URL --source-to-build-branch=SOURCE_TO_BUILD_BRANCH | --source-to-build-tag=SOURCE_TO_BUILD_TAG --source-to-build-github-enterprise-config=SOURCE_TO_BUILD_GITHUB_ENTERPRISE_CONFIG --source-to-build-repo-type=SOURCE_TO_BUILD_REPO_TYPE --source-to-build-uri=SOURCE_TO_BUILD_URI) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Update a Pub/Sub trigger used by Google Cloud Build. + +EXAMPLES + To update the branch from which the trigger clones: + + $ gcloud builds triggers update pubsub my-trigger \ + --source-to-build-branch=my-branch + + To update the topic: + + $ gcloud builds triggers update pubsub my-trigger \ + --topic=projects/my-project/topics/my-topic + + To update the substitutions of the trigger: $ gcloud builds triggers update pubsub my-trigger \ + --update-substitutions=_REPO_NAME=my-repo,_BRANCH_NAME=master + +POSITIONAL ARGUMENTS + Trigger resource - Build Trigger. 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 TRIGGER 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. + + TRIGGER + ID of the trigger or fully qualified identifier for the trigger. + + To set the trigger attribute: + ▸ provide the argument TRIGGER 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 location for the trigger. + + To set the region attribute: + ▸ provide the argument TRIGGER on the command line with a fully + specified name; + ▸ provide the argument --region on the command line; + ▸ set the property builds/region. + +REQUIRED FLAGS + Exactly one of these must be specified: + + --trigger-config=PATH + Path to Build Trigger config file (JSON or YAML format). For more + details, see + https://cloud.google.com/cloud-build/docs/api/reference/rest/v1/projects.triggers#BuildTrigger + + Flag based trigger configuration + + --description=DESCRIPTION + Build trigger description. + + --[no-]require-approval + Require manual approval for triggered builds. Use + --require-approval to enable and --no-require-approval to disable. + + --service-account=SERVICE_ACCOUNT + The service account used for all user-controlled operations + including UpdateBuildTrigger, RunBuildTrigger, CreateBuild, and + CancelBuild. If no service account is set, then the standard Cloud + Build service account ([PROJECT_NUM]@system.gserviceaccount.com) is + used instead. Format: + projects/{PROJECT_ID}/serviceAccounts/{ACCOUNT_ID_OR_EMAIL}. + + --subscription-filter=SUBSCRIPTION_FILTER + CEL filter expression for the trigger. See + https://cloud.google.com/build/docs/filter-build-events-using-cel + for more details. + + --topic=TOPIC + The topic to which this trigger should subscribe. + + At most one of these can be specified: + + --clear-substitutions + Clear existing substitutions. + + --remove-substitutions=[KEY,...] + Remove existing substitutions if present. + + --update-substitutions=[KEY=VALUE,...] + Update or add to existing substitutions. Substitutions are + parameters to be substituted or add in the build specification. + + For example (using some nonsensical substitution keys; all keys + must begin with an underscore): + + $ gcloud builds triggers update ... + --update-substitutions _FAVORITE_COLOR=blue,_NUM_CANDIES=10 + + This will add the provided substitutions to the existing + substitutions and results in a build where every occurrence of + ${_FAVORITE_COLOR} in certain fields is replaced by "blue", and + similarly for ${_NUM_CANDIES} and "10". + + Only the following built-in variables can be specified with the + --substitutions flag: REPO_NAME, BRANCH_NAME, TAG_NAME, + REVISION_ID, COMMIT_SHA, SHORT_SHA. + + For more details, see: + https://cloud.google.com/build/docs/build-config-file-schema#substitutions + + At most one of these can be specified: + + --inline-config=PATH + Local path to a YAML or JSON file containing a build + configuration. + + Dockerfile build configuration flags + + --dockerfile=DOCKERFILE + Path of Dockerfile to use for builds in the repository. + + If specified, a build config will be generated to run docker + build using the specified file. + + The filename is relative to the Dockerfile directory. + + This flag argument must be specified if any of the other + arguments in this group are specified. + + --dockerfile-dir=DOCKERFILE_DIR + Location of the directory containing the Dockerfile in the + repository. + + The directory will also be used as the Docker build context. + + --dockerfile-image=DOCKERFILE_IMAGE + Docker image name to build. + + If not specified, + gcr.io/PROJECT/github.com/REPO_OWNER/REPO_NAME:$COMMIT_SHA will + be used. + + Use a build configuration (cloudbuild.yaml) file for building + multiple images in a single trigger. + + Build file source flags + + At most one of these can be specified: + + --git-file-source-branch=GIT_FILE_SOURCE_BRANCH + The branch of the repository to clone when trigger is + invoked. + + --git-file-source-tag=GIT_FILE_SOURCE_TAG + The tag of the repository to clone when trigger is invoked. + + At most one of these can be specified: + + --git-file-source-github-enterprise-config=GIT_FILE_SOURCE_GITHUB_ENTERPRISE_CONFIG + The resource name of the GitHub Enterprise config that should + be applied to this source. + + --git-file-source-path=PATH + The file in the repository to clone when trigger is invoked. + + --git-file-source-repo-type=GIT_FILE_SOURCE_REPO_TYPE + The type of the repository to clone when trigger is invoked. + + This flag argument must be specified if any of the other + arguments in this group are specified. + + --git-file-source-uri=URL + The URI of the repository to clone when trigger is invoked. + + 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: + + --source-to-build-branch=SOURCE_TO_BUILD_BRANCH + Branch to build. + + --source-to-build-tag=SOURCE_TO_BUILD_TAG + Tag to build. + + At most one of these can be specified: + + --source-to-build-github-enterprise-config=SOURCE_TO_BUILD_GITHUB_ENTERPRISE_CONFIG + The resource name of the GitHub Enterprise config that should be + applied to this source (1st gen). Format: + projects/{project}/locations/{location}/githubEnterpriseConfigs/{id} + or projects/{project}/githubEnterpriseConfigs/{id} + + --source-to-build-repo-type=SOURCE_TO_BUILD_REPO_TYPE + Type of the repository (1st gen). Currently only GitHub and Cloud + Source Repository types are supported. + + This flag argument must be specified if any of the other + arguments in this group are specified. + + --source-to-build-uri=SOURCE_TO_BUILD_URI + The URI of the repository that should be applied to this source + (1st gen). + + 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 builds triggers update pubsub + + $ gcloud beta builds triggers update pubsub + diff --git a/gcloud/builds/triggers/update/webhook b/gcloud/builds/triggers/update/webhook new file mode 100644 index 000000000..a55e84ddd --- /dev/null +++ b/gcloud/builds/triggers/update/webhook @@ -0,0 +1,244 @@ +NAME + gcloud builds triggers update webhook - update a Webhook trigger used by + Google Cloud Build + +SYNOPSIS + gcloud builds triggers update webhook (TRIGGER : --region=REGION) + (--trigger-config=PATH | --description=DESCRIPTION + --[no-]require-approval --secret=SECRET + --service-account=SERVICE_ACCOUNT + --subscription-filter=SUBSCRIPTION_FILTER --clear-substitutions + | --remove-substitutions=[KEY,...] + | --update-substitutions=[KEY=VALUE,...] --inline-config=PATH + | [--dockerfile=DOCKERFILE : --dockerfile-dir=DOCKERFILE_DIR + --dockerfile-image=DOCKERFILE_IMAGE] + | --git-file-source-branch=GIT_FILE_SOURCE_BRANCH + | --git-file-source-tag=GIT_FILE_SOURCE_TAG + --git-file-source-github-enterprise-config=GIT_FILE_SOURCE_GITHUB_ENTERPRISE_CONFIG --git-file-source-path=PATH --git-file-source-repo-type=GIT_FILE_SOURCE_REPO_TYPE --git-file-source-uri=URL --source-to-build-branch=SOURCE_TO_BUILD_BRANCH | --source-to-build-tag=SOURCE_TO_BUILD_TAG --source-to-build-github-enterprise-config=SOURCE_TO_BUILD_GITHUB_ENTERPRISE_CONFIG --source-to-build-repo-type=SOURCE_TO_BUILD_REPO_TYPE --source-to-build-uri=SOURCE_TO_BUILD_URI) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Update a Webhook trigger used by Google Cloud Build. + +EXAMPLES + To update the branch from which the trigger clones: + + $ gcloud builds triggers update webhook my-webhook-trigger \ + --source-to-build-branch=my-branch + + To update the webhook secret: + + $ gcloud builds triggers update webhook my-webhook-trigger \ + --secret=projects/my-project/secrets/my-secret/versions/2 + + To update the substitutions of the trigger: $ gcloud builds triggers update webhook my-trigger \ + --update-substitutions=_REPO_NAME=my-repo,_BRANCH_NAME=master + +POSITIONAL ARGUMENTS + Trigger resource - Build Trigger. 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 TRIGGER 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. + + TRIGGER + ID of the trigger or fully qualified identifier for the trigger. + + To set the trigger attribute: + ▸ provide the argument TRIGGER 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 location for the trigger. + + To set the region attribute: + ▸ provide the argument TRIGGER on the command line with a fully + specified name; + ▸ provide the argument --region on the command line; + ▸ set the property builds/region. + +REQUIRED FLAGS + Exactly one of these must be specified: + + --trigger-config=PATH + Path to Build Trigger config file (JSON or YAML format). For more + details, see + https://cloud.google.com/cloud-build/docs/api/reference/rest/v1/projects.triggers#BuildTrigger + + Flag based trigger configuration + + --description=DESCRIPTION + Build trigger description. + + --[no-]require-approval + Require manual approval for triggered builds. Use + --require-approval to enable and --no-require-approval to disable. + + --secret=SECRET + The full path of the secret version required to validate webhook + requests against this trigger. For example, + projects/my-project/secrets/my-secret/versions/1. + + --service-account=SERVICE_ACCOUNT + The service account used for all user-controlled operations + including UpdateBuildTrigger, RunBuildTrigger, CreateBuild, and + CancelBuild. If no service account is set, then the standard Cloud + Build service account ([PROJECT_NUM]@system.gserviceaccount.com) is + used instead. Format: + projects/{PROJECT_ID}/serviceAccounts/{ACCOUNT_ID_OR_EMAIL}. + + --subscription-filter=SUBSCRIPTION_FILTER + CEL filter expression for the trigger. See + https://cloud.google.com/build/docs/filter-build-events-using-cel + for more details. + + At most one of these can be specified: + + --clear-substitutions + Clear existing substitutions. + + --remove-substitutions=[KEY,...] + Remove existing substitutions if present. + + --update-substitutions=[KEY=VALUE,...] + Update or add to existing substitutions. Substitutions are + parameters to be substituted or add in the build specification. + + For example (using some nonsensical substitution keys; all keys + must begin with an underscore): + + $ gcloud builds triggers update ... + --update-substitutions _FAVORITE_COLOR=blue,_NUM_CANDIES=10 + + This will add the provided substitutions to the existing + substitutions and results in a build where every occurrence of + ${_FAVORITE_COLOR} in certain fields is replaced by "blue", and + similarly for ${_NUM_CANDIES} and "10". + + Only the following built-in variables can be specified with the + --substitutions flag: REPO_NAME, BRANCH_NAME, TAG_NAME, + REVISION_ID, COMMIT_SHA, SHORT_SHA. + + For more details, see: + https://cloud.google.com/build/docs/build-config-file-schema#substitutions + + At most one of these can be specified: + + --inline-config=PATH + Local path to a YAML or JSON file containing a build + configuration. + + Dockerfile build configuration flags + + --dockerfile=DOCKERFILE + Path of Dockerfile to use for builds in the repository. + + If specified, a build config will be generated to run docker + build using the specified file. + + The filename is relative to the Dockerfile directory. + + This flag argument must be specified if any of the other + arguments in this group are specified. + + --dockerfile-dir=DOCKERFILE_DIR + Location of the directory containing the Dockerfile in the + repository. + + The directory will also be used as the Docker build context. + + --dockerfile-image=DOCKERFILE_IMAGE + Docker image name to build. + + If not specified, + gcr.io/PROJECT/github.com/REPO_OWNER/REPO_NAME:$COMMIT_SHA will + be used. + + Use a build configuration (cloudbuild.yaml) file for building + multiple images in a single trigger. + + Build file source flags + + At most one of these can be specified: + + --git-file-source-branch=GIT_FILE_SOURCE_BRANCH + The branch of the repository to clone when trigger is + invoked. + + --git-file-source-tag=GIT_FILE_SOURCE_TAG + The tag of the repository to clone when trigger is invoked. + + At most one of these can be specified: + + --git-file-source-github-enterprise-config=GIT_FILE_SOURCE_GITHUB_ENTERPRISE_CONFIG + The resource name of the GitHub Enterprise config that should + be applied to this source. + + --git-file-source-path=PATH + The file in the repository to clone when trigger is invoked. + + --git-file-source-repo-type=GIT_FILE_SOURCE_REPO_TYPE + The type of the repository to clone when trigger is invoked. + + This flag argument must be specified if any of the other + arguments in this group are specified. + + --git-file-source-uri=URL + The URI of the repository to clone when trigger is invoked. + + 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: + + --source-to-build-branch=SOURCE_TO_BUILD_BRANCH + Branch to build. + + --source-to-build-tag=SOURCE_TO_BUILD_TAG + Tag to build. + + At most one of these can be specified: + + --source-to-build-github-enterprise-config=SOURCE_TO_BUILD_GITHUB_ENTERPRISE_CONFIG + The resource name of the GitHub Enterprise config that should be + applied to this source (1st gen). Format: + projects/{project}/locations/{location}/githubEnterpriseConfigs/{id} + or projects/{project}/githubEnterpriseConfigs/{id} + + --source-to-build-repo-type=SOURCE_TO_BUILD_REPO_TYPE + Type of the repository (1st gen). Currently only GitHub and Cloud + Source Repository types are supported. + + This flag argument must be specified if any of the other + arguments in this group are specified. + + --source-to-build-uri=SOURCE_TO_BUILD_URI + The URI of the repository that should be applied to this source + (1st gen). + + 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 builds triggers update webhook + + $ gcloud beta builds triggers update webhook + diff --git a/gcloud/compute/os-config/patch-deployments/create b/gcloud/compute/os-config/patch-deployments/create index 4d1093b76..80cd4724f 100644 --- a/gcloud/compute/os-config/patch-deployments/create +++ b/gcloud/compute/os-config/patch-deployments/create @@ -44,9 +44,7 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. NOTES - These variants are also available: - - $ gcloud alpha compute os-config patch-deployments create + This variant is also available: $ gcloud beta compute os-config patch-deployments create diff --git a/gcloud/compute/os-config/patch-deployments/delete b/gcloud/compute/os-config/patch-deployments/delete index dcb17fd89..7c7cf4364 100644 --- a/gcloud/compute/os-config/patch-deployments/delete +++ b/gcloud/compute/os-config/patch-deployments/delete @@ -45,9 +45,7 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. NOTES - These variants are also available: - - $ gcloud alpha compute os-config patch-deployments delete + This variant is also available: $ gcloud beta compute os-config patch-deployments delete diff --git a/gcloud/compute/os-config/patch-deployments/describe b/gcloud/compute/os-config/patch-deployments/describe index 5784718af..c5431a130 100644 --- a/gcloud/compute/os-config/patch-deployments/describe +++ b/gcloud/compute/os-config/patch-deployments/describe @@ -45,9 +45,7 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. NOTES - These variants are also available: - - $ gcloud alpha compute os-config patch-deployments describe + This variant is also available: $ gcloud beta compute os-config patch-deployments describe diff --git a/gcloud/compute/os-config/patch-deployments/help b/gcloud/compute/os-config/patch-deployments/help index 9c4bf85a3..a1848bad4 100644 --- a/gcloud/compute/os-config/patch-deployments/help +++ b/gcloud/compute/os-config/patch-deployments/help @@ -38,9 +38,7 @@ COMMANDS Update patch deployment in a project. NOTES - These variants are also available: - - $ gcloud alpha compute os-config patch-deployments + This variant is also available: $ gcloud beta compute os-config patch-deployments diff --git a/gcloud/compute/os-config/patch-deployments/list b/gcloud/compute/os-config/patch-deployments/list index 943decf97..a1d6fd41a 100644 --- a/gcloud/compute/os-config/patch-deployments/list +++ b/gcloud/compute/os-config/patch-deployments/list @@ -56,9 +56,7 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. NOTES - These variants are also available: - - $ gcloud alpha compute os-config patch-deployments list + This variant is also available: $ gcloud beta compute os-config patch-deployments list diff --git a/gcloud/compute/os-config/patch-deployments/pause b/gcloud/compute/os-config/patch-deployments/pause index cbed7a8af..d503e3108 100644 --- a/gcloud/compute/os-config/patch-deployments/pause +++ b/gcloud/compute/os-config/patch-deployments/pause @@ -44,9 +44,7 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. NOTES - These variants are also available: - - $ gcloud alpha compute os-config patch-deployments pause + This variant is also available: $ gcloud beta compute os-config patch-deployments pause diff --git a/gcloud/compute/os-config/patch-deployments/resume b/gcloud/compute/os-config/patch-deployments/resume index f7ed2e5ab..d61d37db1 100644 --- a/gcloud/compute/os-config/patch-deployments/resume +++ b/gcloud/compute/os-config/patch-deployments/resume @@ -45,9 +45,7 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. NOTES - These variants are also available: - - $ gcloud alpha compute os-config patch-deployments resume + This variant is also available: $ gcloud beta compute os-config patch-deployments resume diff --git a/gcloud/compute/os-config/patch-deployments/update b/gcloud/compute/os-config/patch-deployments/update index 747cd236e..6e87db3a2 100644 --- a/gcloud/compute/os-config/patch-deployments/update +++ b/gcloud/compute/os-config/patch-deployments/update @@ -39,9 +39,7 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. NOTES - These variants are also available: - - $ gcloud alpha compute os-config patch-deployments update + This variant is also available: $ gcloud beta compute os-config patch-deployments update diff --git a/gcloud/compute/os-config/patch-jobs/cancel b/gcloud/compute/os-config/patch-jobs/cancel index c7e9e81c3..8c252edf0 100644 --- a/gcloud/compute/os-config/patch-jobs/cancel +++ b/gcloud/compute/os-config/patch-jobs/cancel @@ -38,9 +38,7 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. NOTES - These variants are also available: - - $ gcloud alpha compute os-config patch-jobs cancel + This variant is also available: $ gcloud beta compute os-config patch-jobs cancel diff --git a/gcloud/compute/os-config/patch-jobs/describe b/gcloud/compute/os-config/patch-jobs/describe index 260aa0b49..8a694932a 100644 --- a/gcloud/compute/os-config/patch-jobs/describe +++ b/gcloud/compute/os-config/patch-jobs/describe @@ -39,9 +39,7 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. NOTES - These variants are also available: - - $ gcloud alpha compute os-config patch-jobs describe + This variant is also available: $ gcloud beta compute os-config patch-jobs describe diff --git a/gcloud/compute/os-config/patch-jobs/execute b/gcloud/compute/os-config/patch-jobs/execute index 2d1fdd6aa..6bd1f93fe 100644 --- a/gcloud/compute/os-config/patch-jobs/execute +++ b/gcloud/compute/os-config/patch-jobs/execute @@ -388,9 +388,7 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. NOTES - These variants are also available: - - $ gcloud alpha compute os-config patch-jobs execute + This variant is also available: $ gcloud beta compute os-config patch-jobs execute diff --git a/gcloud/compute/os-config/patch-jobs/help b/gcloud/compute/os-config/patch-jobs/help index 216951b07..5b2411e87 100644 --- a/gcloud/compute/os-config/patch-jobs/help +++ b/gcloud/compute/os-config/patch-jobs/help @@ -32,9 +32,7 @@ COMMANDS List the instance details for an OS patch job. NOTES - These variants are also available: - - $ gcloud alpha compute os-config patch-jobs + This variant is also available: $ gcloud beta compute os-config patch-jobs diff --git a/gcloud/compute/os-config/patch-jobs/list b/gcloud/compute/os-config/patch-jobs/list index cef4d7698..f3aabf3d1 100644 --- a/gcloud/compute/os-config/patch-jobs/list +++ b/gcloud/compute/os-config/patch-jobs/list @@ -53,9 +53,7 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. NOTES - These variants are also available: - - $ gcloud alpha compute os-config patch-jobs list + This variant is also available: $ gcloud beta compute os-config patch-jobs list diff --git a/gcloud/compute/os-config/patch-jobs/list-instance-details b/gcloud/compute/os-config/patch-jobs/list-instance-details index 2b3dfb421..970f139e5 100644 --- a/gcloud/compute/os-config/patch-jobs/list-instance-details +++ b/gcloud/compute/os-config/patch-jobs/list-instance-details @@ -66,9 +66,7 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. NOTES - These variants are also available: - - $ gcloud alpha compute os-config patch-jobs list-instance-details + This variant is also available: $ gcloud beta compute os-config patch-jobs list-instance-details diff --git a/gcloud/compute/routers/add-bgp-peer b/gcloud/compute/routers/add-bgp-peer index 18bc06b8a..18f32181c 100644 --- a/gcloud/compute/routers/add-bgp-peer +++ b/gcloud/compute/routers/add-bgp-peer @@ -6,7 +6,8 @@ SYNOPSIS gcloud compute routers add-bgp-peer NAME --interface=INTERFACE --peer-asn=PEER_ASN --peer-name=PEER_NAME [--advertised-route-priority=ADVERTISED_ROUTE_PRIORITY] - [--advertisement-mode=MODE] [--async] [--[no-]enable-ipv6] + [--advertisement-mode=MODE] [--async] + [--custom-learned-route-priority=PRIORITY] [--[no-]enable-ipv6] [--[no-]enabled] [--instance=INSTANCE] [--instance-zone=INSTANCE_ZONE] [--ipv6-nexthop-address=IPV6_NEXTHOP_ADDRESS] [--md5-authentication-key=MD5_AUTHENTICATION_KEY] @@ -14,6 +15,7 @@ SYNOPSIS [--peer-ipv6-nexthop-address=PEER_IPV6_NEXTHOP_ADDRESS] [--region=REGION] [--set-advertisement-groups=[GROUP,...]] [--set-advertisement-ranges=[CIDR_RANGE=DESC,...]] + [--set-custom-learned-route-ranges=[CIDR_RANGE,...]] [--bfd-min-receive-interval=BFD_MIN_RECEIVE_INTERVAL --bfd-min-transmit-interval=BFD_MIN_TRANSMIT_INTERVAL --bfd-multiplier=BFD_MULTIPLIER @@ -58,6 +60,12 @@ OPTIONAL FLAGS Return immediately, without waiting for the operation in progress to complete. + --custom-learned-route-priority=PRIORITY + An integral value 0 <= priority <= 65535, to be applied to all custom + learned route IP address ranges for this peer. If not specified, a + Google-managed priority value of 100 is used. The routes with the + lowest priority value win. + --[no-]enable-ipv6 If IPv6 is enabled, the peer connection can be established with IPv6 route exchange. If disabled, no IPv6 route exchange is allowed on any @@ -155,6 +163,14 @@ OPTIONAL FLAGS the range, use --set-advertisement-ranges=192.168.10.0/24=my-networks. This list can only be specified in custom advertisement mode. + --set-custom-learned-route-ranges=[CIDR_RANGE,...] + The list of user-defined custom learned route IP address ranges for + this peer. This list is a comma separated IP address ranges such as + 1.2.3.4,6.7.0.0/16,2001:db8:abcd:12::/64 where each IP address range + must be a valid CIDR-formatted prefix. If an IP address is provided + without a subnet mask, it is interpreted as a /32 singular IP address + range for IPv4, and /128 for IPv6. + Arguments to configure BFD (Bidirectional Forwarding Detection) settings: --bfd-min-receive-interval=BFD_MIN_RECEIVE_INTERVAL diff --git a/gcloud/compute/routers/update-bgp-peer b/gcloud/compute/routers/update-bgp-peer index 7f64893da..85bc2b7a6 100644 --- a/gcloud/compute/routers/update-bgp-peer +++ b/gcloud/compute/routers/update-bgp-peer @@ -6,17 +6,21 @@ SYNOPSIS gcloud compute routers update-bgp-peer NAME --peer-name=PEER_NAME [--advertised-route-priority=ADVERTISED_ROUTE_PRIORITY] [--advertisement-mode=MODE] [--async] [--clear-md5-authentication-key] - [--[no-]enable-ipv6] [--[no-]enabled] [--interface=INTERFACE] - [--ip-address=IP_ADDRESS] [--ipv6-nexthop-address=IPV6_NEXTHOP_ADDRESS] + [--custom-learned-route-priority=PRIORITY] [--[no-]enable-ipv6] + [--[no-]enabled] [--interface=INTERFACE] [--ip-address=IP_ADDRESS] + [--ipv6-nexthop-address=IPV6_NEXTHOP_ADDRESS] [--md5-authentication-key=MD5_AUTHENTICATION_KEY] [--peer-asn=PEER_ASN] [--peer-ip-address=PEER_IP_ADDRESS] [--peer-ipv6-nexthop-address=PEER_IPV6_NEXTHOP_ADDRESS] [--region=REGION] [--set-advertisement-groups=[GROUP,...]] [--set-advertisement-ranges=[CIDR_RANGE=DESC,...]] + [--set-custom-learned-route-ranges=[CIDR_RANGE,...]] [--add-advertisement-groups=[GROUP,...] | --add-advertisement-ranges=[CIDR_RANGE=DESC,...] | --remove-advertisement-groups=[GROUP,...] | --remove-advertisement-ranges=[CIDR_RANGE,...]] + [--add-custom-learned-route-ranges=[CIDR_RANGE,...] + | --remove-custom-learned-route-ranges=[CIDR_RANGE,...]] [--bfd-min-receive-interval=BFD_MIN_RECEIVE_INTERVAL --bfd-min-transmit-interval=BFD_MIN_TRANSMIT_INTERVAL --bfd-multiplier=BFD_MULTIPLIER @@ -57,6 +61,12 @@ OPTIONAL FLAGS --clear-md5-authentication-key If specified, remove MD5 authentication from the BGP peer. + --custom-learned-route-priority=PRIORITY + An integral value 0 <= priority <= 65535, to be applied to all custom + learned route IP address ranges for this peer. If not specified, a + Google-managed priority value of 100 is used. The routes with the + lowest priority value win. + --[no-]enable-ipv6 If IPv6 is enabled, the peer connection can be established with IPv6 route exchange. If disabled, no IPv6 route exchange is allowed on any @@ -141,6 +151,14 @@ OPTIONAL FLAGS the range, use --set-advertisement-ranges=192.168.10.0/24=my-networks. This list can only be specified in custom advertisement mode. + --set-custom-learned-route-ranges=[CIDR_RANGE,...] + The list of user-defined custom learned route IP address ranges for + this peer. This list is a comma separated IP address ranges such as + 1.2.3.4,6.7.0.0/16,2001:db8:abcd:12::/64 where each IP address range + must be a valid CIDR-formatted prefix. If an IP address is provided + without a subnet mask, it is interpreted as a /32 singular IP address + range for IPv4, and /128 for IPv6. + At most one of these can be specified: --add-advertisement-groups=[GROUP,...] @@ -181,6 +199,24 @@ OPTIONAL FLAGS exist in the current set of custom advertisements. This field can only be specified in custom advertisement mode. + At most one of these can be specified: + + --add-custom-learned-route-ranges=[CIDR_RANGE,...] + A list of user-defined custom learned route IP address ranges to be + added to this peer. This list is a comma separated IP address ranges + such as 1.2.3.4,6.7.0.0/16,2001:db8:abcd:12::/64 where each IP + address range must be a valid CIDR-formatted prefix. If an IP address + is provided without a subnet mask, it is interpreted as a /32 + singular IP address range for IPv4, and /128 for IPv6. + + --remove-custom-learned-route-ranges=[CIDR_RANGE,...] + A list of user-defined custom learned route IP address ranges to be + removed from this peer. This list is a comma separated IP address + ranges such as 1.2.3.4,6.7.0.0/16,2001:db8:abcd:12::/64 where each IP + address range must be a valid CIDR-formatted prefix. If an IP address + is provided without a subnet mask, it is interpreted as a /32 + singular IP address range for IPv4, and /128 for IPv6. + Arguments to update BFD (Bidirectional Forwarding Detection) settings: --bfd-min-receive-interval=BFD_MIN_RECEIVE_INTERVAL diff --git a/gcloud/compute/target-http-proxies/create b/gcloud/compute/target-http-proxies/create index b74391709..33edce3ef 100644 --- a/gcloud/compute/target-http-proxies/create +++ b/gcloud/compute/target-http-proxies/create @@ -3,7 +3,9 @@ NAME SYNOPSIS gcloud compute target-http-proxies create NAME --url-map=URL_MAP - [--description=DESCRIPTION] [--global | --region=REGION] + [--description=DESCRIPTION] + [--http-keep-alive-timeout-sec=HTTP_KEEP_ALIVE_TIMEOUT_SEC] + [--global | --region=REGION] [--global-url-map | --url-map-region=URL_MAP_REGION] [GCLOUD_WIDE_FLAG ...] @@ -47,6 +49,13 @@ OPTIONAL FLAGS --description=DESCRIPTION An optional, textual description for the target HTTP proxy. + --http-keep-alive-timeout-sec=HTTP_KEEP_ALIVE_TIMEOUT_SEC + Represents the maximum amount of time that a TCP connection can be idle + between the (downstream) client and the target HTTP proxy. If an HTTP + keepalive timeout is not specified, the default value is 610 seconds. + For global external Application load balancer, the minimum allowed + value is 5 seconds and the maximum allowed value is 1200 seconds. + At most one of these can be specified: --global diff --git a/gcloud/compute/target-http-proxies/update b/gcloud/compute/target-http-proxies/update index 3848e0b48..7cb7e2ef9 100644 --- a/gcloud/compute/target-http-proxies/update +++ b/gcloud/compute/target-http-proxies/update @@ -3,6 +3,8 @@ NAME SYNOPSIS gcloud compute target-http-proxies update NAME --url-map=URL_MAP + [--clear-http-keep-alive-timeout-sec + | --http-keep-alive-timeout-sec=HTTP_KEEP_ALIVE_TIMEOUT_SEC] [--global | --region=REGION] [--global-url-map | --url-map-region=URL_MAP_REGION] [GCLOUD_WIDE_FLAG ...] @@ -39,6 +41,19 @@ REQUIRED FLAGS referring to, you must first delete the target HTTP proxy. OPTIONAL FLAGS + At most one of these can be specified: + + --clear-http-keep-alive-timeout-sec + Clears the previously configured HTTP keepalive timeout. + + --http-keep-alive-timeout-sec=HTTP_KEEP_ALIVE_TIMEOUT_SEC + Represents the maximum amount of time that a TCP connection can be + idle between the (downstream) client and the target HTTP proxy. If an + HTTP keepalive timeout is not specified, the default value is 610 + seconds. For global external Application load balancer, the minimum + allowed value is 5 seconds and the maximum allowed value is 1200 + seconds. + At most one of these can be specified: --global diff --git a/gcloud/compute/target-https-proxies/create b/gcloud/compute/target-https-proxies/create index cace86f02..dd50aed21 100644 --- a/gcloud/compute/target-https-proxies/create +++ b/gcloud/compute/target-https-proxies/create @@ -4,6 +4,7 @@ NAME SYNOPSIS gcloud compute target-https-proxies create NAME --url-map=URL_MAP [--certificate-map=CERTIFICATE_MAP] [--description=DESCRIPTION] + [--http-keep-alive-timeout-sec=HTTP_KEEP_ALIVE_TIMEOUT_SEC] [--quic-override=QUIC_OVERRIDE; default="NONE"] [--ssl-policy=SSL_POLICY] [--certificate-manager-certificates=[CERTIFICATE_MANAGER_CERTIFICATES, @@ -76,6 +77,13 @@ OPTIONAL FLAGS --description=DESCRIPTION An optional, textual description for the target HTTPS proxy. + --http-keep-alive-timeout-sec=HTTP_KEEP_ALIVE_TIMEOUT_SEC + Represents the maximum amount of time that a TCP connection can be idle + between the (downstream) client and the target HTTP proxy. If an HTTP + keepalive timeout is not specified, the default value is 610 seconds. + For global external Application load balancer, the minimum allowed + value is 5 seconds and the maximum allowed value is 1200 seconds. + --quic-override=QUIC_OVERRIDE; default="NONE" Controls whether load balancer may negotiate QUIC with clients. QUIC is a new transport which reduces latency compared to that of TCP. See diff --git a/gcloud/compute/target-https-proxies/update b/gcloud/compute/target-https-proxies/update index c1018cce7..22849f9ce 100644 --- a/gcloud/compute/target-https-proxies/update +++ b/gcloud/compute/target-https-proxies/update @@ -9,6 +9,8 @@ SYNOPSIS | --ssl-certificates=SSL_CERTIFICATE,[...] --global-ssl-certificates | --ssl-certificates-region=SSL_CERTIFICATES_REGION | --certificate-map=CERTIFICATE_MAP | --clear-certificate-map] + [--clear-http-keep-alive-timeout-sec + | --http-keep-alive-timeout-sec=HTTP_KEEP_ALIVE_TIMEOUT_SEC] [--clear-ssl-policy | --ssl-policy=SSL_POLICY --global-ssl-policy | --ssl-policy-region=SSL_POLICY_REGION] [--global | --region=REGION] [--global-url-map | --url-map-region=URL_MAP_REGION] @@ -159,6 +161,19 @@ FLAGS --clear-certificate-map Removes any attached certificate map from the HTTPS proxy. + At most one of these can be specified: + + --clear-http-keep-alive-timeout-sec + Clears the previously configured HTTP keepalive timeout. + + --http-keep-alive-timeout-sec=HTTP_KEEP_ALIVE_TIMEOUT_SEC + Represents the maximum amount of time that a TCP connection can be + idle between the (downstream) client and the target HTTP proxy. If an + HTTP keepalive timeout is not specified, the default value is 610 + seconds. For global external Application load balancer, the minimum + allowed value is 5 seconds and the maximum allowed value is 1200 + seconds. + At most one of these can be specified: --clear-ssl-policy diff --git a/gcloud/compute/tpus/tpu-vm/create b/gcloud/compute/tpus/tpu-vm/create index 9e40d1262..72d3ec2db 100644 --- a/gcloud/compute/tpus/tpu-vm/create +++ b/gcloud/compute/tpus/tpu-vm/create @@ -106,7 +106,7 @@ OPTIONAL FLAGS Text description of the TPU. --internal-ips - Indicates that the IP addresses for the node should be internal. The + Indicate that the IP addresses for the node should be internal. The default is that external IP addresses will be associated with the TPU workers. diff --git a/gcloud/config/get b/gcloud/config/get index febdd59e1..4273c0ad2 100644 --- a/gcloud/config/get +++ b/gcloud/config/get @@ -370,6 +370,10 @@ AVAILABLE PROPERTIES Overrides API endpoint for gcloud events command group. Defaults to https://events.googleapis.com/ + faultinjectiontesting + Overrides API endpoint for gcloud fault-injection command group. + Defaults to https://faultinjectiontesting.googleapis.com/ + file Overrides API endpoint for gcloud filestore command group. Defaults to https://file.googleapis.com/ diff --git a/gcloud/config/help b/gcloud/config/help index 746989c1b..c7f4532d0 100644 --- a/gcloud/config/help +++ b/gcloud/config/help @@ -402,6 +402,10 @@ AVAILABLE PROPERTIES Overrides API endpoint for gcloud events command group. Defaults to https://events.googleapis.com/ + faultinjectiontesting + Overrides API endpoint for gcloud fault-injection command group. + Defaults to https://faultinjectiontesting.googleapis.com/ + file Overrides API endpoint for gcloud filestore command group. Defaults to https://file.googleapis.com/ diff --git a/gcloud/config/list b/gcloud/config/list index 8c07fe263..460a8452d 100644 --- a/gcloud/config/list +++ b/gcloud/config/list @@ -414,6 +414,10 @@ AVAILABLE PROPERTIES Overrides API endpoint for gcloud events command group. Defaults to https://events.googleapis.com/ + faultinjectiontesting + Overrides API endpoint for gcloud fault-injection command group. + Defaults to https://faultinjectiontesting.googleapis.com/ + file Overrides API endpoint for gcloud filestore command group. Defaults to https://file.googleapis.com/ diff --git a/gcloud/config/set b/gcloud/config/set index d8a559c05..0a9fe5c41 100644 --- a/gcloud/config/set +++ b/gcloud/config/set @@ -417,6 +417,10 @@ AVAILABLE PROPERTIES Overrides API endpoint for gcloud events command group. Defaults to https://events.googleapis.com/ + faultinjectiontesting + Overrides API endpoint for gcloud fault-injection command group. + Defaults to https://faultinjectiontesting.googleapis.com/ + file Overrides API endpoint for gcloud filestore command group. Defaults to https://file.googleapis.com/ diff --git a/gcloud/config/unset b/gcloud/config/unset index 5c071b2fa..1b4809c09 100644 --- a/gcloud/config/unset +++ b/gcloud/config/unset @@ -378,6 +378,10 @@ AVAILABLE PROPERTIES Overrides API endpoint for gcloud events command group. Defaults to https://events.googleapis.com/ + faultinjectiontesting + Overrides API endpoint for gcloud fault-injection command group. + Defaults to https://faultinjectiontesting.googleapis.com/ + file Overrides API endpoint for gcloud filestore command group. Defaults to https://file.googleapis.com/ diff --git a/gcloud/container/clusters/create b/gcloud/container/clusters/create index c9ac701f4..eab8b4e6a 100644 --- a/gcloud/container/clusters/create +++ b/gcloud/container/clusters/create @@ -18,6 +18,7 @@ SYNOPSIS [--cluster-version=CLUSTER_VERSION] [--create-subnetwork=[KEY=VALUE,...]] [--database-encryption-key=DATABASE_ENCRYPTION_KEY] + [--dataplane-v2-observability-mode=DATAPLANE_V2_OBSERVABILITY_MODE] [--default-max-pods-per-node=DEFAULT_MAX_PODS_PER_NODE] [--disable-default-snat] [--disk-size=DISK_SIZE] [--disk-type=DISK_TYPE] [--enable-autorepair] [--no-enable-autoupgrade] @@ -26,6 +27,7 @@ SYNOPSIS [--enable-cost-allocation] [--enable-dataplane-v2] [--enable-google-cloud-access] [--enable-gvnic] [--enable-identity-service] [--enable-image-streaming] + [--enable-insecure-kubelet-readonly-port] [--enable-intra-node-visibility] [--enable-ip-alias] [--enable-kubernetes-alpha] [--enable-kubernetes-unstable-apis=API,[API,...]] @@ -66,6 +68,7 @@ SYNOPSIS | --enable-binauthz] [--cluster-dns=CLUSTER_DNS --cluster-dns-domain=CLUSTER_DNS_DOMAIN --cluster-dns-scope=CLUSTER_DNS_SCOPE] + [--disable-dataplane-v2-metrics | --enable-dataplane-v2-metrics] [[--enable-autoprovisioning : --autoprovisioning-config-file=AUTOPROVISIONING_CONFIG_FILE | [--max-cpu=MAX_CPU --max-memory=MAX_MEMORY @@ -320,6 +323,35 @@ FLAGS For more information, see https://cloud.google.com/kubernetes-engine/docs/how-to/encrypting-secrets. + --dataplane-v2-observability-mode=DATAPLANE_V2_OBSERVABILITY_MODE + Select Advanced Datapath Observability mode for the cluster. Defaults + to DISABLED. + + Advanced Datapath Observability allows for a real-time view into + pod-to-pod traffic within your cluster. + + Examples: + + $ gcloud container clusters create \ + --dataplane-v2-observability-mode=DISABLED + + $ gcloud container clusters create \ + --dataplane-v2-observability-mode=INTERNAL_VPC_LB + + $ gcloud container clusters create \ + --dataplane-v2-observability-mode=EXTERNAL_LB + + DATAPLANE_V2_OBSERVABILITY_MODE must be one of: + + DISABLED + Disables Advanced Datapath Observability. + EXTERNAL_LB + Makes Advanced Datapath Observability available to the external + network. + INTERNAL_VPC_LB + Makes Advanced Datapath Observability available from the VPC + network. + --default-max-pods-per-node=DEFAULT_MAX_PODS_PER_NODE The default max number of pods per node for node pools in the cluster. @@ -448,6 +480,12 @@ FLAGS --enable-image-streaming Specifies whether to enable image streaming on cluster. + --enable-insecure-kubelet-readonly-port + Enables the Kubelet's insecure Read Only Port. + + To disable in an existing cluster, explicitly set flag to + --no-enable-insecure-kubelet-readonly-port. + --enable-intra-node-visibility Enable Intra-node visibility for this cluster. @@ -1096,8 +1134,7 @@ FLAGS --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, + BINAUTHZ_EVALUATION_MODE must be one of: DISABLED, PROJECT_SINGLETON_POLICY_ENFORCE. --enable-binauthz @@ -1135,6 +1172,14 @@ FLAGS vpc Configures the Cloud DNS zone to be private to the VPC Network. + At most one of these can be specified: + + --disable-dataplane-v2-metrics + Stops exposing advanced datapath flow metrics on node port. + + --enable-dataplane-v2-metrics + Exposes advanced datapath flow metrics on node port. + Node autoprovisioning --enable-autoprovisioning diff --git a/gcloud/container/clusters/create-auto b/gcloud/container/clusters/create-auto index 52161befe..e1dff2e48 100644 --- a/gcloud/container/clusters/create-auto +++ b/gcloud/container/clusters/create-auto @@ -12,7 +12,9 @@ SYNOPSIS [--cluster-version=CLUSTER_VERSION] [--create-subnetwork=[KEY=VALUE,...]] [--database-encryption-key=DATABASE_ENCRYPTION_KEY] + [--dataplane-v2-observability-mode=DATAPLANE_V2_OBSERVABILITY_MODE] [--enable-google-cloud-access] + [--enable-insecure-kubelet-readonly-port] [--enable-kubernetes-unstable-apis=API,[API,...]] [--enable-master-global-access] [--logging=[COMPONENT,...]] [--monitoring=[COMPONENT,...]] [--network=NETWORK] @@ -71,8 +73,7 @@ FLAGS --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, + BINAUTHZ_EVALUATION_MODE must be one of: DISABLED, PROJECT_SINGLETON_POLICY_ENFORCE. --boot-disk-kms-key=BOOT_DISK_KMS_KEY @@ -161,11 +162,46 @@ FLAGS For more information, see https://cloud.google.com/kubernetes-engine/docs/how-to/encrypting-secrets. + --dataplane-v2-observability-mode=DATAPLANE_V2_OBSERVABILITY_MODE + Select Advanced Datapath Observability mode for the cluster. Defaults + to DISABLED. + + Advanced Datapath Observability allows for a real-time view into + pod-to-pod traffic within your cluster. + + Examples: + + $ gcloud container clusters create-auto \ + --dataplane-v2-observability-mode=DISABLED + + $ gcloud container clusters create-auto \ + --dataplane-v2-observability-mode=INTERNAL_VPC_LB + + $ gcloud container clusters create-auto \ + --dataplane-v2-observability-mode=EXTERNAL_LB + + DATAPLANE_V2_OBSERVABILITY_MODE must be one of: + + DISABLED + Disables Advanced Datapath Observability. + EXTERNAL_LB + Makes Advanced Datapath Observability available to the external + network. + INTERNAL_VPC_LB + Makes Advanced Datapath Observability available from the VPC + network. + --enable-google-cloud-access When you enable Google Cloud Access, any public IP addresses owned by Google Cloud can reach the public control plane endpoint of your cluster. + --enable-insecure-kubelet-readonly-port + Enables the Kubelet's insecure Read Only Port. + + To disable in an existing cluster, explicitly set flag to + --no-enable-insecure-kubelet-readonly-port. + --enable-kubernetes-unstable-apis=API,[API,...] Enable Kubernetes beta API features on this cluster. Beta APIs are not expected to be production ready and should be avoided in diff --git a/gcloud/container/clusters/get-credentials b/gcloud/container/clusters/get-credentials index 2f9615dbe..e876b125f 100644 --- a/gcloud/container/clusters/get-credentials +++ b/gcloud/container/clusters/get-credentials @@ -31,8 +31,11 @@ DESCRIPTION (https://cloud.google.com/sdk/docs/properties) to true before running gcloud container clusters get-credentials - See https://cloud.google.com/kubernetes-engine/docs/kubectl for kubectl - documentation. + See + https://cloud.google.com/kubernetes-engine/docs/how-to/cluster-access-for-kubectl + for kubectl usage with Google Kubernetes Engine and + https://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands for + available kubectl commands. EXAMPLES To switch to working on your cluster 'sample-cluster', run: diff --git a/gcloud/container/clusters/update b/gcloud/container/clusters/update index cd15d75b9..48fbabac8 100644 --- a/gcloud/container/clusters/update +++ b/gcloud/container/clusters/update @@ -8,10 +8,12 @@ SYNOPSIS | --autoscaling-profile=AUTOSCALING_PROFILE | --complete-credential-rotation | --complete-ip-rotation | --database-encryption-key=DATABASE_ENCRYPTION_KEY + | --dataplane-v2-observability-mode=DATAPLANE_V2_OBSERVABILITY_MODE | --disable-database-encryption | --disable-default-snat | --disable-workload-identity | --enable-autoscaling | --enable-cost-allocation | --enable-google-cloud-access | --enable-identity-service | --enable-image-streaming + | --enable-insecure-kubelet-readonly-port | --enable-intra-node-visibility | --enable-kubernetes-unstable-apis=API,[API,...] | --enable-l4-ilb-subsetting | --enable-legacy-authorization @@ -52,7 +54,9 @@ SYNOPSIS --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 | [--enable-autoprovisioning + --cluster-dns-scope=CLUSTER_DNS_SCOPE + | --disable-dataplane-v2-metrics | --enable-dataplane-v2-metrics + | [--enable-autoprovisioning : --autoprovisioning-config-file=AUTOPROVISIONING_CONFIG_FILE | --autoprovisioning-image-type=AUTOPROVISIONING_IMAGE_TYPE --autoprovisioning-locations=ZONE,[ZONE,...] @@ -152,6 +156,35 @@ REQUIRED FLAGS For more information, see https://cloud.google.com/kubernetes-engine/docs/how-to/encrypting-secrets. + --dataplane-v2-observability-mode=DATAPLANE_V2_OBSERVABILITY_MODE + Select Advanced Datapath Observability mode for the cluster. Defaults + to DISABLED. + + Advanced Datapath Observability allows for a real-time view into + pod-to-pod traffic within your cluster. + + Examples: + + $ gcloud container clusters update \ + --dataplane-v2-observability-mode=DISABLED + + $ gcloud container clusters update \ + --dataplane-v2-observability-mode=INTERNAL_VPC_LB + + $ gcloud container clusters update \ + --dataplane-v2-observability-mode=EXTERNAL_LB + + DATAPLANE_V2_OBSERVABILITY_MODE must be one of: + + DISABLED + Disables Advanced Datapath Observability. + EXTERNAL_LB + Makes Advanced Datapath Observability available to the external + network. + INTERNAL_VPC_LB + Makes Advanced Datapath Observability available from the VPC + network. + --disable-database-encryption Disable database encryption. @@ -221,6 +254,12 @@ REQUIRED FLAGS --enable-image-streaming Specifies whether to enable image streaming on cluster. + --enable-insecure-kubelet-readonly-port + Enables the Kubelet's insecure Read Only Port. + + To disable in an existing cluster, explicitly set flag to + --no-enable-insecure-kubelet-readonly-port. + --enable-intra-node-visibility Enable Intra-node visibility for this cluster. @@ -602,8 +641,6 @@ REQUIRED FLAGS --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 @@ -777,6 +814,14 @@ REQUIRED FLAGS vpc Configures the Cloud DNS zone to be private to the VPC Network. + At most one of these can be specified: + + --disable-dataplane-v2-metrics + Stops exposing advanced datapath flow metrics on node port. + + --enable-dataplane-v2-metrics + Exposes advanced datapath flow metrics on node port. + Node autoprovisioning --enable-autoprovisioning diff --git a/gcloud/container/fleet/fleetobservability/describe b/gcloud/container/fleet/fleetobservability/describe new file mode 100644 index 000000000..85436e33f --- /dev/null +++ b/gcloud/container/fleet/fleetobservability/describe @@ -0,0 +1,31 @@ +NAME + gcloud container fleet fleetobservability describe - describes the status + of the Fleet Observability Feature resource + +SYNOPSIS + gcloud container fleet fleetobservability describe [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + This command gets the detailed status of the Fleet Observability Feature in + a fleet. + +EXAMPLES + To describe the Fleet Observability Feature, run: + + $ gcloud container fleet fleetobservability describe + +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 fleetobservability describe + + $ gcloud beta container fleet fleetobservability describe + diff --git a/gcloud/container/fleet/fleetobservability/disable b/gcloud/container/fleet/fleetobservability/disable new file mode 100644 index 000000000..025696537 --- /dev/null +++ b/gcloud/container/fleet/fleetobservability/disable @@ -0,0 +1,36 @@ +NAME + gcloud container fleet fleetobservability disable - disables the Fleet + Observability Feature + +SYNOPSIS + gcloud container fleet fleetobservability disable [--force] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + This command disables Fleet Observability Feature in a fleet. + +EXAMPLES + To disable the Fleet Observability Feature, run: + + $ gcloud container fleet fleetobservability disable + +FLAGS + --force + Disable this feature, even if it is currently in use. Force disablement + may result in unexpected behavior. + +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 fleetobservability disable + + $ gcloud beta container fleet fleetobservability disable + diff --git a/gcloud/container/fleet/fleetobservability/enable b/gcloud/container/fleet/fleetobservability/enable new file mode 100644 index 000000000..ba2c83b27 --- /dev/null +++ b/gcloud/container/fleet/fleetobservability/enable @@ -0,0 +1,30 @@ +NAME + gcloud container fleet fleetobservability enable - enables the Fleet + Observability Feature + +SYNOPSIS + gcloud container fleet fleetobservability enable [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + This command enables Fleet Observability Feature in a fleet. + +EXAMPLES + To enable the Fleet Observability Feature, run: + + $ gcloud container fleet fleetobservability enable + +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 fleetobservability enable + + $ gcloud beta container fleet fleetobservability enable + diff --git a/gcloud/container/fleet/fleetobservability/help b/gcloud/container/fleet/fleetobservability/help new file mode 100644 index 000000000..fdbf1c5b6 --- /dev/null +++ b/gcloud/container/fleet/fleetobservability/help @@ -0,0 +1,37 @@ +NAME + gcloud container fleet fleetobservability - manage Fleet Observability + Feature + +SYNOPSIS + gcloud container fleet fleetobservability COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Manage Fleet Observability Feature. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + describe + Describes the status of the Fleet Observability Feature resource. + + disable + Disables the Fleet Observability Feature. + + enable + Enables the Fleet Observability Feature. + + update + Updates the Fleet Observability Feature resource. + +NOTES + These variants are also available: + + $ gcloud alpha container fleet fleetobservability + + $ gcloud beta container fleet fleetobservability + diff --git a/gcloud/container/fleet/fleetobservability/update b/gcloud/container/fleet/fleetobservability/update new file mode 100644 index 000000000..ebe44208f --- /dev/null +++ b/gcloud/container/fleet/fleetobservability/update @@ -0,0 +1,59 @@ +NAME + gcloud container fleet fleetobservability update - updates the Fleet + Observability Feature resource + +SYNOPSIS + gcloud container fleet fleetobservability update + [--logging-config=LOGGING_CONFIG] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + This command updates the Fleet Observability Feature in a fleet. + +EXAMPLES + To describe the Fleet Observability Feature, run: + + $ gcloud container fleet fleetobservability update \ + --logging-config=LOGGING-CONFIG + +FLAGS + --logging-config=LOGGING_CONFIG + Path of the YAML(or JSON) file that contains the logging + configurations. + + The JSON file is formatted as follows, with camelCase field naming: + + { + "loggingConfig": { + "defaultConfig": { + "mode": "COPY" + }, + "fleetScopeLogsConfig": { + "mode": "MOVE" + } + } + } + + The YAML file is formatted as follows, with camelCase field naming: + + --- + loggingConfig: + defaultConfig: + mode: COPY + fleetScopeLogsConfig: + mode: MOVE + +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 fleetobservability update + + $ gcloud beta container fleet fleetobservability update + diff --git a/gcloud/container/fleet/help b/gcloud/container/fleet/help index 0aa743669..b4679c423 100644 --- a/gcloud/container/fleet/help +++ b/gcloud/container/fleet/help @@ -51,6 +51,9 @@ GROUPS features Manage Hub Feature resources. + fleetobservability + Manage Fleet Observability Feature. + identity-service Manage Identity Service Feature. diff --git a/gcloud/container/hub/fleetobservability/describe b/gcloud/container/hub/fleetobservability/describe new file mode 100644 index 000000000..389f4b020 --- /dev/null +++ b/gcloud/container/hub/fleetobservability/describe @@ -0,0 +1,31 @@ +NAME + gcloud container hub fleetobservability describe - describes the status of + the Fleet Observability Feature resource + +SYNOPSIS + gcloud container hub fleetobservability describe [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + This command gets the detailed status of the Fleet Observability Feature in + a fleet. + +EXAMPLES + To describe the Fleet Observability Feature, run: + + $ gcloud container hub fleetobservability describe + +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 fleetobservability describe + + $ gcloud beta container hub fleetobservability describe + diff --git a/gcloud/container/hub/fleetobservability/disable b/gcloud/container/hub/fleetobservability/disable new file mode 100644 index 000000000..c93344d74 --- /dev/null +++ b/gcloud/container/hub/fleetobservability/disable @@ -0,0 +1,36 @@ +NAME + gcloud container hub fleetobservability disable - disables the Fleet + Observability Feature + +SYNOPSIS + gcloud container hub fleetobservability disable [--force] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + This command disables Fleet Observability Feature in a fleet. + +EXAMPLES + To disable the Fleet Observability Feature, run: + + $ gcloud container hub fleetobservability disable + +FLAGS + --force + Disable this feature, even if it is currently in use. Force disablement + may result in unexpected behavior. + +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 fleetobservability disable + + $ gcloud beta container hub fleetobservability disable + diff --git a/gcloud/container/hub/fleetobservability/enable b/gcloud/container/hub/fleetobservability/enable new file mode 100644 index 000000000..a5d26b469 --- /dev/null +++ b/gcloud/container/hub/fleetobservability/enable @@ -0,0 +1,30 @@ +NAME + gcloud container hub fleetobservability enable - enables the Fleet + Observability Feature + +SYNOPSIS + gcloud container hub fleetobservability enable [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + This command enables Fleet Observability Feature in a fleet. + +EXAMPLES + To enable the Fleet Observability Feature, run: + + $ gcloud container hub fleetobservability enable + +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 fleetobservability enable + + $ gcloud beta container hub fleetobservability enable + diff --git a/gcloud/container/hub/fleetobservability/help b/gcloud/container/hub/fleetobservability/help new file mode 100644 index 000000000..8ee2a7109 --- /dev/null +++ b/gcloud/container/hub/fleetobservability/help @@ -0,0 +1,37 @@ +NAME + gcloud container hub fleetobservability - manage Fleet Observability + Feature + +SYNOPSIS + gcloud container hub fleetobservability COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Manage Fleet Observability Feature. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + describe + Describes the status of the Fleet Observability Feature resource. + + disable + Disables the Fleet Observability Feature. + + enable + Enables the Fleet Observability Feature. + + update + Updates the Fleet Observability Feature resource. + +NOTES + These variants are also available: + + $ gcloud alpha container hub fleetobservability + + $ gcloud beta container hub fleetobservability + diff --git a/gcloud/container/hub/fleetobservability/update b/gcloud/container/hub/fleetobservability/update new file mode 100644 index 000000000..7be51dd33 --- /dev/null +++ b/gcloud/container/hub/fleetobservability/update @@ -0,0 +1,59 @@ +NAME + gcloud container hub fleetobservability update - updates the Fleet + Observability Feature resource + +SYNOPSIS + gcloud container hub fleetobservability update + [--logging-config=LOGGING_CONFIG] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + This command updates the Fleet Observability Feature in a fleet. + +EXAMPLES + To describe the Fleet Observability Feature, run: + + $ gcloud container hub fleetobservability update \ + --logging-config=LOGGING-CONFIG + +FLAGS + --logging-config=LOGGING_CONFIG + Path of the YAML(or JSON) file that contains the logging + configurations. + + The JSON file is formatted as follows, with camelCase field naming: + + { + "loggingConfig": { + "defaultConfig": { + "mode": "COPY" + }, + "fleetScopeLogsConfig": { + "mode": "MOVE" + } + } + } + + The YAML file is formatted as follows, with camelCase field naming: + + --- + loggingConfig: + defaultConfig: + mode: COPY + fleetScopeLogsConfig: + mode: MOVE + +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 fleetobservability update + + $ gcloud beta container hub fleetobservability update + diff --git a/gcloud/container/hub/help b/gcloud/container/hub/help index 6bd361371..5ace079a8 100644 --- a/gcloud/container/hub/help +++ b/gcloud/container/hub/help @@ -51,6 +51,9 @@ GROUPS features Manage Hub Feature resources. + fleetobservability + Manage Fleet Observability Feature. + identity-service Manage Identity Service Feature. diff --git a/gcloud/functions/deploy b/gcloud/functions/deploy index 6f3bf86bc..783cb78d8 100644 --- a/gcloud/functions/deploy +++ b/gcloud/functions/deploy @@ -600,6 +600,16 @@ FLAGS argument or as multiple arguments. This is only relevant when --gen2 is provided. + The provided attribute/value pair will be used with the + match-path-pattern operator to configure the trigger, see + https://cloud.google.com/eventarc/docs/reference/rest/v1/projects.locations.triggers#eventfilter + and http://cloud/eventarc/docs/path-patterns for more details about + on how to construct path patterns. + + For example, to filter on events for Compute Engine VMs in a given + zone: + --trigger-event-filters-path-pattern=resourceName='/projects/*/zones/us-central1-a/instances/*' + GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, diff --git a/gcloud/iam/workforce-pools/providers/create-oidc b/gcloud/iam/workforce-pools/providers/create-oidc index 4a5149e94..c8a360f53 100644 --- a/gcloud/iam/workforce-pools/providers/create-oidc +++ b/gcloud/iam/workforce-pools/providers/create-oidc @@ -8,8 +8,9 @@ SYNOPSIS --attribute-mapping=[ATTRIBUTE_MAPPING,...] --client-id=CLIENT_ID --issuer-uri=ISSUER_URI (--web-sso-assertion-claims-behavior=WEB_SSO_ASSERTION_CLAIMS_BEHAVIOR - --web-sso-response-type=WEB_SSO_RESPONSE_TYPE) [--async] - [--attribute-condition=ATTRIBUTE_CONDITION] + --web-sso-response-type=WEB_SSO_RESPONSE_TYPE + : --web-sso-additional-scopes=[WEB_SSO_ADDITIONAL_SCOPES,...]) + [--async] [--attribute-condition=ATTRIBUTE_CONDITION] [--client-secret-value=CLIENT_SECRET_VALUE] [--description=DESCRIPTION] [--disabled] [--display-name=DISPLAY_NAME] [GCLOUD_WIDE_FLAG ...] @@ -28,9 +29,11 @@ EXAMPLES --description="My workforce pool provider description." \ --disabled --attribute-mapping="google.subject=assertion.sub" \ --attribute-condition="true" --client-id="client-id" \ + --client-secret-value="client-secret" \ --issuer-uri="https://test-idp.com" \ - --web-sso-response-type=id-token \ - --web-sso-assertion-claims-behavior=only-id-token-claims + --web-sso-response-type="code" \ + --web-sso-assertion-claims-behavior="merge-user-info-over-id-tok\ + en-claims" --web-sso-additional-scopes="groups,photos" POSITIONAL ARGUMENTS Workforce pool provider resource - The workforce pool provider to create. @@ -182,6 +185,15 @@ REQUIRED FLAGS This flag argument must be specified if any of the other arguments in this group are specified. + --web-sso-additional-scopes=[WEB_SSO_ADDITIONAL_SCOPES,...] + Additional scopes to request for the OIDC authentication on top of + scopes requested by default. By default, the openid, profile and + email scopes that are supported by the identity provider are + requested. + + Each additional scope may be at most 256 characters. A maximum of 10 + additional scopes may be configured. + OPTIONAL FLAGS --async Return immediately, without waiting for the operation in progress to diff --git a/gcloud/iam/workforce-pools/providers/update-oidc b/gcloud/iam/workforce-pools/providers/update-oidc index 74dc8aec4..f66e7b5e9 100644 --- a/gcloud/iam/workforce-pools/providers/update-oidc +++ b/gcloud/iam/workforce-pools/providers/update-oidc @@ -9,6 +9,7 @@ SYNOPSIS [--attribute-mapping=[ATTRIBUTE_MAPPING,...]] [--client-id=CLIENT_ID] [--description=DESCRIPTION] [--disabled] [--display-name=DISPLAY_NAME] [--issuer-uri=ISSUER_URI] + [--web-sso-additional-scopes=[WEB_SSO_ADDITIONAL_SCOPES,...]] [--web-sso-assertion-claims-behavior=WEB_SSO_ASSERTION_CLAIMS_BEHAVIOR] [--web-sso-response-type=WEB_SSO_RESPONSE_TYPE] [--clear-client-secret | --client-secret-value=CLIENT_SECRET_VALUE] @@ -29,9 +30,11 @@ EXAMPLES --description="My workforce pool provider description." \ --disabled --attribute-mapping="google.subject=assertion.sub" \ --attribute-condition="true" --client-id="client-id" \ + --client-secret-value="client-secret" \ --issuer-uri="https://test-idp.com" \ - --web-sso-response-type=id-token \ - --web-sso-assertion-claims-behavior=only-id-token-claims + --web-sso-response-type="code" \ + --web-sso-assertion-claims-behavior="merge-user-info-over-id-tok\ + en-claims" --web-sso-additional-scopes="groups,photos" POSITIONAL ARGUMENTS Workforce pool provider resource - The workforce pool provider to update. @@ -192,6 +195,14 @@ FLAGS --issuer-uri=ISSUER_URI The OIDC issuer URI. Must be a valid URI using the 'https' scheme. + --web-sso-additional-scopes=[WEB_SSO_ADDITIONAL_SCOPES,...] + Additional scopes to request for the OIDC authentication on top of + scopes requested by default. By default, the openid, profile and email + scopes that are supported by the identity provider are requested. + + Each additional scope may be at most 256 characters. A maximum of 10 + additional scopes may be configured. + --web-sso-assertion-claims-behavior=WEB_SSO_ASSERTION_CLAIMS_BEHAVIOR The behavior for how OIDC Claims are included in the assertion object used for attribute mapping and attribute condition. Use diff --git a/gcloud/memcache/instances/create b/gcloud/memcache/instances/create index b1a8daf40..c227cbe7e 100644 --- a/gcloud/memcache/instances/create +++ b/gcloud/memcache/instances/create @@ -10,6 +10,7 @@ SYNOPSIS [--maintenance-window-duration=MAINTENANCE_WINDOW_DURATION] [--maintenance-window-start-time=MAINTENANCE_WINDOW_START_TIME] [--memcached-version=MEMCACHED_VERSION] [--parameters=KEY=VALUE] + [--reserved-ip-range-id=[RESERVED_IP_RANGE_ID,...]] [--zones=[ZONES,...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -169,6 +170,11 @@ OPTIONAL FLAGS hash-algorithm This is an enum with accepted values of ["jenkins", "murmur3"]. + --reserved-ip-range-id=[RESERVED_IP_RANGE_ID,...] + Contains the name of allocated IP address ranges associated with the + private service access connection for example, "test-default" + associated with IP range 10.0.0.0/29. + --zones=[ZONES,...] List of zones for the memcache nodes. The nodes will be divided equally across the given zones up to --node-count value. If not provided, the diff --git a/gcloud/ml-engine/models/remove-iam-policy-binding b/gcloud/ml-engine/models/remove-iam-policy-binding index 416ab8270..426ffee16 100644 --- a/gcloud/ml-engine/models/remove-iam-policy-binding +++ b/gcloud/ml-engine/models/remove-iam-policy-binding @@ -25,7 +25,7 @@ EXAMPLES --member='allAuthenticatedUsers' --role='roles/ml.admin' See https://cloud.google.com/iam/docs/managing-policies for details of - policy role and principal types. + policy role and member types. POSITIONAL ARGUMENTS Model resource - The AI Platform model for which to remove IAM policy diff --git a/gcloud/projects/get-ancestors-iam-policy b/gcloud/projects/get-ancestors-iam-policy index 80beb1725..8e10c3e89 100644 --- a/gcloud/projects/get-ancestors-iam-policy +++ b/gcloud/projects/get-ancestors-iam-policy @@ -17,14 +17,13 @@ EXAMPLES $ gcloud projects get-ancestors-iam-policy example-project-id-1 POSITIONAL ARGUMENTS - Project id resource - ID for the project you want to get IAM policy for. - This represents a Cloud resource. + Project resource - ID for the project you want to get IAM policy for. This + represents a Cloud resource. This must be specified. PROJECT_ID - ID of the project_id or fully qualified identifier for the - project_id. + ID of the project or fully qualified identifier for the project. To set the project_id attribute: ▸ provide the argument project_id on the command line. diff --git a/gcloud/pubsub/subscriptions/create b/gcloud/pubsub/subscriptions/create index 85afa57de..470540660 100644 --- a/gcloud/pubsub/subscriptions/create +++ b/gcloud/pubsub/subscriptions/create @@ -25,6 +25,7 @@ SYNOPSIS [--dead-letter-topic=DEAD_LETTER_TOPIC : --dead-letter-topic-project=DEAD_LETTER_TOPIC_PROJECT]] [--max-retry-delay=MAX_RETRY_DELAY --min-retry-delay=MIN_RETRY_DELAY] + [--push-no-wrapper : --push-no-wrapper-write-metadata] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -271,6 +272,20 @@ OPTIONAL FLAGS of "s", "m", "h", and "d" for seconds, minutes, hours, and days, respectively. If the unit is omitted, seconds is assumed. + NoWrapper Config Options. + + --push-no-wrapper + When set, the message data is delivered directly as the HTTP body. + + This flag argument must be specified if any of the other arguments in + this group are specified. + + --push-no-wrapper-write-metadata + When true, writes the Pub/Sub message metadata to + x-goog-pubsub-: headers of the HTTP request. Writes the + Pub/Sub message attributes to : headers of the HTTP + request. + GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, diff --git a/gcloud/pubsub/subscriptions/modify-push-config b/gcloud/pubsub/subscriptions/modify-push-config index 6af29fda4..d67175b6f 100644 --- a/gcloud/pubsub/subscriptions/modify-push-config +++ b/gcloud/pubsub/subscriptions/modify-push-config @@ -7,6 +7,7 @@ SYNOPSIS --push-endpoint=PUSH_ENDPOINT [--push-auth-service-account=SERVICE_ACCOUNT_EMAIL] [--push-auth-token-audience=OPTIONAL_AUDIENCE_OVERRIDE] + [--push-no-wrapper : --push-no-wrapper-write-metadata] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -46,6 +47,20 @@ OPTIONAL FLAGS Audience used in the generated Open ID Connect token for authenticated push. If not specified, it will be set to the push-endpoint. + NoWrapper Config Options. + + --push-no-wrapper + When set, the message data is delivered directly as the HTTP body. + + This flag argument must be specified if any of the other arguments in + this group are specified. + + --push-no-wrapper-write-metadata + When true, writes the Pub/Sub message metadata to + x-goog-pubsub-: headers of the HTTP request. Writes the + Pub/Sub message attributes to : headers of the HTTP + request. + GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, diff --git a/gcloud/pubsub/subscriptions/update b/gcloud/pubsub/subscriptions/update index fb70e525d..8212bfbeb 100644 --- a/gcloud/pubsub/subscriptions/update +++ b/gcloud/pubsub/subscriptions/update @@ -26,6 +26,8 @@ SYNOPSIS [--dead-letter-topic=DEAD_LETTER_TOPIC : --dead-letter-topic-project=DEAD_LETTER_TOPIC_PROJECT]] [--clear-labels | --remove-labels=[KEY,...]] + [--clear-push-no-wrapper-config + | [--push-no-wrapper : --push-no-wrapper-write-metadata]] [--clear-retry-policy | --max-retry-delay=MAX_RETRY_DELAY --min-retry-delay=MIN_RETRY_DELAY] [GCLOUD_WIDE_FLAG ...] @@ -257,6 +259,25 @@ FLAGS silently ignored. If --update-labels is also specified then --update-labels is applied first. + At most one of these can be specified: + + --clear-push-no-wrapper-config + If set, clear the NoWrapper config from the subscription. + + NoWrapper Config Options. + + --push-no-wrapper + When set, the message data is delivered directly as the HTTP body. + + This flag argument must be specified if any of the other arguments + in this group are specified. + + --push-no-wrapper-write-metadata + When true, writes the Pub/Sub message metadata to + x-goog-pubsub-: headers of the HTTP request. Writes the + Pub/Sub message attributes to : headers of the HTTP + request. + At most one of these can be specified: --clear-retry-policy diff --git a/gcloud/scc/assets/describe b/gcloud/scc/assets/describe index 3d56c85c2..75037e0ac 100644 --- a/gcloud/scc/assets/describe +++ b/gcloud/scc/assets/describe @@ -7,6 +7,12 @@ SYNOPSIS (--asset=ASSET | --resource-name=RESOURCE_NAME) [GCLOUD_WIDE_FLAG ...] DESCRIPTION + (DEPRECATED) Security Command Center Asset APIs are deprecated and will be + removed on or after June 26, 2024. Use Cloud Asset Inventory instead + (gcloud asset) (https://cloud.google.com/sdk/gcloud/reference/asset). For + more information, see the deprecation notice at Assets Page + (https://cloud.google.com/security-command-center/docs/how-to-use-security-command-center#assets_page). + Describe an asset given its resource name or asset id. EXAMPLES diff --git a/gcloud/scc/assets/get-parent b/gcloud/scc/assets/get-parent index a56ec77d4..5689917a4 100644 --- a/gcloud/scc/assets/get-parent +++ b/gcloud/scc/assets/get-parent @@ -7,6 +7,12 @@ SYNOPSIS (--asset=ASSET | --resource-name=RESOURCE_NAME) [GCLOUD_WIDE_FLAG ...] DESCRIPTION + (DEPRECATED) Security Command Center Asset APIs are deprecated and will be + removed on or after June 26, 2024. Use Cloud Asset Inventory instead + (gcloud asset) (https://cloud.google.com/sdk/gcloud/reference/asset). For + more information, see the deprecation notice at Assets Page + (https://cloud.google.com/security-command-center/docs/how-to-use-security-command-center#assets_page). + Get the Parent for an asset given its resource name or asset id. EXAMPLES diff --git a/gcloud/scc/assets/get-project b/gcloud/scc/assets/get-project index 9abb5f191..1db012b78 100644 --- a/gcloud/scc/assets/get-project +++ b/gcloud/scc/assets/get-project @@ -7,6 +7,12 @@ SYNOPSIS (--asset=ASSET | --resource-name=RESOURCE_NAME) [GCLOUD_WIDE_FLAG ...] DESCRIPTION + (DEPRECATED) Security Command Center Asset APIs are deprecated and will be + removed on or after June 26, 2024. Use Cloud Asset Inventory instead + (gcloud asset) (https://cloud.google.com/sdk/gcloud/reference/asset). For + more information, see the deprecation notice at Assets Page + (https://cloud.google.com/security-command-center/docs/how-to-use-security-command-center#assets_page). + Get the Project for an asset given its resource name or asset id. EXAMPLES diff --git a/gcloud/scc/assets/group b/gcloud/scc/assets/group index 8c0bcb24f..df96f78fe 100644 --- a/gcloud/scc/assets/group +++ b/gcloud/scc/assets/group @@ -9,6 +9,12 @@ SYNOPSIS [GCLOUD_WIDE_FLAG ...] DESCRIPTION + (DEPRECATED) Security Command Center Asset APIs are deprecated and will be + removed on or after June 26, 2024. Use Cloud Asset Inventory instead + (gcloud asset) (https://cloud.google.com/sdk/gcloud/reference/asset). For + more information, see the deprecation notice at Assets Page + (https://cloud.google.com/security-command-center/docs/how-to-use-security-command-center#assets_page). + Filter an organization's assets and groups them by their specified properties. diff --git a/gcloud/scc/assets/help b/gcloud/scc/assets/help index a445d2bf4..9e8eea45d 100644 --- a/gcloud/scc/assets/help +++ b/gcloud/scc/assets/help @@ -16,26 +16,28 @@ COMMANDS COMMAND is one of the following: describe - Describe an asset given its resource name or asset id. + (DEPRECATED) Describe an asset given its resource name or asset id. get-parent - Get the Parent for an asset given its resource name or asset id. + (DEPRECATED) Get the Parent for an asset given its resource name or + asset id. get-project - Get the Project for an asset given its resource name or asset id. + (DEPRECATED) Get the Project for an asset given its resource name or + asset id. group - Filter an organization's assets and groups them by their specified - properties. + (DEPRECATED) Filter an organization's assets and groups them by their + specified properties. list - List Cloud Security Command Center assets. + (DEPRECATED) List Cloud Security Command Center assets. list-marks - List an assets's security marks. + (DEPRECATED) List an assets's security marks. run-discovery - Scan an organization for new/modified/deleted assets. + (DEPRECATED) Scan an organization for new/modified/deleted assets. update-marks Update Cloud Security Command Center asset's security marks. diff --git a/gcloud/scc/assets/list b/gcloud/scc/assets/list index b72770471..594e57c48 100644 --- a/gcloud/scc/assets/list +++ b/gcloud/scc/assets/list @@ -9,6 +9,12 @@ SYNOPSIS [GCLOUD_WIDE_FLAG ...] DESCRIPTION + (DEPRECATED) Security Command Center Asset APIs are deprecated and will be + removed on or after June 26, 2024. Use Cloud Asset Inventory instead + (gcloud asset) (https://cloud.google.com/sdk/gcloud/reference/asset). For + more information, see the deprecation notice at Assets Page + (https://cloud.google.com/security-command-center/docs/how-to-use-security-command-center#assets_page). + List Cloud Security Command Center assets. EXAMPLES diff --git a/gcloud/scc/assets/list-marks b/gcloud/scc/assets/list-marks index c0c4e48b7..0b88ad76a 100644 --- a/gcloud/scc/assets/list-marks +++ b/gcloud/scc/assets/list-marks @@ -8,6 +8,12 @@ SYNOPSIS [GCLOUD_WIDE_FLAG ...] DESCRIPTION + (DEPRECATED) Security Command Center Asset APIs are deprecated and will be + removed on or after June 26, 2024. Use Cloud Asset Inventory instead + (gcloud asset) (https://cloud.google.com/sdk/gcloud/reference/asset). For + more information, see the deprecation notice at Assets Page + (https://cloud.google.com/security-command-center/docs/how-to-use-security-command-center#assets_page). + List an assets's security marks. EXAMPLES diff --git a/gcloud/scc/assets/run-discovery b/gcloud/scc/assets/run-discovery index 4a403b077..99d181966 100644 --- a/gcloud/scc/assets/run-discovery +++ b/gcloud/scc/assets/run-discovery @@ -6,6 +6,12 @@ SYNOPSIS gcloud scc assets run-discovery [ORGANIZATION] [GCLOUD_WIDE_FLAG ...] DESCRIPTION + (DEPRECATED) Security Command Center Asset APIs are deprecated and will be + removed on or after June 26, 2024. Use Cloud Asset Inventory instead + (gcloud asset) (https://cloud.google.com/sdk/gcloud/reference/asset). For + more information, see the deprecation notice at Assets Page + (https://cloud.google.com/security-command-center/docs/how-to-use-security-command-center#assets_page). + Scan an organization for new/modified/deleted assets. Note that this API can only be called with limited frequency for an organization. If it is called too frequently the caller will receive a TOO_MANY_REQUESTS error. diff --git a/gcloud/spanner/databases/execute-sql b/gcloud/spanner/databases/execute-sql index 31b5e7412..a6f504056 100644 --- a/gcloud/spanner/databases/execute-sql +++ b/gcloud/spanner/databases/execute-sql @@ -5,7 +5,7 @@ NAME SYNOPSIS gcloud spanner databases execute-sql (DATABASE : --instance=INSTANCE) --sql=SQL [--database-role=DATABASE_ROLE] [--enable-partitioned-dml] - [--query-mode=QUERY_MODE; default="NORMAL"] + [--priority=PRIORITY] [--query-mode=QUERY_MODE; default="NORMAL"] [--timeout=TIMEOUT; default="10m"] [--read-timestamp=TIMESTAMP | --strong] [GCLOUD_WIDE_FLAG ...] @@ -64,6 +64,10 @@ OPTIONAL FLAGS --enable-partitioned-dml Execute DML statement using Partitioned DML + --priority=PRIORITY + The priority for the execute SQL request. PRIORITY must be one of: + high, low, medium, unspecified. + --query-mode=QUERY_MODE; default="NORMAL" Mode in which the query must be processed. QUERY_MODE must be one of: diff --git a/gcloud/sql/instances/create b/gcloud/sql/instances/create index 4dc038550..7f9151567 100644 --- a/gcloud/sql/instances/create +++ b/gcloud/sql/instances/create @@ -38,6 +38,7 @@ SYNOPSIS [--password-policy-min-length=PASSWORD_POLICY_MIN_LENGTH] [--password-policy-password-change-interval=PASSWORD_POLICY_PASSWORD_CHANGE_INTERVAL] [--password-policy-reuse-interval=PASSWORD_POLICY_REUSE_INTERVAL] + [--[no-]recreate-replicas-on-primary-crash] [--replica-type=REPLICA_TYPE] [--replication=REPLICATION] [--require-ssl] [--retained-backups-count=RETAINED_BACKUPS_COUNT] [--retained-transaction-log-days=RETAINED_TRANSACTION_LOG_DAYS] @@ -338,6 +339,14 @@ FLAGS Number of previous passwords that cannot be reused. The valid range is 0 to 100. + --[no-]recreate-replicas-on-primary-crash + Allow/Disallow replica recreation when a primary MySQL instance + operating in reduced durability mode crashes. Not recreating the + replicas might lead to data inconsistencies between the primary and its + replicas. This setting is only applicable for MySQL instances and is + enabled by default. Use --recreate-replicas-on-primary-crash to enable + and --no-recreate-replicas-on-primary-crash to disable. + --replica-type=REPLICA_TYPE The type of replica to create. REPLICA_TYPE must be one of: READ, FAILOVER. diff --git a/gcloud/sql/instances/patch b/gcloud/sql/instances/patch index 3009a4729..d079889e7 100644 --- a/gcloud/sql/instances/patch +++ b/gcloud/sql/instances/patch @@ -33,6 +33,7 @@ SYNOPSIS [--password-policy-password-change-interval=PASSWORD_POLICY_PASSWORD_CHANGE_INTERVAL] [--password-policy-reuse-interval=PASSWORD_POLICY_REUSE_INTERVAL] [--pricing-plan=PRICING_PLAN, -p PRICING_PLAN] + [--[no-]recreate-replicas-on-primary-crash] [--remove-deny-maintenance-period] [--replication=REPLICATION] [--[no-]require-ssl] [--[no-]storage-auto-increase] [--storage-size=STORAGE_SIZE] [--threads-per-core=THREADS_PER_CORE] @@ -302,6 +303,14 @@ FLAGS First Generation instances only. The pricing plan for this instance. PRICING_PLAN must be one of: PER_USE, PACKAGE. + --[no-]recreate-replicas-on-primary-crash + Allow/Disallow replica recreation when a primary MySQL instance + operating in reduced durability mode crashes. Not recreating the + replicas might lead to data inconsistencies between the primary and its + replicas. This setting is only applicable for MySQL instances and is + enabled by default. Use --recreate-replicas-on-primary-crash to enable + and --no-recreate-replicas-on-primary-crash to disable. + --remove-deny-maintenance-period Removes the user-specified deny maintenance period. diff --git a/gcloud/storage/buckets/describe b/gcloud/storage/buckets/describe index ec03c5503..782f2ab28 100644 --- a/gcloud/storage/buckets/describe +++ b/gcloud/storage/buckets/describe @@ -3,7 +3,7 @@ NAME SYNOPSIS gcloud storage buckets describe URL [--additional-headers=HEADER=VALUE] - [GCLOUD_WIDE_FLAG ...] + [--raw] [GCLOUD_WIDE_FLAG ...] DESCRIPTION Describe a Cloud Storage bucket. @@ -29,6 +29,10 @@ FLAGS Overrides the default storage/additional_headers property value for this command invocation. + --raw + Shows metadata in the format returned by the API instead of + standardizing it. + GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, diff --git a/gcloud/storage/buckets/list b/gcloud/storage/buckets/list index 25bfb4560..6de09aa17 100644 --- a/gcloud/storage/buckets/list +++ b/gcloud/storage/buckets/list @@ -3,7 +3,7 @@ NAME SYNOPSIS gcloud storage buckets list [URLS ...] [--additional-headers=HEADER=VALUE] - [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--raw] [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -33,6 +33,10 @@ FLAGS Overrides the default storage/additional_headers property value for this command invocation. + --raw + Shows metadata in the format returned by the API instead of + standardizing it. + LIST COMMAND FLAGS --filter=EXPRESSION Apply a Boolean filter EXPRESSION to each resource item to be listed. diff --git a/gcloud/storage/buckets/update b/gcloud/storage/buckets/update index ac12b3d92..71e78a497 100644 --- a/gcloud/storage/buckets/update +++ b/gcloud/storage/buckets/update @@ -226,7 +226,8 @@ FLAGS At most one of these can be specified: --clear-log-bucket - Clears logging bucket receiving the usage current bucket's data. + Clears logging bucket receiving the usage current bucket's data and + disables usage logging. --log-bucket=LOG_BUCKET Enables usage logging of the bucket, outputting log files to the @@ -245,6 +246,7 @@ FLAGS Specifies the object prefix for logging activity to the log bucket. The default prefix is the bucket name. All read and write activity to objects in the bucket will be logged for objects matching the prefix. + If usage logging is not enabled this flag will have no effect. At most one of these can be specified: diff --git a/gcloud/storage/du b/gcloud/storage/du new file mode 100644 index 000000000..fc75a7364 --- /dev/null +++ b/gcloud/storage/du @@ -0,0 +1,100 @@ +NAME + gcloud storage du - displays the amount of space in bytes used up storage + resources + +SYNOPSIS + gcloud storage du [URL ...] [--additional-headers=HEADER=VALUE] + [--all-versions, -a] + [--exclude-name-pattern=EXCLUDE_NAME_PATTERN, -e EXCLUDE_NAME_PATTERN] + [--exclude-name-pattern-file=EXCLUDE_NAME_PATTERN_FILE, + -X EXCLUDE_NAME_PATTERN_FILE] [--readable-sizes, -r] + [--summarize, -s] [--total, -c] [--zero-terminator, -0] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Displays the amount of space in bytes used up by the objects in a bucket, + subdirectory, or project. + +EXAMPLES + To list the size of each object in a bucket: + + $ gcloud storage du gs://bucketname + + To list the size of each object in the prefix subdirectory: + + $ gcloud storage du gs://bucketname/prefix/* + + To print the total number of bytes in a bucket in human-readable form: + + $ gcloud storage du -ch gs://bucketname + + To see a summary of the total number of bytes in two given buckets: + + $ gcloud storage du -s gs://bucket1 gs://bucket2 + + To list the size of each object in a bucket with Object Versioning enabled, + including noncurrent objects: + + $ gcloud storage du -a gs://bucketname + + To list the size of each object in a bucket, except objects that end in + ".bak", with each object printed ending in a null byte: + + $ gcloud storage du -e "*.bak" -0 gs://bucketname + + To list the size of each bucket in a project and the total size of the + project: + + $ gcloud storage du --summarize --readable-sizes --total + +POSITIONAL ARGUMENTS + [URL ...] + The url of objects to list. + +FLAGS + --additional-headers=HEADER=VALUE + Includes arbitrary headers in storage API calls. Accepts a comma + separated list of key=value pairs, e.g. header1=value1,header2=value2. + Overrides the default storage/additional_headers property value for + this command invocation. + + --all-versions, -a + Includes noncurrent object versions for a bucket with Object Versioning + enabled. Also prints the generation and metageneration number for each + listed object. + + --exclude-name-pattern=EXCLUDE_NAME_PATTERN, -e EXCLUDE_NAME_PATTERN + Exclude a pattern from the report. Example: -e ".o" excludes any object + that ends in ".o". Can be specified multiple times. + + --exclude-name-pattern-file=EXCLUDE_NAME_PATTERN_FILE, -X EXCLUDE_NAME_PATTERN_FILE + Similar to -e, but excludes patterns from the given file. The patterns + to exclude should be listed one per line. + + --readable-sizes, -r + Prints object sizes in human-readable format. For example, 1 KiB, 234 + MiB, or 2GiB. + + --summarize, -s + Displays only the summary for each argument. + + --total, -c + Includes a total size of all input sources. + + --zero-terminator, -0 + Ends each output line with a 0 byte rather than a newline. You can use + this to make the output machine-readable. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This variant is also available: + + $ gcloud alpha storage du + diff --git a/gcloud/storage/help b/gcloud/storage/help index 48bb00815..0071c82c3 100644 --- a/gcloud/storage/help +++ b/gcloud/storage/help @@ -23,6 +23,9 @@ GROUPS buckets Manage Cloud Storage buckets. + hmac + Manage Cloud Storage service account HMAC keys. + insights Manage Cloud Storage inventory reports. @@ -38,6 +41,9 @@ COMMANDS cp Upload, download, and copy Cloud Storage objects. + du + Displays the amount of space in bytes used up storage resources. + hash Calculates hashes on local or cloud files. @@ -57,6 +63,9 @@ COMMANDS Manage a project's Cloud Storage service agent, which is used to perform Cloud KMS operations. + sign-url + Generate a URL with embedded authentication that can be used by anyone. + NOTES This variant is also available: diff --git a/gcloud/storage/hmac/create b/gcloud/storage/hmac/create new file mode 100644 index 000000000..ed8b4c180 --- /dev/null +++ b/gcloud/storage/hmac/create @@ -0,0 +1,35 @@ +NAME + gcloud storage hmac create - add a service account HMAC + +SYNOPSIS + gcloud storage hmac create SERVICE_ACCOUNT [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + gcloud storage hmac create command creates an HMAC key for the specified + service account. The secret key material is only available upon creation, + so be sure to store the returned secret along with the access_id. + +EXAMPLES + To create an HMAC key for + test.service.account@test_project.iam.gserviceaccount.com: + + $ gcloud storage hmac create \ + test.service.account@test_project.iam.gserviceaccount.com + +POSITIONAL ARGUMENTS + SERVICE_ACCOUNT + The service account email. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This variant is also available: + + $ gcloud alpha storage hmac create + diff --git a/gcloud/storage/hmac/delete b/gcloud/storage/hmac/delete new file mode 100644 index 000000000..b5a640bdd --- /dev/null +++ b/gcloud/storage/hmac/delete @@ -0,0 +1,37 @@ +NAME + gcloud storage hmac delete - remove a service account HMAC + +SYNOPSIS + gcloud storage hmac delete ACCESS_ID [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + gcloud storage hmac delete permanently deletes the specified HMAC key. Note + that keys must be updated to be in the INACTIVE state before they can be + deleted. + +EXAMPLES + To delete a specific HMAC key: + + $ gcloud storage hmac delete GOOG56JBMFZX6PMPTQ62VD2 + + To be prompted for HMAC keys to delete: + + $ gcloud storage hmac delete + +POSITIONAL ARGUMENTS + ACCESS_ID + Access ID for HMAC key to delete. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This variant is also available: + + $ gcloud alpha storage hmac delete + diff --git a/gcloud/storage/hmac/describe b/gcloud/storage/hmac/describe new file mode 100644 index 000000000..60a6de1c5 --- /dev/null +++ b/gcloud/storage/hmac/describe @@ -0,0 +1,37 @@ +NAME + gcloud storage hmac describe - describes a service account HMAC key + +SYNOPSIS + gcloud storage hmac describe ACCESS_ID [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + gcloud storage hmac describe retrieves the specified HMAC key's metadata. + Note that there is no option to retrieve a key's secret material after it + has been created. + +EXAMPLES + The following command retrieves the HMAC key's metadata: + + $ gcloud storage hmac describe GOOG56JBMFZX6PMPTQ62VD2 + + Note GOOG56JBMFZX6PMPTQ62VD2 is the ACCESS_ID of the HMAC key. + +POSITIONAL ARGUMENTS + ACCESS_ID + The Access ID + (https://cloud.google.com/storage/docs/authentication/hmackeys#overview) + of the HMAC key + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This variant is also available: + + $ gcloud alpha storage hmac describe + diff --git a/gcloud/storage/hmac/help b/gcloud/storage/hmac/help new file mode 100644 index 000000000..e4d41cec4 --- /dev/null +++ b/gcloud/storage/hmac/help @@ -0,0 +1,37 @@ +NAME + gcloud storage hmac - manage Cloud Storage service account HMAC keys + +SYNOPSIS + gcloud storage hmac COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Manage Cloud Storage service account HMAC keys. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + create + Add a service account HMAC. + + delete + Remove a service account HMAC. + + describe + Describes a service account HMAC key. + + list + List service account HMAC keys. + + update + Change the status of a service account HMAC. + +NOTES + This variant is also available: + + $ gcloud alpha storage hmac + diff --git a/gcloud/storage/hmac/list b/gcloud/storage/hmac/list new file mode 100644 index 000000000..1373a449d --- /dev/null +++ b/gcloud/storage/hmac/list @@ -0,0 +1,80 @@ +NAME + gcloud storage hmac list - list service account HMAC keys + +SYNOPSIS + gcloud storage hmac list [--all, -a] [--long, -l] + [--service-account=SERVICE_ACCOUNT, -u SERVICE_ACCOUNT] + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + gcloud storage hmac list lists the HMAC key metadata for keys in the + current project. + +EXAMPLES + To show metadata for all keys, including recently deleted keys: + + $ gcloud storage hmac list --all --long + + To list only HMAC keys belonging to the service account + test.sa@test.iam.gserviceaccount.com: + + $ gcloud storage hmac list \ + --service-account=test.sa@test.iam.gserviceaccount.com + +FLAGS + --all, -a + Shows all keys, including recently deleted keys. + + --long, -l + Use long listing format, showing the full metadata for each key + excluding the secret. + + --service-account=SERVICE_ACCOUNT, -u SERVICE_ACCOUNT + Filter keys for the provided service account email. + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + + --uri + Print a list of resource URIs instead of the default output, and change + the command output to a list of URIs. If this flag is used with + --format, the formatting is applied on this URI list. To display URIs + alongside other keys instead, use the uri() transform. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This variant is also available: + + $ gcloud alpha storage hmac list + diff --git a/gcloud/storage/hmac/update b/gcloud/storage/hmac/update new file mode 100644 index 000000000..0551d0e20 --- /dev/null +++ b/gcloud/storage/hmac/update @@ -0,0 +1,55 @@ +NAME + gcloud storage hmac update - change the status of a service account HMAC + +SYNOPSIS + gcloud storage hmac update ACCESS_ID (--activate | --deactivate) + [--etag=ETAG, -e ETAG] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + gcloud storage hmac update sets the state of the specified key. Valid state + arguments are ACTIVE and INACTIVE. To set a key to state DELETED, use + gcloud storage hmac delete on an INACTIVE key. If an etag is set in the + command, it will only succeed if the provided etag matches the etag of the + stored key. + +EXAMPLES + To activate an HMAC key: + + $ gcloud storage hmac update GOOG56JBMFZX6PMPTQ62VD2 --activate + + To set the state of an HMAC key to INACTIVE provided its etag is M42da=: + + $ gcloud storage hmac update GOOG56JBMFZX6PMPTQ62VD2 --deactivate \ + --etag=M42da= + +POSITIONAL ARGUMENTS + ACCESS_ID + Access ID for HMAC key to update. + +REQUIRED FLAGS + Exactly one of these must be specified: + + --activate + Sets the state of the specified key to ACTIVE. + + --deactivate + Sets the state of the specified key to INACTIVE. + +OPTIONAL FLAGS + --etag=ETAG, -e ETAG + If provided, the update will only be performed if the specified etag + matches the etag of the stored key. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This variant is also available: + + $ gcloud alpha storage hmac update + diff --git a/gcloud/storage/objects/describe b/gcloud/storage/objects/describe index 21e1cc6a9..312ae17be 100644 --- a/gcloud/storage/objects/describe +++ b/gcloud/storage/objects/describe @@ -3,7 +3,7 @@ NAME SYNOPSIS gcloud storage objects describe URL [--additional-headers=HEADER=VALUE] - [--fetch-encrypted-object-hashes] + [--fetch-encrypted-object-hashes] [--raw] [--decryption-keys=[DECRYPTION_KEY,...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -37,6 +37,10 @@ FLAGS matching decryption key is present on the system, this flag retries the GET request with the key. + --raw + Shows metadata in the format returned by the API instead of + standardizing it. + ENCRYPTION FLAGS --decryption-keys=[DECRYPTION_KEY,...] A comma-separated list of customer-supplied encryption keys (RFC 4648 diff --git a/gcloud/storage/objects/list b/gcloud/storage/objects/list index 9aab408ab..4166ac853 100644 --- a/gcloud/storage/objects/list +++ b/gcloud/storage/objects/list @@ -4,9 +4,9 @@ NAME SYNOPSIS gcloud storage objects list URLS [URLS ...] [--additional-headers=HEADER=VALUE] [--fetch-encrypted-object-hashes] - [--stat] [--decryption-keys=[DECRYPTION_KEY,...]] [--filter=EXPRESSION] - [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] - [GCLOUD_WIDE_FLAG ...] + [--raw] [--stat] [--decryption-keys=[DECRYPTION_KEY,...]] + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] DESCRIPTION List Cloud Storage objects. @@ -45,6 +45,10 @@ FLAGS encrypted object in order to fetch hashes. This can significantly increase the cost of the command. + --raw + Shows metadata in the format returned by the API instead of + standardizing it. + --stat Emulates gsutil stat-style behavior. Does not show past object versions and changes output format. diff --git a/gcloud/storage/sign-url b/gcloud/storage/sign-url new file mode 100644 index 000000000..a7c27fc68 --- /dev/null +++ b/gcloud/storage/sign-url @@ -0,0 +1,111 @@ +NAME + gcloud storage sign-url - generate a URL with embedded authentication that + can be used by anyone + +SYNOPSIS + gcloud storage sign-url URL [URL ...] --private-key-file=PRIVATE_KEY_FILE + [--duration=DURATION, -d DURATION; default=3600] + [--headers=[KEY=VALUE,...]] + [--http-verb=HTTP_VERB, -m HTTP_VERB; default="GET"] + [--private-key-password=PRIVATE_KEY_PASSWORD, -p PRIVATE_KEY_PASSWORD] + [--query-params=[KEY=VALUE,...]] [--region=REGION, -r REGION] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + gcloud storage sign-url will generate a signed URL that embeds + authentication data so the URL can be used by someone who does not have a + Google account. Please see the Signed URLs documentation + (https://cloud.google.com/storage/docs/access-control/signed-urls) for + background about signed URLs. + + Note, gcloud storage sign-url does not support operations on + sub-directories. For example, unless you have an object named + some-directory/ stored inside the bucket some-bucket, the following command + returns an error: gcloud storage sign-url gs://some-bucket/some-directory/. + +EXAMPLES + To create a signed url for downloading an object valid for 10 minutes: + + $ gcloud storage sign-url gs://my-bucket/file.txt --duration=10m \ + --private-key-file=key.json + + To create a signed url that will bill to my-billing-project: + + $ gcloud storage sign-url gs://my-bucket/file.txt \ + --query-params=userProject=my-billing-project \ + --private-key-file=key.json + + To create a signed url, valid for one hour, for uploading a plain text file + via HTTP PUT: + + $ gcloud storage sign-url gs://my-bucket/file.txt --http-verb=PUT \ + --duration=1h --headers=content-type=text/plain \ + --private-key-file=key.json + + To create a signed URL that initiates a resumable upload for a plain text + file: + + $ gcloud storage sign-url gs://my-bucket/file.txt --http-verb=POST \ + --headers=x-goog-resumable=start,content-type=text/plain \ + --private-key-file=key.json + +POSITIONAL ARGUMENTS + URL [URL ...] + The URLs to be signed. May contain wildcards. + +REQUIRED FLAGS + --private-key-file=PRIVATE_KEY_FILE + The service account private key used to generate the cryptographic + signature for the generated URL. Must be in PKCS12 or JSON format. If + encrypted, will prompt for the passphrase used to protect the private + key file (default notasecret). + +OPTIONAL FLAGS + --duration=DURATION, -d DURATION; default=3600 + Specifies the duration that the signed url should be valid for, default + duration is 1 hour. For example 10s for 10 seconds. See $ gcloud topic + datetimes for information on duration formats. + + The max duration allowed is 7 days when PRIVATE_KEY_FILE is used. + + --headers=[KEY=VALUE,...] + Specifies the headers to be used in the signed request. Possible + headers are listed in the XML API's documentation: + https://cloud.google.com/storage/docs/xml-api/reference-headers#headers + + --http-verb=HTTP_VERB, -m HTTP_VERB; default="GET" + Specifies the HTTP verb to be authorized for use with the signed URL, + default is GET. When using a signed URL to start a resumable upload + session, you will need to specify the x-goog-resumable:start header in + the request or else signature validation will fail. + + --private-key-password=PRIVATE_KEY_PASSWORD, -p PRIVATE_KEY_PASSWORD + Specifies the private key password instead of prompting. + + --query-params=[KEY=VALUE,...] + Specifies the query parameters to be used in the signed request. + Possible query parameters are listed in the XML API's documentation: + https://cloud.google.com/storage/docs/xml-api/reference-headers#query + + --region=REGION, -r REGION + Specifies the region in which the resources for which you are creating + signed URLs are stored. + + Default value is auto which will cause gcloud storage sign-url to fetch + the region for the resource. When auto-detecting the region, the + current user's credentials, not the credentials from PRIVATE_KEY_FILE, + are used to fetch the bucket's metadata. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This variant is also available: + + $ gcloud alpha storage sign-url + diff --git a/gcloud/vmware/private-clouds/clusters/update b/gcloud/vmware/private-clouds/clusters/update index 67c1d68bc..358d81390 100644 --- a/gcloud/vmware/private-clouds/clusters/update +++ b/gcloud/vmware/private-clouds/clusters/update @@ -16,7 +16,7 @@ DESCRIPTION EXAMPLES To resize a cluster called my-cluster in private cloud my-private-cloud and - zone us-west2-a to have ``3'' nodes, run: + zone us-west2-a to have 3 nodes, run: $ gcloud vmware private-clouds clusters update my-cluster \ --location=us-west2-a --project=my-project \ diff --git a/gcloud/workbench/help b/gcloud/workbench/help new file mode 100644 index 000000000..382652f37 --- /dev/null +++ b/gcloud/workbench/help @@ -0,0 +1,19 @@ +NAME + gcloud workbench - workbench Command Group + +SYNOPSIS + gcloud workbench GROUP [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Workbench Command Group. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +GROUPS + GROUP is one of the following: + + instances + Workbench Instances command group. diff --git a/gcloud/workbench/instances/help b/gcloud/workbench/instances/help new file mode 100644 index 000000000..d6fc8b7b7 --- /dev/null +++ b/gcloud/workbench/instances/help @@ -0,0 +1,19 @@ +NAME + gcloud workbench instances - workbench Instances command group + +SYNOPSIS + gcloud workbench instances COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Workbench Instances command group. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + list + Request for listing instances. diff --git a/gcloud/alpha/compute/os-config/patch-deployments/list b/gcloud/workbench/instances/list similarity index 73% rename from gcloud/alpha/compute/os-config/patch-deployments/list rename to gcloud/workbench/instances/list index 68a0ef84c..e7dd1c529 100644 --- a/gcloud/alpha/compute/os-config/patch-deployments/list +++ b/gcloud/workbench/instances/list @@ -1,19 +1,23 @@ NAME - gcloud alpha compute os-config patch-deployments list - list patch - deployments in a project + gcloud workbench instances list - request for listing instances SYNOPSIS - gcloud alpha compute os-config patch-deployments list [--filter=EXPRESSION] + gcloud workbench instances list [--location=LOCATION] [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) List patch deployments in a project. + Request for listing instances. EXAMPLES - To list all patch deployments in the current project, run: + To list instances in a particular location, run: - $ gcloud alpha compute os-config patch-deployments list + $ gcloud workbench instances list --location=us-central1-a + +FLAGS + --location=LOCATION + Google Cloud location of this environment + https://cloud.google.com/compute/docs/regions-zones/#locations. LIST COMMAND FLAGS --filter=EXPRESSION @@ -54,14 +58,3 @@ GCLOUD WIDE FLAGS --trace-token, --user-output-enabled, --verbosity. Run $ gcloud help for details. - -NOTES - This command is currently in alpha and might change without notice. If this - command fails with API permission errors despite specifying the correct - project, you might be trying to access an API with an invitation-only early - access allowlist. These variants are also available: - - $ gcloud compute os-config patch-deployments list - - $ gcloud beta compute os-config patch-deployments list -