From b589c4c4ade3f2150cdb3f2ef675489393e2ca10 Mon Sep 17 00:00:00 2001 From: Automated Date: Wed, 16 Apr 2025 10:41:40 +0000 Subject: [PATCH] gcloud: Wed Apr 16 10:41:40 UTC 2025 --- gcloud/_version | 10 +- gcloud/alloydb/clusters/export | 2 +- gcloud/alloydb/clusters/import | 2 +- gcloud/alpha/alloydb/clusters/export | 2 +- gcloud/alpha/alloydb/clusters/import | 2 +- .../create/macos | 6 + .../alpha/backup-dr/management-servers/create | 20 +- gcloud/alpha/bigtable/help | 3 + gcloud/alpha/bigtable/instances/tables/create | 32 ++- gcloud/alpha/bigtable/instances/tables/update | 46 ++- .../alpha/bigtable/materialized-views/create | 80 ++++++ .../alpha/bigtable/materialized-views/delete | 67 +++++ .../bigtable/materialized-views/describe | 67 +++++ gcloud/alpha/bigtable/materialized-views/help | 43 +++ gcloud/alpha/bigtable/materialized-views/list | 87 ++++++ .../alpha/bigtable/materialized-views/update | 77 +++++ gcloud/alpha/bigtable/tables/create | 32 ++- gcloud/alpha/bigtable/tables/update | 46 ++- gcloud/alpha/compute/commitments/create | 22 +- .../compute/commitments/update-reservations | 42 ++- gcloud/alpha/compute/config-ssh | 4 +- gcloud/alpha/compute/disks/create | 4 +- gcloud/alpha/compute/images/create | 4 +- gcloud/alpha/compute/images/list | 3 +- .../managed/resize-requests/create | 15 +- .../application-awareness/get-config | 40 +++ .../interconnects/application-awareness/help | 31 ++ gcloud/alpha/compute/interconnects/help | 4 + .../network-firewall-policies/rules/create | 18 +- .../network-firewall-policies/rules/update | 18 +- gcloud/alpha/compute/networks/peerings/help | 3 + .../compute/networks/peerings/request-delete | 53 ++++ gcloud/alpha/compute/reservations/create | 24 +- gcloud/alpha/compute/reservations/update | 25 +- gcloud/alpha/compute/routers/nats/create | 12 +- gcloud/alpha/compute/routers/nats/update | 12 +- .../compute/service-attachments/describe | 8 +- .../compute/tpus/queued-resources/create | 5 +- gcloud/alpha/compute/tpus/tpu-vm/create | 14 +- .../ai/recommender/accelerators/list | 38 ++- .../model-and-server-combinations/list | 36 ++- .../ai/recommender/model-server-versions/list | 36 ++- .../ai/recommender/model-servers/list | 35 ++- .../container/ai/recommender/models/list | 36 ++- .../backup-restore/backup-channels/create | 104 +++++++ .../backup-restore/backup-channels/delete | 87 ++++++ .../backup-restore/backup-channels/describe | 76 +++++ .../backup-restore/backup-channels/help | 42 +++ .../backup-restore/backup-channels/list | 100 +++++++ .../backup-restore/backup-channels/update | 123 ++++++++ .../backup-plan-bindings/describe | 90 ++++++ .../backup-restore/backup-plan-bindings/help | 33 +++ .../backup-restore/backup-plan-bindings/list | 115 ++++++++ gcloud/alpha/container/backup-restore/help | 12 + .../backup-restore/restore-channels/create | 104 +++++++ .../backup-restore/restore-channels/delete | 87 ++++++ .../backup-restore/restore-channels/describe | 76 +++++ .../backup-restore/restore-channels/help | 42 +++ .../backup-restore/restore-channels/list | 100 +++++++ .../backup-restore/restore-channels/update | 123 ++++++++ .../restore-plan-bindings/describe | 90 ++++++ .../backup-restore/restore-plan-bindings/help | 33 +++ .../backup-restore/restore-plan-bindings/list | 115 ++++++++ gcloud/alpha/container/clusters/create | 39 ++- gcloud/alpha/container/clusters/create-auto | 50 ++-- .../alpha/container/clusters/get-upgrade-info | 4 +- gcloud/alpha/container/clusters/update | 39 ++- gcloud/alpha/container/node-pools/create | 29 +- .../container/node-pools/get-upgrade-info | 15 +- gcloud/alpha/container/node-pools/help | 5 +- gcloud/alpha/dataproc/clusters/create | 22 +- gcloud/alpha/dataproc/clusters/update | 33 +-- .../account-connectors/create | 6 +- .../account-connectors/update | 12 +- .../edge-cloud/container/clusters/create | 4 + .../edge-cloud/container/clusters/update | 5 + .../firestore/databases/connection-string | 56 ++++ gcloud/alpha/firestore/databases/create | 15 +- gcloud/alpha/firestore/databases/help | 4 + gcloud/alpha/firestore/help | 3 + .../alpha/firestore/indexes/composite/create | 16 +- gcloud/alpha/firestore/user-creds/create | 46 +++ gcloud/alpha/firestore/user-creds/delete | 46 +++ gcloud/alpha/firestore/user-creds/describe | 46 +++ gcloud/alpha/firestore/user-creds/disable | 46 +++ gcloud/alpha/firestore/user-creds/enable | 46 +++ gcloud/alpha/firestore/user-creds/help | 47 +++ gcloud/alpha/firestore/user-creds/list | 70 +++++ .../alpha/firestore/user-creds/reset-password | 47 +++ .../create-cred-config | 9 +- gcloud/alpha/logging/write | 20 +- gcloud/alpha/managed-kafka/clusters/create | 9 +- gcloud/alpha/managed-kafka/clusters/update | 11 +- .../alpha/migration/vms/target-projects/help | 4 +- .../alpha/migration/vms/target-projects/list | 4 +- .../network-security/server-tls-policies/list | 24 +- gcloud/alpha/network-services/help | 3 + .../alpha/network-services/operations/cancel | 66 +++++ .../network-services/operations/describe | 66 +++++ gcloud/alpha/network-services/operations/help | 36 +++ gcloud/alpha/network-services/operations/list | 87 ++++++ gcloud/alpha/network-services/operations/wait | 65 +++++ gcloud/alpha/scc/findings/list-marks | 64 ++--- gcloud/alpha/scc/findings/update | 67 ++--- gcloud/alpha/scc/findings/update-marks | 64 ++--- gcloud/alpha/sql/backups/restore | 9 - gcloud/alpha/sql/instances/clone | 12 +- gcloud/artifacts/go/auth | 53 ++++ gcloud/artifacts/go/help | 3 + .../create/macos | 11 +- gcloud/backup-dr/management-servers/create | 20 +- gcloud/beta/alloydb/clusters/export | 2 +- gcloud/beta/alloydb/clusters/import | 2 +- .../create/macos | 11 +- .../beta/backup-dr/management-servers/create | 20 +- gcloud/beta/bigtable/help | 3 + gcloud/beta/bigtable/instances/tables/create | 32 ++- gcloud/beta/bigtable/instances/tables/update | 46 ++- .../beta/bigtable/materialized-views/create | 78 +++++ .../beta/bigtable/materialized-views/delete | 65 +++++ .../beta/bigtable/materialized-views/describe | 65 +++++ gcloud/beta/bigtable/materialized-views/help | 41 +++ gcloud/beta/bigtable/materialized-views/list | 85 ++++++ .../beta/bigtable/materialized-views/update | 75 +++++ gcloud/beta/bigtable/tables/create | 32 ++- gcloud/beta/bigtable/tables/update | 46 ++- gcloud/beta/compute/commitments/create | 36 ++- .../compute/commitments/update-reservations | 42 ++- gcloud/beta/compute/config-ssh | 4 +- gcloud/beta/compute/images/list | 3 +- .../managed/resize-requests/create | 23 +- .../network-firewall-policies/rules/create | 2 +- .../network-firewall-policies/rules/update | 2 +- gcloud/beta/compute/reservations/create | 19 +- gcloud/beta/compute/reservations/update | 25 +- gcloud/beta/compute/routers/nats/create | 12 +- gcloud/beta/compute/routers/nats/update | 12 +- .../backup-restore/backup-channels/create | 102 +++++++ .../backup-restore/backup-channels/delete | 85 ++++++ .../backup-restore/backup-channels/describe | 74 +++++ .../backup-restore/backup-channels/help | 40 +++ .../backup-restore/backup-channels/list | 98 +++++++ .../backup-restore/backup-channels/update | 121 ++++++++ .../backup-plan-bindings/describe | 88 ++++++ .../backup-restore/backup-plan-bindings/help | 31 ++ .../backup-restore/backup-plan-bindings/list | 113 ++++++++ gcloud/beta/container/backup-restore/help | 12 + .../backup-restore/restore-channels/create | 102 +++++++ .../backup-restore/restore-channels/delete | 85 ++++++ .../backup-restore/restore-channels/describe | 74 +++++ .../backup-restore/restore-channels/help | 40 +++ .../backup-restore/restore-channels/list | 98 +++++++ .../backup-restore/restore-channels/update | 121 ++++++++ .../restore-plan-bindings/describe | 89 ++++++ .../backup-restore/restore-plan-bindings/help | 31 ++ .../backup-restore/restore-plan-bindings/list | 113 ++++++++ gcloud/beta/container/clusters/create | 39 ++- gcloud/beta/container/clusters/create-auto | 50 ++-- .../beta/container/clusters/get-upgrade-info | 6 +- gcloud/beta/container/clusters/update | 39 ++- gcloud/beta/container/node-pools/create | 29 +- .../container/node-pools/get-upgrade-info | 17 +- gcloud/beta/container/node-pools/help | 4 +- gcloud/beta/dataflow/flex-template/run | 2 +- gcloud/beta/dataflow/jobs/run | 5 + gcloud/beta/dataproc/clusters/create | 22 +- gcloud/beta/dataproc/clusters/update | 33 +-- gcloud/beta/filestore/instances/create | 58 +++- gcloud/beta/filestore/instances/update | 2 +- .../firestore/databases/connection-string | 54 ++++ gcloud/beta/firestore/databases/create | 15 +- gcloud/beta/firestore/databases/help | 4 + gcloud/beta/firestore/help | 3 + .../beta/firestore/indexes/composite/create | 16 +- gcloud/beta/firestore/user-creds/create | 44 +++ gcloud/beta/firestore/user-creds/delete | 44 +++ gcloud/beta/firestore/user-creds/describe | 44 +++ gcloud/beta/firestore/user-creds/disable | 44 +++ gcloud/beta/firestore/user-creds/enable | 44 +++ gcloud/beta/firestore/user-creds/help | 45 +++ gcloud/beta/firestore/user-creds/list | 68 +++++ .../beta/firestore/user-creds/reset-password | 45 +++ .../create-cred-config | 9 +- gcloud/beta/logging/write | 20 +- gcloud/beta/managed-kafka/clusters/create | 9 +- gcloud/beta/managed-kafka/clusters/update | 11 +- .../network-security/server-tls-policies/list | 19 +- gcloud/beta/scc/findings/list-marks | 64 ++--- gcloud/beta/scc/findings/update | 67 ++--- gcloud/beta/scc/findings/update-marks | 64 ++--- gcloud/beta/sql/backups/restore | 9 - gcloud/bigtable/help | 3 + gcloud/bigtable/instances/tables/create | 32 ++- gcloud/bigtable/instances/tables/update | 46 ++- gcloud/bigtable/materialized-views/create | 77 +++++ gcloud/bigtable/materialized-views/delete | 64 +++++ gcloud/bigtable/materialized-views/describe | 64 +++++ gcloud/bigtable/materialized-views/help | 39 +++ gcloud/bigtable/materialized-views/list | 83 ++++++ gcloud/bigtable/materialized-views/update | 74 +++++ gcloud/bigtable/tables/create | 32 ++- gcloud/bigtable/tables/update | 46 ++- gcloud/compute/commitments/create | 36 ++- gcloud/compute/config-ssh | 4 +- gcloud/compute/images/list | 3 +- .../managed/resize-requests/create | 5 +- gcloud/compute/reservations/create | 19 +- gcloud/compute/reservations/update | 6 +- gcloud/compute/routers/nats/create | 68 +++-- gcloud/compute/routers/nats/update | 71 +++-- gcloud/compute/tpus/queued-resources/create | 2 +- gcloud/container/clusters/create | 5 + gcloud/container/clusters/get-upgrade-info | 56 ++++ gcloud/container/clusters/help | 5 + gcloud/container/node-pools/create | 36 ++- gcloud/container/node-pools/get-upgrade-info | 61 ++++ gcloud/container/node-pools/help | 3 + .../database-migration/migration-jobs/create | 43 +++ .../private-connections/create | 5 +- gcloud/dataflow/flex-template/run | 2 +- gcloud/dataflow/jobs/run | 5 + gcloud/dataproc/clusters/create | 22 +- gcloud/dataproc/clusters/update | 33 +-- .../container/clusters/node-pools/update | 20 +- gcloud/edge-cloud/container/clusters/update | 12 + gcloud/firestore/databases/create | 15 +- gcloud/firestore/indexes/composite/create | 16 +- gcloud/gemini/code-repository-indexes/create | 6 - gcloud/gemini/code-repository-indexes/delete | 6 - .../repository-groups/create | 10 +- .../repository-groups/delete | 6 - .../repository-groups/update | 18 +- gcloud/gemini/code-repository-indexes/update | 6 - gcloud/gemini/code-tools-settings/create | 141 +++++++++ gcloud/gemini/code-tools-settings/delete | 80 ++++++ gcloud/gemini/code-tools-settings/describe | 58 ++++ gcloud/gemini/code-tools-settings/help | 37 +++ gcloud/gemini/code-tools-settings/list | 78 +++++ .../setting-bindings/create | 128 +++++++++ .../setting-bindings/delete | 89 ++++++ .../setting-bindings/describe | 69 +++++ .../code-tools-settings/setting-bindings/help | 33 +++ .../code-tools-settings/setting-bindings/list | 93 ++++++ .../setting-bindings/update | 165 +++++++++++ gcloud/gemini/code-tools-settings/update | 270 ++++++++++++++++++ .../data-sharing-with-google-settings/create | 105 +++++++ .../data-sharing-with-google-settings/delete | 77 +++++ .../describe | 61 ++++ .../data-sharing-with-google-settings/help | 39 +++ .../data-sharing-with-google-settings/list | 80 ++++++ .../setting-bindings/create | 130 +++++++++ .../setting-bindings/delete | 91 ++++++ .../setting-bindings/describe | 70 +++++ .../setting-bindings/help | 33 +++ .../setting-bindings/list | 95 ++++++ .../setting-bindings/update | 166 +++++++++++ .../data-sharing-with-google-settings/update | 144 ++++++++++ .../gemini-gcp-enablement-settings/create | 105 +++++++ .../gemini-gcp-enablement-settings/delete | 77 +++++ .../gemini-gcp-enablement-settings/describe | 61 ++++ .../gemini-gcp-enablement-settings/help | 39 +++ .../gemini-gcp-enablement-settings/list | 80 ++++++ .../setting-bindings/create | 130 +++++++++ .../setting-bindings/delete | 91 ++++++ .../setting-bindings/describe | 70 +++++ .../setting-bindings/help | 33 +++ .../setting-bindings/list | 95 ++++++ .../setting-bindings/update | 166 +++++++++++ .../gemini-gcp-enablement-settings/update | 144 ++++++++++ gcloud/gemini/help | 15 + gcloud/gemini/logging-settings/create | 106 +++++++ gcloud/gemini/logging-settings/delete | 75 +++++ gcloud/gemini/logging-settings/describe | 58 ++++ gcloud/gemini/logging-settings/help | 37 +++ gcloud/gemini/logging-settings/list | 78 +++++ .../logging-settings/setting-bindings/create | 128 +++++++++ .../logging-settings/setting-bindings/delete | 89 ++++++ .../setting-bindings/describe | 69 +++++ .../logging-settings/setting-bindings/help | 33 +++ .../logging-settings/setting-bindings/list | 92 ++++++ .../logging-settings/setting-bindings/update | 164 +++++++++++ gcloud/gemini/logging-settings/update | 145 ++++++++++ gcloud/gemini/release-channel-settings/create | 109 +++++++ gcloud/gemini/release-channel-settings/delete | 76 +++++ .../gemini/release-channel-settings/describe | 59 ++++ gcloud/gemini/release-channel-settings/help | 39 +++ gcloud/gemini/release-channel-settings/list | 78 +++++ .../setting-bindings/create | 129 +++++++++ .../setting-bindings/delete | 90 ++++++ .../setting-bindings/describe | 70 +++++ .../setting-bindings/help | 33 +++ .../setting-bindings/list | 95 ++++++ .../setting-bindings/update | 165 +++++++++++ gcloud/gemini/release-channel-settings/update | 146 ++++++++++ .../create-cred-config | 9 +- gcloud/logging/write | 20 +- gcloud/managed-kafka/clusters/create | 9 +- gcloud/managed-kafka/clusters/update | 11 +- gcloud/migration/vms/help | 3 + gcloud/migration/vms/target-projects/help | 29 ++ gcloud/migration/vms/target-projects/list | 67 +++++ .../internal-ranges/create | 9 +- .../network-security/server-tls-policies/list | 18 +- .../autonomous-databases/create | 72 +++-- .../oracle-database/autonomous-databases/help | 12 + .../autonomous-databases/restart | 69 +++++ .../autonomous-databases/start | 69 +++++ .../oracle-database/autonomous-databases/stop | 69 +++++ .../autonomous-databases/switchover | 97 +++++++ gcloud/scc/findings/list-marks | 64 ++--- gcloud/scc/findings/update | 67 ++--- gcloud/scc/findings/update-marks | 64 ++--- gcloud/sql/backups/restore | 9 - gcloud/transfer/jobs/create | 10 +- gcloud/transfer/jobs/update | 17 +- gcloud/workbench/instances/create | 7 +- 316 files changed, 13928 insertions(+), 1163 deletions(-) create mode 100644 gcloud/alpha/bigtable/materialized-views/create create mode 100644 gcloud/alpha/bigtable/materialized-views/delete create mode 100644 gcloud/alpha/bigtable/materialized-views/describe create mode 100644 gcloud/alpha/bigtable/materialized-views/help create mode 100644 gcloud/alpha/bigtable/materialized-views/list create mode 100644 gcloud/alpha/bigtable/materialized-views/update create mode 100644 gcloud/alpha/compute/interconnects/application-awareness/get-config create mode 100644 gcloud/alpha/compute/interconnects/application-awareness/help create mode 100644 gcloud/alpha/compute/networks/peerings/request-delete create mode 100644 gcloud/alpha/container/backup-restore/backup-channels/create create mode 100644 gcloud/alpha/container/backup-restore/backup-channels/delete create mode 100644 gcloud/alpha/container/backup-restore/backup-channels/describe create mode 100644 gcloud/alpha/container/backup-restore/backup-channels/help create mode 100644 gcloud/alpha/container/backup-restore/backup-channels/list create mode 100644 gcloud/alpha/container/backup-restore/backup-channels/update create mode 100644 gcloud/alpha/container/backup-restore/backup-plan-bindings/describe create mode 100644 gcloud/alpha/container/backup-restore/backup-plan-bindings/help create mode 100644 gcloud/alpha/container/backup-restore/backup-plan-bindings/list create mode 100644 gcloud/alpha/container/backup-restore/restore-channels/create create mode 100644 gcloud/alpha/container/backup-restore/restore-channels/delete create mode 100644 gcloud/alpha/container/backup-restore/restore-channels/describe create mode 100644 gcloud/alpha/container/backup-restore/restore-channels/help create mode 100644 gcloud/alpha/container/backup-restore/restore-channels/list create mode 100644 gcloud/alpha/container/backup-restore/restore-channels/update create mode 100644 gcloud/alpha/container/backup-restore/restore-plan-bindings/describe create mode 100644 gcloud/alpha/container/backup-restore/restore-plan-bindings/help create mode 100644 gcloud/alpha/container/backup-restore/restore-plan-bindings/list create mode 100644 gcloud/alpha/firestore/databases/connection-string create mode 100644 gcloud/alpha/firestore/user-creds/create create mode 100644 gcloud/alpha/firestore/user-creds/delete create mode 100644 gcloud/alpha/firestore/user-creds/describe create mode 100644 gcloud/alpha/firestore/user-creds/disable create mode 100644 gcloud/alpha/firestore/user-creds/enable create mode 100644 gcloud/alpha/firestore/user-creds/help create mode 100644 gcloud/alpha/firestore/user-creds/list create mode 100644 gcloud/alpha/firestore/user-creds/reset-password create mode 100644 gcloud/alpha/network-services/operations/cancel create mode 100644 gcloud/alpha/network-services/operations/describe create mode 100644 gcloud/alpha/network-services/operations/help create mode 100644 gcloud/alpha/network-services/operations/list create mode 100644 gcloud/alpha/network-services/operations/wait create mode 100644 gcloud/artifacts/go/auth create mode 100644 gcloud/beta/bigtable/materialized-views/create create mode 100644 gcloud/beta/bigtable/materialized-views/delete create mode 100644 gcloud/beta/bigtable/materialized-views/describe create mode 100644 gcloud/beta/bigtable/materialized-views/help create mode 100644 gcloud/beta/bigtable/materialized-views/list create mode 100644 gcloud/beta/bigtable/materialized-views/update create mode 100644 gcloud/beta/container/backup-restore/backup-channels/create create mode 100644 gcloud/beta/container/backup-restore/backup-channels/delete create mode 100644 gcloud/beta/container/backup-restore/backup-channels/describe create mode 100644 gcloud/beta/container/backup-restore/backup-channels/help create mode 100644 gcloud/beta/container/backup-restore/backup-channels/list create mode 100644 gcloud/beta/container/backup-restore/backup-channels/update create mode 100644 gcloud/beta/container/backup-restore/backup-plan-bindings/describe create mode 100644 gcloud/beta/container/backup-restore/backup-plan-bindings/help create mode 100644 gcloud/beta/container/backup-restore/backup-plan-bindings/list create mode 100644 gcloud/beta/container/backup-restore/restore-channels/create create mode 100644 gcloud/beta/container/backup-restore/restore-channels/delete create mode 100644 gcloud/beta/container/backup-restore/restore-channels/describe create mode 100644 gcloud/beta/container/backup-restore/restore-channels/help create mode 100644 gcloud/beta/container/backup-restore/restore-channels/list create mode 100644 gcloud/beta/container/backup-restore/restore-channels/update create mode 100644 gcloud/beta/container/backup-restore/restore-plan-bindings/describe create mode 100644 gcloud/beta/container/backup-restore/restore-plan-bindings/help create mode 100644 gcloud/beta/container/backup-restore/restore-plan-bindings/list create mode 100644 gcloud/beta/firestore/databases/connection-string create mode 100644 gcloud/beta/firestore/user-creds/create create mode 100644 gcloud/beta/firestore/user-creds/delete create mode 100644 gcloud/beta/firestore/user-creds/describe create mode 100644 gcloud/beta/firestore/user-creds/disable create mode 100644 gcloud/beta/firestore/user-creds/enable create mode 100644 gcloud/beta/firestore/user-creds/help create mode 100644 gcloud/beta/firestore/user-creds/list create mode 100644 gcloud/beta/firestore/user-creds/reset-password create mode 100644 gcloud/bigtable/materialized-views/create create mode 100644 gcloud/bigtable/materialized-views/delete create mode 100644 gcloud/bigtable/materialized-views/describe create mode 100644 gcloud/bigtable/materialized-views/help create mode 100644 gcloud/bigtable/materialized-views/list create mode 100644 gcloud/bigtable/materialized-views/update create mode 100644 gcloud/container/clusters/get-upgrade-info create mode 100644 gcloud/container/node-pools/get-upgrade-info create mode 100644 gcloud/gemini/code-tools-settings/create create mode 100644 gcloud/gemini/code-tools-settings/delete create mode 100644 gcloud/gemini/code-tools-settings/describe create mode 100644 gcloud/gemini/code-tools-settings/help create mode 100644 gcloud/gemini/code-tools-settings/list create mode 100644 gcloud/gemini/code-tools-settings/setting-bindings/create create mode 100644 gcloud/gemini/code-tools-settings/setting-bindings/delete create mode 100644 gcloud/gemini/code-tools-settings/setting-bindings/describe create mode 100644 gcloud/gemini/code-tools-settings/setting-bindings/help create mode 100644 gcloud/gemini/code-tools-settings/setting-bindings/list create mode 100644 gcloud/gemini/code-tools-settings/setting-bindings/update create mode 100644 gcloud/gemini/code-tools-settings/update create mode 100644 gcloud/gemini/data-sharing-with-google-settings/create create mode 100644 gcloud/gemini/data-sharing-with-google-settings/delete create mode 100644 gcloud/gemini/data-sharing-with-google-settings/describe create mode 100644 gcloud/gemini/data-sharing-with-google-settings/help create mode 100644 gcloud/gemini/data-sharing-with-google-settings/list create mode 100644 gcloud/gemini/data-sharing-with-google-settings/setting-bindings/create create mode 100644 gcloud/gemini/data-sharing-with-google-settings/setting-bindings/delete create mode 100644 gcloud/gemini/data-sharing-with-google-settings/setting-bindings/describe create mode 100644 gcloud/gemini/data-sharing-with-google-settings/setting-bindings/help create mode 100644 gcloud/gemini/data-sharing-with-google-settings/setting-bindings/list create mode 100644 gcloud/gemini/data-sharing-with-google-settings/setting-bindings/update create mode 100644 gcloud/gemini/data-sharing-with-google-settings/update create mode 100644 gcloud/gemini/gemini-gcp-enablement-settings/create create mode 100644 gcloud/gemini/gemini-gcp-enablement-settings/delete create mode 100644 gcloud/gemini/gemini-gcp-enablement-settings/describe create mode 100644 gcloud/gemini/gemini-gcp-enablement-settings/help create mode 100644 gcloud/gemini/gemini-gcp-enablement-settings/list create mode 100644 gcloud/gemini/gemini-gcp-enablement-settings/setting-bindings/create create mode 100644 gcloud/gemini/gemini-gcp-enablement-settings/setting-bindings/delete create mode 100644 gcloud/gemini/gemini-gcp-enablement-settings/setting-bindings/describe create mode 100644 gcloud/gemini/gemini-gcp-enablement-settings/setting-bindings/help create mode 100644 gcloud/gemini/gemini-gcp-enablement-settings/setting-bindings/list create mode 100644 gcloud/gemini/gemini-gcp-enablement-settings/setting-bindings/update create mode 100644 gcloud/gemini/gemini-gcp-enablement-settings/update create mode 100644 gcloud/gemini/logging-settings/create create mode 100644 gcloud/gemini/logging-settings/delete create mode 100644 gcloud/gemini/logging-settings/describe create mode 100644 gcloud/gemini/logging-settings/help create mode 100644 gcloud/gemini/logging-settings/list create mode 100644 gcloud/gemini/logging-settings/setting-bindings/create create mode 100644 gcloud/gemini/logging-settings/setting-bindings/delete create mode 100644 gcloud/gemini/logging-settings/setting-bindings/describe create mode 100644 gcloud/gemini/logging-settings/setting-bindings/help create mode 100644 gcloud/gemini/logging-settings/setting-bindings/list create mode 100644 gcloud/gemini/logging-settings/setting-bindings/update create mode 100644 gcloud/gemini/logging-settings/update create mode 100644 gcloud/gemini/release-channel-settings/create create mode 100644 gcloud/gemini/release-channel-settings/delete create mode 100644 gcloud/gemini/release-channel-settings/describe create mode 100644 gcloud/gemini/release-channel-settings/help create mode 100644 gcloud/gemini/release-channel-settings/list create mode 100644 gcloud/gemini/release-channel-settings/setting-bindings/create create mode 100644 gcloud/gemini/release-channel-settings/setting-bindings/delete create mode 100644 gcloud/gemini/release-channel-settings/setting-bindings/describe create mode 100644 gcloud/gemini/release-channel-settings/setting-bindings/help create mode 100644 gcloud/gemini/release-channel-settings/setting-bindings/list create mode 100644 gcloud/gemini/release-channel-settings/setting-bindings/update create mode 100644 gcloud/gemini/release-channel-settings/update create mode 100644 gcloud/migration/vms/target-projects/help create mode 100644 gcloud/migration/vms/target-projects/list create mode 100644 gcloud/oracle-database/autonomous-databases/restart create mode 100644 gcloud/oracle-database/autonomous-databases/start create mode 100644 gcloud/oracle-database/autonomous-databases/stop create mode 100644 gcloud/oracle-database/autonomous-databases/switchover diff --git a/gcloud/_version b/gcloud/_version index 0f5b82f55..96c5b5b04 100644 --- a/gcloud/_version +++ b/gcloud/_version @@ -1,8 +1,8 @@ -Google Cloud SDK 517.0.0 -alpha 2025.03.29 -beta 2025.03.29 -bq 2.1.14 +Google Cloud SDK 518.0.0 +alpha 2025.04.11 +beta 2025.04.11 +bq 2.1.15 bundled-python3-unix 3.12.8 -core 2025.03.29 +core 2025.04.11 gcloud-crc32c 1.0.0 gsutil 5.33 diff --git a/gcloud/alloydb/clusters/export b/gcloud/alloydb/clusters/export index b77c35299..2d71828d7 100644 --- a/gcloud/alloydb/clusters/export +++ b/gcloud/alloydb/clusters/export @@ -28,7 +28,7 @@ POSITIONAL ARGUMENTS REQUIRED FLAGS --database=DATABASE - Database name from which export has to be done. + Database name. Destination URI where the file needs to be exported. diff --git a/gcloud/alloydb/clusters/import b/gcloud/alloydb/clusters/import index a3c41aec9..f9ef02b83 100644 --- a/gcloud/alloydb/clusters/import +++ b/gcloud/alloydb/clusters/import @@ -77,7 +77,7 @@ OPTIONAL FLAGS complete. --database=DATABASE - Database name from which export has to be done. + Database name. --user=USER Database user for the import. diff --git a/gcloud/alpha/alloydb/clusters/export b/gcloud/alpha/alloydb/clusters/export index c402a0de3..e7de99d3b 100644 --- a/gcloud/alpha/alloydb/clusters/export +++ b/gcloud/alpha/alloydb/clusters/export @@ -28,7 +28,7 @@ POSITIONAL ARGUMENTS REQUIRED FLAGS --database=DATABASE - Database name from which export has to be done. + Database name. Destination URI where the file needs to be exported. diff --git a/gcloud/alpha/alloydb/clusters/import b/gcloud/alpha/alloydb/clusters/import index 61a4b9ae3..9a2d551b3 100644 --- a/gcloud/alpha/alloydb/clusters/import +++ b/gcloud/alpha/alloydb/clusters/import @@ -78,7 +78,7 @@ OPTIONAL FLAGS complete. --database=DATABASE - Database name from which export has to be done. + Database name. --user=USER Database user for the import. diff --git a/gcloud/alpha/auth/enterprise-certificate-config/create/macos b/gcloud/alpha/auth/enterprise-certificate-config/create/macos index b32b00251..57149622b 100644 --- a/gcloud/alpha/auth/enterprise-certificate-config/create/macos +++ b/gcloud/alpha/auth/enterprise-certificate-config/create/macos @@ -5,6 +5,7 @@ NAME SYNOPSIS gcloud alpha auth enterprise-certificate-config create macos --issuer=ISSUER [--ecp=ECP] [--ecp-client=ECP_CLIENT] + [--keychain-type=KEYCHAIN_TYPE; default="all"] [--output-file=OUTPUT_FILE] [--tls-offload=TLS_OFFLOAD] [GCLOUD_WIDE_FLAG ...] @@ -31,6 +32,11 @@ OPTIONAL FLAGS Provide a custom path to the enterprise-certificate-proxy shared client library. This flag must be the full path to the shared library. + --keychain-type=KEYCHAIN_TYPE; default="all" + Specify the target keychain(s) for certificate lookup.Accepted values + are "login", "system", or "all". If omitted,defaults to "all". Use + "all" to include custom keychains. + --output-file=OUTPUT_FILE Override the file path that the enterprise-certificate-proxy configuration is written to. diff --git a/gcloud/alpha/backup-dr/management-servers/create b/gcloud/alpha/backup-dr/management-servers/create index f733fcf88..619664772 100644 --- a/gcloud/alpha/backup-dr/management-servers/create +++ b/gcloud/alpha/backup-dr/management-servers/create @@ -15,11 +15,10 @@ DESCRIPTION EXAMPLES To create a new management server sample-ms in project sample-project and - location us-central1 with network sample-network, run: + location us-central1, run: $ gcloud alpha backup-dr management-servers create sample-ms \ - --project=sample-project --location=us-central1 \ - --network=projects/sample-project/global/networks/sample-network + --project=sample-project --location=us-central1 POSITIONAL ARGUMENTS Management Server resource - Name of the management server to be created. @@ -62,14 +61,17 @@ FLAGS disable. --network=NETWORK - Name of an existing VPC network with private service access configured - in the format - projects//global/networks/. This VPC - network allows the management console to communicate with all - backup/recovery appliances and requires a minimum IP range of /23. This - value cannot be changed after you deploy the management server. If you - don't have private service access, configure one. [Learn more] + (DEPRECATED) Name of an existing VPC network with private service + access configured in the format - + projects//global/networks/. This VPC network allows + the management console to communicate with all backup/recovery + appliances and requires a minimum IP range of /23. This value cannot be + changed after you deploy the management server. If you don't have + private service access, configure one. [Learn more] (https://cloud.google.com/vpc/docs/configure-private-services-access) + Flag --network is deprecated. + 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/bigtable/help b/gcloud/alpha/bigtable/help index f287a8a85..16c3151c9 100644 --- a/gcloud/alpha/bigtable/help +++ b/gcloud/alpha/bigtable/help @@ -36,6 +36,9 @@ GROUPS logical-views (ALPHA) Manage Bigtable logical views. + materialized-views + (ALPHA) Manage Bigtable materialized views. + operations (ALPHA) Manage Cloud Bigtable operations. diff --git a/gcloud/alpha/bigtable/instances/tables/create b/gcloud/alpha/bigtable/instances/tables/create index 8951c9222..b7e818be6 100644 --- a/gcloud/alpha/bigtable/instances/tables/create +++ b/gcloud/alpha/bigtable/instances/tables/create @@ -6,7 +6,9 @@ SYNOPSIS gcloud alpha bigtable instances tables create (TABLE : --instance=INSTANCE) --column-families=[COLUMN_FAMILIES,...] [--change-stream-retention-period=CHANGE_STREAM_RETENTION_PERIOD] - [--deletion-protection] [--splits=[SPLITS,...]] + [--deletion-protection] + [--row-key-schema-definition-file=ROW_KEY_SCHEMA_DEFINITION_FILE] + [--row-key-schema-pre-encoded-bytes] [--splits=[SPLITS,...]] [--automated-backup-retention-period=AUTOMATED_BACKUP_RETENTION_PERIOD | --enable-automated-backup] [GCLOUD_WIDE_FLAG ...] @@ -125,6 +127,34 @@ OPTIONAL FLAGS --deletion-protection Once specified, the table is deletion protected. + --row-key-schema-definition-file=ROW_KEY_SCHEMA_DEFINITION_FILE + The row key schema for the table. The schema is defined in a YAML or + JSON file, equivalent to the StructType protobuf message. + + Example YAML: + + encoding: + delimitedBytes: + delimiter: '#' + fields: + - fieldName: field1 + type: + bytesType: + encoding: + raw: {} + - fieldName: field2 + type: + bytesType: + encoding: + raw: {} + + --row-key-schema-pre-encoded-bytes + By default, Base64 encoding is applied to all binary fields in the + YAML/JSON file (for example, encoding.delimitedBytes.delimiter). + + Use this to indicate that all binary fields are already encoded in the + YAML/JSON file and should not be encoded again. + --splits=[SPLITS,...] Row keys where the table should initially be split. For example: car,key diff --git a/gcloud/alpha/bigtable/instances/tables/update b/gcloud/alpha/bigtable/instances/tables/update index 9e11c1ba3..618ce97e8 100644 --- a/gcloud/alpha/bigtable/instances/tables/update +++ b/gcloud/alpha/bigtable/instances/tables/update @@ -4,11 +4,14 @@ NAME SYNOPSIS gcloud alpha bigtable instances tables update (TABLE : --instance=INSTANCE) - [--async] [--deletion-protection] + [--async] [--deletion-protection] [--row-key-schema-pre-encoded-bytes] [--automated-backup-retention-period=AUTOMATED_BACKUP_RETENTION_PERIOD | --disable-automated-backup | --enable-automated-backup] [--change-stream-retention-period=CHANGE_STREAM_RETENTION_PERIOD - | --clear-change-stream-retention-period] [GCLOUD_WIDE_FLAG ...] + | --clear-change-stream-retention-period] + [--clear-row-key-schema + | --row-key-schema-definition-file=ROW_KEY_SCHEMA_DEFINITION_FILE] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Update an existing new Cloud Bigtable table with the specified @@ -92,6 +95,16 @@ FLAGS --deletion-protection Once specified, the table is deletion protected. + --row-key-schema-pre-encoded-bytes + By default, Base64 encoding is applied to all binary fields in the + YAML/JSON file (for example, encoding.delimitedBytes.delimiter). + + Use this to indicate that all binary fields are already encoded in the + YAML/JSON file and should not be encoded again. + + This field is only used when row-key-schema-definition-file is set. It + is ignored if clear-row-key-schema is set. + At most one of these can be specified: --automated-backup-retention-period=AUTOMATED_BACKUP_RETENTION_PERIOD @@ -120,6 +133,35 @@ FLAGS This disables the change stream and eventually removes the change stream data. + Whether to update or clear the row key schema in the updated table. Only + one of these flags can be set. + + At most one of these can be specified: + + --clear-row-key-schema + Whether to clear the row key schema in the updated table. + + --row-key-schema-definition-file=ROW_KEY_SCHEMA_DEFINITION_FILE + The row key schema for the table. The schema is defined in a YAML or + JSON file, equivalent to the StructType protobuf message. + + Example YAML: + + encoding: + delimitedBytes: + delimiter: '#' + fields: + - fieldName: field1 + type: + bytesType: + encoding: + raw: {} + - fieldName: field2 + type: + bytesType: + encoding: + raw: {} + 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/bigtable/materialized-views/create b/gcloud/alpha/bigtable/materialized-views/create new file mode 100644 index 000000000..9fc2a95cf --- /dev/null +++ b/gcloud/alpha/bigtable/materialized-views/create @@ -0,0 +1,80 @@ +NAME + gcloud alpha bigtable materialized-views create - create a new Bigtable + materialized view + +SYNOPSIS + gcloud alpha bigtable materialized-views create + (MATERIALIZED_VIEW : --instance=INSTANCE) --query=QUERY [--async] + [--deletion-protection=DELETION_PROTECTION] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Create a new Bigtable materialized view. + +EXAMPLES + To create a materialized view, run: $ gcloud alpha bigtable materialized-views create \ + my-materialized-view-id --instance=my-instance-id \ + --query="SELECT my-column-family FROM my-table \ + --deletion-protection=false" + +POSITIONAL ARGUMENTS + Materialized view resource - The materialized view 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 materialized_view 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. + + MATERIALIZED_VIEW + ID of the materialized view or fully qualified identifier for the + materialized view. + + To set the name attribute: + ▸ provide the argument materialized_view on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --instance=INSTANCE + Bigtable instance for the materialized view. + + To set the instance attribute: + ▸ provide the argument materialized_view on the command line with a + fully specified name; + ▸ provide the argument --instance on the command line. + +REQUIRED FLAGS + --query=QUERY + The query of the view. + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --deletion-protection=DELETION_PROTECTION + Whether the view is protected from deletion. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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 bigtable materialized-views create + + $ gcloud beta bigtable materialized-views create + diff --git a/gcloud/alpha/bigtable/materialized-views/delete b/gcloud/alpha/bigtable/materialized-views/delete new file mode 100644 index 000000000..a41f93865 --- /dev/null +++ b/gcloud/alpha/bigtable/materialized-views/delete @@ -0,0 +1,67 @@ +NAME + gcloud alpha bigtable materialized-views delete - delete a Bigtable + materialized view + +SYNOPSIS + gcloud alpha bigtable materialized-views delete + (MATERIALIZED_VIEW : --instance=INSTANCE) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Delete a Bigtable materialized view. + +EXAMPLES + To delete a materialized view, run: + + $ gcloud alpha bigtable materialized-views delete \ + my-materialized-view-id --instance=my-instance-id + +POSITIONAL ARGUMENTS + Materialized view resource - The materialized view 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 materialized_view 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. + + MATERIALIZED_VIEW + ID of the materialized view or fully qualified identifier for the + materialized view. + + To set the name attribute: + ▸ provide the argument materialized_view on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --instance=INSTANCE + Bigtable instance for the materialized view. + + To set the instance attribute: + ▸ provide the argument materialized_view on the command line with a + fully specified name; + ▸ provide the argument --instance on the command line. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. These variants are also available: + + $ gcloud bigtable materialized-views delete + + $ gcloud beta bigtable materialized-views delete + diff --git a/gcloud/alpha/bigtable/materialized-views/describe b/gcloud/alpha/bigtable/materialized-views/describe new file mode 100644 index 000000000..8151df322 --- /dev/null +++ b/gcloud/alpha/bigtable/materialized-views/describe @@ -0,0 +1,67 @@ +NAME + gcloud alpha bigtable materialized-views describe - describe an existing + Bigtable materialized view + +SYNOPSIS + gcloud alpha bigtable materialized-views describe + (MATERIALIZED_VIEW : --instance=INSTANCE) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Describe an existing Bigtable materialized view. + +EXAMPLES + To view a materialized view's description, run: + + $ gcloud alpha bigtable materialized-views describe \ + my-materialized-view-id --instance=my-instance-id + +POSITIONAL ARGUMENTS + Materialized view resource - The materialized view 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 materialized_view 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. + + MATERIALIZED_VIEW + ID of the materialized view or fully qualified identifier for the + materialized view. + + To set the name attribute: + ▸ provide the argument materialized_view on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --instance=INSTANCE + Bigtable instance for the materialized view. + + To set the instance attribute: + ▸ provide the argument materialized_view on the command line with a + fully specified name; + ▸ provide the argument --instance on the command line. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. These variants are also available: + + $ gcloud bigtable materialized-views describe + + $ gcloud beta bigtable materialized-views describe + diff --git a/gcloud/alpha/bigtable/materialized-views/help b/gcloud/alpha/bigtable/materialized-views/help new file mode 100644 index 000000000..7290e34f3 --- /dev/null +++ b/gcloud/alpha/bigtable/materialized-views/help @@ -0,0 +1,43 @@ +NAME + gcloud alpha bigtable materialized-views - manage Bigtable materialized + views + +SYNOPSIS + gcloud alpha bigtable materialized-views COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Manage Bigtable materialized views. + +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 Bigtable materialized view. + + delete + (ALPHA) Delete a Bigtable materialized view. + + describe + (ALPHA) Describe an existing Bigtable materialized view. + + list + (ALPHA) List existing Bigtable materialized views. + + update + (ALPHA) Update a Bigtable materialized view. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails 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 bigtable materialized-views + + $ gcloud beta bigtable materialized-views + diff --git a/gcloud/alpha/bigtable/materialized-views/list b/gcloud/alpha/bigtable/materialized-views/list new file mode 100644 index 000000000..b5894fbeb --- /dev/null +++ b/gcloud/alpha/bigtable/materialized-views/list @@ -0,0 +1,87 @@ +NAME + gcloud alpha bigtable materialized-views list - list existing Bigtable + materialized views + +SYNOPSIS + gcloud alpha bigtable materialized-views list --instance=INSTANCE + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) List existing Bigtable materialized views. + +EXAMPLES + To list all materialized views for an instance, run: + + $ gcloud alpha bigtable materialized-views list \ + --instance=my-instance-id + +REQUIRED FLAGS + Instance resource - The instance to list materialized views for. This + represents a Cloud resource. (NOTE) Some attributes are not given + arguments in this group but can be set in other ways. + + To set the project attribute: + ◆ provide the argument --instance on the command line with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + --instance=INSTANCE + ID of the instance or fully qualified identifier for the instance. + + To set the instance attribute: + ▸ provide the argument --instance on the command line. + +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 bigtable materialized-views list + + $ gcloud beta bigtable materialized-views list + diff --git a/gcloud/alpha/bigtable/materialized-views/update b/gcloud/alpha/bigtable/materialized-views/update new file mode 100644 index 000000000..740ae5564 --- /dev/null +++ b/gcloud/alpha/bigtable/materialized-views/update @@ -0,0 +1,77 @@ +NAME + gcloud alpha bigtable materialized-views update - update a Bigtable + materialized view + +SYNOPSIS + gcloud alpha bigtable materialized-views update + (MATERIALIZED_VIEW : --instance=INSTANCE) + --deletion-protection=DELETION_PROTECTION [--async] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Update a Bigtable materialized view. + +EXAMPLES + To update a materialized view, run: $ gcloud alpha bigtable materialized-views update \ + my-materialized-view-id --instance=my-instance-id \ + --deletion-protection=true" + +POSITIONAL ARGUMENTS + Materialized view resource - The materialized view 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 materialized_view 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. + + MATERIALIZED_VIEW + ID of the materialized view or fully qualified identifier for the + materialized view. + + To set the name attribute: + ▸ provide the argument materialized_view on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --instance=INSTANCE + Bigtable instance for the materialized view. + + To set the instance attribute: + ▸ provide the argument materialized_view on the command line with a + fully specified name; + ▸ provide the argument --instance on the command line. + +REQUIRED FLAGS + --deletion-protection=DELETION_PROTECTION + Whether the view is protected from deletion. + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. These variants are also available: + + $ gcloud bigtable materialized-views update + + $ gcloud beta bigtable materialized-views update + diff --git a/gcloud/alpha/bigtable/tables/create b/gcloud/alpha/bigtable/tables/create index 65725205a..689627864 100644 --- a/gcloud/alpha/bigtable/tables/create +++ b/gcloud/alpha/bigtable/tables/create @@ -5,7 +5,9 @@ SYNOPSIS gcloud alpha bigtable tables create (TABLE : --instance=INSTANCE) --column-families=[COLUMN_FAMILIES,...] [--change-stream-retention-period=CHANGE_STREAM_RETENTION_PERIOD] - [--deletion-protection] [--splits=[SPLITS,...]] + [--deletion-protection] + [--row-key-schema-definition-file=ROW_KEY_SCHEMA_DEFINITION_FILE] + [--row-key-schema-pre-encoded-bytes] [--splits=[SPLITS,...]] [--automated-backup-retention-period=AUTOMATED_BACKUP_RETENTION_PERIOD | --enable-automated-backup] [GCLOUD_WIDE_FLAG ...] @@ -124,6 +126,34 @@ OPTIONAL FLAGS --deletion-protection Once specified, the table is deletion protected. + --row-key-schema-definition-file=ROW_KEY_SCHEMA_DEFINITION_FILE + The row key schema for the table. The schema is defined in a YAML or + JSON file, equivalent to the StructType protobuf message. + + Example YAML: + + encoding: + delimitedBytes: + delimiter: '#' + fields: + - fieldName: field1 + type: + bytesType: + encoding: + raw: {} + - fieldName: field2 + type: + bytesType: + encoding: + raw: {} + + --row-key-schema-pre-encoded-bytes + By default, Base64 encoding is applied to all binary fields in the + YAML/JSON file (for example, encoding.delimitedBytes.delimiter). + + Use this to indicate that all binary fields are already encoded in the + YAML/JSON file and should not be encoded again. + --splits=[SPLITS,...] Row keys where the table should initially be split. For example: car,key diff --git a/gcloud/alpha/bigtable/tables/update b/gcloud/alpha/bigtable/tables/update index 1c42e32d1..0243c7e2b 100644 --- a/gcloud/alpha/bigtable/tables/update +++ b/gcloud/alpha/bigtable/tables/update @@ -4,11 +4,14 @@ NAME SYNOPSIS gcloud alpha bigtable tables update (TABLE : --instance=INSTANCE) [--async] - [--deletion-protection] + [--deletion-protection] [--row-key-schema-pre-encoded-bytes] [--automated-backup-retention-period=AUTOMATED_BACKUP_RETENTION_PERIOD | --disable-automated-backup | --enable-automated-backup] [--change-stream-retention-period=CHANGE_STREAM_RETENTION_PERIOD - | --clear-change-stream-retention-period] [GCLOUD_WIDE_FLAG ...] + | --clear-change-stream-retention-period] + [--clear-row-key-schema + | --row-key-schema-definition-file=ROW_KEY_SCHEMA_DEFINITION_FILE] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Update an existing new Cloud Bigtable table with the specified @@ -92,6 +95,16 @@ FLAGS --deletion-protection Once specified, the table is deletion protected. + --row-key-schema-pre-encoded-bytes + By default, Base64 encoding is applied to all binary fields in the + YAML/JSON file (for example, encoding.delimitedBytes.delimiter). + + Use this to indicate that all binary fields are already encoded in the + YAML/JSON file and should not be encoded again. + + This field is only used when row-key-schema-definition-file is set. It + is ignored if clear-row-key-schema is set. + At most one of these can be specified: --automated-backup-retention-period=AUTOMATED_BACKUP_RETENTION_PERIOD @@ -120,6 +133,35 @@ FLAGS This disables the change stream and eventually removes the change stream data. + Whether to update or clear the row key schema in the updated table. Only + one of these flags can be set. + + At most one of these can be specified: + + --clear-row-key-schema + Whether to clear the row key schema in the updated table. + + --row-key-schema-definition-file=ROW_KEY_SCHEMA_DEFINITION_FILE + The row key schema for the table. The schema is defined in a YAML or + JSON file, equivalent to the StructType protobuf message. + + Example YAML: + + encoding: + delimitedBytes: + delimiter: '#' + fields: + - fieldName: field1 + type: + bytesType: + encoding: + raw: {} + - fieldName: field2 + type: + bytesType: + encoding: + raw: {} + GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, diff --git a/gcloud/alpha/compute/commitments/create b/gcloud/alpha/compute/commitments/create index 3831100a9..35196c9bb 100644 --- a/gcloud/alpha/compute/commitments/create +++ b/gcloud/alpha/compute/commitments/create @@ -257,15 +257,23 @@ OPTIONAL FLAGS Manage the properties of a shared reservation to create --share-setting=SHARE_SETTING - Specify if this reservation is shared, and if so, the type of - sharing. If you omit this flag, this value is local (not shared) - by default. SHARE_SETTING must be one of: local, projects. + The projects that can use the reservation. SHARE_SETTING must be + one of: + + local + Only your project can use the reservation. This is the + default value. + projects + Your project and up to 100 other projects within your + project's organization can use the reservation. If you + specify this value, then you must also include the + --share-with flag in the command. --share-with=SHARE_WITH,[SHARE_WITH,...] - If this reservation is shared (--share-setting is not local), - provide a list of all of the specific projects that this - reservation is shared with. List must contain project IDs or - project numbers. + If this reservation is shared (--share-setting=projects), then + specify a comma-separated list of projects to share the + reservation with. List projects using project IDs or project + numbers. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/alpha/compute/commitments/update-reservations b/gcloud/alpha/compute/commitments/update-reservations index 6594ec00b..a9ee9eb60 100644 --- a/gcloud/alpha/compute/commitments/update-reservations +++ b/gcloud/alpha/compute/commitments/update-reservations @@ -155,15 +155,22 @@ FLAGS The size of the local SSD in base-2 GB. --dest-share-setting=DEST_SHARE_SETTING - Specify if this reservation is shared, and if so, the type of - sharing. If you omit this flag, this value is local (not shared) by - default. DEST_SHARE_SETTING must be one of: local, projects. + The projects that can use the reservation. DEST_SHARE_SETTING must + be one of: + + local + Only your project can use the reservation. This is the default + value. + projects + Your project and up to 100 other projects within your project's + organization can use the reservation. If you specify this + value, then you must also include the --share-with flag in the + command. --dest-share-with=SHARE_WITH,[SHARE_WITH,...] - If this reservation is shared (--share-setting is not local), - provide a list of all of the specific projects that this - reservation is shared with. List must contain project IDs or - project numbers. + If this reservation is shared (--share-setting=projects), then + specify a comma-separated list of projects to share the reservation + with. List projects using project IDs or project numbers. --source-accelerator=[count=COUNT],[type=TYPE] Manage the configuration of the type and number of accelerator @@ -190,15 +197,22 @@ FLAGS The size of the local SSD in base-2 GB. --source-share-setting=SOURCE_SHARE_SETTING - Specify if this reservation is shared, and if so, the type of - sharing. If you omit this flag, this value is local (not shared) by - default. SOURCE_SHARE_SETTING must be one of: local, projects. + The projects that can use the reservation. SOURCE_SHARE_SETTING + must be one of: + + local + Only your project can use the reservation. This is the default + value. + projects + Your project and up to 100 other projects within your project's + organization can use the reservation. If you specify this + value, then you must also include the --share-with flag in the + command. --source-share-with=SHARE_WITH,[SHARE_WITH,...] - If this reservation is shared (--share-setting is not local), - provide a list of all of the specific projects that this - reservation is shared with. List must contain project IDs or - project numbers. + If this reservation is shared (--share-setting=projects), then + specify a comma-separated list of projects to share the reservation + with. List projects using project IDs or project numbers. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/alpha/compute/config-ssh b/gcloud/alpha/compute/config-ssh index b52a218e1..70e945d21 100644 --- a/gcloud/alpha/compute/config-ssh +++ b/gcloud/alpha/compute/config-ssh @@ -31,7 +31,9 @@ DESCRIPTION $ scp ~/MY-FILE example-instance.us-central1-a.MY-PROJECT:~ Whenever instances are added, removed, or their external IP addresses are - changed, this command should be re-executed to update the configuration. + changed, the remove command must be run to clear the existing configuration + and then the command can set executed to set the configuration to the + current state. This command ensures that the user's public SSH key is present in the project's metadata. If the user does not have a public SSH key, one is diff --git a/gcloud/alpha/compute/disks/create b/gcloud/alpha/compute/disks/create index 1f1a1a434..803110350 100644 --- a/gcloud/alpha/compute/disks/create +++ b/gcloud/alpha/compute/disks/create @@ -105,8 +105,8 @@ FLAGS https://cloud.google.com/compute/docs/images/create-delete-deprecate-private-images#guest-os-features. GUEST_OS_FEATURE must be one of: BARE_METAL_LINUX_COMPATIBLE, GVNIC, IDPF, MULTI_IP_SUBNET, SEV_CAPABLE, SEV_LIVE_MIGRATABLE, - SEV_LIVE_MIGRATABLE_V2, SEV_SNP_CAPABLE, TDX_CAPABLE, UEFI_COMPATIBLE, - VIRTIO_SCSI_MULTIQUEUE, WINDOWS. + SEV_LIVE_MIGRATABLE_V2, SEV_SNP_CAPABLE, SNP_SVSM_CAPABLE, TDX_CAPABLE, + UEFI_COMPATIBLE, VIRTIO_SCSI_MULTIQUEUE, WINDOWS. --interface=INTERFACE Specifies the disk interface to use for attaching this disk. Valid diff --git a/gcloud/alpha/compute/images/create b/gcloud/alpha/compute/images/create index 1ea6ae629..59f224713 100644 --- a/gcloud/alpha/compute/images/create +++ b/gcloud/alpha/compute/images/create @@ -155,8 +155,8 @@ OPTIONAL FLAGS https://cloud.google.com/compute/docs/images/create-delete-deprecate-private-images#guest-os-features. GUEST_OS_FEATURE must be one of: BARE_METAL_LINUX_COMPATIBLE, GVNIC, IDPF, MULTI_IP_SUBNET, SEV_CAPABLE, SEV_LIVE_MIGRATABLE, - SEV_LIVE_MIGRATABLE_V2, SEV_SNP_CAPABLE, TDX_CAPABLE, UEFI_COMPATIBLE, - VIRTIO_SCSI_MULTIQUEUE, WINDOWS. + SEV_LIVE_MIGRATABLE_V2, SEV_SNP_CAPABLE, SNP_SVSM_CAPABLE, TDX_CAPABLE, + UEFI_COMPATIBLE, VIRTIO_SCSI_MULTIQUEUE, WINDOWS. --key-exchange-key-file=[KEK_VALUE,...] Comma-separated list of file paths that point to X.509 certificates in diff --git a/gcloud/alpha/compute/images/list b/gcloud/alpha/compute/images/list index 810301450..04d288687 100644 --- a/gcloud/alpha/compute/images/list +++ b/gcloud/alpha/compute/images/list @@ -60,7 +60,8 @@ FLAGS are available include the following: cos-cloud, debian-cloud, rocky-linux-cloud, ubuntu-os-cloud, centos-cloud, fedora-coreos-cloud, opensuse-cloud, oracle-linux-cloud, rhel-cloud, rhel-sap-cloud, - suse-cloud, suse-sap-cloud, ubuntu-os-pro-cloud, windows-cloud, + rocky-linux-accelerator-cloud, suse-cloud, suse-sap-cloud, + ubuntu-os-accelerator-images, ubuntu-os-pro-cloud, windows-cloud, windows-sql-cloud. Enabled by default, use --no-standard-images to disable. diff --git a/gcloud/alpha/compute/instance-groups/managed/resize-requests/create b/gcloud/alpha/compute/instance-groups/managed/resize-requests/create index b6ac1333a..e2f688ef7 100644 --- a/gcloud/alpha/compute/instance-groups/managed/resize-requests/create +++ b/gcloud/alpha/compute/instance-groups/managed/resize-requests/create @@ -31,13 +31,14 @@ REQUIRED FLAGS Exactly one of these must be specified: --instances=INSTANCE,[INSTANCE,...] - The names of instances to be created by this resize request. The - number of names specified determines the number of instances to - create. The group's target size will be increased by this number. + A comma-separated list of instance names. The number of names you + provide determines the number of instances to create with this resize + request. The group's target size increases by this count. --resize-by=RESIZE_BY - The number of instances to be created by this resize request. The - group's target size will be increased by this number. + The number of instances to create with this resize request. Instances + have automatically-generated names. The group's target size increases + by this number. OPTIONAL FLAGS --requested-run-duration=REQUESTED_RUN_DURATION @@ -48,6 +49,10 @@ OPTIONAL FLAGS day, 2 hours, 3 minutes, and 4 seconds. The value must be between 10m (10 minutes) and 7d (7 days). + If you want the managed instance group to consume a reservation or use + FLEX_START provisioning model, then this flag is optional. Otherwise, + it's required. + At most one of these can be specified: --region=REGION diff --git a/gcloud/alpha/compute/interconnects/application-awareness/get-config b/gcloud/alpha/compute/interconnects/application-awareness/get-config new file mode 100644 index 000000000..9a714e742 --- /dev/null +++ b/gcloud/alpha/compute/interconnects/application-awareness/get-config @@ -0,0 +1,40 @@ +NAME + gcloud alpha compute interconnects application-awareness get-config - get + application awareness configuration of a Compute Engine interconnect + +SYNOPSIS + gcloud alpha compute interconnects application-awareness get-config NAME + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) gcloud alpha compute interconnects application-awareness get-config + displays configuration data associated with application awareness on + Compute Engine interconnect in a project. + + For an example, refer to the EXAMPLES section below. + +EXAMPLES + To displays configuration data associated with application awareness on + Compute Engine interconnect in a project, run: + + $ gcloud alpha compute interconnects application-awareness \ + get-config example-interconnect + +POSITIONAL ARGUMENTS + NAME + Name of the interconnect to describe. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails 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/interconnects/application-awareness/help b/gcloud/alpha/compute/interconnects/application-awareness/help new file mode 100644 index 000000000..9c2774bb4 --- /dev/null +++ b/gcloud/alpha/compute/interconnects/application-awareness/help @@ -0,0 +1,31 @@ +NAME + gcloud alpha compute interconnects application-awareness - read and + manipulate configuration for application awareness on Compute Engine + interconnect + +SYNOPSIS + gcloud alpha compute interconnects application-awareness COMMAND + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Read and manipulate configuration for application awareness on + Compute Engine interconnect. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + get-config + (ALPHA) Get application awareness configuration of a Compute Engine + interconnect. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails 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/interconnects/help b/gcloud/alpha/compute/interconnects/help index 5cbc0db0a..b53e3c2e0 100644 --- a/gcloud/alpha/compute/interconnects/help +++ b/gcloud/alpha/compute/interconnects/help @@ -23,6 +23,10 @@ GCLOUD WIDE FLAGS GROUPS GROUP is one of the following: + application-awareness + (ALPHA) Read and manipulate configuration for application awareness on + Compute Engine interconnect. + attachments (ALPHA) Read and manipulate Compute Engine interconnect attachments. diff --git a/gcloud/alpha/compute/network-firewall-policies/rules/create b/gcloud/alpha/compute/network-firewall-policies/rules/create index 9565d4e76..47ac2ba01 100644 --- a/gcloud/alpha/compute/network-firewall-policies/rules/create +++ b/gcloud/alpha/compute/network-firewall-policies/rules/create @@ -21,9 +21,10 @@ SYNOPSIS [--src-region-codes=[SOURCE_REGION_CODES,...]] [--src-secure-tags=[SOURCE_SECURE_TAGS,...]] [--src-threat-intelligence=[SOURCE_THREAT_INTELLIGENCE_LISTS,...]] + [--target-forwarding-rules=[TARGET_FORWARDING_RULES,...]] [--target-secure-tags=[TARGET_SECURE_TAGS,...]] [--target-service-accounts=[TARGET_SERVICE_ACCOUNTS,...]] - [--[no-]tls-inspect] + [--target-type=TARGET_TYPE] [--[no-]tls-inspect] [--firewall-policy-region=FIREWALL_POLICY_REGION | --global-firewall-policy] [GCLOUD_WIDE_FLAG ...] @@ -146,7 +147,7 @@ OPTIONAL FLAGS --src-region-codes=[SOURCE_REGION_CODES,...] Source Region Code to match for this rule. Can only be specified if - DIRECTION is ingress. Cannot be specified when the source network scope + DIRECTION is ingress. Cannot be specified when the source network type is NON_INTERNET, VPC_NETWORK or INTRA_VPC. --src-secure-tags=[SOURCE_SECURE_TAGS,...] @@ -167,6 +168,13 @@ OPTIONAL FLAGS lists can be found here: https://cloud.google.com/vpc/docs/firewall-policies-rule-details#threat-intelligence-fw-policy. + --target-forwarding-rules=[TARGET_FORWARDING_RULES,...] + A list of forwarding rules to which this rule applies. This field + allows you to control which load balancers get this rule. If not + specified, the rule applies to all load balancers. This field is only + applicable when --target-type is INTERNAL_MANAGED_LB. It accepts full + or partial resourceURLs. + --target-secure-tags=[TARGET_SECURE_TAGS,...] An optional, list of target secure tags with a name of the format tagValues/ or full namespaced name @@ -174,6 +182,12 @@ OPTIONAL FLAGS --target-service-accounts=[TARGET_SERVICE_ACCOUNTS,...] List of target service accounts for the rule. + --target-type=TARGET_TYPE + Target type of the rule. By default a rule applies to VM instances + (target-type = INSTANCES). Use INTERNAL_MANAGED_LB value to apply the + rule to load balancers. TARGET_TYPE must be one of: INSTANCES, + INTERNAL_MANAGED_LB. + --[no-]tls-inspect Use this flag to indicate whether TLS traffic should be inspected using the TLS inspection policy when the security profile group is applied. diff --git a/gcloud/alpha/compute/network-firewall-policies/rules/update b/gcloud/alpha/compute/network-firewall-policies/rules/update index 86ec3b26c..6815a819a 100644 --- a/gcloud/alpha/compute/network-firewall-policies/rules/update +++ b/gcloud/alpha/compute/network-firewall-policies/rules/update @@ -21,9 +21,10 @@ SYNOPSIS [--src-region-codes=[SOURCE_REGION_CODES,...]] [--src-secure-tags=[SOURCE_SECURE_TAGS,...]] [--src-threat-intelligence=[SOURCE_THREAT_INTELLIGENCE_LISTS,...]] + [--target-forwarding-rules=[TARGET_FORWARDING_RULES,...]] [--target-secure-tags=[TARGET_SECURE_TAGS,...]] [--target-service-accounts=[TARGET_SERVICE_ACCOUNTS,...]] - [--[no-]tls-inspect] + [--target-type=TARGET_TYPE] [--[no-]tls-inspect] [--firewall-policy-region=FIREWALL_POLICY_REGION | --global-firewall-policy] [GCLOUD_WIDE_FLAG ...] @@ -142,7 +143,7 @@ OPTIONAL FLAGS --src-region-codes=[SOURCE_REGION_CODES,...] Source Region Code to match for this rule. Can only be specified if - DIRECTION is ingress. Cannot be specified when the source network scope + DIRECTION is ingress. Cannot be specified when the source network type is NON_INTERNET, VPC_NETWORK or INTRA_VPC. --src-secure-tags=[SOURCE_SECURE_TAGS,...] @@ -163,6 +164,13 @@ OPTIONAL FLAGS lists can be found here: https://cloud.google.com/vpc/docs/firewall-policies-rule-details#threat-intelligence-fw-policy. + --target-forwarding-rules=[TARGET_FORWARDING_RULES,...] + A list of forwarding rules to which this rule applies. This field + allows you to control which load balancers get this rule. If not + specified, the rule applies to all load balancers. This field is only + applicable when --target-type is INTERNAL_MANAGED_LB. It accepts full + or partial resourceURLs. + --target-secure-tags=[TARGET_SECURE_TAGS,...] An optional, list of target secure tags with a name of the format tagValues/ or full namespaced name @@ -170,6 +178,12 @@ OPTIONAL FLAGS --target-service-accounts=[TARGET_SERVICE_ACCOUNTS,...] List of target service accounts for the rule. + --target-type=TARGET_TYPE + Target type of the rule. By default a rule applies to VM instances + (target-type = INSTANCES). Use INTERNAL_MANAGED_LB value to apply the + rule to load balancers. TARGET_TYPE must be one of: INSTANCES, + INTERNAL_MANAGED_LB. + --[no-]tls-inspect Use this flag to indicate whether TLS traffic should be inspected using the TLS inspection policy when the security profile group is applied. diff --git a/gcloud/alpha/compute/networks/peerings/help b/gcloud/alpha/compute/networks/peerings/help index cb24f353c..0d7fae302 100644 --- a/gcloud/alpha/compute/networks/peerings/help +++ b/gcloud/alpha/compute/networks/peerings/help @@ -28,6 +28,9 @@ COMMANDS list-routes (ALPHA) List received or advertised routes for a VPC network peering. + request-delete + (ALPHA) Request deletion of a Compute Engine network peering. + update (ALPHA) Update a Compute Engine network peering. diff --git a/gcloud/alpha/compute/networks/peerings/request-delete b/gcloud/alpha/compute/networks/peerings/request-delete new file mode 100644 index 000000000..f0d333e84 --- /dev/null +++ b/gcloud/alpha/compute/networks/peerings/request-delete @@ -0,0 +1,53 @@ +NAME + gcloud alpha compute networks peerings request-delete - request deletion of + a Compute Engine network peering + +SYNOPSIS + gcloud alpha compute networks peerings request-delete NAME + --network=NETWORK [--async] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) gcloud alpha compute networks peerings request-delete is used to + request deletion of a consensus peering between virtual networks. The + peering can be deleted if both sides request deletion. + +EXAMPLES + To request deletion of a consensus peering with the name 'peering-name' + between the network 'local-network' and the network 'peer-network', run: + + $ gcloud alpha compute networks peerings request-delete \ + peering-name --network=local-network + + $ gcloud alpha compute networks peerings request-delete \ + peering-name --network=peer-network + + To complete the deletion, run gcloud alpha compute networks peerings delete + for each side of the peering. + +POSITIONAL ARGUMENTS + NAME + The name of the peering. + +REQUIRED FLAGS + --network=NETWORK + The name of the network in the current project containing the peering. + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/compute/reservations/create b/gcloud/alpha/compute/reservations/create index 21354e845..4c23ce6bc 100644 --- a/gcloud/alpha/compute/reservations/create +++ b/gcloud/alpha/compute/reservations/create @@ -201,15 +201,25 @@ OPTIONAL FLAGS Manage the properties of a shared reservation. --share-setting=SHARE_SETTING - Specify if this reservation is shared, and if so, the type of - sharing. If you omit this flag, this value is local (not shared) by - default. SHARE_SETTING must be one of: local, projects, folders. + The projects that can use the reservation. SHARE_SETTING must be one + of: + + folders + Any project on the specified list of folders can use the + reservation. + local + Only your project can use the reservation. This is the default + value. + projects + Your project and up to 100 other projects within your project's + organization can use the reservation. If you specify this value, + then you must also include the --share-with flag in the command. --share-with=SHARE_WITH,[SHARE_WITH,...] - If this reservation is shared (--share-setting is not local), provide - a list of all of the specific projects or folders that this - reservation is shared with. List must contain project IDs or project - numbers or folder IDs. + If this reservation is shared (--share-setting=projects), then + specify a comma-separated list of projects to share the reservation + with. List projects using project IDs, project numbers, or folder + IDs. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/alpha/compute/reservations/update b/gcloud/alpha/compute/reservations/update index f9d01a55a..e4f1dd9f3 100644 --- a/gcloud/alpha/compute/reservations/update +++ b/gcloud/alpha/compute/reservations/update @@ -8,6 +8,7 @@ SYNOPSIS [--[no-]enable-emergent-maintenance] [--remove-share-with=PROJECT,[PROJECT,...]] [--reservation-sharing-policy=RESERVATION_SHARING_POLICY] + [--share-setting=SHARE_SETTING] [--share-with=SHARE_WITH,[SHARE_WITH,...]] [--vm-count=VM_COUNT] [--zone=ZONE] [--delete-after-duration=DELETE_AFTER_DURATION @@ -52,9 +53,9 @@ POSITIONAL ARGUMENTS FLAGS --add-share-with=PROJECT,[PROJECT,...] - A list of specific projects to add to the list of projects that this - reservation is shared with. List must contain project IDs or project - numbers. + If this reservation is shared (--share-setting is projects), then + specify a comma-separated list of projects to share the reservation + with. You must list the projects using project IDs or project numbers. --[no-]enable-emergent-maintenance The emergent maintenance flag for the reservation, which enrolls all @@ -77,10 +78,22 @@ FLAGS The reservation won't be shared with Google Cloud services. If you omit this flag during creation, the default value is DISALLOW_ALL. + --share-setting=SHARE_SETTING + The projects that can use the reservation. SHARE_SETTING must be one + of: + + local + Only your project can use the reservation. This is the default + value. + projects + Your project and up to 100 other projects within your project's + organization can use the reservation. If you specify this value, + then you must also include the --share-with flag in the command. + --share-with=SHARE_WITH,[SHARE_WITH,...] - If this reservation is shared (--share-setting is not local), provide a - list of all of the specific projects that this reservation is shared - with. List must contain project IDs or project numbers. + If this reservation is shared (--share-setting=projects), then specify + a comma-separated list of projects to share the reservation with. List + projects using project IDs or project numbers. --vm-count=VM_COUNT The number of VM instances that are allocated to this reservation. The diff --git a/gcloud/alpha/compute/routers/nats/create b/gcloud/alpha/compute/routers/nats/create index 34bfeff5a..b7fcd3de2 100644 --- a/gcloud/alpha/compute/routers/nats/create +++ b/gcloud/alpha/compute/routers/nats/create @@ -221,8 +221,8 @@ OPTIONAL FLAGS --nat-external-ip-pool=IP_ADDRESS,[IP_ADDRESS,...] External IP Addresses to use for Cloud NAT - IPv4 subnetwork range options. If they are not specified, one of IPv6 - subnetwork range option has to be provided. + Options for IPv4 subnetwork ranges. If not specified, one of the options + for IPv6 subnetwork ranges must be provided. At most one of these can be specified: @@ -246,16 +246,16 @@ OPTIONAL FLAGS Allow only primary IP ranges of all subnetworks in the region to use NAT. - IPv6 subnetwork range options. If they are not specified, one of IPv4 - subnetwork range option has to be provided. + Options for IPv6 subnetwork ranges. If not specified, one of the options + for IPv4 subnetwork ranges must be provided. At most one of these can be specified: --nat64-all-v6-subnet-ip-ranges - Allow all ip ranges of ipv6 subnetworks in the region to use NAT. + Allow all IPv6 subnetwork ranges in the region to use NAT. --nat64-custom-v6-subnet-ip-ranges=SUBNETWORK,[SUBNETWORK,...] - List of ipv6 subnetworks to be allowed tp use NAT. + List of subnetworks with IPv6 ranges to be allowed to use NAT. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/alpha/compute/routers/nats/update b/gcloud/alpha/compute/routers/nats/update index 2579572c3..db6aa9120 100644 --- a/gcloud/alpha/compute/routers/nats/update +++ b/gcloud/alpha/compute/routers/nats/update @@ -209,12 +209,12 @@ OPTIONAL FLAGS These IPs must be valid external IPs that have been used as NAT IPs - IPv4 subnetwork range options. + Options for IPv4 subnetwork ranges. At most one of these can be specified: --clear-nat-subnet-ip-ranges - Clear options related to the NAT's subnet ranges. + Clear IPv4 subnetwork ranges. --nat-all-subnet-ip-ranges Allow all IP ranges of all subnetworks in the region, including @@ -236,18 +236,18 @@ OPTIONAL FLAGS Allow only primary IP ranges of all subnetworks in the region to use NAT. - IPv6 subnetwork range options. + Options for IPv6 subnetwork ranges. At most one of these can be specified: --clear-nat64-subnet-ip-ranges - Clear options related to the NAT64's subnet ranges. + Clear IPv6 subnetwork ranges. --nat64-all-v6-subnet-ip-ranges - Allow all ip ranges of ipv6 subnetworks in the region to use NAT. + Allow all IPv6 subnetwork ranges in the region to use NAT. --nat64-custom-v6-subnet-ip-ranges=SUBNETWORK,[SUBNETWORK,...] - List of ipv6 subnetworks to be allowed tp use NAT. + List of subnetworks with IPv6 ranges to be allowed to use NAT. At most one of these can be specified: diff --git a/gcloud/alpha/compute/service-attachments/describe b/gcloud/alpha/compute/service-attachments/describe index 62ee80738..16f3c74ce 100644 --- a/gcloud/alpha/compute/service-attachments/describe +++ b/gcloud/alpha/compute/service-attachments/describe @@ -4,7 +4,7 @@ NAME SYNOPSIS gcloud alpha compute service-attachments describe NAME [--region=REGION] - [GCLOUD_WIDE_FLAG ...] + [--show-nat-ips] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Display details about a Google Compute Engine service attachment. @@ -40,6 +40,12 @@ FLAGS Alternatively, the region can be stored in the environment variable CLOUDSDK_COMPUTE_REGION. + --show-nat-ips + Determines whether to include the NAT IPs of connected endpoints in the + service attachment output. If enabled (--show-nat-ips), the output will + include the list of NAT IPs for each connected PSC endpoint and any + endpoints propagated from them. + GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, diff --git a/gcloud/alpha/compute/tpus/queued-resources/create b/gcloud/alpha/compute/tpus/queued-resources/create index 4777b16a1..4e7bbcfe2 100644 --- a/gcloud/alpha/compute/tpus/queued-resources/create +++ b/gcloud/alpha/compute/tpus/queued-resources/create @@ -85,7 +85,7 @@ POSITIONAL ARGUMENTS REQUIRED FLAGS --runtime-version=RUNTIME_VERSION - Runtime version for the TPU, such as 2.3. + Runtime version for the TPU, such as tpu-ubuntu2204-base. Specify a chip-based or core-based TPU node. @@ -223,8 +223,7 @@ OPTIONAL FLAGS --provisioning-model=PROVISIONING_MODEL If provided, the resource will be provisioned with the specified - provisioning model. Currently only flex-start and reservation-bound are - supported. + provisioning model. --range=RANGE CIDR range for the TPU. diff --git a/gcloud/alpha/compute/tpus/tpu-vm/create b/gcloud/alpha/compute/tpus/tpu-vm/create index f58c5195c..3f11a0b43 100644 --- a/gcloud/alpha/compute/tpus/tpu-vm/create +++ b/gcloud/alpha/compute/tpus/tpu-vm/create @@ -8,10 +8,11 @@ SYNOPSIS [--description=DESCRIPTION] [--internal-ips] [--labels=[KEY=VALUE,...]] [--metadata=[KEY=VALUE,...]] [--metadata-from-file=[KEY=VALUE,...]] [--network=NETWORK; default="default"] [--preemptible] - [--queue-count=QUEUE_COUNT] [--range=RANGE] [--reservation=RESERVATION] - [--reserved] [--scopes=[SCOPES,...]] - [--service-account=SERVICE_ACCOUNT] [--shielded-secure-boot] [--spot] - [--subnetwork=SUBNETWORK] [--tags=[TAGS,...]] + [--provisioning-model=PROVISIONING_MODEL] [--queue-count=QUEUE_COUNT] + [--range=RANGE] [--reservation=RESERVATION] [--reserved] + [--scopes=[SCOPES,...]] [--service-account=SERVICE_ACCOUNT] + [--shielded-secure-boot] [--spot] [--subnetwork=SUBNETWORK] + [--tags=[TAGS,...]] [--accelerator-type=ACCELERATOR_TYPE; default="v2-8" | --topology=TOPOLOGY --type=TYPE] [GCLOUD_WIDE_FLAG ...] @@ -156,6 +157,11 @@ OPTIONAL FLAGS Preemptible TPUs cannot be restarted. + --provisioning-model=PROVISIONING_MODEL + The provisioning model of the TPU node. One of [standard, spot, + reservation-bound]. Setting --provisioning-model=spot is functionally + equivalent to setting --spot. + --queue-count=QUEUE_COUNT Specifies the networking queue count for TPU VM instances. Both Rx and Tx queues will be set to this number. If it's not specified, a default diff --git a/gcloud/alpha/container/ai/recommender/accelerators/list b/gcloud/alpha/container/ai/recommender/accelerators/list index 6a461122c..3b2e73d11 100644 --- a/gcloud/alpha/container/ai/recommender/accelerators/list +++ b/gcloud/alpha/container/ai/recommender/accelerators/list @@ -7,7 +7,9 @@ SYNOPSIS [--format=FORMAT; default="table"] [--max-ntpot-milliseconds=MAX_NTPOT_MILLISECONDS] [--model-server=MODEL_SERVER] - [--model-server-version=MODEL_SERVER_VERSION] [GCLOUD_WIDE_FLAG ...] + [--model-server-version=MODEL_SERVER_VERSION] [--filter=EXPRESSION] + [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) This command lists all supported accelerators with their @@ -26,7 +28,7 @@ REQUIRED FLAGS --model=MODEL The model. -OPTIONAL FLAGS +FLAGS --format=FORMAT; default="table" The output format. Default is table, which displays select information in a table format. Use --format=yaml to display all details. FORMAT @@ -47,6 +49,38 @@ OPTIONAL FLAGS The model server version. If not specified, this defaults to the latest version. +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, diff --git a/gcloud/alpha/container/ai/recommender/model-and-server-combinations/list b/gcloud/alpha/container/ai/recommender/model-and-server-combinations/list index 97490f316..1f4befc6f 100644 --- a/gcloud/alpha/container/ai/recommender/model-and-server-combinations/list +++ b/gcloud/alpha/container/ai/recommender/model-and-server-combinations/list @@ -5,7 +5,9 @@ NAME SYNOPSIS gcloud alpha container ai recommender model-and-server-combinations list [--model=MODEL] [--model-server=MODEL_SERVER] - [--model-server-version=MODEL_SERVER_VERSION] [GCLOUD_WIDE_FLAG ...] + [--model-server-version=MODEL_SERVER_VERSION] [--filter=EXPRESSION] + [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) This command lists all supported model, model server, and model @@ -22,6 +24,38 @@ FLAGS The model server version. If not specified, this defaults to the any model server version. +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, diff --git a/gcloud/alpha/container/ai/recommender/model-server-versions/list b/gcloud/alpha/container/ai/recommender/model-server-versions/list index 85b3a8f98..1175ec3e1 100644 --- a/gcloud/alpha/container/ai/recommender/model-server-versions/list +++ b/gcloud/alpha/container/ai/recommender/model-server-versions/list @@ -4,7 +4,9 @@ NAME SYNOPSIS gcloud alpha container ai recommender model-server-versions list - --model=MODEL --model-server=MODEL_SERVER [GCLOUD_WIDE_FLAG ...] + --model=MODEL --model-server=MODEL_SERVER [--filter=EXPRESSION] + [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) To get supported model and model servers, run gcloud alpha @@ -20,6 +22,38 @@ REQUIRED FLAGS --model-server=MODEL_SERVER The model server. If not specified, this defaults to any model server. +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, diff --git a/gcloud/alpha/container/ai/recommender/model-servers/list b/gcloud/alpha/container/ai/recommender/model-servers/list index b588f01f7..14cc0af05 100644 --- a/gcloud/alpha/container/ai/recommender/model-servers/list +++ b/gcloud/alpha/container/ai/recommender/model-servers/list @@ -4,7 +4,8 @@ NAME SYNOPSIS gcloud alpha container ai recommender model-servers list --model=MODEL - [GCLOUD_WIDE_FLAG ...] + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) To get supported models, run gcloud alpha container ai recommender @@ -15,6 +16,38 @@ REQUIRED FLAGS --model=MODEL The model. +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, diff --git a/gcloud/alpha/container/ai/recommender/models/list b/gcloud/alpha/container/ai/recommender/models/list index 60015b1ee..1ee0d7d1a 100644 --- a/gcloud/alpha/container/ai/recommender/models/list +++ b/gcloud/alpha/container/ai/recommender/models/list @@ -2,11 +2,45 @@ NAME gcloud alpha container ai recommender models list - list supported models SYNOPSIS - gcloud alpha container ai recommender models list [GCLOUD_WIDE_FLAG ...] + gcloud alpha container ai recommender models list [--filter=EXPRESSION] + [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) List supported models. +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + 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, diff --git a/gcloud/alpha/container/backup-restore/backup-channels/create b/gcloud/alpha/container/backup-restore/backup-channels/create new file mode 100644 index 000000000..46f5ff766 --- /dev/null +++ b/gcloud/alpha/container/backup-restore/backup-channels/create @@ -0,0 +1,104 @@ +NAME + gcloud alpha container backup-restore backup-channels create - create a + backup channel + +SYNOPSIS + gcloud alpha container backup-restore backup-channels create + (BACKUP_CHANNEL : --location=LOCATION) + --destination-project=DESTINATION_PROJECT [--async] + [--description=DESCRIPTION] [--labels=[KEY=VALUE,...]] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Create a Backup for GKE backup channel. + +EXAMPLES + To create a backup channel my-backup-channel in project my-project in + location us-central1 with destination project projects/1234567890, run: + + $ gcloud alpha container backup-restore backup-channels create \ + my-backup-channel --project=my-project --location=us-central1 \ + --destination_project=projects/1234567890 + +POSITIONAL ARGUMENTS + Backup channel resource - Name of the backup channel to create. Once the + channel is created, this name can't be changed. This must be 63 or fewer + characters long and must be unique within the project and location. The + name may be provided either as a relative name, e.g. + projects//locations//backupChannels/ or + as a single ID name (with the parent resources provided via options or + through properties), e.g. BACKUP_CHANNEL --project= + --location=. 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 backup_channel 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. + + BACKUP_CHANNEL + ID of the backup channel or fully qualified identifier for the backup + channel. + + To set the backup_channel attribute: + ▸ provide the argument backup_channel on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + Google Cloud location. + + To set the location attribute: + ▸ provide the argument backup_channel on the command line with a + fully specified name; + ▸ provide the argument --location on the command line; + ▸ set the property gkebackup/location. + +REQUIRED FLAGS + --destination-project=DESTINATION_PROJECT + The project where Backups are allowed to be created. The format is + projects/{project}. Currently, {project} can only be the project + number. e.g. projects/1234567890. + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --description=DESCRIPTION + The description of the backup channel. + + --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 gkebackup/v1 API. The full documentation for this API + can be found at: + https://cloud.google.com/kubernetes-engine/docs/add-on/backup-for-gke + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud beta container backup-restore backup-channels create + diff --git a/gcloud/alpha/container/backup-restore/backup-channels/delete b/gcloud/alpha/container/backup-restore/backup-channels/delete new file mode 100644 index 000000000..96915e9e2 --- /dev/null +++ b/gcloud/alpha/container/backup-restore/backup-channels/delete @@ -0,0 +1,87 @@ +NAME + gcloud alpha container backup-restore backup-channels delete - delete a + backup channel + +SYNOPSIS + gcloud alpha container backup-restore backup-channels delete + (BACKUP_CHANNEL : --location=LOCATION) [--async] [--etag=ETAG] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Delete a Backup for GKE backup channel. + +EXAMPLES + To delete a backup channel my-backup-channel in project my-project in + location us-central1, run: + + $ gcloud alpha container backup-restore backup-channels delete \ + my-backup-channel --project=my-project --location=us-central1 + +POSITIONAL ARGUMENTS + Backup channel resource - Name of the backup channel to delete. The name + may be provided either as a relative name, e.g. + projects//locations//backupChannels/ or + as a single ID name (with the parent resources provided via options or + through properties), e.g. BACKUP_CHANNEL --project= + --location=. 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 backup_channel 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. + + BACKUP_CHANNEL + ID of the backup channel or fully qualified identifier for the backup + channel. + + To set the backup_channel attribute: + ▸ provide the argument backup_channel on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + Google Cloud location. + + To set the location attribute: + ▸ provide the argument backup_channel on the command line with a + fully specified name; + ▸ provide the argument --location on the command line; + ▸ set the property gkebackup/location. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --etag=ETAG + The etag is used for optimistic concurrency control as a way to help + prevent simultaneous updates or deletes of a resource from overwriting + each other. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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 gkebackup/v1 API. The full documentation for this API + can be found at: + https://cloud.google.com/kubernetes-engine/docs/add-on/backup-for-gke + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud beta container backup-restore backup-channels delete + diff --git a/gcloud/alpha/container/backup-restore/backup-channels/describe b/gcloud/alpha/container/backup-restore/backup-channels/describe new file mode 100644 index 000000000..cf3cd5c89 --- /dev/null +++ b/gcloud/alpha/container/backup-restore/backup-channels/describe @@ -0,0 +1,76 @@ +NAME + gcloud alpha container backup-restore backup-channels describe - describe a + backup channel + +SYNOPSIS + gcloud alpha container backup-restore backup-channels describe + (BACKUP_CHANNEL : --location=LOCATION) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Describe a Backup for GKE backup channel. + +EXAMPLES + To describe a backup channel my-backup-channel in project my-project in + location us-central1, run: + + $ gcloud alpha container backup-restore backup-channels describe \ + my-backup-channel --project=my-project --location=us-central1 + +POSITIONAL ARGUMENTS + Backup channel resource - Name of the backup channel to describe. The name + may be provided either as a relative name, e.g. + projects//locations//backupChannels/ or + as a single ID name (with the parent resources provided via options or + through properties), e.g. BACKUP_CHANNEL --project= + --location= 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 backup_channel 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. + + BACKUP_CHANNEL + ID of the backup channel or fully qualified identifier for the backup + channel. + + To set the backup_channel attribute: + ▸ provide the argument backup_channel on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + Google Cloud location. + + To set the location attribute: + ▸ provide the argument backup_channel on the command line with a + fully specified name; + ▸ provide the argument --location on the command line; + ▸ set the property gkebackup/location. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the gkebackup/v1 API. The full documentation for this API + can be found at: + https://cloud.google.com/kubernetes-engine/docs/add-on/backup-for-gke + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud beta container backup-restore backup-channels describe + diff --git a/gcloud/alpha/container/backup-restore/backup-channels/help b/gcloud/alpha/container/backup-restore/backup-channels/help new file mode 100644 index 000000000..ea0cfa5f7 --- /dev/null +++ b/gcloud/alpha/container/backup-restore/backup-channels/help @@ -0,0 +1,42 @@ +NAME + gcloud alpha container backup-restore backup-channels - backup for GKE + Backup Channels + +SYNOPSIS + gcloud alpha container backup-restore backup-channels COMMAND + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Backup for GKE Backup Channels. + +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 backup channel. + + delete + (ALPHA) Delete a backup channel. + + describe + (ALPHA) Describe a backup channel. + + list + (ALPHA) List backup channels. + + update + (ALPHA) Update a backup channel. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud beta container backup-restore backup-channels + diff --git a/gcloud/alpha/container/backup-restore/backup-channels/list b/gcloud/alpha/container/backup-restore/backup-channels/list new file mode 100644 index 000000000..fe016863c --- /dev/null +++ b/gcloud/alpha/container/backup-restore/backup-channels/list @@ -0,0 +1,100 @@ +NAME + gcloud alpha container backup-restore backup-channels list - list backup + channels + +SYNOPSIS + gcloud alpha container backup-restore backup-channels list + [--location=LOCATION] [--filter=EXPRESSION] [--limit=LIMIT] + [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) List Backup for GKE backup channels. + +EXAMPLES + To list all backup channels in project my-project in location us-central1, + run: + + $ gcloud alpha container backup-restore backup-channels list \ + --project=my-project --location=us-central1 + + To list all backup channels in project my-project across all locations, + run: + + $ gcloud alpha container backup-restore backup-channels list \ + --project=my-project + +FLAGS + Location resource - Name of the location from which to list backup + channels (provided via options or through properties): --project= + --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 gkebackup/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; + ▸ set the property gkebackup/location. + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + + --uri + Print a list of resource URIs instead of the default output, and change + the command output to a list of URIs. If this flag is used with + --format, the formatting is applied on this URI list. To display URIs + alongside other keys instead, use the uri() transform. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the gkebackup/v1 API. The full documentation for this API + can be found at: + https://cloud.google.com/kubernetes-engine/docs/add-on/backup-for-gke + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud beta container backup-restore backup-channels list + diff --git a/gcloud/alpha/container/backup-restore/backup-channels/update b/gcloud/alpha/container/backup-restore/backup-channels/update new file mode 100644 index 000000000..5e91c963e --- /dev/null +++ b/gcloud/alpha/container/backup-restore/backup-channels/update @@ -0,0 +1,123 @@ +NAME + gcloud alpha container backup-restore backup-channels update - update a + backup channel + +SYNOPSIS + gcloud alpha container backup-restore backup-channels update + (BACKUP_CHANNEL : --location=LOCATION) [--async] + [--description=DESCRIPTION] [--etag=ETAG] + [--update-labels=[KEY=VALUE,...]] + [--clear-labels | --remove-labels=[KEY,...]] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Update a Backup for GKE backup channel. + +EXAMPLES + To update a backup channel my-backup-channel in project my-project in + location us-central1 to add new description, run: + + $ gcloud alpha container backup-restore backup-channels update \ + my-backup-channel --project=my-project --location=us-central1 \ + --description="New description" + +POSITIONAL ARGUMENTS + Backup channel resource - Name of the backup channel to update. The name + may be provided either as a relative name, e.g. + projects//locations//backupChannels/ or + as a single ID name (with the parent resources provided via options or + through properties), e.g. BACKUP_CHANNEL --project= + --location=. 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 backup_channel 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. + + BACKUP_CHANNEL + ID of the backup channel or fully qualified identifier for the backup + channel. + + To set the backup_channel attribute: + ▸ provide the argument backup_channel on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + Google Cloud location. + + To set the location attribute: + ▸ provide the argument backup_channel on the command line with a + fully specified name; + ▸ provide the argument --location on the command line; + ▸ set the property gkebackup/location. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --description=DESCRIPTION + The description of the backup channel. + + --etag=ETAG + The etag is used for optimistic concurrency control as a way to help + prevent simultaneous updates or deletes of a resource from overwriting + each other. + + --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 container backup-restore backup-channels update \ + --clear-labels + + To remove all existing labels and create two new labels, foo and baz: + + $ gcloud alpha container backup-restore backup-channels 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 gkebackup/v1 API. The full documentation for this API + can be found at: + https://cloud.google.com/kubernetes-engine/docs/add-on/backup-for-gke + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud beta container backup-restore backup-channels update + diff --git a/gcloud/alpha/container/backup-restore/backup-plan-bindings/describe b/gcloud/alpha/container/backup-restore/backup-plan-bindings/describe new file mode 100644 index 000000000..79a27ad8a --- /dev/null +++ b/gcloud/alpha/container/backup-restore/backup-plan-bindings/describe @@ -0,0 +1,90 @@ +NAME + gcloud alpha container backup-restore backup-plan-bindings describe - + describe a backup plan binding + +SYNOPSIS + gcloud alpha container backup-restore backup-plan-bindings describe + (BACKUP_PLAN_BINDING + : --backup-channel=BACKUP_CHANNEL --location=LOCATION) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Describe a Backup for GKE backup plan binding. + +EXAMPLES + To describe a backup plan binding my-backup-plan-binding in project + my-project in location us-central1 under backup channel my-backup-channel, + run: + + $ gcloud alpha container backup-restore backup-plan-bindings \ + describe my-backup-plan-binding \ + --backup-channel=my-backup-channel --project=my-project \ + --location=us-central1 + +POSITIONAL ARGUMENTS + Backup plan binding resource - Name of the backup plan binding to + describe. The name may be provided either as a relative name, e.g. + projects//locations//backupChannels//backupPlanBindings/ + or as a single ID name (with the parent resources provided via options or + through properties), e.g. BACKUP_PLAN_BINDING --project= + --location= --backup-channel=. 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 backup_plan_binding 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. + + BACKUP_PLAN_BINDING + ID of the backup plan binding or fully qualified identifier for the + backup plan binding. + + To set the backup_plan_binding attribute: + ▸ provide the argument backup_plan_binding on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --backup-channel=BACKUP_CHANNEL + Backup Channel name. + + To set the backup-channel attribute: + ▸ provide the argument backup_plan_binding on the command line with + a fully specified name; + ▸ provide the argument --backup-channel on the command line. + + --location=LOCATION + Google Cloud location. + + To set the location attribute: + ▸ provide the argument backup_plan_binding on the command line with + a fully specified name; + ▸ provide the argument --location on the command line; + ▸ set the property gkebackup/location. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the gkebackup/v1 API. The full documentation for this API + can be found at: + https://cloud.google.com/kubernetes-engine/docs/add-on/backup-for-gke + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud beta container backup-restore backup-plan-bindings describe + diff --git a/gcloud/alpha/container/backup-restore/backup-plan-bindings/help b/gcloud/alpha/container/backup-restore/backup-plan-bindings/help new file mode 100644 index 000000000..b838cef41 --- /dev/null +++ b/gcloud/alpha/container/backup-restore/backup-plan-bindings/help @@ -0,0 +1,33 @@ +NAME + gcloud alpha container backup-restore backup-plan-bindings - backup for GKE + Backup Plan Bindings + +SYNOPSIS + gcloud alpha container backup-restore backup-plan-bindings COMMAND + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Backup for GKE Backup Plan Bindings. + +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 a backup plan binding. + + list + (ALPHA) List backup plan bindings. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud beta container backup-restore backup-plan-bindings + diff --git a/gcloud/alpha/container/backup-restore/backup-plan-bindings/list b/gcloud/alpha/container/backup-restore/backup-plan-bindings/list new file mode 100644 index 000000000..2648c7b24 --- /dev/null +++ b/gcloud/alpha/container/backup-restore/backup-plan-bindings/list @@ -0,0 +1,115 @@ +NAME + gcloud alpha container backup-restore backup-plan-bindings list - list + backup plan bindings + +SYNOPSIS + gcloud alpha container backup-restore backup-plan-bindings list + (--backup-channel=BACKUP_CHANNEL : --location=LOCATION) + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) List Backup Plan Bindings for GKE backup plan bindings. + +EXAMPLES + To list all backup plan bindings in project my-project in location + us-central1 under backup channel my-backup-channel, run: + + $ gcloud alpha container backup-restore backup-plan-bindings list \ + --backup-channel=my-backup-channel --project=my-project \ + --location=us-central1 + + To list all backup plan bindings in project my-project across all locations + under all backup channels, run: + + $ gcloud alpha container backup-restore backup-plan-bindings list \ + --project=my-project + +REQUIRED FLAGS + Backup channel resource - Name of the backup channel from which to list + backup plan bindings (provided via options or through properties), e.g. + --project= --location= + --backup-channel=. 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 --backup-channel 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. + + --backup-channel=BACKUP_CHANNEL + ID of the backup channel or fully qualified identifier for the backup + channel. + + To set the backup-channel attribute: + ▸ provide the argument --backup-channel on the command line. + + This flag argument must be specified if any of the other arguments in + this group are specified. + + --location=LOCATION + Google Cloud location. + + To set the location attribute: + ▸ provide the argument --backup-channel on the command line with a + fully specified name; + ▸ provide the argument --location on the command line; + ▸ set the property gkebackup/location. + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + + --uri + Print a list of resource URIs instead of the default output, and change + the command output to a list of URIs. If this flag is used with + --format, the formatting is applied on this URI list. To display URIs + alongside other keys instead, use the uri() transform. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the gkebackup/v1 API. The full documentation for this API + can be found at: + https://cloud.google.com/kubernetes-engine/docs/add-on/backup-for-gke + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud beta container backup-restore backup-plan-bindings list + diff --git a/gcloud/alpha/container/backup-restore/help b/gcloud/alpha/container/backup-restore/help index 6796d818b..1c8b96ab6 100644 --- a/gcloud/alpha/container/backup-restore/help +++ b/gcloud/alpha/container/backup-restore/help @@ -15,6 +15,12 @@ GCLOUD WIDE FLAGS GROUPS GROUP is one of the following: + backup-channels + (ALPHA) Backup for GKE Backup Channels. + + backup-plan-bindings + (ALPHA) Backup for GKE Backup Plan Bindings. + backup-plans (ALPHA) Backup for GKE Backup Plans. @@ -27,6 +33,12 @@ GROUPS operations (ALPHA) Backup for GKE Operations. + restore-channels + (ALPHA) Backup for GKE Restore Channels. + + restore-plan-bindings + (ALPHA) Backup for GKE Restore Plan Bindings. + restore-plans (ALPHA) Backup for GKE Restore Plans. diff --git a/gcloud/alpha/container/backup-restore/restore-channels/create b/gcloud/alpha/container/backup-restore/restore-channels/create new file mode 100644 index 000000000..e5340fe02 --- /dev/null +++ b/gcloud/alpha/container/backup-restore/restore-channels/create @@ -0,0 +1,104 @@ +NAME + gcloud alpha container backup-restore restore-channels create - create a + restore channel + +SYNOPSIS + gcloud alpha container backup-restore restore-channels create + (RESTORE_CHANNEL : --location=LOCATION) + --destination-project=DESTINATION_PROJECT [--async] + [--description=DESCRIPTION] [--labels=[KEY=VALUE,...]] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Create a Backup for GKE restore channel. + +EXAMPLES + To create a restore channel my-restore-channel in project my-project in + location us-central1 with destination project projects/1234567890, run: + + $ gcloud alpha container backup-restore restore-channels create \ + my-restore-channel --project=my-project --location=us-central1 \ + --destination_project=projects/1234567890 + +POSITIONAL ARGUMENTS + Restore channel resource - Name of the restore channel to create. Once the + channel is created, this name can't be changed. This must be 63 or fewer + characters long and must be unique within the project and location. The + name may be provided either as a relative name, e.g. + projects//locations//restoreChannels/ + or as a single ID name (with the parent resources provided via options or + through properties), e.g. RESTORE_CHANNEL --project= + --location=. 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 restore_channel 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. + + RESTORE_CHANNEL + ID of the restore channel or fully qualified identifier for the + restore channel. + + To set the restore_channel attribute: + ▸ provide the argument restore_channel on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + Google Cloud location. + + To set the location attribute: + ▸ provide the argument restore_channel on the command line with a + fully specified name; + ▸ provide the argument --location on the command line; + ▸ set the property gkebackup/location. + +REQUIRED FLAGS + --destination-project=DESTINATION_PROJECT + The project where Restores are allowed to be created. The format is + projects/{project}. Currently, {project} can only be the project + number. e.g. projects/1234567890. + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --description=DESCRIPTION + The description of the restore channel. + + --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 gkebackup/v1 API. The full documentation for this API + can be found at: + https://cloud.google.com/kubernetes-engine/docs/add-on/backup-for-gke + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud beta container backup-restore restore-channels create + diff --git a/gcloud/alpha/container/backup-restore/restore-channels/delete b/gcloud/alpha/container/backup-restore/restore-channels/delete new file mode 100644 index 000000000..4a94edeeb --- /dev/null +++ b/gcloud/alpha/container/backup-restore/restore-channels/delete @@ -0,0 +1,87 @@ +NAME + gcloud alpha container backup-restore restore-channels delete - delete a + restore channel + +SYNOPSIS + gcloud alpha container backup-restore restore-channels delete + (RESTORE_CHANNEL : --location=LOCATION) [--async] [--etag=ETAG] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Delete a Backup for GKE restore channel. + +EXAMPLES + To delete a restore channel my-restore-channel in project my-project in + location us-central1, run: + + $ gcloud alpha container backup-restore restore-channels delete \ + my-restore-channel --project=my-project --location=us-central1 + +POSITIONAL ARGUMENTS + Restore channel resource - Name of the restore channel to delete. The name + may be provided either as a relative name, e.g. + projects//locations//restoreChannels/ + or as a single ID name (with the parent resources provided via options or + through properties), e.g. RESTORE_CHANNEL --project= + --location=. 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 restore_channel 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. + + RESTORE_CHANNEL + ID of the restore channel or fully qualified identifier for the + restore channel. + + To set the restore_channel attribute: + ▸ provide the argument restore_channel on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + Google Cloud location. + + To set the location attribute: + ▸ provide the argument restore_channel on the command line with a + fully specified name; + ▸ provide the argument --location on the command line; + ▸ set the property gkebackup/location. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --etag=ETAG + The etag is used for optimistic concurrency control as a way to help + prevent simultaneous updates or deletes of a resource from overwriting + each other. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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 gkebackup/v1 API. The full documentation for this API + can be found at: + https://cloud.google.com/kubernetes-engine/docs/add-on/backup-for-gke + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud beta container backup-restore restore-channels delete + diff --git a/gcloud/alpha/container/backup-restore/restore-channels/describe b/gcloud/alpha/container/backup-restore/restore-channels/describe new file mode 100644 index 000000000..1cc63e683 --- /dev/null +++ b/gcloud/alpha/container/backup-restore/restore-channels/describe @@ -0,0 +1,76 @@ +NAME + gcloud alpha container backup-restore restore-channels describe - describe + a restore channel + +SYNOPSIS + gcloud alpha container backup-restore restore-channels describe + (RESTORE_CHANNEL : --location=LOCATION) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Describe a Backup for GKE restore channel. + +EXAMPLES + To describe a restore channel my-restore-channel in project my-project in + location us-central1, run: + + $ gcloud alpha container backup-restore restore-channels describe \ + my-restore-channel --project=my-project --location=us-central1 + +POSITIONAL ARGUMENTS + Restore channel resource - Name of the restore channel to describe. The + name may be provided either as a relative name, e.g. + projects//locations//restoreChannels/ + or as a single ID name (with the parent resources provided via options or + through properties), e.g. RESTORE_CHANNEL --project= + --location= 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 restore_channel 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. + + RESTORE_CHANNEL + ID of the restore channel or fully qualified identifier for the + restore channel. + + To set the restore_channel attribute: + ▸ provide the argument restore_channel on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + Google Cloud location. + + To set the location attribute: + ▸ provide the argument restore_channel on the command line with a + fully specified name; + ▸ provide the argument --location on the command line; + ▸ set the property gkebackup/location. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the gkebackup/v1 API. The full documentation for this API + can be found at: + https://cloud.google.com/kubernetes-engine/docs/add-on/backup-for-gke + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud beta container backup-restore restore-channels describe + diff --git a/gcloud/alpha/container/backup-restore/restore-channels/help b/gcloud/alpha/container/backup-restore/restore-channels/help new file mode 100644 index 000000000..57d73a50f --- /dev/null +++ b/gcloud/alpha/container/backup-restore/restore-channels/help @@ -0,0 +1,42 @@ +NAME + gcloud alpha container backup-restore restore-channels - backup for GKE + Restore Channels + +SYNOPSIS + gcloud alpha container backup-restore restore-channels COMMAND + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Backup for GKE Restore Channels. + +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 restore channel. + + delete + (ALPHA) Delete a restore channel. + + describe + (ALPHA) Describe a restore channel. + + list + (ALPHA) List restore channels. + + update + (ALPHA) Update a restore channel. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud beta container backup-restore restore-channels + diff --git a/gcloud/alpha/container/backup-restore/restore-channels/list b/gcloud/alpha/container/backup-restore/restore-channels/list new file mode 100644 index 000000000..2141abf6c --- /dev/null +++ b/gcloud/alpha/container/backup-restore/restore-channels/list @@ -0,0 +1,100 @@ +NAME + gcloud alpha container backup-restore restore-channels list - list restore + channels + +SYNOPSIS + gcloud alpha container backup-restore restore-channels list + [--location=LOCATION] [--filter=EXPRESSION] [--limit=LIMIT] + [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) List Backup for GKE restore channels. + +EXAMPLES + To list all restore channels in project my-project in location us-central1, + run: + + $ gcloud alpha container backup-restore restore-channels list \ + --project=my-project --location=us-central1 + + To list all restore channels in project my-project across all locations, + run: + + $ gcloud alpha container backup-restore restore-channels list \ + --project=my-project + +FLAGS + Location resource - Name of the location from which to list restore + channels (provided via options or through properties): --project= + --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 gkebackup/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; + ▸ set the property gkebackup/location. + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + + --uri + Print a list of resource URIs instead of the default output, and change + the command output to a list of URIs. If this flag is used with + --format, the formatting is applied on this URI list. To display URIs + alongside other keys instead, use the uri() transform. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the gkebackup/v1 API. The full documentation for this API + can be found at: + https://cloud.google.com/kubernetes-engine/docs/add-on/backup-for-gke + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud beta container backup-restore restore-channels list + diff --git a/gcloud/alpha/container/backup-restore/restore-channels/update b/gcloud/alpha/container/backup-restore/restore-channels/update new file mode 100644 index 000000000..ef8e9a178 --- /dev/null +++ b/gcloud/alpha/container/backup-restore/restore-channels/update @@ -0,0 +1,123 @@ +NAME + gcloud alpha container backup-restore restore-channels update - update a + restore channel + +SYNOPSIS + gcloud alpha container backup-restore restore-channels update + (RESTORE_CHANNEL : --location=LOCATION) [--async] + [--description=DESCRIPTION] [--etag=ETAG] + [--update-labels=[KEY=VALUE,...]] + [--clear-labels | --remove-labels=[KEY,...]] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Update a Backup for GKE restore channel. + +EXAMPLES + To update a restore channel my-restore-channel in project my-project in + location us-central1 to add new description, run: + + $ gcloud alpha container backup-restore restore-channels update \ + my-restore-channel --project=my-project --location=us-central1 \ + --description="New description" + +POSITIONAL ARGUMENTS + Restore channel resource - Name of the restore channel to update. The name + may be provided either as a relative name, e.g. + projects//locations//restoreChannels/ + or as a single ID name (with the parent resources provided via options or + through properties), e.g. RESTORE_CHANNEL --project= + --location=. 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 restore_channel 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. + + RESTORE_CHANNEL + ID of the restore channel or fully qualified identifier for the + restore channel. + + To set the restore_channel attribute: + ▸ provide the argument restore_channel on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + Google Cloud location. + + To set the location attribute: + ▸ provide the argument restore_channel on the command line with a + fully specified name; + ▸ provide the argument --location on the command line; + ▸ set the property gkebackup/location. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --description=DESCRIPTION + The description of the restore channel. + + --etag=ETAG + The etag is used for optimistic concurrency control as a way to help + prevent simultaneous updates or deletes of a resource from overwriting + each other. + + --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 container backup-restore restore-channels update \ + --clear-labels + + To remove all existing labels and create two new labels, foo and baz: + + $ gcloud alpha container backup-restore restore-channels 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 gkebackup/v1 API. The full documentation for this API + can be found at: + https://cloud.google.com/kubernetes-engine/docs/add-on/backup-for-gke + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud beta container backup-restore restore-channels update + diff --git a/gcloud/alpha/container/backup-restore/restore-plan-bindings/describe b/gcloud/alpha/container/backup-restore/restore-plan-bindings/describe new file mode 100644 index 000000000..10439b943 --- /dev/null +++ b/gcloud/alpha/container/backup-restore/restore-plan-bindings/describe @@ -0,0 +1,90 @@ +NAME + gcloud alpha container backup-restore restore-plan-bindings describe - + describe a restore plan binding + +SYNOPSIS + gcloud alpha container backup-restore restore-plan-bindings describe + (RESTORE_PLAN_BINDING + : --location=LOCATION --restore-channel=RESTORE_CHANNEL) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Describe a Backup for GKE restore plan binding. + +EXAMPLES + To describe a restore plan binding my-restore-plan-binding in project + my-project in location us-central1 under restore channel + my-restore-channel, run: + + $ gcloud alpha container backup-restore restore-plan-bindings \ + describe my-restore-plan-binding \ + --restore-channel=my-restore-channel --project=my-project \ + --location=us-central1 + +POSITIONAL ARGUMENTS + Restore plan binding resource - Name of the restore plan binding to + describe. The name may be provided either as a relative name, e.g. + projects//locations//restoreChannels//restorePlanBindings/ + or as a single ID name (with the parent resources provided via options or + through properties), e.g. RESTORE_PLAN_BINDING --project= + --location= --restore-channel=. 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 restore_plan_binding 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. + + RESTORE_PLAN_BINDING + ID of the restore plan binding or fully qualified identifier for the + restore plan binding. + + To set the restore_plan_binding attribute: + ▸ provide the argument restore_plan_binding on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + Google Cloud location. + + To set the location attribute: + ▸ provide the argument restore_plan_binding on the command line + with a fully specified name; + ▸ provide the argument --location on the command line; + ▸ set the property gkebackup/location. + + --restore-channel=RESTORE_CHANNEL + Restore Channel name. + + To set the restore-channel attribute: + ▸ provide the argument restore_plan_binding on the command line + with a fully specified name; + ▸ provide the argument --restore-channel 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 gkebackup/v1 API. The full documentation for this API + can be found at: + https://cloud.google.com/kubernetes-engine/docs/add-on/backup-for-gke + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud beta container backup-restore restore-plan-bindings describe + diff --git a/gcloud/alpha/container/backup-restore/restore-plan-bindings/help b/gcloud/alpha/container/backup-restore/restore-plan-bindings/help new file mode 100644 index 000000000..4477069c7 --- /dev/null +++ b/gcloud/alpha/container/backup-restore/restore-plan-bindings/help @@ -0,0 +1,33 @@ +NAME + gcloud alpha container backup-restore restore-plan-bindings - backup for + GKE Restore Plan Bindings + +SYNOPSIS + gcloud alpha container backup-restore restore-plan-bindings COMMAND + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Backup for GKE Restore Plan Bindings. + +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 a restore plan binding. + + list + (ALPHA) List restore plan bindings. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud beta container backup-restore restore-plan-bindings + diff --git a/gcloud/alpha/container/backup-restore/restore-plan-bindings/list b/gcloud/alpha/container/backup-restore/restore-plan-bindings/list new file mode 100644 index 000000000..db635bdb8 --- /dev/null +++ b/gcloud/alpha/container/backup-restore/restore-plan-bindings/list @@ -0,0 +1,115 @@ +NAME + gcloud alpha container backup-restore restore-plan-bindings list - list + restore plan bindings + +SYNOPSIS + gcloud alpha container backup-restore restore-plan-bindings list + (--restore-channel=RESTORE_CHANNEL : --location=LOCATION) + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) List Restore Plan Bindings for GKE restore plan bindings. + +EXAMPLES + To list all restore plan bindings in project my-project in location + us-central1 under restore channel my-restore-channel, run: + + $ gcloud alpha container backup-restore restore-plan-bindings list \ + --restore-channel=my-restore-channel --project=my-project \ + --location=us-central1 + + To list all restore plan bindings in project my-project across all + locations under all restore channels, run: + + $ gcloud alpha container backup-restore restore-plan-bindings list \ + --project=my-project + +REQUIRED FLAGS + Restore channel resource - Name of the restore channel from which to list + restore plan bindings (provided via options or through properties), e.g. + --project= --location= + --restore-channel=. 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 --restore-channel 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. + + --restore-channel=RESTORE_CHANNEL + ID of the restore channel or fully qualified identifier for the + restore channel. + + To set the restore-channel attribute: + ▸ provide the argument --restore-channel on the command line. + + This flag argument must be specified if any of the other arguments in + this group are specified. + + --location=LOCATION + Google Cloud location. + + To set the location attribute: + ▸ provide the argument --restore-channel on the command line with a + fully specified name; + ▸ provide the argument --location on the command line; + ▸ set the property gkebackup/location. + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + + --uri + Print a list of resource URIs instead of the default output, and change + the command output to a list of URIs. If this flag is used with + --format, the formatting is applied on this URI list. To display URIs + alongside other keys instead, use the uri() transform. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the gkebackup/v1 API. The full documentation for this API + can be found at: + https://cloud.google.com/kubernetes-engine/docs/add-on/backup-for-gke + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud beta container backup-restore restore-plan-bindings list + diff --git a/gcloud/alpha/container/clusters/create b/gcloud/alpha/container/clusters/create index a7735787a..50664f975 100644 --- a/gcloud/alpha/container/clusters/create +++ b/gcloud/alpha/container/clusters/create @@ -46,9 +46,9 @@ SYNOPSIS [--enable-master-global-access] [--enable-multi-networking] [--enable-nested-virtualization] [--enable-network-policy] [--enable-pod-security-policy] [--enable-ray-cluster-logging] - [--enable-ray-cluster-monitoring] [--enable-secret-manager] - [--enable-service-externalips] [--enable-shielded-nodes] - [--enable-stackdriver-kubernetes] [--enable-vertical-pod-autoscaling] + [--enable-ray-cluster-monitoring] [--enable-service-externalips] + [--enable-shielded-nodes] [--enable-stackdriver-kubernetes] + [--enable-vertical-pod-autoscaling] [--fleet-project=PROJECT_ID_OR_NUMBER] [--gateway-api=GATEWAY_API] [--hpa-profile=HPA_PROFILE] [--identity-provider=IDENTITY_PROVIDER] [--image-type=IMAGE_TYPE] @@ -133,6 +133,8 @@ SYNOPSIS --resource-usage-bigquery-dataset=RESOURCE_USAGE_BIGQUERY_DATASET] [--enable-private-endpoint --enable-private-nodes --master-ipv4-cidr=MASTER_IPV4_CIDR --private-cluster] + [--enable-secret-manager --enable-secret-manager-rotation + --secret-manager-rotation-interval=SECRET_MANAGER_ROTATION_INTERVAL] [--enable-tpu --enable-tpu-service-networking | --tpu-ipv4-cidr=CIDR] [--ephemeral-storage[=[local-ssd-count=LOCAL-SSD-COUNT]] | --ephemeral-storage-local-ssd[=[count=COUNT]] @@ -719,16 +721,6 @@ FLAGS --enable-ray-cluster-monitoring Enable automatic metrics collection for Ray clusters. - Flags for Secret Manager configuration: - - --enable-secret-manager - Enables the Secret Manager CSI driver provider component. See - https://secrets-store-csi-driver.sigs.k8s.io/introduction - https://github.com/GoogleCloudPlatform/secrets-store-csi-driver-provider-gcp - - To disable in an existing cluster, explicitly set flag to - --no-enable-secret-manager - --enable-service-externalips Enables use of services with externalIPs field. @@ -2144,6 +2136,27 @@ FLAGS The --private-cluster flag is deprecated and will be removed in a future release. Use --enable-private-nodes instead. + Flags for Secret Manager configuration: + + --enable-secret-manager + Enables the Secret Manager CSI driver provider component. See + https://secrets-store-csi-driver.sigs.k8s.io/introduction + https://github.com/GoogleCloudPlatform/secrets-store-csi-driver-provider-gcp + + To disable in an existing cluster, explicitly set flag to + --no-enable-secret-manager + + --enable-secret-manager-rotation + Enables the rotation of secrets in the Secret Manager CSI driver + provider component. + + To disable in an existing cluster, explicitly set flag to + --no-enable-secret-manager-rotation + + --secret-manager-rotation-interval=SECRET_MANAGER_ROTATION_INTERVAL + Set the rotation period for secrets in the Secret Manager CSI driver + provider component. + Flags relating to Cloud TPUs: --enable-tpu diff --git a/gcloud/alpha/container/clusters/create-auto b/gcloud/alpha/container/clusters/create-auto index c67d7d4b7..7c8399677 100644 --- a/gcloud/alpha/container/clusters/create-auto +++ b/gcloud/alpha/container/clusters/create-auto @@ -22,15 +22,14 @@ SYNOPSIS [--enable-ip-access] [--enable-kubernetes-unstable-apis=API,[API,...]] [--enable-master-global-access] [--enable-multi-networking] [--enable-ray-cluster-logging] [--enable-ray-cluster-monitoring] - [--enable-ray-operator] [--enable-secret-manager] - [--fleet-project=PROJECT_ID_OR_NUMBER] [--hpa-profile=HPA_PROFILE] - [--labels=[KEY=VALUE,...]] [--logging=[COMPONENT,...]] - [--monitoring=[COMPONENT,...]] [--network=NETWORK] - [--private-endpoint-subnetwork=NAME] [--release-channel=[CHANNEL]] - [--security-group=SECURITY_GROUP] [--security-posture=SECURITY_POSTURE] - [--services-ipv4-cidr=CIDR] [--services-secondary-range-name=NAME] - [--subnetwork=SUBNETWORK] [--tier=TIER] - [--workload-policies=WORKLOAD_POLICIES] + [--enable-ray-operator] [--fleet-project=PROJECT_ID_OR_NUMBER] + [--hpa-profile=HPA_PROFILE] [--labels=[KEY=VALUE,...]] + [--logging=[COMPONENT,...]] [--monitoring=[COMPONENT,...]] + [--network=NETWORK] [--private-endpoint-subnetwork=NAME] + [--release-channel=[CHANNEL]] [--security-group=SECURITY_GROUP] + [--security-posture=SECURITY_POSTURE] [--services-ipv4-cidr=CIDR] + [--services-secondary-range-name=NAME] [--subnetwork=SUBNETWORK] + [--tier=TIER] [--workload-policies=WORKLOAD_POLICIES] [--workload-vulnerability-scanning=WORKLOAD_VULNERABILITY_SCANNING] [--additive-vpc-scope-dns-domain=ADDITIVE_VPC_SCOPE_DNS_DOMAIN | --disable-additive-vpc-scope] @@ -51,6 +50,8 @@ SYNOPSIS --master-authorized-networks=NETWORK,[NETWORK,...]] [--enable-private-endpoint --enable-private-nodes --master-ipv4-cidr=MASTER_IPV4_CIDR] + [--enable-secret-manager --enable-secret-manager-rotation + --secret-manager-rotation-interval=SECRET_MANAGER_ROTATION_INTERVAL] [--location=LOCATION | --region=REGION | --zone=ZONE, -z ZONE] [--scopes=[SCOPE,...]; default="gke-default" --service-account=SERVICE_ACCOUNT] @@ -296,16 +297,6 @@ FLAGS --enable-ray-operator Enable the Ray Operator GKE add-on. This add-on is disabled by default. - Flags for Secret Manager configuration: - - --enable-secret-manager - Enables the Secret Manager CSI driver provider component. See - https://secrets-store-csi-driver.sigs.k8s.io/introduction - https://github.com/GoogleCloudPlatform/secrets-store-csi-driver-provider-gcp - - To disable in an existing cluster, explicitly set flag to - --no-enable-secret-manager - --fleet-project=PROJECT_ID_OR_NUMBER Sets fleet host project for the cluster. If specified, the current cluster will be registered as a fleet membership under the fleet host @@ -660,6 +651,27 @@ FLAGS netmask of size /28 and should be used in conjunction with the --enable-private-nodes flag. + Flags for Secret Manager configuration: + + --enable-secret-manager + Enables the Secret Manager CSI driver provider component. See + https://secrets-store-csi-driver.sigs.k8s.io/introduction + https://github.com/GoogleCloudPlatform/secrets-store-csi-driver-provider-gcp + + To disable in an existing cluster, explicitly set flag to + --no-enable-secret-manager + + --enable-secret-manager-rotation + Enables the rotation of secrets in the Secret Manager CSI driver + provider component. + + To disable in an existing cluster, explicitly set flag to + --no-enable-secret-manager-rotation + + --secret-manager-rotation-interval=SECRET_MANAGER_ROTATION_INTERVAL + Set the rotation period for secrets in the Secret Manager CSI driver + provider component. + At most one of these can be specified: --location=LOCATION diff --git a/gcloud/alpha/container/clusters/get-upgrade-info b/gcloud/alpha/container/clusters/get-upgrade-info index e48213cda..951cd943b 100644 --- a/gcloud/alpha/container/clusters/get-upgrade-info +++ b/gcloud/alpha/container/clusters/get-upgrade-info @@ -52,7 +52,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud container clusters get-upgrade-info $ gcloud beta container clusters get-upgrade-info diff --git a/gcloud/alpha/container/clusters/update b/gcloud/alpha/container/clusters/update index a475b61fc..1b55c6a0a 100644 --- a/gcloud/alpha/container/clusters/update +++ b/gcloud/alpha/container/clusters/update @@ -27,9 +27,9 @@ SYNOPSIS | --enable-logging-monitoring-system-only | --enable-multi-networking | --enable-network-policy | --enable-pod-security-policy | --enable-private-nodes | --[no-]enable-ray-cluster-logging - | --[no-]enable-ray-cluster-monitoring | --enable-secret-manager - | --enable-service-externalips | --enable-shielded-nodes - | --enable-stackdriver-kubernetes | --enable-vertical-pod-autoscaling + | --[no-]enable-ray-cluster-monitoring | --enable-service-externalips + | --enable-shielded-nodes | --enable-stackdriver-kubernetes + | --enable-vertical-pod-autoscaling | --fleet-project=PROJECT_ID_OR_NUMBER | --gateway-api=GATEWAY_API | --generate-password | --hpa-profile=HPA_PROFILE | --identity-provider=IDENTITY_PROVIDER @@ -108,6 +108,8 @@ SYNOPSIS : --min-accelerator=[type=TYPE,count=COUNT,...]]] | --enable-insecure-binding-system-authenticated --enable-insecure-binding-system-unauthenticated + | --enable-secret-manager --enable-secret-manager-rotation + --secret-manager-rotation-interval=SECRET_MANAGER_ROTATION_INTERVAL | --enable-tpu --enable-tpu-service-networking | --tpu-ipv4-cidr=CIDR | --logging-service=LOGGING_SERVICE --monitoring-service=MONITORING_SERVICE @@ -461,16 +463,6 @@ REQUIRED FLAGS --enable-ray-cluster-monitoring to enable and --no-enable-ray-cluster-monitoring to disable. - Flags for Secret Manager configuration: - - --enable-secret-manager - Enables the Secret Manager CSI driver provider component. See - https://secrets-store-csi-driver.sigs.k8s.io/introduction - https://github.com/GoogleCloudPlatform/secrets-store-csi-driver-provider-gcp - - To disable in an existing cluster, explicitly set flag to - --no-enable-secret-manager - --enable-service-externalips Enables use of services with externalIPs field. @@ -1521,6 +1513,27 @@ REQUIRED FLAGS To disallow binding system:authenticated in a cluster, explicitly set the --no-enable-insecure-binding-system-unauthenticated flag instead. + Flags for Secret Manager configuration: + + --enable-secret-manager + Enables the Secret Manager CSI driver provider component. See + https://secrets-store-csi-driver.sigs.k8s.io/introduction + https://github.com/GoogleCloudPlatform/secrets-store-csi-driver-provider-gcp + + To disable in an existing cluster, explicitly set flag to + --no-enable-secret-manager + + --enable-secret-manager-rotation + Enables the rotation of secrets in the Secret Manager CSI driver + provider component. + + To disable in an existing cluster, explicitly set flag to + --no-enable-secret-manager-rotation + + --secret-manager-rotation-interval=SECRET_MANAGER_ROTATION_INTERVAL + Set the rotation period for secrets in the Secret Manager CSI + driver provider component. + Flags relating to Cloud TPUs: --enable-tpu diff --git a/gcloud/alpha/container/node-pools/create b/gcloud/alpha/container/node-pools/create index b312e1388..5f8863eb2 100644 --- a/gcloud/alpha/container/node-pools/create +++ b/gcloud/alpha/container/node-pools/create @@ -42,9 +42,12 @@ SYNOPSIS [--node-locations=ZONE,[ZONE,...]] [--node-pool-soak-duration=NODE_POOL_SOAK_DURATION] [--node-taints=[NODE_TAINT,...]] [--node-version=NODE_VERSION] - [--num-nodes=NUM_NODES] [--placement-policy=PLACEMENT_POLICY] - [--placement-type=PLACEMENT_TYPE] [--preemptible] - [--resource-manager-tags=[KEY=VALUE,...]] [--sandbox=[type=TYPE]] + [--num-nodes=NUM_NODES] + [--opportunistic-maintenance=[node-idle-time=NODE_IDLE_TIME, + window=WINDOW,min-nodes=MIN_NODES,...]] + [--placement-policy=PLACEMENT_POLICY] [--placement-type=PLACEMENT_TYPE] + [--preemptible] [--resource-manager-tags=[KEY=VALUE,...]] + [--sandbox=[type=TYPE]] [--secondary-boot-disk=[disk-image=DISK_IMAGE,[mode=MODE],...]] [--shielded-integrity-monitoring] [--shielded-secure-boot] [--sole-tenant-node-affinity-file=SOLE_TENANT_NODE_AFFINITY_FILE] @@ -576,6 +579,26 @@ FLAGS types the number of nodes will be defaulted to (product of topology)/(# of chips per VM). + --opportunistic-maintenance=[node-idle-time=NODE_IDLE_TIME,window=WINDOW,min-nodes=MIN_NODES,...] + Opportunistic maintenance options. + + node-idle-time: Time to be spent waiting for node to be idle before + starting maintenance, ending with 's'. Example: "3.5s" + + window: The window of time that opportunistic maintenance can run, + ending with 's'. Example: A setting of 14 days (1209600s) implies that + opportunistic maintenance can only be ran in the 2 weeks leading up to + the scheduled maintenance date. Setting 28 days(2419200s) allows + opportunistic maintenance to run at any time in the scheduled + maintenance window. + + min-nodes: Minimum number of nodes in the node pool to be available + during the opportunistic triggered maintenance. + + $ gcloud alpha container node-pools create example-cluster \ + --opportunistic-maintenance=node-idle-time=600s,window=600s,\ + min-nodes=2 + --placement-policy=PLACEMENT_POLICY Indicates the desired resource policy to use. diff --git a/gcloud/alpha/container/node-pools/get-upgrade-info b/gcloud/alpha/container/node-pools/get-upgrade-info index 954341922..7a472e98c 100644 --- a/gcloud/alpha/container/node-pools/get-upgrade-info +++ b/gcloud/alpha/container/node-pools/get-upgrade-info @@ -1,7 +1,6 @@ NAME - gcloud alpha container node-pools get-upgrade-info - get information about - upgrades for existing clusters including auto upgrade status, upgrade - history, upgrade targets, and end of support timelines + gcloud alpha container node-pools get-upgrade-info - get upgrade + information for an existing node pool for a cluster SYNOPSIS gcloud alpha container node-pools get-upgrade-info NAME [--cluster=CLUSTER] @@ -9,9 +8,9 @@ SYNOPSIS [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) Get information about upgrades for existing clusters including auto - upgrade status, upgrade history, upgrade targets, and end of support - timelines. + (ALPHA) gcloud alpha container node-pools get-upgrade-info displays all + upgrade information associated with the node pool in the Google Kubernetes + Engine cluster. EXAMPLES To get upgrade information for a node pool of an existing cluster, run: @@ -57,7 +56,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud container node-pools get-upgrade-info $ gcloud beta container node-pools get-upgrade-info diff --git a/gcloud/alpha/container/node-pools/help b/gcloud/alpha/container/node-pools/help index d50770cf6..e90bf441e 100644 --- a/gcloud/alpha/container/node-pools/help +++ b/gcloud/alpha/container/node-pools/help @@ -56,9 +56,8 @@ COMMANDS (ALPHA) Describe an existing node pool for a cluster. get-upgrade-info - (ALPHA) Get information about upgrades for existing clusters including - auto upgrade status, upgrade history, upgrade targets, and end of - support timelines. + (ALPHA) Get upgrade information for an existing node pool for a + cluster. list (ALPHA) List existing node pools for a cluster. diff --git a/gcloud/alpha/dataproc/clusters/create b/gcloud/alpha/dataproc/clusters/create index 2399f7546..cd91785be 100644 --- a/gcloud/alpha/dataproc/clusters/create +++ b/gcloud/alpha/dataproc/clusters/create @@ -43,8 +43,7 @@ SYNOPSIS [--secondary-worker-standard-capacity-base=SECONDARY_WORKER_STANDARD_CAPACITY_BASE] [--secondary-worker-standard-capacity-percent-above-base=SECONDARY_WORKER_STANDARD_CAPACITY_PERCENT_ABOVE_BASE] [--shielded-integrity-monitoring] [--shielded-secure-boot] - [--shielded-vtpm] [--stop-max-idle=STOP_MAX_IDLE] - [--temp-bucket=TEMP_BUCKET] + [--shielded-vtpm] [--temp-bucket=TEMP_BUCKET] [--worker-accelerator=[type=TYPE,[count=COUNT],...]] [--worker-boot-disk-provisioned-iops=WORKER_BOOT_DISK_PROVISIONED_IOPS] [--worker-boot-disk-provisioned-throughput=WORKER_BOOT_DISK_PROVISIONED_THROUGHPUT] @@ -78,8 +77,6 @@ SYNOPSIS --num-secondary-workers=NUM_SECONDARY_WORKERS --num-workers=NUM_WORKERS --secondary-worker-type=TYPE; default="preemptible"] - [--stop-expiration-time=STOP_EXPIRATION_TIME - | --stop-max-age=STOP_MAX_AGE] [--worker-machine-type=WORKER_MACHINE_TYPE | --worker-machine-types=type=MACHINE_TYPE[, type=MACHINE_TYPE...][,rank=RANK]] [GCLOUD_WIDE_FLAG ...] @@ -421,11 +418,6 @@ FLAGS security operations, such as remote attestation, encryption, and sealing of keys. - --stop-max-idle=STOP_MAX_IDLE - The duration after the last job completes to auto-stop the cluster, - such as "2h" or "1d". See $ gcloud topic datetimes for information on - duration formats. - --temp-bucket=TEMP_BUCKET The Google Cloud Storage bucket to use by default to store ephemeral cluster and jobs data, such as Spark and MapReduce history files. @@ -950,18 +942,6 @@ FLAGS The type of the secondary worker group. TYPE must be one of: preemptible, non-preemptible, spot. - At most one of these can be specified: - - --stop-expiration-time=STOP_EXPIRATION_TIME - The time when the cluster will be auto-stopped, such as - "2017-08-29T18:52:51.142Z." See $ gcloud topic datetimes for - information on time formats. - - --stop-max-age=STOP_MAX_AGE - The lifespan of the cluster, with auto-stop upon completion, such as - "2h" or "1d". See $ gcloud topic datetimes for information on - duration formats. - At most one of these can be specified: --worker-machine-type=WORKER_MACHINE_TYPE diff --git a/gcloud/alpha/dataproc/clusters/update b/gcloud/alpha/dataproc/clusters/update index 7f4d56dc6..392179dd9 100644 --- a/gcloud/alpha/dataproc/clusters/update +++ b/gcloud/alpha/dataproc/clusters/update @@ -17,11 +17,7 @@ SYNOPSIS | --expiration-time=EXPIRATION_TIME | --max-age=MAX_AGE | --no-max-age] [--delete-max-idle=DELETE_MAX_IDLE | --no-delete-max-idle - | --max-idle=MAX_IDLE | --no-max-idle] - [--stop-expiration-time=STOP_EXPIRATION_TIME - | --stop-max-age=STOP_MAX_AGE | --no-stop-max-age] - [--stop-max-idle=STOP_MAX_IDLE | --no-stop-max-idle] - [GCLOUD_WIDE_FLAG ...] + | --max-idle=MAX_IDLE | --no-max-idle] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Update the number of worker nodes and/or the labels in a cluster. @@ -225,33 +221,6 @@ FLAGS Cancels the cluster auto-deletion by cluster idle duration (configured by --max-idle flag) - At most one of these can be specified: - - --stop-expiration-time=STOP_EXPIRATION_TIME - The time when the cluster will be auto-stopped, such as - "2017-08-29T18:52:51.142Z". See $ gcloud topic datetimes for - information on time formats. - - --stop-max-age=STOP_MAX_AGE - The lifespan of the cluster, with auto-stop upon completion, such as - "2h" or "1d". See $ gcloud topic datetimes for information on - duration formats. - - --no-stop-max-age - Cancels the cluster auto-stop by maximum cluster age (configured by - --stop-max-age or --stop-expiration-time flags) - - At most one of these can be specified: - - --stop-max-idle=STOP_MAX_IDLE - The duration after the last job completes to auto-stop the cluster, - such as "2h" or "1d". See $ gcloud topic datetimes for information on - duration formats. - - --no-stop-max-idle - Cancels the cluster auto-stop by cluster idle duration (configured by - --stop-max-idle flag) - GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, diff --git a/gcloud/alpha/developer-connect/account-connectors/create b/gcloud/alpha/developer-connect/account-connectors/create index dd038ecae..c241c6dd9 100644 --- a/gcloud/alpha/developer-connect/account-connectors/create +++ b/gcloud/alpha/developer-connect/account-connectors/create @@ -21,7 +21,7 @@ EXAMPLES POSITIONAL ARGUMENTS AccountConnector resource - Identifier. The resource name of the - userConnection, in the format + accountConnector, in the format projects/{project}/locations/{location}/accountConnectors/{account_connector_id}. 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 @@ -143,6 +143,8 @@ FLAGS Developer Connect provided OAuth. PROVIDER_OAUTH_CONFIG_SYSTEM_ID must be one of: + datastax + Datastax provider. No scopes are allowed. github GitHub provider. Scopes can be found at https://docs.github.com/en/apps/oauth-apps/building-oauth-apps/scopes-for-oauth-apps#available-scopes @@ -153,6 +155,8 @@ FLAGS Google provider. Recommended scopes: "https://www.googleapis.com/auth/drive.readonly", "https://www.googleapis.com/auth/documents.readonly" + new-relic + New Relic provider. No scopes are allowed. rovo Rovo provider. Must select the "rovo" scope. sentry diff --git a/gcloud/alpha/developer-connect/account-connectors/update b/gcloud/alpha/developer-connect/account-connectors/update index 8af4dc171..565762286 100644 --- a/gcloud/alpha/developer-connect/account-connectors/update +++ b/gcloud/alpha/developer-connect/account-connectors/update @@ -26,7 +26,7 @@ EXAMPLES POSITIONAL ARGUMENTS AccountConnector resource - Identifier. The resource name of the - userConnection, in the format + accountConnector, in the format projects/{project}/locations/{location}/accountConnectors/{account_connector_id}. 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 @@ -60,11 +60,11 @@ POSITIONAL ARGUMENTS FLAGS --[no-]allow-missing - If set to true, and the userConnection is not found a new - userConnection will be created. In this situation update_mask is - ignored. The creation will succeed only if the input userConnection has - all the necessary. Use --allow-missing to enable and --no-allow-missing - to disable. + If set to true, and the accountConnector is not found a new + accountConnector will be created. In this situation update_mask is + ignored. The creation will succeed only if the input accountConnector + has all the necessary. Use --allow-missing to enable and + --no-allow-missing to disable. --async Return immediately, without waiting for the operation in progress to diff --git a/gcloud/alpha/edge-cloud/container/clusters/create b/gcloud/alpha/edge-cloud/container/clusters/create index 3a6337d55..a993c3512 100644 --- a/gcloud/alpha/edge-cloud/container/clusters/create +++ b/gcloud/alpha/edge-cloud/container/clusters/create @@ -15,6 +15,7 @@ SYNOPSIS [--control-plane-node-storage-schema=CONTROL_PLANE_NODE_STORAGE_SCHEMA] [--control-plane-shared-deployment-policy=CONTROL_PLANE_SHARED_DEPLOYMENT_POLICY] [--default-max-pods-per-node=DEFAULT_MAX_PODS_PER_NODE] + [--enable-cluster-isolation=ENABLE_CLUSTER_ISOLATION] [--external-lb-address-pools=EXTERNAL_LB_ADDRESS_POOLS] [--external-lb-ipv4-address-pools=[EXTERNAL_LB_IPV4_ADDRESS,...]] [--external-lb-ipv6-address-pools=[EXTERNAL_LB_IPV6_ADDRESS,...]] @@ -131,6 +132,9 @@ FLAGS --default-max-pods-per-node=DEFAULT_MAX_PODS_PER_NODE The default maximum number of pods per node. + --enable-cluster-isolation=ENABLE_CLUSTER_ISOLATION + If set, the cluster will be created in a secure cluster isolation mode. + --external-lb-address-pools=EXTERNAL_LB_ADDRESS_POOLS Path to a YAML/JSON file containing external load balancer pool configuration. External load balancer pools are used for data plane diff --git a/gcloud/alpha/edge-cloud/container/clusters/update b/gcloud/alpha/edge-cloud/container/clusters/update index 1b43dbf38..a2324c3e4 100644 --- a/gcloud/alpha/edge-cloud/container/clusters/update +++ b/gcloud/alpha/edge-cloud/container/clusters/update @@ -6,6 +6,7 @@ SYNOPSIS gcloud alpha edge-cloud container clusters update (CLUSTER : --location=LOCATION) [--async] [--container-default-runtime-class=CONTAINER_DEFAULT_RUNTIME_CLASS] + [--enable-cluster-isolation=ENABLE_CLUSTER_ISOLATION] [--offline-reboot-ttl=OFFLINE_REBOOT_TTL] [--release-channel=RELEASE_CHANNEL] [--clear-maintenance-window @@ -69,6 +70,10 @@ FLAGS If set, use the specified default container runtime class for the cluster. + --enable-cluster-isolation=ENABLE_CLUSTER_ISOLATION + If set to true, the cluster will be created in a secure cluster + isolation mode. + --offline-reboot-ttl=OFFLINE_REBOOT_TTL Specifies the maximum duration a node can reboot offline (without connection to Google) and then rejoin its cluster to resume its diff --git a/gcloud/alpha/firestore/databases/connection-string b/gcloud/alpha/firestore/databases/connection-string new file mode 100644 index 000000000..4f35ed17c --- /dev/null +++ b/gcloud/alpha/firestore/databases/connection-string @@ -0,0 +1,56 @@ +NAME + gcloud alpha firestore databases connection-string - prints the mongo + connection string for the given Firestore database + +SYNOPSIS + gcloud alpha firestore databases connection-string --database=DATABASE + [--auth=AUTH; default="none"] [GCLOUD_WIDE_FLAG ...] + +EXAMPLES + To get the connection string for a Firestore database with a databaseId + testdb without auth configuration. + + $ gcloud alpha firestore databases connection-string \ + --database=testdb --auth=none + + To get the connection string for a Firestore database with a databaseId + testdb with Google Compute Engine VM auth. + + $ gcloud alpha firestore databases connection-string \ + --database=testdb --auth=gce-vm + +REQUIRED FLAGS + --database=DATABASE + The database to operate on. + + For example, to operate on database foo: + + $ gcloud alpha firestore databases connection-string --database='foo' + +OPTIONAL FLAGS + --auth=AUTH; default="none" + The auth configuration for the connection string. + + If connecting from a Google Compute Engine VM, use gce-vm. For short + term access using the gcloud CLI's access token, use access-token. For + password auth use scram-sha-256. Otherwise, use none and configure auth + manually. + + AUTH must be one of: none, gce-vm, access-token, scram-sha-256. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud beta firestore databases connection-string + diff --git a/gcloud/alpha/firestore/databases/create b/gcloud/alpha/firestore/databases/create index 196a46010..00fa15e7c 100644 --- a/gcloud/alpha/firestore/databases/create +++ b/gcloud/alpha/firestore/databases/create @@ -5,10 +5,17 @@ NAME SYNOPSIS gcloud alpha firestore databases create --location=LOCATION [--database=DATABASE; default="(default)"] [--delete-protection] - [--enable-pitr] [--kms-key-name=KMS_KEY_NAME] - [--type=TYPE; default="firestore-native"] [GCLOUD_WIDE_FLAG ...] + [--edition=EDITION; default="standard"] [--enable-pitr] + [--kms-key-name=KMS_KEY_NAME] [--type=TYPE; default="firestore-native"] + [GCLOUD_WIDE_FLAG ...] EXAMPLES + To create a Firestore Enterprise database named foo in nam5 for use with + Ignite APIs. + + $ gcloud alpha firestore databases create --database=foo \ + --edition=enterprise --location=nam5 + To create a Firestore Native database in nam5. $ gcloud alpha firestore databases create --location=nam5 @@ -72,6 +79,10 @@ OPTIONAL FLAGS Default to false. + --edition=EDITION; default="standard" + The edition of the database. EDITION must be one of: standard, + enterprise. + --enable-pitr Whether to enable Point In Time Recovery (PITR) on the created database. diff --git a/gcloud/alpha/firestore/databases/help b/gcloud/alpha/firestore/databases/help index 8d771d94a..6a8e0c889 100644 --- a/gcloud/alpha/firestore/databases/help +++ b/gcloud/alpha/firestore/databases/help @@ -16,6 +16,10 @@ GCLOUD WIDE FLAGS COMMANDS COMMAND is one of the following: + connection-string + (ALPHA) Prints the mongo connection string for the given Firestore + database. + create (ALPHA) Create a Google Cloud Firestore database via Firestore API. diff --git a/gcloud/alpha/firestore/help b/gcloud/alpha/firestore/help index db63fcca1..ec40b282d 100644 --- a/gcloud/alpha/firestore/help +++ b/gcloud/alpha/firestore/help @@ -41,6 +41,9 @@ GROUPS operations (ALPHA) Manage Long Running Operations for Cloud Firestore. + user-creds + (ALPHA) Manage the user creds for a Cloud Firestore Database. + COMMANDS COMMAND is one of the following: diff --git a/gcloud/alpha/firestore/indexes/composite/create b/gcloud/alpha/firestore/indexes/composite/create index 25c661e2a..e94d5015c 100644 --- a/gcloud/alpha/firestore/indexes/composite/create +++ b/gcloud/alpha/firestore/indexes/composite/create @@ -8,6 +8,7 @@ SYNOPSIS [field-path=FIELD-PATH],[order=ORDER],[vector-config=VECTOR-CONFIG] (--collection-group=COLLECTION_GROUP : --database=DATABASE) [--api-scope=API_SCOPE; default="any-api"] [--async] + [--density=DENSITY] [--multikey] [--query-scope=QUERY_SCOPE; default="collection"] [GCLOUD_WIDE_FLAG ...] @@ -103,12 +104,25 @@ REQUIRED FLAGS OPTIONAL FLAGS --api-scope=API_SCOPE; default="any-api" Api scope the index applies to. API_SCOPE must be one of: any-api, - datastore-mode-api. + datastore-mode-api, mongodb-compatible-api. --async Return immediately, without waiting for the operation in progress to complete. + --density=DENSITY + Density of the index. DENSITY must be one of: dense, + density-unspecified, sparse-all, sparse-any. + + --multikey + Optional. Whether the index is multikey. By default, the index is not + multikey. For non-multikey indexes, none of the paths in the index + definition reach or traverse an array, except via an explicit array + index. For multikey indexes, at most one of the paths in the index + definition reach or traverse an array, except via an explicit array + index. Violations will result in errors. Note this field only applies + to index with MONGODB_COMPATIBLE_API ApiScope. + --query-scope=QUERY_SCOPE; default="collection" Query scope the index applies to. QUERY_SCOPE must be one of: collection, collection-group, collection-recursive. diff --git a/gcloud/alpha/firestore/user-creds/create b/gcloud/alpha/firestore/user-creds/create new file mode 100644 index 000000000..7e07643b6 --- /dev/null +++ b/gcloud/alpha/firestore/user-creds/create @@ -0,0 +1,46 @@ +NAME + gcloud alpha firestore user-creds create - creates a Cloud Firestore user + creds + +SYNOPSIS + gcloud alpha firestore user-creds create USER_CREDS --database=DATABASE + [GCLOUD_WIDE_FLAG ...] + +EXAMPLES + To create a user creds called test-user-creds-id under database testdb. + + $ gcloud alpha firestore user-creds create test-user-creds-id \ + --database=testdb + +POSITIONAL ARGUMENTS + USER_CREDS + The user creds to operate on. + + For example, to operate on user creds creds-name-1: + + $ gcloud alpha firestore user-creds create creds-name-1 + +REQUIRED FLAGS + --database=DATABASE + The database to operate on. + + For example, to operate on database foo: + + $ gcloud alpha firestore user-creds create --database='foo' + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud beta firestore user-creds create + diff --git a/gcloud/alpha/firestore/user-creds/delete b/gcloud/alpha/firestore/user-creds/delete new file mode 100644 index 000000000..0265496b4 --- /dev/null +++ b/gcloud/alpha/firestore/user-creds/delete @@ -0,0 +1,46 @@ +NAME + gcloud alpha firestore user-creds delete - deletes a Cloud Firestore user + creds + +SYNOPSIS + gcloud alpha firestore user-creds delete USER_CREDS --database=DATABASE + [GCLOUD_WIDE_FLAG ...] + +EXAMPLES + To delete user creds 'test-user-creds-id' under database testdb. + + $ gcloud alpha firestore user-creds delete test-user-creds-id \ + --database='testdb' + +POSITIONAL ARGUMENTS + USER_CREDS + The user creds to operate on. + + For example, to operate on user creds creds-name-1: + + $ gcloud alpha firestore user-creds delete creds-name-1 + +REQUIRED FLAGS + --database=DATABASE + The database to operate on. + + For example, to operate on database foo: + + $ gcloud alpha firestore user-creds delete --database='foo' + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud beta firestore user-creds delete + diff --git a/gcloud/alpha/firestore/user-creds/describe b/gcloud/alpha/firestore/user-creds/describe new file mode 100644 index 000000000..d0c36a9d2 --- /dev/null +++ b/gcloud/alpha/firestore/user-creds/describe @@ -0,0 +1,46 @@ +NAME + gcloud alpha firestore user-creds describe - describes a Cloud Firestore + user creds + +SYNOPSIS + gcloud alpha firestore user-creds describe USER_CREDS --database=DATABASE + [GCLOUD_WIDE_FLAG ...] + +EXAMPLES + To describe user creds 'test-user-creds-id' under database testdb. + + $ gcloud alpha firestore user-creds describe test-user-creds-id \ + --database='testdb' + +POSITIONAL ARGUMENTS + USER_CREDS + The user creds to operate on. + + For example, to operate on user creds creds-name-1: + + $ gcloud alpha firestore user-creds describe creds-name-1 + +REQUIRED FLAGS + --database=DATABASE + The database to operate on. + + For example, to operate on database foo: + + $ gcloud alpha firestore user-creds describe --database='foo' + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud beta firestore user-creds describe + diff --git a/gcloud/alpha/firestore/user-creds/disable b/gcloud/alpha/firestore/user-creds/disable new file mode 100644 index 000000000..f7cb4330a --- /dev/null +++ b/gcloud/alpha/firestore/user-creds/disable @@ -0,0 +1,46 @@ +NAME + gcloud alpha firestore user-creds disable - disables a Cloud Firestore user + creds + +SYNOPSIS + gcloud alpha firestore user-creds disable USER_CREDS --database=DATABASE + [GCLOUD_WIDE_FLAG ...] + +EXAMPLES + To disable user creds 'test-user-creds-id' under database testdb. + + $ gcloud alpha firestore user-creds disable test-user-creds-id \ + --database='testdb' + +POSITIONAL ARGUMENTS + USER_CREDS + The user creds to operate on. + + For example, to operate on user creds creds-name-1: + + $ gcloud alpha firestore user-creds disable creds-name-1 + +REQUIRED FLAGS + --database=DATABASE + The database to operate on. + + For example, to operate on database foo: + + $ gcloud alpha firestore user-creds disable --database='foo' + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud beta firestore user-creds disable + diff --git a/gcloud/alpha/firestore/user-creds/enable b/gcloud/alpha/firestore/user-creds/enable new file mode 100644 index 000000000..90f13723c --- /dev/null +++ b/gcloud/alpha/firestore/user-creds/enable @@ -0,0 +1,46 @@ +NAME + gcloud alpha firestore user-creds enable - enables a Cloud Firestore user + creds + +SYNOPSIS + gcloud alpha firestore user-creds enable USER_CREDS --database=DATABASE + [GCLOUD_WIDE_FLAG ...] + +EXAMPLES + To enable user creds 'test-user-creds-id' under database testdb. + + $ gcloud alpha firestore user-creds enable test-user-creds-id \ + --database='testdb' + +POSITIONAL ARGUMENTS + USER_CREDS + The user creds to operate on. + + For example, to operate on user creds creds-name-1: + + $ gcloud alpha firestore user-creds enable creds-name-1 + +REQUIRED FLAGS + --database=DATABASE + The database to operate on. + + For example, to operate on database foo: + + $ gcloud alpha firestore user-creds enable --database='foo' + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud beta firestore user-creds enable + diff --git a/gcloud/alpha/firestore/user-creds/help b/gcloud/alpha/firestore/user-creds/help new file mode 100644 index 000000000..fc86879e0 --- /dev/null +++ b/gcloud/alpha/firestore/user-creds/help @@ -0,0 +1,47 @@ +NAME + gcloud alpha firestore user-creds - manage the user creds for a Cloud + Firestore Database + +SYNOPSIS + gcloud alpha firestore user-creds COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Manage the user creds for a Cloud Firestore Database. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + create + (ALPHA) Creates a Cloud Firestore user creds. + + delete + (ALPHA) Deletes a Cloud Firestore user creds. + + describe + (ALPHA) Describes a Cloud Firestore user creds. + + disable + (ALPHA) Disables a Cloud Firestore user creds. + + enable + (ALPHA) Enables a Cloud Firestore user creds. + + list + (ALPHA) Lists user creds under a Cloud Firesore database. + + reset-password + (ALPHA) Resets a Cloud Firestore user creds. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud beta firestore user-creds + diff --git a/gcloud/alpha/firestore/user-creds/list b/gcloud/alpha/firestore/user-creds/list new file mode 100644 index 000000000..b660742c1 --- /dev/null +++ b/gcloud/alpha/firestore/user-creds/list @@ -0,0 +1,70 @@ +NAME + gcloud alpha firestore user-creds list - lists user creds under a Cloud + Firesore database + +SYNOPSIS + gcloud alpha firestore user-creds list --database=DATABASE + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + +EXAMPLES + To list all user creds under database testdb. + + $ gcloud alpha firestore user-creds list --database='testdb' + +REQUIRED FLAGS + --database=DATABASE + The database to operate on. + + For example, to operate on database foo: + + $ gcloud alpha firestore user-creds list --database='foo' + +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. This variant is also available: + + $ gcloud beta firestore user-creds list + diff --git a/gcloud/alpha/firestore/user-creds/reset-password b/gcloud/alpha/firestore/user-creds/reset-password new file mode 100644 index 000000000..2ccf9b84f --- /dev/null +++ b/gcloud/alpha/firestore/user-creds/reset-password @@ -0,0 +1,47 @@ +NAME + gcloud alpha firestore user-creds reset-password - resets a Cloud Firestore + user creds + +SYNOPSIS + gcloud alpha firestore user-creds reset-password USER_CREDS + --database=DATABASE [GCLOUD_WIDE_FLAG ...] + +EXAMPLES + To reset password for user creds 'test-user-creds-id' under database + testdb. + + $ gcloud alpha firestore user-creds reset-password \ + test-user-creds-id --database='testdb' + +POSITIONAL ARGUMENTS + USER_CREDS + The user creds to operate on. + + For example, to operate on user creds creds-name-1: + + $ gcloud alpha firestore user-creds reset-password creds-name-1 + +REQUIRED FLAGS + --database=DATABASE + The database to operate on. + + For example, to operate on database foo: + + $ gcloud alpha firestore user-creds reset-password --database='foo' + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud beta firestore user-creds reset-password + diff --git a/gcloud/alpha/iam/workload-identity-pools/create-cred-config b/gcloud/alpha/iam/workload-identity-pools/create-cred-config index ab574d251..7f0c494c0 100644 --- a/gcloud/alpha/iam/workload-identity-pools/create-cred-config +++ b/gcloud/alpha/iam/workload-identity-pools/create-cred-config @@ -14,7 +14,7 @@ SYNOPSIS [--credential-source-type=CREDENTIAL_SOURCE_TYPE] [--enable-imdsv2] [--subject-token-type=SUBJECT_TOKEN_TYPE] [--credential-cert-private-key-path=CREDENTIAL_CERT_PRIVATE_KEY_PATH - : --credential-cert-configuration-output-file=CREDENTIAL_CERT_CONFIGURATION_OUTPUT_FILE] + : --credential-cert-configuration-output-file=CREDENTIAL_CERT_CONFIGURATION_OUTPUT_FILE --credential-cert-trust-chain-path=CREDENTIAL_CERT_TRUST_CHAIN_PATH] [--executable-output-file=EXECUTABLE_OUTPUT_FILE --executable-timeout-millis=EXECUTABLE_TIMEOUT_MILLIS] [--service-account=SERVICE_ACCOUNT @@ -153,6 +153,13 @@ OPTIONAL FLAGS If not specified, the certificate configuration will be created at the default gcloud location. + --credential-cert-trust-chain-path=CREDENTIAL_CERT_TRUST_CHAIN_PATH + Path for the trust chain file. A trust chain file is required if + there are intermediate certificates in the certificate chain in + between the root certificate stored in the workload identity pool + provider trust store. This trust chain file should be a list of PEM + certificates, with the leaf certificate at the top. + Arguments for an executable type credential source. --executable-output-file=EXECUTABLE_OUTPUT_FILE diff --git a/gcloud/alpha/logging/write b/gcloud/alpha/logging/write index efea17df0..4fe474f67 100644 --- a/gcloud/alpha/logging/write +++ b/gcloud/alpha/logging/write @@ -3,6 +3,8 @@ NAME SYNOPSIS gcloud alpha logging write LOG_NAME MESSAGE + [--monitored-resource-labels=[KEY=VALUE, ...,...]] + [--monitored-resource-type=MONITORED_RESOURCE_TYPE; default="global"] [--payload-type=PAYLOAD_TYPE; default="text"] [--severity=SEVERITY; default="DEFAULT"] [--billing-account=BILLING_ACCOUNT_ID | --folder=FOLDER_ID @@ -11,10 +13,8 @@ SYNOPSIS DESCRIPTION (ALPHA) Write a log entry. If the destination log does not exist, it will - be created. All log entries written with this command are considered to be - from the "custom.googleapis.com" v1 service or the "global" v2 resource - type. The log entries will be listed in the Logs Explorer under that - service or resource type. + be created. By default, all log entries written with this command are + written with the "global" resource type. gcloud alpha logging write should be used for simple testing purposes. Check Cloud Logging agent for a proper way to send log entries: @@ -35,6 +35,12 @@ EXAMPLES $ gcloud alpha logging write LOG_NAME '{"key": "value"}' \ --payload-type=json + To create a log entry with a custom resource type, run: + + $ gcloud alpha logging write LOG_NAME "A simple entry" \ + --monitored-resource-type=gce_instance \ + --monitored-resource-labels=zone=us-centra1-a,instance_id=1234 + POSITIONAL ARGUMENTS LOG_NAME Name of the log where the log entry will be written. @@ -44,6 +50,12 @@ POSITIONAL ARGUMENTS --payload-type=json. FLAGS + --monitored-resource-labels=[KEY=VALUE, ...,...] + Monitored Resource labels to add to the payload + + --monitored-resource-type=MONITORED_RESOURCE_TYPE; default="global" + Monitored Resource type to add to the payload + --payload-type=PAYLOAD_TYPE; default="text" Type of the log entry payload. PAYLOAD_TYPE must be one of: text, json. diff --git a/gcloud/alpha/managed-kafka/clusters/create b/gcloud/alpha/managed-kafka/clusters/create index bf9628e98..b9984b409 100644 --- a/gcloud/alpha/managed-kafka/clusters/create +++ b/gcloud/alpha/managed-kafka/clusters/create @@ -64,10 +64,11 @@ REQUIRED FLAGS --subnets=[SUBNETS,...] VPC subnets from which the cluster is accessible. Both broker and bootstrap server IP addresses and DNS entries are automatically created - in each subnet. The subnet must be located in the same region as the - cluster. The project may differ. A minimum of 1 subnet is required. A - maximum of 10 subnets can be specified. Use commas to separate multiple - subnets. The name of the subnet must be in the format + in each subnet. Only one subnet per network is allowed, and the subnet + must be located in the same region as the cluster. The project may + differ. A minimum of 1 subnet is required. A maximum of 10 subnets can + be specified. Use commas to separate multiple subnets. The name of the + subnet must be in the format projects/PROJECT_ID/regions/REGION/subnetworks/SUBNET. OPTIONAL FLAGS diff --git a/gcloud/alpha/managed-kafka/clusters/update b/gcloud/alpha/managed-kafka/clusters/update index feeec0634..bb73fed65 100644 --- a/gcloud/alpha/managed-kafka/clusters/update +++ b/gcloud/alpha/managed-kafka/clusters/update @@ -77,11 +77,12 @@ REQUIRED FLAGS --subnets=[SUBNETS,...] VPC subnets from which the cluster is accessible. Both broker and bootstrap server IP addresses and DNS entries are automatically - created in each subnet. The subnet must be located in the same region - as the cluster. The project may differ. A minimum of 1 subnet is - required. A maximum of 10 subnets can be specified. Use commas to - separate multiple subnets. The name of the subnet must be in the - format projects/PROJECT_ID/regions/REGION/subnetworks/SUBNET. + created in each subnet. Only one subnet per network is allowed, and + the subnet must be located in the same region as the cluster. The + project may differ. A minimum of 1 subnet is required. A maximum of + 10 subnets can be specified. Use commas to separate multiple subnets. + The name of the subnet must be in the format + projects/PROJECT_ID/regions/REGION/subnetworks/SUBNET. OPTIONAL FLAGS --async diff --git a/gcloud/alpha/migration/vms/target-projects/help b/gcloud/alpha/migration/vms/target-projects/help index 82b63afe5..59c1d44ab 100644 --- a/gcloud/alpha/migration/vms/target-projects/help +++ b/gcloud/alpha/migration/vms/target-projects/help @@ -26,5 +26,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 migration vms target-projects diff --git a/gcloud/alpha/migration/vms/target-projects/list b/gcloud/alpha/migration/vms/target-projects/list index f3ff51e6b..563e158b4 100644 --- a/gcloud/alpha/migration/vms/target-projects/list +++ b/gcloud/alpha/migration/vms/target-projects/list @@ -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 migration vms target-projects list diff --git a/gcloud/alpha/network-security/server-tls-policies/list b/gcloud/alpha/network-security/server-tls-policies/list index 66c6e2829..adae0fbf3 100644 --- a/gcloud/alpha/network-security/server-tls-policies/list +++ b/gcloud/alpha/network-security/server-tls-policies/list @@ -3,38 +3,38 @@ NAME ServerTlsPolicies SYNOPSIS - gcloud alpha network-security server-tls-policies list --location=LOCATION - [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] - [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + gcloud alpha network-security server-tls-policies list + [--location=LOCATION] [--filter=EXPRESSION] [--limit=LIMIT] + [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) List all ServerTlsPolicies in the specified location of the current - project. + (ALPHA) List all ServerTlsPolicies in the current project. EXAMPLES To list ServerTlsPolicies in the current project, run: - $ gcloud alpha network-security server-tls-policies list \ - --location=global + $ gcloud alpha network-security server-tls-policies list -REQUIRED FLAGS - Location resource - The project of the ServerTlsPolicies to display. This +FLAGS + Location resource - The location of the ServerTlsPolicies 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; + ◆ if left empty, will use the wildcard '-' to list all locations with a + fully specified name; ◆ provide the argument --project on the command line; ◆ set the property core/project. - 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. + ▸ provide the argument --location on the command line; + ▸ if left empty, will use the wildcard '-' to list all locations. LIST COMMAND FLAGS --filter=EXPRESSION diff --git a/gcloud/alpha/network-services/help b/gcloud/alpha/network-services/help index da423b441..de26bebf2 100644 --- a/gcloud/alpha/network-services/help +++ b/gcloud/alpha/network-services/help @@ -69,6 +69,9 @@ GROUPS observability-policies (ALPHA) Manage Network Services ObservabilityPolicies. + operations + (ALPHA) Manage Network Services Operations. + route-views (ALPHA) View Network Services Route Views. diff --git a/gcloud/alpha/network-services/operations/cancel b/gcloud/alpha/network-services/operations/cancel new file mode 100644 index 000000000..7137b15ef --- /dev/null +++ b/gcloud/alpha/network-services/operations/cancel @@ -0,0 +1,66 @@ +NAME + gcloud alpha network-services operations cancel - cancel a Network Services + long running operation + +SYNOPSIS + gcloud alpha network-services operations cancel + (OPERATION : --location=LOCATION) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Cancel a Network Services long running operation. + +EXAMPLES + The following command cancels an operation with the full name + OPERATION_NAME: + + $ gcloud alpha network-services operations cancel OPERATION_NAME + +POSITIONAL ARGUMENTS + Operation resource - Name of the operation to cancel. 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 argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + The location Id. + + 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 networkservices/v1alpha1 API. The full documentation + for this API can be found at: https://cloud.google.com/networking + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/network-services/operations/describe b/gcloud/alpha/network-services/operations/describe new file mode 100644 index 000000000..111a68acc --- /dev/null +++ b/gcloud/alpha/network-services/operations/describe @@ -0,0 +1,66 @@ +NAME + gcloud alpha network-services operations describe - show details of a + Network Services long running operation + +SYNOPSIS + gcloud alpha network-services operations describe + (OPERATION : --location=LOCATION) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Show details of a Network Services long running operation. + +EXAMPLES + The following command describes an operation with the full name + OPERATION_NAME: + + $ gcloud alpha network-services operations describe OPERATION_NAME + +POSITIONAL ARGUMENTS + Operation resource - Name of the operation 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; + ◆ 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 argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + The location Id. + + 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 networkservices/v1alpha1 API. The full documentation + for this API can be found at: https://cloud.google.com/networking + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/network-services/operations/help b/gcloud/alpha/network-services/operations/help new file mode 100644 index 000000000..3218d7f76 --- /dev/null +++ b/gcloud/alpha/network-services/operations/help @@ -0,0 +1,36 @@ +NAME + gcloud alpha network-services operations - manage Network Services + Operations + +SYNOPSIS + gcloud alpha network-services operations COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Manage Network Services Operations. + +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 Network Services long running operation. + + describe + (ALPHA) Show details of a Network Services long running operation. + + list + (ALPHA) List all Network Services long running operations. + + wait + (ALPHA) Poll a Network Services long running operation. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/network-services/operations/list b/gcloud/alpha/network-services/operations/list new file mode 100644 index 000000000..5a3cbb8fc --- /dev/null +++ b/gcloud/alpha/network-services/operations/list @@ -0,0 +1,87 @@ +NAME + gcloud alpha network-services operations list - list all Network Services + long running operations + +SYNOPSIS + gcloud alpha network-services operations list --location=LOCATION + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) List all Network Services long running operations. + +EXAMPLES + The following command lists all operations in the current project and in + location global: + + $ gcloud alpha network-services operations list --location=global + +REQUIRED FLAGS + Location resource - Location of the operations. This represents a Cloud + resource. (NOTE) Some attributes are not given arguments in this group but + can be set in other ways. + + To set the project attribute: + ◆ provide the argument --location on the command line with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + --location=LOCATION + ID of the location or fully qualified identifier for the location. + + To set the location attribute: + ▸ provide the argument --location on the command line. + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + + --uri + Print a list of resource URIs instead of the default output, and change + the command output to a list of URIs. If this flag is used with + --format, the formatting is applied on this URI list. To display URIs + alongside other keys instead, use the uri() transform. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the networkservices/v1alpha1 API. The full documentation + for this API can be found at: https://cloud.google.com/networking + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/network-services/operations/wait b/gcloud/alpha/network-services/operations/wait new file mode 100644 index 000000000..990d6bc92 --- /dev/null +++ b/gcloud/alpha/network-services/operations/wait @@ -0,0 +1,65 @@ +NAME + gcloud alpha network-services operations wait - poll a Network Services + long running operation + +SYNOPSIS + gcloud alpha network-services operations wait + (OPERATION : --location=LOCATION) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Poll a Network Services long running operation. + +EXAMPLES + The following command polls an operation with the full name OPERATION_NAME: + + $ gcloud alpha network-services operations wait OPERATION_NAME + +POSITIONAL ARGUMENTS + Operation resource - Name of the operation to poll. 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 argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + The location Id. + + 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 networkservices/v1alpha1 API. The full documentation + for this API can be found at: https://cloud.google.com/networking + +NOTES + This command is currently in alpha and might change without notice. If this + command fails 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/scc/findings/list-marks b/gcloud/alpha/scc/findings/list-marks index 3692e4162..0878337f7 100644 --- a/gcloud/alpha/scc/findings/list-marks +++ b/gcloud/alpha/scc/findings/list-marks @@ -2,11 +2,12 @@ NAME gcloud alpha scc findings list-marks - list a finding's security marks SYNOPSIS - gcloud alpha scc findings list-marks - (FINDING : --organization=ORGANIZATION --source=SOURCE) + gcloud alpha scc findings list-marks FINDING [--location=LOCATION; default="global"] [--page-token=PAGE_TOKEN] - [--read-time=READ_TIME] [--filter=EXPRESSION] [--limit=LIMIT] - [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [GCLOUD_WIDE_FLAG ...] + [--read-time=READ_TIME] [--source=SOURCE; default="-"] + [--folder=FOLDER | --organization=ORGANIZATION | --project=PROJECT] + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) List a finding's security marks. @@ -36,45 +37,8 @@ EXAMPLES --organization=123456 --source=5678 --location=eu POSITIONAL ARGUMENTS - Finding resource - The finding to be used for the SCC (Security Command - Center) command. The arguments in this group can be used to specify the - attributes of this resource. - - This must be specified. - - FINDING - ID of the finding or fully qualified identifier for the finding. - - To set the finding attribute: - ▸ provide the argument finding on the command line. - - This positional argument must be specified if any of the other - arguments in this group are specified. - - --organization=ORGANIZATION - (Optional) If the full resource name isn't provided e.g. - organizations/123, then provide the organization id which is the - suffix of the organization. Example: organizations/123, the id is - 123. - - To set the organization attribute: - ▸ provide the argument finding on the command line with a fully - specified name; - ▸ provide the argument --organization on the command line; - ▸ Set the organization property in configuration using gcloud - config set scc/organization if it is not specified in command - line.. - - --source=SOURCE - (Optional) If the full resource name isn't provided e.g. - organizations/123/sources/456, then provide the source id which is - the suffix of the source. Example: organizations/123/sources/456, the - id is 456. - - To set the source attribute: - ▸ provide the argument finding on the command line with a fully - specified name; - ▸ provide the argument --source on the command line. + FINDING + ID of the finding or fully qualified identifier for the finding. FLAGS --location=LOCATION; default="global" @@ -104,6 +68,20 @@ FLAGS (https://cloud.google.com/security-command-center/docs/release-notes#April_15_2024) on the SCC release notes page. + --source=SOURCE; default="-" + Source id. Defaults to all sources. + + At most one of these can be specified: + + --folder=FOLDER + The folder ID (e.g., 456) that contains the finding. + + --organization=ORGANIZATION + The organization ID (e.g., 123) that contains the finding. + + --project=PROJECT + The project ID (e.g., example-project) that contains the finding. + LIST COMMAND FLAGS --filter=EXPRESSION Apply a Boolean filter EXPRESSION to each resource item to be listed. diff --git a/gcloud/alpha/scc/findings/update b/gcloud/alpha/scc/findings/update index 2a6146578..b87cb1e82 100644 --- a/gcloud/alpha/scc/findings/update +++ b/gcloud/alpha/scc/findings/update @@ -2,12 +2,12 @@ NAME gcloud alpha scc findings update - update a Security Command Center finding SYNOPSIS - gcloud alpha scc findings update - (FINDING : --organization=ORGANIZATION --source=SOURCE) - [--event-time=EVENT_TIME] [--external-uri=EXTERNAL_URI] - [--location=LOCATION; default="global"] - [--source-properties=[KEY=VALUE,...]] [--state=STATE] - [--update-mask=UPDATE_MASK] [GCLOUD_WIDE_FLAG ...] + gcloud alpha scc findings update FINDING [--event-time=EVENT_TIME] + [--external-uri=EXTERNAL_URI] [--location=LOCATION; default="global"] + [--source=SOURCE; default="-"] [--source-properties=[KEY=VALUE,...]] + [--state=STATE] [--update-mask=UPDATE_MASK] + [--folder=FOLDER | --organization=ORGANIZATION | --project=PROJECT] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Update a Security Command Center finding. @@ -50,45 +50,8 @@ EXAMPLES --location=eu POSITIONAL ARGUMENTS - Finding resource - The finding to be used for the SCC (Security Command - Center) command. The arguments in this group can be used to specify the - attributes of this resource. - - This must be specified. - - FINDING - ID of the finding or fully qualified identifier for the finding. - - To set the finding attribute: - ▸ provide the argument finding on the command line. - - This positional argument must be specified if any of the other - arguments in this group are specified. - - --organization=ORGANIZATION - (Optional) If the full resource name isn't provided e.g. - organizations/123, then provide the organization id which is the - suffix of the organization. Example: organizations/123, the id is - 123. - - To set the organization attribute: - ▸ provide the argument finding on the command line with a fully - specified name; - ▸ provide the argument --organization on the command line; - ▸ Set the organization property in configuration using gcloud - config set scc/organization if it is not specified in command - line.. - - --source=SOURCE - (Optional) If the full resource name isn't provided e.g. - organizations/123/sources/456, then provide the source id which is - the suffix of the source. Example: organizations/123/sources/456, the - id is 456. - - To set the source attribute: - ▸ provide the argument finding on the command line with a fully - specified name; - ▸ provide the argument --source on the command line. + FINDING + ID of the finding or fully qualified identifier for the finding. FLAGS --event-time=EVENT_TIME @@ -115,6 +78,9 @@ FLAGS location that is specified when data residency controls are enabled for Security Command Center. + --source=SOURCE; default="-" + Source id. Defaults to all sources. + --source-properties=[KEY=VALUE,...] Source specific properties. These properties are managed by the source that writes the finding. The key names in the source_properties map @@ -141,6 +107,17 @@ FLAGS State can be toggled from ACTIVE to INACTIVE and vice-versa but it cannot be deleted. + At most one of these can be specified: + + --folder=FOLDER + The folder ID (e.g., 456) that contains the finding. + + --organization=ORGANIZATION + The organization ID (e.g., 123) that contains the finding. + + --project=PROJECT + The project ID (e.g., example-project) that contains the finding. + 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/scc/findings/update-marks b/gcloud/alpha/scc/findings/update-marks index 9d1100d7b..80e1e0402 100644 --- a/gcloud/alpha/scc/findings/update-marks +++ b/gcloud/alpha/scc/findings/update-marks @@ -3,11 +3,12 @@ NAME finding's security marks SYNOPSIS - gcloud alpha scc findings update-marks - (FINDING : --organization=ORGANIZATION --source=SOURCE) + gcloud alpha scc findings update-marks FINDING [--location=LOCATION; default="global"] - [--security-marks=[KEY=VALUE,...]] [--start-time=START_TIME] - [--update-mask=UPDATE_MASK] [GCLOUD_WIDE_FLAG ...] + [--security-marks=[KEY=VALUE,...]] [--source=SOURCE; default="-"] + [--start-time=START_TIME] [--update-mask=UPDATE_MASK] + [--folder=FOLDER | --organization=ORGANIZATION | --project=PROJECT] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Update Security Command Center finding's security marks. @@ -53,45 +54,8 @@ EXAMPLES --security-marks="key1=v1,key2=v2" --location=eu POSITIONAL ARGUMENTS - Finding resource - The finding to be used for the SCC (Security Command - Center) command. The arguments in this group can be used to specify the - attributes of this resource. - - This must be specified. - - FINDING - ID of the finding or fully qualified identifier for the finding. - - To set the finding attribute: - ▸ provide the argument finding on the command line. - - This positional argument must be specified if any of the other - arguments in this group are specified. - - --organization=ORGANIZATION - (Optional) If the full resource name isn't provided e.g. - organizations/123, then provide the organization id which is the - suffix of the organization. Example: organizations/123, the id is - 123. - - To set the organization attribute: - ▸ provide the argument finding on the command line with a fully - specified name; - ▸ provide the argument --organization on the command line; - ▸ Set the organization property in configuration using gcloud - config set scc/organization if it is not specified in command - line.. - - --source=SOURCE - (Optional) If the full resource name isn't provided e.g. - organizations/123/sources/456, then provide the source id which is - the suffix of the source. Example: organizations/123/sources/456, the - id is 456. - - To set the source attribute: - ▸ provide the argument finding on the command line with a fully - specified name; - ▸ provide the argument --source on the command line. + FINDING + ID of the finding or fully qualified identifier for the finding. FLAGS --location=LOCATION; default="global" @@ -110,6 +74,9 @@ FLAGS key=value pair separated by comma (,). For example: --security-marks="key1=val1,key2=val2". + --source=SOURCE; default="-" + Source id. Defaults to all sources. + --start-time=START_TIME Time at which the updated SecurityMarks take effect. See $ gcloud topic datetimes for information on supported time formats. @@ -121,6 +88,17 @@ FLAGS marks for the given finding either skip the update-mask flag or provide an empty value (--update-mask '') for it. + At most one of these can be specified: + + --folder=FOLDER + The folder ID (e.g., 456) that contains the finding. + + --organization=ORGANIZATION + The organization ID (e.g., 123) that contains the finding. + + --project=PROJECT + The project ID (e.g., example-project) that contains the finding. + 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/sql/backups/restore b/gcloud/alpha/sql/backups/restore index 821019a00..480b936e5 100644 --- a/gcloud/alpha/sql/backups/restore +++ b/gcloud/alpha/sql/backups/restore @@ -15,7 +15,6 @@ SYNOPSIS [--backup-project=BACKUP_PROJECT] [--backup-start-time=BACKUP_START_TIME] [--collation=COLLATION] [--connector-enforcement=CONNECTOR_ENFORCEMENT] [--cpu=CPU] - [--database-flags=FLAG=VALUE,[FLAG=VALUE,...]] [--database-version=DATABASE_VERSION] [--[no-]deletion-protection] [--deny-maintenance-period-end-date=DENY_MAINTENANCE_PERIOD_END_DATE] [--deny-maintenance-period-start-date=DENY_MAINTENANCE_PERIOD_START_DATE] @@ -164,14 +163,6 @@ OPTIONAL FLAGS machine. Both --cpu and --memory must be specified if a custom machine type is desired, and the --tier flag must be omitted. - --database-flags=FLAG=VALUE,[FLAG=VALUE,...] - Comma-separated list of database flags to set on the instance. Use an - equals sign to separate flag name and value. Flags without values, like - skip_grant_tables, can be written out without a value after, e.g., - skip_grant_tables=. Use on/off for booleans. View the Instance Resource - API for allowed flags. (e.g., --database-flags - max_allowed_packet=55555,skip_grant_tables=,log_output=1) - --database-version=DATABASE_VERSION The database engine type and versions. If left unspecified, no changes occur. See the list of database versions at diff --git a/gcloud/alpha/sql/instances/clone b/gcloud/alpha/sql/instances/clone index dfcbb4ec0..22cb3b361 100644 --- a/gcloud/alpha/sql/instances/clone +++ b/gcloud/alpha/sql/instances/clone @@ -60,8 +60,16 @@ EXAMPLES To specify the allocated IP range for the private IP target Instance (reserved for future use): - $ gcloud alpha sql instances clone instance-foo instance-bar \ - --allocated-ip-range-name range-bar + $ gcloud alpha sql instances clone my-source-instance \ + my-cloned-instance \ + --allocated-ip-range-name cloned-instance-ip-range + + To clone a deleted instance, include the name and deletion time of the + source instance: + + $ gcloud alpha sql instances clone my-source-instance \ + my-cloned-instance \ + --source-instance-deletion-time '2012-11-15T16:19:00.094Z' POSITIONAL ARGUMENTS SOURCE diff --git a/gcloud/artifacts/go/auth b/gcloud/artifacts/go/auth new file mode 100644 index 000000000..3b0d34266 --- /dev/null +++ b/gcloud/artifacts/go/auth @@ -0,0 +1,53 @@ +NAME + gcloud artifacts go auth - print authentication commands for the GOAUTH + environment variable + +SYNOPSIS + gcloud artifacts go auth [URL ...] --location=LOCATION + [--json-key=JSON_KEY] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + This command implements the GOAUTH credential provider command introduced + in Go 1.24. For more details about the GOAUTH environment variable, see + https://pkg.go.dev/cmd/go#hdr-GOAUTH_environment_variable. When you + configure the GOAUTH environment variable for repositories, Artifact + Registry looks for credentials in the following order: + + ▪ Application Default Credentials (ADC) + ▪ Credentials provided by the Google Cloud CLI, including user + credentials from the command gcloud auth application-default login. + +EXAMPLES + To configure the GOAUTH environment variable for repositories in + us-central1 and use your credentials: + + $ export GOAUTH="gcloud artifacts go auth --location=us-central1" + + To configure the GOAUTH environment variable for repositories in + us-central1 and use the credentials from a service account: + + $ export \ + GOAUTH="gcloud artifacts go auth --location=us-central1 \ + --json-key=path/to/key.json" + +POSITIONAL ARGUMENTS + [URL ...] + A URL generated by Go to set up authentication. + +REQUIRED FLAGS + --location=LOCATION + The location of the repository to print commands for. + +OPTIONAL FLAGS + --json-key=JSON_KEY + The path to the JSON key file to use for authentication. If not + specified, the authentication commands printed will use the token from + the logged in user. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. diff --git a/gcloud/artifacts/go/help b/gcloud/artifacts/go/help index 1da6d390c..f25e2badd 100644 --- a/gcloud/artifacts/go/help +++ b/gcloud/artifacts/go/help @@ -15,6 +15,9 @@ GCLOUD WIDE FLAGS COMMANDS COMMAND is one of the following: + auth + Print authentication commands for the GOAUTH environment variable. + upload Upload a Go module to an artifact repository. diff --git a/gcloud/auth/enterprise-certificate-config/create/macos b/gcloud/auth/enterprise-certificate-config/create/macos index ea976cb2f..30c47e001 100644 --- a/gcloud/auth/enterprise-certificate-config/create/macos +++ b/gcloud/auth/enterprise-certificate-config/create/macos @@ -4,8 +4,10 @@ NAME SYNOPSIS gcloud auth enterprise-certificate-config create macos --issuer=ISSUER - [--ecp=ECP] [--ecp-client=ECP_CLIENT] [--output-file=OUTPUT_FILE] - [--tls-offload=TLS_OFFLOAD] [GCLOUD_WIDE_FLAG ...] + [--ecp=ECP] [--ecp-client=ECP_CLIENT] + [--keychain-type=KEYCHAIN_TYPE; default="all"] + [--output-file=OUTPUT_FILE] [--tls-offload=TLS_OFFLOAD] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION This command creates a configuration file used by gcloud to use the @@ -30,6 +32,11 @@ OPTIONAL FLAGS Provide a custom path to the enterprise-certificate-proxy shared client library. This flag must be the full path to the shared library. + --keychain-type=KEYCHAIN_TYPE; default="all" + Specify the target keychain(s) for certificate lookup.Accepted values + are "login", "system", or "all". If omitted,defaults to "all". Use + "all" to include custom keychains. + --output-file=OUTPUT_FILE Override the file path that the enterprise-certificate-proxy configuration is written to. diff --git a/gcloud/backup-dr/management-servers/create b/gcloud/backup-dr/management-servers/create index a91b08ab4..9d739e6fc 100644 --- a/gcloud/backup-dr/management-servers/create +++ b/gcloud/backup-dr/management-servers/create @@ -15,11 +15,10 @@ DESCRIPTION EXAMPLES To create a new management server sample-ms in project sample-project and - location us-central1 with network sample-network, run: + location us-central1, run: $ gcloud backup-dr management-servers create sample-ms \ - --project=sample-project --location=us-central1 \ - --network=projects/sample-project/global/networks/sample-network + --project=sample-project --location=us-central1 POSITIONAL ARGUMENTS Management Server resource - Name of the management server to be created. @@ -62,14 +61,17 @@ FLAGS disable. --network=NETWORK - Name of an existing VPC network with private service access configured - in the format - projects//global/networks/. This VPC - network allows the management console to communicate with all - backup/recovery appliances and requires a minimum IP range of /23. This - value cannot be changed after you deploy the management server. If you - don't have private service access, configure one. [Learn more] + (DEPRECATED) Name of an existing VPC network with private service + access configured in the format - + projects//global/networks/. This VPC network allows + the management console to communicate with all backup/recovery + appliances and requires a minimum IP range of /23. This value cannot be + changed after you deploy the management server. If you don't have + private service access, configure one. [Learn more] (https://cloud.google.com/vpc/docs/configure-private-services-access) + Flag --network is deprecated. + 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/clusters/export b/gcloud/beta/alloydb/clusters/export index 13662f90c..698c43dbe 100644 --- a/gcloud/beta/alloydb/clusters/export +++ b/gcloud/beta/alloydb/clusters/export @@ -28,7 +28,7 @@ POSITIONAL ARGUMENTS REQUIRED FLAGS --database=DATABASE - Database name from which export has to be done. + Database name. Destination URI where the file needs to be exported. diff --git a/gcloud/beta/alloydb/clusters/import b/gcloud/beta/alloydb/clusters/import index c53ee2b7b..7ca09870e 100644 --- a/gcloud/beta/alloydb/clusters/import +++ b/gcloud/beta/alloydb/clusters/import @@ -78,7 +78,7 @@ OPTIONAL FLAGS complete. --database=DATABASE - Database name from which export has to be done. + Database name. --user=USER Database user for the import. diff --git a/gcloud/beta/auth/enterprise-certificate-config/create/macos b/gcloud/beta/auth/enterprise-certificate-config/create/macos index e1a69cf37..4842a7f6d 100644 --- a/gcloud/beta/auth/enterprise-certificate-config/create/macos +++ b/gcloud/beta/auth/enterprise-certificate-config/create/macos @@ -4,8 +4,10 @@ NAME SYNOPSIS gcloud beta auth enterprise-certificate-config create macos --issuer=ISSUER - [--ecp=ECP] [--ecp-client=ECP_CLIENT] [--output-file=OUTPUT_FILE] - [--tls-offload=TLS_OFFLOAD] [GCLOUD_WIDE_FLAG ...] + [--ecp=ECP] [--ecp-client=ECP_CLIENT] + [--keychain-type=KEYCHAIN_TYPE; default="all"] + [--output-file=OUTPUT_FILE] [--tls-offload=TLS_OFFLOAD] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) This command creates a configuration file used by gcloud to use the @@ -30,6 +32,11 @@ OPTIONAL FLAGS Provide a custom path to the enterprise-certificate-proxy shared client library. This flag must be the full path to the shared library. + --keychain-type=KEYCHAIN_TYPE; default="all" + Specify the target keychain(s) for certificate lookup.Accepted values + are "login", "system", or "all". If omitted,defaults to "all". Use + "all" to include custom keychains. + --output-file=OUTPUT_FILE Override the file path that the enterprise-certificate-proxy configuration is written to. diff --git a/gcloud/beta/backup-dr/management-servers/create b/gcloud/beta/backup-dr/management-servers/create index bf970438f..0bd661eb2 100644 --- a/gcloud/beta/backup-dr/management-servers/create +++ b/gcloud/beta/backup-dr/management-servers/create @@ -15,11 +15,10 @@ DESCRIPTION EXAMPLES To create a new management server sample-ms in project sample-project and - location us-central1 with network sample-network, run: + location us-central1, run: $ gcloud beta backup-dr management-servers create sample-ms \ - --project=sample-project --location=us-central1 \ - --network=projects/sample-project/global/networks/sample-network + --project=sample-project --location=us-central1 POSITIONAL ARGUMENTS Management Server resource - Name of the management server to be created. @@ -62,14 +61,17 @@ FLAGS disable. --network=NETWORK - Name of an existing VPC network with private service access configured - in the format - projects//global/networks/. This VPC - network allows the management console to communicate with all - backup/recovery appliances and requires a minimum IP range of /23. This - value cannot be changed after you deploy the management server. If you - don't have private service access, configure one. [Learn more] + (DEPRECATED) Name of an existing VPC network with private service + access configured in the format - + projects//global/networks/. This VPC network allows + the management console to communicate with all backup/recovery + appliances and requires a minimum IP range of /23. This value cannot be + changed after you deploy the management server. If you don't have + private service access, configure one. [Learn more] (https://cloud.google.com/vpc/docs/configure-private-services-access) + Flag --network is deprecated. + 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/bigtable/help b/gcloud/beta/bigtable/help index 0e1a4a92b..01072ff75 100644 --- a/gcloud/beta/bigtable/help +++ b/gcloud/beta/bigtable/help @@ -36,6 +36,9 @@ GROUPS logical-views (BETA) Manage Bigtable logical views. + materialized-views + (BETA) Manage Bigtable materialized views. + operations (BETA) Manage Cloud Bigtable operations. diff --git a/gcloud/beta/bigtable/instances/tables/create b/gcloud/beta/bigtable/instances/tables/create index ef02fcf04..2ac95de7c 100644 --- a/gcloud/beta/bigtable/instances/tables/create +++ b/gcloud/beta/bigtable/instances/tables/create @@ -6,7 +6,9 @@ SYNOPSIS gcloud beta bigtable instances tables create (TABLE : --instance=INSTANCE) --column-families=[COLUMN_FAMILIES,...] [--change-stream-retention-period=CHANGE_STREAM_RETENTION_PERIOD] - [--deletion-protection] [--splits=[SPLITS,...]] + [--deletion-protection] + [--row-key-schema-definition-file=ROW_KEY_SCHEMA_DEFINITION_FILE] + [--row-key-schema-pre-encoded-bytes] [--splits=[SPLITS,...]] [--automated-backup-retention-period=AUTOMATED_BACKUP_RETENTION_PERIOD | --enable-automated-backup] [GCLOUD_WIDE_FLAG ...] @@ -125,6 +127,34 @@ OPTIONAL FLAGS --deletion-protection Once specified, the table is deletion protected. + --row-key-schema-definition-file=ROW_KEY_SCHEMA_DEFINITION_FILE + The row key schema for the table. The schema is defined in a YAML or + JSON file, equivalent to the StructType protobuf message. + + Example YAML: + + encoding: + delimitedBytes: + delimiter: '#' + fields: + - fieldName: field1 + type: + bytesType: + encoding: + raw: {} + - fieldName: field2 + type: + bytesType: + encoding: + raw: {} + + --row-key-schema-pre-encoded-bytes + By default, Base64 encoding is applied to all binary fields in the + YAML/JSON file (for example, encoding.delimitedBytes.delimiter). + + Use this to indicate that all binary fields are already encoded in the + YAML/JSON file and should not be encoded again. + --splits=[SPLITS,...] Row keys where the table should initially be split. For example: car,key diff --git a/gcloud/beta/bigtable/instances/tables/update b/gcloud/beta/bigtable/instances/tables/update index ae07592ac..7c409907c 100644 --- a/gcloud/beta/bigtable/instances/tables/update +++ b/gcloud/beta/bigtable/instances/tables/update @@ -4,11 +4,14 @@ NAME SYNOPSIS gcloud beta bigtable instances tables update (TABLE : --instance=INSTANCE) - [--async] [--deletion-protection] + [--async] [--deletion-protection] [--row-key-schema-pre-encoded-bytes] [--automated-backup-retention-period=AUTOMATED_BACKUP_RETENTION_PERIOD | --disable-automated-backup | --enable-automated-backup] [--change-stream-retention-period=CHANGE_STREAM_RETENTION_PERIOD - | --clear-change-stream-retention-period] [GCLOUD_WIDE_FLAG ...] + | --clear-change-stream-retention-period] + [--clear-row-key-schema + | --row-key-schema-definition-file=ROW_KEY_SCHEMA_DEFINITION_FILE] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) Update an existing new Cloud Bigtable table with the specified @@ -92,6 +95,16 @@ FLAGS --deletion-protection Once specified, the table is deletion protected. + --row-key-schema-pre-encoded-bytes + By default, Base64 encoding is applied to all binary fields in the + YAML/JSON file (for example, encoding.delimitedBytes.delimiter). + + Use this to indicate that all binary fields are already encoded in the + YAML/JSON file and should not be encoded again. + + This field is only used when row-key-schema-definition-file is set. It + is ignored if clear-row-key-schema is set. + At most one of these can be specified: --automated-backup-retention-period=AUTOMATED_BACKUP_RETENTION_PERIOD @@ -120,6 +133,35 @@ FLAGS This disables the change stream and eventually removes the change stream data. + Whether to update or clear the row key schema in the updated table. Only + one of these flags can be set. + + At most one of these can be specified: + + --clear-row-key-schema + Whether to clear the row key schema in the updated table. + + --row-key-schema-definition-file=ROW_KEY_SCHEMA_DEFINITION_FILE + The row key schema for the table. The schema is defined in a YAML or + JSON file, equivalent to the StructType protobuf message. + + Example YAML: + + encoding: + delimitedBytes: + delimiter: '#' + fields: + - fieldName: field1 + type: + bytesType: + encoding: + raw: {} + - fieldName: field2 + type: + bytesType: + encoding: + raw: {} + 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/bigtable/materialized-views/create b/gcloud/beta/bigtable/materialized-views/create new file mode 100644 index 000000000..dee50f276 --- /dev/null +++ b/gcloud/beta/bigtable/materialized-views/create @@ -0,0 +1,78 @@ +NAME + gcloud beta bigtable materialized-views create - create a new Bigtable + materialized view + +SYNOPSIS + gcloud beta bigtable materialized-views create + (MATERIALIZED_VIEW : --instance=INSTANCE) --query=QUERY [--async] + [--deletion-protection=DELETION_PROTECTION] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Create a new Bigtable materialized view. + +EXAMPLES + To create a materialized view, run: $ gcloud beta bigtable materialized-views create \ + my-materialized-view-id --instance=my-instance-id \ + --query="SELECT my-column-family FROM my-table \ + --deletion-protection=false" + +POSITIONAL ARGUMENTS + Materialized view resource - The materialized view 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 materialized_view 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. + + MATERIALIZED_VIEW + ID of the materialized view or fully qualified identifier for the + materialized view. + + To set the name attribute: + ▸ provide the argument materialized_view on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --instance=INSTANCE + Bigtable instance for the materialized view. + + To set the instance attribute: + ▸ provide the argument materialized_view on the command line with a + fully specified name; + ▸ provide the argument --instance on the command line. + +REQUIRED FLAGS + --query=QUERY + The query of the view. + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --deletion-protection=DELETION_PROTECTION + Whether the view is protected from deletion. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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 bigtable materialized-views create + + $ gcloud alpha bigtable materialized-views create + diff --git a/gcloud/beta/bigtable/materialized-views/delete b/gcloud/beta/bigtable/materialized-views/delete new file mode 100644 index 000000000..84cc0b250 --- /dev/null +++ b/gcloud/beta/bigtable/materialized-views/delete @@ -0,0 +1,65 @@ +NAME + gcloud beta bigtable materialized-views delete - delete a Bigtable + materialized view + +SYNOPSIS + gcloud beta bigtable materialized-views delete + (MATERIALIZED_VIEW : --instance=INSTANCE) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Delete a Bigtable materialized view. + +EXAMPLES + To delete a materialized view, run: + + $ gcloud beta bigtable materialized-views delete \ + my-materialized-view-id --instance=my-instance-id + +POSITIONAL ARGUMENTS + Materialized view resource - The materialized view 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 materialized_view 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. + + MATERIALIZED_VIEW + ID of the materialized view or fully qualified identifier for the + materialized view. + + To set the name attribute: + ▸ provide the argument materialized_view on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --instance=INSTANCE + Bigtable instance for the materialized view. + + To set the instance attribute: + ▸ provide the argument materialized_view on the command line with a + fully specified name; + ▸ provide the argument --instance 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 beta and might change without notice. These + variants are also available: + + $ gcloud bigtable materialized-views delete + + $ gcloud alpha bigtable materialized-views delete + diff --git a/gcloud/beta/bigtable/materialized-views/describe b/gcloud/beta/bigtable/materialized-views/describe new file mode 100644 index 000000000..2ebee63b2 --- /dev/null +++ b/gcloud/beta/bigtable/materialized-views/describe @@ -0,0 +1,65 @@ +NAME + gcloud beta bigtable materialized-views describe - describe an existing + Bigtable materialized view + +SYNOPSIS + gcloud beta bigtable materialized-views describe + (MATERIALIZED_VIEW : --instance=INSTANCE) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Describe an existing Bigtable materialized view. + +EXAMPLES + To view a materialized view's description, run: + + $ gcloud beta bigtable materialized-views describe \ + my-materialized-view-id --instance=my-instance-id + +POSITIONAL ARGUMENTS + Materialized view resource - The materialized view 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 materialized_view 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. + + MATERIALIZED_VIEW + ID of the materialized view or fully qualified identifier for the + materialized view. + + To set the name attribute: + ▸ provide the argument materialized_view on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --instance=INSTANCE + Bigtable instance for the materialized view. + + To set the instance attribute: + ▸ provide the argument materialized_view on the command line with a + fully specified name; + ▸ provide the argument --instance 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 beta and might change without notice. These + variants are also available: + + $ gcloud bigtable materialized-views describe + + $ gcloud alpha bigtable materialized-views describe + diff --git a/gcloud/beta/bigtable/materialized-views/help b/gcloud/beta/bigtable/materialized-views/help new file mode 100644 index 000000000..cf9154e34 --- /dev/null +++ b/gcloud/beta/bigtable/materialized-views/help @@ -0,0 +1,41 @@ +NAME + gcloud beta bigtable materialized-views - manage Bigtable materialized + views + +SYNOPSIS + gcloud beta bigtable materialized-views COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Manage Bigtable materialized views. + +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 new Bigtable materialized view. + + delete + (BETA) Delete a Bigtable materialized view. + + describe + (BETA) Describe an existing Bigtable materialized view. + + list + (BETA) List existing Bigtable materialized views. + + update + (BETA) Update a Bigtable materialized view. + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud bigtable materialized-views + + $ gcloud alpha bigtable materialized-views + diff --git a/gcloud/beta/bigtable/materialized-views/list b/gcloud/beta/bigtable/materialized-views/list new file mode 100644 index 000000000..4573e705e --- /dev/null +++ b/gcloud/beta/bigtable/materialized-views/list @@ -0,0 +1,85 @@ +NAME + gcloud beta bigtable materialized-views list - list existing Bigtable + materialized views + +SYNOPSIS + gcloud beta bigtable materialized-views list --instance=INSTANCE + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) List existing Bigtable materialized views. + +EXAMPLES + To list all materialized views for an instance, run: + + $ gcloud beta bigtable materialized-views list \ + --instance=my-instance-id + +REQUIRED FLAGS + Instance resource - The instance to list materialized views for. This + represents a Cloud resource. (NOTE) Some attributes are not given + arguments in this group but can be set in other ways. + + To set the project attribute: + ◆ provide the argument --instance on the command line with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + --instance=INSTANCE + ID of the instance or fully qualified identifier for the instance. + + To set the instance attribute: + ▸ provide the argument --instance on the command line. + +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 bigtable materialized-views list + + $ gcloud alpha bigtable materialized-views list + diff --git a/gcloud/beta/bigtable/materialized-views/update b/gcloud/beta/bigtable/materialized-views/update new file mode 100644 index 000000000..09fe64bc3 --- /dev/null +++ b/gcloud/beta/bigtable/materialized-views/update @@ -0,0 +1,75 @@ +NAME + gcloud beta bigtable materialized-views update - update a Bigtable + materialized view + +SYNOPSIS + gcloud beta bigtable materialized-views update + (MATERIALIZED_VIEW : --instance=INSTANCE) + --deletion-protection=DELETION_PROTECTION [--async] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Update a Bigtable materialized view. + +EXAMPLES + To update a materialized view, run: $ gcloud beta bigtable materialized-views update \ + my-materialized-view-id --instance=my-instance-id \ + --deletion-protection=true" + +POSITIONAL ARGUMENTS + Materialized view resource - The materialized view 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 materialized_view 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. + + MATERIALIZED_VIEW + ID of the materialized view or fully qualified identifier for the + materialized view. + + To set the name attribute: + ▸ provide the argument materialized_view on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --instance=INSTANCE + Bigtable instance for the materialized view. + + To set the instance attribute: + ▸ provide the argument materialized_view on the command line with a + fully specified name; + ▸ provide the argument --instance on the command line. + +REQUIRED FLAGS + --deletion-protection=DELETION_PROTECTION + Whether the view is protected from deletion. + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud bigtable materialized-views update + + $ gcloud alpha bigtable materialized-views update + diff --git a/gcloud/beta/bigtable/tables/create b/gcloud/beta/bigtable/tables/create index 31900c0fd..49dfd2d8e 100644 --- a/gcloud/beta/bigtable/tables/create +++ b/gcloud/beta/bigtable/tables/create @@ -5,7 +5,9 @@ SYNOPSIS gcloud beta bigtable tables create (TABLE : --instance=INSTANCE) --column-families=[COLUMN_FAMILIES,...] [--change-stream-retention-period=CHANGE_STREAM_RETENTION_PERIOD] - [--deletion-protection] [--splits=[SPLITS,...]] + [--deletion-protection] + [--row-key-schema-definition-file=ROW_KEY_SCHEMA_DEFINITION_FILE] + [--row-key-schema-pre-encoded-bytes] [--splits=[SPLITS,...]] [--automated-backup-retention-period=AUTOMATED_BACKUP_RETENTION_PERIOD | --enable-automated-backup] [GCLOUD_WIDE_FLAG ...] @@ -124,6 +126,34 @@ OPTIONAL FLAGS --deletion-protection Once specified, the table is deletion protected. + --row-key-schema-definition-file=ROW_KEY_SCHEMA_DEFINITION_FILE + The row key schema for the table. The schema is defined in a YAML or + JSON file, equivalent to the StructType protobuf message. + + Example YAML: + + encoding: + delimitedBytes: + delimiter: '#' + fields: + - fieldName: field1 + type: + bytesType: + encoding: + raw: {} + - fieldName: field2 + type: + bytesType: + encoding: + raw: {} + + --row-key-schema-pre-encoded-bytes + By default, Base64 encoding is applied to all binary fields in the + YAML/JSON file (for example, encoding.delimitedBytes.delimiter). + + Use this to indicate that all binary fields are already encoded in the + YAML/JSON file and should not be encoded again. + --splits=[SPLITS,...] Row keys where the table should initially be split. For example: car,key diff --git a/gcloud/beta/bigtable/tables/update b/gcloud/beta/bigtable/tables/update index 12159df04..607deabfe 100644 --- a/gcloud/beta/bigtable/tables/update +++ b/gcloud/beta/bigtable/tables/update @@ -4,11 +4,14 @@ NAME SYNOPSIS gcloud beta bigtable tables update (TABLE : --instance=INSTANCE) [--async] - [--deletion-protection] + [--deletion-protection] [--row-key-schema-pre-encoded-bytes] [--automated-backup-retention-period=AUTOMATED_BACKUP_RETENTION_PERIOD | --disable-automated-backup | --enable-automated-backup] [--change-stream-retention-period=CHANGE_STREAM_RETENTION_PERIOD - | --clear-change-stream-retention-period] [GCLOUD_WIDE_FLAG ...] + | --clear-change-stream-retention-period] + [--clear-row-key-schema + | --row-key-schema-definition-file=ROW_KEY_SCHEMA_DEFINITION_FILE] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) Update an existing new Cloud Bigtable table with the specified @@ -92,6 +95,16 @@ FLAGS --deletion-protection Once specified, the table is deletion protected. + --row-key-schema-pre-encoded-bytes + By default, Base64 encoding is applied to all binary fields in the + YAML/JSON file (for example, encoding.delimitedBytes.delimiter). + + Use this to indicate that all binary fields are already encoded in the + YAML/JSON file and should not be encoded again. + + This field is only used when row-key-schema-definition-file is set. It + is ignored if clear-row-key-schema is set. + At most one of these can be specified: --automated-backup-retention-period=AUTOMATED_BACKUP_RETENTION_PERIOD @@ -120,6 +133,35 @@ FLAGS This disables the change stream and eventually removes the change stream data. + Whether to update or clear the row key schema in the updated table. Only + one of these flags can be set. + + At most one of these can be specified: + + --clear-row-key-schema + Whether to clear the row key schema in the updated table. + + --row-key-schema-definition-file=ROW_KEY_SCHEMA_DEFINITION_FILE + The row key schema for the table. The schema is defined in a YAML or + JSON file, equivalent to the StructType protobuf message. + + Example YAML: + + encoding: + delimitedBytes: + delimiter: '#' + fields: + - fieldName: field1 + type: + bytesType: + encoding: + raw: {} + - fieldName: field2 + type: + bytesType: + encoding: + raw: {} + 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/commitments/create b/gcloud/beta/compute/commitments/create index 0c46d46a6..f84f06b31 100644 --- a/gcloud/beta/compute/commitments/create +++ b/gcloud/beta/compute/commitments/create @@ -107,13 +107,13 @@ OPTIONAL FLAGS Type of commitment. memory-optimized indicates that the commitment is for memory-optimized VMs. TYPE must be one of: accelerator-optimized, accelerator-optimized-a3, accelerator-optimized-a3-mega, - accelerator-optimized-a3-ultra, compute-optimized, - compute-optimized-c2d, compute-optimized-c3, compute-optimized-c3d, - compute-optimized-h3, general-purpose, general-purpose-c4, - general-purpose-c4a, general-purpose-e2, general-purpose-n2, - general-purpose-n2d, general-purpose-n4, general-purpose-t2d, - graphics-optimized, memory-optimized, memory-optimized-m3, - memory-optimized-m4, memory-optimized-x4-16tb, + accelerator-optimized-a3-ultra, accelerator-optimized-a4, + compute-optimized, compute-optimized-c2d, compute-optimized-c3, + compute-optimized-c3d, compute-optimized-h3, general-purpose, + general-purpose-c4, general-purpose-c4a, general-purpose-e2, + general-purpose-n2, general-purpose-n2d, general-purpose-n4, + general-purpose-t2d, graphics-optimized, memory-optimized, + memory-optimized-m3, memory-optimized-m4, memory-optimized-x4-16tb, memory-optimized-x4-24tb, memory-optimized-x4-32tb, storage-optimized-z3. @@ -257,15 +257,23 @@ OPTIONAL FLAGS Manage the properties of a shared reservation to create --share-setting=SHARE_SETTING - Specify if this reservation is shared, and if so, the type of - sharing. If you omit this flag, this value is local (not shared) - by default. SHARE_SETTING must be one of: local, projects. + The projects that can use the reservation. SHARE_SETTING must be + one of: + + local + Only your project can use the reservation. This is the + default value. + projects + Your project and up to 100 other projects within your + project's organization can use the reservation. If you + specify this value, then you must also include the + --share-with flag in the command. --share-with=SHARE_WITH,[SHARE_WITH,...] - If this reservation is shared (--share-setting is not local), - provide a list of all of the specific projects that this - reservation is shared with. List must contain project IDs or - project numbers. + If this reservation is shared (--share-setting=projects), then + specify a comma-separated list of projects to share the + reservation with. List projects using project IDs or project + numbers. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/beta/compute/commitments/update-reservations b/gcloud/beta/compute/commitments/update-reservations index 0c2f27e93..29c4e7aea 100644 --- a/gcloud/beta/compute/commitments/update-reservations +++ b/gcloud/beta/compute/commitments/update-reservations @@ -155,15 +155,22 @@ FLAGS The size of the local SSD in base-2 GB. --dest-share-setting=DEST_SHARE_SETTING - Specify if this reservation is shared, and if so, the type of - sharing. If you omit this flag, this value is local (not shared) by - default. DEST_SHARE_SETTING must be one of: local, projects. + The projects that can use the reservation. DEST_SHARE_SETTING must + be one of: + + local + Only your project can use the reservation. This is the default + value. + projects + Your project and up to 100 other projects within your project's + organization can use the reservation. If you specify this + value, then you must also include the --share-with flag in the + command. --dest-share-with=SHARE_WITH,[SHARE_WITH,...] - If this reservation is shared (--share-setting is not local), - provide a list of all of the specific projects that this - reservation is shared with. List must contain project IDs or - project numbers. + If this reservation is shared (--share-setting=projects), then + specify a comma-separated list of projects to share the reservation + with. List projects using project IDs or project numbers. --source-accelerator=[count=COUNT],[type=TYPE] Manage the configuration of the type and number of accelerator @@ -190,15 +197,22 @@ FLAGS The size of the local SSD in base-2 GB. --source-share-setting=SOURCE_SHARE_SETTING - Specify if this reservation is shared, and if so, the type of - sharing. If you omit this flag, this value is local (not shared) by - default. SOURCE_SHARE_SETTING must be one of: local, projects. + The projects that can use the reservation. SOURCE_SHARE_SETTING + must be one of: + + local + Only your project can use the reservation. This is the default + value. + projects + Your project and up to 100 other projects within your project's + organization can use the reservation. If you specify this + value, then you must also include the --share-with flag in the + command. --source-share-with=SHARE_WITH,[SHARE_WITH,...] - If this reservation is shared (--share-setting is not local), - provide a list of all of the specific projects that this - reservation is shared with. List must contain project IDs or - project numbers. + If this reservation is shared (--share-setting=projects), then + specify a comma-separated list of projects to share the reservation + with. List projects using project IDs or project numbers. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/beta/compute/config-ssh b/gcloud/beta/compute/config-ssh index 4dbd026ee..711b5df87 100644 --- a/gcloud/beta/compute/config-ssh +++ b/gcloud/beta/compute/config-ssh @@ -31,7 +31,9 @@ DESCRIPTION $ scp ~/MY-FILE example-instance.us-central1-a.MY-PROJECT:~ Whenever instances are added, removed, or their external IP addresses are - changed, this command should be re-executed to update the configuration. + changed, the remove command must be run to clear the existing configuration + and then the command can set executed to set the configuration to the + current state. This command ensures that the user's public SSH key is present in the project's metadata. If the user does not have a public SSH key, one is diff --git a/gcloud/beta/compute/images/list b/gcloud/beta/compute/images/list index 46035041b..d9453f1b1 100644 --- a/gcloud/beta/compute/images/list +++ b/gcloud/beta/compute/images/list @@ -60,7 +60,8 @@ FLAGS are available include the following: cos-cloud, debian-cloud, rocky-linux-cloud, ubuntu-os-cloud, centos-cloud, fedora-coreos-cloud, opensuse-cloud, oracle-linux-cloud, rhel-cloud, rhel-sap-cloud, - suse-cloud, suse-sap-cloud, ubuntu-os-pro-cloud, windows-cloud, + rocky-linux-accelerator-cloud, suse-cloud, suse-sap-cloud, + ubuntu-os-accelerator-images, ubuntu-os-pro-cloud, windows-cloud, windows-sql-cloud. Enabled by default, use --no-standard-images to disable. diff --git a/gcloud/beta/compute/instance-groups/managed/resize-requests/create b/gcloud/beta/compute/instance-groups/managed/resize-requests/create index 7fc7e4e9e..4a587392c 100644 --- a/gcloud/beta/compute/instance-groups/managed/resize-requests/create +++ b/gcloud/beta/compute/instance-groups/managed/resize-requests/create @@ -4,7 +4,8 @@ NAME SYNOPSIS gcloud beta compute instance-groups managed resize-requests create NAME - --resize-by=RESIZE_BY --resize-request=RESIZE_REQUEST_NAME + --resize-request=RESIZE_REQUEST_NAME + (--instances=INSTANCE,[INSTANCE,...] | --resize-by=RESIZE_BY) [--requested-run-duration=REQUESTED_RUN_DURATION] [--region=REGION | --zone=ZONE] [GCLOUD_WIDE_FLAG ...] @@ -24,12 +25,21 @@ POSITIONAL ARGUMENTS Name of the managed instance group to operate on. REQUIRED FLAGS - --resize-by=RESIZE_BY - The number of VMs to resize managed instance group by. - --resize-request=RESIZE_REQUEST_NAME The name of the resize request to create. + Exactly one of these must be specified: + + --instances=INSTANCE,[INSTANCE,...] + A comma-separated list of instance names. The number of names you + provide determines the number of instances to create with this resize + request. The group's target size increases by this count. + + --resize-by=RESIZE_BY + The number of instances to create with this resize request. Instances + have automatically-generated names. The group's target size increases + by this number. + OPTIONAL FLAGS --requested-run-duration=REQUESTED_RUN_DURATION The time you need the requested VMs to run before being automatically @@ -39,8 +49,9 @@ OPTIONAL FLAGS day, 2 hours, 3 minutes, and 4 seconds. The value must be between 10m (10 minutes) and 7d (7 days). - If you want the managed instance group to consume a reservation, then - this flag is optional. Otherwise, it's required. + If you want the managed instance group to consume a reservation or use + FLEX_START provisioning model, then this flag is optional. Otherwise, + it's required. At most one of these can be specified: diff --git a/gcloud/beta/compute/network-firewall-policies/rules/create b/gcloud/beta/compute/network-firewall-policies/rules/create index 43eb4cd87..93795cabd 100644 --- a/gcloud/beta/compute/network-firewall-policies/rules/create +++ b/gcloud/beta/compute/network-firewall-policies/rules/create @@ -146,7 +146,7 @@ OPTIONAL FLAGS --src-region-codes=[SOURCE_REGION_CODES,...] Source Region Code to match for this rule. Can only be specified if - DIRECTION is ingress. Cannot be specified when the source network scope + DIRECTION is ingress. Cannot be specified when the source network type is NON_INTERNET, VPC_NETWORK or INTRA_VPC. --src-secure-tags=[SOURCE_SECURE_TAGS,...] diff --git a/gcloud/beta/compute/network-firewall-policies/rules/update b/gcloud/beta/compute/network-firewall-policies/rules/update index 33ac2ff7b..56f291346 100644 --- a/gcloud/beta/compute/network-firewall-policies/rules/update +++ b/gcloud/beta/compute/network-firewall-policies/rules/update @@ -142,7 +142,7 @@ OPTIONAL FLAGS --src-region-codes=[SOURCE_REGION_CODES,...] Source Region Code to match for this rule. Can only be specified if - DIRECTION is ingress. Cannot be specified when the source network scope + DIRECTION is ingress. Cannot be specified when the source network type is NON_INTERNET, VPC_NETWORK or INTRA_VPC. --src-secure-tags=[SOURCE_SECURE_TAGS,...] diff --git a/gcloud/beta/compute/reservations/create b/gcloud/beta/compute/reservations/create index 8b9629857..253af8ceb 100644 --- a/gcloud/beta/compute/reservations/create +++ b/gcloud/beta/compute/reservations/create @@ -175,14 +175,21 @@ OPTIONAL FLAGS Manage the properties of a shared reservation. --share-setting=SHARE_SETTING - Specify if this reservation is shared, and if so, the type of - sharing. If you omit this flag, this value is local (not shared) by - default. SHARE_SETTING must be one of: local, projects. + The projects that can use the reservation. SHARE_SETTING must be one + of: + + local + Only your project can use the reservation. This is the default + value. + projects + Your project and up to 100 other projects within your project's + organization can use the reservation. If you specify this value, + then you must also include the --share-with flag in the command. --share-with=SHARE_WITH,[SHARE_WITH,...] - If this reservation is shared (--share-setting is not local), provide - a list of all of the specific projects that this reservation is - shared with. List must contain project IDs or project numbers. + If this reservation is shared (--share-setting=projects), then + specify a comma-separated list of projects to share the reservation + with. List projects using project IDs or project numbers. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/beta/compute/reservations/update b/gcloud/beta/compute/reservations/update index eb6ac2db4..a63a6d612 100644 --- a/gcloud/beta/compute/reservations/update +++ b/gcloud/beta/compute/reservations/update @@ -7,6 +7,7 @@ SYNOPSIS [--add-share-with=PROJECT,[PROJECT,...]] [--remove-share-with=PROJECT,[PROJECT,...]] [--reservation-sharing-policy=RESERVATION_SHARING_POLICY] + [--share-setting=SHARE_SETTING] [--share-with=SHARE_WITH,[SHARE_WITH,...]] [--vm-count=VM_COUNT] [--zone=ZONE] [--delete-after-duration=DELETE_AFTER_DURATION @@ -51,9 +52,9 @@ POSITIONAL ARGUMENTS FLAGS --add-share-with=PROJECT,[PROJECT,...] - A list of specific projects to add to the list of projects that this - reservation is shared with. List must contain project IDs or project - numbers. + If this reservation is shared (--share-setting is projects), then + specify a comma-separated list of projects to share the reservation + with. You must list the projects using project IDs or project numbers. --remove-share-with=PROJECT,[PROJECT,...] A list of specific projects to remove from the list of projects that @@ -70,10 +71,22 @@ FLAGS The reservation won't be shared with Google Cloud services. If you omit this flag during creation, the default value is DISALLOW_ALL. + --share-setting=SHARE_SETTING + The projects that can use the reservation. SHARE_SETTING must be one + of: + + local + Only your project can use the reservation. This is the default + value. + projects + Your project and up to 100 other projects within your project's + organization can use the reservation. If you specify this value, + then you must also include the --share-with flag in the command. + --share-with=SHARE_WITH,[SHARE_WITH,...] - If this reservation is shared (--share-setting is not local), provide a - list of all of the specific projects that this reservation is shared - with. List must contain project IDs or project numbers. + If this reservation is shared (--share-setting=projects), then specify + a comma-separated list of projects to share the reservation with. List + projects using project IDs or project numbers. --vm-count=VM_COUNT The number of VM instances that are allocated to this reservation. The diff --git a/gcloud/beta/compute/routers/nats/create b/gcloud/beta/compute/routers/nats/create index 540f28d1d..d0e26ad69 100644 --- a/gcloud/beta/compute/routers/nats/create +++ b/gcloud/beta/compute/routers/nats/create @@ -221,8 +221,8 @@ OPTIONAL FLAGS --nat-external-ip-pool=IP_ADDRESS,[IP_ADDRESS,...] External IP Addresses to use for Cloud NAT - IPv4 subnetwork range options. If they are not specified, one of IPv6 - subnetwork range option has to be provided. + Options for IPv4 subnetwork ranges. If not specified, one of the options + for IPv6 subnetwork ranges must be provided. At most one of these can be specified: @@ -246,16 +246,16 @@ OPTIONAL FLAGS Allow only primary IP ranges of all subnetworks in the region to use NAT. - IPv6 subnetwork range options. If they are not specified, one of IPv4 - subnetwork range option has to be provided. + Options for IPv6 subnetwork ranges. If not specified, one of the options + for IPv4 subnetwork ranges must be provided. At most one of these can be specified: --nat64-all-v6-subnet-ip-ranges - Allow all ip ranges of ipv6 subnetworks in the region to use NAT. + Allow all IPv6 subnetwork ranges in the region to use NAT. --nat64-custom-v6-subnet-ip-ranges=SUBNETWORK,[SUBNETWORK,...] - List of ipv6 subnetworks to be allowed tp use NAT. + List of subnetworks with IPv6 ranges to be allowed to use NAT. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/beta/compute/routers/nats/update b/gcloud/beta/compute/routers/nats/update index cf24917ac..5393028a0 100644 --- a/gcloud/beta/compute/routers/nats/update +++ b/gcloud/beta/compute/routers/nats/update @@ -209,12 +209,12 @@ OPTIONAL FLAGS These IPs must be valid external IPs that have been used as NAT IPs - IPv4 subnetwork range options. + Options for IPv4 subnetwork ranges. At most one of these can be specified: --clear-nat-subnet-ip-ranges - Clear options related to the NAT's subnet ranges. + Clear IPv4 subnetwork ranges. --nat-all-subnet-ip-ranges Allow all IP ranges of all subnetworks in the region, including @@ -236,18 +236,18 @@ OPTIONAL FLAGS Allow only primary IP ranges of all subnetworks in the region to use NAT. - IPv6 subnetwork range options. + Options for IPv6 subnetwork ranges. At most one of these can be specified: --clear-nat64-subnet-ip-ranges - Clear options related to the NAT64's subnet ranges. + Clear IPv6 subnetwork ranges. --nat64-all-v6-subnet-ip-ranges - Allow all ip ranges of ipv6 subnetworks in the region to use NAT. + Allow all IPv6 subnetwork ranges in the region to use NAT. --nat64-custom-v6-subnet-ip-ranges=SUBNETWORK,[SUBNETWORK,...] - List of ipv6 subnetworks to be allowed tp use NAT. + List of subnetworks with IPv6 ranges to be allowed to use NAT. At most one of these can be specified: diff --git a/gcloud/beta/container/backup-restore/backup-channels/create b/gcloud/beta/container/backup-restore/backup-channels/create new file mode 100644 index 000000000..d2c737b2f --- /dev/null +++ b/gcloud/beta/container/backup-restore/backup-channels/create @@ -0,0 +1,102 @@ +NAME + gcloud beta container backup-restore backup-channels create - create a + backup channel + +SYNOPSIS + gcloud beta container backup-restore backup-channels create + (BACKUP_CHANNEL : --location=LOCATION) + --destination-project=DESTINATION_PROJECT [--async] + [--description=DESCRIPTION] [--labels=[KEY=VALUE,...]] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Create a Backup for GKE backup channel. + +EXAMPLES + To create a backup channel my-backup-channel in project my-project in + location us-central1 with destination project projects/1234567890, run: + + $ gcloud beta container backup-restore backup-channels create \ + my-backup-channel --project=my-project --location=us-central1 \ + --destination_project=projects/1234567890 + +POSITIONAL ARGUMENTS + Backup channel resource - Name of the backup channel to create. Once the + channel is created, this name can't be changed. This must be 63 or fewer + characters long and must be unique within the project and location. The + name may be provided either as a relative name, e.g. + projects//locations//backupChannels/ or + as a single ID name (with the parent resources provided via options or + through properties), e.g. BACKUP_CHANNEL --project= + --location=. 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 backup_channel 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. + + BACKUP_CHANNEL + ID of the backup channel or fully qualified identifier for the backup + channel. + + To set the backup_channel attribute: + ▸ provide the argument backup_channel on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + Google Cloud location. + + To set the location attribute: + ▸ provide the argument backup_channel on the command line with a + fully specified name; + ▸ provide the argument --location on the command line; + ▸ set the property gkebackup/location. + +REQUIRED FLAGS + --destination-project=DESTINATION_PROJECT + The project where Backups are allowed to be created. The format is + projects/{project}. Currently, {project} can only be the project + number. e.g. projects/1234567890. + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --description=DESCRIPTION + The description of the backup channel. + + --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 gkebackup/v1 API. The full documentation for this API + can be found at: + https://cloud.google.com/kubernetes-engine/docs/add-on/backup-for-gke + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha container backup-restore backup-channels create + diff --git a/gcloud/beta/container/backup-restore/backup-channels/delete b/gcloud/beta/container/backup-restore/backup-channels/delete new file mode 100644 index 000000000..d72df8363 --- /dev/null +++ b/gcloud/beta/container/backup-restore/backup-channels/delete @@ -0,0 +1,85 @@ +NAME + gcloud beta container backup-restore backup-channels delete - delete a + backup channel + +SYNOPSIS + gcloud beta container backup-restore backup-channels delete + (BACKUP_CHANNEL : --location=LOCATION) [--async] [--etag=ETAG] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Delete a Backup for GKE backup channel. + +EXAMPLES + To delete a backup channel my-backup-channel in project my-project in + location us-central1, run: + + $ gcloud beta container backup-restore backup-channels delete \ + my-backup-channel --project=my-project --location=us-central1 + +POSITIONAL ARGUMENTS + Backup channel resource - Name of the backup channel to delete. The name + may be provided either as a relative name, e.g. + projects//locations//backupChannels/ or + as a single ID name (with the parent resources provided via options or + through properties), e.g. BACKUP_CHANNEL --project= + --location=. 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 backup_channel 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. + + BACKUP_CHANNEL + ID of the backup channel or fully qualified identifier for the backup + channel. + + To set the backup_channel attribute: + ▸ provide the argument backup_channel on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + Google Cloud location. + + To set the location attribute: + ▸ provide the argument backup_channel on the command line with a + fully specified name; + ▸ provide the argument --location on the command line; + ▸ set the property gkebackup/location. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --etag=ETAG + The etag is used for optimistic concurrency control as a way to help + prevent simultaneous updates or deletes of a resource from overwriting + each other. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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 gkebackup/v1 API. The full documentation for this API + can be found at: + https://cloud.google.com/kubernetes-engine/docs/add-on/backup-for-gke + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha container backup-restore backup-channels delete + diff --git a/gcloud/beta/container/backup-restore/backup-channels/describe b/gcloud/beta/container/backup-restore/backup-channels/describe new file mode 100644 index 000000000..f381aacda --- /dev/null +++ b/gcloud/beta/container/backup-restore/backup-channels/describe @@ -0,0 +1,74 @@ +NAME + gcloud beta container backup-restore backup-channels describe - describe a + backup channel + +SYNOPSIS + gcloud beta container backup-restore backup-channels describe + (BACKUP_CHANNEL : --location=LOCATION) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Describe a Backup for GKE backup channel. + +EXAMPLES + To describe a backup channel my-backup-channel in project my-project in + location us-central1, run: + + $ gcloud beta container backup-restore backup-channels describe \ + my-backup-channel --project=my-project --location=us-central1 + +POSITIONAL ARGUMENTS + Backup channel resource - Name of the backup channel to describe. The name + may be provided either as a relative name, e.g. + projects//locations//backupChannels/ or + as a single ID name (with the parent resources provided via options or + through properties), e.g. BACKUP_CHANNEL --project= + --location= 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 backup_channel 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. + + BACKUP_CHANNEL + ID of the backup channel or fully qualified identifier for the backup + channel. + + To set the backup_channel attribute: + ▸ provide the argument backup_channel on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + Google Cloud location. + + To set the location attribute: + ▸ provide the argument backup_channel on the command line with a + fully specified name; + ▸ provide the argument --location on the command line; + ▸ set the property gkebackup/location. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the gkebackup/v1 API. The full documentation for this API + can be found at: + https://cloud.google.com/kubernetes-engine/docs/add-on/backup-for-gke + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha container backup-restore backup-channels describe + diff --git a/gcloud/beta/container/backup-restore/backup-channels/help b/gcloud/beta/container/backup-restore/backup-channels/help new file mode 100644 index 000000000..347b4762c --- /dev/null +++ b/gcloud/beta/container/backup-restore/backup-channels/help @@ -0,0 +1,40 @@ +NAME + gcloud beta container backup-restore backup-channels - backup for GKE + Backup Channels + +SYNOPSIS + gcloud beta container backup-restore backup-channels COMMAND + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Backup for GKE Backup Channels. + +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 backup channel. + + delete + (BETA) Delete a backup channel. + + describe + (BETA) Describe a backup channel. + + list + (BETA) List backup channels. + + update + (BETA) Update a backup channel. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha container backup-restore backup-channels + diff --git a/gcloud/beta/container/backup-restore/backup-channels/list b/gcloud/beta/container/backup-restore/backup-channels/list new file mode 100644 index 000000000..d6530d0a6 --- /dev/null +++ b/gcloud/beta/container/backup-restore/backup-channels/list @@ -0,0 +1,98 @@ +NAME + gcloud beta container backup-restore backup-channels list - list backup + channels + +SYNOPSIS + gcloud beta container backup-restore backup-channels list + [--location=LOCATION] [--filter=EXPRESSION] [--limit=LIMIT] + [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) List Backup for GKE backup channels. + +EXAMPLES + To list all backup channels in project my-project in location us-central1, + run: + + $ gcloud beta container backup-restore backup-channels list \ + --project=my-project --location=us-central1 + + To list all backup channels in project my-project across all locations, + run: + + $ gcloud beta container backup-restore backup-channels list \ + --project=my-project + +FLAGS + Location resource - Name of the location from which to list backup + channels (provided via options or through properties): --project= + --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 gkebackup/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; + ▸ set the property gkebackup/location. + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + + --uri + Print a list of resource URIs instead of the default output, and change + the command output to a list of URIs. If this flag is used with + --format, the formatting is applied on this URI list. To display URIs + alongside other keys instead, use the uri() transform. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the gkebackup/v1 API. The full documentation for this API + can be found at: + https://cloud.google.com/kubernetes-engine/docs/add-on/backup-for-gke + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha container backup-restore backup-channels list + diff --git a/gcloud/beta/container/backup-restore/backup-channels/update b/gcloud/beta/container/backup-restore/backup-channels/update new file mode 100644 index 000000000..9a2d7b691 --- /dev/null +++ b/gcloud/beta/container/backup-restore/backup-channels/update @@ -0,0 +1,121 @@ +NAME + gcloud beta container backup-restore backup-channels update - update a + backup channel + +SYNOPSIS + gcloud beta container backup-restore backup-channels update + (BACKUP_CHANNEL : --location=LOCATION) [--async] + [--description=DESCRIPTION] [--etag=ETAG] + [--update-labels=[KEY=VALUE,...]] + [--clear-labels | --remove-labels=[KEY,...]] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Update a Backup for GKE backup channel. + +EXAMPLES + To update a backup channel my-backup-channel in project my-project in + location us-central1 to add new description, run: + + $ gcloud beta container backup-restore backup-channels update \ + my-backup-channel --project=my-project --location=us-central1 \ + --description="New description" + +POSITIONAL ARGUMENTS + Backup channel resource - Name of the backup channel to update. The name + may be provided either as a relative name, e.g. + projects//locations//backupChannels/ or + as a single ID name (with the parent resources provided via options or + through properties), e.g. BACKUP_CHANNEL --project= + --location=. 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 backup_channel 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. + + BACKUP_CHANNEL + ID of the backup channel or fully qualified identifier for the backup + channel. + + To set the backup_channel attribute: + ▸ provide the argument backup_channel on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + Google Cloud location. + + To set the location attribute: + ▸ provide the argument backup_channel on the command line with a + fully specified name; + ▸ provide the argument --location on the command line; + ▸ set the property gkebackup/location. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --description=DESCRIPTION + The description of the backup channel. + + --etag=ETAG + The etag is used for optimistic concurrency control as a way to help + prevent simultaneous updates or deletes of a resource from overwriting + each other. + + --update-labels=[KEY=VALUE,...] + List of label KEY=VALUE pairs to update. If a label exists, its value + is modified. Otherwise, a new label is created. + + Keys must start with a lowercase character and contain only hyphens + (-), underscores (_), lowercase characters, and numbers. Values must + contain only hyphens (-), underscores (_), lowercase characters, and + numbers. + + At most one of these can be specified: + + --clear-labels + Remove all labels. If --update-labels is also specified then + --clear-labels is applied first. + + For example, to remove all labels: + + $ gcloud beta container backup-restore backup-channels update \ + --clear-labels + + To remove all existing labels and create two new labels, foo and baz: + + $ gcloud beta container backup-restore backup-channels 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 gkebackup/v1 API. The full documentation for this API + can be found at: + https://cloud.google.com/kubernetes-engine/docs/add-on/backup-for-gke + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha container backup-restore backup-channels update + diff --git a/gcloud/beta/container/backup-restore/backup-plan-bindings/describe b/gcloud/beta/container/backup-restore/backup-plan-bindings/describe new file mode 100644 index 000000000..396d32961 --- /dev/null +++ b/gcloud/beta/container/backup-restore/backup-plan-bindings/describe @@ -0,0 +1,88 @@ +NAME + gcloud beta container backup-restore backup-plan-bindings describe - + describe a backup plan binding + +SYNOPSIS + gcloud beta container backup-restore backup-plan-bindings describe + (BACKUP_PLAN_BINDING + : --backup-channel=BACKUP_CHANNEL --location=LOCATION) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Describe a Backup for GKE backup plan binding. + +EXAMPLES + To describe a backup plan binding my-backup-plan-binding in project + my-project in location us-central1 under backup channel my-backup-channel, + run: + + $ gcloud beta container backup-restore backup-plan-bindings \ + describe my-backup-plan-binding \ + --backup-channel=my-backup-channel --project=my-project \ + --location=us-central1 + +POSITIONAL ARGUMENTS + Backup plan binding resource - Name of the backup plan binding to + describe. The name may be provided either as a relative name, e.g. + projects//locations//backupChannels//backupPlanBindings/ + or as a single ID name (with the parent resources provided via options or + through properties), e.g. BACKUP_PLAN_BINDING --project= + --location= --backup-channel=. 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 backup_plan_binding 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. + + BACKUP_PLAN_BINDING + ID of the backup plan binding or fully qualified identifier for the + backup plan binding. + + To set the backup_plan_binding attribute: + ▸ provide the argument backup_plan_binding on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --backup-channel=BACKUP_CHANNEL + Backup Channel name. + + To set the backup-channel attribute: + ▸ provide the argument backup_plan_binding on the command line with + a fully specified name; + ▸ provide the argument --backup-channel on the command line. + + --location=LOCATION + Google Cloud location. + + To set the location attribute: + ▸ provide the argument backup_plan_binding on the command line with + a fully specified name; + ▸ provide the argument --location on the command line; + ▸ set the property gkebackup/location. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the gkebackup/v1 API. The full documentation for this API + can be found at: + https://cloud.google.com/kubernetes-engine/docs/add-on/backup-for-gke + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha container backup-restore backup-plan-bindings describe + diff --git a/gcloud/beta/container/backup-restore/backup-plan-bindings/help b/gcloud/beta/container/backup-restore/backup-plan-bindings/help new file mode 100644 index 000000000..c536ff5c0 --- /dev/null +++ b/gcloud/beta/container/backup-restore/backup-plan-bindings/help @@ -0,0 +1,31 @@ +NAME + gcloud beta container backup-restore backup-plan-bindings - backup for GKE + Backup Plan Bindings + +SYNOPSIS + gcloud beta container backup-restore backup-plan-bindings COMMAND + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Backup for GKE Backup Plan Bindings. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + describe + (BETA) Describe a backup plan binding. + + list + (BETA) List backup plan bindings. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha container backup-restore backup-plan-bindings + diff --git a/gcloud/beta/container/backup-restore/backup-plan-bindings/list b/gcloud/beta/container/backup-restore/backup-plan-bindings/list new file mode 100644 index 000000000..bec86d6c1 --- /dev/null +++ b/gcloud/beta/container/backup-restore/backup-plan-bindings/list @@ -0,0 +1,113 @@ +NAME + gcloud beta container backup-restore backup-plan-bindings list - list + backup plan bindings + +SYNOPSIS + gcloud beta container backup-restore backup-plan-bindings list + (--backup-channel=BACKUP_CHANNEL : --location=LOCATION) + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) List Backup Plan Bindings for GKE backup plan bindings. + +EXAMPLES + To list all backup plan bindings in project my-project in location + us-central1 under backup channel my-backup-channel, run: + + $ gcloud beta container backup-restore backup-plan-bindings list \ + --backup-channel=my-backup-channel --project=my-project \ + --location=us-central1 + + To list all backup plan bindings in project my-project across all locations + under all backup channels, run: + + $ gcloud beta container backup-restore backup-plan-bindings list \ + --project=my-project + +REQUIRED FLAGS + Backup channel resource - Name of the backup channel from which to list + backup plan bindings (provided via options or through properties), e.g. + --project= --location= + --backup-channel=. 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 --backup-channel 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. + + --backup-channel=BACKUP_CHANNEL + ID of the backup channel or fully qualified identifier for the backup + channel. + + To set the backup-channel attribute: + ▸ provide the argument --backup-channel on the command line. + + This flag argument must be specified if any of the other arguments in + this group are specified. + + --location=LOCATION + Google Cloud location. + + To set the location attribute: + ▸ provide the argument --backup-channel on the command line with a + fully specified name; + ▸ provide the argument --location on the command line; + ▸ set the property gkebackup/location. + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + + --uri + Print a list of resource URIs instead of the default output, and change + the command output to a list of URIs. If this flag is used with + --format, the formatting is applied on this URI list. To display URIs + alongside other keys instead, use the uri() transform. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the gkebackup/v1 API. The full documentation for this API + can be found at: + https://cloud.google.com/kubernetes-engine/docs/add-on/backup-for-gke + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha container backup-restore backup-plan-bindings list + diff --git a/gcloud/beta/container/backup-restore/help b/gcloud/beta/container/backup-restore/help index 4325e5b0b..fc94a95c6 100644 --- a/gcloud/beta/container/backup-restore/help +++ b/gcloud/beta/container/backup-restore/help @@ -15,6 +15,12 @@ GCLOUD WIDE FLAGS GROUPS GROUP is one of the following: + backup-channels + (BETA) Backup for GKE Backup Channels. + + backup-plan-bindings + (BETA) Backup for GKE Backup Plan Bindings. + backup-plans (BETA) Backup for GKE Backup Plans. @@ -27,6 +33,12 @@ GROUPS operations (BETA) Backup for GKE Operations. + restore-channels + (BETA) Backup for GKE Restore Channels. + + restore-plan-bindings + (BETA) Backup for GKE Restore Plan Bindings. + restore-plans (BETA) Backup for GKE Restore Plans. diff --git a/gcloud/beta/container/backup-restore/restore-channels/create b/gcloud/beta/container/backup-restore/restore-channels/create new file mode 100644 index 000000000..eade4e89b --- /dev/null +++ b/gcloud/beta/container/backup-restore/restore-channels/create @@ -0,0 +1,102 @@ +NAME + gcloud beta container backup-restore restore-channels create - create a + restore channel + +SYNOPSIS + gcloud beta container backup-restore restore-channels create + (RESTORE_CHANNEL : --location=LOCATION) + --destination-project=DESTINATION_PROJECT [--async] + [--description=DESCRIPTION] [--labels=[KEY=VALUE,...]] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Create a Backup for GKE restore channel. + +EXAMPLES + To create a restore channel my-restore-channel in project my-project in + location us-central1 with destination project projects/1234567890, run: + + $ gcloud beta container backup-restore restore-channels create \ + my-restore-channel --project=my-project --location=us-central1 \ + --destination_project=projects/1234567890 + +POSITIONAL ARGUMENTS + Restore channel resource - Name of the restore channel to create. Once the + channel is created, this name can't be changed. This must be 63 or fewer + characters long and must be unique within the project and location. The + name may be provided either as a relative name, e.g. + projects//locations//restoreChannels/ + or as a single ID name (with the parent resources provided via options or + through properties), e.g. RESTORE_CHANNEL --project= + --location=. 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 restore_channel 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. + + RESTORE_CHANNEL + ID of the restore channel or fully qualified identifier for the + restore channel. + + To set the restore_channel attribute: + ▸ provide the argument restore_channel on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + Google Cloud location. + + To set the location attribute: + ▸ provide the argument restore_channel on the command line with a + fully specified name; + ▸ provide the argument --location on the command line; + ▸ set the property gkebackup/location. + +REQUIRED FLAGS + --destination-project=DESTINATION_PROJECT + The project where Restores are allowed to be created. The format is + projects/{project}. Currently, {project} can only be the project + number. e.g. projects/1234567890. + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --description=DESCRIPTION + The description of the restore channel. + + --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 gkebackup/v1 API. The full documentation for this API + can be found at: + https://cloud.google.com/kubernetes-engine/docs/add-on/backup-for-gke + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha container backup-restore restore-channels create + diff --git a/gcloud/beta/container/backup-restore/restore-channels/delete b/gcloud/beta/container/backup-restore/restore-channels/delete new file mode 100644 index 000000000..8bce7c83b --- /dev/null +++ b/gcloud/beta/container/backup-restore/restore-channels/delete @@ -0,0 +1,85 @@ +NAME + gcloud beta container backup-restore restore-channels delete - delete a + restore channel + +SYNOPSIS + gcloud beta container backup-restore restore-channels delete + (RESTORE_CHANNEL : --location=LOCATION) [--async] [--etag=ETAG] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Delete a Backup for GKE restore channel. + +EXAMPLES + To delete a restore channel my-restore-channel in project my-project in + location us-central1, run: + + $ gcloud beta container backup-restore restore-channels delete \ + my-restore-channel --project=my-project --location=us-central1 + +POSITIONAL ARGUMENTS + Restore channel resource - Name of the restore channel to delete. The name + may be provided either as a relative name, e.g. + projects//locations//restoreChannels/ + or as a single ID name (with the parent resources provided via options or + through properties), e.g. RESTORE_CHANNEL --project= + --location=. 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 restore_channel 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. + + RESTORE_CHANNEL + ID of the restore channel or fully qualified identifier for the + restore channel. + + To set the restore_channel attribute: + ▸ provide the argument restore_channel on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + Google Cloud location. + + To set the location attribute: + ▸ provide the argument restore_channel on the command line with a + fully specified name; + ▸ provide the argument --location on the command line; + ▸ set the property gkebackup/location. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --etag=ETAG + The etag is used for optimistic concurrency control as a way to help + prevent simultaneous updates or deletes of a resource from overwriting + each other. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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 gkebackup/v1 API. The full documentation for this API + can be found at: + https://cloud.google.com/kubernetes-engine/docs/add-on/backup-for-gke + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha container backup-restore restore-channels delete + diff --git a/gcloud/beta/container/backup-restore/restore-channels/describe b/gcloud/beta/container/backup-restore/restore-channels/describe new file mode 100644 index 000000000..55684424e --- /dev/null +++ b/gcloud/beta/container/backup-restore/restore-channels/describe @@ -0,0 +1,74 @@ +NAME + gcloud beta container backup-restore restore-channels describe - describe a + restore channel + +SYNOPSIS + gcloud beta container backup-restore restore-channels describe + (RESTORE_CHANNEL : --location=LOCATION) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Describe a Backup for GKE restore channel. + +EXAMPLES + To describe a restore channel my-restore-channel in project my-project in + location us-central1, run: + + $ gcloud beta container backup-restore restore-channels describe \ + my-restore-channel --project=my-project --location=us-central1 + +POSITIONAL ARGUMENTS + Restore channel resource - Name of the restore channel to describe. The + name may be provided either as a relative name, e.g. + projects//locations//restoreChannels/ + or as a single ID name (with the parent resources provided via options or + through properties), e.g. RESTORE_CHANNEL --project= + --location= 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 restore_channel 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. + + RESTORE_CHANNEL + ID of the restore channel or fully qualified identifier for the + restore channel. + + To set the restore_channel attribute: + ▸ provide the argument restore_channel on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + Google Cloud location. + + To set the location attribute: + ▸ provide the argument restore_channel on the command line with a + fully specified name; + ▸ provide the argument --location on the command line; + ▸ set the property gkebackup/location. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the gkebackup/v1 API. The full documentation for this API + can be found at: + https://cloud.google.com/kubernetes-engine/docs/add-on/backup-for-gke + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha container backup-restore restore-channels describe + diff --git a/gcloud/beta/container/backup-restore/restore-channels/help b/gcloud/beta/container/backup-restore/restore-channels/help new file mode 100644 index 000000000..e862bcccb --- /dev/null +++ b/gcloud/beta/container/backup-restore/restore-channels/help @@ -0,0 +1,40 @@ +NAME + gcloud beta container backup-restore restore-channels - backup for GKE + Restore Channels + +SYNOPSIS + gcloud beta container backup-restore restore-channels COMMAND + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Backup for GKE Restore Channels. + +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 restore channel. + + delete + (BETA) Delete a restore channel. + + describe + (BETA) Describe a restore channel. + + list + (BETA) List restore channels. + + update + (BETA) Update a restore channel. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha container backup-restore restore-channels + diff --git a/gcloud/beta/container/backup-restore/restore-channels/list b/gcloud/beta/container/backup-restore/restore-channels/list new file mode 100644 index 000000000..56b5cfc5a --- /dev/null +++ b/gcloud/beta/container/backup-restore/restore-channels/list @@ -0,0 +1,98 @@ +NAME + gcloud beta container backup-restore restore-channels list - list restore + channels + +SYNOPSIS + gcloud beta container backup-restore restore-channels list + [--location=LOCATION] [--filter=EXPRESSION] [--limit=LIMIT] + [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) List Backup for GKE restore channels. + +EXAMPLES + To list all restore channels in project my-project in location us-central1, + run: + + $ gcloud beta container backup-restore restore-channels list \ + --project=my-project --location=us-central1 + + To list all restore channels in project my-project across all locations, + run: + + $ gcloud beta container backup-restore restore-channels list \ + --project=my-project + +FLAGS + Location resource - Name of the location from which to list restore + channels (provided via options or through properties): --project= + --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 gkebackup/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; + ▸ set the property gkebackup/location. + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + + --uri + Print a list of resource URIs instead of the default output, and change + the command output to a list of URIs. If this flag is used with + --format, the formatting is applied on this URI list. To display URIs + alongside other keys instead, use the uri() transform. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the gkebackup/v1 API. The full documentation for this API + can be found at: + https://cloud.google.com/kubernetes-engine/docs/add-on/backup-for-gke + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha container backup-restore restore-channels list + diff --git a/gcloud/beta/container/backup-restore/restore-channels/update b/gcloud/beta/container/backup-restore/restore-channels/update new file mode 100644 index 000000000..df8e1a0b9 --- /dev/null +++ b/gcloud/beta/container/backup-restore/restore-channels/update @@ -0,0 +1,121 @@ +NAME + gcloud beta container backup-restore restore-channels update - update a + restore channel + +SYNOPSIS + gcloud beta container backup-restore restore-channels update + (RESTORE_CHANNEL : --location=LOCATION) [--async] + [--description=DESCRIPTION] [--etag=ETAG] + [--update-labels=[KEY=VALUE,...]] + [--clear-labels | --remove-labels=[KEY,...]] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Update a Backup for GKE restore channel. + +EXAMPLES + To update a restore channel my-restore-channel in project my-project in + location us-central1 to add new description, run: + + $ gcloud beta container backup-restore restore-channels update \ + my-restore-channel --project=my-project --location=us-central1 \ + --description="New description" + +POSITIONAL ARGUMENTS + Restore channel resource - Name of the restore channel to update. The name + may be provided either as a relative name, e.g. + projects//locations//restoreChannels/ + or as a single ID name (with the parent resources provided via options or + through properties), e.g. RESTORE_CHANNEL --project= + --location=. 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 restore_channel 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. + + RESTORE_CHANNEL + ID of the restore channel or fully qualified identifier for the + restore channel. + + To set the restore_channel attribute: + ▸ provide the argument restore_channel on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + Google Cloud location. + + To set the location attribute: + ▸ provide the argument restore_channel on the command line with a + fully specified name; + ▸ provide the argument --location on the command line; + ▸ set the property gkebackup/location. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --description=DESCRIPTION + The description of the restore channel. + + --etag=ETAG + The etag is used for optimistic concurrency control as a way to help + prevent simultaneous updates or deletes of a resource from overwriting + each other. + + --update-labels=[KEY=VALUE,...] + List of label KEY=VALUE pairs to update. If a label exists, its value + is modified. Otherwise, a new label is created. + + Keys must start with a lowercase character and contain only hyphens + (-), underscores (_), lowercase characters, and numbers. Values must + contain only hyphens (-), underscores (_), lowercase characters, and + numbers. + + At most one of these can be specified: + + --clear-labels + Remove all labels. If --update-labels is also specified then + --clear-labels is applied first. + + For example, to remove all labels: + + $ gcloud beta container backup-restore restore-channels update \ + --clear-labels + + To remove all existing labels and create two new labels, foo and baz: + + $ gcloud beta container backup-restore restore-channels 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 gkebackup/v1 API. The full documentation for this API + can be found at: + https://cloud.google.com/kubernetes-engine/docs/add-on/backup-for-gke + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha container backup-restore restore-channels update + diff --git a/gcloud/beta/container/backup-restore/restore-plan-bindings/describe b/gcloud/beta/container/backup-restore/restore-plan-bindings/describe new file mode 100644 index 000000000..099c6ed49 --- /dev/null +++ b/gcloud/beta/container/backup-restore/restore-plan-bindings/describe @@ -0,0 +1,89 @@ +NAME + gcloud beta container backup-restore restore-plan-bindings describe - + describe a restore plan binding + +SYNOPSIS + gcloud beta container backup-restore restore-plan-bindings describe + (RESTORE_PLAN_BINDING + : --location=LOCATION --restore-channel=RESTORE_CHANNEL) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Describe a Backup for GKE restore plan binding. + +EXAMPLES + To describe a restore plan binding my-restore-plan-binding in project + my-project in location us-central1 under restore channel + my-restore-channel, run: + + $ gcloud beta container backup-restore restore-plan-bindings \ + describe my-restore-plan-binding \ + --restore-channel=my-restore-channel --project=my-project \ + --location=us-central1 + +POSITIONAL ARGUMENTS + Restore plan binding resource - Name of the restore plan binding to + describe. The name may be provided either as a relative name, e.g. + projects//locations//restoreChannels//restorePlanBindings/ + or as a single ID name (with the parent resources provided via options or + through properties), e.g. RESTORE_PLAN_BINDING --project= + --location= --restore-channel=. 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 restore_plan_binding 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. + + RESTORE_PLAN_BINDING + ID of the restore plan binding or fully qualified identifier for the + restore plan binding. + + To set the restore_plan_binding attribute: + ▸ provide the argument restore_plan_binding on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + Google Cloud location. + + To set the location attribute: + ▸ provide the argument restore_plan_binding on the command line + with a fully specified name; + ▸ provide the argument --location on the command line; + ▸ set the property gkebackup/location. + + --restore-channel=RESTORE_CHANNEL + Restore Channel name. + + To set the restore-channel attribute: + ▸ provide the argument restore_plan_binding on the command line + with a fully specified name; + ▸ provide the argument --restore-channel 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 gkebackup/v1 API. The full documentation for this API + can be found at: + https://cloud.google.com/kubernetes-engine/docs/add-on/backup-for-gke + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha container backup-restore restore-plan-bindings \ + describe + diff --git a/gcloud/beta/container/backup-restore/restore-plan-bindings/help b/gcloud/beta/container/backup-restore/restore-plan-bindings/help new file mode 100644 index 000000000..4e83a5d47 --- /dev/null +++ b/gcloud/beta/container/backup-restore/restore-plan-bindings/help @@ -0,0 +1,31 @@ +NAME + gcloud beta container backup-restore restore-plan-bindings - backup for GKE + Restore Plan Bindings + +SYNOPSIS + gcloud beta container backup-restore restore-plan-bindings COMMAND + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Backup for GKE Restore Plan Bindings. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + describe + (BETA) Describe a restore plan binding. + + list + (BETA) List restore plan bindings. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha container backup-restore restore-plan-bindings + diff --git a/gcloud/beta/container/backup-restore/restore-plan-bindings/list b/gcloud/beta/container/backup-restore/restore-plan-bindings/list new file mode 100644 index 000000000..54e0ccfc5 --- /dev/null +++ b/gcloud/beta/container/backup-restore/restore-plan-bindings/list @@ -0,0 +1,113 @@ +NAME + gcloud beta container backup-restore restore-plan-bindings list - list + restore plan bindings + +SYNOPSIS + gcloud beta container backup-restore restore-plan-bindings list + (--restore-channel=RESTORE_CHANNEL : --location=LOCATION) + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) List Restore Plan Bindings for GKE restore plan bindings. + +EXAMPLES + To list all restore plan bindings in project my-project in location + us-central1 under restore channel my-restore-channel, run: + + $ gcloud beta container backup-restore restore-plan-bindings list \ + --restore-channel=my-restore-channel --project=my-project \ + --location=us-central1 + + To list all restore plan bindings in project my-project across all + locations under all restore channels, run: + + $ gcloud beta container backup-restore restore-plan-bindings list \ + --project=my-project + +REQUIRED FLAGS + Restore channel resource - Name of the restore channel from which to list + restore plan bindings (provided via options or through properties), e.g. + --project= --location= + --restore-channel=. 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 --restore-channel 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. + + --restore-channel=RESTORE_CHANNEL + ID of the restore channel or fully qualified identifier for the + restore channel. + + To set the restore-channel attribute: + ▸ provide the argument --restore-channel on the command line. + + This flag argument must be specified if any of the other arguments in + this group are specified. + + --location=LOCATION + Google Cloud location. + + To set the location attribute: + ▸ provide the argument --restore-channel on the command line with a + fully specified name; + ▸ provide the argument --location on the command line; + ▸ set the property gkebackup/location. + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + + --uri + Print a list of resource URIs instead of the default output, and change + the command output to a list of URIs. If this flag is used with + --format, the formatting is applied on this URI list. To display URIs + alongside other keys instead, use the uri() transform. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the gkebackup/v1 API. The full documentation for this API + can be found at: + https://cloud.google.com/kubernetes-engine/docs/add-on/backup-for-gke + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha container backup-restore restore-plan-bindings list + diff --git a/gcloud/beta/container/clusters/create b/gcloud/beta/container/clusters/create index aa3149715..855f115e9 100644 --- a/gcloud/beta/container/clusters/create +++ b/gcloud/beta/container/clusters/create @@ -46,9 +46,9 @@ SYNOPSIS [--enable-master-global-access] [--enable-multi-networking] [--enable-nested-virtualization] [--enable-network-policy] [--enable-pod-security-policy] [--enable-ray-cluster-logging] - [--enable-ray-cluster-monitoring] [--enable-secret-manager] - [--enable-service-externalips] [--enable-shielded-nodes] - [--enable-stackdriver-kubernetes] [--enable-vertical-pod-autoscaling] + [--enable-ray-cluster-monitoring] [--enable-service-externalips] + [--enable-shielded-nodes] [--enable-stackdriver-kubernetes] + [--enable-vertical-pod-autoscaling] [--fleet-project=PROJECT_ID_OR_NUMBER] [--gateway-api=GATEWAY_API] [--hpa-profile=HPA_PROFILE] [--identity-provider=IDENTITY_PROVIDER] [--image-type=IMAGE_TYPE] @@ -131,6 +131,8 @@ SYNOPSIS --resource-usage-bigquery-dataset=RESOURCE_USAGE_BIGQUERY_DATASET] [--enable-private-endpoint --enable-private-nodes --master-ipv4-cidr=MASTER_IPV4_CIDR --private-cluster] + [--enable-secret-manager --enable-secret-manager-rotation + --secret-manager-rotation-interval=SECRET_MANAGER_ROTATION_INTERVAL] [--enable-tpu --enable-tpu-service-networking | --tpu-ipv4-cidr=CIDR] [--ephemeral-storage[=[local-ssd-count=LOCAL-SSD-COUNT]] | --ephemeral-storage-local-ssd[=[count=COUNT]] @@ -713,16 +715,6 @@ FLAGS --enable-ray-cluster-monitoring Enable automatic metrics collection for Ray clusters. - Flags for Secret Manager configuration: - - --enable-secret-manager - Enables the Secret Manager CSI driver provider component. See - https://secrets-store-csi-driver.sigs.k8s.io/introduction - https://github.com/GoogleCloudPlatform/secrets-store-csi-driver-provider-gcp - - To disable in an existing cluster, explicitly set flag to - --no-enable-secret-manager - --enable-service-externalips Enables use of services with externalIPs field. @@ -2100,6 +2092,27 @@ FLAGS The --private-cluster flag is deprecated and will be removed in a future release. Use --enable-private-nodes instead. + Flags for Secret Manager configuration: + + --enable-secret-manager + Enables the Secret Manager CSI driver provider component. See + https://secrets-store-csi-driver.sigs.k8s.io/introduction + https://github.com/GoogleCloudPlatform/secrets-store-csi-driver-provider-gcp + + To disable in an existing cluster, explicitly set flag to + --no-enable-secret-manager + + --enable-secret-manager-rotation + Enables the rotation of secrets in the Secret Manager CSI driver + provider component. + + To disable in an existing cluster, explicitly set flag to + --no-enable-secret-manager-rotation + + --secret-manager-rotation-interval=SECRET_MANAGER_ROTATION_INTERVAL + Set the rotation period for secrets in the Secret Manager CSI driver + provider component. + Flags relating to Cloud TPUs: --enable-tpu diff --git a/gcloud/beta/container/clusters/create-auto b/gcloud/beta/container/clusters/create-auto index 731077de9..1a3c50663 100644 --- a/gcloud/beta/container/clusters/create-auto +++ b/gcloud/beta/container/clusters/create-auto @@ -22,15 +22,14 @@ SYNOPSIS [--enable-ip-access] [--enable-kubernetes-unstable-apis=API,[API,...]] [--enable-master-global-access] [--enable-multi-networking] [--enable-ray-cluster-logging] [--enable-ray-cluster-monitoring] - [--enable-ray-operator] [--enable-secret-manager] - [--fleet-project=PROJECT_ID_OR_NUMBER] [--hpa-profile=HPA_PROFILE] - [--labels=[KEY=VALUE,...]] [--logging=[COMPONENT,...]] - [--monitoring=[COMPONENT,...]] [--network=NETWORK] - [--private-endpoint-subnetwork=NAME] [--release-channel=[CHANNEL]] - [--security-group=SECURITY_GROUP] [--security-posture=SECURITY_POSTURE] - [--services-ipv4-cidr=CIDR] [--services-secondary-range-name=NAME] - [--subnetwork=SUBNETWORK] [--tier=TIER] - [--workload-policies=WORKLOAD_POLICIES] + [--enable-ray-operator] [--fleet-project=PROJECT_ID_OR_NUMBER] + [--hpa-profile=HPA_PROFILE] [--labels=[KEY=VALUE,...]] + [--logging=[COMPONENT,...]] [--monitoring=[COMPONENT,...]] + [--network=NETWORK] [--private-endpoint-subnetwork=NAME] + [--release-channel=[CHANNEL]] [--security-group=SECURITY_GROUP] + [--security-posture=SECURITY_POSTURE] [--services-ipv4-cidr=CIDR] + [--services-secondary-range-name=NAME] [--subnetwork=SUBNETWORK] + [--tier=TIER] [--workload-policies=WORKLOAD_POLICIES] [--workload-vulnerability-scanning=WORKLOAD_VULNERABILITY_SCANNING] [--additive-vpc-scope-dns-domain=ADDITIVE_VPC_SCOPE_DNS_DOMAIN | --disable-additive-vpc-scope] @@ -50,6 +49,8 @@ SYNOPSIS --master-authorized-networks=NETWORK,[NETWORK,...]] [--enable-private-endpoint --enable-private-nodes --master-ipv4-cidr=MASTER_IPV4_CIDR] + [--enable-secret-manager --enable-secret-manager-rotation + --secret-manager-rotation-interval=SECRET_MANAGER_ROTATION_INTERVAL] [--location=LOCATION | --region=REGION | --zone=ZONE, -z ZONE] [--scopes=[SCOPE,...]; default="gke-default" --service-account=SERVICE_ACCOUNT] @@ -295,16 +296,6 @@ FLAGS --enable-ray-operator Enable the Ray Operator GKE add-on. This add-on is disabled by default. - Flags for Secret Manager configuration: - - --enable-secret-manager - Enables the Secret Manager CSI driver provider component. See - https://secrets-store-csi-driver.sigs.k8s.io/introduction - https://github.com/GoogleCloudPlatform/secrets-store-csi-driver-provider-gcp - - To disable in an existing cluster, explicitly set flag to - --no-enable-secret-manager - --fleet-project=PROJECT_ID_OR_NUMBER Sets fleet host project for the cluster. If specified, the current cluster will be registered as a fleet membership under the fleet host @@ -650,6 +641,27 @@ FLAGS netmask of size /28 and should be used in conjunction with the --enable-private-nodes flag. + Flags for Secret Manager configuration: + + --enable-secret-manager + Enables the Secret Manager CSI driver provider component. See + https://secrets-store-csi-driver.sigs.k8s.io/introduction + https://github.com/GoogleCloudPlatform/secrets-store-csi-driver-provider-gcp + + To disable in an existing cluster, explicitly set flag to + --no-enable-secret-manager + + --enable-secret-manager-rotation + Enables the rotation of secrets in the Secret Manager CSI driver + provider component. + + To disable in an existing cluster, explicitly set flag to + --no-enable-secret-manager-rotation + + --secret-manager-rotation-interval=SECRET_MANAGER_ROTATION_INTERVAL + Set the rotation period for secrets in the Secret Manager CSI driver + provider component. + At most one of these can be specified: --location=LOCATION diff --git a/gcloud/beta/container/clusters/get-upgrade-info b/gcloud/beta/container/clusters/get-upgrade-info index 0a9ce3c1a..40eea7024 100644 --- a/gcloud/beta/container/clusters/get-upgrade-info +++ b/gcloud/beta/container/clusters/get-upgrade-info @@ -49,8 +49,10 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud container clusters get-upgrade-info $ gcloud alpha container clusters get-upgrade-info diff --git a/gcloud/beta/container/clusters/update b/gcloud/beta/container/clusters/update index ed6d75b92..1361e5fe0 100644 --- a/gcloud/beta/container/clusters/update +++ b/gcloud/beta/container/clusters/update @@ -27,9 +27,9 @@ SYNOPSIS | --enable-logging-monitoring-system-only | --enable-multi-networking | --enable-network-policy | --enable-pod-security-policy | --enable-private-nodes | --[no-]enable-ray-cluster-logging - | --[no-]enable-ray-cluster-monitoring | --enable-secret-manager - | --enable-service-externalips | --enable-shielded-nodes - | --enable-stackdriver-kubernetes | --enable-vertical-pod-autoscaling + | --[no-]enable-ray-cluster-monitoring | --enable-service-externalips + | --enable-shielded-nodes | --enable-stackdriver-kubernetes + | --enable-vertical-pod-autoscaling | --fleet-project=PROJECT_ID_OR_NUMBER | --gateway-api=GATEWAY_API | --generate-password | --hpa-profile=HPA_PROFILE | --identity-provider=IDENTITY_PROVIDER @@ -106,6 +106,8 @@ SYNOPSIS : --min-accelerator=[type=TYPE,count=COUNT,...]]] | --enable-insecure-binding-system-authenticated --enable-insecure-binding-system-unauthenticated + | --enable-secret-manager --enable-secret-manager-rotation + --secret-manager-rotation-interval=SECRET_MANAGER_ROTATION_INTERVAL | --enable-tpu --enable-tpu-service-networking | --tpu-ipv4-cidr=CIDR | --logging-service=LOGGING_SERVICE --monitoring-service=MONITORING_SERVICE @@ -459,16 +461,6 @@ REQUIRED FLAGS --enable-ray-cluster-monitoring to enable and --no-enable-ray-cluster-monitoring to disable. - Flags for Secret Manager configuration: - - --enable-secret-manager - Enables the Secret Manager CSI driver provider component. See - https://secrets-store-csi-driver.sigs.k8s.io/introduction - https://github.com/GoogleCloudPlatform/secrets-store-csi-driver-provider-gcp - - To disable in an existing cluster, explicitly set flag to - --no-enable-secret-manager - --enable-service-externalips Enables use of services with externalIPs field. @@ -1500,6 +1492,27 @@ REQUIRED FLAGS To disallow binding system:authenticated in a cluster, explicitly set the --no-enable-insecure-binding-system-unauthenticated flag instead. + Flags for Secret Manager configuration: + + --enable-secret-manager + Enables the Secret Manager CSI driver provider component. See + https://secrets-store-csi-driver.sigs.k8s.io/introduction + https://github.com/GoogleCloudPlatform/secrets-store-csi-driver-provider-gcp + + To disable in an existing cluster, explicitly set flag to + --no-enable-secret-manager + + --enable-secret-manager-rotation + Enables the rotation of secrets in the Secret Manager CSI driver + provider component. + + To disable in an existing cluster, explicitly set flag to + --no-enable-secret-manager-rotation + + --secret-manager-rotation-interval=SECRET_MANAGER_ROTATION_INTERVAL + Set the rotation period for secrets in the Secret Manager CSI + driver provider component. + Flags relating to Cloud TPUs: --enable-tpu diff --git a/gcloud/beta/container/node-pools/create b/gcloud/beta/container/node-pools/create index 3c1e09f81..40f24d54e 100644 --- a/gcloud/beta/container/node-pools/create +++ b/gcloud/beta/container/node-pools/create @@ -41,9 +41,12 @@ SYNOPSIS [--node-locations=ZONE,[ZONE,...]] [--node-pool-soak-duration=NODE_POOL_SOAK_DURATION] [--node-taints=[NODE_TAINT,...]] [--node-version=NODE_VERSION] - [--num-nodes=NUM_NODES] [--placement-policy=PLACEMENT_POLICY] - [--placement-type=PLACEMENT_TYPE] [--preemptible] - [--resource-manager-tags=[KEY=VALUE,...]] [--sandbox=[type=TYPE]] + [--num-nodes=NUM_NODES] + [--opportunistic-maintenance=[node-idle-time=NODE_IDLE_TIME, + window=WINDOW,min-nodes=MIN_NODES,...]] + [--placement-policy=PLACEMENT_POLICY] [--placement-type=PLACEMENT_TYPE] + [--preemptible] [--resource-manager-tags=[KEY=VALUE,...]] + [--sandbox=[type=TYPE]] [--secondary-boot-disk=[disk-image=DISK_IMAGE,[mode=MODE],...]] [--shielded-integrity-monitoring] [--shielded-secure-boot] [--sole-tenant-node-affinity-file=SOLE_TENANT_NODE_AFFINITY_FILE] @@ -560,6 +563,26 @@ FLAGS types the number of nodes will be defaulted to (product of topology)/(# of chips per VM). + --opportunistic-maintenance=[node-idle-time=NODE_IDLE_TIME,window=WINDOW,min-nodes=MIN_NODES,...] + Opportunistic maintenance options. + + node-idle-time: Time to be spent waiting for node to be idle before + starting maintenance, ending with 's'. Example: "3.5s" + + window: The window of time that opportunistic maintenance can run, + ending with 's'. Example: A setting of 14 days (1209600s) implies that + opportunistic maintenance can only be ran in the 2 weeks leading up to + the scheduled maintenance date. Setting 28 days(2419200s) allows + opportunistic maintenance to run at any time in the scheduled + maintenance window. + + min-nodes: Minimum number of nodes in the node pool to be available + during the opportunistic triggered maintenance. + + $ gcloud beta container node-pools create example-cluster \ + --opportunistic-maintenance=node-idle-time=600s,window=600s,\ + min-nodes=2 + --placement-policy=PLACEMENT_POLICY Indicates the desired resource policy to use. diff --git a/gcloud/beta/container/node-pools/get-upgrade-info b/gcloud/beta/container/node-pools/get-upgrade-info index a740a7b64..840f27d5a 100644 --- a/gcloud/beta/container/node-pools/get-upgrade-info +++ b/gcloud/beta/container/node-pools/get-upgrade-info @@ -1,7 +1,6 @@ NAME - gcloud beta container node-pools get-upgrade-info - get information about - upgrades for existing clusters including auto upgrade status, upgrade - history, upgrade targets, and end of support timelines + gcloud beta container node-pools get-upgrade-info - get upgrade information + for an existing node pool for a cluster SYNOPSIS gcloud beta container node-pools get-upgrade-info NAME [--cluster=CLUSTER] @@ -9,9 +8,9 @@ SYNOPSIS [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) Get information about upgrades for existing clusters including auto - upgrade status, upgrade history, upgrade targets, and end of support - timelines. + (BETA) gcloud beta container node-pools get-upgrade-info displays all + upgrade information associated with the node pool in the Google Kubernetes + Engine cluster. EXAMPLES To get upgrade information for a node pool of an existing cluster, run: @@ -54,8 +53,10 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud container node-pools get-upgrade-info $ gcloud alpha container node-pools get-upgrade-info diff --git a/gcloud/beta/container/node-pools/help b/gcloud/beta/container/node-pools/help index 66530b9f0..6ca7b0f24 100644 --- a/gcloud/beta/container/node-pools/help +++ b/gcloud/beta/container/node-pools/help @@ -50,9 +50,7 @@ COMMANDS (BETA) Describe an existing node pool for a cluster. get-upgrade-info - (BETA) Get information about upgrades for existing clusters including - auto upgrade status, upgrade history, upgrade targets, and end of - support timelines. + (BETA) Get upgrade information for an existing node pool for a cluster. list (BETA) List existing node pools for a cluster. diff --git a/gcloud/beta/dataflow/flex-template/run b/gcloud/beta/dataflow/flex-template/run index 68704943a..d417ed6ed 100644 --- a/gcloud/beta/dataflow/flex-template/run +++ b/gcloud/beta/dataflow/flex-template/run @@ -53,7 +53,7 @@ OPTIONAL FLAGS --additional-user-labels=[ADDITIONAL_USER_LABELS,...] Additional user labels to pass to the job. Example: - --additional-user-labels='{"key1":"value1"}' + --additional-user-labels='key1=value1,key2=value2' --dataflow-kms-key=DATAFLOW_KMS_KEY Cloud KMS key to protect the job resources. diff --git a/gcloud/beta/dataflow/jobs/run b/gcloud/beta/dataflow/jobs/run index 8a20bad21..69d24b80b 100644 --- a/gcloud/beta/dataflow/jobs/run +++ b/gcloud/beta/dataflow/jobs/run @@ -4,6 +4,7 @@ NAME SYNOPSIS gcloud beta dataflow jobs run JOB_NAME --gcs-location=GCS_LOCATION [--additional-experiments=[ADDITIONAL_EXPERIMENTS,...]] + [--additional-user-labels=[ADDITIONAL_USER_LABELS,...]] [--dataflow-kms-key=DATAFLOW_KMS_KEY] [--disable-public-ips] [--enable-streaming-engine] [--max-workers=MAX_WORKERS] [--network=NETWORK] [--num-workers=NUM_WORKERS] @@ -33,6 +34,10 @@ OPTIONAL FLAGS Additional experiments to pass to the job. These experiments are appended to any experiments already set by the template. + --additional-user-labels=[ADDITIONAL_USER_LABELS,...] + Additional user labels to pass to the job. Example: + --additional-user-labels='key1=value1,key2=value2' + --dataflow-kms-key=DATAFLOW_KMS_KEY The Cloud KMS key to protect the job resources. diff --git a/gcloud/beta/dataproc/clusters/create b/gcloud/beta/dataproc/clusters/create index b161ecaad..db8423087 100644 --- a/gcloud/beta/dataproc/clusters/create +++ b/gcloud/beta/dataproc/clusters/create @@ -43,8 +43,7 @@ SYNOPSIS [--secondary-worker-standard-capacity-base=SECONDARY_WORKER_STANDARD_CAPACITY_BASE] [--secondary-worker-standard-capacity-percent-above-base=SECONDARY_WORKER_STANDARD_CAPACITY_PERCENT_ABOVE_BASE] [--shielded-integrity-monitoring] [--shielded-secure-boot] - [--shielded-vtpm] [--stop-max-idle=STOP_MAX_IDLE] - [--temp-bucket=TEMP_BUCKET] + [--shielded-vtpm] [--temp-bucket=TEMP_BUCKET] [--worker-accelerator=[type=TYPE,[count=COUNT],...]] [--worker-boot-disk-provisioned-iops=WORKER_BOOT_DISK_PROVISIONED_IOPS] [--worker-boot-disk-provisioned-throughput=WORKER_BOOT_DISK_PROVISIONED_THROUGHPUT] @@ -78,8 +77,6 @@ SYNOPSIS --num-secondary-workers=NUM_SECONDARY_WORKERS --num-workers=NUM_WORKERS --secondary-worker-type=TYPE; default="preemptible"] - [--stop-expiration-time=STOP_EXPIRATION_TIME - | --stop-max-age=STOP_MAX_AGE] [--worker-machine-type=WORKER_MACHINE_TYPE | --worker-machine-types=type=MACHINE_TYPE[, type=MACHINE_TYPE...][,rank=RANK]] [GCLOUD_WIDE_FLAG ...] @@ -421,11 +418,6 @@ FLAGS security operations, such as remote attestation, encryption, and sealing of keys. - --stop-max-idle=STOP_MAX_IDLE - The duration after the last job completes to auto-stop the cluster, - such as "2h" or "1d". See $ gcloud topic datetimes for information on - duration formats. - --temp-bucket=TEMP_BUCKET The Google Cloud Storage bucket to use by default to store ephemeral cluster and jobs data, such as Spark and MapReduce history files. @@ -950,18 +942,6 @@ FLAGS The type of the secondary worker group. TYPE must be one of: preemptible, non-preemptible, spot. - At most one of these can be specified: - - --stop-expiration-time=STOP_EXPIRATION_TIME - The time when the cluster will be auto-stopped, such as - "2017-08-29T18:52:51.142Z." See $ gcloud topic datetimes for - information on time formats. - - --stop-max-age=STOP_MAX_AGE - The lifespan of the cluster, with auto-stop upon completion, such as - "2h" or "1d". See $ gcloud topic datetimes for information on - duration formats. - At most one of these can be specified: --worker-machine-type=WORKER_MACHINE_TYPE diff --git a/gcloud/beta/dataproc/clusters/update b/gcloud/beta/dataproc/clusters/update index e7d4b5048..5e032cc9e 100644 --- a/gcloud/beta/dataproc/clusters/update +++ b/gcloud/beta/dataproc/clusters/update @@ -15,11 +15,7 @@ SYNOPSIS | --expiration-time=EXPIRATION_TIME | --max-age=MAX_AGE | --no-max-age] [--delete-max-idle=DELETE_MAX_IDLE | --no-delete-max-idle - | --max-idle=MAX_IDLE | --no-max-idle] - [--stop-expiration-time=STOP_EXPIRATION_TIME - | --stop-max-age=STOP_MAX_AGE | --no-stop-max-age] - [--stop-max-idle=STOP_MAX_IDLE | --no-stop-max-idle] - [GCLOUD_WIDE_FLAG ...] + | --max-idle=MAX_IDLE | --no-max-idle] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) Update the number of worker nodes and/or the labels in a cluster. @@ -220,33 +216,6 @@ FLAGS Cancels the cluster auto-deletion by cluster idle duration (configured by --max-idle flag) - At most one of these can be specified: - - --stop-expiration-time=STOP_EXPIRATION_TIME - The time when the cluster will be auto-stopped, such as - "2017-08-29T18:52:51.142Z". See $ gcloud topic datetimes for - information on time formats. - - --stop-max-age=STOP_MAX_AGE - The lifespan of the cluster, with auto-stop upon completion, such as - "2h" or "1d". See $ gcloud topic datetimes for information on - duration formats. - - --no-stop-max-age - Cancels the cluster auto-stop by maximum cluster age (configured by - --stop-max-age or --stop-expiration-time flags) - - At most one of these can be specified: - - --stop-max-idle=STOP_MAX_IDLE - The duration after the last job completes to auto-stop the cluster, - such as "2h" or "1d". See $ gcloud topic datetimes for information on - duration formats. - - --no-stop-max-idle - Cancels the cluster auto-stop by cluster idle duration (configured by - --stop-max-idle flag) - GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, diff --git a/gcloud/beta/filestore/instances/create b/gcloud/beta/filestore/instances/create index d8358dc5e..6e7de85c7 100644 --- a/gcloud/beta/filestore/instances/create +++ b/gcloud/beta/filestore/instances/create @@ -11,7 +11,6 @@ SYNOPSIS [reserved-ip-range=RESERVED-IP-RANGE] [--async] [--description=DESCRIPTION] [--labels=[KEY=VALUE,...]] [--location=LOCATION] - [--managed-ad=[computer=COMPUTER],[domain=DOMAIN]] [--performance=[max-iops=MAX-IOPS],[max-iops-per-tb=MAX-IOPS-PER-TB]] [--protocol=PROTOCOL; default="NFS_V3"] [--region=REGION] [--source-instance=SOURCE_INSTANCE] [--tags=[KEY=VALUE,...]] @@ -20,6 +19,9 @@ SYNOPSIS : --deletion-protection-reason=DELETION_PROTECTION_REASON] [--kms-key=KMS_KEY : --kms-keyring=KMS_KEYRING --kms-location=KMS_LOCATION --kms-project=KMS_PROJECT] + [--ldap=[^:^domain=DOMAIN:servers=SERVER1, + SERVER2:users_ou=USERSOU:groups_ou=GROUPSOU,...] + | --managed-ad=[computer=COMPUTER],[domain=DOMAIN]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -39,6 +41,8 @@ EXAMPLES --kms-key=KMS-KEY --kms-keyring=KMS_KEYRING \ --kms-location=KMS_LOCATION --kms-project=KMS_PROJECT \ --managed-ad=domain=DOMAIN,computer=COMPUTER \ + --ldap=^:^domain=DOMAIN:servers=SERVER1,\ + SERVER2:users_ou=USERSOU:groups_ou=GROUPSOU \ --flags-file=FLAGS_FILE --source-instance=SOURCE_INSTANCE Example json configuration file: @@ -241,19 +245,6 @@ OPTIONAL FLAGS --location=LOCATION Location of the Cloud Filestore instance/operation. - --managed-ad=[computer=COMPUTER],[domain=DOMAIN] - Managed Active Directory configuration for an instance. Specifies both - the domain name and a computer name (unique to the domain) to be - created by the filestore instance. - - domain - The desired domain full uri. i.e: - projects/PROJECT/locations/global/domains/DOMAIN - - computer - The desired active directory computer name to be created by - the filestore instance when connecting to the domain. - --performance=[max-iops=MAX-IOPS],[max-iops-per-tb=MAX-IOPS-PER-TB] Performance configuration for the instance. This flag is used to configure the read IOPS provisioned for the instance. The instance's @@ -394,6 +385,45 @@ OPTIONAL FLAGS ▸ provide the argument --kms-project on the command line; ▸ set the property core/project. + Directory services configuration for an instance. + + At most one of these can be specified: + + --ldap=[^:^domain=DOMAIN:servers=SERVER1,SERVER2:users_ou=USERSOU:groups_ou=GROUPSOU,...] + LDAP configuration for an instance. Specifies the domain name, + servers, users_ou, and groups_ou to be created by the filestore + instance. users_ou and groups_ou are optional. + + domain + The desired domain name. i.e.: + 'my-domain.com' + + Servers + The desired LDAP servers. i.e.: + 'ldap.example.com', 'ldap2.example.com' + + Usersou + The desired usersou. + + Groups_ou + The desired groups_ou. + + Use the following format to specify the LDAP configuration: + --ldap=^:^domain=my-domain.com:servers=ldap.example.com,ldap2.example.com:users_ou=users:groups_ou=groups + + --managed-ad=[computer=COMPUTER],[domain=DOMAIN] + Managed Active Directory configuration for an instance. Specifies + both the domain name and a computer name (unique to the domain) to be + created by the filestore instance. + + domain + The desired domain full uri. i.e.: + projects/PROJECT/locations/global/domains/DOMAIN + + computer + The desired active directory computer name to be created by + the filestore instance when connecting to the domain. + 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/filestore/instances/update b/gcloud/beta/filestore/instances/update index d1d88b768..f9ae368b7 100644 --- a/gcloud/beta/filestore/instances/update +++ b/gcloud/beta/filestore/instances/update @@ -194,7 +194,7 @@ FLAGS created by the filestore instance. domain - The desired domain full uri. i.e: + The desired domain full uri. i.e.: projects/PROJECT/locations/global/domains/DOMAIN computer diff --git a/gcloud/beta/firestore/databases/connection-string b/gcloud/beta/firestore/databases/connection-string new file mode 100644 index 000000000..afd6a67c8 --- /dev/null +++ b/gcloud/beta/firestore/databases/connection-string @@ -0,0 +1,54 @@ +NAME + gcloud beta firestore databases connection-string - prints the mongo + connection string for the given Firestore database + +SYNOPSIS + gcloud beta firestore databases connection-string --database=DATABASE + [--auth=AUTH; default="none"] [GCLOUD_WIDE_FLAG ...] + +EXAMPLES + To get the connection string for a Firestore database with a databaseId + testdb without auth configuration. + + $ gcloud beta firestore databases connection-string \ + --database=testdb --auth=none + + To get the connection string for a Firestore database with a databaseId + testdb with Google Compute Engine VM auth. + + $ gcloud beta firestore databases connection-string \ + --database=testdb --auth=gce-vm + +REQUIRED FLAGS + --database=DATABASE + The database to operate on. + + For example, to operate on database foo: + + $ gcloud beta firestore databases connection-string --database='foo' + +OPTIONAL FLAGS + --auth=AUTH; default="none" + The auth configuration for the connection string. + + If connecting from a Google Compute Engine VM, use gce-vm. For short + term access using the gcloud CLI's access token, use access-token. For + password auth use scram-sha-256. Otherwise, use none and configure auth + manually. + + AUTH must be one of: none, gce-vm, access-token, scram-sha-256. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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 firestore databases connection-string + diff --git a/gcloud/beta/firestore/databases/create b/gcloud/beta/firestore/databases/create index ac3b36982..5178de29e 100644 --- a/gcloud/beta/firestore/databases/create +++ b/gcloud/beta/firestore/databases/create @@ -5,10 +5,17 @@ NAME SYNOPSIS gcloud beta firestore databases create --location=LOCATION [--database=DATABASE; default="(default)"] [--delete-protection] - [--enable-pitr] [--kms-key-name=KMS_KEY_NAME] - [--type=TYPE; default="firestore-native"] [GCLOUD_WIDE_FLAG ...] + [--edition=EDITION; default="standard"] [--enable-pitr] + [--kms-key-name=KMS_KEY_NAME] [--type=TYPE; default="firestore-native"] + [GCLOUD_WIDE_FLAG ...] EXAMPLES + To create a Firestore Enterprise database named foo in nam5 for use with + Ignite APIs. + + $ gcloud beta firestore databases create --database=foo \ + --edition=enterprise --location=nam5 + To create a Firestore Native database in nam5. $ gcloud beta firestore databases create --location=nam5 @@ -72,6 +79,10 @@ OPTIONAL FLAGS Default to false. + --edition=EDITION; default="standard" + The edition of the database. EDITION must be one of: standard, + enterprise. + --enable-pitr Whether to enable Point In Time Recovery (PITR) on the created database. diff --git a/gcloud/beta/firestore/databases/help b/gcloud/beta/firestore/databases/help index 782002dd1..c15096c73 100644 --- a/gcloud/beta/firestore/databases/help +++ b/gcloud/beta/firestore/databases/help @@ -16,6 +16,10 @@ GCLOUD WIDE FLAGS COMMANDS COMMAND is one of the following: + connection-string + (BETA) Prints the mongo connection string for the given Firestore + database. + create (BETA) Create a Google Cloud Firestore database via Firestore API. diff --git a/gcloud/beta/firestore/help b/gcloud/beta/firestore/help index 350c9f3ef..44bd5aeca 100644 --- a/gcloud/beta/firestore/help +++ b/gcloud/beta/firestore/help @@ -41,6 +41,9 @@ GROUPS operations (BETA) Manage Long Running Operations for Cloud Firestore. + user-creds + (BETA) Manage the user creds for a Cloud Firestore Database. + COMMANDS COMMAND is one of the following: diff --git a/gcloud/beta/firestore/indexes/composite/create b/gcloud/beta/firestore/indexes/composite/create index 38e1018ff..c18421ad7 100644 --- a/gcloud/beta/firestore/indexes/composite/create +++ b/gcloud/beta/firestore/indexes/composite/create @@ -8,6 +8,7 @@ SYNOPSIS [field-path=FIELD-PATH],[order=ORDER],[vector-config=VECTOR-CONFIG] (--collection-group=COLLECTION_GROUP : --database=DATABASE) [--api-scope=API_SCOPE; default="any-api"] [--async] + [--density=DENSITY] [--multikey] [--query-scope=QUERY_SCOPE; default="collection"] [GCLOUD_WIDE_FLAG ...] @@ -103,12 +104,25 @@ REQUIRED FLAGS OPTIONAL FLAGS --api-scope=API_SCOPE; default="any-api" Api scope the index applies to. API_SCOPE must be one of: any-api, - datastore-mode-api. + datastore-mode-api, mongodb-compatible-api. --async Return immediately, without waiting for the operation in progress to complete. + --density=DENSITY + Density of the index. DENSITY must be one of: dense, + density-unspecified, sparse-all, sparse-any. + + --multikey + Optional. Whether the index is multikey. By default, the index is not + multikey. For non-multikey indexes, none of the paths in the index + definition reach or traverse an array, except via an explicit array + index. For multikey indexes, at most one of the paths in the index + definition reach or traverse an array, except via an explicit array + index. Violations will result in errors. Note this field only applies + to index with MONGODB_COMPATIBLE_API ApiScope. + --query-scope=QUERY_SCOPE; default="collection" Query scope the index applies to. QUERY_SCOPE must be one of: collection, collection-group, collection-recursive. diff --git a/gcloud/beta/firestore/user-creds/create b/gcloud/beta/firestore/user-creds/create new file mode 100644 index 000000000..329fbd211 --- /dev/null +++ b/gcloud/beta/firestore/user-creds/create @@ -0,0 +1,44 @@ +NAME + gcloud beta firestore user-creds create - creates a Cloud Firestore user + creds + +SYNOPSIS + gcloud beta firestore user-creds create USER_CREDS --database=DATABASE + [GCLOUD_WIDE_FLAG ...] + +EXAMPLES + To create a user creds called test-user-creds-id under database testdb. + + $ gcloud beta firestore user-creds create test-user-creds-id \ + --database=testdb + +POSITIONAL ARGUMENTS + USER_CREDS + The user creds to operate on. + + For example, to operate on user creds creds-name-1: + + $ gcloud beta firestore user-creds create creds-name-1 + +REQUIRED FLAGS + --database=DATABASE + The database to operate on. + + For example, to operate on database foo: + + $ gcloud beta firestore user-creds create --database='foo' + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha firestore user-creds create + diff --git a/gcloud/beta/firestore/user-creds/delete b/gcloud/beta/firestore/user-creds/delete new file mode 100644 index 000000000..5d9a1cf3a --- /dev/null +++ b/gcloud/beta/firestore/user-creds/delete @@ -0,0 +1,44 @@ +NAME + gcloud beta firestore user-creds delete - deletes a Cloud Firestore user + creds + +SYNOPSIS + gcloud beta firestore user-creds delete USER_CREDS --database=DATABASE + [GCLOUD_WIDE_FLAG ...] + +EXAMPLES + To delete user creds 'test-user-creds-id' under database testdb. + + $ gcloud beta firestore user-creds delete test-user-creds-id \ + --database='testdb' + +POSITIONAL ARGUMENTS + USER_CREDS + The user creds to operate on. + + For example, to operate on user creds creds-name-1: + + $ gcloud beta firestore user-creds delete creds-name-1 + +REQUIRED FLAGS + --database=DATABASE + The database to operate on. + + For example, to operate on database foo: + + $ gcloud beta firestore user-creds delete --database='foo' + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha firestore user-creds delete + diff --git a/gcloud/beta/firestore/user-creds/describe b/gcloud/beta/firestore/user-creds/describe new file mode 100644 index 000000000..59a093f15 --- /dev/null +++ b/gcloud/beta/firestore/user-creds/describe @@ -0,0 +1,44 @@ +NAME + gcloud beta firestore user-creds describe - describes a Cloud Firestore + user creds + +SYNOPSIS + gcloud beta firestore user-creds describe USER_CREDS --database=DATABASE + [GCLOUD_WIDE_FLAG ...] + +EXAMPLES + To describe user creds 'test-user-creds-id' under database testdb. + + $ gcloud beta firestore user-creds describe test-user-creds-id \ + --database='testdb' + +POSITIONAL ARGUMENTS + USER_CREDS + The user creds to operate on. + + For example, to operate on user creds creds-name-1: + + $ gcloud beta firestore user-creds describe creds-name-1 + +REQUIRED FLAGS + --database=DATABASE + The database to operate on. + + For example, to operate on database foo: + + $ gcloud beta firestore user-creds describe --database='foo' + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha firestore user-creds describe + diff --git a/gcloud/beta/firestore/user-creds/disable b/gcloud/beta/firestore/user-creds/disable new file mode 100644 index 000000000..d3b86122f --- /dev/null +++ b/gcloud/beta/firestore/user-creds/disable @@ -0,0 +1,44 @@ +NAME + gcloud beta firestore user-creds disable - disables a Cloud Firestore user + creds + +SYNOPSIS + gcloud beta firestore user-creds disable USER_CREDS --database=DATABASE + [GCLOUD_WIDE_FLAG ...] + +EXAMPLES + To disable user creds 'test-user-creds-id' under database testdb. + + $ gcloud beta firestore user-creds disable test-user-creds-id \ + --database='testdb' + +POSITIONAL ARGUMENTS + USER_CREDS + The user creds to operate on. + + For example, to operate on user creds creds-name-1: + + $ gcloud beta firestore user-creds disable creds-name-1 + +REQUIRED FLAGS + --database=DATABASE + The database to operate on. + + For example, to operate on database foo: + + $ gcloud beta firestore user-creds disable --database='foo' + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha firestore user-creds disable + diff --git a/gcloud/beta/firestore/user-creds/enable b/gcloud/beta/firestore/user-creds/enable new file mode 100644 index 000000000..6a5cdc416 --- /dev/null +++ b/gcloud/beta/firestore/user-creds/enable @@ -0,0 +1,44 @@ +NAME + gcloud beta firestore user-creds enable - enables a Cloud Firestore user + creds + +SYNOPSIS + gcloud beta firestore user-creds enable USER_CREDS --database=DATABASE + [GCLOUD_WIDE_FLAG ...] + +EXAMPLES + To enable user creds 'test-user-creds-id' under database testdb. + + $ gcloud beta firestore user-creds enable test-user-creds-id \ + --database='testdb' + +POSITIONAL ARGUMENTS + USER_CREDS + The user creds to operate on. + + For example, to operate on user creds creds-name-1: + + $ gcloud beta firestore user-creds enable creds-name-1 + +REQUIRED FLAGS + --database=DATABASE + The database to operate on. + + For example, to operate on database foo: + + $ gcloud beta firestore user-creds enable --database='foo' + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha firestore user-creds enable + diff --git a/gcloud/beta/firestore/user-creds/help b/gcloud/beta/firestore/user-creds/help new file mode 100644 index 000000000..c1ad6053b --- /dev/null +++ b/gcloud/beta/firestore/user-creds/help @@ -0,0 +1,45 @@ +NAME + gcloud beta firestore user-creds - manage the user creds for a Cloud + Firestore Database + +SYNOPSIS + gcloud beta firestore user-creds COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Manage the user creds for a Cloud Firestore Database. + +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) Creates a Cloud Firestore user creds. + + delete + (BETA) Deletes a Cloud Firestore user creds. + + describe + (BETA) Describes a Cloud Firestore user creds. + + disable + (BETA) Disables a Cloud Firestore user creds. + + enable + (BETA) Enables a Cloud Firestore user creds. + + list + (BETA) Lists user creds under a Cloud Firesore database. + + reset-password + (BETA) Resets a Cloud Firestore user creds. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha firestore user-creds + diff --git a/gcloud/beta/firestore/user-creds/list b/gcloud/beta/firestore/user-creds/list new file mode 100644 index 000000000..e01afdb4f --- /dev/null +++ b/gcloud/beta/firestore/user-creds/list @@ -0,0 +1,68 @@ +NAME + gcloud beta firestore user-creds list - lists user creds under a Cloud + Firesore database + +SYNOPSIS + gcloud beta firestore user-creds list --database=DATABASE + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + +EXAMPLES + To list all user creds under database testdb. + + $ gcloud beta firestore user-creds list --database='testdb' + +REQUIRED FLAGS + --database=DATABASE + The database to operate on. + + For example, to operate on database foo: + + $ gcloud beta firestore user-creds list --database='foo' + +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 firestore user-creds list + diff --git a/gcloud/beta/firestore/user-creds/reset-password b/gcloud/beta/firestore/user-creds/reset-password new file mode 100644 index 000000000..31d8121d4 --- /dev/null +++ b/gcloud/beta/firestore/user-creds/reset-password @@ -0,0 +1,45 @@ +NAME + gcloud beta firestore user-creds reset-password - resets a Cloud Firestore + user creds + +SYNOPSIS + gcloud beta firestore user-creds reset-password USER_CREDS + --database=DATABASE [GCLOUD_WIDE_FLAG ...] + +EXAMPLES + To reset password for user creds 'test-user-creds-id' under database + testdb. + + $ gcloud beta firestore user-creds reset-password \ + test-user-creds-id --database='testdb' + +POSITIONAL ARGUMENTS + USER_CREDS + The user creds to operate on. + + For example, to operate on user creds creds-name-1: + + $ gcloud beta firestore user-creds reset-password creds-name-1 + +REQUIRED FLAGS + --database=DATABASE + The database to operate on. + + For example, to operate on database foo: + + $ gcloud beta firestore user-creds reset-password --database='foo' + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha firestore user-creds reset-password + diff --git a/gcloud/beta/iam/workload-identity-pools/create-cred-config b/gcloud/beta/iam/workload-identity-pools/create-cred-config index d5eb79283..7080c268f 100644 --- a/gcloud/beta/iam/workload-identity-pools/create-cred-config +++ b/gcloud/beta/iam/workload-identity-pools/create-cred-config @@ -14,7 +14,7 @@ SYNOPSIS [--credential-source-type=CREDENTIAL_SOURCE_TYPE] [--enable-imdsv2] [--subject-token-type=SUBJECT_TOKEN_TYPE] [--credential-cert-private-key-path=CREDENTIAL_CERT_PRIVATE_KEY_PATH - : --credential-cert-configuration-output-file=CREDENTIAL_CERT_CONFIGURATION_OUTPUT_FILE] + : --credential-cert-configuration-output-file=CREDENTIAL_CERT_CONFIGURATION_OUTPUT_FILE --credential-cert-trust-chain-path=CREDENTIAL_CERT_TRUST_CHAIN_PATH] [--executable-output-file=EXECUTABLE_OUTPUT_FILE --executable-timeout-millis=EXECUTABLE_TIMEOUT_MILLIS] [--service-account=SERVICE_ACCOUNT @@ -153,6 +153,13 @@ OPTIONAL FLAGS If not specified, the certificate configuration will be created at the default gcloud location. + --credential-cert-trust-chain-path=CREDENTIAL_CERT_TRUST_CHAIN_PATH + Path for the trust chain file. A trust chain file is required if + there are intermediate certificates in the certificate chain in + between the root certificate stored in the workload identity pool + provider trust store. This trust chain file should be a list of PEM + certificates, with the leaf certificate at the top. + Arguments for an executable type credential source. --executable-output-file=EXECUTABLE_OUTPUT_FILE diff --git a/gcloud/beta/logging/write b/gcloud/beta/logging/write index 7673fbd85..c45ddf81e 100644 --- a/gcloud/beta/logging/write +++ b/gcloud/beta/logging/write @@ -3,6 +3,8 @@ NAME SYNOPSIS gcloud beta logging write LOG_NAME MESSAGE + [--monitored-resource-labels=[KEY=VALUE, ...,...]] + [--monitored-resource-type=MONITORED_RESOURCE_TYPE; default="global"] [--payload-type=PAYLOAD_TYPE; default="text"] [--severity=SEVERITY; default="DEFAULT"] [--billing-account=BILLING_ACCOUNT_ID | --folder=FOLDER_ID @@ -11,10 +13,8 @@ SYNOPSIS DESCRIPTION (BETA) Write a log entry. If the destination log does not exist, it will be - created. All log entries written with this command are considered to be - from the "custom.googleapis.com" v1 service or the "global" v2 resource - type. The log entries will be listed in the Logs Explorer under that - service or resource type. + created. By default, all log entries written with this command are written + with the "global" resource type. gcloud beta logging write should be used for simple testing purposes. Check Cloud Logging agent for a proper way to send log entries: @@ -35,6 +35,12 @@ EXAMPLES $ gcloud beta logging write LOG_NAME '{"key": "value"}' \ --payload-type=json + To create a log entry with a custom resource type, run: + + $ gcloud beta logging write LOG_NAME "A simple entry" \ + --monitored-resource-type=gce_instance \ + --monitored-resource-labels=zone=us-centra1-a,instance_id=1234 + POSITIONAL ARGUMENTS LOG_NAME Name of the log where the log entry will be written. @@ -44,6 +50,12 @@ POSITIONAL ARGUMENTS --payload-type=json. FLAGS + --monitored-resource-labels=[KEY=VALUE, ...,...] + Monitored Resource labels to add to the payload + + --monitored-resource-type=MONITORED_RESOURCE_TYPE; default="global" + Monitored Resource type to add to the payload + --payload-type=PAYLOAD_TYPE; default="text" Type of the log entry payload. PAYLOAD_TYPE must be one of: text, json. diff --git a/gcloud/beta/managed-kafka/clusters/create b/gcloud/beta/managed-kafka/clusters/create index 74b772f64..6938aae21 100644 --- a/gcloud/beta/managed-kafka/clusters/create +++ b/gcloud/beta/managed-kafka/clusters/create @@ -64,10 +64,11 @@ REQUIRED FLAGS --subnets=[SUBNETS,...] VPC subnets from which the cluster is accessible. Both broker and bootstrap server IP addresses and DNS entries are automatically created - in each subnet. The subnet must be located in the same region as the - cluster. The project may differ. A minimum of 1 subnet is required. A - maximum of 10 subnets can be specified. Use commas to separate multiple - subnets. The name of the subnet must be in the format + in each subnet. Only one subnet per network is allowed, and the subnet + must be located in the same region as the cluster. The project may + differ. A minimum of 1 subnet is required. A maximum of 10 subnets can + be specified. Use commas to separate multiple subnets. The name of the + subnet must be in the format projects/PROJECT_ID/regions/REGION/subnetworks/SUBNET. OPTIONAL FLAGS diff --git a/gcloud/beta/managed-kafka/clusters/update b/gcloud/beta/managed-kafka/clusters/update index e931f3d63..1ada40e15 100644 --- a/gcloud/beta/managed-kafka/clusters/update +++ b/gcloud/beta/managed-kafka/clusters/update @@ -77,11 +77,12 @@ REQUIRED FLAGS --subnets=[SUBNETS,...] VPC subnets from which the cluster is accessible. Both broker and bootstrap server IP addresses and DNS entries are automatically - created in each subnet. The subnet must be located in the same region - as the cluster. The project may differ. A minimum of 1 subnet is - required. A maximum of 10 subnets can be specified. Use commas to - separate multiple subnets. The name of the subnet must be in the - format projects/PROJECT_ID/regions/REGION/subnetworks/SUBNET. + created in each subnet. Only one subnet per network is allowed, and + the subnet must be located in the same region as the cluster. The + project may differ. A minimum of 1 subnet is required. A maximum of + 10 subnets can be specified. Use commas to separate multiple subnets. + The name of the subnet must be in the format + projects/PROJECT_ID/regions/REGION/subnetworks/SUBNET. OPTIONAL FLAGS --async diff --git a/gcloud/beta/network-security/server-tls-policies/list b/gcloud/beta/network-security/server-tls-policies/list index 0b389aa87..3ae0582c7 100644 --- a/gcloud/beta/network-security/server-tls-policies/list +++ b/gcloud/beta/network-security/server-tls-policies/list @@ -3,38 +3,37 @@ NAME ServerTlsPolicies SYNOPSIS - gcloud beta network-security server-tls-policies list --location=LOCATION + gcloud beta network-security server-tls-policies list [--location=LOCATION] [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) List all ServerTlsPolicies in the specified location of the current - project. + (BETA) List all ServerTlsPolicies in the current project. EXAMPLES To list ServerTlsPolicies in the current project, run: - $ gcloud beta network-security server-tls-policies list \ - --location=global + $ gcloud beta network-security server-tls-policies list -REQUIRED FLAGS - Location resource - The project of the ServerTlsPolicies to display. This +FLAGS + Location resource - The location of the ServerTlsPolicies 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; + ◆ if left empty, will use the wildcard '-' to list all locations with a + fully specified name; ◆ provide the argument --project on the command line; ◆ set the property core/project. - 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. + ▸ provide the argument --location on the command line; + ▸ if left empty, will use the wildcard '-' to list all locations. LIST COMMAND FLAGS --filter=EXPRESSION diff --git a/gcloud/beta/scc/findings/list-marks b/gcloud/beta/scc/findings/list-marks index 649d3c11a..89916965b 100644 --- a/gcloud/beta/scc/findings/list-marks +++ b/gcloud/beta/scc/findings/list-marks @@ -2,11 +2,12 @@ NAME gcloud beta scc findings list-marks - list a finding's security marks SYNOPSIS - gcloud beta scc findings list-marks - (FINDING : --organization=ORGANIZATION --source=SOURCE) + gcloud beta scc findings list-marks FINDING [--location=LOCATION; default="global"] [--page-token=PAGE_TOKEN] - [--read-time=READ_TIME] [--filter=EXPRESSION] [--limit=LIMIT] - [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [GCLOUD_WIDE_FLAG ...] + [--read-time=READ_TIME] [--source=SOURCE; default="-"] + [--folder=FOLDER | --organization=ORGANIZATION | --project=PROJECT] + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) List a finding's security marks. @@ -36,45 +37,8 @@ EXAMPLES --organization=123456 --source=5678 --location=eu POSITIONAL ARGUMENTS - Finding resource - The finding to be used for the SCC (Security Command - Center) command. The arguments in this group can be used to specify the - attributes of this resource. - - This must be specified. - - FINDING - ID of the finding or fully qualified identifier for the finding. - - To set the finding attribute: - ▸ provide the argument finding on the command line. - - This positional argument must be specified if any of the other - arguments in this group are specified. - - --organization=ORGANIZATION - (Optional) If the full resource name isn't provided e.g. - organizations/123, then provide the organization id which is the - suffix of the organization. Example: organizations/123, the id is - 123. - - To set the organization attribute: - ▸ provide the argument finding on the command line with a fully - specified name; - ▸ provide the argument --organization on the command line; - ▸ Set the organization property in configuration using gcloud - config set scc/organization if it is not specified in command - line.. - - --source=SOURCE - (Optional) If the full resource name isn't provided e.g. - organizations/123/sources/456, then provide the source id which is - the suffix of the source. Example: organizations/123/sources/456, the - id is 456. - - To set the source attribute: - ▸ provide the argument finding on the command line with a fully - specified name; - ▸ provide the argument --source on the command line. + FINDING + ID of the finding or fully qualified identifier for the finding. FLAGS --location=LOCATION; default="global" @@ -104,6 +68,20 @@ FLAGS (https://cloud.google.com/security-command-center/docs/release-notes#April_15_2024) on the SCC release notes page. + --source=SOURCE; default="-" + Source id. Defaults to all sources. + + At most one of these can be specified: + + --folder=FOLDER + The folder ID (e.g., 456) that contains the finding. + + --organization=ORGANIZATION + The organization ID (e.g., 123) that contains the finding. + + --project=PROJECT + The project ID (e.g., example-project) that contains the finding. + LIST COMMAND FLAGS --filter=EXPRESSION Apply a Boolean filter EXPRESSION to each resource item to be listed. diff --git a/gcloud/beta/scc/findings/update b/gcloud/beta/scc/findings/update index 5fca5a286..a7c698a09 100644 --- a/gcloud/beta/scc/findings/update +++ b/gcloud/beta/scc/findings/update @@ -2,12 +2,12 @@ NAME gcloud beta scc findings update - update a Security Command Center finding SYNOPSIS - gcloud beta scc findings update - (FINDING : --organization=ORGANIZATION --source=SOURCE) - [--event-time=EVENT_TIME] [--external-uri=EXTERNAL_URI] - [--location=LOCATION; default="global"] - [--source-properties=[KEY=VALUE,...]] [--state=STATE] - [--update-mask=UPDATE_MASK] [GCLOUD_WIDE_FLAG ...] + gcloud beta scc findings update FINDING [--event-time=EVENT_TIME] + [--external-uri=EXTERNAL_URI] [--location=LOCATION; default="global"] + [--source=SOURCE; default="-"] [--source-properties=[KEY=VALUE,...]] + [--state=STATE] [--update-mask=UPDATE_MASK] + [--folder=FOLDER | --organization=ORGANIZATION | --project=PROJECT] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) Update a Security Command Center finding. @@ -50,45 +50,8 @@ EXAMPLES --location=eu POSITIONAL ARGUMENTS - Finding resource - The finding to be used for the SCC (Security Command - Center) command. The arguments in this group can be used to specify the - attributes of this resource. - - This must be specified. - - FINDING - ID of the finding or fully qualified identifier for the finding. - - To set the finding attribute: - ▸ provide the argument finding on the command line. - - This positional argument must be specified if any of the other - arguments in this group are specified. - - --organization=ORGANIZATION - (Optional) If the full resource name isn't provided e.g. - organizations/123, then provide the organization id which is the - suffix of the organization. Example: organizations/123, the id is - 123. - - To set the organization attribute: - ▸ provide the argument finding on the command line with a fully - specified name; - ▸ provide the argument --organization on the command line; - ▸ Set the organization property in configuration using gcloud - config set scc/organization if it is not specified in command - line.. - - --source=SOURCE - (Optional) If the full resource name isn't provided e.g. - organizations/123/sources/456, then provide the source id which is - the suffix of the source. Example: organizations/123/sources/456, the - id is 456. - - To set the source attribute: - ▸ provide the argument finding on the command line with a fully - specified name; - ▸ provide the argument --source on the command line. + FINDING + ID of the finding or fully qualified identifier for the finding. FLAGS --event-time=EVENT_TIME @@ -115,6 +78,9 @@ FLAGS location that is specified when data residency controls are enabled for Security Command Center. + --source=SOURCE; default="-" + Source id. Defaults to all sources. + --source-properties=[KEY=VALUE,...] Source specific properties. These properties are managed by the source that writes the finding. The key names in the source_properties map @@ -141,6 +107,17 @@ FLAGS State can be toggled from ACTIVE to INACTIVE and vice-versa but it cannot be deleted. + At most one of these can be specified: + + --folder=FOLDER + The folder ID (e.g., 456) that contains the finding. + + --organization=ORGANIZATION + The organization ID (e.g., 123) that contains the finding. + + --project=PROJECT + The project ID (e.g., example-project) that contains the finding. + 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/scc/findings/update-marks b/gcloud/beta/scc/findings/update-marks index 6764709f2..cd8fb34ee 100644 --- a/gcloud/beta/scc/findings/update-marks +++ b/gcloud/beta/scc/findings/update-marks @@ -3,11 +3,12 @@ NAME finding's security marks SYNOPSIS - gcloud beta scc findings update-marks - (FINDING : --organization=ORGANIZATION --source=SOURCE) + gcloud beta scc findings update-marks FINDING [--location=LOCATION; default="global"] - [--security-marks=[KEY=VALUE,...]] [--start-time=START_TIME] - [--update-mask=UPDATE_MASK] [GCLOUD_WIDE_FLAG ...] + [--security-marks=[KEY=VALUE,...]] [--source=SOURCE; default="-"] + [--start-time=START_TIME] [--update-mask=UPDATE_MASK] + [--folder=FOLDER | --organization=ORGANIZATION | --project=PROJECT] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) Update Security Command Center finding's security marks. @@ -53,45 +54,8 @@ EXAMPLES --security-marks="key1=v1,key2=v2" --location=eu POSITIONAL ARGUMENTS - Finding resource - The finding to be used for the SCC (Security Command - Center) command. The arguments in this group can be used to specify the - attributes of this resource. - - This must be specified. - - FINDING - ID of the finding or fully qualified identifier for the finding. - - To set the finding attribute: - ▸ provide the argument finding on the command line. - - This positional argument must be specified if any of the other - arguments in this group are specified. - - --organization=ORGANIZATION - (Optional) If the full resource name isn't provided e.g. - organizations/123, then provide the organization id which is the - suffix of the organization. Example: organizations/123, the id is - 123. - - To set the organization attribute: - ▸ provide the argument finding on the command line with a fully - specified name; - ▸ provide the argument --organization on the command line; - ▸ Set the organization property in configuration using gcloud - config set scc/organization if it is not specified in command - line.. - - --source=SOURCE - (Optional) If the full resource name isn't provided e.g. - organizations/123/sources/456, then provide the source id which is - the suffix of the source. Example: organizations/123/sources/456, the - id is 456. - - To set the source attribute: - ▸ provide the argument finding on the command line with a fully - specified name; - ▸ provide the argument --source on the command line. + FINDING + ID of the finding or fully qualified identifier for the finding. FLAGS --location=LOCATION; default="global" @@ -110,6 +74,9 @@ FLAGS key=value pair separated by comma (,). For example: --security-marks="key1=val1,key2=val2". + --source=SOURCE; default="-" + Source id. Defaults to all sources. + --start-time=START_TIME Time at which the updated SecurityMarks take effect. See $ gcloud topic datetimes for information on supported time formats. @@ -121,6 +88,17 @@ FLAGS marks for the given finding either skip the update-mask flag or provide an empty value (--update-mask '') for it. + At most one of these can be specified: + + --folder=FOLDER + The folder ID (e.g., 456) that contains the finding. + + --organization=ORGANIZATION + The organization ID (e.g., 123) that contains the finding. + + --project=PROJECT + The project ID (e.g., example-project) that contains the finding. + 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/sql/backups/restore b/gcloud/beta/sql/backups/restore index 02e315c35..23b48c154 100644 --- a/gcloud/beta/sql/backups/restore +++ b/gcloud/beta/sql/backups/restore @@ -14,7 +14,6 @@ SYNOPSIS [--backup-project=BACKUP_PROJECT] [--backup-start-time=BACKUP_START_TIME] [--collation=COLLATION] [--connector-enforcement=CONNECTOR_ENFORCEMENT] [--cpu=CPU] - [--database-flags=FLAG=VALUE,[FLAG=VALUE,...]] [--database-version=DATABASE_VERSION] [--[no-]deletion-protection] [--deny-maintenance-period-end-date=DENY_MAINTENANCE_PERIOD_END_DATE] [--deny-maintenance-period-start-date=DENY_MAINTENANCE_PERIOD_START_DATE] @@ -163,14 +162,6 @@ OPTIONAL FLAGS machine. Both --cpu and --memory must be specified if a custom machine type is desired, and the --tier flag must be omitted. - --database-flags=FLAG=VALUE,[FLAG=VALUE,...] - Comma-separated list of database flags to set on the instance. Use an - equals sign to separate flag name and value. Flags without values, like - skip_grant_tables, can be written out without a value after, e.g., - skip_grant_tables=. Use on/off for booleans. View the Instance Resource - API for allowed flags. (e.g., --database-flags - max_allowed_packet=55555,skip_grant_tables=,log_output=1) - --database-version=DATABASE_VERSION The database engine type and versions. If left unspecified, no changes occur. See the list of database versions at diff --git a/gcloud/bigtable/help b/gcloud/bigtable/help index fb159d9c2..79a6be93a 100644 --- a/gcloud/bigtable/help +++ b/gcloud/bigtable/help @@ -36,6 +36,9 @@ GROUPS logical-views Manage Bigtable logical views. + materialized-views + Manage Bigtable materialized views. + operations Manage Cloud Bigtable operations. diff --git a/gcloud/bigtable/instances/tables/create b/gcloud/bigtable/instances/tables/create index 96da8c76b..b48d0c163 100644 --- a/gcloud/bigtable/instances/tables/create +++ b/gcloud/bigtable/instances/tables/create @@ -5,7 +5,9 @@ SYNOPSIS gcloud bigtable instances tables create (TABLE : --instance=INSTANCE) --column-families=[COLUMN_FAMILIES,...] [--change-stream-retention-period=CHANGE_STREAM_RETENTION_PERIOD] - [--deletion-protection] [--splits=[SPLITS,...]] + [--deletion-protection] + [--row-key-schema-definition-file=ROW_KEY_SCHEMA_DEFINITION_FILE] + [--row-key-schema-pre-encoded-bytes] [--splits=[SPLITS,...]] [--automated-backup-retention-period=AUTOMATED_BACKUP_RETENTION_PERIOD | --enable-automated-backup] [GCLOUD_WIDE_FLAG ...] @@ -124,6 +126,34 @@ OPTIONAL FLAGS --deletion-protection Once specified, the table is deletion protected. + --row-key-schema-definition-file=ROW_KEY_SCHEMA_DEFINITION_FILE + The row key schema for the table. The schema is defined in a YAML or + JSON file, equivalent to the StructType protobuf message. + + Example YAML: + + encoding: + delimitedBytes: + delimiter: '#' + fields: + - fieldName: field1 + type: + bytesType: + encoding: + raw: {} + - fieldName: field2 + type: + bytesType: + encoding: + raw: {} + + --row-key-schema-pre-encoded-bytes + By default, Base64 encoding is applied to all binary fields in the + YAML/JSON file (for example, encoding.delimitedBytes.delimiter). + + Use this to indicate that all binary fields are already encoded in the + YAML/JSON file and should not be encoded again. + --splits=[SPLITS,...] Row keys where the table should initially be split. For example: car,key diff --git a/gcloud/bigtable/instances/tables/update b/gcloud/bigtable/instances/tables/update index a574e7fbb..4dc23073b 100644 --- a/gcloud/bigtable/instances/tables/update +++ b/gcloud/bigtable/instances/tables/update @@ -4,11 +4,14 @@ NAME SYNOPSIS gcloud bigtable instances tables update (TABLE : --instance=INSTANCE) - [--async] [--deletion-protection] + [--async] [--deletion-protection] [--row-key-schema-pre-encoded-bytes] [--automated-backup-retention-period=AUTOMATED_BACKUP_RETENTION_PERIOD | --disable-automated-backup | --enable-automated-backup] [--change-stream-retention-period=CHANGE_STREAM_RETENTION_PERIOD - | --clear-change-stream-retention-period] [GCLOUD_WIDE_FLAG ...] + | --clear-change-stream-retention-period] + [--clear-row-key-schema + | --row-key-schema-definition-file=ROW_KEY_SCHEMA_DEFINITION_FILE] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION Update an existing new Cloud Bigtable table with the specified @@ -92,6 +95,16 @@ FLAGS --deletion-protection Once specified, the table is deletion protected. + --row-key-schema-pre-encoded-bytes + By default, Base64 encoding is applied to all binary fields in the + YAML/JSON file (for example, encoding.delimitedBytes.delimiter). + + Use this to indicate that all binary fields are already encoded in the + YAML/JSON file and should not be encoded again. + + This field is only used when row-key-schema-definition-file is set. It + is ignored if clear-row-key-schema is set. + At most one of these can be specified: --automated-backup-retention-period=AUTOMATED_BACKUP_RETENTION_PERIOD @@ -120,6 +133,35 @@ FLAGS This disables the change stream and eventually removes the change stream data. + Whether to update or clear the row key schema in the updated table. Only + one of these flags can be set. + + At most one of these can be specified: + + --clear-row-key-schema + Whether to clear the row key schema in the updated table. + + --row-key-schema-definition-file=ROW_KEY_SCHEMA_DEFINITION_FILE + The row key schema for the table. The schema is defined in a YAML or + JSON file, equivalent to the StructType protobuf message. + + Example YAML: + + encoding: + delimitedBytes: + delimiter: '#' + fields: + - fieldName: field1 + type: + bytesType: + encoding: + raw: {} + - fieldName: field2 + type: + bytesType: + encoding: + raw: {} + 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/bigtable/materialized-views/create b/gcloud/bigtable/materialized-views/create new file mode 100644 index 000000000..b46acd5cd --- /dev/null +++ b/gcloud/bigtable/materialized-views/create @@ -0,0 +1,77 @@ +NAME + gcloud bigtable materialized-views create - create a new Bigtable + materialized view + +SYNOPSIS + gcloud bigtable materialized-views create + (MATERIALIZED_VIEW : --instance=INSTANCE) --query=QUERY [--async] + [--deletion-protection=DELETION_PROTECTION] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Create a new Bigtable materialized view. + +EXAMPLES + To create a materialized view, run: $ gcloud bigtable materialized-views create \ + my-materialized-view-id --instance=my-instance-id \ + --query="SELECT my-column-family FROM my-table \ + --deletion-protection=false" + +POSITIONAL ARGUMENTS + Materialized view resource - The materialized view 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 materialized_view 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. + + MATERIALIZED_VIEW + ID of the materialized view or fully qualified identifier for the + materialized view. + + To set the name attribute: + ▸ provide the argument materialized_view on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --instance=INSTANCE + Bigtable instance for the materialized view. + + To set the instance attribute: + ▸ provide the argument materialized_view on the command line with a + fully specified name; + ▸ provide the argument --instance on the command line. + +REQUIRED FLAGS + --query=QUERY + The query of the view. + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --deletion-protection=DELETION_PROTECTION + Whether the view is protected from deletion. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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 bigtable materialized-views create + + $ gcloud beta bigtable materialized-views create + diff --git a/gcloud/bigtable/materialized-views/delete b/gcloud/bigtable/materialized-views/delete new file mode 100644 index 000000000..2509f3f2c --- /dev/null +++ b/gcloud/bigtable/materialized-views/delete @@ -0,0 +1,64 @@ +NAME + gcloud bigtable materialized-views delete - delete a Bigtable materialized + view + +SYNOPSIS + gcloud bigtable materialized-views delete + (MATERIALIZED_VIEW : --instance=INSTANCE) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Delete a Bigtable materialized view. + +EXAMPLES + To delete a materialized view, run: + + $ gcloud bigtable materialized-views delete \ + my-materialized-view-id --instance=my-instance-id + +POSITIONAL ARGUMENTS + Materialized view resource - The materialized view 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 materialized_view 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. + + MATERIALIZED_VIEW + ID of the materialized view or fully qualified identifier for the + materialized view. + + To set the name attribute: + ▸ provide the argument materialized_view on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --instance=INSTANCE + Bigtable instance for the materialized view. + + To set the instance attribute: + ▸ provide the argument materialized_view on the command line with a + fully specified name; + ▸ provide the argument --instance 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 + These variants are also available: + + $ gcloud alpha bigtable materialized-views delete + + $ gcloud beta bigtable materialized-views delete + diff --git a/gcloud/bigtable/materialized-views/describe b/gcloud/bigtable/materialized-views/describe new file mode 100644 index 000000000..12b268411 --- /dev/null +++ b/gcloud/bigtable/materialized-views/describe @@ -0,0 +1,64 @@ +NAME + gcloud bigtable materialized-views describe - describe an existing Bigtable + materialized view + +SYNOPSIS + gcloud bigtable materialized-views describe + (MATERIALIZED_VIEW : --instance=INSTANCE) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Describe an existing Bigtable materialized view. + +EXAMPLES + To view a materialized view's description, run: + + $ gcloud bigtable materialized-views describe \ + my-materialized-view-id --instance=my-instance-id + +POSITIONAL ARGUMENTS + Materialized view resource - The materialized view 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 materialized_view 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. + + MATERIALIZED_VIEW + ID of the materialized view or fully qualified identifier for the + materialized view. + + To set the name attribute: + ▸ provide the argument materialized_view on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --instance=INSTANCE + Bigtable instance for the materialized view. + + To set the instance attribute: + ▸ provide the argument materialized_view on the command line with a + fully specified name; + ▸ provide the argument --instance 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 + These variants are also available: + + $ gcloud alpha bigtable materialized-views describe + + $ gcloud beta bigtable materialized-views describe + diff --git a/gcloud/bigtable/materialized-views/help b/gcloud/bigtable/materialized-views/help new file mode 100644 index 000000000..466030465 --- /dev/null +++ b/gcloud/bigtable/materialized-views/help @@ -0,0 +1,39 @@ +NAME + gcloud bigtable materialized-views - manage Bigtable materialized views + +SYNOPSIS + gcloud bigtable materialized-views COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Manage Bigtable materialized views. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + create + Create a new Bigtable materialized view. + + delete + Delete a Bigtable materialized view. + + describe + Describe an existing Bigtable materialized view. + + list + List existing Bigtable materialized views. + + update + Update a Bigtable materialized view. + +NOTES + These variants are also available: + + $ gcloud alpha bigtable materialized-views + + $ gcloud beta bigtable materialized-views + diff --git a/gcloud/bigtable/materialized-views/list b/gcloud/bigtable/materialized-views/list new file mode 100644 index 000000000..4a8b9e143 --- /dev/null +++ b/gcloud/bigtable/materialized-views/list @@ -0,0 +1,83 @@ +NAME + gcloud bigtable materialized-views list - list existing Bigtable + materialized views + +SYNOPSIS + gcloud bigtable materialized-views list --instance=INSTANCE + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + List existing Bigtable materialized views. + +EXAMPLES + To list all materialized views for an instance, run: + + $ gcloud bigtable materialized-views list --instance=my-instance-id + +REQUIRED FLAGS + Instance resource - The instance to list materialized views for. This + represents a Cloud resource. (NOTE) Some attributes are not given + arguments in this group but can be set in other ways. + + To set the project attribute: + ◆ provide the argument --instance on the command line with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + --instance=INSTANCE + ID of the instance or fully qualified identifier for the instance. + + To set the instance attribute: + ▸ provide the argument --instance on the command line. + +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 bigtable materialized-views list + + $ gcloud beta bigtable materialized-views list + diff --git a/gcloud/bigtable/materialized-views/update b/gcloud/bigtable/materialized-views/update new file mode 100644 index 000000000..502853396 --- /dev/null +++ b/gcloud/bigtable/materialized-views/update @@ -0,0 +1,74 @@ +NAME + gcloud bigtable materialized-views update - update a Bigtable materialized + view + +SYNOPSIS + gcloud bigtable materialized-views update + (MATERIALIZED_VIEW : --instance=INSTANCE) + --deletion-protection=DELETION_PROTECTION [--async] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Update a Bigtable materialized view. + +EXAMPLES + To update a materialized view, run: $ gcloud bigtable materialized-views update \ + my-materialized-view-id --instance=my-instance-id \ + --deletion-protection=true" + +POSITIONAL ARGUMENTS + Materialized view resource - The materialized view 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 materialized_view 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. + + MATERIALIZED_VIEW + ID of the materialized view or fully qualified identifier for the + materialized view. + + To set the name attribute: + ▸ provide the argument materialized_view on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --instance=INSTANCE + Bigtable instance for the materialized view. + + To set the instance attribute: + ▸ provide the argument materialized_view on the command line with a + fully specified name; + ▸ provide the argument --instance on the command line. + +REQUIRED FLAGS + --deletion-protection=DELETION_PROTECTION + Whether the view is protected from deletion. + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + These variants are also available: + + $ gcloud alpha bigtable materialized-views update + + $ gcloud beta bigtable materialized-views update + diff --git a/gcloud/bigtable/tables/create b/gcloud/bigtable/tables/create index 37f8e977e..166da8d7d 100644 --- a/gcloud/bigtable/tables/create +++ b/gcloud/bigtable/tables/create @@ -5,7 +5,9 @@ SYNOPSIS gcloud bigtable tables create (TABLE : --instance=INSTANCE) --column-families=[COLUMN_FAMILIES,...] [--change-stream-retention-period=CHANGE_STREAM_RETENTION_PERIOD] - [--deletion-protection] [--splits=[SPLITS,...]] + [--deletion-protection] + [--row-key-schema-definition-file=ROW_KEY_SCHEMA_DEFINITION_FILE] + [--row-key-schema-pre-encoded-bytes] [--splits=[SPLITS,...]] [--automated-backup-retention-period=AUTOMATED_BACKUP_RETENTION_PERIOD | --enable-automated-backup] [GCLOUD_WIDE_FLAG ...] @@ -118,6 +120,34 @@ OPTIONAL FLAGS --deletion-protection Once specified, the table is deletion protected. + --row-key-schema-definition-file=ROW_KEY_SCHEMA_DEFINITION_FILE + The row key schema for the table. The schema is defined in a YAML or + JSON file, equivalent to the StructType protobuf message. + + Example YAML: + + encoding: + delimitedBytes: + delimiter: '#' + fields: + - fieldName: field1 + type: + bytesType: + encoding: + raw: {} + - fieldName: field2 + type: + bytesType: + encoding: + raw: {} + + --row-key-schema-pre-encoded-bytes + By default, Base64 encoding is applied to all binary fields in the + YAML/JSON file (for example, encoding.delimitedBytes.delimiter). + + Use this to indicate that all binary fields are already encoded in the + YAML/JSON file and should not be encoded again. + --splits=[SPLITS,...] Row keys where the table should initially be split. For example: car,key diff --git a/gcloud/bigtable/tables/update b/gcloud/bigtable/tables/update index 89e3f265e..f06f7d53b 100644 --- a/gcloud/bigtable/tables/update +++ b/gcloud/bigtable/tables/update @@ -3,11 +3,14 @@ NAME SYNOPSIS gcloud bigtable tables update (TABLE : --instance=INSTANCE) [--async] - [--deletion-protection] + [--deletion-protection] [--row-key-schema-pre-encoded-bytes] [--automated-backup-retention-period=AUTOMATED_BACKUP_RETENTION_PERIOD | --disable-automated-backup | --enable-automated-backup] [--change-stream-retention-period=CHANGE_STREAM_RETENTION_PERIOD - | --clear-change-stream-retention-period] [GCLOUD_WIDE_FLAG ...] + | --clear-change-stream-retention-period] + [--clear-row-key-schema + | --row-key-schema-definition-file=ROW_KEY_SCHEMA_DEFINITION_FILE] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION Update an existing new Cloud Bigtable table with the specified @@ -91,6 +94,16 @@ FLAGS --deletion-protection Once specified, the table is deletion protected. + --row-key-schema-pre-encoded-bytes + By default, Base64 encoding is applied to all binary fields in the + YAML/JSON file (for example, encoding.delimitedBytes.delimiter). + + Use this to indicate that all binary fields are already encoded in the + YAML/JSON file and should not be encoded again. + + This field is only used when row-key-schema-definition-file is set. It + is ignored if clear-row-key-schema is set. + At most one of these can be specified: --automated-backup-retention-period=AUTOMATED_BACKUP_RETENTION_PERIOD @@ -119,6 +132,35 @@ FLAGS This disables the change stream and eventually removes the change stream data. + Whether to update or clear the row key schema in the updated table. Only + one of these flags can be set. + + At most one of these can be specified: + + --clear-row-key-schema + Whether to clear the row key schema in the updated table. + + --row-key-schema-definition-file=ROW_KEY_SCHEMA_DEFINITION_FILE + The row key schema for the table. The schema is defined in a YAML or + JSON file, equivalent to the StructType protobuf message. + + Example YAML: + + encoding: + delimitedBytes: + delimiter: '#' + fields: + - fieldName: field1 + type: + bytesType: + encoding: + raw: {} + - fieldName: field2 + type: + bytesType: + encoding: + raw: {} + 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/compute/commitments/create b/gcloud/compute/commitments/create index a8e29ffd8..05922c92b 100644 --- a/gcloud/compute/commitments/create +++ b/gcloud/compute/commitments/create @@ -103,13 +103,13 @@ OPTIONAL FLAGS Type of commitment. memory-optimized indicates that the commitment is for memory-optimized VMs. TYPE must be one of: accelerator-optimized, accelerator-optimized-a3, accelerator-optimized-a3-mega, - accelerator-optimized-a3-ultra, compute-optimized, - compute-optimized-c2d, compute-optimized-c3, compute-optimized-c3d, - compute-optimized-h3, general-purpose, general-purpose-c4, - general-purpose-c4a, general-purpose-e2, general-purpose-n2, - general-purpose-n2d, general-purpose-n4, general-purpose-t2d, - graphics-optimized, memory-optimized, memory-optimized-m3, - memory-optimized-m4, memory-optimized-x4-16tb, + accelerator-optimized-a3-ultra, accelerator-optimized-a4, + compute-optimized, compute-optimized-c2d, compute-optimized-c3, + compute-optimized-c3d, compute-optimized-h3, general-purpose, + general-purpose-c4, general-purpose-c4a, general-purpose-e2, + general-purpose-n2, general-purpose-n2d, general-purpose-n4, + general-purpose-t2d, graphics-optimized, memory-optimized, + memory-optimized-m3, memory-optimized-m4, memory-optimized-x4-16tb, memory-optimized-x4-24tb, memory-optimized-x4-32tb, storage-optimized-z3. @@ -221,15 +221,23 @@ OPTIONAL FLAGS Manage the properties of a shared reservation to create --share-setting=SHARE_SETTING - Specify if this reservation is shared, and if so, the type of - sharing. If you omit this flag, this value is local (not shared) - by default. SHARE_SETTING must be one of: local, projects. + The projects that can use the reservation. SHARE_SETTING must be + one of: + + local + Only your project can use the reservation. This is the + default value. + projects + Your project and up to 100 other projects within your + project's organization can use the reservation. If you + specify this value, then you must also include the + --share-with flag in the command. --share-with=SHARE_WITH,[SHARE_WITH,...] - If this reservation is shared (--share-setting is not local), - provide a list of all of the specific projects that this - reservation is shared with. List must contain project IDs or - project numbers. + If this reservation is shared (--share-setting=projects), then + specify a comma-separated list of projects to share the + reservation with. List projects using project IDs or project + numbers. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/compute/config-ssh b/gcloud/compute/config-ssh index 78b79ae26..4cca441e1 100644 --- a/gcloud/compute/config-ssh +++ b/gcloud/compute/config-ssh @@ -31,7 +31,9 @@ DESCRIPTION $ scp ~/MY-FILE example-instance.us-central1-a.MY-PROJECT:~ Whenever instances are added, removed, or their external IP addresses are - changed, this command should be re-executed to update the configuration. + changed, the remove command must be run to clear the existing configuration + and then the command can set executed to set the configuration to the + current state. This command ensures that the user's public SSH key is present in the project's metadata. If the user does not have a public SSH key, one is diff --git a/gcloud/compute/images/list b/gcloud/compute/images/list index c94cc69a5..7be05b92c 100644 --- a/gcloud/compute/images/list +++ b/gcloud/compute/images/list @@ -54,7 +54,8 @@ FLAGS are available include the following: cos-cloud, debian-cloud, rocky-linux-cloud, ubuntu-os-cloud, centos-cloud, fedora-coreos-cloud, opensuse-cloud, oracle-linux-cloud, rhel-cloud, rhel-sap-cloud, - suse-cloud, suse-sap-cloud, ubuntu-os-pro-cloud, windows-cloud, + rocky-linux-accelerator-cloud, suse-cloud, suse-sap-cloud, + ubuntu-os-accelerator-images, ubuntu-os-pro-cloud, windows-cloud, windows-sql-cloud. Enabled by default, use --no-standard-images to disable. diff --git a/gcloud/compute/instance-groups/managed/resize-requests/create b/gcloud/compute/instance-groups/managed/resize-requests/create index 36efca7ec..0330b483f 100644 --- a/gcloud/compute/instance-groups/managed/resize-requests/create +++ b/gcloud/compute/instance-groups/managed/resize-requests/create @@ -40,8 +40,9 @@ OPTIONAL FLAGS day, 2 hours, 3 minutes, and 4 seconds. The value must be between 10m (10 minutes) and 7d (7 days). - If you want the managed instance group to consume a reservation, then - this flag is optional. Otherwise, it's required. + If you want the managed instance group to consume a reservation or use + FLEX_START provisioning model, then this flag is optional. Otherwise, + it's required. --zone=ZONE Zone of the managed instance group to operate on. If not specified and diff --git a/gcloud/compute/reservations/create b/gcloud/compute/reservations/create index cf1da5b32..da5333380 100644 --- a/gcloud/compute/reservations/create +++ b/gcloud/compute/reservations/create @@ -152,14 +152,21 @@ OPTIONAL FLAGS Manage the properties of a shared reservation. --share-setting=SHARE_SETTING - Specify if this reservation is shared, and if so, the type of - sharing. If you omit this flag, this value is local (not shared) by - default. SHARE_SETTING must be one of: local, projects. + The projects that can use the reservation. SHARE_SETTING must be one + of: + + local + Only your project can use the reservation. This is the default + value. + projects + Your project and up to 100 other projects within your project's + organization can use the reservation. If you specify this value, + then you must also include the --share-with flag in the command. --share-with=SHARE_WITH,[SHARE_WITH,...] - If this reservation is shared (--share-setting is not local), provide - a list of all of the specific projects that this reservation is - shared with. List must contain project IDs or project numbers. + If this reservation is shared (--share-setting=projects), then + specify a comma-separated list of projects to share the reservation + with. List projects using project IDs or project numbers. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/compute/reservations/update b/gcloud/compute/reservations/update index a89703475..7c2c393ad 100644 --- a/gcloud/compute/reservations/update +++ b/gcloud/compute/reservations/update @@ -40,9 +40,9 @@ POSITIONAL ARGUMENTS FLAGS --add-share-with=PROJECT,[PROJECT,...] - A list of specific projects to add to the list of projects that this - reservation is shared with. List must contain project IDs or project - numbers. + If this reservation is shared (--share-setting is projects), then + specify a comma-separated list of projects to share the reservation + with. You must list the projects using project IDs or project numbers. --remove-share-with=PROJECT,[PROJECT,...] A list of specific projects to remove from the list of projects that diff --git a/gcloud/compute/routers/nats/create b/gcloud/compute/routers/nats/create index e5a2de958..243996de5 100644 --- a/gcloud/compute/routers/nats/create +++ b/gcloud/compute/routers/nats/create @@ -2,10 +2,7 @@ NAME gcloud compute routers nats create - add a NAT to a Compute Engine router SYNOPSIS - gcloud compute routers nats create NAME --router=ROUTER - (--nat-all-subnet-ip-ranges - | --nat-custom-subnet-ip-ranges=SUBNETWORK[:RANGE_NAME|:ALL],[...] - | --nat-primary-subnet-ip-ranges) [--async] + gcloud compute routers nats create NAME --router=ROUTER [--async] [--auto-network-tier=AUTO_NETWORK_TIER] [--[no-]enable-dynamic-port-allocation] [--enable-endpoint-independent-mapping] [--enable-logging] @@ -19,6 +16,11 @@ SYNOPSIS [--type=TYPE] [--udp-idle-timeout=UDP_IDLE_TIMEOUT] [--auto-allocate-nat-external-ips | --nat-external-ip-pool=IP_ADDRESS,[IP_ADDRESS,...]] + [--nat-all-subnet-ip-ranges + | --nat-custom-subnet-ip-ranges=SUBNETWORK[:RANGE_NAME|:ALL],[...] + | --nat-primary-subnet-ip-ranges] + [--nat64-all-v6-subnet-ip-ranges + | --nat64-custom-v6-subnet-ip-ranges=SUBNETWORK,[SUBNETWORK,...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -56,28 +58,6 @@ REQUIRED FLAGS --router=ROUTER The Router to use for NAT. - Exactly one of these must be specified: - - --nat-all-subnet-ip-ranges - Allow all IP ranges of all subnetworks in the region, including - primary and secondary ranges, to use NAT. - - --nat-custom-subnet-ip-ranges=SUBNETWORK[:RANGE_NAME|:ALL],[...] - List of subnetwork primary and secondary IP ranges to be allowed to - use NAT. - - ▸ SUBNETWORK:ALL - specifying a subnetwork name with ALL includes - the primary range and all secondary ranges of the subnet. - ▸ SUBNETWORK - including a subnetwork name includes only the - primary subnet range of the subnetwork. - ▸ SUBNETWORK:RANGE_NAME - specifying a subnetwork and secondary - range name includes only that secondary range. It does not include - the primary range of the subnet. - - --nat-primary-subnet-ip-ranges - Allow only primary IP ranges of all subnetworks in the region to use - NAT. - OPTIONAL FLAGS --async Return immediately, without waiting for the operation in progress to @@ -240,6 +220,42 @@ OPTIONAL FLAGS --nat-external-ip-pool=IP_ADDRESS,[IP_ADDRESS,...] External IP Addresses to use for Cloud NAT + Options for IPv4 subnetwork ranges. If not specified, one of the options + for IPv6 subnetwork ranges must be provided. + + At most one of these can be specified: + + --nat-all-subnet-ip-ranges + Allow all IP ranges of all subnetworks in the region, including + primary and secondary ranges, to use NAT. + + --nat-custom-subnet-ip-ranges=SUBNETWORK[:RANGE_NAME|:ALL],[...] + List of subnetwork primary and secondary IP ranges to be allowed to + use NAT. + + ▸ SUBNETWORK:ALL - specifying a subnetwork name with ALL includes + the primary range and all secondary ranges of the subnet. + ▸ SUBNETWORK - including a subnetwork name includes only the + primary subnet range of the subnetwork. + ▸ SUBNETWORK:RANGE_NAME - specifying a subnetwork and secondary + range name includes only that secondary range. It does not include + the primary range of the subnet. + + --nat-primary-subnet-ip-ranges + Allow only primary IP ranges of all subnetworks in the region to use + NAT. + + Options for IPv6 subnetwork ranges. If not specified, one of the options + for IPv4 subnetwork ranges must be provided. + + At most one of these can be specified: + + --nat64-all-v6-subnet-ip-ranges + Allow all IPv6 subnetwork ranges in the region to use NAT. + + --nat64-custom-v6-subnet-ip-ranges=SUBNETWORK,[SUBNETWORK,...] + List of subnetworks with IPv6 ranges to be allowed to use NAT. + 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/compute/routers/nats/update b/gcloud/compute/routers/nats/update index 91472a073..5caea1f2e 100644 --- a/gcloud/compute/routers/nats/update +++ b/gcloud/compute/routers/nats/update @@ -15,6 +15,11 @@ SYNOPSIS [--clear-min-ports-per-vm | --min-ports-per-vm=MIN_PORTS_PER_VM] [--clear-nat-external-drain-ip-pool | --nat-external-drain-ip-pool=NAT_EXTERNAL_DRAIN_IP_POOL,[...]] + [--clear-nat-subnet-ip-ranges | --nat-all-subnet-ip-ranges + | --nat-custom-subnet-ip-ranges=SUBNETWORK[:RANGE_NAME|:ALL],[...] + | --nat-primary-subnet-ip-ranges] + [--clear-nat64-subnet-ip-ranges | --nat64-all-v6-subnet-ip-ranges + | --nat64-custom-v6-subnet-ip-ranges=SUBNETWORK,[SUBNETWORK,...]] [--clear-tcp-established-idle-timeout | --tcp-established-idle-timeout=TCP_ESTABLISHED_IDLE_TIMEOUT] [--clear-tcp-time-wait-timeout @@ -22,9 +27,7 @@ SYNOPSIS [--clear-tcp-transitory-idle-timeout | --tcp-transitory-idle-timeout=TCP_TRANSITORY_IDLE_TIMEOUT] [--clear-udp-idle-timeout | --udp-idle-timeout=UDP_IDLE_TIMEOUT] - [--nat-all-subnet-ip-ranges - | --nat-custom-subnet-ip-ranges=SUBNETWORK[:RANGE_NAME|:ALL],[...] - | --nat-primary-subnet-ip-ranges] [GCLOUD_WIDE_FLAG ...] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION gcloud compute routers nats update is used to update a NAT in a Compute @@ -206,6 +209,46 @@ OPTIONAL FLAGS These IPs must be valid external IPs that have been used as NAT IPs + Options for IPv4 subnetwork ranges. + + At most one of these can be specified: + + --clear-nat-subnet-ip-ranges + Clear IPv4 subnetwork ranges. + + --nat-all-subnet-ip-ranges + Allow all IP ranges of all subnetworks in the region, including + primary and secondary ranges, to use NAT. + + --nat-custom-subnet-ip-ranges=SUBNETWORK[:RANGE_NAME|:ALL],[...] + List of subnetwork primary and secondary IP ranges to be allowed to + use NAT. + + ▸ SUBNETWORK:ALL - specifying a subnetwork name with ALL includes + the primary range and all secondary ranges of the subnet. + ▸ SUBNETWORK - including a subnetwork name includes only the + primary subnet range of the subnetwork. + ▸ SUBNETWORK:RANGE_NAME - specifying a subnetwork and secondary + range name includes only that secondary range. It does not include + the primary range of the subnet. + + --nat-primary-subnet-ip-ranges + Allow only primary IP ranges of all subnetworks in the region to use + NAT. + + Options for IPv6 subnetwork ranges. + + At most one of these can be specified: + + --clear-nat64-subnet-ip-ranges + Clear IPv6 subnetwork ranges. + + --nat64-all-v6-subnet-ip-ranges + Allow all IPv6 subnetwork ranges in the region to use NAT. + + --nat64-custom-v6-subnet-ip-ranges=SUBNETWORK,[SUBNETWORK,...] + List of subnetworks with IPv6 ranges to be allowed to use NAT. + At most one of these can be specified: --clear-tcp-established-idle-timeout @@ -246,28 +289,6 @@ OPTIONAL FLAGS https://cloud.google.com/sdk/gcloud/reference/topic/datetimes for information on duration formats. - At most one of these can be specified: - - --nat-all-subnet-ip-ranges - Allow all IP ranges of all subnetworks in the region, including - primary and secondary ranges, to use NAT. - - --nat-custom-subnet-ip-ranges=SUBNETWORK[:RANGE_NAME|:ALL],[...] - List of subnetwork primary and secondary IP ranges to be allowed to - use NAT. - - ▸ SUBNETWORK:ALL - specifying a subnetwork name with ALL includes - the primary range and all secondary ranges of the subnet. - ▸ SUBNETWORK - including a subnetwork name includes only the - primary subnet range of the subnetwork. - ▸ SUBNETWORK:RANGE_NAME - specifying a subnetwork and secondary - range name includes only that secondary range. It does not include - the primary range of the subnet. - - --nat-primary-subnet-ip-ranges - Allow only primary IP ranges of all subnetworks in the region to use - NAT. - 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/compute/tpus/queued-resources/create b/gcloud/compute/tpus/queued-resources/create index 069aa42c2..c1ac70f60 100644 --- a/gcloud/compute/tpus/queued-resources/create +++ b/gcloud/compute/tpus/queued-resources/create @@ -76,7 +76,7 @@ POSITIONAL ARGUMENTS REQUIRED FLAGS --runtime-version=RUNTIME_VERSION - Runtime version for the TPU, such as 2.3. + Runtime version for the TPU, such as tpu-ubuntu2204-base. Specify a chip-based or core-based TPU node. diff --git a/gcloud/container/clusters/create b/gcloud/container/clusters/create index bdb72534f..dc5abdcf9 100644 --- a/gcloud/container/clusters/create +++ b/gcloud/container/clusters/create @@ -21,6 +21,7 @@ SYNOPSIS [--cluster-version=CLUSTER_VERSION] [--containerd-config-from-file=PATH_TO_FILE] [--create-subnetwork=[KEY=VALUE,...]] + [--data-cache-count=DATA_CACHE_COUNT] [--database-encryption-key=DATABASE_ENCRYPTION_KEY] [--default-max-pods-per-node=DEFAULT_MAX_PODS_PER_NODE] [--disable-default-snat] [--disable-l4-lb-firewall-reconciliation] @@ -398,6 +399,10 @@ FLAGS Cannot be specified unless '--enable-ip-alias' option is also specified. Cannot be used in conjunction with '--subnetwork' option. + --data-cache-count=DATA_CACHE_COUNT + Specifies the number of local SSDs to be utilized for GKE Data Cache in + the cluster. + --database-encryption-key=DATABASE_ENCRYPTION_KEY Enable Database Encryption. diff --git a/gcloud/container/clusters/get-upgrade-info b/gcloud/container/clusters/get-upgrade-info new file mode 100644 index 000000000..28e61e897 --- /dev/null +++ b/gcloud/container/clusters/get-upgrade-info @@ -0,0 +1,56 @@ +NAME + gcloud container clusters get-upgrade-info - get information about upgrades + for existing clusters including auto upgrade status, upgrade history, + upgrade targets, and end of support timelines + +SYNOPSIS + gcloud container clusters get-upgrade-info NAME + [--location=LOCATION | --region=REGION | --zone=ZONE, -z ZONE] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Get information about upgrades for existing clusters including auto upgrade + status, upgrade history, upgrade targets, and end of support timelines. + +EXAMPLES + To get upgrade information for an existing cluster, run: + + $ gcloud container clusters get-upgrade-info sample-cluster + +POSITIONAL ARGUMENTS + NAME + The name of your existing cluster. + +FLAGS + At most one of these can be specified: + + --location=LOCATION + Compute zone or region (e.g. us-central1-a or us-central1) for the + cluster. Overrides the default compute/region or compute/zone value + for this command invocation. Prefer using this flag over the --region + or --zone flags. + + --region=REGION + Compute region (e.g. us-central1) for a regional cluster. Overrides + the default compute/region property value for this command + invocation. + + --zone=ZONE, -z ZONE + Compute zone (e.g. us-central1-a) for a zonal cluster. Overrides the + default compute/zone 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 + These variants are also available: + + $ gcloud alpha container clusters get-upgrade-info + + $ gcloud beta container clusters get-upgrade-info + diff --git a/gcloud/container/clusters/help b/gcloud/container/clusters/help index 1715e6ed6..52c21d086 100644 --- a/gcloud/container/clusters/help +++ b/gcloud/container/clusters/help @@ -58,6 +58,11 @@ COMMANDS get-credentials Fetch credentials for a running cluster. + get-upgrade-info + Get information about upgrades for existing clusters including auto + upgrade status, upgrade history, upgrade targets, and end of support + timelines. + list List existing clusters for running containers. diff --git a/gcloud/container/node-pools/create b/gcloud/container/node-pools/create index e8f060ccb..26bcb1c21 100644 --- a/gcloud/container/node-pools/create +++ b/gcloud/container/node-pools/create @@ -15,7 +15,8 @@ SYNOPSIS pod-ipv4-range=SECONDARY_RANGE_NAME, [max-pods-per-node=NUM_PODS],...]] [--async] [--boot-disk-kms-key=BOOT_DISK_KMS_KEY] [--cluster=CLUSTER] - [--containerd-config-from-file=PATH_TO_FILE] [--disk-size=DISK_SIZE] + [--containerd-config-from-file=PATH_TO_FILE] + [--data-cache-count=DATA_CACHE_COUNT] [--disk-size=DISK_SIZE] [--disk-type=DISK_TYPE] [--enable-autoprovisioning] [--enable-autorepair] [--no-enable-autoupgrade] [--enable-blue-green-upgrade] [--enable-confidential-nodes] @@ -38,9 +39,12 @@ SYNOPSIS [--node-locations=ZONE,[ZONE,...]] [--node-pool-soak-duration=NODE_POOL_SOAK_DURATION] [--node-taints=[NODE_TAINT,...]] [--node-version=NODE_VERSION] - [--num-nodes=NUM_NODES] [--placement-policy=PLACEMENT_POLICY] - [--placement-type=PLACEMENT_TYPE] [--preemptible] - [--resource-manager-tags=[KEY=VALUE,...]] [--sandbox=[type=TYPE]] + [--num-nodes=NUM_NODES] + [--opportunistic-maintenance=[node-idle-time=NODE_IDLE_TIME, + window=WINDOW,min-nodes=MIN_NODES,...]] + [--placement-policy=PLACEMENT_POLICY] [--placement-type=PLACEMENT_TYPE] + [--preemptible] [--resource-manager-tags=[KEY=VALUE,...]] + [--sandbox=[type=TYPE]] [--secondary-boot-disk=[disk-image=DISK_IMAGE,[mode=MODE],...]] [--shielded-integrity-monitoring] [--shielded-secure-boot] [--sole-tenant-node-affinity-file=SOLE_TENANT_NODE_AFFINITY_FILE] @@ -198,6 +202,10 @@ FLAGS Use a full or relative path to a local file containing the value of containerd_config. + --data-cache-count=DATA_CACHE_COUNT + Specifies the number of local SSDs to be utilized for GKE Data Cache in + the node pool. + --disk-size=DISK_SIZE Size for node VM boot disks in GB. Defaults to 100GB. @@ -543,6 +551,26 @@ FLAGS types the number of nodes will be defaulted to (product of topology)/(# of chips per VM). + --opportunistic-maintenance=[node-idle-time=NODE_IDLE_TIME,window=WINDOW,min-nodes=MIN_NODES,...] + Opportunistic maintenance options. + + node-idle-time: Time to be spent waiting for node to be idle before + starting maintenance, ending with 's'. Example: "3.5s" + + window: The window of time that opportunistic maintenance can run, + ending with 's'. Example: A setting of 14 days (1209600s) implies that + opportunistic maintenance can only be ran in the 2 weeks leading up to + the scheduled maintenance date. Setting 28 days(2419200s) allows + opportunistic maintenance to run at any time in the scheduled + maintenance window. + + min-nodes: Minimum number of nodes in the node pool to be available + during the opportunistic triggered maintenance. + + $ gcloud container node-pools create example-cluster \ + --opportunistic-maintenance=node-idle-time=600s,window=600s,\ + min-nodes=2 + --placement-policy=PLACEMENT_POLICY Indicates the desired resource policy to use. diff --git a/gcloud/container/node-pools/get-upgrade-info b/gcloud/container/node-pools/get-upgrade-info new file mode 100644 index 000000000..6085aa506 --- /dev/null +++ b/gcloud/container/node-pools/get-upgrade-info @@ -0,0 +1,61 @@ +NAME + gcloud container node-pools get-upgrade-info - get upgrade information for + an existing node pool for a cluster + +SYNOPSIS + gcloud container node-pools get-upgrade-info NAME [--cluster=CLUSTER] + [--location=LOCATION | --region=REGION | --zone=ZONE, -z ZONE] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + gcloud container node-pools get-upgrade-info displays all upgrade + information associated with the node pool in the Google Kubernetes Engine + cluster. + +EXAMPLES + To get upgrade information for a node pool of an existing cluster, run: + + $ gcloud container node-pools get-upgrade-info node-pool-1 \ + --cluster=sample-cluster + +POSITIONAL ARGUMENTS + NAME + The name of the node pool. + +FLAGS + --cluster=CLUSTER + The name of the cluster. Overrides the default container/cluster + property value for this command invocation. + + At most one of these can be specified: + + --location=LOCATION + Compute zone or region (e.g. us-central1-a or us-central1) for the + cluster. Overrides the default compute/region or compute/zone value + for this command invocation. Prefer using this flag over the --region + or --zone flags. + + --region=REGION + Compute region (e.g. us-central1) for a regional cluster. Overrides + the default compute/region property value for this command + invocation. + + --zone=ZONE, -z ZONE + Compute zone (e.g. us-central1-a) for a zonal cluster. Overrides the + default compute/zone 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 + These variants are also available: + + $ gcloud alpha container node-pools get-upgrade-info + + $ gcloud beta container node-pools get-upgrade-info + diff --git a/gcloud/container/node-pools/help b/gcloud/container/node-pools/help index d6a55182e..aa9ab6959 100644 --- a/gcloud/container/node-pools/help +++ b/gcloud/container/node-pools/help @@ -48,6 +48,9 @@ COMMANDS describe Describe an existing node pool for a cluster. + get-upgrade-info + Get upgrade information for an existing node pool for a cluster. + list List existing node pools for a cluster. diff --git a/gcloud/database-migration/migration-jobs/create b/gcloud/database-migration/migration-jobs/create index 414962a1d..ce2a28021 100644 --- a/gcloud/database-migration/migration-jobs/create +++ b/gcloud/database-migration/migration-jobs/create @@ -13,6 +13,8 @@ SYNOPSIS [--all-databases | --databases-filter=databaseName,[...]] [--cmek-key=CMEK_KEY : --cmek-keyring=CMEK_KEYRING --cmek-project=CMEK_PROJECT] + [--max-concurrent-cdc-connections=MAX_CONCURRENT_CDC_CONNECTIONS + --max-concurrent-full-dump-connections=MAX_CONCURRENT_FULL_DUMP_CONNECTIONS --skip-full-dump --oracle-cdc-start-position=ORACLE_CDC_START_POSITION | --sqlserver-cdc-start-position=SQLSERVER_CDC_START_POSITION --max-concurrent-destination-connections=MAX_CONCURRENT_DESTINATION_CONNECTIONS --transaction-timeout=TRANSACTION_TIMEOUT] [--peer-vpc=PEER_VPC | --static-ip | [--vm-ip=VM_IP --vm-port=VM_PORT --vpc=VPC : --vm=VM]] [--sqlserver-databases=databaseName,[...] : --sqlserver-diff-backup @@ -272,6 +274,47 @@ OPTIONAL FLAGS specified name; ▸ provide the argument --cmek-project on the command line. + The heterogeneous migration config. This is used only for Oracle to Cloud + SQL for PostgreSQL and SQL Server to Cloud SQL for PostgreSQL migrations. + + Configuration for Oracle or SQL Server as a source in a heterogeneous + migration. + + --max-concurrent-cdc-connections=MAX_CONCURRENT_CDC_CONNECTIONS + Maximum number of connections Database Migration Service will open + to the source for CDC phase. + + --max-concurrent-full-dump-connections=MAX_CONCURRENT_FULL_DUMP_CONNECTIONS + Maximum number of connections Database Migration Service will open + to the source for full dump phase. + + Configuration for skipping full dump. + + --skip-full-dump + Whether to skip full dump or not. + + Configuration for CDC start position. + + At most one of these can be specified: + + --oracle-cdc-start-position=ORACLE_CDC_START_POSITION + Oracle schema change number (SCN) to start CDC data migration + from. + + --sqlserver-cdc-start-position=SQLSERVER_CDC_START_POSITION + Sqlserver log squence number (LSN) to start CDC data migration + from. + + Configuration for Postgres as a destination in a heterogeneous + migration. + + --max-concurrent-destination-connections=MAX_CONCURRENT_DESTINATION_CONNECTIONS + Maximum number of concurrent connections Database Migration Service + will open to the destination for data migration. + + --transaction-timeout=TRANSACTION_TIMEOUT + Timeout for data migration transactions. + The connectivity method used by the migration job. If a connectivity method isn't specified, then it isn't added to the migration job. diff --git a/gcloud/database-migration/private-connections/create b/gcloud/database-migration/private-connections/create index 3ec3137cf..1bcf773c7 100644 --- a/gcloud/database-migration/private-connections/create +++ b/gcloud/database-migration/private-connections/create @@ -6,7 +6,7 @@ SYNOPSIS gcloud database-migration private-connections create (PRIVATE_CONNECTION : --region=REGION) --display-name=DISPLAY_NAME (--subnet=SUBNET --vpc=VPC) [--no-async] [--labels=[KEY=VALUE,...]] - [GCLOUD_WIDE_FLAG ...] + [--skip-validation] [GCLOUD_WIDE_FLAG ...] DESCRIPTION Create a Database Migration private connection @@ -97,6 +97,9 @@ OPTIONAL FLAGS contain only hyphens (-), underscores (_), lowercase characters, and numbers. + --skip-validation + Creates the private connection without running prior verifications. + 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/dataflow/flex-template/run b/gcloud/dataflow/flex-template/run index 379325730..b652ca4c4 100644 --- a/gcloud/dataflow/flex-template/run +++ b/gcloud/dataflow/flex-template/run @@ -53,7 +53,7 @@ OPTIONAL FLAGS --additional-user-labels=[ADDITIONAL_USER_LABELS,...] Additional user labels to pass to the job. Example: - --additional-user-labels='{"key1":"value1"}' + --additional-user-labels='key1=value1,key2=value2' --dataflow-kms-key=DATAFLOW_KMS_KEY Cloud KMS key to protect the job resources. diff --git a/gcloud/dataflow/jobs/run b/gcloud/dataflow/jobs/run index 08f8ad726..363f32091 100644 --- a/gcloud/dataflow/jobs/run +++ b/gcloud/dataflow/jobs/run @@ -4,6 +4,7 @@ NAME SYNOPSIS gcloud dataflow jobs run JOB_NAME --gcs-location=GCS_LOCATION [--additional-experiments=[ADDITIONAL_EXPERIMENTS,...]] + [--additional-user-labels=[ADDITIONAL_USER_LABELS,...]] [--dataflow-kms-key=DATAFLOW_KMS_KEY] [--disable-public-ips] [--enable-streaming-engine] [--max-workers=MAX_WORKERS] [--network=NETWORK] [--num-workers=NUM_WORKERS] @@ -33,6 +34,10 @@ OPTIONAL FLAGS Additional experiments to pass to the job. These experiments are appended to any experiments already set by the template. + --additional-user-labels=[ADDITIONAL_USER_LABELS,...] + Additional user labels to pass to the job. Example: + --additional-user-labels='key1=value1,key2=value2' + --dataflow-kms-key=DATAFLOW_KMS_KEY The Cloud KMS key to protect the job resources. diff --git a/gcloud/dataproc/clusters/create b/gcloud/dataproc/clusters/create index 81955493b..dad1a68f0 100644 --- a/gcloud/dataproc/clusters/create +++ b/gcloud/dataproc/clusters/create @@ -45,8 +45,7 @@ SYNOPSIS [--secondary-worker-standard-capacity-base=SECONDARY_WORKER_STANDARD_CAPACITY_BASE] [--secondary-worker-standard-capacity-percent-above-base=SECONDARY_WORKER_STANDARD_CAPACITY_PERCENT_ABOVE_BASE] [--shielded-integrity-monitoring] [--shielded-secure-boot] - [--shielded-vtpm] [--stop-max-idle=STOP_MAX_IDLE] - [--temp-bucket=TEMP_BUCKET] + [--shielded-vtpm] [--temp-bucket=TEMP_BUCKET] [--worker-accelerator=[type=TYPE,[count=COUNT],...]] [--worker-boot-disk-provisioned-iops=WORKER_BOOT_DISK_PROVISIONED_IOPS] [--worker-boot-disk-provisioned-throughput=WORKER_BOOT_DISK_PROVISIONED_THROUGHPUT] @@ -83,8 +82,6 @@ SYNOPSIS --num-secondary-workers=NUM_SECONDARY_WORKERS --num-workers=NUM_WORKERS --secondary-worker-type=TYPE; default="preemptible"] - [--stop-expiration-time=STOP_EXPIRATION_TIME - | --stop-max-age=STOP_MAX_AGE] [--worker-machine-type=WORKER_MACHINE_TYPE | --worker-machine-types=type=MACHINE_TYPE[, type=MACHINE_TYPE...][,rank=RANK]] [GCLOUD_WIDE_FLAG ...] @@ -449,11 +446,6 @@ FLAGS security operations, such as remote attestation, encryption, and sealing of keys. - --stop-max-idle=STOP_MAX_IDLE - The duration after the last job completes to auto-stop the cluster, - such as "2h" or "1d". See $ gcloud topic datetimes for information on - duration formats. - --temp-bucket=TEMP_BUCKET The Google Cloud Storage bucket to use by default to store ephemeral cluster and jobs data, such as Spark and MapReduce history files. @@ -1018,18 +1010,6 @@ FLAGS The type of the secondary worker group. TYPE must be one of: preemptible, non-preemptible, spot. - At most one of these can be specified: - - --stop-expiration-time=STOP_EXPIRATION_TIME - The time when the cluster will be auto-stopped, such as - "2017-08-29T18:52:51.142Z." See $ gcloud topic datetimes for - information on time formats. - - --stop-max-age=STOP_MAX_AGE - The lifespan of the cluster, with auto-stop upon completion, such as - "2h" or "1d". See $ gcloud topic datetimes for information on - duration formats. - At most one of these can be specified: --worker-machine-type=WORKER_MACHINE_TYPE diff --git a/gcloud/dataproc/clusters/update b/gcloud/dataproc/clusters/update index f8443da4f..24c5880cf 100644 --- a/gcloud/dataproc/clusters/update +++ b/gcloud/dataproc/clusters/update @@ -15,11 +15,7 @@ SYNOPSIS | --expiration-time=EXPIRATION_TIME | --max-age=MAX_AGE | --no-max-age] [--delete-max-idle=DELETE_MAX_IDLE | --no-delete-max-idle - | --max-idle=MAX_IDLE | --no-max-idle] - [--stop-expiration-time=STOP_EXPIRATION_TIME - | --stop-max-age=STOP_MAX_AGE | --no-stop-max-age] - [--stop-max-idle=STOP_MAX_IDLE | --no-stop-max-idle] - [GCLOUD_WIDE_FLAG ...] + | --max-idle=MAX_IDLE | --no-max-idle] [GCLOUD_WIDE_FLAG ...] DESCRIPTION Update the number of worker nodes and/or the labels in a cluster. @@ -220,33 +216,6 @@ FLAGS Cancels the cluster auto-deletion by cluster idle duration (configured by --max-idle flag) - At most one of these can be specified: - - --stop-expiration-time=STOP_EXPIRATION_TIME - The time when the cluster will be auto-stopped, such as - "2017-08-29T18:52:51.142Z". See $ gcloud topic datetimes for - information on time formats. - - --stop-max-age=STOP_MAX_AGE - The lifespan of the cluster, with auto-stop upon completion, such as - "2h" or "1d". See $ gcloud topic datetimes for information on - duration formats. - - --no-stop-max-age - Cancels the cluster auto-stop by maximum cluster age (configured by - --stop-max-age or --stop-expiration-time flags) - - At most one of these can be specified: - - --stop-max-idle=STOP_MAX_IDLE - The duration after the last job completes to auto-stop the cluster, - such as "2h" or "1d". See $ gcloud topic datetimes for information on - duration formats. - - --no-stop-max-idle - Cancels the cluster auto-stop by cluster idle duration (configured by - --stop-max-idle flag) - GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, diff --git a/gcloud/edge-cloud/container/clusters/node-pools/update b/gcloud/edge-cloud/container/clusters/node-pools/update index 15d2243de..072a18e1f 100644 --- a/gcloud/edge-cloud/container/clusters/node-pools/update +++ b/gcloud/edge-cloud/container/clusters/node-pools/update @@ -5,10 +5,11 @@ NAME SYNOPSIS gcloud edge-cloud container clusters node-pools update (NODE_POOL : --cluster=CLUSTER --location=LOCATION) [--async] - [--lro-timeout=LRO_TIMEOUT] [--machine-filter=MACHINE_FILTER] - [--node-count=NODE_COUNT] [--node-labels=[KEY=VALUE,...]] - [--update-labels=[KEY=VALUE,...]] - [--clear-labels | --remove-labels=[KEY,...]] [GCLOUD_WIDE_FLAG ...] + [--local-disk-kms-key=LOCAL_DISK_KMS_KEY] [--lro-timeout=LRO_TIMEOUT] + [--machine-filter=MACHINE_FILTER] [--node-count=NODE_COUNT] + [--node-labels=[KEY=VALUE,...]] [--update-labels=[KEY=VALUE,...]] + [--use-google-managed-key] [--clear-labels | --remove-labels=[KEY,...]] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION Updates an Edge Container node pool. @@ -65,6 +66,13 @@ FLAGS Return immediately, without waiting for the operation in progress to complete. + --local-disk-kms-key=LOCAL_DISK_KMS_KEY + Google Cloud KMS key that will be used to secure local disks on nodes + in this node pool. The Edge Container service account for this project + must have roles/cloudkms.cryptoKeyEncrypterDecrypter on the key. + + If not provided, a Google-managed key will be used instead. + --lro-timeout=LRO_TIMEOUT Overwrite the default LRO maximum timeout. @@ -89,6 +97,10 @@ FLAGS contain only hyphens (-), underscores (_), lowercase characters, and numbers. + --use-google-managed-key + Once specified, a Google-managed key will be used for the control plane + disk encryption. + At most one of these can be specified: --clear-labels diff --git a/gcloud/edge-cloud/container/clusters/update b/gcloud/edge-cloud/container/clusters/update index 81a50be5f..0481096d3 100644 --- a/gcloud/edge-cloud/container/clusters/update +++ b/gcloud/edge-cloud/container/clusters/update @@ -8,6 +8,8 @@ SYNOPSIS [--release-channel=RELEASE_CHANNEL] [--clear-maintenance-window | --remove-maintenance-exclusion-window=REMOVE_MAINTENANCE_EXCLUSION_WINDOW | --add-maintenance-exclusion-end=ADD_MAINTENANCE_EXCLUSION_END --add-maintenance-exclusion-name=ADD_MAINTENANCE_EXCLUSION_NAME --add-maintenance-exclusion-start=ADD_MAINTENANCE_EXCLUSION_START | --maintenance-window-end=MAINTENANCE_WINDOW_END --maintenance-window-recurrence=MAINTENANCE_WINDOW_RECURRENCE --maintenance-window-start=MAINTENANCE_WINDOW_START] + [--control-plane-kms-key=CONTROL_PLANE_KMS_KEY + | --use-google-managed-key] [--use-google-managed-zone-key | --zone-storage-kms-key=ZONE_STORAGE_KMS_KEY] [GCLOUD_WIDE_FLAG ...] @@ -123,6 +125,16 @@ FLAGS 3339 (https://www.ietf.org/rfc/rfc3339.txt) format. E.g. "2021-01-01T00:00:00Z" or "2021-01-01T00:00:00-05:00" + At most one of these can be specified: + + --control-plane-kms-key=CONTROL_PLANE_KMS_KEY + If set, use the specified KMS key for the cluster control plane nodes + encryption. + + --use-google-managed-key + If set, use Google managed key for the cluster control plane nodes + encryption. + At most one of these can be specified: --use-google-managed-zone-key diff --git a/gcloud/firestore/databases/create b/gcloud/firestore/databases/create index 31637d806..44403ce2c 100644 --- a/gcloud/firestore/databases/create +++ b/gcloud/firestore/databases/create @@ -5,10 +5,17 @@ NAME SYNOPSIS gcloud firestore databases create --location=LOCATION [--database=DATABASE; default="(default)"] [--delete-protection] - [--enable-pitr] [--kms-key-name=KMS_KEY_NAME] - [--type=TYPE; default="firestore-native"] [GCLOUD_WIDE_FLAG ...] + [--edition=EDITION; default="standard"] [--enable-pitr] + [--kms-key-name=KMS_KEY_NAME] [--type=TYPE; default="firestore-native"] + [GCLOUD_WIDE_FLAG ...] EXAMPLES + To create a Firestore Enterprise database named foo in nam5 for use with + Ignite APIs. + + $ gcloud firestore databases create --database=foo \ + --edition=enterprise --location=nam5 + To create a Firestore Native database in nam5. $ gcloud firestore databases create --location=nam5 @@ -71,6 +78,10 @@ OPTIONAL FLAGS Default to false. + --edition=EDITION; default="standard" + The edition of the database. EDITION must be one of: standard, + enterprise. + --enable-pitr Whether to enable Point In Time Recovery (PITR) on the created database. diff --git a/gcloud/firestore/indexes/composite/create b/gcloud/firestore/indexes/composite/create index 5e4ade314..3ee040d31 100644 --- a/gcloud/firestore/indexes/composite/create +++ b/gcloud/firestore/indexes/composite/create @@ -7,6 +7,7 @@ SYNOPSIS [field-path=FIELD-PATH],[order=ORDER],[vector-config=VECTOR-CONFIG] (--collection-group=COLLECTION_GROUP : --database=DATABASE) [--api-scope=API_SCOPE; default="any-api"] [--async] + [--density=DENSITY] [--multikey] [--query-scope=QUERY_SCOPE; default="collection"] [GCLOUD_WIDE_FLAG ...] @@ -102,12 +103,25 @@ REQUIRED FLAGS OPTIONAL FLAGS --api-scope=API_SCOPE; default="any-api" Api scope the index applies to. API_SCOPE must be one of: any-api, - datastore-mode-api. + datastore-mode-api, mongodb-compatible-api. --async Return immediately, without waiting for the operation in progress to complete. + --density=DENSITY + Density of the index. DENSITY must be one of: dense, + density-unspecified, sparse-all, sparse-any. + + --multikey + Optional. Whether the index is multikey. By default, the index is not + multikey. For non-multikey indexes, none of the paths in the index + definition reach or traverse an array, except via an explicit array + index. For multikey indexes, at most one of the paths in the index + definition reach or traverse an array, except via an explicit array + index. Violations will result in errors. Note this field only applies + to index with MONGODB_COMPATIBLE_API ApiScope. + --query-scope=QUERY_SCOPE; default="collection" Query scope the index applies to. QUERY_SCOPE must be one of: collection, collection-group, collection-recursive. diff --git a/gcloud/gemini/code-repository-indexes/create b/gcloud/gemini/code-repository-indexes/create index 303981fe3..5523ce45a 100644 --- a/gcloud/gemini/code-repository-indexes/create +++ b/gcloud/gemini/code-repository-indexes/create @@ -100,12 +100,6 @@ FLAGS ignore the request if it has already been completed. The server will guarantee that for at least 60 minutes since the first request. - For example, consider a situation where you make an initial request and - the request times out. If you make the request again with the same - request ID, the server can check if original operation with the same - request ID was received, and if so, will ignore the second request. - This prevents clients from accidentally creating duplicate commitments. - The request ID must be a valid UUID with the exception that zero UUID is not supported (00000000-0000-0000-0000-000000000000). diff --git a/gcloud/gemini/code-repository-indexes/delete b/gcloud/gemini/code-repository-indexes/delete index 411b8a725..dbf2cf834 100644 --- a/gcloud/gemini/code-repository-indexes/delete +++ b/gcloud/gemini/code-repository-indexes/delete @@ -65,12 +65,6 @@ FLAGS ignore the request if it has already been completed. The server will guarantee that for at least 60 minutes after the first request. - For example, consider a situation where you make an initial request and - the request times out. If you make the request again with the same - request ID, the server can check if original operation with the same - request ID was received, and if so, will ignore the second request. - This prevents clients from accidentally creating duplicate commitments. - The request ID must be a valid UUID with the exception that zero UUID is not supported (00000000-0000-0000-0000-000000000000). diff --git a/gcloud/gemini/code-repository-indexes/repository-groups/create b/gcloud/gemini/code-repository-indexes/repository-groups/create index bcef325b3..11914e4e9 100644 --- a/gcloud/gemini/code-repository-indexes/repository-groups/create +++ b/gcloud/gemini/code-repository-indexes/repository-groups/create @@ -112,8 +112,8 @@ REQUIRED FLAGS https://github.com/google/re2/wiki/syntax for syntax. resource - The link to the DeveloperConnect repository resource name or URL to - be indexed. + The DeveloperConnect repository full resource name, relative + resource name or resource URL to be indexed. Shorthand Example: @@ -161,12 +161,6 @@ OPTIONAL FLAGS ignore the request if it has already been completed. The server will guarantee that for at least 60 minutes since the first request. - For example, consider a situation where you make an initial request and - the request times out. If you make the request again with the same - request ID, the server can check if original operation with the same - request ID was received, and if so, will ignore the second request. - This prevents clients from accidentally creating duplicate commitments. - The request ID must be a valid UUID with the exception that zero UUID is not supported (00000000-0000-0000-0000-000000000000). diff --git a/gcloud/gemini/code-repository-indexes/repository-groups/delete b/gcloud/gemini/code-repository-indexes/repository-groups/delete index 20969c9b7..ea113af28 100644 --- a/gcloud/gemini/code-repository-indexes/repository-groups/delete +++ b/gcloud/gemini/code-repository-indexes/repository-groups/delete @@ -71,12 +71,6 @@ FLAGS ignore the request if it has already been completed. The server will guarantee that for at least 60 minutes after the first request. - For example, consider a situation where you make an initial request and - the request times out. If you make the request again with the same - request ID, the server can check if original operation with the same - request ID was received, and if so, will ignore the second request. - This prevents clients from accidentally creating duplicate commitments. - The request ID must be a valid UUID with the exception that zero UUID is not supported (00000000-0000-0000-0000-000000000000). diff --git a/gcloud/gemini/code-repository-indexes/repository-groups/update b/gcloud/gemini/code-repository-indexes/repository-groups/update index f57b18977..25f05197b 100644 --- a/gcloud/gemini/code-repository-indexes/repository-groups/update +++ b/gcloud/gemini/code-repository-indexes/repository-groups/update @@ -83,12 +83,6 @@ FLAGS ignore the request if it has already been completed. The server will guarantee that for at least 60 minutes since the first request. - For example, consider a situation where you make an initial request and - the request times out. If you make the request again with the same - request ID, the server can check if original operation with the same - request ID was received, and if so, will ignore the second request. - This prevents clients from accidentally creating duplicate commitments. - The request ID must be a valid UUID with the exception that zero UUID is not supported (00000000-0000-0000-0000-000000000000). @@ -162,8 +156,8 @@ FLAGS https://github.com/google/re2/wiki/syntax for syntax. resource - The link to the DeveloperConnect repository resource name or URL - to be indexed. + The DeveloperConnect repository full resource name, relative + resource name or resource URL to be indexed. Shorthand Example: @@ -185,8 +179,8 @@ FLAGS https://github.com/google/re2/wiki/syntax for syntax. resource - The link to the DeveloperConnect repository resource name or URL - to be indexed. + The DeveloperConnect repository full resource name, relative + resource name or resource URL to be indexed. Shorthand Example: @@ -214,8 +208,8 @@ FLAGS https://github.com/google/re2/wiki/syntax for syntax. resource - The link to the DeveloperConnect repository resource name or - URL to be indexed. + The DeveloperConnect repository full resource name, relative + resource name or resource URL to be indexed. Shorthand Example: diff --git a/gcloud/gemini/code-repository-indexes/update b/gcloud/gemini/code-repository-indexes/update index f9a9fa40f..678b5b2aa 100644 --- a/gcloud/gemini/code-repository-indexes/update +++ b/gcloud/gemini/code-repository-indexes/update @@ -64,12 +64,6 @@ FLAGS ignore the request if it has already been completed. The server will guarantee that for at least 60 minutes since the first request. - For example, consider a situation where you make an initial request and - the request times out. If you make the request again with the same - request ID, the server can check if original operation with the same - request ID was received, and if so, will ignore the second request. - This prevents clients from accidentally creating duplicate commitments. - The request ID must be a valid UUID with the exception that zero UUID is not supported (00000000-0000-0000-0000-000000000000). diff --git a/gcloud/gemini/code-tools-settings/create b/gcloud/gemini/code-tools-settings/create new file mode 100644 index 000000000..ebc4f1c49 --- /dev/null +++ b/gcloud/gemini/code-tools-settings/create @@ -0,0 +1,141 @@ +NAME + gcloud gemini code-tools-settings create - create codeToolsSettings + +SYNOPSIS + gcloud gemini code-tools-settings create + (CODE_TOOLS_SETTING : --location=LOCATION) + --enabled-tool=[accountConnector=ACCOUNTCONNECTOR], + [config=CONFIG],[handle=HANDLE],[tool=TOOL],[uriOverride=URIOVERRIDE] + [--labels=[LABELS,...]] [--request-id=REQUEST_ID] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Create a codeToolsSetting + +EXAMPLES + To create the codeToolsSetting, run: + + $ gcloud gemini code-tools-settings create + +POSITIONAL ARGUMENTS + CodeToolsSetting resource - Identifier. Name of the resource. + Format:projects/{project}/locations/{location}/codeToolsSettings/{codeToolsSetting} + 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 code_tools_setting 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. + + CODE_TOOLS_SETTING + ID of the codeToolsSetting or fully qualified identifier for the + codeToolsSetting. + + To set the code_tools_setting attribute: + ▸ provide the argument code_tools_setting on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + The location id of the codeToolsSetting resource. + + To set the location attribute: + ▸ provide the argument code_tools_setting on the command line with + a fully specified name; + ▸ provide the argument --location on the command line. + +REQUIRED FLAGS + --enabled-tool=[accountConnector=ACCOUNTCONNECTOR],[config=CONFIG],[handle=HANDLE],[tool=TOOL],[uriOverride=URIOVERRIDE] + Required, Represents the full set of enabled tools. + + accountConnector + Link to the Dev Connect Account Connector that holds the user + credentials. + projects/{project}/locations/{location}/accountConnectors/{account_connector_id}. + + config + Configuration parameters for the tool. + + key + Key of the configuration item. + + value + Value of the configuration item. + + handle + Handle used to invoke the tool. + + tool + Link to the Tool. + + uriOverride + Overridden URI, if allowed by Tool. + + Shorthand Example: + + --enabled-tool=accountConnector=string,config=[{key=string,value=string}],handle=string,tool=string,uriOverride=string --enabled-tool=accountConnector=string,config=[{key=string,value=string}],handle=string,tool=string,uriOverride=string + + JSON Example: + + --enabled-tool='[{"accountConnector": "string", "config": [{"key": "string", "value": "string"}], "handle": "string", "tool": "string", "uriOverride": "string"}]' + + File Example: + + --enabled-tool=path_to_file.(yaml|json) + +OPTIONAL FLAGS + --labels=[LABELS,...] + Labels as key value pairs. + + KEY + Keys must start with a lowercase character and contain only hyphens + (-), underscores (_), lowercase characters, and numbers. + + VALUE + Values must contain only hyphens (-), underscores (_), lowercase + characters, and numbers. + + Shorthand Example: + + --labels=string=string + + JSON Example: + + --labels='{"string": "string"}' + + File Example: + + --labels=path_to_file.(yaml|json) + + --request-id=REQUEST_ID + An optional request ID to identify requests. Specify a unique request + ID so that if you must retry your request, the server will know to + ignore the request if it has already been completed. The server will + guarantee that for at least 60 minutes since the first request. + + For example, consider a situation where you make an initial request and + the request times out. If you make the request again with the same + request ID, the server can check if original operation with the same + request ID was received, and if so, will ignore the second request. + This prevents clients from accidentally creating duplicate commitments. + + The request ID must be a valid UUID with the exception that zero UUID + is not supported (00000000-0000-0000-0000-000000000000). + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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 cloudaicompanion/v1 API. The full documentation for + this API can be found at: https://cloud.google.com/gemini diff --git a/gcloud/gemini/code-tools-settings/delete b/gcloud/gemini/code-tools-settings/delete new file mode 100644 index 000000000..4f8f1b702 --- /dev/null +++ b/gcloud/gemini/code-tools-settings/delete @@ -0,0 +1,80 @@ +NAME + gcloud gemini code-tools-settings delete - delete codeToolsSettings + +SYNOPSIS + gcloud gemini code-tools-settings delete + (CODE_TOOLS_SETTING : --location=LOCATION) [--force] + [--request-id=REQUEST_ID] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Delete a codeToolsSetting + +EXAMPLES + To delete the codeToolsSetting, run: + + $ gcloud gemini code-tools-settings delete + +POSITIONAL ARGUMENTS + CodeToolsSetting resource - Name of the resource 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 code_tools_setting 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. + + CODE_TOOLS_SETTING + ID of the codeToolsSetting or fully qualified identifier for the + codeToolsSetting. + + To set the code_tools_setting attribute: + ▸ provide the argument code_tools_setting on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + The location id of the codeToolsSetting resource. + + To set the location attribute: + ▸ provide the argument code_tools_setting on the command line with + a fully specified name; + ▸ provide the argument --location on the command line. + +FLAGS + --force + If set to true, any code tools settings from this publisher will also + be deleted. (Otherwise, the request will only work if the publisher has + no books.) + + --request-id=REQUEST_ID + An optional request ID to identify requests. Specify a unique request + ID so that if you must retry your request, the server will know to + ignore the request if it has already been completed. The server will + guarantee that for at least 60 minutes after the first request. + + For example, consider a situation where you make an initial request and + the request times out. If you make the request again with the same + request ID, the server can check if original operation with the same + request ID was received, and if so, will ignore the second request. + This prevents clients from accidentally creating duplicate commitments. + + The request ID must be a valid UUID with the exception that zero UUID + is not supported (00000000-0000-0000-0000-000000000000). + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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 cloudaicompanion/v1 API. The full documentation for + this API can be found at: https://cloud.google.com/gemini diff --git a/gcloud/gemini/code-tools-settings/describe b/gcloud/gemini/code-tools-settings/describe new file mode 100644 index 000000000..62b3ba1b4 --- /dev/null +++ b/gcloud/gemini/code-tools-settings/describe @@ -0,0 +1,58 @@ +NAME + gcloud gemini code-tools-settings describe - describe codeToolsSettings + +SYNOPSIS + gcloud gemini code-tools-settings describe + (CODE_TOOLS_SETTING : --location=LOCATION) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Describe a codeToolsSetting + +EXAMPLES + To describe the codeToolsSetting, run: + + $ gcloud gemini code-tools-settings describe + +POSITIONAL ARGUMENTS + CodeToolsSetting resource - Name of the resource. 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 code_tools_setting 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. + + CODE_TOOLS_SETTING + ID of the codeToolsSetting or fully qualified identifier for the + codeToolsSetting. + + To set the code_tools_setting attribute: + ▸ provide the argument code_tools_setting on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + The location id of the codeToolsSetting resource. + + To set the location attribute: + ▸ provide the argument code_tools_setting 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 cloudaicompanion/v1 API. The full documentation for + this API can be found at: https://cloud.google.com/gemini diff --git a/gcloud/gemini/code-tools-settings/help b/gcloud/gemini/code-tools-settings/help new file mode 100644 index 000000000..b7b157aa8 --- /dev/null +++ b/gcloud/gemini/code-tools-settings/help @@ -0,0 +1,37 @@ +NAME + gcloud gemini code-tools-settings - manage Code Tools Setting resources + +SYNOPSIS + gcloud gemini code-tools-settings GROUP | COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Manage Code Tools Setting resources. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +GROUPS + GROUP is one of the following: + + setting-bindings + Manage Setting Binding resources. + +COMMANDS + COMMAND is one of the following: + + create + Create codeToolsSettings. + + delete + Delete codeToolsSettings. + + describe + Describe codeToolsSettings. + + list + List codeToolsSettings. + + update + Update codeToolsSettings. diff --git a/gcloud/gemini/code-tools-settings/list b/gcloud/gemini/code-tools-settings/list new file mode 100644 index 000000000..3c71cd597 --- /dev/null +++ b/gcloud/gemini/code-tools-settings/list @@ -0,0 +1,78 @@ +NAME + gcloud gemini code-tools-settings list - list codeToolsSettings + +SYNOPSIS + gcloud gemini code-tools-settings list --location=LOCATION + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + List codeToolsSettings + +EXAMPLES + To list all codeToolsSettings, run: + + $ gcloud gemini code-tools-settings list + +REQUIRED FLAGS + Location resource - Parent value for ListCodeToolsSettingsRequest This + represents a Cloud resource. (NOTE) Some attributes are not given + arguments in this group but can be set in other ways. + + To set the project attribute: + ◆ provide the argument --location on the command line with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + --location=LOCATION + ID of the location or fully qualified identifier for the location. + + To set the location attribute: + ▸ provide the argument --location on the command line. + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + + --uri + Print a list of resource URIs instead of the default output, and change + the command output to a list of URIs. If this flag is used with + --format, the formatting is applied on this URI list. To display URIs + alongside other keys instead, use the uri() transform. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the cloudaicompanion/v1 API. The full documentation for + this API can be found at: https://cloud.google.com/gemini diff --git a/gcloud/gemini/code-tools-settings/setting-bindings/create b/gcloud/gemini/code-tools-settings/setting-bindings/create new file mode 100644 index 000000000..d34aca918 --- /dev/null +++ b/gcloud/gemini/code-tools-settings/setting-bindings/create @@ -0,0 +1,128 @@ +NAME + gcloud gemini code-tools-settings setting-bindings create - create + settingBindings + +SYNOPSIS + gcloud gemini code-tools-settings setting-bindings create + (SETTING_BINDING + : --code-tools-setting=CODE_TOOLS_SETTING --location=LOCATION) + --target=TARGET [--async] [--labels=[LABELS,...]] [--product=PRODUCT] + [--request-id=REQUEST_ID] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Create a settingBinding + +EXAMPLES + To create the settingBinding, run: + + $ gcloud gemini code-tools-settings setting-bindings create + +POSITIONAL ARGUMENTS + SettingBinding resource - Identifier. Name of the resource. + Format:projects/{project}/locations/{location}/{settingType}/{setting}/settingBindings/{setting_binding} + 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 setting_binding 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. + + SETTING_BINDING + ID of the settingBinding or fully qualified identifier for the + settingBinding. + + To set the setting_binding attribute: + ▸ provide the argument setting_binding on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --code-tools-setting=CODE_TOOLS_SETTING + The codeToolsSetting id of the settingBinding resource. + + To set the code-tools-setting attribute: + ▸ provide the argument setting_binding on the command line with a + fully specified name; + ▸ provide the argument --code-tools-setting on the command line. + + --location=LOCATION + The location id of the settingBinding resource. + + To set the location attribute: + ▸ provide the argument setting_binding on the command line with a + fully specified name; + ▸ provide the argument --location on the command line. + +REQUIRED FLAGS + --target=TARGET + Target of the binding. + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --labels=[LABELS,...] + Labels as key value pairs. + + KEY + Keys must start with a lowercase character and contain only hyphens + (-), underscores (_), lowercase characters, and numbers. + + VALUE + Values must contain only hyphens (-), underscores (_), lowercase + characters, and numbers. + + Shorthand Example: + + --labels=string=string + + JSON Example: + + --labels='{"string": "string"}' + + File Example: + + --labels=path_to_file.(yaml|json) + + --product=PRODUCT + Product type of the setting binding. PRODUCT must be one of: + + gemini-cloud-assist + Gemini Cloud Assist. + gemini-code-assist + Gemini Code Assist. + gemini-in-bigquery + Gemini in BigQuery. + + --request-id=REQUEST_ID + An optional request ID to identify requests. Specify a unique request + ID so that if you must retry your request, the server will know to + ignore the request if it has already been completed. The server will + guarantee that for at least 60 minutes since the first request. + + For example, consider a situation where you make an initial request and + the request times out. If you make the request again with the same + request ID, the server can check if original operation with the same + request ID was received, and if so, will ignore the second request. + This prevents clients from accidentally creating duplicate commitments. + + The request ID must be a valid UUID with the exception that zero UUID + is not supported (00000000-0000-0000-0000-000000000000). + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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 cloudaicompanion/v1 API. The full documentation for + this API can be found at: https://cloud.google.com/gemini diff --git a/gcloud/gemini/code-tools-settings/setting-bindings/delete b/gcloud/gemini/code-tools-settings/setting-bindings/delete new file mode 100644 index 000000000..e693313ef --- /dev/null +++ b/gcloud/gemini/code-tools-settings/setting-bindings/delete @@ -0,0 +1,89 @@ +NAME + gcloud gemini code-tools-settings setting-bindings delete - delete + settingBindings + +SYNOPSIS + gcloud gemini code-tools-settings setting-bindings delete + (SETTING_BINDING + : --code-tools-setting=CODE_TOOLS_SETTING --location=LOCATION) + [--async] [--request-id=REQUEST_ID] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Delete a settingBinding + +EXAMPLES + To delete the settingBinding, run: + + $ gcloud gemini code-tools-settings setting-bindings delete + +POSITIONAL ARGUMENTS + SettingBinding resource - Name of the resource. 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 setting_binding 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. + + SETTING_BINDING + ID of the settingBinding or fully qualified identifier for the + settingBinding. + + To set the setting_binding attribute: + ▸ provide the argument setting_binding on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --code-tools-setting=CODE_TOOLS_SETTING + The codeToolsSetting id of the settingBinding resource. + + To set the code-tools-setting attribute: + ▸ provide the argument setting_binding on the command line with a + fully specified name; + ▸ provide the argument --code-tools-setting on the command line. + + --location=LOCATION + The location id of the settingBinding resource. + + To set the location attribute: + ▸ provide the argument setting_binding 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. + + --request-id=REQUEST_ID + An optional request ID to identify requests. Specify a unique request + ID so that if you must retry your request, the server will know to + ignore the request if it has already been completed. The server will + guarantee that for at least 60 minutes after the first request. + + For example, consider a situation where you make an initial request and + the request times out. If you make the request again with the same + request ID, the server can check if original operation with the same + request ID was received, and if so, will ignore the second request. + This prevents clients from accidentally creating duplicate commitments. + + The request ID must be a valid UUID with the exception that zero UUID + is not supported (00000000-0000-0000-0000-000000000000). + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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 cloudaicompanion/v1 API. The full documentation for + this API can be found at: https://cloud.google.com/gemini diff --git a/gcloud/gemini/code-tools-settings/setting-bindings/describe b/gcloud/gemini/code-tools-settings/setting-bindings/describe new file mode 100644 index 000000000..ad59ba318 --- /dev/null +++ b/gcloud/gemini/code-tools-settings/setting-bindings/describe @@ -0,0 +1,69 @@ +NAME + gcloud gemini code-tools-settings setting-bindings describe - describe + settingBindings + +SYNOPSIS + gcloud gemini code-tools-settings setting-bindings describe + (SETTING_BINDING + : --code-tools-setting=CODE_TOOLS_SETTING --location=LOCATION) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Describe a settingBinding + +EXAMPLES + To describe the settingBinding, run: + + $ gcloud gemini code-tools-settings setting-bindings describe + +POSITIONAL ARGUMENTS + SettingBinding resource - Name of the resource. 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 setting_binding 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. + + SETTING_BINDING + ID of the settingBinding or fully qualified identifier for the + settingBinding. + + To set the setting_binding attribute: + ▸ provide the argument setting_binding on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --code-tools-setting=CODE_TOOLS_SETTING + The codeToolsSetting id of the settingBinding resource. + + To set the code-tools-setting attribute: + ▸ provide the argument setting_binding on the command line with a + fully specified name; + ▸ provide the argument --code-tools-setting on the command line. + + --location=LOCATION + The location id of the settingBinding resource. + + To set the location attribute: + ▸ provide the argument setting_binding 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 cloudaicompanion/v1 API. The full documentation for + this API can be found at: https://cloud.google.com/gemini diff --git a/gcloud/gemini/code-tools-settings/setting-bindings/help b/gcloud/gemini/code-tools-settings/setting-bindings/help new file mode 100644 index 000000000..c71079a35 --- /dev/null +++ b/gcloud/gemini/code-tools-settings/setting-bindings/help @@ -0,0 +1,33 @@ +NAME + gcloud gemini code-tools-settings setting-bindings - manage Setting Binding + resources + +SYNOPSIS + gcloud gemini code-tools-settings setting-bindings COMMAND + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Manage Setting Binding resources. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + create + Create settingBindings. + + delete + Delete settingBindings. + + describe + Describe settingBindings. + + list + List settingBindings. + + update + Update settingBindings. diff --git a/gcloud/gemini/code-tools-settings/setting-bindings/list b/gcloud/gemini/code-tools-settings/setting-bindings/list new file mode 100644 index 000000000..003978d53 --- /dev/null +++ b/gcloud/gemini/code-tools-settings/setting-bindings/list @@ -0,0 +1,93 @@ +NAME + gcloud gemini code-tools-settings setting-bindings list - list + settingBindings + +SYNOPSIS + gcloud gemini code-tools-settings setting-bindings list + (--code-tools-setting=CODE_TOOLS_SETTING : --location=LOCATION) + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + List settingBindings + +EXAMPLES + To list all settingBindings, run: + + $ gcloud gemini code-tools-settings setting-bindings list + +REQUIRED FLAGS + CodeToolsSetting resource - Parent value for ListSettingBindingsRequest. + 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 --code-tools-setting 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. + + --code-tools-setting=CODE_TOOLS_SETTING + ID of the codeToolsSetting or fully qualified identifier for the + codeToolsSetting. + + To set the code-tools-setting attribute: + ▸ provide the argument --code-tools-setting on the command line. + + This flag argument must be specified if any of the other arguments in + this group are specified. + + --location=LOCATION + The location id of the codeToolsSetting resource. + + To set the location attribute: + ▸ provide the argument --code-tools-setting on the command line + with a fully specified name; + ▸ provide the argument --location on the command line. + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + + --uri + Print a list of resource URIs instead of the default output, and change + the command output to a list of URIs. If this flag is used with + --format, the formatting is applied on this URI list. To display URIs + alongside other keys instead, use the uri() transform. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the cloudaicompanion/v1 API. The full documentation for + this API can be found at: https://cloud.google.com/gemini diff --git a/gcloud/gemini/code-tools-settings/setting-bindings/update b/gcloud/gemini/code-tools-settings/setting-bindings/update new file mode 100644 index 000000000..ba6e78b7b --- /dev/null +++ b/gcloud/gemini/code-tools-settings/setting-bindings/update @@ -0,0 +1,165 @@ +NAME + gcloud gemini code-tools-settings setting-bindings update - update + settingBindings + +SYNOPSIS + gcloud gemini code-tools-settings setting-bindings update + (SETTING_BINDING + : --code-tools-setting=CODE_TOOLS_SETTING --location=LOCATION) + [--async] [--product=PRODUCT] [--request-id=REQUEST_ID] + [--target=TARGET] + [--labels=[LABELS,...] + | --update-labels=[UPDATE_LABELS,...] --clear-labels + | --remove-labels=[__REMOVE_LABELS,...]] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Update a settingBinding + +EXAMPLES + To update the settingBinding, run: + + $ gcloud gemini code-tools-settings setting-bindings update + +POSITIONAL ARGUMENTS + SettingBinding resource - Identifier. Name of the resource. + Format:projects/{project}/locations/{location}/{settingType}/{setting}/settingBindings/{setting_binding} + 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 setting_binding 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. + + SETTING_BINDING + ID of the settingBinding or fully qualified identifier for the + settingBinding. + + To set the setting_binding attribute: + ▸ provide the argument setting_binding on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --code-tools-setting=CODE_TOOLS_SETTING + The codeToolsSetting id of the settingBinding resource. + + To set the code-tools-setting attribute: + ▸ provide the argument setting_binding on the command line with a + fully specified name; + ▸ provide the argument --code-tools-setting on the command line. + + --location=LOCATION + The location id of the settingBinding resource. + + To set the location attribute: + ▸ provide the argument setting_binding 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. + + --product=PRODUCT + Product type of the setting binding. PRODUCT must be one of: + + gemini-cloud-assist + Gemini Cloud Assist. + gemini-code-assist + Gemini Code Assist. + gemini-in-bigquery + Gemini in BigQuery. + + --request-id=REQUEST_ID + An optional request ID to identify requests. Specify a unique request + ID so that if you must retry your request, the server will know to + ignore the request if it has already been completed. The server will + guarantee that for at least 60 minutes since the first request. + + For example, consider a situation where you make an initial request and + the request times out. If you make the request again with the same + request ID, the server can check if original operation with the same + request ID was received, and if so, will ignore the second request. + This prevents clients from accidentally creating duplicate commitments. + + The request ID must be a valid UUID with the exception that zero UUID + is not supported (00000000-0000-0000-0000-000000000000). + + --target=TARGET + Target of the binding. + + Update labels. + + At most one of these can be specified: + + --labels=[LABELS,...] + Set labels to new value. Labels as key value pairs. + + KEY + Keys must start with a lowercase character and contain only + hyphens (-), underscores (_), lowercase characters, and numbers. + + VALUE + Values must contain only hyphens (-), underscores (_), lowercase + characters, and numbers. + + Shorthand Example: + + --labels=string=string + + JSON Example: + + --labels='{"string": "string"}' + + File Example: + + --labels=path_to_file.(yaml|json) + + --update-labels=[UPDATE_LABELS,...] + Update labels value or add key value pair. Labels as key value pairs. + + KEY + Keys must start with a lowercase character and contain only + hyphens (-), underscores (_), lowercase characters, and numbers. + + VALUE + Values must contain only hyphens (-), underscores (_), lowercase + characters, and numbers. + + Shorthand Example: + + --update-labels=string=string + + JSON Example: + + --update-labels='{"string": "string"}' + + File Example: + + --update-labels=path_to_file.(yaml|json) + + At most one of these can be specified: + + --clear-labels + Clear labels value and set to empty map. + + --remove-labels=[__REMOVE_LABELS,...] + Remove existing value from map labels. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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 cloudaicompanion/v1 API. The full documentation for + this API can be found at: https://cloud.google.com/gemini diff --git a/gcloud/gemini/code-tools-settings/update b/gcloud/gemini/code-tools-settings/update new file mode 100644 index 000000000..693f26af6 --- /dev/null +++ b/gcloud/gemini/code-tools-settings/update @@ -0,0 +1,270 @@ +NAME + gcloud gemini code-tools-settings update - update codeToolsSettings + +SYNOPSIS + gcloud gemini code-tools-settings update + (CODE_TOOLS_SETTING : --location=LOCATION) [--request-id=REQUEST_ID] + [--enabled-tool=[accountConnector=ACCOUNTCONNECTOR], + [config=CONFIG],[handle=HANDLE],[tool=TOOL],[uriOverride=URIOVERRIDE] + | --add-enabled-tool=[accountConnector=ACCOUNTCONNECTOR], + [config=CONFIG],[handle=HANDLE],[tool=TOOL],[uriOverride=URIOVERRIDE] + --clear-enabled-tool + | --remove-enabled-tool=[accountConnector=ACCOUNTCONNECTOR], + [config=CONFIG], + [handle=HANDLE],[tool=TOOL],[uriOverride=URIOVERRIDE]] + [--labels=[LABELS,...] + | --update-labels=[UPDATE_LABELS,...] --clear-labels + | --remove-labels=[__REMOVE_LABELS,...]] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Update a codeToolsSetting + +EXAMPLES + To update the codeToolsSetting, run: + + $ gcloud gemini code-tools-settings update + +POSITIONAL ARGUMENTS + CodeToolsSetting resource - Identifier. Name of the resource. + Format:projects/{project}/locations/{location}/codeToolsSettings/{codeToolsSetting} + 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 code_tools_setting 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. + + CODE_TOOLS_SETTING + ID of the codeToolsSetting or fully qualified identifier for the + codeToolsSetting. + + To set the code_tools_setting attribute: + ▸ provide the argument code_tools_setting on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + The location id of the codeToolsSetting resource. + + To set the location attribute: + ▸ provide the argument code_tools_setting on the command line with + a fully specified name; + ▸ provide the argument --location on the command line. + +FLAGS + --request-id=REQUEST_ID + An optional request ID to identify requests. Specify a unique request + ID so that if you must retry your request, the server will know to + ignore the request if it has already been completed. The server will + guarantee that for at least 60 minutes since the first request. + + For example, consider a situation where you make an initial request and + the request times out. If you make the request again with the same + request ID, the server can check if original operation with the same + request ID was received, and if so, will ignore the second request. + This prevents clients from accidentally creating duplicate commitments. + + The request ID must be a valid UUID with the exception that zero UUID + is not supported (00000000-0000-0000-0000-000000000000). + + Update enabled_tool. + + At most one of these can be specified: + + --enabled-tool=[accountConnector=ACCOUNTCONNECTOR],[config=CONFIG],[handle=HANDLE],[tool=TOOL],[uriOverride=URIOVERRIDE] + Set enabled_tool to new value. Represents the full set of enabled + tools. + + accountConnector + Link to the Dev Connect Account Connector that holds the user + credentials. + projects/{project}/locations/{location}/accountConnectors/{account_connector_id}. + + config + Configuration parameters for the tool. + + key + Key of the configuration item. + + value + Value of the configuration item. + + handle + Handle used to invoke the tool. + + tool + Link to the Tool. + + uriOverride + Overridden URI, if allowed by Tool. + + Shorthand Example: + + --enabled-tool=accountConnector=string,config=[{key=string,value=string}],handle=string,tool=string,uriOverride=string --enabled-tool=accountConnector=string,config=[{key=string,value=string}],handle=string,tool=string,uriOverride=string + + JSON Example: + + --enabled-tool='[{"accountConnector": "string", "config": [{"key": "string", "value": "string"}], "handle": "string", "tool": "string", "uriOverride": "string"}]' + + File Example: + + --enabled-tool=path_to_file.(yaml|json) + + --add-enabled-tool=[accountConnector=ACCOUNTCONNECTOR],[config=CONFIG],[handle=HANDLE],[tool=TOOL],[uriOverride=URIOVERRIDE] + Add new value to enabled_tool list. Represents the full set of + enabled tools. + + accountConnector + Link to the Dev Connect Account Connector that holds the user + credentials. + projects/{project}/locations/{location}/accountConnectors/{account_connector_id}. + + config + Configuration parameters for the tool. + + key + Key of the configuration item. + + value + Value of the configuration item. + + handle + Handle used to invoke the tool. + + tool + Link to the Tool. + + uriOverride + Overridden URI, if allowed by Tool. + + Shorthand Example: + + --add-enabled-tool=accountConnector=string,config=[{key=string,value=string}],handle=string,tool=string,uriOverride=string --add-enabled-tool=accountConnector=string,config=[{key=string,value=string}],handle=string,tool=string,uriOverride=string + + JSON Example: + + --add-enabled-tool='[{"accountConnector": "string", "config": [{"key": "string", "value": "string"}], "handle": "string", "tool": "string", "uriOverride": "string"}]' + + File Example: + + --add-enabled-tool=path_to_file.(yaml|json) + + At most one of these can be specified: + + --clear-enabled-tool + Clear enabled_tool value and set to empty list. + + --remove-enabled-tool=[accountConnector=ACCOUNTCONNECTOR],[config=CONFIG],[handle=HANDLE],[tool=TOOL],[uriOverride=URIOVERRIDE] + Remove existing value from enabled_tool list. Represents the full + set of enabled tools. + + accountConnector + Link to the Dev Connect Account Connector that holds the user + credentials. + projects/{project}/locations/{location}/accountConnectors/{account_connector_id}. + + config + Configuration parameters for the tool. + + key + Key of the configuration item. + + value + Value of the configuration item. + + handle + Handle used to invoke the tool. + + tool + Link to the Tool. + + uriOverride + Overridden URI, if allowed by Tool. + + Shorthand Example: + + --remove-enabled-tool=accountConnector=string,config=[{key=string,value=string}],handle=string,tool=string,uriOverride=string --remove-enabled-tool=accountConnector=string,config=[{key=string,value=string}],handle=string,tool=string,uriOverride=string + + JSON Example: + + --remove-enabled-tool='[{"accountConnector": "string", "config": [{"key": "string", "value": "string"}], "handle": "string", "tool": "string", "uriOverride": "string"}]' + + File Example: + + --remove-enabled-tool=path_to_file.(yaml|json) + + Update labels. + + At most one of these can be specified: + + --labels=[LABELS,...] + Set labels to new value. Labels as key value pairs. + + KEY + Keys must start with a lowercase character and contain only + hyphens (-), underscores (_), lowercase characters, and numbers. + + VALUE + Values must contain only hyphens (-), underscores (_), lowercase + characters, and numbers. + + Shorthand Example: + + --labels=string=string + + JSON Example: + + --labels='{"string": "string"}' + + File Example: + + --labels=path_to_file.(yaml|json) + + --update-labels=[UPDATE_LABELS,...] + Update labels value or add key value pair. Labels as key value pairs. + + KEY + Keys must start with a lowercase character and contain only + hyphens (-), underscores (_), lowercase characters, and numbers. + + VALUE + Values must contain only hyphens (-), underscores (_), lowercase + characters, and numbers. + + Shorthand Example: + + --update-labels=string=string + + JSON Example: + + --update-labels='{"string": "string"}' + + File Example: + + --update-labels=path_to_file.(yaml|json) + + At most one of these can be specified: + + --clear-labels + Clear labels value and set to empty map. + + --remove-labels=[__REMOVE_LABELS,...] + Remove existing value from map labels. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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 cloudaicompanion/v1 API. The full documentation for + this API can be found at: https://cloud.google.com/gemini diff --git a/gcloud/gemini/data-sharing-with-google-settings/create b/gcloud/gemini/data-sharing-with-google-settings/create new file mode 100644 index 000000000..b351e39a4 --- /dev/null +++ b/gcloud/gemini/data-sharing-with-google-settings/create @@ -0,0 +1,105 @@ +NAME + gcloud gemini data-sharing-with-google-settings create - create + dataSharingWithGoogleSettings + +SYNOPSIS + gcloud gemini data-sharing-with-google-settings create + (DATA_SHARING_WITH_GOOGLE_SETTING : --location=LOCATION) + [--enable-preview-data-sharing] [--labels=[LABELS,...]] + [--request-id=REQUEST_ID] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Create a dataSharingWithGoogleSetting + +EXAMPLES + To create the dataSharingWithGoogleSetting, run: + + $ gcloud gemini data-sharing-with-google-settings create + +POSITIONAL ARGUMENTS + DataSharingWithGoogleSetting resource - Identifier. Name of the resource. + Format:projects/{project}/locations/{location}/dataSharingWithGoogleSettings/{dataSharingWithGoogleSetting} + 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 data_sharing_with_google_setting 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. + + DATA_SHARING_WITH_GOOGLE_SETTING + ID of the dataSharingWithGoogleSetting or fully qualified identifier + for the dataSharingWithGoogleSetting. + + To set the data_sharing_with_google_setting attribute: + ▸ provide the argument data_sharing_with_google_setting on the + command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + The location id of the dataSharingWithGoogleSetting resource. + + To set the location attribute: + ▸ provide the argument data_sharing_with_google_setting on the + command line with a fully specified name; + ▸ provide the argument --location on the command line. + +FLAGS + --enable-preview-data-sharing + Whether preview data sharing should be enabled. + + --labels=[LABELS,...] + Labels as key value pairs. + + KEY + Keys must start with a lowercase character and contain only hyphens + (-), underscores (_), lowercase characters, and numbers. + + VALUE + Values must contain only hyphens (-), underscores (_), lowercase + characters, and numbers. + + Shorthand Example: + + --labels=string=string + + JSON Example: + + --labels='{"string": "string"}' + + File Example: + + --labels=path_to_file.(yaml|json) + + --request-id=REQUEST_ID + An optional request ID to identify requests. Specify a unique request + ID so that if you must retry your request, the server will know to + ignore the request if it has already been completed. The server will + guarantee that for at least 60 minutes since the first request. + + For example, consider a situation where you make an initial request and + the request times out. If you make the request again with the same + request ID, the server can check if original operation with the same + request ID was received, and if so, will ignore the second request. + This prevents clients from accidentally creating duplicate commitments. + + The request ID must be a valid UUID with the exception that zero UUID + is not supported (00000000-0000-0000-0000-000000000000). + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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 cloudaicompanion/v1 API. The full documentation for + this API can be found at: https://cloud.google.com/gemini diff --git a/gcloud/gemini/data-sharing-with-google-settings/delete b/gcloud/gemini/data-sharing-with-google-settings/delete new file mode 100644 index 000000000..65876fdc4 --- /dev/null +++ b/gcloud/gemini/data-sharing-with-google-settings/delete @@ -0,0 +1,77 @@ +NAME + gcloud gemini data-sharing-with-google-settings delete - delete + dataSharingWithGoogleSettings + +SYNOPSIS + gcloud gemini data-sharing-with-google-settings delete + (DATA_SHARING_WITH_GOOGLE_SETTING : --location=LOCATION) + [--request-id=REQUEST_ID] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Delete a dataSharingWithGoogleSetting + +EXAMPLES + To delete the dataSharingWithGoogleSetting, run: + + $ gcloud gemini data-sharing-with-google-settings delete + +POSITIONAL ARGUMENTS + DataSharingWithGoogleSetting resource - Name of the resource 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 data_sharing_with_google_setting 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. + + DATA_SHARING_WITH_GOOGLE_SETTING + ID of the dataSharingWithGoogleSetting or fully qualified identifier + for the dataSharingWithGoogleSetting. + + To set the data_sharing_with_google_setting attribute: + ▸ provide the argument data_sharing_with_google_setting on the + command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + The location id of the dataSharingWithGoogleSetting resource. + + To set the location attribute: + ▸ provide the argument data_sharing_with_google_setting on the + command line with a fully specified name; + ▸ provide the argument --location on the command line. + +FLAGS + --request-id=REQUEST_ID + An optional request ID to identify requests. Specify a unique request + ID so that if you must retry your request, the server will know to + ignore the request if it has already been completed. The server will + guarantee that for at least 60 minutes after the first request. + + For example, consider a situation where you make an initial request and + the request times out. If you make the request again with the same + request ID, the server can check if original operation with the same + request ID was received, and if so, will ignore the second request. + This prevents clients from accidentally creating duplicate commitments. + + The request ID must be a valid UUID with the exception that zero UUID + is not supported (00000000-0000-0000-0000-000000000000). + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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 cloudaicompanion/v1 API. The full documentation for + this API can be found at: https://cloud.google.com/gemini diff --git a/gcloud/gemini/data-sharing-with-google-settings/describe b/gcloud/gemini/data-sharing-with-google-settings/describe new file mode 100644 index 000000000..f7a550c68 --- /dev/null +++ b/gcloud/gemini/data-sharing-with-google-settings/describe @@ -0,0 +1,61 @@ +NAME + gcloud gemini data-sharing-with-google-settings describe - describe + dataSharingWithGoogleSettings + +SYNOPSIS + gcloud gemini data-sharing-with-google-settings describe + (DATA_SHARING_WITH_GOOGLE_SETTING : --location=LOCATION) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Describe a dataSharingWithGoogleSetting + +EXAMPLES + To describe the dataSharingWithGoogleSetting, run: + + $ gcloud gemini data-sharing-with-google-settings describe + +POSITIONAL ARGUMENTS + DataSharingWithGoogleSetting resource - Name of the resource. 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 data_sharing_with_google_setting 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. + + DATA_SHARING_WITH_GOOGLE_SETTING + ID of the dataSharingWithGoogleSetting or fully qualified identifier + for the dataSharingWithGoogleSetting. + + To set the data_sharing_with_google_setting attribute: + ▸ provide the argument data_sharing_with_google_setting on the + command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + The location id of the dataSharingWithGoogleSetting resource. + + To set the location attribute: + ▸ provide the argument data_sharing_with_google_setting 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 cloudaicompanion/v1 API. The full documentation for + this API can be found at: https://cloud.google.com/gemini diff --git a/gcloud/gemini/data-sharing-with-google-settings/help b/gcloud/gemini/data-sharing-with-google-settings/help new file mode 100644 index 000000000..d80cc369f --- /dev/null +++ b/gcloud/gemini/data-sharing-with-google-settings/help @@ -0,0 +1,39 @@ +NAME + gcloud gemini data-sharing-with-google-settings - manage Data Sharing With + Google Setting resources + +SYNOPSIS + gcloud gemini data-sharing-with-google-settings GROUP | COMMAND + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Manage Data Sharing With Google Setting resources. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +GROUPS + GROUP is one of the following: + + setting-bindings + Manage Setting Binding resources. + +COMMANDS + COMMAND is one of the following: + + create + Create dataSharingWithGoogleSettings. + + delete + Delete dataSharingWithGoogleSettings. + + describe + Describe dataSharingWithGoogleSettings. + + list + List dataSharingWithGoogleSettings. + + update + Update dataSharingWithGoogleSettings. diff --git a/gcloud/gemini/data-sharing-with-google-settings/list b/gcloud/gemini/data-sharing-with-google-settings/list new file mode 100644 index 000000000..504b83fba --- /dev/null +++ b/gcloud/gemini/data-sharing-with-google-settings/list @@ -0,0 +1,80 @@ +NAME + gcloud gemini data-sharing-with-google-settings list - list + dataSharingWithGoogleSettings + +SYNOPSIS + gcloud gemini data-sharing-with-google-settings list --location=LOCATION + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + List dataSharingWithGoogleSettings + +EXAMPLES + To list all dataSharingWithGoogleSettings, run: + + $ gcloud gemini data-sharing-with-google-settings list + +REQUIRED FLAGS + Location resource - Parent value for + ListDataSharingWithGoogleSettingsRequest This represents a Cloud resource. + (NOTE) Some attributes are not given arguments in this group but can be + set in other ways. + + To set the project attribute: + ◆ provide the argument --location on the command line with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + --location=LOCATION + ID of the location or fully qualified identifier for the location. + + To set the location attribute: + ▸ provide the argument --location on the command line. + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + + --uri + Print a list of resource URIs instead of the default output, and change + the command output to a list of URIs. If this flag is used with + --format, the formatting is applied on this URI list. To display URIs + alongside other keys instead, use the uri() transform. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the cloudaicompanion/v1 API. The full documentation for + this API can be found at: https://cloud.google.com/gemini diff --git a/gcloud/gemini/data-sharing-with-google-settings/setting-bindings/create b/gcloud/gemini/data-sharing-with-google-settings/setting-bindings/create new file mode 100644 index 000000000..db9c94f50 --- /dev/null +++ b/gcloud/gemini/data-sharing-with-google-settings/setting-bindings/create @@ -0,0 +1,130 @@ +NAME + gcloud gemini data-sharing-with-google-settings setting-bindings create - + create settingBindings + +SYNOPSIS + gcloud gemini data-sharing-with-google-settings setting-bindings create + (SETTING_BINDING + : --data-sharing-with-google-setting=DATA_SHARING_WITH_GOOGLE_SETTING + --location=LOCATION) --target=TARGET [--async] + [--labels=[LABELS,...]] [--product=PRODUCT] [--request-id=REQUEST_ID] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Create a settingBinding + +EXAMPLES + To create the settingBinding, run: + + $ gcloud gemini data-sharing-with-google-settings setting-bindings \ create + +POSITIONAL ARGUMENTS + SettingBinding resource - Identifier. Name of the resource. + Format:projects/{project}/locations/{location}/{settingType}/{setting}/settingBindings/{setting_binding} + 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 setting_binding 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. + + SETTING_BINDING + ID of the settingBinding or fully qualified identifier for the + settingBinding. + + To set the setting_binding attribute: + ▸ provide the argument setting_binding on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --data-sharing-with-google-setting=DATA_SHARING_WITH_GOOGLE_SETTING + The dataSharingWithGoogleSetting id of the settingBinding resource. + + To set the data-sharing-with-google-setting attribute: + ▸ provide the argument setting_binding on the command line with a + fully specified name; + ▸ provide the argument --data-sharing-with-google-setting on the + command line. + + --location=LOCATION + The location id of the settingBinding resource. + + To set the location attribute: + ▸ provide the argument setting_binding on the command line with a + fully specified name; + ▸ provide the argument --location on the command line. + +REQUIRED FLAGS + --target=TARGET + Target of the binding. + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --labels=[LABELS,...] + Labels as key value pairs. + + KEY + Keys must start with a lowercase character and contain only hyphens + (-), underscores (_), lowercase characters, and numbers. + + VALUE + Values must contain only hyphens (-), underscores (_), lowercase + characters, and numbers. + + Shorthand Example: + + --labels=string=string + + JSON Example: + + --labels='{"string": "string"}' + + File Example: + + --labels=path_to_file.(yaml|json) + + --product=PRODUCT + Product type of the setting binding. PRODUCT must be one of: + + gemini-cloud-assist + Gemini Cloud Assist. + gemini-code-assist + Gemini Code Assist. + gemini-in-bigquery + Gemini in BigQuery. + + --request-id=REQUEST_ID + An optional request ID to identify requests. Specify a unique request + ID so that if you must retry your request, the server will know to + ignore the request if it has already been completed. The server will + guarantee that for at least 60 minutes since the first request. + + For example, consider a situation where you make an initial request and + the request times out. If you make the request again with the same + request ID, the server can check if original operation with the same + request ID was received, and if so, will ignore the second request. + This prevents clients from accidentally creating duplicate commitments. + + The request ID must be a valid UUID with the exception that zero UUID + is not supported (00000000-0000-0000-0000-000000000000). + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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 cloudaicompanion/v1 API. The full documentation for + this API can be found at: https://cloud.google.com/gemini diff --git a/gcloud/gemini/data-sharing-with-google-settings/setting-bindings/delete b/gcloud/gemini/data-sharing-with-google-settings/setting-bindings/delete new file mode 100644 index 000000000..695927b16 --- /dev/null +++ b/gcloud/gemini/data-sharing-with-google-settings/setting-bindings/delete @@ -0,0 +1,91 @@ +NAME + gcloud gemini data-sharing-with-google-settings setting-bindings delete - + delete settingBindings + +SYNOPSIS + gcloud gemini data-sharing-with-google-settings setting-bindings delete + (SETTING_BINDING + : --data-sharing-with-google-setting=DATA_SHARING_WITH_GOOGLE_SETTING + --location=LOCATION) [--async] [--request-id=REQUEST_ID] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Delete a settingBinding + +EXAMPLES + To delete the settingBinding, run: + + $ gcloud gemini data-sharing-with-google-settings setting-bindings \ delete + +POSITIONAL ARGUMENTS + SettingBinding resource - Name of the resource. 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 setting_binding 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. + + SETTING_BINDING + ID of the settingBinding or fully qualified identifier for the + settingBinding. + + To set the setting_binding attribute: + ▸ provide the argument setting_binding on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --data-sharing-with-google-setting=DATA_SHARING_WITH_GOOGLE_SETTING + The dataSharingWithGoogleSetting id of the settingBinding resource. + + To set the data-sharing-with-google-setting attribute: + ▸ provide the argument setting_binding on the command line with a + fully specified name; + ▸ provide the argument --data-sharing-with-google-setting on the + command line. + + --location=LOCATION + The location id of the settingBinding resource. + + To set the location attribute: + ▸ provide the argument setting_binding 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. + + --request-id=REQUEST_ID + An optional request ID to identify requests. Specify a unique request + ID so that if you must retry your request, the server will know to + ignore the request if it has already been completed. The server will + guarantee that for at least 60 minutes after the first request. + + For example, consider a situation where you make an initial request and + the request times out. If you make the request again with the same + request ID, the server can check if original operation with the same + request ID was received, and if so, will ignore the second request. + This prevents clients from accidentally creating duplicate commitments. + + The request ID must be a valid UUID with the exception that zero UUID + is not supported (00000000-0000-0000-0000-000000000000). + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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 cloudaicompanion/v1 API. The full documentation for + this API can be found at: https://cloud.google.com/gemini diff --git a/gcloud/gemini/data-sharing-with-google-settings/setting-bindings/describe b/gcloud/gemini/data-sharing-with-google-settings/setting-bindings/describe new file mode 100644 index 000000000..22cfd40b6 --- /dev/null +++ b/gcloud/gemini/data-sharing-with-google-settings/setting-bindings/describe @@ -0,0 +1,70 @@ +NAME + gcloud gemini data-sharing-with-google-settings setting-bindings describe - + describe settingBindings + +SYNOPSIS + gcloud gemini data-sharing-with-google-settings setting-bindings describe + (SETTING_BINDING + : --data-sharing-with-google-setting=DATA_SHARING_WITH_GOOGLE_SETTING + --location=LOCATION) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Describe a settingBinding + +EXAMPLES + To describe the settingBinding, run: + + $ gcloud gemini data-sharing-with-google-settings setting-bindings \ describe + +POSITIONAL ARGUMENTS + SettingBinding resource - Name of the resource. 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 setting_binding 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. + + SETTING_BINDING + ID of the settingBinding or fully qualified identifier for the + settingBinding. + + To set the setting_binding attribute: + ▸ provide the argument setting_binding on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --data-sharing-with-google-setting=DATA_SHARING_WITH_GOOGLE_SETTING + The dataSharingWithGoogleSetting id of the settingBinding resource. + + To set the data-sharing-with-google-setting attribute: + ▸ provide the argument setting_binding on the command line with a + fully specified name; + ▸ provide the argument --data-sharing-with-google-setting on the + command line. + + --location=LOCATION + The location id of the settingBinding resource. + + To set the location attribute: + ▸ provide the argument setting_binding 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 cloudaicompanion/v1 API. The full documentation for + this API can be found at: https://cloud.google.com/gemini diff --git a/gcloud/gemini/data-sharing-with-google-settings/setting-bindings/help b/gcloud/gemini/data-sharing-with-google-settings/setting-bindings/help new file mode 100644 index 000000000..685a7d2d2 --- /dev/null +++ b/gcloud/gemini/data-sharing-with-google-settings/setting-bindings/help @@ -0,0 +1,33 @@ +NAME + gcloud gemini data-sharing-with-google-settings setting-bindings - manage + Setting Binding resources + +SYNOPSIS + gcloud gemini data-sharing-with-google-settings setting-bindings COMMAND + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Manage Setting Binding resources. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + create + Create settingBindings. + + delete + Delete settingBindings. + + describe + Describe settingBindings. + + list + List settingBindings. + + update + Update settingBindings. diff --git a/gcloud/gemini/data-sharing-with-google-settings/setting-bindings/list b/gcloud/gemini/data-sharing-with-google-settings/setting-bindings/list new file mode 100644 index 000000000..1f9254f1a --- /dev/null +++ b/gcloud/gemini/data-sharing-with-google-settings/setting-bindings/list @@ -0,0 +1,95 @@ +NAME + gcloud gemini data-sharing-with-google-settings setting-bindings list - + list settingBindings + +SYNOPSIS + gcloud gemini data-sharing-with-google-settings setting-bindings list + (--data-sharing-with-google-setting=DATA_SHARING_WITH_GOOGLE_SETTING + : --location=LOCATION) [--filter=EXPRESSION] [--limit=LIMIT] + [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + List settingBindings + +EXAMPLES + To list all settingBindings, run: + + $ gcloud gemini data-sharing-with-google-settings setting-bindings \ list + +REQUIRED FLAGS + DataSharingWithGoogleSetting resource - Parent value for + ListSettingBindingsRequest. 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 --data-sharing-with-google-setting 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. + + --data-sharing-with-google-setting=DATA_SHARING_WITH_GOOGLE_SETTING + ID of the dataSharingWithGoogleSetting or fully qualified identifier + for the dataSharingWithGoogleSetting. + + To set the data-sharing-with-google-setting attribute: + ▸ provide the argument --data-sharing-with-google-setting on the + command line. + + This flag argument must be specified if any of the other arguments in + this group are specified. + + --location=LOCATION + The location id of the dataSharingWithGoogleSetting resource. + + To set the location attribute: + ▸ provide the argument --data-sharing-with-google-setting on the + command line with a fully specified name; + ▸ provide the argument --location on the command line. + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + + --uri + Print a list of resource URIs instead of the default output, and change + the command output to a list of URIs. If this flag is used with + --format, the formatting is applied on this URI list. To display URIs + alongside other keys instead, use the uri() transform. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the cloudaicompanion/v1 API. The full documentation for + this API can be found at: https://cloud.google.com/gemini diff --git a/gcloud/gemini/data-sharing-with-google-settings/setting-bindings/update b/gcloud/gemini/data-sharing-with-google-settings/setting-bindings/update new file mode 100644 index 000000000..0f9f4b6db --- /dev/null +++ b/gcloud/gemini/data-sharing-with-google-settings/setting-bindings/update @@ -0,0 +1,166 @@ +NAME + gcloud gemini data-sharing-with-google-settings setting-bindings update - + update settingBindings + +SYNOPSIS + gcloud gemini data-sharing-with-google-settings setting-bindings update + (SETTING_BINDING + : --data-sharing-with-google-setting=DATA_SHARING_WITH_GOOGLE_SETTING + --location=LOCATION) [--async] [--product=PRODUCT] + [--request-id=REQUEST_ID] [--target=TARGET] + [--labels=[LABELS,...] + | --update-labels=[UPDATE_LABELS,...] --clear-labels + | --remove-labels=[__REMOVE_LABELS,...]] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Update a settingBinding + +EXAMPLES + To update the settingBinding, run: + + $ gcloud gemini data-sharing-with-google-settings setting-bindings \ update + +POSITIONAL ARGUMENTS + SettingBinding resource - Identifier. Name of the resource. + Format:projects/{project}/locations/{location}/{settingType}/{setting}/settingBindings/{setting_binding} + 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 setting_binding 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. + + SETTING_BINDING + ID of the settingBinding or fully qualified identifier for the + settingBinding. + + To set the setting_binding attribute: + ▸ provide the argument setting_binding on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --data-sharing-with-google-setting=DATA_SHARING_WITH_GOOGLE_SETTING + The dataSharingWithGoogleSetting id of the settingBinding resource. + + To set the data-sharing-with-google-setting attribute: + ▸ provide the argument setting_binding on the command line with a + fully specified name; + ▸ provide the argument --data-sharing-with-google-setting on the + command line. + + --location=LOCATION + The location id of the settingBinding resource. + + To set the location attribute: + ▸ provide the argument setting_binding 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. + + --product=PRODUCT + Product type of the setting binding. PRODUCT must be one of: + + gemini-cloud-assist + Gemini Cloud Assist. + gemini-code-assist + Gemini Code Assist. + gemini-in-bigquery + Gemini in BigQuery. + + --request-id=REQUEST_ID + An optional request ID to identify requests. Specify a unique request + ID so that if you must retry your request, the server will know to + ignore the request if it has already been completed. The server will + guarantee that for at least 60 minutes since the first request. + + For example, consider a situation where you make an initial request and + the request times out. If you make the request again with the same + request ID, the server can check if original operation with the same + request ID was received, and if so, will ignore the second request. + This prevents clients from accidentally creating duplicate commitments. + + The request ID must be a valid UUID with the exception that zero UUID + is not supported (00000000-0000-0000-0000-000000000000). + + --target=TARGET + Target of the binding. + + Update labels. + + At most one of these can be specified: + + --labels=[LABELS,...] + Set labels to new value. Labels as key value pairs. + + KEY + Keys must start with a lowercase character and contain only + hyphens (-), underscores (_), lowercase characters, and numbers. + + VALUE + Values must contain only hyphens (-), underscores (_), lowercase + characters, and numbers. + + Shorthand Example: + + --labels=string=string + + JSON Example: + + --labels='{"string": "string"}' + + File Example: + + --labels=path_to_file.(yaml|json) + + --update-labels=[UPDATE_LABELS,...] + Update labels value or add key value pair. Labels as key value pairs. + + KEY + Keys must start with a lowercase character and contain only + hyphens (-), underscores (_), lowercase characters, and numbers. + + VALUE + Values must contain only hyphens (-), underscores (_), lowercase + characters, and numbers. + + Shorthand Example: + + --update-labels=string=string + + JSON Example: + + --update-labels='{"string": "string"}' + + File Example: + + --update-labels=path_to_file.(yaml|json) + + At most one of these can be specified: + + --clear-labels + Clear labels value and set to empty map. + + --remove-labels=[__REMOVE_LABELS,...] + Remove existing value from map labels. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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 cloudaicompanion/v1 API. The full documentation for + this API can be found at: https://cloud.google.com/gemini diff --git a/gcloud/gemini/data-sharing-with-google-settings/update b/gcloud/gemini/data-sharing-with-google-settings/update new file mode 100644 index 000000000..379dff593 --- /dev/null +++ b/gcloud/gemini/data-sharing-with-google-settings/update @@ -0,0 +1,144 @@ +NAME + gcloud gemini data-sharing-with-google-settings update - update + dataSharingWithGoogleSettings + +SYNOPSIS + gcloud gemini data-sharing-with-google-settings update + (DATA_SHARING_WITH_GOOGLE_SETTING : --location=LOCATION) + [--[no-]enable-preview-data-sharing] [--request-id=REQUEST_ID] + [--labels=[LABELS,...] + | --update-labels=[UPDATE_LABELS,...] --clear-labels + | --remove-labels=[__REMOVE_LABELS,...]] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Update a dataSharingWithGoogleSetting + +EXAMPLES + To update the dataSharingWithGoogleSetting, run: + + $ gcloud gemini data-sharing-with-google-settings update + +POSITIONAL ARGUMENTS + DataSharingWithGoogleSetting resource - Identifier. Name of the resource. + Format:projects/{project}/locations/{location}/dataSharingWithGoogleSettings/{dataSharingWithGoogleSetting} + 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 data_sharing_with_google_setting 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. + + DATA_SHARING_WITH_GOOGLE_SETTING + ID of the dataSharingWithGoogleSetting or fully qualified identifier + for the dataSharingWithGoogleSetting. + + To set the data_sharing_with_google_setting attribute: + ▸ provide the argument data_sharing_with_google_setting on the + command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + The location id of the dataSharingWithGoogleSetting resource. + + To set the location attribute: + ▸ provide the argument data_sharing_with_google_setting on the + command line with a fully specified name; + ▸ provide the argument --location on the command line. + +FLAGS + --[no-]enable-preview-data-sharing + Whether preview data sharing should be enabled. Use + --enable-preview-data-sharing to enable and + --no-enable-preview-data-sharing to disable. + + --request-id=REQUEST_ID + An optional request ID to identify requests. Specify a unique request + ID so that if you must retry your request, the server will know to + ignore the request if it has already been completed. The server will + guarantee that for at least 60 minutes since the first request. + + For example, consider a situation where you make an initial request and + the request times out. If you make the request again with the same + request ID, the server can check if original operation with the same + request ID was received, and if so, will ignore the second request. + This prevents clients from accidentally creating duplicate commitments. + + The request ID must be a valid UUID with the exception that zero UUID + is not supported (00000000-0000-0000-0000-000000000000). + + Update labels. + + At most one of these can be specified: + + --labels=[LABELS,...] + Set labels to new value. Labels as key value pairs. + + KEY + Keys must start with a lowercase character and contain only + hyphens (-), underscores (_), lowercase characters, and numbers. + + VALUE + Values must contain only hyphens (-), underscores (_), lowercase + characters, and numbers. + + Shorthand Example: + + --labels=string=string + + JSON Example: + + --labels='{"string": "string"}' + + File Example: + + --labels=path_to_file.(yaml|json) + + --update-labels=[UPDATE_LABELS,...] + Update labels value or add key value pair. Labels as key value pairs. + + KEY + Keys must start with a lowercase character and contain only + hyphens (-), underscores (_), lowercase characters, and numbers. + + VALUE + Values must contain only hyphens (-), underscores (_), lowercase + characters, and numbers. + + Shorthand Example: + + --update-labels=string=string + + JSON Example: + + --update-labels='{"string": "string"}' + + File Example: + + --update-labels=path_to_file.(yaml|json) + + At most one of these can be specified: + + --clear-labels + Clear labels value and set to empty map. + + --remove-labels=[__REMOVE_LABELS,...] + Remove existing value from map labels. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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 cloudaicompanion/v1 API. The full documentation for + this API can be found at: https://cloud.google.com/gemini diff --git a/gcloud/gemini/gemini-gcp-enablement-settings/create b/gcloud/gemini/gemini-gcp-enablement-settings/create new file mode 100644 index 000000000..a9ef7c4be --- /dev/null +++ b/gcloud/gemini/gemini-gcp-enablement-settings/create @@ -0,0 +1,105 @@ +NAME + gcloud gemini gemini-gcp-enablement-settings create - create + geminiGcpEnablementSettings + +SYNOPSIS + gcloud gemini gemini-gcp-enablement-settings create + (GEMINI_GCP_ENABLEMENT_SETTING : --location=LOCATION) + [--enable-customer-data-sharing] [--labels=[LABELS,...]] + [--request-id=REQUEST_ID] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Create a geminiGcpEnablementSetting + +EXAMPLES + To create the geminiGcpEnablementSetting, run: + + $ gcloud gemini gemini-gcp-enablement-settings create + +POSITIONAL ARGUMENTS + GeminiGcpEnablementSetting resource - Identifier. Name of the resource. + Format:projects/{project}/locations/{location}/geminiGcpEnablementSettings/{geminiGcpEnablementSetting} + 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 gemini_gcp_enablement_setting 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. + + GEMINI_GCP_ENABLEMENT_SETTING + ID of the geminiGcpEnablementSetting or fully qualified identifier + for the geminiGcpEnablementSetting. + + To set the gemini_gcp_enablement_setting attribute: + ▸ provide the argument gemini_gcp_enablement_setting on the command + line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + The location id of the geminiGcpEnablementSetting resource. + + To set the location attribute: + ▸ provide the argument gemini_gcp_enablement_setting on the command + line with a fully specified name; + ▸ provide the argument --location on the command line. + +FLAGS + --enable-customer-data-sharing + Whether customer data sharing should be enabled. + + --labels=[LABELS,...] + Labels as key value pairs. + + KEY + Keys must start with a lowercase character and contain only hyphens + (-), underscores (_), lowercase characters, and numbers. + + VALUE + Values must contain only hyphens (-), underscores (_), lowercase + characters, and numbers. + + Shorthand Example: + + --labels=string=string + + JSON Example: + + --labels='{"string": "string"}' + + File Example: + + --labels=path_to_file.(yaml|json) + + --request-id=REQUEST_ID + An optional request ID to identify requests. Specify a unique request + ID so that if you must retry your request, the server will know to + ignore the request if it has already been completed. The server will + guarantee that for at least 60 minutes since the first request. + + For example, consider a situation where you make an initial request and + the request times out. If you make the request again with the same + request ID, the server can check if original operation with the same + request ID was received, and if so, will ignore the second request. + This prevents clients from accidentally creating duplicate commitments. + + The request ID must be a valid UUID with the exception that zero UUID + is not supported (00000000-0000-0000-0000-000000000000). + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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 cloudaicompanion/v1 API. The full documentation for + this API can be found at: https://cloud.google.com/gemini diff --git a/gcloud/gemini/gemini-gcp-enablement-settings/delete b/gcloud/gemini/gemini-gcp-enablement-settings/delete new file mode 100644 index 000000000..21a3c2af4 --- /dev/null +++ b/gcloud/gemini/gemini-gcp-enablement-settings/delete @@ -0,0 +1,77 @@ +NAME + gcloud gemini gemini-gcp-enablement-settings delete - delete + geminiGcpEnablementSettings + +SYNOPSIS + gcloud gemini gemini-gcp-enablement-settings delete + (GEMINI_GCP_ENABLEMENT_SETTING : --location=LOCATION) + [--request-id=REQUEST_ID] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Delete a geminiGcpEnablementSetting + +EXAMPLES + To delete the geminiGcpEnablementSetting, run: + + $ gcloud gemini gemini-gcp-enablement-settings delete + +POSITIONAL ARGUMENTS + GeminiGcpEnablementSetting resource - Name of the resource 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 gemini_gcp_enablement_setting 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. + + GEMINI_GCP_ENABLEMENT_SETTING + ID of the geminiGcpEnablementSetting or fully qualified identifier + for the geminiGcpEnablementSetting. + + To set the gemini_gcp_enablement_setting attribute: + ▸ provide the argument gemini_gcp_enablement_setting on the command + line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + The location id of the geminiGcpEnablementSetting resource. + + To set the location attribute: + ▸ provide the argument gemini_gcp_enablement_setting on the command + line with a fully specified name; + ▸ provide the argument --location on the command line. + +FLAGS + --request-id=REQUEST_ID + An optional request ID to identify requests. Specify a unique request + ID so that if you must retry your request, the server will know to + ignore the request if it has already been completed. The server will + guarantee that for at least 60 minutes after the first request. + + For example, consider a situation where you make an initial request and + the request times out. If you make the request again with the same + request ID, the server can check if original operation with the same + request ID was received, and if so, will ignore the second request. + This prevents clients from accidentally creating duplicate commitments. + + The request ID must be a valid UUID with the exception that zero UUID + is not supported (00000000-0000-0000-0000-000000000000). + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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 cloudaicompanion/v1 API. The full documentation for + this API can be found at: https://cloud.google.com/gemini diff --git a/gcloud/gemini/gemini-gcp-enablement-settings/describe b/gcloud/gemini/gemini-gcp-enablement-settings/describe new file mode 100644 index 000000000..3e62617b2 --- /dev/null +++ b/gcloud/gemini/gemini-gcp-enablement-settings/describe @@ -0,0 +1,61 @@ +NAME + gcloud gemini gemini-gcp-enablement-settings describe - describe + geminiGcpEnablementSettings + +SYNOPSIS + gcloud gemini gemini-gcp-enablement-settings describe + (GEMINI_GCP_ENABLEMENT_SETTING : --location=LOCATION) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Describe a geminiGcpEnablementSetting + +EXAMPLES + To describe the geminiGcpEnablementSetting, run: + + $ gcloud gemini gemini-gcp-enablement-settings describe + +POSITIONAL ARGUMENTS + GeminiGcpEnablementSetting resource - Name of the resource. 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 gemini_gcp_enablement_setting 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. + + GEMINI_GCP_ENABLEMENT_SETTING + ID of the geminiGcpEnablementSetting or fully qualified identifier + for the geminiGcpEnablementSetting. + + To set the gemini_gcp_enablement_setting attribute: + ▸ provide the argument gemini_gcp_enablement_setting on the command + line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + The location id of the geminiGcpEnablementSetting resource. + + To set the location attribute: + ▸ provide the argument gemini_gcp_enablement_setting 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 cloudaicompanion/v1 API. The full documentation for + this API can be found at: https://cloud.google.com/gemini diff --git a/gcloud/gemini/gemini-gcp-enablement-settings/help b/gcloud/gemini/gemini-gcp-enablement-settings/help new file mode 100644 index 000000000..e18aab084 --- /dev/null +++ b/gcloud/gemini/gemini-gcp-enablement-settings/help @@ -0,0 +1,39 @@ +NAME + gcloud gemini gemini-gcp-enablement-settings - manage Gemini Gcp Enablement + Setting resources + +SYNOPSIS + gcloud gemini gemini-gcp-enablement-settings GROUP | COMMAND + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Manage Gemini Gcp Enablement Setting resources. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +GROUPS + GROUP is one of the following: + + setting-bindings + Manage Setting Binding resources. + +COMMANDS + COMMAND is one of the following: + + create + Create geminiGcpEnablementSettings. + + delete + Delete geminiGcpEnablementSettings. + + describe + Describe geminiGcpEnablementSettings. + + list + List geminiGcpEnablementSettings. + + update + Update geminiGcpEnablementSettings. diff --git a/gcloud/gemini/gemini-gcp-enablement-settings/list b/gcloud/gemini/gemini-gcp-enablement-settings/list new file mode 100644 index 000000000..a29700e3f --- /dev/null +++ b/gcloud/gemini/gemini-gcp-enablement-settings/list @@ -0,0 +1,80 @@ +NAME + gcloud gemini gemini-gcp-enablement-settings list - list + geminiGcpEnablementSettings + +SYNOPSIS + gcloud gemini gemini-gcp-enablement-settings list --location=LOCATION + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + List geminiGcpEnablementSettings + +EXAMPLES + To list all geminiGcpEnablementSettings, run: + + $ gcloud gemini gemini-gcp-enablement-settings list + +REQUIRED FLAGS + Location resource - Parent value for + ListGeminiGcpEnablementSettingsRequest This represents a Cloud resource. + (NOTE) Some attributes are not given arguments in this group but can be + set in other ways. + + To set the project attribute: + ◆ provide the argument --location on the command line with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + --location=LOCATION + ID of the location or fully qualified identifier for the location. + + To set the location attribute: + ▸ provide the argument --location on the command line. + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + + --uri + Print a list of resource URIs instead of the default output, and change + the command output to a list of URIs. If this flag is used with + --format, the formatting is applied on this URI list. To display URIs + alongside other keys instead, use the uri() transform. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the cloudaicompanion/v1 API. The full documentation for + this API can be found at: https://cloud.google.com/gemini diff --git a/gcloud/gemini/gemini-gcp-enablement-settings/setting-bindings/create b/gcloud/gemini/gemini-gcp-enablement-settings/setting-bindings/create new file mode 100644 index 000000000..83ed1504b --- /dev/null +++ b/gcloud/gemini/gemini-gcp-enablement-settings/setting-bindings/create @@ -0,0 +1,130 @@ +NAME + gcloud gemini gemini-gcp-enablement-settings setting-bindings create - + create settingBindings + +SYNOPSIS + gcloud gemini gemini-gcp-enablement-settings setting-bindings create + (SETTING_BINDING + : --gemini-gcp-enablement-setting=GEMINI_GCP_ENABLEMENT_SETTING + --location=LOCATION) --target=TARGET [--async] + [--labels=[LABELS,...]] [--product=PRODUCT] [--request-id=REQUEST_ID] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Create a settingBinding + +EXAMPLES + To create the settingBinding, run: + + $ gcloud gemini gemini-gcp-enablement-settings setting-bindings \ create + +POSITIONAL ARGUMENTS + SettingBinding resource - Identifier. Name of the resource. + Format:projects/{project}/locations/{location}/{settingType}/{setting}/settingBindings/{setting_binding} + 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 setting_binding 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. + + SETTING_BINDING + ID of the settingBinding or fully qualified identifier for the + settingBinding. + + To set the setting_binding attribute: + ▸ provide the argument setting_binding on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --gemini-gcp-enablement-setting=GEMINI_GCP_ENABLEMENT_SETTING + The geminiGcpEnablementSetting id of the settingBinding resource. + + To set the gemini-gcp-enablement-setting attribute: + ▸ provide the argument setting_binding on the command line with a + fully specified name; + ▸ provide the argument --gemini-gcp-enablement-setting on the + command line. + + --location=LOCATION + The location id of the settingBinding resource. + + To set the location attribute: + ▸ provide the argument setting_binding on the command line with a + fully specified name; + ▸ provide the argument --location on the command line. + +REQUIRED FLAGS + --target=TARGET + Target of the binding. + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --labels=[LABELS,...] + Labels as key value pairs. + + KEY + Keys must start with a lowercase character and contain only hyphens + (-), underscores (_), lowercase characters, and numbers. + + VALUE + Values must contain only hyphens (-), underscores (_), lowercase + characters, and numbers. + + Shorthand Example: + + --labels=string=string + + JSON Example: + + --labels='{"string": "string"}' + + File Example: + + --labels=path_to_file.(yaml|json) + + --product=PRODUCT + Product type of the setting binding. PRODUCT must be one of: + + gemini-cloud-assist + Gemini Cloud Assist. + gemini-code-assist + Gemini Code Assist. + gemini-in-bigquery + Gemini in BigQuery. + + --request-id=REQUEST_ID + An optional request ID to identify requests. Specify a unique request + ID so that if you must retry your request, the server will know to + ignore the request if it has already been completed. The server will + guarantee that for at least 60 minutes since the first request. + + For example, consider a situation where you make an initial request and + the request times out. If you make the request again with the same + request ID, the server can check if original operation with the same + request ID was received, and if so, will ignore the second request. + This prevents clients from accidentally creating duplicate commitments. + + The request ID must be a valid UUID with the exception that zero UUID + is not supported (00000000-0000-0000-0000-000000000000). + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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 cloudaicompanion/v1 API. The full documentation for + this API can be found at: https://cloud.google.com/gemini diff --git a/gcloud/gemini/gemini-gcp-enablement-settings/setting-bindings/delete b/gcloud/gemini/gemini-gcp-enablement-settings/setting-bindings/delete new file mode 100644 index 000000000..f39d68555 --- /dev/null +++ b/gcloud/gemini/gemini-gcp-enablement-settings/setting-bindings/delete @@ -0,0 +1,91 @@ +NAME + gcloud gemini gemini-gcp-enablement-settings setting-bindings delete - + delete settingBindings + +SYNOPSIS + gcloud gemini gemini-gcp-enablement-settings setting-bindings delete + (SETTING_BINDING + : --gemini-gcp-enablement-setting=GEMINI_GCP_ENABLEMENT_SETTING + --location=LOCATION) [--async] [--request-id=REQUEST_ID] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Delete a settingBinding + +EXAMPLES + To delete the settingBinding, run: + + $ gcloud gemini gemini-gcp-enablement-settings setting-bindings \ delete + +POSITIONAL ARGUMENTS + SettingBinding resource - Name of the resource. 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 setting_binding 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. + + SETTING_BINDING + ID of the settingBinding or fully qualified identifier for the + settingBinding. + + To set the setting_binding attribute: + ▸ provide the argument setting_binding on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --gemini-gcp-enablement-setting=GEMINI_GCP_ENABLEMENT_SETTING + The geminiGcpEnablementSetting id of the settingBinding resource. + + To set the gemini-gcp-enablement-setting attribute: + ▸ provide the argument setting_binding on the command line with a + fully specified name; + ▸ provide the argument --gemini-gcp-enablement-setting on the + command line. + + --location=LOCATION + The location id of the settingBinding resource. + + To set the location attribute: + ▸ provide the argument setting_binding 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. + + --request-id=REQUEST_ID + An optional request ID to identify requests. Specify a unique request + ID so that if you must retry your request, the server will know to + ignore the request if it has already been completed. The server will + guarantee that for at least 60 minutes after the first request. + + For example, consider a situation where you make an initial request and + the request times out. If you make the request again with the same + request ID, the server can check if original operation with the same + request ID was received, and if so, will ignore the second request. + This prevents clients from accidentally creating duplicate commitments. + + The request ID must be a valid UUID with the exception that zero UUID + is not supported (00000000-0000-0000-0000-000000000000). + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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 cloudaicompanion/v1 API. The full documentation for + this API can be found at: https://cloud.google.com/gemini diff --git a/gcloud/gemini/gemini-gcp-enablement-settings/setting-bindings/describe b/gcloud/gemini/gemini-gcp-enablement-settings/setting-bindings/describe new file mode 100644 index 000000000..6e4339e20 --- /dev/null +++ b/gcloud/gemini/gemini-gcp-enablement-settings/setting-bindings/describe @@ -0,0 +1,70 @@ +NAME + gcloud gemini gemini-gcp-enablement-settings setting-bindings describe - + describe settingBindings + +SYNOPSIS + gcloud gemini gemini-gcp-enablement-settings setting-bindings describe + (SETTING_BINDING + : --gemini-gcp-enablement-setting=GEMINI_GCP_ENABLEMENT_SETTING + --location=LOCATION) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Describe a settingBinding + +EXAMPLES + To describe the settingBinding, run: + + $ gcloud gemini gemini-gcp-enablement-settings setting-bindings \ describe + +POSITIONAL ARGUMENTS + SettingBinding resource - Name of the resource. 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 setting_binding 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. + + SETTING_BINDING + ID of the settingBinding or fully qualified identifier for the + settingBinding. + + To set the setting_binding attribute: + ▸ provide the argument setting_binding on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --gemini-gcp-enablement-setting=GEMINI_GCP_ENABLEMENT_SETTING + The geminiGcpEnablementSetting id of the settingBinding resource. + + To set the gemini-gcp-enablement-setting attribute: + ▸ provide the argument setting_binding on the command line with a + fully specified name; + ▸ provide the argument --gemini-gcp-enablement-setting on the + command line. + + --location=LOCATION + The location id of the settingBinding resource. + + To set the location attribute: + ▸ provide the argument setting_binding 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 cloudaicompanion/v1 API. The full documentation for + this API can be found at: https://cloud.google.com/gemini diff --git a/gcloud/gemini/gemini-gcp-enablement-settings/setting-bindings/help b/gcloud/gemini/gemini-gcp-enablement-settings/setting-bindings/help new file mode 100644 index 000000000..85a77ebee --- /dev/null +++ b/gcloud/gemini/gemini-gcp-enablement-settings/setting-bindings/help @@ -0,0 +1,33 @@ +NAME + gcloud gemini gemini-gcp-enablement-settings setting-bindings - manage + Setting Binding resources + +SYNOPSIS + gcloud gemini gemini-gcp-enablement-settings setting-bindings COMMAND + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Manage Setting Binding resources. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + create + Create settingBindings. + + delete + Delete settingBindings. + + describe + Describe settingBindings. + + list + List settingBindings. + + update + Update settingBindings. diff --git a/gcloud/gemini/gemini-gcp-enablement-settings/setting-bindings/list b/gcloud/gemini/gemini-gcp-enablement-settings/setting-bindings/list new file mode 100644 index 000000000..f62e0124c --- /dev/null +++ b/gcloud/gemini/gemini-gcp-enablement-settings/setting-bindings/list @@ -0,0 +1,95 @@ +NAME + gcloud gemini gemini-gcp-enablement-settings setting-bindings list - list + settingBindings + +SYNOPSIS + gcloud gemini gemini-gcp-enablement-settings setting-bindings list + (--gemini-gcp-enablement-setting=GEMINI_GCP_ENABLEMENT_SETTING + : --location=LOCATION) [--filter=EXPRESSION] [--limit=LIMIT] + [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + List settingBindings + +EXAMPLES + To list all settingBindings, run: + + $ gcloud gemini gemini-gcp-enablement-settings setting-bindings list + +REQUIRED FLAGS + GeminiGcpEnablementSetting resource - Parent value for + ListSettingBindingsRequest. 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 --gemini-gcp-enablement-setting 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. + + --gemini-gcp-enablement-setting=GEMINI_GCP_ENABLEMENT_SETTING + ID of the geminiGcpEnablementSetting or fully qualified identifier + for the geminiGcpEnablementSetting. + + To set the gemini-gcp-enablement-setting attribute: + ▸ provide the argument --gemini-gcp-enablement-setting on the + command line. + + This flag argument must be specified if any of the other arguments in + this group are specified. + + --location=LOCATION + The location id of the geminiGcpEnablementSetting resource. + + To set the location attribute: + ▸ provide the argument --gemini-gcp-enablement-setting on the + command line with a fully specified name; + ▸ provide the argument --location on the command line. + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + + --uri + Print a list of resource URIs instead of the default output, and change + the command output to a list of URIs. If this flag is used with + --format, the formatting is applied on this URI list. To display URIs + alongside other keys instead, use the uri() transform. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the cloudaicompanion/v1 API. The full documentation for + this API can be found at: https://cloud.google.com/gemini diff --git a/gcloud/gemini/gemini-gcp-enablement-settings/setting-bindings/update b/gcloud/gemini/gemini-gcp-enablement-settings/setting-bindings/update new file mode 100644 index 000000000..d28df4640 --- /dev/null +++ b/gcloud/gemini/gemini-gcp-enablement-settings/setting-bindings/update @@ -0,0 +1,166 @@ +NAME + gcloud gemini gemini-gcp-enablement-settings setting-bindings update - + update settingBindings + +SYNOPSIS + gcloud gemini gemini-gcp-enablement-settings setting-bindings update + (SETTING_BINDING + : --gemini-gcp-enablement-setting=GEMINI_GCP_ENABLEMENT_SETTING + --location=LOCATION) [--async] [--product=PRODUCT] + [--request-id=REQUEST_ID] [--target=TARGET] + [--labels=[LABELS,...] + | --update-labels=[UPDATE_LABELS,...] --clear-labels + | --remove-labels=[__REMOVE_LABELS,...]] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Update a settingBinding + +EXAMPLES + To update the settingBinding, run: + + $ gcloud gemini gemini-gcp-enablement-settings setting-bindings \ update + +POSITIONAL ARGUMENTS + SettingBinding resource - Identifier. Name of the resource. + Format:projects/{project}/locations/{location}/{settingType}/{setting}/settingBindings/{setting_binding} + 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 setting_binding 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. + + SETTING_BINDING + ID of the settingBinding or fully qualified identifier for the + settingBinding. + + To set the setting_binding attribute: + ▸ provide the argument setting_binding on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --gemini-gcp-enablement-setting=GEMINI_GCP_ENABLEMENT_SETTING + The geminiGcpEnablementSetting id of the settingBinding resource. + + To set the gemini-gcp-enablement-setting attribute: + ▸ provide the argument setting_binding on the command line with a + fully specified name; + ▸ provide the argument --gemini-gcp-enablement-setting on the + command line. + + --location=LOCATION + The location id of the settingBinding resource. + + To set the location attribute: + ▸ provide the argument setting_binding 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. + + --product=PRODUCT + Product type of the setting binding. PRODUCT must be one of: + + gemini-cloud-assist + Gemini Cloud Assist. + gemini-code-assist + Gemini Code Assist. + gemini-in-bigquery + Gemini in BigQuery. + + --request-id=REQUEST_ID + An optional request ID to identify requests. Specify a unique request + ID so that if you must retry your request, the server will know to + ignore the request if it has already been completed. The server will + guarantee that for at least 60 minutes since the first request. + + For example, consider a situation where you make an initial request and + the request times out. If you make the request again with the same + request ID, the server can check if original operation with the same + request ID was received, and if so, will ignore the second request. + This prevents clients from accidentally creating duplicate commitments. + + The request ID must be a valid UUID with the exception that zero UUID + is not supported (00000000-0000-0000-0000-000000000000). + + --target=TARGET + Target of the binding. + + Update labels. + + At most one of these can be specified: + + --labels=[LABELS,...] + Set labels to new value. Labels as key value pairs. + + KEY + Keys must start with a lowercase character and contain only + hyphens (-), underscores (_), lowercase characters, and numbers. + + VALUE + Values must contain only hyphens (-), underscores (_), lowercase + characters, and numbers. + + Shorthand Example: + + --labels=string=string + + JSON Example: + + --labels='{"string": "string"}' + + File Example: + + --labels=path_to_file.(yaml|json) + + --update-labels=[UPDATE_LABELS,...] + Update labels value or add key value pair. Labels as key value pairs. + + KEY + Keys must start with a lowercase character and contain only + hyphens (-), underscores (_), lowercase characters, and numbers. + + VALUE + Values must contain only hyphens (-), underscores (_), lowercase + characters, and numbers. + + Shorthand Example: + + --update-labels=string=string + + JSON Example: + + --update-labels='{"string": "string"}' + + File Example: + + --update-labels=path_to_file.(yaml|json) + + At most one of these can be specified: + + --clear-labels + Clear labels value and set to empty map. + + --remove-labels=[__REMOVE_LABELS,...] + Remove existing value from map labels. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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 cloudaicompanion/v1 API. The full documentation for + this API can be found at: https://cloud.google.com/gemini diff --git a/gcloud/gemini/gemini-gcp-enablement-settings/update b/gcloud/gemini/gemini-gcp-enablement-settings/update new file mode 100644 index 000000000..1ade400d4 --- /dev/null +++ b/gcloud/gemini/gemini-gcp-enablement-settings/update @@ -0,0 +1,144 @@ +NAME + gcloud gemini gemini-gcp-enablement-settings update - update + geminiGcpEnablementSettings + +SYNOPSIS + gcloud gemini gemini-gcp-enablement-settings update + (GEMINI_GCP_ENABLEMENT_SETTING : --location=LOCATION) + [--[no-]enable-customer-data-sharing] [--request-id=REQUEST_ID] + [--labels=[LABELS,...] + | --update-labels=[UPDATE_LABELS,...] --clear-labels + | --remove-labels=[__REMOVE_LABELS,...]] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Update a geminiGcpEnablementSetting + +EXAMPLES + To update the geminiGcpEnablementSetting, run: + + $ gcloud gemini gemini-gcp-enablement-settings update + +POSITIONAL ARGUMENTS + GeminiGcpEnablementSetting resource - Identifier. Name of the resource. + Format:projects/{project}/locations/{location}/geminiGcpEnablementSettings/{geminiGcpEnablementSetting} + 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 gemini_gcp_enablement_setting 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. + + GEMINI_GCP_ENABLEMENT_SETTING + ID of the geminiGcpEnablementSetting or fully qualified identifier + for the geminiGcpEnablementSetting. + + To set the gemini_gcp_enablement_setting attribute: + ▸ provide the argument gemini_gcp_enablement_setting on the command + line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + The location id of the geminiGcpEnablementSetting resource. + + To set the location attribute: + ▸ provide the argument gemini_gcp_enablement_setting on the command + line with a fully specified name; + ▸ provide the argument --location on the command line. + +FLAGS + --[no-]enable-customer-data-sharing + Whether customer data sharing should be enabled. Use + --enable-customer-data-sharing to enable and + --no-enable-customer-data-sharing to disable. + + --request-id=REQUEST_ID + An optional request ID to identify requests. Specify a unique request + ID so that if you must retry your request, the server will know to + ignore the request if it has already been completed. The server will + guarantee that for at least 60 minutes since the first request. + + For example, consider a situation where you make an initial request and + the request times out. If you make the request again with the same + request ID, the server can check if original operation with the same + request ID was received, and if so, will ignore the second request. + This prevents clients from accidentally creating duplicate commitments. + + The request ID must be a valid UUID with the exception that zero UUID + is not supported (00000000-0000-0000-0000-000000000000). + + Update labels. + + At most one of these can be specified: + + --labels=[LABELS,...] + Set labels to new value. Labels as key value pairs. + + KEY + Keys must start with a lowercase character and contain only + hyphens (-), underscores (_), lowercase characters, and numbers. + + VALUE + Values must contain only hyphens (-), underscores (_), lowercase + characters, and numbers. + + Shorthand Example: + + --labels=string=string + + JSON Example: + + --labels='{"string": "string"}' + + File Example: + + --labels=path_to_file.(yaml|json) + + --update-labels=[UPDATE_LABELS,...] + Update labels value or add key value pair. Labels as key value pairs. + + KEY + Keys must start with a lowercase character and contain only + hyphens (-), underscores (_), lowercase characters, and numbers. + + VALUE + Values must contain only hyphens (-), underscores (_), lowercase + characters, and numbers. + + Shorthand Example: + + --update-labels=string=string + + JSON Example: + + --update-labels='{"string": "string"}' + + File Example: + + --update-labels=path_to_file.(yaml|json) + + At most one of these can be specified: + + --clear-labels + Clear labels value and set to empty map. + + --remove-labels=[__REMOVE_LABELS,...] + Remove existing value from map labels. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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 cloudaicompanion/v1 API. The full documentation for + this API can be found at: https://cloud.google.com/gemini diff --git a/gcloud/gemini/help b/gcloud/gemini/help index e3b2eae31..170dc9a5f 100644 --- a/gcloud/gemini/help +++ b/gcloud/gemini/help @@ -18,5 +18,20 @@ GROUPS code-repository-indexes Manage Code Repository Index resources. + code-tools-settings + Manage Code Tools Setting resources. + + data-sharing-with-google-settings + Manage Data Sharing With Google Setting resources. + + gemini-gcp-enablement-settings + Manage Gemini Gcp Enablement Setting resources. + + logging-settings + Manage Logging Setting resources. + operations Manage Operation resources. + + release-channel-settings + Manage Release Channel Setting resources. diff --git a/gcloud/gemini/logging-settings/create b/gcloud/gemini/logging-settings/create new file mode 100644 index 000000000..065381d45 --- /dev/null +++ b/gcloud/gemini/logging-settings/create @@ -0,0 +1,106 @@ +NAME + gcloud gemini logging-settings create - create loggingSettings + +SYNOPSIS + gcloud gemini logging-settings create + (LOGGING_SETTING : --location=LOCATION) [--labels=[LABELS,...]] + [--log-metadata] [--log-prompts-and-responses] + [--request-id=REQUEST_ID] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Create a loggingSetting + +EXAMPLES + To create the loggingSetting, run: + + $ gcloud gemini logging-settings create + +POSITIONAL ARGUMENTS + LoggingSetting resource - Identifier. Name of the resource. + Format:projects/{project}/locations/{location}/loggingsettings/{loggingsetting} + 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 logging_setting 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. + + LOGGING_SETTING + ID of the loggingSetting or fully qualified identifier for the + loggingSetting. + + To set the logging_setting attribute: + ▸ provide the argument logging_setting on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + The location id of the loggingSetting resource. + + To set the location attribute: + ▸ provide the argument logging_setting on the command line with a + fully specified name; + ▸ provide the argument --location on the command line. + +FLAGS + --labels=[LABELS,...] + Labels as key value pairs. + + KEY + Keys must start with a lowercase character and contain only hyphens + (-), underscores (_), lowercase characters, and numbers. + + VALUE + Values must contain only hyphens (-), underscores (_), lowercase + characters, and numbers. + + Shorthand Example: + + --labels=string=string + + JSON Example: + + --labels='{"string": "string"}' + + File Example: + + --labels=path_to_file.(yaml|json) + + --log-metadata + Whether to log metadata. + + --log-prompts-and-responses + Whether to log prompts and responses. + + --request-id=REQUEST_ID + An optional request ID to identify requests. Specify a unique request + ID so that if you must retry your request, the server will know to + ignore the request if it has already been completed. The server will + guarantee that for at least 60 minutes since the first request. + + For example, consider a situation where you make an initial request and + the request times out. If you make the request again with the same + request ID, the server can check if original operation with the same + request ID was received, and if so, will ignore the second request. + This prevents clients from accidentally creating duplicate commitments. + + The request ID must be a valid UUID with the exception that zero UUID + is not supported (00000000-0000-0000-0000-000000000000). + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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 cloudaicompanion/v1 API. The full documentation for + this API can be found at: https://cloud.google.com/gemini diff --git a/gcloud/gemini/logging-settings/delete b/gcloud/gemini/logging-settings/delete new file mode 100644 index 000000000..04e4967bc --- /dev/null +++ b/gcloud/gemini/logging-settings/delete @@ -0,0 +1,75 @@ +NAME + gcloud gemini logging-settings delete - delete loggingSettings + +SYNOPSIS + gcloud gemini logging-settings delete + (LOGGING_SETTING : --location=LOCATION) [--request-id=REQUEST_ID] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Delete a loggingSetting + +EXAMPLES + To delete the loggingSetting, run: + + $ gcloud gemini logging-settings delete + +POSITIONAL ARGUMENTS + LoggingSetting resource - Name of the resource. 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 logging_setting 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. + + LOGGING_SETTING + ID of the loggingSetting or fully qualified identifier for the + loggingSetting. + + To set the logging_setting attribute: + ▸ provide the argument logging_setting on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + The location id of the loggingSetting resource. + + To set the location attribute: + ▸ provide the argument logging_setting on the command line with a + fully specified name; + ▸ provide the argument --location on the command line. + +FLAGS + --request-id=REQUEST_ID + An optional request ID to identify requests. Specify a unique request + ID so that if you must retry your request, the server will know to + ignore the request if it has already been completed. The server will + guarantee that for at least 60 minutes after the first request. + + For example, consider a situation where you make an initial request and + the request times out. If you make the request again with the same + request ID, the server can check if original operation with the same + request ID was received, and if so, will ignore the second request. + This prevents clients from accidentally creating duplicate commitments. + + The request ID must be a valid UUID with the exception that zero UUID + is not supported (00000000-0000-0000-0000-000000000000). + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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 cloudaicompanion/v1 API. The full documentation for + this API can be found at: https://cloud.google.com/gemini diff --git a/gcloud/gemini/logging-settings/describe b/gcloud/gemini/logging-settings/describe new file mode 100644 index 000000000..0d442beab --- /dev/null +++ b/gcloud/gemini/logging-settings/describe @@ -0,0 +1,58 @@ +NAME + gcloud gemini logging-settings describe - describe loggingSettings + +SYNOPSIS + gcloud gemini logging-settings describe + (LOGGING_SETTING : --location=LOCATION) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Describe a loggingSetting + +EXAMPLES + To describe the loggingSetting, run: + + $ gcloud gemini logging-settings describe + +POSITIONAL ARGUMENTS + LoggingSetting resource - Name of the resource. 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 logging_setting 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. + + LOGGING_SETTING + ID of the loggingSetting or fully qualified identifier for the + loggingSetting. + + To set the logging_setting attribute: + ▸ provide the argument logging_setting on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + The location id of the loggingSetting resource. + + To set the location attribute: + ▸ provide the argument logging_setting 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 cloudaicompanion/v1 API. The full documentation for + this API can be found at: https://cloud.google.com/gemini diff --git a/gcloud/gemini/logging-settings/help b/gcloud/gemini/logging-settings/help new file mode 100644 index 000000000..29b75c3c0 --- /dev/null +++ b/gcloud/gemini/logging-settings/help @@ -0,0 +1,37 @@ +NAME + gcloud gemini logging-settings - manage Logging Setting resources + +SYNOPSIS + gcloud gemini logging-settings GROUP | COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Manage Logging Setting resources. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +GROUPS + GROUP is one of the following: + + setting-bindings + Manage Setting Binding resources. + +COMMANDS + COMMAND is one of the following: + + create + Create loggingSettings. + + delete + Delete loggingSettings. + + describe + Describe loggingSettings. + + list + List loggingSettings. + + update + Update loggingSettings. diff --git a/gcloud/gemini/logging-settings/list b/gcloud/gemini/logging-settings/list new file mode 100644 index 000000000..e1fe8e446 --- /dev/null +++ b/gcloud/gemini/logging-settings/list @@ -0,0 +1,78 @@ +NAME + gcloud gemini logging-settings list - list loggingSettings + +SYNOPSIS + gcloud gemini logging-settings list --location=LOCATION + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + List loggingSettings + +EXAMPLES + To list all loggingSettings, run: + + $ gcloud gemini logging-settings list + +REQUIRED FLAGS + Location resource - Parent value for ListLoggingSettingsRequest. This + represents a Cloud resource. (NOTE) Some attributes are not given + arguments in this group but can be set in other ways. + + To set the project attribute: + ◆ provide the argument --location on the command line with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + --location=LOCATION + ID of the location or fully qualified identifier for the location. + + To set the location attribute: + ▸ provide the argument --location on the command line. + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + + --uri + Print a list of resource URIs instead of the default output, and change + the command output to a list of URIs. If this flag is used with + --format, the formatting is applied on this URI list. To display URIs + alongside other keys instead, use the uri() transform. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the cloudaicompanion/v1 API. The full documentation for + this API can be found at: https://cloud.google.com/gemini diff --git a/gcloud/gemini/logging-settings/setting-bindings/create b/gcloud/gemini/logging-settings/setting-bindings/create new file mode 100644 index 000000000..86c015fef --- /dev/null +++ b/gcloud/gemini/logging-settings/setting-bindings/create @@ -0,0 +1,128 @@ +NAME + gcloud gemini logging-settings setting-bindings create - create + settingBindings + +SYNOPSIS + gcloud gemini logging-settings setting-bindings create + (SETTING_BINDING + : --location=LOCATION --logging-setting=LOGGING_SETTING) + --target=TARGET [--async] [--labels=[LABELS,...]] [--product=PRODUCT] + [--request-id=REQUEST_ID] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Create a settingBinding + +EXAMPLES + To create the settingBinding, run: + + $ gcloud gemini logging-settings setting-bindings create + +POSITIONAL ARGUMENTS + SettingBinding resource - Identifier. Name of the resource. + Format:projects/{project}/locations/{location}/{settingType}/{setting}/settingBindings/{setting_binding} + 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 setting_binding 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. + + SETTING_BINDING + ID of the settingBinding or fully qualified identifier for the + settingBinding. + + To set the setting_binding attribute: + ▸ provide the argument setting_binding on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + The location id of the settingBinding resource. + + To set the location attribute: + ▸ provide the argument setting_binding on the command line with a + fully specified name; + ▸ provide the argument --location on the command line. + + --logging-setting=LOGGING_SETTING + The loggingSetting id of the settingBinding resource. + + To set the logging-setting attribute: + ▸ provide the argument setting_binding on the command line with a + fully specified name; + ▸ provide the argument --logging-setting on the command line. + +REQUIRED FLAGS + --target=TARGET + Target of the binding. + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --labels=[LABELS,...] + Labels as key value pairs. + + KEY + Keys must start with a lowercase character and contain only hyphens + (-), underscores (_), lowercase characters, and numbers. + + VALUE + Values must contain only hyphens (-), underscores (_), lowercase + characters, and numbers. + + Shorthand Example: + + --labels=string=string + + JSON Example: + + --labels='{"string": "string"}' + + File Example: + + --labels=path_to_file.(yaml|json) + + --product=PRODUCT + Product type of the setting binding. PRODUCT must be one of: + + gemini-cloud-assist + Gemini Cloud Assist. + gemini-code-assist + Gemini Code Assist. + gemini-in-bigquery + Gemini in BigQuery. + + --request-id=REQUEST_ID + An optional request ID to identify requests. Specify a unique request + ID so that if you must retry your request, the server will know to + ignore the request if it has already been completed. The server will + guarantee that for at least 60 minutes since the first request. + + For example, consider a situation where you make an initial request and + the request times out. If you make the request again with the same + request ID, the server can check if original operation with the same + request ID was received, and if so, will ignore the second request. + This prevents clients from accidentally creating duplicate commitments. + + The request ID must be a valid UUID with the exception that zero UUID + is not supported (00000000-0000-0000-0000-000000000000). + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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 cloudaicompanion/v1 API. The full documentation for + this API can be found at: https://cloud.google.com/gemini diff --git a/gcloud/gemini/logging-settings/setting-bindings/delete b/gcloud/gemini/logging-settings/setting-bindings/delete new file mode 100644 index 000000000..8fc4f7ced --- /dev/null +++ b/gcloud/gemini/logging-settings/setting-bindings/delete @@ -0,0 +1,89 @@ +NAME + gcloud gemini logging-settings setting-bindings delete - delete + settingBindings + +SYNOPSIS + gcloud gemini logging-settings setting-bindings delete + (SETTING_BINDING + : --location=LOCATION --logging-setting=LOGGING_SETTING) [--async] + [--request-id=REQUEST_ID] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Delete a settingBinding + +EXAMPLES + To delete the settingBinding, run: + + $ gcloud gemini logging-settings setting-bindings delete + +POSITIONAL ARGUMENTS + SettingBinding resource - Name of the resource. 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 setting_binding 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. + + SETTING_BINDING + ID of the settingBinding or fully qualified identifier for the + settingBinding. + + To set the setting_binding attribute: + ▸ provide the argument setting_binding on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + The location id of the settingBinding resource. + + To set the location attribute: + ▸ provide the argument setting_binding on the command line with a + fully specified name; + ▸ provide the argument --location on the command line. + + --logging-setting=LOGGING_SETTING + The loggingSetting id of the settingBinding resource. + + To set the logging-setting attribute: + ▸ provide the argument setting_binding on the command line with a + fully specified name; + ▸ provide the argument --logging-setting on the command line. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --request-id=REQUEST_ID + An optional request ID to identify requests. Specify a unique request + ID so that if you must retry your request, the server will know to + ignore the request if it has already been completed. The server will + guarantee that for at least 60 minutes after the first request. + + For example, consider a situation where you make an initial request and + the request times out. If you make the request again with the same + request ID, the server can check if original operation with the same + request ID was received, and if so, will ignore the second request. + This prevents clients from accidentally creating duplicate commitments. + + The request ID must be a valid UUID with the exception that zero UUID + is not supported (00000000-0000-0000-0000-000000000000). + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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 cloudaicompanion/v1 API. The full documentation for + this API can be found at: https://cloud.google.com/gemini diff --git a/gcloud/gemini/logging-settings/setting-bindings/describe b/gcloud/gemini/logging-settings/setting-bindings/describe new file mode 100644 index 000000000..37ffee12e --- /dev/null +++ b/gcloud/gemini/logging-settings/setting-bindings/describe @@ -0,0 +1,69 @@ +NAME + gcloud gemini logging-settings setting-bindings describe - describe + settingBindings + +SYNOPSIS + gcloud gemini logging-settings setting-bindings describe + (SETTING_BINDING + : --location=LOCATION --logging-setting=LOGGING_SETTING) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Describe a settingBinding + +EXAMPLES + To describe the settingBinding, run: + + $ gcloud gemini logging-settings setting-bindings describe + +POSITIONAL ARGUMENTS + SettingBinding resource - Name of the resource. 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 setting_binding 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. + + SETTING_BINDING + ID of the settingBinding or fully qualified identifier for the + settingBinding. + + To set the setting_binding attribute: + ▸ provide the argument setting_binding on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + The location id of the settingBinding resource. + + To set the location attribute: + ▸ provide the argument setting_binding on the command line with a + fully specified name; + ▸ provide the argument --location on the command line. + + --logging-setting=LOGGING_SETTING + The loggingSetting id of the settingBinding resource. + + To set the logging-setting attribute: + ▸ provide the argument setting_binding on the command line with a + fully specified name; + ▸ provide the argument --logging-setting 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 cloudaicompanion/v1 API. The full documentation for + this API can be found at: https://cloud.google.com/gemini diff --git a/gcloud/gemini/logging-settings/setting-bindings/help b/gcloud/gemini/logging-settings/setting-bindings/help new file mode 100644 index 000000000..4bbd817c7 --- /dev/null +++ b/gcloud/gemini/logging-settings/setting-bindings/help @@ -0,0 +1,33 @@ +NAME + gcloud gemini logging-settings setting-bindings - manage Setting Binding + resources + +SYNOPSIS + gcloud gemini logging-settings setting-bindings COMMAND + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Manage Setting Binding resources. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + create + Create settingBindings. + + delete + Delete settingBindings. + + describe + Describe settingBindings. + + list + List settingBindings. + + update + Update settingBindings. diff --git a/gcloud/gemini/logging-settings/setting-bindings/list b/gcloud/gemini/logging-settings/setting-bindings/list new file mode 100644 index 000000000..f5da000ea --- /dev/null +++ b/gcloud/gemini/logging-settings/setting-bindings/list @@ -0,0 +1,92 @@ +NAME + gcloud gemini logging-settings setting-bindings list - list settingBindings + +SYNOPSIS + gcloud gemini logging-settings setting-bindings list + (--logging-setting=LOGGING_SETTING : --location=LOCATION) + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + List settingBindings + +EXAMPLES + To list all settingBindings, run: + + $ gcloud gemini logging-settings setting-bindings list + +REQUIRED FLAGS + LoggingSetting resource - Parent value for ListSettingBindingsRequest. 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 --logging-setting 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. + + --logging-setting=LOGGING_SETTING + ID of the loggingSetting or fully qualified identifier for the + loggingSetting. + + To set the logging-setting attribute: + ▸ provide the argument --logging-setting on the command line. + + This flag argument must be specified if any of the other arguments in + this group are specified. + + --location=LOCATION + The location id of the loggingSetting resource. + + To set the location attribute: + ▸ provide the argument --logging-setting on the command line with a + fully specified name; + ▸ provide the argument --location on the command line. + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + + --uri + Print a list of resource URIs instead of the default output, and change + the command output to a list of URIs. If this flag is used with + --format, the formatting is applied on this URI list. To display URIs + alongside other keys instead, use the uri() transform. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the cloudaicompanion/v1 API. The full documentation for + this API can be found at: https://cloud.google.com/gemini diff --git a/gcloud/gemini/logging-settings/setting-bindings/update b/gcloud/gemini/logging-settings/setting-bindings/update new file mode 100644 index 000000000..76f826ebb --- /dev/null +++ b/gcloud/gemini/logging-settings/setting-bindings/update @@ -0,0 +1,164 @@ +NAME + gcloud gemini logging-settings setting-bindings update - update + settingBindings + +SYNOPSIS + gcloud gemini logging-settings setting-bindings update + (SETTING_BINDING + : --location=LOCATION --logging-setting=LOGGING_SETTING) [--async] + [--product=PRODUCT] [--request-id=REQUEST_ID] [--target=TARGET] + [--labels=[LABELS,...] + | --update-labels=[UPDATE_LABELS,...] --clear-labels + | --remove-labels=[__REMOVE_LABELS,...]] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Update a settingBinding + +EXAMPLES + To update the settingBinding, run: + + $ gcloud gemini logging-settings setting-bindings update + +POSITIONAL ARGUMENTS + SettingBinding resource - Identifier. Name of the resource. + Format:projects/{project}/locations/{location}/{settingType}/{setting}/settingBindings/{setting_binding} + 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 setting_binding 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. + + SETTING_BINDING + ID of the settingBinding or fully qualified identifier for the + settingBinding. + + To set the setting_binding attribute: + ▸ provide the argument setting_binding on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + The location id of the settingBinding resource. + + To set the location attribute: + ▸ provide the argument setting_binding on the command line with a + fully specified name; + ▸ provide the argument --location on the command line. + + --logging-setting=LOGGING_SETTING + The loggingSetting id of the settingBinding resource. + + To set the logging-setting attribute: + ▸ provide the argument setting_binding on the command line with a + fully specified name; + ▸ provide the argument --logging-setting on the command line. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --product=PRODUCT + Product type of the setting binding. PRODUCT must be one of: + + gemini-cloud-assist + Gemini Cloud Assist. + gemini-code-assist + Gemini Code Assist. + gemini-in-bigquery + Gemini in BigQuery. + + --request-id=REQUEST_ID + An optional request ID to identify requests. Specify a unique request + ID so that if you must retry your request, the server will know to + ignore the request if it has already been completed. The server will + guarantee that for at least 60 minutes since the first request. + + For example, consider a situation where you make an initial request and + the request times out. If you make the request again with the same + request ID, the server can check if original operation with the same + request ID was received, and if so, will ignore the second request. + This prevents clients from accidentally creating duplicate commitments. + + The request ID must be a valid UUID with the exception that zero UUID + is not supported (00000000-0000-0000-0000-000000000000). + + --target=TARGET + Target of the binding. + + Update labels. + + At most one of these can be specified: + + --labels=[LABELS,...] + Set labels to new value. Labels as key value pairs. + + KEY + Keys must start with a lowercase character and contain only + hyphens (-), underscores (_), lowercase characters, and numbers. + + VALUE + Values must contain only hyphens (-), underscores (_), lowercase + characters, and numbers. + + Shorthand Example: + + --labels=string=string + + JSON Example: + + --labels='{"string": "string"}' + + File Example: + + --labels=path_to_file.(yaml|json) + + --update-labels=[UPDATE_LABELS,...] + Update labels value or add key value pair. Labels as key value pairs. + + KEY + Keys must start with a lowercase character and contain only + hyphens (-), underscores (_), lowercase characters, and numbers. + + VALUE + Values must contain only hyphens (-), underscores (_), lowercase + characters, and numbers. + + Shorthand Example: + + --update-labels=string=string + + JSON Example: + + --update-labels='{"string": "string"}' + + File Example: + + --update-labels=path_to_file.(yaml|json) + + At most one of these can be specified: + + --clear-labels + Clear labels value and set to empty map. + + --remove-labels=[__REMOVE_LABELS,...] + Remove existing value from map labels. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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 cloudaicompanion/v1 API. The full documentation for + this API can be found at: https://cloud.google.com/gemini diff --git a/gcloud/gemini/logging-settings/update b/gcloud/gemini/logging-settings/update new file mode 100644 index 000000000..92ec52034 --- /dev/null +++ b/gcloud/gemini/logging-settings/update @@ -0,0 +1,145 @@ +NAME + gcloud gemini logging-settings update - update loggingSettings + +SYNOPSIS + gcloud gemini logging-settings update + (LOGGING_SETTING : --location=LOCATION) [--[no-]log-metadata] + [--[no-]log-prompts-and-responses] [--request-id=REQUEST_ID] + [--labels=[LABELS,...] + | --update-labels=[UPDATE_LABELS,...] --clear-labels + | --remove-labels=[__REMOVE_LABELS,...]] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Update a loggingSetting + +EXAMPLES + To update the loggingSetting, run: + + $ gcloud gemini logging-settings update + +POSITIONAL ARGUMENTS + LoggingSetting resource - Identifier. Name of the resource. + Format:projects/{project}/locations/{location}/loggingsettings/{loggingsetting} + 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 logging_setting 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. + + LOGGING_SETTING + ID of the loggingSetting or fully qualified identifier for the + loggingSetting. + + To set the logging_setting attribute: + ▸ provide the argument logging_setting on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + The location id of the loggingSetting resource. + + To set the location attribute: + ▸ provide the argument logging_setting on the command line with a + fully specified name; + ▸ provide the argument --location on the command line. + +FLAGS + --[no-]log-metadata + Whether to log metadata. Use --log-metadata to enable and + --no-log-metadata to disable. + + --[no-]log-prompts-and-responses + Whether to log prompts and responses. Use --log-prompts-and-responses + to enable and --no-log-prompts-and-responses to disable. + + --request-id=REQUEST_ID + An optional request ID to identify requests. Specify a unique request + ID so that if you must retry your request, the server will know to + ignore the request if it has already been completed. The server will + guarantee that for at least 60 minutes since the first request. + + For example, consider a situation where you make an initial request and + the request times out. If you make the request again with the same + request ID, the server can check if original operation with the same + request ID was received, and if so, will ignore the second request. + This prevents clients from accidentally creating duplicate commitments. + + The request ID must be a valid UUID with the exception that zero UUID + is not supported (00000000-0000-0000-0000-000000000000). + + Update labels. + + At most one of these can be specified: + + --labels=[LABELS,...] + Set labels to new value. Labels as key value pairs. + + KEY + Keys must start with a lowercase character and contain only + hyphens (-), underscores (_), lowercase characters, and numbers. + + VALUE + Values must contain only hyphens (-), underscores (_), lowercase + characters, and numbers. + + Shorthand Example: + + --labels=string=string + + JSON Example: + + --labels='{"string": "string"}' + + File Example: + + --labels=path_to_file.(yaml|json) + + --update-labels=[UPDATE_LABELS,...] + Update labels value or add key value pair. Labels as key value pairs. + + KEY + Keys must start with a lowercase character and contain only + hyphens (-), underscores (_), lowercase characters, and numbers. + + VALUE + Values must contain only hyphens (-), underscores (_), lowercase + characters, and numbers. + + Shorthand Example: + + --update-labels=string=string + + JSON Example: + + --update-labels='{"string": "string"}' + + File Example: + + --update-labels=path_to_file.(yaml|json) + + At most one of these can be specified: + + --clear-labels + Clear labels value and set to empty map. + + --remove-labels=[__REMOVE_LABELS,...] + Remove existing value from map labels. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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 cloudaicompanion/v1 API. The full documentation for + this API can be found at: https://cloud.google.com/gemini diff --git a/gcloud/gemini/release-channel-settings/create b/gcloud/gemini/release-channel-settings/create new file mode 100644 index 000000000..61fe0d5e6 --- /dev/null +++ b/gcloud/gemini/release-channel-settings/create @@ -0,0 +1,109 @@ +NAME + gcloud gemini release-channel-settings create - create + releaseChannelSettings + +SYNOPSIS + gcloud gemini release-channel-settings create + (RELEASE_CHANNEL_SETTING : --location=LOCATION) [--labels=[LABELS,...]] + [--release-channel=RELEASE_CHANNEL] [--request-id=REQUEST_ID] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Create a releaseChannelSetting + +EXAMPLES + To create the releaseChannelSetting, run: + + $ gcloud gemini release-channel-settings create + +POSITIONAL ARGUMENTS + ReleaseChannelSetting resource - Identifier. Name of the resource. + Format:projects/{project}/locations/{location}/releaseChannelSettings/{releaseChannelSetting} + 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 release_channel_setting 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. + + RELEASE_CHANNEL_SETTING + ID of the releaseChannelSetting or fully qualified identifier for the + releaseChannelSetting. + + To set the release_channel_setting attribute: + ▸ provide the argument release_channel_setting on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + The location id of the releaseChannelSetting resource. + + To set the location attribute: + ▸ provide the argument release_channel_setting on the command line + with a fully specified name; + ▸ provide the argument --location on the command line. + +FLAGS + --labels=[LABELS,...] + Labels as key value pairs. + + KEY + Keys must start with a lowercase character and contain only hyphens + (-), underscores (_), lowercase characters, and numbers. + + VALUE + Values must contain only hyphens (-), underscores (_), lowercase + characters, and numbers. + + Shorthand Example: + + --labels=string=string + + JSON Example: + + --labels='{"string": "string"}' + + File Example: + + --labels=path_to_file.(yaml|json) + + --release-channel=RELEASE_CHANNEL + Release channel to be used. RELEASE_CHANNEL must be one of: + + experimental + Experimental release channel. + stable + Stable channel. + + --request-id=REQUEST_ID + An optional request ID to identify requests. Specify a unique request + ID so that if you must retry your request, the server will know to + ignore the request if it has already been completed. The server will + guarantee that for at least 60 minutes since the first request. + + For example, consider a situation where you make an initial request and + the request times out. If you make the request again with the same + request ID, the server can check if original operation with the same + request ID was received, and if so, will ignore the second request. + This prevents clients from accidentally creating duplicate commitments. + + The request ID must be a valid UUID with the exception that zero UUID + is not supported (00000000-0000-0000-0000-000000000000). + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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 cloudaicompanion/v1 API. The full documentation for + this API can be found at: https://cloud.google.com/gemini diff --git a/gcloud/gemini/release-channel-settings/delete b/gcloud/gemini/release-channel-settings/delete new file mode 100644 index 000000000..f6a00be74 --- /dev/null +++ b/gcloud/gemini/release-channel-settings/delete @@ -0,0 +1,76 @@ +NAME + gcloud gemini release-channel-settings delete - delete + releaseChannelSettings + +SYNOPSIS + gcloud gemini release-channel-settings delete + (RELEASE_CHANNEL_SETTING : --location=LOCATION) + [--request-id=REQUEST_ID] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Delete a releaseChannelSetting + +EXAMPLES + To delete the releaseChannelSetting, run: + + $ gcloud gemini release-channel-settings delete + +POSITIONAL ARGUMENTS + ReleaseChannelSetting resource - Name of the resource 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 release_channel_setting 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. + + RELEASE_CHANNEL_SETTING + ID of the releaseChannelSetting or fully qualified identifier for the + releaseChannelSetting. + + To set the release_channel_setting attribute: + ▸ provide the argument release_channel_setting on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + The location id of the releaseChannelSetting resource. + + To set the location attribute: + ▸ provide the argument release_channel_setting on the command line + with a fully specified name; + ▸ provide the argument --location on the command line. + +FLAGS + --request-id=REQUEST_ID + An optional request ID to identify requests. Specify a unique request + ID so that if you must retry your request, the server will know to + ignore the request if it has already been completed. The server will + guarantee that for at least 60 minutes after the first request. + + For example, consider a situation where you make an initial request and + the request times out. If you make the request again with the same + request ID, the server can check if original operation with the same + request ID was received, and if so, will ignore the second request. + This prevents clients from accidentally creating duplicate commitments. + + The request ID must be a valid UUID with the exception that zero UUID + is not supported (00000000-0000-0000-0000-000000000000). + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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 cloudaicompanion/v1 API. The full documentation for + this API can be found at: https://cloud.google.com/gemini diff --git a/gcloud/gemini/release-channel-settings/describe b/gcloud/gemini/release-channel-settings/describe new file mode 100644 index 000000000..0b6bd74f6 --- /dev/null +++ b/gcloud/gemini/release-channel-settings/describe @@ -0,0 +1,59 @@ +NAME + gcloud gemini release-channel-settings describe - describe + releaseChannelSettings + +SYNOPSIS + gcloud gemini release-channel-settings describe + (RELEASE_CHANNEL_SETTING : --location=LOCATION) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Describe a releaseChannelSetting + +EXAMPLES + To describe the releaseChannelSetting, run: + + $ gcloud gemini release-channel-settings describe + +POSITIONAL ARGUMENTS + ReleaseChannelSetting resource - Name of the resource. 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 release_channel_setting 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. + + RELEASE_CHANNEL_SETTING + ID of the releaseChannelSetting or fully qualified identifier for the + releaseChannelSetting. + + To set the release_channel_setting attribute: + ▸ provide the argument release_channel_setting on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + The location id of the releaseChannelSetting resource. + + To set the location attribute: + ▸ provide the argument release_channel_setting 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 cloudaicompanion/v1 API. The full documentation for + this API can be found at: https://cloud.google.com/gemini diff --git a/gcloud/gemini/release-channel-settings/help b/gcloud/gemini/release-channel-settings/help new file mode 100644 index 000000000..d05f2050e --- /dev/null +++ b/gcloud/gemini/release-channel-settings/help @@ -0,0 +1,39 @@ +NAME + gcloud gemini release-channel-settings - manage Release Channel Setting + resources + +SYNOPSIS + gcloud gemini release-channel-settings GROUP | COMMAND + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Manage Release Channel Setting resources. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +GROUPS + GROUP is one of the following: + + setting-bindings + Manage Setting Binding resources. + +COMMANDS + COMMAND is one of the following: + + create + Create releaseChannelSettings. + + delete + Delete releaseChannelSettings. + + describe + Describe releaseChannelSettings. + + list + List releaseChannelSettings. + + update + Update releaseChannelSettings. diff --git a/gcloud/gemini/release-channel-settings/list b/gcloud/gemini/release-channel-settings/list new file mode 100644 index 000000000..28ccc6609 --- /dev/null +++ b/gcloud/gemini/release-channel-settings/list @@ -0,0 +1,78 @@ +NAME + gcloud gemini release-channel-settings list - list releaseChannelSettings + +SYNOPSIS + gcloud gemini release-channel-settings list --location=LOCATION + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + List releaseChannelSettings + +EXAMPLES + To list all releaseChannelSettings, run: + + $ gcloud gemini release-channel-settings list + +REQUIRED FLAGS + Location resource - Parent value for ListReleaseChannelSettingsRequest + This represents a Cloud resource. (NOTE) Some attributes are not given + arguments in this group but can be set in other ways. + + To set the project attribute: + ◆ provide the argument --location on the command line with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + --location=LOCATION + ID of the location or fully qualified identifier for the location. + + To set the location attribute: + ▸ provide the argument --location on the command line. + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + + --uri + Print a list of resource URIs instead of the default output, and change + the command output to a list of URIs. If this flag is used with + --format, the formatting is applied on this URI list. To display URIs + alongside other keys instead, use the uri() transform. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the cloudaicompanion/v1 API. The full documentation for + this API can be found at: https://cloud.google.com/gemini diff --git a/gcloud/gemini/release-channel-settings/setting-bindings/create b/gcloud/gemini/release-channel-settings/setting-bindings/create new file mode 100644 index 000000000..3244323d2 --- /dev/null +++ b/gcloud/gemini/release-channel-settings/setting-bindings/create @@ -0,0 +1,129 @@ +NAME + gcloud gemini release-channel-settings setting-bindings create - create + settingBindings + +SYNOPSIS + gcloud gemini release-channel-settings setting-bindings create + (SETTING_BINDING : --location=LOCATION + --release-channel-setting=RELEASE_CHANNEL_SETTING) --target=TARGET + [--async] [--labels=[LABELS,...]] [--product=PRODUCT] + [--request-id=REQUEST_ID] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Create a settingBinding + +EXAMPLES + To create the settingBinding, run: + + $ gcloud gemini release-channel-settings setting-bindings create + +POSITIONAL ARGUMENTS + SettingBinding resource - Identifier. Name of the resource. + Format:projects/{project}/locations/{location}/{settingType}/{setting}/settingBindings/{setting_binding} + 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 setting_binding 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. + + SETTING_BINDING + ID of the settingBinding or fully qualified identifier for the + settingBinding. + + To set the setting_binding attribute: + ▸ provide the argument setting_binding on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + The location id of the settingBinding resource. + + To set the location attribute: + ▸ provide the argument setting_binding on the command line with a + fully specified name; + ▸ provide the argument --location on the command line. + + --release-channel-setting=RELEASE_CHANNEL_SETTING + The releaseChannelSetting id of the settingBinding resource. + + To set the release-channel-setting attribute: + ▸ provide the argument setting_binding on the command line with a + fully specified name; + ▸ provide the argument --release-channel-setting on the command + line. + +REQUIRED FLAGS + --target=TARGET + Target of the binding. + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --labels=[LABELS,...] + Labels as key value pairs. + + KEY + Keys must start with a lowercase character and contain only hyphens + (-), underscores (_), lowercase characters, and numbers. + + VALUE + Values must contain only hyphens (-), underscores (_), lowercase + characters, and numbers. + + Shorthand Example: + + --labels=string=string + + JSON Example: + + --labels='{"string": "string"}' + + File Example: + + --labels=path_to_file.(yaml|json) + + --product=PRODUCT + Product type of the setting binding. PRODUCT must be one of: + + gemini-cloud-assist + Gemini Cloud Assist. + gemini-code-assist + Gemini Code Assist. + gemini-in-bigquery + Gemini in BigQuery. + + --request-id=REQUEST_ID + An optional request ID to identify requests. Specify a unique request + ID so that if you must retry your request, the server will know to + ignore the request if it has already been completed. The server will + guarantee that for at least 60 minutes since the first request. + + For example, consider a situation where you make an initial request and + the request times out. If you make the request again with the same + request ID, the server can check if original operation with the same + request ID was received, and if so, will ignore the second request. + This prevents clients from accidentally creating duplicate commitments. + + The request ID must be a valid UUID with the exception that zero UUID + is not supported (00000000-0000-0000-0000-000000000000). + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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 cloudaicompanion/v1 API. The full documentation for + this API can be found at: https://cloud.google.com/gemini diff --git a/gcloud/gemini/release-channel-settings/setting-bindings/delete b/gcloud/gemini/release-channel-settings/setting-bindings/delete new file mode 100644 index 000000000..e7f657c18 --- /dev/null +++ b/gcloud/gemini/release-channel-settings/setting-bindings/delete @@ -0,0 +1,90 @@ +NAME + gcloud gemini release-channel-settings setting-bindings delete - delete + settingBindings + +SYNOPSIS + gcloud gemini release-channel-settings setting-bindings delete + (SETTING_BINDING : --location=LOCATION + --release-channel-setting=RELEASE_CHANNEL_SETTING) [--async] + [--request-id=REQUEST_ID] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Delete a settingBinding + +EXAMPLES + To delete the settingBinding, run: + + $ gcloud gemini release-channel-settings setting-bindings delete + +POSITIONAL ARGUMENTS + SettingBinding resource - Name of the resource. 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 setting_binding 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. + + SETTING_BINDING + ID of the settingBinding or fully qualified identifier for the + settingBinding. + + To set the setting_binding attribute: + ▸ provide the argument setting_binding on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + The location id of the settingBinding resource. + + To set the location attribute: + ▸ provide the argument setting_binding on the command line with a + fully specified name; + ▸ provide the argument --location on the command line. + + --release-channel-setting=RELEASE_CHANNEL_SETTING + The releaseChannelSetting id of the settingBinding resource. + + To set the release-channel-setting attribute: + ▸ provide the argument setting_binding on the command line with a + fully specified name; + ▸ provide the argument --release-channel-setting on the command + line. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --request-id=REQUEST_ID + An optional request ID to identify requests. Specify a unique request + ID so that if you must retry your request, the server will know to + ignore the request if it has already been completed. The server will + guarantee that for at least 60 minutes after the first request. + + For example, consider a situation where you make an initial request and + the request times out. If you make the request again with the same + request ID, the server can check if original operation with the same + request ID was received, and if so, will ignore the second request. + This prevents clients from accidentally creating duplicate commitments. + + The request ID must be a valid UUID with the exception that zero UUID + is not supported (00000000-0000-0000-0000-000000000000). + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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 cloudaicompanion/v1 API. The full documentation for + this API can be found at: https://cloud.google.com/gemini diff --git a/gcloud/gemini/release-channel-settings/setting-bindings/describe b/gcloud/gemini/release-channel-settings/setting-bindings/describe new file mode 100644 index 000000000..170e73e48 --- /dev/null +++ b/gcloud/gemini/release-channel-settings/setting-bindings/describe @@ -0,0 +1,70 @@ +NAME + gcloud gemini release-channel-settings setting-bindings describe - describe + settingBindings + +SYNOPSIS + gcloud gemini release-channel-settings setting-bindings describe + (SETTING_BINDING : --location=LOCATION + --release-channel-setting=RELEASE_CHANNEL_SETTING) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Describe a settingBinding + +EXAMPLES + To describe the settingBinding, run: + + $ gcloud gemini release-channel-settings setting-bindings describe + +POSITIONAL ARGUMENTS + SettingBinding resource - Name of the resource. 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 setting_binding 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. + + SETTING_BINDING + ID of the settingBinding or fully qualified identifier for the + settingBinding. + + To set the setting_binding attribute: + ▸ provide the argument setting_binding on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + The location id of the settingBinding resource. + + To set the location attribute: + ▸ provide the argument setting_binding on the command line with a + fully specified name; + ▸ provide the argument --location on the command line. + + --release-channel-setting=RELEASE_CHANNEL_SETTING + The releaseChannelSetting id of the settingBinding resource. + + To set the release-channel-setting attribute: + ▸ provide the argument setting_binding on the command line with a + fully specified name; + ▸ provide the argument --release-channel-setting 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 cloudaicompanion/v1 API. The full documentation for + this API can be found at: https://cloud.google.com/gemini diff --git a/gcloud/gemini/release-channel-settings/setting-bindings/help b/gcloud/gemini/release-channel-settings/setting-bindings/help new file mode 100644 index 000000000..f398d433a --- /dev/null +++ b/gcloud/gemini/release-channel-settings/setting-bindings/help @@ -0,0 +1,33 @@ +NAME + gcloud gemini release-channel-settings setting-bindings - manage Setting + Binding resources + +SYNOPSIS + gcloud gemini release-channel-settings setting-bindings COMMAND + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Manage Setting Binding resources. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + create + Create settingBindings. + + delete + Delete settingBindings. + + describe + Describe settingBindings. + + list + List settingBindings. + + update + Update settingBindings. diff --git a/gcloud/gemini/release-channel-settings/setting-bindings/list b/gcloud/gemini/release-channel-settings/setting-bindings/list new file mode 100644 index 000000000..8e0413acb --- /dev/null +++ b/gcloud/gemini/release-channel-settings/setting-bindings/list @@ -0,0 +1,95 @@ +NAME + gcloud gemini release-channel-settings setting-bindings list - list + settingBindings + +SYNOPSIS + gcloud gemini release-channel-settings setting-bindings list + (--release-channel-setting=RELEASE_CHANNEL_SETTING + : --location=LOCATION) [--filter=EXPRESSION] [--limit=LIMIT] + [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + List settingBindings + +EXAMPLES + To list all settingBindings, run: + + $ gcloud gemini release-channel-settings setting-bindings list + +REQUIRED FLAGS + ReleaseChannelSetting resource - Parent value for + ListSettingBindingsRequest. 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 --release-channel-setting 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. + + --release-channel-setting=RELEASE_CHANNEL_SETTING + ID of the releaseChannelSetting or fully qualified identifier for the + releaseChannelSetting. + + To set the release-channel-setting attribute: + ▸ provide the argument --release-channel-setting on the command + line. + + This flag argument must be specified if any of the other arguments in + this group are specified. + + --location=LOCATION + The location id of the releaseChannelSetting resource. + + To set the location attribute: + ▸ provide the argument --release-channel-setting on the command + line with a fully specified name; + ▸ provide the argument --location on the command line. + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + + --uri + Print a list of resource URIs instead of the default output, and change + the command output to a list of URIs. If this flag is used with + --format, the formatting is applied on this URI list. To display URIs + alongside other keys instead, use the uri() transform. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the cloudaicompanion/v1 API. The full documentation for + this API can be found at: https://cloud.google.com/gemini diff --git a/gcloud/gemini/release-channel-settings/setting-bindings/update b/gcloud/gemini/release-channel-settings/setting-bindings/update new file mode 100644 index 000000000..e1dac35e9 --- /dev/null +++ b/gcloud/gemini/release-channel-settings/setting-bindings/update @@ -0,0 +1,165 @@ +NAME + gcloud gemini release-channel-settings setting-bindings update - update + settingBindings + +SYNOPSIS + gcloud gemini release-channel-settings setting-bindings update + (SETTING_BINDING : --location=LOCATION + --release-channel-setting=RELEASE_CHANNEL_SETTING) [--async] + [--product=PRODUCT] [--request-id=REQUEST_ID] [--target=TARGET] + [--labels=[LABELS,...] + | --update-labels=[UPDATE_LABELS,...] --clear-labels + | --remove-labels=[__REMOVE_LABELS,...]] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Update a settingBinding + +EXAMPLES + To update the settingBinding, run: + + $ gcloud gemini release-channel-settings setting-bindings update + +POSITIONAL ARGUMENTS + SettingBinding resource - Identifier. Name of the resource. + Format:projects/{project}/locations/{location}/{settingType}/{setting}/settingBindings/{setting_binding} + 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 setting_binding 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. + + SETTING_BINDING + ID of the settingBinding or fully qualified identifier for the + settingBinding. + + To set the setting_binding attribute: + ▸ provide the argument setting_binding on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + The location id of the settingBinding resource. + + To set the location attribute: + ▸ provide the argument setting_binding on the command line with a + fully specified name; + ▸ provide the argument --location on the command line. + + --release-channel-setting=RELEASE_CHANNEL_SETTING + The releaseChannelSetting id of the settingBinding resource. + + To set the release-channel-setting attribute: + ▸ provide the argument setting_binding on the command line with a + fully specified name; + ▸ provide the argument --release-channel-setting on the command + line. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --product=PRODUCT + Product type of the setting binding. PRODUCT must be one of: + + gemini-cloud-assist + Gemini Cloud Assist. + gemini-code-assist + Gemini Code Assist. + gemini-in-bigquery + Gemini in BigQuery. + + --request-id=REQUEST_ID + An optional request ID to identify requests. Specify a unique request + ID so that if you must retry your request, the server will know to + ignore the request if it has already been completed. The server will + guarantee that for at least 60 minutes since the first request. + + For example, consider a situation where you make an initial request and + the request times out. If you make the request again with the same + request ID, the server can check if original operation with the same + request ID was received, and if so, will ignore the second request. + This prevents clients from accidentally creating duplicate commitments. + + The request ID must be a valid UUID with the exception that zero UUID + is not supported (00000000-0000-0000-0000-000000000000). + + --target=TARGET + Target of the binding. + + Update labels. + + At most one of these can be specified: + + --labels=[LABELS,...] + Set labels to new value. Labels as key value pairs. + + KEY + Keys must start with a lowercase character and contain only + hyphens (-), underscores (_), lowercase characters, and numbers. + + VALUE + Values must contain only hyphens (-), underscores (_), lowercase + characters, and numbers. + + Shorthand Example: + + --labels=string=string + + JSON Example: + + --labels='{"string": "string"}' + + File Example: + + --labels=path_to_file.(yaml|json) + + --update-labels=[UPDATE_LABELS,...] + Update labels value or add key value pair. Labels as key value pairs. + + KEY + Keys must start with a lowercase character and contain only + hyphens (-), underscores (_), lowercase characters, and numbers. + + VALUE + Values must contain only hyphens (-), underscores (_), lowercase + characters, and numbers. + + Shorthand Example: + + --update-labels=string=string + + JSON Example: + + --update-labels='{"string": "string"}' + + File Example: + + --update-labels=path_to_file.(yaml|json) + + At most one of these can be specified: + + --clear-labels + Clear labels value and set to empty map. + + --remove-labels=[__REMOVE_LABELS,...] + Remove existing value from map labels. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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 cloudaicompanion/v1 API. The full documentation for + this API can be found at: https://cloud.google.com/gemini diff --git a/gcloud/gemini/release-channel-settings/update b/gcloud/gemini/release-channel-settings/update new file mode 100644 index 000000000..b59993be8 --- /dev/null +++ b/gcloud/gemini/release-channel-settings/update @@ -0,0 +1,146 @@ +NAME + gcloud gemini release-channel-settings update - update + releaseChannelSettings + +SYNOPSIS + gcloud gemini release-channel-settings update + (RELEASE_CHANNEL_SETTING : --location=LOCATION) + [--release-channel=RELEASE_CHANNEL] [--request-id=REQUEST_ID] + [--labels=[LABELS,...] + | --update-labels=[UPDATE_LABELS,...] --clear-labels + | --remove-labels=[__REMOVE_LABELS,...]] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Update a releaseChannelSetting + +EXAMPLES + To update the releaseChannelSetting, run: + + $ gcloud gemini release-channel-settings update + +POSITIONAL ARGUMENTS + ReleaseChannelSetting resource - Identifier. Name of the resource. + Format:projects/{project}/locations/{location}/releaseChannelSettings/{releaseChannelSetting} + 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 release_channel_setting 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. + + RELEASE_CHANNEL_SETTING + ID of the releaseChannelSetting or fully qualified identifier for the + releaseChannelSetting. + + To set the release_channel_setting attribute: + ▸ provide the argument release_channel_setting on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + The location id of the releaseChannelSetting resource. + + To set the location attribute: + ▸ provide the argument release_channel_setting on the command line + with a fully specified name; + ▸ provide the argument --location on the command line. + +FLAGS + --release-channel=RELEASE_CHANNEL + Release channel to be used. RELEASE_CHANNEL must be one of: + + experimental + Experimental release channel. + stable + Stable channel. + + --request-id=REQUEST_ID + An optional request ID to identify requests. Specify a unique request + ID so that if you must retry your request, the server will know to + ignore the request if it has already been completed. The server will + guarantee that for at least 60 minutes since the first request. + + For example, consider a situation where you make an initial request and + the request times out. If you make the request again with the same + request ID, the server can check if original operation with the same + request ID was received, and if so, will ignore the second request. + This prevents clients from accidentally creating duplicate commitments. + + The request ID must be a valid UUID with the exception that zero UUID + is not supported (00000000-0000-0000-0000-000000000000). + + Update labels. + + At most one of these can be specified: + + --labels=[LABELS,...] + Set labels to new value. Labels as key value pairs. + + KEY + Keys must start with a lowercase character and contain only + hyphens (-), underscores (_), lowercase characters, and numbers. + + VALUE + Values must contain only hyphens (-), underscores (_), lowercase + characters, and numbers. + + Shorthand Example: + + --labels=string=string + + JSON Example: + + --labels='{"string": "string"}' + + File Example: + + --labels=path_to_file.(yaml|json) + + --update-labels=[UPDATE_LABELS,...] + Update labels value or add key value pair. Labels as key value pairs. + + KEY + Keys must start with a lowercase character and contain only + hyphens (-), underscores (_), lowercase characters, and numbers. + + VALUE + Values must contain only hyphens (-), underscores (_), lowercase + characters, and numbers. + + Shorthand Example: + + --update-labels=string=string + + JSON Example: + + --update-labels='{"string": "string"}' + + File Example: + + --update-labels=path_to_file.(yaml|json) + + At most one of these can be specified: + + --clear-labels + Clear labels value and set to empty map. + + --remove-labels=[__REMOVE_LABELS,...] + Remove existing value from map labels. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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 cloudaicompanion/v1 API. The full documentation for + this API can be found at: https://cloud.google.com/gemini diff --git a/gcloud/iam/workload-identity-pools/create-cred-config b/gcloud/iam/workload-identity-pools/create-cred-config index 9f7c6fce8..0e339277f 100644 --- a/gcloud/iam/workload-identity-pools/create-cred-config +++ b/gcloud/iam/workload-identity-pools/create-cred-config @@ -14,7 +14,7 @@ SYNOPSIS [--credential-source-type=CREDENTIAL_SOURCE_TYPE] [--enable-imdsv2] [--subject-token-type=SUBJECT_TOKEN_TYPE] [--credential-cert-private-key-path=CREDENTIAL_CERT_PRIVATE_KEY_PATH - : --credential-cert-configuration-output-file=CREDENTIAL_CERT_CONFIGURATION_OUTPUT_FILE] + : --credential-cert-configuration-output-file=CREDENTIAL_CERT_CONFIGURATION_OUTPUT_FILE --credential-cert-trust-chain-path=CREDENTIAL_CERT_TRUST_CHAIN_PATH] [--executable-output-file=EXECUTABLE_OUTPUT_FILE --executable-timeout-millis=EXECUTABLE_TIMEOUT_MILLIS] [--service-account=SERVICE_ACCOUNT @@ -153,6 +153,13 @@ OPTIONAL FLAGS If not specified, the certificate configuration will be created at the default gcloud location. + --credential-cert-trust-chain-path=CREDENTIAL_CERT_TRUST_CHAIN_PATH + Path for the trust chain file. A trust chain file is required if + there are intermediate certificates in the certificate chain in + between the root certificate stored in the workload identity pool + provider trust store. This trust chain file should be a list of PEM + certificates, with the leaf certificate at the top. + Arguments for an executable type credential source. --executable-output-file=EXECUTABLE_OUTPUT_FILE diff --git a/gcloud/logging/write b/gcloud/logging/write index 2230348ee..bcb0b5665 100644 --- a/gcloud/logging/write +++ b/gcloud/logging/write @@ -3,6 +3,8 @@ NAME SYNOPSIS gcloud logging write LOG_NAME MESSAGE + [--monitored-resource-labels=[KEY=VALUE, ...,...]] + [--monitored-resource-type=MONITORED_RESOURCE_TYPE; default="global"] [--payload-type=PAYLOAD_TYPE; default="text"] [--severity=SEVERITY; default="DEFAULT"] [--billing-account=BILLING_ACCOUNT_ID | --folder=FOLDER_ID @@ -11,10 +13,8 @@ SYNOPSIS DESCRIPTION Write a log entry. If the destination log does not exist, it will be - created. All log entries written with this command are considered to be - from the "custom.googleapis.com" v1 service or the "global" v2 resource - type. The log entries will be listed in the Logs Explorer under that - service or resource type. + created. By default, all log entries written with this command are written + with the "global" resource type. gcloud logging write should be used for simple testing purposes. Check Cloud Logging agent for a proper way to send log entries: @@ -34,6 +34,12 @@ EXAMPLES $ gcloud logging write LOG_NAME '{"key": "value"}' \ --payload-type=json + To create a log entry with a custom resource type, run: + + $ gcloud logging write LOG_NAME "A simple entry" \ + --monitored-resource-type=gce_instance \ + --monitored-resource-labels=zone=us-centra1-a,instance_id=1234 + POSITIONAL ARGUMENTS LOG_NAME Name of the log where the log entry will be written. @@ -43,6 +49,12 @@ POSITIONAL ARGUMENTS --payload-type=json. FLAGS + --monitored-resource-labels=[KEY=VALUE, ...,...] + Monitored Resource labels to add to the payload + + --monitored-resource-type=MONITORED_RESOURCE_TYPE; default="global" + Monitored Resource type to add to the payload + --payload-type=PAYLOAD_TYPE; default="text" Type of the log entry payload. PAYLOAD_TYPE must be one of: text, json. diff --git a/gcloud/managed-kafka/clusters/create b/gcloud/managed-kafka/clusters/create index c700320bc..e5b50adb9 100644 --- a/gcloud/managed-kafka/clusters/create +++ b/gcloud/managed-kafka/clusters/create @@ -64,10 +64,11 @@ REQUIRED FLAGS --subnets=[SUBNETS,...] VPC subnets from which the cluster is accessible. Both broker and bootstrap server IP addresses and DNS entries are automatically created - in each subnet. The subnet must be located in the same region as the - cluster. The project may differ. A minimum of 1 subnet is required. A - maximum of 10 subnets can be specified. Use commas to separate multiple - subnets. The name of the subnet must be in the format + in each subnet. Only one subnet per network is allowed, and the subnet + must be located in the same region as the cluster. The project may + differ. A minimum of 1 subnet is required. A maximum of 10 subnets can + be specified. Use commas to separate multiple subnets. The name of the + subnet must be in the format projects/PROJECT_ID/regions/REGION/subnetworks/SUBNET. OPTIONAL FLAGS diff --git a/gcloud/managed-kafka/clusters/update b/gcloud/managed-kafka/clusters/update index 46dcdc4c7..b7043ec6b 100644 --- a/gcloud/managed-kafka/clusters/update +++ b/gcloud/managed-kafka/clusters/update @@ -77,11 +77,12 @@ REQUIRED FLAGS --subnets=[SUBNETS,...] VPC subnets from which the cluster is accessible. Both broker and bootstrap server IP addresses and DNS entries are automatically - created in each subnet. The subnet must be located in the same region - as the cluster. The project may differ. A minimum of 1 subnet is - required. A maximum of 10 subnets can be specified. Use commas to - separate multiple subnets. The name of the subnet must be in the - format projects/PROJECT_ID/regions/REGION/subnetworks/SUBNET. + created in each subnet. Only one subnet per network is allowed, and + the subnet must be located in the same region as the cluster. The + project may differ. A minimum of 1 subnet is required. A maximum of + 10 subnets can be specified. Use commas to separate multiple subnets. + The name of the subnet must be in the format + projects/PROJECT_ID/regions/REGION/subnetworks/SUBNET. OPTIONAL FLAGS --async diff --git a/gcloud/migration/vms/help b/gcloud/migration/vms/help index f6bfddaec..6a44afc4c 100644 --- a/gcloud/migration/vms/help +++ b/gcloud/migration/vms/help @@ -27,6 +27,9 @@ GROUPS Imports machine images to Google Compute Engine from Google Cloud Storage. + target-projects + Manage Target Projects. + NOTES This variant is also available: diff --git a/gcloud/migration/vms/target-projects/help b/gcloud/migration/vms/target-projects/help new file mode 100644 index 000000000..d6d74be7f --- /dev/null +++ b/gcloud/migration/vms/target-projects/help @@ -0,0 +1,29 @@ +NAME + gcloud migration vms target-projects - manage Target Projects + +SYNOPSIS + gcloud migration vms target-projects COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + target-projects sub-group is used to manage Target Project resources of the + Migrate to Virtual Machines service. Target projects are defined for each + customer project in the global location. A Target Project could be used as + the target project of various migration commands. VM Migration API must be + enabled in your project. + +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 Target Projects. + +NOTES + This variant is also available: + + $ gcloud alpha migration vms target-projects + diff --git a/gcloud/migration/vms/target-projects/list b/gcloud/migration/vms/target-projects/list new file mode 100644 index 000000000..2bc6f2be4 --- /dev/null +++ b/gcloud/migration/vms/target-projects/list @@ -0,0 +1,67 @@ +NAME + gcloud migration vms target-projects list - list Target Projects + +SYNOPSIS + gcloud migration vms target-projects list [--filter=EXPRESSION] + [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + gcloud migration vms target-projects list lists Target Project resources, + which are required for setting the target project for migration. Target + projects are defined for each customer project in the global location. To + use this command, you must enable VM Migration API in your project. + +EXAMPLES + To list the Target Project resources in the global location in the default + project, run: $ gcloud migration vms target-projects list + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + + --uri + Print a list of resource URIs instead of the default output, and change + the command output to a list of URIs. If this flag is used with + --format, the formatting is applied on this URI list. To display URIs + alongside other keys instead, use the uri() transform. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the vmmigration/v1 API. The full documentation for this + API can be found at: https://cloud.google.com/migrate/virtual-machines + +NOTES + This variant is also available: + + $ gcloud alpha migration vms target-projects list + diff --git a/gcloud/network-connectivity/internal-ranges/create b/gcloud/network-connectivity/internal-ranges/create index 7bcc858c8..b6315343b 100644 --- a/gcloud/network-connectivity/internal-ranges/create +++ b/gcloud/network-connectivity/internal-ranges/create @@ -6,7 +6,8 @@ SYNOPSIS gcloud network-connectivity internal-ranges create (INTERNAL_RANGE : --region=REGION) --network=NETWORK (--ip-cidr-range=IP_CIDR_RANGE | [--prefix-length=PREFIX_LENGTH - : --target-cidr-range=[TARGET_CIDR_RANGE,...]]) [--async] + : --exclude-cidr-ranges=[EXCLUDE_CIDR_RANGES,...] + --target-cidr-range=[TARGET_CIDR_RANGE,...]]) [--async] [--description=DESCRIPTION] [--labels=[KEY=VALUE,...]] [--overlaps=[OVERLAPS,...]] [--peering=PEERING; default="for-self"] [--usage=USAGE; default="for-vpc"] @@ -88,6 +89,12 @@ REQUIRED FLAGS This flag argument must be specified if any of the other arguments in this group are specified. + --exclude-cidr-ranges=[EXCLUDE_CIDR_RANGES,...] + A list of CIDR ranges to exclude from the search for a free range. + This can be used to exclude specific ranges that are already intended + to have some other use. This option can only be used if prefix length + is also set. + --target-cidr-range=[TARGET_CIDR_RANGE,...] Can be set to narrow down or pick a different address space while searching for a free range. If not set, defaults to the "10.0.0.0/8" diff --git a/gcloud/network-security/server-tls-policies/list b/gcloud/network-security/server-tls-policies/list index cfa1c8b2b..cadf405c1 100644 --- a/gcloud/network-security/server-tls-policies/list +++ b/gcloud/network-security/server-tls-policies/list @@ -2,37 +2,37 @@ NAME gcloud network-security server-tls-policies list - list ServerTlsPolicies SYNOPSIS - gcloud network-security server-tls-policies list --location=LOCATION + gcloud network-security server-tls-policies list [--location=LOCATION] [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - List all ServerTlsPolicies in the specified location of the current - project. + List all ServerTlsPolicies in the current project. EXAMPLES To list ServerTlsPolicies in the current project, run: - $ gcloud network-security server-tls-policies list --location=global + $ gcloud network-security server-tls-policies list -REQUIRED FLAGS - Location resource - The project of the ServerTlsPolicies to display. This +FLAGS + Location resource - The location of the ServerTlsPolicies 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; + ◆ if left empty, will use the wildcard '-' to list all locations with a + fully specified name; ◆ provide the argument --project on the command line; ◆ set the property core/project. - 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. + ▸ provide the argument --location on the command line; + ▸ if left empty, will use the wildcard '-' to list all locations. LIST COMMAND FLAGS --filter=EXPRESSION diff --git a/gcloud/oracle-database/autonomous-databases/create b/gcloud/oracle-database/autonomous-databases/create index 5fa1f4063..ef47f56d7 100644 --- a/gcloud/oracle-database/autonomous-databases/create +++ b/gcloud/oracle-database/autonomous-databases/create @@ -3,14 +3,17 @@ NAME AutonomousDatabase SYNOPSIS - gcloud oracle-database autonomous-databases create - (AUTONOMOUS_DATABASE : --location=LOCATION) + gcloud oracle-database autonomous-databases create AUTONOMOUS_DATABASE [--admin-password=ADMIN_PASSWORD] [--async] [--cidr=CIDR] [--database=DATABASE] [--display-name=DISPLAY_NAME] - [--labels=[LABELS,...]] [--network=NETWORK] [--request-id=REQUEST_ID] - [--properties-db-workload=PROPERTIES_DB_WORKLOAD + [--labels=[LABELS,...]] [--location=LOCATION] [--network=NETWORK] + [--request-id=REQUEST_ID] + [[--properties-db-workload=PROPERTIES_DB_WORKLOAD --properties-license-type=PROPERTIES_LICENSE_TYPE - : --properties-backup-retention-period-days=PROPERTIES_BACKUP_RETENTION_PERIOD_DAYS --properties-character-set=PROPERTIES_CHARACTER_SET --properties-compute-count=PROPERTIES_COMPUTE_COUNT --properties-cpu-core-count=PROPERTIES_CPU_CORE_COUNT --properties-customer-contacts=[email=EMAIL] --properties-data-storage-size-gb=PROPERTIES_DATA_STORAGE_SIZE_GB --properties-data-storage-size-tb=PROPERTIES_DATA_STORAGE_SIZE_TB --properties-db-edition=PROPERTIES_DB_EDITION --properties-db-version=PROPERTIES_DB_VERSION --properties-is-auto-scaling-enabled --properties-is-storage-auto-scaling-enabled --properties-maintenance-schedule-type=PROPERTIES_MAINTENANCE_SCHEDULE_TYPE --properties-mtls-connection-required --properties-n-character-set=PROPERTIES_N_CHARACTER_SET --properties-private-endpoint-ip=PROPERTIES_PRIVATE_ENDPOINT_IP --properties-private-endpoint-label=PROPERTIES_PRIVATE_ENDPOINT_LABEL --properties-secret-id=PROPERTIES_SECRET_ID --properties-vault-id=PROPERTIES_VAULT_ID] + : --properties-allowlisted-ips=[PROPERTIES_ALLOWLISTED_IPS,...] + --properties-backup-retention-period-days=PROPERTIES_BACKUP_RETENTION_PERIOD_DAYS --properties-character-set=PROPERTIES_CHARACTER_SET --properties-compute-count=PROPERTIES_COMPUTE_COUNT --properties-cpu-core-count=PROPERTIES_CPU_CORE_COUNT --properties-customer-contacts=[email=EMAIL] --properties-data-storage-size-gb=PROPERTIES_DATA_STORAGE_SIZE_GB --properties-data-storage-size-tb=PROPERTIES_DATA_STORAGE_SIZE_TB --properties-db-edition=PROPERTIES_DB_EDITION --properties-db-version=PROPERTIES_DB_VERSION --properties-is-auto-scaling-enabled --properties-is-storage-auto-scaling-enabled --properties-maintenance-schedule-type=PROPERTIES_MAINTENANCE_SCHEDULE_TYPE --properties-mtls-connection-required --properties-n-character-set=PROPERTIES_N_CHARACTER_SET --properties-private-endpoint-ip=PROPERTIES_PRIVATE_ENDPOINT_IP --properties-private-endpoint-label=PROPERTIES_PRIVATE_ENDPOINT_LABEL --properties-secret-id=PROPERTIES_SECRET_ID --properties-vault-id=PROPERTIES_VAULT_ID]] + [--source-config-automatic-backups-replication-enabled + --source-config-autonomous-database=SOURCE_CONFIG_AUTONOMOUS_DATABASE] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -37,9 +40,8 @@ POSITIONAL ARGUMENTS AutonomousDatabase resource - Identifier. The name of the Autonomous Database resource in the following format: projects/{project}/locations/{region}/autonomousDatabases/{autonomous_database} - 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. + 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 autonomous_database on the command line with a @@ -47,6 +49,11 @@ POSITIONAL ARGUMENTS ◆ provide the argument --project on the command line; ◆ set the property core/project. + To set the location attribute: + ◆ provide the argument autonomous_database on the command line with a + fully specified name; + ◆ provide the argument --location on the command line. + This must be specified. AUTONOMOUS_DATABASE @@ -56,17 +63,6 @@ POSITIONAL ARGUMENTS To set the autonomous_database attribute: ▸ provide the argument autonomous_database on the command line. - This positional argument must be specified if any of the other - arguments in this group are specified. - - --location=LOCATION - The location id of the autonomousDatabase resource. - - To set the location attribute: - ▸ provide the argument autonomous_database on the command line with - a fully specified name; - ▸ provide the argument --location on the command line. - FLAGS --admin-password=ADMIN_PASSWORD The password for the default ADMIN user. @@ -110,6 +106,11 @@ FLAGS --labels=path_to_file.(yaml|json) + --location=LOCATION + For resources [autonomousDatabase], provides fallback value for + resource location attribute. When the resource's full URI path is not + provided, location will fallback to this flag value. + Network resource - The name of the VPC network used by the Autonomous Database in the following format: projects/{project}/global/networks/{network} This represents a Cloud @@ -169,6 +170,9 @@ FLAGS This flag argument must be specified if any of the other arguments in this group are specified. + --properties-allowlisted-ips=[PROPERTIES_ALLOWLISTED_IPS,...] + The list of allowlisted IP addresses for the Autonomous Database. + --properties-backup-retention-period-days=PROPERTIES_BACKUP_RETENTION_PERIOD_DAYS The retention period for the Autonomous Database. This field is specified in days, can range from 1 day to 60 days, and has a default @@ -260,6 +264,36 @@ FLAGS --properties-vault-id=PROPERTIES_VAULT_ID The ID of the Oracle Cloud Infrastructure vault. + The source configuration for the standby Autonomnous Database. + + --source-config-automatic-backups-replication-enabled + This field specifies if the replication of automatic backups is + enabled when creating a Data Guard. + + AutonomousDatabase resource - The name of the primary Autonomous + Database that is used to create a Peer Autonomous Database from a + source. 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 --source-config-autonomous-database on the + command line with a fully specified name; + ▸ provide the argument --project on the command line; + ▸ set the property core/project. + + To set the location attribute: + ▸ provide the argument --source-config-autonomous-database on the + command line with a fully specified name; + ▸ provide the argument --location on the command line. + + --source-config-autonomous-database=SOURCE_CONFIG_AUTONOMOUS_DATABASE + ID of the autonomousDatabase or fully qualified identifier for the + autonomousDatabase. + + To set the autonomous-database attribute: + ▫ provide the argument --source-config-autonomous-database on the + command line. + GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, diff --git a/gcloud/oracle-database/autonomous-databases/help b/gcloud/oracle-database/autonomous-databases/help index e1762290f..a65c79131 100644 --- a/gcloud/oracle-database/autonomous-databases/help +++ b/gcloud/oracle-database/autonomous-databases/help @@ -31,5 +31,17 @@ COMMANDS list List all AutonomousDatabases. + restart + Restarts an AutonomousDatabase. + restore Restore an AutonomousDatabase. + + start + Starts an AutonomousDatabase. + + stop + Stops an AutonomousDatabase. + + switchover + Switchovers an AutonomousDatabase to a new primary. diff --git a/gcloud/oracle-database/autonomous-databases/restart b/gcloud/oracle-database/autonomous-databases/restart new file mode 100644 index 000000000..3499a3f99 --- /dev/null +++ b/gcloud/oracle-database/autonomous-databases/restart @@ -0,0 +1,69 @@ +NAME + gcloud oracle-database autonomous-databases restart - restarts an + AutonomousDatabase + +SYNOPSIS + gcloud oracle-database autonomous-databases restart + (AUTONOMOUS_DATABASE : --location=LOCATION) [--async] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Restarts an AutonomousDatabase which is in Running state. + +EXAMPLES + To restart an AutonomousDatabase with id my-instance in the location + us-east4, run: + + $ gcloud oracle-database autonomous-databases restart my-instance \ + --location=us-east4 + +POSITIONAL ARGUMENTS + AutonomousDatabase resource - The name of the Autonomous Database in the + following format: + projects/{project}/locations/{location}/autonomousDatabases/{autonomous_database}. + 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 autonomous_database 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. + + AUTONOMOUS_DATABASE + ID of the autonomousDatabase or fully qualified identifier for the + autonomousDatabase. + + To set the autonomous_database attribute: + ▸ provide the argument autonomous_database on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + The location id of the autonomousDatabase resource. + + To set the location attribute: + ▸ provide the argument autonomous_database 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 oracledatabase/v1 API. The full documentation for + this API can be found at: https://cloud.google.com/oracle/database/docs diff --git a/gcloud/oracle-database/autonomous-databases/start b/gcloud/oracle-database/autonomous-databases/start new file mode 100644 index 000000000..03aea8222 --- /dev/null +++ b/gcloud/oracle-database/autonomous-databases/start @@ -0,0 +1,69 @@ +NAME + gcloud oracle-database autonomous-databases start - starts an + AutonomousDatabase + +SYNOPSIS + gcloud oracle-database autonomous-databases start + (AUTONOMOUS_DATABASE : --location=LOCATION) [--async] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Starts an AutonomousDatabase which is in Stopped state. + +EXAMPLES + To start an AutonomousDatabase with id my-instance in the location + us-east4, run: + + $ gcloud oracle-database autonomous-databases start my-instance \ + --location=us-east4 + +POSITIONAL ARGUMENTS + AutonomousDatabase resource - The name of the Autonomous Database in the + following format: + projects/{project}/locations/{location}/autonomousDatabases/{autonomous_database}. + 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 autonomous_database 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. + + AUTONOMOUS_DATABASE + ID of the autonomousDatabase or fully qualified identifier for the + autonomousDatabase. + + To set the autonomous_database attribute: + ▸ provide the argument autonomous_database on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + The location id of the autonomousDatabase resource. + + To set the location attribute: + ▸ provide the argument autonomous_database 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 oracledatabase/v1 API. The full documentation for + this API can be found at: https://cloud.google.com/oracle/database/docs diff --git a/gcloud/oracle-database/autonomous-databases/stop b/gcloud/oracle-database/autonomous-databases/stop new file mode 100644 index 000000000..af33d4248 --- /dev/null +++ b/gcloud/oracle-database/autonomous-databases/stop @@ -0,0 +1,69 @@ +NAME + gcloud oracle-database autonomous-databases stop - stops an + AutonomousDatabase + +SYNOPSIS + gcloud oracle-database autonomous-databases stop + (AUTONOMOUS_DATABASE : --location=LOCATION) [--async] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Stops an AutonomousDatabase which is in Running state. + +EXAMPLES + To stop an AutonomousDatabase with id my-instance in the location us-east4, + run: + + $ gcloud oracle-database autonomous-databases stop my-instance \ + --location=us-east4 + +POSITIONAL ARGUMENTS + AutonomousDatabase resource - The name of the Autonomous Database in the + following format: + projects/{project}/locations/{location}/autonomousDatabases/{autonomous_database}. + 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 autonomous_database 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. + + AUTONOMOUS_DATABASE + ID of the autonomousDatabase or fully qualified identifier for the + autonomousDatabase. + + To set the autonomous_database attribute: + ▸ provide the argument autonomous_database on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + The location id of the autonomousDatabase resource. + + To set the location attribute: + ▸ provide the argument autonomous_database 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 oracledatabase/v1 API. The full documentation for + this API can be found at: https://cloud.google.com/oracle/database/docs diff --git a/gcloud/oracle-database/autonomous-databases/switchover b/gcloud/oracle-database/autonomous-databases/switchover new file mode 100644 index 000000000..f21be6d46 --- /dev/null +++ b/gcloud/oracle-database/autonomous-databases/switchover @@ -0,0 +1,97 @@ +NAME + gcloud oracle-database autonomous-databases switchover - switchovers an + AutonomousDatabase to a new primary + +SYNOPSIS + gcloud oracle-database autonomous-databases switchover AUTONOMOUS_DATABASE + --peer-autonomous-database=PEER_AUTONOMOUS_DATABASE [--async] + [--location=LOCATION] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Switchovers an AutonomousDatabase from a standby database to a new primary. + +EXAMPLES + To switchover an AutonomousDatabase with id my-instance in the location + us-east4 with primary database name as + 'projects/project-id/locations/us-west3/autonomousDatabases/my-instance' + run: + + $ gcloud oracle-database autonomous-databases switchover \ + my-instance --location=us-east4 \ + --peer-autonomous-database=projects/project-id/locations/\ + us-west3/autonomousDatabases/my-instance + +POSITIONAL ARGUMENTS + AutonomousDatabase resource - The name of the Autonomous Database in the + following format: + projects/{project}/locations/{location}/autonomousDatabases/{autonomous_database}. + 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 autonomous_database on the command line with a + fully specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + To set the location attribute: + ◆ provide the argument autonomous_database on the command line with a + fully specified name; + ◆ provide the argument --location on the command line. + + This must be specified. + + AUTONOMOUS_DATABASE + ID of the autonomousDatabase or fully qualified identifier for the + autonomousDatabase. + + To set the autonomous_database attribute: + ▸ provide the argument autonomous_database on the command line. + +REQUIRED FLAGS + AutonomousDatabase resource - The peer database name to switch over to. + 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 --peer-autonomous-database on the command line + with a fully specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + To set the location attribute: + ◆ provide the argument --peer-autonomous-database on the command line + with a fully specified name; + ◆ provide the argument --location on the command line. + + This must be specified. + + --peer-autonomous-database=PEER_AUTONOMOUS_DATABASE + ID of the autonomousDatabase or fully qualified identifier for the + autonomousDatabase. + + To set the autonomous-database attribute: + ▸ provide the argument --peer-autonomous-database on the command + line. + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --location=LOCATION + For resources [autonomousDatabase], provides fallback value for + resource location attribute. When the resource's full URI path is not + provided, location will fallback to this flag value. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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 oracledatabase/v1 API. The full documentation for + this API can be found at: https://cloud.google.com/oracle/database/docs diff --git a/gcloud/scc/findings/list-marks b/gcloud/scc/findings/list-marks index 4843efd25..d2ddaa6f1 100644 --- a/gcloud/scc/findings/list-marks +++ b/gcloud/scc/findings/list-marks @@ -2,11 +2,12 @@ NAME gcloud scc findings list-marks - list a finding's security marks SYNOPSIS - gcloud scc findings list-marks - (FINDING : --organization=ORGANIZATION --source=SOURCE) + gcloud scc findings list-marks FINDING [--location=LOCATION; default="global"] [--page-token=PAGE_TOKEN] - [--read-time=READ_TIME] [--filter=EXPRESSION] [--limit=LIMIT] - [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [GCLOUD_WIDE_FLAG ...] + [--read-time=READ_TIME] [--source=SOURCE; default="-"] + [--folder=FOLDER | --organization=ORGANIZATION | --project=PROJECT] + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION List a finding's security marks. @@ -36,45 +37,8 @@ EXAMPLES --organization=123456 --source=5678 --location=eu POSITIONAL ARGUMENTS - Finding resource - The finding to be used for the SCC (Security Command - Center) command. The arguments in this group can be used to specify the - attributes of this resource. - - This must be specified. - - FINDING - ID of the finding or fully qualified identifier for the finding. - - To set the finding attribute: - ▸ provide the argument finding on the command line. - - This positional argument must be specified if any of the other - arguments in this group are specified. - - --organization=ORGANIZATION - (Optional) If the full resource name isn't provided e.g. - organizations/123, then provide the organization id which is the - suffix of the organization. Example: organizations/123, the id is - 123. - - To set the organization attribute: - ▸ provide the argument finding on the command line with a fully - specified name; - ▸ provide the argument --organization on the command line; - ▸ Set the organization property in configuration using gcloud - config set scc/organization if it is not specified in command - line.. - - --source=SOURCE - (Optional) If the full resource name isn't provided e.g. - organizations/123/sources/456, then provide the source id which is - the suffix of the source. Example: organizations/123/sources/456, the - id is 456. - - To set the source attribute: - ▸ provide the argument finding on the command line with a fully - specified name; - ▸ provide the argument --source on the command line. + FINDING + ID of the finding or fully qualified identifier for the finding. FLAGS --location=LOCATION; default="global" @@ -104,6 +68,20 @@ FLAGS (https://cloud.google.com/security-command-center/docs/release-notes#April_15_2024) on the SCC release notes page. + --source=SOURCE; default="-" + Source id. Defaults to all sources. + + At most one of these can be specified: + + --folder=FOLDER + The folder ID (e.g., 456) that contains the finding. + + --organization=ORGANIZATION + The organization ID (e.g., 123) that contains the finding. + + --project=PROJECT + The project ID (e.g., example-project) that contains the finding. + LIST COMMAND FLAGS --filter=EXPRESSION Apply a Boolean filter EXPRESSION to each resource item to be listed. diff --git a/gcloud/scc/findings/update b/gcloud/scc/findings/update index c02f25d2e..9ce63335e 100644 --- a/gcloud/scc/findings/update +++ b/gcloud/scc/findings/update @@ -2,12 +2,12 @@ NAME gcloud scc findings update - update a Security Command Center finding SYNOPSIS - gcloud scc findings update - (FINDING : --organization=ORGANIZATION --source=SOURCE) - [--event-time=EVENT_TIME] [--external-uri=EXTERNAL_URI] - [--location=LOCATION; default="global"] - [--source-properties=[KEY=VALUE,...]] [--state=STATE] - [--update-mask=UPDATE_MASK] [GCLOUD_WIDE_FLAG ...] + gcloud scc findings update FINDING [--event-time=EVENT_TIME] + [--external-uri=EXTERNAL_URI] [--location=LOCATION; default="global"] + [--source=SOURCE; default="-"] [--source-properties=[KEY=VALUE,...]] + [--state=STATE] [--update-mask=UPDATE_MASK] + [--folder=FOLDER | --organization=ORGANIZATION | --project=PROJECT] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION Update a Security Command Center finding. @@ -49,45 +49,8 @@ EXAMPLES --source=5678 --state=INACTIVE --location=eu POSITIONAL ARGUMENTS - Finding resource - The finding to be used for the SCC (Security Command - Center) command. The arguments in this group can be used to specify the - attributes of this resource. - - This must be specified. - - FINDING - ID of the finding or fully qualified identifier for the finding. - - To set the finding attribute: - ▸ provide the argument finding on the command line. - - This positional argument must be specified if any of the other - arguments in this group are specified. - - --organization=ORGANIZATION - (Optional) If the full resource name isn't provided e.g. - organizations/123, then provide the organization id which is the - suffix of the organization. Example: organizations/123, the id is - 123. - - To set the organization attribute: - ▸ provide the argument finding on the command line with a fully - specified name; - ▸ provide the argument --organization on the command line; - ▸ Set the organization property in configuration using gcloud - config set scc/organization if it is not specified in command - line.. - - --source=SOURCE - (Optional) If the full resource name isn't provided e.g. - organizations/123/sources/456, then provide the source id which is - the suffix of the source. Example: organizations/123/sources/456, the - id is 456. - - To set the source attribute: - ▸ provide the argument finding on the command line with a fully - specified name; - ▸ provide the argument --source on the command line. + FINDING + ID of the finding or fully qualified identifier for the finding. FLAGS --event-time=EVENT_TIME @@ -114,6 +77,9 @@ FLAGS location that is specified when data residency controls are enabled for Security Command Center. + --source=SOURCE; default="-" + Source id. Defaults to all sources. + --source-properties=[KEY=VALUE,...] Source specific properties. These properties are managed by the source that writes the finding. The key names in the source_properties map @@ -140,6 +106,17 @@ FLAGS State can be toggled from ACTIVE to INACTIVE and vice-versa but it cannot be deleted. + At most one of these can be specified: + + --folder=FOLDER + The folder ID (e.g., 456) that contains the finding. + + --organization=ORGANIZATION + The organization ID (e.g., 123) that contains the finding. + + --project=PROJECT + The project ID (e.g., example-project) that contains the finding. + 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/scc/findings/update-marks b/gcloud/scc/findings/update-marks index a6299b686..b4b1004ba 100644 --- a/gcloud/scc/findings/update-marks +++ b/gcloud/scc/findings/update-marks @@ -3,11 +3,12 @@ NAME security marks SYNOPSIS - gcloud scc findings update-marks - (FINDING : --organization=ORGANIZATION --source=SOURCE) + gcloud scc findings update-marks FINDING [--location=LOCATION; default="global"] - [--security-marks=[KEY=VALUE,...]] [--start-time=START_TIME] - [--update-mask=UPDATE_MASK] [GCLOUD_WIDE_FLAG ...] + [--security-marks=[KEY=VALUE,...]] [--source=SOURCE; default="-"] + [--start-time=START_TIME] [--update-mask=UPDATE_MASK] + [--folder=FOLDER | --organization=ORGANIZATION | --project=PROJECT] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION Update Security Command Center finding's security marks. @@ -53,45 +54,8 @@ EXAMPLES --security-marks="key1=v1,key2=v2" --location=eu POSITIONAL ARGUMENTS - Finding resource - The finding to be used for the SCC (Security Command - Center) command. The arguments in this group can be used to specify the - attributes of this resource. - - This must be specified. - - FINDING - ID of the finding or fully qualified identifier for the finding. - - To set the finding attribute: - ▸ provide the argument finding on the command line. - - This positional argument must be specified if any of the other - arguments in this group are specified. - - --organization=ORGANIZATION - (Optional) If the full resource name isn't provided e.g. - organizations/123, then provide the organization id which is the - suffix of the organization. Example: organizations/123, the id is - 123. - - To set the organization attribute: - ▸ provide the argument finding on the command line with a fully - specified name; - ▸ provide the argument --organization on the command line; - ▸ Set the organization property in configuration using gcloud - config set scc/organization if it is not specified in command - line.. - - --source=SOURCE - (Optional) If the full resource name isn't provided e.g. - organizations/123/sources/456, then provide the source id which is - the suffix of the source. Example: organizations/123/sources/456, the - id is 456. - - To set the source attribute: - ▸ provide the argument finding on the command line with a fully - specified name; - ▸ provide the argument --source on the command line. + FINDING + ID of the finding or fully qualified identifier for the finding. FLAGS --location=LOCATION; default="global" @@ -110,6 +74,9 @@ FLAGS key=value pair separated by comma (,). For example: --security-marks="key1=val1,key2=val2". + --source=SOURCE; default="-" + Source id. Defaults to all sources. + --start-time=START_TIME Time at which the updated SecurityMarks take effect. See $ gcloud topic datetimes for information on supported time formats. @@ -121,6 +88,17 @@ FLAGS marks for the given finding either skip the update-mask flag or provide an empty value (--update-mask '') for it. + At most one of these can be specified: + + --folder=FOLDER + The folder ID (e.g., 456) that contains the finding. + + --organization=ORGANIZATION + The organization ID (e.g., 123) that contains the finding. + + --project=PROJECT + The project ID (e.g., example-project) that contains the finding. + 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/sql/backups/restore b/gcloud/sql/backups/restore index 439399918..6911a3cc4 100644 --- a/gcloud/sql/backups/restore +++ b/gcloud/sql/backups/restore @@ -14,7 +14,6 @@ SYNOPSIS [--backup-project=BACKUP_PROJECT] [--backup-start-time=BACKUP_START_TIME] [--collation=COLLATION] [--connector-enforcement=CONNECTOR_ENFORCEMENT] [--cpu=CPU] - [--database-flags=FLAG=VALUE,[FLAG=VALUE,...]] [--database-version=DATABASE_VERSION] [--[no-]deletion-protection] [--deny-maintenance-period-end-date=DENY_MAINTENANCE_PERIOD_END_DATE] [--deny-maintenance-period-start-date=DENY_MAINTENANCE_PERIOD_START_DATE] @@ -163,14 +162,6 @@ OPTIONAL FLAGS machine. Both --cpu and --memory must be specified if a custom machine type is desired, and the --tier flag must be omitted. - --database-flags=FLAG=VALUE,[FLAG=VALUE,...] - Comma-separated list of database flags to set on the instance. Use an - equals sign to separate flag name and value. Flags without values, like - skip_grant_tables, can be written out without a value after, e.g., - skip_grant_tables=. Use on/off for booleans. View the Instance Resource - API for allowed flags. (e.g., --database-flags - max_allowed_packet=55555,skip_grant_tables=,log_output=1) - --database-version=DATABASE_VERSION The database engine type and versions. If left unspecified, no changes occur. See the list of database versions at diff --git a/gcloud/transfer/jobs/create b/gcloud/transfer/jobs/create index d9d053be0..dffd6ec45 100644 --- a/gcloud/transfer/jobs/create +++ b/gcloud/transfer/jobs/create @@ -34,7 +34,8 @@ SYNOPSIS --source-auth-method=SOURCE_AUTH_METHOD --source-list-api=SOURCE_LIST_API --source-network-protocol=SOURCE_NETWORK_PROTOCOL - --source-request-model=SOURCE_REQUEST_MODEL] [--no-async] + --source-request-model=SOURCE_REQUEST_MODEL + --s3-cloudfront-domain=S3_CLOUDFRONT_DOMAIN] [--no-async] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -423,6 +424,13 @@ FLAGS virtual-hosted style. SOURCE_REQUEST_MODEL must be one of: PATH_STYLE, VIRTUAL_HOSTED_STYLE. + --s3-cloudfront-domain=S3_CLOUDFRONT_DOMAIN + For transfers from S3, optionally route egress traffic through a + CloudFront instance. Supply the endpoint of the CloudFront instance: + https://example.cloudfront.net. See documentation + (https://cloud.google.com/storage-transfer/docs/s3-cloudfront) for + more information. + EXECUTION OPTIONS --no-async diff --git a/gcloud/transfer/jobs/update b/gcloud/transfer/jobs/update index 3b20eafb6..e1949dda1 100644 --- a/gcloud/transfer/jobs/update +++ b/gcloud/transfer/jobs/update @@ -45,10 +45,11 @@ SYNOPSIS --source-auth-method=SOURCE_AUTH_METHOD --source-list-api=SOURCE_LIST_API --source-network-protocol=SOURCE_NETWORK_PROTOCOL - --source-request-model=SOURCE_REQUEST_MODEL --clear-source-endpoint + --source-request-model=SOURCE_REQUEST_MODEL + --s3-cloudfront-domain=S3_CLOUDFRONT_DOMAIN --clear-source-endpoint --clear-source-signing-region --clear-source-auth-method - --clear-source-list-api - --clear-source-network-protocol --clear-source-request-model] + --clear-source-list-api --clear-source-network-protocol + --clear-source-request-model --clear-s3-cloudfront-domain] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -496,6 +497,13 @@ FLAGS virtual-hosted style. SOURCE_REQUEST_MODEL must be one of: PATH_STYLE, VIRTUAL_HOSTED_STYLE. + --s3-cloudfront-domain=S3_CLOUDFRONT_DOMAIN + For transfers from S3, optionally route egress traffic through a + CloudFront instance. Supply the endpoint of the CloudFront instance: + https://example.cloudfront.net. See documentation + (https://cloud.google.com/storage-transfer/docs/s3-cloudfront) for + more information. + --clear-source-endpoint Removes source endpoint. @@ -514,6 +522,9 @@ FLAGS --clear-source-request-model Removes source request model. + --clear-s3-cloudfront-domain + Removes S3 CloudFront domain. + 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/workbench/instances/create b/gcloud/workbench/instances/create index 18182e982..43b17f31e 100644 --- a/gcloud/workbench/instances/create +++ b/gcloud/workbench/instances/create @@ -5,7 +5,8 @@ SYNOPSIS gcloud workbench instances create (INSTANCE : --location=LOCATION) [--async] [--disable-proxy-access] [--enable-third-party-identity] [--instance-owners=INSTANCE_OWNERS] [--labels=[KEY=VALUE,...]] - [--disable-public-ip --enable-ip-forwarding + [--confidential-compute-type=CONFIDENTIAL_COMPUTE_TYPE + --disable-public-ip --enable-ip-forwarding --machine-type=MACHINE_TYPE; default="n1-standard-4" --metadata=[KEY=VALUE,...] --min-cpu-platform=MIN_CPU_PLATFORM --service-account-email=SERVICE_ACCOUNT_EMAIL --tags=[TAGS,...] @@ -129,6 +130,10 @@ FLAGS Gce Setup for the instance + --confidential-compute-type=CONFIDENTIAL_COMPUTE_TYPE + String. VM instance with CC (Confidential Compute) of type. Supported + values: SEV. + --disable-public-ip If specified, no public IP will be assigned to this instance.