From 879929cbc6eaeef9ca959b78b3fa7f7c29ce0575 Mon Sep 17 00:00:00 2001 From: Automated Date: Wed, 13 Jul 2022 09:59:38 +0000 Subject: [PATCH] gcloud: Wed Jul 13 09:59:37 UTC 2022 --- gcloud/_version | 8 +- gcloud/ai/custom-jobs/create | 2 +- gcloud/ai/hp-tuning-jobs/create | 2 +- gcloud/ai/models/delete-version | 58 ++++++ gcloud/ai/models/describe | 2 +- gcloud/ai/models/help | 7 +- gcloud/ai/models/list | 4 +- gcloud/ai/models/upload | 11 +- gcloud/alpha/ai/custom-jobs/create | 2 +- gcloud/alpha/ai/hp-tuning-jobs/create | 2 +- gcloud/alpha/ai/models/delete-version | 61 +++++++ gcloud/alpha/ai/models/describe | 2 +- gcloud/alpha/ai/models/help | 7 +- gcloud/alpha/ai/models/list | 4 +- gcloud/alpha/ai/models/upload | 11 +- gcloud/alpha/alloydb/instances/create | 8 +- gcloud/alpha/alloydb/instances/update | 8 +- gcloud/alpha/anthos/config/controller/create | 13 +- gcloud/alpha/artifacts/apt/import | 18 +- gcloud/alpha/artifacts/apt/upload | 18 +- gcloud/alpha/artifacts/files/list | 22 +-- gcloud/alpha/artifacts/print-settings/apt | 22 +-- gcloud/alpha/artifacts/print-settings/gradle | 22 +-- gcloud/alpha/artifacts/print-settings/mvn | 22 +-- gcloud/alpha/artifacts/print-settings/npm | 22 +-- gcloud/alpha/artifacts/print-settings/python | 22 +-- gcloud/alpha/artifacts/print-settings/yum | 22 +-- gcloud/alpha/artifacts/repositories/list | 6 +- gcloud/alpha/artifacts/yum/import | 18 +- gcloud/alpha/artifacts/yum/upload | 18 +- gcloud/alpha/asset/analyze-org-policies | 11 +- .../analyze-org-policy-governed-containers | 11 +- .../analyze-org-policy-governed-resources | 11 +- gcloud/alpha/auth/application-default/login | 45 ++++- gcloud/alpha/auth/login | 42 ++++- .../alpha/beyondcorp/app/connections/create | 129 ++++++++++++++ .../alpha/beyondcorp/app/connections/delete | 67 +++++++ .../alpha/beyondcorp/app/connections/describe | 72 ++++++++ gcloud/alpha/beyondcorp/app/connections/help | 42 +++++ gcloud/alpha/beyondcorp/app/connections/list | 88 ++++++++++ .../alpha/beyondcorp/app/connections/update | 117 ++++++++++++ gcloud/alpha/beyondcorp/app/connectors/create | 98 +++++++++++ gcloud/alpha/beyondcorp/app/connectors/delete | 67 +++++++ .../alpha/beyondcorp/app/connectors/describe | 75 ++++++++ gcloud/alpha/beyondcorp/app/connectors/help | 43 +++++ .../app/connectors}/list | 52 +++--- gcloud/alpha/beyondcorp/app/connectors/update | 106 +++++++++++ gcloud/alpha/beyondcorp/app/help | 47 +++++ .../beyondcorp/app/legacy/connections/create | 130 ++++++++++++++ .../beyondcorp/app/legacy/connections/delete | 68 +++++++ .../app/legacy/connections/describe | 72 ++++++++ .../beyondcorp/app/legacy/connections/help | 43 +++++ .../beyondcorp/app/legacy/connections/list | 90 ++++++++++ .../beyondcorp/app/legacy/connections/update | 119 +++++++++++++ .../beyondcorp/app/legacy/connectors/create | 98 +++++++++++ .../beyondcorp/app/legacy/connectors/delete | 68 +++++++ .../beyondcorp/app/legacy/connectors/describe | 75 ++++++++ .../beyondcorp/app/legacy/connectors/help | 44 +++++ .../beyondcorp/app/legacy/connectors/list | 89 ++++++++++ .../beyondcorp/app/legacy/connectors/update | 107 +++++++++++ gcloud/alpha/beyondcorp/app/legacy/help | 41 +++++ .../alpha/beyondcorp/app/operations/describe | 67 +++++++ .../app}/operations/help | 12 +- .../app}/operations/list | 48 +++-- .../client-connector/gateways/create | 88 ++++++++++ .../client-connector/gateways/delete | 69 ++++++++ .../client-connector/gateways/describe | 65 +++++++ .../beyondcorp/client-connector/gateways/help | 42 +++++ .../client-connector/gateways}/list | 49 +++--- gcloud/alpha/beyondcorp/client-connector/help | 44 +++++ .../client-connector/operations/describe | 67 +++++++ .../client-connector/operations}/help | 14 +- .../client-connector/operations/list | 82 +++++++++ .../client-connector/services/create | 139 +++++++++++++++ .../client-connector/services/delete | 73 ++++++++ .../client-connector/services/describe | 67 +++++++ .../beyondcorp/client-connector/services/help | 47 +++++ .../client-connector/services}/list | 52 +++--- .../client-connector/services/update | 81 +++++++++ gcloud/alpha/beyondcorp/help | 41 +++++ .../compute/firewall-policies/rules/create | 2 +- .../compute/firewall-policies/rules/update | 2 +- .../compute/instance-groups/managed/create | 31 ++-- .../compute/instance-groups/managed/update | 31 ++-- .../alpha/compute/instance-templates/create | 14 +- .../instance-templates/create-with-container | 7 +- .../network-edge-security-services/create | 4 +- .../network-edge-security-services/delete | 4 +- .../network-edge-security-services/describe | 4 +- .../network-edge-security-services/help | 4 +- .../network-edge-security-services/list | 4 +- .../network-edge-security-services/update | 4 +- .../network-firewall-policies/rules/create | 2 +- .../network-firewall-policies/rules/help | 2 +- .../network-firewall-policies/rules/update | 6 +- gcloud/alpha/compute/os-config/troubleshoot | 10 +- gcloud/alpha/compute/security-policies/update | 6 + .../compute/tpus/queued-resources/create | 19 +- gcloud/alpha/compute/tpus/tpu-vm/help | 3 + gcloud/alpha/compute/tpus/tpu-vm/scp | 17 +- .../tpus/tpu-vm/simulate-maintenance-event | 74 ++++++++ gcloud/alpha/compute/tpus/tpu-vm/ssh | 15 +- gcloud/alpha/config/list | 12 +- .../backup-restore/restore-plans/create | 65 +++++-- .../backup-restore/restore-plans/update | 65 +++++-- gcloud/alpha/container/clusters/create | 57 +++++- gcloud/alpha/container/clusters/create-auto | 8 + gcloud/alpha/container/clusters/update | 60 ++++++- .../container/fleet/memberships/register | 39 +++- .../container/fleet/memberships/unregister | 37 +++- .../alpha/container/hub/memberships/register | 39 +++- .../container/hub/memberships/unregister | 37 +++- gcloud/alpha/container/node-pools/create | 29 ++- gcloud/alpha/container/node-pools/update | 32 +++- gcloud/alpha/dataplex/tasks/create | 14 ++ gcloud/alpha/dataplex/tasks/update | 16 +- gcloud/alpha/dataproc/clusters/gke/create | 108 ++++-------- gcloud/alpha/deploy/targets/rollback | 25 ++- gcloud/alpha/functions/deploy | 2 +- gcloud/alpha/functions/help | 3 + .../locations => functions/runtimes}/help | 16 +- gcloud/alpha/functions/runtimes/list | 72 ++++++++ gcloud/alpha/ids/help | 3 + .../describe => ids/operations/cancel} | 38 ++-- gcloud/alpha/ids/operations/describe | 63 +++++++ gcloud/alpha/ids/operations/help | 40 +++++ gcloud/alpha/ids/operations/list | 81 +++++++++ gcloud/alpha/ids/operations/wait | 71 ++++++++ gcloud/alpha/kms/keys/versions/import | 19 +- gcloud/alpha/ml/speech/recognize | 11 ++ gcloud/alpha/ml/speech/recognize-long-running | 11 ++ gcloud/alpha/recommender/insights/list | 2 +- gcloud/alpha/run/jobs/create | 2 +- gcloud/alpha/run/jobs/update | 2 +- gcloud/alpha/spanner/help | 3 + gcloud/alpha/spanner/samples/backend | 63 +++++++ gcloud/alpha/spanner/samples/help | 48 +++++ gcloud/alpha/spanner/samples/init | 42 +++++ .../locations => spanner/samples}/list | 12 +- gcloud/alpha/spanner/samples/run | 60 +++++++ gcloud/alpha/spanner/samples/workload | 54 ++++++ gcloud/alpha/sql/instances/create | 12 +- gcloud/alpha/sql/instances/patch | 12 +- gcloud/alpha/sql/users/create | 17 +- gcloud/alpha/sql/users/set-password | 11 ++ gcloud/alpha/sql/users/set-password-policy | 17 +- gcloud/alpha/transfer/agents/install | 7 +- gcloud/alpha/vmware/clusters/create | 108 ------------ gcloud/alpha/vmware/clusters/delete | 81 --------- gcloud/alpha/vmware/clusters/describe | 75 -------- gcloud/alpha/vmware/clusters/help | 39 ---- gcloud/alpha/vmware/clusters/list | 99 ----------- gcloud/alpha/vmware/clusters/update | 86 --------- gcloud/alpha/vmware/hcx/activationkeys/create | 85 --------- .../alpha/vmware/hcx/activationkeys/describe | 76 -------- gcloud/alpha/vmware/hcx/activationkeys/help | 34 ---- gcloud/alpha/vmware/hcx/activationkeys/list | 101 ----------- gcloud/alpha/vmware/hcx/help | 27 --- gcloud/alpha/vmware/help | 35 ---- gcloud/alpha/vmware/network-peerings/create | 166 ------------------ gcloud/alpha/vmware/network-peerings/delete | 59 ------- gcloud/alpha/vmware/network-peerings/describe | 51 ------ gcloud/alpha/vmware/network-peerings/help | 46 ----- .../alpha/vmware/network-peerings/routes/help | 28 --- .../alpha/vmware/network-peerings/routes/list | 91 ---------- gcloud/alpha/vmware/network-peerings/update | 62 ------- gcloud/alpha/vmware/network-policies/create | 138 --------------- gcloud/alpha/vmware/network-policies/delete | 73 -------- gcloud/alpha/vmware/network-policies/describe | 67 ------- gcloud/alpha/vmware/network-policies/help | 40 ----- gcloud/alpha/vmware/network-policies/list | 100 ----------- gcloud/alpha/vmware/network-policies/update | 93 ---------- gcloud/alpha/vmware/node-types/describe | 66 ------- gcloud/alpha/vmware/nsx/credentials/describe | 69 -------- gcloud/alpha/vmware/nsx/credentials/help | 32 ---- gcloud/alpha/vmware/nsx/credentials/reset | 76 -------- gcloud/alpha/vmware/nsx/help | 26 --- gcloud/alpha/vmware/private-clouds/create | 145 --------------- gcloud/alpha/vmware/private-clouds/delete | 79 --------- gcloud/alpha/vmware/private-clouds/describe | 66 ------- gcloud/alpha/vmware/private-clouds/help | 42 ----- gcloud/alpha/vmware/private-clouds/undelete | 72 -------- gcloud/alpha/vmware/private-clouds/update | 78 -------- .../alpha/vmware/vcenter/credentials/describe | 70 -------- gcloud/alpha/vmware/vcenter/credentials/help | 31 ---- gcloud/alpha/vmware/vcenter/credentials/reset | 77 -------- gcloud/alpha/vmware/vcenter/help | 28 --- gcloud/anthos/config/controller/create | 13 +- gcloud/artifacts/apt/import | 18 +- gcloud/artifacts/apt/upload | 18 +- gcloud/artifacts/files/list | 22 +-- gcloud/artifacts/print-settings/gradle | 22 +-- gcloud/artifacts/print-settings/mvn | 22 +-- gcloud/artifacts/print-settings/npm | 22 +-- gcloud/artifacts/print-settings/python | 22 +-- gcloud/artifacts/repositories/list | 6 +- gcloud/artifacts/yum/import | 18 +- gcloud/artifacts/yum/upload | 18 +- gcloud/auth/application-default/login | 45 ++++- gcloud/auth/login | 42 ++++- gcloud/beta/ai/custom-jobs/create | 2 +- gcloud/beta/ai/hp-tuning-jobs/create | 2 +- gcloud/beta/ai/models/delete-version | 59 +++++++ gcloud/beta/ai/models/describe | 2 +- gcloud/beta/ai/models/help | 7 +- gcloud/beta/ai/models/list | 4 +- gcloud/beta/ai/models/upload | 11 +- gcloud/beta/alloydb/instances/create | 8 +- gcloud/beta/alloydb/instances/update | 8 +- gcloud/beta/artifacts/apt/import | 18 +- gcloud/beta/artifacts/apt/upload | 18 +- gcloud/beta/artifacts/files/list | 22 +-- gcloud/beta/artifacts/print-settings/apt | 22 +-- gcloud/beta/artifacts/print-settings/gradle | 22 +-- gcloud/beta/artifacts/print-settings/mvn | 22 +-- gcloud/beta/artifacts/print-settings/npm | 22 +-- gcloud/beta/artifacts/print-settings/python | 22 +-- gcloud/beta/artifacts/print-settings/yum | 22 +-- gcloud/beta/artifacts/repositories/list | 6 +- gcloud/beta/artifacts/yum/import | 18 +- gcloud/beta/artifacts/yum/upload | 18 +- gcloud/beta/auth/application-default/login | 45 ++++- gcloud/beta/auth/login | 42 ++++- gcloud/beta/compute/help | 3 + .../compute/instance-groups/managed/create | 31 ++-- .../compute/instance-groups/managed/update | 31 ++-- gcloud/beta/compute/instance-templates/create | 3 - .../network-edge-security-services/create | 69 ++++++++ .../network-edge-security-services/delete | 42 +++++ .../network-edge-security-services/describe | 43 +++++ .../network-edge-security-services/help | 47 +++++ .../network-edge-security-services/list | 78 ++++++++ .../network-edge-security-services/update | 69 ++++++++ gcloud/beta/compute/security-policies/create | 14 +- gcloud/beta/compute/security-policies/delete | 12 +- .../beta/compute/security-policies/describe | 13 +- gcloud/beta/compute/security-policies/export | 12 +- gcloud/beta/compute/security-policies/help | 2 +- gcloud/beta/compute/security-policies/import | 12 +- gcloud/beta/compute/security-policies/list | 41 +++-- gcloud/beta/compute/security-policies/update | 17 +- gcloud/beta/config/list | 12 +- .../backup-restore/restore-plans/create | 65 +++++-- .../backup-restore/restore-plans/update | 65 +++++-- gcloud/beta/container/clusters/create | 57 +++++- gcloud/beta/container/clusters/create-auto | 8 + gcloud/beta/container/clusters/update | 60 ++++++- .../beta/container/fleet/memberships/register | 4 +- .../container/fleet/memberships/unregister | 7 +- .../beta/container/hub/memberships/register | 4 +- .../beta/container/hub/memberships/unregister | 7 +- gcloud/beta/container/node-pools/create | 29 ++- gcloud/beta/container/node-pools/update | 32 +++- gcloud/beta/dataproc/clusters/gke/create | 108 ++++-------- .../datastream/connection-profiles/create | 29 ++- .../datastream/connection-profiles/update | 2 +- gcloud/beta/datastream/streams/create | 43 +++-- gcloud/beta/datastream/streams/update | 42 +++-- gcloud/beta/deploy/targets/rollback | 25 ++- gcloud/beta/functions/deploy | 2 +- gcloud/beta/functions/help | 3 + gcloud/beta/functions/runtimes/help | 29 +++ gcloud/beta/functions/runtimes/list | 70 ++++++++ gcloud/beta/kms/keys/versions/import | 19 +- gcloud/beta/ml/speech/recognize | 11 ++ gcloud/beta/ml/speech/recognize-long-running | 11 ++ gcloud/beta/recommender/insights/list | 2 +- gcloud/beta/run/jobs/create | 2 +- gcloud/beta/run/jobs/update | 2 +- gcloud/beta/sql/instances/create | 12 +- gcloud/beta/sql/instances/patch | 12 +- gcloud/beta/sql/users/create | 17 +- gcloud/beta/sql/users/set-password | 11 ++ gcloud/beta/sql/users/set-password-policy | 17 +- gcloud/compute/instance-groups/managed/create | 25 ++- gcloud/compute/instance-groups/managed/update | 25 ++- gcloud/compute/instance-templates/create | 16 +- gcloud/compute/instances/bulk/create | 20 +++ gcloud/compute/instances/create | 12 +- gcloud/config/list | 11 +- gcloud/container/clusters/create | 78 ++++++-- gcloud/container/clusters/create-auto | 8 + gcloud/container/clusters/update | 73 ++++++-- gcloud/container/fleet/memberships/register | 4 +- gcloud/container/fleet/memberships/unregister | 7 +- gcloud/container/hub/memberships/register | 4 +- gcloud/container/hub/memberships/unregister | 7 +- gcloud/container/node-pools/create | 29 ++- gcloud/container/node-pools/update | 32 +++- gcloud/dataplex/tasks/create | 14 ++ gcloud/dataplex/tasks/update | 16 +- gcloud/dataproc/clusters/gke/create | 108 ++++-------- gcloud/datastream/connection-profiles/create | 40 +++-- gcloud/datastream/connection-profiles/update | 7 +- gcloud/datastream/streams/create | 52 ++++-- gcloud/datastream/streams/update | 42 +++-- gcloud/deploy/targets/rollback | 24 ++- gcloud/eventarc/channels/create | 2 +- gcloud/eventarc/channels/delete | 4 +- gcloud/eventarc/channels/describe | 4 +- gcloud/eventarc/channels/help | 6 +- gcloud/eventarc/channels/update | 10 +- gcloud/eventarc/google-channels/describe | 6 +- gcloud/eventarc/google-channels/help | 4 +- gcloud/eventarc/google-channels/update | 14 +- gcloud/functions/deploy | 19 +- gcloud/functions/help | 3 + gcloud/functions/runtimes/help | 28 +++ gcloud/functions/runtimes/list | 69 ++++++++ gcloud/kms/keys/versions/import | 19 +- gcloud/ml/speech/recognize | 11 ++ gcloud/ml/speech/recognize-long-running | 11 ++ gcloud/recommender/insights/list | 2 +- gcloud/redis/instances/create | 29 +++ gcloud/redis/instances/update | 29 +++ gcloud/sql/instances/create | 12 +- gcloud/sql/instances/patch | 12 +- gcloud/sql/users/create | 17 +- gcloud/sql/users/set-password | 14 +- gcloud/sql/users/set-password-policy | 17 +- gcloud/transcoder/jobs/create | 16 +- gcloud/transcoder/templates/create | 17 +- gcloud/transfer/agents/install | 7 +- 323 files changed, 7203 insertions(+), 4178 deletions(-) create mode 100644 gcloud/ai/models/delete-version create mode 100644 gcloud/alpha/ai/models/delete-version create mode 100644 gcloud/alpha/beyondcorp/app/connections/create create mode 100644 gcloud/alpha/beyondcorp/app/connections/delete create mode 100644 gcloud/alpha/beyondcorp/app/connections/describe create mode 100644 gcloud/alpha/beyondcorp/app/connections/help create mode 100644 gcloud/alpha/beyondcorp/app/connections/list create mode 100644 gcloud/alpha/beyondcorp/app/connections/update create mode 100644 gcloud/alpha/beyondcorp/app/connectors/create create mode 100644 gcloud/alpha/beyondcorp/app/connectors/delete create mode 100644 gcloud/alpha/beyondcorp/app/connectors/describe create mode 100644 gcloud/alpha/beyondcorp/app/connectors/help rename gcloud/alpha/{vmware/node-types => beyondcorp/app/connectors}/list (65%) create mode 100644 gcloud/alpha/beyondcorp/app/connectors/update create mode 100644 gcloud/alpha/beyondcorp/app/help create mode 100644 gcloud/alpha/beyondcorp/app/legacy/connections/create create mode 100644 gcloud/alpha/beyondcorp/app/legacy/connections/delete create mode 100644 gcloud/alpha/beyondcorp/app/legacy/connections/describe create mode 100644 gcloud/alpha/beyondcorp/app/legacy/connections/help create mode 100644 gcloud/alpha/beyondcorp/app/legacy/connections/list create mode 100644 gcloud/alpha/beyondcorp/app/legacy/connections/update create mode 100644 gcloud/alpha/beyondcorp/app/legacy/connectors/create create mode 100644 gcloud/alpha/beyondcorp/app/legacy/connectors/delete create mode 100644 gcloud/alpha/beyondcorp/app/legacy/connectors/describe create mode 100644 gcloud/alpha/beyondcorp/app/legacy/connectors/help create mode 100644 gcloud/alpha/beyondcorp/app/legacy/connectors/list create mode 100644 gcloud/alpha/beyondcorp/app/legacy/connectors/update create mode 100644 gcloud/alpha/beyondcorp/app/legacy/help create mode 100644 gcloud/alpha/beyondcorp/app/operations/describe rename gcloud/alpha/{vmware => beyondcorp/app}/operations/help (56%) rename gcloud/alpha/{vmware => beyondcorp/app}/operations/list (67%) create mode 100644 gcloud/alpha/beyondcorp/client-connector/gateways/create create mode 100644 gcloud/alpha/beyondcorp/client-connector/gateways/delete create mode 100644 gcloud/alpha/beyondcorp/client-connector/gateways/describe create mode 100644 gcloud/alpha/beyondcorp/client-connector/gateways/help rename gcloud/alpha/{vmware/private-clouds => beyondcorp/client-connector/gateways}/list (67%) create mode 100644 gcloud/alpha/beyondcorp/client-connector/help create mode 100644 gcloud/alpha/beyondcorp/client-connector/operations/describe rename gcloud/alpha/{vmware/node-types => beyondcorp/client-connector/operations}/help (53%) create mode 100644 gcloud/alpha/beyondcorp/client-connector/operations/list create mode 100644 gcloud/alpha/beyondcorp/client-connector/services/create create mode 100644 gcloud/alpha/beyondcorp/client-connector/services/delete create mode 100644 gcloud/alpha/beyondcorp/client-connector/services/describe create mode 100644 gcloud/alpha/beyondcorp/client-connector/services/help rename gcloud/alpha/{vmware/network-peerings => beyondcorp/client-connector/services}/list (65%) create mode 100644 gcloud/alpha/beyondcorp/client-connector/services/update create mode 100644 gcloud/alpha/beyondcorp/help create mode 100644 gcloud/alpha/compute/tpus/tpu-vm/simulate-maintenance-event rename gcloud/alpha/{vmware/locations => functions/runtimes}/help (50%) create mode 100644 gcloud/alpha/functions/runtimes/list rename gcloud/alpha/{vmware/operations/describe => ids/operations/cancel} (57%) create mode 100644 gcloud/alpha/ids/operations/describe create mode 100644 gcloud/alpha/ids/operations/help create mode 100644 gcloud/alpha/ids/operations/list create mode 100644 gcloud/alpha/ids/operations/wait create mode 100644 gcloud/alpha/spanner/samples/backend create mode 100644 gcloud/alpha/spanner/samples/help create mode 100644 gcloud/alpha/spanner/samples/init rename gcloud/alpha/{vmware/locations => spanner/samples}/list (88%) create mode 100644 gcloud/alpha/spanner/samples/run create mode 100644 gcloud/alpha/spanner/samples/workload delete mode 100644 gcloud/alpha/vmware/clusters/create delete mode 100644 gcloud/alpha/vmware/clusters/delete delete mode 100644 gcloud/alpha/vmware/clusters/describe delete mode 100644 gcloud/alpha/vmware/clusters/help delete mode 100644 gcloud/alpha/vmware/clusters/list delete mode 100644 gcloud/alpha/vmware/clusters/update delete mode 100644 gcloud/alpha/vmware/hcx/activationkeys/create delete mode 100644 gcloud/alpha/vmware/hcx/activationkeys/describe delete mode 100644 gcloud/alpha/vmware/hcx/activationkeys/help delete mode 100644 gcloud/alpha/vmware/hcx/activationkeys/list delete mode 100644 gcloud/alpha/vmware/hcx/help delete mode 100644 gcloud/alpha/vmware/network-peerings/create delete mode 100644 gcloud/alpha/vmware/network-peerings/delete delete mode 100644 gcloud/alpha/vmware/network-peerings/describe delete mode 100644 gcloud/alpha/vmware/network-peerings/help delete mode 100644 gcloud/alpha/vmware/network-peerings/routes/help delete mode 100644 gcloud/alpha/vmware/network-peerings/routes/list delete mode 100644 gcloud/alpha/vmware/network-peerings/update delete mode 100644 gcloud/alpha/vmware/network-policies/create delete mode 100644 gcloud/alpha/vmware/network-policies/delete delete mode 100644 gcloud/alpha/vmware/network-policies/describe delete mode 100644 gcloud/alpha/vmware/network-policies/help delete mode 100644 gcloud/alpha/vmware/network-policies/list delete mode 100644 gcloud/alpha/vmware/network-policies/update delete mode 100644 gcloud/alpha/vmware/node-types/describe delete mode 100644 gcloud/alpha/vmware/nsx/credentials/describe delete mode 100644 gcloud/alpha/vmware/nsx/credentials/help delete mode 100644 gcloud/alpha/vmware/nsx/credentials/reset delete mode 100644 gcloud/alpha/vmware/nsx/help delete mode 100644 gcloud/alpha/vmware/private-clouds/create delete mode 100644 gcloud/alpha/vmware/private-clouds/delete delete mode 100644 gcloud/alpha/vmware/private-clouds/describe delete mode 100644 gcloud/alpha/vmware/private-clouds/help delete mode 100644 gcloud/alpha/vmware/private-clouds/undelete delete mode 100644 gcloud/alpha/vmware/private-clouds/update delete mode 100644 gcloud/alpha/vmware/vcenter/credentials/describe delete mode 100644 gcloud/alpha/vmware/vcenter/credentials/help delete mode 100644 gcloud/alpha/vmware/vcenter/credentials/reset delete mode 100644 gcloud/alpha/vmware/vcenter/help create mode 100644 gcloud/beta/ai/models/delete-version create mode 100644 gcloud/beta/compute/network-edge-security-services/create create mode 100644 gcloud/beta/compute/network-edge-security-services/delete create mode 100644 gcloud/beta/compute/network-edge-security-services/describe create mode 100644 gcloud/beta/compute/network-edge-security-services/help create mode 100644 gcloud/beta/compute/network-edge-security-services/list create mode 100644 gcloud/beta/compute/network-edge-security-services/update create mode 100644 gcloud/beta/functions/runtimes/help create mode 100644 gcloud/beta/functions/runtimes/list create mode 100644 gcloud/functions/runtimes/help create mode 100644 gcloud/functions/runtimes/list diff --git a/gcloud/_version b/gcloud/_version index 7d03eab02..770ea4337 100644 --- a/gcloud/_version +++ b/gcloud/_version @@ -1,6 +1,6 @@ -Google Cloud SDK 392.0.0 -alpha 2022.06.24 -beta 2022.06.24 +Google Cloud SDK 393.0.0 +alpha 2022.07.08 +beta 2022.07.08 bq 2.0.75 -core 2022.06.24 +core 2022.07.08 gsutil 5.10 diff --git a/gcloud/ai/custom-jobs/create b/gcloud/ai/custom-jobs/create index ff3fa87a1..971ec6504 100644 --- a/gcloud/ai/custom-jobs/create +++ b/gcloud/ai/custom-jobs/create @@ -156,7 +156,7 @@ OPTIONAL FLAGS entrypoint instruction in Dockerfile when provided. --enable-web-access - Whether you want Vertex AI to enable [interactive shell access] + Whether you want Vertex AI to enable interactive shell access (https://cloud.google.com/vertex-ai/docs/training/monitor-debug-interactive-shell) to training containers. If set to true, you can access interactive shells at the URIs given by CustomJob.web_access_uris or diff --git a/gcloud/ai/hp-tuning-jobs/create b/gcloud/ai/hp-tuning-jobs/create index 79c86479b..776cc74b1 100644 --- a/gcloud/ai/hp-tuning-jobs/create +++ b/gcloud/ai/hp-tuning-jobs/create @@ -61,7 +61,7 @@ OPTIONAL FLAGS of: algorithm-unspecified, grid-search, random-search. --enable-web-access - Whether you want Vertex AI to enable [interactive shell access] + Whether you want Vertex AI to enable interactive shell access (https://cloud.google.com/vertex-ai/docs/training/monitor-debug-interactive-shell) to training containers. If set to true, you can access interactive shells at the URIs given by CustomJob.web_access_uris or diff --git a/gcloud/ai/models/delete-version b/gcloud/ai/models/delete-version new file mode 100644 index 000000000..2a9ceb909 --- /dev/null +++ b/gcloud/ai/models/delete-version @@ -0,0 +1,58 @@ +NAME + gcloud ai models delete-version - delete an existing Vertex AI model + version + +SYNOPSIS + gcloud ai models delete-version (MODEL_VERSION : --region=REGION) + [GCLOUD_WIDE_FLAG ...] + +EXAMPLES + To delete a model 123 version 1234 under project example in region + us-central1, run: + + $ gcloud ai models delete-version 123@1234 --project=example \ + --region=us-central1 + +POSITIONAL ARGUMENTS + Model resource - Model version 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 model_version 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. + + MODEL_VERSION + ID of the model or fully qualified identifier for the model. To set + the name attribute: + ▸ provide the argument model_version on the command line. + + This positional must be specified if any of the other arguments in + this group are specified. + + --region=REGION + Cloud region for the model. To set the region attribute: + ▸ provide the argument model_version on the command line with a + fully specified name; + ▸ provide the argument --region on the command line; + ▸ set the property ai/region; + ▸ choose one from the prompted list of available regions. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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 ai models delete-version + + $ gcloud beta ai models delete-version + diff --git a/gcloud/ai/models/describe b/gcloud/ai/models/describe index f7dadbc5d..2aa28c8ab 100644 --- a/gcloud/ai/models/describe +++ b/gcloud/ai/models/describe @@ -1,5 +1,5 @@ NAME - gcloud ai models describe - gets detailed model information about the given + gcloud ai models describe - get detailed model information about the given model id SYNOPSIS diff --git a/gcloud/ai/models/help b/gcloud/ai/models/help index d5a191c5a..c82fc8c65 100644 --- a/gcloud/ai/models/help +++ b/gcloud/ai/models/help @@ -18,11 +18,14 @@ COMMANDS delete Delete an existing Vertex AI model. + delete-version + Delete an existing Vertex AI model version. + describe - Gets detailed model information about the given model id. + Get detailed model information about the given model id. list - Lists the models of the given project and region. + List the models of the given project and region. upload Upload a new model. diff --git a/gcloud/ai/models/list b/gcloud/ai/models/list index 5f1d32b1e..fdd61461c 100644 --- a/gcloud/ai/models/list +++ b/gcloud/ai/models/list @@ -1,5 +1,5 @@ NAME - gcloud ai models list - lists the models of the given project and region + gcloud ai models list - list the models of the given project and region SYNOPSIS gcloud ai models list [--region=REGION] [--filter=EXPRESSION] @@ -7,7 +7,7 @@ SYNOPSIS [GCLOUD_WIDE_FLAG ...] EXAMPLES - Lists the models of project example in region us-central1, run: + List the models of project example in region us-central1, run: $ gcloud ai models list --project=example --region=us-central1 diff --git a/gcloud/ai/models/upload b/gcloud/ai/models/upload index b811ed6ad..c057e389c 100644 --- a/gcloud/ai/models/upload +++ b/gcloud/ai/models/upload @@ -13,7 +13,8 @@ SYNOPSIS [--explanation-metadata-file=EXPLANATION_METADATA_FILE] [--explanation-method=EXPLANATION_METHOD] [--explanation-path-count=EXPLANATION_PATH_COUNT] - [--explanation-step-count=EXPLANATION_STEP_COUNT] [--region=REGION] + [--explanation-step-count=EXPLANATION_STEP_COUNT] [--model-id=MODEL_ID] + [--parent-model=PARENT_MODEL] [--region=REGION] [--smooth-grad-noise-sigma=SMOOTH_GRAD_NOISE_SIGMA] [--smooth-grad-noise-sigma-by-feature=[KEY=VALUE,...]] [--smooth-grad-noisy-sample-count=SMOOTH_GRAD_NOISY_SAMPLE_COUNT] @@ -81,6 +82,14 @@ OPTIONAL FLAGS --explanation-step-count=EXPLANATION_STEP_COUNT Number of steps to approximate the path integral for explanation. + --model-id=MODEL_ID + ID to use for the uploaded Model, which will become the final component + of the model resource name. + + --parent-model=PARENT_MODEL + Resource name of the model into which to upload the version. Only + specify this field when uploading a new version. + Region resource - Cloud region to upload model. This represents a Cloud resource. (NOTE) Some attributes are not given arguments in this group but can be set in other ways. To set the project attribute: diff --git a/gcloud/alpha/ai/custom-jobs/create b/gcloud/alpha/ai/custom-jobs/create index b67f0e448..d15f753be 100644 --- a/gcloud/alpha/ai/custom-jobs/create +++ b/gcloud/alpha/ai/custom-jobs/create @@ -157,7 +157,7 @@ OPTIONAL FLAGS entrypoint instruction in Dockerfile when provided. --enable-web-access - Whether you want Vertex AI to enable [interactive shell access] + Whether you want Vertex AI to enable interactive shell access (https://cloud.google.com/vertex-ai/docs/training/monitor-debug-interactive-shell) to training containers. If set to true, you can access interactive shells at the URIs given by CustomJob.web_access_uris or diff --git a/gcloud/alpha/ai/hp-tuning-jobs/create b/gcloud/alpha/ai/hp-tuning-jobs/create index 0525521c1..c84b2fae3 100644 --- a/gcloud/alpha/ai/hp-tuning-jobs/create +++ b/gcloud/alpha/ai/hp-tuning-jobs/create @@ -61,7 +61,7 @@ OPTIONAL FLAGS of: algorithm-unspecified, grid-search, random-search. --enable-web-access - Whether you want Vertex AI to enable [interactive shell access] + Whether you want Vertex AI to enable interactive shell access (https://cloud.google.com/vertex-ai/docs/training/monitor-debug-interactive-shell) to training containers. If set to true, you can access interactive shells at the URIs given by CustomJob.web_access_uris or diff --git a/gcloud/alpha/ai/models/delete-version b/gcloud/alpha/ai/models/delete-version new file mode 100644 index 000000000..90e9ea641 --- /dev/null +++ b/gcloud/alpha/ai/models/delete-version @@ -0,0 +1,61 @@ +NAME + gcloud alpha ai models delete-version - delete an existing Vertex AI model + version + +SYNOPSIS + gcloud alpha ai models delete-version (MODEL_VERSION : --region=REGION) + [GCLOUD_WIDE_FLAG ...] + +EXAMPLES + To delete a model 123 of version 1234 under project example in region + us-central1, run: + + $ gcloud alpha ai models delete-version 123@1234 --project=example \ + --region=us-central1 + +POSITIONAL ARGUMENTS + Model resource - Model version 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 model_version 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. + + MODEL_VERSION + ID of the model or fully qualified identifier for the model. To set + the name attribute: + ▸ provide the argument model_version on the command line. + + This positional must be specified if any of the other arguments in + this group are specified. + + --region=REGION + Cloud region for the model. To set the region attribute: + ▸ provide the argument model_version on the command line with a + fully specified name; + ▸ provide the argument --region on the command line; + ▸ set the property ai/region; + ▸ choose one from the prompted list of available regions. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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 ai models delete-version + + $ gcloud beta ai models delete-version + diff --git a/gcloud/alpha/ai/models/describe b/gcloud/alpha/ai/models/describe index 1e86b913e..f55bfe483 100644 --- a/gcloud/alpha/ai/models/describe +++ b/gcloud/alpha/ai/models/describe @@ -1,5 +1,5 @@ NAME - gcloud alpha ai models describe - gets detailed model information about the + gcloud alpha ai models describe - get detailed model information about the given model id SYNOPSIS diff --git a/gcloud/alpha/ai/models/help b/gcloud/alpha/ai/models/help index 23b6da98e..ecafd0d5f 100644 --- a/gcloud/alpha/ai/models/help +++ b/gcloud/alpha/ai/models/help @@ -18,11 +18,14 @@ COMMANDS delete (ALPHA) Delete an existing Vertex AI model. + delete-version + (ALPHA) Delete an existing Vertex AI model version. + describe - (ALPHA) Gets detailed model information about the given model id. + (ALPHA) Get detailed model information about the given model id. list - (ALPHA) Lists the models of the given project and region. + (ALPHA) List the models of the given project and region. upload (ALPHA) Upload a new model. diff --git a/gcloud/alpha/ai/models/list b/gcloud/alpha/ai/models/list index ca7256502..07275b35c 100644 --- a/gcloud/alpha/ai/models/list +++ b/gcloud/alpha/ai/models/list @@ -1,5 +1,5 @@ NAME - gcloud alpha ai models list - lists the models of the given project and + gcloud alpha ai models list - list the models of the given project and region SYNOPSIS @@ -8,7 +8,7 @@ SYNOPSIS [GCLOUD_WIDE_FLAG ...] EXAMPLES - Lists the models of project example in region us-central1, run: + List the models of project example in region us-central1, run: $ gcloud alpha ai models list --project=example --region=us-central1 diff --git a/gcloud/alpha/ai/models/upload b/gcloud/alpha/ai/models/upload index 12bde610a..e8faf4859 100644 --- a/gcloud/alpha/ai/models/upload +++ b/gcloud/alpha/ai/models/upload @@ -13,7 +13,8 @@ SYNOPSIS [--explanation-metadata-file=EXPLANATION_METADATA_FILE] [--explanation-method=EXPLANATION_METHOD] [--explanation-path-count=EXPLANATION_PATH_COUNT] - [--explanation-step-count=EXPLANATION_STEP_COUNT] [--region=REGION] + [--explanation-step-count=EXPLANATION_STEP_COUNT] [--model-id=MODEL_ID] + [--parent-model=PARENT_MODEL] [--region=REGION] [--smooth-grad-noise-sigma=SMOOTH_GRAD_NOISE_SIGMA] [--smooth-grad-noise-sigma-by-feature=[KEY=VALUE,...]] [--smooth-grad-noisy-sample-count=SMOOTH_GRAD_NOISY_SAMPLE_COUNT] @@ -81,6 +82,14 @@ OPTIONAL FLAGS --explanation-step-count=EXPLANATION_STEP_COUNT Number of steps to approximate the path integral for explanation. + --model-id=MODEL_ID + ID to use for the uploaded Model, which will become the final component + of the model resource name. + + --parent-model=PARENT_MODEL + Resource name of the model into which to upload the version. Only + specify this field when uploading a new version. + Region resource - Cloud region to upload model. This represents a Cloud resource. (NOTE) Some attributes are not given arguments in this group but can be set in other ways. To set the project attribute: diff --git a/gcloud/alpha/alloydb/instances/create b/gcloud/alpha/alloydb/instances/create index 75bbf48c1..c9cb0193a 100644 --- a/gcloud/alpha/alloydb/instances/create +++ b/gcloud/alpha/alloydb/instances/create @@ -7,8 +7,7 @@ SYNOPSIS --cpu-count=CPU_COUNT --instance-type=INSTANCE_TYPE --region=REGION [--async] [--availability-type=AVAILABILITY_TYPE] [--database-flags=FLAG=VALUE,[FLAG=VALUE,...]] - [--read-pool-node-count=READ_POOL_NODE_COUNT] [--zone=ZONE] - [GCLOUD_WIDE_FLAG ...] + [--read-pool-node-count=READ_POOL_NODE_COUNT] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Creates a new AlloyDB instance within a given cluster. @@ -38,7 +37,7 @@ REQUIRED FLAGS Whole number value indicating how many vCPUs the machine should contain. Each vCPU count corresponds to a N2 high-mem machine: (https://cloud.google.com/compute/docs/general-purpose-machines#n2_machines). - CPU_COUNT must be one of: 4, 8, 16, 32, 64. + CPU_COUNT must be one of: 2, 4, 8, 16, 32, 64. --instance-type=INSTANCE_TYPE Specifies instance type. INSTANCE_TYPE must be one of: @@ -81,9 +80,6 @@ OPTIONAL FLAGS --read-pool-node-count=READ_POOL_NODE_COUNT Read capacity, i.e. number of nodes in a read pool instance. - --zone=ZONE - Primary Compute Engine zone (e.g. us-central1, us-central1, etc. - 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/alloydb/instances/update b/gcloud/alpha/alloydb/instances/update index f9d48c5a7..0f8ce51f7 100644 --- a/gcloud/alpha/alloydb/instances/update +++ b/gcloud/alpha/alloydb/instances/update @@ -6,8 +6,7 @@ SYNOPSIS gcloud alpha alloydb instances update INSTANCE --cluster=CLUSTER --region=REGION [--async] [--availability-type=AVAILABILITY_TYPE] [--cpu-count=CPU_COUNT] [--database-flags=FLAG=VALUE,[FLAG=VALUE,...]] - [--read-pool-node-count=READ_POOL_NODE_COUNT] [--zone=ZONE] - [GCLOUD_WIDE_FLAG ...] + [--read-pool-node-count=READ_POOL_NODE_COUNT] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Updates an AlloyDB instance within a given cluster. @@ -49,7 +48,7 @@ OPTIONAL FLAGS Whole number value indicating how many vCPUs the machine should contain. Each vCPU count corresponds to a N2 high-mem machine: (https://cloud.google.com/compute/docs/general-purpose-machines#n2_machines). - CPU_COUNT must be one of: 4, 8, 16, 32, 64. + CPU_COUNT must be one of: 2, 4, 8, 16, 32, 64. --database-flags=FLAG=VALUE,[FLAG=VALUE,...] Comma-separated list of database flags to set on the instance. Use an @@ -62,9 +61,6 @@ OPTIONAL FLAGS --read-pool-node-count=READ_POOL_NODE_COUNT Read capacity, i.e. number of nodes in a read pool instance. - --zone=ZONE - Primary Compute Engine zone (e.g. us-central1, us-central1, etc. - 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/anthos/config/controller/create b/gcloud/alpha/anthos/config/controller/create index 70c13c1a7..d69611a7f 100644 --- a/gcloud/alpha/anthos/config/controller/create +++ b/gcloud/alpha/anthos/config/controller/create @@ -7,6 +7,7 @@ SYNOPSIS [--async] [--cluster-ipv4-cidr-block=CLUSTER_IPV4_CIDR_BLOCK] [--cluster-named-range=CLUSTER_NAMED_RANGE] [--experimental-features=[FEATURE,...]] [--man-block=MAN_BLOCK] + [--man-blocks=[BLOCK,...]] [--master-ipv4-cidr-block=MASTER_IPV4_CIDR_BLOCK] [--network=NETWORK] [--services-ipv4-cidr-block=SERVICES_IPV4_CIDR_BLOCK] [--services-named-range=SERVICES_NAMED_RANGE] [--subnet=SUBNET] @@ -71,8 +72,16 @@ FLAGS Enable experimental features. It can only be enabled in ALPHA version. --man-block=MAN_BLOCK - Master Authorized Network. Allows access to the Kubernetes control - plane from this block. Defaults to '0.0.0.0/0' if flag is not provided. + (DEPRECATED) Master Authorized Network. Allows access to the Kubernetes + control plane from this block. Defaults to 0.0.0.0/0 if flag is not + provided. + + The --man-block option is deprecated; use --man-blocks instead. + + --man-blocks=[BLOCK,...] + Master Authorized Network. Allows users to specify multiple blocks to + access the Kubernetescontrol plane from this block. Defaults to + 0.0.0.0/0 if flag is not provided. --master-ipv4-cidr-block=MASTER_IPV4_CIDR_BLOCK The /28 network that the control plane will use. Defaults to diff --git a/gcloud/alpha/artifacts/apt/import b/gcloud/alpha/artifacts/apt/import index 52299db90..1cadefd1a 100644 --- a/gcloud/alpha/artifacts/apt/import +++ b/gcloud/alpha/artifacts/apt/import @@ -3,7 +3,7 @@ NAME an artifact repository SYNOPSIS - gcloud alpha artifacts apt import (REPOSITORY : --location=LOCATION) + gcloud alpha artifacts apt import [[REPOSITORY] --location=LOCATION] --gcs-source=[GCS_SOURCE,...] [--async] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -43,24 +43,24 @@ POSITIONAL ARGUMENTS the project attribute: ◆ provide the argument repository on the command line with a fully specified name; + ◆ set the property artifacts/repository with a fully specified name; ◆ provide the argument --project on the command line; ◆ set the property core/project. - This must be specified. - - REPOSITORY + [REPOSITORY] ID of the repository or fully qualified identifier for the repository. To set the repository attribute: - ▸ provide the argument repository on the command line. - - This positional must be specified if any of the other arguments in - this group are specified. + ▸ provide the argument repository on the command line; + ▸ set the property artifacts/repository. --location=LOCATION Location of the repository. To set the location attribute: ▸ provide the argument repository on the command line with a fully specified name; - ▸ provide the argument --location on the command line. + ▸ set the property artifacts/repository with a fully specified + name; + ▸ provide the argument --location on the command line; + ▸ set the property artifacts/location. REQUIRED FLAGS --gcs-source=[GCS_SOURCE,...] diff --git a/gcloud/alpha/artifacts/apt/upload b/gcloud/alpha/artifacts/apt/upload index 78f534a18..bf6f186a5 100644 --- a/gcloud/alpha/artifacts/apt/upload +++ b/gcloud/alpha/artifacts/apt/upload @@ -3,7 +3,7 @@ NAME repository SYNOPSIS - gcloud alpha artifacts apt upload (REPOSITORY : --location=LOCATION) + gcloud alpha artifacts apt upload [[REPOSITORY] --location=LOCATION] --source=SOURCE [--async] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -24,24 +24,24 @@ POSITIONAL ARGUMENTS the project attribute: ◆ provide the argument repository on the command line with a fully specified name; + ◆ set the property artifacts/repository with a fully specified name; ◆ provide the argument --project on the command line; ◆ set the property core/project. - This must be specified. - - REPOSITORY + [REPOSITORY] ID of the repository or fully qualified identifier for the repository. To set the repository attribute: - ▸ provide the argument repository on the command line. - - This positional must be specified if any of the other arguments in - this group are specified. + ▸ provide the argument repository on the command line; + ▸ set the property artifacts/repository. --location=LOCATION Location of the repository. To set the location attribute: ▸ provide the argument repository on the command line with a fully specified name; - ▸ provide the argument --location on the command line. + ▸ set the property artifacts/repository with a fully specified + name; + ▸ provide the argument --location on the command line; + ▸ set the property artifacts/location. REQUIRED FLAGS --source=SOURCE diff --git a/gcloud/alpha/artifacts/files/list b/gcloud/alpha/artifacts/files/list index 5be14b49a..a7affe92b 100644 --- a/gcloud/alpha/artifacts/files/list +++ b/gcloud/alpha/artifacts/files/list @@ -3,7 +3,7 @@ NAME SYNOPSIS gcloud alpha artifacts files list [--package=PACKAGE] [--tag=TAG] - [--version=VERSION] [--repository=REPOSITORY : --location=LOCATION] + [--version=VERSION] [--location=LOCATION --repository=REPOSITORY] [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [GCLOUD_WIDE_FLAG ...] @@ -65,22 +65,24 @@ FLAGS the project attribute: ◆ provide the argument --repository on the command line with a fully specified name; + ◆ set the property artifacts/repository with a fully specified name; ◆ provide the argument --project on the command line; ◆ set the property core/project. - --repository=REPOSITORY - ID of the repository or fully qualified identifier for the - repository. To set the repository attribute: - ▸ provide the argument --repository on the command line. - - This flag must be specified if any of the other arguments in this - group are specified. - --location=LOCATION Location of the repository. To set the location attribute: ▸ provide the argument --repository on the command line with a fully specified name; - ▸ provide the argument --location on the command line. + ▸ set the property artifacts/repository with a fully specified + name; + ▸ provide the argument --location on the command line; + ▸ set the property artifacts/location. + + --repository=REPOSITORY + ID of the repository or fully qualified identifier for the + repository. To set the repository attribute: + ▸ provide the argument --repository on the command line; + ▸ set the property artifacts/repository. LIST COMMAND FLAGS --filter=EXPRESSION diff --git a/gcloud/alpha/artifacts/print-settings/apt b/gcloud/alpha/artifacts/print-settings/apt index f0297e7a4..7e9fee40b 100644 --- a/gcloud/alpha/artifacts/print-settings/apt +++ b/gcloud/alpha/artifacts/print-settings/apt @@ -4,7 +4,7 @@ NAME SYNOPSIS gcloud alpha artifacts print-settings apt - [--repository=REPOSITORY : --location=LOCATION] [GCLOUD_WIDE_FLAG ...] + [--location=LOCATION --repository=REPOSITORY] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Print settings to add to the sources.list.d directory for @@ -29,22 +29,24 @@ FLAGS the project attribute: ◆ provide the argument --repository on the command line with a fully specified name; + ◆ set the property artifacts/repository with a fully specified name; ◆ provide the argument --project on the command line; ◆ set the property core/project. - --repository=REPOSITORY - ID of the repository or fully qualified identifier for the - repository. To set the repository attribute: - ▸ provide the argument --repository on the command line. - - This flag must be specified if any of the other arguments in this - group are specified. - --location=LOCATION Location of the repository. To set the location attribute: ▸ provide the argument --repository on the command line with a fully specified name; - ▸ provide the argument --location on the command line. + ▸ set the property artifacts/repository with a fully specified + name; + ▸ provide the argument --location on the command line; + ▸ set the property artifacts/location. + + --repository=REPOSITORY + ID of the repository or fully qualified identifier for the + repository. To set the repository attribute: + ▸ provide the argument --repository on the command line; + ▸ set the property artifacts/repository. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/alpha/artifacts/print-settings/gradle b/gcloud/alpha/artifacts/print-settings/gradle index 69bc50ec1..cfbcefe73 100644 --- a/gcloud/alpha/artifacts/print-settings/gradle +++ b/gcloud/alpha/artifacts/print-settings/gradle @@ -4,7 +4,7 @@ NAME SYNOPSIS gcloud alpha artifacts print-settings gradle [--json-key=JSON_KEY] - [--repository=REPOSITORY : --location=LOCATION] [GCLOUD_WIDE_FLAG ...] + [--location=LOCATION --repository=REPOSITORY] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Print a snippet to add a repository to the Gradle build.gradle @@ -39,22 +39,24 @@ FLAGS the project attribute: ◆ provide the argument --repository on the command line with a fully specified name; + ◆ set the property artifacts/repository with a fully specified name; ◆ provide the argument --project on the command line; ◆ set the property core/project. - --repository=REPOSITORY - ID of the repository or fully qualified identifier for the - repository. To set the repository attribute: - ▸ provide the argument --repository on the command line. - - This flag must be specified if any of the other arguments in this - group are specified. - --location=LOCATION Location of the repository. To set the location attribute: ▸ provide the argument --repository on the command line with a fully specified name; - ▸ provide the argument --location on the command line. + ▸ set the property artifacts/repository with a fully specified + name; + ▸ provide the argument --location on the command line; + ▸ set the property artifacts/location. + + --repository=REPOSITORY + ID of the repository or fully qualified identifier for the + repository. To set the repository attribute: + ▸ provide the argument --repository on the command line; + ▸ set the property artifacts/repository. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/alpha/artifacts/print-settings/mvn b/gcloud/alpha/artifacts/print-settings/mvn index ba19c199c..1f7cb4136 100644 --- a/gcloud/alpha/artifacts/print-settings/mvn +++ b/gcloud/alpha/artifacts/print-settings/mvn @@ -4,7 +4,7 @@ NAME SYNOPSIS gcloud alpha artifacts print-settings mvn [--json-key=JSON_KEY] - [--repository=REPOSITORY : --location=LOCATION] [GCLOUD_WIDE_FLAG ...] + [--location=LOCATION --repository=REPOSITORY] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Print a snippet to add a Maven repository to the pom.xml file. @@ -38,22 +38,24 @@ FLAGS the project attribute: ◆ provide the argument --repository on the command line with a fully specified name; + ◆ set the property artifacts/repository with a fully specified name; ◆ provide the argument --project on the command line; ◆ set the property core/project. - --repository=REPOSITORY - ID of the repository or fully qualified identifier for the - repository. To set the repository attribute: - ▸ provide the argument --repository on the command line. - - This flag must be specified if any of the other arguments in this - group are specified. - --location=LOCATION Location of the repository. To set the location attribute: ▸ provide the argument --repository on the command line with a fully specified name; - ▸ provide the argument --location on the command line. + ▸ set the property artifacts/repository with a fully specified + name; + ▸ provide the argument --location on the command line; + ▸ set the property artifacts/location. + + --repository=REPOSITORY + ID of the repository or fully qualified identifier for the + repository. To set the repository attribute: + ▸ provide the argument --repository on the command line; + ▸ set the property artifacts/repository. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/alpha/artifacts/print-settings/npm b/gcloud/alpha/artifacts/print-settings/npm index cacc80574..b3a422fd4 100644 --- a/gcloud/alpha/artifacts/print-settings/npm +++ b/gcloud/alpha/artifacts/print-settings/npm @@ -4,7 +4,7 @@ NAME SYNOPSIS gcloud alpha artifacts print-settings npm [--json-key=JSON_KEY] - [--scope=SCOPE] [--repository=REPOSITORY : --location=LOCATION] + [--scope=SCOPE] [--location=LOCATION --repository=REPOSITORY] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -49,22 +49,24 @@ FLAGS the project attribute: ◆ provide the argument --repository on the command line with a fully specified name; + ◆ set the property artifacts/repository with a fully specified name; ◆ provide the argument --project on the command line; ◆ set the property core/project. - --repository=REPOSITORY - ID of the repository or fully qualified identifier for the - repository. To set the repository attribute: - ▸ provide the argument --repository on the command line. - - This flag must be specified if any of the other arguments in this - group are specified. - --location=LOCATION Location of the repository. To set the location attribute: ▸ provide the argument --repository on the command line with a fully specified name; - ▸ provide the argument --location on the command line. + ▸ set the property artifacts/repository with a fully specified + name; + ▸ provide the argument --location on the command line; + ▸ set the property artifacts/location. + + --repository=REPOSITORY + ID of the repository or fully qualified identifier for the + repository. To set the repository attribute: + ▸ provide the argument --repository on the command line; + ▸ set the property artifacts/repository. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/alpha/artifacts/print-settings/python b/gcloud/alpha/artifacts/print-settings/python index a9423694e..b851ec030 100644 --- a/gcloud/alpha/artifacts/print-settings/python +++ b/gcloud/alpha/artifacts/print-settings/python @@ -4,7 +4,7 @@ NAME SYNOPSIS gcloud alpha artifacts print-settings python [--json-key=JSON_KEY] - [--repository=REPOSITORY : --location=LOCATION] [GCLOUD_WIDE_FLAG ...] + [--location=LOCATION --repository=REPOSITORY] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Print credential settings to add to the .pypirc and pip.conf files @@ -39,22 +39,24 @@ FLAGS the project attribute: ◆ provide the argument --repository on the command line with a fully specified name; + ◆ set the property artifacts/repository with a fully specified name; ◆ provide the argument --project on the command line; ◆ set the property core/project. - --repository=REPOSITORY - ID of the repository or fully qualified identifier for the - repository. To set the repository attribute: - ▸ provide the argument --repository on the command line. - - This flag must be specified if any of the other arguments in this - group are specified. - --location=LOCATION Location of the repository. To set the location attribute: ▸ provide the argument --repository on the command line with a fully specified name; - ▸ provide the argument --location on the command line. + ▸ set the property artifacts/repository with a fully specified + name; + ▸ provide the argument --location on the command line; + ▸ set the property artifacts/location. + + --repository=REPOSITORY + ID of the repository or fully qualified identifier for the + repository. To set the repository attribute: + ▸ provide the argument --repository on the command line; + ▸ set the property artifacts/repository. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/alpha/artifacts/print-settings/yum b/gcloud/alpha/artifacts/print-settings/yum index df20cdf58..bfdf84cd8 100644 --- a/gcloud/alpha/artifacts/print-settings/yum +++ b/gcloud/alpha/artifacts/print-settings/yum @@ -4,7 +4,7 @@ NAME SYNOPSIS gcloud alpha artifacts print-settings yum - [--repository=REPOSITORY : --location=LOCATION] [GCLOUD_WIDE_FLAG ...] + [--location=LOCATION --repository=REPOSITORY] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Print settings to add to the yum.repos.d directory for connecting @@ -29,22 +29,24 @@ FLAGS the project attribute: ◆ provide the argument --repository on the command line with a fully specified name; + ◆ set the property artifacts/repository with a fully specified name; ◆ provide the argument --project on the command line; ◆ set the property core/project. - --repository=REPOSITORY - ID of the repository or fully qualified identifier for the - repository. To set the repository attribute: - ▸ provide the argument --repository on the command line. - - This flag must be specified if any of the other arguments in this - group are specified. - --location=LOCATION Location of the repository. To set the location attribute: ▸ provide the argument --repository on the command line with a fully specified name; - ▸ provide the argument --location on the command line. + ▸ set the property artifacts/repository with a fully specified + name; + ▸ provide the argument --location on the command line; + ▸ set the property artifacts/location. + + --repository=REPOSITORY + ID of the repository or fully qualified identifier for the + repository. To set the repository attribute: + ▸ provide the argument --repository on the command line; + ▸ set the property artifacts/repository. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/alpha/artifacts/repositories/list b/gcloud/alpha/artifacts/repositories/list index 22469818c..e3ea34747 100644 --- a/gcloud/alpha/artifacts/repositories/list +++ b/gcloud/alpha/artifacts/repositories/list @@ -3,7 +3,7 @@ NAME specified project SYNOPSIS - gcloud alpha artifacts repositories list --location=LOCATION + gcloud alpha artifacts repositories list [--location=LOCATION] [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [GCLOUD_WIDE_FLAG ...] @@ -28,13 +28,15 @@ FLAGS set in other ways. To set the project attribute: ◆ provide the argument --location on the command line with a fully specified name; + ◆ set the property artifacts/location with a fully specified name; ◆ provide the argument --project on the command line; ◆ set the property core/project. --location=LOCATION ID of the location or fully qualified identifier for the location. To set the location attribute: - ▸ provide the argument --location on the command line. + ▸ provide the argument --location on the command line; + ▸ set the property artifacts/location. LIST COMMAND FLAGS --filter=EXPRESSION diff --git a/gcloud/alpha/artifacts/yum/import b/gcloud/alpha/artifacts/yum/import index 34f082c8e..7ee53375c 100644 --- a/gcloud/alpha/artifacts/yum/import +++ b/gcloud/alpha/artifacts/yum/import @@ -3,7 +3,7 @@ NAME artifact repository SYNOPSIS - gcloud alpha artifacts yum import (REPOSITORY : --location=LOCATION) + gcloud alpha artifacts yum import [[REPOSITORY] --location=LOCATION] --gcs-source=[GCS_SOURCE,...] [--async] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -43,24 +43,24 @@ POSITIONAL ARGUMENTS the project attribute: ◆ provide the argument repository on the command line with a fully specified name; + ◆ set the property artifacts/repository with a fully specified name; ◆ provide the argument --project on the command line; ◆ set the property core/project. - This must be specified. - - REPOSITORY + [REPOSITORY] ID of the repository or fully qualified identifier for the repository. To set the repository attribute: - ▸ provide the argument repository on the command line. - - This positional must be specified if any of the other arguments in - this group are specified. + ▸ provide the argument repository on the command line; + ▸ set the property artifacts/repository. --location=LOCATION Location of the repository. To set the location attribute: ▸ provide the argument repository on the command line with a fully specified name; - ▸ provide the argument --location on the command line. + ▸ set the property artifacts/repository with a fully specified + name; + ▸ provide the argument --location on the command line; + ▸ set the property artifacts/location. REQUIRED FLAGS --gcs-source=[GCS_SOURCE,...] diff --git a/gcloud/alpha/artifacts/yum/upload b/gcloud/alpha/artifacts/yum/upload index 1415422b8..cef896b1e 100644 --- a/gcloud/alpha/artifacts/yum/upload +++ b/gcloud/alpha/artifacts/yum/upload @@ -3,7 +3,7 @@ NAME repository SYNOPSIS - gcloud alpha artifacts yum upload (REPOSITORY : --location=LOCATION) + gcloud alpha artifacts yum upload [[REPOSITORY] --location=LOCATION] --source=SOURCE [--async] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -24,24 +24,24 @@ POSITIONAL ARGUMENTS the project attribute: ◆ provide the argument repository on the command line with a fully specified name; + ◆ set the property artifacts/repository with a fully specified name; ◆ provide the argument --project on the command line; ◆ set the property core/project. - This must be specified. - - REPOSITORY + [REPOSITORY] ID of the repository or fully qualified identifier for the repository. To set the repository attribute: - ▸ provide the argument repository on the command line. - - This positional must be specified if any of the other arguments in - this group are specified. + ▸ provide the argument repository on the command line; + ▸ set the property artifacts/repository. --location=LOCATION Location of the repository. To set the location attribute: ▸ provide the argument repository on the command line with a fully specified name; - ▸ provide the argument --location on the command line. + ▸ set the property artifacts/repository with a fully specified + name; + ▸ provide the argument --location on the command line; + ▸ set the property artifacts/location. REQUIRED FLAGS --source=SOURCE diff --git a/gcloud/alpha/asset/analyze-org-policies b/gcloud/alpha/asset/analyze-org-policies index 3eea0d7b9..9be268212 100644 --- a/gcloud/alpha/asset/analyze-org-policies +++ b/gcloud/alpha/asset/analyze-org-policies @@ -29,16 +29,13 @@ REQUIRED FLAGS for a user-defined custom constraint. --scope=SCOPE - Scope can be a project, a folder, or an organization. The analysis is - limited to the Cloud org policies within this scope. The caller must be - granted the cloudasset.assets.searchAllResources permission on the - desired scope. + Scope can only be an organization for now. The analysis is limited to + the Cloud org policies within this scope. The caller must be granted + the cloudasset.assets.searchAllResources permission on the desired + scope. The allowed values are: - ◆ projects/{PROJECT_ID} (e.g., projects/foo-bar) - ◆ projects/{PROJECT_NUMBER} (e.g., projects/12345678) - ◆ folders/{FOLDER_NUMBER} (e.g., folders/1234567) ◆ organizations/{ORGANIZATION_NUMBER} (e.g. organizations/123456) LIST COMMAND FLAGS diff --git a/gcloud/alpha/asset/analyze-org-policy-governed-containers b/gcloud/alpha/asset/analyze-org-policy-governed-containers index 7d888998d..49f6f79a6 100644 --- a/gcloud/alpha/asset/analyze-org-policy-governed-containers +++ b/gcloud/alpha/asset/analyze-org-policy-governed-containers @@ -30,16 +30,13 @@ REQUIRED FLAGS for a user-defined custom constraint. --scope=SCOPE - Scope can be a project, a folder, or an organization. The analysis is - limited to the Cloud org policies and containers within this scope. The - caller must be granted the cloudasset.assets.searchAllResources - permission on the desired scope. + Scope can only be an organization for now. The analysis is limited to + the Cloud org policies and containers within this scope. The caller + must be granted the cloudasset.assets.searchAllResources permission on + the desired scope. The allowed values are: - ◆ projects/{PROJECT_ID} (e.g., projects/foo-bar) - ◆ projects/{PROJECT_NUMBER} (e.g., projects/12345678) - ◆ folders/{FOLDER_NUMBER} (e.g., folders/1234567) ◆ organizations/{ORGANIZATION_NUMBER} (e.g. organizations/123456) LIST COMMAND FLAGS diff --git a/gcloud/alpha/asset/analyze-org-policy-governed-resources b/gcloud/alpha/asset/analyze-org-policy-governed-resources index a76437bc9..cf6aad3c7 100644 --- a/gcloud/alpha/asset/analyze-org-policy-governed-resources +++ b/gcloud/alpha/asset/analyze-org-policy-governed-resources @@ -30,16 +30,13 @@ REQUIRED FLAGS for a user-defined custom constraint. --scope=SCOPE - Scope can be a project, a folder, or an organization. The analysis is - limited to the Cloud org policies and resources within this scope. The - caller must be granted the cloudasset.assets.searchAllResources - permission on the desired scope. + Scope can only be an organization for now. The analysis is limited to + the Cloud org policies and resources within this scope. The caller must + be granted the cloudasset.assets.searchAllResources permission on the + desired scope. The allowed values are: - ◆ projects/{PROJECT_ID} (e.g., projects/foo-bar) - ◆ projects/{PROJECT_NUMBER} (e.g., projects/12345678) - ◆ folders/{FOLDER_NUMBER} (e.g., folders/1234567) ◆ organizations/{ORGANIZATION_NUMBER} (e.g. organizations/123456) LIST COMMAND FLAGS diff --git a/gcloud/alpha/auth/application-default/login b/gcloud/alpha/auth/application-default/login index 6ae9f3446..d4dcb8b5e 100644 --- a/gcloud/alpha/auth/application-default/login +++ b/gcloud/alpha/auth/application-default/login @@ -45,21 +45,24 @@ EXAMPLES FLAGS --no-browser - Use this flag to authenticate the client libraries on a machine without - a web browser. + If you want to authorize the client libraries on a machine that doesn't + have a browser and you can install the gcloud CLI on another machine + with a browser, use the --no-browser flag. - Run gcloud auth login --no-browser and follow these steps: + 1. To initiate authorization, enter the following command: - 1. Copy the long command that begins with "gcloud auth login - --remote-bootstrap=". + gcloud auth application-default login --no-browser - 2. Paste and run this command on the command line of a different, + 2. Copy the long command that begins with gcloud auth + application-default login --remote-bootstrap=". + + 3. Paste and run this command on the command line of a different, trusted machine that has local installations of both a web browser and the gcloud CLI tool version 372.0 or later. - 3. Copy the long URL output from the machine with the web browser. + 4. Copy the long URL output from the machine with the web browser. - 4. Paste the long URL back to the first machine under the prompt, + 5. Paste the long URL back to the first machine under the prompt, "Enter the output of the above command", and press Enter to complete the authorization. @@ -94,7 +97,31 @@ FLAGS --launch-browser Launch a browser for authorization. If not enabled or if it is not possible to launch a browser, prints a URL to standard output to be - copied. Enabled by default, use --no-launch-browser to disable. + copied. + + If you want to authorize the client libraries on a machine that doesn't + have a browser and you cannot install the gcloud CLI on another machine + with a browser, use the --no-launch-browser flag. The + --no-launch-browser flag prevents the command from automatically + opening a web browser. + + 1. To initiate authorization, enter the following command: + + gcloud auth application-default login --no-launch-browser + + 2. Copy the long URL that begins with + https://accounts.google.com/o/oauth2/auth... + + 3. Paste this URL into the browser of a different, trusted machine that + has a web browser. + + 4. Copy the authorization code from the machine with the web browser. + + 5. Paste the authorization code back to the first machine at the + prompt, "Enter authorization code", and press Enter to complete the + authorization. + + Enabled by default, use --no-launch-browser to disable. --scopes=SCOPE,[SCOPE,...] The names of the scopes to authorize for. By default openid, diff --git a/gcloud/alpha/auth/login b/gcloud/alpha/auth/login index 68c3d7616..75edb4202 100644 --- a/gcloud/alpha/auth/login +++ b/gcloud/alpha/auth/login @@ -61,21 +61,24 @@ FLAGS Minimal user output. --no-browser - Use this flag to authenticate the gcloud CLI on a machine without a web - browser. + If you want to authorize the gcloud CLI on a machine that doesn't have + a browser and you can install the gcloud CLI on another machine with a + browser, use the --no-browser flag. - Run gcloud auth login --no-browser and follow these steps: + 1. To initiate authorization, enter the following command: - 1. Copy the long command that begins with "gcloud auth login + gcloud auth login --no-browser + + 2. Copy the long command that begins with gcloud auth login --remote-bootstrap=". - 2. Paste and run this command on the command line of a different, + 3. Paste and run this command on the command line of a different, trusted machine that has local installations of both a web browser and the gcloud CLI tool version 372.0 or later. - 3. Copy the long URL output from the machine with the web browser. + 4. Copy the long URL output from the machine with the web browser. - 4. Paste the long URL back to the first machine under the prompt, + 5. Paste the long URL back to the first machine under the prompt, "Enter the output of the above command", and press Enter to complete the authorization. @@ -95,7 +98,30 @@ FLAGS --launch-browser Launch a browser for authorization. If not enabled or if it is not possible to launch a browser, prints a URL to standard output to be - copied. Enabled by default, use --no-launch-browser to disable. + copied. + + If you want to authorize the gcloud CLI on a machine that doesn't have + a browser and you cannot install the gcloud CLI on another machine with + a browser, use the --no-launch-browser flag. The --no-launch-browser + flag prevents the command from automatically opening a web browser. + + 1. To initiate authorization, enter the following command: + + gcloud auth login --no-launch-browser + + 2. Copy the long URL that begins with + https://accounts.google.com/o/oauth2/auth... + + 3. Paste this URL into the browser of a different, trusted machine that + has a web browser. + + 4. Copy the authorization code from the machine with the web browser. + + 5. Paste the authorization code back to the first machine at the + prompt, "Enter authorization code", and press Enter to complete the + authorization. + + Enabled by default, use --no-launch-browser to disable. --update-adc Write the obtained credentials to the well-known location for diff --git a/gcloud/alpha/beyondcorp/app/connections/create b/gcloud/alpha/beyondcorp/app/connections/create new file mode 100644 index 000000000..f1a9c5b93 --- /dev/null +++ b/gcloud/alpha/beyondcorp/app/connections/create @@ -0,0 +1,129 @@ +NAME + gcloud alpha beyondcorp app connections create - create a new Beyondcorp + application connection + +SYNOPSIS + gcloud alpha beyondcorp app connections create + (CONNECTION : --location=LOCATION) + (--application-endpoint=APPLICATION_ENDPOINT + | --application-endpoint-host=APPLICATION_ENDPOINT_HOST + --application-endpoint-port=APPLICATION_ENDPOINT_PORT) [--async] + [--connectors=[CONNECTORS,...]] [--display-name=DISPLAY_NAME] + [--labels=[KEY=VALUE,...]] [--type=TYPE; default="TCP_PROXY"] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Create a new Beyondcorp application connection. + +EXAMPLES + The following command creates a Connection with ID my-connection using + default tcp type connection: + + $ gcloud alpha beyondcorp app connections create my-connection \ + --location=us-central1 --application-endpoint=localhost:8080 + + The following command creates a Connection with ID my-connection with + explicit project value for all required and optional parameters: + + $ gcloud alpha beyondcorp app connections create my-connection \ + --project=projectId --location=us-central1 \ + --application-endpoint-host=localhost \ + --application-endpoint-port=8080 --type=tcp \ + --connectors=my-connector1,my-connector2 --labels='foo=bar' \ + --display-name=connection-display-name --async + +POSITIONAL ARGUMENTS + Connection resource - The Beyondcorp application connection 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 connection on the command line with a fully + specified name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + This must be specified. + + CONNECTION + ID of the connection or fully qualified identifier for the + connection. To set the app_connection attribute: + ▸ provide the argument connection on the command line. + + This positional must be specified if any of the other arguments in + this group are specified. + + --location=LOCATION + The location of the beyondcorp service. + + To set the location attribute: + ▸ provide the argument connection on the command line with a fully + specified name; + ▸ provide the argument --location on the command line. + +REQUIRED FLAGS + Application endpoint. + + Exactly one of these must be specified: + + --application-endpoint=APPLICATION_ENDPOINT + Address of the remote application endpoint for the Beyondcorp + Connection in form of :. + + --application-endpoint-host=APPLICATION_ENDPOINT_HOST + Hostname or IP address of the remote application endpoint. + + This flag must be specified if any of the other arguments in this + group are specified. + + --application-endpoint-port=APPLICATION_ENDPOINT_PORT + Port of the remote application endpoint. + + This flag must be specified if any of the other arguments in this + group are specified. + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --connectors=[CONNECTORS,...] + List of connectors names that are authorised to be associated with this + Connection. + + --display-name=DISPLAY_NAME + An arbitrary user-provided name for the connection. Cannot exceed 64 + characters. + + --labels=[KEY=VALUE,...] + List of label KEY=VALUE pairs to add. + + Keys must start with a lowercase character and contain only hyphens + (-), underscores (_), lowercase characters, and numbers. Values must + contain only hyphens (-), underscores (_), lowercase characters, and + numbers. + + --type=TYPE; default="TCP_PROXY" + The type of network connnectivity used by the connection. TYPE must be + (currently only one value is supported): + + tcp + TCP connection + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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 beyondcorp/v1alpha API. The full documentation for + this API can be found at: https://cloud.google.com/ + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/beyondcorp/app/connections/delete b/gcloud/alpha/beyondcorp/app/connections/delete new file mode 100644 index 000000000..3bff330a5 --- /dev/null +++ b/gcloud/alpha/beyondcorp/app/connections/delete @@ -0,0 +1,67 @@ +NAME + gcloud alpha beyondcorp app connections delete - delete a single Connection + +SYNOPSIS + gcloud alpha beyondcorp app connections delete + (CONNECTION : --location=LOCATION) [--async] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Delete a single Connection. + +EXAMPLES + To delete a connection named my-connection run: + + $ gcloud alpha beyondcorp app connections delete my-connection \ + --project={project} --location={location} + +POSITIONAL ARGUMENTS + Connection resource - The Beyondcorp connection 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 connection on the command line with a fully + specified name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + This must be specified. + + CONNECTION + ID of the connection or fully qualified identifier for the + connection. To set the app_connection attribute: + ▸ provide the argument connection on the command line. + + This positional must be specified if any of the other arguments in + this group are specified. + + --location=LOCATION + The location of the beyondcorp service. + + To set the location attribute: + ▸ provide the argument connection on the command line with a fully + specified name; + ▸ provide the argument --location on the command line. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the beyondcorp/v1alpha API. The full documentation for + this API can be found at: https://cloud.google.com/ + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/beyondcorp/app/connections/describe b/gcloud/alpha/beyondcorp/app/connections/describe new file mode 100644 index 000000000..9a889c9c0 --- /dev/null +++ b/gcloud/alpha/beyondcorp/app/connections/describe @@ -0,0 +1,72 @@ +NAME + gcloud alpha beyondcorp app connections describe - describe a single + Connection + +SYNOPSIS + gcloud alpha beyondcorp app connections describe + (CONNECTION : --location=LOCATION) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Describe a single Connection. + +EXAMPLES + To describe a connection my-connection run: + + $ gcloud alpha beyondcorp app connections describe my-connection \ + --project={project} --location=us-central1 + + To describe a connection my-connection in a project for location + us-central1 in table form, run: + + $ gcloud alpha beyondcorp app connections describe my-connection \ + --project={project} --location=us-central1 \ + --format=table(displayName, name.basename(), state, \ + applicationEndpoint.host, applicationEndpoint.port, \ + updateTime, labels) + +POSITIONAL ARGUMENTS + Connection resource - The Beyondcorp connector you want to get details + about. 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 connection on the command line with a fully + specified name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + This must be specified. + + CONNECTION + ID of the connection or fully qualified identifier for the + connection. To set the app_connection attribute: + ▸ provide the argument connection on the command line. + + This positional must be specified if any of the other arguments in + this group are specified. + + --location=LOCATION + The location of the beyondcorp service. + + To set the location attribute: + ▸ provide the argument connection on the command line with a fully + specified name; + ▸ provide the argument --location on the command line. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the beyondcorp/v1alpha API. The full documentation for + this API can be found at: https://cloud.google.com/ + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/beyondcorp/app/connections/help b/gcloud/alpha/beyondcorp/app/connections/help new file mode 100644 index 000000000..b41723bcb --- /dev/null +++ b/gcloud/alpha/beyondcorp/app/connections/help @@ -0,0 +1,42 @@ +NAME + gcloud alpha beyondcorp app connections - create and manipulate beyondcorp + connections + +SYNOPSIS + gcloud alpha beyondcorp app connections COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) A Beyondcorp Connection resource represents a BeyondCorp protected + connection to a remote application. It creates all the necessary Google + Cloud Platform components needed for creating a BeyondCorp protected + connection. Multiple connectors can be authorised for a single Connection. + +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 Beyondcorp application connection. + + delete + (ALPHA) Delete a single Connection. + + describe + (ALPHA) Describe a single Connection. + + list + (ALPHA) List Beyondcorp connection Resources. + + update + (ALPHA) Update an existing Beyondcorp application connection. + +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/beyondcorp/app/connections/list b/gcloud/alpha/beyondcorp/app/connections/list new file mode 100644 index 000000000..61d8dda94 --- /dev/null +++ b/gcloud/alpha/beyondcorp/app/connections/list @@ -0,0 +1,88 @@ +NAME + gcloud alpha beyondcorp app connections list - list Beyondcorp connection + Resources + +SYNOPSIS + gcloud alpha beyondcorp app connections list --location=LOCATION + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) List Beyondcorp connection resources based on project and location. + +EXAMPLES + To list all connections in a project for location us-central1 in table + form, run: + + $ gcloud alpha beyondcorp app connections list --project=projectId \ + --location=us-central1 + + To list all connections in a project for location us-central1 in json form, + run: + + $ gcloud alpha beyondcorp app connections list --project=projectId \ + --location=us-central1 --format=json(displayName, \ + name.basename(), state, applicationEndpoint.host, \ + applicationEndpoint.port, updateTime, labels) + +REQUIRED FLAGS + Location resource - Arguments and flags that define the Beyondcorp + connector you want to list. This represents a Cloud resource. (NOTE) Some + attributes are not given arguments in this group but can be set in other + ways. To set the project attribute: + ◆ provide the argument --location on the command line with a fully + specified name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + This must be specified. + + --location=LOCATION + ID of the location or fully qualified identifier for the location. To + set the location attribute: + ▸ provide the argument --location on the command line. + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the beyondcorp/v1alpha API. The full documentation for + this API can be found at: https://cloud.google.com/ + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/beyondcorp/app/connections/update b/gcloud/alpha/beyondcorp/app/connections/update new file mode 100644 index 000000000..2e71aa78e --- /dev/null +++ b/gcloud/alpha/beyondcorp/app/connections/update @@ -0,0 +1,117 @@ +NAME + gcloud alpha beyondcorp app connections update - update an existing + Beyondcorp application connection + +SYNOPSIS + gcloud alpha beyondcorp app connections update + (CONNECTION : --location=LOCATION) + [--application-endpoint=APPLICATION_ENDPOINT] [--async] + [--connectors=[CONNECTORS,...]] [--display-name=DISPLAY_NAME] + [--update-labels=[KEY=VALUE,...]] + [--clear-labels | --remove-labels=[KEY,...]] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Update an existing Beyondcorp application connection. + +EXAMPLES + To modify the connection my-connection in 'us-central1' by adding labels + 'k0', with value 'value1' and label 'k1' with value 'value2' and removing + labels with key 'k3', run: + + $ gcloud alpha beyondcorp app connections update my-connection \ + --location=us-central1 --display-name=new-display-name \ + --connectors={connector1} --application-endpoint=host:port \ + --update-labels=k0=value1,k1=value2 --remove-labels=k3 + +POSITIONAL ARGUMENTS + Connection resource - The Beyondcorp connection 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 connection on the command line with a fully + specified name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + This must be specified. + + CONNECTION + ID of the connection or fully qualified identifier for the + connection. To set the app_connection attribute: + ▸ provide the argument connection on the command line. + + This positional must be specified if any of the other arguments in + this group are specified. + + --location=LOCATION + The location of the beyondcorp service. + + To set the location attribute: + ▸ provide the argument connection on the command line with a fully + specified name; + ▸ provide the argument --location on the command line. + +FLAGS + --application-endpoint=APPLICATION_ENDPOINT + Address of the remote application endpoint for the Beyondcorp + Connection in form of :. + + --async + Return immediately, without waiting for the operation in progress to + complete. + + --connectors=[CONNECTORS,...] + List of connectors names that are authorised to be associated with this + Connection. + + --display-name=DISPLAY_NAME + An arbitrary user-provided name for the connection. Cannot exceed 64 + characters. + + --update-labels=[KEY=VALUE,...] + List of label KEY=VALUE pairs to update. If a label exists, its value + is modified. Otherwise, a new label is created. + + Keys must start with a lowercase character and contain only hyphens + (-), underscores (_), lowercase characters, and numbers. Values must + contain only hyphens (-), underscores (_), lowercase characters, and + numbers. + + At most one of these can be specified: + + --clear-labels + Remove all labels. If --update-labels is also specified then + --clear-labels is applied first. + + For example, to remove all labels: + + $ gcloud alpha beyondcorp app connections update --clear-labels + + To remove all existing labels and create two new labels, foo and baz: + + $ gcloud alpha beyondcorp app connections update --clear-labels \ + --update-labels foo=bar,baz=qux + + --remove-labels=[KEY,...] + List of label keys to remove. If a label does not exist it is + silently ignored. If --update-labels is also specified then + --update-labels is applied first. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the beyondcorp/v1alpha API. The full documentation for + this API can be found at: https://cloud.google.com/ + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/beyondcorp/app/connectors/create b/gcloud/alpha/beyondcorp/app/connectors/create new file mode 100644 index 000000000..551dd000f --- /dev/null +++ b/gcloud/alpha/beyondcorp/app/connectors/create @@ -0,0 +1,98 @@ +NAME + gcloud alpha beyondcorp app connectors create - create a new Beyondcorp + application connector + +SYNOPSIS + gcloud alpha beyondcorp app connectors create + (CONNECTOR : --location=LOCATION) --member=MEMBER [--async] + [--display-name=DISPLAY_NAME] [--labels=[KEY=VALUE,...]] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Create a new Beyondcorp application connector. + +EXAMPLES + The following command creates a Connector with ID my-connector in the + default user project: + + $ gcloud alpha beyondcorp app connectors create my-connector \ + --location=us-central1 \ + --member=serviceAccount:connector-sa@projectId.iam.gserviceaccou\ + nt.com + + The following command creates a Connector with ID my-connector with + explicit project value for all required and optional parameters: + + $ gcloud alpha beyondcorp app connectors create my-connector \ + --project=projectId --location=us-central1 \ + --member=serviceAccount:connector-sa@projectId.iam.gserviceaccou\ + nt.com --labels='foo=bar' --display-name=connector-display-name \ + --async + +POSITIONAL ARGUMENTS + Connector resource - The Beyondcorp connector 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 connector on the command line with a fully + specified name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + This must be specified. + + CONNECTOR + ID of the connector or fully qualified identifier for the connector. + To set the app_connector attribute: + ▸ provide the argument connector on the command line. + + This positional must be specified if any of the other arguments in + this group are specified. + + --location=LOCATION + The location of the beyondcorp service. + + To set the location attribute: + ▸ provide the argument connector on the command line with a fully + specified name; + ▸ provide the argument --location on the command line. + +REQUIRED FLAGS + --member=MEMBER + Connector service account email in form of 'serviceAccount:email'. + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --display-name=DISPLAY_NAME + An arbitrary user-provided name for the connector. Cannot exceed 64 + characters. + + --labels=[KEY=VALUE,...] + List of label KEY=VALUE pairs to add. + + Keys must start with a lowercase character and contain only hyphens + (-), underscores (_), lowercase characters, and numbers. Values must + contain only hyphens (-), underscores (_), lowercase characters, and + numbers. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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 beyondcorp/v1alpha API. The full documentation for + this API can be found at: https://cloud.google.com/ + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/beyondcorp/app/connectors/delete b/gcloud/alpha/beyondcorp/app/connectors/delete new file mode 100644 index 000000000..c9d6884b5 --- /dev/null +++ b/gcloud/alpha/beyondcorp/app/connectors/delete @@ -0,0 +1,67 @@ +NAME + gcloud alpha beyondcorp app connectors delete - delete a single Connector + +SYNOPSIS + gcloud alpha beyondcorp app connectors delete + (CONNECTOR : --location=LOCATION) [--async] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Delete a single Connector. + +EXAMPLES + To delete a connector my-connector run: + + $ gcloud alpha beyondcorp app connectors delete my-connector \ + --project={project} --location={location} + +POSITIONAL ARGUMENTS + Connector resource - The Beyondcorp connector 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 connector on the command line with a fully + specified name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + This must be specified. + + CONNECTOR + ID of the connector or fully qualified identifier for the connector. + To set the app_connector attribute: + ▸ provide the argument connector on the command line. + + This positional must be specified if any of the other arguments in + this group are specified. + + --location=LOCATION + The location of the beyondcorp service. + + To set the location attribute: + ▸ provide the argument connector on the command line with a fully + specified name; + ▸ provide the argument --location on the command line. + +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 beyondcorp/v1alpha API. The full documentation for + this API can be found at: https://cloud.google.com/ + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/beyondcorp/app/connectors/describe b/gcloud/alpha/beyondcorp/app/connectors/describe new file mode 100644 index 000000000..80fbb6f38 --- /dev/null +++ b/gcloud/alpha/beyondcorp/app/connectors/describe @@ -0,0 +1,75 @@ +NAME + gcloud alpha beyondcorp app connectors describe - describe a single + Connector + +SYNOPSIS + gcloud alpha beyondcorp app connectors describe + (CONNECTOR : --location=LOCATION) [--details] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Describe a single Connector. + +EXAMPLES + To describe a connector my-connector run: + + $ gcloud alpha beyondcorp app connectors describe my-connector \ + --project={project} --location={location} + + To describe a connector in a project for location us-central1 in table + form, run: + + $ gcloud alpha beyondcorp app connectors describe \ + --project=projectId --location=us-central1 \ + --format=table(displayName, name, state, \ + principalInfo.serviceAccount.email,createTime,updateTime,labels) + +POSITIONAL ARGUMENTS + Connector resource - The Beyondcorp connector you want to get details + about. The arguments in this group can be used to specify the attributes + of this resource. (NOTE) Some attributes are not given arguments in this + group but can be set in other ways. To set the project attribute: + ◆ provide the argument connector on the command line with a fully + specified name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + This must be specified. + + CONNECTOR + ID of the connector or fully qualified identifier for the connector. + To set the app_connector attribute: + ▸ provide the argument connector on the command line. + + This positional must be specified if any of the other arguments in + this group are specified. + + --location=LOCATION + The location of the beyondcorp service. + + To set the location attribute: + ▸ provide the argument connector on the command line with a fully + specified name; + ▸ provide the argument --location on the command line. + +FLAGS + --details + Includes details. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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 beyondcorp/v1alpha API. The full documentation for + this API can be found at: https://cloud.google.com/ + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/beyondcorp/app/connectors/help b/gcloud/alpha/beyondcorp/app/connectors/help new file mode 100644 index 000000000..bbe94b224 --- /dev/null +++ b/gcloud/alpha/beyondcorp/app/connectors/help @@ -0,0 +1,43 @@ +NAME + gcloud alpha beyondcorp app connectors - create and manipulate beyondcorp + connectors + +SYNOPSIS + gcloud alpha beyondcorp app connectors COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) A Beyondcorp connector represents an application facing component + deployed proximal to and with direct access to the application instances. + It is used to establish connectivity between the remote enterprise + environment and Google Cloud Platform. It initiates connections to the + applications and can proxy the data from users over the connection. + +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 Beyondcorp application connector. + + delete + (ALPHA) Delete a single Connector. + + describe + (ALPHA) Describe a single Connector. + + list + (ALPHA) List Beyondcorp connector Resources. + + update + (ALPHA) Update an existing Beyondcorp application connector. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/vmware/node-types/list b/gcloud/alpha/beyondcorp/app/connectors/list similarity index 65% rename from gcloud/alpha/vmware/node-types/list rename to gcloud/alpha/beyondcorp/app/connectors/list index 4727bc057..bbb909198 100644 --- a/gcloud/alpha/vmware/node-types/list +++ b/gcloud/alpha/beyondcorp/app/connectors/list @@ -1,43 +1,45 @@ NAME - gcloud alpha vmware node-types list - list supported Google Cloud VMware - Engine node types + gcloud alpha beyondcorp app connectors list - list Beyondcorp connector + Resources SYNOPSIS - gcloud alpha vmware node-types list [--location=LOCATION] + gcloud alpha beyondcorp app connectors list --location=LOCATION [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] - [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + [--sort-by=[FIELD,...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) List VMware Engine node types. + (ALPHA) List Beyondcorp connector resources based on project and location. EXAMPLES - To list VMware Engine node types, run: + To list all connectors in a project for location us-central1 in table form, + run: - $ gcloud alpha vmware node-types list --location=us-central1 \ - --project=my-project + $ gcloud alpha beyondcorp app connectors list --project=projectId \ + --location=us-central1 - Or: + To list all connectors in a project for location us-central1 in json form, + run: - $ gcloud alpha vmware node-types list + $ gcloud alpha beyondcorp app connectors list --project=projectId \ + --location=us-central1 --format=json(displayName, name, state, \ + principalInfo.serviceAccount.email,createTime,updateTime,labels) - In the second example, the project and location are taken from gcloud - properties core/project and compute/zone. - -FLAGS - Location resource - location. 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: +REQUIRED FLAGS + Location resource - Arguments and flags that define the Beyondcorp + connector you want to list. This represents a Cloud resource. (NOTE) Some + attributes are not given arguments in this group but can be set in other + ways. To set the project attribute: ◆ provide the argument --location on the command line with a fully specified name; - ◆ set the property compute/zone with a fully specified name; ◆ set the property core/project; ◆ provide the argument --project on the command line. + This must be specified. + --location=LOCATION ID of the location or fully qualified identifier for the location. To set the location attribute: - ▸ provide the argument --location on the command line; - ▸ set the property compute/zone. + ▸ provide the argument --location on the command line. LIST COMMAND FLAGS --filter=EXPRESSION @@ -65,12 +67,6 @@ LIST COMMAND FLAGS order on that field. This flag interacts with other flags that are applied in this order: --flatten, --sort-by, --filter, --limit. - --uri - Print a list of resource URIs instead of the default output, and change - the command output to a list of URIs. If this flag is used with - --format, the formatting is applied on this URI list. To display URIs - alongside other keys instead, use the uri() transform. - GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, @@ -79,6 +75,10 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. +API REFERENCE + This command uses the beyondcorp/v1alpha API. The full documentation for + this API can be found at: https://cloud.google.com/ + NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct diff --git a/gcloud/alpha/beyondcorp/app/connectors/update b/gcloud/alpha/beyondcorp/app/connectors/update new file mode 100644 index 000000000..05aea6ccf --- /dev/null +++ b/gcloud/alpha/beyondcorp/app/connectors/update @@ -0,0 +1,106 @@ +NAME + gcloud alpha beyondcorp app connectors update - update an existing + Beyondcorp application connector + +SYNOPSIS + gcloud alpha beyondcorp app connectors update + (CONNECTOR : --location=LOCATION) [--async] + [--display-name=DISPLAY_NAME] [--update-labels=[KEY=VALUE,...]] + [--clear-labels | --remove-labels=[KEY,...]] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Update an existing Beyondcorp application connector. + +EXAMPLES + To modify the connector my-connector in 'us-central1' by adding labels + 'k0', with value 'value1' and label 'k1' with value 'value2' and removing + labels with key 'k3', run: + + $ gcloud alpha beyondcorp app connectors update my-connector \ + --location=us-central1 --display-name=new-display-name \ + --update-labels=k0=value1,k1=value2 --remove-labels=k3 + +POSITIONAL ARGUMENTS + Connector resource - The Beyondcorp connector 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 connector on the command line with a fully + specified name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + This must be specified. + + CONNECTOR + ID of the connector or fully qualified identifier for the connector. + To set the app_connector attribute: + ▸ provide the argument connector on the command line. + + This positional must be specified if any of the other arguments in + this group are specified. + + --location=LOCATION + The location of the beyondcorp service. + + To set the location attribute: + ▸ provide the argument connector on the command line with a fully + specified name; + ▸ provide the argument --location on the command line. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --display-name=DISPLAY_NAME + An arbitrary user-provided name for the connector. Cannot exceed 64 + characters. + + --update-labels=[KEY=VALUE,...] + List of label KEY=VALUE pairs to update. If a label exists, its value + is modified. Otherwise, a new label is created. + + Keys must start with a lowercase character and contain only hyphens + (-), underscores (_), lowercase characters, and numbers. Values must + contain only hyphens (-), underscores (_), lowercase characters, and + numbers. + + At most one of these can be specified: + + --clear-labels + Remove all labels. If --update-labels is also specified then + --clear-labels is applied first. + + For example, to remove all labels: + + $ gcloud alpha beyondcorp app connectors update --clear-labels + + To remove all existing labels and create two new labels, foo and baz: + + $ gcloud alpha beyondcorp app connectors update --clear-labels \ + --update-labels foo=bar,baz=qux + + --remove-labels=[KEY,...] + List of label keys to remove. If a label does not exist it is + silently ignored. If --update-labels is also specified then + --update-labels is applied first. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the beyondcorp/v1alpha API. The full documentation for + this API can be found at: https://cloud.google.com/ + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/beyondcorp/app/help b/gcloud/alpha/beyondcorp/app/help new file mode 100644 index 000000000..75cb6b542 --- /dev/null +++ b/gcloud/alpha/beyondcorp/app/help @@ -0,0 +1,47 @@ +NAME + gcloud alpha beyondcorp app - manages application connectors and + connections + +SYNOPSIS + gcloud alpha beyondcorp app GROUP [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) The gcloud beyondcorp command group lets you secure non-gcp + application by managing connectors and connections. + + BeyondCorp Enterprise offers a zero trust solution that enables secure + access with integrated threat and data protection.The solution enables + secure access to both Google Cloud Platform and on-prem hosted apps. For + remote apps that are not deployed in Google Cloud Platform, BeyondCorp + Enterprise's App connector provides simplified connectivity and app + publishing experience. + + More information on Beyondcorp can be found here: + https://cloud.google.com/beyondcorp + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +GROUPS + GROUP is one of the following: + + connections + (ALPHA) Create and manipulate beyondcorp connections. + + connectors + (ALPHA) Create and manipulate beyondcorp connectors. + + legacy + (ALPHA) Manages application legacy connectors and connections. + + operations + (ALPHA) List and Describe beyondcorp appconnector operations. + +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/beyondcorp/app/legacy/connections/create b/gcloud/alpha/beyondcorp/app/legacy/connections/create new file mode 100644 index 000000000..95b9672cd --- /dev/null +++ b/gcloud/alpha/beyondcorp/app/legacy/connections/create @@ -0,0 +1,130 @@ +NAME + gcloud alpha beyondcorp app legacy connections create - create a new + Beyondcorp application legacy connection + +SYNOPSIS + gcloud alpha beyondcorp app legacy connections create + (CONNECTION : --location=LOCATION) + (--application-endpoint=APPLICATION_ENDPOINT + | --application-endpoint-host=APPLICATION_ENDPOINT_HOST + --application-endpoint-port=APPLICATION_ENDPOINT_PORT) [--async] + [--connectors=[CONNECTORS,...]] [--display-name=DISPLAY_NAME] + [--labels=[KEY=VALUE,...]] [--type=TYPE; default="TCP_PROXY"] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Create a new Beyondcorp application legacy connection. + +EXAMPLES + The following command creates a legacy Connection with ID my-connection + using default tcp type connection: + + $ gcloud alpha beyondcorp app legacy connections create \ + my-connection --location=us-central1 \ + --application-endpoint=localhost:8080 + + The following command creates a legacy Connection with ID my-connection + with explicit project value for all required and optional parameters: + + $ gcloud alpha beyondcorp app legacy connections create \ + my-connection --project=projectId --location=us-central1 \ + --application-endpoint-host=localhost \ + --application-endpoint-port=8080 --type=tcp \ + --connectors=my-connector1,my-connector2 --labels='foo=bar' \ + --display-name=connection-display-name --async + +POSITIONAL ARGUMENTS + Connection resource - The Beyondcorp application connection 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 connection on the command line with a fully + specified name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + This must be specified. + + CONNECTION + ID of the connection or fully qualified identifier for the + connection. To set the connection attribute: + ▸ provide the argument connection on the command line. + + This positional must be specified if any of the other arguments in + this group are specified. + + --location=LOCATION + The location of the beyondcorp service. + + To set the location attribute: + ▸ provide the argument connection on the command line with a fully + specified name; + ▸ provide the argument --location on the command line. + +REQUIRED FLAGS + Application endpoint. + + Exactly one of these must be specified: + + --application-endpoint=APPLICATION_ENDPOINT + Address of the remote application endpoint for the Beyondcorp + Connection in form of :. + + --application-endpoint-host=APPLICATION_ENDPOINT_HOST + Hostname or IP address of the remote application endpoint. + + This flag must be specified if any of the other arguments in this + group are specified. + + --application-endpoint-port=APPLICATION_ENDPOINT_PORT + Port of the remote application endpoint. + + This flag must be specified if any of the other arguments in this + group are specified. + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --connectors=[CONNECTORS,...] + List of connectors name that are authorised to be associated with this + Connection. + + --display-name=DISPLAY_NAME + An arbitrary user-provided name for the connection. Cannot exceed 64 + characters. + + --labels=[KEY=VALUE,...] + List of label KEY=VALUE pairs to add. + + Keys must start with a lowercase character and contain only hyphens + (-), underscores (_), lowercase characters, and numbers. Values must + contain only hyphens (-), underscores (_), lowercase characters, and + numbers. + + --type=TYPE; default="TCP_PROXY" + The type of network connnectivity used by the connection. TYPE must be + (currently only one value is supported): + + tcp + TCP connection + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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 beyondcorp/v1alpha API. The full documentation for + this API can be found at: https://cloud.google.com/ + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/beyondcorp/app/legacy/connections/delete b/gcloud/alpha/beyondcorp/app/legacy/connections/delete new file mode 100644 index 000000000..14a365a26 --- /dev/null +++ b/gcloud/alpha/beyondcorp/app/legacy/connections/delete @@ -0,0 +1,68 @@ +NAME + gcloud alpha beyondcorp app legacy connections delete - delete a single + legacy Connection + +SYNOPSIS + gcloud alpha beyondcorp app legacy connections delete + (CONNECTION : --location=LOCATION) [--async] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Delete a single legacy Connection. + +EXAMPLES + To delete a legacy connection named my-connection run: + + $ gcloud alpha beyondcorp app legacy connections delete \ + my-connection --project={project} --location={location} + +POSITIONAL ARGUMENTS + Connection resource - The Beyondcorp connection 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 connection on the command line with a fully + specified name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + This must be specified. + + CONNECTION + ID of the connection or fully qualified identifier for the + connection. To set the connection attribute: + ▸ provide the argument connection on the command line. + + This positional must be specified if any of the other arguments in + this group are specified. + + --location=LOCATION + The location of the beyondcorp service. + + To set the location attribute: + ▸ provide the argument connection on the command line with a fully + specified name; + ▸ provide the argument --location on the command line. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the beyondcorp/v1alpha API. The full documentation for + this API can be found at: https://cloud.google.com/ + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/beyondcorp/app/legacy/connections/describe b/gcloud/alpha/beyondcorp/app/legacy/connections/describe new file mode 100644 index 000000000..3893de27c --- /dev/null +++ b/gcloud/alpha/beyondcorp/app/legacy/connections/describe @@ -0,0 +1,72 @@ +NAME + gcloud alpha beyondcorp app legacy connections describe - describe a single + legacy Connection + +SYNOPSIS + gcloud alpha beyondcorp app legacy connections describe + (CONNECTION : --location=LOCATION) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Describe a single legacy Connection. + +EXAMPLES + To describe a legacy connection my-connection run: + + $ gcloud alpha beyondcorp app legacy connections describe \ + my-connection --project={project} --location=us-central1 + + To describe a legacy connection my-connection in a project for location + us-central1 in table form, run: + + $ gcloud alpha beyondcorp app legacy connections describe \ + my-connection --project={project} --location=us-central1 \ + --format=table(displayName, name.basename(), state, \ + applicationEndpoint.host, applicationEndpoint.port, \ + updateTime, labels) + +POSITIONAL ARGUMENTS + Connection resource - The Beyondcorp connector you want to get details + about. 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 connection on the command line with a fully + specified name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + This must be specified. + + CONNECTION + ID of the connection or fully qualified identifier for the + connection. To set the connection attribute: + ▸ provide the argument connection on the command line. + + This positional must be specified if any of the other arguments in + this group are specified. + + --location=LOCATION + The location of the beyondcorp service. + + To set the location attribute: + ▸ provide the argument connection on the command line with a fully + specified name; + ▸ provide the argument --location on the command line. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the beyondcorp/v1alpha API. The full documentation for + this API can be found at: https://cloud.google.com/ + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/beyondcorp/app/legacy/connections/help b/gcloud/alpha/beyondcorp/app/legacy/connections/help new file mode 100644 index 000000000..612657de3 --- /dev/null +++ b/gcloud/alpha/beyondcorp/app/legacy/connections/help @@ -0,0 +1,43 @@ +NAME + gcloud alpha beyondcorp app legacy connections - create and manipulate + beyondcorp connections + +SYNOPSIS + gcloud alpha beyondcorp app legacy connections COMMAND + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) A Beyondcorp Connection resource represents a BeyondCorp protected + connection to a remote application. It creates all the necessary Google + Cloud Platform components needed for creating a BeyondCorp protected + connection. Multiple connectors can be authorised for a single Connection. + +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 Beyondcorp application legacy connection. + + delete + (ALPHA) Delete a single legacy Connection. + + describe + (ALPHA) Describe a single legacy Connection. + + list + (ALPHA) List Beyondcorp legacy connection Resources. + + update + (ALPHA) Update an existing legacy Beyondcorp application connection. + +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/beyondcorp/app/legacy/connections/list b/gcloud/alpha/beyondcorp/app/legacy/connections/list new file mode 100644 index 000000000..06ffd9db6 --- /dev/null +++ b/gcloud/alpha/beyondcorp/app/legacy/connections/list @@ -0,0 +1,90 @@ +NAME + gcloud alpha beyondcorp app legacy connections list - list Beyondcorp + legacy connection Resources + +SYNOPSIS + gcloud alpha beyondcorp app legacy connections list --location=LOCATION + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) List Beyondcorp legacy connection resources based on project and + location. + +EXAMPLES + To list all legacy connections in a project for location us-central1 in + table form, run: + + $ gcloud alpha beyondcorp app legacy connections list \ + --project=projectId --location=us-central1 + + To list all legacy connections in a project for location us-central1 in + json form, run: + + $ gcloud alpha beyondcorp app legacy connections list \ + --project=projectId --location=us-central1 \ + --format=json(displayName, name.basename(), state, \ + applicationEndpoint.host, applicationEndpoint.port, \ + updateTime, labels) + +REQUIRED FLAGS + Location resource - Arguments and flags that define the Beyondcorp + connector you want to list. This represents a Cloud resource. (NOTE) Some + attributes are not given arguments in this group but can be set in other + ways. To set the project attribute: + ◆ provide the argument --location on the command line with a fully + specified name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + This must be specified. + + --location=LOCATION + ID of the location or fully qualified identifier for the location. To + set the location attribute: + ▸ provide the argument --location on the command line. + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the beyondcorp/v1alpha API. The full documentation for + this API can be found at: https://cloud.google.com/ + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/beyondcorp/app/legacy/connections/update b/gcloud/alpha/beyondcorp/app/legacy/connections/update new file mode 100644 index 000000000..e4bdc6c6b --- /dev/null +++ b/gcloud/alpha/beyondcorp/app/legacy/connections/update @@ -0,0 +1,119 @@ +NAME + gcloud alpha beyondcorp app legacy connections update - update an existing + legacy Beyondcorp application connection + +SYNOPSIS + gcloud alpha beyondcorp app legacy connections update + (CONNECTION : --location=LOCATION) + [--application-endpoint=APPLICATION_ENDPOINT] [--async] + [--connectors=[CONNECTORS,...]] [--display-name=DISPLAY_NAME] + [--update-labels=[KEY=VALUE,...]] + [--clear-labels | --remove-labels=[KEY,...]] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Update an existing legacy Beyondcorp application connection. + +EXAMPLES + To modify the legacy connection my-connection in 'us-central1' by adding + labels 'k0', with value 'value1' and label 'k1' with value 'value2' and + removing labels with key 'k3', run: + + $ gcloud alpha beyondcorp app legacy connections update \ + my-connection --location=us-central1 \ + --display-name=new-display-name --connectors={connector1} \ + --application-endpoint=host:port \ + --update-labels=k0=value1,k1=value2 --remove-labels=k3 + +POSITIONAL ARGUMENTS + Connection resource - The Beyondcorp connection 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 connection on the command line with a fully + specified name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + This must be specified. + + CONNECTION + ID of the connection or fully qualified identifier for the + connection. To set the connection attribute: + ▸ provide the argument connection on the command line. + + This positional must be specified if any of the other arguments in + this group are specified. + + --location=LOCATION + The location of the beyondcorp service. + + To set the location attribute: + ▸ provide the argument connection on the command line with a fully + specified name; + ▸ provide the argument --location on the command line. + +FLAGS + --application-endpoint=APPLICATION_ENDPOINT + Address of the remote application endpoint for the Beyondcorp + Connection in form of :. + + --async + Return immediately, without waiting for the operation in progress to + complete. + + --connectors=[CONNECTORS,...] + List of connectors name that are authorised to be associated with this + Connection. + + --display-name=DISPLAY_NAME + An arbitrary user-provided name for the connection. Cannot exceed 64 + characters. + + --update-labels=[KEY=VALUE,...] + List of label KEY=VALUE pairs to update. If a label exists, its value + is modified. Otherwise, a new label is created. + + Keys must start with a lowercase character and contain only hyphens + (-), underscores (_), lowercase characters, and numbers. Values must + contain only hyphens (-), underscores (_), lowercase characters, and + numbers. + + At most one of these can be specified: + + --clear-labels + Remove all labels. If --update-labels is also specified then + --clear-labels is applied first. + + For example, to remove all labels: + + $ gcloud alpha beyondcorp app legacy connections update \ + --clear-labels + + To remove all existing labels and create two new labels, foo and baz: + + $ gcloud alpha beyondcorp app legacy connections update \ + --clear-labels --update-labels foo=bar,baz=qux + + --remove-labels=[KEY,...] + List of label keys to remove. If a label does not exist it is + silently ignored. If --update-labels is also specified then + --update-labels is applied first. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the beyondcorp/v1alpha API. The full documentation for + this API can be found at: https://cloud.google.com/ + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/beyondcorp/app/legacy/connectors/create b/gcloud/alpha/beyondcorp/app/legacy/connectors/create new file mode 100644 index 000000000..c153dec41 --- /dev/null +++ b/gcloud/alpha/beyondcorp/app/legacy/connectors/create @@ -0,0 +1,98 @@ +NAME + gcloud alpha beyondcorp app legacy connectors create - create a new + Beyondcorp application legacy connector + +SYNOPSIS + gcloud alpha beyondcorp app legacy connectors create + (CONNECTOR : --location=LOCATION) --member=MEMBER [--async] + [--display-name=DISPLAY_NAME] [--labels=[KEY=VALUE,...]] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Create a new Beyondcorp application legacy connector. + +EXAMPLES + The following command creates a Connector with ID my-connector in the + default user project: + + $ gcloud alpha beyondcorp app legacy connectors create \ + my-connector --location=us-central1 \ + --member=serviceAccount:connector-sa@projectId.iam.gserviceaccou\ + nt.com + + The following command creates a Connector with ID my-connector with + explicit project value for all required and optional parameters: + + $ gcloud alpha beyondcorp app legacy connectors create \ + my-connector --project=projectId --location=us-central1 \ + --member=serviceAccount:connector-sa@projectId.iam.gserviceaccou\ + nt.com --labels='foo=bar' --display-name=connector-display-name \ + --async + +POSITIONAL ARGUMENTS + Connector resource - The Beyondcorp connector 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 connector on the command line with a fully + specified name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + This must be specified. + + CONNECTOR + ID of the connector or fully qualified identifier for the connector. + To set the connector attribute: + ▸ provide the argument connector on the command line. + + This positional must be specified if any of the other arguments in + this group are specified. + + --location=LOCATION + The location of the beyondcorp service. + + To set the location attribute: + ▸ provide the argument connector on the command line with a fully + specified name; + ▸ provide the argument --location on the command line. + +REQUIRED FLAGS + --member=MEMBER + Connector service account email in form of 'serviceAccount:email'. + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --display-name=DISPLAY_NAME + An arbitrary user-provided name for the connector. Cannot exceed 64 + characters. + + --labels=[KEY=VALUE,...] + List of label KEY=VALUE pairs to add. + + Keys must start with a lowercase character and contain only hyphens + (-), underscores (_), lowercase characters, and numbers. Values must + contain only hyphens (-), underscores (_), lowercase characters, and + numbers. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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 beyondcorp/v1alpha API. The full documentation for + this API can be found at: https://cloud.google.com/ + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/beyondcorp/app/legacy/connectors/delete b/gcloud/alpha/beyondcorp/app/legacy/connectors/delete new file mode 100644 index 000000000..880f6a22a --- /dev/null +++ b/gcloud/alpha/beyondcorp/app/legacy/connectors/delete @@ -0,0 +1,68 @@ +NAME + gcloud alpha beyondcorp app legacy connectors delete - delete a single + legacy Connector + +SYNOPSIS + gcloud alpha beyondcorp app legacy connectors delete + (CONNECTOR : --location=LOCATION) [--async] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Delete a single legacy Connector. + +EXAMPLES + To delete a legacy connector my-connector run: + + $ gcloud alpha beyondcorp app legacy connectors delete \ + my-connector --project={project} --location={location} + +POSITIONAL ARGUMENTS + Connector resource - The Beyondcorp connector 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 connector on the command line with a fully + specified name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + This must be specified. + + CONNECTOR + ID of the connector or fully qualified identifier for the connector. + To set the connector attribute: + ▸ provide the argument connector on the command line. + + This positional must be specified if any of the other arguments in + this group are specified. + + --location=LOCATION + The location of the beyondcorp service. + + To set the location attribute: + ▸ provide the argument connector on the command line with a fully + specified name; + ▸ provide the argument --location on the command line. + +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 beyondcorp/v1alpha API. The full documentation for + this API can be found at: https://cloud.google.com/ + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/beyondcorp/app/legacy/connectors/describe b/gcloud/alpha/beyondcorp/app/legacy/connectors/describe new file mode 100644 index 000000000..acdf055ad --- /dev/null +++ b/gcloud/alpha/beyondcorp/app/legacy/connectors/describe @@ -0,0 +1,75 @@ +NAME + gcloud alpha beyondcorp app legacy connectors describe - describe a single + legacy Connector + +SYNOPSIS + gcloud alpha beyondcorp app legacy connectors describe + (CONNECTOR : --location=LOCATION) [--details] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Describe a single legacy Connector. + +EXAMPLES + To describe a connector my-connector run: + + $ gcloud alpha beyondcorp app legacy connectors describe \ + my-connector --project={project} --location={location} + + To describe a connector in a project for location us-central1 in table + form, run: + + $ gcloud alpha beyondcorp app legacy connectors describe \ + --project=projectId --location=us-central1 \ + --format=table(displayName, name, state, \ + principalInfo.serviceAccount.email,createTime,updateTime,labels) + +POSITIONAL ARGUMENTS + Connector resource - The Beyondcorp connector you want to get details + about. The arguments in this group can be used to specify the attributes + of this resource. (NOTE) Some attributes are not given arguments in this + group but can be set in other ways. To set the project attribute: + ◆ provide the argument connector on the command line with a fully + specified name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + This must be specified. + + CONNECTOR + ID of the connector or fully qualified identifier for the connector. + To set the connector attribute: + ▸ provide the argument connector on the command line. + + This positional must be specified if any of the other arguments in + this group are specified. + + --location=LOCATION + The location of the beyondcorp service. + + To set the location attribute: + ▸ provide the argument connector on the command line with a fully + specified name; + ▸ provide the argument --location on the command line. + +FLAGS + --details + Includes details. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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 beyondcorp/v1alpha API. The full documentation for + this API can be found at: https://cloud.google.com/ + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/beyondcorp/app/legacy/connectors/help b/gcloud/alpha/beyondcorp/app/legacy/connectors/help new file mode 100644 index 000000000..4f3a55169 --- /dev/null +++ b/gcloud/alpha/beyondcorp/app/legacy/connectors/help @@ -0,0 +1,44 @@ +NAME + gcloud alpha beyondcorp app legacy connectors - create and manipulate + beyondcorp connectors + +SYNOPSIS + gcloud alpha beyondcorp app legacy connectors COMMAND + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) A Beyondcorp connector represents an application facing component + deployed proximal to and with direct access to the application instances. + It is used to establish connectivity between the remote enterprise + environment and Google Cloud Platform. It initiates connections to the + applications and can proxy the data from users over the connection. + +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 Beyondcorp application legacy connector. + + delete + (ALPHA) Delete a single legacy Connector. + + describe + (ALPHA) Describe a single legacy Connector. + + list + (ALPHA) List Beyondcorp legacy connector Resources. + + update + (ALPHA) Update an existing Beyondcorp application legacy connector. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/beyondcorp/app/legacy/connectors/list b/gcloud/alpha/beyondcorp/app/legacy/connectors/list new file mode 100644 index 000000000..ba71407f7 --- /dev/null +++ b/gcloud/alpha/beyondcorp/app/legacy/connectors/list @@ -0,0 +1,89 @@ +NAME + gcloud alpha beyondcorp app legacy connectors list - list Beyondcorp legacy + connector Resources + +SYNOPSIS + gcloud alpha beyondcorp app legacy connectors list --location=LOCATION + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) List Beyondcorp legacy connector resources based on project and + location. + +EXAMPLES + To list all legacy connectors in a project for location us-central1 in + table form, run: + + $ gcloud alpha beyondcorp app legacy connectors list \ + --project=projectId --location=us-central1 + + To list all legacy connectors in a project for location us-central1 in json + form, run: + + $ gcloud alpha beyondcorp app legacy connectors list \ + --project=projectId --location=us-central1 \ + --format=json(displayName, name, state, \ + principalInfo.serviceAccount.email,createTime,updateTime,labels) + +REQUIRED FLAGS + Location resource - Arguments and flags that define the Beyondcorp + connector you want to list. This represents a Cloud resource. (NOTE) Some + attributes are not given arguments in this group but can be set in other + ways. To set the project attribute: + ◆ provide the argument --location on the command line with a fully + specified name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + This must be specified. + + --location=LOCATION + ID of the location or fully qualified identifier for the location. To + set the location attribute: + ▸ provide the argument --location on the command line. + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the beyondcorp/v1alpha API. The full documentation for + this API can be found at: https://cloud.google.com/ + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/beyondcorp/app/legacy/connectors/update b/gcloud/alpha/beyondcorp/app/legacy/connectors/update new file mode 100644 index 000000000..bd216c94a --- /dev/null +++ b/gcloud/alpha/beyondcorp/app/legacy/connectors/update @@ -0,0 +1,107 @@ +NAME + gcloud alpha beyondcorp app legacy connectors update - update an existing + Beyondcorp application legacy connector + +SYNOPSIS + gcloud alpha beyondcorp app legacy connectors update + (CONNECTOR : --location=LOCATION) [--async] + [--display-name=DISPLAY_NAME] [--update-labels=[KEY=VALUE,...]] + [--clear-labels | --remove-labels=[KEY,...]] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Update an existing Beyondcorp application legacy connector. + +EXAMPLES + To modify the legacy connector my-connector in 'us-central1' by adding + labels 'k0', with value 'value1' and label 'k1' with value 'value2' and + removing labels with key 'k3', run: + + $ gcloud alpha beyondcorp app legacy connectors update \ + my-connector --location=us-central1 \ + --display-name=new-display-name \ + --update-labels=k0=value1,k1=value2 --remove-labels=k3 + +POSITIONAL ARGUMENTS + Connector resource - The Beyondcorp connector 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 connector on the command line with a fully + specified name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + This must be specified. + + CONNECTOR + ID of the connector or fully qualified identifier for the connector. + To set the connector attribute: + ▸ provide the argument connector on the command line. + + This positional must be specified if any of the other arguments in + this group are specified. + + --location=LOCATION + The location of the beyondcorp service. + + To set the location attribute: + ▸ provide the argument connector on the command line with a fully + specified name; + ▸ provide the argument --location on the command line. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --display-name=DISPLAY_NAME + An arbitrary user-provided name for the connector. Cannot exceed 64 + characters. + + --update-labels=[KEY=VALUE,...] + List of label KEY=VALUE pairs to update. If a label exists, its value + is modified. Otherwise, a new label is created. + + Keys must start with a lowercase character and contain only hyphens + (-), underscores (_), lowercase characters, and numbers. Values must + contain only hyphens (-), underscores (_), lowercase characters, and + numbers. + + At most one of these can be specified: + + --clear-labels + Remove all labels. If --update-labels is also specified then + --clear-labels is applied first. + + For example, to remove all labels: + + $ gcloud alpha beyondcorp app legacy connectors update --clear-labels + + To remove all existing labels and create two new labels, foo and baz: + + $ gcloud alpha beyondcorp app legacy connectors update \ + --clear-labels --update-labels foo=bar,baz=qux + + --remove-labels=[KEY,...] + List of label keys to remove. If a label does not exist it is + silently ignored. If --update-labels is also specified then + --update-labels is applied first. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the beyondcorp/v1alpha API. The full documentation for + this API can be found at: https://cloud.google.com/ + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/beyondcorp/app/legacy/help b/gcloud/alpha/beyondcorp/app/legacy/help new file mode 100644 index 000000000..06b3da35e --- /dev/null +++ b/gcloud/alpha/beyondcorp/app/legacy/help @@ -0,0 +1,41 @@ +NAME + gcloud alpha beyondcorp app legacy - manages application legacy connectors + and connections + +SYNOPSIS + gcloud alpha beyondcorp app legacy GROUP [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) The gcloud beyondcorp command group lets you secure non-gcp + application by managing legacy connectors and connections. + + BeyondCorp Enterprise offers a zero trust solution that enables secure + access with integrated threat and data protection.The solution enables + secure access to both Google Cloud Platform and on-prem hosted apps. For + remote apps that are not deployed in Google Cloud Platform, BeyondCorp + Enterprise's App connector provides simplified connectivity and app + publishing experience. + + More information on Beyondcorp can be found here: + https://cloud.google.com/beyondcorp + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +GROUPS + GROUP is one of the following: + + connections + (ALPHA) Create and manipulate beyondcorp connections. + + connectors + (ALPHA) Create and manipulate beyondcorp connectors. + +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/beyondcorp/app/operations/describe b/gcloud/alpha/beyondcorp/app/operations/describe new file mode 100644 index 000000000..769a4ec6b --- /dev/null +++ b/gcloud/alpha/beyondcorp/app/operations/describe @@ -0,0 +1,67 @@ +NAME + gcloud alpha beyondcorp app operations describe - describe a Beyondcorp + Appconnector operation + +SYNOPSIS + gcloud alpha beyondcorp app operations describe + (OPERATION : --location=LOCATION) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Describe a Beyondcorp Appconnector operation given a valid + operation name. + +EXAMPLES + The following command describes an operation called + operation-1484002552235-425b144f8c3f8-81aa4b49-0830d1e9: + + $ gcloud alpha beyondcorp app operations describe \ + --location=us-central1 \ + operation-1484002552235-425b144f8c3f8-81aa4b49-0830d1e9 + +POSITIONAL ARGUMENTS + Operation resource - Name of the AppConnector operation 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 operation on the command line with a fully + specified name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + This must be specified. + + OPERATION + ID of the operation or fully qualified identifier for the operation. + To set the operation attribute: + ▸ provide the argument operation on the command line. + + This positional must be specified if any of the other arguments in + this group are specified. + + --location=LOCATION + The location of the beyondcorp service. + + To set the location attribute: + ▸ provide the argument operation on the command line with a fully + specified name; + ▸ provide the argument --location on the command line. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the beyondcorp/v1alpha API. The full documentation for + this API can be found at: https://cloud.google.com/ + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/vmware/operations/help b/gcloud/alpha/beyondcorp/app/operations/help similarity index 56% rename from gcloud/alpha/vmware/operations/help rename to gcloud/alpha/beyondcorp/app/operations/help index 849da51cf..f2f8a18ea 100644 --- a/gcloud/alpha/vmware/operations/help +++ b/gcloud/alpha/beyondcorp/app/operations/help @@ -1,12 +1,12 @@ NAME - gcloud alpha vmware operations - list and describe operations in Google - Cloud VMware Engine + gcloud alpha beyondcorp app operations - list and Describe beyondcorp + appconnector operations SYNOPSIS - gcloud alpha vmware operations COMMAND [GCLOUD_WIDE_FLAG ...] + gcloud alpha beyondcorp app operations COMMAND [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) List and describe operations in Google Cloud VMware Engine. + (ALPHA) List and Describe beyondcorp appconnector operations. GCLOUD WIDE FLAGS These flags are available to all commands: --help. @@ -17,10 +17,10 @@ COMMANDS COMMAND is one of the following: describe - (ALPHA) Describe a Google Cloud VMware Engine operation. + (ALPHA) Describe a Beyondcorp Appconnector operation. list - (ALPHA) List Google Cloud VMware Engine operations. + (ALPHA) List Beyondcorp Appconnector operations. NOTES This command is currently in alpha and might change without notice. If this diff --git a/gcloud/alpha/vmware/operations/list b/gcloud/alpha/beyondcorp/app/operations/list similarity index 67% rename from gcloud/alpha/vmware/operations/list rename to gcloud/alpha/beyondcorp/app/operations/list index bb02baab9..7219899bf 100644 --- a/gcloud/alpha/vmware/operations/list +++ b/gcloud/alpha/beyondcorp/app/operations/list @@ -1,42 +1,40 @@ NAME - gcloud alpha vmware operations list - list Google Cloud VMware Engine + gcloud alpha beyondcorp app operations list - list Beyondcorp Appconnector operations SYNOPSIS - gcloud alpha vmware operations list [--location=LOCATION] + gcloud alpha beyondcorp app operations list --location=LOCATION [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] - [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + [--sort-by=[FIELD,...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) List VMware Engine operations in a location. + (ALPHA) List all Beyondcorp Appconnector operations in the specified + project. + + You can specify the maximum number of operations to list using the --limit + flag. EXAMPLES - To list VMware Engine operations in a location us-west2-a, run: + The following command lists a maximum of five operations: - $ gcloud alpha vmware operations list --location=us-west2-a + $ gcloud alpha beyondcorp app operations list \ + --location=us-central1 --limit=5 - Or: - - $ gcloud alpha vmware operations list - - In the second example, the location is taken from gcloud property - compute/zone. - -FLAGS - Location resource - location. 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: +REQUIRED FLAGS + Location resource - Region of the operations to display. This represents a + Cloud resource. (NOTE) Some attributes are not given arguments in this + group but can be set in other ways. To set the project attribute: ◆ provide the argument --location on the command line with a fully specified name; - ◆ set the property compute/zone with a fully specified name; ◆ set the property core/project; ◆ provide the argument --project on the command line. + This must be specified. + --location=LOCATION ID of the location or fully qualified identifier for the location. To set the location attribute: - ▸ provide the argument --location on the command line; - ▸ set the property compute/zone. + ▸ provide the argument --location on the command line. LIST COMMAND FLAGS --filter=EXPRESSION @@ -64,12 +62,6 @@ LIST COMMAND FLAGS order on that field. This flag interacts with other flags that are applied in this order: --flatten, --sort-by, --filter, --limit. - --uri - Print a list of resource URIs instead of the default output, and change - the command output to a list of URIs. If this flag is used with - --format, the formatting is applied on this URI list. To display URIs - alongside other keys instead, use the uri() transform. - GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, @@ -78,6 +70,10 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. +API REFERENCE + This command uses the beyondcorp/v1alpha API. The full documentation for + this API can be found at: https://cloud.google.com/ + NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct diff --git a/gcloud/alpha/beyondcorp/client-connector/gateways/create b/gcloud/alpha/beyondcorp/client-connector/gateways/create new file mode 100644 index 000000000..53a9e0f87 --- /dev/null +++ b/gcloud/alpha/beyondcorp/client-connector/gateways/create @@ -0,0 +1,88 @@ +NAME + gcloud alpha beyondcorp client-connector gateways create - create a new + BeyondCorp client gateway + +SYNOPSIS + gcloud alpha beyondcorp client-connector gateways create + (CLIENT_GATEWAY : --location=LOCATION) + --client-connector-service=CLIENT_CONNECTOR_SERVICE [--async] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Create a new BeyondCorp client gateway. + +EXAMPLES + The following command creates a client gateway with ID my-client-gateway in + the default user project and location us-central1: + + $ gcloud alpha beyondcorp client-connector gateways create \ + my-client-gateway --location=us-central1 \ + --client-connector-service=projects/consumer-project-id/\ + locations/us-central1/clientConnectorServices/my-service-resource + + The following command creates a client gateway with ID my-client-gateway + with explicit values for all required and optional parameters: + + $ gcloud alpha beyondcorp client-connector gateways create \ + my-client-gateway --project=consumer-project-id \ + --location=us-central1 \ + --client-connector-service=projects/consumer-project-id/\ + locations/us-central1/clientConnectorServices/my-service-resource + +POSITIONAL ARGUMENTS + Client gateway resource - The BeyondCorp client gateway 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 client_gateway on the command line with a fully + specified name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + This must be specified. + + CLIENT_GATEWAY + ID of the client_gateway or fully qualified identifier for the + client_gateway. To set the client_gateway attribute: + ▸ provide the argument client_gateway on the command line. + + This positional must be specified if any of the other arguments in + this group are specified. + + --location=LOCATION + The location of the BeyondCorp Enterprise client connector. + + To set the location attribute: + ▸ provide the argument client_gateway on the command line with a + fully specified name; + ▸ provide the argument --location on the command line. + +REQUIRED FLAGS + --client-connector-service=CLIENT_CONNECTOR_SERVICE + The client connector service that the client gateway is associated + with. Example - + projects/consumer-project-id/locations/us-central1/clientConnectorServices/my-service-resource. + +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 beyondcorp/v1alpha API. The full documentation for + this API can be found at: https://cloud.google.com/ + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/beyondcorp/client-connector/gateways/delete b/gcloud/alpha/beyondcorp/client-connector/gateways/delete new file mode 100644 index 000000000..f86ce9e7d --- /dev/null +++ b/gcloud/alpha/beyondcorp/client-connector/gateways/delete @@ -0,0 +1,69 @@ +NAME + gcloud alpha beyondcorp client-connector gateways delete - delete a single + BeyondCorp client gateway + +SYNOPSIS + gcloud alpha beyondcorp client-connector gateways delete + (CLIENT_GATEWAY : --location=LOCATION) [--async] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Delete a single BeyondCorp client gateway. + +EXAMPLES + To delete a client gateway with ID my-client-gateway run: + + $ gcloud alpha beyondcorp client-connector gateways delete \ + my-client-gateway --project=consumer-project-id \ + --location=us-central1 + +POSITIONAL ARGUMENTS + Client gateway resource - The BeyondCorp client gateway 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 client_gateway on the command line with a fully + specified name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + This must be specified. + + CLIENT_GATEWAY + ID of the client_gateway or fully qualified identifier for the + client_gateway. To set the client_gateway attribute: + ▸ provide the argument client_gateway on the command line. + + This positional must be specified if any of the other arguments in + this group are specified. + + --location=LOCATION + The location of the BeyondCorp Enterprise client connector. + + To set the location attribute: + ▸ provide the argument client_gateway on the command line with a + fully specified name; + ▸ provide the argument --location on the command line. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the beyondcorp/v1alpha API. The full documentation for + this API can be found at: https://cloud.google.com/ + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/beyondcorp/client-connector/gateways/describe b/gcloud/alpha/beyondcorp/client-connector/gateways/describe new file mode 100644 index 000000000..78c6bd021 --- /dev/null +++ b/gcloud/alpha/beyondcorp/client-connector/gateways/describe @@ -0,0 +1,65 @@ +NAME + gcloud alpha beyondcorp client-connector gateways describe - describe a + single BeyondCorp client gateway + +SYNOPSIS + gcloud alpha beyondcorp client-connector gateways describe + (CLIENT_GATEWAY : --location=LOCATION) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Describe a single BeyondCorp client gateway. + +EXAMPLES + To describe a client gateway my-client-gateway run: + + $ gcloud alpha beyondcorp client-connector gateways describe \ + my-client-gateway --project=consumer-project-id \ + --location=us-central1 + +POSITIONAL ARGUMENTS + Client gateway resource - The BeyondCorp client gateway you want to get + details about. 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 client_gateway on the command line with a fully + specified name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + This must be specified. + + CLIENT_GATEWAY + ID of the client_gateway or fully qualified identifier for the + client_gateway. To set the client_gateway attribute: + ▸ provide the argument client_gateway on the command line. + + This positional must be specified if any of the other arguments in + this group are specified. + + --location=LOCATION + The location of the BeyondCorp Enterprise client connector. + + To set the location attribute: + ▸ provide the argument client_gateway on the command line with a + fully specified name; + ▸ provide the argument --location on the command line. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the beyondcorp/v1alpha API. The full documentation for + this API can be found at: https://cloud.google.com/ + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/beyondcorp/client-connector/gateways/help b/gcloud/alpha/beyondcorp/client-connector/gateways/help new file mode 100644 index 000000000..b87b3aac9 --- /dev/null +++ b/gcloud/alpha/beyondcorp/client-connector/gateways/help @@ -0,0 +1,42 @@ +NAME + gcloud alpha beyondcorp client-connector gateways - create and manipulate + BeyondCorp client gateways + +SYNOPSIS + gcloud alpha beyondcorp client-connector gateways COMMAND + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Regional, server-side components to which clients can connect. + Client gateways are deployed by administrators. The gateways communicate + with the BeyondCorp Enterprise enforcement system to enforce context-aware + checks. The BeyondCorp Enterprise enforcement system uses Identity-Aware + Proxy and Access Context Manager, a flexible BeyondCorp Enterprise zero + trust policy engine. + +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 BeyondCorp client gateway. + + delete + (ALPHA) Delete a single BeyondCorp client gateway. + + describe + (ALPHA) Describe a single BeyondCorp client gateway. + + list + (ALPHA) List BeyondCorp client gateway resources. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/vmware/private-clouds/list b/gcloud/alpha/beyondcorp/client-connector/gateways/list similarity index 67% rename from gcloud/alpha/vmware/private-clouds/list rename to gcloud/alpha/beyondcorp/client-connector/gateways/list index 40253e6c4..fa23ecee5 100644 --- a/gcloud/alpha/vmware/private-clouds/list +++ b/gcloud/alpha/beyondcorp/client-connector/gateways/list @@ -1,42 +1,39 @@ NAME - gcloud alpha vmware private-clouds list - list Google Cloud VMware Engine - private clouds + gcloud alpha beyondcorp client-connector gateways list - list BeyondCorp + client gateway resources SYNOPSIS - gcloud alpha vmware private-clouds list [--location=LOCATION] + gcloud alpha beyondcorp client-connector gateways list --location=LOCATION [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] - [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + [--sort-by=[FIELD,...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) List VMware Engine private clouds. + (ALPHA) List BeyondCorp client gateway resources based on project and + location. EXAMPLES - To list VMware Engine operations in the location us-west2-a, run: + To list all client gateways in a project for location us-central1 in table + form, run: - $ gcloud alpha vmware private-clouds list --location=us-west2-a + $ gcloud alpha beyondcorp client-connector gateways list \ + --project=consumer-project-id --location=us-central1 - Or: - - $ gcloud alpha vmware private-clouds list - - In the second example, the location is taken from gcloud properties - compute/zone. - -FLAGS - Location resource - location. 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: +REQUIRED FLAGS + Location resource - Arguments and flags that define the BeyondCorp client + gateways you want to list. This represents a Cloud resource. (NOTE) Some + attributes are not given arguments in this group but can be set in other + ways. To set the project attribute: ◆ provide the argument --location on the command line with a fully specified name; - ◆ set the property compute/zone with a fully specified name; ◆ set the property core/project; ◆ provide the argument --project on the command line. + This must be specified. + --location=LOCATION ID of the location or fully qualified identifier for the location. To set the location attribute: - ▸ provide the argument --location on the command line; - ▸ set the property compute/zone. + ▸ provide the argument --location on the command line. LIST COMMAND FLAGS --filter=EXPRESSION @@ -64,12 +61,6 @@ LIST COMMAND FLAGS order on that field. This flag interacts with other flags that are applied in this order: --flatten, --sort-by, --filter, --limit. - --uri - Print a list of resource URIs instead of the default output, and change - the command output to a list of URIs. If this flag is used with - --format, the formatting is applied on this URI list. To display URIs - alongside other keys instead, use the uri() transform. - GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, @@ -78,6 +69,10 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. +API REFERENCE + This command uses the beyondcorp/v1alpha API. The full documentation for + this API can be found at: https://cloud.google.com/ + NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct diff --git a/gcloud/alpha/beyondcorp/client-connector/help b/gcloud/alpha/beyondcorp/client-connector/help new file mode 100644 index 000000000..e7f11198a --- /dev/null +++ b/gcloud/alpha/beyondcorp/client-connector/help @@ -0,0 +1,44 @@ +NAME + gcloud alpha beyondcorp client-connector - provides context-aware access to + non-web applications + +SYNOPSIS + gcloud alpha beyondcorp client-connector GROUP [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) BeyondCorp Enterprise is the zero trust solution from Google that + provides secure access to private applications with integrated threat and + data protection. BeyondCorp Enterprise uses Chrome to provide secure access + for all web-based (HTTPS) applications. + + The BeyondCorp Enterprise client connector extends support to non-web + applications by creating a secure connection to applications running in + both Google Cloud and non-Google Cloud environments with full context and + identity aware access. + + More information on Beyondcorp can be found here: + https://cloud.google.com/beyondcorp-enterprise/docs/client-connector + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +GROUPS + GROUP is one of the following: + + gateways + (ALPHA) Create and manipulate BeyondCorp client gateways. + + operations + (ALPHA) List and describe BeyondCorp client connector operations. + + services + (ALPHA) Create and manipulate BeyondCorp client connector services. + +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/beyondcorp/client-connector/operations/describe b/gcloud/alpha/beyondcorp/client-connector/operations/describe new file mode 100644 index 000000000..6ada6952c --- /dev/null +++ b/gcloud/alpha/beyondcorp/client-connector/operations/describe @@ -0,0 +1,67 @@ +NAME + gcloud alpha beyondcorp client-connector operations describe - describe a + BeyondCorp client connector operation + +SYNOPSIS + gcloud alpha beyondcorp client-connector operations describe + (OPERATION : --location=LOCATION) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Describe a BeyondCorp client connector operation given a valid + operation name. + +EXAMPLES + The following command describes an operation called + operation-1484002552235-425b144f8c3f8-81aa4b49-0830d1e9: + + $ gcloud alpha beyondcorp client-connector operations describe \ + operation-1484002552235-425b144f8c3f8-81aa4b49-0830d1e9 \ + --project=consumer-project-id --location=us-central1 + +POSITIONAL ARGUMENTS + Operation resource - Name of the client connector operation 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 operation on the command line with a fully + specified name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + This must be specified. + + OPERATION + ID of the operation or fully qualified identifier for the operation. + To set the operation attribute: + ▸ provide the argument operation on the command line. + + This positional must be specified if any of the other arguments in + this group are specified. + + --location=LOCATION + The location of the BeyondCorp Enterprise client connector. + + To set the location attribute: + ▸ provide the argument operation on the command line with a fully + specified name; + ▸ provide the argument --location on the command line. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the beyondcorp/v1alpha API. The full documentation for + this API can be found at: https://cloud.google.com/ + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/vmware/node-types/help b/gcloud/alpha/beyondcorp/client-connector/operations/help similarity index 53% rename from gcloud/alpha/vmware/node-types/help rename to gcloud/alpha/beyondcorp/client-connector/operations/help index 97e3bcfea..782f1fc2e 100644 --- a/gcloud/alpha/vmware/node-types/help +++ b/gcloud/alpha/beyondcorp/client-connector/operations/help @@ -1,12 +1,13 @@ NAME - gcloud alpha vmware node-types - show node types in Google Cloud VMware - Engine + gcloud alpha beyondcorp client-connector operations - list and describe + BeyondCorp client connector operations SYNOPSIS - gcloud alpha vmware node-types COMMAND [GCLOUD_WIDE_FLAG ...] + gcloud alpha beyondcorp client-connector operations COMMAND + [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) Show node types in Google Cloud VMware Engine. + (ALPHA) List and describe BeyondCorp client connector operations. GCLOUD WIDE FLAGS These flags are available to all commands: --help. @@ -17,11 +18,10 @@ COMMANDS COMMAND is one of the following: describe - (ALPHA) Display data associated with a Google Cloud VMware Engine node - type. + (ALPHA) Describe a BeyondCorp client connector operation. list - (ALPHA) List supported Google Cloud VMware Engine node types. + (ALPHA) List BeyondCorp client connector operations. NOTES This command is currently in alpha and might change without notice. If this diff --git a/gcloud/alpha/beyondcorp/client-connector/operations/list b/gcloud/alpha/beyondcorp/client-connector/operations/list new file mode 100644 index 000000000..2a6c32160 --- /dev/null +++ b/gcloud/alpha/beyondcorp/client-connector/operations/list @@ -0,0 +1,82 @@ +NAME + gcloud alpha beyondcorp client-connector operations list - list BeyondCorp + client connector operations + +SYNOPSIS + gcloud alpha beyondcorp client-connector operations list + --location=LOCATION [--filter=EXPRESSION] [--limit=LIMIT] + [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) List all BeyondCorp client connector operations in the specified + project. + + You can specify the maximum number of operations to list using the --limit + flag. + +EXAMPLES + The following command lists a maximum of five operations: + + $ gcloud alpha beyondcorp client-connector operations list \ + --project=consumer-project-id --location=us-central1 --limit=5 + +REQUIRED FLAGS + Location resource - Location of the operations to display. This represents + a Cloud resource. (NOTE) Some attributes are not given arguments in this + group but can be set in other ways. To set the project attribute: + ◆ provide the argument --location on the command line with a fully + specified name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + This must be specified. + + --location=LOCATION + ID of the location or fully qualified identifier for the location. To + set the location attribute: + ▸ provide the argument --location on the command line. + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the beyondcorp/v1alpha API. The full documentation for + this API can be found at: https://cloud.google.com/ + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/beyondcorp/client-connector/services/create b/gcloud/alpha/beyondcorp/client-connector/services/create new file mode 100644 index 000000000..add75ad5e --- /dev/null +++ b/gcloud/alpha/beyondcorp/client-connector/services/create @@ -0,0 +1,139 @@ +NAME + gcloud alpha beyondcorp client-connector services create - create a new + BeyondCorp client connector service + +SYNOPSIS + gcloud alpha beyondcorp client-connector services create + (CLIENT_CONNECTOR_SERVICE : --location=LOCATION) + (--config-from-file=CONFIG_FROM_FILE + | [--egress-peered-vpc=EGRESS_PEERED_VPC + --ingress-config=INGRESS_CONFIG : --display-name=DISPLAY_NAME]) + [--async] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Create a new BeyondCorp client connector service. + +EXAMPLES + The following command creates a client connector service with ID + my-service-resource using ingress/egress config provided: + + $ gcloud alpha beyondcorp client-connector services create \ + my-service-resource --location=us-central1 \ + --project=consumer-project-id \ + --ingress-config='{"transportProtocol":"TCP", + "destinationRoutes":[{"address":"196.0.0.1", + "netmask":"255.255.255.0"}]}' \ + --egress-peered-vpc='{"networkVpc":"projects/consumer-project-id\ + /global/networks/my-vpc-network"}' + + The following command creates a client connector service with ID + my-service-resource with configuration from file: + + $ gcloud alpha beyondcorp client-connector services create \ + my-service-resource --project=consumer-project-id \ + --location=us-central1 \ + --config-from-file=/path/to/file/configJson.txt + +POSITIONAL ARGUMENTS + Client connector service resource - The BeyondCorp client connector + service 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 client_connector_service on the command line + with a fully specified name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + This must be specified. + + CLIENT_CONNECTOR_SERVICE + ID of the client_connector_service or fully qualified identifier for + the client_connector_service. To set the client_connector_service + attribute: + ▸ provide the argument client_connector_service on the command + line. + + This positional must be specified if any of the other arguments in + this group are specified. + + --location=LOCATION + The location of the BeyondCorp Enterprise client connector. + + To set the location attribute: + ▸ provide the argument client_connector_service on the command line + with a fully specified name; + ▸ provide the argument --location on the command line. + +REQUIRED FLAGS + Client connector service configuration. + + Exactly one of these must be specified: + + --config-from-file=CONFIG_FROM_FILE + Path to json file containing client connector service configuration. + Example - "/file/path/configJson.txt" where configJson.txt contains - { + "ingress":{ + "config":{ + "transportProtocol":"TCP", + "destinationRoutes":[{ + "address":"196.0.0.1", + "netmask":"255.255.255.0" + }] + } + }, + "egress":{ + "peeredVpc":{ + "networkVpc":"projects/consumer-project-id/global/networks/my-vpc-network" + } + }, + "displayName":"my-service-resource" + } + + --egress-peered-vpc=EGRESS_PEERED_VPC + The peered VPC owned by the consumer project. Example - + {"networkVpc": + "projects/consumer-project-id/global/networks/my-vpc-network"}. + + This flag must be specified if any of the other arguments in this + group are specified. + + --ingress-config=INGRESS_CONFIG + The basic ingress config for client gateways. Example - + {"transportProtocol": + "TCP","destinationRoutes":[{"address":"196.0.0.1", + "netmask":"255.255.255.0"}]}. + + This flag must be specified if any of the other arguments in this + group are specified. + + --display-name=DISPLAY_NAME + An arbitrary user-provided name for the client connector service. The + display name should follow format - + ▸ Must be 6 to 30 characters in length. + ▸ Can only contain lowercase letters, numbers and hyphens. + ▸ Must start with a letter. + +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 beyondcorp/v1alpha API. The full documentation for + this API can be found at: https://cloud.google.com/ + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/beyondcorp/client-connector/services/delete b/gcloud/alpha/beyondcorp/client-connector/services/delete new file mode 100644 index 000000000..b25e9264d --- /dev/null +++ b/gcloud/alpha/beyondcorp/client-connector/services/delete @@ -0,0 +1,73 @@ +NAME + gcloud alpha beyondcorp client-connector services delete - delete a + BeyondCorp client connector service + +SYNOPSIS + gcloud alpha beyondcorp client-connector services delete + (CLIENT_CONNECTOR_SERVICE : --location=LOCATION) [--async] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Delete a BeyondCorp client connector service. + +EXAMPLES + To delete a client connector service with ID my-service-resource run: + + $ gcloud alpha beyondcorp client-connector services delete \ + my-service-resource --project=consumer-project-id \ + --location=us-central1 + +POSITIONAL ARGUMENTS + Client connector service resource - The BeyondCorp client connector + service 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 client_connector_service on the command line + with a fully specified name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + This must be specified. + + CLIENT_CONNECTOR_SERVICE + ID of the client_connector_service or fully qualified identifier for + the client_connector_service. To set the client_connector_service + attribute: + ▸ provide the argument client_connector_service on the command + line. + + This positional must be specified if any of the other arguments in + this group are specified. + + --location=LOCATION + The location of the BeyondCorp Enterprise client connector. + + To set the location attribute: + ▸ provide the argument client_connector_service on the command line + with a fully specified name; + ▸ provide the argument --location on the command line. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the beyondcorp/v1alpha API. The full documentation for + this API can be found at: https://cloud.google.com/ + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/beyondcorp/client-connector/services/describe b/gcloud/alpha/beyondcorp/client-connector/services/describe new file mode 100644 index 000000000..8329f0d57 --- /dev/null +++ b/gcloud/alpha/beyondcorp/client-connector/services/describe @@ -0,0 +1,67 @@ +NAME + gcloud alpha beyondcorp client-connector services describe - describe a + BeyondCorp client connector service + +SYNOPSIS + gcloud alpha beyondcorp client-connector services describe + (CLIENT_CONNECTOR_SERVICE : --location=LOCATION) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Describe a BeyondCorp client connector service. + +EXAMPLES + To describe a client connector service with ID my-service-resource run: + + $ gcloud alpha beyondcorp client-connector services describe \ + my-service-resource --project=consumer-project-id \ + --location=us-central1 + +POSITIONAL ARGUMENTS + Client connector service resource - The BeyondCorp client connector + service you want to get details about. 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 client_connector_service on the command line + with a fully specified name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + This must be specified. + + CLIENT_CONNECTOR_SERVICE + ID of the client_connector_service or fully qualified identifier for + the client_connector_service. To set the client_connector_service + attribute: + ▸ provide the argument client_connector_service on the command + line. + + This positional must be specified if any of the other arguments in + this group are specified. + + --location=LOCATION + The location of the BeyondCorp Enterprise client connector. + + To set the location attribute: + ▸ provide the argument client_connector_service on the command line + with a fully specified name; + ▸ provide the argument --location on the command line. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the beyondcorp/v1alpha API. The full documentation for + this API can be found at: https://cloud.google.com/ + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/beyondcorp/client-connector/services/help b/gcloud/alpha/beyondcorp/client-connector/services/help new file mode 100644 index 000000000..000440549 --- /dev/null +++ b/gcloud/alpha/beyondcorp/client-connector/services/help @@ -0,0 +1,47 @@ +NAME + gcloud alpha beyondcorp client-connector services - create and manipulate + BeyondCorp client connector services + +SYNOPSIS + gcloud alpha beyondcorp client-connector services COMMAND + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) The client connector service is used to define a common + configuration for a group of client gateways. Client gateways refer to the + client connector service and are used to control the regions where you want + to manage user traffic. The gateways communicate with the BeyondCorp + Enterprise enforcement system to enforce context-aware checks. The + BeyondCorp Enterprise enforcement system uses Identity-Aware Proxy and + Access Context Manager, a flexible BeyondCorp Enterprise zero trust policy + engine. + +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 BeyondCorp client connector service. + + delete + (ALPHA) Delete a BeyondCorp client connector service. + + describe + (ALPHA) Describe a BeyondCorp client connector service. + + list + (ALPHA) List BeyondCorp client connector service resources. + + update + (ALPHA) Update a BeyondCorp client connector 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 + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/vmware/network-peerings/list b/gcloud/alpha/beyondcorp/client-connector/services/list similarity index 65% rename from gcloud/alpha/vmware/network-peerings/list rename to gcloud/alpha/beyondcorp/client-connector/services/list index b5341fc0b..c40496e42 100644 --- a/gcloud/alpha/vmware/network-peerings/list +++ b/gcloud/alpha/beyondcorp/client-connector/services/list @@ -1,41 +1,45 @@ NAME - gcloud alpha vmware network-peerings list - list Google Cloud VMware Engine - VPC network peerings + gcloud alpha beyondcorp client-connector services list - list BeyondCorp + client connector service resources SYNOPSIS - gcloud alpha vmware network-peerings list [--location=LOCATION] + gcloud alpha beyondcorp client-connector services list --location=LOCATION [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] - [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + [--sort-by=[FIELD,...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) List VPC network peerings across all locations in your project. + (ALPHA) List BeyondCorp client connector service resources based on project + and location. EXAMPLES - To list all the VPC network peerings created on or after April 12, 2021, - sorted from oldest to newest, run: + To list all client connector services in a project for location us-central1 + in table form, run: - $ gcloud alpha vmware network-peerings list \ - --filter="createTime > 2021-04-12T00:00:00.00Z" \ - --sort-by=createTime + $ gcloud alpha beyondcorp client-connector services list \ + --project=consumer-project-id --location=us-central1 - In this example, the location is taken as global. + To list all client connector service in a project for location us-central1 + with limit=1, run: -FLAGS - Location resource - location. 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: + $ gcloud alpha beyondcorp client-connector services list \ + --project=consumer-project-id --location=us-central1 --limit=1 + +REQUIRED FLAGS + Location resource - Arguments and flags that define the BeyondCorp client + connector services you want to list. This represents a Cloud resource. + (NOTE) Some attributes are not given arguments in this group but can be + set in other ways. To set the project attribute: ◆ provide the argument --location on the command line with a fully specified name; - ◆ set location as 'global' (default) or a region with a fully specified - name; ◆ set the property core/project; ◆ provide the argument --project on the command line. + This must be specified. + --location=LOCATION ID of the location or fully qualified identifier for the location. To set the location attribute: - ▸ provide the argument --location on the command line; - ▸ set location as 'global' (default) or a region. + ▸ provide the argument --location on the command line. LIST COMMAND FLAGS --filter=EXPRESSION @@ -63,12 +67,6 @@ LIST COMMAND FLAGS order on that field. This flag interacts with other flags that are applied in this order: --flatten, --sort-by, --filter, --limit. - --uri - Print a list of resource URIs instead of the default output, and change - the command output to a list of URIs. If this flag is used with - --format, the formatting is applied on this URI list. To display URIs - alongside other keys instead, use the uri() transform. - GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, @@ -77,6 +75,10 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. +API REFERENCE + This command uses the beyondcorp/v1alpha API. The full documentation for + this API can be found at: https://cloud.google.com/ + NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct diff --git a/gcloud/alpha/beyondcorp/client-connector/services/update b/gcloud/alpha/beyondcorp/client-connector/services/update new file mode 100644 index 000000000..ea40785d0 --- /dev/null +++ b/gcloud/alpha/beyondcorp/client-connector/services/update @@ -0,0 +1,81 @@ +NAME + gcloud alpha beyondcorp client-connector services update - update a + BeyondCorp client connector service + +SYNOPSIS + gcloud alpha beyondcorp client-connector services update + (CLIENT_CONNECTOR_SERVICE : --location=LOCATION) [--async] + [--display-name=DISPLAY_NAME] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Update a BeyondCorp client connector service. + +EXAMPLES + The following command updates a client connector service with ID + my-service-resource in location us-central1: + + $ gcloud alpha beyondcorp client-connector services update \ + my-service-resource --project=consumer-project-id \ + --location=us-central1 --display-name="my-new-resource" + +POSITIONAL ARGUMENTS + Client connector service resource - The BeyondCorp client connector + service 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 client_connector_service on the command line + with a fully specified name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + This must be specified. + + CLIENT_CONNECTOR_SERVICE + ID of the client_connector_service or fully qualified identifier for + the client_connector_service. To set the client_connector_service + attribute: + ▸ provide the argument client_connector_service on the command + line. + + This positional must be specified if any of the other arguments in + this group are specified. + + --location=LOCATION + The location of the BeyondCorp Enterprise client connector. + + To set the location attribute: + ▸ provide the argument client_connector_service on the command line + with a fully specified name; + ▸ provide the argument --location on the command line. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --display-name=DISPLAY_NAME + An arbitrary user-provided name for the client connector service. The + display name should follow format - + ◆ Must be 6 to 30 characters in length. + ◆ Can only contain lowercase letters, numbers and hyphens. + ◆ Must start with a letter. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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 beyondcorp/v1alpha API. The full documentation for + this API can be found at: https://cloud.google.com/ + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/beyondcorp/help b/gcloud/alpha/beyondcorp/help new file mode 100644 index 000000000..000b275e9 --- /dev/null +++ b/gcloud/alpha/beyondcorp/help @@ -0,0 +1,41 @@ +NAME + gcloud alpha beyondcorp - manage secure access to applications with + integrated threat and data protection + +SYNOPSIS + gcloud alpha beyondcorp GROUP [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) BeyondCorp Enterprise offers a zero trust solution that enables + secure access with integrated threat and data protection.The solution + enables secure access to both Google Cloud Platform and on-prem hosted + apps. For remote apps that are not deployed in Google Cloud Platform, + BeyondCorp Enterprise's App connector provides simplified connectivity and + app publishing experience. The BeyondCorp Enterprise client connector + extends support to non-web applications by creating a secure connection to + applications running in both Google Cloud and non-Google Cloud environments + with full context and identity aware access. + + More information on Beyondcorp can be found here: + https://cloud.google.com/beyondcorp + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +GROUPS + GROUP is one of the following: + + app + (ALPHA) Manages application connectors and connections. + + client-connector + (ALPHA) Provides context-aware access to non-web applications. + +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/firewall-policies/rules/create b/gcloud/alpha/compute/firewall-policies/rules/create index 67e4546bc..24f70a7e7 100644 --- a/gcloud/alpha/compute/firewall-policies/rules/create +++ b/gcloud/alpha/compute/firewall-policies/rules/create @@ -32,7 +32,7 @@ POSITIONAL ARGUMENTS REQUIRED FLAGS --action=ACTION Action to take if the request matches the match condition. ACTION must - be one of: allow, deny, goto_next. + be one of: allow, deny, goto_next, apply_profile_group. --firewall-policy=FIREWALL_POLICY Short name of the firewall policy into which the rule should be diff --git a/gcloud/alpha/compute/firewall-policies/rules/update b/gcloud/alpha/compute/firewall-policies/rules/update index f437e9830..d621e97b8 100644 --- a/gcloud/alpha/compute/firewall-policies/rules/update +++ b/gcloud/alpha/compute/firewall-policies/rules/update @@ -38,7 +38,7 @@ REQUIRED FLAGS OPTIONAL FLAGS --action=ACTION Action to take if the request matches the match condition. ACTION must - be one of: allow, deny, goto_next. + be one of: allow, deny, goto_next, apply_profile_group. --description=DESCRIPTION An optional, textual description for the rule. diff --git a/gcloud/alpha/compute/instance-groups/managed/create b/gcloud/alpha/compute/instance-groups/managed/create index 2e7cb1267..e87165763 100644 --- a/gcloud/alpha/compute/instance-groups/managed/create +++ b/gcloud/alpha/compute/instance-groups/managed/create @@ -66,28 +66,27 @@ OPTIONAL FLAGS An instance redistribution type can be specified only for a non-autoscaled regional managed instance group. By default it is set to - PROACTIVE. + proactive. - The following types are available: + TYPE must be one of: - ◆ NONE - The managed instance group does not redistribute instances - across zones. - - ◆ PROACTIVE - The managed instance group proactively redistributes - instances to meet its target distribution. - - TYPE must be one of: NONE, PROACTIVE. + none + The managed instance group does not redistribute instances across + zones. + proactive + The managed instance group proactively redistributes instances to + meet its target distribution. --list-managed-instances-results=MODE Pagination behavior for the group's listManagedInstances API method. This flag does not affect the group's gcloud or console list-instances - behavior. By default it is set to PAGELESS. MODE must be one of: + behavior. By default it is set to pageless. MODE must be one of: - PAGELESS + pageless Pagination is disabled for the group's listManagedInstances API method. maxResults and pageToken query parameters are ignored and all instances are returned in a single response. - PAGINATED + paginated Pagination is enabled for the group's listManagedInstances API method. maxResults and pageToken query parameters are respected. @@ -183,21 +182,21 @@ OPTIONAL FLAGS --target-distribution-shape=SHAPE Specifies how a regional managed instance group distributes its - instances across zones within the region. The default shape is EVEN. + instances across zones within the region. The default shape is even. SHAPE must be one of: - ANY + any The group picks zones for creating VM instances to fulfill the requested number of VMs within present resource constraints and to maximize utilization of unused zonal reservations. Recommended for batch workloads that do not require high availability. - BALANCED + balanced The group prioritizes acquisition of resources, scheduling VMs in zones where resources are available while distributing VMs as evenly as possible across selected zones to minimize the impact of zonal failure. Recommended for highly available serving or batch workloads that do not require autoscaling. - EVEN + even The group schedules VM instance creation and deletion to achieve and maintain an even number of managed instances across the selected zones. The distribution is even when the number of managed diff --git a/gcloud/alpha/compute/instance-groups/managed/update b/gcloud/alpha/compute/instance-groups/managed/update index 2e902ac03..7d5c6a3b5 100644 --- a/gcloud/alpha/compute/instance-groups/managed/update +++ b/gcloud/alpha/compute/instance-groups/managed/update @@ -59,28 +59,27 @@ FLAGS An instance redistribution type can be specified only for a non-autoscaled regional managed instance group. By default it is set to - PROACTIVE. + proactive. - The following types are available: + TYPE must be one of: - ◆ NONE - The managed instance group does not redistribute instances - across zones. - - ◆ PROACTIVE - The managed instance group proactively redistributes - instances to meet its target distribution. - - TYPE must be one of: NONE, PROACTIVE. + none + The managed instance group does not redistribute instances across + zones. + proactive + The managed instance group proactively redistributes instances to + meet its target distribution. --list-managed-instances-results=MODE Pagination behavior for the group's listManagedInstances API method. This flag does not affect the group's gcloud or console list-instances - behavior. By default it is set to PAGELESS. MODE must be one of: + behavior. By default it is set to pageless. MODE must be one of: - PAGELESS + pageless Pagination is disabled for the group's listManagedInstances API method. maxResults and pageToken query parameters are ignored and all instances are returned in a single response. - PAGINATED + paginated Pagination is enabled for the group's listManagedInstances API method. maxResults and pageToken query parameters are respected. @@ -200,21 +199,21 @@ FLAGS --target-distribution-shape=SHAPE Specifies how a regional managed instance group distributes its - instances across zones within the region. The default shape is EVEN. + instances across zones within the region. The default shape is even. SHAPE must be one of: - ANY + any The group picks zones for creating VM instances to fulfill the requested number of VMs within present resource constraints and to maximize utilization of unused zonal reservations. Recommended for batch workloads that do not require high availability. - BALANCED + balanced The group prioritizes acquisition of resources, scheduling VMs in zones where resources are available while distributing VMs as evenly as possible across selected zones to minimize the impact of zonal failure. Recommended for highly available serving or batch workloads that do not require autoscaling. - EVEN + even The group schedules VM instance creation and deletion to achieve and maintain an even number of managed instances across the selected zones. The distribution is even when the number of managed diff --git a/gcloud/alpha/compute/instance-templates/create b/gcloud/alpha/compute/instance-templates/create index e37c830a1..ff8211b4b 100644 --- a/gcloud/alpha/compute/instance-templates/create +++ b/gcloud/alpha/compute/instance-templates/create @@ -15,6 +15,7 @@ SYNOPSIS [boot=BOOT],[device-name=DEVICE-NAME],[mode=MODE],[name=NAME]] [--[no-]enable-nested-virtualization] [--[no-]enable-uefi-networking] [--host-error-timeout-seconds=HOST_ERROR_TIMEOUT_SECONDS] + [--instance-template-region=INSTANCE_TEMPLATE_REGION] [--instance-termination-action=INSTANCE_TERMINATION_ACTION] [--ipv6-network-tier=IPV6_NETWORK_TIER] [--key-revocation-action-type=POLICY] [--labels=[KEY=VALUE,...]] @@ -38,8 +39,8 @@ SYNOPSIS [--shielded-integrity-monitoring] [--shielded-secure-boot] [--shielded-vtpm] [--source-instance=SOURCE_INSTANCE] [--source-instance-zone=SOURCE_INSTANCE_ZONE] [--stack-type=STACK_TYPE] - [--subnet=SUBNET] [--tags=TAG,[TAG,...]] - [--termination-time=TERMINATION_TIME] + [--subnet=SUBNET] [--subnet-region=SUBNET_REGION] + [--tags=TAG,[TAG,...]] [--termination-time=TERMINATION_TIME] [--threads-per-core=THREADS_PER_CORE] [--visible-core-count=VISIBLE_CORE_COUNT] [--address=ADDRESS | --no-address] @@ -364,6 +365,9 @@ FLAGS with 30 second increments, with a range of 90 to 330 seconds. If unset, the default behavior of the host error recovery is used. + --instance-template-region=INSTANCE_TEMPLATE_REGION + Specifies the region of the regional instance template. + --instance-termination-action=INSTANCE_TERMINATION_ACTION Specifies the termination action that will be taken upon VM preemption. INSTANCE_TERMINATION_ACTION must be one of: @@ -730,9 +734,6 @@ FLAGS The name of the source instance that the instance template will be created from. - You can override machine type and labels. Values of other flags will be - ignored and values from the source instance will be used instead. - --source-instance-zone=SOURCE_INSTANCE_ZONE Zone of the instance to operate on. Overrides the default compute/zone property value for this command invocation. @@ -751,6 +752,9 @@ FLAGS is also specified, subnet must be a subnetwork of the network specified by the --network flag. + --subnet-region=SUBNET_REGION + Specifies the region of the subnetwork. + --tags=TAG,[TAG,...] Specifies a list of tags to apply to the instance. These tags allow network firewall rules and routes to be applied to specified VM diff --git a/gcloud/alpha/compute/instance-templates/create-with-container b/gcloud/alpha/compute/instance-templates/create-with-container index cd57757f9..6799491df 100644 --- a/gcloud/alpha/compute/instance-templates/create-with-container +++ b/gcloud/alpha/compute/instance-templates/create-with-container @@ -38,8 +38,8 @@ SYNOPSIS [--private-network-ip=PRIVATE_NETWORK_IP] [--region=REGION] [--no-restart-on-failure] [--shielded-integrity-monitoring] [--shielded-secure-boot] [--shielded-vtpm] [--stack-type=STACK_TYPE] - [--subnet=SUBNET] [--tags=TAG,[TAG,...]] - [--address=ADDRESS | --no-address] + [--subnet=SUBNET] [--subnet-region=SUBNET_REGION] + [--tags=TAG,[TAG,...]] [--address=ADDRESS | --no-address] [--custom-cpu=CUSTOM_CPU --custom-memory=CUSTOM_MEMORY : --custom-extensions --custom-vm-type=CUSTOM_VM_TYPE] [--image-project=IMAGE_PROJECT --image=IMAGE @@ -641,6 +641,9 @@ FLAGS is also specified, subnet must be a subnetwork of the network specified by the --network flag. + --subnet-region=SUBNET_REGION + Specifies the region of the subnetwork. + --tags=TAG,[TAG,...] Specifies a list of tags to apply to the instance. These tags allow network firewall rules and routes to be applied to specified VM diff --git a/gcloud/alpha/compute/network-edge-security-services/create b/gcloud/alpha/compute/network-edge-security-services/create index f388a4dde..83d6ea3b5 100644 --- a/gcloud/alpha/compute/network-edge-security-services/create +++ b/gcloud/alpha/compute/network-edge-security-services/create @@ -65,5 +65,7 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. + access allowlist. This variant is also available: + + $ gcloud beta compute network-edge-security-services create diff --git a/gcloud/alpha/compute/network-edge-security-services/delete b/gcloud/alpha/compute/network-edge-security-services/delete index 152ed853b..487262885 100644 --- a/gcloud/alpha/compute/network-edge-security-services/delete +++ b/gcloud/alpha/compute/network-edge-security-services/delete @@ -38,5 +38,7 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. + access allowlist. This variant is also available: + + $ gcloud beta compute network-edge-security-services delete diff --git a/gcloud/alpha/compute/network-edge-security-services/describe b/gcloud/alpha/compute/network-edge-security-services/describe index 65f637404..9dc182549 100644 --- a/gcloud/alpha/compute/network-edge-security-services/describe +++ b/gcloud/alpha/compute/network-edge-security-services/describe @@ -39,5 +39,7 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. + access allowlist. This variant is also available: + + $ gcloud beta compute network-edge-security-services describe diff --git a/gcloud/alpha/compute/network-edge-security-services/help b/gcloud/alpha/compute/network-edge-security-services/help index 45e6804ff..03e52a817 100644 --- a/gcloud/alpha/compute/network-edge-security-services/help +++ b/gcloud/alpha/compute/network-edge-security-services/help @@ -43,5 +43,7 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. + access allowlist. This variant is also available: + + $ gcloud beta compute network-edge-security-services diff --git a/gcloud/alpha/compute/network-edge-security-services/list b/gcloud/alpha/compute/network-edge-security-services/list index 3c517c749..72e9bf432 100644 --- a/gcloud/alpha/compute/network-edge-security-services/list +++ b/gcloud/alpha/compute/network-edge-security-services/list @@ -74,5 +74,7 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. + access allowlist. This variant is also available: + + $ gcloud beta compute network-edge-security-services list diff --git a/gcloud/alpha/compute/network-edge-security-services/update b/gcloud/alpha/compute/network-edge-security-services/update index 16795dfc2..acbe493f8 100644 --- a/gcloud/alpha/compute/network-edge-security-services/update +++ b/gcloud/alpha/compute/network-edge-security-services/update @@ -65,5 +65,7 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. + access allowlist. This variant is also available: + + $ gcloud beta compute network-edge-security-services update diff --git a/gcloud/alpha/compute/network-firewall-policies/rules/create b/gcloud/alpha/compute/network-firewall-policies/rules/create index 909638033..9ed7c41f0 100644 --- a/gcloud/alpha/compute/network-firewall-policies/rules/create +++ b/gcloud/alpha/compute/network-firewall-policies/rules/create @@ -42,7 +42,7 @@ POSITIONAL ARGUMENTS REQUIRED FLAGS --action=ACTION Action to take if the request matches the match condition. ACTION must - be one of: allow, deny, goto_next. + be one of: allow, deny, goto_next, apply_profile_group. --firewall-policy=FIREWALL_POLICY Firewall policy ID with which to create rule. diff --git a/gcloud/alpha/compute/network-firewall-policies/rules/help b/gcloud/alpha/compute/network-firewall-policies/rules/help index 06198660a..d6e17c364 100644 --- a/gcloud/alpha/compute/network-firewall-policies/rules/help +++ b/gcloud/alpha/compute/network-firewall-policies/rules/help @@ -27,7 +27,7 @@ COMMANDS (ALPHA) Describes a Compute Engine network firewall policy rule. update - (ALPHA) Creates a Compute Engine network firewall policy rule. + (ALPHA) Updates a Compute Engine network firewall policy rule. NOTES This command is currently in alpha and might change without notice. If this diff --git a/gcloud/alpha/compute/network-firewall-policies/rules/update b/gcloud/alpha/compute/network-firewall-policies/rules/update index a0c30d24c..caccfcf21 100644 --- a/gcloud/alpha/compute/network-firewall-policies/rules/update +++ b/gcloud/alpha/compute/network-firewall-policies/rules/update @@ -1,5 +1,5 @@ NAME - gcloud alpha compute network-firewall-policies rules update - creates a + gcloud alpha compute network-firewall-policies rules update - updates a Compute Engine network firewall policy rule SYNOPSIS @@ -17,7 +17,7 @@ SYNOPSIS DESCRIPTION (ALPHA) gcloud alpha compute network-firewall-policies rules update is used - to create network firewall policy rules. + to update network firewall policy rules. EXAMPLES To update a rule with priority 10 in a global network firewall policy with @@ -39,7 +39,7 @@ REQUIRED FLAGS OPTIONAL FLAGS --action=ACTION Action to take if the request matches the match condition. ACTION must - be one of: allow, deny, goto_next. + be one of: allow, deny, goto_next, apply_profile_group. --description=DESCRIPTION An optional, textual description for the rule. diff --git a/gcloud/alpha/compute/os-config/troubleshoot b/gcloud/alpha/compute/os-config/troubleshoot index c67c8fb6d..ed59fe262 100644 --- a/gcloud/alpha/compute/os-config/troubleshoot +++ b/gcloud/alpha/compute/os-config/troubleshoot @@ -10,12 +10,20 @@ DESCRIPTION (ALPHA) gcloud alpha compute os-config troubleshoot troubleshoots issues with the setup of VM Manager on a specified VM instance - The troubleshoot command investigates the following issues with VM Manager: + The troubleshoot command investigates the following settings or + configurations for your VM Manager setup: + Checks if the OS Config API is enabled in the project. + Checks if the required metadata is set up correctly in the VM instance. + + Checks if the latest version of the OS Config agent is running on the VM + instance. + + + Checks if a service account is attached to the VM instance. + + + Checks if the VM Manager service agent is enabled. + EXAMPLES To troubleshoot an instance named my-instance in zone us-west1-a, run diff --git a/gcloud/alpha/compute/security-policies/update b/gcloud/alpha/compute/security-policies/update index 8d51151e2..2e0a229be 100644 --- a/gcloud/alpha/compute/security-policies/update +++ b/gcloud/alpha/compute/security-policies/update @@ -9,6 +9,7 @@ SYNOPSIS [--json-parsing=JSON_PARSING] [--layer7-ddos-defense-rule-visibility=VISIBILITY_TYPE] [--log-level=LOG_LEVEL] + [--network-ddos-protection=NETWORK_DDOS_PROTECTION] [--recaptcha-redirect-site-key=RECAPTCHA_REDIRECT_SITE_KEY] [--global | --region=REGION] [GCLOUD_WIDE_FLAG ...] @@ -53,6 +54,11 @@ FLAGS The level of detail to display for WAF logging. LOG_LEVEL must be one of: NORMAL, VERBOSE. + --network-ddos-protection=NETWORK_DDOS_PROTECTION + The DDoS protection level for network load balancing and instances with + external IPs. NETWORK_DDOS_PROTECTION must be one of: STANDARD, + ADVANCED. + --recaptcha-redirect-site-key=RECAPTCHA_REDIRECT_SITE_KEY The reCAPTCHA site key to be used for rules using the redirect action and the google-recaptcha redirect type under the security policy. diff --git a/gcloud/alpha/compute/tpus/queued-resources/create b/gcloud/alpha/compute/tpus/queued-resources/create index c75f874a1..3ed89bea3 100644 --- a/gcloud/alpha/compute/tpus/queued-resources/create +++ b/gcloud/alpha/compute/tpus/queued-resources/create @@ -6,7 +6,7 @@ SYNOPSIS gcloud alpha compute tpus queued-resources create (QUEUED_RESOURCE : --zone=ZONE) --accelerator-type=ACCELERATOR_TYPE --node-id=[NODE_ID,...] --runtime-version=RUNTIME_VERSION [--async] - [--best-effort] [--guaranteed] [--reserved] + [--best-effort] [--guaranteed] [--internal-ips] [--reserved] [--valid-after-duration=VALID_AFTER_DURATION] [--valid-after-time=VALID_AFTER_TIME] [--valid-until-duration=VALID_UNTIL_DURATION] @@ -89,6 +89,11 @@ OPTIONAL FLAGS If provided, the Node requested here will only be scheduled at the 'guaranteed' tier. + --internal-ips + Indicates that the IP addresses for the node should be internal. The + default is that external IP addresses will be associated with the TPU + workers. + --reserved Specifies the request should be scheduled on reserved capacity. @@ -96,17 +101,21 @@ OPTIONAL FLAGS --valid-after-duration=VALID_AFTER_DURATION A duration before which the TPU must not be provisioned, relative to - the current time. + the current time. See $ gcloud topic datetimes for information on + duration formats. --valid-after-time=VALID_AFTER_TIME - An absolute time before which the TPU must not be provisioned. + An absolute time before which the TPU must not be provisioned. See $ + gcloud topic datetimes for information on duration formats. --valid-until-duration=VALID_UNTIL_DURATION A duration after which the TPU must not be provisioned, relative to the - current time. + current time. See $ gcloud topic datetimes for information on duration + formats. --valid-until-time=VALID_UNTIL_TIME - An absolute time after which resources must not be created. + An absolute time after which resources must not be created. See $ + gcloud topic datetimes for information on duration formats. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/alpha/compute/tpus/tpu-vm/help b/gcloud/alpha/compute/tpus/tpu-vm/help index ffe707921..4b5b47682 100644 --- a/gcloud/alpha/compute/tpus/tpu-vm/help +++ b/gcloud/alpha/compute/tpus/tpu-vm/help @@ -52,6 +52,9 @@ COMMANDS scp (ALPHA) Copy files to and from a Cloud TPU VM via SCP. + simulate-maintenance-event + (ALPHA) Simulates a maintenance event on a Cloud TPU VM. + ssh (ALPHA) SSH into a Cloud TPU VM. diff --git a/gcloud/alpha/compute/tpus/tpu-vm/scp b/gcloud/alpha/compute/tpus/tpu-vm/scp index b8ef58a3a..75ec10966 100644 --- a/gcloud/alpha/compute/tpus/tpu-vm/scp +++ b/gcloud/alpha/compute/tpus/tpu-vm/scp @@ -4,8 +4,9 @@ NAME SYNOPSIS gcloud alpha compute tpus tpu-vm scp [[USER@]INSTANCE:]SRC - [[[USER@]INSTANCE:]SRC ...] [[USER@]INSTANCE:]DEST [--compress] - [--dry-run] [--force-key-file-overwrite] [--plain] [--recurse] + [[[USER@]INSTANCE:]SRC ...] [[USER@]INSTANCE:]DEST + [--batch-size=BATCH_SIZE; default="all"] [--compress] [--dry-run] + [--force-key-file-overwrite] [--plain] [--recurse] [--scp-flag=SCP_FLAG] [--ssh-key-file=SSH_KEY_FILE] [--strict-host-key-checking=STRICT_HOST_KEY_CHECKING] [--worker=WORKER; default="0"] [--zone=ZONE] @@ -43,6 +44,18 @@ POSITIONAL ARGUMENTS Specifies a destination for the source files. FLAGS + --batch-size=BATCH_SIZE; default="all" + Batch size for simultaneous command execution. When using a + comma-separated list (e.g. '1,4,6') or a range (e.g. '1-3') or ``all`` + keyword in --worker flag, it executes the command concurrently in + groups of the batch size. This flag takes a value greater than 0 to + specify the batch size to control the concurrent connections that can + be established with the TPU workers, or the special keyword ``all`` to + allow the concurrent command executions on all the specified workers in + --worker flag. Maximum value of this flag should not be more than the + number of specified workers, otherwise the value will be treated as + ``--batch-size=all``. + --compress Enable compression. diff --git a/gcloud/alpha/compute/tpus/tpu-vm/simulate-maintenance-event b/gcloud/alpha/compute/tpus/tpu-vm/simulate-maintenance-event new file mode 100644 index 000000000..38d05ee0a --- /dev/null +++ b/gcloud/alpha/compute/tpus/tpu-vm/simulate-maintenance-event @@ -0,0 +1,74 @@ +NAME + gcloud alpha compute tpus tpu-vm simulate-maintenance-event - simulates a + maintenance event on a Cloud TPU VM + +SYNOPSIS + gcloud alpha compute tpus tpu-vm simulate-maintenance-event + (TPU : --zone=ZONE) [--workers=[WORKERS,...]] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) For testing the resilience of applications build on top of Cloud + TPUs. + +EXAMPLES + The following command simulates a maintenance event on workers 0 and 1 in + the Cloud TPU named "my-tpu" in zone "us-central1-b" of the default + project. + + $ gcloud alpha compute tpus tpu-vm simulate-maintenance-event \ + my-tpu --zone=us-central1-b --workers=0,1 + +POSITIONAL ARGUMENTS + Tpu resource - The Cloud TPU on which to simulate maintenance. 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 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 + --workers=[WORKERS,...] + The zero-based ID(s) of workers on which to simulate maintenance. By + default, only the first (ID 0) worker VM is flagged for maintenance. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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/v2alpha1 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. + diff --git a/gcloud/alpha/compute/tpus/tpu-vm/ssh b/gcloud/alpha/compute/tpus/tpu-vm/ssh index 977adc18c..43ec1ce99 100644 --- a/gcloud/alpha/compute/tpus/tpu-vm/ssh +++ b/gcloud/alpha/compute/tpus/tpu-vm/ssh @@ -2,7 +2,8 @@ NAME gcloud alpha compute tpus tpu-vm ssh - SSH into a Cloud TPU VM SYNOPSIS - gcloud alpha compute tpus tpu-vm ssh [USER@]TPU [--dry-run] + gcloud alpha compute tpus tpu-vm ssh [USER@]TPU + [--batch-size=BATCH_SIZE; default="all"] [--dry-run] [--force-key-file-overwrite] [--plain] [--ssh-flag=SSH_FLAG] [--ssh-key-file=SSH_KEY_FILE] [--strict-host-key-checking=STRICT_HOST_KEY_CHECKING] @@ -55,6 +56,18 @@ POSITIONAL ARGUMENTS --zone=us-central1-a -- -vvv -L 80:%TPU%:80 FLAGS + --batch-size=BATCH_SIZE; default="all" + Batch size for simultaneous command execution. When using a + comma-separated list (e.g. '1,4,6') or a range (e.g. '1-3') or ``all`` + keyword in --worker flag, it executes the command concurrently in + groups of the batch size. This flag takes a value greater than 0 to + specify the batch size to control the concurrent connections that can + be established with the TPU workers, or the special keyword ``all`` to + allow the concurrent command executions on all the specified workers in + --worker flag. Maximum value of this flag should not be more than the + number of specified workers, otherwise the value will be treated as + ``--batch-size=all``. + --dry-run Print the equivalent scp/ssh command that would be run to stdout, instead of executing it. diff --git a/gcloud/alpha/config/list b/gcloud/alpha/config/list index 69e102a46..829be4a37 100644 --- a/gcloud/alpha/config/list +++ b/gcloud/alpha/config/list @@ -8,10 +8,10 @@ SYNOPSIS DESCRIPTION (ALPHA) gcloud alpha config list lists all properties of the active - configuration. These include the account used to authorize access to the - Cloud Platform, the current Cloud Platform project, and the default Compute - Engine region and zone, if set. See gcloud topic configurations for more - about configurations. + configuration. These include the account used to authorize access to Google + Cloud, the current Google Cloud project, and the default Compute Engine + region and zone, if set. See gcloud topic configurations for more about + configurations. EXAMPLES To list the project property in the core section, run: @@ -22,6 +22,10 @@ EXAMPLES $ gcloud alpha config list compute/zone + To list all the properties in the compute section, run: + + $ gcloud alpha config list compute/ + To list all the properties, run: $ gcloud alpha config list --all diff --git a/gcloud/alpha/container/backup-restore/restore-plans/create b/gcloud/alpha/container/backup-restore/restore-plans/create index b94fe579a..644cc2655 100644 --- a/gcloud/alpha/container/backup-restore/restore-plans/create +++ b/gcloud/alpha/container/backup-restore/restore-plans/create @@ -11,7 +11,8 @@ SYNOPSIS | --selected-namespaces=[SELECTED_NAMESPACES,...]) [--async] [--description=DESCRIPTION] [--labels=[KEY=VALUE,...]] [--substitution-rules-file=SUBSTITUTION_RULES_FILE] - [--volume-data-restore-policy=VOLUME_DATA_RESTORE_POLICY] + [--volume-data-restore-policy=VOLUME_DATA_RESTORE_POLICY; + default="no-volume-data-restoration"] [--cluster-resource-conflict-policy=CLUSTER_RESOURCE_CONFLICT_POLICY --cluster-resource-restore-scope=[CLUSTER_RESOURCE_RESTORE_SCOPE, ...]] [GCLOUD_WIDE_FLAG ...] @@ -83,8 +84,25 @@ REQUIRED FLAGS --namespaced-resource-restore-mode=NAMESPACED_RESOURCE_RESTORE_MODE Define how to handle restore-time conflicts for namespaced resources. - NAMESPACED_RESOURCE_RESTORE_MODE must be one of: delete-and-restore, - fail-on-conflict, namespaced-resource-restore-mode-unspecified. + NAMESPACED_RESOURCE_RESTORE_MODE must be one of: + + delete-and-restore + When conflicting top-level resources (either Namespaces or + ProtectedApplications, depending upon the scope) are encountered, + this will first trigger a delete of the conflicting resource AND + ALL OF ITS REFERENCED RESOURCES (e.g., all resources in the + Namespace or all resources referenced by the ProtectedApplication) + before restoring the resources from the Backup. This mode should + only be used when you are intending to revert some portion of a + cluster to an earlier state. + + fail-on-conflict + If conflicting top-level resources (either Namespaces or + ProtectedApplications, depending upon the scope) are encountered at + the beginning of a restore process, the Restore will fail. If a + conflict occurs during the restore process itself (e.g., because an + out of band process creates conflicting resources), a conflict will + be reported. Exactly one of these must be specified: @@ -121,17 +139,44 @@ OPTIONAL FLAGS applied to resources from the source backup before they are created in the target cluster. - --volume-data-restore-policy=VOLUME_DATA_RESTORE_POLICY - Define how data is populated for restored volumes. - VOLUME_DATA_RESTORE_POLICY must be one of: no-volume-data-restoration, - restore-volume-data-from-backup, reuse-volume-handle-from-backup, - volume-data-restore-policy-unspecified. + --volume-data-restore-policy=VOLUME_DATA_RESTORE_POLICY; default="no-volume-data-restoration" + Define how data is populated for restored volumes. If this flag is not + specified, 'no-volume-data-restoration' will be used. + VOLUME_DATA_RESTORE_POLICY must be one of: + + no-volume-data-restoration + Selecting 'no-volume-data-restoration' means PV will not be + restored. The restoration will ONLY restore selected PVCs and + expects corresponding Kubernetes controllers to either dynamically + provision blank PVs or bind them to pre-provisioned PVs created + out-of-band. + + restore-volume-data-from-backup + Selecting 'restore-volume-data-from-backup' means a new PV will be + restored using the corresponding volume backup data in the Backup. + + reuse-volume-handle-from-backup + Selecting 'reuse-volume-handle-from-backup' means a PV will be + pre-provisioned using the volume handle of the original PV in the + Backup. --cluster-resource-conflict-policy=CLUSTER_RESOURCE_CONFLICT_POLICY Define how to handle restore-time conflicts for cluster-scoped resources. CLUSTER_RESOURCE_CONFLICT_POLICY must be one of: - cluster-resource-conflict-policy-unspecified, use-backup-version, - use-existing-version. + + use-backup-version + Selecting 'use-existing-version' means deleting the existing + version of the conflicting resources before re-creating them from + the Backup. + + Note that this is a dangerous option which could cause + unintentional data loss if used inappropriately. For example, + deleting a CRD will cause Kubernetes to delete all CRs of that + type. + + use-existing-version + Selecting 'use-existing-version' means no conflicting resources + will be restored. --cluster-resource-restore-scope=[CLUSTER_RESOURCE_RESTORE_SCOPE,...] List of cluster-scoped resource types to be restored. Not specifying diff --git a/gcloud/alpha/container/backup-restore/restore-plans/update b/gcloud/alpha/container/backup-restore/restore-plans/update index e956b83d3..196fe28aa 100644 --- a/gcloud/alpha/container/backup-restore/restore-plans/update +++ b/gcloud/alpha/container/backup-restore/restore-plans/update @@ -9,7 +9,8 @@ SYNOPSIS [--namespaced-resource-restore-mode=NAMESPACED_RESOURCE_RESTORE_MODE] [--substitution-rules-file=SUBSTITUTION_RULES_FILE] [--update-labels=[KEY=VALUE,...]] - [--volume-data-restore-policy=VOLUME_DATA_RESTORE_POLICY] + [--volume-data-restore-policy=VOLUME_DATA_RESTORE_POLICY; + default="no-volume-data-restoration"] [--all-namespaces | --selected-applications=SELECTED_APPLICATIONS | --selected-namespaces=[SELECTED_NAMESPACES,...]] [--clear-labels | --remove-labels=[KEY,...]] @@ -74,8 +75,25 @@ FLAGS --namespaced-resource-restore-mode=NAMESPACED_RESOURCE_RESTORE_MODE Define how to handle restore-time conflicts for namespaced resources. - NAMESPACED_RESOURCE_RESTORE_MODE must be one of: delete-and-restore, - fail-on-conflict, namespaced-resource-restore-mode-unspecified. + NAMESPACED_RESOURCE_RESTORE_MODE must be one of: + + delete-and-restore + When conflicting top-level resources (either Namespaces or + ProtectedApplications, depending upon the scope) are encountered, + this will first trigger a delete of the conflicting resource AND + ALL OF ITS REFERENCED RESOURCES (e.g., all resources in the + Namespace or all resources referenced by the ProtectedApplication) + before restoring the resources from the Backup. This mode should + only be used when you are intending to revert some portion of a + cluster to an earlier state. + + fail-on-conflict + If conflicting top-level resources (either Namespaces or + ProtectedApplications, depending upon the scope) are encountered at + the beginning of a restore process, the Restore will fail. If a + conflict occurs during the restore process itself (e.g., because an + out of band process creates conflicting resources), a conflict will + be reported. --substitution-rules-file=SUBSTITUTION_RULES_FILE If provided, defines a set of resource transformations that will be @@ -91,11 +109,26 @@ FLAGS contain only hyphens (-), underscores (_), lowercase characters, and numbers. - --volume-data-restore-policy=VOLUME_DATA_RESTORE_POLICY - Define how data is populated for restored volumes. - VOLUME_DATA_RESTORE_POLICY must be one of: no-volume-data-restoration, - restore-volume-data-from-backup, reuse-volume-handle-from-backup, - volume-data-restore-policy-unspecified. + --volume-data-restore-policy=VOLUME_DATA_RESTORE_POLICY; default="no-volume-data-restoration" + Define how data is populated for restored volumes. If this flag is not + specified, 'no-volume-data-restoration' will be used. + VOLUME_DATA_RESTORE_POLICY must be one of: + + no-volume-data-restoration + Selecting 'no-volume-data-restoration' means PV will not be + restored. The restoration will ONLY restore selected PVCs and + expects corresponding Kubernetes controllers to either dynamically + provision blank PVs or bind them to pre-provisioned PVs created + out-of-band. + + restore-volume-data-from-backup + Selecting 'restore-volume-data-from-backup' means a new PV will be + restored using the corresponding volume backup data in the Backup. + + reuse-volume-handle-from-backup + Selecting 'reuse-volume-handle-from-backup' means a PV will be + pre-provisioned using the volume handle of the original PV in the + Backup. At most one of these can be specified: @@ -135,8 +168,20 @@ FLAGS --cluster-resource-conflict-policy=CLUSTER_RESOURCE_CONFLICT_POLICY Define how to handle restore-time conflicts for cluster-scoped resources. CLUSTER_RESOURCE_CONFLICT_POLICY must be one of: - cluster-resource-conflict-policy-unspecified, use-backup-version, - use-existing-version. + + use-backup-version + Selecting 'use-existing-version' means deleting the existing + version of the conflicting resources before re-creating them from + the Backup. + + Note that this is a dangerous option which could cause + unintentional data loss if used inappropriately. For example, + deleting a CRD will cause Kubernetes to delete all CRs of that + type. + + use-existing-version + Selecting 'use-existing-version' means no conflicting resources + will be restored. --cluster-resource-restore-scope=[CLUSTER_RESOURCE_RESTORE_SCOPE,...] List of cluster-scoped resource types to be restored. Not specifying diff --git a/gcloud/alpha/container/clusters/create b/gcloud/alpha/container/clusters/create index b70976946..942e2eafd 100644 --- a/gcloud/alpha/container/clusters/create +++ b/gcloud/alpha/container/clusters/create @@ -18,7 +18,7 @@ SYNOPSIS [--default-max-pods-per-node=DEFAULT_MAX_PODS_PER_NODE] [--disable-default-snat] [--disable-pod-cidr-overprovision] [--disk-size=DISK_SIZE] [--disk-type=DISK_TYPE] [--enable-autorepair] - [--no-enable-autoupgrade] [--enable-binauthz] [--enable-cloud-logging] + [--no-enable-autoupgrade] [--enable-cloud-logging] [--enable-cloud-monitoring] [--enable-cloud-run-alpha] [--enable-confidential-nodes] [--enable-cost-allocation] [--enable-dataplane-v2] [--enable-gke-oidc] [--enable-gvnic] @@ -58,6 +58,8 @@ SYNOPSIS [--tags=TAG,[TAG,...]] [--threads-per-core=THREADS_PER_CORE] [--workload-metadata=WORKLOAD_METADATA] [--workload-pool=WORKLOAD_POOL] [--additional-zones=ZONE,[ZONE,...] | --node-locations=ZONE,[ZONE,...]] + [--binauthz-evaluation-mode=BINAUTHZ_EVALUATION_MODE + | --enable-binauthz] [--cluster-dns=CLUSTER_DNS --cluster-dns-domain=CLUSTER_DNS_DOMAIN --cluster-dns-scope=CLUSTER_DNS_SCOPE] [[--enable-autoprovisioning @@ -78,7 +80,9 @@ SYNOPSIS --enable-autoprovisioning-autoupgrade [--max-accelerator=[type=TYPE,count=COUNT,...] : --min-accelerator=[type=TYPE,count=COUNT,...]]]]] - [--enable-autoscaling --max-nodes=MAX_NODES --min-nodes=MIN_NODES] + [--enable-autoscaling --location-policy=LOCATION_POLICY + --max-nodes=MAX_NODES --min-nodes=MIN_NODES + --total-max-nodes=TOTAL_MAX_NODES --total-min-nodes=TOTAL_MIN_NODES] [--enable-master-authorized-networks --master-authorized-networks=NETWORK,[NETWORK,...]] [--enable-network-egress-metering @@ -347,9 +351,6 @@ FLAGS Enabled by default, use --no-enable-autoupgrade to disable. - --enable-binauthz - Enable Binary Authorization for this cluster. - --enable-cloud-logging (DEPRECATED) Automatically send logs from the cluster to the Google Cloud Logging API. @@ -713,14 +714,16 @@ FLAGS --monitoring=[COMPONENT,...] Set the components that have monitoring enabled. Valid component values - are: SYSTEM, WORKLOAD (Deprecated), NONE + are: SYSTEM, WORKLOAD (Deprecated), NONE,API_SERVER, + CONTROLLER_MANAGER, SCHEDULER For more information, look at https://cloud.google.com/stackdriver/docs/solutions/gke/installing#available-metrics Examples: - $ gcloud alpha container clusters create --monitoring=SYSTEM + $ gcloud alpha container clusters create \ + --monitoring=SYSTEM,API_SERVER $ gcloud alpha container clusters create --monitoring=NONE --network=NETWORK @@ -1100,6 +1103,21 @@ FLAGS --zone us-central1-a \ --node-locations us-central1-a,us-central1-b + Flags for Binary Authorization: + + At most one of these can be specified: + + --binauthz-evaluation-mode=BINAUTHZ_EVALUATION_MODE + Enable Binary Authorization for this cluster. + BINAUTHZ_EVALUATION_MODE must be one of: DISABLED, + PROJECT_SINGLETON_POLICY_ENFORCE. + + --enable-binauthz + (DEPRECATED) Enable Binary Authorization for this cluster. + + The --enable-binauthz flag is deprecated. Please use + --binauthz-evaluation-mode instead. + ClusterDNS --cluster-dns=CLUSTER_DNS @@ -1370,6 +1388,17 @@ FLAGS Enables autoscaling in the node pool specified by --node-pool or the default node pool if --node-pool is not provided. + --location-policy=LOCATION_POLICY + Location policy specifies the algorithm used when scaling-up the node + pool. + + ▸ BALANCED - Is a best effort policy that aims to balance the sizes + of available zones. + ▸ ANY - Instructs the cluster autoscaler to prioritize utilization + of unused reservations, and reduces preemption risk for Spot VMs. + + LOCATION_POLICY must be one of: BALANCED, ANY. + --max-nodes=MAX_NODES Maximum number of nodes per zone in the node pool. @@ -1384,6 +1413,20 @@ FLAGS --node-pool (or default node pool if unspecified) can scale. Ignored unless --enable-autoscaling is also specified. + --total-max-nodes=TOTAL_MAX_NODES + Maximum number of all nodes in the node pool. + + Maximum number of all nodes to which the node pool specified by + --node-pool (or default node pool if unspecified) can scale. Ignored + unless --enable-autoscaling is also specified. + + --total-min-nodes=TOTAL_MIN_NODES + Minimum number of all nodes in the node pool. + + Minimum number of all nodes to which the node pool specified by + --node-pool (or default node pool if unspecified) can scale. Ignored + unless --enable-autoscaling is also specified. + Master Authorized Networks --enable-master-authorized-networks diff --git a/gcloud/alpha/container/clusters/create-auto b/gcloud/alpha/container/clusters/create-auto index 8f9ba5886..99e38febf 100644 --- a/gcloud/alpha/container/clusters/create-auto +++ b/gcloud/alpha/container/clusters/create-auto @@ -5,6 +5,7 @@ NAME SYNOPSIS gcloud alpha container clusters create-auto NAME [--async] [--autoprovisioning-network-tags=TAGS,[TAGS,...]] + [--binauthz-evaluation-mode=BINAUTHZ_EVALUATION_MODE] [--boot-disk-kms-key=BOOT_DISK_KMS_KEY] [--cluster-ipv4-cidr=CLUSTER_IPV4_CIDR] [--cluster-secondary-range-name=NAME] @@ -60,6 +61,13 @@ FLAGS https://cloud.google.com/sdk/gcloud/reference/compute/firewall-rules/create for examples. + Flags for Binary Authorization: + + --binauthz-evaluation-mode=BINAUTHZ_EVALUATION_MODE + Enable Binary Authorization for this cluster. + BINAUTHZ_EVALUATION_MODE must be one of: DISABLED, + PROJECT_SINGLETON_POLICY_ENFORCE. + --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/clusters/update b/gcloud/alpha/container/clusters/update index a310d0022..c5ec8609e 100644 --- a/gcloud/alpha/container/clusters/update +++ b/gcloud/alpha/container/clusters/update @@ -10,7 +10,7 @@ SYNOPSIS | --database-encryption-key=DATABASE_ENCRYPTION_KEY | --disable-database-encryption | --disable-default-snat | --disable-workload-identity | --enable-autoscaling - | --enable-binauthz | --enable-cost-allocation | --enable-gke-oidc + | --enable-cost-allocation | --enable-gke-oidc | --enable-identity-service | --enable-image-streaming | --enable-intra-node-visibility | --enable-l4-ilb-subsetting | --enable-legacy-authorization @@ -31,7 +31,9 @@ SYNOPSIS | --update-addons=[ADDON=ENABLED|DISABLED,...] | --update-labels=[KEY=VALUE,...] | --workload-pool=WORKLOAD_POOL | --additional-zones=[ZONE,...] | --node-locations=ZONE,[ZONE,...] - | --clear-maintenance-window | --remove-maintenance-exclusion=NAME + | --binauthz-evaluation-mode=BINAUTHZ_EVALUATION_MODE + | --enable-binauthz | --clear-maintenance-window + | --remove-maintenance-exclusion=NAME | [--add-maintenance-exclusion-end=TIME_STAMP : --add-maintenance-exclusion-name=NAME --add-maintenance-exclusion-scope=SCOPE @@ -71,7 +73,10 @@ SYNOPSIS [--cloud-run-config=[load-balancer-type=EXTERNAL,...]] [--istio-config=[auth=MTLS_PERMISSIVE,...]] [--master-authorized-networks=NETWORK,[NETWORK,...]] - [--node-pool=NODE_POOL] [--max-nodes=MAX_NODES --min-nodes=MIN_NODES] + [--node-pool=NODE_POOL] + [--location-policy=LOCATION_POLICY --max-nodes=MAX_NODES + --min-nodes=MIN_NODES + --total-max-nodes=TOTAL_MAX_NODES --total-min-nodes=TOTAL_MIN_NODES] [--region=REGION | --zone=ZONE, -z ZONE] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -182,9 +187,6 @@ REQUIRED FLAGS Enables autoscaling in the node pool specified by --node-pool or the default node pool if --node-pool is not provided. - --enable-binauthz - Enable Binary Authorization for this cluster. - --enable-cost-allocation Enable the cost management feature. @@ -552,6 +554,21 @@ REQUIRED FLAGS --zone us-central1-a \ --node-locations us-central1-a,us-central1-b + Flags for Binary Authorization: + + At most one of these can be specified: + + --binauthz-evaluation-mode=BINAUTHZ_EVALUATION_MODE + Enable Binary Authorization for this cluster. + BINAUTHZ_EVALUATION_MODE must be one of: DISABLED, + PROJECT_SINGLETON_POLICY_ENFORCE. + + --enable-binauthz + (DEPRECATED) Enable Binary Authorization for this cluster. + + The --enable-binauthz flag is deprecated. Please use + --binauthz-evaluation-mode instead. + At most one of these can be specified: --clear-maintenance-window @@ -999,14 +1016,16 @@ REQUIRED FLAGS --monitoring=[COMPONENT,...] Set the components that have monitoring enabled. Valid component - values are: SYSTEM, WORKLOAD (Deprecated), NONE + values are: SYSTEM, WORKLOAD (Deprecated), NONE,API_SERVER, + CONTROLLER_MANAGER, SCHEDULER For more information, look at https://cloud.google.com/stackdriver/docs/solutions/gke/installing#available-metrics Examples: - $ gcloud alpha container clusters update --monitoring=SYSTEM + $ gcloud alpha container clusters update \ + --monitoring=SYSTEM,API_SERVER $ gcloud alpha container clusters update --monitoring=NONE --logging-service=LOGGING_SERVICE @@ -1102,6 +1121,17 @@ OPTIONAL FLAGS Cluster autoscaling + --location-policy=LOCATION_POLICY + Location policy specifies the algorithm used when scaling-up the node + pool. + + ▸ BALANCED - Is a best effort policy that aims to balance the sizes + of available zones. + ▸ ANY - Instructs the cluster autoscaler to prioritize utilization + of unused reservations, and reduces preemption risk for Spot VMs. + + LOCATION_POLICY must be one of: BALANCED, ANY. + --max-nodes=MAX_NODES Maximum number of nodes per zone in the node pool. @@ -1116,6 +1146,20 @@ OPTIONAL FLAGS --node-pool (or default node pool if unspecified) can scale. Ignored unless --enable-autoscaling is also specified. + --total-max-nodes=TOTAL_MAX_NODES + Maximum number of all nodes in the node pool. + + Maximum number of all nodes to which the node pool specified by + --node-pool (or default node pool if unspecified) can scale. Ignored + unless --enable-autoscaling is also specified. + + --total-min-nodes=TOTAL_MIN_NODES + Minimum number of all nodes in the node pool. + + Minimum number of all nodes to which the node pool specified by + --node-pool (or default node pool if unspecified) can scale. Ignored + unless --enable-autoscaling is also specified. + At most one of these can be specified: --region=REGION diff --git a/gcloud/alpha/container/fleet/memberships/register b/gcloud/alpha/container/fleet/memberships/register index e39493ec0..d8e974b34 100644 --- a/gcloud/alpha/container/fleet/memberships/register +++ b/gcloud/alpha/container/fleet/memberships/register @@ -3,7 +3,8 @@ NAME a fleet SYNOPSIS - gcloud alpha container fleet memberships register MEMBERSHIP_NAME + gcloud alpha container fleet memberships register + [[MEMBERSHIP_NAME] --location=LOCATION] (--gke-cluster=LOCATION/CLUSTER_NAME | --gke-uri=GKE_URI | [--context=CONTEXT : --kubeconfig=KUBECONFIG]) (--service-account-key-file=SERVICE_ACCOUNT_KEY_FILE @@ -37,11 +38,11 @@ DESCRIPTION corresponds to a service account that has been granted gkehub.connect permissions. - If the cluster is already registered to another Fleet, the registration is + If the cluster is already registered to another fleet, the registration is not successful. Rerunning this command against the same cluster with the same - MEMBERSHIP_NAME and target GKEFleet is successful and upgrades the Connect + MEMBERSHIP_NAME and target fleet is successful and upgrades the Connect Agent if a new agent is available. EXAMPLES @@ -117,9 +118,35 @@ EXAMPLES --service-account-key-file=/tmp/keyfile.json POSITIONAL ARGUMENTS - MEMBERSHIP_NAME - The membership name that you choose to uniquely represents the cluster - being registered on the fleet. + Membership resource - Membership resource name. 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 MEMBERSHIP_NAME on the command line with a fully + specified name; + ◆ provide the argument --membership on the command line with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + [MEMBERSHIP_NAME] + ID of the membership or fully qualified identifier for the + membership. To set the membership attribute: + ▸ provide the argument MEMBERSHIP_NAME on the command line; + ▸ provide the argument --membership on the command line. + + --location=LOCATION + The location for the membership resource, e.g. us-central1. If not + specified, defaults to global. Not supported for GKE clusters, whose + membership location will be the location of the cluster. + + To set the location attribute: + ▸ provide the argument MEMBERSHIP_NAME on the command line with a + fully specified name; + ▸ provide the argument --membership on the command line with a + fully specified name; + ▸ provide the argument --location on the command line; + ▸ set the property gkehub/location. REQUIRED FLAGS Cluster identifier. diff --git a/gcloud/alpha/container/fleet/memberships/unregister b/gcloud/alpha/container/fleet/memberships/unregister index bd28043ca..6e813bbbe 100644 --- a/gcloud/alpha/container/fleet/memberships/unregister +++ b/gcloud/alpha/container/fleet/memberships/unregister @@ -3,7 +3,8 @@ NAME from Fleet SYNOPSIS - gcloud alpha container fleet memberships unregister MEMBERSHIP_NAME + gcloud alpha container fleet memberships unregister + [[MEMBERSHIP_NAME] --location=LOCATION] (--gke-cluster=LOCATION/CLUSTER_NAME | --gke-uri=GKE_URI | [--context=CONTEXT : --kubeconfig=KUBECONFIG]) [GCLOUD_WIDE_FLAG ...] @@ -29,7 +30,7 @@ DESCRIPTION To register a GKE cluster use --gke-cluster or --gke-uri flag (no --kubeconfig flag is required). - To only delete the Fleet membership resource, consider using the command: + To only delete the Fleet Membership resource, consider using the command: gcloud alpha container fleet memberships delete. This command is intended to delete stale Fleet Membership resources as doing so on a fully registered cluster will skip some of the steps above and orphan in-cluster @@ -58,10 +59,34 @@ EXAMPLES my-membership --gke-cluster=my-cluster-region-or-zone/my-cluster POSITIONAL ARGUMENTS - MEMBERSHIP_NAME - The membership name that corresponds to the cluster being unregistered. - To get list of all the memberships on the Fleet, consider using the - command: gcloud alpha container fleet memberships list. + Membership resource - Membership resource name. 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 MEMBERSHIP_NAME on the command line with a fully + specified name; + ◆ provide the argument --membership on the command line with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + [MEMBERSHIP_NAME] + ID of the membership or fully qualified identifier for the + membership. To set the membership attribute: + ▸ provide the argument MEMBERSHIP_NAME on the command line; + ▸ provide the argument --membership on the command line. + + --location=LOCATION + The location of the membership resource, e.g. us-central1. If not + specified, defaults to global. + + To set the location attribute: + ▸ provide the argument MEMBERSHIP_NAME on the command line with a + fully specified name; + ▸ provide the argument --membership on the command line with a + fully specified name; + ▸ provide the argument --location on the command line; + ▸ set the property gkehub/location. REQUIRED FLAGS Cluster identifier. diff --git a/gcloud/alpha/container/hub/memberships/register b/gcloud/alpha/container/hub/memberships/register index 5afa5576d..4dcc47023 100644 --- a/gcloud/alpha/container/hub/memberships/register +++ b/gcloud/alpha/container/hub/memberships/register @@ -3,7 +3,8 @@ NAME fleet SYNOPSIS - gcloud alpha container hub memberships register MEMBERSHIP_NAME + gcloud alpha container hub memberships register + [[MEMBERSHIP_NAME] --location=LOCATION] (--gke-cluster=LOCATION/CLUSTER_NAME | --gke-uri=GKE_URI | [--context=CONTEXT : --kubeconfig=KUBECONFIG]) (--service-account-key-file=SERVICE_ACCOUNT_KEY_FILE @@ -37,11 +38,11 @@ DESCRIPTION corresponds to a service account that has been granted gkehub.connect permissions. - If the cluster is already registered to another Fleet, the registration is + If the cluster is already registered to another fleet, the registration is not successful. Rerunning this command against the same cluster with the same - MEMBERSHIP_NAME and target GKEFleet is successful and upgrades the Connect + MEMBERSHIP_NAME and target fleet is successful and upgrades the Connect Agent if a new agent is available. EXAMPLES @@ -117,9 +118,35 @@ EXAMPLES --service-account-key-file=/tmp/keyfile.json POSITIONAL ARGUMENTS - MEMBERSHIP_NAME - The membership name that you choose to uniquely represents the cluster - being registered on the fleet. + Membership resource - Membership resource name. 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 MEMBERSHIP_NAME on the command line with a fully + specified name; + ◆ provide the argument --membership on the command line with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + [MEMBERSHIP_NAME] + ID of the membership or fully qualified identifier for the + membership. To set the membership attribute: + ▸ provide the argument MEMBERSHIP_NAME on the command line; + ▸ provide the argument --membership on the command line. + + --location=LOCATION + The location for the membership resource, e.g. us-central1. If not + specified, defaults to global. Not supported for GKE clusters, whose + membership location will be the location of the cluster. + + To set the location attribute: + ▸ provide the argument MEMBERSHIP_NAME on the command line with a + fully specified name; + ▸ provide the argument --membership on the command line with a + fully specified name; + ▸ provide the argument --location on the command line; + ▸ set the property gkehub/location. REQUIRED FLAGS Cluster identifier. diff --git a/gcloud/alpha/container/hub/memberships/unregister b/gcloud/alpha/container/hub/memberships/unregister index 5658adfb1..e8b214142 100644 --- a/gcloud/alpha/container/hub/memberships/unregister +++ b/gcloud/alpha/container/hub/memberships/unregister @@ -3,7 +3,8 @@ NAME from Fleet SYNOPSIS - gcloud alpha container hub memberships unregister MEMBERSHIP_NAME + gcloud alpha container hub memberships unregister + [[MEMBERSHIP_NAME] --location=LOCATION] (--gke-cluster=LOCATION/CLUSTER_NAME | --gke-uri=GKE_URI | [--context=CONTEXT : --kubeconfig=KUBECONFIG]) [GCLOUD_WIDE_FLAG ...] @@ -29,7 +30,7 @@ DESCRIPTION To register a GKE cluster use --gke-cluster or --gke-uri flag (no --kubeconfig flag is required). - To only delete the Fleet membership resource, consider using the command: + To only delete the Fleet Membership resource, consider using the command: gcloud alpha container hub memberships delete. This command is intended to delete stale Fleet Membership resources as doing so on a fully registered cluster will skip some of the steps above and orphan in-cluster resources @@ -58,10 +59,34 @@ EXAMPLES --gke-cluster=my-cluster-region-or-zone/my-cluster POSITIONAL ARGUMENTS - MEMBERSHIP_NAME - The membership name that corresponds to the cluster being unregistered. - To get list of all the memberships on the Fleet, consider using the - command: gcloud alpha container hub memberships list. + Membership resource - Membership resource name. 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 MEMBERSHIP_NAME on the command line with a fully + specified name; + ◆ provide the argument --membership on the command line with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + [MEMBERSHIP_NAME] + ID of the membership or fully qualified identifier for the + membership. To set the membership attribute: + ▸ provide the argument MEMBERSHIP_NAME on the command line; + ▸ provide the argument --membership on the command line. + + --location=LOCATION + The location of the membership resource, e.g. us-central1. If not + specified, defaults to global. + + To set the location attribute: + ▸ provide the argument MEMBERSHIP_NAME on the command line with a + fully specified name; + ▸ provide the argument --membership on the command line with a + fully specified name; + ▸ provide the argument --location on the command line; + ▸ set the property gkehub/location. REQUIRED FLAGS Cluster identifier. diff --git a/gcloud/alpha/container/node-pools/create b/gcloud/alpha/container/node-pools/create index 54a3cf2d3..4db0a085c 100644 --- a/gcloud/alpha/container/node-pools/create +++ b/gcloud/alpha/container/node-pools/create @@ -34,7 +34,9 @@ SYNOPSIS [--tags=TAG,[TAG,...]] [--threads-per-core=THREADS_PER_CORE] [--workload-metadata=WORKLOAD_METADATA] [--create-pod-ipv4-range=[KEY=VALUE,...] | --pod-ipv4-range=NAME] - [--enable-autoscaling --max-nodes=MAX_NODES --min-nodes=MIN_NODES] + [--enable-autoscaling --location-policy=LOCATION_POLICY + --max-nodes=MAX_NODES --min-nodes=MIN_NODES + --total-max-nodes=TOTAL_MAX_NODES --total-min-nodes=TOTAL_MIN_NODES] [--ephemeral-storage=[local-ssd-count=LOCAL-SSD-COUNT] | --local-ssd-count=LOCAL_SSD_COUNT | --local-ssd-volumes=[[count=COUNT], @@ -606,6 +608,17 @@ FLAGS Enables autoscaling in the node pool specified by --node-pool or the default node pool if --node-pool is not provided. + --location-policy=LOCATION_POLICY + Location policy specifies the algorithm used when scaling-up the node + pool. + + ▸ BALANCED - Is a best effort policy that aims to balance the sizes + of available zones. + ▸ ANY - Instructs the cluster autoscaler to prioritize utilization + of unused reservations, and reduces preemption risk for Spot VMs. + + LOCATION_POLICY must be one of: BALANCED, ANY. + --max-nodes=MAX_NODES Maximum number of nodes per zone in the node pool. @@ -620,6 +633,20 @@ FLAGS --node-pool (or default node pool if unspecified) can scale. Ignored unless --enable-autoscaling is also specified. + --total-max-nodes=TOTAL_MAX_NODES + Maximum number of all nodes in the node pool. + + Maximum number of all nodes to which the node pool specified by + --node-pool (or default node pool if unspecified) can scale. Ignored + unless --enable-autoscaling is also specified. + + --total-min-nodes=TOTAL_MIN_NODES + Minimum number of all nodes in the node pool. + + Minimum number of all nodes to which the node pool specified by + --node-pool (or default node pool if unspecified) can scale. Ignored + unless --enable-autoscaling is also specified. + At most one of these can be specified: --ephemeral-storage=[local-ssd-count=LOCAL-SSD-COUNT] diff --git a/gcloud/alpha/container/node-pools/update b/gcloud/alpha/container/node-pools/update index 645918092..6c431b1b5 100644 --- a/gcloud/alpha/container/node-pools/update +++ b/gcloud/alpha/container/node-pools/update @@ -11,8 +11,10 @@ SYNOPSIS | --node-taints=[NODE_TAINT,...] | --system-config-from-file=SYSTEM_CONFIG_FROM_FILE | --tags=[TAG,...] | --workload-metadata=WORKLOAD_METADATA - | --enable-autoprovisioning - --enable-autoscaling --max-nodes=MAX_NODES --min-nodes=MIN_NODES + | --enable-autoprovisioning --enable-autoscaling + --location-policy=LOCATION_POLICY --max-nodes=MAX_NODES + --min-nodes=MIN_NODES + --total-max-nodes=TOTAL_MAX_NODES --total-min-nodes=TOTAL_MIN_NODES | --enable-autorepair --enable-autoupgrade | --enable-blue-green-upgrade --enable-surge-upgrade --max-surge-upgrade=MAX_SURGE_UPGRADE @@ -220,6 +222,18 @@ REQUIRED FLAGS Enables autoscaling in the node pool specified by --node-pool or the default node pool if --node-pool is not provided. + --location-policy=LOCATION_POLICY + Location policy specifies the algorithm used when scaling-up the + node pool. + + ▫ BALANCED - Is a best effort policy that aims to balance the + sizes of available zones. + ▫ ANY - Instructs the cluster autoscaler to prioritize + utilization of unused reservations, and reduces preemption risk + for Spot VMs. + + LOCATION_POLICY must be one of: BALANCED, ANY. + --max-nodes=MAX_NODES Maximum number of nodes per zone in the node pool. @@ -234,6 +248,20 @@ REQUIRED FLAGS by --node-pool (or default node pool if unspecified) can scale. Ignored unless --enable-autoscaling is also specified. + --total-max-nodes=TOTAL_MAX_NODES + Maximum number of all nodes in the node pool. + + Maximum number of all nodes to which the node pool specified by + --node-pool (or default node pool if unspecified) can scale. + Ignored unless --enable-autoscaling is also specified. + + --total-min-nodes=TOTAL_MIN_NODES + Minimum number of all nodes in the node pool. + + Minimum number of all nodes to which the node pool specified by + --node-pool (or default node pool if unspecified) can scale. + Ignored unless --enable-autoscaling is also specified. + Node management --enable-autorepair diff --git a/gcloud/alpha/dataplex/tasks/create b/gcloud/alpha/dataplex/tasks/create index a57f3786a..3138e2fc8 100644 --- a/gcloud/alpha/dataplex/tasks/create +++ b/gcloud/alpha/dataplex/tasks/create @@ -5,6 +5,7 @@ SYNOPSIS gcloud alpha dataplex tasks create (TASK : --lake=LAKE --location=LOCATION) (--execution-service-account=EXECUTION_SERVICE_ACCOUNT : --execution-args=EXECUTION_ARGS + --execution-project=EXECUTION_PROJECT --kms-key=KMS_KEY --max-job-execution-lifetime=MAX_JOB_EXECUTION_LIFETIME) ((--spark-main-class=SPARK_MAIN_CLASS | --spark-main-jar-file-uri=SPARK_MAIN_JAR_FILE_URI @@ -15,6 +16,7 @@ SYNOPSIS --spark-file-uris=[SPARK_FILE_URIS,...] --batch-executors-count=BATCH_EXECUTORS_COUNT --batch-max-executors-count=BATCH_MAX_EXECUTORS_COUNT + --container-image=CONTAINER_IMAGE --container-image-java-jars=[CONTAINER_IMAGE_JAVA_JARS,...] --container-image-properties=CONTAINER_IMAGE_PROPERTIES --container-image-python-packages=[CONTAINER_IMAGE_PYTHON_PACKAGES, @@ -128,6 +130,15 @@ REQUIRED FLAGS keys being present in the args, then TASK_ARGS will be passed as the last argument. + --execution-project=EXECUTION_PROJECT + The project in which jobs are run. By default, the project containing + the Lake is used. If a project is provided, the + --execution-service-account must belong to this same project. + + --kms-key=KMS_KEY + The Cloud KMS key to use for encryption, of the form: + projects/{project_number}/locations/{location_id}/keyRings/{key-ring-name}/cryptoKeys/{key-name} + --max-job-execution-lifetime=MAX_JOB_EXECUTION_LIFETIME The maximum duration before the job execution expires. @@ -182,6 +193,9 @@ REQUIRED FLAGS Container Image Runtime Configuration. + --container-image=CONTAINER_IMAGE + Optional custom container image for the job. + --container-image-java-jars=[CONTAINER_IMAGE_JAVA_JARS,...] A list of Java JARS to add to the classpath. Valid input includes Cloud Storage URIs to Jar binaries. For example, diff --git a/gcloud/alpha/dataplex/tasks/update b/gcloud/alpha/dataplex/tasks/update index 155e54302..83de24e57 100644 --- a/gcloud/alpha/dataplex/tasks/update +++ b/gcloud/alpha/dataplex/tasks/update @@ -6,13 +6,15 @@ SYNOPSIS [--async] [--description=DESCRIPTION] [--display-name=DISPLAY_NAME] [--update-labels=[KEY=VALUE,...]] [--clear-labels | --remove-labels=[KEY,...]] - [--execution-args=EXECUTION_ARGS + [--execution-args=EXECUTION_ARGS --execution-project=EXECUTION_PROJECT --execution-service-account=EXECUTION_SERVICE_ACCOUNT + --kms-key=KMS_KEY --max-job-execution-lifetime=MAX_JOB_EXECUTION_LIFETIME] [--spark-archive-uris=[SPARK_ARCHIVE_URIS,...] --spark-file-uris=[SPARK_FILE_URIS,...] --batch-executors-count=BATCH_EXECUTORS_COUNT --batch-max-executors-count=BATCH_MAX_EXECUTORS_COUNT + --container-image=CONTAINER_IMAGE --container-image-java-jars=[CONTAINER_IMAGE_JAVA_JARS,...] --container-image-properties=CONTAINER_IMAGE_PROPERTIES --container-image-python-packages=[CONTAINER_IMAGE_PYTHON_PACKAGES, @@ -132,10 +134,19 @@ FLAGS case of other keys being present in the args, then TASK_ARGS will be passed as the last argument. + --execution-project=EXECUTION_PROJECT + The project in which jobs are run. By default, the project containing + the Lake is used. If a project is provided, the + --execution-service-account must belong to this same project. + --execution-service-account=EXECUTION_SERVICE_ACCOUNT Service account to use to execute a task. If not provided, the default Compute service account for the project is used. + --kms-key=KMS_KEY + The Cloud KMS key to use for encryption, of the form: + projects/{project_number}/locations/{location_id}/keyRings/{key-ring-name}/cryptoKeys/{key-name} + --max-job-execution-lifetime=MAX_JOB_EXECUTION_LIFETIME The maximum duration before the job execution expires. @@ -161,6 +172,9 @@ FLAGS Container Image Runtime Configuration. + --container-image=CONTAINER_IMAGE + Optional custom container image for the job. + --container-image-java-jars=[CONTAINER_IMAGE_JAVA_JARS,...] A list of Java JARS to add to the classpath. Valid input includes Cloud Storage URIs to Jar binaries. For example, diff --git a/gcloud/alpha/dataproc/clusters/gke/create b/gcloud/alpha/dataproc/clusters/gke/create index 21cdda024..f21f18ca6 100644 --- a/gcloud/alpha/dataproc/clusters/gke/create +++ b/gcloud/alpha/dataproc/clusters/gke/create @@ -135,82 +135,42 @@ OPTIONAL FLAGS The following KEYs must be specified: - KEY Type Example Description - name string `my-node-pool` Name of the node pool. - roles repeated string `default;spark-driver` Roles that this node - pool should perform. - Valid values are - `default`, - `controller`, - `spark-driver`, - `spark-executor`. + ----------------------------------------------------------------------------------------------------------- + KEY Type Example Description + ------ ---------------- ------------------------ ---------------------------------------------------------- + name string `my-node-pool` Name of the node pool. - The following KEYs may be specified. + roles repeated string `default;spark-driver` Roles that this node pool should perform. Valid values are + `default`, `controller`, `spark-driver`, `spark-executor`. + ----------------------------------------------------------------------------------------------------------- - KEY Type Example Description - machineType string `n1-standard-8` Compute - Engine - machine type - to use. - preemptible boolean `false` If true, - then this - node pool - uses - preemptible - VMs. This - cannot be - true on the - node pool - with the - `controllers - ` role (or - `default` - role if - `controllers - ` role is - not - specified). - localSsdCount int `2` The number - of local - SSDs to - attach to - each node. - accelerator repeated string `nvidia-tesla-a100=1` Accelerators - to attach to - each node. - In the - format - NAME=COUNT. - minCpuPlatform string `Intel Skylake` Minimum CPU - platform for - each node. - locations repeated string `us-west1-a;us-west1-c` Zones within - the location - of the GKE - cluster. All - `--pools` - flags for a - single - Dataproc - cluster must - have - identical - locations. - min int `0` Minimum - number of - nodes per - zone that - this node - pool can - scale down - to. - max int `10` Maximum - number of - nodes per - zone that - this node - pool can - scale up to. + The following KEYs may be specified: + + ---------------------------------------------------------------------------------------------------------------------------------------------------------------- + KEY Type Example Description + --------------- ---------------- --------------------------------------------- --------------------------------------------------------------------------------- + machineType string `n1-standard-8` Compute Engine machine type to use. + + preemptible boolean `false` If true, then this node pool uses preemptible VMs. + This cannot be true on the node pool with the `controllers` role + (or `default` role if `controllers` role is not specified). + + localSsdCount int `2` The number of local SSDs to attach to each node. + + accelerator repeated string `nvidia-tesla-a100=1` Accelerators to attach to each node. In the format NAME=COUNT. + + minCpuPlatform string `Intel Skylake` Minimum CPU platform for each node. + + bootDiskKmsKey string `projects/project-id/locations/us-central1 The Customer Managed Encryption Key (CMEK) used to encrypt + /keyRings/keyRing-name/cryptoKeys/key-name` the boot disk attached to each node in the node pool. + + locations repeated string `us-west1-a;us-west1-c` Zones within the location of the GKE cluster. + All `--pools` flags for a single Dataproc cluster must have identical locations. + + min int `0` Minimum number of nodes per zone that this node pool can scale down to. + + max int `10` Maximum number of nodes per zone that this node pool can scale up to. + ---------------------------------------------------------------------------------------------------------------------------------------------------------------- --properties=[PREFIX:PROPERTY=VALUE,...] Specifies configuration properties for installed packages, such as diff --git a/gcloud/alpha/deploy/targets/rollback b/gcloud/alpha/deploy/targets/rollback index 7548df767..6aaf6c874 100644 --- a/gcloud/alpha/deploy/targets/rollback +++ b/gcloud/alpha/deploy/targets/rollback @@ -4,7 +4,8 @@ NAME SYNOPSIS gcloud alpha deploy targets rollback (TARGET : --region=REGION) - --delivery-pipeline=DELIVERY_PIPELINE [--description=DESCRIPTION] + --delivery-pipeline=DELIVERY_PIPELINE [--annotations=[KEY=VALUE,...]] + [--description=DESCRIPTION] [--labels=[KEY=VALUE,...]] [--release=RELEASE] [--rollout-id=ROLLOUT_ID] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -52,9 +53,31 @@ REQUIRED FLAGS The name of the Cloud Deploy delivery pipeline OPTIONAL FLAGS + --annotations=[KEY=VALUE,...] + Annotations to apply to the rollback. Annotations take the form of + key/value string pairs. + + Examples: + + Add annotations: + + $ gcloud alpha deploy targets rollback \ + --annotations="from_target=test,status=stable" + --description=DESCRIPTION Description of rollout created during a rollback. + --labels=[KEY=VALUE,...] + Labels to apply to the rollback. Labels take the form of key/value + string pairs. + + Examples: + + Add labels: + + $ gcloud alpha deploy targets rollback \ + --labels="commit=abc123,author=foo" + --release=RELEASE Name of the release to rollback to. diff --git a/gcloud/alpha/functions/deploy b/gcloud/alpha/functions/deploy index b13f954eb..04abef749 100644 --- a/gcloud/alpha/functions/deploy +++ b/gcloud/alpha/functions/deploy @@ -175,7 +175,7 @@ FLAGS ◆ nodejs14: Node.js 14 ◆ nodejs16: Node.js 16 ◆ php74: PHP 7.4 - ◆ php81: PHP 8.1 (preview) + ◆ php81: PHP 8.1 ◆ python37: Python 3.7 ◆ python38: Python 3.8 ◆ python39: Python 3.9 diff --git a/gcloud/alpha/functions/help b/gcloud/alpha/functions/help index 0ed48beab..e8d97c3e1 100644 --- a/gcloud/alpha/functions/help +++ b/gcloud/alpha/functions/help @@ -25,6 +25,9 @@ GROUPS regions (ALPHA) List regions available to Google Cloud Functions. + runtimes + (ALPHA) List runtimes available to Google Cloud Functions. + COMMANDS COMMAND is one of the following: diff --git a/gcloud/alpha/vmware/locations/help b/gcloud/alpha/functions/runtimes/help similarity index 50% rename from gcloud/alpha/vmware/locations/help rename to gcloud/alpha/functions/runtimes/help index af7142e43..5ae4daf63 100644 --- a/gcloud/alpha/vmware/locations/help +++ b/gcloud/alpha/functions/runtimes/help @@ -1,12 +1,12 @@ NAME - gcloud alpha vmware locations - list locations in Google Cloud VMware - Engine + gcloud alpha functions runtimes - list runtimes available to Google Cloud + Functions SYNOPSIS - gcloud alpha vmware locations COMMAND [GCLOUD_WIDE_FLAG ...] + gcloud alpha functions runtimes COMMAND [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) List locations in Google Cloud VMware Engine. + (ALPHA) List runtimes available to Google Cloud Functions. GCLOUD WIDE FLAGS These flags are available to all commands: --help. @@ -17,11 +17,15 @@ COMMANDS COMMAND is one of the following: list - (ALPHA) List Google Cloud VMware Engine locations. + (ALPHA) List runtimes available to Google Cloud Functions. 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 functions runtimes + + $ gcloud beta functions runtimes diff --git a/gcloud/alpha/functions/runtimes/list b/gcloud/alpha/functions/runtimes/list new file mode 100644 index 000000000..fdde6be7b --- /dev/null +++ b/gcloud/alpha/functions/runtimes/list @@ -0,0 +1,72 @@ +NAME + gcloud alpha functions runtimes list - list runtimes available to Google + Cloud Functions + +SYNOPSIS + gcloud alpha functions runtimes list [--region=REGION] + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) List runtimes available to Google Cloud Functions. + +EXAMPLES + To list the available runtimes, run: + + $ gcloud alpha functions runtimes list + +FLAGS + --region=REGION + Only show runtimes within the region. Overrides the default + functions/region property value for this command invocation. + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + + --uri + Print a list of resource URIs instead of the default output, and change + the command output to a list of URIs. If this flag is used with + --format, the formatting is applied on this URI list. To display URIs + alongside other keys instead, use the uri() transform. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. These variants are also available: + + $ gcloud functions runtimes list + + $ gcloud beta functions runtimes list + diff --git a/gcloud/alpha/ids/help b/gcloud/alpha/ids/help index 0b76961c0..1281a4998 100644 --- a/gcloud/alpha/ids/help +++ b/gcloud/alpha/ids/help @@ -19,6 +19,9 @@ GROUPS endpoints (ALPHA) Create and manage Cloud IDS Endpoints. + operations + (ALPHA) Manage Cloud IDS Operations. + 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/vmware/operations/describe b/gcloud/alpha/ids/operations/cancel similarity index 57% rename from gcloud/alpha/vmware/operations/describe rename to gcloud/alpha/ids/operations/cancel index 3e4f46f84..f42421720 100644 --- a/gcloud/alpha/vmware/operations/describe +++ b/gcloud/alpha/ids/operations/cancel @@ -1,30 +1,25 @@ NAME - gcloud alpha vmware operations describe - describe a Google Cloud VMware - Engine operation + gcloud alpha ids operations cancel - cancel a Cloud IDS operation SYNOPSIS - gcloud alpha vmware operations describe (OPERATION : --location=LOCATION) + gcloud alpha ids operations cancel (OPERATION : --zone=ZONE) [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) Describe a VMware Engine operation. An operation contains - information about the status of a previous request. + (ALPHA) Cancel a Cloud IDS operation. EXAMPLES - To get details about an operation on a private cloud with the operation ID - operation-111-222-333-444, run: + To cancel an operation called my-operation in project my-project and zone + us-central1-a, run: - $ gcloud alpha vmware operations describe \ - operation-111-222-333-444 --location=us-central1 \ - --project=my-project + $ gcloud alpha ids operations cancel my-operation \ + --project=my-project --zone=us-central1-a - Or: + OR - $ gcloud alpha vmware operations describe \ - operation-111-222-333-444 --location=us-central1 - - In the second example, the location is taken from gcloud property - compute/zone. + $ gcloud alpha ids operations cancel \ + projects/myproject/locations/us-central1-a/endpoints/\ + my-operation POSITIONAL ARGUMENTS Operation resource - operation. The arguments in this group can be used to @@ -33,8 +28,8 @@ POSITIONAL ARGUMENTS project attribute: ◆ provide the argument operation on the command line with a fully specified name; - ◆ set the property core/project; - ◆ provide the argument --project on the command line. + ◆ provide the argument --project on the command line; + ◆ set the property core/project. This must be specified. @@ -46,12 +41,11 @@ POSITIONAL ARGUMENTS This positional must be specified if any of the other arguments in this group are specified. - --location=LOCATION - Zone of the private cloud or cluster. To set the location attribute: + --zone=ZONE + The zone of the operation. To set the zone attribute: ▸ provide the argument operation on the command line with a fully specified name; - ▸ provide the argument --location on the command line; - ▸ set the property compute/zone. + ▸ provide the argument --zone on the command line. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/alpha/ids/operations/describe b/gcloud/alpha/ids/operations/describe new file mode 100644 index 000000000..de9f6c220 --- /dev/null +++ b/gcloud/alpha/ids/operations/describe @@ -0,0 +1,63 @@ +NAME + gcloud alpha ids operations describe - describe a Cloud IDS operation + +SYNOPSIS + gcloud alpha ids operations describe (OPERATION : --zone=ZONE) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Describe a Cloud IDS operation. + +EXAMPLES + To get a description of an operation called my-operation in project + my-project and zone us-central1-a, run: + + $ gcloud alpha ids operations describe my-operation \ + --project=my-project --zone=us-central1-a + + OR + + $ gcloud alpha ids operations describe \ + projects/myproject/locations/us-central1-a/operations/\ + my-operation + +POSITIONAL ARGUMENTS + Operation resource - operation. 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 operation 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. + + OPERATION + ID of the operation or fully qualified identifier for the operation. + To set the operation attribute: + ▸ provide the argument operation on the command line. + + This positional must be specified if any of the other arguments in + this group are specified. + + --zone=ZONE + The zone of the operation. To set the zone attribute: + ▸ provide the argument operation on the command line with a fully + specified name; + ▸ provide the argument --zone on the command line. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/ids/operations/help b/gcloud/alpha/ids/operations/help new file mode 100644 index 000000000..2d809f3eb --- /dev/null +++ b/gcloud/alpha/ids/operations/help @@ -0,0 +1,40 @@ +NAME + gcloud alpha ids operations - manage Cloud IDS Operations + +SYNOPSIS + gcloud alpha ids operations COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) The gcloud alpha ids operations group lets you manage Cloud IDS + Operations, including canceling, waiting for complition, listing ,and + describing their properties. + + More information on Cloud IDS Operations can be found at + https://cloud.google.com/intrusion-detection-system + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + cancel + (ALPHA) Cancel a Cloud IDS operation. + + describe + (ALPHA) Describe a Cloud IDS operation. + + list + (ALPHA) List Cloud IDS operations. + + wait + (ALPHA) Wait for a Cloud IDS operation to complete. + +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/ids/operations/list b/gcloud/alpha/ids/operations/list new file mode 100644 index 000000000..9cdafcd89 --- /dev/null +++ b/gcloud/alpha/ids/operations/list @@ -0,0 +1,81 @@ +NAME + gcloud alpha ids operations list - list Cloud IDS operations + +SYNOPSIS + gcloud alpha ids operations list [--project=PROJECT_ID] + [--zone=ZONE; default="-"] [--filter=EXPRESSION] [--limit=LIMIT] + [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) List Cloud IDS operation in a project. + +EXAMPLES + $ gcloud alpha ids operations list --project=my-project + + The project is automatically read from the core/project property if it is + defined. + +COMMONLY USED FLAGS + --project=PROJECT_ID + The Google Cloud project ID to use for this invocation. If omitted, + then the current project is assumed; the current project can be listed + using gcloud config list --format='text(core.project)' and can be set + using gcloud config set project PROJECTID. + + --project and its fallback core/project property play two roles in the + invocation. It specifies the project of the resource to operate on. It + also specifies the project for API enablement check, quota, and + billing. To specify a different project for quota and billing, use + --billing-project or billing/quota_project property. + +FLAGS + --zone=ZONE; default="-" + The zone of an operation + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + + --uri + Print a list of resource URIs instead of the default output, and change + the command output to a list of URIs. If this flag is used with + --format, the formatting is applied on this URI list. To display URIs + alongside other keys instead, use the uri() transform. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/ids/operations/wait b/gcloud/alpha/ids/operations/wait new file mode 100644 index 000000000..0bf42b4e9 --- /dev/null +++ b/gcloud/alpha/ids/operations/wait @@ -0,0 +1,71 @@ +NAME + gcloud alpha ids operations wait - wait for a Cloud IDS operation to + complete + +SYNOPSIS + gcloud alpha ids operations wait (OPERATION : --zone=ZONE) + [--max-wait=MAX_WAIT; default="60m"] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Wait for a Cloud IDS operation to complete. + +EXAMPLES + To get a description of an operation called my-operation in project + my-project and zone us-central1-a, run: + + $ gcloud alpha ids operations wait my-operation \ + --project=my-project --zone=us-central1-a + + OR + + $ gcloud alpha ids operations wait \ + projects/myproject/locations/us-central1-a/operations/\ + my-operation + +POSITIONAL ARGUMENTS + Operation resource - operation. 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 operation 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. + + OPERATION + ID of the operation or fully qualified identifier for the operation. + To set the operation attribute: + ▸ provide the argument operation on the command line. + + This positional must be specified if any of the other arguments in + this group are specified. + + --zone=ZONE + The zone of the operation. To set the zone attribute: + ▸ provide the argument operation on the command line with a fully + specified name; + ▸ provide the argument --zone on the command line. + +FLAGS + --max-wait=MAX_WAIT; default="60m" + Time to synchronously wait for the operation to complete, after which + the operation continues asynchronously. Ignored if --no-async isn't + specified. See $ gcloud topic datetimes for information on time + formats. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/kms/keys/versions/import b/gcloud/alpha/kms/keys/versions/import index 65ffcd915..3ac762777 100644 --- a/gcloud/alpha/kms/keys/versions/import +++ b/gcloud/alpha/kms/keys/versions/import @@ -6,9 +6,8 @@ SYNOPSIS gcloud alpha kms keys versions import --algorithm=ALGORITHM --import-job=IMPORT_JOB [--key=KEY] [--keyring=KEYRING] [--location=LOCATION] [--public-key-file=PUBLIC_KEY_FILE] - [--rsa-aes-wrapped-key-file=RSA_AES_WRAPPED_KEY_FILE] [--target-key-file=TARGET_KEY_FILE] [--version=VERSION] - [GCLOUD_WIDE_FLAG ...] + [--wrapped-key-file=WRAPPED_KEY_FILE] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Imports wrapped key material into a new version within an existing @@ -24,7 +23,7 @@ EXAMPLES $ gcloud alpha kms keys versions import --location=global \ --keyring=fellowship --key=frodo --import-job=strider \ - --rsa-aes-wrapped-key-file=path/to/target/key \ + --wrapped-key-file=path/to/target/key \ --algorithm=google-symmetric-encryption REQUIRED FLAGS @@ -58,20 +57,20 @@ OPTIONAL FLAGS Location of the keyring. --public-key-file=PUBLIC_KEY_FILE - Optional path to the public key of the ImportJob, used to wrap the key - for import. If missing, the public key will be fetched on your behalf. - - --rsa-aes-wrapped-key-file=RSA_AES_WRAPPED_KEY_FILE - Path to the wrapped RSA AES key file to import. + Path to the public key of the ImportJob, used to wrap the key for + import. If missing, the public key will be fetched on your behalf. --target-key-file=TARGET_KEY_FILE - Optional path to the unwrapped target key to import into a Cloud KMS - key version. If specified, the key will be securely wrapped before + Path to the unwrapped target key to import into a Cloud KMS key + version. If specified, the key will be securely wrapped before transmission to Google. --version=VERSION Version to re-import into. Omit this field for first-time import. + --wrapped-key-file=WRAPPED_KEY_FILE + Path to the RSA/RSA+AES wrapped key file to import. + 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/ml/speech/recognize b/gcloud/alpha/ml/speech/recognize index d2bdac7f1..ccc3f8eb7 100644 --- a/gcloud/alpha/ml/speech/recognize +++ b/gcloud/alpha/ml/speech/recognize @@ -117,6 +117,17 @@ OPTIONAL FLAGS audio that is not one of the specific audio models. For example, long-form audio. Ideally the audio is high-fidelity, recorded at a 16khz or greater sampling rate. + latest_long + Use this model for any kind of long form content such as media or + spontaneous speech and conversations. Consider using this model in + place of the video model, especially if the video model is not + available in your target language. You can also use this in place + of the default model. + latest_short + Use this model for short utterances that are a few seconds in + length. It is useful for trying to capture commands or other single + shot directed speech use cases. Consider using this model instead + of the command and search model. medical_conversation Best for audio that originated from a conversation between a medical provider and patient. diff --git a/gcloud/alpha/ml/speech/recognize-long-running b/gcloud/alpha/ml/speech/recognize-long-running index ae8d10ba2..26f18f55c 100644 --- a/gcloud/alpha/ml/speech/recognize-long-running +++ b/gcloud/alpha/ml/speech/recognize-long-running @@ -126,6 +126,17 @@ OPTIONAL FLAGS audio that is not one of the specific audio models. For example, long-form audio. Ideally the audio is high-fidelity, recorded at a 16khz or greater sampling rate. + latest_long + Use this model for any kind of long form content such as media or + spontaneous speech and conversations. Consider using this model in + place of the video model, especially if the video model is not + available in your target language. You can also use this in place + of the default model. + latest_short + Use this model for short utterances that are a few seconds in + length. It is useful for trying to capture commands or other single + shot directed speech use cases. Consider using this model instead + of the command and search model. medical_conversation Best for audio that originated from a conversation between a medical provider and patient. diff --git a/gcloud/alpha/recommender/insights/list b/gcloud/alpha/recommender/insights/list index 702449dea..66302840e 100644 --- a/gcloud/alpha/recommender/insights/list +++ b/gcloud/alpha/recommender/insights/list @@ -10,7 +10,7 @@ SYNOPSIS [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) This command will list all insights for a give cloud entity, + (ALPHA) This command will list all insights for a given cloud entity, location and insight type. Supported insight-types can be found here: https://cloud.google.com/recommender/docs/insights/insight-types. Currently the following cloud_entity_types are supported: project, billing_account, diff --git a/gcloud/alpha/run/jobs/create b/gcloud/alpha/run/jobs/create index 7228672da..4a2715f93 100644 --- a/gcloud/alpha/run/jobs/create +++ b/gcloud/alpha/run/jobs/create @@ -50,7 +50,7 @@ POSITIONAL ARGUMENTS REQUIRED FLAGS --image=IMAGE Name of the container image to deploy (e.g. - gcr.io/cloudrun/hello:latest). + us-docker.pkg.dev/cloudrun/container/job:latest). OPTIONAL FLAGS --args=[ARG,...] diff --git a/gcloud/alpha/run/jobs/update b/gcloud/alpha/run/jobs/update index 852321af5..42f5513a5 100644 --- a/gcloud/alpha/run/jobs/update +++ b/gcloud/alpha/run/jobs/update @@ -84,7 +84,7 @@ FLAGS --image=IMAGE Name of the container image to deploy (e.g. - gcr.io/cloudrun/hello:latest). + us-docker.pkg.dev/cloudrun/container/job:latest). --key=KEY CMEK key reference to encrypt the container with. diff --git a/gcloud/alpha/spanner/help b/gcloud/alpha/spanner/help index dec1bb124..ce586d06e 100644 --- a/gcloud/alpha/spanner/help +++ b/gcloud/alpha/spanner/help @@ -33,6 +33,9 @@ GROUPS rows (ALPHA) Manage the rows in Cloud Spanner databases. + samples + (ALPHA) Cloud Spanner sample apps. + 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/spanner/samples/backend b/gcloud/alpha/spanner/samples/backend new file mode 100644 index 000000000..a0ca45e49 --- /dev/null +++ b/gcloud/alpha/spanner/samples/backend @@ -0,0 +1,63 @@ +NAME + gcloud alpha spanner samples backend - run the backend gRPC service for the + given Cloud Spanner sample app + +SYNOPSIS + gcloud alpha spanner samples backend APPNAME --instance-id=INSTANCE_ID + [--database-id=DATABASE_ID] [--duration=DURATION; default="1h"] + [--port=PORT] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) This command starts the backend gRPC service for the given sample + application. Before starting the service, create the database and load any + initial data with: + + $ gcloud alpha spanner samples init APPNAME --instance-id=INSTANCE_ID + + After starting the service, generate traffic with: + + $ gcloud alpha spanner samples workload APPNAME + + To run all three steps together, use: + + $ gcloud alpha spanner samples run APPNAME --instance-id=INSTANCE_ID + +EXAMPLES + To run the backend gRPC service for the 'finance' sample app using instance + 'my-instance', run: + + $ gcloud alpha spanner samples backend finance \ + --instance-id=my-instance + +POSITIONAL ARGUMENTS + APPNAME + The sample app name, e.g. "finance". + +REQUIRED FLAGS + --instance-id=INSTANCE_ID + The Cloud Spanner instance ID for the sample app. + +OPTIONAL FLAGS + --database-id=DATABASE_ID + The Cloud Spanner database ID for the sample app. + + --duration=DURATION; default="1h" + Duration of time allowed to run before stopping the service. + + --port=PORT + Port on which to receive gRPC requests. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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/spanner/samples/help b/gcloud/alpha/spanner/samples/help new file mode 100644 index 000000000..8eed1dde2 --- /dev/null +++ b/gcloud/alpha/spanner/samples/help @@ -0,0 +1,48 @@ +NAME + gcloud alpha spanner samples - cloud Spanner sample apps + +SYNOPSIS + gcloud alpha spanner samples COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Each Cloud Spanner sample application includes a backend gRPC + service backed by a Cloud Spanner database and a workload script that + generates service traffic. + + These sample apps are open source and available at + https://github.com/GoogleCloudPlatform/cloud-spanner-samples. + + To see a list of available sample apps, run: + + $ gcloud spanner samples list + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + backend + (ALPHA) Run the backend gRPC service for the given Cloud Spanner sample + app. + + init + (ALPHA) Initialize a Cloud Spanner sample app. + + list + (ALPHA) List available sample applications. + + run + (ALPHA) Run the given Cloud Spanner sample app. + + workload + (ALPHA) Generate gRPC traffic for a given sample app's backend 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 + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/spanner/samples/init b/gcloud/alpha/spanner/samples/init new file mode 100644 index 000000000..3bc89a491 --- /dev/null +++ b/gcloud/alpha/spanner/samples/init @@ -0,0 +1,42 @@ +NAME + gcloud alpha spanner samples init - initialize a Cloud Spanner sample app + +SYNOPSIS + gcloud alpha spanner samples init APPNAME --instance-id=INSTANCE_ID + [--database-id=DATABASE_ID] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) This command creates a Cloud Spanner database in the given instance + for the sample app and loads any initial data required by the application. + +EXAMPLES + To initialize the 'finance' sample app using instance 'my-instance', run: + + $ gcloud alpha spanner samples init finance --instance-id=my-instance + +POSITIONAL ARGUMENTS + APPNAME + The sample app name, e.g. "finance". + +REQUIRED FLAGS + --instance-id=INSTANCE_ID + The Cloud Spanner instance ID for the sample app. + +OPTIONAL FLAGS + --database-id=DATABASE_ID + ID of the new Cloud Spanner database to create for the sample app. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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/vmware/locations/list b/gcloud/alpha/spanner/samples/list similarity index 88% rename from gcloud/alpha/vmware/locations/list rename to gcloud/alpha/spanner/samples/list index 17bf71973..04330c671 100644 --- a/gcloud/alpha/vmware/locations/list +++ b/gcloud/alpha/spanner/samples/list @@ -1,19 +1,13 @@ NAME - gcloud alpha vmware locations list - list Google Cloud VMware Engine - locations + gcloud alpha spanner samples list - list available sample applications SYNOPSIS - gcloud alpha vmware locations list [--filter=EXPRESSION] [--limit=LIMIT] + gcloud alpha spanner samples list [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) List supported VMware Engine locations. - -EXAMPLES - To list VMware Engine locations, run: - - $ gcloud alpha vmware locations list + (ALPHA) List available sample applications. LIST COMMAND FLAGS --filter=EXPRESSION diff --git a/gcloud/alpha/spanner/samples/run b/gcloud/alpha/spanner/samples/run new file mode 100644 index 000000000..f30cd97df --- /dev/null +++ b/gcloud/alpha/spanner/samples/run @@ -0,0 +1,60 @@ +NAME + gcloud alpha spanner samples run - run the given Cloud Spanner sample app + +SYNOPSIS + gcloud alpha spanner samples run APPNAME --instance-id=INSTANCE_ID + [--no-cleanup] [--database-id=DATABASE_ID] + [--duration=DURATION; default="1h"] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Each Cloud Spanner sample application includes a backend gRPC + service backed by a Cloud Spanner database and a workload script that + generates service traffic. This command creates and initializes the Cloud + Spanner database and runs both the backend service and workload script. + + These sample apps are open source and available at + https://github.com/GoogleCloudPlatform/cloud-spanner-samples. + + To see a list of available sample apps, run: + + $ gcloud alpha spanner samples list + +EXAMPLES + To run the 'finance' sample app using instance 'my-instance', run: + + $ gcloud alpha spanner samples run finance --instance-id=my-instance + +POSITIONAL ARGUMENTS + APPNAME + The sample app name, e.g. "finance". + +REQUIRED FLAGS + --instance-id=INSTANCE_ID + The Cloud Spanner instance ID for the sample app. + +OPTIONAL FLAGS + --cleanup + Delete the instance after running the sample app. Enabled by default, + use --no-cleanup to disable. + + --database-id=DATABASE_ID + ID of the new Cloud Spanner database to create for the sample app. + + --duration=DURATION; default="1h" + Duration of time allowed to run the sample app before stopping the + service. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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/spanner/samples/workload b/gcloud/alpha/spanner/samples/workload new file mode 100644 index 000000000..573a812dc --- /dev/null +++ b/gcloud/alpha/spanner/samples/workload @@ -0,0 +1,54 @@ +NAME + gcloud alpha spanner samples workload - generate gRPC traffic for a given + sample app's backend service + +SYNOPSIS + gcloud alpha spanner samples workload APPNAME + [--duration=DURATION; default="1h"] [--port=PORT] + [--target-qps=TARGET_QPS] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Before sending traffic to the backend service, create the database + and start the service with: + + $ gcloud alpha spanner samples init APPNAME --instance-id=INSTANCE_ID + $ gcloud alpha spanner samples backend APPNAME \ + --instance-id=INSTANCE_ID + + To run all three steps together, use: + + $ gcloud alpha spanner samples run APPNAME --instance-id=INSTANCE_ID + +EXAMPLES + To generate traffic for the 'finance' sample app, run: + + $ gcloud alpha spanner samples workload finance + +POSITIONAL ARGUMENTS + APPNAME + The sample app name, e.g. "finance". + +FLAGS + --duration=DURATION; default="1h" + Duration of time allowed to run before stopping the workload. + + --port=PORT + Port of the running backend service. + + --target-qps=TARGET_QPS + Target requests per second. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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/sql/instances/create b/gcloud/alpha/sql/instances/create index c0ba47b10..d89fbfec2 100644 --- a/gcloud/alpha/sql/instances/create +++ b/gcloud/alpha/sql/instances/create @@ -299,14 +299,12 @@ FLAGS implies that complexity check is not enabled. --[no-]password-policy-disallow-username-substring - Disallow username as a part of the password. This flag is available - only for PostgreSQL. Use --password-policy-disallow-username-substring - to enable and --no-password-policy-disallow-username-substring to - disable. + Disallow username as a part of the password. Use + --password-policy-disallow-username-substring to enable and + --no-password-policy-disallow-username-substring to disable. --password-policy-min-length=PASSWORD_POLICY_MIN_LENGTH - Minimum number of characters allowed in the password. This flag is - available only for PostgreSQL. + Minimum number of characters allowed in the password. --password-policy-password-change-interval=PASSWORD_POLICY_PASSWORD_CHANGE_INTERVAL Minimum interval after which the password can be changed, for example, @@ -316,7 +314,7 @@ FLAGS --password-policy-reuse-interval=PASSWORD_POLICY_REUSE_INTERVAL Number of previous passwords that cannot be reused. The valid range is - 0 to 100. This flag is available only for PostgreSQL. + 0 to 100. --replica-type=REPLICA_TYPE The type of replica to create. REPLICA_TYPE must be one of: READ, diff --git a/gcloud/alpha/sql/instances/patch b/gcloud/alpha/sql/instances/patch index 8c73a3962..e9810378d 100644 --- a/gcloud/alpha/sql/instances/patch +++ b/gcloud/alpha/sql/instances/patch @@ -246,14 +246,12 @@ FLAGS implies that complexity check is not enabled. --[no-]password-policy-disallow-username-substring - Disallow username as a part of the password. This flag is available - only for PostgreSQL. Use --password-policy-disallow-username-substring - to enable and --no-password-policy-disallow-username-substring to - disable. + Disallow username as a part of the password. Use + --password-policy-disallow-username-substring to enable and + --no-password-policy-disallow-username-substring to disable. --password-policy-min-length=PASSWORD_POLICY_MIN_LENGTH - Minimum number of characters allowed in the password. This flag is - available only for PostgreSQL. + Minimum number of characters allowed in the password. --password-policy-password-change-interval=PASSWORD_POLICY_PASSWORD_CHANGE_INTERVAL Minimum interval after which the password can be changed, for example, @@ -263,7 +261,7 @@ FLAGS --password-policy-reuse-interval=PASSWORD_POLICY_REUSE_INTERVAL Number of previous passwords that cannot be reused. The valid range is - 0 to 100. This flag is available only for PostgreSQL. + 0 to 100. --pricing-plan=PRICING_PLAN, -p PRICING_PLAN First Generation instances only. The pricing plan for this instance. diff --git a/gcloud/alpha/sql/users/create b/gcloud/alpha/sql/users/create index 58a15264f..3187ac4d7 100644 --- a/gcloud/alpha/sql/users/create +++ b/gcloud/alpha/sql/users/create @@ -6,6 +6,7 @@ SYNOPSIS [--async] [--host=HOST] [--password=PASSWORD] [--password-policy-allowed-failed-attempts=PASSWORD_POLICY_ALLOWED_FAILED_ATTEMPTS] [--[no-]password-policy-enable-failed-attempts-check] + [--[no-]password-policy-enable-password-verification] [--password-policy-password-expiration-duration=PASSWORD_POLICY_PASSWORD_EXPIRATION_DURATION] [--type=TYPE] [GCLOUD_WIDE_FLAG ...] @@ -40,18 +41,24 @@ OPTIONAL FLAGS --password-policy-allowed-failed-attempts=PASSWORD_POLICY_ALLOWED_FAILED_ATTEMPTS Number of failed login attempts allowed before a user is locked out. - This flag is currently not available. + This flag is available only for MySQL. --[no-]password-policy-enable-failed-attempts-check Enables the failed login attempts check if set to true. This flag is - currently not available. Use + available only for MySQL. Use --password-policy-enable-failed-attempts-check to enable and --no-password-policy-enable-failed-attempts-check to disable. + --[no-]password-policy-enable-password-verification + The current password must be specified when altering the password. This + flag is available only for MySQL. Use + --password-policy-enable-password-verification to enable and + --no-password-policy-enable-password-verification to disable. + --password-policy-password-expiration-duration=PASSWORD_POLICY_PASSWORD_EXPIRATION_DURATION - Expiration duration after a password is updated, for example, 2m for 2 - minutes. See gcloud topic datetimes for information on duration - formats. This flag is currently not available. + Expiration duration after a password is updated, for example, 2d for 2 + days. See gcloud topic datetimes for information on duration formats. + This flag is available only for MySQL. --type=TYPE Cloud SQL user's type. It determines the method to authenticate the diff --git a/gcloud/alpha/sql/users/set-password b/gcloud/alpha/sql/users/set-password index 1f78e3010..cf879284c 100644 --- a/gcloud/alpha/sql/users/set-password +++ b/gcloud/alpha/sql/users/set-password @@ -5,6 +5,7 @@ NAME SYNOPSIS gcloud alpha sql users set-password USERNAME --instance=INSTANCE, -i INSTANCE [--async] [--host=HOST] + [--discard-dual-password | --retain-password] [--password=PASSWORD | --prompt-for-password] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -33,6 +34,16 @@ OPTIONAL FLAGS help on how to do so, read: https://cloud.google.com/sql/docs/mysql/configure-ip + At most one of these can be specified: + + --discard-dual-password + Discard the user's secondary password. Cannot set password and set + this flag. This flag is only available for MySQL 8.0. + + --retain-password + Retain the old password when changing to the new password. Must set + password with this flag. This flag is only available for MySQL 8.0. + At most one of these can be specified: --password=PASSWORD diff --git a/gcloud/alpha/sql/users/set-password-policy b/gcloud/alpha/sql/users/set-password-policy index f42506aa4..5d871423b 100644 --- a/gcloud/alpha/sql/users/set-password-policy +++ b/gcloud/alpha/sql/users/set-password-policy @@ -7,6 +7,7 @@ SYNOPSIS INSTANCE [--async] [--clear-password-policy] [--host=HOST] [--password-policy-allowed-failed-attempts=PASSWORD_POLICY_ALLOWED_FAILED_ATTEMPTS] [--[no-]password-policy-enable-failed-attempts-check] + [--[no-]password-policy-enable-password-verification] [--password-policy-password-expiration-duration=PASSWORD_POLICY_PASSWORD_EXPIRATION_DURATION] [GCLOUD_WIDE_FLAG ...] @@ -56,18 +57,24 @@ OPTIONAL FLAGS --password-policy-allowed-failed-attempts=PASSWORD_POLICY_ALLOWED_FAILED_ATTEMPTS Number of failed login attempts allowed before a user is locked out. - This flag is currently not available. + This flag is available only for MySQL. --[no-]password-policy-enable-failed-attempts-check Enables the failed login attempts check if set to true. This flag is - currently not available. Use + available only for MySQL. Use --password-policy-enable-failed-attempts-check to enable and --no-password-policy-enable-failed-attempts-check to disable. + --[no-]password-policy-enable-password-verification + The current password must be specified when altering the password. This + flag is available only for MySQL. Use + --password-policy-enable-password-verification to enable and + --no-password-policy-enable-password-verification to disable. + --password-policy-password-expiration-duration=PASSWORD_POLICY_PASSWORD_EXPIRATION_DURATION - Expiration duration after a password is updated, for example, 2m for 2 - minutes. See gcloud topic datetimes for information on duration - formats. This flag is currently not available. + Expiration duration after a password is updated, for example, 2d for 2 + days. See gcloud topic datetimes for information on duration formats. + This flag is available only for MySQL. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/alpha/transfer/agents/install b/gcloud/alpha/transfer/agents/install index 3ef9c3234..8802fe2af 100644 --- a/gcloud/alpha/transfer/agents/install +++ b/gcloud/alpha/transfer/agents/install @@ -7,7 +7,7 @@ SYNOPSIS [--logs-directory=LOGS_DIRECTORY; default="/tmp"] [--memlock-limit=MEMLOCK_LIMIT; default=64000000] [--mount-directories=[MOUNT-DIRECTORIES,...]] [--proxy=PROXY] - [GCLOUD_WIDE_FLAG ...] + [--s3-compatible-mode] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Install Transfer Service agents to enable you to transfer data to @@ -84,6 +84,11 @@ OPTIONAL FLAGS double-wrapping requests in TLS encryption. Double-wrapped requests prevent the proxy server from sending valid outbound requests. + --s3-compatible-mode + Allow the agent to work with S3-compatible sources. This flag blocks + the agents ability to work with other source types (e.g. POSIX + filesystems). + 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/vmware/clusters/create b/gcloud/alpha/vmware/clusters/create deleted file mode 100644 index 963363619..000000000 --- a/gcloud/alpha/vmware/clusters/create +++ /dev/null @@ -1,108 +0,0 @@ -NAME - gcloud alpha vmware clusters create - create a Google Cloud VMware Engine - cluster - -SYNOPSIS - gcloud alpha vmware clusters create - (CLUSTER : --location=LOCATION --private-cloud=PRIVATE_CLOUD) - --node-count=NODE_COUNT --node-type=NODE_TYPE [--async] - [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (ALPHA) Create a cluster in a VMware Engine private cloud. Successful - creation of a cluster results in a cluster in READY state. Check the - progress of a cluster using gcloud alpha vmware clusters list. - -EXAMPLES - To create a cluster called my-cluster in private cloud my-private-cloud, - with 3 initial standard-72 nodes in zone us-west2-a, run: - - $ gcloud alpha vmware clusters create my-cluster \ - --location=us-west2-a --project=my-project \ - --private-cloud=my-private-cloud --node-type=standard-72 \ - --node-count=3 - - Or: - - $ gcloud alpha vmware clusters create my-cluster \ - --private-cloud=my-private-cloud --node-type=standard-72 \ - --node-count=3 - - In the second example, the project and location are taken from gcloud properties core/project and compute/zone. - -POSITIONAL ARGUMENTS - Cluster resource - cluster. The arguments in this group can be used to - specify the attributes of this resource. (NOTE) Some attributes are not - given arguments in this group but can be set in other ways. To set the - project attribute: - ◆ provide the argument cluster on the command line with a fully - specified name; - ◆ set the property core/project; - ◆ provide the argument --project on the command line. - - This must be specified. - - CLUSTER - ID of the cluster or fully qualified identifier for the cluster. To - set the cluster attribute: - ▸ provide the argument cluster on the command line. - - This positional must be specified if any of the other arguments in - this group are specified. - - --location=LOCATION - Zone of the private cloud or cluster. To set the location attribute: - ▸ provide the argument cluster on the command line with a fully - specified name; - ▸ provide the argument --location on the command line; - ▸ set the property compute/zone. - - --private-cloud=PRIVATE_CLOUD - VMware Engine private cloud. To set the private-cloud attribute: - ▸ provide the argument cluster on the command line with a fully - specified name; - ▸ provide the argument --private-cloud on the command line. - -REQUIRED FLAGS - --node-count=NODE_COUNT - Nodes count for cluster - - Node type resource - node_type. 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 --node-type on the command line with a fully - specified name; - ◆ set the property core/project; - ◆ provide the argument --project on the command line. To set the - location attribute: - ◆ provide the argument --node-type on the command line with a fully - specified name; - ◆ set the property compute/zone. - - This must be specified. - - --node-type=NODE_TYPE - ID of the node type or fully qualified identifier for the node type. - To set the node-type attribute: - ▸ provide the argument --node-type on the command line. - -OPTIONAL FLAGS - --async - Return immediately, without waiting for the operation in progress to - complete. The default is True. Enabled by default, use --no-async to - disable. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --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/vmware/clusters/delete b/gcloud/alpha/vmware/clusters/delete deleted file mode 100644 index 1e273f4b4..000000000 --- a/gcloud/alpha/vmware/clusters/delete +++ /dev/null @@ -1,81 +0,0 @@ -NAME - gcloud alpha vmware clusters delete - delete a Google Cloud VMware Engine - cluster - -SYNOPSIS - gcloud alpha vmware clusters delete - (CLUSTER : --location=LOCATION --private-cloud=PRIVATE_CLOUD) [--async] - [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (ALPHA) Delete a cluster in a VMware Engine private cloud. - -EXAMPLES - To delete a cluster called my-cluster in private cloud my-private-cloud and - zone us-west2-a, run: - - $ gcloud alpha vmware clusters delete my-cluster \ - --location=us-west2-a --project=my-project \ - --private-cloud=my-private-cloud - - Or: - - $ gcloud alpha vmware clusters delete my-cluster \ - --private-cloud=my-private-cloud - - In the second example, the project and location are taken from gcloud - properties core/project and compute/zone. - -POSITIONAL ARGUMENTS - Cluster resource - cluster. The arguments in this group can be used to - specify the attributes of this resource. (NOTE) Some attributes are not - given arguments in this group but can be set in other ways. To set the - project attribute: - ◆ provide the argument cluster on the command line with a fully - specified name; - ◆ set the property core/project; - ◆ provide the argument --project on the command line. - - This must be specified. - - CLUSTER - ID of the cluster or fully qualified identifier for the cluster. To - set the cluster attribute: - ▸ provide the argument cluster on the command line. - - This positional must be specified if any of the other arguments in - this group are specified. - - --location=LOCATION - Zone of the private cloud or cluster. To set the location attribute: - ▸ provide the argument cluster on the command line with a fully - specified name; - ▸ provide the argument --location on the command line; - ▸ set the property compute/zone. - - --private-cloud=PRIVATE_CLOUD - VMware Engine private cloud. To set the private-cloud attribute: - ▸ provide the argument cluster on the command line with a fully - specified name; - ▸ provide the argument --private-cloud on the command line. - -FLAGS - --async - Return immediately, without waiting for the operation in progress to - complete. The default is True. Enabled by default, use --no-async to - disable. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --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/vmware/clusters/describe b/gcloud/alpha/vmware/clusters/describe deleted file mode 100644 index ce8142f22..000000000 --- a/gcloud/alpha/vmware/clusters/describe +++ /dev/null @@ -1,75 +0,0 @@ -NAME - gcloud alpha vmware clusters describe - describe a Google Cloud VMware - Engine cluster - -SYNOPSIS - gcloud alpha vmware clusters describe - (CLUSTER : --location=LOCATION --private-cloud=PRIVATE_CLOUD) - [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (ALPHA) Display data associated with a VMware Engine cluster, such as its - node count, node type, and status. - -EXAMPLES - To describe a cluster called my-cluster in private cloud my-private-cloud - and zone us-west2-a, run: - - $ gcloud alpha vmware clusters describe my-cluster \ - --location=us-west2-a --project=my-project \ - --private-cloud=my-private-cloud - - Or: - - $ gcloud alpha vmware clusters describe my-cluster \ - --private-cloud=my-private-cloud - - In the second example, the project and location are taken from gcloud properties core/project and compute/zone. - -POSITIONAL ARGUMENTS - Cluster resource - cluster. The arguments in this group can be used to - specify the attributes of this resource. (NOTE) Some attributes are not - given arguments in this group but can be set in other ways. To set the - project attribute: - ◆ provide the argument cluster on the command line with a fully - specified name; - ◆ set the property core/project; - ◆ provide the argument --project on the command line. - - This must be specified. - - CLUSTER - ID of the cluster or fully qualified identifier for the cluster. To - set the cluster attribute: - ▸ provide the argument cluster on the command line. - - This positional must be specified if any of the other arguments in - this group are specified. - - --location=LOCATION - Zone of the private cloud or cluster. To set the location attribute: - ▸ provide the argument cluster on the command line with a fully - specified name; - ▸ provide the argument --location on the command line; - ▸ set the property compute/zone. - - --private-cloud=PRIVATE_CLOUD - VMware Engine private cloud. To set the private-cloud attribute: - ▸ provide the argument cluster on the command line with a fully - specified name; - ▸ provide the argument --private-cloud on the command line. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --configuration, --flags-file, --flatten, --format, - --help, --impersonate-service-account, --log-http, --project, --quiet, - --trace-token, --user-output-enabled, --verbosity. - - Run $ gcloud help for details. - -NOTES - This command is currently in alpha and might change without notice. If this - command fails with API permission errors despite specifying the correct - project, you might be trying to access an API with an invitation-only early - access allowlist. - diff --git a/gcloud/alpha/vmware/clusters/help b/gcloud/alpha/vmware/clusters/help deleted file mode 100644 index 727515d15..000000000 --- a/gcloud/alpha/vmware/clusters/help +++ /dev/null @@ -1,39 +0,0 @@ -NAME - gcloud alpha vmware clusters - manage clusters in Google Cloud VMware - Engine - -SYNOPSIS - gcloud alpha vmware clusters COMMAND [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (ALPHA) Manage clusters in Google Cloud VMware Engine. - -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 Google Cloud VMware Engine cluster. - - delete - (ALPHA) Delete a Google Cloud VMware Engine cluster. - - describe - (ALPHA) Describe a Google Cloud VMware Engine cluster. - - list - (ALPHA) List clusters in a Google Cloud VMware Engine private cloud. - - update - (ALPHA) Update a Google Cloud VMware Engine cluster. - -NOTES - This command is currently in alpha and might change without notice. If this - command fails with API permission errors despite specifying the correct - project, you might be trying to access an API with an invitation-only early - access allowlist. - diff --git a/gcloud/alpha/vmware/clusters/list b/gcloud/alpha/vmware/clusters/list deleted file mode 100644 index ee83b8c8c..000000000 --- a/gcloud/alpha/vmware/clusters/list +++ /dev/null @@ -1,99 +0,0 @@ -NAME - gcloud alpha vmware clusters list - list clusters in a Google Cloud VMware - Engine private cloud - -SYNOPSIS - gcloud alpha vmware clusters list - (--private-cloud=PRIVATE_CLOUD : --location=LOCATION) - [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] - [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (ALPHA) List clusters in a VMware Engine private cloud. - -EXAMPLES - To list clusters in the my-private-cloud private cloud run: - - $ gcloud alpha vmware clusters list --location=us-west2-a \ - --project=my-project --private-cloud=my-private-cloud - - Or: - - $ gcloud alpha vmware clusters list --private-cloud=my-private-cloud - - In the second example, the project and location are taken from gcloud - properties core/project and compute/zone. - -REQUIRED FLAGS - Private cloud resource - private_cloud. 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 --private-cloud on the command line with a fully - specified name; - ◆ set the property core/project; - ◆ provide the argument --project on the command line. - - This must be specified. - - --private-cloud=PRIVATE_CLOUD - ID of the private cloud or fully qualified identifier for the private - cloud. To set the private-cloud attribute: - ▸ provide the argument --private-cloud on the command line. - - This flag must be specified if any of the other arguments in this - group are specified. - - --location=LOCATION - Zone of the private cloud or cluster. To set the location attribute: - ▸ provide the argument --private-cloud on the command line with a - fully specified name; - ▸ provide the argument --location on the command line; - ▸ set the property compute/zone. - -LIST COMMAND FLAGS - --filter=EXPRESSION - Apply a Boolean filter EXPRESSION to each resource item to be listed. - If the expression evaluates True, then that item is listed. For more - details and examples of filter expressions, run $ gcloud topic filters. - This flag interacts with other flags that are applied in this order: - --flatten, --sort-by, --filter, --limit. - - --limit=LIMIT - Maximum number of resources to list. The default is unlimited. This - flag interacts with other flags that are applied in this order: - --flatten, --sort-by, --filter, --limit. - - --page-size=PAGE_SIZE - Some services group resource list output into pages. This flag - specifies the maximum number of resources per page. The default is - determined by the service if it supports paging, otherwise it is - unlimited (no paging). Paging may be applied before or after --filter - and --limit depending on the service. - - --sort-by=[FIELD,...] - Comma-separated list of resource field key names to sort by. The - default order is ascending. Prefix a field with ``~'' for descending - order on that field. This flag interacts with other flags that are - applied in this order: --flatten, --sort-by, --filter, --limit. - - --uri - Print a list of resource URIs instead of the default output, and change - the command output to a list of URIs. If this flag is used with - --format, the formatting is applied on this URI list. To display URIs - alongside other keys instead, use the uri() transform. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --configuration, --flags-file, --flatten, --format, - --help, --impersonate-service-account, --log-http, --project, --quiet, - --trace-token, --user-output-enabled, --verbosity. - - Run $ gcloud help for details. - -NOTES - This command is currently in alpha and might change without notice. If this - command fails with API permission errors despite specifying the correct - project, you might be trying to access an API with an invitation-only early - access allowlist. - diff --git a/gcloud/alpha/vmware/clusters/update b/gcloud/alpha/vmware/clusters/update deleted file mode 100644 index 6cdfcd216..000000000 --- a/gcloud/alpha/vmware/clusters/update +++ /dev/null @@ -1,86 +0,0 @@ -NAME - gcloud alpha vmware clusters update - update a Google Cloud VMware Engine - cluster - -SYNOPSIS - gcloud alpha vmware clusters update - (CLUSTER : --location=LOCATION --private-cloud=PRIVATE_CLOUD) - --node-count=NODE_COUNT [--async] [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (ALPHA) Adjust the number of nodes in the VMware Engine cluster. Successful - addition or removal of a node results in a cluster in READY state. Check - the progress of a cluster using gcloud alpha vmware clusters list. - -EXAMPLES - To resize a cluster called my-cluster in private cloud my-private-cloud and - zone us-west2-a to have ``3'' nodes, run: - - $ gcloud alpha vmware clusters update my-cluster \ - --location=us-west2-a --project=my-project \ - --private-cloud=my-private-cloud --node-count=3 - - Or: - - $ gcloud alpha vmware clusters update my-cluster \ - --private-cloud=my-private-cloud --node-count=3 - - In the second example, the project and location are taken from gcloud properties core/project and compute/zone. - -POSITIONAL ARGUMENTS - Cluster resource - cluster. The arguments in this group can be used to - specify the attributes of this resource. (NOTE) Some attributes are not - given arguments in this group but can be set in other ways. To set the - project attribute: - ◆ provide the argument cluster on the command line with a fully - specified name; - ◆ set the property core/project; - ◆ provide the argument --project on the command line. - - This must be specified. - - CLUSTER - ID of the cluster or fully qualified identifier for the cluster. To - set the cluster attribute: - ▸ provide the argument cluster on the command line. - - This positional must be specified if any of the other arguments in - this group are specified. - - --location=LOCATION - Zone of the private cloud or cluster. To set the location attribute: - ▸ provide the argument cluster on the command line with a fully - specified name; - ▸ provide the argument --location on the command line; - ▸ set the property compute/zone. - - --private-cloud=PRIVATE_CLOUD - VMware Engine private cloud. To set the private-cloud attribute: - ▸ provide the argument cluster on the command line with a fully - specified name; - ▸ provide the argument --private-cloud on the command line. - -REQUIRED FLAGS - --node-count=NODE_COUNT - Nodes count for cluster - -OPTIONAL FLAGS - --async - Return immediately, without waiting for the operation in progress to - complete. The default is True. Enabled by default, use --no-async to - disable. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --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/vmware/hcx/activationkeys/create b/gcloud/alpha/vmware/hcx/activationkeys/create deleted file mode 100644 index e6a8c7be8..000000000 --- a/gcloud/alpha/vmware/hcx/activationkeys/create +++ /dev/null @@ -1,85 +0,0 @@ -NAME - gcloud alpha vmware hcx activationkeys create - create a Google Cloud - VMware HCX activation key - -SYNOPSIS - gcloud alpha vmware hcx activationkeys create - (HCX_ACTIVATION_KEY - : --location=LOCATION --private-cloud=PRIVATE_CLOUD) [--async] - [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (ALPHA) Create a HCX activation key in a VMware Engine private cloud. - Successful creation of a HCX activation key results in a HCX activation key - in AVAILABLE state. Check the progress of a HCX activation key using gcloud - alpha vmware hcx activationkeys list. - -EXAMPLES - To create a HCX activation key called key1 in private cloud - my-private-cloud in zone us-west2-a, run: - - $ gcloud alpha vmware hcx activationkeys create key1 \ - --location=us-west2-a --project=my-project \ - --private-cloud=my-private-cloud - - Or: - - $ gcloud alpha vmware hcx activationkeys create my-cluster \ - --private-cloud=my-private-cloud - - In the second example, the project and location are taken from gcloud - properties core/project and compute/zone. - -POSITIONAL ARGUMENTS - HCX activation key resource - hcxactivationkey. 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 hcx_activation_key on the command line with a - fully specified name; - ◆ set the property core/project; - ◆ provide the argument --project on the command line. - - This must be specified. - - HCX_ACTIVATION_KEY - ID of the HCX activation key or fully qualified identifier for the - HCX activation key. To set the hcx-activation-key attribute: - ▸ provide the argument hcx_activation_key on the command line. - - This positional must be specified if any of the other arguments in - this group are specified. - - --location=LOCATION - Zone of the private cloud or cluster. To set the location attribute: - ▸ provide the argument hcx_activation_key on the command line with - a fully specified name; - ▸ provide the argument --location on the command line; - ▸ set the property compute/zone. - - --private-cloud=PRIVATE_CLOUD - VMware Engine private cloud. To set the private-cloud attribute: - ▸ provide the argument hcx_activation_key on the command line with - a fully specified name; - ▸ provide the argument --private-cloud on the command line. - -FLAGS - --async - Return immediately, without waiting for the operation in progress to - complete. The default is True. Enabled by default, use --no-async to - disable. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --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/vmware/hcx/activationkeys/describe b/gcloud/alpha/vmware/hcx/activationkeys/describe deleted file mode 100644 index 0ddeb26ab..000000000 --- a/gcloud/alpha/vmware/hcx/activationkeys/describe +++ /dev/null @@ -1,76 +0,0 @@ -NAME - gcloud alpha vmware hcx activationkeys describe - describe a Google Cloud - VMware HCX activation key - -SYNOPSIS - gcloud alpha vmware hcx activationkeys describe - (HCX_ACTIVATION_KEY - : --location=LOCATION --private-cloud=PRIVATE_CLOUD) - [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (ALPHA) Display data associated with an HCX activation key, such as the key - itself, its resource name, and when it was created. - -EXAMPLES - To describe a HCX activation key called key1 in private cloud - my-private-cloud in zone us-west2-a, run: - - $ gcloud alpha vmware hcx activationkeys describe key1 \ - --location=us-west2-a --project=my-project \ - --private-cloud=my-private-cloud - - Or: - - $ gcloud alpha vmware hcx activationkeys describe key1 \ - --private-cloud=my-private-cloud - - In the second example, the project and location are taken from gcloud properties core/project and compute/zone. - -POSITIONAL ARGUMENTS - HCX activation key resource - hcxactivationkey. 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 hcx_activation_key on the command line with a - fully specified name; - ◆ set the property core/project; - ◆ provide the argument --project on the command line. - - This must be specified. - - HCX_ACTIVATION_KEY - ID of the HCX activation key or fully qualified identifier for the - HCX activation key. To set the hcx-activation-key attribute: - ▸ provide the argument hcx_activation_key on the command line. - - This positional must be specified if any of the other arguments in - this group are specified. - - --location=LOCATION - Zone of the private cloud or cluster. To set the location attribute: - ▸ provide the argument hcx_activation_key on the command line with - a fully specified name; - ▸ provide the argument --location on the command line; - ▸ set the property compute/zone. - - --private-cloud=PRIVATE_CLOUD - VMware Engine private cloud. To set the private-cloud attribute: - ▸ provide the argument hcx_activation_key on the command line with - a fully specified name; - ▸ provide the argument --private-cloud on the command line. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --configuration, --flags-file, --flatten, --format, - --help, --impersonate-service-account, --log-http, --project, --quiet, - --trace-token, --user-output-enabled, --verbosity. - - Run $ gcloud help for details. - -NOTES - This command is currently in alpha and might change without notice. If this - command fails with API permission errors despite specifying the correct - project, you might be trying to access an API with an invitation-only early - access allowlist. - diff --git a/gcloud/alpha/vmware/hcx/activationkeys/help b/gcloud/alpha/vmware/hcx/activationkeys/help deleted file mode 100644 index 6cbc57416..000000000 --- a/gcloud/alpha/vmware/hcx/activationkeys/help +++ /dev/null @@ -1,34 +0,0 @@ -NAME - gcloud alpha vmware hcx activationkeys - manage VMware HCX activation keys - using Google Cloud VMware Engine - -SYNOPSIS - gcloud alpha vmware hcx activationkeys COMMAND [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (ALPHA) Manage VMware HCX activation keys using Google Cloud VMware Engine. - -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 Google Cloud VMware HCX activation key. - - describe - (ALPHA) Describe a Google Cloud VMware HCX activation key. - - list - (ALPHA) List HCX activation keys in a Google Cloud VMware Engine - private cloud. - -NOTES - This command is currently in alpha and might change without notice. If this - command fails with API permission errors despite specifying the correct - project, you might be trying to access an API with an invitation-only early - access allowlist. - diff --git a/gcloud/alpha/vmware/hcx/activationkeys/list b/gcloud/alpha/vmware/hcx/activationkeys/list deleted file mode 100644 index 854c09485..000000000 --- a/gcloud/alpha/vmware/hcx/activationkeys/list +++ /dev/null @@ -1,101 +0,0 @@ -NAME - gcloud alpha vmware hcx activationkeys list - list HCX activation keys in a - Google Cloud VMware Engine private cloud - -SYNOPSIS - gcloud alpha vmware hcx activationkeys list - (--private-cloud=PRIVATE_CLOUD : --location=LOCATION) - [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] - [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (ALPHA) List HCX activation keys in a VMware Engine private cloud. - -EXAMPLES - To list HCX activation keys in the my-private-cloud private cloud run: - - $ gcloud alpha vmware hcx activationkeys list \ - --location=us-west2-a --project=my-project \ - --private-cloud=my-private-cloud - - Or: - - $ gcloud alpha vmware hcx activationkeys list \ - --private-cloud=my-private-cloud - - In the second example, the project and location are taken from gcloud - properties core/project and compute/zone. - -REQUIRED FLAGS - Private cloud resource - private_cloud. 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 --private-cloud on the command line with a fully - specified name; - ◆ set the property core/project; - ◆ provide the argument --project on the command line. - - This must be specified. - - --private-cloud=PRIVATE_CLOUD - ID of the private cloud or fully qualified identifier for the private - cloud. To set the private-cloud attribute: - ▸ provide the argument --private-cloud on the command line. - - This flag must be specified if any of the other arguments in this - group are specified. - - --location=LOCATION - Zone of the private cloud or cluster. To set the location attribute: - ▸ provide the argument --private-cloud on the command line with a - fully specified name; - ▸ provide the argument --location on the command line; - ▸ set the property compute/zone. - -LIST COMMAND FLAGS - --filter=EXPRESSION - Apply a Boolean filter EXPRESSION to each resource item to be listed. - If the expression evaluates True, then that item is listed. For more - details and examples of filter expressions, run $ gcloud topic filters. - This flag interacts with other flags that are applied in this order: - --flatten, --sort-by, --filter, --limit. - - --limit=LIMIT - Maximum number of resources to list. The default is unlimited. This - flag interacts with other flags that are applied in this order: - --flatten, --sort-by, --filter, --limit. - - --page-size=PAGE_SIZE - Some services group resource list output into pages. This flag - specifies the maximum number of resources per page. The default is - determined by the service if it supports paging, otherwise it is - unlimited (no paging). Paging may be applied before or after --filter - and --limit depending on the service. - - --sort-by=[FIELD,...] - Comma-separated list of resource field key names to sort by. The - default order is ascending. Prefix a field with ``~'' for descending - order on that field. This flag interacts with other flags that are - applied in this order: --flatten, --sort-by, --filter, --limit. - - --uri - Print a list of resource URIs instead of the default output, and change - the command output to a list of URIs. If this flag is used with - --format, the formatting is applied on this URI list. To display URIs - alongside other keys instead, use the uri() transform. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --configuration, --flags-file, --flatten, --format, - --help, --impersonate-service-account, --log-http, --project, --quiet, - --trace-token, --user-output-enabled, --verbosity. - - Run $ gcloud help for details. - -NOTES - This command is currently in alpha and might change without notice. If this - command fails with API permission errors despite specifying the correct - project, you might be trying to access an API with an invitation-only early - access allowlist. - diff --git a/gcloud/alpha/vmware/hcx/help b/gcloud/alpha/vmware/hcx/help deleted file mode 100644 index c57a5b515..000000000 --- a/gcloud/alpha/vmware/hcx/help +++ /dev/null @@ -1,27 +0,0 @@ -NAME - gcloud alpha vmware hcx - manage HCX using Google Cloud VMware Engine - -SYNOPSIS - gcloud alpha vmware hcx GROUP [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (ALPHA) Manage HCX using Google Cloud VMware Engine. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --help. - - Run $ gcloud help for details. - -GROUPS - GROUP is one of the following: - - activationkeys - (ALPHA) Manage VMware HCX activation keys using Google Cloud VMware - Engine. - -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/vmware/help b/gcloud/alpha/vmware/help index a683c01f7..67182da5d 100644 --- a/gcloud/alpha/vmware/help +++ b/gcloud/alpha/vmware/help @@ -12,41 +12,6 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. -GROUPS - GROUP is one of the following: - - clusters - (ALPHA) Manage clusters in Google Cloud VMware Engine. - - hcx - (ALPHA) Manage HCX using Google Cloud VMware Engine. - - locations - (ALPHA) List locations in Google Cloud VMware Engine. - - network-peerings - (ALPHA) Manage VMware Engine VPC peering using Google Cloud VMware - Engine. - - network-policies - (ALPHA) Manage VMware Engine network policies in Google Cloud VMware - Engine. - - node-types - (ALPHA) Show node types in Google Cloud VMware Engine. - - nsx - (ALPHA) Manage NSX using Google Cloud VMware Engine. - - operations - (ALPHA) List and describe operations in Google Cloud VMware Engine. - - private-clouds - (ALPHA) Manage private clouds in Google Cloud VMware Engine. - - vcenter - (ALPHA) Manage vCenter resources in Google Cloud VMware Engine. - 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/vmware/network-peerings/create b/gcloud/alpha/vmware/network-peerings/create deleted file mode 100644 index cc7ae8dd9..000000000 --- a/gcloud/alpha/vmware/network-peerings/create +++ /dev/null @@ -1,166 +0,0 @@ -NAME - gcloud alpha vmware network-peerings create - create a VMware Engine VPC - network peering - -SYNOPSIS - gcloud alpha vmware network-peerings create NETWORK_PEERING - --peer-network=PEER_NETWORK --peer-network-type=PEER_NETWORK_TYPE - (--vmware-engine-network=VMWARE_ENGINE_NETWORK - : --network-location=NETWORK_LOCATION) [--async] - [--description=DESCRIPTION] [--no-exchange-subnet-routes] - [--no-export-custom-routes] [--no-export-custom-routes-with-public-ip] - [--no-import-custom-routes] [--no-import-custom-routes-with-public-ip] - [--peer-mtu=PEER_MTU] [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (ALPHA) Create a VMware Engine VPC network peering. VPC network peering - creation is considered finished when the network peering is in ACTIVE - state. Check the progress of a VPC network peering using gcloud alpha - vmware network-peerings list. - -EXAMPLES - To create a VPC network peering called new-peering that connects the VMware - Engine network - projects/my-project/locations/us-west1/vmwareEngineNetworks/my-vmware-engine-network - with another VMware Engine network - projects/another-project/global/networks/another-vmware-engine-network, - run: - - $ gcloud alpha vmware network-peerings create new-peering \ - --vmware-engine-network=projects/my-project/locations/us-west1/\ - vmwareEngineNetworks/my-vmware-engine-network \ - --peer-network=projects/another-project/global/networks/\ - another-vmware-engine-network \ - --peer-network-type=VMWARE_ENGINE_NETWORK - - In this example, the project is taken from gcloud properties core/project - and location is taken as global. - -POSITIONAL ARGUMENTS - VMware Engine VPC network peering resource - network_peering. This - represents a Cloud resource. (NOTE) Some attributes are not given - arguments in this group but can be set in other ways. To set the project - attribute: - ◆ provide the argument network_peering on the command line with a fully - specified name; - ◆ set the property core/project; - ◆ provide the argument --project on the command line. - - This must be specified. - - NETWORK_PEERING - ID of the VMware Engine VPC network peering or fully qualified - identifier for the VMware Engine VPC network peering. To set the - network-peering attribute: - ▸ provide the argument network_peering on the command line. - -REQUIRED FLAGS - --peer-network=PEER_NETWORK - Name of the VPC network to peer with the VMware Engine network. The - peer network can be a consumer VPC network or another service producer - VPC network. For a consumer VPC network, provide the name in the - following form: projects/{project}/global/networks/{network_id} If the - peer network is of type VMWARE_ENGINE_NETWORK, then the peer network - will be a service producer VPC network. For a service producer VPC - network, provide the name in the following form: - projects/{project}/locations/{location}/vmwareEngineNetworks/{vmware_engine_network_id} - - --peer-network-type=PEER_NETWORK_TYPE - Type of the VPC network to peer with the VMware Engine network. - PEER_NETWORK_TYPE must be one of the following: - ◆ STANDARD: Peering connection used for connecting to another VPC - network established by the same user. For example, a peering - connection to another VPC network in the same project or to an - on-premises network. - ◆ VMWARE_ENGINE_NETWORK: Peering connection used for connecting to - another VMware Engine network. - ◆ PRIVATE_SERVICES_ACCESS: Peering connection used for establishing - private services access. - ◆ NETAPP_CLOUD_VOLUMES: Peering connection used for connecting to - NetApp Cloud Volumes. - ◆ THIRD_PARTY_SERVICE: Peering connection used for connecting to - third-party services. Most third-party services require manual setup - of reverse peering on the VPC network associated with the third-party - service. PEER_NETWORK_TYPE must be one of: - PEER_NETWORK_TYPE_UNSPECIFIED, STANDARD, VMWARE_ENGINE_NETWORK, - PRIVATE_SERVICES_ACCESS, NETAPP_CLOUD_VOLUMES, THIRD_PARTY_SERVICE. - - VMware Engine network resource - vmware_engine_network. 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 --vmware-engine-network on the command line with - a fully specified name; - ◆ set the property core/project; - ◆ provide the argument --project on the command line. - - This must be specified. - - --vmware-engine-network=VMWARE_ENGINE_NETWORK - ID of the VMware Engine network or fully qualified identifier for the - VMware Engine network. To set the vmware-engine-network attribute: - ▸ provide the argument --vmware-engine-network on the command line. - - This flag must be specified if any of the other arguments in this - group are specified. - - --network-location=NETWORK_LOCATION - The resource name of the location. To set the location attribute: - ▸ provide the argument --vmware-engine-network on the command line - with a fully specified name; - ▸ provide the argument --network-location on the command line; - ▸ set location as 'global' (default) or a region. - -OPTIONAL FLAGS - --async - Return immediately, without waiting for the operation in progress to - complete. The default is True. Enabled by default, use --no-async to - disable. - - --description=DESCRIPTION - User-provided description of the VPC network peering. - - --exchange-subnet-routes - True if full-mesh connectivity is created and managed automatically - between peered VPC networks; false otherwise. This field is always true - because Google Compute Engine automatically creates and manages - subnetwork routes between two VPC networks when the peering state is - ACTIVE. Enabled by default, use --no-exchange-subnet-routes to disable. - - --export-custom-routes - True if custom routes are exported to the peered VPC network; false - otherwise. The default value is true. Enabled by default, use - --no-export-custom-routes to disable. - - --export-custom-routes-with-public-ip - True if all subnet routes with public IP address range are exported; - false otherwise. The default value is true. Enabled by default, use - --no-export-custom-routes-with-public-ip to disable. - - --import-custom-routes - True if custom routes are imported to the peered VPC network; false - otherwise. The default value is true. Enabled by default, use - --no-import-custom-routes to disable. - - --import-custom-routes-with-public-ip - True if all subnet routes with public IP address range are imported; - false otherwise. The default value is true. Enabled by default, use - --no-import-custom-routes-with-public-ip to disable. - - --peer-mtu=PEER_MTU - Maximum transmission unit (MTU) in bytes. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --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/vmware/network-peerings/delete b/gcloud/alpha/vmware/network-peerings/delete deleted file mode 100644 index 1c8185fc4..000000000 --- a/gcloud/alpha/vmware/network-peerings/delete +++ /dev/null @@ -1,59 +0,0 @@ -NAME - gcloud alpha vmware network-peerings delete - delete a Google Cloud VMware - Engine VPC network peering - -SYNOPSIS - gcloud alpha vmware network-peerings delete NETWORK_PEERING [--async] - [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (ALPHA) Delete a VPC network peering. After you delete a VPC network - peering, you won't be able to access the corresponding VMware Engine - network through the peer network. - -EXAMPLES - To delete a VPC network peering with name my-peering, run: - - $ gcloud alpha vmware network-peerings delete my-peering - - In this example, the project is taken from gcloud properties core/project - and location is taken as global. - -POSITIONAL ARGUMENTS - VMware Engine VPC network peering resource - network_peering. This - represents a Cloud resource. (NOTE) Some attributes are not given - arguments in this group but can be set in other ways. To set the project - attribute: - ◆ provide the argument network_peering on the command line with a fully - specified name; - ◆ set the property core/project; - ◆ provide the argument --project on the command line. - - This must be specified. - - NETWORK_PEERING - ID of the VMware Engine VPC network peering or fully qualified - identifier for the VMware Engine VPC network peering. To set the - network-peering attribute: - ▸ provide the argument network_peering on the command line. - -FLAGS - --async - Return immediately, without waiting for the operation in progress to - complete. The default is True. Enabled by default, use --no-async to - disable. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --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/vmware/network-peerings/describe b/gcloud/alpha/vmware/network-peerings/describe deleted file mode 100644 index 2d620fcdc..000000000 --- a/gcloud/alpha/vmware/network-peerings/describe +++ /dev/null @@ -1,51 +0,0 @@ -NAME - gcloud alpha vmware network-peerings describe - describe a Google Cloud - VMware Engine VPC network peering - -SYNOPSIS - gcloud alpha vmware network-peerings describe NETWORK_PEERING - [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (ALPHA) Get information about a VPC network peering. - -EXAMPLES - To get information about a VPC network peering called new-peering, run: - - $ gcloud alpha vmware network-peerings describe new-peering - - In this example, the project is taken from gcloud properties core/project - and location is taken as global. - -POSITIONAL ARGUMENTS - VMware Engine VPC network peering resource - network_peering. This - represents a Cloud resource. (NOTE) Some attributes are not given - arguments in this group but can be set in other ways. To set the project - attribute: - ◆ provide the argument network_peering on the command line with a fully - specified name; - ◆ set the property core/project; - ◆ provide the argument --project on the command line. - - This must be specified. - - NETWORK_PEERING - ID of the VMware Engine VPC network peering or fully qualified - identifier for the VMware Engine VPC network peering. To set the - network-peering attribute: - ▸ provide the argument network_peering on the command line. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --configuration, --flags-file, --flatten, --format, - --help, --impersonate-service-account, --log-http, --project, --quiet, - --trace-token, --user-output-enabled, --verbosity. - - Run $ gcloud help for details. - -NOTES - This command is currently in alpha and might change without notice. If this - command fails with API permission errors despite specifying the correct - project, you might be trying to access an API with an invitation-only early - access allowlist. - diff --git a/gcloud/alpha/vmware/network-peerings/help b/gcloud/alpha/vmware/network-peerings/help deleted file mode 100644 index 9e6c6a1f1..000000000 --- a/gcloud/alpha/vmware/network-peerings/help +++ /dev/null @@ -1,46 +0,0 @@ -NAME - gcloud alpha vmware network-peerings - manage VMware Engine VPC peering - using Google Cloud VMware Engine - -SYNOPSIS - gcloud alpha vmware network-peerings GROUP | COMMAND [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (ALPHA) Manage VMware Engine VPC peering using Google Cloud VMware Engine. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --help. - - Run $ gcloud help for details. - -GROUPS - GROUP is one of the following: - - routes - (ALPHA) Manage VMware Engine VPC peering routes using Google Cloud - VMware Engine. - -COMMANDS - COMMAND is one of the following: - - create - (ALPHA) Create a VMware Engine VPC network peering. - - delete - (ALPHA) Delete a Google Cloud VMware Engine VPC network peering. - - describe - (ALPHA) Describe a Google Cloud VMware Engine VPC network peering. - - list - (ALPHA) List Google Cloud VMware Engine VPC network peerings. - - update - (ALPHA) Update a Google Cloud VMware Engine VPC network peering. - -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/vmware/network-peerings/routes/help b/gcloud/alpha/vmware/network-peerings/routes/help deleted file mode 100644 index a7f097f1a..000000000 --- a/gcloud/alpha/vmware/network-peerings/routes/help +++ /dev/null @@ -1,28 +0,0 @@ -NAME - gcloud alpha vmware network-peerings routes - manage VMware Engine VPC - peering routes using Google Cloud VMware Engine - -SYNOPSIS - gcloud alpha vmware network-peerings routes COMMAND [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (ALPHA) Manage VMware Engine VPC peering routes using Google Cloud VMware - Engine. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --help. - - Run $ gcloud help for details. - -COMMANDS - COMMAND is one of the following: - - list - (ALPHA) List Google Cloud VMware Engine VPC network peering routes. - -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/vmware/network-peerings/routes/list b/gcloud/alpha/vmware/network-peerings/routes/list deleted file mode 100644 index d701dabb2..000000000 --- a/gcloud/alpha/vmware/network-peerings/routes/list +++ /dev/null @@ -1,91 +0,0 @@ -NAME - gcloud alpha vmware network-peerings routes list - list Google Cloud VMware - Engine VPC network peering routes - -SYNOPSIS - gcloud alpha vmware network-peerings routes list - --network-peering=NETWORK_PEERING [--filter=EXPRESSION] [--limit=LIMIT] - [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] - [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (ALPHA) List VPC network peering routes across all locations in your - project. - -EXAMPLES - To list peering routes imported from peer network via my-peering: - - $ gcloud alpha vmware network-peerings routes list \ - --network-peering=my-peering --filter="direction=INCOMING" - - To list peering routes exported to peer network via my-peering: - - $ gcloud alpha vmware network-peerings routes list \ - --network-peering=my-peering --filter="direction=OUTGOING" - - In above examples, the location is taken as global. - -REQUIRED FLAGS - VMware Engine VPC network peering resource - network_peering. This - represents a Cloud resource. (NOTE) Some attributes are not given - arguments in this group but can be set in other ways. To set the project - attribute: - ◆ provide the argument --network-peering on the command line with a - fully specified name; - ◆ set the property core/project; - ◆ provide the argument --project on the command line. - - This must be specified. - - --network-peering=NETWORK_PEERING - ID of the VMware Engine VPC network peering or fully qualified - identifier for the VMware Engine VPC network peering. To set the - network-peering attribute: - ▸ provide the argument --network-peering on the command line. - -LIST COMMAND FLAGS - --filter=EXPRESSION - Apply a Boolean filter EXPRESSION to each resource item to be listed. - If the expression evaluates True, then that item is listed. For more - details and examples of filter expressions, run $ gcloud topic filters. - This flag interacts with other flags that are applied in this order: - --flatten, --sort-by, --filter, --limit. - - --limit=LIMIT - Maximum number of resources to list. The default is unlimited. This - flag interacts with other flags that are applied in this order: - --flatten, --sort-by, --filter, --limit. - - --page-size=PAGE_SIZE - Some services group resource list output into pages. This flag - specifies the maximum number of resources per page. The default is - determined by the service if it supports paging, otherwise it is - unlimited (no paging). Paging may be applied before or after --filter - and --limit depending on the service. - - --sort-by=[FIELD,...] - Comma-separated list of resource field key names to sort by. The - default order is ascending. Prefix a field with ``~'' for descending - order on that field. This flag interacts with other flags that are - applied in this order: --flatten, --sort-by, --filter, --limit. - - --uri - Print a list of resource URIs instead of the default output, and change - the command output to a list of URIs. If this flag is used with - --format, the formatting is applied on this URI list. To display URIs - alongside other keys instead, use the uri() transform. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --configuration, --flags-file, --flatten, --format, - --help, --impersonate-service-account, --log-http, --project, --quiet, - --trace-token, --user-output-enabled, --verbosity. - - Run $ gcloud help for details. - -NOTES - This command is currently in 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/vmware/network-peerings/update b/gcloud/alpha/vmware/network-peerings/update deleted file mode 100644 index 7f620ff12..000000000 --- a/gcloud/alpha/vmware/network-peerings/update +++ /dev/null @@ -1,62 +0,0 @@ -NAME - gcloud alpha vmware network-peerings update - update a Google Cloud VMware - Engine VPC network peering - -SYNOPSIS - gcloud alpha vmware network-peerings update NETWORK_PEERING [--async] - [--description=DESCRIPTION] [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (ALPHA) Update a VMware Engine VPC network peering description. - -EXAMPLES - To update only the description of a VPC network peering named my-peering to - Example description, run: - - $ gcloud alpha vmware network-peerings update my-peering \ - --description="Example description" - - In this example, the project is taken from gcloud properties core/project - and location is taken as global. - -POSITIONAL ARGUMENTS - VMware Engine VPC network peering resource - network_peering. This - represents a Cloud resource. (NOTE) Some attributes are not given - arguments in this group but can be set in other ways. To set the project - attribute: - ◆ provide the argument network_peering on the command line with a fully - specified name; - ◆ set the property core/project; - ◆ provide the argument --project on the command line. - - This must be specified. - - NETWORK_PEERING - ID of the VMware Engine VPC network peering or fully qualified - identifier for the VMware Engine VPC network peering. To set the - network-peering attribute: - ▸ provide the argument network_peering on the command line. - -FLAGS - --async - Return immediately, without waiting for the operation in progress to - complete. The default is True. Enabled by default, use --no-async to - disable. - - --description=DESCRIPTION - Updated description for this VPC network peering. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --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/vmware/network-policies/create b/gcloud/alpha/vmware/network-policies/create deleted file mode 100644 index e6e598fbb..000000000 --- a/gcloud/alpha/vmware/network-policies/create +++ /dev/null @@ -1,138 +0,0 @@ -NAME - gcloud alpha vmware network-policies create - create a VMware Engine - network policy - -SYNOPSIS - gcloud alpha vmware network-policies create - (NETWORK_POLICY : --location=LOCATION) - --edge-services-cidr=EDGE_SERVICES_CIDR - (--vmware-engine-network=VMWARE_ENGINE_NETWORK - : --network-location=NETWORK_LOCATION) [--async] - [--description=DESCRIPTION] [--external-ip-access] [--internet-access] - [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (ALPHA) Create a VMware Engine network policy. Only one network policy - applies to a VMware Engine network per region. Check the progress of a - network policy creation using gcloud alpha vmware network-policies list. - -EXAMPLES - To create a network policy called my-network-policy which connects to the - VMware Engine network - projects/my-project/locations/global/vmwareEngineNetworks/my-vmware-engine-network - using the edge services address range 192.168.0.0/26 with the internet - access service enabled and the external IP access service disabled, run: - - $ gcloud alpha vmware network-policies create my-network-policy \ - --location=us-west2 --project=my-project \ - --vmware-engine-network=projects/my-project/locations/global/\ - vmwareEngineNetworks/my-vmware-engine-network \ - --edge-services-cidr=192.168.0.0/26 --internet-access \ - --no-external-ip-access - - Or: - - $ gcloud alpha vmware network-policies create my-network-policy \ - --vmware-engine-network=projects/my-project/locations/global/\ - vmwareEngineNetworks/my-vmware-engine-network \ - --edge-services-cidr=192.168.0.0/26 --internet-access - - In the second example, the project and the location are taken from gcloud - properties core/project and compute/region respectively. If the - --external-ip-access flag is not specified, it is taken as False. - -POSITIONAL ARGUMENTS - VMware Engine Network Policy resource - network_policy. 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 network_policy on the command line with a fully - specified name; - ◆ set the property core/project; - ◆ provide the argument --project on the command line. - - This must be specified. - - NETWORK_POLICY - ID of the VMware Engine Network Policy or fully qualified identifier - for the VMware Engine Network Policy. To set the network-policy - attribute: - ▸ provide the argument network_policy on the command line. - - This positional must be specified if any of the other arguments in - this group are specified. - - --location=LOCATION - The resource name of the location. To set the location attribute: - ▸ provide the argument network_policy on the command line with a - fully specified name; - ▸ provide the argument --location on the command line; - ▸ set the property compute/region. - -REQUIRED FLAGS - --edge-services-cidr=EDGE_SERVICES_CIDR - IP address range to use for internet access and external IP access - gateways, in CIDR notation. An RFC 1918 CIDR block with a "/26" prefix - is required. - - VMware Engine network resource - vmware_engine_network. 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 --vmware-engine-network on the command line with - a fully specified name; - ◆ set the property core/project; - ◆ provide the argument --project on the command line. - - This must be specified. - - --vmware-engine-network=VMWARE_ENGINE_NETWORK - ID of the VMware Engine network or fully qualified identifier for the - VMware Engine network. To set the vmware-engine-network attribute: - ▸ provide the argument --vmware-engine-network on the command line. - - This flag must be specified if any of the other arguments in this - group are specified. - - --network-location=NETWORK_LOCATION - The resource name of the location. To set the location attribute: - ▸ provide the argument --vmware-engine-network on the command line - with a fully specified name; - ▸ provide the argument --network-location on the command line; - ▸ set location as 'global' (default) or a region. - -OPTIONAL FLAGS - --async - Return immediately, without waiting for the operation in progress to - complete. The default is True. Enabled by default, use --no-async to - disable. - - --description=DESCRIPTION - User-provided description of the network policy. - - --external-ip-access - Enable or disable network service that allows external IP addresses to - be assigned to VMware workloads. To enable this service, - internet-access must also be enabled. Use --no-external-ip-access to - disable. If the flag is not provided, access to VMware workloads - through external IP addresses is disabled. - - --internet-access - Enable or disable network service that allows VMware workloads to - access the internet. Use --no-internet-access to disable. If the flag - is not provided, internet access is disabled. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --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/vmware/network-policies/delete b/gcloud/alpha/vmware/network-policies/delete deleted file mode 100644 index feaadb2d7..000000000 --- a/gcloud/alpha/vmware/network-policies/delete +++ /dev/null @@ -1,73 +0,0 @@ -NAME - gcloud alpha vmware network-policies delete - delete a VMware Engine - network policy - -SYNOPSIS - gcloud alpha vmware network-policies delete - (NETWORK_POLICY : --location=LOCATION) [--async] [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (ALPHA) Delete a VMware Engine network policy. - -EXAMPLES - To delete a network policy called my-network-policy in project my-project - and region us-west2, run: - - $ gcloud alpha vmware network-policies delete my-network-policy \ - --location=us-west2 --project=my-project - - Or: - - $ gcloud alpha vmware network-policies delete my-network-policy - - In the second example, the project and the location are taken from gcloud - properties core/project and compute/region respectively. - -POSITIONAL ARGUMENTS - VMware Engine Network Policy resource - network_policy. 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 network_policy on the command line with a fully - specified name; - ◆ set the property core/project; - ◆ provide the argument --project on the command line. - - This must be specified. - - NETWORK_POLICY - ID of the VMware Engine Network Policy or fully qualified identifier - for the VMware Engine Network Policy. To set the network-policy - attribute: - ▸ provide the argument network_policy on the command line. - - This positional must be specified if any of the other arguments in - this group are specified. - - --location=LOCATION - The resource name of the location. To set the location attribute: - ▸ provide the argument network_policy on the command line with a - fully specified name; - ▸ provide the argument --location on the command line; - ▸ set the property compute/region. - -FLAGS - --async - Return immediately, without waiting for the operation in progress to - complete. The default is True. Enabled by default, use --no-async to - disable. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --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/vmware/network-policies/describe b/gcloud/alpha/vmware/network-policies/describe deleted file mode 100644 index d62dff28f..000000000 --- a/gcloud/alpha/vmware/network-policies/describe +++ /dev/null @@ -1,67 +0,0 @@ -NAME - gcloud alpha vmware network-policies describe - describe a VMware Engine - network policy - -SYNOPSIS - gcloud alpha vmware network-policies describe - (NETWORK_POLICY : --location=LOCATION) [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (ALPHA) Describe a VMware Engine network policy. - -EXAMPLES - To get a description of a network policy called my-network-policy in - project my-project and region us-west2, run: - - $ gcloud alpha vmware network-policies describe my-network-policy \ - --location=us-west2 --project=my-project - - Or: - - $ gcloud alpha vmware network-policies describe my-network-policy - - In the second example, the project and the location are taken from gcloud - properties core/project and compute/region respectively. - -POSITIONAL ARGUMENTS - VMware Engine Network Policy resource - network_policy. 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 network_policy on the command line with a fully - specified name; - ◆ set the property core/project; - ◆ provide the argument --project on the command line. - - This must be specified. - - NETWORK_POLICY - ID of the VMware Engine Network Policy or fully qualified identifier - for the VMware Engine Network Policy. To set the network-policy - attribute: - ▸ provide the argument network_policy on the command line. - - This positional must be specified if any of the other arguments in - this group are specified. - - --location=LOCATION - The resource name of the location. To set the location attribute: - ▸ provide the argument network_policy on the command line with a - fully specified name; - ▸ provide the argument --location 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. - -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/vmware/network-policies/help b/gcloud/alpha/vmware/network-policies/help deleted file mode 100644 index dde45f993..000000000 --- a/gcloud/alpha/vmware/network-policies/help +++ /dev/null @@ -1,40 +0,0 @@ -NAME - gcloud alpha vmware network-policies - manage VMware Engine network - policies in Google Cloud VMware Engine - -SYNOPSIS - gcloud alpha vmware network-policies COMMAND [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (ALPHA) Manage VMware Engine network policies in Google Cloud VMware - Engine. - -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 VMware Engine network policy. - - delete - (ALPHA) Delete a VMware Engine network policy. - - describe - (ALPHA) Describe a VMware Engine network policy. - - list - (ALPHA) List VMware Engine network policies. - - update - (ALPHA) Update a VMware 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/vmware/network-policies/list b/gcloud/alpha/vmware/network-policies/list deleted file mode 100644 index 3ee4a5705..000000000 --- a/gcloud/alpha/vmware/network-policies/list +++ /dev/null @@ -1,100 +0,0 @@ -NAME - gcloud alpha vmware network-policies list - list VMware Engine network - policies - -SYNOPSIS - gcloud alpha vmware network-policies list [--location=LOCATION] - [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] - [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (ALPHA) List VMware Engine network policies. - -EXAMPLES - To list network policies in your project in the region us-west2 sorted from - oldest to newest, run: - - $ gcloud alpha vmware network-policies list --location=us-west2 \ - --project=my-project --sort-by=~create_time - - Or: - - $ gcloud alpha vmware network-policies list --sort-by=~create_time - - In the second example, the project and the location are taken from gcloud - properties core/project and compute/region respectively. - - To list network policies in your project from all regions, run: - - $ gcloud alpha vmware network-policies list --location=- \ - --project=my-project - - Or: - - $ gcloud alpha vmware network-policies list --location=- - - In the last example, the project is taken from gcloud properties - core/project. - -FLAGS - Location resource - location. This represents a Cloud resource. (NOTE) - Some attributes are not given arguments in this group but can be set in - other ways. To set the project attribute: - ◆ provide the argument --location on the command line with a fully - specified name; - ◆ set the property compute/region with a fully specified name; - ◆ set the property core/project; - ◆ provide the argument --project on the command line. - - --location=LOCATION - ID of the location or fully qualified identifier for the location. To - set the location attribute: - ▸ provide the argument --location on the command line; - ▸ set the property compute/region. - -LIST COMMAND FLAGS - --filter=EXPRESSION - Apply a Boolean filter EXPRESSION to each resource item to be listed. - If the expression evaluates True, then that item is listed. For more - details and examples of filter expressions, run $ gcloud topic filters. - This flag interacts with other flags that are applied in this order: - --flatten, --sort-by, --filter, --limit. - - --limit=LIMIT - Maximum number of resources to list. The default is unlimited. This - flag interacts with other flags that are applied in this order: - --flatten, --sort-by, --filter, --limit. - - --page-size=PAGE_SIZE - Some services group resource list output into pages. This flag - specifies the maximum number of resources per page. The default is - determined by the service if it supports paging, otherwise it is - unlimited (no paging). Paging may be applied before or after --filter - and --limit depending on the service. - - --sort-by=[FIELD,...] - Comma-separated list of resource field key names to sort by. The - default order is ascending. Prefix a field with ``~'' for descending - order on that field. This flag interacts with other flags that are - applied in this order: --flatten, --sort-by, --filter, --limit. - - --uri - Print a list of resource URIs instead of the default output, and change - the command output to a list of URIs. If this flag is used with - --format, the formatting is applied on this URI list. To display URIs - alongside other keys instead, use the uri() transform. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --configuration, --flags-file, --flatten, --format, - --help, --impersonate-service-account, --log-http, --project, --quiet, - --trace-token, --user-output-enabled, --verbosity. - - Run $ gcloud help for details. - -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/vmware/network-policies/update b/gcloud/alpha/vmware/network-policies/update deleted file mode 100644 index 6bac74abc..000000000 --- a/gcloud/alpha/vmware/network-policies/update +++ /dev/null @@ -1,93 +0,0 @@ -NAME - gcloud alpha vmware network-policies update - update a VMware Engine - network policy - -SYNOPSIS - gcloud alpha vmware network-policies update - (NETWORK_POLICY : --location=LOCATION) [--async] - [--description=DESCRIPTION] [--edge-services-cidr=EDGE_SERVICES_CIDR] - [--external-ip-access] [--internet-access] [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (ALPHA) Update a VMware Engine network policy. - -EXAMPLES - To update a network policy named my-network-policy so that it disables the - external IP access service, run: - - $ gcloud alpha vmware network-policies update my-network-policy \ - --location=us-west2 --project=my-project --no-external-ip-access - - Or: - - $ gcloud alpha vmware network-policies update my-network-policy \ - --no-external-ip-access - - In the second example, the project and the location are taken from gcloud - properties core/project and compute/regions respectively. - -POSITIONAL ARGUMENTS - VMware Engine Network Policy resource - network_policy. 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 network_policy on the command line with a fully - specified name; - ◆ set the property core/project; - ◆ provide the argument --project on the command line. - - This must be specified. - - NETWORK_POLICY - ID of the VMware Engine Network Policy or fully qualified identifier - for the VMware Engine Network Policy. To set the network-policy - attribute: - ▸ provide the argument network_policy on the command line. - - This positional must be specified if any of the other arguments in - this group are specified. - - --location=LOCATION - The resource name of the location. To set the location attribute: - ▸ provide the argument network_policy on the command line with a - fully specified name; - ▸ provide the argument --location on the command line; - ▸ set the property compute/region. - -FLAGS - --async - Return immediately, without waiting for the operation in progress to - complete. The default is True. Enabled by default, use --no-async to - disable. - - --description=DESCRIPTION - Updated description for the network policy. - - --edge-services-cidr=EDGE_SERVICES_CIDR - Updated IP address range to use for internet access and external IP - access gateways, in CIDR notation. - - --external-ip-access - Enable or disable network service that allows external IP addresses to - be assigned to VMware workloads. To enable this service, - internet-access must also be enabled. Use --no-external-ip-access to - disable. - - --internet-access - Enable or disable network service that allows VMware workloads to - access the internet. Use --no-internet-access to disable. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --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/vmware/node-types/describe b/gcloud/alpha/vmware/node-types/describe deleted file mode 100644 index a25454649..000000000 --- a/gcloud/alpha/vmware/node-types/describe +++ /dev/null @@ -1,66 +0,0 @@ -NAME - gcloud alpha vmware node-types describe - display data associated with a - Google Cloud VMware Engine node type - -SYNOPSIS - gcloud alpha vmware node-types describe (NODE_TYPE : --location=LOCATION) - [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (ALPHA) Display data associated with a VMware Engine node type, such as its - compute, storage, and memory. - -EXAMPLES - To describe node type standard-72 in location us-west1-a, run: - - $ gcloud alpha vmware node-types describe standard-72 \ - --location=us-central1 --project=my-project - - Or: - - $ gcloud alpha vmware node-types describe standard-72 - - In the second example, the project and location are taken from gcloud - properties core/project and compute/zone. - -POSITIONAL ARGUMENTS - Node type resource - node_type. The arguments in this group can be used to - specify the attributes of this resource. (NOTE) Some attributes are not - given arguments in this group but can be set in other ways. To set the - project attribute: - ◆ provide the argument node_type on the command line with a fully - specified name; - ◆ set the property core/project; - ◆ provide the argument --project on the command line. - - This must be specified. - - NODE_TYPE - ID of the node type or fully qualified identifier for the node type. - To set the node-type attribute: - ▸ provide the argument node_type on the command line. - - This positional must be specified if any of the other arguments in - this group are specified. - - --location=LOCATION - Zone of the private cloud or cluster. To set the location attribute: - ▸ provide the argument node_type on the command line with a fully - specified name; - ▸ provide the argument --location 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. - -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/vmware/nsx/credentials/describe b/gcloud/alpha/vmware/nsx/credentials/describe deleted file mode 100644 index 33071275b..000000000 --- a/gcloud/alpha/vmware/nsx/credentials/describe +++ /dev/null @@ -1,69 +0,0 @@ -NAME - gcloud alpha vmware nsx credentials describe - retrieve VMware NSX sign-in - credentials associated with a Google Cloud VMware Engine private cloud - -SYNOPSIS - gcloud alpha vmware nsx credentials describe - (--private-cloud=PRIVATE_CLOUD : --location=LOCATION) - [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (ALPHA) Retrieve VMware NSX sign-in credentials associated with a VMware - Engine private cloud. - -EXAMPLES - To get sign-in credentials for NSX in private cloud my-private-cloud, run: - - $ gcloud alpha vmware nsx credentials describe \ - --private-cloud=my-private-cloud --location=us-west2-a \ - --project=my-project - - Or: - - $ gcloud alpha vmware nsx credentials describe \ - --private-cloud=my-private-cloud - - In the second example, the project and location are taken from gcloud - properties core/project and compute/zone. - -REQUIRED FLAGS - Private cloud resource - private_cloud. 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 --private-cloud on the command line with a fully - specified name; - ◆ set the property core/project; - ◆ provide the argument --project on the command line. - - This must be specified. - - --private-cloud=PRIVATE_CLOUD - ID of the private cloud or fully qualified identifier for the private - cloud. To set the private-cloud attribute: - ▸ provide the argument --private-cloud on the command line. - - This flag must be specified if any of the other arguments in this - group are specified. - - --location=LOCATION - Zone of the private cloud or cluster. To set the location attribute: - ▸ provide the argument --private-cloud on the command line with a - fully specified name; - ▸ provide the argument --location 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. - -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/vmware/nsx/credentials/help b/gcloud/alpha/vmware/nsx/credentials/help deleted file mode 100644 index f279060a4..000000000 --- a/gcloud/alpha/vmware/nsx/credentials/help +++ /dev/null @@ -1,32 +0,0 @@ -NAME - gcloud alpha vmware nsx credentials - manage VMware NSX credentials using - Google Cloud VMware Engine - -SYNOPSIS - gcloud alpha vmware nsx credentials COMMAND [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (ALPHA) Manage VMware NSX credentials using Google Cloud VMware Engine. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --help. - - Run $ gcloud help for details. - -COMMANDS - COMMAND is one of the following: - - describe - (ALPHA) Retrieve VMware NSX sign-in credentials associated with a - Google Cloud VMware Engine private cloud. - - reset - (ALPHA) Reset VMware NSX sign-in credentials associated with a Google - Cloud VMware Engine private cloud. - -NOTES - This command is currently in alpha and might change without notice. If this - command fails with API permission errors despite specifying the correct - project, you might be trying to access an API with an invitation-only early - access allowlist. - diff --git a/gcloud/alpha/vmware/nsx/credentials/reset b/gcloud/alpha/vmware/nsx/credentials/reset deleted file mode 100644 index a54e08898..000000000 --- a/gcloud/alpha/vmware/nsx/credentials/reset +++ /dev/null @@ -1,76 +0,0 @@ -NAME - gcloud alpha vmware nsx credentials reset - reset VMware NSX sign-in - credentials associated with a Google Cloud VMware Engine private cloud - -SYNOPSIS - gcloud alpha vmware nsx credentials reset - (--private-cloud=PRIVATE_CLOUD : --location=LOCATION) [--async] - [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (ALPHA) Reset VMware NSX sign-in credentials associated with a VMware - Engine private cloud. - -EXAMPLES - To reset sign-in credentials for NSX in private cloud my-private-cloud, - run: - - $ gcloud alpha vmware nsx credentials reset \ - --private-cloud=my-private-cloud --location=us-west2-a \ - --project=my-project - - Or: - - $ gcloud alpha vmware nsx credentials reset \ - --private-cloud=my-private-cloud - - In the second example, the project and location are taken from gcloud - properties core/project and compute/zone. - -REQUIRED FLAGS - Private cloud resource - private_cloud. 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 --private-cloud on the command line with a fully - specified name; - ◆ set the property core/project; - ◆ provide the argument --project on the command line. - - This must be specified. - - --private-cloud=PRIVATE_CLOUD - ID of the private cloud or fully qualified identifier for the private - cloud. To set the private-cloud attribute: - ▸ provide the argument --private-cloud on the command line. - - This flag must be specified if any of the other arguments in this - group are specified. - - --location=LOCATION - Zone of the private cloud or cluster. To set the location attribute: - ▸ provide the argument --private-cloud on the command line with a - fully specified name; - ▸ provide the argument --location on the command line; - ▸ set the property compute/zone. - -OPTIONAL FLAGS - --async - Return immediately, without waiting for the operation in progress to - complete. The default is True. Enabled by default, use --no-async to - disable. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --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/vmware/nsx/help b/gcloud/alpha/vmware/nsx/help deleted file mode 100644 index 2427f16f0..000000000 --- a/gcloud/alpha/vmware/nsx/help +++ /dev/null @@ -1,26 +0,0 @@ -NAME - gcloud alpha vmware nsx - manage NSX using Google Cloud VMware Engine - -SYNOPSIS - gcloud alpha vmware nsx GROUP [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (ALPHA) Manage NSX using Google Cloud VMware Engine. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --help. - - Run $ gcloud help for details. - -GROUPS - GROUP is one of the following: - - credentials - (ALPHA) Manage VMware NSX credentials using Google Cloud VMware Engine. - -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/vmware/private-clouds/create b/gcloud/alpha/vmware/private-clouds/create deleted file mode 100644 index f4a676f24..000000000 --- a/gcloud/alpha/vmware/private-clouds/create +++ /dev/null @@ -1,145 +0,0 @@ -NAME - gcloud alpha vmware private-clouds create - create a VMware Engine private - cloud - -SYNOPSIS - gcloud alpha vmware private-clouds create - (PRIVATE_CLOUD : --location=LOCATION) --cluster=CLUSTER - --management-range=MANAGEMENT_RANGE --network=NETWORK - --node-count=NODE_COUNT --node-type=NODE_TYPE [--async] - [--description=DESCRIPTION] [--network-project=NETWORK_PROJECT] - [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (ALPHA) Create a VMware Engine private cloud. Private cloud creation is - considered finished when the private cloud is in READY state. Check the - progress of a private cloud using gcloud alpha vmware private-clouds list. - -EXAMPLES - To create a private cloud in the us-west2-a zone using standard-72 nodes - that connects to the default-vpc VPC network of another project, run: - - $ gcloud alpha vmware private-clouds create my-private-cloud \ - --location=us-west2-a --project=my-project \ - --cluster=my-management-cluster --node-type=standard-72 \ - --node-count=3 --management-range=192.168.0.0/24 \ - --network=default-vpc --network-project=another-project - - Or: - - $ gcloud alpha vmware private-clouds create my-private-cloud \ - --cluster=my-management-cluster --node-type=standard-72 \ - --node-count=3 --management-range=192.168.0.0/24 \ - --network=default-vpc --network-project=another-project - - In the second example, the project and location are taken from gcloud - properties core/project and compute/zone. - -POSITIONAL ARGUMENTS - Private cloud resource - private_cloud. 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 private_cloud on the command line with a fully - specified name; - ◆ set the property core/project; - ◆ provide the argument --project on the command line. - - This must be specified. - - PRIVATE_CLOUD - ID of the private cloud or fully qualified identifier for the private - cloud. To set the private-cloud attribute: - ▸ provide the argument private_cloud on the command line. - - This positional must be specified if any of the other arguments in - this group are specified. - - --location=LOCATION - Zone of the private cloud or cluster. To set the location attribute: - ▸ provide the argument private_cloud on the command line with a - fully specified name; - ▸ provide the argument --location on the command line; - ▸ set the property compute/zone. - -REQUIRED FLAGS - Cluster resource - cluster. 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 --cluster on the command line with a fully - specified name; - ◆ set the property core/project; - ◆ provide the argument --project on the command line. To set the - location attribute: - ◆ provide the argument --cluster on the command line with a fully - specified name; - ◆ set the property compute/zone. To set the private-cloud attribute: - ◆ provide the argument --cluster on the command line with a fully - specified name. - - This must be specified. - - --cluster=CLUSTER - ID of the cluster or fully qualified identifier for the cluster. To - set the cluster attribute: - ▸ provide the argument --cluster on the command line. - - --management-range=MANAGEMENT_RANGE - IP address range in the private cloud to use for management appliances, - in CIDR format. Use an IP address range that meets the VMware Engine - networking requirements - (https://cloud.google.com/vmware-engine/docs/quickstart-networking-requirements). - - --network=NETWORK - Network ID of the Google Cloud VPC network to connect with your private - cloud. - - --node-count=NODE_COUNT - Number of nodes in the management cluster. - - Node type resource - node_type. 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 --node-type on the command line with a fully - specified name; - ◆ set the property core/project; - ◆ provide the argument --project on the command line. To set the - location attribute: - ◆ provide the argument --node-type on the command line with a fully - specified name; - ◆ set the property compute/zone. - - This must be specified. - - --node-type=NODE_TYPE - ID of the node type or fully qualified identifier for the node type. - To set the node-type attribute: - ▸ provide the argument --node-type on the command line. - -OPTIONAL FLAGS - --async - Return immediately, without waiting for the operation in progress to - complete. The default is True. Enabled by default, use --no-async to - disable. - - --description=DESCRIPTION - Text describing the private cloud. - - --network-project=NETWORK_PROJECT - Project ID or project name of the VPC network. Use this flag when the - VPC network is in another project. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --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/vmware/private-clouds/delete b/gcloud/alpha/vmware/private-clouds/delete deleted file mode 100644 index a6b08c4b3..000000000 --- a/gcloud/alpha/vmware/private-clouds/delete +++ /dev/null @@ -1,79 +0,0 @@ -NAME - gcloud alpha vmware private-clouds delete - delete a Google Cloud VMware - Engine private cloud - -SYNOPSIS - gcloud alpha vmware private-clouds delete - (PRIVATE_CLOUD : --location=LOCATION) [--async] - [--delay-hours=DELAY_HOURS; default=3] [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (ALPHA) Marks a VMware Engine private cloud for deletion. The resource is - deleted 3 hours after being marked for deletion. This process can be - reversed by using gcloud alpha vmware private-clouds undelete. - -EXAMPLES - To mark a private cloud called my-private-cloud for deletion, run: - - $ gcloud alpha vmware private-clouds delete my-private-cloud \ - --location=us-west2-a --project=my-project - - Or: - - $ gcloud alpha vmware private-clouds delete my-private-cloud - - In the second example, the project and location are taken from gcloud - properties core/project and compute/zone. - -POSITIONAL ARGUMENTS - Private cloud resource - private_cloud. 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 private_cloud on the command line with a fully - specified name; - ◆ set the property core/project; - ◆ provide the argument --project on the command line. - - This must be specified. - - PRIVATE_CLOUD - ID of the private cloud or fully qualified identifier for the private - cloud. To set the private-cloud attribute: - ▸ provide the argument private_cloud on the command line. - - This positional must be specified if any of the other arguments in - this group are specified. - - --location=LOCATION - Zone of the private cloud or cluster. To set the location attribute: - ▸ provide the argument private_cloud on the command line with a - fully specified name; - ▸ provide the argument --location on the command line; - ▸ set the property compute/zone. - -FLAGS - --async - Return immediately, without waiting for the operation in progress to - complete. The default is True. Enabled by default, use --no-async to - disable. - - --delay-hours=DELAY_HOURS; default=3 - Number of hours to wait before deleting the private cloud. Specifying a - value of 0 for this field begins the deletion process immediately. - DELAY_HOURS must be one of: 0, 1, 2, 3, 4, 5, 6, 7, 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. - -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/vmware/private-clouds/describe b/gcloud/alpha/vmware/private-clouds/describe deleted file mode 100644 index cd1c1b67b..000000000 --- a/gcloud/alpha/vmware/private-clouds/describe +++ /dev/null @@ -1,66 +0,0 @@ -NAME - gcloud alpha vmware private-clouds describe - describe a Google Cloud - VMware Engine private cloud - -SYNOPSIS - gcloud alpha vmware private-clouds describe - (PRIVATE_CLOUD : --location=LOCATION) [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (ALPHA) Describe a VMware Engine private cloud. - -EXAMPLES - To get a description of a private cloud called my-private-cloud in project - my-project and zone us-west2-a, run: - - $ gcloud alpha vmware private-clouds describe my-private-cloud \ - --location=us-west2-a --project=my-project - - Or: - - $ gcloud alpha vmware private-clouds describe my-private-cloud - - In the second example, the project and location are taken from gcloud - properties core/project and compute/zone. - -POSITIONAL ARGUMENTS - Private cloud resource - private_cloud. 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 private_cloud on the command line with a fully - specified name; - ◆ set the property core/project; - ◆ provide the argument --project on the command line. - - This must be specified. - - PRIVATE_CLOUD - ID of the private cloud or fully qualified identifier for the private - cloud. To set the private-cloud attribute: - ▸ provide the argument private_cloud on the command line. - - This positional must be specified if any of the other arguments in - this group are specified. - - --location=LOCATION - Zone of the private cloud or cluster. To set the location attribute: - ▸ provide the argument private_cloud on the command line with a - fully specified name; - ▸ provide the argument --location 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. - -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/vmware/private-clouds/help b/gcloud/alpha/vmware/private-clouds/help deleted file mode 100644 index b31b0a58b..000000000 --- a/gcloud/alpha/vmware/private-clouds/help +++ /dev/null @@ -1,42 +0,0 @@ -NAME - gcloud alpha vmware private-clouds - manage private clouds in Google Cloud - VMware Engine - -SYNOPSIS - gcloud alpha vmware private-clouds COMMAND [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (ALPHA) Manage private clouds in Google Cloud VMware Engine. - -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 VMware Engine private cloud. - - delete - (ALPHA) Delete a Google Cloud VMware Engine private cloud. - - describe - (ALPHA) Describe a Google Cloud VMware Engine private cloud. - - list - (ALPHA) List Google Cloud VMware Engine private clouds. - - undelete - (ALPHA) Cancel deletion of a Google Cloud VMware Engine private cloud. - - update - (ALPHA) Update a Google Cloud VMware Engine private cloud. - -NOTES - This command is currently in alpha and might change without notice. If this - command fails with API permission errors despite specifying the correct - project, you might be trying to access an API with an invitation-only early - access allowlist. - diff --git a/gcloud/alpha/vmware/private-clouds/undelete b/gcloud/alpha/vmware/private-clouds/undelete deleted file mode 100644 index 60f118e88..000000000 --- a/gcloud/alpha/vmware/private-clouds/undelete +++ /dev/null @@ -1,72 +0,0 @@ -NAME - gcloud alpha vmware private-clouds undelete - cancel deletion of a Google - Cloud VMware Engine private cloud - -SYNOPSIS - gcloud alpha vmware private-clouds undelete - (PRIVATE_CLOUD : --location=LOCATION) [--async] [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (ALPHA) Unmark a VMware Engine private cloud that was previously marked for - deletion by gcloud alpha vmware private-clouds delete. - -EXAMPLES - To unmark a private cloud called my-private-cloud for deletion, run: - - $ gcloud alpha vmware private-clouds undelete my-private-cloud \ - --location=us-west2-a --project=my-project - - Or: - - $ gcloud alpha vmware private-clouds undelete my-private-cloud - - In the second example, the project and location are taken from gcloud - properties core/project and compute/zone. - -POSITIONAL ARGUMENTS - Private cloud resource - private_cloud. 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 private_cloud on the command line with a fully - specified name; - ◆ set the property core/project; - ◆ provide the argument --project on the command line. - - This must be specified. - - PRIVATE_CLOUD - ID of the private cloud or fully qualified identifier for the private - cloud. To set the private-cloud attribute: - ▸ provide the argument private_cloud on the command line. - - This positional must be specified if any of the other arguments in - this group are specified. - - --location=LOCATION - Zone of the private cloud or cluster. To set the location attribute: - ▸ provide the argument private_cloud on the command line with a - fully specified name; - ▸ provide the argument --location on the command line; - ▸ set the property compute/zone. - -FLAGS - --async - Return immediately, without waiting for the operation in progress to - complete. The default is True. Enabled by default, use --no-async to - disable. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --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/vmware/private-clouds/update b/gcloud/alpha/vmware/private-clouds/update deleted file mode 100644 index 26ec03ab8..000000000 --- a/gcloud/alpha/vmware/private-clouds/update +++ /dev/null @@ -1,78 +0,0 @@ -NAME - gcloud alpha vmware private-clouds update - update a Google Cloud VMware - Engine private cloud - -SYNOPSIS - gcloud alpha vmware private-clouds update - (PRIVATE_CLOUD : --location=LOCATION) [--async] - [--description=DESCRIPTION] [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (ALPHA) Update a VMware Engine private cloud. - -EXAMPLES - To update a private cloud named my-private-cloud by changing its - description to Example description run: - - $ gcloud alpha vmware private-clouds update my-private-cloud \ - --location=us-west2-a --project=my-project \ - --description='Example description' - - Or: - - $ gcloud alpha vmware private-clouds update my-private-cloud \ - --description='Example description' - - In the second example, the project and location are taken from gcloud - properties core/project and compute/zone. - -POSITIONAL ARGUMENTS - Private cloud resource - private_cloud. 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 private_cloud on the command line with a fully - specified name; - ◆ set the property core/project; - ◆ provide the argument --project on the command line. - - This must be specified. - - PRIVATE_CLOUD - ID of the private cloud or fully qualified identifier for the private - cloud. To set the private-cloud attribute: - ▸ provide the argument private_cloud on the command line. - - This positional must be specified if any of the other arguments in - this group are specified. - - --location=LOCATION - Zone of the private cloud or cluster. To set the location attribute: - ▸ provide the argument private_cloud on the command line with a - fully specified name; - ▸ provide the argument --location on the command line; - ▸ set the property compute/zone. - -FLAGS - --async - Return immediately, without waiting for the operation in progress to - complete. The default is True. Enabled by default, use --no-async to - disable. - - --description=DESCRIPTION - Text describing the private cloud - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --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/vmware/vcenter/credentials/describe b/gcloud/alpha/vmware/vcenter/credentials/describe deleted file mode 100644 index c0c6b9af4..000000000 --- a/gcloud/alpha/vmware/vcenter/credentials/describe +++ /dev/null @@ -1,70 +0,0 @@ -NAME - gcloud alpha vmware vcenter credentials describe - describe Google Cloud - VMware Engine vCenter credentials - -SYNOPSIS - gcloud alpha vmware vcenter credentials describe - (--private-cloud=PRIVATE_CLOUD : --location=LOCATION) - [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (ALPHA) Retrieve VMware vCenter sign-in credentials associated with a - VMware Engine private cloud. - -EXAMPLES - To get sign-in credentials for vCenter in private cloud my-private-cloud, - run: - - $ gcloud alpha vmware vcenter credentials describe \ - --private-cloud=my-private-cloud --location=us-west2-a \ - --project=my-project - - Or: - - $ gcloud alpha vmware vcenter credentials describe \ - --private-cloud=my-private-cloud - - In the second example, the project and location are taken from gcloud - properties core/project and compute/zone. - -REQUIRED FLAGS - Private cloud resource - private_cloud. 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 --private-cloud on the command line with a fully - specified name; - ◆ set the property core/project; - ◆ provide the argument --project on the command line. - - This must be specified. - - --private-cloud=PRIVATE_CLOUD - ID of the private cloud or fully qualified identifier for the private - cloud. To set the private-cloud attribute: - ▸ provide the argument --private-cloud on the command line. - - This flag must be specified if any of the other arguments in this - group are specified. - - --location=LOCATION - Zone of the private cloud or cluster. To set the location attribute: - ▸ provide the argument --private-cloud on the command line with a - fully specified name; - ▸ provide the argument --location 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. - -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/vmware/vcenter/credentials/help b/gcloud/alpha/vmware/vcenter/credentials/help deleted file mode 100644 index 02926a011..000000000 --- a/gcloud/alpha/vmware/vcenter/credentials/help +++ /dev/null @@ -1,31 +0,0 @@ -NAME - gcloud alpha vmware vcenter credentials - manage VMware vCenter credentials - using Google Cloud VMware Engine - -SYNOPSIS - gcloud alpha vmware vcenter credentials COMMAND [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (ALPHA) Manage VMware vCenter credentials using Google Cloud VMware Engine. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --help. - - Run $ gcloud help for details. - -COMMANDS - COMMAND is one of the following: - - describe - (ALPHA) Describe Google Cloud VMware Engine vCenter credentials. - - reset - (ALPHA) Reset VMware vCenter sign-in credentials associated with a - Google Cloud VMware Engine private cloud. - -NOTES - This command is currently in alpha and might change without notice. If this - command fails with API permission errors despite specifying the correct - project, you might be trying to access an API with an invitation-only early - access allowlist. - diff --git a/gcloud/alpha/vmware/vcenter/credentials/reset b/gcloud/alpha/vmware/vcenter/credentials/reset deleted file mode 100644 index 41db9666e..000000000 --- a/gcloud/alpha/vmware/vcenter/credentials/reset +++ /dev/null @@ -1,77 +0,0 @@ -NAME - gcloud alpha vmware vcenter credentials reset - reset VMware vCenter - sign-in credentials associated with a Google Cloud VMware Engine - private cloud - -SYNOPSIS - gcloud alpha vmware vcenter credentials reset - (--private-cloud=PRIVATE_CLOUD : --location=LOCATION) [--async] - [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (ALPHA) Reset VMware vCenter sign-in credentials associated with a VMware - Engine private cloud. - -EXAMPLES - To reset sign-in credentials for vCenter in private cloud my-private-cloud, - run: - - $ gcloud alpha vmware vcenter credentials reset \ - --private-cloud=my-private-cloud --location=us-west2-a \ - --project=my-project - - Or: - - $ gcloud alpha vmware vcenter credentials reset \ - --private-cloud=my-private-cloud - - In the second example, the project and location are taken from gcloud - properties core/project and compute/zone. - -REQUIRED FLAGS - Private cloud resource - private_cloud. 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 --private-cloud on the command line with a fully - specified name; - ◆ set the property core/project; - ◆ provide the argument --project on the command line. - - This must be specified. - - --private-cloud=PRIVATE_CLOUD - ID of the private cloud or fully qualified identifier for the private - cloud. To set the private-cloud attribute: - ▸ provide the argument --private-cloud on the command line. - - This flag must be specified if any of the other arguments in this - group are specified. - - --location=LOCATION - Zone of the private cloud or cluster. To set the location attribute: - ▸ provide the argument --private-cloud on the command line with a - fully specified name; - ▸ provide the argument --location on the command line; - ▸ set the property compute/zone. - -OPTIONAL FLAGS - --async - Return immediately, without waiting for the operation in progress to - complete. The default is True. Enabled by default, use --no-async to - disable. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --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/vmware/vcenter/help b/gcloud/alpha/vmware/vcenter/help deleted file mode 100644 index b5f135c5f..000000000 --- a/gcloud/alpha/vmware/vcenter/help +++ /dev/null @@ -1,28 +0,0 @@ -NAME - gcloud alpha vmware vcenter - manage vCenter resources in Google Cloud - VMware Engine - -SYNOPSIS - gcloud alpha vmware vcenter GROUP [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (ALPHA) Manage vCenter resources in Google Cloud VMware Engine. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --help. - - Run $ gcloud help for details. - -GROUPS - GROUP is one of the following: - - credentials - (ALPHA) Manage VMware vCenter credentials using Google Cloud VMware - Engine. - -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/anthos/config/controller/create b/gcloud/anthos/config/controller/create index d952c1f4b..ad5c2bf45 100644 --- a/gcloud/anthos/config/controller/create +++ b/gcloud/anthos/config/controller/create @@ -6,6 +6,7 @@ SYNOPSIS gcloud anthos config controller create (NAME : --location=LOCATION) [--async] [--cluster-ipv4-cidr-block=CLUSTER_IPV4_CIDR_BLOCK] [--cluster-named-range=CLUSTER_NAMED_RANGE] [--man-block=MAN_BLOCK] + [--man-blocks=[BLOCK,...]] [--master-ipv4-cidr-block=MASTER_IPV4_CIDR_BLOCK] [--network=NETWORK] [--services-ipv4-cidr-block=SERVICES_IPV4_CIDR_BLOCK] [--services-named-range=SERVICES_NAMED_RANGE] [--subnet=SUBNET] @@ -67,8 +68,16 @@ FLAGS used to automatically create a GKE-managed one. --man-block=MAN_BLOCK - Master Authorized Network. Allows access to the Kubernetes control - plane from this block. Defaults to '0.0.0.0/0' if flag is not provided. + (DEPRECATED) Master Authorized Network. Allows access to the Kubernetes + control plane from this block. Defaults to 0.0.0.0/0 if flag is not + provided. + + The --man-block option is deprecated; use --man-blocks instead. + + --man-blocks=[BLOCK,...] + Master Authorized Network. Allows users to specify multiple blocks to + access the Kubernetescontrol plane from this block. Defaults to + 0.0.0.0/0 if flag is not provided. --master-ipv4-cidr-block=MASTER_IPV4_CIDR_BLOCK The /28 network that the control plane will use. Defaults to diff --git a/gcloud/artifacts/apt/import b/gcloud/artifacts/apt/import index e9ed5ce72..112a943e5 100644 --- a/gcloud/artifacts/apt/import +++ b/gcloud/artifacts/apt/import @@ -3,7 +3,7 @@ NAME artifact repository SYNOPSIS - gcloud artifacts apt import (REPOSITORY : --location=LOCATION) + gcloud artifacts apt import [[REPOSITORY] --location=LOCATION] --gcs-source=[GCS_SOURCE,...] [--async] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -43,24 +43,24 @@ POSITIONAL ARGUMENTS the project attribute: ◆ provide the argument repository on the command line with a fully specified name; + ◆ set the property artifacts/repository with a fully specified name; ◆ provide the argument --project on the command line; ◆ set the property core/project. - This must be specified. - - REPOSITORY + [REPOSITORY] ID of the repository or fully qualified identifier for the repository. To set the repository attribute: - ▸ provide the argument repository on the command line. - - This positional must be specified if any of the other arguments in - this group are specified. + ▸ provide the argument repository on the command line; + ▸ set the property artifacts/repository. --location=LOCATION Location of the repository. To set the location attribute: ▸ provide the argument repository on the command line with a fully specified name; - ▸ provide the argument --location on the command line. + ▸ set the property artifacts/repository with a fully specified + name; + ▸ provide the argument --location on the command line; + ▸ set the property artifacts/location. REQUIRED FLAGS --gcs-source=[GCS_SOURCE,...] diff --git a/gcloud/artifacts/apt/upload b/gcloud/artifacts/apt/upload index fa32f54f6..b1b7a8201 100644 --- a/gcloud/artifacts/apt/upload +++ b/gcloud/artifacts/apt/upload @@ -3,7 +3,7 @@ NAME repository SYNOPSIS - gcloud artifacts apt upload (REPOSITORY : --location=LOCATION) + gcloud artifacts apt upload [[REPOSITORY] --location=LOCATION] --source=SOURCE [--async] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -24,24 +24,24 @@ POSITIONAL ARGUMENTS the project attribute: ◆ provide the argument repository on the command line with a fully specified name; + ◆ set the property artifacts/repository with a fully specified name; ◆ provide the argument --project on the command line; ◆ set the property core/project. - This must be specified. - - REPOSITORY + [REPOSITORY] ID of the repository or fully qualified identifier for the repository. To set the repository attribute: - ▸ provide the argument repository on the command line. - - This positional must be specified if any of the other arguments in - this group are specified. + ▸ provide the argument repository on the command line; + ▸ set the property artifacts/repository. --location=LOCATION Location of the repository. To set the location attribute: ▸ provide the argument repository on the command line with a fully specified name; - ▸ provide the argument --location on the command line. + ▸ set the property artifacts/repository with a fully specified + name; + ▸ provide the argument --location on the command line; + ▸ set the property artifacts/location. REQUIRED FLAGS --source=SOURCE diff --git a/gcloud/artifacts/files/list b/gcloud/artifacts/files/list index d97e8044c..77897becd 100644 --- a/gcloud/artifacts/files/list +++ b/gcloud/artifacts/files/list @@ -3,7 +3,7 @@ NAME SYNOPSIS gcloud artifacts files list [--package=PACKAGE] [--tag=TAG] - [--version=VERSION] [--repository=REPOSITORY : --location=LOCATION] + [--version=VERSION] [--location=LOCATION --repository=REPOSITORY] [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [GCLOUD_WIDE_FLAG ...] @@ -64,22 +64,24 @@ FLAGS the project attribute: ◆ provide the argument --repository on the command line with a fully specified name; + ◆ set the property artifacts/repository with a fully specified name; ◆ provide the argument --project on the command line; ◆ set the property core/project. - --repository=REPOSITORY - ID of the repository or fully qualified identifier for the - repository. To set the repository attribute: - ▸ provide the argument --repository on the command line. - - This flag must be specified if any of the other arguments in this - group are specified. - --location=LOCATION Location of the repository. To set the location attribute: ▸ provide the argument --repository on the command line with a fully specified name; - ▸ provide the argument --location on the command line. + ▸ set the property artifacts/repository with a fully specified + name; + ▸ provide the argument --location on the command line; + ▸ set the property artifacts/location. + + --repository=REPOSITORY + ID of the repository or fully qualified identifier for the + repository. To set the repository attribute: + ▸ provide the argument --repository on the command line; + ▸ set the property artifacts/repository. LIST COMMAND FLAGS --filter=EXPRESSION diff --git a/gcloud/artifacts/print-settings/gradle b/gcloud/artifacts/print-settings/gradle index 7b943dd13..aee6fb47b 100644 --- a/gcloud/artifacts/print-settings/gradle +++ b/gcloud/artifacts/print-settings/gradle @@ -4,7 +4,7 @@ NAME SYNOPSIS gcloud artifacts print-settings gradle [--json-key=JSON_KEY] - [--repository=REPOSITORY : --location=LOCATION] [GCLOUD_WIDE_FLAG ...] + [--location=LOCATION --repository=REPOSITORY] [GCLOUD_WIDE_FLAG ...] DESCRIPTION Print a snippet to add a repository to the Gradle build.gradle file. @@ -36,22 +36,24 @@ FLAGS the project attribute: ◆ provide the argument --repository on the command line with a fully specified name; + ◆ set the property artifacts/repository with a fully specified name; ◆ provide the argument --project on the command line; ◆ set the property core/project. - --repository=REPOSITORY - ID of the repository or fully qualified identifier for the - repository. To set the repository attribute: - ▸ provide the argument --repository on the command line. - - This flag must be specified if any of the other arguments in this - group are specified. - --location=LOCATION Location of the repository. To set the location attribute: ▸ provide the argument --repository on the command line with a fully specified name; - ▸ provide the argument --location on the command line. + ▸ set the property artifacts/repository with a fully specified + name; + ▸ provide the argument --location on the command line; + ▸ set the property artifacts/location. + + --repository=REPOSITORY + ID of the repository or fully qualified identifier for the + repository. To set the repository attribute: + ▸ provide the argument --repository on the command line; + ▸ set the property artifacts/repository. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/artifacts/print-settings/mvn b/gcloud/artifacts/print-settings/mvn index ae89dc69c..aba9e14c8 100644 --- a/gcloud/artifacts/print-settings/mvn +++ b/gcloud/artifacts/print-settings/mvn @@ -4,7 +4,7 @@ NAME SYNOPSIS gcloud artifacts print-settings mvn [--json-key=JSON_KEY] - [--repository=REPOSITORY : --location=LOCATION] [GCLOUD_WIDE_FLAG ...] + [--location=LOCATION --repository=REPOSITORY] [GCLOUD_WIDE_FLAG ...] DESCRIPTION Print a snippet to add a Maven repository to the pom.xml file. @@ -36,22 +36,24 @@ FLAGS the project attribute: ◆ provide the argument --repository on the command line with a fully specified name; + ◆ set the property artifacts/repository with a fully specified name; ◆ provide the argument --project on the command line; ◆ set the property core/project. - --repository=REPOSITORY - ID of the repository or fully qualified identifier for the - repository. To set the repository attribute: - ▸ provide the argument --repository on the command line. - - This flag must be specified if any of the other arguments in this - group are specified. - --location=LOCATION Location of the repository. To set the location attribute: ▸ provide the argument --repository on the command line with a fully specified name; - ▸ provide the argument --location on the command line. + ▸ set the property artifacts/repository with a fully specified + name; + ▸ provide the argument --location on the command line; + ▸ set the property artifacts/location. + + --repository=REPOSITORY + ID of the repository or fully qualified identifier for the + repository. To set the repository attribute: + ▸ provide the argument --repository on the command line; + ▸ set the property artifacts/repository. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/artifacts/print-settings/npm b/gcloud/artifacts/print-settings/npm index 32dd6ad19..61c00b475 100644 --- a/gcloud/artifacts/print-settings/npm +++ b/gcloud/artifacts/print-settings/npm @@ -4,7 +4,7 @@ NAME SYNOPSIS gcloud artifacts print-settings npm [--json-key=JSON_KEY] [--scope=SCOPE] - [--repository=REPOSITORY : --location=LOCATION] [GCLOUD_WIDE_FLAG ...] + [--location=LOCATION --repository=REPOSITORY] [GCLOUD_WIDE_FLAG ...] DESCRIPTION Print credential settings to add to the .npmrc file for connecting to an @@ -46,22 +46,24 @@ FLAGS the project attribute: ◆ provide the argument --repository on the command line with a fully specified name; + ◆ set the property artifacts/repository with a fully specified name; ◆ provide the argument --project on the command line; ◆ set the property core/project. - --repository=REPOSITORY - ID of the repository or fully qualified identifier for the - repository. To set the repository attribute: - ▸ provide the argument --repository on the command line. - - This flag must be specified if any of the other arguments in this - group are specified. - --location=LOCATION Location of the repository. To set the location attribute: ▸ provide the argument --repository on the command line with a fully specified name; - ▸ provide the argument --location on the command line. + ▸ set the property artifacts/repository with a fully specified + name; + ▸ provide the argument --location on the command line; + ▸ set the property artifacts/location. + + --repository=REPOSITORY + ID of the repository or fully qualified identifier for the + repository. To set the repository attribute: + ▸ provide the argument --repository on the command line; + ▸ set the property artifacts/repository. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/artifacts/print-settings/python b/gcloud/artifacts/print-settings/python index 1119c2388..769be387f 100644 --- a/gcloud/artifacts/print-settings/python +++ b/gcloud/artifacts/print-settings/python @@ -4,7 +4,7 @@ NAME SYNOPSIS gcloud artifacts print-settings python [--json-key=JSON_KEY] - [--repository=REPOSITORY : --location=LOCATION] [GCLOUD_WIDE_FLAG ...] + [--location=LOCATION --repository=REPOSITORY] [GCLOUD_WIDE_FLAG ...] DESCRIPTION Print credential settings to add to the .pypirc and pip.conf files for @@ -37,22 +37,24 @@ FLAGS the project attribute: ◆ provide the argument --repository on the command line with a fully specified name; + ◆ set the property artifacts/repository with a fully specified name; ◆ provide the argument --project on the command line; ◆ set the property core/project. - --repository=REPOSITORY - ID of the repository or fully qualified identifier for the - repository. To set the repository attribute: - ▸ provide the argument --repository on the command line. - - This flag must be specified if any of the other arguments in this - group are specified. - --location=LOCATION Location of the repository. To set the location attribute: ▸ provide the argument --repository on the command line with a fully specified name; - ▸ provide the argument --location on the command line. + ▸ set the property artifacts/repository with a fully specified + name; + ▸ provide the argument --location on the command line; + ▸ set the property artifacts/location. + + --repository=REPOSITORY + ID of the repository or fully qualified identifier for the + repository. To set the repository attribute: + ▸ provide the argument --repository on the command line; + ▸ set the property artifacts/repository. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/artifacts/repositories/list b/gcloud/artifacts/repositories/list index e23c08310..4d2116aec 100644 --- a/gcloud/artifacts/repositories/list +++ b/gcloud/artifacts/repositories/list @@ -3,7 +3,7 @@ NAME project SYNOPSIS - gcloud artifacts repositories list --location=LOCATION + gcloud artifacts repositories list [--location=LOCATION] [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [GCLOUD_WIDE_FLAG ...] @@ -28,13 +28,15 @@ FLAGS set in other ways. To set the project attribute: ◆ provide the argument --location on the command line with a fully specified name; + ◆ set the property artifacts/location with a fully specified name; ◆ provide the argument --project on the command line; ◆ set the property core/project. --location=LOCATION ID of the location or fully qualified identifier for the location. To set the location attribute: - ▸ provide the argument --location on the command line. + ▸ provide the argument --location on the command line; + ▸ set the property artifacts/location. LIST COMMAND FLAGS --filter=EXPRESSION diff --git a/gcloud/artifacts/yum/import b/gcloud/artifacts/yum/import index 211e8560a..1bf99dce7 100644 --- a/gcloud/artifacts/yum/import +++ b/gcloud/artifacts/yum/import @@ -3,7 +3,7 @@ NAME artifact repository SYNOPSIS - gcloud artifacts yum import (REPOSITORY : --location=LOCATION) + gcloud artifacts yum import [[REPOSITORY] --location=LOCATION] --gcs-source=[GCS_SOURCE,...] [--async] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -43,24 +43,24 @@ POSITIONAL ARGUMENTS the project attribute: ◆ provide the argument repository on the command line with a fully specified name; + ◆ set the property artifacts/repository with a fully specified name; ◆ provide the argument --project on the command line; ◆ set the property core/project. - This must be specified. - - REPOSITORY + [REPOSITORY] ID of the repository or fully qualified identifier for the repository. To set the repository attribute: - ▸ provide the argument repository on the command line. - - This positional must be specified if any of the other arguments in - this group are specified. + ▸ provide the argument repository on the command line; + ▸ set the property artifacts/repository. --location=LOCATION Location of the repository. To set the location attribute: ▸ provide the argument repository on the command line with a fully specified name; - ▸ provide the argument --location on the command line. + ▸ set the property artifacts/repository with a fully specified + name; + ▸ provide the argument --location on the command line; + ▸ set the property artifacts/location. REQUIRED FLAGS --gcs-source=[GCS_SOURCE,...] diff --git a/gcloud/artifacts/yum/upload b/gcloud/artifacts/yum/upload index a43d0ef79..48c7194a9 100644 --- a/gcloud/artifacts/yum/upload +++ b/gcloud/artifacts/yum/upload @@ -3,7 +3,7 @@ NAME repository SYNOPSIS - gcloud artifacts yum upload (REPOSITORY : --location=LOCATION) + gcloud artifacts yum upload [[REPOSITORY] --location=LOCATION] --source=SOURCE [--async] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -24,24 +24,24 @@ POSITIONAL ARGUMENTS the project attribute: ◆ provide the argument repository on the command line with a fully specified name; + ◆ set the property artifacts/repository with a fully specified name; ◆ provide the argument --project on the command line; ◆ set the property core/project. - This must be specified. - - REPOSITORY + [REPOSITORY] ID of the repository or fully qualified identifier for the repository. To set the repository attribute: - ▸ provide the argument repository on the command line. - - This positional must be specified if any of the other arguments in - this group are specified. + ▸ provide the argument repository on the command line; + ▸ set the property artifacts/repository. --location=LOCATION Location of the repository. To set the location attribute: ▸ provide the argument repository on the command line with a fully specified name; - ▸ provide the argument --location on the command line. + ▸ set the property artifacts/repository with a fully specified + name; + ▸ provide the argument --location on the command line; + ▸ set the property artifacts/location. REQUIRED FLAGS --source=SOURCE diff --git a/gcloud/auth/application-default/login b/gcloud/auth/application-default/login index f85564d0a..f9ba7f887 100644 --- a/gcloud/auth/application-default/login +++ b/gcloud/auth/application-default/login @@ -45,21 +45,24 @@ EXAMPLES FLAGS --no-browser - Use this flag to authenticate the client libraries on a machine without - a web browser. + If you want to authorize the client libraries on a machine that doesn't + have a browser and you can install the gcloud CLI on another machine + with a browser, use the --no-browser flag. - Run gcloud auth login --no-browser and follow these steps: + 1. To initiate authorization, enter the following command: - 1. Copy the long command that begins with "gcloud auth login - --remote-bootstrap=". + gcloud auth application-default login --no-browser - 2. Paste and run this command on the command line of a different, + 2. Copy the long command that begins with gcloud auth + application-default login --remote-bootstrap=". + + 3. Paste and run this command on the command line of a different, trusted machine that has local installations of both a web browser and the gcloud CLI tool version 372.0 or later. - 3. Copy the long URL output from the machine with the web browser. + 4. Copy the long URL output from the machine with the web browser. - 4. Paste the long URL back to the first machine under the prompt, + 5. Paste the long URL back to the first machine under the prompt, "Enter the output of the above command", and press Enter to complete the authorization. @@ -94,7 +97,31 @@ FLAGS --launch-browser Launch a browser for authorization. If not enabled or if it is not possible to launch a browser, prints a URL to standard output to be - copied. Enabled by default, use --no-launch-browser to disable. + copied. + + If you want to authorize the client libraries on a machine that doesn't + have a browser and you cannot install the gcloud CLI on another machine + with a browser, use the --no-launch-browser flag. The + --no-launch-browser flag prevents the command from automatically + opening a web browser. + + 1. To initiate authorization, enter the following command: + + gcloud auth application-default login --no-launch-browser + + 2. Copy the long URL that begins with + https://accounts.google.com/o/oauth2/auth... + + 3. Paste this URL into the browser of a different, trusted machine that + has a web browser. + + 4. Copy the authorization code from the machine with the web browser. + + 5. Paste the authorization code back to the first machine at the + prompt, "Enter authorization code", and press Enter to complete the + authorization. + + Enabled by default, use --no-launch-browser to disable. --scopes=SCOPE,[SCOPE,...] The names of the scopes to authorize for. By default openid, diff --git a/gcloud/auth/login b/gcloud/auth/login index 29850b688..d665a31d8 100644 --- a/gcloud/auth/login +++ b/gcloud/auth/login @@ -60,21 +60,24 @@ FLAGS Minimal user output. --no-browser - Use this flag to authenticate the gcloud CLI on a machine without a web - browser. + If you want to authorize the gcloud CLI on a machine that doesn't have + a browser and you can install the gcloud CLI on another machine with a + browser, use the --no-browser flag. - Run gcloud auth login --no-browser and follow these steps: + 1. To initiate authorization, enter the following command: - 1. Copy the long command that begins with "gcloud auth login + gcloud auth login --no-browser + + 2. Copy the long command that begins with gcloud auth login --remote-bootstrap=". - 2. Paste and run this command on the command line of a different, + 3. Paste and run this command on the command line of a different, trusted machine that has local installations of both a web browser and the gcloud CLI tool version 372.0 or later. - 3. Copy the long URL output from the machine with the web browser. + 4. Copy the long URL output from the machine with the web browser. - 4. Paste the long URL back to the first machine under the prompt, + 5. Paste the long URL back to the first machine under the prompt, "Enter the output of the above command", and press Enter to complete the authorization. @@ -94,7 +97,30 @@ FLAGS --launch-browser Launch a browser for authorization. If not enabled or if it is not possible to launch a browser, prints a URL to standard output to be - copied. Enabled by default, use --no-launch-browser to disable. + copied. + + If you want to authorize the gcloud CLI on a machine that doesn't have + a browser and you cannot install the gcloud CLI on another machine with + a browser, use the --no-launch-browser flag. The --no-launch-browser + flag prevents the command from automatically opening a web browser. + + 1. To initiate authorization, enter the following command: + + gcloud auth login --no-launch-browser + + 2. Copy the long URL that begins with + https://accounts.google.com/o/oauth2/auth... + + 3. Paste this URL into the browser of a different, trusted machine that + has a web browser. + + 4. Copy the authorization code from the machine with the web browser. + + 5. Paste the authorization code back to the first machine at the + prompt, "Enter authorization code", and press Enter to complete the + authorization. + + Enabled by default, use --no-launch-browser to disable. --update-adc Write the obtained credentials to the well-known location for diff --git a/gcloud/beta/ai/custom-jobs/create b/gcloud/beta/ai/custom-jobs/create index 7c2d7b989..acd836432 100644 --- a/gcloud/beta/ai/custom-jobs/create +++ b/gcloud/beta/ai/custom-jobs/create @@ -157,7 +157,7 @@ OPTIONAL FLAGS entrypoint instruction in Dockerfile when provided. --enable-web-access - Whether you want Vertex AI to enable [interactive shell access] + Whether you want Vertex AI to enable interactive shell access (https://cloud.google.com/vertex-ai/docs/training/monitor-debug-interactive-shell) to training containers. If set to true, you can access interactive shells at the URIs given by CustomJob.web_access_uris or diff --git a/gcloud/beta/ai/hp-tuning-jobs/create b/gcloud/beta/ai/hp-tuning-jobs/create index 51f9cb562..182be9d14 100644 --- a/gcloud/beta/ai/hp-tuning-jobs/create +++ b/gcloud/beta/ai/hp-tuning-jobs/create @@ -61,7 +61,7 @@ OPTIONAL FLAGS of: algorithm-unspecified, grid-search, random-search. --enable-web-access - Whether you want Vertex AI to enable [interactive shell access] + Whether you want Vertex AI to enable interactive shell access (https://cloud.google.com/vertex-ai/docs/training/monitor-debug-interactive-shell) to training containers. If set to true, you can access interactive shells at the URIs given by CustomJob.web_access_uris or diff --git a/gcloud/beta/ai/models/delete-version b/gcloud/beta/ai/models/delete-version new file mode 100644 index 000000000..84cb07fe8 --- /dev/null +++ b/gcloud/beta/ai/models/delete-version @@ -0,0 +1,59 @@ +NAME + gcloud beta ai models delete-version - delete an existing Vertex AI model + version + +SYNOPSIS + gcloud beta ai models delete-version (MODEL_VERSION : --region=REGION) + [GCLOUD_WIDE_FLAG ...] + +EXAMPLES + To delete a model 123 of version 1234 under project example in region + us-central1, run: + + $ gcloud beta ai models delete-version 123@1234 --project=example \ + --region=us-central1 + +POSITIONAL ARGUMENTS + Model resource - Model version 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 model_version 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. + + MODEL_VERSION + ID of the model or fully qualified identifier for the model. To set + the name attribute: + ▸ provide the argument model_version on the command line. + + This positional must be specified if any of the other arguments in + this group are specified. + + --region=REGION + Cloud region for the model. To set the region attribute: + ▸ provide the argument model_version on the command line with a + fully specified name; + ▸ provide the argument --region on the command line; + ▸ set the property ai/region; + ▸ choose one from the prompted list of available regions. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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 ai models delete-version + + $ gcloud alpha ai models delete-version + diff --git a/gcloud/beta/ai/models/describe b/gcloud/beta/ai/models/describe index 32a9df360..aa6a2a21a 100644 --- a/gcloud/beta/ai/models/describe +++ b/gcloud/beta/ai/models/describe @@ -1,5 +1,5 @@ NAME - gcloud beta ai models describe - gets detailed model information about the + gcloud beta ai models describe - get detailed model information about the given model id SYNOPSIS diff --git a/gcloud/beta/ai/models/help b/gcloud/beta/ai/models/help index a1c794759..1b34964a3 100644 --- a/gcloud/beta/ai/models/help +++ b/gcloud/beta/ai/models/help @@ -18,11 +18,14 @@ COMMANDS delete (BETA) Delete an existing Vertex AI model. + delete-version + (BETA) Delete an existing Vertex AI model version. + describe - (BETA) Gets detailed model information about the given model id. + (BETA) Get detailed model information about the given model id. list - (BETA) Lists the models of the given project and region. + (BETA) List the models of the given project and region. upload (BETA) Upload a new model. diff --git a/gcloud/beta/ai/models/list b/gcloud/beta/ai/models/list index 788f1fa84..fca7d5540 100644 --- a/gcloud/beta/ai/models/list +++ b/gcloud/beta/ai/models/list @@ -1,5 +1,5 @@ NAME - gcloud beta ai models list - lists the models of the given project and + gcloud beta ai models list - list the models of the given project and region SYNOPSIS @@ -8,7 +8,7 @@ SYNOPSIS [GCLOUD_WIDE_FLAG ...] EXAMPLES - Lists the models of project example in region us-central1, run: + List the models of project example in region us-central1, run: $ gcloud beta ai models list --project=example --region=us-central1 diff --git a/gcloud/beta/ai/models/upload b/gcloud/beta/ai/models/upload index e236aa18e..cf12ce93a 100644 --- a/gcloud/beta/ai/models/upload +++ b/gcloud/beta/ai/models/upload @@ -13,7 +13,8 @@ SYNOPSIS [--explanation-metadata-file=EXPLANATION_METADATA_FILE] [--explanation-method=EXPLANATION_METHOD] [--explanation-path-count=EXPLANATION_PATH_COUNT] - [--explanation-step-count=EXPLANATION_STEP_COUNT] [--region=REGION] + [--explanation-step-count=EXPLANATION_STEP_COUNT] [--model-id=MODEL_ID] + [--parent-model=PARENT_MODEL] [--region=REGION] [--smooth-grad-noise-sigma=SMOOTH_GRAD_NOISE_SIGMA] [--smooth-grad-noise-sigma-by-feature=[KEY=VALUE,...]] [--smooth-grad-noisy-sample-count=SMOOTH_GRAD_NOISY_SAMPLE_COUNT] @@ -81,6 +82,14 @@ OPTIONAL FLAGS --explanation-step-count=EXPLANATION_STEP_COUNT Number of steps to approximate the path integral for explanation. + --model-id=MODEL_ID + ID to use for the uploaded Model, which will become the final component + of the model resource name. + + --parent-model=PARENT_MODEL + Resource name of the model into which to upload the version. Only + specify this field when uploading a new version. + Region resource - Cloud region to upload model. This represents a Cloud resource. (NOTE) Some attributes are not given arguments in this group but can be set in other ways. To set the project attribute: diff --git a/gcloud/beta/alloydb/instances/create b/gcloud/beta/alloydb/instances/create index 0d24a896b..9330afcde 100644 --- a/gcloud/beta/alloydb/instances/create +++ b/gcloud/beta/alloydb/instances/create @@ -7,8 +7,7 @@ SYNOPSIS --cpu-count=CPU_COUNT --instance-type=INSTANCE_TYPE --region=REGION [--async] [--availability-type=AVAILABILITY_TYPE] [--database-flags=FLAG=VALUE,[FLAG=VALUE,...]] - [--read-pool-node-count=READ_POOL_NODE_COUNT] [--zone=ZONE] - [GCLOUD_WIDE_FLAG ...] + [--read-pool-node-count=READ_POOL_NODE_COUNT] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) Creates a new AlloyDB instance within a given cluster. @@ -38,7 +37,7 @@ REQUIRED FLAGS Whole number value indicating how many vCPUs the machine should contain. Each vCPU count corresponds to a N2 high-mem machine: (https://cloud.google.com/compute/docs/general-purpose-machines#n2_machines). - CPU_COUNT must be one of: 4, 8, 16, 32, 64. + CPU_COUNT must be one of: 2, 4, 8, 16, 32, 64. --instance-type=INSTANCE_TYPE Specifies instance type. INSTANCE_TYPE must be one of: @@ -81,9 +80,6 @@ OPTIONAL FLAGS --read-pool-node-count=READ_POOL_NODE_COUNT Read capacity, i.e. number of nodes in a read pool instance. - --zone=ZONE - Primary Compute Engine zone (e.g. us-central1, us-central1, etc. - 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/alloydb/instances/update b/gcloud/beta/alloydb/instances/update index b81e35e13..941cc2926 100644 --- a/gcloud/beta/alloydb/instances/update +++ b/gcloud/beta/alloydb/instances/update @@ -6,8 +6,7 @@ SYNOPSIS gcloud beta alloydb instances update INSTANCE --cluster=CLUSTER --region=REGION [--async] [--availability-type=AVAILABILITY_TYPE] [--cpu-count=CPU_COUNT] [--database-flags=FLAG=VALUE,[FLAG=VALUE,...]] - [--read-pool-node-count=READ_POOL_NODE_COUNT] [--zone=ZONE] - [GCLOUD_WIDE_FLAG ...] + [--read-pool-node-count=READ_POOL_NODE_COUNT] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) Updates an AlloyDB instance within a given cluster. @@ -49,7 +48,7 @@ OPTIONAL FLAGS Whole number value indicating how many vCPUs the machine should contain. Each vCPU count corresponds to a N2 high-mem machine: (https://cloud.google.com/compute/docs/general-purpose-machines#n2_machines). - CPU_COUNT must be one of: 4, 8, 16, 32, 64. + CPU_COUNT must be one of: 2, 4, 8, 16, 32, 64. --database-flags=FLAG=VALUE,[FLAG=VALUE,...] Comma-separated list of database flags to set on the instance. Use an @@ -62,9 +61,6 @@ OPTIONAL FLAGS --read-pool-node-count=READ_POOL_NODE_COUNT Read capacity, i.e. number of nodes in a read pool instance. - --zone=ZONE - Primary Compute Engine zone (e.g. us-central1, us-central1, etc. - 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/artifacts/apt/import b/gcloud/beta/artifacts/apt/import index dfd9d0f40..2b4546194 100644 --- a/gcloud/beta/artifacts/apt/import +++ b/gcloud/beta/artifacts/apt/import @@ -3,7 +3,7 @@ NAME an artifact repository SYNOPSIS - gcloud beta artifacts apt import (REPOSITORY : --location=LOCATION) + gcloud beta artifacts apt import [[REPOSITORY] --location=LOCATION] --gcs-source=[GCS_SOURCE,...] [--async] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -43,24 +43,24 @@ POSITIONAL ARGUMENTS the project attribute: ◆ provide the argument repository on the command line with a fully specified name; + ◆ set the property artifacts/repository with a fully specified name; ◆ provide the argument --project on the command line; ◆ set the property core/project. - This must be specified. - - REPOSITORY + [REPOSITORY] ID of the repository or fully qualified identifier for the repository. To set the repository attribute: - ▸ provide the argument repository on the command line. - - This positional must be specified if any of the other arguments in - this group are specified. + ▸ provide the argument repository on the command line; + ▸ set the property artifacts/repository. --location=LOCATION Location of the repository. To set the location attribute: ▸ provide the argument repository on the command line with a fully specified name; - ▸ provide the argument --location on the command line. + ▸ set the property artifacts/repository with a fully specified + name; + ▸ provide the argument --location on the command line; + ▸ set the property artifacts/location. REQUIRED FLAGS --gcs-source=[GCS_SOURCE,...] diff --git a/gcloud/beta/artifacts/apt/upload b/gcloud/beta/artifacts/apt/upload index 872246b63..75ce59606 100644 --- a/gcloud/beta/artifacts/apt/upload +++ b/gcloud/beta/artifacts/apt/upload @@ -3,7 +3,7 @@ NAME repository SYNOPSIS - gcloud beta artifacts apt upload (REPOSITORY : --location=LOCATION) + gcloud beta artifacts apt upload [[REPOSITORY] --location=LOCATION] --source=SOURCE [--async] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -24,24 +24,24 @@ POSITIONAL ARGUMENTS the project attribute: ◆ provide the argument repository on the command line with a fully specified name; + ◆ set the property artifacts/repository with a fully specified name; ◆ provide the argument --project on the command line; ◆ set the property core/project. - This must be specified. - - REPOSITORY + [REPOSITORY] ID of the repository or fully qualified identifier for the repository. To set the repository attribute: - ▸ provide the argument repository on the command line. - - This positional must be specified if any of the other arguments in - this group are specified. + ▸ provide the argument repository on the command line; + ▸ set the property artifacts/repository. --location=LOCATION Location of the repository. To set the location attribute: ▸ provide the argument repository on the command line with a fully specified name; - ▸ provide the argument --location on the command line. + ▸ set the property artifacts/repository with a fully specified + name; + ▸ provide the argument --location on the command line; + ▸ set the property artifacts/location. REQUIRED FLAGS --source=SOURCE diff --git a/gcloud/beta/artifacts/files/list b/gcloud/beta/artifacts/files/list index bc4bcf159..64ddfbafa 100644 --- a/gcloud/beta/artifacts/files/list +++ b/gcloud/beta/artifacts/files/list @@ -3,7 +3,7 @@ NAME SYNOPSIS gcloud beta artifacts files list [--package=PACKAGE] [--tag=TAG] - [--version=VERSION] [--repository=REPOSITORY : --location=LOCATION] + [--version=VERSION] [--location=LOCATION --repository=REPOSITORY] [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [GCLOUD_WIDE_FLAG ...] @@ -65,22 +65,24 @@ FLAGS the project attribute: ◆ provide the argument --repository on the command line with a fully specified name; + ◆ set the property artifacts/repository with a fully specified name; ◆ provide the argument --project on the command line; ◆ set the property core/project. - --repository=REPOSITORY - ID of the repository or fully qualified identifier for the - repository. To set the repository attribute: - ▸ provide the argument --repository on the command line. - - This flag must be specified if any of the other arguments in this - group are specified. - --location=LOCATION Location of the repository. To set the location attribute: ▸ provide the argument --repository on the command line with a fully specified name; - ▸ provide the argument --location on the command line. + ▸ set the property artifacts/repository with a fully specified + name; + ▸ provide the argument --location on the command line; + ▸ set the property artifacts/location. + + --repository=REPOSITORY + ID of the repository or fully qualified identifier for the + repository. To set the repository attribute: + ▸ provide the argument --repository on the command line; + ▸ set the property artifacts/repository. LIST COMMAND FLAGS --filter=EXPRESSION diff --git a/gcloud/beta/artifacts/print-settings/apt b/gcloud/beta/artifacts/print-settings/apt index cae098b99..2cdac4483 100644 --- a/gcloud/beta/artifacts/print-settings/apt +++ b/gcloud/beta/artifacts/print-settings/apt @@ -4,7 +4,7 @@ NAME SYNOPSIS gcloud beta artifacts print-settings apt - [--repository=REPOSITORY : --location=LOCATION] [GCLOUD_WIDE_FLAG ...] + [--location=LOCATION --repository=REPOSITORY] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) Print settings to add to the sources.list.d directory for connecting @@ -29,22 +29,24 @@ FLAGS the project attribute: ◆ provide the argument --repository on the command line with a fully specified name; + ◆ set the property artifacts/repository with a fully specified name; ◆ provide the argument --project on the command line; ◆ set the property core/project. - --repository=REPOSITORY - ID of the repository or fully qualified identifier for the - repository. To set the repository attribute: - ▸ provide the argument --repository on the command line. - - This flag must be specified if any of the other arguments in this - group are specified. - --location=LOCATION Location of the repository. To set the location attribute: ▸ provide the argument --repository on the command line with a fully specified name; - ▸ provide the argument --location on the command line. + ▸ set the property artifacts/repository with a fully specified + name; + ▸ provide the argument --location on the command line; + ▸ set the property artifacts/location. + + --repository=REPOSITORY + ID of the repository or fully qualified identifier for the + repository. To set the repository attribute: + ▸ provide the argument --repository on the command line; + ▸ set the property artifacts/repository. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/beta/artifacts/print-settings/gradle b/gcloud/beta/artifacts/print-settings/gradle index f3684354b..1ca4683d0 100644 --- a/gcloud/beta/artifacts/print-settings/gradle +++ b/gcloud/beta/artifacts/print-settings/gradle @@ -4,7 +4,7 @@ NAME SYNOPSIS gcloud beta artifacts print-settings gradle [--json-key=JSON_KEY] - [--repository=REPOSITORY : --location=LOCATION] [GCLOUD_WIDE_FLAG ...] + [--location=LOCATION --repository=REPOSITORY] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) Print a snippet to add a repository to the Gradle build.gradle file. @@ -38,22 +38,24 @@ FLAGS the project attribute: ◆ provide the argument --repository on the command line with a fully specified name; + ◆ set the property artifacts/repository with a fully specified name; ◆ provide the argument --project on the command line; ◆ set the property core/project. - --repository=REPOSITORY - ID of the repository or fully qualified identifier for the - repository. To set the repository attribute: - ▸ provide the argument --repository on the command line. - - This flag must be specified if any of the other arguments in this - group are specified. - --location=LOCATION Location of the repository. To set the location attribute: ▸ provide the argument --repository on the command line with a fully specified name; - ▸ provide the argument --location on the command line. + ▸ set the property artifacts/repository with a fully specified + name; + ▸ provide the argument --location on the command line; + ▸ set the property artifacts/location. + + --repository=REPOSITORY + ID of the repository or fully qualified identifier for the + repository. To set the repository attribute: + ▸ provide the argument --repository on the command line; + ▸ set the property artifacts/repository. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/beta/artifacts/print-settings/mvn b/gcloud/beta/artifacts/print-settings/mvn index 700e9a64a..b7f238b3c 100644 --- a/gcloud/beta/artifacts/print-settings/mvn +++ b/gcloud/beta/artifacts/print-settings/mvn @@ -4,7 +4,7 @@ NAME SYNOPSIS gcloud beta artifacts print-settings mvn [--json-key=JSON_KEY] - [--repository=REPOSITORY : --location=LOCATION] [GCLOUD_WIDE_FLAG ...] + [--location=LOCATION --repository=REPOSITORY] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) Print a snippet to add a Maven repository to the pom.xml file. @@ -38,22 +38,24 @@ FLAGS the project attribute: ◆ provide the argument --repository on the command line with a fully specified name; + ◆ set the property artifacts/repository with a fully specified name; ◆ provide the argument --project on the command line; ◆ set the property core/project. - --repository=REPOSITORY - ID of the repository or fully qualified identifier for the - repository. To set the repository attribute: - ▸ provide the argument --repository on the command line. - - This flag must be specified if any of the other arguments in this - group are specified. - --location=LOCATION Location of the repository. To set the location attribute: ▸ provide the argument --repository on the command line with a fully specified name; - ▸ provide the argument --location on the command line. + ▸ set the property artifacts/repository with a fully specified + name; + ▸ provide the argument --location on the command line; + ▸ set the property artifacts/location. + + --repository=REPOSITORY + ID of the repository or fully qualified identifier for the + repository. To set the repository attribute: + ▸ provide the argument --repository on the command line; + ▸ set the property artifacts/repository. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/beta/artifacts/print-settings/npm b/gcloud/beta/artifacts/print-settings/npm index 44ebc85cc..2e59e09e7 100644 --- a/gcloud/beta/artifacts/print-settings/npm +++ b/gcloud/beta/artifacts/print-settings/npm @@ -4,7 +4,7 @@ NAME SYNOPSIS gcloud beta artifacts print-settings npm [--json-key=JSON_KEY] - [--scope=SCOPE] [--repository=REPOSITORY : --location=LOCATION] + [--scope=SCOPE] [--location=LOCATION --repository=REPOSITORY] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -49,22 +49,24 @@ FLAGS the project attribute: ◆ provide the argument --repository on the command line with a fully specified name; + ◆ set the property artifacts/repository with a fully specified name; ◆ provide the argument --project on the command line; ◆ set the property core/project. - --repository=REPOSITORY - ID of the repository or fully qualified identifier for the - repository. To set the repository attribute: - ▸ provide the argument --repository on the command line. - - This flag must be specified if any of the other arguments in this - group are specified. - --location=LOCATION Location of the repository. To set the location attribute: ▸ provide the argument --repository on the command line with a fully specified name; - ▸ provide the argument --location on the command line. + ▸ set the property artifacts/repository with a fully specified + name; + ▸ provide the argument --location on the command line; + ▸ set the property artifacts/location. + + --repository=REPOSITORY + ID of the repository or fully qualified identifier for the + repository. To set the repository attribute: + ▸ provide the argument --repository on the command line; + ▸ set the property artifacts/repository. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/beta/artifacts/print-settings/python b/gcloud/beta/artifacts/print-settings/python index dd010a877..5cbb0912e 100644 --- a/gcloud/beta/artifacts/print-settings/python +++ b/gcloud/beta/artifacts/print-settings/python @@ -4,7 +4,7 @@ NAME SYNOPSIS gcloud beta artifacts print-settings python [--json-key=JSON_KEY] - [--repository=REPOSITORY : --location=LOCATION] [GCLOUD_WIDE_FLAG ...] + [--location=LOCATION --repository=REPOSITORY] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) Print credential settings to add to the .pypirc and pip.conf files @@ -39,22 +39,24 @@ FLAGS the project attribute: ◆ provide the argument --repository on the command line with a fully specified name; + ◆ set the property artifacts/repository with a fully specified name; ◆ provide the argument --project on the command line; ◆ set the property core/project. - --repository=REPOSITORY - ID of the repository or fully qualified identifier for the - repository. To set the repository attribute: - ▸ provide the argument --repository on the command line. - - This flag must be specified if any of the other arguments in this - group are specified. - --location=LOCATION Location of the repository. To set the location attribute: ▸ provide the argument --repository on the command line with a fully specified name; - ▸ provide the argument --location on the command line. + ▸ set the property artifacts/repository with a fully specified + name; + ▸ provide the argument --location on the command line; + ▸ set the property artifacts/location. + + --repository=REPOSITORY + ID of the repository or fully qualified identifier for the + repository. To set the repository attribute: + ▸ provide the argument --repository on the command line; + ▸ set the property artifacts/repository. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/beta/artifacts/print-settings/yum b/gcloud/beta/artifacts/print-settings/yum index a362e15b5..4d9c49478 100644 --- a/gcloud/beta/artifacts/print-settings/yum +++ b/gcloud/beta/artifacts/print-settings/yum @@ -4,7 +4,7 @@ NAME SYNOPSIS gcloud beta artifacts print-settings yum - [--repository=REPOSITORY : --location=LOCATION] [GCLOUD_WIDE_FLAG ...] + [--location=LOCATION --repository=REPOSITORY] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) Print settings to add to the yum.repos.d directory for connecting to @@ -29,22 +29,24 @@ FLAGS the project attribute: ◆ provide the argument --repository on the command line with a fully specified name; + ◆ set the property artifacts/repository with a fully specified name; ◆ provide the argument --project on the command line; ◆ set the property core/project. - --repository=REPOSITORY - ID of the repository or fully qualified identifier for the - repository. To set the repository attribute: - ▸ provide the argument --repository on the command line. - - This flag must be specified if any of the other arguments in this - group are specified. - --location=LOCATION Location of the repository. To set the location attribute: ▸ provide the argument --repository on the command line with a fully specified name; - ▸ provide the argument --location on the command line. + ▸ set the property artifacts/repository with a fully specified + name; + ▸ provide the argument --location on the command line; + ▸ set the property artifacts/location. + + --repository=REPOSITORY + ID of the repository or fully qualified identifier for the + repository. To set the repository attribute: + ▸ provide the argument --repository on the command line; + ▸ set the property artifacts/repository. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/beta/artifacts/repositories/list b/gcloud/beta/artifacts/repositories/list index 2331ac877..e45b0abe2 100644 --- a/gcloud/beta/artifacts/repositories/list +++ b/gcloud/beta/artifacts/repositories/list @@ -3,7 +3,7 @@ NAME specified project SYNOPSIS - gcloud beta artifacts repositories list --location=LOCATION + gcloud beta artifacts repositories list [--location=LOCATION] [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [GCLOUD_WIDE_FLAG ...] @@ -28,13 +28,15 @@ FLAGS set in other ways. To set the project attribute: ◆ provide the argument --location on the command line with a fully specified name; + ◆ set the property artifacts/location with a fully specified name; ◆ provide the argument --project on the command line; ◆ set the property core/project. --location=LOCATION ID of the location or fully qualified identifier for the location. To set the location attribute: - ▸ provide the argument --location on the command line. + ▸ provide the argument --location on the command line; + ▸ set the property artifacts/location. LIST COMMAND FLAGS --filter=EXPRESSION diff --git a/gcloud/beta/artifacts/yum/import b/gcloud/beta/artifacts/yum/import index 695657874..90e611d96 100644 --- a/gcloud/beta/artifacts/yum/import +++ b/gcloud/beta/artifacts/yum/import @@ -3,7 +3,7 @@ NAME artifact repository SYNOPSIS - gcloud beta artifacts yum import (REPOSITORY : --location=LOCATION) + gcloud beta artifacts yum import [[REPOSITORY] --location=LOCATION] --gcs-source=[GCS_SOURCE,...] [--async] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -43,24 +43,24 @@ POSITIONAL ARGUMENTS the project attribute: ◆ provide the argument repository on the command line with a fully specified name; + ◆ set the property artifacts/repository with a fully specified name; ◆ provide the argument --project on the command line; ◆ set the property core/project. - This must be specified. - - REPOSITORY + [REPOSITORY] ID of the repository or fully qualified identifier for the repository. To set the repository attribute: - ▸ provide the argument repository on the command line. - - This positional must be specified if any of the other arguments in - this group are specified. + ▸ provide the argument repository on the command line; + ▸ set the property artifacts/repository. --location=LOCATION Location of the repository. To set the location attribute: ▸ provide the argument repository on the command line with a fully specified name; - ▸ provide the argument --location on the command line. + ▸ set the property artifacts/repository with a fully specified + name; + ▸ provide the argument --location on the command line; + ▸ set the property artifacts/location. REQUIRED FLAGS --gcs-source=[GCS_SOURCE,...] diff --git a/gcloud/beta/artifacts/yum/upload b/gcloud/beta/artifacts/yum/upload index 4e001542a..9d2b712e7 100644 --- a/gcloud/beta/artifacts/yum/upload +++ b/gcloud/beta/artifacts/yum/upload @@ -3,7 +3,7 @@ NAME repository SYNOPSIS - gcloud beta artifacts yum upload (REPOSITORY : --location=LOCATION) + gcloud beta artifacts yum upload [[REPOSITORY] --location=LOCATION] --source=SOURCE [--async] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -24,24 +24,24 @@ POSITIONAL ARGUMENTS the project attribute: ◆ provide the argument repository on the command line with a fully specified name; + ◆ set the property artifacts/repository with a fully specified name; ◆ provide the argument --project on the command line; ◆ set the property core/project. - This must be specified. - - REPOSITORY + [REPOSITORY] ID of the repository or fully qualified identifier for the repository. To set the repository attribute: - ▸ provide the argument repository on the command line. - - This positional must be specified if any of the other arguments in - this group are specified. + ▸ provide the argument repository on the command line; + ▸ set the property artifacts/repository. --location=LOCATION Location of the repository. To set the location attribute: ▸ provide the argument repository on the command line with a fully specified name; - ▸ provide the argument --location on the command line. + ▸ set the property artifacts/repository with a fully specified + name; + ▸ provide the argument --location on the command line; + ▸ set the property artifacts/location. REQUIRED FLAGS --source=SOURCE diff --git a/gcloud/beta/auth/application-default/login b/gcloud/beta/auth/application-default/login index 33c1c5bd9..a118859c4 100644 --- a/gcloud/beta/auth/application-default/login +++ b/gcloud/beta/auth/application-default/login @@ -45,21 +45,24 @@ EXAMPLES FLAGS --no-browser - Use this flag to authenticate the client libraries on a machine without - a web browser. + If you want to authorize the client libraries on a machine that doesn't + have a browser and you can install the gcloud CLI on another machine + with a browser, use the --no-browser flag. - Run gcloud auth login --no-browser and follow these steps: + 1. To initiate authorization, enter the following command: - 1. Copy the long command that begins with "gcloud auth login - --remote-bootstrap=". + gcloud auth application-default login --no-browser - 2. Paste and run this command on the command line of a different, + 2. Copy the long command that begins with gcloud auth + application-default login --remote-bootstrap=". + + 3. Paste and run this command on the command line of a different, trusted machine that has local installations of both a web browser and the gcloud CLI tool version 372.0 or later. - 3. Copy the long URL output from the machine with the web browser. + 4. Copy the long URL output from the machine with the web browser. - 4. Paste the long URL back to the first machine under the prompt, + 5. Paste the long URL back to the first machine under the prompt, "Enter the output of the above command", and press Enter to complete the authorization. @@ -94,7 +97,31 @@ FLAGS --launch-browser Launch a browser for authorization. If not enabled or if it is not possible to launch a browser, prints a URL to standard output to be - copied. Enabled by default, use --no-launch-browser to disable. + copied. + + If you want to authorize the client libraries on a machine that doesn't + have a browser and you cannot install the gcloud CLI on another machine + with a browser, use the --no-launch-browser flag. The + --no-launch-browser flag prevents the command from automatically + opening a web browser. + + 1. To initiate authorization, enter the following command: + + gcloud auth application-default login --no-launch-browser + + 2. Copy the long URL that begins with + https://accounts.google.com/o/oauth2/auth... + + 3. Paste this URL into the browser of a different, trusted machine that + has a web browser. + + 4. Copy the authorization code from the machine with the web browser. + + 5. Paste the authorization code back to the first machine at the + prompt, "Enter authorization code", and press Enter to complete the + authorization. + + Enabled by default, use --no-launch-browser to disable. --scopes=SCOPE,[SCOPE,...] The names of the scopes to authorize for. By default openid, diff --git a/gcloud/beta/auth/login b/gcloud/beta/auth/login index c282d95c4..b6eea1907 100644 --- a/gcloud/beta/auth/login +++ b/gcloud/beta/auth/login @@ -61,21 +61,24 @@ FLAGS Minimal user output. --no-browser - Use this flag to authenticate the gcloud CLI on a machine without a web - browser. + If you want to authorize the gcloud CLI on a machine that doesn't have + a browser and you can install the gcloud CLI on another machine with a + browser, use the --no-browser flag. - Run gcloud auth login --no-browser and follow these steps: + 1. To initiate authorization, enter the following command: - 1. Copy the long command that begins with "gcloud auth login + gcloud auth login --no-browser + + 2. Copy the long command that begins with gcloud auth login --remote-bootstrap=". - 2. Paste and run this command on the command line of a different, + 3. Paste and run this command on the command line of a different, trusted machine that has local installations of both a web browser and the gcloud CLI tool version 372.0 or later. - 3. Copy the long URL output from the machine with the web browser. + 4. Copy the long URL output from the machine with the web browser. - 4. Paste the long URL back to the first machine under the prompt, + 5. Paste the long URL back to the first machine under the prompt, "Enter the output of the above command", and press Enter to complete the authorization. @@ -95,7 +98,30 @@ FLAGS --launch-browser Launch a browser for authorization. If not enabled or if it is not possible to launch a browser, prints a URL to standard output to be - copied. Enabled by default, use --no-launch-browser to disable. + copied. + + If you want to authorize the gcloud CLI on a machine that doesn't have + a browser and you cannot install the gcloud CLI on another machine with + a browser, use the --no-launch-browser flag. The --no-launch-browser + flag prevents the command from automatically opening a web browser. + + 1. To initiate authorization, enter the following command: + + gcloud auth login --no-launch-browser + + 2. Copy the long URL that begins with + https://accounts.google.com/o/oauth2/auth... + + 3. Paste this URL into the browser of a different, trusted machine that + has a web browser. + + 4. Copy the authorization code from the machine with the web browser. + + 5. Paste the authorization code back to the first machine at the + prompt, "Enter authorization code", and press Enter to complete the + authorization. + + Enabled by default, use --no-launch-browser to disable. --update-adc Write the obtained credentials to the well-known location for diff --git a/gcloud/beta/compute/help b/gcloud/beta/compute/help index 16390ee89..34e25083f 100644 --- a/gcloud/beta/compute/help +++ b/gcloud/beta/compute/help @@ -93,6 +93,9 @@ GROUPS machine-types (BETA) Read Compute Engine virtual machine types. + network-edge-security-services + (BETA) Read and manipulate network edge security services. + network-endpoint-groups (BETA) Read and manipulate Compute Engine network endpoint groups. diff --git a/gcloud/beta/compute/instance-groups/managed/create b/gcloud/beta/compute/instance-groups/managed/create index b6cab3af9..e20c48dd9 100644 --- a/gcloud/beta/compute/instance-groups/managed/create +++ b/gcloud/beta/compute/instance-groups/managed/create @@ -66,28 +66,27 @@ OPTIONAL FLAGS An instance redistribution type can be specified only for a non-autoscaled regional managed instance group. By default it is set to - PROACTIVE. + proactive. - The following types are available: + TYPE must be one of: - ◆ NONE - The managed instance group does not redistribute instances - across zones. - - ◆ PROACTIVE - The managed instance group proactively redistributes - instances to meet its target distribution. - - TYPE must be one of: NONE, PROACTIVE. + none + The managed instance group does not redistribute instances across + zones. + proactive + The managed instance group proactively redistributes instances to + meet its target distribution. --list-managed-instances-results=MODE Pagination behavior for the group's listManagedInstances API method. This flag does not affect the group's gcloud or console list-instances - behavior. By default it is set to PAGELESS. MODE must be one of: + behavior. By default it is set to pageless. MODE must be one of: - PAGELESS + pageless Pagination is disabled for the group's listManagedInstances API method. maxResults and pageToken query parameters are ignored and all instances are returned in a single response. - PAGINATED + paginated Pagination is enabled for the group's listManagedInstances API method. maxResults and pageToken query parameters are respected. @@ -183,21 +182,21 @@ OPTIONAL FLAGS --target-distribution-shape=SHAPE Specifies how a regional managed instance group distributes its - instances across zones within the region. The default shape is EVEN. + instances across zones within the region. The default shape is even. SHAPE must be one of: - ANY + any The group picks zones for creating VM instances to fulfill the requested number of VMs within present resource constraints and to maximize utilization of unused zonal reservations. Recommended for batch workloads that do not require high availability. - BALANCED + balanced The group prioritizes acquisition of resources, scheduling VMs in zones where resources are available while distributing VMs as evenly as possible across selected zones to minimize the impact of zonal failure. Recommended for highly available serving or batch workloads that do not require autoscaling. - EVEN + even The group schedules VM instance creation and deletion to achieve and maintain an even number of managed instances across the selected zones. The distribution is even when the number of managed diff --git a/gcloud/beta/compute/instance-groups/managed/update b/gcloud/beta/compute/instance-groups/managed/update index 5de30b10b..3dc95cc9b 100644 --- a/gcloud/beta/compute/instance-groups/managed/update +++ b/gcloud/beta/compute/instance-groups/managed/update @@ -59,28 +59,27 @@ FLAGS An instance redistribution type can be specified only for a non-autoscaled regional managed instance group. By default it is set to - PROACTIVE. + proactive. - The following types are available: + TYPE must be one of: - ◆ NONE - The managed instance group does not redistribute instances - across zones. - - ◆ PROACTIVE - The managed instance group proactively redistributes - instances to meet its target distribution. - - TYPE must be one of: NONE, PROACTIVE. + none + The managed instance group does not redistribute instances across + zones. + proactive + The managed instance group proactively redistributes instances to + meet its target distribution. --list-managed-instances-results=MODE Pagination behavior for the group's listManagedInstances API method. This flag does not affect the group's gcloud or console list-instances - behavior. By default it is set to PAGELESS. MODE must be one of: + behavior. By default it is set to pageless. MODE must be one of: - PAGELESS + pageless Pagination is disabled for the group's listManagedInstances API method. maxResults and pageToken query parameters are ignored and all instances are returned in a single response. - PAGINATED + paginated Pagination is enabled for the group's listManagedInstances API method. maxResults and pageToken query parameters are respected. @@ -200,21 +199,21 @@ FLAGS --target-distribution-shape=SHAPE Specifies how a regional managed instance group distributes its - instances across zones within the region. The default shape is EVEN. + instances across zones within the region. The default shape is even. SHAPE must be one of: - ANY + any The group picks zones for creating VM instances to fulfill the requested number of VMs within present resource constraints and to maximize utilization of unused zonal reservations. Recommended for batch workloads that do not require high availability. - BALANCED + balanced The group prioritizes acquisition of resources, scheduling VMs in zones where resources are available while distributing VMs as evenly as possible across selected zones to minimize the impact of zonal failure. Recommended for highly available serving or batch workloads that do not require autoscaling. - EVEN + even The group schedules VM instance creation and deletion to achieve and maintain an even number of managed instances across the selected zones. The distribution is even when the number of managed diff --git a/gcloud/beta/compute/instance-templates/create b/gcloud/beta/compute/instance-templates/create index 86eded4ae..4b68fb3f1 100644 --- a/gcloud/beta/compute/instance-templates/create +++ b/gcloud/beta/compute/instance-templates/create @@ -693,9 +693,6 @@ FLAGS The name of the source instance that the instance template will be created from. - You can override machine type and labels. Values of other flags will be - ignored and values from the source instance will be used instead. - --source-instance-zone=SOURCE_INSTANCE_ZONE Zone of the instance to operate on. Overrides the default compute/zone property value for this command invocation. diff --git a/gcloud/beta/compute/network-edge-security-services/create b/gcloud/beta/compute/network-edge-security-services/create new file mode 100644 index 000000000..344c58d72 --- /dev/null +++ b/gcloud/beta/compute/network-edge-security-services/create @@ -0,0 +1,69 @@ +NAME + gcloud beta compute network-edge-security-services create - create a + Compute Engine network edge security service + +SYNOPSIS + gcloud beta compute network-edge-security-services create NAME + [--description=DESCRIPTION] [--region=REGION] + [--security-policy=SECURITY_POLICY] + [--global-security-policy + | --security-policy-region=SECURITY_POLICY_REGION] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) gcloud beta compute network-edge-security-services create is used to + create network edge security services. + +EXAMPLES + To create a network edge security service with the name 'my-service' in + region 'us-central1', run: + + $ gcloud beta compute network-edge-security-services create \ + my-service --region=us-central1 + + To create a network edge security service with the name 'my-service' with + security policy 'my-policy' attached in region 'us-central1', run: + + $ gcloud beta compute network-edge-security-services create \ + my-service --security-policy=my-policy --region=us-central1 + +POSITIONAL ARGUMENTS + NAME + Name of the network edge security service to create. + +FLAGS + --description=DESCRIPTION + An optional, textual description for the network edge security service. + + --region=REGION + Region of the network edge security service to create. Overrides the + default compute/region property value for this command invocation. + + --security-policy=SECURITY_POLICY + The security policy that will be set for this network edge security + service. To remove the policy from this network edge security service + set the policy to an empty string. + + At most one of these can be specified: + + --global-security-policy + If set, the security policy is global. + + --security-policy-region=SECURITY_POLICY_REGION + Region of the security policy to operate on. 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 beta and might change without notice. This + variant is also available: + + $ gcloud alpha compute network-edge-security-services create + diff --git a/gcloud/beta/compute/network-edge-security-services/delete b/gcloud/beta/compute/network-edge-security-services/delete new file mode 100644 index 000000000..6238ff955 --- /dev/null +++ b/gcloud/beta/compute/network-edge-security-services/delete @@ -0,0 +1,42 @@ +NAME + gcloud beta compute network-edge-security-services delete - delete network + edge security services + +SYNOPSIS + gcloud beta compute network-edge-security-services delete NAME + [--region=REGION] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) gcloud beta compute network-edge-security-services delete deletes + Compute Engine network edge security services. + +EXAMPLES + To delete a network edge security service with the name 'my-service' in + region 'us-central1', run: + + $ gcloud beta compute network-edge-security-services delete \ + my-service --region=us-central1 + +POSITIONAL ARGUMENTS + NAME + Name of the network edge security service to delete. + +FLAGS + --region=REGION + Region of the network edge security service 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 beta and might change without notice. This + variant is also available: + + $ gcloud alpha compute network-edge-security-services delete + diff --git a/gcloud/beta/compute/network-edge-security-services/describe b/gcloud/beta/compute/network-edge-security-services/describe new file mode 100644 index 000000000..7ecca788f --- /dev/null +++ b/gcloud/beta/compute/network-edge-security-services/describe @@ -0,0 +1,43 @@ +NAME + gcloud beta compute network-edge-security-services describe - describe a + Compute Engine network edge security service + +SYNOPSIS + gcloud beta compute network-edge-security-services describe NAME + [--region=REGION] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) gcloud beta compute network-edge-security-services describe displays + all data associated with a Compute Engine network edge security service in + a project. + +EXAMPLES + To describe a network edge security service with the name 'my-service' in + region 'us-central1', run: + + $ gcloud beta compute network-edge-security-services describe \ + my-service --region=us-central1 + +POSITIONAL ARGUMENTS + NAME + Name of the network edge security service to describe. + +FLAGS + --region=REGION + Region of the network edge security service 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 beta and might change without notice. This + variant is also available: + + $ gcloud alpha compute network-edge-security-services describe + diff --git a/gcloud/beta/compute/network-edge-security-services/help b/gcloud/beta/compute/network-edge-security-services/help new file mode 100644 index 000000000..92e01ed63 --- /dev/null +++ b/gcloud/beta/compute/network-edge-security-services/help @@ -0,0 +1,47 @@ +NAME + gcloud beta compute network-edge-security-services - read and manipulate + network edge security services + +SYNOPSIS + gcloud beta compute network-edge-security-services COMMAND + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Read and manipulate network edge security services. + + Network edge security services are used to protect network load balancing + resources and instances with external IPs. + + For example, to add advanced protection for a given region, create a + network edge security service in that region and attach a security policy + with ADVANCED DDoS protection enabled. + +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 Compute Engine network edge security service. + + delete + (BETA) Delete network edge security services. + + describe + (BETA) Describe a Compute Engine network edge security service. + + list + (BETA) List Google Compute Engine network edge security services. + + update + (BETA) Update a network edge security service. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha compute network-edge-security-services + diff --git a/gcloud/beta/compute/network-edge-security-services/list b/gcloud/beta/compute/network-edge-security-services/list new file mode 100644 index 000000000..75fedea61 --- /dev/null +++ b/gcloud/beta/compute/network-edge-security-services/list @@ -0,0 +1,78 @@ +NAME + gcloud beta compute network-edge-security-services list - list Google + Compute Engine network edge security services + +SYNOPSIS + gcloud beta compute network-edge-security-services list + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) gcloud beta compute network-edge-security-services list displays all + Google Compute Engine network edge security services in a project. + + By default, network edge security services from all regions are listed. The + results can be narrowed down using a filter: --filter="region:( REGION ... + )". + +EXAMPLES + To list all network edge security services in a project in table form, run: + + $ gcloud beta compute network-edge-security-services list + + To list the URIs of all network edge security services in a project, run: + + $ gcloud beta compute network-edge-security-services list --uri + + To list all network edge security services in the us-central1 and + europe-west1 regions, run: + + $ gcloud beta compute network-edge-security-services list \ + --filter="region:( us-central1 europe-west1 )" + +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 network-edge-security-services list + diff --git a/gcloud/beta/compute/network-edge-security-services/update b/gcloud/beta/compute/network-edge-security-services/update new file mode 100644 index 000000000..346fe3efa --- /dev/null +++ b/gcloud/beta/compute/network-edge-security-services/update @@ -0,0 +1,69 @@ +NAME + gcloud beta compute network-edge-security-services update - update a + network edge security service + +SYNOPSIS + gcloud beta compute network-edge-security-services update NAME + [--description=DESCRIPTION] [--region=REGION] + [--security-policy=SECURITY_POLICY] + [--global-security-policy + | --security-policy-region=SECURITY_POLICY_REGION] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) gcloud beta compute network-edge-security-services update is used to + update network edge security services. + +EXAMPLES + To attach a new security policy 'my-policy' to a network edge security + service with the name 'my-service' in region 'us-central1', run: + + $ gcloud beta compute network-edge-security-services update \ + my-service --security-policy=my-policy --region=us-central1 + + To remove the security policy attached to a network edge security service + with the name 'my-service' in region 'us-central1', run: + + $ gcloud beta compute network-edge-security-services update \ + my-service --security-policy="" --region=us-central1 + +POSITIONAL ARGUMENTS + NAME + Name of the network edge security service to update. + +FLAGS + --description=DESCRIPTION + An optional, textual description for the network edge security service. + + --region=REGION + Region of the network edge security service to update. Overrides the + default compute/region property value for this command invocation. + + --security-policy=SECURITY_POLICY + The security policy that will be set for this network edge security + service. To remove the policy from this network edge security service + set the policy to an empty string. + + At most one of these can be specified: + + --global-security-policy + If set, the security policy is global. + + --security-policy-region=SECURITY_POLICY_REGION + Region of the security policy to operate on. 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 beta and might change without notice. This + variant is also available: + + $ gcloud alpha compute network-edge-security-services update + diff --git a/gcloud/beta/compute/security-policies/create b/gcloud/beta/compute/security-policies/create index 84cf155cf..430ab19d9 100644 --- a/gcloud/beta/compute/security-policies/create +++ b/gcloud/beta/compute/security-policies/create @@ -6,7 +6,7 @@ SYNOPSIS gcloud beta compute security-policies create NAME [--description=DESCRIPTION] [--file-format=FILE_FORMAT] [--file-name=FILE_NAME | --type=SECURITY_POLICY_TYPE] - [GCLOUD_WIDE_FLAG ...] + [--global | --region=REGION] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) gcloud beta compute security-policies create is used to create @@ -37,7 +37,17 @@ FLAGS --type=SECURITY_POLICY_TYPE The type indicates the intended use of the security policy. - SECURITY_POLICY_TYPE must be one of: CLOUD_ARMOR, CLOUD_ARMOR_EDGE. + SECURITY_POLICY_TYPE must be one of: CLOUD_ARMOR, CLOUD_ARMOR_EDGE, + CLOUD_ARMOR_NETWORK. + + At most one of these can be specified: + + --global + If set, the security policy is global. + + --region=REGION + Region of the security 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, diff --git a/gcloud/beta/compute/security-policies/delete b/gcloud/beta/compute/security-policies/delete index 2bcea1a67..0c57e83a7 100644 --- a/gcloud/beta/compute/security-policies/delete +++ b/gcloud/beta/compute/security-policies/delete @@ -3,7 +3,7 @@ NAME SYNOPSIS gcloud beta compute security-policies delete NAME [NAME ...] - [GCLOUD_WIDE_FLAG ...] + [--global | --region=REGION] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) gcloud beta compute security-policies delete deletes Compute Engine @@ -14,6 +14,16 @@ POSITIONAL ARGUMENTS NAME [NAME ...] Names of the security policies to delete. +FLAGS + At most one of these can be specified: + + --global + If set, the security policies are global. + + --region=REGION + Region of the security policies 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, diff --git a/gcloud/beta/compute/security-policies/describe b/gcloud/beta/compute/security-policies/describe index 645d287a7..adf11e118 100644 --- a/gcloud/beta/compute/security-policies/describe +++ b/gcloud/beta/compute/security-policies/describe @@ -3,7 +3,8 @@ NAME security policy SYNOPSIS - gcloud beta compute security-policies describe NAME [GCLOUD_WIDE_FLAG ...] + gcloud beta compute security-policies describe NAME + [--global | --region=REGION] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) gcloud beta compute security-policies describe displays all data @@ -13,6 +14,16 @@ POSITIONAL ARGUMENTS NAME Name of the security policy to describe. +FLAGS + At most one of these can be specified: + + --global + If set, the security policy is global. + + --region=REGION + Region of the security 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, diff --git a/gcloud/beta/compute/security-policies/export b/gcloud/beta/compute/security-policies/export index a77d4958c..c341df98f 100644 --- a/gcloud/beta/compute/security-policies/export +++ b/gcloud/beta/compute/security-policies/export @@ -4,7 +4,8 @@ NAME SYNOPSIS gcloud beta compute security-policies export NAME --file-name=FILE_NAME - [--file-format=FILE_FORMAT] [GCLOUD_WIDE_FLAG ...] + [--file-format=FILE_FORMAT] [--global | --region=REGION] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) Export security policy configs into yaml files. @@ -23,6 +24,15 @@ OPTIONAL FLAGS either yaml or json. Defaults to yaml if not specified. FILE_FORMAT must be one of: json, yaml. + At most one of these can be specified: + + --global + If set, the security policy is global. + + --region=REGION + Region of the security policy to export. 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, diff --git a/gcloud/beta/compute/security-policies/help b/gcloud/beta/compute/security-policies/help index 33df4d697..d61c1991d 100644 --- a/gcloud/beta/compute/security-policies/help +++ b/gcloud/beta/compute/security-policies/help @@ -49,7 +49,7 @@ COMMANDS (BETA) Import security policy configs into your project. list - (BETA) List Google Compute Engine security policies. + (BETA) List security policies. list-preconfigured-expression-sets (BETA) List all available preconfigured expression sets. diff --git a/gcloud/beta/compute/security-policies/import b/gcloud/beta/compute/security-policies/import index 3f7ef2e78..3ba4708de 100644 --- a/gcloud/beta/compute/security-policies/import +++ b/gcloud/beta/compute/security-policies/import @@ -4,7 +4,8 @@ NAME SYNOPSIS gcloud beta compute security-policies import NAME --file-name=FILE_NAME - [--file-format=FILE_FORMAT] [GCLOUD_WIDE_FLAG ...] + [--file-format=FILE_FORMAT] [--global | --region=REGION] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) gcloud beta compute security-policies import imports a security @@ -32,6 +33,15 @@ OPTIONAL FLAGS Specify either yaml or json. Defaults to yaml if not specified. FILE_FORMAT must be one of: json, yaml. + At most one of these can be specified: + + --global + If set, the security policy is global. + + --region=REGION + Region of the security policy to import. 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, diff --git a/gcloud/beta/compute/security-policies/list b/gcloud/beta/compute/security-policies/list index 56574745b..dd81ecf15 100644 --- a/gcloud/beta/compute/security-policies/list +++ b/gcloud/beta/compute/security-policies/list @@ -1,24 +1,41 @@ NAME - gcloud beta compute security-policies list - list Google Compute Engine - security policies + gcloud beta compute security-policies list - list security policies SYNOPSIS - gcloud beta compute security-policies list [--filter=EXPRESSION] - [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] - [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (BETA) gcloud beta compute security-policies list displays all Google - Compute Engine security policies in a project. + gcloud beta compute security-policies list [NAME ...] + [--regexp=REGEXP, -r REGEXP] [--global | --regions=[REGION,...]] + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] EXAMPLES - To list all security policies in a project in table form, run: + To list security policies in all scopes run this: $ gcloud beta compute security-policies list - To list the URIs of all security policies in a project, run: +POSITIONAL ARGUMENTS + [NAME ...] + (DEPRECATED) If provided, show details for the specified names and/or + URIs of resources. - $ gcloud beta compute security-policies list --uri + 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. + + At most one of these can be specified: + + --global + If provided, only global resources are shown. + + --regions=[REGION,...] + If provided, only regional resources are shown. If arguments are + provided, only resources from the given regions are shown. LIST COMMAND FLAGS --filter=EXPRESSION diff --git a/gcloud/beta/compute/security-policies/update b/gcloud/beta/compute/security-policies/update index cbad6375f..525a79302 100644 --- a/gcloud/beta/compute/security-policies/update +++ b/gcloud/beta/compute/security-policies/update @@ -8,8 +8,9 @@ SYNOPSIS [--json-parsing=JSON_PARSING] [--layer7-ddos-defense-rule-visibility=VISIBILITY_TYPE] [--log-level=LOG_LEVEL] + [--network-ddos-protection=NETWORK_DDOS_PROTECTION] [--recaptcha-redirect-site-key=RECAPTCHA_REDIRECT_SITE_KEY] - [GCLOUD_WIDE_FLAG ...] + [--global | --region=REGION] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) gcloud beta compute security-policies update is used to update @@ -45,10 +46,24 @@ FLAGS The level of detail to display for WAF logging. LOG_LEVEL must be one of: NORMAL, VERBOSE. + --network-ddos-protection=NETWORK_DDOS_PROTECTION + The DDoS protection level for network load balancing and instances with + external IPs. NETWORK_DDOS_PROTECTION must be one of: STANDARD, + ADVANCED. + --recaptcha-redirect-site-key=RECAPTCHA_REDIRECT_SITE_KEY The reCAPTCHA site key to be used for rules using the redirect action and the google-recaptcha redirect type under the security policy. + At most one of these can be specified: + + --global + If set, the security policy is global. + + --region=REGION + Region of the security 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, diff --git a/gcloud/beta/config/list b/gcloud/beta/config/list index 2735fcb9d..a0f42a49e 100644 --- a/gcloud/beta/config/list +++ b/gcloud/beta/config/list @@ -8,10 +8,10 @@ SYNOPSIS DESCRIPTION (BETA) gcloud beta config list lists all properties of the active - configuration. These include the account used to authorize access to the - Cloud Platform, the current Cloud Platform project, and the default Compute - Engine region and zone, if set. See gcloud topic configurations for more - about configurations. + configuration. These include the account used to authorize access to Google + Cloud, the current Google Cloud project, and the default Compute Engine + region and zone, if set. See gcloud topic configurations for more about + configurations. EXAMPLES To list the project property in the core section, run: @@ -22,6 +22,10 @@ EXAMPLES $ gcloud beta config list compute/zone + To list all the properties in the compute section, run: + + $ gcloud beta config list compute/ + To list all the properties, run: $ gcloud beta config list --all diff --git a/gcloud/beta/container/backup-restore/restore-plans/create b/gcloud/beta/container/backup-restore/restore-plans/create index 0d4d78f23..67bb098d4 100644 --- a/gcloud/beta/container/backup-restore/restore-plans/create +++ b/gcloud/beta/container/backup-restore/restore-plans/create @@ -11,7 +11,8 @@ SYNOPSIS | --selected-namespaces=[SELECTED_NAMESPACES,...]) [--async] [--description=DESCRIPTION] [--labels=[KEY=VALUE,...]] [--substitution-rules-file=SUBSTITUTION_RULES_FILE] - [--volume-data-restore-policy=VOLUME_DATA_RESTORE_POLICY] + [--volume-data-restore-policy=VOLUME_DATA_RESTORE_POLICY; + default="no-volume-data-restoration"] [--cluster-resource-conflict-policy=CLUSTER_RESOURCE_CONFLICT_POLICY --cluster-resource-restore-scope=[CLUSTER_RESOURCE_RESTORE_SCOPE, ...]] [GCLOUD_WIDE_FLAG ...] @@ -83,8 +84,25 @@ REQUIRED FLAGS --namespaced-resource-restore-mode=NAMESPACED_RESOURCE_RESTORE_MODE Define how to handle restore-time conflicts for namespaced resources. - NAMESPACED_RESOURCE_RESTORE_MODE must be one of: delete-and-restore, - fail-on-conflict, namespaced-resource-restore-mode-unspecified. + NAMESPACED_RESOURCE_RESTORE_MODE must be one of: + + delete-and-restore + When conflicting top-level resources (either Namespaces or + ProtectedApplications, depending upon the scope) are encountered, + this will first trigger a delete of the conflicting resource AND + ALL OF ITS REFERENCED RESOURCES (e.g., all resources in the + Namespace or all resources referenced by the ProtectedApplication) + before restoring the resources from the Backup. This mode should + only be used when you are intending to revert some portion of a + cluster to an earlier state. + + fail-on-conflict + If conflicting top-level resources (either Namespaces or + ProtectedApplications, depending upon the scope) are encountered at + the beginning of a restore process, the Restore will fail. If a + conflict occurs during the restore process itself (e.g., because an + out of band process creates conflicting resources), a conflict will + be reported. Exactly one of these must be specified: @@ -121,17 +139,44 @@ OPTIONAL FLAGS applied to resources from the source backup before they are created in the target cluster. - --volume-data-restore-policy=VOLUME_DATA_RESTORE_POLICY - Define how data is populated for restored volumes. - VOLUME_DATA_RESTORE_POLICY must be one of: no-volume-data-restoration, - restore-volume-data-from-backup, reuse-volume-handle-from-backup, - volume-data-restore-policy-unspecified. + --volume-data-restore-policy=VOLUME_DATA_RESTORE_POLICY; default="no-volume-data-restoration" + Define how data is populated for restored volumes. If this flag is not + specified, 'no-volume-data-restoration' will be used. + VOLUME_DATA_RESTORE_POLICY must be one of: + + no-volume-data-restoration + Selecting 'no-volume-data-restoration' means PV will not be + restored. The restoration will ONLY restore selected PVCs and + expects corresponding Kubernetes controllers to either dynamically + provision blank PVs or bind them to pre-provisioned PVs created + out-of-band. + + restore-volume-data-from-backup + Selecting 'restore-volume-data-from-backup' means a new PV will be + restored using the corresponding volume backup data in the Backup. + + reuse-volume-handle-from-backup + Selecting 'reuse-volume-handle-from-backup' means a PV will be + pre-provisioned using the volume handle of the original PV in the + Backup. --cluster-resource-conflict-policy=CLUSTER_RESOURCE_CONFLICT_POLICY Define how to handle restore-time conflicts for cluster-scoped resources. CLUSTER_RESOURCE_CONFLICT_POLICY must be one of: - cluster-resource-conflict-policy-unspecified, use-backup-version, - use-existing-version. + + use-backup-version + Selecting 'use-existing-version' means deleting the existing + version of the conflicting resources before re-creating them from + the Backup. + + Note that this is a dangerous option which could cause + unintentional data loss if used inappropriately. For example, + deleting a CRD will cause Kubernetes to delete all CRs of that + type. + + use-existing-version + Selecting 'use-existing-version' means no conflicting resources + will be restored. --cluster-resource-restore-scope=[CLUSTER_RESOURCE_RESTORE_SCOPE,...] List of cluster-scoped resource types to be restored. Not specifying diff --git a/gcloud/beta/container/backup-restore/restore-plans/update b/gcloud/beta/container/backup-restore/restore-plans/update index d2d4d5e50..bc8b72232 100644 --- a/gcloud/beta/container/backup-restore/restore-plans/update +++ b/gcloud/beta/container/backup-restore/restore-plans/update @@ -9,7 +9,8 @@ SYNOPSIS [--namespaced-resource-restore-mode=NAMESPACED_RESOURCE_RESTORE_MODE] [--substitution-rules-file=SUBSTITUTION_RULES_FILE] [--update-labels=[KEY=VALUE,...]] - [--volume-data-restore-policy=VOLUME_DATA_RESTORE_POLICY] + [--volume-data-restore-policy=VOLUME_DATA_RESTORE_POLICY; + default="no-volume-data-restoration"] [--all-namespaces | --selected-applications=SELECTED_APPLICATIONS | --selected-namespaces=[SELECTED_NAMESPACES,...]] [--clear-labels | --remove-labels=[KEY,...]] @@ -74,8 +75,25 @@ FLAGS --namespaced-resource-restore-mode=NAMESPACED_RESOURCE_RESTORE_MODE Define how to handle restore-time conflicts for namespaced resources. - NAMESPACED_RESOURCE_RESTORE_MODE must be one of: delete-and-restore, - fail-on-conflict, namespaced-resource-restore-mode-unspecified. + NAMESPACED_RESOURCE_RESTORE_MODE must be one of: + + delete-and-restore + When conflicting top-level resources (either Namespaces or + ProtectedApplications, depending upon the scope) are encountered, + this will first trigger a delete of the conflicting resource AND + ALL OF ITS REFERENCED RESOURCES (e.g., all resources in the + Namespace or all resources referenced by the ProtectedApplication) + before restoring the resources from the Backup. This mode should + only be used when you are intending to revert some portion of a + cluster to an earlier state. + + fail-on-conflict + If conflicting top-level resources (either Namespaces or + ProtectedApplications, depending upon the scope) are encountered at + the beginning of a restore process, the Restore will fail. If a + conflict occurs during the restore process itself (e.g., because an + out of band process creates conflicting resources), a conflict will + be reported. --substitution-rules-file=SUBSTITUTION_RULES_FILE If provided, defines a set of resource transformations that will be @@ -91,11 +109,26 @@ FLAGS contain only hyphens (-), underscores (_), lowercase characters, and numbers. - --volume-data-restore-policy=VOLUME_DATA_RESTORE_POLICY - Define how data is populated for restored volumes. - VOLUME_DATA_RESTORE_POLICY must be one of: no-volume-data-restoration, - restore-volume-data-from-backup, reuse-volume-handle-from-backup, - volume-data-restore-policy-unspecified. + --volume-data-restore-policy=VOLUME_DATA_RESTORE_POLICY; default="no-volume-data-restoration" + Define how data is populated for restored volumes. If this flag is not + specified, 'no-volume-data-restoration' will be used. + VOLUME_DATA_RESTORE_POLICY must be one of: + + no-volume-data-restoration + Selecting 'no-volume-data-restoration' means PV will not be + restored. The restoration will ONLY restore selected PVCs and + expects corresponding Kubernetes controllers to either dynamically + provision blank PVs or bind them to pre-provisioned PVs created + out-of-band. + + restore-volume-data-from-backup + Selecting 'restore-volume-data-from-backup' means a new PV will be + restored using the corresponding volume backup data in the Backup. + + reuse-volume-handle-from-backup + Selecting 'reuse-volume-handle-from-backup' means a PV will be + pre-provisioned using the volume handle of the original PV in the + Backup. At most one of these can be specified: @@ -135,8 +168,20 @@ FLAGS --cluster-resource-conflict-policy=CLUSTER_RESOURCE_CONFLICT_POLICY Define how to handle restore-time conflicts for cluster-scoped resources. CLUSTER_RESOURCE_CONFLICT_POLICY must be one of: - cluster-resource-conflict-policy-unspecified, use-backup-version, - use-existing-version. + + use-backup-version + Selecting 'use-existing-version' means deleting the existing + version of the conflicting resources before re-creating them from + the Backup. + + Note that this is a dangerous option which could cause + unintentional data loss if used inappropriately. For example, + deleting a CRD will cause Kubernetes to delete all CRs of that + type. + + use-existing-version + Selecting 'use-existing-version' means no conflicting resources + will be restored. --cluster-resource-restore-scope=[CLUSTER_RESOURCE_RESTORE_SCOPE,...] List of cluster-scoped resource types to be restored. Not specifying diff --git a/gcloud/beta/container/clusters/create b/gcloud/beta/container/clusters/create index 89623a3ca..7ee3caa68 100644 --- a/gcloud/beta/container/clusters/create +++ b/gcloud/beta/container/clusters/create @@ -18,7 +18,7 @@ SYNOPSIS [--default-max-pods-per-node=DEFAULT_MAX_PODS_PER_NODE] [--disable-default-snat] [--disable-pod-cidr-overprovision] [--disk-size=DISK_SIZE] [--disk-type=DISK_TYPE] [--enable-autorepair] - [--no-enable-autoupgrade] [--enable-binauthz] [--enable-cloud-logging] + [--no-enable-autoupgrade] [--enable-cloud-logging] [--enable-cloud-monitoring] [--enable-cloud-run-alpha] [--enable-confidential-nodes] [--enable-cost-allocation] [--enable-dataplane-v2] [--enable-gke-oidc] [--enable-gvnic] @@ -57,6 +57,8 @@ SYNOPSIS [--tags=TAG,[TAG,...]] [--threads-per-core=THREADS_PER_CORE] [--workload-metadata=WORKLOAD_METADATA] [--workload-pool=WORKLOAD_POOL] [--additional-zones=ZONE,[ZONE,...] | --node-locations=ZONE,[ZONE,...]] + [--binauthz-evaluation-mode=BINAUTHZ_EVALUATION_MODE + | --enable-binauthz] [--cluster-dns=CLUSTER_DNS --cluster-dns-domain=CLUSTER_DNS_DOMAIN --cluster-dns-scope=CLUSTER_DNS_SCOPE] [[--enable-autoprovisioning @@ -77,7 +79,9 @@ SYNOPSIS --enable-autoprovisioning-autoupgrade [--max-accelerator=[type=TYPE,count=COUNT,...] : --min-accelerator=[type=TYPE,count=COUNT,...]]]]] - [--enable-autoscaling --max-nodes=MAX_NODES --min-nodes=MIN_NODES] + [--enable-autoscaling --location-policy=LOCATION_POLICY + --max-nodes=MAX_NODES --min-nodes=MIN_NODES + --total-max-nodes=TOTAL_MAX_NODES --total-min-nodes=TOTAL_MIN_NODES] [--enable-master-authorized-networks --master-authorized-networks=NETWORK,[NETWORK,...]] [--enable-network-egress-metering @@ -343,9 +347,6 @@ FLAGS Enabled by default, use --no-enable-autoupgrade to disable. - --enable-binauthz - Enable Binary Authorization for this cluster. - --enable-cloud-logging (DEPRECATED) Automatically send logs from the cluster to the Google Cloud Logging API. @@ -699,14 +700,16 @@ FLAGS --monitoring=[COMPONENT,...] Set the components that have monitoring enabled. Valid component values - are: SYSTEM, WORKLOAD (Deprecated), NONE + are: SYSTEM, WORKLOAD (Deprecated), NONE,API_SERVER, + CONTROLLER_MANAGER, SCHEDULER For more information, look at https://cloud.google.com/stackdriver/docs/solutions/gke/installing#available-metrics Examples: - $ gcloud beta container clusters create --monitoring=SYSTEM + $ gcloud beta container clusters create \ + --monitoring=SYSTEM,API_SERVER $ gcloud beta container clusters create --monitoring=NONE --network=NETWORK @@ -1071,6 +1074,21 @@ FLAGS --zone us-central1-a \ --node-locations us-central1-a,us-central1-b + Flags for Binary Authorization: + + At most one of these can be specified: + + --binauthz-evaluation-mode=BINAUTHZ_EVALUATION_MODE + Enable Binary Authorization for this cluster. + BINAUTHZ_EVALUATION_MODE must be one of: DISABLED, + PROJECT_SINGLETON_POLICY_ENFORCE. + + --enable-binauthz + (DEPRECATED) Enable Binary Authorization for this cluster. + + The --enable-binauthz flag is deprecated. Please use + --binauthz-evaluation-mode instead. + ClusterDNS --cluster-dns=CLUSTER_DNS @@ -1341,6 +1359,17 @@ FLAGS Enables autoscaling in the node pool specified by --node-pool or the default node pool if --node-pool is not provided. + --location-policy=LOCATION_POLICY + Location policy specifies the algorithm used when scaling-up the node + pool. + + ▸ BALANCED - Is a best effort policy that aims to balance the sizes + of available zones. + ▸ ANY - Instructs the cluster autoscaler to prioritize utilization + of unused reservations, and reduces preemption risk for Spot VMs. + + LOCATION_POLICY must be one of: BALANCED, ANY. + --max-nodes=MAX_NODES Maximum number of nodes per zone in the node pool. @@ -1355,6 +1384,20 @@ FLAGS --node-pool (or default node pool if unspecified) can scale. Ignored unless --enable-autoscaling is also specified. + --total-max-nodes=TOTAL_MAX_NODES + Maximum number of all nodes in the node pool. + + Maximum number of all nodes to which the node pool specified by + --node-pool (or default node pool if unspecified) can scale. Ignored + unless --enable-autoscaling is also specified. + + --total-min-nodes=TOTAL_MIN_NODES + Minimum number of all nodes in the node pool. + + Minimum number of all nodes to which the node pool specified by + --node-pool (or default node pool if unspecified) can scale. Ignored + unless --enable-autoscaling is also specified. + Master Authorized Networks --enable-master-authorized-networks diff --git a/gcloud/beta/container/clusters/create-auto b/gcloud/beta/container/clusters/create-auto index 242cdc53f..48a3d7473 100644 --- a/gcloud/beta/container/clusters/create-auto +++ b/gcloud/beta/container/clusters/create-auto @@ -5,6 +5,7 @@ NAME SYNOPSIS gcloud beta container clusters create-auto NAME [--async] [--autoprovisioning-network-tags=TAGS,[TAGS,...]] + [--binauthz-evaluation-mode=BINAUTHZ_EVALUATION_MODE] [--boot-disk-kms-key=BOOT_DISK_KMS_KEY] [--cluster-ipv4-cidr=CLUSTER_IPV4_CIDR] [--cluster-secondary-range-name=NAME] @@ -60,6 +61,13 @@ FLAGS https://cloud.google.com/sdk/gcloud/reference/compute/firewall-rules/create for examples. + Flags for Binary Authorization: + + --binauthz-evaluation-mode=BINAUTHZ_EVALUATION_MODE + Enable Binary Authorization for this cluster. + BINAUTHZ_EVALUATION_MODE must be one of: DISABLED, + PROJECT_SINGLETON_POLICY_ENFORCE. + --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/clusters/update b/gcloud/beta/container/clusters/update index 3a14dd650..dad8c3109 100644 --- a/gcloud/beta/container/clusters/update +++ b/gcloud/beta/container/clusters/update @@ -10,7 +10,7 @@ SYNOPSIS | --database-encryption-key=DATABASE_ENCRYPTION_KEY | --disable-database-encryption | --disable-default-snat | --disable-workload-identity | --enable-autoscaling - | --enable-binauthz | --enable-cost-allocation | --enable-gke-oidc + | --enable-cost-allocation | --enable-gke-oidc | --enable-identity-service | --enable-image-streaming | --enable-intra-node-visibility | --enable-l4-ilb-subsetting | --enable-legacy-authorization @@ -30,7 +30,9 @@ SYNOPSIS | --update-addons=[ADDON=ENABLED|DISABLED,...] | --update-labels=[KEY=VALUE,...] | --workload-pool=WORKLOAD_POOL | --additional-zones=[ZONE,...] | --node-locations=ZONE,[ZONE,...] - | --clear-maintenance-window | --remove-maintenance-exclusion=NAME + | --binauthz-evaluation-mode=BINAUTHZ_EVALUATION_MODE + | --enable-binauthz | --clear-maintenance-window + | --remove-maintenance-exclusion=NAME | [--add-maintenance-exclusion-end=TIME_STAMP : --add-maintenance-exclusion-name=NAME --add-maintenance-exclusion-scope=SCOPE @@ -70,7 +72,10 @@ SYNOPSIS [--cloud-run-config=[load-balancer-type=EXTERNAL,...]] [--istio-config=[auth=MTLS_PERMISSIVE,...]] [--master-authorized-networks=NETWORK,[NETWORK,...]] - [--node-pool=NODE_POOL] [--max-nodes=MAX_NODES --min-nodes=MIN_NODES] + [--node-pool=NODE_POOL] + [--location-policy=LOCATION_POLICY --max-nodes=MAX_NODES + --min-nodes=MIN_NODES + --total-max-nodes=TOTAL_MAX_NODES --total-min-nodes=TOTAL_MIN_NODES] [--region=REGION | --zone=ZONE, -z ZONE] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -181,9 +186,6 @@ REQUIRED FLAGS Enables autoscaling in the node pool specified by --node-pool or the default node pool if --node-pool is not provided. - --enable-binauthz - Enable Binary Authorization for this cluster. - --enable-cost-allocation Enable the cost management feature. @@ -540,6 +542,21 @@ REQUIRED FLAGS --zone us-central1-a \ --node-locations us-central1-a,us-central1-b + Flags for Binary Authorization: + + At most one of these can be specified: + + --binauthz-evaluation-mode=BINAUTHZ_EVALUATION_MODE + Enable Binary Authorization for this cluster. + BINAUTHZ_EVALUATION_MODE must be one of: DISABLED, + PROJECT_SINGLETON_POLICY_ENFORCE. + + --enable-binauthz + (DEPRECATED) Enable Binary Authorization for this cluster. + + The --enable-binauthz flag is deprecated. Please use + --binauthz-evaluation-mode instead. + At most one of these can be specified: --clear-maintenance-window @@ -987,14 +1004,16 @@ REQUIRED FLAGS --monitoring=[COMPONENT,...] Set the components that have monitoring enabled. Valid component - values are: SYSTEM, WORKLOAD (Deprecated), NONE + values are: SYSTEM, WORKLOAD (Deprecated), NONE,API_SERVER, + CONTROLLER_MANAGER, SCHEDULER For more information, look at https://cloud.google.com/stackdriver/docs/solutions/gke/installing#available-metrics Examples: - $ gcloud beta container clusters update --monitoring=SYSTEM + $ gcloud beta container clusters update \ + --monitoring=SYSTEM,API_SERVER $ gcloud beta container clusters update --monitoring=NONE --logging-service=LOGGING_SERVICE @@ -1090,6 +1109,17 @@ OPTIONAL FLAGS Cluster autoscaling + --location-policy=LOCATION_POLICY + Location policy specifies the algorithm used when scaling-up the node + pool. + + ▸ BALANCED - Is a best effort policy that aims to balance the sizes + of available zones. + ▸ ANY - Instructs the cluster autoscaler to prioritize utilization + of unused reservations, and reduces preemption risk for Spot VMs. + + LOCATION_POLICY must be one of: BALANCED, ANY. + --max-nodes=MAX_NODES Maximum number of nodes per zone in the node pool. @@ -1104,6 +1134,20 @@ OPTIONAL FLAGS --node-pool (or default node pool if unspecified) can scale. Ignored unless --enable-autoscaling is also specified. + --total-max-nodes=TOTAL_MAX_NODES + Maximum number of all nodes in the node pool. + + Maximum number of all nodes to which the node pool specified by + --node-pool (or default node pool if unspecified) can scale. Ignored + unless --enable-autoscaling is also specified. + + --total-min-nodes=TOTAL_MIN_NODES + Minimum number of all nodes in the node pool. + + Minimum number of all nodes to which the node pool specified by + --node-pool (or default node pool if unspecified) can scale. Ignored + unless --enable-autoscaling is also specified. + At most one of these can be specified: --region=REGION diff --git a/gcloud/beta/container/fleet/memberships/register b/gcloud/beta/container/fleet/memberships/register index ed47d425c..f6c54f345 100644 --- a/gcloud/beta/container/fleet/memberships/register +++ b/gcloud/beta/container/fleet/memberships/register @@ -37,11 +37,11 @@ DESCRIPTION corresponds to a service account that has been granted gkehub.connect permissions. - If the cluster is already registered to another Fleet, the registration is + If the cluster is already registered to another fleet, the registration is not successful. Rerunning this command against the same cluster with the same - MEMBERSHIP_NAME and target GKEFleet is successful and upgrades the Connect + MEMBERSHIP_NAME and target fleet is successful and upgrades the Connect Agent if a new agent is available. EXAMPLES diff --git a/gcloud/beta/container/fleet/memberships/unregister b/gcloud/beta/container/fleet/memberships/unregister index 50d966394..85518e139 100644 --- a/gcloud/beta/container/fleet/memberships/unregister +++ b/gcloud/beta/container/fleet/memberships/unregister @@ -29,7 +29,7 @@ DESCRIPTION To register a GKE cluster use --gke-cluster or --gke-uri flag (no --kubeconfig flag is required). - To only delete the Fleet membership resource, consider using the command: + To only delete the Fleet Membership resource, consider using the command: gcloud beta container fleet memberships delete. This command is intended to delete stale Fleet Membership resources as doing so on a fully registered cluster will skip some of the steps above and orphan in-cluster resources @@ -59,9 +59,8 @@ EXAMPLES POSITIONAL ARGUMENTS MEMBERSHIP_NAME - The membership name that corresponds to the cluster being unregistered. - To get list of all the memberships on the Fleet, consider using the - command: gcloud beta container fleet memberships list. + The membership name that you choose to uniquely represents the cluster + being registered on the fleet. REQUIRED FLAGS Cluster identifier. diff --git a/gcloud/beta/container/hub/memberships/register b/gcloud/beta/container/hub/memberships/register index 8d1aab8c4..6c9d347a9 100644 --- a/gcloud/beta/container/hub/memberships/register +++ b/gcloud/beta/container/hub/memberships/register @@ -37,11 +37,11 @@ DESCRIPTION corresponds to a service account that has been granted gkehub.connect permissions. - If the cluster is already registered to another Fleet, the registration is + If the cluster is already registered to another fleet, the registration is not successful. Rerunning this command against the same cluster with the same - MEMBERSHIP_NAME and target GKEFleet is successful and upgrades the Connect + MEMBERSHIP_NAME and target fleet is successful and upgrades the Connect Agent if a new agent is available. EXAMPLES diff --git a/gcloud/beta/container/hub/memberships/unregister b/gcloud/beta/container/hub/memberships/unregister index 77a2aa7c8..847c11e4b 100644 --- a/gcloud/beta/container/hub/memberships/unregister +++ b/gcloud/beta/container/hub/memberships/unregister @@ -29,7 +29,7 @@ DESCRIPTION To register a GKE cluster use --gke-cluster or --gke-uri flag (no --kubeconfig flag is required). - To only delete the Fleet membership resource, consider using the command: + To only delete the Fleet Membership resource, consider using the command: gcloud beta container hub memberships delete. This command is intended to delete stale Fleet Membership resources as doing so on a fully registered cluster will skip some of the steps above and orphan in-cluster resources @@ -59,9 +59,8 @@ EXAMPLES POSITIONAL ARGUMENTS MEMBERSHIP_NAME - The membership name that corresponds to the cluster being unregistered. - To get list of all the memberships on the Fleet, consider using the - command: gcloud beta container hub memberships list. + The membership name that you choose to uniquely represents the cluster + being registered on the fleet. REQUIRED FLAGS Cluster identifier. diff --git a/gcloud/beta/container/node-pools/create b/gcloud/beta/container/node-pools/create index ed9a3db27..60b0fe84c 100644 --- a/gcloud/beta/container/node-pools/create +++ b/gcloud/beta/container/node-pools/create @@ -34,7 +34,9 @@ SYNOPSIS [--tags=TAG,[TAG,...]] [--threads-per-core=THREADS_PER_CORE] [--workload-metadata=WORKLOAD_METADATA] [--create-pod-ipv4-range=[KEY=VALUE,...] | --pod-ipv4-range=NAME] - [--enable-autoscaling --max-nodes=MAX_NODES --min-nodes=MIN_NODES] + [--enable-autoscaling --location-policy=LOCATION_POLICY + --max-nodes=MAX_NODES --min-nodes=MIN_NODES + --total-max-nodes=TOTAL_MAX_NODES --total-min-nodes=TOTAL_MIN_NODES] [--ephemeral-storage=[local-ssd-count=LOCAL-SSD-COUNT] | --local-ssd-count=LOCAL_SSD_COUNT] [--region=REGION | --zone=ZONE, -z ZONE] @@ -592,6 +594,17 @@ FLAGS Enables autoscaling in the node pool specified by --node-pool or the default node pool if --node-pool is not provided. + --location-policy=LOCATION_POLICY + Location policy specifies the algorithm used when scaling-up the node + pool. + + ▸ BALANCED - Is a best effort policy that aims to balance the sizes + of available zones. + ▸ ANY - Instructs the cluster autoscaler to prioritize utilization + of unused reservations, and reduces preemption risk for Spot VMs. + + LOCATION_POLICY must be one of: BALANCED, ANY. + --max-nodes=MAX_NODES Maximum number of nodes per zone in the node pool. @@ -606,6 +619,20 @@ FLAGS --node-pool (or default node pool if unspecified) can scale. Ignored unless --enable-autoscaling is also specified. + --total-max-nodes=TOTAL_MAX_NODES + Maximum number of all nodes in the node pool. + + Maximum number of all nodes to which the node pool specified by + --node-pool (or default node pool if unspecified) can scale. Ignored + unless --enable-autoscaling is also specified. + + --total-min-nodes=TOTAL_MIN_NODES + Minimum number of all nodes in the node pool. + + Minimum number of all nodes to which the node pool specified by + --node-pool (or default node pool if unspecified) can scale. Ignored + unless --enable-autoscaling is also specified. + At most one of these can be specified: --ephemeral-storage=[local-ssd-count=LOCAL-SSD-COUNT] diff --git a/gcloud/beta/container/node-pools/update b/gcloud/beta/container/node-pools/update index 7a626a604..53c2c3b4c 100644 --- a/gcloud/beta/container/node-pools/update +++ b/gcloud/beta/container/node-pools/update @@ -11,8 +11,10 @@ SYNOPSIS | --node-taints=[NODE_TAINT,...] | --system-config-from-file=SYSTEM_CONFIG_FROM_FILE | --tags=[TAG,...] | --workload-metadata=WORKLOAD_METADATA - | --enable-autoprovisioning - --enable-autoscaling --max-nodes=MAX_NODES --min-nodes=MIN_NODES + | --enable-autoprovisioning --enable-autoscaling + --location-policy=LOCATION_POLICY --max-nodes=MAX_NODES + --min-nodes=MIN_NODES + --total-max-nodes=TOTAL_MAX_NODES --total-min-nodes=TOTAL_MIN_NODES | --enable-autorepair --enable-autoupgrade | --enable-blue-green-upgrade --enable-surge-upgrade --max-surge-upgrade=MAX_SURGE_UPGRADE @@ -220,6 +222,18 @@ REQUIRED FLAGS Enables autoscaling in the node pool specified by --node-pool or the default node pool if --node-pool is not provided. + --location-policy=LOCATION_POLICY + Location policy specifies the algorithm used when scaling-up the + node pool. + + ▫ BALANCED - Is a best effort policy that aims to balance the + sizes of available zones. + ▫ ANY - Instructs the cluster autoscaler to prioritize + utilization of unused reservations, and reduces preemption risk + for Spot VMs. + + LOCATION_POLICY must be one of: BALANCED, ANY. + --max-nodes=MAX_NODES Maximum number of nodes per zone in the node pool. @@ -234,6 +248,20 @@ REQUIRED FLAGS by --node-pool (or default node pool if unspecified) can scale. Ignored unless --enable-autoscaling is also specified. + --total-max-nodes=TOTAL_MAX_NODES + Maximum number of all nodes in the node pool. + + Maximum number of all nodes to which the node pool specified by + --node-pool (or default node pool if unspecified) can scale. + Ignored unless --enable-autoscaling is also specified. + + --total-min-nodes=TOTAL_MIN_NODES + Minimum number of all nodes in the node pool. + + Minimum number of all nodes to which the node pool specified by + --node-pool (or default node pool if unspecified) can scale. + Ignored unless --enable-autoscaling is also specified. + Node management --enable-autorepair diff --git a/gcloud/beta/dataproc/clusters/gke/create b/gcloud/beta/dataproc/clusters/gke/create index 7d0425e32..4643a5169 100644 --- a/gcloud/beta/dataproc/clusters/gke/create +++ b/gcloud/beta/dataproc/clusters/gke/create @@ -135,82 +135,42 @@ OPTIONAL FLAGS The following KEYs must be specified: - KEY Type Example Description - name string `my-node-pool` Name of the node pool. - roles repeated string `default;spark-driver` Roles that this node - pool should perform. - Valid values are - `default`, - `controller`, - `spark-driver`, - `spark-executor`. + ----------------------------------------------------------------------------------------------------------- + KEY Type Example Description + ------ ---------------- ------------------------ ---------------------------------------------------------- + name string `my-node-pool` Name of the node pool. - The following KEYs may be specified. + roles repeated string `default;spark-driver` Roles that this node pool should perform. Valid values are + `default`, `controller`, `spark-driver`, `spark-executor`. + ----------------------------------------------------------------------------------------------------------- - KEY Type Example Description - machineType string `n1-standard-8` Compute - Engine - machine type - to use. - preemptible boolean `false` If true, - then this - node pool - uses - preemptible - VMs. This - cannot be - true on the - node pool - with the - `controllers - ` role (or - `default` - role if - `controllers - ` role is - not - specified). - localSsdCount int `2` The number - of local - SSDs to - attach to - each node. - accelerator repeated string `nvidia-tesla-a100=1` Accelerators - to attach to - each node. - In the - format - NAME=COUNT. - minCpuPlatform string `Intel Skylake` Minimum CPU - platform for - each node. - locations repeated string `us-west1-a;us-west1-c` Zones within - the location - of the GKE - cluster. All - `--pools` - flags for a - single - Dataproc - cluster must - have - identical - locations. - min int `0` Minimum - number of - nodes per - zone that - this node - pool can - scale down - to. - max int `10` Maximum - number of - nodes per - zone that - this node - pool can - scale up to. + The following KEYs may be specified: + + ---------------------------------------------------------------------------------------------------------------------------------------------------------------- + KEY Type Example Description + --------------- ---------------- --------------------------------------------- --------------------------------------------------------------------------------- + machineType string `n1-standard-8` Compute Engine machine type to use. + + preemptible boolean `false` If true, then this node pool uses preemptible VMs. + This cannot be true on the node pool with the `controllers` role + (or `default` role if `controllers` role is not specified). + + localSsdCount int `2` The number of local SSDs to attach to each node. + + accelerator repeated string `nvidia-tesla-a100=1` Accelerators to attach to each node. In the format NAME=COUNT. + + minCpuPlatform string `Intel Skylake` Minimum CPU platform for each node. + + bootDiskKmsKey string `projects/project-id/locations/us-central1 The Customer Managed Encryption Key (CMEK) used to encrypt + /keyRings/keyRing-name/cryptoKeys/key-name` the boot disk attached to each node in the node pool. + + locations repeated string `us-west1-a;us-west1-c` Zones within the location of the GKE cluster. + All `--pools` flags for a single Dataproc cluster must have identical locations. + + min int `0` Minimum number of nodes per zone that this node pool can scale down to. + + max int `10` Maximum number of nodes per zone that this node pool can scale up to. + ---------------------------------------------------------------------------------------------------------------------------------------------------------------- --properties=[PREFIX:PROPERTY=VALUE,...] Specifies configuration properties for installed packages, such as diff --git a/gcloud/beta/datastream/connection-profiles/create b/gcloud/beta/datastream/connection-profiles/create index 1a3eeab8f..ca0d67077 100644 --- a/gcloud/beta/datastream/connection-profiles/create +++ b/gcloud/beta/datastream/connection-profiles/create @@ -5,8 +5,8 @@ NAME SYNOPSIS gcloud beta datastream connection-profiles create (CONNECTION_PROFILE : --location=LOCATION) --display-name=DISPLAY_NAME - --type=TYPE - ([--bucket-name=BUCKET_NAME : --root-path=ROOT_PATH] + --type=TYPE [--labels=[KEY=VALUE,...]] + [[--bucket-name=BUCKET_NAME : --root-path=ROOT_PATH] | --database-service=DATABASE_SERVICE --oracle-hostname=ORACLE_HOSTNAME --oracle-port=ORACLE_PORT --oracle-username=ORACLE_USERNAME (--oracle-password=ORACLE_PASSWORD @@ -14,8 +14,7 @@ SYNOPSIS --mysql-port=MYSQL_PORT --mysql-username=MYSQL_USERNAME (--mysql-password=MYSQL_PASSWORD | --mysql-prompt-for-password) : --ca-certificate=CA_CERTIFICATE - --client-certificate=CLIENT_CERTIFICATE --client-key=CLIENT_KEY]) - [--labels=[KEY=VALUE,...]] + --client-certificate=CLIENT_CERTIFICATE --client-key=CLIENT_KEY]] [--private-connection-name=PRIVATE_CONNECTION_NAME : --no-connectivity | --static-ip-connectivity | [--forward-ssh-hostname=FORWARD_SSH_HOSTNAME @@ -89,9 +88,18 @@ REQUIRED FLAGS Friendly name for the connection profile. --type=TYPE - Type can be MYSQL, ORACLE or GOOGLE-CLOUD-STORAGE + Type can be MYSQL, ORACLE, GOOGLE-CLOUD-STORAGE or BIGQUERY - Exactly one of these must be specified: +OPTIONAL FLAGS + --labels=[KEY=VALUE,...] + List of label KEY=VALUE pairs to add. + + Keys must start with a lowercase character and contain only hyphens + (-), underscores (_), lowercase characters, and numbers. Values must + contain only hyphens (-), underscores (_), lowercase characters, and + numbers. + + At most one of these can be specified: --bucket-name=BUCKET_NAME The full project and resource path for Cloud Storage bucket including @@ -187,15 +195,6 @@ REQUIRED FLAGS This flag must be specified if any of the other arguments in this group are specified. -OPTIONAL FLAGS - --labels=[KEY=VALUE,...] - List of label KEY=VALUE pairs to add. - - Keys must start with a lowercase character and contain only hyphens - (-), underscores (_), lowercase characters, and numbers. Values must - contain only hyphens (-), underscores (_), lowercase characters, and - numbers. - At most one of these can be specified: Private connection resource - Resource ID of the private connection. diff --git a/gcloud/beta/datastream/connection-profiles/update b/gcloud/beta/datastream/connection-profiles/update index 03b81405e..ba6d96dd7 100644 --- a/gcloud/beta/datastream/connection-profiles/update +++ b/gcloud/beta/datastream/connection-profiles/update @@ -87,7 +87,7 @@ POSITIONAL ARGUMENTS REQUIRED FLAGS --type=TYPE - Type can be MYSQL, ORACLE or GOOGLE-CLOUD-STORAGE + Type can be MYSQL, ORACLE, GOOGLE-CLOUD-STORAGE or BIGQUERY OPTIONAL FLAGS --display-name=DISPLAY_NAME diff --git a/gcloud/beta/datastream/streams/create b/gcloud/beta/datastream/streams/create index cc4d77c6f..c46ec3dec 100644 --- a/gcloud/beta/datastream/streams/create +++ b/gcloud/beta/datastream/streams/create @@ -8,7 +8,8 @@ SYNOPSIS | --backfill-all --mysql-excluded-objects=MYSQL_EXCLUDED_OBJECTS | --oracle-excluded-objects=ORACLE_EXCLUDED_OBJECTS) (--destination-name=DESTINATION_NAME - --gcs-destination-config=GCS_DESTINATION_CONFIG) + (--bigquery-destination-config=BIGQUERY_DESTINATION_CONFIG + | --gcs-destination-config=GCS_DESTINATION_CONFIG)) (--source-name=SOURCE_NAME (--mysql-source-config=MYSQL_SOURCE_CONFIG | --oracle-source-config=ORACLE_SOURCE_CONFIG)) [--labels=[KEY=VALUE,...]] [--force | --validate-only] @@ -108,21 +109,37 @@ REQUIRED FLAGS connection_profile. To set the connection_profile attribute: ▫ provide the argument --destination-name on the command line. - --gcs-destination-config=GCS_DESTINATION_CONFIG - Path to a YAML (or JSON) file containing the configuration for Google - Cloud Storage Destination Config. + Exactly one of these must be specified: - The JSON file is formatted as follows: + --bigquery-destination-config=BIGQUERY_DESTINATION_CONFIG + Path to a YAML (or JSON) file containing the configuration for + Google BigQuery Destination Config. - { - "path": "some/path", - "file_rotation_mb":5, - "file_rotation_interval":"15s", - "avro_file_format": {} - } + The JSON file is formatted as follows: - This flag must be specified if any of the other arguments in this - group are specified. + { + "source_hierarchy_datasets": { + "dataset_template": { + "location": "us-central1", + "dataset_id_prefix": "my_prefix", + "kms_key_name": "projects/{project}/locations/{location}/keyRings/{key_ring}/cryptoKeys/{cryptoKey}" + } + }, + "data_freshness": 3600 + } + + --gcs-destination-config=GCS_DESTINATION_CONFIG + Path to a YAML (or JSON) file containing the configuration for + Google Cloud Storage Destination Config. + + The JSON file is formatted as follows: + + { + "path": "some/path", + "file_rotation_mb":5, + "file_rotation_interval":"15s", + "avro_file_format": {} + } This must be specified. diff --git a/gcloud/beta/datastream/streams/update b/gcloud/beta/datastream/streams/update index c1a6368ef..a9dcb8b41 100644 --- a/gcloud/beta/datastream/streams/update +++ b/gcloud/beta/datastream/streams/update @@ -10,7 +10,8 @@ SYNOPSIS | --oracle-excluded-objects=ORACLE_EXCLUDED_OBJECTS] [--clear-labels | --remove-labels=[KEY,...]] [--destination-name=DESTINATION_NAME - : --gcs-destination-config=GCS_DESTINATION_CONFIG] + : --bigquery-destination-config=BIGQUERY_DESTINATION_CONFIG + | --gcs-destination-config=GCS_DESTINATION_CONFIG] [--force | --validate-only] [--source-name=SOURCE_NAME : --mysql-source-config=MYSQL_SOURCE_CONFIG | --oracle-source-config=ORACLE_SOURCE_CONFIG] [GCLOUD_WIDE_FLAG ...] @@ -144,18 +145,37 @@ FLAGS connection_profile. To set the connection_profile attribute: ▸ provide the argument --destination-name on the command line. - --gcs-destination-config=GCS_DESTINATION_CONFIG - Path to a YAML (or JSON) file containing the configuration for Google - Cloud Storage Destination Config. + At most one of these can be specified: - The JSON file is formatted as follows: + --bigquery-destination-config=BIGQUERY_DESTINATION_CONFIG + Path to a YAML (or JSON) file containing the configuration for Google + BigQuery Destination Config. - { - "path": "some/path", - "file_rotation_mb":5, - "file_rotation_interval":"15s", - "avro_file_format": {} - } + The JSON file is formatted as follows: + + { + "source_hierarchy_datasets": { + "dataset_template": { + "location": "us-central1", + "dataset_id_prefix": "my_prefix", + "kms_key_name": "projects/{project}/locations/{location}/keyRings/{key_ring}/cryptoKeys/{cryptoKey}" + } + }, + "data_freshness": 3600 + } + + --gcs-destination-config=GCS_DESTINATION_CONFIG + Path to a YAML (or JSON) file containing the configuration for Google + Cloud Storage Destination Config. + + The JSON file is formatted as follows: + + { + "path": "some/path", + "file_rotation_mb":5, + "file_rotation_interval":"15s", + "avro_file_format": {} + } At most one of these can be specified: diff --git a/gcloud/beta/deploy/targets/rollback b/gcloud/beta/deploy/targets/rollback index 19e5c6ddc..8c7e4b64f 100644 --- a/gcloud/beta/deploy/targets/rollback +++ b/gcloud/beta/deploy/targets/rollback @@ -3,7 +3,8 @@ NAME SYNOPSIS gcloud beta deploy targets rollback (TARGET : --region=REGION) - --delivery-pipeline=DELIVERY_PIPELINE [--description=DESCRIPTION] + --delivery-pipeline=DELIVERY_PIPELINE [--annotations=[KEY=VALUE,...]] + [--description=DESCRIPTION] [--labels=[KEY=VALUE,...]] [--release=RELEASE] [--rollout-id=ROLLOUT_ID] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -51,9 +52,31 @@ REQUIRED FLAGS The name of the Cloud Deploy delivery pipeline OPTIONAL FLAGS + --annotations=[KEY=VALUE,...] + Annotations to apply to the rollback. Annotations take the form of + key/value string pairs. + + Examples: + + Add annotations: + + $ gcloud beta deploy targets rollback \ + --annotations="from_target=test,status=stable" + --description=DESCRIPTION Description of rollout created during a rollback. + --labels=[KEY=VALUE,...] + Labels to apply to the rollback. Labels take the form of key/value + string pairs. + + Examples: + + Add labels: + + $ gcloud beta deploy targets rollback \ + --labels="commit=abc123,author=foo" + --release=RELEASE Name of the release to rollback to. diff --git a/gcloud/beta/functions/deploy b/gcloud/beta/functions/deploy index b97365c93..d05f4f040 100644 --- a/gcloud/beta/functions/deploy +++ b/gcloud/beta/functions/deploy @@ -175,7 +175,7 @@ FLAGS ◆ nodejs14: Node.js 14 ◆ nodejs16: Node.js 16 ◆ php74: PHP 7.4 - ◆ php81: PHP 8.1 (preview) + ◆ php81: PHP 8.1 ◆ python37: Python 3.7 ◆ python38: Python 3.8 ◆ python39: Python 3.9 diff --git a/gcloud/beta/functions/help b/gcloud/beta/functions/help index 8472fe345..fbfd3552a 100644 --- a/gcloud/beta/functions/help +++ b/gcloud/beta/functions/help @@ -25,6 +25,9 @@ GROUPS regions (BETA) List regions available to Google Cloud Functions. + runtimes + (BETA) List runtimes available to Google Cloud Functions. + COMMANDS COMMAND is one of the following: diff --git a/gcloud/beta/functions/runtimes/help b/gcloud/beta/functions/runtimes/help new file mode 100644 index 000000000..a7e49585c --- /dev/null +++ b/gcloud/beta/functions/runtimes/help @@ -0,0 +1,29 @@ +NAME + gcloud beta functions runtimes - list runtimes available to Google Cloud + Functions + +SYNOPSIS + gcloud beta functions runtimes COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) List runtimes available to Google Cloud Functions. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + list + (BETA) List runtimes available to Google Cloud Functions. + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud functions runtimes + + $ gcloud alpha functions runtimes + diff --git a/gcloud/beta/functions/runtimes/list b/gcloud/beta/functions/runtimes/list new file mode 100644 index 000000000..6457fb52a --- /dev/null +++ b/gcloud/beta/functions/runtimes/list @@ -0,0 +1,70 @@ +NAME + gcloud beta functions runtimes list - list runtimes available to Google + Cloud Functions + +SYNOPSIS + gcloud beta functions runtimes list [--region=REGION] [--filter=EXPRESSION] + [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) List runtimes available to Google Cloud Functions. + +EXAMPLES + To list the available runtimes, run: + + $ gcloud beta functions runtimes list + +FLAGS + --region=REGION + Only show runtimes within the region. Overrides the default + functions/region property value for this command invocation. + +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. These + variants are also available: + + $ gcloud functions runtimes list + + $ gcloud alpha functions runtimes list + diff --git a/gcloud/beta/kms/keys/versions/import b/gcloud/beta/kms/keys/versions/import index ab0e00cce..f0762d652 100644 --- a/gcloud/beta/kms/keys/versions/import +++ b/gcloud/beta/kms/keys/versions/import @@ -6,9 +6,8 @@ SYNOPSIS gcloud beta kms keys versions import --algorithm=ALGORITHM --import-job=IMPORT_JOB [--key=KEY] [--keyring=KEYRING] [--location=LOCATION] [--public-key-file=PUBLIC_KEY_FILE] - [--rsa-aes-wrapped-key-file=RSA_AES_WRAPPED_KEY_FILE] [--target-key-file=TARGET_KEY_FILE] [--version=VERSION] - [GCLOUD_WIDE_FLAG ...] + [--wrapped-key-file=WRAPPED_KEY_FILE] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) Imports wrapped key material into a new version within an existing @@ -24,7 +23,7 @@ EXAMPLES $ gcloud beta kms keys versions import --location=global \ --keyring=fellowship --key=frodo --import-job=strider \ - --rsa-aes-wrapped-key-file=path/to/target/key \ + --wrapped-key-file=path/to/target/key \ --algorithm=google-symmetric-encryption REQUIRED FLAGS @@ -58,20 +57,20 @@ OPTIONAL FLAGS Location of the keyring. --public-key-file=PUBLIC_KEY_FILE - Optional path to the public key of the ImportJob, used to wrap the key - for import. If missing, the public key will be fetched on your behalf. - - --rsa-aes-wrapped-key-file=RSA_AES_WRAPPED_KEY_FILE - Path to the wrapped RSA AES key file to import. + Path to the public key of the ImportJob, used to wrap the key for + import. If missing, the public key will be fetched on your behalf. --target-key-file=TARGET_KEY_FILE - Optional path to the unwrapped target key to import into a Cloud KMS - key version. If specified, the key will be securely wrapped before + Path to the unwrapped target key to import into a Cloud KMS key + version. If specified, the key will be securely wrapped before transmission to Google. --version=VERSION Version to re-import into. Omit this field for first-time import. + --wrapped-key-file=WRAPPED_KEY_FILE + Path to the RSA/RSA+AES wrapped key file to import. + 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/ml/speech/recognize b/gcloud/beta/ml/speech/recognize index fb473c62a..e080d312f 100644 --- a/gcloud/beta/ml/speech/recognize +++ b/gcloud/beta/ml/speech/recognize @@ -111,6 +111,17 @@ OPTIONAL FLAGS audio that is not one of the specific audio models. For example, long-form audio. Ideally the audio is high-fidelity, recorded at a 16khz or greater sampling rate. + latest_long + Use this model for any kind of long form content such as media or + spontaneous speech and conversations. Consider using this model in + place of the video model, especially if the video model is not + available in your target language. You can also use this in place + of the default model. + latest_short + Use this model for short utterances that are a few seconds in + length. It is useful for trying to capture commands or other single + shot directed speech use cases. Consider using this model instead + of the command and search model. medical_conversation Best for audio that originated from a conversation between a medical provider and patient. diff --git a/gcloud/beta/ml/speech/recognize-long-running b/gcloud/beta/ml/speech/recognize-long-running index 34d4c4127..a3b68d024 100644 --- a/gcloud/beta/ml/speech/recognize-long-running +++ b/gcloud/beta/ml/speech/recognize-long-running @@ -120,6 +120,17 @@ OPTIONAL FLAGS audio that is not one of the specific audio models. For example, long-form audio. Ideally the audio is high-fidelity, recorded at a 16khz or greater sampling rate. + latest_long + Use this model for any kind of long form content such as media or + spontaneous speech and conversations. Consider using this model in + place of the video model, especially if the video model is not + available in your target language. You can also use this in place + of the default model. + latest_short + Use this model for short utterances that are a few seconds in + length. It is useful for trying to capture commands or other single + shot directed speech use cases. Consider using this model instead + of the command and search model. medical_conversation Best for audio that originated from a conversation between a medical provider and patient. diff --git a/gcloud/beta/recommender/insights/list b/gcloud/beta/recommender/insights/list index a577ef604..48b668e84 100644 --- a/gcloud/beta/recommender/insights/list +++ b/gcloud/beta/recommender/insights/list @@ -10,7 +10,7 @@ SYNOPSIS [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) This command will list all insights for a give cloud entity, + (BETA) This command will list all insights for a given cloud entity, location and insight type. Supported insight-types can be found here: https://cloud.google.com/recommender/docs/insights/insight-types. Currently the following cloud_entity_types are supported: project, billing_account, diff --git a/gcloud/beta/run/jobs/create b/gcloud/beta/run/jobs/create index 60d47ebd7..2d63e0069 100644 --- a/gcloud/beta/run/jobs/create +++ b/gcloud/beta/run/jobs/create @@ -49,7 +49,7 @@ POSITIONAL ARGUMENTS REQUIRED FLAGS --image=IMAGE Name of the container image to deploy (e.g. - gcr.io/cloudrun/hello:latest). + us-docker.pkg.dev/cloudrun/container/job:latest). OPTIONAL FLAGS --args=[ARG,...] diff --git a/gcloud/beta/run/jobs/update b/gcloud/beta/run/jobs/update index d5eb92ae0..ac916e5fe 100644 --- a/gcloud/beta/run/jobs/update +++ b/gcloud/beta/run/jobs/update @@ -84,7 +84,7 @@ FLAGS --image=IMAGE Name of the container image to deploy (e.g. - gcr.io/cloudrun/hello:latest). + us-docker.pkg.dev/cloudrun/container/job:latest). --key=KEY CMEK key reference to encrypt the container with. diff --git a/gcloud/beta/sql/instances/create b/gcloud/beta/sql/instances/create index a1f021bd8..bde2453d9 100644 --- a/gcloud/beta/sql/instances/create +++ b/gcloud/beta/sql/instances/create @@ -299,14 +299,12 @@ FLAGS implies that complexity check is not enabled. --[no-]password-policy-disallow-username-substring - Disallow username as a part of the password. This flag is available - only for PostgreSQL. Use --password-policy-disallow-username-substring - to enable and --no-password-policy-disallow-username-substring to - disable. + Disallow username as a part of the password. Use + --password-policy-disallow-username-substring to enable and + --no-password-policy-disallow-username-substring to disable. --password-policy-min-length=PASSWORD_POLICY_MIN_LENGTH - Minimum number of characters allowed in the password. This flag is - available only for PostgreSQL. + Minimum number of characters allowed in the password. --password-policy-password-change-interval=PASSWORD_POLICY_PASSWORD_CHANGE_INTERVAL Minimum interval after which the password can be changed, for example, @@ -316,7 +314,7 @@ FLAGS --password-policy-reuse-interval=PASSWORD_POLICY_REUSE_INTERVAL Number of previous passwords that cannot be reused. The valid range is - 0 to 100. This flag is available only for PostgreSQL. + 0 to 100. --replica-type=REPLICA_TYPE The type of replica to create. REPLICA_TYPE must be one of: READ, diff --git a/gcloud/beta/sql/instances/patch b/gcloud/beta/sql/instances/patch index 33d635228..01c3ef5e0 100644 --- a/gcloud/beta/sql/instances/patch +++ b/gcloud/beta/sql/instances/patch @@ -246,14 +246,12 @@ FLAGS implies that complexity check is not enabled. --[no-]password-policy-disallow-username-substring - Disallow username as a part of the password. This flag is available - only for PostgreSQL. Use --password-policy-disallow-username-substring - to enable and --no-password-policy-disallow-username-substring to - disable. + Disallow username as a part of the password. Use + --password-policy-disallow-username-substring to enable and + --no-password-policy-disallow-username-substring to disable. --password-policy-min-length=PASSWORD_POLICY_MIN_LENGTH - Minimum number of characters allowed in the password. This flag is - available only for PostgreSQL. + Minimum number of characters allowed in the password. --password-policy-password-change-interval=PASSWORD_POLICY_PASSWORD_CHANGE_INTERVAL Minimum interval after which the password can be changed, for example, @@ -263,7 +261,7 @@ FLAGS --password-policy-reuse-interval=PASSWORD_POLICY_REUSE_INTERVAL Number of previous passwords that cannot be reused. The valid range is - 0 to 100. This flag is available only for PostgreSQL. + 0 to 100. --pricing-plan=PRICING_PLAN, -p PRICING_PLAN First Generation instances only. The pricing plan for this instance. diff --git a/gcloud/beta/sql/users/create b/gcloud/beta/sql/users/create index d0cd72efe..fcfe0e463 100644 --- a/gcloud/beta/sql/users/create +++ b/gcloud/beta/sql/users/create @@ -6,6 +6,7 @@ SYNOPSIS [--async] [--host=HOST] [--password=PASSWORD] [--password-policy-allowed-failed-attempts=PASSWORD_POLICY_ALLOWED_FAILED_ATTEMPTS] [--[no-]password-policy-enable-failed-attempts-check] + [--[no-]password-policy-enable-password-verification] [--password-policy-password-expiration-duration=PASSWORD_POLICY_PASSWORD_EXPIRATION_DURATION] [--type=TYPE] [GCLOUD_WIDE_FLAG ...] @@ -40,18 +41,24 @@ OPTIONAL FLAGS --password-policy-allowed-failed-attempts=PASSWORD_POLICY_ALLOWED_FAILED_ATTEMPTS Number of failed login attempts allowed before a user is locked out. - This flag is currently not available. + This flag is available only for MySQL. --[no-]password-policy-enable-failed-attempts-check Enables the failed login attempts check if set to true. This flag is - currently not available. Use + available only for MySQL. Use --password-policy-enable-failed-attempts-check to enable and --no-password-policy-enable-failed-attempts-check to disable. + --[no-]password-policy-enable-password-verification + The current password must be specified when altering the password. This + flag is available only for MySQL. Use + --password-policy-enable-password-verification to enable and + --no-password-policy-enable-password-verification to disable. + --password-policy-password-expiration-duration=PASSWORD_POLICY_PASSWORD_EXPIRATION_DURATION - Expiration duration after a password is updated, for example, 2m for 2 - minutes. See gcloud topic datetimes for information on duration - formats. This flag is currently not available. + Expiration duration after a password is updated, for example, 2d for 2 + days. See gcloud topic datetimes for information on duration formats. + This flag is available only for MySQL. --type=TYPE Cloud SQL user's type. It determines the method to authenticate the diff --git a/gcloud/beta/sql/users/set-password b/gcloud/beta/sql/users/set-password index 039c0a421..4dd800d4a 100644 --- a/gcloud/beta/sql/users/set-password +++ b/gcloud/beta/sql/users/set-password @@ -5,6 +5,7 @@ NAME SYNOPSIS gcloud beta sql users set-password USERNAME --instance=INSTANCE, -i INSTANCE [--async] [--host=HOST] + [--discard-dual-password | --retain-password] [--password=PASSWORD | --prompt-for-password] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -33,6 +34,16 @@ OPTIONAL FLAGS help on how to do so, read: https://cloud.google.com/sql/docs/mysql/configure-ip + At most one of these can be specified: + + --discard-dual-password + Discard the user's secondary password. Cannot set password and set + this flag. This flag is only available for MySQL 8.0. + + --retain-password + Retain the old password when changing to the new password. Must set + password with this flag. This flag is only available for MySQL 8.0. + At most one of these can be specified: --password=PASSWORD diff --git a/gcloud/beta/sql/users/set-password-policy b/gcloud/beta/sql/users/set-password-policy index ff2e438f9..749f42b96 100644 --- a/gcloud/beta/sql/users/set-password-policy +++ b/gcloud/beta/sql/users/set-password-policy @@ -7,6 +7,7 @@ SYNOPSIS INSTANCE [--async] [--clear-password-policy] [--host=HOST] [--password-policy-allowed-failed-attempts=PASSWORD_POLICY_ALLOWED_FAILED_ATTEMPTS] [--[no-]password-policy-enable-failed-attempts-check] + [--[no-]password-policy-enable-password-verification] [--password-policy-password-expiration-duration=PASSWORD_POLICY_PASSWORD_EXPIRATION_DURATION] [GCLOUD_WIDE_FLAG ...] @@ -56,18 +57,24 @@ OPTIONAL FLAGS --password-policy-allowed-failed-attempts=PASSWORD_POLICY_ALLOWED_FAILED_ATTEMPTS Number of failed login attempts allowed before a user is locked out. - This flag is currently not available. + This flag is available only for MySQL. --[no-]password-policy-enable-failed-attempts-check Enables the failed login attempts check if set to true. This flag is - currently not available. Use + available only for MySQL. Use --password-policy-enable-failed-attempts-check to enable and --no-password-policy-enable-failed-attempts-check to disable. + --[no-]password-policy-enable-password-verification + The current password must be specified when altering the password. This + flag is available only for MySQL. Use + --password-policy-enable-password-verification to enable and + --no-password-policy-enable-password-verification to disable. + --password-policy-password-expiration-duration=PASSWORD_POLICY_PASSWORD_EXPIRATION_DURATION - Expiration duration after a password is updated, for example, 2m for 2 - minutes. See gcloud topic datetimes for information on duration - formats. This flag is currently not available. + Expiration duration after a password is updated, for example, 2d for 2 + days. See gcloud topic datetimes for information on duration formats. + This flag is available only for MySQL. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/compute/instance-groups/managed/create b/gcloud/compute/instance-groups/managed/create index ddfc728ea..f460b6be4 100644 --- a/gcloud/compute/instance-groups/managed/create +++ b/gcloud/compute/instance-groups/managed/create @@ -61,17 +61,16 @@ OPTIONAL FLAGS An instance redistribution type can be specified only for a non-autoscaled regional managed instance group. By default it is set to - PROACTIVE. + proactive. - The following types are available: + TYPE must be one of: - ◆ NONE - The managed instance group does not redistribute instances - across zones. - - ◆ PROACTIVE - The managed instance group proactively redistributes - instances to meet its target distribution. - - TYPE must be one of: NONE, PROACTIVE. + none + The managed instance group does not redistribute instances across + zones. + proactive + The managed instance group proactively redistributes instances to + meet its target distribution. --stateful-disk=[auto-delete=AUTO-DELETE],[device-name=DEVICE-NAME] Disks considered stateful by the instance group. Managed instance @@ -95,21 +94,21 @@ OPTIONAL FLAGS --target-distribution-shape=SHAPE Specifies how a regional managed instance group distributes its - instances across zones within the region. The default shape is EVEN. + instances across zones within the region. The default shape is even. SHAPE must be one of: - ANY + any The group picks zones for creating VM instances to fulfill the requested number of VMs within present resource constraints and to maximize utilization of unused zonal reservations. Recommended for batch workloads that do not require high availability. - BALANCED + balanced The group prioritizes acquisition of resources, scheduling VMs in zones where resources are available while distributing VMs as evenly as possible across selected zones to minimize the impact of zonal failure. Recommended for highly available serving or batch workloads that do not require autoscaling. - EVEN + even The group schedules VM instance creation and deletion to achieve and maintain an even number of managed instances across the selected zones. The distribution is even when the number of managed diff --git a/gcloud/compute/instance-groups/managed/update b/gcloud/compute/instance-groups/managed/update index a1e2d1c6d..41e3e1205 100644 --- a/gcloud/compute/instance-groups/managed/update +++ b/gcloud/compute/instance-groups/managed/update @@ -52,17 +52,16 @@ FLAGS An instance redistribution type can be specified only for a non-autoscaled regional managed instance group. By default it is set to - PROACTIVE. + proactive. - The following types are available: + TYPE must be one of: - ◆ NONE - The managed instance group does not redistribute instances - across zones. - - ◆ PROACTIVE - The managed instance group proactively redistributes - instances to meet its target distribution. - - TYPE must be one of: NONE, PROACTIVE. + none + The managed instance group does not redistribute instances across + zones. + proactive + The managed instance group proactively redistributes instances to + meet its target distribution. --remove-stateful-disks=DEVICE_NAME,[DEVICE_NAME,...] Remove stateful configuration for the specified disks. @@ -94,21 +93,21 @@ FLAGS --target-distribution-shape=SHAPE Specifies how a regional managed instance group distributes its - instances across zones within the region. The default shape is EVEN. + instances across zones within the region. The default shape is even. SHAPE must be one of: - ANY + any The group picks zones for creating VM instances to fulfill the requested number of VMs within present resource constraints and to maximize utilization of unused zonal reservations. Recommended for batch workloads that do not require high availability. - BALANCED + balanced The group prioritizes acquisition of resources, scheduling VMs in zones where resources are available while distributing VMs as evenly as possible across selected zones to minimize the impact of zonal failure. Recommended for highly available serving or batch workloads that do not require autoscaling. - EVEN + even The group schedules VM instance creation and deletion to achieve and maintain an even number of managed instances across the selected zones. The distribution is even when the number of managed diff --git a/gcloud/compute/instance-templates/create b/gcloud/compute/instance-templates/create index aa5d81f1f..1e69dd240 100644 --- a/gcloud/compute/instance-templates/create +++ b/gcloud/compute/instance-templates/create @@ -15,7 +15,8 @@ SYNOPSIS [boot=BOOT],[device-name=DEVICE-NAME],[mode=MODE],[name=NAME]] [--[no-]enable-nested-virtualization] [--[no-]enable-uefi-networking] [--instance-termination-action=INSTANCE_TERMINATION_ACTION] - [--ipv6-network-tier=IPV6_NETWORK_TIER] [--labels=[KEY=VALUE,...]] + [--ipv6-network-tier=IPV6_NETWORK_TIER] + [--key-revocation-action-type=POLICY] [--labels=[KEY=VALUE,...]] [--local-ssd=[device-name=DEVICE-NAME],[interface=INTERFACE]] [--machine-type=MACHINE_TYPE] [--maintenance-policy=MAINTENANCE_POLICY] [--metadata=KEY=VALUE,[KEY=VALUE,...]] @@ -350,6 +351,16 @@ FLAGS PREMIUM High quality, Google-grade network tier. + --key-revocation-action-type=POLICY + Specifies the behavior of the instance when the KMS key of one of its + attached disks is revoked. The default is none. POLICY must be one of: + + none + No operation is performed. + stop + The instance is stopped when the KMS key of one of its attached + disks is revoked. + --labels=[KEY=VALUE,...] List of label KEY=VALUE pairs to add. @@ -636,9 +647,6 @@ FLAGS The name of the source instance that the instance template will be created from. - You can override machine type and labels. Values of other flags will be - ignored and values from the source instance will be used instead. - --source-instance-zone=SOURCE_INSTANCE_ZONE Zone of the instance to operate on. Overrides the default compute/zone property value for this command invocation. diff --git a/gcloud/compute/instances/bulk/create b/gcloud/compute/instances/bulk/create index 7cd11748c..0cf7ef8c2 100644 --- a/gcloud/compute/instances/bulk/create +++ b/gcloud/compute/instances/bulk/create @@ -35,6 +35,7 @@ SYNOPSIS [--shielded-integrity-monitoring] [--shielded-secure-boot] [--shielded-vtpm] [--source-instance-template=SOURCE_INSTANCE_TEMPLATE] [--subnet=SUBNET] [--tags=TAG,[TAG,...]] + [--target-distribution-shape=SHAPE] [--threads-per-core=THREADS_PER_CORE] [--boot-disk-kms-key=BOOT_DISK_KMS_KEY : --boot-disk-kms-keyring=BOOT_DISK_KMS_KEYRING @@ -639,6 +640,25 @@ OPTIONAL FLAGS $ gcloud compute instances list --filter='tags:tag1' + --target-distribution-shape=SHAPE + Specifies whether and how to distribute VMs across multiple zones in a + region or to enforce placement of VMs in a single zone. The default + shape is ANY_SINGLE_ZONE. SHAPE must be one of: + + ANY + Allows creating VMs in multiple zones if one zone cannot + accommodate all the requested VMs. The resulting distribution + shapes can vary. + ANY_SINGLE_ZONE + Enforces VM placement in one allowed zone. Use this to avoid + cross-zone network egress or to reduce network latency. This is the + default value. + BALANCED + Allows distribution of VMs in zones where resources are available + while distributing VMs as evenly as possible across selected zones + to minimize the impact of zonal failures. Recommended for highly + available serving or batch workloads. + --threads-per-core=THREADS_PER_CORE The number of visible threads per physical core. To disable simultaneous multithreading (SMT) set this to 1. Valid values are: 1 or diff --git a/gcloud/compute/instances/create b/gcloud/compute/instances/create index 4e51102f3..ec913824d 100644 --- a/gcloud/compute/instances/create +++ b/gcloud/compute/instances/create @@ -19,7 +19,7 @@ SYNOPSIS [--instance-termination-action=INSTANCE_TERMINATION_ACTION] [--ipv6-network-tier=IPV6_NETWORK_TIER] [--ipv6-public-ptr-domain=IPV6_PUBLIC_PTR_DOMAIN] - [--labels=[KEY=VALUE,...]] + [--key-revocation-action-type=POLICY] [--labels=[KEY=VALUE,...]] [--local-ssd=[device-name=DEVICE-NAME],[interface=INTERFACE]] [--machine-type=MACHINE_TYPE] [--maintenance-policy=MAINTENANCE_POLICY] [--metadata=KEY=VALUE,[KEY=VALUE,...]] @@ -415,6 +415,16 @@ FLAGS PTR record will be used. This option can only be specified for the default network interface, nic0. + --key-revocation-action-type=POLICY + Specifies the behavior of the instance when the KMS key of one of its + attached disks is revoked. The default is none. POLICY must be one of: + + none + No operation is performed. + stop + The instance is stopped when the KMS key of one of its attached + disks is revoked. + --labels=[KEY=VALUE,...] List of label KEY=VALUE pairs to add. diff --git a/gcloud/config/list b/gcloud/config/list index 1c27da145..0d7e8bd21 100644 --- a/gcloud/config/list +++ b/gcloud/config/list @@ -8,10 +8,9 @@ SYNOPSIS DESCRIPTION gcloud config list lists all properties of the active configuration. These - include the account used to authorize access to the Cloud Platform, the - current Cloud Platform project, and the default Compute Engine region and - zone, if set. See gcloud topic configurations for more about - configurations. + include the account used to authorize access to Google Cloud, the current + Google Cloud project, and the default Compute Engine region and zone, if + set. See gcloud topic configurations for more about configurations. EXAMPLES To list the project property in the core section, run: @@ -22,6 +21,10 @@ EXAMPLES $ gcloud config list compute/zone + To list all the properties in the compute section, run: + + $ gcloud config list compute/ + To list all the properties, run: $ gcloud config list --all diff --git a/gcloud/container/clusters/create b/gcloud/container/clusters/create index 893bd577a..16f9d8227 100644 --- a/gcloud/container/clusters/create +++ b/gcloud/container/clusters/create @@ -17,18 +17,18 @@ SYNOPSIS [--default-max-pods-per-node=DEFAULT_MAX_PODS_PER_NODE] [--disable-default-snat] [--disk-size=DISK_SIZE] [--disk-type=DISK_TYPE] [--enable-autorepair] [--no-enable-autoupgrade] - [--enable-binauthz] [--enable-cloud-logging] - [--enable-cloud-monitoring] [--enable-cloud-run-alpha] - [--enable-confidential-nodes] [--enable-dataplane-v2] [--enable-gvnic] - [--enable-identity-service] [--enable-image-streaming] - [--enable-intra-node-visibility] [--enable-ip-alias] - [--enable-kubernetes-alpha] [--enable-l4-ilb-subsetting] - [--enable-legacy-authorization] [--enable-master-global-access] - [--enable-network-policy] [--enable-service-externalips] - [--enable-shielded-nodes] [--enable-stackdriver-kubernetes] - [--enable-vertical-pod-autoscaling] [--image-type=IMAGE_TYPE] - [--issue-client-certificate] [--labels=[KEY=VALUE,...]] - [--local-ssd-count=LOCAL_SSD_COUNT] [--logging=[COMPONENT,...]] + [--enable-cloud-logging] [--enable-cloud-monitoring] + [--enable-cloud-run-alpha] [--enable-confidential-nodes] + [--enable-dataplane-v2] [--enable-gvnic] [--enable-identity-service] + [--enable-image-streaming] [--enable-intra-node-visibility] + [--enable-ip-alias] [--enable-kubernetes-alpha] + [--enable-l4-ilb-subsetting] [--enable-legacy-authorization] + [--enable-master-global-access] [--enable-network-policy] + [--enable-service-externalips] [--enable-shielded-nodes] + [--enable-stackdriver-kubernetes] [--enable-vertical-pod-autoscaling] + [--image-type=IMAGE_TYPE] [--issue-client-certificate] + [--labels=[KEY=VALUE,...]] [--local-ssd-count=LOCAL_SSD_COUNT] + [--logging=[COMPONENT,...]] [--machine-type=MACHINE_TYPE, -m MACHINE_TYPE] [--max-nodes-per-pool=MAX_NODES_PER_POOL] [--max-pods-per-node=MAX_PODS_PER_NODE] @@ -51,6 +51,8 @@ SYNOPSIS [--system-config-from-file=SYSTEM_CONFIG_FROM_FILE] [--tags=TAG,[TAG,...]] [--threads-per-core=THREADS_PER_CORE] [--workload-metadata=WORKLOAD_METADATA] [--workload-pool=WORKLOAD_POOL] + [--binauthz-evaluation-mode=BINAUTHZ_EVALUATION_MODE + | --enable-binauthz] [--cluster-dns=CLUSTER_DNS --cluster-dns-domain=CLUSTER_DNS_DOMAIN --cluster-dns-scope=CLUSTER_DNS_SCOPE] [[--enable-autoprovisioning @@ -71,7 +73,9 @@ SYNOPSIS --enable-autoprovisioning-autoupgrade [--max-accelerator=[type=TYPE,count=COUNT,...] : --min-accelerator=[type=TYPE,count=COUNT,...]]]]] - [--enable-autoscaling --max-nodes=MAX_NODES --min-nodes=MIN_NODES] + [--enable-autoscaling --location-policy=LOCATION_POLICY + --max-nodes=MAX_NODES --min-nodes=MIN_NODES + --total-max-nodes=TOTAL_MAX_NODES --total-min-nodes=TOTAL_MIN_NODES] [--enable-master-authorized-networks --master-authorized-networks=NETWORK,[NETWORK,...]] [--enable-network-egress-metering @@ -336,9 +340,6 @@ FLAGS Enabled by default, use --no-enable-autoupgrade to disable. - --enable-binauthz - Enable Binary Authorization for this cluster. - --enable-cloud-logging (DEPRECATED) Automatically send logs from the cluster to the Google Cloud Logging API. @@ -636,14 +637,15 @@ FLAGS --monitoring=[COMPONENT,...] Set the components that have monitoring enabled. Valid component values - are: SYSTEM, WORKLOAD (Deprecated), NONE + are: SYSTEM, WORKLOAD (Deprecated), NONE,API_SERVER, + CONTROLLER_MANAGER, SCHEDULER For more information, look at https://cloud.google.com/stackdriver/docs/solutions/gke/installing#available-metrics Examples: - $ gcloud container clusters create --monitoring=SYSTEM + $ gcloud container clusters create --monitoring=SYSTEM,API_SERVER $ gcloud container clusters create --monitoring=NONE --network=NETWORK @@ -946,6 +948,21 @@ FLAGS https://cloud.google.com/kubernetes-engine/docs/how-to/workload-identity + Flags for Binary Authorization: + + At most one of these can be specified: + + --binauthz-evaluation-mode=BINAUTHZ_EVALUATION_MODE + Enable Binary Authorization for this cluster. + BINAUTHZ_EVALUATION_MODE must be one of: DISABLED, + PROJECT_SINGLETON_POLICY_ENFORCE. + + --enable-binauthz + (DEPRECATED) Enable Binary Authorization for this cluster. + + The --enable-binauthz flag is deprecated. Please use + --binauthz-evaluation-mode instead. + ClusterDNS --cluster-dns=CLUSTER_DNS @@ -1216,6 +1233,17 @@ FLAGS Enables autoscaling in the node pool specified by --node-pool or the default node pool if --node-pool is not provided. + --location-policy=LOCATION_POLICY + Location policy specifies the algorithm used when scaling-up the node + pool. + + ▸ BALANCED - Is a best effort policy that aims to balance the sizes + of available zones. + ▸ ANY - Instructs the cluster autoscaler to prioritize utilization + of unused reservations, and reduces preemption risk for Spot VMs. + + LOCATION_POLICY must be one of: BALANCED, ANY. + --max-nodes=MAX_NODES Maximum number of nodes per zone in the node pool. @@ -1230,6 +1258,20 @@ FLAGS --node-pool (or default node pool if unspecified) can scale. Ignored unless --enable-autoscaling is also specified. + --total-max-nodes=TOTAL_MAX_NODES + Maximum number of all nodes in the node pool. + + Maximum number of all nodes to which the node pool specified by + --node-pool (or default node pool if unspecified) can scale. Ignored + unless --enable-autoscaling is also specified. + + --total-min-nodes=TOTAL_MIN_NODES + Minimum number of all nodes in the node pool. + + Minimum number of all nodes to which the node pool specified by + --node-pool (or default node pool if unspecified) can scale. Ignored + unless --enable-autoscaling is also specified. + Master Authorized Networks --enable-master-authorized-networks diff --git a/gcloud/container/clusters/create-auto b/gcloud/container/clusters/create-auto index eb25a206d..150769159 100644 --- a/gcloud/container/clusters/create-auto +++ b/gcloud/container/clusters/create-auto @@ -5,6 +5,7 @@ NAME SYNOPSIS gcloud container clusters create-auto NAME [--async] [--autoprovisioning-network-tags=TAGS,[TAGS,...]] + [--binauthz-evaluation-mode=BINAUTHZ_EVALUATION_MODE] [--boot-disk-kms-key=BOOT_DISK_KMS_KEY] [--cluster-ipv4-cidr=CLUSTER_IPV4_CIDR] [--cluster-secondary-range-name=NAME] @@ -60,6 +61,13 @@ FLAGS https://cloud.google.com/sdk/gcloud/reference/compute/firewall-rules/create for examples. + Flags for Binary Authorization: + + --binauthz-evaluation-mode=BINAUTHZ_EVALUATION_MODE + Enable Binary Authorization for this cluster. + BINAUTHZ_EVALUATION_MODE must be one of: DISABLED, + PROJECT_SINGLETON_POLICY_ENFORCE. + --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/clusters/update b/gcloud/container/clusters/update index d21370fa4..70b0300e6 100644 --- a/gcloud/container/clusters/update +++ b/gcloud/container/clusters/update @@ -10,14 +10,14 @@ SYNOPSIS | --database-encryption-key=DATABASE_ENCRYPTION_KEY | --disable-database-encryption | --disable-default-snat | --disable-workload-identity | --enable-autoscaling - | --enable-binauthz | --enable-identity-service - | --enable-image-streaming | --enable-intra-node-visibility - | --enable-l4-ilb-subsetting | --enable-legacy-authorization - | --enable-master-authorized-networks | --enable-master-global-access - | --enable-network-policy | --enable-service-externalips - | --enable-shielded-nodes | --enable-stackdriver-kubernetes - | --enable-vertical-pod-autoscaling | --generate-password - | --maintenance-window=START_TIME | --node-locations=ZONE,[ZONE,...] + | --enable-identity-service | --enable-image-streaming + | --enable-intra-node-visibility | --enable-l4-ilb-subsetting + | --enable-legacy-authorization | --enable-master-authorized-networks + | --enable-master-global-access | --enable-network-policy + | --enable-service-externalips | --enable-shielded-nodes + | --enable-stackdriver-kubernetes | --enable-vertical-pod-autoscaling + | --generate-password | --maintenance-window=START_TIME + | --node-locations=ZONE,[ZONE,...] | --notification-config=[pubsub=ENABLED|DISABLED, pubsub-topic=TOPIC,...] | --private-ipv6-google-access-type=PRIVATE_IPV6_GOOGLE_ACCESS_TYPE @@ -26,7 +26,9 @@ SYNOPSIS | --start-credential-rotation | --start-ip-rotation | --update-addons=[ADDON=ENABLED|DISABLED,...] | --update-labels=[KEY=VALUE,...] | --workload-pool=WORKLOAD_POOL - | --clear-maintenance-window | --remove-maintenance-exclusion=NAME + | --binauthz-evaluation-mode=BINAUTHZ_EVALUATION_MODE + | --enable-binauthz | --clear-maintenance-window + | --remove-maintenance-exclusion=NAME | [--add-maintenance-exclusion-end=TIME_STAMP : --add-maintenance-exclusion-name=NAME --add-maintenance-exclusion-scope=SCOPE @@ -63,7 +65,10 @@ SYNOPSIS | --username=USERNAME, -u USERNAME) [--async] [--cloud-run-config=[load-balancer-type=EXTERNAL,...]] [--master-authorized-networks=NETWORK,[NETWORK,...]] - [--node-pool=NODE_POOL] [--max-nodes=MAX_NODES --min-nodes=MIN_NODES] + [--node-pool=NODE_POOL] + [--location-policy=LOCATION_POLICY --max-nodes=MAX_NODES + --min-nodes=MIN_NODES + --total-max-nodes=TOTAL_MAX_NODES --total-min-nodes=TOTAL_MIN_NODES] [--region=REGION | --zone=ZONE, -z ZONE] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -174,9 +179,6 @@ REQUIRED FLAGS Enables autoscaling in the node pool specified by --node-pool or the default node pool if --node-pool is not provided. - --enable-binauthz - Enable Binary Authorization for this cluster. - --enable-identity-service Enable Identity Service component on the cluster. @@ -459,6 +461,21 @@ REQUIRED FLAGS https://cloud.google.com/kubernetes-engine/docs/how-to/workload-identity + Flags for Binary Authorization: + + At most one of these can be specified: + + --binauthz-evaluation-mode=BINAUTHZ_EVALUATION_MODE + Enable Binary Authorization for this cluster. + BINAUTHZ_EVALUATION_MODE must be one of: DISABLED, + PROJECT_SINGLETON_POLICY_ENFORCE. + + --enable-binauthz + (DEPRECATED) Enable Binary Authorization for this cluster. + + The --enable-binauthz flag is deprecated. Please use + --binauthz-evaluation-mode instead. + At most one of these can be specified: --clear-maintenance-window @@ -868,14 +885,15 @@ REQUIRED FLAGS --monitoring=[COMPONENT,...] Set the components that have monitoring enabled. Valid component - values are: SYSTEM, WORKLOAD (Deprecated), NONE + values are: SYSTEM, WORKLOAD (Deprecated), NONE,API_SERVER, + CONTROLLER_MANAGER, SCHEDULER For more information, look at https://cloud.google.com/stackdriver/docs/solutions/gke/installing#available-metrics Examples: - $ gcloud container clusters update --monitoring=SYSTEM + $ gcloud container clusters update --monitoring=SYSTEM,API_SERVER $ gcloud container clusters update --monitoring=NONE --logging-service=LOGGING_SERVICE @@ -955,6 +973,17 @@ OPTIONAL FLAGS Cluster autoscaling + --location-policy=LOCATION_POLICY + Location policy specifies the algorithm used when scaling-up the node + pool. + + ▸ BALANCED - Is a best effort policy that aims to balance the sizes + of available zones. + ▸ ANY - Instructs the cluster autoscaler to prioritize utilization + of unused reservations, and reduces preemption risk for Spot VMs. + + LOCATION_POLICY must be one of: BALANCED, ANY. + --max-nodes=MAX_NODES Maximum number of nodes per zone in the node pool. @@ -969,6 +998,20 @@ OPTIONAL FLAGS --node-pool (or default node pool if unspecified) can scale. Ignored unless --enable-autoscaling is also specified. + --total-max-nodes=TOTAL_MAX_NODES + Maximum number of all nodes in the node pool. + + Maximum number of all nodes to which the node pool specified by + --node-pool (or default node pool if unspecified) can scale. Ignored + unless --enable-autoscaling is also specified. + + --total-min-nodes=TOTAL_MIN_NODES + Minimum number of all nodes in the node pool. + + Minimum number of all nodes to which the node pool specified by + --node-pool (or default node pool if unspecified) can scale. Ignored + unless --enable-autoscaling is also specified. + At most one of these can be specified: --region=REGION diff --git a/gcloud/container/fleet/memberships/register b/gcloud/container/fleet/memberships/register index e333b5750..02e6e3be4 100644 --- a/gcloud/container/fleet/memberships/register +++ b/gcloud/container/fleet/memberships/register @@ -37,11 +37,11 @@ DESCRIPTION corresponds to a service account that has been granted gkehub.connect permissions. - If the cluster is already registered to another Fleet, the registration is + If the cluster is already registered to another fleet, the registration is not successful. Rerunning this command against the same cluster with the same - MEMBERSHIP_NAME and target GKEFleet is successful and upgrades the Connect + MEMBERSHIP_NAME and target fleet is successful and upgrades the Connect Agent if a new agent is available. EXAMPLES diff --git a/gcloud/container/fleet/memberships/unregister b/gcloud/container/fleet/memberships/unregister index 82e08a852..db17c5eaf 100644 --- a/gcloud/container/fleet/memberships/unregister +++ b/gcloud/container/fleet/memberships/unregister @@ -29,7 +29,7 @@ DESCRIPTION To register a GKE cluster use --gke-cluster or --gke-uri flag (no --kubeconfig flag is required). - To only delete the Fleet membership resource, consider using the command: + To only delete the Fleet Membership resource, consider using the command: gcloud container fleet memberships delete. This command is intended to delete stale Fleet Membership resources as doing so on a fully registered cluster will skip some of the steps above and orphan in-cluster resources @@ -59,9 +59,8 @@ EXAMPLES POSITIONAL ARGUMENTS MEMBERSHIP_NAME - The membership name that corresponds to the cluster being unregistered. - To get list of all the memberships on the Fleet, consider using the - command: gcloud container fleet memberships list. + The membership name that you choose to uniquely represents the cluster + being registered on the fleet. REQUIRED FLAGS Cluster identifier. diff --git a/gcloud/container/hub/memberships/register b/gcloud/container/hub/memberships/register index b36a4e5db..37d8ef002 100644 --- a/gcloud/container/hub/memberships/register +++ b/gcloud/container/hub/memberships/register @@ -36,11 +36,11 @@ DESCRIPTION corresponds to a service account that has been granted gkehub.connect permissions. - If the cluster is already registered to another Fleet, the registration is + If the cluster is already registered to another fleet, the registration is not successful. Rerunning this command against the same cluster with the same - MEMBERSHIP_NAME and target GKEFleet is successful and upgrades the Connect + MEMBERSHIP_NAME and target fleet is successful and upgrades the Connect Agent if a new agent is available. EXAMPLES diff --git a/gcloud/container/hub/memberships/unregister b/gcloud/container/hub/memberships/unregister index 681e1167b..eb1b3796d 100644 --- a/gcloud/container/hub/memberships/unregister +++ b/gcloud/container/hub/memberships/unregister @@ -29,7 +29,7 @@ DESCRIPTION To register a GKE cluster use --gke-cluster or --gke-uri flag (no --kubeconfig flag is required). - To only delete the Fleet membership resource, consider using the command: + To only delete the Fleet Membership resource, consider using the command: gcloud container hub memberships delete. This command is intended to delete stale Fleet Membership resources as doing so on a fully registered cluster will skip some of the steps above and orphan in-cluster resources and agent @@ -59,9 +59,8 @@ EXAMPLES POSITIONAL ARGUMENTS MEMBERSHIP_NAME - The membership name that corresponds to the cluster being unregistered. - To get list of all the memberships on the Fleet, consider using the - command: gcloud container hub memberships list. + The membership name that you choose to uniquely represents the cluster + being registered on the fleet. REQUIRED FLAGS Cluster identifier. diff --git a/gcloud/container/node-pools/create b/gcloud/container/node-pools/create index c6bcf1003..d15e53fa8 100644 --- a/gcloud/container/node-pools/create +++ b/gcloud/container/node-pools/create @@ -34,7 +34,9 @@ SYNOPSIS [--tags=TAG,[TAG,...]] [--threads-per-core=THREADS_PER_CORE] [--workload-metadata=WORKLOAD_METADATA] [--create-pod-ipv4-range=[KEY=VALUE,...] | --pod-ipv4-range=NAME] - [--enable-autoscaling --max-nodes=MAX_NODES --min-nodes=MIN_NODES] + [--enable-autoscaling --location-policy=LOCATION_POLICY + --max-nodes=MAX_NODES --min-nodes=MIN_NODES + --total-max-nodes=TOTAL_MAX_NODES --total-min-nodes=TOTAL_MIN_NODES] [--region=REGION | --zone=ZONE, -z ZONE] [--reservation=RESERVATION --reservation-affinity=RESERVATION_AFFINITY] [--scopes=[SCOPE,...]; @@ -561,6 +563,17 @@ FLAGS Enables autoscaling in the node pool specified by --node-pool or the default node pool if --node-pool is not provided. + --location-policy=LOCATION_POLICY + Location policy specifies the algorithm used when scaling-up the node + pool. + + ▸ BALANCED - Is a best effort policy that aims to balance the sizes + of available zones. + ▸ ANY - Instructs the cluster autoscaler to prioritize utilization + of unused reservations, and reduces preemption risk for Spot VMs. + + LOCATION_POLICY must be one of: BALANCED, ANY. + --max-nodes=MAX_NODES Maximum number of nodes per zone in the node pool. @@ -575,6 +588,20 @@ FLAGS --node-pool (or default node pool if unspecified) can scale. Ignored unless --enable-autoscaling is also specified. + --total-max-nodes=TOTAL_MAX_NODES + Maximum number of all nodes in the node pool. + + Maximum number of all nodes to which the node pool specified by + --node-pool (or default node pool if unspecified) can scale. Ignored + unless --enable-autoscaling is also specified. + + --total-min-nodes=TOTAL_MIN_NODES + Minimum number of all nodes in the node pool. + + Minimum number of all nodes to which the node pool specified by + --node-pool (or default node pool if unspecified) can scale. Ignored + unless --enable-autoscaling is also specified. + At most one of these can be specified: --region=REGION diff --git a/gcloud/container/node-pools/update b/gcloud/container/node-pools/update index 30780e981..f1864d95f 100644 --- a/gcloud/container/node-pools/update +++ b/gcloud/container/node-pools/update @@ -11,8 +11,10 @@ SYNOPSIS | --node-taints=[NODE_TAINT,...] | --system-config-from-file=SYSTEM_CONFIG_FROM_FILE | --tags=[TAG,...] | --workload-metadata=WORKLOAD_METADATA - | --enable-autoprovisioning - --enable-autoscaling --max-nodes=MAX_NODES --min-nodes=MIN_NODES + | --enable-autoprovisioning --enable-autoscaling + --location-policy=LOCATION_POLICY --max-nodes=MAX_NODES + --min-nodes=MIN_NODES + --total-max-nodes=TOTAL_MAX_NODES --total-min-nodes=TOTAL_MIN_NODES | --enable-autorepair --enable-autoupgrade | --enable-blue-green-upgrade --enable-surge-upgrade --max-surge-upgrade=MAX_SURGE_UPGRADE @@ -202,6 +204,18 @@ REQUIRED FLAGS Enables autoscaling in the node pool specified by --node-pool or the default node pool if --node-pool is not provided. + --location-policy=LOCATION_POLICY + Location policy specifies the algorithm used when scaling-up the + node pool. + + ▫ BALANCED - Is a best effort policy that aims to balance the + sizes of available zones. + ▫ ANY - Instructs the cluster autoscaler to prioritize + utilization of unused reservations, and reduces preemption risk + for Spot VMs. + + LOCATION_POLICY must be one of: BALANCED, ANY. + --max-nodes=MAX_NODES Maximum number of nodes per zone in the node pool. @@ -216,6 +230,20 @@ REQUIRED FLAGS by --node-pool (or default node pool if unspecified) can scale. Ignored unless --enable-autoscaling is also specified. + --total-max-nodes=TOTAL_MAX_NODES + Maximum number of all nodes in the node pool. + + Maximum number of all nodes to which the node pool specified by + --node-pool (or default node pool if unspecified) can scale. + Ignored unless --enable-autoscaling is also specified. + + --total-min-nodes=TOTAL_MIN_NODES + Minimum number of all nodes in the node pool. + + Minimum number of all nodes to which the node pool specified by + --node-pool (or default node pool if unspecified) can scale. + Ignored unless --enable-autoscaling is also specified. + Node management --enable-autorepair diff --git a/gcloud/dataplex/tasks/create b/gcloud/dataplex/tasks/create index 27432e0cd..ceb3f74a2 100644 --- a/gcloud/dataplex/tasks/create +++ b/gcloud/dataplex/tasks/create @@ -5,6 +5,7 @@ SYNOPSIS gcloud dataplex tasks create (TASK : --lake=LAKE --location=LOCATION) (--execution-service-account=EXECUTION_SERVICE_ACCOUNT : --execution-args=EXECUTION_ARGS + --execution-project=EXECUTION_PROJECT --kms-key=KMS_KEY --max-job-execution-lifetime=MAX_JOB_EXECUTION_LIFETIME) ((--spark-main-class=SPARK_MAIN_CLASS | --spark-main-jar-file-uri=SPARK_MAIN_JAR_FILE_URI @@ -15,6 +16,7 @@ SYNOPSIS --spark-file-uris=[SPARK_FILE_URIS,...] --batch-executors-count=BATCH_EXECUTORS_COUNT --batch-max-executors-count=BATCH_MAX_EXECUTORS_COUNT + --container-image=CONTAINER_IMAGE --container-image-java-jars=[CONTAINER_IMAGE_JAVA_JARS,...] --container-image-properties=CONTAINER_IMAGE_PROPERTIES --container-image-python-packages=[CONTAINER_IMAGE_PYTHON_PACKAGES, @@ -128,6 +130,15 @@ REQUIRED FLAGS keys being present in the args, then TASK_ARGS will be passed as the last argument. + --execution-project=EXECUTION_PROJECT + The project in which jobs are run. By default, the project containing + the Lake is used. If a project is provided, the + --execution-service-account must belong to this same project. + + --kms-key=KMS_KEY + The Cloud KMS key to use for encryption, of the form: + projects/{project_number}/locations/{location_id}/keyRings/{key-ring-name}/cryptoKeys/{key-name} + --max-job-execution-lifetime=MAX_JOB_EXECUTION_LIFETIME The maximum duration before the job execution expires. @@ -182,6 +193,9 @@ REQUIRED FLAGS Container Image Runtime Configuration. + --container-image=CONTAINER_IMAGE + Optional custom container image for the job. + --container-image-java-jars=[CONTAINER_IMAGE_JAVA_JARS,...] A list of Java JARS to add to the classpath. Valid input includes Cloud Storage URIs to Jar binaries. For example, diff --git a/gcloud/dataplex/tasks/update b/gcloud/dataplex/tasks/update index be88e9667..30b76b203 100644 --- a/gcloud/dataplex/tasks/update +++ b/gcloud/dataplex/tasks/update @@ -6,13 +6,15 @@ SYNOPSIS [--async] [--description=DESCRIPTION] [--display-name=DISPLAY_NAME] [--update-labels=[KEY=VALUE,...]] [--clear-labels | --remove-labels=[KEY,...]] - [--execution-args=EXECUTION_ARGS + [--execution-args=EXECUTION_ARGS --execution-project=EXECUTION_PROJECT --execution-service-account=EXECUTION_SERVICE_ACCOUNT + --kms-key=KMS_KEY --max-job-execution-lifetime=MAX_JOB_EXECUTION_LIFETIME] [--spark-archive-uris=[SPARK_ARCHIVE_URIS,...] --spark-file-uris=[SPARK_FILE_URIS,...] --batch-executors-count=BATCH_EXECUTORS_COUNT --batch-max-executors-count=BATCH_MAX_EXECUTORS_COUNT + --container-image=CONTAINER_IMAGE --container-image-java-jars=[CONTAINER_IMAGE_JAVA_JARS,...] --container-image-properties=CONTAINER_IMAGE_PROPERTIES --container-image-python-packages=[CONTAINER_IMAGE_PYTHON_PACKAGES, @@ -132,10 +134,19 @@ FLAGS case of other keys being present in the args, then TASK_ARGS will be passed as the last argument. + --execution-project=EXECUTION_PROJECT + The project in which jobs are run. By default, the project containing + the Lake is used. If a project is provided, the + --execution-service-account must belong to this same project. + --execution-service-account=EXECUTION_SERVICE_ACCOUNT Service account to use to execute a task. If not provided, the default Compute service account for the project is used. + --kms-key=KMS_KEY + The Cloud KMS key to use for encryption, of the form: + projects/{project_number}/locations/{location_id}/keyRings/{key-ring-name}/cryptoKeys/{key-name} + --max-job-execution-lifetime=MAX_JOB_EXECUTION_LIFETIME The maximum duration before the job execution expires. @@ -161,6 +172,9 @@ FLAGS Container Image Runtime Configuration. + --container-image=CONTAINER_IMAGE + Optional custom container image for the job. + --container-image-java-jars=[CONTAINER_IMAGE_JAVA_JARS,...] A list of Java JARS to add to the classpath. Valid input includes Cloud Storage URIs to Jar binaries. For example, diff --git a/gcloud/dataproc/clusters/gke/create b/gcloud/dataproc/clusters/gke/create index 48bb5b2a2..d8b2a7746 100644 --- a/gcloud/dataproc/clusters/gke/create +++ b/gcloud/dataproc/clusters/gke/create @@ -134,82 +134,42 @@ OPTIONAL FLAGS The following KEYs must be specified: - KEY Type Example Description - name string `my-node-pool` Name of the node pool. - roles repeated string `default;spark-driver` Roles that this node - pool should perform. - Valid values are - `default`, - `controller`, - `spark-driver`, - `spark-executor`. + ----------------------------------------------------------------------------------------------------------- + KEY Type Example Description + ------ ---------------- ------------------------ ---------------------------------------------------------- + name string `my-node-pool` Name of the node pool. - The following KEYs may be specified. + roles repeated string `default;spark-driver` Roles that this node pool should perform. Valid values are + `default`, `controller`, `spark-driver`, `spark-executor`. + ----------------------------------------------------------------------------------------------------------- - KEY Type Example Description - machineType string `n1-standard-8` Compute - Engine - machine type - to use. - preemptible boolean `false` If true, - then this - node pool - uses - preemptible - VMs. This - cannot be - true on the - node pool - with the - `controllers - ` role (or - `default` - role if - `controllers - ` role is - not - specified). - localSsdCount int `2` The number - of local - SSDs to - attach to - each node. - accelerator repeated string `nvidia-tesla-a100=1` Accelerators - to attach to - each node. - In the - format - NAME=COUNT. - minCpuPlatform string `Intel Skylake` Minimum CPU - platform for - each node. - locations repeated string `us-west1-a;us-west1-c` Zones within - the location - of the GKE - cluster. All - `--pools` - flags for a - single - Dataproc - cluster must - have - identical - locations. - min int `0` Minimum - number of - nodes per - zone that - this node - pool can - scale down - to. - max int `10` Maximum - number of - nodes per - zone that - this node - pool can - scale up to. + The following KEYs may be specified: + + ---------------------------------------------------------------------------------------------------------------------------------------------------------------- + KEY Type Example Description + --------------- ---------------- --------------------------------------------- --------------------------------------------------------------------------------- + machineType string `n1-standard-8` Compute Engine machine type to use. + + preemptible boolean `false` If true, then this node pool uses preemptible VMs. + This cannot be true on the node pool with the `controllers` role + (or `default` role if `controllers` role is not specified). + + localSsdCount int `2` The number of local SSDs to attach to each node. + + accelerator repeated string `nvidia-tesla-a100=1` Accelerators to attach to each node. In the format NAME=COUNT. + + minCpuPlatform string `Intel Skylake` Minimum CPU platform for each node. + + bootDiskKmsKey string `projects/project-id/locations/us-central1 The Customer Managed Encryption Key (CMEK) used to encrypt + /keyRings/keyRing-name/cryptoKeys/key-name` the boot disk attached to each node in the node pool. + + locations repeated string `us-west1-a;us-west1-c` Zones within the location of the GKE cluster. + All `--pools` flags for a single Dataproc cluster must have identical locations. + + min int `0` Minimum number of nodes per zone that this node pool can scale down to. + + max int `10` Maximum number of nodes per zone that this node pool can scale up to. + ---------------------------------------------------------------------------------------------------------------------------------------------------------------- --properties=[PREFIX:PROPERTY=VALUE,...] Specifies configuration properties for installed packages, such as diff --git a/gcloud/datastream/connection-profiles/create b/gcloud/datastream/connection-profiles/create index 1f65c9a0d..9a3632129 100644 --- a/gcloud/datastream/connection-profiles/create +++ b/gcloud/datastream/connection-profiles/create @@ -5,8 +5,8 @@ NAME SYNOPSIS gcloud datastream connection-profiles create (CONNECTION_PROFILE : --location=LOCATION) --display-name=DISPLAY_NAME - --type=TYPE - ([--bucket=BUCKET : --root-path=ROOT_PATH] + --type=TYPE [--force] [--labels=[KEY=VALUE,...]] + [[--bucket=BUCKET : --root-path=ROOT_PATH] | --database-service=DATABASE_SERVICE --oracle-hostname=ORACLE_HOSTNAME --oracle-port=ORACLE_PORT --oracle-username=ORACLE_USERNAME (--oracle-password=ORACLE_PASSWORD @@ -14,8 +14,7 @@ SYNOPSIS --mysql-port=MYSQL_PORT --mysql-username=MYSQL_USERNAME (--mysql-password=MYSQL_PASSWORD | --mysql-prompt-for-password) : --ca-certificate=CA_CERTIFICATE - --client-certificate=CLIENT_CERTIFICATE --client-key=CLIENT_KEY]) - [--force] [--labels=[KEY=VALUE,...]] + --client-certificate=CLIENT_CERTIFICATE --client-key=CLIENT_KEY]] [--private-connection=PRIVATE_CONNECTION : --static-ip-connectivity | [--forward-ssh-hostname=FORWARD_SSH_HOSTNAME --forward-ssh-username=FORWARD_SSH_USERNAME @@ -52,6 +51,11 @@ EXAMPLES --bucket=fake-bucket --root-path=/root/path \ --display-name=my-profile + To create a connection profile for BigQuery: + + $ gcloud datastream connection-profiles create CONNECTION_PROFILE \ + --location=us-central1 --type=bigquery --display-name=my-profile + POSITIONAL ARGUMENTS Connection profile resource - The connection profile to create. The arguments in this group can be used to specify the attributes of this @@ -84,9 +88,21 @@ REQUIRED FLAGS Friendly name for the connection profile. --type=TYPE - Type can be MYSQL, ORACLE or GOOGLE-CLOUD-STORAGE + Type can be MYSQL, ORACLE, GOOGLE-CLOUD-STORAGE or BIGQUERY - Exactly one of these must be specified: +OPTIONAL FLAGS + --force + Create the connection profile without validating it. + + --labels=[KEY=VALUE,...] + List of label KEY=VALUE pairs to add. + + Keys must start with a lowercase character and contain only hyphens + (-), underscores (_), lowercase characters, and numbers. Values must + contain only hyphens (-), underscores (_), lowercase characters, and + numbers. + + At most one of these can be specified: --bucket=BUCKET The full project and resource path for Cloud Storage bucket including @@ -182,18 +198,6 @@ REQUIRED FLAGS This flag must be specified if any of the other arguments in this group are specified. -OPTIONAL FLAGS - --force - Create the connection profile without validating it. - - --labels=[KEY=VALUE,...] - List of label KEY=VALUE pairs to add. - - Keys must start with a lowercase character and contain only hyphens - (-), underscores (_), lowercase characters, and numbers. Values must - contain only hyphens (-), underscores (_), lowercase characters, and - numbers. - At most one of these can be specified: Private connection resource - Resource ID of the private connection. diff --git a/gcloud/datastream/connection-profiles/update b/gcloud/datastream/connection-profiles/update index d178ef365..9d72ea61e 100644 --- a/gcloud/datastream/connection-profiles/update +++ b/gcloud/datastream/connection-profiles/update @@ -54,6 +54,11 @@ EXAMPLES --bucket=fake-bucket --root-path=/root/path \ --display-name=my-profile + To update a connection profile for Google Cloud Storage: + + $ gcloud datastream connection-profiles update CONNECTION_PROFILE \ + --location=us-central1 --type=bigquery --display-name=my-profile + POSITIONAL ARGUMENTS Connection profile resource - The connection profile to update. The arguments in this group can be used to specify the attributes of this @@ -83,7 +88,7 @@ POSITIONAL ARGUMENTS REQUIRED FLAGS --type=TYPE - Type can be MYSQL, ORACLE or GOOGLE-CLOUD-STORAGE + Type can be MYSQL, ORACLE, GOOGLE-CLOUD-STORAGE or BIGQUERY OPTIONAL FLAGS --display-name=DISPLAY_NAME diff --git a/gcloud/datastream/streams/create b/gcloud/datastream/streams/create index 33c6757dd..447409785 100644 --- a/gcloud/datastream/streams/create +++ b/gcloud/datastream/streams/create @@ -8,7 +8,8 @@ SYNOPSIS | --backfill-all --mysql-excluded-objects=MYSQL_EXCLUDED_OBJECTS | --oracle-excluded-objects=ORACLE_EXCLUDED_OBJECTS) (--destination=DESTINATION - --gcs-destination-config=GCS_DESTINATION_CONFIG) + (--bigquery-destination-config=BIGQUERY_DESTINATION_CONFIG + | --gcs-destination-config=GCS_DESTINATION_CONFIG)) (--source=SOURCE (--mysql-source-config=MYSQL_SOURCE_CONFIG | --oracle-source-config=ORACLE_SOURCE_CONFIG)) [--labels=[KEY=VALUE,...]] [--force | --validate-only] @@ -37,6 +38,15 @@ EXAMPLES --gcs-destination-config=destination_config.json \ --backfill-all --mysql-excluded-objects=excluded_objects.json + To create a stream with an Oracle source and a BigQuery destination: + + $ gcloud datastream streams create STREAM --location=us-central1 \ + --display-name=my-stream --source=source \ + --oracle-source-config=source_config.json \ + --destination=destination \ + --bigquery-destination-config=destination_config.json \ + --backfill-none + POSITIONAL ARGUMENTS Stream resource - The stream to create. The arguments in this group can be used to specify the attributes of this resource. (NOTE) Some attributes @@ -105,21 +115,37 @@ REQUIRED FLAGS connection_profile. To set the connection_profile attribute: ▫ provide the argument --destination on the command line. - --gcs-destination-config=GCS_DESTINATION_CONFIG - Path to a YAML (or JSON) file containing the configuration for Google - Cloud Storage Destination Config. + Exactly one of these must be specified: - The JSON file is formatted as follows: + --bigquery-destination-config=BIGQUERY_DESTINATION_CONFIG + Path to a YAML (or JSON) file containing the configuration for + Google BigQuery Destination Config. - { - "path": "some/path", - "file_rotation_mb":5, - "file_rotation_interval":"15s", - "avro_file_format": {} - } + The JSON file is formatted as follows: - This flag must be specified if any of the other arguments in this - group are specified. + { + "source_hierarchy_datasets": { + "dataset_template": { + "location": "us-central1", + "dataset_id_prefix": "my_prefix", + "kms_key_name": "projects/{project}/locations/{location}/keyRings/{key_ring}/cryptoKeys/{cryptoKey}" + } + }, + "data_freshness": 3600 + } + + --gcs-destination-config=GCS_DESTINATION_CONFIG + Path to a YAML (or JSON) file containing the configuration for + Google Cloud Storage Destination Config. + + The JSON file is formatted as follows: + + { + "path": "some/path", + "file_rotation_mb":5, + "file_rotation_interval":"15s", + "avro_file_format": {} + } This must be specified. diff --git a/gcloud/datastream/streams/update b/gcloud/datastream/streams/update index 344306b8f..5c6d9e559 100644 --- a/gcloud/datastream/streams/update +++ b/gcloud/datastream/streams/update @@ -10,7 +10,8 @@ SYNOPSIS | --oracle-excluded-objects=ORACLE_EXCLUDED_OBJECTS] [--clear-labels | --remove-labels=[KEY,...]] [--destination=DESTINATION - : --gcs-destination-config=GCS_DESTINATION_CONFIG] + : --bigquery-destination-config=BIGQUERY_DESTINATION_CONFIG + | --gcs-destination-config=GCS_DESTINATION_CONFIG] [--force | --validate-only] [--source=SOURCE : --mysql-source-config=MYSQL_SOURCE_CONFIG | --oracle-source-config=ORACLE_SOURCE_CONFIG] [GCLOUD_WIDE_FLAG ...] @@ -140,18 +141,37 @@ FLAGS connection_profile. To set the connection_profile attribute: ▸ provide the argument --destination on the command line. - --gcs-destination-config=GCS_DESTINATION_CONFIG - Path to a YAML (or JSON) file containing the configuration for Google - Cloud Storage Destination Config. + At most one of these can be specified: - The JSON file is formatted as follows: + --bigquery-destination-config=BIGQUERY_DESTINATION_CONFIG + Path to a YAML (or JSON) file containing the configuration for Google + BigQuery Destination Config. - { - "path": "some/path", - "file_rotation_mb":5, - "file_rotation_interval":"15s", - "avro_file_format": {} - } + The JSON file is formatted as follows: + + { + "source_hierarchy_datasets": { + "dataset_template": { + "location": "us-central1", + "dataset_id_prefix": "my_prefix", + "kms_key_name": "projects/{project}/locations/{location}/keyRings/{key_ring}/cryptoKeys/{cryptoKey}" + } + }, + "data_freshness": 3600 + } + + --gcs-destination-config=GCS_DESTINATION_CONFIG + Path to a YAML (or JSON) file containing the configuration for Google + Cloud Storage Destination Config. + + The JSON file is formatted as follows: + + { + "path": "some/path", + "file_rotation_mb":5, + "file_rotation_interval":"15s", + "avro_file_format": {} + } At most one of these can be specified: diff --git a/gcloud/deploy/targets/rollback b/gcloud/deploy/targets/rollback index 9a4581c63..f191932e5 100644 --- a/gcloud/deploy/targets/rollback +++ b/gcloud/deploy/targets/rollback @@ -3,7 +3,8 @@ NAME SYNOPSIS gcloud deploy targets rollback (TARGET : --region=REGION) - --delivery-pipeline=DELIVERY_PIPELINE [--description=DESCRIPTION] + --delivery-pipeline=DELIVERY_PIPELINE [--annotations=[KEY=VALUE,...]] + [--description=DESCRIPTION] [--labels=[KEY=VALUE,...]] [--release=RELEASE] [--rollout-id=ROLLOUT_ID] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -51,9 +52,30 @@ REQUIRED FLAGS The name of the Cloud Deploy delivery pipeline OPTIONAL FLAGS + --annotations=[KEY=VALUE,...] + Annotations to apply to the rollback. Annotations take the form of + key/value string pairs. + + Examples: + + Add annotations: + + $ gcloud deploy targets rollback \ + --annotations="from_target=test,status=stable" + --description=DESCRIPTION Description of rollout created during a rollback. + --labels=[KEY=VALUE,...] + Labels to apply to the rollback. Labels take the form of key/value + string pairs. + + Examples: + + Add labels: + + $ gcloud deploy targets rollback --labels="commit=abc123,author=foo" + --release=RELEASE Name of the release to rollback to. diff --git a/gcloud/eventarc/channels/create b/gcloud/eventarc/channels/create index 4fabf7a43..678552636 100644 --- a/gcloud/eventarc/channels/create +++ b/gcloud/eventarc/channels/create @@ -74,7 +74,7 @@ FLAGS complete. --crypto-key=CRYPTO_KEY - The fully qualified name of the crypto key to use for customer-managed + Fully qualified name of the crypto key to use for customer-managed encryption. If this is unspecified, Google-managed keys will be used for encryption. diff --git a/gcloud/eventarc/channels/delete b/gcloud/eventarc/channels/delete index 86d0f4ab9..fdfbd3fbc 100644 --- a/gcloud/eventarc/channels/delete +++ b/gcloud/eventarc/channels/delete @@ -1,12 +1,12 @@ NAME - gcloud eventarc channels delete - deletes an Eventarc channel + gcloud eventarc channels delete - delete an Eventarc channel SYNOPSIS gcloud eventarc channels delete (CHANNEL : --location=LOCATION) [--async] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - Deletes an Eventarc channel. + Delete an Eventarc channel. EXAMPLES To delete the channel my-channel in location us-central1, run: diff --git a/gcloud/eventarc/channels/describe b/gcloud/eventarc/channels/describe index 66d1358fb..6776e27b8 100644 --- a/gcloud/eventarc/channels/describe +++ b/gcloud/eventarc/channels/describe @@ -1,12 +1,12 @@ NAME - gcloud eventarc channels describe - describes an Eventarc channel + gcloud eventarc channels describe - describe an Eventarc channel SYNOPSIS gcloud eventarc channels describe (CHANNEL : --location=LOCATION) [GCLOUD_WIDE_FLAG ...] DESCRIPTION - Describes an Eventarc channel. + Describe an Eventarc channel. EXAMPLES To describe the channel my-channel in location us-central1, run: diff --git a/gcloud/eventarc/channels/help b/gcloud/eventarc/channels/help index 796bc724b..13a9f9cda 100644 --- a/gcloud/eventarc/channels/help +++ b/gcloud/eventarc/channels/help @@ -19,13 +19,13 @@ COMMANDS Create an Eventarc channel. delete - Deletes an Eventarc channel. + Delete an Eventarc channel. describe - Describes an Eventarc channel. + Describe an Eventarc channel. list List Eventarc channels. update - Updates an Eventarc channel. + Update an Eventarc channel. diff --git a/gcloud/eventarc/channels/update b/gcloud/eventarc/channels/update index 4ed2621b6..5e90619e8 100644 --- a/gcloud/eventarc/channels/update +++ b/gcloud/eventarc/channels/update @@ -1,12 +1,12 @@ NAME - gcloud eventarc channels update - updates an Eventarc channel + gcloud eventarc channels update - update an Eventarc channel SYNOPSIS gcloud eventarc channels update (CHANNEL : --location=LOCATION) [--async] [--clear-crypto-key | --crypto-key=CRYPTO_KEY] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - Updates an Eventarc channel. + Update an Eventarc channel. EXAMPLES To update the channel my-channel in location us-central1, run: @@ -62,9 +62,9 @@ FLAGS continue to be encrypted using Google-managed keys. --crypto-key=CRYPTO_KEY - The fully qualified name of the crypto key to use for - customer-managed encryption. If this is unspecified, Google-managed - keys will be used for encryption. + Fully qualified name of the crypto key to use for customer-managed + encryption. If this is unspecified, Google-managed keys will be used + for encryption. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/eventarc/google-channels/describe b/gcloud/eventarc/google-channels/describe index cf904379f..c5b99a504 100644 --- a/gcloud/eventarc/google-channels/describe +++ b/gcloud/eventarc/google-channels/describe @@ -1,5 +1,5 @@ NAME - gcloud eventarc google-channels describe - describes an Eventarc Google + gcloud eventarc google-channels describe - describe an Eventarc Google channel SYNOPSIS @@ -7,10 +7,10 @@ SYNOPSIS [GCLOUD_WIDE_FLAG ...] DESCRIPTION - Describes an Eventarc Google channel. + Describe an Eventarc Google channel. EXAMPLES - To describe the google channel in location us-central1, run: + To describe the Google channel in location us-central1, run: $ gcloud eventarc google-channels describe --location=us-central1 diff --git a/gcloud/eventarc/google-channels/help b/gcloud/eventarc/google-channels/help index 1342bd787..910316f48 100644 --- a/gcloud/eventarc/google-channels/help +++ b/gcloud/eventarc/google-channels/help @@ -16,7 +16,7 @@ COMMANDS COMMAND is one of the following: describe - Describes an Eventarc Google channel. + Describe an Eventarc Google channel. update - Updates an Eventarc Google channel. + Update an Eventarc Google channel. diff --git a/gcloud/eventarc/google-channels/update b/gcloud/eventarc/google-channels/update index 23ad8afd2..30cf7512f 100644 --- a/gcloud/eventarc/google-channels/update +++ b/gcloud/eventarc/google-channels/update @@ -1,19 +1,19 @@ NAME - gcloud eventarc google-channels update - updates an Eventarc Google channel + gcloud eventarc google-channels update - update an Eventarc Google channel SYNOPSIS gcloud eventarc google-channels update [--location=LOCATION] [--clear-crypto-key | --crypto-key=CRYPTO_KEY] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - Updates an Eventarc Google channel. + Update an Eventarc Google channel. EXAMPLES - To update the google channel in location us-central1, run: + To update the Google channel in location us-central1, run: $ gcloud eventarc google-channels update --location=us-central1 - To configure the google channel in location us-central1 with a Cloud KMS + To configure the Google channel in location us-central1 with a Cloud KMS CryptoKey, run: $ gcloud eventarc google-channels update --location=us-central1 \ @@ -43,9 +43,9 @@ FLAGS continue to be encrypted using Google-managed keys. --crypto-key=CRYPTO_KEY - The fully qualified name of the crypto key to use for - customer-managed encryption. If this is unspecified, Google-managed - keys will be used for encryption. + Fully qualified name of the crypto key to use for customer-managed + encryption. If this is unspecified, Google-managed keys will be used + for encryption. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/functions/deploy b/gcloud/functions/deploy index f5f7cbd03..4ef5c6d75 100644 --- a/gcloud/functions/deploy +++ b/gcloud/functions/deploy @@ -3,9 +3,10 @@ NAME SYNOPSIS gcloud functions deploy (NAME : --region=REGION) [--allow-unauthenticated] - [--egress-settings=EGRESS_SETTINGS] [--entry-point=ENTRY_POINT] - [--ignore-file=IGNORE_FILE] [--ingress-settings=INGRESS_SETTINGS] - [--memory=MEMORY] [--retry] [--runtime=RUNTIME] + [--docker-registry=DOCKER_REGISTRY] [--egress-settings=EGRESS_SETTINGS] + [--entry-point=ENTRY_POINT] [--ignore-file=IGNORE_FILE] + [--ingress-settings=INGRESS_SETTINGS] [--memory=MEMORY] [--retry] + [--runtime=RUNTIME] [--security-level=SECURITY_LEVEL; default="secure-always"] [--service-account=SERVICE_ACCOUNT] [--source=SOURCE] [--stage-bucket=STAGE_BUCKET] [--timeout=TIMEOUT] @@ -88,6 +89,16 @@ FLAGS If set, makes this a public function. This will allow all callers, without checking authentication. + --docker-registry=DOCKER_REGISTRY + Docker Registry to use for storing the function's Docker images. The + option container-registry is used by default. + + Warning: Artifact Registry and Container Registry have different image + storage costs. For more details, please see + https://cloud.google.com/functions/pricing#deployment_costs. + + DOCKER_REGISTRY must be one of: artifact-registry, container-registry. + --egress-settings=EGRESS_SETTINGS Egress settings controls what traffic is diverted through the VPC Access Connector resource. By default private-ranges-only will be used. @@ -133,7 +144,7 @@ FLAGS ◆ nodejs14: Node.js 14 ◆ nodejs16: Node.js 16 ◆ php74: PHP 7.4 - ◆ php81: PHP 8.1 (preview) + ◆ php81: PHP 8.1 ◆ python37: Python 3.7 ◆ python38: Python 3.8 ◆ python39: Python 3.9 diff --git a/gcloud/functions/help b/gcloud/functions/help index 23e86ff0a..ce4661a8c 100644 --- a/gcloud/functions/help +++ b/gcloud/functions/help @@ -24,6 +24,9 @@ GROUPS regions List regions available to Google Cloud Functions. + runtimes + List runtimes available to Google Cloud Functions. + COMMANDS COMMAND is one of the following: diff --git a/gcloud/functions/runtimes/help b/gcloud/functions/runtimes/help new file mode 100644 index 000000000..64c679491 --- /dev/null +++ b/gcloud/functions/runtimes/help @@ -0,0 +1,28 @@ +NAME + gcloud functions runtimes - list runtimes available to Google Cloud + Functions + +SYNOPSIS + gcloud functions runtimes COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + List runtimes available to Google Cloud Functions. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + list + List runtimes available to Google Cloud Functions. + +NOTES + These variants are also available: + + $ gcloud alpha functions runtimes + + $ gcloud beta functions runtimes + diff --git a/gcloud/functions/runtimes/list b/gcloud/functions/runtimes/list new file mode 100644 index 000000000..15a748051 --- /dev/null +++ b/gcloud/functions/runtimes/list @@ -0,0 +1,69 @@ +NAME + gcloud functions runtimes list - list runtimes available to Google Cloud + Functions + +SYNOPSIS + gcloud functions runtimes list [--region=REGION] [--filter=EXPRESSION] + [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + List runtimes available to Google Cloud Functions. + +EXAMPLES + To list the available runtimes, run: + + $ gcloud functions runtimes list + +FLAGS + --region=REGION + Only show runtimes within the region. Overrides the default + functions/region property value for this command invocation. + +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 functions runtimes list + + $ gcloud beta functions runtimes list + diff --git a/gcloud/kms/keys/versions/import b/gcloud/kms/keys/versions/import index 485408cd3..97d3d7834 100644 --- a/gcloud/kms/keys/versions/import +++ b/gcloud/kms/keys/versions/import @@ -6,9 +6,8 @@ SYNOPSIS gcloud kms keys versions import --algorithm=ALGORITHM --import-job=IMPORT_JOB [--key=KEY] [--keyring=KEYRING] [--location=LOCATION] [--public-key-file=PUBLIC_KEY_FILE] - [--rsa-aes-wrapped-key-file=RSA_AES_WRAPPED_KEY_FILE] [--target-key-file=TARGET_KEY_FILE] [--version=VERSION] - [GCLOUD_WIDE_FLAG ...] + [--wrapped-key-file=WRAPPED_KEY_FILE] [GCLOUD_WIDE_FLAG ...] DESCRIPTION Imports wrapped key material into a new version within an existing crypto @@ -24,7 +23,7 @@ EXAMPLES $ gcloud kms keys versions import --location=global \ --keyring=fellowship --key=frodo --import-job=strider \ - --rsa-aes-wrapped-key-file=path/to/target/key \ + --wrapped-key-file=path/to/target/key \ --algorithm=google-symmetric-encryption REQUIRED FLAGS @@ -58,20 +57,20 @@ OPTIONAL FLAGS Location of the keyring. --public-key-file=PUBLIC_KEY_FILE - Optional path to the public key of the ImportJob, used to wrap the key - for import. If missing, the public key will be fetched on your behalf. - - --rsa-aes-wrapped-key-file=RSA_AES_WRAPPED_KEY_FILE - Path to the wrapped RSA AES key file to import. + Path to the public key of the ImportJob, used to wrap the key for + import. If missing, the public key will be fetched on your behalf. --target-key-file=TARGET_KEY_FILE - Optional path to the unwrapped target key to import into a Cloud KMS - key version. If specified, the key will be securely wrapped before + Path to the unwrapped target key to import into a Cloud KMS key + version. If specified, the key will be securely wrapped before transmission to Google. --version=VERSION Version to re-import into. Omit this field for first-time import. + --wrapped-key-file=WRAPPED_KEY_FILE + Path to the RSA/RSA+AES wrapped key file to import. + 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/ml/speech/recognize b/gcloud/ml/speech/recognize index 68a7c7506..af8e586f7 100644 --- a/gcloud/ml/speech/recognize +++ b/gcloud/ml/speech/recognize @@ -91,6 +91,17 @@ OPTIONAL FLAGS audio that is not one of the specific audio models. For example, long-form audio. Ideally the audio is high-fidelity, recorded at a 16khz or greater sampling rate. + latest_long + Use this model for any kind of long form content such as media or + spontaneous speech and conversations. Consider using this model in + place of the video model, especially if the video model is not + available in your target language. You can also use this in place + of the default model. + latest_short + Use this model for short utterances that are a few seconds in + length. It is useful for trying to capture commands or other single + shot directed speech use cases. Consider using this model instead + of the command and search model. medical_conversation Best for audio that originated from a conversation between a medical provider and patient. diff --git a/gcloud/ml/speech/recognize-long-running b/gcloud/ml/speech/recognize-long-running index 550750b09..4e974d7ca 100644 --- a/gcloud/ml/speech/recognize-long-running +++ b/gcloud/ml/speech/recognize-long-running @@ -100,6 +100,17 @@ OPTIONAL FLAGS audio that is not one of the specific audio models. For example, long-form audio. Ideally the audio is high-fidelity, recorded at a 16khz or greater sampling rate. + latest_long + Use this model for any kind of long form content such as media or + spontaneous speech and conversations. Consider using this model in + place of the video model, especially if the video model is not + available in your target language. You can also use this in place + of the default model. + latest_short + Use this model for short utterances that are a few seconds in + length. It is useful for trying to capture commands or other single + shot directed speech use cases. Consider using this model instead + of the command and search model. medical_conversation Best for audio that originated from a conversation between a medical provider and patient. diff --git a/gcloud/recommender/insights/list b/gcloud/recommender/insights/list index b2fbab5d2..df4128a18 100644 --- a/gcloud/recommender/insights/list +++ b/gcloud/recommender/insights/list @@ -10,7 +10,7 @@ SYNOPSIS [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - This command will list all insights for a give cloud entity, location and + This command will list all insights for a given cloud entity, location and insight type. Supported insight-types can be found here: https://cloud.google.com/recommender/docs/insights/insight-types. Currently the following cloud_entity_types are supported: project, billing_account, diff --git a/gcloud/redis/instances/create b/gcloud/redis/instances/create index 575fe17cd..78760fc27 100644 --- a/gcloud/redis/instances/create +++ b/gcloud/redis/instances/create @@ -9,6 +9,9 @@ SYNOPSIS [--maintenance-window-day=MAINTENANCE_WINDOW_DAY] [--maintenance-window-hour=MAINTENANCE_WINDOW_HOUR] [--network=NETWORK; default="default"] + [--persistence-mode=PERSISTENCE_MODE] + [--rdb-snapshot-period=RDB_SNAPSHOT_PERIOD] + [--rdb-snapshot-start-time=RDB_SNAPSHOT_START_TIME] [--read-replicas-mode=READ_REPLICAS_MODE] [--redis-config=KEY=VALUE] [--redis-version=VERSION] [--replica-count=REPLICA_COUNT] [--reserved-ip-range=RESERVED_IP_RANGE] [--size=SIZE; default=1] @@ -105,6 +108,32 @@ FLAGS will be connected. If left unspecified, the default network will be used. + --persistence-mode=PERSISTENCE_MODE + Operation mode for automated persistence. PERSISTENCE_MODE must be one + of: + + disabled + RDB mode is disabled + rdb + Automatic RDB persistence + + --rdb-snapshot-period=RDB_SNAPSHOT_PERIOD + Attempted period between RDB snapshots. RDB_SNAPSHOT_PERIOD must be one + of: + + 12h + 12 hours + 1h + 1 hour + 24h + 24 hours + 6h + 6 hours + + --rdb-snapshot-start-time=RDB_SNAPSHOT_START_TIME + Date and time of the first snapshot in the ISO 1801 format, and + alignment time for future snapshots. For example, 2022-11-02T03:00:00Z. + --read-replicas-mode=READ_REPLICAS_MODE Read replicas mode used by the instance. Only works against standard tier instances with 5GB and above provisioned capacity. diff --git a/gcloud/redis/instances/update b/gcloud/redis/instances/update index 39f6382fa..b0c150476 100644 --- a/gcloud/redis/instances/update +++ b/gcloud/redis/instances/update @@ -4,6 +4,9 @@ NAME SYNOPSIS gcloud redis instances update (INSTANCE : --region=REGION) [--async] [--display-name=DISPLAY_NAME] [--enable-auth] + [--persistence-mode=PERSISTENCE_MODE] + [--rdb-snapshot-period=RDB_SNAPSHOT_PERIOD] + [--rdb-snapshot-start-time=RDB_SNAPSHOT_START_TIME] [--read-replicas-mode=READ_REPLICAS_MODE] [--remove-redis-config=[KEY,...]] [--replica-count=REPLICA_COUNT] [--secondary-ip-range=SECONDARY_IP_RANGE] [--size=SIZE] @@ -73,6 +76,32 @@ FLAGS --enable-auth Enables Redis AUTH for the instance. + --persistence-mode=PERSISTENCE_MODE + Operation mode for automated persistence. PERSISTENCE_MODE must be one + of: + + disabled + RDB mode is disabled + rdb + Automatic RDB persistence + + --rdb-snapshot-period=RDB_SNAPSHOT_PERIOD + The attempted period between RDB snapshots. RDB_SNAPSHOT_PERIOD must be + one of: + + 12h + 12 hours + 1h + 1 hour + 24h + 24 hours + 6h + 6 hours + + --rdb-snapshot-start-time=RDB_SNAPSHOT_START_TIME + Date and time of the first snapshot in the ISO 1801 format, and + alignment time for future snapshots. For example, 2022-11-02T03:00:00Z. + --read-replicas-mode=READ_REPLICAS_MODE Read replicas mode used by the instance. Only works against standard tier instances with 5GB and above provisioned capacity and Redis diff --git a/gcloud/sql/instances/create b/gcloud/sql/instances/create index 0e4e15f3b..b5b7b9c5c 100644 --- a/gcloud/sql/instances/create +++ b/gcloud/sql/instances/create @@ -281,14 +281,12 @@ FLAGS implies that complexity check is not enabled. --[no-]password-policy-disallow-username-substring - Disallow username as a part of the password. This flag is available - only for PostgreSQL. Use --password-policy-disallow-username-substring - to enable and --no-password-policy-disallow-username-substring to - disable. + Disallow username as a part of the password. Use + --password-policy-disallow-username-substring to enable and + --no-password-policy-disallow-username-substring to disable. --password-policy-min-length=PASSWORD_POLICY_MIN_LENGTH - Minimum number of characters allowed in the password. This flag is - available only for PostgreSQL. + Minimum number of characters allowed in the password. --password-policy-password-change-interval=PASSWORD_POLICY_PASSWORD_CHANGE_INTERVAL Minimum interval after which the password can be changed, for example, @@ -298,7 +296,7 @@ FLAGS --password-policy-reuse-interval=PASSWORD_POLICY_REUSE_INTERVAL Number of previous passwords that cannot be reused. The valid range is - 0 to 100. This flag is available only for PostgreSQL. + 0 to 100. --replica-type=REPLICA_TYPE The type of replica to create. REPLICA_TYPE must be one of: READ, diff --git a/gcloud/sql/instances/patch b/gcloud/sql/instances/patch index 4d213aa46..7b1310648 100644 --- a/gcloud/sql/instances/patch +++ b/gcloud/sql/instances/patch @@ -241,14 +241,12 @@ FLAGS implies that complexity check is not enabled. --[no-]password-policy-disallow-username-substring - Disallow username as a part of the password. This flag is available - only for PostgreSQL. Use --password-policy-disallow-username-substring - to enable and --no-password-policy-disallow-username-substring to - disable. + Disallow username as a part of the password. Use + --password-policy-disallow-username-substring to enable and + --no-password-policy-disallow-username-substring to disable. --password-policy-min-length=PASSWORD_POLICY_MIN_LENGTH - Minimum number of characters allowed in the password. This flag is - available only for PostgreSQL. + Minimum number of characters allowed in the password. --password-policy-password-change-interval=PASSWORD_POLICY_PASSWORD_CHANGE_INTERVAL Minimum interval after which the password can be changed, for example, @@ -258,7 +256,7 @@ FLAGS --password-policy-reuse-interval=PASSWORD_POLICY_REUSE_INTERVAL Number of previous passwords that cannot be reused. The valid range is - 0 to 100. This flag is available only for PostgreSQL. + 0 to 100. --pricing-plan=PRICING_PLAN, -p PRICING_PLAN First Generation instances only. The pricing plan for this instance. diff --git a/gcloud/sql/users/create b/gcloud/sql/users/create index f9e2cdd82..65e9a5a9e 100644 --- a/gcloud/sql/users/create +++ b/gcloud/sql/users/create @@ -6,6 +6,7 @@ SYNOPSIS [--host=HOST] [--password=PASSWORD] [--password-policy-allowed-failed-attempts=PASSWORD_POLICY_ALLOWED_FAILED_ATTEMPTS] [--[no-]password-policy-enable-failed-attempts-check] + [--[no-]password-policy-enable-password-verification] [--password-policy-password-expiration-duration=PASSWORD_POLICY_PASSWORD_EXPIRATION_DURATION] [--type=TYPE] [GCLOUD_WIDE_FLAG ...] @@ -40,18 +41,24 @@ OPTIONAL FLAGS --password-policy-allowed-failed-attempts=PASSWORD_POLICY_ALLOWED_FAILED_ATTEMPTS Number of failed login attempts allowed before a user is locked out. - This flag is currently not available. + This flag is available only for MySQL. --[no-]password-policy-enable-failed-attempts-check Enables the failed login attempts check if set to true. This flag is - currently not available. Use + available only for MySQL. Use --password-policy-enable-failed-attempts-check to enable and --no-password-policy-enable-failed-attempts-check to disable. + --[no-]password-policy-enable-password-verification + The current password must be specified when altering the password. This + flag is available only for MySQL. Use + --password-policy-enable-password-verification to enable and + --no-password-policy-enable-password-verification to disable. + --password-policy-password-expiration-duration=PASSWORD_POLICY_PASSWORD_EXPIRATION_DURATION - Expiration duration after a password is updated, for example, 2m for 2 - minutes. See gcloud topic datetimes for information on duration - formats. This flag is currently not available. + Expiration duration after a password is updated, for example, 2d for 2 + days. See gcloud topic datetimes for information on duration formats. + This flag is available only for MySQL. --type=TYPE Cloud SQL user's type. It determines the method to authenticate the diff --git a/gcloud/sql/users/set-password b/gcloud/sql/users/set-password index 0b304e930..da2039d0f 100644 --- a/gcloud/sql/users/set-password +++ b/gcloud/sql/users/set-password @@ -4,8 +4,8 @@ NAME SYNOPSIS gcloud sql users set-password USERNAME --instance=INSTANCE, -i INSTANCE - [--async] [--host=HOST] [--password=PASSWORD | --prompt-for-password] - [GCLOUD_WIDE_FLAG ...] + [--async] [--host=HOST] [--discard-dual-password | --retain-password] + [--password=PASSWORD | --prompt-for-password] [GCLOUD_WIDE_FLAG ...] DESCRIPTION Changes a user's password in a given instance with specified username and @@ -33,6 +33,16 @@ OPTIONAL FLAGS help on how to do so, read: https://cloud.google.com/sql/docs/mysql/configure-ip + At most one of these can be specified: + + --discard-dual-password + Discard the user's secondary password. Cannot set password and set + this flag. This flag is only available for MySQL 8.0. + + --retain-password + Retain the old password when changing to the new password. Must set + password with this flag. This flag is only available for MySQL 8.0. + At most one of these can be specified: --password=PASSWORD diff --git a/gcloud/sql/users/set-password-policy b/gcloud/sql/users/set-password-policy index c95a9efbb..9e9444264 100644 --- a/gcloud/sql/users/set-password-policy +++ b/gcloud/sql/users/set-password-policy @@ -7,6 +7,7 @@ SYNOPSIS INSTANCE [--async] [--clear-password-policy] [--host=HOST] [--password-policy-allowed-failed-attempts=PASSWORD_POLICY_ALLOWED_FAILED_ATTEMPTS] [--[no-]password-policy-enable-failed-attempts-check] + [--[no-]password-policy-enable-password-verification] [--password-policy-password-expiration-duration=PASSWORD_POLICY_PASSWORD_EXPIRATION_DURATION] [GCLOUD_WIDE_FLAG ...] @@ -56,18 +57,24 @@ OPTIONAL FLAGS --password-policy-allowed-failed-attempts=PASSWORD_POLICY_ALLOWED_FAILED_ATTEMPTS Number of failed login attempts allowed before a user is locked out. - This flag is currently not available. + This flag is available only for MySQL. --[no-]password-policy-enable-failed-attempts-check Enables the failed login attempts check if set to true. This flag is - currently not available. Use + available only for MySQL. Use --password-policy-enable-failed-attempts-check to enable and --no-password-policy-enable-failed-attempts-check to disable. + --[no-]password-policy-enable-password-verification + The current password must be specified when altering the password. This + flag is available only for MySQL. Use + --password-policy-enable-password-verification to enable and + --no-password-policy-enable-password-verification to disable. + --password-policy-password-expiration-duration=PASSWORD_POLICY_PASSWORD_EXPIRATION_DURATION - Expiration duration after a password is updated, for example, 2m for 2 - minutes. See gcloud topic datetimes for information on duration - formats. This flag is currently not available. + Expiration duration after a password is updated, for example, 2d for 2 + days. See gcloud topic datetimes for information on duration formats. + This flag is available only for MySQL. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/transcoder/jobs/create b/gcloud/transcoder/jobs/create index 43a64de44..5acfab11a 100644 --- a/gcloud/transcoder/jobs/create +++ b/gcloud/transcoder/jobs/create @@ -2,7 +2,8 @@ NAME gcloud transcoder jobs create - create Transcoder jobs SYNOPSIS - gcloud transcoder jobs create [--input-uri=INPUT_URI] [--location=LOCATION] + gcloud transcoder jobs create [--input-uri=INPUT_URI] + [--labels=[KEY=VALUE,...]] [--location=LOCATION] [--output-uri=OUTPUT_URI] [--file=FILE | --json=JSON | --template-id=TEMPLATE_ID] [GCLOUD_WIDE_FLAG ...] @@ -34,11 +35,24 @@ EXAMPLES $ gcloud transcoder jobs create --location=us-central1 \ --file="config.json" + To Create a transcoder job with labels: + + $ gcloud transcoder jobs create --location=us-central1 \ + --file="config.json" --labels=key=value + FLAGS --input-uri=INPUT_URI Google Cloud Storage URI. If inputs URI exists in job config, this value will be ignored + --labels=[KEY=VALUE,...] + List of label KEY=VALUE pairs to add. + + Keys must start with a lowercase character and contain only hyphens + (-), underscores (_), lowercase characters, and numbers. Values must + contain only hyphens (-), underscores (_), lowercase characters, and + numbers. + Location resource - Transcoder location 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: diff --git a/gcloud/transcoder/templates/create b/gcloud/transcoder/templates/create index 95866d63c..e4b93749e 100644 --- a/gcloud/transcoder/templates/create +++ b/gcloud/transcoder/templates/create @@ -3,7 +3,8 @@ NAME SYNOPSIS gcloud transcoder templates create (TEMPLATE_ID : --location=LOCATION) - (--file=FILE | --json=JSON) [GCLOUD_WIDE_FLAG ...] + (--file=FILE | --json=JSON) [--labels=[KEY=VALUE,...]] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION Create Transcoder job templates. @@ -19,6 +20,11 @@ EXAMPLES $ gcloud transcoder templates create TEMPLATE_ID \ --file="config.json" --location=us-central1 + To create a job template with json format configuration and labels + + $ gcloud transcoder templates create TEMPLATE_ID \ + --file="config.json" --location=us-central1 --labels=key=value + POSITIONAL ARGUMENTS JobTemplate resource - Transcoder job template id The arguments in this group can be used to specify the attributes of this resource. (NOTE) Some @@ -55,6 +61,15 @@ REQUIRED FLAGS --json=JSON Job template in json format. +OPTIONAL FLAGS + --labels=[KEY=VALUE,...] + List of label KEY=VALUE pairs to add. + + Keys must start with a lowercase character and contain only hyphens + (-), underscores (_), lowercase characters, and numbers. Values must + contain only hyphens (-), underscores (_), lowercase characters, and + numbers. + 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/transfer/agents/install b/gcloud/transfer/agents/install index d14783629..1bdcf00b6 100644 --- a/gcloud/transfer/agents/install +++ b/gcloud/transfer/agents/install @@ -7,7 +7,7 @@ SYNOPSIS [--logs-directory=LOGS_DIRECTORY; default="/tmp"] [--memlock-limit=MEMLOCK_LIMIT; default=64000000] [--mount-directories=[MOUNT-DIRECTORIES,...]] [--proxy=PROXY] - [GCLOUD_WIDE_FLAG ...] + [--s3-compatible-mode] [GCLOUD_WIDE_FLAG ...] DESCRIPTION Install Transfer Service agents to enable you to transfer data to or from @@ -83,6 +83,11 @@ OPTIONAL FLAGS double-wrapping requests in TLS encryption. Double-wrapped requests prevent the proxy server from sending valid outbound requests. + --s3-compatible-mode + Allow the agent to work with S3-compatible sources. This flag blocks + the agents ability to work with other source types (e.g. POSIX + filesystems). + GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format,