From 154ebc873d0d977641521f548ff19f6e8ff1b958 Mon Sep 17 00:00:00 2001 From: Automated Date: Wed, 15 Oct 2025 10:52:53 +0000 Subject: [PATCH] gcloud: Wed Oct 15 10:52:53 UTC 2025 --- gcloud/_version | 8 +- gcloud/alpha/biglake/iceberg/catalogs/create | 76 +++++++ .../biglake/iceberg/catalogs/get-iam-policy | 76 +++++++ gcloud/alpha/biglake/iceberg/catalogs/help | 9 + .../biglake/iceberg/catalogs/set-iam-policy | 58 ++++++ gcloud/alpha/biglake/iceberg/catalogs/update | 13 +- gcloud/alpha/biglake/iceberg/help | 6 + .../biglake/iceberg/namespaces/get-iam-policy | 90 +++++++++ gcloud/alpha/biglake/iceberg/namespaces/help | 32 +++ .../biglake/iceberg/namespaces/set-iam-policy | 70 +++++++ .../biglake/iceberg/tables/get-iam-policy | 99 ++++++++++ gcloud/alpha/biglake/iceberg/tables/help | 30 +++ .../biglake/iceberg/tables/set-iam-policy | 79 ++++++++ gcloud/alpha/bigtable/operations/list | 13 ++ gcloud/alpha/compute/backend-services/create | 2 +- gcloud/alpha/compute/backend-services/update | 19 +- .../compute/composite-health-checks/create | 96 +++++++++ .../compute/composite-health-checks/delete | 76 +++++++ .../compute/composite-health-checks/describe | 71 +++++++ .../compute/composite-health-checks/help | 41 ++++ .../compute/composite-health-checks}/list | 58 +++--- .../compute/composite-health-checks/update | 98 ++++++++++ .../health-aggregation-policies/create | 116 +++++++++++ .../health-aggregation-policies/delete | 77 ++++++++ .../health-aggregation-policies/describe | 72 +++++++ .../compute/health-aggregation-policies/help | 42 ++++ .../list | 60 +++--- .../health-aggregation-policies/update | 111 +++++++++++ gcloud/alpha/compute/help | 9 + gcloud/alpha/compute/instances/help | 4 - gcloud/alpha/compute/instances/move | 98 ---------- .../interconnects/cross-site-networks/create | 7 +- .../interconnects/cross-site-networks/delete | 19 +- .../cross-site-networks/describe | 17 +- .../interconnects/cross-site-networks/help | 4 +- .../interconnects/cross-site-networks/list | 4 +- .../interconnects/cross-site-networks/update | 15 +- .../interconnects/wire-groups/add-endpoint | 11 +- .../wire-groups/add-interconnect | 16 +- .../compute/interconnects/wire-groups/create | 10 +- .../compute/interconnects/wire-groups/delete | 16 +- .../interconnects/wire-groups/describe | 16 +- .../compute/interconnects/wire-groups/help | 4 +- .../compute/interconnects/wire-groups/list | 4 +- .../interconnects/wire-groups/remove-endpoint | 12 +- .../wire-groups/remove-interconnect | 13 +- .../compute/interconnects/wire-groups/update | 35 +++- .../network-policies/associations/create | 52 +++++ .../network-policies/associations/delete | 47 +++++ .../network-policies/associations/describe | 47 +++++ .../network-policies/associations/help | 35 ++++ gcloud/alpha/compute/network-policies/create | 46 +++++ gcloud/alpha/compute/network-policies/delete | 42 ++++ .../alpha/compute/network-policies/describe | 42 ++++ gcloud/alpha/compute/network-policies/help | 50 +++++ .../list | 54 ++--- .../traffic-classification-rules/create | 103 ++++++++++ .../traffic-classification-rules/delete | 47 +++++ .../traffic-classification-rules/describe | 47 +++++ .../traffic-classification-rules/help | 37 ++++ .../traffic-classification-rules/update | 98 ++++++++++ gcloud/alpha/compute/network-policies/update | 46 +++++ .../org-security-policies/associations/create | 4 +- .../org-security-policies/associations/delete | 4 +- .../org-security-policies/associations/help | 4 +- .../org-security-policies/associations/list | 4 +- .../compute/org-security-policies/copy-rules | 4 +- .../compute/org-security-policies/create | 4 +- .../compute/org-security-policies/delete | 4 +- .../compute/org-security-policies/describe | 4 +- .../alpha/compute/org-security-policies/help | 4 +- .../alpha/compute/org-security-policies/list | 4 +- .../compute/org-security-policies/list-rules | 4 +- .../alpha/compute/org-security-policies/move | 4 +- .../rules/add-preconfig-waf-exclusion | 5 +- .../org-security-policies/rules/create | 4 +- .../org-security-policies/rules/delete | 4 +- .../org-security-policies/rules/describe | 4 +- .../compute/org-security-policies/rules/help | 4 +- .../rules/remove-preconfig-waf-exclusion | 5 +- .../org-security-policies/rules/update | 4 +- .../compute/org-security-policies/update | 4 +- .../alpha/compute/preview-features/describe | 4 +- gcloud/alpha/compute/preview-features/help | 4 +- gcloud/alpha/compute/preview-features/list | 4 +- gcloud/alpha/compute/preview-features/update | 4 +- .../compute/reservations/sub-blocks/help | 2 +- .../sub-blocks/report-subblock-as-faulty | 24 ++- .../alpha/compute/service-attachments/update | 23 +-- gcloud/alpha/compute/tpus/create | 185 ------------------ gcloud/alpha/compute/tpus/delete | 79 -------- gcloud/alpha/compute/tpus/describe | 74 ------- .../compute/tpus/execution-groups/create | 165 ---------------- .../compute/tpus/execution-groups/delete | 75 ------- .../compute/tpus/execution-groups/describe | 66 ------- .../alpha/compute/tpus/execution-groups/help | 53 ----- .../compute/tpus/execution-groups/resume | 91 --------- .../compute/tpus/execution-groups/suspend | 64 ------ gcloud/alpha/compute/tpus/help | 28 --- gcloud/alpha/compute/tpus/reimage | 86 -------- gcloud/alpha/compute/tpus/start | 78 -------- gcloud/alpha/compute/tpus/stop | 78 -------- .../compute/zone-vm-extension-policies/create | 8 +- .../compute/zone-vm-extension-policies/update | 8 +- gcloud/alpha/container/clusters/create | 11 +- gcloud/alpha/container/clusters/create-auto | 12 +- gcloud/alpha/container/clusters/update | 9 + gcloud/alpha/container/node-pools/create | 18 ++ gcloud/alpha/container/node-pools/update | 24 ++- .../design-center/spaces/applications/create | 47 ++++- .../design-center/spaces/applications/update | 32 ++- gcloud/alpha/firestore/databases/help | 4 + gcloud/alpha/firestore/databases/ping | 40 ++++ .../providers/scim-tenants/delete | 6 +- gcloud/alpha/looker/instances/update | 24 +++ gcloud/alpha/memorystore/instances/update | 15 +- gcloud/alpha/redis/clusters/update | 6 +- .../alpha/resource-manager/tags/values/create | 12 +- gcloud/alpha/run/deploy | 20 ++ gcloud/alpha/run/jobs/create | 6 + gcloud/alpha/run/jobs/deploy | 6 + gcloud/alpha/run/jobs/update | 6 + gcloud/alpha/run/multi-region-services/help | 4 + gcloud/alpha/run/multi-region-services/update | 14 ++ .../run/multi-region-services/update-traffic | 171 ++++++++++++++++ gcloud/alpha/run/services/update | 20 ++ gcloud/alpha/run/worker-pools/deploy | 6 + gcloud/alpha/run/worker-pools/update | 6 + gcloud/alpha/sql/instances/create | 10 +- gcloud/alpha/sql/instances/patch | 10 +- gcloud/beta/bigtable/operations/list | 12 ++ gcloud/beta/compute/backend-services/create | 2 +- gcloud/beta/compute/backend-services/update | 19 +- .../compute/composite-health-checks/create | 94 +++++++++ .../compute/composite-health-checks/delete | 74 +++++++ .../compute/composite-health-checks/describe | 69 +++++++ .../beta/compute/composite-health-checks/help | 39 ++++ .../list | 57 ++---- .../compute/composite-health-checks/update | 96 +++++++++ .../health-aggregation-policies/create | 114 +++++++++++ .../health-aggregation-policies/delete | 75 +++++++ .../health-aggregation-policies/describe | 70 +++++++ .../compute/health-aggregation-policies/help | 40 ++++ .../compute/health-aggregation-policies/list | 78 ++++++++ .../health-aggregation-policies/update | 109 +++++++++++ gcloud/beta/compute/help | 6 + gcloud/beta/compute/instances/help | 4 - gcloud/beta/compute/instances/move | 96 --------- .../interconnects/cross-site-networks/create | 9 +- .../interconnects/cross-site-networks/delete | 21 +- .../cross-site-networks/describe | 19 +- .../interconnects/cross-site-networks/help | 6 +- .../interconnects/cross-site-networks/list | 6 +- .../interconnects/cross-site-networks/update | 17 +- .../interconnects/wire-groups/add-endpoint | 13 +- .../wire-groups/add-interconnect | 18 +- .../compute/interconnects/wire-groups/create | 12 +- .../compute/interconnects/wire-groups/delete | 18 +- .../interconnects/wire-groups/describe | 18 +- .../compute/interconnects/wire-groups/help | 6 +- .../compute/interconnects/wire-groups/list | 6 +- .../interconnects/wire-groups/remove-endpoint | 14 +- .../wire-groups/remove-interconnect | 15 +- .../compute/interconnects/wire-groups/update | 37 +++- .../org-security-policies/associations/create | 6 +- .../org-security-policies/associations/delete | 6 +- .../org-security-policies/associations/help | 6 +- .../org-security-policies/associations/list | 6 +- .../compute/org-security-policies/copy-rules | 6 +- .../beta/compute/org-security-policies/create | 6 +- .../beta/compute/org-security-policies/delete | 6 +- .../compute/org-security-policies/describe | 6 +- .../beta/compute/org-security-policies/help | 6 +- .../beta/compute/org-security-policies/list | 6 +- .../compute/org-security-policies/list-rules | 6 +- .../beta/compute/org-security-policies/move | 6 +- .../rules/add-preconfig-waf-exclusion | 7 +- .../org-security-policies/rules/create | 6 +- .../org-security-policies/rules/delete | 6 +- .../org-security-policies/rules/describe | 6 +- .../compute/org-security-policies/rules/help | 6 +- .../rules/remove-preconfig-waf-exclusion | 7 +- .../org-security-policies/rules/update | 6 +- .../beta/compute/org-security-policies/update | 6 +- gcloud/beta/compute/preview-features/describe | 6 +- gcloud/beta/compute/preview-features/help | 6 +- gcloud/beta/compute/preview-features/list | 6 +- gcloud/beta/compute/preview-features/update | 6 +- .../beta/compute/reservations/sub-blocks/help | 3 + .../sub-blocks/report-subblock-as-faulty | 99 ++++++++++ gcloud/beta/compute/tpus/create | 142 -------------- gcloud/beta/compute/tpus/delete | 77 -------- gcloud/beta/compute/tpus/describe | 72 ------- .../beta/compute/tpus/execution-groups/create | 163 --------------- .../beta/compute/tpus/execution-groups/delete | 73 ------- .../compute/tpus/execution-groups/describe | 64 ------ .../beta/compute/tpus/execution-groups/help | 50 ----- .../beta/compute/tpus/execution-groups/resume | 89 --------- .../compute/tpus/execution-groups/suspend | 62 ------ gcloud/beta/compute/tpus/help | 28 --- gcloud/beta/compute/tpus/reimage | 84 -------- gcloud/beta/compute/tpus/start | 76 ------- gcloud/beta/compute/tpus/stop | 76 ------- gcloud/beta/container/clusters/create | 11 +- gcloud/beta/container/clusters/create-auto | 12 +- gcloud/beta/container/clusters/update | 9 + gcloud/beta/container/node-pools/create | 18 ++ gcloud/beta/container/node-pools/update | 24 ++- gcloud/beta/firestore/databases/help | 4 + gcloud/beta/firestore/databases/ping | 38 ++++ .../providers/scim-tenants/delete | 6 +- gcloud/beta/memorystore/instances/update | 15 +- gcloud/beta/redis/clusters/update | 6 +- .../beta/resource-manager/tags/values/create | 12 +- gcloud/beta/sql/instances/create | 10 +- gcloud/beta/sql/instances/patch | 10 +- gcloud/bigtable/operations/list | 18 +- gcloud/compute/backend-services/create | 2 +- gcloud/compute/backend-services/update | 19 +- gcloud/compute/help | 6 + gcloud/compute/instances/help | 4 - gcloud/compute/instances/move | 95 --------- .../interconnects/cross-site-networks/create | 43 ++++ .../interconnects/cross-site-networks/delete | 41 ++++ .../cross-site-networks/describe | 39 ++++ .../interconnects/cross-site-networks/help | 41 ++++ .../interconnects/cross-site-networks/list | 69 +++++++ .../interconnects/cross-site-networks/update | 43 ++++ gcloud/compute/interconnects/help | 6 + .../interconnects/wire-groups/add-endpoint | 47 +++++ .../wire-groups/add-interconnect | 60 ++++++ .../compute/interconnects/wire-groups/create | 87 ++++++++ .../compute/interconnects/wire-groups/delete | 43 ++++ .../interconnects/wire-groups/describe | 43 ++++ gcloud/compute/interconnects/wire-groups/help | 51 +++++ .../interconnects/wire-groups}/list | 52 ++--- .../interconnects/wire-groups/remove-endpoint | 48 +++++ .../wire-groups/remove-interconnect | 52 +++++ .../compute/interconnects/wire-groups/update | 105 ++++++++++ .../compute/network-firewall-policies/create | 8 +- .../org-security-policies/associations/create | 80 ++++++++ .../org-security-policies/associations/delete | 48 +++++ .../org-security-policies/associations/help | 37 ++++ .../associations}/list | 51 ++--- .../compute/org-security-policies/copy-rules | 50 +++++ gcloud/compute/org-security-policies/create | 83 ++++++++ gcloud/compute/org-security-policies/delete | 42 ++++ gcloud/compute/org-security-policies/describe | 42 ++++ gcloud/compute/org-security-policies/help | 61 ++++++ gcloud/compute/org-security-policies/list | 93 +++++++++ .../compute/org-security-policies/list-rules | 107 ++++++++++ gcloud/compute/org-security-policies/move | 46 +++++ .../rules/add-preconfig-waf-exclusion | 148 ++++++++++++++ .../org-security-policies/rules/create | 122 ++++++++++++ .../org-security-policies/rules/delete | 49 +++++ .../org-security-policies/rules/describe | 49 +++++ .../compute/org-security-policies/rules/help | 45 +++++ .../rules/remove-preconfig-waf-exclusion | 166 ++++++++++++++++ .../org-security-policies/rules/update | 128 ++++++++++++ gcloud/compute/org-security-policies/update | 72 +++++++ gcloud/compute/preview-features/describe | 55 ++++++ gcloud/compute/preview-features/help | 34 ++++ gcloud/compute/preview-features/list | 67 +++++++ gcloud/compute/preview-features/update | 74 +++++++ gcloud/compute/reservations/sub-blocks/help | 3 + .../sub-blocks/report-subblock-as-faulty | 98 ++++++++++ gcloud/compute/tpus/create | 123 ------------ gcloud/compute/tpus/delete | 76 ------- gcloud/compute/tpus/describe | 70 ------- gcloud/compute/tpus/execution-groups/create | 162 --------------- gcloud/compute/tpus/execution-groups/delete | 71 ------- gcloud/compute/tpus/execution-groups/describe | 63 ------ gcloud/compute/tpus/execution-groups/help | 43 ---- gcloud/compute/tpus/help | 28 --- gcloud/compute/tpus/reimage | 83 -------- gcloud/compute/tpus/start | 75 ------- gcloud/compute/tpus/stop | 75 ------- gcloud/container/ai/profiles/benchmarks/list | 9 +- gcloud/container/clusters/create | 11 +- gcloud/container/clusters/create-auto | 12 +- gcloud/container/clusters/update | 9 + gcloud/container/node-pools/create | 18 ++ gcloud/container/node-pools/update | 24 ++- gcloud/firestore/databases/help | 4 + gcloud/firestore/databases/ping | 36 ++++ .../providers/scim-tenants/delete | 6 +- gcloud/memorystore/instances/update | 15 +- .../autonomous-databases/create | 54 +++-- .../oracle-database/autonomous-databases/help | 2 +- .../autonomous-databases/update | 83 ++++++-- .../db-servers/list | 3 +- .../cloud-vm-clusters/db-nodes/list | 38 ++-- gcloud/redis/clusters/update | 6 +- gcloud/resource-manager/tags/values/create | 14 +- gcloud/run/jobs/create | 18 +- gcloud/run/jobs/deploy | 16 +- gcloud/run/jobs/update | 22 ++- gcloud/sql/instances/create | 10 +- gcloud/sql/instances/patch | 10 +- 299 files changed, 7497 insertions(+), 3961 deletions(-) create mode 100644 gcloud/alpha/biglake/iceberg/catalogs/create create mode 100644 gcloud/alpha/biglake/iceberg/catalogs/get-iam-policy create mode 100644 gcloud/alpha/biglake/iceberg/catalogs/set-iam-policy create mode 100644 gcloud/alpha/biglake/iceberg/namespaces/get-iam-policy create mode 100644 gcloud/alpha/biglake/iceberg/namespaces/help create mode 100644 gcloud/alpha/biglake/iceberg/namespaces/set-iam-policy create mode 100644 gcloud/alpha/biglake/iceberg/tables/get-iam-policy create mode 100644 gcloud/alpha/biglake/iceberg/tables/help create mode 100644 gcloud/alpha/biglake/iceberg/tables/set-iam-policy create mode 100644 gcloud/alpha/compute/composite-health-checks/create create mode 100644 gcloud/alpha/compute/composite-health-checks/delete create mode 100644 gcloud/alpha/compute/composite-health-checks/describe create mode 100644 gcloud/alpha/compute/composite-health-checks/help rename gcloud/{compute/tpus/execution-groups => alpha/compute/composite-health-checks}/list (60%) create mode 100644 gcloud/alpha/compute/composite-health-checks/update create mode 100644 gcloud/alpha/compute/health-aggregation-policies/create create mode 100644 gcloud/alpha/compute/health-aggregation-policies/delete create mode 100644 gcloud/alpha/compute/health-aggregation-policies/describe create mode 100644 gcloud/alpha/compute/health-aggregation-policies/help rename gcloud/alpha/compute/{tpus => health-aggregation-policies}/list (55%) create mode 100644 gcloud/alpha/compute/health-aggregation-policies/update delete mode 100644 gcloud/alpha/compute/instances/move create mode 100644 gcloud/alpha/compute/network-policies/associations/create create mode 100644 gcloud/alpha/compute/network-policies/associations/delete create mode 100644 gcloud/alpha/compute/network-policies/associations/describe create mode 100644 gcloud/alpha/compute/network-policies/associations/help create mode 100644 gcloud/alpha/compute/network-policies/create create mode 100644 gcloud/alpha/compute/network-policies/delete create mode 100644 gcloud/alpha/compute/network-policies/describe create mode 100644 gcloud/alpha/compute/network-policies/help rename gcloud/alpha/compute/{tpus/execution-groups => network-policies}/list (62%) create mode 100644 gcloud/alpha/compute/network-policies/traffic-classification-rules/create create mode 100644 gcloud/alpha/compute/network-policies/traffic-classification-rules/delete create mode 100644 gcloud/alpha/compute/network-policies/traffic-classification-rules/describe create mode 100644 gcloud/alpha/compute/network-policies/traffic-classification-rules/help create mode 100644 gcloud/alpha/compute/network-policies/traffic-classification-rules/update create mode 100644 gcloud/alpha/compute/network-policies/update delete mode 100644 gcloud/alpha/compute/tpus/create delete mode 100644 gcloud/alpha/compute/tpus/delete delete mode 100644 gcloud/alpha/compute/tpus/describe delete mode 100644 gcloud/alpha/compute/tpus/execution-groups/create delete mode 100644 gcloud/alpha/compute/tpus/execution-groups/delete delete mode 100644 gcloud/alpha/compute/tpus/execution-groups/describe delete mode 100644 gcloud/alpha/compute/tpus/execution-groups/help delete mode 100644 gcloud/alpha/compute/tpus/execution-groups/resume delete mode 100644 gcloud/alpha/compute/tpus/execution-groups/suspend delete mode 100644 gcloud/alpha/compute/tpus/reimage delete mode 100644 gcloud/alpha/compute/tpus/start delete mode 100644 gcloud/alpha/compute/tpus/stop create mode 100644 gcloud/alpha/firestore/databases/ping create mode 100644 gcloud/alpha/run/multi-region-services/update-traffic create mode 100644 gcloud/beta/compute/composite-health-checks/create create mode 100644 gcloud/beta/compute/composite-health-checks/delete create mode 100644 gcloud/beta/compute/composite-health-checks/describe create mode 100644 gcloud/beta/compute/composite-health-checks/help rename gcloud/beta/compute/{tpus/execution-groups => composite-health-checks}/list (60%) create mode 100644 gcloud/beta/compute/composite-health-checks/update create mode 100644 gcloud/beta/compute/health-aggregation-policies/create create mode 100644 gcloud/beta/compute/health-aggregation-policies/delete create mode 100644 gcloud/beta/compute/health-aggregation-policies/describe create mode 100644 gcloud/beta/compute/health-aggregation-policies/help create mode 100644 gcloud/beta/compute/health-aggregation-policies/list create mode 100644 gcloud/beta/compute/health-aggregation-policies/update delete mode 100644 gcloud/beta/compute/instances/move create mode 100644 gcloud/beta/compute/reservations/sub-blocks/report-subblock-as-faulty delete mode 100644 gcloud/beta/compute/tpus/create delete mode 100644 gcloud/beta/compute/tpus/delete delete mode 100644 gcloud/beta/compute/tpus/describe delete mode 100644 gcloud/beta/compute/tpus/execution-groups/create delete mode 100644 gcloud/beta/compute/tpus/execution-groups/delete delete mode 100644 gcloud/beta/compute/tpus/execution-groups/describe delete mode 100644 gcloud/beta/compute/tpus/execution-groups/help delete mode 100644 gcloud/beta/compute/tpus/execution-groups/resume delete mode 100644 gcloud/beta/compute/tpus/execution-groups/suspend delete mode 100644 gcloud/beta/compute/tpus/reimage delete mode 100644 gcloud/beta/compute/tpus/start delete mode 100644 gcloud/beta/compute/tpus/stop create mode 100644 gcloud/beta/firestore/databases/ping delete mode 100644 gcloud/compute/instances/move create mode 100644 gcloud/compute/interconnects/cross-site-networks/create create mode 100644 gcloud/compute/interconnects/cross-site-networks/delete create mode 100644 gcloud/compute/interconnects/cross-site-networks/describe create mode 100644 gcloud/compute/interconnects/cross-site-networks/help create mode 100644 gcloud/compute/interconnects/cross-site-networks/list create mode 100644 gcloud/compute/interconnects/cross-site-networks/update create mode 100644 gcloud/compute/interconnects/wire-groups/add-endpoint create mode 100644 gcloud/compute/interconnects/wire-groups/add-interconnect create mode 100644 gcloud/compute/interconnects/wire-groups/create create mode 100644 gcloud/compute/interconnects/wire-groups/delete create mode 100644 gcloud/compute/interconnects/wire-groups/describe create mode 100644 gcloud/compute/interconnects/wire-groups/help rename gcloud/{beta/compute/tpus => compute/interconnects/wire-groups}/list (55%) create mode 100644 gcloud/compute/interconnects/wire-groups/remove-endpoint create mode 100644 gcloud/compute/interconnects/wire-groups/remove-interconnect create mode 100644 gcloud/compute/interconnects/wire-groups/update create mode 100644 gcloud/compute/org-security-policies/associations/create create mode 100644 gcloud/compute/org-security-policies/associations/delete create mode 100644 gcloud/compute/org-security-policies/associations/help rename gcloud/compute/{tpus => org-security-policies/associations}/list (57%) create mode 100644 gcloud/compute/org-security-policies/copy-rules create mode 100644 gcloud/compute/org-security-policies/create create mode 100644 gcloud/compute/org-security-policies/delete create mode 100644 gcloud/compute/org-security-policies/describe create mode 100644 gcloud/compute/org-security-policies/help create mode 100644 gcloud/compute/org-security-policies/list create mode 100644 gcloud/compute/org-security-policies/list-rules create mode 100644 gcloud/compute/org-security-policies/move create mode 100644 gcloud/compute/org-security-policies/rules/add-preconfig-waf-exclusion create mode 100644 gcloud/compute/org-security-policies/rules/create create mode 100644 gcloud/compute/org-security-policies/rules/delete create mode 100644 gcloud/compute/org-security-policies/rules/describe create mode 100644 gcloud/compute/org-security-policies/rules/help create mode 100644 gcloud/compute/org-security-policies/rules/remove-preconfig-waf-exclusion create mode 100644 gcloud/compute/org-security-policies/rules/update create mode 100644 gcloud/compute/org-security-policies/update create mode 100644 gcloud/compute/preview-features/describe create mode 100644 gcloud/compute/preview-features/help create mode 100644 gcloud/compute/preview-features/list create mode 100644 gcloud/compute/preview-features/update create mode 100644 gcloud/compute/reservations/sub-blocks/report-subblock-as-faulty delete mode 100644 gcloud/compute/tpus/create delete mode 100644 gcloud/compute/tpus/delete delete mode 100644 gcloud/compute/tpus/describe delete mode 100644 gcloud/compute/tpus/execution-groups/create delete mode 100644 gcloud/compute/tpus/execution-groups/delete delete mode 100644 gcloud/compute/tpus/execution-groups/describe delete mode 100644 gcloud/compute/tpus/execution-groups/help delete mode 100644 gcloud/compute/tpus/reimage delete mode 100644 gcloud/compute/tpus/start delete mode 100644 gcloud/compute/tpus/stop create mode 100644 gcloud/firestore/databases/ping diff --git a/gcloud/_version b/gcloud/_version index 5cd3bbc79..d3ba667d4 100644 --- a/gcloud/_version +++ b/gcloud/_version @@ -1,8 +1,8 @@ -Google Cloud SDK 542.0.0 -alpha 2025.10.03 -beta 2025.10.03 +Google Cloud SDK 543.0.0 +alpha 2025.10.10 +beta 2025.10.10 bq 2.1.24 bundled-python3-unix 3.12.9 -core 2025.10.03 +core 2025.10.10 gcloud-crc32c 1.0.0 gsutil 5.35 diff --git a/gcloud/alpha/biglake/iceberg/catalogs/create b/gcloud/alpha/biglake/iceberg/catalogs/create new file mode 100644 index 000000000..5e0abc61f --- /dev/null +++ b/gcloud/alpha/biglake/iceberg/catalogs/create @@ -0,0 +1,76 @@ +NAME + gcloud alpha biglake iceberg catalogs create - create a BigLake Iceberg + REST catalog + +SYNOPSIS + gcloud alpha biglake iceberg catalogs create CATALOG + --catalog-type=CATALOG_TYPE + [--credential-mode=CREDENTIAL_MODE; default="end-user"] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Create a BigLake Iceberg REST catalog. + +EXAMPLES + To add a catalog using a GCS bucket my-catalog-bucket, run: + + $ gcloud alpha biglake iceberg catalogs create my-catalog-bucket \ + --catalog-type=gcs-bucket + + To create a catalog using a GCS bucket my-catalog-bucket with vended + credentials, run: + + $ gcloud alpha biglake iceberg catalogs create my-catalog-bucket \ + --catalog-type=gcs-bucket --credential-mode=vended-credentials + +POSITIONAL ARGUMENTS + Catalog resource - The Iceberg Catalog to create. 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 catalog 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. + + CATALOG + ID of the catalog or fully qualified identifier for the catalog. + + To set the catalog attribute: + ▸ provide the argument catalog on the command line. + +REQUIRED FLAGS + --catalog-type=CATALOG_TYPE + Catalog type to create the catalog with. CATALOG_TYPE must be (only one + value is supported): + + gcs-bucket + A catalog backed by a GCS bucket. + +OPTIONAL FLAGS + --credential-mode=CREDENTIAL_MODE; default="end-user" + Credential mode to create the catalog with. CREDENTIAL_MODE must be one + of: + + end-user + Use end user credentials to access the catalog. + vended-credentials + Use vended credentials to access the catalog. + +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/biglake/iceberg/catalogs/get-iam-policy b/gcloud/alpha/biglake/iceberg/catalogs/get-iam-policy new file mode 100644 index 000000000..b82f675c2 --- /dev/null +++ b/gcloud/alpha/biglake/iceberg/catalogs/get-iam-policy @@ -0,0 +1,76 @@ +NAME + gcloud alpha biglake iceberg catalogs get-iam-policy - get the IAM policy + for a BigLake Iceberg REST catalog + +SYNOPSIS + gcloud alpha biglake iceberg catalogs get-iam-policy CATALOG + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Gets the IAM policy for a BigLake Iceberg REST catalog. + +EXAMPLES + To get the IAM policy for the catalog my-catalog run: + + $ gcloud alpha biglake iceberg catalogs get-iam-policy my-catalog + +POSITIONAL ARGUMENTS + Catalog resource - The Iceberg Catalog to get the IAM policy for. 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 catalog 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. + + CATALOG + ID of the catalog or fully qualified identifier for the catalog. + + To set the catalog attribute: + ▸ provide the argument catalog on the command line. + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +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/biglake/iceberg/catalogs/help b/gcloud/alpha/biglake/iceberg/catalogs/help index 7a548e410..56ae1ee28 100644 --- a/gcloud/alpha/biglake/iceberg/catalogs/help +++ b/gcloud/alpha/biglake/iceberg/catalogs/help @@ -16,15 +16,24 @@ GCLOUD WIDE FLAGS COMMANDS COMMAND is one of the following: + create + (ALPHA) Create a BigLake Iceberg REST catalog. + delete (ALPHA) Delete a BigLake Iceberg REST catalog. describe (ALPHA) Describe a BigLake Iceberg REST catalog. + get-iam-policy + (ALPHA) Get the IAM policy for a BigLake Iceberg REST catalog. + list (ALPHA) List BigLake Iceberg REST catalogs. + set-iam-policy + (ALPHA) Set the IAM policy for a BigLake Iceberg REST catalog. + update (ALPHA) Update a BigLake Iceberg REST catalog. diff --git a/gcloud/alpha/biglake/iceberg/catalogs/set-iam-policy b/gcloud/alpha/biglake/iceberg/catalogs/set-iam-policy new file mode 100644 index 000000000..5c51d569c --- /dev/null +++ b/gcloud/alpha/biglake/iceberg/catalogs/set-iam-policy @@ -0,0 +1,58 @@ +NAME + gcloud alpha biglake iceberg catalogs set-iam-policy - set the IAM policy + for a BigLake Iceberg REST catalog + +SYNOPSIS + gcloud alpha biglake iceberg catalogs set-iam-policy CATALOG POLICY_FILE + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Sets the IAM policy for a BigLake Iceberg REST catalog. + +EXAMPLES + To set the IAM policy for the catalog my-catalog with the policy in + policy.json run: + + $ gcloud alpha biglake iceberg catalogs set-iam-policy my-catalog \ + policy.json + +POSITIONAL ARGUMENTS + Catalog resource - The Iceberg Catalog to set the IAM policy for. 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 catalog 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. + + CATALOG + ID of the catalog or fully qualified identifier for the catalog. + + To set the catalog attribute: + ▸ provide the argument catalog on the command line. + + POLICY_FILE + Path to a local JSON or YAML formatted file containing a valid policy. + + The output of the get-iam-policy command is a valid file, as is any + JSON or YAML file conforming to the structure of a Policy + (https://cloud.google.com/iam/reference/rest/v1/Policy). + +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/biglake/iceberg/catalogs/update b/gcloud/alpha/biglake/iceberg/catalogs/update index 88470e8b1..6f960630e 100644 --- a/gcloud/alpha/biglake/iceberg/catalogs/update +++ b/gcloud/alpha/biglake/iceberg/catalogs/update @@ -4,7 +4,7 @@ NAME SYNOPSIS gcloud alpha biglake iceberg catalogs update CATALOG - [--credential-mode=TYPE; default="CREDENTIAL_MODE_END_USER"] + [--credential-mode=CREDENTIAL_MODE; default="end-user"] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -30,9 +30,14 @@ POSITIONAL ARGUMENTS ▸ provide the argument catalog on the command line. FLAGS - --credential-mode=TYPE; default="CREDENTIAL_MODE_END_USER" - Credential mode to update the catalog with. TYPE must be one of: - CREDENTIAL_MODE_END_USER, CREDENTIAL_MODE_VENDED_CREDENTIALS. + --credential-mode=CREDENTIAL_MODE; default="end-user" + Credential mode to create the catalog with. CREDENTIAL_MODE must be one + of: + + end-user + Use end user credentials to access the catalog. + vended-credentials + Use vended credentials to access the catalog. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/alpha/biglake/iceberg/help b/gcloud/alpha/biglake/iceberg/help index c21cef895..ca2290ba1 100644 --- a/gcloud/alpha/biglake/iceberg/help +++ b/gcloud/alpha/biglake/iceberg/help @@ -18,6 +18,12 @@ GROUPS catalogs (ALPHA) Manage BigLake Iceberg REST catalogs. + namespaces + (ALPHA) Manage BigLake Iceberg REST catalog namespaces. + + tables + (ALPHA) Manage BigLake Iceberg REST catalog tables. + 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/biglake/iceberg/namespaces/get-iam-policy b/gcloud/alpha/biglake/iceberg/namespaces/get-iam-policy new file mode 100644 index 000000000..b8291003f --- /dev/null +++ b/gcloud/alpha/biglake/iceberg/namespaces/get-iam-policy @@ -0,0 +1,90 @@ +NAME + gcloud alpha biglake iceberg namespaces get-iam-policy - get the IAM policy + for a BigLake Iceberg REST catalog namespace + +SYNOPSIS + gcloud alpha biglake iceberg namespaces get-iam-policy + (NAMESPACE : --catalog=CATALOG) [--filter=EXPRESSION] [--limit=LIMIT] + [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Gets the IAM policy for a BigLake Iceberg REST catalog namespace. + +EXAMPLES + To get the IAM policy for the catalog my-catalog and namespace my-namespace + run: + + $ gcloud alpha biglake iceberg namespaces get-iam-policy \ + my-namespace --catalog=my-catalog + +POSITIONAL ARGUMENTS + Namespace resource - The Iceberg Namespace to get the IAM policy for. 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 namespace 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. + + NAMESPACE + ID of the namespace or fully qualified identifier for the namespace. + + To set the namespace attribute: + ▸ provide the argument namespace on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --catalog=CATALOG + The Iceberg Catalog for the resource. + + To set the catalog attribute: + ▸ provide the argument namespace on the command line with a fully + specified name; + ▸ provide the argument --catalog on the command line. + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +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/biglake/iceberg/namespaces/help b/gcloud/alpha/biglake/iceberg/namespaces/help new file mode 100644 index 000000000..63240ffa4 --- /dev/null +++ b/gcloud/alpha/biglake/iceberg/namespaces/help @@ -0,0 +1,32 @@ +NAME + gcloud alpha biglake iceberg namespaces - manage BigLake Iceberg REST + catalog namespaces + +SYNOPSIS + gcloud alpha biglake iceberg namespaces COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Manage BigLake Iceberg REST catalog namespaces. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + get-iam-policy + (ALPHA) Get the IAM policy for a BigLake Iceberg REST catalog + namespace. + + set-iam-policy + (ALPHA) Set the IAM policy for a BigLake Iceberg REST catalog + namespace. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/biglake/iceberg/namespaces/set-iam-policy b/gcloud/alpha/biglake/iceberg/namespaces/set-iam-policy new file mode 100644 index 000000000..8b3c29775 --- /dev/null +++ b/gcloud/alpha/biglake/iceberg/namespaces/set-iam-policy @@ -0,0 +1,70 @@ +NAME + gcloud alpha biglake iceberg namespaces set-iam-policy - set the IAM policy + for a BigLake Iceberg REST catalog namespace + +SYNOPSIS + gcloud alpha biglake iceberg namespaces set-iam-policy + (NAMESPACE : --catalog=CATALOG) POLICY_FILE [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Sets the IAM policy for a BigLake Iceberg REST catalog namespace. + +EXAMPLES + To set the IAM policy for the catalog my-catalog and namespace my-namespace + with the policy in policy.json run: + + $ gcloud alpha biglake iceberg namespaces set-iam-policy \ + my-namespace policy.json --catalog=my-catalog + +POSITIONAL ARGUMENTS + Namespace resource - The Iceberg Namespace to set the IAM policy for. 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 namespace 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. + + NAMESPACE + ID of the namespace or fully qualified identifier for the namespace. + + To set the namespace attribute: + ▸ provide the argument namespace on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --catalog=CATALOG + The Iceberg Catalog for the resource. + + To set the catalog attribute: + ▸ provide the argument namespace on the command line with a fully + specified name; + ▸ provide the argument --catalog on the command line. + + POLICY_FILE + Path to a local JSON or YAML formatted file containing a valid policy. + + The output of the get-iam-policy command is a valid file, as is any + JSON or YAML file conforming to the structure of a Policy + (https://cloud.google.com/iam/reference/rest/v1/Policy). + +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/biglake/iceberg/tables/get-iam-policy b/gcloud/alpha/biglake/iceberg/tables/get-iam-policy new file mode 100644 index 000000000..1020137c9 --- /dev/null +++ b/gcloud/alpha/biglake/iceberg/tables/get-iam-policy @@ -0,0 +1,99 @@ +NAME + gcloud alpha biglake iceberg tables get-iam-policy - get the IAM policy for + a BigLake Iceberg REST catalog table + +SYNOPSIS + gcloud alpha biglake iceberg tables get-iam-policy + (TABLE : --catalog=CATALOG --namespace=NAMESPACE) [--filter=EXPRESSION] + [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Gets the IAM policy for a BigLake Iceberg REST catalog table. + +EXAMPLES + To get the IAM policy for the catalog my-catalog, namespace my-namespace, + and table my-table run: + + $ gcloud alpha biglake iceberg tables get-iam-policy my-table \ + --catalog=my-catalog --namespace=my-namespace + +POSITIONAL ARGUMENTS + Table resource - The Iceberg Table to get the IAM policy for. 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 table 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. + + TABLE + ID of the table or fully qualified identifier for the table. + + To set the table attribute: + ▸ provide the argument table on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --catalog=CATALOG + The Iceberg Catalog for the resource. + + To set the catalog attribute: + ▸ provide the argument table on the command line with a fully + specified name; + ▸ provide the argument --catalog on the command line. + + --namespace=NAMESPACE + The Iceberg Namespace for the resource. + + To set the namespace attribute: + ▸ provide the argument table on the command line with a fully + specified name; + ▸ provide the argument --namespace on the command line. + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +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/biglake/iceberg/tables/help b/gcloud/alpha/biglake/iceberg/tables/help new file mode 100644 index 000000000..8f040d1d6 --- /dev/null +++ b/gcloud/alpha/biglake/iceberg/tables/help @@ -0,0 +1,30 @@ +NAME + gcloud alpha biglake iceberg tables - manage BigLake Iceberg REST catalog + tables + +SYNOPSIS + gcloud alpha biglake iceberg tables COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Manage BigLake Iceberg REST catalog tables. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + get-iam-policy + (ALPHA) Get the IAM policy for a BigLake Iceberg REST catalog table. + + set-iam-policy + (ALPHA) Set the IAM policy for a BigLake Iceberg REST catalog table. + +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/biglake/iceberg/tables/set-iam-policy b/gcloud/alpha/biglake/iceberg/tables/set-iam-policy new file mode 100644 index 000000000..f53eb98fe --- /dev/null +++ b/gcloud/alpha/biglake/iceberg/tables/set-iam-policy @@ -0,0 +1,79 @@ +NAME + gcloud alpha biglake iceberg tables set-iam-policy - set the IAM policy for + a BigLake Iceberg REST catalog table + +SYNOPSIS + gcloud alpha biglake iceberg tables set-iam-policy + (TABLE : --catalog=CATALOG --namespace=NAMESPACE) POLICY_FILE + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Sets the IAM policy for a BigLake Iceberg REST catalog table. + +EXAMPLES + To set the IAM policy for the catalog my-catalog, namespace my-namespace, + and table my-table with the policy in policy.json run: + + $ gcloud alpha biglake iceberg tables set-iam-policy my-table \ + policy.json --catalog=my-catalog --namespace=my-namespace + +POSITIONAL ARGUMENTS + Table resource - The Iceberg Table to set the IAM policy for. 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 table 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. + + TABLE + ID of the table or fully qualified identifier for the table. + + To set the table attribute: + ▸ provide the argument table on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --catalog=CATALOG + The Iceberg Catalog for the resource. + + To set the catalog attribute: + ▸ provide the argument table on the command line with a fully + specified name; + ▸ provide the argument --catalog on the command line. + + --namespace=NAMESPACE + The Iceberg Namespace for the resource. + + To set the namespace attribute: + ▸ provide the argument table on the command line with a fully + specified name; + ▸ provide the argument --namespace on the command line. + + POLICY_FILE + Path to a local JSON or YAML formatted file containing a valid policy. + + The output of the get-iam-policy command is a valid file, as is any + JSON or YAML file conforming to the structure of a Policy + (https://cloud.google.com/iam/reference/rest/v1/Policy). + +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/bigtable/operations/list b/gcloud/alpha/bigtable/operations/list index 40f4c77af..94ee9f5c1 100644 --- a/gcloud/alpha/bigtable/operations/list +++ b/gcloud/alpha/bigtable/operations/list @@ -3,6 +3,7 @@ NAME SYNOPSIS gcloud alpha bigtable operations list [--instance=INSTANCE] + [--return-partial-success=RETURN_PARTIAL_SUCCESS; default=True] [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] @@ -18,6 +19,11 @@ EXAMPLES $ gcloud alpha bigtable operations list --instance=INSTANCE_NAME + To fail the command if any location is unreachable, run: + + $ gcloud alpha bigtable operations list \ + --return-partial-success=false + FLAGS Instance resource - The instance to list operations for. This represents a Cloud resource. (NOTE) Some attributes are not given arguments in this @@ -35,6 +41,13 @@ FLAGS To set the instance attribute: ▸ provide the argument --instance on the command line. + --return-partial-success=RETURN_PARTIAL_SUCCESS; default=True + If true, operations that are reachable are returned as normal, and + those that are unreachable are returned in the unreachable field of the + response. If false, the command will fail if any location is + unreachable. Enabled by default, use --no-return-partial-success to + disable. + LIST COMMAND FLAGS --filter=EXPRESSION Apply a Boolean filter EXPRESSION to each resource item to be listed. diff --git a/gcloud/alpha/compute/backend-services/create b/gcloud/alpha/compute/backend-services/create index 3d78e738c..4e65a32a4 100644 --- a/gcloud/alpha/compute/backend-services/create +++ b/gcloud/alpha/compute/backend-services/create @@ -413,7 +413,7 @@ FLAGS The load balancing algorithm used within the scope of the locality. LOCALITY_LB_POLICY must be one of: INVALID_LB_POLICY, ROUND_ROBIN, LEAST_REQUEST, RING_HASH, RANDOM, ORIGINAL_DESTINATION, MAGLEV, - WEIGHTED_MAGLEV, WEIGHTED_ROUND_ROBIN. + WEIGHTED_MAGLEV, WEIGHTED_ROUND_ROBIN, WEIGHTED_GCP_RENDEZVOUS. --logging-optional=LOGGING_OPTIONAL This field can only be specified if logging is enabled for the backend diff --git a/gcloud/alpha/compute/backend-services/update b/gcloud/alpha/compute/backend-services/update index a5422f857..00e9f94a2 100644 --- a/gcloud/alpha/compute/backend-services/update +++ b/gcloud/alpha/compute/backend-services/update @@ -27,7 +27,6 @@ SYNOPSIS [--ip-address-selection-policy=IP_ADDRESS_SELECTION_POLICY] [--ip-port-dynamic-forwarding] [--load-balancing-scheme=LOAD_BALANCING_SCHEME] - [--locality-lb-policy=LOCALITY_LB_POLICY] [--logging-optional=LOGGING_OPTIONAL] [--logging-optional-fields=[LOGGING_OPTIONAL_FIELDS,...]] [--logging-sample-rate=LOGGING_SAMPLE_RATE] [--port-name=PORT_NAME] @@ -56,6 +55,7 @@ SYNOPSIS [--default-ttl=DEFAULT_TTL | --no-default-ttl] [--global | --region=REGION] [--global-health-checks | --health-checks-region=HEALTH_CHECKS_REGION] + [--locality-lb-policy=LOCALITY_LB_POLICY | --no-locality-lb-policy] [--max-ttl=MAX_TTL | --no-max-ttl] [--[no-]negative-caching | --no-negative-caching-policies | --negative-caching-policy=[[CODE=TTL],...]] @@ -330,12 +330,6 @@ FLAGS LOAD_BALANCING_SCHEME must be one of: EXTERNAL, EXTERNAL_MANAGED. - --locality-lb-policy=LOCALITY_LB_POLICY - The load balancing algorithm used within the scope of the locality. - LOCALITY_LB_POLICY must be one of: INVALID_LB_POLICY, ROUND_ROBIN, - LEAST_REQUEST, RING_HASH, RANDOM, ORIGINAL_DESTINATION, MAGLEV, - WEIGHTED_MAGLEV, WEIGHTED_ROUND_ROBIN. - --logging-optional=LOGGING_OPTIONAL This field can only be specified if logging is enabled for the backend service. Configures whether all, none, or a subset of optional fields @@ -875,6 +869,17 @@ FLAGS Alternatively, the region can be stored in the environment variable CLOUDSDK_COMPUTE_REGION. + At most one of these can be specified: + + --locality-lb-policy=LOCALITY_LB_POLICY + The load balancing algorithm used within the scope of the locality. + LOCALITY_LB_POLICY must be one of: INVALID_LB_POLICY, ROUND_ROBIN, + LEAST_REQUEST, RING_HASH, RANDOM, ORIGINAL_DESTINATION, MAGLEV, + WEIGHTED_MAGLEV, WEIGHTED_ROUND_ROBIN, WEIGHTED_GCP_RENDEZVOUS. + + --no-locality-lb-policy + Removes the locality load balancing policy from the backend service. + At most one of these can be specified: --max-ttl=MAX_TTL diff --git a/gcloud/alpha/compute/composite-health-checks/create b/gcloud/alpha/compute/composite-health-checks/create new file mode 100644 index 000000000..541b42bc1 --- /dev/null +++ b/gcloud/alpha/compute/composite-health-checks/create @@ -0,0 +1,96 @@ +NAME + gcloud alpha compute composite-health-checks create - create a composite + health check + +SYNOPSIS + gcloud alpha compute composite-health-checks create + (COMPOSITE_HEALTH_CHECK : --region=REGION) + --health-destination=HEALTH_DESTINATION + --health-sources=[HEALTH_SOURCES,...] [--async] + [--description=DESCRIPTION] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Create a composite health check. + +EXAMPLES + The following command creates a new composite health check: + + $ gcloud alpha compute composite-health-checks create \ + --region= \ + --health-sources=my-hs --health-destination=my-fr + +POSITIONAL ARGUMENTS + Composite health check resource - The name of the composite health check + you want to create. 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 composite_health_check 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. + + COMPOSITE_HEALTH_CHECK + ID of the composite health check or fully qualified identifier for + the composite health check. + + To set the composite_health_check attribute: + ▸ provide the argument composite_health_check on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --region=REGION + The name of the Google Compute Engine region. + + To set the region attribute: + ▸ provide the argument composite_health_check on the command line + with a fully specified name; + ▸ provide the argument --region on the command line; + ▸ set the property compute/region. + +REQUIRED FLAGS + --health-destination=HEALTH_DESTINATION + URL to the destination resource. Must be set. Must be a ForwardingRule. + The ForwardingRule must have load balancing scheme INTERNAL or + INTERNAL_MANAGED and must be regional and in the same region as the + CompositeHealthCheck (cross-region deployment for INTERNAL_MANAGED is + not supported). Can be mutated. + + --health-sources=[HEALTH_SOURCES,...] + URLs to the HealthSource resources whose results are AND'ed. I.e. the + aggregated result is HEALTHY only if all sources are HEALTHY. Must have + at least 1. Must not have more than 10. Must be regional and in the + same region as the CompositeHealthCheck. Can be mutated. + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --description=DESCRIPTION + A textual description of this resource. + +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 compute/alpha API. The full documentation for this + API can be found at: https://cloud.google.com/compute/ + +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 composite-health-checks create + diff --git a/gcloud/alpha/compute/composite-health-checks/delete b/gcloud/alpha/compute/composite-health-checks/delete new file mode 100644 index 000000000..af20e6380 --- /dev/null +++ b/gcloud/alpha/compute/composite-health-checks/delete @@ -0,0 +1,76 @@ +NAME + gcloud alpha compute composite-health-checks delete - delete a composite + health check + +SYNOPSIS + gcloud alpha compute composite-health-checks delete + (COMPOSITE_HEALTH_CHECK : --region=REGION) [--async] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Delete a composite health check. + +EXAMPLES + To delete a single composite health check, run the following command: + + $ gcloud alpha compute composite-health-checks delete \ + --region= + +POSITIONAL ARGUMENTS + Composite health check resource - Name of the composite health check you + want to delete. The arguments in this group can be used to specify the + attributes of this resource. (NOTE) Some attributes are not given + arguments in this group but can be set in other ways. + + To set the project attribute: + ◆ provide the argument composite_health_check 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. + + COMPOSITE_HEALTH_CHECK + ID of the composite health check or fully qualified identifier for + the composite health check. + + To set the composite_health_check attribute: + ▸ provide the argument composite_health_check on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --region=REGION + The name of the Google Compute Engine region. + + To set the region attribute: + ▸ provide the argument composite_health_check on the command line + with a fully specified name; + ▸ provide the argument --region on the command line; + ▸ set the property compute/region. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the compute/alpha API. The full documentation for this + API can be found at: https://cloud.google.com/compute/ + +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 composite-health-checks delete + diff --git a/gcloud/alpha/compute/composite-health-checks/describe b/gcloud/alpha/compute/composite-health-checks/describe new file mode 100644 index 000000000..f0f821621 --- /dev/null +++ b/gcloud/alpha/compute/composite-health-checks/describe @@ -0,0 +1,71 @@ +NAME + gcloud alpha compute composite-health-checks describe - describe a + composite health check + +SYNOPSIS + gcloud alpha compute composite-health-checks describe + (COMPOSITE_HEALTH_CHECK : --region=REGION) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Describe a composite health check. + +EXAMPLES + To retrieve a single composite health check and print its properties, run + the following command: + + $ gcloud alpha compute composite-health-checks describe \ + --region= + +POSITIONAL ARGUMENTS + Composite health check resource - Name of the composite health check you + want to inspect. 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 composite_health_check 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. + + COMPOSITE_HEALTH_CHECK + ID of the composite health check or fully qualified identifier for + the composite health check. + + To set the composite_health_check attribute: + ▸ provide the argument composite_health_check on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --region=REGION + The name of the Google Compute Engine region. + + To set the region attribute: + ▸ provide the argument composite_health_check on the command line + with a fully specified name; + ▸ provide the argument --region on the command line; + ▸ set the property compute/region. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the compute/alpha API. The full documentation for this + API can be found at: https://cloud.google.com/compute/ + +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 composite-health-checks describe + diff --git a/gcloud/alpha/compute/composite-health-checks/help b/gcloud/alpha/compute/composite-health-checks/help new file mode 100644 index 000000000..182c448ba --- /dev/null +++ b/gcloud/alpha/compute/composite-health-checks/help @@ -0,0 +1,41 @@ +NAME + gcloud alpha compute composite-health-checks - manage composite health + checks + +SYNOPSIS + gcloud alpha compute composite-health-checks COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Manage composite health checks. + +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 composite health check. + + delete + (ALPHA) Delete a composite health check. + + describe + (ALPHA) Describe a composite health check. + + list + (ALPHA) List composite health checks. + + update + (ALPHA) Update a composite health check. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud beta compute composite-health-checks + diff --git a/gcloud/compute/tpus/execution-groups/list b/gcloud/alpha/compute/composite-health-checks/list similarity index 60% rename from gcloud/compute/tpus/execution-groups/list rename to gcloud/alpha/compute/composite-health-checks/list index 44b89d610..6f6090195 100644 --- a/gcloud/compute/tpus/execution-groups/list +++ b/gcloud/alpha/compute/composite-health-checks/list @@ -1,47 +1,34 @@ NAME - gcloud compute tpus execution-groups list - list TPU Node+VM groups created - by execution group + gcloud alpha compute composite-health-checks list - list composite health + checks SYNOPSIS - gcloud compute tpus execution-groups list [--zone=ZONE] + gcloud alpha compute composite-health-checks list [NAME ...] + [--regexp=REGEXP, -r REGEXP] [--regions=REGION,[REGION,...]] [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (DEPRECATED) List TPU Node+VM groups created by execution group. + (ALPHA) List composite health checks. - This command is deprecated and will be removed in a future release. We - recommend that you use the TPU-VM or Queued Resource API. See - https://cloud.google.com/tpu/docs/managing-tpus-tpu-vm for more - information. +POSITIONAL ARGUMENTS + [NAME ...] + (DEPRECATED) If provided, show details for the specified names and/or + URIs of resources. -EXAMPLES - To list all active execution groups, run: - - $ gcloud compute tpus execution-groups list --zone=test-zone \ - --project=test-project + Argument NAME is deprecated. Use --filter="name=( 'NAME' ... )" + instead. FLAGS - --zone=ZONE - Zone of the tpu to list. If not specified and the compute/zone property - isn't set, you might be prompted to select a zone (interactive mode - only). + --regexp=REGEXP, -r REGEXP + (DEPRECATED) Regular expression to filter the names of the results on. + Any names that do not match the entire regular expression will be + filtered out. - To avoid prompting when this flag is omitted, you can set the - compute/zone property: + Flag --regexp is deprecated. Use --filter="name~'REGEXP'" instead. - $ 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. + --regions=REGION,[REGION,...] + If provided, only resources from the given regions are queried. LIST COMMAND FLAGS --filter=EXPRESSION @@ -84,9 +71,10 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. NOTES - These variants are also available: + 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 alpha compute tpus execution-groups list - - $ gcloud beta compute tpus execution-groups list + $ gcloud beta compute composite-health-checks list diff --git a/gcloud/alpha/compute/composite-health-checks/update b/gcloud/alpha/compute/composite-health-checks/update new file mode 100644 index 000000000..0efd37dc8 --- /dev/null +++ b/gcloud/alpha/compute/composite-health-checks/update @@ -0,0 +1,98 @@ +NAME + gcloud alpha compute composite-health-checks update - update a composite + health check + +SYNOPSIS + gcloud alpha compute composite-health-checks update + (COMPOSITE_HEALTH_CHECK : --region=REGION) + (--description=DESCRIPTION --health-destination=HEALTH_DESTINATION + --health-sources=[HEALTH_SOURCES,...]) [--async] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Update a composite health check. + +EXAMPLES + The following command updates an existing composite health check: + + $ gcloud alpha compute composite-health-checks update \ + --region= \ + --health-destination=my-new-fr + +POSITIONAL ARGUMENTS + Composite health check resource - The name of the composite health check + you want to update. The arguments in this group can be used to specify the + attributes of this resource. (NOTE) Some attributes are not given + arguments in this group but can be set in other ways. + + To set the project attribute: + ◆ provide the argument composite_health_check 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. + + COMPOSITE_HEALTH_CHECK + ID of the composite health check or fully qualified identifier for + the composite health check. + + To set the composite_health_check attribute: + ▸ provide the argument composite_health_check on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --region=REGION + The name of the Google Compute Engine region. + + To set the region attribute: + ▸ provide the argument composite_health_check on the command line + with a fully specified name; + ▸ provide the argument --region on the command line; + ▸ set the property compute/region. + +REQUIRED FLAGS + At least one of these must be specified: + + --description=DESCRIPTION + A textual description of this resource. + + --health-destination=HEALTH_DESTINATION + URL to the destination resource. Must be set. Must be a + ForwardingRule. The ForwardingRule must have load balancing scheme + INTERNAL or INTERNAL_MANAGED and must be regional and in the same + region as the CompositeHealthCheck (cross-region deployment for + INTERNAL_MANAGED is not supported). Can be mutated. + + --health-sources=[HEALTH_SOURCES,...] + URLs to the HealthSource resources whose results are AND'ed. I.e. the + aggregated result is HEALTHY only if all sources are HEALTHY. Must + have at least 1. Must not have more than 10. Must be regional and in + the same region as the CompositeHealthCheck. Can be mutated. + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the compute/alpha API. The full documentation for this + API can be found at: https://cloud.google.com/compute/ + +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 composite-health-checks update + diff --git a/gcloud/alpha/compute/health-aggregation-policies/create b/gcloud/alpha/compute/health-aggregation-policies/create new file mode 100644 index 000000000..c9e8507fd --- /dev/null +++ b/gcloud/alpha/compute/health-aggregation-policies/create @@ -0,0 +1,116 @@ +NAME + gcloud alpha compute health-aggregation-policies create - create a health + aggregation policy + +SYNOPSIS + gcloud alpha compute health-aggregation-policies create + (HEALTH_AGGREGATION_POLICY : --region=REGION) [--async] + [--description=DESCRIPTION] + [--healthy-percent-threshold=HEALTHY_PERCENT_THRESHOLD; default=60] + [--min-healthy-threshold=MIN_HEALTHY_THRESHOLD; default=1] + [--policy-type=POLICY_TYPE; default="backend-service-policy"] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Create a health aggregation policy. + +EXAMPLES + The following command creates a new health aggregation policy: + + $ gcloud alpha compute health-aggregation-policies create \ + --region= \ + --healthy-percent-threshold 60 --min-healthy-threshold 2 \ + --policy-type=BACKEND_SERVICE_POLICY + +POSITIONAL ARGUMENTS + Health aggregation policy resource - The name of the health aggregation + policy you want to create. 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 health_aggregation_policy 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. + + HEALTH_AGGREGATION_POLICY + ID of the health aggregation policy or fully qualified identifier for + the health aggregation policy. + + To set the health_aggregation_policy attribute: + ▸ provide the argument health_aggregation_policy on the command + line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --region=REGION + The name of the Google Compute Engine region. + + To set the region attribute: + ▸ provide the argument health_aggregation_policy on the command + line with a fully specified name; + ▸ provide the argument --region on the command line; + ▸ set the property compute/region. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --description=DESCRIPTION + A textual description of the health aggregation policy. + + --healthy-percent-threshold=HEALTHY_PERCENT_THRESHOLD; default=60 + Can only be set if the policyType field is BACKEND_SERVICE_POLICY. + Specifies the threshold (as a percentage) of healthy endpoints required + in order to consider the aggregated health result HEALTHY. Defaults to + 60. Must be in range [0, 100]. Not applicable if the policyType field + is DNS_PUBLIC_IP_POLICY. Can be mutated. This field is optional, and + will be set to the default if unspecified. Note that both this + threshold and minHealthyThreshold must be satisfied in order for + HEALTHY to be the aggregated result. "Endpoints" refers to network + endpoints within a Network Endpoint Group or instances within an + Instance Group. + + --min-healthy-threshold=MIN_HEALTHY_THRESHOLD; default=1 + Can only be set if the policyType field is BACKEND_SERVICE_POLICY. + Specifies the minimum number of healthy endpoints required in order to + consider the aggregated health result HEALTHY. Defaults to 1. Must be + positive. Not applicable if the policyType field is + DNS_PUBLIC_IP_POLICY. Can be mutated. This field is optional, and will + be set to the default if unspecified. Note that both this threshold and + healthyPercentThreshold must be satisfied in order for HEALTHY to be + the aggregated result. "Endpoints" refers to network endpoints within a + Network Endpoint Group or instances within an Instance Group. + + --policy-type=POLICY_TYPE; default="backend-service-policy" + Specifies the type of the healthAggregationPolicy. The only allowed + value for regional resources is BACKEND_SERVICE_POLICY. Must be + specified when the healthAggregationPolicy is created, and cannot be + mutated. POLICY_TYPE must be one of: backend-service-policy, + dns-public-ip-policy. + +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 compute/alpha API. The full documentation for this + API can be found at: https://cloud.google.com/compute/ + +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 health-aggregation-policies create + diff --git a/gcloud/alpha/compute/health-aggregation-policies/delete b/gcloud/alpha/compute/health-aggregation-policies/delete new file mode 100644 index 000000000..7743e17d5 --- /dev/null +++ b/gcloud/alpha/compute/health-aggregation-policies/delete @@ -0,0 +1,77 @@ +NAME + gcloud alpha compute health-aggregation-policies delete - delete a health + aggregation policy + +SYNOPSIS + gcloud alpha compute health-aggregation-policies delete + (HEALTH_AGGREGATION_POLICY : --region=REGION) [--async] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Delete a health aggregation policy. + +EXAMPLES + To delete a single health aggregation policy, run the following command: + + $ gcloud alpha compute health-aggregation-policies delete \ + --region= + +POSITIONAL ARGUMENTS + Health aggregation policy resource - Name of the health aggregation policy + you want to delete. The arguments in this group can be used to specify the + attributes of this resource. (NOTE) Some attributes are not given + arguments in this group but can be set in other ways. + + To set the project attribute: + ◆ provide the argument health_aggregation_policy 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. + + HEALTH_AGGREGATION_POLICY + ID of the health aggregation policy or fully qualified identifier for + the health aggregation policy. + + To set the health_aggregation_policy attribute: + ▸ provide the argument health_aggregation_policy on the command + line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --region=REGION + The name of the Google Compute Engine region. + + To set the region attribute: + ▸ provide the argument health_aggregation_policy on the command + line with a fully specified name; + ▸ provide the argument --region on the command line; + ▸ set the property compute/region. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the compute/alpha API. The full documentation for this + API can be found at: https://cloud.google.com/compute/ + +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 health-aggregation-policies delete + diff --git a/gcloud/alpha/compute/health-aggregation-policies/describe b/gcloud/alpha/compute/health-aggregation-policies/describe new file mode 100644 index 000000000..9f9f970a0 --- /dev/null +++ b/gcloud/alpha/compute/health-aggregation-policies/describe @@ -0,0 +1,72 @@ +NAME + gcloud alpha compute health-aggregation-policies describe - describe a + health aggregation policy + +SYNOPSIS + gcloud alpha compute health-aggregation-policies describe + (HEALTH_AGGREGATION_POLICY : --region=REGION) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Describe a health aggregation policy. + +EXAMPLES + To retrieve a single health aggregation policy and print its properties, + run the following command: + + $ gcloud alpha compute health-aggregation-policies describe \ + --region= + +POSITIONAL ARGUMENTS + Health aggregation policy resource - Name of the health aggregation policy + you want to inspect. 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 health_aggregation_policy 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. + + HEALTH_AGGREGATION_POLICY + ID of the health aggregation policy or fully qualified identifier for + the health aggregation policy. + + To set the health_aggregation_policy attribute: + ▸ provide the argument health_aggregation_policy on the command + line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --region=REGION + The name of the Google Compute Engine region. + + To set the region attribute: + ▸ provide the argument health_aggregation_policy on the command + line with a fully specified name; + ▸ provide the argument --region on the command line; + ▸ set the property compute/region. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the compute/alpha API. The full documentation for this + API can be found at: https://cloud.google.com/compute/ + +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 health-aggregation-policies describe + diff --git a/gcloud/alpha/compute/health-aggregation-policies/help b/gcloud/alpha/compute/health-aggregation-policies/help new file mode 100644 index 000000000..473f23231 --- /dev/null +++ b/gcloud/alpha/compute/health-aggregation-policies/help @@ -0,0 +1,42 @@ +NAME + gcloud alpha compute health-aggregation-policies - manage health + aggregation policies + +SYNOPSIS + gcloud alpha compute health-aggregation-policies COMMAND + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Manage health aggregation policies. + +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 health aggregation policy. + + delete + (ALPHA) Delete a health aggregation policy. + + describe + (ALPHA) Describe a health aggregation policy. + + list + (ALPHA) List health aggregation policies. + + update + (ALPHA) Update a health aggregation policy. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud beta compute health-aggregation-policies + diff --git a/gcloud/alpha/compute/tpus/list b/gcloud/alpha/compute/health-aggregation-policies/list similarity index 55% rename from gcloud/alpha/compute/tpus/list rename to gcloud/alpha/compute/health-aggregation-policies/list index 3ac9976c9..f8c65e128 100644 --- a/gcloud/alpha/compute/tpus/list +++ b/gcloud/alpha/compute/health-aggregation-policies/list @@ -1,44 +1,34 @@ NAME - gcloud alpha compute tpus list - list Cloud TPUs + gcloud alpha compute health-aggregation-policies list - list health + aggregation policies SYNOPSIS - gcloud alpha compute tpus list [--zone=ZONE] [--filter=EXPRESSION] - [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] - [GCLOUD_WIDE_FLAG ...] + gcloud alpha compute health-aggregation-policies list [NAME ...] + [--regexp=REGEXP, -r REGEXP] [--regions=REGION,[REGION,...]] + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) (DEPRECATED) This command is being deprecated. Please use gcloud - compute tpus tpu-vm list instead. + (ALPHA) List health aggregation policies. - List Cloud TPUs +POSITIONAL ARGUMENTS + [NAME ...] + (DEPRECATED) If provided, show details for the specified names and/or + URIs of resources. -EXAMPLES - The following command lists the status of TPUs in zone us-central1-b: - - $ gcloud alpha compute tpus list --zone=us-central1-b + Argument NAME is deprecated. Use --filter="name=( 'NAME' ... )" + instead. FLAGS - Location resource - The compute/zone of the Cloud TPU. + --regexp=REGEXP, -r REGEXP + (DEPRECATED) Regular expression to filter the names of the results on. + Any names that do not match the entire regular expression will be + filtered out. - If not specified, will use the value of the [compute/zone] property in the - current gcloud configuration. To find a list of compute zones available - for Cloud TPUs in your project, run gcloud alpha compute tpus locations - list. This represents a Cloud resource. (NOTE) Some attributes are not - given arguments in this group but can be set in other ways. + Flag --regexp is deprecated. Use --filter="name~'REGEXP'" instead. - To set the project attribute: - ◆ provide the argument --zone on the command line with a fully - specified name; - ◆ set the property compute/zone with a fully specified name; - ◆ provide the argument --project on the command line; - ◆ set the property core/project. - - --zone=ZONE - ID of the location or fully qualified identifier for the location. - - To set the zone attribute: - ▸ provide the argument --zone on the command line; - ▸ set the property compute/zone. + --regions=REGION,[REGION,...] + If provided, only resources from the given regions are queried. LIST COMMAND FLAGS --filter=EXPRESSION @@ -80,17 +70,11 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. -API REFERENCE - This command uses the tpu/v1 API. The full documentation for this API can - be found at: https://cloud.google.com/tpu/ - 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 tpus list - - $ gcloud beta compute tpus list + $ gcloud beta compute health-aggregation-policies list diff --git a/gcloud/alpha/compute/health-aggregation-policies/update b/gcloud/alpha/compute/health-aggregation-policies/update new file mode 100644 index 000000000..468497ea4 --- /dev/null +++ b/gcloud/alpha/compute/health-aggregation-policies/update @@ -0,0 +1,111 @@ +NAME + gcloud alpha compute health-aggregation-policies update - update a health + aggregation policy + +SYNOPSIS + gcloud alpha compute health-aggregation-policies update + (HEALTH_AGGREGATION_POLICY : --region=REGION) + (--description=DESCRIPTION + --healthy-percent-threshold=HEALTHY_PERCENT_THRESHOLD + --min-healthy-threshold=MIN_HEALTHY_THRESHOLD) [--async] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Update a health aggregation policy. + +EXAMPLES + The following command updates a health aggregation policy: + + $ gcloud alpha compute health-aggregation-policies update \ + --region= \ + --healthy-percent-threshold 60 --min-healthy-threshold 2 \ + +POSITIONAL ARGUMENTS + Health aggregation policy resource - The health aggregation policy you + want to update. The arguments in this group can be used to specify the + attributes of this resource. (NOTE) Some attributes are not given + arguments in this group but can be set in other ways. + + To set the project attribute: + ◆ provide the argument health_aggregation_policy 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. + + HEALTH_AGGREGATION_POLICY + ID of the health aggregation policy or fully qualified identifier for + the health aggregation policy. + + To set the health_aggregation_policy attribute: + ▸ provide the argument health_aggregation_policy on the command + line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --region=REGION + The name of the Google Compute Engine region. + + To set the region attribute: + ▸ provide the argument health_aggregation_policy on the command + line with a fully specified name; + ▸ provide the argument --region on the command line; + ▸ set the property compute/region. + +REQUIRED FLAGS + At least one of these must be specified: + + --description=DESCRIPTION + A textual description of the health aggregation policy. + + --healthy-percent-threshold=HEALTHY_PERCENT_THRESHOLD + Can only be set if the policyType field is BACKEND_SERVICE_POLICY. + Specifies the threshold (as a percentage) of healthy endpoints + required in order to consider the aggregated health result HEALTHY. + Defaults to 60. Must be in range [0, 100]. Not applicable if the + policyType field is DNS_PUBLIC_IP_POLICY. Can be mutated. This field + is optional, and will be set to the default if unspecified. Note that + both this threshold and minHealthyThreshold must be satisfied in + order for HEALTHY to be the aggregated result. "Endpoints" refers to + network endpoints within a Network Endpoint Group or instances within + an Instance Group. + + --min-healthy-threshold=MIN_HEALTHY_THRESHOLD + Can only be set if the policyType field is BACKEND_SERVICE_POLICY. + Specifies the minimum number of healthy endpoints required in order + to consider the aggregated health result HEALTHY. Defaults to 1. Must + be positive. Not applicable if the policyType field is + DNS_PUBLIC_IP_POLICY. Can be mutated. This field is optional, and + will be set to the default if unspecified. Note that both this + threshold and healthyPercentThreshold must be satisfied in order for + HEALTHY to be the aggregated result. "Endpoints" refers to network + endpoints within a Network Endpoint Group or instances within an + Instance Group. + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the compute/alpha API. The full documentation for this + API can be found at: https://cloud.google.com/compute/ + +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 health-aggregation-policies update + diff --git a/gcloud/alpha/compute/help b/gcloud/alpha/compute/help index 55ab99e7b..d9be00eb5 100644 --- a/gcloud/alpha/compute/help +++ b/gcloud/alpha/compute/help @@ -43,6 +43,9 @@ GROUPS commitments (ALPHA) Manage Compute Engine commitments. + composite-health-checks + (ALPHA) Manage composite health checks. + diagnose (ALPHA) Debugging tools for Compute Engine virtual machine instances. @@ -71,6 +74,9 @@ GROUPS future-reservations (ALPHA) Manage Compute Engine future reservations. + health-aggregation-policies + (ALPHA) Manage health aggregation policies. + health-checks (ALPHA) Read and manipulate health checks for load balanced instances. @@ -128,6 +134,9 @@ GROUPS network-firewall-policies (ALPHA) Manage Compute Engine network firewall policies. + network-policies + (ALPHA) Manage Compute Engine network policies. + network-profiles (ALPHA) Read Compute Engine network profiles. diff --git a/gcloud/alpha/compute/instances/help b/gcloud/alpha/compute/instances/help index 987776a4c..aea57020f 100644 --- a/gcloud/alpha/compute/instances/help +++ b/gcloud/alpha/compute/instances/help @@ -113,10 +113,6 @@ COMMANDS list (ALPHA) List Compute Engine instances. - move - (ALPHA) (DEPRECATED) Move an instance and its attached persistent disks - between zones. - patch-partner-metadata (ALPHA) Patch partner metadata. diff --git a/gcloud/alpha/compute/instances/move b/gcloud/alpha/compute/instances/move deleted file mode 100644 index 798f5fbcf..000000000 --- a/gcloud/alpha/compute/instances/move +++ /dev/null @@ -1,98 +0,0 @@ -NAME - gcloud alpha compute instances move - move an instance and its attached - persistent disks between zones - -SYNOPSIS - gcloud alpha compute instances move INSTANCE_NAME - --destination-zone=DESTINATION_ZONE [--async] [--zone=ZONE] - [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (ALPHA) (DEPRECATED) This command is deprecated. Please see - https://cloud.google.com/compute/docs/instances/moving-instance-across-zones - for an alternative method. - - gcloud alpha compute instances move moves a Compute Engine virtual machine - from one zone to another. Moving a virtual machine might incur downtime if - the guest OS must be shut down in order to quiesce disk volumes prior to - snapshotting. - - For example, running the following command moves the instance called - example-instance-1 with its attached persistent disks, currently running in - us-central1-b, to us-central1-f. - - $ gcloud compute instances move example-instance-1 \ - --zone=us-central1-b --destination-zone=us-central1-f - - Note: Moving VMs or disks by using the gcloud alpha compute instances move - command might cause unexpected behavior. For more information, see - https://cloud.google.com/compute/docs/troubleshooting/known-issues#moving_vms_or_disks_using_the_moveinstance_api_or_the_causes_unexpected_behavior. - - Please note that gcloud compute instances move does not yet support - instances which have regional persistent disks attached. Please see - https://cloud.google.com/compute/docs/disks/regional-persistent-disk for - more details. - -EXAMPLES - To move instance-1 from us-central-a to europe-west1-d, run: - - $ gcloud alpha compute instances move instance-1 \ - --zone=us-central1-a --destination-zone=europe-west1-d - -POSITIONAL ARGUMENTS - INSTANCE_NAME - Name of the instance to operate on. For details on valid instance - names, refer to the criteria documented under the field 'name' at: - https://cloud.google.com/compute/docs/reference/rest/v1/instances - -REQUIRED FLAGS - --destination-zone=DESTINATION_ZONE - The zone to move the instance to. - -OPTIONAL FLAGS - --async - Return immediately, without waiting for the operation in progress to - complete. - - --zone=ZONE - Zone of the instance to operate on. If not specified, you might be - prompted to select a zone (interactive mode only). gcloud attempts to - identify the appropriate zone by searching for resources in your - currently active project. If the zone cannot be determined, gcloud - prompts you for a selection with all available Google Cloud Platform - zones. - - To avoid prompting when this flag is omitted, the user can set the - compute/zone property: - - $ gcloud config set compute/zone ZONE - - A list of zones can be fetched by running: - - $ gcloud compute zones list - - To unset the property, run: - - $ gcloud config unset compute/zone - - Alternatively, the zone can be stored in the environment variable - CLOUDSDK_COMPUTE_ZONE. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --configuration, --flags-file, --flatten, --format, - --help, --impersonate-service-account, --log-http, --project, --quiet, - --trace-token, --user-output-enabled, --verbosity. - - Run $ gcloud help for details. - -NOTES - This command is currently in alpha and might change without notice. If this - command fails with API permission errors despite specifying the correct - project, you might be trying to access an API with an invitation-only early - access allowlist. These variants are also available: - - $ gcloud compute instances move - - $ gcloud beta compute instances move - diff --git a/gcloud/alpha/compute/interconnects/cross-site-networks/create b/gcloud/alpha/compute/interconnects/cross-site-networks/create index 308f8482a..2f17c8b74 100644 --- a/gcloud/alpha/compute/interconnects/cross-site-networks/create +++ b/gcloud/alpha/compute/interconnects/cross-site-networks/create @@ -17,8 +17,7 @@ EXAMPLES To create a cross site network, run: $ gcloud alpha compute interconnects cross-site-networks create \ - example-cross-site-network --project=my-project \ - --description="Example cross site network" + example-csn --description="Example cross site network" POSITIONAL ARGUMENTS NAME @@ -40,7 +39,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud compute interconnects cross-site-networks create $ gcloud beta compute interconnects cross-site-networks create diff --git a/gcloud/alpha/compute/interconnects/cross-site-networks/delete b/gcloud/alpha/compute/interconnects/cross-site-networks/delete index 1e42618bb..8d0f04949 100644 --- a/gcloud/alpha/compute/interconnects/cross-site-networks/delete +++ b/gcloud/alpha/compute/interconnects/cross-site-networks/delete @@ -7,8 +7,19 @@ SYNOPSIS [NAME ...] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) gcloud alpha compute interconnects cross-site-networks delete - deletes Compute Engine cross site networks. + (ALPHA) gcloud alpha compute interconnects cross-site-networks delete is + used to delete cross site networks. + + For an example, refer to the EXAMPLES section below. + +EXAMPLES + To delete a cross site network, run: + + $ gcloud alpha compute interconnects cross-site-networks delete \ + example-csn + + Although not shown in this example, you can delete multiple cross site + networks in a single command. POSITIONAL ARGUMENTS NAME [NAME ...] @@ -26,7 +37,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud compute interconnects cross-site-networks delete $ gcloud beta compute interconnects cross-site-networks delete diff --git a/gcloud/alpha/compute/interconnects/cross-site-networks/describe b/gcloud/alpha/compute/interconnects/cross-site-networks/describe index 52e1f27a9..19d3a9451 100644 --- a/gcloud/alpha/compute/interconnects/cross-site-networks/describe +++ b/gcloud/alpha/compute/interconnects/cross-site-networks/describe @@ -7,9 +7,16 @@ SYNOPSIS [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) gcloud alpha compute interconnects cross-site-networks describe - displays all data associated with Compute Engine cross site network in a - project. + (ALPHA) gcloud alpha compute interconnects cross-site-networks describe is + used to describe a cross site network. + + For an example, refer to the EXAMPLES section below. + +EXAMPLES + To describe a cross site network, run: + + $ gcloud alpha compute interconnects cross-site-networks describe \ + example-csn POSITIONAL ARGUMENTS NAME @@ -27,7 +34,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud compute interconnects cross-site-networks describe $ gcloud beta compute interconnects cross-site-networks describe diff --git a/gcloud/alpha/compute/interconnects/cross-site-networks/help b/gcloud/alpha/compute/interconnects/cross-site-networks/help index 111779d32..87aaca767 100644 --- a/gcloud/alpha/compute/interconnects/cross-site-networks/help +++ b/gcloud/alpha/compute/interconnects/cross-site-networks/help @@ -36,7 +36,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud compute interconnects cross-site-networks $ gcloud beta compute interconnects cross-site-networks diff --git a/gcloud/alpha/compute/interconnects/cross-site-networks/list b/gcloud/alpha/compute/interconnects/cross-site-networks/list index e9d0c39ca..938883eca 100644 --- a/gcloud/alpha/compute/interconnects/cross-site-networks/list +++ b/gcloud/alpha/compute/interconnects/cross-site-networks/list @@ -64,7 +64,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud compute interconnects cross-site-networks list $ gcloud beta compute interconnects cross-site-networks list diff --git a/gcloud/alpha/compute/interconnects/cross-site-networks/update b/gcloud/alpha/compute/interconnects/cross-site-networks/update index dd7a4fe82..3f1e30fac 100644 --- a/gcloud/alpha/compute/interconnects/cross-site-networks/update +++ b/gcloud/alpha/compute/interconnects/cross-site-networks/update @@ -8,8 +8,15 @@ SYNOPSIS DESCRIPTION (ALPHA) gcloud alpha compute interconnects cross-site-networks update is - used to update cross site networks. A cross site network encapsulates wire - groups. + used to update cross site networks. + + For an example, refer to the EXAMPLES section below. + +EXAMPLES + To update a cross site network's description, run: + + $ gcloud alpha compute interconnects cross-site-networks update \ + example-csn --description="New description" POSITIONAL ARGUMENTS NAME @@ -31,7 +38,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud compute interconnects cross-site-networks update $ gcloud beta compute interconnects cross-site-networks update diff --git a/gcloud/alpha/compute/interconnects/wire-groups/add-endpoint b/gcloud/alpha/compute/interconnects/wire-groups/add-endpoint index 619769149..d6f105888 100644 --- a/gcloud/alpha/compute/interconnects/wire-groups/add-endpoint +++ b/gcloud/alpha/compute/interconnects/wire-groups/add-endpoint @@ -14,12 +14,11 @@ DESCRIPTION For an example, refer to the EXAMPLES section below. EXAMPLES - To add endpoint example-endpoint to wire group example-wire-group, run: + To add an endpoint to a wire group, run: $ gcloud alpha compute interconnects wire-groups add-endpoint \ - example-wire-group --project=example-project \ - --cross-site-network=example-cross-site-network \ - --endpoint-label=example-endpoint + example-wg --cross-site-network=example-csn \ + --endpoint-label=endpoint-1 POSITIONAL ARGUMENTS NAME @@ -44,7 +43,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud compute interconnects wire-groups add-endpoint $ gcloud beta compute interconnects wire-groups add-endpoint diff --git a/gcloud/alpha/compute/interconnects/wire-groups/add-interconnect b/gcloud/alpha/compute/interconnects/wire-groups/add-interconnect index 47119c57a..713a4475f 100644 --- a/gcloud/alpha/compute/interconnects/wire-groups/add-interconnect +++ b/gcloud/alpha/compute/interconnects/wire-groups/add-interconnect @@ -15,15 +15,13 @@ DESCRIPTION For an example, refer to the EXAMPLES section below. EXAMPLES - To add an interconnect example-interconnect to wire group - example-wire-group, run: + To add an interconnect to a wire group, run: $ gcloud alpha compute interconnects wire-groups add-interconnect \ - example-wire-group --project=example-project \ - --cross-site-network=example-cross-site-network \ - --endpoint-label=example-endpoint \ - --interconnect-label=example-interconnect \ - --interconnect=some-interconnect-uri --vlan-tags=111,222 + example-wg --cross-site-network=example-csn \ + --endpoint-label=endpoint-1 \ + --interconnect-label=interconnect-1 \ + --interconnect=example-interconnect --vlan-tags=111 POSITIONAL ARGUMENTS NAME @@ -57,7 +55,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud compute interconnects wire-groups add-interconnect $ gcloud beta compute interconnects wire-groups add-interconnect diff --git a/gcloud/alpha/compute/interconnects/wire-groups/create b/gcloud/alpha/compute/interconnects/wire-groups/create index e7e2d8d87..00397ebcb 100644 --- a/gcloud/alpha/compute/interconnects/wire-groups/create +++ b/gcloud/alpha/compute/interconnects/wire-groups/create @@ -23,10 +23,8 @@ DESCRIPTION EXAMPLES To create a wire group, run: - $ gcloud alpha compute interconnects wire-groups create \ - example-wire-group --project my-project \ - --cross-site-network example-cross-site-network \ - --bandwidth-unmetered 1 + $ gcloud alpha compute interconnects wire-groups create example-wg \ + --cross-site-network=example-csn --bandwidth-unmetered=1 POSITIONAL ARGUMENTS NAME @@ -110,7 +108,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud compute interconnects wire-groups create $ gcloud beta compute interconnects wire-groups create diff --git a/gcloud/alpha/compute/interconnects/wire-groups/delete b/gcloud/alpha/compute/interconnects/wire-groups/delete index 677472567..6533b53d5 100644 --- a/gcloud/alpha/compute/interconnects/wire-groups/delete +++ b/gcloud/alpha/compute/interconnects/wire-groups/delete @@ -7,8 +7,16 @@ SYNOPSIS --cross-site-network=CROSS_SITE_NETWORK [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) gcloud alpha compute interconnects wire-groups delete deletes - Compute Engine wire groups. + (ALPHA) gcloud alpha compute interconnects wire-groups delete is used to + delete wire groups. + + For an example, refer to the EXAMPLES section below. + +EXAMPLES + To delete a wire group, run: + + $ gcloud alpha compute interconnects wire-groups delete example-wg \ + --cross-site-network=example-csn POSITIONAL ARGUMENTS NAME [NAME ...] @@ -30,7 +38,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud compute interconnects wire-groups delete $ gcloud beta compute interconnects wire-groups delete diff --git a/gcloud/alpha/compute/interconnects/wire-groups/describe b/gcloud/alpha/compute/interconnects/wire-groups/describe index 868c6af6a..23bed9d65 100644 --- a/gcloud/alpha/compute/interconnects/wire-groups/describe +++ b/gcloud/alpha/compute/interconnects/wire-groups/describe @@ -7,8 +7,16 @@ SYNOPSIS --cross-site-network=CROSS_SITE_NETWORK [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) gcloud alpha compute interconnects wire-groups describe displays - all data associated with Compute Engine wire group in a project. + (ALPHA) gcloud alpha compute interconnects wire-groups describe is used to + describe a wire group. + + For an example, refer to the EXAMPLES section below. + +EXAMPLES + To describe a wire group, run: + + $ gcloud alpha compute interconnects wire-groups describe \ + example-wg --cross-site-network=example-csn POSITIONAL ARGUMENTS NAME @@ -30,7 +38,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud compute interconnects wire-groups describe $ gcloud beta compute interconnects wire-groups describe diff --git a/gcloud/alpha/compute/interconnects/wire-groups/help b/gcloud/alpha/compute/interconnects/wire-groups/help index 57351d99d..bdfe2e106 100644 --- a/gcloud/alpha/compute/interconnects/wire-groups/help +++ b/gcloud/alpha/compute/interconnects/wire-groups/help @@ -48,7 +48,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud compute interconnects wire-groups $ gcloud beta compute interconnects wire-groups diff --git a/gcloud/alpha/compute/interconnects/wire-groups/list b/gcloud/alpha/compute/interconnects/wire-groups/list index ca5e7bf85..1bdbc5cdd 100644 --- a/gcloud/alpha/compute/interconnects/wire-groups/list +++ b/gcloud/alpha/compute/interconnects/wire-groups/list @@ -69,7 +69,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud compute interconnects wire-groups list $ gcloud beta compute interconnects wire-groups list diff --git a/gcloud/alpha/compute/interconnects/wire-groups/remove-endpoint b/gcloud/alpha/compute/interconnects/wire-groups/remove-endpoint index 7d4ee31ea..10eac80d4 100644 --- a/gcloud/alpha/compute/interconnects/wire-groups/remove-endpoint +++ b/gcloud/alpha/compute/interconnects/wire-groups/remove-endpoint @@ -14,13 +14,11 @@ DESCRIPTION For an example, refer to the EXAMPLES section below. EXAMPLES - To remove endpoint example-endpoint from wire group example-wire-group, - run: + To remove an endpoint from a wire group, run: $ gcloud alpha compute interconnects wire-groups remove-endpoint \ - example-wire-group --project=example-project \ - --cross-site-network=example-cross-site-network \ - --endpoint-label=example-endpoint + example-wg --cross-site-network=example-csn \ + --endpoint-label=endpoint-1 POSITIONAL ARGUMENTS NAME @@ -45,7 +43,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud compute interconnects wire-groups remove-endpoint $ gcloud beta compute interconnects wire-groups remove-endpoint diff --git a/gcloud/alpha/compute/interconnects/wire-groups/remove-interconnect b/gcloud/alpha/compute/interconnects/wire-groups/remove-interconnect index 1ae2f1f02..6e385f41a 100644 --- a/gcloud/alpha/compute/interconnects/wire-groups/remove-interconnect +++ b/gcloud/alpha/compute/interconnects/wire-groups/remove-interconnect @@ -14,14 +14,11 @@ DESCRIPTION For an example, refer to the EXAMPLES section below. EXAMPLES - To remove an interconnect example-interconnect from wire group - example-wire-group, run: + To remove an interconnect from a wire group endpoint, run: $ gcloud alpha compute interconnects wire-groups \ - remove-interconnect example-wire-group \ - --project=example-project \ - --cross-site-network=example-cross-site-network \ - --endpoint-label=example-endpoint \ + remove-interconnect example-wg \ + --cross-site-network=example-csn --endpoint-label=endpoint-1 \ --interconnect-label=example-interconnect POSITIONAL ARGUMENTS @@ -50,7 +47,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud compute interconnects wire-groups remove-interconnect $ gcloud beta compute interconnects wire-groups remove-interconnect diff --git a/gcloud/alpha/compute/interconnects/wire-groups/update b/gcloud/alpha/compute/interconnects/wire-groups/update index 4b73a40be..9b3511a7e 100644 --- a/gcloud/alpha/compute/interconnects/wire-groups/update +++ b/gcloud/alpha/compute/interconnects/wire-groups/update @@ -14,7 +14,36 @@ SYNOPSIS DESCRIPTION (ALPHA) gcloud alpha compute interconnects wire-groups update is used to - update wire groups. A wire group represents a group of redundant wires. + update wire groups. + + For an example, refer to the EXAMPLES section below. + +EXAMPLES + To disable a wire group, run: + + $ gcloud alpha compute interconnects wire-groups update example-wg \ + --cross-site-network=example-csn --no-admin-enabled + + To change a wire group's unmetered bandwidth, run: + + $ gcloud alpha compute interconnects wire-groups update example-wg \ + --cross-site-network=example-csn --bandwidth-unmetered=5 + + To enable automatic failure detection for a wire group, run: + + $ gcloud alpha compute interconnects wire-groups update example-wg \ + --cross-site-network=example-csn --fault-response=DISABLE_PORT + + To enable bandwidth sharing for a wire group, run: + + $ gcloud alpha compute interconnects wire-groups update example-wg \ + --cross-site-network=example-csn \ + --bandwidth-allocation=SHARED_WITH_WIRE_GROUP + + To update a wire group's description, run: + + $ gcloud alpha compute interconnects wire-groups update example-wg \ + --cross-site-network=example-csn --description="new description" POSITIONAL ARGUMENTS NAME @@ -97,7 +126,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud compute interconnects wire-groups update $ gcloud beta compute interconnects wire-groups update diff --git a/gcloud/alpha/compute/network-policies/associations/create b/gcloud/alpha/compute/network-policies/associations/create new file mode 100644 index 000000000..d4c79887d --- /dev/null +++ b/gcloud/alpha/compute/network-policies/associations/create @@ -0,0 +1,52 @@ +NAME + gcloud alpha compute network-policies associations create - create a new + association between a network policy and a network + +SYNOPSIS + gcloud alpha compute network-policies associations create --network=NETWORK + --network-policy=NETWORK_POLICY [--name=NAME] + [--network-policy-region=NETWORK_POLICY_REGION] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) gcloud alpha compute network-policies associations create is used + to create network policy associations. A network policy is a set of rules + that controls access to various resources. + +EXAMPLES + To associate a network policy with name my-region-policy in region region-a + to network my-network with an association named my-association, run: + + $ gcloud alpha compute network-policies associations create \ + --network-policy=my-policy --network-policy-region=region-a \ + --network=my-network --name=my-association + +REQUIRED FLAGS + --network=NETWORK + Name of the network with which the association is created. + + --network-policy=NETWORK_POLICY + Network Policy ID with which to create association for association. + +OPTIONAL FLAGS + --name=NAME + Name of the new association. If not specified, the name will be + auto-generated. + + --network-policy-region=NETWORK_POLICY_REGION + Region of the network policy to create. Overrides the default + compute/region property value for this command invocation. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/compute/network-policies/associations/delete b/gcloud/alpha/compute/network-policies/associations/delete new file mode 100644 index 000000000..305a514ca --- /dev/null +++ b/gcloud/alpha/compute/network-policies/associations/delete @@ -0,0 +1,47 @@ +NAME + gcloud alpha compute network-policies associations delete - delete an + association between a network policy and a network + +SYNOPSIS + gcloud alpha compute network-policies associations delete --name=NAME + --network-policy=NETWORK_POLICY + [--network-policy-region=NETWORK_POLICY_REGION] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) gcloud alpha compute network-policies associations delete is used + to delete network policy associations. + +EXAMPLES + To delete an association named my-association from a network policy with + name my-policy in region region-a, run: + + $ gcloud alpha compute network-policies associations delete \ + --network-policy=my-policy --name=my-association \ + --network-policy-region=region-a + +REQUIRED FLAGS + --name=NAME + Name of the association to remove. + + --network-policy=NETWORK_POLICY + Network Policy ID with which to delete association. + +OPTIONAL FLAGS + --network-policy-region=NETWORK_POLICY_REGION + Region of the network policy to delete. Overrides the default + compute/region property value for this command invocation. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/compute/network-policies/associations/describe b/gcloud/alpha/compute/network-policies/associations/describe new file mode 100644 index 000000000..4c2f293c7 --- /dev/null +++ b/gcloud/alpha/compute/network-policies/associations/describe @@ -0,0 +1,47 @@ +NAME + gcloud alpha compute network-policies associations describe - describe an + association between a network policy and a network + +SYNOPSIS + gcloud alpha compute network-policies associations describe --name=NAME + --network-policy=NETWORK_POLICY + [--network-policy-region=NETWORK_POLICY_REGION] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) gcloud alpha compute network-policies associations describe is used + to describe network policy associations. + +EXAMPLES + To describe an association named my-association on a network policy with + name my-policy in region region-a, run: + + $ gcloud alpha compute network-policies associations describe \ + --network-policy=my-policy --name=my-association \ + --network-policy-region=region-a + +REQUIRED FLAGS + --name=NAME + Name of the association to describe. + + --network-policy=NETWORK_POLICY + Network Policy ID with which to describe association. + +OPTIONAL FLAGS + --network-policy-region=NETWORK_POLICY_REGION + Region of the network policy to describe. Overrides the default + compute/region property value for this command invocation. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/compute/network-policies/associations/help b/gcloud/alpha/compute/network-policies/associations/help new file mode 100644 index 000000000..d93746038 --- /dev/null +++ b/gcloud/alpha/compute/network-policies/associations/help @@ -0,0 +1,35 @@ +NAME + gcloud alpha compute network-policies associations - read and manipulate + Compute Engine network policy associations + +SYNOPSIS + gcloud alpha compute network-policies associations COMMAND + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Read and manipulate Compute Engine network policy associations. + +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 new association between a network policy and a + network. + + delete + (ALPHA) Delete an association between a network policy and a network. + + describe + (ALPHA) Describe an association between a network policy and a network. + +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/network-policies/create b/gcloud/alpha/compute/network-policies/create new file mode 100644 index 000000000..bcfafe8b4 --- /dev/null +++ b/gcloud/alpha/compute/network-policies/create @@ -0,0 +1,46 @@ +NAME + gcloud alpha compute network-policies create - create a Compute Engine + network policy + +SYNOPSIS + gcloud alpha compute network-policies create NETWORK_POLICY + [--description=DESCRIPTION] [--region=REGION] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) gcloud alpha compute network-policies create is used to create + network policies. A network policy is a set of rules that classifies + network traffic. + +EXAMPLES + To create a regional network policy named my-region-policy under project + with ID test-project, in region my-region, run: + + $ gcloud alpha compute network-policies create my-region-policy \ + --project=test-project --region=my-region + +POSITIONAL ARGUMENTS + NETWORK_POLICY + name of the network policy to create. + +FLAGS + --description=DESCRIPTION + An optional, textual description for the network policy. + + --region=REGION + Region of the network policy to create. Overrides the default + compute/region property value for this command invocation. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/compute/network-policies/delete b/gcloud/alpha/compute/network-policies/delete new file mode 100644 index 000000000..7bfa2f9b3 --- /dev/null +++ b/gcloud/alpha/compute/network-policies/delete @@ -0,0 +1,42 @@ +NAME + gcloud alpha compute network-policies delete - delete a Compute Engine + network policy + +SYNOPSIS + gcloud alpha compute network-policies delete NETWORK_POLICY + [--region=REGION] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) gcloud alpha compute network-policies delete is used to delete + network policies. A network policy is a set of rules that classifies + network traffic. + +EXAMPLES + To delete a network policy with name my-policy, in region my-region, run: + + $ gcloud alpha compute network-policies delete my-policy \ + --region=my-region + +POSITIONAL ARGUMENTS + NETWORK_POLICY + name of the network policy to delete. + +FLAGS + --region=REGION + Region of the network policy to delete. Overrides the default + compute/region property value for this command invocation. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/compute/network-policies/describe b/gcloud/alpha/compute/network-policies/describe new file mode 100644 index 000000000..12899b957 --- /dev/null +++ b/gcloud/alpha/compute/network-policies/describe @@ -0,0 +1,42 @@ +NAME + gcloud alpha compute network-policies describe - describe a Compute Engine + network policy + +SYNOPSIS + gcloud alpha compute network-policies describe NETWORK_POLICY + [--region=REGION] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) gcloud alpha compute network-policies describe is used to describe + network policies. A network policy is a set of rules that classifies + network traffic. + +EXAMPLES + To describe a network policy with name my-policy, in region my-region, run: + + $ gcloud alpha compute network-policies describe my-policy \ + --region=my-region + +POSITIONAL ARGUMENTS + NETWORK_POLICY + name of the network policy to describe. + +FLAGS + --region=REGION + Region of the network policy to describe. Overrides the default + compute/region property value for this command invocation. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/compute/network-policies/help b/gcloud/alpha/compute/network-policies/help new file mode 100644 index 000000000..9cf51f57b --- /dev/null +++ b/gcloud/alpha/compute/network-policies/help @@ -0,0 +1,50 @@ +NAME + gcloud alpha compute network-policies - manage Compute Engine network + policies + +SYNOPSIS + gcloud alpha compute network-policies GROUP | COMMAND + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Manage Compute Engine network policies. Network policies are used + to classify network traffic. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +GROUPS + GROUP is one of the following: + + associations + (ALPHA) Read and manipulate Compute Engine network policy associations. + + traffic-classification-rules + (ALPHA) Read and manipulate Compute Engine network policy rules. + +COMMANDS + COMMAND is one of the following: + + create + (ALPHA) Create a Compute Engine network policy. + + delete + (ALPHA) Delete a Compute Engine network policy. + + describe + (ALPHA) Describe a Compute Engine network policy. + + list + (ALPHA) List Compute Engine network policies. + + update + (ALPHA) Update a Compute Engine network policy. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/compute/tpus/execution-groups/list b/gcloud/alpha/compute/network-policies/list similarity index 62% rename from gcloud/alpha/compute/tpus/execution-groups/list rename to gcloud/alpha/compute/network-policies/list index cbe9e9044..485da89a6 100644 --- a/gcloud/alpha/compute/tpus/execution-groups/list +++ b/gcloud/alpha/compute/network-policies/list @@ -1,47 +1,31 @@ NAME - gcloud alpha compute tpus execution-groups list - list TPU Node+VM groups - created by execution group + gcloud alpha compute network-policies list - list Compute Engine network + policies SYNOPSIS - gcloud alpha compute tpus execution-groups list [--zone=ZONE] + gcloud alpha compute network-policies list [--regions=REGION,[REGION,...]] [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) (DEPRECATED) List TPU Node+VM groups created by execution group. - - This command is deprecated and will be removed in a future release. We - recommend that you use the TPU-VM or Queued Resource API. See - https://cloud.google.com/tpu/docs/managing-tpus-tpu-vm for more - information. + (ALPHA) gcloud alpha compute network-policies list is used to list network + policies. A network policy is a set of rules that controls network traffic + classification. EXAMPLES - To list all active execution groups, run: + To list regional network policies under project my-project, specify a list + of regions with --regions: - $ gcloud alpha compute tpus execution-groups list --zone=test-zone \ - --project=test-project + $ gcloud alpha compute network-policies list --project=my-project \ + --regions="region-a, region-b" + + To list all network policies under project my-project, omit --regions: + + $ gcloud alpha compute network-policies list --project=my-project FLAGS - --zone=ZONE - Zone of the tpu to list. If not specified and the compute/zone property - isn't set, you might be prompted to select a zone (interactive mode - only). - - To avoid prompting when this flag is omitted, you 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. + --regions=REGION,[REGION,...] + If provided, only resources from the given regions are queried. LIST COMMAND FLAGS --filter=EXPRESSION @@ -87,9 +71,5 @@ 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 tpus execution-groups list - - $ gcloud beta compute tpus execution-groups list + access allowlist. diff --git a/gcloud/alpha/compute/network-policies/traffic-classification-rules/create b/gcloud/alpha/compute/network-policies/traffic-classification-rules/create new file mode 100644 index 000000000..f7f80cc95 --- /dev/null +++ b/gcloud/alpha/compute/network-policies/traffic-classification-rules/create @@ -0,0 +1,103 @@ +NAME + gcloud alpha compute network-policies traffic-classification-rules create - + creates a Compute Engine network policy rule + +SYNOPSIS + gcloud alpha compute network-policies traffic-classification-rules create + --action=ACTION --dest-ip-ranges=[DEST_IP_RANGE,...] + --dscp-mode=DSCP_MODE --layer4-configs=[LAYER4_CONFIG,...] + --network-policy=NETWORK_POLICY --priority=PRIORITY + --traffic-class=TRAFFIC_CLASS [--description=DESCRIPTION] + [--[no-]disabled] [--dscp-value=DSCP_VALUE] [--name=NAME] + [--network-policy-region=NETWORK_POLICY_REGION] + [--src-ip-ranges=[SRC_IP_RANGE,...]] + [--target-secure-tags=[TARGET_SECURE_TAGS,...]] + [--target-service-accounts=[TARGET_SERVICE_ACCOUNTS,...]] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) gcloud alpha compute network-policies traffic-classification-rules + create is used to create network policy rules. + +EXAMPLES + To create a traffic classification rule with priority 10 in a network + policy with name my-policy and description example rule, in region + region-a, run: + + $ gcloud alpha compute network-policies \ + traffic-classification-rules create --priority=10 \ + --action=apply_traffic_classification \ + --network-policy=my-policy --network-policy-region=region-a \ + --dest-ip-ranges=11.0.0.0/8 --description="example rule" \ + --traffic-class tc1 --dscp-mode custom --dscp-value 3 \ + --layer4-configs=tcp:80,udp + +REQUIRED FLAGS + --action=ACTION + Action to take if the request matches the match condition. ACTION must + be (only one value is supported): apply_traffic_classification. + + --dest-ip-ranges=[DEST_IP_RANGE,...] + Destination IP ranges to match for this rule. + + --dscp-mode=DSCP_MODE + When set to AUTO, the DSCP value will be picked automatically based on + selected traffic class. Otherwise, DSCP value must be specified. + DSCP_MODE must be one of: auto, custom. + + --layer4-configs=[LAYER4_CONFIG,...] + A list of destination protocols and ports to which the network policy + rule will apply. + + --network-policy=NETWORK_POLICY + Network policy ID with which to create rule. + + --priority=PRIORITY + Priority of the rule to be added. Valid in [1, 2147482547]. + + --traffic-class=TRAFFIC_CLASS + The traffic class that be applied to matching packet. TRAFFIC_CLASS + must be one of: tc1, tc2, tc3, tc4, tc5, tc6. + +OPTIONAL FLAGS + --description=DESCRIPTION + An optional, textual description for the rule. + + --[no-]disabled + Use this flag to disable the rule. Disabled rules will not affect + traffic. Use --disabled to enable and --no-disabled to disable. + + --dscp-value=DSCP_VALUE + Custom DSCP value from 0-63 range. + + --name=NAME + An optional name for the network policy rule. + + --network-policy-region=NETWORK_POLICY_REGION + Region of the network policy to create. Overrides the default + compute/region property value for this command invocation. + + --src-ip-ranges=[SRC_IP_RANGE,...] + CIDR IP address range. + + --target-secure-tags=[TARGET_SECURE_TAGS,...] + An optional, list of target secure tags with a name of the format + tagValues/ or full namespaced name + + --target-service-accounts=[TARGET_SERVICE_ACCOUNTS,...] + List of target service accounts for the rule. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/compute/network-policies/traffic-classification-rules/delete b/gcloud/alpha/compute/network-policies/traffic-classification-rules/delete new file mode 100644 index 000000000..6082de99a --- /dev/null +++ b/gcloud/alpha/compute/network-policies/traffic-classification-rules/delete @@ -0,0 +1,47 @@ +NAME + gcloud alpha compute network-policies traffic-classification-rules delete - + deletes a Compute Engine network policy rule + +SYNOPSIS + gcloud alpha compute network-policies traffic-classification-rules delete + --network-policy=NETWORK_POLICY --priority=PRIORITY + [--network-policy-region=NETWORK_POLICY_REGION] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) gcloud alpha compute network-policies traffic-classification-rules + delete is used to delete network policy rules. + +EXAMPLES + To delete a rule with priority 10 in a network policy with name my-policy, + in region region-a, run: + + $ gcloud alpha compute network-policies \ + traffic-classification-rules delete --priority=10 \ + --network-policy=my-policy --network-policy-region=region-a + +REQUIRED FLAGS + --network-policy=NETWORK_POLICY + Network policy ID with which to delete rule. + + --priority=PRIORITY + Priority of the rule to be removed. Valid in [1, 2147483547]. + +OPTIONAL FLAGS + --network-policy-region=NETWORK_POLICY_REGION + Region of the network policy to delete. Overrides the default + compute/region property value for this command invocation. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/compute/network-policies/traffic-classification-rules/describe b/gcloud/alpha/compute/network-policies/traffic-classification-rules/describe new file mode 100644 index 000000000..495deffec --- /dev/null +++ b/gcloud/alpha/compute/network-policies/traffic-classification-rules/describe @@ -0,0 +1,47 @@ +NAME + gcloud alpha compute network-policies traffic-classification-rules describe + - describes a Compute Engine network policy rule + +SYNOPSIS + gcloud alpha compute network-policies traffic-classification-rules describe + --network-policy=NETWORK_POLICY --priority=PRIORITY + [--network-policy-region=NETWORK_POLICY_REGION] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) gcloud alpha compute network-policies traffic-classification-rules + describe is used to describe network policy rules. + +EXAMPLES + To describe a rule with priority 10 in a network policy with name + my-policy, in region region-a, run: + + $ gcloud alpha compute network-policies \ + traffic-classification-rules describe --priority=10 \ + --network-policy=my-policy --network-policy-region=region-a + +REQUIRED FLAGS + --network-policy=NETWORK_POLICY + Network policy ID with which to describe rule. + + --priority=PRIORITY + Priority of the rule to be described. Valid in [1, 2147483547]. + +OPTIONAL FLAGS + --network-policy-region=NETWORK_POLICY_REGION + Region of the network policy to describe. Overrides the default + compute/region property value for this command invocation. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/compute/network-policies/traffic-classification-rules/help b/gcloud/alpha/compute/network-policies/traffic-classification-rules/help new file mode 100644 index 000000000..008f99c4c --- /dev/null +++ b/gcloud/alpha/compute/network-policies/traffic-classification-rules/help @@ -0,0 +1,37 @@ +NAME + gcloud alpha compute network-policies traffic-classification-rules - read + and manipulate Compute Engine network policy rules + +SYNOPSIS + gcloud alpha compute network-policies traffic-classification-rules COMMAND + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Read and manipulate Compute Engine network policy rules. + +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) Creates a Compute Engine network policy rule. + + delete + (ALPHA) Deletes a Compute Engine network policy rule. + + describe + (ALPHA) Describes a Compute Engine network policy rule. + + update + (ALPHA) Updates a Compute Engine network policy rule. + +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/network-policies/traffic-classification-rules/update b/gcloud/alpha/compute/network-policies/traffic-classification-rules/update new file mode 100644 index 000000000..46d888c8a --- /dev/null +++ b/gcloud/alpha/compute/network-policies/traffic-classification-rules/update @@ -0,0 +1,98 @@ +NAME + gcloud alpha compute network-policies traffic-classification-rules update - + updates a Compute Engine network policy rule + +SYNOPSIS + gcloud alpha compute network-policies traffic-classification-rules update + --network-policy=NETWORK_POLICY --priority=PRIORITY [--action=ACTION] + [--description=DESCRIPTION] [--dest-ip-ranges=[DEST_IP_RANGE,...]] + [--[no-]disabled] [--dscp-mode=DSCP_MODE] [--dscp-value=DSCP_VALUE] + [--layer4-configs=[LAYER4_CONFIG,...]] + [--network-policy-region=NETWORK_POLICY_REGION] + [--new-priority=NEW_PRIORITY] [--src-ip-ranges=[SRC_IP_RANGE,...]] + [--target-secure-tags=[TARGET_SECURE_TAGS,...]] + [--target-service-accounts=[TARGET_SERVICE_ACCOUNTS,...]] + [--traffic-class=TRAFFIC_CLASS] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) gcloud alpha compute network-policies traffic-classification-rules + update is used to update network policy rules. + +EXAMPLES + To update a rule with priority 10 in a network policy with name my-policy + to change the description to new example rule, run: + + $ gcloud alpha compute network-policies \ + traffic-classification-rules update --priority=10 \ + --network-policy=my-policy --description="new example rule" + +REQUIRED FLAGS + --network-policy=NETWORK_POLICY + Network policy ID with which to update rule. + + --priority=PRIORITY + Priority of the rule to be updated. Valid in [1, 2147482547]. + +OPTIONAL FLAGS + --action=ACTION + Action to take if the request matches the match condition. ACTION must + be (only one value is supported): apply_traffic_classification. + + --description=DESCRIPTION + An optional, textual description for the rule. + + --dest-ip-ranges=[DEST_IP_RANGE,...] + Destination IP ranges to match for this rule. + + --[no-]disabled + Use this flag to disable the rule. Disabled rules will not affect + traffic. Use --disabled to enable and --no-disabled to disable. + + --dscp-mode=DSCP_MODE + When set to AUTO, the DSCP value will be picked automatically based on + selected traffic class. Otherwise, DSCP value must be specified. + DSCP_MODE must be one of: auto, custom. + + --dscp-value=DSCP_VALUE + Custom DSCP value from 0-63 range. + + --layer4-configs=[LAYER4_CONFIG,...] + A list of destination protocols and ports to which the network policy + rule will apply. + + --network-policy-region=NETWORK_POLICY_REGION + Region of the network policy to operate on. Overrides the default + compute/region property value for this command invocation. + + --new-priority=NEW_PRIORITY + New priority for the rule to update. Valid priority range: [1, + 2147482547]. + + --src-ip-ranges=[SRC_IP_RANGE,...] + CIDR IP address range. + + --target-secure-tags=[TARGET_SECURE_TAGS,...] + An optional, list of target secure tags with a name of the format + tagValues/ or full namespaced name + + --target-service-accounts=[TARGET_SERVICE_ACCOUNTS,...] + List of target service accounts for the rule. + + --traffic-class=TRAFFIC_CLASS + The traffic class that be applied to matching packet. TRAFFIC_CLASS + must be one of: tc1, tc2, tc3, tc4, tc5, tc6. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/compute/network-policies/update b/gcloud/alpha/compute/network-policies/update new file mode 100644 index 000000000..a1dbbed4d --- /dev/null +++ b/gcloud/alpha/compute/network-policies/update @@ -0,0 +1,46 @@ +NAME + gcloud alpha compute network-policies update - update a Compute Engine + network policy + +SYNOPSIS + gcloud alpha compute network-policies update NETWORK_POLICY + [--description=DESCRIPTION] [--region=REGION] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) gcloud alpha compute network-policies update is used to update + network policies. A network policy is a set of rules that classifies + network traffic. + +EXAMPLES + To update a network policy with name my-policy, to change the description + to New description, run: + + $ gcloud alpha compute network-policies update my-policy \ + --description='New description' --region=my-region + +POSITIONAL ARGUMENTS + NETWORK_POLICY + name of the network policy to update. + +FLAGS + --description=DESCRIPTION + An optional, textual description for the network policy. + + --region=REGION + Region of the network policy to update. Overrides the default + compute/region property value for this command invocation. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/compute/org-security-policies/associations/create b/gcloud/alpha/compute/org-security-policies/associations/create index ef8c98178..415f43f55 100644 --- a/gcloud/alpha/compute/org-security-policies/associations/create +++ b/gcloud/alpha/compute/org-security-policies/associations/create @@ -76,7 +76,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud compute org-security-policies associations create $ gcloud beta compute org-security-policies associations create diff --git a/gcloud/alpha/compute/org-security-policies/associations/delete b/gcloud/alpha/compute/org-security-policies/associations/delete index c9aa95ce9..118799d75 100644 --- a/gcloud/alpha/compute/org-security-policies/associations/delete +++ b/gcloud/alpha/compute/org-security-policies/associations/delete @@ -43,7 +43,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud compute org-security-policies associations delete $ gcloud beta compute org-security-policies associations delete diff --git a/gcloud/alpha/compute/org-security-policies/associations/help b/gcloud/alpha/compute/org-security-policies/associations/help index 52330930b..268ef2e38 100644 --- a/gcloud/alpha/compute/org-security-policies/associations/help +++ b/gcloud/alpha/compute/org-security-policies/associations/help @@ -33,7 +33,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud compute org-security-policies associations $ gcloud beta compute org-security-policies associations diff --git a/gcloud/alpha/compute/org-security-policies/associations/list b/gcloud/alpha/compute/org-security-policies/associations/list index c8c4f30e2..6d4af3386 100644 --- a/gcloud/alpha/compute/org-security-policies/associations/list +++ b/gcloud/alpha/compute/org-security-policies/associations/list @@ -71,7 +71,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud compute org-security-policies associations list $ gcloud beta compute org-security-policies associations list diff --git a/gcloud/alpha/compute/org-security-policies/copy-rules b/gcloud/alpha/compute/org-security-policies/copy-rules index dd5267d0c..4b137c1c3 100644 --- a/gcloud/alpha/compute/org-security-policies/copy-rules +++ b/gcloud/alpha/compute/org-security-policies/copy-rules @@ -46,7 +46,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud compute org-security-policies copy-rules $ gcloud beta compute org-security-policies copy-rules diff --git a/gcloud/alpha/compute/org-security-policies/create b/gcloud/alpha/compute/org-security-policies/create index 64d032d4d..02ea743b5 100644 --- a/gcloud/alpha/compute/org-security-policies/create +++ b/gcloud/alpha/compute/org-security-policies/create @@ -78,7 +78,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud compute org-security-policies create $ gcloud beta compute org-security-policies create diff --git a/gcloud/alpha/compute/org-security-policies/delete b/gcloud/alpha/compute/org-security-policies/delete index 7f8e08fed..a4458b7ca 100644 --- a/gcloud/alpha/compute/org-security-policies/delete +++ b/gcloud/alpha/compute/org-security-policies/delete @@ -37,7 +37,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud compute org-security-policies delete $ gcloud beta compute org-security-policies delete diff --git a/gcloud/alpha/compute/org-security-policies/describe b/gcloud/alpha/compute/org-security-policies/describe index b73afc37a..6761939f2 100644 --- a/gcloud/alpha/compute/org-security-policies/describe +++ b/gcloud/alpha/compute/org-security-policies/describe @@ -37,7 +37,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud compute org-security-policies describe $ gcloud beta compute org-security-policies describe diff --git a/gcloud/alpha/compute/org-security-policies/help b/gcloud/alpha/compute/org-security-policies/help index f37d709aa..b13febf2b 100644 --- a/gcloud/alpha/compute/org-security-policies/help +++ b/gcloud/alpha/compute/org-security-policies/help @@ -59,7 +59,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud compute org-security-policies $ gcloud beta compute org-security-policies diff --git a/gcloud/alpha/compute/org-security-policies/list b/gcloud/alpha/compute/org-security-policies/list index c0c990eaa..ccf9e328c 100644 --- a/gcloud/alpha/compute/org-security-policies/list +++ b/gcloud/alpha/compute/org-security-policies/list @@ -88,7 +88,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud compute org-security-policies list $ gcloud beta compute org-security-policies list diff --git a/gcloud/alpha/compute/org-security-policies/list-rules b/gcloud/alpha/compute/org-security-policies/list-rules index e87be42eb..b9b0b67e4 100644 --- a/gcloud/alpha/compute/org-security-policies/list-rules +++ b/gcloud/alpha/compute/org-security-policies/list-rules @@ -102,7 +102,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud compute org-security-policies list-rules $ gcloud beta compute org-security-policies list-rules diff --git a/gcloud/alpha/compute/org-security-policies/move b/gcloud/alpha/compute/org-security-policies/move index aaad31517..3b739fb39 100644 --- a/gcloud/alpha/compute/org-security-policies/move +++ b/gcloud/alpha/compute/org-security-policies/move @@ -41,7 +41,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud compute org-security-policies move $ gcloud beta compute org-security-policies move diff --git a/gcloud/alpha/compute/org-security-policies/rules/add-preconfig-waf-exclusion b/gcloud/alpha/compute/org-security-policies/rules/add-preconfig-waf-exclusion index 0770a61d2..70cece5ef 100644 --- a/gcloud/alpha/compute/org-security-policies/rules/add-preconfig-waf-exclusion +++ b/gcloud/alpha/compute/org-security-policies/rules/add-preconfig-waf-exclusion @@ -141,7 +141,10 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud compute org-security-policies rules \ + add-preconfig-waf-exclusion $ gcloud beta compute org-security-policies rules \ add-preconfig-waf-exclusion diff --git a/gcloud/alpha/compute/org-security-policies/rules/create b/gcloud/alpha/compute/org-security-policies/rules/create index 683555ed4..7d70827e7 100644 --- a/gcloud/alpha/compute/org-security-policies/rules/create +++ b/gcloud/alpha/compute/org-security-policies/rules/create @@ -122,7 +122,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud compute org-security-policies rules create $ gcloud beta compute org-security-policies rules create diff --git a/gcloud/alpha/compute/org-security-policies/rules/delete b/gcloud/alpha/compute/org-security-policies/rules/delete index 15a475a5c..463e1456a 100644 --- a/gcloud/alpha/compute/org-security-policies/rules/delete +++ b/gcloud/alpha/compute/org-security-policies/rules/delete @@ -44,7 +44,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud compute org-security-policies rules delete $ gcloud beta compute org-security-policies rules delete diff --git a/gcloud/alpha/compute/org-security-policies/rules/describe b/gcloud/alpha/compute/org-security-policies/rules/describe index bb9f85cae..caa58f727 100644 --- a/gcloud/alpha/compute/org-security-policies/rules/describe +++ b/gcloud/alpha/compute/org-security-policies/rules/describe @@ -44,7 +44,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud compute org-security-policies rules describe $ gcloud beta compute org-security-policies rules describe diff --git a/gcloud/alpha/compute/org-security-policies/rules/help b/gcloud/alpha/compute/org-security-policies/rules/help index d8e9e7c17..13283c1e1 100644 --- a/gcloud/alpha/compute/org-security-policies/rules/help +++ b/gcloud/alpha/compute/org-security-policies/rules/help @@ -42,7 +42,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud compute org-security-policies rules $ gcloud beta compute org-security-policies rules diff --git a/gcloud/alpha/compute/org-security-policies/rules/remove-preconfig-waf-exclusion b/gcloud/alpha/compute/org-security-policies/rules/remove-preconfig-waf-exclusion index 535ab610b..6a58105aa 100644 --- a/gcloud/alpha/compute/org-security-policies/rules/remove-preconfig-waf-exclusion +++ b/gcloud/alpha/compute/org-security-policies/rules/remove-preconfig-waf-exclusion @@ -160,7 +160,10 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud compute org-security-policies rules \ + remove-preconfig-waf-exclusion $ gcloud beta compute org-security-policies rules \ remove-preconfig-waf-exclusion diff --git a/gcloud/alpha/compute/org-security-policies/rules/update b/gcloud/alpha/compute/org-security-policies/rules/update index b66b9959d..406e64e8e 100644 --- a/gcloud/alpha/compute/org-security-policies/rules/update +++ b/gcloud/alpha/compute/org-security-policies/rules/update @@ -127,7 +127,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud compute org-security-policies rules update $ gcloud beta compute org-security-policies rules update diff --git a/gcloud/alpha/compute/org-security-policies/update b/gcloud/alpha/compute/org-security-policies/update index 8258a33ad..c2b892b82 100644 --- a/gcloud/alpha/compute/org-security-policies/update +++ b/gcloud/alpha/compute/org-security-policies/update @@ -67,7 +67,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud compute org-security-policies update $ gcloud beta compute org-security-policies update diff --git a/gcloud/alpha/compute/preview-features/describe b/gcloud/alpha/compute/preview-features/describe index 754672f27..349d68c8e 100644 --- a/gcloud/alpha/compute/preview-features/describe +++ b/gcloud/alpha/compute/preview-features/describe @@ -50,7 +50,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud compute preview-features describe $ gcloud beta compute preview-features describe diff --git a/gcloud/alpha/compute/preview-features/help b/gcloud/alpha/compute/preview-features/help index 69d39bb98..e03d77dc5 100644 --- a/gcloud/alpha/compute/preview-features/help +++ b/gcloud/alpha/compute/preview-features/help @@ -29,7 +29,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud compute preview-features $ gcloud beta compute preview-features diff --git a/gcloud/alpha/compute/preview-features/list b/gcloud/alpha/compute/preview-features/list index aa697c0a2..2b622abba 100644 --- a/gcloud/alpha/compute/preview-features/list +++ b/gcloud/alpha/compute/preview-features/list @@ -62,7 +62,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud compute preview-features list $ gcloud beta compute preview-features list diff --git a/gcloud/alpha/compute/preview-features/update b/gcloud/alpha/compute/preview-features/update index f5a839e37..89ad6760a 100644 --- a/gcloud/alpha/compute/preview-features/update +++ b/gcloud/alpha/compute/preview-features/update @@ -69,7 +69,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud compute preview-features update $ gcloud beta compute preview-features update diff --git a/gcloud/alpha/compute/reservations/sub-blocks/help b/gcloud/alpha/compute/reservations/sub-blocks/help index 3795c65cd..b5f071315 100644 --- a/gcloud/alpha/compute/reservations/sub-blocks/help +++ b/gcloud/alpha/compute/reservations/sub-blocks/help @@ -26,7 +26,7 @@ COMMANDS (ALPHA) Perform maintenance on a reservation sub-block. report-subblock-as-faulty - (ALPHA) Report a faulty reservation sub block. + (ALPHA) Report a sub-block within a reservation as faulty. NOTES This command is currently in alpha and might change without notice. If this diff --git a/gcloud/alpha/compute/reservations/sub-blocks/report-subblock-as-faulty b/gcloud/alpha/compute/reservations/sub-blocks/report-subblock-as-faulty index d563412fd..58e7d2f94 100644 --- a/gcloud/alpha/compute/reservations/sub-blocks/report-subblock-as-faulty +++ b/gcloud/alpha/compute/reservations/sub-blocks/report-subblock-as-faulty @@ -1,6 +1,6 @@ NAME gcloud alpha compute reservations sub-blocks report-subblock-as-faulty - - report a faulty reservation sub block + report a sub-block within a reservation as faulty SYNOPSIS gcloud alpha compute reservations sub-blocks report-subblock-as-faulty @@ -11,7 +11,7 @@ SYNOPSIS --sub-block-name=SUB_BLOCK_NAME [--zone=ZONE] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) Report a faulty reservation sub block. + (ALPHA) Report a sub-block within a reservation as faulty. EXAMPLES To report reservation exr-1 in ZONE with block name block-1 and sub block @@ -26,7 +26,8 @@ EXAMPLES POSITIONAL ARGUMENTS RESERVATION - Name of the reservation to report-subblock-as-faulty. + The name of the reservation containing the sub-block to report as + faulty REQUIRED FLAGS --block-name=BLOCK_NAME @@ -37,7 +38,7 @@ REQUIRED FLAGS (only one value is supported): IMMEDIATE - All VMs will be disrupted immediately. + All VMs are immediately disrupted. --failure-component=FAILURE_COMPONENT The component that experienced the fault. FAILURE_COMPONENT must be one @@ -49,10 +50,10 @@ REQUIRED FLAGS The NVLink switch experienced the fault. --fault-reasons=[behavior=BEHAVIOR],[description=DESCRIPTION] - The reasons for the fault experienced with the sub-block. This flag can - be repeated. Each instance should specify a "behavior" and an optional - "description". The possible values for "behavior" are: PERFORMANCE, - SWITCH_FAILURE, GPU_ERROR. + The reasons for reporting the sub-block as faulty. You can repeat this + flag. Each flag must specify a "behavior" attribute and can optionally + include a "description" attribute. The possible values for "behavior" + are: PERFORMANCE, SWITCH_FAILURE, GPU_ERROR. --sub-block-name=SUB_BLOCK_NAME The name of the reservation sub block. @@ -91,5 +92,10 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. + access allowlist. These variants are also available: + + $ gcloud compute reservations sub-blocks report-subblock-as-faulty + + $ gcloud beta compute reservations sub-blocks \ + report-subblock-as-faulty diff --git a/gcloud/alpha/compute/service-attachments/update b/gcloud/alpha/compute/service-attachments/update index 2a3c48031..143ab0686 100644 --- a/gcloud/alpha/compute/service-attachments/update +++ b/gcloud/alpha/compute/service-attachments/update @@ -5,7 +5,7 @@ NAME SYNOPSIS gcloud alpha compute service-attachments update NAME [--connection-preference=CONNECTION_PREFERENCE] - [--consumer-accept-list=[PROJECT_OR_NETWORK=LIMIT,...]] + [--consumer-accept-list=[PROJECT_OR_NETWORK_OR_ENDPOINT=LIMIT,...]] [--consumer-reject-list=[REJECT_LIST,...]] [--description=DESCRIPTION] [--[no-]enable-proxy-protocol] [--nat-subnets=NAT_SUBNETS,[NAT_SUBNETS,...]] @@ -52,21 +52,22 @@ FLAGS Only accept connection requests from consumers with the approval of the service provider. - --consumer-accept-list=[PROJECT_OR_NETWORK=LIMIT,...] - Specifies which consumer projects or networks are allowed to connect to - the service attachment. Each project or network has a connection limit. - A given service attachment can manage connections at either the project - or network level. Therefore, both the accept and reject lists for a - given service attachment must contain either only projects or only - networks. + --consumer-accept-list=[PROJECT_OR_NETWORK_OR_ENDPOINT=LIMIT,...] + Specifies which consumer projects/networks/endpoints are allowed to + connect to the service attachment. Each project or network has a + connection limit. For endpoints, the connection limit is optional. Both + the accept and reject lists for a given service attachment must contain + either only one of projects, networks or endpoints. For example, --consumer-accept-list myProjectId1=20 accepts a consumer project myProjectId1 with connection limit 20; --consumer-accept-list projects/myProjectId1/global/networks/myNet1=20 accepts a consumer - network myNet1 with connection limit 20 + network myNet1 with connection limit 20 --consumer-accept-list + projects/myProjectId1/regions/myRegion1/forwardingRules/8167352512 also + accepts a consumer endpoint with ID 8167352512. - ◆ PROJECT_OR_NETWORK - Consumer project ID, project number or network - URL. + ◆ PROJECT_OR_NETWORK_OR_ENDPOINT - Consumer project ID/number or + network URL orendpoint URL. ◆ CONNECTION_LIMIT - The maximum number of allowed connections. --consumer-reject-list=[REJECT_LIST,...] diff --git a/gcloud/alpha/compute/tpus/create b/gcloud/alpha/compute/tpus/create deleted file mode 100644 index 5c9346e05..000000000 --- a/gcloud/alpha/compute/tpus/create +++ /dev/null @@ -1,185 +0,0 @@ -NAME - gcloud alpha compute tpus create - create a new Cloud TPU - -SYNOPSIS - gcloud alpha compute tpus create (TPU : --zone=ZONE) --version=VERSION - [--accelerator-type=ACCELERATOR_TYPE; default="v2-8"] [--async] - [--description=DESCRIPTION] [--network=NETWORK; default="default"] - [--preemptible] [--range=RANGE] [--reserved] [--use-service-networking] - [--model-base-path=MODEL_BASE_PATH --model-name=MODEL_NAME - | --model-config-file=MODEL_CONFIG_FILE - --platform-config-file=PLATFORM_CONFIG_FILE] [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (ALPHA) (DEPRECATED) This command is being deprecated. Please use gcloud - compute tpus tpu-vm create instead. - - Create a new Cloud TPU. - -EXAMPLES - The following command creates a TPU with ID my-tpu in the default user - project, network and compute/region (with other defaults supplied by API): - - $ gcloud alpha compute tpus create my-tpu - - The following command creates a TPU with ID my-tpu with explicit values for - all required and optional parameters: - - $ gcloud alpha compute tpus create my-tpu --zone=us-central1-a \ - --range='10.240.0.0/29' --accelerator-type='v2-8' \ - --network=my-tf-network --description='My TF Node' \ - --version='1.1' - -POSITIONAL ARGUMENTS - Tpu resource - The Cloud TPU you want to create. The arguments in this - group can be used to specify the attributes of this resource. (NOTE) Some - attributes are not given arguments in this group but can be set in other - ways. - - To set the project attribute: - ◆ provide the argument tpu on the command line with a fully specified - name; - ◆ provide the argument --project on the command line; - ◆ set the property core/project. - - This must be specified. - - TPU - ID of the tpu or fully qualified identifier for the tpu. - - To set the tpu attribute: - ▸ provide the argument tpu on the command line. - - This positional argument must be specified if any of the other - arguments in this group are specified. - - --zone=ZONE - The compute/zone of the Cloud TPU. - - If not specified, will use default compute/zone. - - To set the zone attribute: - ▸ provide the argument tpu on the command line with a fully - specified name; - ▸ provide the argument --zone on the command line; - ▸ set the property compute/zone. - -REQUIRED FLAGS - --version=VERSION - TensorFlow version for the TPU, such as 1.14. For a list of available - TensorFlow versions please see https://www.tensorflow.org/versions/. - -OPTIONAL FLAGS - --accelerator-type=ACCELERATOR_TYPE; default="v2-8" - TPU accelerator type for the TPU. If not specified, this defaults to - v2-8. - - For a list of available accelerator types run: - - gcloud alpha compute tpus accelerator-types list - - --async - Return immediately, without waiting for the operation in progress to - complete. - - --description=DESCRIPTION - Specifies a text description of the TPU. - - --network=NETWORK; default="default" - Specifies the network that this TPU will be a part of. - - --preemptible - If provided, the TPU will be preemptible and time-limited. It may be - preempted to free up resources for standard TPUs, and will only be able - to run for a limited amount of time. - - Preemptible TPUs cannot be restarted. - - --range=RANGE - CIDR Range for the TPU. - - The IP range that the TPU will select an IP address from. Must be in - CIDR notation and a /29 range, for example 192.168.0.0/29. Errors will - occur if the CIDR range has already been used for a currently existing - TPU, the CIDR range conflicts with any networks in the user's provided - network, or the provided network is peered with another network that is - using that CIDR range. - - --reserved - When specified, will attempt to create the TPU node under reservations - made in the current project. The reservations can be made separately - but used in aggregated form. i.e., the user can make a reservation of - 128 V2 TPUs and later on make another reservation of 128 V2 TPUs then - creates a v2-256 TPU instance. If there exists no reservation or not - sufficient amount of reserved cores under the project, the request will - fail due to lack of capacity. - - --use-service-networking - If provided, the TPU will be configured via the Service Networking (SN) - API instead of using a CIDR range. The Service Networking API should be - enabled on the project before creating the TPU. - - For more information on Service Networking see - https://cloud.google.com/service-infrastructure/docs/service-networking/getting-started. - - At most one of these can be specified: - - --model-base-path=MODEL_BASE_PATH - Base path to exported saved model. This flag can be used instead of - '--model-config-file' directly to specify the exported saved model's - base path (excluding timestamp), whereas '--model-config-file' points - to a Google Cloud Storage path to a ModelServerConfig proto. - - --model-name=MODEL_NAME - Model name for tensorflow serving to serve to incoming requests. If - not provided, 'serving_default' will be used. - - --model-config-file=MODEL_CONFIG_FILE - Google Cloud Storage URI of the configuration file for models to - serve. For example: 'gs://my_bucket/path/to/config.pbtxt'. - - The contents of the model configuration file should look something - like the following: - - model_config_list: { config: { name: "Model1", base_path: - "gs://my_bucket/path/to/model1", model_platform: "tensorflow" }, - config: { name: "Model2", base_path: - "gs://my_other_bucket/path/to/model2", model_platform: "tensorflow" - }, } - - --platform-config-file=PLATFORM_CONFIG_FILE - Google Cloud Storage URI of configuration file for platform - requirements. For example: 'gs://my_bucket/path/to/platform.pbtxt'. - - The contents of the platform configuration file should look something - like the following: - - platform_configs { key: "tensorflow" value { source_adapter_config { - [type.googleapis.com/tensorflow.serving.SavedModelBundleSourceAdapterConfig] - { legacy_config { saved_model_tags: "tpu" saved_model_tags: "serve" - batching_parameters { max_batch_size { value: 8 } - batch_timeout_micros { value: 50000 } max_enqueued_batches { value: - 10000 } num_batch_threads { value: 8 } } } } } } } - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --configuration, --flags-file, --flatten, --format, - --help, --impersonate-service-account, --log-http, --project, --quiet, - --trace-token, --user-output-enabled, --verbosity. - - Run $ gcloud help for details. - -API REFERENCE - This command uses the tpu/v1alpha1 API. The full documentation for this API - can be found at: https://cloud.google.com/tpu/ - -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 tpus create - - $ gcloud beta compute tpus create - diff --git a/gcloud/alpha/compute/tpus/delete b/gcloud/alpha/compute/tpus/delete deleted file mode 100644 index 537cf9a87..000000000 --- a/gcloud/alpha/compute/tpus/delete +++ /dev/null @@ -1,79 +0,0 @@ -NAME - gcloud alpha compute tpus delete - deletes a Cloud TPU - -SYNOPSIS - gcloud alpha compute tpus delete (TPU : --zone=ZONE) [--async] - [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (ALPHA) (DEPRECATED) This command is being deprecated. Please use gcloud - compute tpus tpu-vm delete instead. - - Deletes a Cloud TPU. - -EXAMPLES - The following command deletes a TPU with ID my-tpu in zone us-central1-b: - - $ gcloud alpha compute tpus delete my-tpu --zone=us-central1-b - -POSITIONAL ARGUMENTS - Tpu resource - The Cloud TPU you want to delete. The arguments in this - group can be used to specify the attributes of this resource. (NOTE) Some - attributes are not given arguments in this group but can be set in other - ways. - - To set the project attribute: - ◆ provide the argument tpu on the command line with a fully specified - name; - ◆ provide the argument --project on the command line; - ◆ set the property core/project. - - This must be specified. - - TPU - ID of the tpu or fully qualified identifier for the tpu. - - To set the tpu attribute: - ▸ provide the argument tpu on the command line. - - This positional argument must be specified if any of the other - arguments in this group are specified. - - --zone=ZONE - The compute/zone of the Cloud TPU. - - If not specified, will use default compute/zone. - - To set the zone attribute: - ▸ provide the argument tpu on the command line with a fully - specified name; - ▸ provide the argument --zone on the command line; - ▸ set the property compute/zone. - -FLAGS - --async - Return immediately, without waiting for the operation in progress to - complete. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --configuration, --flags-file, --flatten, --format, - --help, --impersonate-service-account, --log-http, --project, --quiet, - --trace-token, --user-output-enabled, --verbosity. - - Run $ gcloud help for details. - -API REFERENCE - This command uses the tpu/v1 API. The full documentation for this API can - be found at: https://cloud.google.com/tpu/ - -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 tpus delete - - $ gcloud beta compute tpus delete - diff --git a/gcloud/alpha/compute/tpus/describe b/gcloud/alpha/compute/tpus/describe deleted file mode 100644 index 2e1647303..000000000 --- a/gcloud/alpha/compute/tpus/describe +++ /dev/null @@ -1,74 +0,0 @@ -NAME - gcloud alpha compute tpus describe - describe a Cloud TPU - -SYNOPSIS - gcloud alpha compute tpus describe (TPU : --zone=ZONE) - [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (ALPHA) (DEPRECATED) This command is being deprecated. Please use gcloud - compute tpus tpu-vm describe instead. - - Describe a Cloud TPU. - -EXAMPLES - The following command describes a TPU with ID my-tpu in zone us-central1-b: - - $ gcloud alpha compute tpus describe my-tpu --zone=us-central1-b - -POSITIONAL ARGUMENTS - Tpu resource - The Cloud TPU you want to describe. The arguments in this - group can be used to specify the attributes of this resource. (NOTE) Some - attributes are not given arguments in this group but can be set in other - ways. - - To set the project attribute: - ◆ provide the argument tpu on the command line with a fully specified - name; - ◆ provide the argument --project on the command line; - ◆ set the property core/project. - - This must be specified. - - TPU - ID of the tpu or fully qualified identifier for the tpu. - - To set the tpu attribute: - ▸ provide the argument tpu on the command line. - - This positional argument must be specified if any of the other - arguments in this group are specified. - - --zone=ZONE - The compute/zone of the Cloud TPU. - - If not specified, will use default compute/zone. - - To set the zone attribute: - ▸ provide the argument tpu on the command line with a fully - specified name; - ▸ provide the argument --zone on the command line; - ▸ set the property compute/zone. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --configuration, --flags-file, --flatten, --format, - --help, --impersonate-service-account, --log-http, --project, --quiet, - --trace-token, --user-output-enabled, --verbosity. - - Run $ gcloud help for details. - -API REFERENCE - This command uses the tpu/v1 API. The full documentation for this API can - be found at: https://cloud.google.com/tpu/ - -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 tpus describe - - $ gcloud beta compute tpus describe - diff --git a/gcloud/alpha/compute/tpus/execution-groups/create b/gcloud/alpha/compute/tpus/execution-groups/create deleted file mode 100644 index 3cc921c72..000000000 --- a/gcloud/alpha/compute/tpus/execution-groups/create +++ /dev/null @@ -1,165 +0,0 @@ -NAME - gcloud alpha compute tpus execution-groups create - create Google Compute - TPUs along with VMs - -SYNOPSIS - gcloud alpha compute tpus execution-groups create - [--accelerator-type=ACCELERATOR_TYPE; default="v2-8"] - [--disk-size=DISK_SIZE; default="250GB"] [--dry-run] [--forward-ports] - [--gce-image=GCE_IMAGE] - [--machine-type=MACHINE_TYPE; default="n1-standard-1"] [--name=NAME] - [--network=NETWORK; default="default"] [--preemptible] - [--preemptible-vm] [--tf-version=TF_VERSION] [--tpu-only] - [--use-dl-images] [--use-with-notebook] [--vm-only] [--zone=ZONE] - [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (ALPHA) (DEPRECATED) Create Google Compute TPUs along with VMs. - - This command is deprecated and will be removed in a future release. We - recommend that you use the TPU-VM or Queued Resource API. See - https://cloud.google.com/tpu/docs/managing-tpus-tpu-vm for more - information. - -EXAMPLES - To create both TPU and VM, run: - - $ gcloud alpha compute tpus execution-groups create \ - --name=test-execution-group --zone=test-zone \ - --project=test-project --accelerator-type=v2-8 \ - --tf-version=2.4.1 - - To create both TPU and VM with additional flags, run: - - $ gcloud alpha compute tpus execution-groups create \ - --name=test-execution-group --zone=test-zone \ - --project=test-project --accelerator-type=v2-8 \ - --tf-version=2.4.1 --network=default --preemptible-vm \ - --disk-size=100 --machine-type=n1-standard-2 --use-dl-images - - To create a VM only before creating the TPU, run: - - $ gcloud alpha compute tpus execution-groups create \ - --name=test-execution-group-tpu-only --zone=test-zone \ - --project=test-project --accelerator-type=v2-8 \ - --tf-version=2.4.1 --tpu-only - - To create the TPU only after the VM has been created, run: - - $ gcloud alpha compute tpus execution-groups create \ - --name=test-execution-group-tpu-only --zone=test-zone \ - --project=test-project --accelerator-type=v2-8 \ - --tf-version=2.4.1 --vm-only - -FLAGS - --accelerator-type=ACCELERATOR_TYPE; default="v2-8" - TPU accelerator type for the TPU. If not specified, this defaults to - v2-8. - - --disk-size=DISK_SIZE; default="250GB" - Configures the root volume size of your Compute Engine VM (in GB). The - minimum size is 20GB and the maximum is 2000GB. Specified value must be - an integer multiple of Gigabytes. - - --dry-run - Do not make changes; print only what would have happened. - - --forward-ports - Automatically forward useful ports from the Compute Engine VM to your - local machine. The ports forwarded are: 6006 (tensorboard), 8888 - (jupyter notebooks), 8470 (TPU port), 8466 (TPU profiler port). - - Enabled by default, use --no-forward-ports to disable. - - --gce-image=GCE_IMAGE - Override the automatically chosen Compute Engine Image. Use this flag - when you're using your own custom images instead of the provided ones - with TensorFlow pre-installed. - - --machine-type=MACHINE_TYPE; default="n1-standard-1" - Specifies the machine type used for the Compute Engine VM. To get a - list of available machine types, run 'gcloud compute machine-types - list'. If unspecified, the default type is n1-standard-1. - - --name=NAME - Override the name to use for VMs and TPUs (defaults to your username). - - --network=NETWORK; default="default" - Specifies the network the Cloud TPU and associated VM should be created - in. If unspecified, the network "default" is picked. - - --preemptible - Create a preemptible Cloud TPU, instead of a normal (non-preemptible) - Cloud TPU. A preemptible Cloud TPU costs less per hour, but the Cloud - TPU service can stop/terminate the node at any time. - - --preemptible-vm - Create a preemptible Compute Engine VM, instead of a normal - (non-preemptible) VM. A preemptible VM costs less per hour, but the - Compute Engine service can terminate the instance at any time. - - --tf-version=TF_VERSION - Set the version of TensorFlow to use when creating the Compute Engine - VM and the Cloud TPU. (It defaults to auto-selecting the latest stable - release.) - - --tpu-only - Do not allocate a VM, only allocate a TPU. To be used after the command - has been run with a --vm-only flag and the user is ready to run on a - TPU. Ensure that the name matches the name passed in when creating with - the --vm-only flag. - - --use-dl-images - Use Deep Learning VM Images (see docs - - https://cloud.google.com/deep-learning-vm/) instead of TPU-specific - machine images. Defaults to TPU-specific images. This value is set to - true automatically if the --use-with-notebook flag is set to true. - - --use-with-notebook - Allow Compute Engine VM to be recognized by Cloud AI Notebooks. This - automatically sets the content of the flag --use-dl-images flag to be - true. - - --vm-only - Do not allocate a TPU, only allocate a VM (useful if you're not ready - to run on a TPU yet). - - --zone=ZONE - Zone of the tpu to create. If not specified and the compute/zone - property isn't set, you might be prompted to select a zone (interactive - mode only). - - To avoid prompting when this flag is omitted, you can set the - compute/zone property: - - $ gcloud config set compute/zone ZONE - - A list of zones can be fetched by running: - - $ gcloud compute zones list - - To unset the property, run: - - $ gcloud config unset compute/zone - - Alternatively, the zone can be stored in the environment variable - CLOUDSDK_COMPUTE_ZONE. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --configuration, --flags-file, --flatten, --format, - --help, --impersonate-service-account, --log-http, --project, --quiet, - --trace-token, --user-output-enabled, --verbosity. - - Run $ gcloud help for details. - -NOTES - This command is currently in alpha and might change without notice. If this - command fails with API permission errors despite specifying the correct - project, you might be trying to access an API with an invitation-only early - access allowlist. These variants are also available: - - $ gcloud compute tpus execution-groups create - - $ gcloud beta compute tpus execution-groups create - diff --git a/gcloud/alpha/compute/tpus/execution-groups/delete b/gcloud/alpha/compute/tpus/execution-groups/delete deleted file mode 100644 index 864e238f3..000000000 --- a/gcloud/alpha/compute/tpus/execution-groups/delete +++ /dev/null @@ -1,75 +0,0 @@ -NAME - gcloud alpha compute tpus execution-groups delete - delete TPU Node + VM - created by execution group - -SYNOPSIS - gcloud alpha compute tpus execution-groups delete EXECUTION_GROUP_NAME - [--tpu-only] [--zone=ZONE] [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (ALPHA) (DEPRECATED) Delete TPU Node + VM created by execution group. - - This command is deprecated and will be removed in a future release. We - recommend that you use the TPU-VM or Queued Resource API. See - https://cloud.google.com/tpu/docs/managing-tpus-tpu-vm for more - information. - -EXAMPLES - To delete both, the TPU and the VM, run: - - $ gcloud alpha compute tpus execution-groups delete \ - test-execution-group --zone=test-zone --project=test-project - - To delete the TPU only, run: - - $ gcloud alpha compute tpus execution-groups delete \ - test-execution-group --zone=test-zone --project=test-project \ - --tpu-only - -POSITIONAL ARGUMENTS - EXECUTION_GROUP_NAME - The execution group name to delete. - -FLAGS - --tpu-only - Do not delete VM, only delete the TPU. - - --zone=ZONE - Zone of the tpu to delete. If not specified and the compute/zone - property isn't set, you might be prompted to select a zone (interactive - mode only). - - To avoid prompting when this flag is omitted, you can set the - compute/zone property: - - $ gcloud config set compute/zone ZONE - - A list of zones can be fetched by running: - - $ gcloud compute zones list - - To unset the property, run: - - $ gcloud config unset compute/zone - - Alternatively, the zone can be stored in the environment variable - CLOUDSDK_COMPUTE_ZONE. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --configuration, --flags-file, --flatten, --format, - --help, --impersonate-service-account, --log-http, --project, --quiet, - --trace-token, --user-output-enabled, --verbosity. - - Run $ gcloud help for details. - -NOTES - This command is currently in alpha and might change without notice. If this - command fails with API permission errors despite specifying the correct - project, you might be trying to access an API with an invitation-only early - access allowlist. These variants are also available: - - $ gcloud compute tpus execution-groups delete - - $ gcloud beta compute tpus execution-groups delete - diff --git a/gcloud/alpha/compute/tpus/execution-groups/describe b/gcloud/alpha/compute/tpus/execution-groups/describe deleted file mode 100644 index 16107334f..000000000 --- a/gcloud/alpha/compute/tpus/execution-groups/describe +++ /dev/null @@ -1,66 +0,0 @@ -NAME - gcloud alpha compute tpus execution-groups describe - describe Google - Compute TPU + VM combination - -SYNOPSIS - gcloud alpha compute tpus execution-groups describe EXECUTION_GROUP_NAME - [--zone=ZONE] [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (ALPHA) (DEPRECATED) Describe Google Compute TPU + VM combination. - - This command is deprecated and will be removed in a future release. We - recommend that you use the TPU-VM or Queued Resource API. See - https://cloud.google.com/tpu/docs/managing-tpus-tpu-vm for more - information. - -EXAMPLES - To describe the TPU and VM combination, run: - - $ gcloud alpha compute tpus execution-groups describe \ - test-execution-group --zone=test-zone --project=test-project - -POSITIONAL ARGUMENTS - EXECUTION_GROUP_NAME - The execution group name to delete. - -FLAGS - --zone=ZONE - Zone of the tpu to describe. If not specified and the compute/zone - property isn't set, you might be prompted to select a zone (interactive - mode only). - - To avoid prompting when this flag is omitted, you can set the - compute/zone property: - - $ gcloud config set compute/zone ZONE - - A list of zones can be fetched by running: - - $ gcloud compute zones list - - To unset the property, run: - - $ gcloud config unset compute/zone - - Alternatively, the zone can be stored in the environment variable - CLOUDSDK_COMPUTE_ZONE. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --configuration, --flags-file, --flatten, --format, - --help, --impersonate-service-account, --log-http, --project, --quiet, - --trace-token, --user-output-enabled, --verbosity. - - Run $ gcloud help for details. - -NOTES - This command is currently in alpha and might change without notice. If this - command fails with API permission errors despite specifying the correct - project, you might be trying to access an API with an invitation-only early - access allowlist. These variants are also available: - - $ gcloud compute tpus execution-groups describe - - $ gcloud beta compute tpus execution-groups describe - diff --git a/gcloud/alpha/compute/tpus/execution-groups/help b/gcloud/alpha/compute/tpus/execution-groups/help deleted file mode 100644 index 45cf25d1f..000000000 --- a/gcloud/alpha/compute/tpus/execution-groups/help +++ /dev/null @@ -1,53 +0,0 @@ -NAME - gcloud alpha compute tpus execution-groups - command group that helps - create and manage Cloud TPUs and Compute VMs - -SYNOPSIS - gcloud alpha compute tpus execution-groups COMMAND [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (ALPHA) (DEPRECATED) Command group that helps create and manage Cloud TPUs - and Compute VMs. - - This command group is deprecated and will be removed in a future release. - We recommend that you use the TPU-VM or Queued Resource API. See - https://cloud.google.com/tpu/docs/managing-tpus-tpu-vm for more - information. - -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) (DEPRECATED) Create Google Compute TPUs along with VMs. - - delete - (ALPHA) (DEPRECATED) Delete TPU Node + VM created by execution group. - - describe - (ALPHA) (DEPRECATED) Describe Google Compute TPU + VM combination. - - list - (ALPHA) (DEPRECATED) List TPU Node+VM groups created by execution - group. - - resume - (ALPHA) (DEPRECATED) Creates Google Compute TPU and resumes the VM. - - suspend - (ALPHA) (DEPRECATED) Deletes Google Compute TPU and suspends the VM. - -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 tpus execution-groups - - $ gcloud beta compute tpus execution-groups - diff --git a/gcloud/alpha/compute/tpus/execution-groups/resume b/gcloud/alpha/compute/tpus/execution-groups/resume deleted file mode 100644 index 34c31acb5..000000000 --- a/gcloud/alpha/compute/tpus/execution-groups/resume +++ /dev/null @@ -1,91 +0,0 @@ -NAME - gcloud alpha compute tpus execution-groups resume - creates Google Compute - TPU and resumes the VM - -SYNOPSIS - gcloud alpha compute tpus execution-groups resume EXECUTION_GROUP_NAME - [--accelerator-type=ACCELERATOR_TYPE; default="v2-8"] - [--network=NETWORK; default="default"] [--preemptible] - [--tf-version=TF_VERSION] [--vm-only] [--zone=ZONE] - [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (ALPHA) (DEPRECATED) Creates Google Compute TPU and resumes the VM. - - This command is deprecated and will be removed in a future release. We - recommend that you use the TPU-VM or Queued Resource API. See - https://cloud.google.com/tpu/docs/managing-tpus-tpu-vm for more - information. - -EXAMPLES - To resume a suspended TPU VM combination, run: - - $ gcloud alpha compute tpus execution-groups resume \ - test-execution-group --zone=test-zone --project=test-project \ - --accelerator-type=v2-8 --tf-version=2.4.1 - -POSITIONAL ARGUMENTS - EXECUTION_GROUP_NAME - The execution group name to delete. - -FLAGS - --accelerator-type=ACCELERATOR_TYPE; default="v2-8" - TPU accelerator type for the TPU. If not specified, this defaults to - v2-8. - - --network=NETWORK; default="default" - Set to the network that was originally used creating the suspended - Cloud TPU and Compute Engine VM. (It defaults to using the 'default' - network.) - - --preemptible - Create a preemptible Cloud TPU, instead of a normal (non-preemptible) - Cloud TPU. A preemptible Cloud TPU costs less per hour, but the Cloud - TPU service can stop/terminate the node at any time. - - --tf-version=TF_VERSION - Set the version of TensorFlow to the version originally set when - creating the suspended Cloud TPU and Compute Engine VM . (It defaults - to auto-selecting the latest stable release.) - - --vm-only - Do not allocate a TPU, only allocate a VM (useful if you're not ready - to run on a TPU yet). - - --zone=ZONE - Zone of the tpu to resume. If not specified and the compute/zone - property isn't set, you might be prompted to select a zone (interactive - mode only). - - To avoid prompting when this flag is omitted, you 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 tpus execution-groups resume - diff --git a/gcloud/alpha/compute/tpus/execution-groups/suspend b/gcloud/alpha/compute/tpus/execution-groups/suspend deleted file mode 100644 index f28d4bb80..000000000 --- a/gcloud/alpha/compute/tpus/execution-groups/suspend +++ /dev/null @@ -1,64 +0,0 @@ -NAME - gcloud alpha compute tpus execution-groups suspend - deletes Google Compute - TPU and suspends the VM - -SYNOPSIS - gcloud alpha compute tpus execution-groups suspend EXECUTION_GROUP_NAME - [--zone=ZONE] [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (ALPHA) (DEPRECATED) Deletes Google Compute TPU and suspends the VM. - - This command is deprecated and will be removed in a future release. We - recommend that you use the TPU-VM or Queued Resource API. See - https://cloud.google.com/tpu/docs/managing-tpus-tpu-vm for more - information. - -EXAMPLES - To delete the TPU and suspend the VM, run: - - $ gcloud alpha compute tpus execution-groups suspend \ - test-execution-group --zone=test-zone --project=test-project - -POSITIONAL ARGUMENTS - EXECUTION_GROUP_NAME - The execution group name to delete. - -FLAGS - --zone=ZONE - Zone of the tpu to suspend. If not specified and the compute/zone - property isn't set, you might be prompted to select a zone (interactive - mode only). - - To avoid prompting when this flag is omitted, you 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 tpus execution-groups suspend - diff --git a/gcloud/alpha/compute/tpus/help b/gcloud/alpha/compute/tpus/help index 06f608831..e747bb519 100644 --- a/gcloud/alpha/compute/tpus/help +++ b/gcloud/alpha/compute/tpus/help @@ -24,10 +24,6 @@ GROUPS accelerator-types (ALPHA) List or Describe Available Cloud TPU accelerator types. - execution-groups - (ALPHA) (DEPRECATED) Command group that helps create and manage Cloud - TPUs and Compute VMs. - locations (ALPHA) List or Describe Available Cloud TPU Locations. @@ -46,30 +42,6 @@ GROUPS versions (ALPHA) Explore Available Tensorflow versions for Cloud TPUs. -COMMANDS - COMMAND is one of the following: - - create - (ALPHA) (DEPRECATED) Create a new Cloud TPU. - - delete - (ALPHA) (DEPRECATED) Deletes a Cloud TPU. - - describe - (ALPHA) (DEPRECATED) Describe a Cloud TPU. - - list - (ALPHA) (DEPRECATED) List Cloud TPUs. - - reimage - (ALPHA) (DEPRECATED) Reimages the OS on a Cloud TPU. - - start - (ALPHA) (DEPRECATED) Start a Cloud TPU. - - stop - (ALPHA) (DEPRECATED) Stop a Cloud TPU. - NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct diff --git a/gcloud/alpha/compute/tpus/reimage b/gcloud/alpha/compute/tpus/reimage deleted file mode 100644 index c9c9537d0..000000000 --- a/gcloud/alpha/compute/tpus/reimage +++ /dev/null @@ -1,86 +0,0 @@ -NAME - gcloud alpha compute tpus reimage - reimages the OS on a Cloud TPU - -SYNOPSIS - gcloud alpha compute tpus reimage (TPU : --zone=ZONE) --version=VERSION - [--async] [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (ALPHA) (DEPRECATED) This command is being deprecated. Please use gcloud - compute tpus tpu-vm reimage instead. - - Reimages the OS on a Cloud TPU. - -EXAMPLES - The following command reimages a TPU with ID my-tpu in zone us-central1-b - with TensorFlow version 1.15: - - $ gcloud alpha compute tpus reimage my-tpu --zone=us-central1-b \ - --version=1.15 - -POSITIONAL ARGUMENTS - Tpu resource - The Cloud TPU you want to reimage. The arguments in this - group can be used to specify the attributes of this resource. (NOTE) Some - attributes are not given arguments in this group but can be set in other - ways. - - To set the project attribute: - ◆ provide the argument tpu on the command line with a fully specified - name; - ◆ provide the argument --project on the command line; - ◆ set the property core/project. - - This must be specified. - - TPU - ID of the tpu or fully qualified identifier for the tpu. - - To set the tpu attribute: - ▸ provide the argument tpu on the command line. - - This positional argument must be specified if any of the other - arguments in this group are specified. - - --zone=ZONE - The compute/zone of the Cloud TPU. - - If not specified, will use default compute/zone. - - To set the zone attribute: - ▸ provide the argument tpu on the command line with a fully - specified name; - ▸ provide the argument --zone on the command line; - ▸ set the property compute/zone. - -REQUIRED FLAGS - --version=VERSION - TensorFlow version for the TPU, such as 1.6. For a list of available - TensorFlow versions please see https://www.tensorflow.org/versions/. - -OPTIONAL FLAGS - --async - Return immediately, without waiting for the operation in progress to - complete. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --configuration, --flags-file, --flatten, --format, - --help, --impersonate-service-account, --log-http, --project, --quiet, - --trace-token, --user-output-enabled, --verbosity. - - Run $ gcloud help for details. - -API REFERENCE - This command uses the tpu/v1 API. The full documentation for this API can - be found at: https://cloud.google.com/tpu/ - -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 tpus reimage - - $ gcloud beta compute tpus reimage - diff --git a/gcloud/alpha/compute/tpus/start b/gcloud/alpha/compute/tpus/start deleted file mode 100644 index 6449a30bd..000000000 --- a/gcloud/alpha/compute/tpus/start +++ /dev/null @@ -1,78 +0,0 @@ -NAME - gcloud alpha compute tpus start - start a Cloud TPU - -SYNOPSIS - gcloud alpha compute tpus start (TPU : --zone=ZONE) [--async] - [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (ALPHA) (DEPRECATED) This command is being deprecated. Please use gcloud - compute tpus tpu-vm start instead. - - Start a Cloud TPU. - -EXAMPLES - The following command starts a TPU with ID my-tpu in zone us-central1-b: - - $ gcloud alpha compute tpus start my-tpu --zone=us-central1-b - -POSITIONAL ARGUMENTS - Tpu resource - The Cloud TPU to start. The arguments in this group can be - used to specify the attributes of this resource. (NOTE) Some attributes - are not given arguments in this group but can be set in other ways. - - To set the project attribute: - ◆ provide the argument tpu on the command line with a fully specified - name; - ◆ provide the argument --project on the command line; - ◆ set the property core/project. - - This must be specified. - - TPU - ID of the tpu or fully qualified identifier for the tpu. - - To set the tpu attribute: - ▸ provide the argument tpu on the command line. - - This positional argument must be specified if any of the other - arguments in this group are specified. - - --zone=ZONE - The compute/zone of the Cloud TPU. - - If not specified, will use default compute/zone. - - To set the zone attribute: - ▸ provide the argument tpu on the command line with a fully - specified name; - ▸ provide the argument --zone on the command line; - ▸ set the property compute/zone. - -FLAGS - --async - Return immediately, without waiting for the operation in progress to - complete. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --configuration, --flags-file, --flatten, --format, - --help, --impersonate-service-account, --log-http, --project, --quiet, - --trace-token, --user-output-enabled, --verbosity. - - Run $ gcloud help for details. - -API REFERENCE - This command uses the tpu/v1 API. The full documentation for this API can - be found at: https://cloud.google.com/tpu/ - -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 tpus start - - $ gcloud beta compute tpus start - diff --git a/gcloud/alpha/compute/tpus/stop b/gcloud/alpha/compute/tpus/stop deleted file mode 100644 index 58131d0a3..000000000 --- a/gcloud/alpha/compute/tpus/stop +++ /dev/null @@ -1,78 +0,0 @@ -NAME - gcloud alpha compute tpus stop - stop a Cloud TPU - -SYNOPSIS - gcloud alpha compute tpus stop (TPU : --zone=ZONE) [--async] - [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (ALPHA) (DEPRECATED) This command is being deprecated. Please use gcloud - compute tpus tpu-vm stop instead. - - Stop a Cloud TPU. - -EXAMPLES - The following command stops a TPU with ID my-tpu in zone us-central1-b: - - $ gcloud alpha compute tpus stop my-tpu --zone=us-central1-b - -POSITIONAL ARGUMENTS - Tpu resource - The Cloud TPU to stop. The arguments in this group can be - used to specify the attributes of this resource. (NOTE) Some attributes - are not given arguments in this group but can be set in other ways. - - To set the project attribute: - ◆ provide the argument tpu on the command line with a fully specified - name; - ◆ provide the argument --project on the command line; - ◆ set the property core/project. - - This must be specified. - - TPU - ID of the tpu or fully qualified identifier for the tpu. - - To set the tpu attribute: - ▸ provide the argument tpu on the command line. - - This positional argument must be specified if any of the other - arguments in this group are specified. - - --zone=ZONE - The compute/zone of the Cloud TPU. - - If not specified, will use default compute/zone. - - To set the zone attribute: - ▸ provide the argument tpu on the command line with a fully - specified name; - ▸ provide the argument --zone on the command line; - ▸ set the property compute/zone. - -FLAGS - --async - Return immediately, without waiting for the operation in progress to - complete. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --configuration, --flags-file, --flatten, --format, - --help, --impersonate-service-account, --log-http, --project, --quiet, - --trace-token, --user-output-enabled, --verbosity. - - Run $ gcloud help for details. - -API REFERENCE - This command uses the tpu/v1 API. The full documentation for this API can - be found at: https://cloud.google.com/tpu/ - -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 tpus stop - - $ gcloud beta compute tpus stop - diff --git a/gcloud/alpha/compute/zone-vm-extension-policies/create b/gcloud/alpha/compute/zone-vm-extension-policies/create index 79a3bd487..60072845a 100644 --- a/gcloud/alpha/compute/zone-vm-extension-policies/create +++ b/gcloud/alpha/compute/zone-vm-extension-policies/create @@ -41,7 +41,10 @@ OPTIONAL FLAGS extension name must be one of the extensions specified in the --extensions flag. - E.g. --config=filestore=,ops-agent= + E.g. --config=filestore='filestore config',ops-agent='ops agent config' + + Raises: ArgumentTypeError: If the extension name is not specified in + the --extensions flag. --config-from-file=KEY=FILE_PATH,[...] Same as --config except that the value for the entry will be read from @@ -90,6 +93,9 @@ OPTIONAL FLAGS E.g. --version=filestore=123ABC,ops-agent=456DEF + Raises: ArgumentTypeError: If the extension name is not specified in + the --extensions flag. + --zone=ZONE Zone of the zone vm extension policy to create. If not specified and the compute/zone property isn't set, you might be prompted to select a diff --git a/gcloud/alpha/compute/zone-vm-extension-policies/update b/gcloud/alpha/compute/zone-vm-extension-policies/update index 7eb2d71de..f51585e94 100644 --- a/gcloud/alpha/compute/zone-vm-extension-policies/update +++ b/gcloud/alpha/compute/zone-vm-extension-policies/update @@ -41,7 +41,10 @@ OPTIONAL FLAGS extension name must be one of the extensions specified in the --extensions flag. - E.g. --config=filestore=,ops-agent= + E.g. --config=filestore='filestore config',ops-agent='ops agent config' + + Raises: ArgumentTypeError: If the extension name is not specified in + the --extensions flag. --config-from-file=KEY=FILE_PATH,[...] Same as --config except that the value for the entry will be read from @@ -90,6 +93,9 @@ OPTIONAL FLAGS E.g. --version=filestore=123ABC,ops-agent=456DEF + Raises: ArgumentTypeError: If the extension name is not specified in + the --extensions flag. + --zone=ZONE Zone of the zone vm extension policy to update. If not specified and the compute/zone property isn't set, you might be prompted to select a diff --git a/gcloud/alpha/container/clusters/create b/gcloud/alpha/container/clusters/create index b1ee2fbf3..450929ef9 100644 --- a/gcloud/alpha/container/clusters/create +++ b/gcloud/alpha/container/clusters/create @@ -43,7 +43,8 @@ SYNOPSIS [--enable-identity-service] [--enable-image-streaming] [--enable-insecure-kubelet-readonly-port] [--enable-intra-node-visibility] [--enable-ip-access] - [--enable-ip-alias] [--enable-kubernetes-alpha] + [--enable-ip-alias] [--enable-k8s-certs-via-dns] + [--enable-k8s-tokens-via-dns] [--enable-kubernetes-alpha] [--enable-kubernetes-unstable-apis=API,[API,...]] [--enable-l4-ilb-subsetting] [--enable-legacy-authorization] [--enable-legacy-lustre-port] [--enable-logging-monitoring-system-only] @@ -687,6 +688,14 @@ FLAGS you omit both --enable-ip-alias and --no-enable-ip-alias, the default is a VPC-native cluster. + --enable-k8s-certs-via-dns + Enable K8s client certificates Authentication to the cluster's control + plane over DNS-based endpoint. + + --enable-k8s-tokens-via-dns + Enable K8s Service Account tokens Authentication to the cluster's + control plane over DNS-based endpoint. + --enable-kubernetes-alpha Enable Kubernetes alpha features on this cluster. Selecting this option will result in the cluster having all Kubernetes alpha API groups and diff --git a/gcloud/alpha/container/clusters/create-auto b/gcloud/alpha/container/clusters/create-auto index d2e80a673..2cb3ac1f7 100644 --- a/gcloud/alpha/container/clusters/create-auto +++ b/gcloud/alpha/container/clusters/create-auto @@ -21,7 +21,9 @@ SYNOPSIS [--enable-backup-restore] [--enable-cilium-clusterwide-network-policy] [--enable-confidential-nodes] [--enable-default-compute-class] [--enable-dns-access] [--enable-fleet] [--enable-google-cloud-access] - [--enable-ip-access] [--enable-kubernetes-unstable-apis=API,[API,...]] + [--enable-ip-access] [--enable-k8s-certs-via-dns] + [--enable-k8s-tokens-via-dns] + [--enable-kubernetes-unstable-apis=API,[API,...]] [--enable-legacy-lustre-port] [--enable-lustre-csi-driver] [--enable-master-global-access] [--enable-multi-networking] [--enable-ray-cluster-logging] [--enable-ray-cluster-monitoring] @@ -309,6 +311,14 @@ FLAGS Enable access to the cluster's control plane over private IP and public IP if --enable-private-endpoint is not enabled. + --enable-k8s-certs-via-dns + Enable K8s client certificates Authentication to the cluster's control + plane over DNS-based endpoint. + + --enable-k8s-tokens-via-dns + Enable K8s Service Account tokens Authentication to the cluster's + control plane over DNS-based endpoint. + --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/alpha/container/clusters/update b/gcloud/alpha/container/clusters/update index 8d711c498..f0b0ebb91 100644 --- a/gcloud/alpha/container/clusters/update +++ b/gcloud/alpha/container/clusters/update @@ -93,6 +93,7 @@ SYNOPSIS | --enable-l4-lb-firewall-reconciliation | --enable-authorized-networks-on-private-endpoint --enable-dns-access --enable-google-cloud-access --enable-ip-access + --enable-k8s-certs-via-dns --enable-k8s-tokens-via-dns --enable-master-global-access --enable-private-endpoint --enable-master-authorized-networks --master-authorized-networks=NETWORK,[NETWORK,...] @@ -1329,6 +1330,14 @@ REQUIRED FLAGS Enable access to the cluster's control plane over private IP and public IP if --enable-private-endpoint is not enabled. + --enable-k8s-certs-via-dns + Enable K8s client certificates Authentication to the cluster's + control plane over DNS-based endpoint. + + --enable-k8s-tokens-via-dns + Enable K8s Service Account tokens Authentication to the cluster's + control plane over DNS-based endpoint. + --enable-master-global-access Use with private clusters to allow access to the master's private endpoint from any Google Cloud region or on-premises environment diff --git a/gcloud/alpha/container/node-pools/create b/gcloud/alpha/container/node-pools/create index b15c2937e..317645517 100644 --- a/gcloud/alpha/container/node-pools/create +++ b/gcloud/alpha/container/node-pools/create @@ -15,6 +15,7 @@ SYNOPSIS [--additional-pod-network=[subnetwork=SUBNETWORK_NAME, pod-ipv4-range=SECONDARY_RANGE_NAME, [max-pods-per-node=NUM_PODS],...]] [--async] + [--autoscaled-rollout-policy=[wait-for-drain-duration=WAIT-FOR-DRAIN-DURATION]] [--boot-disk-kms-key=BOOT_DISK_KMS_KEY] [--boot-disk-provisioned-iops=BOOT_DISK_PROVISIONED_IOPS] [--boot-disk-provisioned-throughput=BOOT_DISK_PROVISIONED_THROUGHPUT] @@ -197,6 +198,23 @@ FLAGS Return immediately, without waiting for the operation in progress to complete. + --autoscaled-rollout-policy=[wait-for-drain-duration=WAIT-FOR-DRAIN-DURATION] + Autoscaled rollout policy options for blue-green upgrade. + + wait-for-drain-duration + (Optional) Time in seconds to wait after cordoning the blue pool + before draining the nodes. + + Examples: + + $ gcloud alpha container node-pools create node-pool-1 \ + --cluster=example-cluster --enable-blue-green-upgrade \ + --autoscaled-rollout-policy="" + + $ gcloud alpha container node-pools create node-pool-1 \ + --cluster=example-cluster --enable-blue-green-upgrade \ + --autoscaled-rollout-policy=wait-for-drain-duration=7200s + --boot-disk-kms-key=BOOT_DISK_KMS_KEY The Customer Managed Encryption Key used to encrypt the boot disk attached to each node in the node pool. This should be of the form diff --git a/gcloud/alpha/container/node-pools/update b/gcloud/alpha/container/node-pools/update index 7853f6d68..af79c94aa 100644 --- a/gcloud/alpha/container/node-pools/update +++ b/gcloud/alpha/container/node-pools/update @@ -24,11 +24,8 @@ SYNOPSIS | --storage-pools=STORAGE_POOL,[...] | --system-config-from-file=PATH_TO_FILE | --tags=[TAG,...] | --windows-os-version=WINDOWS_OS_VERSION - | --workload-metadata=WORKLOAD_METADATA | --enable-blue-green-upgrade - --enable-surge-upgrade --max-surge-upgrade=MAX_SURGE_UPGRADE - --max-unavailable-upgrade=MAX_UNAVAILABLE_UPGRADE - --node-pool-soak-duration=NODE_POOL_SOAK_DURATION - --standard-rollout-policy=[batch-node-count=BATCH_NODE_COUNT, + | --workload-metadata=WORKLOAD_METADATA + | --autoscaled-rollout-policy=[wait-for-drain-duration=WAIT-FOR-DRAIN-DURATION] --enable-blue-green-upgrade --enable-surge-upgrade --max-surge-upgrade=MAX_SURGE_UPGRADE --max-unavailable-upgrade=MAX_UNAVAILABLE_UPGRADE --node-pool-soak-duration=NODE_POOL_SOAK_DURATION --standard-rollout-policy=[batch-node-count=BATCH_NODE_COUNT, batch-percent=BATCH_NODE_PERCENTAGE, batch-soak-duration=BATCH_SOAK_DURATION,...] | --boot-disk-provisioned-iops=BOOT_DISK_PROVISIONED_IOPS @@ -762,6 +759,23 @@ REQUIRED FLAGS Upgrade settings + --autoscaled-rollout-policy=[wait-for-drain-duration=WAIT-FOR-DRAIN-DURATION] + Autoscaled rollout policy options for blue-green upgrade. + + wait-for-drain-duration + (Optional) Time in seconds to wait after cordoning the blue + pool before draining the nodes. + + Examples: + + $ gcloud alpha container node-pools update node-pool-1 \ + --cluster=example-cluster --enable-blue-green-upgrade \ + --autoscaled-rollout-policy="" + + $ gcloud alpha container node-pools update node-pool-1 \ + --cluster=example-cluster --enable-blue-green-upgrade \ + --autoscaled-rollout-policy=wait-for-drain-duration=7200s + --enable-blue-green-upgrade Changes node pool upgrade strategy to blue-green upgrade. diff --git a/gcloud/alpha/design-center/spaces/applications/create b/gcloud/alpha/design-center/spaces/applications/create index 96c07ad70..d07d3808e 100644 --- a/gcloud/alpha/design-center/spaces/applications/create +++ b/gcloud/alpha/design-center/spaces/applications/create @@ -15,6 +15,7 @@ SYNOPSIS [--deployment-region=DEPLOYMENT_REGION] [--description=DESCRIPTION] [--display-name=DISPLAY_NAME] [--import-existing-resources] [--scope-type=SCOPE_TYPE] [--service-account=SERVICE_ACCOUNT] + [--type=TYPE] [--attributes-business-owners=[channel=CHANNEL], [displayName=DISPLAYNAME],[email=EMAIL] --attributes-developer-owners=[channel=CHANNEL], @@ -24,22 +25,24 @@ SYNOPSIS [--criticality-type=CRITICALITY_TYPE : --criticality-level=CRITICALITY_LEVEL --criticality-mission-critical] [--environment-type=ENVIRONMENT_TYPE - : --environment=ENVIRONMENT]] [GCLOUD_WIDE_FLAG ...] + : --environment=ENVIRONMENT]] + [--gke-deployment-target-cluster-self-link=GKE_DEPLOYMENT_TARGET_CLUSTER_SELF_LINK --gke-deployment-target-kubernetes-service-account=GKE_DEPLOYMENT_TARGET_KUBERNETES_SERVICE_ACCOUNT --gke-deployment-target-namespace=GKE_DEPLOYMENT_TARGET_NAMESPACE] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Create an application in a space. EXAMPLES - To create the application my-application with a display name of My - Application, description of My application description and source - application template revision + To create the application my-application with a display name My + Application, description My application description, scope type global and + source application template revision projects/my-project/locations/us-central1/spaces/my-space/applicationTemplates/my-app-template/revisions/rev1 in space my-space, project my-project and location us-central1, run: $ gcloud alpha design-center spaces applications create \ my-application --space=my-space --project=my-project \ --location=us-central1 --display-name="My Application" \ - --description="My application description" \ + --description="My application description" --scope-type=global \ --source-application-template-revision=projects/my-project/\ locations/us-central1/spaces/my-space/applicationTemplates/\ my-app-template/revisions/rev1 @@ -231,6 +234,14 @@ OPTIONAL FLAGS --service-account=SERVICE_ACCOUNT Your own service account that you use to deploy an application. + --type=TYPE + The type of the application. TYPE must be one of: + + helm-app + Application type is helm application. + terraform-app + Application type is terraform application. + Consumer provided attributes. --attributes-business-owners=[channel=CHANNEL],[displayName=DISPLAYNAME],[email=EMAIL] @@ -362,6 +373,32 @@ OPTIONAL FLAGS characters, underscores, and dashes. Can have a maximum length of 63 characters. Deprecated: Please refer to type instead. + The deployment target of the application. + + Arguments for the target. + + The GKE deployment target. + + --gke-deployment-target-cluster-self-link=GKE_DEPLOYMENT_TARGET_CLUSTER_SELF_LINK + The self link of the cluster where GKE based application is + deployed. + + This flag argument must be specified if any of the other + arguments in this group are specified. + + --gke-deployment-target-kubernetes-service-account=GKE_DEPLOYMENT_TARGET_KUBERNETES_SERVICE_ACCOUNT + The kubernetes service account that is created within the + namespace provided above. Example: default or node-sa + + This flag argument must be specified if any of the other + arguments in this group are specified. + + --gke-deployment-target-namespace=GKE_DEPLOYMENT_TARGET_NAMESPACE + The namespace where the application is deployed. + + 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, diff --git a/gcloud/alpha/design-center/spaces/applications/update b/gcloud/alpha/design-center/spaces/applications/update index 3fec02e22..9ba1d4a12 100644 --- a/gcloud/alpha/design-center/spaces/applications/update +++ b/gcloud/alpha/design-center/spaces/applications/update @@ -8,7 +8,7 @@ SYNOPSIS [--deployment-project=DEPLOYMENT_PROJECT] [--deployment-region=DEPLOYMENT_REGION] [--description=DESCRIPTION] [--display-name=DISPLAY_NAME] [--[no-]import-existing-resources] - [--service-account=SERVICE_ACCOUNT] + [--service-account=SERVICE_ACCOUNT] [--type=TYPE] [--app-parameters=[key=KEY],[value=VALUE] | --add-app-parameters=[key=KEY],[value=VALUE] --clear-app-parameters | --remove-app-parameters=[key=KEY],[value=VALUE]] @@ -38,6 +38,8 @@ SYNOPSIS --[no-]criticality-mission-critical --criticality-type=CRITICALITY_TYPE --environment=ENVIRONMENT --environment-type=ENVIRONMENT_TYPE] + [--clear-deployment-target + --gke-deployment-target-cluster-self-link=GKE_DEPLOYMENT_TARGET_CLUSTER_SELF_LINK --gke-deployment-target-kubernetes-service-account=GKE_DEPLOYMENT_TARGET_KUBERNETES_SERVICE_ACCOUNT --gke-deployment-target-namespace=GKE_DEPLOYMENT_TARGET_NAMESPACE] [--clear-scope --scope-type=SCOPE_TYPE] [--clear-source --source-application-template-revision=SOURCE_APPLICATION_TEMPLATE_REVISION | --source-shared-template-revision-uri=SOURCE_SHARED_TEMPLATE_REVISION_URI] @@ -183,6 +185,14 @@ FLAGS --service-account=SERVICE_ACCOUNT Your own service account that you use to deploy an application. + --type=TYPE + The type of the application. TYPE must be one of: + + helm-app + Application type is helm application. + terraform-app + Application type is terraform application. + Update app_parameters. At most one of these can be specified: @@ -590,6 +600,26 @@ FLAGS test Test environment. + The deployment target of the application. + + --clear-deployment-target + Set application.deploymentTarget back to default value. + + Arguments for the target. + + The GKE deployment target. + + --gke-deployment-target-cluster-self-link=GKE_DEPLOYMENT_TARGET_CLUSTER_SELF_LINK + The self link of the cluster where GKE based application is + deployed. + + --gke-deployment-target-kubernetes-service-account=GKE_DEPLOYMENT_TARGET_KUBERNETES_SERVICE_ACCOUNT + The kubernetes service account that is created within the + namespace provided above. Example: default or node-sa + + --gke-deployment-target-namespace=GKE_DEPLOYMENT_TARGET_NAMESPACE + The namespace where the application is deployed. + Scope of an application. --clear-scope diff --git a/gcloud/alpha/firestore/databases/help b/gcloud/alpha/firestore/databases/help index be64f0b4f..657567a16 100644 --- a/gcloud/alpha/firestore/databases/help +++ b/gcloud/alpha/firestore/databases/help @@ -35,6 +35,10 @@ COMMANDS list (ALPHA) Lists all Firestore databases under the project. + ping + (ALPHA) Times the connection and ping time for a Firestore with MongoDB + compatibility database. + restore (ALPHA) Restores a Cloud Firestore database from a backup. diff --git a/gcloud/alpha/firestore/databases/ping b/gcloud/alpha/firestore/databases/ping new file mode 100644 index 000000000..2c5b767ae --- /dev/null +++ b/gcloud/alpha/firestore/databases/ping @@ -0,0 +1,40 @@ +NAME + gcloud alpha firestore databases ping - times the connection and ping time + for a Firestore with MongoDB compatibility database + +SYNOPSIS + gcloud alpha firestore databases ping --database=DATABASE + [GCLOUD_WIDE_FLAG ...] + +EXAMPLES + To time the connection and ping times for a Firestore with MongoDB + compatibility database testdb: + + $ gcloud alpha firestore databases ping --database=testdb + +REQUIRED FLAGS + --database=DATABASE + The database to operate on. + + For example, to operate on database foo: + + $ gcloud alpha firestore databases ping --database='foo' + +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 firestore databases ping + + $ gcloud beta firestore databases ping + diff --git a/gcloud/alpha/iam/workforce-pools/providers/scim-tenants/delete b/gcloud/alpha/iam/workforce-pools/providers/scim-tenants/delete index d31bba282..d6010f9e1 100644 --- a/gcloud/alpha/iam/workforce-pools/providers/scim-tenants/delete +++ b/gcloud/alpha/iam/workforce-pools/providers/scim-tenants/delete @@ -5,7 +5,7 @@ NAME SYNOPSIS gcloud alpha iam workforce-pools providers scim-tenants delete (SCIM_TENANT : --location=LOCATION - --provider=PROVIDER --workforce-pool=WORKFORCE_POOL) + --provider=PROVIDER --workforce-pool=WORKFORCE_POOL) [--hard-delete] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -70,6 +70,10 @@ POSITIONAL ARGUMENTS specified name; ▸ provide the argument --workforce-pool on the command line. +FLAGS + --hard-delete + Deletes the SCIM tenant immediately. This operation cannot be undone. + 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/looker/instances/update b/gcloud/alpha/looker/instances/update index 1cf0f693c..22d96ca3d 100644 --- a/gcloud/alpha/looker/instances/update +++ b/gcloud/alpha/looker/instances/update @@ -10,6 +10,10 @@ SYNOPSIS [--add-developer-users=ADD_DEVELOPER_USERS --add-standard-users=ADD_STANDARD_USERS --add-viewer-users=ADD_VIEWER_USERS] + [--clear-periodic-export-config + | --periodic-export-gcs-uri=PERIODIC_EXPORT_GCS_URI + --periodic-export-kms-key=PERIODIC_EXPORT_KMS_KEY + --periodic-export-start-time=PERIODIC_EXPORT_START_TIME] [--clear-psc-allowed-vpcs | --psc-allowed-vpcs=[PSC_ALLOWED_VPCS,...] --clear-psc-service-attachments | --psc-service-attachment=[attachment=ATTACHMENT], @@ -125,6 +129,26 @@ FLAGS --add-viewer-users=ADD_VIEWER_USERS Number of additional Viewer Users to allocate to the Looker Instance. + At most one of these can be specified: + + --clear-periodic-export-config + Clears all periodic export configuration from the instance. + + Configuration for periodic export. All flags in this group must be + provided to enable or update the configuration. + + --periodic-export-gcs-uri=PERIODIC_EXPORT_GCS_URI + Cloud Storage bucket URI for periodic export. Format: + gs://{bucket_name} + + --periodic-export-kms-key=PERIODIC_EXPORT_KMS_KEY + Name of the CMEK key in KMS. Format: + projects/{project}/locations/{location}/keyRings/{key_ring}/cryptoKeys/{crypto_key} + + --periodic-export-start-time=PERIODIC_EXPORT_START_TIME + Time in UTC when the periodic export job starts. A valid time of + day must be specified in 24hr format (ex: 13:00, 17:30, 23:45). + Private Service Connect - Private Service Connect allows the Looker Instance to be reached via a private connection from inside a VPC network, and for the Looker Instance to connect to managed services via private diff --git a/gcloud/alpha/memorystore/instances/update b/gcloud/alpha/memorystore/instances/update index af72a5062..3bef3f26f 100644 --- a/gcloud/alpha/memorystore/instances/update +++ b/gcloud/alpha/memorystore/instances/update @@ -6,10 +6,10 @@ SYNOPSIS gcloud alpha memorystore instances update INSTANCE [--async] [--[no-]async-instance-endpoints-deletion-enabled] [--[no-]deletion-protection-enabled] [--engine-version=ENGINE_VERSION] - [--location=LOCATION] [--mode=MODE] [--node-type=NODE_TYPE] - [--[no-]ondemand-maintenance] [--replica-count=REPLICA_COUNT] - [--request-id=REQUEST_ID] [--shard-count=SHARD_COUNT] - [--[no-]simulate-maintenance-event] + [--location=LOCATION] [--maintenance-version=MAINTENANCE_VERSION] + [--mode=MODE] [--node-type=NODE_TYPE] [--[no-]ondemand-maintenance] + [--replica-count=REPLICA_COUNT] [--request-id=REQUEST_ID] + [--shard-count=SHARD_COUNT] [--[no-]simulate-maintenance-event] [--aof-config-append-fsync=AOF_CONFIG_APPEND_FSYNC --clear-persistence-config --persistence-config-mode=PERSISTENCE_CONFIG_MODE @@ -111,6 +111,13 @@ FLAGS value for resource location attribute. When the resource's full URI path is not provided, location will fallback to this flag value. + Arguments for the maintenance version. + + --maintenance-version=MAINTENANCE_VERSION + This field can be used to trigger self service update to indicate the + desired maintenance version. The input to this field can be + determined by the available_maintenance_versions field. + --mode=MODE The mode config for the instance. MODE must be one of: diff --git a/gcloud/alpha/redis/clusters/update b/gcloud/alpha/redis/clusters/update index 5d3e46ae3..9bbf5e7ab 100644 --- a/gcloud/alpha/redis/clusters/update +++ b/gcloud/alpha/redis/clusters/update @@ -8,7 +8,8 @@ SYNOPSIS [--automated-backup-mode=AUTOMATED_BACKUP_MODE] [--automated-backup-start-time=AUTOMATED_BACKUP_START_TIME] [--automated-backup-ttl=AUTOMATED_BACKUP_TTL] [--deletion-protection] - [--node-type=NODE_TYPE] [--persistence-mode=PERSISTENCE_MODE] + [--maintenance-version=MAINTENANCE_VERSION] [--node-type=NODE_TYPE] + [--persistence-mode=PERSISTENCE_MODE] [--rdb-snapshot-period=RDB_SNAPSHOT_PERIOD] [--rdb-snapshot-start-time=RDB_SNAPSHOT_START_TIME] [--remove-redis-config=[KEY,...]] [--replica-count=REPLICA_COUNT] @@ -107,6 +108,9 @@ FLAGS Enable deletion protection for the Redis Cluster. Use --deletion-protection/--no-deletion-protection to enable/disable it. + --maintenance-version=MAINTENANCE_VERSION + The maintenance version of the cluster. + --node-type=NODE_TYPE Node Type of the redis cluster Node. NODE_TYPE must be one of: redis-highmem-medium, redis-highmem-xlarge, redis-shared-core-nano, diff --git a/gcloud/alpha/resource-manager/tags/values/create b/gcloud/alpha/resource-manager/tags/values/create index e927b723d..26bdd2219 100644 --- a/gcloud/alpha/resource-manager/tags/values/create +++ b/gcloud/alpha/resource-manager/tags/values/create @@ -10,18 +10,18 @@ SYNOPSIS DESCRIPTION (ALPHA) Creates a TagValue resource given the short_name and description (optional) as well as the parent, the of the TagValue. The parent of the - TagValue can be a TagKey and TagValue the parent's details can be passed as - a numeric id or the namespaced name. + TagValue can be a TagKey or TagValue. The parent can be specified by its + numeric ID or its namespaced name. EXAMPLES - To create a TagValue with the short name 'test' and the description - 'description' under a TagKey with a short name 'env' under - 'organizations/123', run: + To create a TagValue with the short name test and the description + descriptio under a TagKey with a short name env under organizations/123, + run: $ gcloud alpha resource-manager tags values create test \ --parent=123/env --description=description - To create a TagValue with the short name 'test' under TagKey with id '456', + To create a TagValue with the short name test under TagKey with id 456, run: $ gcloud alpha resource-manager tags values create test \ diff --git a/gcloud/alpha/run/deploy b/gcloud/alpha/run/deploy index 849079aaf..738cbf317 100644 --- a/gcloud/alpha/run/deploy +++ b/gcloud/alpha/run/deploy @@ -15,6 +15,8 @@ SYNOPSIS [--min-instances=MIN_INSTANCES] [--region=REGION] [--regions=REGIONS] [--remove-containers=[CONTAINER,...]] [--revision-suffix=REVISION_SUFFIX] [--scaling=SCALING] + [--scaling-concurrency-utilization=SCALING_CONCURRENCY_UTILIZATION] + [--scaling-cpu-utilization=SCALING_CPU_UTILIZATION] [--service-account=SERVICE_ACCOUNT] [--[no-]session-affinity] [--tag=TAG] [--timeout=TIMEOUT] [--no-traffic] [--vpc-connector=VPC_CONNECTOR] [--vpc-egress=VPC_EGRESS] @@ -281,6 +283,18 @@ FLAGS "auto" for automatic scaling, or a positive integer to configure manual scaling with the given integer as a fixed instance count. + --scaling-concurrency-utilization=SCALING_CONCURRENCY_UTILIZATION + A value between 0.0 and 1.0 that indicates the target concurrency + utilization where a new instance should be started. Also accepts + "default" to restore the default value or "disabled" to disable + concurrency utilization scaling. + + --scaling-cpu-utilization=SCALING_CPU_UTILIZATION + A value between 0.0 and 1.0 that indicates the target CPU utilization + where a new instance should be started. Also accepts "default" to + restore the default value or "disabled" to disable CPU utilization + scaling. + --service-account=SERVICE_ACCOUNT the email address of an IAM service account associated with the revision of the service. The service account represents the identity of @@ -401,6 +415,12 @@ FLAGS Must be in the form project_id:region:instance_id and separated by semicolons. + ephemeral-disk: A volume that stores data on a temporary disk. With + this type of volume, data is not shared between instances and all data + will be lost when the instance it is on is terminated. Additional keys: + ◆ size: (optional) A quantity representing the amount of disk space + allocated to this volume, such as "512Mi" or "3G". + in-memory: An ephemeral volume that stores data in the instance's memory. With this type of volume, data is not shared between instances and all data will be lost when the instance it is on is terminated. diff --git a/gcloud/alpha/run/jobs/create b/gcloud/alpha/run/jobs/create index f5302dc91..2fc522478 100644 --- a/gcloud/alpha/run/jobs/create +++ b/gcloud/alpha/run/jobs/create @@ -182,6 +182,12 @@ FLAGS Must be in the form project_id:region:instance_id and separated by semicolons. + ephemeral-disk: A volume that stores data on a temporary disk. With + this type of volume, data is not shared between instances and all data + will be lost when the instance it is on is terminated. Additional keys: + ◆ size: (optional) A quantity representing the amount of disk space + allocated to this volume, such as "512Mi" or "3G". + in-memory: An ephemeral volume that stores data in the instance's memory. With this type of volume, data is not shared between instances and all data will be lost when the instance it is on is terminated. diff --git a/gcloud/alpha/run/jobs/deploy b/gcloud/alpha/run/jobs/deploy index eb4bfd31e..2907915ea 100644 --- a/gcloud/alpha/run/jobs/deploy +++ b/gcloud/alpha/run/jobs/deploy @@ -187,6 +187,12 @@ FLAGS Must be in the form project_id:region:instance_id and separated by semicolons. + ephemeral-disk: A volume that stores data on a temporary disk. With + this type of volume, data is not shared between instances and all data + will be lost when the instance it is on is terminated. Additional keys: + ◆ size: (optional) A quantity representing the amount of disk space + allocated to this volume, such as "512Mi" or "3G". + in-memory: An ephemeral volume that stores data in the instance's memory. With this type of volume, data is not shared between instances and all data will be lost when the instance it is on is terminated. diff --git a/gcloud/alpha/run/jobs/update b/gcloud/alpha/run/jobs/update index ef125f2fb..3486299d5 100644 --- a/gcloud/alpha/run/jobs/update +++ b/gcloud/alpha/run/jobs/update @@ -197,6 +197,12 @@ FLAGS Must be in the form project_id:region:instance_id and separated by semicolons. + ephemeral-disk: A volume that stores data on a temporary disk. With + this type of volume, data is not shared between instances and all data + will be lost when the instance it is on is terminated. Additional keys: + ◆ size: (optional) A quantity representing the amount of disk space + allocated to this volume, such as "512Mi" or "3G". + in-memory: An ephemeral volume that stores data in the instance's memory. With this type of volume, data is not shared between instances and all data will be lost when the instance it is on is terminated. diff --git a/gcloud/alpha/run/multi-region-services/help b/gcloud/alpha/run/multi-region-services/help index da28aaaf3..310b0f5bb 100644 --- a/gcloud/alpha/run/multi-region-services/help +++ b/gcloud/alpha/run/multi-region-services/help @@ -48,6 +48,10 @@ COMMANDS (ALPHA) Update environment variables, add/remove regions, and other configuration settings in Multi-Region Services. + update-traffic + (ALPHA) Adjust the traffic assignments for a Cloud Run Multi-Region + service. + 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/run/multi-region-services/update b/gcloud/alpha/run/multi-region-services/update index 7737f4d8b..3f8db743d 100644 --- a/gcloud/alpha/run/multi-region-services/update +++ b/gcloud/alpha/run/multi-region-services/update @@ -17,6 +17,8 @@ SYNOPSIS [--min-instances=MIN_INSTANCES] [--region=REGION] [--remove-containers=[CONTAINER,...]] [--revision-suffix=REVISION_SUFFIX] [--scaling=SCALING] + [--scaling-concurrency-utilization=SCALING_CONCURRENCY_UTILIZATION] + [--scaling-cpu-utilization=SCALING_CPU_UTILIZATION] [--service-account=SERVICE_ACCOUNT] [--[no-]session-affinity] [--tag=TAG] [--timeout=TIMEOUT] [--no-traffic] [--vpc-connector=VPC_CONNECTOR] [--vpc-egress=VPC_EGRESS] @@ -242,6 +244,18 @@ FLAGS "auto" for automatic scaling, or a positive integer to configure manual scaling with the given integer as a fixed instance count. + --scaling-concurrency-utilization=SCALING_CONCURRENCY_UTILIZATION + A value between 0.0 and 1.0 that indicates the target concurrency + utilization where a new instance should be started. Also accepts + "default" to restore the default value or "disabled" to disable + concurrency utilization scaling. + + --scaling-cpu-utilization=SCALING_CPU_UTILIZATION + A value between 0.0 and 1.0 that indicates the target CPU utilization + where a new instance should be started. Also accepts "default" to + restore the default value or "disabled" to disable CPU utilization + scaling. + --service-account=SERVICE_ACCOUNT the email address of an IAM service account associated with the revision of the service. The service account represents the identity of diff --git a/gcloud/alpha/run/multi-region-services/update-traffic b/gcloud/alpha/run/multi-region-services/update-traffic new file mode 100644 index 000000000..88f4b63a7 --- /dev/null +++ b/gcloud/alpha/run/multi-region-services/update-traffic @@ -0,0 +1,171 @@ +NAME + gcloud alpha run multi-region-services update-traffic - adjust the traffic + assignments for a Cloud Run Multi-Region service + +SYNOPSIS + gcloud alpha run multi-region-services update-traffic + [[SERVICE] --namespace=NAMESPACE] [--async] [--region=REGION] + [--clear-tags | --set-tags=[TAG=REVISION,...] + | --remove-tags=[TAG,...] --update-tags=[TAG=REVISION,...]] + [--to-latest | --to-revisions=[REVISION-NAME=PERCENTAGE,...] + | --to-tags=[TAG=PERCENTAGE,...]] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Adjust the traffic assignments for a Cloud Run Multi-Region + service. + +EXAMPLES + To assign 10% of traffic to revision myservice-s5sxn and 90% of traffic to + revision myservice-cp9kw run: + + $ gcloud alpha run multi-region-services update-traffic myservice \ + --to-revisions=myservice-s5sxn=10,myservice-cp9kw=90 + + To increase the traffic to revision myservice-s5sxn to 20% and by reducing + the traffic to revision myservice-cp9kw to 80% run: + + $ gcloud alpha run multi-region-services update-traffic myservice \ + --to-revisions=myservice-s5sxn=20 + + To rollback to revision myservice-cp9kw run: + + $ gcloud alpha run multi-region-services update-traffic myservice \ + --to-revisions=myservice-cp9kw=100 + + To assign 100% of traffic to the current or future LATEST revision run: + + $ gcloud alpha run multi-region-services update-traffic myservice \ + --to-latest + + You can also refer to the current or future LATEST revision in + --to-revisions by the string "LATEST". For example, to set 10% of traffic + to always float to the latest revision: + + $ gcloud alpha run multi-region-services update-traffic myservice \ + --to-revisions=LATEST=10 + +POSITIONAL ARGUMENTS + Service resource - Service to update the configuration of. The arguments + in this group can be used to specify the attributes of this resource. + + [SERVICE] + ID of the service or fully qualified identifier for the service. + + To set the service attribute: + ▸ provide the argument SERVICE on the command line; + ▸ specify the service name from an interactive prompt. + + --namespace=NAMESPACE + Specific to Cloud Run for Anthos: Kubernetes namespace for the + service. + + To set the namespace attribute: + ▸ provide the argument SERVICE on the command line with a fully + specified name; + ▸ specify the service name from an interactive prompt with a fully + specified name; + ▸ provide the argument --namespace on the command line; + ▸ set the property run/namespace; + ▸ For Cloud Run on Kubernetes Engine, defaults to "default". + Otherwise, defaults to project ID.; + ▸ provide the argument project on the command line; + ▸ set the property core/project. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --region=REGION + Region in which the resource can be found. Alternatively, set the + property [run/region]. + + Specify traffic tags. Traffic tags can be assigned to a revision by name + or to the latest ready revision. Assigning a tag to a revision generates a + URL prefixed with the tag that allows addressing that revision directly, + regardless of the percent traffic specified. Keys are tags. Values are + revision names or "LATEST" for the latest ready revision. For example, + --set-tags=candidate=LATEST,current=myservice-v1 assigns the tag + "candidate" to the latest ready revision and the tag "current" to the + revision with name "myservice-v1" and clears any existing tags. Changing + tags does not affect the traffic percentage assigned to revisions. When + using a tags flag and one or more of --to-latest and --to-revisions in the + same command, the tags change occurs first then the traffic percentage + change occurs. + + At most one of these can be specified: + + --clear-tags + Remove all tags. + + --set-tags=[TAG=REVISION,...] + List of key-value pairs to set as tags. All existing tags will be + removed first. + + Only --update-tags and --remove-tags can be used together. If both are + specified, --remove-tags will be applied first. + + --remove-tags=[TAG,...] + List of tags to be removed. + + --update-tags=[TAG=REVISION,...] + List of key-value pairs to set as tags. + + At most one of these can be specified: + + --to-latest + True to assign 100 percent of traffic to the 'latest' revision of + this service. Note that when a new revision is created, it will + become the 'latest' and traffic will be directed to it. Defaults to + False. Synonymous with '--to-revisions=LATEST=100'. + + --to-revisions=[REVISION-NAME=PERCENTAGE,...] + Comma separated list of traffic assignments in the form + REVISION-NAME=PERCENTAGE. REVISION-NAME must be the name for a + revision for the service as returned by 'gcloud beta run list + revisions'. PERCENTAGE must be an integer percentage between 0 and + 100 inclusive. Ex service-nw9hs=10,service-nw9hs=20 Up to 100 percent + of traffic may be assigned. If 100 percent of traffic is assigned, + the Service traffic is updated as specified. If under 100 percent of + traffic is assigned, the Service traffic is updated as specified for + revisions with assignments and traffic is scaled up or down down + proportionally as needed for revision that are currently serving + traffic but that do not have new assignments. For example assume + revision-1 is serving 40 percent of traffic and revision-2 is serving + 60 percent. If revision-1 is assigned 45 percent of traffic and no + assignment is made for revision-2, the service is updated with + revsion-1 assigned 45 percent of traffic and revision-2 scaled down + to 55 percent. You can use "LATEST" as a special revision name to + always put the given percentage of traffic on the latest ready + revision. + + --to-tags=[TAG=PERCENTAGE,...] + Comma separated list of traffic assignments in the form + TAG=PERCENTAGE. TAG must match a traffic tag on a revision of the + service. It may match a previously-set tag, or one assigned using the + --set-tags or --update-tags flags on this command. PERCENTAGE must be + an integer percentage between 0 and 100 inclusive. Up to 100 percent + of traffic may be assigned. If 100 percent of traffic is assigned, + the service traffic is updated as specified. If under 100 percent of + traffic is assigned, the service traffic is updated as specified to + the given tags, and other traffic is scaled up or down + proportionally. For example, assume the revision tagged next is + serving 40 percent of traffic and the revision tagged current is + serving 60 percent. If next is assigned 45 percent of traffic and no + assignment is made for current, the service is updated with next + assigned 45 percent of traffic and current scaled down to 55 percent. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/run/services/update b/gcloud/alpha/run/services/update index 6f849ff21..5fd669893 100644 --- a/gcloud/alpha/run/services/update +++ b/gcloud/alpha/run/services/update @@ -15,6 +15,8 @@ SYNOPSIS [--min-instances=MIN_INSTANCES] [--region=REGION] [--remove-containers=[CONTAINER,...]] [--revision-suffix=REVISION_SUFFIX] [--scaling=SCALING] + [--scaling-concurrency-utilization=SCALING_CONCURRENCY_UTILIZATION] + [--scaling-cpu-utilization=SCALING_CPU_UTILIZATION] [--service-account=SERVICE_ACCOUNT] [--[no-]session-affinity] [--tag=TAG] [--timeout=TIMEOUT] [--no-traffic] [--vpc-connector=VPC_CONNECTOR] [--vpc-egress=VPC_EGRESS] @@ -240,6 +242,18 @@ FLAGS "auto" for automatic scaling, or a positive integer to configure manual scaling with the given integer as a fixed instance count. + --scaling-concurrency-utilization=SCALING_CONCURRENCY_UTILIZATION + A value between 0.0 and 1.0 that indicates the target concurrency + utilization where a new instance should be started. Also accepts + "default" to restore the default value or "disabled" to disable + concurrency utilization scaling. + + --scaling-cpu-utilization=SCALING_CPU_UTILIZATION + A value between 0.0 and 1.0 that indicates the target CPU utilization + where a new instance should be started. Also accepts "default" to + restore the default value or "disabled" to disable CPU utilization + scaling. + --service-account=SERVICE_ACCOUNT the email address of an IAM service account associated with the revision of the service. The service account represents the identity of @@ -360,6 +374,12 @@ FLAGS Must be in the form project_id:region:instance_id and separated by semicolons. + ephemeral-disk: A volume that stores data on a temporary disk. With + this type of volume, data is not shared between instances and all data + will be lost when the instance it is on is terminated. Additional keys: + ◆ size: (optional) A quantity representing the amount of disk space + allocated to this volume, such as "512Mi" or "3G". + in-memory: An ephemeral volume that stores data in the instance's memory. With this type of volume, data is not shared between instances and all data will be lost when the instance it is on is terminated. diff --git a/gcloud/alpha/run/worker-pools/deploy b/gcloud/alpha/run/worker-pools/deploy index cdd4cc0ce..4473a4d97 100644 --- a/gcloud/alpha/run/worker-pools/deploy +++ b/gcloud/alpha/run/worker-pools/deploy @@ -231,6 +231,12 @@ FLAGS Must be in the form project_id:region:instance_id and separated by semicolons. + ephemeral-disk: A volume that stores data on a temporary disk. With + this type of volume, data is not shared between instances and all data + will be lost when the instance it is on is terminated. Additional keys: + ◆ size: (optional) A quantity representing the amount of disk space + allocated to this volume, such as "512Mi" or "3G". + in-memory: An ephemeral volume that stores data in the instance's memory. With this type of volume, data is not shared between instances and all data will be lost when the instance it is on is terminated. diff --git a/gcloud/alpha/run/worker-pools/update b/gcloud/alpha/run/worker-pools/update index e69cf99b8..afe245572 100644 --- a/gcloud/alpha/run/worker-pools/update +++ b/gcloud/alpha/run/worker-pools/update @@ -227,6 +227,12 @@ FLAGS Must be in the form project_id:region:instance_id and separated by semicolons. + ephemeral-disk: A volume that stores data on a temporary disk. With + this type of volume, data is not shared between instances and all data + will be lost when the instance it is on is terminated. Additional keys: + ◆ size: (optional) A quantity representing the amount of disk space + allocated to this volume, such as "512Mi" or "3G". + in-memory: An ephemeral volume that stores data in the instance's memory. With this type of volume, data is not shared between instances and all data will be lost when the instance it is on is terminated. diff --git a/gcloud/alpha/sql/instances/create b/gcloud/alpha/sql/instances/create index 401af1630..c982af842 100644 --- a/gcloud/alpha/sql/instances/create +++ b/gcloud/alpha/sql/instances/create @@ -23,9 +23,9 @@ SYNOPSIS [--deny-maintenance-period-end-date=DENY_MAINTENANCE_PERIOD_END_DATE] [--deny-maintenance-period-start-date=DENY_MAINTENANCE_PERIOD_START_DATE] [--deny-maintenance-period-time=DENY_MAINTENANCE_PERIOD_TIME] - [--edition=EDITION] [--enable-bin-log] - [--[no-]enable-connection-pooling] [--[no-]enable-data-cache] - [--[no-]enable-dataplex-integration] + [--edition=EDITION] [--enable-auto-upgrade-minor-version] + [--enable-bin-log] [--[no-]enable-connection-pooling] + [--[no-]enable-data-cache] [--[no-]enable-dataplex-integration] [--[no-]enable-google-ml-integration] [--enable-google-private-path] [--enable-password-policy] [--enable-point-in-time-recovery] [--enforce-new-sql-network-architecture] @@ -266,6 +266,10 @@ FLAGS Specifies the edition of Cloud SQL instance. EDITION must be one of: enterprise, enterprise-plus. + --enable-auto-upgrade-minor-version + Enables auto-upgrade for MySQL 8.0 minor versions. The MySQL version + must be 8.0.35 or higher. + --enable-bin-log Allows for data recovery from a specific point in time, down to a fraction of a second. Must have automatic backups enabled to use. Make diff --git a/gcloud/alpha/sql/instances/patch b/gcloud/alpha/sql/instances/patch index 0817d280e..b36b9f133 100644 --- a/gcloud/alpha/sql/instances/patch +++ b/gcloud/alpha/sql/instances/patch @@ -17,9 +17,9 @@ SYNOPSIS [--deny-maintenance-period-end-date=DENY_MAINTENANCE_PERIOD_END_DATE] [--deny-maintenance-period-start-date=DENY_MAINTENANCE_PERIOD_START_DATE] [--deny-maintenance-period-time=DENY_MAINTENANCE_PERIOD_TIME] [--diff] - [--edition=EDITION] [--[no-]enable-bin-log] - [--[no-]enable-connection-pooling] [--[no-]enable-data-cache] - [--[no-]enable-database-replication] + [--edition=EDITION] [--enable-auto-upgrade-minor-version] + [--[no-]enable-bin-log] [--[no-]enable-connection-pooling] + [--[no-]enable-data-cache] [--[no-]enable-database-replication] [--[no-]enable-dataplex-integration] [--[no-]enable-google-ml-integration] [--[no-]enable-google-private-path] [--enable-password-policy] @@ -202,6 +202,10 @@ FLAGS Specifies the edition of Cloud SQL instance. EDITION must be one of: enterprise, enterprise-plus. + --enable-auto-upgrade-minor-version + Enables auto-upgrade for MySQL 8.0 minor versions. The MySQL version + must be 8.0.35 or higher. + --[no-]enable-bin-log Allows for data recovery from a specific point in time, down to a fraction of a second. Must have automatic backups enabled to use. Make diff --git a/gcloud/beta/bigtable/operations/list b/gcloud/beta/bigtable/operations/list index 4c2d26cf8..c949196d9 100644 --- a/gcloud/beta/bigtable/operations/list +++ b/gcloud/beta/bigtable/operations/list @@ -3,6 +3,7 @@ NAME SYNOPSIS gcloud beta bigtable operations list [--instance=INSTANCE] + [--return-partial-success=RETURN_PARTIAL_SUCCESS; default=True] [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] @@ -18,6 +19,10 @@ EXAMPLES $ gcloud beta bigtable operations list --instance=INSTANCE_NAME + To fail the command if any location is unreachable, run: + + $ gcloud beta bigtable operations list --return-partial-success=false + FLAGS Instance resource - The instance to list operations for. This represents a Cloud resource. (NOTE) Some attributes are not given arguments in this @@ -35,6 +40,13 @@ FLAGS To set the instance attribute: ▸ provide the argument --instance on the command line. + --return-partial-success=RETURN_PARTIAL_SUCCESS; default=True + If true, operations that are reachable are returned as normal, and + those that are unreachable are returned in the unreachable field of the + response. If false, the command will fail if any location is + unreachable. Enabled by default, use --no-return-partial-success to + disable. + LIST COMMAND FLAGS --filter=EXPRESSION Apply a Boolean filter EXPRESSION to each resource item to be listed. diff --git a/gcloud/beta/compute/backend-services/create b/gcloud/beta/compute/backend-services/create index 4cfbb0728..0dfd6e48c 100644 --- a/gcloud/beta/compute/backend-services/create +++ b/gcloud/beta/compute/backend-services/create @@ -406,7 +406,7 @@ FLAGS The load balancing algorithm used within the scope of the locality. LOCALITY_LB_POLICY must be one of: INVALID_LB_POLICY, ROUND_ROBIN, LEAST_REQUEST, RING_HASH, RANDOM, ORIGINAL_DESTINATION, MAGLEV, - WEIGHTED_MAGLEV, WEIGHTED_ROUND_ROBIN. + WEIGHTED_MAGLEV, WEIGHTED_ROUND_ROBIN, WEIGHTED_GCP_RENDEZVOUS. --logging-optional=LOGGING_OPTIONAL This field can only be specified if logging is enabled for the backend diff --git a/gcloud/beta/compute/backend-services/update b/gcloud/beta/compute/backend-services/update index a57a6a9a9..6be410bec 100644 --- a/gcloud/beta/compute/backend-services/update +++ b/gcloud/beta/compute/backend-services/update @@ -26,7 +26,6 @@ SYNOPSIS [--ip-address-selection-policy=IP_ADDRESS_SELECTION_POLICY] [--ip-port-dynamic-forwarding] [--load-balancing-scheme=LOAD_BALANCING_SCHEME] - [--locality-lb-policy=LOCALITY_LB_POLICY] [--logging-optional=LOGGING_OPTIONAL] [--logging-optional-fields=[LOGGING_OPTIONAL_FIELDS,...]] [--logging-sample-rate=LOGGING_SAMPLE_RATE] [--port-name=PORT_NAME] @@ -55,6 +54,7 @@ SYNOPSIS [--default-ttl=DEFAULT_TTL | --no-default-ttl] [--global | --region=REGION] [--global-health-checks | --health-checks-region=HEALTH_CHECKS_REGION] + [--locality-lb-policy=LOCALITY_LB_POLICY | --no-locality-lb-policy] [--max-ttl=MAX_TTL | --no-max-ttl] [--[no-]negative-caching | --no-negative-caching-policies | --negative-caching-policy=[[CODE=TTL],...]] @@ -322,12 +322,6 @@ FLAGS LOAD_BALANCING_SCHEME must be one of: EXTERNAL, EXTERNAL_MANAGED. - --locality-lb-policy=LOCALITY_LB_POLICY - The load balancing algorithm used within the scope of the locality. - LOCALITY_LB_POLICY must be one of: INVALID_LB_POLICY, ROUND_ROBIN, - LEAST_REQUEST, RING_HASH, RANDOM, ORIGINAL_DESTINATION, MAGLEV, - WEIGHTED_MAGLEV, WEIGHTED_ROUND_ROBIN. - --logging-optional=LOGGING_OPTIONAL This field can only be specified if logging is enabled for the backend service. Configures whether all, none, or a subset of optional fields @@ -867,6 +861,17 @@ FLAGS Alternatively, the region can be stored in the environment variable CLOUDSDK_COMPUTE_REGION. + At most one of these can be specified: + + --locality-lb-policy=LOCALITY_LB_POLICY + The load balancing algorithm used within the scope of the locality. + LOCALITY_LB_POLICY must be one of: INVALID_LB_POLICY, ROUND_ROBIN, + LEAST_REQUEST, RING_HASH, RANDOM, ORIGINAL_DESTINATION, MAGLEV, + WEIGHTED_MAGLEV, WEIGHTED_ROUND_ROBIN, WEIGHTED_GCP_RENDEZVOUS. + + --no-locality-lb-policy + Removes the locality load balancing policy from the backend service. + At most one of these can be specified: --max-ttl=MAX_TTL diff --git a/gcloud/beta/compute/composite-health-checks/create b/gcloud/beta/compute/composite-health-checks/create new file mode 100644 index 000000000..827e6a16f --- /dev/null +++ b/gcloud/beta/compute/composite-health-checks/create @@ -0,0 +1,94 @@ +NAME + gcloud beta compute composite-health-checks create - create a composite + health check + +SYNOPSIS + gcloud beta compute composite-health-checks create + (COMPOSITE_HEALTH_CHECK : --region=REGION) + --health-destination=HEALTH_DESTINATION + --health-sources=[HEALTH_SOURCES,...] [--async] + [--description=DESCRIPTION] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Create a composite health check. + +EXAMPLES + The following command creates a new composite health check: + + $ gcloud beta compute composite-health-checks create \ + --region= \ + --health-sources=my-hs --health-destination=my-fr + +POSITIONAL ARGUMENTS + Composite health check resource - The name of the composite health check + you want to create. 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 composite_health_check 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. + + COMPOSITE_HEALTH_CHECK + ID of the composite health check or fully qualified identifier for + the composite health check. + + To set the composite_health_check attribute: + ▸ provide the argument composite_health_check on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --region=REGION + The name of the Google Compute Engine region. + + To set the region attribute: + ▸ provide the argument composite_health_check on the command line + with a fully specified name; + ▸ provide the argument --region on the command line; + ▸ set the property compute/region. + +REQUIRED FLAGS + --health-destination=HEALTH_DESTINATION + URL to the destination resource. Must be set. Must be a ForwardingRule. + The ForwardingRule must have load balancing scheme INTERNAL or + INTERNAL_MANAGED and must be regional and in the same region as the + CompositeHealthCheck (cross-region deployment for INTERNAL_MANAGED is + not supported). Can be mutated. + + --health-sources=[HEALTH_SOURCES,...] + URLs to the HealthSource resources whose results are AND'ed. I.e. the + aggregated result is HEALTHY only if all sources are HEALTHY. Must have + at least 1. Must not have more than 10. Must be regional and in the + same region as the CompositeHealthCheck. Can be mutated. + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --description=DESCRIPTION + A textual description of this resource. + +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 compute/beta API. The full documentation for this API + can be found at: https://cloud.google.com/compute/ + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha compute composite-health-checks create + diff --git a/gcloud/beta/compute/composite-health-checks/delete b/gcloud/beta/compute/composite-health-checks/delete new file mode 100644 index 000000000..e01965405 --- /dev/null +++ b/gcloud/beta/compute/composite-health-checks/delete @@ -0,0 +1,74 @@ +NAME + gcloud beta compute composite-health-checks delete - delete a composite + health check + +SYNOPSIS + gcloud beta compute composite-health-checks delete + (COMPOSITE_HEALTH_CHECK : --region=REGION) [--async] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Delete a composite health check. + +EXAMPLES + To delete a single composite health check, run the following command: + + $ gcloud beta compute composite-health-checks delete \ + --region= + +POSITIONAL ARGUMENTS + Composite health check resource - Name of the composite health check you + want to delete. The arguments in this group can be used to specify the + attributes of this resource. (NOTE) Some attributes are not given + arguments in this group but can be set in other ways. + + To set the project attribute: + ◆ provide the argument composite_health_check 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. + + COMPOSITE_HEALTH_CHECK + ID of the composite health check or fully qualified identifier for + the composite health check. + + To set the composite_health_check attribute: + ▸ provide the argument composite_health_check on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --region=REGION + The name of the Google Compute Engine region. + + To set the region attribute: + ▸ provide the argument composite_health_check on the command line + with a fully specified name; + ▸ provide the argument --region on the command line; + ▸ set the property compute/region. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the compute/beta API. The full documentation for this API + can be found at: https://cloud.google.com/compute/ + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha compute composite-health-checks delete + diff --git a/gcloud/beta/compute/composite-health-checks/describe b/gcloud/beta/compute/composite-health-checks/describe new file mode 100644 index 000000000..7e6e5e308 --- /dev/null +++ b/gcloud/beta/compute/composite-health-checks/describe @@ -0,0 +1,69 @@ +NAME + gcloud beta compute composite-health-checks describe - describe a composite + health check + +SYNOPSIS + gcloud beta compute composite-health-checks describe + (COMPOSITE_HEALTH_CHECK : --region=REGION) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Describe a composite health check. + +EXAMPLES + To retrieve a single composite health check and print its properties, run + the following command: + + $ gcloud beta compute composite-health-checks describe \ + --region= + +POSITIONAL ARGUMENTS + Composite health check resource - Name of the composite health check you + want to inspect. 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 composite_health_check 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. + + COMPOSITE_HEALTH_CHECK + ID of the composite health check or fully qualified identifier for + the composite health check. + + To set the composite_health_check attribute: + ▸ provide the argument composite_health_check on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --region=REGION + The name of the Google Compute Engine region. + + To set the region attribute: + ▸ provide the argument composite_health_check on the command line + with a fully specified name; + ▸ provide the argument --region on the command line; + ▸ set the property compute/region. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the compute/beta API. The full documentation for this API + can be found at: https://cloud.google.com/compute/ + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha compute composite-health-checks describe + diff --git a/gcloud/beta/compute/composite-health-checks/help b/gcloud/beta/compute/composite-health-checks/help new file mode 100644 index 000000000..eaeebe383 --- /dev/null +++ b/gcloud/beta/compute/composite-health-checks/help @@ -0,0 +1,39 @@ +NAME + gcloud beta compute composite-health-checks - manage composite health + checks + +SYNOPSIS + gcloud beta compute composite-health-checks COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Manage composite health checks. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + create + (BETA) Create a composite health check. + + delete + (BETA) Delete a composite health check. + + describe + (BETA) Describe a composite health check. + + list + (BETA) List composite health checks. + + update + (BETA) Update a composite health check. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha compute composite-health-checks + diff --git a/gcloud/beta/compute/tpus/execution-groups/list b/gcloud/beta/compute/composite-health-checks/list similarity index 60% rename from gcloud/beta/compute/tpus/execution-groups/list rename to gcloud/beta/compute/composite-health-checks/list index 2f0e0c3cf..7c11ed99f 100644 --- a/gcloud/beta/compute/tpus/execution-groups/list +++ b/gcloud/beta/compute/composite-health-checks/list @@ -1,47 +1,34 @@ NAME - gcloud beta compute tpus execution-groups list - list TPU Node+VM groups - created by execution group + gcloud beta compute composite-health-checks list - list composite health + checks SYNOPSIS - gcloud beta compute tpus execution-groups list [--zone=ZONE] + gcloud beta compute composite-health-checks list [NAME ...] + [--regexp=REGEXP, -r REGEXP] [--regions=REGION,[REGION,...]] [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) (DEPRECATED) List TPU Node+VM groups created by execution group. + (BETA) List composite health checks. - This command is deprecated and will be removed in a future release. We - recommend that you use the TPU-VM or Queued Resource API. See - https://cloud.google.com/tpu/docs/managing-tpus-tpu-vm for more - information. +POSITIONAL ARGUMENTS + [NAME ...] + (DEPRECATED) If provided, show details for the specified names and/or + URIs of resources. -EXAMPLES - To list all active execution groups, run: - - $ gcloud beta compute tpus execution-groups list --zone=test-zone \ - --project=test-project + Argument NAME is deprecated. Use --filter="name=( 'NAME' ... )" + instead. FLAGS - --zone=ZONE - Zone of the tpu to list. If not specified and the compute/zone property - isn't set, you might be prompted to select a zone (interactive mode - only). + --regexp=REGEXP, -r REGEXP + (DEPRECATED) Regular expression to filter the names of the results on. + Any names that do not match the entire regular expression will be + filtered out. - To avoid prompting when this flag is omitted, you can set the - compute/zone property: + Flag --regexp is deprecated. Use --filter="name~'REGEXP'" instead. - $ 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. + --regions=REGION,[REGION,...] + If provided, only resources from the given regions are queried. LIST COMMAND FLAGS --filter=EXPRESSION @@ -84,10 +71,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 tpus execution-groups list - - $ gcloud alpha compute tpus execution-groups list + $ gcloud alpha compute composite-health-checks list diff --git a/gcloud/beta/compute/composite-health-checks/update b/gcloud/beta/compute/composite-health-checks/update new file mode 100644 index 000000000..070d37676 --- /dev/null +++ b/gcloud/beta/compute/composite-health-checks/update @@ -0,0 +1,96 @@ +NAME + gcloud beta compute composite-health-checks update - update a composite + health check + +SYNOPSIS + gcloud beta compute composite-health-checks update + (COMPOSITE_HEALTH_CHECK : --region=REGION) + (--description=DESCRIPTION --health-destination=HEALTH_DESTINATION + --health-sources=[HEALTH_SOURCES,...]) [--async] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Update a composite health check. + +EXAMPLES + The following command updates an existing composite health check: + + $ gcloud beta compute composite-health-checks update \ + --region= \ + --health-destination=my-new-fr + +POSITIONAL ARGUMENTS + Composite health check resource - The name of the composite health check + you want to update. The arguments in this group can be used to specify the + attributes of this resource. (NOTE) Some attributes are not given + arguments in this group but can be set in other ways. + + To set the project attribute: + ◆ provide the argument composite_health_check 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. + + COMPOSITE_HEALTH_CHECK + ID of the composite health check or fully qualified identifier for + the composite health check. + + To set the composite_health_check attribute: + ▸ provide the argument composite_health_check on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --region=REGION + The name of the Google Compute Engine region. + + To set the region attribute: + ▸ provide the argument composite_health_check on the command line + with a fully specified name; + ▸ provide the argument --region on the command line; + ▸ set the property compute/region. + +REQUIRED FLAGS + At least one of these must be specified: + + --description=DESCRIPTION + A textual description of this resource. + + --health-destination=HEALTH_DESTINATION + URL to the destination resource. Must be set. Must be a + ForwardingRule. The ForwardingRule must have load balancing scheme + INTERNAL or INTERNAL_MANAGED and must be regional and in the same + region as the CompositeHealthCheck (cross-region deployment for + INTERNAL_MANAGED is not supported). Can be mutated. + + --health-sources=[HEALTH_SOURCES,...] + URLs to the HealthSource resources whose results are AND'ed. I.e. the + aggregated result is HEALTHY only if all sources are HEALTHY. Must + have at least 1. Must not have more than 10. Must be regional and in + the same region as the CompositeHealthCheck. Can be mutated. + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the compute/beta API. The full documentation for this API + can be found at: https://cloud.google.com/compute/ + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha compute composite-health-checks update + diff --git a/gcloud/beta/compute/health-aggregation-policies/create b/gcloud/beta/compute/health-aggregation-policies/create new file mode 100644 index 000000000..23ff2e5a9 --- /dev/null +++ b/gcloud/beta/compute/health-aggregation-policies/create @@ -0,0 +1,114 @@ +NAME + gcloud beta compute health-aggregation-policies create - create a health + aggregation policy + +SYNOPSIS + gcloud beta compute health-aggregation-policies create + (HEALTH_AGGREGATION_POLICY : --region=REGION) [--async] + [--description=DESCRIPTION] + [--healthy-percent-threshold=HEALTHY_PERCENT_THRESHOLD; default=60] + [--min-healthy-threshold=MIN_HEALTHY_THRESHOLD; default=1] + [--policy-type=POLICY_TYPE; default="backend-service-policy"] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Create a health aggregation policy. + +EXAMPLES + The following command creates a new health aggregation policy: + + $ gcloud beta compute health-aggregation-policies create \ + --region= \ + --healthy-percent-threshold 60 --min-healthy-threshold 2 \ + --policy-type=BACKEND_SERVICE_POLICY + +POSITIONAL ARGUMENTS + Health aggregation policy resource - The name of the health aggregation + policy you want to create. 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 health_aggregation_policy 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. + + HEALTH_AGGREGATION_POLICY + ID of the health aggregation policy or fully qualified identifier for + the health aggregation policy. + + To set the health_aggregation_policy attribute: + ▸ provide the argument health_aggregation_policy on the command + line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --region=REGION + The name of the Google Compute Engine region. + + To set the region attribute: + ▸ provide the argument health_aggregation_policy on the command + line with a fully specified name; + ▸ provide the argument --region on the command line; + ▸ set the property compute/region. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --description=DESCRIPTION + A textual description of the health aggregation policy. + + --healthy-percent-threshold=HEALTHY_PERCENT_THRESHOLD; default=60 + Can only be set if the policyType field is BACKEND_SERVICE_POLICY. + Specifies the threshold (as a percentage) of healthy endpoints required + in order to consider the aggregated health result HEALTHY. Defaults to + 60. Must be in range [0, 100]. Not applicable if the policyType field + is DNS_PUBLIC_IP_POLICY. Can be mutated. This field is optional, and + will be set to the default if unspecified. Note that both this + threshold and minHealthyThreshold must be satisfied in order for + HEALTHY to be the aggregated result. "Endpoints" refers to network + endpoints within a Network Endpoint Group or instances within an + Instance Group. + + --min-healthy-threshold=MIN_HEALTHY_THRESHOLD; default=1 + Can only be set if the policyType field is BACKEND_SERVICE_POLICY. + Specifies the minimum number of healthy endpoints required in order to + consider the aggregated health result HEALTHY. Defaults to 1. Must be + positive. Not applicable if the policyType field is + DNS_PUBLIC_IP_POLICY. Can be mutated. This field is optional, and will + be set to the default if unspecified. Note that both this threshold and + healthyPercentThreshold must be satisfied in order for HEALTHY to be + the aggregated result. "Endpoints" refers to network endpoints within a + Network Endpoint Group or instances within an Instance Group. + + --policy-type=POLICY_TYPE; default="backend-service-policy" + Specifies the type of the healthAggregationPolicy. The only allowed + value for regional resources is BACKEND_SERVICE_POLICY. Must be + specified when the healthAggregationPolicy is created, and cannot be + mutated. POLICY_TYPE must be one of: backend-service-policy, + dns-public-ip-policy. + +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 compute/beta API. The full documentation for this API + can be found at: https://cloud.google.com/compute/ + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha compute health-aggregation-policies create + diff --git a/gcloud/beta/compute/health-aggregation-policies/delete b/gcloud/beta/compute/health-aggregation-policies/delete new file mode 100644 index 000000000..48aca9918 --- /dev/null +++ b/gcloud/beta/compute/health-aggregation-policies/delete @@ -0,0 +1,75 @@ +NAME + gcloud beta compute health-aggregation-policies delete - delete a health + aggregation policy + +SYNOPSIS + gcloud beta compute health-aggregation-policies delete + (HEALTH_AGGREGATION_POLICY : --region=REGION) [--async] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Delete a health aggregation policy. + +EXAMPLES + To delete a single health aggregation policy, run the following command: + + $ gcloud beta compute health-aggregation-policies delete \ + --region= + +POSITIONAL ARGUMENTS + Health aggregation policy resource - Name of the health aggregation policy + you want to delete. The arguments in this group can be used to specify the + attributes of this resource. (NOTE) Some attributes are not given + arguments in this group but can be set in other ways. + + To set the project attribute: + ◆ provide the argument health_aggregation_policy 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. + + HEALTH_AGGREGATION_POLICY + ID of the health aggregation policy or fully qualified identifier for + the health aggregation policy. + + To set the health_aggregation_policy attribute: + ▸ provide the argument health_aggregation_policy on the command + line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --region=REGION + The name of the Google Compute Engine region. + + To set the region attribute: + ▸ provide the argument health_aggregation_policy on the command + line with a fully specified name; + ▸ provide the argument --region on the command line; + ▸ set the property compute/region. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the compute/beta API. The full documentation for this API + can be found at: https://cloud.google.com/compute/ + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha compute health-aggregation-policies delete + diff --git a/gcloud/beta/compute/health-aggregation-policies/describe b/gcloud/beta/compute/health-aggregation-policies/describe new file mode 100644 index 000000000..d75fc4e1f --- /dev/null +++ b/gcloud/beta/compute/health-aggregation-policies/describe @@ -0,0 +1,70 @@ +NAME + gcloud beta compute health-aggregation-policies describe - describe a + health aggregation policy + +SYNOPSIS + gcloud beta compute health-aggregation-policies describe + (HEALTH_AGGREGATION_POLICY : --region=REGION) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Describe a health aggregation policy. + +EXAMPLES + To retrieve a single health aggregation policy and print its properties, + run the following command: + + $ gcloud beta compute health-aggregation-policies describe \ + --region= + +POSITIONAL ARGUMENTS + Health aggregation policy resource - Name of the health aggregation policy + you want to inspect. 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 health_aggregation_policy 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. + + HEALTH_AGGREGATION_POLICY + ID of the health aggregation policy or fully qualified identifier for + the health aggregation policy. + + To set the health_aggregation_policy attribute: + ▸ provide the argument health_aggregation_policy on the command + line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --region=REGION + The name of the Google Compute Engine region. + + To set the region attribute: + ▸ provide the argument health_aggregation_policy on the command + line with a fully specified name; + ▸ provide the argument --region on the command line; + ▸ set the property compute/region. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the compute/beta API. The full documentation for this API + can be found at: https://cloud.google.com/compute/ + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha compute health-aggregation-policies describe + diff --git a/gcloud/beta/compute/health-aggregation-policies/help b/gcloud/beta/compute/health-aggregation-policies/help new file mode 100644 index 000000000..128313a2a --- /dev/null +++ b/gcloud/beta/compute/health-aggregation-policies/help @@ -0,0 +1,40 @@ +NAME + gcloud beta compute health-aggregation-policies - manage health aggregation + policies + +SYNOPSIS + gcloud beta compute health-aggregation-policies COMMAND + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Manage health aggregation policies. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + create + (BETA) Create a health aggregation policy. + + delete + (BETA) Delete a health aggregation policy. + + describe + (BETA) Describe a health aggregation policy. + + list + (BETA) List health aggregation policies. + + update + (BETA) Update a health aggregation policy. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha compute health-aggregation-policies + diff --git a/gcloud/beta/compute/health-aggregation-policies/list b/gcloud/beta/compute/health-aggregation-policies/list new file mode 100644 index 000000000..17b7df245 --- /dev/null +++ b/gcloud/beta/compute/health-aggregation-policies/list @@ -0,0 +1,78 @@ +NAME + gcloud beta compute health-aggregation-policies list - list health + aggregation policies + +SYNOPSIS + gcloud beta compute health-aggregation-policies list [NAME ...] + [--regexp=REGEXP, -r REGEXP] [--regions=REGION,[REGION,...]] + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) List health aggregation policies. + +POSITIONAL ARGUMENTS + [NAME ...] + (DEPRECATED) If provided, show details for the specified names and/or + URIs of resources. + + Argument NAME is deprecated. Use --filter="name=( 'NAME' ... )" + instead. + +FLAGS + --regexp=REGEXP, -r REGEXP + (DEPRECATED) Regular expression to filter the names of the results on. + Any names that do not match the entire regular expression will be + filtered out. + + Flag --regexp is deprecated. Use --filter="name~'REGEXP'" instead. + + --regions=REGION,[REGION,...] + If provided, only resources from the given regions are queried. + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + + --uri + Print a list of resource URIs instead of the default output, and change + the command output to a list of URIs. If this flag is used with + --format, the formatting is applied on this URI list. To display URIs + alongside other keys instead, use the uri() transform. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha compute health-aggregation-policies list + diff --git a/gcloud/beta/compute/health-aggregation-policies/update b/gcloud/beta/compute/health-aggregation-policies/update new file mode 100644 index 000000000..8c46e3b76 --- /dev/null +++ b/gcloud/beta/compute/health-aggregation-policies/update @@ -0,0 +1,109 @@ +NAME + gcloud beta compute health-aggregation-policies update - update a health + aggregation policy + +SYNOPSIS + gcloud beta compute health-aggregation-policies update + (HEALTH_AGGREGATION_POLICY : --region=REGION) + (--description=DESCRIPTION + --healthy-percent-threshold=HEALTHY_PERCENT_THRESHOLD + --min-healthy-threshold=MIN_HEALTHY_THRESHOLD) [--async] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Update a health aggregation policy. + +EXAMPLES + The following command updates a health aggregation policy: + + $ gcloud beta compute health-aggregation-policies update \ + --region= \ + --healthy-percent-threshold 60 --min-healthy-threshold 2 \ + +POSITIONAL ARGUMENTS + Health aggregation policy resource - The health aggregation policy you + want to update. The arguments in this group can be used to specify the + attributes of this resource. (NOTE) Some attributes are not given + arguments in this group but can be set in other ways. + + To set the project attribute: + ◆ provide the argument health_aggregation_policy 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. + + HEALTH_AGGREGATION_POLICY + ID of the health aggregation policy or fully qualified identifier for + the health aggregation policy. + + To set the health_aggregation_policy attribute: + ▸ provide the argument health_aggregation_policy on the command + line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --region=REGION + The name of the Google Compute Engine region. + + To set the region attribute: + ▸ provide the argument health_aggregation_policy on the command + line with a fully specified name; + ▸ provide the argument --region on the command line; + ▸ set the property compute/region. + +REQUIRED FLAGS + At least one of these must be specified: + + --description=DESCRIPTION + A textual description of the health aggregation policy. + + --healthy-percent-threshold=HEALTHY_PERCENT_THRESHOLD + Can only be set if the policyType field is BACKEND_SERVICE_POLICY. + Specifies the threshold (as a percentage) of healthy endpoints + required in order to consider the aggregated health result HEALTHY. + Defaults to 60. Must be in range [0, 100]. Not applicable if the + policyType field is DNS_PUBLIC_IP_POLICY. Can be mutated. This field + is optional, and will be set to the default if unspecified. Note that + both this threshold and minHealthyThreshold must be satisfied in + order for HEALTHY to be the aggregated result. "Endpoints" refers to + network endpoints within a Network Endpoint Group or instances within + an Instance Group. + + --min-healthy-threshold=MIN_HEALTHY_THRESHOLD + Can only be set if the policyType field is BACKEND_SERVICE_POLICY. + Specifies the minimum number of healthy endpoints required in order + to consider the aggregated health result HEALTHY. Defaults to 1. Must + be positive. Not applicable if the policyType field is + DNS_PUBLIC_IP_POLICY. Can be mutated. This field is optional, and + will be set to the default if unspecified. Note that both this + threshold and healthyPercentThreshold must be satisfied in order for + HEALTHY to be the aggregated result. "Endpoints" refers to network + endpoints within a Network Endpoint Group or instances within an + Instance Group. + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the compute/beta API. The full documentation for this API + can be found at: https://cloud.google.com/compute/ + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha compute health-aggregation-policies update + diff --git a/gcloud/beta/compute/help b/gcloud/beta/compute/help index 0440fdd0e..78ab4aab5 100644 --- a/gcloud/beta/compute/help +++ b/gcloud/beta/compute/help @@ -43,6 +43,9 @@ GROUPS commitments (BETA) Manage Compute Engine commitments. + composite-health-checks + (BETA) Manage composite health checks. + diagnose (BETA) Debugging tools for Compute Engine virtual machine instances. @@ -71,6 +74,9 @@ GROUPS future-reservations (BETA) Manage Compute Engine future reservations. + health-aggregation-policies + (BETA) Manage health aggregation policies. + health-checks (BETA) Read and manipulate health checks for load balanced instances. diff --git a/gcloud/beta/compute/instances/help b/gcloud/beta/compute/instances/help index 271a97fe3..9a257d931 100644 --- a/gcloud/beta/compute/instances/help +++ b/gcloud/beta/compute/instances/help @@ -111,10 +111,6 @@ COMMANDS list (BETA) List Compute Engine instances. - move - (BETA) (DEPRECATED) Move an instance and its attached persistent disks - between zones. - patch-partner-metadata (BETA) Patch partner metadata. diff --git a/gcloud/beta/compute/instances/move b/gcloud/beta/compute/instances/move deleted file mode 100644 index 4f1ae9bce..000000000 --- a/gcloud/beta/compute/instances/move +++ /dev/null @@ -1,96 +0,0 @@ -NAME - gcloud beta compute instances move - move an instance and its attached - persistent disks between zones - -SYNOPSIS - gcloud beta compute instances move INSTANCE_NAME - --destination-zone=DESTINATION_ZONE [--async] [--zone=ZONE] - [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (BETA) (DEPRECATED) This command is deprecated. Please see - https://cloud.google.com/compute/docs/instances/moving-instance-across-zones - for an alternative method. - - gcloud beta compute instances move moves a Compute Engine virtual machine - from one zone to another. Moving a virtual machine might incur downtime if - the guest OS must be shut down in order to quiesce disk volumes prior to - snapshotting. - - For example, running the following command moves the instance called - example-instance-1 with its attached persistent disks, currently running in - us-central1-b, to us-central1-f. - - $ gcloud compute instances move example-instance-1 \ - --zone=us-central1-b --destination-zone=us-central1-f - - Note: Moving VMs or disks by using the gcloud beta compute instances move - command might cause unexpected behavior. For more information, see - https://cloud.google.com/compute/docs/troubleshooting/known-issues#moving_vms_or_disks_using_the_moveinstance_api_or_the_causes_unexpected_behavior. - - Please note that gcloud compute instances move does not yet support - instances which have regional persistent disks attached. Please see - https://cloud.google.com/compute/docs/disks/regional-persistent-disk for - more details. - -EXAMPLES - To move instance-1 from us-central-a to europe-west1-d, run: - - $ gcloud beta compute instances move instance-1 \ - --zone=us-central1-a --destination-zone=europe-west1-d - -POSITIONAL ARGUMENTS - INSTANCE_NAME - Name of the instance to operate on. For details on valid instance - names, refer to the criteria documented under the field 'name' at: - https://cloud.google.com/compute/docs/reference/rest/v1/instances - -REQUIRED FLAGS - --destination-zone=DESTINATION_ZONE - The zone to move the instance to. - -OPTIONAL FLAGS - --async - Return immediately, without waiting for the operation in progress to - complete. - - --zone=ZONE - Zone of the instance to operate on. If not specified, you might be - prompted to select a zone (interactive mode only). gcloud attempts to - identify the appropriate zone by searching for resources in your - currently active project. If the zone cannot be determined, gcloud - prompts you for a selection with all available Google Cloud Platform - zones. - - To avoid prompting when this flag is omitted, the user can set the - compute/zone property: - - $ gcloud config set compute/zone ZONE - - A list of zones can be fetched by running: - - $ gcloud compute zones list - - To unset the property, run: - - $ gcloud config unset compute/zone - - Alternatively, the zone can be stored in the environment variable - CLOUDSDK_COMPUTE_ZONE. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --configuration, --flags-file, --flatten, --format, - --help, --impersonate-service-account, --log-http, --project, --quiet, - --trace-token, --user-output-enabled, --verbosity. - - Run $ gcloud help for details. - -NOTES - This command is currently in beta and might change without notice. These - variants are also available: - - $ gcloud compute instances move - - $ gcloud alpha compute instances move - diff --git a/gcloud/beta/compute/interconnects/cross-site-networks/create b/gcloud/beta/compute/interconnects/cross-site-networks/create index 3f0c9c862..c32a513bb 100644 --- a/gcloud/beta/compute/interconnects/cross-site-networks/create +++ b/gcloud/beta/compute/interconnects/cross-site-networks/create @@ -16,8 +16,7 @@ EXAMPLES To create a cross site network, run: $ gcloud beta compute interconnects cross-site-networks create \ - example-cross-site-network --project=my-project \ - --description="Example cross site network" + example-csn --description="Example cross site network" POSITIONAL ARGUMENTS NAME @@ -36,8 +35,10 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud compute interconnects cross-site-networks create $ gcloud alpha compute interconnects cross-site-networks create diff --git a/gcloud/beta/compute/interconnects/cross-site-networks/delete b/gcloud/beta/compute/interconnects/cross-site-networks/delete index 3cb9deb41..f2ce189b9 100644 --- a/gcloud/beta/compute/interconnects/cross-site-networks/delete +++ b/gcloud/beta/compute/interconnects/cross-site-networks/delete @@ -7,8 +7,19 @@ SYNOPSIS [NAME ...] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) gcloud beta compute interconnects cross-site-networks delete deletes - Compute Engine cross site networks. + (BETA) gcloud beta compute interconnects cross-site-networks delete is used + to delete cross site networks. + + For an example, refer to the EXAMPLES section below. + +EXAMPLES + To delete a cross site network, run: + + $ gcloud beta compute interconnects cross-site-networks delete \ + example-csn + + Although not shown in this example, you can delete multiple cross site + networks in a single command. POSITIONAL ARGUMENTS NAME [NAME ...] @@ -23,8 +34,10 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud compute interconnects cross-site-networks delete $ gcloud alpha compute interconnects cross-site-networks delete diff --git a/gcloud/beta/compute/interconnects/cross-site-networks/describe b/gcloud/beta/compute/interconnects/cross-site-networks/describe index d576c0257..6dff074c1 100644 --- a/gcloud/beta/compute/interconnects/cross-site-networks/describe +++ b/gcloud/beta/compute/interconnects/cross-site-networks/describe @@ -7,9 +7,16 @@ SYNOPSIS [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) gcloud beta compute interconnects cross-site-networks describe - displays all data associated with Compute Engine cross site network in a - project. + (BETA) gcloud beta compute interconnects cross-site-networks describe is + used to describe a cross site network. + + For an example, refer to the EXAMPLES section below. + +EXAMPLES + To describe a cross site network, run: + + $ gcloud beta compute interconnects cross-site-networks describe \ + example-csn POSITIONAL ARGUMENTS NAME @@ -24,8 +31,10 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud compute interconnects cross-site-networks describe $ gcloud alpha compute interconnects cross-site-networks describe diff --git a/gcloud/beta/compute/interconnects/cross-site-networks/help b/gcloud/beta/compute/interconnects/cross-site-networks/help index f08eca5fa..b6770b233 100644 --- a/gcloud/beta/compute/interconnects/cross-site-networks/help +++ b/gcloud/beta/compute/interconnects/cross-site-networks/help @@ -33,8 +33,10 @@ COMMANDS (BETA) Update a Compute Engine cross site network. NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud compute interconnects cross-site-networks $ gcloud alpha compute interconnects cross-site-networks diff --git a/gcloud/beta/compute/interconnects/cross-site-networks/list b/gcloud/beta/compute/interconnects/cross-site-networks/list index cad2d1967..fe5564b38 100644 --- a/gcloud/beta/compute/interconnects/cross-site-networks/list +++ b/gcloud/beta/compute/interconnects/cross-site-networks/list @@ -61,8 +61,10 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud compute interconnects cross-site-networks list $ gcloud alpha compute interconnects cross-site-networks list diff --git a/gcloud/beta/compute/interconnects/cross-site-networks/update b/gcloud/beta/compute/interconnects/cross-site-networks/update index 5c4706bbb..a632f4e1e 100644 --- a/gcloud/beta/compute/interconnects/cross-site-networks/update +++ b/gcloud/beta/compute/interconnects/cross-site-networks/update @@ -8,8 +8,15 @@ SYNOPSIS DESCRIPTION (BETA) gcloud beta compute interconnects cross-site-networks update is used - to update cross site networks. A cross site network encapsulates wire - groups. + to update cross site networks. + + For an example, refer to the EXAMPLES section below. + +EXAMPLES + To update a cross site network's description, run: + + $ gcloud beta compute interconnects cross-site-networks update \ + example-csn --description="New description" POSITIONAL ARGUMENTS NAME @@ -28,8 +35,10 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud compute interconnects cross-site-networks update $ gcloud alpha compute interconnects cross-site-networks update diff --git a/gcloud/beta/compute/interconnects/wire-groups/add-endpoint b/gcloud/beta/compute/interconnects/wire-groups/add-endpoint index 057c48bbf..dfb96deb9 100644 --- a/gcloud/beta/compute/interconnects/wire-groups/add-endpoint +++ b/gcloud/beta/compute/interconnects/wire-groups/add-endpoint @@ -14,12 +14,11 @@ DESCRIPTION For an example, refer to the EXAMPLES section below. EXAMPLES - To add endpoint example-endpoint to wire group example-wire-group, run: + To add an endpoint to a wire group, run: $ gcloud beta compute interconnects wire-groups add-endpoint \ - example-wire-group --project=example-project \ - --cross-site-network=example-cross-site-network \ - --endpoint-label=example-endpoint + example-wg --cross-site-network=example-csn \ + --endpoint-label=endpoint-1 POSITIONAL ARGUMENTS NAME @@ -41,8 +40,10 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud compute interconnects wire-groups add-endpoint $ gcloud alpha compute interconnects wire-groups add-endpoint diff --git a/gcloud/beta/compute/interconnects/wire-groups/add-interconnect b/gcloud/beta/compute/interconnects/wire-groups/add-interconnect index 290ae8ada..8b9bb52fc 100644 --- a/gcloud/beta/compute/interconnects/wire-groups/add-interconnect +++ b/gcloud/beta/compute/interconnects/wire-groups/add-interconnect @@ -15,15 +15,13 @@ DESCRIPTION For an example, refer to the EXAMPLES section below. EXAMPLES - To add an interconnect example-interconnect to wire group - example-wire-group, run: + To add an interconnect to a wire group, run: $ gcloud beta compute interconnects wire-groups add-interconnect \ - example-wire-group --project=example-project \ - --cross-site-network=example-cross-site-network \ - --endpoint-label=example-endpoint \ - --interconnect-label=example-interconnect \ - --interconnect=some-interconnect-uri --vlan-tags=111,222 + example-wg --cross-site-network=example-csn \ + --endpoint-label=endpoint-1 \ + --interconnect-label=interconnect-1 \ + --interconnect=example-interconnect --vlan-tags=111 POSITIONAL ARGUMENTS NAME @@ -54,8 +52,10 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud compute interconnects wire-groups add-interconnect $ gcloud alpha compute interconnects wire-groups add-interconnect diff --git a/gcloud/beta/compute/interconnects/wire-groups/create b/gcloud/beta/compute/interconnects/wire-groups/create index d9d6d3675..862042e82 100644 --- a/gcloud/beta/compute/interconnects/wire-groups/create +++ b/gcloud/beta/compute/interconnects/wire-groups/create @@ -21,10 +21,8 @@ DESCRIPTION EXAMPLES To create a wire group, run: - $ gcloud beta compute interconnects wire-groups create \ - example-wire-group --project my-project \ - --cross-site-network example-cross-site-network \ - --bandwidth-unmetered 1 + $ gcloud beta compute interconnects wire-groups create example-wg \ + --cross-site-network=example-csn --bandwidth-unmetered=1 POSITIONAL ARGUMENTS NAME @@ -93,8 +91,10 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud compute interconnects wire-groups create $ gcloud alpha compute interconnects wire-groups create diff --git a/gcloud/beta/compute/interconnects/wire-groups/delete b/gcloud/beta/compute/interconnects/wire-groups/delete index c63b11f7b..e0fb2216d 100644 --- a/gcloud/beta/compute/interconnects/wire-groups/delete +++ b/gcloud/beta/compute/interconnects/wire-groups/delete @@ -7,8 +7,16 @@ SYNOPSIS --cross-site-network=CROSS_SITE_NETWORK [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) gcloud beta compute interconnects wire-groups delete deletes Compute - Engine wire groups. + (BETA) gcloud beta compute interconnects wire-groups delete is used to + delete wire groups. + + For an example, refer to the EXAMPLES section below. + +EXAMPLES + To delete a wire group, run: + + $ gcloud beta compute interconnects wire-groups delete example-wg \ + --cross-site-network=example-csn POSITIONAL ARGUMENTS NAME [NAME ...] @@ -27,8 +35,10 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud compute interconnects wire-groups delete $ gcloud alpha compute interconnects wire-groups delete diff --git a/gcloud/beta/compute/interconnects/wire-groups/describe b/gcloud/beta/compute/interconnects/wire-groups/describe index 3c1a56c09..2b1e2efb8 100644 --- a/gcloud/beta/compute/interconnects/wire-groups/describe +++ b/gcloud/beta/compute/interconnects/wire-groups/describe @@ -7,8 +7,16 @@ SYNOPSIS --cross-site-network=CROSS_SITE_NETWORK [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) gcloud beta compute interconnects wire-groups describe displays all - data associated with Compute Engine wire group in a project. + (BETA) gcloud beta compute interconnects wire-groups describe is used to + describe a wire group. + + For an example, refer to the EXAMPLES section below. + +EXAMPLES + To describe a wire group, run: + + $ gcloud beta compute interconnects wire-groups describe \ + example-wg --cross-site-network=example-csn POSITIONAL ARGUMENTS NAME @@ -27,8 +35,10 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud compute interconnects wire-groups describe $ gcloud alpha compute interconnects wire-groups describe diff --git a/gcloud/beta/compute/interconnects/wire-groups/help b/gcloud/beta/compute/interconnects/wire-groups/help index 26e41addf..99924531e 100644 --- a/gcloud/beta/compute/interconnects/wire-groups/help +++ b/gcloud/beta/compute/interconnects/wire-groups/help @@ -45,8 +45,10 @@ COMMANDS (BETA) Update a Compute Engine wire group. NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud compute interconnects wire-groups $ gcloud alpha compute interconnects wire-groups diff --git a/gcloud/beta/compute/interconnects/wire-groups/list b/gcloud/beta/compute/interconnects/wire-groups/list index d9c08cc6a..a49fd36d7 100644 --- a/gcloud/beta/compute/interconnects/wire-groups/list +++ b/gcloud/beta/compute/interconnects/wire-groups/list @@ -66,8 +66,10 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud compute interconnects wire-groups list $ gcloud alpha compute interconnects wire-groups list diff --git a/gcloud/beta/compute/interconnects/wire-groups/remove-endpoint b/gcloud/beta/compute/interconnects/wire-groups/remove-endpoint index f7028f847..f7e371355 100644 --- a/gcloud/beta/compute/interconnects/wire-groups/remove-endpoint +++ b/gcloud/beta/compute/interconnects/wire-groups/remove-endpoint @@ -14,13 +14,11 @@ DESCRIPTION For an example, refer to the EXAMPLES section below. EXAMPLES - To remove endpoint example-endpoint from wire group example-wire-group, - run: + To remove an endpoint from a wire group, run: $ gcloud beta compute interconnects wire-groups remove-endpoint \ - example-wire-group --project=example-project \ - --cross-site-network=example-cross-site-network \ - --endpoint-label=example-endpoint + example-wg --cross-site-network=example-csn \ + --endpoint-label=endpoint-1 POSITIONAL ARGUMENTS NAME @@ -42,8 +40,10 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud compute interconnects wire-groups remove-endpoint $ gcloud alpha compute interconnects wire-groups remove-endpoint diff --git a/gcloud/beta/compute/interconnects/wire-groups/remove-interconnect b/gcloud/beta/compute/interconnects/wire-groups/remove-interconnect index 709326fdb..695c0b0d1 100644 --- a/gcloud/beta/compute/interconnects/wire-groups/remove-interconnect +++ b/gcloud/beta/compute/interconnects/wire-groups/remove-interconnect @@ -14,14 +14,11 @@ DESCRIPTION For an example, refer to the EXAMPLES section below. EXAMPLES - To remove an interconnect example-interconnect from wire group - example-wire-group, run: + To remove an interconnect from a wire group endpoint, run: $ gcloud beta compute interconnects wire-groups \ - remove-interconnect example-wire-group \ - --project=example-project \ - --cross-site-network=example-cross-site-network \ - --endpoint-label=example-endpoint \ + remove-interconnect example-wg \ + --cross-site-network=example-csn --endpoint-label=endpoint-1 \ --interconnect-label=example-interconnect POSITIONAL ARGUMENTS @@ -47,8 +44,10 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud compute interconnects wire-groups remove-interconnect $ gcloud alpha compute interconnects wire-groups remove-interconnect diff --git a/gcloud/beta/compute/interconnects/wire-groups/update b/gcloud/beta/compute/interconnects/wire-groups/update index 56bc84095..e733cd501 100644 --- a/gcloud/beta/compute/interconnects/wire-groups/update +++ b/gcloud/beta/compute/interconnects/wire-groups/update @@ -12,7 +12,36 @@ SYNOPSIS DESCRIPTION (BETA) gcloud beta compute interconnects wire-groups update is used to - update wire groups. A wire group represents a group of redundant wires. + update wire groups. + + For an example, refer to the EXAMPLES section below. + +EXAMPLES + To disable a wire group, run: + + $ gcloud beta compute interconnects wire-groups update example-wg \ + --cross-site-network=example-csn --no-admin-enabled + + To change a wire group's unmetered bandwidth, run: + + $ gcloud beta compute interconnects wire-groups update example-wg \ + --cross-site-network=example-csn --bandwidth-unmetered=5 + + To enable automatic failure detection for a wire group, run: + + $ gcloud beta compute interconnects wire-groups update example-wg \ + --cross-site-network=example-csn --fault-response=DISABLE_PORT + + To enable bandwidth sharing for a wire group, run: + + $ gcloud beta compute interconnects wire-groups update example-wg \ + --cross-site-network=example-csn \ + --bandwidth-allocation=SHARED_WITH_WIRE_GROUP + + To update a wire group's description, run: + + $ gcloud beta compute interconnects wire-groups update example-wg \ + --cross-site-network=example-csn --description="new description" POSITIONAL ARGUMENTS NAME @@ -80,8 +109,10 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud compute interconnects wire-groups update $ gcloud alpha compute interconnects wire-groups update diff --git a/gcloud/beta/compute/org-security-policies/associations/create b/gcloud/beta/compute/org-security-policies/associations/create index dafdf4846..3ab8a6bc2 100644 --- a/gcloud/beta/compute/org-security-policies/associations/create +++ b/gcloud/beta/compute/org-security-policies/associations/create @@ -73,8 +73,10 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud compute org-security-policies associations create $ gcloud alpha compute org-security-policies associations create diff --git a/gcloud/beta/compute/org-security-policies/associations/delete b/gcloud/beta/compute/org-security-policies/associations/delete index 061fb41c9..b0f7b08cf 100644 --- a/gcloud/beta/compute/org-security-policies/associations/delete +++ b/gcloud/beta/compute/org-security-policies/associations/delete @@ -40,8 +40,10 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud compute org-security-policies associations delete $ gcloud alpha compute org-security-policies associations delete diff --git a/gcloud/beta/compute/org-security-policies/associations/help b/gcloud/beta/compute/org-security-policies/associations/help index 1226bf229..6e2e0dd84 100644 --- a/gcloud/beta/compute/org-security-policies/associations/help +++ b/gcloud/beta/compute/org-security-policies/associations/help @@ -30,8 +30,10 @@ COMMANDS (BETA) List the associations of an organization or folder resource. NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud compute org-security-policies associations $ gcloud alpha compute org-security-policies associations diff --git a/gcloud/beta/compute/org-security-policies/associations/list b/gcloud/beta/compute/org-security-policies/associations/list index 2cb640225..b2a8da8de 100644 --- a/gcloud/beta/compute/org-security-policies/associations/list +++ b/gcloud/beta/compute/org-security-policies/associations/list @@ -68,8 +68,10 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud compute org-security-policies associations list $ gcloud alpha compute org-security-policies associations list diff --git a/gcloud/beta/compute/org-security-policies/copy-rules b/gcloud/beta/compute/org-security-policies/copy-rules index e7faf5e17..477049eea 100644 --- a/gcloud/beta/compute/org-security-policies/copy-rules +++ b/gcloud/beta/compute/org-security-policies/copy-rules @@ -43,8 +43,10 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud compute org-security-policies copy-rules $ gcloud alpha compute org-security-policies copy-rules diff --git a/gcloud/beta/compute/org-security-policies/create b/gcloud/beta/compute/org-security-policies/create index b738bf8ce..0e49fc128 100644 --- a/gcloud/beta/compute/org-security-policies/create +++ b/gcloud/beta/compute/org-security-policies/create @@ -75,8 +75,10 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud compute org-security-policies create $ gcloud alpha compute org-security-policies create diff --git a/gcloud/beta/compute/org-security-policies/delete b/gcloud/beta/compute/org-security-policies/delete index f2806fa00..1fe74d31d 100644 --- a/gcloud/beta/compute/org-security-policies/delete +++ b/gcloud/beta/compute/org-security-policies/delete @@ -34,8 +34,10 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud compute org-security-policies delete $ gcloud alpha compute org-security-policies delete diff --git a/gcloud/beta/compute/org-security-policies/describe b/gcloud/beta/compute/org-security-policies/describe index 785fa7f96..00662095a 100644 --- a/gcloud/beta/compute/org-security-policies/describe +++ b/gcloud/beta/compute/org-security-policies/describe @@ -34,8 +34,10 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud compute org-security-policies describe $ gcloud alpha compute org-security-policies describe diff --git a/gcloud/beta/compute/org-security-policies/help b/gcloud/beta/compute/org-security-policies/help index b8c52d178..4a87fc799 100644 --- a/gcloud/beta/compute/org-security-policies/help +++ b/gcloud/beta/compute/org-security-policies/help @@ -55,8 +55,10 @@ COMMANDS (BETA) Update a Compute Engine organization security policy. NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud compute org-security-policies $ gcloud alpha compute org-security-policies diff --git a/gcloud/beta/compute/org-security-policies/list b/gcloud/beta/compute/org-security-policies/list index c2bcef973..a04e35a1f 100644 --- a/gcloud/beta/compute/org-security-policies/list +++ b/gcloud/beta/compute/org-security-policies/list @@ -85,8 +85,10 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud compute org-security-policies list $ gcloud alpha compute org-security-policies list diff --git a/gcloud/beta/compute/org-security-policies/list-rules b/gcloud/beta/compute/org-security-policies/list-rules index c23391571..6cfb312c6 100644 --- a/gcloud/beta/compute/org-security-policies/list-rules +++ b/gcloud/beta/compute/org-security-policies/list-rules @@ -99,8 +99,10 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud compute org-security-policies list-rules $ gcloud alpha compute org-security-policies list-rules diff --git a/gcloud/beta/compute/org-security-policies/move b/gcloud/beta/compute/org-security-policies/move index d415f3823..19ff47606 100644 --- a/gcloud/beta/compute/org-security-policies/move +++ b/gcloud/beta/compute/org-security-policies/move @@ -38,8 +38,10 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud compute org-security-policies move $ gcloud alpha compute org-security-policies move diff --git a/gcloud/beta/compute/org-security-policies/rules/add-preconfig-waf-exclusion b/gcloud/beta/compute/org-security-policies/rules/add-preconfig-waf-exclusion index ac676a135..ebfff5438 100644 --- a/gcloud/beta/compute/org-security-policies/rules/add-preconfig-waf-exclusion +++ b/gcloud/beta/compute/org-security-policies/rules/add-preconfig-waf-exclusion @@ -138,8 +138,11 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud compute org-security-policies rules \ + add-preconfig-waf-exclusion $ gcloud alpha compute org-security-policies rules \ add-preconfig-waf-exclusion diff --git a/gcloud/beta/compute/org-security-policies/rules/create b/gcloud/beta/compute/org-security-policies/rules/create index e1a5696f6..67fbe8be7 100644 --- a/gcloud/beta/compute/org-security-policies/rules/create +++ b/gcloud/beta/compute/org-security-policies/rules/create @@ -114,8 +114,10 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud compute org-security-policies rules create $ gcloud alpha compute org-security-policies rules create diff --git a/gcloud/beta/compute/org-security-policies/rules/delete b/gcloud/beta/compute/org-security-policies/rules/delete index ad64c5392..a989faf4b 100644 --- a/gcloud/beta/compute/org-security-policies/rules/delete +++ b/gcloud/beta/compute/org-security-policies/rules/delete @@ -41,8 +41,10 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud compute org-security-policies rules delete $ gcloud alpha compute org-security-policies rules delete diff --git a/gcloud/beta/compute/org-security-policies/rules/describe b/gcloud/beta/compute/org-security-policies/rules/describe index 1a1bb09d4..02e56286d 100644 --- a/gcloud/beta/compute/org-security-policies/rules/describe +++ b/gcloud/beta/compute/org-security-policies/rules/describe @@ -41,8 +41,10 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud compute org-security-policies rules describe $ gcloud alpha compute org-security-policies rules describe diff --git a/gcloud/beta/compute/org-security-policies/rules/help b/gcloud/beta/compute/org-security-policies/rules/help index 142657b5c..36a96d144 100644 --- a/gcloud/beta/compute/org-security-policies/rules/help +++ b/gcloud/beta/compute/org-security-policies/rules/help @@ -39,8 +39,10 @@ COMMANDS (BETA) Update a Compute Engine security policy rule. NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud compute org-security-policies rules $ gcloud alpha compute org-security-policies rules diff --git a/gcloud/beta/compute/org-security-policies/rules/remove-preconfig-waf-exclusion b/gcloud/beta/compute/org-security-policies/rules/remove-preconfig-waf-exclusion index 215861335..6f5e1d08c 100644 --- a/gcloud/beta/compute/org-security-policies/rules/remove-preconfig-waf-exclusion +++ b/gcloud/beta/compute/org-security-policies/rules/remove-preconfig-waf-exclusion @@ -157,8 +157,11 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud compute org-security-policies rules \ + remove-preconfig-waf-exclusion $ gcloud alpha compute org-security-policies rules \ remove-preconfig-waf-exclusion diff --git a/gcloud/beta/compute/org-security-policies/rules/update b/gcloud/beta/compute/org-security-policies/rules/update index 37fe7df7a..ebcc3325f 100644 --- a/gcloud/beta/compute/org-security-policies/rules/update +++ b/gcloud/beta/compute/org-security-policies/rules/update @@ -120,8 +120,10 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud compute org-security-policies rules update $ gcloud alpha compute org-security-policies rules update diff --git a/gcloud/beta/compute/org-security-policies/update b/gcloud/beta/compute/org-security-policies/update index 7738a12f1..4a7b163da 100644 --- a/gcloud/beta/compute/org-security-policies/update +++ b/gcloud/beta/compute/org-security-policies/update @@ -64,8 +64,10 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud compute org-security-policies update $ gcloud alpha compute org-security-policies update diff --git a/gcloud/beta/compute/preview-features/describe b/gcloud/beta/compute/preview-features/describe index fe5987bce..92affe7ab 100644 --- a/gcloud/beta/compute/preview-features/describe +++ b/gcloud/beta/compute/preview-features/describe @@ -47,8 +47,10 @@ API REFERENCE can be found at: https://cloud.google.com/compute/ NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud compute preview-features describe $ gcloud alpha compute preview-features describe diff --git a/gcloud/beta/compute/preview-features/help b/gcloud/beta/compute/preview-features/help index 3aa91bd6f..7fc8ff5af 100644 --- a/gcloud/beta/compute/preview-features/help +++ b/gcloud/beta/compute/preview-features/help @@ -26,8 +26,10 @@ COMMANDS (BETA) Update a preview feature's activation status. NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud compute preview-features $ gcloud alpha compute preview-features diff --git a/gcloud/beta/compute/preview-features/list b/gcloud/beta/compute/preview-features/list index 3b470ac32..efd833627 100644 --- a/gcloud/beta/compute/preview-features/list +++ b/gcloud/beta/compute/preview-features/list @@ -59,8 +59,10 @@ API REFERENCE can be found at: https://cloud.google.com/compute/ NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud compute preview-features list $ gcloud alpha compute preview-features list diff --git a/gcloud/beta/compute/preview-features/update b/gcloud/beta/compute/preview-features/update index 982145e47..152e50919 100644 --- a/gcloud/beta/compute/preview-features/update +++ b/gcloud/beta/compute/preview-features/update @@ -66,8 +66,10 @@ API REFERENCE can be found at: https://cloud.google.com/compute/ NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud compute preview-features update $ gcloud alpha compute preview-features update diff --git a/gcloud/beta/compute/reservations/sub-blocks/help b/gcloud/beta/compute/reservations/sub-blocks/help index 19e463ce8..45b152395 100644 --- a/gcloud/beta/compute/reservations/sub-blocks/help +++ b/gcloud/beta/compute/reservations/sub-blocks/help @@ -25,6 +25,9 @@ COMMANDS perform-maintenance (BETA) Perform maintenance on a reservation sub-block. + report-subblock-as-faulty + (BETA) Report a sub-block within a reservation as faulty. + NOTES This command is currently in beta and might change without notice. These variants are also available: diff --git a/gcloud/beta/compute/reservations/sub-blocks/report-subblock-as-faulty b/gcloud/beta/compute/reservations/sub-blocks/report-subblock-as-faulty new file mode 100644 index 000000000..e5fb8905a --- /dev/null +++ b/gcloud/beta/compute/reservations/sub-blocks/report-subblock-as-faulty @@ -0,0 +1,99 @@ +NAME + gcloud beta compute reservations sub-blocks report-subblock-as-faulty - + report a sub-block within a reservation as faulty + +SYNOPSIS + gcloud beta compute reservations sub-blocks report-subblock-as-faulty + RESERVATION --block-name=BLOCK_NAME + --disruption-schedule=DISRUPTION_SCHEDULE + --failure-component=FAILURE_COMPONENT + --fault-reasons=[behavior=BEHAVIOR],[description=DESCRIPTION] + --sub-block-name=SUB_BLOCK_NAME [--zone=ZONE] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Report a sub-block within a reservation as faulty. + +EXAMPLES + To report reservation exr-1 in ZONE with block name block-1 and sub block + name sub-block-1 as faulty, run: + + $ gcloud beta compute reservations sub-blocks \ + report-subblock-as-faulty exr-1 --zone=ZONE \ + --block-name=block-1 --sub-block-name=sub-block-1 \ + --disruption-schedule=IMMEDIATE \ + --fault-reasons=behavior=PERFORMANCE,description="performance \ + issues" --failure-component=NVLINK_SWITCH + +POSITIONAL ARGUMENTS + RESERVATION + The name of the reservation containing the sub-block to report as + faulty + +REQUIRED FLAGS + --block-name=BLOCK_NAME + The name of the reservation block. + + --disruption-schedule=DISRUPTION_SCHEDULE + The disruption schedule for the sub-block. DISRUPTION_SCHEDULE must be + (only one value is supported): + + IMMEDIATE + All VMs are immediately disrupted. + + --failure-component=FAILURE_COMPONENT + The component that experienced the fault. FAILURE_COMPONENT must be one + of: + + MULTIPLE_FAULTY_HOSTS + Multiple hosts experienced the fault. + NVLINK_SWITCH + The NVLink switch experienced the fault. + + --fault-reasons=[behavior=BEHAVIOR],[description=DESCRIPTION] + The reasons for reporting the sub-block as faulty. You can repeat this + flag. Each flag must specify a "behavior" attribute and can optionally + include a "description" attribute. The possible values for "behavior" + are: PERFORMANCE, SWITCH_FAILURE, GPU_ERROR. + + --sub-block-name=SUB_BLOCK_NAME + The name of the reservation sub block. + +OPTIONAL FLAGS + --zone=ZONE + Zone of the reservation to report-subblock-as-faulty. If not specified + and the compute/zone property isn't set, you might be prompted to + select a zone (interactive mode only). + + To avoid prompting when this flag is omitted, you can set the + compute/zone property: + + $ gcloud config set compute/zone ZONE + + A list of zones can be fetched by running: + + $ gcloud compute zones list + + To unset the property, run: + + $ gcloud config unset compute/zone + + Alternatively, the zone can be stored in the environment variable + CLOUDSDK_COMPUTE_ZONE. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud compute reservations sub-blocks report-subblock-as-faulty + + $ gcloud alpha compute reservations sub-blocks \ + report-subblock-as-faulty + diff --git a/gcloud/beta/compute/tpus/create b/gcloud/beta/compute/tpus/create deleted file mode 100644 index 8b0704a1f..000000000 --- a/gcloud/beta/compute/tpus/create +++ /dev/null @@ -1,142 +0,0 @@ -NAME - gcloud beta compute tpus create - create a new Cloud TPU - -SYNOPSIS - gcloud beta compute tpus create (TPU : --zone=ZONE) --version=VERSION - [--accelerator-type=ACCELERATOR_TYPE; default="v2-8"] [--async] - [--description=DESCRIPTION] [--network=NETWORK; default="default"] - [--preemptible] [--range=RANGE] [--reserved] [--use-service-networking] - [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (BETA) (DEPRECATED) This command is being deprecated. Please use gcloud - compute tpus tpu-vm create instead. - - Create a new Cloud TPU. - -EXAMPLES - The following command creates a TPU with ID my-tpu in the default user - project, network and compute/region (with other defaults supplied by API): - - $ gcloud beta compute tpus create my-tpu - - The following command creates a TPU with ID my-tpu with explicit values for - all required and optional parameters: - - $ gcloud beta compute tpus create my-tpu --zone=us-central1-a \ - --range='10.240.0.0/29' --accelerator-type='v2-8' \ - --network=my-tf-network --description='My TF Node' \ - --version='1.1' - -POSITIONAL ARGUMENTS - Tpu resource - The Cloud TPU you want to create. The arguments in this - group can be used to specify the attributes of this resource. (NOTE) Some - attributes are not given arguments in this group but can be set in other - ways. - - To set the project attribute: - ◆ provide the argument tpu on the command line with a fully specified - name; - ◆ provide the argument --project on the command line; - ◆ set the property core/project. - - This must be specified. - - TPU - ID of the tpu or fully qualified identifier for the tpu. - - To set the tpu attribute: - ▸ provide the argument tpu on the command line. - - This positional argument must be specified if any of the other - arguments in this group are specified. - - --zone=ZONE - The compute/zone of the Cloud TPU. - - If not specified, will use default compute/zone. - - To set the zone attribute: - ▸ provide the argument tpu on the command line with a fully - specified name; - ▸ provide the argument --zone on the command line; - ▸ set the property compute/zone. - -REQUIRED FLAGS - --version=VERSION - TensorFlow version for the TPU, such as 1.14. For a list of available - TensorFlow versions please see https://www.tensorflow.org/versions/. - -OPTIONAL FLAGS - --accelerator-type=ACCELERATOR_TYPE; default="v2-8" - TPU accelerator type for the TPU. If not specified, this defaults to - v2-8. - - For a list of available accelerator types run: - - gcloud beta compute tpus accelerator-types list - - --async - Return immediately, without waiting for the operation in progress to - complete. - - --description=DESCRIPTION - Specifies a text description of the TPU. - - --network=NETWORK; default="default" - Specifies the network that this TPU will be a part of. - - --preemptible - If provided, the TPU will be preemptible and time-limited. It may be - preempted to free up resources for standard TPUs, and will only be able - to run for a limited amount of time. - - Preemptible TPUs cannot be restarted. - - --range=RANGE - CIDR Range for the TPU. - - The IP range that the TPU will select an IP address from. Must be in - CIDR notation and a /29 range, for example 192.168.0.0/29. Errors will - occur if the CIDR range has already been used for a currently existing - TPU, the CIDR range conflicts with any networks in the user's provided - network, or the provided network is peered with another network that is - using that CIDR range. - - --reserved - When specified, will attempt to create the TPU node under reservations - made in the current project. The reservations can be made separately - but used in aggregated form. i.e., the user can make a reservation of - 128 V2 TPUs and later on make another reservation of 128 V2 TPUs then - creates a v2-256 TPU instance. If there exists no reservation or not - sufficient amount of reserved cores under the project, the request will - fail due to lack of capacity. - - --use-service-networking - If provided, the TPU will be configured via the Service Networking (SN) - API instead of using a CIDR range. The Service Networking API should be - enabled on the project before creating the TPU. - - For more information on Service Networking see - https://cloud.google.com/service-infrastructure/docs/service-networking/getting-started. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --configuration, --flags-file, --flatten, --format, - --help, --impersonate-service-account, --log-http, --project, --quiet, - --trace-token, --user-output-enabled, --verbosity. - - Run $ gcloud help for details. - -API REFERENCE - This command uses the tpu/v1 API. The full documentation for this API can - be found at: https://cloud.google.com/tpu/ - -NOTES - This command is currently in beta and might change without notice. These - variants are also available: - - $ gcloud compute tpus create - - $ gcloud alpha compute tpus create - diff --git a/gcloud/beta/compute/tpus/delete b/gcloud/beta/compute/tpus/delete deleted file mode 100644 index 78eaee343..000000000 --- a/gcloud/beta/compute/tpus/delete +++ /dev/null @@ -1,77 +0,0 @@ -NAME - gcloud beta compute tpus delete - deletes a Cloud TPU - -SYNOPSIS - gcloud beta compute tpus delete (TPU : --zone=ZONE) [--async] - [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (BETA) (DEPRECATED) This command is being deprecated. Please use gcloud - compute tpus tpu-vm delete instead. - - Deletes a Cloud TPU. - -EXAMPLES - The following command deletes a TPU with ID my-tpu in zone us-central1-b: - - $ gcloud beta compute tpus delete my-tpu --zone=us-central1-b - -POSITIONAL ARGUMENTS - Tpu resource - The Cloud TPU you want to delete. The arguments in this - group can be used to specify the attributes of this resource. (NOTE) Some - attributes are not given arguments in this group but can be set in other - ways. - - To set the project attribute: - ◆ provide the argument tpu on the command line with a fully specified - name; - ◆ provide the argument --project on the command line; - ◆ set the property core/project. - - This must be specified. - - TPU - ID of the tpu or fully qualified identifier for the tpu. - - To set the tpu attribute: - ▸ provide the argument tpu on the command line. - - This positional argument must be specified if any of the other - arguments in this group are specified. - - --zone=ZONE - The compute/zone of the Cloud TPU. - - If not specified, will use default compute/zone. - - To set the zone attribute: - ▸ provide the argument tpu on the command line with a fully - specified name; - ▸ provide the argument --zone on the command line; - ▸ set the property compute/zone. - -FLAGS - --async - Return immediately, without waiting for the operation in progress to - complete. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --configuration, --flags-file, --flatten, --format, - --help, --impersonate-service-account, --log-http, --project, --quiet, - --trace-token, --user-output-enabled, --verbosity. - - Run $ gcloud help for details. - -API REFERENCE - This command uses the tpu/v1 API. The full documentation for this API can - be found at: https://cloud.google.com/tpu/ - -NOTES - This command is currently in beta and might change without notice. These - variants are also available: - - $ gcloud compute tpus delete - - $ gcloud alpha compute tpus delete - diff --git a/gcloud/beta/compute/tpus/describe b/gcloud/beta/compute/tpus/describe deleted file mode 100644 index d9e0d11a1..000000000 --- a/gcloud/beta/compute/tpus/describe +++ /dev/null @@ -1,72 +0,0 @@ -NAME - gcloud beta compute tpus describe - describe a Cloud TPU - -SYNOPSIS - gcloud beta compute tpus describe (TPU : --zone=ZONE) - [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (BETA) (DEPRECATED) This command is being deprecated. Please use gcloud - compute tpus tpu-vm describe instead. - - Describe a Cloud TPU. - -EXAMPLES - The following command describes a TPU with ID my-tpu in zone us-central1-b: - - $ gcloud beta compute tpus describe my-tpu --zone=us-central1-b - -POSITIONAL ARGUMENTS - Tpu resource - The Cloud TPU you want to describe. The arguments in this - group can be used to specify the attributes of this resource. (NOTE) Some - attributes are not given arguments in this group but can be set in other - ways. - - To set the project attribute: - ◆ provide the argument tpu on the command line with a fully specified - name; - ◆ provide the argument --project on the command line; - ◆ set the property core/project. - - This must be specified. - - TPU - ID of the tpu or fully qualified identifier for the tpu. - - To set the tpu attribute: - ▸ provide the argument tpu on the command line. - - This positional argument must be specified if any of the other - arguments in this group are specified. - - --zone=ZONE - The compute/zone of the Cloud TPU. - - If not specified, will use default compute/zone. - - To set the zone attribute: - ▸ provide the argument tpu on the command line with a fully - specified name; - ▸ provide the argument --zone on the command line; - ▸ set the property compute/zone. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --configuration, --flags-file, --flatten, --format, - --help, --impersonate-service-account, --log-http, --project, --quiet, - --trace-token, --user-output-enabled, --verbosity. - - Run $ gcloud help for details. - -API REFERENCE - This command uses the tpu/v1 API. The full documentation for this API can - be found at: https://cloud.google.com/tpu/ - -NOTES - This command is currently in beta and might change without notice. These - variants are also available: - - $ gcloud compute tpus describe - - $ gcloud alpha compute tpus describe - diff --git a/gcloud/beta/compute/tpus/execution-groups/create b/gcloud/beta/compute/tpus/execution-groups/create deleted file mode 100644 index 94174a690..000000000 --- a/gcloud/beta/compute/tpus/execution-groups/create +++ /dev/null @@ -1,163 +0,0 @@ -NAME - gcloud beta compute tpus execution-groups create - create Google Compute - TPUs along with VMs - -SYNOPSIS - gcloud beta compute tpus execution-groups create - [--accelerator-type=ACCELERATOR_TYPE; default="v2-8"] - [--disk-size=DISK_SIZE; default="250GB"] [--dry-run] [--forward-ports] - [--gce-image=GCE_IMAGE] - [--machine-type=MACHINE_TYPE; default="n1-standard-1"] [--name=NAME] - [--network=NETWORK; default="default"] [--preemptible] - [--preemptible-vm] [--tf-version=TF_VERSION] [--tpu-only] - [--use-dl-images] [--use-with-notebook] [--vm-only] [--zone=ZONE] - [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (BETA) (DEPRECATED) Create Google Compute TPUs along with VMs. - - This command is deprecated and will be removed in a future release. We - recommend that you use the TPU-VM or Queued Resource API. See - https://cloud.google.com/tpu/docs/managing-tpus-tpu-vm for more - information. - -EXAMPLES - To create both TPU and VM, run: - - $ gcloud beta compute tpus execution-groups create \ - --name=test-execution-group --zone=test-zone \ - --project=test-project --accelerator-type=v2-8 \ - --tf-version=2.4.1 - - To create both TPU and VM with additional flags, run: - - $ gcloud beta compute tpus execution-groups create \ - --name=test-execution-group --zone=test-zone \ - --project=test-project --accelerator-type=v2-8 \ - --tf-version=2.4.1 --network=default --preemptible-vm \ - --disk-size=100 --machine-type=n1-standard-2 --use-dl-images - - To create a VM only before creating the TPU, run: - - $ gcloud beta compute tpus execution-groups create \ - --name=test-execution-group-tpu-only --zone=test-zone \ - --project=test-project --accelerator-type=v2-8 \ - --tf-version=2.4.1 --tpu-only - - To create the TPU only after the VM has been created, run: - - $ gcloud beta compute tpus execution-groups create \ - --name=test-execution-group-tpu-only --zone=test-zone \ - --project=test-project --accelerator-type=v2-8 \ - --tf-version=2.4.1 --vm-only - -FLAGS - --accelerator-type=ACCELERATOR_TYPE; default="v2-8" - TPU accelerator type for the TPU. If not specified, this defaults to - v2-8. - - --disk-size=DISK_SIZE; default="250GB" - Configures the root volume size of your Compute Engine VM (in GB). The - minimum size is 20GB and the maximum is 2000GB. Specified value must be - an integer multiple of Gigabytes. - - --dry-run - Do not make changes; print only what would have happened. - - --forward-ports - Automatically forward useful ports from the Compute Engine VM to your - local machine. The ports forwarded are: 6006 (tensorboard), 8888 - (jupyter notebooks), 8470 (TPU port), 8466 (TPU profiler port). - - Enabled by default, use --no-forward-ports to disable. - - --gce-image=GCE_IMAGE - Override the automatically chosen Compute Engine Image. Use this flag - when you're using your own custom images instead of the provided ones - with TensorFlow pre-installed. - - --machine-type=MACHINE_TYPE; default="n1-standard-1" - Specifies the machine type used for the Compute Engine VM. To get a - list of available machine types, run 'gcloud compute machine-types - list'. If unspecified, the default type is n1-standard-1. - - --name=NAME - Override the name to use for VMs and TPUs (defaults to your username). - - --network=NETWORK; default="default" - Specifies the network the Cloud TPU and associated VM should be created - in. If unspecified, the network "default" is picked. - - --preemptible - Create a preemptible Cloud TPU, instead of a normal (non-preemptible) - Cloud TPU. A preemptible Cloud TPU costs less per hour, but the Cloud - TPU service can stop/terminate the node at any time. - - --preemptible-vm - Create a preemptible Compute Engine VM, instead of a normal - (non-preemptible) VM. A preemptible VM costs less per hour, but the - Compute Engine service can terminate the instance at any time. - - --tf-version=TF_VERSION - Set the version of TensorFlow to use when creating the Compute Engine - VM and the Cloud TPU. (It defaults to auto-selecting the latest stable - release.) - - --tpu-only - Do not allocate a VM, only allocate a TPU. To be used after the command - has been run with a --vm-only flag and the user is ready to run on a - TPU. Ensure that the name matches the name passed in when creating with - the --vm-only flag. - - --use-dl-images - Use Deep Learning VM Images (see docs - - https://cloud.google.com/deep-learning-vm/) instead of TPU-specific - machine images. Defaults to TPU-specific images. This value is set to - true automatically if the --use-with-notebook flag is set to true. - - --use-with-notebook - Allow Compute Engine VM to be recognized by Cloud AI Notebooks. This - automatically sets the content of the flag --use-dl-images flag to be - true. - - --vm-only - Do not allocate a TPU, only allocate a VM (useful if you're not ready - to run on a TPU yet). - - --zone=ZONE - Zone of the tpu to create. If not specified and the compute/zone - property isn't set, you might be prompted to select a zone (interactive - mode only). - - To avoid prompting when this flag is omitted, you can set the - compute/zone property: - - $ gcloud config set compute/zone ZONE - - A list of zones can be fetched by running: - - $ gcloud compute zones list - - To unset the property, run: - - $ gcloud config unset compute/zone - - Alternatively, the zone can be stored in the environment variable - CLOUDSDK_COMPUTE_ZONE. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --configuration, --flags-file, --flatten, --format, - --help, --impersonate-service-account, --log-http, --project, --quiet, - --trace-token, --user-output-enabled, --verbosity. - - Run $ gcloud help for details. - -NOTES - This command is currently in beta and might change without notice. These - variants are also available: - - $ gcloud compute tpus execution-groups create - - $ gcloud alpha compute tpus execution-groups create - diff --git a/gcloud/beta/compute/tpus/execution-groups/delete b/gcloud/beta/compute/tpus/execution-groups/delete deleted file mode 100644 index d56869fb5..000000000 --- a/gcloud/beta/compute/tpus/execution-groups/delete +++ /dev/null @@ -1,73 +0,0 @@ -NAME - gcloud beta compute tpus execution-groups delete - delete TPU Node + VM - created by execution group - -SYNOPSIS - gcloud beta compute tpus execution-groups delete EXECUTION_GROUP_NAME - [--tpu-only] [--zone=ZONE] [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (BETA) (DEPRECATED) Delete TPU Node + VM created by execution group. - - This command is deprecated and will be removed in a future release. We - recommend that you use the TPU-VM or Queued Resource API. See - https://cloud.google.com/tpu/docs/managing-tpus-tpu-vm for more - information. - -EXAMPLES - To delete both, the TPU and the VM, run: - - $ gcloud beta compute tpus execution-groups delete \ - test-execution-group --zone=test-zone --project=test-project - - To delete the TPU only, run: - - $ gcloud beta compute tpus execution-groups delete \ - test-execution-group --zone=test-zone --project=test-project \ - --tpu-only - -POSITIONAL ARGUMENTS - EXECUTION_GROUP_NAME - The execution group name to delete. - -FLAGS - --tpu-only - Do not delete VM, only delete the TPU. - - --zone=ZONE - Zone of the tpu to delete. If not specified and the compute/zone - property isn't set, you might be prompted to select a zone (interactive - mode only). - - To avoid prompting when this flag is omitted, you can set the - compute/zone property: - - $ gcloud config set compute/zone ZONE - - A list of zones can be fetched by running: - - $ gcloud compute zones list - - To unset the property, run: - - $ gcloud config unset compute/zone - - Alternatively, the zone can be stored in the environment variable - CLOUDSDK_COMPUTE_ZONE. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --configuration, --flags-file, --flatten, --format, - --help, --impersonate-service-account, --log-http, --project, --quiet, - --trace-token, --user-output-enabled, --verbosity. - - Run $ gcloud help for details. - -NOTES - This command is currently in beta and might change without notice. These - variants are also available: - - $ gcloud compute tpus execution-groups delete - - $ gcloud alpha compute tpus execution-groups delete - diff --git a/gcloud/beta/compute/tpus/execution-groups/describe b/gcloud/beta/compute/tpus/execution-groups/describe deleted file mode 100644 index 758dcb5ae..000000000 --- a/gcloud/beta/compute/tpus/execution-groups/describe +++ /dev/null @@ -1,64 +0,0 @@ -NAME - gcloud beta compute tpus execution-groups describe - describe Google - Compute TPU + VM combination - -SYNOPSIS - gcloud beta compute tpus execution-groups describe EXECUTION_GROUP_NAME - [--zone=ZONE] [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (BETA) (DEPRECATED) Describe Google Compute TPU + VM combination. - - This command is deprecated and will be removed in a future release. We - recommend that you use the TPU-VM or Queued Resource API. See - https://cloud.google.com/tpu/docs/managing-tpus-tpu-vm for more - information. - -EXAMPLES - To describe the TPU and VM combination, run: - - $ gcloud beta compute tpus execution-groups describe \ - test-execution-group --zone=test-zone --project=test-project - -POSITIONAL ARGUMENTS - EXECUTION_GROUP_NAME - The execution group name to delete. - -FLAGS - --zone=ZONE - Zone of the tpu to describe. If not specified and the compute/zone - property isn't set, you might be prompted to select a zone (interactive - mode only). - - To avoid prompting when this flag is omitted, you can set the - compute/zone property: - - $ gcloud config set compute/zone ZONE - - A list of zones can be fetched by running: - - $ gcloud compute zones list - - To unset the property, run: - - $ gcloud config unset compute/zone - - Alternatively, the zone can be stored in the environment variable - CLOUDSDK_COMPUTE_ZONE. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --configuration, --flags-file, --flatten, --format, - --help, --impersonate-service-account, --log-http, --project, --quiet, - --trace-token, --user-output-enabled, --verbosity. - - Run $ gcloud help for details. - -NOTES - This command is currently in beta and might change without notice. These - variants are also available: - - $ gcloud compute tpus execution-groups describe - - $ gcloud alpha compute tpus execution-groups describe - diff --git a/gcloud/beta/compute/tpus/execution-groups/help b/gcloud/beta/compute/tpus/execution-groups/help deleted file mode 100644 index 892996e21..000000000 --- a/gcloud/beta/compute/tpus/execution-groups/help +++ /dev/null @@ -1,50 +0,0 @@ -NAME - gcloud beta compute tpus execution-groups - command group that helps create - and manage Cloud TPUs and Compute VMs - -SYNOPSIS - gcloud beta compute tpus execution-groups COMMAND [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (BETA) (DEPRECATED) Command group that helps create and manage Cloud TPUs - and Compute VMs. - - This command group is deprecated and will be removed in a future release. - We recommend that you use the TPU-VM or Queued Resource API. See - https://cloud.google.com/tpu/docs/managing-tpus-tpu-vm for more - information. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --help. - - Run $ gcloud help for details. - -COMMANDS - COMMAND is one of the following: - - create - (BETA) (DEPRECATED) Create Google Compute TPUs along with VMs. - - delete - (BETA) (DEPRECATED) Delete TPU Node + VM created by execution group. - - describe - (BETA) (DEPRECATED) Describe Google Compute TPU + VM combination. - - list - (BETA) (DEPRECATED) List TPU Node+VM groups created by execution group. - - resume - (BETA) (DEPRECATED) Creates Google Compute TPU and resumes the VM. - - suspend - (BETA) (DEPRECATED) Deletes Google Compute TPU and suspends the VM. - -NOTES - This command is currently in beta and might change without notice. These - variants are also available: - - $ gcloud compute tpus execution-groups - - $ gcloud alpha compute tpus execution-groups - diff --git a/gcloud/beta/compute/tpus/execution-groups/resume b/gcloud/beta/compute/tpus/execution-groups/resume deleted file mode 100644 index 6086224c1..000000000 --- a/gcloud/beta/compute/tpus/execution-groups/resume +++ /dev/null @@ -1,89 +0,0 @@ -NAME - gcloud beta compute tpus execution-groups resume - creates Google Compute - TPU and resumes the VM - -SYNOPSIS - gcloud beta compute tpus execution-groups resume EXECUTION_GROUP_NAME - [--accelerator-type=ACCELERATOR_TYPE; default="v2-8"] - [--network=NETWORK; default="default"] [--preemptible] - [--tf-version=TF_VERSION] [--vm-only] [--zone=ZONE] - [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (BETA) (DEPRECATED) Creates Google Compute TPU and resumes the VM. - - This command is deprecated and will be removed in a future release. We - recommend that you use the TPU-VM or Queued Resource API. See - https://cloud.google.com/tpu/docs/managing-tpus-tpu-vm for more - information. - -EXAMPLES - To resume a suspended TPU VM combination, run: - - $ gcloud beta compute tpus execution-groups resume \ - test-execution-group --zone=test-zone --project=test-project \ - --accelerator-type=v2-8 --tf-version=2.4.1 - -POSITIONAL ARGUMENTS - EXECUTION_GROUP_NAME - The execution group name to delete. - -FLAGS - --accelerator-type=ACCELERATOR_TYPE; default="v2-8" - TPU accelerator type for the TPU. If not specified, this defaults to - v2-8. - - --network=NETWORK; default="default" - Set to the network that was originally used creating the suspended - Cloud TPU and Compute Engine VM. (It defaults to using the 'default' - network.) - - --preemptible - Create a preemptible Cloud TPU, instead of a normal (non-preemptible) - Cloud TPU. A preemptible Cloud TPU costs less per hour, but the Cloud - TPU service can stop/terminate the node at any time. - - --tf-version=TF_VERSION - Set the version of TensorFlow to the version originally set when - creating the suspended Cloud TPU and Compute Engine VM . (It defaults - to auto-selecting the latest stable release.) - - --vm-only - Do not allocate a TPU, only allocate a VM (useful if you're not ready - to run on a TPU yet). - - --zone=ZONE - Zone of the tpu to resume. If not specified and the compute/zone - property isn't set, you might be prompted to select a zone (interactive - mode only). - - To avoid prompting when this flag is omitted, you can set the - compute/zone property: - - $ gcloud config set compute/zone ZONE - - A list of zones can be fetched by running: - - $ gcloud compute zones list - - To unset the property, run: - - $ gcloud config unset compute/zone - - Alternatively, the zone can be stored in the environment variable - CLOUDSDK_COMPUTE_ZONE. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --configuration, --flags-file, --flatten, --format, - --help, --impersonate-service-account, --log-http, --project, --quiet, - --trace-token, --user-output-enabled, --verbosity. - - Run $ gcloud help for details. - -NOTES - This command is currently in beta and might change without notice. This - variant is also available: - - $ gcloud alpha compute tpus execution-groups resume - diff --git a/gcloud/beta/compute/tpus/execution-groups/suspend b/gcloud/beta/compute/tpus/execution-groups/suspend deleted file mode 100644 index df4779c5c..000000000 --- a/gcloud/beta/compute/tpus/execution-groups/suspend +++ /dev/null @@ -1,62 +0,0 @@ -NAME - gcloud beta compute tpus execution-groups suspend - deletes Google Compute - TPU and suspends the VM - -SYNOPSIS - gcloud beta compute tpus execution-groups suspend EXECUTION_GROUP_NAME - [--zone=ZONE] [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (BETA) (DEPRECATED) Deletes Google Compute TPU and suspends the VM. - - This command is deprecated and will be removed in a future release. We - recommend that you use the TPU-VM or Queued Resource API. See - https://cloud.google.com/tpu/docs/managing-tpus-tpu-vm for more - information. - -EXAMPLES - To delete the TPU and suspend the VM, run: - - $ gcloud beta compute tpus execution-groups suspend \ - test-execution-group --zone=test-zone --project=test-project - -POSITIONAL ARGUMENTS - EXECUTION_GROUP_NAME - The execution group name to delete. - -FLAGS - --zone=ZONE - Zone of the tpu to suspend. If not specified and the compute/zone - property isn't set, you might be prompted to select a zone (interactive - mode only). - - To avoid prompting when this flag is omitted, you can set the - compute/zone property: - - $ gcloud config set compute/zone ZONE - - A list of zones can be fetched by running: - - $ gcloud compute zones list - - To unset the property, run: - - $ gcloud config unset compute/zone - - Alternatively, the zone can be stored in the environment variable - CLOUDSDK_COMPUTE_ZONE. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --configuration, --flags-file, --flatten, --format, - --help, --impersonate-service-account, --log-http, --project, --quiet, - --trace-token, --user-output-enabled, --verbosity. - - Run $ gcloud help for details. - -NOTES - This command is currently in beta and might change without notice. This - variant is also available: - - $ gcloud alpha compute tpus execution-groups suspend - diff --git a/gcloud/beta/compute/tpus/help b/gcloud/beta/compute/tpus/help index 6cf0dd105..7d1755c1f 100644 --- a/gcloud/beta/compute/tpus/help +++ b/gcloud/beta/compute/tpus/help @@ -24,40 +24,12 @@ GROUPS accelerator-types (BETA) List or Describe Available Cloud TPU accelerator types. - execution-groups - (BETA) (DEPRECATED) Command group that helps create and manage Cloud - TPUs and Compute VMs. - locations (BETA) List or Describe Available Cloud TPU Locations. versions (BETA) Explore Available Tensorflow versions for Cloud TPUs. -COMMANDS - COMMAND is one of the following: - - create - (BETA) (DEPRECATED) Create a new Cloud TPU. - - delete - (BETA) (DEPRECATED) Deletes a Cloud TPU. - - describe - (BETA) (DEPRECATED) Describe a Cloud TPU. - - list - (BETA) (DEPRECATED) List Cloud TPUs. - - reimage - (BETA) (DEPRECATED) Reimages the OS on a Cloud TPU. - - start - (BETA) (DEPRECATED) Start a Cloud TPU. - - stop - (BETA) (DEPRECATED) Stop a Cloud TPU. - NOTES This command is currently in beta and might change without notice. These variants are also available: diff --git a/gcloud/beta/compute/tpus/reimage b/gcloud/beta/compute/tpus/reimage deleted file mode 100644 index e580a4605..000000000 --- a/gcloud/beta/compute/tpus/reimage +++ /dev/null @@ -1,84 +0,0 @@ -NAME - gcloud beta compute tpus reimage - reimages the OS on a Cloud TPU - -SYNOPSIS - gcloud beta compute tpus reimage (TPU : --zone=ZONE) --version=VERSION - [--async] [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (BETA) (DEPRECATED) This command is being deprecated. Please use gcloud - compute tpus tpu-vm reimage instead. - - Reimages the OS on a Cloud TPU. - -EXAMPLES - The following command reimages a TPU with ID my-tpu in zone us-central1-b - with TensorFlow version 1.15: - - $ gcloud beta compute tpus reimage my-tpu --zone=us-central1-b \ - --version=1.15 - -POSITIONAL ARGUMENTS - Tpu resource - The Cloud TPU you want to reimage. The arguments in this - group can be used to specify the attributes of this resource. (NOTE) Some - attributes are not given arguments in this group but can be set in other - ways. - - To set the project attribute: - ◆ provide the argument tpu on the command line with a fully specified - name; - ◆ provide the argument --project on the command line; - ◆ set the property core/project. - - This must be specified. - - TPU - ID of the tpu or fully qualified identifier for the tpu. - - To set the tpu attribute: - ▸ provide the argument tpu on the command line. - - This positional argument must be specified if any of the other - arguments in this group are specified. - - --zone=ZONE - The compute/zone of the Cloud TPU. - - If not specified, will use default compute/zone. - - To set the zone attribute: - ▸ provide the argument tpu on the command line with a fully - specified name; - ▸ provide the argument --zone on the command line; - ▸ set the property compute/zone. - -REQUIRED FLAGS - --version=VERSION - TensorFlow version for the TPU, such as 1.6. For a list of available - TensorFlow versions please see https://www.tensorflow.org/versions/. - -OPTIONAL FLAGS - --async - Return immediately, without waiting for the operation in progress to - complete. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --configuration, --flags-file, --flatten, --format, - --help, --impersonate-service-account, --log-http, --project, --quiet, - --trace-token, --user-output-enabled, --verbosity. - - Run $ gcloud help for details. - -API REFERENCE - This command uses the tpu/v1 API. The full documentation for this API can - be found at: https://cloud.google.com/tpu/ - -NOTES - This command is currently in beta and might change without notice. These - variants are also available: - - $ gcloud compute tpus reimage - - $ gcloud alpha compute tpus reimage - diff --git a/gcloud/beta/compute/tpus/start b/gcloud/beta/compute/tpus/start deleted file mode 100644 index e0bcab259..000000000 --- a/gcloud/beta/compute/tpus/start +++ /dev/null @@ -1,76 +0,0 @@ -NAME - gcloud beta compute tpus start - start a Cloud TPU - -SYNOPSIS - gcloud beta compute tpus start (TPU : --zone=ZONE) [--async] - [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (BETA) (DEPRECATED) This command is being deprecated. Please use gcloud - compute tpus tpu-vm start instead. - - Start a Cloud TPU. - -EXAMPLES - The following command starts a TPU with ID my-tpu in zone us-central1-b: - - $ gcloud beta compute tpus start my-tpu --zone=us-central1-b - -POSITIONAL ARGUMENTS - Tpu resource - The Cloud TPU to start. The arguments in this group can be - used to specify the attributes of this resource. (NOTE) Some attributes - are not given arguments in this group but can be set in other ways. - - To set the project attribute: - ◆ provide the argument tpu on the command line with a fully specified - name; - ◆ provide the argument --project on the command line; - ◆ set the property core/project. - - This must be specified. - - TPU - ID of the tpu or fully qualified identifier for the tpu. - - To set the tpu attribute: - ▸ provide the argument tpu on the command line. - - This positional argument must be specified if any of the other - arguments in this group are specified. - - --zone=ZONE - The compute/zone of the Cloud TPU. - - If not specified, will use default compute/zone. - - To set the zone attribute: - ▸ provide the argument tpu on the command line with a fully - specified name; - ▸ provide the argument --zone on the command line; - ▸ set the property compute/zone. - -FLAGS - --async - Return immediately, without waiting for the operation in progress to - complete. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --configuration, --flags-file, --flatten, --format, - --help, --impersonate-service-account, --log-http, --project, --quiet, - --trace-token, --user-output-enabled, --verbosity. - - Run $ gcloud help for details. - -API REFERENCE - This command uses the tpu/v1 API. The full documentation for this API can - be found at: https://cloud.google.com/tpu/ - -NOTES - This command is currently in beta and might change without notice. These - variants are also available: - - $ gcloud compute tpus start - - $ gcloud alpha compute tpus start - diff --git a/gcloud/beta/compute/tpus/stop b/gcloud/beta/compute/tpus/stop deleted file mode 100644 index 03401e788..000000000 --- a/gcloud/beta/compute/tpus/stop +++ /dev/null @@ -1,76 +0,0 @@ -NAME - gcloud beta compute tpus stop - stop a Cloud TPU - -SYNOPSIS - gcloud beta compute tpus stop (TPU : --zone=ZONE) [--async] - [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (BETA) (DEPRECATED) This command is being deprecated. Please use gcloud - compute tpus tpu-vm stop instead. - - Stop a Cloud TPU. - -EXAMPLES - The following command stops a TPU with ID my-tpu in zone us-central1-b: - - $ gcloud beta compute tpus stop my-tpu --zone=us-central1-b - -POSITIONAL ARGUMENTS - Tpu resource - The Cloud TPU to stop. The arguments in this group can be - used to specify the attributes of this resource. (NOTE) Some attributes - are not given arguments in this group but can be set in other ways. - - To set the project attribute: - ◆ provide the argument tpu on the command line with a fully specified - name; - ◆ provide the argument --project on the command line; - ◆ set the property core/project. - - This must be specified. - - TPU - ID of the tpu or fully qualified identifier for the tpu. - - To set the tpu attribute: - ▸ provide the argument tpu on the command line. - - This positional argument must be specified if any of the other - arguments in this group are specified. - - --zone=ZONE - The compute/zone of the Cloud TPU. - - If not specified, will use default compute/zone. - - To set the zone attribute: - ▸ provide the argument tpu on the command line with a fully - specified name; - ▸ provide the argument --zone on the command line; - ▸ set the property compute/zone. - -FLAGS - --async - Return immediately, without waiting for the operation in progress to - complete. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --configuration, --flags-file, --flatten, --format, - --help, --impersonate-service-account, --log-http, --project, --quiet, - --trace-token, --user-output-enabled, --verbosity. - - Run $ gcloud help for details. - -API REFERENCE - This command uses the tpu/v1 API. The full documentation for this API can - be found at: https://cloud.google.com/tpu/ - -NOTES - This command is currently in beta and might change without notice. These - variants are also available: - - $ gcloud compute tpus stop - - $ gcloud alpha compute tpus stop - diff --git a/gcloud/beta/container/clusters/create b/gcloud/beta/container/clusters/create index abca0eb46..07f6b8770 100644 --- a/gcloud/beta/container/clusters/create +++ b/gcloud/beta/container/clusters/create @@ -43,7 +43,8 @@ SYNOPSIS [--enable-identity-service] [--enable-image-streaming] [--enable-insecure-kubelet-readonly-port] [--enable-intra-node-visibility] [--enable-ip-access] - [--enable-ip-alias] [--enable-kubernetes-alpha] + [--enable-ip-alias] [--enable-k8s-certs-via-dns] + [--enable-k8s-tokens-via-dns] [--enable-kubernetes-alpha] [--enable-kubernetes-unstable-apis=API,[API,...]] [--enable-l4-ilb-subsetting] [--enable-legacy-authorization] [--enable-legacy-lustre-port] [--enable-logging-monitoring-system-only] @@ -682,6 +683,14 @@ FLAGS you omit both --enable-ip-alias and --no-enable-ip-alias, the default is a VPC-native cluster. + --enable-k8s-certs-via-dns + Enable K8s client certificates Authentication to the cluster's control + plane over DNS-based endpoint. + + --enable-k8s-tokens-via-dns + Enable K8s Service Account tokens Authentication to the cluster's + control plane over DNS-based endpoint. + --enable-kubernetes-alpha Enable Kubernetes alpha features on this cluster. Selecting this option will result in the cluster having all Kubernetes alpha API groups and diff --git a/gcloud/beta/container/clusters/create-auto b/gcloud/beta/container/clusters/create-auto index 1d0ef9913..7ac495eff 100644 --- a/gcloud/beta/container/clusters/create-auto +++ b/gcloud/beta/container/clusters/create-auto @@ -21,7 +21,9 @@ SYNOPSIS [--enable-backup-restore] [--enable-cilium-clusterwide-network-policy] [--enable-confidential-nodes] [--enable-default-compute-class] [--enable-dns-access] [--enable-fleet] [--enable-google-cloud-access] - [--enable-ip-access] [--enable-kubernetes-unstable-apis=API,[API,...]] + [--enable-ip-access] [--enable-k8s-certs-via-dns] + [--enable-k8s-tokens-via-dns] + [--enable-kubernetes-unstable-apis=API,[API,...]] [--enable-legacy-lustre-port] [--enable-lustre-csi-driver] [--enable-master-global-access] [--enable-multi-networking] [--enable-ray-cluster-logging] [--enable-ray-cluster-monitoring] @@ -308,6 +310,14 @@ FLAGS Enable access to the cluster's control plane over private IP and public IP if --enable-private-endpoint is not enabled. + --enable-k8s-certs-via-dns + Enable K8s client certificates Authentication to the cluster's control + plane over DNS-based endpoint. + + --enable-k8s-tokens-via-dns + Enable K8s Service Account tokens Authentication to the cluster's + control plane over DNS-based endpoint. + --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/beta/container/clusters/update b/gcloud/beta/container/clusters/update index c19a40e91..f1da3b8cb 100644 --- a/gcloud/beta/container/clusters/update +++ b/gcloud/beta/container/clusters/update @@ -91,6 +91,7 @@ SYNOPSIS | --enable-l4-lb-firewall-reconciliation | --enable-authorized-networks-on-private-endpoint --enable-dns-access --enable-google-cloud-access --enable-ip-access + --enable-k8s-certs-via-dns --enable-k8s-tokens-via-dns --enable-master-global-access --enable-private-endpoint --enable-master-authorized-networks --master-authorized-networks=NETWORK,[NETWORK,...] @@ -1308,6 +1309,14 @@ REQUIRED FLAGS Enable access to the cluster's control plane over private IP and public IP if --enable-private-endpoint is not enabled. + --enable-k8s-certs-via-dns + Enable K8s client certificates Authentication to the cluster's + control plane over DNS-based endpoint. + + --enable-k8s-tokens-via-dns + Enable K8s Service Account tokens Authentication to the cluster's + control plane over DNS-based endpoint. + --enable-master-global-access Use with private clusters to allow access to the master's private endpoint from any Google Cloud region or on-premises environment diff --git a/gcloud/beta/container/node-pools/create b/gcloud/beta/container/node-pools/create index bf1694aea..672eab3a2 100644 --- a/gcloud/beta/container/node-pools/create +++ b/gcloud/beta/container/node-pools/create @@ -14,6 +14,7 @@ SYNOPSIS [--additional-pod-network=[subnetwork=SUBNETWORK_NAME, pod-ipv4-range=SECONDARY_RANGE_NAME, [max-pods-per-node=NUM_PODS],...]] [--async] + [--autoscaled-rollout-policy=[wait-for-drain-duration=WAIT-FOR-DRAIN-DURATION]] [--boot-disk-kms-key=BOOT_DISK_KMS_KEY] [--boot-disk-provisioned-iops=BOOT_DISK_PROVISIONED_IOPS] [--boot-disk-provisioned-throughput=BOOT_DISK_PROVISIONED_THROUGHPUT] @@ -183,6 +184,23 @@ FLAGS Return immediately, without waiting for the operation in progress to complete. + --autoscaled-rollout-policy=[wait-for-drain-duration=WAIT-FOR-DRAIN-DURATION] + Autoscaled rollout policy options for blue-green upgrade. + + wait-for-drain-duration + (Optional) Time in seconds to wait after cordoning the blue pool + before draining the nodes. + + Examples: + + $ gcloud beta container node-pools create node-pool-1 \ + --cluster=example-cluster --enable-blue-green-upgrade \ + --autoscaled-rollout-policy="" + + $ gcloud beta container node-pools create node-pool-1 \ + --cluster=example-cluster --enable-blue-green-upgrade \ + --autoscaled-rollout-policy=wait-for-drain-duration=7200s + --boot-disk-kms-key=BOOT_DISK_KMS_KEY The Customer Managed Encryption Key used to encrypt the boot disk attached to each node in the node pool. This should be of the form diff --git a/gcloud/beta/container/node-pools/update b/gcloud/beta/container/node-pools/update index b80bbc98b..708cabbc2 100644 --- a/gcloud/beta/container/node-pools/update +++ b/gcloud/beta/container/node-pools/update @@ -24,11 +24,8 @@ SYNOPSIS | --storage-pools=STORAGE_POOL,[...] | --system-config-from-file=PATH_TO_FILE | --tags=[TAG,...] | --windows-os-version=WINDOWS_OS_VERSION - | --workload-metadata=WORKLOAD_METADATA | --enable-blue-green-upgrade - --enable-surge-upgrade --max-surge-upgrade=MAX_SURGE_UPGRADE - --max-unavailable-upgrade=MAX_UNAVAILABLE_UPGRADE - --node-pool-soak-duration=NODE_POOL_SOAK_DURATION - --standard-rollout-policy=[batch-node-count=BATCH_NODE_COUNT, + | --workload-metadata=WORKLOAD_METADATA + | --autoscaled-rollout-policy=[wait-for-drain-duration=WAIT-FOR-DRAIN-DURATION] --enable-blue-green-upgrade --enable-surge-upgrade --max-surge-upgrade=MAX_SURGE_UPGRADE --max-unavailable-upgrade=MAX_UNAVAILABLE_UPGRADE --node-pool-soak-duration=NODE_POOL_SOAK_DURATION --standard-rollout-policy=[batch-node-count=BATCH_NODE_COUNT, batch-percent=BATCH_NODE_PERCENTAGE, batch-soak-duration=BATCH_SOAK_DURATION,...] | --boot-disk-provisioned-iops=BOOT_DISK_PROVISIONED_IOPS @@ -762,6 +759,23 @@ REQUIRED FLAGS Upgrade settings + --autoscaled-rollout-policy=[wait-for-drain-duration=WAIT-FOR-DRAIN-DURATION] + Autoscaled rollout policy options for blue-green upgrade. + + wait-for-drain-duration + (Optional) Time in seconds to wait after cordoning the blue + pool before draining the nodes. + + Examples: + + $ gcloud beta container node-pools update node-pool-1 \ + --cluster=example-cluster --enable-blue-green-upgrade \ + --autoscaled-rollout-policy="" + + $ gcloud beta container node-pools update node-pool-1 \ + --cluster=example-cluster --enable-blue-green-upgrade \ + --autoscaled-rollout-policy=wait-for-drain-duration=7200s + --enable-blue-green-upgrade Changes node pool upgrade strategy to blue-green upgrade. diff --git a/gcloud/beta/firestore/databases/help b/gcloud/beta/firestore/databases/help index c15096c73..c20abbb1d 100644 --- a/gcloud/beta/firestore/databases/help +++ b/gcloud/beta/firestore/databases/help @@ -32,6 +32,10 @@ COMMANDS list (BETA) Lists all Firestore databases under the project. + ping + (BETA) Times the connection and ping time for a Firestore with MongoDB + compatibility database. + restore (BETA) Restores a Cloud Firestore database from a backup. diff --git a/gcloud/beta/firestore/databases/ping b/gcloud/beta/firestore/databases/ping new file mode 100644 index 000000000..666275046 --- /dev/null +++ b/gcloud/beta/firestore/databases/ping @@ -0,0 +1,38 @@ +NAME + gcloud beta firestore databases ping - times the connection and ping time + for a Firestore with MongoDB compatibility database + +SYNOPSIS + gcloud beta firestore databases ping --database=DATABASE + [GCLOUD_WIDE_FLAG ...] + +EXAMPLES + To time the connection and ping times for a Firestore with MongoDB + compatibility database testdb: + + $ gcloud beta firestore databases ping --database=testdb + +REQUIRED FLAGS + --database=DATABASE + The database to operate on. + + For example, to operate on database foo: + + $ gcloud beta firestore databases ping --database='foo' + +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 firestore databases ping + + $ gcloud alpha firestore databases ping + diff --git a/gcloud/beta/iam/workforce-pools/providers/scim-tenants/delete b/gcloud/beta/iam/workforce-pools/providers/scim-tenants/delete index 1a66e1f58..07fb71f1a 100644 --- a/gcloud/beta/iam/workforce-pools/providers/scim-tenants/delete +++ b/gcloud/beta/iam/workforce-pools/providers/scim-tenants/delete @@ -5,7 +5,7 @@ NAME SYNOPSIS gcloud beta iam workforce-pools providers scim-tenants delete (SCIM_TENANT : --location=LOCATION - --provider=PROVIDER --workforce-pool=WORKFORCE_POOL) + --provider=PROVIDER --workforce-pool=WORKFORCE_POOL) [--hard-delete] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -70,6 +70,10 @@ POSITIONAL ARGUMENTS specified name; ▸ provide the argument --workforce-pool on the command line. +FLAGS + --hard-delete + Deletes the SCIM tenant immediately. This operation cannot be undone. + 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/memorystore/instances/update b/gcloud/beta/memorystore/instances/update index d056a059e..690981636 100644 --- a/gcloud/beta/memorystore/instances/update +++ b/gcloud/beta/memorystore/instances/update @@ -6,10 +6,10 @@ SYNOPSIS gcloud beta memorystore instances update INSTANCE [--async] [--[no-]async-instance-endpoints-deletion-enabled] [--[no-]deletion-protection-enabled] [--engine-version=ENGINE_VERSION] - [--location=LOCATION] [--mode=MODE] [--node-type=NODE_TYPE] - [--[no-]ondemand-maintenance] [--replica-count=REPLICA_COUNT] - [--request-id=REQUEST_ID] [--shard-count=SHARD_COUNT] - [--[no-]simulate-maintenance-event] + [--location=LOCATION] [--maintenance-version=MAINTENANCE_VERSION] + [--mode=MODE] [--node-type=NODE_TYPE] [--[no-]ondemand-maintenance] + [--replica-count=REPLICA_COUNT] [--request-id=REQUEST_ID] + [--shard-count=SHARD_COUNT] [--[no-]simulate-maintenance-event] [--aof-config-append-fsync=AOF_CONFIG_APPEND_FSYNC --clear-persistence-config --persistence-config-mode=PERSISTENCE_CONFIG_MODE @@ -111,6 +111,13 @@ FLAGS value for resource location attribute. When the resource's full URI path is not provided, location will fallback to this flag value. + Arguments for the maintenance version. + + --maintenance-version=MAINTENANCE_VERSION + This field can be used to trigger self service update to indicate the + desired maintenance version. The input to this field can be + determined by the available_maintenance_versions field. + --mode=MODE The mode config for the instance. MODE must be one of: diff --git a/gcloud/beta/redis/clusters/update b/gcloud/beta/redis/clusters/update index 9b50dd390..e43f4d991 100644 --- a/gcloud/beta/redis/clusters/update +++ b/gcloud/beta/redis/clusters/update @@ -8,7 +8,8 @@ SYNOPSIS [--automated-backup-mode=AUTOMATED_BACKUP_MODE] [--automated-backup-start-time=AUTOMATED_BACKUP_START_TIME] [--automated-backup-ttl=AUTOMATED_BACKUP_TTL] [--deletion-protection] - [--node-type=NODE_TYPE] [--persistence-mode=PERSISTENCE_MODE] + [--maintenance-version=MAINTENANCE_VERSION] [--node-type=NODE_TYPE] + [--persistence-mode=PERSISTENCE_MODE] [--rdb-snapshot-period=RDB_SNAPSHOT_PERIOD] [--rdb-snapshot-start-time=RDB_SNAPSHOT_START_TIME] [--remove-redis-config=[KEY,...]] [--replica-count=REPLICA_COUNT] @@ -107,6 +108,9 @@ FLAGS Enable deletion protection for the Redis Cluster. Use --deletion-protection/--no-deletion-protection to enable/disable it. + --maintenance-version=MAINTENANCE_VERSION + The maintenance version of the cluster. + --node-type=NODE_TYPE Node Type of the redis cluster Node. NODE_TYPE must be one of: redis-highmem-medium, redis-highmem-xlarge, redis-shared-core-nano, diff --git a/gcloud/beta/resource-manager/tags/values/create b/gcloud/beta/resource-manager/tags/values/create index 0c7955a71..294f9fd56 100644 --- a/gcloud/beta/resource-manager/tags/values/create +++ b/gcloud/beta/resource-manager/tags/values/create @@ -10,18 +10,18 @@ SYNOPSIS DESCRIPTION (BETA) Creates a TagValue resource given the short_name and description (optional) as well as the parent, the of the TagValue. The parent of the - TagValue can be a TagKey and TagValue the parent's details can be passed as - a numeric id or the namespaced name. + TagValue can be a TagKey or TagValue. The parent can be specified by its + numeric ID or its namespaced name. EXAMPLES - To create a TagValue with the short name 'test' and the description - 'description' under a TagKey with a short name 'env' under - 'organizations/123', run: + To create a TagValue with the short name test and the description + descriptio under a TagKey with a short name env under organizations/123, + run: $ gcloud beta resource-manager tags values create test \ --parent=123/env --description=description - To create a TagValue with the short name 'test' under TagKey with id '456', + To create a TagValue with the short name test under TagKey with id 456, run: $ gcloud beta resource-manager tags values create test \ diff --git a/gcloud/beta/sql/instances/create b/gcloud/beta/sql/instances/create index 9266c254a..e34a76a34 100644 --- a/gcloud/beta/sql/instances/create +++ b/gcloud/beta/sql/instances/create @@ -23,9 +23,9 @@ SYNOPSIS [--deny-maintenance-period-end-date=DENY_MAINTENANCE_PERIOD_END_DATE] [--deny-maintenance-period-start-date=DENY_MAINTENANCE_PERIOD_START_DATE] [--deny-maintenance-period-time=DENY_MAINTENANCE_PERIOD_TIME] - [--edition=EDITION] [--enable-bin-log] - [--[no-]enable-connection-pooling] [--[no-]enable-data-cache] - [--[no-]enable-dataplex-integration] + [--edition=EDITION] [--enable-auto-upgrade-minor-version] + [--enable-bin-log] [--[no-]enable-connection-pooling] + [--[no-]enable-data-cache] [--[no-]enable-dataplex-integration] [--[no-]enable-google-ml-integration] [--enable-google-private-path] [--enable-password-policy] [--enable-point-in-time-recovery] [--enforce-new-sql-network-architecture] @@ -266,6 +266,10 @@ FLAGS Specifies the edition of Cloud SQL instance. EDITION must be one of: enterprise, enterprise-plus. + --enable-auto-upgrade-minor-version + Enables auto-upgrade for MySQL 8.0 minor versions. The MySQL version + must be 8.0.35 or higher. + --enable-bin-log Allows for data recovery from a specific point in time, down to a fraction of a second. Must have automatic backups enabled to use. Make diff --git a/gcloud/beta/sql/instances/patch b/gcloud/beta/sql/instances/patch index bafbbb539..27d795250 100644 --- a/gcloud/beta/sql/instances/patch +++ b/gcloud/beta/sql/instances/patch @@ -17,9 +17,9 @@ SYNOPSIS [--deny-maintenance-period-end-date=DENY_MAINTENANCE_PERIOD_END_DATE] [--deny-maintenance-period-start-date=DENY_MAINTENANCE_PERIOD_START_DATE] [--deny-maintenance-period-time=DENY_MAINTENANCE_PERIOD_TIME] [--diff] - [--edition=EDITION] [--[no-]enable-bin-log] - [--[no-]enable-connection-pooling] [--[no-]enable-data-cache] - [--[no-]enable-database-replication] + [--edition=EDITION] [--enable-auto-upgrade-minor-version] + [--[no-]enable-bin-log] [--[no-]enable-connection-pooling] + [--[no-]enable-data-cache] [--[no-]enable-database-replication] [--[no-]enable-dataplex-integration] [--[no-]enable-google-ml-integration] [--[no-]enable-google-private-path] [--enable-password-policy] @@ -202,6 +202,10 @@ FLAGS Specifies the edition of Cloud SQL instance. EDITION must be one of: enterprise, enterprise-plus. + --enable-auto-upgrade-minor-version + Enables auto-upgrade for MySQL 8.0 minor versions. The MySQL version + must be 8.0.35 or higher. + --[no-]enable-bin-log Allows for data recovery from a specific point in time, down to a fraction of a second. Must have automatic backups enabled to use. Make diff --git a/gcloud/bigtable/operations/list b/gcloud/bigtable/operations/list index ae48b4789..44f3974c4 100644 --- a/gcloud/bigtable/operations/list +++ b/gcloud/bigtable/operations/list @@ -2,9 +2,10 @@ NAME gcloud bigtable operations list - list Cloud Bigtable operations SYNOPSIS - gcloud bigtable operations list [--instance=INSTANCE] [--filter=EXPRESSION] - [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] - [GCLOUD_WIDE_FLAG ...] + gcloud bigtable operations list [--instance=INSTANCE] + [--return-partial-success=RETURN_PARTIAL_SUCCESS; default=True] + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] DESCRIPTION List Cloud Bigtable operations. @@ -18,6 +19,10 @@ EXAMPLES $ gcloud bigtable operations list --instance=INSTANCE_NAME + To fail the command if any location is unreachable, run: + + $ gcloud bigtable operations list --return-partial-success=false + FLAGS Instance resource - The instance to list operations for. This represents a Cloud resource. (NOTE) Some attributes are not given arguments in this @@ -35,6 +40,13 @@ FLAGS To set the instance attribute: ▸ provide the argument --instance on the command line. + --return-partial-success=RETURN_PARTIAL_SUCCESS; default=True + If true, operations that are reachable are returned as normal, and + those that are unreachable are returned in the unreachable field of the + response. If false, the command will fail if any location is + unreachable. Enabled by default, use --no-return-partial-success to + disable. + LIST COMMAND FLAGS --filter=EXPRESSION Apply a Boolean filter EXPRESSION to each resource item to be listed. diff --git a/gcloud/compute/backend-services/create b/gcloud/compute/backend-services/create index 548d56145..05e108dfa 100644 --- a/gcloud/compute/backend-services/create +++ b/gcloud/compute/backend-services/create @@ -396,7 +396,7 @@ FLAGS The load balancing algorithm used within the scope of the locality. LOCALITY_LB_POLICY must be one of: INVALID_LB_POLICY, ROUND_ROBIN, LEAST_REQUEST, RING_HASH, RANDOM, ORIGINAL_DESTINATION, MAGLEV, - WEIGHTED_MAGLEV, WEIGHTED_ROUND_ROBIN. + WEIGHTED_MAGLEV, WEIGHTED_ROUND_ROBIN, WEIGHTED_GCP_RENDEZVOUS. --logging-optional=LOGGING_OPTIONAL This field can only be specified if logging is enabled for the backend diff --git a/gcloud/compute/backend-services/update b/gcloud/compute/backend-services/update index b16deccb2..82ad88fea 100644 --- a/gcloud/compute/backend-services/update +++ b/gcloud/compute/backend-services/update @@ -25,7 +25,6 @@ SYNOPSIS [--idle-timeout-sec=IDLE_TIMEOUT_SEC] [--ip-address-selection-policy=IP_ADDRESS_SELECTION_POLICY] [--load-balancing-scheme=LOAD_BALANCING_SCHEME] - [--locality-lb-policy=LOCALITY_LB_POLICY] [--logging-optional=LOGGING_OPTIONAL] [--logging-optional-fields=[LOGGING_OPTIONAL_FIELDS,...]] [--logging-sample-rate=LOGGING_SAMPLE_RATE] [--port-name=PORT_NAME] @@ -51,6 +50,7 @@ SYNOPSIS [--default-ttl=DEFAULT_TTL | --no-default-ttl] [--global | --region=REGION] [--global-health-checks | --health-checks-region=HEALTH_CHECKS_REGION] + [--locality-lb-policy=LOCALITY_LB_POLICY | --no-locality-lb-policy] [--max-ttl=MAX_TTL | --no-max-ttl] [--[no-]negative-caching | --no-negative-caching-policies | --negative-caching-policy=[[CODE=TTL],...]] @@ -314,12 +314,6 @@ FLAGS LOAD_BALANCING_SCHEME must be one of: EXTERNAL, EXTERNAL_MANAGED. - --locality-lb-policy=LOCALITY_LB_POLICY - The load balancing algorithm used within the scope of the locality. - LOCALITY_LB_POLICY must be one of: INVALID_LB_POLICY, ROUND_ROBIN, - LEAST_REQUEST, RING_HASH, RANDOM, ORIGINAL_DESTINATION, MAGLEV, - WEIGHTED_MAGLEV, WEIGHTED_ROUND_ROBIN. - --logging-optional=LOGGING_OPTIONAL This field can only be specified if logging is enabled for the backend service. Configures whether all, none, or a subset of optional fields @@ -806,6 +800,17 @@ FLAGS Alternatively, the region can be stored in the environment variable CLOUDSDK_COMPUTE_REGION. + At most one of these can be specified: + + --locality-lb-policy=LOCALITY_LB_POLICY + The load balancing algorithm used within the scope of the locality. + LOCALITY_LB_POLICY must be one of: INVALID_LB_POLICY, ROUND_ROBIN, + LEAST_REQUEST, RING_HASH, RANDOM, ORIGINAL_DESTINATION, MAGLEV, + WEIGHTED_MAGLEV, WEIGHTED_ROUND_ROBIN, WEIGHTED_GCP_RENDEZVOUS. + + --no-locality-lb-policy + Removes the locality load balancing policy from the backend service. + At most one of these can be specified: --max-ttl=MAX_TTL diff --git a/gcloud/compute/help b/gcloud/compute/help index 712cd1baa..9e0be46a5 100644 --- a/gcloud/compute/help +++ b/gcloud/compute/help @@ -118,6 +118,9 @@ GROUPS operations Read and manipulate Compute Engine operations. + org-security-policies + Manage Compute Engine organization security policies. + os-config Manage OS Config tasks for Compute Engine VM instances. @@ -127,6 +130,9 @@ GROUPS packet-mirrorings Manage Compute Engine packet mirroring resources. + preview-features + Read and manipulate Compute Engine Preview Features. + project-info Read and manipulate project-level data like quotas and metadata. diff --git a/gcloud/compute/instances/help b/gcloud/compute/instances/help index af787c9de..fbbfc4173 100644 --- a/gcloud/compute/instances/help +++ b/gcloud/compute/instances/help @@ -108,10 +108,6 @@ COMMANDS list List Compute Engine instances. - move - (DEPRECATED) Move an instance and its attached persistent disks between - zones. - perform-maintenance Perform maintenance of Google Compute Engine instance. diff --git a/gcloud/compute/instances/move b/gcloud/compute/instances/move deleted file mode 100644 index 54f824f34..000000000 --- a/gcloud/compute/instances/move +++ /dev/null @@ -1,95 +0,0 @@ -NAME - gcloud compute instances move - move an instance and its attached - persistent disks between zones - -SYNOPSIS - gcloud compute instances move INSTANCE_NAME - --destination-zone=DESTINATION_ZONE [--async] [--zone=ZONE] - [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (DEPRECATED) This command is deprecated. Please see - https://cloud.google.com/compute/docs/instances/moving-instance-across-zones - for an alternative method. - - gcloud compute instances move moves a Compute Engine virtual machine from - one zone to another. Moving a virtual machine might incur downtime if the - guest OS must be shut down in order to quiesce disk volumes prior to - snapshotting. - - For example, running the following command moves the instance called - example-instance-1 with its attached persistent disks, currently running in - us-central1-b, to us-central1-f. - - $ gcloud compute instances move example-instance-1 \ - --zone=us-central1-b --destination-zone=us-central1-f - - Note: Moving VMs or disks by using the gcloud compute instances move - command might cause unexpected behavior. For more information, see - https://cloud.google.com/compute/docs/troubleshooting/known-issues#moving_vms_or_disks_using_the_moveinstance_api_or_the_causes_unexpected_behavior. - - Please note that gcloud compute instances move does not yet support - instances which have regional persistent disks attached. Please see - https://cloud.google.com/compute/docs/disks/regional-persistent-disk for - more details. - -EXAMPLES - To move instance-1 from us-central-a to europe-west1-d, run: - - $ gcloud compute instances move instance-1 --zone=us-central1-a \ - --destination-zone=europe-west1-d - -POSITIONAL ARGUMENTS - INSTANCE_NAME - Name of the instance to operate on. For details on valid instance - names, refer to the criteria documented under the field 'name' at: - https://cloud.google.com/compute/docs/reference/rest/v1/instances - -REQUIRED FLAGS - --destination-zone=DESTINATION_ZONE - The zone to move the instance to. - -OPTIONAL FLAGS - --async - Return immediately, without waiting for the operation in progress to - complete. - - --zone=ZONE - Zone of the instance to operate on. If not specified, you might be - prompted to select a zone (interactive mode only). gcloud attempts to - identify the appropriate zone by searching for resources in your - currently active project. If the zone cannot be determined, gcloud - prompts you for a selection with all available Google Cloud Platform - zones. - - To avoid prompting when this flag is omitted, the user can set the - compute/zone property: - - $ gcloud config set compute/zone ZONE - - A list of zones can be fetched by running: - - $ gcloud compute zones list - - To unset the property, run: - - $ gcloud config unset compute/zone - - Alternatively, the zone can be stored in the environment variable - CLOUDSDK_COMPUTE_ZONE. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --configuration, --flags-file, --flatten, --format, - --help, --impersonate-service-account, --log-http, --project, --quiet, - --trace-token, --user-output-enabled, --verbosity. - - Run $ gcloud help for details. - -NOTES - These variants are also available: - - $ gcloud alpha compute instances move - - $ gcloud beta compute instances move - diff --git a/gcloud/compute/interconnects/cross-site-networks/create b/gcloud/compute/interconnects/cross-site-networks/create new file mode 100644 index 000000000..76d491529 --- /dev/null +++ b/gcloud/compute/interconnects/cross-site-networks/create @@ -0,0 +1,43 @@ +NAME + gcloud compute interconnects cross-site-networks create - create a Compute + Engine cross site network + +SYNOPSIS + gcloud compute interconnects cross-site-networks create NAME + [--description=DESCRIPTION] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + gcloud compute interconnects cross-site-networks create is used to create + cross site networks. A cross site network contains wire groups. + + For an example, refer to the EXAMPLES section below. + +EXAMPLES + To create a cross site network, run: + + $ gcloud compute interconnects cross-site-networks create \ + example-csn --description="Example cross site network" + +POSITIONAL ARGUMENTS + NAME + Name of the crossSiteNetwork to create. + +FLAGS + --description=DESCRIPTION + An optional, textual description for the cross site network. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + These variants are also available: + + $ gcloud alpha compute interconnects cross-site-networks create + + $ gcloud beta compute interconnects cross-site-networks create + diff --git a/gcloud/compute/interconnects/cross-site-networks/delete b/gcloud/compute/interconnects/cross-site-networks/delete new file mode 100644 index 000000000..0c14bdc6e --- /dev/null +++ b/gcloud/compute/interconnects/cross-site-networks/delete @@ -0,0 +1,41 @@ +NAME + gcloud compute interconnects cross-site-networks delete - delete Compute + Engine cross site networks + +SYNOPSIS + gcloud compute interconnects cross-site-networks delete NAME [NAME ...] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + gcloud compute interconnects cross-site-networks delete is used to delete + cross site networks. + + For an example, refer to the EXAMPLES section below. + +EXAMPLES + To delete a cross site network, run: + + $ gcloud compute interconnects cross-site-networks delete example-csn + + Although not shown in this example, you can delete multiple cross site + networks in a single command. + +POSITIONAL ARGUMENTS + NAME [NAME ...] + Names of the crossSiteNetworks 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 + These variants are also available: + + $ gcloud alpha compute interconnects cross-site-networks delete + + $ gcloud beta compute interconnects cross-site-networks delete + diff --git a/gcloud/compute/interconnects/cross-site-networks/describe b/gcloud/compute/interconnects/cross-site-networks/describe new file mode 100644 index 000000000..a3a0efb6b --- /dev/null +++ b/gcloud/compute/interconnects/cross-site-networks/describe @@ -0,0 +1,39 @@ +NAME + gcloud compute interconnects cross-site-networks describe - describe a + Compute Engine cross site network + +SYNOPSIS + gcloud compute interconnects cross-site-networks describe NAME + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + gcloud compute interconnects cross-site-networks describe is used to + describe a cross site network. + + For an example, refer to the EXAMPLES section below. + +EXAMPLES + To describe a cross site network, run: + + $ gcloud compute interconnects cross-site-networks describe \ + example-csn + +POSITIONAL ARGUMENTS + NAME + Name of the crossSiteNetwork 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 + These variants are also available: + + $ gcloud alpha compute interconnects cross-site-networks describe + + $ gcloud beta compute interconnects cross-site-networks describe + diff --git a/gcloud/compute/interconnects/cross-site-networks/help b/gcloud/compute/interconnects/cross-site-networks/help new file mode 100644 index 000000000..927ffbb0a --- /dev/null +++ b/gcloud/compute/interconnects/cross-site-networks/help @@ -0,0 +1,41 @@ +NAME + gcloud compute interconnects cross-site-networks - create or manipulate + cross site networks + +SYNOPSIS + gcloud compute interconnects cross-site-networks COMMAND + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Create or manipulate cross site networks. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + create + Create a Compute Engine cross site network. + + delete + Delete Compute Engine cross site networks. + + describe + Describe a Compute Engine cross site network. + + list + List Google Compute Engine cross site networks. + + update + Update a Compute Engine cross site network. + +NOTES + These variants are also available: + + $ gcloud alpha compute interconnects cross-site-networks + + $ gcloud beta compute interconnects cross-site-networks + diff --git a/gcloud/compute/interconnects/cross-site-networks/list b/gcloud/compute/interconnects/cross-site-networks/list new file mode 100644 index 000000000..5822a0817 --- /dev/null +++ b/gcloud/compute/interconnects/cross-site-networks/list @@ -0,0 +1,69 @@ +NAME + gcloud compute interconnects cross-site-networks list - list Google Compute + Engine cross site networks + +SYNOPSIS + gcloud compute interconnects cross-site-networks list [--filter=EXPRESSION] + [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + gcloud compute interconnects cross-site-networks list displays all Google + Compute Engine cross site networks in a project. + +EXAMPLES + To list all cross site networks in a project in table form, run: + + $ gcloud compute interconnects cross-site-networks list + + To list the URIs of all cross site networks in a project, run: + + $ gcloud compute interconnects cross-site-networks list --uri + +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 + These variants are also available: + + $ gcloud alpha compute interconnects cross-site-networks list + + $ gcloud beta compute interconnects cross-site-networks list + diff --git a/gcloud/compute/interconnects/cross-site-networks/update b/gcloud/compute/interconnects/cross-site-networks/update new file mode 100644 index 000000000..1f726edd6 --- /dev/null +++ b/gcloud/compute/interconnects/cross-site-networks/update @@ -0,0 +1,43 @@ +NAME + gcloud compute interconnects cross-site-networks update - update a Compute + Engine cross site network + +SYNOPSIS + gcloud compute interconnects cross-site-networks update NAME + [--description=DESCRIPTION] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + gcloud compute interconnects cross-site-networks update is used to update + cross site networks. + + For an example, refer to the EXAMPLES section below. + +EXAMPLES + To update a cross site network's description, run: + + $ gcloud compute interconnects cross-site-networks update \ + example-csn --description="New description" + +POSITIONAL ARGUMENTS + NAME + Name of the crossSiteNetwork to update. + +FLAGS + --description=DESCRIPTION + An optional, textual description for the cross site network. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + These variants are also available: + + $ gcloud alpha compute interconnects cross-site-networks update + + $ gcloud beta compute interconnects cross-site-networks update + diff --git a/gcloud/compute/interconnects/help b/gcloud/compute/interconnects/help index acaec33f7..42fe241b3 100644 --- a/gcloud/compute/interconnects/help +++ b/gcloud/compute/interconnects/help @@ -30,6 +30,9 @@ GROUPS attachments Read and manipulate Compute Engine interconnect attachments. + cross-site-networks + Create or manipulate cross site networks. + groups Create or manipulate interconnect groups. @@ -43,6 +46,9 @@ GROUPS Read and manipulate Google Compute Engine interconnect remote locations. + wire-groups + Create or manipulate wire groups. + COMMANDS COMMAND is one of the following: diff --git a/gcloud/compute/interconnects/wire-groups/add-endpoint b/gcloud/compute/interconnects/wire-groups/add-endpoint new file mode 100644 index 000000000..db9565fb8 --- /dev/null +++ b/gcloud/compute/interconnects/wire-groups/add-endpoint @@ -0,0 +1,47 @@ +NAME + gcloud compute interconnects wire-groups add-endpoint - add endpoint to a + Compute Engine wire group + +SYNOPSIS + gcloud compute interconnects wire-groups add-endpoint NAME + --cross-site-network=CROSS_SITE_NETWORK --endpoint-label=ENDPOINT_LABEL + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + gcloud compute interconnects wire-groups add-endpoint is used to add + endpoints to a wire group. + + For an example, refer to the EXAMPLES section below. + +EXAMPLES + To add an endpoint to a wire group, run: + + $ gcloud compute interconnects wire-groups add-endpoint example-wg \ + --cross-site-network=example-csn --endpoint-label=endpoint-1 + +POSITIONAL ARGUMENTS + NAME + Name of the wire group to update. + +REQUIRED FLAGS + --cross-site-network=CROSS_SITE_NETWORK + Name of the crossSiteNetwork to operate on. + + --endpoint-label=ENDPOINT_LABEL + The endpoint label for the wire group. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + These variants are also available: + + $ gcloud alpha compute interconnects wire-groups add-endpoint + + $ gcloud beta compute interconnects wire-groups add-endpoint + diff --git a/gcloud/compute/interconnects/wire-groups/add-interconnect b/gcloud/compute/interconnects/wire-groups/add-interconnect new file mode 100644 index 000000000..1a9983a64 --- /dev/null +++ b/gcloud/compute/interconnects/wire-groups/add-interconnect @@ -0,0 +1,60 @@ +NAME + gcloud compute interconnects wire-groups add-interconnect - add + interconnect to a Compute Engine wire group + +SYNOPSIS + gcloud compute interconnects wire-groups add-interconnect NAME + --cross-site-network=CROSS_SITE_NETWORK --endpoint-label=ENDPOINT_LABEL + --interconnect=INTERCONNECT --interconnect-label=INTERCONNECT_LABEL + --vlan-tags=VLAN_TAGS [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + gcloud compute interconnects wire-groups add-interconnect is used to add + interconnects to a wire group. + + For an example, refer to the EXAMPLES section below. + +EXAMPLES + To add an interconnect to a wire group, run: + + $ gcloud compute interconnects wire-groups add-interconnect \ + example-wg --cross-site-network=example-csn \ + --endpoint-label=endpoint-1 \ + --interconnect-label=interconnect-1 \ + --interconnect=example-interconnect --vlan-tags=111 + +POSITIONAL ARGUMENTS + NAME + Name of the wire group to update. + +REQUIRED FLAGS + --cross-site-network=CROSS_SITE_NETWORK + Name of the crossSiteNetwork to operate on. + + --endpoint-label=ENDPOINT_LABEL + The endpoint label for the wire group. + + --interconnect=INTERCONNECT + The interconnect for the wire group endpoint. + + --interconnect-label=INTERCONNECT_LABEL + The interconnect label for the wire group endpoint. + + --vlan-tags=VLAN_TAGS + The vlan tags for the interconnect on the wire group endpoint. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + These variants are also available: + + $ gcloud alpha compute interconnects wire-groups add-interconnect + + $ gcloud beta compute interconnects wire-groups add-interconnect + diff --git a/gcloud/compute/interconnects/wire-groups/create b/gcloud/compute/interconnects/wire-groups/create new file mode 100644 index 000000000..408be4601 --- /dev/null +++ b/gcloud/compute/interconnects/wire-groups/create @@ -0,0 +1,87 @@ +NAME + gcloud compute interconnects wire-groups create - create a Compute Engine + wire group + +SYNOPSIS + gcloud compute interconnects wire-groups create NAME + --bandwidth-allocation=BANDWIDTH_ALLOCATION + --bandwidth-unmetered=BANDWIDTH_UNMETERED + --cross-site-network=CROSS_SITE_NETWORK [--admin-enabled] + [--description=DESCRIPTION] [--fault-response=FAULT_RESPONSE] + [--validate-only] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + gcloud compute interconnects wire-groups create is used to create wire + groups. A wire group represents a group of redundant wires between + interconnects in two different metros. Each WireGroup belongs to a + CrossSiteNetwork. + + For an example, refer to the EXAMPLES section below. + +EXAMPLES + To create a wire group, run: + + $ gcloud compute interconnects wire-groups create example-wg \ + --cross-site-network=example-csn --bandwidth-unmetered=1 + +POSITIONAL ARGUMENTS + NAME + Name of the wire group to create. + +REQUIRED FLAGS + --bandwidth-allocation=BANDWIDTH_ALLOCATION + The bandwidth allocation for the wire group. BANDWIDTH_ALLOCATION must + be one of: + + ALLOCATE_PER_WIRE + Configures a separate unmetered bandwidth allocation (and + associated charges) for each wire in the group. + SHARED_WITH_WIRE_GROUP + Configures one unmetered bandwidth allocation for the wire group. + The unmetered bandwidth is divided equally across each wire in the + group, but dynamic throttling reallocates unused unmetered + bandwidth from unused or underused wires to other wires in the + group. + + --bandwidth-unmetered=BANDWIDTH_UNMETERED + The amount of unmetered bandwidth to assign to the wire group. + + --cross-site-network=CROSS_SITE_NETWORK + Name of the crossSiteNetwork to operate on. + +OPTIONAL FLAGS + --admin-enabled + Administrative status of the wire group. If not provided on creation, + defaults to enabled. When this is enabled, the wire group is + operational and will carry traffic. Use --no-admin-enabled to disable + it. + + --description=DESCRIPTION + An optional, textual description for the wire group. + + --fault-response=FAULT_RESPONSE + The fault response for the wire group. FAULT_RESPONSE must be one of: + + DISABLE_PORT + Disable port + NONE + None + + --validate-only + Validate the new configuration, but don't update 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 + These variants are also available: + + $ gcloud alpha compute interconnects wire-groups create + + $ gcloud beta compute interconnects wire-groups create + diff --git a/gcloud/compute/interconnects/wire-groups/delete b/gcloud/compute/interconnects/wire-groups/delete new file mode 100644 index 000000000..518e30678 --- /dev/null +++ b/gcloud/compute/interconnects/wire-groups/delete @@ -0,0 +1,43 @@ +NAME + gcloud compute interconnects wire-groups delete - delete Compute Engine + wire groups + +SYNOPSIS + gcloud compute interconnects wire-groups delete NAME [NAME ...] + --cross-site-network=CROSS_SITE_NETWORK [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + gcloud compute interconnects wire-groups delete is used to delete wire + groups. + + For an example, refer to the EXAMPLES section below. + +EXAMPLES + To delete a wire group, run: + + $ gcloud compute interconnects wire-groups delete example-wg \ + --cross-site-network=example-csn + +POSITIONAL ARGUMENTS + NAME [NAME ...] + Names of the wire groups to delete. + +REQUIRED FLAGS + --cross-site-network=CROSS_SITE_NETWORK + Name of the crossSiteNetwork to operate on. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + These variants are also available: + + $ gcloud alpha compute interconnects wire-groups delete + + $ gcloud beta compute interconnects wire-groups delete + diff --git a/gcloud/compute/interconnects/wire-groups/describe b/gcloud/compute/interconnects/wire-groups/describe new file mode 100644 index 000000000..44b7c5de0 --- /dev/null +++ b/gcloud/compute/interconnects/wire-groups/describe @@ -0,0 +1,43 @@ +NAME + gcloud compute interconnects wire-groups describe - describe a Compute + Engine wire group + +SYNOPSIS + gcloud compute interconnects wire-groups describe NAME + --cross-site-network=CROSS_SITE_NETWORK [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + gcloud compute interconnects wire-groups describe is used to describe a + wire group. + + For an example, refer to the EXAMPLES section below. + +EXAMPLES + To describe a wire group, run: + + $ gcloud compute interconnects wire-groups describe example-wg \ + --cross-site-network=example-csn + +POSITIONAL ARGUMENTS + NAME + Name of the wire group to describe. + +REQUIRED FLAGS + --cross-site-network=CROSS_SITE_NETWORK + Name of the crossSiteNetwork to operate on. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + These variants are also available: + + $ gcloud alpha compute interconnects wire-groups describe + + $ gcloud beta compute interconnects wire-groups describe + diff --git a/gcloud/compute/interconnects/wire-groups/help b/gcloud/compute/interconnects/wire-groups/help new file mode 100644 index 000000000..dac87a85c --- /dev/null +++ b/gcloud/compute/interconnects/wire-groups/help @@ -0,0 +1,51 @@ +NAME + gcloud compute interconnects wire-groups - create or manipulate wire groups + +SYNOPSIS + gcloud compute interconnects wire-groups COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Create or manipulate wire groups. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + add-endpoint + Add endpoint to a Compute Engine wire group. + + add-interconnect + Add interconnect to a Compute Engine wire group. + + create + Create a Compute Engine wire group. + + delete + Delete Compute Engine wire groups. + + describe + Describe a Compute Engine wire group. + + list + List Google Compute Engine wire groups. + + remove-endpoint + Remove endpoint from a Compute Engine wire group. + + remove-interconnect + Remove interconnect from a wire group. + + update + Update a Compute Engine wire group. + +NOTES + These variants are also available: + + $ gcloud alpha compute interconnects wire-groups + + $ gcloud beta compute interconnects wire-groups + diff --git a/gcloud/beta/compute/tpus/list b/gcloud/compute/interconnects/wire-groups/list similarity index 55% rename from gcloud/beta/compute/tpus/list rename to gcloud/compute/interconnects/wire-groups/list index 7a320d14e..6d60a78e4 100644 --- a/gcloud/beta/compute/tpus/list +++ b/gcloud/compute/interconnects/wire-groups/list @@ -1,44 +1,29 @@ NAME - gcloud beta compute tpus list - list Cloud TPUs + gcloud compute interconnects wire-groups list - list Google Compute Engine + wire groups SYNOPSIS - gcloud beta compute tpus list [--zone=ZONE] [--filter=EXPRESSION] + gcloud compute interconnects wire-groups list + --cross-site-network=CROSS_SITE_NETWORK [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) (DEPRECATED) This command is being deprecated. Please use gcloud - compute tpus tpu-vm list instead. - - List Cloud TPUs + gcloud compute interconnects wire-groups list displays all Google Compute + Engine wire groups in a project. EXAMPLES - The following command lists the status of TPUs in zone us-central1-b: + To list all wire groups in a project in table form, run: - $ gcloud beta compute tpus list --zone=us-central1-b + $ gcloud compute interconnects wire-groups list -FLAGS - Location resource - The compute/zone of the Cloud TPU. + To list the URIs of all wire groups in a project, run: - If not specified, will use the value of the [compute/zone] property in the - current gcloud configuration. To find a list of compute zones available - for Cloud TPUs in your project, run gcloud beta compute tpus locations - list. This represents a Cloud resource. (NOTE) Some attributes are not - given arguments in this group but can be set in other ways. + $ gcloud compute interconnects wire-groups list --uri - To set the project attribute: - ◆ provide the argument --zone on the command line with a fully - specified name; - ◆ set the property compute/zone with a fully specified name; - ◆ provide the argument --project on the command line; - ◆ set the property core/project. - - --zone=ZONE - ID of the location or fully qualified identifier for the location. - - To set the zone attribute: - ▸ provide the argument --zone on the command line; - ▸ set the property compute/zone. +REQUIRED FLAGS + --cross-site-network=CROSS_SITE_NETWORK + Name of the crossSiteNetwork to operate on. LIST COMMAND FLAGS --filter=EXPRESSION @@ -80,15 +65,10 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. -API REFERENCE - This command uses the tpu/v1 API. The full documentation for this API can - be found at: https://cloud.google.com/tpu/ - NOTES - This command is currently in beta and might change without notice. These - variants are also available: + These variants are also available: - $ gcloud compute tpus list + $ gcloud alpha compute interconnects wire-groups list - $ gcloud alpha compute tpus list + $ gcloud beta compute interconnects wire-groups list diff --git a/gcloud/compute/interconnects/wire-groups/remove-endpoint b/gcloud/compute/interconnects/wire-groups/remove-endpoint new file mode 100644 index 000000000..123db0593 --- /dev/null +++ b/gcloud/compute/interconnects/wire-groups/remove-endpoint @@ -0,0 +1,48 @@ +NAME + gcloud compute interconnects wire-groups remove-endpoint - remove endpoint + from a Compute Engine wire group + +SYNOPSIS + gcloud compute interconnects wire-groups remove-endpoint NAME + --cross-site-network=CROSS_SITE_NETWORK --endpoint-label=ENDPOINT_LABEL + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + gcloud compute interconnects wire-groups remove-endpoint is used to remove + endpoints from a wire group. + + For an example, refer to the EXAMPLES section below. + +EXAMPLES + To remove an endpoint from a wire group, run: + + $ gcloud compute interconnects wire-groups remove-endpoint \ + example-wg --cross-site-network=example-csn \ + --endpoint-label=endpoint-1 + +POSITIONAL ARGUMENTS + NAME + Name of the wire group to update. + +REQUIRED FLAGS + --cross-site-network=CROSS_SITE_NETWORK + Name of the crossSiteNetwork to operate on. + + --endpoint-label=ENDPOINT_LABEL + The endpoint label for the wire group. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + These variants are also available: + + $ gcloud alpha compute interconnects wire-groups remove-endpoint + + $ gcloud beta compute interconnects wire-groups remove-endpoint + diff --git a/gcloud/compute/interconnects/wire-groups/remove-interconnect b/gcloud/compute/interconnects/wire-groups/remove-interconnect new file mode 100644 index 000000000..0ce45ab47 --- /dev/null +++ b/gcloud/compute/interconnects/wire-groups/remove-interconnect @@ -0,0 +1,52 @@ +NAME + gcloud compute interconnects wire-groups remove-interconnect - remove + interconnect from a wire group + +SYNOPSIS + gcloud compute interconnects wire-groups remove-interconnect NAME + --cross-site-network=CROSS_SITE_NETWORK --endpoint-label=ENDPOINT_LABEL + --interconnect-label=INTERCONNECT_LABEL [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + gcloud compute interconnects wire-groups remove-interconnect is used to + remove interconnects from a wire group endpoint. + + For an example, refer to the EXAMPLES section below. + +EXAMPLES + To remove an interconnect from a wire group endpoint, run: + + $ gcloud compute interconnects wire-groups remove-interconnect \ + example-wg --cross-site-network=example-csn \ + --endpoint-label=endpoint-1 \ + --interconnect-label=example-interconnect + +POSITIONAL ARGUMENTS + NAME + Name of the wire group to update. + +REQUIRED FLAGS + --cross-site-network=CROSS_SITE_NETWORK + Name of the crossSiteNetwork to operate on. + + --endpoint-label=ENDPOINT_LABEL + The endpoint label for the wire group. + + --interconnect-label=INTERCONNECT_LABEL + The interconnect label for the wire group endpoint. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + These variants are also available: + + $ gcloud alpha compute interconnects wire-groups remove-interconnect + + $ gcloud beta compute interconnects wire-groups remove-interconnect + diff --git a/gcloud/compute/interconnects/wire-groups/update b/gcloud/compute/interconnects/wire-groups/update new file mode 100644 index 000000000..43561e82f --- /dev/null +++ b/gcloud/compute/interconnects/wire-groups/update @@ -0,0 +1,105 @@ +NAME + gcloud compute interconnects wire-groups update - update a Compute Engine + wire group + +SYNOPSIS + gcloud compute interconnects wire-groups update NAME + --cross-site-network=CROSS_SITE_NETWORK [--admin-enabled] + [--bandwidth-allocation=BANDWIDTH_ALLOCATION] + [--bandwidth-unmetered=BANDWIDTH_UNMETERED] [--description=DESCRIPTION] + [--fault-response=FAULT_RESPONSE] [--validate-only] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + gcloud compute interconnects wire-groups update is used to update wire + groups. + + For an example, refer to the EXAMPLES section below. + +EXAMPLES + To disable a wire group, run: + + $ gcloud compute interconnects wire-groups update example-wg \ + --cross-site-network=example-csn --no-admin-enabled + + To change a wire group's unmetered bandwidth, run: + + $ gcloud compute interconnects wire-groups update example-wg \ + --cross-site-network=example-csn --bandwidth-unmetered=5 + + To enable automatic failure detection for a wire group, run: + + $ gcloud compute interconnects wire-groups update example-wg \ + --cross-site-network=example-csn --fault-response=DISABLE_PORT + + To enable bandwidth sharing for a wire group, run: + + $ gcloud compute interconnects wire-groups update example-wg \ + --cross-site-network=example-csn \ + --bandwidth-allocation=SHARED_WITH_WIRE_GROUP + + To update a wire group's description, run: + + $ gcloud compute interconnects wire-groups update example-wg \ + --cross-site-network=example-csn --description="new description" + +POSITIONAL ARGUMENTS + NAME + Name of the wire group to update. + +REQUIRED FLAGS + --cross-site-network=CROSS_SITE_NETWORK + Name of the crossSiteNetwork to operate on. + +OPTIONAL FLAGS + --admin-enabled + Administrative status of the wire group. When this is enabled, the wire + group is operational and will carry traffic. Use --no-admin-enabled to + disable it. + + --bandwidth-allocation=BANDWIDTH_ALLOCATION + The bandwidth allocation for the wire group. BANDWIDTH_ALLOCATION must + be one of: + + ALLOCATE_PER_WIRE + Configures a separate unmetered bandwidth allocation (and + associated charges) for each wire in the group. + SHARED_WITH_WIRE_GROUP + Configures one unmetered bandwidth allocation for the wire group. + The unmetered bandwidth is divided equally across each wire in the + group, but dynamic throttling reallocates unused unmetered + bandwidth from unused or underused wires to other wires in the + group. + + --bandwidth-unmetered=BANDWIDTH_UNMETERED + The amount of unmetered bandwidth to assign to the wire group. + + --description=DESCRIPTION + An optional, textual description for the wire group. + + --fault-response=FAULT_RESPONSE + The fault response for the wire group. FAULT_RESPONSE must be one of: + + DISABLE_PORT + Disable port + NONE + None + + --validate-only + Validate the new configuration, but don't update 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 + These variants are also available: + + $ gcloud alpha compute interconnects wire-groups update + + $ gcloud beta compute interconnects wire-groups update + diff --git a/gcloud/compute/network-firewall-policies/create b/gcloud/compute/network-firewall-policies/create index 054d2cbd0..0f77d9e13 100644 --- a/gcloud/compute/network-firewall-policies/create +++ b/gcloud/compute/network-firewall-policies/create @@ -4,8 +4,8 @@ NAME SYNOPSIS gcloud compute network-firewall-policies create FIREWALL_POLICY - [--description=DESCRIPTION] [--global | --region=REGION] - [GCLOUD_WIDE_FLAG ...] + [--description=DESCRIPTION] [--policy-type=POLICY_TYPE] + [--global | --region=REGION] [GCLOUD_WIDE_FLAG ...] DESCRIPTION gcloud compute network-firewall-policies create is used to create network @@ -33,6 +33,10 @@ FLAGS --description=DESCRIPTION An optional, textual description for the network firewall policy. + --policy-type=POLICY_TYPE + Network firewall policy type. POLICY_TYPE must be one of: VPC_POLICY, + RDMA_ROCE_POLICY. + At most one of these can be specified: --global diff --git a/gcloud/compute/org-security-policies/associations/create b/gcloud/compute/org-security-policies/associations/create new file mode 100644 index 000000000..d32ddc873 --- /dev/null +++ b/gcloud/compute/org-security-policies/associations/create @@ -0,0 +1,80 @@ +NAME + gcloud compute org-security-policies associations create - create a new + association between a security policy and an organization or folder + resource + +SYNOPSIS + gcloud compute org-security-policies associations create + --security-policy=SECURITY_POLICY + [--excluded-folders=[EXCLUDED_FOLDERS,...]] + [--excluded-projects=[EXCLUDED_PROJECTS,...]] [--name=NAME] + [--organization=ORGANIZATION] [--replace-association-on-target] + [--folder=FOLDER | --project-number=PROJECT_NUMBER] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + gcloud compute org-security-policies associations create is used to create + organization security policy associations. An organization security policy + is a set of rules that controls access to various resources. + + This command has billing implications. Projects in the hierarchy with + effective hierarchical security policies will be automatically enrolled + into Cloud Armor Enterprise if not already enrolled. + +EXAMPLES + To associate an organization security policy under folder with ID 123456789 + to folder 987654321, run: + + $ gcloud compute org-security-policies associations create \ + --security-policy=123456789 --folder=987654321 + +REQUIRED FLAGS + --security-policy=SECURITY_POLICY + Security policy ID of the association. + +OPTIONAL FLAGS + --excluded-folders=[EXCLUDED_FOLDERS,...] + List of folders to exclude from the application of this security + policy. Folders should be specified in the form "folders/123". + + --excluded-projects=[EXCLUDED_PROJECTS,...] + List of projects to exclude from the application of this security + policy. Projects should be specified in the form "projects/123". + + --name=NAME + Name to identify this association. If unspecified, the name will be set + to "organization-{ORGANIZATION_ID}" or "folder-{FOLDER_ID}". + + --organization=ORGANIZATION + ID of the organization to associate the security policy with. Must be + set if SECURITY_POLICY is short name. + + --replace-association-on-target + By default, if you attempt to insert an association to an organization + or folder resource that is already associated with a security policy + the method will fail. If this is set, the existing association will be + deleted at the same time that the new association is created. + + At most one of these can be specified: + + --folder=FOLDER + ID of the folder to associate the security policy with. + + --project-number=PROJECT_NUMBER + Project number to associate the security policy with. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + These variants are also available: + + $ gcloud alpha compute org-security-policies associations create + + $ gcloud beta compute org-security-policies associations create + diff --git a/gcloud/compute/org-security-policies/associations/delete b/gcloud/compute/org-security-policies/associations/delete new file mode 100644 index 000000000..05649d6b7 --- /dev/null +++ b/gcloud/compute/org-security-policies/associations/delete @@ -0,0 +1,48 @@ +NAME + gcloud compute org-security-policies associations delete - delete a Compute + Engine organization security policy association + +SYNOPSIS + gcloud compute org-security-policies associations delete NAME + --security-policy=SECURITY_POLICY [--organization=ORGANIZATION] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + gcloud compute org-security-policies associations delete is used to delete + organization security policy association. + +EXAMPLES + To delete an association with name example-association of an organization + security policy with ID 123456789, run: + + $ gcloud compute org-security-policies associations delete \ + example-association --security-policy=123456789 + +POSITIONAL ARGUMENTS + NAME + Name of the association to delete. + +REQUIRED FLAGS + --security-policy=SECURITY_POLICY + short name or ID of the security policy ID of the association. + +OPTIONAL FLAGS + --organization=ORGANIZATION + ID of the organization in which the security policy is to be detached. + Must be set if SECURITY_POLICY is short name. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + These variants are also available: + + $ gcloud alpha compute org-security-policies associations delete + + $ gcloud beta compute org-security-policies associations delete + diff --git a/gcloud/compute/org-security-policies/associations/help b/gcloud/compute/org-security-policies/associations/help new file mode 100644 index 000000000..82bfc60cd --- /dev/null +++ b/gcloud/compute/org-security-policies/associations/help @@ -0,0 +1,37 @@ +NAME + gcloud compute org-security-policies associations - read and manipulate + Compute Engine organization security policy associations + +SYNOPSIS + gcloud compute org-security-policies associations COMMAND + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Read and manipulate Compute Engine organization security policy + associations. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + create + Create a new association between a security policy and an organization + or folder resource. + + delete + Delete a Compute Engine organization security policy association. + + list + List the associations of an organization or folder resource. + +NOTES + These variants are also available: + + $ gcloud alpha compute org-security-policies associations + + $ gcloud beta compute org-security-policies associations + diff --git a/gcloud/compute/tpus/list b/gcloud/compute/org-security-policies/associations/list similarity index 57% rename from gcloud/compute/tpus/list rename to gcloud/compute/org-security-policies/associations/list index 552b830ca..4d055d5cf 100644 --- a/gcloud/compute/tpus/list +++ b/gcloud/compute/org-security-policies/associations/list @@ -1,44 +1,31 @@ NAME - gcloud compute tpus list - list Cloud TPUs + gcloud compute org-security-policies associations list - list the + associations of an organization or folder resource SYNOPSIS - gcloud compute tpus list [--zone=ZONE] [--filter=EXPRESSION] + gcloud compute org-security-policies associations list + (--folder=FOLDER | --organization=ORGANIZATION) [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (DEPRECATED) This command is being deprecated. Please use gcloud compute - tpus tpu-vm list instead. - - List Cloud TPUs + gcloud compute org-security-policies associations list is used to list the + associations of an organization or folder resource. EXAMPLES - The following command lists the status of TPUs in zone us-central1-b: + To list the associations of the folder with ID 987654321, run: - $ gcloud compute tpus list --zone=us-central1-b + $ gcloud compute org-security-policies associations list \ + --folder=987654321 -FLAGS - Location resource - The compute/zone of the Cloud TPU. +REQUIRED FLAGS + Exactly one of these must be specified: - If not specified, will use the value of the [compute/zone] property in the - current gcloud configuration. To find a list of compute zones available - for Cloud TPUs in your project, run gcloud compute tpus locations list. - This represents a Cloud resource. (NOTE) Some attributes are not given - arguments in this group but can be set in other ways. + --folder=FOLDER + ID of the folder with which the association is listed. - To set the project attribute: - ◆ provide the argument --zone on the command line with a fully - specified name; - ◆ set the property compute/zone with a fully specified name; - ◆ provide the argument --project on the command line; - ◆ set the property core/project. - - --zone=ZONE - ID of the location or fully qualified identifier for the location. - - To set the zone attribute: - ▸ provide the argument --zone on the command line; - ▸ set the property compute/zone. + --organization=ORGANIZATION + ID of the organization with which the association is listed. LIST COMMAND FLAGS --filter=EXPRESSION @@ -80,14 +67,10 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. -API REFERENCE - This command uses the tpu/v1 API. The full documentation for this API can - be found at: https://cloud.google.com/tpu/ - NOTES These variants are also available: - $ gcloud alpha compute tpus list + $ gcloud alpha compute org-security-policies associations list - $ gcloud beta compute tpus list + $ gcloud beta compute org-security-policies associations list diff --git a/gcloud/compute/org-security-policies/copy-rules b/gcloud/compute/org-security-policies/copy-rules new file mode 100644 index 000000000..5afa4b815 --- /dev/null +++ b/gcloud/compute/org-security-policies/copy-rules @@ -0,0 +1,50 @@ +NAME + gcloud compute org-security-policies copy-rules - replace the rules of a + Compute Engine organization security policy with rules from another + policy + +SYNOPSIS + gcloud compute org-security-policies copy-rules SECURITY_POLICY + --source-security-policy=SOURCE_SECURITY_POLICY + [--organization=ORGANIZATION] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + gcloud compute org-security-policies copy-rules is used to replace the + rules of organization security policies. An organization security policy is + a set of rules that controls access to various resources. + +EXAMPLES + To copy the rules of an organization security policy with ID 123456789, + from another organization security policy with ID 987654321, run: + + $ gcloud compute org-security-policies copy-rules 123456789 \ + --source-security-policy=987654321 + +POSITIONAL ARGUMENTS + SECURITY_POLICY + Short name or ID of the security policy to copy the rules to. + +REQUIRED FLAGS + --source-security-policy=SOURCE_SECURITY_POLICY + The URL of the source security policy to copy the rules from. + +OPTIONAL FLAGS + --organization=ORGANIZATION + Organization in which the organization security policy to copy the + rules to. Must be set if security-policy is the short name. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + These variants are also available: + + $ gcloud alpha compute org-security-policies copy-rules + + $ gcloud beta compute org-security-policies copy-rules + diff --git a/gcloud/compute/org-security-policies/create b/gcloud/compute/org-security-policies/create new file mode 100644 index 000000000..eaf81707f --- /dev/null +++ b/gcloud/compute/org-security-policies/create @@ -0,0 +1,83 @@ +NAME + gcloud compute org-security-policies create - create a Compute Engine + organization security policy + +SYNOPSIS + gcloud compute org-security-policies create + (--folder=FOLDER | --organization=ORGANIZATION) + [--description=DESCRIPTION] [--display-name=DISPLAY_NAME] + [--file-format=FILE_FORMAT] [--short-name=SHORT_NAME] + [--file-name=FILE_NAME | --type=SECURITY_POLICY_TYPE] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + gcloud compute org-security-policies create is used to create organization + security policies. An organization security policy is a set of rules that + controls access to various resources. + +EXAMPLES + To create an organization security policy under folder with ID 123456789, + run: + + $ gcloud compute org-security-policies create \ + --short-name=my-policy --folder=123456789 + + To create an organization security under organization with ID 12345 from an + input file, run: + + $ gcloud compute org-security-policies create \ + --file-name=my-file-name --organization=12345 + +REQUIRED FLAGS + Exactly one of these must be specified: + + --folder=FOLDER + Folder in which the organization security policy is to be created. + + --organization=ORGANIZATION + Organization in which the organization security policy is to be + created. + +OPTIONAL FLAGS + --description=DESCRIPTION + An optional, textual description for the organization security policy. + + --display-name=DISPLAY_NAME + A textual name of the security policy. + + --file-format=FILE_FORMAT + The format of the file to create the organization security policy + config from. Specify either yaml or json. Defaults to yaml if not + specified. Will be ignored if --file-name is not specified. FILE_FORMAT + must be one of: json, yaml. + + --short-name=SHORT_NAME + A textual name of the security policy. + + Creation options. + + At most one of these can be specified: + + --file-name=FILE_NAME + The name of the JSON or YAML file to create a organization security + policy config from. + + --type=SECURITY_POLICY_TYPE + The type indicates the intended use of the organization security + policy. SECURITY_POLICY_TYPE must be one of: CLOUD_ARMOR, FIREWALL. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + These variants are also available: + + $ gcloud alpha compute org-security-policies create + + $ gcloud beta compute org-security-policies create + diff --git a/gcloud/compute/org-security-policies/delete b/gcloud/compute/org-security-policies/delete new file mode 100644 index 000000000..e8c2189c1 --- /dev/null +++ b/gcloud/compute/org-security-policies/delete @@ -0,0 +1,42 @@ +NAME + gcloud compute org-security-policies delete - delete a Compute Engine + organization security policy + +SYNOPSIS + gcloud compute org-security-policies delete SECURITY_POLICY + [--organization=ORGANIZATION] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + gcloud compute org-security-policies delete is used to delete organization + security policies. An organization security policy is a set of rules that + controls access to various resources. + +EXAMPLES + To delete an organization security policy with ID 123456789, run: + + $ gcloud compute org-security-policies delete 123456789 + +POSITIONAL ARGUMENTS + SECURITY_POLICY + Short name or ID of the security policy to delete. + +FLAGS + --organization=ORGANIZATION + Organization in which the organization security policy is to be + deleted. Must be set if SECURITY_POLICY is short name. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + These variants are also available: + + $ gcloud alpha compute org-security-policies delete + + $ gcloud beta compute org-security-policies delete + diff --git a/gcloud/compute/org-security-policies/describe b/gcloud/compute/org-security-policies/describe new file mode 100644 index 000000000..1fbfac76a --- /dev/null +++ b/gcloud/compute/org-security-policies/describe @@ -0,0 +1,42 @@ +NAME + gcloud compute org-security-policies describe - describe a Compute Engine + organization security policy + +SYNOPSIS + gcloud compute org-security-policies describe SECURITY_POLICY + [--organization=ORGANIZATION] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + gcloud compute org-security-policies describe is used to describe + organization security policies. An organization security policy is a set of + rules that controls access to various resources. + +EXAMPLES + To describe an organization security policy with ID 123456789, run: + + $ gcloud compute org-security-policies describe 123456789 + +POSITIONAL ARGUMENTS + SECURITY_POLICY + Short name or ID of the security policy to describe. + +FLAGS + --organization=ORGANIZATION + Organization in which the organization security policy is to be + described. Must be set if SECURITY_POLICY is short name. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + These variants are also available: + + $ gcloud alpha compute org-security-policies describe + + $ gcloud beta compute org-security-policies describe + diff --git a/gcloud/compute/org-security-policies/help b/gcloud/compute/org-security-policies/help new file mode 100644 index 000000000..7bce1b786 --- /dev/null +++ b/gcloud/compute/org-security-policies/help @@ -0,0 +1,61 @@ +NAME + gcloud compute org-security-policies - manage Compute Engine organization + security policies + +SYNOPSIS + gcloud compute org-security-policies GROUP | COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Manage Compute Engine organization security policies. Organization security + policies are used to control incoming/outgoing traffic. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +GROUPS + GROUP is one of the following: + + associations + Read and manipulate Compute Engine organization security policy + associations. + + rules + Read and manipulate Compute Engine organization security policy rules. + +COMMANDS + COMMAND is one of the following: + + copy-rules + Replace the rules of a Compute Engine organization security policy with + rules from another policy. + + create + Create a Compute Engine organization security policy. + + delete + Delete a Compute Engine organization security policy. + + describe + Describe a Compute Engine organization security policy. + + list + List Compute Engine organization security policies. + + list-rules + List the rules of a Compute Engine organization security policy. + + move + Move a Compute Engine organization security policy. + + update + Update a Compute Engine organization security policy. + +NOTES + These variants are also available: + + $ gcloud alpha compute org-security-policies + + $ gcloud beta compute org-security-policies + diff --git a/gcloud/compute/org-security-policies/list b/gcloud/compute/org-security-policies/list new file mode 100644 index 000000000..f8b278121 --- /dev/null +++ b/gcloud/compute/org-security-policies/list @@ -0,0 +1,93 @@ +NAME + gcloud compute org-security-policies list - list Compute Engine + organization security policies + +SYNOPSIS + gcloud compute org-security-policies list [NAME ...] + (--folder=FOLDER | --organization=ORGANIZATION) + [--regexp=REGEXP, -r REGEXP] [--filter=EXPRESSION] [--limit=LIMIT] + [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + gcloud compute org-security-policies list is used to list organization + security policies. An organization security policy is a set of rules that + controls access to various resources. + +EXAMPLES + To list organization security policies under folder with ID 123456789, run: + + $ gcloud compute org-security-policies list --folder=123456789 + +POSITIONAL ARGUMENTS + [NAME ...] + (DEPRECATED) If provided, show details for the specified names and/or + URIs of resources. + + Argument NAME is deprecated. Use --filter="name=( 'NAME' ... )" + instead. + +REQUIRED FLAGS + Exactly one of these must be specified: + + --folder=FOLDER + Folder in which security policies are listed + + --organization=ORGANIZATION + Organization in which security policies are listed + +FLAGS + --regexp=REGEXP, -r REGEXP + (DEPRECATED) Regular expression to filter the names of the results on. + Any names that do not match the entire regular expression will be + filtered out. + + Flag --regexp is deprecated. Use --filter="name~'REGEXP'" instead. + +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 + These variants are also available: + + $ gcloud alpha compute org-security-policies list + + $ gcloud beta compute org-security-policies list + diff --git a/gcloud/compute/org-security-policies/list-rules b/gcloud/compute/org-security-policies/list-rules new file mode 100644 index 000000000..b5f1df3d0 --- /dev/null +++ b/gcloud/compute/org-security-policies/list-rules @@ -0,0 +1,107 @@ +NAME + gcloud compute org-security-policies list-rules - list the rules of a + Compute Engine organization security policy + +SYNOPSIS + gcloud compute org-security-policies list-rules SECURITY_POLICY [NAME ...] + [--organization=ORGANIZATION] [--regexp=REGEXP, -r REGEXP] + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + gcloud compute org-security-policies list-rules is used to list the rules + of an organization security policy. + +EXAMPLES + To list the rules of an organization security policy with ID 123456789, + run: + + $ gcloud compute org-security-policies list-rules 123456789 + + To list all the fields of the rules of an organization security policy with + ID 123456789, run: + + $ gcloud compute org-security-policies list-rules list-rules \ + 123456789 --format="table( + priority, + action, + direction, + match.config.srcIpRanges.list():label=SRC_RANGES, + match.config.destIpRanges.list():label=DEST_RANGES, + match.config.layer4Configs.map().org_firewall_rule().list():label=PORT_RANGES, + targetServiceAccounts.list():label=TARGET_SVC_ACCT, + targetResources:label=TARGET_RESOURCES, + ruleTupleCount, + enableLogging, + description)" + +POSITIONAL ARGUMENTS + SECURITY_POLICY + Short name or ID of the security policy to list rules for. + + [NAME ...] + (DEPRECATED) If provided, show details for the specified names and/or + URIs of resources. + + Argument NAME is deprecated. Use --filter="name=( 'NAME' ... )" + instead. + +FLAGS + --organization=ORGANIZATION + Organization which the organization security policy belongs to. Must be + set if SECURITY_POLICY is display name. + + --regexp=REGEXP, -r REGEXP + (DEPRECATED) Regular expression to filter the names of the results on. + Any names that do not match the entire regular expression will be + filtered out. + + Flag --regexp is deprecated. Use --filter="name~'REGEXP'" instead. + +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 + These variants are also available: + + $ gcloud alpha compute org-security-policies list-rules + + $ gcloud beta compute org-security-policies list-rules + diff --git a/gcloud/compute/org-security-policies/move b/gcloud/compute/org-security-policies/move new file mode 100644 index 000000000..ce4e82a6a --- /dev/null +++ b/gcloud/compute/org-security-policies/move @@ -0,0 +1,46 @@ +NAME + gcloud compute org-security-policies move - move a Compute Engine + organization security policy + +SYNOPSIS + gcloud compute org-security-policies move SECURITY_POLICY [--folder=FOLDER] + [--organization=ORGANIZATION] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + gcloud compute org-security-policies move is used to move is used to move + organization security policies to new parent nodes. + +EXAMPLES + To move an organization security policy under folder with ID 123456789 to + folder 987654321, run: + + $ gcloud compute org-security-policies move 123456789 \ + --folder=987654321 + +POSITIONAL ARGUMENTS + SECURITY_POLICY + Short name or ID of the security policy to move. + +FLAGS + --folder=FOLDER + Folder to which the organization security policy is to be moved. + + --organization=ORGANIZATION + Organization in which the organization security policy is to be moved. + Must be set if SECURITY_POLICY is the short name. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + These variants are also available: + + $ gcloud alpha compute org-security-policies move + + $ gcloud beta compute org-security-policies move + diff --git a/gcloud/compute/org-security-policies/rules/add-preconfig-waf-exclusion b/gcloud/compute/org-security-policies/rules/add-preconfig-waf-exclusion new file mode 100644 index 000000000..786fe8533 --- /dev/null +++ b/gcloud/compute/org-security-policies/rules/add-preconfig-waf-exclusion @@ -0,0 +1,148 @@ +NAME + gcloud compute org-security-policies rules add-preconfig-waf-exclusion - + add an exclusion configuration for preconfigured WAF evaluation into a + security policy rule + +SYNOPSIS + gcloud compute org-security-policies rules add-preconfig-waf-exclusion + PRIORITY --security-policy=SECURITY_POLICY + --target-rule-set=TARGET_RULE_SET [--organization=ORGANIZATION] + [--request-cookie-to-exclude=[op=OP],[val=VAL]] + [--request-header-to-exclude=[op=OP],[val=VAL]] + [--request-query-param-to-exclude=[op=OP],[val=VAL]] + [--request-uri-to-exclude=[op=OP],[val=VAL]] + [--target-rule-ids=[RULE_ID,...]] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + gcloud compute org-security-policies rules add-preconfig-waf-exclusion is + used to add an exclusion configuration for preconfigured WAF evaluation + into a security policy rule. + + Note that request field exclusions are associated with a target, which can + be a single rule set, or a rule set plus a list of rule IDs under the rule + set. + +EXAMPLES + To add specific request field exclusions that are associated with the + target of 'sqli-stable': ['owasp-crs-v030001-id942110-sqli', + 'owasp-crs-v030001-id942120-sqli'], run: + + $ gcloud compute org-security-policies rules \ + add-preconfig-waf-exclusion 1000 --security-policy=1234567890 \ + --target-rule-set=sqli-stable \ + --target-rule-ids=owasp-crs-v030001-id942110-sqli,\ + owasp-crs-v030001-id942120-sqli \ + --request-header-to-exclude='op=EQUALS,val=abc' \ + --request-header-to-exclude='op=STARTS_WITH,val=xyz' \ + --request-uri-to-exclude='op=EQUALS_ANY' + + To add specific request field exclusions that are associated with the + target of 'sqli-stable': [], run: + + $ gcloud compute org-security-policies rules \ + add-preconfig-waf-exclusion 1000 --security-policy=1234567890 \ + --target-rule-set=sqli-stable \ + --request-cookie-to-exclude='op=EQUALS_ANY' + +POSITIONAL ARGUMENTS + PRIORITY + Priority of the security policy rule to add preconfig WAF exclusion. + +REQUIRED FLAGS + --security-policy=SECURITY_POLICY + short name of the security policy into which the rule should be + updated. + + --target-rule-set=TARGET_RULE_SET + Target WAF rule set where the request field exclusions being added + would apply. + + This, together with the target rule IDs (if given), determines the + target for associating request field exclusions. See --target-rule-ids. + +OPTIONAL FLAGS + --organization=ORGANIZATION + Organization which the organization security policy belongs to. Must be + set if SECURITY_POLICY is short name. + + --request-cookie-to-exclude=[op=OP],[val=VAL] + Adds a request cookie to the request field exclusions associated with + the rule set and rule IDs (if given). This specifies a request cookie + whose value will be excluded from inspection during preconfigured WAF + evaluation. + + You can specify an exact match or a partial match by using a field + operator and a field value. Available field operators are: + ◆ EQUALS: the operator matches if the field value equals the + specified value. + ◆ STARTS_WITH: the operator matches if the field value starts with + the specified value. + ◆ ENDS_WITH: the operator matches if the field value ends with the + specified value. + ◆ CONTAINS: the operator matches if the field value contains the + specified value. + ◆ EQUALS_ANY: the operator matches if the field value is any value. + + A field value must be given if the field operator is not EQUALS_ANY, + and cannot be given if the field operator is EQUALS_ANY. For example, + --request-header-to-exclude op=EQUALS,val=abc or + --request-header-to-exclude op=EQUALS_ANY. + + This flag can be repeated to specify multiple request headers to + exclude. For example, --request-header-to-exclude op=EQUALS,val=abc + --request-header-to-exclude op=STARTS_WITH,val=xyz. + + --request-header-to-exclude=[op=OP],[val=VAL] + Adds a request header to the request field exclusions associated with + the rule set and rule IDs (if given). This specifies a request header + whose value will be excluded from inspection during preconfigured WAF + evaluation. + + Refer to the syntax under --request-cookie-to-exclude. + + This flag can be repeated to specify multiple request headers. + + --request-query-param-to-exclude=[op=OP],[val=VAL] + Adds a request query parameter to the request field exclusions + associated with the rule set and rule IDs (if given). This specifies a + request query parameter in the query string or in the POST body whose + value will be excluded from inspection during preconfigured WAF + evaluation. + + Refer to the syntax under --request-cookie-to-exclude. + + This flag can be repeated to specify multiple request query parameters. + + --request-uri-to-exclude=[op=OP],[val=VAL] + Adds a request URI to the request field exclusions associated with the + rule set and rule IDs (if given). This specifies a request URI from the + request line to be excluded from inspection during preconfigured WAF + evaluation. + + Refer to the syntax under --request-cookie-to-exclude. + + This flag can be repeated to specify multiple request URIs. + + --target-rule-ids=[RULE_ID,...] + A comma-separated list of target rule IDs under the WAF rule set where + the request field exclusions being added would apply. If omitted, the + added request field exclusions will be associated with the rule set + only, which would apply to all the rule IDs under the rule set. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + These variants are also available: + + $ gcloud alpha compute org-security-policies rules \ + add-preconfig-waf-exclusion + + $ gcloud beta compute org-security-policies rules \ + add-preconfig-waf-exclusion + diff --git a/gcloud/compute/org-security-policies/rules/create b/gcloud/compute/org-security-policies/rules/create new file mode 100644 index 000000000..c48ff85c6 --- /dev/null +++ b/gcloud/compute/org-security-policies/rules/create @@ -0,0 +1,122 @@ +NAME + gcloud compute org-security-policies rules create - create a Compute Engine + organizationsecurity policy rule + +SYNOPSIS + gcloud compute org-security-policies rules create PRIORITY --action=ACTION + --security-policy=SECURITY_POLICY [--cloud-armor] + [--description=DESCRIPTION] [--dest-ip-ranges=[DEST_IP_RANGE,...]] + [--direction=DIRECTION] [--[no-]enable-logging] + [--layer4-configs=[LAYER4_CONFIG,...]] [--organization=ORGANIZATION] + [--preview] [--target-resources=[TARGET_RESOURCES,...]] + [--target-service-accounts=[TARGET_SERVICE_ACCOUNTS,...]] + [--expression=EXPRESSION | --src-ip-ranges=[SRC_IP_RANGE,...]] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + gcloud compute org-security-policies rules create is used to create + organization security policy rules. + +EXAMPLES + To create a rule with priority 10 in an organization security policy with + ID 123456789, run: + + $ gcloud compute org-security-policies rules create 10 \ + --security-policy=123456789 --action=allow \ + --description=example-rule --cloud-armor + +POSITIONAL ARGUMENTS + PRIORITY + Priority of the security policy rule to create. + +REQUIRED FLAGS + --action=ACTION + Action to take if the request matches the match condition. ACTION must + be one of: + + allow + Allows the request from HTTP(S) Load Balancing. + deny + (DEPRECATED) Only used for Hierarchical Firewalls. + deny-403 + Denies the request from HTTP(S) Load Balancing, with an HTTP + response status code of 403. + deny-404 + Denies the request from HTTP(S) Load Balancing, with an HTTP + response status code of 404. + deny-502 + Denies the request from HTTP(S) Load Balancing, with an HTTP + response status code of 502. + goto-next + Defers enforcement to the next policy in the hierarchy. + redirect + Redirects the request from HTTP(S) Load Balancing, based on + redirect options. + + --security-policy=SECURITY_POLICY + short name of the security policy into which the rule should be + inserted. + +OPTIONAL FLAGS + --cloud-armor + Specified for Hierarchical Cloud Armor rules. + + --description=DESCRIPTION + An optional, textual description for the rule. + + --dest-ip-ranges=[DEST_IP_RANGE,...] + Destination IP ranges to match for this rule. Can only be specified if + DIRECTION is egress. + + --direction=DIRECTION + Direction of the traffic the rule is applied. The default is to apply + on incoming traffic. DIRECTION must be one of: INGRESS, EGRESS. + + --[no-]enable-logging + Use this flag to enable logging of connections that allowed or denied + by this rule. Use --enable-logging to enable and --no-enable-logging to + disable. + + --layer4-configs=[LAYER4_CONFIG,...] + A list of destination protocols and ports to which the firewall rule + will apply. + + --organization=ORGANIZATION + Organization which the organization security policy belongs to. Must be + set if SECURITY_POLICY is short name. + + --preview + If specified, the action will not be enforced. + + --target-resources=[TARGET_RESOURCES,...] + List of URLs of target resources to which the rule is applied. + + --target-service-accounts=[TARGET_SERVICE_ACCOUNTS,...] + List of target service accounts for the rule. + + Security policy rule matcher. + + At most one of these can be specified: + + --expression=EXPRESSION + The Cloud Armor rules language expression to match for this rule. + + --src-ip-ranges=[SRC_IP_RANGE,...] + The source IPs/IP ranges to match for this rule. To match all IPs + specify *. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + These variants are also available: + + $ gcloud alpha compute org-security-policies rules create + + $ gcloud beta compute org-security-policies rules create + diff --git a/gcloud/compute/org-security-policies/rules/delete b/gcloud/compute/org-security-policies/rules/delete new file mode 100644 index 000000000..d3abb16e8 --- /dev/null +++ b/gcloud/compute/org-security-policies/rules/delete @@ -0,0 +1,49 @@ +NAME + gcloud compute org-security-policies rules delete - delete a Compute Engine + organization security policy rule + +SYNOPSIS + gcloud compute org-security-policies rules delete PRIORITY + --security-policy=SECURITY_POLICY [--organization=ORGANIZATION] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + gcloud compute org-security-policies rules delete is used to delete + organization security policy rule. + +EXAMPLES + To delete a rule with priority 10 in an organization security policy with + ID 123456789, run: + + $ gcloud compute org-security-policies rules delete 10 \ + --security-policy=123456789 + +POSITIONAL ARGUMENTS + PRIORITY + Priority of the security policy rule to delete. + +REQUIRED FLAGS + --security-policy=SECURITY_POLICY + short name of the security policy into which the rule should be + deleted. + +OPTIONAL FLAGS + --organization=ORGANIZATION + Organization which the organization security policy belongs to. Must be + set if SECURITY_POLICY is short name. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + These variants are also available: + + $ gcloud alpha compute org-security-policies rules delete + + $ gcloud beta compute org-security-policies rules delete + diff --git a/gcloud/compute/org-security-policies/rules/describe b/gcloud/compute/org-security-policies/rules/describe new file mode 100644 index 000000000..f51ca0976 --- /dev/null +++ b/gcloud/compute/org-security-policies/rules/describe @@ -0,0 +1,49 @@ +NAME + gcloud compute org-security-policies rules describe - describe a Compute + Engine organization security policy rule + +SYNOPSIS + gcloud compute org-security-policies rules describe PRIORITY + --security-policy=SECURITY_POLICY [--organization=ORGANIZATION] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + gcloud compute org-security-policies rules describe is used to describe + organization security policy rule. + +EXAMPLES + To describe a rule with priority 10 in an organization security policy with + ID 123456789, run: + + $ gcloud compute org-security-policies rules describe 10 \ + --security-policy=123456789 + +POSITIONAL ARGUMENTS + PRIORITY + Priority of the security policy rule to describe. + +REQUIRED FLAGS + --security-policy=SECURITY_POLICY + short name of the security policy into which the rule should be + described. + +OPTIONAL FLAGS + --organization=ORGANIZATION + Organization which the organization security policy belongs to. Must be + set if SECURITY_POLICY is short name. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + These variants are also available: + + $ gcloud alpha compute org-security-policies rules describe + + $ gcloud beta compute org-security-policies rules describe + diff --git a/gcloud/compute/org-security-policies/rules/help b/gcloud/compute/org-security-policies/rules/help new file mode 100644 index 000000000..12eb54400 --- /dev/null +++ b/gcloud/compute/org-security-policies/rules/help @@ -0,0 +1,45 @@ +NAME + gcloud compute org-security-policies rules - read and manipulate Compute + Engine organization security policy rules + +SYNOPSIS + gcloud compute org-security-policies rules COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Read and manipulate Compute Engine organization security policy rules. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + add-preconfig-waf-exclusion + Add an exclusion configuration for preconfigured WAF evaluation into a + security policy rule. + + create + Create a Compute Engine organizationsecurity policy rule. + + delete + Delete a Compute Engine organization security policy rule. + + describe + Describe a Compute Engine organization security policy rule. + + remove-preconfig-waf-exclusion + Remove an exclusion configuration for preconfigured WAF evaluation from + a security policy rule. + + update + Update a Compute Engine security policy rule. + +NOTES + These variants are also available: + + $ gcloud alpha compute org-security-policies rules + + $ gcloud beta compute org-security-policies rules + diff --git a/gcloud/compute/org-security-policies/rules/remove-preconfig-waf-exclusion b/gcloud/compute/org-security-policies/rules/remove-preconfig-waf-exclusion new file mode 100644 index 000000000..c3d263270 --- /dev/null +++ b/gcloud/compute/org-security-policies/rules/remove-preconfig-waf-exclusion @@ -0,0 +1,166 @@ +NAME + gcloud compute org-security-policies rules remove-preconfig-waf-exclusion - + remove an exclusion configuration for preconfigured WAF evaluation from + a security policy rule + +SYNOPSIS + gcloud compute org-security-policies rules remove-preconfig-waf-exclusion + PRIORITY --security-policy=SECURITY_POLICY + --target-rule-set=TARGET_RULE_SET [--organization=ORGANIZATION] + [--request-cookie-to-exclude=[op=OP],[val=VAL]] + [--request-header-to-exclude=[op=OP],[val=VAL]] + [--request-query-param-to-exclude=[op=OP],[val=VAL]] + [--request-uri-to-exclude=[op=OP],[val=VAL]] + [--target-rule-ids=[RULE_ID,...]] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + gcloud compute org-security-policies rules remove-preconfig-waf-exclusion + is used to remove an exclusion configuration for preconfigured WAF + evaluation from a security policy rule. + + Note that request field exclusions are associated with a target, which can + be a single rule set, or a rule set plus a list of rule IDs under the rule + set. + + It is possible to remove request field exclusions at 3 levels: + ▪ Remove specific request field exclusions that are associated with a + matching target. + ▪ Remove all the request field exclusions that are associated with a + matching target. + ▪ Remove all the request field exclusions that are configured under the + security policy rule, regardless of the target. + +EXAMPLES + To remove specific request field exclusions that are associated with the + target of 'sqli-stable': ['owasp-crs-v030001-id942110-sqli', + 'owasp-crs-v030001-id942120-sqli'], run: + + $ gcloud compute org-security-policies rules \ + remove-preconfig-waf-exclusion 1000 \ + --security-policy=1234567890 --target-rule-set=sqli-stable \ + --target-rule-ids='owasp-crs-v030001-id942110-sqli',\ + 'owasp-crs-v030001-id942120-sqli' \ + --request-header-to-exclude='op=EQUALS,val=abc' \ + --request-header-to-exclude='op=STARTS_WITH,val=xyz' \ + --request-uri-to-exclude='op=EQUALS_ANY' + + To remove all the request field exclusions that are associated with the + target of 'sqli-stable': ['owasp-crs-v030001-id942110-sqli', + 'owasp-crs-v030001-id942120-sqli'], run: + + $ gcloud compute org-security-policies rules \ + remove-preconfig-waf-exclusion 1000 \ + --security-policy=1234567890 --target-rule-set=sqli-stable \ + --target-rule-ids='owasp-crs-v030001-id942110-sqli',\ + 'owasp-crs-v030001-id942120-sqli' + + To remove all the request field exclusions that are associated with the + target of 'sqli-stable': [], run: + + $ gcloud compute org-security-policies rules \ + remove-preconfig-waf-exclusion 1000 \ + --security-policy=1234567890 --target-rule-set=sqli-stable + + To remove all the request field exclusions that are configured under the + security policy rule, regardless of the target, run: + + $ gcloud compute org-security-policies rules \ + remove-preconfig-waf-exclusion 1000 \ + --security-policy=1234567890 --target-rule-set=* + +POSITIONAL ARGUMENTS + PRIORITY + Priority of the security policy rule to remove preconfig WAF exclusion. + +REQUIRED FLAGS + --security-policy=SECURITY_POLICY + short name of the security policy into which the rule should be + updated. + + --target-rule-set=TARGET_RULE_SET + Target WAF rule set from where to remove the request field exclusions. + + This, together with the target rule IDs (if given), determines the + target for associating request field exclusions. See --target-rule-ids. + + Note that the removal of request field exclusions is restricted to + those associated with a matching target. Set this flag to * if you want + to remove request field exclusions regardless of the target. + +OPTIONAL FLAGS + --organization=ORGANIZATION + Organization which the organization security policy belongs to. Must be + set if SECURITY_POLICY is short name. + + --request-cookie-to-exclude=[op=OP],[val=VAL] + Removes a request cookie from the existing request field exclusions + associated with the rule set and rule IDs (if given). + + You can specify an exact match or a partial match by using a field + operator and a field value. Available field operators are: + ◆ EQUALS: the operator matches if the field value equals the + specified value. + ◆ STARTS_WITH: the operator matches if the field value starts with + the specified value. + ◆ ENDS_WITH: the operator matches if the field value ends with the + specified value. + ◆ CONTAINS: the operator matches if the field value contains the + specified value. + ◆ EQUALS_ANY: the operator matches if the field value is any value. + + A field value must be given if the field operator is not EQUALS_ANY, + and cannot be given if the field operator is EQUALS_ANY. For example, + --request-header-to-exclude op=EQUALS,val=abc or + --request-header-to-exclude op=EQUALS_ANY. + + This flag can be repeated to specify multiple request headers to + exclude. For example, --request-header-to-exclude op=EQUALS,val=abc + --request-header-to-exclude op=STARTS_WITH,val=xyz. + + --request-header-to-exclude=[op=OP],[val=VAL] + Removes a request header from the existing request field exclusions + associated with the rule set and rule IDs (if given). + + Refer to the syntax under --request-cookie-to-exclude. + + This flag can be repeated to specify multiple request headers. + + --request-query-param-to-exclude=[op=OP],[val=VAL] + Removes a request query parameter from the existing request field + exclusions associated with the rule set and rule IDs (if given). + + Refer to the syntax under --request-cookie-to-exclude. + + This flag can be repeated to specify multiple request query parameters. + + --request-uri-to-exclude=[op=OP],[val=VAL] + Removes a request URI from the existing request field exclusions + associated with the rule set and rule IDs (if given). + + Refer to the syntax under --request-cookie-to-exclude. + + This flag can be repeated to specify multiple request URIs. + + --target-rule-ids=[RULE_ID,...] + A comma-separated list of target rule IDs under the WAF rule set from + where to remove the request field exclusions. If omitted, the removal + of request field exclusions is restricted to those associated with the + rule set only, without specific rule IDs. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + These variants are also available: + + $ gcloud alpha compute org-security-policies rules \ + remove-preconfig-waf-exclusion + + $ gcloud beta compute org-security-policies rules \ + remove-preconfig-waf-exclusion + diff --git a/gcloud/compute/org-security-policies/rules/update b/gcloud/compute/org-security-policies/rules/update new file mode 100644 index 000000000..c7aa236b6 --- /dev/null +++ b/gcloud/compute/org-security-policies/rules/update @@ -0,0 +1,128 @@ +NAME + gcloud compute org-security-policies rules update - update a Compute Engine + security policy rule + +SYNOPSIS + gcloud compute org-security-policies rules update PRIORITY + --security-policy=SECURITY_POLICY [--action=ACTION] [--cloud-armor] + [--description=DESCRIPTION] [--dest-ip-ranges=[DEST_IP_RANGE,...]] + [--direction=DIRECTION] [--[no-]enable-logging] + [--layer4-configs=[LAYER4_CONFIG,...]] [--new-priority=NEW_PRIORITY] + [--organization=ORGANIZATION] [--[no-]preview] + [--target-resources=[TARGET_RESOURCES,...]] + [--target-service-accounts=[TARGET_SERVICE_ACCOUNTS,...]] + [--expression=EXPRESSION | --src-ip-ranges=[SRC_IP_RANGE,...]] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + gcloud compute org-security-policies rules update is used to update + organization security policy rules. + +EXAMPLES + To update a rule with priority 10 in an organization security policy with + ID 123456789 to change the action to allow and description to + new-example-rule, run: + + $ gcloud compute org-security-policies rules update 10 \ + --security-policy=123456789 --action=allow \ + --description=new-example-rule + +POSITIONAL ARGUMENTS + PRIORITY + Priority of the security policy rule to update. + +REQUIRED FLAGS + --security-policy=SECURITY_POLICY + short name of the security policy into which the rule should be + updated. + +OPTIONAL FLAGS + --action=ACTION + Action to take if the request matches the match condition. ACTION must + be one of: + + allow + Allows the request from HTTP(S) Load Balancing. + deny + (DEPRECATED) Only used for Hierarchical Firewalls. + deny-403 + Denies the request from HTTP(S) Load Balancing, with an HTTP + response status code of 403. + deny-404 + Denies the request from HTTP(S) Load Balancing, with an HTTP + response status code of 404. + deny-502 + Denies the request from HTTP(S) Load Balancing, with an HTTP + response status code of 502. + goto-next + Defers enforcement to the next policy in the hierarchy. + redirect + Redirects the request from HTTP(S) Load Balancing, based on + redirect options. + + --cloud-armor + Specified for Hierarchical Cloud Armor rules. + + --description=DESCRIPTION + An optional, textual description for the rule. + + --dest-ip-ranges=[DEST_IP_RANGE,...] + Destination IP ranges to match for this rule. Can only be specified if + DIRECTION is egress. + + --direction=DIRECTION + Direction of the traffic the rule is applied. The default is to apply + on incoming traffic. DIRECTION must be one of: INGRESS, EGRESS. + + --[no-]enable-logging + Use this flag to enable logging of connections that allowed or denied + by this rule. Use --enable-logging to enable and --no-enable-logging to + disable. + + --layer4-configs=[LAYER4_CONFIG,...] + A list of destination protocols and ports to which the firewall rule + will apply. + + --new-priority=NEW_PRIORITY + New priority for the rule to update. Valid in [0, 65535]. + + --organization=ORGANIZATION + Organization which the organization security policy belongs to. Must be + set if SECURITY_POLICY is short name. + + --[no-]preview + If specified, the action will not be enforced. Use --preview to enable + and --no-preview to disable. + + --target-resources=[TARGET_RESOURCES,...] + List of URLs of target resources to which the rule is applied. + + --target-service-accounts=[TARGET_SERVICE_ACCOUNTS,...] + List of target service accounts for the rule. + + Security policy rule matcher. + + At most one of these can be specified: + + --expression=EXPRESSION + The Cloud Armor rules language expression to match for this rule. + + --src-ip-ranges=[SRC_IP_RANGE,...] + The source IPs/IP ranges to match for this rule. To match all IPs + specify *. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + These variants are also available: + + $ gcloud alpha compute org-security-policies rules update + + $ gcloud beta compute org-security-policies rules update + diff --git a/gcloud/compute/org-security-policies/update b/gcloud/compute/org-security-policies/update new file mode 100644 index 000000000..d10b0876a --- /dev/null +++ b/gcloud/compute/org-security-policies/update @@ -0,0 +1,72 @@ +NAME + gcloud compute org-security-policies update - update a Compute Engine + organization security policy + +SYNOPSIS + gcloud compute org-security-policies update SECURITY_POLICY + [--description=DESCRIPTION] + [--json-custom-content-types=[CONTENT_TYPE,...]] + [--json-parsing=JSON_PARSING] [--log-level=LOG_LEVEL] + [--organization=ORGANIZATION] + [--user-ip-request-headers=[USER_IP_REQUEST_HEADER,...]] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + gcloud compute org-security-policies update is used to update organization + security policies. An organization security policy is a set of rules that + controls access to various resources. + +EXAMPLES + To update an organization security policy with ID 123456789 to change the + description to New description, run: + + $ gcloud compute org-security-policies update 123456789 \ + --description='New description' + +POSITIONAL ARGUMENTS + SECURITY_POLICY + Short name or ID of the security policy to update. + +FLAGS + --description=DESCRIPTION + An optional, textual description for the organization security policy. + + --json-custom-content-types=[CONTENT_TYPE,...] + A comma-separated list of custom Content-Type header values to apply + JSON parsing for preconfigured WAF rules. Only applicable when JSON + parsing is enabled, like --json-parsing=STANDARD. When configuring a + Content-Type header value, only the type/subtype needs to be specified, + and the parameters should be excluded. + + --json-parsing=JSON_PARSING + The JSON parsing behavior for this rule. Must be one of the following + values: [DISABLED, STANDARD, STANDARD_WITH_GRAPHQL]. JSON_PARSING must + be one of: DISABLED, STANDARD, STANDARD_WITH_GRAPHQL. + + --log-level=LOG_LEVEL + The level of detail to display for WAF logging. LOG_LEVEL must be one + of: NORMAL, VERBOSE. + + --organization=ORGANIZATION + Organization in which the organization security policy is to be + updated. Must be set if SECURITY_POLICY is the short name. + + --user-ip-request-headers=[USER_IP_REQUEST_HEADER,...] + A comma-separated list of request header names to use for resolving the + caller's user IP address. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + These variants are also available: + + $ gcloud alpha compute org-security-policies update + + $ gcloud beta compute org-security-policies update + diff --git a/gcloud/compute/preview-features/describe b/gcloud/compute/preview-features/describe new file mode 100644 index 000000000..4d07f1bc6 --- /dev/null +++ b/gcloud/compute/preview-features/describe @@ -0,0 +1,55 @@ +NAME + gcloud compute preview-features describe - describe a preview feature + +SYNOPSIS + gcloud compute preview-features describe PREVIEW_FEATURE + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Describe a preview feature. + +EXAMPLES + To retrieve a single preview feature and print its properties, run the + following command: + + $ gcloud compute preview-features describe my-preview-feature + +POSITIONAL ARGUMENTS + Preview feature resource - Name of the preview feature you want to + inspect. 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 preview_feature 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. + + PREVIEW_FEATURE + ID of the preview feature or fully qualified identifier for the + preview feature. + + To set the preview_feature attribute: + ▸ provide the argument preview_feature 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 compute/v1 API. The full documentation for this API + can be found at: https://cloud.google.com/compute/ + +NOTES + These variants are also available: + + $ gcloud alpha compute preview-features describe + + $ gcloud beta compute preview-features describe + diff --git a/gcloud/compute/preview-features/help b/gcloud/compute/preview-features/help new file mode 100644 index 000000000..5a8e48110 --- /dev/null +++ b/gcloud/compute/preview-features/help @@ -0,0 +1,34 @@ +NAME + gcloud compute preview-features - read and manipulate Compute Engine + Preview Features + +SYNOPSIS + gcloud compute preview-features COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Read and manipulate Compute Engine Preview Features. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + describe + Describe a preview feature. + + list + View preview features. + + update + Update a preview feature's activation status. + +NOTES + These variants are also available: + + $ gcloud alpha compute preview-features + + $ gcloud beta compute preview-features + diff --git a/gcloud/compute/preview-features/list b/gcloud/compute/preview-features/list new file mode 100644 index 000000000..8c99ded4a --- /dev/null +++ b/gcloud/compute/preview-features/list @@ -0,0 +1,67 @@ +NAME + gcloud compute preview-features list - view preview features + +SYNOPSIS + gcloud compute preview-features list [--filter=EXPRESSION] [--limit=LIMIT] + [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + View preview features. + +EXAMPLES + To display all preview features, run the following command: + + $ gcloud compute preview-features list + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + + --uri + Print a list of resource URIs instead of the default output, and change + the command output to a list of URIs. If this flag is used with + --format, the formatting is applied on this URI list. To display URIs + alongside other keys instead, use the uri() transform. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the compute/v1 API. The full documentation for this API + can be found at: https://cloud.google.com/compute/ + +NOTES + These variants are also available: + + $ gcloud alpha compute preview-features list + + $ gcloud beta compute preview-features list + diff --git a/gcloud/compute/preview-features/update b/gcloud/compute/preview-features/update new file mode 100644 index 000000000..57dcb8a6d --- /dev/null +++ b/gcloud/compute/preview-features/update @@ -0,0 +1,74 @@ +NAME + gcloud compute preview-features update - update a preview feature's + activation status + +SYNOPSIS + gcloud compute preview-features update PREVIEW_FEATURE + --activation-status=ACTIVATION_STATUS + (--custom-rollout-plan=CUSTOM_ROLLOUT_PLAN + | --rollout-plan=ROLLOUT_PLAN) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Update a preview feature's activation status. + +EXAMPLES + To enable/unspecify a preview feature's activation status, run the + following command: + + $ gcloud compute preview-features update + +POSITIONAL ARGUMENTS + Preview feature resource - Name of the preview feature you want to update. + This represents a Cloud resource. (NOTE) Some attributes are not given + arguments in this group but can be set in other ways. + + To set the project attribute: + ◆ provide the argument preview_feature 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. + + PREVIEW_FEATURE + ID of the preview feature or fully qualified identifier for the + preview feature. + + To set the preview_feature attribute: + ▸ provide the argument preview_feature on the command line. + +REQUIRED FLAGS + --activation-status=ACTIVATION_STATUS + The activation status of the preview feature. ACTIVATION_STATUS must be + one of: enabled, unspecified. + + The rollout plan of the preview feature. + + Exactly one of these must be specified: + + --custom-rollout-plan=CUSTOM_ROLLOUT_PLAN + Use a custom rollout plan by name. + + --rollout-plan=ROLLOUT_PLAN + Use a predefined rollout plan. ROLLOUT_PLAN must be one of: + fast-rollout, two-day-rollout. + +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 compute/v1 API. The full documentation for this API + can be found at: https://cloud.google.com/compute/ + +NOTES + These variants are also available: + + $ gcloud alpha compute preview-features update + + $ gcloud beta compute preview-features update + diff --git a/gcloud/compute/reservations/sub-blocks/help b/gcloud/compute/reservations/sub-blocks/help index 88311cfea..a15c33d85 100644 --- a/gcloud/compute/reservations/sub-blocks/help +++ b/gcloud/compute/reservations/sub-blocks/help @@ -25,6 +25,9 @@ COMMANDS perform-maintenance Perform maintenance on a reservation sub-block. + report-subblock-as-faulty + Report a sub-block within a reservation as faulty. + NOTES These variants are also available: diff --git a/gcloud/compute/reservations/sub-blocks/report-subblock-as-faulty b/gcloud/compute/reservations/sub-blocks/report-subblock-as-faulty new file mode 100644 index 000000000..0b079e3c6 --- /dev/null +++ b/gcloud/compute/reservations/sub-blocks/report-subblock-as-faulty @@ -0,0 +1,98 @@ +NAME + gcloud compute reservations sub-blocks report-subblock-as-faulty - report a + sub-block within a reservation as faulty + +SYNOPSIS + gcloud compute reservations sub-blocks report-subblock-as-faulty + RESERVATION --block-name=BLOCK_NAME + --disruption-schedule=DISRUPTION_SCHEDULE + --failure-component=FAILURE_COMPONENT + --fault-reasons=[behavior=BEHAVIOR],[description=DESCRIPTION] + --sub-block-name=SUB_BLOCK_NAME [--zone=ZONE] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Report a sub-block within a reservation as faulty. + +EXAMPLES + To report reservation exr-1 in ZONE with block name block-1 and sub block + name sub-block-1 as faulty, run: + + $ gcloud compute reservations sub-blocks report-subblock-as-faulty \ + exr-1 --zone=ZONE --block-name=block-1 \ + --sub-block-name=sub-block-1 --disruption-schedule=IMMEDIATE \ + --fault-reasons=behavior=PERFORMANCE,description="performance \ + issues" --failure-component=NVLINK_SWITCH + +POSITIONAL ARGUMENTS + RESERVATION + The name of the reservation containing the sub-block to report as + faulty + +REQUIRED FLAGS + --block-name=BLOCK_NAME + The name of the reservation block. + + --disruption-schedule=DISRUPTION_SCHEDULE + The disruption schedule for the sub-block. DISRUPTION_SCHEDULE must be + (only one value is supported): + + IMMEDIATE + All VMs are immediately disrupted. + + --failure-component=FAILURE_COMPONENT + The component that experienced the fault. FAILURE_COMPONENT must be one + of: + + MULTIPLE_FAULTY_HOSTS + Multiple hosts experienced the fault. + NVLINK_SWITCH + The NVLink switch experienced the fault. + + --fault-reasons=[behavior=BEHAVIOR],[description=DESCRIPTION] + The reasons for reporting the sub-block as faulty. You can repeat this + flag. Each flag must specify a "behavior" attribute and can optionally + include a "description" attribute. The possible values for "behavior" + are: PERFORMANCE, SWITCH_FAILURE, GPU_ERROR. + + --sub-block-name=SUB_BLOCK_NAME + The name of the reservation sub block. + +OPTIONAL FLAGS + --zone=ZONE + Zone of the reservation to report-subblock-as-faulty. If not specified + and the compute/zone property isn't set, you might be prompted to + select a zone (interactive mode only). + + To avoid prompting when this flag is omitted, you can set the + compute/zone property: + + $ gcloud config set compute/zone ZONE + + A list of zones can be fetched by running: + + $ gcloud compute zones list + + To unset the property, run: + + $ gcloud config unset compute/zone + + Alternatively, the zone can be stored in the environment variable + CLOUDSDK_COMPUTE_ZONE. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + These variants are also available: + + $ gcloud alpha compute reservations sub-blocks \ + report-subblock-as-faulty + + $ gcloud beta compute reservations sub-blocks \ + report-subblock-as-faulty + diff --git a/gcloud/compute/tpus/create b/gcloud/compute/tpus/create deleted file mode 100644 index ae6920392..000000000 --- a/gcloud/compute/tpus/create +++ /dev/null @@ -1,123 +0,0 @@ -NAME - gcloud compute tpus create - create a new Cloud TPU - -SYNOPSIS - gcloud compute tpus create (TPU : --zone=ZONE) --version=VERSION - [--accelerator-type=ACCELERATOR_TYPE; default="v2-8"] [--async] - [--description=DESCRIPTION] [--network=NETWORK; default="default"] - [--preemptible] [--range=RANGE] [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (DEPRECATED) This command is being deprecated. Please use gcloud compute - tpus tpu-vm create instead. - - Create a new Cloud TPU. - -EXAMPLES - The following command creates a TPU with ID my-tpu in the default user - project, network and compute/region (with other defaults supplied by API): - - $ gcloud compute tpus create my-tpu - - The following command creates a TPU with ID my-tpu with explicit values for - all required and optional parameters: - - $ gcloud compute tpus create my-tpu --zone=us-central1-a \ - --range='10.240.0.0/29' --accelerator-type='v2-8' \ - --network=my-tf-network --description='My TF Node' \ - --version='1.1' - -POSITIONAL ARGUMENTS - Tpu resource - The Cloud TPU you want to create. The arguments in this - group can be used to specify the attributes of this resource. (NOTE) Some - attributes are not given arguments in this group but can be set in other - ways. - - To set the project attribute: - ◆ provide the argument tpu on the command line with a fully specified - name; - ◆ provide the argument --project on the command line; - ◆ set the property core/project. - - This must be specified. - - TPU - ID of the tpu or fully qualified identifier for the tpu. - - To set the tpu attribute: - ▸ provide the argument tpu on the command line. - - This positional argument must be specified if any of the other - arguments in this group are specified. - - --zone=ZONE - The compute/zone of the Cloud TPU. - - If not specified, will use default compute/zone. - - To set the zone attribute: - ▸ provide the argument tpu on the command line with a fully - specified name; - ▸ provide the argument --zone on the command line; - ▸ set the property compute/zone. - -REQUIRED FLAGS - --version=VERSION - TensorFlow version for the TPU, such as 1.14. For a list of available - TensorFlow versions please see https://www.tensorflow.org/versions/. - -OPTIONAL FLAGS - --accelerator-type=ACCELERATOR_TYPE; default="v2-8" - TPU accelerator type for the TPU. If not specified, this defaults to - v2-8. - - For a list of available accelerator types run: - - gcloud compute tpus accelerator-types list - - --async - Return immediately, without waiting for the operation in progress to - complete. - - --description=DESCRIPTION - Specifies a text description of the TPU. - - --network=NETWORK; default="default" - Specifies the network that this TPU will be a part of. - - --preemptible - If provided, the TPU will be preemptible and time-limited. It may be - preempted to free up resources for standard TPUs, and will only be able - to run for a limited amount of time. - - Preemptible TPUs cannot be restarted. - - --range=RANGE - CIDR Range for the TPU. - - The IP range that the TPU will select an IP address from. Must be in - CIDR notation and a /29 range, for example 192.168.0.0/29. Errors will - occur if the CIDR range has already been used for a currently existing - TPU, the CIDR range conflicts with any networks in the user's provided - network, or the provided network is peered with another network that is - using that CIDR range. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --configuration, --flags-file, --flatten, --format, - --help, --impersonate-service-account, --log-http, --project, --quiet, - --trace-token, --user-output-enabled, --verbosity. - - Run $ gcloud help for details. - -API REFERENCE - This command uses the tpu/v1 API. The full documentation for this API can - be found at: https://cloud.google.com/tpu/ - -NOTES - These variants are also available: - - $ gcloud alpha compute tpus create - - $ gcloud beta compute tpus create - diff --git a/gcloud/compute/tpus/delete b/gcloud/compute/tpus/delete deleted file mode 100644 index aee3bbfcc..000000000 --- a/gcloud/compute/tpus/delete +++ /dev/null @@ -1,76 +0,0 @@ -NAME - gcloud compute tpus delete - deletes a Cloud TPU - -SYNOPSIS - gcloud compute tpus delete (TPU : --zone=ZONE) [--async] - [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (DEPRECATED) This command is being deprecated. Please use gcloud compute - tpus tpu-vm delete instead. - - Deletes a Cloud TPU. - -EXAMPLES - The following command deletes a TPU with ID my-tpu in zone us-central1-b: - - $ gcloud compute tpus delete my-tpu --zone=us-central1-b - -POSITIONAL ARGUMENTS - Tpu resource - The Cloud TPU you want to delete. The arguments in this - group can be used to specify the attributes of this resource. (NOTE) Some - attributes are not given arguments in this group but can be set in other - ways. - - To set the project attribute: - ◆ provide the argument tpu on the command line with a fully specified - name; - ◆ provide the argument --project on the command line; - ◆ set the property core/project. - - This must be specified. - - TPU - ID of the tpu or fully qualified identifier for the tpu. - - To set the tpu attribute: - ▸ provide the argument tpu on the command line. - - This positional argument must be specified if any of the other - arguments in this group are specified. - - --zone=ZONE - The compute/zone of the Cloud TPU. - - If not specified, will use default compute/zone. - - To set the zone attribute: - ▸ provide the argument tpu on the command line with a fully - specified name; - ▸ provide the argument --zone on the command line; - ▸ set the property compute/zone. - -FLAGS - --async - Return immediately, without waiting for the operation in progress to - complete. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --configuration, --flags-file, --flatten, --format, - --help, --impersonate-service-account, --log-http, --project, --quiet, - --trace-token, --user-output-enabled, --verbosity. - - Run $ gcloud help for details. - -API REFERENCE - This command uses the tpu/v1 API. The full documentation for this API can - be found at: https://cloud.google.com/tpu/ - -NOTES - These variants are also available: - - $ gcloud alpha compute tpus delete - - $ gcloud beta compute tpus delete - diff --git a/gcloud/compute/tpus/describe b/gcloud/compute/tpus/describe deleted file mode 100644 index d3f905a2f..000000000 --- a/gcloud/compute/tpus/describe +++ /dev/null @@ -1,70 +0,0 @@ -NAME - gcloud compute tpus describe - describe a Cloud TPU - -SYNOPSIS - gcloud compute tpus describe (TPU : --zone=ZONE) [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (DEPRECATED) This command is being deprecated. Please use gcloud compute - tpus tpu-vm describe instead. - - Describe a Cloud TPU. - -EXAMPLES - The following command describes a TPU with ID my-tpu in zone us-central1-b: - - $ gcloud compute tpus describe my-tpu --zone=us-central1-b - -POSITIONAL ARGUMENTS - Tpu resource - The Cloud TPU you want to describe. The arguments in this - group can be used to specify the attributes of this resource. (NOTE) Some - attributes are not given arguments in this group but can be set in other - ways. - - To set the project attribute: - ◆ provide the argument tpu on the command line with a fully specified - name; - ◆ provide the argument --project on the command line; - ◆ set the property core/project. - - This must be specified. - - TPU - ID of the tpu or fully qualified identifier for the tpu. - - To set the tpu attribute: - ▸ provide the argument tpu on the command line. - - This positional argument must be specified if any of the other - arguments in this group are specified. - - --zone=ZONE - The compute/zone of the Cloud TPU. - - If not specified, will use default compute/zone. - - To set the zone attribute: - ▸ provide the argument tpu on the command line with a fully - specified name; - ▸ provide the argument --zone on the command line; - ▸ set the property compute/zone. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --configuration, --flags-file, --flatten, --format, - --help, --impersonate-service-account, --log-http, --project, --quiet, - --trace-token, --user-output-enabled, --verbosity. - - Run $ gcloud help for details. - -API REFERENCE - This command uses the tpu/v1 API. The full documentation for this API can - be found at: https://cloud.google.com/tpu/ - -NOTES - These variants are also available: - - $ gcloud alpha compute tpus describe - - $ gcloud beta compute tpus describe - diff --git a/gcloud/compute/tpus/execution-groups/create b/gcloud/compute/tpus/execution-groups/create deleted file mode 100644 index 08ac08563..000000000 --- a/gcloud/compute/tpus/execution-groups/create +++ /dev/null @@ -1,162 +0,0 @@ -NAME - gcloud compute tpus execution-groups create - create Google Compute TPUs - along with VMs - -SYNOPSIS - gcloud compute tpus execution-groups create - [--accelerator-type=ACCELERATOR_TYPE; default="v2-8"] - [--disk-size=DISK_SIZE; default="250GB"] [--dry-run] [--forward-ports] - [--gce-image=GCE_IMAGE] - [--machine-type=MACHINE_TYPE; default="n1-standard-1"] [--name=NAME] - [--network=NETWORK; default="default"] [--preemptible] - [--preemptible-vm] [--tf-version=TF_VERSION] [--tpu-only] - [--use-dl-images] [--use-with-notebook] [--vm-only] [--zone=ZONE] - [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (DEPRECATED) Create Google Compute TPUs along with VMs. - - This command is deprecated and will be removed in a future release. We - recommend that you use the TPU-VM or Queued Resource API. See - https://cloud.google.com/tpu/docs/managing-tpus-tpu-vm for more - information. - -EXAMPLES - To create both TPU and VM, run: - - $ gcloud compute tpus execution-groups create \ - --name=test-execution-group --zone=test-zone \ - --project=test-project --accelerator-type=v2-8 \ - --tf-version=2.4.1 - - To create both TPU and VM with additional flags, run: - - $ gcloud compute tpus execution-groups create \ - --name=test-execution-group --zone=test-zone \ - --project=test-project --accelerator-type=v2-8 \ - --tf-version=2.4.1 --network=default --preemptible-vm \ - --disk-size=100 --machine-type=n1-standard-2 --use-dl-images - - To create a VM only before creating the TPU, run: - - $ gcloud compute tpus execution-groups create \ - --name=test-execution-group-tpu-only --zone=test-zone \ - --project=test-project --accelerator-type=v2-8 \ - --tf-version=2.4.1 --tpu-only - - To create the TPU only after the VM has been created, run: - - $ gcloud compute tpus execution-groups create \ - --name=test-execution-group-tpu-only --zone=test-zone \ - --project=test-project --accelerator-type=v2-8 \ - --tf-version=2.4.1 --vm-only - -FLAGS - --accelerator-type=ACCELERATOR_TYPE; default="v2-8" - TPU accelerator type for the TPU. If not specified, this defaults to - v2-8. - - --disk-size=DISK_SIZE; default="250GB" - Configures the root volume size of your Compute Engine VM (in GB). The - minimum size is 20GB and the maximum is 2000GB. Specified value must be - an integer multiple of Gigabytes. - - --dry-run - Do not make changes; print only what would have happened. - - --forward-ports - Automatically forward useful ports from the Compute Engine VM to your - local machine. The ports forwarded are: 6006 (tensorboard), 8888 - (jupyter notebooks), 8470 (TPU port), 8466 (TPU profiler port). - - Enabled by default, use --no-forward-ports to disable. - - --gce-image=GCE_IMAGE - Override the automatically chosen Compute Engine Image. Use this flag - when you're using your own custom images instead of the provided ones - with TensorFlow pre-installed. - - --machine-type=MACHINE_TYPE; default="n1-standard-1" - Specifies the machine type used for the Compute Engine VM. To get a - list of available machine types, run 'gcloud compute machine-types - list'. If unspecified, the default type is n1-standard-1. - - --name=NAME - Override the name to use for VMs and TPUs (defaults to your username). - - --network=NETWORK; default="default" - Specifies the network the Cloud TPU and associated VM should be created - in. If unspecified, the network "default" is picked. - - --preemptible - Create a preemptible Cloud TPU, instead of a normal (non-preemptible) - Cloud TPU. A preemptible Cloud TPU costs less per hour, but the Cloud - TPU service can stop/terminate the node at any time. - - --preemptible-vm - Create a preemptible Compute Engine VM, instead of a normal - (non-preemptible) VM. A preemptible VM costs less per hour, but the - Compute Engine service can terminate the instance at any time. - - --tf-version=TF_VERSION - Set the version of TensorFlow to use when creating the Compute Engine - VM and the Cloud TPU. (It defaults to auto-selecting the latest stable - release.) - - --tpu-only - Do not allocate a VM, only allocate a TPU. To be used after the command - has been run with a --vm-only flag and the user is ready to run on a - TPU. Ensure that the name matches the name passed in when creating with - the --vm-only flag. - - --use-dl-images - Use Deep Learning VM Images (see docs - - https://cloud.google.com/deep-learning-vm/) instead of TPU-specific - machine images. Defaults to TPU-specific images. This value is set to - true automatically if the --use-with-notebook flag is set to true. - - --use-with-notebook - Allow Compute Engine VM to be recognized by Cloud AI Notebooks. This - automatically sets the content of the flag --use-dl-images flag to be - true. - - --vm-only - Do not allocate a TPU, only allocate a VM (useful if you're not ready - to run on a TPU yet). - - --zone=ZONE - Zone of the tpu to create. If not specified and the compute/zone - property isn't set, you might be prompted to select a zone (interactive - mode only). - - To avoid prompting when this flag is omitted, you can set the - compute/zone property: - - $ gcloud config set compute/zone ZONE - - A list of zones can be fetched by running: - - $ gcloud compute zones list - - To unset the property, run: - - $ gcloud config unset compute/zone - - Alternatively, the zone can be stored in the environment variable - CLOUDSDK_COMPUTE_ZONE. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --configuration, --flags-file, --flatten, --format, - --help, --impersonate-service-account, --log-http, --project, --quiet, - --trace-token, --user-output-enabled, --verbosity. - - Run $ gcloud help for details. - -NOTES - These variants are also available: - - $ gcloud alpha compute tpus execution-groups create - - $ gcloud beta compute tpus execution-groups create - diff --git a/gcloud/compute/tpus/execution-groups/delete b/gcloud/compute/tpus/execution-groups/delete deleted file mode 100644 index 7d799bb9c..000000000 --- a/gcloud/compute/tpus/execution-groups/delete +++ /dev/null @@ -1,71 +0,0 @@ -NAME - gcloud compute tpus execution-groups delete - delete TPU Node + VM created - by execution group - -SYNOPSIS - gcloud compute tpus execution-groups delete EXECUTION_GROUP_NAME - [--tpu-only] [--zone=ZONE] [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (DEPRECATED) Delete TPU Node + VM created by execution group. - - This command is deprecated and will be removed in a future release. We - recommend that you use the TPU-VM or Queued Resource API. See - https://cloud.google.com/tpu/docs/managing-tpus-tpu-vm for more - information. - -EXAMPLES - To delete both, the TPU and the VM, run: - - $ gcloud compute tpus execution-groups delete test-execution-group \ - --zone=test-zone --project=test-project - - To delete the TPU only, run: - - $ gcloud compute tpus execution-groups delete test-execution-group \ - --zone=test-zone --project=test-project --tpu-only - -POSITIONAL ARGUMENTS - EXECUTION_GROUP_NAME - The execution group name to delete. - -FLAGS - --tpu-only - Do not delete VM, only delete the TPU. - - --zone=ZONE - Zone of the tpu to delete. If not specified and the compute/zone - property isn't set, you might be prompted to select a zone (interactive - mode only). - - To avoid prompting when this flag is omitted, you can set the - compute/zone property: - - $ gcloud config set compute/zone ZONE - - A list of zones can be fetched by running: - - $ gcloud compute zones list - - To unset the property, run: - - $ gcloud config unset compute/zone - - Alternatively, the zone can be stored in the environment variable - CLOUDSDK_COMPUTE_ZONE. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --configuration, --flags-file, --flatten, --format, - --help, --impersonate-service-account, --log-http, --project, --quiet, - --trace-token, --user-output-enabled, --verbosity. - - Run $ gcloud help for details. - -NOTES - These variants are also available: - - $ gcloud alpha compute tpus execution-groups delete - - $ gcloud beta compute tpus execution-groups delete - diff --git a/gcloud/compute/tpus/execution-groups/describe b/gcloud/compute/tpus/execution-groups/describe deleted file mode 100644 index 2546101be..000000000 --- a/gcloud/compute/tpus/execution-groups/describe +++ /dev/null @@ -1,63 +0,0 @@ -NAME - gcloud compute tpus execution-groups describe - describe Google Compute TPU - + VM combination - -SYNOPSIS - gcloud compute tpus execution-groups describe EXECUTION_GROUP_NAME - [--zone=ZONE] [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (DEPRECATED) Describe Google Compute TPU + VM combination. - - This command is deprecated and will be removed in a future release. We - recommend that you use the TPU-VM or Queued Resource API. See - https://cloud.google.com/tpu/docs/managing-tpus-tpu-vm for more - information. - -EXAMPLES - To describe the TPU and VM combination, run: - - $ gcloud compute tpus execution-groups describe \ - test-execution-group --zone=test-zone --project=test-project - -POSITIONAL ARGUMENTS - EXECUTION_GROUP_NAME - The execution group name to delete. - -FLAGS - --zone=ZONE - Zone of the tpu to describe. If not specified and the compute/zone - property isn't set, you might be prompted to select a zone (interactive - mode only). - - To avoid prompting when this flag is omitted, you can set the - compute/zone property: - - $ gcloud config set compute/zone ZONE - - A list of zones can be fetched by running: - - $ gcloud compute zones list - - To unset the property, run: - - $ gcloud config unset compute/zone - - Alternatively, the zone can be stored in the environment variable - CLOUDSDK_COMPUTE_ZONE. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --configuration, --flags-file, --flatten, --format, - --help, --impersonate-service-account, --log-http, --project, --quiet, - --trace-token, --user-output-enabled, --verbosity. - - Run $ gcloud help for details. - -NOTES - These variants are also available: - - $ gcloud alpha compute tpus execution-groups describe - - $ gcloud beta compute tpus execution-groups describe - diff --git a/gcloud/compute/tpus/execution-groups/help b/gcloud/compute/tpus/execution-groups/help deleted file mode 100644 index 129120e19..000000000 --- a/gcloud/compute/tpus/execution-groups/help +++ /dev/null @@ -1,43 +0,0 @@ -NAME - gcloud compute tpus execution-groups - command group that helps create and - manage Cloud TPUs and Compute VMs - -SYNOPSIS - gcloud compute tpus execution-groups COMMAND [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (DEPRECATED) Command group that helps create and manage Cloud TPUs and - Compute VMs. - - This command group is deprecated and will be removed in a future release. - We recommend that you use the TPU-VM or Queued Resource API. See - https://cloud.google.com/tpu/docs/managing-tpus-tpu-vm for more - information. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --help. - - Run $ gcloud help for details. - -COMMANDS - COMMAND is one of the following: - - create - (DEPRECATED) Create Google Compute TPUs along with VMs. - - delete - (DEPRECATED) Delete TPU Node + VM created by execution group. - - describe - (DEPRECATED) Describe Google Compute TPU + VM combination. - - list - (DEPRECATED) List TPU Node+VM groups created by execution group. - -NOTES - These variants are also available: - - $ gcloud alpha compute tpus execution-groups - - $ gcloud beta compute tpus execution-groups - diff --git a/gcloud/compute/tpus/help b/gcloud/compute/tpus/help index b9f8db1ad..2b26d9382 100644 --- a/gcloud/compute/tpus/help +++ b/gcloud/compute/tpus/help @@ -24,10 +24,6 @@ GROUPS accelerator-types List or Describe Available Cloud TPU accelerator types. - execution-groups - (DEPRECATED) Command group that helps create and manage Cloud TPUs and - Compute VMs. - locations List or Describe Available Cloud TPU Locations. @@ -43,30 +39,6 @@ GROUPS versions Explore Available Tensorflow versions for Cloud TPUs. -COMMANDS - COMMAND is one of the following: - - create - (DEPRECATED) Create a new Cloud TPU. - - delete - (DEPRECATED) Deletes a Cloud TPU. - - describe - (DEPRECATED) Describe a Cloud TPU. - - list - (DEPRECATED) List Cloud TPUs. - - reimage - (DEPRECATED) Reimages the OS on a Cloud TPU. - - start - (DEPRECATED) Start a Cloud TPU. - - stop - (DEPRECATED) Stop a Cloud TPU. - NOTES These variants are also available: diff --git a/gcloud/compute/tpus/reimage b/gcloud/compute/tpus/reimage deleted file mode 100644 index e5d3eb367..000000000 --- a/gcloud/compute/tpus/reimage +++ /dev/null @@ -1,83 +0,0 @@ -NAME - gcloud compute tpus reimage - reimages the OS on a Cloud TPU - -SYNOPSIS - gcloud compute tpus reimage (TPU : --zone=ZONE) --version=VERSION [--async] - [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (DEPRECATED) This command is being deprecated. Please use gcloud compute - tpus tpu-vm reimage instead. - - Reimages the OS on a Cloud TPU. - -EXAMPLES - The following command reimages a TPU with ID my-tpu in zone us-central1-b - with TensorFlow version 1.15: - - $ gcloud compute tpus reimage my-tpu --zone=us-central1-b \ - --version=1.15 - -POSITIONAL ARGUMENTS - Tpu resource - The Cloud TPU you want to reimage. The arguments in this - group can be used to specify the attributes of this resource. (NOTE) Some - attributes are not given arguments in this group but can be set in other - ways. - - To set the project attribute: - ◆ provide the argument tpu on the command line with a fully specified - name; - ◆ provide the argument --project on the command line; - ◆ set the property core/project. - - This must be specified. - - TPU - ID of the tpu or fully qualified identifier for the tpu. - - To set the tpu attribute: - ▸ provide the argument tpu on the command line. - - This positional argument must be specified if any of the other - arguments in this group are specified. - - --zone=ZONE - The compute/zone of the Cloud TPU. - - If not specified, will use default compute/zone. - - To set the zone attribute: - ▸ provide the argument tpu on the command line with a fully - specified name; - ▸ provide the argument --zone on the command line; - ▸ set the property compute/zone. - -REQUIRED FLAGS - --version=VERSION - TensorFlow version for the TPU, such as 1.6. For a list of available - TensorFlow versions please see https://www.tensorflow.org/versions/. - -OPTIONAL FLAGS - --async - Return immediately, without waiting for the operation in progress to - complete. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --configuration, --flags-file, --flatten, --format, - --help, --impersonate-service-account, --log-http, --project, --quiet, - --trace-token, --user-output-enabled, --verbosity. - - Run $ gcloud help for details. - -API REFERENCE - This command uses the tpu/v1 API. The full documentation for this API can - be found at: https://cloud.google.com/tpu/ - -NOTES - These variants are also available: - - $ gcloud alpha compute tpus reimage - - $ gcloud beta compute tpus reimage - diff --git a/gcloud/compute/tpus/start b/gcloud/compute/tpus/start deleted file mode 100644 index 0787a36f9..000000000 --- a/gcloud/compute/tpus/start +++ /dev/null @@ -1,75 +0,0 @@ -NAME - gcloud compute tpus start - start a Cloud TPU - -SYNOPSIS - gcloud compute tpus start (TPU : --zone=ZONE) [--async] - [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (DEPRECATED) This command is being deprecated. Please use gcloud compute - tpus tpu-vm start instead. - - Start a Cloud TPU. - -EXAMPLES - The following command starts a TPU with ID my-tpu in zone us-central1-b: - - $ gcloud compute tpus start my-tpu --zone=us-central1-b - -POSITIONAL ARGUMENTS - Tpu resource - The Cloud TPU to start. The arguments in this group can be - used to specify the attributes of this resource. (NOTE) Some attributes - are not given arguments in this group but can be set in other ways. - - To set the project attribute: - ◆ provide the argument tpu on the command line with a fully specified - name; - ◆ provide the argument --project on the command line; - ◆ set the property core/project. - - This must be specified. - - TPU - ID of the tpu or fully qualified identifier for the tpu. - - To set the tpu attribute: - ▸ provide the argument tpu on the command line. - - This positional argument must be specified if any of the other - arguments in this group are specified. - - --zone=ZONE - The compute/zone of the Cloud TPU. - - If not specified, will use default compute/zone. - - To set the zone attribute: - ▸ provide the argument tpu on the command line with a fully - specified name; - ▸ provide the argument --zone on the command line; - ▸ set the property compute/zone. - -FLAGS - --async - Return immediately, without waiting for the operation in progress to - complete. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --configuration, --flags-file, --flatten, --format, - --help, --impersonate-service-account, --log-http, --project, --quiet, - --trace-token, --user-output-enabled, --verbosity. - - Run $ gcloud help for details. - -API REFERENCE - This command uses the tpu/v1 API. The full documentation for this API can - be found at: https://cloud.google.com/tpu/ - -NOTES - These variants are also available: - - $ gcloud alpha compute tpus start - - $ gcloud beta compute tpus start - diff --git a/gcloud/compute/tpus/stop b/gcloud/compute/tpus/stop deleted file mode 100644 index 8c664ec6c..000000000 --- a/gcloud/compute/tpus/stop +++ /dev/null @@ -1,75 +0,0 @@ -NAME - gcloud compute tpus stop - stop a Cloud TPU - -SYNOPSIS - gcloud compute tpus stop (TPU : --zone=ZONE) [--async] - [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (DEPRECATED) This command is being deprecated. Please use gcloud compute - tpus tpu-vm stop instead. - - Stop a Cloud TPU. - -EXAMPLES - The following command stops a TPU with ID my-tpu in zone us-central1-b: - - $ gcloud compute tpus stop my-tpu --zone=us-central1-b - -POSITIONAL ARGUMENTS - Tpu resource - The Cloud TPU to stop. The arguments in this group can be - used to specify the attributes of this resource. (NOTE) Some attributes - are not given arguments in this group but can be set in other ways. - - To set the project attribute: - ◆ provide the argument tpu on the command line with a fully specified - name; - ◆ provide the argument --project on the command line; - ◆ set the property core/project. - - This must be specified. - - TPU - ID of the tpu or fully qualified identifier for the tpu. - - To set the tpu attribute: - ▸ provide the argument tpu on the command line. - - This positional argument must be specified if any of the other - arguments in this group are specified. - - --zone=ZONE - The compute/zone of the Cloud TPU. - - If not specified, will use default compute/zone. - - To set the zone attribute: - ▸ provide the argument tpu on the command line with a fully - specified name; - ▸ provide the argument --zone on the command line; - ▸ set the property compute/zone. - -FLAGS - --async - Return immediately, without waiting for the operation in progress to - complete. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --configuration, --flags-file, --flatten, --format, - --help, --impersonate-service-account, --log-http, --project, --quiet, - --trace-token, --user-output-enabled, --verbosity. - - Run $ gcloud help for details. - -API REFERENCE - This command uses the tpu/v1 API. The full documentation for this API can - be found at: https://cloud.google.com/tpu/ - -NOTES - These variants are also available: - - $ gcloud alpha compute tpus stop - - $ gcloud beta compute tpus stop - diff --git a/gcloud/container/ai/profiles/benchmarks/list b/gcloud/container/ai/profiles/benchmarks/list index 7b01bef75..256fd0745 100644 --- a/gcloud/container/ai/profiles/benchmarks/list +++ b/gcloud/container/ai/profiles/benchmarks/list @@ -6,8 +6,9 @@ SYNOPSIS gcloud container ai profiles benchmarks list --model=MODEL --model-server=MODEL_SERVER [--format=FORMAT] [--instance-type=INSTANCE_TYPE] - [--model-server-version=MODEL_SERVER_VERSION] [--filter=EXPRESSION] - [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [--model-server-version=MODEL_SERVER_VERSION] + [--pricing-model=PRICING_MODEL] [--filter=EXPRESSION] [--limit=LIMIT] + [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -38,6 +39,10 @@ FLAGS The model server version. Default is latest. Other options include the model server version of a profile, all which returns all versions. + --pricing-model=PRICING_MODEL + The pricing model to use to calculate token cost. Currently, this + supports on-demand, spot, 3-years-cud, 1-year-cud + LIST COMMAND FLAGS --filter=EXPRESSION Apply a Boolean filter EXPRESSION to each resource item to be listed. diff --git a/gcloud/container/clusters/create b/gcloud/container/clusters/create index d3f2b4c41..92bbb3e52 100644 --- a/gcloud/container/clusters/create +++ b/gcloud/container/clusters/create @@ -41,7 +41,8 @@ SYNOPSIS [--enable-gvnic] [--enable-identity-service] [--enable-image-streaming] [--enable-insecure-kubelet-readonly-port] [--enable-intra-node-visibility] [--enable-ip-access] - [--enable-ip-alias] [--enable-kubernetes-alpha] + [--enable-ip-alias] [--enable-k8s-certs-via-dns] + [--enable-k8s-tokens-via-dns] [--enable-kubernetes-alpha] [--enable-kubernetes-unstable-apis=API,[API,...]] [--enable-l4-ilb-subsetting] [--enable-legacy-authorization] [--enable-legacy-lustre-port] [--enable-managed-prometheus] @@ -664,6 +665,14 @@ FLAGS you omit both --enable-ip-alias and --no-enable-ip-alias, the default is a VPC-native cluster. + --enable-k8s-certs-via-dns + Enable K8s client certificates Authentication to the cluster's control + plane over DNS-based endpoint. + + --enable-k8s-tokens-via-dns + Enable K8s Service Account tokens Authentication to the cluster's + control plane over DNS-based endpoint. + --enable-kubernetes-alpha Enable Kubernetes alpha features on this cluster. Selecting this option will result in the cluster having all Kubernetes alpha API groups and diff --git a/gcloud/container/clusters/create-auto b/gcloud/container/clusters/create-auto index 7ef058f2a..85c057bdc 100644 --- a/gcloud/container/clusters/create-auto +++ b/gcloud/container/clusters/create-auto @@ -22,7 +22,9 @@ SYNOPSIS [--enable-backup-restore] [--enable-cilium-clusterwide-network-policy] [--enable-confidential-nodes] [--enable-default-compute-class] [--enable-dns-access] [--enable-fleet] [--enable-google-cloud-access] - [--enable-ip-access] [--enable-kubernetes-unstable-apis=API,[API,...]] + [--enable-ip-access] [--enable-k8s-certs-via-dns] + [--enable-k8s-tokens-via-dns] + [--enable-kubernetes-unstable-apis=API,[API,...]] [--enable-legacy-lustre-port] [--enable-lustre-csi-driver] [--enable-master-global-access] [--enable-multi-networking] [--enable-ray-cluster-logging] [--enable-ray-cluster-monitoring] @@ -314,6 +316,14 @@ FLAGS Enable access to the cluster's control plane over private IP and public IP if --enable-private-endpoint is not enabled. + --enable-k8s-certs-via-dns + Enable K8s client certificates Authentication to the cluster's control + plane over DNS-based endpoint. + + --enable-k8s-tokens-via-dns + Enable K8s Service Account tokens Authentication to the cluster's + control plane over DNS-based endpoint. + --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/update b/gcloud/container/clusters/update index 4673b6709..f9c4b3ecd 100644 --- a/gcloud/container/clusters/update +++ b/gcloud/container/clusters/update @@ -87,6 +87,7 @@ SYNOPSIS | --enable-l4-lb-firewall-reconciliation | --enable-authorized-networks-on-private-endpoint --enable-dns-access --enable-google-cloud-access --enable-ip-access + --enable-k8s-certs-via-dns --enable-k8s-tokens-via-dns --enable-master-global-access --enable-private-endpoint --enable-master-authorized-networks --master-authorized-networks=NETWORK,[NETWORK,...] @@ -1229,6 +1230,14 @@ REQUIRED FLAGS Enable access to the cluster's control plane over private IP and public IP if --enable-private-endpoint is not enabled. + --enable-k8s-certs-via-dns + Enable K8s client certificates Authentication to the cluster's + control plane over DNS-based endpoint. + + --enable-k8s-tokens-via-dns + Enable K8s Service Account tokens Authentication to the cluster's + control plane over DNS-based endpoint. + --enable-master-global-access Use with private clusters to allow access to the master's private endpoint from any Google Cloud region or on-premises environment diff --git a/gcloud/container/node-pools/create b/gcloud/container/node-pools/create index 74f086823..47d041873 100644 --- a/gcloud/container/node-pools/create +++ b/gcloud/container/node-pools/create @@ -14,6 +14,7 @@ SYNOPSIS [--additional-pod-network=[subnetwork=SUBNETWORK_NAME, pod-ipv4-range=SECONDARY_RANGE_NAME, [max-pods-per-node=NUM_PODS],...]] [--async] + [--autoscaled-rollout-policy=[wait-for-drain-duration=WAIT-FOR-DRAIN-DURATION]] [--boot-disk-kms-key=BOOT_DISK_KMS_KEY] [--boot-disk-provisioned-iops=BOOT_DISK_PROVISIONED_IOPS] [--boot-disk-provisioned-throughput=BOOT_DISK_PROVISIONED_THROUGHPUT] @@ -180,6 +181,23 @@ FLAGS Return immediately, without waiting for the operation in progress to complete. + --autoscaled-rollout-policy=[wait-for-drain-duration=WAIT-FOR-DRAIN-DURATION] + Autoscaled rollout policy options for blue-green upgrade. + + wait-for-drain-duration + (Optional) Time in seconds to wait after cordoning the blue pool + before draining the nodes. + + Examples: + + $ gcloud container node-pools create node-pool-1 \ + --cluster=example-cluster --enable-blue-green-upgrade \ + --autoscaled-rollout-policy="" + + $ gcloud container node-pools create node-pool-1 \ + --cluster=example-cluster --enable-blue-green-upgrade \ + --autoscaled-rollout-policy=wait-for-drain-duration=7200s + --boot-disk-kms-key=BOOT_DISK_KMS_KEY The Customer Managed Encryption Key used to encrypt the boot disk attached to each node in the node pool. This should be of the form diff --git a/gcloud/container/node-pools/update b/gcloud/container/node-pools/update index 09d3771b0..25c6a2a56 100644 --- a/gcloud/container/node-pools/update +++ b/gcloud/container/node-pools/update @@ -24,11 +24,8 @@ SYNOPSIS | --storage-pools=STORAGE_POOL,[...] | --system-config-from-file=PATH_TO_FILE | --tags=[TAG,...] | --windows-os-version=WINDOWS_OS_VERSION - | --workload-metadata=WORKLOAD_METADATA | --enable-blue-green-upgrade - --enable-surge-upgrade --max-surge-upgrade=MAX_SURGE_UPGRADE - --max-unavailable-upgrade=MAX_UNAVAILABLE_UPGRADE - --node-pool-soak-duration=NODE_POOL_SOAK_DURATION - --standard-rollout-policy=[batch-node-count=BATCH_NODE_COUNT, + | --workload-metadata=WORKLOAD_METADATA + | --autoscaled-rollout-policy=[wait-for-drain-duration=WAIT-FOR-DRAIN-DURATION] --enable-blue-green-upgrade --enable-surge-upgrade --max-surge-upgrade=MAX_SURGE_UPGRADE --max-unavailable-upgrade=MAX_UNAVAILABLE_UPGRADE --node-pool-soak-duration=NODE_POOL_SOAK_DURATION --standard-rollout-policy=[batch-node-count=BATCH_NODE_COUNT, batch-percent=BATCH_NODE_PERCENTAGE, batch-soak-duration=BATCH_SOAK_DURATION,...] | --boot-disk-provisioned-iops=BOOT_DISK_PROVISIONED_IOPS @@ -744,6 +741,23 @@ REQUIRED FLAGS Upgrade settings + --autoscaled-rollout-policy=[wait-for-drain-duration=WAIT-FOR-DRAIN-DURATION] + Autoscaled rollout policy options for blue-green upgrade. + + wait-for-drain-duration + (Optional) Time in seconds to wait after cordoning the blue + pool before draining the nodes. + + Examples: + + $ gcloud container node-pools update node-pool-1 \ + --cluster=example-cluster --enable-blue-green-upgrade \ + --autoscaled-rollout-policy="" + + $ gcloud container node-pools update node-pool-1 \ + --cluster=example-cluster --enable-blue-green-upgrade \ + --autoscaled-rollout-policy=wait-for-drain-duration=7200s + --enable-blue-green-upgrade Changes node pool upgrade strategy to blue-green upgrade. diff --git a/gcloud/firestore/databases/help b/gcloud/firestore/databases/help index 3a14fddf6..78de077b8 100644 --- a/gcloud/firestore/databases/help +++ b/gcloud/firestore/databases/help @@ -31,6 +31,10 @@ COMMANDS list Lists all Firestore databases under the project. + ping + Times the connection and ping time for a Firestore with MongoDB + compatibility database. + restore Restores a Cloud Firestore database from a backup. diff --git a/gcloud/firestore/databases/ping b/gcloud/firestore/databases/ping new file mode 100644 index 000000000..6c26b8824 --- /dev/null +++ b/gcloud/firestore/databases/ping @@ -0,0 +1,36 @@ +NAME + gcloud firestore databases ping - times the connection and ping time for a + Firestore with MongoDB compatibility database + +SYNOPSIS + gcloud firestore databases ping --database=DATABASE [GCLOUD_WIDE_FLAG ...] + +EXAMPLES + To time the connection and ping times for a Firestore with MongoDB + compatibility database testdb: + + $ gcloud firestore databases ping --database=testdb + +REQUIRED FLAGS + --database=DATABASE + The database to operate on. + + For example, to operate on database foo: + + $ gcloud firestore databases ping --database='foo' + +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 firestore databases ping + + $ gcloud beta firestore databases ping + diff --git a/gcloud/iam/workforce-pools/providers/scim-tenants/delete b/gcloud/iam/workforce-pools/providers/scim-tenants/delete index aead2d0e0..7bf5bcf4c 100644 --- a/gcloud/iam/workforce-pools/providers/scim-tenants/delete +++ b/gcloud/iam/workforce-pools/providers/scim-tenants/delete @@ -5,7 +5,7 @@ NAME SYNOPSIS gcloud iam workforce-pools providers scim-tenants delete (SCIM_TENANT : --location=LOCATION - --provider=PROVIDER --workforce-pool=WORKFORCE_POOL) + --provider=PROVIDER --workforce-pool=WORKFORCE_POOL) [--hard-delete] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -70,6 +70,10 @@ POSITIONAL ARGUMENTS specified name; ▸ provide the argument --workforce-pool on the command line. +FLAGS + --hard-delete + Deletes the SCIM tenant immediately. This operation cannot be undone. + 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/memorystore/instances/update b/gcloud/memorystore/instances/update index 190fb981e..22942b657 100644 --- a/gcloud/memorystore/instances/update +++ b/gcloud/memorystore/instances/update @@ -6,10 +6,10 @@ SYNOPSIS gcloud memorystore instances update INSTANCE [--async] [--[no-]async-instance-endpoints-deletion-enabled] [--[no-]deletion-protection-enabled] [--engine-version=ENGINE_VERSION] - [--location=LOCATION] [--mode=MODE] [--node-type=NODE_TYPE] - [--[no-]ondemand-maintenance] [--replica-count=REPLICA_COUNT] - [--request-id=REQUEST_ID] [--shard-count=SHARD_COUNT] - [--[no-]simulate-maintenance-event] + [--location=LOCATION] [--maintenance-version=MAINTENANCE_VERSION] + [--mode=MODE] [--node-type=NODE_TYPE] [--[no-]ondemand-maintenance] + [--replica-count=REPLICA_COUNT] [--request-id=REQUEST_ID] + [--shard-count=SHARD_COUNT] [--[no-]simulate-maintenance-event] [--aof-config-append-fsync=AOF_CONFIG_APPEND_FSYNC --clear-persistence-config --persistence-config-mode=PERSISTENCE_CONFIG_MODE @@ -111,6 +111,13 @@ FLAGS value for resource location attribute. When the resource's full URI path is not provided, location will fallback to this flag value. + Arguments for the maintenance version. + + --maintenance-version=MAINTENANCE_VERSION + This field can be used to trigger self service update to indicate the + desired maintenance version. The input to this field can be + determined by the available_maintenance_versions field. + --mode=MODE The mode config for the instance. MODE must be one of: diff --git a/gcloud/oracle-database/autonomous-databases/create b/gcloud/oracle-database/autonomous-databases/create index 54754b81d..469c4ad8b 100644 --- a/gcloud/oracle-database/autonomous-databases/create +++ b/gcloud/oracle-database/autonomous-databases/create @@ -12,7 +12,7 @@ SYNOPSIS [[--properties-db-workload=PROPERTIES_DB_WORKLOAD --properties-license-type=PROPERTIES_LICENSE_TYPE : --properties-allowlisted-ips=[PROPERTIES_ALLOWLISTED_IPS,...] - --properties-backup-retention-period-days=PROPERTIES_BACKUP_RETENTION_PERIOD_DAYS --properties-character-set=PROPERTIES_CHARACTER_SET --properties-compute-count=PROPERTIES_COMPUTE_COUNT --properties-cpu-core-count=PROPERTIES_CPU_CORE_COUNT --properties-customer-contacts=[email=EMAIL] --properties-data-storage-size-gb=PROPERTIES_DATA_STORAGE_SIZE_GB --properties-data-storage-size-tb=PROPERTIES_DATA_STORAGE_SIZE_TB --properties-db-edition=PROPERTIES_DB_EDITION --properties-db-version=PROPERTIES_DB_VERSION --properties-is-auto-scaling-enabled --properties-is-storage-auto-scaling-enabled --properties-maintenance-schedule-type=PROPERTIES_MAINTENANCE_SCHEDULE_TYPE --properties-mtls-connection-required --properties-n-character-set=PROPERTIES_N_CHARACTER_SET --properties-private-endpoint-ip=PROPERTIES_PRIVATE_ENDPOINT_IP --properties-private-endpoint-label=PROPERTIES_PRIVATE_ENDPOINT_LABEL --properties-secret-id=PROPERTIES_SECRET_ID --properties-vault-id=PROPERTIES_VAULT_ID --encryption-key-kms=ENCRYPTION_KEY_KMS --encryption-key-provider=ENCRYPTION_KEY_PROVIDER]] + --properties-backup-retention-period-days=PROPERTIES_BACKUP_RETENTION_PERIOD_DAYS --properties-character-set=PROPERTIES_CHARACTER_SET --properties-compute-count=PROPERTIES_COMPUTE_COUNT --properties-cpu-core-count=PROPERTIES_CPU_CORE_COUNT --properties-customer-contacts=[email=EMAIL] --properties-data-storage-size-gb=PROPERTIES_DATA_STORAGE_SIZE_GB --properties-data-storage-size-tb=PROPERTIES_DATA_STORAGE_SIZE_TB --properties-db-edition=PROPERTIES_DB_EDITION --properties-db-version=PROPERTIES_DB_VERSION --properties-is-auto-scaling-enabled --properties-is-storage-auto-scaling-enabled --properties-maintenance-schedule-type=PROPERTIES_MAINTENANCE_SCHEDULE_TYPE --properties-mtls-connection-required --properties-n-character-set=PROPERTIES_N_CHARACTER_SET --properties-private-endpoint-ip=PROPERTIES_PRIVATE_ENDPOINT_IP --properties-private-endpoint-label=PROPERTIES_PRIVATE_ENDPOINT_LABEL --properties-secret-id=PROPERTIES_SECRET_ID --properties-vault-id=PROPERTIES_VAULT_ID --encryption-key-provider=ENCRYPTION_KEY_PROVIDER [--encryption-key-kms=ENCRYPTION_KEY_KMS : --key-ring=KEY_RING]]] [--source-config-automatic-backups-replication-enabled --source-config-autonomous-database=SOURCE_CONFIG_AUTONOMOUS_DATABASE] [GCLOUD_WIDE_FLAG ...] @@ -128,10 +128,10 @@ FLAGS --labels=path_to_file.(yaml|json) --location=LOCATION - For resources [autonomous_database, odb-network, odb-subnet, - source-config-autonomous-database], provides fallback value for - resource location attribute. When the resource's full URI path is not - provided, location will fallback to this flag value. + For resources [autonomous_database, encryption-key-kms, odb-network, + odb-subnet, source-config-autonomous-database], provides fallback value + for resource location attribute. When the resource's full URI path is + not provided, location will fallback to this flag value. Network resource - The name of the VPC network used by the Autonomous Database in the following format: @@ -321,12 +321,6 @@ FLAGS The encryption key used to encrypt the Autonomous Database. - --encryption-key-kms=ENCRYPTION_KEY_KMS - The KMS key used to encrypt the Autonomous Database. This field is - required if the provider is GOOGLE_MANAGED. The name of the KMS key - resource in the following format: - projects/{project}/locations/{location}/keyRings/{key_ring}/cryptoKeys/{crypto_key}. - --encryption-key-provider=ENCRYPTION_KEY_PROVIDER The provider of the encryption key. ENCRYPTION_KEY_PROVIDER must be one of: @@ -337,6 +331,44 @@ FLAGS oracle-managed Oracle Managed. + CryptoKey resource - The KMS key used to encrypt the Autonomous + Database. This field is required if the provider is GOOGLE_MANAGED. + The name of the KMS key resource in the following format: + projects/{project}/locations/{location}/keyRings/{key_ring}/cryptoKeys/{crypto_key}. + 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 --encryption-key-kms on the command line + with a fully specified name; + ▫ provide the argument --project on the command line; + ▫ set the property core/project. + + To set the location attribute: + ▫ provide the argument --encryption-key-kms on the command line + with a fully specified name; + ▫ provide the argument --location on the command line. + + --encryption-key-kms=ENCRYPTION_KEY_KMS + ID of the cryptoKey or fully qualified identifier for the + cryptoKey. + + To set the crypto-key attribute: + ◇ provide the argument --encryption-key-kms on the command + line. + + This flag argument must be specified if any of the other + arguments in this group are specified. + + --key-ring=KEY_RING + The keyRing id of the cryptoKey resource. + + To set the key-ring attribute: + ◇ provide the argument --encryption-key-kms on the command line + with a fully specified name; + ◇ provide the argument --key-ring on the command line. + The source configuration for the standby Autonomous Database. --source-config-automatic-backups-replication-enabled diff --git a/gcloud/oracle-database/autonomous-databases/help b/gcloud/oracle-database/autonomous-databases/help index 115a576a2..0a3e3e520 100644 --- a/gcloud/oracle-database/autonomous-databases/help +++ b/gcloud/oracle-database/autonomous-databases/help @@ -50,4 +50,4 @@ COMMANDS Switchovers an AutonomousDatabase to a new primary. update - Update autonomousDatabases. + Update an AutonomousDatabase. diff --git a/gcloud/oracle-database/autonomous-databases/update b/gcloud/oracle-database/autonomous-databases/update index 785acd5b1..d71cfe910 100644 --- a/gcloud/oracle-database/autonomous-databases/update +++ b/gcloud/oracle-database/autonomous-databases/update @@ -1,6 +1,6 @@ NAME - gcloud oracle-database autonomous-databases update - update - autonomousDatabases + gcloud oracle-database autonomous-databases update - update an + AutonomousDatabase SYNOPSIS gcloud oracle-database autonomous-databases update AUTONOMOUS_DATABASE @@ -11,7 +11,7 @@ SYNOPSIS [--clear-network | --network=NETWORK] [--clear-odb-subnet | --odb-subnet=ODB_SUBNET] [--clear-properties - --properties-backup-retention-period-days=PROPERTIES_BACKUP_RETENTION_PERIOD_DAYS --properties-character-set=PROPERTIES_CHARACTER_SET --properties-compute-count=PROPERTIES_COMPUTE_COUNT --properties-cpu-core-count=PROPERTIES_CPU_CORE_COUNT --properties-data-storage-size-gb=PROPERTIES_DATA_STORAGE_SIZE_GB --properties-data-storage-size-tb=PROPERTIES_DATA_STORAGE_SIZE_TB --properties-db-edition=PROPERTIES_DB_EDITION --properties-db-version=PROPERTIES_DB_VERSION --properties-db-workload=PROPERTIES_DB_WORKLOAD --[no-]properties-is-auto-scaling-enabled --[no-]properties-is-storage-auto-scaling-enabled --properties-license-type=PROPERTIES_LICENSE_TYPE --properties-maintenance-schedule-type=PROPERTIES_MAINTENANCE_SCHEDULE_TYPE --[no-]properties-mtls-connection-required --properties-n-character-set=PROPERTIES_N_CHARACTER_SET --properties-private-endpoint-ip=PROPERTIES_PRIVATE_ENDPOINT_IP --properties-private-endpoint-label=PROPERTIES_PRIVATE_ENDPOINT_LABEL --properties-secret-id=PROPERTIES_SECRET_ID --properties-vault-id=PROPERTIES_VAULT_ID --encryption-key-kms=ENCRYPTION_KEY_KMS --encryption-key-provider=ENCRYPTION_KEY_PROVIDER --properties-allowlisted-ips=[PROPERTIES_ALLOWLISTED_IPS, + --properties-backup-retention-period-days=PROPERTIES_BACKUP_RETENTION_PERIOD_DAYS --properties-character-set=PROPERTIES_CHARACTER_SET --properties-compute-count=PROPERTIES_COMPUTE_COUNT --properties-cpu-core-count=PROPERTIES_CPU_CORE_COUNT --properties-data-storage-size-gb=PROPERTIES_DATA_STORAGE_SIZE_GB --properties-data-storage-size-tb=PROPERTIES_DATA_STORAGE_SIZE_TB --properties-db-edition=PROPERTIES_DB_EDITION --properties-db-version=PROPERTIES_DB_VERSION --properties-db-workload=PROPERTIES_DB_WORKLOAD --[no-]properties-is-auto-scaling-enabled --[no-]properties-is-storage-auto-scaling-enabled --properties-license-type=PROPERTIES_LICENSE_TYPE --properties-maintenance-schedule-type=PROPERTIES_MAINTENANCE_SCHEDULE_TYPE --[no-]properties-mtls-connection-required --properties-n-character-set=PROPERTIES_N_CHARACTER_SET --properties-private-endpoint-ip=PROPERTIES_PRIVATE_ENDPOINT_IP --properties-private-endpoint-label=PROPERTIES_PRIVATE_ENDPOINT_LABEL --properties-secret-id=PROPERTIES_SECRET_ID --properties-vault-id=PROPERTIES_VAULT_ID --encryption-key-provider=ENCRYPTION_KEY_PROVIDER --key-ring=KEY_RING --clear-encryption-key-kms | --encryption-key-kms=ENCRYPTION_KEY_KMS --properties-allowlisted-ips=[PROPERTIES_ALLOWLISTED_IPS, ...] | --add-properties-allowlisted-ips=[ADD_PROPERTIES_ALLOWLISTED_IPS, ...] --clear-properties-allowlisted-ips @@ -29,12 +29,19 @@ SYNOPSIS | --remove-labels=REMOVE_LABELS] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - Update an autonomousDatabase + Update an AutonomousDatabase. EXAMPLES - To update the autonomousDatabase, run: + To Update the encryption for a given AutonomousDatabase with id + my-autonomous-database with custom KMS encryption key + projects/project-id/locations/us-east4/keyRings/keyring/cryptoKeys/key, + run: - $ gcloud oracle-database autonomous-databases update + $ gcloud oracle-database autonomous-databases update \ + my-autonomous-database --location=us-east4 \ + --properties-encryption-key-provider=GOOGLE_MANAGED \ + --properties-encryption-key-kms-key=projects/project-id/\ + locations/us-east4/keyRings/keyring/cryptoKeys/key POSITIONAL ARGUMENTS AutonomousDatabase resource - Identifier. The name of the Autonomous @@ -89,10 +96,10 @@ FLAGS be unique within your project. --location=LOCATION - For resources [autonomous_database, odb-network, odb-subnet, - source-config-autonomous-database], provides fallback value for - resource location attribute. When the resource's full URI path is not - provided, location will fallback to this flag value. + For resources [autonomous_database, encryption-key-kms, odb-network, + odb-subnet, source-config-autonomous-database], provides fallback value + for resource location attribute. When the resource's full URI path is + not provided, location will fallback to this flag value. --odb-network=ODB_NETWORK For resources [odb-network, odb-subnet], provides fallback value for @@ -279,12 +286,6 @@ FLAGS The encryption key used to encrypt the Autonomous Database. - --encryption-key-kms=ENCRYPTION_KEY_KMS - The KMS key used to encrypt the Autonomous Database. This field is - required if the provider is GOOGLE_MANAGED. The name of the KMS key - resource in the following format: - projects/{project}/locations/{location}/keyRings/{key_ring}/cryptoKeys/{crypto_key}. - --encryption-key-provider=ENCRYPTION_KEY_PROVIDER The provider of the encryption key. ENCRYPTION_KEY_PROVIDER must be one of: @@ -295,6 +296,56 @@ FLAGS oracle-managed Oracle Managed. + All arguments needed to update encryption_key_kms. + + --key-ring=KEY_RING + The keyRing id of the cryptoKey resource. + + To set the key-ring attribute: + ◇ provide the argument --current on the command line with a + fully specified name; + ◇ provide the argument --key-ring on the command line. + + Update encryption_key_kms. + + At most one of these can be specified: + + --clear-encryption-key-kms + Clear encryption_key_kms value and set to null. + + CryptoKey resource - Set encryption_key_kms to new value. + + The KMS key used to encrypt the Autonomous Database. This field is + required if the provider is GOOGLE_MANAGED. The name of the KMS + key resource in the following format: + projects/{project}/locations/{location}/keyRings/{key_ring}/cryptoKeys/{crypto_key}. + 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 --encryption-key-kms on the command line + with a fully specified name; + ▹ provide the argument --project on the command line; + ▹ set the property core/project. + + To set the location attribute: + ▹ provide the argument --encryption-key-kms on the command line + with a fully specified name; + ▹ provide the argument --location on the command line. + + To set the key-ring attribute: + ▹ provide the argument --encryption-key-kms on the command line + with a fully specified name; + ▹ provide the argument --key-ring on the command line. + + --encryption-key-kms=ENCRYPTION_KEY_KMS + ID of the cryptoKey or fully qualified identifier for the + cryptoKey. + + To set the crypto-key attribute: + ▪ provide the argument --encryption-key-kms on the command + line. + Update properties_allowlisted_ips. At most one of these can be specified: diff --git a/gcloud/oracle-database/cloud-exadata-infrastructures/db-servers/list b/gcloud/oracle-database/cloud-exadata-infrastructures/db-servers/list index c86b2cce2..99ef95eba 100644 --- a/gcloud/oracle-database/cloud-exadata-infrastructures/db-servers/list +++ b/gcloud/oracle-database/cloud-exadata-infrastructures/db-servers/list @@ -15,7 +15,8 @@ DESCRIPTION EXAMPLES To list all DbServers in the location us-east4, run: - $ gcloud oracle-database cloud-exadata-infrastructures db-servers \ list --location=us-east4 + $ gcloud oracle-database cloud-exadata-infrastructures db-servers \ + list --location=us-east4 REQUIRED FLAGS CloudExadataInfrastructure resource - The parent value for database server diff --git a/gcloud/oracle-database/cloud-vm-clusters/db-nodes/list b/gcloud/oracle-database/cloud-vm-clusters/db-nodes/list index 867f6b810..aa155dcc3 100644 --- a/gcloud/oracle-database/cloud-vm-clusters/db-nodes/list +++ b/gcloud/oracle-database/cloud-vm-clusters/db-nodes/list @@ -3,7 +3,8 @@ NAME SYNOPSIS gcloud oracle-database cloud-vm-clusters db-nodes list - (--cloud-vm-cluster=CLOUD_VM_CLUSTER : --location=LOCATION) + [--cloud-vm-cluster=CLOUD_VM_CLUSTER + --exadb-vm-cluster=EXADB_VM_CLUSTER --location=LOCATION] [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] @@ -16,36 +17,45 @@ EXAMPLES $ gcloud oracle-database cloud-vm-clusters db-nodes list \ --location=us-east4 -REQUIRED FLAGS - CloudVmCluster resource - The parent value for database node in the - following format: +FLAGS + CloudVmClusterOrExadbVmCluster resource - The parent value for database + node in the following format: projects/{project}/locations/{location}/cloudVmClusters/{cloudVmCluster}. . 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 --exadb-vm-cluster on the command line with a + fully specified name; ◆ provide the argument --cloud-vm-cluster on the command line with a fully specified name; ◆ provide the argument --project on the command line; - ◆ set the property core/project. - - This must be specified. + ◆ set the property core/project. This resource can be one of the + following types: [cloudVmCluster, exadbVmCluster]. --cloud-vm-cluster=CLOUD_VM_CLUSTER - ID of the cloudVmCluster or fully qualified identifier for the - cloudVmCluster. + ID of the cloudVmClusterOrExadbVmCluster or fully qualified + identifier for the cloudVmClusterOrExadbVmCluster. - To set the cloud-vm-cluster attribute: - ▸ provide the argument --cloud-vm-cluster on the command line. + To set the cloud_vm_cluster attribute: + ▸ provide the argument --cloud-vm-cluster on the command line. Must + be specified for resource of type [cloudVmCluster]. - This flag argument must be specified if any of the other arguments in - this group are specified. + --exadb-vm-cluster=EXADB_VM_CLUSTER + ID of the cloudVmClusterOrExadbVmCluster or fully qualified + identifier for the cloudVmClusterOrExadbVmCluster. + + To set the exadb_vm_cluster attribute: + ▸ provide the argument --exadb-vm-cluster on the command line. Must + be specified for resource of type [exadbVmCluster]. --location=LOCATION - The location id of the cloudVmCluster resource. + The location id of the cloudVmClusterOrExadbVmCluster resource. To set the location attribute: + ▸ provide the argument --exadb-vm-cluster on the command line with + a fully specified name; ▸ provide the argument --cloud-vm-cluster on the command line with a fully specified name; ▸ provide the argument --location on the command line. diff --git a/gcloud/redis/clusters/update b/gcloud/redis/clusters/update index 49e8be7e5..d2c94cb4e 100644 --- a/gcloud/redis/clusters/update +++ b/gcloud/redis/clusters/update @@ -8,7 +8,8 @@ SYNOPSIS [--automated-backup-mode=AUTOMATED_BACKUP_MODE] [--automated-backup-start-time=AUTOMATED_BACKUP_START_TIME] [--automated-backup-ttl=AUTOMATED_BACKUP_TTL] [--deletion-protection] - [--node-type=NODE_TYPE] [--persistence-mode=PERSISTENCE_MODE] + [--maintenance-version=MAINTENANCE_VERSION] [--node-type=NODE_TYPE] + [--persistence-mode=PERSISTENCE_MODE] [--rdb-snapshot-period=RDB_SNAPSHOT_PERIOD] [--rdb-snapshot-start-time=RDB_SNAPSHOT_START_TIME] [--remove-redis-config=[KEY,...]] [--replica-count=REPLICA_COUNT] @@ -106,6 +107,9 @@ FLAGS Enable deletion protection for the Redis Cluster. Use --deletion-protection/--no-deletion-protection to enable/disable it. + --maintenance-version=MAINTENANCE_VERSION + The maintenance version of the cluster. + --node-type=NODE_TYPE Node Type of the redis cluster Node. NODE_TYPE must be one of: redis-highmem-medium, redis-highmem-xlarge, redis-shared-core-nano, diff --git a/gcloud/resource-manager/tags/values/create b/gcloud/resource-manager/tags/values/create index d43e2a95b..d269c1703 100644 --- a/gcloud/resource-manager/tags/values/create +++ b/gcloud/resource-manager/tags/values/create @@ -7,19 +7,19 @@ SYNOPSIS DESCRIPTION Creates a TagValue resource given the short_name and description (optional) - as well as the parent, the of the TagValue. The parent of the TagValue is - always a TagKey and the TagKey's details can be passed as a numeric id or - the namespaced name. + as well as the parent, the of the TagValue. The parent of the TagValue can + be a TagKey or TagValue. The parent can be specified by its numeric ID or + its namespaced name. EXAMPLES - To create a TagValue with the short name 'test' and the description - 'description' under a TagKey with a short name 'env' under - 'organizations/123', run: + To create a TagValue with the short name test and the description + descriptio under a TagKey with a short name env under organizations/123, + run: $ gcloud resource-manager tags values create test --parent=123/env \ --description=description - To create a TagValue with the short name 'test' under TagKey with id '456', + To create a TagValue with the short name test under TagKey with id 456, run: $ gcloud resource-manager tags values create test \ diff --git a/gcloud/run/jobs/create b/gcloud/run/jobs/create index 33fb397e5..50c3b29d5 100644 --- a/gcloud/run/jobs/create +++ b/gcloud/run/jobs/create @@ -3,7 +3,8 @@ NAME SYNOPSIS gcloud run jobs create [JOB] [--binary-authorization=POLICY] - [--breakglass=JUSTIFICATION] [--container=CONTAINER] [--key=KEY] + [--breakglass=JUSTIFICATION] [--container=CONTAINER] + [--gpu-type=GPU_TYPE] [--[no-]gpu-zonal-redundancy] [--key=KEY] [--labels=[KEY=VALUE,...]] [--max-retries=MAX_RETRIES] [--parallelism=PARALLELISM] [--region=REGION] [--service-account=SERVICE_ACCOUNT] @@ -14,8 +15,8 @@ SYNOPSIS --clear-volumes --remove-volume=[VOLUME,...]] [--add-volume-mount=[volume=NAME,mount-path=MOUNT_PATH,...] --args=[ARG,...] --clear-volume-mounts --command=[COMMAND,...] - --cpu=CPU --depends-on=[CONTAINER,...] --image=IMAGE --memory=MEMORY - --remove-volume-mount=[MOUNT_PATH,...] + --cpu=CPU --depends-on=[CONTAINER,...] --gpu=GPU --image=IMAGE + --memory=MEMORY --remove-volume-mount=[MOUNT_PATH,...] --startup-probe=[KEY=VALUE,...] --clear-env-vars | --env-vars-file=FILE_PATH | --set-env-vars=[KEY=VALUE,...] | --remove-env-vars=[KEY,...] @@ -79,6 +80,13 @@ FLAGS Flags that are not container-specific must be specified before --container. + --gpu-type=GPU_TYPE + The GPU type to use. + + --[no-]gpu-zonal-redundancy + Set GPU zonal redundancy. Use --gpu-zonal-redundancy to enable and + --no-gpu-zonal-redundancy to disable. + --key=KEY CMEK key reference to encrypt the container with. @@ -222,6 +230,10 @@ FLAGS --depends-on=[CONTAINER,...] List of container dependencies to add to the current container. + --gpu=GPU + Cloud Run supports values 0 or 1. 1 gpu also requires a minimum 4 + --cpu value and a minimum 16Gi --memory value. + --image=IMAGE Name of the container image to deploy (e.g. us-docker.pkg.dev/cloudrun/container/job:latest). diff --git a/gcloud/run/jobs/deploy b/gcloud/run/jobs/deploy index 746948d49..d9a0a3a75 100644 --- a/gcloud/run/jobs/deploy +++ b/gcloud/run/jobs/deploy @@ -3,7 +3,8 @@ NAME SYNOPSIS gcloud run jobs deploy [JOB] [--binary-authorization=POLICY] - [--breakglass=JUSTIFICATION] [--container=CONTAINER] [--key=KEY] + [--breakglass=JUSTIFICATION] [--container=CONTAINER] + [--gpu-type=GPU_TYPE] [--[no-]gpu-zonal-redundancy] [--key=KEY] [--labels=[KEY=VALUE,...]] [--max-retries=MAX_RETRIES] [--parallelism=PARALLELISM] [--region=REGION] [--remove-containers=[CONTAINER,...]] @@ -15,7 +16,7 @@ SYNOPSIS --clear-volumes --remove-volume=[VOLUME,...]] [--add-volume-mount=[volume=NAME,mount-path=MOUNT_PATH,...] --args=[ARG,...] --clear-volume-mounts --command=[COMMAND,...] - --cpu=CPU --depends-on=[CONTAINER,...] --memory=MEMORY + --cpu=CPU --depends-on=[CONTAINER,...] --gpu=GPU --memory=MEMORY --remove-volume-mount=[MOUNT_PATH,...] --startup-probe=[KEY=VALUE,...] --clear-env-vars | --env-vars-file=FILE_PATH | --set-env-vars=[KEY=VALUE,...] @@ -81,6 +82,13 @@ FLAGS Flags that are not container-specific must be specified before --container. + --gpu-type=GPU_TYPE + The GPU type to use. + + --[no-]gpu-zonal-redundancy + Set GPU zonal redundancy. Use --gpu-zonal-redundancy to enable and + --no-gpu-zonal-redundancy to disable. + --key=KEY CMEK key reference to encrypt the container with. @@ -228,6 +236,10 @@ FLAGS --depends-on=[CONTAINER,...] List of container dependencies to add to the current container. + --gpu=GPU + Cloud Run supports values 0 or 1. 1 gpu also requires a minimum 4 + --cpu value and a minimum 16Gi --memory value. + --memory=MEMORY Set a memory limit. Ex: 1024Mi, 4Gi. diff --git a/gcloud/run/jobs/update b/gcloud/run/jobs/update index 4211c3d0a..5b26e0353 100644 --- a/gcloud/run/jobs/update +++ b/gcloud/run/jobs/update @@ -3,9 +3,10 @@ NAME SYNOPSIS gcloud run jobs update [JOB] [--breakglass=JUSTIFICATION] - [--clear-vpc-connector] [--container=CONTAINER] [--key=KEY] - [--max-retries=MAX_RETRIES] [--parallelism=PARALLELISM] - [--region=REGION] [--remove-containers=[CONTAINER,...]] + [--clear-vpc-connector] [--container=CONTAINER] [--gpu-type=GPU_TYPE] + [--[no-]gpu-zonal-redundancy] [--key=KEY] [--max-retries=MAX_RETRIES] + [--parallelism=PARALLELISM] [--region=REGION] + [--remove-containers=[CONTAINER,...]] [--service-account=SERVICE_ACCOUNT] [--task-timeout=TASK_TIMEOUT] [--tasks=TASKS; default=1] [--vpc-connector=VPC_CONNECTOR] [--vpc-egress=VPC_EGRESS] @@ -17,8 +18,8 @@ SYNOPSIS --clear-volumes --remove-volume=[VOLUME,...]] [--add-volume-mount=[volume=NAME,mount-path=MOUNT_PATH,...] --args=[ARG,...] --clear-volume-mounts --command=[COMMAND,...] - --cpu=CPU --depends-on=[CONTAINER,...] --image=IMAGE --memory=MEMORY - --remove-volume-mount=[MOUNT_PATH,...] + --cpu=CPU --depends-on=[CONTAINER,...] --gpu=GPU --image=IMAGE + --memory=MEMORY --remove-volume-mount=[MOUNT_PATH,...] --startup-probe=[KEY=VALUE,...] --clear-env-vars | --env-vars-file=FILE_PATH | --set-env-vars=[KEY=VALUE,...] | --remove-env-vars=[KEY,...] @@ -80,6 +81,13 @@ FLAGS Flags that are not container-specific must be specified before --container. + --gpu-type=GPU_TYPE + The GPU type to use. + + --[no-]gpu-zonal-redundancy + Set GPU zonal redundancy. Use --gpu-zonal-redundancy to enable and + --no-gpu-zonal-redundancy to disable. + --key=KEY CMEK key reference to encrypt the container with. @@ -239,6 +247,10 @@ FLAGS --depends-on=[CONTAINER,...] List of container dependencies to add to the current container. + --gpu=GPU + Cloud Run supports values 0 or 1. 1 gpu also requires a minimum 4 + --cpu value and a minimum 16Gi --memory value. + --image=IMAGE Name of the container image to deploy (e.g. us-docker.pkg.dev/cloudrun/container/job:latest). diff --git a/gcloud/sql/instances/create b/gcloud/sql/instances/create index 74b0f87a1..26e985634 100644 --- a/gcloud/sql/instances/create +++ b/gcloud/sql/instances/create @@ -22,9 +22,9 @@ SYNOPSIS [--deny-maintenance-period-end-date=DENY_MAINTENANCE_PERIOD_END_DATE] [--deny-maintenance-period-start-date=DENY_MAINTENANCE_PERIOD_START_DATE] [--deny-maintenance-period-time=DENY_MAINTENANCE_PERIOD_TIME] - [--edition=EDITION] [--enable-bin-log] - [--[no-]enable-connection-pooling] [--[no-]enable-data-cache] - [--[no-]enable-dataplex-integration] + [--edition=EDITION] [--enable-auto-upgrade-minor-version] + [--enable-bin-log] [--[no-]enable-connection-pooling] + [--[no-]enable-data-cache] [--[no-]enable-dataplex-integration] [--[no-]enable-google-ml-integration] [--enable-google-private-path] [--enable-password-policy] [--enable-point-in-time-recovery] [--enforce-new-sql-network-architecture] @@ -258,6 +258,10 @@ FLAGS Specifies the edition of Cloud SQL instance. EDITION must be one of: enterprise, enterprise-plus. + --enable-auto-upgrade-minor-version + Enables auto-upgrade for MySQL 8.0 minor versions. The MySQL version + must be 8.0.35 or higher. + --enable-bin-log Allows for data recovery from a specific point in time, down to a fraction of a second. Must have automatic backups enabled to use. Make diff --git a/gcloud/sql/instances/patch b/gcloud/sql/instances/patch index 495e3e1eb..1f2914f69 100644 --- a/gcloud/sql/instances/patch +++ b/gcloud/sql/instances/patch @@ -14,9 +14,9 @@ SYNOPSIS [--deny-maintenance-period-end-date=DENY_MAINTENANCE_PERIOD_END_DATE] [--deny-maintenance-period-start-date=DENY_MAINTENANCE_PERIOD_START_DATE] [--deny-maintenance-period-time=DENY_MAINTENANCE_PERIOD_TIME] [--diff] - [--edition=EDITION] [--[no-]enable-bin-log] - [--[no-]enable-connection-pooling] [--[no-]enable-data-cache] - [--[no-]enable-database-replication] + [--edition=EDITION] [--enable-auto-upgrade-minor-version] + [--[no-]enable-bin-log] [--[no-]enable-connection-pooling] + [--[no-]enable-data-cache] [--[no-]enable-database-replication] [--[no-]enable-dataplex-integration] [--[no-]enable-google-ml-integration] [--[no-]enable-google-private-path] [--enable-password-policy] @@ -197,6 +197,10 @@ FLAGS Specifies the edition of Cloud SQL instance. EDITION must be one of: enterprise, enterprise-plus. + --enable-auto-upgrade-minor-version + Enables auto-upgrade for MySQL 8.0 minor versions. The MySQL version + must be 8.0.35 or higher. + --[no-]enable-bin-log Allows for data recovery from a specific point in time, down to a fraction of a second. Must have automatic backups enabled to use. Make