From 39dc808917c3e4787d5a2fe03f7b224e042d9623 Mon Sep 17 00:00:00 2001 From: Automated Date: Wed, 13 May 2026 13:12:23 +0000 Subject: [PATCH] gcloud: Wed May 13 13:12:23 UTC 2026 --- gcloud/_version | 12 +- .../cloud-bindings/create | 8 +- .../cloud-bindings/update | 3 +- gcloud/ai/model-garden/models/deploy | 7 +- gcloud/alloydb/clusters/create | 7 + gcloud/alloydb/instances/create | 43 +- gcloud/alloydb/instances/update | 43 +- gcloud/alloydb/users/create | 3 + .../cloud-bindings/create | 86 ++- .../cloud-bindings/update | 51 +- .../connectors}/add-iam-policy-binding | 59 ++- gcloud/alpha/agent-identity/connectors/create | 5 +- .../connectors}/get-iam-policy | 56 +- gcloud/alpha/agent-identity/connectors/help | 15 + .../connectors}/remove-iam-policy-binding | 57 +- .../connectors}/set-iam-policy | 51 +- .../connectors/test-iam-permissions | 73 +++ gcloud/alpha/agent-identity/help | 3 - gcloud/alpha/agent-identity/operations/help | 23 - gcloud/alpha/agent-registry/agents/help | 3 + gcloud/alpha/agent-registry/agents/search | 75 +++ gcloud/alpha/agent-registry/bindings/create | 144 +++++ gcloud/alpha/agent-registry/bindings/delete | 86 +++ gcloud/alpha/agent-registry/bindings/describe | 66 +++ .../agent-registry/bindings/fetch-available | 96 ++++ gcloud/alpha/agent-registry/bindings/help | 21 + gcloud/alpha/agent-registry/bindings/list | 87 +++ gcloud/alpha/agent-registry/bindings/update | 166 ++++++ gcloud/alpha/agent-registry/mcp-servers/help | 3 + .../alpha/agent-registry/mcp-servers/search | 76 +++ gcloud/alpha/ai/model-garden/models/deploy | 7 +- gcloud/alpha/alloydb/clusters/promote | 8 +- gcloud/alpha/alloydb/instances/create | 17 +- gcloud/alpha/alloydb/instances/update | 17 +- gcloud/alpha/alloydb/users/create | 3 + gcloud/alpha/api-registry/help | 2 +- gcloud/alpha/api-registry/mcp/disable | 6 +- gcloud/alpha/api-registry/mcp/enable | 6 +- gcloud/alpha/api-registry/mcp/help | 18 +- gcloud/alpha/api-registry/mcp/servers/help | 6 +- gcloud/alpha/api-registry/mcp/servers/list | 15 +- gcloud/alpha/api-registry/mcp/tools/help | 6 +- gcloud/alpha/api-registry/mcp/tools/list | 18 +- gcloud/alpha/app/migrate-to-run | 25 +- .../backup-dr/backup-plan-associations/create | 4 +- .../backup-dr/backup-plan-associations/delete | 4 +- .../backup-plan-associations/describe | 8 +- .../fetch-for-resource-type | 5 +- .../backup-dr/backup-plan-associations/help | 4 +- .../backup-dr/backup-plan-associations/list | 8 +- .../backup-plan-associations/trigger-backup | 4 +- .../backup-dr/backup-plan-associations/update | 4 +- .../backup-dr/backup-plan-revisions/describe | 8 +- .../backup-dr/backup-plan-revisions/help | 4 +- .../backup-dr/backup-plan-revisions/list | 8 +- gcloud/alpha/backup-dr/backup-plans/create | 23 +- gcloud/alpha/backup-dr/backup-plans/delete | 4 +- gcloud/alpha/backup-dr/backup-plans/describe | 8 +- gcloud/alpha/backup-dr/backup-plans/help | 4 +- gcloud/alpha/backup-dr/backup-plans/list | 8 +- gcloud/alpha/backup-dr/backup-plans/update | 22 +- gcloud/alpha/backup-dr/backup-vaults/create | 4 +- gcloud/alpha/backup-dr/backup-vaults/delete | 4 +- gcloud/alpha/backup-dr/backup-vaults/describe | 4 +- gcloud/alpha/backup-dr/backup-vaults/help | 4 +- gcloud/alpha/backup-dr/backup-vaults/list | 4 +- gcloud/alpha/backup-dr/backup-vaults/update | 4 +- gcloud/alpha/backup-dr/backups/delete | 4 +- gcloud/alpha/backup-dr/backups/describe | 8 +- .../backup-dr/backups/fetch-for-resource-type | 4 +- gcloud/alpha/backup-dr/backups/help | 4 +- gcloud/alpha/backup-dr/backups/list | 8 +- .../alpha/backup-dr/backups/restore/compute | 4 +- gcloud/alpha/backup-dr/backups/restore/disk | 4 +- gcloud/alpha/backup-dr/backups/restore/help | 4 +- gcloud/alpha/backup-dr/backups/update | 4 +- .../backup-dr/data-source-references/describe | 8 +- .../fetch-for-resource-type | 5 +- .../backup-dr/data-source-references/help | 4 +- .../backup-dr/data-source-references/list | 8 +- gcloud/alpha/backup-dr/data-sources/describe | 8 +- gcloud/alpha/backup-dr/data-sources/help | 4 +- gcloud/alpha/backup-dr/data-sources/list | 8 +- gcloud/alpha/backup-dr/locations/list | 4 +- .../backup-dr/management-servers/describe | 4 +- .../alpha/backup-dr/management-servers/list | 4 +- gcloud/alpha/backup-dr/operations/describe | 4 +- gcloud/alpha/backup-dr/operations/list | 4 +- .../backup-dr/resource-backup-config/help | 4 +- .../backup-dr/resource-backup-config/list | 4 +- gcloud/alpha/backup-dr/service-config/help | 4 +- gcloud/alpha/backup-dr/service-config/init | 4 +- gcloud/alpha/biglake/iceberg/catalogs/create | 47 +- gcloud/alpha/biglake/iceberg/catalogs/update | 33 +- gcloud/alpha/biglake/iceberg/tables/create | 4 +- gcloud/alpha/biglake/iceberg/tables/delete | 4 +- gcloud/alpha/biglake/iceberg/tables/describe | 4 +- .../biglake/iceberg/tables/get-iam-policy | 4 +- gcloud/alpha/biglake/iceberg/tables/help | 4 +- gcloud/alpha/biglake/iceberg/tables/list | 4 +- gcloud/alpha/biglake/iceberg/tables/register | 4 +- .../biglake/iceberg/tables/set-iam-policy | 4 +- gcloud/alpha/biglake/iceberg/tables/update | 4 +- gcloud/alpha/bigtable/app-profiles/create | 15 +- gcloud/alpha/bigtable/app-profiles/update | 13 +- gcloud/alpha/bigtable/help | 3 + gcloud/alpha/bigtable/instances/create | 14 +- gcloud/alpha/bigtable/instances/tables/create | 36 +- gcloud/alpha/bigtable/instances/tables/update | 48 +- gcloud/alpha/bigtable/instances/update | 12 +- gcloud/alpha/bigtable/memory-layers/describe | 64 +++ .../pipelines => bigtable/memory-layers}/help | 15 +- gcloud/alpha/bigtable/memory-layers/update | 82 +++ gcloud/alpha/bigtable/tables/create | 36 +- gcloud/alpha/bigtable/tables/update | 48 +- gcloud/alpha/bq/translation/translate | 24 +- .../certificate-manager/certificates/create | 3 +- .../certificate-manager/certificates/describe | 3 +- .../dns-authorizations/create | 3 +- .../dns-authorizations/delete | 3 +- .../dns-authorizations/describe | 3 +- .../dns-authorizations/list | 3 +- .../dns-authorizations/update | 3 +- .../issuance-configs/create | 3 +- .../issuance-configs/delete | 3 +- .../issuance-configs/describe | 3 +- .../certificate-manager/issuance-configs/list | 3 +- .../issuance-configs/update | 3 +- .../certificate-manager/operations/describe | 3 +- .../alpha/certificate-manager/operations/list | 3 +- .../certificate-manager/trust-configs/create | 3 +- .../certificate-manager/trust-configs/delete | 3 +- .../trust-configs/describe | 3 +- .../certificate-manager/trust-configs/export | 3 +- .../certificate-manager/trust-configs/import | 3 +- .../certificate-manager/trust-configs/list | 3 +- .../certificate-manager/trust-configs/update | 3 +- gcloud/alpha/cluster-director/clusters/create | 6 +- gcloud/alpha/cluster-director/clusters/update | 6 +- gcloud/alpha/composer/environments/create | 11 +- gcloud/alpha/composer/environments/update | 11 + gcloud/alpha/compute/addresses/create | 8 +- gcloud/alpha/compute/addresses/help | 2 +- gcloud/alpha/compute/addresses/update | 6 +- gcloud/alpha/compute/advice/capacity | 18 +- .../compute/backend-buckets/set-iam-policy | 2 +- .../compute/backend-services/add-backend | 12 +- gcloud/alpha/compute/backend-services/update | 11 +- .../compute/backend-services/update-backend | 12 +- gcloud/alpha/compute/commitments/create | 4 + .../compute/composite-health-checks/create | 4 +- .../compute/composite-health-checks/delete | 4 +- .../compute/composite-health-checks/describe | 4 +- .../composite-health-checks/get-health | 4 +- .../compute/composite-health-checks/help | 4 +- .../compute/composite-health-checks/list | 4 +- .../compute/composite-health-checks/update | 4 +- gcloud/alpha/compute/disks/bulk/create | 10 +- gcloud/alpha/compute/disks/bulk/help | 3 +- gcloud/alpha/compute/disks/help | 2 +- gcloud/alpha/compute/disks/update | 2 +- gcloud/alpha/compute/disks/update-kms-key | 10 +- gcloud/alpha/compute/forwarding-rules/create | 18 +- .../alpha/compute/future-reservations/create | 2 +- .../global-vm-extension-policies/create | 4 +- .../global-vm-extension-policies/delete | 4 +- .../global-vm-extension-policies/describe | 4 +- .../compute/global-vm-extension-policies/help | 4 +- .../compute/global-vm-extension-policies/list | 4 +- .../global-vm-extension-policies/update | 4 +- .../health-aggregation-policies/create | 4 +- .../health-aggregation-policies/delete | 4 +- .../health-aggregation-policies/describe | 4 +- .../compute/health-aggregation-policies/help | 4 +- .../compute/health-aggregation-policies/list | 4 +- .../health-aggregation-policies/update | 4 +- gcloud/alpha/compute/health-sources/create | 4 +- gcloud/alpha/compute/health-sources/delete | 4 +- gcloud/alpha/compute/health-sources/describe | 4 +- .../alpha/compute/health-sources/get-health | 4 +- gcloud/alpha/compute/health-sources/help | 4 +- gcloud/alpha/compute/health-sources/list | 4 +- gcloud/alpha/compute/health-sources/update | 4 +- .../alpha/compute/instance-templates/create | 4 +- .../instance-templates/create-with-container | 4 +- gcloud/alpha/compute/instances/add-metadata | 4 +- gcloud/alpha/compute/instances/bulk/create | 4 +- gcloud/alpha/compute/instances/create | 4 +- .../compute/instances/create-with-container | 4 +- gcloud/alpha/compute/instances/update | 16 + .../compute/instant-snapshot-groups/create | 12 +- .../compute/instant-snapshot-groups/delete | 8 +- .../compute/instant-snapshot-groups/describe | 13 +- .../compute/instant-snapshot-groups/help | 11 +- .../compute/instant-snapshot-groups/list | 4 +- .../interconnects/groups/create-members | 31 +- .../compute/migration/image-imports/help | 10 +- .../compute/network-endpoint-groups/create | 10 +- .../networks/peerings/cancel-request-delete | 4 +- gcloud/alpha/compute/networks/subnets/create | 10 + gcloud/alpha/compute/networks/subnets/update | 16 +- .../alpha/compute/project-info/add-metadata | 4 +- gcloud/alpha/compute/queued-resources/create | 4 +- gcloud/alpha/compute/rollout-plans/create | 4 +- gcloud/alpha/compute/rollout-plans/delete | 4 +- gcloud/alpha/compute/rollout-plans/describe | 4 +- gcloud/alpha/compute/rollout-plans/help | 4 +- gcloud/alpha/compute/rollout-plans/list | 4 +- gcloud/alpha/compute/rollouts/cancel | 4 +- gcloud/alpha/compute/rollouts/delete | 4 +- gcloud/alpha/compute/rollouts/describe | 4 +- gcloud/alpha/compute/rollouts/help | 4 +- gcloud/alpha/compute/rollouts/list | 4 +- .../alpha/compute/service-attachments/create | 4 + .../alpha/compute/service-attachments/update | 4 + gcloud/alpha/compute/snapshots/help | 3 +- gcloud/alpha/compute/snapshots/update-kms-key | 8 +- .../compute/zone-vm-extension-policies/create | 4 +- .../compute/zone-vm-extension-policies/delete | 4 +- .../zone-vm-extension-policies/describe | 4 +- .../compute/zone-vm-extension-policies/help | 4 +- .../compute/zone-vm-extension-policies/list | 4 +- .../compute/zone-vm-extension-policies/update | 4 +- gcloud/alpha/config/get | 19 +- gcloud/alpha/config/help | 19 +- gcloud/alpha/config/list | 19 +- gcloud/alpha/config/set | 19 +- gcloud/alpha/config/unset | 19 +- .../binauthz/continuous-validation/describe | 33 -- .../binauthz/continuous-validation/disable | 27 - .../binauthz/continuous-validation/enable | 27 - .../binauthz/continuous-validation/help | 37 -- gcloud/alpha/container/binauthz/help | 3 - gcloud/alpha/container/clusters/create | 67 ++- gcloud/alpha/container/clusters/create-auto | 49 +- gcloud/alpha/container/clusters/update | 35 +- .../fleet/config-management/describe | 3 +- .../fleet/memberships/get-credentials | 7 + .../container/hub/config-management/describe | 3 +- .../container/hub/memberships/get-credentials | 7 + gcloud/alpha/container/node-pools/create | 42 +- gcloud/alpha/container/node-pools/update | 32 ++ gcloud/alpha/dataplex/context/help | 2 +- gcloud/alpha/dataplex/context/lookup | 36 +- .../add-iam-policy-binding | 93 ---- .../dataplex/data-attribute-bindings/create | 131 ----- .../dataplex/data-attribute-bindings/delete | 79 --- .../dataplex/data-attribute-bindings/describe | 69 --- .../dataplex/data-attribute-bindings/help | 54 -- .../remove-iam-policy-binding | 95 ---- .../data-attribute-bindings/set-iam-policy | 79 --- .../dataplex/data-attribute-bindings/update | 127 ----- .../attributes/add-iam-policy-binding | 101 ---- .../data-taxonomies/attributes/create | 138 ----- .../data-taxonomies/attributes/delete | 87 --- .../data-taxonomies/attributes/describe | 79 --- .../data-taxonomies/attributes/get-iam-policy | 112 ---- .../dataplex/data-taxonomies/attributes/help | 53 -- .../attributes/remove-iam-policy-binding | 103 ---- .../data-taxonomies/attributes/set-iam-policy | 87 --- .../data-taxonomies/attributes/update | 143 ----- gcloud/alpha/dataplex/data-taxonomies/create | 94 ---- gcloud/alpha/dataplex/data-taxonomies/delete | 78 --- gcloud/alpha/dataplex/data-taxonomies/help | 58 -- gcloud/alpha/dataplex/data-taxonomies/update | 96 ---- .../dataplex/datascans/create/data-profile | 15 +- .../dataplex/datascans/create/data-quality | 15 +- gcloud/alpha/dataplex/entries/help | 3 + gcloud/alpha/dataplex/entries/modify | 295 +++++++++++ gcloud/alpha/dataplex/help | 6 - gcloud/alpha/dataproc/clusters/create | 120 ++++- .../workflow-templates/set-managed-cluster | 121 ++++- .../spaces/application-templates/help | 3 + .../application-templates/policies/create | 142 +++++ .../application-templates/policies/delete | 87 +++ .../application-templates/policies/describe | 87 +++ .../application-templates/policies/help | 40 ++ .../application-templates/policies/list | 115 ++++ .../application-templates/policies/update | 201 +++++++ .../fault-testing/experiment-templates/create | 160 ++++++ .../fault-testing/experiment-templates/delete | 70 +++ .../experiment-templates/describe | 70 +++ .../fault-testing/experiment-templates/help | 40 ++ .../experiment-templates}/list | 34 +- .../fault-testing/experiment-templates/update | 144 +++++ .../experiments/affected-resources/describe | 79 +++ .../experiments/affected-resources/help | 31 ++ .../experiments/affected-resources}/list | 52 +- gcloud/alpha/fault-testing/experiments/create | 107 ++++ gcloud/alpha/fault-testing/experiments/delete | 74 +++ .../experiments}/describe | 46 +- gcloud/alpha/fault-testing/experiments/help | 51 ++ gcloud/alpha/fault-testing/experiments/list | 87 +++ gcloud/alpha/fault-testing/experiments/start | 68 +++ gcloud/alpha/fault-testing/experiments/stop | 67 +++ .../alpha/fault-testing/experiments/stop-all | 56 ++ gcloud/alpha/fault-testing/help | 32 ++ gcloud/alpha/fault-testing/validations/create | 154 ++++++ gcloud/alpha/fault-testing/validations/delete | 73 +++ .../alpha/fault-testing/validations/describe | 68 +++ gcloud/alpha/fault-testing/validations/help | 42 ++ gcloud/alpha/fault-testing/validations/list | 86 +++ .../validations/validation-resources/describe | 78 +++ .../validations/validation-resources/help | 31 ++ .../validations/validation-resources/list | 102 ++++ gcloud/alpha/firestore/databases/create | 9 + gcloud/alpha/firestore/databases/update | 7 +- gcloud/alpha/firestore/fields/ttls/update | 24 +- .../alpha/firestore/indexes/composite/create | 96 +++- .../iam/workforce-pools/providers/create-oidc | 3 + .../iam/workforce-pools/providers/update-oidc | 3 + gcloud/alpha/iap/web/add-iam-policy-binding | 19 +- gcloud/alpha/iap/web/get-iam-policy | 19 +- .../alpha/iap/web/remove-iam-policy-binding | 19 +- gcloud/alpha/iap/web/set-iam-policy | 19 +- gcloud/alpha/kms/asymmetric-sign | 7 +- gcloud/alpha/kms/key-handles/create | 4 +- gcloud/alpha/kms/single-tenant-hsm/create | 6 +- gcloud/alpha/kms/single-tenant-hsm/describe | 10 +- .../kms/single-tenant-hsm/proposal/describe | 14 +- gcloud/alpha/lifesciences/help | 34 -- gcloud/alpha/lifesciences/locations/describe | 55 -- gcloud/alpha/lifesciences/operations/help | 38 -- gcloud/alpha/lifesciences/pipelines/run | 199 ------- gcloud/alpha/lustre/instances/update | 16 - gcloud/alpha/memorystore/instances/create | 12 + .../instances/create-token-auth-user | 79 +++ gcloud/alpha/memorystore/instances/help | 9 + .../token-auth-users/auth-tokens/delete | 94 ++++ .../token-auth-users/auth-tokens/describe | 89 ++++ .../token-auth-users/auth-tokens}/help | 17 +- .../token-auth-users/auth-tokens/list | 113 ++++ .../token-auth-users/create-auth-token | 84 +++ .../instances/token-auth-users/delete | 104 ++++ .../instances/token-auth-users/describe | 79 +++ .../instances/token-auth-users/help | 45 ++ .../instances/token-auth-users/list | 102 ++++ gcloud/alpha/memorystore/instances/update | 24 +- gcloud/alpha/migration/vms/image-imports/help | 4 +- .../mldiagnostics/machine-learning-run/create | 24 +- .../mldiagnostics/machine-learning-run/update | 24 +- gcloud/alpha/netapp/storage-pools/create | 21 +- gcloud/alpha/netapp/storage-pools/execute | 4 +- gcloud/alpha/netapp/storage-pools/help | 10 + .../storage-pools/list-backup-configs} | 65 ++- .../alpha/netapp/storage-pools/restore-volume | 155 ++++++ .../netapp/storage-pools/update-backup-config | 99 ++++ .../generate-monitoring-point-config | 73 +++ .../network-monitoring-providers/help | 3 + .../download-recreate-install-script | 58 ++ .../download-server-connect-config | 50 ++ .../monitoring-points/help | 8 + .../firewall-endpoint-associations/create | 17 +- .../firewall-endpoint-associations/delete | 9 +- .../firewall-endpoint-associations/describe | 10 +- .../firewall-endpoint-associations/list | 13 +- .../firewall-endpoint-associations/update | 8 +- .../firewall-endpoints/create | 8 +- .../firewall-endpoints/delete | 9 +- .../firewall-endpoints/describe | 9 +- .../network-security/firewall-endpoints/list | 12 +- .../firewall-endpoints/update | 9 +- .../threat-prevention/describe | 91 ++++ .../security-profiles/threat-prevention/help | 8 + .../network-services/agent-gateways/delete | 4 +- .../network-services/agent-gateways/describe | 4 +- .../network-services/agent-gateways/export | 4 +- .../network-services/agent-gateways/help | 4 +- .../network-services/agent-gateways/import | 4 +- .../network-services/agent-gateways/list | 4 +- .../number-registry/custom-ranges/create | 198 +++++++ .../number-registry/custom-ranges/delete | 92 ++++ .../number-registry/custom-ranges/describe | 68 +++ .../custom-ranges/find-free-ip-ranges | 94 ++++ .../alpha/number-registry/custom-ranges/help | 44 ++ .../alpha/number-registry/custom-ranges/list | 87 +++ .../custom-ranges/show-utilization | 68 +++ .../number-registry/custom-ranges/update | 326 ++++++++++++ .../discovered-ranges/describe | 68 +++ .../discovered-ranges/find-free-ip-ranges | 93 ++++ .../number-registry/discovered-ranges/help | 37 ++ .../number-registry/discovered-ranges/list | 88 ++++ .../discovered-ranges/show-utilization | 68 +++ gcloud/alpha/number-registry/help | 42 ++ .../ipam-admin-scopes/check-availability | 58 ++ .../number-registry/ipam-admin-scopes/cleanup | 89 ++++ .../number-registry/ipam-admin-scopes/create | 130 +++++ .../number-registry/ipam-admin-scopes/delete | 92 ++++ .../ipam-admin-scopes/describe | 68 +++ .../number-registry/ipam-admin-scopes/disable | 89 ++++ .../number-registry/ipam-admin-scopes/help | 50 ++ .../number-registry/ipam-admin-scopes/list | 88 ++++ .../number-registry/ipam-admin-scopes/update | 182 +++++++ .../operations/cancel} | 29 +- .../operations/delete} | 27 +- .../number-registry}/operations/describe | 37 +- gcloud/alpha/number-registry/operations/help | 38 ++ .../operations/list | 38 +- .../operations/wait | 30 +- gcloud/alpha/number-registry/realms/create | 154 ++++++ gcloud/alpha/number-registry/realms/delete | 79 +++ gcloud/alpha/number-registry/realms/describe | 66 +++ gcloud/alpha/number-registry/realms/help | 39 ++ gcloud/alpha/number-registry/realms/list | 86 +++ gcloud/alpha/number-registry/realms/update | 205 ++++++++ .../number-registry/registry-books/create | 118 +++++ .../number-registry/registry-books/delete | 92 ++++ .../number-registry/registry-books/describe | 81 +++ .../alpha/number-registry/registry-books/help | 42 ++ .../alpha/number-registry/registry-books/list | 100 ++++ .../registry-books/search-ip-resources | 115 ++++ .../number-registry/registry-books/update | 191 +++++++ gcloud/alpha/pam/grants/create | 6 + gcloud/alpha/redis/clusters/create | 3 +- .../redis/clusters/create-token-auth-user | 75 +++ gcloud/alpha/redis/clusters/help | 7 + .../token-auth-users/auth-tokens/delete | 101 ++++ .../token-auth-users/auth-tokens/describe | 98 ++++ .../token-auth-users/auth-tokens/help | 36 ++ .../token-auth-users/auth-tokens/list | 116 ++++ .../token-auth-users/create-auth-token | 81 +++ .../redis/clusters/token-auth-users/delete | 95 ++++ .../redis/clusters/token-auth-users/describe | 89 ++++ .../redis/clusters/token-auth-users/help | 46 ++ .../redis/clusters/token-auth-users/list | 105 ++++ gcloud/alpha/redis/clusters/update | 3 +- gcloud/alpha/run/deploy | 14 +- gcloud/alpha/run/instances/create | 29 +- gcloud/alpha/run/instances/dev/help | 35 ++ gcloud/alpha/run/instances/help | 16 +- gcloud/alpha/run/instances/logs/help | 35 ++ gcloud/alpha/run/instances/logs/read | 83 +++ gcloud/alpha/run/instances/logs/tail | 53 ++ gcloud/alpha/run/instances/replace | 44 ++ gcloud/alpha/run/multi-region-services/update | 6 +- gcloud/alpha/run/services/update | 6 +- .../run/worker-pools/add-iam-policy-binding | 4 +- gcloud/alpha/run/worker-pools/delete | 4 +- gcloud/alpha/run/worker-pools/deploy | 4 +- gcloud/alpha/run/worker-pools/describe | 4 +- gcloud/alpha/run/worker-pools/get-iam-policy | 4 +- gcloud/alpha/run/worker-pools/help | 4 +- gcloud/alpha/run/worker-pools/list | 4 +- gcloud/alpha/run/worker-pools/logs/help | 4 +- gcloud/alpha/run/worker-pools/logs/read | 4 +- gcloud/alpha/run/worker-pools/logs/tail | 4 +- .../worker-pools/remove-iam-policy-binding | 4 +- gcloud/alpha/run/worker-pools/replace | 4 +- .../alpha/run/worker-pools/revisions/delete | 6 +- .../alpha/run/worker-pools/revisions/describe | 8 +- gcloud/alpha/run/worker-pools/revisions/help | 4 +- gcloud/alpha/run/worker-pools/revisions/list | 4 +- gcloud/alpha/run/worker-pools/set-iam-policy | 4 +- gcloud/alpha/run/worker-pools/update | 4 +- .../run/worker-pools/update-instance-split | 4 +- gcloud/alpha/scc/sources/help | 3 + gcloud/alpha/scc/sources/list | 86 +++ .../alpha/service-health/artifacts/describe | 4 +- gcloud/alpha/service-health/artifacts/help | 4 +- gcloud/alpha/service-health/artifacts/list | 4 +- gcloud/alpha/service-health/events/describe | 6 +- gcloud/alpha/service-health/events/help | 6 +- gcloud/alpha/service-health/events/list | 6 +- gcloud/alpha/service-health/help | 6 +- .../organization-events/describe | 10 +- .../service-health/organization-events/help | 6 +- .../service-health/organization-events/list | 10 +- .../organization-impacts/describe | 6 +- .../service-health/organization-impacts/help | 6 +- .../service-health/organization-impacts/list | 6 +- gcloud/alpha/services/api-keys/update | 21 +- gcloud/alpha/spanner/databases/update | 13 +- gcloud/alpha/sql/instances/create | 27 +- gcloud/alpha/sql/instances/patch | 29 +- .../storage/batch-operations/jobs/create | 105 +++- gcloud/alpha/storage/objects/compose | 14 +- gcloud/alpha/workload-identity/help | 30 ++ .../workload-identity/service-agents/generate | 78 +++ .../workload-identity/service-agents/help | 32 ++ gcloud/alpha/workstations/clusters/create | 9 +- gcloud/alpha/workstations/clusters/help | 3 + gcloud/alpha/workstations/clusters/update | 113 ++++ gcloud/alpha/workstations/ssh | 6 +- gcloud/alpha/workstations/start-tcp-tunnel | 6 +- gcloud/artifacts/help | 4 + gcloud/artifacts/projects/describe | 46 ++ gcloud/artifacts/projects/help | 24 + gcloud/artifacts/projects/update | 70 +++ gcloud/artifacts/repositories/create | 26 +- gcloud/artifacts/repositories/update | 29 +- gcloud/artifacts/tags/export | 2 +- gcloud/artifacts/versions/export | 2 +- .../backup-dr/backup-plan-associations/create | 4 +- .../backup-dr/backup-plan-associations/delete | 4 +- .../backup-plan-associations/describe | 4 +- .../fetch-for-resource-type | 5 +- .../backup-dr/backup-plan-associations/help | 4 +- .../backup-dr/backup-plan-associations/list | 4 +- .../backup-plan-associations/trigger-backup | 4 +- .../backup-dr/backup-plan-associations/update | 4 +- .../backup-dr/backup-plan-revisions/describe | 4 +- gcloud/backup-dr/backup-plan-revisions/help | 4 +- gcloud/backup-dr/backup-plan-revisions/list | 4 +- gcloud/backup-dr/backup-plans/create | 23 +- gcloud/backup-dr/backup-plans/delete | 4 +- gcloud/backup-dr/backup-plans/describe | 4 +- gcloud/backup-dr/backup-plans/help | 4 +- gcloud/backup-dr/backup-plans/list | 4 +- gcloud/backup-dr/backup-plans/update | 22 +- gcloud/backup-dr/backup-vaults/create | 4 +- gcloud/backup-dr/backup-vaults/delete | 4 +- gcloud/backup-dr/backup-vaults/describe | 4 +- gcloud/backup-dr/backup-vaults/help | 4 +- gcloud/backup-dr/backup-vaults/list | 4 +- gcloud/backup-dr/backup-vaults/update | 4 +- gcloud/backup-dr/backups/delete | 4 +- gcloud/backup-dr/backups/describe | 4 +- .../backup-dr/backups/fetch-for-resource-type | 4 +- gcloud/backup-dr/backups/help | 4 +- gcloud/backup-dr/backups/list | 4 +- gcloud/backup-dr/backups/restore/compute | 4 +- gcloud/backup-dr/backups/restore/disk | 4 +- gcloud/backup-dr/backups/restore/help | 4 +- gcloud/backup-dr/backups/update | 4 +- .../backup-dr/data-source-references/describe | 4 +- .../fetch-for-resource-type | 5 +- gcloud/backup-dr/data-source-references/help | 4 +- gcloud/backup-dr/data-source-references/list | 4 +- gcloud/backup-dr/data-sources/describe | 4 +- gcloud/backup-dr/data-sources/help | 4 +- gcloud/backup-dr/data-sources/list | 4 +- gcloud/backup-dr/resource-backup-config/help | 4 +- gcloud/backup-dr/resource-backup-config/list | 4 +- gcloud/backup-dr/service-config/help | 4 +- gcloud/backup-dr/service-config/init | 4 +- gcloud/beta/ai/help | 6 + gcloud/beta/ai/model-garden/models/deploy | 7 +- .../ai/semantic-governance-policies/create | 92 ++++ .../ai/semantic-governance-policies/delete | 77 +++ .../ai/semantic-governance-policies/describe | 64 +++ .../beta/ai/semantic-governance-policies/help | 36 ++ .../beta/ai/semantic-governance-policies/list | 78 +++ .../ai/semantic-governance-policies/update | 95 ++++ .../describe | 37 ++ .../ai/semantic-governance-policy-engine/help | 28 + .../semantic-governance-policy-engine/update | 55 ++ gcloud/beta/alloydb/clusters/create | 9 +- gcloud/beta/alloydb/clusters/promote | 8 +- gcloud/beta/alloydb/instances/create | 17 +- gcloud/beta/alloydb/instances/update | 17 +- gcloud/beta/alloydb/users/create | 3 + gcloud/beta/api-registry/help | 2 +- gcloud/beta/api-registry/mcp/disable | 6 +- gcloud/beta/api-registry/mcp/enable | 6 +- gcloud/beta/api-registry/mcp/help | 18 +- gcloud/beta/api-registry/mcp/servers/help | 6 +- gcloud/beta/api-registry/mcp/servers/list | 15 +- gcloud/beta/api-registry/mcp/tools/help | 6 +- gcloud/beta/api-registry/mcp/tools/list | 18 +- .../flags/attributes/create | 11 +- .../flags/attributes/delete | 24 +- .../flags/attributes/describe | 28 +- .../flags/attributes/list | 32 +- .../flags/attributes/update | 18 +- .../beta/app-lifecycle-manager/flags/create | 82 ++- .../beta/app-lifecycle-manager/flags/delete | 25 +- .../beta/app-lifecycle-manager/flags/describe | 35 +- gcloud/beta/app-lifecycle-manager/flags/list | 21 +- .../flags/releases/create | 47 +- .../flags/releases/delete | 22 +- .../flags/releases/describe | 30 +- .../app-lifecycle-manager/flags/releases/help | 6 +- .../app-lifecycle-manager/flags/releases/list | 26 +- .../flags/releases/update | 19 +- .../flags/revisions/create | 29 +- .../flags/revisions/delete | 33 +- .../flags/revisions/describe | 36 +- .../flags/revisions/help | 2 +- .../flags/revisions/list | 35 +- .../flags/revisions/update | 16 +- .../beta/app-lifecycle-manager/flags/update | 118 ++++- gcloud/beta/app-lifecycle-manager/saas/create | 18 +- gcloud/beta/app-lifecycle-manager/saas/update | 16 + .../app-lifecycle-manager/unit-kinds/create | 19 + .../app-lifecycle-manager/unit-kinds/update | 23 + .../beta/app-lifecycle-manager/units/create | 9 +- .../beta/app-lifecycle-manager/units/update | 11 + gcloud/beta/app-optimize/help | 30 ++ gcloud/beta/app-optimize/reports/create | 116 ++++ gcloud/beta/app-optimize/reports/delete | 64 +++ .../wait => app-optimize/reports/describe} | 42 +- gcloud/beta/app-optimize/reports/help | 38 ++ gcloud/beta/app-optimize/reports/list | 79 +++ gcloud/beta/app-optimize/reports/read | 54 ++ gcloud/beta/app/migrate-to-run | 24 +- .../backup-dr/backup-plan-associations/create | 125 +++++ .../backup-dr/backup-plan-associations/delete | 80 +++ .../backup-plan-associations/describe | 70 +++ .../fetch-for-resource-type | 88 ++++ .../backup-dr/backup-plan-associations/help | 49 ++ .../backup-dr/backup-plan-associations/list | 94 ++++ .../backup-plan-associations/trigger-backup | 98 ++++ .../backup-dr/backup-plan-associations/update | 130 +++++ .../backup-dr/backup-plan-revisions/describe | 78 +++ .../beta/backup-dr/backup-plan-revisions/help | 32 ++ .../beta/backup-dr/backup-plan-revisions/list | 112 ++++ gcloud/beta/backup-dr/backup-plans/create | 299 +++++++++++ gcloud/beta/backup-dr/backup-plans/delete | 74 +++ gcloud/beta/backup-dr/backup-plans/describe | 68 +++ gcloud/beta/backup-dr/backup-plans/help | 40 ++ .../backup-plans}/list | 37 +- gcloud/beta/backup-dr/backup-plans/update | 323 ++++++++++++ gcloud/beta/backup-dr/backup-vaults/create | 151 ++++++ gcloud/beta/backup-dr/backup-vaults/delete | 107 ++++ gcloud/beta/backup-dr/backup-vaults/describe | 71 +++ gcloud/beta/backup-dr/backup-vaults/help | 40 ++ .../backup-dr/backup-vaults}/list | 39 +- gcloud/beta/backup-dr/backup-vaults/update | 152 ++++++ gcloud/beta/backup-dr/backups/delete | 92 ++++ gcloud/beta/backup-dr/backups/describe | 83 +++ .../backup-dr/backups/fetch-for-resource-type | 118 +++++ gcloud/beta/backup-dr/backups/help | 46 ++ gcloud/beta/backup-dr/backups/list | 116 ++++ gcloud/beta/backup-dr/backups/restore/compute | 434 +++++++++++++++ gcloud/beta/backup-dr/backups/restore/disk | 221 ++++++++ gcloud/beta/backup-dr/backups/restore/help | 32 ++ gcloud/beta/backup-dr/backups/update | 154 ++++++ .../backup-dr/data-source-references/describe | 70 +++ .../fetch-for-resource-type | 84 +++ .../backup-dr/data-source-references/help | 36 ++ .../backup-dr/data-source-references/list | 93 ++++ gcloud/beta/backup-dr/data-sources/describe | 78 +++ gcloud/beta/backup-dr/data-sources/help | 31 ++ gcloud/beta/backup-dr/data-sources/list | 106 ++++ gcloud/beta/backup-dr/help | 28 + gcloud/beta/backup-dr/locations/list | 4 +- .../backup-dr/management-servers/describe | 4 +- gcloud/beta/backup-dr/management-servers/list | 4 +- gcloud/beta/backup-dr/operations/describe | 4 +- gcloud/beta/backup-dr/operations/list | 4 +- .../backup-dr/resource-backup-config/help | 31 ++ .../backup-dr/resource-backup-config/list | 144 +++++ gcloud/beta/backup-dr/service-config/help | 29 + gcloud/beta/backup-dr/service-config/init | 76 +++ .../security-gateways/add-iam-policy-binding | 96 ++++ .../applications/add-iam-policy-binding | 109 ++++ .../security-gateways/applications/help | 7 + .../applications/remove-iam-policy-binding | 110 ++++ .../beta/beyondcorp/security-gateways/create | 17 +- gcloud/beta/beyondcorp/security-gateways/help | 6 + .../remove-iam-policy-binding | 98 ++++ .../beta/beyondcorp/security-gateways/update | 28 - gcloud/beta/biglake/iceberg/catalogs/create | 2 +- gcloud/beta/biglake/iceberg/catalogs/update | 8 +- gcloud/beta/biglake/iceberg/tables/create | 6 +- gcloud/beta/biglake/iceberg/tables/delete | 6 +- gcloud/beta/biglake/iceberg/tables/describe | 6 +- .../biglake/iceberg/tables/get-iam-policy | 6 +- gcloud/beta/biglake/iceberg/tables/help | 6 +- gcloud/beta/biglake/iceberg/tables/list | 6 +- gcloud/beta/biglake/iceberg/tables/register | 6 +- .../biglake/iceberg/tables/set-iam-policy | 6 +- gcloud/beta/biglake/iceberg/tables/update | 6 +- gcloud/beta/bigtable/app-profiles/create | 15 +- gcloud/beta/bigtable/app-profiles/update | 13 +- gcloud/beta/bigtable/help | 3 + gcloud/beta/bigtable/instances/create | 14 +- gcloud/beta/bigtable/instances/tables/create | 36 +- gcloud/beta/bigtable/instances/tables/update | 48 +- gcloud/beta/bigtable/instances/update | 12 +- gcloud/beta/bigtable/memory-layers/describe | 62 +++ gcloud/beta/bigtable/memory-layers/help | 29 + gcloud/beta/bigtable/memory-layers/update | 80 +++ gcloud/beta/bigtable/tables/create | 36 +- gcloud/beta/bigtable/tables/update | 48 +- .../certificate-manager/certificates/create | 3 +- .../certificate-manager/certificates/describe | 3 +- .../dns-authorizations/create | 3 +- .../dns-authorizations/delete | 3 +- .../dns-authorizations/describe | 3 +- .../dns-authorizations/list | 3 +- .../dns-authorizations/update | 3 +- .../issuance-configs/create | 3 +- .../issuance-configs/delete | 3 +- .../issuance-configs/describe | 3 +- .../certificate-manager/issuance-configs/list | 3 +- .../issuance-configs/update | 3 +- .../certificate-manager/operations/describe | 3 +- .../beta/certificate-manager/operations/list | 3 +- .../certificate-manager/trust-configs/create | 3 +- .../certificate-manager/trust-configs/delete | 3 +- .../trust-configs/describe | 3 +- .../certificate-manager/trust-configs/export | 3 +- .../certificate-manager/trust-configs/import | 3 +- .../certificate-manager/trust-configs/list | 3 +- .../certificate-manager/trust-configs/update | 3 +- gcloud/beta/composer/environments/create | 11 +- gcloud/beta/composer/environments/update | 11 + gcloud/beta/compute/addresses/create | 25 +- gcloud/beta/compute/addresses/help | 2 +- gcloud/beta/compute/addresses/update | 8 +- .../compute/backend-buckets/set-iam-policy | 2 +- .../beta/compute/backend-services/add-backend | 2 +- gcloud/beta/compute/backend-services/update | 11 +- .../compute/backend-services/update-backend | 2 +- .../compute/composite-health-checks/create | 6 +- .../compute/composite-health-checks/delete | 6 +- .../compute/composite-health-checks/describe | 6 +- .../composite-health-checks/get-health | 6 +- .../beta/compute/composite-health-checks/help | 6 +- .../beta/compute/composite-health-checks/list | 6 +- .../compute/composite-health-checks/update | 6 +- gcloud/beta/compute/disks/bulk/create | 50 +- gcloud/beta/compute/disks/bulk/help | 3 +- gcloud/beta/compute/disks/help | 2 +- gcloud/beta/compute/disks/update | 4 +- gcloud/beta/compute/disks/update-kms-key | 10 +- gcloud/beta/compute/forwarding-rules/describe | 12 +- .../beta/compute/future-reservations/create | 4 + .../global-vm-extension-policies/create | 6 +- .../global-vm-extension-policies/delete | 6 +- .../global-vm-extension-policies/describe | 6 +- .../compute/global-vm-extension-policies/help | 6 +- .../compute/global-vm-extension-policies/list | 6 +- .../global-vm-extension-policies/update | 6 +- .../health-aggregation-policies/create | 6 +- .../health-aggregation-policies/delete | 6 +- .../health-aggregation-policies/describe | 6 +- .../compute/health-aggregation-policies/help | 6 +- .../compute/health-aggregation-policies/list | 6 +- .../health-aggregation-policies/update | 6 +- gcloud/beta/compute/health-sources/create | 6 +- gcloud/beta/compute/health-sources/delete | 6 +- gcloud/beta/compute/health-sources/describe | 6 +- gcloud/beta/compute/health-sources/get-health | 6 +- gcloud/beta/compute/health-sources/help | 6 +- gcloud/beta/compute/health-sources/list | 6 +- gcloud/beta/compute/health-sources/update | 6 +- gcloud/beta/compute/instances/add-metadata | 4 +- .../beta/compute/instances/update-from-file | 7 +- .../compute/instant-snapshot-groups/create | 14 +- .../compute/instant-snapshot-groups/delete | 10 +- .../compute/instant-snapshot-groups/describe | 15 +- .../beta/compute/instant-snapshot-groups/help | 13 +- .../beta/compute/instant-snapshot-groups/list | 6 +- .../interconnects/groups/create-members | 31 +- .../compute/network-endpoint-groups/create | 10 +- .../networks/peerings/cancel-request-delete | 6 +- gcloud/beta/compute/project-info/add-metadata | 4 +- gcloud/beta/compute/rollout-plans/create | 6 +- gcloud/beta/compute/rollout-plans/delete | 6 +- gcloud/beta/compute/rollout-plans/describe | 6 +- gcloud/beta/compute/rollout-plans/help | 6 +- gcloud/beta/compute/rollout-plans/list | 6 +- gcloud/beta/compute/rollouts/cancel | 6 +- gcloud/beta/compute/rollouts/delete | 6 +- gcloud/beta/compute/rollouts/describe | 6 +- gcloud/beta/compute/rollouts/help | 6 +- gcloud/beta/compute/rollouts/list | 6 +- gcloud/beta/compute/snapshots/help | 3 +- gcloud/beta/compute/snapshots/update-kms-key | 6 +- .../compute/zone-vm-extension-policies/create | 6 +- .../compute/zone-vm-extension-policies/delete | 6 +- .../zone-vm-extension-policies/describe | 6 +- .../compute/zone-vm-extension-policies/help | 6 +- .../compute/zone-vm-extension-policies/list | 6 +- .../compute/zone-vm-extension-policies/update | 6 +- gcloud/beta/config/get | 19 +- gcloud/beta/config/help | 19 +- gcloud/beta/config/list | 19 +- gcloud/beta/config/set | 19 +- gcloud/beta/config/unset | 19 +- gcloud/beta/container/clusters/create | 71 ++- gcloud/beta/container/clusters/create-auto | 49 +- gcloud/beta/container/clusters/update | 35 +- .../fleet/memberships/get-credentials | 7 + .../container/hub/memberships/get-credentials | 7 + gcloud/beta/container/node-pools/create | 42 +- gcloud/beta/container/node-pools/update | 32 ++ gcloud/beta/dataflow/flex-template/run | 5 + gcloud/beta/dataproc/clusters/create | 120 ++++- .../workflow-templates/set-managed-cluster | 121 ++++- gcloud/beta/firestore/databases/create | 9 + gcloud/beta/firestore/databases/update | 7 +- gcloud/beta/firestore/fields/ttls/update | 24 +- .../beta/firestore/indexes/composite/create | 96 +++- gcloud/beta/iam/access-policies/create | 10 +- gcloud/beta/iam/access-policies/update | 24 +- .../iam/workforce-pools/providers/create-oidc | 3 + .../iam/workforce-pools/providers/update-oidc | 3 + gcloud/beta/iap/tcp/help | 2 +- gcloud/beta/iap/web/add-iam-policy-binding | 19 +- gcloud/beta/iap/web/get-iam-policy | 19 +- gcloud/beta/iap/web/remove-iam-policy-binding | 19 +- gcloud/beta/iap/web/set-iam-policy | 19 +- gcloud/beta/kms/asymmetric-sign | 7 +- gcloud/beta/kms/key-handles/create | 4 +- gcloud/beta/kms/single-tenant-hsm/create | 6 +- gcloud/beta/kms/single-tenant-hsm/describe | 10 +- .../kms/single-tenant-hsm/proposal/describe | 14 +- gcloud/beta/lifesciences/help | 32 -- gcloud/beta/lifesciences/locations/describe | 53 -- gcloud/beta/lifesciences/locations/help | 29 - gcloud/beta/lifesciences/operations/help | 35 -- gcloud/beta/lifesciences/pipelines/help | 26 - gcloud/beta/lifesciences/pipelines/run | 197 ------- gcloud/beta/memorystore/instances/create | 12 + .../instances/create-token-auth-user | 77 +++ gcloud/beta/memorystore/instances/help | 9 + .../token-auth-users/auth-tokens/delete | 92 ++++ .../token-auth-users/auth-tokens/describe | 87 +++ .../token-auth-users/auth-tokens/help | 34 ++ .../token-auth-users/auth-tokens/list | 111 ++++ .../token-auth-users/create-auth-token | 82 +++ .../instances/token-auth-users/delete | 102 ++++ .../instances/token-auth-users/describe | 77 +++ .../instances/token-auth-users/help | 43 ++ .../instances/token-auth-users/list | 100 ++++ gcloud/beta/memorystore/instances/update | 24 +- .../beta/netapp/backup-vaults/backups/create | 137 ++--- gcloud/beta/netapp/backup-vaults/create | 11 +- gcloud/beta/netapp/storage-pools/create | 21 +- gcloud/beta/netapp/storage-pools/execute | 6 +- gcloud/beta/netapp/storage-pools/help | 12 + .../netapp/storage-pools/list-backup-configs | 100 ++++ .../beta/netapp/storage-pools/restore-volume | 153 ++++++ .../netapp/storage-pools/update-backup-config | 97 ++++ .../spokes/linked-producer-vpc-network/create | 5 +- .../spokes/linked-vpc-network/create | 5 +- .../network-connectivity/transports/create | 106 ++-- .../network-connectivity/transports/delete | 5 +- .../network-connectivity/transports/describe | 5 +- .../beta/network-connectivity/transports/help | 5 +- .../beta/network-connectivity/transports/list | 5 +- .../transports/remote-profiles/describe | 5 +- .../transports/remote-profiles/help | 5 +- .../transports/remote-profiles/list | 5 +- .../network-connectivity/transports/update | 5 +- .../firewall-endpoint-associations/create | 42 +- .../firewall-endpoint-associations/delete | 9 +- .../firewall-endpoint-associations/describe | 10 +- .../firewall-endpoint-associations/list | 13 +- .../firewall-endpoint-associations/update | 8 +- .../firewall-endpoints/create | 26 +- .../firewall-endpoints/delete | 26 +- .../firewall-endpoints/describe | 26 +- .../network-security/firewall-endpoints/list | 30 +- .../firewall-endpoints/update | 26 +- .../security-profile-groups/create | 94 +++- .../security-profile-groups/delete | 16 +- .../security-profile-groups/describe | 16 +- .../security-profile-groups/list | 16 +- .../security-profile-groups/update | 58 +- .../security-profiles/custom-intercept/create | 21 +- .../security-profiles/custom-intercept/delete | 17 +- .../custom-intercept/describe | 17 +- .../security-profiles/custom-intercept/list | 16 +- .../security-profiles/custom-intercept/update | 17 +- .../security-profiles/custom-mirroring/create | 21 +- .../security-profiles/custom-mirroring/delete | 17 +- .../custom-mirroring/describe | 17 +- .../security-profiles/custom-mirroring/list | 16 +- .../security-profiles/custom-mirroring/update | 17 +- .../network-security/security-profiles/delete | 17 +- .../security-profiles/describe | 17 +- .../network-security/security-profiles/export | 17 +- .../network-security/security-profiles/import | 17 +- .../network-security/security-profiles/list | 16 +- .../threat-prevention/add-override | 17 +- .../threat-prevention/create | 17 +- .../threat-prevention/delete | 17 +- .../threat-prevention/delete-override | 17 +- .../threat-prevention/describe | 89 ++++ .../security-profiles/threat-prevention/help | 8 + .../security-profiles/threat-prevention/list | 16 +- .../threat-prevention/list-overrides | 17 +- .../threat-prevention/update-override | 17 +- .../security-profiles/url-filtering/create | 17 +- .../security-profiles/url-filtering/delete | 17 +- .../security-profiles/url-filtering/describe | 17 +- .../security-profiles/url-filtering/list | 16 +- .../network-services/agent-gateways/delete | 71 +++ .../agent-gateways/describe} | 43 +- .../network-services/agent-gateways/export | 76 +++ .../beta/network-services/agent-gateways/help | 39 ++ .../network-services/agent-gateways/import | 83 +++ .../beta/network-services/agent-gateways/list | 87 +++ gcloud/beta/network-services/help | 3 + gcloud/beta/pam/grants/create | 6 + gcloud/beta/redis/clusters/create | 3 +- .../redis/clusters/create-token-auth-user | 73 +++ gcloud/beta/redis/clusters/help | 7 + .../token-auth-users/auth-tokens/delete | 99 ++++ .../token-auth-users/auth-tokens/describe | 97 ++++ .../token-auth-users/auth-tokens/help | 34 ++ .../token-auth-users/auth-tokens/list | 114 ++++ .../token-auth-users/create-auth-token | 79 +++ .../redis/clusters/token-auth-users/delete | 93 ++++ .../redis/clusters/token-auth-users/describe | 87 +++ .../beta/redis/clusters/token-auth-users/help | 44 ++ .../beta/redis/clusters/token-auth-users/list | 103 ++++ gcloud/beta/redis/clusters/update | 3 +- gcloud/beta/run/deploy | 18 + gcloud/beta/run/multi-region-services/update | 18 + gcloud/beta/run/services/update | 18 + .../run/worker-pools/add-iam-policy-binding | 6 +- gcloud/beta/run/worker-pools/delete | 6 +- gcloud/beta/run/worker-pools/deploy | 6 +- gcloud/beta/run/worker-pools/describe | 6 +- gcloud/beta/run/worker-pools/get-iam-policy | 6 +- gcloud/beta/run/worker-pools/help | 6 +- gcloud/beta/run/worker-pools/list | 6 +- gcloud/beta/run/worker-pools/logs/help | 6 +- gcloud/beta/run/worker-pools/logs/read | 6 +- gcloud/beta/run/worker-pools/logs/tail | 6 +- .../worker-pools/remove-iam-policy-binding | 6 +- gcloud/beta/run/worker-pools/replace | 6 +- gcloud/beta/run/worker-pools/revisions/delete | 8 +- .../beta/run/worker-pools/revisions/describe | 10 +- gcloud/beta/run/worker-pools/revisions/help | 6 +- gcloud/beta/run/worker-pools/revisions/list | 6 +- gcloud/beta/run/worker-pools/set-iam-policy | 6 +- gcloud/beta/run/worker-pools/update | 6 +- .../run/worker-pools/update-instance-split | 6 +- .../beta/saas-runtime/flags/attributes/create | 10 +- .../beta/saas-runtime/flags/attributes/delete | 24 +- .../saas-runtime/flags/attributes/describe | 28 +- .../beta/saas-runtime/flags/attributes/list | 30 +- .../beta/saas-runtime/flags/attributes/update | 17 +- gcloud/beta/saas-runtime/flags/create | 82 ++- gcloud/beta/saas-runtime/flags/delete | 25 +- gcloud/beta/saas-runtime/flags/describe | 35 +- gcloud/beta/saas-runtime/flags/list | 21 +- .../beta/saas-runtime/flags/releases/create | 47 +- .../beta/saas-runtime/flags/releases/delete | 22 +- .../beta/saas-runtime/flags/releases/describe | 30 +- gcloud/beta/saas-runtime/flags/releases/help | 6 +- gcloud/beta/saas-runtime/flags/releases/list | 25 +- .../beta/saas-runtime/flags/releases/update | 19 +- .../beta/saas-runtime/flags/revisions/create | 28 +- .../beta/saas-runtime/flags/revisions/delete | 33 +- .../saas-runtime/flags/revisions/describe | 36 +- gcloud/beta/saas-runtime/flags/revisions/help | 2 +- gcloud/beta/saas-runtime/flags/revisions/list | 33 +- .../beta/saas-runtime/flags/revisions/update | 15 +- gcloud/beta/saas-runtime/flags/update | 116 +++- gcloud/beta/saas-runtime/saas/create | 18 +- gcloud/beta/saas-runtime/saas/update | 16 + gcloud/beta/saas-runtime/unit-kinds/create | 19 + gcloud/beta/saas-runtime/unit-kinds/update | 23 + gcloud/beta/saas-runtime/units/create | 7 +- gcloud/beta/saas-runtime/units/update | 11 + gcloud/beta/scc/sources/help | 3 + gcloud/beta/scc/sources/list | 83 +++ gcloud/beta/service-health/artifacts/describe | 80 +++ gcloud/beta/service-health/artifacts/help | 30 ++ gcloud/beta/service-health/artifacts/list | 93 ++++ gcloud/beta/service-health/events/describe | 82 +++ gcloud/beta/service-health/events/help | 32 ++ gcloud/beta/service-health/events/list | 104 ++++ gcloud/beta/service-health/help | 39 ++ .../organization-events/describe | 85 +++ .../service-health/organization-events/help | 34 ++ .../service-health/organization-events/list | 112 ++++ .../organization-impacts/describe | 85 +++ .../service-health/organization-impacts/help | 34 ++ .../service-health/organization-impacts/list | 105 ++++ gcloud/beta/services/api-keys/update | 21 +- gcloud/beta/spanner/databases/update | 13 +- gcloud/beta/sql/instances/create | 27 +- gcloud/beta/sql/instances/help | 4 + gcloud/beta/sql/instances/patch | 29 +- .../instances/pre-check-major-version-upgrade | 53 ++ gcloud/beta/vector-search/collections/create | 27 +- gcloud/beta/workbench/instances/create | 19 +- gcloud/beta/workbench/instances/update | 9 +- gcloud/beta/workload-identity/help | 28 + .../workload-identity/service-agents/generate | 76 +++ .../workload-identity/service-agents/help | 29 + gcloud/beta/workstations/clusters/create | 9 +- gcloud/beta/workstations/clusters/help | 3 + gcloud/beta/workstations/clusters/update | 111 ++++ gcloud/beta/workstations/ssh | 6 +- gcloud/beta/workstations/start-tcp-tunnel | 6 +- .../security-gateways/add-iam-policy-binding | 95 ++++ .../applications/add-iam-policy-binding | 105 ++++ .../security-gateways/applications/help | 6 + .../applications/remove-iam-policy-binding | 106 ++++ gcloud/beyondcorp/security-gateways/create | 17 +- gcloud/beyondcorp/security-gateways/help | 6 + .../remove-iam-policy-binding | 96 ++++ gcloud/beyondcorp/security-gateways/update | 28 - gcloud/biglake/iceberg/catalogs/create | 2 +- gcloud/biglake/iceberg/catalogs/update | 8 +- gcloud/biglake/iceberg/help | 3 + gcloud/biglake/iceberg/tables/create | 126 +++++ gcloud/biglake/iceberg/tables/delete | 72 +++ gcloud/biglake/iceberg/tables/describe | 76 +++ gcloud/biglake/iceberg/tables/get-iam-policy | 100 ++++ gcloud/biglake/iceberg/tables/help | 48 ++ gcloud/biglake/iceberg/tables/list | 97 ++++ gcloud/biglake/iceberg/tables/register | 89 ++++ gcloud/biglake/iceberg/tables/set-iam-policy | 80 +++ gcloud/biglake/iceberg/tables/update | 96 ++++ gcloud/bigtable/instances/create | 13 +- gcloud/bigtable/instances/tables/create | 36 +- gcloud/bigtable/instances/tables/update | 48 +- gcloud/bigtable/instances/update | 11 +- gcloud/bigtable/tables/create | 35 +- gcloud/bigtable/tables/update | 47 +- .../certificate-manager/certificates/create | 3 +- .../certificate-manager/certificates/describe | 3 +- .../dns-authorizations/create | 3 +- .../dns-authorizations/delete | 3 +- .../dns-authorizations/describe | 3 +- .../dns-authorizations/list | 3 +- .../dns-authorizations/update | 3 +- .../issuance-configs/create | 3 +- .../issuance-configs/delete | 3 +- .../issuance-configs/describe | 3 +- .../certificate-manager/issuance-configs/list | 3 +- .../issuance-configs/update | 3 +- .../certificate-manager/operations/describe | 3 +- gcloud/certificate-manager/operations/list | 3 +- .../certificate-manager/trust-configs/create | 3 +- .../certificate-manager/trust-configs/delete | 3 +- .../trust-configs/describe | 3 +- .../certificate-manager/trust-configs/export | 3 +- .../certificate-manager/trust-configs/import | 3 +- gcloud/certificate-manager/trust-configs/list | 3 +- .../certificate-manager/trust-configs/update | 3 +- gcloud/compute/addresses/help | 3 + gcloud/compute/addresses/update | 87 +++ .../backend-buckets/add-iam-policy-binding | 58 +- gcloud/compute/backend-buckets/create | 13 +- gcloud/compute/backend-buckets/delete | 13 +- gcloud/compute/backend-buckets/describe | 12 +- gcloud/compute/backend-buckets/get-iam-policy | 45 +- gcloud/compute/backend-buckets/list | 14 +- .../backend-buckets/remove-iam-policy-binding | 58 +- gcloud/compute/backend-buckets/set-iam-policy | 52 +- gcloud/compute/backend-buckets/update | 11 +- gcloud/compute/backend-services/add-backend | 55 +- gcloud/compute/backend-services/update | 11 +- .../compute/backend-services/update-backend | 43 +- gcloud/compute/commitments/create | 4 +- gcloud/compute/composite-health-checks/create | 95 ++++ gcloud/compute/composite-health-checks/delete | 75 +++ .../compute/composite-health-checks/describe | 70 +++ .../composite-health-checks/get-health | 41 ++ gcloud/compute/composite-health-checks/help | 42 ++ gcloud/compute/composite-health-checks/list | 78 +++ gcloud/compute/composite-health-checks/update | 97 ++++ gcloud/compute/disks/bulk/create | 41 +- gcloud/compute/disks/bulk/help | 3 +- gcloud/compute/disks/help | 4 +- gcloud/compute/disks/update | 6 +- gcloud/compute/disks/update-kms-key | 12 +- gcloud/compute/future-reservations/create | 4 + .../global-vm-extension-policies/create | 144 +++++ .../global-vm-extension-policies/delete | 57 ++ .../global-vm-extension-policies/describe | 36 ++ .../compute/global-vm-extension-policies/help | 40 ++ .../global-vm-extension-policies}/list | 23 +- .../global-vm-extension-policies/update | 149 ++++++ .../health-aggregation-policies/create | 115 ++++ .../health-aggregation-policies/delete | 76 +++ .../health-aggregation-policies/describe | 71 +++ .../compute/health-aggregation-policies/help | 40 ++ .../compute/health-aggregation-policies/list | 79 +++ .../health-aggregation-policies/update | 110 ++++ gcloud/compute/health-sources/create | 101 ++++ gcloud/compute/health-sources/delete | 73 +++ gcloud/compute/health-sources/describe | 69 +++ gcloud/compute/health-sources/get-health | 41 ++ gcloud/compute/health-sources/help | 42 ++ gcloud/compute/health-sources/list | 78 +++ gcloud/compute/health-sources/update | 96 ++++ gcloud/compute/help | 24 + gcloud/compute/instances/add-metadata | 4 +- gcloud/compute/instances/update-from-file | 7 +- gcloud/compute/instant-snapshot-groups/create | 93 ++++ gcloud/compute/instant-snapshot-groups/delete | 75 +++ .../compute/instant-snapshot-groups/describe | 83 +++ gcloud/compute/instant-snapshot-groups/help | 37 ++ gcloud/compute/instant-snapshot-groups/list | 97 ++++ .../interconnects/groups/create-members | 31 +- gcloud/compute/migration/image-imports/help | 8 +- gcloud/compute/network-endpoint-groups/create | 10 +- .../networks/peerings/cancel-request-delete | 51 ++ gcloud/compute/networks/peerings/help | 3 + gcloud/compute/project-info/add-metadata | 4 +- .../resource-policies/create/group-placement | 11 + .../resource-policies/create/workload-policy | 11 + gcloud/compute/rollout-plans/create | 69 +++ gcloud/compute/rollout-plans/delete | 50 ++ gcloud/compute/rollout-plans/describe | 54 ++ gcloud/compute/rollout-plans/help | 37 ++ gcloud/compute/rollout-plans/list | 68 +++ gcloud/compute/rollouts/cancel | 53 ++ gcloud/compute/rollouts/delete | 48 ++ gcloud/compute/rollouts/describe | 53 ++ gcloud/compute/rollouts/help | 36 ++ gcloud/compute/rollouts/list | 67 +++ gcloud/compute/snapshots/help | 2 +- gcloud/compute/snapshots/update-kms-key | 8 +- .../compute/zone-vm-extension-policies/create | 139 +++++ .../compute/zone-vm-extension-policies/delete | 57 ++ .../zone-vm-extension-policies/describe | 57 ++ .../compute/zone-vm-extension-policies/help | 40 ++ .../compute/zone-vm-extension-policies/list | 68 +++ .../compute/zone-vm-extension-policies/update | 134 +++++ gcloud/config/get | 19 +- gcloud/config/help | 19 +- gcloud/config/list | 19 +- gcloud/config/set | 19 +- gcloud/config/unset | 19 +- gcloud/container/clusters/create | 102 +++- gcloud/container/clusters/create-auto | 34 ++ gcloud/container/clusters/update | 41 +- .../fleet/memberships/get-credentials | 7 + gcloud/container/help | 3 + .../container/hub/memberships/get-credentials | 7 + gcloud/container/node-pools/create | 42 +- gcloud/container/node-pools/update | 32 ++ gcloud/container/workload/help | 20 + gcloud/container/workload/profiles/help | 20 + .../workload/profiles/manifests/create | 43 ++ .../workload/profiles/manifests/help | 20 + .../connection-profiles/create/postgresql | 4 +- .../database-migration/migration-jobs/create | 9 + .../database-migration/migration-jobs/update | 9 +- gcloud/dataflow/flex-template/run | 5 + gcloud/dataplex/context/help | 2 +- gcloud/dataplex/context/lookup | 36 +- gcloud/dataplex/datascans/create/data-profile | 15 +- gcloud/dataplex/datascans/create/data-quality | 15 +- gcloud/dataplex/entries/help | 3 + gcloud/dataplex/entries/modify | 288 ++++++++++ gcloud/dataproc/clusters/create | 120 ++++- .../workflow-templates/set-managed-cluster | 121 ++++- gcloud/firestore/databases/create | 9 + gcloud/firestore/databases/update | 7 +- gcloud/firestore/fields/ttls/update | 24 +- gcloud/firestore/indexes/composite/create | 2 +- gcloud/iam/help | 2 +- gcloud/iam/policy-bindings/help | 4 +- .../iam/workforce-pools/providers/create-oidc | 3 + .../iam/workforce-pools/providers/update-oidc | 3 + gcloud/kms/asymmetric-sign | 7 +- gcloud/kms/key-handles/create | 4 +- gcloud/kms/single-tenant-hsm/create | 6 +- gcloud/kms/single-tenant-hsm/describe | 10 +- .../kms/single-tenant-hsm/proposal/describe | 14 +- gcloud/logging/help | 6 + gcloud/logging/recent-queries/help | 21 + gcloud/logging/recent-queries/list | 89 ++++ gcloud/logging/saved-queries/create | 101 ++++ gcloud/logging/saved-queries/delete | 59 +++ gcloud/logging/saved-queries/describe | 60 +++ gcloud/logging/saved-queries/help | 32 ++ gcloud/logging/saved-queries/list | 89 ++++ gcloud/logging/saved-queries/update | 105 ++++ gcloud/lustre/instances/update | 16 - gcloud/memorystore/instances/create | 12 + gcloud/memorystore/instances/update | 12 + gcloud/migration/vms/image-imports/help | 16 +- gcloud/netapp/storage-pools/create | 18 +- gcloud/netapp/storage-pools/execute | 61 +++ gcloud/netapp/storage-pools/help | 3 + gcloud/netapp/volumes/create | 12 + gcloud/network-connectivity/help | 3 + .../spokes/linked-producer-vpc-network/create | 5 +- .../spokes/linked-vpc-network/create | 5 +- gcloud/network-connectivity/transports/create | 157 ++++++ gcloud/network-connectivity/transports/delete | 70 +++ .../network-connectivity/transports/describe | 66 +++ gcloud/network-connectivity/transports/help | 45 ++ gcloud/network-connectivity/transports/list | 75 +++ .../transports/remote-profiles/describe | 70 +++ .../transports/remote-profiles/help | 30 ++ .../transports/remote-profiles/list | 79 +++ gcloud/network-connectivity/transports/update | 118 +++++ .../firewall-endpoint-associations/create | 18 +- .../firewall-endpoint-associations/delete | 9 +- .../firewall-endpoint-associations/describe | 10 +- .../firewall-endpoint-associations/list | 13 +- .../firewall-endpoint-associations/update | 8 +- .../firewall-endpoints/create | 9 +- .../firewall-endpoints/delete | 9 +- .../firewall-endpoints/describe | 9 +- .../network-security/firewall-endpoints/list | 15 +- .../firewall-endpoints/update | 9 +- .../threat-prevention/describe | 77 +++ .../security-profiles/threat-prevention/help | 8 + gcloud/oracle-database/databases/help | 2 +- gcloud/oracle-database/databases/list | 34 +- gcloud/oracle-database/gi-versions/help | 2 +- gcloud/oracle-database/gi-versions/list | 29 +- .../gi-versions/minor-versions/help | 2 +- .../gi-versions/minor-versions/list | 45 +- .../oracle-database/pluggable-databases/help | 2 +- .../oracle-database/pluggable-databases/list | 30 +- gcloud/privateca/roots/list | 18 +- gcloud/redis/clusters/create | 3 +- gcloud/redis/clusters/update | 3 +- gcloud/run/deploy | 24 +- gcloud/run/help | 3 + gcloud/run/jobs/create | 24 +- gcloud/run/jobs/deploy | 24 +- gcloud/run/jobs/update | 24 +- gcloud/run/services/update | 24 +- .../run/worker-pools/add-iam-policy-binding | 139 +++++ gcloud/run/worker-pools/delete | 70 +++ gcloud/run/worker-pools/deploy | 494 ++++++++++++++++++ gcloud/run/worker-pools/describe | 64 +++ gcloud/run/worker-pools/get-iam-policy | 101 ++++ gcloud/run/worker-pools/help | 73 +++ .../locations => run/worker-pools}/list | 29 +- gcloud/run/worker-pools/logs/help | 45 ++ gcloud/run/worker-pools/logs/read | 84 +++ gcloud/run/worker-pools/logs/tail | 54 ++ .../worker-pools/remove-iam-policy-binding | 144 +++++ gcloud/run/worker-pools/replace | 46 ++ gcloud/run/worker-pools/revisions/delete | 81 +++ gcloud/run/worker-pools/revisions/describe | 56 ++ gcloud/run/worker-pools/revisions/help | 40 ++ gcloud/run/worker-pools/revisions/list | 73 +++ gcloud/run/worker-pools/set-iam-policy | 88 ++++ gcloud/run/worker-pools/update | 473 +++++++++++++++++ gcloud/run/worker-pools/update-instance-split | 133 +++++ gcloud/scc/sources/help | 3 + gcloud/scc/sources/list | 82 +++ gcloud/service-health/events/describe | 81 +++ gcloud/service-health/events/help | 31 ++ gcloud/service-health/events/list | 103 ++++ gcloud/service-health/help | 35 ++ .../organization-events/describe | 83 +++ .../service-health/organization-events/help | 31 ++ .../service-health/organization-events/list | 110 ++++ .../organization-impacts/describe | 83 +++ .../service-health/organization-impacts/help | 31 ++ .../service-health/organization-impacts/list | 104 ++++ gcloud/services/api-keys/update | 21 +- gcloud/spanner/databases/update | 13 +- gcloud/sql/instances/create | 20 + gcloud/sql/instances/patch | 20 + .../instances/pre-check-major-version-upgrade | 15 +- gcloud/storage/batch-operations/jobs/create | 45 +- gcloud/storage/objects/compose | 14 +- gcloud/vector-search/collections/create | 29 +- gcloud/workbench/instances/create | 19 +- gcloud/workbench/instances/update | 9 +- gcloud/workload-identity/help | 27 + .../workload-identity/service-agents/generate | 74 +++ gcloud/workload-identity/service-agents/help | 28 + gcloud/workstations/clusters/create | 5 +- gcloud/workstations/clusters/help | 3 + gcloud/workstations/clusters/update | 110 ++++ gcloud/workstations/ssh | 6 +- gcloud/workstations/start-tcp-tunnel | 6 +- 1261 files changed, 38952 insertions(+), 5626 deletions(-) rename gcloud/alpha/{dataplex/data-taxonomies => agent-identity/connectors}/add-iam-policy-binding (55%) rename gcloud/alpha/{dataplex/data-taxonomies => agent-identity/connectors}/get-iam-policy (56%) rename gcloud/alpha/{dataplex/data-taxonomies => agent-identity/connectors}/remove-iam-policy-binding (56%) rename gcloud/alpha/{dataplex/data-taxonomies => agent-identity/connectors}/set-iam-policy (55%) create mode 100644 gcloud/alpha/agent-identity/connectors/test-iam-permissions delete mode 100644 gcloud/alpha/agent-identity/operations/help create mode 100644 gcloud/alpha/agent-registry/agents/search create mode 100644 gcloud/alpha/agent-registry/bindings/create create mode 100644 gcloud/alpha/agent-registry/bindings/delete create mode 100644 gcloud/alpha/agent-registry/bindings/describe create mode 100644 gcloud/alpha/agent-registry/bindings/fetch-available create mode 100644 gcloud/alpha/agent-registry/bindings/list create mode 100644 gcloud/alpha/agent-registry/bindings/update create mode 100644 gcloud/alpha/agent-registry/mcp-servers/search create mode 100644 gcloud/alpha/bigtable/memory-layers/describe rename gcloud/alpha/{lifesciences/pipelines => bigtable/memory-layers}/help (57%) create mode 100644 gcloud/alpha/bigtable/memory-layers/update delete mode 100644 gcloud/alpha/container/binauthz/continuous-validation/describe delete mode 100644 gcloud/alpha/container/binauthz/continuous-validation/disable delete mode 100644 gcloud/alpha/container/binauthz/continuous-validation/enable delete mode 100644 gcloud/alpha/container/binauthz/continuous-validation/help delete mode 100644 gcloud/alpha/dataplex/data-attribute-bindings/add-iam-policy-binding delete mode 100644 gcloud/alpha/dataplex/data-attribute-bindings/create delete mode 100644 gcloud/alpha/dataplex/data-attribute-bindings/delete delete mode 100644 gcloud/alpha/dataplex/data-attribute-bindings/describe delete mode 100644 gcloud/alpha/dataplex/data-attribute-bindings/help delete mode 100644 gcloud/alpha/dataplex/data-attribute-bindings/remove-iam-policy-binding delete mode 100644 gcloud/alpha/dataplex/data-attribute-bindings/set-iam-policy delete mode 100644 gcloud/alpha/dataplex/data-attribute-bindings/update delete mode 100644 gcloud/alpha/dataplex/data-taxonomies/attributes/add-iam-policy-binding delete mode 100644 gcloud/alpha/dataplex/data-taxonomies/attributes/create delete mode 100644 gcloud/alpha/dataplex/data-taxonomies/attributes/delete delete mode 100644 gcloud/alpha/dataplex/data-taxonomies/attributes/describe delete mode 100644 gcloud/alpha/dataplex/data-taxonomies/attributes/get-iam-policy delete mode 100644 gcloud/alpha/dataplex/data-taxonomies/attributes/help delete mode 100644 gcloud/alpha/dataplex/data-taxonomies/attributes/remove-iam-policy-binding delete mode 100644 gcloud/alpha/dataplex/data-taxonomies/attributes/set-iam-policy delete mode 100644 gcloud/alpha/dataplex/data-taxonomies/attributes/update delete mode 100644 gcloud/alpha/dataplex/data-taxonomies/create delete mode 100644 gcloud/alpha/dataplex/data-taxonomies/delete delete mode 100644 gcloud/alpha/dataplex/data-taxonomies/help delete mode 100644 gcloud/alpha/dataplex/data-taxonomies/update create mode 100644 gcloud/alpha/dataplex/entries/modify create mode 100644 gcloud/alpha/design-center/spaces/application-templates/policies/create create mode 100644 gcloud/alpha/design-center/spaces/application-templates/policies/delete create mode 100644 gcloud/alpha/design-center/spaces/application-templates/policies/describe create mode 100644 gcloud/alpha/design-center/spaces/application-templates/policies/help create mode 100644 gcloud/alpha/design-center/spaces/application-templates/policies/list create mode 100644 gcloud/alpha/design-center/spaces/application-templates/policies/update create mode 100644 gcloud/alpha/fault-testing/experiment-templates/create create mode 100644 gcloud/alpha/fault-testing/experiment-templates/delete create mode 100644 gcloud/alpha/fault-testing/experiment-templates/describe create mode 100644 gcloud/alpha/fault-testing/experiment-templates/help rename gcloud/alpha/{dataplex/data-taxonomies => fault-testing/experiment-templates}/list (75%) create mode 100644 gcloud/alpha/fault-testing/experiment-templates/update create mode 100644 gcloud/alpha/fault-testing/experiments/affected-resources/describe create mode 100644 gcloud/alpha/fault-testing/experiments/affected-resources/help rename gcloud/alpha/{dataplex/data-taxonomies/attributes => fault-testing/experiments/affected-resources}/list (64%) create mode 100644 gcloud/alpha/fault-testing/experiments/create create mode 100644 gcloud/alpha/fault-testing/experiments/delete rename gcloud/alpha/{dataplex/data-taxonomies => fault-testing/experiments}/describe (50%) create mode 100644 gcloud/alpha/fault-testing/experiments/help create mode 100644 gcloud/alpha/fault-testing/experiments/list create mode 100644 gcloud/alpha/fault-testing/experiments/start create mode 100644 gcloud/alpha/fault-testing/experiments/stop create mode 100644 gcloud/alpha/fault-testing/experiments/stop-all create mode 100644 gcloud/alpha/fault-testing/help create mode 100644 gcloud/alpha/fault-testing/validations/create create mode 100644 gcloud/alpha/fault-testing/validations/delete create mode 100644 gcloud/alpha/fault-testing/validations/describe create mode 100644 gcloud/alpha/fault-testing/validations/help create mode 100644 gcloud/alpha/fault-testing/validations/list create mode 100644 gcloud/alpha/fault-testing/validations/validation-resources/describe create mode 100644 gcloud/alpha/fault-testing/validations/validation-resources/help create mode 100644 gcloud/alpha/fault-testing/validations/validation-resources/list delete mode 100644 gcloud/alpha/lifesciences/help delete mode 100644 gcloud/alpha/lifesciences/locations/describe delete mode 100644 gcloud/alpha/lifesciences/operations/help delete mode 100644 gcloud/alpha/lifesciences/pipelines/run create mode 100644 gcloud/alpha/memorystore/instances/create-token-auth-user create mode 100644 gcloud/alpha/memorystore/instances/token-auth-users/auth-tokens/delete create mode 100644 gcloud/alpha/memorystore/instances/token-auth-users/auth-tokens/describe rename gcloud/alpha/{lifesciences/locations => memorystore/instances/token-auth-users/auth-tokens}/help (53%) create mode 100644 gcloud/alpha/memorystore/instances/token-auth-users/auth-tokens/list create mode 100644 gcloud/alpha/memorystore/instances/token-auth-users/create-auth-token create mode 100644 gcloud/alpha/memorystore/instances/token-auth-users/delete create mode 100644 gcloud/alpha/memorystore/instances/token-auth-users/describe create mode 100644 gcloud/alpha/memorystore/instances/token-auth-users/help create mode 100644 gcloud/alpha/memorystore/instances/token-auth-users/list rename gcloud/alpha/{dataplex/data-attribute-bindings/get-iam-policy => netapp/storage-pools/list-backup-configs} (59%) create mode 100644 gcloud/alpha/netapp/storage-pools/restore-volume create mode 100644 gcloud/alpha/netapp/storage-pools/update-backup-config create mode 100644 gcloud/alpha/network-management/network-monitoring-providers/generate-monitoring-point-config create mode 100644 gcloud/alpha/network-management/network-monitoring-providers/monitoring-points/download-recreate-install-script create mode 100644 gcloud/alpha/network-management/network-monitoring-providers/monitoring-points/download-server-connect-config create mode 100644 gcloud/alpha/network-security/security-profiles/threat-prevention/describe create mode 100644 gcloud/alpha/number-registry/custom-ranges/create create mode 100644 gcloud/alpha/number-registry/custom-ranges/delete create mode 100644 gcloud/alpha/number-registry/custom-ranges/describe create mode 100644 gcloud/alpha/number-registry/custom-ranges/find-free-ip-ranges create mode 100644 gcloud/alpha/number-registry/custom-ranges/help create mode 100644 gcloud/alpha/number-registry/custom-ranges/list create mode 100644 gcloud/alpha/number-registry/custom-ranges/show-utilization create mode 100644 gcloud/alpha/number-registry/custom-ranges/update create mode 100644 gcloud/alpha/number-registry/discovered-ranges/describe create mode 100644 gcloud/alpha/number-registry/discovered-ranges/find-free-ip-ranges create mode 100644 gcloud/alpha/number-registry/discovered-ranges/help create mode 100644 gcloud/alpha/number-registry/discovered-ranges/list create mode 100644 gcloud/alpha/number-registry/discovered-ranges/show-utilization create mode 100644 gcloud/alpha/number-registry/help create mode 100644 gcloud/alpha/number-registry/ipam-admin-scopes/check-availability create mode 100644 gcloud/alpha/number-registry/ipam-admin-scopes/cleanup create mode 100644 gcloud/alpha/number-registry/ipam-admin-scopes/create create mode 100644 gcloud/alpha/number-registry/ipam-admin-scopes/delete create mode 100644 gcloud/alpha/number-registry/ipam-admin-scopes/describe create mode 100644 gcloud/alpha/number-registry/ipam-admin-scopes/disable create mode 100644 gcloud/alpha/number-registry/ipam-admin-scopes/help create mode 100644 gcloud/alpha/number-registry/ipam-admin-scopes/list create mode 100644 gcloud/alpha/number-registry/ipam-admin-scopes/update rename gcloud/alpha/{lifesciences/operations/describe => number-registry/operations/cancel} (67%) rename gcloud/alpha/{lifesciences/operations/cancel => number-registry/operations/delete} (70%) rename gcloud/{beta/lifesciences => alpha/number-registry}/operations/describe (56%) create mode 100644 gcloud/alpha/number-registry/operations/help rename gcloud/alpha/{lifesciences => number-registry}/operations/list (71%) rename gcloud/alpha/{lifesciences => number-registry}/operations/wait (71%) create mode 100644 gcloud/alpha/number-registry/realms/create create mode 100644 gcloud/alpha/number-registry/realms/delete create mode 100644 gcloud/alpha/number-registry/realms/describe create mode 100644 gcloud/alpha/number-registry/realms/help create mode 100644 gcloud/alpha/number-registry/realms/list create mode 100644 gcloud/alpha/number-registry/realms/update create mode 100644 gcloud/alpha/number-registry/registry-books/create create mode 100644 gcloud/alpha/number-registry/registry-books/delete create mode 100644 gcloud/alpha/number-registry/registry-books/describe create mode 100644 gcloud/alpha/number-registry/registry-books/help create mode 100644 gcloud/alpha/number-registry/registry-books/list create mode 100644 gcloud/alpha/number-registry/registry-books/search-ip-resources create mode 100644 gcloud/alpha/number-registry/registry-books/update create mode 100644 gcloud/alpha/redis/clusters/create-token-auth-user create mode 100644 gcloud/alpha/redis/clusters/token-auth-users/auth-tokens/delete create mode 100644 gcloud/alpha/redis/clusters/token-auth-users/auth-tokens/describe create mode 100644 gcloud/alpha/redis/clusters/token-auth-users/auth-tokens/help create mode 100644 gcloud/alpha/redis/clusters/token-auth-users/auth-tokens/list create mode 100644 gcloud/alpha/redis/clusters/token-auth-users/create-auth-token create mode 100644 gcloud/alpha/redis/clusters/token-auth-users/delete create mode 100644 gcloud/alpha/redis/clusters/token-auth-users/describe create mode 100644 gcloud/alpha/redis/clusters/token-auth-users/help create mode 100644 gcloud/alpha/redis/clusters/token-auth-users/list create mode 100644 gcloud/alpha/run/instances/dev/help create mode 100644 gcloud/alpha/run/instances/logs/help create mode 100644 gcloud/alpha/run/instances/logs/read create mode 100644 gcloud/alpha/run/instances/logs/tail create mode 100644 gcloud/alpha/run/instances/replace create mode 100644 gcloud/alpha/scc/sources/list create mode 100644 gcloud/alpha/workload-identity/help create mode 100644 gcloud/alpha/workload-identity/service-agents/generate create mode 100644 gcloud/alpha/workload-identity/service-agents/help create mode 100644 gcloud/alpha/workstations/clusters/update create mode 100644 gcloud/artifacts/projects/describe create mode 100644 gcloud/artifacts/projects/help create mode 100644 gcloud/artifacts/projects/update create mode 100644 gcloud/beta/ai/semantic-governance-policies/create create mode 100644 gcloud/beta/ai/semantic-governance-policies/delete create mode 100644 gcloud/beta/ai/semantic-governance-policies/describe create mode 100644 gcloud/beta/ai/semantic-governance-policies/help create mode 100644 gcloud/beta/ai/semantic-governance-policies/list create mode 100644 gcloud/beta/ai/semantic-governance-policies/update create mode 100644 gcloud/beta/ai/semantic-governance-policy-engine/describe create mode 100644 gcloud/beta/ai/semantic-governance-policy-engine/help create mode 100644 gcloud/beta/ai/semantic-governance-policy-engine/update create mode 100644 gcloud/beta/app-optimize/help create mode 100644 gcloud/beta/app-optimize/reports/create create mode 100644 gcloud/beta/app-optimize/reports/delete rename gcloud/beta/{lifesciences/operations/wait => app-optimize/reports/describe} (54%) create mode 100644 gcloud/beta/app-optimize/reports/help create mode 100644 gcloud/beta/app-optimize/reports/list create mode 100644 gcloud/beta/app-optimize/reports/read create mode 100644 gcloud/beta/backup-dr/backup-plan-associations/create create mode 100644 gcloud/beta/backup-dr/backup-plan-associations/delete create mode 100644 gcloud/beta/backup-dr/backup-plan-associations/describe create mode 100644 gcloud/beta/backup-dr/backup-plan-associations/fetch-for-resource-type create mode 100644 gcloud/beta/backup-dr/backup-plan-associations/help create mode 100644 gcloud/beta/backup-dr/backup-plan-associations/list create mode 100644 gcloud/beta/backup-dr/backup-plan-associations/trigger-backup create mode 100644 gcloud/beta/backup-dr/backup-plan-associations/update create mode 100644 gcloud/beta/backup-dr/backup-plan-revisions/describe create mode 100644 gcloud/beta/backup-dr/backup-plan-revisions/help create mode 100644 gcloud/beta/backup-dr/backup-plan-revisions/list create mode 100644 gcloud/beta/backup-dr/backup-plans/create create mode 100644 gcloud/beta/backup-dr/backup-plans/delete create mode 100644 gcloud/beta/backup-dr/backup-plans/describe create mode 100644 gcloud/beta/backup-dr/backup-plans/help rename gcloud/beta/{lifesciences/operations => backup-dr/backup-plans}/list (72%) create mode 100644 gcloud/beta/backup-dr/backup-plans/update create mode 100644 gcloud/beta/backup-dr/backup-vaults/create create mode 100644 gcloud/beta/backup-dr/backup-vaults/delete create mode 100644 gcloud/beta/backup-dr/backup-vaults/describe create mode 100644 gcloud/beta/backup-dr/backup-vaults/help rename gcloud/{alpha/dataplex/data-attribute-bindings => beta/backup-dr/backup-vaults}/list (73%) create mode 100644 gcloud/beta/backup-dr/backup-vaults/update create mode 100644 gcloud/beta/backup-dr/backups/delete create mode 100644 gcloud/beta/backup-dr/backups/describe create mode 100644 gcloud/beta/backup-dr/backups/fetch-for-resource-type create mode 100644 gcloud/beta/backup-dr/backups/help create mode 100644 gcloud/beta/backup-dr/backups/list create mode 100644 gcloud/beta/backup-dr/backups/restore/compute create mode 100644 gcloud/beta/backup-dr/backups/restore/disk create mode 100644 gcloud/beta/backup-dr/backups/restore/help create mode 100644 gcloud/beta/backup-dr/backups/update create mode 100644 gcloud/beta/backup-dr/data-source-references/describe create mode 100644 gcloud/beta/backup-dr/data-source-references/fetch-for-resource-type create mode 100644 gcloud/beta/backup-dr/data-source-references/help create mode 100644 gcloud/beta/backup-dr/data-source-references/list create mode 100644 gcloud/beta/backup-dr/data-sources/describe create mode 100644 gcloud/beta/backup-dr/data-sources/help create mode 100644 gcloud/beta/backup-dr/data-sources/list create mode 100644 gcloud/beta/backup-dr/resource-backup-config/help create mode 100644 gcloud/beta/backup-dr/resource-backup-config/list create mode 100644 gcloud/beta/backup-dr/service-config/help create mode 100644 gcloud/beta/backup-dr/service-config/init create mode 100644 gcloud/beta/beyondcorp/security-gateways/add-iam-policy-binding create mode 100644 gcloud/beta/beyondcorp/security-gateways/applications/add-iam-policy-binding create mode 100644 gcloud/beta/beyondcorp/security-gateways/applications/remove-iam-policy-binding create mode 100644 gcloud/beta/beyondcorp/security-gateways/remove-iam-policy-binding create mode 100644 gcloud/beta/bigtable/memory-layers/describe create mode 100644 gcloud/beta/bigtable/memory-layers/help create mode 100644 gcloud/beta/bigtable/memory-layers/update delete mode 100644 gcloud/beta/lifesciences/help delete mode 100644 gcloud/beta/lifesciences/locations/describe delete mode 100644 gcloud/beta/lifesciences/locations/help delete mode 100644 gcloud/beta/lifesciences/operations/help delete mode 100644 gcloud/beta/lifesciences/pipelines/help delete mode 100644 gcloud/beta/lifesciences/pipelines/run create mode 100644 gcloud/beta/memorystore/instances/create-token-auth-user create mode 100644 gcloud/beta/memorystore/instances/token-auth-users/auth-tokens/delete create mode 100644 gcloud/beta/memorystore/instances/token-auth-users/auth-tokens/describe create mode 100644 gcloud/beta/memorystore/instances/token-auth-users/auth-tokens/help create mode 100644 gcloud/beta/memorystore/instances/token-auth-users/auth-tokens/list create mode 100644 gcloud/beta/memorystore/instances/token-auth-users/create-auth-token create mode 100644 gcloud/beta/memorystore/instances/token-auth-users/delete create mode 100644 gcloud/beta/memorystore/instances/token-auth-users/describe create mode 100644 gcloud/beta/memorystore/instances/token-auth-users/help create mode 100644 gcloud/beta/memorystore/instances/token-auth-users/list create mode 100644 gcloud/beta/netapp/storage-pools/list-backup-configs create mode 100644 gcloud/beta/netapp/storage-pools/restore-volume create mode 100644 gcloud/beta/netapp/storage-pools/update-backup-config create mode 100644 gcloud/beta/network-security/security-profiles/threat-prevention/describe create mode 100644 gcloud/beta/network-services/agent-gateways/delete rename gcloud/beta/{lifesciences/operations/cancel => network-services/agent-gateways/describe} (50%) create mode 100644 gcloud/beta/network-services/agent-gateways/export create mode 100644 gcloud/beta/network-services/agent-gateways/help create mode 100644 gcloud/beta/network-services/agent-gateways/import create mode 100644 gcloud/beta/network-services/agent-gateways/list create mode 100644 gcloud/beta/redis/clusters/create-token-auth-user create mode 100644 gcloud/beta/redis/clusters/token-auth-users/auth-tokens/delete create mode 100644 gcloud/beta/redis/clusters/token-auth-users/auth-tokens/describe create mode 100644 gcloud/beta/redis/clusters/token-auth-users/auth-tokens/help create mode 100644 gcloud/beta/redis/clusters/token-auth-users/auth-tokens/list create mode 100644 gcloud/beta/redis/clusters/token-auth-users/create-auth-token create mode 100644 gcloud/beta/redis/clusters/token-auth-users/delete create mode 100644 gcloud/beta/redis/clusters/token-auth-users/describe create mode 100644 gcloud/beta/redis/clusters/token-auth-users/help create mode 100644 gcloud/beta/redis/clusters/token-auth-users/list create mode 100644 gcloud/beta/scc/sources/list create mode 100644 gcloud/beta/service-health/artifacts/describe create mode 100644 gcloud/beta/service-health/artifacts/help create mode 100644 gcloud/beta/service-health/artifacts/list create mode 100644 gcloud/beta/service-health/events/describe create mode 100644 gcloud/beta/service-health/events/help create mode 100644 gcloud/beta/service-health/events/list create mode 100644 gcloud/beta/service-health/help create mode 100644 gcloud/beta/service-health/organization-events/describe create mode 100644 gcloud/beta/service-health/organization-events/help create mode 100644 gcloud/beta/service-health/organization-events/list create mode 100644 gcloud/beta/service-health/organization-impacts/describe create mode 100644 gcloud/beta/service-health/organization-impacts/help create mode 100644 gcloud/beta/service-health/organization-impacts/list create mode 100644 gcloud/beta/sql/instances/pre-check-major-version-upgrade create mode 100644 gcloud/beta/workload-identity/help create mode 100644 gcloud/beta/workload-identity/service-agents/generate create mode 100644 gcloud/beta/workload-identity/service-agents/help create mode 100644 gcloud/beta/workstations/clusters/update create mode 100644 gcloud/beyondcorp/security-gateways/add-iam-policy-binding create mode 100644 gcloud/beyondcorp/security-gateways/applications/add-iam-policy-binding create mode 100644 gcloud/beyondcorp/security-gateways/applications/remove-iam-policy-binding create mode 100644 gcloud/beyondcorp/security-gateways/remove-iam-policy-binding create mode 100644 gcloud/biglake/iceberg/tables/create create mode 100644 gcloud/biglake/iceberg/tables/delete create mode 100644 gcloud/biglake/iceberg/tables/describe create mode 100644 gcloud/biglake/iceberg/tables/get-iam-policy create mode 100644 gcloud/biglake/iceberg/tables/help create mode 100644 gcloud/biglake/iceberg/tables/list create mode 100644 gcloud/biglake/iceberg/tables/register create mode 100644 gcloud/biglake/iceberg/tables/set-iam-policy create mode 100644 gcloud/biglake/iceberg/tables/update create mode 100644 gcloud/compute/addresses/update create mode 100644 gcloud/compute/composite-health-checks/create create mode 100644 gcloud/compute/composite-health-checks/delete create mode 100644 gcloud/compute/composite-health-checks/describe create mode 100644 gcloud/compute/composite-health-checks/get-health create mode 100644 gcloud/compute/composite-health-checks/help create mode 100644 gcloud/compute/composite-health-checks/list create mode 100644 gcloud/compute/composite-health-checks/update create mode 100644 gcloud/compute/global-vm-extension-policies/create create mode 100644 gcloud/compute/global-vm-extension-policies/delete create mode 100644 gcloud/compute/global-vm-extension-policies/describe create mode 100644 gcloud/compute/global-vm-extension-policies/help rename gcloud/{beta/lifesciences/locations => compute/global-vm-extension-policies}/list (76%) create mode 100644 gcloud/compute/global-vm-extension-policies/update create mode 100644 gcloud/compute/health-aggregation-policies/create create mode 100644 gcloud/compute/health-aggregation-policies/delete create mode 100644 gcloud/compute/health-aggregation-policies/describe create mode 100644 gcloud/compute/health-aggregation-policies/help create mode 100644 gcloud/compute/health-aggregation-policies/list create mode 100644 gcloud/compute/health-aggregation-policies/update create mode 100644 gcloud/compute/health-sources/create create mode 100644 gcloud/compute/health-sources/delete create mode 100644 gcloud/compute/health-sources/describe create mode 100644 gcloud/compute/health-sources/get-health create mode 100644 gcloud/compute/health-sources/help create mode 100644 gcloud/compute/health-sources/list create mode 100644 gcloud/compute/health-sources/update create mode 100644 gcloud/compute/instant-snapshot-groups/create create mode 100644 gcloud/compute/instant-snapshot-groups/delete create mode 100644 gcloud/compute/instant-snapshot-groups/describe create mode 100644 gcloud/compute/instant-snapshot-groups/help create mode 100644 gcloud/compute/instant-snapshot-groups/list create mode 100644 gcloud/compute/networks/peerings/cancel-request-delete create mode 100644 gcloud/compute/rollout-plans/create create mode 100644 gcloud/compute/rollout-plans/delete create mode 100644 gcloud/compute/rollout-plans/describe create mode 100644 gcloud/compute/rollout-plans/help create mode 100644 gcloud/compute/rollout-plans/list create mode 100644 gcloud/compute/rollouts/cancel create mode 100644 gcloud/compute/rollouts/delete create mode 100644 gcloud/compute/rollouts/describe create mode 100644 gcloud/compute/rollouts/help create mode 100644 gcloud/compute/rollouts/list create mode 100644 gcloud/compute/zone-vm-extension-policies/create create mode 100644 gcloud/compute/zone-vm-extension-policies/delete create mode 100644 gcloud/compute/zone-vm-extension-policies/describe create mode 100644 gcloud/compute/zone-vm-extension-policies/help create mode 100644 gcloud/compute/zone-vm-extension-policies/list create mode 100644 gcloud/compute/zone-vm-extension-policies/update create mode 100644 gcloud/container/workload/help create mode 100644 gcloud/container/workload/profiles/help create mode 100644 gcloud/container/workload/profiles/manifests/create create mode 100644 gcloud/container/workload/profiles/manifests/help create mode 100644 gcloud/dataplex/entries/modify create mode 100644 gcloud/logging/recent-queries/help create mode 100644 gcloud/logging/recent-queries/list create mode 100644 gcloud/logging/saved-queries/create create mode 100644 gcloud/logging/saved-queries/delete create mode 100644 gcloud/logging/saved-queries/describe create mode 100644 gcloud/logging/saved-queries/help create mode 100644 gcloud/logging/saved-queries/list create mode 100644 gcloud/logging/saved-queries/update create mode 100644 gcloud/netapp/storage-pools/execute create mode 100644 gcloud/network-connectivity/transports/create create mode 100644 gcloud/network-connectivity/transports/delete create mode 100644 gcloud/network-connectivity/transports/describe create mode 100644 gcloud/network-connectivity/transports/help create mode 100644 gcloud/network-connectivity/transports/list create mode 100644 gcloud/network-connectivity/transports/remote-profiles/describe create mode 100644 gcloud/network-connectivity/transports/remote-profiles/help create mode 100644 gcloud/network-connectivity/transports/remote-profiles/list create mode 100644 gcloud/network-connectivity/transports/update create mode 100644 gcloud/network-security/security-profiles/threat-prevention/describe create mode 100644 gcloud/run/worker-pools/add-iam-policy-binding create mode 100644 gcloud/run/worker-pools/delete create mode 100644 gcloud/run/worker-pools/deploy create mode 100644 gcloud/run/worker-pools/describe create mode 100644 gcloud/run/worker-pools/get-iam-policy create mode 100644 gcloud/run/worker-pools/help rename gcloud/{alpha/lifesciences/locations => run/worker-pools}/list (71%) create mode 100644 gcloud/run/worker-pools/logs/help create mode 100644 gcloud/run/worker-pools/logs/read create mode 100644 gcloud/run/worker-pools/logs/tail create mode 100644 gcloud/run/worker-pools/remove-iam-policy-binding create mode 100644 gcloud/run/worker-pools/replace create mode 100644 gcloud/run/worker-pools/revisions/delete create mode 100644 gcloud/run/worker-pools/revisions/describe create mode 100644 gcloud/run/worker-pools/revisions/help create mode 100644 gcloud/run/worker-pools/revisions/list create mode 100644 gcloud/run/worker-pools/set-iam-policy create mode 100644 gcloud/run/worker-pools/update create mode 100644 gcloud/run/worker-pools/update-instance-split create mode 100644 gcloud/scc/sources/list create mode 100644 gcloud/service-health/events/describe create mode 100644 gcloud/service-health/events/help create mode 100644 gcloud/service-health/events/list create mode 100644 gcloud/service-health/help create mode 100644 gcloud/service-health/organization-events/describe create mode 100644 gcloud/service-health/organization-events/help create mode 100644 gcloud/service-health/organization-events/list create mode 100644 gcloud/service-health/organization-impacts/describe create mode 100644 gcloud/service-health/organization-impacts/help create mode 100644 gcloud/service-health/organization-impacts/list create mode 100644 gcloud/workload-identity/help create mode 100644 gcloud/workload-identity/service-agents/generate create mode 100644 gcloud/workload-identity/service-agents/help create mode 100644 gcloud/workstations/clusters/update diff --git a/gcloud/_version b/gcloud/_version index 80274b60d..dad0b9030 100644 --- a/gcloud/_version +++ b/gcloud/_version @@ -1,8 +1,8 @@ -Google Cloud SDK 564.0.0 -alpha 2026.04.03 -beta 2026.04.03 +Google Cloud SDK 568.0.0 +alpha 2026.05.08 +beta 2026.05.08 bq 2.1.31 -bundled-python3-unix 3.13.11 -core 2026.04.03 +bundled-python3-unix 3.14.4 +core 2026.05.08 gcloud-crc32c 1.0.0 -gsutil 5.36 +gsutil 5.37 diff --git a/gcloud/access-context-manager/cloud-bindings/create b/gcloud/access-context-manager/cloud-bindings/create index ed40f081b..b9a4195c8 100644 --- a/gcloud/access-context-manager/cloud-bindings/create +++ b/gcloud/access-context-manager/cloud-bindings/create @@ -90,8 +90,12 @@ OPTIONAL FLAGS binding. This file contains a YAML-compliant object representing a - GcpUserAccessBinding (as described in the API reference) containing - ScopedAccessSettings only. No other binding fields are allowed. + GcpUserAccessBinding (as described in the API reference: + https://docs.cloud.google.com/access-context-manager/docs/apply-policies-to-user-groups#define_configurations_for_specific_applications) + containing ScopedAccessSettings only. No other binding fields are + allowed. For bindings tied to all workforce identities in a given org, + the ScopedAccessSettings must only contain sessionSettings within the + activeSettings list. No other fields are allowed. --dry-run-level=[DRY_RUN_LEVEL,...] The dry run access level that binds to the given group. The dry run diff --git a/gcloud/access-context-manager/cloud-bindings/update b/gcloud/access-context-manager/cloud-bindings/update index efec73ff0..a058f2275 100644 --- a/gcloud/access-context-manager/cloud-bindings/update +++ b/gcloud/access-context-manager/cloud-bindings/update @@ -94,8 +94,7 @@ OPTIONAL FLAGS settings (i.e no access levels). --binding-file=YAML_FILE - Path to the file that contains a Google Cloud Platform user access - binding. + Path to the file that contains a Google Cloud user access binding. This file contains a YAML-compliant object representing a GcpUserAccessBinding (as described in the API reference) containing diff --git a/gcloud/ai/model-garden/models/deploy b/gcloud/ai/model-garden/models/deploy index 65336bea4..62fa328fb 100644 --- a/gcloud/ai/model-garden/models/deploy +++ b/gcloud/ai/model-garden/models/deploy @@ -27,8 +27,8 @@ SYNOPSIS [--machine-type=MACHINE_TYPE] [--region=REGION] [--reservation-affinity=[key=KEY], [reservation-affinity-type=RESERVATION-AFFINITY-TYPE], - [values=VALUES]] [--spot] [--use-dedicated-endpoint] - [GCLOUD_WIDE_FLAG ...] + [values=VALUES]] [--spot] [--system-labels=[KEY=VALUE,...]] + [--use-dedicated-endpoint] [GCLOUD_WIDE_FLAG ...] EXAMPLES To deploy a Model Garden model google/gemma2/gemma2-9b under project @@ -188,6 +188,9 @@ OPTIONAL FLAGS --spot If true, schedule the deployment workload on Spot VM. + --system-labels=[KEY=VALUE,...] + System labels for Model Garden deployments. + --use-dedicated-endpoint If true, the endpoint will be exposed through a dedicated DNS. Your request to the dedicated DNS will be isolated from other users' traffic diff --git a/gcloud/alloydb/clusters/create b/gcloud/alloydb/clusters/create index 268d706e4..a1fd68cbb 100644 --- a/gcloud/alloydb/clusters/create +++ b/gcloud/alloydb/clusters/create @@ -5,6 +5,7 @@ NAME SYNOPSIS gcloud alloydb clusters create CLUSTER --password=PASSWORD --region=REGION [--allocated-ip-range-name=ALLOCATED_IP_RANGE_NAME] [--async] + [--backupdr-backup-plan=BACKUPDR_BACKUP_PLAN] [--database-version=DATABASE_VERSION] [--[no-]enable-dataplex-integration] [--enable-private-service-connect] [--network=NETWORK] [--subscription-type=SUBSCRIPTION_TYPE] @@ -61,6 +62,12 @@ OPTIONAL FLAGS Return immediately, without waiting for the operation in progress to complete. + --backupdr-backup-plan=BACKUPDR_BACKUP_PLAN + The resource name of the BackupDR backup plan to associate with the + cluster. The format should be + projects/{project}/locations/{location}/backupPlans/{backupPlanId}. + This flag cannot be used with the --async flag. + --database-version=DATABASE_VERSION Database version of the cluster. DATABASE_VERSION must be one of: POSTGRES_14, POSTGRES_15, POSTGRES_16, POSTGRES_17, POSTGRES_18. diff --git a/gcloud/alloydb/instances/create b/gcloud/alloydb/instances/create index 5900616fe..bd7820565 100644 --- a/gcloud/alloydb/instances/create +++ b/gcloud/alloydb/instances/create @@ -28,7 +28,13 @@ SYNOPSIS [--insights-config-query-string-length=INSIGHTS_CONFIG_QUERY_STRING_LENGTH] [--[no-]insights-config-record-application-tags] [--[no-]insights-config-record-client-address] - [--machine-type=MACHINE_TYPE] [--[no-]outbound-public-ip] + [--machine-type=MACHINE_TYPE] [--[no-]observability-config-enabled] + [--observability-config-max-query-string-length=OBSERVABILITY_CONFIG_MAX_QUERY_STRING_LENGTH] + [--[no-]observability-config-preserve-comments] + [--observability-config-query-plans-per-minute=OBSERVABILITY_CONFIG_QUERY_PLANS_PER_MINUTE] + [--[no-]observability-config-record-application-tags] + [--[no-]observability-config-track-active-queries] + [--observability-config-track-wait-events] [--[no-]outbound-public-ip] [--psc-auto-connections=[network=NETWORK],[project=PROJECT]] [--psc-network-attachment-uri=PSC_NETWORK_ATTACHMENT_URI] [--read-pool-node-count=READ_POOL_NODE_COUNT] @@ -227,6 +233,41 @@ OPTIONAL FLAGS z3-highmem-8-highlssd, z3-highmem-16-highlssd, z3-highmem-22-highlssd, z3-highmem-32-highlssd, z3-highmem-44-highlssd. + --[no-]observability-config-enabled + Enable enhanced query insights feature. Use + --observability-config-enabled to enable and + --no-observability-config-enabled to disable. + + --observability-config-max-query-string-length=OBSERVABILITY_CONFIG_MAX_QUERY_STRING_LENGTH + Query string length in bytes to be stored by the enhanced query + insights feature. Default length is 10k bytes. + + --[no-]observability-config-preserve-comments + Allow preservation of comments in query string recorded by the enhanced + query insights feature. + + Use --observability-config-preserve-comments to enable and + --no-observability-config-preserve-comments to disable. + + --observability-config-query-plans-per-minute=OBSERVABILITY_CONFIG_QUERY_PLANS_PER_MINUTE + Number of query plans to sample every minute. Default value is 20. + Allowed range: 0 to 200. + + --[no-]observability-config-record-application-tags + Allow application tags to be recorded by the enhanced query insights + feature. + + Use --observability-config-record-application-tags to enable and + --no-observability-config-record-application-tags to disable. + + --[no-]observability-config-track-active-queries + Track actively running queries. Use + --observability-config-track-active-queries to enable and + --no-observability-config-track-active-queries to disable. + + --observability-config-track-wait-events + Track wait events during query execution. + --[no-]outbound-public-ip Add outbound Public IP connectivity to an AlloyDB instance. Use --outbound-public-ip to enable and --no-outbound-public-ip to disable. diff --git a/gcloud/alloydb/instances/update b/gcloud/alloydb/instances/update index dc5891f6c..0cbcc5d52 100644 --- a/gcloud/alloydb/instances/update +++ b/gcloud/alloydb/instances/update @@ -28,7 +28,13 @@ SYNOPSIS [--insights-config-query-string-length=INSIGHTS_CONFIG_QUERY_STRING_LENGTH] [--[no-]insights-config-record-application-tags] [--[no-]insights-config-record-client-address] - [--machine-type=MACHINE_TYPE] [--[no-]outbound-public-ip] + [--machine-type=MACHINE_TYPE] [--[no-]observability-config-enabled] + [--observability-config-max-query-string-length=OBSERVABILITY_CONFIG_MAX_QUERY_STRING_LENGTH] + [--[no-]observability-config-preserve-comments] + [--observability-config-query-plans-per-minute=OBSERVABILITY_CONFIG_QUERY_PLANS_PER_MINUTE] + [--[no-]observability-config-record-application-tags] + [--[no-]observability-config-track-active-queries] + [--observability-config-track-wait-events] [--[no-]outbound-public-ip] [--psc-network-attachment-uri=PSC_NETWORK_ATTACHMENT_URI] [--read-pool-node-count=READ_POOL_NODE_COUNT] [--[no-]require-connectors] [--ssl-mode=SSL_MODE] @@ -213,6 +219,41 @@ OPTIONAL FLAGS z3-highmem-8-highlssd, z3-highmem-16-highlssd, z3-highmem-22-highlssd, z3-highmem-32-highlssd, z3-highmem-44-highlssd. + --[no-]observability-config-enabled + Enable enhanced query insights feature. Use + --observability-config-enabled to enable and + --no-observability-config-enabled to disable. + + --observability-config-max-query-string-length=OBSERVABILITY_CONFIG_MAX_QUERY_STRING_LENGTH + Query string length in bytes to be stored by the enhanced query + insights feature. Default length is 10k bytes. + + --[no-]observability-config-preserve-comments + Allow preservation of comments in query string recorded by the enhanced + query insights feature. + + Use --observability-config-preserve-comments to enable and + --no-observability-config-preserve-comments to disable. + + --observability-config-query-plans-per-minute=OBSERVABILITY_CONFIG_QUERY_PLANS_PER_MINUTE + Number of query plans to sample every minute. Default value is 20. + Allowed range: 0 to 200. + + --[no-]observability-config-record-application-tags + Allow application tags to be recorded by the enhanced query insights + feature. + + Use --observability-config-record-application-tags to enable and + --no-observability-config-record-application-tags to disable. + + --[no-]observability-config-track-active-queries + Track actively running queries. Use + --observability-config-track-active-queries to enable and + --no-observability-config-track-active-queries to disable. + + --observability-config-track-wait-events + Track wait events during query execution. + --[no-]outbound-public-ip Add outbound Public IP connectivity to an AlloyDB instance. Use --outbound-public-ip to enable and --no-outbound-public-ip to disable. diff --git a/gcloud/alloydb/users/create b/gcloud/alloydb/users/create index ffc927a07..6e03c867d 100644 --- a/gcloud/alloydb/users/create +++ b/gcloud/alloydb/users/create @@ -52,6 +52,9 @@ OPTIONAL FLAGS authentication IAM_BASED This database user can authenticate via IAM-based authentication + IAM_GROUP + This database user represents an IAM group whose members can + authenticate via IAM group-based authentication GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/alpha/access-context-manager/cloud-bindings/create b/gcloud/alpha/access-context-manager/cloud-bindings/create index e2383d70a..21a96b049 100644 --- a/gcloud/alpha/access-context-manager/cloud-bindings/create +++ b/gcloud/alpha/access-context-manager/cloud-bindings/create @@ -5,12 +5,14 @@ NAME SYNOPSIS gcloud alpha access-context-manager cloud-bindings create [--binding-file=YAML_FILE] [--dry-run-level=[DRY_RUN_LEVEL,...]] - [--group-key=GROUP_KEY] [--level=[LEVEL,...]] - [--organization=ORGANIZATION] + [--federated-principal=FEDERATED_PRINCIPAL] [--group-key=GROUP_KEY] + [--level=[LEVEL,...]] [--organization=ORGANIZATION] [--restricted-client-application-client-ids=[RESTRICTED_CLIENT_APPLICATION_CLIENT_IDS, ...]] [--restricted-client-application-names=[RESTRICTED_CLIENT_APPLICATION_NAMES, - ...]] [--session-length=SESSION_LENGTH] + ...]] [--service-account=SERVICE_ACCOUNT] + [--service-account-project-number=SERVICE_ACCOUNT_PROJECT_NUMBER] + [--session-length=SESSION_LENGTH] [--session-reauth-method=SESSION_REAUTH_METHOD; default="login"] [GCLOUD_WIDE_FLAG ...] @@ -39,7 +41,9 @@ DESCRIPTION then --binding-file cannot be set. If a service account is specified, then the enforcement applies only to the specified service account. If a service account project is specified, the enforcement applies to all of the service - accounts belonging to the specified project. + accounts that belong to the specified project. If a federated principal is + specified, then the enforcement applies only to the specified federated + principal. EXAMPLES To create a new global cloud access binding, run: @@ -119,6 +123,14 @@ EXAMPLES --level=accessPolicies/123/accessLevels/abc \ --organization='1234567890' + To create a new cloud access binding for all workforce identities in a + given org, run the following command: + + $ gcloud alpha access-context-manager cloud-bindings create \ + --federated-principal='principalSet://cloudresourcemanager.googl\ + eapis.com/organizations/ORG_NUMBER/type/WorkforcePool' \ + --organization='1234567890' --binding-file='binding.yaml' + To create a new cloud access binding with global session settings, specify your session length using an ISO duration string and the session-length flag. For example: @@ -156,8 +168,12 @@ FLAGS binding. This file contains a YAML-compliant object representing a - GcpUserAccessBinding (as described in the API reference) containing - ScopedAccessSettings only. No other binding fields are allowed. + GcpUserAccessBinding (as described in the API reference: + https://docs.cloud.google.com/access-context-manager/docs/apply-policies-to-user-groups#define_configurations_for_specific_applications) + containing ScopedAccessSettings only. No other binding fields are + allowed. For bindings tied to all workforce identities in a given org, + the ScopedAccessSettings must only contain sessionSettings within the + activeSettings list. No other fields are allowed. --dry-run-level=[DRY_RUN_LEVEL,...] The dry run access level that binds to the given group and restricted @@ -165,37 +181,65 @@ FLAGS enforced. Denial on a dry run access level is logged. The input must be the full identifier of an access level, such as accessPolicies/123/accessLevels/new-def. If no - restricted-client-application-client-ids or - restricted-client-application-names are provided, then the access level - is applied to the entire organization. + --restricted-client-application-client-ids or + --restricted-client-application-names are provided, then the access + level is applied to the entire organization. This parameter is not + supported for bindings tied to all workforce identities in an + organization. + + --federated-principal=FEDERATED_PRINCIPAL + IAM federated principal that this binding applies to. Can be a single + principal or a principal set. Used to assign policies to third-party + workforce or workload identities. At most one of --group-key, + --federated-principal, --service-account, or + --service-account-project-number may be specified. --group-key=GROUP_KEY Google Group ID whose members are subject to the restrictions of this - binding. + binding. At most one of --group-key, --federated-principal, + --service-account, or --service-account-project-number may be + specified. --level=[LEVEL,...] The access level that binds to the given group and restricted client applications. The input must be the full identifier of an access level, such as accessPolicies/123/accessLevels/abc. If no - restricted-client-application-client-ids or - restricted-client-application-names are provided, then the access level - is applied to the entire organization. + --restricted-client-application-client-ids or + --restricted-client-application-names are provided, then the access + level is applied to the entire organization. This parameter is not + supported for bindings tied to all workforce identities in an + organization. --organization=ORGANIZATION Parent organization for this binding. --restricted-client-application-client-ids=[RESTRICTED_CLIENT_APPLICATION_CLIENT_IDS,...] - Client IDs to which the access level is applied. + Client IDs that this access level applies to. This parameter is not + supported for bindings tied to all workforce identities in an + organization. --restricted-client-application-names=[RESTRICTED_CLIENT_APPLICATION_NAMES,...] - Application names to which the access level is applied. + Application names that the access level applies to. + + --service-account=SERVICE_ACCOUNT + Service account email that this binding applies to. Used to assign + policies to a single first-party service account. At most one of + --group-key, --federated-principal, --service-account, or + --service-account-project-number may be specified. + + --service-account-project-number=SERVICE_ACCOUNT_PROJECT_NUMBER + Project number of the project that contains the service accounts that + are subject to the restrictions of this binding. Used to assign + policies to all service accounts in a Google Cloud project. At most one + of --group-key, --federated-principal, --service-account, or + --service-account-project-number may be specified. --session-length=SESSION_LENGTH The maximum lifetime of a user session provided as an ISO 8601 duration string. For Cloud Identity users, this must be at least one hour or - zero seconds, and no more than twenty-four hours. For Workforce - Identity Federated users, this can be up to 90 days, or 14 days for - Cloud Console. Granularity is limited to seconds. + zero seconds, and no more than twenty-four hours. For workforce + identities, this can be up to 90 days, or 14 days for Cloud Console. + Granularity is limited to seconds. When --session-length=0 then users in the group attached to this binding will have infinite session length, effectively disabling @@ -210,13 +254,15 @@ FLAGS an error. Cannot set --session-length with --restricted-client-application-client-ids or --restricted-client-application-names; please use scoped access - settings. + settings. This parameter is not supported for bindings tied to all + workforce identities in an organization. --session-reauth-method=SESSION_REAUTH_METHOD; default="login" Specifies the type of re-authentication challenge given to the user when their session expires. Defaults to --session-reauth-method=login if unspecified and --session-length is set. Cannot be used when - --session-length is empty or 0. + --session-length is empty or 0. This parameter is not supported for + bindings tied to all workforce identities in an organization. SESSION_REAUTH_METHOD must be one of: diff --git a/gcloud/alpha/access-context-manager/cloud-bindings/update b/gcloud/alpha/access-context-manager/cloud-bindings/update index 8d5ebe4c0..39a49dcac 100644 --- a/gcloud/alpha/access-context-manager/cloud-bindings/update +++ b/gcloud/alpha/access-context-manager/cloud-bindings/update @@ -19,8 +19,8 @@ DESCRIPTION run level, scoped access settings, session settings, restricted client application client IDs, and restricted client application names. They can't all be empty. Session settings are incompatible with restricted client - application client IDs/names; please use scoped access settings to bind - session settings to an application. + application client IDs/names; use scoped access settings to bind session + settings to an application. EXAMPLES To update an existing access binding, run: @@ -62,6 +62,12 @@ EXAMPLES Note this is only possible for scoped access settings that exclusively hold session settings. + To update a cloud access binding for all workforce identities in a given + org, run: + + $ gcloud alpha access-context-manager cloud-bindings update \ + --binding=my-binding-id --binding-file='binding.yaml' + To update session settings, run: $ gcloud alpha access-context-manager cloud-bindings update \ @@ -115,12 +121,14 @@ OPTIONAL FLAGS settings (i.e no access levels). --binding-file=YAML_FILE - Path to the file that contains a Google Cloud Platform user access - binding. + Path to the file that contains a Google Cloud user access binding. This file contains a YAML-compliant object representing a GcpUserAccessBinding (as described in the API reference) containing - ScopedAccessSettings only. No other binding fields are allowed. + ScopedAccessSettings only. No other binding fields are allowed. For + bindings tied to all workforce identities in a given org, the + ScopedAccessSettings must only contain sessionSettings within the + activeSettings list. No other fields are allowed. The file content replaces the corresponding fields in the existing binding. Unless --append is specified. See --append help text for more @@ -129,27 +137,34 @@ OPTIONAL FLAGS --dry-run-level=[DRY_RUN_LEVEL,...] The dry run access level that replaces the existing dry run level for the given binding. The input must be the full identifier of an access - level, such as accessPolicies/123/accessLevels/new-def. + level, such as accessPolicies/123/accessLevels/new-def. This parameter + is not supported for bindings tied to all workforce identities in an + organization. --level=[LEVEL,...] The access level that replaces the existing level for the given binding. The input must be the full identifier of an access level, such - as accessPolicies/123/accessLevels/new-abc. + as accessPolicies/123/accessLevels/new-abc. This parameter is not + supported for bindings tied to all workforce identities in an + organization. --restricted-client-application-client-ids=[RESTRICTED_CLIENT_APPLICATION_CLIENT_IDS,...] The application client IDs that replace the existing application client - IDs for the restricted client applications in the given binding. + IDs for the restricted client applications in the given binding. This + parameter is not supported for bindings tied to all workforce + identities in an organization. --restricted-client-application-names=[RESTRICTED_CLIENT_APPLICATION_NAMES,...] The application names that replace the existing application names for - the restricted client applications in the given binding. + the restricted client applications in the given binding. This parameter + is not supported for bindings tied to all workforce identities in an + organization. --session-length=SESSION_LENGTH The maximum lifetime of a user session provided as an ISO 8601 duration string. For first-party users, this must be at least one hour or zero - seconds, and no more than twenty-four hours. For third-party users, - this can be up to 90 days, or 14 days for Cloud Console. Granularity is - limited to seconds. + seconds, and no more than twenty-four hours. This field is not allowed + for bindings tied to Principals. When --session-length=0 users in the group attached to this binding will have infinite session length, effectively disabling the session @@ -162,13 +177,21 @@ OPTIONAL FLAGS Setting --session-reauth-method when --session-length is empty raises an error. Cannot set --session-length on restricted client - applications; please use scoped access settings. + applications; use scoped access settings. This parameter is not + supported for bindings tied to all workforce identities in an + organization. For bindings tied to all workforce identities in an + organization, session settings can be configured by including them in + the binding-file. --session-reauth-method=SESSION_REAUTH_METHOD; default="login" Specifies the security check a user must undergo when their session expires. Defaults to --session-reauth-method=LOGIN if unspecified and --session-length is set. Cannot be used when --session-length is empty - or 0. SESSION_REAUTH_METHOD must be one of: + or 0. This parameter is not supported for bindings tied to all + workforce identities in an organization. For bindings tied to all + workforce identities in an organization, session settings can be + configured by including them in the binding-file. SESSION_REAUTH_METHOD + must be one of: login The user will be prompted to perform regular login. Users who are diff --git a/gcloud/alpha/dataplex/data-taxonomies/add-iam-policy-binding b/gcloud/alpha/agent-identity/connectors/add-iam-policy-binding similarity index 55% rename from gcloud/alpha/dataplex/data-taxonomies/add-iam-policy-binding rename to gcloud/alpha/agent-identity/connectors/add-iam-policy-binding index a882b571d..29daee649 100644 --- a/gcloud/alpha/dataplex/data-taxonomies/add-iam-policy-binding +++ b/gcloud/alpha/agent-identity/connectors/add-iam-policy-binding @@ -1,59 +1,56 @@ NAME - gcloud alpha dataplex data-taxonomies add-iam-policy-binding - add IAM - policy binding to a Dataplex Data Taxonomy + gcloud alpha agent-identity connectors add-iam-policy-binding - add IAM + policy binding to an Agent Identity connector SYNOPSIS - gcloud alpha dataplex data-taxonomies add-iam-policy-binding - (DATA_TAXONOMY : --location=LOCATION) --member=PRINCIPAL --role=ROLE + gcloud alpha agent-identity connectors add-iam-policy-binding + (CONNECTOR : --location=LOCATION) --member=PRINCIPAL --role=ROLE [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) Add IAM policy binding to a Dataplex Data Taxonomy. + (ALPHA) Add an IAM policy binding to the IAM policy of an Agent Identity + connector. One binding consists of a member, and a role. EXAMPLES - To add an IAM policy binding for the role of roles/dataplex.viewer for the - user test-user@gmail.com to Data Taxonomy test-taxonomy in location - us-central, run: + To add an IAM policy binding for the role of 'roles/iamconnectors.user' for + the user 'test-user@gmail.com' with connector 'my-connector' and location + 'us-central1', run: - $ gcloud alpha dataplex data-taxonomies add-iam-policy-binding \ - test-taxonomy --project=test-project --location=us-central1 \ - --role=roles/dataplex.viewer --member=user:foo@gmail.com - - See https://cloud.google.com/dataplex/docs/iam-roles for details of policy - role and member types. + $ gcloud alpha agent-identity connectors add-iam-policy-binding \ + my-connector --location='us-central1' \ + --member='user:test-user@gmail.com' \ + --role='roles/iamconnectors.user' POSITIONAL ARGUMENTS - Data taxonomy resource - The DataTaxonomy to add IAM policy binding to. - 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. + Connector resource - The connector for which to add the IAM policy + 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 data_taxonomy on the command line with a fully + ◆ provide the argument connector 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_TAXONOMY - ID of the data taxonomy or fully qualified identifier for the data - taxonomy. + CONNECTOR + ID of the connector or fully qualified identifier for the connector. - To set the data_taxonomy attribute: - ▸ provide the argument data_taxonomy on the command line. + To set the connector attribute: + ▸ provide the argument connector 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 of the Dataplex resource. + The location id of the connector resource. To set the location attribute: - ▸ provide the argument data_taxonomy on the command line with a - fully specified name; - ▸ provide the argument --location on the command line; - ▸ set the property dataplex/location. + ▸ provide the argument connector on the command line with a fully + specified name; + ▸ provide the argument --location on the command line. REQUIRED FLAGS --member=PRINCIPAL @@ -84,6 +81,10 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. +API REFERENCE + This command uses the iamconnectors/v1alpha API. The full documentation for + this API can be found at: https://cloud.google.com/iam/docs/ + NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct diff --git a/gcloud/alpha/agent-identity/connectors/create b/gcloud/alpha/agent-identity/connectors/create index 9a91608d9..966579401 100644 --- a/gcloud/alpha/agent-identity/connectors/create +++ b/gcloud/alpha/agent-identity/connectors/create @@ -98,14 +98,15 @@ OPTIONAL FLAGS this list is non-empty, only scopes within this list may be requested. If this list is empty, all scopes may be requested. Scopes appearing in blocked_scopes are disallowed even if they appear in allowed_scopes. - The number of allowed scopes is limited to 200. + The number of allowed scopes is limited to 200. Scopes must be + comma-separated. --blocked-scopes=[BLOCKED_SCOPES,...] List of scopes that are blocked from being requested for this connector. If a scope appears in this list, it may not be requested, even if it also appears in allowed_scopes. blocked_scopes takes precedence over allowed_scopes. The number of blocked scopes is limited - to 200. + to 200. Scopes must be comma-separated. --description=DESCRIPTION Description of the resource. Must be less than 256 characters. diff --git a/gcloud/alpha/dataplex/data-taxonomies/get-iam-policy b/gcloud/alpha/agent-identity/connectors/get-iam-policy similarity index 56% rename from gcloud/alpha/dataplex/data-taxonomies/get-iam-policy rename to gcloud/alpha/agent-identity/connectors/get-iam-policy index 7be7f522d..d8feff0f8 100644 --- a/gcloud/alpha/dataplex/data-taxonomies/get-iam-policy +++ b/gcloud/alpha/agent-identity/connectors/get-iam-policy @@ -1,59 +1,51 @@ NAME - gcloud alpha dataplex data-taxonomies get-iam-policy - retrieve a Dataplex - Data Taxonomy IAM policy + gcloud alpha agent-identity connectors get-iam-policy - get the IAM policy + for an Agent Identity connector SYNOPSIS - gcloud alpha dataplex data-taxonomies get-iam-policy - (DATA_TAXONOMY : --location=LOCATION) [--filter=EXPRESSION] - [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] - [GCLOUD_WIDE_FLAG ...] + gcloud alpha agent-identity connectors get-iam-policy + (CONNECTOR : --location=LOCATION) [--filter=EXPRESSION] [--limit=LIMIT] + [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) Displays the IAM policy associated with a Dataplex Data Taxonomy - resource. If formatted as JSON, the output can be edited and used as a - policy file for set-iam-policy. The output includes an "etag" field - identifying the version emitted and allowing detection of concurrent policy - updates. + (ALPHA) This command gets the IAM policy for a connector. EXAMPLES - To get the IAM policy of a Dataplex Data Taxonomy test-taxonomy in project - test-project under location us-central1 + To print the IAM policy for a given connector, run: - $ gcloud alpha dataplex data-taxonomies get-iam-policy \ - test-taxonomy --project=test-project --location=us-central1 + $ gcloud alpha agent-identity connectors get-iam-policy \ + my-connector --location=LOCATION POSITIONAL ARGUMENTS - Data taxonomy resource - Arguments and flags that define the Dataplex Data - Taxonomy IAM policy you want to retrieve. 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. + Connector resource - The connector for which to display the IAM policy. + The arguments in this group can be used to specify the attributes of this + resource. (NOTE) Some attributes are not given arguments in this group but + can be set in other ways. To set the project attribute: - ◆ provide the argument data_taxonomy on the command line with a fully + ◆ provide the argument connector 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_TAXONOMY - ID of the data taxonomy or fully qualified identifier for the data - taxonomy. + CONNECTOR + ID of the connector or fully qualified identifier for the connector. - To set the data_taxonomy attribute: - ▸ provide the argument data_taxonomy on the command line. + To set the connector attribute: + ▸ provide the argument connector on the command line. This positional argument must be specified if any of the other arguments in this group are specified. --location=LOCATION - Location of the Dataplex resource. + The location id of the connector resource. To set the location attribute: - ▸ provide the argument data_taxonomy on the command line with a - fully specified name; - ▸ provide the argument --location on the command line; - ▸ set the property dataplex/location. + ▸ provide the argument connector on the command line with a fully + specified name; + ▸ provide the argument --location on the command line. LIST COMMAND FLAGS --filter=EXPRESSION @@ -90,8 +82,8 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. API REFERENCE - This command uses the dataplex/v1 API. The full documentation for this API - can be found at: https://cloud.google.com/dataplex/docs + This command uses the iamconnectors/v1alpha API. The full documentation for + this API can be found at: https://cloud.google.com/iam/docs/ NOTES This command is currently in alpha and might change without notice. If this diff --git a/gcloud/alpha/agent-identity/connectors/help b/gcloud/alpha/agent-identity/connectors/help index 23a159462..612618d2f 100644 --- a/gcloud/alpha/agent-identity/connectors/help +++ b/gcloud/alpha/agent-identity/connectors/help @@ -22,6 +22,9 @@ GROUPS COMMANDS COMMAND is one of the following: + add-iam-policy-binding + (ALPHA) Add IAM policy binding to an Agent Identity connector. + create (ALPHA) Create connectors. @@ -31,6 +34,9 @@ COMMANDS describe (ALPHA) Describe connectors. + get-iam-policy + (ALPHA) Get the IAM policy for an Agent Identity connector. + list (ALPHA) List connectors. @@ -40,9 +46,18 @@ COMMANDS query-workloads (ALPHA) query connectors. + remove-iam-policy-binding + (ALPHA) Remove IAM policy binding from an Agent Identity connector. + revoke-authorization (ALPHA) revoke connectors. + set-iam-policy + (ALPHA) Set the IAM policy for an Agent Identity connector. + + test-iam-permissions + (ALPHA) Test IAM permissions for an Agent Identity connector. + undelete (ALPHA) undelete connectors. diff --git a/gcloud/alpha/dataplex/data-taxonomies/remove-iam-policy-binding b/gcloud/alpha/agent-identity/connectors/remove-iam-policy-binding similarity index 56% rename from gcloud/alpha/dataplex/data-taxonomies/remove-iam-policy-binding rename to gcloud/alpha/agent-identity/connectors/remove-iam-policy-binding index eaa6f721f..f8202fda1 100644 --- a/gcloud/alpha/dataplex/data-taxonomies/remove-iam-policy-binding +++ b/gcloud/alpha/agent-identity/connectors/remove-iam-policy-binding @@ -1,59 +1,56 @@ NAME - gcloud alpha dataplex data-taxonomies remove-iam-policy-binding - removes - IAM policy binding from a Dataplex Data Taxonomy + gcloud alpha agent-identity connectors remove-iam-policy-binding - remove + IAM policy binding from an Agent Identity connector SYNOPSIS - gcloud alpha dataplex data-taxonomies remove-iam-policy-binding - (DATA_TAXONOMY : --location=LOCATION) --member=PRINCIPAL --role=ROLE + gcloud alpha agent-identity connectors remove-iam-policy-binding + (CONNECTOR : --location=LOCATION) --member=PRINCIPAL --role=ROLE [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) Removes IAM policy binding from a Dataplex Data Taxonomy. + (ALPHA) Remove an IAM policy binding from the IAM policy of an Agent + Identity connector. One binding consists of a member, and a role. EXAMPLES - To remove an IAM policy binding for the role roles/dataplex.viewer for the - user testuser@gmail.com from an taxonomy test-taxonomy within projet - test-project in location us-central1, run: + To remove an IAM policy binding for the role of 'roles/iamconnectors.user' + for the user 'test-user@gmail.com' with connector 'my-connector' and + location 'us-central1', run: - $ gcloud alpha dataplex data-taxonomies remove-iam-policy-binding \ - test-taxonomy --project=test-project --location=us-central1 \ - --role=roles/dataplex.viewer --member=user:testuser@gmail.com - - See https://cloud.google.com/dataplex/docs/iam-roles for details of policy - role and member types. + $ gcloud alpha agent-identity connectors remove-iam-policy-binding \ + my-connector --location='us-central1' \ + --member='user:test-user@gmail.com' \ + --role='roles/iamconnectors.user' POSITIONAL ARGUMENTS - Data taxonomy resource - The DataTaxonomy to remove IAM policy binding - from The arguments in this group can be used to specify the attributes of - this resource. (NOTE) Some attributes are not given arguments in this + Connector resource - The connector from which to remove the IAM policy + 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 data_taxonomy on the command line with a fully + ◆ provide the argument connector 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_TAXONOMY - ID of the data taxonomy or fully qualified identifier for the data - taxonomy. + CONNECTOR + ID of the connector or fully qualified identifier for the connector. - To set the data_taxonomy attribute: - ▸ provide the argument data_taxonomy on the command line. + To set the connector attribute: + ▸ provide the argument connector 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 of the Dataplex resource. + The location id of the connector resource. To set the location attribute: - ▸ provide the argument data_taxonomy on the command line with a - fully specified name; - ▸ provide the argument --location on the command line; - ▸ set the property dataplex/location. + ▸ provide the argument connector on the command line with a fully + specified name; + ▸ provide the argument --location on the command line. REQUIRED FLAGS --member=PRINCIPAL @@ -85,6 +82,10 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. +API REFERENCE + This command uses the iamconnectors/v1alpha API. The full documentation for + this API can be found at: https://cloud.google.com/iam/docs/ + NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct diff --git a/gcloud/alpha/dataplex/data-taxonomies/set-iam-policy b/gcloud/alpha/agent-identity/connectors/set-iam-policy similarity index 55% rename from gcloud/alpha/dataplex/data-taxonomies/set-iam-policy rename to gcloud/alpha/agent-identity/connectors/set-iam-policy index 4ebd24731..b6ada3856 100644 --- a/gcloud/alpha/dataplex/data-taxonomies/set-iam-policy +++ b/gcloud/alpha/agent-identity/connectors/set-iam-policy @@ -1,59 +1,54 @@ NAME - gcloud alpha dataplex data-taxonomies set-iam-policy - set an IAM policy - binding for a Dataplex Data Taxonomy as defined in a JSON or YAML file + gcloud alpha agent-identity connectors set-iam-policy - set the IAM policy + for an Agent Identity connector SYNOPSIS - gcloud alpha dataplex data-taxonomies set-iam-policy - (DATA_TAXONOMY : --location=LOCATION) POLICY_FILE - [GCLOUD_WIDE_FLAG ...] + gcloud alpha agent-identity connectors set-iam-policy + (CONNECTOR : --location=LOCATION) POLICY_FILE [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) See https://cloud.google.com/iam/docs/managing-policies for details - of the policy file format and contents. + (ALPHA) This command replaces the existing IAM policy for a connector, + given a connector and a file encoded in JSON or YAML that contains the IAM + policy. EXAMPLES The following command will read an IAM policy defined in a JSON file - policy.json and set it for the Dataplex Data Taxonomy test-taxonomy within - project test-project in location us-central1: + 'policy.json' and set it for a connector with identifier 'my-connector' and + location 'us-central1': - $ gcloud alpha dataplex data-taxonomies set-iam-policy \ - test-taxonomy --project=test-project --location=us-central1 \ - policy.json - - where policy.json is the relative path to the json file. + $ gcloud alpha agent-identity connectors set-iam-policy \ + my-connector policy.json --location=us-central1 POSITIONAL ARGUMENTS - Data taxonomy resource - The DataTaxonomy to set IAM policy to. The + Connector resource - The connector for which to set the IAM policy. The arguments in this group can be used to specify the attributes of this resource. (NOTE) Some attributes are not given arguments in this group but can be set in other ways. To set the project attribute: - ◆ provide the argument data_taxonomy on the command line with a fully + ◆ provide the argument connector 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_TAXONOMY - ID of the data taxonomy or fully qualified identifier for the data - taxonomy. + CONNECTOR + ID of the connector or fully qualified identifier for the connector. - To set the data_taxonomy attribute: - ▸ provide the argument data_taxonomy on the command line. + To set the connector attribute: + ▸ provide the argument connector 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 of the Dataplex resource. + The location id of the connector resource. To set the location attribute: - ▸ provide the argument data_taxonomy on the command line with a - fully specified name; - ▸ provide the argument --location on the command line; - ▸ set the property dataplex/location. + ▸ provide the argument connector on the command line with a fully + specified name; + ▸ provide the argument --location on the command line. POLICY_FILE Path to a local JSON or YAML formatted file containing a valid policy. @@ -70,6 +65,10 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. +API REFERENCE + This command uses the iamconnectors/v1alpha API. The full documentation for + this API can be found at: https://cloud.google.com/iam/docs/ + NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct diff --git a/gcloud/alpha/agent-identity/connectors/test-iam-permissions b/gcloud/alpha/agent-identity/connectors/test-iam-permissions new file mode 100644 index 000000000..1bbef660d --- /dev/null +++ b/gcloud/alpha/agent-identity/connectors/test-iam-permissions @@ -0,0 +1,73 @@ +NAME + gcloud alpha agent-identity connectors test-iam-permissions - test IAM + permissions for an Agent Identity connector + +SYNOPSIS + gcloud alpha agent-identity connectors test-iam-permissions + (CONNECTOR : --location=LOCATION) --permissions=[PERMISSIONS,...] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Returns permissions that a caller has on the specified resource. + +EXAMPLES + To test if the caller has 'iamconnectors.connectors.get' permission on a + connector, run: + + $ gcloud alpha agent-identity connectors test-iam-permissions \ + my-connector --location=us-central1 \ + --permissions=iamconnectors.connectors.get + +POSITIONAL ARGUMENTS + Connector resource - The connector for which to test permissions. The + arguments in this group can be used to specify the attributes of this + resource. (NOTE) Some attributes are not given arguments in this group but + can be set in other ways. + + To set the project attribute: + ◆ provide the argument connector on the command line with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + CONNECTOR + ID of the connector or fully qualified identifier for the connector. + + To set the connector attribute: + ▸ provide the argument connector on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + The location id of the connector resource. + + To set the location attribute: + ▸ provide the argument connector on the command line with a fully + specified name; + ▸ provide the argument --location on the command line. + +REQUIRED FLAGS + --permissions=[PERMISSIONS,...] + The permissions to test. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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 iamconnectors/v1alpha API. The full documentation for + this API can be found at: https://cloud.google.com/iam/docs/ + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/agent-identity/help b/gcloud/alpha/agent-identity/help index f0031c33f..0d5bec83e 100644 --- a/gcloud/alpha/agent-identity/help +++ b/gcloud/alpha/agent-identity/help @@ -21,9 +21,6 @@ GROUPS connectors (ALPHA) Manage Connector resources. - operations - (ALPHA) Manage Operation resources. - NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct diff --git a/gcloud/alpha/agent-identity/operations/help b/gcloud/alpha/agent-identity/operations/help deleted file mode 100644 index b893285e0..000000000 --- a/gcloud/alpha/agent-identity/operations/help +++ /dev/null @@ -1,23 +0,0 @@ -NAME - gcloud alpha agent-identity operations - manage Operation resources - -SYNOPSIS - gcloud alpha agent-identity operations [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (ALPHA) Manage Operation resources. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --configuration, --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/agent-registry/agents/help b/gcloud/alpha/agent-registry/agents/help index 099d2d711..61b7b83e7 100644 --- a/gcloud/alpha/agent-registry/agents/help +++ b/gcloud/alpha/agent-registry/agents/help @@ -21,6 +21,9 @@ COMMANDS list (ALPHA) List agents. + search + (ALPHA) search agents. + NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct diff --git a/gcloud/alpha/agent-registry/agents/search b/gcloud/alpha/agent-registry/agents/search new file mode 100644 index 000000000..14753067b --- /dev/null +++ b/gcloud/alpha/agent-registry/agents/search @@ -0,0 +1,75 @@ +NAME + gcloud alpha agent-registry agents search - search agents + +SYNOPSIS + gcloud alpha agent-registry agents search --location=LOCATION + [--page-size=PAGE_SIZE] [--page-token=PAGE_TOKEN] + [--search-string=SEARCH_STRING] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) search agents + +EXAMPLES + To search all agents, run: + + $ gcloud alpha agent-registry agents search + +REQUIRED FLAGS + Location resource - Parent value for SearchAgentsRequest 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. + +OPTIONAL FLAGS + --page-size=PAGE_SIZE + The maximum number of agents to return. The service may return fewer + than this value. If unspecified, at most 20 agents will be returned. + The maximum value is 100; values above 100 will be coerced to 100. + + --page-token=PAGE_TOKEN + A page token, received from a previous SearchAgents call. Provide this + to retrieve the subsequent page. + + When paginating, all other parameters provided to SearchAgents must + match the call that provided the page token. + + --search-string=SEARCH_STRING + Search criteria used to select the Agents to return. If no search + criteria is specified then all accessible Agents will be returned. + + Search expressions can be used to restrict results based upon skills, + agentId, description, name and trust, where the operators =, NOT, AND + and OR can be used along with the suffix wildcard symbol *. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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 agentregistry/v1alpha API. The full documentation for + this API can be found at: + https://docs.cloud.google.com/agent-registry/overview + +NOTES + This command is currently in alpha and might change without notice. If this + command fails 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/agent-registry/bindings/create b/gcloud/alpha/agent-registry/bindings/create new file mode 100644 index 000000000..9c864e180 --- /dev/null +++ b/gcloud/alpha/agent-registry/bindings/create @@ -0,0 +1,144 @@ +NAME + gcloud alpha agent-registry bindings create - create bindings + +SYNOPSIS + gcloud alpha agent-registry bindings create (BINDING : --location=LOCATION) + --source-identifier=SOURCE_IDENTIFIER + --target-identifier=TARGET_IDENTIFIER [--async] + [--description=DESCRIPTION] [--display-name=DISPLAY_NAME] + [--request-id=REQUEST_ID] + [--auth-provider-binding=AUTH_PROVIDER_BINDING + : --auth-provider-binding-continue-uri=AUTH_PROVIDER_BINDING_CONTINUE_URI --auth-provider-binding-scopes=[AUTH_PROVIDER_BINDING_SCOPES, + ...]] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Create a binding + +EXAMPLES + To create the binding, run: + + $ gcloud alpha agent-registry bindings create + +POSITIONAL ARGUMENTS + Binding resource - Identifier. The resource name of the Binding. Format: + projects/{project}/locations/{location}/bindings/{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 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. + + BINDING + ID of the binding or fully qualified identifier for the binding. + + To set the binding attribute: + ▸ provide the argument 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 binding resource. + + To set the location attribute: + ▸ provide the argument binding on the command line with a fully + specified name; + ▸ provide the argument --location on the command line. + +REQUIRED FLAGS + The source of the Binding. + + This must be specified. + + Arguments for the source type. + + --source-identifier=SOURCE_IDENTIFIER + The identifier of the source Agent. Format: + + ▸ urn:agent:{publisher}:{namespace}:{name} + + The target of the Binding. + + This must be specified. + + Arguments for the target type. + + --target-identifier=TARGET_IDENTIFIER + The identifier of the target Agent, MCP Server, or Endpoint. Format: + + ▸ urn:agent:{publisher}:{namespace}:{name} + ▸ urn:mcp:{publisher}:{namespace}:{name} + ▸ urn:endpoint:{publisher}:{namespace}:{name} + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --description=DESCRIPTION + User-defined description of a Binding. Can have a maximum length of + 2048 characters. + + --display-name=DISPLAY_NAME + User-defined display name for the Binding. Can have a maximum length of + 63 characters. + + --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). + + Arguments for the binding. + + The AuthProvider of the Binding. + + --auth-provider-binding=AUTH_PROVIDER_BINDING + The resource name of the target AuthProvider. Format: + + ◆ projects/{project}/locations/{location}/authProviders/{auth_provider} + + This flag argument must be specified if any of the other arguments in + this group are specified. + + --auth-provider-binding-continue-uri=AUTH_PROVIDER_BINDING_CONTINUE_URI + The continue URI of the AuthProvider. The URI is used to reauthenticate + the user and finalize the managed OAuth flow. + + --auth-provider-binding-scopes=[AUTH_PROVIDER_BINDING_SCOPES,...] + The list of OAuth2 scopes of the AuthProvider. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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 agentregistry/v1alpha API. The full documentation for + this API can be found at: + https://docs.cloud.google.com/agent-registry/overview + +NOTES + This command is currently in alpha and might change without notice. If this + command fails 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/agent-registry/bindings/delete b/gcloud/alpha/agent-registry/bindings/delete new file mode 100644 index 000000000..51a8e5342 --- /dev/null +++ b/gcloud/alpha/agent-registry/bindings/delete @@ -0,0 +1,86 @@ +NAME + gcloud alpha agent-registry bindings delete - delete bindings + +SYNOPSIS + gcloud alpha agent-registry bindings delete (BINDING : --location=LOCATION) + [--async] [--request-id=REQUEST_ID] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Delete a binding + +EXAMPLES + To delete the binding, run: + + $ gcloud alpha agent-registry bindings delete + +POSITIONAL ARGUMENTS + Binding resource - The name of the Binding. Format: + projects/{project}/locations/{location}/bindings/{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 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. + + BINDING + ID of the binding or fully qualified identifier for the binding. + + To set the binding attribute: + ▸ provide the argument 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 binding resource. + + To set the location attribute: + ▸ provide the argument 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 agentregistry/v1alpha API. The full documentation for + this API can be found at: + https://docs.cloud.google.com/agent-registry/overview + +NOTES + This command is currently in alpha and might change without notice. If this + command fails 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/agent-registry/bindings/describe b/gcloud/alpha/agent-registry/bindings/describe new file mode 100644 index 000000000..d87d8fb24 --- /dev/null +++ b/gcloud/alpha/agent-registry/bindings/describe @@ -0,0 +1,66 @@ +NAME + gcloud alpha agent-registry bindings describe - describe bindings + +SYNOPSIS + gcloud alpha agent-registry bindings describe + (BINDING : --location=LOCATION) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Describe a binding + +EXAMPLES + To describe the binding, run: + + $ gcloud alpha agent-registry bindings describe + +POSITIONAL ARGUMENTS + Binding resource - The name of the Binding. Format: + projects/{project}/locations/{location}/bindings/{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 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. + + BINDING + ID of the binding or fully qualified identifier for the binding. + + To set the binding attribute: + ▸ provide the argument 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 binding resource. + + To set the location attribute: + ▸ provide the argument 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 agentregistry/v1alpha API. The full documentation for + this API can be found at: + https://docs.cloud.google.com/agent-registry/overview + +NOTES + This command is currently in alpha and might change without notice. If this + command fails 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/agent-registry/bindings/fetch-available b/gcloud/alpha/agent-registry/bindings/fetch-available new file mode 100644 index 000000000..222243aeb --- /dev/null +++ b/gcloud/alpha/agent-registry/bindings/fetch-available @@ -0,0 +1,96 @@ +NAME + gcloud alpha agent-registry bindings fetch-available - fetch bindings + +SYNOPSIS + gcloud alpha agent-registry bindings fetch-available --location=LOCATION + [--source-identifier=SOURCE_IDENTIFIER] + [--target-identifier=TARGET_IDENTIFIER] [--filter=EXPRESSION] + [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) fetch bindings + +EXAMPLES + To fetch all bindings, run: + + $ gcloud alpha agent-registry bindings fetch-available + +REQUIRED FLAGS + Location resource - The parent, in the format + projects/{project}/locations/{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; + ◆ 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. + +FLAGS + --source-identifier=SOURCE_IDENTIFIER + The identifier of the source Agent. Format: + + ◆ urn:agent:{publisher}:{namespace}:{name} + + --target-identifier=TARGET_IDENTIFIER + The identifier of the target Agent, MCP Server, or Endpoint. Format: + + ◆ urn:agent:{publisher}:{namespace}:{name} + ◆ urn:mcp:{publisher}:{namespace}:{name} + ◆ urn:endpoint:{publisher}:{namespace}:{name} + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the agentregistry/v1alpha API. The full documentation for + this API can be found at: + https://docs.cloud.google.com/agent-registry/overview + +NOTES + This command is currently in alpha and might change without notice. If this + command fails 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/agent-registry/bindings/help b/gcloud/alpha/agent-registry/bindings/help index 152edacba..05b98ff58 100644 --- a/gcloud/alpha/agent-registry/bindings/help +++ b/gcloud/alpha/agent-registry/bindings/help @@ -12,6 +12,27 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. +COMMANDS + COMMAND is one of the following: + + create + (ALPHA) Create bindings. + + delete + (ALPHA) Delete bindings. + + describe + (ALPHA) Describe bindings. + + fetch-available + (ALPHA) fetch bindings. + + list + (ALPHA) List bindings. + + update + (ALPHA) Update 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 diff --git a/gcloud/alpha/agent-registry/bindings/list b/gcloud/alpha/agent-registry/bindings/list new file mode 100644 index 000000000..e73bcb31c --- /dev/null +++ b/gcloud/alpha/agent-registry/bindings/list @@ -0,0 +1,87 @@ +NAME + gcloud alpha agent-registry bindings list - list bindings + +SYNOPSIS + gcloud alpha agent-registry bindings list --location=LOCATION + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) List bindings + +EXAMPLES + To list all bindings, run: + + $ gcloud alpha agent-registry bindings list + +REQUIRED FLAGS + Location resource - The project and location to list bindings in. Expected + format: projects/{project}/locations/{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; + ◆ 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 agentregistry/v1alpha API. The full documentation for + this API can be found at: + https://docs.cloud.google.com/agent-registry/overview + +NOTES + This command is currently in alpha and might change without notice. If this + command fails 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/agent-registry/bindings/update b/gcloud/alpha/agent-registry/bindings/update new file mode 100644 index 000000000..618b1c9a8 --- /dev/null +++ b/gcloud/alpha/agent-registry/bindings/update @@ -0,0 +1,166 @@ +NAME + gcloud alpha agent-registry bindings update - update bindings + +SYNOPSIS + gcloud alpha agent-registry bindings update (BINDING : --location=LOCATION) + [--async] [--description=DESCRIPTION] [--display-name=DISPLAY_NAME] + [--request-id=REQUEST_ID] + [--auth-provider-binding=AUTH_PROVIDER_BINDING + --auth-provider-binding-continue-uri=AUTH_PROVIDER_BINDING_CONTINUE_URI --clear-auth-provider-binding --auth-provider-binding-scopes=[AUTH_PROVIDER_BINDING_SCOPES, + ...] + | --add-auth-provider-binding-scopes=[ADD_AUTH_PROVIDER_BINDING_SCOPES, + ...] --clear-auth-provider-binding-scopes + | --remove-auth-provider-binding-scopes=[REMOVE_AUTH_PROVIDER_BINDING_SCOPES, + ...]] [--clear-source --source-identifier=SOURCE_IDENTIFIER] + [--clear-target --target-identifier=TARGET_IDENTIFIER] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Update a binding + +EXAMPLES + To update the binding, run: + + $ gcloud alpha agent-registry bindings update + +POSITIONAL ARGUMENTS + Binding resource - Identifier. The resource name of the Binding. Format: + projects/{project}/locations/{location}/bindings/{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 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. + + BINDING + ID of the binding or fully qualified identifier for the binding. + + To set the binding attribute: + ▸ provide the argument 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 binding resource. + + To set the location attribute: + ▸ provide the argument 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. + + --description=DESCRIPTION + User-defined description of a Binding. Can have a maximum length of + 2048 characters. + + --display-name=DISPLAY_NAME + User-defined display name for the Binding. Can have a maximum length of + 63 characters. + + --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). + + Arguments for the binding. + + The AuthProvider of the Binding. + + --auth-provider-binding=AUTH_PROVIDER_BINDING + The resource name of the target AuthProvider. Format: + + ◆ projects/{project}/locations/{location}/authProviders/{auth_provider} + + --auth-provider-binding-continue-uri=AUTH_PROVIDER_BINDING_CONTINUE_URI + The continue URI of the AuthProvider. The URI is used to reauthenticate + the user and finalize the managed OAuth flow. + + --clear-auth-provider-binding + Set binding.authProviderBinding back to default value. + + Update auth_provider_binding_scopes. + + At most one of these can be specified: + + --auth-provider-binding-scopes=[AUTH_PROVIDER_BINDING_SCOPES,...] + Set auth_provider_binding_scopes to new value. + + Or at least one of these can be specified: + + --add-auth-provider-binding-scopes=[ADD_AUTH_PROVIDER_BINDING_SCOPES,...] + Add new value to auth_provider_binding_scopes list. + + At most one of these can be specified: + + --clear-auth-provider-binding-scopes + Clear auth_provider_binding_scopes value and set to empty list. + + --remove-auth-provider-binding-scopes=[REMOVE_AUTH_PROVIDER_BINDING_SCOPES,...] + Remove existing value from auth_provider_binding_scopes list. + + The source of the Binding. + + --clear-source + Set binding.source back to default value. + + Arguments for the source type. + + --source-identifier=SOURCE_IDENTIFIER + The identifier of the source Agent. Format: + + ◆ urn:agent:{publisher}:{namespace}:{name} + + The target of the Binding. + + --clear-target + Set binding.target back to default value. + + Arguments for the target type. + + --target-identifier=TARGET_IDENTIFIER + The identifier of the target Agent, MCP Server, or Endpoint. Format: + + ◆ urn:agent:{publisher}:{namespace}:{name} + ◆ urn:mcp:{publisher}:{namespace}:{name} + ◆ urn:endpoint:{publisher}:{namespace}:{name} + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the agentregistry/v1alpha API. The full documentation for + this API can be found at: + https://docs.cloud.google.com/agent-registry/overview + +NOTES + This command is currently in alpha and might change without notice. If this + command fails 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/agent-registry/mcp-servers/help b/gcloud/alpha/agent-registry/mcp-servers/help index 0c87649ef..67b4870af 100644 --- a/gcloud/alpha/agent-registry/mcp-servers/help +++ b/gcloud/alpha/agent-registry/mcp-servers/help @@ -21,6 +21,9 @@ COMMANDS list (ALPHA) List mcpServers. + search + (ALPHA) search mcpServers. + NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct diff --git a/gcloud/alpha/agent-registry/mcp-servers/search b/gcloud/alpha/agent-registry/mcp-servers/search new file mode 100644 index 000000000..c98e1a428 --- /dev/null +++ b/gcloud/alpha/agent-registry/mcp-servers/search @@ -0,0 +1,76 @@ +NAME + gcloud alpha agent-registry mcp-servers search - search mcpServers + +SYNOPSIS + gcloud alpha agent-registry mcp-servers search --location=LOCATION + [--page-size=PAGE_SIZE] [--page-token=PAGE_TOKEN] + [--search-string=SEARCH_STRING] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) search mcpServers + +EXAMPLES + To search all mcpServers, run: + + $ gcloud alpha agent-registry mcp-servers search + +REQUIRED FLAGS + Location resource - Parent value for SearchMcpServersRequest. 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. + +OPTIONAL FLAGS + --page-size=PAGE_SIZE + The maximum number of MCP Servers to return. The service may return + fewer than this value. If unspecified, at most 20 MCP Servers will be + returned. The maximum value is 100; values above 100 will be coerced to + 100. + + --page-token=PAGE_TOKEN + A page token, received from a previous SearchMcpServers call. Provide + this to retrieve the subsequent page. + + When paginating, all other parameters provided to SearchMcpServers must + match the call that provided the page token. + + --search-string=SEARCH_STRING + Search criteria used to select the MCP Servers to return. If no search + criteria is specified then all accessible MCP Servers will be returned. + + Search expressions can be used to restrict results based upon + mcpServerId, description, and name, where the operators =, NOT, AND and + OR can be used along with the suffix wildcard symbol *. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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 agentregistry/v1alpha API. The full documentation for + this API can be found at: + https://docs.cloud.google.com/agent-registry/overview + +NOTES + This command is currently in alpha and might change without notice. If this + command fails 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/ai/model-garden/models/deploy b/gcloud/alpha/ai/model-garden/models/deploy index 27554a608..14fd03788 100644 --- a/gcloud/alpha/ai/model-garden/models/deploy +++ b/gcloud/alpha/ai/model-garden/models/deploy @@ -27,8 +27,8 @@ SYNOPSIS [--machine-type=MACHINE_TYPE] [--region=REGION] [--reservation-affinity=[key=KEY], [reservation-affinity-type=RESERVATION-AFFINITY-TYPE], - [values=VALUES]] [--spot] [--use-dedicated-endpoint] - [GCLOUD_WIDE_FLAG ...] + [values=VALUES]] [--spot] [--system-labels=[KEY=VALUE,...]] + [--use-dedicated-endpoint] [GCLOUD_WIDE_FLAG ...] EXAMPLES To deploy a Model Garden model google/gemma2/gemma2-9b under project @@ -188,6 +188,9 @@ OPTIONAL FLAGS --spot If true, schedule the deployment workload on Spot VM. + --system-labels=[KEY=VALUE,...] + System labels for Model Garden deployments. + --use-dedicated-endpoint If true, the endpoint will be exposed through a dedicated DNS. Your request to the dedicated DNS will be isolated from other users' traffic diff --git a/gcloud/alpha/alloydb/clusters/promote b/gcloud/alpha/alloydb/clusters/promote index a292f887c..674f59aac 100644 --- a/gcloud/alpha/alloydb/clusters/promote +++ b/gcloud/alpha/alloydb/clusters/promote @@ -4,7 +4,7 @@ NAME SYNOPSIS gcloud alpha alloydb clusters promote CLUSTER --region=REGION [--async] - [--failover] [GCLOUD_WIDE_FLAG ...] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Promote an AlloyDB SECONDARY cluster in a given project and region. @@ -29,12 +29,6 @@ OPTIONAL FLAGS Return immediately, without waiting for the operation in progress to complete. - --failover - If set, the promote operation will attempt to recreate the original - primary cluster as a secondary cluster when it comes back online. - Otherwise, the promoted cluster will be a standalone cluster. Currently - only supported when there is a single secondary cluster. - GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, diff --git a/gcloud/alpha/alloydb/instances/create b/gcloud/alpha/alloydb/instances/create index 2cbbd4b8f..fae117ffb 100644 --- a/gcloud/alpha/alloydb/instances/create +++ b/gcloud/alpha/alloydb/instances/create @@ -28,13 +28,16 @@ SYNOPSIS [--insights-config-query-string-length=INSIGHTS_CONFIG_QUERY_STRING_LENGTH] [--[no-]insights-config-record-application-tags] [--[no-]insights-config-record-client-address] - [--machine-type=MACHINE_TYPE] [--[no-]observability-config-enabled] + [--machine-type=MACHINE_TYPE] + [--[no-]observability-config-assistive-experiences-enabled] + [--[no-]observability-config-enabled] [--observability-config-max-query-string-length=OBSERVABILITY_CONFIG_MAX_QUERY_STRING_LENGTH] [--[no-]observability-config-preserve-comments] [--observability-config-query-plans-per-minute=OBSERVABILITY_CONFIG_QUERY_PLANS_PER_MINUTE] [--[no-]observability-config-record-application-tags] [--[no-]observability-config-track-active-queries] [--[no-]observability-config-track-active-query-plan] + [--[no-]observability-config-track-client-address] [--observability-config-track-wait-events] [--[no-]outbound-public-ip] [--psc-auto-connections=[network=NETWORK],[project=PROJECT]] [--psc-network-attachment-uri=PSC_NETWORK_ATTACHMENT_URI] @@ -235,6 +238,11 @@ OPTIONAL FLAGS z3-highmem-8-highlssd, z3-highmem-16-highlssd, z3-highmem-22-highlssd, z3-highmem-32-highlssd, z3-highmem-44-highlssd. + --[no-]observability-config-assistive-experiences-enabled + Enable assistive experiences to monitor, troubleshoot and recommend. + Use --observability-config-assistive-experiences-enabled to enable and + --no-observability-config-assistive-experiences-enabled to disable. + --[no-]observability-config-enabled Enable enhanced query insights feature. Use --observability-config-enabled to enable and @@ -252,7 +260,7 @@ OPTIONAL FLAGS --no-observability-config-preserve-comments to disable. --observability-config-query-plans-per-minute=OBSERVABILITY_CONFIG_QUERY_PLANS_PER_MINUTE - Number of query plans to sample every minute. Default value is 200. + Number of query plans to sample every minute. Default value is 20. Allowed range: 0 to 200. --[no-]observability-config-record-application-tags @@ -272,6 +280,11 @@ OPTIONAL FLAGS --observability-config-track-active-query-plan to enable and --no-observability-config-track-active-query-plan to disable. + --[no-]observability-config-track-client-address + Enable tracking of client address in query insights. Use + --observability-config-track-client-address to enable and + --no-observability-config-track-client-address to disable. + --observability-config-track-wait-events Track wait events during query execution. diff --git a/gcloud/alpha/alloydb/instances/update b/gcloud/alpha/alloydb/instances/update index fe2448603..97c97a088 100644 --- a/gcloud/alpha/alloydb/instances/update +++ b/gcloud/alpha/alloydb/instances/update @@ -28,13 +28,16 @@ SYNOPSIS [--insights-config-query-string-length=INSIGHTS_CONFIG_QUERY_STRING_LENGTH] [--[no-]insights-config-record-application-tags] [--[no-]insights-config-record-client-address] - [--machine-type=MACHINE_TYPE] [--[no-]observability-config-enabled] + [--machine-type=MACHINE_TYPE] + [--[no-]observability-config-assistive-experiences-enabled] + [--[no-]observability-config-enabled] [--observability-config-max-query-string-length=OBSERVABILITY_CONFIG_MAX_QUERY_STRING_LENGTH] [--[no-]observability-config-preserve-comments] [--observability-config-query-plans-per-minute=OBSERVABILITY_CONFIG_QUERY_PLANS_PER_MINUTE] [--[no-]observability-config-record-application-tags] [--[no-]observability-config-track-active-queries] [--[no-]observability-config-track-active-query-plan] + [--[no-]observability-config-track-client-address] [--observability-config-track-wait-events] [--[no-]outbound-public-ip] [--psc-network-attachment-uri=PSC_NETWORK_ATTACHMENT_URI] [--read-pool-node-count=READ_POOL_NODE_COUNT] @@ -221,6 +224,11 @@ OPTIONAL FLAGS z3-highmem-8-highlssd, z3-highmem-16-highlssd, z3-highmem-22-highlssd, z3-highmem-32-highlssd, z3-highmem-44-highlssd. + --[no-]observability-config-assistive-experiences-enabled + Enable assistive experiences to monitor, troubleshoot and recommend. + Use --observability-config-assistive-experiences-enabled to enable and + --no-observability-config-assistive-experiences-enabled to disable. + --[no-]observability-config-enabled Enable enhanced query insights feature. Use --observability-config-enabled to enable and @@ -238,7 +246,7 @@ OPTIONAL FLAGS --no-observability-config-preserve-comments to disable. --observability-config-query-plans-per-minute=OBSERVABILITY_CONFIG_QUERY_PLANS_PER_MINUTE - Number of query plans to sample every minute. Default value is 200. + Number of query plans to sample every minute. Default value is 20. Allowed range: 0 to 200. --[no-]observability-config-record-application-tags @@ -258,6 +266,11 @@ OPTIONAL FLAGS --observability-config-track-active-query-plan to enable and --no-observability-config-track-active-query-plan to disable. + --[no-]observability-config-track-client-address + Enable tracking of client address in query insights. Use + --observability-config-track-client-address to enable and + --no-observability-config-track-client-address to disable. + --observability-config-track-wait-events Track wait events during query execution. diff --git a/gcloud/alpha/alloydb/users/create b/gcloud/alpha/alloydb/users/create index 34748fce4..5d1eb7e87 100644 --- a/gcloud/alpha/alloydb/users/create +++ b/gcloud/alpha/alloydb/users/create @@ -53,6 +53,9 @@ OPTIONAL FLAGS authentication IAM_BASED This database user can authenticate via IAM-based authentication + IAM_GROUP + This database user represents an IAM group whose members can + authenticate via IAM group-based authentication GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/alpha/api-registry/help b/gcloud/alpha/api-registry/help index f6e82ce62..dcac8a6f0 100644 --- a/gcloud/alpha/api-registry/help +++ b/gcloud/alpha/api-registry/help @@ -16,7 +16,7 @@ GROUPS GROUP is one of the following: mcp - (ALPHA) Manage MCP Command Group. + (ALPHA) (DEPRECATED) Manage MCP Command Group. NOTES This command is currently in alpha and might change without notice. If this diff --git a/gcloud/alpha/api-registry/mcp/disable b/gcloud/alpha/api-registry/mcp/disable index fb4625981..91efed7a8 100644 --- a/gcloud/alpha/api-registry/mcp/disable +++ b/gcloud/alpha/api-registry/mcp/disable @@ -6,7 +6,11 @@ SYNOPSIS gcloud alpha api-registry mcp disable SERVICE [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) Disables MCP server for a given service in the current project. + (ALPHA) (DEPRECATED) Disables MCP server for a given service in the current + project. + + The gcloud alpha api-registry mcp disable command is deprecated and will be + removed in a future release. POSITIONAL ARGUMENTS SERVICE diff --git a/gcloud/alpha/api-registry/mcp/enable b/gcloud/alpha/api-registry/mcp/enable index a872bb844..ef4c0f76c 100644 --- a/gcloud/alpha/api-registry/mcp/enable +++ b/gcloud/alpha/api-registry/mcp/enable @@ -6,7 +6,11 @@ SYNOPSIS gcloud alpha api-registry mcp enable SERVICE [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) Enables MCP server for a given service in the current project. + (ALPHA) (DEPRECATED) Enables MCP server for a given service in the current + project. + + The gcloud alpha api-registry mcp enable command is deprecated and will be + removed in a future release. POSITIONAL ARGUMENTS SERVICE diff --git a/gcloud/alpha/api-registry/mcp/help b/gcloud/alpha/api-registry/mcp/help index c40463dc2..b32e40f5a 100644 --- a/gcloud/alpha/api-registry/mcp/help +++ b/gcloud/alpha/api-registry/mcp/help @@ -5,8 +5,12 @@ SYNOPSIS gcloud alpha api-registry mcp GROUP | COMMAND [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) Commands for managing MCP enablement and disablement for a given - service in the current project. + (ALPHA) (DEPRECATED) Manage MCP Command Group. + + This command is deprecated. + + Commands for managing MCP enablement and disablement for a given service in + the current project. GCLOUD WIDE FLAGS These flags are available to all commands: --help. @@ -17,19 +21,21 @@ GROUPS GROUP is one of the following: servers - (ALPHA) Manage Cloud API Registry MCP servers. + (ALPHA) (DEPRECATED) Manage Cloud API Registry MCP servers. tools - (ALPHA) Manage Cloud API Registry MCP tools. + (ALPHA) (DEPRECATED) Manage Cloud API Registry MCP tools. COMMANDS COMMAND is one of the following: disable - (ALPHA) Disables MCP server for a given service in the current project. + (ALPHA) (DEPRECATED) Disables MCP server for a given service in the + current project. enable - (ALPHA) Enables MCP server for a given service in the current project. + (ALPHA) (DEPRECATED) Enables MCP server for a given service in the + current project. NOTES This command is currently in alpha and might change without notice. If this diff --git a/gcloud/alpha/api-registry/mcp/servers/help b/gcloud/alpha/api-registry/mcp/servers/help index 8a340743a..de4e41c61 100644 --- a/gcloud/alpha/api-registry/mcp/servers/help +++ b/gcloud/alpha/api-registry/mcp/servers/help @@ -6,7 +6,9 @@ SYNOPSIS gcloud alpha api-registry mcp servers COMMAND [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) Manage Cloud API Registry MCP servers. + (ALPHA) (DEPRECATED) Manage Cloud API Registry MCP servers. + + This command is deprecated. GCLOUD WIDE FLAGS These flags are available to all commands: --help. @@ -17,7 +19,7 @@ COMMANDS COMMAND is one of the following: list - (ALPHA) List MCP servers. + (ALPHA) (DEPRECATED) List MCP servers. NOTES This command is currently in alpha and might change without notice. If this diff --git a/gcloud/alpha/api-registry/mcp/servers/list b/gcloud/alpha/api-registry/mcp/servers/list index b0fa3ea74..15b5d6a3c 100644 --- a/gcloud/alpha/api-registry/mcp/servers/list +++ b/gcloud/alpha/api-registry/mcp/servers/list @@ -7,7 +7,20 @@ SYNOPSIS [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) List MCP servers. + (ALPHA) (DEPRECATED) The gcloud alpha api-registry mcp servers list command + is deprecated and will be removed in a future release. Please use gcloud + alpha agent-registry mcp-servers list instead. Note: Agent Registry only + lists MCP servers for service APIs that are enabled in a project. For more + information, see: + https://docs.cloud.google.com/sdk/gcloud/reference/alpha/agent-registry/mcp-servers + + (ALPHA) (DEPRECATED) List MCP servers. + + The gcloud alpha api-registry mcp servers list command is deprecated and + will be removed in a future release. Please use gcloud alpha agent-registry + mcp-servers list instead. Note: Agent Registry only lists MCP servers for + service APIs that are enabled in a project. For more information, see: + https://docs.cloud.google.com/sdk/gcloud/reference/alpha/agent-registry/mcp-servers EXAMPLES To list all MCP servers in a project, run: diff --git a/gcloud/alpha/api-registry/mcp/tools/help b/gcloud/alpha/api-registry/mcp/tools/help index 7c6891b77..591a2cc9e 100644 --- a/gcloud/alpha/api-registry/mcp/tools/help +++ b/gcloud/alpha/api-registry/mcp/tools/help @@ -5,7 +5,9 @@ SYNOPSIS gcloud alpha api-registry mcp tools COMMAND [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) Manage Cloud API Registry MCP tools. + (ALPHA) (DEPRECATED) Manage Cloud API Registry MCP tools. + + This command is deprecated. GCLOUD WIDE FLAGS These flags are available to all commands: --help. @@ -16,7 +18,7 @@ COMMANDS COMMAND is one of the following: list - (ALPHA) List MCP tools. + (ALPHA) (DEPRECATED) List MCP tools. NOTES This command is currently in alpha and might change without notice. If this diff --git a/gcloud/alpha/api-registry/mcp/tools/list b/gcloud/alpha/api-registry/mcp/tools/list index 436a91bb2..8cdf6bc65 100644 --- a/gcloud/alpha/api-registry/mcp/tools/list +++ b/gcloud/alpha/api-registry/mcp/tools/list @@ -7,7 +7,23 @@ SYNOPSIS [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) List MCP tools. + (ALPHA) (DEPRECATED) The gcloud alpha api-registry mcp tools list command + is deprecated and will be removed in a future release. For similar + functionality, you can use Agent Registry. Note: Agent Registry does not + treat tools as a separate collection. To view tools, please use gcloud + alpha agent-registry mcp-servers list or describe command to view the tools + included in the server payloads. For more information, see: + https://docs.cloud.google.com/sdk/gcloud/reference/alpha/agent-registry/mcp-servers + + (ALPHA) (DEPRECATED) List MCP tools. + + The gcloud alpha api-registry mcp tools list command is deprecated and will + be removed in a future release. For similar functionality, you can use + Agent Registry. Note: Agent Registry does not treat tools as a separate + collection. To view tools, please use gcloud alpha agent-registry + mcp-servers list or describe command to view the tools included in the + server payloads. For more information, see: + https://docs.cloud.google.com/sdk/gcloud/reference/alpha/agent-registry/mcp-servers EXAMPLES To list MCP tools, run: diff --git a/gcloud/alpha/app/migrate-to-run b/gcloud/alpha/app/migrate-to-run index cca5df7aa..bafae37bd 100644 --- a/gcloud/alpha/app/migrate-to-run +++ b/gcloud/alpha/app/migrate-to-run @@ -4,9 +4,9 @@ NAME SYNOPSIS gcloud alpha app migrate-to-run [--appyaml=APPYAML] - [--destination-repository=DESTINATION_REPOSITORY] - [--entrypoint=ENTRYPOINT] [--from-image] [--from-source] - [--service=SERVICE] [--version=VERSION] [GCLOUD_WIDE_FLAG ...] + [--destination-repository=DESTINATION_REPOSITORY] [--from-image] + [--from-source] [--service=SERVICE] [--version=VERSION] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Migrates the second-generation App Engine app to Cloud Run. @@ -16,25 +16,24 @@ EXAMPLES through app.yaml - gcloud app migrate-to-run --appyaml=path/to/app.yaml --entrypoint=main + gcloud app migrate-to-run --appyaml=path/to/app.yaml OR through service and version - gcloud app migrate-to-run --service=default --version=v1 --entrypoint=main + gcloud app migrate-to-run --service=default --version=v1 FLAGS --appyaml=APPYAML - YAML file for the second generation App Engine version to be migrated. + Path to the app.yaml file for the second generation App Engine version + to be migrated. If not provided, the app.yaml present in the current + directory is used. --destination-repository=DESTINATION_REPOSITORY The full resource name of the AR repository to export to in the format of projects/*/locations/*/repositories/*. - --entrypoint=ENTRYPOINT - entrypoint required for some runtimes - --from-image Use image based migration. @@ -42,10 +41,14 @@ FLAGS Use source based migration. --service=SERVICE - service name that is deployed in App Engine + Name of the service that is deployed in App Engine. If specified, the + configuration of the existing service will be used and app.yaml in the + current directory will be ignored. --version=VERSION - version name that is deployed in App Engine + Name of the version that is deployed in App Engine. If specified, the + configuration of the existing version will be used and app.yaml in the + current directory will be ignored. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/alpha/backup-dr/backup-plan-associations/create b/gcloud/alpha/backup-dr/backup-plan-associations/create index 0bbb7feca..19d1b83dd 100644 --- a/gcloud/alpha/backup-dr/backup-plan-associations/create +++ b/gcloud/alpha/backup-dr/backup-plan-associations/create @@ -119,7 +119,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 backup-dr backup-plan-associations create + $ gcloud beta backup-dr backup-plan-associations create + diff --git a/gcloud/alpha/backup-dr/backup-plan-associations/delete b/gcloud/alpha/backup-dr/backup-plan-associations/delete index 66f58775f..7e9340047 100644 --- a/gcloud/alpha/backup-dr/backup-plan-associations/delete +++ b/gcloud/alpha/backup-dr/backup-plan-associations/delete @@ -74,7 +74,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 backup-dr backup-plan-associations delete + $ gcloud beta backup-dr backup-plan-associations delete + diff --git a/gcloud/alpha/backup-dr/backup-plan-associations/describe b/gcloud/alpha/backup-dr/backup-plan-associations/describe index c54cbbca9..68b78bccf 100644 --- a/gcloud/alpha/backup-dr/backup-plan-associations/describe +++ b/gcloud/alpha/backup-dr/backup-plan-associations/describe @@ -57,14 +57,16 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. API REFERENCE - This command uses the backupdr/v1 API. The full documentation for this API - can be found at: https://cloud.google.com/backup-disaster-recovery + This command uses the backupdr/v1alpha API. The full documentation for this + API can be found at: https://cloud.google.com/backup-disaster-recovery NOTES This command is currently in alpha and might change without notice. If this command fails 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 backup-dr backup-plan-associations describe + $ gcloud beta backup-dr backup-plan-associations describe + diff --git a/gcloud/alpha/backup-dr/backup-plan-associations/fetch-for-resource-type b/gcloud/alpha/backup-dr/backup-plan-associations/fetch-for-resource-type index 8dea21774..af9a5bca7 100644 --- a/gcloud/alpha/backup-dr/backup-plan-associations/fetch-for-resource-type +++ b/gcloud/alpha/backup-dr/backup-plan-associations/fetch-for-resource-type @@ -81,7 +81,10 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: $ gcloud backup-dr backup-plan-associations fetch-for-resource-type + $ gcloud beta backup-dr backup-plan-associations \ + fetch-for-resource-type + diff --git a/gcloud/alpha/backup-dr/backup-plan-associations/help b/gcloud/alpha/backup-dr/backup-plan-associations/help index f5a1171b1..7b9f93f9b 100644 --- a/gcloud/alpha/backup-dr/backup-plan-associations/help +++ b/gcloud/alpha/backup-dr/backup-plan-associations/help @@ -43,7 +43,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: $ gcloud backup-dr backup-plan-associations + $ gcloud beta backup-dr backup-plan-associations + diff --git a/gcloud/alpha/backup-dr/backup-plan-associations/list b/gcloud/alpha/backup-dr/backup-plan-associations/list index e0465bdf5..341b3ce1d 100644 --- a/gcloud/alpha/backup-dr/backup-plan-associations/list +++ b/gcloud/alpha/backup-dr/backup-plan-associations/list @@ -81,14 +81,16 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. API REFERENCE - This command uses the backupdr/v1 API. The full documentation for this API - can be found at: https://cloud.google.com/backup-disaster-recovery + This command uses the backupdr/v1alpha API. The full documentation for this + API can be found at: https://cloud.google.com/backup-disaster-recovery NOTES This command is currently in alpha and might change without notice. If this command fails 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 backup-dr backup-plan-associations list + $ gcloud beta backup-dr backup-plan-associations list + diff --git a/gcloud/alpha/backup-dr/backup-plan-associations/trigger-backup b/gcloud/alpha/backup-dr/backup-plan-associations/trigger-backup index 2b95e2596..7b3bfda69 100644 --- a/gcloud/alpha/backup-dr/backup-plan-associations/trigger-backup +++ b/gcloud/alpha/backup-dr/backup-plan-associations/trigger-backup @@ -92,7 +92,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 backup-dr backup-plan-associations trigger-backup + $ gcloud beta backup-dr backup-plan-associations trigger-backup + diff --git a/gcloud/alpha/backup-dr/backup-plan-associations/update b/gcloud/alpha/backup-dr/backup-plan-associations/update index 38d46ac8e..3e0f2679b 100644 --- a/gcloud/alpha/backup-dr/backup-plan-associations/update +++ b/gcloud/alpha/backup-dr/backup-plan-associations/update @@ -126,7 +126,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: $ gcloud backup-dr backup-plan-associations update + $ gcloud beta backup-dr backup-plan-associations update + diff --git a/gcloud/alpha/backup-dr/backup-plan-revisions/describe b/gcloud/alpha/backup-dr/backup-plan-revisions/describe index c6cfa6754..6999bc89b 100644 --- a/gcloud/alpha/backup-dr/backup-plan-revisions/describe +++ b/gcloud/alpha/backup-dr/backup-plan-revisions/describe @@ -65,14 +65,16 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. API REFERENCE - This command uses the backupdr/v1 API. The full documentation for this API - can be found at: https://cloud.google.com/backup-disaster-recovery + This command uses the backupdr/v1alpha API. The full documentation for this + API can be found at: https://cloud.google.com/backup-disaster-recovery NOTES This command is currently in alpha and might change without notice. If this command fails 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 backup-dr backup-plan-revisions describe + $ gcloud beta backup-dr backup-plan-revisions describe + diff --git a/gcloud/alpha/backup-dr/backup-plan-revisions/help b/gcloud/alpha/backup-dr/backup-plan-revisions/help index 6553c6de8..8e1acc32a 100644 --- a/gcloud/alpha/backup-dr/backup-plan-revisions/help +++ b/gcloud/alpha/backup-dr/backup-plan-revisions/help @@ -26,7 +26,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 backup-dr backup-plan-revisions + $ gcloud beta backup-dr backup-plan-revisions + diff --git a/gcloud/alpha/backup-dr/backup-plan-revisions/list b/gcloud/alpha/backup-dr/backup-plan-revisions/list index a386cc9b4..07b6429fc 100644 --- a/gcloud/alpha/backup-dr/backup-plan-revisions/list +++ b/gcloud/alpha/backup-dr/backup-plan-revisions/list @@ -99,14 +99,16 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. API REFERENCE - This command uses the backupdr/v1 API. The full documentation for this API - can be found at: https://cloud.google.com/backup-disaster-recovery + This command uses the backupdr/v1alpha API. The full documentation for this + API can be found at: https://cloud.google.com/backup-disaster-recovery NOTES This command is currently in alpha and might change without notice. If this command fails 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 backup-dr backup-plan-revisions list + $ gcloud beta backup-dr backup-plan-revisions list + diff --git a/gcloud/alpha/backup-dr/backup-plans/create b/gcloud/alpha/backup-dr/backup-plans/create index edf83006b..087e58cca 100644 --- a/gcloud/alpha/backup-dr/backup-plans/create +++ b/gcloud/alpha/backup-dr/backup-plans/create @@ -5,8 +5,10 @@ SYNOPSIS gcloud alpha backup-dr backup-plans create (BACKUP_PLAN : --location=LOCATION) --backup-vault=BACKUP_VAULT --resource-type=RESOURCE_TYPE [--async] - [--backup-rule=[PROPERTY=VALUE,...]] [--description=DESCRIPTION] - [--disk-properties=[PROPERTY=VALUE,...]] [--labels=[KEY=VALUE,...]] + [--backup-rule=[PROPERTY=VALUE,...]] + [--compute-instance-properties=[PROPERTY=VALUE,...]] + [--description=DESCRIPTION] [--disk-properties=[PROPERTY=VALUE,...]] + [--labels=[KEY=VALUE,...]] [--max-custom-on-demand-retention-days=MAX_CUSTOM_ON_DEMAND_RETENTION_DAYS] [GCLOUD_WIDE_FLAG ...] @@ -231,6 +233,19 @@ OPTIONAL FLAGS "rule-id=sample-daily-rule,recurrence=WEEKLY,backup-window-start=2,backup-window-end=14,retention-days=20,days-of-week='SUNDAY MONDAY'" + --compute-instance-properties=[PROPERTY=VALUE,...] + Workload-specific properties for Compute Engine instance backups + generated by this plan. + + guest-flush + Indicates whether to perform a guest flush operation before taking + a compute backup. When set to true, the system will attempt to + ensure application-consistent backups. When set to false, the + system will create crash-consistent backups. Default value is + false. + + Example: --compute-instance-properties=guest-flush=true + --description=DESCRIPTION Provide a description of the backup plan, such as specific use cases and relevant details, in 2048 characters or less. @@ -278,7 +293,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 backup-dr backup-plans create + $ gcloud beta backup-dr backup-plans create + diff --git a/gcloud/alpha/backup-dr/backup-plans/delete b/gcloud/alpha/backup-dr/backup-plans/delete index 9c199e99f..f1c5b821f 100644 --- a/gcloud/alpha/backup-dr/backup-plans/delete +++ b/gcloud/alpha/backup-dr/backup-plans/delete @@ -68,7 +68,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 backup-dr backup-plans delete + $ gcloud beta backup-dr backup-plans delete + diff --git a/gcloud/alpha/backup-dr/backup-plans/describe b/gcloud/alpha/backup-dr/backup-plans/describe index f7977e24d..d9d82f58a 100644 --- a/gcloud/alpha/backup-dr/backup-plans/describe +++ b/gcloud/alpha/backup-dr/backup-plans/describe @@ -55,14 +55,16 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. API REFERENCE - This command uses the backupdr/v1 API. The full documentation for this API - can be found at: https://cloud.google.com/backup-disaster-recovery + This command uses the backupdr/v1alpha API. The full documentation for this + API can be found at: https://cloud.google.com/backup-disaster-recovery NOTES This command is currently in alpha and might change without notice. If this command fails 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 backup-dr backup-plans describe + $ gcloud beta backup-dr backup-plans describe + diff --git a/gcloud/alpha/backup-dr/backup-plans/help b/gcloud/alpha/backup-dr/backup-plans/help index fc94508c3..18f78bc5d 100644 --- a/gcloud/alpha/backup-dr/backup-plans/help +++ b/gcloud/alpha/backup-dr/backup-plans/help @@ -34,7 +34,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: $ gcloud backup-dr backup-plans + $ gcloud beta backup-dr backup-plans + diff --git a/gcloud/alpha/backup-dr/backup-plans/list b/gcloud/alpha/backup-dr/backup-plans/list index 99d63cc39..7d9cb9010 100644 --- a/gcloud/alpha/backup-dr/backup-plans/list +++ b/gcloud/alpha/backup-dr/backup-plans/list @@ -78,14 +78,16 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. API REFERENCE - This command uses the backupdr/v1 API. The full documentation for this API - can be found at: https://cloud.google.com/backup-disaster-recovery + This command uses the backupdr/v1alpha API. The full documentation for this + API can be found at: https://cloud.google.com/backup-disaster-recovery NOTES This command is currently in alpha and might change without notice. If this command fails 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 backup-dr backup-plans list + $ gcloud beta backup-dr backup-plans list + diff --git a/gcloud/alpha/backup-dr/backup-plans/update b/gcloud/alpha/backup-dr/backup-plans/update index 8cb32f5e0..77dfd6828 100644 --- a/gcloud/alpha/backup-dr/backup-plans/update +++ b/gcloud/alpha/backup-dr/backup-plans/update @@ -6,8 +6,9 @@ SYNOPSIS (BACKUP_PLAN : --location=LOCATION) [--add-backup-rule=[PROPERTY=VALUE,...]] [--async] [--backup-rule=[PROPERTY=VALUE,...]] - [--backup-rules-from-file=PATH_TO_FILE] [--description=DESCRIPTION] - [--disk-properties=[PROPERTY=VALUE,...]] + [--backup-rules-from-file=PATH_TO_FILE] + [--compute-instance-properties=[PROPERTY=VALUE,...]] + [--description=DESCRIPTION] [--disk-properties=[PROPERTY=VALUE,...]] [--max-custom-on-demand-retention-days=MAX_CUSTOM_ON_DEMAND_RETENTION_DAYS] [--remove-backup-rule=RULE-ID] [GCLOUD_WIDE_FLAG ...] @@ -261,6 +262,19 @@ FLAGS Path to a YAML or JSON file containing backup rules. Use a full or relative path to a local file containing the value of backup_rules. + --compute-instance-properties=[PROPERTY=VALUE,...] + Workload-specific properties for Compute Engine instance backups + generated by this plan. + + guest-flush + Indicates whether to perform a guest flush operation before taking + a compute backup. When set to true, the system will attempt to + ensure application-consistent backups. When set to false, the + system will create crash-consistent backups. Default value is + false. + + Example: --compute-instance-properties=guest-flush=true + --description=DESCRIPTION Provide a description of the backup plan, such as specific use cases and relevant details, in 2048 characters or less. @@ -303,7 +317,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 backup-dr backup-plans update + $ gcloud beta backup-dr backup-plans update + diff --git a/gcloud/alpha/backup-dr/backup-vaults/create b/gcloud/alpha/backup-dr/backup-vaults/create index 513e02651..5fcac02aa 100644 --- a/gcloud/alpha/backup-dr/backup-vaults/create +++ b/gcloud/alpha/backup-dr/backup-vaults/create @@ -145,7 +145,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 backup-dr backup-vaults create + $ gcloud beta backup-dr backup-vaults create + diff --git a/gcloud/alpha/backup-dr/backup-vaults/delete b/gcloud/alpha/backup-dr/backup-vaults/delete index 06d213e49..55d2efdab 100644 --- a/gcloud/alpha/backup-dr/backup-vaults/delete +++ b/gcloud/alpha/backup-dr/backup-vaults/delete @@ -101,7 +101,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 backup-dr backup-vaults delete + $ gcloud beta backup-dr backup-vaults delete + diff --git a/gcloud/alpha/backup-dr/backup-vaults/describe b/gcloud/alpha/backup-dr/backup-vaults/describe index 491d1fe6e..be74fb25f 100644 --- a/gcloud/alpha/backup-dr/backup-vaults/describe +++ b/gcloud/alpha/backup-dr/backup-vaults/describe @@ -65,7 +65,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 backup-dr backup-vaults describe + $ gcloud beta backup-dr backup-vaults describe + diff --git a/gcloud/alpha/backup-dr/backup-vaults/help b/gcloud/alpha/backup-dr/backup-vaults/help index 2e3ada38f..7b7b51318 100644 --- a/gcloud/alpha/backup-dr/backup-vaults/help +++ b/gcloud/alpha/backup-dr/backup-vaults/help @@ -34,7 +34,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: $ gcloud backup-dr backup-vaults + $ gcloud beta backup-dr backup-vaults + diff --git a/gcloud/alpha/backup-dr/backup-vaults/list b/gcloud/alpha/backup-dr/backup-vaults/list index 76bfaabb6..f0fb3b285 100644 --- a/gcloud/alpha/backup-dr/backup-vaults/list +++ b/gcloud/alpha/backup-dr/backup-vaults/list @@ -89,7 +89,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: $ gcloud backup-dr backup-vaults list + $ gcloud beta backup-dr backup-vaults list + diff --git a/gcloud/alpha/backup-dr/backup-vaults/update b/gcloud/alpha/backup-dr/backup-vaults/update index c551c03c9..db5687432 100644 --- a/gcloud/alpha/backup-dr/backup-vaults/update +++ b/gcloud/alpha/backup-dr/backup-vaults/update @@ -146,7 +146,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 backup-dr backup-vaults update + $ gcloud beta backup-dr backup-vaults update + diff --git a/gcloud/alpha/backup-dr/backups/delete b/gcloud/alpha/backup-dr/backups/delete index 28b4a042a..71b844e74 100644 --- a/gcloud/alpha/backup-dr/backups/delete +++ b/gcloud/alpha/backup-dr/backups/delete @@ -86,7 +86,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 backup-dr backups delete + $ gcloud beta backup-dr backups delete + diff --git a/gcloud/alpha/backup-dr/backups/describe b/gcloud/alpha/backup-dr/backups/describe index 44282f3f9..a4f787452 100644 --- a/gcloud/alpha/backup-dr/backups/describe +++ b/gcloud/alpha/backup-dr/backups/describe @@ -70,14 +70,16 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. API REFERENCE - This command uses the backupdr/v1 API. The full documentation for this API - can be found at: https://cloud.google.com/backup-disaster-recovery + This command uses the backupdr/v1alpha API. The full documentation for this + API can be found at: https://cloud.google.com/backup-disaster-recovery NOTES This command is currently in alpha and might change without notice. If this command fails 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 backup-dr backups describe + $ gcloud beta backup-dr backups describe + diff --git a/gcloud/alpha/backup-dr/backups/fetch-for-resource-type b/gcloud/alpha/backup-dr/backups/fetch-for-resource-type index 40e9416e4..1b18d616a 100644 --- a/gcloud/alpha/backup-dr/backups/fetch-for-resource-type +++ b/gcloud/alpha/backup-dr/backups/fetch-for-resource-type @@ -112,7 +112,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 backup-dr backups fetch-for-resource-type + $ gcloud beta backup-dr backups fetch-for-resource-type + diff --git a/gcloud/alpha/backup-dr/backups/help b/gcloud/alpha/backup-dr/backups/help index 4e0981cf3..8c6dcb954 100644 --- a/gcloud/alpha/backup-dr/backups/help +++ b/gcloud/alpha/backup-dr/backups/help @@ -40,7 +40,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 backup-dr backups + $ gcloud beta backup-dr backups + diff --git a/gcloud/alpha/backup-dr/backups/list b/gcloud/alpha/backup-dr/backups/list index aa3c49288..efda43f7f 100644 --- a/gcloud/alpha/backup-dr/backups/list +++ b/gcloud/alpha/backup-dr/backups/list @@ -103,14 +103,16 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. API REFERENCE - This command uses the backupdr/v1 API. The full documentation for this API - can be found at: https://cloud.google.com/backup-disaster-recovery + This command uses the backupdr/v1alpha API. The full documentation for this + API can be found at: https://cloud.google.com/backup-disaster-recovery NOTES This command is currently in alpha and might change without notice. If this command fails 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 backup-dr backups list + $ gcloud beta backup-dr backups list + diff --git a/gcloud/alpha/backup-dr/backups/restore/compute b/gcloud/alpha/backup-dr/backups/restore/compute index 136137a98..c8d09e4f3 100644 --- a/gcloud/alpha/backup-dr/backups/restore/compute +++ b/gcloud/alpha/backup-dr/backups/restore/compute @@ -428,7 +428,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 backup-dr backups restore compute + $ gcloud beta backup-dr backups restore compute + diff --git a/gcloud/alpha/backup-dr/backups/restore/disk b/gcloud/alpha/backup-dr/backups/restore/disk index bdd1decb9..cc45006f9 100644 --- a/gcloud/alpha/backup-dr/backups/restore/disk +++ b/gcloud/alpha/backup-dr/backups/restore/disk @@ -216,7 +216,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 backup-dr backups restore disk + $ gcloud beta backup-dr backups restore disk + diff --git a/gcloud/alpha/backup-dr/backups/restore/help b/gcloud/alpha/backup-dr/backups/restore/help index 697f68226..6fbb75bd0 100644 --- a/gcloud/alpha/backup-dr/backups/restore/help +++ b/gcloud/alpha/backup-dr/backups/restore/help @@ -26,7 +26,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 backup-dr backups restore + $ gcloud beta backup-dr backups restore + diff --git a/gcloud/alpha/backup-dr/backups/update b/gcloud/alpha/backup-dr/backups/update index 97674e726..699e17617 100644 --- a/gcloud/alpha/backup-dr/backups/update +++ b/gcloud/alpha/backup-dr/backups/update @@ -148,7 +148,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 backup-dr backups update + $ gcloud beta backup-dr backups update + diff --git a/gcloud/alpha/backup-dr/data-source-references/describe b/gcloud/alpha/backup-dr/data-source-references/describe index eb7c8ab01..b1e03cdfb 100644 --- a/gcloud/alpha/backup-dr/data-source-references/describe +++ b/gcloud/alpha/backup-dr/data-source-references/describe @@ -57,14 +57,16 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. API REFERENCE - This command uses the backupdr/v1 API. The full documentation for this API - can be found at: https://cloud.google.com/backup-disaster-recovery + This command uses the backupdr/v1alpha API. The full documentation for this + API can be found at: https://cloud.google.com/backup-disaster-recovery NOTES This command is currently in alpha and might change without notice. If this command fails 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 backup-dr data-source-references describe + $ gcloud beta backup-dr data-source-references describe + diff --git a/gcloud/alpha/backup-dr/data-source-references/fetch-for-resource-type b/gcloud/alpha/backup-dr/data-source-references/fetch-for-resource-type index 7e70ab280..cfc9dd50f 100644 --- a/gcloud/alpha/backup-dr/data-source-references/fetch-for-resource-type +++ b/gcloud/alpha/backup-dr/data-source-references/fetch-for-resource-type @@ -77,7 +77,10 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: $ gcloud backup-dr data-source-references fetch-for-resource-type + $ gcloud beta backup-dr data-source-references \ + fetch-for-resource-type + diff --git a/gcloud/alpha/backup-dr/data-source-references/help b/gcloud/alpha/backup-dr/data-source-references/help index 7336856c8..861455143 100644 --- a/gcloud/alpha/backup-dr/data-source-references/help +++ b/gcloud/alpha/backup-dr/data-source-references/help @@ -31,7 +31,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 backup-dr data-source-references + $ gcloud beta backup-dr data-source-references + diff --git a/gcloud/alpha/backup-dr/data-source-references/list b/gcloud/alpha/backup-dr/data-source-references/list index a01134736..bc8a83f89 100644 --- a/gcloud/alpha/backup-dr/data-source-references/list +++ b/gcloud/alpha/backup-dr/data-source-references/list @@ -80,14 +80,16 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. API REFERENCE - This command uses the backupdr/v1 API. The full documentation for this API - can be found at: https://cloud.google.com/backup-disaster-recovery + This command uses the backupdr/v1alpha API. The full documentation for this + API can be found at: https://cloud.google.com/backup-disaster-recovery NOTES This command is currently in alpha and might change without notice. If this command fails 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 backup-dr data-source-references list + $ gcloud beta backup-dr data-source-references list + diff --git a/gcloud/alpha/backup-dr/data-sources/describe b/gcloud/alpha/backup-dr/data-sources/describe index 55b4c9c0f..13fff0327 100644 --- a/gcloud/alpha/backup-dr/data-sources/describe +++ b/gcloud/alpha/backup-dr/data-sources/describe @@ -65,14 +65,16 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. API REFERENCE - This command uses the backupdr/v1 API. The full documentation for this API - can be found at: https://cloud.google.com/backup-disaster-recovery + This command uses the backupdr/v1alpha API. The full documentation for this + API can be found at: https://cloud.google.com/backup-disaster-recovery NOTES This command is currently in alpha and might change without notice. If this command fails 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 backup-dr data-sources describe + $ gcloud beta backup-dr data-sources describe + diff --git a/gcloud/alpha/backup-dr/data-sources/help b/gcloud/alpha/backup-dr/data-sources/help index 0327450dd..4533e1ccd 100644 --- a/gcloud/alpha/backup-dr/data-sources/help +++ b/gcloud/alpha/backup-dr/data-sources/help @@ -25,7 +25,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 backup-dr data-sources + $ gcloud beta backup-dr data-sources + diff --git a/gcloud/alpha/backup-dr/data-sources/list b/gcloud/alpha/backup-dr/data-sources/list index 274c426af..6aff0d874 100644 --- a/gcloud/alpha/backup-dr/data-sources/list +++ b/gcloud/alpha/backup-dr/data-sources/list @@ -93,14 +93,16 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. API REFERENCE - This command uses the backupdr/v1 API. The full documentation for this API - can be found at: https://cloud.google.com/backup-disaster-recovery + This command uses the backupdr/v1alpha API. The full documentation for this + API can be found at: https://cloud.google.com/backup-disaster-recovery NOTES This command is currently in alpha and might change without notice. If this command fails 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 backup-dr data-sources list + $ gcloud beta backup-dr data-sources list + diff --git a/gcloud/alpha/backup-dr/locations/list b/gcloud/alpha/backup-dr/locations/list index d7ee2be95..7d617f32f 100644 --- a/gcloud/alpha/backup-dr/locations/list +++ b/gcloud/alpha/backup-dr/locations/list @@ -56,8 +56,8 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. API REFERENCE - This command uses the backupdr/v1 API. The full documentation for this API - can be found at: https://cloud.google.com/backup-disaster-recovery + This command uses the backupdr/v1alpha API. The full documentation for this + API can be found at: https://cloud.google.com/backup-disaster-recovery NOTES This command is currently in alpha and might change without notice. If this diff --git a/gcloud/alpha/backup-dr/management-servers/describe b/gcloud/alpha/backup-dr/management-servers/describe index a19a94bd6..20d38d9e7 100644 --- a/gcloud/alpha/backup-dr/management-servers/describe +++ b/gcloud/alpha/backup-dr/management-servers/describe @@ -57,8 +57,8 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. API REFERENCE - This command uses the backupdr/v1 API. The full documentation for this API - can be found at: https://cloud.google.com/backup-disaster-recovery + This command uses the backupdr/v1alpha API. The full documentation for this + API can be found at: https://cloud.google.com/backup-disaster-recovery NOTES This command is currently in alpha and might change without notice. If this diff --git a/gcloud/alpha/backup-dr/management-servers/list b/gcloud/alpha/backup-dr/management-servers/list index 93bf1a4ae..180a9f92b 100644 --- a/gcloud/alpha/backup-dr/management-servers/list +++ b/gcloud/alpha/backup-dr/management-servers/list @@ -81,8 +81,8 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. API REFERENCE - This command uses the backupdr/v1 API. The full documentation for this API - can be found at: https://cloud.google.com/backup-disaster-recovery + This command uses the backupdr/v1alpha API. The full documentation for this + API can be found at: https://cloud.google.com/backup-disaster-recovery NOTES This command is currently in alpha and might change without notice. If this diff --git a/gcloud/alpha/backup-dr/operations/describe b/gcloud/alpha/backup-dr/operations/describe index 8722ef76f..32e634ca2 100644 --- a/gcloud/alpha/backup-dr/operations/describe +++ b/gcloud/alpha/backup-dr/operations/describe @@ -53,8 +53,8 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. API REFERENCE - This command uses the backupdr/v1 API. The full documentation for this API - can be found at: https://cloud.google.com/backup-disaster-recovery + This command uses the backupdr/v1alpha API. The full documentation for this + API can be found at: https://cloud.google.com/backup-disaster-recovery NOTES This command is currently in alpha and might change without notice. If this diff --git a/gcloud/alpha/backup-dr/operations/list b/gcloud/alpha/backup-dr/operations/list index c76105922..ca357ad30 100644 --- a/gcloud/alpha/backup-dr/operations/list +++ b/gcloud/alpha/backup-dr/operations/list @@ -78,8 +78,8 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. API REFERENCE - This command uses the backupdr/v1 API. The full documentation for this API - can be found at: https://cloud.google.com/backup-disaster-recovery + This command uses the backupdr/v1alpha API. The full documentation for this + API can be found at: https://cloud.google.com/backup-disaster-recovery NOTES This command is currently in alpha and might change without notice. If this diff --git a/gcloud/alpha/backup-dr/resource-backup-config/help b/gcloud/alpha/backup-dr/resource-backup-config/help index 2521b1f09..b58ce6e00 100644 --- a/gcloud/alpha/backup-dr/resource-backup-config/help +++ b/gcloud/alpha/backup-dr/resource-backup-config/help @@ -26,7 +26,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 backup-dr resource-backup-config + $ gcloud beta backup-dr resource-backup-config + diff --git a/gcloud/alpha/backup-dr/resource-backup-config/list b/gcloud/alpha/backup-dr/resource-backup-config/list index 2fb835d81..7660095c9 100644 --- a/gcloud/alpha/backup-dr/resource-backup-config/list +++ b/gcloud/alpha/backup-dr/resource-backup-config/list @@ -138,7 +138,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 backup-dr resource-backup-config list + $ gcloud beta backup-dr resource-backup-config list + diff --git a/gcloud/alpha/backup-dr/service-config/help b/gcloud/alpha/backup-dr/service-config/help index 71d5d5242..f1e95cce7 100644 --- a/gcloud/alpha/backup-dr/service-config/help +++ b/gcloud/alpha/backup-dr/service-config/help @@ -23,7 +23,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 backup-dr service-config + $ gcloud beta backup-dr service-config + diff --git a/gcloud/alpha/backup-dr/service-config/init b/gcloud/alpha/backup-dr/service-config/init index c8ff4628f..75992d6f6 100644 --- a/gcloud/alpha/backup-dr/service-config/init +++ b/gcloud/alpha/backup-dr/service-config/init @@ -70,7 +70,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 backup-dr service-config init + $ gcloud beta backup-dr service-config init + diff --git a/gcloud/alpha/biglake/iceberg/catalogs/create b/gcloud/alpha/biglake/iceberg/catalogs/create index d53faf1ce..da42e7d96 100644 --- a/gcloud/alpha/biglake/iceberg/catalogs/create +++ b/gcloud/alpha/biglake/iceberg/catalogs/create @@ -6,8 +6,13 @@ SYNOPSIS gcloud alpha biglake iceberg catalogs create CATALOG --catalog-type=CATALOG_TYPE [--credential-mode=CREDENTIAL_MODE; default="end-user"] - [--description=DESCRIPTION] [--primary-location=PRIMARY_LOCATION] - [GCLOUD_WIDE_FLAG ...] + [--description=DESCRIPTION] + [--federated-catalog-type=FEDERATED_CATALOG_TYPE] + [--namespace-filters=[NAMESPACE,...]] + [--primary-location=PRIMARY_LOCATION] + [--refresh-interval=REFRESH_INTERVAL] [--secret-name=SECRET_NAME] + [--unity-catalog-name=UNITY_CATALOG_NAME] + [--unity-instance-name=UNITY_INSTANCE_NAME] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Create a BigLake Iceberg REST catalog. @@ -24,6 +29,15 @@ EXAMPLES $ gcloud alpha biglake iceberg catalogs create my-catalog-bucket \ --catalog-type=gcs-bucket --credential-mode=vended-credentials + To create a unity federated catalog my-federated-catalog, run: + + $ gcloud alpha biglake iceberg catalogs create \ + my-federated-catalog --catalog-type=federated \ + --federated-catalog-type=unity \ + --secret-name=projects/my-project/locations/us/secrets/\ + my-secret --unity-instance-name=instance.cloud.databricks.com \ + --unity-catalog-name=my-catalog --primary-location=us + POSITIONAL ARGUMENTS Catalog resource - The Iceberg Catalog to create. This represents a Cloud resource. (NOTE) Some attributes are not given arguments in this group but @@ -62,13 +76,40 @@ OPTIONAL FLAGS Use vended credentials to access the catalog. --description=DESCRIPTION - Description of the resource being created. + Description of the resource. + + --federated-catalog-type=FEDERATED_CATALOG_TYPE + Type of the federated catalog. FEDERATED_CATALOG_TYPE must be (only one + value is supported): unity. + + --namespace-filters=[NAMESPACE,...] + Filters to determine which namespaces are included in the refresh + process. Empty list means include all namespaces. --primary-location=PRIMARY_LOCATION Primary location for mirroring the remote catalog metadata. It must be a BigLake-supported location, and it should be proximate to the remote catalog's location for better performance and lower cost. + --refresh-interval=REFRESH_INTERVAL + The interval for refreshing metadata from the remote catalog (e.g., + "1hr5m30s"). Defaults to seconds if no unit is specified. If unset, the + refresh interval will be set to 0s (background refresh disabled). + + --secret-name=SECRET_NAME + The secret resource name in Secret Manager, in the format + projects/{project_id}/locations/{location}/secrets/{secret_id} or + projects/{project_id}/locations/{location}/secrets/{secret_id}/versions/{version_id}. + + --unity-catalog-name=UNITY_CATALOG_NAME + Name of the catalog in Unity Catalog. + + --unity-instance-name=UNITY_INSTANCE_NAME + The instance name is the first part of the URL when you log into your + Databricks deployment. For example, for a Databricks on Google Cloud + workspace URL https://1.1.gcp.databricks.com, the instance name is + 1.1.gcp.databricks.com. + 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/biglake/iceberg/catalogs/update b/gcloud/alpha/biglake/iceberg/catalogs/update index dcac6e459..a13bfe3a7 100644 --- a/gcloud/alpha/biglake/iceberg/catalogs/update +++ b/gcloud/alpha/biglake/iceberg/catalogs/update @@ -5,11 +5,26 @@ NAME SYNOPSIS gcloud alpha biglake iceberg catalogs update CATALOG [--credential-mode=CREDENTIAL_MODE; default="end-user"] - [--description=DESCRIPTION] [GCLOUD_WIDE_FLAG ...] + [--description=DESCRIPTION] [--namespace-filters=[NAMESPACE,...]] + [--refresh-interval=REFRESH_INTERVAL] [--secret-name=SECRET_NAME] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Update a BigLake Iceberg REST catalog. +EXAMPLES + To update the description of a catalog my-catalog, run: + + $ gcloud alpha biglake iceberg catalogs update my-catalog \ + --description="updated description" + + To update the refresh interval and namespace filters for a federated + catalog my-federated-catalog, run: + + $ gcloud alpha biglake iceberg catalogs update \ + my-federated-catalog --refresh-interval=1h \ + --namespace-filters=db1,db2 + POSITIONAL ARGUMENTS Catalog resource - The Iceberg Catalog to update. This represents a Cloud resource. (NOTE) Some attributes are not given arguments in this group but @@ -40,7 +55,21 @@ FLAGS Use vended credentials to access the catalog. --description=DESCRIPTION - Description of the resource being created. + Description of the resource. + + --namespace-filters=[NAMESPACE,...] + Filters to determine which namespaces are included in the refresh + process. Empty list means include all namespaces. + + --refresh-interval=REFRESH_INTERVAL + Interval for refreshing metadata from the remote catalog (e.g., + "1hr5m30s"). Defaults to seconds if no unit is specified. If unset, the + refresh interval will be set to 0s (background refresh disabled). + + --secret-name=SECRET_NAME + Resource name of the Secret Manager secret, in the format + projects/{project_id}/locations/{location}/secrets/{secret_id} or + projects/{project_id}/locations/{location}/secrets/{secret_id}/versions/{version_id}. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/alpha/biglake/iceberg/tables/create b/gcloud/alpha/biglake/iceberg/tables/create index b689ac9ee..1d7a6d516 100644 --- a/gcloud/alpha/biglake/iceberg/tables/create +++ b/gcloud/alpha/biglake/iceberg/tables/create @@ -123,7 +123,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 biglake iceberg tables create $ gcloud beta biglake iceberg tables create diff --git a/gcloud/alpha/biglake/iceberg/tables/delete b/gcloud/alpha/biglake/iceberg/tables/delete index 39bb29453..902d36486 100644 --- a/gcloud/alpha/biglake/iceberg/tables/delete +++ b/gcloud/alpha/biglake/iceberg/tables/delete @@ -67,7 +67,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud biglake iceberg tables delete $ gcloud beta biglake iceberg tables delete diff --git a/gcloud/alpha/biglake/iceberg/tables/describe b/gcloud/alpha/biglake/iceberg/tables/describe index 2dae767fd..6ea4384e7 100644 --- a/gcloud/alpha/biglake/iceberg/tables/describe +++ b/gcloud/alpha/biglake/iceberg/tables/describe @@ -72,7 +72,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 biglake iceberg tables describe $ gcloud beta biglake iceberg tables describe diff --git a/gcloud/alpha/biglake/iceberg/tables/get-iam-policy b/gcloud/alpha/biglake/iceberg/tables/get-iam-policy index 86ede004b..be968157c 100644 --- a/gcloud/alpha/biglake/iceberg/tables/get-iam-policy +++ b/gcloud/alpha/biglake/iceberg/tables/get-iam-policy @@ -95,7 +95,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 biglake iceberg tables get-iam-policy $ gcloud beta biglake iceberg tables get-iam-policy diff --git a/gcloud/alpha/biglake/iceberg/tables/help b/gcloud/alpha/biglake/iceberg/tables/help index 53688b8a1..7142d2248 100644 --- a/gcloud/alpha/biglake/iceberg/tables/help +++ b/gcloud/alpha/biglake/iceberg/tables/help @@ -44,7 +44,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud biglake iceberg tables $ gcloud beta biglake iceberg tables diff --git a/gcloud/alpha/biglake/iceberg/tables/list b/gcloud/alpha/biglake/iceberg/tables/list index ff7e1a445..4278c3026 100644 --- a/gcloud/alpha/biglake/iceberg/tables/list +++ b/gcloud/alpha/biglake/iceberg/tables/list @@ -92,7 +92,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 biglake iceberg tables list $ gcloud beta biglake iceberg tables list diff --git a/gcloud/alpha/biglake/iceberg/tables/register b/gcloud/alpha/biglake/iceberg/tables/register index 0cbf1409a..851acf7bb 100644 --- a/gcloud/alpha/biglake/iceberg/tables/register +++ b/gcloud/alpha/biglake/iceberg/tables/register @@ -85,7 +85,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 biglake iceberg tables register $ gcloud beta biglake iceberg tables register diff --git a/gcloud/alpha/biglake/iceberg/tables/set-iam-policy b/gcloud/alpha/biglake/iceberg/tables/set-iam-policy index 78ec11cca..f095bc631 100644 --- a/gcloud/alpha/biglake/iceberg/tables/set-iam-policy +++ b/gcloud/alpha/biglake/iceberg/tables/set-iam-policy @@ -75,7 +75,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 biglake iceberg tables set-iam-policy $ gcloud beta biglake iceberg tables set-iam-policy diff --git a/gcloud/alpha/biglake/iceberg/tables/update b/gcloud/alpha/biglake/iceberg/tables/update index 05f80348e..e67862084 100644 --- a/gcloud/alpha/biglake/iceberg/tables/update +++ b/gcloud/alpha/biglake/iceberg/tables/update @@ -91,7 +91,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 biglake iceberg tables update $ gcloud beta biglake iceberg tables update diff --git a/gcloud/alpha/bigtable/app-profiles/create b/gcloud/alpha/bigtable/app-profiles/create index 6ae3b6738..6980410f2 100644 --- a/gcloud/alpha/bigtable/app-profiles/create +++ b/gcloud/alpha/bigtable/app-profiles/create @@ -10,7 +10,8 @@ SYNOPSIS [--description=DESCRIPTION] [--force] [--data-boost --data-boost-compute-billing-owner=DATA_BOOST_COMPUTE_BILLING_OWNER - | --priority=PRIORITY --standard] [GCLOUD_WIDE_FLAG ...] + | --priority=PRIORITY --standard --use-memory-layer] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Create a new Bigtable app profile. @@ -51,6 +52,12 @@ EXAMPLES $ gcloud alpha bigtable app-profiles create my-app-profile-id \ --instance=my-instance-id --route-any --row-affinity + To create an app profile with the memory layer enabled, run: + + $ gcloud alpha bigtable app-profiles create my-app-profile-id \ + --instance=my-instance-id --route-to=my-cluster-id \ + --use-memory-layer + POSITIONAL ARGUMENTS App profile resource - The app profile to create. The arguments in this group can be used to specify the attributes of this resource. (NOTE) Some @@ -170,6 +177,12 @@ OPTIONAL FLAGS compute option. If specified, --priority or --use-memory-layer is required. + --use-memory-layer + Enables the in-memory layer for standard provisioned node compute. + This option sets the compute option to --standard with the in-memory + layer enabled. Use --no-use-memory-layer to disable the in-memory + layer. + 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/app-profiles/update b/gcloud/alpha/bigtable/app-profiles/update index 1d9d9a8a4..06e089851 100644 --- a/gcloud/alpha/bigtable/app-profiles/update +++ b/gcloud/alpha/bigtable/app-profiles/update @@ -7,7 +7,7 @@ SYNOPSIS [--description=DESCRIPTION] [--force] [--data-boost --data-boost-compute-billing-owner=DATA_BOOST_COMPUTE_BILLING_OWNER - | --priority=PRIORITY --standard] + | --priority=PRIORITY --standard --use-memory-layer] [[--route-any : --restrict-to=[RESTRICT_TO,...] --row-affinity] | [--route-to=ROUTE_TO : --transactional-writes]] [GCLOUD_WIDE_FLAG ...] @@ -50,6 +50,11 @@ EXAMPLES $ gcloud alpha bigtable app-profiles update my-app-profile-id \ --instance=my-instance-id --route-any --row-affinity + To update an app profile to use the memory layer, run: + + $ gcloud alpha bigtable app-profiles update my-app-profile-id \ + --instance=my-instance-id --use-memory-layer + POSITIONAL ARGUMENTS App profile resource - The app profile to update. The arguments in this group can be used to specify the attributes of this resource. (NOTE) Some @@ -144,6 +149,12 @@ FLAGS compute option. If specified, --priority or --use-memory-layer is required. + --use-memory-layer + Enables the in-memory layer for standard provisioned node compute. + This option sets the compute option to --standard with the in-memory + layer enabled. Use --no-use-memory-layer to disable the in-memory + layer. + At most one of these can be specified: Multi Cluster Routing Policy diff --git a/gcloud/alpha/bigtable/help b/gcloud/alpha/bigtable/help index ff0e21097..9403daedc 100644 --- a/gcloud/alpha/bigtable/help +++ b/gcloud/alpha/bigtable/help @@ -39,6 +39,9 @@ GROUPS materialized-views (ALPHA) Manage Bigtable materialized views. + memory-layers + (ALPHA) Manage Cloud Bigtable memory layers. + operations (ALPHA) Manage Cloud Bigtable operations. diff --git a/gcloud/alpha/bigtable/instances/create b/gcloud/alpha/bigtable/instances/create index da825b1c9..e79d688d5 100644 --- a/gcloud/alpha/bigtable/instances/create +++ b/gcloud/alpha/bigtable/instances/create @@ -12,7 +12,7 @@ SYNOPSIS autoscaling-storage-target=AUTOSCALING_STORAGE_TARGET],...]] [--cluster-num-nodes=CLUSTER_NUM_NODES] [--cluster-storage-type=CLUSTER_STORAGE_TYPE; default="ssd"] - [--cluster-zone=CLUSTER_ZONE] + [--cluster-zone=CLUSTER_ZONE] [--edition=EDITION] [--instance-type=INSTANCE_TYPE; default="PRODUCTION"] [GCLOUD_WIDE_FLAG ...] @@ -40,6 +40,14 @@ EXAMPLES --display-name="HDD Instance" --cluster-storage-type=HDD \ --cluster-config=id=my-cluster-id,zone=us-east1-c,nodes=10 + To create an instance with edition ENTERPRISE_PLUS, run: + + $ gcloud alpha bigtable instances create \ + my-enterprise-plus-instance \ + --display-name="Enterprise Plus Instance" \ + --edition=ENTERPRISE_PLUS \ + --cluster-config=id=my-cluster-id,zone=us-east1-c,nodes=1 + POSITIONAL ARGUMENTS Instance resource - The instance to create. This represents a Cloud resource. (NOTE) Some attributes are not given arguments in this group but @@ -121,6 +129,10 @@ OPTIONAL FLAGS The --cluster-zone argument is deprecated; use --cluster-config instead. + --edition=EDITION + The edition of the instance. EDITION must be one of: ENTERPRISE, + ENTERPRISE_PLUS. + --instance-type=INSTANCE_TYPE; default="PRODUCTION" (DEPRECATED) The type of instance to create. diff --git a/gcloud/alpha/bigtable/instances/tables/create b/gcloud/alpha/bigtable/instances/tables/create index 02cfc12e1..cf19f1ff0 100644 --- a/gcloud/alpha/bigtable/instances/tables/create +++ b/gcloud/alpha/bigtable/instances/tables/create @@ -10,8 +10,10 @@ SYNOPSIS [--row-key-schema-definition-file=ROW_KEY_SCHEMA_DEFINITION_FILE] [--row-key-schema-pre-encoded-bytes] [--splits=[SPLITS,...]] [--tiered-storage-infrequent-access-older-than=TIERED_STORAGE_INFREQUENT_ACCESS_OLDER_THAN] - [--automated-backup-retention-period=AUTOMATED_BACKUP_RETENTION_PERIOD - | --enable-automated-backup] [GCLOUD_WIDE_FLAG ...] + [--enable-automated-backup + | --automated-backup-locations=[LOCATION,...] + --automated-backup-retention-period=AUTOMATED_BACKUP_RETENTION_PERIOD] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Create a new Cloud Bigtable table. @@ -80,6 +82,13 @@ EXAMPLES --instance=my-instance --column-families="my-family" \ --automated-backup-retention_period=30d + To create a table my-table with a custom automated backup policy configured + to take backups in only us-central1-b and us-east1-c, run: + + $ gcloud alpha bigtable instances tables create my-table \ + --instance=my-instance \ + --automated-backup-locations=us-central1-b,us-east1-c + POSITIONAL ARGUMENTS Table resource - Cloud Bigtable table to create. The arguments in this group can be used to specify the attributes of this resource. (NOTE) Some @@ -168,15 +177,28 @@ OPTIONAL FLAGS At most one of these can be specified: - --automated-backup-retention-period=AUTOMATED_BACKUP_RETENTION_PERIOD - The retention period of automated backup in the format of 30d for 30 - days. Min retention period is 3d and max is 90d. Setting this flag - will enable automated backup for the table. - --enable-automated-backup Once set, enables the default automated backup policy (retention_period=7d, frequency=1d) for the table. + Or at least one of these can be specified: + + Group for automated backup policy parameters. + + --automated-backup-locations=[LOCATION,...] + List of Cloud Bigtable zones where automated backups are allowed to + be created. If empty, automated backups will be created in all + zones of the instance. Locations are in the format + projects/{project}/locations/{zone}. Setting this flag will enable + automated backup for the table. If automated backup retention + period is not specified, it defaults to 7 days. + + --automated-backup-retention-period=AUTOMATED_BACKUP_RETENTION_PERIOD + The retention period of automated backup in the format of 30d for + 30 days. Min retention period is 3d and max is 90d. Setting this + flag will enable automated backup for the table. If automated + backup retention period is not specified, it defaults to 7 days. + 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/instances/tables/update b/gcloud/alpha/bigtable/instances/tables/update index d8379c74f..3af4255ab 100644 --- a/gcloud/alpha/bigtable/instances/tables/update +++ b/gcloud/alpha/bigtable/instances/tables/update @@ -6,7 +6,9 @@ SYNOPSIS gcloud alpha bigtable instances tables update (TABLE : --instance=INSTANCE) [--async] [--deletion-protection] [--row-key-schema-pre-encoded-bytes] [--automated-backup-retention-period=AUTOMATED_BACKUP_RETENTION_PERIOD - | --disable-automated-backup | --enable-automated-backup] + --automated-backup-locations=[LOCATION,...] + | --clear-automated-backup-locations | --disable-automated-backup + | --enable-automated-backup] [--change-stream-retention-period=CHANGE_STREAM_RETENTION_PERIOD | --clear-change-stream-retention-period] [--clear-row-key-schema @@ -56,7 +58,19 @@ EXAMPLES retain backups for 30 days, run: $ gcloud alpha bigtable instances tables update my-table \ - --instance=my-instance --automated-backup-retention_period=30d + --instance=my-instance --automated-backup-retention-period=30d + + To enable or update a custom automated backup policy and configure it to + take backups in only us-central1-b and us-east1-c, run: + + $ gcloud alpha bigtable instances tables update my-table \ + --instance=my-instance \ + --automated-backup-locations=us-central1-b,us-east1-c + + To empty the automated backup locations list, run: + + $ gcloud alpha bigtable instances tables update my-table \ + --instance=my-instance --clear-automated-backup-locations POSITIONAL ARGUMENTS Table resource - Cloud Bigtable table to update. The arguments in this @@ -109,19 +123,35 @@ FLAGS At most one of these can be specified: + Group for automated backup policy parameters. + --automated-backup-retention-period=AUTOMATED_BACKUP_RETENTION_PERIOD The retention period of automated backup in the format of 30d for 30 days. Min retention period is 3d and max is 90d. Setting this flag will enable automated backup for the table. - --disable-automated-backup - Once set, disables automated backup policy for the table. + At most one of these can be specified: - --enable-automated-backup - Once set, enables the default automated backup policy - (retention_period=7d, frequency=1d) for the table. Note: If a table - has automated backup enabled, this flag resets it to the default - policy. + --automated-backup-locations=[LOCATION,...] + List of Cloud Bigtable zones where automated backups are allowed to + be created. If empty, automated backups will be created in all + zones of the instance. Locations are in the format + projects/{project}/locations/{zone}. Setting this flag will enable + automated backup for the table. + + --clear-automated-backup-locations + Empty the automated backup locations list if populated. + + At most one of these can be specified: + + --disable-automated-backup + Once set, disables automated backup policy for the table. + + --enable-automated-backup + Once set, enables the default automated backup policy + (retention_period=7d, frequency=1d) for the table. Note: If a table + has automated backup enabled, this flag resets it to the default + policy. At most one of these can be specified: diff --git a/gcloud/alpha/bigtable/instances/update b/gcloud/alpha/bigtable/instances/update index 1ed7a4be2..cbc38e376 100644 --- a/gcloud/alpha/bigtable/instances/update +++ b/gcloud/alpha/bigtable/instances/update @@ -4,7 +4,8 @@ NAME SYNOPSIS gcloud alpha bigtable instances update INSTANCE - [--display-name=DISPLAY_NAME] [GCLOUD_WIDE_FLAG ...] + [--display-name=DISPLAY_NAME] [--edition=EDITION] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Modify an existing Bigtable instance. @@ -15,6 +16,11 @@ EXAMPLES $ gcloud alpha bigtable instances update my-instance-id \ --display-name="Updated Instance Name" + To update the edition for an instance to ENTERPRISE_PLUS, run: + + $ gcloud alpha bigtable instances update my-instance-id \ + --edition=ENTERPRISE_PLUS + POSITIONAL ARGUMENTS Instance resource - The instance to update. This represents a Cloud resource. (NOTE) Some attributes are not given arguments in this group but @@ -38,6 +44,10 @@ FLAGS --display-name=DISPLAY_NAME Friendly name of the instance. + --edition=EDITION + The edition of the instance. EDITION must be one of: ENTERPRISE, + ENTERPRISE_PLUS. + 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/memory-layers/describe b/gcloud/alpha/bigtable/memory-layers/describe new file mode 100644 index 000000000..9896a1499 --- /dev/null +++ b/gcloud/alpha/bigtable/memory-layers/describe @@ -0,0 +1,64 @@ +NAME + gcloud alpha bigtable memory-layers describe - describe a Bigtable memory + layer + +SYNOPSIS + gcloud alpha bigtable memory-layers describe + (CLUSTER : --instance=INSTANCE) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Describe a Bigtable memory layer. + +EXAMPLES + To view a memory layer's description, run: + + $ gcloud alpha bigtable memory-layers describe my-cluster-id \ + --instance=my-instance-id + +POSITIONAL ARGUMENTS + Cluster resource - The cluster of the memory layer 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 cluster on the command line with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + CLUSTER + ID of the cluster or fully qualified identifier for the cluster. + + To set the cluster attribute: + ▸ provide the argument cluster on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --instance=INSTANCE + Bigtable instance for the cluster. + + To set the instance attribute: + ▸ provide the argument cluster 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. This variant is also available: + + $ gcloud beta bigtable memory-layers describe + diff --git a/gcloud/alpha/lifesciences/pipelines/help b/gcloud/alpha/bigtable/memory-layers/help similarity index 57% rename from gcloud/alpha/lifesciences/pipelines/help rename to gcloud/alpha/bigtable/memory-layers/help index c72a541e3..2c7d9b7ae 100644 --- a/gcloud/alpha/lifesciences/pipelines/help +++ b/gcloud/alpha/bigtable/memory-layers/help @@ -1,11 +1,11 @@ NAME - gcloud alpha lifesciences pipelines - commands for Life Sciences pipelines + gcloud alpha bigtable memory-layers - manage Cloud Bigtable memory layers SYNOPSIS - gcloud alpha lifesciences pipelines COMMAND [GCLOUD_WIDE_FLAG ...] + gcloud alpha bigtable memory-layers COMMAND [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) Command to run pipelines. + (ALPHA) Manage Cloud Bigtable memory layers. GCLOUD WIDE FLAGS These flags are available to all commands: --help. @@ -15,8 +15,11 @@ GCLOUD WIDE FLAGS COMMANDS COMMAND is one of the following: - run - (ALPHA) Defines and runs a pipeline. + describe + (ALPHA) Describe a Bigtable memory layer. + + update + (ALPHA) Update a Bigtable memory layer. NOTES This command is currently in alpha and might change without notice. If this @@ -24,5 +27,5 @@ NOTES project, you might be trying to access an API with an invitation-only early access allowlist. This variant is also available: - $ gcloud beta lifesciences pipelines + $ gcloud beta bigtable memory-layers diff --git a/gcloud/alpha/bigtable/memory-layers/update b/gcloud/alpha/bigtable/memory-layers/update new file mode 100644 index 000000000..275288049 --- /dev/null +++ b/gcloud/alpha/bigtable/memory-layers/update @@ -0,0 +1,82 @@ +NAME + gcloud alpha bigtable memory-layers update - update a Bigtable memory layer + +SYNOPSIS + gcloud alpha bigtable memory-layers update (CLUSTER : --instance=INSTANCE) + (--disable | --enable) [--async] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Update a Bigtable memory layer. + +EXAMPLES + To enable a memory layer, run: + + $ gcloud alpha bigtable memory-layers update my-cluster-id \ + --instance=my-instance-id --enable + + To disable a memory layer, run: + + $ gcloud alpha bigtable memory-layers update my-cluster-id \ + --instance=my-instance-id --disable + +POSITIONAL ARGUMENTS + Cluster resource - The cluster of the memory layer 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 cluster on the command line with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + CLUSTER + ID of the cluster or fully qualified identifier for the cluster. + + To set the cluster attribute: + ▸ provide the argument cluster on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --instance=INSTANCE + Bigtable instance for the cluster. + + To set the instance attribute: + ▸ provide the argument cluster on the command line with a fully + specified name; + ▸ provide the argument --instance on the command line. + +REQUIRED FLAGS + Exactly one of these must be specified: + + --disable + Disable the memory layer for the cluster. + + --enable + Enable the memory layer for the cluster. + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud beta bigtable memory-layers update + diff --git a/gcloud/alpha/bigtable/tables/create b/gcloud/alpha/bigtable/tables/create index fcec2315e..0c1dd0a05 100644 --- a/gcloud/alpha/bigtable/tables/create +++ b/gcloud/alpha/bigtable/tables/create @@ -9,8 +9,10 @@ SYNOPSIS [--row-key-schema-definition-file=ROW_KEY_SCHEMA_DEFINITION_FILE] [--row-key-schema-pre-encoded-bytes] [--splits=[SPLITS,...]] [--tiered-storage-infrequent-access-older-than=TIERED_STORAGE_INFREQUENT_ACCESS_OLDER_THAN] - [--automated-backup-retention-period=AUTOMATED_BACKUP_RETENTION_PERIOD - | --enable-automated-backup] [GCLOUD_WIDE_FLAG ...] + [--enable-automated-backup + | --automated-backup-locations=[LOCATION,...] + --automated-backup-retention-period=AUTOMATED_BACKUP_RETENTION_PERIOD] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Create a new Cloud Bigtable table. @@ -79,6 +81,13 @@ EXAMPLES --instance=my-instance --column-families="my-family" \ --automated-backup-retention_period=30d + To create a table my-table with a custom automated backup policy configured + to take backups in only us-central1-b and us-east1-c, run: + + $ gcloud alpha bigtable tables create my-table \ + --instance=my-instance \ + --automated-backup-locations=us-central1-b,us-east1-c + POSITIONAL ARGUMENTS Table resource - Cloud Bigtable table to create. The arguments in this group can be used to specify the attributes of this resource. (NOTE) Some @@ -167,15 +176,28 @@ OPTIONAL FLAGS At most one of these can be specified: - --automated-backup-retention-period=AUTOMATED_BACKUP_RETENTION_PERIOD - The retention period of automated backup in the format of 30d for 30 - days. Min retention period is 3d and max is 90d. Setting this flag - will enable automated backup for the table. - --enable-automated-backup Once set, enables the default automated backup policy (retention_period=7d, frequency=1d) for the table. + Or at least one of these can be specified: + + Group for automated backup policy parameters. + + --automated-backup-locations=[LOCATION,...] + List of Cloud Bigtable zones where automated backups are allowed to + be created. If empty, automated backups will be created in all + zones of the instance. Locations are in the format + projects/{project}/locations/{zone}. Setting this flag will enable + automated backup for the table. If automated backup retention + period is not specified, it defaults to 7 days. + + --automated-backup-retention-period=AUTOMATED_BACKUP_RETENTION_PERIOD + The retention period of automated backup in the format of 30d for + 30 days. Min retention period is 3d and max is 90d. Setting this + flag will enable automated backup for the table. If automated + backup retention period is not specified, it defaults to 7 days. + 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/tables/update b/gcloud/alpha/bigtable/tables/update index 241a6e7d9..2237e2ca1 100644 --- a/gcloud/alpha/bigtable/tables/update +++ b/gcloud/alpha/bigtable/tables/update @@ -6,7 +6,9 @@ SYNOPSIS gcloud alpha bigtable tables update (TABLE : --instance=INSTANCE) [--async] [--deletion-protection] [--row-key-schema-pre-encoded-bytes] [--automated-backup-retention-period=AUTOMATED_BACKUP_RETENTION_PERIOD - | --disable-automated-backup | --enable-automated-backup] + --automated-backup-locations=[LOCATION,...] + | --clear-automated-backup-locations | --disable-automated-backup + | --enable-automated-backup] [--change-stream-retention-period=CHANGE_STREAM_RETENTION_PERIOD | --clear-change-stream-retention-period] [--clear-row-key-schema @@ -56,7 +58,19 @@ EXAMPLES retain backups for 30 days, run: $ gcloud alpha bigtable tables update my-table \ - --instance=my-instance --automated-backup-retention_period=30d + --instance=my-instance --automated-backup-retention-period=30d + + To enable or update a custom automated backup policy and configure it to + take backups in only us-central1-b and us-east1-c, run: + + $ gcloud alpha bigtable tables update my-table \ + --instance=my-instance \ + --automated-backup-locations=us-central1-b,us-east1-c + + To empty the automated backup locations list, run: + + $ gcloud alpha bigtable tables update my-table \ + --instance=my-instance --clear-automated-backup-locations POSITIONAL ARGUMENTS Table resource - Cloud Bigtable table to update. The arguments in this @@ -109,19 +123,35 @@ FLAGS At most one of these can be specified: + Group for automated backup policy parameters. + --automated-backup-retention-period=AUTOMATED_BACKUP_RETENTION_PERIOD The retention period of automated backup in the format of 30d for 30 days. Min retention period is 3d and max is 90d. Setting this flag will enable automated backup for the table. - --disable-automated-backup - Once set, disables automated backup policy for the table. + At most one of these can be specified: - --enable-automated-backup - Once set, enables the default automated backup policy - (retention_period=7d, frequency=1d) for the table. Note: If a table - has automated backup enabled, this flag resets it to the default - policy. + --automated-backup-locations=[LOCATION,...] + List of Cloud Bigtable zones where automated backups are allowed to + be created. If empty, automated backups will be created in all + zones of the instance. Locations are in the format + projects/{project}/locations/{zone}. Setting this flag will enable + automated backup for the table. + + --clear-automated-backup-locations + Empty the automated backup locations list if populated. + + At most one of these can be specified: + + --disable-automated-backup + Once set, disables automated backup policy for the table. + + --enable-automated-backup + Once set, enables the default automated backup policy + (retention_period=7d, frequency=1d) for the table. Note: If a table + has automated backup enabled, this flag resets it to the default + policy. At most one of these can be specified: diff --git a/gcloud/alpha/bq/translation/translate b/gcloud/alpha/bq/translation/translate index d107f17c6..d3b9f0b1c 100644 --- a/gcloud/alpha/bq/translation/translate +++ b/gcloud/alpha/bq/translation/translate @@ -4,8 +4,11 @@ NAME SYNOPSIS gcloud alpha bq translation translate --location=LOCATION - --source-dialect=SOURCE_DIALECT [--input-file=INPUT_FILE] + --source-dialect=SOURCE_DIALECT --target-dialect=TARGET_DIALECT + [--explanation-output-file=EXPLANATION_OUTPUT_FILE] + [--input-file=INPUT_FILE] [--metadata-gcs-uri=METADATA_GCS_URI] [--output-file=OUTPUT_FILE] + [--translation-config-files=[CONFIG_FILE,...]] [--translation-log-file=TRANSLATION_LOG_FILE] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -33,17 +36,34 @@ REQUIRED FLAGS Google Cloud Storage location to use for the translation. --source-dialect=SOURCE_DIALECT - Source dialect of the query. + Source dialect of the query. See supported dialects in + https://docs.cloud.google.com/bigquery/docs/batch-sql-translator#supported_sql_dialects + + --target-dialect=TARGET_DIALECT + Target dialect of the query. See supported dialects in + https://docs.cloud.google.com/bigquery/docs/batch-sql-translator#supported_sql_dialects OPTIONAL FLAGS + --explanation-output-file=EXPLANATION_OUTPUT_FILE + File to which to write the translation explanation. + --input-file=INPUT_FILE File from which to read the SQL query to translate. Can be piped through stdin as well. + --metadata-gcs-uri=METADATA_GCS_URI + Cloud Storage URI for the metadata zip file. + --output-file=OUTPUT_FILE File to which to write the translated SQL. Writes to stdout if not provided or if set to ``-''. + --translation-config-files=[CONFIG_FILE,...] + A comma-separated list of paths to YAML configuration files. File names + must end with .config.yaml. See + https://docs.cloud.google.com/bigquery/docs/config-yaml-translation for + more details. + --translation-log-file=TRANSLATION_LOG_FILE File to which to write the translation logs. diff --git a/gcloud/alpha/certificate-manager/certificates/create b/gcloud/alpha/certificate-manager/certificates/create index 6610d9693..187bbfda3 100644 --- a/gcloud/alpha/certificate-manager/certificates/create +++ b/gcloud/alpha/certificate-manager/certificates/create @@ -181,7 +181,8 @@ GCLOUD WIDE FLAGS API REFERENCE This command uses the certificatemanager/v1 API. The full documentation for - this API can be found at: https://cloud.google.com/certificate-manager + this API can be found at: + https://docs.cloud.google.com/certificate-manager/docs/overview NOTES This command is currently in alpha and might change without notice. If this diff --git a/gcloud/alpha/certificate-manager/certificates/describe b/gcloud/alpha/certificate-manager/certificates/describe index edea55675..0ec857569 100644 --- a/gcloud/alpha/certificate-manager/certificates/describe +++ b/gcloud/alpha/certificate-manager/certificates/describe @@ -58,7 +58,8 @@ GCLOUD WIDE FLAGS API REFERENCE This command uses the certificatemanager/v1 API. The full documentation for - this API can be found at: https://cloud.google.com/certificate-manager + this API can be found at: + https://docs.cloud.google.com/certificate-manager/docs/overview NOTES This command is currently in alpha and might change without notice. If this diff --git a/gcloud/alpha/certificate-manager/dns-authorizations/create b/gcloud/alpha/certificate-manager/dns-authorizations/create index c8801d4c4..8af5e31fd 100644 --- a/gcloud/alpha/certificate-manager/dns-authorizations/create +++ b/gcloud/alpha/certificate-manager/dns-authorizations/create @@ -84,7 +84,8 @@ GCLOUD WIDE FLAGS API REFERENCE This command uses the certificatemanager/v1 API. The full documentation for - this API can be found at: https://cloud.google.com/certificate-manager + this API can be found at: + https://docs.cloud.google.com/certificate-manager/docs/overview NOTES This command is currently in alpha and might change without notice. If this diff --git a/gcloud/alpha/certificate-manager/dns-authorizations/delete b/gcloud/alpha/certificate-manager/dns-authorizations/delete index 227570f43..1cc8e82ea 100644 --- a/gcloud/alpha/certificate-manager/dns-authorizations/delete +++ b/gcloud/alpha/certificate-manager/dns-authorizations/delete @@ -64,7 +64,8 @@ GCLOUD WIDE FLAGS API REFERENCE This command uses the certificatemanager/v1 API. The full documentation for - this API can be found at: https://cloud.google.com/certificate-manager + this API can be found at: + https://docs.cloud.google.com/certificate-manager/docs/overview NOTES This command is currently in alpha and might change without notice. If this diff --git a/gcloud/alpha/certificate-manager/dns-authorizations/describe b/gcloud/alpha/certificate-manager/dns-authorizations/describe index b609fb425..6831d4dae 100644 --- a/gcloud/alpha/certificate-manager/dns-authorizations/describe +++ b/gcloud/alpha/certificate-manager/dns-authorizations/describe @@ -58,7 +58,8 @@ GCLOUD WIDE FLAGS API REFERENCE This command uses the certificatemanager/v1 API. The full documentation for - this API can be found at: https://cloud.google.com/certificate-manager + this API can be found at: + https://docs.cloud.google.com/certificate-manager/docs/overview NOTES This command is currently in alpha and might change without notice. If this diff --git a/gcloud/alpha/certificate-manager/dns-authorizations/list b/gcloud/alpha/certificate-manager/dns-authorizations/list index 5f0d6e61a..e987e9823 100644 --- a/gcloud/alpha/certificate-manager/dns-authorizations/list +++ b/gcloud/alpha/certificate-manager/dns-authorizations/list @@ -78,7 +78,8 @@ GCLOUD WIDE FLAGS API REFERENCE This command uses the certificatemanager/v1 API. The full documentation for - this API can be found at: https://cloud.google.com/certificate-manager + this API can be found at: + https://docs.cloud.google.com/certificate-manager/docs/overview NOTES This command is currently in alpha and might change without notice. If this diff --git a/gcloud/alpha/certificate-manager/dns-authorizations/update b/gcloud/alpha/certificate-manager/dns-authorizations/update index 8bb10136f..2eb02a2c0 100644 --- a/gcloud/alpha/certificate-manager/dns-authorizations/update +++ b/gcloud/alpha/certificate-manager/dns-authorizations/update @@ -98,7 +98,8 @@ GCLOUD WIDE FLAGS API REFERENCE This command uses the certificatemanager/v1 API. The full documentation for - this API can be found at: https://cloud.google.com/certificate-manager + this API can be found at: + https://docs.cloud.google.com/certificate-manager/docs/overview NOTES This command is currently in alpha and might change without notice. If this diff --git a/gcloud/alpha/certificate-manager/issuance-configs/create b/gcloud/alpha/certificate-manager/issuance-configs/create index ece15fd5e..5b84fe817 100644 --- a/gcloud/alpha/certificate-manager/issuance-configs/create +++ b/gcloud/alpha/certificate-manager/issuance-configs/create @@ -100,7 +100,8 @@ GCLOUD WIDE FLAGS API REFERENCE This command uses the certificatemanager/v1 API. The full documentation for - this API can be found at: https://cloud.google.com/certificate-manager + this API can be found at: + https://docs.cloud.google.com/certificate-manager/docs/overview NOTES This command is currently in alpha and might change without notice. If this diff --git a/gcloud/alpha/certificate-manager/issuance-configs/delete b/gcloud/alpha/certificate-manager/issuance-configs/delete index 18baeb94e..c6c315d78 100644 --- a/gcloud/alpha/certificate-manager/issuance-configs/delete +++ b/gcloud/alpha/certificate-manager/issuance-configs/delete @@ -64,7 +64,8 @@ GCLOUD WIDE FLAGS API REFERENCE This command uses the certificatemanager/v1 API. The full documentation for - this API can be found at: https://cloud.google.com/certificate-manager + this API can be found at: + https://docs.cloud.google.com/certificate-manager/docs/overview NOTES This command is currently in alpha and might change without notice. If this diff --git a/gcloud/alpha/certificate-manager/issuance-configs/describe b/gcloud/alpha/certificate-manager/issuance-configs/describe index 2a44e3fa6..c773bf3fb 100644 --- a/gcloud/alpha/certificate-manager/issuance-configs/describe +++ b/gcloud/alpha/certificate-manager/issuance-configs/describe @@ -59,7 +59,8 @@ GCLOUD WIDE FLAGS API REFERENCE This command uses the certificatemanager/v1 API. The full documentation for - this API can be found at: https://cloud.google.com/certificate-manager + this API can be found at: + https://docs.cloud.google.com/certificate-manager/docs/overview NOTES This command is currently in alpha and might change without notice. If this diff --git a/gcloud/alpha/certificate-manager/issuance-configs/list b/gcloud/alpha/certificate-manager/issuance-configs/list index 17be4fe49..582a94930 100644 --- a/gcloud/alpha/certificate-manager/issuance-configs/list +++ b/gcloud/alpha/certificate-manager/issuance-configs/list @@ -78,7 +78,8 @@ GCLOUD WIDE FLAGS API REFERENCE This command uses the certificatemanager/v1 API. The full documentation for - this API can be found at: https://cloud.google.com/certificate-manager + this API can be found at: + https://docs.cloud.google.com/certificate-manager/docs/overview NOTES This command is currently in alpha and might change without notice. If this diff --git a/gcloud/alpha/certificate-manager/issuance-configs/update b/gcloud/alpha/certificate-manager/issuance-configs/update index 7ddc4aff9..2bc30fb33 100644 --- a/gcloud/alpha/certificate-manager/issuance-configs/update +++ b/gcloud/alpha/certificate-manager/issuance-configs/update @@ -101,7 +101,8 @@ GCLOUD WIDE FLAGS API REFERENCE This command uses the certificatemanager/v1 API. The full documentation for - this API can be found at: https://cloud.google.com/certificate-manager + this API can be found at: + https://docs.cloud.google.com/certificate-manager/docs/overview NOTES This command is currently in alpha and might change without notice. If this diff --git a/gcloud/alpha/certificate-manager/operations/describe b/gcloud/alpha/certificate-manager/operations/describe index 2c5254972..b33f180b4 100644 --- a/gcloud/alpha/certificate-manager/operations/describe +++ b/gcloud/alpha/certificate-manager/operations/describe @@ -57,7 +57,8 @@ GCLOUD WIDE FLAGS API REFERENCE This command uses the certificatemanager/v1 API. The full documentation for - this API can be found at: https://cloud.google.com/certificate-manager + this API can be found at: + https://docs.cloud.google.com/certificate-manager/docs/overview NOTES This command is currently in alpha and might change without notice. If this diff --git a/gcloud/alpha/certificate-manager/operations/list b/gcloud/alpha/certificate-manager/operations/list index 9a9319763..47ace0d6c 100644 --- a/gcloud/alpha/certificate-manager/operations/list +++ b/gcloud/alpha/certificate-manager/operations/list @@ -76,7 +76,8 @@ GCLOUD WIDE FLAGS API REFERENCE This command uses the certificatemanager/v1 API. The full documentation for - this API can be found at: https://cloud.google.com/certificate-manager + this API can be found at: + https://docs.cloud.google.com/certificate-manager/docs/overview NOTES This command is currently in alpha and might change without notice. If this diff --git a/gcloud/alpha/certificate-manager/trust-configs/create b/gcloud/alpha/certificate-manager/trust-configs/create index 003194dc0..a36b09645 100644 --- a/gcloud/alpha/certificate-manager/trust-configs/create +++ b/gcloud/alpha/certificate-manager/trust-configs/create @@ -109,7 +109,8 @@ GCLOUD WIDE FLAGS API REFERENCE This command uses the certificatemanager/v1 API. The full documentation for - this API can be found at: https://cloud.google.com/certificate-manager + this API can be found at: + https://docs.cloud.google.com/certificate-manager/docs/overview NOTES This command is currently in alpha and might change without notice. If this diff --git a/gcloud/alpha/certificate-manager/trust-configs/delete b/gcloud/alpha/certificate-manager/trust-configs/delete index 8fdaa2874..305188fff 100644 --- a/gcloud/alpha/certificate-manager/trust-configs/delete +++ b/gcloud/alpha/certificate-manager/trust-configs/delete @@ -67,7 +67,8 @@ GCLOUD WIDE FLAGS API REFERENCE This command uses the certificatemanager/v1 API. The full documentation for - this API can be found at: https://cloud.google.com/certificate-manager + this API can be found at: + https://docs.cloud.google.com/certificate-manager/docs/overview NOTES This command is currently in alpha and might change without notice. If this diff --git a/gcloud/alpha/certificate-manager/trust-configs/describe b/gcloud/alpha/certificate-manager/trust-configs/describe index 46615d165..27a4deb9a 100644 --- a/gcloud/alpha/certificate-manager/trust-configs/describe +++ b/gcloud/alpha/certificate-manager/trust-configs/describe @@ -58,7 +58,8 @@ GCLOUD WIDE FLAGS API REFERENCE This command uses the certificatemanager/v1 API. The full documentation for - this API can be found at: https://cloud.google.com/certificate-manager + this API can be found at: + https://docs.cloud.google.com/certificate-manager/docs/overview NOTES This command is currently in alpha and might change without notice. If this diff --git a/gcloud/alpha/certificate-manager/trust-configs/export b/gcloud/alpha/certificate-manager/trust-configs/export index be1a8b311..e13a02894 100644 --- a/gcloud/alpha/certificate-manager/trust-configs/export +++ b/gcloud/alpha/certificate-manager/trust-configs/export @@ -67,7 +67,8 @@ GCLOUD WIDE FLAGS API REFERENCE This command uses the certificatemanager/v1 API. The full documentation for - this API can be found at: https://cloud.google.com/certificate-manager + this API can be found at: + https://docs.cloud.google.com/certificate-manager/docs/overview NOTES This command is currently in alpha and might change without notice. If this diff --git a/gcloud/alpha/certificate-manager/trust-configs/import b/gcloud/alpha/certificate-manager/trust-configs/import index 1f8fc1b43..73823d324 100644 --- a/gcloud/alpha/certificate-manager/trust-configs/import +++ b/gcloud/alpha/certificate-manager/trust-configs/import @@ -80,7 +80,8 @@ GCLOUD WIDE FLAGS API REFERENCE This command uses the certificatemanager/v1 API. The full documentation for - this API can be found at: https://cloud.google.com/certificate-manager + this API can be found at: + https://docs.cloud.google.com/certificate-manager/docs/overview NOTES This command is currently in alpha and might change without notice. If this diff --git a/gcloud/alpha/certificate-manager/trust-configs/list b/gcloud/alpha/certificate-manager/trust-configs/list index 14fdfe861..a820d1f0a 100644 --- a/gcloud/alpha/certificate-manager/trust-configs/list +++ b/gcloud/alpha/certificate-manager/trust-configs/list @@ -77,7 +77,8 @@ GCLOUD WIDE FLAGS API REFERENCE This command uses the certificatemanager/v1 API. The full documentation for - this API can be found at: https://cloud.google.com/certificate-manager + this API can be found at: + https://docs.cloud.google.com/certificate-manager/docs/overview NOTES This command is currently in alpha and might change without notice. If this diff --git a/gcloud/alpha/certificate-manager/trust-configs/update b/gcloud/alpha/certificate-manager/trust-configs/update index 7cd107292..b3d960328 100644 --- a/gcloud/alpha/certificate-manager/trust-configs/update +++ b/gcloud/alpha/certificate-manager/trust-configs/update @@ -149,7 +149,8 @@ GCLOUD WIDE FLAGS API REFERENCE This command uses the certificatemanager/v1 API. The full documentation for - this API can be found at: https://cloud.google.com/certificate-manager + this API can be found at: + https://docs.cloud.google.com/certificate-manager/docs/overview NOTES This command is currently in alpha and might change without notice. If this diff --git a/gcloud/alpha/cluster-director/clusters/create b/gcloud/alpha/cluster-director/clusters/create index f33019a8d..111110397 100644 --- a/gcloud/alpha/cluster-director/clusters/create +++ b/gcloud/alpha/cluster-director/clusters/create @@ -802,7 +802,7 @@ REQUIRED FLAGS in your project in the format of bucket-1. For e.g. --create-buckets - id=my-bucket,name=bucket-1,storageClass=STANDARD,terminalStorageClass=TERMINAL_STORAGE_CLASS_NEARLINE,enableHNS=true + id=my-bucket,name=bucket-1,storageClass=STANDARD,terminalStorageClass=NEARLINE,enableHNS=true Supported storageClass values: ▫ STANDARD @@ -811,8 +811,8 @@ REQUIRED FLAGS ▫ ARCHIVE Supported terminalStorageClass values: - ▫ TERMINAL_STORAGE_CLASS_NEARLINE - ▫ TERMINAL_STORAGE_CLASS_ARCHIVE + ▫ NEARLINE + ▫ ARCHIVE Defaults: ▫ storageClass: STANDARD diff --git a/gcloud/alpha/cluster-director/clusters/update b/gcloud/alpha/cluster-director/clusters/update index b1ff4c224..aea5a2ef2 100644 --- a/gcloud/alpha/cluster-director/clusters/update +++ b/gcloud/alpha/cluster-director/clusters/update @@ -493,7 +493,7 @@ REQUIRED FLAGS your project in the format of bucket-1. For e.g. --add-new-storage-buckets - id=my-bucket,name=bucket-1,storageClass=STANDARD,terminalStorageClass=TERMINAL_STORAGE_CLASS_NEARLINE,enableHNS=true + id=my-bucket,name=bucket-1,storageClass=STANDARD,terminalStorageClass=NEARLINE,enableHNS=true Supported storageClass values: ▸ STANDARD @@ -502,8 +502,8 @@ REQUIRED FLAGS ▸ ARCHIVE Supported terminalStorageClass values: - ▸ TERMINAL_STORAGE_CLASS_NEARLINE - ▸ TERMINAL_STORAGE_CLASS_ARCHIVE + ▸ NEARLINE + ▸ ARCHIVE Defaults: ▸ storageClass: STANDARD diff --git a/gcloud/alpha/composer/environments/create b/gcloud/alpha/composer/environments/create index 982e21c7b..edf59d029 100644 --- a/gcloud/alpha/composer/environments/create +++ b/gcloud/alpha/composer/environments/create @@ -6,7 +6,8 @@ SYNOPSIS gcloud alpha composer environments create (ENVIRONMENT : --location=LOCATION) [--airflow-configs=[KEY=VALUE,...]] [--airflow-database-retention-days=AIRFLOW_DATABASE_RETENTION_DAYS] - [--async] [--cloud-sql-machine-type=CLOUD_SQL_MACHINE_TYPE] + [--async] [--cloud-run-functions-routing=CLOUD_RUN_FUNCTIONS_ROUTING] + [--cloud-sql-machine-type=CLOUD_SQL_MACHINE_TYPE] [--cloud-sql-preferred-zone=CLOUD_SQL_PREFERRED_ZONE] [--composer-internal-ipv4-cidr-block=COMPOSER_INTERNAL_IPV4_CIDR_BLOCK] [--disable-logs-in-cloud-logging-only] [--disk-size=DISK_SIZE] @@ -133,6 +134,14 @@ FLAGS Return immediately, without waiting for the operation in progress to complete. + Group of arguments for configuring traffic routing in Composer 3 or + greater. + + --cloud-run-functions-routing=CLOUD_RUN_FUNCTIONS_ROUTING + Controls how network traffic to Cloud Run functions is routed. + CLOUD_RUN_FUNCTIONS_ROUTING must be one of: direct, + via-network-attachment. + --cloud-sql-machine-type=CLOUD_SQL_MACHINE_TYPE Cloud SQL machine type used by the Airflow database. The list of available machine types is available here: diff --git a/gcloud/alpha/composer/environments/update b/gcloud/alpha/composer/environments/update index 287700aa9..74949d55e 100644 --- a/gcloud/alpha/composer/environments/update +++ b/gcloud/alpha/composer/environments/update @@ -6,6 +6,7 @@ SYNOPSIS gcloud alpha composer environments update (ENVIRONMENT : --location=LOCATION) (--airflow-database-retention-days=AIRFLOW_DATABASE_RETENTION_DAYS + | --cloud-run-functions-routing=CLOUD_RUN_FUNCTIONS_ROUTING | --cloud-sql-machine-type=CLOUD_SQL_MACHINE_TYPE | --disable-high-resilience | --disable-logs-in-cloud-logging-only | --disable-private-environment | --enable-high-resilience @@ -111,6 +112,16 @@ REQUIRED FLAGS The number of days for the Airflow database retention period. If set to 0, the Airflow database retention mechanism will be disabled. + Or at least one of these can be specified: + + Group of arguments for configuring traffic routing in Composer 3 or + greater. + + --cloud-run-functions-routing=CLOUD_RUN_FUNCTIONS_ROUTING + Controls how network traffic to Cloud Run functions is routed. + CLOUD_RUN_FUNCTIONS_ROUTING must be one of: direct, + via-network-attachment. + --cloud-sql-machine-type=CLOUD_SQL_MACHINE_TYPE Cloud SQL machine type used by the Airflow database. The list of available machine types is available here: diff --git a/gcloud/alpha/compute/addresses/create b/gcloud/alpha/compute/addresses/create index 953fa610f..c39c73cd0 100644 --- a/gcloud/alpha/compute/addresses/create +++ b/gcloud/alpha/compute/addresses/create @@ -123,8 +123,12 @@ FLAGS addresses. --purpose=PURPOSE - The purpose of the address resource. This field is not applicable to - external addresses. PURPOSE must be one of: VPC_PEERING, + The purpose of the address resource. VPC_PEERING, + SHARED_LOADBALANCER_VIP, GCE_ENDPOINT, IPSEC_INTERCONNECT, and + PRIVATE_SERVICE_CONNECT are only applicable to internal addresses. + PASSTHROUGH_LOAD_BALANCER_AVAILABILITY_GROUP0 and + PASSTHROUGH_LOAD_BALANCER_AVAILABILITY_GROUP1 are only applicable to + global external addresses. PURPOSE must be one of: VPC_PEERING, SHARED_LOADBALANCER_VIP, GCE_ENDPOINT, IPSEC_INTERCONNECT, PRIVATE_SERVICE_CONNECT, PASSTHROUGH_LOAD_BALANCER_AVAILABILITY_GROUP0, PASSTHROUGH_LOAD_BALANCER_AVAILABILITY_GROUP1. diff --git a/gcloud/alpha/compute/addresses/help b/gcloud/alpha/compute/addresses/help index 86acb951f..1dae2ba07 100644 --- a/gcloud/alpha/compute/addresses/help +++ b/gcloud/alpha/compute/addresses/help @@ -44,7 +44,7 @@ COMMANDS (ALPHA) Move an address to another project. update - (ALPHA) Update a Compute Engine address. + (ALPHA) Update an address's labels. NOTES This command is currently in alpha and might change without notice. If this diff --git a/gcloud/alpha/compute/addresses/update b/gcloud/alpha/compute/addresses/update index 5c52244e4..9683a4972 100644 --- a/gcloud/alpha/compute/addresses/update +++ b/gcloud/alpha/compute/addresses/update @@ -1,5 +1,5 @@ NAME - gcloud alpha compute addresses update - update a Compute Engine address + gcloud alpha compute addresses update - update an address's labels SYNOPSIS gcloud alpha compute addresses update NAME @@ -83,7 +83,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud compute addresses update $ gcloud beta compute addresses update diff --git a/gcloud/alpha/compute/advice/capacity b/gcloud/alpha/compute/advice/capacity index 04fe721d1..9d32dd184 100644 --- a/gcloud/alpha/compute/advice/capacity +++ b/gcloud/alpha/compute/advice/capacity @@ -8,6 +8,7 @@ SYNOPSIS --target-distribution-shape=TARGET_DISTRIBUTION_SHAPE (--instance-selection=INSTANCE_SELECTION --instance-selection-machine-types=[MACHINE_TYPE,...]) + [--accelerator-topology=ACCELERATOR_TOPOLOGY] [--max-run-duration=MAX_RUN_DURATION] [--region=REGION] [--zones=[ZONE,...]] [GCLOUD_WIDE_FLAG ...] @@ -47,7 +48,8 @@ EXAMPLES --provisioning-model="FLEX_START" --max-run-duration=1d \ --size=10 \ --instance-selection-machine-types="ct5lp-hightpu-4t" \ - --target-distribution-shape="any-single-zone" + --target-distribution-shape="any-single-zone" \ + --accelerator-topology="2x2" REQUIRED FLAGS --provisioning-model=PROVISIONING_MODEL @@ -72,9 +74,7 @@ REQUIRED FLAGS ANY When you specify ANY for VM instance creation across multiple zones, you specify that you want to create your VM instances in one - or more zones based on resource availability, and to use any - unused, matching reservation in your project. Use ANY for batch - workloads that don't require high availability. + or more zones based on resource availability. ANY_SINGLE_ZONE When you specify ANY_SINGLE_ZONE for VM instance creation, you specify that you want to create all VM instances in a single @@ -84,6 +84,12 @@ REQUIRED FLAGS prevent Compute Engine from creating all your requested VM instances. Use ANY_SINGLE_ZONE when the VM instances in your workloads need to frequently communicate among each other. + BALANCED + Prioritizes provisioning VMs in zones where resources are + available. Compute Engine then distributes VMs as evenly as + possible across zones. If resources are unavailable in one or more + zones, then the actual distribution might be uneven. Use BALANCED + to minimize the impact of zonal failures. Specifies the machine types for which advice is being sought. @@ -98,6 +104,10 @@ REQUIRED FLAGS creating virtual machines. OPTIONAL FLAGS + --accelerator-topology=ACCELERATOR_TOPOLOGY + Topology required to create a partition for VMs that have + interconnected GPUs or TPUs. For example, 2x2 for ct5l-hightpu-4t. + --max-run-duration=MAX_RUN_DURATION Maximum duration for which the requested VMs can run. This flag must be used when the requested provisioning model is FLEX_START. diff --git a/gcloud/alpha/compute/backend-buckets/set-iam-policy b/gcloud/alpha/compute/backend-buckets/set-iam-policy index 9fcdb770d..7c18f9ef4 100644 --- a/gcloud/alpha/compute/backend-buckets/set-iam-policy +++ b/gcloud/alpha/compute/backend-buckets/set-iam-policy @@ -12,7 +12,7 @@ DESCRIPTION EXAMPLES The following command will read an IAM policy defined in a JSON file - 'policy.json' and set it for the regionalbackend bucket my-backend-bucket: + 'policy.json' and set it for the regional backend bucket my-backend-bucket: $ gcloud alpha compute backend-buckets set-iam-policy \ my-backend-bucket policy.json --region=REGION diff --git a/gcloud/alpha/compute/backend-services/add-backend b/gcloud/alpha/compute/backend-services/add-backend index b130b200b..f2ed64f1e 100644 --- a/gcloud/alpha/compute/backend-services/add-backend +++ b/gcloud/alpha/compute/backend-services/add-backend @@ -195,7 +195,7 @@ OPTIONAL FLAGS Spreads load based on custom defined and reported metrics. IN_FLIGHT - Available if the backend service's load balancing scheme is + Available if the backend service's load balancing scheme is INTERNAL_MANAGED, INTERNAL_SELF_MANAGED, or EXTERNAL_MANAGED. Available if the backend service's protocol is one of HTTP, HTTPS, or HTTP/2. @@ -209,8 +209,9 @@ OPTIONAL FLAGS RATE Available if the backend service's load balancing scheme is - INTERNAL_MANAGED, INTERNAL_SELF_MANAGED, or EXTERNAL. Available if - the backend service's protocol is one of HTTP, HTTPS, or HTTP/2. + INTERNAL_MANAGED, INTERNAL_SELF_MANAGED, EXTERNAL or + EXTERNAL_PASSTHROUGH. Available if the backend service's protocol + is one of HTTP, HTTPS, or HTTP/2. Spreads load based on how many HTTP requests per second (RPS) the backend can handle. @@ -220,8 +221,9 @@ OPTIONAL FLAGS UTILIZATION Available if the backend service's load balancing scheme is - INTERNAL_MANAGED, INTERNAL_SELF_MANAGED, or EXTERNAL. Available - only for managed or unmanaged instance group backends. + INTERNAL_MANAGED, INTERNAL_SELF_MANAGED, EXTERNAL or + EXTERNAL_PASSTHROUGH. Available only for managed or unmanaged + instance group backends. Spreads load based on the backend utilization of instances in a backend instance group. diff --git a/gcloud/alpha/compute/backend-services/update b/gcloud/alpha/compute/backend-services/update index c43f23dae..05340a0e7 100644 --- a/gcloud/alpha/compute/backend-services/update +++ b/gcloud/alpha/compute/backend-services/update @@ -321,7 +321,16 @@ FLAGS IPV6_ONLY. --load-balancing-scheme=LOAD_BALANCING_SCHEME - Only for the Global external Application Load Balancer migration. + Specifies the load balancer type. Choose EXTERNAL for the classic + Application Load Balancers. Choose EXTERNAL_MANAGED for the Envoy-based + global external Application Load Balancers For more information, refer + to this guide: + https://cloud.google.com/load-balancing/docs/choosing-load-balancer. + + This field should only be used for migration from the Classic + Application Load Balancer to the global external Application Load + Balancer. The --load-balancing-scheme is immutable for all other use + cases. The value of this field must be EXTERNAL or EXTERNAL_MANAGED. diff --git a/gcloud/alpha/compute/backend-services/update-backend b/gcloud/alpha/compute/backend-services/update-backend index d9cca91e3..34bd5b49e 100644 --- a/gcloud/alpha/compute/backend-services/update-backend +++ b/gcloud/alpha/compute/backend-services/update-backend @@ -166,7 +166,7 @@ OPTIONAL FLAGS Spreads load based on custom defined and reported metrics. IN_FLIGHT - Available if the backend service's load balancing scheme is + Available if the backend service's load balancing scheme is INTERNAL_MANAGED, INTERNAL_SELF_MANAGED, or EXTERNAL_MANAGED. Available if the backend service's protocol is one of HTTP, HTTPS, or HTTP/2. @@ -180,8 +180,9 @@ OPTIONAL FLAGS RATE Available if the backend service's load balancing scheme is - INTERNAL_MANAGED, INTERNAL_SELF_MANAGED, or EXTERNAL. Available if - the backend service's protocol is one of HTTP, HTTPS, or HTTP/2. + INTERNAL_MANAGED, INTERNAL_SELF_MANAGED, EXTERNAL or + EXTERNAL_PASSTHROUGH. Available if the backend service's protocol + is one of HTTP, HTTPS, or HTTP/2. Spreads load based on how many HTTP requests per second (RPS) the backend can handle. @@ -191,8 +192,9 @@ OPTIONAL FLAGS UTILIZATION Available if the backend service's load balancing scheme is - INTERNAL_MANAGED, INTERNAL_SELF_MANAGED, or EXTERNAL. Available - only for managed or unmanaged instance group backends. + INTERNAL_MANAGED, INTERNAL_SELF_MANAGED, EXTERNAL or + EXTERNAL_PASSTHROUGH. Available only for managed or unmanaged + instance group backends. Spreads load based on the backend utilization of instances in a backend instance group. diff --git a/gcloud/alpha/compute/commitments/create b/gcloud/alpha/compute/commitments/create index c39ae03ba..f69a9482a 100644 --- a/gcloud/alpha/compute/commitments/create +++ b/gcloud/alpha/compute/commitments/create @@ -7,6 +7,7 @@ SYNOPSIS --resources-accelerator=[count=COUNT],[type=TYPE]) [--auto-renew] [--custom-end-time=CUSTOM_END_TIME] [--merge-source-commitments=MERGE_SOURCE_COMMITMENTS] [--region=REGION] + [--resource-manager-tags=[KEY=VALUE,...]] [--split-source-commitment=SPLIT_SOURCE_COMMITMENT] [--type=TYPE; default="general-purpose"] [--existing-reservation=[name=NAME],[zone=ZONE] @@ -100,6 +101,9 @@ OPTIONAL FLAGS Alternatively, the region can be stored in the environment variable CLOUDSDK_COMPUTE_REGION. + --resource-manager-tags=[KEY=VALUE,...] + Resource manager tags to be bound to the commitment. + --split-source-commitment=SPLIT_SOURCE_COMMITMENT Creates the new commitment by splitting the specified source commitment and redistributing the specified resources. diff --git a/gcloud/alpha/compute/composite-health-checks/create b/gcloud/alpha/compute/composite-health-checks/create index 7c51b4e0b..7c26f9f81 100644 --- a/gcloud/alpha/compute/composite-health-checks/create +++ b/gcloud/alpha/compute/composite-health-checks/create @@ -90,7 +90,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud compute composite-health-checks create $ gcloud beta compute composite-health-checks create diff --git a/gcloud/alpha/compute/composite-health-checks/delete b/gcloud/alpha/compute/composite-health-checks/delete index af20e6380..6036a3e0e 100644 --- a/gcloud/alpha/compute/composite-health-checks/delete +++ b/gcloud/alpha/compute/composite-health-checks/delete @@ -70,7 +70,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud compute composite-health-checks delete $ gcloud beta compute composite-health-checks delete diff --git a/gcloud/alpha/compute/composite-health-checks/describe b/gcloud/alpha/compute/composite-health-checks/describe index f0f821621..d9325c443 100644 --- a/gcloud/alpha/compute/composite-health-checks/describe +++ b/gcloud/alpha/compute/composite-health-checks/describe @@ -65,7 +65,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud compute composite-health-checks describe $ gcloud beta compute composite-health-checks describe diff --git a/gcloud/alpha/compute/composite-health-checks/get-health b/gcloud/alpha/compute/composite-health-checks/get-health index 1c67259f6..7182cde09 100644 --- a/gcloud/alpha/compute/composite-health-checks/get-health +++ b/gcloud/alpha/compute/composite-health-checks/get-health @@ -36,7 +36,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud compute composite-health-checks get-health $ gcloud beta compute composite-health-checks get-health diff --git a/gcloud/alpha/compute/composite-health-checks/help b/gcloud/alpha/compute/composite-health-checks/help index e28da50be..7d997fbee 100644 --- a/gcloud/alpha/compute/composite-health-checks/help +++ b/gcloud/alpha/compute/composite-health-checks/help @@ -38,7 +38,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud compute composite-health-checks $ gcloud beta compute composite-health-checks diff --git a/gcloud/alpha/compute/composite-health-checks/list b/gcloud/alpha/compute/composite-health-checks/list index 6f6090195..f1cf8bd53 100644 --- a/gcloud/alpha/compute/composite-health-checks/list +++ b/gcloud/alpha/compute/composite-health-checks/list @@ -74,7 +74,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud compute composite-health-checks list $ gcloud beta compute composite-health-checks list diff --git a/gcloud/alpha/compute/composite-health-checks/update b/gcloud/alpha/compute/composite-health-checks/update index ff1eccfc7..70959f41d 100644 --- a/gcloud/alpha/compute/composite-health-checks/update +++ b/gcloud/alpha/compute/composite-health-checks/update @@ -92,7 +92,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud compute composite-health-checks update $ gcloud beta compute composite-health-checks update diff --git a/gcloud/alpha/compute/disks/bulk/create b/gcloud/alpha/compute/disks/bulk/create index a94350e1e..7512ddad4 100644 --- a/gcloud/alpha/compute/disks/bulk/create +++ b/gcloud/alpha/compute/disks/bulk/create @@ -1,6 +1,6 @@ NAME gcloud alpha compute disks bulk create - create multiple Compute Engine - disks + disks or a consistency group of instant snapshots SYNOPSIS gcloud alpha compute disks bulk create (--region=REGION | --zone=ZONE) @@ -13,7 +13,8 @@ SYNOPSIS DESCRIPTION (ALPHA) gcloud alpha compute disks bulk create facilitates the creation of multiple Compute Engine disks with a single command. This includes cloning - a set of Async PD secondary disks with the same consistency group policy. + a set of Async PD secondary disks with the same consistency group policy or + a consistency group of instant snapshots. EXAMPLES To consistently clone secondary disks with the same consistency group @@ -77,7 +78,10 @@ OPTIONAL FLAGS policy is always the same region as the source disks. --source-instant-snapshot-group=SOURCE_INSTANT_SNAPSHOT_GROUP - Source instant snapshot group used to create the disks. + URL of the format + regions//instantSnapshotGroups/ or + zones//instantSnapshotGroups/ of the + source consistency group of instant snapshots used to create the disks. --source-snapshot-group=SOURCE_SNAPSHOT_GROUP Source snapshot group used to create the disks. diff --git a/gcloud/alpha/compute/disks/bulk/help b/gcloud/alpha/compute/disks/bulk/help index c753a22e3..aaedddc2e 100644 --- a/gcloud/alpha/compute/disks/bulk/help +++ b/gcloud/alpha/compute/disks/bulk/help @@ -18,7 +18,8 @@ COMMANDS COMMAND is one of the following: create - (ALPHA) Create multiple Compute Engine disks. + (ALPHA) Create multiple Compute Engine disks or a consistency group of + instant snapshots. NOTES This command is currently in alpha and might change without notice. If this diff --git a/gcloud/alpha/compute/disks/help b/gcloud/alpha/compute/disks/help index 5ba0b3161..71826ff0d 100644 --- a/gcloud/alpha/compute/disks/help +++ b/gcloud/alpha/compute/disks/help @@ -98,7 +98,7 @@ COMMANDS (ALPHA) Update a Compute Engine persistent disk. update-kms-key - (ALPHA) Update the KMS key of a persistent disk. + (ALPHA) Update the KMS key of a Hyperdisk or Persistent Disk. wait-for-replication-catchup (ALPHA) Provides the operation id for the asynchronous replication of a diff --git a/gcloud/alpha/compute/disks/update b/gcloud/alpha/compute/disks/update index 91d8d4d41..59e29361b 100644 --- a/gcloud/alpha/compute/disks/update +++ b/gcloud/alpha/compute/disks/update @@ -17,7 +17,7 @@ SYNOPSIS DESCRIPTION (ALPHA) gcloud alpha compute disks update updates a Compute Engine - persistent disk. + Hyperdisk or Persistent Disk. EXAMPLES To update labels 'k0' and 'k1' and remove label 'k3' of a disk, run: diff --git a/gcloud/alpha/compute/disks/update-kms-key b/gcloud/alpha/compute/disks/update-kms-key index 865706d50..1519f71e5 100644 --- a/gcloud/alpha/compute/disks/update-kms-key +++ b/gcloud/alpha/compute/disks/update-kms-key @@ -1,6 +1,6 @@ NAME gcloud alpha compute disks update-kms-key - update the KMS key of a - persistent disk + Hyperdisk or Persistent Disk SYNOPSIS gcloud alpha compute disks update-kms-key DISK_NAME @@ -9,12 +9,12 @@ SYNOPSIS [--region=REGION | --zone=ZONE] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) * gcloud alpha compute disks update-kms-key * updates the KMS key - of a Compute Engine persistent disk by rotating it to the primary version - of the key or to the primary version of a new KMS key. + (ALPHA) gcloud alpha compute disks update-kms-key updates the KMS key of a + Compute Engine Persistent or Hyperdisk Disk by rotating it to the primary + version of the key or to the primary version of a new KMS key. EXAMPLES - To rotate the KMS key of a disk named example-disk-1 to the primary + To change the KMS key of a disk named example-disk-1 to the primary version, run: $ gcloud alpha compute disks update-kms-key example-disk-1 \ diff --git a/gcloud/alpha/compute/forwarding-rules/create b/gcloud/alpha/compute/forwarding-rules/create index 2d93056aa..1effcc1b2 100644 --- a/gcloud/alpha/compute/forwarding-rules/create +++ b/gcloud/alpha/compute/forwarding-rules/create @@ -16,7 +16,6 @@ SYNOPSIS | --target-vpn-gateway=TARGET_VPN_GATEWAY) [--allow-global-access] [--allow-psc-global-access] [--description=DESCRIPTION] [--disable-automate-dns-zone] [--ip-collection=IP_COLLECTION] - [--ip-collection-region=IP_COLLECTION_REGION] [--ip-protocol=IP_PROTOCOL] [--ip-version=IP_VERSION] [--is-mirroring-collector] [--load-balancing-scheme=LOAD_BALANCING_SCHEME] [--network=NETWORK] @@ -33,6 +32,7 @@ SYNOPSIS [--address-region=ADDRESS_REGION | --global-address] [--backend-service-region=BACKEND_SERVICE_REGION | --global-backend-service] [--global | --region=REGION] + [--global-ip-collection | --ip-collection-region=IP_COLLECTION_REGION] [--global-target-http-proxy | --target-http-proxy-region=TARGET_HTTP_PROXY_REGION] [--global-target-https-proxy @@ -199,11 +199,6 @@ OPTIONAL FLAGS PublicDelegatedPrefix (PDP) must be a sub-prefix in EXTERNAL_IPV6_FORWARDING_RULE_CREATION mode. - --ip-collection-region=IP_COLLECTION_REGION - Region of the public delegated prefix to operate on. If not specified, - the region is set to the region of the forwarding rule. Overrides the - default compute/region property value for this command invocation. - --ip-protocol=IP_PROTOCOL IP protocol that the rule will serve. The default is TCP. @@ -445,6 +440,17 @@ OPTIONAL FLAGS Alternatively, the region can be stored in the environment variable CLOUDSDK_COMPUTE_REGION. + At most one of these can be specified: + + --global-ip-collection + If set, the public delegated prefix is global. + + --ip-collection-region=IP_COLLECTION_REGION + Region of the public delegated prefix to operate on. If not + specified, the region is set to the region of the forwarding rule. + Overrides the default compute/region property value for this command + invocation. + At most one of these can be specified: --global-target-http-proxy diff --git a/gcloud/alpha/compute/future-reservations/create b/gcloud/alpha/compute/future-reservations/create index 7457b84f5..5b7bc7b9a 100644 --- a/gcloud/alpha/compute/future-reservations/create +++ b/gcloud/alpha/compute/future-reservations/create @@ -266,7 +266,7 @@ OPTIONAL FLAGS the reservation_name or a name_prefix. --resource-manager-tags=[KEY=VALUE,...] - Resource manager tags to be bound to the commitment. + Resource manager tags to be bound to the future reservation. --scheduling-type=SCHEDULING_TYPE Maintenance for the reserved capacity. SCHEDULING_TYPE must be one of: diff --git a/gcloud/alpha/compute/global-vm-extension-policies/create b/gcloud/alpha/compute/global-vm-extension-policies/create index 6ec454d60..3ef17fb5f 100644 --- a/gcloud/alpha/compute/global-vm-extension-policies/create +++ b/gcloud/alpha/compute/global-vm-extension-policies/create @@ -139,7 +139,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud compute global-vm-extension-policies create $ gcloud beta compute global-vm-extension-policies create diff --git a/gcloud/alpha/compute/global-vm-extension-policies/delete b/gcloud/alpha/compute/global-vm-extension-policies/delete index 943174823..46a22cef8 100644 --- a/gcloud/alpha/compute/global-vm-extension-policies/delete +++ b/gcloud/alpha/compute/global-vm-extension-policies/delete @@ -53,7 +53,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud compute global-vm-extension-policies delete $ gcloud beta compute global-vm-extension-policies delete diff --git a/gcloud/alpha/compute/global-vm-extension-policies/describe b/gcloud/alpha/compute/global-vm-extension-policies/describe index 56c0df218..164b68a71 100644 --- a/gcloud/alpha/compute/global-vm-extension-policies/describe +++ b/gcloud/alpha/compute/global-vm-extension-policies/describe @@ -31,7 +31,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud compute global-vm-extension-policies describe $ gcloud beta compute global-vm-extension-policies describe diff --git a/gcloud/alpha/compute/global-vm-extension-policies/help b/gcloud/alpha/compute/global-vm-extension-policies/help index 2b19a40bd..64054047e 100644 --- a/gcloud/alpha/compute/global-vm-extension-policies/help +++ b/gcloud/alpha/compute/global-vm-extension-policies/help @@ -42,7 +42,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud compute global-vm-extension-policies $ gcloud beta compute global-vm-extension-policies diff --git a/gcloud/alpha/compute/global-vm-extension-policies/list b/gcloud/alpha/compute/global-vm-extension-policies/list index d75abfeda..f090f5a58 100644 --- a/gcloud/alpha/compute/global-vm-extension-policies/list +++ b/gcloud/alpha/compute/global-vm-extension-policies/list @@ -59,7 +59,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud compute global-vm-extension-policies list $ gcloud beta compute global-vm-extension-policies list diff --git a/gcloud/alpha/compute/global-vm-extension-policies/update b/gcloud/alpha/compute/global-vm-extension-policies/update index 5330337e5..fecbcf7d8 100644 --- a/gcloud/alpha/compute/global-vm-extension-policies/update +++ b/gcloud/alpha/compute/global-vm-extension-policies/update @@ -144,7 +144,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud compute global-vm-extension-policies update $ gcloud beta compute global-vm-extension-policies update diff --git a/gcloud/alpha/compute/health-aggregation-policies/create b/gcloud/alpha/compute/health-aggregation-policies/create index c9e8507fd..5dccaeaee 100644 --- a/gcloud/alpha/compute/health-aggregation-policies/create +++ b/gcloud/alpha/compute/health-aggregation-policies/create @@ -110,7 +110,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud compute health-aggregation-policies create $ gcloud beta compute health-aggregation-policies create diff --git a/gcloud/alpha/compute/health-aggregation-policies/delete b/gcloud/alpha/compute/health-aggregation-policies/delete index 7743e17d5..763ae15e7 100644 --- a/gcloud/alpha/compute/health-aggregation-policies/delete +++ b/gcloud/alpha/compute/health-aggregation-policies/delete @@ -71,7 +71,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud compute health-aggregation-policies delete $ gcloud beta compute health-aggregation-policies delete diff --git a/gcloud/alpha/compute/health-aggregation-policies/describe b/gcloud/alpha/compute/health-aggregation-policies/describe index 9f9f970a0..66c66db45 100644 --- a/gcloud/alpha/compute/health-aggregation-policies/describe +++ b/gcloud/alpha/compute/health-aggregation-policies/describe @@ -66,7 +66,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud compute health-aggregation-policies describe $ gcloud beta compute health-aggregation-policies describe diff --git a/gcloud/alpha/compute/health-aggregation-policies/help b/gcloud/alpha/compute/health-aggregation-policies/help index 473f23231..b7a18214f 100644 --- a/gcloud/alpha/compute/health-aggregation-policies/help +++ b/gcloud/alpha/compute/health-aggregation-policies/help @@ -36,7 +36,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud compute health-aggregation-policies $ gcloud beta compute health-aggregation-policies diff --git a/gcloud/alpha/compute/health-aggregation-policies/list b/gcloud/alpha/compute/health-aggregation-policies/list index f8c65e128..ffc5555a2 100644 --- a/gcloud/alpha/compute/health-aggregation-policies/list +++ b/gcloud/alpha/compute/health-aggregation-policies/list @@ -74,7 +74,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud compute health-aggregation-policies list $ gcloud beta compute health-aggregation-policies list diff --git a/gcloud/alpha/compute/health-aggregation-policies/update b/gcloud/alpha/compute/health-aggregation-policies/update index 468497ea4..2456b742f 100644 --- a/gcloud/alpha/compute/health-aggregation-policies/update +++ b/gcloud/alpha/compute/health-aggregation-policies/update @@ -105,7 +105,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud compute health-aggregation-policies update $ gcloud beta compute health-aggregation-policies update diff --git a/gcloud/alpha/compute/health-sources/create b/gcloud/alpha/compute/health-sources/create index 8b70ea3c0..0fdf895a5 100644 --- a/gcloud/alpha/compute/health-sources/create +++ b/gcloud/alpha/compute/health-sources/create @@ -97,7 +97,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud compute health-sources create $ gcloud beta compute health-sources create diff --git a/gcloud/alpha/compute/health-sources/delete b/gcloud/alpha/compute/health-sources/delete index be4ae97a3..12f0458dc 100644 --- a/gcloud/alpha/compute/health-sources/delete +++ b/gcloud/alpha/compute/health-sources/delete @@ -68,7 +68,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud compute health-sources delete $ gcloud beta compute health-sources delete diff --git a/gcloud/alpha/compute/health-sources/describe b/gcloud/alpha/compute/health-sources/describe index 4ea00b2f8..e44b1168f 100644 --- a/gcloud/alpha/compute/health-sources/describe +++ b/gcloud/alpha/compute/health-sources/describe @@ -64,7 +64,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud compute health-sources describe $ gcloud beta compute health-sources describe diff --git a/gcloud/alpha/compute/health-sources/get-health b/gcloud/alpha/compute/health-sources/get-health index 574b8ad22..e1ef0c5fb 100644 --- a/gcloud/alpha/compute/health-sources/get-health +++ b/gcloud/alpha/compute/health-sources/get-health @@ -36,7 +36,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud compute health-sources get-health $ gcloud beta compute health-sources get-health diff --git a/gcloud/alpha/compute/health-sources/help b/gcloud/alpha/compute/health-sources/help index c05b9c319..1434872e3 100644 --- a/gcloud/alpha/compute/health-sources/help +++ b/gcloud/alpha/compute/health-sources/help @@ -37,7 +37,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud compute health-sources $ gcloud beta compute health-sources diff --git a/gcloud/alpha/compute/health-sources/list b/gcloud/alpha/compute/health-sources/list index 322185127..f266b37f9 100644 --- a/gcloud/alpha/compute/health-sources/list +++ b/gcloud/alpha/compute/health-sources/list @@ -73,7 +73,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud compute health-sources list $ gcloud beta compute health-sources list diff --git a/gcloud/alpha/compute/health-sources/update b/gcloud/alpha/compute/health-sources/update index cacdd83f1..00671efbf 100644 --- a/gcloud/alpha/compute/health-sources/update +++ b/gcloud/alpha/compute/health-sources/update @@ -92,7 +92,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud compute health-sources update $ gcloud beta compute health-sources update diff --git a/gcloud/alpha/compute/instance-templates/create b/gcloud/alpha/compute/instance-templates/create index 76d2a92f3..c766ca72c 100644 --- a/gcloud/alpha/compute/instance-templates/create +++ b/gcloud/alpha/compute/instance-templates/create @@ -471,7 +471,7 @@ FLAGS The workload identity to use for the instance. --[no-]identity-certificate - Enables or disables managed workload identities on a VM. Use + Enables or disables managed workload identity certificates on a VM. Use --identity-certificate to enable and --no-identity-certificate to disable. @@ -1311,6 +1311,8 @@ FLAGS any Consume any available, matching reservation. + any-reservation-then-fail + Must consume from any automatic reservation; fail otherwise. none Do not consume from any reserved capacity. specific diff --git a/gcloud/alpha/compute/instance-templates/create-with-container b/gcloud/alpha/compute/instance-templates/create-with-container index 79097ea5f..73518812a 100644 --- a/gcloud/alpha/compute/instance-templates/create-with-container +++ b/gcloud/alpha/compute/instance-templates/create-with-container @@ -468,7 +468,7 @@ FLAGS The workload identity to use for the instance. --[no-]identity-certificate - Enables or disables managed workload identities on a VM. Use + Enables or disables managed workload identity certificates on a VM. Use --identity-certificate to enable and --no-identity-certificate to disable. @@ -982,6 +982,8 @@ FLAGS any Consume any available, matching reservation. + any-reservation-then-fail + Must consume from any automatic reservation; fail otherwise. none Do not consume from any reserved capacity. specific diff --git a/gcloud/alpha/compute/instances/add-metadata b/gcloud/alpha/compute/instances/add-metadata index f90afaddd..a8c71271b 100644 --- a/gcloud/alpha/compute/instances/add-metadata +++ b/gcloud/alpha/compute/instances/add-metadata @@ -31,10 +31,10 @@ DESCRIPTION If you are using this command to manage SSH keys for your project, please note the risks - (https://cloud.google.com/compute/docs/instances/adding-removing-ssh-keys#risks) + (https://docs.cloud.google.com/compute/docs/instances/access-overview#risks) of manual SSH key management as well as the required format for SSH key metadata, available at - https://cloud.google.com/compute/docs/instances/adding-removing-ssh-keys. + https://docs.cloud.google.com/compute/docs/connect/add-ssh-keys. EXAMPLES To add metadata under key important-data to an instance named diff --git a/gcloud/alpha/compute/instances/bulk/create b/gcloud/alpha/compute/instances/bulk/create index 3b6ddef63..1d4d65973 100644 --- a/gcloud/alpha/compute/instances/bulk/create +++ b/gcloud/alpha/compute/instances/bulk/create @@ -485,7 +485,7 @@ OPTIONAL FLAGS The workload identity to use for the instance. --[no-]identity-certificate - Enables or disables managed workload identities on a VM. Use + Enables or disables managed workload identity certificates on a VM. Use --identity-certificate to enable and --no-identity-certificate to disable. @@ -1154,6 +1154,8 @@ OPTIONAL FLAGS any Consume any available, matching reservation. + any-reservation-then-fail + Must consume from any automatic reservation; fail otherwise. none Do not consume from any reserved capacity. specific diff --git a/gcloud/alpha/compute/instances/create b/gcloud/alpha/compute/instances/create index 008c55841..f8ce5ccae 100644 --- a/gcloud/alpha/compute/instances/create +++ b/gcloud/alpha/compute/instances/create @@ -600,7 +600,7 @@ FLAGS The workload identity to use for the instance. --[no-]identity-certificate - Enables or disables managed workload identities on a VM. Use + Enables or disables managed workload identity certificates on a VM. Use --identity-certificate to enable and --no-identity-certificate to disable. @@ -1623,6 +1623,8 @@ FLAGS any Consume any available, matching reservation. + any-reservation-then-fail + Must consume from any automatic reservation; fail otherwise. none Do not consume from any reserved capacity. specific diff --git a/gcloud/alpha/compute/instances/create-with-container b/gcloud/alpha/compute/instances/create-with-container index a85fc2d9a..da5147ad6 100644 --- a/gcloud/alpha/compute/instances/create-with-container +++ b/gcloud/alpha/compute/instances/create-with-container @@ -526,7 +526,7 @@ FLAGS The workload identity to use for the instance. --[no-]identity-certificate - Enables or disables managed workload identities on a VM. Use + Enables or disables managed workload identity certificates on a VM. Use --identity-certificate to enable and --no-identity-certificate to disable. @@ -1205,6 +1205,8 @@ FLAGS any Consume any available, matching reservation. + any-reservation-then-fail + Must consume from any automatic reservation; fail otherwise. none Do not consume from any reserved capacity. specific diff --git a/gcloud/alpha/compute/instances/update b/gcloud/alpha/compute/instances/update index ee25f7384..7568bdd81 100644 --- a/gcloud/alpha/compute/instances/update +++ b/gcloud/alpha/compute/instances/update @@ -7,7 +7,9 @@ SYNOPSIS [--[no-]deletion-protection] [--[no-]enable-display-device] [--[no-]graceful-shutdown] [--graceful-shutdown-max-duration=GRACEFUL_SHUTDOWN_MAX_DURATION] + [--identity=IDENTITY] [--[no-]identity-certificate] [--min-cpu-platform=PLATFORM] + [--most-disruptive-allowed-action=MOST_DISRUPTIVE_ALLOWED_ACTION] [--partner-metadata=[NAMESPACE/KEY=VALUE,...]] [--partner-metadata-from-file=LOCAL_FILE_PATH] [--[no-]shielded-integrity-monitoring] @@ -69,6 +71,14 @@ FLAGS 20m10s for 20 minutes and 10 seconds. The value must be between 1 second and 1 hour. + --identity=IDENTITY + The workload identity to use for the instance. + + --[no-]identity-certificate + Enables or disables managed workload identity certificates on a VM. Use + --identity-certificate to enable and --no-identity-certificate to + disable. + --min-cpu-platform=PLATFORM When specified, the VM will be scheduled on host with specified CPU architecture or a newer one. To list available CPU platforms in given @@ -84,6 +94,12 @@ FLAGS You can find more information on-line: https://cloud.google.com/compute/docs/instances/specify-min-cpu-platform + --most-disruptive-allowed-action=MOST_DISRUPTIVE_ALLOWED_ACTION + If specified, Compute Engine returns an error if the update requires a + higher action to be applied to the instance. If not specified, the + default will be REFRESH. MOST_DISRUPTIVE_ALLOWED_ACTION must be one of: + NO_EFFECT, REFRESH, RESTART. + --partner-metadata=[NAMESPACE/KEY=VALUE,...] Partner metadata specifying namespace and its entries. The entries can be key-value pairs or in json format. diff --git a/gcloud/alpha/compute/instant-snapshot-groups/create b/gcloud/alpha/compute/instant-snapshot-groups/create index 505b336db..0ec1db0f1 100644 --- a/gcloud/alpha/compute/instant-snapshot-groups/create +++ b/gcloud/alpha/compute/instant-snapshot-groups/create @@ -1,6 +1,6 @@ NAME gcloud alpha compute instant-snapshot-groups create - create a Compute - Engine instant snapshot group + Engine consistency group of instant snapshots SYNOPSIS gcloud alpha compute instant-snapshot-groups create @@ -28,8 +28,10 @@ POSITIONAL ARGUMENTS REQUIRED FLAGS --source-consistency-group=SOURCE_CONSISTENCY_GROUP - URL of the source consistency group resource policy. The resource - policy is always in the same region as the source disks. + Specifies the source consistency group resource policy. The value + should be the relative name of the resource policy, in the format + ``regions/REGION/resourcePolicies/POLICY_NAME``. The resource policy is + always in the same region as the source disks. OPTIONAL FLAGS At most one of these can be specified: @@ -87,7 +89,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud compute instant-snapshot-groups create $ gcloud beta compute instant-snapshot-groups create diff --git a/gcloud/alpha/compute/instant-snapshot-groups/delete b/gcloud/alpha/compute/instant-snapshot-groups/delete index f1e270cda..7bd584f65 100644 --- a/gcloud/alpha/compute/instant-snapshot-groups/delete +++ b/gcloud/alpha/compute/instant-snapshot-groups/delete @@ -1,6 +1,6 @@ NAME gcloud alpha compute instant-snapshot-groups delete - delete a Compute - Engine instant snapshot group + Engine consistency group of instant snapshots SYNOPSIS gcloud alpha compute instant-snapshot-groups delete @@ -8,7 +8,7 @@ SYNOPSIS [--region=REGION | --zone=ZONE] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) Delete a Compute Engine instant snapshot group. + (ALPHA) Delete a Compute Engine consistency group of instant snapshots. POSITIONAL ARGUMENTS INSTANT_SNAPSHOT_GROUP_NAME [INSTANT_SNAPSHOT_GROUP_NAME ...] @@ -70,7 +70,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud compute instant-snapshot-groups delete $ gcloud beta compute instant-snapshot-groups delete diff --git a/gcloud/alpha/compute/instant-snapshot-groups/describe b/gcloud/alpha/compute/instant-snapshot-groups/describe index 831c76827..410f59699 100644 --- a/gcloud/alpha/compute/instant-snapshot-groups/describe +++ b/gcloud/alpha/compute/instant-snapshot-groups/describe @@ -1,6 +1,6 @@ NAME gcloud alpha compute instant-snapshot-groups describe - describe a Compute - Engine instant snapshot group + Engine consistency group of instant snapshots SYNOPSIS gcloud alpha compute instant-snapshot-groups describe @@ -9,11 +9,12 @@ SYNOPSIS DESCRIPTION (ALPHA) gcloud alpha compute instant-snapshot-groups describe displays all - data associated with a Compute Engine instant snapshot group in a project. + data associated with a Compute Engine consistency group of instant + snapshots in a project. EXAMPLES - To describe the instant snapshot group 'instant-snapshot-group-1' in zone - 'us-east1-a', run: + To describe the consistency group of instant snapshots + 'instant-snapshot-group-1' in zone 'us-east1-a', run: $ gcloud alpha compute instant-snapshot-groups describe \ instant-snapshot-group-1 --zone=us-east1-a @@ -78,7 +79,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud compute instant-snapshot-groups describe $ gcloud beta compute instant-snapshot-groups describe diff --git a/gcloud/alpha/compute/instant-snapshot-groups/help b/gcloud/alpha/compute/instant-snapshot-groups/help index 6321d0975..6289f21d9 100644 --- a/gcloud/alpha/compute/instant-snapshot-groups/help +++ b/gcloud/alpha/compute/instant-snapshot-groups/help @@ -17,13 +17,14 @@ COMMANDS COMMAND is one of the following: create - (ALPHA) Create a Compute Engine instant snapshot group. + (ALPHA) Create a Compute Engine consistency group of instant snapshots. delete - (ALPHA) Delete a Compute Engine instant snapshot group. + (ALPHA) Delete a Compute Engine consistency group of instant snapshots. describe - (ALPHA) Describe a Compute Engine instant snapshot group. + (ALPHA) Describe a Compute Engine consistency group of instant + snapshots. list (ALPHA) List Google Compute Engine instant snapshot groups. @@ -32,7 +33,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud compute instant-snapshot-groups $ gcloud beta compute instant-snapshot-groups diff --git a/gcloud/alpha/compute/instant-snapshot-groups/list b/gcloud/alpha/compute/instant-snapshot-groups/list index 9ccdc95ca..3c7eee109 100644 --- a/gcloud/alpha/compute/instant-snapshot-groups/list +++ b/gcloud/alpha/compute/instant-snapshot-groups/list @@ -92,7 +92,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud compute instant-snapshot-groups list $ gcloud beta compute instant-snapshot-groups list diff --git a/gcloud/alpha/compute/interconnects/groups/create-members b/gcloud/alpha/compute/interconnects/groups/create-members index 4bb89f16b..65edf3ae3 100644 --- a/gcloud/alpha/compute/interconnects/groups/create-members +++ b/gcloud/alpha/compute/interconnects/groups/create-members @@ -28,7 +28,12 @@ EXAMPLES example-interconnect-group --interconnect-type=DEDICATED \ --link-type=LINK_TYPE_ETHERNET_10G_LR --requested-link-count=1 \ --facility=iad-1 --interconnect="name=interconnect1" \ - --interconnect="name=interconnect2" + --interconnect="name=interconnect2,facility=iad-5467" + + Note that facility is required for each member interconnect. + interconnect1's facility is set to the default value iad-1 and + interconnect2's facility is overridden to iad-5467 in the --interconnect + flag. POSITIONAL ARGUMENTS NAME @@ -44,12 +49,9 @@ REQUIRED FLAGS must be specified. These flags are defined as a comma separated list of flag=value pairs. - Example: --interconnect - name=interconnect1,facility=iad-1,description="my - interconnect",link-type=LINK_TYPE_ETHERNET_10G_LR,requested-link-count=1, - interconnect-type=DEDICATED,admin-enabled, - noc-contact-email=noc@google.com,customer-name=customer-name - requested-features=MACSEC:CROSS_SITE_NETWORK + Example: + + --interconnect name=interconnect1,facility=iad-1,description="my interconnect",link-type=LINK_TYPE_ETHERNET_10G_LR,requested-link-count=1,interconnect-type=DEDICATED,admin-enabled,noc-contact-email=noc@google.com,customer-name=customer-name,requested-features=MACSEC:CROSS_SITE_NETWORK Note that for multiple requested-features, use a colon (:) as the delimiter, as the comma is used to separate the flags. Similarly, if @@ -136,6 +138,21 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. +DEFAULTABLE PER-INTERCONNECT FLAGS + All flags except --intent-mismatch-behavior in the OPTIONAL FLAGS section + are defaultable per-interconnect. This means that you can set a default + value by using these flags, or you can override the value for each + interconnect by using the --interconnect flag. + + Furthermore, if the default values for the following flags are not + specified, then they must be specified per-interconnect in the + --interconnect flag: + + ▪ --facility + ▪ --interconnect-type + ▪ --link-type + ▪ --requested-link-count + NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct diff --git a/gcloud/alpha/compute/migration/image-imports/help b/gcloud/alpha/compute/migration/image-imports/help index 17e3a31a2..f2899ac4d 100644 --- a/gcloud/alpha/compute/migration/image-imports/help +++ b/gcloud/alpha/compute/migration/image-imports/help @@ -6,22 +6,22 @@ SYNOPSIS gcloud alpha compute migration image-imports COMMAND [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) gcloud alpha migration vms image-imports provides a more robust and - better supported method for importing images to Google Compute Engine. + (ALPHA) gcloud alpha compute migration image-imports provides a more robust + and better supported method for importing images to Google Compute Engine. Other image-related operations (for example, list) can be done using gcloud compute images, as usual. - The commands use VM Migartion API which supports importing of an image from + The commands use VM Migration API which supports importing of an image from a Google Cloud Storage file (gs://...) to a target project. VM Migration API must be enabled in your project. - gcloud alpha migration vms image-imports create creates an Image Import + gcloud alpha compute migration image-imports create creates an Image Import resource with a nested Image Import Job resource. The Image Import Job resource tracks the image import progress. After the Image Import Job completes, successfully or otherwise, there's no further use for the Image Import resource. - The image is imported to a Google Cloud Project, desginated by the Target + The image is imported to a Google Cloud Project, designated by the Target Project resource. To get a list of Target Projects, run the gcloud alpha migration vms target-projects list command. Use the Google Cloud console to add target project resources. For information on adding target projects, diff --git a/gcloud/alpha/compute/network-endpoint-groups/create b/gcloud/alpha/compute/network-endpoint-groups/create index 5a98081df..4b2a2afc7 100644 --- a/gcloud/alpha/compute/network-endpoint-groups/create +++ b/gcloud/alpha/compute/network-endpoint-groups/create @@ -52,8 +52,14 @@ FLAGS private-service-connect. --network=NETWORK - Name of the network in which the NEG is created. default project - network is used if unspecified. + Name of the network in which the NEG is created. For + networkEndpointType GCE_VM_IP_PORT, GCE_VM_IP_PORTMAP or + NON_GCP_PRIVATE_IP_PORT, if this field is not specified, a default + network will be used. This field cannot be set for NEGs with + networkEndpointType set to SERVERLESS or PRIVATE_SERVICE_CONNECT and + for global NEGs. + + For all other network endpoint types, this field is required. This is only supported for NEGs with endpoint type gce-vm-ip-port, non-gcp-private-ip-port, gce-vm-ip, private-service-connect, diff --git a/gcloud/alpha/compute/networks/peerings/cancel-request-delete b/gcloud/alpha/compute/networks/peerings/cancel-request-delete index 8c0a89828..17e1d5262 100644 --- a/gcloud/alpha/compute/networks/peerings/cancel-request-delete +++ b/gcloud/alpha/compute/networks/peerings/cancel-request-delete @@ -47,7 +47,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud compute networks peerings cancel-request-delete $ gcloud beta compute networks peerings cancel-request-delete diff --git a/gcloud/alpha/compute/networks/subnets/create b/gcloud/alpha/compute/networks/subnets/create index 3b9e5e617..00ed8fd5f 100644 --- a/gcloud/alpha/compute/networks/subnets/create +++ b/gcloud/alpha/compute/networks/subnets/create @@ -11,6 +11,7 @@ SYNOPSIS [--flow-sampling=FLOW_SAMPLING] [--internal-ipv6-prefix=INTERNAL_IPV6_PREFIX] [--ip-collection=IP_COLLECTION] [--ipv6-access-type=IPV6_ACCESS_TYPE] + [--ipv6-network-tier=IPV6_NETWORK_TIER] [--logging-aggregation-interval=LOGGING_AGGREGATION_INTERVAL] [--logging-filter-expr=LOGGING_FILTER_EXPR] [--logging-flow-sampling=LOGGING_FLOW_SAMPLING] @@ -21,6 +22,8 @@ SYNOPSIS [--reserved-internal-range=RESERVED_INTERNAL_RANGE] [--resolve-subnet-mask=RESOLVE_SUBNET_MASK] [--resource-manager-tags=[KEY=VALUE,...]] [--role=ROLE] + [--secondary-ipv6-range=rangeName=RANGE_NAME, + ipv6CidrRange=IPV6_RANGE,ipCollection=IP_COLLECTION,[...]] [--secondary-range=PROPERTY=VALUE,[...]] [--secondary-range-with-reserved-internal-range=RANGE_NAME=INTERNAL_RANGE_URL, [...]] [--stack-type=STACK_TYPE] [--enable-l2 : --vlan=VLAN] @@ -115,6 +118,10 @@ OPTIONAL FLAGS INTERNAL VMs in this subnet can have internal IPv6. + --ipv6-network-tier=IPV6_NETWORK_TIER + The network tier for EXTERNAL IPv6 addresses in this subnetwork. + IPV6_NETWORK_TIER must be one of: PREMIUM, STANDARD. + --logging-aggregation-interval=LOGGING_AGGREGATION_INTERVAL Can only be specified if VPC Flow Logs for this subnetwork is enabled. Toggles the aggregation interval for collecting flow logs. Increasing @@ -245,6 +252,9 @@ OPTIONAL FLAGS BACKUP The BACKUP subnet that could be promoted to ACTIVE. + --secondary-ipv6-range=rangeName=RANGE_NAME,ipv6CidrRange=IPV6_RANGE,ipCollection=IP_COLLECTION,[...] + Adds a secondary IPv6 range to the subnetwork. + --secondary-range=PROPERTY=VALUE,[...] Adds a secondary IP range to the subnetwork for use in IP aliasing. diff --git a/gcloud/alpha/compute/networks/subnets/update b/gcloud/alpha/compute/networks/subnets/update index eeb6cd8e3..c960b5f8f 100644 --- a/gcloud/alpha/compute/networks/subnets/update +++ b/gcloud/alpha/compute/networks/subnets/update @@ -11,17 +11,21 @@ SYNOPSIS [--flow-sampling=FLOW_SAMPLING] [--internal-ipv6-prefix=INTERNAL_IPV6_PREFIX] [--ip-collection=IP_COLLECTION] [--ipv6-access-type=IPV6_ACCESS_TYPE] + [--ipv6-network-tier=IPV6_NETWORK_TIER] [--logging-aggregation-interval=LOGGING_AGGREGATION_INTERVAL] [--logging-filter-expr=LOGGING_FILTER_EXPR] [--logging-flow-sampling=LOGGING_FLOW_SAMPLING] [--logging-metadata=LOGGING_METADATA] [--logging-metadata-fields=[METADATA_FIELD,...]] [--metadata=METADATA] [--region=REGION] [--stack-type=STACK_TYPE] - [--add-secondary-ranges=PROPERTY=VALUE,[...] + [--add-secondary-ipv6-range=rangeName=RANGE_NAME, + ipv6CidrRange=IPV6_RANGE,ipCollection=IP_COLLECTION,[...] + | --add-secondary-ranges=PROPERTY=VALUE,[...] | --[no-]allow-cidr-routes-overlap | --[no-]enable-flow-logs | --[no-]enable-private-ip-google-access | --private-ipv6-google-access-type=PRIVATE_IPV6_GOOGLE_ACCESS_TYPE | --purpose=PURPOSE + | --remove-secondary-ipv6-range=RANGE_NAME,[RANGE_NAME,...] | --remove-secondary-ranges=RANGE_NAME,[RANGE_NAME,...] | --role=ROLE] [GCLOUD_WIDE_FLAG ...] @@ -113,6 +117,10 @@ FLAGS INTERNAL VMs in this subnet can have internal IPv6. + --ipv6-network-tier=IPV6_NETWORK_TIER + The network tier for EXTERNAL IPv6 addresses in this subnetwork. + IPV6_NETWORK_TIER must be one of: PREMIUM, STANDARD. + --logging-aggregation-interval=LOGGING_AGGREGATION_INTERVAL Can only be specified if VPC Flow Logs for this subnetwork is enabled. Toggles the aggregation interval for collecting flow logs. Increasing @@ -181,6 +189,9 @@ FLAGS At most one of these can be specified: + --add-secondary-ipv6-range=rangeName=RANGE_NAME,ipv6CidrRange=IPV6_RANGE,ipCollection=IP_COLLECTION,[...] + Adds a secondary IPv6 range to the subnetwork. + --add-secondary-ranges=PROPERTY=VALUE,[...] Adds secondary IP ranges to the subnetwork for use in IP aliasing. @@ -224,6 +235,9 @@ FLAGS INTERNAL_HTTPS_LOAD_BALANCER subnets can be changed to REGIONAL_MANAGED_PROXY. + --remove-secondary-ipv6-range=RANGE_NAME,[RANGE_NAME,...] + Removes secondary IPv6 ranges from the subnetwork. + --remove-secondary-ranges=RANGE_NAME,[RANGE_NAME,...] Removes secondary ranges from the subnetwork. diff --git a/gcloud/alpha/compute/project-info/add-metadata b/gcloud/alpha/compute/project-info/add-metadata index 4a065269c..cffc4033a 100644 --- a/gcloud/alpha/compute/project-info/add-metadata +++ b/gcloud/alpha/compute/project-info/add-metadata @@ -21,10 +21,10 @@ DESCRIPTION If you are using this command to manage SSH keys for your project, please note the risks - (https://cloud.google.com/compute/docs/instances/adding-removing-ssh-keys#risks) + (https://docs.cloud.google.com/compute/docs/instances/access-overview#risks) of manual SSH key management as well as the required format for SSH key metadata, available at - https://cloud.google.com/compute/docs/instances/adding-removing-ssh-keys + https://docs.cloud.google.com/compute/docs/connect/add-ssh-keys FLAGS --metadata=KEY=VALUE,[KEY=VALUE,...] diff --git a/gcloud/alpha/compute/queued-resources/create b/gcloud/alpha/compute/queued-resources/create index 841f0d185..a7b2d8148 100644 --- a/gcloud/alpha/compute/queued-resources/create +++ b/gcloud/alpha/compute/queued-resources/create @@ -466,7 +466,7 @@ OPTIONAL FLAGS The workload identity to use for the instance. --[no-]identity-certificate - Enables or disables managed workload identities on a VM. Use + Enables or disables managed workload identity certificates on a VM. Use --identity-certificate to enable and --no-identity-certificate to disable. @@ -1140,6 +1140,8 @@ OPTIONAL FLAGS any Consume any available, matching reservation. + any-reservation-then-fail + Must consume from any automatic reservation; fail otherwise. none Do not consume from any reserved capacity. specific diff --git a/gcloud/alpha/compute/rollout-plans/create b/gcloud/alpha/compute/rollout-plans/create index ae43e7517..e9f49de8e 100644 --- a/gcloud/alpha/compute/rollout-plans/create +++ b/gcloud/alpha/compute/rollout-plans/create @@ -64,7 +64,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud compute rollout-plans create $ gcloud beta compute rollout-plans create diff --git a/gcloud/alpha/compute/rollout-plans/delete b/gcloud/alpha/compute/rollout-plans/delete index 607214246..818cbccbc 100644 --- a/gcloud/alpha/compute/rollout-plans/delete +++ b/gcloud/alpha/compute/rollout-plans/delete @@ -45,7 +45,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud compute rollout-plans delete $ gcloud beta compute rollout-plans delete diff --git a/gcloud/alpha/compute/rollout-plans/describe b/gcloud/alpha/compute/rollout-plans/describe index aee2bb4b0..92ff26daf 100644 --- a/gcloud/alpha/compute/rollout-plans/describe +++ b/gcloud/alpha/compute/rollout-plans/describe @@ -50,7 +50,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud compute rollout-plans describe $ gcloud beta compute rollout-plans describe diff --git a/gcloud/alpha/compute/rollout-plans/help b/gcloud/alpha/compute/rollout-plans/help index 91106f517..a0fd74c4d 100644 --- a/gcloud/alpha/compute/rollout-plans/help +++ b/gcloud/alpha/compute/rollout-plans/help @@ -32,7 +32,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud compute rollout-plans $ gcloud beta compute rollout-plans diff --git a/gcloud/alpha/compute/rollout-plans/list b/gcloud/alpha/compute/rollout-plans/list index 1eb856f63..789ae2cd0 100644 --- a/gcloud/alpha/compute/rollout-plans/list +++ b/gcloud/alpha/compute/rollout-plans/list @@ -63,7 +63,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud compute rollout-plans list $ gcloud beta compute rollout-plans list diff --git a/gcloud/alpha/compute/rollouts/cancel b/gcloud/alpha/compute/rollouts/cancel index 30a3c501f..f79c3774b 100644 --- a/gcloud/alpha/compute/rollouts/cancel +++ b/gcloud/alpha/compute/rollouts/cancel @@ -50,7 +50,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud compute rollouts cancel $ gcloud beta compute rollouts cancel diff --git a/gcloud/alpha/compute/rollouts/delete b/gcloud/alpha/compute/rollouts/delete index f443698be..209caa4de 100644 --- a/gcloud/alpha/compute/rollouts/delete +++ b/gcloud/alpha/compute/rollouts/delete @@ -44,7 +44,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud compute rollouts delete $ gcloud beta compute rollouts delete diff --git a/gcloud/alpha/compute/rollouts/describe b/gcloud/alpha/compute/rollouts/describe index c1821d73c..2364c7293 100644 --- a/gcloud/alpha/compute/rollouts/describe +++ b/gcloud/alpha/compute/rollouts/describe @@ -48,7 +48,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud compute rollouts describe $ gcloud beta compute rollouts describe diff --git a/gcloud/alpha/compute/rollouts/help b/gcloud/alpha/compute/rollouts/help index a3dcb9c00..0baea3537 100644 --- a/gcloud/alpha/compute/rollouts/help +++ b/gcloud/alpha/compute/rollouts/help @@ -31,7 +31,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud compute rollouts $ gcloud beta compute rollouts diff --git a/gcloud/alpha/compute/rollouts/list b/gcloud/alpha/compute/rollouts/list index 85d51ba73..a73baa2b0 100644 --- a/gcloud/alpha/compute/rollouts/list +++ b/gcloud/alpha/compute/rollouts/list @@ -62,7 +62,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud compute rollouts list $ gcloud beta compute rollouts list diff --git a/gcloud/alpha/compute/service-attachments/create b/gcloud/alpha/compute/service-attachments/create index 5f8fcc282..020b57c8d 100644 --- a/gcloud/alpha/compute/service-attachments/create +++ b/gcloud/alpha/compute/service-attachments/create @@ -12,6 +12,7 @@ SYNOPSIS [--consumer-accept-list=[PROJECT_OR_NETWORK=LIMIT,...]] [--consumer-reject-list=[REJECT_LIST,...]] [--description=DESCRIPTION] [--domain-names=[DOMAIN_NAMES,...]] [--enable-proxy-protocol] + [--nat-ips-per-endpoint=NAT_IPS_PER_ENDPOINT] [--nat-subnets-region=NAT_SUBNETS_REGION] [--propagated-connection-limit=PROPAGATED_CONNECTION_LIMIT] [--reconcile-connections] [--region=REGION] @@ -110,6 +111,9 @@ OPTIONAL FLAGS TCP/IP address data in TCP connections that traverse proxies on their way to destination servers. + --nat-ips-per-endpoint=NAT_IPS_PER_ENDPOINT + The number of NAT IP addresses to be allocated per connected endpoint. + --nat-subnets-region=NAT_SUBNETS_REGION Region of the subnetworks to operate on. If not specified, it will be set to the region of the service attachment. Overrides the default diff --git a/gcloud/alpha/compute/service-attachments/update b/gcloud/alpha/compute/service-attachments/update index 8d2fc2001..dd1893240 100644 --- a/gcloud/alpha/compute/service-attachments/update +++ b/gcloud/alpha/compute/service-attachments/update @@ -8,6 +8,7 @@ SYNOPSIS [--consumer-accept-list=[PROJECT_OR_NETWORK_OR_ENDPOINT=LIMIT,...]] [--consumer-reject-list=[REJECT_LIST,...]] [--description=DESCRIPTION] [--[no-]enable-proxy-protocol] + [--nat-ips-per-endpoint=NAT_IPS_PER_ENDPOINT] [--nat-subnets=NAT_SUBNETS,[NAT_SUBNETS,...]] [--nat-subnets-region=NAT_SUBNETS_REGION] [--propagated-connection-limit=PROPAGATED_CONNECTION_LIMIT] @@ -92,6 +93,9 @@ FLAGS way to destination servers. Use --enable-proxy-protocol to enable and --no-enable-proxy-protocol to disable. + --nat-ips-per-endpoint=NAT_IPS_PER_ENDPOINT + The number of NAT IP addresses to be allocated per connected endpoint. + --nat-subnets=NAT_SUBNETS,[NAT_SUBNETS,...] The subnetworks provided by service producer to use for NAT diff --git a/gcloud/alpha/compute/snapshots/help b/gcloud/alpha/compute/snapshots/help index 1dea23398..ff21cc180 100644 --- a/gcloud/alpha/compute/snapshots/help +++ b/gcloud/alpha/compute/snapshots/help @@ -56,7 +56,8 @@ COMMANDS (ALPHA) Update a Compute Engine snapshot. update-kms-key - (ALPHA) Update the KMS key of a Compute Engine snapshot. + (ALPHA) Update the KMS key of a Compute Engine standard or archive + snapshot. NOTES This command is currently in alpha and might change without notice. If this diff --git a/gcloud/alpha/compute/snapshots/update-kms-key b/gcloud/alpha/compute/snapshots/update-kms-key index b30b7f478..929c96bb1 100644 --- a/gcloud/alpha/compute/snapshots/update-kms-key +++ b/gcloud/alpha/compute/snapshots/update-kms-key @@ -1,6 +1,6 @@ NAME gcloud alpha compute snapshots update-kms-key - update the KMS key of a - Compute Engine snapshot + Compute Engine standard or archive snapshot SYNOPSIS gcloud alpha compute snapshots update-kms-key SNAPSHOT_NAME @@ -10,9 +10,9 @@ SYNOPSIS [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) * gcloud alpha compute snapshots update-kms-key updates the KMS key - of a Compute Engine persistent snapshot by rotating it to the primary - version of the key or to the primary version of a new KMS key. + (ALPHA) gcloud alpha compute snapshots update-kms-key updates the KMS key + of a Compute Engine standard or archive snapshot by rotating it to the + primary version of the key or to the primary version of a new KMS key. EXAMPLES To update the KMS key of a snapshot named example-snapshot-1, run: diff --git a/gcloud/alpha/compute/zone-vm-extension-policies/create b/gcloud/alpha/compute/zone-vm-extension-policies/create index 799658aa6..22951cbd8 100644 --- a/gcloud/alpha/compute/zone-vm-extension-policies/create +++ b/gcloud/alpha/compute/zone-vm-extension-policies/create @@ -134,7 +134,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud compute zone-vm-extension-policies create $ gcloud beta compute zone-vm-extension-policies create diff --git a/gcloud/alpha/compute/zone-vm-extension-policies/delete b/gcloud/alpha/compute/zone-vm-extension-policies/delete index 1a9784d6e..858970d3f 100644 --- a/gcloud/alpha/compute/zone-vm-extension-policies/delete +++ b/gcloud/alpha/compute/zone-vm-extension-policies/delete @@ -53,7 +53,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud compute zone-vm-extension-policies delete $ gcloud beta compute zone-vm-extension-policies delete diff --git a/gcloud/alpha/compute/zone-vm-extension-policies/describe b/gcloud/alpha/compute/zone-vm-extension-policies/describe index 9810c1264..581d32410 100644 --- a/gcloud/alpha/compute/zone-vm-extension-policies/describe +++ b/gcloud/alpha/compute/zone-vm-extension-policies/describe @@ -53,7 +53,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud compute zone-vm-extension-policies describe $ gcloud beta compute zone-vm-extension-policies describe diff --git a/gcloud/alpha/compute/zone-vm-extension-policies/help b/gcloud/alpha/compute/zone-vm-extension-policies/help index 83f90f26f..1327de1f7 100644 --- a/gcloud/alpha/compute/zone-vm-extension-policies/help +++ b/gcloud/alpha/compute/zone-vm-extension-policies/help @@ -43,7 +43,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud compute zone-vm-extension-policies $ gcloud beta compute zone-vm-extension-policies diff --git a/gcloud/alpha/compute/zone-vm-extension-policies/list b/gcloud/alpha/compute/zone-vm-extension-policies/list index 93182d814..1c160872e 100644 --- a/gcloud/alpha/compute/zone-vm-extension-policies/list +++ b/gcloud/alpha/compute/zone-vm-extension-policies/list @@ -63,7 +63,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud compute zone-vm-extension-policies list $ gcloud beta compute zone-vm-extension-policies list diff --git a/gcloud/alpha/compute/zone-vm-extension-policies/update b/gcloud/alpha/compute/zone-vm-extension-policies/update index f788c376f..4e9f9f780 100644 --- a/gcloud/alpha/compute/zone-vm-extension-policies/update +++ b/gcloud/alpha/compute/zone-vm-extension-policies/update @@ -129,7 +129,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud compute zone-vm-extension-policies update $ gcloud beta compute zone-vm-extension-policies update diff --git a/gcloud/alpha/config/get b/gcloud/alpha/config/get index 17eaabeb3..b4642749a 100644 --- a/gcloud/alpha/config/get +++ b/gcloud/alpha/config/get @@ -208,6 +208,10 @@ AVAILABLE PROPERTIES Overrides API endpoint for gcloud apphub command group. Defaults to https://apphub.googleapis.com/ + appoptimize + Overrides API endpoint for gcloud app-optimize command group. + Defaults to https://appoptimize.googleapis.com/ + artifactregistry Overrides API endpoint for gcloud artifacts command group. Defaults to https://artifactregistry.googleapis.com/ @@ -384,7 +388,6 @@ AVAILABLE PROPERTIES faultinjectiontesting Overrides API endpoint for gcloud fault-injection command group. - Defaults to https://faultinjectiontesting.googleapis.com/ faulttesting Overrides API endpoint for gcloud fault-testing command group. @@ -446,10 +449,6 @@ AVAILABLE PROPERTIES Overrides API endpoint for gcloud ml language command group. Defaults to https://language.googleapis.com/ - lifesciences - Overrides API endpoint for gcloud lifesciences command group. - Defaults to https://lifesciences.googleapis.com/ - logging Overrides API endpoint for gcloud logging command group. Defaults to https://logging.googleapis.com/ @@ -570,6 +569,10 @@ AVAILABLE PROPERTIES Overrides API endpoint for gcloud service-directory command group. Defaults to https://servicedirectory.googleapis.com/ + servicehealth + Overrides API endpoint for gcloud servicehealth command group. + Defaults to https://servicehealth.googleapis.com/ + servicemanagement Overrides API endpoint for gcloud endpoints command group. Defaults to https://servicemanagement.googleapis.com/ @@ -1049,12 +1052,6 @@ AVAILABLE PROPERTIES suggest If True, add command line suggestions based on history. - lifesciences - location - Default location to use when working with Cloud Life Sciences - resources. When a --location flag is required but not provided, the - command will fall back to this value. - looker region Default region to use when working with Cloud Looker resources. diff --git a/gcloud/alpha/config/help b/gcloud/alpha/config/help index 6e4d68839..4ad4177fc 100644 --- a/gcloud/alpha/config/help +++ b/gcloud/alpha/config/help @@ -240,6 +240,10 @@ AVAILABLE PROPERTIES Overrides API endpoint for gcloud apphub command group. Defaults to https://apphub.googleapis.com/ + appoptimize + Overrides API endpoint for gcloud app-optimize command group. + Defaults to https://appoptimize.googleapis.com/ + artifactregistry Overrides API endpoint for gcloud artifacts command group. Defaults to https://artifactregistry.googleapis.com/ @@ -416,7 +420,6 @@ AVAILABLE PROPERTIES faultinjectiontesting Overrides API endpoint for gcloud fault-injection command group. - Defaults to https://faultinjectiontesting.googleapis.com/ faulttesting Overrides API endpoint for gcloud fault-testing command group. @@ -478,10 +481,6 @@ AVAILABLE PROPERTIES Overrides API endpoint for gcloud ml language command group. Defaults to https://language.googleapis.com/ - lifesciences - Overrides API endpoint for gcloud lifesciences command group. - Defaults to https://lifesciences.googleapis.com/ - logging Overrides API endpoint for gcloud logging command group. Defaults to https://logging.googleapis.com/ @@ -602,6 +601,10 @@ AVAILABLE PROPERTIES Overrides API endpoint for gcloud service-directory command group. Defaults to https://servicedirectory.googleapis.com/ + servicehealth + Overrides API endpoint for gcloud servicehealth command group. + Defaults to https://servicehealth.googleapis.com/ + servicemanagement Overrides API endpoint for gcloud endpoints command group. Defaults to https://servicemanagement.googleapis.com/ @@ -1081,12 +1084,6 @@ AVAILABLE PROPERTIES suggest If True, add command line suggestions based on history. - lifesciences - location - Default location to use when working with Cloud Life Sciences - resources. When a --location flag is required but not provided, the - command will fall back to this value. - looker region Default region to use when working with Cloud Looker resources. diff --git a/gcloud/alpha/config/list b/gcloud/alpha/config/list index d72beddc3..1884dbb20 100644 --- a/gcloud/alpha/config/list +++ b/gcloud/alpha/config/list @@ -252,6 +252,10 @@ AVAILABLE PROPERTIES Overrides API endpoint for gcloud apphub command group. Defaults to https://apphub.googleapis.com/ + appoptimize + Overrides API endpoint for gcloud app-optimize command group. + Defaults to https://appoptimize.googleapis.com/ + artifactregistry Overrides API endpoint for gcloud artifacts command group. Defaults to https://artifactregistry.googleapis.com/ @@ -428,7 +432,6 @@ AVAILABLE PROPERTIES faultinjectiontesting Overrides API endpoint for gcloud fault-injection command group. - Defaults to https://faultinjectiontesting.googleapis.com/ faulttesting Overrides API endpoint for gcloud fault-testing command group. @@ -490,10 +493,6 @@ AVAILABLE PROPERTIES Overrides API endpoint for gcloud ml language command group. Defaults to https://language.googleapis.com/ - lifesciences - Overrides API endpoint for gcloud lifesciences command group. - Defaults to https://lifesciences.googleapis.com/ - logging Overrides API endpoint for gcloud logging command group. Defaults to https://logging.googleapis.com/ @@ -614,6 +613,10 @@ AVAILABLE PROPERTIES Overrides API endpoint for gcloud service-directory command group. Defaults to https://servicedirectory.googleapis.com/ + servicehealth + Overrides API endpoint for gcloud servicehealth command group. + Defaults to https://servicehealth.googleapis.com/ + servicemanagement Overrides API endpoint for gcloud endpoints command group. Defaults to https://servicemanagement.googleapis.com/ @@ -1093,12 +1096,6 @@ AVAILABLE PROPERTIES suggest If True, add command line suggestions based on history. - lifesciences - location - Default location to use when working with Cloud Life Sciences - resources. When a --location flag is required but not provided, the - command will fall back to this value. - looker region Default region to use when working with Cloud Looker resources. diff --git a/gcloud/alpha/config/set b/gcloud/alpha/config/set index 00646fd93..a99dced89 100644 --- a/gcloud/alpha/config/set +++ b/gcloud/alpha/config/set @@ -255,6 +255,10 @@ AVAILABLE PROPERTIES Overrides API endpoint for gcloud apphub command group. Defaults to https://apphub.googleapis.com/ + appoptimize + Overrides API endpoint for gcloud app-optimize command group. + Defaults to https://appoptimize.googleapis.com/ + artifactregistry Overrides API endpoint for gcloud artifacts command group. Defaults to https://artifactregistry.googleapis.com/ @@ -431,7 +435,6 @@ AVAILABLE PROPERTIES faultinjectiontesting Overrides API endpoint for gcloud fault-injection command group. - Defaults to https://faultinjectiontesting.googleapis.com/ faulttesting Overrides API endpoint for gcloud fault-testing command group. @@ -493,10 +496,6 @@ AVAILABLE PROPERTIES Overrides API endpoint for gcloud ml language command group. Defaults to https://language.googleapis.com/ - lifesciences - Overrides API endpoint for gcloud lifesciences command group. - Defaults to https://lifesciences.googleapis.com/ - logging Overrides API endpoint for gcloud logging command group. Defaults to https://logging.googleapis.com/ @@ -617,6 +616,10 @@ AVAILABLE PROPERTIES Overrides API endpoint for gcloud service-directory command group. Defaults to https://servicedirectory.googleapis.com/ + servicehealth + Overrides API endpoint for gcloud servicehealth command group. + Defaults to https://servicehealth.googleapis.com/ + servicemanagement Overrides API endpoint for gcloud endpoints command group. Defaults to https://servicemanagement.googleapis.com/ @@ -1096,12 +1099,6 @@ AVAILABLE PROPERTIES suggest If True, add command line suggestions based on history. - lifesciences - location - Default location to use when working with Cloud Life Sciences - resources. When a --location flag is required but not provided, the - command will fall back to this value. - looker region Default region to use when working with Cloud Looker resources. diff --git a/gcloud/alpha/config/unset b/gcloud/alpha/config/unset index a7300f2c3..513e61ff7 100644 --- a/gcloud/alpha/config/unset +++ b/gcloud/alpha/config/unset @@ -216,6 +216,10 @@ AVAILABLE PROPERTIES Overrides API endpoint for gcloud apphub command group. Defaults to https://apphub.googleapis.com/ + appoptimize + Overrides API endpoint for gcloud app-optimize command group. + Defaults to https://appoptimize.googleapis.com/ + artifactregistry Overrides API endpoint for gcloud artifacts command group. Defaults to https://artifactregistry.googleapis.com/ @@ -392,7 +396,6 @@ AVAILABLE PROPERTIES faultinjectiontesting Overrides API endpoint for gcloud fault-injection command group. - Defaults to https://faultinjectiontesting.googleapis.com/ faulttesting Overrides API endpoint for gcloud fault-testing command group. @@ -454,10 +457,6 @@ AVAILABLE PROPERTIES Overrides API endpoint for gcloud ml language command group. Defaults to https://language.googleapis.com/ - lifesciences - Overrides API endpoint for gcloud lifesciences command group. - Defaults to https://lifesciences.googleapis.com/ - logging Overrides API endpoint for gcloud logging command group. Defaults to https://logging.googleapis.com/ @@ -578,6 +577,10 @@ AVAILABLE PROPERTIES Overrides API endpoint for gcloud service-directory command group. Defaults to https://servicedirectory.googleapis.com/ + servicehealth + Overrides API endpoint for gcloud servicehealth command group. + Defaults to https://servicehealth.googleapis.com/ + servicemanagement Overrides API endpoint for gcloud endpoints command group. Defaults to https://servicemanagement.googleapis.com/ @@ -1057,12 +1060,6 @@ AVAILABLE PROPERTIES suggest If True, add command line suggestions based on history. - lifesciences - location - Default location to use when working with Cloud Life Sciences - resources. When a --location flag is required but not provided, the - command will fall back to this value. - looker region Default region to use when working with Cloud Looker resources. diff --git a/gcloud/alpha/container/binauthz/continuous-validation/describe b/gcloud/alpha/container/binauthz/continuous-validation/describe deleted file mode 100644 index c92efd5d3..000000000 --- a/gcloud/alpha/container/binauthz/continuous-validation/describe +++ /dev/null @@ -1,33 +0,0 @@ -NAME - gcloud alpha container binauthz continuous-validation describe - show the - configuration of Binary Authorization Continuous Validation for the - project - -SYNOPSIS - gcloud alpha container binauthz continuous-validation describe - [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (ALPHA) The output will contain "enabled: true" if Continuous Validation is - enabled for the project, or "enabled: false" if CV is disabled. - -EXAMPLES - $ gcloud alpha container binauthz continuous-validation describe \ - enforcementPolicyConfig: enabled: true name: \ - projects/my-project/continuousValidationConfig updateTime: \ - '2020-01-01T01:23:45.678901234Z' - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --configuration, --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/container/binauthz/continuous-validation/disable b/gcloud/alpha/container/binauthz/continuous-validation/disable deleted file mode 100644 index b1e54bef8..000000000 --- a/gcloud/alpha/container/binauthz/continuous-validation/disable +++ /dev/null @@ -1,27 +0,0 @@ -NAME - gcloud alpha container binauthz continuous-validation disable - disable - Binary Authorization Continuous Validation for the project - -SYNOPSIS - gcloud alpha container binauthz continuous-validation disable - [GCLOUD_WIDE_FLAG ...] - -EXAMPLES - To disable Continuous Validation for the project: - - $ gcloud alpha container binauthz continuous-validation disable - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --configuration, --flags-file, --flatten, --format, - --help, --impersonate-service-account, --log-http, --project, --quiet, - --trace-token, --user-output-enabled, --verbosity. - - Run $ gcloud help for details. - -NOTES - This command is currently in alpha and might change without notice. If this - command fails with API permission errors despite specifying the correct - project, you might be trying to access an API with an invitation-only early - access allowlist. - diff --git a/gcloud/alpha/container/binauthz/continuous-validation/enable b/gcloud/alpha/container/binauthz/continuous-validation/enable deleted file mode 100644 index 66c29a1bb..000000000 --- a/gcloud/alpha/container/binauthz/continuous-validation/enable +++ /dev/null @@ -1,27 +0,0 @@ -NAME - gcloud alpha container binauthz continuous-validation enable - enable - Binary Authorization Continuous Validation for the project - -SYNOPSIS - gcloud alpha container binauthz continuous-validation enable - [GCLOUD_WIDE_FLAG ...] - -EXAMPLES - To enable Continuous Validation for the project: - - $ gcloud alpha container binauthz continuous-validation enable - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --configuration, --flags-file, --flatten, --format, - --help, --impersonate-service-account, --log-http, --project, --quiet, - --trace-token, --user-output-enabled, --verbosity. - - Run $ gcloud help for details. - -NOTES - This command is currently in alpha and might change without notice. If this - command fails with API permission errors despite specifying the correct - project, you might be trying to access an API with an invitation-only early - access allowlist. - diff --git a/gcloud/alpha/container/binauthz/continuous-validation/help b/gcloud/alpha/container/binauthz/continuous-validation/help deleted file mode 100644 index 54c2b5592..000000000 --- a/gcloud/alpha/container/binauthz/continuous-validation/help +++ /dev/null @@ -1,37 +0,0 @@ -NAME - gcloud alpha container binauthz continuous-validation - manage Binary - Authorization Continuous Validation - -SYNOPSIS - gcloud alpha container binauthz continuous-validation COMMAND - [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (ALPHA) Manage Binary Authorization Continuous Validation. - -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) Show the configuration of Binary Authorization Continuous - Validation for the project. - - disable - (ALPHA) Disable Binary Authorization Continuous Validation for the - project. - - enable - (ALPHA) Enable Binary Authorization Continuous Validation for the - project. - -NOTES - This command is currently in alpha and might change without notice. If this - command fails with API permission errors despite specifying the correct - project, you might be trying to access an API with an invitation-only early - access allowlist. - diff --git a/gcloud/alpha/container/binauthz/help b/gcloud/alpha/container/binauthz/help index 21a5a0e61..f4bc6744b 100644 --- a/gcloud/alpha/container/binauthz/help +++ b/gcloud/alpha/container/binauthz/help @@ -115,9 +115,6 @@ GROUPS attestors (ALPHA) Create and manage Google Binary Authorization Attestors. - continuous-validation - (ALPHA) Manage Binary Authorization Continuous Validation. - policy (ALPHA) Create and manage Google Binary Authorization policies. diff --git a/gcloud/alpha/container/clusters/create b/gcloud/alpha/container/clusters/create index 78e3d137b..83f120c2e 100644 --- a/gcloud/alpha/container/clusters/create +++ b/gcloud/alpha/container/clusters/create @@ -27,6 +27,7 @@ SYNOPSIS [--cluster-version=CLUSTER_VERSION] [--confidential-node-type=CONFIDENTIAL_NODE_TYPE] [--containerd-config-from-file=PATH_TO_FILE] + [--control-plane-egress=CONTROL_PLANE_EGRESS] [--create-subnetwork=[KEY=VALUE,...]] [--data-cache-count=DATA_CACHE_COUNT] [--database-encryption-key=DATABASE_ENCRYPTION_KEY] @@ -82,7 +83,9 @@ SYNOPSIS [--min-cpu-platform=PLATFORM] [--monitoring=[COMPONENT,...]] [--network=NETWORK] [--network-performance-configs=[PROPERTY1=VALUE1,...]] + [--node-architecture-taint-behavior=NODE_ARCHITECTURE_TAINT_BEHAVIOR] [--node-labels=[NODE_LABEL,...]] [--node-pool-name=NODE_POOL_NAME] + [--node-pool-upgrade-concurrency-config=[max-count=MAX-COUNT]] [--node-taints=[NODE_TAINT,...]] [--node-version=NODE_VERSION] [--notification-config=[pubsub=ENABLED|DISABLED, pubsub-topic=TOPIC,...]] [--num-nodes=NUM_NODES; default=3] @@ -502,6 +505,23 @@ FLAGS Use a full or relative path to a local file containing the value of containerd_config. + --control-plane-egress=CONTROL_PLANE_EGRESS + Configures the egress policy for the GKE control plane to control + outbound traffic from the kube-apiserver. CONTROL_PLANE_EGRESS must be + one of: + + NONE + (Recommended) Provides maximum security. This mode removes the + control plane's public IP address and blocks all outbound traffic + from the kube-apiserver by default, preventing unexpected data + exfiltration. Webhooks that use clientConfig.url will be disabled. + Essential GKE-managed services are still permitted to function via + an internal allowlist. + VIA_CONTROL_PLANE + (Default) Maintains backward compatibility. The control plane + retains its public IP address and allows egress traffic from the + kube-apiserver. + --create-subnetwork=[KEY=VALUE,...] Create a new subnetwork for the cluster. The name and range of the subnetwork can be customized via optional 'name' and 'range' key-value @@ -1252,6 +1272,26 @@ FLAGS https://cloud.google.com/compute/docs/networking/configure-vm-with-high-bandwidth-configuration for more information. + --node-architecture-taint-behavior=NODE_ARCHITECTURE_TAINT_BEHAVIOR + Control how architecture taint should be applied to nodes in default + node pool(s) in new cluster. + + Supported values: + * unspecified: Default behavior, currently the same as `arm`. + * arm: kubernetes.io/arch=arm:NoSchedule taint will be added for ARM nodes. + * none: No architecture taint will be applied. + + Examples: + + $ gcloud alpha container clusters create example-cluster \ + --node-architecture-taint-behavior=none + + To read more about node-taints, see + https://cloud.google.com/kubernetes-engine/docs/node-taints. + + NODE_ARCHITECTURE_TAINT_BEHAVIOR must be one of: unspecified, arm, + none. + --node-labels=[NODE_LABEL,...] Applies the given Kubernetes labels on all nodes in the new node pool. @@ -1287,6 +1327,18 @@ FLAGS --num-nodes 9 --max-nodes-per-pool 3 \ --node-pool-name example-node-pool + --node-pool-upgrade-concurrency-config=[max-count=MAX-COUNT] + Configure the concurrency settings for node pool auto upgrades. + + Examples: + + $ gcloud alpha container clusters create example-cluster \ + --node-pool-upgrade-concurrency-config=max-count=10 + + max-count + The maximum number of node pools to upgrade concurrently. The + maximum allowed value is 100. + --node-taints=[NODE_TAINT,...] Applies the given kubernetes taints on all nodes in default node pool(s) in new cluster, which can be used with tolerations for pod @@ -1829,6 +1881,12 @@ FLAGS 'veno', 'westwood', 'yeah'. + net.ipv4.neigh.default.gc_thresh1 Must be between + [0, 262144] + net.ipv4.neigh.default.gc_thresh2 Must be between + [512, 524288] + net.ipv4.neigh.default.gc_thresh3 Must be between + [1024, 1048576] net.netfilter.nf_conntrack_max Must be between [65536, 4194304] net.netfilter.nf_conntrack_buckets Must be between @@ -1844,6 +1902,10 @@ FLAGS net.netfilter.nf_conntrack_tcp_timeout_established Must be between [600, 86400] net.netfilter.nf_conntrack_acct Must be {0, 1} + kernel.keys.maxkeys Must be between + [200, 1048576] + kernel.keys.maxbytes Must be between + [20000, 2097152] kernel.shmmni Must be between [4096, 32768] kernel.shmmax Must be between @@ -2448,13 +2510,14 @@ FLAGS --max-cpu=MAX_CPU Maximum number of cores in the cluster. - Maximum number of cores to which the cluster can scale. + Maximum number of cores to which the cluster can scale. Required to + be set when --enable-autoprovisioning is used. --max-memory=MAX_MEMORY Maximum memory in the cluster. Maximum number of gigabytes of memory to which the cluster can - scale. + scale. Required to be set when --enable-autoprovisioning is used. --min-cpu=MIN_CPU Minimum number of cores in the cluster. diff --git a/gcloud/alpha/container/clusters/create-auto b/gcloud/alpha/container/clusters/create-auto index 17e437f09..01aaab196 100644 --- a/gcloud/alpha/container/clusters/create-auto +++ b/gcloud/alpha/container/clusters/create-auto @@ -15,7 +15,9 @@ SYNOPSIS [--cluster-ipv4-cidr=CLUSTER_IPV4_CIDR] [--cluster-secondary-range-name=NAME] [--cluster-version=CLUSTER_VERSION] + [--confidential-node-type=CONFIDENTIAL_NODE_TYPE] [--containerd-config-from-file=PATH_TO_FILE] + [--control-plane-egress=CONTROL_PLANE_EGRESS] [--create-subnetwork=[KEY=VALUE,...]] [--database-encryption-key=DATABASE_ENCRYPTION_KEY] [--disable-l4-lb-firewall-reconciliation] [--disable-multi-nic-lustre] @@ -36,11 +38,13 @@ SYNOPSIS [--hpa-profile=HPA_PROFILE] [--labels=[KEY=VALUE,...]] [--logging=[COMPONENT,...]] [--managed-otel-scope=MANAGED_OTEL_SCOPE] [--membership-type=MEMBERSHIP_TYPE] [--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] + [--network=NETWORK] + [--node-pool-upgrade-concurrency-config=[max-count=MAX-COUNT]] + [--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] @@ -281,6 +285,12 @@ FLAGS $ gcloud container get-server-config + --confidential-node-type=CONFIDENTIAL_NODE_TYPE + Enable confidential nodes for the cluster. Enabling Confidential Nodes + will create nodes using Confidential VM + https://docs.cloud.google.com/compute/docs/about-confidential-vm. + CONFIDENTIAL_NODE_TYPE must be one of: sev, sev_snp, tdx. + --containerd-config-from-file=PATH_TO_FILE Path of the YAML file that contains containerd configuration entries like configuring access to private image registries. @@ -295,6 +305,23 @@ FLAGS Use a full or relative path to a local file containing the value of containerd_config. + --control-plane-egress=CONTROL_PLANE_EGRESS + Configures the egress policy for the GKE control plane to control + outbound traffic from the kube-apiserver. CONTROL_PLANE_EGRESS must be + one of: + + NONE + (Recommended) Provides maximum security. This mode removes the + control plane's public IP address and blocks all outbound traffic + from the kube-apiserver by default, preventing unexpected data + exfiltration. Webhooks that use clientConfig.url will be disabled. + Essential GKE-managed services are still permitted to function via + an internal allowlist. + VIA_CONTROL_PLANE + (Default) Maintains backward compatibility. The control plane + retains its public IP address and allows egress traffic from the + kube-apiserver. + --create-subnetwork=[KEY=VALUE,...] Create a new subnetwork for the cluster. The name and range of the subnetwork can be customized via optional 'name' and 'range' key-value @@ -555,6 +582,18 @@ FLAGS Kubernetes Engine will use this network when creating routes and firewalls for the clusters. Defaults to the 'default' network. + --node-pool-upgrade-concurrency-config=[max-count=MAX-COUNT] + Configure the concurrency settings for node pool auto upgrades. + + Examples: + + $ gcloud alpha container clusters create-auto example-cluster \ + --node-pool-upgrade-concurrency-config=max-count=10 + + max-count + The maximum number of node pools to upgrade concurrently. The + maximum allowed value is 100. + --private-endpoint-subnetwork=NAME Sets the subnetwork GKE uses to provision the control plane's private endpoint. diff --git a/gcloud/alpha/container/clusters/update b/gcloud/alpha/container/clusters/update index 9e5ffd510..8ce41f91a 100644 --- a/gcloud/alpha/container/clusters/update +++ b/gcloud/alpha/container/clusters/update @@ -15,6 +15,7 @@ SYNOPSIS | --autoscaling-profile=AUTOSCALING_PROFILE | --complete-credential-rotation | --complete-ip-rotation | --containerd-config-from-file=PATH_TO_FILE + | --control-plane-egress=CONTROL_PLANE_EGRESS | --database-encryption-key=DATABASE_ENCRYPTION_KEY | --disable-database-encryption | --disable-default-snat | --disable-multi-nic-lustre | --disable-workload-identity @@ -42,6 +43,7 @@ SYNOPSIS | --in-transit-encryption=IN_TRANSIT_ENCRYPTION | --logging-variant=LOGGING_VARIANT | --maintenance-window=START_TIME | --network-performance-configs=[PROPERTY1=VALUE1,...] + | --node-pool-upgrade-concurrency-config=[max-count=MAX-COUNT] | --notification-config=[pubsub=ENABLED|DISABLED, pubsub-topic=TOPIC,...] | --patch-update=[PATCH_UPDATE] | --private-ipv6-google-access-type=PRIVATE_IPV6_GOOGLE_ACCESS_TYPE @@ -353,6 +355,23 @@ REQUIRED FLAGS Use a full or relative path to a local file containing the value of containerd_config. + --control-plane-egress=CONTROL_PLANE_EGRESS + Configures the egress policy for the GKE control plane to control + outbound traffic from the kube-apiserver. CONTROL_PLANE_EGRESS must + be one of: + + NONE + (Recommended) Provides maximum security. This mode removes the + control plane's public IP address and blocks all outbound traffic + from the kube-apiserver by default, preventing unexpected data + exfiltration. Webhooks that use clientConfig.url will be + disabled. Essential GKE-managed services are still permitted to + function via an internal allowlist. + VIA_CONTROL_PLANE + (Default) Maintains backward compatibility. The control plane + retains its public IP address and allows egress traffic from the + kube-apiserver. + --database-encryption-key=DATABASE_ENCRYPTION_KEY Enable Database Encryption. @@ -697,6 +716,18 @@ REQUIRED FLAGS https://cloud.google.com/compute/docs/networking/configure-vm-with-high-bandwidth-configuration for more information. + --node-pool-upgrade-concurrency-config=[max-count=MAX-COUNT] + Configure the concurrency settings for node pool auto upgrades. + + Examples: + + $ gcloud alpha container clusters update example-cluster \ + --node-pool-upgrade-concurrency-config=max-count=10 + + max-count + The maximum number of node pools to upgrade concurrently. The + maximum allowed value is 100. + --notification-config=[pubsub=ENABLED|DISABLED,pubsub-topic=TOPIC,...] The notification configuration of the cluster. GKE supports publishing cluster upgrade notifications to any Pub/Sub topic you @@ -1686,12 +1717,14 @@ REQUIRED FLAGS Maximum number of cores in the cluster. Maximum number of cores to which the cluster can scale. + Required to be set when --enable-autoprovisioning is used. --max-memory=MAX_MEMORY Maximum memory in the cluster. Maximum number of gigabytes of memory to which the cluster can - scale. + scale. Required to be set when --enable-autoprovisioning is + used. --min-cpu=MIN_CPU Minimum number of cores in the cluster. diff --git a/gcloud/alpha/container/fleet/config-management/describe b/gcloud/alpha/container/fleet/config-management/describe index 1da60d275..1a4271852 100644 --- a/gcloud/alpha/container/fleet/config-management/describe +++ b/gcloud/alpha/container/fleet/config-management/describe @@ -114,7 +114,8 @@ FLAGS order on that field. This flag interacts with other flags that are applied in this order: --flatten, --sort-by, --filter, --limit. - The default table summary sorts by LOCATION then MEMBERSHIP. + The default sort order is by the LOCATION, then MEMBERSHIP table + columns. To sort the table by VERSION instead, run: diff --git a/gcloud/alpha/container/fleet/memberships/get-credentials b/gcloud/alpha/container/fleet/memberships/get-credentials index 27b96eb28..5e10fa95c 100644 --- a/gcloud/alpha/container/fleet/memberships/get-credentials +++ b/gcloud/alpha/container/fleet/memberships/get-credentials @@ -21,6 +21,13 @@ DESCRIPTION Upon success, this command will switch the current context to the target cluster if other contexts are already present in the kubeconfig file. + To force the use of Application Default Credentials (ADC) for + authentication, you can set the + container/use_application_default_credentials property to true: + + $ gcloud config set container/use_application_default_credentials \ + true + EXAMPLES Get the Gateway kubeconfig for a globally registered cluster: diff --git a/gcloud/alpha/container/hub/config-management/describe b/gcloud/alpha/container/hub/config-management/describe index f0ddd3946..461fe5fd7 100644 --- a/gcloud/alpha/container/hub/config-management/describe +++ b/gcloud/alpha/container/hub/config-management/describe @@ -114,7 +114,8 @@ FLAGS order on that field. This flag interacts with other flags that are applied in this order: --flatten, --sort-by, --filter, --limit. - The default table summary sorts by LOCATION then MEMBERSHIP. + The default sort order is by the LOCATION, then MEMBERSHIP table + columns. To sort the table by VERSION instead, run: diff --git a/gcloud/alpha/container/hub/memberships/get-credentials b/gcloud/alpha/container/hub/memberships/get-credentials index 6a9af5044..b4eb1730e 100644 --- a/gcloud/alpha/container/hub/memberships/get-credentials +++ b/gcloud/alpha/container/hub/memberships/get-credentials @@ -20,6 +20,13 @@ DESCRIPTION Upon success, this command will switch the current context to the target cluster if other contexts are already present in the kubeconfig file. + To force the use of Application Default Credentials (ADC) for + authentication, you can set the + container/use_application_default_credentials property to true: + + $ gcloud config set container/use_application_default_credentials \ + true + EXAMPLES Get the Gateway kubeconfig for a globally registered cluster: diff --git a/gcloud/alpha/container/node-pools/create b/gcloud/alpha/container/node-pools/create index a6255b98c..70dd11806 100644 --- a/gcloud/alpha/container/node-pools/create +++ b/gcloud/alpha/container/node-pools/create @@ -45,6 +45,7 @@ SYNOPSIS [--metadata-from-file=KEY=LOCAL_FILE_PATH,[...]] [--min-cpu-platform=PLATFORM] [--network-performance-configs=[PROPERTY=VALUE,...]] + [--node-architecture-taint-behavior=NODE_ARCHITECTURE_TAINT_BEHAVIOR] [--node-group=NODE_GROUP] [--node-labels=[NODE_LABEL,...]] [--node-locations=ZONE,[ZONE,...]] [--node-pool-soak-duration=NODE_POOL_SOAK_DURATION] @@ -64,7 +65,7 @@ SYNOPSIS [--standard-rollout-policy=[batch-node-count=BATCH_NODE_COUNT, batch-percent=BATCH_NODE_PERCENTAGE, batch-soak-duration=BATCH_SOAK_DURATION,...]] - [--storage-pools=STORAGE_POOL,[...]] + [--storage-pools=STORAGE_POOL,[...]] [--subnetwork=SUBNETWORK] [--system-config-from-file=PATH_TO_FILE] [--tags=TAG,[TAG,...]] [--threads-per-core=THREADS_PER_CORE] [--tpu-topology=TPU_TOPOLOGY] [--windows-os-version=WINDOWS_OS_VERSION] @@ -575,6 +576,27 @@ FLAGS external IP destinations. The following tier values are allowed: [TIER_UNSPECIFIED,TIER_1] + --node-architecture-taint-behavior=NODE_ARCHITECTURE_TAINT_BEHAVIOR + Control how architecture taint should be applied to nodes in a new node + pool. + + Supported values: + * unspecified: Default behavior, currently the same as `arm`. + * arm: kubernetes.io/arch=arm:NoSchedule taint will be added for ARM nodes. + * none: No architecture taint will be applied. + + Examples: + + $ gcloud alpha container node-pools create node-pool-1 \ + --cluster=example-cluster \ + --node-architecture-taint-behavior=none + + To read more about node-taints, see + https://cloud.google.com/kubernetes-engine/docs/node-taints. + + NODE_ARCHITECTURE_TAINT_BEHAVIOR must be one of: unspecified, arm, + none. + --node-group=NODE_GROUP Assign instances of this pool to run on the specified Google Compute Engine node group. This is useful for running workloads on sole tenant @@ -849,6 +871,14 @@ FLAGS STORAGE_POOL must be in the format projects/project/zones/zone/storagePools/storagePool + --subnetwork=SUBNETWORK + The subnetwork to use for nodes. This subnetwork must exist in the + cluster's list of additional subnetworks. + + If not specified, the node pool's node IP addresses are allocated from + the least utilized subnet and its secondary range. See details at + https://cloud.google.com/kubernetes-engine/docs/how-to/multi-subnet-clusters#create-node-pool + --system-config-from-file=PATH_TO_FILE Path of the YAML/JSON file that contains the node configuration, including Linux kernel parameters (sysctls) and kubelet configs. @@ -1107,6 +1137,12 @@ FLAGS 'veno', 'westwood', 'yeah'. + net.ipv4.neigh.default.gc_thresh1 Must be between + [0, 262144] + net.ipv4.neigh.default.gc_thresh2 Must be between + [512, 524288] + net.ipv4.neigh.default.gc_thresh3 Must be between + [1024, 1048576] net.netfilter.nf_conntrack_max Must be between [65536, 4194304] net.netfilter.nf_conntrack_buckets Must be between @@ -1122,6 +1158,10 @@ FLAGS net.netfilter.nf_conntrack_tcp_timeout_established Must be between [600, 86400] net.netfilter.nf_conntrack_acct Must be {0, 1} + kernel.keys.maxkeys Must be between + [200, 1048576] + kernel.keys.maxbytes Must be between + [20000, 2097152] kernel.shmmni Must be between [4096, 32768] kernel.shmmax Must be between diff --git a/gcloud/alpha/container/node-pools/update b/gcloud/alpha/container/node-pools/update index 6a17d5b2f..cd3b7a5dd 100644 --- a/gcloud/alpha/container/node-pools/update +++ b/gcloud/alpha/container/node-pools/update @@ -20,6 +20,7 @@ SYNOPSIS | --logging-variant=LOGGING_VARIANT | --max-run-duration=MAX_RUN_DURATION | --network-performance-configs=[PROPERTY=VALUE,...] + | --node-architecture-taint-behavior=NODE_ARCHITECTURE_TAINT_BEHAVIOR | --node-labels=[NODE_LABEL,...] | --node-locations=ZONE,[ZONE,...] | --node-taints=[NODE_TAINT,...] | --resource-manager-tags=[KEY=VALUE,...] @@ -237,6 +238,27 @@ REQUIRED FLAGS external IP destinations. The following tier values are allowed: [TIER_UNSPECIFIED,TIER_1] + --node-architecture-taint-behavior=NODE_ARCHITECTURE_TAINT_BEHAVIOR + Control how architecture taint should be applied to nodes in an + existing node pool. + + Supported values: + * unspecified: Default behavior, currently the same as `arm`. + * arm: kubernetes.io/arch=arm:NoSchedule taint will be added for ARM nodes. + * none: No architecture taint will be applied. + + Examples: + + $ gcloud alpha container node-pools update node-pool-1 \ + --cluster=example-cluster \ + --node-architecture-taint-behavior=none + + To read more about node-taints, see + https://cloud.google.com/kubernetes-engine/docs/node-taints. + + NODE_ARCHITECTURE_TAINT_BEHAVIOR must be one of: unspecified, arm, + none. + --node-labels=[NODE_LABEL,...] Replaces all the user specified Kubernetes labels on all nodes in an existing node pool with the given labels. @@ -595,6 +617,12 @@ REQUIRED FLAGS 'veno', 'westwood', 'yeah'. + net.ipv4.neigh.default.gc_thresh1 Must be between + [0, 262144] + net.ipv4.neigh.default.gc_thresh2 Must be between + [512, 524288] + net.ipv4.neigh.default.gc_thresh3 Must be between + [1024, 1048576] net.netfilter.nf_conntrack_max Must be between [65536, 4194304] net.netfilter.nf_conntrack_buckets Must be between @@ -612,6 +640,10 @@ REQUIRED FLAGS net.netfilter.nf_conntrack_tcp_timeout_established Must be between [600, 86400] net.netfilter.nf_conntrack_acct Must be {0, 1} + kernel.keys.maxkeys Must be between + [200, 1048576] + kernel.keys.maxbytes Must be between + [20000, 2097152] kernel.shmmni Must be between [4096, 32768] kernel.shmmax Must be between diff --git a/gcloud/alpha/dataplex/context/help b/gcloud/alpha/dataplex/context/help index df646aaa4..510b9115e 100644 --- a/gcloud/alpha/dataplex/context/help +++ b/gcloud/alpha/dataplex/context/help @@ -16,7 +16,7 @@ COMMANDS COMMAND is one of the following: lookup - (ALPHA) Looks up LLM context for data assets. + (ALPHA) Looks up metadata that can be used as context by agents. NOTES This command is currently in alpha and might change without notice. If this diff --git a/gcloud/alpha/dataplex/context/lookup b/gcloud/alpha/dataplex/context/lookup index 6d7846e88..27e40aa3f 100644 --- a/gcloud/alpha/dataplex/context/lookup +++ b/gcloud/alpha/dataplex/context/lookup @@ -1,20 +1,22 @@ NAME - gcloud alpha dataplex context lookup - looks up LLM context for data assets + gcloud alpha dataplex context lookup - looks up metadata that can be used + as context by agents SYNOPSIS gcloud alpha dataplex context lookup --resources=[RESOURCES,...] - [--location=LOCATION] [GCLOUD_WIDE_FLAG ...] + [--context-format=CONTEXT_FORMAT; default="yaml"] [--location=LOCATION] + [--options=OPTIONS] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) Looks up LLM context for data assets. + (ALPHA) Looks up metadata that can be used as context by agents. Fetches detailed contextual metadata for the specified data assets. Data - assets can be identified by their Dataplex entry name, source system - resource name or fully qualified name. The returned context can include - schema, descriptions, business annotations, data quality insights, and - relationships, structured for application use. This output is particularly - useful for providing grounding to Large Language Models (LLMs), enabling - more accurate and context-aware interactions with your data. + assets can be identified by their Dataplex entry name. The returned context + can include schema, descriptions, business annotations, data quality + insights, and relationships, structured for application use. This output is + particularly useful for providing grounding to Large Language Models + (LLMs), enabling more accurate and context-aware interactions with your + data. EXAMPLES To look up Dataplex Context for BigQuery tables 'table1' and 'table2' in @@ -39,14 +41,14 @@ EXAMPLES REQUIRED FLAGS --resources=[RESOURCES,...] - The identifier describing the resource, - ◆ in the form of a entry name, or - ◆ in the form of a linked resource name, or - ◆ in the form of a fully qualified name. Examples: - ◆ projects/{project}/locations/{location}/entryGroups/{entry_group}/entries/{entry} - ◆ bigquery:{project}.{dataset}.{table} + The identifier describing the resource, for example: + projects/{project}/locations/{location}/entryGroups/{entry_group}/entries/{entry} OPTIONAL FLAGS + --context-format=CONTEXT_FORMAT; default="yaml" + The output format of the command. CONTEXT_FORMAT must be one of: json, + xml, yaml. + Location resource - The Dataplex location for the context lookup. If not specified, the location will be taken from the dataplex/location property in your gcloud configuration. This represents a Cloud resource. (NOTE) @@ -67,6 +69,10 @@ OPTIONAL FLAGS ◆ provide the argument --location on the command line; ◆ set the property dataplex/location. + --options=OPTIONS + Additional options for the command. This can be provided as a JSON + string. Example: --options='{"key": "value"}' + 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/dataplex/data-attribute-bindings/add-iam-policy-binding b/gcloud/alpha/dataplex/data-attribute-bindings/add-iam-policy-binding deleted file mode 100644 index f120e5c77..000000000 --- a/gcloud/alpha/dataplex/data-attribute-bindings/add-iam-policy-binding +++ /dev/null @@ -1,93 +0,0 @@ -NAME - gcloud alpha dataplex data-attribute-bindings add-iam-policy-binding - add - IAM policy binding to a Dataplex Data Attribute Binding - -SYNOPSIS - gcloud alpha dataplex data-attribute-bindings add-iam-policy-binding - (DATA_ATTRIBUTE_BINDING : --location=LOCATION) --member=PRINCIPAL - --role=ROLE [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (ALPHA) Add IAM policy binding to a Dataplex Data Attribute Binding. - -EXAMPLES - To add an IAM policy binding for the role of roles/dataplex.viewer for the - user test-user@gmail.com to Data Attribute Binding test-attribute-binding - in location us-central, run: - - $ gcloud alpha dataplex data-attribute-bindings \ - add-iam-policy-binding test-attribute-binding \ - --project=test-project --location=us-central1 \ - --role=roles/dataplex.viewer --member=user:foo@gmail.com - - See https://cloud.google.com/dataplex/docs/iam-roles for details of policy - role and member types. - -POSITIONAL ARGUMENTS - Data attribute binding resource - The DataAttributeBinding to add IAM - policy binding to. 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_attribute_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. - - DATA_ATTRIBUTE_BINDING - ID of the data attribute binding or fully qualified identifier for - the data attribute binding. - - To set the data_attribute_binding attribute: - ▸ provide the argument data_attribute_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 of the Dataplex resource. - - To set the location attribute: - ▸ provide the argument data_attribute_binding on the command line - with a fully specified name; - ▸ provide the argument --location on the command line; - ▸ set the property dataplex/location. - -REQUIRED FLAGS - --member=PRINCIPAL - The principal to add the binding for. Should be of the form - user|group|serviceAccount:email or domain:domain. - - Examples: user:test-user@gmail.com, group:admins@example.com, - serviceAccount:test123@example.domain.com, or - domain:example.domain.com. - - Some resources also accept the following special values: - ◆ allUsers - Special identifier that represents anyone who is on the - internet, with or without a Google account. - ◆ allAuthenticatedUsers - Special identifier that represents anyone - who is authenticated with a Google account or a service account. - - --role=ROLE - Role name to assign to the principal. The role name is the complete - path of a predefined role, such as roles/logging.viewer, or the role ID - for a custom role, such as - organizations/{ORGANIZATION_ID}/roles/logging.viewer. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --configuration, --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/dataplex/data-attribute-bindings/create b/gcloud/alpha/dataplex/data-attribute-bindings/create deleted file mode 100644 index ea2858442..000000000 --- a/gcloud/alpha/dataplex/data-attribute-bindings/create +++ /dev/null @@ -1,131 +0,0 @@ -NAME - gcloud alpha dataplex data-attribute-bindings create - create a Dataplex - Data Attribute Binding - -SYNOPSIS - gcloud alpha dataplex data-attribute-bindings create - (DATA_ATTRIBUTE_BINDING : --location=LOCATION) - [--description=DESCRIPTION] [--display-name=DISPLAY_NAME] - [--labels=[KEY=VALUE,...]] [--path-file-format=PATH_FILE_FORMAT] - [--resource=RESOURCE] [--resource-attributes=[ATTRIBUTES,...]] - [--async | --validate-only] - [--path-file-name=PATH_FILE_NAME | --paths=[PATH,...]] - [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (ALPHA) Create a Dataplex Data Attribute Binding. - -EXAMPLES - To create Data Attribute Binding test-attribute-binding in project - test-dataplex at location us-central1 with resouce name 'testResource' and - resource attributes a1 and a2. Test column 'testColumn1' attached to - attribute 'a1' and 'testColumn2' attached to attribute 'a2' , run: - - $ gcloud alpha dataplex data-attribute-bindings create \ - test-attribute-binding --project=test-dataplex \ - --location=us-central1 \ - --resource='projects/test-dataplex/locations/us-central1/lakes/m\ - y-lake/zones/test-zone/entities/testResource' \ - --resource-attributes='a1,a2' \ - --paths=name=testColumn1,attributes=a1 \ - --paths=name=testColumn2,attributes=a2 - -POSITIONAL ARGUMENTS - Data attribute binding resource - The DataAttributeBinding 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 data_attribute_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. - - DATA_ATTRIBUTE_BINDING - ID of the data attribute binding or fully qualified identifier for - the data attribute binding. - - To set the data_attribute_binding attribute: - ▸ provide the argument data_attribute_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 of the Dataplex resource. - - To set the location attribute: - ▸ provide the argument data_attribute_binding on the command line - with a fully specified name; - ▸ provide the argument --location on the command line; - ▸ set the property dataplex/location. - -FLAGS - --description=DESCRIPTION - Description of the Data Attribute Binding. - - --display-name=DISPLAY_NAME - Display Name of the Data Attribute Binding. - - --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. - - --path-file-format=PATH_FILE_FORMAT - The format of the file to create the path. Specify either yaml or json. - Defaults to json if not specified. Will be ignored if --file-name is - not specified. PATH_FILE_FORMAT must be one of: json, yaml. - - --resource=RESOURCE - The resource name of the resource that is binded to Data Attribute. - - --resource-attributes=[ATTRIBUTES,...] - List of attributes to be associated with the resource. It should be - fully qualified attribute name - - At most one of these can be specified: - - --async - Return immediately, without waiting for the operation in progress to - complete. - - --validate-only - Validate the create action, but don't actually perform it. - - Creation options. - - At most one of these can be specified: - - --path-file-name=PATH_FILE_NAME - The name of the JSON or YAML file to define Path config from. - - --paths=[PATH,...] - The list of paths for items within the associated resource (eg. - columns within a table) along with attribute bindings. The args can - be passed as key value pair. Supported Keys are - --path=name=value1,attributes=value2 ,See - https://cloud.google.com/sdk/gcloud/reference/topic/escaping for - details on using a delimiter other than a comma. Attribute name - should be fully qualified attribute name. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --configuration, --flags-file, --flatten, --format, - --help, --impersonate-service-account, --log-http, --project, --quiet, - --trace-token, --user-output-enabled, --verbosity. - - Run $ gcloud help for details. - -NOTES - This command is currently in alpha and might change without notice. If this - command fails 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/dataplex/data-attribute-bindings/delete b/gcloud/alpha/dataplex/data-attribute-bindings/delete deleted file mode 100644 index 139597c24..000000000 --- a/gcloud/alpha/dataplex/data-attribute-bindings/delete +++ /dev/null @@ -1,79 +0,0 @@ -NAME - gcloud alpha dataplex data-attribute-bindings delete - delete a Dataplex - Data Attribute Binding - -SYNOPSIS - gcloud alpha dataplex data-attribute-bindings delete - (DATA_ATTRIBUTE_BINDING : --location=LOCATION) --etag=ETAG [--async] - [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (ALPHA) Delete a Dataplex Data Attribute Binding. - -EXAMPLES - To Delete Data Attribute Binding test-attribute-binding in project - test-dataplex at location us-central1, run: - - $gcloud alpha dataplex data-attribute-bindings delete test-attribute-binding --project=test-dataplex --location=us-central1 - -POSITIONAL ARGUMENTS - Data attribute binding resource - Arguments and flags that define the - Dataplex Attribute Binding you want to delete. The arguments in this group - can be used to specify the attributes of this resource. (NOTE) Some - attributes are not given arguments in this group but can be set in other - ways. - - To set the project attribute: - ◆ provide the argument data_attribute_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. - - DATA_ATTRIBUTE_BINDING - ID of the data attribute binding or fully qualified identifier for - the data attribute binding. - - To set the data_attribute_binding attribute: - ▸ provide the argument data_attribute_binding on the command line. - - This positional argument must be specified if any of the other - arguments in this group are specified. - - --location=LOCATION - Location of the Dataplex resource. - - To set the location attribute: - ▸ provide the argument data_attribute_binding on the command line - with a fully specified name; - ▸ provide the argument --location on the command line; - ▸ set the property dataplex/location. - -REQUIRED FLAGS - --etag=ETAG - etag value for particular Data Attribute Binding. - -OPTIONAL FLAGS - --async - Return immediately, without waiting for the operation in progress to - complete. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --configuration, --flags-file, --flatten, --format, - --help, --impersonate-service-account, --log-http, --project, --quiet, - --trace-token, --user-output-enabled, --verbosity. - - Run $ gcloud help for details. - -API REFERENCE - This command uses the dataplex/v1 API. The full documentation for this API - can be found at: https://cloud.google.com/dataplex/docs - -NOTES - This command is currently in alpha and might change without notice. If this - command fails with API permission errors despite specifying the correct - project, you might be trying to access an API with an invitation-only early - access allowlist. - diff --git a/gcloud/alpha/dataplex/data-attribute-bindings/describe b/gcloud/alpha/dataplex/data-attribute-bindings/describe deleted file mode 100644 index 24c584c2f..000000000 --- a/gcloud/alpha/dataplex/data-attribute-bindings/describe +++ /dev/null @@ -1,69 +0,0 @@ -NAME - gcloud alpha dataplex data-attribute-bindings describe - describe a Data - Attribute Binding resource - -SYNOPSIS - gcloud alpha dataplex data-attribute-bindings describe - (DATA_ATTRIBUTE_BINDING : --location=LOCATION) [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (ALPHA) Describe a Data Attribute Binding resource. Displays all details of - a Data Attribute Binding resource given a valid DataAttributeBindingID. - -EXAMPLES - To Describe Data Attribute Binding test-attribute-binding in project - test-dataplex at location us-central1, run: - - $gcloud alpha dataplex data-attribute-bindings describe test-attribute-binding --project=test-dataplex --location=us-central1 - -POSITIONAL ARGUMENTS - Data attribute binding resource - Data Attribute Binding you want to - describe. The arguments in this group can be used to specify the - attributes of this resource. (NOTE) Some attributes are not given - arguments in this group but can be set in other ways. - - To set the project attribute: - ◆ provide the argument data_attribute_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. - - DATA_ATTRIBUTE_BINDING - ID of the data attribute binding or fully qualified identifier for - the data attribute binding. - - To set the data_attribute_binding attribute: - ▸ provide the argument data_attribute_binding on the command line. - - This positional argument must be specified if any of the other - arguments in this group are specified. - - --location=LOCATION - Location of the Dataplex resource. - - To set the location attribute: - ▸ provide the argument data_attribute_binding on the command line - with a fully specified name; - ▸ provide the argument --location on the command line; - ▸ set the property dataplex/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 dataplex/v1 API. The full documentation for this API - can be found at: https://cloud.google.com/dataplex/docs - -NOTES - This command is currently in alpha and might change without notice. If this - command fails with API permission errors despite specifying the correct - project, you might be trying to access an API with an invitation-only early - access allowlist. - diff --git a/gcloud/alpha/dataplex/data-attribute-bindings/help b/gcloud/alpha/dataplex/data-attribute-bindings/help deleted file mode 100644 index f83198c3a..000000000 --- a/gcloud/alpha/dataplex/data-attribute-bindings/help +++ /dev/null @@ -1,54 +0,0 @@ -NAME - gcloud alpha dataplex data-attribute-bindings - manage Dataplex Data - Attribute Bindings - -SYNOPSIS - gcloud alpha dataplex data-attribute-bindings COMMAND - [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (ALPHA) Manage Dataplex Data Attribute Bindings. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --help. - - Run $ gcloud help for details. - -COMMANDS - COMMAND is one of the following: - - add-iam-policy-binding - (ALPHA) Add IAM policy binding to a Dataplex Data Attribute Binding. - - create - (ALPHA) Create a Dataplex Data Attribute Binding. - - delete - (ALPHA) Delete a Dataplex Data Attribute Binding. - - describe - (ALPHA) Describe a Data Attribute Binding resource. - - get-iam-policy - (ALPHA) Retrieve a Dataplex Data Attribute Binding IAM policy. - - list - (ALPHA) List Data Attribute Bindings. - - remove-iam-policy-binding - (ALPHA) Removes IAM policy binding from a Dataplex Data Attribute - Binding. - - set-iam-policy - (ALPHA) Set an IAM policy binding for a Dataplex Data Attribute Binding - as defined in a JSON or YAML file. - - update - (ALPHA) Update a Dataplex Data Attribute Binding. - -NOTES - This command is currently in alpha and might change without notice. If this - command fails 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/dataplex/data-attribute-bindings/remove-iam-policy-binding b/gcloud/alpha/dataplex/data-attribute-bindings/remove-iam-policy-binding deleted file mode 100644 index 498a263f0..000000000 --- a/gcloud/alpha/dataplex/data-attribute-bindings/remove-iam-policy-binding +++ /dev/null @@ -1,95 +0,0 @@ -NAME - gcloud alpha dataplex data-attribute-bindings remove-iam-policy-binding - - removes IAM policy binding from a Dataplex Data Attribute Binding - -SYNOPSIS - gcloud alpha dataplex data-attribute-bindings remove-iam-policy-binding - (DATA_ATTRIBUTE_BINDING : --location=LOCATION) --member=PRINCIPAL - --role=ROLE [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (ALPHA) Removes IAM policy binding from a Dataplex Data Attribute Binding. - -EXAMPLES - To remove an IAM policy binding for the role roles/dataplex.viewer for the - user testuser@gmail.com from an Data Attribute Binding - test-attribute-binding within projet test-project in location us-central1, - run: - - $ gcloud alpha dataplex data-attribute-bindings \ - remove-iam-policy-binding test-attribute-binding \ - --project=test-project --location=us-central1 \ - --role=roles/dataplex.viewer --member=user:testuser@gmail.com - - See https://cloud.google.com/dataplex/docs/iam-roles for details of policy - role and member types. - -POSITIONAL ARGUMENTS - Data attribute binding resource - The DataAttributeBinding to remove IAM - policy binding from 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_attribute_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. - - DATA_ATTRIBUTE_BINDING - ID of the data attribute binding or fully qualified identifier for - the data attribute binding. - - To set the data_attribute_binding attribute: - ▸ provide the argument data_attribute_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 of the Dataplex resource. - - To set the location attribute: - ▸ provide the argument data_attribute_binding on the command line - with a fully specified name; - ▸ provide the argument --location on the command line; - ▸ set the property dataplex/location. - -REQUIRED FLAGS - --member=PRINCIPAL - The principal to remove the binding for. Should be of the form - user|group|serviceAccount:email or domain:domain. - - Examples: user:test-user@gmail.com, group:admins@example.com, - serviceAccount:test123@example.domain.com, or - domain:example.domain.com. - - Deleted principals have an additional deleted: prefix and a ?uid=UID - suffix, where UID is a unique identifier for the principal. Example: - deleted:user:test-user@gmail.com?uid=123456789012345678901. - - Some resources also accept the following special values: - ◆ allUsers - Special identifier that represents anyone who is on the - internet, with or without a Google account. - ◆ allAuthenticatedUsers - Special identifier that represents anyone - who is authenticated with a Google account or a service account. - - --role=ROLE - The role to remove the principal from. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --configuration, --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/dataplex/data-attribute-bindings/set-iam-policy b/gcloud/alpha/dataplex/data-attribute-bindings/set-iam-policy deleted file mode 100644 index e9fe3101b..000000000 --- a/gcloud/alpha/dataplex/data-attribute-bindings/set-iam-policy +++ /dev/null @@ -1,79 +0,0 @@ -NAME - gcloud alpha dataplex data-attribute-bindings set-iam-policy - set an IAM - policy binding for a Dataplex Data Attribute Binding as defined in a - JSON or YAML file - -SYNOPSIS - gcloud alpha dataplex data-attribute-bindings set-iam-policy - (DATA_ATTRIBUTE_BINDING : --location=LOCATION) POLICY_FILE - [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (ALPHA) See https://cloud.google.com/iam/docs/managing-policies for details - of the policy file format and contents. - -EXAMPLES - The following command will read an IAM policy defined in a JSON file - policy.json and set it for the Dataplex Data Attribute Binding - test-attribute-binding within project test-project in location us-central1: - - $ gcloud alpha dataplex data-attribute-bindings set-iam-policy \ - test-attribute-binding --project=test-project \ - --location=us-central1 policy.json - - where policy.json is the relative path to the json file. - -POSITIONAL ARGUMENTS - Data attribute binding resource - The DataAttributeBinding to set IAM - policy to. 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_attribute_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. - - DATA_ATTRIBUTE_BINDING - ID of the data attribute binding or fully qualified identifier for - the data attribute binding. - - To set the data_attribute_binding attribute: - ▸ provide the argument data_attribute_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 of the Dataplex resource. - - To set the location attribute: - ▸ provide the argument data_attribute_binding on the command line - with a fully specified name; - ▸ provide the argument --location on the command line; - ▸ set the property dataplex/location. - - POLICY_FILE - Path to a local JSON or YAML formatted file containing a valid policy. - - The output of the get-iam-policy command is a valid file, as is any - JSON or YAML file conforming to the structure of a Policy - (https://cloud.google.com/iam/reference/rest/v1/Policy). - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --configuration, --flags-file, --flatten, --format, - --help, --impersonate-service-account, --log-http, --project, --quiet, - --trace-token, --user-output-enabled, --verbosity. - - Run $ gcloud help for details. - -NOTES - This command is currently in alpha and might change without notice. If this - command fails with API permission errors despite specifying the correct - project, you might be trying to access an API with an invitation-only early - access allowlist. - diff --git a/gcloud/alpha/dataplex/data-attribute-bindings/update b/gcloud/alpha/dataplex/data-attribute-bindings/update deleted file mode 100644 index 46d5285ae..000000000 --- a/gcloud/alpha/dataplex/data-attribute-bindings/update +++ /dev/null @@ -1,127 +0,0 @@ -NAME - gcloud alpha dataplex data-attribute-bindings update - update a Dataplex - Data Attribute Binding - -SYNOPSIS - gcloud alpha dataplex data-attribute-bindings update - (DATA_ATTRIBUTE_BINDING : --location=LOCATION) --etag=ETAG - [--description=DESCRIPTION] [--display-name=DISPLAY_NAME] - [--labels=[KEY=VALUE,...]] [--path-file-format=PATH_FILE_FORMAT] - [--resource-attributes=[ATTRIBUTES,...]] [--async | --validate-only] - [--path-file-name=PATH_FILE_NAME | --paths=[PATH,...]] - [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (ALPHA) Update a Dataplex Data Attribute Binding. - -EXAMPLES - To Update Data Attribute Binding test-attribute-binding in project - test-dataplex at location us-central1 with resource attributes a1 and a2. - Test column 'testColumn1' attached to attribute 'a1' and 'testColumn2' - attached to attribute 'a2' , run: - - $ gcloud alpha dataplex data-attribute-bindings update \ - test-attribute-binding --project=test-dataplex \ - --location=us-central1 --resource-attributes='a1,a2' \ - --paths=name=testColumn1,attributes=a1 \ - --paths=name=testColumn2,attributes=a2 \ - --etag=Etag_Received_From_Get - -POSITIONAL ARGUMENTS - Data attribute binding resource - The DataAttributeBinding 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 data_attribute_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. - - DATA_ATTRIBUTE_BINDING - ID of the data attribute binding or fully qualified identifier for - the data attribute binding. - - To set the data_attribute_binding attribute: - ▸ provide the argument data_attribute_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 of the Dataplex resource. - - To set the location attribute: - ▸ provide the argument data_attribute_binding on the command line - with a fully specified name; - ▸ provide the argument --location on the command line; - ▸ set the property dataplex/location. - -REQUIRED FLAGS - --etag=ETAG - etag value of the Data Attribute Binding resource. - -OPTIONAL FLAGS - --description=DESCRIPTION - Description of the Data Attribute Binding. - - --display-name=DISPLAY_NAME - Display Name of the Data Attribute Binding. - - --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. - - --path-file-format=PATH_FILE_FORMAT - The format of the file to create the path. Specify either yaml or json. - Defaults to yaml if not specified. Will be ignored if --file-name is - not specified. PATH_FILE_FORMAT must be one of: json, yaml. - - --resource-attributes=[ATTRIBUTES,...] - List of Data Attributes to be associated with the resource - - At most one of these can be specified: - - --async - Return immediately, without waiting for the operation in progress to - complete. - - --validate-only - Validate the update action, but don't actually perform it. - - Creation options. - - At most one of these can be specified: - - --path-file-name=PATH_FILE_NAME - The name of the JSON or YAML file to define Path config from. - - --paths=[PATH,...] - The list of paths for items within the associated resource (eg. - columns within a table) along with attribute bindings. The args can - be passed as key value pair. Supported Keys are - --path=name=value1,attributes=value2 ,See - https://cloud.google.com/sdk/gcloud/reference/topic/escaping for - details on using a delimiter other than a comma. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --configuration, --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/dataplex/data-taxonomies/attributes/add-iam-policy-binding b/gcloud/alpha/dataplex/data-taxonomies/attributes/add-iam-policy-binding deleted file mode 100644 index c1d9a47e4..000000000 --- a/gcloud/alpha/dataplex/data-taxonomies/attributes/add-iam-policy-binding +++ /dev/null @@ -1,101 +0,0 @@ -NAME - gcloud alpha dataplex data-taxonomies attributes add-iam-policy-binding - - add IAM policy binding to a Dataplex Data Attribute - -SYNOPSIS - gcloud alpha dataplex data-taxonomies attributes add-iam-policy-binding - (DATA_ATTRIBUTE : --data_taxonomy=DATA_TAXONOMY --location=LOCATION) - --member=PRINCIPAL --role=ROLE [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (ALPHA) Add IAM policy binding to a Dataplex Data Attribute. - -EXAMPLES - To add an IAM policy binding for the role of roles/dataplex.viewer for the - user test-user@gmail.com to Data Attribute test-attribute in location - us-central, in Data Taxonomy 'test-taxonomy', run: - - $ gcloud alpha dataplex data-taxonomies attributes \ - add-iam-policy-binding test-attribute --project=test-project \ - --location=us-central1 --data_taxonomy=test-datataxonomy \ - --role=roles/dataplex.viewer --member=user:foo@gmail.com - - See https://cloud.google.com/dataplex/docs/iam-roles for details of policy - role and member types. - -POSITIONAL ARGUMENTS - Data attribute resource - The DataAttribute to add IAM policy binding to. - 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_attribute 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_ATTRIBUTE - ID of the data attribute or fully qualified identifier for the data - attribute. - - To set the data_attribute attribute: - ▸ provide the argument data_attribute on the command line. - - This positional argument must be specified if any of the other - arguments in this group are specified. - - --data_taxonomy=DATA_TAXONOMY - The name of data attribute to use. - - To set the data_taxonomy attribute: - ▸ provide the argument data_attribute on the command line with a - fully specified name; - ▸ provide the argument --data_taxonomy on the command line. - - --location=LOCATION - The location of the Dataplex resource. - - To set the location attribute: - ▸ provide the argument data_attribute on the command line with a - fully specified name; - ▸ provide the argument --location on the command line; - ▸ set the property dataplex/location. - -REQUIRED FLAGS - --member=PRINCIPAL - The principal to add the binding for. Should be of the form - user|group|serviceAccount:email or domain:domain. - - Examples: user:test-user@gmail.com, group:admins@example.com, - serviceAccount:test123@example.domain.com, or - domain:example.domain.com. - - Some resources also accept the following special values: - ◆ allUsers - Special identifier that represents anyone who is on the - internet, with or without a Google account. - ◆ allAuthenticatedUsers - Special identifier that represents anyone - who is authenticated with a Google account or a service account. - - --role=ROLE - Role name to assign to the principal. The role name is the complete - path of a predefined role, such as roles/logging.viewer, or the role ID - for a custom role, such as - organizations/{ORGANIZATION_ID}/roles/logging.viewer. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --configuration, --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/dataplex/data-taxonomies/attributes/create b/gcloud/alpha/dataplex/data-taxonomies/attributes/create deleted file mode 100644 index 201d926bf..000000000 --- a/gcloud/alpha/dataplex/data-taxonomies/attributes/create +++ /dev/null @@ -1,138 +0,0 @@ -NAME - gcloud alpha dataplex data-taxonomies attributes create - create a Dataplex - Data Attribute - -SYNOPSIS - gcloud alpha dataplex data-taxonomies attributes create - (DATA_ATTRIBUTE : --data_taxonomy=DATA_TAXONOMY --location=LOCATION) - [--data-readers=[DATA_READERS,...]] [--description=DESCRIPTION] - [--display-name=DISPLAY_NAME] [--labels=[KEY=VALUE,...]] - [--parent=PARENT] [--async | --validate-only] - [--resource-owners=[RESOURCE_OWNERS,...] - --resource-readers=[RESOURCE_READERS,...] - --resource-writers=[RESOURCE_WRITERS,...]] [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (ALPHA) Create a Dataplex Data Attribute. - -EXAMPLES - To create Data Attribute test-attribute for Data Taxonomy test-datataxonomy - in project test-dataplex at location us-central1 with description as test - description , display name as displayName, resource-readers as - user:test@google.com, resource-writers as user:test@google.com, - resource-owner as user:test@google.com, data-readers as - user:test@google.com and parent as test-attribute-parent, run: - - $ gcloud alpha dataplex data-taxonomies attributes create \ - test-attribute-6 --location=us-central1 --project=test-dataplex' - --data_taxonomy=test-datataxonomy --description='test description' - --display-name='displayName' --resource-readers='user:test@google.com' - --resource-writers='user:test@google.com' --resource-owners='user:test@google.com' - --data-readers='user:test@google.com' - --parent='test-attribute-parent' - -POSITIONAL ARGUMENTS - Data attribute resource - The DataAttribute 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 data_attribute 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_ATTRIBUTE - ID of the data attribute or fully qualified identifier for the data - attribute. - - To set the data_attribute attribute: - ▸ provide the argument data_attribute on the command line. - - This positional argument must be specified if any of the other - arguments in this group are specified. - - --data_taxonomy=DATA_TAXONOMY - The name of data attribute to use. - - To set the data_taxonomy attribute: - ▸ provide the argument data_attribute on the command line with a - fully specified name; - ▸ provide the argument --data_taxonomy on the command line. - - --location=LOCATION - The location of the Dataplex resource. - - To set the location attribute: - ▸ provide the argument data_attribute on the command line with a - fully specified name; - ▸ provide the argument --location on the command line; - ▸ set the property dataplex/location. - -FLAGS - Specified when applied to data stored on the resource (eg: rows,columns in - BigQuery Tables). - - --data-readers=[DATA_READERS,...] - The set of principals to be granted reader role on the resource. - Expected principal formats are user:$userEmail, group:$groupEmail - - --description=DESCRIPTION - Description of the Data Attribute. - - --display-name=DISPLAY_NAME - Display Name of the Data Attribute. - - --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. - - --parent=PARENT - Parent Data Attribute for the created Data Attribute. It can be - attribute name or fully qualified attribute name. - - At most one of these can be specified: - - --async - Return immediately, without waiting for the operation in progress to - complete. - - --validate-only - Validate the create action, but don't actually perform it. - - Spec related to Dataplex Resource.Specified when applied to a resource - (eg: Google Cloud Storage bucket, BigQuery, dataset, BigQuery table). - - --resource-owners=[RESOURCE_OWNERS,...] - The set of principals to be granted owner role on the resource. - Expected principal formats are user:$userEmail, group:$groupEmail - - --resource-readers=[RESOURCE_READERS,...] - The set of principals to be granted reader role on the resource. - Expected principal formats are user:$userEmail, group:$groupEmail - - --resource-writers=[RESOURCE_WRITERS,...] - The set of principals to be granted writer role on the resource. - Expected principal formats are user:$userEmail, group:$groupEmail - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --configuration, --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/dataplex/data-taxonomies/attributes/delete b/gcloud/alpha/dataplex/data-taxonomies/attributes/delete deleted file mode 100644 index 08cbbe966..000000000 --- a/gcloud/alpha/dataplex/data-taxonomies/attributes/delete +++ /dev/null @@ -1,87 +0,0 @@ -NAME - gcloud alpha dataplex data-taxonomies attributes delete - delete a Dataplex - Data Attribute - -SYNOPSIS - gcloud alpha dataplex data-taxonomies attributes delete - (DATA_ATTRIBUTE : --data_taxonomy=DATA_TAXONOMY --location=LOCATION) - [--async] [--etag=ETAG] [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (ALPHA) Delete a Dataplex Data Attribute. - -EXAMPLES - To delete Data Attribute test-attribute for Data Taxonomy test-datataxonomy - in project test-dataplex at location us-central1, run: - - $ gcloud alpha dataplex data-taxonomies attributes delete \ - test-attribute --location=us-central1 --project=test-dataplex \ - --data_taxonomy=test-datataxonomy - -POSITIONAL ARGUMENTS - Data attribute resource - Arguments and flags that define the Dataplex - Data Attribute you want to delete. The arguments in this group can be used - to specify the attributes of this resource. (NOTE) Some attributes are not - given arguments in this group but can be set in other ways. - - To set the project attribute: - ◆ provide the argument data_attribute 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_ATTRIBUTE - ID of the data attribute or fully qualified identifier for the data - attribute. - - To set the data_attribute attribute: - ▸ provide the argument data_attribute on the command line. - - This positional argument must be specified if any of the other - arguments in this group are specified. - - --data_taxonomy=DATA_TAXONOMY - Identifier of the Dataplex DataTaxonomy resource. - - To set the data_taxonomy attribute: - ▸ provide the argument data_attribute on the command line with a - fully specified name; - ▸ provide the argument --data_taxonomy on the command line. - - --location=LOCATION - Location of the Dataplex resource. - - To set the location attribute: - ▸ provide the argument data_attribute on the command line with a - fully specified name; - ▸ provide the argument --location on the command line; - ▸ set the property dataplex/location. - -FLAGS - --async - Return immediately, without waiting for the operation in progress to - complete. - - --etag=ETAG - etag value for particular Data Attribute resource. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --configuration, --flags-file, --flatten, --format, - --help, --impersonate-service-account, --log-http, --project, --quiet, - --trace-token, --user-output-enabled, --verbosity. - - Run $ gcloud help for details. - -API REFERENCE - This command uses the dataplex/v1 API. The full documentation for this API - can be found at: https://cloud.google.com/dataplex/docs - -NOTES - This command is currently in alpha and might change without notice. If this - command fails with API permission errors despite specifying the correct - project, you might be trying to access an API with an invitation-only early - access allowlist. - diff --git a/gcloud/alpha/dataplex/data-taxonomies/attributes/describe b/gcloud/alpha/dataplex/data-taxonomies/attributes/describe deleted file mode 100644 index c60657710..000000000 --- a/gcloud/alpha/dataplex/data-taxonomies/attributes/describe +++ /dev/null @@ -1,79 +0,0 @@ -NAME - gcloud alpha dataplex data-taxonomies attributes describe - describe a - Dataplex Data Attribute - -SYNOPSIS - gcloud alpha dataplex data-taxonomies attributes describe - (DATA_ATTRIBUTE : --data_taxonomy=DATA_TAXONOMY --location=LOCATION) - [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (ALPHA) Describe a Dataplex Data Attribute. - -EXAMPLES - To Describe Data Attribute test-attribute for Data Taxonomy - test-datataxonomy in project test-dataplex at location us-central1, run: - - $ gcloud alpha dataplex data-taxonomies attributes describe \ - test-attribute --location=us-central1 --project=test-dataplex \ - --data_taxonomy=test-datataxonomy - -POSITIONAL ARGUMENTS - Data attribute resource - DataAttribute 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 data_attribute 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_ATTRIBUTE - ID of the data attribute or fully qualified identifier for the data - attribute. - - To set the data_attribute attribute: - ▸ provide the argument data_attribute on the command line. - - This positional argument must be specified if any of the other - arguments in this group are specified. - - --data_taxonomy=DATA_TAXONOMY - Identifier of the Dataplex DataTaxonomy resource. - - To set the data_taxonomy attribute: - ▸ provide the argument data_attribute on the command line with a - fully specified name; - ▸ provide the argument --data_taxonomy on the command line. - - --location=LOCATION - Location of the Dataplex resource. - - To set the location attribute: - ▸ provide the argument data_attribute on the command line with a - fully specified name; - ▸ provide the argument --location on the command line; - ▸ set the property dataplex/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 dataplex/v1 API. The full documentation for this API - can be found at: https://cloud.google.com/dataplex/docs - -NOTES - This command is currently in alpha and might change without notice. If this - command fails with API permission errors despite specifying the correct - project, you might be trying to access an API with an invitation-only early - access allowlist. - diff --git a/gcloud/alpha/dataplex/data-taxonomies/attributes/get-iam-policy b/gcloud/alpha/dataplex/data-taxonomies/attributes/get-iam-policy deleted file mode 100644 index 2855435b0..000000000 --- a/gcloud/alpha/dataplex/data-taxonomies/attributes/get-iam-policy +++ /dev/null @@ -1,112 +0,0 @@ -NAME - gcloud alpha dataplex data-taxonomies attributes get-iam-policy - retrieve - a Dataplex Data Attribute IAM policy - -SYNOPSIS - gcloud alpha dataplex data-taxonomies attributes get-iam-policy - (DATA_ATTRIBUTE : --data_taxonomy=DATA_TAXONOMY --location=LOCATION) - [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] - [--sort-by=[FIELD,...]] [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (ALPHA) Displays the IAM policy associated with a Dataplex Data Attribute - resource. If formatted as JSON, the output can be edited and used as a - policy file for set-iam-policy. The output includes an "etag" field - identifying the version emitted and allowing detection of concurrent policy - updates. - -EXAMPLES - To get the IAM policy of a Dataplex Data Attribute test-attribute in - project test-project under location us-central1 in Data Taxonomy - 'test-taxonomy' - - $ gcloud alpha dataplex data-taxonomies attributes get-iam-policy \ - test-taxonomy --project=test-project --location=us-central1 \ - --data_taxonomy=test-datataxonomy - -POSITIONAL ARGUMENTS - Data attribute resource - Arguments and flags that define the Dataplex - Data Attribute IAM policy you want to retrieve. 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_attribute 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_ATTRIBUTE - ID of the data attribute or fully qualified identifier for the data - attribute. - - To set the data_attribute attribute: - ▸ provide the argument data_attribute on the command line. - - This positional argument must be specified if any of the other - arguments in this group are specified. - - --data_taxonomy=DATA_TAXONOMY - Identifier of the Dataplex DataTaxonomy resource. - - To set the data_taxonomy attribute: - ▸ provide the argument data_attribute on the command line with a - fully specified name; - ▸ provide the argument --data_taxonomy on the command line. - - --location=LOCATION - Location of the Dataplex resource. - - To set the location attribute: - ▸ provide the argument data_attribute on the command line with a - fully specified name; - ▸ provide the argument --location on the command line; - ▸ set the property dataplex/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. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --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 dataplex/v1 API. The full documentation for this API - can be found at: https://cloud.google.com/dataplex/docs - -NOTES - This command is currently in alpha and might change without notice. If this - command fails with API permission errors despite specifying the correct - project, you might be trying to access an API with an invitation-only early - access allowlist. - diff --git a/gcloud/alpha/dataplex/data-taxonomies/attributes/help b/gcloud/alpha/dataplex/data-taxonomies/attributes/help deleted file mode 100644 index 19a742716..000000000 --- a/gcloud/alpha/dataplex/data-taxonomies/attributes/help +++ /dev/null @@ -1,53 +0,0 @@ -NAME - gcloud alpha dataplex data-taxonomies attributes - manage Dataplex Data - Attributes - -SYNOPSIS - gcloud alpha dataplex data-taxonomies attributes COMMAND - [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (ALPHA) Manage Dataplex Data Attributes. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --help. - - Run $ gcloud help for details. - -COMMANDS - COMMAND is one of the following: - - add-iam-policy-binding - (ALPHA) Add IAM policy binding to a Dataplex Data Attribute. - - create - (ALPHA) Create a Dataplex Data Attribute. - - delete - (ALPHA) Delete a Dataplex Data Attribute. - - describe - (ALPHA) Describe a Dataplex Data Attribute. - - get-iam-policy - (ALPHA) Retrieve a Dataplex Data Attribute IAM policy. - - list - (ALPHA) List Data Attributes within provided Data Taxonomy. - - remove-iam-policy-binding - (ALPHA) Removes IAM policy binding from a Dataplex Data Attribute. - - set-iam-policy - (ALPHA) Set an IAM policy binding for a Dataplex Data Attribute as - defined in a JSON or YAML file. - - update - (ALPHA) Update a Dataplex Data Attribute. - -NOTES - This command is currently in alpha and might change without notice. If this - command fails 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/dataplex/data-taxonomies/attributes/remove-iam-policy-binding b/gcloud/alpha/dataplex/data-taxonomies/attributes/remove-iam-policy-binding deleted file mode 100644 index be91eec9f..000000000 --- a/gcloud/alpha/dataplex/data-taxonomies/attributes/remove-iam-policy-binding +++ /dev/null @@ -1,103 +0,0 @@ -NAME - gcloud alpha dataplex data-taxonomies attributes remove-iam-policy-binding - - removes IAM policy binding from a Dataplex Data Attribute - -SYNOPSIS - gcloud alpha dataplex data-taxonomies attributes remove-iam-policy-binding - (DATA_ATTRIBUTE : --data_taxonomy=DATA_TAXONOMY --location=LOCATION) - --member=PRINCIPAL --role=ROLE [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (ALPHA) Removes IAM policy binding from a Dataplex Data Attribute. - -EXAMPLES - To remove an IAM policy binding for the role roles/dataplex.viewer for the - user testuser@gmail.com from Data Attribute test-attribute in location - us-central, in Data Taxonomy 'test-taxonomy', run: - - $ gcloud alpha dataplex data-taxonomies attributes \ - remove-iam-policy-binding test-attribute \ - --project=test-project --location=us-central1 \ - --data_taxonomy=test-datataxonomy --role=roles/dataplex.viewer \ - --member=user:testuser@gmail.com - - See https://cloud.google.com/dataplex/docs/iam-roles for details of policy - role and member types. - -POSITIONAL ARGUMENTS - Data attribute resource - The DataAttribute to remove IAM policy binding - from 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_attribute 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_ATTRIBUTE - ID of the data attribute or fully qualified identifier for the data - attribute. - - To set the data_attribute attribute: - ▸ provide the argument data_attribute on the command line. - - This positional argument must be specified if any of the other - arguments in this group are specified. - - --data_taxonomy=DATA_TAXONOMY - The name of data attribute to use. - - To set the data_taxonomy attribute: - ▸ provide the argument data_attribute on the command line with a - fully specified name; - ▸ provide the argument --data_taxonomy on the command line. - - --location=LOCATION - The location of the Dataplex resource. - - To set the location attribute: - ▸ provide the argument data_attribute on the command line with a - fully specified name; - ▸ provide the argument --location on the command line; - ▸ set the property dataplex/location. - -REQUIRED FLAGS - --member=PRINCIPAL - The principal to remove the binding for. Should be of the form - user|group|serviceAccount:email or domain:domain. - - Examples: user:test-user@gmail.com, group:admins@example.com, - serviceAccount:test123@example.domain.com, or - domain:example.domain.com. - - Deleted principals have an additional deleted: prefix and a ?uid=UID - suffix, where UID is a unique identifier for the principal. Example: - deleted:user:test-user@gmail.com?uid=123456789012345678901. - - Some resources also accept the following special values: - ◆ allUsers - Special identifier that represents anyone who is on the - internet, with or without a Google account. - ◆ allAuthenticatedUsers - Special identifier that represents anyone - who is authenticated with a Google account or a service account. - - --role=ROLE - The role to remove the principal from. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --configuration, --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/dataplex/data-taxonomies/attributes/set-iam-policy b/gcloud/alpha/dataplex/data-taxonomies/attributes/set-iam-policy deleted file mode 100644 index dbd3fb580..000000000 --- a/gcloud/alpha/dataplex/data-taxonomies/attributes/set-iam-policy +++ /dev/null @@ -1,87 +0,0 @@ -NAME - gcloud alpha dataplex data-taxonomies attributes set-iam-policy - set an - IAM policy binding for a Dataplex Data Attribute as defined in a JSON - or YAML file - -SYNOPSIS - gcloud alpha dataplex data-taxonomies attributes set-iam-policy - (DATA_ATTRIBUTE : --data_taxonomy=DATA_TAXONOMY --location=LOCATION) - POLICY_FILE [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (ALPHA) See https://cloud.google.com/iam/docs/managing-policies for details - of the policy file format and contents. - -EXAMPLES - The following command will read an IAM policy defined in a JSON file - policy.json and set it for the Dataplex Data Attribute test-attribute in - location us-central, in Data Taxonomy 'test-taxonomy', run: - - $ gcloud alpha dataplex data-taxonomies attributes set-iam-policy \ - test-attribute --project=test-project --location=us-central1 \ - --data_taxonomy=test-datataxonomy policy.json - - where policy.json is the relative path to the json file. - -POSITIONAL ARGUMENTS - Data attribute resource - The DataAttribute to set IAM policy to. 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_attribute 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_ATTRIBUTE - ID of the data attribute or fully qualified identifier for the data - attribute. - - To set the data_attribute attribute: - ▸ provide the argument data_attribute on the command line. - - This positional argument must be specified if any of the other - arguments in this group are specified. - - --data_taxonomy=DATA_TAXONOMY - The name of data attribute to use. - - To set the data_taxonomy attribute: - ▸ provide the argument data_attribute on the command line with a - fully specified name; - ▸ provide the argument --data_taxonomy on the command line. - - --location=LOCATION - The location of the Dataplex resource. - - To set the location attribute: - ▸ provide the argument data_attribute on the command line with a - fully specified name; - ▸ provide the argument --location on the command line; - ▸ set the property dataplex/location. - - POLICY_FILE - Path to a local JSON or YAML formatted file containing a valid policy. - - The output of the get-iam-policy command is a valid file, as is any - JSON or YAML file conforming to the structure of a Policy - (https://cloud.google.com/iam/reference/rest/v1/Policy). - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --configuration, --flags-file, --flatten, --format, - --help, --impersonate-service-account, --log-http, --project, --quiet, - --trace-token, --user-output-enabled, --verbosity. - - Run $ gcloud help for details. - -NOTES - This command is currently in alpha and might change without notice. If this - command fails with API permission errors despite specifying the correct - project, you might be trying to access an API with an invitation-only early - access allowlist. - diff --git a/gcloud/alpha/dataplex/data-taxonomies/attributes/update b/gcloud/alpha/dataplex/data-taxonomies/attributes/update deleted file mode 100644 index 5f6e6456e..000000000 --- a/gcloud/alpha/dataplex/data-taxonomies/attributes/update +++ /dev/null @@ -1,143 +0,0 @@ -NAME - gcloud alpha dataplex data-taxonomies attributes update - update a Dataplex - Data Attribute - -SYNOPSIS - gcloud alpha dataplex data-taxonomies attributes update - (DATA_ATTRIBUTE : --data_taxonomy=DATA_TAXONOMY --location=LOCATION) - [--data-readers=[DATA_READERS,...]] [--description=DESCRIPTION] - [--display-name=DISPLAY_NAME] [--etag=ETAG] [--labels=[KEY=VALUE,...]] - [--parent=PARENT] [--async | --validate-only] - [--resource-owners=[RESOURCE_OWNERS,...] - --resource-readers=[RESOURCE_READERS,...] - --resource-writers=[RESOURCE_WRITERS,...]] [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (ALPHA) Update a Dataplex Data Attribute. - -EXAMPLES - To update Data Attribute test-attribute for Data Taxonomy test-datataxonomy - in project test-dataplex at location us-central1 with description as test - description , display name as displayName, resource-readers as - user:test@google.com, resource-writers as user:test@google.com, - resource-owner as user:test@google.com run: data-readers as - user:test@google.com and parent as test-attribute-parent, run: - - $ gcloud alpha dataplex data-taxonomies attributes update \ - test-attribute --location=us-central1 --project=test-dataplex' - --data_taxonomy=test-datataxonomy --description='test description' - --display-name='displayName' --resource-readers='user:test@google.com' - --resource-writers='user:test@google.com' --resource-owners='user:test@google.com' - --data-readers='user:test@google.com' - --parent='test-attribute-parent' - -POSITIONAL ARGUMENTS - Data attribute resource - The DataAttribute 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 data_attribute 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_ATTRIBUTE - ID of the data attribute or fully qualified identifier for the data - attribute. - - To set the data_attribute attribute: - ▸ provide the argument data_attribute on the command line. - - This positional argument must be specified if any of the other - arguments in this group are specified. - - --data_taxonomy=DATA_TAXONOMY - The name of data attribute to use. - - To set the data_taxonomy attribute: - ▸ provide the argument data_attribute on the command line with a - fully specified name; - ▸ provide the argument --data_taxonomy on the command line. - - --location=LOCATION - The location of the Dataplex resource. - - To set the location attribute: - ▸ provide the argument data_attribute on the command line with a - fully specified name; - ▸ provide the argument --location on the command line; - ▸ set the property dataplex/location. - -FLAGS - Specified when applied to data stored on the resource (eg: rows,columns in - BigQuery Tables). - - --data-readers=[DATA_READERS,...] - The set of principals to be granted reader role on the resource. - Expected principal formats are user:$userEmail, group:$groupEmail - - --description=DESCRIPTION - Description of the Data Attribute. - - --display-name=DISPLAY_NAME - Display Name of the Data Attribute. - - --etag=ETAG - etag value of the Data Attribute resource. - - --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. - - --parent=PARENT - Parent Data Attribute for the defined Data Attribute. It can be - attribute name or fully qualified attribute name. - - At most one of --async | --validate-only can be specified. - - At most one of these can be specified: - - --async - Return immediately, without waiting for the operation in progress to - complete. - - --validate-only - Validate the update action, but don't actually perform it. - - Spec related to Dataplex Resource.Specified when applied to a resource - (eg: Google Cloud Storage bucket, BigQuery, dataset, BigQuery table). - - --resource-owners=[RESOURCE_OWNERS,...] - The set of principals to be granted owner role on the resource. - Expected principal formats are user:$userEmail, group:$groupEmail - - --resource-readers=[RESOURCE_READERS,...] - The set of principals to be granted reader role on the resource. - Expected principal formats are user:$userEmail, group:$groupEmail - - --resource-writers=[RESOURCE_WRITERS,...] - The set of principals to be granted writer role on the resource. - Expected principal formats are user:$userEmail, group:$groupEmail - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --configuration, --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/dataplex/data-taxonomies/create b/gcloud/alpha/dataplex/data-taxonomies/create deleted file mode 100644 index 15cd097cb..000000000 --- a/gcloud/alpha/dataplex/data-taxonomies/create +++ /dev/null @@ -1,94 +0,0 @@ -NAME - gcloud alpha dataplex data-taxonomies create - create a Dataplex Data - Taxonomy - -SYNOPSIS - gcloud alpha dataplex data-taxonomies create - (DATA_TAXONOMY : --location=LOCATION) [--description=DESCRIPTION] - [--display-name=DISPLAY_NAME] [--labels=[KEY=VALUE,...]] - [--async | --validate-only] [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (ALPHA) A Data Taxonomy represents a logical group of related Data - Attributes. - -EXAMPLES - To create Data Taxonomy test-taxonomy in project test-dataplex at location - us-central1, with description test description and displayName displayName - , run: - - $ gcloud alpha dataplex data-taxonomies create test-taxonomy \ - --location=us-central1 --project=test-dataplex \ - --description='test description' --display-name='displayName' - -POSITIONAL ARGUMENTS - Data taxonomy resource - The DataTaxonomy 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 data_taxonomy 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_TAXONOMY - ID of the data taxonomy or fully qualified identifier for the data - taxonomy. - - To set the data_taxonomy attribute: - ▸ provide the argument data_taxonomy 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 of the Dataplex resource. - - To set the location attribute: - ▸ provide the argument data_taxonomy on the command line with a - fully specified name; - ▸ provide the argument --location on the command line; - ▸ set the property dataplex/location. - -FLAGS - --description=DESCRIPTION - Description of the Data Taxonomy. - - --display-name=DISPLAY_NAME - Display Name of the Data Taxonomy. - - --labels=[KEY=VALUE,...] - List of label KEY=VALUE pairs to add. - - Keys must start with a lowercase character and contain only hyphens - (-), underscores (_), lowercase characters, and numbers. Values must - contain only hyphens (-), underscores (_), lowercase characters, and - numbers. - - At most one of these can be specified: - - --async - Return immediately, without waiting for the operation in progress to - complete. - - --validate-only - Validate the create action, but don't actually perform it. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --configuration, --flags-file, --flatten, --format, - --help, --impersonate-service-account, --log-http, --project, --quiet, - --trace-token, --user-output-enabled, --verbosity. - - Run $ gcloud help for details. - -NOTES - This command is currently in alpha and might change without notice. If this - command fails 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/dataplex/data-taxonomies/delete b/gcloud/alpha/dataplex/data-taxonomies/delete deleted file mode 100644 index c0242d24d..000000000 --- a/gcloud/alpha/dataplex/data-taxonomies/delete +++ /dev/null @@ -1,78 +0,0 @@ -NAME - gcloud alpha dataplex data-taxonomies delete - delete a Dataplex Data - Taxonomy - -SYNOPSIS - gcloud alpha dataplex data-taxonomies delete - (DATA_TAXONOMY : --location=LOCATION) [--async] [--etag=ETAG] - [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (ALPHA) Delete a Dataplex Data Taxonomy. - -EXAMPLES - To Delete Data Taxonomy test-taxonomy in project test-dataplex at location - us-central1, run: - - $ gcloud alpha dataplex data-taxonomies delete test-taxonomy \ - --location=us-central1 --project=test-dataplex - -POSITIONAL ARGUMENTS - Data taxonomy resource - Arguments and flags that define the Dataplex Data - Taxonomy you want to delete. The arguments in this group can be used to - specify the attributes of this resource. (NOTE) Some attributes are not - given arguments in this group but can be set in other ways. - - To set the project attribute: - ◆ provide the argument data_taxonomy 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_TAXONOMY - ID of the data taxonomy or fully qualified identifier for the data - taxonomy. - - To set the data_taxonomy attribute: - ▸ provide the argument data_taxonomy on the command line. - - This positional argument must be specified if any of the other - arguments in this group are specified. - - --location=LOCATION - Location of the Dataplex resource. - - To set the location attribute: - ▸ provide the argument data_taxonomy on the command line with a - fully specified name; - ▸ provide the argument --location on the command line; - ▸ set the property dataplex/location. - -FLAGS - --async - Return immediately, without waiting for the operation in progress to - complete. - - --etag=ETAG - etag value for particular Data Taxonomy. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --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 dataplex/v1 API. The full documentation for this API - can be found at: https://cloud.google.com/dataplex/docs - -NOTES - This command is currently in alpha and might change without notice. If this - command fails with API permission errors despite specifying the correct - project, you might be trying to access an API with an invitation-only early - access allowlist. - diff --git a/gcloud/alpha/dataplex/data-taxonomies/help b/gcloud/alpha/dataplex/data-taxonomies/help deleted file mode 100644 index c85de5de3..000000000 --- a/gcloud/alpha/dataplex/data-taxonomies/help +++ /dev/null @@ -1,58 +0,0 @@ -NAME - gcloud alpha dataplex data-taxonomies - manage Dataplex Data Taxonomies - -SYNOPSIS - gcloud alpha dataplex data-taxonomies GROUP | COMMAND - [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (ALPHA) Manage Dataplex Data Taxonomies. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --help. - - Run $ gcloud help for details. - -GROUPS - GROUP is one of the following: - - attributes - (ALPHA) Manage Dataplex Data Attributes. - -COMMANDS - COMMAND is one of the following: - - add-iam-policy-binding - (ALPHA) Add IAM policy binding to a Dataplex Data Taxonomy. - - create - (ALPHA) Create a Dataplex Data Taxonomy. - - delete - (ALPHA) Delete a Dataplex Data Taxonomy. - - describe - (ALPHA) Describe a Data Taxonomy. - - get-iam-policy - (ALPHA) Retrieve a Dataplex Data Taxonomy IAM policy. - - list - (ALPHA) List Data Taxonomies. - - remove-iam-policy-binding - (ALPHA) Removes IAM policy binding from a Dataplex Data Taxonomy. - - set-iam-policy - (ALPHA) Set an IAM policy binding for a Dataplex Data Taxonomy as - defined in a JSON or YAML file. - - update - (ALPHA) Update a Dataplex Data Taxonomy. - -NOTES - This command is currently in alpha and might change without notice. If this - command fails 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/dataplex/data-taxonomies/update b/gcloud/alpha/dataplex/data-taxonomies/update deleted file mode 100644 index 34f3535f7..000000000 --- a/gcloud/alpha/dataplex/data-taxonomies/update +++ /dev/null @@ -1,96 +0,0 @@ -NAME - gcloud alpha dataplex data-taxonomies update - update a Dataplex Data - Taxonomy - -SYNOPSIS - gcloud alpha dataplex data-taxonomies update - (DATA_TAXONOMY : --location=LOCATION) [--description=DESCRIPTION] - [--display-name=DISPLAY_NAME] [--etag=ETAG] [--labels=[KEY=VALUE,...]] - [--async | --validate-only] [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (ALPHA) Update a Dataplex Data Taxonomy. - -EXAMPLES - To update Data Taxonomy test-taxonomy in project test-dataplex at location - us-central1, with description updated description and displayName - displayName - - $ gcloud alpha dataplex data-taxonomies update test-taxonomy \ - --location=us-central1 --project=test-dataplex \ - --description='updated description' - -POSITIONAL ARGUMENTS - Data taxonomy resource - The DataTaxonomy 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 data_taxonomy 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_TAXONOMY - ID of the data taxonomy or fully qualified identifier for the data - taxonomy. - - To set the data_taxonomy attribute: - ▸ provide the argument data_taxonomy 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 of the Dataplex resource. - - To set the location attribute: - ▸ provide the argument data_taxonomy on the command line with a - fully specified name; - ▸ provide the argument --location on the command line; - ▸ set the property dataplex/location. - -FLAGS - --description=DESCRIPTION - Description of the Data Taxonomy. - - --display-name=DISPLAY_NAME - Display Name of the Data Taxonomy. - - --etag=ETAG - etag value for particular Data Taxonomy. - - --labels=[KEY=VALUE,...] - List of label KEY=VALUE pairs to add. - - Keys must start with a lowercase character and contain only hyphens - (-), underscores (_), lowercase characters, and numbers. Values must - contain only hyphens (-), underscores (_), lowercase characters, and - numbers. - - At most one of these can be specified: - - --async - Return immediately, without waiting for the operation in progress to - complete. - - --validate-only - Validate the update action, but don't actually perform it. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --configuration, --flags-file, --flatten, --format, - --help, --impersonate-service-account, --log-http, --project, --quiet, - --trace-token, --user-output-enabled, --verbosity. - - Run $ gcloud help for details. - -NOTES - This command is currently in alpha and might change without notice. If this - command fails 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/dataplex/datascans/create/data-profile b/gcloud/alpha/dataplex/datascans/create/data-profile index 60aaded09..641dee6d9 100644 --- a/gcloud/alpha/dataplex/datascans/create/data-profile +++ b/gcloud/alpha/dataplex/datascans/create/data-profile @@ -16,8 +16,9 @@ SYNOPSIS --include-field-names=INCLUDE_FIELD_NAMES --row-filter=ROW_FILTER --sampling-percent=SAMPLING_PERCENT] [--incremental-field=INCREMENTAL_FIELD --on-demand=ON_DEMAND - | --schedule=SCHEDULE - | --one-time --ttl-after-scan-completion=TTL_AFTER_SCAN_COMPLETION] + | --schedule=SCHEDULE | --one-time + --ttl-after-scan-completion=TTL_AFTER_SCAN_COMPLETION + --service-account=SERVICE_ACCOUNT | --use-user-credential] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -190,6 +191,16 @@ OPTIONAL FLAGS "100s" for 100 seconds.The argument is only valid when --one-time is set. + Identity to run the datascan. + + At most one of these can be specified: + + --service-account=SERVICE_ACCOUNT + Service account email to run the scan as. + + --use-user-credential + If set, the scan runs with the caller's credential. + 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/dataplex/datascans/create/data-quality b/gcloud/alpha/dataplex/datascans/create/data-quality index 56cbb5fbf..35fb69b87 100644 --- a/gcloud/alpha/dataplex/datascans/create/data-quality +++ b/gcloud/alpha/dataplex/datascans/create/data-quality @@ -11,8 +11,9 @@ SYNOPSIS [--description=DESCRIPTION] [--display-name=DISPLAY_NAME] [--labels=[KEY=VALUE,...]] [--async | --validate-only] [--incremental-field=INCREMENTAL_FIELD --on-demand=ON_DEMAND - | --schedule=SCHEDULE - | --one-time --ttl-after-scan-completion=TTL_AFTER_SCAN_COMPLETION] + | --schedule=SCHEDULE | --one-time + --ttl-after-scan-completion=TTL_AFTER_SCAN_COMPLETION + --service-account=SERVICE_ACCOUNT | --use-user-credential] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -154,6 +155,16 @@ OPTIONAL FLAGS "100s" for 100 seconds.The argument is only valid when --one-time is set. + Identity to run the datascan. + + At most one of these can be specified: + + --service-account=SERVICE_ACCOUNT + Service account email to run the scan as. + + --use-user-credential + If set, the scan runs with the caller's credential. + 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/dataplex/entries/help b/gcloud/alpha/dataplex/entries/help index 34fde88bf..7ebdd5940 100644 --- a/gcloud/alpha/dataplex/entries/help +++ b/gcloud/alpha/dataplex/entries/help @@ -30,6 +30,9 @@ COMMANDS lookup (ALPHA) Lookup a Dataplex entry. + modify + (ALPHA) Modify a Dataplex Entry. + remove-aspects (ALPHA) Remove aspects from a Dataplex Entry. diff --git a/gcloud/alpha/dataplex/entries/modify b/gcloud/alpha/dataplex/entries/modify new file mode 100644 index 000000000..b69426a74 --- /dev/null +++ b/gcloud/alpha/dataplex/entries/modify @@ -0,0 +1,295 @@ +NAME + gcloud alpha dataplex entries modify - modify a Dataplex Entry + +SYNOPSIS + gcloud alpha dataplex entries modify + (ENTRY : --entry-group=ENTRY_GROUP --location=LOCATION) + [--remove-aspects=[ASPECT_TYPE@PATH,...]] + [--update-aspects=YAML_OR_JSON_FILE] + [--clear-fully-qualified-name + | --fully-qualified-name=FULLY_QUALIFIED_NAME] + [--entry-source-update-time=DATE_TIME + : --clear-entry-source-create-time + | --entry-source-create-time=DATE_TIME + --clear-entry-source-description + | --entry-source-description=DESCRIPTION + --clear-entry-source-display-name + | --entry-source-display-name=DISPLAY_NAME + --clear-entry-source-labels + | --entry-source-labels=[KEY=VALUE,...] --clear-entry-source-platform + | --entry-source-platform=PLATFORM_NAME --clear-entry-source-resource + | --entry-source-resource=RESOURCE --clear-entry-source-system + | --entry-source-system=SYSTEM_NAME] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Modify specified fields in a given Dataplex Entry. + +EXAMPLES + To modify fully qualified name (FQN) of an entry, run: + + $ gcloud alpha dataplex entries modify entry1 \ + --project=test-project --location=us-central1 \ + --entry-group entry-group1 --fully-qualified-name='custom:a.b.c' + + To modify description of an entry, run: + + $ gcloud alpha dataplex entries modify entry1 \ + --project=test-project --location=us-central1 \ + --entry-group entry-group1 \ + --entry-source-description='Updated description' \ + --entry-source-update-time='1998-09-04T12:00:00-0700' + + To clear the description of an entry, run: + + $ gcloud alpha dataplex entries modify entry1 \ + --project=test-project --location=us-central1 \ + --entry-group entry-group1 --clear-entry-source-description \ + --entry-source-update-time='1998-09-04T12:00:00-0700' + + To add or update aspects from the YAML/JSON file, run: + + $ gcloud alpha dataplex entries modify entry1 \ + --project=test-project --location=us-central1 \ + --entry-group entry-group1 \ + --update-aspects=path-to-a-file-with-aspects.json + + To remove all aspects of type test-project.us-central1.some-aspect-type + from the entry, run: + + $ gcloud alpha dataplex entries modify entry1 \ + --project=test-project --location=us-central1 \ + --entry-group entry-group1 \ + --remove-aspects='test-project.us-central1.some-aspect-type@*' + + To remove all aspects on path Schema.column1 from the entry, run: + + $ gcloud alpha dataplex entries modify entry1 \ + --project=test-project --location=us-central1 \ + --entry-group entry-group1 --remove-aspects='*@Schema.column1' + + To remove exact aspects + test-project.us-central1.some-aspect-type@Schema.column1 and + test-project.us-central1.some-aspect-type2@Schema.column2 from the entry, + run: + + $ gcloud alpha dataplex entries modify entry1 \ + --project=test-project --location=us-central1 \ + --entry-group entry-group1 \ + --remove-aspects=test-project.us-central1.some-aspect-type@Schem\ + a.column1,test-project.us-central2.some-aspect-type@Schema.column2 + +POSITIONAL ARGUMENTS + Entry resource - Arguments and flags that define the Dataplex Entry you + want to reference. 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 entry 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. + + ENTRY + ID of the entry or fully qualified identifier for the entry. + + To set the entry attribute: + ▸ provide the argument entry on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --entry-group=ENTRY_GROUP + Entry group containing Dataplex Entries. + + To set the entry-group attribute: + ▸ provide the argument entry on the command line with a fully + specified name; + ▸ provide the argument --entry-group on the command line. + + --location=LOCATION + Location of the Dataplex resource. + + To set the location attribute: + ▸ provide the argument entry on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ set the property dataplex/location. + +FLAGS + --remove-aspects=[ASPECT_TYPE@PATH,...] + List of Aspect keys, identifying Aspects to remove from the entry. + + Keys are in the format ASPECT_TYPE@PATH, or just ASPECT_TYPE, if the + Aspect is attached to an entry itself rather than to a specific column + defined in the schema. + + ASPECT_TYPE is expected to be in a format + PROJECT_ID.LOCATION.ASPECT_TYPE_ID or a wildcard *, which targets all + aspect types. + + PATH can be either empty (which means a 'root' path, such that Aspect + is attached to the entry itself), point to a specific column defined in + the schema (for example: Schema.some_column) or a wildcard * (target + all paths). + + ASPECT_TYPE and PATH cannot be both specified as wildcards *. + + If both --update-aspects and --remove-aspects flags are specified, and + the same aspect key is used in both flags, then --update-aspects takes + precedence, and such an aspect will be updated and not removed. + + --update-aspects=YAML_OR_JSON_FILE + Path to a YAML or JSON file containing Aspects to add or update. + + When this flag is specified, only Aspects referenced in the file are + going to be added or updated. Specifying this flag does not remove any + Aspects from the entry. In other words, specifying this flag will not + lead to a full replacement of Aspects with a contents of the provided + file. + + Content of the file contains a map, where keys are in the format + ASPECT_TYPE@PATH, or just ASPECT_TYPE, if the Aspect is attached to an + entry itself rather than to a specific column defined in the schema. + + Values in the map represent Aspect's content, which must conform to a + template defined for a given ASPECT_TYPE. Each Aspect will be replaced + fully by the provided content. That means data in the Aspect will be + replaced and not merged with existing contents of that Aspect in the + Entry. + + ASPECT_TYPE is expected to be in a format + PROJECT_ID.LOCATION.ASPECT_TYPE_ID. + + PATH can be either empty (which means a 'root' path, such that Aspect + is attached to the entry itself) or point to a specific column defined + in the schema. For example: Schema.some_column. + + Example YAML format: + + project-id1.us-central1.my-aspect-type1: + data: + aspectField1: someValue + aspectField2: someOtherValue + project-id2.us-central1.my-aspect-type2@Schema.column1: + data: + aspectField3: someValue3 + + Example JSON format: + + { + "project-id1.us-central1.my-aspect-type1": { + "data": { + "aspectField1": "someValue", + "aspectField2": "someOtherValue" + } + }, + "project-id2.us-central1.my-aspect-type2@Schema.column1": { + "data": { + "aspectField3": "someValue3" + } + } + } + + If both --update-aspects and --remove-aspects flags are specified, and + the same aspect key is used in both flags, then --update-aspects takes + precedence, and such an aspect will be updated and not removed. + + At most one of these can be specified: + + --clear-fully-qualified-name + Clear the FQN for the Entry. + + --fully-qualified-name=FULLY_QUALIFIED_NAME + FQN, a name for the entry that can reference it in an external + system. + + Source system related information for an entry. If any of the entry source + fields are specified, then ``--entry-source-update-time must be specified + as well. + + --entry-source-update-time=DATE_TIME + The update date and time of the resource in the source system. + + This flag argument must be specified if any of the other arguments in + this group are specified. + + At most one of these can be specified: + + --clear-entry-source-create-time + Clear the value for the create_time field in the Entry Source. + + --entry-source-create-time=DATE_TIME + The creation date and time of the resource in the source system. + + At most one of these can be specified: + + --clear-entry-source-description + Clear the value for the description field in the Entry Source. + + --entry-source-description=DESCRIPTION + Description of the Entry. + + At most one of these can be specified: + + --clear-entry-source-display-name + Clear the value for the display_name field in the Entry Source. + + --entry-source-display-name=DISPLAY_NAME + User friendly display name. + + At most one of these can be specified: + + --clear-entry-source-labels + Clear the labels for the Entry Source. + + --entry-source-labels=[KEY=VALUE,...] + List of label KEY=VALUE pairs to add. + + Keys must start with a lowercase character and contain only hyphens + (-), underscores (_), lowercase characters, and numbers. Values must + contain only hyphens (-), underscores (_), lowercase characters, and + numbers. + + At most one of these can be specified: + + --clear-entry-source-platform + Clear the value for the platform field in the Entry Source. + + --entry-source-platform=PLATFORM_NAME + The platform containing the source system. + + At most one of these can be specified: + + --clear-entry-source-resource + Clear the value for the resource field in the Entry Source. + + --entry-source-resource=RESOURCE + The name of the resource in the source system. + + At most one of these can be specified: + + --clear-entry-source-system + Clear the value for the system field in the Entry Source. + + --entry-source-system=SYSTEM_NAME + The name of the source system. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --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 dataplex entries modify + diff --git a/gcloud/alpha/dataplex/help b/gcloud/alpha/dataplex/help index fce94aa23..c86c2e05b 100644 --- a/gcloud/alpha/dataplex/help +++ b/gcloud/alpha/dataplex/help @@ -24,12 +24,6 @@ GROUPS context (ALPHA) Manage Dataplex Context. - data-attribute-bindings - (ALPHA) Manage Dataplex Data Attribute Bindings. - - data-taxonomies - (ALPHA) Manage Dataplex Data Taxonomies. - datascans (ALPHA) Manage Dataplex Datascan. diff --git a/gcloud/alpha/dataproc/clusters/create b/gcloud/alpha/dataproc/clusters/create index 14a00e5d3..d9a92a8a8 100644 --- a/gcloud/alpha/dataproc/clusters/create +++ b/gcloud/alpha/dataproc/clusters/create @@ -13,10 +13,12 @@ SYNOPSIS [--driver-pool-machine-type=DRIVER_POOL_MACHINE_TYPE] [--driver-pool-min-cpu-platform=PLATFORM] [--driver-pool-size=DRIVER_POOL_SIZE] [--enable-component-gateway] + [--engine=ENGINE] [--initialization-action-timeout=TIMEOUT; default="10m"] [--initialization-actions=CLOUD_STORAGE_URI,[...]] [--labels=[KEY=VALUE,...]] [--master-accelerator=[type=TYPE,[count=COUNT],...]] + [--master-attached-disks=MASTER_ATTACHED_DISKS] [--master-boot-disk-provisioned-iops=MASTER_BOOT_DISK_PROVISIONED_IOPS] [--master-boot-disk-provisioned-throughput=MASTER_BOOT_DISK_PROVISIONED_THROUGHPUT] [--master-boot-disk-size=MASTER_BOOT_DISK_SIZE] @@ -35,6 +37,7 @@ SYNOPSIS [--private-ipv6-google-access-type=PRIVATE_IPV6_GOOGLE_ACCESS_TYPE] [--properties=[PREFIX:PROPERTY=VALUE,...]] [--secondary-worker-accelerator=[type=TYPE,[count=COUNT],...]] + [--secondary-worker-attached-disks=SECONDARY_WORKER_ATTACHED_DISKS] [--secondary-worker-boot-disk-size=SECONDARY_WORKER_BOOT_DISK_SIZE] [--secondary-worker-boot-disk-type=SECONDARY_WORKER_BOOT_DISK_TYPE] [--secondary-worker-local-ssd-interface=SECONDARY_WORKER_LOCAL_SSD_INTERFACE] @@ -44,8 +47,9 @@ SYNOPSIS [--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] [--tier=TIER] + [--temp-bucket=TEMP_BUCKET] [--worker-accelerator=[type=TYPE,[count=COUNT],...]] + [--worker-attached-disks=WORKER_ATTACHED_DISKS] [--worker-boot-disk-provisioned-iops=WORKER_BOOT_DISK_PROVISIONED_IOPS] [--worker-boot-disk-provisioned-throughput=WORKER_BOOT_DISK_PROVISIONED_THROUGHPUT] [--worker-boot-disk-size=WORKER_BOOT_DISK_SIZE] @@ -206,6 +210,9 @@ FLAGS Enable access to the web UIs of selected components on the cluster through the component gateway. + --engine=ENGINE + Cluster engine. ENGINE must be one of: default, lightning. + --initialization-action-timeout=TIMEOUT; default="10m" The maximum duration of each initialization action. See $ gcloud topic datetimes for information on duration formats. @@ -234,6 +241,42 @@ FLAGS The number of accelerators to attach to each instance. The default value is 1. + --master-attached-disks=MASTER_ATTACHED_DISKS + A list of disk configurations to attach to each instance in this group. + Disk configurations are separated by semicolons. Each disk + configuration is a comma-separated list of the following parameters. + + type - required + The type of disk to attach to the instances + (https://cloud.google.com/compute/docs/disks/hyperdisks). + Allowed disk types are: hyperdisk-balanced, hyperdisk-extreme, + hyperdisk-ml, hyperdisk-throughput. + + size - optional + The size of the disk. The value must be a whole number followed by + a size unit GB for gigabyte, or TB for terabyte. For example, + 10GB produces a 10 gigabyte disk. + + iops - optional + Indicates the IOPS + (https://cloud.google.com/compute/docs/disks/hyperdisks#iops) to + provision for the attached hyperdisk. This parameter sets the limit + for disk I/O operations per second. + + throughput - optional + Indicates the throughput + (https://cloud.google.com/compute/docs/disks/hyperdisks#throughput) + to provision for the attached hyperdisk. This parameter sets the + limit for throughput in MiB per second. + + Example: + type='hyperdisk-balanced,iops=5000,throughput=200,size=100G;type=hyperdisk-throughput,size=9000G' + + Attaches two disks to the instances. The first disk is a + hyperdisk-balanced disk with 5000 IOPS, 200 MiB/s throughput, and 100 + GiB size. The second disk is a hyperdisk-throughput disk with 9000 + GiB size. + --master-boot-disk-provisioned-iops=MASTER_BOOT_DISK_PROVISIONED_IOPS Indicates the IOPS (https://cloud.google.com/compute/docs/disks/hyperdisks#iops) to @@ -372,6 +415,42 @@ FLAGS The number of accelerators to attach to each instance. The default value is 1. + --secondary-worker-attached-disks=SECONDARY_WORKER_ATTACHED_DISKS + A list of disk configurations to attach to each instance in this group. + Disk configurations are separated by semicolons. Each disk + configuration is a comma-separated list of the following parameters. + + type - required + The type of disk to attach to the instances + (https://cloud.google.com/compute/docs/disks/hyperdisks). + Allowed disk types are: hyperdisk-balanced, hyperdisk-extreme, + hyperdisk-ml, hyperdisk-throughput. + + size - optional + The size of the disk. The value must be a whole number followed by + a size unit GB for gigabyte, or TB for terabyte. For example, + 10GB produces a 10 gigabyte disk. + + iops - optional + Indicates the IOPS + (https://cloud.google.com/compute/docs/disks/hyperdisks#iops) to + provision for the attached hyperdisk. This parameter sets the limit + for disk I/O operations per second. + + throughput - optional + Indicates the throughput + (https://cloud.google.com/compute/docs/disks/hyperdisks#throughput) + to provision for the attached hyperdisk. This parameter sets the + limit for throughput in MiB per second. + + Example: + type='hyperdisk-balanced,iops=5000,throughput=200,size=100G;type=hyperdisk-throughput,size=9000G' + + Attaches two disks to the instances. The first disk is a + hyperdisk-balanced disk with 5000 IOPS, 200 MiB/s throughput, and 100 + GiB size. The second disk is a hyperdisk-throughput disk with 9000 + GiB size. + --secondary-worker-boot-disk-size=SECONDARY_WORKER_BOOT_DISK_SIZE The size of the boot disk. The value must be a whole number followed by a size unit of KB for kilobyte, MB for megabyte, GB for gigabyte, or TB @@ -434,9 +513,6 @@ FLAGS The Google Cloud Storage bucket to use by default to store ephemeral cluster and jobs data, such as Spark and MapReduce history files. - --tier=TIER - Cluster tier. TIER must be one of: premium, standard. - --worker-accelerator=[type=TYPE,[count=COUNT],...] Attaches accelerators, such as GPUs, to the worker instance(s). @@ -449,6 +525,42 @@ FLAGS The number of accelerators to attach to each instance. The default value is 1. + --worker-attached-disks=WORKER_ATTACHED_DISKS + A list of disk configurations to attach to each instance in this group. + Disk configurations are separated by semicolons. Each disk + configuration is a comma-separated list of the following parameters. + + type - required + The type of disk to attach to the instances + (https://cloud.google.com/compute/docs/disks/hyperdisks). + Allowed disk types are: hyperdisk-balanced, hyperdisk-extreme, + hyperdisk-ml, hyperdisk-throughput. + + size - optional + The size of the disk. The value must be a whole number followed by + a size unit GB for gigabyte, or TB for terabyte. For example, + 10GB produces a 10 gigabyte disk. + + iops - optional + Indicates the IOPS + (https://cloud.google.com/compute/docs/disks/hyperdisks#iops) to + provision for the attached hyperdisk. This parameter sets the limit + for disk I/O operations per second. + + throughput - optional + Indicates the throughput + (https://cloud.google.com/compute/docs/disks/hyperdisks#throughput) + to provision for the attached hyperdisk. This parameter sets the + limit for throughput in MiB per second. + + Example: + type='hyperdisk-balanced,iops=5000,throughput=200,size=100G;type=hyperdisk-throughput,size=9000G' + + Attaches two disks to the instances. The first disk is a + hyperdisk-balanced disk with 5000 IOPS, 200 MiB/s throughput, and 100 + GiB size. The second disk is a hyperdisk-throughput disk with 9000 + GiB size. + --worker-boot-disk-provisioned-iops=WORKER_BOOT_DISK_PROVISIONED_IOPS Indicates the IOPS (https://cloud.google.com/compute/docs/disks/hyperdisks#iops) to diff --git a/gcloud/alpha/dataproc/workflow-templates/set-managed-cluster b/gcloud/alpha/dataproc/workflow-templates/set-managed-cluster index 61adad2ac..f0ecd832f 100644 --- a/gcloud/alpha/dataproc/workflow-templates/set-managed-cluster +++ b/gcloud/alpha/dataproc/workflow-templates/set-managed-cluster @@ -6,11 +6,12 @@ SYNOPSIS gcloud alpha dataproc workflow-templates set-managed-cluster (TEMPLATE : --region=REGION) [--autoscaling-policy=AUTOSCALING_POLICY] [--bucket=BUCKET] [--cluster-name=CLUSTER_NAME] [--cluster-type=TYPE] - [--enable-component-gateway] + [--enable-component-gateway] [--engine=ENGINE] [--initialization-action-timeout=TIMEOUT; default="10m"] [--initialization-actions=CLOUD_STORAGE_URI,[...]] [--labels=[KEY=VALUE,...]] [--master-accelerator=[type=TYPE,[count=COUNT],...]] + [--master-attached-disks=MASTER_ATTACHED_DISKS] [--master-boot-disk-provisioned-iops=MASTER_BOOT_DISK_PROVISIONED_IOPS] [--master-boot-disk-provisioned-throughput=MASTER_BOOT_DISK_PROVISIONED_THROUGHPUT] [--master-boot-disk-size=MASTER_BOOT_DISK_SIZE] @@ -28,6 +29,7 @@ SYNOPSIS [--private-ipv6-google-access-type=PRIVATE_IPV6_GOOGLE_ACCESS_TYPE] [--properties=[PREFIX:PROPERTY=VALUE,...]] [--secondary-worker-accelerator=[type=TYPE,[count=COUNT],...]] + [--secondary-worker-attached-disks=SECONDARY_WORKER_ATTACHED_DISKS] [--secondary-worker-boot-disk-size=SECONDARY_WORKER_BOOT_DISK_SIZE] [--secondary-worker-boot-disk-type=SECONDARY_WORKER_BOOT_DISK_TYPE] [--secondary-worker-local-ssd-interface=SECONDARY_WORKER_LOCAL_SSD_INTERFACE] @@ -36,8 +38,9 @@ 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] [--temp-bucket=TEMP_BUCKET] [--tier=TIER] + [--shielded-vtpm] [--temp-bucket=TEMP_BUCKET] [--worker-accelerator=[type=TYPE,[count=COUNT],...]] + [--worker-attached-disks=WORKER_ATTACHED_DISKS] [--worker-boot-disk-provisioned-iops=WORKER_BOOT_DISK_PROVISIONED_IOPS] [--worker-boot-disk-provisioned-throughput=WORKER_BOOT_DISK_PROVISIONED_THROUGHPUT] [--worker-boot-disk-size=WORKER_BOOT_DISK_SIZE] @@ -137,6 +140,9 @@ FLAGS Enable access to the web UIs of selected components on the cluster through the component gateway. + --engine=ENGINE + Cluster engine. ENGINE must be one of: default, lightning. + --initialization-action-timeout=TIMEOUT; default="10m" The maximum duration of each initialization action. See $ gcloud topic datetimes for information on duration formats. @@ -165,6 +171,42 @@ FLAGS The number of accelerators to attach to each instance. The default value is 1. + --master-attached-disks=MASTER_ATTACHED_DISKS + A list of disk configurations to attach to each instance in this group. + Disk configurations are separated by semicolons. Each disk + configuration is a comma-separated list of the following parameters. + + type - required + The type of disk to attach to the instances + (https://cloud.google.com/compute/docs/disks/hyperdisks). + Allowed disk types are: hyperdisk-balanced, hyperdisk-extreme, + hyperdisk-ml, hyperdisk-throughput. + + size - optional + The size of the disk. The value must be a whole number followed by + a size unit GB for gigabyte, or TB for terabyte. For example, + 10GB produces a 10 gigabyte disk. + + iops - optional + Indicates the IOPS + (https://cloud.google.com/compute/docs/disks/hyperdisks#iops) to + provision for the attached hyperdisk. This parameter sets the limit + for disk I/O operations per second. + + throughput - optional + Indicates the throughput + (https://cloud.google.com/compute/docs/disks/hyperdisks#throughput) + to provision for the attached hyperdisk. This parameter sets the + limit for throughput in MiB per second. + + Example: + type='hyperdisk-balanced,iops=5000,throughput=200,size=100G;type=hyperdisk-throughput,size=9000G' + + Attaches two disks to the instances. The first disk is a + hyperdisk-balanced disk with 5000 IOPS, 200 MiB/s throughput, and 100 + GiB size. The second disk is a hyperdisk-throughput disk with 9000 + GiB size. + --master-boot-disk-provisioned-iops=MASTER_BOOT_DISK_PROVISIONED_IOPS Indicates the IOPS (https://cloud.google.com/compute/docs/disks/hyperdisks#iops) to @@ -300,6 +342,42 @@ FLAGS The number of accelerators to attach to each instance. The default value is 1. + --secondary-worker-attached-disks=SECONDARY_WORKER_ATTACHED_DISKS + A list of disk configurations to attach to each instance in this group. + Disk configurations are separated by semicolons. Each disk + configuration is a comma-separated list of the following parameters. + + type - required + The type of disk to attach to the instances + (https://cloud.google.com/compute/docs/disks/hyperdisks). + Allowed disk types are: hyperdisk-balanced, hyperdisk-extreme, + hyperdisk-ml, hyperdisk-throughput. + + size - optional + The size of the disk. The value must be a whole number followed by + a size unit GB for gigabyte, or TB for terabyte. For example, + 10GB produces a 10 gigabyte disk. + + iops - optional + Indicates the IOPS + (https://cloud.google.com/compute/docs/disks/hyperdisks#iops) to + provision for the attached hyperdisk. This parameter sets the limit + for disk I/O operations per second. + + throughput - optional + Indicates the throughput + (https://cloud.google.com/compute/docs/disks/hyperdisks#throughput) + to provision for the attached hyperdisk. This parameter sets the + limit for throughput in MiB per second. + + Example: + type='hyperdisk-balanced,iops=5000,throughput=200,size=100G;type=hyperdisk-throughput,size=9000G' + + Attaches two disks to the instances. The first disk is a + hyperdisk-balanced disk with 5000 IOPS, 200 MiB/s throughput, and 100 + GiB size. The second disk is a hyperdisk-throughput disk with 9000 + GiB size. + --secondary-worker-boot-disk-size=SECONDARY_WORKER_BOOT_DISK_SIZE The size of the boot disk. The value must be a whole number followed by a size unit of KB for kilobyte, MB for megabyte, GB for gigabyte, or TB @@ -357,9 +435,6 @@ FLAGS The Google Cloud Storage bucket to use by default to store ephemeral cluster and jobs data, such as Spark and MapReduce history files. - --tier=TIER - Cluster tier. TIER must be one of: premium, standard. - --worker-accelerator=[type=TYPE,[count=COUNT],...] Attaches accelerators, such as GPUs, to the worker instance(s). @@ -372,6 +447,42 @@ FLAGS The number of accelerators to attach to each instance. The default value is 1. + --worker-attached-disks=WORKER_ATTACHED_DISKS + A list of disk configurations to attach to each instance in this group. + Disk configurations are separated by semicolons. Each disk + configuration is a comma-separated list of the following parameters. + + type - required + The type of disk to attach to the instances + (https://cloud.google.com/compute/docs/disks/hyperdisks). + Allowed disk types are: hyperdisk-balanced, hyperdisk-extreme, + hyperdisk-ml, hyperdisk-throughput. + + size - optional + The size of the disk. The value must be a whole number followed by + a size unit GB for gigabyte, or TB for terabyte. For example, + 10GB produces a 10 gigabyte disk. + + iops - optional + Indicates the IOPS + (https://cloud.google.com/compute/docs/disks/hyperdisks#iops) to + provision for the attached hyperdisk. This parameter sets the limit + for disk I/O operations per second. + + throughput - optional + Indicates the throughput + (https://cloud.google.com/compute/docs/disks/hyperdisks#throughput) + to provision for the attached hyperdisk. This parameter sets the + limit for throughput in MiB per second. + + Example: + type='hyperdisk-balanced,iops=5000,throughput=200,size=100G;type=hyperdisk-throughput,size=9000G' + + Attaches two disks to the instances. The first disk is a + hyperdisk-balanced disk with 5000 IOPS, 200 MiB/s throughput, and 100 + GiB size. The second disk is a hyperdisk-throughput disk with 9000 + GiB size. + --worker-boot-disk-provisioned-iops=WORKER_BOOT_DISK_PROVISIONED_IOPS Indicates the IOPS (https://cloud.google.com/compute/docs/disks/hyperdisks#iops) to diff --git a/gcloud/alpha/design-center/spaces/application-templates/help b/gcloud/alpha/design-center/spaces/application-templates/help index f7cd17927..da5be249b 100644 --- a/gcloud/alpha/design-center/spaces/application-templates/help +++ b/gcloud/alpha/design-center/spaces/application-templates/help @@ -20,6 +20,9 @@ GROUPS components (ALPHA) Manage component resources. + policies + (ALPHA) Manage policy resources. + revisions (ALPHA) Manage application template revision resources. diff --git a/gcloud/alpha/design-center/spaces/application-templates/policies/create b/gcloud/alpha/design-center/spaces/application-templates/policies/create new file mode 100644 index 000000000..5d1434e04 --- /dev/null +++ b/gcloud/alpha/design-center/spaces/application-templates/policies/create @@ -0,0 +1,142 @@ +NAME + gcloud alpha design-center spaces application-templates policies create - + create a policy + +SYNOPSIS + gcloud alpha design-center spaces application-templates policies create + (POLICY : --application-template=APPLICATION_TEMPLATE + --location=LOCATION --space=SPACE) --policy-type=POLICY_TYPE + [--apply-conditions=[conditionKey=CONDITIONKEY], + [conditionValue=CONDITIONVALUE]] [--description=DESCRIPTION] + [--display-name=DISPLAY_NAME] + [--policy-revision-uri=POLICY_REVISION_URI | --policy-uri=POLICY_URI] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Create a policy for an application template. + +EXAMPLES + To create a policy my-policy for application template my-template in space + my-space with type COMPLIANCE_FRAMEWORK and URI https://example.com/policy, + run: + + $ gcloud alpha design-center spaces application-templates policies \ + create my-policy --application-template=my-template \ + --space=my-space --project=my-project --location=us-central1 \ + --policy-type=COMPLIANCE_FRAMEWORK \ + --policy-uri=https://example.com/policy + +POSITIONAL ARGUMENTS + Policy resource - Identifier. The policy name in the following format: + projects/$project/locations/$location/spaces/$space/applicationTemplates/$applicationTemplate/policies/$policy + The arguments in this group can be used to specify the attributes of this + resource. (NOTE) Some attributes are not given arguments in this group but + can be set in other ways. + + To set the project attribute: + ◆ provide the argument policy on the command line with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + POLICY + ID of the policy or fully qualified identifier for the policy. + + To set the policy attribute: + ▸ provide the argument policy on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --application-template=APPLICATION_TEMPLATE + The applicationTemplate id of the policy resource. + + To set the application-template attribute: + ▸ provide the argument policy on the command line with a fully + specified name; + ▸ provide the argument --application-template on the command line. + + --location=LOCATION + The location id of the policy resource. + + To set the location attribute: + ▸ provide the argument policy on the command line with a fully + specified name; + ▸ provide the argument --location on the command line. + + --space=SPACE + The space id of the policy resource. + + To set the space attribute: + ▸ provide the argument policy on the command line with a fully + specified name; + ▸ provide the argument --space on the command line. + +REQUIRED FLAGS + --policy-type=POLICY_TYPE + The policy type. Policy type will be used to determine the domain of + the policy. POLICY_TYPE must be (only one value is supported): + + compliance-framework + Compliance framework policy. + +OPTIONAL FLAGS + --apply-conditions=[conditionKey=CONDITIONKEY],[conditionValue=CONDITIONVALUE] + Conditions for applying the policy. Condition accepts AppTemplate + parameters like criticality, environment only. + + conditionKey + The key of the parameter for the condition. + + conditionValue + The value of the parameter for the condition. + + Shorthand Example: + + --apply-conditions=conditionKey=string,conditionValue=string --apply-conditions=conditionKey=string,conditionValue=string + + JSON Example: + + --apply-conditions='[{"conditionKey": "string", "conditionValue": "string"}]' + + File Example: + + --apply-conditions=path_to_file.(yaml|json) + + --description=DESCRIPTION + The policy description. + + --display-name=DISPLAY_NAME + The policy display name. + + Arguments for the uri. + + At most one of these can be specified: + + --policy-revision-uri=POLICY_REVISION_URI + URI of the policy revision. + + --policy-uri=POLICY_URI + URI of the policy. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the designcenter/v1alpha API. The full documentation for + this API can be found at: + http://cloud.google.com/application-design-center/docs + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/design-center/spaces/application-templates/policies/delete b/gcloud/alpha/design-center/spaces/application-templates/policies/delete new file mode 100644 index 000000000..8536cef5f --- /dev/null +++ b/gcloud/alpha/design-center/spaces/application-templates/policies/delete @@ -0,0 +1,87 @@ +NAME + gcloud alpha design-center spaces application-templates policies delete - + delete a policy + +SYNOPSIS + gcloud alpha design-center spaces application-templates policies delete + (POLICY : --application-template=APPLICATION_TEMPLATE + --location=LOCATION --space=SPACE) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Delete a policy from an application template. + +EXAMPLES + To delete the policy my-policy for application template my-template in + space my-space, run: + + $ gcloud alpha design-center spaces application-templates policies \ + delete my-policy --application-template=my-template \ + --space=my-space --project=my-project --location=us-central1 + +POSITIONAL ARGUMENTS + Policy resource - The policy name in the following format: + projects/$project/locations/$location/spaces/$space/applicationTemplates/$applicationTemplate/policies/$policy + The arguments in this group can be used to specify the attributes of this + resource. (NOTE) Some attributes are not given arguments in this group but + can be set in other ways. + + To set the project attribute: + ◆ provide the argument policy on the command line with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + POLICY + ID of the policy or fully qualified identifier for the policy. + + To set the policy attribute: + ▸ provide the argument policy on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --application-template=APPLICATION_TEMPLATE + The applicationTemplate id of the policy resource. + + To set the application-template attribute: + ▸ provide the argument policy on the command line with a fully + specified name; + ▸ provide the argument --application-template on the command line. + + --location=LOCATION + The location id of the policy resource. + + To set the location attribute: + ▸ provide the argument policy on the command line with a fully + specified name; + ▸ provide the argument --location on the command line. + + --space=SPACE + The space id of the policy resource. + + To set the space attribute: + ▸ provide the argument policy on the command line with a fully + specified name; + ▸ provide the argument --space 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 designcenter/v1alpha API. The full documentation for + this API can be found at: + http://cloud.google.com/application-design-center/docs + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/design-center/spaces/application-templates/policies/describe b/gcloud/alpha/design-center/spaces/application-templates/policies/describe new file mode 100644 index 000000000..f716d5fbc --- /dev/null +++ b/gcloud/alpha/design-center/spaces/application-templates/policies/describe @@ -0,0 +1,87 @@ +NAME + gcloud alpha design-center spaces application-templates policies describe - + describe a policy + +SYNOPSIS + gcloud alpha design-center spaces application-templates policies describe + (POLICY : --application-template=APPLICATION_TEMPLATE + --location=LOCATION --space=SPACE) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Describe a policy for an application template. + +EXAMPLES + To describe a policy my-policy for application template my-template in + space my-space, project my-project and location us-central1, run: + + $ gcloud alpha design-center spaces application-templates policies \ + describe my-policy --application-template=my-template \ + --space=my-space --project=my-project --location=us-central1 + +POSITIONAL ARGUMENTS + Policy resource - The policy name in the following format: + projects/$project/locations/$location/spaces/$space/applicationTemplates/$applicationTemplate/policies/$policy + The arguments in this group can be used to specify the attributes of this + resource. (NOTE) Some attributes are not given arguments in this group but + can be set in other ways. + + To set the project attribute: + ◆ provide the argument policy on the command line with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + POLICY + ID of the policy or fully qualified identifier for the policy. + + To set the policy attribute: + ▸ provide the argument policy on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --application-template=APPLICATION_TEMPLATE + The applicationTemplate id of the policy resource. + + To set the application-template attribute: + ▸ provide the argument policy on the command line with a fully + specified name; + ▸ provide the argument --application-template on the command line. + + --location=LOCATION + The location id of the policy resource. + + To set the location attribute: + ▸ provide the argument policy on the command line with a fully + specified name; + ▸ provide the argument --location on the command line. + + --space=SPACE + The space id of the policy resource. + + To set the space attribute: + ▸ provide the argument policy on the command line with a fully + specified name; + ▸ provide the argument --space 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 designcenter/v1alpha API. The full documentation for + this API can be found at: + http://cloud.google.com/application-design-center/docs + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/design-center/spaces/application-templates/policies/help b/gcloud/alpha/design-center/spaces/application-templates/policies/help new file mode 100644 index 000000000..b48981649 --- /dev/null +++ b/gcloud/alpha/design-center/spaces/application-templates/policies/help @@ -0,0 +1,40 @@ +NAME + gcloud alpha design-center spaces application-templates policies - manage + policy resources + +SYNOPSIS + gcloud alpha design-center spaces application-templates policies COMMAND + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Manage policy 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 + (ALPHA) Create a policy. + + delete + (ALPHA) Delete a policy. + + describe + (ALPHA) Describe a policy. + + list + (ALPHA) List policies. + + update + (ALPHA) Update a policy. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/design-center/spaces/application-templates/policies/list b/gcloud/alpha/design-center/spaces/application-templates/policies/list new file mode 100644 index 000000000..001274b5c --- /dev/null +++ b/gcloud/alpha/design-center/spaces/application-templates/policies/list @@ -0,0 +1,115 @@ +NAME + gcloud alpha design-center spaces application-templates policies list - + list policies + +SYNOPSIS + gcloud alpha design-center spaces application-templates policies list + (--application-template=APPLICATION_TEMPLATE + : --location=LOCATION --space=SPACE) [--filter=EXPRESSION] + [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) List policies for an application template. + +EXAMPLES + To list all policies for application template my-template in space + my-space, run: + + $ gcloud alpha design-center spaces application-templates policies \ + list --application-template=my-template --space=my-space \ + --project=my-project --location=us-central1 + +REQUIRED FLAGS + ApplicationTemplate resource - The parent application template from which + policies are listed in the following format: + projects/$project/locations/$location/spaces/$space/applicationTemplates/$applicationTemplate + 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 --application-template 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. + + --application-template=APPLICATION_TEMPLATE + ID of the applicationTemplate or fully qualified identifier for the + applicationTemplate. + + To set the application-template attribute: + ▸ provide the argument --application-template 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 applicationTemplate resource. + + To set the location attribute: + ▸ provide the argument --application-template on the command line + with a fully specified name; + ▸ provide the argument --location on the command line. + + --space=SPACE + The space id of the applicationTemplate resource. + + To set the space attribute: + ▸ provide the argument --application-template on the command line + with a fully specified name; + ▸ provide the argument --space 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 designcenter/v1alpha API. The full documentation for + this API can be found at: + http://cloud.google.com/application-design-center/docs + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/design-center/spaces/application-templates/policies/update b/gcloud/alpha/design-center/spaces/application-templates/policies/update new file mode 100644 index 000000000..91939fa80 --- /dev/null +++ b/gcloud/alpha/design-center/spaces/application-templates/policies/update @@ -0,0 +1,201 @@ +NAME + gcloud alpha design-center spaces application-templates policies update - + update a policy + +SYNOPSIS + gcloud alpha design-center spaces application-templates policies update + (POLICY : --application-template=APPLICATION_TEMPLATE + --location=LOCATION --space=SPACE) [--description=DESCRIPTION] + [--display-name=DISPLAY_NAME] [--policy-type=POLICY_TYPE] + [--apply-conditions=[conditionKey=CONDITIONKEY], + [conditionValue=CONDITIONVALUE] + | --add-apply-conditions=[conditionKey=CONDITIONKEY], + [conditionValue=CONDITIONVALUE] --clear-apply-conditions + | --remove-apply-conditions=[conditionKey=CONDITIONKEY], + [conditionValue=CONDITIONVALUE]] + [--policy-revision-uri=POLICY_REVISION_URI | --policy-uri=POLICY_URI] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Update a policy for an application template. + +EXAMPLES + To update the display name to My New Policy Name for the policy my-policy + in application template my-template and space my-space, run: + + $ gcloud alpha design-center spaces application-templates policies \ + update my-policy --application-template=my-template \ + --space=my-space --project=my-project --location=us-central1 \ + --display-name="My New Policy Name" + +POSITIONAL ARGUMENTS + Policy resource - Identifier. The policy name in the following format: + projects/$project/locations/$location/spaces/$space/applicationTemplates/$applicationTemplate/policies/$policy + The arguments in this group can be used to specify the attributes of this + resource. (NOTE) Some attributes are not given arguments in this group but + can be set in other ways. + + To set the project attribute: + ◆ provide the argument policy on the command line with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + POLICY + ID of the policy or fully qualified identifier for the policy. + + To set the policy attribute: + ▸ provide the argument policy on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --application-template=APPLICATION_TEMPLATE + The applicationTemplate id of the policy resource. + + To set the application-template attribute: + ▸ provide the argument policy on the command line with a fully + specified name; + ▸ provide the argument --application-template on the command line. + + --location=LOCATION + The location id of the policy resource. + + To set the location attribute: + ▸ provide the argument policy on the command line with a fully + specified name; + ▸ provide the argument --location on the command line. + + --space=SPACE + The space id of the policy resource. + + To set the space attribute: + ▸ provide the argument policy on the command line with a fully + specified name; + ▸ provide the argument --space on the command line. + +FLAGS + --description=DESCRIPTION + The policy description. + + --display-name=DISPLAY_NAME + The policy display name. + + --policy-type=POLICY_TYPE + The policy type. Policy type will be used to determine the domain of + the policy. POLICY_TYPE must be (only one value is supported): + + compliance-framework + Compliance framework policy. + + Update apply_conditions. + + At most one of these can be specified: + + --apply-conditions=[conditionKey=CONDITIONKEY],[conditionValue=CONDITIONVALUE] + Set apply_conditions to new value. Conditions for applying the + policy. Condition accepts AppTemplate parameters like criticality, + environment only. + + conditionKey + The key of the parameter for the condition. + + conditionValue + The value of the parameter for the condition. + + Shorthand Example: + + --apply-conditions=conditionKey=string,conditionValue=string --apply-conditions=conditionKey=string,conditionValue=string + + JSON Example: + + --apply-conditions='[{"conditionKey": "string", "conditionValue": "string"}]' + + File Example: + + --apply-conditions=path_to_file.(yaml|json) + + Or at least one of these can be specified: + + --add-apply-conditions=[conditionKey=CONDITIONKEY],[conditionValue=CONDITIONVALUE] + Add new value to apply_conditions list. Conditions for applying the + policy. Condition accepts AppTemplate parameters like criticality, + environment only. + + conditionKey + The key of the parameter for the condition. + + conditionValue + The value of the parameter for the condition. + + Shorthand Example: + + --add-apply-conditions=conditionKey=string,conditionValue=string --add-apply-conditions=conditionKey=string,conditionValue=string + + JSON Example: + + --add-apply-conditions='[{"conditionKey": "string", "conditionValue": "string"}]' + + File Example: + + --add-apply-conditions=path_to_file.(yaml|json) + + At most one of these can be specified: + + --clear-apply-conditions + Clear apply_conditions value and set to empty list. + + --remove-apply-conditions=[conditionKey=CONDITIONKEY],[conditionValue=CONDITIONVALUE] + Remove existing value from apply_conditions list. Conditions for + applying the policy. Condition accepts AppTemplate parameters + like criticality, environment only. + + conditionKey + The key of the parameter for the condition. + + conditionValue + The value of the parameter for the condition. + + Shorthand Example: + + --remove-apply-conditions=conditionKey=string,conditionValue=string --remove-apply-conditions=conditionKey=string,conditionValue=string + + JSON Example: + + --remove-apply-conditions='[{"conditionKey": "string", "conditionValue": "string"}]' + + File Example: + + --remove-apply-conditions=path_to_file.(yaml|json) + + Arguments for the uri. + + At most one of these can be specified: + + --policy-revision-uri=POLICY_REVISION_URI + URI of the policy revision. + + --policy-uri=POLICY_URI + URI of the policy. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the designcenter/v1alpha API. The full documentation for + this API can be found at: + http://cloud.google.com/application-design-center/docs + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/fault-testing/experiment-templates/create b/gcloud/alpha/fault-testing/experiment-templates/create new file mode 100644 index 000000000..2052b0174 --- /dev/null +++ b/gcloud/alpha/fault-testing/experiment-templates/create @@ -0,0 +1,160 @@ +NAME + gcloud alpha fault-testing experiment-templates create - create an + experiment template + +SYNOPSIS + gcloud alpha fault-testing experiment-templates create + (EXPERIMENT_TEMPLATE : --location=LOCATION) --duration=DURATION + (--cloud-sql-failover-instance=CLOUD_SQL_FAILOVER_INSTANCE + | [--l7-lb-http-fault-forwarding-rule=L7_LB_HTTP_FAULT_FORWARDING_RULE : --l7-lb-http-fault-backend-service=L7_LB_HTTP_FAULT_BACKEND_SERVICE --l7-lb-http-fault-abort-percentage=L7_LB_HTTP_FAULT_ABORT_PERCENTAGE --l7-lb-http-fault-abort-status-code=L7_LB_HTTP_FAULT_ABORT_STATUS_CODE | --l7-lb-http-fault-delay=L7_LB_HTTP_FAULT_DELAY --l7-lb-http-fault-delay-percentage=L7_LB_HTTP_FAULT_DELAY_PERCENTAGE]) + [--description=DESCRIPTION] [--display-name=DISPLAY_NAME] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Create an experiment template. + +EXAMPLES + To create an experiment template test-template-id in location asia-east1 + with display name test-template with a duration of 100s using Cloud SQL + failover instance test-cloud-sql-instance in project test-project run: + + $ gcloud alpha fault-testing experiment-templates create \ + test-template-id --location=asia-east1 \ + --display-name=test-template --duration=100s \ + --cloud-sql-failover-instance="projects/test-project/instances/t\ + est-cloud-sql-instance" + +POSITIONAL ARGUMENTS + ExperimentTemplate resource - Identifier. The resource name of this + experiment template. Format: + projects/{project}/locations/{location}/experimentTemplates/{experiment_template} + 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 experiment_template 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. + + EXPERIMENT_TEMPLATE + ID of the experimentTemplate or fully qualified identifier for the + experimentTemplate. + + To set the experiment_template attribute: + ▸ provide the argument experiment_template 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 experimentTemplate resource. + + To set the location attribute: + ▸ provide the argument experiment_template on the command line with + a fully specified name; + ▸ provide the argument --location on the command line. + +REQUIRED FLAGS + --duration=DURATION + How long the experiment is intended to run. Min duration is 0, max is + 10 days. + + The action to be performed by the experiment. + + This must be specified. + + Arguments for the action. + + At most one of these can be specified: + + CloudSQLFailover causes a Cloud SQL primary instance to fail over to + another instance. + + --cloud-sql-failover-instance=CLOUD_SQL_FAILOVER_INSTANCE + The identifying name of the Cloud SQL instance to fail over. + Format: projects/{project}/instances/{instance} + + Injection of HTTP faults into a layer 7 load balancer. + + --l7-lb-http-fault-forwarding-rule=L7_LB_HTTP_FAULT_FORWARDING_RULE + The identifying name of the forwarding rule resource where the + faults will be injected. Format: + projects/{project}/regions/{region}/forwardingRules/{forwarding_rule} + or projects/{project}/global/forwardingRules/{forwarding_rule} + + This flag argument must be specified if any of the other arguments + in this group are specified. + + --l7-lb-http-fault-backend-service=L7_LB_HTTP_FAULT_BACKEND_SERVICE + Optional identifying name of the backend service to inject faults + into. Format: + projects/{project}/regions/{region}/backendServices/{backend_service} + or projects/{project}/global/backendServices/{backend_service} If + not specified, all backend services connected to the + forwarding_rule will be affected. + + Arguments for the fault. + + At most one of these can be specified: + + Artificially return a specific HTTP status code for a percentage of + requests. + + --l7-lb-http-fault-abort-percentage=L7_LB_HTTP_FAULT_ABORT_PERCENTAGE + Percentage of requests to abort, in the range 0 to 100, + inclusive. + + This flag argument must be specified if any of the other + arguments in this group are specified. + + --l7-lb-http-fault-abort-status-code=L7_LB_HTTP_FAULT_ABORT_STATUS_CODE + HTTP status code to return. In the range 500 to 599, inclusive. + + This flag argument must be specified if any of the other + arguments in this group are specified. + + Artificially delay HTTP responses for a percentage of requests. + + --l7-lb-http-fault-delay=L7_LB_HTTP_FAULT_DELAY + Delay duration. + + This flag argument must be specified if any of the other + arguments in this group are specified. + + --l7-lb-http-fault-delay-percentage=L7_LB_HTTP_FAULT_DELAY_PERCENTAGE + Percentage of requests to delay, in the range 0 to 100, + inclusive. + + This flag argument must be specified if any of the other + arguments in this group are specified. + +OPTIONAL FLAGS + --description=DESCRIPTION + Optional user-provided description or notes. Min length 0. Max length + 2000. + + --display-name=DISPLAY_NAME + Human-readable template name. Min length 0, max 1000. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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 faulttesting/v1alpha API. The full documentation for + this API can be found at: + +NOTES + This command is currently in alpha and might change without notice. If this + command fails 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/fault-testing/experiment-templates/delete b/gcloud/alpha/fault-testing/experiment-templates/delete new file mode 100644 index 000000000..81240bf22 --- /dev/null +++ b/gcloud/alpha/fault-testing/experiment-templates/delete @@ -0,0 +1,70 @@ +NAME + gcloud alpha fault-testing experiment-templates delete - delete an + experiment template + +SYNOPSIS + gcloud alpha fault-testing experiment-templates delete + (EXPERIMENT_TEMPLATE : --location=LOCATION) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Delete an experiment template. + +EXAMPLES + To delete an experiment template test-template-id in location asia-east1 + run + + $ gcloud alpha fault-testing experiment-templates delete \ + test-template-id --location=asia-east1 + +POSITIONAL ARGUMENTS + ExperimentTemplate resource - The resource name of the experiment template + to delete. Format: + projects/{projectId}/locations/{location}/experimentTemplates/{experimentTemplateId}. + 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 experiment_template 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. + + EXPERIMENT_TEMPLATE + ID of the experimentTemplate or fully qualified identifier for the + experimentTemplate. + + To set the experiment_template attribute: + ▸ provide the argument experiment_template 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 experimentTemplate resource. + + To set the location attribute: + ▸ provide the argument experiment_template 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 faulttesting/v1alpha API. The full documentation for + this API can be found at: + +NOTES + This command is currently in alpha and might change without notice. If this + command fails 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/fault-testing/experiment-templates/describe b/gcloud/alpha/fault-testing/experiment-templates/describe new file mode 100644 index 000000000..ce34a7d9b --- /dev/null +++ b/gcloud/alpha/fault-testing/experiment-templates/describe @@ -0,0 +1,70 @@ +NAME + gcloud alpha fault-testing experiment-templates describe - describe a + single experiment template + +SYNOPSIS + gcloud alpha fault-testing experiment-templates describe + (EXPERIMENT_TEMPLATE : --location=LOCATION) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Describe a single experiment template. + +EXAMPLES + To describe an experiment template test-template-id in location asia-east1 + run + + $ gcloud alpha fault-testing experiment-templates describe \ + test-template-id --location=asia-east1 + +POSITIONAL ARGUMENTS + ExperimentTemplate resource - The resource name of the experiment template + to retrieve. Format: + projects/{projectId}/locations/{location}/experimentTemplates/{experimentTemplateId}. + 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 experiment_template 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. + + EXPERIMENT_TEMPLATE + ID of the experimentTemplate or fully qualified identifier for the + experimentTemplate. + + To set the experiment_template attribute: + ▸ provide the argument experiment_template 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 experimentTemplate resource. + + To set the location attribute: + ▸ provide the argument experiment_template 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 faulttesting/v1alpha API. The full documentation for + this API can be found at: + +NOTES + This command is currently in alpha and might change without notice. If this + command fails 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/fault-testing/experiment-templates/help b/gcloud/alpha/fault-testing/experiment-templates/help new file mode 100644 index 000000000..e3b3936ed --- /dev/null +++ b/gcloud/alpha/fault-testing/experiment-templates/help @@ -0,0 +1,40 @@ +NAME + gcloud alpha fault-testing experiment-templates - manage Experiment + Template resources + +SYNOPSIS + gcloud alpha fault-testing experiment-templates COMMAND + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Manage Experiment Template 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 + (ALPHA) Create an experiment template. + + delete + (ALPHA) Delete an experiment template. + + describe + (ALPHA) Describe a single experiment template. + + list + (ALPHA) List experiment templates. + + update + (ALPHA) Update an existing experiment template. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails 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/dataplex/data-taxonomies/list b/gcloud/alpha/fault-testing/experiment-templates/list similarity index 75% rename from gcloud/alpha/dataplex/data-taxonomies/list rename to gcloud/alpha/fault-testing/experiment-templates/list index 764091f10..6e1a51e14 100644 --- a/gcloud/alpha/dataplex/data-taxonomies/list +++ b/gcloud/alpha/fault-testing/experiment-templates/list @@ -1,38 +1,40 @@ NAME - gcloud alpha dataplex data-taxonomies list - list Data Taxonomies + gcloud alpha fault-testing experiment-templates list - list experiment + templates SYNOPSIS - gcloud alpha dataplex data-taxonomies list [--location=LOCATION] + gcloud alpha fault-testing experiment-templates list --location=LOCATION [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) List Data Taxonomies. + (ALPHA) List experiment templates. EXAMPLES - To List Data Taxonomies in project test-dataplex at location us-central1 + To list all experiment templates in location asia-east1 run - $ gcloud alpha dataplex data-taxonomies list \ - --location=us-central1 --project=test-dataplex + $ gcloud alpha fault-testing experiment-templates list \ + --location=asia-east1 -FLAGS - Location resource - Location in which to list Data Taxonomies. This +REQUIRED FLAGS + Location resource - The project and location from which to list experiment + templates. Format: projects/{project}/locations/{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 dataplex/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. + This must be specified. - To set the location attribute: - ◆ provide the argument --location on the command line; - ◆ set the property dataplex/location. + --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 @@ -75,8 +77,8 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. API REFERENCE - This command uses the dataplex/v1 API. The full documentation for this API - can be found at: https://cloud.google.com/dataplex/docs + This command uses the faulttesting/v1alpha API. The full documentation for + this API can be found at: NOTES This command is currently in alpha and might change without notice. If this diff --git a/gcloud/alpha/fault-testing/experiment-templates/update b/gcloud/alpha/fault-testing/experiment-templates/update new file mode 100644 index 000000000..1043079d1 --- /dev/null +++ b/gcloud/alpha/fault-testing/experiment-templates/update @@ -0,0 +1,144 @@ +NAME + gcloud alpha fault-testing experiment-templates update - update an existing + experiment template + +SYNOPSIS + gcloud alpha fault-testing experiment-templates update + (EXPERIMENT_TEMPLATE : --location=LOCATION) [--description=DESCRIPTION] + [--display-name=DISPLAY_NAME] [--duration=DURATION] + [--clear-action + --cloud-sql-failover-instance=CLOUD_SQL_FAILOVER_INSTANCE + | --l7-lb-http-fault-backend-service=L7_LB_HTTP_FAULT_BACKEND_SERVICE + --l7-lb-http-fault-forwarding-rule=L7_LB_HTTP_FAULT_FORWARDING_RULE + --l7-lb-http-fault-abort-percentage=L7_LB_HTTP_FAULT_ABORT_PERCENTAGE + --l7-lb-http-fault-abort-status-code=L7_LB_HTTP_FAULT_ABORT_STATUS_CODE | --l7-lb-http-fault-delay=L7_LB_HTTP_FAULT_DELAY --l7-lb-http-fault-delay-percentage=L7_LB_HTTP_FAULT_DELAY_PERCENTAGE] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Update an existing experiment template. + +EXAMPLES + To update the display name and duration of an experiment template + test-template-id located in asia-east1 run: + + $ gcloud alpha fault-testing experiment-templates update \ + test-template-id --location=asia-east1 \ + --display-name=test-template-new-name --duration=200s + +POSITIONAL ARGUMENTS + ExperimentTemplate resource - Identifier. The resource name of this + experiment template. Format: + projects/{project}/locations/{location}/experimentTemplates/{experiment_template} + 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 experiment_template 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. + + EXPERIMENT_TEMPLATE + ID of the experimentTemplate or fully qualified identifier for the + experimentTemplate. + + To set the experiment_template attribute: + ▸ provide the argument experiment_template 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 experimentTemplate resource. + + To set the location attribute: + ▸ provide the argument experiment_template on the command line with + a fully specified name; + ▸ provide the argument --location on the command line. + +FLAGS + --description=DESCRIPTION + Optional user-provided description or notes. Min length 0. Max length + 2000. + + --display-name=DISPLAY_NAME + Human-readable template name. Min length 0, max 1000. + + --duration=DURATION + How long the experiment is intended to run. Min duration is 0, max is + 10 days. + + The action to be performed by the experiment. + + --clear-action + Set experimentTemplate.action back to default value. + + Arguments for the action. + + At most one of these can be specified: + + CloudSQLFailover causes a Cloud SQL primary instance to fail over to + another instance. + + --cloud-sql-failover-instance=CLOUD_SQL_FAILOVER_INSTANCE + The identifying name of the Cloud SQL instance to fail over. Format: + projects/{project}/instances/{instance} + + Injection of HTTP faults into a layer 7 load balancer. + + --l7-lb-http-fault-backend-service=L7_LB_HTTP_FAULT_BACKEND_SERVICE + Optional identifying name of the backend service to inject faults + into. Format: + projects/{project}/regions/{region}/backendServices/{backend_service} + or projects/{project}/global/backendServices/{backend_service} If not + specified, all backend services connected to the forwarding_rule will + be affected. + + --l7-lb-http-fault-forwarding-rule=L7_LB_HTTP_FAULT_FORWARDING_RULE + The identifying name of the forwarding rule resource where the faults + will be injected. Format: + projects/{project}/regions/{region}/forwardingRules/{forwarding_rule} + or projects/{project}/global/forwardingRules/{forwarding_rule} + + Arguments for the fault. + + At most one of these can be specified: + + Artificially return a specific HTTP status code for a percentage of + requests. + + --l7-lb-http-fault-abort-percentage=L7_LB_HTTP_FAULT_ABORT_PERCENTAGE + Percentage of requests to abort, in the range 0 to 100, inclusive. + + --l7-lb-http-fault-abort-status-code=L7_LB_HTTP_FAULT_ABORT_STATUS_CODE + HTTP status code to return. In the range 500 to 599, inclusive. + + Artificially delay HTTP responses for a percentage of requests. + + --l7-lb-http-fault-delay=L7_LB_HTTP_FAULT_DELAY + Delay duration. + + --l7-lb-http-fault-delay-percentage=L7_LB_HTTP_FAULT_DELAY_PERCENTAGE + Percentage of requests to delay, in the range 0 to 100, inclusive. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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 faulttesting/v1alpha API. The full documentation for + this API can be found at: + +NOTES + This command is currently in alpha and might change without notice. If this + command fails 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/fault-testing/experiments/affected-resources/describe b/gcloud/alpha/fault-testing/experiments/affected-resources/describe new file mode 100644 index 000000000..701923842 --- /dev/null +++ b/gcloud/alpha/fault-testing/experiments/affected-resources/describe @@ -0,0 +1,79 @@ +NAME + gcloud alpha fault-testing experiments affected-resources describe - + describe an affected resource + +SYNOPSIS + gcloud alpha fault-testing experiments affected-resources describe + (AFFECTED_RESOURCE : --experiment=EXPERIMENT --location=LOCATION) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Describe an affected resource. + +EXAMPLES + To describe an affected resource test-affected-resource-id associated with + experiment test-experiment-id in location asia-east1 run + + $ gcloud alpha fault-testing experiments affected-resources \ describe test-affected-resource-id \ + --experiment=test-experiment-id --location=asia-east1 + +POSITIONAL ARGUMENTS + AffectedResource resource - The resource name of the affected resource. + Format: + projects/{projectId}/locations/{location}/experiments/{experimentId}/affectedResources/{affectedResourceId}. + 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 affected_resource 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. + + AFFECTED_RESOURCE + ID of the affectedResource or fully qualified identifier for the + affectedResource. + + To set the affected_resource attribute: + ▸ provide the argument affected_resource on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --experiment=EXPERIMENT + The experiment id of the affectedResource resource. + + To set the experiment attribute: + ▸ provide the argument affected_resource on the command line with a + fully specified name; + ▸ provide the argument --experiment on the command line. + + --location=LOCATION + The location id of the affectedResource resource. + + To set the location attribute: + ▸ provide the argument affected_resource 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 faulttesting/v1alpha API. The full documentation for + this API can be found at: + +NOTES + This command is currently in alpha and might change without notice. If this + command fails 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/fault-testing/experiments/affected-resources/help b/gcloud/alpha/fault-testing/experiments/affected-resources/help new file mode 100644 index 000000000..083e0cae0 --- /dev/null +++ b/gcloud/alpha/fault-testing/experiments/affected-resources/help @@ -0,0 +1,31 @@ +NAME + gcloud alpha fault-testing experiments affected-resources - manage Affected + Resource resources + +SYNOPSIS + gcloud alpha fault-testing experiments affected-resources COMMAND + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Manage Affected Resource resources. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + describe + (ALPHA) Describe an affected resource. + + list + (ALPHA) List affected resources. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/dataplex/data-taxonomies/attributes/list b/gcloud/alpha/fault-testing/experiments/affected-resources/list similarity index 64% rename from gcloud/alpha/dataplex/data-taxonomies/attributes/list rename to gcloud/alpha/fault-testing/experiments/affected-resources/list index 60cc5a6d0..20dd5a4d6 100644 --- a/gcloud/alpha/dataplex/data-taxonomies/attributes/list +++ b/gcloud/alpha/fault-testing/experiments/affected-resources/list @@ -1,56 +1,56 @@ NAME - gcloud alpha dataplex data-taxonomies attributes list - list Data - Attributes within provided Data Taxonomy + gcloud alpha fault-testing experiments affected-resources list - list + affected resources SYNOPSIS - gcloud alpha dataplex data-taxonomies attributes list - (--data_taxonomy=DATA_TAXONOMY : --location=LOCATION) - [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] - [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + gcloud alpha fault-testing experiments affected-resources list + (--experiment=EXPERIMENT : --location=LOCATION) [--filter=EXPRESSION] + [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) List Data Attributes within provided Data Taxonomy. + (ALPHA) List affected resources. EXAMPLES - To List Data Attribute test-attribute for Data Taxonomy test-datataxonomy - in project test-dataplex at location us-central1, run: + To list all affected resources associated with experiment + test-experiment-id in location asia-east1 run - $ gcloud alpha dataplex data-taxonomies attributes list \ - test-attribute --location=us-central1 --project=test-dataplex \ - --data_taxonomy=test-datataxonomy + $ gcloud alpha fault-testing experiments affected-resources list \ + --experiment=test-experiment-id --location=asia-east1 REQUIRED FLAGS - Data taxonomy resource - Data Taxonomy in which to list Data Attributes. - The arguments in this group can be used to specify the attributes of this + Experiment resource - The Experiment from which to list affected + resources. Format: + projects/{projectId}/locations/{location}/experiments/{experimentId}. 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_taxonomy on the command line with a fully + ◆ provide the argument --experiment 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_taxonomy=DATA_TAXONOMY - ID of the data taxonomy or fully qualified identifier for the data - taxonomy. + --experiment=EXPERIMENT + ID of the experiment or fully qualified identifier for the + experiment. - To set the data_taxonomy attribute: - ▸ provide the argument --data_taxonomy on the command line. + To set the experiment attribute: + ▸ provide the argument --experiment on the command line. This flag argument must be specified if any of the other arguments in this group are specified. --location=LOCATION - Location of the Dataplex resource. + The location id of the experiment resource. To set the location attribute: - ▸ provide the argument --data_taxonomy on the command line with a + ▸ provide the argument --experiment on the command line with a fully specified name; - ▸ provide the argument --location on the command line; - ▸ set the property dataplex/location. + ▸ provide the argument --location on the command line. LIST COMMAND FLAGS --filter=EXPRESSION @@ -93,8 +93,8 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. API REFERENCE - This command uses the dataplex/v1 API. The full documentation for this API - can be found at: https://cloud.google.com/dataplex/docs + This command uses the faulttesting/v1alpha API. The full documentation for + this API can be found at: NOTES This command is currently in alpha and might change without notice. If this diff --git a/gcloud/alpha/fault-testing/experiments/create b/gcloud/alpha/fault-testing/experiments/create new file mode 100644 index 000000000..2ada624b0 --- /dev/null +++ b/gcloud/alpha/fault-testing/experiments/create @@ -0,0 +1,107 @@ +NAME + gcloud alpha fault-testing experiments create - create an experiment + +SYNOPSIS + gcloud alpha fault-testing experiments create EXPERIMENT + --experiment-template=EXPERIMENT_TEMPLATE [--description=DESCRIPTION] + [--display-name=DISPLAY_NAME] [--location=LOCATION] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Create an experiment. + +EXAMPLES + To create an experiment test-experiment-id associated with experiment + template test-template-id in location asia-east1 with display name + test-experiment run: + + $ gcloud alpha fault-testing experiments create test-experiment-id \ + --experiment-template=test-template-id --location=asia-east1 \ + --display-name=test-experiment + +POSITIONAL ARGUMENTS + Experiment resource - Identifier. Unique identifier for the experiment. + Format: + projects/{project_id}/locations/{location}/experiments/{experiment_id}. + 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 experiment 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 experiment on the command line with a fully + specified name; + ◆ provide the argument --location on the command line. + + This must be specified. + + EXPERIMENT + ID of the experiment or fully qualified identifier for the + experiment. + + To set the experiment attribute: + ▸ provide the argument experiment on the command line. + +REQUIRED FLAGS + ExperimentTemplate resource - The unique identifier of the reusable + experiment template used to configure the experiment. This field + determines the type of fault, target, and duration. Format: + projects/{project_id}/locations/{location}/experimentTemplates/{experimentTemplateId}. + 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 --experiment-template 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 --experiment-template on the command line with a + fully specified name; + ◆ provide the argument --location on the command line. + + This must be specified. + + --experiment-template=EXPERIMENT_TEMPLATE + ID of the experimentTemplate or fully qualified identifier for the + experimentTemplate. + + To set the experiment-template attribute: + ▸ provide the argument --experiment-template on the command line. + +OPTIONAL FLAGS + --description=DESCRIPTION + Notes or details to describe the purpose or context of the experiment. + Minimum length is 0, maximum length is 2000. + + --display-name=DISPLAY_NAME + A human-readable name of the experiment. + + --location=LOCATION + For resources [experiment, experiment-template], 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 faulttesting/v1alpha API. The full documentation for + this API can be found at: + +NOTES + This command is currently in alpha and might change without notice. If this + command fails 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/fault-testing/experiments/delete b/gcloud/alpha/fault-testing/experiments/delete new file mode 100644 index 000000000..18df10866 --- /dev/null +++ b/gcloud/alpha/fault-testing/experiments/delete @@ -0,0 +1,74 @@ +NAME + gcloud alpha fault-testing experiments delete - delete an experiment + +SYNOPSIS + gcloud alpha fault-testing experiments delete + (EXPERIMENT : --location=LOCATION) [--force] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Delete an experiment + +EXAMPLES + To delete an experiment test-experiment-id in location asia-east1 run: + + $ gcloud alpha fault-testing experiments delete test-experiment-id \ + --location=asia-east1 --force + +POSITIONAL ARGUMENTS + Experiment resource - The resource name of the experiment to delete. + Format: + projects/{projectId}/locations/{location}/experiments/{experimentId}. 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 experiment 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. + + EXPERIMENT + ID of the experiment or fully qualified identifier for the + experiment. + + To set the experiment attribute: + ▸ provide the argument experiment 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 experiment resource. + + To set the location attribute: + ▸ provide the argument experiment on the command line with a fully + specified name; + ▸ provide the argument --location on the command line. + +FLAGS + --force + Should always be set to true. If set to true, any affected resources + under this experiment will also be deleted. Otherwise, the request will + only work if the experiment has no affected resources. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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 faulttesting/v1alpha API. The full documentation for + this API can be found at: + +NOTES + This command is currently in alpha and might change without notice. If this + command fails 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/dataplex/data-taxonomies/describe b/gcloud/alpha/fault-testing/experiments/describe similarity index 50% rename from gcloud/alpha/dataplex/data-taxonomies/describe rename to gcloud/alpha/fault-testing/experiments/describe index 5745a1545..71514e2c4 100644 --- a/gcloud/alpha/dataplex/data-taxonomies/describe +++ b/gcloud/alpha/fault-testing/experiments/describe @@ -1,53 +1,53 @@ NAME - gcloud alpha dataplex data-taxonomies describe - describe a Data Taxonomy + gcloud alpha fault-testing experiments describe - describe a current or + past experiment SYNOPSIS - gcloud alpha dataplex data-taxonomies describe - (DATA_TAXONOMY : --location=LOCATION) [GCLOUD_WIDE_FLAG ...] + gcloud alpha fault-testing experiments describe + (EXPERIMENT : --location=LOCATION) [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) Describe a Data Taxonomy. Displays all details of a Data Taxonomy - given a valid Data Taxonomy ID. + (ALPHA) Describe a current or past experiment. EXAMPLES - To describe a Dataplex Data Taxonomy test-taxonomy within location - us-central1 and in project test-project + To describe an experiment test-experiment-id in location asia-east1 run: - $ gcloud alpha dataplex data-taxonomies describe test-taxonomy \ - --location=us-central1 --project=test-project + $ gcloud alpha fault-testing experiments describe \ + test-experiment-id --location=asia-east1 POSITIONAL ARGUMENTS - Data taxonomy resource - Data Taxonomies you want to describe. The + Experiment resource - The resource name of the experiment to retrieve. + Format: + projects/{projectId}/locations/{location}/experiments/{experimentId}. 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_taxonomy on the command line with a fully + ◆ provide the argument experiment 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_TAXONOMY - ID of the data taxonomy or fully qualified identifier for the data - taxonomy. + EXPERIMENT + ID of the experiment or fully qualified identifier for the + experiment. - To set the data_taxonomy attribute: - ▸ provide the argument data_taxonomy on the command line. + To set the experiment attribute: + ▸ provide the argument experiment on the command line. This positional argument must be specified if any of the other arguments in this group are specified. --location=LOCATION - Location of the Dataplex resource. + The location id of the experiment resource. To set the location attribute: - ▸ provide the argument data_taxonomy on the command line with a - fully specified name; - ▸ provide the argument --location on the command line; - ▸ set the property dataplex/location. + ▸ provide the argument experiment 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, @@ -58,8 +58,8 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. API REFERENCE - This command uses the dataplex/v1 API. The full documentation for this API - can be found at: https://cloud.google.com/dataplex/docs + This command uses the faulttesting/v1alpha API. The full documentation for + this API can be found at: NOTES This command is currently in alpha and might change without notice. If this diff --git a/gcloud/alpha/fault-testing/experiments/help b/gcloud/alpha/fault-testing/experiments/help new file mode 100644 index 000000000..fdf14c5b4 --- /dev/null +++ b/gcloud/alpha/fault-testing/experiments/help @@ -0,0 +1,51 @@ +NAME + gcloud alpha fault-testing experiments - manage Experiment resources + +SYNOPSIS + gcloud alpha fault-testing experiments GROUP | COMMAND + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Manage Experiment resources. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +GROUPS + GROUP is one of the following: + + affected-resources + (ALPHA) Manage Affected Resource resources. + +COMMANDS + COMMAND is one of the following: + + create + (ALPHA) Create an experiment. + + delete + (ALPHA) Delete an experiment. + + describe + (ALPHA) Describe a current or past experiment. + + list + (ALPHA) List current or past experiments. + + start + (ALPHA) Start a new experiment run. + + stop + (ALPHA) Cancel a running experiment. + + stop-all + (ALPHA) Cancel all experiments in a given location. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails 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/fault-testing/experiments/list b/gcloud/alpha/fault-testing/experiments/list new file mode 100644 index 000000000..c801d6c25 --- /dev/null +++ b/gcloud/alpha/fault-testing/experiments/list @@ -0,0 +1,87 @@ +NAME + gcloud alpha fault-testing experiments list - list current or past + experiments + +SYNOPSIS + gcloud alpha fault-testing experiments list --location=LOCATION + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) List current or past experiments. + +EXAMPLES + To list experiments in location asia-east1 run + + $ gcloud alpha fault-testing experiments list --location=asia-east1 + +REQUIRED FLAGS + Location resource - The project and location from which to list + experiments. Format: projects/{projectId}/locations/{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; + ◆ 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 faulttesting/v1alpha API. The full documentation for + this API can be found at: + +NOTES + This command is currently in alpha and might change without notice. If this + command fails 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/fault-testing/experiments/start b/gcloud/alpha/fault-testing/experiments/start new file mode 100644 index 000000000..a2b645e22 --- /dev/null +++ b/gcloud/alpha/fault-testing/experiments/start @@ -0,0 +1,68 @@ +NAME + gcloud alpha fault-testing experiments start - start a new experiment run + +SYNOPSIS + gcloud alpha fault-testing experiments start + (EXPERIMENT : --location=LOCATION) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Start a new experiment run. + +EXAMPLES + To start an experiment test-experiment-id in location asia-east1 run + + $ gcloud alpha fault-testing experiments start test-experiment-id \ + --location=asia-east1 + +POSITIONAL ARGUMENTS + Experiment resource - The resource name of the experiment to start. + Format: + projects/{projectId}/locations/{location}/experiments/{experimentId}. 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 experiment 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. + + EXPERIMENT + ID of the experiment or fully qualified identifier for the + experiment. + + To set the experiment attribute: + ▸ provide the argument experiment 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 experiment resource. + + To set the location attribute: + ▸ provide the argument experiment 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 faulttesting/v1alpha API. The full documentation for + this API can be found at: + +NOTES + This command is currently in alpha and might change without notice. If this + command fails 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/fault-testing/experiments/stop b/gcloud/alpha/fault-testing/experiments/stop new file mode 100644 index 000000000..d705b6261 --- /dev/null +++ b/gcloud/alpha/fault-testing/experiments/stop @@ -0,0 +1,67 @@ +NAME + gcloud alpha fault-testing experiments stop - cancel a running experiment + +SYNOPSIS + gcloud alpha fault-testing experiments stop + (EXPERIMENT : --location=LOCATION) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Cancel a running experiment. + +EXAMPLES + To stop an experiment test-experiment-id in location asia-east1 run + + $ gcloud alpha fault-testing experiments stop test-experiment-id \ + --location=asia-east1 + +POSITIONAL ARGUMENTS + Experiment resource - The resource name of the experiment to stop. Format: + projects/{projectId}/locations/{location}/experiments/{experimentId}. 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 experiment 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. + + EXPERIMENT + ID of the experiment or fully qualified identifier for the + experiment. + + To set the experiment attribute: + ▸ provide the argument experiment 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 experiment resource. + + To set the location attribute: + ▸ provide the argument experiment 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 faulttesting/v1alpha API. The full documentation for + this API can be found at: + +NOTES + This command is currently in alpha and might change without notice. If this + command fails 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/fault-testing/experiments/stop-all b/gcloud/alpha/fault-testing/experiments/stop-all new file mode 100644 index 000000000..3a100d43d --- /dev/null +++ b/gcloud/alpha/fault-testing/experiments/stop-all @@ -0,0 +1,56 @@ +NAME + gcloud alpha fault-testing experiments stop-all - cancel all experiments in + a given location + +SYNOPSIS + gcloud alpha fault-testing experiments stop-all --location=LOCATION + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Cancels all experiments in a given location that are not already + stopping or stopped. + +EXAMPLES + To stop experiments in location asia-east1 run + + $ gcloud alpha fault-testing experiments stop-all \ + --location=asia-east1 + +REQUIRED FLAGS + Location resource - The project and location where all experiments will be + stopped. Format: projects/{projectId}/locations/{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; + ◆ 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. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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 faulttesting/v1alpha API. The full documentation for + this API can be found at: + +NOTES + This command is currently in alpha and might change without notice. If this + command fails 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/fault-testing/help b/gcloud/alpha/fault-testing/help new file mode 100644 index 000000000..bf81db9c5 --- /dev/null +++ b/gcloud/alpha/fault-testing/help @@ -0,0 +1,32 @@ +NAME + gcloud alpha fault-testing - manage Fault Testing resources + +SYNOPSIS + gcloud alpha fault-testing GROUP [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Manage Fault Testing resources. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +GROUPS + GROUP is one of the following: + + experiment-templates + (ALPHA) Manage Experiment Template resources. + + experiments + (ALPHA) Manage Experiment resources. + + validations + (ALPHA) Manage Validation resources. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/fault-testing/validations/create b/gcloud/alpha/fault-testing/validations/create new file mode 100644 index 000000000..911ec5e64 --- /dev/null +++ b/gcloud/alpha/fault-testing/validations/create @@ -0,0 +1,154 @@ +NAME + gcloud alpha fault-testing validations create - create a validation + +SYNOPSIS + gcloud alpha fault-testing validations create + (VALIDATION : --location=LOCATION) + (--cloud-sql-failover-instance=CLOUD_SQL_FAILOVER_INSTANCE + | [--l7-lb-http-fault-forwarding-rule=L7_LB_HTTP_FAULT_FORWARDING_RULE : --l7-lb-http-fault-backend-service=L7_LB_HTTP_FAULT_BACKEND_SERVICE --l7-lb-http-fault-abort-percentage=L7_LB_HTTP_FAULT_ABORT_PERCENTAGE --l7-lb-http-fault-abort-status-code=L7_LB_HTTP_FAULT_ABORT_STATUS_CODE | --l7-lb-http-fault-delay=L7_LB_HTTP_FAULT_DELAY --l7-lb-http-fault-delay-percentage=L7_LB_HTTP_FAULT_DELAY_PERCENTAGE]) + [--description=DESCRIPTION] [--display-name=DISPLAY_NAME] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Create a new validation. + +EXAMPLES + To create a validation test-validation-id in location asia-east1 using + Cloud SQL failover instance test-cloud-sql-instance in project test-project + run: + + $ gcloud alpha fault-testing validations create test-validation-id \ + --location=asia-east1 \ + --cloud-sql-failover-instance="projects/test-project/instances/t\ + est-cloud-sql-instance" + +POSITIONAL ARGUMENTS + Validation resource - Identifier. Unique identifier for the Validation dry + run. Format: + projects/{project_id}/locations/{location}/validations/{validationId}. 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 validation 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. + + VALIDATION + ID of the validation or fully qualified identifier for the + validation. + + To set the validation attribute: + ▸ provide the argument validation 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 validation resource. + + To set the location attribute: + ▸ provide the argument validation on the command line with a fully + specified name; + ▸ provide the argument --location on the command line. + +REQUIRED FLAGS + The action to be performed by the experiment. + + This must be specified. + + Arguments for the action. + + At most one of these can be specified: + + CloudSQLFailover causes a Cloud SQL primary instance to fail over to + another instance. + + --cloud-sql-failover-instance=CLOUD_SQL_FAILOVER_INSTANCE + The identifying name of the Cloud SQL instance to fail over. + Format: projects/{project}/instances/{instance} + + Injection of HTTP faults into a layer 7 load balancer. + + --l7-lb-http-fault-forwarding-rule=L7_LB_HTTP_FAULT_FORWARDING_RULE + The identifying name of the forwarding rule resource where the + faults will be injected. Format: + projects/{project}/regions/{region}/forwardingRules/{forwarding_rule} + or projects/{project}/global/forwardingRules/{forwarding_rule} + + This flag argument must be specified if any of the other arguments + in this group are specified. + + --l7-lb-http-fault-backend-service=L7_LB_HTTP_FAULT_BACKEND_SERVICE + Optional identifying name of the backend service to inject faults + into. Format: + projects/{project}/regions/{region}/backendServices/{backend_service} + or projects/{project}/global/backendServices/{backend_service} If + not specified, all backend services connected to the + forwarding_rule will be affected. + + Arguments for the fault. + + At most one of these can be specified: + + Artificially return a specific HTTP status code for a percentage of + requests. + + --l7-lb-http-fault-abort-percentage=L7_LB_HTTP_FAULT_ABORT_PERCENTAGE + Percentage of requests to abort, in the range 0 to 100, + inclusive. + + This flag argument must be specified if any of the other + arguments in this group are specified. + + --l7-lb-http-fault-abort-status-code=L7_LB_HTTP_FAULT_ABORT_STATUS_CODE + HTTP status code to return. In the range 500 to 599, inclusive. + + This flag argument must be specified if any of the other + arguments in this group are specified. + + Artificially delay HTTP responses for a percentage of requests. + + --l7-lb-http-fault-delay=L7_LB_HTTP_FAULT_DELAY + Delay duration. + + This flag argument must be specified if any of the other + arguments in this group are specified. + + --l7-lb-http-fault-delay-percentage=L7_LB_HTTP_FAULT_DELAY_PERCENTAGE + Percentage of requests to delay, in the range 0 to 100, + inclusive. + + This flag argument must be specified if any of the other + arguments in this group are specified. + +OPTIONAL FLAGS + --description=DESCRIPTION + Notes or details about the Validation dry run. Minimum length is 0, + maximum length is 2000. + + --display-name=DISPLAY_NAME + A human-readable name of the Validation dry run. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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 faulttesting/v1alpha API. The full documentation for + this API can be found at: + +NOTES + This command is currently in alpha and might change without notice. If this + command fails 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/fault-testing/validations/delete b/gcloud/alpha/fault-testing/validations/delete new file mode 100644 index 000000000..494fb27f6 --- /dev/null +++ b/gcloud/alpha/fault-testing/validations/delete @@ -0,0 +1,73 @@ +NAME + gcloud alpha fault-testing validations delete - delete a validation + +SYNOPSIS + gcloud alpha fault-testing validations delete + (VALIDATION : --location=LOCATION) [--force] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Delete a validation. + +EXAMPLES + To delete a validation test-validation-id in location asia-east1 run: + + $ gcloud alpha fault-testing validations delete test-validation-id \ + --location=asia-east1 --force + +POSITIONAL ARGUMENTS + Validation resource - The resource name of the dry run to delete. Format: + projects/{projectId}/locations/{location}/validations/{validationId}. 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 validation 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. + + VALIDATION + ID of the validation or fully qualified identifier for the + validation. + + To set the validation attribute: + ▸ provide the argument validation 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 validation resource. + + To set the location attribute: + ▸ provide the argument validation on the command line with a fully + specified name; + ▸ provide the argument --location on the command line. + +FLAGS + --force + Should always be set to true. If set to true, any ValidationResource`s + under this Validation will also be deleted. Otherwise, the request will + only work if the Validation has no ValidationResource`s. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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 faulttesting/v1alpha API. The full documentation for + this API can be found at: + +NOTES + This command is currently in alpha and might change without notice. If this + command fails 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/fault-testing/validations/describe b/gcloud/alpha/fault-testing/validations/describe new file mode 100644 index 000000000..064535a1a --- /dev/null +++ b/gcloud/alpha/fault-testing/validations/describe @@ -0,0 +1,68 @@ +NAME + gcloud alpha fault-testing validations describe - describe a validation + +SYNOPSIS + gcloud alpha fault-testing validations describe + (VALIDATION : --location=LOCATION) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Describe a single validation. + +EXAMPLES + To describe a validation test-validation-id in location asia-east1 run: + + $ gcloud alpha fault-testing validations describe \ + test-validation-id --location=asia-east1 + +POSITIONAL ARGUMENTS + Validation resource - The resource name of the dry run to retrieve. + Format: + projects/{projectId}/locations/{location}/validations/{validationId}. 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 validation 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. + + VALIDATION + ID of the validation or fully qualified identifier for the + validation. + + To set the validation attribute: + ▸ provide the argument validation 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 validation resource. + + To set the location attribute: + ▸ provide the argument validation 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 faulttesting/v1alpha API. The full documentation for + this API can be found at: + +NOTES + This command is currently in alpha and might change without notice. If this + command fails 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/fault-testing/validations/help b/gcloud/alpha/fault-testing/validations/help new file mode 100644 index 000000000..04e3c0cb6 --- /dev/null +++ b/gcloud/alpha/fault-testing/validations/help @@ -0,0 +1,42 @@ +NAME + gcloud alpha fault-testing validations - manage Validation resources + +SYNOPSIS + gcloud alpha fault-testing validations GROUP | COMMAND + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Manage Validation resources. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +GROUPS + GROUP is one of the following: + + validation-resources + (ALPHA) Manage Validation Resource resources. + +COMMANDS + COMMAND is one of the following: + + create + (ALPHA) Create a validation. + + delete + (ALPHA) Delete a validation. + + describe + (ALPHA) Describe a validation. + + list + (ALPHA) List validations. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails 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/fault-testing/validations/list b/gcloud/alpha/fault-testing/validations/list new file mode 100644 index 000000000..23b730ee5 --- /dev/null +++ b/gcloud/alpha/fault-testing/validations/list @@ -0,0 +1,86 @@ +NAME + gcloud alpha fault-testing validations list - list validations + +SYNOPSIS + gcloud alpha fault-testing validations list --location=LOCATION + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) List validations. + +EXAMPLES + To list all validations in location asia-east1 run: + + $ gcloud alpha fault-testing validations list --location=asia-east1 + +REQUIRED FLAGS + Location resource - The project and location from which to list dry runs. + Format: projects/{projectId}/locations/{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; + ◆ 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 faulttesting/v1alpha API. The full documentation for + this API can be found at: + +NOTES + This command is currently in alpha and might change without notice. If this + command fails 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/fault-testing/validations/validation-resources/describe b/gcloud/alpha/fault-testing/validations/validation-resources/describe new file mode 100644 index 000000000..3e95599ce --- /dev/null +++ b/gcloud/alpha/fault-testing/validations/validation-resources/describe @@ -0,0 +1,78 @@ +NAME + gcloud alpha fault-testing validations validation-resources describe - + describe validationResources + +SYNOPSIS + gcloud alpha fault-testing validations validation-resources describe + (VALIDATION_RESOURCE : --location=LOCATION --validation=VALIDATION) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Describe a validationResource + +EXAMPLES + To describe the validationResource, run: + + $ gcloud alpha fault-testing validations validation-resources \ + describe + +POSITIONAL ARGUMENTS + ValidationResource resource - The resource name of the validation resource + to retrieve. Format: + projects/{projectId}/locations/{location}/validations/{validationId}/validationResources/{validationResourceId}. + 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 validation_resource 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. + + VALIDATION_RESOURCE + ID of the validationResource or fully qualified identifier for the + validationResource. + + To set the validation_resource attribute: + ▸ provide the argument validation_resource 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 validationResource resource. + + To set the location attribute: + ▸ provide the argument validation_resource on the command line with + a fully specified name; + ▸ provide the argument --location on the command line. + + --validation=VALIDATION + The validation id of the validationResource resource. + + To set the validation attribute: + ▸ provide the argument validation_resource on the command line with + a fully specified name; + ▸ provide the argument --validation 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 faulttesting/v1alpha API. The full documentation for + this API can be found at: + +NOTES + This command is currently in alpha and might change without notice. If this + command fails 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/fault-testing/validations/validation-resources/help b/gcloud/alpha/fault-testing/validations/validation-resources/help new file mode 100644 index 000000000..224f868cf --- /dev/null +++ b/gcloud/alpha/fault-testing/validations/validation-resources/help @@ -0,0 +1,31 @@ +NAME + gcloud alpha fault-testing validations validation-resources - manage + Validation Resource resources + +SYNOPSIS + gcloud alpha fault-testing validations validation-resources COMMAND + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Manage Validation Resource resources. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + describe + (ALPHA) Describe validationResources. + + list + (ALPHA) List validationResources. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails 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/fault-testing/validations/validation-resources/list b/gcloud/alpha/fault-testing/validations/validation-resources/list new file mode 100644 index 000000000..20b0da5a2 --- /dev/null +++ b/gcloud/alpha/fault-testing/validations/validation-resources/list @@ -0,0 +1,102 @@ +NAME + gcloud alpha fault-testing validations validation-resources list - list + validationResources + +SYNOPSIS + gcloud alpha fault-testing validations validation-resources list + (--validation=VALIDATION : --location=LOCATION) [--filter=EXPRESSION] + [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) List validationResources + +EXAMPLES + To list all validationResources, run: + + $ gcloud alpha fault-testing validations validation-resources list + +REQUIRED FLAGS + Validation resource - The Validation dry run from which to list validation + resources. Format: + projects/{projectId}/locations/{location}/validations/{validationId}. 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 --validation 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. + + --validation=VALIDATION + ID of the validation or fully qualified identifier for the + validation. + + To set the validation attribute: + ▸ provide the argument --validation 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 validation resource. + + To set the location attribute: + ▸ provide the argument --validation 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 faulttesting/v1alpha API. The full documentation for + this API can be found at: + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/firestore/databases/create b/gcloud/alpha/firestore/databases/create index d5e752c5c..410cf9bd9 100644 --- a/gcloud/alpha/firestore/databases/create +++ b/gcloud/alpha/firestore/databases/create @@ -4,6 +4,7 @@ NAME SYNOPSIS gcloud alpha firestore databases create --location=LOCATION + [--concurrency-mode=CONCURRENCY_MODE] [--database=DATABASE; default="(default)"] [--delete-protection] [--edition=EDITION; default="standard"] [--enable-firestore-data-access] @@ -82,6 +83,14 @@ REQUIRED FLAGS $ gcloud alpha firestore databases create --location='us-east1' OPTIONAL FLAGS + --concurrency-mode=CONCURRENCY_MODE + The concurrency control mode to use for this database. + + When not specified, Firestore will pick a default concurrency mode + based on the database edition. + + CONCURRENCY_MODE must be one of: optimistic, pessimistic. + --database=DATABASE; default="(default)" The ID to use for the database, which will become the final component of the database's resource name. If database ID is not provided, diff --git a/gcloud/alpha/firestore/databases/update b/gcloud/alpha/firestore/databases/update index 720b17b20..0ce83415d 100644 --- a/gcloud/alpha/firestore/databases/update +++ b/gcloud/alpha/firestore/databases/update @@ -3,7 +3,8 @@ NAME of a Cloud Firestore database SYNOPSIS - gcloud alpha firestore databases update [--async] [--database=DATABASE] + gcloud alpha firestore databases update [--async] + [--concurrency-mode=CONCURRENCY_MODE] [--database=DATABASE] [--delete-protection] [--enable-pitr] [--type=TYPE] [GCLOUD_WIDE_FLAG ...] @@ -21,6 +22,10 @@ FLAGS Return immediately, without waiting for the operation in progress to complete. + --concurrency-mode=CONCURRENCY_MODE + The concurrency control mode to use for this database. CONCURRENCY_MODE + must be one of: optimistic, pessimistic. + Database resource - Cloud Firestore database to update. This represents a Cloud resource. (NOTE) Some attributes are not given arguments in this group but can be set in other ways. diff --git a/gcloud/alpha/firestore/fields/ttls/update b/gcloud/alpha/firestore/fields/ttls/update index 48a7f2aee..424194835 100644 --- a/gcloud/alpha/firestore/fields/ttls/update +++ b/gcloud/alpha/firestore/fields/ttls/update @@ -5,7 +5,9 @@ NAME SYNOPSIS gcloud alpha firestore fields ttls update (FIELD : --collection-group=COLLECTION_GROUP --database=DATABASE) - (--disable-ttl | --enable-ttl) [--async] [GCLOUD_WIDE_FLAG ...] + (--disable-ttl + | [--enable-ttl : --expiration-offset=EXPIRATION_OFFSET]) [--async] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Update the TTL configuration of the given field. @@ -27,6 +29,12 @@ EXAMPLES $ gcloud alpha firestore fields ttls update expiry \ --collection-group=Events --disable-ttl + The following command sets the expiry field of the Events collection group + (kind) to be the TTL field, with an expiration offset of one week: + + $ gcloud alpha firestore fields ttls update expiry \ + --collection-group=Events --enable-ttl --expiration-offset=7d + POSITIONAL ARGUMENTS Field resource - Field to update. The arguments in this group can be used to specify the attributes of this resource. (NOTE) Some attributes are not @@ -72,8 +80,18 @@ REQUIRED FLAGS --disable-ttl Set to make this field no longer the TTL for its collection group. - --enable-ttl - Set to enable this field as the TTL for its collection group. + Or at least one of these can be specified: + + --enable-ttl + Set to enable this field as the TTL for its collection group. + + This flag argument must be specified if any of the other arguments + in this group are specified. + + --expiration-offset=EXPIRATION_OFFSET + The offset, relative to the timestamp value from the TTL-enabled + field, used to determine the document's expiration time. If unset, + defaults to 0. OPTIONAL FLAGS --async diff --git a/gcloud/alpha/firestore/indexes/composite/create b/gcloud/alpha/firestore/indexes/composite/create index d9645ed03..8df18ec01 100644 --- a/gcloud/alpha/firestore/indexes/composite/create +++ b/gcloud/alpha/firestore/indexes/composite/create @@ -4,13 +4,16 @@ NAME SYNOPSIS gcloud alpha firestore indexes composite create - --field-config=[array-config=ARRAY-CONFIG], - [field-path=FIELD-PATH],[order=ORDER],[vector-config=VECTOR-CONFIG] + --field-config=[array-config=ARRAY-CONFIG],[field-path=FIELD-PATH], + [order=ORDER], + [search-config=SEARCH-CONFIG],[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"] [--unique] - [GCLOUD_WIDE_FLAG ...] + [--query-scope=QUERY_SCOPE; default="collection"] + [--search-index-options=[text-language=TEXT-LANGUAGE], + [text-language-override-field-path=TEXT-LANGUAGE-OVERRIDE-FIELD-PATH]] + [--unique] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Create a new composite index. @@ -31,7 +34,7 @@ EXAMPLES --field-config=field-path=timestamp,order=descending REQUIRED FLAGS - --field-config=[array-config=ARRAY-CONFIG],[field-path=FIELD-PATH],[order=ORDER],[vector-config=VECTOR-CONFIG] + --field-config=[array-config=ARRAY-CONFIG],[field-path=FIELD-PATH],[order=ORDER],[search-config=SEARCH-CONFIG],[vector-config=VECTOR-CONFIG] Required, Configuration for an index field. array-config @@ -47,6 +50,53 @@ REQUIRED FLAGS Exactly one of 'order', 'array-config', or 'vector-config' must be specified. + search-config + Specifies the configuration for a search field. An index definition + must contain either only 'search-config' fields or only non + 'search-config' fields. + + Examples: + + Text search: + + --field-config=field-path=title,search-config='{"text-spec": {"index-specs": [{"index-type": "TOKENIZED", "match-type": "MATCH_GLOBALLY"}]}}' + + Geo search: + + --field-config=field-path=location,search-config='{"geo-spec": {"geo-json-indexing-disabled": true}}' + + With file: + + --field-config=field-path=text,search-config='/path/to/configs/search-config.json' + + For complex configurations, it is recommended to use a file. + + geo-spec + Optional. The specification for building a geo search index for + a field. + + geo-json-indexing-disabled + Optional. Disables geoJSON indexing for the field. By + default, geoJSON points are indexed. + + text-spec + Optional. The specification for building a text search index + for a field. + + index-specs + Optional. Array of specifications for how the field should + be indexed. + + index-type + Required. How to index the text field value. Valid + options are: + ▹ TOKENIZED: Field values are tokenized. + + match-type + Required. How to match the text field value. Valid + options are: + ▹ MATCH_GLOBALLY: Match on any indexed field. + vector-config Specifies the configuration for a vector field. Exactly one of 'order', 'array-config', or 'vector-config' must be specified. @@ -59,11 +109,11 @@ REQUIRED FLAGS Shorthand Example: - --field-config=array-config=string,field-path=string,order=string,vector-config={dimension=int,flat} --field-config=array-config=string,field-path=string,order=string,vector-config={dimension=int,flat} + --field-config=array-config=string,field-path=string,order=string,search-config={geo-spec={geo-json-indexing-disabled=boolean},text-spec={index-specs=[{index-type=string,match-type=string}]}},vector-config={dimension=int,flat} --field-config=array-config=string,field-path=string,order=string,search-config={geo-spec={geo-json-indexing-disabled=boolean},text-spec={index-specs=[{index-type=string,match-type=string}]}},vector-config={dimension=int,flat} JSON Example: - --field-config='[{"array-config": "string", "field-path": "string", "order": "string", "vector-config": {"dimension": int, "flat": {}}}]' + --field-config='[{"array-config": "string", "field-path": "string", "order": "string", "search-config": {"geo-spec": {"geo-json-indexing-disabled": boolean}, "text-spec": {"index-specs": [{"index-type": "string", "match-type": "string"}]}}, "vector-config": {"dimension": int, "flat": {}}}]' File Example: @@ -121,12 +171,42 @@ OPTIONAL FLAGS 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. + 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. + --search-index-options=[text-language=TEXT-LANGUAGE],[text-language-override-field-path=TEXT-LANGUAGE-OVERRIDE-FIELD-PATH] + Optional. Configuration options for search indexes. + + text-language + Optional. The language to use for text search indexes. Used as the + default language if not overridden at the document level by + specifying the 'text-language-override-field-path'. The language is + specified as a BCP 47 language code. For indexes with + 'MONGODB_COMPATIBLE_API' ApiScope: If unspecified, the default + language is English. For indexes with 'ANY_API' ApiScope: If + unspecified, the default behavior is autodetect. + + text-language-override-field-path + Optional. The field in the document that specifies which language + to use for that specific document. If unspecified, the language is + taken from the 'language' document field if it exists or from + 'text-language' if it does not. + + Shorthand Example: + + --search-index-options=text-language=string,text-language-override-field-path=string + + JSON Example: + + --search-index-options='{"text-language": "string", "text-language-override-field-path": "string"}' + + File Example: + + --search-index-options=path_to_file.(yaml|json) + --unique Optional. Whether it is an unique index. Unique index ensures all values for the indexed field(s) are unique across documents. diff --git a/gcloud/alpha/iam/workforce-pools/providers/create-oidc b/gcloud/alpha/iam/workforce-pools/providers/create-oidc index c6ded2998..3fe4eebfe 100644 --- a/gcloud/alpha/iam/workforce-pools/providers/create-oidc +++ b/gcloud/alpha/iam/workforce-pools/providers/create-oidc @@ -202,6 +202,9 @@ REQUIRED FLAGS Each additional scope may be at most 256 characters. A maximum of 10 additional scopes may be configured. + Updating this field replaces any existing values. Include the full + list of additional scopes to avoid losing existing values. + OPTIONAL FLAGS --async Return immediately, without waiting for the operation in progress to diff --git a/gcloud/alpha/iam/workforce-pools/providers/update-oidc b/gcloud/alpha/iam/workforce-pools/providers/update-oidc index 56a72089d..937af4bb0 100644 --- a/gcloud/alpha/iam/workforce-pools/providers/update-oidc +++ b/gcloud/alpha/iam/workforce-pools/providers/update-oidc @@ -239,6 +239,9 @@ FLAGS Each additional scope may be at most 256 characters. A maximum of 10 additional scopes may be configured. + Updating this field replaces any existing values. Include the full list + of additional scopes to avoid losing existing values. + --web-sso-assertion-claims-behavior=WEB_SSO_ASSERTION_CLAIMS_BEHAVIOR The behavior for how OIDC Claims are included in the assertion object used for attribute mapping and attribute condition. Use diff --git a/gcloud/alpha/iap/web/add-iam-policy-binding b/gcloud/alpha/iap/web/add-iam-policy-binding index 27f5d45b7..d40db531f 100644 --- a/gcloud/alpha/iap/web/add-iam-policy-binding +++ b/gcloud/alpha/iap/web/add-iam-policy-binding @@ -5,8 +5,9 @@ NAME SYNOPSIS gcloud alpha iap web add-iam-policy-binding --member=PRINCIPAL --role=ROLE [--condition=[KEY=VALUE,...] | --condition-from-file=PATH_TO_FILE] - [--region=REGION - --resource-type=RESOURCE_TYPE --service=SERVICE --version=VERSION] + [--region=REGION --resource-type=RESOURCE_TYPE + --service=SERVICE --version=VERSION --agent=AGENT + | --endpoint=ENDPOINT | --mcp-server=MCP_SERVER] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -122,7 +123,8 @@ OPTIONAL FLAGS --resource-type=RESOURCE_TYPE Resource type of the IAP resource. RESOURCE_TYPE must be one of: - app-engine, backend-services, forwarding-rule, cloud-run. + app-engine, backend-services, forwarding-rule, cloud-run, + agent-registry. --service=SERVICE Service name. @@ -131,6 +133,17 @@ OPTIONAL FLAGS Service version. Should only be specified with --resource-type=app-engine. + At most one of these can be specified: + + --agent=AGENT + Agent ID for the agent-registry resource type. + + --endpoint=ENDPOINT + Endpoint ID for the agent-registry resource type. + + --mcp-server=MCP_SERVER + MCP server ID for the agent-registry resource type. + 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/iap/web/get-iam-policy b/gcloud/alpha/iap/web/get-iam-policy index 4434c6e81..19037aa2f 100644 --- a/gcloud/alpha/iap/web/get-iam-policy +++ b/gcloud/alpha/iap/web/get-iam-policy @@ -4,8 +4,9 @@ NAME SYNOPSIS gcloud alpha iap web get-iam-policy - [--region=REGION - --resource-type=RESOURCE_TYPE --service=SERVICE --version=VERSION] + [--region=REGION --resource-type=RESOURCE_TYPE + --service=SERVICE --version=VERSION --agent=AGENT + | --endpoint=ENDPOINT | --mcp-server=MCP_SERVER] [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [GCLOUD_WIDE_FLAG ...] @@ -78,7 +79,8 @@ FLAGS --resource-type=RESOURCE_TYPE Resource type of the IAP resource. RESOURCE_TYPE must be one of: - app-engine, backend-services, forwarding-rule, cloud-run. + app-engine, backend-services, forwarding-rule, cloud-run, + agent-registry. --service=SERVICE Service name. @@ -87,6 +89,17 @@ FLAGS Service version. Should only be specified with --resource-type=app-engine. + At most one of these can be specified: + + --agent=AGENT + Agent ID for the agent-registry resource type. + + --endpoint=ENDPOINT + Endpoint ID for the agent-registry resource type. + + --mcp-server=MCP_SERVER + MCP server ID for the agent-registry resource type. + LIST COMMAND FLAGS --filter=EXPRESSION Apply a Boolean filter EXPRESSION to each resource item to be listed. diff --git a/gcloud/alpha/iap/web/remove-iam-policy-binding b/gcloud/alpha/iap/web/remove-iam-policy-binding index d4814c2ba..32d296f27 100644 --- a/gcloud/alpha/iap/web/remove-iam-policy-binding +++ b/gcloud/alpha/iap/web/remove-iam-policy-binding @@ -7,8 +7,9 @@ SYNOPSIS --role=ROLE [--all | --condition=[KEY=VALUE,...] | --condition-from-file=PATH_TO_FILE] - [--region=REGION - --resource-type=RESOURCE_TYPE --service=SERVICE --version=VERSION] + [--region=REGION --resource-type=RESOURCE_TYPE + --service=SERVICE --version=VERSION --agent=AGENT + | --endpoint=ENDPOINT | --mcp-server=MCP_SERVER] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -139,7 +140,8 @@ OPTIONAL FLAGS --resource-type=RESOURCE_TYPE Resource type of the IAP resource. RESOURCE_TYPE must be one of: - app-engine, backend-services, forwarding-rule, cloud-run. + app-engine, backend-services, forwarding-rule, cloud-run, + agent-registry. --service=SERVICE Service name. @@ -148,6 +150,17 @@ OPTIONAL FLAGS Service version. Should only be specified with --resource-type=app-engine. + At most one of these can be specified: + + --agent=AGENT + Agent ID for the agent-registry resource type. + + --endpoint=ENDPOINT + Endpoint ID for the agent-registry resource type. + + --mcp-server=MCP_SERVER + MCP server ID for the agent-registry resource type. + 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/iap/web/set-iam-policy b/gcloud/alpha/iap/web/set-iam-policy index d0240b7d0..a61f4e2c4 100644 --- a/gcloud/alpha/iap/web/set-iam-policy +++ b/gcloud/alpha/iap/web/set-iam-policy @@ -4,8 +4,9 @@ NAME SYNOPSIS gcloud alpha iap web set-iam-policy POLICY_FILE - [--region=REGION - --resource-type=RESOURCE_TYPE --service=SERVICE --version=VERSION] + [--region=REGION --resource-type=RESOURCE_TYPE + --service=SERVICE --version=VERSION --agent=AGENT + | --endpoint=ENDPOINT | --mcp-server=MCP_SERVER] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -86,7 +87,8 @@ FLAGS --resource-type=RESOURCE_TYPE Resource type of the IAP resource. RESOURCE_TYPE must be one of: - app-engine, backend-services, forwarding-rule, cloud-run. + app-engine, backend-services, forwarding-rule, cloud-run, + agent-registry. --service=SERVICE Service name. @@ -95,6 +97,17 @@ FLAGS Service version. Should only be specified with --resource-type=app-engine. + At most one of these can be specified: + + --agent=AGENT + Agent ID for the agent-registry resource type. + + --endpoint=ENDPOINT + Endpoint ID for the agent-registry resource type. + + --mcp-server=MCP_SERVER + MCP server ID for the agent-registry resource type. + 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/kms/asymmetric-sign b/gcloud/alpha/kms/asymmetric-sign index 1b5af8f6f..ab50837f9 100644 --- a/gcloud/alpha/kms/asymmetric-sign +++ b/gcloud/alpha/kms/asymmetric-sign @@ -19,6 +19,11 @@ DESCRIPTION received from Cloud KMS. Use --skip-integrity-verification to disable integrity verification. + For the ML-DSA EXTERNAL-MU algorithms, the digest external-mu should be + used that depends on the public key. This command will fetch the public key + from KMS and compute the external-mu digest. Note that this requires signer + permissions on the associated CryptoKeyVersion. + EXAMPLES The following command will read the file '/tmp/my/file.to.sign', digest it with the digest algorithm 'sha256' and sign it using the asymmetric @@ -40,7 +45,7 @@ REQUIRED FLAGS OPTIONAL FLAGS --digest-algorithm=DIGEST_ALGORITHM The algorithm to digest the input. DIGEST_ALGORITHM must be one of: - sha256, sha384, sha512. + external-mu, sha256, sha384, sha512. --key=KEY to use for signing. diff --git a/gcloud/alpha/kms/key-handles/create b/gcloud/alpha/kms/key-handles/create index 5fc4149a1..cfd8be92f 100644 --- a/gcloud/alpha/kms/key-handles/create +++ b/gcloud/alpha/kms/key-handles/create @@ -20,8 +20,8 @@ EXAMPLES --key-handle-id=my-key-handle --location=global \ --resource-type=compute.googleapis.com/Disk - In case we want to generate a random KeyHandle id, we can use the - --generate-key-handle-id flag instead of the --key-handle-id flag. + To generate a random KeyHandle id, the --generate-key-handle-id flag can be + used instead of --key-handle-id. REQUIRED FLAGS Location resource - The KMS location resource. This represents a Cloud diff --git a/gcloud/alpha/kms/single-tenant-hsm/create b/gcloud/alpha/kms/single-tenant-hsm/create index b952a6940..40905dfbe 100644 --- a/gcloud/alpha/kms/single-tenant-hsm/create +++ b/gcloud/alpha/kms/single-tenant-hsm/create @@ -4,7 +4,7 @@ NAME SYNOPSIS gcloud alpha kms single-tenant-hsm create --location=LOCATION - --total-approver-count=TOTAL_APPROVER_COUNT + --total-approver-count=TOTAL_APPROVER_COUNT [--key-portability-enabled] [--single-tenant-hsm-instance-id=SINGLE_TENANT_HSM_INSTANCE_ID] [GCLOUD_WIDE_FLAG ...] @@ -47,6 +47,10 @@ REQUIRED FLAGS to 16. OPTIONAL FLAGS + --key-portability-enabled + If set, the single tenant HSM instance will be able to perform key + portability operations. + --single-tenant-hsm-instance-id=SINGLE_TENANT_HSM_INSTANCE_ID Specify an ID for the single tenant HSM instance. It must be unique within a location and match the regular expression [a-zA-Z0-9-]{1,63}. diff --git a/gcloud/alpha/kms/single-tenant-hsm/describe b/gcloud/alpha/kms/single-tenant-hsm/describe index 84ef55fd6..70a8c1a55 100644 --- a/gcloud/alpha/kms/single-tenant-hsm/describe +++ b/gcloud/alpha/kms/single-tenant-hsm/describe @@ -10,14 +10,14 @@ SYNOPSIS DESCRIPTION (ALPHA) Returns metadata for the given single tenant HSM instance. - ## EXAMPLES - +EXAMPLES The following command returns the metadata for the single tenant HSM - instance with the name my_sthi in the location us-east1`using the fully + instance with the name my_sthi in the location us-east1 using the fully specified name: - $ gcloud alpha kms single-tenant-hsm describe - projects/my-project/locations/us-east1/singleTenantHsmInstances/mysthi + $ gcloud alpha kms single-tenant-hsm describe \ + projects/my-project/locations/us-east1/\ + singleTenantHsmInstances/mysthi The following command returns the metadata for the singletenanthsm instance with the name mysthi in the location us-east1 using the location and diff --git a/gcloud/alpha/kms/single-tenant-hsm/proposal/describe b/gcloud/alpha/kms/single-tenant-hsm/proposal/describe index 9aa05e9bc..2e5340fdc 100644 --- a/gcloud/alpha/kms/single-tenant-hsm/proposal/describe +++ b/gcloud/alpha/kms/single-tenant-hsm/proposal/describe @@ -13,16 +13,16 @@ EXAMPLES instance proposal with the name my_proposal, of the instance my_sthi, and in the location us-east1 using the fully specified resource name. - $ gcloud alpha kms single-tenant-hsm proposal describe \ - projects/my-project/locations/us-east1/\ - singleTenantHsmInstances/ my_sthi/proposals/my_proposal ``` + $ gcloud alpha kms single-tenant-hsm proposal describe \ + projects/my-project/locations/us-east1/\ + singleTenantHsmInstances/my_sthi/proposals/my_proposal - The following command returns the metadata for the single tenant HSM instance - proposal with the name `my_proposal`, of the instance `my_sthi`, and in the - location `us-east1` using the location, instance id, and proposal id. + The following command returns the metadata for the single tenant HSM + instance proposal with the name my_proposal, of the instance my_sthi, and + in the location us-east1 using the location, instance id, and proposal id. $ gcloud alpha kms single-tenant-hsm proposal describe my_proposal \ - --single_tenant_hsm_instance=my_sthi --location=us-east1 ``` + --single_tenant_hsm_instance=my_sthi --location=us-east1 POSITIONAL ARGUMENTS SingleTenantHsmInstanceProposal resource - The KMS single tenant HSM diff --git a/gcloud/alpha/lifesciences/help b/gcloud/alpha/lifesciences/help deleted file mode 100644 index 0989da906..000000000 --- a/gcloud/alpha/lifesciences/help +++ /dev/null @@ -1,34 +0,0 @@ -NAME - gcloud alpha lifesciences - manage Cloud Life Sciences resources - -SYNOPSIS - gcloud alpha lifesciences GROUP [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (ALPHA) Manage Cloud Life Sciences resources. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --help. - - Run $ gcloud help for details. - -GROUPS - GROUP is one of the following: - - locations - (ALPHA) Query Cloud Life Sciences locations. - - operations - (ALPHA) Manage Cloud Life Sciences operations. - - pipelines - (ALPHA) Commands for Life Sciences pipelines. - -NOTES - This command is currently in alpha and might change without notice. If this - command fails 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 lifesciences - diff --git a/gcloud/alpha/lifesciences/locations/describe b/gcloud/alpha/lifesciences/locations/describe deleted file mode 100644 index ede1e4688..000000000 --- a/gcloud/alpha/lifesciences/locations/describe +++ /dev/null @@ -1,55 +0,0 @@ -NAME - gcloud alpha lifesciences locations describe - describe a Cloud Life - Sciences location - -SYNOPSIS - gcloud alpha lifesciences locations describe [LOCATION] - [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (ALPHA) Describe a Cloud Life Sciences location. - -EXAMPLES - To describe a location (for example, us-central1) called my-location, run: - - $ gcloud alpha lifesciences locations describe my-location - -POSITIONAL ARGUMENTS - Location resource - Cloud Life Sciences location to describe. This - represents a Cloud resource. (NOTE) Some attributes are not given - arguments in this group but can be set in other ways. - - To set the project attribute: - ◆ provide the argument location on the command line with a fully - specified name; - ◆ set the property lifesciences/location with a fully specified name; - ◆ provide the argument --project on the command line; - ◆ set the property core/project. - - [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 lifesciences/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 lifesciences/v2beta API. The full documentation for - this API can be found at: https://cloud.google.com/life-sciences - -NOTES - This command is currently in alpha and might change without notice. If this - command fails 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 lifesciences locations describe - diff --git a/gcloud/alpha/lifesciences/operations/help b/gcloud/alpha/lifesciences/operations/help deleted file mode 100644 index 841ed2ce6..000000000 --- a/gcloud/alpha/lifesciences/operations/help +++ /dev/null @@ -1,38 +0,0 @@ -NAME - gcloud alpha lifesciences operations - manage Cloud Life Sciences - operations - -SYNOPSIS - gcloud alpha lifesciences operations COMMAND [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (ALPHA) Manage Cloud Life Sciences 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 Cloud Life Sciences operation. - - describe - (ALPHA) Describe a Cloud Life Sciences operation. - - list - (ALPHA) List Cloud Life Sciences operations. - - wait - (ALPHA) Wait for Cloud Life Sciences operation to complete. - -NOTES - This command is currently in alpha and might change without notice. If this - command fails with API permission errors despite specifying the correct - project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: - - $ gcloud beta lifesciences operations - diff --git a/gcloud/alpha/lifesciences/pipelines/run b/gcloud/alpha/lifesciences/pipelines/run deleted file mode 100644 index 3859adf08..000000000 --- a/gcloud/alpha/lifesciences/pipelines/run +++ /dev/null @@ -1,199 +0,0 @@ -NAME - gcloud alpha lifesciences pipelines run - defines and runs a pipeline - -SYNOPSIS - gcloud alpha lifesciences pipelines run - (--command-line=COMMAND_LINE | --pipeline-file=PIPELINE_FILE) - [--disk-size=DISK_SIZE] - [--docker-image=DOCKER_IMAGE; default="google/cloud-sdk:slim"] - [--env-vars=[NAME=VALUE,...]] [--inputs=[NAME=VALUE,...]] - [--inputs-from-file=[NAME=FILE,...]] [--logging=LOGGING] - [--outputs=[NAME=VALUE,...]] [--preemptible] - [--boot-disk-size=BOOT_DISK_SIZE] [--labels=[KEY=VALUE,...]] - [--location=LOCATION] - [--machine-type=MACHINE_TYPE; default="n1-standard-1"] - [--network=NETWORK] [--regions=[REGION,...]] - [--service-account-email=SERVICE_ACCOUNT_EMAIL; default="default"] - [--service-account-scopes=[SCOPE,...]] [--subnetwork=SUBNETWORK] - [--zones=[ZONE,...]] [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (ALPHA) A pipeline is a transformation of a set of inputs to a set of - outputs. Supports Docker-based commands. - -EXAMPLES - To run a pipeline described in the pipeline.json file, run: - - $ gcloud alpha lifesciences pipelines run \ - --pipeline-file=pipeline.json - -REQUIRED FLAGS - Exactly one of these must be specified: - - --command-line=COMMAND_LINE - Command line to run with /bin/sh in the specified Docker image. - Cannot be used with --pipeline-file. - - --pipeline-file=PIPELINE_FILE - A YAML or JSON file containing a Pipeline object. See - https://cloud.google.com/life-sciences/docs/reference/rest/v2beta/projects.locations.pipelines/run#pipeline - -COMMONLY USED FLAGS - --disk-size=DISK_SIZE - The disk size(s) in GB, specified as a comma-separated list of pairs of - disk name and size. For example: --disk-size "name:size,name2:size2". - Overrides any values specified in the pipeline-file. - - --docker-image=DOCKER_IMAGE; default="google/cloud-sdk:slim" - A Docker image to run. Requires --command-line to be specified and - cannot be used with --pipeline-file. - - --env-vars=[NAME=VALUE,...] - List of key-value pairs to set as environment variables. - - --inputs=[NAME=VALUE,...] - Map of input PipelineParameter names to values. Used to pass literal - parameters to the pipeline, and to specify input files in Google Cloud - Storage that will have a localCopy made. Specified as a comma-separated - list: --inputs file=gs://my-bucket/in.txt,name=hello - - --inputs-from-file=[NAME=FILE,...] - Map of input PipelineParameter names to values. Used to pass literal - parameters to the pipeline where values come from local files; this can - be used to send large pipeline input parameters, such as code, data, or - configuration values. Specified as a comma-separated list: - --inputs-from-file script=myshellscript.sh,pyfile=mypython.py - - --logging=LOGGING - The location in Google Cloud Storage to which the pipeline logs will be - copied. Can be specified as a fully qualified directory path, in which - case logs will be output with a unique identifier as the filename in - that directory, or as a fully specified path, which must end in .log, - in which case that path will be used. Stdout and stderr logs from the - run are also generated and output as -stdout.log and -stderr.log. - - --outputs=[NAME=VALUE,...] - Map of output PipelineParameter names to values. Used to specify output - files in Google Cloud Storage that will be made from a localCopy. - Specified as a comma-separated list: --outputs - ref=gs://my-bucket/foo,ref2=gs://my-bucket/bar - - --preemptible - Whether to use a preemptible VM for this pipeline. The "resource" - section of the pipeline-file must also set preemptible to "true" for - this flag to take effect. - -OTHER FLAGS - --boot-disk-size=BOOT_DISK_SIZE - The size of the boot disk in GB. - - The boot disk size must be large enough to accommodate all Docker - images from each action in the pipeline at the same time. If not - specified, a small but reasonable default value is used. - - --labels=[KEY=VALUE,...] - List of label KEY=VALUE pairs to add. - - Keys must start with a lowercase character and contain only hyphens - (-), underscores (_), lowercase characters, and numbers. Values must - contain only hyphens (-), underscores (_), lowercase characters, and - numbers. - - Location resource - The Google Cloud location to run the pipeline. 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 lifesciences/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 lifesciences/location. - - --machine-type=MACHINE_TYPE; default="n1-standard-1" - The type of VirtualMachine to use. Defaults to n1-standard-1. - - --network=NETWORK - The network name to attach the VM's network interface to. - - The value will be prefixed with global/networks/ unless it contains a - /, in which case it is assumed to be a fully specified network resource - URL. - - If unspecified, the global default network is used. - - --regions=[REGION,...] - List of Compute Engine regions the pipeline can run in. - - If no regions are specified with the regions flag, then regions in the - pipeline definition file will be used. - - If no regions are specified in the pipeline definition, then the - default region in your local client configuration is used. - - At least one region or region must be specified. - - For more information on default regions, see - https://cloud.google.com/compute/docs/gcloud-compute/#set_default_zone_and_region_in_your_local_client - - --service-account-email=SERVICE_ACCOUNT_EMAIL; default="default" - The service account used on the Compute Engine VMs that run the - pipeline. If unspecified, defaults to the Compute Engine service - account for your project. - - --service-account-scopes=[SCOPE,...] - List of additional scopes to be made available for this service - account. The following scopes are always requested: - - https://www.googleapis.com/auth/cloud-platform - - --subnetwork=SUBNETWORK - The subnetwork to use on the provided network. - - If the specified network is configured for custom subnet creation, the - name of the subnetwork to attach the instance to must be specified - here. - - The value is prefixed with regions/*/subnetworks/ unless it contains a - /, in which case it is assumed to be a fully specified subnetwork - resource URL. - - If the * character appears in the value, it is replaced with the region - that the virtual machine has been allocated in. - - --zones=[ZONE,...] - List of Compute Engine zones the pipeline can run in. - - If no zones are specified with the zones flag, then zones in the - pipeline definition file will be used. - - If no zones are specified in the pipeline definition, then the default - zone in your local client configuration is used (and must be - specified). - - For more information on default zones, see - https://cloud.google.com/compute/docs/gcloud-compute/#set_default_zone_and_region_in_your_local_client - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --configuration, --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 lifesciences pipelines run - diff --git a/gcloud/alpha/lustre/instances/update b/gcloud/alpha/lustre/instances/update index 7d1a6f7d3..f1cfe30dd 100644 --- a/gcloud/alpha/lustre/instances/update +++ b/gcloud/alpha/lustre/instances/update @@ -24,8 +24,6 @@ SYNOPSIS [ipAddressRanges=IPADDRESSRANGES], [mountableSubdirectories=MOUNTABLESUBDIRECTORIES],[name=NAME], [squashGid=SQUASHGID],[squashMode=SQUASHMODE],[squashUid=SQUASHUID]] - [--clear-dynamic-tier-options - --dynamic-tier-options-mode=DYNAMIC_TIER_OPTIONS_MODE] [--clear-maintenance-policy --maintenance-policy-exclusion-window=[endDate=ENDDATE], [startDate=STARTDATE],[time=TIME] @@ -362,20 +360,6 @@ FLAGS --remove-access-rules=path_to_file.(yaml|json) - Dynamic tier options for a Managed Lustre instance. - - --clear-dynamic-tier-options - Set instance.dynamicTierOptions back to default value. - - --dynamic-tier-options-mode=DYNAMIC_TIER_OPTIONS_MODE - The dynamic tier mode of the instance. DYNAMIC_TIER_OPTIONS_MODE must - be one of: - - default-cache - The dynamic tier is enabled. - disabled - The dynamic tier is explicitly disabled. - Defines a maintenance policy for a resource. --clear-maintenance-policy diff --git a/gcloud/alpha/memorystore/instances/create b/gcloud/alpha/memorystore/instances/create index eef927d9a..55fb50f39 100644 --- a/gcloud/alpha/memorystore/instances/create +++ b/gcloud/alpha/memorystore/instances/create @@ -283,12 +283,24 @@ FLAGS Machine type for individual nodes of the instance. NODE_TYPE must be one of: + custom-micro + Custom micro. + custom-mini + Custom mini. + custom-pico + Custom pico. + highcpu-medium + High cpu medium. + highmem-2xlarge + High memory 2xlarge. highmem-medium High memory medium. highmem-xlarge High memory extra large. shared-core-nano Shared core nano. + standard-large + Standard large. standard-small Standard small. diff --git a/gcloud/alpha/memorystore/instances/create-token-auth-user b/gcloud/alpha/memorystore/instances/create-token-auth-user new file mode 100644 index 000000000..7ffcd74af --- /dev/null +++ b/gcloud/alpha/memorystore/instances/create-token-auth-user @@ -0,0 +1,79 @@ +NAME + gcloud alpha memorystore instances create-token-auth-user - create token + auth user for a Memorystore instance + +SYNOPSIS + gcloud alpha memorystore instances create-token-auth-user + (INSTANCE : --location=LOCATION) --token-auth-user=TOKEN_AUTH_USER + [--async] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) create token auth user for a Memorystore instance + +EXAMPLES + To create a token auth user for a Memorystore instance, run: + + $ gcloud alpha memorystore instances create-token-auth-user + +POSITIONAL ARGUMENTS + Instance resource - The instance resource that this token auth user will + be created for. Format: + projects/{project}/locations/{location}/instances/{instance} 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 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 + ID of the instance or fully qualified identifier for the instance. + + To set the instance attribute: + ▸ provide the argument instance 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 instance resource. + + To set the location attribute: + ▸ provide the argument instance on the command line with a fully + specified name; + ▸ provide the argument --location on the command line. + +REQUIRED FLAGS + --token-auth-user=TOKEN_AUTH_USER + The name of the token auth user to create. + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the memorystore/v1alpha API. The full documentation for + this API can be found at: https://cloud.google.com/memorystore/ + +NOTES + This command is currently in alpha and might change without notice. If this + command fails 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 memorystore instances create-token-auth-user + diff --git a/gcloud/alpha/memorystore/instances/help b/gcloud/alpha/memorystore/instances/help index 26cefc4d3..04f0e22aa 100644 --- a/gcloud/alpha/memorystore/instances/help +++ b/gcloud/alpha/memorystore/instances/help @@ -12,6 +12,12 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. +GROUPS + GROUP is one of the following: + + token-auth-users + (ALPHA) Manage Token Auth User resources. + COMMANDS COMMAND is one of the following: @@ -21,6 +27,9 @@ COMMANDS create (ALPHA) Create a Memorystore instance. + create-token-auth-user + (ALPHA) create token auth user for a Memorystore instance. + delete (ALPHA) Delete a Memorystore instance. diff --git a/gcloud/alpha/memorystore/instances/token-auth-users/auth-tokens/delete b/gcloud/alpha/memorystore/instances/token-auth-users/auth-tokens/delete new file mode 100644 index 000000000..d1d5c31e4 --- /dev/null +++ b/gcloud/alpha/memorystore/instances/token-auth-users/auth-tokens/delete @@ -0,0 +1,94 @@ +NAME + gcloud alpha memorystore instances token-auth-users auth-tokens delete - + delete authTokens + +SYNOPSIS + gcloud alpha memorystore instances token-auth-users auth-tokens delete + (AUTH_TOKEN : --instance=INSTANCE + --location=LOCATION --token-auth-user=TOKEN_AUTH_USER) [--async] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Delete an authToken + +EXAMPLES + To delete the authToken, run: + + $ gcloud alpha memorystore instances token-auth-users auth-tokens \ + delete + +POSITIONAL ARGUMENTS + AuthToken resource - The name of the token auth user resource that this + token will be deleted from. Format: + projects/{project}/locations/{location}/instances/{instance}/tokenAuthUsers/{token_auth_user}/authTokens/{name} + The arguments in this group can be used to specify the attributes of this + resource. (NOTE) Some attributes are not given arguments in this group but + can be set in other ways. + + To set the project attribute: + ◆ provide the argument auth_token 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. + + AUTH_TOKEN + ID of the authToken or fully qualified identifier for the authToken. + + To set the auth_token attribute: + ▸ provide the argument auth_token on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --instance=INSTANCE + The instance id of the authToken resource. + + To set the instance attribute: + ▸ provide the argument auth_token on the command line with a fully + specified name; + ▸ provide the argument --instance on the command line. + + --location=LOCATION + The location id of the authToken resource. + + To set the location attribute: + ▸ provide the argument auth_token on the command line with a fully + specified name; + ▸ provide the argument --location on the command line. + + --token-auth-user=TOKEN_AUTH_USER + The tokenAuthUser id of the authToken resource. + + To set the token-auth-user attribute: + ▸ provide the argument auth_token on the command line with a fully + specified name; + ▸ provide the argument --token-auth-user 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 memorystore/v1alpha API. The full documentation for + this API can be found at: https://cloud.google.com/memorystore/ + +NOTES + This command is currently in alpha and might change without notice. If this + command fails 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 memorystore instances token-auth-users auth-tokens \ + delete + diff --git a/gcloud/alpha/memorystore/instances/token-auth-users/auth-tokens/describe b/gcloud/alpha/memorystore/instances/token-auth-users/auth-tokens/describe new file mode 100644 index 000000000..9e3bb5343 --- /dev/null +++ b/gcloud/alpha/memorystore/instances/token-auth-users/auth-tokens/describe @@ -0,0 +1,89 @@ +NAME + gcloud alpha memorystore instances token-auth-users auth-tokens describe - + describe authTokens + +SYNOPSIS + gcloud alpha memorystore instances token-auth-users auth-tokens describe + (AUTH_TOKEN : --instance=INSTANCE + --location=LOCATION --token-auth-user=TOKEN_AUTH_USER) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Describe an authToken + +EXAMPLES + To describe the authToken, run: + + $ gcloud alpha memorystore instances token-auth-users auth-tokens \ + describe + +POSITIONAL ARGUMENTS + AuthToken resource - The name of token auth user for a token auth enabled + instance. Format: + projects/{project}/locations/{location}/instances/{instance}/tokenAuthUsers/{token_auth_user}/authTokens/{auth_token} + 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 auth_token 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. + + AUTH_TOKEN + ID of the authToken or fully qualified identifier for the authToken. + + To set the auth_token attribute: + ▸ provide the argument auth_token on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --instance=INSTANCE + The instance id of the authToken resource. + + To set the instance attribute: + ▸ provide the argument auth_token on the command line with a fully + specified name; + ▸ provide the argument --instance on the command line. + + --location=LOCATION + The location id of the authToken resource. + + To set the location attribute: + ▸ provide the argument auth_token on the command line with a fully + specified name; + ▸ provide the argument --location on the command line. + + --token-auth-user=TOKEN_AUTH_USER + The tokenAuthUser id of the authToken resource. + + To set the token-auth-user attribute: + ▸ provide the argument auth_token on the command line with a fully + specified name; + ▸ provide the argument --token-auth-user 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 memorystore/v1alpha API. The full documentation for + this API can be found at: https://cloud.google.com/memorystore/ + +NOTES + This command is currently in alpha and might change without notice. If this + command fails 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 memorystore instances token-auth-users auth-tokens \ + describe + diff --git a/gcloud/alpha/lifesciences/locations/help b/gcloud/alpha/memorystore/instances/token-auth-users/auth-tokens/help similarity index 53% rename from gcloud/alpha/lifesciences/locations/help rename to gcloud/alpha/memorystore/instances/token-auth-users/auth-tokens/help index 2fa4060ea..e5c5bde5b 100644 --- a/gcloud/alpha/lifesciences/locations/help +++ b/gcloud/alpha/memorystore/instances/token-auth-users/auth-tokens/help @@ -1,11 +1,13 @@ NAME - gcloud alpha lifesciences locations - query Cloud Life Sciences locations + gcloud alpha memorystore instances token-auth-users auth-tokens - manage + Auth Token resources SYNOPSIS - gcloud alpha lifesciences locations COMMAND [GCLOUD_WIDE_FLAG ...] + gcloud alpha memorystore instances token-auth-users auth-tokens COMMAND + [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) Query Cloud Life Sciences locations. + (ALPHA) Manage Auth Token resources. GCLOUD WIDE FLAGS These flags are available to all commands: --help. @@ -15,11 +17,14 @@ GCLOUD WIDE FLAGS COMMANDS COMMAND is one of the following: + delete + (ALPHA) Delete authTokens. + describe - (ALPHA) Describe a Cloud Life Sciences location. + (ALPHA) Describe authTokens. list - (ALPHA) List all locations where Cloud Life Sciences is available. + (ALPHA) List authTokens. NOTES This command is currently in alpha and might change without notice. If this @@ -27,5 +32,5 @@ NOTES project, you might be trying to access an API with an invitation-only early access allowlist. This variant is also available: - $ gcloud beta lifesciences locations + $ gcloud beta memorystore instances token-auth-users auth-tokens diff --git a/gcloud/alpha/memorystore/instances/token-auth-users/auth-tokens/list b/gcloud/alpha/memorystore/instances/token-auth-users/auth-tokens/list new file mode 100644 index 000000000..0c064f6b4 --- /dev/null +++ b/gcloud/alpha/memorystore/instances/token-auth-users/auth-tokens/list @@ -0,0 +1,113 @@ +NAME + gcloud alpha memorystore instances token-auth-users auth-tokens list - list + authTokens + +SYNOPSIS + gcloud alpha memorystore instances token-auth-users auth-tokens list + (--token-auth-user=TOKEN_AUTH_USER + : --instance=INSTANCE --location=LOCATION) [--filter=EXPRESSION] + [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) List authTokens + +EXAMPLES + To list all authTokens, run: + + $ gcloud alpha memorystore instances token-auth-users auth-tokens \ + list + +REQUIRED FLAGS + TokenAuthUser resource - The parent to list auth tokens from. Format: + projects/{project}/locations/{location}/instances/{instance}/tokenAuthUsers/{token_auth_user} + 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 --token-auth-user 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. + + --token-auth-user=TOKEN_AUTH_USER + ID of the tokenAuthUser or fully qualified identifier for the + tokenAuthUser. + + To set the token-auth-user attribute: + ▸ provide the argument --token-auth-user on the command line. + + This flag argument must be specified if any of the other arguments in + this group are specified. + + --instance=INSTANCE + The instance id of the tokenAuthUser resource. + + To set the instance attribute: + ▸ provide the argument --token-auth-user on the command line with a + fully specified name; + ▸ provide the argument --instance on the command line. + + --location=LOCATION + The location id of the tokenAuthUser resource. + + To set the location attribute: + ▸ provide the argument --token-auth-user 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 memorystore/v1alpha API. The full documentation for + this API can be found at: https://cloud.google.com/memorystore/ + +NOTES + This command is currently in alpha and might change without notice. If this + command fails 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 memorystore instances token-auth-users auth-tokens list + diff --git a/gcloud/alpha/memorystore/instances/token-auth-users/create-auth-token b/gcloud/alpha/memorystore/instances/token-auth-users/create-auth-token new file mode 100644 index 000000000..057114f4c --- /dev/null +++ b/gcloud/alpha/memorystore/instances/token-auth-users/create-auth-token @@ -0,0 +1,84 @@ +NAME + gcloud alpha memorystore instances token-auth-users create-auth-token - + create auth token for a token auth user + +SYNOPSIS + gcloud alpha memorystore instances token-auth-users create-auth-token + (TOKEN_AUTH_USER : --instance=INSTANCE --location=LOCATION) [--async] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) create auth token for a token auth user + +EXAMPLES + To create an auth token for a token auth user, run: + + $ gcloud alpha memorystore instances token-auth-users \ + create-auth-token + +POSITIONAL ARGUMENTS + TokenAuthUser resource - The name of the token auth user resource that + this token will be created for. The arguments in this group can be used to + specify the attributes of this resource. (NOTE) Some attributes are not + given arguments in this group but can be set in other ways. + + To set the project attribute: + ◆ provide the argument token_auth_user 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. + + TOKEN_AUTH_USER + ID of the tokenAuthUser or fully qualified identifier for the + tokenAuthUser. + + To set the token_auth_user attribute: + ▸ provide the argument token_auth_user on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --instance=INSTANCE + The instance id of the tokenAuthUser resource. + + To set the instance attribute: + ▸ provide the argument token_auth_user on the command line with a + fully specified name; + ▸ provide the argument --instance on the command line. + + --location=LOCATION + The location id of the tokenAuthUser resource. + + To set the location attribute: + ▸ provide the argument token_auth_user 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 memorystore/v1alpha API. The full documentation for + this API can be found at: https://cloud.google.com/memorystore/ + +NOTES + This command is currently in alpha and might change without notice. If this + command fails 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 memorystore instances token-auth-users \ + create-auth-token + diff --git a/gcloud/alpha/memorystore/instances/token-auth-users/delete b/gcloud/alpha/memorystore/instances/token-auth-users/delete new file mode 100644 index 000000000..820ef1af9 --- /dev/null +++ b/gcloud/alpha/memorystore/instances/token-auth-users/delete @@ -0,0 +1,104 @@ +NAME + gcloud alpha memorystore instances token-auth-users delete - delete + tokenAuthUsers + +SYNOPSIS + gcloud alpha memorystore instances token-auth-users delete + (TOKEN_AUTH_USER : --instance=INSTANCE --location=LOCATION) [--async] + [--no-force] [--request-id=REQUEST_ID] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Delete a tokenAuthUser + +EXAMPLES + To delete the tokenAuthUser, run: + + $ gcloud alpha memorystore instances token-auth-users delete + +POSITIONAL ARGUMENTS + TokenAuthUser resource - The name of the token auth user to delete. + Format: + projects/{project}/locations/{location}/instances/{instance}/tokenAuthUsers/{token_auth_user} + 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 token_auth_user 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. + + TOKEN_AUTH_USER + ID of the tokenAuthUser or fully qualified identifier for the + tokenAuthUser. + + To set the token_auth_user attribute: + ▸ provide the argument token_auth_user on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --instance=INSTANCE + The instance id of the tokenAuthUser resource. + + To set the instance attribute: + ▸ provide the argument token_auth_user on the command line with a + fully specified name; + ▸ provide the argument --instance on the command line. + + --location=LOCATION + The location id of the tokenAuthUser resource. + + To set the location attribute: + ▸ provide the argument token_auth_user 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. + + --force + If set to true, any auth tokens from this user will also be deleted. + Otherwise, the request will only work if the user has no auth tokens. + Enabled by default, use --no-force 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 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 memorystore/v1alpha API. The full documentation for + this API can be found at: https://cloud.google.com/memorystore/ + +NOTES + This command is currently in alpha and might change without notice. If this + command fails 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 memorystore instances token-auth-users delete + diff --git a/gcloud/alpha/memorystore/instances/token-auth-users/describe b/gcloud/alpha/memorystore/instances/token-auth-users/describe new file mode 100644 index 000000000..05a18561a --- /dev/null +++ b/gcloud/alpha/memorystore/instances/token-auth-users/describe @@ -0,0 +1,79 @@ +NAME + gcloud alpha memorystore instances token-auth-users describe - describe + tokenAuthUsers + +SYNOPSIS + gcloud alpha memorystore instances token-auth-users describe + (TOKEN_AUTH_USER : --instance=INSTANCE --location=LOCATION) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Describe a tokenAuthUser + +EXAMPLES + To describe the tokenAuthUser, run: + + $ gcloud alpha memorystore instances token-auth-users describe + +POSITIONAL ARGUMENTS + TokenAuthUser resource - The name of token auth user for a basic auth + enabled instance. Format: + projects/{project}/locations/{location}/instances/{instance}/tokenAuthUsers/{token_auth_user} + 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 token_auth_user 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. + + TOKEN_AUTH_USER + ID of the tokenAuthUser or fully qualified identifier for the + tokenAuthUser. + + To set the token_auth_user attribute: + ▸ provide the argument token_auth_user on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --instance=INSTANCE + The instance id of the tokenAuthUser resource. + + To set the instance attribute: + ▸ provide the argument token_auth_user on the command line with a + fully specified name; + ▸ provide the argument --instance on the command line. + + --location=LOCATION + The location id of the tokenAuthUser resource. + + To set the location attribute: + ▸ provide the argument token_auth_user 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 memorystore/v1alpha API. The full documentation for + this API can be found at: https://cloud.google.com/memorystore/ + +NOTES + This command is currently in alpha and might change without notice. If this + command fails 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 memorystore instances token-auth-users describe + diff --git a/gcloud/alpha/memorystore/instances/token-auth-users/help b/gcloud/alpha/memorystore/instances/token-auth-users/help new file mode 100644 index 000000000..f838ee3c7 --- /dev/null +++ b/gcloud/alpha/memorystore/instances/token-auth-users/help @@ -0,0 +1,45 @@ +NAME + gcloud alpha memorystore instances token-auth-users - manage Token Auth + User resources + +SYNOPSIS + gcloud alpha memorystore instances token-auth-users GROUP | COMMAND + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Manage Token Auth User resources. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +GROUPS + GROUP is one of the following: + + auth-tokens + (ALPHA) Manage Auth Token resources. + +COMMANDS + COMMAND is one of the following: + + create-auth-token + (ALPHA) create auth token for a token auth user. + + delete + (ALPHA) Delete tokenAuthUsers. + + describe + (ALPHA) Describe tokenAuthUsers. + + list + (ALPHA) List tokenAuthUsers. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails 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 memorystore instances token-auth-users + diff --git a/gcloud/alpha/memorystore/instances/token-auth-users/list b/gcloud/alpha/memorystore/instances/token-auth-users/list new file mode 100644 index 000000000..ab598798e --- /dev/null +++ b/gcloud/alpha/memorystore/instances/token-auth-users/list @@ -0,0 +1,102 @@ +NAME + gcloud alpha memorystore instances token-auth-users list - list + tokenAuthUsers + +SYNOPSIS + gcloud alpha memorystore instances token-auth-users list + (--instance=INSTANCE : --location=LOCATION) [--filter=EXPRESSION] + [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) List tokenAuthUsers + +EXAMPLES + To list all tokenAuthUsers, run: + + $ gcloud alpha memorystore instances token-auth-users list + +REQUIRED FLAGS + Instance resource - The parent to list token auth users from. Format: + projects/{project}/locations/{location}/instances/{instance} 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 --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. + + This flag argument must be specified if any of the other arguments in + this group are specified. + + --location=LOCATION + The location id of the instance resource. + + To set the location attribute: + ▸ provide the argument --instance 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 memorystore/v1alpha API. The full documentation for + this API can be found at: https://cloud.google.com/memorystore/ + +NOTES + This command is currently in alpha and might change without notice. If this + command fails 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 memorystore instances token-auth-users list + diff --git a/gcloud/alpha/memorystore/instances/update b/gcloud/alpha/memorystore/instances/update index b8bd2c52c..2bb09f722 100644 --- a/gcloud/alpha/memorystore/instances/update +++ b/gcloud/alpha/memorystore/instances/update @@ -5,10 +5,10 @@ NAME SYNOPSIS gcloud alpha memorystore instances update INSTANCE [--async] [--[no-]async-instance-endpoints-deletion-enabled] - [--auth-mode=AUTH_MODE] [--[no-]deletion-protection-enabled] - [--engine-version=ENGINE_VERSION] [--location=LOCATION] - [--maintenance-version=MAINTENANCE_VERSION] [--mode=MODE] - [--node-type=NODE_TYPE] [--[no-]ondemand-maintenance] + [--authorization-mode=AUTHORIZATION_MODE] + [--[no-]deletion-protection-enabled] [--engine-version=ENGINE_VERSION] + [--location=LOCATION] [--maintenance-version=MAINTENANCE_VERSION] + [--mode=MODE] [--node-type=NODE_TYPE] [--[no-]ondemand-maintenance] [--replica-count=REPLICA_COUNT] [--request-id=REQUEST_ID] [--[no-]rotate-server-certificate] [--shard-count=SHARD_COUNT] [--[no-]simulate-maintenance-event] @@ -99,8 +99,8 @@ FLAGS --async-instance-endpoints-deletion-enabled to enable and --no-async-instance-endpoints-deletion-enabled to disable. - --auth-mode=AUTH_MODE - Authorization mode of the instance. AUTH_MODE must be one of: + --authorization-mode=AUTHORIZATION_MODE + Authorization mode of the instance. AUTHORIZATION_MODE must be one of: auth-disabled Authorization disabled. @@ -144,12 +144,24 @@ FLAGS Machine type for individual nodes of the instance. NODE_TYPE must be one of: + custom-micro + Custom micro. + custom-mini + Custom mini. + custom-pico + Custom pico. + highcpu-medium + High cpu medium. + highmem-2xlarge + High memory 2xlarge. highmem-medium High memory medium. highmem-xlarge High memory extra large. shared-core-nano Shared core nano. + standard-large + Standard large. standard-small Standard small. diff --git a/gcloud/alpha/migration/vms/image-imports/help b/gcloud/alpha/migration/vms/image-imports/help index 23742ba47..07586c8b8 100644 --- a/gcloud/alpha/migration/vms/image-imports/help +++ b/gcloud/alpha/migration/vms/image-imports/help @@ -11,7 +11,7 @@ DESCRIPTION Other image-related operations (for example, list) can be done using gcloud compute images, as usual. - The commands use VM Migartion API which supports importing of an image from + The commands use VM Migration API which supports importing of an image from a Google Cloud Storage file (gs://...) to a target project. VM Migration API must be enabled in your project. @@ -21,7 +21,7 @@ DESCRIPTION completes, successfully or otherwise, there's no further use for the Image Import resource. - The image is imported to a Google Cloud Project, desginated by the Target + The image is imported to a Google Cloud Project, designated by the Target Project resource. To get a list of Target Projects, run the gcloud alpha migration vms target-projects list command. Use the Google Cloud console to add target project resources. For information on adding target projects, diff --git a/gcloud/alpha/mldiagnostics/machine-learning-run/create b/gcloud/alpha/mldiagnostics/machine-learning-run/create index d10261eb0..7aa48585c 100644 --- a/gcloud/alpha/mldiagnostics/machine-learning-run/create +++ b/gcloud/alpha/mldiagnostics/machine-learning-run/create @@ -10,8 +10,7 @@ SYNOPSIS [--run-group=RUN_GROUP] [--run-phase=RUN_PHASE; default="active"] [--tools=[xprof=XPROF]; default="xprof"] [--configs-hardware=[CONFIGS_HARDWARE,...] - --configs-software=[CONFIGS_SOFTWARE,...] - --configs-user=[CONFIGS_USER,...]] + --configs-software=[CONFIGS_SOFTWARE,...]] [--gke-cluster-name=GKE_CLUSTER_NAME --gke-kind=GKE_KIND --gke-namespace=GKE_NAMESPACE --gke-workload-create-time=GKE_WORKLOAD_CREATE_TIME @@ -227,27 +226,6 @@ FLAGS --configs-software=path_to_file.(yaml|json) - --configs-user=[CONFIGS_USER,...] - User defined configs. - - KEY - Sets KEY value. - - VALUE - Sets VALUE value. - - Shorthand Example: - - --configs-user=string=string - - JSON Example: - - --configs-user='{"string": "string"}' - - File Example: - - --configs-user=path_to_file.(yaml|json) - Workload details associated for the Machine Learning Run. Workload have different metadata based on the orchestrator like GKE cluster, Slurm cluster, Google Compute Engine instance etc. diff --git a/gcloud/alpha/mldiagnostics/machine-learning-run/update b/gcloud/alpha/mldiagnostics/machine-learning-run/update index 0ee9566c1..80fc1d9ab 100644 --- a/gcloud/alpha/mldiagnostics/machine-learning-run/update +++ b/gcloud/alpha/mldiagnostics/machine-learning-run/update @@ -10,8 +10,7 @@ SYNOPSIS [--run-group=RUN_GROUP] [--run-phase=RUN_PHASE; default="active"] [--tools=[xprof=XPROF]; default="xprof"] [--configs-hardware=[CONFIGS_HARDWARE,...] - --configs-software=[CONFIGS_SOFTWARE,...] - --configs-user=[CONFIGS_USER,...]] + --configs-software=[CONFIGS_SOFTWARE,...]] [--gke-cluster-name=GKE_CLUSTER_NAME --gke-kind=GKE_KIND --gke-namespace=GKE_NAMESPACE --gke-workload-create-time=GKE_WORKLOAD_CREATE_TIME @@ -244,27 +243,6 @@ OPTIONAL FLAGS --configs-software=path_to_file.(yaml|json) - --configs-user=[CONFIGS_USER,...] - User defined configs. - - KEY - Sets KEY value. - - VALUE - Sets VALUE value. - - Shorthand Example: - - --configs-user=string=string - - JSON Example: - - --configs-user='{"string": "string"}' - - File Example: - - --configs-user=path_to_file.(yaml|json) - Workload details associated for the Machine Learning Run. Workload have different metadata based on the orchestrator like GKE cluster, Slurm cluster, Google Compute Engine instance etc. diff --git a/gcloud/alpha/netapp/storage-pools/create b/gcloud/alpha/netapp/storage-pools/create index 841307d22..9985a3fcb 100644 --- a/gcloud/alpha/netapp/storage-pools/create +++ b/gcloud/alpha/netapp/storage-pools/create @@ -14,9 +14,9 @@ SYNOPSIS [--enable-ldap=ENABLE_LDAP] [--hot-tier-size=HOT_TIER_SIZE] [--kms-config=KMS_CONFIG] [--labels=[KEY=VALUE,...]] [--mode=MODE] [--qos-type=QOS_TYPE] [--replica-zone=REPLICA_ZONE] - [--scale-tier=SCALE_TIER] [--total-iops=TOTAL_IOPS] - [--total-throughput=TOTAL_THROUGHPUT] [--type=TYPE] [--zone=ZONE] - [GCLOUD_WIDE_FLAG ...] + [--scale-tier=SCALE_TIER] [--scale-type=SCALE_TYPE] + [--total-iops=TOTAL_IOPS] [--total-throughput=TOTAL_THROUGHPUT] + [--type=TYPE] [--zone=ZONE] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Creates a Storage Pool to contain Volumes with a specified Service @@ -214,10 +214,17 @@ OPTIONAL FLAGS String indicating replica zone for the Storage Pool --scale-tier=SCALE_TIER - The scale tier of the Storage Pool. standard scale tier is for standard - capacity and performance tier. enterprise scale tier is for higher - capacity and performance tier. SCALE_TIER must be one of: enterprise, - standard. + (DEPRECATED) The scale tier of the Storage Pool. standard scale tier is + for standard capacity and performance tier. enterprise scale tier is + for higher capacity and performance tier. + + The --scale-tier flag is deprecated. Use --scale-type instead. + SCALE_TIER must be one of: enterprise, standard. + + --scale-type=SCALE_TYPE + The scale type of the Storage Pool. default scale type is for standard + capacity and performance. scaleout scale type is for higher capacity + and performance. SCALE_TYPE must be one of: default, scaleout. --total-iops=TOTAL_IOPS Integer indicating total IOPS of the Storage Pool diff --git a/gcloud/alpha/netapp/storage-pools/execute b/gcloud/alpha/netapp/storage-pools/execute index 3b0ac0488..a7b5768b7 100644 --- a/gcloud/alpha/netapp/storage-pools/execute +++ b/gcloud/alpha/netapp/storage-pools/execute @@ -57,7 +57,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 netapp storage-pools execute $ gcloud beta netapp storage-pools execute diff --git a/gcloud/alpha/netapp/storage-pools/help b/gcloud/alpha/netapp/storage-pools/help index 5e5ac9dec..75c83d577 100644 --- a/gcloud/alpha/netapp/storage-pools/help +++ b/gcloud/alpha/netapp/storage-pools/help @@ -31,12 +31,22 @@ COMMANDS list (ALPHA) List Cloud NetApp Storage Pools. + list-backup-configs + (ALPHA) A command to list backup configurations for all volumes in an + ONTAP-mode Storage Pool. + + restore-volume + (ALPHA) Restore a backup to a volume in an ONTAP-mode Storage Pool. + switch (ALPHA) Switch a Regional Cloud NetApp Flex Storage Pool zone. update (ALPHA) Update a Cloud NetApp Storage Pool. + update-backup-config + (ALPHA) Update backup config of a volume in an ONTAP-mode Storage Pool. + NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct diff --git a/gcloud/alpha/dataplex/data-attribute-bindings/get-iam-policy b/gcloud/alpha/netapp/storage-pools/list-backup-configs similarity index 59% rename from gcloud/alpha/dataplex/data-attribute-bindings/get-iam-policy rename to gcloud/alpha/netapp/storage-pools/list-backup-configs index 8dabf295f..dd958ff6d 100644 --- a/gcloud/alpha/dataplex/data-attribute-bindings/get-iam-policy +++ b/gcloud/alpha/netapp/storage-pools/list-backup-configs @@ -1,61 +1,56 @@ NAME - gcloud alpha dataplex data-attribute-bindings get-iam-policy - retrieve a - Dataplex Data Attribute Binding IAM policy + gcloud alpha netapp storage-pools list-backup-configs - a command to list + backup configurations for all volumes in an ONTAP-mode Storage Pool SYNOPSIS - gcloud alpha dataplex data-attribute-bindings get-iam-policy - (DATA_ATTRIBUTE_BINDING : --location=LOCATION) [--filter=EXPRESSION] - [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] + gcloud alpha netapp storage-pools list-backup-configs + (STORAGE_POOL : --location=LOCATION) [--filter=EXPRESSION] + [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) Displays the IAM policy associated with a Dataplex Data Attribute - Binding resource. If formatted as JSON, the output can be edited and used - as a policy file for set-iam-policy. The output includes an "etag" field - identifying the version emitted and allowing detection of concurrent policy - updates. + (ALPHA) Lists backup configurations for all volumes in an ONTAP-mode + Storage Pool. EXAMPLES - To get the IAM policy of a Dataplex Data Attribute Binding - test-attribute-binding in project test-project under location us-central1 + The following command lists backup configurations in Storage Pool named + NAME in location us-central1: - $ gcloud alpha dataplex data-attribute-bindings get-iam-policy \ - test-attribute-binding --project=test-project \ - --location=us-central1 + $ gcloud alpha netapp storage-pools list-backup-configs NAME \ + --location=us-central1 POSITIONAL ARGUMENTS - Data attribute binding resource - Arguments and flags that define the - Dataplex Data Attribute Binding IAM policy you want to retrieve. The + Storage pool resource - The Storage Pool to list backup configs for. The arguments in this group can be used to specify the attributes of this resource. (NOTE) Some attributes are not given arguments in this group but can be set in other ways. To set the project attribute: - ◆ provide the argument data_attribute_binding on the command line with - a fully specified name; + ◆ provide the argument storage_pool on the command line with a fully + specified name; ◆ provide the argument --project on the command line; ◆ set the property core/project. This must be specified. - DATA_ATTRIBUTE_BINDING - ID of the data attribute binding or fully qualified identifier for - the data attribute binding. + STORAGE_POOL + ID of the storage_pool or fully qualified identifier for the + storage_pool. - To set the data_attribute_binding attribute: - ▸ provide the argument data_attribute_binding on the command line. + To set the storage_pool attribute: + ▸ provide the argument storage_pool on the command line. This positional argument must be specified if any of the other arguments in this group are specified. --location=LOCATION - Location of the Dataplex resource. + The location of the storage_pool. To set the location attribute: - ▸ provide the argument data_attribute_binding on the command line - with a fully specified name; + ▸ provide the argument storage_pool on the command line with a + fully specified name; ▸ provide the argument --location on the command line; - ▸ set the property dataplex/location. + ▸ set the property netapp/location. LIST COMMAND FLAGS --filter=EXPRESSION @@ -83,6 +78,12 @@ LIST COMMAND FLAGS order on that field. This flag interacts with other flags that are applied in this order: --flatten, --sort-by, --filter, --limit. + --uri + Print a list of resource URIs instead of the default output, and change + the command output to a list of URIs. If this flag is used with + --format, the formatting is applied on this URI list. To display URIs + alongside other keys instead, use the uri() transform. + GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, @@ -91,13 +92,11 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. -API REFERENCE - This command uses the dataplex/v1 API. The full documentation for this API - can be found at: https://cloud.google.com/dataplex/docs - NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. + access allowlist. This variant is also available: + + $ gcloud beta netapp storage-pools list-backup-configs diff --git a/gcloud/alpha/netapp/storage-pools/restore-volume b/gcloud/alpha/netapp/storage-pools/restore-volume new file mode 100644 index 000000000..f29c3d7af --- /dev/null +++ b/gcloud/alpha/netapp/storage-pools/restore-volume @@ -0,0 +1,155 @@ +NAME + gcloud alpha netapp storage-pools restore-volume - restore a backup to a + volume in an ONTAP-mode Storage Pool + +SYNOPSIS + gcloud alpha netapp storage-pools restore-volume + (STORAGE_POOL : --location=LOCATION) --volume-uuid=VOLUME_UUID + (--backup=BACKUP : --backup_vault=BACKUP_VAULT) [--async] + [--file-list=[FILE_LIST,...]] + [--restore-destination-path=RESTORE_DESTINATION_PATH] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Restores a backup to a volume within the specified Storage Pool. + + This command supports both full backup restore and selective file restore: + + Full Backup Restore: The --volume-uuid must reference a Data Protection + (DP) volume where the backup will be restored. + + File Restore: The --volume-uuid must reference a Read-Write (RW) volume + where the file(s) from the backup will be restored. For file restore, + --file-list and --restore-destination-path must be included in the request + payload. + + For the complete backup restore, users should first create a Data + Protection volume via the ONTAP Mode APIs whereas a Read-Write volume must + be created first for selective file restore. + +EXAMPLES + The following command restores full backup from a backup with full resource + name + projects/my-project/locations/us-central1/backupVaults/my-vault/backups/backup-1 + to an ONTAP-mode volume with UUID 5dc61a44-3d99-11f1-b8ff-39021cc41d7a in + Storage Pool named NAME. + + $ gcloud alpha netapp storage-pools restore-volume NAME \ + --location=us-central1 \ + --backup=projects/my-project/locations/us-central1/\ + backupVaults/my-vault/backups/backup-1 \ + --volume-uuid=5dc61a44-3d99-11f1-b8ff-39021cc41d7a + + The following command restores file1.txt from the same backup to an + ONTAP-mode volume with UUID 5dc61a44-3d99-11f1-b8ff-39021cc41d7a in Storage + Pool named NAME to the directory /my_restore_destination. + + $ gcloud alpha netapp storage-pools restore-volume NAME \ + --location=us-central1 \ + --backup=projects/my-project/locations/us-central1/\ + backupVaults/my-vault/backups/backup-1 \ + --volume-uuid=5dc61a44-3d99-11f1-b8ff-39021cc41d7a \ + --file-list=/path/to/file1.txt \ + --restore-destination-path=/my_restore_destination + +POSITIONAL ARGUMENTS + Storage pool resource - The Storage Pool to restore into. 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 storage_pool on the command line with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + STORAGE_POOL + ID of the storage_pool or fully qualified identifier for the + storage_pool. + + To set the storage_pool attribute: + ▸ provide the argument storage_pool 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 of the storage_pool. + + To set the location attribute: + ▸ provide the argument storage_pool on the command line with a + fully specified name; + ▸ provide the argument --location on the command line; + ▸ set the property netapp/location. + +REQUIRED FLAGS + --volume-uuid=VOLUME_UUID + The UUID of the ONTAP-mode volume to restore to. + + Backup resource - The Backup from which files are restored back to the + Volume. 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 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 --backup on the command line with a fully + specified name; + ◆ set the property netapp/location. + + This must be specified. + + --backup=BACKUP + ID of the backup or fully qualified identifier for the backup. + + To set the backup attribute: + ▸ provide the argument --backup on the command line. + + This flag argument must be specified if any of the other arguments in + this group are specified. + + --backup_vault=BACKUP_VAULT + The Backup Vault of the backup. + + To set the backup_vault attribute: + ▸ provide the argument --backup on the command line with a fully + specified name; + ▸ provide the argument --backup_vault on the command line; + ▸ provide the argument --backup-vault on the command line. + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --file-list=[FILE_LIST,...] + List of files to be restored in the form of their absolute path as in + source volume. + + --restore-destination-path=RESTORE_DESTINATION_PATH + Name of the absolute directory path in the destination volume. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --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 netapp storage-pools restore-volume + diff --git a/gcloud/alpha/netapp/storage-pools/update-backup-config b/gcloud/alpha/netapp/storage-pools/update-backup-config new file mode 100644 index 000000000..015c9c63b --- /dev/null +++ b/gcloud/alpha/netapp/storage-pools/update-backup-config @@ -0,0 +1,99 @@ +NAME + gcloud alpha netapp storage-pools update-backup-config - update backup + config of a volume in an ONTAP-mode Storage Pool + +SYNOPSIS + gcloud alpha netapp storage-pools update-backup-config + (STORAGE_POOL : --location=LOCATION) + --backup-config=[backup-policies=BACKUP-POLICIES], + [backup-vault=BACKUP-VAULT], + [enable-scheduled-backups=ENABLE-SCHEDULED-BACKUPS] + --volume-uuid=VOLUME_UUID [--async] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Updates the backup configuration of a volume within the specified + Storage Pool. + +EXAMPLES + The following command updates the backup configuration of a volume with + UUID 5dc61a44-3d99-11f1-b8ff-39021cc41d7a in an ONTAP-mode Storage Pool + named NAME. + + $ gcloud alpha netapp storage-pools update-backup-config NAME \ + --location=us-central1 \ + --volume-uuid=5dc61a44-3d99-11f1-b8ff-39021cc41d7a \ + --backup-config=backup-vault=my-vault,\ + enable-scheduled-backups=true + +POSITIONAL ARGUMENTS + Storage pool resource - The Storage Pool. 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 storage_pool on the command line with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + STORAGE_POOL + ID of the storage_pool or fully qualified identifier for the + storage_pool. + + To set the storage_pool attribute: + ▸ provide the argument storage_pool 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 of the storage_pool. + + To set the location attribute: + ▸ provide the argument storage_pool on the command line with a + fully specified name; + ▸ provide the argument --location on the command line; + ▸ set the property netapp/location. + +REQUIRED FLAGS + --backup-config=[backup-policies=BACKUP-POLICIES],[backup-vault=BACKUP-VAULT],[enable-scheduled-backups=ENABLE-SCHEDULED-BACKUPS] + Backup Config contains backup related config on a volume in ONTAP-mode + Storage Pool. + + Backup Config will have the following format + --backup-config=backup-policies=BACKUP_POLICIES, + backup-vault=BACKUP_VAULT_NAME, + enable-scheduled-backups=ENABLE_SCHEDULED_BACKUPS + + backup-policies is a pound-separated (#) list of backup policy names, + backup-vault can include a single backup-vault resource name, and + enable-scheduled-backups is a Boolean value indicating whether or not + scheduled backups are enabled on the volume in the ONTAP-mode Storage + Pool. + + --volume-uuid=VOLUME_UUID + The UUID of the volume to update backup config for. + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud beta netapp storage-pools update-backup-config + diff --git a/gcloud/alpha/network-management/network-monitoring-providers/generate-monitoring-point-config b/gcloud/alpha/network-management/network-monitoring-providers/generate-monitoring-point-config new file mode 100644 index 000000000..1b69598a4 --- /dev/null +++ b/gcloud/alpha/network-management/network-monitoring-providers/generate-monitoring-point-config @@ -0,0 +1,73 @@ +NAME + gcloud alpha network-management network-monitoring-providers + generate-monitoring-point-config - generate a monitoring point config + +SYNOPSIS + gcloud alpha network-management network-monitoring-providers + generate-monitoring-point-config + (NETWORK_MONITORING_PROVIDER : --location=LOCATION) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Generate a monitoring point config. + +EXAMPLES + To generate a monitoring point configuration for provider my-provider-id, + run: + + $ gcloud alpha network-management network-monitoring-providers \ + generate-monitoring-point-config my-provider-id \ + --location=global + +POSITIONAL ARGUMENTS + NetworkMonitoringProvider resource - Name of the resource. Format: + projects/{project}/locations/{location}/networkMonitoringProviders/{network_monitoring_provider} + The arguments in this group can be used to specify the attributes of this + resource. (NOTE) Some attributes are not given arguments in this group but + can be set in other ways. + + To set the project attribute: + ◆ provide the argument network_monitoring_provider 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. + + NETWORK_MONITORING_PROVIDER + ID of the networkMonitoringProvider or fully qualified identifier for + the networkMonitoringProvider. + + To set the network_monitoring_provider attribute: + ▸ provide the argument network_monitoring_provider 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 networkMonitoringProvider resource. + + To set the location attribute: + ▸ provide the argument network_monitoring_provider 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 networkmanagement/v1alpha1 API. The full + documentation for this API can be found at: https://cloud.google.com/ + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/network-management/network-monitoring-providers/help b/gcloud/alpha/network-management/network-monitoring-providers/help index c74030ab4..ad0543990 100644 --- a/gcloud/alpha/network-management/network-monitoring-providers/help +++ b/gcloud/alpha/network-management/network-monitoring-providers/help @@ -46,6 +46,9 @@ COMMANDS describe (ALPHA) Describe a Network Monitoring Provider. + generate-monitoring-point-config + (ALPHA) Generate a monitoring point config. + generate-provider-access-token (ALPHA) Generate a provider access token. diff --git a/gcloud/alpha/network-management/network-monitoring-providers/monitoring-points/download-recreate-install-script b/gcloud/alpha/network-management/network-monitoring-providers/monitoring-points/download-recreate-install-script new file mode 100644 index 000000000..b161161a3 --- /dev/null +++ b/gcloud/alpha/network-management/network-monitoring-providers/monitoring-points/download-recreate-install-script @@ -0,0 +1,58 @@ +NAME + gcloud alpha network-management network-monitoring-providers + monitoring-points download-recreate-install-script - download an + installation script for recreating a Monitoring Point + +SYNOPSIS + gcloud alpha network-management network-monitoring-providers + monitoring-points download-recreate-install-script --location=LOCATION + --monitoring-point=MONITORING_POINT + --network-monitoring-provider=NETWORK_MONITORING_PROVIDER + --output-file=OUTPUT_FILE [--hostname=HOSTNAME] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Downloads an installation script for recreating a specific + Container Monitoring Point. The response is a tarball file. + +EXAMPLES + To download the recreate install script for monitoring point my-mp, run: + + $ gcloud alpha network-management network-monitoring-providers \ + monitoring-points download-recreate-install-script \ + --network-monitoring-provider=my-provider --location=global \ + --monitoring-point=my-mp --output-file=script.tar.gz + +REQUIRED FLAGS + --location=LOCATION + The location of the Network Monitoring Provider (example: global). + + --monitoring-point=MONITORING_POINT + The ID of the Monitoring Point. + + --network-monitoring-provider=NETWORK_MONITORING_PROVIDER + The ID of the Network Monitoring Provider. + + --output-file=OUTPUT_FILE + The path to save the downloaded install script. + +OPTIONAL FLAGS + --hostname=HOSTNAME + The hostname of the Monitoring Point, e.g. "test-vm". + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +BRIEF + Download an installation script for recreating a Monitoring Point. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails 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-management/network-monitoring-providers/monitoring-points/download-server-connect-config b/gcloud/alpha/network-management/network-monitoring-providers/monitoring-points/download-server-connect-config new file mode 100644 index 000000000..73c0b1d94 --- /dev/null +++ b/gcloud/alpha/network-management/network-monitoring-providers/monitoring-points/download-server-connect-config @@ -0,0 +1,50 @@ +NAME + gcloud alpha network-management network-monitoring-providers + monitoring-points download-server-connect-config - download the server + connect configuration for a Network Monitoring Provider + +SYNOPSIS + gcloud alpha network-management network-monitoring-providers + monitoring-points download-server-connect-config --location=LOCATION + --network-monitoring-provider=NETWORK_MONITORING_PROVIDER + --output-file=OUTPUT_FILE [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Downloads the server connect configuration for a given Network + Monitoring Provider. The response is a zip file. + +EXAMPLES + To download the server connect configuration for provider my-provider, run: + + $ gcloud alpha network-management network-monitoring-providers \ + monitoring-points download-server-connect-config \ + --network-monitoring-provider=my-provider --location=global \ + --output-file=config.zip + +REQUIRED FLAGS + --location=LOCATION + The location of the Network Monitoring Provider (example: global). + + --network-monitoring-provider=NETWORK_MONITORING_PROVIDER + The ID of the Network Monitoring Provider. + + --output-file=OUTPUT_FILE + The path to save the downloaded server connect configuration. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +BRIEF + Download the server connect configuration. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/network-management/network-monitoring-providers/monitoring-points/help b/gcloud/alpha/network-management/network-monitoring-providers/monitoring-points/help index d7d691f94..9cec43205 100644 --- a/gcloud/alpha/network-management/network-monitoring-providers/monitoring-points/help +++ b/gcloud/alpha/network-management/network-monitoring-providers/monitoring-points/help @@ -25,6 +25,14 @@ COMMANDS download-install-script (ALPHA) Download an installation script for a Monitoring Point. + download-recreate-install-script + (ALPHA) Download an installation script for recreating a Monitoring + Point. + + download-server-connect-config + (ALPHA) Download the server connect configuration for a Network + Monitoring Provider. + list (ALPHA) List Monitoring Points. diff --git a/gcloud/alpha/network-security/firewall-endpoint-associations/create b/gcloud/alpha/network-security/firewall-endpoint-associations/create index 945f8536c..824bec657 100644 --- a/gcloud/alpha/network-security/firewall-endpoint-associations/create +++ b/gcloud/alpha/network-security/firewall-endpoint-associations/create @@ -4,9 +4,10 @@ NAME SYNOPSIS gcloud alpha network-security firewall-endpoint-associations create - [ASSOCIATION_ID] --network=NETWORK --zone=ZONE + [ASSOCIATION_ID] --network=NETWORK (--endpoint=ENDPOINT : --endpoint-project=ENDPOINT_PROJECT - --endpoint-zone=ENDPOINT_ZONE --organization=ORGANIZATION) [--async] + --endpoint-zone=ENDPOINT_ZONE --organization=ORGANIZATION) + (--location=LOCATION | --zone=ZONE) [--async] [--labels=[KEY=VALUE,...]] [--max-wait=MAX_WAIT; default="60m"] [--tls-inspection-policy=TLS_INSPECTION_POLICY : --tls-inspection-policy-project=TLS_INSPECTION_POLICY_PROJECT @@ -54,9 +55,6 @@ REQUIRED FLAGS To set the network-name attribute: ▸ provide the argument --network on the command line. - --zone=ZONE - Zone of a firewall endpoint association - Firewall endpoint resource - Firewall Plus. The arguments in this group can be used to specify the attributes of this resource. This resource can be one of the following types: @@ -95,6 +93,7 @@ REQUIRED FLAGS specified name; ▸ provide the argument --endpoint-zone on the command line; ▸ provide the argument --zone on the command line; + ▸ provide the argument --location on the command line; ▸ provide the argument FIREWALL_ENDPOINT_ASSOCIATION on the command line with a fully specified name. @@ -108,6 +107,14 @@ REQUIRED FLAGS specified for resource of type [networksecurity.organizations.locations.firewallEndpoints]. + Exactly one of these must be specified: + + --location=LOCATION + Location of the firewall endpoint association + + --zone=ZONE + Zone of the firewall endpoint association + OPTIONAL FLAGS --async Return immediately, without waiting for the operation in progress to diff --git a/gcloud/alpha/network-security/firewall-endpoint-associations/delete b/gcloud/alpha/network-security/firewall-endpoint-associations/delete index 4228c082c..ef667232a 100644 --- a/gcloud/alpha/network-security/firewall-endpoint-associations/delete +++ b/gcloud/alpha/network-security/firewall-endpoint-associations/delete @@ -5,7 +5,8 @@ NAME SYNOPSIS gcloud alpha network-security firewall-endpoint-associations delete (FIREWALL_ENDPOINT_ASSOCIATION : --zone=ZONE) [--async] - [--max-wait=MAX_WAIT; default="60m"] [GCLOUD_WIDE_FLAG ...] + [--location=LOCATION] [--max-wait=MAX_WAIT; default="60m"] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Unassociate the specified network from a firewall endpoint. Check @@ -55,7 +56,8 @@ POSITIONAL ARGUMENTS To set the zone attribute: ▸ provide the argument FIREWALL_ENDPOINT_ASSOCIATION on the command line with a fully specified name; - ▸ provide the argument --zone on the command line. + ▸ provide the argument --zone on the command line; + ▸ provide the argument --location on the command line. FLAGS --async @@ -63,6 +65,9 @@ FLAGS complete. The default is True. Enabled by default, use --no-async to disable. + --location=LOCATION + Location of the firewall endpoint association + --max-wait=MAX_WAIT; default="60m" Time to synchronously wait for the operation to complete, after which the operation continues asynchronously. Ignored if --no-async isn't diff --git a/gcloud/alpha/network-security/firewall-endpoint-associations/describe b/gcloud/alpha/network-security/firewall-endpoint-associations/describe index 7b9841c73..1971d5915 100644 --- a/gcloud/alpha/network-security/firewall-endpoint-associations/describe +++ b/gcloud/alpha/network-security/firewall-endpoint-associations/describe @@ -4,7 +4,8 @@ NAME SYNOPSIS gcloud alpha network-security firewall-endpoint-associations describe - (FIREWALL_ENDPOINT_ASSOCIATION : --zone=ZONE) [GCLOUD_WIDE_FLAG ...] + (FIREWALL_ENDPOINT_ASSOCIATION : --zone=ZONE) [--location=LOCATION] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Describe a firewall endpoint association. @@ -54,7 +55,12 @@ POSITIONAL ARGUMENTS To set the zone attribute: ▸ provide the argument FIREWALL_ENDPOINT_ASSOCIATION on the command line with a fully specified name; - ▸ provide the argument --zone on the command line. + ▸ provide the argument --zone on the command line; + ▸ provide the argument --location on the command line. + +FLAGS + --location=LOCATION + Location of the firewall endpoint association GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/alpha/network-security/firewall-endpoint-associations/list b/gcloud/alpha/network-security/firewall-endpoint-associations/list index b583f759f..2e9e329da 100644 --- a/gcloud/alpha/network-security/firewall-endpoint-associations/list +++ b/gcloud/alpha/network-security/firewall-endpoint-associations/list @@ -4,8 +4,8 @@ NAME SYNOPSIS gcloud alpha network-security firewall-endpoint-associations list - [--zone=ZONE; default="-"] [--filter=EXPRESSION] [--limit=LIMIT] - [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [--location=LOCATION | --zone=ZONE] [--filter=EXPRESSION] + [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -26,8 +26,13 @@ EXAMPLES defined. FLAGS - --zone=ZONE; default="-" - Zone for the list operation + At most one of these can be specified: + + --location=LOCATION + Location of the firewall endpoint association + + --zone=ZONE + Zone of the firewall endpoint association LIST COMMAND FLAGS --filter=EXPRESSION diff --git a/gcloud/alpha/network-security/firewall-endpoint-associations/update b/gcloud/alpha/network-security/firewall-endpoint-associations/update index d21eed87b..d61d6e733 100644 --- a/gcloud/alpha/network-security/firewall-endpoint-associations/update +++ b/gcloud/alpha/network-security/firewall-endpoint-associations/update @@ -5,7 +5,7 @@ NAME SYNOPSIS gcloud alpha network-security firewall-endpoint-associations update (FIREWALL_ENDPOINT_ASSOCIATION : --zone=ZONE) [--async] - [--max-wait=MAX_WAIT; default="60m"] + [--location=LOCATION] [--max-wait=MAX_WAIT; default="60m"] [--disabled | --update-labels=[KEY=VALUE,...] --clear-labels | --remove-labels=[KEY,...] --no-tls-inspection-policy | [--tls-inspection-policy=TLS_INSPECTION_POLICY @@ -70,7 +70,8 @@ POSITIONAL ARGUMENTS To set the zone attribute: ▸ provide the argument FIREWALL_ENDPOINT_ASSOCIATION on the command line with a fully specified name; - ▸ provide the argument --zone on the command line. + ▸ provide the argument --zone on the command line; + ▸ provide the argument --location on the command line. FLAGS --async @@ -78,6 +79,9 @@ FLAGS complete. The default is True. Enabled by default, use --no-async to disable. + --location=LOCATION + Location of the firewall endpoint association + --max-wait=MAX_WAIT; default="60m" Time to synchronously wait for the operation to complete, after which the operation continues asynchronously. Ignored if --no-async isn't diff --git a/gcloud/alpha/network-security/firewall-endpoints/create b/gcloud/alpha/network-security/firewall-endpoints/create index dad3aeb3b..9f0ce28a0 100644 --- a/gcloud/alpha/network-security/firewall-endpoints/create +++ b/gcloud/alpha/network-security/firewall-endpoints/create @@ -7,7 +7,7 @@ SYNOPSIS (FIREWALL_ENDPOINT : --organization=ORGANIZATION --zone=ZONE) [--async] [--billing-project=BILLING_PROJECT] [--description=DESCRIPTION] [--enable-jumbo-frames] [--labels=[KEY=VALUE,...]] - [--max-wait=MAX_WAIT; default="60m"] + [--location=LOCATION] [--max-wait=MAX_WAIT; default="60m"] [--target-firewall-attachment=TARGET_FIREWALL_ATTACHMENT] [GCLOUD_WIDE_FLAG ...] @@ -67,7 +67,8 @@ POSITIONAL ARGUMENTS To set the zone attribute: ▸ provide the argument FIREWALL_ENDPOINT on the command line with a fully specified name; - ▸ provide the argument --zone on the command line. + ▸ provide the argument --zone on the command line; + ▸ provide the argument --location on the command line. FLAGS --async @@ -95,6 +96,9 @@ FLAGS contain only hyphens (-), underscores (_), lowercase characters, and numbers. + --location=LOCATION + Location of the endpoint + --max-wait=MAX_WAIT; default="60m" Time to synchronously wait for the operation to complete, after which the operation continues asynchronously. Ignored if --no-async isn't diff --git a/gcloud/alpha/network-security/firewall-endpoints/delete b/gcloud/alpha/network-security/firewall-endpoints/delete index 59323a614..f21f86317 100644 --- a/gcloud/alpha/network-security/firewall-endpoints/delete +++ b/gcloud/alpha/network-security/firewall-endpoints/delete @@ -5,7 +5,8 @@ NAME SYNOPSIS gcloud alpha network-security firewall-endpoints delete (FIREWALL_ENDPOINT : --organization=ORGANIZATION --zone=ZONE) [--async] - [--max-wait=MAX_WAIT; default="60m"] [GCLOUD_WIDE_FLAG ...] + [--location=LOCATION] [--max-wait=MAX_WAIT; default="60m"] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Delete a firewall endpoint. Check the progress of endpoint deletion @@ -68,7 +69,8 @@ POSITIONAL ARGUMENTS To set the zone attribute: ▸ provide the argument FIREWALL_ENDPOINT on the command line with a fully specified name; - ▸ provide the argument --zone on the command line. + ▸ provide the argument --zone on the command line; + ▸ provide the argument --location on the command line. FLAGS --async @@ -76,6 +78,9 @@ FLAGS complete. The default is True. Enabled by default, use --no-async to disable. + --location=LOCATION + Location of the endpoint + --max-wait=MAX_WAIT; default="60m" Time to synchronously wait for the operation to complete, after which the operation continues asynchronously. Ignored if --no-async isn't diff --git a/gcloud/alpha/network-security/firewall-endpoints/describe b/gcloud/alpha/network-security/firewall-endpoints/describe index 9d2f77040..2a96eb60c 100644 --- a/gcloud/alpha/network-security/firewall-endpoints/describe +++ b/gcloud/alpha/network-security/firewall-endpoints/describe @@ -5,7 +5,7 @@ NAME SYNOPSIS gcloud alpha network-security firewall-endpoints describe (FIREWALL_ENDPOINT : --organization=ORGANIZATION --zone=ZONE) - [GCLOUD_WIDE_FLAG ...] + [--location=LOCATION] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Describe a firewall endpoint. @@ -67,7 +67,12 @@ POSITIONAL ARGUMENTS To set the zone attribute: ▸ provide the argument FIREWALL_ENDPOINT on the command line with a fully specified name; - ▸ provide the argument --zone on the command line. + ▸ provide the argument --zone on the command line; + ▸ provide the argument --location on the command line. + +FLAGS + --location=LOCATION + Location of the endpoint GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/alpha/network-security/firewall-endpoints/list b/gcloud/alpha/network-security/firewall-endpoints/list index 6f16a5a0a..662f8c589 100644 --- a/gcloud/alpha/network-security/firewall-endpoints/list +++ b/gcloud/alpha/network-security/firewall-endpoints/list @@ -3,7 +3,8 @@ NAME endpoints SYNOPSIS - gcloud alpha network-security firewall-endpoints list [--zone=ZONE] + gcloud alpha network-security firewall-endpoints list + [--location=LOCATION | --zone=ZONE] [--organization=ORGANIZATION --project=PROJECT_ID] [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] @@ -20,8 +21,13 @@ EXAMPLES --organization=1234 FLAGS - --zone=ZONE - The zone for a list operation + At most one of these can be specified: + + --location=LOCATION + The location for a list operation + + --zone=ZONE + The zone for a list operation --organization=ORGANIZATION The organization for a list operation diff --git a/gcloud/alpha/network-security/firewall-endpoints/update b/gcloud/alpha/network-security/firewall-endpoints/update index eb64bb22f..432944244 100644 --- a/gcloud/alpha/network-security/firewall-endpoints/update +++ b/gcloud/alpha/network-security/firewall-endpoints/update @@ -5,7 +5,8 @@ NAME SYNOPSIS gcloud alpha network-security firewall-endpoints update (FIREWALL_ENDPOINT : --organization=ORGANIZATION --zone=ZONE) [--async] - [--description=DESCRIPTION] [--max-wait=MAX_WAIT; default="60m"] + [--description=DESCRIPTION] [--location=LOCATION] + [--max-wait=MAX_WAIT; default="60m"] [--update-billing-project=BILLING_PROJECT] [--update-labels=[KEY=VALUE,...]] [--clear-labels | --remove-labels=[KEY,...]] [GCLOUD_WIDE_FLAG ...] @@ -77,7 +78,8 @@ POSITIONAL ARGUMENTS To set the zone attribute: ▸ provide the argument FIREWALL_ENDPOINT on the command line with a fully specified name; - ▸ provide the argument --zone on the command line. + ▸ provide the argument --zone on the command line; + ▸ provide the argument --location on the command line. FLAGS --async @@ -88,6 +90,9 @@ FLAGS --description=DESCRIPTION Description of the endpoint + --location=LOCATION + Location of the endpoint + --max-wait=MAX_WAIT; default="60m" Time to synchronously wait for the operation to complete, after which the operation continues asynchronously. Ignored if --no-async isn't diff --git a/gcloud/alpha/network-security/security-profiles/threat-prevention/describe b/gcloud/alpha/network-security/security-profiles/threat-prevention/describe new file mode 100644 index 000000000..db0a53681 --- /dev/null +++ b/gcloud/alpha/network-security/security-profiles/threat-prevention/describe @@ -0,0 +1,91 @@ +NAME + gcloud alpha network-security security-profiles threat-prevention describe + - describe a Threat Prevention Security Profile + +SYNOPSIS + gcloud alpha network-security security-profiles threat-prevention describe + (SECURITY_PROFILE : --location=LOCATION --organization=ORGANIZATION) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Show details of a Threat Prevention Security Profile. + + For more examples, refer to the EXAMPLES section below. + +EXAMPLES + To show details of a Threat Prevention security profile named + my-security-profile in an organization, run: + + $ gcloud alpha network-security security-profiles \ threat-prevention describe my-security-profile \ + --organization=1234 --location=global + + To show details of a Threat Prevention security profile named + my-security-profile in a project, run: + + $ gcloud alpha network-security security-profiles \ threat-prevention describe my-security-profile \ + --project=my-project --location=global + +POSITIONAL ARGUMENTS + Security profile resource - Security Profile Name. The arguments in this + group can be used to specify the attributes of this resource. (NOTE) Some + attributes are not given arguments in this group but can be set in other + ways. + + To set the project attribute: + ◆ provide the argument security_profile on the command line with a + fully specified name; + ◆ set the property core/project. This resource can be one of the + following types: + [networksecurity.organizations.locations.securityProfiles, + networksecurity.projects.locations.securityProfiles]. + + This must be specified. + + SECURITY_PROFILE + ID of the security_profile or fully qualified identifier for the + security_profile. + + To set the security_profile attribute: + ▸ provide the argument security_profile on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + Location of the security profile. + + To set the location attribute: + ▸ provide the argument security_profile on the command line with a + fully specified name; + ▸ provide the argument --location on the command line. + + --organization=ORGANIZATION + Organization ID to which the changes should apply. + + To set the organization attribute: + ▸ provide the argument security_profile on the command line with a + fully specified name; + ▸ provide the argument --organization on the command line. Must be + specified for resource of type + [networksecurity.organizations.locations.securityProfiles]. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --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 network-security security-profiles threat-prevention \ + describe + + $ gcloud beta network-security security-profiles threat-prevention \ + describe + diff --git a/gcloud/alpha/network-security/security-profiles/threat-prevention/help b/gcloud/alpha/network-security/security-profiles/threat-prevention/help index ef8833433..f7c73e90d 100644 --- a/gcloud/alpha/network-security/security-profiles/threat-prevention/help +++ b/gcloud/alpha/network-security/security-profiles/threat-prevention/help @@ -70,6 +70,11 @@ EXAMPLES $ gcloud alpha network-security security-profiles \ threat-prevention list --location=global + To describe a Security Profile called my-security-profile, run: + + $ gcloud alpha network-security security-profiles \ + threat-prevention describe my-security-profile + To delete a Security Profile called my-security-profile which includes location as global or region specified and organization ID, run: @@ -96,6 +101,9 @@ COMMANDS delete-override (ALPHA) Delete overrides of Threat Prevention Profile. + describe + (ALPHA) Describe a Threat Prevention Security Profile. + list (ALPHA) List Threat Prevention Security Profiles. diff --git a/gcloud/alpha/network-services/agent-gateways/delete b/gcloud/alpha/network-services/agent-gateways/delete index 8fc1dc0ce..793e09bca 100644 --- a/gcloud/alpha/network-services/agent-gateways/delete +++ b/gcloud/alpha/network-services/agent-gateways/delete @@ -68,5 +68,7 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. + access allowlist. This variant is also available: + + $ gcloud beta network-services agent-gateways delete diff --git a/gcloud/alpha/network-services/agent-gateways/describe b/gcloud/alpha/network-services/agent-gateways/describe index 72870a50a..451ca5cea 100644 --- a/gcloud/alpha/network-services/agent-gateways/describe +++ b/gcloud/alpha/network-services/agent-gateways/describe @@ -63,5 +63,7 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. + access allowlist. This variant is also available: + + $ gcloud beta network-services agent-gateways describe diff --git a/gcloud/alpha/network-services/agent-gateways/export b/gcloud/alpha/network-services/agent-gateways/export index c568b142d..038f4b8d8 100644 --- a/gcloud/alpha/network-services/agent-gateways/export +++ b/gcloud/alpha/network-services/agent-gateways/export @@ -73,5 +73,7 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. + access allowlist. This variant is also available: + + $ gcloud beta network-services agent-gateways export diff --git a/gcloud/alpha/network-services/agent-gateways/help b/gcloud/alpha/network-services/agent-gateways/help index 77e8fb9e0..3f2ebd5cf 100644 --- a/gcloud/alpha/network-services/agent-gateways/help +++ b/gcloud/alpha/network-services/agent-gateways/help @@ -35,5 +35,7 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. + access allowlist. This variant is also available: + + $ gcloud beta network-services agent-gateways diff --git a/gcloud/alpha/network-services/agent-gateways/import b/gcloud/alpha/network-services/agent-gateways/import index d0649bd0a..5ff6b5835 100644 --- a/gcloud/alpha/network-services/agent-gateways/import +++ b/gcloud/alpha/network-services/agent-gateways/import @@ -80,5 +80,7 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. + access allowlist. This variant is also available: + + $ gcloud beta network-services agent-gateways import diff --git a/gcloud/alpha/network-services/agent-gateways/list b/gcloud/alpha/network-services/agent-gateways/list index 8e48bd104..1e0931dc2 100644 --- a/gcloud/alpha/network-services/agent-gateways/list +++ b/gcloud/alpha/network-services/agent-gateways/list @@ -83,5 +83,7 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. + access allowlist. This variant is also available: + + $ gcloud beta network-services agent-gateways list diff --git a/gcloud/alpha/number-registry/custom-ranges/create b/gcloud/alpha/number-registry/custom-ranges/create new file mode 100644 index 000000000..4e293ac71 --- /dev/null +++ b/gcloud/alpha/number-registry/custom-ranges/create @@ -0,0 +1,198 @@ +NAME + gcloud alpha number-registry custom-ranges create - create a custom range + resource + +SYNOPSIS + gcloud alpha number-registry custom-ranges create CUSTOM_RANGE [--async] + [--attributes=[key=KEY],[value=VALUE]] [--description=DESCRIPTION] + [--labels=[LABELS,...]] [--location=LOCATION] + [--parent-range=PARENT_RANGE] [--realm=REALM] [--request-id=REQUEST_ID] + [--ipv4-cidr-range=IPV4_CIDR_RANGE | --ipv6-cidr-range=IPV6_CIDR_RANGE] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Create a custom range resource. + +EXAMPLES + To create a custom range my-custom-range run: + + $ gcloud alpha number-registry custom-ranges create \ + my-custom-range --location=global --realm=my-realm \ + --ipv4-cidr-range=10.0.0.0/24 \ + +POSITIONAL ARGUMENTS + CustomRange resource - Identifier. name of resource 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 custom_range 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 custom_range on the command line with a fully + specified name; + ◆ provide the argument --location on the command line. + + This must be specified. + + CUSTOM_RANGE + ID of the customRange or fully qualified identifier for the + customRange. + + To set the custom_range attribute: + ▸ provide the argument custom_range on the command line. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --attributes=[key=KEY],[value=VALUE] + The attributes of the CustomRange. + + key + Key of attribute. + + value + Value of attribute. + + Shorthand Example: + + --attributes=key=string,value=string --attributes=key=string,value=string + + JSON Example: + + --attributes='[{"key": "string", "value": "string"}]' + + File Example: + + --attributes=path_to_file.(yaml|json) + + --description=DESCRIPTION + Description of the CustomRange. + + --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) + + --location=LOCATION + For resources [custom_range, parent-range, realm], provides fallback + value for resource location attribute. When the resource's full URI + path is not provided, location will fallback to this flag value. + + CustomRange resource - The parent range of the CustomRange. Do not allow + setting parent range if realm is specified. Format must follow this + pattern: + projects/{project}/locations/{location}/customRanges/{custom_range} 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 --parent-range 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 --parent-range on the command line with a fully + specified name; + ◆ provide the argument --location on the command line. + + --parent-range=PARENT_RANGE + ID of the customRange or fully qualified identifier for the + customRange. + + To set the custom-range attribute: + ◆ provide the argument --parent-range on the command line. + + Realm resource - The realm of the CustomRange. The realm must be in the + same project as the custom range. Do not allow setting realm if parent + range is specified, since the realm should be inherited from the parent + range. Format must follow this pattern: + projects/{project}/locations/{location}/realms/{realm} 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 --realm 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 --realm on the command line with a fully + specified name; + ◆ provide the argument --location on the command line. + + --realm=REALM + ID of the realm or fully qualified identifier for the realm. + + To set the realm attribute: + ◆ provide the argument --realm on the command line. + + --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). + + Arguments for the ip cidr range. + + At most one of these can be specified: + + --ipv4-cidr-range=IPV4_CIDR_RANGE + The IPv4 CIDR range of the CustomRange. + + --ipv6-cidr-range=IPV6_CIDR_RANGE + The IPv6 CIDR range of the CustomRange. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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 cloudnumberregistry/v1alpha API. The full + documentation for this API can be found at: + https://docs.cloud.google.com/number-registry/reference/rest + +NOTES + This command is currently in alpha and might change without notice. If this + command fails 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/number-registry/custom-ranges/delete b/gcloud/alpha/number-registry/custom-ranges/delete new file mode 100644 index 000000000..eb229afbb --- /dev/null +++ b/gcloud/alpha/number-registry/custom-ranges/delete @@ -0,0 +1,92 @@ +NAME + gcloud alpha number-registry custom-ranges delete - delete a single custom + range resource + +SYNOPSIS + gcloud alpha number-registry custom-ranges delete + (CUSTOM_RANGE : --location=LOCATION) [--async] [--force] + [--request-id=REQUEST_ID] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Deletes a single custom range. + +EXAMPLES + To delete a custom range my-custom-range run: + + $ gcloud alpha number-registry custom-ranges delete \ + my-custom-range --location=global + +POSITIONAL ARGUMENTS + CustomRange 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 custom_range on the command line with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + CUSTOM_RANGE + ID of the customRange or fully qualified identifier for the + customRange. + + To set the custom_range attribute: + ▸ provide the argument custom_range 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 customRange resource. + + To set the location attribute: + ▸ provide the argument custom_range 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. + + --force + If set to true, all associated resources will be deleted. + + --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 cloudnumberregistry/v1alpha API. The full + documentation for this API can be found at: + https://docs.cloud.google.com/number-registry/reference/rest + +NOTES + This command is currently in alpha and might change without notice. If this + command fails 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/number-registry/custom-ranges/describe b/gcloud/alpha/number-registry/custom-ranges/describe new file mode 100644 index 000000000..4320bb104 --- /dev/null +++ b/gcloud/alpha/number-registry/custom-ranges/describe @@ -0,0 +1,68 @@ +NAME + gcloud alpha number-registry custom-ranges describe - gets details of a + single custom range resource + +SYNOPSIS + gcloud alpha number-registry custom-ranges describe + (CUSTOM_RANGE : --location=LOCATION) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Gets details of a single custom range resource. + +EXAMPLES + To get the details of a single custom range my-custom-range run: + + $ gcloud alpha number-registry custom-ranges describe \ + my-custom-range --location=global + +POSITIONAL ARGUMENTS + CustomRange 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 custom_range on the command line with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + CUSTOM_RANGE + ID of the customRange or fully qualified identifier for the + customRange. + + To set the custom_range attribute: + ▸ provide the argument custom_range 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 customRange resource. + + To set the location attribute: + ▸ provide the argument custom_range 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 cloudnumberregistry/v1alpha API. The full + documentation for this API can be found at: + https://docs.cloud.google.com/number-registry/reference/rest + +NOTES + This command is currently in alpha and might change without notice. If this + command fails 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/number-registry/custom-ranges/find-free-ip-ranges b/gcloud/alpha/number-registry/custom-ranges/find-free-ip-ranges new file mode 100644 index 000000000..3dbecab8e --- /dev/null +++ b/gcloud/alpha/number-registry/custom-ranges/find-free-ip-ranges @@ -0,0 +1,94 @@ +NAME + gcloud alpha number-registry custom-ranges find-free-ip-ranges - find free + IP ranges in a custom range + +SYNOPSIS + gcloud alpha number-registry custom-ranges find-free-ip-ranges + (CUSTOM_RANGE : --location=LOCATION) + --cidr-prefix-length=CIDR_PREFIX_LENGTH [--range-count=RANGE_COUNT] + [--request-id=REQUEST_ID] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Find free IP ranges in a custom range. + +EXAMPLES + To find free IP ranges in a custom range my-custom-range run: + + $ gcloud alpha number-registry custom-ranges find-free-ip-ranges \ + my-custom-range --location=global --cidr_prefix_length=24 \ + --range-count=1 + +POSITIONAL ARGUMENTS + CustomRange resource - Name of the CustomRange. The arguments in this + group can be used to specify the attributes of this resource. (NOTE) Some + attributes are not given arguments in this group but can be set in other + ways. + + To set the project attribute: + ◆ provide the argument custom_range on the command line with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + CUSTOM_RANGE + ID of the customRange or fully qualified identifier for the + customRange. + + To set the custom_range attribute: + ▸ provide the argument custom_range 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 customRange resource. + + To set the location attribute: + ▸ provide the argument custom_range on the command line with a + fully specified name; + ▸ provide the argument --location on the command line. + +REQUIRED FLAGS + --cidr-prefix-length=CIDR_PREFIX_LENGTH + The prefix length of the free IP ranges to find. + +OPTIONAL FLAGS + --range-count=RANGE_COUNT + The number of free IP ranges to find. + + --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 cloudnumberregistry/v1alpha API. The full + documentation for this API can be found at: + https://docs.cloud.google.com/number-registry/reference/rest + +NOTES + This command is currently in alpha and might change without notice. If this + command fails 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/number-registry/custom-ranges/help b/gcloud/alpha/number-registry/custom-ranges/help new file mode 100644 index 000000000..a36886564 --- /dev/null +++ b/gcloud/alpha/number-registry/custom-ranges/help @@ -0,0 +1,44 @@ +NAME + gcloud alpha number-registry custom-ranges - manage custom range resources + +SYNOPSIS + gcloud alpha number-registry custom-ranges COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Manage custom range 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 + (ALPHA) Create a custom range resource. + + delete + (ALPHA) Delete a single custom range resource. + + describe + (ALPHA) Gets details of a single custom range resource. + + find-free-ip-ranges + (ALPHA) Find free IP ranges in a custom range. + + list + (ALPHA) List custom range resources. + + show-utilization + (ALPHA) Show utilization of a custom range. + + update + (ALPHA) Update the parameters of a single custom range resource. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/number-registry/custom-ranges/list b/gcloud/alpha/number-registry/custom-ranges/list new file mode 100644 index 000000000..6174671fd --- /dev/null +++ b/gcloud/alpha/number-registry/custom-ranges/list @@ -0,0 +1,87 @@ +NAME + gcloud alpha number-registry custom-ranges list - list custom range + resources + +SYNOPSIS + gcloud alpha number-registry custom-ranges list --location=LOCATION + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) List custom range resources. + +EXAMPLES + To list all custom ranges run: + + $ gcloud alpha number-registry custom-ranges list --location=global + +REQUIRED FLAGS + Location resource - Parent value for ListCustomRangesRequest 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 cloudnumberregistry/v1alpha API. The full + documentation for this API can be found at: + https://docs.cloud.google.com/number-registry/reference/rest + +NOTES + This command is currently in alpha and might change without notice. If this + command fails 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/number-registry/custom-ranges/show-utilization b/gcloud/alpha/number-registry/custom-ranges/show-utilization new file mode 100644 index 000000000..6cced7cd9 --- /dev/null +++ b/gcloud/alpha/number-registry/custom-ranges/show-utilization @@ -0,0 +1,68 @@ +NAME + gcloud alpha number-registry custom-ranges show-utilization - show + utilization of a custom range + +SYNOPSIS + gcloud alpha number-registry custom-ranges show-utilization + (CUSTOM_RANGE : --location=LOCATION) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Show utilization of a custom range. + +EXAMPLES + To show the utilization of a custom range my-custom-range run: + + $ gcloud alpha number-registry custom-ranges show-utilization \ + my-custom-range --location=global + +POSITIONAL ARGUMENTS + CustomRange 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 custom_range on the command line with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + CUSTOM_RANGE + ID of the customRange or fully qualified identifier for the + customRange. + + To set the custom_range attribute: + ▸ provide the argument custom_range 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 customRange resource. + + To set the location attribute: + ▸ provide the argument custom_range 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 cloudnumberregistry/v1alpha API. The full + documentation for this API can be found at: + https://docs.cloud.google.com/number-registry/reference/rest + +NOTES + This command is currently in alpha and might change without notice. If this + command fails 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/number-registry/custom-ranges/update b/gcloud/alpha/number-registry/custom-ranges/update new file mode 100644 index 000000000..af8643718 --- /dev/null +++ b/gcloud/alpha/number-registry/custom-ranges/update @@ -0,0 +1,326 @@ +NAME + gcloud alpha number-registry custom-ranges update - update the parameters + of a single custom range resource + +SYNOPSIS + gcloud alpha number-registry custom-ranges update CUSTOM_RANGE [--async] + [--description=DESCRIPTION] [--location=LOCATION] + [--request-id=REQUEST_ID] + [--attributes=[key=KEY],[value=VALUE] + | --add-attributes=[key=KEY],[value=VALUE] --clear-attributes + | --remove-attributes=[key=KEY],[value=VALUE]] + [--clear-parent-range | --parent-range=PARENT_RANGE] + [--clear-realm | --realm=REALM] + [--ipv4-cidr-range=IPV4_CIDR_RANGE | --ipv6-cidr-range=IPV6_CIDR_RANGE] + [--labels=[LABELS,...] + | --update-labels=[UPDATE_LABELS,...] --clear-labels + | --remove-labels=REMOVE_LABELS] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Update a custom range resource. + +EXAMPLES + To update the labels of a custom range my-custom-range run: + + $ gcloud alpha number-registry custom-ranges update \ + my-custom-range --location=global --update-labels=key=value + +POSITIONAL ARGUMENTS + CustomRange resource - Identifier. name of resource 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 custom_range 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 custom_range on the command line with a fully + specified name; + ◆ provide the argument --location on the command line. + + This must be specified. + + CUSTOM_RANGE + ID of the customRange or fully qualified identifier for the + customRange. + + To set the custom_range attribute: + ▸ provide the argument custom_range on the command line. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --description=DESCRIPTION + Description of the CustomRange. + + --location=LOCATION + For resources [custom_range, parent-range, realm], provides fallback + value for resource location attribute. When the resource's full URI + path is not provided, location will fallback to this flag value. + + --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 attributes. + + At most one of these can be specified: + + --attributes=[key=KEY],[value=VALUE] + Set attributes to new value. The attributes of the CustomRange. + + key + Key of attribute. + + value + Value of attribute. + + Shorthand Example: + + --attributes=key=string,value=string --attributes=key=string,value=string + + JSON Example: + + --attributes='[{"key": "string", "value": "string"}]' + + File Example: + + --attributes=path_to_file.(yaml|json) + + Or at least one of these can be specified: + + --add-attributes=[key=KEY],[value=VALUE] + Add new value to attributes list. The attributes of the + CustomRange. + + key + Key of attribute. + + value + Value of attribute. + + Shorthand Example: + + --add-attributes=key=string,value=string --add-attributes=key=string,value=string + + JSON Example: + + --add-attributes='[{"key": "string", "value": "string"}]' + + File Example: + + --add-attributes=path_to_file.(yaml|json) + + At most one of these can be specified: + + --clear-attributes + Clear attributes value and set to empty list. + + --remove-attributes=[key=KEY],[value=VALUE] + Remove existing value from attributes list. The attributes of the + CustomRange. + + key + Key of attribute. + + value + Value of attribute. + + Shorthand Example: + + --remove-attributes=key=string,value=string --remove-attributes=key=string,value=string + + JSON Example: + + --remove-attributes='[{"key": "string", "value": "string"}]' + + File Example: + + --remove-attributes=path_to_file.(yaml|json) + + Update parent_range. + + At most one of these can be specified: + + --clear-parent-range + Clear parent_range value and set to null. + + CustomRange resource - Set parent_range to new value. + + The parent range of the CustomRange. Do not allow setting parent range + if realm is specified. Format must follow this pattern: + projects/{project}/locations/{location}/customRanges/{custom_range} 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 --parent-range 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 --parent-range on the command line with a + fully specified name; + ▸ provide the argument --location on the command line. + + --parent-range=PARENT_RANGE + ID of the customRange or fully qualified identifier for the + customRange. + + To set the custom-range attribute: + ▸ provide the argument --parent-range on the command line. + + Update realm. + + At most one of these can be specified: + + --clear-realm + Clear realm value and set to null. + + Realm resource - Set realm to new value. + + The realm of the CustomRange. The realm must be in the same project as + the custom range. Do not allow setting realm if parent range is + specified, since the realm should be inherited from the parent range. + Format must follow this pattern: + projects/{project}/locations/{location}/realms/{realm} 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 --realm 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 --realm on the command line with a fully + specified name; + ▸ provide the argument --location on the command line. + + --realm=REALM + ID of the realm or fully qualified identifier for the realm. + + To set the realm attribute: + ▸ provide the argument --realm on the command line. + + Arguments for the ip cidr range. + + At most one of these can be specified: + + --ipv4-cidr-range=IPV4_CIDR_RANGE + The IPv4 CIDR range of the CustomRange. + + --ipv6-cidr-range=IPV6_CIDR_RANGE + The IPv6 CIDR range of the CustomRange. + + 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) + + Or at least one of these can be specified: + + --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. Sets remove_labels value. + + Shorthand Example: + + --remove-labels=string,string + + JSON Example: + + --remove-labels=["string"] + + File Example: + + --remove-labels=path_to_file.(yaml|json) + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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 cloudnumberregistry/v1alpha API. The full + documentation for this API can be found at: + https://docs.cloud.google.com/number-registry/reference/rest + +NOTES + This command is currently in alpha and might change without notice. If this + command fails 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/number-registry/discovered-ranges/describe b/gcloud/alpha/number-registry/discovered-ranges/describe new file mode 100644 index 000000000..0aed11097 --- /dev/null +++ b/gcloud/alpha/number-registry/discovered-ranges/describe @@ -0,0 +1,68 @@ +NAME + gcloud alpha number-registry discovered-ranges describe - gets details of a + single discovered range resource + +SYNOPSIS + gcloud alpha number-registry discovered-ranges describe + (DISCOVERED_RANGE : --location=LOCATION) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Gets details of a single discovered range resource. + +EXAMPLES + To get the details of a single discovered range my-discovered-range run: + + $ gcloud alpha number-registry discovered-ranges describe \ + my-discovered-range --location=global + +POSITIONAL ARGUMENTS + DiscoveredRange 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 discovered_range 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. + + DISCOVERED_RANGE + ID of the discoveredRange or fully qualified identifier for the + discoveredRange. + + To set the discovered_range attribute: + ▸ provide the argument discovered_range 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 discoveredRange resource. + + To set the location attribute: + ▸ provide the argument discovered_range 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 cloudnumberregistry/v1alpha API. The full + documentation for this API can be found at: + https://docs.cloud.google.com/number-registry/reference/rest + +NOTES + This command is currently in alpha and might change without notice. If this + command fails 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/number-registry/discovered-ranges/find-free-ip-ranges b/gcloud/alpha/number-registry/discovered-ranges/find-free-ip-ranges new file mode 100644 index 000000000..7cb6d142f --- /dev/null +++ b/gcloud/alpha/number-registry/discovered-ranges/find-free-ip-ranges @@ -0,0 +1,93 @@ +NAME + gcloud alpha number-registry discovered-ranges find-free-ip-ranges - find + free IP ranges in a discovered range + +SYNOPSIS + gcloud alpha number-registry discovered-ranges find-free-ip-ranges + (DISCOVERED_RANGE : --location=LOCATION) + --cidr-prefix-length=CIDR_PREFIX_LENGTH [--range-count=RANGE_COUNT] + [--request-id=REQUEST_ID] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Find free IP ranges in a discovered range. + +EXAMPLES + To find free IP ranges in a discovered range my-discovered-range run: + + $ gcloud alpha number-registry discovered-ranges \ find-free-ip-ranges my-discovered-range --location=global \ + --cidr_prefix_length=24 --range-count=1 + +POSITIONAL ARGUMENTS + DiscoveredRange resource - Name of the DiscoveredRange. 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 discovered_range 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. + + DISCOVERED_RANGE + ID of the discoveredRange or fully qualified identifier for the + discoveredRange. + + To set the discovered_range attribute: + ▸ provide the argument discovered_range 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 discoveredRange resource. + + To set the location attribute: + ▸ provide the argument discovered_range on the command line with a + fully specified name; + ▸ provide the argument --location on the command line. + +REQUIRED FLAGS + --cidr-prefix-length=CIDR_PREFIX_LENGTH + The prefix length of the free IP ranges to find. + +OPTIONAL FLAGS + --range-count=RANGE_COUNT + The number of free IP ranges to find. + + --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 cloudnumberregistry/v1alpha API. The full + documentation for this API can be found at: + https://docs.cloud.google.com/number-registry/reference/rest + +NOTES + This command is currently in alpha and might change without notice. If this + command fails 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/number-registry/discovered-ranges/help b/gcloud/alpha/number-registry/discovered-ranges/help new file mode 100644 index 000000000..ad92ed0f7 --- /dev/null +++ b/gcloud/alpha/number-registry/discovered-ranges/help @@ -0,0 +1,37 @@ +NAME + gcloud alpha number-registry discovered-ranges - manage discovered range + resources + +SYNOPSIS + gcloud alpha number-registry discovered-ranges COMMAND + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Manage discovered range resources. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + describe + (ALPHA) Gets details of a single discovered range resource. + + find-free-ip-ranges + (ALPHA) Find free IP ranges in a discovered range. + + list + (ALPHA) List discovered range resources. + + show-utilization + (ALPHA) Show utilization of a discovered range. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails 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/number-registry/discovered-ranges/list b/gcloud/alpha/number-registry/discovered-ranges/list new file mode 100644 index 000000000..d95416526 --- /dev/null +++ b/gcloud/alpha/number-registry/discovered-ranges/list @@ -0,0 +1,88 @@ +NAME + gcloud alpha number-registry discovered-ranges list - list discovered range + resources + +SYNOPSIS + gcloud alpha number-registry discovered-ranges list --location=LOCATION + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) List discovered range resources. + +EXAMPLES + To list all discovered ranges run: + + $ gcloud alpha number-registry discovered-ranges list \ + --location=global + +REQUIRED FLAGS + Location resource - Parent value for ListDiscoveredRangesRequest 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 cloudnumberregistry/v1alpha API. The full + documentation for this API can be found at: + https://docs.cloud.google.com/number-registry/reference/rest + +NOTES + This command is currently in alpha and might change without notice. If this + command fails 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/number-registry/discovered-ranges/show-utilization b/gcloud/alpha/number-registry/discovered-ranges/show-utilization new file mode 100644 index 000000000..c6c73b5de --- /dev/null +++ b/gcloud/alpha/number-registry/discovered-ranges/show-utilization @@ -0,0 +1,68 @@ +NAME + gcloud alpha number-registry discovered-ranges show-utilization - show + utilization of a discovered range + +SYNOPSIS + gcloud alpha number-registry discovered-ranges show-utilization + (DISCOVERED_RANGE : --location=LOCATION) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Show utilization of a discovered range. + +EXAMPLES + To show the utilization of a discovered range my-discovered-range run: + + $ gcloud alpha number-registry discovered-ranges show-utilization \ + my-discovered-range --location=global + +POSITIONAL ARGUMENTS + DiscoveredRange 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 discovered_range 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. + + DISCOVERED_RANGE + ID of the discoveredRange or fully qualified identifier for the + discoveredRange. + + To set the discovered_range attribute: + ▸ provide the argument discovered_range 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 discoveredRange resource. + + To set the location attribute: + ▸ provide the argument discovered_range 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 cloudnumberregistry/v1alpha API. The full + documentation for this API can be found at: + https://docs.cloud.google.com/number-registry/reference/rest + +NOTES + This command is currently in alpha and might change without notice. If this + command fails 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/number-registry/help b/gcloud/alpha/number-registry/help new file mode 100644 index 000000000..1956bfbba --- /dev/null +++ b/gcloud/alpha/number-registry/help @@ -0,0 +1,42 @@ +NAME + gcloud alpha number-registry - manage Cloud Number Registry resources + +SYNOPSIS + gcloud alpha number-registry GROUP [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Manage Cloud Number Registry resources. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +GROUPS + GROUP is one of the following: + + custom-ranges + (ALPHA) Manage custom range resources. + + discovered-ranges + (ALPHA) Manage discovered range resources. + + ipam-admin-scopes + (ALPHA) Manage IPAM admin scopes. This is the scope of which resources + CNR can discover. + + operations + (ALPHA) Manage Operation resources. + + realms + (ALPHA) Manage discovered and custom realm resources. + + registry-books + (ALPHA) Manage registry book resources. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/number-registry/ipam-admin-scopes/check-availability b/gcloud/alpha/number-registry/ipam-admin-scopes/check-availability new file mode 100644 index 000000000..261c23776 --- /dev/null +++ b/gcloud/alpha/number-registry/ipam-admin-scopes/check-availability @@ -0,0 +1,58 @@ +NAME + gcloud alpha number-registry ipam-admin-scopes check-availability - check + the availability of IPAM admin scopes + +SYNOPSIS + gcloud alpha number-registry ipam-admin-scopes check-availability + --location=LOCATION --scopes=[SCOPES,...] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Checks whether the scope of the project is available to be managed. + +EXAMPLES + To check the availability of an organization scope run: + + $ gcloud alpha number-registry ipam-admin-scopes \ check-availability --location=global \ + --scopes organizations/123456789 + +REQUIRED FLAGS + Location resource - Parent value for the IpamAdminScopes. 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. + + --scopes=[SCOPES,...] + The scopes of the IpamAdminScopes to look for. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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 cloudnumberregistry/v1alpha API. The full + documentation for this API can be found at: + https://docs.cloud.google.com/number-registry/reference/rest + +NOTES + This command is currently in alpha and might change without notice. If this + command fails 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/number-registry/ipam-admin-scopes/cleanup b/gcloud/alpha/number-registry/ipam-admin-scopes/cleanup new file mode 100644 index 000000000..a322ad474 --- /dev/null +++ b/gcloud/alpha/number-registry/ipam-admin-scopes/cleanup @@ -0,0 +1,89 @@ +NAME + gcloud alpha number-registry ipam-admin-scopes cleanup - clean up a single + IPAM admin scope resource + +SYNOPSIS + gcloud alpha number-registry ipam-admin-scopes cleanup + (IPAM_ADMIN_SCOPE : --location=LOCATION) [--async] + [--request-id=REQUEST_ID] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Clean up a single IPAM admin scope. + +EXAMPLES + To clean up an IPAM admin scope my-ipam-admin-scope run: + + $ gcloud alpha number-registry ipam-admin-scopes cleanup \ + my-ipam-admin-scope --location=global + +POSITIONAL ARGUMENTS + IpamAdminScope 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 ipam_admin_scope 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. + + IPAM_ADMIN_SCOPE + ID of the ipamAdminScope or fully qualified identifier for the + ipamAdminScope. + + To set the ipam_admin_scope attribute: + ▸ provide the argument ipam_admin_scope 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 ipamAdminScope resource. + + To set the location attribute: + ▸ provide the argument ipam_admin_scope 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 cloudnumberregistry/v1alpha API. The full + documentation for this API can be found at: + https://docs.cloud.google.com/number-registry/reference/rest + +NOTES + This command is currently in alpha and might change without notice. If this + command fails 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/number-registry/ipam-admin-scopes/create b/gcloud/alpha/number-registry/ipam-admin-scopes/create new file mode 100644 index 000000000..d52019832 --- /dev/null +++ b/gcloud/alpha/number-registry/ipam-admin-scopes/create @@ -0,0 +1,130 @@ +NAME + gcloud alpha number-registry ipam-admin-scopes create - create an IPAM + admin scope resource + +SYNOPSIS + gcloud alpha number-registry ipam-admin-scopes create + (IPAM_ADMIN_SCOPE : --location=LOCATION) + --enabled-addon-platforms=[ENABLED_ADDON_PLATFORMS,...] + --scopes=[SCOPES,...] [--async] [--labels=[LABELS,...]] + [--request-id=REQUEST_ID] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Create an IPAM admin scope resource. + +EXAMPLES + To create an IPAM admin scope my-ipam-admin-scope run: + + $ gcloud alpha number-registry ipam-admin-scopes create \ + my-ipam-admin-scope --location=global + +POSITIONAL ARGUMENTS + IpamAdminScope resource - Identifier. name of 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 ipam_admin_scope 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. + + IPAM_ADMIN_SCOPE + ID of the ipamAdminScope or fully qualified identifier for the + ipamAdminScope. + + To set the ipam_admin_scope attribute: + ▸ provide the argument ipam_admin_scope 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 ipamAdminScope resource. + + To set the location attribute: + ▸ provide the argument ipam_admin_scope on the command line with a + fully specified name; + ▸ provide the argument --location on the command line. + +REQUIRED FLAGS + --enabled-addon-platforms=[ENABLED_ADDON_PLATFORMS,...] + Addon platforms that are enabled for this IPAM admin scope. Cloud + Number Registry only discovers the IP addresses from the enabled + platforms. ENABLED_ADDON_PLATFORMS must be one of: + + compute-engine + Google Compute Engine. + gce + Deprecated: Use COMPUTE_ENGINE instead. + + --scopes=[SCOPES,...] + Administrative scopes enabled for IP address discovery and management. + For example, "organizations/1234567890". Minimum of 1 scope is + required. In preview, only one organization scope is allowed. + +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) + + --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 cloudnumberregistry/v1alpha API. The full + documentation for this API can be found at: + https://docs.cloud.google.com/number-registry/reference/rest + +NOTES + This command is currently in alpha and might change without notice. If this + command fails 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/number-registry/ipam-admin-scopes/delete b/gcloud/alpha/number-registry/ipam-admin-scopes/delete new file mode 100644 index 000000000..cf6921d35 --- /dev/null +++ b/gcloud/alpha/number-registry/ipam-admin-scopes/delete @@ -0,0 +1,92 @@ +NAME + gcloud alpha number-registry ipam-admin-scopes delete - delete a single + IPAM admin scope resource + +SYNOPSIS + gcloud alpha number-registry ipam-admin-scopes delete + (IPAM_ADMIN_SCOPE : --location=LOCATION) [--async] [--force] + [--request-id=REQUEST_ID] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Deletes a single IPAM admin scope. + +EXAMPLES + To delete an IPAM admin scope my-ipam-admin-scope run: + + $ gcloud alpha number-registry ipam-admin-scopes delete \ + my-ipam-admin-scope --location=global + +POSITIONAL ARGUMENTS + IpamAdminScope 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 ipam_admin_scope 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. + + IPAM_ADMIN_SCOPE + ID of the ipamAdminScope or fully qualified identifier for the + ipamAdminScope. + + To set the ipam_admin_scope attribute: + ▸ provide the argument ipam_admin_scope 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 ipamAdminScope resource. + + To set the location attribute: + ▸ provide the argument ipam_admin_scope 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. + + --force + If set to true, all associated resources will be deleted. + + --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 cloudnumberregistry/v1alpha API. The full + documentation for this API can be found at: + https://docs.cloud.google.com/number-registry/reference/rest + +NOTES + This command is currently in alpha and might change without notice. If this + command fails 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/number-registry/ipam-admin-scopes/describe b/gcloud/alpha/number-registry/ipam-admin-scopes/describe new file mode 100644 index 000000000..55cb11d30 --- /dev/null +++ b/gcloud/alpha/number-registry/ipam-admin-scopes/describe @@ -0,0 +1,68 @@ +NAME + gcloud alpha number-registry ipam-admin-scopes describe - gets details of a + single IPAM admin scope resource + +SYNOPSIS + gcloud alpha number-registry ipam-admin-scopes describe + (IPAM_ADMIN_SCOPE : --location=LOCATION) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Gets details of a single IPAM admin scope resource. + +EXAMPLES + To get the details of a single IPAM admin scope my-ipam-admin-scope run: + + $ gcloud alpha number-registry ipam-admin-scopes describe \ + my-ipam-admin-scope --location=global + +POSITIONAL ARGUMENTS + IpamAdminScope 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 ipam_admin_scope 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. + + IPAM_ADMIN_SCOPE + ID of the ipamAdminScope or fully qualified identifier for the + ipamAdminScope. + + To set the ipam_admin_scope attribute: + ▸ provide the argument ipam_admin_scope 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 ipamAdminScope resource. + + To set the location attribute: + ▸ provide the argument ipam_admin_scope 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 cloudnumberregistry/v1alpha API. The full + documentation for this API can be found at: + https://docs.cloud.google.com/number-registry/reference/rest + +NOTES + This command is currently in alpha and might change without notice. If this + command fails 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/number-registry/ipam-admin-scopes/disable b/gcloud/alpha/number-registry/ipam-admin-scopes/disable new file mode 100644 index 000000000..1cf062ad7 --- /dev/null +++ b/gcloud/alpha/number-registry/ipam-admin-scopes/disable @@ -0,0 +1,89 @@ +NAME + gcloud alpha number-registry ipam-admin-scopes disable - disable a single + IPAM admin scope resource + +SYNOPSIS + gcloud alpha number-registry ipam-admin-scopes disable + (IPAM_ADMIN_SCOPE : --location=LOCATION) [--async] + [--request-id=REQUEST_ID] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Disable a single IPAM admin scope. + +EXAMPLES + To disable an IPAM admin scope my-ipam-admin-scope run: + + $ gcloud alpha number-registry ipam-admin-scopes disable \ + my-ipam-admin-scope --location=global + +POSITIONAL ARGUMENTS + IpamAdminScope 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 ipam_admin_scope 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. + + IPAM_ADMIN_SCOPE + ID of the ipamAdminScope or fully qualified identifier for the + ipamAdminScope. + + To set the ipam_admin_scope attribute: + ▸ provide the argument ipam_admin_scope 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 ipamAdminScope resource. + + To set the location attribute: + ▸ provide the argument ipam_admin_scope 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 cloudnumberregistry/v1alpha API. The full + documentation for this API can be found at: + https://docs.cloud.google.com/number-registry/reference/rest + +NOTES + This command is currently in alpha and might change without notice. If this + command fails 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/number-registry/ipam-admin-scopes/help b/gcloud/alpha/number-registry/ipam-admin-scopes/help new file mode 100644 index 000000000..b1d129c3f --- /dev/null +++ b/gcloud/alpha/number-registry/ipam-admin-scopes/help @@ -0,0 +1,50 @@ +NAME + gcloud alpha number-registry ipam-admin-scopes - manage IPAM admin scopes. + This is the scope of which resources CNR can discover + +SYNOPSIS + gcloud alpha number-registry ipam-admin-scopes COMMAND + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Manage IPAM admin scopes. This is the scope of which resources CNR + can discover. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + check-availability + (ALPHA) Check the availability of IPAM admin scopes. + + cleanup + (ALPHA) Clean up a single IPAM admin scope resource. + + create + (ALPHA) Create an IPAM admin scope resource. + + delete + (ALPHA) Delete a single IPAM admin scope resource. + + describe + (ALPHA) Gets details of a single IPAM admin scope resource. + + disable + (ALPHA) Disable a single IPAM admin scope resource. + + list + (ALPHA) List IPAM admin scope resources. + + update + (ALPHA) Update the parameters of a single IPAM admin scope resource. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/number-registry/ipam-admin-scopes/list b/gcloud/alpha/number-registry/ipam-admin-scopes/list new file mode 100644 index 000000000..2ceb609d1 --- /dev/null +++ b/gcloud/alpha/number-registry/ipam-admin-scopes/list @@ -0,0 +1,88 @@ +NAME + gcloud alpha number-registry ipam-admin-scopes list - list IPAM admin scope + resources + +SYNOPSIS + gcloud alpha number-registry ipam-admin-scopes list --location=LOCATION + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) List IPAM admin scope resources. + +EXAMPLES + To list all IPAM admin scopes run: + + $ gcloud alpha number-registry ipam-admin-scopes list \ + --location=global + +REQUIRED FLAGS + Location resource - Parent value for ListIpamAdminScopesRequest 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 cloudnumberregistry/v1alpha API. The full + documentation for this API can be found at: + https://docs.cloud.google.com/number-registry/reference/rest + +NOTES + This command is currently in alpha and might change without notice. If this + command fails 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/number-registry/ipam-admin-scopes/update b/gcloud/alpha/number-registry/ipam-admin-scopes/update new file mode 100644 index 000000000..9e003e7f5 --- /dev/null +++ b/gcloud/alpha/number-registry/ipam-admin-scopes/update @@ -0,0 +1,182 @@ +NAME + gcloud alpha number-registry ipam-admin-scopes update - update the + parameters of a single IPAM admin scope resource + +SYNOPSIS + gcloud alpha number-registry ipam-admin-scopes update + (IPAM_ADMIN_SCOPE : --location=LOCATION) [--async] + [--enabled-addon-platforms=[ENABLED_ADDON_PLATFORMS,...]] + [--request-id=REQUEST_ID] [--scopes=[SCOPES,...]] + [--labels=[LABELS,...] + | --update-labels=[UPDATE_LABELS,...] --clear-labels + | --remove-labels=REMOVE_LABELS] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Update an IPAM admin scope resource. + +EXAMPLES + To update the labels of an IPAM admin scope my-ipam-admin-scope run: + + $ gcloud alpha number-registry ipam-admin-scopes update \ + my-ipam-admin-scope --location=global --update-labels=key=value + +POSITIONAL ARGUMENTS + IpamAdminScope resource - Identifier. name of 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 ipam_admin_scope 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. + + IPAM_ADMIN_SCOPE + ID of the ipamAdminScope or fully qualified identifier for the + ipamAdminScope. + + To set the ipam_admin_scope attribute: + ▸ provide the argument ipam_admin_scope 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 ipamAdminScope resource. + + To set the location attribute: + ▸ provide the argument ipam_admin_scope 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. + + --enabled-addon-platforms=[ENABLED_ADDON_PLATFORMS,...] + Addon platforms that are enabled for this IPAM admin scope. Cloud + Number Registry only discovers the IP addresses from the enabled + platforms. ENABLED_ADDON_PLATFORMS must be one of: + + compute-engine + Google Compute Engine. + gce + Deprecated: Use COMPUTE_ENGINE instead. + + --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). + + --scopes=[SCOPES,...] + Administrative scopes enabled for IP address discovery and management. + For example, "organizations/1234567890". Minimum of 1 scope is + required. In preview, only one organization scope is allowed. + + 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) + + Or at least one of these can be specified: + + --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. Sets remove_labels value. + + Shorthand Example: + + --remove-labels=string,string + + JSON Example: + + --remove-labels=["string"] + + File Example: + + --remove-labels=path_to_file.(yaml|json) + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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 cloudnumberregistry/v1alpha API. The full + documentation for this API can be found at: + https://docs.cloud.google.com/number-registry/reference/rest + +NOTES + This command is currently in alpha and might change without notice. If this + command fails 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/lifesciences/operations/describe b/gcloud/alpha/number-registry/operations/cancel similarity index 67% rename from gcloud/alpha/lifesciences/operations/describe rename to gcloud/alpha/number-registry/operations/cancel index eb412966c..58e4748cd 100644 --- a/gcloud/alpha/lifesciences/operations/describe +++ b/gcloud/alpha/number-registry/operations/cancel @@ -1,22 +1,21 @@ NAME - gcloud alpha lifesciences operations describe - describe a Cloud Life - Sciences operation + gcloud alpha number-registry operations cancel - cancel operations SYNOPSIS - gcloud alpha lifesciences operations describe + gcloud alpha number-registry operations cancel (OPERATION : --location=LOCATION) [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) Describe a Cloud Life Sciences operation. + (ALPHA) Cancel an operation EXAMPLES - To describe an operation called my-operation, run: + To cancel the operation, run: - $ gcloud alpha lifesciences operations describe my-operation + $ gcloud alpha number-registry operations cancel POSITIONAL ARGUMENTS - Operation resource - Cloud Life Sciences operation to describe. The - arguments in this group can be used to specify the attributes of this + Operation resource - The name of the operation resource to be cancelled. + 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. @@ -38,13 +37,12 @@ POSITIONAL ARGUMENTS arguments in this group are specified. --location=LOCATION - Google Cloud location. + The location id of the operation resource. 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; - ▸ set the property lifesciences/location. + ▸ provide the argument --location on the command line. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, @@ -55,14 +53,13 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. API REFERENCE - This command uses the lifesciences/v2beta API. The full documentation for - this API can be found at: https://cloud.google.com/life-sciences + This command uses the cloudnumberregistry/v1alpha API. The full + documentation for this API can be found at: + https://docs.cloud.google.com/number-registry/reference/rest NOTES This command is currently in alpha and might change without notice. If this command fails 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 lifesciences operations describe + access allowlist. diff --git a/gcloud/alpha/lifesciences/operations/cancel b/gcloud/alpha/number-registry/operations/delete similarity index 70% rename from gcloud/alpha/lifesciences/operations/cancel rename to gcloud/alpha/number-registry/operations/delete index e9ab6955e..050546ce2 100644 --- a/gcloud/alpha/lifesciences/operations/cancel +++ b/gcloud/alpha/number-registry/operations/delete @@ -1,21 +1,20 @@ NAME - gcloud alpha lifesciences operations cancel - cancel a Cloud Life Sciences - operation + gcloud alpha number-registry operations delete - delete operations SYNOPSIS - gcloud alpha lifesciences operations cancel + gcloud alpha number-registry operations delete (OPERATION : --location=LOCATION) [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) Cancel a Cloud Life Sciences operation. + (ALPHA) Delete an operation EXAMPLES - To cancel an operation called my-operation, run: + To delete the operation, run: - $ gcloud alpha lifesciences operations cancel my-operation + $ gcloud alpha number-registry operations delete POSITIONAL ARGUMENTS - Operation resource - Cloud Life Sciences operation to cancel. The + Operation resource - The name of the operation resource to be deleted. 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. @@ -38,13 +37,12 @@ POSITIONAL ARGUMENTS arguments in this group are specified. --location=LOCATION - Google Cloud location. + The location id of the operation resource. 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; - ▸ set the property lifesciences/location. + ▸ provide the argument --location on the command line. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, @@ -55,14 +53,13 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. API REFERENCE - This command uses the lifesciences/v2beta API. The full documentation for - this API can be found at: https://cloud.google.com/life-sciences + This command uses the cloudnumberregistry/v1alpha API. The full + documentation for this API can be found at: + https://docs.cloud.google.com/number-registry/reference/rest NOTES This command is currently in alpha and might change without notice. If this command fails 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 lifesciences operations cancel + access allowlist. diff --git a/gcloud/beta/lifesciences/operations/describe b/gcloud/alpha/number-registry/operations/describe similarity index 56% rename from gcloud/beta/lifesciences/operations/describe rename to gcloud/alpha/number-registry/operations/describe index 66d0c756e..697c695cf 100644 --- a/gcloud/beta/lifesciences/operations/describe +++ b/gcloud/alpha/number-registry/operations/describe @@ -1,24 +1,23 @@ NAME - gcloud beta lifesciences operations describe - describe a Cloud Life - Sciences operation + gcloud alpha number-registry operations describe - describe operations SYNOPSIS - gcloud beta lifesciences operations describe + gcloud alpha number-registry operations describe (OPERATION : --location=LOCATION) [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) Describe a Cloud Life Sciences operation. + (ALPHA) Describe an operation EXAMPLES - To describe an operation called my-operation, run: + To describe the operation, run: - $ gcloud beta lifesciences operations describe my-operation + $ gcloud alpha number-registry operations describe POSITIONAL ARGUMENTS - Operation resource - Cloud Life Sciences 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. + Operation resource - The name of the operation 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 operation on the command line with a fully @@ -38,13 +37,12 @@ POSITIONAL ARGUMENTS arguments in this group are specified. --location=LOCATION - Google Cloud location. + The location id of the operation resource. 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; - ▸ set the property lifesciences/location. + ▸ provide the argument --location on the command line. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, @@ -55,12 +53,13 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. API REFERENCE - This command uses the lifesciences/v2beta API. The full documentation for - this API can be found at: https://cloud.google.com/life-sciences + This command uses the cloudnumberregistry/v1alpha API. The full + documentation for this API can be found at: + https://docs.cloud.google.com/number-registry/reference/rest NOTES - This command is currently in beta and might change without notice. This - variant is also available: - - $ gcloud alpha lifesciences operations describe + This command is currently in alpha and might change without notice. If this + command fails 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/number-registry/operations/help b/gcloud/alpha/number-registry/operations/help new file mode 100644 index 000000000..8a5ebe8dd --- /dev/null +++ b/gcloud/alpha/number-registry/operations/help @@ -0,0 +1,38 @@ +NAME + gcloud alpha number-registry operations - manage Operation resources + +SYNOPSIS + gcloud alpha number-registry operations COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Manage Operation resources. + +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 operations. + + delete + (ALPHA) Delete operations. + + describe + (ALPHA) Describe operations. + + list + (ALPHA) List operations. + + wait + (ALPHA) Wait operations. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/lifesciences/operations/list b/gcloud/alpha/number-registry/operations/list similarity index 71% rename from gcloud/alpha/lifesciences/operations/list rename to gcloud/alpha/number-registry/operations/list index 28935f02b..006ce8993 100644 --- a/gcloud/alpha/lifesciences/operations/list +++ b/gcloud/alpha/number-registry/operations/list @@ -1,38 +1,37 @@ NAME - gcloud alpha lifesciences operations list - list Cloud Life Sciences - operations + gcloud alpha number-registry operations list - list operations SYNOPSIS - gcloud alpha lifesciences operations list [--location=LOCATION] + gcloud alpha number-registry operations list --location=LOCATION [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) List Cloud Life Sciences operations. + (ALPHA) List operations EXAMPLES To list all operations, run: - $ gcloud alpha lifesciences operations list + $ gcloud alpha number-registry operations list -FLAGS - Location resource - Cloud Life Sciences Location of the Operations to - list. This represents a Cloud resource. (NOTE) Some attributes are not - given arguments in this group but can be set in other ways. +REQUIRED FLAGS + Location resource - The name of the operation's parent resource. 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 lifesciences/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. + This must be specified. - To set the location attribute: - ◆ provide the argument --location on the command line; - ◆ set the property lifesciences/location. + --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 @@ -75,14 +74,13 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. API REFERENCE - This command uses the lifesciences/v2beta API. The full documentation for - this API can be found at: https://cloud.google.com/life-sciences + This command uses the cloudnumberregistry/v1alpha API. The full + documentation for this API can be found at: + https://docs.cloud.google.com/number-registry/reference/rest NOTES This command is currently in alpha and might change without notice. If this command fails 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 lifesciences operations list + access allowlist. diff --git a/gcloud/alpha/lifesciences/operations/wait b/gcloud/alpha/number-registry/operations/wait similarity index 71% rename from gcloud/alpha/lifesciences/operations/wait rename to gcloud/alpha/number-registry/operations/wait index b0673e55b..b0d138b2a 100644 --- a/gcloud/alpha/lifesciences/operations/wait +++ b/gcloud/alpha/number-registry/operations/wait @@ -1,18 +1,20 @@ NAME - gcloud alpha lifesciences operations wait - wait for Cloud Life Sciences - operation to complete + gcloud alpha number-registry operations wait - wait operations SYNOPSIS - gcloud alpha lifesciences operations wait (OPERATION : --location=LOCATION) - [GCLOUD_WIDE_FLAG ...] + gcloud alpha number-registry operations wait + (OPERATION : --location=LOCATION) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Wait an operation EXAMPLES - To wait for the completion of the operation called my-operation, run: + To wait the operation, run: - $ gcloud alpha lifesciences operations wait my-operation + $ gcloud alpha number-registry operations wait POSITIONAL ARGUMENTS - Operation resource - The Cloud Life Sciences operation to wait for. The + Operation resource - The name of the operation resource to wait on. 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. @@ -35,13 +37,12 @@ POSITIONAL ARGUMENTS arguments in this group are specified. --location=LOCATION - Google Cloud location. + The location id of the operation resource. 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; - ▸ set the property lifesciences/location. + ▸ provide the argument --location on the command line. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, @@ -51,11 +52,14 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. +API REFERENCE + This command uses the cloudnumberregistry/v1alpha API. The full + documentation for this API can be found at: + https://docs.cloud.google.com/number-registry/reference/rest + NOTES This command is currently in alpha and might change without notice. If this command fails 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 lifesciences operations wait + access allowlist. diff --git a/gcloud/alpha/number-registry/realms/create b/gcloud/alpha/number-registry/realms/create new file mode 100644 index 000000000..c94dba17f --- /dev/null +++ b/gcloud/alpha/number-registry/realms/create @@ -0,0 +1,154 @@ +NAME + gcloud alpha number-registry realms create - create a realm resource + +SYNOPSIS + gcloud alpha number-registry realms create REALM + --management-type=MANAGEMENT_TYPE --registry-book=REGISTRY_BOOK + --traffic-type=TRAFFIC_TYPE [--async] [--ip-version=IP_VERSION] + [--labels=[LABELS,...]] [--location=LOCATION] [--request-id=REQUEST_ID] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Create a realm resource. + +EXAMPLES + To create a realm my-realm run: + + $ gcloud alpha number-registry realms create my-realm \ + --location=global + +POSITIONAL ARGUMENTS + Realm resource - Identifier. Unique name/ID of the realm 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 realm 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 realm on the command line with a fully specified + name; + ◆ provide the argument --location on the command line. + + This must be specified. + + REALM + ID of the realm or fully qualified identifier for the realm. + + To set the realm attribute: + ▸ provide the argument realm on the command line. + +REQUIRED FLAGS + --management-type=MANAGEMENT_TYPE + Management type of realm. MANAGEMENT_TYPE must be one of: + + cnr + Managed by Cloud Number Registry. + user + Managed by User. + + RegistryBook resource - URI of the registry book that claims the realm. + 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 --registry-book 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 --registry-book on the command line with a fully + specified name; + ◆ provide the argument --location on the command line. + + This must be specified. + + --registry-book=REGISTRY_BOOK + ID of the registryBook or fully qualified identifier for the + registryBook. + + To set the registry-book attribute: + ▸ provide the argument --registry-book on the command line. + + --traffic-type=TRAFFIC_TYPE + Traffic type of realm. TRAFFIC_TYPE must be one of: + + internet + Internet traffic. + linklocal + Linklocal traffic. + private + Private traffic. + unset + Unset traffic type. + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --ip-version=IP_VERSION + IP version of the realm. IP_VERSION must be one of: + + ipv4 + IPv4 IP version. + ipv6 + IPv6 IP version. + + --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) + + --location=LOCATION + For resources [realm, registry-book], provides fallback value for + resource location attribute. When the resource's full URI path is not + provided, location will fallback to this flag value. + + --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. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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 cloudnumberregistry/v1alpha API. The full + documentation for this API can be found at: + https://docs.cloud.google.com/number-registry/reference/rest + +NOTES + This command is currently in alpha and might change without notice. If this + command fails 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/number-registry/realms/delete b/gcloud/alpha/number-registry/realms/delete new file mode 100644 index 000000000..06040106b --- /dev/null +++ b/gcloud/alpha/number-registry/realms/delete @@ -0,0 +1,79 @@ +NAME + gcloud alpha number-registry realms delete - delete a single realm resource + +SYNOPSIS + gcloud alpha number-registry realms delete (REALM : --location=LOCATION) + [--async] [--force] [--request-id=REQUEST_ID] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Deletes a single realm. + +EXAMPLES + To delete a realm my-realm run: + + $ gcloud alpha number-registry realms delete my-realm \ + --location=global + +POSITIONAL ARGUMENTS + Realm 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 realm 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. + + REALM + ID of the realm or fully qualified identifier for the realm. + + To set the realm attribute: + ▸ provide the argument realm 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 realm resource. + + To set the location attribute: + ▸ provide the argument realm 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. + + --force + If set to true, all associated resources will be deleted. + + --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. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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 cloudnumberregistry/v1alpha API. The full + documentation for this API can be found at: + https://docs.cloud.google.com/number-registry/reference/rest + +NOTES + This command is currently in alpha and might change without notice. If this + command fails 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/number-registry/realms/describe b/gcloud/alpha/number-registry/realms/describe new file mode 100644 index 000000000..d11b6d403 --- /dev/null +++ b/gcloud/alpha/number-registry/realms/describe @@ -0,0 +1,66 @@ +NAME + gcloud alpha number-registry realms describe - gets details of a single + realm resource + +SYNOPSIS + gcloud alpha number-registry realms describe (REALM : --location=LOCATION) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Gets details of a single realm resource. + +EXAMPLES + To get the details of a single realm my-realm run: + + $ gcloud alpha number-registry realms describe my-realm \ + --location=global + +POSITIONAL ARGUMENTS + Realm 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 realm 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. + + REALM + ID of the realm or fully qualified identifier for the realm. + + To set the realm attribute: + ▸ provide the argument realm 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 realm resource. + + To set the location attribute: + ▸ provide the argument realm 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 cloudnumberregistry/v1alpha API. The full + documentation for this API can be found at: + https://docs.cloud.google.com/number-registry/reference/rest + +NOTES + This command is currently in alpha and might change without notice. If this + command fails 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/number-registry/realms/help b/gcloud/alpha/number-registry/realms/help new file mode 100644 index 000000000..1f2b6742e --- /dev/null +++ b/gcloud/alpha/number-registry/realms/help @@ -0,0 +1,39 @@ +NAME + gcloud alpha number-registry realms - manage discovered and custom realm + resources + +SYNOPSIS + gcloud alpha number-registry realms COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Manage discovered and custom realm 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 + (ALPHA) Create a realm resource. + + delete + (ALPHA) Delete a single realm resource. + + describe + (ALPHA) Gets details of a single realm resource. + + list + (ALPHA) List realm resources. + + update + (ALPHA) Update the parameters of a single realm resource. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/number-registry/realms/list b/gcloud/alpha/number-registry/realms/list new file mode 100644 index 000000000..47beb7522 --- /dev/null +++ b/gcloud/alpha/number-registry/realms/list @@ -0,0 +1,86 @@ +NAME + gcloud alpha number-registry realms list - list realm resources + +SYNOPSIS + gcloud alpha number-registry realms list --location=LOCATION + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) List realm resources. + +EXAMPLES + To list all realms run: + + $ gcloud alpha number-registry realms list --location=global + +REQUIRED FLAGS + Location resource - Parent value for ListRealmsRequest 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 cloudnumberregistry/v1alpha API. The full + documentation for this API can be found at: + https://docs.cloud.google.com/number-registry/reference/rest + +NOTES + This command is currently in alpha and might change without notice. If this + command fails 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/number-registry/realms/update b/gcloud/alpha/number-registry/realms/update new file mode 100644 index 000000000..c1024ab25 --- /dev/null +++ b/gcloud/alpha/number-registry/realms/update @@ -0,0 +1,205 @@ +NAME + gcloud alpha number-registry realms update - update the parameters of a + single realm resource + +SYNOPSIS + gcloud alpha number-registry realms update REALM [--async] + [--ip-version=IP_VERSION] [--location=LOCATION] + [--management-type=MANAGEMENT_TYPE] [--registry-book=REGISTRY_BOOK] + [--request-id=REQUEST_ID] [--traffic-type=TRAFFIC_TYPE] + [--labels=[LABELS,...] + | --update-labels=[UPDATE_LABELS,...] --clear-labels + | --remove-labels=REMOVE_LABELS] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Update a realm resource. + +EXAMPLES + To update the labels of a realm my-realm run: + + $ gcloud alpha number-registry realms update my-realm \ + --location=global --update-labels=key=value + +POSITIONAL ARGUMENTS + Realm resource - Identifier. Unique name/ID of the realm 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 realm 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 realm on the command line with a fully specified + name; + ◆ provide the argument --location on the command line. + + This must be specified. + + REALM + ID of the realm or fully qualified identifier for the realm. + + To set the realm attribute: + ▸ provide the argument realm on the command line. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --ip-version=IP_VERSION + IP version of the realm. IP_VERSION must be one of: + + ipv4 + IPv4 IP version. + ipv6 + IPv6 IP version. + + --location=LOCATION + For resources [realm, registry-book], provides fallback value for + resource location attribute. When the resource's full URI path is not + provided, location will fallback to this flag value. + + --management-type=MANAGEMENT_TYPE + Management type of realm. MANAGEMENT_TYPE must be one of: + + cnr + Managed by Cloud Number Registry. + user + Managed by User. + + RegistryBook resource - URI of the registry book that claims the realm. + 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 --registry-book 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 --registry-book on the command line with a fully + specified name; + ◆ provide the argument --location on the command line. + + --registry-book=REGISTRY_BOOK + ID of the registryBook or fully qualified identifier for the + registryBook. + + To set the registry-book attribute: + ◆ provide the argument --registry-book on the command line. + + --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. + + --traffic-type=TRAFFIC_TYPE + Traffic type of realm. TRAFFIC_TYPE must be one of: + + internet + Internet traffic. + linklocal + Linklocal traffic. + private + Private traffic. + unset + Unset traffic type. + + 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) + + Or at least one of these can be specified: + + --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. Sets remove_labels value. + + Shorthand Example: + + --remove-labels=string,string + + JSON Example: + + --remove-labels=["string"] + + File Example: + + --remove-labels=path_to_file.(yaml|json) + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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 cloudnumberregistry/v1alpha API. The full + documentation for this API can be found at: + https://docs.cloud.google.com/number-registry/reference/rest + +NOTES + This command is currently in alpha and might change without notice. If this + command fails 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/number-registry/registry-books/create b/gcloud/alpha/number-registry/registry-books/create new file mode 100644 index 000000000..4f77d4029 --- /dev/null +++ b/gcloud/alpha/number-registry/registry-books/create @@ -0,0 +1,118 @@ +NAME + gcloud alpha number-registry registry-books create - create a registry book + resource + +SYNOPSIS + gcloud alpha number-registry registry-books create + (REGISTRY_BOOK : --location=LOCATION) [--async] + [--claimed-scopes=[CLAIMED_SCOPES,...]] [--labels=[LABELS,...]] + [--request-id=REQUEST_ID] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Create a registry book resource. + +EXAMPLES + To create an registry book my-registry-book run: + + $ gcloud alpha number-registry registry-books create \ + my-registry-book --location=global + +POSITIONAL ARGUMENTS + RegistryBook resource - Identifier. name of 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 registry_book 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. + + REGISTRY_BOOK + ID of the registryBook or fully qualified identifier for the + registryBook. + + To set the registry_book attribute: + ▸ provide the argument registry_book 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 registryBook resource. + + To set the location attribute: + ▸ provide the argument registry_book 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. + + --claimed-scopes=[CLAIMED_SCOPES,...] + List of scopes claimed by the RegistryBook. In Preview, Only project + scope is supported. Each scope is in the format of projects/{project}. + Each scope can only be claimed once. + + --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 cloudnumberregistry/v1alpha API. The full + documentation for this API can be found at: + https://docs.cloud.google.com/number-registry/reference/rest + +NOTES + This command is currently in alpha and might change without notice. If this + command fails 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/number-registry/registry-books/delete b/gcloud/alpha/number-registry/registry-books/delete new file mode 100644 index 000000000..c3a01abc3 --- /dev/null +++ b/gcloud/alpha/number-registry/registry-books/delete @@ -0,0 +1,92 @@ +NAME + gcloud alpha number-registry registry-books delete - delete a single + registry book resource + +SYNOPSIS + gcloud alpha number-registry registry-books delete + (REGISTRY_BOOK : --location=LOCATION) [--async] [--force] + [--request-id=REQUEST_ID] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Deletes a single registry book. + +EXAMPLES + To delete a registry book my-registry-book run: + + $ gcloud alpha number-registry registry-books delete \ + my-registry-book --location=global + +POSITIONAL ARGUMENTS + RegistryBook 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 registry_book 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. + + REGISTRY_BOOK + ID of the registryBook or fully qualified identifier for the + registryBook. + + To set the registry_book attribute: + ▸ provide the argument registry_book 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 registryBook resource. + + To set the location attribute: + ▸ provide the argument registry_book 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. + + --force + If set to true, all associated resources will be deleted. + + --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 cloudnumberregistry/v1alpha API. The full + documentation for this API can be found at: + https://docs.cloud.google.com/number-registry/reference/rest + +NOTES + This command is currently in alpha and might change without notice. If this + command fails 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/number-registry/registry-books/describe b/gcloud/alpha/number-registry/registry-books/describe new file mode 100644 index 000000000..181cf43d1 --- /dev/null +++ b/gcloud/alpha/number-registry/registry-books/describe @@ -0,0 +1,81 @@ +NAME + gcloud alpha number-registry registry-books describe - gets details of a + single registry book resource + +SYNOPSIS + gcloud alpha number-registry registry-books describe + (REGISTRY_BOOK : --location=LOCATION) [--view=VIEW] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Gets details of a single registry book resource. + +EXAMPLES + To get the details of a single registry book my-registry-book run: + + $ gcloud alpha number-registry registry-books describe \ + my-registry-book --location=global + +POSITIONAL ARGUMENTS + RegistryBook 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 registry_book 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. + + REGISTRY_BOOK + ID of the registryBook or fully qualified identifier for the + registryBook. + + To set the registry_book attribute: + ▸ provide the argument registry_book 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 registryBook resource. + + To set the location attribute: + ▸ provide the argument registry_book on the command line with a + fully specified name; + ▸ provide the argument --location on the command line. + +FLAGS + --view=VIEW + The view of the RegistryBook. VIEW must be one of: + + aggregate + Aggregate includes data about the child resources of the + RegistryBook. + basic + Basic view. + full + Full view. Includes the same data as the BASIC view. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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 cloudnumberregistry/v1alpha API. The full + documentation for this API can be found at: + https://docs.cloud.google.com/number-registry/reference/rest + +NOTES + This command is currently in alpha and might change without notice. If this + command fails 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/number-registry/registry-books/help b/gcloud/alpha/number-registry/registry-books/help new file mode 100644 index 000000000..4d1e1b51a --- /dev/null +++ b/gcloud/alpha/number-registry/registry-books/help @@ -0,0 +1,42 @@ +NAME + gcloud alpha number-registry registry-books - manage registry book + resources + +SYNOPSIS + gcloud alpha number-registry registry-books COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Manage registry book 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 + (ALPHA) Create a registry book resource. + + delete + (ALPHA) Delete a single registry book resource. + + describe + (ALPHA) Gets details of a single registry book resource. + + list + (ALPHA) List registry book resources. + + search-ip-resources + (ALPHA) Search IP resources in a registry book. + + update + (ALPHA) Update the parameters of a single registry book resource. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/number-registry/registry-books/list b/gcloud/alpha/number-registry/registry-books/list new file mode 100644 index 000000000..bcb33c5b1 --- /dev/null +++ b/gcloud/alpha/number-registry/registry-books/list @@ -0,0 +1,100 @@ +NAME + gcloud alpha number-registry registry-books list - list registry book + resources + +SYNOPSIS + gcloud alpha number-registry registry-books list --location=LOCATION + [--view=VIEW] [--filter=EXPRESSION] [--limit=LIMIT] + [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) List registry book resources. + +EXAMPLES + To list all registry books run: + + $ gcloud alpha number-registry registry-books list --location=global + +REQUIRED FLAGS + Location resource - Parent value for ListRegistryBooksRequest 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. + +FLAGS + --view=VIEW + The view of the RegistryBook. VIEW must be one of: + + aggregate + Aggregate includes data about the child resources of the + RegistryBook. + basic + Basic view. + full + Full view. Includes the same data as the BASIC view. + +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 cloudnumberregistry/v1alpha API. The full + documentation for this API can be found at: + https://docs.cloud.google.com/number-registry/reference/rest + +NOTES + This command is currently in alpha and might change without notice. If this + command fails 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/number-registry/registry-books/search-ip-resources b/gcloud/alpha/number-registry/registry-books/search-ip-resources new file mode 100644 index 000000000..d3c4304e2 --- /dev/null +++ b/gcloud/alpha/number-registry/registry-books/search-ip-resources @@ -0,0 +1,115 @@ +NAME + gcloud alpha number-registry registry-books search-ip-resources - search IP + resources in a registry book + +SYNOPSIS + gcloud alpha number-registry registry-books search-ip-resources + (REGISTRY_BOOK : --location=LOCATION) [--query=QUERY] + [--show-utilization] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Search IP resources in a registry book using IP address, IP + version, attributes, etc. + +EXAMPLES + To search for an ip address across ranges in a registry book run: + + $ gcloud alpha number-registry registry-books search-ip-resources \ + my-registry-book --location=global \ + --query="ip_address=10.0.0.1 AND ip_version=IPV4" + + To search for a range in a registry book with text in its attributes run: + + $ gcloud alpha number-registry registry-books search-ip-resources \ + my-registry-book --location=global --query="attribute_text=foo" + + To search for a range in a registry book with exact text in its attributes + run: + + $ gcloud alpha number-registry registry-books search-ip-resources \ + my-registry-book --location=global --query="attribute:(foo=bar)" + + To additionally show the utilization of a range in a registry book run: + + $ gcloud alpha number-registry registry-books search-ip-resources \ + my-registry-book --location=global \ + --query="ip_address=10.0.0.1 AND ip_version=IPV4" \ + --show-utilization + +POSITIONAL ARGUMENTS + RegistryBook resource - The name of the RegistryBook to search in. 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 registry_book 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. + + REGISTRY_BOOK + ID of the registryBook or fully qualified identifier for the + registryBook. + + To set the registry_book attribute: + ▸ provide the argument registry_book 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 registryBook resource. + + To set the location attribute: + ▸ provide the argument registry_book on the command line with a + fully specified name; + ▸ provide the argument --location on the command line. + +FLAGS + --query=QUERY + Search query. This string filters resources in an AIP-160-like format. + It has some limitations. You can only specify top level conjunctions or + attribute level negations. Each restriction can only be used once + except the attribute restriction. The available restrictions are: + ◆ realm: The realm name to search in. + ◆ ip_address: The IP address to search for within ranges. + ◆ ip_version: The IP version to filter by (e.g., "IPV4", "IPV6"). + ◆ attribute_text: The attribute text to search for within ranges. + ◆ attribute: The attribute key and value to filter by. + + Only one of attribute_text or multiple attribute filters can be + specified. Examples: + ◆ realm=test-realm + ◆ realm=test-realm AND ip_address=10.0.0.0 + ◆ realm=test-realm AND ip_version=IPV6 + ◆ realm=test-realm AND attribute_text=test + ◆ ip_address=10.0.0.0 AND attribute:(key1=value1) AND + attribute:(key2=value2) + ◆ attribute_text=test AND + parent_range=projects/123/locations/global/discoveredRanges/test-parent-range + + --show-utilization + Whether to show the utilization of the ranges in the response. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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 cloudnumberregistry/v1alpha API. The full + documentation for this API can be found at: + https://docs.cloud.google.com/number-registry/reference/rest + +NOTES + This command is currently in alpha and might change without notice. If this + command fails 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/number-registry/registry-books/update b/gcloud/alpha/number-registry/registry-books/update new file mode 100644 index 000000000..29dd5ca6b --- /dev/null +++ b/gcloud/alpha/number-registry/registry-books/update @@ -0,0 +1,191 @@ +NAME + gcloud alpha number-registry registry-books update - update the parameters + of a single registry book resource + +SYNOPSIS + gcloud alpha number-registry registry-books update + (REGISTRY_BOOK : --location=LOCATION) [--async] + [--request-id=REQUEST_ID] + [--claimed-scopes=[CLAIMED_SCOPES,...] + | --add-claimed-scopes=[ADD_CLAIMED_SCOPES,...] + --clear-claimed-scopes + | --remove-claimed-scopes=[REMOVE_CLAIMED_SCOPES,...]] + [--labels=[LABELS,...] + | --update-labels=[UPDATE_LABELS,...] --clear-labels + | --remove-labels=REMOVE_LABELS] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Update a registry book resource. + +EXAMPLES + To update the name of a registry book my-registry-book run: + + $ gcloud alpha number-registry registry-books update \ + my-registry-book --location=global \ + --name="updated-registry-book" + +POSITIONAL ARGUMENTS + RegistryBook resource - Identifier. name of 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 registry_book 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. + + REGISTRY_BOOK + ID of the registryBook or fully qualified identifier for the + registryBook. + + To set the registry_book attribute: + ▸ provide the argument registry_book 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 registryBook resource. + + To set the location attribute: + ▸ provide the argument registry_book 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 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 claimed_scopes. + + At most one of these can be specified: + + --claimed-scopes=[CLAIMED_SCOPES,...] + Set claimed_scopes to new value. + + Or at least one of these can be specified: + + --add-claimed-scopes=[ADD_CLAIMED_SCOPES,...] + Add new value to claimed_scopes list. + + At most one of these can be specified: + + --clear-claimed-scopes + Clear claimed_scopes value and set to empty list. + + --remove-claimed-scopes=[REMOVE_CLAIMED_SCOPES,...] + Remove existing value from claimed_scopes list. + + 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) + + Or at least one of these can be specified: + + --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. Sets remove_labels value. + + Shorthand Example: + + --remove-labels=string,string + + JSON Example: + + --remove-labels=["string"] + + File Example: + + --remove-labels=path_to_file.(yaml|json) + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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 cloudnumberregistry/v1alpha API. The full + documentation for this API can be found at: + https://docs.cloud.google.com/number-registry/reference/rest + +NOTES + This command is currently in alpha and might change without notice. If this + command fails 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/pam/grants/create b/gcloud/alpha/pam/grants/create index 2fd85d85b..40d055077 100644 --- a/gcloud/alpha/pam/grants/create +++ b/gcloud/alpha/pam/grants/create @@ -8,6 +8,7 @@ SYNOPSIS : --folder=FOLDER --location=LOCATION --organization=ORGANIZATION) [--additional-email-recipients=[ADDITIONAL_EMAIL_RECIPIENTS,...]] [--justification=JUSTIFICATION] + [--scheduled-activation-time=SCHEDULED_ACTIVATION_TIME] [--requested-access-from-file=[REQUESTED_ACCESS_FROM_FILE,...] | --requested-resources=[REQUESTED_RESOURCES,...]] [GCLOUD_WIDE_FLAG ...] @@ -94,6 +95,11 @@ OPTIONAL FLAGS --justification=JUSTIFICATION Justification for the grant. + --scheduled-activation-time=SCHEDULED_ACTIVATION_TIME + To schedule the grant, specify a start date and time up to 7 days in + the future. If not scheduled, the grant activates immediately upon + creation or approval(s). + Specify the grant's scope using either high-level resource or a fine-grained scope configuration. diff --git a/gcloud/alpha/redis/clusters/create b/gcloud/alpha/redis/clusters/create index e0c6289d6..2fc550fcb 100644 --- a/gcloud/alpha/redis/clusters/create +++ b/gcloud/alpha/redis/clusters/create @@ -184,7 +184,8 @@ FLAGS --node-type=NODE_TYPE Node Type of the redis cluster Node. NODE_TYPE must be one of: - redis-highmem-medium, redis-highmem-xlarge, redis-shared-core-nano, + redis-highcpu-medium, redis-highmem-2xlarge, redis-highmem-medium, + redis-highmem-xlarge, redis-shared-core-nano, redis-standard-large, redis-standard-small. --persistence-mode=PERSISTENCE_MODE diff --git a/gcloud/alpha/redis/clusters/create-token-auth-user b/gcloud/alpha/redis/clusters/create-token-auth-user new file mode 100644 index 000000000..6eb5df600 --- /dev/null +++ b/gcloud/alpha/redis/clusters/create-token-auth-user @@ -0,0 +1,75 @@ +NAME + gcloud alpha redis clusters create-token-auth-user - create a token auth + user for a Redis cluster + +SYNOPSIS + gcloud alpha redis clusters create-token-auth-user + (CLUSTER : --region=REGION) [--async] + [--token-auth-user=TOKEN_AUTH_USER] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Create a token-auth user for a token-auth-enabled Redis cluster. An + initial token will be generated for the user. The username and token can be + used to authenticate a client connecting to the cluster. + +POSITIONAL ARGUMENTS + Cluster resource - Arguments and flags that specify the Memorystore Redis + cluster to create a backup for. The arguments in this group can be used to + specify the attributes of this resource. (NOTE) Some attributes are not + given arguments in this group but can be set in other ways. + + To set the project attribute: + ◆ provide the argument cluster on the command line with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + CLUSTER + ID of the cluster or fully qualified identifier for the cluster. + + To set the cluster attribute: + ▸ provide the argument cluster on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --region=REGION + The name of the Redis region of the cluster. Overrides the default + redis/region property value for this command invocation. + + To set the region attribute: + ▸ provide the argument cluster on the command line with a fully + specified name; + ▸ provide the argument --region on the command line; + ▸ set the property redis/region. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --token-auth-user=TOKEN_AUTH_USER + The name of the token auth user to be created. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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 redis/v1alpha1 API. The full documentation for this + API can be found at: https://cloud.google.com/memorystore/docs/redis/ + +NOTES + This command is currently in alpha and might change without notice. If this + command fails 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 redis clusters create-token-auth-user + diff --git a/gcloud/alpha/redis/clusters/help b/gcloud/alpha/redis/clusters/help index 1bd0144fe..83b3955db 100644 --- a/gcloud/alpha/redis/clusters/help +++ b/gcloud/alpha/redis/clusters/help @@ -23,6 +23,10 @@ GROUPS backups (ALPHA) Manage backups of Memorystore for Redis Cluster instances. + token-auth-users + (ALPHA) Manage token auth users of Memorystore for Redis Cluster + instances. + COMMANDS COMMAND is one of the following: @@ -35,6 +39,9 @@ COMMANDS create-backup (ALPHA) Create a backup of a Redis cluster. + create-token-auth-user + (ALPHA) Create a token auth user for a Redis cluster. + delete (ALPHA) Delete a Memorystore for Redis Cluster instance. diff --git a/gcloud/alpha/redis/clusters/token-auth-users/auth-tokens/delete b/gcloud/alpha/redis/clusters/token-auth-users/auth-tokens/delete new file mode 100644 index 000000000..d2a965b67 --- /dev/null +++ b/gcloud/alpha/redis/clusters/token-auth-users/auth-tokens/delete @@ -0,0 +1,101 @@ +NAME + gcloud alpha redis clusters token-auth-users auth-tokens delete - delete a + Memorystore for Redis Cluster auth token + +SYNOPSIS + gcloud alpha redis clusters token-auth-users auth-tokens delete + (AUTH_TOKEN : --cluster=CLUSTER + --region=REGION --token-auth-user=TOKEN_AUTH_USER) [--async] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Delete a Memorystore for Redis Cluster auth token. + + This command can fail for the following reasons: + ▪ The auth token specified does not exist. + ▪ The active account does not have permission to access the given auth + token. + +EXAMPLES + To delete an auth token with the name my-auth-token of token auth user + my-token-auth-user under cluster my-cluster in us-central1 region, run: + + $ gcloud alpha redis clusters token-auth-users auth-tokens delete \ + my-auth-token --token-auth-user=my-token-auth-user \ + --cluster=my-cluster --region=us-central1 + +POSITIONAL ARGUMENTS + Auth token resource - Arguments and flags that specify the Redis auth + token you want to delete. The arguments in this group can be used to + specify the attributes of this resource. (NOTE) Some attributes are not + given arguments in this group but can be set in other ways. + + To set the project attribute: + ◆ provide the argument auth_token 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. + + AUTH_TOKEN + ID of the auth token or fully qualified identifier for the auth + token. + + To set the auth_token attribute: + ▸ provide the argument auth_token on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --cluster=CLUSTER + The name of the Redis cluster. + + To set the cluster attribute: + ▸ provide the argument auth_token on the command line with a fully + specified name; + ▸ provide the argument --cluster on the command line. + + --region=REGION + The name of the Redis region of the auth token. Overrides the default + redis/region property value for this command invocation. + + To set the region attribute: + ▸ provide the argument auth_token on the command line with a fully + specified name; + ▸ provide the argument --region on the command line; + ▸ set the property redis/region. + + --token-auth-user=TOKEN_AUTH_USER + The name of the Redis cluster token auth user. + + To set the token-auth-user attribute: + ▸ provide the argument auth_token on the command line with a fully + specified name; + ▸ provide the argument --token-auth-user 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 redis/v1alpha1 API. The full documentation for this + API can be found at: https://cloud.google.com/memorystore/docs/redis/ + +NOTES + This command is currently in alpha and might change without notice. If this + command fails 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 redis clusters token-auth-users auth-tokens delete + diff --git a/gcloud/alpha/redis/clusters/token-auth-users/auth-tokens/describe b/gcloud/alpha/redis/clusters/token-auth-users/auth-tokens/describe new file mode 100644 index 000000000..ad0504e56 --- /dev/null +++ b/gcloud/alpha/redis/clusters/token-auth-users/auth-tokens/describe @@ -0,0 +1,98 @@ +NAME + gcloud alpha redis clusters token-auth-users auth-tokens describe - show + metadata for a Memorystore for Redis Cluster auth token + +SYNOPSIS + gcloud alpha redis clusters token-auth-users auth-tokens describe + (AUTH_TOKEN : --cluster=CLUSTER + --region=REGION --token-auth-user=TOKEN_AUTH_USER) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Show metadata for a Memorystore for Redis Cluster auth token. + + Displays all metadata associated with an auth token given a valid auth + token name. + + This command can fail for the following reasons: + ▪ The auth token specified does not exist. + ▪ The active account does not have permission to access the given auth + token. + +EXAMPLES + To display metadata for an auth token named my-auth-token for the user + my-token-auth-user in the my-cluster cluster in us-central1 region, run: + + $ gcloud alpha redis clusters token-auth-users auth-tokens \ describe my-auth-token --cluster=my-cluster \ + --token-auth-user=my-token-auth-user --region=us-central1 + +POSITIONAL ARGUMENTS + Auth token resource - The name of the Redis cluster auth token you want to + describe. The arguments in this group can be used to specify the + attributes of this resource. (NOTE) Some attributes are not given + arguments in this group but can be set in other ways. + + To set the project attribute: + ◆ provide the argument auth_token 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. + + AUTH_TOKEN + ID of the auth token or fully qualified identifier for the auth + token. + + To set the auth_token attribute: + ▸ provide the argument auth_token on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --cluster=CLUSTER + The name of the Redis cluster. + + To set the cluster attribute: + ▸ provide the argument auth_token on the command line with a fully + specified name; + ▸ provide the argument --cluster on the command line. + + --region=REGION + The name of the Redis region of the auth token. Overrides the default + redis/region property value for this command invocation. + + To set the region attribute: + ▸ provide the argument auth_token on the command line with a fully + specified name; + ▸ provide the argument --region on the command line; + ▸ set the property redis/region. + + --token-auth-user=TOKEN_AUTH_USER + The name of the Redis cluster token auth user. + + To set the token-auth-user attribute: + ▸ provide the argument auth_token on the command line with a fully + specified name; + ▸ provide the argument --token-auth-user 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 redis/v1alpha1 API. The full documentation for this + API can be found at: https://cloud.google.com/memorystore/docs/redis/ + +NOTES + This command is currently in alpha and might change without notice. If this + command fails 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 redis clusters token-auth-users auth-tokens describe + diff --git a/gcloud/alpha/redis/clusters/token-auth-users/auth-tokens/help b/gcloud/alpha/redis/clusters/token-auth-users/auth-tokens/help new file mode 100644 index 000000000..3a7e5914f --- /dev/null +++ b/gcloud/alpha/redis/clusters/token-auth-users/auth-tokens/help @@ -0,0 +1,36 @@ +NAME + gcloud alpha redis clusters token-auth-users auth-tokens - manage auth + tokens of Memorystore for Redis Cluster instances + +SYNOPSIS + gcloud alpha redis clusters token-auth-users auth-tokens COMMAND + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Manage auth tokens of Memorystore for Redis Cluster instances. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + delete + (ALPHA) Delete a Memorystore for Redis Cluster auth token. + + describe + (ALPHA) Show metadata for a Memorystore for Redis Cluster auth token. + + list + (ALPHA) List auth tokens for a token auth user. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails 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 redis clusters token-auth-users auth-tokens + diff --git a/gcloud/alpha/redis/clusters/token-auth-users/auth-tokens/list b/gcloud/alpha/redis/clusters/token-auth-users/auth-tokens/list new file mode 100644 index 000000000..c562bd112 --- /dev/null +++ b/gcloud/alpha/redis/clusters/token-auth-users/auth-tokens/list @@ -0,0 +1,116 @@ +NAME + gcloud alpha redis clusters token-auth-users auth-tokens list - list auth + tokens for a token auth user + +SYNOPSIS + gcloud alpha redis clusters token-auth-users auth-tokens list + (--token-auth-user=TOKEN_AUTH_USER : --cluster=CLUSTER --region=REGION) + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) List auth tokens for a token auth user. + +EXAMPLES + To list up to 2 auth tokens for a token auth user named + 'my-token-auth-user' on a cluster named 'my-cluster' in the us-central1 + region, run: + + $ gcloud alpha redis clusters token-auth-users auth-tokens list \ + --cluster=my-cluster --token-auth-user=my-token-auth-user \ + --region=us-central1 --limit=2 + +REQUIRED FLAGS + Token auth user resource - The token auth user to whom the auth tokens + belong. 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 --token-auth-user 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. + + --token-auth-user=TOKEN_AUTH_USER + ID of the token auth user or fully qualified identifier for the token + auth user. + + To set the token-auth-user attribute: + ▸ provide the argument --token-auth-user on the command line. + + This flag argument must be specified if any of the other arguments in + this group are specified. + + --cluster=CLUSTER + The name of the Redis cluster. + + To set the cluster attribute: + ▸ provide the argument --token-auth-user on the command line with a + fully specified name; + ▸ provide the argument --cluster on the command line. + + --region=REGION + The name of the Redis region of the token auth user. Overrides the + default redis/region property value for this command invocation. + + To set the region attribute: + ▸ provide the argument --token-auth-user on the command line with a + fully specified name; + ▸ provide the argument --region on the command line; + ▸ set the property redis/region. + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + + --uri + Print a list of resource URIs instead of the default output, and change + the command output to a list of URIs. If this flag is used with + --format, the formatting is applied on this URI list. To display URIs + alongside other keys instead, use the uri() transform. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the redis/v1alpha1 API. The full documentation for this + API can be found at: https://cloud.google.com/memorystore/docs/redis/ + +NOTES + This command is currently in alpha and might change without notice. If this + command fails 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 redis clusters token-auth-users auth-tokens list + diff --git a/gcloud/alpha/redis/clusters/token-auth-users/create-auth-token b/gcloud/alpha/redis/clusters/token-auth-users/create-auth-token new file mode 100644 index 000000000..4fb1b2d51 --- /dev/null +++ b/gcloud/alpha/redis/clusters/token-auth-users/create-auth-token @@ -0,0 +1,81 @@ +NAME + gcloud alpha redis clusters token-auth-users create-auth-token - create an + auth token for a token auth user of a Redis cluster + +SYNOPSIS + gcloud alpha redis clusters token-auth-users create-auth-token + (USER : --cluster=CLUSTER --region=REGION) [--async] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Create an auth token for a token auth user of a token auth enabled + Redis cluster. + +POSITIONAL ARGUMENTS + Token auth user resource - Arguments and flags that specify the + Memorystore Redis token auth user to create an auth token for. The + arguments in this group can be used to specify the attributes of this + resource. (NOTE) Some attributes are not given arguments in this group but + can be set in other ways. + + To set the project attribute: + ◆ provide the argument user 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. + + USER + ID of the token auth user or fully qualified identifier for the token + auth user. + + To set the token-auth-user attribute: + ▸ provide the argument user on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --cluster=CLUSTER + The name of the Redis cluster. + + To set the cluster attribute: + ▸ provide the argument user on the command line with a fully + specified name; + ▸ provide the argument --cluster on the command line. + + --region=REGION + The name of the Redis region of the token auth user. Overrides the + default redis/region property value for this command invocation. + + To set the region attribute: + ▸ provide the argument user on the command line with a fully + specified name; + ▸ provide the argument --region on the command line; + ▸ set the property redis/region. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the redis/v1alpha1 API. The full documentation for this + API can be found at: https://cloud.google.com/memorystore/docs/redis/ + +NOTES + This command is currently in alpha and might change without notice. If this + command fails 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 redis clusters token-auth-users create-auth-token + diff --git a/gcloud/alpha/redis/clusters/token-auth-users/delete b/gcloud/alpha/redis/clusters/token-auth-users/delete new file mode 100644 index 000000000..da7e333ae --- /dev/null +++ b/gcloud/alpha/redis/clusters/token-auth-users/delete @@ -0,0 +1,95 @@ +NAME + gcloud alpha redis clusters token-auth-users delete - delete a Memorystore + for Redis Cluster token auth user + +SYNOPSIS + gcloud alpha redis clusters token-auth-users delete + (TOKEN_AUTH_USER : --cluster=CLUSTER --region=REGION) [--async] + [--no-force] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Delete a Memorystore for Redis Cluster token auth user. + + This command can fail for the following reasons: + ▪ The token auth user specified does not exist. + ▪ The active account does not have permission to access the given token + auth user. + +EXAMPLES + To delete a token auth user with the name my-token-auth-user for cluster + my-cluster in us-central1 region, run: + + $ gcloud alpha redis clusters token-auth-users delete \ + my-token-auth-user --cluster=my-cluster --region=us-central1 + +POSITIONAL ARGUMENTS + Token auth user resource - Arguments and flags that specify the Redis + token auth user you want to delete. The arguments in this group can be + used to specify the attributes of this resource. (NOTE) Some attributes + are not given arguments in this group but can be set in other ways. + + To set the project attribute: + ◆ provide the argument token_auth_user 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. + + TOKEN_AUTH_USER + ID of the token auth user or fully qualified identifier for the token + auth user. + + To set the token_auth_user attribute: + ▸ provide the argument token_auth_user on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --cluster=CLUSTER + The name of the Redis cluster. + + To set the cluster attribute: + ▸ provide the argument token_auth_user on the command line with a + fully specified name; + ▸ provide the argument --cluster on the command line. + + --region=REGION + The name of the Redis region of the token auth user. Overrides the + default redis/region property value for this command invocation. + + To set the region attribute: + ▸ provide the argument token_auth_user on the command line with a + fully specified name; + ▸ provide the argument --region on the command line; + ▸ set the property redis/region. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --force + If set to true, the token auth user and its nested resources will be + deleted. Enabled by default, use --no-force to disable. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the redis/v1alpha1 API. The full documentation for this + API can be found at: https://cloud.google.com/memorystore/docs/redis/ + +NOTES + This command is currently in alpha and might change without notice. If this + command fails 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 redis clusters token-auth-users delete + diff --git a/gcloud/alpha/redis/clusters/token-auth-users/describe b/gcloud/alpha/redis/clusters/token-auth-users/describe new file mode 100644 index 000000000..054cc2b50 --- /dev/null +++ b/gcloud/alpha/redis/clusters/token-auth-users/describe @@ -0,0 +1,89 @@ +NAME + gcloud alpha redis clusters token-auth-users describe - show metadata for a + Memorystore for Redis Cluster token auth user + +SYNOPSIS + gcloud alpha redis clusters token-auth-users describe + (TOKEN_AUTH_USER : --cluster=CLUSTER --region=REGION) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Show metadata for a Memorystore for Redis Cluster token auth user. + + Displays all metadata associated with a token auth user given a valid token + auth user name. + + This command can fail for the following reasons: + ▪ The token auth user specified does not exist. + ▪ The active account does not have permission to access the given token + auth user. + +EXAMPLES + To display the metadata for a token auth user named my-token-auth-user for + cluster my-cluster in us-central1 region, run: + + $ gcloud alpha redis clusters token-auth-users describe \ + my-token-auth-user --cluster=my-cluster --region=us-central1 + +POSITIONAL ARGUMENTS + Token auth user resource - The name of the Redis cluster token auth user + you want to describe. The arguments in this group can be used to specify + the attributes of this resource. (NOTE) Some attributes are not given + arguments in this group but can be set in other ways. + + To set the project attribute: + ◆ provide the argument token_auth_user 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. + + TOKEN_AUTH_USER + ID of the token auth user or fully qualified identifier for the token + auth user. + + To set the token_auth_user attribute: + ▸ provide the argument token_auth_user on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --cluster=CLUSTER + The name of the Redis cluster. + + To set the cluster attribute: + ▸ provide the argument token_auth_user on the command line with a + fully specified name; + ▸ provide the argument --cluster on the command line. + + --region=REGION + The name of the Redis region of the token auth user. Overrides the + default redis/region property value for this command invocation. + + To set the region attribute: + ▸ provide the argument token_auth_user on the command line with a + fully specified name; + ▸ provide the argument --region on the command line; + ▸ set the property redis/region. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the redis/v1alpha1 API. The full documentation for this + API can be found at: https://cloud.google.com/memorystore/docs/redis/ + +NOTES + This command is currently in alpha and might change without notice. If this + command fails 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 redis clusters token-auth-users describe + diff --git a/gcloud/alpha/redis/clusters/token-auth-users/help b/gcloud/alpha/redis/clusters/token-auth-users/help new file mode 100644 index 000000000..2b9772771 --- /dev/null +++ b/gcloud/alpha/redis/clusters/token-auth-users/help @@ -0,0 +1,46 @@ +NAME + gcloud alpha redis clusters token-auth-users - manage token auth users of + Memorystore for Redis Cluster instances + +SYNOPSIS + gcloud alpha redis clusters token-auth-users GROUP | COMMAND + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Manage token auth users of Memorystore for Redis Cluster instances. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +GROUPS + GROUP is one of the following: + + auth-tokens + (ALPHA) Manage auth tokens of Memorystore for Redis Cluster instances. + +COMMANDS + COMMAND is one of the following: + + create-auth-token + (ALPHA) Create an auth token for a token auth user of a Redis cluster. + + delete + (ALPHA) Delete a Memorystore for Redis Cluster token auth user. + + describe + (ALPHA) Show metadata for a Memorystore for Redis Cluster token auth + user. + + list + (ALPHA) List token auth users of a Redis cluster in a region. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails 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 redis clusters token-auth-users + diff --git a/gcloud/alpha/redis/clusters/token-auth-users/list b/gcloud/alpha/redis/clusters/token-auth-users/list new file mode 100644 index 000000000..ef5d462d5 --- /dev/null +++ b/gcloud/alpha/redis/clusters/token-auth-users/list @@ -0,0 +1,105 @@ +NAME + gcloud alpha redis clusters token-auth-users list - list token auth users + of a Redis cluster in a region + +SYNOPSIS + gcloud alpha redis clusters token-auth-users list + (--cluster=CLUSTER : --region=REGION) [--filter=EXPRESSION] + [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) List token auth users of a Redis cluster in a region. + +EXAMPLES + To list up to 5 token auth users for a cluster named 'my-cluster' in the + us-central1 region, run: + + $ gcloud alpha redis clusters token-auth-users list \ + --cluster=my-cluster --region=us-central1 --limit=5 + +REQUIRED FLAGS + Cluster resource - The cluster of the token auth users to display. The + arguments in this group can be used to specify the attributes of this + resource. (NOTE) Some attributes are not given arguments in this group but + can be set in other ways. + + To set the project attribute: + ◆ provide the argument --cluster on the command line with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + --cluster=CLUSTER + ID of the cluster or fully qualified identifier for the cluster. + + To set the cluster attribute: + ▸ provide the argument --cluster on the command line. + + This flag argument must be specified if any of the other arguments in + this group are specified. + + --region=REGION + The name of the Redis region of the cluster. Overrides the default + redis/region property value for this command invocation. + + To set the region attribute: + ▸ provide the argument --cluster on the command line with a fully + specified name; + ▸ provide the argument --region on the command line; + ▸ set the property redis/region. + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + + --uri + Print a list of resource URIs instead of the default output, and change + the command output to a list of URIs. If this flag is used with + --format, the formatting is applied on this URI list. To display URIs + alongside other keys instead, use the uri() transform. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the redis/v1alpha1 API. The full documentation for this + API can be found at: https://cloud.google.com/memorystore/docs/redis/ + +NOTES + This command is currently in alpha and might change without notice. If this + command fails 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 redis clusters token-auth-users list + diff --git a/gcloud/alpha/redis/clusters/update b/gcloud/alpha/redis/clusters/update index 243e1a3c8..6e38499af 100644 --- a/gcloud/alpha/redis/clusters/update +++ b/gcloud/alpha/redis/clusters/update @@ -129,7 +129,8 @@ FLAGS --node-type=NODE_TYPE Node Type of the redis cluster Node. NODE_TYPE must be one of: - redis-highmem-medium, redis-highmem-xlarge, redis-shared-core-nano, + redis-highcpu-medium, redis-highmem-2xlarge, redis-highmem-medium, + redis-highmem-xlarge, redis-shared-core-nano, redis-standard-large, redis-standard-small. --persistence-mode=PERSISTENCE_MODE diff --git a/gcloud/alpha/run/deploy b/gcloud/alpha/run/deploy index e695f7294..af8d68771 100644 --- a/gcloud/alpha/run/deploy +++ b/gcloud/alpha/run/deploy @@ -13,13 +13,13 @@ SYNOPSIS [--[no-]gpu-zonal-redundancy] [--[no-]iap] [--ingress=INGRESS; default="all"] [--[no-]invoker-iam-check] [--max=MAX] [--max-instances=MAX_INSTANCES] [--mesh=MESH] [--min=MIN] - [--min-instances=MIN_INSTANCES] [--region=REGION] [--regions=REGIONS] - [--remove-containers=[CONTAINER,...]] + [--min-instances=MIN_INSTANCES] [--public] [--region=REGION] + [--regions=REGIONS] [--remove-containers=[CONTAINER,...]] [--revision-suffix=REVISION_SUFFIX] [--scaling=SCALING] [--scaling-concurrency-target=SCALING_CONCURRENCY_TARGET] [--scaling-cpu-target=SCALING_CPU_TARGET] [--service-account=SERVICE_ACCOUNT] [--[no-]session-affinity] - [--tag=TAG] [--timeout=TIMEOUT] [--no-traffic] + [--[no-]ssh] [--tag=TAG] [--timeout=TIMEOUT] [--no-traffic] [--vpc-connector=VPC_CONNECTOR] [--vpc-egress=VPC_EGRESS] [--add-cloudsql-instances=[CLOUDSQL-INSTANCES,...] | --clear-cloudsql-instances @@ -285,6 +285,10 @@ FLAGS --min to set the minimum number of instances across all revisions of the Service which may be modified dynamically. + --public + Make the service public by disabling invoker IAM checks and IAP. + Equivalent to setting --no-invoker-iam-check and --no-iap. + --region=REGION Region in which the resource can be found. Alternatively, set the property [run/region]. @@ -333,6 +337,10 @@ FLAGS Whether to enable session affinity for connections to the service. Use --session-affinity to enable and --no-session-affinity to disable. + --[no-]ssh + Whether to enable SSH access to the service's container instancesfor + inspection and debugging. Use --ssh to enable and --no-ssh to disable. + --tag=TAG Traffic tag to assign to the newly created revision. diff --git a/gcloud/alpha/run/instances/create b/gcloud/alpha/run/instances/create index 139fed502..7a7f6b2c0 100644 --- a/gcloud/alpha/run/instances/create +++ b/gcloud/alpha/run/instances/create @@ -4,11 +4,11 @@ NAME SYNOPSIS gcloud alpha run instances create [INSTANCE] [--async] [--binary-authorization=POLICY] [--breakglass=JUSTIFICATION] - [--container=CONTAINER] [--endpoint-mode=ENDPOINT_MODE] - [--gpu-type=GPU_TYPE] [--[no-]gpu-zonal-redundancy] - [--ingress=INGRESS; default="all"] [--[no-]invoker-iam-check] - [--key=KEY] [--labels=[KEY=VALUE,...]] [--region=REGION] - [--service-account=SERVICE_ACCOUNT] + [--container=CONTAINER] [--[no-]default-url] + [--endpoint-mode=ENDPOINT_MODE] [--gpu-type=GPU_TYPE] + [--[no-]gpu-zonal-redundancy] [--ingress=INGRESS; default="all"] + [--[no-]invoker-iam-check] [--key=KEY] [--labels=[KEY=VALUE,...]] + [--region=REGION] [--service-account=SERVICE_ACCOUNT] [--set-cloudsql-instances=[CLOUDSQL-INSTANCES,...]] [--timeout=TIMEOUT] [--vpc-connector=VPC_CONNECTOR] [--vpc-egress=VPC_EGRESS] [--add-volume=[KEY=VALUE,...] @@ -81,6 +81,11 @@ FLAGS Flags that are not container-specific must be specified before --container. + --[no-]default-url + Toggles the default url for a run instance. This is enabled by default + if not specified. Use --default-url to enable and --no-default-url to + disable. + --endpoint-mode=ENDPOINT_MODE Specifies endpoint mode for a given command. Regional endpoints provide enhanced data residency and reliability by ensuring your request is @@ -418,17 +423,17 @@ FLAGS Direct VPC egress setting flags group. --network=NETWORK - The VPC network that the Cloud Run job will be able to send traffic to. - If --subnet is also specified, subnet must be a subnetwork of the - network specified by this --network flag. To clear existing VPC network - settings, use --clear-network. + The VPC network that the Cloud Run instance will be able to send + traffic to. If --subnet is also specified, subnet must be a subnetwork + of the network specified by this --network flag. To clear existing VPC + network settings, use --clear-network. --network-tags=[TAG,...] - Applies the given network tags (comma separated) to the Cloud Run job. - To clear existing tags, use --clear-network-tags. + Applies the given network tags (comma separated) to the Cloud Run + instance. To clear existing tags, use --clear-network-tags. --subnet=SUBNET - The VPC subnetwork that the Cloud Run job will get IPs from. The + The VPC subnetwork that the Cloud Run instance will get IPs from. The subnetwork must be /26 or larger. If --network is also specified, subnet must be a subnetwork of the network specified by the --network flag. If --network is not specified, network will be looked up from diff --git a/gcloud/alpha/run/instances/dev/help b/gcloud/alpha/run/instances/dev/help new file mode 100644 index 000000000..5075f9835 --- /dev/null +++ b/gcloud/alpha/run/instances/dev/help @@ -0,0 +1,35 @@ +NAME + gcloud alpha run instances dev - commands for development on Cloud Run + Instances + +SYNOPSIS + gcloud alpha run instances dev COMMAND [--region=REGION] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) This set of commands can be used for development on Cloud Run + Instances. + + To start new sync session, use gcloud alpha run instances sync. + +EXAMPLES + To start a new sync session, run: + + $ gcloud alpha run instances dev sync my-instance --source=. + +FLAGS + --region=REGION + Region in which the resource can be found. Alternatively, set the + property [run/region]. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/run/instances/help b/gcloud/alpha/run/instances/help index 2c69d66fe..7c515b59d 100644 --- a/gcloud/alpha/run/instances/help +++ b/gcloud/alpha/run/instances/help @@ -2,7 +2,8 @@ NAME gcloud alpha run instances - view and manage your Cloud Run instances SYNOPSIS - gcloud alpha run instances COMMAND [--region=REGION] [GCLOUD_WIDE_FLAG ...] + gcloud alpha run instances GROUP | COMMAND [--region=REGION] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) This set of commands can be used to view and manage your Cloud Run @@ -23,6 +24,15 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. +GROUPS + GROUP is one of the following: + + dev + (ALPHA) Commands for development on Cloud Run Instances. + + logs + (ALPHA) Read logs for Cloud Run instances. + COMMANDS COMMAND is one of the following: @@ -47,6 +57,10 @@ COMMANDS remove-iam-policy-binding (ALPHA) Remove IAM policy binding of a Cloud Run instance. + replace + (ALPHA) Create or replace an instance from a YAML instance + specification. + set-iam-policy (ALPHA) Set the IAM policy for a instance. diff --git a/gcloud/alpha/run/instances/logs/help b/gcloud/alpha/run/instances/logs/help new file mode 100644 index 000000000..0bec621c4 --- /dev/null +++ b/gcloud/alpha/run/instances/logs/help @@ -0,0 +1,35 @@ +NAME + gcloud alpha run instances logs - read logs for Cloud Run instances + +SYNOPSIS + gcloud alpha run instances logs COMMAND [--region=REGION] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Read logs for Cloud Run instances. + +FLAGS + --region=REGION + Region in which the resource can be found. Alternatively, set the + property [run/region]. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + read + (ALPHA) Read logs for a Cloud Run instance. + + tail + (ALPHA) Tail logs for a Cloud Run instance. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/run/instances/logs/read b/gcloud/alpha/run/instances/logs/read new file mode 100644 index 000000000..144380e81 --- /dev/null +++ b/gcloud/alpha/run/instances/logs/read @@ -0,0 +1,83 @@ +NAME + gcloud alpha run instances logs read - read logs for a Cloud Run instance + +SYNOPSIS + gcloud alpha run instances logs read INSTANCE + [--freshness=FRESHNESS; default="1d"] [--log-filter=LOG_FILTER] + [--order=ORDER; default="desc"] [--region=REGION] [--limit=LIMIT] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) gcloud alpha run instances logs read reads log entries. Log entries + matching --log-filter are returned according to the specified --order. If + the log entries come from multiple logs, then entries from different logs + might be intermingled in the results. + +EXAMPLES + To read log entries from for a Cloud Run instance, run: + + $ gcloud alpha run instances logs read my-instance + + To read log entries with severity ERROR or higher, run: + + $ gcloud alpha run instances logs read my-instance \ + --log-filter="severity>=ERROR" + + To read log entries written in a specific time window, run: + + $ gcloud alpha run instances logs read my-instance \ + --log-filter='timestamp<="2015-05-31T23:59:59Z" AND + timestamp>="2015-05-31T00:00:00Z"' + + To read up to 10 log entries in your instance payloads that include the + word SearchText and format the output in JSON format, run: + + $ gcloud alpha run instances logs read my-instance \ + --log-filter="textPayload:SearchText" --limit=10 --format=json + + Detailed information about filters can be found at: + https://cloud.google.com/logging/docs/view/advanced_filters + +POSITIONAL ARGUMENTS + INSTANCE + Name for a Cloud Run instance. + +FLAGS + --freshness=FRESHNESS; default="1d" + Return entries that are not older than this value. Works only with DESC + ordering and filters without a timestamp. See $ gcloud topic datetimes + for information on duration formats. + + --log-filter=LOG_FILTER + Filter expression that specifies the log entries to return. Detailed + information about filters can be found at: + https://cloud.google.com/logging/docs/view/logging-query-language + + --order=ORDER; default="desc" + Ordering of returned log entries based on timestamp field. ORDER must + be one of: desc, asc. + + --region=REGION + Region in which the resource can be found. Alternatively, set the + property [run/region]. + +LIST COMMAND FLAGS + --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. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/run/instances/logs/tail b/gcloud/alpha/run/instances/logs/tail new file mode 100644 index 000000000..5f4813e28 --- /dev/null +++ b/gcloud/alpha/run/instances/logs/tail @@ -0,0 +1,53 @@ +NAME + gcloud alpha run instances logs tail - tail logs for a Cloud Run instance + +SYNOPSIS + gcloud alpha run instances logs tail INSTANCE [--log-filter=LOG_FILTER] + [--region=REGION] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) gcloud alpha run instances logs tail tails log-entries for a + particular Cloud Run instance in real time. The log entries are formatted + for consumption in a terminal. + +EXAMPLES + To tail log entries for a Cloud Run instance, run: + + $ gcloud alpha run instances logs tail my-instance + + To tail log entries with severity ERROR or higher, run: + + $ gcloud alpha run instances logs tail my-instance \ + --log-filter="severity>=ERROR" + + Detailed information about filters can be found at: + https://cloud.google.com/logging/docs/view/advanced_filters + +POSITIONAL ARGUMENTS + INSTANCE + Name for a Cloud Run instance. + +FLAGS + --log-filter=LOG_FILTER + Filter expression that specifies the log entries to return. Detailed + information about filters can be found at: + https://cloud.google.com/logging/docs/view/logging-query-language + + --region=REGION + Region in which the resource can be found. Alternatively, set the + property [run/region]. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/run/instances/replace b/gcloud/alpha/run/instances/replace new file mode 100644 index 000000000..1a03dd74c --- /dev/null +++ b/gcloud/alpha/run/instances/replace @@ -0,0 +1,44 @@ +NAME + gcloud alpha run instances replace - create or replace an instance from a + YAML instance specification + +SYNOPSIS + gcloud alpha run instances replace FILE [--async] [--region=REGION] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Creates or replaces an instance from a YAML instance specification. + +EXAMPLES + To replace the specification for an instance defined in myinstance.yaml + + $ gcloud alpha run instances replace myinstance.yaml + +POSITIONAL ARGUMENTS + FILE + The absolute path to the YAML file with a Cloud Run instance definition + for the instance to update or create. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --region=REGION + Region in which the resource can be found. Alternatively, set the + property [run/region]. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/run/multi-region-services/update b/gcloud/alpha/run/multi-region-services/update index 97e80c6ae..88d8923e1 100644 --- a/gcloud/alpha/run/multi-region-services/update +++ b/gcloud/alpha/run/multi-region-services/update @@ -20,7 +20,7 @@ SYNOPSIS [--scaling-concurrency-target=SCALING_CONCURRENCY_TARGET] [--scaling-cpu-target=SCALING_CPU_TARGET] [--service-account=SERVICE_ACCOUNT] [--[no-]session-affinity] - [--tag=TAG] [--timeout=TIMEOUT] [--no-traffic] + [--[no-]ssh] [--tag=TAG] [--timeout=TIMEOUT] [--no-traffic] [--vpc-connector=VPC_CONNECTOR] [--vpc-egress=VPC_EGRESS] [--add-cloudsql-instances=[CLOUDSQL-INSTANCES,...] | --clear-cloudsql-instances @@ -268,6 +268,10 @@ FLAGS Whether to enable session affinity for connections to the service. Use --session-affinity to enable and --no-session-affinity to disable. + --[no-]ssh + Whether to enable SSH access to the service's container instancesfor + inspection and debugging. Use --ssh to enable and --no-ssh to disable. + --tag=TAG Traffic tag to assign to the newly created revision. diff --git a/gcloud/alpha/run/services/update b/gcloud/alpha/run/services/update index 5602dca65..600637c0b 100644 --- a/gcloud/alpha/run/services/update +++ b/gcloud/alpha/run/services/update @@ -19,7 +19,7 @@ SYNOPSIS [--scaling-concurrency-target=SCALING_CONCURRENCY_TARGET] [--scaling-cpu-target=SCALING_CPU_TARGET] [--service-account=SERVICE_ACCOUNT] [--[no-]session-affinity] - [--tag=TAG] [--timeout=TIMEOUT] [--no-traffic] + [--[no-]ssh] [--tag=TAG] [--timeout=TIMEOUT] [--no-traffic] [--vpc-connector=VPC_CONNECTOR] [--vpc-egress=VPC_EGRESS] [--add-cloudsql-instances=[CLOUDSQL-INSTANCES,...] | --clear-cloudsql-instances @@ -285,6 +285,10 @@ FLAGS Whether to enable session affinity for connections to the service. Use --session-affinity to enable and --no-session-affinity to disable. + --[no-]ssh + Whether to enable SSH access to the service's container instancesfor + inspection and debugging. Use --ssh to enable and --no-ssh to disable. + --tag=TAG Traffic tag to assign to the newly created revision. diff --git a/gcloud/alpha/run/worker-pools/add-iam-policy-binding b/gcloud/alpha/run/worker-pools/add-iam-policy-binding index cca85a12f..aa6a9238c 100644 --- a/gcloud/alpha/run/worker-pools/add-iam-policy-binding +++ b/gcloud/alpha/run/worker-pools/add-iam-policy-binding @@ -134,7 +134,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 run worker-pools add-iam-policy-binding $ gcloud beta run worker-pools add-iam-policy-binding diff --git a/gcloud/alpha/run/worker-pools/delete b/gcloud/alpha/run/worker-pools/delete index 7cfd42a80..026af6ac8 100644 --- a/gcloud/alpha/run/worker-pools/delete +++ b/gcloud/alpha/run/worker-pools/delete @@ -65,7 +65,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 run worker-pools delete $ gcloud beta run worker-pools delete diff --git a/gcloud/alpha/run/worker-pools/deploy b/gcloud/alpha/run/worker-pools/deploy index 54c93d093..bdcad7796 100644 --- a/gcloud/alpha/run/worker-pools/deploy +++ b/gcloud/alpha/run/worker-pools/deploy @@ -534,7 +534,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 run worker-pools deploy $ gcloud beta run worker-pools deploy diff --git a/gcloud/alpha/run/worker-pools/describe b/gcloud/alpha/run/worker-pools/describe index 7462210b3..dd89be035 100644 --- a/gcloud/alpha/run/worker-pools/describe +++ b/gcloud/alpha/run/worker-pools/describe @@ -62,7 +62,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud run worker-pools describe $ gcloud beta run worker-pools describe diff --git a/gcloud/alpha/run/worker-pools/get-iam-policy b/gcloud/alpha/run/worker-pools/get-iam-policy index 92a1b60bb..6bf7af51a 100644 --- a/gcloud/alpha/run/worker-pools/get-iam-policy +++ b/gcloud/alpha/run/worker-pools/get-iam-policy @@ -96,7 +96,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 run worker-pools get-iam-policy $ gcloud beta run worker-pools get-iam-policy diff --git a/gcloud/alpha/run/worker-pools/help b/gcloud/alpha/run/worker-pools/help index 792ee211d..059fbd8ea 100644 --- a/gcloud/alpha/run/worker-pools/help +++ b/gcloud/alpha/run/worker-pools/help @@ -69,7 +69,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud run worker-pools $ gcloud beta run worker-pools diff --git a/gcloud/alpha/run/worker-pools/list b/gcloud/alpha/run/worker-pools/list index a8ee75930..78fe0432e 100644 --- a/gcloud/alpha/run/worker-pools/list +++ b/gcloud/alpha/run/worker-pools/list @@ -63,7 +63,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud run worker-pools list $ gcloud beta run worker-pools list diff --git a/gcloud/alpha/run/worker-pools/logs/help b/gcloud/alpha/run/worker-pools/logs/help index b81d041a6..60a7dc6f4 100644 --- a/gcloud/alpha/run/worker-pools/logs/help +++ b/gcloud/alpha/run/worker-pools/logs/help @@ -40,7 +40,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 run worker-pools logs $ gcloud beta run worker-pools logs diff --git a/gcloud/alpha/run/worker-pools/logs/read b/gcloud/alpha/run/worker-pools/logs/read index 310743d63..76160e918 100644 --- a/gcloud/alpha/run/worker-pools/logs/read +++ b/gcloud/alpha/run/worker-pools/logs/read @@ -80,7 +80,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 run worker-pools logs read $ gcloud beta run worker-pools logs read diff --git a/gcloud/alpha/run/worker-pools/logs/tail b/gcloud/alpha/run/worker-pools/logs/tail index d02f7e4ab..9545a7a98 100644 --- a/gcloud/alpha/run/worker-pools/logs/tail +++ b/gcloud/alpha/run/worker-pools/logs/tail @@ -50,7 +50,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud run worker-pools logs tail $ gcloud beta run worker-pools logs tail diff --git a/gcloud/alpha/run/worker-pools/remove-iam-policy-binding b/gcloud/alpha/run/worker-pools/remove-iam-policy-binding index 722e0fb97..40df79e12 100644 --- a/gcloud/alpha/run/worker-pools/remove-iam-policy-binding +++ b/gcloud/alpha/run/worker-pools/remove-iam-policy-binding @@ -139,7 +139,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 run worker-pools remove-iam-policy-binding $ gcloud beta run worker-pools remove-iam-policy-binding diff --git a/gcloud/alpha/run/worker-pools/replace b/gcloud/alpha/run/worker-pools/replace index 7b8eeb4b1..ae12c172a 100644 --- a/gcloud/alpha/run/worker-pools/replace +++ b/gcloud/alpha/run/worker-pools/replace @@ -42,7 +42,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud run worker-pools replace $ gcloud beta run worker-pools replace diff --git a/gcloud/alpha/run/worker-pools/revisions/delete b/gcloud/alpha/run/worker-pools/revisions/delete index 12defa74a..2aac505fb 100644 --- a/gcloud/alpha/run/worker-pools/revisions/delete +++ b/gcloud/alpha/run/worker-pools/revisions/delete @@ -14,7 +14,7 @@ EXAMPLES To delete a revision rev1 of a worker pool worker1 in us-central1: $ gcloud alpha run worker-pools revisions delete rev1 \ - --region=us-central1 --workerpool=worker1 + --region=us-central1 --worker-pool=worker1 POSITIONAL ARGUMENTS WorkerPoolRevision resource - Worker pool revision to delete. The @@ -77,7 +77,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 run worker-pools revisions delete $ gcloud beta run worker-pools revisions delete diff --git a/gcloud/alpha/run/worker-pools/revisions/describe b/gcloud/alpha/run/worker-pools/revisions/describe index 59a244145..ae6a4d7e4 100644 --- a/gcloud/alpha/run/worker-pools/revisions/describe +++ b/gcloud/alpha/run/worker-pools/revisions/describe @@ -10,10 +10,10 @@ DESCRIPTION (ALPHA) Obtain details about a given worker pool revision. EXAMPLES - To describe a revision rev.1 of a worker pool worker1 in us-central1: + To describe a revision rev.1 in us-central1: $ gcloud alpha run worker-pools revisions describe rev.1 \ - --region=us-central1 --workerpool=worker1 + --region=us-central1 POSITIONAL ARGUMENTS Revision resource - Worker pool revision to describe. This represents a @@ -51,7 +51,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 run worker-pools revisions describe $ gcloud beta run worker-pools revisions describe diff --git a/gcloud/alpha/run/worker-pools/revisions/help b/gcloud/alpha/run/worker-pools/revisions/help index 7be535f98..7a1557f44 100644 --- a/gcloud/alpha/run/worker-pools/revisions/help +++ b/gcloud/alpha/run/worker-pools/revisions/help @@ -42,7 +42,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud run worker-pools revisions $ gcloud beta run worker-pools revisions diff --git a/gcloud/alpha/run/worker-pools/revisions/list b/gcloud/alpha/run/worker-pools/revisions/list index b049747fd..d911a2317 100644 --- a/gcloud/alpha/run/worker-pools/revisions/list +++ b/gcloud/alpha/run/worker-pools/revisions/list @@ -68,7 +68,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 run worker-pools revisions list $ gcloud beta run worker-pools revisions list diff --git a/gcloud/alpha/run/worker-pools/set-iam-policy b/gcloud/alpha/run/worker-pools/set-iam-policy index a9749fa3d..37006457d 100644 --- a/gcloud/alpha/run/worker-pools/set-iam-policy +++ b/gcloud/alpha/run/worker-pools/set-iam-policy @@ -83,7 +83,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 run worker-pools set-iam-policy $ gcloud beta run worker-pools set-iam-policy diff --git a/gcloud/alpha/run/worker-pools/update b/gcloud/alpha/run/worker-pools/update index ad3534eb4..5ad743597 100644 --- a/gcloud/alpha/run/worker-pools/update +++ b/gcloud/alpha/run/worker-pools/update @@ -512,7 +512,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 run worker-pools update $ gcloud beta run worker-pools update diff --git a/gcloud/alpha/run/worker-pools/update-instance-split b/gcloud/alpha/run/worker-pools/update-instance-split index e1f1efc65..c837d29ab 100644 --- a/gcloud/alpha/run/worker-pools/update-instance-split +++ b/gcloud/alpha/run/worker-pools/update-instance-split @@ -129,7 +129,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 run worker-pools update-instance-split $ gcloud beta run worker-pools update-instance-split diff --git a/gcloud/alpha/scc/sources/help b/gcloud/alpha/scc/sources/help index 5671409c9..7c9b86b37 100644 --- a/gcloud/alpha/scc/sources/help +++ b/gcloud/alpha/scc/sources/help @@ -19,6 +19,9 @@ COMMANDS describe (ALPHA) Describe a source given its display name or source id. + list + (ALPHA) List Cloud Security Command Center sources. + NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct diff --git a/gcloud/alpha/scc/sources/list b/gcloud/alpha/scc/sources/list new file mode 100644 index 000000000..f2cb93cdc --- /dev/null +++ b/gcloud/alpha/scc/sources/list @@ -0,0 +1,86 @@ +NAME + gcloud alpha scc sources list - list Cloud Security Command Center sources + +SYNOPSIS + gcloud alpha scc sources list [PARENT] [--filter=EXPRESSION] + [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) List Cloud Security Command Center sources. + +EXAMPLES + List all sources under organization 123456: + + $ gcloud alpha scc sources list organizations/123456 + + List all sources under folder 456: + + $ gcloud alpha scc sources list folders/456 + + List all sources under project example-project: + + $ gcloud alpha scc sources list projects/example-project + +POSITIONAL ARGUMENTS + Parent resource - parent organization, folder, or project in the Google + Cloud resource hierarchy to be used for the gcloud scc command. Specify + the argument as either [RESOURCE_TYPE/RESOURCE_ID] or [RESOURCE_ID], as + shown in the preceding examples. This represents a Cloud resource. + + [PARENT] + ID of the parent or fully qualified identifier for the parent. + + To set the parent attribute: + ◆ provide the argument parent on the command line; + ◆ Set the parent property in configuration using gcloud config set + scc/parent if it is not specified in command line. + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the securitycenter/v2 API. The full documentation for + this API can be found at: https://cloud.google.com/security-command-center + +NOTES + This command is currently in alpha and might change without notice. If this + command fails 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 scc sources list + + $ gcloud beta scc sources list + diff --git a/gcloud/alpha/service-health/artifacts/describe b/gcloud/alpha/service-health/artifacts/describe index 7cc33ac34..471c2e789 100644 --- a/gcloud/alpha/service-health/artifacts/describe +++ b/gcloud/alpha/service-health/artifacts/describe @@ -76,5 +76,7 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. + access allowlist. This variant is also available: + + $ gcloud beta service-health artifacts describe diff --git a/gcloud/alpha/service-health/artifacts/help b/gcloud/alpha/service-health/artifacts/help index 4146b64cd..b980e6079 100644 --- a/gcloud/alpha/service-health/artifacts/help +++ b/gcloud/alpha/service-health/artifacts/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 beta service-health artifacts diff --git a/gcloud/alpha/service-health/artifacts/list b/gcloud/alpha/service-health/artifacts/list index 5134c2547..eb51fe9e3 100644 --- a/gcloud/alpha/service-health/artifacts/list +++ b/gcloud/alpha/service-health/artifacts/list @@ -89,5 +89,7 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. + access allowlist. This variant is also available: + + $ gcloud beta service-health artifacts list diff --git a/gcloud/alpha/service-health/events/describe b/gcloud/alpha/service-health/events/describe index 0622e4f4d..a58eb27ad 100644 --- a/gcloud/alpha/service-health/events/describe +++ b/gcloud/alpha/service-health/events/describe @@ -76,5 +76,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. + access allowlist. These variants are also available: + + $ gcloud service-health events describe + + $ gcloud beta service-health events describe diff --git a/gcloud/alpha/service-health/events/help b/gcloud/alpha/service-health/events/help index 2ed9cd7a7..21772aa35 100644 --- a/gcloud/alpha/service-health/events/help +++ b/gcloud/alpha/service-health/events/help @@ -26,5 +26,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. + access allowlist. These variants are also available: + + $ gcloud service-health events + + $ gcloud beta service-health events diff --git a/gcloud/alpha/service-health/events/list b/gcloud/alpha/service-health/events/list index 9580751fc..07482aaa8 100644 --- a/gcloud/alpha/service-health/events/list +++ b/gcloud/alpha/service-health/events/list @@ -98,5 +98,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. + access allowlist. These variants are also available: + + $ gcloud service-health events list + + $ gcloud beta service-health events list diff --git a/gcloud/alpha/service-health/help b/gcloud/alpha/service-health/help index 93105db0f..0fda960ec 100644 --- a/gcloud/alpha/service-health/help +++ b/gcloud/alpha/service-health/help @@ -33,5 +33,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. + access allowlist. These variants are also available: + + $ gcloud service-health + + $ gcloud beta service-health diff --git a/gcloud/alpha/service-health/organization-events/describe b/gcloud/alpha/service-health/organization-events/describe index efdac7997..43e35fe8f 100644 --- a/gcloud/alpha/service-health/organization-events/describe +++ b/gcloud/alpha/service-health/organization-events/describe @@ -25,8 +25,8 @@ POSITIONAL ARGUMENTS including organization and event ID using the form organizations/{organization_id}/locations/locations/global/organizationEvents/{event_id}. - organization_id - ID (number) of the project that contains the event. To - get your organization_id, see Getting your organization resource ID + organization_id - ID (number) of the organization that contains the event. + To get your organization_id, see Getting your organization resource ID (https://cloud.google.com/resource-manager/docs/creating-managing-organization#retrieving_your_organization_id). event_id - Organization event ID to retrieve. The arguments in this group @@ -79,5 +79,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. + access allowlist. These variants are also available: + + $ gcloud service-health organization-events describe + + $ gcloud beta service-health organization-events describe diff --git a/gcloud/alpha/service-health/organization-events/help b/gcloud/alpha/service-health/organization-events/help index c6d732989..47ef06562 100644 --- a/gcloud/alpha/service-health/organization-events/help +++ b/gcloud/alpha/service-health/organization-events/help @@ -28,5 +28,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. + access allowlist. These variants are also available: + + $ gcloud service-health organization-events + + $ gcloud beta service-health organization-events diff --git a/gcloud/alpha/service-health/organization-events/list b/gcloud/alpha/service-health/organization-events/list index 46fe3e0ff..36d1b73e9 100644 --- a/gcloud/alpha/service-health/organization-events/list +++ b/gcloud/alpha/service-health/organization-events/list @@ -33,8 +33,8 @@ FLAGS Location resource - Parent value using the form organizations/{organization_id}/locations/{location}/organizationEvents. - organization_id - ID (number) of the project that contains the event. To - get your organization_id, see Getting your organization resource ID + organization_id - ID (number) of the organization that contains the event. + To get your organization_id, see Getting your organization resource ID (https://cloud.google.com/resource-manager/docs/creating-managing-organization#retrieving_your_organization_id). location - The location to get organization events from. Set this field to @@ -106,5 +106,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. + access allowlist. These variants are also available: + + $ gcloud service-health organization-events list + + $ gcloud beta service-health organization-events list diff --git a/gcloud/alpha/service-health/organization-impacts/describe b/gcloud/alpha/service-health/organization-impacts/describe index 362a37292..17a858e25 100644 --- a/gcloud/alpha/service-health/organization-impacts/describe +++ b/gcloud/alpha/service-health/organization-impacts/describe @@ -79,5 +79,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. + access allowlist. These variants are also available: + + $ gcloud service-health organization-impacts describe + + $ gcloud beta service-health organization-impacts describe diff --git a/gcloud/alpha/service-health/organization-impacts/help b/gcloud/alpha/service-health/organization-impacts/help index 1ae56d6d7..73df6b815 100644 --- a/gcloud/alpha/service-health/organization-impacts/help +++ b/gcloud/alpha/service-health/organization-impacts/help @@ -28,5 +28,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. + access allowlist. These variants are also available: + + $ gcloud service-health organization-impacts + + $ gcloud beta service-health organization-impacts diff --git a/gcloud/alpha/service-health/organization-impacts/list b/gcloud/alpha/service-health/organization-impacts/list index 19b36651e..c561fe993 100644 --- a/gcloud/alpha/service-health/organization-impacts/list +++ b/gcloud/alpha/service-health/organization-impacts/list @@ -99,5 +99,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. + access allowlist. These variants are also available: + + $ gcloud service-health organization-impacts list + + $ gcloud beta service-health organization-impacts list diff --git a/gcloud/alpha/services/api-keys/update b/gcloud/alpha/services/api-keys/update index 2d3aa95dc..0e66ab2cd 100644 --- a/gcloud/alpha/services/api-keys/update +++ b/gcloud/alpha/services/api-keys/update @@ -19,49 +19,54 @@ EXAMPLES To remove all restrictions of the key: $ gcloud alpha services api-keys update \ - projects/myproject/keys/my-key-id --clear-restrictions + projects/myproject/locations/global/keys/my-key-id \ + --clear-restrictions To update display name and set allowed ips as server key restrictions: $ gcloud alpha services api-keys update \ - projects/myproject/keys/my-key-id --display-name="test name" \ + projects/myproject/locations/global/keys/my-key-id \ + --display-name="test name" \ --allowed-ips=2620:15c:2c4:203:2776:1f90:6b3b:217,104.133.8.78 To update annotations: $ gcloud alpha services api-keys update \ - projects/myproject/keys/my-key-id --annotations=foo=bar,abc=def + projects/myproject/locations/global/keys/my-key-id \ + --annotations=foo=bar,abc=def To update key's allowed referrers restriction: $ gcloud alpha services api-keys update \ - projects/myproject/keys/my-key-id \ + projects/myproject/locations/global/keys/my-key-id \ --allowed-referrers="https://www.example.com/*,http://sub.exampl\ e.com/*" To update key's allowed ios app bundle ids: $ gcloud alpha services api-keys update \ - projects/myproject/keys/my-key-id --allowed-bundle-ids=my.app + projects/myproject/locations/global/keys/my-key-id \ + --allowed-bundle-ids=my.app To update key's allowed android application: $ gcloud alpha services api-keys update \ - projects/myproject/keys/my-key-id \ + projects/myproject/locations/global/keys/my-key-id \ --allowed-application=sha1_fingerprint=foo1,package_name=bar1 \ --allowed-application=sha1_fingerprint=foo2,package_name=bar2 To update keys' allowed api target with multiple services: $ gcloud alpha services api-keys update \ - projects/myproject/keys/my-key-id \ + projects/myproject/locations/global/keys/my-key-id \ --api-target=service=bar.service.com \ --api-target=service=foo.service.com To update keys' allowed api target with service and method: $ gcloud alpha services api-keys update \ - projects/myproject/keys/my-key-id --flags-file=my-flags.yaml + projects/myproject/locations/global/keys/my-key-id \ + --flags-file=my-flags.yaml The content of 'my-flags.yaml' is as following: diff --git a/gcloud/alpha/spanner/databases/update b/gcloud/alpha/spanner/databases/update index 1f72505a4..71d5ab1a8 100644 --- a/gcloud/alpha/spanner/databases/update +++ b/gcloud/alpha/spanner/databases/update @@ -4,8 +4,8 @@ NAME SYNOPSIS gcloud alpha spanner databases update (DATABASE : --instance=INSTANCE) [--async] - [--[no-]enable-drop-protection | --kms-keys=KMS_KEY,[KMS_KEY,...]] - [GCLOUD_WIDE_FLAG ...] + [--clear-kms-keys | --[no-]enable-drop-protection + | --kms-keys=KMS_KEY,[KMS_KEY,...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Update a Cloud Spanner database. @@ -29,6 +29,11 @@ EXAMPLES $ gcloud alpha spanner databases update my-database \ --kms-keys="KEY1,KEY2" + To remove all KMS key references and revert a Cloud Spanner database + 'my-database' to Google-managed encryption, run: + + $ gcloud alpha spanner databases update my-database --clear-kms-keys + POSITIONAL ARGUMENTS Database resource - The Cloud Spanner database to update. The arguments in this group can be used to specify the attributes of this resource. (NOTE) @@ -68,6 +73,10 @@ FLAGS At most one of these can be specified: + --clear-kms-keys + Removes all KMS key references and reverts the database to + Google-managed encryption. + --[no-]enable-drop-protection Enable database deletion protection on this database. Use --enable-drop-protection to enable and --no-enable-drop-protection to diff --git a/gcloud/alpha/sql/instances/create b/gcloud/alpha/sql/instances/create index db5bf2223..a52b91f1d 100644 --- a/gcloud/alpha/sql/instances/create +++ b/gcloud/alpha/sql/instances/create @@ -33,6 +33,7 @@ SYNOPSIS [--[no-]enable-data-cache] [--[no-]enable-dataplex-integration] [--[no-]enable-google-ml-integration] [--enable-google-private-path] [--enable-password-policy] [--enable-point-in-time-recovery] + [--[no-]enable-psc-auto-dns] [--[no-]enable-psc-write-endpoint-dns] [--enforce-new-sql-network-architecture] [--failover-replica-name=FAILOVER_REPLICA_NAME] [--[no-]final-backup] [--final-backup-retention-days=FINAL_BACKUP_RETENTION_DAYS] @@ -365,6 +366,16 @@ FLAGS backups enabled to use. Make sure storage can support at least 7 days of logs. + --[no-]enable-psc-auto-dns + Enable per instance DNS records for PSC auto-connections. Use + --enable-psc-auto-dns to enable and --no-enable-psc-auto-dns to + disable. + + --[no-]enable-psc-write-endpoint-dns + Enable the global DNS record pointing to the primary, for Enterprise + Plus edition only. Use --enable-psc-write-endpoint-dns to enable and + --no-enable-psc-write-endpoint-dns to disable. + --enforce-new-sql-network-architecture Force the instance to use the new network architecture. @@ -521,9 +532,19 @@ FLAGS MySQL instance. The input should be in a format of key=value. Available case-sensitive keys are: enabled (boolean), probing-interval-seconds (integer), probe-threshold (integer), running-threads-threshold - (integer), seconds-behind-source-threshold (integer), and - transaction-duration-threshold (integer). Example: - --performance-capture-config enabled=true,probe-threshold=5 + (integer), seconds-behind-source-threshold (integer), + transaction-duration-threshold (integer), + cpu-utilization-threshold-percent (integer), + memory-usage-threshold-percent (integer), + transaction-lock-wait-threshold-count (integer), + semaphore-wait-threshold-count (integer), + history-list-length-threshold-count (integer), + transaction-kill-threshold-seconds (integer), transaction-kill-type + (string), transaction-kill-excluded-user-hosts (string, + semicolon-separated list) Example: --performance-capture-config + enabled=true,probe-threshold=5, cpu-utilization-threshold-percent=80, + transaction-kill-excluded-user-hosts=user1@host1;user2@%, + transaction-kill-type=READ_ONLY_TRANSACTIONS --psc-auto-connections=[network=NETWORK],[project=PROJECT] A comma-separated list of networks or network-project pairs. Each diff --git a/gcloud/alpha/sql/instances/patch b/gcloud/alpha/sql/instances/patch index 828efd040..cc107e087 100644 --- a/gcloud/alpha/sql/instances/patch +++ b/gcloud/alpha/sql/instances/patch @@ -30,7 +30,8 @@ SYNOPSIS [--[no-]enable-google-ml-integration] [--[no-]enable-google-private-path] [--enable-password-policy] [--[no-]enable-point-in-time-recovery] - [--[no-]enable-private-service-connect] + [--[no-]enable-private-service-connect] [--[no-]enable-psc-auto-dns] + [--[no-]enable-psc-write-endpoint-dns] [--enforce-new-sql-network-architecture] [--failover-dr-replica-name=FAILOVER_DR_REPLICA_NAME] [--[no-]final-backup] @@ -322,6 +323,16 @@ FLAGS Connect. Use --enable-private-service-connect to enable and --no-enable-private-service-connect to disable. + --[no-]enable-psc-auto-dns + Enable per instance DNS records for PSC auto-connections. Use + --enable-psc-auto-dns to enable and --no-enable-psc-auto-dns to + disable. + + --[no-]enable-psc-write-endpoint-dns + Enable the global DNS record pointing to the primary, for Enterprise + Plus edition only. Use --enable-psc-write-endpoint-dns to enable and + --no-enable-psc-write-endpoint-dns to disable. + --enforce-new-sql-network-architecture Force the instance to use the new network architecture. @@ -487,9 +498,19 @@ FLAGS MySQL instance. The input should be in a format of key=value. Available case-sensitive keys are: enabled (boolean), probing-interval-seconds (integer), probe-threshold (integer), running-threads-threshold - (integer), seconds-behind-source-threshold (integer), and - transaction-duration-threshold (integer). Example: - --performance-capture-config enabled=true,probe-threshold=5 + (integer), seconds-behind-source-threshold (integer), + transaction-duration-threshold (integer), + cpu-utilization-threshold-percent (integer), + memory-usage-threshold-percent (integer), + transaction-lock-wait-threshold-count (integer), + semaphore-wait-threshold-count (integer), + history-list-length-threshold-count (integer), + transaction-kill-threshold-seconds (integer), transaction-kill-type + (string), transaction-kill-excluded-user-hosts (string, + semicolon-separated list) Example: --performance-capture-config + enabled=true,probe-threshold=5, cpu-utilization-threshold-percent=80, + transaction-kill-excluded-user-hosts=user1@host1;user2@%, + transaction-kill-type=READ_ONLY_TRANSACTIONS --pricing-plan=PRICING_PLAN, -p PRICING_PLAN First Generation instances only. The pricing plan for this instance. diff --git a/gcloud/alpha/storage/batch-operations/jobs/create b/gcloud/alpha/storage/batch-operations/jobs/create index c709f58b3..3a78246ff 100644 --- a/gcloud/alpha/storage/batch-operations/jobs/create +++ b/gcloud/alpha/storage/batch-operations/jobs/create @@ -4,9 +4,13 @@ NAME SYNOPSIS gcloud alpha storage batch-operations jobs create BATCH_JOB - (--bucket=BUCKET | --bucket-list=[BUCKETS,...]) - (--included-object-prefixes=[PREFIXES,...] + ((--bucket=BUCKET | --bucket-list=[BUCKETS,...]) + (--included-object-prefixes=[PREFIXES,...] | --manifest-location=MANIFEST_LOCATION) + | --dry-run-job-id=DRY_RUN_JOB_ID + | [--insights-dataset-config=INSIGHTS_DATASET_CONFIG + --target-project=TARGET_PROJECT + : --bucket-filters=BUCKET_FILTERS --object-filters=OBJECT_FILTERS]) (--put-metadata=KEY=VALUE,[KEY=VALUE,...] | --rewrite-object=KEY=VALUE,[KEY=VALUE,...] | --clear-all-object-custom-contexts @@ -71,6 +75,18 @@ EXAMPLES --put-metadata=Content-Disposition=inline,Content-Language=en \ --log-actions=transform --log-action-states=succeeded,failed + The following example command creates a batch job, named my-job, that uses + a project as the source and updates object retention: + + $ gcloud alpha storage batch-operations jobs create my-job \ + --target-project=my-project \ + --insights-dataset-config=projects/my-project/locations/\ + us-central1/datasetConfigs/my-config \ + --bucket-filters="bucket_name == 'my-bucket'" \ + --object-filters="size > 100" \ + --put-metadata=Retain-Until=2025-01-01T00:00:00Z,\ + Retention-Mode=locked + POSITIONAL ARGUMENTS Batch job resource - The batch job to create. This represents a Cloud resource. (NOTE) Some attributes are not given arguments in this group but @@ -96,32 +112,73 @@ POSITIONAL ARGUMENTS ▸ provide the argument batch_job on the command line. REQUIRED FLAGS - Exactly one of these must be specified: - - --bucket=BUCKET - Bucket containing the objects that the batch job will operate on. - - --bucket-list=[BUCKETS,...] - List of buckets containing the objects that the batch job will - operate on. - - Source specifying objects to perform batch operations on. Must be one of - --manifest-location=``MANIFEST_LOCATION or - --included-object-prefixes=``COMMA_SEPARATED_PREFIXES + Source specifying objects to perform batch operations on. You can specify + either a bucket-based source or a project-based source. Exactly one of these must be specified: - --included-object-prefixes=[PREFIXES,...] - A comma-separated list of object prefixes to describe the objects - being transformed. An empty string means all objects in the bucket. + Use bucket(s) as the source. - --manifest-location=MANIFEST_LOCATION - An absolute path to the manifest source file in a Google Cloud - Storage bucket. The file must be a CSV file where each row specifies - the object details i.e. ProjectId, BucketId, and Name. Generation may - optionally be specified. When generation is not specified, the live - object is acted upon. Format: - --manifest-location=gs://bucket_name/path/manifest_name.csv + Exactly one of these must be specified: + + --bucket=BUCKET + Bucket containing the objects that the batch job will operate on. + + --bucket-list=[BUCKETS,...] + List of buckets containing the objects that the batch job will + operate on. + + Source specifying objects to perform batch operations on. Must be one of + --manifest-location=``MANIFEST_LOCATION or + --included-object-prefixes=``COMMA_SEPARATED_PREFIXES + + Exactly one of these must be specified: + + --included-object-prefixes=[PREFIXES,...] + A comma-separated list of object prefixes to describe the objects + being transformed. An empty string means all objects in the bucket. + + --manifest-location=MANIFEST_LOCATION + An absolute path to the manifest source file in a Google Cloud + Storage bucket. The file must be a CSV file where each row + specifies the object details i.e. ProjectId, BucketId, and Name. + Generation may optionally be specified. When generation is not + specified, the live object is acted upon. Format: + --manifest-location=gs://bucket_name/path/manifest_name.csv + + Use a project as the source. + + At most one of these can be specified: + + --dry-run-job-id=DRY_RUN_JOB_ID + The unique identifier of a dry run job to use as the baseline. + Specifying this ID ensures the job is executed against the same set + of objects validated during the dry run. + + Or at least one of these can be specified: + + --insights-dataset-config=INSIGHTS_DATASET_CONFIG + The resource identifier of the Storage Insights dataset + configuration. Format: + projects/{project}/locations/{location}/datasetConfigs/{datasetConfig} + + This flag argument must be specified if any of the other + arguments in this group are specified. + + --target-project=TARGET_PROJECT + Project name of the objects to be transformed. e.g. my-project or + 123456. + + This flag argument must be specified if any of the other + arguments in this group are specified. + + --bucket-filters=BUCKET_FILTERS + Filters expressed in Common Expression Language (CEL) to apply to + buckets. E.g. "bucket_name == 'my-bucket'". + + --object-filters=OBJECT_FILTERS + Filters expressed in Common Expression Language (CEL) to apply to + objects. E.g. "size > 100". Transformation to be performed on the objects. diff --git a/gcloud/alpha/storage/objects/compose b/gcloud/alpha/storage/objects/compose index 2a8f654c7..04c5c6a39 100644 --- a/gcloud/alpha/storage/objects/compose +++ b/gcloud/alpha/storage/objects/compose @@ -4,7 +4,7 @@ NAME SYNOPSIS gcloud alpha storage objects compose SOURCE [SOURCE ...] DESTINATION - [--additional-headers=HEADER=VALUE] + [--additional-headers=HEADER=VALUE] [--delete-source-objects] [--clear-custom-contexts | --custom-contexts=[CUSTOM_CONTEXTS_KEYS_AND_VALUES,...] | --custom-contexts-file=CUSTOM_CONTEXTS_FILE] @@ -37,6 +37,13 @@ EXAMPLES gs://bucket/b.txt gs://bucket/target.txt \ --custom-contexts=key1=value1,key2=value2 + The following command creates a new object target.txt by concatenating + a.txt and b.txt, and deletes the source objects after a successful + composition: + + $ gcloud alpha storage objects compose gs://bucket/a.txt \ + gs://bucket/b.txt gs://bucket/target.txt --delete-source-objects + POSITIONAL ARGUMENTS SOURCE [SOURCE ...] The list of source objects that will be concatenated into a single @@ -52,6 +59,11 @@ FLAGS Overrides the default storage/additional_headers property value for this command invocation. + --delete-source-objects + If set, the source objects will be deleted after a successful + composition. Note that this deletion bypasses the soft delete policy if + configured on the bucket. + OBJECT CONTEXTS FLAGS Group that allow users to handle object contexts. diff --git a/gcloud/alpha/workload-identity/help b/gcloud/alpha/workload-identity/help new file mode 100644 index 000000000..5036338b6 --- /dev/null +++ b/gcloud/alpha/workload-identity/help @@ -0,0 +1,30 @@ +NAME + gcloud alpha workload-identity - manage Workload Identity + +SYNOPSIS + gcloud alpha workload-identity GROUP [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Manage Workload Identity. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +GROUPS + GROUP is one of the following: + + service-agents + (ALPHA) Manage Service Agents for Workload Identity. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails 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 workload-identity + + $ gcloud beta workload-identity + diff --git a/gcloud/alpha/workload-identity/service-agents/generate b/gcloud/alpha/workload-identity/service-agents/generate new file mode 100644 index 000000000..66d09537e --- /dev/null +++ b/gcloud/alpha/workload-identity/service-agents/generate @@ -0,0 +1,78 @@ +NAME + gcloud alpha workload-identity service-agents generate - generate service + agents for a service producer + +SYNOPSIS + gcloud alpha workload-identity service-agents generate --service=SERVICE + (--folder=FOLDER | --organization=ORGANIZATION | --project=PROJECT) + [--location=LOCATION; default="global"] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) It can be generated in a project, folder, or organization and + location. + + gcloud alpha workload-identity service-agents generate generates service + agents for a given service producer in a specific project, folder, or + organization and location. + +EXAMPLES + To generate service agents for bigquery.googleapis.com in the global + location for the project 123456, run: + + $ gcloud alpha workload-identity service-agents generate \ + --service="bigquery.googleapis.com" --location="global" \ + --project="123456" + + To generate service agents for bigquery.googleapis.com in the global + location for the folder 123456, run: + + $ gcloud alpha workload-identity service-agents generate \ + --service="bigquery.googleapis.com" --location="global" \ + --folder="123456" + + To generate service agents for bigquery.googleapis.com in the global + location for the organization 123456, run: + + $ gcloud alpha workload-identity service-agents generate \ + --service="bigquery.googleapis.com" --location="global" \ + --organization="123456" + +REQUIRED FLAGS + --service=SERVICE + The service producer to generate service agents for (e.g. + bigquery.googleapis.com). + + Exactly one of these must be specified: + + --folder=FOLDER + The folder number to generate service agents for. + + --organization=ORGANIZATION + The organization number to generate service agents for. + + --project=PROJECT + The project number to generate service agents for. + +OPTIONAL FLAGS + --location=LOCATION; default="global" + The location for which to generate the service agents. Defaults to + global. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --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 workload-identity service-agents generate + + $ gcloud beta workload-identity service-agents generate + diff --git a/gcloud/alpha/workload-identity/service-agents/help b/gcloud/alpha/workload-identity/service-agents/help new file mode 100644 index 000000000..cff5a2f51 --- /dev/null +++ b/gcloud/alpha/workload-identity/service-agents/help @@ -0,0 +1,32 @@ +NAME + gcloud alpha workload-identity service-agents - manage Service Agents for + Workload Identity + +SYNOPSIS + gcloud alpha workload-identity service-agents COMMAND + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Manage Service Agents for Workload Identity. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + generate + (ALPHA) Generate service agents for a service producer. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails 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 workload-identity service-agents + + $ gcloud beta workload-identity service-agents + diff --git a/gcloud/alpha/workstations/clusters/create b/gcloud/alpha/workstations/clusters/create index 511313764..34410d7dc 100644 --- a/gcloud/alpha/workstations/clusters/create +++ b/gcloud/alpha/workstations/clusters/create @@ -3,9 +3,9 @@ NAME SYNOPSIS gcloud alpha workstations clusters create (CLUSTER : --region=REGION) - [--async] [--domain=DOMAIN] [--enable-private-endpoint] - [--labels=[KEY=VALUE,...]] [--network=NETWORK] - [--subnetwork=SUBNETWORK] [--tags=[KEY=VALUE,...]] + [--async] [--domain=DOMAIN] [--enable-http2] + [--enable-private-endpoint] [--labels=[KEY=VALUE,...]] + [--network=NETWORK] [--subnetwork=SUBNETWORK] [--tags=[KEY=VALUE,...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -64,6 +64,9 @@ FLAGS --domain=DOMAIN Domain used by Workstations for HTTP ingress. + --enable-http2 + Whether HTTP/2 is enabled for the workstation cluster. + --enable-private-endpoint Default is false. If specified, the cluster will be assigned an internal IP address to the Cluster Gateway. This isolates the cluster's diff --git a/gcloud/alpha/workstations/clusters/help b/gcloud/alpha/workstations/clusters/help index 242b93e0a..b5f50d8bf 100644 --- a/gcloud/alpha/workstations/clusters/help +++ b/gcloud/alpha/workstations/clusters/help @@ -28,6 +28,9 @@ COMMANDS list (ALPHA) List workstation clusters. + update + (ALPHA) Update a workstation cluster. + NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct diff --git a/gcloud/alpha/workstations/clusters/update b/gcloud/alpha/workstations/clusters/update new file mode 100644 index 000000000..f1ba34560 --- /dev/null +++ b/gcloud/alpha/workstations/clusters/update @@ -0,0 +1,113 @@ +NAME + gcloud alpha workstations clusters update - update a workstation cluster + +SYNOPSIS + gcloud alpha workstations clusters update (CLUSTER : --region=REGION) + [--async] [--display-name=DISPLAY_NAME] [--enable-http2] + [--update-labels=[KEY=VALUE,...]] + [--clear-labels | --remove-labels=[KEY,...]] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Update a workstation cluster. + +EXAMPLES + To update the display name of workstation cluster my-cluster in region + us-central1, run: + + $ gcloud alpha workstations clusters update my-cluster \ + --region=us-central1 --display-name='My New Cluster Name' + +POSITIONAL ARGUMENTS + Cluster resource - Arguments and flags that specify the cluster 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 cluster on the command line with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + CLUSTER + ID of the cluster or fully qualified identifier for the cluster. + + To set the cluster attribute: + ▸ provide the argument cluster on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --region=REGION + The name of the region of the cluster. + + To set the region attribute: + ▸ provide the argument cluster on the command line with a fully + specified name; + ▸ provide the argument --region on the command line; + ▸ set the property workstations/region. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --display-name=DISPLAY_NAME + Human-readable name for this workstation cluster. + + --enable-http2 + Enable or disable HTTP/2 for the workstation cluster. + + --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 workstations clusters update --clear-labels + + To remove all existing labels and create two new labels, foo and baz: + + $ gcloud alpha workstations clusters 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 workstations/v1beta API. The full documentation for + this API can be found at: https://cloud.google.com/workstations + +NOTES + This command is currently in alpha and might change without notice. If this + command fails 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 workstations clusters update + + $ gcloud beta workstations clusters update + diff --git a/gcloud/alpha/workstations/ssh b/gcloud/alpha/workstations/ssh index 5ce7dc164..8a3f34007 100644 --- a/gcloud/alpha/workstations/ssh +++ b/gcloud/alpha/workstations/ssh @@ -6,7 +6,7 @@ SYNOPSIS (WORKSTATION : --cluster=CLUSTER --config=CONFIG --region=REGION) [--command=COMMAND] [--local-host-port=LOCAL_HOST_PORT; default="localhost:0"] - [--port=PORT; default=22] [--ssh-flag=SSH_FLAG] + [--port=PORT; default=22] [--ssh-flag=SSH_FLAG] [--start-workstation] [--user=USER; default="user"] [GCLOUD_WIDE_FLAG ...] [-- SSH_ARGS ...] DESCRIPTION @@ -113,6 +113,10 @@ FLAGS $ gcloud alpha workstations ssh --ssh-flag="-vvv" \ --ssh-flag="-L 80:localhost:80" + --start-workstation + If set, automatically starts the workstation if it is currently + stopped. + --user=USER; default="user" The username with which to SSH. diff --git a/gcloud/alpha/workstations/start-tcp-tunnel b/gcloud/alpha/workstations/start-tcp-tunnel index d958a4152..3dc49d23d 100644 --- a/gcloud/alpha/workstations/start-tcp-tunnel +++ b/gcloud/alpha/workstations/start-tcp-tunnel @@ -7,7 +7,7 @@ SYNOPSIS (WORKSTATION : --cluster=CLUSTER --config=CONFIG --region=REGION) WORKSTATION_PORT [--local-host-port=LOCAL_HOST_PORT; default="localhost:0"] - [GCLOUD_WIDE_FLAG ...] + [--start-workstation] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Start a tunnel through which a local process can forward TCP @@ -87,6 +87,10 @@ FLAGS If LOCAL_PORT is 0, an arbitrary unused local port is chosen. + --start-workstation + If set, automatically starts the workstation if it is currently + stopped. + 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/artifacts/help b/gcloud/artifacts/help index b2de8c742..e61099752 100644 --- a/gcloud/artifacts/help +++ b/gcloud/artifacts/help @@ -45,6 +45,10 @@ GROUPS print-settings Print snippets to add to native tools settings files. + projects + Manage Artifact Registry project-level configurations for a specific + location. + repositories Manage Artifact Registry repositories. diff --git a/gcloud/artifacts/projects/describe b/gcloud/artifacts/projects/describe new file mode 100644 index 000000000..16c7b4b56 --- /dev/null +++ b/gcloud/artifacts/projects/describe @@ -0,0 +1,46 @@ +NAME + gcloud artifacts projects describe - describe project configuration + +SYNOPSIS + gcloud artifacts projects describe [--location=LOCATION] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Describe the Artifact Registry project configuration for the current + project in a given location. + +EXAMPLES + To describe project configuration in us-west1: + + $ gcloud artifacts projects describe --location=us-west1 + +FLAGS + Location resource - The location of the project configuration to describe. + This represents a Cloud resource. (NOTE) Some attributes are not given + arguments in this group but can be set in other ways. + + To set the project attribute: + ◆ provide the argument --location on the command line with a fully + specified name; + ◆ set the property artifacts/location with a fully specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + --location=LOCATION + ID of the location or fully qualified identifier for the location. + + To set the location attribute: + ◆ provide the argument --location on the command line; + ◆ set the property artifacts/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 artifactregistry/v1 API. The full documentation for + this API can be found at: https://cloud.google.com/artifacts/docs/ diff --git a/gcloud/artifacts/projects/help b/gcloud/artifacts/projects/help new file mode 100644 index 000000000..58ad7a31c --- /dev/null +++ b/gcloud/artifacts/projects/help @@ -0,0 +1,24 @@ +NAME + gcloud artifacts projects - manage Artifact Registry project-level + configurations for a specific location + +SYNOPSIS + gcloud artifacts projects COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Manage Artifact Registry project-level configurations for a specific + location. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + describe + Describe project configuration. + + update + Update project configuration. diff --git a/gcloud/artifacts/projects/update b/gcloud/artifacts/projects/update new file mode 100644 index 000000000..930a91aad --- /dev/null +++ b/gcloud/artifacts/projects/update @@ -0,0 +1,70 @@ +NAME + gcloud artifacts projects update - update project configuration + +SYNOPSIS + gcloud artifacts projects update [--location=LOCATION] + [--severity=SEVERITY] + [--clear-platform-logs | --disable-platform-logs + | --enable-platform-logs] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Update the Artifact Registry project configuration for the current project + in a given location. + +EXAMPLES + To enable INFO level platform logs for project configuration in us-west1: + + $ gcloud artifacts projects update --location=us-west1 \ + --enable-platform-logs --severity=INFO + +FLAGS + Location resource - The location of the project configuration to update. + This represents a Cloud resource. (NOTE) Some attributes are not given + arguments in this group but can be set in other ways. + + To set the project attribute: + ◆ provide the argument --location on the command line with a fully + specified name; + ◆ set the property artifacts/location with a fully specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + --location=LOCATION + ID of the location or fully qualified identifier for the location. + + To set the location attribute: + ◆ provide the argument --location on the command line; + ◆ set the property artifacts/location. + + --severity=SEVERITY + The minimum severity level of logs to generate. This flag is only + applicable when using --enable-platform-logs. SEVERITY must be one of: + + error + Log events with severity ERROR or higher. + info + Log events with severity INFO or higher. + + At most one of these can be specified: + + --clear-platform-logs + Clear platform logging settings for the project in this location to + fall back to organization settings or AR defaults. + + --disable-platform-logs + Disable platform logging for the project in this location. + + --enable-platform-logs + Enable platform logging for the project in this 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 artifactregistry/v1 API. The full documentation for + this API can be found at: https://cloud.google.com/artifacts/docs/ diff --git a/gcloud/artifacts/repositories/create b/gcloud/artifacts/repositories/create index 4d7b3e39e..133fea9de 100644 --- a/gcloud/artifacts/repositories/create +++ b/gcloud/artifacts/repositories/create @@ -16,10 +16,11 @@ SYNOPSIS [--remote-python-repo=REMOTE_PYTHON_REPO] [--remote-repo-config-desc=REMOTE_REPO_CONFIG_DESC] [--remote-username=REMOTE_USERNAME] [--remote-yum-repo=REMOTE_YUM_REPO] - [--remote-yum-repo-path=REMOTE_YUM_REPO_PATH] + [--remote-yum-repo-path=REMOTE_YUM_REPO_PATH] [--severity=SEVERITY] [--upstream-policy-file=FILE] [--version-policy=VERSION_POLICY] [--allow-vulnerability-scanning | --disable-vulnerability-scanning] - [GCLOUD_WIDE_FLAG ...] + [--clear-platform-logs | --disable-platform-logs + | --enable-platform-logs] [GCLOUD_WIDE_FLAG ...] DESCRIPTION Create a new Artifact Registry repository. @@ -202,6 +203,15 @@ OPTIONAL FLAGS --remote-yum-repo-path=REMOTE_YUM_REPO_PATH (Yum only) Remaining URL path to yum remote repository. + --severity=SEVERITY + The minimum severity level of logs to generate. This flag is only + applicable when using --enable-platform-logs. SEVERITY must be one of: + + error + Log events with severity ERROR or higher. + info + Log events with severity INFO or higher. + --upstream-policy-file=FILE (Virtual Repositories only) is the upstreams for the Virtual Repository. Example of the file contents: [ { "id": "test1", @@ -228,6 +238,18 @@ OPTIONAL FLAGS --disable-vulnerability-scanning Disable vulnerability scanning on the repository. + At most one of these can be specified: + + --clear-platform-logs + Clear platform logging settings for the repository to fall back to + project settings. + + --disable-platform-logs + Disable platform logging for the repository. + + --enable-platform-logs + Enable platform logging for the repository. + 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/artifacts/repositories/update b/gcloud/artifacts/repositories/update index 285989bb8..d1c64a655 100644 --- a/gcloud/artifacts/repositories/update +++ b/gcloud/artifacts/repositories/update @@ -7,10 +7,12 @@ SYNOPSIS [--description=DESCRIPTION] [--disable-remote-validation] [--immutable-tags] [--remote-password-secret-version=REMOTE_PASSWORD_SECRET_VERSION] - [--remote-username=REMOTE_USERNAME] [--update-labels=[KEY=VALUE,...]] - [--upstream-policy-file=FILE] + [--remote-username=REMOTE_USERNAME] [--severity=SEVERITY] + [--update-labels=[KEY=VALUE,...]] [--upstream-policy-file=FILE] [--allow-vulnerability-scanning | --disable-vulnerability-scanning] - [--clear-labels | --remove-labels=[KEY,...]] [GCLOUD_WIDE_FLAG ...] + [--clear-labels | --remove-labels=[KEY,...]] + [--clear-platform-logs | --disable-platform-logs + | --enable-platform-logs] [GCLOUD_WIDE_FLAG ...] DESCRIPTION Update the description or labels for an Artifact Registry repository. @@ -82,6 +84,15 @@ FLAGS --remote-username=REMOTE_USERNAME Remote Repository upstream registry username. + --severity=SEVERITY + The minimum severity level of logs to generate. This flag is only + applicable when using --enable-platform-logs. SEVERITY must be one of: + + error + Log events with severity ERROR or higher. + info + Log events with severity INFO or higher. + --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. @@ -126,6 +137,18 @@ FLAGS silently ignored. If --update-labels is also specified then --update-labels is applied first. + At most one of these can be specified: + + --clear-platform-logs + Clear platform logging settings for the repository to fall back to + project settings. + + --disable-platform-logs + Disable platform logging for the repository. + + --enable-platform-logs + Enable platform logging for the repository. + 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/artifacts/tags/export b/gcloud/artifacts/tags/export index cf79e08b3..39a8f69bc 100644 --- a/gcloud/artifacts/tags/export +++ b/gcloud/artifacts/tags/export @@ -36,7 +36,7 @@ POSITIONAL ARGUMENTS TAG ID of the tag or fully qualified identifier for the tag. - To set the name attribute: + To set the tag attribute: ▸ provide the argument tag on the command line. This positional argument must be specified if any of the other diff --git a/gcloud/artifacts/versions/export b/gcloud/artifacts/versions/export index d16f39ce3..b43fb5c9a 100644 --- a/gcloud/artifacts/versions/export +++ b/gcloud/artifacts/versions/export @@ -37,7 +37,7 @@ POSITIONAL ARGUMENTS VERSION ID of the version or fully qualified identifier for the version. - To set the name attribute: + To set the version attribute: ▸ provide the argument version on the command line. This positional argument must be specified if any of the other diff --git a/gcloud/backup-dr/backup-plan-associations/create b/gcloud/backup-dr/backup-plan-associations/create index c0dceca94..5dbae75f8 100644 --- a/gcloud/backup-dr/backup-plan-associations/create +++ b/gcloud/backup-dr/backup-plan-associations/create @@ -116,7 +116,9 @@ BRIEF Creates a new backup plan association NOTES - This variant is also available: + These variants are also available: $ gcloud alpha backup-dr backup-plan-associations create + $ gcloud beta backup-dr backup-plan-associations create + diff --git a/gcloud/backup-dr/backup-plan-associations/delete b/gcloud/backup-dr/backup-plan-associations/delete index d2adfeb27..5ea5a18a7 100644 --- a/gcloud/backup-dr/backup-plan-associations/delete +++ b/gcloud/backup-dr/backup-plan-associations/delete @@ -71,7 +71,9 @@ BRIEF Delete a specific backup plan association NOTES - This variant is also available: + These variants are also available: $ gcloud alpha backup-dr backup-plan-associations delete + $ gcloud beta backup-dr backup-plan-associations delete + diff --git a/gcloud/backup-dr/backup-plan-associations/describe b/gcloud/backup-dr/backup-plan-associations/describe index f119f230a..9ecfa1ce0 100644 --- a/gcloud/backup-dr/backup-plan-associations/describe +++ b/gcloud/backup-dr/backup-plan-associations/describe @@ -61,7 +61,9 @@ API REFERENCE can be found at: https://cloud.google.com/backup-disaster-recovery NOTES - This variant is also available: + These variants are also available: $ gcloud alpha backup-dr backup-plan-associations describe + $ gcloud beta backup-dr backup-plan-associations describe + diff --git a/gcloud/backup-dr/backup-plan-associations/fetch-for-resource-type b/gcloud/backup-dr/backup-plan-associations/fetch-for-resource-type index ed336bfc9..394e5ddcd 100644 --- a/gcloud/backup-dr/backup-plan-associations/fetch-for-resource-type +++ b/gcloud/backup-dr/backup-plan-associations/fetch-for-resource-type @@ -78,8 +78,11 @@ BRIEF a project. NOTES - This variant is also available: + These variants are also available: $ gcloud alpha backup-dr backup-plan-associations \ fetch-for-resource-type + $ gcloud beta backup-dr backup-plan-associations \ + fetch-for-resource-type + diff --git a/gcloud/backup-dr/backup-plan-associations/help b/gcloud/backup-dr/backup-plan-associations/help index 8e5d52d87..f5af78183 100644 --- a/gcloud/backup-dr/backup-plan-associations/help +++ b/gcloud/backup-dr/backup-plan-associations/help @@ -38,7 +38,9 @@ COMMANDS Update a specific backup plan within a backup plan association. NOTES - This variant is also available: + These variants are also available: $ gcloud alpha backup-dr backup-plan-associations + $ gcloud beta backup-dr backup-plan-associations + diff --git a/gcloud/backup-dr/backup-plan-associations/list b/gcloud/backup-dr/backup-plan-associations/list index f9b4e8fd6..61f190f40 100644 --- a/gcloud/backup-dr/backup-plan-associations/list +++ b/gcloud/backup-dr/backup-plan-associations/list @@ -84,7 +84,9 @@ API REFERENCE can be found at: https://cloud.google.com/backup-disaster-recovery NOTES - This variant is also available: + These variants are also available: $ gcloud alpha backup-dr backup-plan-associations list + $ gcloud beta backup-dr backup-plan-associations list + diff --git a/gcloud/backup-dr/backup-plan-associations/trigger-backup b/gcloud/backup-dr/backup-plan-associations/trigger-backup index c2c1651ca..751db0dac 100644 --- a/gcloud/backup-dr/backup-plan-associations/trigger-backup +++ b/gcloud/backup-dr/backup-plan-associations/trigger-backup @@ -89,7 +89,9 @@ BRIEF Create an on-demand backup. NOTES - This variant is also available: + These variants are also available: $ gcloud alpha backup-dr backup-plan-associations trigger-backup + $ gcloud beta backup-dr backup-plan-associations trigger-backup + diff --git a/gcloud/backup-dr/backup-plan-associations/update b/gcloud/backup-dr/backup-plan-associations/update index 725d46310..c1eb50d16 100644 --- a/gcloud/backup-dr/backup-plan-associations/update +++ b/gcloud/backup-dr/backup-plan-associations/update @@ -121,7 +121,9 @@ BRIEF Update a specific backup plan within a backup plan association. NOTES - This variant is also available: + These variants are also available: $ gcloud alpha backup-dr backup-plan-associations update + $ gcloud beta backup-dr backup-plan-associations update + diff --git a/gcloud/backup-dr/backup-plan-revisions/describe b/gcloud/backup-dr/backup-plan-revisions/describe index a6dce4c66..4e86d45d5 100644 --- a/gcloud/backup-dr/backup-plan-revisions/describe +++ b/gcloud/backup-dr/backup-plan-revisions/describe @@ -69,7 +69,9 @@ API REFERENCE can be found at: https://cloud.google.com/backup-disaster-recovery NOTES - This variant is also available: + These variants are also available: $ gcloud alpha backup-dr backup-plan-revisions describe + $ gcloud beta backup-dr backup-plan-revisions describe + diff --git a/gcloud/backup-dr/backup-plan-revisions/help b/gcloud/backup-dr/backup-plan-revisions/help index 59ae1fb06..371abda0f 100644 --- a/gcloud/backup-dr/backup-plan-revisions/help +++ b/gcloud/backup-dr/backup-plan-revisions/help @@ -23,7 +23,9 @@ COMMANDS List backup plan revisions. NOTES - This variant is also available: + These variants are also available: $ gcloud alpha backup-dr backup-plan-revisions + $ gcloud beta backup-dr backup-plan-revisions + diff --git a/gcloud/backup-dr/backup-plan-revisions/list b/gcloud/backup-dr/backup-plan-revisions/list index a0263d01f..80d8e3ec9 100644 --- a/gcloud/backup-dr/backup-plan-revisions/list +++ b/gcloud/backup-dr/backup-plan-revisions/list @@ -102,7 +102,9 @@ API REFERENCE can be found at: https://cloud.google.com/backup-disaster-recovery NOTES - This variant is also available: + These variants are also available: $ gcloud alpha backup-dr backup-plan-revisions list + $ gcloud beta backup-dr backup-plan-revisions list + diff --git a/gcloud/backup-dr/backup-plans/create b/gcloud/backup-dr/backup-plans/create index b758e16cd..5af3b4d5c 100644 --- a/gcloud/backup-dr/backup-plans/create +++ b/gcloud/backup-dr/backup-plans/create @@ -4,8 +4,10 @@ NAME SYNOPSIS gcloud backup-dr backup-plans create (BACKUP_PLAN : --location=LOCATION) --backup-vault=BACKUP_VAULT --resource-type=RESOURCE_TYPE [--async] - [--backup-rule=[PROPERTY=VALUE,...]] [--description=DESCRIPTION] - [--disk-properties=[PROPERTY=VALUE,...]] [--labels=[KEY=VALUE,...]] + [--backup-rule=[PROPERTY=VALUE,...]] + [--compute-instance-properties=[PROPERTY=VALUE,...]] + [--description=DESCRIPTION] [--disk-properties=[PROPERTY=VALUE,...]] + [--labels=[KEY=VALUE,...]] [--max-custom-on-demand-retention-days=MAX_CUSTOM_ON_DEMAND_RETENTION_DAYS] [GCLOUD_WIDE_FLAG ...] @@ -230,6 +232,19 @@ OPTIONAL FLAGS "rule-id=sample-daily-rule,recurrence=WEEKLY,backup-window-start=2,backup-window-end=14,retention-days=20,days-of-week='SUNDAY MONDAY'" + --compute-instance-properties=[PROPERTY=VALUE,...] + Workload-specific properties for Compute Engine instance backups + generated by this plan. + + guest-flush + Indicates whether to perform a guest flush operation before taking + a compute backup. When set to true, the system will attempt to + ensure application-consistent backups. When set to false, the + system will create crash-consistent backups. Default value is + false. + + Example: --compute-instance-properties=guest-flush=true + --description=DESCRIPTION Provide a description of the backup plan, such as specific use cases and relevant details, in 2048 characters or less. @@ -274,7 +289,9 @@ BRIEF Creates a new backup plan NOTES - This variant is also available: + These variants are also available: $ gcloud alpha backup-dr backup-plans create + $ gcloud beta backup-dr backup-plans create + diff --git a/gcloud/backup-dr/backup-plans/delete b/gcloud/backup-dr/backup-plans/delete index 7d1823196..342e74ed4 100644 --- a/gcloud/backup-dr/backup-plans/delete +++ b/gcloud/backup-dr/backup-plans/delete @@ -65,7 +65,9 @@ BRIEF Deletes a specific backup plan NOTES - This variant is also available: + These variants are also available: $ gcloud alpha backup-dr backup-plans delete + $ gcloud beta backup-dr backup-plans delete + diff --git a/gcloud/backup-dr/backup-plans/describe b/gcloud/backup-dr/backup-plans/describe index 2f0b7165d..612a47aa0 100644 --- a/gcloud/backup-dr/backup-plans/describe +++ b/gcloud/backup-dr/backup-plans/describe @@ -58,7 +58,9 @@ API REFERENCE can be found at: https://cloud.google.com/backup-disaster-recovery NOTES - This variant is also available: + These variants are also available: $ gcloud alpha backup-dr backup-plans describe + $ gcloud beta backup-dr backup-plans describe + diff --git a/gcloud/backup-dr/backup-plans/help b/gcloud/backup-dr/backup-plans/help index 8e94ceaad..1781aa648 100644 --- a/gcloud/backup-dr/backup-plans/help +++ b/gcloud/backup-dr/backup-plans/help @@ -31,7 +31,9 @@ COMMANDS Update a specific backup plan. NOTES - This variant is also available: + These variants are also available: $ gcloud alpha backup-dr backup-plans + $ gcloud beta backup-dr backup-plans + diff --git a/gcloud/backup-dr/backup-plans/list b/gcloud/backup-dr/backup-plans/list index b562fac0b..5a1c7acaa 100644 --- a/gcloud/backup-dr/backup-plans/list +++ b/gcloud/backup-dr/backup-plans/list @@ -82,7 +82,9 @@ API REFERENCE can be found at: https://cloud.google.com/backup-disaster-recovery NOTES - This variant is also available: + These variants are also available: $ gcloud alpha backup-dr backup-plans list + $ gcloud beta backup-dr backup-plans list + diff --git a/gcloud/backup-dr/backup-plans/update b/gcloud/backup-dr/backup-plans/update index c4107ebd7..fbc1b93e0 100644 --- a/gcloud/backup-dr/backup-plans/update +++ b/gcloud/backup-dr/backup-plans/update @@ -5,8 +5,9 @@ SYNOPSIS gcloud backup-dr backup-plans update (BACKUP_PLAN : --location=LOCATION) [--add-backup-rule=[PROPERTY=VALUE,...]] [--async] [--backup-rule=[PROPERTY=VALUE,...]] - [--backup-rules-from-file=PATH_TO_FILE] [--description=DESCRIPTION] - [--disk-properties=[PROPERTY=VALUE,...]] + [--backup-rules-from-file=PATH_TO_FILE] + [--compute-instance-properties=[PROPERTY=VALUE,...]] + [--description=DESCRIPTION] [--disk-properties=[PROPERTY=VALUE,...]] [--max-custom-on-demand-retention-days=MAX_CUSTOM_ON_DEMAND_RETENTION_DAYS] [--remove-backup-rule=RULE-ID] [GCLOUD_WIDE_FLAG ...] @@ -260,6 +261,19 @@ FLAGS Path to a YAML or JSON file containing backup rules. Use a full or relative path to a local file containing the value of backup_rules. + --compute-instance-properties=[PROPERTY=VALUE,...] + Workload-specific properties for Compute Engine instance backups + generated by this plan. + + guest-flush + Indicates whether to perform a guest flush operation before taking + a compute backup. When set to true, the system will attempt to + ensure application-consistent backups. When set to false, the + system will create crash-consistent backups. Default value is + false. + + Example: --compute-instance-properties=guest-flush=true + --description=DESCRIPTION Provide a description of the backup plan, such as specific use cases and relevant details, in 2048 characters or less. @@ -299,7 +313,9 @@ BRIEF Update a specific backup plan NOTES - This variant is also available: + These variants are also available: $ gcloud alpha backup-dr backup-plans update + $ gcloud beta backup-dr backup-plans update + diff --git a/gcloud/backup-dr/backup-vaults/create b/gcloud/backup-dr/backup-vaults/create index 80d33f9fc..c3bd245ba 100644 --- a/gcloud/backup-dr/backup-vaults/create +++ b/gcloud/backup-dr/backup-vaults/create @@ -140,7 +140,9 @@ BRIEF Creates a Backup and DR backup vault. NOTES - This variant is also available: + These variants are also available: $ gcloud alpha backup-dr backup-vaults create + $ gcloud beta backup-dr backup-vaults create + diff --git a/gcloud/backup-dr/backup-vaults/delete b/gcloud/backup-dr/backup-vaults/delete index 2be671051..e171f69c7 100644 --- a/gcloud/backup-dr/backup-vaults/delete +++ b/gcloud/backup-dr/backup-vaults/delete @@ -96,7 +96,9 @@ BRIEF Deletes a specific backup vault NOTES - This variant is also available: + These variants are also available: $ gcloud alpha backup-dr backup-vaults delete + $ gcloud beta backup-dr backup-vaults delete + diff --git a/gcloud/backup-dr/backup-vaults/describe b/gcloud/backup-dr/backup-vaults/describe index 5715e5e76..9318d9fff 100644 --- a/gcloud/backup-dr/backup-vaults/describe +++ b/gcloud/backup-dr/backup-vaults/describe @@ -62,7 +62,9 @@ BRIEF Show the metadata for a Backup and DR backup vault. NOTES - This variant is also available: + These variants are also available: $ gcloud alpha backup-dr backup-vaults describe + $ gcloud beta backup-dr backup-vaults describe + diff --git a/gcloud/backup-dr/backup-vaults/help b/gcloud/backup-dr/backup-vaults/help index d08915843..c8386c593 100644 --- a/gcloud/backup-dr/backup-vaults/help +++ b/gcloud/backup-dr/backup-vaults/help @@ -31,7 +31,9 @@ COMMANDS Update a Backup and DR backup vault. NOTES - This variant is also available: + These variants are also available: $ gcloud alpha backup-dr backup-vaults + $ gcloud beta backup-dr backup-vaults + diff --git a/gcloud/backup-dr/backup-vaults/list b/gcloud/backup-dr/backup-vaults/list index 6f28a4d87..274e26327 100644 --- a/gcloud/backup-dr/backup-vaults/list +++ b/gcloud/backup-dr/backup-vaults/list @@ -85,7 +85,9 @@ BRIEF List Backup and DR backup vaults. NOTES - This variant is also available: + These variants are also available: $ gcloud alpha backup-dr backup-vaults list + $ gcloud beta backup-dr backup-vaults list + diff --git a/gcloud/backup-dr/backup-vaults/update b/gcloud/backup-dr/backup-vaults/update index 66ed46f74..a1de39f86 100644 --- a/gcloud/backup-dr/backup-vaults/update +++ b/gcloud/backup-dr/backup-vaults/update @@ -141,7 +141,9 @@ BRIEF Updates a Backup and DR backup vault. NOTES - This variant is also available: + These variants are also available: $ gcloud alpha backup-dr backup-vaults update + $ gcloud beta backup-dr backup-vaults update + diff --git a/gcloud/backup-dr/backups/delete b/gcloud/backup-dr/backups/delete index 3585dc74d..c670654a7 100644 --- a/gcloud/backup-dr/backups/delete +++ b/gcloud/backup-dr/backups/delete @@ -83,7 +83,9 @@ BRIEF Deletes a specific backup NOTES - This variant is also available: + These variants are also available: $ gcloud alpha backup-dr backups delete + $ gcloud beta backup-dr backups delete + diff --git a/gcloud/backup-dr/backups/describe b/gcloud/backup-dr/backups/describe index c751e8c92..56d37b465 100644 --- a/gcloud/backup-dr/backups/describe +++ b/gcloud/backup-dr/backups/describe @@ -74,7 +74,9 @@ API REFERENCE can be found at: https://cloud.google.com/backup-disaster-recovery NOTES - This variant is also available: + These variants are also available: $ gcloud alpha backup-dr backups describe + $ gcloud beta backup-dr backups describe + diff --git a/gcloud/backup-dr/backups/fetch-for-resource-type b/gcloud/backup-dr/backups/fetch-for-resource-type index 20f0ed818..9894bf89d 100644 --- a/gcloud/backup-dr/backups/fetch-for-resource-type +++ b/gcloud/backup-dr/backups/fetch-for-resource-type @@ -109,7 +109,9 @@ BRIEF List backups in a specified location and resource type in a project. NOTES - This variant is also available: + These variants are also available: $ gcloud alpha backup-dr backups fetch-for-resource-type + $ gcloud beta backup-dr backups fetch-for-resource-type + diff --git a/gcloud/backup-dr/backups/help b/gcloud/backup-dr/backups/help index c6eb38caf..4cc2731dc 100644 --- a/gcloud/backup-dr/backups/help +++ b/gcloud/backup-dr/backups/help @@ -37,7 +37,9 @@ COMMANDS Update the specified Backup. NOTES - This variant is also available: + These variants are also available: $ gcloud alpha backup-dr backups + $ gcloud beta backup-dr backups + diff --git a/gcloud/backup-dr/backups/list b/gcloud/backup-dr/backups/list index db134ef13..b84648b13 100644 --- a/gcloud/backup-dr/backups/list +++ b/gcloud/backup-dr/backups/list @@ -107,7 +107,9 @@ API REFERENCE can be found at: https://cloud.google.com/backup-disaster-recovery NOTES - This variant is also available: + These variants are also available: $ gcloud alpha backup-dr backups list + $ gcloud beta backup-dr backups list + diff --git a/gcloud/backup-dr/backups/restore/compute b/gcloud/backup-dr/backups/restore/compute index d3853a52e..11fc2e72a 100644 --- a/gcloud/backup-dr/backups/restore/compute +++ b/gcloud/backup-dr/backups/restore/compute @@ -425,7 +425,9 @@ BRIEF Restores the specified backup NOTES - This variant is also available: + These variants are also available: $ gcloud alpha backup-dr backups restore compute + $ gcloud beta backup-dr backups restore compute + diff --git a/gcloud/backup-dr/backups/restore/disk b/gcloud/backup-dr/backups/restore/disk index 726c55d26..c18a3b1ff 100644 --- a/gcloud/backup-dr/backups/restore/disk +++ b/gcloud/backup-dr/backups/restore/disk @@ -212,7 +212,9 @@ BRIEF Restores the specified backup NOTES - This variant is also available: + These variants are also available: $ gcloud alpha backup-dr backups restore disk + $ gcloud beta backup-dr backups restore disk + diff --git a/gcloud/backup-dr/backups/restore/help b/gcloud/backup-dr/backups/restore/help index 0cbb44908..30d97a2cf 100644 --- a/gcloud/backup-dr/backups/restore/help +++ b/gcloud/backup-dr/backups/restore/help @@ -22,7 +22,9 @@ COMMANDS Restores a Compute Disk Backup. NOTES - This variant is also available: + These variants are also available: $ gcloud alpha backup-dr backups restore + $ gcloud beta backup-dr backups restore + diff --git a/gcloud/backup-dr/backups/update b/gcloud/backup-dr/backups/update index 8264bcfe4..5d90b0b1b 100644 --- a/gcloud/backup-dr/backups/update +++ b/gcloud/backup-dr/backups/update @@ -143,7 +143,9 @@ BRIEF Updates a specific backup NOTES - This variant is also available: + These variants are also available: $ gcloud alpha backup-dr backups update + $ gcloud beta backup-dr backups update + diff --git a/gcloud/backup-dr/data-source-references/describe b/gcloud/backup-dr/data-source-references/describe index d4bfc0cd2..bc56651bd 100644 --- a/gcloud/backup-dr/data-source-references/describe +++ b/gcloud/backup-dr/data-source-references/describe @@ -61,7 +61,9 @@ API REFERENCE can be found at: https://cloud.google.com/backup-disaster-recovery NOTES - This variant is also available: + These variants are also available: $ gcloud alpha backup-dr data-source-references describe + $ gcloud beta backup-dr data-source-references describe + diff --git a/gcloud/backup-dr/data-source-references/fetch-for-resource-type b/gcloud/backup-dr/data-source-references/fetch-for-resource-type index ae8bb56f9..3471d3e0c 100644 --- a/gcloud/backup-dr/data-source-references/fetch-for-resource-type +++ b/gcloud/backup-dr/data-source-references/fetch-for-resource-type @@ -73,8 +73,11 @@ BRIEF project. NOTES - This variant is also available: + These variants are also available: $ gcloud alpha backup-dr data-source-references \ fetch-for-resource-type + $ gcloud beta backup-dr data-source-references \ + fetch-for-resource-type + diff --git a/gcloud/backup-dr/data-source-references/help b/gcloud/backup-dr/data-source-references/help index 335fbf487..c3039a336 100644 --- a/gcloud/backup-dr/data-source-references/help +++ b/gcloud/backup-dr/data-source-references/help @@ -26,7 +26,9 @@ COMMANDS List Backup and DR data source references. NOTES - This variant is also available: + These variants are also available: $ gcloud alpha backup-dr data-source-references + $ gcloud beta backup-dr data-source-references + diff --git a/gcloud/backup-dr/data-source-references/list b/gcloud/backup-dr/data-source-references/list index 0eef26e44..87c7a814f 100644 --- a/gcloud/backup-dr/data-source-references/list +++ b/gcloud/backup-dr/data-source-references/list @@ -83,7 +83,9 @@ API REFERENCE can be found at: https://cloud.google.com/backup-disaster-recovery NOTES - This variant is also available: + These variants are also available: $ gcloud alpha backup-dr data-source-references list + $ gcloud beta backup-dr data-source-references list + diff --git a/gcloud/backup-dr/data-sources/describe b/gcloud/backup-dr/data-sources/describe index b5baaf07a..a12fe4991 100644 --- a/gcloud/backup-dr/data-sources/describe +++ b/gcloud/backup-dr/data-sources/describe @@ -67,7 +67,9 @@ API REFERENCE can be found at: https://cloud.google.com/backup-disaster-recovery NOTES - This variant is also available: + These variants are also available: $ gcloud alpha backup-dr data-sources describe + $ gcloud beta backup-dr data-sources describe + diff --git a/gcloud/backup-dr/data-sources/help b/gcloud/backup-dr/data-sources/help index 74ea94ac5..2621eb903 100644 --- a/gcloud/backup-dr/data-sources/help +++ b/gcloud/backup-dr/data-sources/help @@ -22,7 +22,9 @@ COMMANDS List Data Sources. NOTES - This variant is also available: + These variants are also available: $ gcloud alpha backup-dr data-sources + $ gcloud beta backup-dr data-sources + diff --git a/gcloud/backup-dr/data-sources/list b/gcloud/backup-dr/data-sources/list index 0f824fe46..773556bc5 100644 --- a/gcloud/backup-dr/data-sources/list +++ b/gcloud/backup-dr/data-sources/list @@ -97,7 +97,9 @@ API REFERENCE can be found at: https://cloud.google.com/backup-disaster-recovery NOTES - This variant is also available: + These variants are also available: $ gcloud alpha backup-dr data-sources list + $ gcloud beta backup-dr data-sources list + diff --git a/gcloud/backup-dr/resource-backup-config/help b/gcloud/backup-dr/resource-backup-config/help index aa4cb216f..da4bd095d 100644 --- a/gcloud/backup-dr/resource-backup-config/help +++ b/gcloud/backup-dr/resource-backup-config/help @@ -21,7 +21,9 @@ COMMANDS in a particular location for the project. NOTES - This variant is also available: + These variants are also available: $ gcloud alpha backup-dr resource-backup-config + $ gcloud beta backup-dr resource-backup-config + diff --git a/gcloud/backup-dr/resource-backup-config/list b/gcloud/backup-dr/resource-backup-config/list index 8176bfbed..680db83f9 100644 --- a/gcloud/backup-dr/resource-backup-config/list +++ b/gcloud/backup-dr/resource-backup-config/list @@ -135,7 +135,9 @@ SUBARGUMENTS ▪ BACKUPDR_TEMPLATE NOTES - This variant is also available: + These variants are also available: $ gcloud alpha backup-dr resource-backup-config list + $ gcloud beta backup-dr resource-backup-config list + diff --git a/gcloud/backup-dr/service-config/help b/gcloud/backup-dr/service-config/help index cd436d899..7d5fe5ced 100644 --- a/gcloud/backup-dr/service-config/help +++ b/gcloud/backup-dr/service-config/help @@ -20,7 +20,9 @@ COMMANDS Initialize a Backup and DR Service configuration. NOTES - This variant is also available: + These variants are also available: $ gcloud alpha backup-dr service-config + $ gcloud beta backup-dr service-config + diff --git a/gcloud/backup-dr/service-config/init b/gcloud/backup-dr/service-config/init index 0a82697ea..e5f1809ec 100644 --- a/gcloud/backup-dr/service-config/init +++ b/gcloud/backup-dr/service-config/init @@ -67,7 +67,9 @@ BRIEF Initializes a Backup and DR Service configuration. NOTES - This variant is also available: + These variants are also available: $ gcloud alpha backup-dr service-config init + $ gcloud beta backup-dr service-config init + diff --git a/gcloud/beta/ai/help b/gcloud/beta/ai/help index 6988d6307..70260360a 100644 --- a/gcloud/beta/ai/help +++ b/gcloud/beta/ai/help @@ -45,6 +45,12 @@ GROUPS persistent-resources (BETA) Create and manage Vertex AI rersistent resources. + semantic-governance-policies + (BETA) Manage Vertex AI Semantic Governance Policy resources. + + semantic-governance-policy-engine + (BETA) Manage Vertex AI Semantic Governance Policy engine. + tensorboard-experiments (BETA) Manage Vertex AI Tensorboard experiments. diff --git a/gcloud/beta/ai/model-garden/models/deploy b/gcloud/beta/ai/model-garden/models/deploy index cb05fb3ec..52505e317 100644 --- a/gcloud/beta/ai/model-garden/models/deploy +++ b/gcloud/beta/ai/model-garden/models/deploy @@ -27,8 +27,8 @@ SYNOPSIS [--machine-type=MACHINE_TYPE] [--region=REGION] [--reservation-affinity=[key=KEY], [reservation-affinity-type=RESERVATION-AFFINITY-TYPE], - [values=VALUES]] [--spot] [--use-dedicated-endpoint] - [GCLOUD_WIDE_FLAG ...] + [values=VALUES]] [--spot] [--system-labels=[KEY=VALUE,...]] + [--use-dedicated-endpoint] [GCLOUD_WIDE_FLAG ...] EXAMPLES To deploy a Model Garden model google/gemma2/gemma2-9b under project @@ -188,6 +188,9 @@ OPTIONAL FLAGS --spot If true, schedule the deployment workload on Spot VM. + --system-labels=[KEY=VALUE,...] + System labels for Model Garden deployments. + --use-dedicated-endpoint If true, the endpoint will be exposed through a dedicated DNS. Your request to the dedicated DNS will be isolated from other users' traffic diff --git a/gcloud/beta/ai/semantic-governance-policies/create b/gcloud/beta/ai/semantic-governance-policies/create new file mode 100644 index 000000000..bdbc9f842 --- /dev/null +++ b/gcloud/beta/ai/semantic-governance-policies/create @@ -0,0 +1,92 @@ +NAME + gcloud beta ai semantic-governance-policies create - create a new semantic + governance policy + +SYNOPSIS + gcloud beta ai semantic-governance-policies create + (POLICY : --location=LOCATION) --agent=AGENT + --display-name=DISPLAY_NAME + --natural-language-constraint=NATURAL_LANGUAGE_CONSTRAINT [--async] + [--description=DESCRIPTION] [--mcp-tools=MCP_TOOLS] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Create a new semantic governance policy. + +EXAMPLES + To create a semantic governance policy my-policy in location us-central1, + run: + + $ gcloud beta ai semantic-governance-policies create my-policy \ + --location=us-central1 --display-name="My Policy" \ + --natural-language-constraint="constraint" --agent="agent-name" + +POSITIONAL ARGUMENTS + Policy resource - The semantic governance policy 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 policy on the command line with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + POLICY + ID of the policy or fully qualified identifier for the policy. + + To set the policy attribute: + ▸ provide the argument policy 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 to create the policy in. + + To set the location attribute: + ▸ provide the argument policy on the command line with a fully + specified name; + ▸ provide the argument --location on the command line. + +REQUIRED FLAGS + --agent=AGENT + The name of the agent in Agent Registry that is affected by this + policy. + + --display-name=DISPLAY_NAME + The user-defined name of the semantic governance policy. + + --natural-language-constraint=NATURAL_LANGUAGE_CONSTRAINT + The natural language constraint of the semantic governance policy. + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --description=DESCRIPTION + The description of the semantic governance policy. + + --mcp-tools=MCP_TOOLS + The MCP tools that are affected by this policy. Syntax: + --mcp-tools=mcp-server=S1,tools=T1;T2 + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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 aiplatform/v1beta1 API. The full documentation for + this API can be found at: https://cloud.google.com/vertex-ai/ + +NOTES + This command is currently in beta and might change without notice. + diff --git a/gcloud/beta/ai/semantic-governance-policies/delete b/gcloud/beta/ai/semantic-governance-policies/delete new file mode 100644 index 000000000..2ac342343 --- /dev/null +++ b/gcloud/beta/ai/semantic-governance-policies/delete @@ -0,0 +1,77 @@ +NAME + gcloud beta ai semantic-governance-policies delete - delete a semantic + governance policy + +SYNOPSIS + gcloud beta ai semantic-governance-policies delete + (POLICY : --location=LOCATION) [--async] [--etag=ETAG] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Delete a semantic governance policy. + +EXAMPLES + To delete a semantic governance policy my-policy in location us-central1, + run: + + $ gcloud beta ai semantic-governance-policies delete my-policy \ + --location=us-central1 + +POSITIONAL ARGUMENTS + Policy resource - The semantic governance policy 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 policy on the command line with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + POLICY + ID of the policy or fully qualified identifier for the policy. + + To set the policy attribute: + ▸ provide the argument policy 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 containing the policy. + + To set the location attribute: + ▸ provide the argument policy 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. + + --etag=ETAG + The etag of the SemanticGovernancePolicy to delete. + + If an etag is provided and does not match the current etag of the + SemanticGovernancePolicy, deletion will be blocked and an ABORTED error + will be returned. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the aiplatform/v1beta1 API. The full documentation for + this API can be found at: https://cloud.google.com/vertex-ai/ + +NOTES + This command is currently in beta and might change without notice. + diff --git a/gcloud/beta/ai/semantic-governance-policies/describe b/gcloud/beta/ai/semantic-governance-policies/describe new file mode 100644 index 000000000..0081bc2d1 --- /dev/null +++ b/gcloud/beta/ai/semantic-governance-policies/describe @@ -0,0 +1,64 @@ +NAME + gcloud beta ai semantic-governance-policies describe - describe a semantic + governance policy + +SYNOPSIS + gcloud beta ai semantic-governance-policies describe + (POLICY : --location=LOCATION) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Describe a semantic governance policy. + +EXAMPLES + To describe a semantic governance policy my-policy in location us-central1, + run: + + $ gcloud beta ai semantic-governance-policies describe my-policy \ + --location=us-central1 + +POSITIONAL ARGUMENTS + Policy resource - The semantic governance policy 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 policy on the command line with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + POLICY + ID of the policy or fully qualified identifier for the policy. + + To set the policy attribute: + ▸ provide the argument policy 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 containing the policy. + + To set the location attribute: + ▸ provide the argument policy 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 aiplatform/v1beta1 API. The full documentation for + this API can be found at: https://cloud.google.com/vertex-ai/ + +NOTES + This command is currently in beta and might change without notice. + diff --git a/gcloud/beta/ai/semantic-governance-policies/help b/gcloud/beta/ai/semantic-governance-policies/help new file mode 100644 index 000000000..bbc447cf5 --- /dev/null +++ b/gcloud/beta/ai/semantic-governance-policies/help @@ -0,0 +1,36 @@ +NAME + gcloud beta ai semantic-governance-policies - manage Vertex AI Semantic + Governance Policy resources + +SYNOPSIS + gcloud beta ai semantic-governance-policies COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Manage Vertex AI Semantic Governance Policy 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 + (BETA) Create a new semantic governance policy. + + delete + (BETA) Delete a semantic governance policy. + + describe + (BETA) Describe a semantic governance policy. + + list + (BETA) List semantic governance policies. + + update + (BETA) Update a semantic governance policy. + +NOTES + This command is currently in beta and might change without notice. + diff --git a/gcloud/beta/ai/semantic-governance-policies/list b/gcloud/beta/ai/semantic-governance-policies/list new file mode 100644 index 000000000..8073de627 --- /dev/null +++ b/gcloud/beta/ai/semantic-governance-policies/list @@ -0,0 +1,78 @@ +NAME + gcloud beta ai semantic-governance-policies list - list semantic governance + policies + +SYNOPSIS + gcloud beta ai semantic-governance-policies list --location=LOCATION + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) List semantic governance policies. + +EXAMPLES + To list semantic governance policies in location us-central1, run: + + $ gcloud beta ai semantic-governance-policies list \ + --location=us-central1 + +REQUIRED FLAGS + Location resource - The location of the policies to list. This represents + a Cloud resource. (NOTE) Some attributes are not given arguments in this + group but can be set in other ways. + + To set the project attribute: + ◆ provide the argument --location on the command line with a fully + specified name; + ◆ 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. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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 aiplatform/v1beta1 API. The full documentation for + this API can be found at: https://cloud.google.com/vertex-ai/ + +NOTES + This command is currently in beta and might change without notice. + diff --git a/gcloud/beta/ai/semantic-governance-policies/update b/gcloud/beta/ai/semantic-governance-policies/update new file mode 100644 index 000000000..cb961a322 --- /dev/null +++ b/gcloud/beta/ai/semantic-governance-policies/update @@ -0,0 +1,95 @@ +NAME + gcloud beta ai semantic-governance-policies update - update a semantic + governance policy + +SYNOPSIS + gcloud beta ai semantic-governance-policies update + (POLICY : --location=LOCATION) [--agent=AGENT] [--async] + [--description=DESCRIPTION] [--display-name=DISPLAY_NAME] [--etag=ETAG] + [--mcp-tools=MCP_TOOLS] + [--natural-language-constraint=NATURAL_LANGUAGE_CONSTRAINT] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Update a semantic governance policy. + +EXAMPLES + To update the display name of a semantic governance policy my-policy in + location us-central1, run: + + $ gcloud beta ai semantic-governance-policies update my-policy \ + --location=us-central1 --display-name="New display name" + +POSITIONAL ARGUMENTS + Policy resource - The semantic governance policy 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 policy on the command line with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + POLICY + ID of the policy or fully qualified identifier for the policy. + + To set the policy attribute: + ▸ provide the argument policy 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 to update the policy in. + + To set the location attribute: + ▸ provide the argument policy on the command line with a fully + specified name; + ▸ provide the argument --location on the command line. + +FLAGS + --agent=AGENT + The name of the agent in Agent Registry that is affected by this + policy. + + --async + Return immediately, without waiting for the operation in progress to + complete. + + --description=DESCRIPTION + The description of the semantic governance policy. + + --display-name=DISPLAY_NAME + The user-defined name of the semantic governance policy. + + --etag=ETAG + The etag of the semantic governance policy. If an etag is provided and + does not match the current etag of the SemanticGovernancePolicy, update + will be blocked and an ABORTED error will be returned. + + --mcp-tools=MCP_TOOLS + The MCP tools that are affected by this policy. Syntax: + --mcp-tools=mcp-server=S1,tools=T1;T2 + + --natural-language-constraint=NATURAL_LANGUAGE_CONSTRAINT + The natural language constraint of the semantic governance policy. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the aiplatform/v1beta1 API. The full documentation for + this API can be found at: https://cloud.google.com/vertex-ai/ + +NOTES + This command is currently in beta and might change without notice. + diff --git a/gcloud/beta/ai/semantic-governance-policy-engine/describe b/gcloud/beta/ai/semantic-governance-policy-engine/describe new file mode 100644 index 000000000..7b33eecd0 --- /dev/null +++ b/gcloud/beta/ai/semantic-governance-policy-engine/describe @@ -0,0 +1,37 @@ +NAME + gcloud beta ai semantic-governance-policy-engine describe - describe the + semantic governance policy engine config + +SYNOPSIS + gcloud beta ai semantic-governance-policy-engine describe + --location=LOCATION [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Describe the semantic governance policy engine config. + +EXAMPLES + To describe the semantic governance policy engine config in location + us-central1, run: + + $ gcloud beta ai semantic-governance-policy-engine describe \ + --location=us-central1 + +REQUIRED FLAGS + --location=LOCATION + Cloud location of the semantic governance policy engine. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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 aiplatform/v1beta1 API. The full documentation for + this API can be found at: https://cloud.google.com/vertex-ai/ + +NOTES + This command is currently in beta and might change without notice. + diff --git a/gcloud/beta/ai/semantic-governance-policy-engine/help b/gcloud/beta/ai/semantic-governance-policy-engine/help new file mode 100644 index 000000000..afc6d8ff9 --- /dev/null +++ b/gcloud/beta/ai/semantic-governance-policy-engine/help @@ -0,0 +1,28 @@ +NAME + gcloud beta ai semantic-governance-policy-engine - manage Vertex AI + Semantic Governance Policy engine + +SYNOPSIS + gcloud beta ai semantic-governance-policy-engine COMMAND + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Manage Vertex AI Semantic Governance Policy engine. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + describe + (BETA) Describe the semantic governance policy engine config. + + update + (BETA) Update the semantic governance policy engine config. + +NOTES + This command is currently in beta and might change without notice. + diff --git a/gcloud/beta/ai/semantic-governance-policy-engine/update b/gcloud/beta/ai/semantic-governance-policy-engine/update new file mode 100644 index 000000000..533687625 --- /dev/null +++ b/gcloud/beta/ai/semantic-governance-policy-engine/update @@ -0,0 +1,55 @@ +NAME + gcloud beta ai semantic-governance-policy-engine update - update the + semantic governance policy engine config + +SYNOPSIS + gcloud beta ai semantic-governance-policy-engine update --location=LOCATION + [--async] [--gateway-config=GATEWAY_CONFIG] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Update the semantic governance policy engine config. + +REQUIRED FLAGS + Location resource - The semantic governance policy engine config. 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. + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --gateway-config=GATEWAY_CONFIG + Configuration for a single gateway. The value is a comma-separated list + of key-value pairs. For example: + name=mygateway,network=net,subnetwork=subnet,dns-zone-name=dns + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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 aiplatform/v1beta1 API. The full documentation for + this API can be found at: https://cloud.google.com/vertex-ai/ + +NOTES + This command is currently in beta and might change without notice. + diff --git a/gcloud/beta/alloydb/clusters/create b/gcloud/beta/alloydb/clusters/create index ab2e4b220..202630cbb 100644 --- a/gcloud/beta/alloydb/clusters/create +++ b/gcloud/beta/alloydb/clusters/create @@ -5,7 +5,8 @@ NAME SYNOPSIS gcloud beta alloydb clusters create CLUSTER --password=PASSWORD --region=REGION [--allocated-ip-range-name=ALLOCATED_IP_RANGE_NAME] - [--async] [--database-version=DATABASE_VERSION] + [--async] [--backupdr-backup-plan=BACKUPDR_BACKUP_PLAN] + [--database-version=DATABASE_VERSION] [--[no-]enable-dataplex-integration] [--enable-private-service-connect] [--network=NETWORK] [--subscription-type=SUBSCRIPTION_TYPE] [--tags=[KEY=VALUE,...]] @@ -61,6 +62,12 @@ OPTIONAL FLAGS Return immediately, without waiting for the operation in progress to complete. + --backupdr-backup-plan=BACKUPDR_BACKUP_PLAN + The resource name of the BackupDR backup plan to associate with the + cluster. The format should be + projects/{project}/locations/{location}/backupPlans/{backupPlanId}. + This flag cannot be used with the --async flag. + --database-version=DATABASE_VERSION Database version of the cluster. DATABASE_VERSION must be one of: POSTGRES_14, POSTGRES_15, POSTGRES_16, POSTGRES_17, POSTGRES_18. diff --git a/gcloud/beta/alloydb/clusters/promote b/gcloud/beta/alloydb/clusters/promote index eea5203df..c1d2b184f 100644 --- a/gcloud/beta/alloydb/clusters/promote +++ b/gcloud/beta/alloydb/clusters/promote @@ -4,7 +4,7 @@ NAME SYNOPSIS gcloud beta alloydb clusters promote CLUSTER --region=REGION [--async] - [--failover] [GCLOUD_WIDE_FLAG ...] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) Promote an AlloyDB SECONDARY cluster in a given project and region. @@ -29,12 +29,6 @@ OPTIONAL FLAGS Return immediately, without waiting for the operation in progress to complete. - --failover - If set, the promote operation will attempt to recreate the original - primary cluster as a secondary cluster when it comes back online. - Otherwise, the promoted cluster will be a standalone cluster. Currently - only supported when there is a single secondary cluster. - GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, diff --git a/gcloud/beta/alloydb/instances/create b/gcloud/beta/alloydb/instances/create index 8387994a5..47e2a7890 100644 --- a/gcloud/beta/alloydb/instances/create +++ b/gcloud/beta/alloydb/instances/create @@ -28,13 +28,16 @@ SYNOPSIS [--insights-config-query-string-length=INSIGHTS_CONFIG_QUERY_STRING_LENGTH] [--[no-]insights-config-record-application-tags] [--[no-]insights-config-record-client-address] - [--machine-type=MACHINE_TYPE] [--[no-]observability-config-enabled] + [--machine-type=MACHINE_TYPE] + [--[no-]observability-config-assistive-experiences-enabled] + [--[no-]observability-config-enabled] [--observability-config-max-query-string-length=OBSERVABILITY_CONFIG_MAX_QUERY_STRING_LENGTH] [--[no-]observability-config-preserve-comments] [--observability-config-query-plans-per-minute=OBSERVABILITY_CONFIG_QUERY_PLANS_PER_MINUTE] [--[no-]observability-config-record-application-tags] [--[no-]observability-config-track-active-queries] [--[no-]observability-config-track-active-query-plan] + [--[no-]observability-config-track-client-address] [--observability-config-track-wait-events] [--[no-]outbound-public-ip] [--psc-auto-connections=[network=NETWORK],[project=PROJECT]] [--psc-network-attachment-uri=PSC_NETWORK_ATTACHMENT_URI] @@ -235,6 +238,11 @@ OPTIONAL FLAGS z3-highmem-8-highlssd, z3-highmem-16-highlssd, z3-highmem-22-highlssd, z3-highmem-32-highlssd, z3-highmem-44-highlssd. + --[no-]observability-config-assistive-experiences-enabled + Enable assistive experiences to monitor, troubleshoot and recommend. + Use --observability-config-assistive-experiences-enabled to enable and + --no-observability-config-assistive-experiences-enabled to disable. + --[no-]observability-config-enabled Enable enhanced query insights feature. Use --observability-config-enabled to enable and @@ -252,7 +260,7 @@ OPTIONAL FLAGS --no-observability-config-preserve-comments to disable. --observability-config-query-plans-per-minute=OBSERVABILITY_CONFIG_QUERY_PLANS_PER_MINUTE - Number of query plans to sample every minute. Default value is 200. + Number of query plans to sample every minute. Default value is 20. Allowed range: 0 to 200. --[no-]observability-config-record-application-tags @@ -272,6 +280,11 @@ OPTIONAL FLAGS --observability-config-track-active-query-plan to enable and --no-observability-config-track-active-query-plan to disable. + --[no-]observability-config-track-client-address + Enable tracking of client address in query insights. Use + --observability-config-track-client-address to enable and + --no-observability-config-track-client-address to disable. + --observability-config-track-wait-events Track wait events during query execution. diff --git a/gcloud/beta/alloydb/instances/update b/gcloud/beta/alloydb/instances/update index c29d0aa1e..b04ddfd1a 100644 --- a/gcloud/beta/alloydb/instances/update +++ b/gcloud/beta/alloydb/instances/update @@ -28,13 +28,16 @@ SYNOPSIS [--insights-config-query-string-length=INSIGHTS_CONFIG_QUERY_STRING_LENGTH] [--[no-]insights-config-record-application-tags] [--[no-]insights-config-record-client-address] - [--machine-type=MACHINE_TYPE] [--[no-]observability-config-enabled] + [--machine-type=MACHINE_TYPE] + [--[no-]observability-config-assistive-experiences-enabled] + [--[no-]observability-config-enabled] [--observability-config-max-query-string-length=OBSERVABILITY_CONFIG_MAX_QUERY_STRING_LENGTH] [--[no-]observability-config-preserve-comments] [--observability-config-query-plans-per-minute=OBSERVABILITY_CONFIG_QUERY_PLANS_PER_MINUTE] [--[no-]observability-config-record-application-tags] [--[no-]observability-config-track-active-queries] [--[no-]observability-config-track-active-query-plan] + [--[no-]observability-config-track-client-address] [--observability-config-track-wait-events] [--[no-]outbound-public-ip] [--psc-network-attachment-uri=PSC_NETWORK_ATTACHMENT_URI] [--read-pool-node-count=READ_POOL_NODE_COUNT] @@ -221,6 +224,11 @@ OPTIONAL FLAGS z3-highmem-8-highlssd, z3-highmem-16-highlssd, z3-highmem-22-highlssd, z3-highmem-32-highlssd, z3-highmem-44-highlssd. + --[no-]observability-config-assistive-experiences-enabled + Enable assistive experiences to monitor, troubleshoot and recommend. + Use --observability-config-assistive-experiences-enabled to enable and + --no-observability-config-assistive-experiences-enabled to disable. + --[no-]observability-config-enabled Enable enhanced query insights feature. Use --observability-config-enabled to enable and @@ -238,7 +246,7 @@ OPTIONAL FLAGS --no-observability-config-preserve-comments to disable. --observability-config-query-plans-per-minute=OBSERVABILITY_CONFIG_QUERY_PLANS_PER_MINUTE - Number of query plans to sample every minute. Default value is 200. + Number of query plans to sample every minute. Default value is 20. Allowed range: 0 to 200. --[no-]observability-config-record-application-tags @@ -258,6 +266,11 @@ OPTIONAL FLAGS --observability-config-track-active-query-plan to enable and --no-observability-config-track-active-query-plan to disable. + --[no-]observability-config-track-client-address + Enable tracking of client address in query insights. Use + --observability-config-track-client-address to enable and + --no-observability-config-track-client-address to disable. + --observability-config-track-wait-events Track wait events during query execution. diff --git a/gcloud/beta/alloydb/users/create b/gcloud/beta/alloydb/users/create index 64019c315..63b2a677e 100644 --- a/gcloud/beta/alloydb/users/create +++ b/gcloud/beta/alloydb/users/create @@ -52,6 +52,9 @@ OPTIONAL FLAGS authentication IAM_BASED This database user can authenticate via IAM-based authentication + IAM_GROUP + This database user represents an IAM group whose members can + authenticate via IAM group-based authentication GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/beta/api-registry/help b/gcloud/beta/api-registry/help index 207c49671..9a3230e96 100644 --- a/gcloud/beta/api-registry/help +++ b/gcloud/beta/api-registry/help @@ -16,7 +16,7 @@ GROUPS GROUP is one of the following: mcp - (BETA) Manage MCP Command Group. + (BETA) (DEPRECATED) Manage MCP Command Group. NOTES This command is currently in beta and might change without notice. This diff --git a/gcloud/beta/api-registry/mcp/disable b/gcloud/beta/api-registry/mcp/disable index f774d6cfb..d04dfb9d8 100644 --- a/gcloud/beta/api-registry/mcp/disable +++ b/gcloud/beta/api-registry/mcp/disable @@ -6,7 +6,11 @@ SYNOPSIS gcloud beta api-registry mcp disable SERVICE [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) Disables MCP server for a given service in the current project. + (BETA) (DEPRECATED) Disables MCP server for a given service in the current + project. + + The gcloud beta api-registry mcp disable command is deprecated and will be + removed in a future release. POSITIONAL ARGUMENTS SERVICE diff --git a/gcloud/beta/api-registry/mcp/enable b/gcloud/beta/api-registry/mcp/enable index e1609dd35..854561690 100644 --- a/gcloud/beta/api-registry/mcp/enable +++ b/gcloud/beta/api-registry/mcp/enable @@ -6,7 +6,11 @@ SYNOPSIS gcloud beta api-registry mcp enable SERVICE [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) Enables MCP server for a given service in the current project. + (BETA) (DEPRECATED) Enables MCP server for a given service in the current + project. + + The gcloud beta api-registry mcp enable command is deprecated and will be + removed in a future release. POSITIONAL ARGUMENTS SERVICE diff --git a/gcloud/beta/api-registry/mcp/help b/gcloud/beta/api-registry/mcp/help index 994742a4f..93636e380 100644 --- a/gcloud/beta/api-registry/mcp/help +++ b/gcloud/beta/api-registry/mcp/help @@ -5,8 +5,12 @@ SYNOPSIS gcloud beta api-registry mcp GROUP | COMMAND [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) Commands for managing MCP enablement and disablement for a given - service in the current project. + (BETA) (DEPRECATED) Manage MCP Command Group. + + This command is deprecated. + + Commands for managing MCP enablement and disablement for a given service in + the current project. GCLOUD WIDE FLAGS These flags are available to all commands: --help. @@ -17,19 +21,21 @@ GROUPS GROUP is one of the following: servers - (BETA) Manage Cloud API Registry MCP servers. + (BETA) (DEPRECATED) Manage Cloud API Registry MCP servers. tools - (BETA) Manage Cloud API Registry MCP tools. + (BETA) (DEPRECATED) Manage Cloud API Registry MCP tools. COMMANDS COMMAND is one of the following: disable - (BETA) Disables MCP server for a given service in the current project. + (BETA) (DEPRECATED) Disables MCP server for a given service in the + current project. enable - (BETA) Enables MCP server for a given service in the current project. + (BETA) (DEPRECATED) Enables MCP server for a given service in the + current project. NOTES This command is currently in beta and might change without notice. This diff --git a/gcloud/beta/api-registry/mcp/servers/help b/gcloud/beta/api-registry/mcp/servers/help index 119048a81..b1d628934 100644 --- a/gcloud/beta/api-registry/mcp/servers/help +++ b/gcloud/beta/api-registry/mcp/servers/help @@ -6,7 +6,9 @@ SYNOPSIS gcloud beta api-registry mcp servers COMMAND [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) Manage Cloud API Registry MCP servers. + (BETA) (DEPRECATED) Manage Cloud API Registry MCP servers. + + This command is deprecated. GCLOUD WIDE FLAGS These flags are available to all commands: --help. @@ -17,7 +19,7 @@ COMMANDS COMMAND is one of the following: list - (BETA) List MCP servers. + (BETA) (DEPRECATED) List MCP servers. NOTES This command is currently in beta and might change without notice. This diff --git a/gcloud/beta/api-registry/mcp/servers/list b/gcloud/beta/api-registry/mcp/servers/list index bc662a97c..2995f1e21 100644 --- a/gcloud/beta/api-registry/mcp/servers/list +++ b/gcloud/beta/api-registry/mcp/servers/list @@ -7,7 +7,20 @@ SYNOPSIS [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) List MCP servers. + (BETA) (DEPRECATED) The gcloud beta api-registry mcp servers list command + is deprecated and will be removed in a future release. Please use gcloud + alpha agent-registry mcp-servers list instead. Note: Agent Registry only + lists MCP servers for service APIs that are enabled in a project. For more + information, see: + https://docs.cloud.google.com/sdk/gcloud/reference/alpha/agent-registry/mcp-servers + + (BETA) (DEPRECATED) List MCP servers. + + The gcloud beta api-registry mcp servers list command is deprecated and + will be removed in a future release. Please use gcloud alpha agent-registry + mcp-servers list instead. Note: Agent Registry only lists MCP servers for + service APIs that are enabled in a project. For more information, see: + https://docs.cloud.google.com/sdk/gcloud/reference/alpha/agent-registry/mcp-servers EXAMPLES To list all MCP servers in a project, run: diff --git a/gcloud/beta/api-registry/mcp/tools/help b/gcloud/beta/api-registry/mcp/tools/help index cd6fc958c..347b9f2bc 100644 --- a/gcloud/beta/api-registry/mcp/tools/help +++ b/gcloud/beta/api-registry/mcp/tools/help @@ -5,7 +5,9 @@ SYNOPSIS gcloud beta api-registry mcp tools COMMAND [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) Manage Cloud API Registry MCP tools. + (BETA) (DEPRECATED) Manage Cloud API Registry MCP tools. + + This command is deprecated. GCLOUD WIDE FLAGS These flags are available to all commands: --help. @@ -16,7 +18,7 @@ COMMANDS COMMAND is one of the following: list - (BETA) List MCP tools. + (BETA) (DEPRECATED) List MCP tools. NOTES This command is currently in beta and might change without notice. This diff --git a/gcloud/beta/api-registry/mcp/tools/list b/gcloud/beta/api-registry/mcp/tools/list index 6c87a7d2c..78db2382c 100644 --- a/gcloud/beta/api-registry/mcp/tools/list +++ b/gcloud/beta/api-registry/mcp/tools/list @@ -7,7 +7,23 @@ SYNOPSIS [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) List MCP tools. + (BETA) (DEPRECATED) The gcloud beta api-registry mcp tools list command is + deprecated and will be removed in a future release. For similar + functionality, you can use Agent Registry. Note: Agent Registry does not + treat tools as a separate collection. To view tools, please use gcloud + alpha agent-registry mcp-servers list or describe command to view the tools + included in the server payloads. For more information, see: + https://docs.cloud.google.com/sdk/gcloud/reference/alpha/agent-registry/mcp-servers + + (BETA) (DEPRECATED) List MCP tools. + + The gcloud beta api-registry mcp tools list command is deprecated and will + be removed in a future release. For similar functionality, you can use + Agent Registry. Note: Agent Registry does not treat tools as a separate + collection. To view tools, please use gcloud alpha agent-registry + mcp-servers list or describe command to view the tools included in the + server payloads. For more information, see: + https://docs.cloud.google.com/sdk/gcloud/reference/alpha/agent-registry/mcp-servers EXAMPLES To list MCP tools, run: diff --git a/gcloud/beta/app-lifecycle-manager/flags/attributes/create b/gcloud/beta/app-lifecycle-manager/flags/attributes/create index 6958bf24e..515e7d9c3 100644 --- a/gcloud/beta/app-lifecycle-manager/flags/attributes/create +++ b/gcloud/beta/app-lifecycle-manager/flags/attributes/create @@ -10,12 +10,17 @@ SYNOPSIS [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) Create a Flag Attribute + (BETA) Create a new flag attribute resource. Flag attributes define the + data schema for targeting rules and percentage-based rollouts. These + attributes correspond to the keys in the OpenFeature EvaluationContext used + by the application SDK to provide contextual data for flag evaluation. EXAMPLES - To create a Flag Attribute, run: + To create a string attribute for user IDs in the global location, run: - $ gcloud beta app-lifecycle-manager flags attributes create + $ gcloud beta app-lifecycle-manager flags attributes create \ + user-id-attr --key=userID --attribute-value-type=string \ + --location=global POSITIONAL ARGUMENTS FlagAttribute resource - Flag Attribute ID. Google Cloud resource name diff --git a/gcloud/beta/app-lifecycle-manager/flags/attributes/delete b/gcloud/beta/app-lifecycle-manager/flags/attributes/delete index 9d51b45ac..1629e1349 100644 --- a/gcloud/beta/app-lifecycle-manager/flags/attributes/delete +++ b/gcloud/beta/app-lifecycle-manager/flags/attributes/delete @@ -7,12 +7,30 @@ SYNOPSIS (FLAG_ATTRIBUTE : --location=LOCATION) [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) Delete a Flag Attribute + (BETA) Delete a Flag Attribute resource. + + This operation is permanent. To prevent evaluation errors in production, + the attribute MUST be removed from all active Flag evaluation + specifications before it is deleted. + + The safe deletion workflow is: + + 1. Identify all flags that reference this attribute in their `evaluation-spec`. + 2. Remove the attribute reference from those flags using `flags update` or delete the flags. + 3. Execute a `Rollout` for any affected flags to ensure the updated configuration is deployed to all units. + 4. Run this `delete` command to permanently remove the attribute definition. EXAMPLES - To delete a Flag Attribute, run: + To delete a Flag Attribute named user-id-attr in the global location, run: - $ gcloud beta app-lifecycle-manager flags attributes delete + $ gcloud beta app-lifecycle-manager flags attributes delete \ + user-id-attr --location=global + + To delete a Flag Attribute using a fully qualified resource name (useful + for automation), run: + + $ gcloud beta app-lifecycle-manager flags attributes delete \ + projects/my-project/locations/global/flagAttributes/user-id-attr POSITIONAL ARGUMENTS FlagAttribute resource - Flag Attribute ID of the Flag Attribute to diff --git a/gcloud/beta/app-lifecycle-manager/flags/attributes/describe b/gcloud/beta/app-lifecycle-manager/flags/attributes/describe index 2a4df3aaf..b324fc7a5 100644 --- a/gcloud/beta/app-lifecycle-manager/flags/attributes/describe +++ b/gcloud/beta/app-lifecycle-manager/flags/attributes/describe @@ -7,12 +7,34 @@ SYNOPSIS (FLAG_ATTRIBUTE : --location=LOCATION) [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) Describe a Flag Attribute + (BETA) Show detailed information about a Flag Attribute resource. + + This command retrieves the metadata and configuration of a Flag Attribute. + Flag Attributes are the fundamental building blocks for targeted rollouts + and randomization, defining the keys (such as userID or version) that are + referenced in a flag's evaluation specification. + + For automated processing, use --format=json or --format=yaml to retrieve + the structured representation of the attribute, which can be useful for + programmatically verifying targeting schemas across environments. EXAMPLES - To describe a Flag Attribute, run: + To describe a Flag Attribute named user-id-attr in the global location, + run: - $ gcloud beta app-lifecycle-manager flags attributes describe + $ gcloud beta app-lifecycle-manager flags attributes describe \ + user-id-attr --location=global + + To describe a Flag Attribute using its fully qualified resource name, run: + + $ gcloud beta app-lifecycle-manager flags attributes describe \ + projects/my-project/locations/global/flagAttributes/user-id-attr + + To inspect the attribute configuration in JSON format for automated + auditing, run: + + $ gcloud beta app-lifecycle-manager flags attributes describe \ + user-id-attr --location=global --format=json POSITIONAL ARGUMENTS FlagAttribute resource - Flag Attribute ID of the Flag Attribute to diff --git a/gcloud/beta/app-lifecycle-manager/flags/attributes/list b/gcloud/beta/app-lifecycle-manager/flags/attributes/list index fe9ab3191..d42b340dd 100644 --- a/gcloud/beta/app-lifecycle-manager/flags/attributes/list +++ b/gcloud/beta/app-lifecycle-manager/flags/attributes/list @@ -9,13 +9,41 @@ SYNOPSIS [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) List Flags Attributes + (BETA) List Flag Attributes available in a specific location for your SaaS + offerings. + + Use this command to audit available attributes (such as userID or tenantID) + used in feature flag evaluation specs to determine variant assignment. + These attributes are typically defined in the global location and must + exist before they can be referenced in a flag's evaluation criteria. EXAMPLES - To list all Flags Attributes, run: + To list all Flag Attributes across all locations in the current project, + run: $ gcloud beta app-lifecycle-manager flags attributes list + To list Flag Attributes for a specific location (e.g., global), run: + + $ gcloud beta app-lifecycle-manager flags attributes list \ + --location=global + + To find a specific attribute by its key (e.g., userID), run: + + $ gcloud beta app-lifecycle-manager flags attributes list \ + --filter="key:userID" + + To get the full resource URIs for use in a flag's evaluation-spec JSON, + run: + + $ gcloud beta app-lifecycle-manager flags attributes list \ + --location=global --uri + + To list attributes and output in JSON format for automation/scripting, run: + + $ gcloud beta app-lifecycle-manager flags attributes list \ + --format=json + FLAGS Location resource - Location in which to list Flag Attributes. This represents a Cloud resource. (NOTE) Some attributes are not given diff --git a/gcloud/beta/app-lifecycle-manager/flags/attributes/update b/gcloud/beta/app-lifecycle-manager/flags/attributes/update index 71b4faf9a..c1eeea6aa 100644 --- a/gcloud/beta/app-lifecycle-manager/flags/attributes/update +++ b/gcloud/beta/app-lifecycle-manager/flags/attributes/update @@ -13,12 +13,24 @@ SYNOPSIS | --remove-labels=REMOVE_LABELS] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) Update a Flag Attribute. + (BETA) Update the metadata of a Flag Attribute. This command allows you to + modify labels and annotations associated with the resource. + + Flag Attributes are foundational resources that define the evaluation + context such as 'userID', 'tenantID', or 'region' used by targeting rules + and randomization algorithms to determine flag values. + + Note that core fields like the attribute key and value type are immutable + after creation to maintain evaluation consistency across your service. This + command is primarily used for categorization via labels or for attaching + audit metadata via annotations. EXAMPLES - To update Flag Attribute, run: + To update labels and annotations for a flag attribute, run: - $ gcloud beta app-lifecycle-manager flags attributes update + $ gcloud beta app-lifecycle-manager flags attributes update \ + my-attribute --location=global --labels=env=prod \ + --annotations=ticket=123 POSITIONAL ARGUMENTS FlagAttribute resource - Flag Attribute ID. Flag Attribute ID. Google diff --git a/gcloud/beta/app-lifecycle-manager/flags/create b/gcloud/beta/app-lifecycle-manager/flags/create index 53a3b1856..191d0a8ca 100644 --- a/gcloud/beta/app-lifecycle-manager/flags/create +++ b/gcloud/beta/app-lifecycle-manager/flags/create @@ -5,20 +5,43 @@ SYNOPSIS gcloud beta app-lifecycle-manager flags create FLAG --flag-value-type=FLAG_VALUE_TYPE --key=KEY --unit-kind=UNIT_KIND [--annotations=[ANNOTATIONS,...]] [--description=DESCRIPTION] - [--evaluation-spec=[defaultTarget=DEFAULTTARGET]] [--flag-set=FLAG_SET] - [--labels=[LABELS,...]] [--location=LOCATION] [--state=STATE] + [--evaluation-spec=[allocations=ALLOCATIONS], + [attributes=ATTRIBUTES],[defaultTarget=DEFAULTTARGET],[rules=RULES]] + [--flag-set=FLAG_SET] [--labels=[LABELS,...]] [--location=LOCATION] + [--state=STATE] [--variants=[booleanValue=BOOLEANVALUE],[description=DESCRIPTION], [doubleValue=DOUBLEVALUE], [id=ID],[integerValue=INTEGERVALUE],[stringValue=STRINGVALUE]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) Create a Flag + (BETA) Create a new feature flag resource. Flags define toggleable features + or configurations that can be evaluated at runtime by applications. EXAMPLES - To create a Flag, run: + To create a simple boolean flag with a default Disabled state, run: - $ gcloud beta app-lifecycle-manager flags create + $ gcloud beta app-lifecycle-manager flags create my-feature-flag \ + --key=enable_new_feature --flag-value-type=bool \ + --unit-kind=my-service-unit \ + --variants='[{"id": "Enabled", "booleanValue": true}, {"id": + "Disabled", "booleanValue": false}]' \ + --evaluation-spec='{"defaultTarget": "Disabled"}' \ + --location=global + + To create a percentage rollout (10% Enabled) using a userID attribute, run: + + $ gcloud beta app-lifecycle-manager flags create beta-feature \ + --key=beta_rollout --flag-value-type=bool \ + --unit-kind=my-service-unit \ + --variants='[{"id": "Enabled", "booleanValue": true}, {"id": + "Disabled", "booleanValue": false}]' \ + --evaluation-spec='{"allocations": [{"id": "p10", + "randomizedOn": "userID", "slots": [{"variant": "Disabled", + "weight": 90}, {"variant": "Enabled", "weight": 10}]}], + "defaultTarget": "p10", "attributes": + ["projects/my-project/locations/global/flagAttributes/id-attr"]}' \ + --location=global POSITIONAL ARGUMENTS Flag resource - ID of the Flag: @@ -116,19 +139,62 @@ OPTIONAL FLAGS --description=DESCRIPTION A description of the flag. Max length: 500 bytes. - --evaluation-spec=[defaultTarget=DEFAULTTARGET] + --evaluation-spec=[allocations=ALLOCATIONS],[attributes=ATTRIBUTES],[defaultTarget=DEFAULTTARGET],[rules=RULES] Specification of how the Flag value should be evaluated. + allocations + A list of allocations. + + description + A description of the allocation. Max length: 500 bytes. + + id + Id of the allocation. Max length: 128 bytes. + + randomizedOn + Key of the context attribute that is used for traffic + splitting. + + slots + Slots defines the weighted distribution of variants. + + variant + Variant of the allocation slot. + + weight + Weight defines the proportion of traffic to allocate to the + variant, relative to other slots in the same allocation. + + attributes + Names of the context attributes that are used in the evaluation + rules and allocations. + defaultTarget Default variant for the flag. + rules + Define the logic for evaluating the flag against a given context. + The rules are evaluated sequentially in their specified order. + + condition + A Common Expression Language (CEL cel.dev) expression evaluated + against the evaluation context. For example: plan == "premium" + && country == "DE". + + id + A unique identifier for the rule. + + target + The ID of the variant to return if the condition evaluates to + true. + Shorthand Example: - --evaluation-spec=defaultTarget=string + --evaluation-spec=allocations=[{description=string,id=string,randomizedOn=string,slots=[{variant=string,weight=int}]}],attributes=[string],defaultTarget=string,rules=[{condition=string,id=string,target=string}] JSON Example: - --evaluation-spec='{"defaultTarget": "string"}' + --evaluation-spec='{"allocations": [{"description": "string", "id": "string", "randomizedOn": "string", "slots": [{"variant": "string", "weight": int}]}], "attributes": ["string"], "defaultTarget": "string", "rules": [{"condition": "string", "id": "string", "target": "string"}]}' File Example: diff --git a/gcloud/beta/app-lifecycle-manager/flags/delete b/gcloud/beta/app-lifecycle-manager/flags/delete index 33a155b4f..aaf06d1dd 100644 --- a/gcloud/beta/app-lifecycle-manager/flags/delete +++ b/gcloud/beta/app-lifecycle-manager/flags/delete @@ -6,12 +6,31 @@ SYNOPSIS [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) Delete a Flag + (BETA) Delete a feature flag resource. + + This operation is permanent. To prevent production outages, the flag MUST + be detached from all Units and UnitKinds via a rollout before it is + deleted. + + The safe deletion workflow is: + + 1. Ensure all application code using the flag has been removed and the updated binary is deployed to production. + 2. Confirm that no active Units are still requesting evaluations for that specific flag key. + 3. Detach from Units: create a new FlagRelease that includes Flag to remove and initiate a Rollout. + 4. Once the cleanup rollout is complete, you can safely delete the FlagRelease and FlagRevision. + 5. Run this delete command to permanently remove the Flag. EXAMPLES - To delete a Flag, run: + To delete a flag named my-feature-flag in the global location, run: - $ gcloud beta app-lifecycle-manager flags delete + $ gcloud beta app-lifecycle-manager flags delete my-feature-flag \ + --location=global + + To delete a flag using a fully qualified resource name (useful for + automation), run: + + $ gcloud beta app-lifecycle-manager flags delete \ + projects/my-project/locations/global/flags/my-feature-flag POSITIONAL ARGUMENTS Flag resource - Flag ID of the Flag to delete. The arguments in this group diff --git a/gcloud/beta/app-lifecycle-manager/flags/describe b/gcloud/beta/app-lifecycle-manager/flags/describe index 1743848e7..a0f5f92ef 100644 --- a/gcloud/beta/app-lifecycle-manager/flags/describe +++ b/gcloud/beta/app-lifecycle-manager/flags/describe @@ -6,18 +6,39 @@ SYNOPSIS (FLAG : --location=LOCATION) [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) Describe a Flag + (BETA) Show detailed information about a feature flag resource. + + This command retrieves the complete configuration and status of a flag. It + is the primary tool for auditing flag definitions and troubleshooting + rollout discrepancies. + + For automated processing, use --format=json or --format=yaml to retrieve + the structured representation of the flag's evaluation specification, which + can be used to programmatically verify rollout configurations before + deployment. EXAMPLES - To describe a Flag, run: + To describe a flag named my-feature-flag in the global location, run: - $ gcloud beta app-lifecycle-manager flags describe + $ gcloud beta app-lifecycle-manager flags describe my-feature-flag \ + --location=global + + To describe a flag using its fully qualified resource name, run: + + $ gcloud beta app-lifecycle-manager flags describe \ + projects/my-project/locations/global/flags/my-feature-flag + + To inspect the evaluation specification in JSON format for automated + auditing, run: + + $ gcloud beta app-lifecycle-manager flags describe my-feature-flag \ + --location=global --format=json POSITIONAL ARGUMENTS - Flag resource - Flag ID of the Flag 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. + Flag resource - Flag ID of the Flag to describe or the fully qualified + resource name. The arguments in this group can be used to specify the + attributes of this resource. (NOTE) Some attributes are not given + arguments in this group but can be set in other ways. To set the project attribute: ◆ provide the argument flag on the command line with a fully specified diff --git a/gcloud/beta/app-lifecycle-manager/flags/list b/gcloud/beta/app-lifecycle-manager/flags/list index 038e0591b..a27a6f3a3 100644 --- a/gcloud/beta/app-lifecycle-manager/flags/list +++ b/gcloud/beta/app-lifecycle-manager/flags/list @@ -7,13 +7,30 @@ SYNOPSIS [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) List Flags + (BETA) List all feature flags available in a specific location for your + SaaS offerings. + + Use this command to audit available flags and their associated UnitKind + assignments. EXAMPLES - To list Flags, run: + To list all flags across all locations in the current project, run: $ gcloud beta app-lifecycle-manager flags list + To list flags for a specific location (e.g., us-central1), run: + + $ gcloud beta app-lifecycle-manager flags list --location=us-central1 + + To filter flags belonging to a specific UnitKind, run: + + $ gcloud beta app-lifecycle-manager flags list \ + --filter="unitKind:my-unit-kind" + + To list flags and output in JSON format for automation/scripting, run: + + $ gcloud beta app-lifecycle-manager flags list --format=json + FLAGS Location resource - Location in which to list Flags. This represents a Cloud resource. (NOTE) Some attributes are not given arguments in this diff --git a/gcloud/beta/app-lifecycle-manager/flags/releases/create b/gcloud/beta/app-lifecycle-manager/flags/releases/create index 4ff38bbf6..52695f530 100644 --- a/gcloud/beta/app-lifecycle-manager/flags/releases/create +++ b/gcloud/beta/app-lifecycle-manager/flags/releases/create @@ -6,16 +6,27 @@ SYNOPSIS gcloud beta app-lifecycle-manager flags releases create FLAG_RELEASE --unit-kind=UNIT_KIND [--annotations=[ANNOTATIONS,...]] [--labels=[LABELS,...]] [--location=LOCATION] + [--obsolete-flags=[OBSOLETE_FLAGS,...]] [--all-flags | --flag-sets=[FLAG_SETS,...] | --revisions=[REVISIONS,...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) Create a Flag Release. + (BETA) Create a new Flag Release resource. A Flag Release defines a + specific set of flag revisions to be applied to a UnitKind. It serves as + the immutable input for a Rollout. EXAMPLES - To create a Flag Release, run: + To create a targeted Flag Release for specific flag revisions, run: - $ gcloud beta app-lifecycle-manager flags releases create + $ gcloud beta app-lifecycle-manager flags releases create \ + my-release --unit-kind=my-unit-kind --revisions=rev-1,rev-2 \ + --location=global + + To create a Flag Release that includes all current flags in a UnitKind, + run: + + $ gcloud beta app-lifecycle-manager flags releases create \ + full-sync --unit-kind=my-unit-kind --all-flags --location=global POSITIONAL ARGUMENTS FlagRelease resource - ID of the Flag Release: @@ -118,9 +129,33 @@ OPTIONAL FLAGS --labels=path_to_file.(yaml|json) --location=LOCATION - For resources [flag_release, revisions, unit-kind], provides fallback - value for resource location attribute. When the resource's full URI - path is not provided, location will fallback to this flag value. + For resources [flag_release, obsolete-flags, revisions, unit-kind], + provides fallback value for resource location attribute. When the + resource's full URI path is not provided, location will fallback to + this flag value. + + Flag resource - Flags (IDs) to be removed from the given UnitKind and all + the related Units. If Flag (ID) is provided here, its Flag Revisions will + be removed from the UnitKind and Units. 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 --obsolete-flags 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 --obsolete-flags on the command line with a + fully specified name; + ◆ provide the argument --location on the command line. + + --obsolete-flags=[OBSOLETE_FLAGS,...] + IDs of the flags or fully qualified identifiers for the flags. + + To set the flag attribute: + ◆ provide the argument --obsolete-flags on the command line. Flags for specifying the content of the release. You can use only one of the following flags. diff --git a/gcloud/beta/app-lifecycle-manager/flags/releases/delete b/gcloud/beta/app-lifecycle-manager/flags/releases/delete index a95e83ded..4820c11be 100644 --- a/gcloud/beta/app-lifecycle-manager/flags/releases/delete +++ b/gcloud/beta/app-lifecycle-manager/flags/releases/delete @@ -7,12 +7,28 @@ SYNOPSIS (FLAG_RELEASE : --location=LOCATION) [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) Delete a Flag Release + (BETA) Delete a Flag Release resource. + + Flag Releases are resources that groups one or more FlagRevision resources + that are intended to be deployed together as a single payload for a + Rollout. + + The safe deletion workflow is: + + 1. Ensure no active Rollouts reference this Flag Release. + 2. Run this `delete` command to permanently remove the Flag Release. EXAMPLES - To delete a Flag Release, run: + To delete a Flag Release named 'v1-release' in the 'global' location, run: - $ gcloud beta app-lifecycle-manager flags releases delete + $ gcloud beta app-lifecycle-manager flags releases delete \ + v1-release --location=global + + To delete a Flag Release using a fully qualified resource name (useful for + automation), run: + + $ gcloud beta app-lifecycle-manager flags releases delete \ + projects/my-project/locations/global/flagReleases/v1-release POSITIONAL ARGUMENTS FlagRelease resource - Flag Release ID of the Flag Release to delete. The diff --git a/gcloud/beta/app-lifecycle-manager/flags/releases/describe b/gcloud/beta/app-lifecycle-manager/flags/releases/describe index d2c555298..cde3a4f73 100644 --- a/gcloud/beta/app-lifecycle-manager/flags/releases/describe +++ b/gcloud/beta/app-lifecycle-manager/flags/releases/describe @@ -1,18 +1,40 @@ NAME gcloud beta app-lifecycle-manager flags releases describe - describe Flag - Revision + Release SYNOPSIS gcloud beta app-lifecycle-manager flags releases describe (FLAG_RELEASE : --location=LOCATION) [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) Describe a Flag Release + (BETA) Show detailed information about a Flag Release resource. + + A Flag Release is a configuration snapshot that groups one or more Flag + Revisions for a specific UnitKind. This command retrieves the list of + revisions, target UnitKind, and other metadata. It is the primary tool for + auditing the content of a rollout. + + For automated processing, use --format=json or --format=yaml to retrieve + the structured representation of the release, which can be used to + programmatically verify rollout configurations or generate recovery + scripts. EXAMPLES - To describe a Flag Release, run: + To describe a Flag Release named my-release in the global location, run: - $ gcloud beta app-lifecycle-manager flags releases describe + $ gcloud beta app-lifecycle-manager flags releases describe \ + my-release --location=global + + To describe a Flag Release using its fully qualified resource name, run: + + $ gcloud beta app-lifecycle-manager flags releases describe \ + projects/my-project/locations/global/flagReleases/my-release + + To inspect the revisions in JSON format for automated auditing or recovery, + run: + + $ gcloud beta app-lifecycle-manager flags releases describe \ + my-release --location=global --format=json POSITIONAL ARGUMENTS FlagRelease resource - Flag Release ID of the Flag Release to describe. diff --git a/gcloud/beta/app-lifecycle-manager/flags/releases/help b/gcloud/beta/app-lifecycle-manager/flags/releases/help index f853f54ed..7962d8143 100644 --- a/gcloud/beta/app-lifecycle-manager/flags/releases/help +++ b/gcloud/beta/app-lifecycle-manager/flags/releases/help @@ -24,13 +24,13 @@ COMMANDS (BETA) Delete Flag Release. describe - (BETA) Describe Flag Revision. + (BETA) Describe Flag Release. list - (BETA) List Flags Releases. + (BETA) List Flag Releases. update - (BETA) Update Flag Release. + (BETA) Update a Flag Release. NOTES This command is currently in beta and might change without notice. diff --git a/gcloud/beta/app-lifecycle-manager/flags/releases/list b/gcloud/beta/app-lifecycle-manager/flags/releases/list index dd92abe2f..f334e9c41 100644 --- a/gcloud/beta/app-lifecycle-manager/flags/releases/list +++ b/gcloud/beta/app-lifecycle-manager/flags/releases/list @@ -1,5 +1,5 @@ NAME - gcloud beta app-lifecycle-manager flags releases list - list Flags Releases + gcloud beta app-lifecycle-manager flags releases list - list Flag Releases SYNOPSIS gcloud beta app-lifecycle-manager flags releases list [--location=LOCATION] @@ -7,13 +7,33 @@ SYNOPSIS [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) List Flags Releases + (BETA) List all Flag Releases available in a specific location for your + SaaS offerings. + + A Flag Release represents a versioned snapshot of one or more flags + associated with a specific UnitKind. It serves as the baseline for flag + rollouts and is the primary mechanism for synchronizing flag configurations + across a fleet of units. EXAMPLES - To list all Flags Releases, run: + To list all Flag Releases across all locations in the current project, run: $ gcloud beta app-lifecycle-manager flags releases list + To list Flag Releases for a specific location (e.g., us-central1), run: + + $ gcloud beta app-lifecycle-manager flags releases list \ + --location=us-central1 + + To filter releases belonging to a specific UnitKind, run: + + $ gcloud beta app-lifecycle-manager flags releases list \ + --filter="unitKind:my-unit-kind" + + To list releases and output in JSON format for automation/scripting, run: + + $ gcloud beta app-lifecycle-manager flags releases list --format=json + FLAGS Location resource - Location in which to list Flag Releases. This represents a Cloud resource. (NOTE) Some attributes are not given diff --git a/gcloud/beta/app-lifecycle-manager/flags/releases/update b/gcloud/beta/app-lifecycle-manager/flags/releases/update index 5e545d356..b8c1338af 100644 --- a/gcloud/beta/app-lifecycle-manager/flags/releases/update +++ b/gcloud/beta/app-lifecycle-manager/flags/releases/update @@ -1,5 +1,5 @@ NAME - gcloud beta app-lifecycle-manager flags releases update - update Flag + gcloud beta app-lifecycle-manager flags releases update - update a Flag Release SYNOPSIS @@ -13,12 +13,23 @@ SYNOPSIS | --remove-labels=REMOVE_LABELS] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) Update a Flag Release + (BETA) Update the administrative metadata of an existing Flag Release. This + command modifies the resource's labels (for categorization and filtering) + and annotations (for external tool metadata). + + Note that Flag Releases are immutable snapshots of flag configurations. + This command does not modify the flag revisions or the associated UnitKind. + To change the flag logic or revisions associated with a UnitKind, you must + create a new Flag Release and initiate a Rollout. This architecture ensures + that once a release is created, its behavioral payload remains constant + while allowing for operational metadata updates. EXAMPLES - To update a Flag Release, run: + To update labels and annotations for a flag release, run: - $ gcloud beta app-lifecycle-manager flags releases update + $ gcloud beta app-lifecycle-manager flags releases update \ + my-release --location=us-central1 --labels=env=prod \ + --annotations=ticket=123 POSITIONAL ARGUMENTS FlagRelease resource - ID of the Flag Release: diff --git a/gcloud/beta/app-lifecycle-manager/flags/revisions/create b/gcloud/beta/app-lifecycle-manager/flags/revisions/create index 4babc199d..ac6b91642 100644 --- a/gcloud/beta/app-lifecycle-manager/flags/revisions/create +++ b/gcloud/beta/app-lifecycle-manager/flags/revisions/create @@ -8,12 +8,35 @@ SYNOPSIS [--location=LOCATION] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) Create a Flag Revision. + (BETA) Create a new flag revision resource. Flag revisions act as immutable + snapshots of a flag's configuration (variants, rules, and allocations) at a + specific point in time. + + This snapshot is a required prerequisite for creating a Flag Release and + initiating a Flag Rollout. Creating a revision ensures that the + configuration state is frozen and safely decoupled from the live flag + definition during the rollout process. EXAMPLES - To create a Flag Revision, run: + To create a Flag Revision for a flag named my-flag in the global location, + run: - $ gcloud beta app-lifecycle-manager flags revisions create + $ gcloud beta app-lifecycle-manager flags revisions create \ + my-revision-v1 --flag=my-flag --location=global + + To create a revision using a fully qualified resource name for the revision + ID, run: + + $ gcloud beta app-lifecycle-manager flags revisions create \ + projects/my-project/locations/global/flagRevisions/\ + my-revision-v1 --flag=my-flag + + To create a revision with metadata for tracking, run: + + $ gcloud beta app-lifecycle-manager flags revisions create \ + prod-ready-rev --flag=search-optimizations \ + --location=us-central1 --labels=env=prod,owner=search-team \ + --annotations=ticket=123 POSITIONAL ARGUMENTS FlagRevision resource - Flag Revision ID. Google Cloud resource name (full diff --git a/gcloud/beta/app-lifecycle-manager/flags/revisions/delete b/gcloud/beta/app-lifecycle-manager/flags/revisions/delete index 71ae4aa42..50f81bedb 100644 --- a/gcloud/beta/app-lifecycle-manager/flags/revisions/delete +++ b/gcloud/beta/app-lifecycle-manager/flags/revisions/delete @@ -7,12 +7,39 @@ SYNOPSIS (FLAG_REVISION : --location=LOCATION) [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) Delete a Flag Revision + (BETA) Delete a flag revision resource. + + This operation is permanent. To prevent production outages, ensure the + revision is no longer referenced by any active Flag Releases, Rollouts, + UnitKinds, or Units before it is deleted. + + The safe deletion workflow is: + + 1. Confirm the FlagRevision is not used by any active Units or + UnitKinds (the baseline configuration). + 2. If the revision is active, initiate a Rollout to detach it from + your fleet. This is typically done by rolling out a new FlagRelease + that references a different revision or, if the flag is being + decommissioned, a cleanup FlagRelease. + 3. Run this delete command to permanently remove Flag Revision. EXAMPLES - To delete a Flag Revision, run: + To delete a flag revision named my-revision-v1 in the global location, run: - $ gcloud beta app-lifecycle-manager flags revisions delete + $ gcloud beta app-lifecycle-manager flags revisions delete \ + my-revision-v1 --location=global + + To delete a flag revision using a fully qualified resource name, run: + + $ gcloud beta app-lifecycle-manager flags revisions delete \ + projects/my-project/locations/global/flagRevisions/\ + my-revision-v1 + + To delete a revision as part of a script without interactive confirmation, + run: + + $ gcloud beta app-lifecycle-manager flags revisions delete \ + my-revision-v1 --location=global --quiet POSITIONAL ARGUMENTS FlagRevision resource - Flag Revision ID of the Flag Revision to delete. diff --git a/gcloud/beta/app-lifecycle-manager/flags/revisions/describe b/gcloud/beta/app-lifecycle-manager/flags/revisions/describe index c1906d933..6982141c3 100644 --- a/gcloud/beta/app-lifecycle-manager/flags/revisions/describe +++ b/gcloud/beta/app-lifecycle-manager/flags/revisions/describe @@ -7,18 +7,40 @@ SYNOPSIS (FLAG_REVISION : --location=LOCATION) [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) Describe a Flag Revision + (BETA) Show detailed information about a flag revision resource. + + This command retrieves the complete configuration of a specific flag + revision. It is the primary tool for auditing historical flag definitions + and inspecting snapshots before they are included in a Flag Release. + + For automated processing, use --format=json or --format=yaml to retrieve + the structured representation of the revision's evaluation logic, which can + be used to programmatically verify configurations. EXAMPLES - To describe a Flag Revision, run: + To describe a flag revision named my-revision-v1 in the global location, + run: - $ gcloud beta app-lifecycle-manager flags revisions describe + $ gcloud beta app-lifecycle-manager flags revisions describe \ + my-revision-v1 --location=global + + To describe a flag revision using its fully qualified resource name, run: + + $ gcloud beta app-lifecycle-manager flags revisions describe \ + projects/my-project/locations/global/flagRevisions/\ + my-revision-v1 + + To inspect the revision configuration in JSON format for automated + auditing, run: + + $ gcloud beta app-lifecycle-manager flags revisions describe \ + my-revision-v1 --location=global --format=json POSITIONAL ARGUMENTS - FlagRevision resource - Flag Revision ID of the Flag Revision to describe. - The arguments in this group can be used to specify the attributes of this - resource. (NOTE) Some attributes are not given arguments in this group but - can be set in other ways. + FlagRevision resource - Flag Revision ID of the Flag Revision to describe + or the fully qualified resource name. The arguments in this group can be + used to specify the attributes of this resource. (NOTE) Some attributes + are not given arguments in this group but can be set in other ways. To set the project attribute: ◆ provide the argument flag_revision on the command line with a fully diff --git a/gcloud/beta/app-lifecycle-manager/flags/revisions/help b/gcloud/beta/app-lifecycle-manager/flags/revisions/help index 8d123ed7d..2a662e9d7 100644 --- a/gcloud/beta/app-lifecycle-manager/flags/revisions/help +++ b/gcloud/beta/app-lifecycle-manager/flags/revisions/help @@ -27,7 +27,7 @@ COMMANDS (BETA) Describe Flag Revision. list - (BETA) List Flags Revisions. + (BETA) List Flag Revisions. update (BETA) Update Flag Revision. diff --git a/gcloud/beta/app-lifecycle-manager/flags/revisions/list b/gcloud/beta/app-lifecycle-manager/flags/revisions/list index 15e5343ad..9d9512eb5 100644 --- a/gcloud/beta/app-lifecycle-manager/flags/revisions/list +++ b/gcloud/beta/app-lifecycle-manager/flags/revisions/list @@ -1,5 +1,5 @@ NAME - gcloud beta app-lifecycle-manager flags revisions list - list Flags + gcloud beta app-lifecycle-manager flags revisions list - list Flag Revisions SYNOPSIS @@ -9,15 +9,42 @@ SYNOPSIS [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) List Flags Revisions + (BETA) List all flag revisions available in a specific location. Flag + revisions are immutable, point-in-time snapshots of a flag's configuration. + + Use this command to audit configuration history, verify revision creation + success, or identify specific revision IDs for manual recovery or inclusion + in a Flag Release. EXAMPLES - To list Flags Revisions, run: + To list all flag revisions across all locations in the current project, + run: $ gcloud beta app-lifecycle-manager flags revisions list + To list all flag revisions in the global location, run: + + $ gcloud beta app-lifecycle-manager flags revisions list \ + --location=global + + To list revisions specifically for a flag named my-flag, run: + + $ gcloud beta app-lifecycle-manager flags revisions list \ + --location=global --filter="flag:my-flag" + + To list the 5 most recent revisions to identify the latest configuration + state, run: + + $ gcloud beta app-lifecycle-manager flags revisions list \ + --location=global --limit=5 --sort-by=~createTime + + To list revisions and output in JSON format for automation/scripting, run: + + $ gcloud beta app-lifecycle-manager flags revisions list \ + --format=json + FLAGS - Location resource - Parent value for ListFlagRevisionsRequest This + Location resource - Location in which to list Flag Revisions. This represents a Cloud resource. (NOTE) Some attributes are not given arguments in this group but can be set in other ways. diff --git a/gcloud/beta/app-lifecycle-manager/flags/revisions/update b/gcloud/beta/app-lifecycle-manager/flags/revisions/update index f69617dbf..d758d2660 100644 --- a/gcloud/beta/app-lifecycle-manager/flags/revisions/update +++ b/gcloud/beta/app-lifecycle-manager/flags/revisions/update @@ -13,12 +13,22 @@ SYNOPSIS | --remove-labels=REMOVE_LABELS] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) Update a Flag Revision. + (BETA) Update the metadata of a flag revision. This command modifies the + revision's labels and annotations without altering the underlying flag + configuration. + + Note that a flag revision serves as an immutable snapshot of a flag's + definition at a specific point in time. While the configuration (variants + and evaluation logic) cannot be modified once created, this command allows + you to add labels and annotations to the revision for categorization and + tracking. EXAMPLES - To update Flag Revision, run: + To update labels and annotations for a flag revision, run: - $ gcloud beta app-lifecycle-manager flags revisions update + $ gcloud beta app-lifecycle-manager flags revisions update \ + my-revision --location=global --labels=env=prod \ + --annotations=ticket=123 POSITIONAL ARGUMENTS FlagRevision resource - Flag Revision ID. Google Cloud resource name (full diff --git a/gcloud/beta/app-lifecycle-manager/flags/update b/gcloud/beta/app-lifecycle-manager/flags/update index 9025cfd06..d887d60b2 100644 --- a/gcloud/beta/app-lifecycle-manager/flags/update +++ b/gcloud/beta/app-lifecycle-manager/flags/update @@ -3,7 +3,8 @@ NAME SYNOPSIS gcloud beta app-lifecycle-manager flags update (FLAG : --location=LOCATION) - [--evaluation-spec=[defaultTarget=DEFAULTTARGET],[variants=VARIANTS]] + [--evaluation-spec=[allocations=ALLOCATIONS], + [attributes=ATTRIBUTES],[defaultTarget=DEFAULTTARGET],[rules=RULES]] [--state=STATE] [--variants=[booleanValue=BOOLEANVALUE],[description=DESCRIPTION], [doubleValue=DOUBLEVALUE], @@ -18,12 +19,68 @@ SYNOPSIS | --remove-labels=REMOVE_LABELS] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) Update a Flag + (BETA) Update the definition of a feature flag. This command modifies the + flag's configuration such as variants, evaluation logic, or metadata within + its parent UnitKind. + + Feature flags follow a lifecycle managed through their state: + + The in-development state is the initial state for a feature flag. It + indicates that the flag is currently being defined, variants are being + added, and evaluation logic is being refined. Flags in this state are + typically used for initial setup and testing and are not yet intended for + production rollouts. + + The active state is the default state for a feature flag. It signifies that + the flag is in use, authorized for production rollouts, and actively being + evaluated by application services. Active flags are included in + configuration manifests and release snapshots for the fleet. + + The sunsetting state indicates that a feature flag is being phased out. It + serves as a signal to engineering teams that the code associated with the + flag should be removed. While still functional, sunsetting flags should not + be used for new feature logic and are candidates for future cleanup. + + When a flag is no longer needed, its state can be updated to cleanup. + Performing a rollout with a flag in this state will remove all its + revisions from the Units. This is a mandatory step in the flag deletion + flow. + + Note that updating a flag definition does not immediately change the flag's + value in production units. To apply these changes to your fleet, you must + subsequently create a new FlagRelease and initiate a Rollout. This + architecture enables the decoupling of feature releases from code + deployments, facilitating safe, progressive rollouts and instant rollbacks. EXAMPLES - To update a Flag, run: + To initialize a flag in the in-development state for testing, run: - $ gcloud beta app-lifecycle-manager flags update + $ gcloud beta app-lifecycle-manager flags update my-flag \ + --location=global --state=in-development + + To guarantee a flag is active for a new production rollout, run: + + $ gcloud beta app-lifecycle-manager flags update my-flag \ + --location=global --state=active + + To update the variants of a boolean flag, run: + + $ gcloud beta app-lifecycle-manager flags update my-flag \ + --location=global \ + --variants='[{"id": "Enabled", "booleanValue": true}, {"id": + "Disabled", "booleanValue": false}]' + + To mark a flag as sunsetting to signal code removal, run: + + $ gcloud beta app-lifecycle-manager flags update my-flag \ + --location=global --state=sunsetting \ + --description="Feature fully launched. Starting code removal." + + To mark a flag for cleanup (remove from Units in the next rollout), run: + + $ gcloud beta app-lifecycle-manager flags update my-flag \ + --location=global --state=cleanup \ + --description="Ready for permanent deletion." POSITIONAL ARGUMENTS Flag resource - ID of the Flag: @@ -61,29 +118,62 @@ POSITIONAL ARGUMENTS ▸ provide the argument --location on the command line. FLAGS - --evaluation-spec=[defaultTarget=DEFAULTTARGET],[variants=VARIANTS] + --evaluation-spec=[allocations=ALLOCATIONS],[attributes=ATTRIBUTES],[defaultTarget=DEFAULTTARGET],[rules=RULES] Specification of how the Flag value should be evaluated. + allocations + A list of allocations. + + description + A description of the allocation. Max length: 500 bytes. + + id + Id of the allocation. Max length: 128 bytes. + + randomizedOn + Key of the context attribute that is used for traffic + splitting. + + slots + Slots defines the weighted distribution of variants. + + variant + Variant of the allocation slot. + + weight + Weight defines the proportion of traffic to allocate to the + variant, relative to other slots in the same allocation. + + attributes + Names of the context attributes that are used in the evaluation + rules and allocations. + defaultTarget Default variant for the flag. - variants - A list of variants. Variant is an identifier for a value (name - assigned to a value). + rules + Define the logic for evaluating the flag against a given context. + The rules are evaluated sequentially in their specified order. - boolValue - Value is a single boolean flag value for the variant. + condition + A Common Expression Language (CEL cel.dev) expression evaluated + against the evaluation context. For example: plan == "premium" + && country == "DE". - name - Name of the variant. Max length: 128 bytes. + id + A unique identifier for the rule. + + target + The ID of the variant to return if the condition evaluates to + true. Shorthand Example: - --evaluation-spec=defaultTarget=string,variants=[{boolValue=boolean,name=string}] + --evaluation-spec=allocations=[{description=string,id=string,randomizedOn=string,slots=[{variant=string,weight=int}]}],attributes=[string],defaultTarget=string,rules=[{condition=string,id=string,target=string}] JSON Example: - --evaluation-spec='{"defaultTarget": "string", "variants": [{"boolValue": boolean, "name": "string"}]}' + --evaluation-spec='{"allocations": [{"description": "string", "id": "string", "randomizedOn": "string", "slots": [{"variant": "string", "weight": int}]}], "attributes": ["string"], "defaultTarget": "string", "rules": [{"condition": "string", "id": "string", "target": "string"}]}' File Example: diff --git a/gcloud/beta/app-lifecycle-manager/saas/create b/gcloud/beta/app-lifecycle-manager/saas/create index 812689721..520513ecd 100644 --- a/gcloud/beta/app-lifecycle-manager/saas/create +++ b/gcloud/beta/app-lifecycle-manager/saas/create @@ -3,7 +3,10 @@ NAME SYNOPSIS gcloud beta app-lifecycle-manager saas create (SAAS : --location=LOCATION) - --locations=[name=NAME] [--labels=[LABELS,...]] [GCLOUD_WIDE_FLAG ...] + --locations=[name=NAME] [--labels=[LABELS,...]] + [--application-template=APPLICATION_TEMPLATE + : --application-template-revision=APPLICATION_TEMPLATE_REVISION] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) Create a SaaS @@ -90,6 +93,19 @@ OPTIONAL FLAGS --labels=path_to_file.(yaml|json) + CompositeRef represents a reference to a composite resource. + + --application-template=APPLICATION_TEMPLATE + Reference to the ApplicationTemplate resource. + + This flag argument must be specified if any of the other arguments in + this group are specified. + + --application-template-revision=APPLICATION_TEMPLATE_REVISION + Revision of the ApplicationTemplate to use. Changes to revision will + trigger manual resynchronization. If empty, ApplicationTemplate will be + ignored. + 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/app-lifecycle-manager/saas/update b/gcloud/beta/app-lifecycle-manager/saas/update index cdda4a2db..9ec20d1c8 100644 --- a/gcloud/beta/app-lifecycle-manager/saas/update +++ b/gcloud/beta/app-lifecycle-manager/saas/update @@ -3,6 +3,9 @@ NAME SYNOPSIS gcloud beta app-lifecycle-manager saas update (SAAS : --location=LOCATION) + [--application-template=APPLICATION_TEMPLATE + --application-template-revision=APPLICATION_TEMPLATE_REVISION + --clear-application-template] [--labels=[LABELS,...] | --update-labels=[UPDATE_LABELS,...] --clear-labels | --remove-labels=REMOVE_LABELS] @@ -50,6 +53,19 @@ POSITIONAL ARGUMENTS ▸ provide the argument --location on the command line. FLAGS + CompositeRef represents a reference to a composite resource. + + --application-template=APPLICATION_TEMPLATE + Reference to the ApplicationTemplate resource. + + --application-template-revision=APPLICATION_TEMPLATE_REVISION + Revision of the ApplicationTemplate to use. Changes to revision will + trigger manual resynchronization. If empty, ApplicationTemplate will be + ignored. + + --clear-application-template + Set saas.applicationTemplate back to default value. + Update labels. At most one of these can be specified: diff --git a/gcloud/beta/app-lifecycle-manager/unit-kinds/create b/gcloud/beta/app-lifecycle-manager/unit-kinds/create index 27bfdd42b..be1a7fc19 100644 --- a/gcloud/beta/app-lifecycle-manager/unit-kinds/create +++ b/gcloud/beta/app-lifecycle-manager/unit-kinds/create @@ -8,6 +8,7 @@ SYNOPSIS [--input-variable-mappings=[from=FROM],[to=TO],[variable=VARIABLE]] [--labels=[LABELS,...]] [--location=LOCATION] [--output-variable-mappings=[from=FROM],[to=TO],[variable=VARIABLE]] + [--app-params-group=APP_PARAMS_GROUP --scope-type=SCOPE_TYPE] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -232,6 +233,24 @@ OPTIONAL FLAGS --output-variable-mappings=path_to_file.(yaml|json) + AppParams contains the parameters for creating an AppHub Application. + + --app-params-group=APP_PARAMS_GROUP + Grouping used to construct the name of the AppHub Application. Multiple + UnitKinds can specify the same group to use the same Application across + their respective units. Corresponds to the app_boundary_id in the ADC + composite ApplicationTemplate. Defaults to UnitKind.name + + Scope of an application. + + --scope-type=SCOPE_TYPE + Scope Type. SCOPE_TYPE must be one of: + + type-global + Global type. + type-regional + Regional type. + 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/app-lifecycle-manager/unit-kinds/update b/gcloud/beta/app-lifecycle-manager/unit-kinds/update index b20432cf0..e3caf0dbd 100644 --- a/gcloud/beta/app-lifecycle-manager/unit-kinds/update +++ b/gcloud/beta/app-lifecycle-manager/unit-kinds/update @@ -4,6 +4,8 @@ NAME SYNOPSIS gcloud beta app-lifecycle-manager unit-kinds update UNIT_KIND [--location=LOCATION] [--saas=SAAS] + [--app-params-group=APP_PARAMS_GROUP + --clear-app-params --scope-type=SCOPE_TYPE] [--clear-default-release | --default-release=DEFAULT_RELEASE] [--dependencies=[alias=ALIAS],[unitKind=UNITKIND] | --add-dependencies=[alias=ALIAS],[unitKind=UNITKIND] @@ -85,6 +87,27 @@ FLAGS To set the saas attribute: ◆ provide the argument --saas on the command line. + AppParams contains the parameters for creating an AppHub Application. + + --app-params-group=APP_PARAMS_GROUP + Grouping used to construct the name of the AppHub Application. Multiple + UnitKinds can specify the same group to use the same Application across + their respective units. Corresponds to the app_boundary_id in the ADC + composite ApplicationTemplate. Defaults to UnitKind.name + + --clear-app-params + Set unitKind.appParams back to default value. + + Scope of an application. + + --scope-type=SCOPE_TYPE + Scope Type. SCOPE_TYPE must be one of: + + type-global + Global type. + type-regional + Regional type. + Update default_release. At most one of these can be specified: diff --git a/gcloud/beta/app-lifecycle-manager/units/create b/gcloud/beta/app-lifecycle-manager/units/create index 74ba46418..9e6a74afc 100644 --- a/gcloud/beta/app-lifecycle-manager/units/create +++ b/gcloud/beta/app-lifecycle-manager/units/create @@ -3,8 +3,8 @@ NAME SYNOPSIS gcloud beta app-lifecycle-manager units create UNIT - [--flag-revisions=[FLAG_REVISIONS,...]] [--labels=[LABELS,...]] - [--location=LOCATION] + [--application=APPLICATION] [--flag-revisions=[FLAG_REVISIONS,...]] + [--labels=[LABELS,...]] [--location=LOCATION] [--maintenance-pinned-until-time=MAINTENANCE_PINNED_UNTIL_TIME] [--management-mode=MANAGEMENT_MODE] [--tenant=TENANT] [--unit-kind=UNIT_KIND] [GCLOUD_WIDE_FLAG ...] @@ -43,6 +43,11 @@ POSITIONAL ARGUMENTS ▸ provide the argument unit on the command line. FLAGS + --application=APPLICATION + Reference to the AppHub Application this unit belongs to. All resources + deployed in this Unit will be associated with the specified + Application. + FlagRevision resource - List of flag revisions used by this unit This represents a Cloud resource. (NOTE) Some attributes are not given arguments in this group but can be set in other ways. diff --git a/gcloud/beta/app-lifecycle-manager/units/update b/gcloud/beta/app-lifecycle-manager/units/update index b409036bf..2d8b8baa9 100644 --- a/gcloud/beta/app-lifecycle-manager/units/update +++ b/gcloud/beta/app-lifecycle-manager/units/update @@ -4,6 +4,7 @@ NAME SYNOPSIS gcloud beta app-lifecycle-manager units update UNIT [--location=LOCATION] [--maintenance-pinned-until-time=MAINTENANCE_PINNED_UNTIL_TIME] + [--application=APPLICATION | --clear-application] [--clear-tenant | --tenant=TENANT] [--clear-unit-kind | --unit-kind=UNIT_KIND] [--flag-revisions=[FLAG_REVISIONS,...] @@ -64,6 +65,16 @@ FLAGS changes to the release field will be rejected. Rollouts should and will also respect this by not requesting an upgrade in the first place. + Update application. + + At most one of these can be specified: + + --application=APPLICATION + Set application to new value. + + --clear-application + Clear application value and set to null. + Update tenant. At most one of these can be specified: diff --git a/gcloud/beta/app-optimize/help b/gcloud/beta/app-optimize/help new file mode 100644 index 000000000..c96a3bb0c --- /dev/null +++ b/gcloud/beta/app-optimize/help @@ -0,0 +1,30 @@ +NAME + gcloud beta app-optimize - the App Optimize API lets developers and + platform administrators monitor and analyze cost and resource + utilization data and identify cost optimization opportunities for their + applications + +SYNOPSIS + gcloud beta app-optimize GROUP [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) The App Optimize API lets developers and platform administrators + monitor and analyze cost and resource utilization data and identify cost + optimization opportunities for their applications. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +GROUPS + GROUP is one of the following: + + reports + (BETA) A Report is a collection of data for a given Scope (i.e., + Project or Application) consisting of the requested dimensions, + metrics, and filters. + +NOTES + This command is currently in beta and might change without notice. + diff --git a/gcloud/beta/app-optimize/reports/create b/gcloud/beta/app-optimize/reports/create new file mode 100644 index 000000000..fe15d0d8d --- /dev/null +++ b/gcloud/beta/app-optimize/reports/create @@ -0,0 +1,116 @@ +NAME + gcloud beta app-optimize reports create - creates an AppOptimize Report + +SYNOPSIS + gcloud beta app-optimize reports create (REPORT : --location=LOCATION) + --dimensions=[DIMENSIONS,...] --metrics=[METRICS,...] [--async] + [--report-filter=REPORT_FILTER] + [--scopes=[application=APPLICATION],[project=PROJECT]] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Creates a report with the requested dimensions, metrics, and filters + for a specific Scope (i.e. Project or Application). + +EXAMPLES + To create a report called 'my-report' for a scope with project as + 'my-project' with resource and cost metrics: $ gcloud beta app-optimize reports create \ + --dimensions=resource,product --metrics=cost \ + --scope=projects=my-project --location=global my-report + +POSITIONAL ARGUMENTS + Report resource - Identifier. The name of this report. 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 report 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. + + REPORT + ID of the report or fully qualified identifier for the report. + + To set the report attribute: + ▸ provide the argument report 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 report resource. + + To set the location attribute: + ▸ provide the argument report on the command line with a fully + specified name; + ▸ provide the argument --location on the command line. + +REQUIRED FLAGS + --dimensions=[DIMENSIONS,...] + The list of dimensions to include in the report. The list of dimensions + to include in the report. Supported values: application, day, hour, + month, product, project, resource, resource_type, sku. (default: + 'product,resource') (a comma separated list) + + --metrics=[METRICS,...] + The list of metrics to include in the report. The list of metrics to + include in the report. Supported values: cost, + cpu_allocation_core_seconds, cpu_mean_utilization, cpu_p95_utilization, + cpu_usage_core_seconds, memory_allocation_byte_seconds, + memory_mean_utilization, memory_p95_utilization, + memory_usage_byte_seconds (default: 'cost') (a comma separated list) + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --report-filter=REPORT_FILTER + The Common Expression Language (CEL) filter to apply to the report. + + --scopes=[application=APPLICATION],[project=PROJECT] + The resource containers for which to fetch data. Default is the project + specified in the report's parent. + + application + An App Hub Application to fetch data from. + + Format: + "projects/{project}/locations/{location}/applications/{application}". + + project + A Google Cloud Platform project to fetch data from. + + Format: "projects/{project}". + + Shorthand Example: + + --scopes=application=string,project=string --scopes=application=string,project=string + + JSON Example: + + --scopes='[{"application": "string", "project": "string"}]' + + File Example: + + --scopes=path_to_file.(yaml|json) + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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 appoptimize/v1beta API. The full documentation for + this API can be found at: https://cloud.google.com/hub/docs/optimize + +NOTES + This command is currently in beta and might change without notice. + diff --git a/gcloud/beta/app-optimize/reports/delete b/gcloud/beta/app-optimize/reports/delete new file mode 100644 index 000000000..e6be2e3d2 --- /dev/null +++ b/gcloud/beta/app-optimize/reports/delete @@ -0,0 +1,64 @@ +NAME + gcloud beta app-optimize reports delete - deletes an existing AppOptimize + Report + +SYNOPSIS + gcloud beta app-optimize reports delete (REPORT : --location=LOCATION) + [--allow-missing] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Deletes the specified Report. + +POSITIONAL ARGUMENTS + Report resource - The name of the report to delete. + + Format: projects/{project}/locations/{location}/reports/{report_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 + can be set in other ways. + + To set the project attribute: + ◆ provide the argument report 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. + + REPORT + ID of the report or fully qualified identifier for the report. + + To set the report attribute: + ▸ provide the argument report 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 report resource. + + To set the location attribute: + ▸ provide the argument report on the command line with a fully + specified name; + ▸ provide the argument --location on the command line. + +FLAGS + --allow-missing + If set to true, and the report is not found, the request will succeed + but no action will be taken on the server. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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 appoptimize/v1beta API. The full documentation for + this API can be found at: https://cloud.google.com/hub/docs/optimize + +NOTES + This command is currently in beta and might change without notice. + diff --git a/gcloud/beta/lifesciences/operations/wait b/gcloud/beta/app-optimize/reports/describe similarity index 54% rename from gcloud/beta/lifesciences/operations/wait rename to gcloud/beta/app-optimize/reports/describe index d62fea72c..91d6c3a6d 100644 --- a/gcloud/beta/lifesciences/operations/wait +++ b/gcloud/beta/app-optimize/reports/describe @@ -1,47 +1,46 @@ NAME - gcloud beta lifesciences operations wait - wait for Cloud Life Sciences - operation to complete + gcloud beta app-optimize reports describe - gets an existing AppOptimize + Report SYNOPSIS - gcloud beta lifesciences operations wait (OPERATION : --location=LOCATION) + gcloud beta app-optimize reports describe (REPORT : --location=LOCATION) [GCLOUD_WIDE_FLAG ...] -EXAMPLES - To wait for the completion of the operation called my-operation, run: - - $ gcloud beta lifesciences operations wait my-operation +DESCRIPTION + (BETA) Prints the metadata for a specific Report. POSITIONAL ARGUMENTS - Operation resource - The Cloud Life Sciences operation to wait for. The + Report resource - The name of the report to retrieve. + + Format: projects/{project}/locations/{location}/reports/{report_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 can be set in other ways. To set the project attribute: - ◆ provide the argument operation on the command line with a fully + ◆ provide the argument report 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. + REPORT + ID of the report or fully qualified identifier for the report. - To set the operation attribute: - ▸ provide the argument operation on the command line. + To set the report attribute: + ▸ provide the argument report 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. + The location id of the report resource. To set the location attribute: - ▸ provide the argument operation on the command line with a fully + ▸ provide the argument report on the command line with a fully specified name; - ▸ provide the argument --location on the command line; - ▸ set the property lifesciences/location. + ▸ provide the argument --location on the command line. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, @@ -51,9 +50,10 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. +API REFERENCE + This command uses the appoptimize/v1beta API. The full documentation for + this API can be found at: https://cloud.google.com/hub/docs/optimize + NOTES - This command is currently in beta and might change without notice. This - variant is also available: - - $ gcloud alpha lifesciences operations wait + This command is currently in beta and might change without notice. diff --git a/gcloud/beta/app-optimize/reports/help b/gcloud/beta/app-optimize/reports/help new file mode 100644 index 000000000..083d9feec --- /dev/null +++ b/gcloud/beta/app-optimize/reports/help @@ -0,0 +1,38 @@ +NAME + gcloud beta app-optimize reports - a Report is a collection of data for a + given Scope (i.e., Project or Application) consisting of the requested + dimensions, metrics, and filters + +SYNOPSIS + gcloud beta app-optimize reports COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) A Report is a collection of data for a given Scope (i.e., Project or + Application) consisting of the requested dimensions, metrics, and filters. + +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 an AppOptimize Report. + + delete + (BETA) Deletes an existing AppOptimize Report. + + describe + (BETA) Gets an existing AppOptimize Report. + + list + (BETA) Lists existing AppOptimize Reports. + + read + (BETA) Reads an existing AppOptimize Report. + +NOTES + This command is currently in beta and might change without notice. + diff --git a/gcloud/beta/app-optimize/reports/list b/gcloud/beta/app-optimize/reports/list new file mode 100644 index 000000000..78a5a31b5 --- /dev/null +++ b/gcloud/beta/app-optimize/reports/list @@ -0,0 +1,79 @@ +NAME + gcloud beta app-optimize reports list - lists existing AppOptimize Reports + +SYNOPSIS + gcloud beta app-optimize reports list --location=LOCATION + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Displays the list of Reports generated for a given Project. + +REQUIRED FLAGS + Location resource - The parent project whose reports are to be listed. + + Format: projects/{project}/locations/{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; + ◆ 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 appoptimize/v1beta API. The full documentation for + this API can be found at: https://cloud.google.com/hub/docs/optimize + +NOTES + This command is currently in beta and might change without notice. + diff --git a/gcloud/beta/app-optimize/reports/read b/gcloud/beta/app-optimize/reports/read new file mode 100644 index 000000000..2f516f046 --- /dev/null +++ b/gcloud/beta/app-optimize/reports/read @@ -0,0 +1,54 @@ +NAME + gcloud beta app-optimize reports read - reads an existing AppOptimize + Report + +SYNOPSIS + gcloud beta app-optimize reports read (REPORT : --location=LOCATION) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Reads an existing AppOptimize Report. + +POSITIONAL ARGUMENTS + Report resource - The resource name of the report to query. Format: + projects/{project}/locations/{location}/reports/{report_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 can be + set in other ways. + + To set the project attribute: + ◆ provide the argument report 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. + + REPORT + ID of the report or fully qualified identifier for the report. + + To set the report attribute: + ▸ provide the argument report 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 report resource. + + To set the location attribute: + ▸ provide the argument report 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. + +NOTES + This command is currently in beta and might change without notice. + diff --git a/gcloud/beta/app/migrate-to-run b/gcloud/beta/app/migrate-to-run index cdd617ba2..f53abad7c 100644 --- a/gcloud/beta/app/migrate-to-run +++ b/gcloud/beta/app/migrate-to-run @@ -3,9 +3,8 @@ NAME to Cloud Run SYNOPSIS - gcloud beta app migrate-to-run [--appyaml=APPYAML] - [--entrypoint=ENTRYPOINT] [--service=SERVICE] [--version=VERSION] - [GCLOUD_WIDE_FLAG ...] + gcloud beta app migrate-to-run [--appyaml=APPYAML] [--service=SERVICE] + [--version=VERSION] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) Migrates the second-generation App Engine app to Cloud Run. @@ -15,26 +14,29 @@ EXAMPLES through app.yaml - gcloud app migrate-to-run --appyaml=path/to/app.yaml --entrypoint=main + gcloud app migrate-to-run --appyaml=path/to/app.yaml OR through service and version - gcloud app migrate-to-run --service=default --version=v1 --entrypoint=main + gcloud app migrate-to-run --service=default --version=v1 FLAGS --appyaml=APPYAML - YAML file for the second generation App Engine version to be migrated. - - --entrypoint=ENTRYPOINT - entrypoint required for some runtimes + Path to the app.yaml file for the second generation App Engine version + to be migrated. If not provided, the app.yaml present in the current + directory is used. --service=SERVICE - service name that is deployed in App Engine + Name of the service that is deployed in App Engine. If specified, the + configuration of the existing service will be used and app.yaml in the + current directory will be ignored. --version=VERSION - version name that is deployed in App Engine + Name of the version that is deployed in App Engine. If specified, the + configuration of the existing version will be used and app.yaml in the + current directory will be ignored. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/beta/backup-dr/backup-plan-associations/create b/gcloud/beta/backup-dr/backup-plan-associations/create new file mode 100644 index 000000000..776db5d81 --- /dev/null +++ b/gcloud/beta/backup-dr/backup-plan-associations/create @@ -0,0 +1,125 @@ +NAME + gcloud beta backup-dr backup-plan-associations create - create a new backup + plan association + +SYNOPSIS + gcloud beta backup-dr backup-plan-associations create + (BACKUP_PLAN_ASSOCIATION + : --location=LOCATION --workload-project=WORKLOAD_PROJECT) + --backup-plan=BACKUP_PLAN --resource=RESOURCE + --resource-type=RESOURCE_TYPE [--async] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Create a new backup plan association in the project. It can only be + created in locations where Backup and DR is available. + +EXAMPLES + To create a new backup plan association sample-bpa in project + sample-project and location us-central1 for resource sample-resource-uri + with backup plan sample-backup-plan, run: + + $ gcloud beta backup-dr backup-plan-associations create sample-bpa \ + --project=sample-project --location=us-central1 \ + --backup-plan=sample-backup-plan --resource=sample-resource-uri + +POSITIONAL ARGUMENTS + Backup Plan Association resource - Name of the backup plan association to + be created. Once the backup plan association is created, this name can't + be changed. The name must be unique for a project and location. To create + backup plan associations in a project that's different from the backup + plan, use the --workload-project flag. The arguments in this group can be + used to specify the attributes of this resource. + + This must be specified. + + BACKUP_PLAN_ASSOCIATION + ID of the Backup Plan Association or fully qualified identifier for + the Backup Plan Association. + + To set the name attribute: + ▸ provide the argument BACKUP_PLAN_ASSOCIATION 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 of the Backup Plan Association. + + To set the location attribute: + ▸ provide the argument BACKUP_PLAN_ASSOCIATION on the command line + with a fully specified name; + ▸ provide the argument --location on the command line. + + --workload-project=WORKLOAD_PROJECT + Cloud project id for the Backup Plan Association. + + To set the workload-project attribute: + ▸ provide the argument BACKUP_PLAN_ASSOCIATION on the command line + with a fully specified name; + ▸ provide the argument --workload-project on the command line; + ▸ provide the argument --project on the command line; + ▸ set the property core/project. + +REQUIRED FLAGS + Backup Plan resource - The backup plan to be applied to the resource. + E.g., + projects/sample-project/locations/us-central1/backupPlans/sample-backup-plan + 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 --backup-plan 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 --backup-plan on the command line with a fully + specified name; + ◆ provide the argument --location on the command line. + + This must be specified. + + --backup-plan=BACKUP_PLAN + ID of the Backup Plan or fully qualified identifier for the Backup + Plan. + + To set the name attribute: + ▸ provide the argument --backup-plan on the command line. + + --resource=RESOURCE + The resource to which the backup plan is to be applied. E.g., + projects/sample-project/zones/us-central1-a/instances/sample-instance + + --resource-type=RESOURCE_TYPE + Type of resource to which the backup plan should be applied. + + For example: + ◆ compute./Instance for Compute Engine instances. + ◆ file./Instance for Filestore instances. + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. The default is True. Enabled by default, use --no-async to + disable. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +BRIEF + Creates a new backup plan association + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud backup-dr backup-plan-associations create + + $ gcloud alpha backup-dr backup-plan-associations create + diff --git a/gcloud/beta/backup-dr/backup-plan-associations/delete b/gcloud/beta/backup-dr/backup-plan-associations/delete new file mode 100644 index 000000000..211c13527 --- /dev/null +++ b/gcloud/beta/backup-dr/backup-plan-associations/delete @@ -0,0 +1,80 @@ +NAME + gcloud beta backup-dr backup-plan-associations delete - delete the + specified backup plan association + +SYNOPSIS + gcloud beta backup-dr backup-plan-associations delete + (BACKUP_PLAN_ASSOCIATION + : --location=LOCATION --workload-project=WORKLOAD_PROJECT) [--async] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Delete the specified backup plan association. + +EXAMPLES + To delete a backup plan association sample-bpa in project sample-project + and location us-central1 , run: + + $ gcloud beta backup-dr backup-plan-associations delete sample-bpa \ + --project=sample-project --location=us-central1 + +POSITIONAL ARGUMENTS + Backup Plan Association resource - Name of the backup plan association to + delete. The arguments in this group can be used to specify the attributes + of this resource. + + This must be specified. + + BACKUP_PLAN_ASSOCIATION + ID of the Backup Plan Association or fully qualified identifier for + the Backup Plan Association. + + To set the name attribute: + ▸ provide the argument backup_plan_association 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 of the Backup Plan Association. + + To set the location attribute: + ▸ provide the argument backup_plan_association on the command line + with a fully specified name; + ▸ provide the argument --location on the command line. + + --workload-project=WORKLOAD_PROJECT + Cloud project id for the Backup Plan Association. + + To set the workload-project attribute: + ▸ provide the argument backup_plan_association on the command line + with a fully specified name; + ▸ provide the argument --workload-project on the command line; + ▸ provide the argument --project on the command line; + ▸ set the property core/project. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. The default is True. Enabled by default, use --no-async to + disable. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +BRIEF + Delete a specific backup plan association + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud backup-dr backup-plan-associations delete + + $ gcloud alpha backup-dr backup-plan-associations delete + diff --git a/gcloud/beta/backup-dr/backup-plan-associations/describe b/gcloud/beta/backup-dr/backup-plan-associations/describe new file mode 100644 index 000000000..ab9ea7552 --- /dev/null +++ b/gcloud/beta/backup-dr/backup-plan-associations/describe @@ -0,0 +1,70 @@ +NAME + gcloud beta backup-dr backup-plan-associations describe - show details of + the backup plan association + +SYNOPSIS + gcloud beta backup-dr backup-plan-associations describe + (BACKUP_PLAN_ASSOCIATION : --location=LOCATION) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Show all configuration data associated with the specified backup + plan association. + +EXAMPLES + To view details for backup plan association BACKUP_PLAN_ASSOCIATION, run: + + $ gcloud beta backup-dr backup-plan-associations describe \ + BACKUP_PLAN_ASSOCIATION + +POSITIONAL ARGUMENTS + Backup plan association resource - Name of the backup plan association 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 backup_plan_association 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_ASSOCIATION + ID of the backup_plan_association or fully qualified identifier for + the backup_plan_association. + + To set the backup_plan_association attribute: + ▸ provide the argument backup_plan_association on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + Location ID of the resource. + + To set the location attribute: + ▸ provide the argument backup_plan_association 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 backupdr/v1beta API. The full documentation for this + API can be found at: https://cloud.google.com/backup-disaster-recovery + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud backup-dr backup-plan-associations describe + + $ gcloud alpha backup-dr backup-plan-associations describe + diff --git a/gcloud/beta/backup-dr/backup-plan-associations/fetch-for-resource-type b/gcloud/beta/backup-dr/backup-plan-associations/fetch-for-resource-type new file mode 100644 index 000000000..89b6c84da --- /dev/null +++ b/gcloud/beta/backup-dr/backup-plan-associations/fetch-for-resource-type @@ -0,0 +1,88 @@ +NAME + gcloud beta backup-dr backup-plan-associations fetch-for-resource-type - + fetch Backup Plan Associations for a given resource type and location + +SYNOPSIS + gcloud beta backup-dr backup-plan-associations fetch-for-resource-type + RESOURCE_TYPE --location=LOCATION [--filter=EXPRESSION] [--limit=LIMIT] + [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Fetch Backup Plan Associations for a given resource type and + location. List backup plan associations in a specified location and + resource type in a project. + +EXAMPLES + To list backup plan associations for Cloud SQL with location us-central1, + run: + + $ gcloud beta backup-dr backup-plan-associations \ + fetch-for-resource-type sqladmin.googleapis.com/Instance \ + --location="us-central1" + +POSITIONAL ARGUMENTS + RESOURCE_TYPE + Resource type for which backup plan associations should be fetched. + + For example: + ◆ compute./Instance for Compute Engine instances. + ◆ file./Instance for Filestore instances. + +REQUIRED FLAGS + --location=LOCATION + Location for which backup plan associations should be fetched. + +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. + +BRIEF + List backup plan associations in a specified location and resource type in + a project. + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud backup-dr backup-plan-associations fetch-for-resource-type + + $ gcloud alpha backup-dr backup-plan-associations \ + fetch-for-resource-type + diff --git a/gcloud/beta/backup-dr/backup-plan-associations/help b/gcloud/beta/backup-dr/backup-plan-associations/help new file mode 100644 index 000000000..bd150a62b --- /dev/null +++ b/gcloud/beta/backup-dr/backup-plan-associations/help @@ -0,0 +1,49 @@ +NAME + gcloud beta backup-dr backup-plan-associations - manage Backup and DR + backup plan associations + +SYNOPSIS + gcloud beta backup-dr backup-plan-associations COMMAND + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Manage Backup and DR backup plan associations. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + create + (BETA) Create a new backup plan association. + + delete + (BETA) Delete the specified backup plan association. + + describe + (BETA) Show details of the backup plan association. + + fetch-for-resource-type + (BETA) Fetch Backup Plan Associations for a given resource type and + location. + + list + (BETA) List Backup and DR backup plan associations. + + trigger-backup + (BETA) Create an on-demand backup for a resource. + + update + (BETA) Update a specific backup plan within a backup plan association. + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud backup-dr backup-plan-associations + + $ gcloud alpha backup-dr backup-plan-associations + diff --git a/gcloud/beta/backup-dr/backup-plan-associations/list b/gcloud/beta/backup-dr/backup-plan-associations/list new file mode 100644 index 000000000..f24e12f34 --- /dev/null +++ b/gcloud/beta/backup-dr/backup-plan-associations/list @@ -0,0 +1,94 @@ +NAME + gcloud beta backup-dr backup-plan-associations list - list Backup and DR + backup plan associations + +SYNOPSIS + gcloud beta backup-dr backup-plan-associations list [--location=LOCATION] + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) List backup plan associations in the project for a specified + location. + +EXAMPLES + To list backup plan associations for all locations, run: + + $ gcloud beta backup-dr backup-plan-associations list + + To list backup plan associations in a location my-location, run: + + $ gcloud beta backup-dr backup-plan-associations list \ + --location=my-location + +FLAGS + Location resource - Location for which backup plan associations should be + listed. 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; + ◆ default is all locations 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; + ◆ default is all locations . + +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 backupdr/v1beta API. The full documentation for this + API can be found at: https://cloud.google.com/backup-disaster-recovery + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud backup-dr backup-plan-associations list + + $ gcloud alpha backup-dr backup-plan-associations list + diff --git a/gcloud/beta/backup-dr/backup-plan-associations/trigger-backup b/gcloud/beta/backup-dr/backup-plan-associations/trigger-backup new file mode 100644 index 000000000..16ac37821 --- /dev/null +++ b/gcloud/beta/backup-dr/backup-plan-associations/trigger-backup @@ -0,0 +1,98 @@ +NAME + gcloud beta backup-dr backup-plan-associations trigger-backup - create an + on-demand backup for a resource + +SYNOPSIS + gcloud beta backup-dr backup-plan-associations trigger-backup + (BACKUP_PLAN_ASSOCIATION + : --location=LOCATION --workload-project=WORKLOAD_PROJECT) [--async] + [--labels=[KEY=VALUE,...]] + [--backup-rule-id=BACKUP_RULE_ID + | --custom-retention-days=CUSTOM_RETENTION_DAYS] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Create an on-demand backup for a resource. Trigger an on demand + backup for the given backup rule. + +EXAMPLES + To trigger an on demand backup for a backup plan association sample-bpa in + project sample-project and location us-central1 with backup rule + sample-backup-rule, run: + + $ gcloud beta backup-dr backup-plan-associations trigger-backup \ + sample-bpa --project=sample-project --location=us-central1 \ + --backup-rule-id=sample-backup-rule + +POSITIONAL ARGUMENTS + Backup Plan Association resource - Name of an existing backup plan + association to use for creating an on-demand backup. The arguments in this + group can be used to specify the attributes of this resource. + + This must be specified. + + BACKUP_PLAN_ASSOCIATION + ID of the Backup Plan Association or fully qualified identifier for + the Backup Plan Association. + + To set the name attribute: + ▸ provide the argument BACKUP_PLAN_ASSOCIATION 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 of the Backup Plan Association. + + To set the location attribute: + ▸ provide the argument BACKUP_PLAN_ASSOCIATION on the command line + with a fully specified name; + ▸ provide the argument --location on the command line. + + --workload-project=WORKLOAD_PROJECT + Cloud project id for the Backup Plan Association. + + To set the workload-project attribute: + ▸ provide the argument BACKUP_PLAN_ASSOCIATION on the command line + with a fully specified name; + ▸ provide the argument --workload-project on the command line; + ▸ provide the argument --project on the command line; + ▸ set the property core/project. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. The default is True. Enabled by default, use --no-async to + disable. + + --labels=[KEY=VALUE,...] + Labels to be applied to the backup. + + At most one of these can be specified: + + --backup-rule-id=BACKUP_RULE_ID + Name of an existing backup rule to use for creating an on-demand + backup. + + --custom-retention-days=CUSTOM_RETENTION_DAYS + Duration for which backup data will be retained. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +BRIEF + Create an on-demand backup. + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud backup-dr backup-plan-associations trigger-backup + + $ gcloud alpha backup-dr backup-plan-associations trigger-backup + diff --git a/gcloud/beta/backup-dr/backup-plan-associations/update b/gcloud/beta/backup-dr/backup-plan-associations/update new file mode 100644 index 000000000..a5723f92b --- /dev/null +++ b/gcloud/beta/backup-dr/backup-plan-associations/update @@ -0,0 +1,130 @@ +NAME + gcloud beta backup-dr backup-plan-associations update - update a specific + backup plan within a backup plan association + +SYNOPSIS + gcloud beta backup-dr backup-plan-associations update + (BACKUP_PLAN_ASSOCIATION + : --location=LOCATION --workload-project=WORKLOAD_PROJECT) + --backup-plan=BACKUP_PLAN [--async] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Update a specific backup plan within a backup plan association. + +EXAMPLES + To update backup plan association sample-bpa in project sample-project and + location us-central1 with backup plan sample-backup-plan in the same + project and location, run: + + $ gcloud beta backup-dr backup-plan-associations update sample-bpa \ + --project=sample-project --location=us-central1 \ + --backup-plan=sample-backup-plan + + To update backup plan association sample-bpa-uri with backup plan + sample-backup-plan-uri (using full URIs), run: + + $ gcloud beta backup-dr backup-plan-associations update \ + sample-bpa-uri --backup-plan=sample-backup-plan-uri + + To update backup plan association sample-bpa in location us-central1 with + backup plan sample-backup-plan-uri, run: + + $ gcloud beta backup-dr backup-plan-associations update sample-bpa \ + --location=us-central1 --backup-plan=sample-backup-plan-uri + + To update backup plan association sample-bpa in project workload-project + and location us-central1 with backup plan sample-backup-plan in project + sample-project, run: + + $ gcloud beta backup-dr backup-plan-associations update sample-bpa \ + --workload-project=workload-project --location=us-central1 \ + --backup-plan=sample-backup-plan --project=sample-project + +POSITIONAL ARGUMENTS + Backup Plan Association resource - Backup plan association to be updated. + To update backup plan associations in a project that's different from the + backup plan, use the --workload-project flag. The arguments in this group + can be used to specify the attributes of this resource. + + This must be specified. + + BACKUP_PLAN_ASSOCIATION + ID of the Backup Plan Association or fully qualified identifier for + the Backup Plan Association. + + To set the name attribute: + ▸ provide the argument BACKUP_PLAN_ASSOCIATION 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 of the Backup Plan Association. + + To set the location attribute: + ▸ provide the argument BACKUP_PLAN_ASSOCIATION on the command line + with a fully specified name; + ▸ provide the argument --location on the command line. + + --workload-project=WORKLOAD_PROJECT + Cloud project id for the Backup Plan Association. + + To set the workload-project attribute: + ▸ provide the argument BACKUP_PLAN_ASSOCIATION on the command line + with a fully specified name; + ▸ provide the argument --workload-project on the command line; + ▸ provide the argument --project on the command line; + ▸ set the property core/project. + +REQUIRED FLAGS + Backup Plan resource - Name of the specific backup plan to be applied to + the backup plan association. E.g., + projects/sample-project/locations/us-central1/backupPlans/sample-backup-plan + 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 --backup-plan 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 --backup-plan on the command line with a fully + specified name; + ◆ provide the argument --location on the command line. + + This must be specified. + + --backup-plan=BACKUP_PLAN + ID of the Backup Plan or fully qualified identifier for the Backup + Plan. + + To set the name attribute: + ▸ provide the argument --backup-plan on the command line. + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. The default is True. Enabled by default, use --no-async to + disable. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +BRIEF + Update a specific backup plan within a backup plan association. + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud backup-dr backup-plan-associations update + + $ gcloud alpha backup-dr backup-plan-associations update + diff --git a/gcloud/beta/backup-dr/backup-plan-revisions/describe b/gcloud/beta/backup-dr/backup-plan-revisions/describe new file mode 100644 index 000000000..60ed76755 --- /dev/null +++ b/gcloud/beta/backup-dr/backup-plan-revisions/describe @@ -0,0 +1,78 @@ +NAME + gcloud beta backup-dr backup-plan-revisions describe - show details of the + backup plan revision + +SYNOPSIS + gcloud beta backup-dr backup-plan-revisions describe + (BACKUP_PLAN_REVISION : --backup_plan=BACKUP_PLAN --location=LOCATION) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Show all data associated with the specified backup plan revision. + +EXAMPLES + To view details for backup plan revision 'BACKUP_PLAN_REVISION', run: + + $ gcloud beta backup-dr backup-plan-revisions describe \ + BACKUP_PLAN_REVISION + +POSITIONAL ARGUMENTS + Backup plan revision resource - Name of the backup plan revision to + describe. The arguments in this group can be used to specify the + attributes of this resource. (NOTE) Some attributes are not given + arguments in this group but can be set in other ways. + + To set the project attribute: + ◆ provide the argument backup_plan_revision on the command line with a + fully specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + BACKUP_PLAN_REVISION + ID of the backup_plan_revision or fully qualified identifier for the + backup_plan_revision. + + To set the backup_plan_revision attribute: + ▸ provide the argument backup_plan_revision on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --backup_plan=BACKUP_PLAN + The ID of the Backup Plan + + To set the backup_plan attribute: + ▸ provide the argument backup_plan_revision on the command line + with a fully specified name; + ▸ provide the argument --backup_plan on the command line. + + --location=LOCATION + Location ID of the resource. + + To set the location attribute: + ▸ provide the argument backup_plan_revision on the command line + with a fully specified name; + ▸ provide the argument --location on the command line. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the backupdr/v1beta API. The full documentation for this + API can be found at: https://cloud.google.com/backup-disaster-recovery + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud backup-dr backup-plan-revisions describe + + $ gcloud alpha backup-dr backup-plan-revisions describe + diff --git a/gcloud/beta/backup-dr/backup-plan-revisions/help b/gcloud/beta/backup-dr/backup-plan-revisions/help new file mode 100644 index 000000000..323505063 --- /dev/null +++ b/gcloud/beta/backup-dr/backup-plan-revisions/help @@ -0,0 +1,32 @@ +NAME + gcloud beta backup-dr backup-plan-revisions - view Backup and DR backup + plan revisions + +SYNOPSIS + gcloud beta backup-dr backup-plan-revisions COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) View Backup and DR backup plan revisions. + +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) Show details of the backup plan revision. + + list + (BETA) List backup plan revisions. + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud backup-dr backup-plan-revisions + + $ gcloud alpha backup-dr backup-plan-revisions + diff --git a/gcloud/beta/backup-dr/backup-plan-revisions/list b/gcloud/beta/backup-dr/backup-plan-revisions/list new file mode 100644 index 000000000..33251a5c9 --- /dev/null +++ b/gcloud/beta/backup-dr/backup-plan-revisions/list @@ -0,0 +1,112 @@ +NAME + gcloud beta backup-dr backup-plan-revisions list - list backup plan + revisions + +SYNOPSIS + gcloud beta backup-dr backup-plan-revisions list + [--backup-plan=BACKUP_PLAN --location=LOCATION] [--filter=EXPRESSION] + [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) List backup plan revisions in the project. + +EXAMPLES + To list backup plan revisions for all backup plans and locations, run: + + $ gcloud beta backup-dr backup-plan-revisions list + + To list all backup plan revisions for a backup plan my-backup-plan, run: + + $ gcloud beta backup-dr backup-plan-revisions list \ + --backup-plan=my-backup-plan + + To list all backup plan revisions for a backup plan my-backup-plan in + location my-location, run: + + $ gcloud beta backup-dr backup-plan-revisions list \ + --backup-plan=my-backup-plan --location=my-location + +FLAGS + Backup plan resource - Backup plan to list backup plan revisions from. 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 on the command line with a fully + specified name; + ◆ default is all backup plans with a fully specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + --backup-plan=BACKUP_PLAN + ID of the backup_plan or fully qualified identifier for the + backup_plan. + + To set the backup-plan attribute: + ◆ provide the argument --backup-plan on the command line; + ◆ default is all backup plans . + + --location=LOCATION + Location ID of the resource. + + To set the location attribute: + ◆ provide the argument --backup-plan on the command line with a fully + specified name; + ◆ default is all backup plans with a fully specified name; + ◆ provide the argument --location on the command line; + ◆ default is all locations . + +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 backupdr/v1beta API. The full documentation for this + API can be found at: https://cloud.google.com/backup-disaster-recovery + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud backup-dr backup-plan-revisions list + + $ gcloud alpha backup-dr backup-plan-revisions list + diff --git a/gcloud/beta/backup-dr/backup-plans/create b/gcloud/beta/backup-dr/backup-plans/create new file mode 100644 index 000000000..ef5967068 --- /dev/null +++ b/gcloud/beta/backup-dr/backup-plans/create @@ -0,0 +1,299 @@ +NAME + gcloud beta backup-dr backup-plans create - creates a new Backup Plan + +SYNOPSIS + gcloud beta backup-dr backup-plans create + (BACKUP_PLAN : --location=LOCATION) --backup-vault=BACKUP_VAULT + --resource-type=RESOURCE_TYPE [--async] + [--backup-rule=[PROPERTY=VALUE,...]] + [--compute-instance-properties=[PROPERTY=VALUE,...]] + [--description=DESCRIPTION] [--disk-properties=[PROPERTY=VALUE,...]] + [--labels=[KEY=VALUE,...]] + [--max-custom-on-demand-retention-days=MAX_CUSTOM_ON_DEMAND_RETENTION_DAYS] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Create a new backup plan in the project. It can only be created in + locations where Backup and DR is available. + +EXAMPLES + To create a new backup plan sample-backup-plan for Compute Engine instances + in project sample-project, at location us-central1, with resource-type + compute./Instance and backup-vault backup-vault with 2 + backup-rules: + + run: + + $ gcloud beta backup-dr backup-plans create sample-backup-plan \ + --project=sample-project --location=us-central1 \ + --resource-type 'compute./Instance' \ + --backup-vault --backup-rule \ + --backup-rule + + To create a new backup plan sample-filestore-backup-plan for Filestore + instances in project sample-project, at location us-central1, with + resource-type file./Instance and backup-vault backup-vault + with 1 backup-rule: + + run: + + $ gcloud beta backup-dr backup-plans create \ + sample-filestore-backup-plan --project=sample-project \ + --location=us-central1 \ + --resource-type 'file./Instance' \ + --backup-vault --backup-rule + + Backup Rule Examples: + + 1. Hourly backup rule with hourly backup frequency of 6 hours and store it + for 30 days, and expect the backups to run only between 10:00 to 20:00 UTC + + : + rule-id=sample-hourly-rule,retention-days=30,recurrence=HOURLY,hourly-frequency=6,time-zone=UTC,backup-window-start=10,backup-window-end=20 + + Properties: + ▪ rule-id = "sample-hourly-rule" + ▪ retention-days = 30 + ▪ recurrence = HOURLY + ▪ hourly-frequency = 6 + ▪ time-zone = UTC + ▪ backup-window-start = 10 + ▪ backup-window-end = 20 + + 2. Daily backup rule with daily backup frequency of 6 hours and store it + for 7 days + + : + rule-id=sample-daily-rule,retention-days=7,recurrence=DAILY,backup-window-start=1,backup-window-end=14 + + Properties: + ▪ rule-id = "sample-daily-rule" + ▪ retention-days = 7 + ▪ recurrence = DAILY + ▪ backup-window-start = 1 + ▪ backup-window-end = 14 + + 3. Weekly backup rule with weekly backup frequency on every MONDAY & FRIDAY + and store it for 21 days + + : + rule-id=sample-weekly-rule,retention-days=21,recurrence=WEEKLY,days-of-week="MONDAY + FRIDAY",backup-window-start=10,backup-window-end=20 + + Properties: + ▪ rule-id = "sample-weekly-rule" + ▪ retention-days: 21 + ▪ recurrence = WEEKLY + ▪ days-of-week = "MONDAY FRIDAY" + ▪ backup-window-start = 10 + ▪ backup-window-end = 20 + +POSITIONAL ARGUMENTS + Backup Plan resource - Name of the backup plan to be created. Once the + backup plan is created, this name can't be changed. The name must be + unique for a project and 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_PLAN 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 + ID of the Backup Plan or fully qualified identifier for the Backup + Plan. + + To set the name attribute: + ▸ provide the argument BACKUP_PLAN 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 of the Backup Plan. + + To set the location attribute: + ▸ provide the argument BACKUP_PLAN on the command line with a fully + specified name; + ▸ provide the argument --location on the command line. + +REQUIRED FLAGS + Backup Vault resource - The backup vault where the backups gets stored + using this backup plan. 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 --backup-vault 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 --backup-vault on the command line with a fully + specified name; + ◆ provide the argument --location on the command line. + + This must be specified. + + --backup-vault=BACKUP_VAULT + ID of the Backup Vault or fully qualified identifier for the Backup + Vault. + + To set the name attribute: + ▸ provide the argument --backup-vault on the command line. + + --resource-type=RESOURCE_TYPE + Type of resource to which the backup plan should be applied. + + For example: + ◆ compute./Instance for Compute Engine instances. + ◆ file./Instance for Filestore instances. + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. The default is True. Enabled by default, use --no-async to + disable. + + --backup-rule=[PROPERTY=VALUE,...] + Backup rule that defines parameters for when and how a backup is + created. This flag can be repeated to create more backup rules. + + Parameters for the backup rule include: + + rule-id + Name of the backup rule. The name must be unique and start with a + lowercase letter followed by up to 62 lowercase letters, numbers, + or hyphens. + + retention-days + Duration for which backup data should be retained. It must be + defined in "days". The value should be greater than or equal to the + enforced retention period set for the backup vault. + + recurrence + Frequency for the backup schedule. It must be either: HOURLY, + DAILY, WEEKLY, MONTHLY or YEARLY. + + backup-window-start + Start time of the interval during which backup jobs should be + executed. It can be defined as backup-window-start=2, that means + backup window starts at 2 a.m. The start time and end time must + have an interval of 6 hours. + + backup-window-end + End time of the interval during which backup jobs should be + executed. It can be defined as backup-window-end=14, that means + backup window ends at 2 p.m. The start time and end time must have + an interval of 6 hours. + + Jobs are queued at the beginning of the window and will be marked + as SKIPPED if they do not start by the end time. Jobs that are in + progress will not be canceled at the end time. + + time-zone + The time zone to be used for the backup schedule. The value must + exist in the IANA tz database (https://www.iana.org/time-zones). + The default value is UTC. E.g., Europe/Paris + + Following flags are mutually exclusive: + + hourly-frequency + Frequency for hourly backups. An hourly frequency of 2 means backup + jobs will run every 2 hours from start time till the end time + defined. The hourly frequency must be between 4 and 23. The value + is needed only if recurrence type is HOURLY. + + days-of-week + Days of the week when the backup job should be executed. The value + is needed if recurrence type is WEEKLY. E.g., MONDAY,TUESDAY + + days-of-month + Days of the month when the backup job should be executed. The value + is needed only if recurrence type is YEARLY. E.g.,"1,5,14" + + months + Month for the backup schedule. The value is needed only if + recurrence type is YEARLY. E.g., JANUARY, MARCH + + week-day-of-month + Recurring day of the week in the month or year when the backup job + should be executed. E.g. FIRST-SUNDAY, THIRD-MONDAY. The value can + only be provided if the recurrence type is MONTHLY or YEARLY. + Allowed values for the number of week - FIRST, SECOND, THIRD, + FOURTH, LAST. Allowed values for days of the week - MONDAY to + SUNDAY. + + E.g., + "rule-id=sample-daily-rule,recurrence=WEEKLY,backup-window-start=2,backup-window-end=14,retention-days=20,days-of-week='SUNDAY + MONDAY'" + + --compute-instance-properties=[PROPERTY=VALUE,...] + Workload-specific properties for Compute Engine instance backups + generated by this plan. + + guest-flush + Indicates whether to perform a guest flush operation before taking + a compute backup. When set to true, the system will attempt to + ensure application-consistent backups. When set to false, the + system will create crash-consistent backups. Default value is + false. + + Example: --compute-instance-properties=guest-flush=true + + --description=DESCRIPTION + Provide a description of the backup plan, such as specific use cases + and relevant details, in 2048 characters or less. + + E.g., This is a backup plan that performs a daily backup at 6 p.m. and + retains data for 3 months. + + --disk-properties=[PROPERTY=VALUE,...] + Workload-specific properties for disk backups generated by this plan. + + guest-flush + Indicates whether to perform a guest flush operation before taking + a disk backup. When set to true, the system will attempt to ensure + application-consistent backups. When set to false, the system will + create crash-consistent backups. Default value is false. + + Example: --disk-properties=guest-flush=true + + --labels=[KEY=VALUE,...] + If you have assigned labels to your resources for grouping, you can + provide the label using this flag.A label is a key-value pair. + + 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. + + --max-custom-on-demand-retention-days=MAX_CUSTOM_ON_DEMAND_RETENTION_DAYS + Configure the maximum retention period for on-demand backups. The value + must be greater than or equal to the minimum enforced retention period + set on the backup vault. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +BRIEF + Creates a new backup plan + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud backup-dr backup-plans create + + $ gcloud alpha backup-dr backup-plans create + diff --git a/gcloud/beta/backup-dr/backup-plans/delete b/gcloud/beta/backup-dr/backup-plans/delete new file mode 100644 index 000000000..832f81c3f --- /dev/null +++ b/gcloud/beta/backup-dr/backup-plans/delete @@ -0,0 +1,74 @@ +NAME + gcloud beta backup-dr backup-plans delete - deletes a Backup Plan + +SYNOPSIS + gcloud beta backup-dr backup-plans delete + (BACKUP_PLAN : --location=LOCATION) [--async] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Deletes a Backup Plan. + +EXAMPLES + To delete a backup plan sample-backup-plan in project sample-project and + location us-central1 , run: + + $ gcloud beta backup-dr backup-plans delete sample-backup-plan \ + --project=sample-project --location=us-central1 + +POSITIONAL ARGUMENTS + Backup Plan resource - Name of the backup plan 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 backup_plan 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 + ID of the Backup Plan or fully qualified identifier for the Backup + Plan. + + To set the name attribute: + ▸ provide the argument backup_plan 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 of the Backup Plan. + + To set the location attribute: + ▸ provide the argument backup_plan 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. The default is True. Enabled by default, use --no-async to + disable. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +BRIEF + Deletes a specific backup plan + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud backup-dr backup-plans delete + + $ gcloud alpha backup-dr backup-plans delete + diff --git a/gcloud/beta/backup-dr/backup-plans/describe b/gcloud/beta/backup-dr/backup-plans/describe new file mode 100644 index 000000000..9263beecb --- /dev/null +++ b/gcloud/beta/backup-dr/backup-plans/describe @@ -0,0 +1,68 @@ +NAME + gcloud beta backup-dr backup-plans describe - show details of the backup + plan + +SYNOPSIS + gcloud beta backup-dr backup-plans describe + (BACKUP_PLAN : --location=LOCATION) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Show all data associated with the specified backup plan. + +EXAMPLES + To view details for backup plan 'BACKUP_PLAN', run: + + $ gcloud beta backup-dr backup-plans describe BACKUP_PLAN + +POSITIONAL ARGUMENTS + Backup plan resource - Name of the backup plan 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 backup_plan 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 + ID of the backup_plan or fully qualified identifier for the + backup_plan. + + To set the backup_plan attribute: + ▸ provide the argument backup_plan on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + Location ID of the resource. + + To set the location attribute: + ▸ provide the argument backup_plan 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 backupdr/v1beta API. The full documentation for this + API can be found at: https://cloud.google.com/backup-disaster-recovery + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud backup-dr backup-plans describe + + $ gcloud alpha backup-dr backup-plans describe + diff --git a/gcloud/beta/backup-dr/backup-plans/help b/gcloud/beta/backup-dr/backup-plans/help new file mode 100644 index 000000000..8da565039 --- /dev/null +++ b/gcloud/beta/backup-dr/backup-plans/help @@ -0,0 +1,40 @@ +NAME + gcloud beta backup-dr backup-plans - manage Backup and DR backup plans + +SYNOPSIS + gcloud beta backup-dr backup-plans COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Manage Backup and DR backup plans. + +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 new Backup Plan. + + delete + (BETA) Deletes a Backup Plan. + + describe + (BETA) Show details of the backup plan. + + list + (BETA) List backup plans in the project. + + update + (BETA) Update a specific backup plan. + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud backup-dr backup-plans + + $ gcloud alpha backup-dr backup-plans + diff --git a/gcloud/beta/lifesciences/operations/list b/gcloud/beta/backup-dr/backup-plans/list similarity index 72% rename from gcloud/beta/lifesciences/operations/list rename to gcloud/beta/backup-dr/backup-plans/list index e2843d8e9..9d3f78ccd 100644 --- a/gcloud/beta/lifesciences/operations/list +++ b/gcloud/beta/backup-dr/backup-plans/list @@ -1,29 +1,32 @@ NAME - gcloud beta lifesciences operations list - list Cloud Life Sciences - operations + gcloud beta backup-dr backup-plans list - list backup plans in the project SYNOPSIS - gcloud beta lifesciences operations list [--location=LOCATION] + gcloud beta backup-dr backup-plans list [--location=LOCATION] [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) List Cloud Life Sciences operations. + (BETA) List backup plans in the project. EXAMPLES - To list all operations, run: + To list backup plans for all locations, run: - $ gcloud beta lifesciences operations list + $ gcloud beta backup-dr backup-plans list + + To list backup plans in a location "my-location", run: + + $ gcloud beta backup-dr backup-plans list --location=my-location FLAGS - Location resource - Cloud Life Sciences Location of the Operations to - list. This represents a Cloud resource. (NOTE) Some attributes are not - given arguments in this group but can be set in other ways. + Location resource - Location for which backup plans should be listed. 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 lifesciences/location with a fully specified name; + ◆ default is all locations with a fully specified name; ◆ provide the argument --project on the command line; ◆ set the property core/project. @@ -32,7 +35,7 @@ FLAGS To set the location attribute: ◆ provide the argument --location on the command line; - ◆ set the property lifesciences/location. + ◆ default is all locations . LIST COMMAND FLAGS --filter=EXPRESSION @@ -75,12 +78,14 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. API REFERENCE - This command uses the lifesciences/v2beta API. The full documentation for - this API can be found at: https://cloud.google.com/life-sciences + This command uses the backupdr/v1beta API. The full documentation for this + API can be found at: https://cloud.google.com/backup-disaster-recovery 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 alpha lifesciences operations list + $ gcloud backup-dr backup-plans list + + $ gcloud alpha backup-dr backup-plans list diff --git a/gcloud/beta/backup-dr/backup-plans/update b/gcloud/beta/backup-dr/backup-plans/update new file mode 100644 index 000000000..74eec67d2 --- /dev/null +++ b/gcloud/beta/backup-dr/backup-plans/update @@ -0,0 +1,323 @@ +NAME + gcloud beta backup-dr backup-plans update - update a specific backup plan + +SYNOPSIS + gcloud beta backup-dr backup-plans update + (BACKUP_PLAN : --location=LOCATION) + [--add-backup-rule=[PROPERTY=VALUE,...]] [--async] + [--backup-rule=[PROPERTY=VALUE,...]] + [--backup-rules-from-file=PATH_TO_FILE] + [--compute-instance-properties=[PROPERTY=VALUE,...]] + [--description=DESCRIPTION] [--disk-properties=[PROPERTY=VALUE,...]] + [--max-custom-on-demand-retention-days=MAX_CUSTOM_ON_DEMAND_RETENTION_DAYS] + [--remove-backup-rule=RULE-ID] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Update a specific backup plan in the project. It can only be updated + in regions supported by the Backup and DR Service. + +EXAMPLES + To update 2 backup rules and description of an existing backup plan + sample-backup-plan in project sample-project, at location us-central1: + + run: + + $ gcloud beta backup-dr backup-plans update sample-backup-plan \ + --project=sample-project --location=us-central1 \ + --backup-rule --backup-rule \ + --description "This is a sample backup plan" + + To add backup rules to an existing backup plan sample-backup-plan in + project sample-project, at location us-central1: + + run: + + $ gcloud beta backup-dr backup-plans update sample-backup-plan \ + --project=sample-project --location=us-central1 \ + --add-backup-rule --add-backup-rule + + To remove a backup rule with id sample-daily-rule from an existing backup + plan sample-backup-plan in project sample-project, at location us-central1: + + run: + + $ gcloud beta backup-dr backup-plans update sample-backup-plan \ + --project=sample-project --location=us-central1 \ + --remove-backup-rule sample-daily-rule + + To override backup rules in an existing backup plan sample-backup-plan in + project sample-project, at location us-central1, pass a file path + containing backup rules in YAML or JSON format: This flag is mutually + exclusive with --add-backup-rule, --remove-backup-rule and --backup-rule + flags. + + run: $ gcloud beta backup-dr backup-plans update sample-backup-plan \ + --project=sample-project --location=us-central1 \ + --backup-rules-fom-file + + Backup Rule Examples: + + 1. Hourly backup rule with hourly backup frequency of 6 hours and store it + for 30 days, and expect the backups to run only between 10:00 to 20:00 UTC + + : + rule-id=sample-hourly-rule,retention-days=30,recurrence=HOURLY,hourly-frequency=6,time-zone=UTC,backup-window-start=10,backup-window-end=20 + + Properties: + ▪ rule-id = "sample-hourly-rule" + ▪ retention-days = 30 + ▪ recurrence = HOURLY + ▪ hourly-frequency = 6 + ▪ time-zone = UTC + ▪ backup-window-start = 10 + ▪ backup-window-end = 20 + + 2. Daily backup rule with daily backup frequency of 6 hours and store it + for 7 days + + : + rule-id=sample-daily-rule,retention-days=7,recurrence=DAILY,backup-window-start=1,backup-window-end=14 + + Properties: + ▪ rule-id = "sample-daily-rule" + ▪ retention-days = 7 + ▪ recurrence = DAILY + ▪ backup-window-start = 1 + ▪ backup-window-end = 14 + + 3. Weekly backup rule with weekly backup frequency on every MONDAY & FRIDAY + and store it for 21 days + + : + rule-id=sample-weekly-rule,retention-days=21,recurrence=WEEKLY,days-of-week="MONDAY + FRIDAY",backup-window-start=10,backup-window-end=20 + + Properties: + ▪ rule-id = "sample-weekly-rule" + ▪ retention-days: 21 + ▪ recurrence = WEEKLY + ▪ days-of-week = "MONDAY FRIDAY" + ▪ backup-window-start = 10 + ▪ backup-window-end = 20 + + YAML and JSON file examples: + + YAML file example: + + backup-rules: + - rule-id: weekly-rule + retention-days: 7 + recurrence: WEEKLY + backup-window-start: 0 + backup-window-end: 23 + days-of-week: [MONDAY, TUESDAY] + time-zone: UTC + - rule-id: daily-rule + retention-days: 1 + recurrence: DAILY + backup-window-start: 1 + backup-window-end: 24 + time-zone: UTC + + JSON file example: { + "backup-rules": [ + { + "rule-id": "weekly-rule", + "retention-days": 7, + "recurrence": "WEEKLY", + "backup-window-start": 0, + "backup-window-end": 23, + "days-of-week": ["MONDAY", "TUESDAY"], + "time-zone": "UTC" + }, + { + "rule-id": "daily-rule", + "retention-days": 1, + "recurrence": "DAILY", + "backup-window-start": 1, + "backup-window-end": 24, + "time-zone": "UTC" + } + ] + } + +POSITIONAL ARGUMENTS + Backup Plan resource - Name of the backup plan to be updated. The name + must be unique for a project and 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_plan 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 + ID of the Backup Plan or fully qualified identifier for the Backup + Plan. + + To set the name attribute: + ▸ provide the argument backup_plan 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 of the Backup Plan. + + To set the location attribute: + ▸ provide the argument backup_plan on the command line with a fully + specified name; + ▸ provide the argument --location on the command line. + +FLAGS + --add-backup-rule=[PROPERTY=VALUE,...] + Parameters of backup rule to be added to the Backup Plan. This flag can + be repeated to add more backup rules. + + --async + Return immediately, without waiting for the operation in progress to + complete. The default is True. Enabled by default, use --no-async to + disable. + + --backup-rule=[PROPERTY=VALUE,...] + Full definition of an existing backup rule with updated values. The + existing backup rule is replaced by this new set of values. This flag + can be repeated to update multiple backup rules. It is not allowed to + pass the same rule-id in this flag more than once in the same command. + + Parameters for the backup rule include: + + rule-id + Name of the backup rule. The name must be unique and start with a + lowercase letter followed by up to 62 lowercase letters, numbers, + or hyphens. + + retention-days + Duration for which backup data should be retained. It must be + defined in "days". The value should be greater than or equal to the + enforced retention period set for the backup vault. + + recurrence + Frequency for the backup schedule. It must be either: HOURLY, + DAILY, WEEKLY, MONTHLY or YEARLY. + + backup-window-start + Start time of the interval during which backup jobs should be + executed. It can be defined as backup-window-start=2, that means + backup window starts at 2 a.m. The start time and end time must + have an interval of 6 hours. + + backup-window-end + End time of the interval during which backup jobs should be + executed. It can be defined as backup-window-end=14, that means + backup window ends at 2 p.m. The start time and end time must have + an interval of 6 hours. + + Jobs are queued at the beginning of the window and will be marked + as SKIPPED if they do not start by the end time. Jobs that are in + progress will not be canceled at the end time. + + time-zone + The time zone to be used for the backup schedule. The value must + exist in the IANA tz database (https://www.iana.org/time-zones). + The default value is UTC. E.g., Europe/Paris + + Following flags are mutually exclusive: + + hourly-frequency + Frequency for hourly backups. An hourly frequency of 2 means backup + jobs will run every 2 hours from start time till the end time + defined. The hourly frequency must be between 4 and 23. The value + is needed only if recurrence type is HOURLY. + + days-of-week + Days of the week when the backup job should be executed. The value + is needed if recurrence type is WEEKLY. E.g., MONDAY,TUESDAY + + days-of-month + Days of the month when the backup job should be executed. The value + is needed only if recurrence type is YEARLY. E.g.,"1,5,14" + + months + Month for the backup schedule. The value is needed only if + recurrence type is YEARLY. E.g., JANUARY, MARCH + + week-day-of-month + Recurring day of the week in the month or year when the backup job + should be executed. E.g. FIRST-SUNDAY, THIRD-MONDAY. The value can + only be provided if the recurrence type is MONTHLY or YEARLY. + Allowed values for the number of week - FIRST, SECOND, THIRD, + FOURTH, LAST. Allowed values for days of the week - MONDAY to + SUNDAY. + + E.g., + "rule-id=sample-daily-rule,recurrence=WEEKLY,backup-window-start=2,backup-window-end=14,retention-days=20,days-of-week='SUNDAY + MONDAY'" + + --backup-rules-from-file=PATH_TO_FILE + Path to a YAML or JSON file containing backup rules. Use a full or + relative path to a local file containing the value of backup_rules. + + --compute-instance-properties=[PROPERTY=VALUE,...] + Workload-specific properties for Compute Engine instance backups + generated by this plan. + + guest-flush + Indicates whether to perform a guest flush operation before taking + a compute backup. When set to true, the system will attempt to + ensure application-consistent backups. When set to false, the + system will create crash-consistent backups. Default value is + false. + + Example: --compute-instance-properties=guest-flush=true + + --description=DESCRIPTION + Provide a description of the backup plan, such as specific use cases + and relevant details, in 2048 characters or less. + + E.g., This is a backup plan that performs a daily backup at 6 p.m. and + retains data for 3 months. + + --disk-properties=[PROPERTY=VALUE,...] + Workload-specific properties for disk backups generated by this plan. + + guest-flush + Indicates whether to perform a guest flush operation before taking + a disk backup. When set to true, the system will attempt to ensure + application-consistent backups. When set to false, the system will + create crash-consistent backups. Default value is false. + + Example: --disk-properties=guest-flush=true + + --max-custom-on-demand-retention-days=MAX_CUSTOM_ON_DEMAND_RETENTION_DAYS + Configure the maximum retention period for on-demand backups. The value + must be greater than or equal to the minimum enforced retention period + set on the backup vault. + + --remove-backup-rule=RULE-ID + Name of an existing backup rule to be removed from the Backup Plan. + This flag can be repeated to remove more backup rules. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +BRIEF + Update a specific backup plan + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud backup-dr backup-plans update + + $ gcloud alpha backup-dr backup-plans update + diff --git a/gcloud/beta/backup-dr/backup-vaults/create b/gcloud/beta/backup-dr/backup-vaults/create new file mode 100644 index 000000000..6760d16b5 --- /dev/null +++ b/gcloud/beta/backup-dr/backup-vaults/create @@ -0,0 +1,151 @@ +NAME + gcloud beta backup-dr backup-vaults create - create a Backup and DR backup + vault + +SYNOPSIS + gcloud beta backup-dr backup-vaults create + (BACKUP_VAULT : --location=LOCATION) + --backup-min-enforced-retention=BACKUP_MIN_ENFORCED_RETENTION + [--access-restriction=ACCESS_RESTRICTION; default="within-org"] + [--no-async] + [--backup-retention-inheritance=BACKUP_RETENTION_INHERITANCE] + [--description=DESCRIPTION] [--effective-time=EFFECTIVE_TIME] + [--kms-key=KMS_KEY] [--labels=[KEY=VALUE,...]] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Create a Backup and DR backup vault. + +EXAMPLES + To create a new backup vault BACKUP_VAULT in location MY_LOCATION with + minimum enforced-retention for backups of 1 month and 1 day, run: + + $ gcloud beta backup-dr backup-vaults create BACKUP_VAULT \ + --location=MY_LOCATION --backup-min-enforced-retention="p1m1d" + + To create a new backup vault BACKUP_VAULT in location MY_LOCATION with + minimum enforced-retention for backups of 1 day and description + DESCRIPTION, run: + + $ gcloud beta backup-dr backup-vaults create BACKUP_VAULT \ + --location=MY_LOCATION --backup-min-enforced-retention="1d" \ + --description=DESCRIPTION + + To create a new backup vault BACKUP_VAULT in location MY_LOCATION with + minimum enforced-retention for backups of 1 day and label key1 with value + value1, run: + + $ gcloud beta backup-dr backup-vaults create BACKUP_VAULT \ + --location=MY_LOCATION --backup-min-enforced-retention="1d" \ + --labels=key1=value1 + + To create a new backup vault BACKUP_VAULT in location MY_LOCATION with + minimum enforced-retention for backups of 1 day and effective-time + "2024-03-22", run: + + $ gcloud beta backup-dr backup-vaults create BACKUP_VAULT \ + --location=MY_LOCATION --backup-min-enforced-retention="1d" \ + --effective-time="2024-03-22" + +POSITIONAL ARGUMENTS + Backup Vault resource - Name of the backup vault to create. A vault name + cannot be changed after creation. It must be between 3-63 characters long + and must be unique within the project and 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_vault 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_VAULT + ID of the Backup Vault or fully qualified identifier for the Backup + Vault. + + To set the name attribute: + ▸ provide the argument backup_vault 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 of the Backup Vault. + + To set the location attribute: + ▸ provide the argument backup_vault on the command line with a + fully specified name; + ▸ provide the argument --location on the command line. + +REQUIRED FLAGS + --backup-min-enforced-retention=BACKUP_MIN_ENFORCED_RETENTION + Backups will be kept for this minimum period before they can be + deleted. Once the effective time is reached, the enforced retention + period cannot be decreased or removed. The value must be specified in + relative time format (e.g. p1d, p1m, p1m1d). + +OPTIONAL FLAGS + --access-restriction=ACCESS_RESTRICTION; default="within-org" + Authorize certain sources and destinations for data being sent into, or + restored from, the backup vault being created. This choice determines + the type of resources that can be stored. Restricting access to within + your project or organization limits the resources to those managed + through the Google Cloud console (e.g., Compute Engine VMs). + Unrestricted access is required for resources managed through the + management console (e.g., VMware Engine VMs, databases, and file + systems). ACCESS_RESTRICTION must be one of: within-project, + within-org, unrestricted, within-org-but-unrestricted-for-ba. + + --no-async + Wait for the operation in progress to complete. + + --backup-retention-inheritance=BACKUP_RETENTION_INHERITANCE + The inheritance mode for enforced retention end time of the backup + within this backup vault. Once set, the inheritance mode cannot be + changed. Default is inherit-vault-retention. If set to + inherit-vault-retention, the backup retention period will be inherited + from the backup vault. If set to match-backup-expire-time, the backup + retention period will be the same as the backup expiration time. + BACKUP_RETENTION_INHERITANCE must be one of: inherit-vault-retention, + match-backup-expire-time. + + --description=DESCRIPTION + Optional description for the backup vault (2048 characters or less). + + --effective-time=EFFECTIVE_TIME + The time at which the enforced retention period becomes locked. This + flag is mutually exclusive with --unlock-backup-min-enforced-retention. + + --kms-key=KMS_KEY + The Cloud KMS key resource name to be used for encryption. Format: + projects/{project}/locations/{location}/keyRings/{ring}/cryptoKeys/{key} + + --labels=[KEY=VALUE,...] + Optional resource labels to represent metadata provided by the 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. + +API REFERENCE + This command uses the backupdr/v1 API. The full documentation for this API + can be found at: https://cloud.google.com/backup-disaster-recovery + +BRIEF + Creates a Backup and DR backup vault. + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud backup-dr backup-vaults create + + $ gcloud alpha backup-dr backup-vaults create + diff --git a/gcloud/beta/backup-dr/backup-vaults/delete b/gcloud/beta/backup-dr/backup-vaults/delete new file mode 100644 index 000000000..b536ec38d --- /dev/null +++ b/gcloud/beta/backup-dr/backup-vaults/delete @@ -0,0 +1,107 @@ +NAME + gcloud beta backup-dr backup-vaults delete - delete the specified Backup + Vault + +SYNOPSIS + gcloud beta backup-dr backup-vaults delete + (BACKUP_VAULT : --location=LOCATION) [--allow-missing] [--no-async] + [--ignore-backup-plan-references] [--ignore-inactive-datasources] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Delete the specified Backup Vault. + +EXAMPLES + To delete a backup vault BACKUP_VAULT in location MY_LOCATION, run: + + $ gcloud beta backup-dr backup-vaults delete BACKUP_VAULT \ + --location=MY_LOCATION + + To override restrictions against the deletion of a backup vault + BACKUP_VAULT containing inactive datasources in location MY_LOCATION, run: + + $ gcloud beta backup-dr backup-vaults delete BACKUP_VAULT \ + --location=MY_LOCATION --ignore-inactive-datasources + + To override restrictions against the deletion of a backup vault + BACKUP_VAULT containing backup plan references in location MY_LOCATION, + run: + + $ gcloud beta backup-dr backup-vaults delete BACKUP_VAULT \ + --location=MY_LOCATION --ignore-backup-plan-references + +POSITIONAL ARGUMENTS + Backup Vault resource - Name of the backup vault to delete. Before you + delete, take a look at the prerequisites here + (https://cloud.google.com/backup-disaster-recovery/docs/configuration/decommission). + 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_vault 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_VAULT + ID of the Backup Vault or fully qualified identifier for the Backup + Vault. + + To set the name attribute: + ▸ provide the argument backup_vault 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 of the Backup Vault. + + To set the location attribute: + ▸ provide the argument backup_vault on the command line with a + fully specified name; + ▸ provide the argument --location on the command line. + +FLAGS + --allow-missing + Allow idempotent deletion of backup vault. The request will still + succeed in case the backup vault does not exist. + + --no-async + Wait for the operation in progress to complete. + + --ignore-backup-plan-references + If set, the following restrictions against deletion of the backup vault + instance can be overridden: * deletion of a backup vault instance being + actively referenced by a backup plan. + + --ignore-inactive-datasources + If set, the following restrictions against deletion of the backup vault + instance can be overridden: * deletion of a backup vault instance + containing no backups,but still contains empty datasources. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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 backupdr/v1 API. The full documentation for this API + can be found at: https://cloud.google.com/backup-disaster-recovery + +BRIEF + Deletes a specific backup vault + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud backup-dr backup-vaults delete + + $ gcloud alpha backup-dr backup-vaults delete + diff --git a/gcloud/beta/backup-dr/backup-vaults/describe b/gcloud/beta/backup-dr/backup-vaults/describe new file mode 100644 index 000000000..ab44a85ac --- /dev/null +++ b/gcloud/beta/backup-dr/backup-vaults/describe @@ -0,0 +1,71 @@ +NAME + gcloud beta backup-dr backup-vaults describe - show the metadata for a + Backup and DR backup vault + +SYNOPSIS + gcloud beta backup-dr backup-vaults describe + (BACKUP_VAULT : --location=LOCATION) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Show the metadata for a Backup and DR backup vault. + +EXAMPLES + To view details associated with backup vault 'BACKUP_VAULT', run: + + $ gcloud beta backup-dr backup-vaults describe BACKUP_VAULT + +POSITIONAL ARGUMENTS + Backup Vault resource - Name of the backup vault to retreive metadata of. + 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_vault 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_VAULT + ID of the Backup Vault or fully qualified identifier for the Backup + Vault. + + To set the name attribute: + ▸ provide the argument backup_vault 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 of the Backup Vault. + + To set the location attribute: + ▸ provide the argument backup_vault 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 backupdr/v1 API. The full documentation for this API + can be found at: https://cloud.google.com/backup-disaster-recovery + +BRIEF + Show the metadata for a Backup and DR backup vault. + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud backup-dr backup-vaults describe + + $ gcloud alpha backup-dr backup-vaults describe + diff --git a/gcloud/beta/backup-dr/backup-vaults/help b/gcloud/beta/backup-dr/backup-vaults/help new file mode 100644 index 000000000..470dee844 --- /dev/null +++ b/gcloud/beta/backup-dr/backup-vaults/help @@ -0,0 +1,40 @@ +NAME + gcloud beta backup-dr backup-vaults - manage Backup and DR backup vaults + +SYNOPSIS + gcloud beta backup-dr backup-vaults COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Manage Backup and DR backup vaults. + +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 and DR backup vault. + + delete + (BETA) Delete the specified Backup Vault. + + describe + (BETA) Show the metadata for a Backup and DR backup vault. + + list + (BETA) List Backup and DR backup vaults. + + update + (BETA) Update a Backup and DR backup vault. + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud backup-dr backup-vaults + + $ gcloud alpha backup-dr backup-vaults + diff --git a/gcloud/alpha/dataplex/data-attribute-bindings/list b/gcloud/beta/backup-dr/backup-vaults/list similarity index 73% rename from gcloud/alpha/dataplex/data-attribute-bindings/list rename to gcloud/beta/backup-dr/backup-vaults/list index 1b1f08dbb..383ab4dcc 100644 --- a/gcloud/alpha/dataplex/data-attribute-bindings/list +++ b/gcloud/beta/backup-dr/backup-vaults/list @@ -1,30 +1,32 @@ NAME - gcloud alpha dataplex data-attribute-bindings list - list Data Attribute - Bindings + gcloud beta backup-dr backup-vaults list - list Backup and DR backup vaults SYNOPSIS - gcloud alpha dataplex data-attribute-bindings list [--location=LOCATION] + gcloud beta backup-dr backup-vaults list [--location=LOCATION] [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) List Data Attribute Bindings. + (BETA) List Backup and DR backup vaults. EXAMPLES - To List all the Data Attribute Bindings in project test-dataplex at - location us-central1, run: + To list backup vaults in all location, run: - $gcloud alpha dataplex data-attribute-bindings list --project=test-dataplex --location=us-central1 + $ gcloud beta backup-dr backup-vaults list + + To list backup vaults in a location ''my-location'', run: + + $ gcloud beta backup-dr backup-vaults list --location=my-location FLAGS - Location resource - Location in which to list Data Attribute Bindings. + Location resource - Location for which backup vaults should be listed. 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 dataplex/location with a fully specified name; + ◆ Defaults to all locations with a fully specified name; ◆ provide the argument --project on the command line; ◆ set the property core/project. @@ -33,7 +35,7 @@ FLAGS To set the location attribute: ◆ provide the argument --location on the command line; - ◆ set the property dataplex/location. + ◆ Defaults to all locations. LIST COMMAND FLAGS --filter=EXPRESSION @@ -76,12 +78,17 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. API REFERENCE - This command uses the dataplex/v1 API. The full documentation for this API - can be found at: https://cloud.google.com/dataplex/docs + This command uses the backupdr/v1 API. The full documentation for this API + can be found at: https://cloud.google.com/backup-disaster-recovery + +BRIEF + List Backup and DR backup vaults. NOTES - This command is currently in alpha and might change without notice. If this - command fails 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 command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud backup-dr backup-vaults list + + $ gcloud alpha backup-dr backup-vaults list diff --git a/gcloud/beta/backup-dr/backup-vaults/update b/gcloud/beta/backup-dr/backup-vaults/update new file mode 100644 index 000000000..f0417b24e --- /dev/null +++ b/gcloud/beta/backup-dr/backup-vaults/update @@ -0,0 +1,152 @@ +NAME + gcloud beta backup-dr backup-vaults update - update a Backup and DR backup + vault + +SYNOPSIS + gcloud beta backup-dr backup-vaults update + (BACKUP_VAULT : --location=LOCATION) + [--access-restriction=ACCESS_RESTRICTION] [--no-async] + [--backup-min-enforced-retention=BACKUP_MIN_ENFORCED_RETENTION] + [--description=DESCRIPTION] [--effective-time=EFFECTIVE_TIME] + [--force-update] [--force-update-access-restriction] + [--unlock-backup-min-enforced-retention] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Update a Backup and DR backup vault. + +EXAMPLES + To update a backup vault BACKUP_VAULT in location MY_LOCATION with one + update field, run: + + $ gcloud beta backup-dr backup-vaults update BACKUP_VAULT \ + --location=MY_LOCATION --effective-time="2024-03-22" + + To update a backup vault BACKUP_VAULT in location MY_LOCATION with multiple + update fields, run: + + $ gcloud beta backup-dr backup-vaults update BACKUP_VAULT \ + --location=MY_LOCATION \ + --backup-min-enforced-retention="400000s" \ + --description="Updated backup vault" + +POSITIONAL ARGUMENTS + Backup Vault resource - Name of the existing backup vault 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 backup_vault 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_VAULT + ID of the Backup Vault or fully qualified identifier for the Backup + Vault. + + To set the name attribute: + ▸ provide the argument backup_vault 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 of the Backup Vault. + + To set the location attribute: + ▸ provide the argument backup_vault on the command line with a + fully specified name; + ▸ provide the argument --location on the command line. + +FLAGS + --access-restriction=ACCESS_RESTRICTION + Authorize certain sources and destinations for data being sent into, or + restored from the current backup vault. + + Access restrictions can be modified to be more or less restrictive. + + ::: More restrictive access restriction update will fail by default if there will be non compliant Data Sources. + To allow such updates, use the --force-update-access-restriction flag. + ::: For Google Cloud Console resources, the following changes are allowed to make access restrictions more restrictive: + * `UNRESTRICTED` to `WITHIN_PROJECT` / `WITHIN_ORG_BUT_UNRESTRICTED_FOR_BA` / `WITHIN_ORGANIZATION` + * `WITHIN_PROJECT` to `WITHIN_ORGANIZATION` / `WITHIN_ORG_BUT_UNRESTRICTED_FOR_BA` + + ::: For Management Server resources, the following changes are allowed to make access restrictions more restrictive: + * `UNRESTRICTED` to `WITHIN_PROJECT` / `WITHIN_ORG_BUT_UNRESTRICTED_FOR_BA` / `WITHIN_ORGANIZATION` + * `WITHIN_PROJECT` to `WITHIN_ORGANIZATION` / `WITHIN_ORG_BUT_UNRESTRICTED_FOR_BA` + + ::: For both Google Cloud Console and Management Server resources, the following changes are allowed to make access restrictions more restrictive: + * `UNRESTRICTED` to `WITHIN_PROJECT` / `WITHIN_ORG_BUT_UNRESTRICTED_FOR_BA` / `WITHIN_ORGANIZATION` + * `WITHIN_PROJECT` to `WITHIN_ORGANIZATION` / `WITHIN_ORG_BUT_UNRESTRICTED_FOR_BA` + + ::: For Google Cloud Console resources, the following changes are allowed to make access restrictions less restrictive: + * `WITHIN_ORGANIZATION` to `UNRESTRICTED` / `WITHIN_ORG_BUT_UNRESTRICTED_FOR_BA` + * `WITHIN_PROJECT` to `UNRESTRICTED` + * `WITHIN_ORG_BUT_UNRESTRICTED_FOR_BA` to `UNRESTRICTED` + + ::: For Management Server resources, the following changes are allowed to make access restrictions less restrictive: + * `WITHIN_ORG_BUT_UNRESTRICTED_FOR_BA` to `UNRESTRICTED` + + ACCESS_RESTRICTION must be one of: within-project, within-org, + unrestricted, within-org-but-unrestricted-for-ba. + + --no-async + Wait for the operation in progress to complete. + + --backup-min-enforced-retention=BACKUP_MIN_ENFORCED_RETENTION + Backups will be kept for this minimum period before they can be + deleted. Once the effective time is reached, the enforced retention + period cannot be decreased or removed. The value must be specified in + relative time format (e.g. p1d, p1m, p1m1d). + + --description=DESCRIPTION + Optional description for the backup vault (2048 characters or less). + + --effective-time=EFFECTIVE_TIME + The time at which the enforced retention period becomes locked. This + flag is mutually exclusive with --unlock-backup-min-enforced-retention. + + --force-update + If set, allow update to extend the minimum enforced retention for + backup vault. This overrides the restriction against conflicting + retention periods. This conflict may occur when the expiration schedule + defined by the associated backup plan is shorter than the minimum + retention set by the backup vault. + + --force-update-access-restriction + If set, the access restriction can be updated even if there are + non-compliant data sources. Backups for those data sources will fail + afterward. + + --unlock-backup-min-enforced-retention + Removes the lock on the backup minimum enforced retention period, and + resets the effective time. When unlocked, the enforced retention period + can be changed at any time. This flag is mutually exclusive with + --effective-time. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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 backupdr/v1 API. The full documentation for this API + can be found at: https://cloud.google.com/backup-disaster-recovery + +BRIEF + Updates a Backup and DR backup vault. + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud backup-dr backup-vaults update + + $ gcloud alpha backup-dr backup-vaults update + diff --git a/gcloud/beta/backup-dr/backups/delete b/gcloud/beta/backup-dr/backups/delete new file mode 100644 index 000000000..bc35d71a7 --- /dev/null +++ b/gcloud/beta/backup-dr/backups/delete @@ -0,0 +1,92 @@ +NAME + gcloud beta backup-dr backups delete - delete the specified Backup + +SYNOPSIS + gcloud beta backup-dr backups delete + (BACKUP : --backup-vault=BACKUP_VAULT + --data-source=DATA_SOURCE --location=LOCATION) [--async] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Delete the specified Backup. + +EXAMPLES + To delete a backup sample-backup in backup vault sample-vault, data source + sample-ds, project sample-project and location us-central1 , run: + + $ gcloud beta backup-dr backups delete sample-backup \ + --backup-vault=sample-vault --data-source=sample-ds \ + --project=sample-project --location=us-central1 + +POSITIONAL ARGUMENTS + Backup resource - Name of the backup 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 backup 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 + ID of the Backup or fully qualified identifier for the Backup. + + To set the name attribute: + ▸ provide the argument backup on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --backup-vault=BACKUP_VAULT + The ID of the Backup Vault. + + To set the backup-vault attribute: + ▸ provide the argument backup on the command line with a fully + specified name; + ▸ provide the argument --backup-vault on the command line. + + --data-source=DATA_SOURCE + The ID of the Data Source. + + To set the data-source attribute: + ▸ provide the argument backup on the command line with a fully + specified name; + ▸ provide the argument --data-source on the command line. + + --location=LOCATION + The location of the Backup. + + To set the location attribute: + ▸ provide the argument backup 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. The default is True. Enabled by default, use --no-async to + disable. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +BRIEF + Deletes a specific backup + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud backup-dr backups delete + + $ gcloud alpha backup-dr backups delete + diff --git a/gcloud/beta/backup-dr/backups/describe b/gcloud/beta/backup-dr/backups/describe new file mode 100644 index 000000000..74cc8821e --- /dev/null +++ b/gcloud/beta/backup-dr/backups/describe @@ -0,0 +1,83 @@ +NAME + gcloud beta backup-dr backups describe - show details of the backup + +SYNOPSIS + gcloud beta backup-dr backups describe + (BACKUP : --backup-vault=BACKUP_VAULT + --data-source=DATA_SOURCE --location=LOCATION) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Show all data associated with the specified backup. + +EXAMPLES + To view details for backup 'BACKUP', run: + + $ gcloud beta backup-dr backups describe BACKUP + +POSITIONAL ARGUMENTS + Backup resource - Name of the backup 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 backup 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 + ID of the backup or fully qualified identifier for the backup. + + To set the backup attribute: + ▸ provide the argument backup on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --backup-vault=BACKUP_VAULT + The ID of the Backup Vault. + + To set the backup-vault attribute: + ▸ provide the argument backup on the command line with a fully + specified name; + ▸ provide the argument --backup-vault on the command line. + + --data-source=DATA_SOURCE + The ID of the Data Source. + + To set the data-source attribute: + ▸ provide the argument backup on the command line with a fully + specified name; + ▸ provide the argument --data-source on the command line. + + --location=LOCATION + Location ID of the resource. + + To set the location attribute: + ▸ provide the argument backup 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 backupdr/v1beta API. The full documentation for this + API can be found at: https://cloud.google.com/backup-disaster-recovery + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud backup-dr backups describe + + $ gcloud alpha backup-dr backups describe + diff --git a/gcloud/beta/backup-dr/backups/fetch-for-resource-type b/gcloud/beta/backup-dr/backups/fetch-for-resource-type new file mode 100644 index 000000000..485b3fb9d --- /dev/null +++ b/gcloud/beta/backup-dr/backups/fetch-for-resource-type @@ -0,0 +1,118 @@ +NAME + gcloud beta backup-dr backups fetch-for-resource-type - fetch Backups for a + given resource type and location + +SYNOPSIS + gcloud beta backup-dr backups fetch-for-resource-type RESOURCE_TYPE + (--data-source=DATA_SOURCE + : --backup-vault=BACKUP_VAULT --location=LOCATION) + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Fetch Backups for a given resource type and location. List backups + for the specified resource type for a data source. + +EXAMPLES + To list backups for Cloud SQL instance resources for data source + my-data-source with location us-central1 under backup vault, my-vault. + + $ gcloud beta backup-dr backups fetch-for-resource-type \ + sqladmin.googleapis.com/Instance --data-source=my-data-source \ + --backup-vault=my-vault --location=us-central1 + +POSITIONAL ARGUMENTS + RESOURCE_TYPE + Resource type for which backup plan associations should be fetched. + +REQUIRED FLAGS + Data Source resource - Data source for which backups should be fetched. + 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-source 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-source=DATA_SOURCE + ID of the Data Source or fully qualified identifier for the Data + Source. + + To set the data-source attribute: + ▸ provide the argument --data-source on the command line. + + This flag argument must be specified if any of the other arguments in + this group are specified. + + --backup-vault=BACKUP_VAULT + The ID of the Backup Vault. + + To set the backup-vault attribute: + ▸ provide the argument --data-source on the command line with a + fully specified name; + ▸ provide the argument --backup-vault on the command line. + + --location=LOCATION + The location of the Data Source. + + To set the location attribute: + ▸ provide the argument --data-source 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. + +BRIEF + List backups in a specified location and resource type in a project. + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud backup-dr backups fetch-for-resource-type + + $ gcloud alpha backup-dr backups fetch-for-resource-type + diff --git a/gcloud/beta/backup-dr/backups/help b/gcloud/beta/backup-dr/backups/help new file mode 100644 index 000000000..d3f0ea99e --- /dev/null +++ b/gcloud/beta/backup-dr/backups/help @@ -0,0 +1,46 @@ +NAME + gcloud beta backup-dr backups - manage Backup and DR backups + +SYNOPSIS + gcloud beta backup-dr backups GROUP | COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Manage Backup and DR backups. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +GROUPS + GROUP is one of the following: + + restore + (BETA) Manage restore operations for resources. + +COMMANDS + COMMAND is one of the following: + + delete + (BETA) Delete the specified Backup. + + describe + (BETA) Show details of the backup. + + fetch-for-resource-type + (BETA) Fetch Backups for a given resource type and location. + + list + (BETA) List Backups. + + update + (BETA) Update the specified Backup. + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud backup-dr backups + + $ gcloud alpha backup-dr backups + diff --git a/gcloud/beta/backup-dr/backups/list b/gcloud/beta/backup-dr/backups/list new file mode 100644 index 000000000..4ea36205c --- /dev/null +++ b/gcloud/beta/backup-dr/backups/list @@ -0,0 +1,116 @@ +NAME + gcloud beta backup-dr backups list - list Backups + +SYNOPSIS + gcloud beta backup-dr backups list + [--backup-vault=BACKUP_VAULT + --data-source=DATA_SOURCE --location=LOCATION] [--filter=EXPRESSION] + [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Displays all backups in a project. + +EXAMPLES + To list backups for all data sources, backup vaults and locations, run: + + $ gcloud beta backup-dr backups list + + To list all backups for a data source my-data-source and a backup vault + my-vault in a location my-location, run: + + $ gcloud beta backup-dr backups list --data-source=my-data-source \ + --backup-vault=my-vault --location=my-location + +FLAGS + DataSource resource - Data source to list backups from. 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-source on the command line with a fully + specified name; + ◆ default is all data sources with a fully specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + --backup-vault=BACKUP_VAULT + The ID of the Backup Vault. + + To set the backup-vault attribute: + ◆ provide the argument --data-source on the command line with a fully + specified name; + ◆ default is all data sources with a fully specified name; + ◆ provide the argument --backup-vault on the command line; + ◆ default is all backup vaults . + + --data-source=DATA_SOURCE + ID of the dataSource or fully qualified identifier for the dataSource. + + To set the data-source attribute: + ◆ provide the argument --data-source on the command line; + ◆ default is all data sources . + + --location=LOCATION + Location ID of the resource. + + To set the location attribute: + ◆ provide the argument --data-source on the command line with a fully + specified name; + ◆ default is all data sources with a fully specified name; + ◆ provide the argument --location on the command line; + ◆ default is all locations . + +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 backupdr/v1beta API. The full documentation for this + API can be found at: https://cloud.google.com/backup-disaster-recovery + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud backup-dr backups list + + $ gcloud alpha backup-dr backups list + diff --git a/gcloud/beta/backup-dr/backups/restore/compute b/gcloud/beta/backup-dr/backups/restore/compute new file mode 100644 index 000000000..4ba9532bf --- /dev/null +++ b/gcloud/beta/backup-dr/backups/restore/compute @@ -0,0 +1,434 @@ +NAME + gcloud beta backup-dr backups restore compute - restores a Compute Engine + VM Backup + +SYNOPSIS + gcloud beta backup-dr backups restore compute + (BACKUP : --backup-vault=BACKUP_VAULT + --data-source=DATA_SOURCE --location=LOCATION) --name=NAME + --target-project=TARGET_PROJECT --target-zone=TARGET_ZONE + [--accelerator=[count=COUNT],[type=TYPE]] [--async] + [--[no-]can-ip-forward] [--clear-encryption-key] + [--confidential-compute] [--create-disk=[PROPERTY=VALUE,...]] + [--[no-]deletion-protection] [--description=DESCRIPTION] + [--[no-]enable-display-device] [--[no-]enable-uefi-networking] + [--hostname=HOSTNAME] [--instance-kms-key=INSTANCE_KMS_KEY] + [--instance-termination-action=INSTANCE_TERMINATION_ACTION] + [--key-revocation-action-type=POLICY] [--labels=[KEY=VALUE,...]] + [--local-ssd-recovery-timeout=LOCAL_SSD_RECOVERY_TIMEOUT] + [--machine-type=MACHINE_TYPE] [--maintenance-policy=MAINTENANCE_POLICY] + [--metadata=KEY=VALUE,[KEY=VALUE,...]] [--min-cpu-platform=PLATFORM] + [--min-node-cpu=MIN_NODE_CPU] + [--network-interface=[PROPERTY=VALUE,...]] + [--network-performance-configs=[PROPERTY=VALUE,...]] + [--[no-]preemptible] + [--private-ipv6-google-access-type=PRIVATE_IPV6_GOOGLE_ACCESS_TYPE] + [--provisioning-model=PROVISIONING_MODEL] + [--resource-manager-tags=[KEY=VALUE,...]] + [--resource-policies=RESOURCE_POLICY,[...]] [--[no-]restart-on-failure] + [--service-account=SERVICE_ACCOUNT] [--tags=TAG,[TAG,...]] + [--threads-per-core=THREADS_PER_CORE] + [--visible-core-count=VISIBLE_CORE_COUNT] + [--reservation=RESERVATION --reservation-affinity=RESERVATION_AFFINITY] + [--scopes=[SCOPE,...] | --no-scopes] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Restores a Compute Engine VM Backup. + +EXAMPLES + To restore a backup sample-backup in project sample-project and location + us-central1, with sample-data-store and sample-backup-vault, and additional + target properties, run: + + $ gcloud beta backup-dr backups restore compute sample-backup \ + --project=sample-project --location=us-central1 \ + --backup-vault=sample-backup-vault \ + --data-source=sample-data-source -- + +POSITIONAL ARGUMENTS + Backup resource - The backup of a resource to be restored. 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 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 + ID of the Backup or fully qualified identifier for the Backup. + + To set the name attribute: + ▸ provide the argument backup on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --backup-vault=BACKUP_VAULT + The ID of the Backup Vault. + + To set the backup-vault attribute: + ▸ provide the argument backup on the command line with a fully + specified name; + ▸ provide the argument --backup-vault on the command line. + + --data-source=DATA_SOURCE + The ID of the Data Source. + + To set the data-source attribute: + ▸ provide the argument backup on the command line with a fully + specified name; + ▸ provide the argument --data-source on the command line. + + --location=LOCATION + The location of the Backup. + + To set the location attribute: + ▸ provide the argument backup on the command line with a fully + specified name; + ▸ provide the argument --location on the command line. + +REQUIRED FLAGS + --name=NAME + Name of the restored Compute Instance. + + --target-project=TARGET_PROJECT + Project where the restore should happen. + + --target-zone=TARGET_ZONE + Zone where the target instance is restored. + +OPTIONAL FLAGS + --accelerator=[count=COUNT],[type=TYPE] + Attaches accelerators (e.g. GPUs) to the instances. + + type + The specific type (e.g. nvidia-tesla-k80 for nVidia Tesla K80) of + accelerator to attach to the instances. Use 'gcloud compute + accelerator-types list' to learn about all available accelerator + types. + + count + Number of accelerators to attach to each instance. The default + value is 1. + + --async + Return immediately, without waiting for the operation in progress to + complete. The default is True. Enabled by default, use --no-async to + disable. + + --[no-]can-ip-forward + If provided, allows the restored instances to send and receive packets + with non-matching destination or source IP addresses. Use + --can-ip-forward to enable and --no-can-ip-forward to disable. + + --clear-encryption-key + Clears the CMEK encryption of the restored disks and defaults to GMEK + unless the kms-key is specified in the --create-disk flag. + + --confidential-compute + The restored instance boots with Confidential Computing enabled. + Confidential Computing is based on Secure Encrypted Virtualization + (SEV), an AMD virtualization feature for running confidential + instances. + + --create-disk=[PROPERTY=VALUE,...] + Creates and attaches persistent disks to the instances. + + name: Specifies the name of the disk. + + replica-zones: Required for each regional disk associated with the + instance. Specify the URLs of the zones where the disk should be + replicated to. You must provide exactly two replica zones, and one zone + must be the same as the instance zone. + + device-name: Device name of the disk from the source instance. + + kms-key: The Cloud KMS key resource name to be used for encryption. If + supplied, it will encrypt the disk with the given key, if not supplied, + the restored disk will use the encryption of the disk from the source + instance. The device-name field must be provided for kms-key to take + effect. Format: + 'projects/{project}/locations/{location}/keyRings/{ring}/cryptoKeys/{key}' + + --[no-]deletion-protection + Enables deletion protection for the restored instance. Use + --deletion-protection to enable and --no-deletion-protection to + disable. + + --description=DESCRIPTION + Specifies a textual description of the restored instance. + + --[no-]enable-display-device + Enable a display device on the restored VM instances. Disabled by + default. Use --enable-display-device to enable and + --no-enable-display-device to disable. + + --[no-]enable-uefi-networking + If set to true, enables UEFI networking for the instance creation. Use + --enable-uefi-networking to enable and --no-enable-uefi-networking to + disable. + + --hostname=HOSTNAME + Specify the hostname of the restore instance to be created. The + specified hostname must be RFC1035 compliant. If hostname is not + specified, the default hostname is + [INSTANCE_NAME].c.[TARGET_PROJECT_ID].internal when using the global + DNS, and [INSTANCE_NAME].[ZONE].c.[TARGET_PROJECT_ID].internal when + using zonal DNS. + + --instance-kms-key=INSTANCE_KMS_KEY + The Cloud KMS (Key Management Service) cryptokey that will be used to + protect the restored instance. + + Provide the full resource name of the cryptokey in the format: + projects//locations//keyRings//cryptoKeys/ + + --instance-termination-action=INSTANCE_TERMINATION_ACTION + Specifies the termination action that will be taken upon VM preemption + (--provisioning-model=SPOT) or automatic instance termination + (--max-run-duration or --termination-time). + + INSTANCE_TERMINATION_ACTION must be one of: + + DELETE + Permanently delete the VM. + STOP + Default only for Spot VMs. Stop the VM without preserving memory. + The VM can be restarted later. + + --key-revocation-action-type=POLICY + Specifies the behavior of the instance when the KMS key of one of its + attached disks is revoked. The default is none. POLICY must be one of: + ◆ none No operation is performed. + ◆ stop The instance is stopped when the KMS key of one of its + attached disks is revoked. + + --labels=[KEY=VALUE,...] + List of label KEY=VALUE pairs to add. + + 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. + + --local-ssd-recovery-timeout=LOCAL_SSD_RECOVERY_TIMEOUT + Specifies the maximum amount of time a Local SSD VM should wait while + recovery of the Local SSD state is attempted. Its value should be in + between 0 and 168 hours with hour granularity and the default value + being 1 hour. + + --machine-type=MACHINE_TYPE + Specifies the machine type used for the restored instance. To get a + list of available machine types, run 'gcloud compute machine-types + list'. If unspecified, the default type will be based on the source + instance. + + This can either be the fully qualified path or the name. For example: + ◆ --machine-type=projects/my-project/zones/us-central1-a/machineTypes/n1-standard-1 + ◆ --machine-type=n1-standard-1 + + --maintenance-policy=MAINTENANCE_POLICY + Specifies the behavior of the VMs when their host machines undergo + maintenance. The default is MIGRATE. For more information, see + https://cloud.google.com/compute/docs/instances/host-maintenance-options. + MAINTENANCE_POLICY must be one of: + + MIGRATE + The instances should be migrated to a new host. This will + temporarily impact the performance of instances during a migration + event. + TERMINATE + The instances should be terminated. + + --metadata=KEY=VALUE,[KEY=VALUE,...] + Metadata to be made available to the guest operating system running on + the instances. Each metadata entry is a key/value pair separated by an + equals sign. Each metadata key must be unique and have a max of 128 + bytes in length. Each value must have a max of 256 KB in length. + Multiple arguments can be passed to this flag, e.g., --metadata + key-1=value-1,key-2=value-2,key-3=value-3. The combined total size for + all metadata entries is 512 KB. + + In images that have Compute Engine tools installed on them, such as the + official images (https://cloud.google.com/compute/docs/images), the + following metadata keys have special meanings: + + startup-script + Specifies a script that will be executed by the instances once they + start running. + + startup-script-url + Same as startup-script except that the script contents are pulled + from a publicly-accessible location on the web. + + For startup scripts on Windows instances, the following metadata + keys have special meanings: windows-startup-script-url, + windows-startup-script-cmd, windows-startup-script-bat, + windows-startup-script-ps1, sysprep-specialize-script-url, + sysprep-specialize-script-cmd, sysprep-specialize-script-bat, and + sysprep-specialize-script-ps1. For more information, see Running + startup scripts + (https://cloud.google.com/compute/docs/startupscript). + + --min-cpu-platform=PLATFORM + When specified, the VM will be scheduled on host with specified CPU + architecture or a newer one. To list available CPU platforms in given + zone, run: + + $ gcloud compute zones describe ZONE \ + --format="value(availableCpuPlatforms)" + + Default setting is "AUTOMATIC". + + CPU platform selection is available only in selected zones. + + You can find more information on-line: + https://cloud.google.com/compute/docs/instances/specify-min-cpu-platform + + --min-node-cpu=MIN_NODE_CPU + Minimum number of virtual CPUs this instance will consume when running + on a sole-tenant node. + + --network-interface=[PROPERTY=VALUE,...] + Adds a network interface to the instance. This flag can be repeated to + specify multiple network interfaces. The following keys are allowed: + network, subnet, private-network-ip, internal-ipv6-address, + internal-ipv6-prefix-length, address, external-ipv6-address, + external-ipv6-prefix-length, network-tier, aliases, stack-type, + queue-count, nic-type, network-attachment + + --network-performance-configs=[PROPERTY=VALUE,...] + Configures network performance settings for the restored instance. If + this flag is not specified, the restored instance will be created with + its source instance's network performance configuration. + + total-egress-bandwidth-tier + Total egress bandwidth is the available outbound bandwidth from a + VM, regardless of whether the traffic is going to internal IP or + external IP destinations. The following tier values are allowed: + [DEFAULT, TIER_1] + + --[no-]preemptible + If provided, instances will be preemptible and time-limited. Instances + might be preempted to free up resources for standard VM instances, and + will only be able to run for a limited amount of time. Preemptible + instances can not be restarted and will not migrate. Use --preemptible + to enable and --no-preemptible to disable. + + --private-ipv6-google-access-type=PRIVATE_IPV6_GOOGLE_ACCESS_TYPE + The private IPv6 Google access type for the restored VM. + PRIVATE_IPV6_GOOGLE_ACCESS_TYPE must be one of: inherit-subnetwork, + enable-bidirectional-access, enable-outbound-vm-access + + --provisioning-model=PROVISIONING_MODEL + Specifies provisioning model, which determines price, obtainability, + and runtime for the restored VM instance. PROVISIONING_MODEL must be + one of: + + SPOT + Spot VMs are spare capacity; Spot VMs are discounted to have much + lower prices than standard VMs but have no guaranteed runtime. Spot + VMs are the new version of preemptible VM instances, except Spot + VMs do not have a 24-hour maximum runtime. + STANDARD + Default. Standard provisioning model for VM instances, which has + user-controlled runtime but no Spot discounts. + + --resource-manager-tags=[KEY=VALUE,...] + Specifies a list of resource manager tags to apply to the instance. + + --resource-policies=RESOURCE_POLICY,[...] + A list of resource policy names to be added to the instance. The + policies must exist in the same region as the instance. + + --[no-]restart-on-failure + The instances will be restarted if they are terminated by Compute + Engine. This does not affect terminations performed by the user. Use + --restart-on-failure to enable and --no-restart-on-failure to disable. + + --service-account=SERVICE_ACCOUNT + A service account is an identity attached to the instance. Its access + tokens can be accessed through the instance metadata server and are + used to authenticate applications on the instance. The account can be + set using an email address corresponding to the required service + account. If not provided, the instance will use the project's default + service account. + + --tags=TAG,[TAG,...] + Specifies a list of tags to apply to the instance. These tags allow + network firewall rules and routes to be applied to specified VM + instances. See gcloud compute firewall-rules create(1) for more + details. + + --threads-per-core=THREADS_PER_CORE + The number of visible threads per physical core. To disable + simultaneous multithreading (SMT) set this to 1. Valid values are: 1 or + 2. + + For more information about configuring SMT, see: + https://cloud.google.com/compute/docs/instances/configuring-simultaneous-multithreading. + + --visible-core-count=VISIBLE_CORE_COUNT + The number of physical cores to expose to the instance's guest + operating system. The number of virtual CPUs visible to the instance's + guest operating system is this number of cores multiplied by the + instance's count of visible threads per physical core. + + Specifies the reservation for the instance. + + --reservation=RESERVATION + The name of the reservation, required when + --reservation-affinity=specific. + + --reservation-affinity=RESERVATION_AFFINITY + Specifies the reservation affinity of the instance. + RESERVATION_AFFINITY must be one of: + + any + Consume any available, matching reservation. + none + Do not consume from any reserved capacity. + specific + Must consume from a specific reservation. + + At most one of these can be specified: + + --scopes=[SCOPE,...] + If not provided, the instance will be assigned the default scopes, + described below. However, if neither --scopes nor --no-scopes are + specified and the project has no default service account, then the + instance will be created with no scopes. Note that the level of + access that a service account has is determined by a combination of + access scopes and IAM roles so you must configure both access scopes + and IAM roles for the service account to work properly. SCOPE can be + either the full URI of the scope or an alias. Default scopes are + assigned to all instances. Available aliases are: + https://cloud.google.com/sdk/gcloud/reference/compute/instances/create#--scopes + + --no-scopes + Create the instance with no scopes. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +BRIEF + Restores the specified backup + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud backup-dr backups restore compute + + $ gcloud alpha backup-dr backups restore compute + diff --git a/gcloud/beta/backup-dr/backups/restore/disk b/gcloud/beta/backup-dr/backups/restore/disk new file mode 100644 index 000000000..0120d46ab --- /dev/null +++ b/gcloud/beta/backup-dr/backups/restore/disk @@ -0,0 +1,221 @@ +NAME + gcloud beta backup-dr backups restore disk - restores a Compute Disk Backup + +SYNOPSIS + gcloud beta backup-dr backups restore disk + (BACKUP : --backup-vault=BACKUP_VAULT + --data-source=DATA_SOURCE --location=LOCATION) --name=NAME + --target-project=TARGET_PROJECT [--access-mode=ACCESS_MODE] + [--architecture=ARCHITECTURE] [--async] [--clear-encryption-key] + [--confidential-compute] [--description=DESCRIPTION] + [--guest-os-features=[GUEST_OS_FEATURES,...]] [--kms-key=KMS_KEY] + [--labels=[KEY=VALUE,...]] [--licenses=LICENSE,[LICENSE,...]] + [--provisioned-iops=PROVISIONED_IOPS] + [--provisioned-throughput=PROVISIONED_THROUGHPUT] + [--replica-zones=ZONE,ZONE] [--resource-policies=RESOURCE_POLICY,[...]] + [--size=SIZE] [--storage-pool=STORAGE_POOL] + [--target-region=TARGET_REGION] [--target-zone=TARGET_ZONE] + [--type=TYPE] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Restores a Compute Disk Backup. + +EXAMPLES + To restore a backup sample-backup in project sample-project and location + us-central1, with sample-data-store and sample-backup-vault, and additional + target properties, run: + + $ gcloud beta backup-dr backups restore disk sample-backup \ + --project=sample-project --location=us-central1 \ + --backup-vault=sample-backup-vault \ + --data-source=sample-data-source -- + +POSITIONAL ARGUMENTS + Backup resource - The backup of a resource to be restored. 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 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 + ID of the Backup or fully qualified identifier for the Backup. + + To set the name attribute: + ▸ provide the argument backup on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --backup-vault=BACKUP_VAULT + The ID of the Backup Vault. + + To set the backup-vault attribute: + ▸ provide the argument backup on the command line with a fully + specified name; + ▸ provide the argument --backup-vault on the command line. + + --data-source=DATA_SOURCE + The ID of the Data Source. + + To set the data-source attribute: + ▸ provide the argument backup on the command line with a fully + specified name; + ▸ provide the argument --data-source on the command line. + + --location=LOCATION + The location of the Backup. + + To set the location attribute: + ▸ provide the argument backup on the command line with a fully + specified name; + ▸ provide the argument --location on the command line. + +REQUIRED FLAGS + --name=NAME + Name of the restored Disk. + + --target-project=TARGET_PROJECT + Project where the restore should happen. + +OPTIONAL FLAGS + --access-mode=ACCESS_MODE + Specifies how VMs attached to the disk can access the data on the disk. + To grant read-only access to multiple VMs attached to the disk, set + access-mode to READ_ONLY_MANY. To grant read-write access to only one + VM attached to the disk, use READ_WRITE_SINGLE. READ_WRITE_SINGLE is + used if omitted. ACCESS_MODE must be one of: READ_ONLY_MANY, + READ_WRITE_MANY, READ_WRITE_SINGLE. ACCESS_MODE must be one of: + + READ_ONLY_MANY + The AccessMode means the disk can be attached to multiple instances + in RW mode. + READ_WRITE_MANY + The AccessMode means the disk can be attached to multiple instances + in RO mode. + READ_WRITE_SINGLE + The default AccessMode, means the disk can be attached to single + instance in RW mode. + + --architecture=ARCHITECTURE + Specifies the architecture or processor type that this disk can + support. For available processor types on Compute Engine, see + https://cloud.google.com/compute/docs/cpu-platforms. ARCHITECTURE must + be one of: ARM64, X86_64. ARCHITECTURE must be one of: + + ARM64 + The disk can only be used with ARM64 machines. + X86_64 + The disk can only be used with x86_64 machines. + + --async + Return immediately, without waiting for the operation in progress to + complete. The default is True. Enabled by default, use --no-async to + disable. + + --clear-encryption-key + The restored disk reverts to GMEK (CMEK is disabled). + + --confidential-compute + Creates the disk with confidential compute mode enabled. Encryption + with a Cloud KMS key is required to enable this option. + + --description=DESCRIPTION + Specifies a textual description of the restored disk. + + --guest-os-features=[GUEST_OS_FEATURES,...] + Enables one or more features for VM instances that use the image for + their boot disks. See the descriptions of supported features at: + https://cloud.google.com/compute/docs/images/create-delete-deprecate-private-images#guest-os-features. + GUEST_OS_FEATURE must be one of: VIRTIO_SCSI_MULTIQUEUE, WINDOWS, + MULTI_IP_SUBNET, UEFI_COMPATIBLE, SEV_CAPABLE, SEV_LIVE_MIGRATABLE, + SEV_LIVE_MIGRATABLE_V2, SEV_SNP_CAPABLE, GVNIC, IDPF, TDX_CAPABLE, + SUSPEND_RESUME_COMPATIBLE. + + --kms-key=KMS_KEY + The Cloud KMS (Key Management Service) cryptokey that will be used to + protect the disk Provide the full resource name of the cryptokey in the + format: + projects//locations//keyRings//cryptoKeys/ + + --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. + + --licenses=LICENSE,[LICENSE,...] + A list of URIs to license resources. The provided licenses will be + added onto the created disks to indicate the licensing and billing + policies. + + --provisioned-iops=PROVISIONED_IOPS + Provisioned IOPS of disk to create. Only for use with disks of type + pd-extreme and hyperdisk-extreme. + + --provisioned-throughput=PROVISIONED_THROUGHPUT + Provisioned throughput of disk to create. The throughput unit is MB per + sec. Only for use with disks of type hyperdisk-throughput. + + --replica-zones=ZONE,ZONE + A comma-separated list of exactly 2 URLs of the zones where the disk + should be replicated to. Required when restoring to a regional disk. + The zones must be in the same region as specified in the + --target-region flag. See available zones with gcloud compute zones + list. + + --resource-policies=RESOURCE_POLICY,[...] + A list of resource policy names to be added to the disk. The policies + must exist in the same region as the disk. + + --size=SIZE + Size of the disk in GB. Disk size must be a multiple of 1 GB. If disk + size is not specified, the default size of 500GB for pd-standard disks, + 100GB for pd-balanced disks, 100GB for pd-ssd disks, and 1000GB for + pd-extreme disks will be used. For details about disk size limits, + refer to: https://cloud.google.com/compute/docs/disks + + --storage-pool=STORAGE_POOL + Specifies the URI of the storage pool in which the disk is created. + + --target-region=TARGET_REGION + Region where the target disk is restored. This flag is mutually + exclusive with --target-zone. + + --target-zone=TARGET_ZONE + Zone where the target disk is restored. This flag is mutually exclusive + with --target-region. + + --type=TYPE + URL of the disk type describing which disk type to use to restore the + disk. For example: projects/project/zones/zone/diskTypes/pd-ssd. To get + a list of available disk types, run gcloud compute disk-types list. The + default disk type is pd-standard. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +BRIEF + Restores the specified backup + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud backup-dr backups restore disk + + $ gcloud alpha backup-dr backups restore disk + diff --git a/gcloud/beta/backup-dr/backups/restore/help b/gcloud/beta/backup-dr/backups/restore/help new file mode 100644 index 000000000..f683785a3 --- /dev/null +++ b/gcloud/beta/backup-dr/backups/restore/help @@ -0,0 +1,32 @@ +NAME + gcloud beta backup-dr backups restore - manage restore operations for + resources + +SYNOPSIS + gcloud beta backup-dr backups restore COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Manage restore operations for resources. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + compute + (BETA) Restores a Compute Engine VM Backup. + + disk + (BETA) Restores a Compute Disk Backup. + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud backup-dr backups restore + + $ gcloud alpha backup-dr backups restore + diff --git a/gcloud/beta/backup-dr/backups/update b/gcloud/beta/backup-dr/backups/update new file mode 100644 index 000000000..37215cab8 --- /dev/null +++ b/gcloud/beta/backup-dr/backups/update @@ -0,0 +1,154 @@ +NAME + gcloud beta backup-dr backups update - update the specified Backup + +SYNOPSIS + gcloud beta backup-dr backups update + (BACKUP : --backup-vault=BACKUP_VAULT + --data-source=DATA_SOURCE --location=LOCATION) [--async] + [--clear-labels | --remove-labels=KEY,[KEY,...] + | --update-labels=[KEY=VALUE,...]] + [--enforced-retention-end-time=ENFORCED_RETENTION_END_TIME + --expire-time=EXPIRE_TIME] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Update the specified Backup. + +EXAMPLES + To update the enforced retention of a backup sample-backup in backup vault + sample-vault, data source sample-ds, project sample-project and location + us-central1, run: + + $ gcloud beta backup-dr backups update sample-backup \ + --backup-vault=sample-vault --data-source=sample-ds \ + --project=sample-project --location=us-central1 \ + --enforced-retention-end-time="2025-02-14T01:10:20Z" + + To update the labels on a backup named my-backup in the test-bv vault and + us-central1 location, run: + + $ gcloud beta backup-dr backups update my-backup \ + --backup-vault=test-bv --location=us-central1 \ + --update-labels=env=prod,team=storage + + To remove the env label from the same backup, run: + + $ gcloud beta backup-dr backups update my-backup \ + --backup-vault=test-bv --location=us-central1 \ + --remove-labels=env + + To clear all labels from the backup, run: + + $ gcloud beta backup-dr backups update my-backup \ + --backup-vault=test-bv --location=us-central1 --clear-labels + +POSITIONAL ARGUMENTS + Backup resource - Name of the backup 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 backup 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 + ID of the Backup or fully qualified identifier for the Backup. + + To set the name attribute: + ▸ provide the argument backup on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --backup-vault=BACKUP_VAULT + The ID of the Backup Vault. + + To set the backup-vault attribute: + ▸ provide the argument backup on the command line with a fully + specified name; + ▸ provide the argument --backup-vault on the command line. + + --data-source=DATA_SOURCE + The ID of the Data Source. + + To set the data-source attribute: + ▸ provide the argument backup on the command line with a fully + specified name; + ▸ provide the argument --data-source on the command line. + + --location=LOCATION + The location of the Backup. + + To set the location attribute: + ▸ provide the argument backup 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. The default is True. Enabled by default, use --no-async to + disable. + + At most one of these can be specified: + + --clear-labels + Remove all labels from the backup. + + If the backup has no labels, this operation is a no-op. + + --remove-labels=KEY,[KEY,...] + A list of label keys to remove from the backup. + + If a label does not exist, it is silently ignored. + + --update-labels=[KEY=VALUE,...] + A list of labels to apply to the backup. + + Keys must start with a lowercase letter and contain only lowercase + letters, numbers, and hyphens, and must be between 1 and 63 + characters long. Values must contain only lowercase letters, numbers, + and hyphens, and must be between 0 and 63 characters long. + + For example: --update-labels=env=prod,team=storage + + Update Backup Flags + + --enforced-retention-end-time=ENFORCED_RETENTION_END_TIME + Backups cannot be deleted until this time or later. This period can be + extended, but not shortened. It should be specified in the format of + "YYYY-MM-DD". + + ◆ For backup configured with a backup appliance, there are additional + restrictions: 1. Enforced retention cannot be extended past the + expiry time. 2. Enforced retention can only be updated for finalized + backups. + + --expire-time=EXPIRE_TIME + The date when this backup is automatically expired. This date can be + extended, but not shortened. It should be specified in the format of + "YYYY-MM-DD". + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +BRIEF + Updates a specific backup + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud backup-dr backups update + + $ gcloud alpha backup-dr backups update + diff --git a/gcloud/beta/backup-dr/data-source-references/describe b/gcloud/beta/backup-dr/data-source-references/describe new file mode 100644 index 000000000..5650ad4e6 --- /dev/null +++ b/gcloud/beta/backup-dr/data-source-references/describe @@ -0,0 +1,70 @@ +NAME + gcloud beta backup-dr data-source-references describe - show details of the + data source reference + +SYNOPSIS + gcloud beta backup-dr data-source-references describe + (DATA_SOURCE_REFERENCE : --location=LOCATION) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Show all configuration data source associated with the specified + data source reference. + +EXAMPLES + To view details for data source 'DATA_SOURCE_REFERENCE', run: + + $ gcloud beta backup-dr data-source-references describe \ + DATA_SOURCE_REFERENCE + +POSITIONAL ARGUMENTS + Data source reference resource - Name of the data source reference 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 data_source_reference 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_SOURCE_REFERENCE + ID of the data_source_reference or fully qualified identifier for the + data_source_reference. + + To set the data_source_reference attribute: + ▸ provide the argument data_source_reference on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + Location ID of the resource. + + To set the location attribute: + ▸ provide the argument data_source_reference 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 backupdr/v1beta API. The full documentation for this + API can be found at: https://cloud.google.com/backup-disaster-recovery + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud backup-dr data-source-references describe + + $ gcloud alpha backup-dr data-source-references describe + diff --git a/gcloud/beta/backup-dr/data-source-references/fetch-for-resource-type b/gcloud/beta/backup-dr/data-source-references/fetch-for-resource-type new file mode 100644 index 000000000..f865c0e23 --- /dev/null +++ b/gcloud/beta/backup-dr/data-source-references/fetch-for-resource-type @@ -0,0 +1,84 @@ +NAME + gcloud beta backup-dr data-source-references fetch-for-resource-type - + fetch Data Source References for a given resource type and location + +SYNOPSIS + gcloud beta backup-dr data-source-references fetch-for-resource-type + RESOURCE_TYPE --location=LOCATION [--filter=EXPRESSION] [--limit=LIMIT] + [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Fetch Data Source References for a given resource type and location. + Show all configuration data associated with the specified data source + reference. + +EXAMPLES + To list data source references for Cloud SQL with location us-central1 in + project test-project, run: + + $ gcloud beta backup-dr data-source-references \ + fetch-for-resource-type sqladmin.googleapis.com/Instance \ + --location="us-central1" --project="test-project" + +POSITIONAL ARGUMENTS + RESOURCE_TYPE + Resource type for which data source references should be fetched. + +REQUIRED FLAGS + --location=LOCATION + Location for which data source references should be fetched. + +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. + +BRIEF + List data source references in a specified location and resource type in a + project. + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud backup-dr data-source-references fetch-for-resource-type + + $ gcloud alpha backup-dr data-source-references \ + fetch-for-resource-type + diff --git a/gcloud/beta/backup-dr/data-source-references/help b/gcloud/beta/backup-dr/data-source-references/help new file mode 100644 index 000000000..6e16b0add --- /dev/null +++ b/gcloud/beta/backup-dr/data-source-references/help @@ -0,0 +1,36 @@ +NAME + gcloud beta backup-dr data-source-references - command group for Backup and + DR Data Source References + +SYNOPSIS + gcloud beta backup-dr data-source-references COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Command group for Backup and DR Data Source References. + +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) Show details of the data source reference. + + fetch-for-resource-type + (BETA) Fetch Data Source References for a given resource type and + location. + + list + (BETA) List Backup and DR data source references. + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud backup-dr data-source-references + + $ gcloud alpha backup-dr data-source-references + diff --git a/gcloud/beta/backup-dr/data-source-references/list b/gcloud/beta/backup-dr/data-source-references/list new file mode 100644 index 000000000..1307cea1c --- /dev/null +++ b/gcloud/beta/backup-dr/data-source-references/list @@ -0,0 +1,93 @@ +NAME + gcloud beta backup-dr data-source-references list - list Backup and DR data + source references + +SYNOPSIS + gcloud beta backup-dr data-source-references list [--location=LOCATION] + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) List Backup and DR data source references. + +EXAMPLES + To list data source references in all locations, run: + + $ gcloud beta backup-dr data-source-references list + + To list data source references in a location 'my-location', run: + + $ gcloud beta backup-dr data-source-references list \ + --location=my-location + +FLAGS + Location resource - Location for which data source references should be + listed. 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; + ◆ default is all locations 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; + ◆ default is all locations . + +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 backupdr/v1beta API. The full documentation for this + API can be found at: https://cloud.google.com/backup-disaster-recovery + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud backup-dr data-source-references list + + $ gcloud alpha backup-dr data-source-references list + diff --git a/gcloud/beta/backup-dr/data-sources/describe b/gcloud/beta/backup-dr/data-sources/describe new file mode 100644 index 000000000..772c6b670 --- /dev/null +++ b/gcloud/beta/backup-dr/data-sources/describe @@ -0,0 +1,78 @@ +NAME + gcloud beta backup-dr data-sources describe - show details of the data + source + +SYNOPSIS + gcloud beta backup-dr data-sources describe + (DATA_SOURCE : --backup-vault=BACKUP_VAULT --location=LOCATION) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Show all configuration data associated with the specified data + source. + +EXAMPLES + To view details for data source 'DATA_SOURCE', run: + + $ gcloud beta backup-dr data-sources describe DATA_SOURCE + +POSITIONAL ARGUMENTS + Data source resource - Name of the data source 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 data_source 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_SOURCE + ID of the data_source or fully qualified identifier for the + data_source. + + To set the data_source attribute: + ▸ provide the argument data_source on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --backup-vault=BACKUP_VAULT + The ID of the Backup Vault. + + To set the backup-vault attribute: + ▸ provide the argument data_source on the command line with a fully + specified name; + ▸ provide the argument --backup-vault on the command line. + + --location=LOCATION + Location ID of the resource. + + To set the location attribute: + ▸ provide the argument data_source 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 backupdr/v1beta API. The full documentation for this + API can be found at: https://cloud.google.com/backup-disaster-recovery + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud backup-dr data-sources describe + + $ gcloud alpha backup-dr data-sources describe + diff --git a/gcloud/beta/backup-dr/data-sources/help b/gcloud/beta/backup-dr/data-sources/help new file mode 100644 index 000000000..8c3043116 --- /dev/null +++ b/gcloud/beta/backup-dr/data-sources/help @@ -0,0 +1,31 @@ +NAME + gcloud beta backup-dr data-sources - view Backup and DR data sources + +SYNOPSIS + gcloud beta backup-dr data-sources COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) View Backup and DR data sources. + +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) Show details of the data source. + + list + (BETA) List Data Sources. + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud backup-dr data-sources + + $ gcloud alpha backup-dr data-sources + diff --git a/gcloud/beta/backup-dr/data-sources/list b/gcloud/beta/backup-dr/data-sources/list new file mode 100644 index 000000000..67b81de66 --- /dev/null +++ b/gcloud/beta/backup-dr/data-sources/list @@ -0,0 +1,106 @@ +NAME + gcloud beta backup-dr data-sources list - list Data Sources + +SYNOPSIS + gcloud beta backup-dr data-sources list + [--backup-vault=BACKUP_VAULT --location=LOCATION] [--filter=EXPRESSION] + [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Displays all data sources in a project. + +EXAMPLES + To list data sources for all backup vaults and locations, run: + + $ gcloud beta backup-dr data-sources list + + To list all data sources for a backup vault my-vault in a location + my-location, run: + + $ gcloud beta backup-dr data-sources list --backup-vault=my-vault \ + --location=my-location + +FLAGS + Backup vault resource - Backup vault to list data sources from. 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-vault on the command line with a fully + specified name; + ◆ default is all backup vaults with a fully specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + --backup-vault=BACKUP_VAULT + ID of the backup_vault or fully qualified identifier for the + backup_vault. + + To set the backup-vault attribute: + ◆ provide the argument --backup-vault on the command line; + ◆ default is all backup vaults . + + --location=LOCATION + Location ID of the resource. + + To set the location attribute: + ◆ provide the argument --backup-vault on the command line with a + fully specified name; + ◆ default is all backup vaults with a fully specified name; + ◆ provide the argument --location on the command line; + ◆ default is all locations . + +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 backupdr/v1beta API. The full documentation for this + API can be found at: https://cloud.google.com/backup-disaster-recovery + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud backup-dr data-sources list + + $ gcloud alpha backup-dr data-sources list + diff --git a/gcloud/beta/backup-dr/help b/gcloud/beta/backup-dr/help index 6ee9c223d..8a9638ade 100644 --- a/gcloud/beta/backup-dr/help +++ b/gcloud/beta/backup-dr/help @@ -15,6 +15,27 @@ GCLOUD WIDE FLAGS GROUPS GROUP is one of the following: + backup-plan-associations + (BETA) Manage Backup and DR backup plan associations. + + backup-plan-revisions + (BETA) View Backup and DR backup plan revisions. + + backup-plans + (BETA) Manage Backup and DR backup plans. + + backup-vaults + (BETA) Manage Backup and DR backup vaults. + + backups + (BETA) Manage Backup and DR backups. + + data-source-references + (BETA) Command group for Backup and DR Data Source References. + + data-sources + (BETA) View Backup and DR data sources. + locations (BETA) Manage Backup and DR locations. @@ -24,6 +45,13 @@ GROUPS operations (BETA) Manage Backup and DR operations. + resource-backup-config + (BETA) Show protection summary for resources in a particular location + and project. + + service-config + (BETA) Manage Backup and DR Service configuration. + NOTES This command is currently in beta and might change without notice. These variants are also available: diff --git a/gcloud/beta/backup-dr/locations/list b/gcloud/beta/backup-dr/locations/list index e0ee9c847..0bf1b81b1 100644 --- a/gcloud/beta/backup-dr/locations/list +++ b/gcloud/beta/backup-dr/locations/list @@ -56,8 +56,8 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. API REFERENCE - This command uses the backupdr/v1 API. The full documentation for this API - can be found at: https://cloud.google.com/backup-disaster-recovery + This command uses the backupdr/v1beta API. The full documentation for this + API can be found at: https://cloud.google.com/backup-disaster-recovery NOTES This command is currently in beta and might change without notice. These diff --git a/gcloud/beta/backup-dr/management-servers/describe b/gcloud/beta/backup-dr/management-servers/describe index a85a4fc42..58e39e994 100644 --- a/gcloud/beta/backup-dr/management-servers/describe +++ b/gcloud/beta/backup-dr/management-servers/describe @@ -56,8 +56,8 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. API REFERENCE - This command uses the backupdr/v1 API. The full documentation for this API - can be found at: https://cloud.google.com/backup-disaster-recovery + This command uses the backupdr/v1beta API. The full documentation for this + API can be found at: https://cloud.google.com/backup-disaster-recovery NOTES This command is currently in beta and might change without notice. These diff --git a/gcloud/beta/backup-dr/management-servers/list b/gcloud/beta/backup-dr/management-servers/list index b1e6ca522..5e354cba9 100644 --- a/gcloud/beta/backup-dr/management-servers/list +++ b/gcloud/beta/backup-dr/management-servers/list @@ -81,8 +81,8 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. API REFERENCE - This command uses the backupdr/v1 API. The full documentation for this API - can be found at: https://cloud.google.com/backup-disaster-recovery + This command uses the backupdr/v1beta API. The full documentation for this + API can be found at: https://cloud.google.com/backup-disaster-recovery NOTES This command is currently in beta and might change without notice. These diff --git a/gcloud/beta/backup-dr/operations/describe b/gcloud/beta/backup-dr/operations/describe index 9da54162a..9eca4d599 100644 --- a/gcloud/beta/backup-dr/operations/describe +++ b/gcloud/beta/backup-dr/operations/describe @@ -53,8 +53,8 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. API REFERENCE - This command uses the backupdr/v1 API. The full documentation for this API - can be found at: https://cloud.google.com/backup-disaster-recovery + This command uses the backupdr/v1beta API. The full documentation for this + API can be found at: https://cloud.google.com/backup-disaster-recovery NOTES This command is currently in beta and might change without notice. These diff --git a/gcloud/beta/backup-dr/operations/list b/gcloud/beta/backup-dr/operations/list index 7f10afb88..6e1886697 100644 --- a/gcloud/beta/backup-dr/operations/list +++ b/gcloud/beta/backup-dr/operations/list @@ -78,8 +78,8 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. API REFERENCE - This command uses the backupdr/v1 API. The full documentation for this API - can be found at: https://cloud.google.com/backup-disaster-recovery + This command uses the backupdr/v1beta API. The full documentation for this + API can be found at: https://cloud.google.com/backup-disaster-recovery NOTES This command is currently in beta and might change without notice. These diff --git a/gcloud/beta/backup-dr/resource-backup-config/help b/gcloud/beta/backup-dr/resource-backup-config/help new file mode 100644 index 000000000..6813ede4f --- /dev/null +++ b/gcloud/beta/backup-dr/resource-backup-config/help @@ -0,0 +1,31 @@ +NAME + gcloud beta backup-dr resource-backup-config - show protection summary for + resources in a particular location and project + +SYNOPSIS + gcloud beta backup-dr resource-backup-config COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Show protection summary for resources in a particular location and + 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 + (BETA) Show backup configuration metadata associated with specified + resources in a particular location for the project. + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud backup-dr resource-backup-config + + $ gcloud alpha backup-dr resource-backup-config + diff --git a/gcloud/beta/backup-dr/resource-backup-config/list b/gcloud/beta/backup-dr/resource-backup-config/list new file mode 100644 index 000000000..213622a1a --- /dev/null +++ b/gcloud/beta/backup-dr/resource-backup-config/list @@ -0,0 +1,144 @@ +NAME + gcloud beta backup-dr resource-backup-config list - show backup + configuration metadata associated with specified resources in a + particular location for the project + +SYNOPSIS + gcloud beta backup-dr resource-backup-config list --location=LOCATION + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Show backup configuration metadata associated with specified + resources in a particular location for the project. + +EXAMPLES + ▪ To list protection summary for a resource named resource-1: + + $ gcloud beta backup-dr resource-backup-config list \ + --project=sample-project --location=us-central1 \ + --filter="target_resource_display_name=resource-1" + + ▪ To list protection summary for a resource named resource-1 that has + backup configured: + + $ gcloud beta backup-dr resource-backup-config list \ + --project=sample-project --location=us-central1 \ + --filter="target_resource_display_name=resource-1 AND \ + backup_configured=true" + + You can sort the results using the --sort-by flag. The only supported field + for sorting is target_resource_display_name. + + Example of sorting: + + $ gcloud beta backup-dr resource-backup-config list \ + --project=sample-project --location=us-central1 \ + --sort-by="target_resource_display_name" + +REQUIRED FLAGS + Location resource - Location for which the resource backup config should + be listed. 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. + +BRIEF + list backup configurations for a specified project and location. + +FLAGS/ARGUMENTS + --project: Project for which backup configurations should be listed. + + --location: Location for which backup configurations should be listed. + + --filter: The filter expression to filter results. + + --sort-by: The field to sort results by. + +SUBARGUMENTS + target_resource_display_name: Name of the resource for which protection + summary is to be listed. + + target_resource_type: Type of resource for which protection summary is to + be displayed. + + Allowed values: + ▪ CLOUD_SQL_INSTANCE + ▪ COMPUTE_ENGINE_VM + + backup_configured: Displays if the specified resource has backups + configured. + + vaulted: Displays if configured backups are protected using a backup vault. + + backup_configs_details.backup_config_source_display_name: Name of the + backup schedule applied to the resource. + + backup_configs_details.type: Backup schedule type applied to the resource. + + Allowed values: + ▪ CLOUD_SQL_INSTANCE_BACKUP_CONFIG + ▪ COMPUTE_ENGINE_RESOURCE_POLICY + ▪ BACKUPDR_BACKUP_PLAN + ▪ BACKUPDR_TEMPLATE + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud backup-dr resource-backup-config list + + $ gcloud alpha backup-dr resource-backup-config list + diff --git a/gcloud/beta/backup-dr/service-config/help b/gcloud/beta/backup-dr/service-config/help new file mode 100644 index 000000000..02aef39bd --- /dev/null +++ b/gcloud/beta/backup-dr/service-config/help @@ -0,0 +1,29 @@ +NAME + gcloud beta backup-dr service-config - manage Backup and DR Service + configuration + +SYNOPSIS + gcloud beta backup-dr service-config COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Manage Backup and DR Service configuration. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + init + (BETA) Initialize a Backup and DR Service configuration. + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud backup-dr service-config + + $ gcloud alpha backup-dr service-config + diff --git a/gcloud/beta/backup-dr/service-config/init b/gcloud/beta/backup-dr/service-config/init new file mode 100644 index 000000000..b2bcb51d2 --- /dev/null +++ b/gcloud/beta/backup-dr/service-config/init @@ -0,0 +1,76 @@ +NAME + gcloud beta backup-dr service-config init - initialize a Backup and DR + Service configuration + +SYNOPSIS + gcloud beta backup-dr service-config init --location=LOCATION + --resource-type=RESOURCE_TYPE [--no-async] + [--cloudsql-edition=CLOUDSQL_EDITION] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Initialize a Backup and DR Service configuration. + +EXAMPLES + To initialize a new service configuration in location MY_LOCATION and + project MY_PROJECT for resource type MY_RESOURCE_TYPE, run: + + $ gcloud beta backup-dr service-config init --project=MY_PROJECT \ + --location=MY_LOCATION --resource-type=MY_RESOURCE_TYPE + +REQUIRED FLAGS + Location resource - The location for which the service configuration + should be created. 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. + + --resource-type=RESOURCE_TYPE + The resource type to which the default service configuration will be + applied. Examples include, "compute..com/Instance" + +OPTIONAL FLAGS + --no-async + Wait for the operation in progress to complete. + + --cloudsql-edition=CLOUDSQL_EDITION + Cloud SQL Edition: (Required only for Cloud SQL instances, ignored + otherwise). The edition of the Cloud SQL instance. Possible values: + "ENTERPRISE" - Enterprise edition. "ENTERPRISE_PLUS" - Enterprise Plus + edition. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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 backupdr/v1 API. The full documentation for this API + can be found at: https://cloud.google.com/backup-disaster-recovery + +BRIEF + Initializes a Backup and DR Service configuration. + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud backup-dr service-config init + + $ gcloud alpha backup-dr service-config init + diff --git a/gcloud/beta/beyondcorp/security-gateways/add-iam-policy-binding b/gcloud/beta/beyondcorp/security-gateways/add-iam-policy-binding new file mode 100644 index 000000000..dbe9673b6 --- /dev/null +++ b/gcloud/beta/beyondcorp/security-gateways/add-iam-policy-binding @@ -0,0 +1,96 @@ +NAME + gcloud beta beyondcorp security-gateways add-iam-policy-binding - add an + IAM policy binding to a security gateway + +SYNOPSIS + gcloud beta beyondcorp security-gateways add-iam-policy-binding + (SECURITY_GATEWAY : --location=LOCATION) --member=PRINCIPAL --role=ROLE + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Adds an IAM policy binding to the given security gateway. + +EXAMPLES + To add an IAM policy binding for the role of + 'roles/beyondcorp.serviceDiscoveryUser' for the user 'test-user@gmail.com' + on a security gateway with ID 'my-security-gateway': + + $ gcloud beta beyondcorp security-gateways add-iam-policy-binding \ + my-security-gateway --member='user:test-user@gmail.com' \ + --role='roles/beyondcorp.serviceDiscoveryUser' --location=global + + See https://cloud.google.com/iam/docs/managing-policies for details on + policy role and member types. + +POSITIONAL ARGUMENTS + SecurityGateway resource - The security gateway for which to add the IAM + policy 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 security_gateway 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. + + SECURITY_GATEWAY + ID of the securityGateway or fully qualified identifier for the + securityGateway. + + To set the security_gateway attribute: + ▸ provide the argument security_gateway 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 securityGateway resource. We support only + global location. + + To set the location attribute: + ▸ provide the argument security_gateway on the command line with a + fully specified name; + ▸ provide the argument --location on the command line. + +REQUIRED FLAGS + --member=PRINCIPAL + The principal to add the binding for. Should be of the form + user|group|serviceAccount:email or domain:domain. + + Examples: user:test-user@gmail.com, group:admins@example.com, + serviceAccount:test123@example.domain.com, or + domain:example.domain.com. + + Some resources also accept the following special values: + ◆ allUsers - Special identifier that represents anyone who is on the + internet, with or without a Google account. + ◆ allAuthenticatedUsers - Special identifier that represents anyone + who is authenticated with a Google account or a service account. + + --role=ROLE + Role name to assign to the principal. The role name is the complete + path of a predefined role, such as roles/logging.viewer, or the role ID + for a custom role, such as + organizations/{ORGANIZATION_ID}/roles/logging.viewer. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the beyondcorp/v1 API. The full documentation for this + API can be found at: https://cloud.google.com/ + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud beyondcorp security-gateways add-iam-policy-binding + diff --git a/gcloud/beta/beyondcorp/security-gateways/applications/add-iam-policy-binding b/gcloud/beta/beyondcorp/security-gateways/applications/add-iam-policy-binding new file mode 100644 index 000000000..f1d4b4b11 --- /dev/null +++ b/gcloud/beta/beyondcorp/security-gateways/applications/add-iam-policy-binding @@ -0,0 +1,109 @@ +NAME + gcloud beta beyondcorp security-gateways applications + add-iam-policy-binding - add an IAM policy binding to a security + gateway application + +SYNOPSIS + gcloud beta beyondcorp security-gateways applications + add-iam-policy-binding + (APPLICATION : --location=LOCATION --security-gateway=SECURITY_GATEWAY) + --member=PRINCIPAL --role=ROLE [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Adds an IAM policy binding to the given security gateway + application. + +EXAMPLES + To add an IAM policy binding for the role of + 'roles/beyondcorp.sgApplicationUser' for the user 'test-user@gmail.com' on + a security gateway application with ID 'my-application': + + $ gcloud beta beyondcorp security-gateways applications \ + add-iam-policy-binding my-application \ + --member='user:test-user@gmail.com' \ + --role='roles/beyondcorp.sgApplicationUser' --location=global + + See https://cloud.google.com/iam/docs/managing-policies for details on + policy role and member types. + +POSITIONAL ARGUMENTS + Application resource - The security gateway application for which to add + the IAM policy 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 application 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. + + APPLICATION + ID of the application or fully qualified identifier for the + application. + + To set the application attribute: + ▸ provide the argument application 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 application resource. We support only global + location. + + To set the location attribute: + ▸ provide the argument application on the command line with a fully + specified name; + ▸ provide the argument --location on the command line. + + --security-gateway=SECURITY_GATEWAY + The securityGateway id of the application resource. + + To set the security-gateway attribute: + ▸ provide the argument application on the command line with a fully + specified name; + ▸ provide the argument --security-gateway on the command line. + +REQUIRED FLAGS + --member=PRINCIPAL + The principal to add the binding for. Should be of the form + user|group|serviceAccount:email or domain:domain. + + Examples: user:test-user@gmail.com, group:admins@example.com, + serviceAccount:test123@example.domain.com, or + domain:example.domain.com. + + Some resources also accept the following special values: + ◆ allUsers - Special identifier that represents anyone who is on the + internet, with or without a Google account. + ◆ allAuthenticatedUsers - Special identifier that represents anyone + who is authenticated with a Google account or a service account. + + --role=ROLE + Role name to assign to the principal. The role name is the complete + path of a predefined role, such as roles/logging.viewer, or the role ID + for a custom role, such as + organizations/{ORGANIZATION_ID}/roles/logging.viewer. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the beyondcorp/v1 API. The full documentation for this + API can be found at: https://cloud.google.com/ + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud beyondcorp security-gateways applications \ + add-iam-policy-binding + diff --git a/gcloud/beta/beyondcorp/security-gateways/applications/help b/gcloud/beta/beyondcorp/security-gateways/applications/help index 1a3efb90b..ea7cb511a 100644 --- a/gcloud/beta/beyondcorp/security-gateways/applications/help +++ b/gcloud/beta/beyondcorp/security-gateways/applications/help @@ -17,6 +17,9 @@ GCLOUD WIDE FLAGS COMMANDS COMMAND is one of the following: + add-iam-policy-binding + (BETA) Add an IAM policy binding to a security gateway application. + create (BETA) Create applications. @@ -32,6 +35,10 @@ COMMANDS list (BETA) List applications. + remove-iam-policy-binding + (BETA) Remove an IAM policy binding from a security gateway + application. + set-iam-policy (BETA) Set the IAM policy for a security gateway application. diff --git a/gcloud/beta/beyondcorp/security-gateways/applications/remove-iam-policy-binding b/gcloud/beta/beyondcorp/security-gateways/applications/remove-iam-policy-binding new file mode 100644 index 000000000..a9f03364f --- /dev/null +++ b/gcloud/beta/beyondcorp/security-gateways/applications/remove-iam-policy-binding @@ -0,0 +1,110 @@ +NAME + gcloud beta beyondcorp security-gateways applications + remove-iam-policy-binding - remove an IAM policy binding from a + security gateway application + +SYNOPSIS + gcloud beta beyondcorp security-gateways applications + remove-iam-policy-binding + (APPLICATION : --location=LOCATION --security-gateway=SECURITY_GATEWAY) + --member=PRINCIPAL --role=ROLE [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Removes an IAM policy binding from the given security gateway + application. + +EXAMPLES + To remove an IAM policy binding for the role of + 'roles/beyondcorp.sgApplicationUser' for the user 'test-user@gmail.com' on + a security gateway application with ID 'my-application': + + $ gcloud beta beyondcorp security-gateways applications \ + remove-iam-policy-binding my-application \ + --member='user:test-user@gmail.com' \ + --role='roles/beyondcorp.sgApplicationUser' --location=global + + See https://cloud.google.com/iam/docs/managing-policies for details on + policy role and member types. + +POSITIONAL ARGUMENTS + Application resource - The security gateway application for which to + remove the IAM policy 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 application 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. + + APPLICATION + ID of the application or fully qualified identifier for the + application. + + To set the application attribute: + ▸ provide the argument application 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 application resource. We support only global + location. + + To set the location attribute: + ▸ provide the argument application on the command line with a fully + specified name; + ▸ provide the argument --location on the command line. + + --security-gateway=SECURITY_GATEWAY + The securityGateway id of the application resource. + + To set the security-gateway attribute: + ▸ provide the argument application on the command line with a fully + specified name; + ▸ provide the argument --security-gateway on the command line. + +REQUIRED FLAGS + --member=PRINCIPAL + The principal to remove the binding for. Should be of the form + user|group|serviceAccount:email or domain:domain. + + Examples: user:test-user@gmail.com, group:admins@example.com, + serviceAccount:test123@example.domain.com, or + domain:example.domain.com. + + Deleted principals have an additional deleted: prefix and a ?uid=UID + suffix, where UID is a unique identifier for the principal. Example: + deleted:user:test-user@gmail.com?uid=123456789012345678901. + + Some resources also accept the following special values: + ◆ allUsers - Special identifier that represents anyone who is on the + internet, with or without a Google account. + ◆ allAuthenticatedUsers - Special identifier that represents anyone + who is authenticated with a Google account or a service account. + + --role=ROLE + The role to remove the principal from. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the beyondcorp/v1 API. The full documentation for this + API can be found at: https://cloud.google.com/ + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud beyondcorp security-gateways applications \ + remove-iam-policy-binding + diff --git a/gcloud/beta/beyondcorp/security-gateways/create b/gcloud/beta/beyondcorp/security-gateways/create index 24a0a989c..d95332991 100644 --- a/gcloud/beta/beyondcorp/security-gateways/create +++ b/gcloud/beta/beyondcorp/security-gateways/create @@ -5,7 +5,7 @@ SYNOPSIS gcloud beta beyondcorp security-gateways create (SECURITY_GATEWAY : --location=LOCATION) [--async] [--display-name=DISPLAY_NAME] [--hubs=[HUBS,...]] - [--logging=[LOGGING,...]] [--request-id=REQUEST_ID] + [--request-id=REQUEST_ID] [--proxy-protocol-config-allowed-client-headers=[PROXY_PROTOCOL_CONFIG_ALLOWED_CLIENT_HEADERS, ...] --proxy-protocol-config-client-ip --proxy-protocol-config-gateway-identity=PROXY_PROTOCOL_CONFIG_GATEWAY_IDENTITY --proxy-protocol-config-metadata-headers=[PROXY_PROTOCOL_CONFIG_METADATA_HEADERS, @@ -88,21 +88,6 @@ FLAGS --hubs=path_to_file.(yaml|json) - --logging=[LOGGING,...] - Configuration for Cloud Logging. - - Shorthand Example: - - --logging= - - JSON Example: - - --logging={} - - File Example: - - --logging=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 diff --git a/gcloud/beta/beyondcorp/security-gateways/help b/gcloud/beta/beyondcorp/security-gateways/help index 738ef5c9e..eea5974d4 100644 --- a/gcloud/beta/beyondcorp/security-gateways/help +++ b/gcloud/beta/beyondcorp/security-gateways/help @@ -23,6 +23,9 @@ GROUPS COMMANDS COMMAND is one of the following: + add-iam-policy-binding + (BETA) Add an IAM policy binding to a security gateway. + create (BETA) Create securityGateways. @@ -38,6 +41,9 @@ COMMANDS list (BETA) List securityGateways. + remove-iam-policy-binding + (BETA) Remove an IAM policy binding from a security gateway. + set-iam-policy (BETA) Set the IAM policy for a security gateway. diff --git a/gcloud/beta/beyondcorp/security-gateways/remove-iam-policy-binding b/gcloud/beta/beyondcorp/security-gateways/remove-iam-policy-binding new file mode 100644 index 000000000..cc3cdd3a1 --- /dev/null +++ b/gcloud/beta/beyondcorp/security-gateways/remove-iam-policy-binding @@ -0,0 +1,98 @@ +NAME + gcloud beta beyondcorp security-gateways remove-iam-policy-binding - remove + an IAM policy binding from a security gateway + +SYNOPSIS + gcloud beta beyondcorp security-gateways remove-iam-policy-binding + (SECURITY_GATEWAY : --location=LOCATION) --member=PRINCIPAL --role=ROLE + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Removes an IAM policy binding from the given security gateway. + +EXAMPLES + To remove an IAM policy binding for the role of + 'roles/beyondcorp.serviceDiscoveryUser' for the user 'test-user@gmail.com' + on a security gateway with ID 'my-security-gateway': + + $ gcloud beta beyondcorp security-gateways \ + remove-iam-policy-binding my-security-gateway \ + --member='user:test-user@gmail.com' \ + --role='roles/beyondcorp.serviceDiscoveryUser' --location=global + + See https://cloud.google.com/iam/docs/managing-policies for details on + policy role and member types. + +POSITIONAL ARGUMENTS + SecurityGateway resource - The security gateway for which to remove the + IAM policy 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 security_gateway 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. + + SECURITY_GATEWAY + ID of the securityGateway or fully qualified identifier for the + securityGateway. + + To set the security_gateway attribute: + ▸ provide the argument security_gateway 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 securityGateway resource. We support only + global location. + + To set the location attribute: + ▸ provide the argument security_gateway on the command line with a + fully specified name; + ▸ provide the argument --location on the command line. + +REQUIRED FLAGS + --member=PRINCIPAL + The principal to remove the binding for. Should be of the form + user|group|serviceAccount:email or domain:domain. + + Examples: user:test-user@gmail.com, group:admins@example.com, + serviceAccount:test123@example.domain.com, or + domain:example.domain.com. + + Deleted principals have an additional deleted: prefix and a ?uid=UID + suffix, where UID is a unique identifier for the principal. Example: + deleted:user:test-user@gmail.com?uid=123456789012345678901. + + Some resources also accept the following special values: + ◆ allUsers - Special identifier that represents anyone who is on the + internet, with or without a Google account. + ◆ allAuthenticatedUsers - Special identifier that represents anyone + who is authenticated with a Google account or a service account. + + --role=ROLE + The role to remove the principal from. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the beyondcorp/v1 API. The full documentation for this + API can be found at: https://cloud.google.com/ + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud beyondcorp security-gateways remove-iam-policy-binding + diff --git a/gcloud/beta/beyondcorp/security-gateways/update b/gcloud/beta/beyondcorp/security-gateways/update index da2249670..b02237aa4 100644 --- a/gcloud/beta/beyondcorp/security-gateways/update +++ b/gcloud/beta/beyondcorp/security-gateways/update @@ -5,7 +5,6 @@ SYNOPSIS gcloud beta beyondcorp security-gateways update (SECURITY_GATEWAY : --location=LOCATION) [--async] [--display-name=DISPLAY_NAME] [--request-id=REQUEST_ID] - [--clear-logging | --logging=[LOGGING,...]] [--clear-proxy-protocol-config --[no-]proxy-protocol-config-client-ip --proxy-protocol-config-gateway-identity=PROXY_PROTOCOL_CONFIG_GATEWAY_IDENTITY --contextual-headers-output-type=CONTEXTUAL_HEADERS_OUTPUT_TYPE --device-info-output-type=DEVICE_INFO_OUTPUT_TYPE --group-info-output-type=GROUP_INFO_OUTPUT_TYPE --user-info-output-type=USER_INFO_OUTPUT_TYPE --proxy-protocol-config-allowed-client-headers=[PROXY_PROTOCOL_CONFIG_ALLOWED_CLIENT_HEADERS, ...] @@ -90,33 +89,6 @@ FLAGS The request ID must be a valid UUID with the exception that zero UUID is not supported (00000000-0000-0000-0000-000000000000). - Set the value of - googleCloudBeyondcorpSecuritygatewaysV1SecurityGateway.logging by using - flag [logging] or flags []. - - At most one of these can be specified: - - Configuration for Cloud Logging. - - --clear-logging - Set googleCloudBeyondcorpSecuritygatewaysV1SecurityGateway.logging - back to default value. - - --logging=[LOGGING,...] - Configuration for Cloud Logging. - - Shorthand Example: - - --logging= - - JSON Example: - - --logging={} - - File Example: - - --logging=path_to_file.(yaml|json) - The configuration for the proxy. --clear-proxy-protocol-config diff --git a/gcloud/beta/biglake/iceberg/catalogs/create b/gcloud/beta/biglake/iceberg/catalogs/create index 7f1ee0ad1..1aea300e8 100644 --- a/gcloud/beta/biglake/iceberg/catalogs/create +++ b/gcloud/beta/biglake/iceberg/catalogs/create @@ -61,7 +61,7 @@ OPTIONAL FLAGS Use vended credentials to access the catalog. --description=DESCRIPTION - Description of the resource being created. + Description of the resource. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/beta/biglake/iceberg/catalogs/update b/gcloud/beta/biglake/iceberg/catalogs/update index 807db08e5..5df76356a 100644 --- a/gcloud/beta/biglake/iceberg/catalogs/update +++ b/gcloud/beta/biglake/iceberg/catalogs/update @@ -10,6 +10,12 @@ SYNOPSIS DESCRIPTION (BETA) Update a BigLake Iceberg REST catalog. +EXAMPLES + To update the description of a catalog my-catalog, run: + + $ gcloud beta biglake iceberg catalogs update my-catalog \ + --description="updated description" + POSITIONAL ARGUMENTS Catalog resource - The Iceberg Catalog to update. This represents a Cloud resource. (NOTE) Some attributes are not given arguments in this group but @@ -40,7 +46,7 @@ FLAGS Use vended credentials to access the catalog. --description=DESCRIPTION - Description of the resource being created. + Description of the resource. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/beta/biglake/iceberg/tables/create b/gcloud/beta/biglake/iceberg/tables/create index 14bb661d1..97097c6c0 100644 --- a/gcloud/beta/biglake/iceberg/tables/create +++ b/gcloud/beta/biglake/iceberg/tables/create @@ -120,8 +120,10 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud biglake iceberg tables create $ gcloud alpha biglake iceberg tables create diff --git a/gcloud/beta/biglake/iceberg/tables/delete b/gcloud/beta/biglake/iceberg/tables/delete index 9bc4ce4c8..54006dc71 100644 --- a/gcloud/beta/biglake/iceberg/tables/delete +++ b/gcloud/beta/biglake/iceberg/tables/delete @@ -64,8 +64,10 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud biglake iceberg tables delete $ gcloud alpha biglake iceberg tables delete diff --git a/gcloud/beta/biglake/iceberg/tables/describe b/gcloud/beta/biglake/iceberg/tables/describe index b98097646..a830e7c78 100644 --- a/gcloud/beta/biglake/iceberg/tables/describe +++ b/gcloud/beta/biglake/iceberg/tables/describe @@ -69,8 +69,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 biglake iceberg tables describe $ gcloud alpha biglake iceberg tables describe diff --git a/gcloud/beta/biglake/iceberg/tables/get-iam-policy b/gcloud/beta/biglake/iceberg/tables/get-iam-policy index f0334665a..b9b4a904a 100644 --- a/gcloud/beta/biglake/iceberg/tables/get-iam-policy +++ b/gcloud/beta/biglake/iceberg/tables/get-iam-policy @@ -92,8 +92,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 biglake iceberg tables get-iam-policy $ gcloud alpha biglake iceberg tables get-iam-policy diff --git a/gcloud/beta/biglake/iceberg/tables/help b/gcloud/beta/biglake/iceberg/tables/help index aaca9d1f6..f74393889 100644 --- a/gcloud/beta/biglake/iceberg/tables/help +++ b/gcloud/beta/biglake/iceberg/tables/help @@ -41,8 +41,10 @@ COMMANDS (BETA) Update a BigLake Iceberg table. 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 biglake iceberg tables $ gcloud alpha biglake iceberg tables diff --git a/gcloud/beta/biglake/iceberg/tables/list b/gcloud/beta/biglake/iceberg/tables/list index 032c610d8..ace17393c 100644 --- a/gcloud/beta/biglake/iceberg/tables/list +++ b/gcloud/beta/biglake/iceberg/tables/list @@ -89,8 +89,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 biglake iceberg tables list $ gcloud alpha biglake iceberg tables list diff --git a/gcloud/beta/biglake/iceberg/tables/register b/gcloud/beta/biglake/iceberg/tables/register index f20f1feb0..dff4f66c8 100644 --- a/gcloud/beta/biglake/iceberg/tables/register +++ b/gcloud/beta/biglake/iceberg/tables/register @@ -82,8 +82,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 biglake iceberg tables register $ gcloud alpha biglake iceberg tables register diff --git a/gcloud/beta/biglake/iceberg/tables/set-iam-policy b/gcloud/beta/biglake/iceberg/tables/set-iam-policy index e580ada39..62e8efbbe 100644 --- a/gcloud/beta/biglake/iceberg/tables/set-iam-policy +++ b/gcloud/beta/biglake/iceberg/tables/set-iam-policy @@ -72,8 +72,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 biglake iceberg tables set-iam-policy $ gcloud alpha biglake iceberg tables set-iam-policy diff --git a/gcloud/beta/biglake/iceberg/tables/update b/gcloud/beta/biglake/iceberg/tables/update index a231799f8..3cf44a823 100644 --- a/gcloud/beta/biglake/iceberg/tables/update +++ b/gcloud/beta/biglake/iceberg/tables/update @@ -88,8 +88,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 biglake iceberg tables update $ gcloud alpha biglake iceberg tables update diff --git a/gcloud/beta/bigtable/app-profiles/create b/gcloud/beta/bigtable/app-profiles/create index 5f04bc798..bb99c8931 100644 --- a/gcloud/beta/bigtable/app-profiles/create +++ b/gcloud/beta/bigtable/app-profiles/create @@ -10,7 +10,8 @@ SYNOPSIS [--description=DESCRIPTION] [--force] [--data-boost --data-boost-compute-billing-owner=DATA_BOOST_COMPUTE_BILLING_OWNER - | --priority=PRIORITY --standard] [GCLOUD_WIDE_FLAG ...] + | --priority=PRIORITY --standard --use-memory-layer] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) Create a new Bigtable app profile. @@ -51,6 +52,12 @@ EXAMPLES $ gcloud beta bigtable app-profiles create my-app-profile-id \ --instance=my-instance-id --route-any --row-affinity + To create an app profile with the memory layer enabled, run: + + $ gcloud beta bigtable app-profiles create my-app-profile-id \ + --instance=my-instance-id --route-to=my-cluster-id \ + --use-memory-layer + POSITIONAL ARGUMENTS App profile resource - The app profile to create. The arguments in this group can be used to specify the attributes of this resource. (NOTE) Some @@ -170,6 +177,12 @@ OPTIONAL FLAGS compute option. If specified, --priority or --use-memory-layer is required. + --use-memory-layer + Enables the in-memory layer for standard provisioned node compute. + This option sets the compute option to --standard with the in-memory + layer enabled. Use --no-use-memory-layer to disable the in-memory + layer. + 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/app-profiles/update b/gcloud/beta/bigtable/app-profiles/update index 90c7b3c12..c5f8c3702 100644 --- a/gcloud/beta/bigtable/app-profiles/update +++ b/gcloud/beta/bigtable/app-profiles/update @@ -7,7 +7,7 @@ SYNOPSIS [--description=DESCRIPTION] [--force] [--data-boost --data-boost-compute-billing-owner=DATA_BOOST_COMPUTE_BILLING_OWNER - | --priority=PRIORITY --standard] + | --priority=PRIORITY --standard --use-memory-layer] [[--route-any : --restrict-to=[RESTRICT_TO,...] --row-affinity] | [--route-to=ROUTE_TO : --transactional-writes]] [GCLOUD_WIDE_FLAG ...] @@ -50,6 +50,11 @@ EXAMPLES $ gcloud beta bigtable app-profiles update my-app-profile-id \ --instance=my-instance-id --route-any --row-affinity + To update an app profile to use the memory layer, run: + + $ gcloud beta bigtable app-profiles update my-app-profile-id \ + --instance=my-instance-id --use-memory-layer + POSITIONAL ARGUMENTS App profile resource - The app profile to update. The arguments in this group can be used to specify the attributes of this resource. (NOTE) Some @@ -144,6 +149,12 @@ FLAGS compute option. If specified, --priority or --use-memory-layer is required. + --use-memory-layer + Enables the in-memory layer for standard provisioned node compute. + This option sets the compute option to --standard with the in-memory + layer enabled. Use --no-use-memory-layer to disable the in-memory + layer. + At most one of these can be specified: Multi Cluster Routing Policy diff --git a/gcloud/beta/bigtable/help b/gcloud/beta/bigtable/help index f3195fb37..adc3c19a3 100644 --- a/gcloud/beta/bigtable/help +++ b/gcloud/beta/bigtable/help @@ -39,6 +39,9 @@ GROUPS materialized-views (BETA) Manage Bigtable materialized views. + memory-layers + (BETA) Manage Cloud Bigtable memory layers. + operations (BETA) Manage Cloud Bigtable operations. diff --git a/gcloud/beta/bigtable/instances/create b/gcloud/beta/bigtable/instances/create index 927e98fc8..92226c434 100644 --- a/gcloud/beta/bigtable/instances/create +++ b/gcloud/beta/bigtable/instances/create @@ -12,7 +12,7 @@ SYNOPSIS autoscaling-storage-target=AUTOSCALING_STORAGE_TARGET],...]] [--cluster-num-nodes=CLUSTER_NUM_NODES] [--cluster-storage-type=CLUSTER_STORAGE_TYPE; default="ssd"] - [--cluster-zone=CLUSTER_ZONE] + [--cluster-zone=CLUSTER_ZONE] [--edition=EDITION] [--instance-type=INSTANCE_TYPE; default="PRODUCTION"] [GCLOUD_WIDE_FLAG ...] @@ -40,6 +40,14 @@ EXAMPLES --display-name="HDD Instance" --cluster-storage-type=HDD \ --cluster-config=id=my-cluster-id,zone=us-east1-c,nodes=10 + To create an instance with edition ENTERPRISE_PLUS, run: + + $ gcloud beta bigtable instances create \ + my-enterprise-plus-instance \ + --display-name="Enterprise Plus Instance" \ + --edition=ENTERPRISE_PLUS \ + --cluster-config=id=my-cluster-id,zone=us-east1-c,nodes=1 + POSITIONAL ARGUMENTS Instance resource - The instance to create. This represents a Cloud resource. (NOTE) Some attributes are not given arguments in this group but @@ -121,6 +129,10 @@ OPTIONAL FLAGS The --cluster-zone argument is deprecated; use --cluster-config instead. + --edition=EDITION + The edition of the instance. EDITION must be one of: ENTERPRISE, + ENTERPRISE_PLUS. + --instance-type=INSTANCE_TYPE; default="PRODUCTION" (DEPRECATED) The type of instance to create. diff --git a/gcloud/beta/bigtable/instances/tables/create b/gcloud/beta/bigtable/instances/tables/create index 3055d2c95..57252e123 100644 --- a/gcloud/beta/bigtable/instances/tables/create +++ b/gcloud/beta/bigtable/instances/tables/create @@ -10,8 +10,10 @@ SYNOPSIS [--row-key-schema-definition-file=ROW_KEY_SCHEMA_DEFINITION_FILE] [--row-key-schema-pre-encoded-bytes] [--splits=[SPLITS,...]] [--tiered-storage-infrequent-access-older-than=TIERED_STORAGE_INFREQUENT_ACCESS_OLDER_THAN] - [--automated-backup-retention-period=AUTOMATED_BACKUP_RETENTION_PERIOD - | --enable-automated-backup] [GCLOUD_WIDE_FLAG ...] + [--enable-automated-backup + | --automated-backup-locations=[LOCATION,...] + --automated-backup-retention-period=AUTOMATED_BACKUP_RETENTION_PERIOD] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) Create a new Cloud Bigtable table. @@ -80,6 +82,13 @@ EXAMPLES --instance=my-instance --column-families="my-family" \ --automated-backup-retention_period=30d + To create a table my-table with a custom automated backup policy configured + to take backups in only us-central1-b and us-east1-c, run: + + $ gcloud beta bigtable instances tables create my-table \ + --instance=my-instance \ + --automated-backup-locations=us-central1-b,us-east1-c + POSITIONAL ARGUMENTS Table resource - Cloud Bigtable table to create. The arguments in this group can be used to specify the attributes of this resource. (NOTE) Some @@ -168,15 +177,28 @@ OPTIONAL FLAGS At most one of these can be specified: - --automated-backup-retention-period=AUTOMATED_BACKUP_RETENTION_PERIOD - The retention period of automated backup in the format of 30d for 30 - days. Min retention period is 3d and max is 90d. Setting this flag - will enable automated backup for the table. - --enable-automated-backup Once set, enables the default automated backup policy (retention_period=7d, frequency=1d) for the table. + Or at least one of these can be specified: + + Group for automated backup policy parameters. + + --automated-backup-locations=[LOCATION,...] + List of Cloud Bigtable zones where automated backups are allowed to + be created. If empty, automated backups will be created in all + zones of the instance. Locations are in the format + projects/{project}/locations/{zone}. Setting this flag will enable + automated backup for the table. If automated backup retention + period is not specified, it defaults to 7 days. + + --automated-backup-retention-period=AUTOMATED_BACKUP_RETENTION_PERIOD + The retention period of automated backup in the format of 30d for + 30 days. Min retention period is 3d and max is 90d. Setting this + flag will enable automated backup for the table. If automated + backup retention period is not specified, it defaults to 7 days. + 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/instances/tables/update b/gcloud/beta/bigtable/instances/tables/update index db0ee6c33..af54515a9 100644 --- a/gcloud/beta/bigtable/instances/tables/update +++ b/gcloud/beta/bigtable/instances/tables/update @@ -6,7 +6,9 @@ SYNOPSIS gcloud beta bigtable instances tables update (TABLE : --instance=INSTANCE) [--async] [--deletion-protection] [--row-key-schema-pre-encoded-bytes] [--automated-backup-retention-period=AUTOMATED_BACKUP_RETENTION_PERIOD - | --disable-automated-backup | --enable-automated-backup] + --automated-backup-locations=[LOCATION,...] + | --clear-automated-backup-locations | --disable-automated-backup + | --enable-automated-backup] [--change-stream-retention-period=CHANGE_STREAM_RETENTION_PERIOD | --clear-change-stream-retention-period] [--clear-row-key-schema @@ -56,7 +58,19 @@ EXAMPLES retain backups for 30 days, run: $ gcloud beta bigtable instances tables update my-table \ - --instance=my-instance --automated-backup-retention_period=30d + --instance=my-instance --automated-backup-retention-period=30d + + To enable or update a custom automated backup policy and configure it to + take backups in only us-central1-b and us-east1-c, run: + + $ gcloud beta bigtable instances tables update my-table \ + --instance=my-instance \ + --automated-backup-locations=us-central1-b,us-east1-c + + To empty the automated backup locations list, run: + + $ gcloud beta bigtable instances tables update my-table \ + --instance=my-instance --clear-automated-backup-locations POSITIONAL ARGUMENTS Table resource - Cloud Bigtable table to update. The arguments in this @@ -109,19 +123,35 @@ FLAGS At most one of these can be specified: + Group for automated backup policy parameters. + --automated-backup-retention-period=AUTOMATED_BACKUP_RETENTION_PERIOD The retention period of automated backup in the format of 30d for 30 days. Min retention period is 3d and max is 90d. Setting this flag will enable automated backup for the table. - --disable-automated-backup - Once set, disables automated backup policy for the table. + At most one of these can be specified: - --enable-automated-backup - Once set, enables the default automated backup policy - (retention_period=7d, frequency=1d) for the table. Note: If a table - has automated backup enabled, this flag resets it to the default - policy. + --automated-backup-locations=[LOCATION,...] + List of Cloud Bigtable zones where automated backups are allowed to + be created. If empty, automated backups will be created in all + zones of the instance. Locations are in the format + projects/{project}/locations/{zone}. Setting this flag will enable + automated backup for the table. + + --clear-automated-backup-locations + Empty the automated backup locations list if populated. + + At most one of these can be specified: + + --disable-automated-backup + Once set, disables automated backup policy for the table. + + --enable-automated-backup + Once set, enables the default automated backup policy + (retention_period=7d, frequency=1d) for the table. Note: If a table + has automated backup enabled, this flag resets it to the default + policy. At most one of these can be specified: diff --git a/gcloud/beta/bigtable/instances/update b/gcloud/beta/bigtable/instances/update index 27d72cff4..5cbf95ba2 100644 --- a/gcloud/beta/bigtable/instances/update +++ b/gcloud/beta/bigtable/instances/update @@ -4,7 +4,8 @@ NAME SYNOPSIS gcloud beta bigtable instances update INSTANCE - [--display-name=DISPLAY_NAME] [GCLOUD_WIDE_FLAG ...] + [--display-name=DISPLAY_NAME] [--edition=EDITION] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) Modify an existing Bigtable instance. @@ -15,6 +16,11 @@ EXAMPLES $ gcloud beta bigtable instances update my-instance-id \ --display-name="Updated Instance Name" + To update the edition for an instance to ENTERPRISE_PLUS, run: + + $ gcloud beta bigtable instances update my-instance-id \ + --edition=ENTERPRISE_PLUS + POSITIONAL ARGUMENTS Instance resource - The instance to update. This represents a Cloud resource. (NOTE) Some attributes are not given arguments in this group but @@ -38,6 +44,10 @@ FLAGS --display-name=DISPLAY_NAME Friendly name of the instance. + --edition=EDITION + The edition of the instance. EDITION must be one of: ENTERPRISE, + ENTERPRISE_PLUS. + 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/memory-layers/describe b/gcloud/beta/bigtable/memory-layers/describe new file mode 100644 index 000000000..0dcaf0319 --- /dev/null +++ b/gcloud/beta/bigtable/memory-layers/describe @@ -0,0 +1,62 @@ +NAME + gcloud beta bigtable memory-layers describe - describe a Bigtable memory + layer + +SYNOPSIS + gcloud beta bigtable memory-layers describe (CLUSTER : --instance=INSTANCE) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Describe a Bigtable memory layer. + +EXAMPLES + To view a memory layer's description, run: + + $ gcloud beta bigtable memory-layers describe my-cluster-id \ + --instance=my-instance-id + +POSITIONAL ARGUMENTS + Cluster resource - The cluster of the memory layer 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 cluster on the command line with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + CLUSTER + ID of the cluster or fully qualified identifier for the cluster. + + To set the cluster attribute: + ▸ provide the argument cluster on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --instance=INSTANCE + Bigtable instance for the cluster. + + To set the instance attribute: + ▸ provide the argument cluster 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. This + variant is also available: + + $ gcloud alpha bigtable memory-layers describe + diff --git a/gcloud/beta/bigtable/memory-layers/help b/gcloud/beta/bigtable/memory-layers/help new file mode 100644 index 000000000..a708495e8 --- /dev/null +++ b/gcloud/beta/bigtable/memory-layers/help @@ -0,0 +1,29 @@ +NAME + gcloud beta bigtable memory-layers - manage Cloud Bigtable memory layers + +SYNOPSIS + gcloud beta bigtable memory-layers COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Manage Cloud Bigtable memory layers. + +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 Bigtable memory layer. + + update + (BETA) Update a Bigtable memory layer. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha bigtable memory-layers + diff --git a/gcloud/beta/bigtable/memory-layers/update b/gcloud/beta/bigtable/memory-layers/update new file mode 100644 index 000000000..a1489dac0 --- /dev/null +++ b/gcloud/beta/bigtable/memory-layers/update @@ -0,0 +1,80 @@ +NAME + gcloud beta bigtable memory-layers update - update a Bigtable memory layer + +SYNOPSIS + gcloud beta bigtable memory-layers update (CLUSTER : --instance=INSTANCE) + (--disable | --enable) [--async] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Update a Bigtable memory layer. + +EXAMPLES + To enable a memory layer, run: + + $ gcloud beta bigtable memory-layers update my-cluster-id \ + --instance=my-instance-id --enable + + To disable a memory layer, run: + + $ gcloud beta bigtable memory-layers update my-cluster-id \ + --instance=my-instance-id --disable + +POSITIONAL ARGUMENTS + Cluster resource - The cluster of the memory layer 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 cluster on the command line with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + CLUSTER + ID of the cluster or fully qualified identifier for the cluster. + + To set the cluster attribute: + ▸ provide the argument cluster on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --instance=INSTANCE + Bigtable instance for the cluster. + + To set the instance attribute: + ▸ provide the argument cluster on the command line with a fully + specified name; + ▸ provide the argument --instance on the command line. + +REQUIRED FLAGS + Exactly one of these must be specified: + + --disable + Disable the memory layer for the cluster. + + --enable + Enable the memory layer for the cluster. + +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. This + variant is also available: + + $ gcloud alpha bigtable memory-layers update + diff --git a/gcloud/beta/bigtable/tables/create b/gcloud/beta/bigtable/tables/create index 16ac3c230..5b1308de2 100644 --- a/gcloud/beta/bigtable/tables/create +++ b/gcloud/beta/bigtable/tables/create @@ -9,8 +9,10 @@ SYNOPSIS [--row-key-schema-definition-file=ROW_KEY_SCHEMA_DEFINITION_FILE] [--row-key-schema-pre-encoded-bytes] [--splits=[SPLITS,...]] [--tiered-storage-infrequent-access-older-than=TIERED_STORAGE_INFREQUENT_ACCESS_OLDER_THAN] - [--automated-backup-retention-period=AUTOMATED_BACKUP_RETENTION_PERIOD - | --enable-automated-backup] [GCLOUD_WIDE_FLAG ...] + [--enable-automated-backup + | --automated-backup-locations=[LOCATION,...] + --automated-backup-retention-period=AUTOMATED_BACKUP_RETENTION_PERIOD] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) Create a new Cloud Bigtable table. @@ -79,6 +81,13 @@ EXAMPLES --instance=my-instance --column-families="my-family" \ --automated-backup-retention_period=30d + To create a table my-table with a custom automated backup policy configured + to take backups in only us-central1-b and us-east1-c, run: + + $ gcloud beta bigtable tables create my-table \ + --instance=my-instance \ + --automated-backup-locations=us-central1-b,us-east1-c + POSITIONAL ARGUMENTS Table resource - Cloud Bigtable table to create. The arguments in this group can be used to specify the attributes of this resource. (NOTE) Some @@ -167,15 +176,28 @@ OPTIONAL FLAGS At most one of these can be specified: - --automated-backup-retention-period=AUTOMATED_BACKUP_RETENTION_PERIOD - The retention period of automated backup in the format of 30d for 30 - days. Min retention period is 3d and max is 90d. Setting this flag - will enable automated backup for the table. - --enable-automated-backup Once set, enables the default automated backup policy (retention_period=7d, frequency=1d) for the table. + Or at least one of these can be specified: + + Group for automated backup policy parameters. + + --automated-backup-locations=[LOCATION,...] + List of Cloud Bigtable zones where automated backups are allowed to + be created. If empty, automated backups will be created in all + zones of the instance. Locations are in the format + projects/{project}/locations/{zone}. Setting this flag will enable + automated backup for the table. If automated backup retention + period is not specified, it defaults to 7 days. + + --automated-backup-retention-period=AUTOMATED_BACKUP_RETENTION_PERIOD + The retention period of automated backup in the format of 30d for + 30 days. Min retention period is 3d and max is 90d. Setting this + flag will enable automated backup for the table. If automated + backup retention period is not specified, it defaults to 7 days. + 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/tables/update b/gcloud/beta/bigtable/tables/update index 8ac6a0990..5a52ed73b 100644 --- a/gcloud/beta/bigtable/tables/update +++ b/gcloud/beta/bigtable/tables/update @@ -6,7 +6,9 @@ SYNOPSIS gcloud beta bigtable tables update (TABLE : --instance=INSTANCE) [--async] [--deletion-protection] [--row-key-schema-pre-encoded-bytes] [--automated-backup-retention-period=AUTOMATED_BACKUP_RETENTION_PERIOD - | --disable-automated-backup | --enable-automated-backup] + --automated-backup-locations=[LOCATION,...] + | --clear-automated-backup-locations | --disable-automated-backup + | --enable-automated-backup] [--change-stream-retention-period=CHANGE_STREAM_RETENTION_PERIOD | --clear-change-stream-retention-period] [--clear-row-key-schema @@ -56,7 +58,19 @@ EXAMPLES retain backups for 30 days, run: $ gcloud beta bigtable tables update my-table \ - --instance=my-instance --automated-backup-retention_period=30d + --instance=my-instance --automated-backup-retention-period=30d + + To enable or update a custom automated backup policy and configure it to + take backups in only us-central1-b and us-east1-c, run: + + $ gcloud beta bigtable tables update my-table \ + --instance=my-instance \ + --automated-backup-locations=us-central1-b,us-east1-c + + To empty the automated backup locations list, run: + + $ gcloud beta bigtable tables update my-table \ + --instance=my-instance --clear-automated-backup-locations POSITIONAL ARGUMENTS Table resource - Cloud Bigtable table to update. The arguments in this @@ -109,19 +123,35 @@ FLAGS At most one of these can be specified: + Group for automated backup policy parameters. + --automated-backup-retention-period=AUTOMATED_BACKUP_RETENTION_PERIOD The retention period of automated backup in the format of 30d for 30 days. Min retention period is 3d and max is 90d. Setting this flag will enable automated backup for the table. - --disable-automated-backup - Once set, disables automated backup policy for the table. + At most one of these can be specified: - --enable-automated-backup - Once set, enables the default automated backup policy - (retention_period=7d, frequency=1d) for the table. Note: If a table - has automated backup enabled, this flag resets it to the default - policy. + --automated-backup-locations=[LOCATION,...] + List of Cloud Bigtable zones where automated backups are allowed to + be created. If empty, automated backups will be created in all + zones of the instance. Locations are in the format + projects/{project}/locations/{zone}. Setting this flag will enable + automated backup for the table. + + --clear-automated-backup-locations + Empty the automated backup locations list if populated. + + At most one of these can be specified: + + --disable-automated-backup + Once set, disables automated backup policy for the table. + + --enable-automated-backup + Once set, enables the default automated backup policy + (retention_period=7d, frequency=1d) for the table. Note: If a table + has automated backup enabled, this flag resets it to the default + policy. At most one of these can be specified: diff --git a/gcloud/beta/certificate-manager/certificates/create b/gcloud/beta/certificate-manager/certificates/create index 70a406b37..80bd29825 100644 --- a/gcloud/beta/certificate-manager/certificates/create +++ b/gcloud/beta/certificate-manager/certificates/create @@ -181,7 +181,8 @@ GCLOUD WIDE FLAGS API REFERENCE This command uses the certificatemanager/v1 API. The full documentation for - this API can be found at: https://cloud.google.com/certificate-manager + this API can be found at: + https://docs.cloud.google.com/certificate-manager/docs/overview NOTES This command is currently in beta and might change without notice. These diff --git a/gcloud/beta/certificate-manager/certificates/describe b/gcloud/beta/certificate-manager/certificates/describe index a90858b1a..bf8b5ec07 100644 --- a/gcloud/beta/certificate-manager/certificates/describe +++ b/gcloud/beta/certificate-manager/certificates/describe @@ -58,7 +58,8 @@ GCLOUD WIDE FLAGS API REFERENCE This command uses the certificatemanager/v1 API. The full documentation for - this API can be found at: https://cloud.google.com/certificate-manager + this API can be found at: + https://docs.cloud.google.com/certificate-manager/docs/overview NOTES This command is currently in beta and might change without notice. These diff --git a/gcloud/beta/certificate-manager/dns-authorizations/create b/gcloud/beta/certificate-manager/dns-authorizations/create index 32af185d1..1abb3b13a 100644 --- a/gcloud/beta/certificate-manager/dns-authorizations/create +++ b/gcloud/beta/certificate-manager/dns-authorizations/create @@ -84,7 +84,8 @@ GCLOUD WIDE FLAGS API REFERENCE This command uses the certificatemanager/v1 API. The full documentation for - this API can be found at: https://cloud.google.com/certificate-manager + this API can be found at: + https://docs.cloud.google.com/certificate-manager/docs/overview NOTES This command is currently in beta and might change without notice. These diff --git a/gcloud/beta/certificate-manager/dns-authorizations/delete b/gcloud/beta/certificate-manager/dns-authorizations/delete index 2544af92b..0542f2734 100644 --- a/gcloud/beta/certificate-manager/dns-authorizations/delete +++ b/gcloud/beta/certificate-manager/dns-authorizations/delete @@ -64,7 +64,8 @@ GCLOUD WIDE FLAGS API REFERENCE This command uses the certificatemanager/v1 API. The full documentation for - this API can be found at: https://cloud.google.com/certificate-manager + this API can be found at: + https://docs.cloud.google.com/certificate-manager/docs/overview NOTES This command is currently in beta and might change without notice. These diff --git a/gcloud/beta/certificate-manager/dns-authorizations/describe b/gcloud/beta/certificate-manager/dns-authorizations/describe index 23338f23e..cebdde715 100644 --- a/gcloud/beta/certificate-manager/dns-authorizations/describe +++ b/gcloud/beta/certificate-manager/dns-authorizations/describe @@ -58,7 +58,8 @@ GCLOUD WIDE FLAGS API REFERENCE This command uses the certificatemanager/v1 API. The full documentation for - this API can be found at: https://cloud.google.com/certificate-manager + this API can be found at: + https://docs.cloud.google.com/certificate-manager/docs/overview NOTES This command is currently in beta and might change without notice. These diff --git a/gcloud/beta/certificate-manager/dns-authorizations/list b/gcloud/beta/certificate-manager/dns-authorizations/list index 6c890e47b..04883987e 100644 --- a/gcloud/beta/certificate-manager/dns-authorizations/list +++ b/gcloud/beta/certificate-manager/dns-authorizations/list @@ -78,7 +78,8 @@ GCLOUD WIDE FLAGS API REFERENCE This command uses the certificatemanager/v1 API. The full documentation for - this API can be found at: https://cloud.google.com/certificate-manager + this API can be found at: + https://docs.cloud.google.com/certificate-manager/docs/overview NOTES This command is currently in beta and might change without notice. These diff --git a/gcloud/beta/certificate-manager/dns-authorizations/update b/gcloud/beta/certificate-manager/dns-authorizations/update index d7e78efef..74140f7d2 100644 --- a/gcloud/beta/certificate-manager/dns-authorizations/update +++ b/gcloud/beta/certificate-manager/dns-authorizations/update @@ -98,7 +98,8 @@ GCLOUD WIDE FLAGS API REFERENCE This command uses the certificatemanager/v1 API. The full documentation for - this API can be found at: https://cloud.google.com/certificate-manager + this API can be found at: + https://docs.cloud.google.com/certificate-manager/docs/overview NOTES This command is currently in beta and might change without notice. These diff --git a/gcloud/beta/certificate-manager/issuance-configs/create b/gcloud/beta/certificate-manager/issuance-configs/create index f8a00781b..84baa7fda 100644 --- a/gcloud/beta/certificate-manager/issuance-configs/create +++ b/gcloud/beta/certificate-manager/issuance-configs/create @@ -100,7 +100,8 @@ GCLOUD WIDE FLAGS API REFERENCE This command uses the certificatemanager/v1 API. The full documentation for - this API can be found at: https://cloud.google.com/certificate-manager + this API can be found at: + https://docs.cloud.google.com/certificate-manager/docs/overview NOTES This command is currently in beta and might change without notice. These diff --git a/gcloud/beta/certificate-manager/issuance-configs/delete b/gcloud/beta/certificate-manager/issuance-configs/delete index 36a647f62..a89bd344b 100644 --- a/gcloud/beta/certificate-manager/issuance-configs/delete +++ b/gcloud/beta/certificate-manager/issuance-configs/delete @@ -64,7 +64,8 @@ GCLOUD WIDE FLAGS API REFERENCE This command uses the certificatemanager/v1 API. The full documentation for - this API can be found at: https://cloud.google.com/certificate-manager + this API can be found at: + https://docs.cloud.google.com/certificate-manager/docs/overview NOTES This command is currently in beta and might change without notice. These diff --git a/gcloud/beta/certificate-manager/issuance-configs/describe b/gcloud/beta/certificate-manager/issuance-configs/describe index 9b5f9bdc8..ca3fbe30e 100644 --- a/gcloud/beta/certificate-manager/issuance-configs/describe +++ b/gcloud/beta/certificate-manager/issuance-configs/describe @@ -59,7 +59,8 @@ GCLOUD WIDE FLAGS API REFERENCE This command uses the certificatemanager/v1 API. The full documentation for - this API can be found at: https://cloud.google.com/certificate-manager + this API can be found at: + https://docs.cloud.google.com/certificate-manager/docs/overview NOTES This command is currently in beta and might change without notice. These diff --git a/gcloud/beta/certificate-manager/issuance-configs/list b/gcloud/beta/certificate-manager/issuance-configs/list index c7785dfa7..0d925f172 100644 --- a/gcloud/beta/certificate-manager/issuance-configs/list +++ b/gcloud/beta/certificate-manager/issuance-configs/list @@ -77,7 +77,8 @@ GCLOUD WIDE FLAGS API REFERENCE This command uses the certificatemanager/v1 API. The full documentation for - this API can be found at: https://cloud.google.com/certificate-manager + this API can be found at: + https://docs.cloud.google.com/certificate-manager/docs/overview NOTES This command is currently in beta and might change without notice. These diff --git a/gcloud/beta/certificate-manager/issuance-configs/update b/gcloud/beta/certificate-manager/issuance-configs/update index bbb3dab02..e6060cd6a 100644 --- a/gcloud/beta/certificate-manager/issuance-configs/update +++ b/gcloud/beta/certificate-manager/issuance-configs/update @@ -101,7 +101,8 @@ GCLOUD WIDE FLAGS API REFERENCE This command uses the certificatemanager/v1 API. The full documentation for - this API can be found at: https://cloud.google.com/certificate-manager + this API can be found at: + https://docs.cloud.google.com/certificate-manager/docs/overview NOTES This command is currently in beta and might change without notice. These diff --git a/gcloud/beta/certificate-manager/operations/describe b/gcloud/beta/certificate-manager/operations/describe index a3278620d..7942fdfe8 100644 --- a/gcloud/beta/certificate-manager/operations/describe +++ b/gcloud/beta/certificate-manager/operations/describe @@ -57,7 +57,8 @@ GCLOUD WIDE FLAGS API REFERENCE This command uses the certificatemanager/v1 API. The full documentation for - this API can be found at: https://cloud.google.com/certificate-manager + this API can be found at: + https://docs.cloud.google.com/certificate-manager/docs/overview NOTES This command is currently in beta and might change without notice. These diff --git a/gcloud/beta/certificate-manager/operations/list b/gcloud/beta/certificate-manager/operations/list index 1739996f5..716596b7f 100644 --- a/gcloud/beta/certificate-manager/operations/list +++ b/gcloud/beta/certificate-manager/operations/list @@ -76,7 +76,8 @@ GCLOUD WIDE FLAGS API REFERENCE This command uses the certificatemanager/v1 API. The full documentation for - this API can be found at: https://cloud.google.com/certificate-manager + this API can be found at: + https://docs.cloud.google.com/certificate-manager/docs/overview NOTES This command is currently in beta and might change without notice. These diff --git a/gcloud/beta/certificate-manager/trust-configs/create b/gcloud/beta/certificate-manager/trust-configs/create index f8e72e453..c39b22136 100644 --- a/gcloud/beta/certificate-manager/trust-configs/create +++ b/gcloud/beta/certificate-manager/trust-configs/create @@ -109,7 +109,8 @@ GCLOUD WIDE FLAGS API REFERENCE This command uses the certificatemanager/v1 API. The full documentation for - this API can be found at: https://cloud.google.com/certificate-manager + this API can be found at: + https://docs.cloud.google.com/certificate-manager/docs/overview NOTES This command is currently in beta and might change without notice. These diff --git a/gcloud/beta/certificate-manager/trust-configs/delete b/gcloud/beta/certificate-manager/trust-configs/delete index 2efcbaabc..e01abb42f 100644 --- a/gcloud/beta/certificate-manager/trust-configs/delete +++ b/gcloud/beta/certificate-manager/trust-configs/delete @@ -67,7 +67,8 @@ GCLOUD WIDE FLAGS API REFERENCE This command uses the certificatemanager/v1 API. The full documentation for - this API can be found at: https://cloud.google.com/certificate-manager + this API can be found at: + https://docs.cloud.google.com/certificate-manager/docs/overview NOTES This command is currently in beta and might change without notice. These diff --git a/gcloud/beta/certificate-manager/trust-configs/describe b/gcloud/beta/certificate-manager/trust-configs/describe index 743b4ae3c..9f103840c 100644 --- a/gcloud/beta/certificate-manager/trust-configs/describe +++ b/gcloud/beta/certificate-manager/trust-configs/describe @@ -58,7 +58,8 @@ GCLOUD WIDE FLAGS API REFERENCE This command uses the certificatemanager/v1 API. The full documentation for - this API can be found at: https://cloud.google.com/certificate-manager + this API can be found at: + https://docs.cloud.google.com/certificate-manager/docs/overview NOTES This command is currently in beta and might change without notice. These diff --git a/gcloud/beta/certificate-manager/trust-configs/export b/gcloud/beta/certificate-manager/trust-configs/export index cf6a0f23f..bc31d3073 100644 --- a/gcloud/beta/certificate-manager/trust-configs/export +++ b/gcloud/beta/certificate-manager/trust-configs/export @@ -67,7 +67,8 @@ GCLOUD WIDE FLAGS API REFERENCE This command uses the certificatemanager/v1 API. The full documentation for - this API can be found at: https://cloud.google.com/certificate-manager + this API can be found at: + https://docs.cloud.google.com/certificate-manager/docs/overview NOTES This command is currently in beta and might change without notice. These diff --git a/gcloud/beta/certificate-manager/trust-configs/import b/gcloud/beta/certificate-manager/trust-configs/import index c7fd1a6ae..8d154087a 100644 --- a/gcloud/beta/certificate-manager/trust-configs/import +++ b/gcloud/beta/certificate-manager/trust-configs/import @@ -80,7 +80,8 @@ GCLOUD WIDE FLAGS API REFERENCE This command uses the certificatemanager/v1 API. The full documentation for - this API can be found at: https://cloud.google.com/certificate-manager + this API can be found at: + https://docs.cloud.google.com/certificate-manager/docs/overview NOTES This command is currently in beta and might change without notice. These diff --git a/gcloud/beta/certificate-manager/trust-configs/list b/gcloud/beta/certificate-manager/trust-configs/list index 6b6e5d549..d60015647 100644 --- a/gcloud/beta/certificate-manager/trust-configs/list +++ b/gcloud/beta/certificate-manager/trust-configs/list @@ -77,7 +77,8 @@ GCLOUD WIDE FLAGS API REFERENCE This command uses the certificatemanager/v1 API. The full documentation for - this API can be found at: https://cloud.google.com/certificate-manager + this API can be found at: + https://docs.cloud.google.com/certificate-manager/docs/overview NOTES This command is currently in beta and might change without notice. These diff --git a/gcloud/beta/certificate-manager/trust-configs/update b/gcloud/beta/certificate-manager/trust-configs/update index b7d12bf55..eee1487b6 100644 --- a/gcloud/beta/certificate-manager/trust-configs/update +++ b/gcloud/beta/certificate-manager/trust-configs/update @@ -148,7 +148,8 @@ GCLOUD WIDE FLAGS API REFERENCE This command uses the certificatemanager/v1 API. The full documentation for - this API can be found at: https://cloud.google.com/certificate-manager + this API can be found at: + https://docs.cloud.google.com/certificate-manager/docs/overview NOTES This command is currently in beta and might change without notice. These diff --git a/gcloud/beta/composer/environments/create b/gcloud/beta/composer/environments/create index 60f3ca745..f93b9d4ca 100644 --- a/gcloud/beta/composer/environments/create +++ b/gcloud/beta/composer/environments/create @@ -6,7 +6,8 @@ SYNOPSIS gcloud beta composer environments create (ENVIRONMENT : --location=LOCATION) [--airflow-configs=[KEY=VALUE,...]] [--airflow-database-retention-days=AIRFLOW_DATABASE_RETENTION_DAYS] - [--async] [--cloud-sql-machine-type=CLOUD_SQL_MACHINE_TYPE] + [--async] [--cloud-run-functions-routing=CLOUD_RUN_FUNCTIONS_ROUTING] + [--cloud-sql-machine-type=CLOUD_SQL_MACHINE_TYPE] [--cloud-sql-preferred-zone=CLOUD_SQL_PREFERRED_ZONE] [--composer-internal-ipv4-cidr-block=COMPOSER_INTERNAL_IPV4_CIDR_BLOCK] [--disable-logs-in-cloud-logging-only] [--disk-size=DISK_SIZE] @@ -133,6 +134,14 @@ FLAGS Return immediately, without waiting for the operation in progress to complete. + Group of arguments for configuring traffic routing in Composer 3 or + greater. + + --cloud-run-functions-routing=CLOUD_RUN_FUNCTIONS_ROUTING + Controls how network traffic to Cloud Run functions is routed. + CLOUD_RUN_FUNCTIONS_ROUTING must be one of: direct, + via-network-attachment. + --cloud-sql-machine-type=CLOUD_SQL_MACHINE_TYPE Cloud SQL machine type used by the Airflow database. The list of available machine types is available here: diff --git a/gcloud/beta/composer/environments/update b/gcloud/beta/composer/environments/update index 729bb4b21..75b959000 100644 --- a/gcloud/beta/composer/environments/update +++ b/gcloud/beta/composer/environments/update @@ -6,6 +6,7 @@ SYNOPSIS gcloud beta composer environments update (ENVIRONMENT : --location=LOCATION) (--airflow-database-retention-days=AIRFLOW_DATABASE_RETENTION_DAYS + | --cloud-run-functions-routing=CLOUD_RUN_FUNCTIONS_ROUTING | --cloud-sql-machine-type=CLOUD_SQL_MACHINE_TYPE | --disable-high-resilience | --disable-logs-in-cloud-logging-only | --disable-private-environment | --enable-high-resilience @@ -111,6 +112,16 @@ REQUIRED FLAGS The number of days for the Airflow database retention period. If set to 0, the Airflow database retention mechanism will be disabled. + Or at least one of these can be specified: + + Group of arguments for configuring traffic routing in Composer 3 or + greater. + + --cloud-run-functions-routing=CLOUD_RUN_FUNCTIONS_ROUTING + Controls how network traffic to Cloud Run functions is routed. + CLOUD_RUN_FUNCTIONS_ROUTING must be one of: direct, + via-network-attachment. + --cloud-sql-machine-type=CLOUD_SQL_MACHINE_TYPE Cloud SQL machine type used by the Airflow database. The list of available machine types is available here: diff --git a/gcloud/beta/compute/addresses/create b/gcloud/beta/compute/addresses/create index 1686a6692..0d3190d72 100644 --- a/gcloud/beta/compute/addresses/create +++ b/gcloud/beta/compute/addresses/create @@ -64,6 +64,20 @@ EXAMPLES --addresses=10.110.0.10 --purpose=PRIVATE_SERVICE_CONNECT \ --network=default + To reserve an external IPv4 address for global passthrough Network Load + Balancer in availability group 0, run: + + $ gcloud beta compute addresses create gnlb-ipv4-address-0 \ + --global --ip-version=IPV4 \ + --purpose=PASSTHROUGH_LOAD_BALANCER_AVAILABILITY_GROUP0 + + To reserve an external IPv6 address for global passthrough Network Load + Balancer in availability group 1, run: + + $ gcloud beta compute addresses create gnlb-ipv6-address-1 \ + --global --ip-version=IPV6 \ + --purpose=PASSTHROUGH_LOAD_BALANCER_AVAILABILITY_GROUP1 + POSITIONAL ARGUMENTS [NAME ...] Names of the addresses to create. @@ -108,10 +122,15 @@ FLAGS addresses. --purpose=PURPOSE - The purpose of the address resource. This field is not applicable to - external addresses. PURPOSE must be one of: VPC_PEERING, + The purpose of the address resource. VPC_PEERING, + SHARED_LOADBALANCER_VIP, GCE_ENDPOINT, IPSEC_INTERCONNECT, and + PRIVATE_SERVICE_CONNECT are only applicable to internal addresses. + PASSTHROUGH_LOAD_BALANCER_AVAILABILITY_GROUP0 and + PASSTHROUGH_LOAD_BALANCER_AVAILABILITY_GROUP1 are only applicable to + global external addresses. PURPOSE must be one of: VPC_PEERING, SHARED_LOADBALANCER_VIP, GCE_ENDPOINT, IPSEC_INTERCONNECT, - PRIVATE_SERVICE_CONNECT. + PRIVATE_SERVICE_CONNECT, PASSTHROUGH_LOAD_BALANCER_AVAILABILITY_GROUP0, + PASSTHROUGH_LOAD_BALANCER_AVAILABILITY_GROUP1. --subnet=SUBNET If specified, the subnet name in which the address(es) should be diff --git a/gcloud/beta/compute/addresses/help b/gcloud/beta/compute/addresses/help index 0fb342caa..f45f5cc02 100644 --- a/gcloud/beta/compute/addresses/help +++ b/gcloud/beta/compute/addresses/help @@ -38,7 +38,7 @@ COMMANDS (BETA) Move an address to another project. update - (BETA) Update a Compute Engine address. + (BETA) Update an address's labels. NOTES This command is currently in beta and might change without notice. These diff --git a/gcloud/beta/compute/addresses/update b/gcloud/beta/compute/addresses/update index f0a96db85..ba27576e5 100644 --- a/gcloud/beta/compute/addresses/update +++ b/gcloud/beta/compute/addresses/update @@ -1,5 +1,5 @@ NAME - gcloud beta compute addresses update - update a Compute Engine address + gcloud beta compute addresses update - update an address's labels SYNOPSIS gcloud beta compute addresses update NAME [--update-labels=[KEY=VALUE,...]] @@ -79,8 +79,10 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud compute addresses update $ gcloud alpha compute addresses update diff --git a/gcloud/beta/compute/backend-buckets/set-iam-policy b/gcloud/beta/compute/backend-buckets/set-iam-policy index 901d5a23e..3ce12116f 100644 --- a/gcloud/beta/compute/backend-buckets/set-iam-policy +++ b/gcloud/beta/compute/backend-buckets/set-iam-policy @@ -12,7 +12,7 @@ DESCRIPTION EXAMPLES The following command will read an IAM policy defined in a JSON file - 'policy.json' and set it for the regionalbackend bucket my-backend-bucket: + 'policy.json' and set it for the regional backend bucket my-backend-bucket: $ gcloud beta compute backend-buckets set-iam-policy \ my-backend-bucket policy.json --region=REGION diff --git a/gcloud/beta/compute/backend-services/add-backend b/gcloud/beta/compute/backend-services/add-backend index 8937ef212..4bfb3d967 100644 --- a/gcloud/beta/compute/backend-services/add-backend +++ b/gcloud/beta/compute/backend-services/add-backend @@ -195,7 +195,7 @@ OPTIONAL FLAGS Spreads load based on custom defined and reported metrics. IN_FLIGHT - Available if the backend service's load balancing scheme is + Available if the backend service's load balancing scheme is INTERNAL_MANAGED, INTERNAL_SELF_MANAGED, or EXTERNAL_MANAGED. Available if the backend service's protocol is one of HTTP, HTTPS, or HTTP/2. diff --git a/gcloud/beta/compute/backend-services/update b/gcloud/beta/compute/backend-services/update index aa01c55ee..fcef8e93f 100644 --- a/gcloud/beta/compute/backend-services/update +++ b/gcloud/beta/compute/backend-services/update @@ -313,7 +313,16 @@ FLAGS IPV6_ONLY. --load-balancing-scheme=LOAD_BALANCING_SCHEME - Only for the Global external Application Load Balancer migration. + Specifies the load balancer type. Choose EXTERNAL for the classic + Application Load Balancers. Choose EXTERNAL_MANAGED for the Envoy-based + global external Application Load Balancers For more information, refer + to this guide: + https://cloud.google.com/load-balancing/docs/choosing-load-balancer. + + This field should only be used for migration from the Classic + Application Load Balancer to the global external Application Load + Balancer. The --load-balancing-scheme is immutable for all other use + cases. The value of this field must be EXTERNAL or EXTERNAL_MANAGED. diff --git a/gcloud/beta/compute/backend-services/update-backend b/gcloud/beta/compute/backend-services/update-backend index 2a8acb3e1..8cb6b9990 100644 --- a/gcloud/beta/compute/backend-services/update-backend +++ b/gcloud/beta/compute/backend-services/update-backend @@ -166,7 +166,7 @@ OPTIONAL FLAGS Spreads load based on custom defined and reported metrics. IN_FLIGHT - Available if the backend service's load balancing scheme is + Available if the backend service's load balancing scheme is INTERNAL_MANAGED, INTERNAL_SELF_MANAGED, or EXTERNAL_MANAGED. Available if the backend service's protocol is one of HTTP, HTTPS, or HTTP/2. diff --git a/gcloud/beta/compute/composite-health-checks/create b/gcloud/beta/compute/composite-health-checks/create index 3409ff398..a15755692 100644 --- a/gcloud/beta/compute/composite-health-checks/create +++ b/gcloud/beta/compute/composite-health-checks/create @@ -87,8 +87,10 @@ API REFERENCE can be found at: https://cloud.google.com/compute/ NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud compute composite-health-checks create $ gcloud alpha compute composite-health-checks create diff --git a/gcloud/beta/compute/composite-health-checks/delete b/gcloud/beta/compute/composite-health-checks/delete index e01965405..e5a81ae77 100644 --- a/gcloud/beta/compute/composite-health-checks/delete +++ b/gcloud/beta/compute/composite-health-checks/delete @@ -67,8 +67,10 @@ API REFERENCE can be found at: https://cloud.google.com/compute/ NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud compute composite-health-checks delete $ gcloud alpha compute composite-health-checks delete diff --git a/gcloud/beta/compute/composite-health-checks/describe b/gcloud/beta/compute/composite-health-checks/describe index 7e6e5e308..1db945faa 100644 --- a/gcloud/beta/compute/composite-health-checks/describe +++ b/gcloud/beta/compute/composite-health-checks/describe @@ -62,8 +62,10 @@ API REFERENCE can be found at: https://cloud.google.com/compute/ NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud compute composite-health-checks describe $ gcloud alpha compute composite-health-checks describe diff --git a/gcloud/beta/compute/composite-health-checks/get-health b/gcloud/beta/compute/composite-health-checks/get-health index 2d5d8bd05..794ece2b9 100644 --- a/gcloud/beta/compute/composite-health-checks/get-health +++ b/gcloud/beta/compute/composite-health-checks/get-health @@ -33,8 +33,10 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud compute composite-health-checks get-health $ gcloud alpha compute composite-health-checks get-health diff --git a/gcloud/beta/compute/composite-health-checks/help b/gcloud/beta/compute/composite-health-checks/help index 4fd4de79a..305a4dee5 100644 --- a/gcloud/beta/compute/composite-health-checks/help +++ b/gcloud/beta/compute/composite-health-checks/help @@ -35,8 +35,10 @@ COMMANDS (BETA) Update a composite health check. NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud compute composite-health-checks $ gcloud alpha compute composite-health-checks diff --git a/gcloud/beta/compute/composite-health-checks/list b/gcloud/beta/compute/composite-health-checks/list index 7c11ed99f..a721ce732 100644 --- a/gcloud/beta/compute/composite-health-checks/list +++ b/gcloud/beta/compute/composite-health-checks/list @@ -71,8 +71,10 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud compute composite-health-checks list $ gcloud alpha compute composite-health-checks list diff --git a/gcloud/beta/compute/composite-health-checks/update b/gcloud/beta/compute/composite-health-checks/update index 1d460da8c..93d737e5a 100644 --- a/gcloud/beta/compute/composite-health-checks/update +++ b/gcloud/beta/compute/composite-health-checks/update @@ -89,8 +89,10 @@ API REFERENCE can be found at: https://cloud.google.com/compute/ NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud compute composite-health-checks update $ gcloud alpha compute composite-health-checks update diff --git a/gcloud/beta/compute/disks/bulk/create b/gcloud/beta/compute/disks/bulk/create index 4f8c437fe..f39bb1213 100644 --- a/gcloud/beta/compute/disks/bulk/create +++ b/gcloud/beta/compute/disks/bulk/create @@ -1,16 +1,19 @@ NAME gcloud beta compute disks bulk create - create multiple Compute Engine - disks + disks or a consistency group of instant snapshots SYNOPSIS - gcloud beta compute disks bulk create - --source-consistency-group-policy=SOURCE_CONSISTENCY_GROUP_POLICY - (--region=REGION | --zone=ZONE) [GCLOUD_WIDE_FLAG ...] + gcloud beta compute disks bulk create (--region=REGION | --zone=ZONE) + [--source-consistency-group-policy=SOURCE_CONSISTENCY_GROUP_POLICY] + [--source-instant-snapshot-group=SOURCE_INSTANT_SNAPSHOT_GROUP] + [--source-instant-snapshot-group-region=SOURCE_INSTANT_SNAPSHOT_GROUP_REGION | --source-instant-snapshot-group-zone=SOURCE_INSTANT_SNAPSHOT_GROUP_ZONE] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) gcloud beta compute disks bulk create facilitates the creation of multiple Compute Engine disks with a single command. This includes cloning - a set of Async PD secondary disks with the same consistency group policy. + a set of Async PD secondary disks with the same consistency group policy or + a consistency group of instant snapshots. EXAMPLES To consistently clone secondary disks with the same consistency group @@ -24,16 +27,12 @@ EXAMPLES --zone=us-central1-a REQUIRED FLAGS - --source-consistency-group-policy=SOURCE_CONSISTENCY_GROUP_POLICY - URL of the source consistency group resource policy. The resource - policy is always the same region as the source disks. - Exactly one of these must be specified: --region=REGION - Target region of the created disks, which currently must be the same - as the source region. If not specified, you might be prompted to - select a region (interactive mode only). + The region in which to create the disks, which must be the same as + the source region. If not specified, you might be prompted to select + a region (interactive mode only). To avoid prompting when this flag is omitted, you can set the compute/region property: @@ -52,8 +51,8 @@ REQUIRED FLAGS CLOUDSDK_COMPUTE_REGION. --zone=ZONE - Target zone of the created disks, which currently must be the same as - the source zone. If not specified and the compute/zone property isn't + The zone in which to create the disks, which must be the same as the + source zone. If not specified and the compute/zone property isn't set, you might be prompted to select a zone (interactive mode only). To avoid prompting when this flag is omitted, you can set the @@ -72,6 +71,29 @@ REQUIRED FLAGS Alternatively, the zone can be stored in the environment variable CLOUDSDK_COMPUTE_ZONE. +OPTIONAL FLAGS + --source-consistency-group-policy=SOURCE_CONSISTENCY_GROUP_POLICY + URL of the format regions//resourcePolicies/ + of the source consistency group resource policy. The resource policy is + always in the same region as the source disks. + + --source-instant-snapshot-group=SOURCE_INSTANT_SNAPSHOT_GROUP + URL of the format + regions//instantSnapshotGroups/ or + zones//instantSnapshotGroups/ of the + source consistency group of instant snapshots used to create the disks. + + At most one of these can be specified: + + --source-instant-snapshot-group-region=SOURCE_INSTANT_SNAPSHOT_GROUP_REGION + Region of the source instant snapshot group to operate on. Overrides + the default compute/region property value for this command + invocation. + + --source-instant-snapshot-group-zone=SOURCE_INSTANT_SNAPSHOT_GROUP_ZONE + Zone of the source instant snapshot group to operate on. 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, diff --git a/gcloud/beta/compute/disks/bulk/help b/gcloud/beta/compute/disks/bulk/help index f4f5e2163..5fa8c9a31 100644 --- a/gcloud/beta/compute/disks/bulk/help +++ b/gcloud/beta/compute/disks/bulk/help @@ -18,7 +18,8 @@ COMMANDS COMMAND is one of the following: create - (BETA) Create multiple Compute Engine disks. + (BETA) Create multiple Compute Engine disks or a consistency group of + instant snapshots. NOTES This command is currently in beta and might change without notice. These diff --git a/gcloud/beta/compute/disks/help b/gcloud/beta/compute/disks/help index 2c9adbb18..d5f792841 100644 --- a/gcloud/beta/compute/disks/help +++ b/gcloud/beta/compute/disks/help @@ -91,7 +91,7 @@ COMMANDS (BETA) Update a Compute Engine persistent disk. update-kms-key - (BETA) Update the KMS key of a persistent disk. + (BETA) Update the KMS key of a Hyperdisk or Persistent Disk. NOTES This command is currently in beta and might change without notice. These diff --git a/gcloud/beta/compute/disks/update b/gcloud/beta/compute/disks/update index f20355a0f..d42b4436c 100644 --- a/gcloud/beta/compute/disks/update +++ b/gcloud/beta/compute/disks/update @@ -15,8 +15,8 @@ SYNOPSIS [--region=REGION | --zone=ZONE] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) gcloud beta compute disks update updates a Compute Engine persistent - disk. + (BETA) gcloud beta compute disks update updates a Compute Engine Hyperdisk + or Persistent Disk. EXAMPLES To update labels 'k0' and 'k1' and remove label 'k3' of a disk, run: diff --git a/gcloud/beta/compute/disks/update-kms-key b/gcloud/beta/compute/disks/update-kms-key index f146b911a..29221a5a2 100644 --- a/gcloud/beta/compute/disks/update-kms-key +++ b/gcloud/beta/compute/disks/update-kms-key @@ -1,6 +1,6 @@ NAME gcloud beta compute disks update-kms-key - update the KMS key of a - persistent disk + Hyperdisk or Persistent Disk SYNOPSIS gcloud beta compute disks update-kms-key DISK_NAME @@ -9,12 +9,12 @@ SYNOPSIS [--region=REGION | --zone=ZONE] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) * gcloud beta compute disks update-kms-key * updates the KMS key of - a Compute Engine persistent disk by rotating it to the primary version of - the key or to the primary version of a new KMS key. + (BETA) gcloud beta compute disks update-kms-key updates the KMS key of a + Compute Engine Persistent or Hyperdisk Disk by rotating it to the primary + version of the key or to the primary version of a new KMS key. EXAMPLES - To rotate the KMS key of a disk named example-disk-1 to the primary + To change the KMS key of a disk named example-disk-1 to the primary version, run: $ gcloud beta compute disks update-kms-key example-disk-1 \ diff --git a/gcloud/beta/compute/forwarding-rules/describe b/gcloud/beta/compute/forwarding-rules/describe index f7e3735f3..a3be99e2b 100644 --- a/gcloud/beta/compute/forwarding-rules/describe +++ b/gcloud/beta/compute/forwarding-rules/describe @@ -3,7 +3,7 @@ NAME information about a forwarding rule SYNOPSIS - gcloud beta compute forwarding-rules describe NAME + gcloud beta compute forwarding-rules describe NAME [--view=VIEW] [--global | --region=REGION] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -21,11 +21,21 @@ EXAMPLES $ gcloud beta compute forwarding-rules describe FORWARDING-RULE \ --region=us-central1 + To get full details, including any extensions attached to the rule, run: + + $ gcloud beta compute forwarding-rules describe FORWARDING-RULE \ + --region=us-central1 --view=FULL + POSITIONAL ARGUMENTS NAME Name of the forwarding rule to describe. FLAGS + --view=VIEW + The view of the forwarding rule to return. BASIC includes the standard + fields. FULL includes standard fields plus any extensions attached to + the forwarding rule. VIEW must be one of: BASIC, FULL. + At most one of these can be specified: --global diff --git a/gcloud/beta/compute/future-reservations/create b/gcloud/beta/compute/future-reservations/create index bac594c6d..500ba41eb 100644 --- a/gcloud/beta/compute/future-reservations/create +++ b/gcloud/beta/compute/future-reservations/create @@ -17,6 +17,7 @@ SYNOPSIS [--[no-]require-specific-reservation] [--reservation-mode=RESERVATION_MODE] [--reservation-name=RESERVATION_NAME] + [--resource-manager-tags=[KEY=VALUE,...]] [--scheduling-type=SCHEDULING_TYPE] [--total-count=TOTAL_COUNT] [--zone=ZONE] [--auto-created-reservations-delete-time=AUTO_CREATED_RESERVATIONS_DELETE_TIME | --auto-created-reservations-duration=AUTO_CREATED_RESERVATIONS_DURATION] @@ -239,6 +240,9 @@ OPTIONAL FLAGS Approval with INACTIVE state till specified start-time. Either provide the reservation_name or a name_prefix. + --resource-manager-tags=[KEY=VALUE,...] + Resource manager tags to be bound to the future reservation. + --scheduling-type=SCHEDULING_TYPE Maintenance for the reserved capacity. SCHEDULING_TYPE must be one of: diff --git a/gcloud/beta/compute/global-vm-extension-policies/create b/gcloud/beta/compute/global-vm-extension-policies/create index ac0d97740..95ad88075 100644 --- a/gcloud/beta/compute/global-vm-extension-policies/create +++ b/gcloud/beta/compute/global-vm-extension-policies/create @@ -136,8 +136,10 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud compute global-vm-extension-policies create $ gcloud alpha compute global-vm-extension-policies create diff --git a/gcloud/beta/compute/global-vm-extension-policies/delete b/gcloud/beta/compute/global-vm-extension-policies/delete index 8c7f70472..700f784cf 100644 --- a/gcloud/beta/compute/global-vm-extension-policies/delete +++ b/gcloud/beta/compute/global-vm-extension-policies/delete @@ -50,8 +50,10 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud compute global-vm-extension-policies delete $ gcloud alpha compute global-vm-extension-policies delete diff --git a/gcloud/beta/compute/global-vm-extension-policies/describe b/gcloud/beta/compute/global-vm-extension-policies/describe index 6adf8903f..bec45334f 100644 --- a/gcloud/beta/compute/global-vm-extension-policies/describe +++ b/gcloud/beta/compute/global-vm-extension-policies/describe @@ -28,8 +28,10 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud compute global-vm-extension-policies describe $ gcloud alpha compute global-vm-extension-policies describe diff --git a/gcloud/beta/compute/global-vm-extension-policies/help b/gcloud/beta/compute/global-vm-extension-policies/help index 099cf7695..f09d5e986 100644 --- a/gcloud/beta/compute/global-vm-extension-policies/help +++ b/gcloud/beta/compute/global-vm-extension-policies/help @@ -33,8 +33,10 @@ COMMANDS (BETA) Update a Compute Engine global VM extension policy. NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud compute global-vm-extension-policies $ gcloud alpha compute global-vm-extension-policies diff --git a/gcloud/beta/compute/global-vm-extension-policies/list b/gcloud/beta/compute/global-vm-extension-policies/list index eac72e88a..b4e05b38b 100644 --- a/gcloud/beta/compute/global-vm-extension-policies/list +++ b/gcloud/beta/compute/global-vm-extension-policies/list @@ -56,8 +56,10 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud compute global-vm-extension-policies list $ gcloud alpha compute global-vm-extension-policies list diff --git a/gcloud/beta/compute/global-vm-extension-policies/update b/gcloud/beta/compute/global-vm-extension-policies/update index 415b7f370..4e4a7e65c 100644 --- a/gcloud/beta/compute/global-vm-extension-policies/update +++ b/gcloud/beta/compute/global-vm-extension-policies/update @@ -141,8 +141,10 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud compute global-vm-extension-policies update $ gcloud alpha compute global-vm-extension-policies update diff --git a/gcloud/beta/compute/health-aggregation-policies/create b/gcloud/beta/compute/health-aggregation-policies/create index 23ff2e5a9..b6d1952ec 100644 --- a/gcloud/beta/compute/health-aggregation-policies/create +++ b/gcloud/beta/compute/health-aggregation-policies/create @@ -107,8 +107,10 @@ API REFERENCE can be found at: https://cloud.google.com/compute/ NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud compute health-aggregation-policies create $ gcloud alpha compute health-aggregation-policies create diff --git a/gcloud/beta/compute/health-aggregation-policies/delete b/gcloud/beta/compute/health-aggregation-policies/delete index 48aca9918..0f5a498a5 100644 --- a/gcloud/beta/compute/health-aggregation-policies/delete +++ b/gcloud/beta/compute/health-aggregation-policies/delete @@ -68,8 +68,10 @@ API REFERENCE can be found at: https://cloud.google.com/compute/ NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud compute health-aggregation-policies delete $ gcloud alpha compute health-aggregation-policies delete diff --git a/gcloud/beta/compute/health-aggregation-policies/describe b/gcloud/beta/compute/health-aggregation-policies/describe index d75fc4e1f..b277854ce 100644 --- a/gcloud/beta/compute/health-aggregation-policies/describe +++ b/gcloud/beta/compute/health-aggregation-policies/describe @@ -63,8 +63,10 @@ API REFERENCE can be found at: https://cloud.google.com/compute/ NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud compute health-aggregation-policies describe $ gcloud alpha compute health-aggregation-policies describe diff --git a/gcloud/beta/compute/health-aggregation-policies/help b/gcloud/beta/compute/health-aggregation-policies/help index 128313a2a..e16492c95 100644 --- a/gcloud/beta/compute/health-aggregation-policies/help +++ b/gcloud/beta/compute/health-aggregation-policies/help @@ -33,8 +33,10 @@ COMMANDS (BETA) Update a health aggregation policy. NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud compute health-aggregation-policies $ gcloud alpha compute health-aggregation-policies diff --git a/gcloud/beta/compute/health-aggregation-policies/list b/gcloud/beta/compute/health-aggregation-policies/list index 17b7df245..28611fee1 100644 --- a/gcloud/beta/compute/health-aggregation-policies/list +++ b/gcloud/beta/compute/health-aggregation-policies/list @@ -71,8 +71,10 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud compute health-aggregation-policies list $ gcloud alpha compute health-aggregation-policies list diff --git a/gcloud/beta/compute/health-aggregation-policies/update b/gcloud/beta/compute/health-aggregation-policies/update index 8c46e3b76..3263ae63c 100644 --- a/gcloud/beta/compute/health-aggregation-policies/update +++ b/gcloud/beta/compute/health-aggregation-policies/update @@ -102,8 +102,10 @@ API REFERENCE can be found at: https://cloud.google.com/compute/ NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud compute health-aggregation-policies update $ gcloud alpha compute health-aggregation-policies update diff --git a/gcloud/beta/compute/health-sources/create b/gcloud/beta/compute/health-sources/create index 353abb6d1..ba1fbf52f 100644 --- a/gcloud/beta/compute/health-sources/create +++ b/gcloud/beta/compute/health-sources/create @@ -93,8 +93,10 @@ API REFERENCE can be found at: https://cloud.google.com/compute/ NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud compute health-sources create $ gcloud alpha compute health-sources create diff --git a/gcloud/beta/compute/health-sources/delete b/gcloud/beta/compute/health-sources/delete index 668698353..d705d7a3e 100644 --- a/gcloud/beta/compute/health-sources/delete +++ b/gcloud/beta/compute/health-sources/delete @@ -65,8 +65,10 @@ API REFERENCE can be found at: https://cloud.google.com/compute/ NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud compute health-sources delete $ gcloud alpha compute health-sources delete diff --git a/gcloud/beta/compute/health-sources/describe b/gcloud/beta/compute/health-sources/describe index 9caf6b9f5..b110d8d6c 100644 --- a/gcloud/beta/compute/health-sources/describe +++ b/gcloud/beta/compute/health-sources/describe @@ -61,8 +61,10 @@ API REFERENCE can be found at: https://cloud.google.com/compute/ NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud compute health-sources describe $ gcloud alpha compute health-sources describe diff --git a/gcloud/beta/compute/health-sources/get-health b/gcloud/beta/compute/health-sources/get-health index 7b3f889dd..34d882952 100644 --- a/gcloud/beta/compute/health-sources/get-health +++ b/gcloud/beta/compute/health-sources/get-health @@ -33,8 +33,10 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud compute health-sources get-health $ gcloud alpha compute health-sources get-health diff --git a/gcloud/beta/compute/health-sources/help b/gcloud/beta/compute/health-sources/help index 4d41cf02d..34facbbe4 100644 --- a/gcloud/beta/compute/health-sources/help +++ b/gcloud/beta/compute/health-sources/help @@ -34,8 +34,10 @@ COMMANDS (BETA) Update a health source. NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud compute health-sources $ gcloud alpha compute health-sources diff --git a/gcloud/beta/compute/health-sources/list b/gcloud/beta/compute/health-sources/list index 2184c3670..a67cbd6be 100644 --- a/gcloud/beta/compute/health-sources/list +++ b/gcloud/beta/compute/health-sources/list @@ -70,8 +70,10 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud compute health-sources list $ gcloud alpha compute health-sources list diff --git a/gcloud/beta/compute/health-sources/update b/gcloud/beta/compute/health-sources/update index 6f7a7111f..33cf0d1fe 100644 --- a/gcloud/beta/compute/health-sources/update +++ b/gcloud/beta/compute/health-sources/update @@ -88,8 +88,10 @@ API REFERENCE can be found at: https://cloud.google.com/compute/ NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud compute health-sources update $ gcloud alpha compute health-sources update diff --git a/gcloud/beta/compute/instances/add-metadata b/gcloud/beta/compute/instances/add-metadata index 4f8dab321..2d68d85a3 100644 --- a/gcloud/beta/compute/instances/add-metadata +++ b/gcloud/beta/compute/instances/add-metadata @@ -31,10 +31,10 @@ DESCRIPTION If you are using this command to manage SSH keys for your project, please note the risks - (https://cloud.google.com/compute/docs/instances/adding-removing-ssh-keys#risks) + (https://docs.cloud.google.com/compute/docs/instances/access-overview#risks) of manual SSH key management as well as the required format for SSH key metadata, available at - https://cloud.google.com/compute/docs/instances/adding-removing-ssh-keys. + https://docs.cloud.google.com/compute/docs/connect/add-ssh-keys. EXAMPLES To add metadata under key important-data to an instance named diff --git a/gcloud/beta/compute/instances/update-from-file b/gcloud/beta/compute/instances/update-from-file index 6360a0348..8f0af3129 100644 --- a/gcloud/beta/compute/instances/update-from-file +++ b/gcloud/beta/compute/instances/update-from-file @@ -4,7 +4,7 @@ NAME SYNOPSIS gcloud beta compute instances update-from-file INSTANCE_NAME - [--minimal-action=MINIMAL_ACTION] + [--discard-local-ssd] [--minimal-action=MINIMAL_ACTION] [--most-disruptive-allowed-action=MOST_DISRUPTIVE_ALLOWED_ACTION] [--source=SOURCE] [--zone=ZONE] [GCLOUD_WIDE_FLAG ...] @@ -26,6 +26,11 @@ POSITIONAL ARGUMENTS https://cloud.google.com/compute/docs/reference/rest/v1/instances FLAGS + --discard-local-ssd + If specified, all local SSDs data attached to this instance will be + discarded. This is only used with most-disruptive-allowed-action set to + RESTART. + --minimal-action=MINIMAL_ACTION If specified, this action or higher level action is performed on the instance irrespective of what action is required for the update to take diff --git a/gcloud/beta/compute/instant-snapshot-groups/create b/gcloud/beta/compute/instant-snapshot-groups/create index 2e6ebb88b..0bde1473f 100644 --- a/gcloud/beta/compute/instant-snapshot-groups/create +++ b/gcloud/beta/compute/instant-snapshot-groups/create @@ -1,6 +1,6 @@ NAME gcloud beta compute instant-snapshot-groups create - create a Compute - Engine instant snapshot group + Engine consistency group of instant snapshots SYNOPSIS gcloud beta compute instant-snapshot-groups create @@ -28,8 +28,10 @@ POSITIONAL ARGUMENTS REQUIRED FLAGS --source-consistency-group=SOURCE_CONSISTENCY_GROUP - URL of the source consistency group resource policy. The resource - policy is always in the same region as the source disks. + Specifies the source consistency group resource policy. The value + should be the relative name of the resource policy, in the format + ``regions/REGION/resourcePolicies/POLICY_NAME``. The resource policy is + always in the same region as the source disks. OPTIONAL FLAGS At most one of these can be specified: @@ -84,8 +86,10 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud compute instant-snapshot-groups create $ gcloud alpha compute instant-snapshot-groups create diff --git a/gcloud/beta/compute/instant-snapshot-groups/delete b/gcloud/beta/compute/instant-snapshot-groups/delete index 0d0f39f7e..856d8ae10 100644 --- a/gcloud/beta/compute/instant-snapshot-groups/delete +++ b/gcloud/beta/compute/instant-snapshot-groups/delete @@ -1,6 +1,6 @@ NAME gcloud beta compute instant-snapshot-groups delete - delete a Compute - Engine instant snapshot group + Engine consistency group of instant snapshots SYNOPSIS gcloud beta compute instant-snapshot-groups delete @@ -8,7 +8,7 @@ SYNOPSIS [--region=REGION | --zone=ZONE] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) Delete a Compute Engine instant snapshot group. + (BETA) Delete a Compute Engine consistency group of instant snapshots. POSITIONAL ARGUMENTS INSTANT_SNAPSHOT_GROUP_NAME [INSTANT_SNAPSHOT_GROUP_NAME ...] @@ -67,8 +67,10 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud compute instant-snapshot-groups delete $ gcloud alpha compute instant-snapshot-groups delete diff --git a/gcloud/beta/compute/instant-snapshot-groups/describe b/gcloud/beta/compute/instant-snapshot-groups/describe index 120f42bd7..b266bb7ac 100644 --- a/gcloud/beta/compute/instant-snapshot-groups/describe +++ b/gcloud/beta/compute/instant-snapshot-groups/describe @@ -1,6 +1,6 @@ NAME gcloud beta compute instant-snapshot-groups describe - describe a Compute - Engine instant snapshot group + Engine consistency group of instant snapshots SYNOPSIS gcloud beta compute instant-snapshot-groups describe @@ -9,11 +9,12 @@ SYNOPSIS DESCRIPTION (BETA) gcloud beta compute instant-snapshot-groups describe displays all - data associated with a Compute Engine instant snapshot group in a project. + data associated with a Compute Engine consistency group of instant + snapshots in a project. EXAMPLES - To describe the instant snapshot group 'instant-snapshot-group-1' in zone - 'us-east1-a', run: + To describe the consistency group of instant snapshots + 'instant-snapshot-group-1' in zone 'us-east1-a', run: $ gcloud beta compute instant-snapshot-groups describe \ instant-snapshot-group-1 --zone=us-east1-a @@ -75,8 +76,10 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud compute instant-snapshot-groups describe $ gcloud alpha compute instant-snapshot-groups describe diff --git a/gcloud/beta/compute/instant-snapshot-groups/help b/gcloud/beta/compute/instant-snapshot-groups/help index b81f01e8d..1b083c3b6 100644 --- a/gcloud/beta/compute/instant-snapshot-groups/help +++ b/gcloud/beta/compute/instant-snapshot-groups/help @@ -17,20 +17,23 @@ COMMANDS COMMAND is one of the following: create - (BETA) Create a Compute Engine instant snapshot group. + (BETA) Create a Compute Engine consistency group of instant snapshots. delete - (BETA) Delete a Compute Engine instant snapshot group. + (BETA) Delete a Compute Engine consistency group of instant snapshots. describe - (BETA) Describe a Compute Engine instant snapshot group. + (BETA) Describe a Compute Engine consistency group of instant + snapshots. list (BETA) List Google Compute Engine instant snapshot groups. NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud compute instant-snapshot-groups $ gcloud alpha compute instant-snapshot-groups diff --git a/gcloud/beta/compute/instant-snapshot-groups/list b/gcloud/beta/compute/instant-snapshot-groups/list index c0084a6cb..4c57496f9 100644 --- a/gcloud/beta/compute/instant-snapshot-groups/list +++ b/gcloud/beta/compute/instant-snapshot-groups/list @@ -89,8 +89,10 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud compute instant-snapshot-groups list $ gcloud alpha compute instant-snapshot-groups list diff --git a/gcloud/beta/compute/interconnects/groups/create-members b/gcloud/beta/compute/interconnects/groups/create-members index 89ed80717..a815f71d9 100644 --- a/gcloud/beta/compute/interconnects/groups/create-members +++ b/gcloud/beta/compute/interconnects/groups/create-members @@ -28,7 +28,12 @@ EXAMPLES example-interconnect-group --interconnect-type=DEDICATED \ --link-type=LINK_TYPE_ETHERNET_10G_LR --requested-link-count=1 \ --facility=iad-1 --interconnect="name=interconnect1" \ - --interconnect="name=interconnect2" + --interconnect="name=interconnect2,facility=iad-5467" + + Note that facility is required for each member interconnect. + interconnect1's facility is set to the default value iad-1 and + interconnect2's facility is overridden to iad-5467 in the --interconnect + flag. POSITIONAL ARGUMENTS NAME @@ -44,12 +49,9 @@ REQUIRED FLAGS must be specified. These flags are defined as a comma separated list of flag=value pairs. - Example: --interconnect - name=interconnect1,facility=iad-1,description="my - interconnect",link-type=LINK_TYPE_ETHERNET_10G_LR,requested-link-count=1, - interconnect-type=DEDICATED,admin-enabled, - noc-contact-email=noc@google.com,customer-name=customer-name - requested-features=MACSEC:CROSS_SITE_NETWORK + Example: + + --interconnect name=interconnect1,facility=iad-1,description="my interconnect",link-type=LINK_TYPE_ETHERNET_10G_LR,requested-link-count=1,interconnect-type=DEDICATED,admin-enabled,noc-contact-email=noc@google.com,customer-name=customer-name,requested-features=MACSEC:CROSS_SITE_NETWORK Note that for multiple requested-features, use a colon (:) as the delimiter, as the comma is used to separate the flags. Similarly, if @@ -136,6 +138,21 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. +DEFAULTABLE PER-INTERCONNECT FLAGS + All flags except --intent-mismatch-behavior in the OPTIONAL FLAGS section + are defaultable per-interconnect. This means that you can set a default + value by using these flags, or you can override the value for each + interconnect by using the --interconnect flag. + + Furthermore, if the default values for the following flags are not + specified, then they must be specified per-interconnect in the + --interconnect flag: + + ▪ --facility + ▪ --interconnect-type + ▪ --link-type + ▪ --requested-link-count + NOTES This command is currently in beta and might change without notice. These variants are also available: diff --git a/gcloud/beta/compute/network-endpoint-groups/create b/gcloud/beta/compute/network-endpoint-groups/create index 2b18e5872..472345412 100644 --- a/gcloud/beta/compute/network-endpoint-groups/create +++ b/gcloud/beta/compute/network-endpoint-groups/create @@ -52,8 +52,14 @@ FLAGS private-service-connect. --network=NETWORK - Name of the network in which the NEG is created. default project - network is used if unspecified. + Name of the network in which the NEG is created. For + networkEndpointType GCE_VM_IP_PORT, GCE_VM_IP_PORTMAP or + NON_GCP_PRIVATE_IP_PORT, if this field is not specified, a default + network will be used. This field cannot be set for NEGs with + networkEndpointType set to SERVERLESS or PRIVATE_SERVICE_CONNECT and + for global NEGs. + + For all other network endpoint types, this field is required. This is only supported for NEGs with endpoint type gce-vm-ip-port, non-gcp-private-ip-port, gce-vm-ip, private-service-connect, diff --git a/gcloud/beta/compute/networks/peerings/cancel-request-delete b/gcloud/beta/compute/networks/peerings/cancel-request-delete index cfb85ba2d..43ce120c0 100644 --- a/gcloud/beta/compute/networks/peerings/cancel-request-delete +++ b/gcloud/beta/compute/networks/peerings/cancel-request-delete @@ -44,8 +44,10 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud compute networks peerings cancel-request-delete $ gcloud alpha compute networks peerings cancel-request-delete diff --git a/gcloud/beta/compute/project-info/add-metadata b/gcloud/beta/compute/project-info/add-metadata index b9ef336d7..417978291 100644 --- a/gcloud/beta/compute/project-info/add-metadata +++ b/gcloud/beta/compute/project-info/add-metadata @@ -21,10 +21,10 @@ DESCRIPTION If you are using this command to manage SSH keys for your project, please note the risks - (https://cloud.google.com/compute/docs/instances/adding-removing-ssh-keys#risks) + (https://docs.cloud.google.com/compute/docs/instances/access-overview#risks) of manual SSH key management as well as the required format for SSH key metadata, available at - https://cloud.google.com/compute/docs/instances/adding-removing-ssh-keys + https://docs.cloud.google.com/compute/docs/connect/add-ssh-keys FLAGS --metadata=KEY=VALUE,[KEY=VALUE,...] diff --git a/gcloud/beta/compute/rollout-plans/create b/gcloud/beta/compute/rollout-plans/create index 69057ab2f..75f7fad0c 100644 --- a/gcloud/beta/compute/rollout-plans/create +++ b/gcloud/beta/compute/rollout-plans/create @@ -61,8 +61,10 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud compute rollout-plans create $ gcloud alpha compute rollout-plans create diff --git a/gcloud/beta/compute/rollout-plans/delete b/gcloud/beta/compute/rollout-plans/delete index 6aecfbc84..cb890abc0 100644 --- a/gcloud/beta/compute/rollout-plans/delete +++ b/gcloud/beta/compute/rollout-plans/delete @@ -42,8 +42,10 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud compute rollout-plans delete $ gcloud alpha compute rollout-plans delete diff --git a/gcloud/beta/compute/rollout-plans/describe b/gcloud/beta/compute/rollout-plans/describe index 90aa5e4e6..e79795fb9 100644 --- a/gcloud/beta/compute/rollout-plans/describe +++ b/gcloud/beta/compute/rollout-plans/describe @@ -47,8 +47,10 @@ API REFERENCE can be found at: https://cloud.google.com/compute/ NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud compute rollout-plans describe $ gcloud alpha compute rollout-plans describe diff --git a/gcloud/beta/compute/rollout-plans/help b/gcloud/beta/compute/rollout-plans/help index d9b0e3db2..0f2075653 100644 --- a/gcloud/beta/compute/rollout-plans/help +++ b/gcloud/beta/compute/rollout-plans/help @@ -29,8 +29,10 @@ COMMANDS (BETA) List Google Compute Engine Rollout Plans. NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud compute rollout-plans $ gcloud alpha compute rollout-plans diff --git a/gcloud/beta/compute/rollout-plans/list b/gcloud/beta/compute/rollout-plans/list index 90e6b093f..7b4fafb9c 100644 --- a/gcloud/beta/compute/rollout-plans/list +++ b/gcloud/beta/compute/rollout-plans/list @@ -60,8 +60,10 @@ API REFERENCE can be found at: https://cloud.google.com/compute/ NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud compute rollout-plans list $ gcloud alpha compute rollout-plans list diff --git a/gcloud/beta/compute/rollouts/cancel b/gcloud/beta/compute/rollouts/cancel index 9d363b42d..ced860d2d 100644 --- a/gcloud/beta/compute/rollouts/cancel +++ b/gcloud/beta/compute/rollouts/cancel @@ -47,8 +47,10 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud compute rollouts cancel $ gcloud alpha compute rollouts cancel diff --git a/gcloud/beta/compute/rollouts/delete b/gcloud/beta/compute/rollouts/delete index 4139f612b..cc8983c99 100644 --- a/gcloud/beta/compute/rollouts/delete +++ b/gcloud/beta/compute/rollouts/delete @@ -41,8 +41,10 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud compute rollouts delete $ gcloud alpha compute rollouts delete diff --git a/gcloud/beta/compute/rollouts/describe b/gcloud/beta/compute/rollouts/describe index cceae0b23..f2b1ddbb7 100644 --- a/gcloud/beta/compute/rollouts/describe +++ b/gcloud/beta/compute/rollouts/describe @@ -45,8 +45,10 @@ API REFERENCE can be found at: https://cloud.google.com/compute/ NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud compute rollouts describe $ gcloud alpha compute rollouts describe diff --git a/gcloud/beta/compute/rollouts/help b/gcloud/beta/compute/rollouts/help index 1013294a5..d94472c73 100644 --- a/gcloud/beta/compute/rollouts/help +++ b/gcloud/beta/compute/rollouts/help @@ -28,8 +28,10 @@ COMMANDS (BETA) List Google Compute Engine Rollouts. NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud compute rollouts $ gcloud alpha compute rollouts diff --git a/gcloud/beta/compute/rollouts/list b/gcloud/beta/compute/rollouts/list index 23626323f..dbc7efefb 100644 --- a/gcloud/beta/compute/rollouts/list +++ b/gcloud/beta/compute/rollouts/list @@ -59,8 +59,10 @@ API REFERENCE can be found at: https://cloud.google.com/compute/ NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud compute rollouts list $ gcloud alpha compute rollouts list diff --git a/gcloud/beta/compute/snapshots/help b/gcloud/beta/compute/snapshots/help index fe0afd1a8..2470697e3 100644 --- a/gcloud/beta/compute/snapshots/help +++ b/gcloud/beta/compute/snapshots/help @@ -56,7 +56,8 @@ COMMANDS (BETA) Update a Compute Engine snapshot. update-kms-key - (BETA) Update the KMS key of a Compute Engine snapshot. + (BETA) Update the KMS key of a Compute Engine standard or archive + snapshot. NOTES This command is currently in beta and might change without notice. These diff --git a/gcloud/beta/compute/snapshots/update-kms-key b/gcloud/beta/compute/snapshots/update-kms-key index eb34e8400..896b1d01a 100644 --- a/gcloud/beta/compute/snapshots/update-kms-key +++ b/gcloud/beta/compute/snapshots/update-kms-key @@ -1,6 +1,6 @@ NAME gcloud beta compute snapshots update-kms-key - update the KMS key of a - Compute Engine snapshot + Compute Engine standard or archive snapshot SYNOPSIS gcloud beta compute snapshots update-kms-key SNAPSHOT_NAME @@ -10,8 +10,8 @@ SYNOPSIS [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) * gcloud beta compute snapshots update-kms-key updates the KMS key - of a Compute Engine persistent snapshot by rotating it to the primary + (BETA) gcloud beta compute snapshots update-kms-key updates the KMS key of + a Compute Engine standard or archive snapshot by rotating it to the primary version of the key or to the primary version of a new KMS key. EXAMPLES diff --git a/gcloud/beta/compute/zone-vm-extension-policies/create b/gcloud/beta/compute/zone-vm-extension-policies/create index 4a33bb41d..d49ad326f 100644 --- a/gcloud/beta/compute/zone-vm-extension-policies/create +++ b/gcloud/beta/compute/zone-vm-extension-policies/create @@ -131,8 +131,10 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud compute zone-vm-extension-policies create $ gcloud alpha compute zone-vm-extension-policies create diff --git a/gcloud/beta/compute/zone-vm-extension-policies/delete b/gcloud/beta/compute/zone-vm-extension-policies/delete index 8e8aa20aa..485a4a8c0 100644 --- a/gcloud/beta/compute/zone-vm-extension-policies/delete +++ b/gcloud/beta/compute/zone-vm-extension-policies/delete @@ -50,8 +50,10 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud compute zone-vm-extension-policies delete $ gcloud alpha compute zone-vm-extension-policies delete diff --git a/gcloud/beta/compute/zone-vm-extension-policies/describe b/gcloud/beta/compute/zone-vm-extension-policies/describe index 2c9e329f7..c2fed3242 100644 --- a/gcloud/beta/compute/zone-vm-extension-policies/describe +++ b/gcloud/beta/compute/zone-vm-extension-policies/describe @@ -50,8 +50,10 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud compute zone-vm-extension-policies describe $ gcloud alpha compute zone-vm-extension-policies describe diff --git a/gcloud/beta/compute/zone-vm-extension-policies/help b/gcloud/beta/compute/zone-vm-extension-policies/help index 947939218..2553680d4 100644 --- a/gcloud/beta/compute/zone-vm-extension-policies/help +++ b/gcloud/beta/compute/zone-vm-extension-policies/help @@ -33,8 +33,10 @@ COMMANDS (BETA) Update a Compute Engine zone VM extension policy. NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud compute zone-vm-extension-policies $ gcloud alpha compute zone-vm-extension-policies diff --git a/gcloud/beta/compute/zone-vm-extension-policies/list b/gcloud/beta/compute/zone-vm-extension-policies/list index fd612faa4..3c7cfb2c4 100644 --- a/gcloud/beta/compute/zone-vm-extension-policies/list +++ b/gcloud/beta/compute/zone-vm-extension-policies/list @@ -60,8 +60,10 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud compute zone-vm-extension-policies list $ gcloud alpha compute zone-vm-extension-policies list diff --git a/gcloud/beta/compute/zone-vm-extension-policies/update b/gcloud/beta/compute/zone-vm-extension-policies/update index 544dee63f..d5629107a 100644 --- a/gcloud/beta/compute/zone-vm-extension-policies/update +++ b/gcloud/beta/compute/zone-vm-extension-policies/update @@ -126,8 +126,10 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud compute zone-vm-extension-policies update $ gcloud alpha compute zone-vm-extension-policies update diff --git a/gcloud/beta/config/get b/gcloud/beta/config/get index e5675e6e2..768e78122 100644 --- a/gcloud/beta/config/get +++ b/gcloud/beta/config/get @@ -208,6 +208,10 @@ AVAILABLE PROPERTIES Overrides API endpoint for gcloud apphub command group. Defaults to https://apphub.googleapis.com/ + appoptimize + Overrides API endpoint for gcloud app-optimize command group. + Defaults to https://appoptimize.googleapis.com/ + artifactregistry Overrides API endpoint for gcloud artifacts command group. Defaults to https://artifactregistry.googleapis.com/ @@ -384,7 +388,6 @@ AVAILABLE PROPERTIES faultinjectiontesting Overrides API endpoint for gcloud fault-injection command group. - Defaults to https://faultinjectiontesting.googleapis.com/ faulttesting Overrides API endpoint for gcloud fault-testing command group. @@ -446,10 +449,6 @@ AVAILABLE PROPERTIES Overrides API endpoint for gcloud ml language command group. Defaults to https://language.googleapis.com/ - lifesciences - Overrides API endpoint for gcloud lifesciences command group. - Defaults to https://lifesciences.googleapis.com/ - logging Overrides API endpoint for gcloud logging command group. Defaults to https://logging.googleapis.com/ @@ -570,6 +569,10 @@ AVAILABLE PROPERTIES Overrides API endpoint for gcloud service-directory command group. Defaults to https://servicedirectory.googleapis.com/ + servicehealth + Overrides API endpoint for gcloud servicehealth command group. + Defaults to https://servicehealth.googleapis.com/ + servicemanagement Overrides API endpoint for gcloud endpoints command group. Defaults to https://servicemanagement.googleapis.com/ @@ -1049,12 +1052,6 @@ AVAILABLE PROPERTIES suggest If True, add command line suggestions based on history. - lifesciences - location - Default location to use when working with Cloud Life Sciences - resources. When a --location flag is required but not provided, the - command will fall back to this value. - looker region Default region to use when working with Cloud Looker resources. diff --git a/gcloud/beta/config/help b/gcloud/beta/config/help index 3352c0435..941717b34 100644 --- a/gcloud/beta/config/help +++ b/gcloud/beta/config/help @@ -240,6 +240,10 @@ AVAILABLE PROPERTIES Overrides API endpoint for gcloud apphub command group. Defaults to https://apphub.googleapis.com/ + appoptimize + Overrides API endpoint for gcloud app-optimize command group. + Defaults to https://appoptimize.googleapis.com/ + artifactregistry Overrides API endpoint for gcloud artifacts command group. Defaults to https://artifactregistry.googleapis.com/ @@ -416,7 +420,6 @@ AVAILABLE PROPERTIES faultinjectiontesting Overrides API endpoint for gcloud fault-injection command group. - Defaults to https://faultinjectiontesting.googleapis.com/ faulttesting Overrides API endpoint for gcloud fault-testing command group. @@ -478,10 +481,6 @@ AVAILABLE PROPERTIES Overrides API endpoint for gcloud ml language command group. Defaults to https://language.googleapis.com/ - lifesciences - Overrides API endpoint for gcloud lifesciences command group. - Defaults to https://lifesciences.googleapis.com/ - logging Overrides API endpoint for gcloud logging command group. Defaults to https://logging.googleapis.com/ @@ -602,6 +601,10 @@ AVAILABLE PROPERTIES Overrides API endpoint for gcloud service-directory command group. Defaults to https://servicedirectory.googleapis.com/ + servicehealth + Overrides API endpoint for gcloud servicehealth command group. + Defaults to https://servicehealth.googleapis.com/ + servicemanagement Overrides API endpoint for gcloud endpoints command group. Defaults to https://servicemanagement.googleapis.com/ @@ -1081,12 +1084,6 @@ AVAILABLE PROPERTIES suggest If True, add command line suggestions based on history. - lifesciences - location - Default location to use when working with Cloud Life Sciences - resources. When a --location flag is required but not provided, the - command will fall back to this value. - looker region Default region to use when working with Cloud Looker resources. diff --git a/gcloud/beta/config/list b/gcloud/beta/config/list index be105323a..3f719b7a9 100644 --- a/gcloud/beta/config/list +++ b/gcloud/beta/config/list @@ -252,6 +252,10 @@ AVAILABLE PROPERTIES Overrides API endpoint for gcloud apphub command group. Defaults to https://apphub.googleapis.com/ + appoptimize + Overrides API endpoint for gcloud app-optimize command group. + Defaults to https://appoptimize.googleapis.com/ + artifactregistry Overrides API endpoint for gcloud artifacts command group. Defaults to https://artifactregistry.googleapis.com/ @@ -428,7 +432,6 @@ AVAILABLE PROPERTIES faultinjectiontesting Overrides API endpoint for gcloud fault-injection command group. - Defaults to https://faultinjectiontesting.googleapis.com/ faulttesting Overrides API endpoint for gcloud fault-testing command group. @@ -490,10 +493,6 @@ AVAILABLE PROPERTIES Overrides API endpoint for gcloud ml language command group. Defaults to https://language.googleapis.com/ - lifesciences - Overrides API endpoint for gcloud lifesciences command group. - Defaults to https://lifesciences.googleapis.com/ - logging Overrides API endpoint for gcloud logging command group. Defaults to https://logging.googleapis.com/ @@ -614,6 +613,10 @@ AVAILABLE PROPERTIES Overrides API endpoint for gcloud service-directory command group. Defaults to https://servicedirectory.googleapis.com/ + servicehealth + Overrides API endpoint for gcloud servicehealth command group. + Defaults to https://servicehealth.googleapis.com/ + servicemanagement Overrides API endpoint for gcloud endpoints command group. Defaults to https://servicemanagement.googleapis.com/ @@ -1093,12 +1096,6 @@ AVAILABLE PROPERTIES suggest If True, add command line suggestions based on history. - lifesciences - location - Default location to use when working with Cloud Life Sciences - resources. When a --location flag is required but not provided, the - command will fall back to this value. - looker region Default region to use when working with Cloud Looker resources. diff --git a/gcloud/beta/config/set b/gcloud/beta/config/set index 33124e98b..89c91f6d4 100644 --- a/gcloud/beta/config/set +++ b/gcloud/beta/config/set @@ -255,6 +255,10 @@ AVAILABLE PROPERTIES Overrides API endpoint for gcloud apphub command group. Defaults to https://apphub.googleapis.com/ + appoptimize + Overrides API endpoint for gcloud app-optimize command group. + Defaults to https://appoptimize.googleapis.com/ + artifactregistry Overrides API endpoint for gcloud artifacts command group. Defaults to https://artifactregistry.googleapis.com/ @@ -431,7 +435,6 @@ AVAILABLE PROPERTIES faultinjectiontesting Overrides API endpoint for gcloud fault-injection command group. - Defaults to https://faultinjectiontesting.googleapis.com/ faulttesting Overrides API endpoint for gcloud fault-testing command group. @@ -493,10 +496,6 @@ AVAILABLE PROPERTIES Overrides API endpoint for gcloud ml language command group. Defaults to https://language.googleapis.com/ - lifesciences - Overrides API endpoint for gcloud lifesciences command group. - Defaults to https://lifesciences.googleapis.com/ - logging Overrides API endpoint for gcloud logging command group. Defaults to https://logging.googleapis.com/ @@ -617,6 +616,10 @@ AVAILABLE PROPERTIES Overrides API endpoint for gcloud service-directory command group. Defaults to https://servicedirectory.googleapis.com/ + servicehealth + Overrides API endpoint for gcloud servicehealth command group. + Defaults to https://servicehealth.googleapis.com/ + servicemanagement Overrides API endpoint for gcloud endpoints command group. Defaults to https://servicemanagement.googleapis.com/ @@ -1096,12 +1099,6 @@ AVAILABLE PROPERTIES suggest If True, add command line suggestions based on history. - lifesciences - location - Default location to use when working with Cloud Life Sciences - resources. When a --location flag is required but not provided, the - command will fall back to this value. - looker region Default region to use when working with Cloud Looker resources. diff --git a/gcloud/beta/config/unset b/gcloud/beta/config/unset index 6facd6f31..c577f9441 100644 --- a/gcloud/beta/config/unset +++ b/gcloud/beta/config/unset @@ -216,6 +216,10 @@ AVAILABLE PROPERTIES Overrides API endpoint for gcloud apphub command group. Defaults to https://apphub.googleapis.com/ + appoptimize + Overrides API endpoint for gcloud app-optimize command group. + Defaults to https://appoptimize.googleapis.com/ + artifactregistry Overrides API endpoint for gcloud artifacts command group. Defaults to https://artifactregistry.googleapis.com/ @@ -392,7 +396,6 @@ AVAILABLE PROPERTIES faultinjectiontesting Overrides API endpoint for gcloud fault-injection command group. - Defaults to https://faultinjectiontesting.googleapis.com/ faulttesting Overrides API endpoint for gcloud fault-testing command group. @@ -454,10 +457,6 @@ AVAILABLE PROPERTIES Overrides API endpoint for gcloud ml language command group. Defaults to https://language.googleapis.com/ - lifesciences - Overrides API endpoint for gcloud lifesciences command group. - Defaults to https://lifesciences.googleapis.com/ - logging Overrides API endpoint for gcloud logging command group. Defaults to https://logging.googleapis.com/ @@ -578,6 +577,10 @@ AVAILABLE PROPERTIES Overrides API endpoint for gcloud service-directory command group. Defaults to https://servicedirectory.googleapis.com/ + servicehealth + Overrides API endpoint for gcloud servicehealth command group. + Defaults to https://servicehealth.googleapis.com/ + servicemanagement Overrides API endpoint for gcloud endpoints command group. Defaults to https://servicemanagement.googleapis.com/ @@ -1057,12 +1060,6 @@ AVAILABLE PROPERTIES suggest If True, add command line suggestions based on history. - lifesciences - location - Default location to use when working with Cloud Life Sciences - resources. When a --location flag is required but not provided, the - command will fall back to this value. - looker region Default region to use when working with Cloud Looker resources. diff --git a/gcloud/beta/container/clusters/create b/gcloud/beta/container/clusters/create index b4f18c737..7815f4987 100644 --- a/gcloud/beta/container/clusters/create +++ b/gcloud/beta/container/clusters/create @@ -27,6 +27,7 @@ SYNOPSIS [--cluster-version=CLUSTER_VERSION] [--confidential-node-type=CONFIDENTIAL_NODE_TYPE] [--containerd-config-from-file=PATH_TO_FILE] + [--control-plane-egress=CONTROL_PLANE_EGRESS] [--create-subnetwork=[KEY=VALUE,...]] [--data-cache-count=DATA_CACHE_COUNT] [--database-encryption-key=DATABASE_ENCRYPTION_KEY] @@ -81,8 +82,10 @@ SYNOPSIS [--min-cpu-platform=PLATFORM] [--monitoring=[COMPONENT,...]] [--network=NETWORK] [--network-performance-configs=[PROPERTY1=VALUE1,...]] - [--node-labels=[NODE_LABEL,...]] [--node-taints=[NODE_TAINT,...]] - [--node-version=NODE_VERSION] + [--node-architecture-taint-behavior=NODE_ARCHITECTURE_TAINT_BEHAVIOR] + [--node-labels=[NODE_LABEL,...]] + [--node-pool-upgrade-concurrency-config=[max-count=MAX-COUNT]] + [--node-taints=[NODE_TAINT,...]] [--node-version=NODE_VERSION] [--notification-config=[pubsub=ENABLED|DISABLED, pubsub-topic=TOPIC,...]] [--num-nodes=NUM_NODES; default=3] [--patch-update=[PATCH_UPDATE]] @@ -497,6 +500,23 @@ FLAGS Use a full or relative path to a local file containing the value of containerd_config. + --control-plane-egress=CONTROL_PLANE_EGRESS + Configures the egress policy for the GKE control plane to control + outbound traffic from the kube-apiserver. CONTROL_PLANE_EGRESS must be + one of: + + NONE + (Recommended) Provides maximum security. This mode removes the + control plane's public IP address and blocks all outbound traffic + from the kube-apiserver by default, preventing unexpected data + exfiltration. Webhooks that use clientConfig.url will be disabled. + Essential GKE-managed services are still permitted to function via + an internal allowlist. + VIA_CONTROL_PLANE + (Default) Maintains backward compatibility. The control plane + retains its public IP address and allows egress traffic from the + kube-apiserver. + --create-subnetwork=[KEY=VALUE,...] Create a new subnetwork for the cluster. The name and range of the subnetwork can be customized via optional 'name' and 'range' key-value @@ -1233,6 +1253,26 @@ FLAGS https://cloud.google.com/compute/docs/networking/configure-vm-with-high-bandwidth-configuration for more information. + --node-architecture-taint-behavior=NODE_ARCHITECTURE_TAINT_BEHAVIOR + Control how architecture taint should be applied to nodes in default + node pool(s) in new cluster. + + Supported values: + * unspecified: Default behavior, currently the same as `arm`. + * arm: kubernetes.io/arch=arm:NoSchedule taint will be added for ARM nodes. + * none: No architecture taint will be applied. + + Examples: + + $ gcloud beta container clusters create example-cluster \ + --node-architecture-taint-behavior=none + + To read more about node-taints, see + https://cloud.google.com/kubernetes-engine/docs/node-taints. + + NODE_ARCHITECTURE_TAINT_BEHAVIOR must be one of: unspecified, arm, + none. + --node-labels=[NODE_LABEL,...] Applies the given Kubernetes labels on all nodes in the new node pool. @@ -1254,6 +1294,18 @@ FLAGS different from Google Kubernetes Engine labels that are used for the purpose of tracking billing and usage information. + --node-pool-upgrade-concurrency-config=[max-count=MAX-COUNT] + Configure the concurrency settings for node pool auto upgrades. + + Examples: + + $ gcloud beta container clusters create example-cluster \ + --node-pool-upgrade-concurrency-config=max-count=10 + + max-count + The maximum number of node pools to upgrade concurrently. The + maximum allowed value is 100. + --node-taints=[NODE_TAINT,...] Applies the given kubernetes taints on all nodes in default node pool(s) in new cluster, which can be used with tolerations for pod @@ -1795,6 +1847,12 @@ FLAGS 'veno', 'westwood', 'yeah'. + net.ipv4.neigh.default.gc_thresh1 Must be between + [0, 262144] + net.ipv4.neigh.default.gc_thresh2 Must be between + [512, 524288] + net.ipv4.neigh.default.gc_thresh3 Must be between + [1024, 1048576] net.netfilter.nf_conntrack_max Must be between [65536, 4194304] net.netfilter.nf_conntrack_buckets Must be between @@ -1810,6 +1868,10 @@ FLAGS net.netfilter.nf_conntrack_tcp_timeout_established Must be between [600, 86400] net.netfilter.nf_conntrack_acct Must be {0, 1} + kernel.keys.maxkeys Must be between + [200, 1048576] + kernel.keys.maxbytes Must be between + [20000, 2097152] kernel.shmmni Must be between [4096, 32768] kernel.shmmax Must be between @@ -2405,13 +2467,14 @@ FLAGS --max-cpu=MAX_CPU Maximum number of cores in the cluster. - Maximum number of cores to which the cluster can scale. + Maximum number of cores to which the cluster can scale. Required to + be set when --enable-autoprovisioning is used. --max-memory=MAX_MEMORY Maximum memory in the cluster. Maximum number of gigabytes of memory to which the cluster can - scale. + scale. Required to be set when --enable-autoprovisioning is used. --min-cpu=MIN_CPU Minimum number of cores in the cluster. diff --git a/gcloud/beta/container/clusters/create-auto b/gcloud/beta/container/clusters/create-auto index c9998de65..353cdfc9e 100644 --- a/gcloud/beta/container/clusters/create-auto +++ b/gcloud/beta/container/clusters/create-auto @@ -15,7 +15,9 @@ SYNOPSIS [--cluster-ipv4-cidr=CLUSTER_IPV4_CIDR] [--cluster-secondary-range-name=NAME] [--cluster-version=CLUSTER_VERSION] + [--confidential-node-type=CONFIDENTIAL_NODE_TYPE] [--containerd-config-from-file=PATH_TO_FILE] + [--control-plane-egress=CONTROL_PLANE_EGRESS] [--create-subnetwork=[KEY=VALUE,...]] [--database-encryption-key=DATABASE_ENCRYPTION_KEY] [--disable-l4-lb-firewall-reconciliation] [--disable-multi-nic-lustre] @@ -36,11 +38,13 @@ SYNOPSIS [--hpa-profile=HPA_PROFILE] [--labels=[KEY=VALUE,...]] [--logging=[COMPONENT,...]] [--managed-otel-scope=MANAGED_OTEL_SCOPE] [--membership-type=MEMBERSHIP_TYPE] [--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] + [--network=NETWORK] + [--node-pool-upgrade-concurrency-config=[max-count=MAX-COUNT]] + [--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] @@ -280,6 +284,12 @@ FLAGS $ gcloud container get-server-config + --confidential-node-type=CONFIDENTIAL_NODE_TYPE + Enable confidential nodes for the cluster. Enabling Confidential Nodes + will create nodes using Confidential VM + https://docs.cloud.google.com/compute/docs/about-confidential-vm. + CONFIDENTIAL_NODE_TYPE must be one of: sev, sev_snp, tdx. + --containerd-config-from-file=PATH_TO_FILE Path of the YAML file that contains containerd configuration entries like configuring access to private image registries. @@ -294,6 +304,23 @@ FLAGS Use a full or relative path to a local file containing the value of containerd_config. + --control-plane-egress=CONTROL_PLANE_EGRESS + Configures the egress policy for the GKE control plane to control + outbound traffic from the kube-apiserver. CONTROL_PLANE_EGRESS must be + one of: + + NONE + (Recommended) Provides maximum security. This mode removes the + control plane's public IP address and blocks all outbound traffic + from the kube-apiserver by default, preventing unexpected data + exfiltration. Webhooks that use clientConfig.url will be disabled. + Essential GKE-managed services are still permitted to function via + an internal allowlist. + VIA_CONTROL_PLANE + (Default) Maintains backward compatibility. The control plane + retains its public IP address and allows egress traffic from the + kube-apiserver. + --create-subnetwork=[KEY=VALUE,...] Create a new subnetwork for the cluster. The name and range of the subnetwork can be customized via optional 'name' and 'range' key-value @@ -554,6 +581,18 @@ FLAGS Kubernetes Engine will use this network when creating routes and firewalls for the clusters. Defaults to the 'default' network. + --node-pool-upgrade-concurrency-config=[max-count=MAX-COUNT] + Configure the concurrency settings for node pool auto upgrades. + + Examples: + + $ gcloud beta container clusters create-auto example-cluster \ + --node-pool-upgrade-concurrency-config=max-count=10 + + max-count + The maximum number of node pools to upgrade concurrently. The + maximum allowed value is 100. + --private-endpoint-subnetwork=NAME Sets the subnetwork GKE uses to provision the control plane's private endpoint. diff --git a/gcloud/beta/container/clusters/update b/gcloud/beta/container/clusters/update index 04ab1d2e9..bd5acf204 100644 --- a/gcloud/beta/container/clusters/update +++ b/gcloud/beta/container/clusters/update @@ -15,6 +15,7 @@ SYNOPSIS | --autoscaling-profile=AUTOSCALING_PROFILE | --complete-credential-rotation | --complete-ip-rotation | --containerd-config-from-file=PATH_TO_FILE + | --control-plane-egress=CONTROL_PLANE_EGRESS | --database-encryption-key=DATABASE_ENCRYPTION_KEY | --disable-database-encryption | --disable-default-snat | --disable-multi-nic-lustre | --disable-workload-identity @@ -42,6 +43,7 @@ SYNOPSIS | --in-transit-encryption=IN_TRANSIT_ENCRYPTION | --logging-variant=LOGGING_VARIANT | --maintenance-window=START_TIME | --network-performance-configs=[PROPERTY1=VALUE1,...] + | --node-pool-upgrade-concurrency-config=[max-count=MAX-COUNT] | --notification-config=[pubsub=ENABLED|DISABLED, pubsub-topic=TOPIC,...] | --patch-update=[PATCH_UPDATE] | --private-ipv6-google-access-type=PRIVATE_IPV6_GOOGLE_ACCESS_TYPE @@ -351,6 +353,23 @@ REQUIRED FLAGS Use a full or relative path to a local file containing the value of containerd_config. + --control-plane-egress=CONTROL_PLANE_EGRESS + Configures the egress policy for the GKE control plane to control + outbound traffic from the kube-apiserver. CONTROL_PLANE_EGRESS must + be one of: + + NONE + (Recommended) Provides maximum security. This mode removes the + control plane's public IP address and blocks all outbound traffic + from the kube-apiserver by default, preventing unexpected data + exfiltration. Webhooks that use clientConfig.url will be + disabled. Essential GKE-managed services are still permitted to + function via an internal allowlist. + VIA_CONTROL_PLANE + (Default) Maintains backward compatibility. The control plane + retains its public IP address and allows egress traffic from the + kube-apiserver. + --database-encryption-key=DATABASE_ENCRYPTION_KEY Enable Database Encryption. @@ -695,6 +714,18 @@ REQUIRED FLAGS https://cloud.google.com/compute/docs/networking/configure-vm-with-high-bandwidth-configuration for more information. + --node-pool-upgrade-concurrency-config=[max-count=MAX-COUNT] + Configure the concurrency settings for node pool auto upgrades. + + Examples: + + $ gcloud beta container clusters update example-cluster \ + --node-pool-upgrade-concurrency-config=max-count=10 + + max-count + The maximum number of node pools to upgrade concurrently. The + maximum allowed value is 100. + --notification-config=[pubsub=ENABLED|DISABLED,pubsub-topic=TOPIC,...] The notification configuration of the cluster. GKE supports publishing cluster upgrade notifications to any Pub/Sub topic you @@ -1665,12 +1696,14 @@ REQUIRED FLAGS Maximum number of cores in the cluster. Maximum number of cores to which the cluster can scale. + Required to be set when --enable-autoprovisioning is used. --max-memory=MAX_MEMORY Maximum memory in the cluster. Maximum number of gigabytes of memory to which the cluster can - scale. + scale. Required to be set when --enable-autoprovisioning is + used. --min-cpu=MIN_CPU Minimum number of cores in the cluster. diff --git a/gcloud/beta/container/fleet/memberships/get-credentials b/gcloud/beta/container/fleet/memberships/get-credentials index 3b0b87b02..b48ea9119 100644 --- a/gcloud/beta/container/fleet/memberships/get-credentials +++ b/gcloud/beta/container/fleet/memberships/get-credentials @@ -20,6 +20,13 @@ DESCRIPTION Upon success, this command will switch the current context to the target cluster if other contexts are already present in the kubeconfig file. + To force the use of Application Default Credentials (ADC) for + authentication, you can set the + container/use_application_default_credentials property to true: + + $ gcloud config set container/use_application_default_credentials \ + true + EXAMPLES Get the Gateway kubeconfig for a globally registered cluster: diff --git a/gcloud/beta/container/hub/memberships/get-credentials b/gcloud/beta/container/hub/memberships/get-credentials index 991574925..9e4625450 100644 --- a/gcloud/beta/container/hub/memberships/get-credentials +++ b/gcloud/beta/container/hub/memberships/get-credentials @@ -20,6 +20,13 @@ DESCRIPTION Upon success, this command will switch the current context to the target cluster if other contexts are already present in the kubeconfig file. + To force the use of Application Default Credentials (ADC) for + authentication, you can set the + container/use_application_default_credentials property to true: + + $ gcloud config set container/use_application_default_credentials \ + true + EXAMPLES Get the Gateway kubeconfig for a globally registered cluster: diff --git a/gcloud/beta/container/node-pools/create b/gcloud/beta/container/node-pools/create index 28fadcdd7..c0c63878d 100644 --- a/gcloud/beta/container/node-pools/create +++ b/gcloud/beta/container/node-pools/create @@ -44,6 +44,7 @@ SYNOPSIS [--metadata-from-file=KEY=LOCAL_FILE_PATH,[...]] [--min-cpu-platform=PLATFORM] [--network-performance-configs=[PROPERTY=VALUE,...]] + [--node-architecture-taint-behavior=NODE_ARCHITECTURE_TAINT_BEHAVIOR] [--node-group=NODE_GROUP] [--node-labels=[NODE_LABEL,...]] [--node-locations=ZONE,[ZONE,...]] [--node-pool-soak-duration=NODE_POOL_SOAK_DURATION] @@ -63,7 +64,7 @@ SYNOPSIS [--standard-rollout-policy=[batch-node-count=BATCH_NODE_COUNT, batch-percent=BATCH_NODE_PERCENTAGE, batch-soak-duration=BATCH_SOAK_DURATION,...]] - [--storage-pools=STORAGE_POOL,[...]] + [--storage-pools=STORAGE_POOL,[...]] [--subnetwork=SUBNETWORK] [--system-config-from-file=PATH_TO_FILE] [--tags=TAG,[TAG,...]] [--threads-per-core=THREADS_PER_CORE] [--tpu-topology=TPU_TOPOLOGY] [--windows-os-version=WINDOWS_OS_VERSION] @@ -559,6 +560,27 @@ FLAGS external IP destinations. The following tier values are allowed: [TIER_UNSPECIFIED,TIER_1] + --node-architecture-taint-behavior=NODE_ARCHITECTURE_TAINT_BEHAVIOR + Control how architecture taint should be applied to nodes in a new node + pool. + + Supported values: + * unspecified: Default behavior, currently the same as `arm`. + * arm: kubernetes.io/arch=arm:NoSchedule taint will be added for ARM nodes. + * none: No architecture taint will be applied. + + Examples: + + $ gcloud beta container node-pools create node-pool-1 \ + --cluster=example-cluster \ + --node-architecture-taint-behavior=none + + To read more about node-taints, see + https://cloud.google.com/kubernetes-engine/docs/node-taints. + + NODE_ARCHITECTURE_TAINT_BEHAVIOR must be one of: unspecified, arm, + none. + --node-group=NODE_GROUP Assign instances of this pool to run on the specified Google Compute Engine node group. This is useful for running workloads on sole tenant @@ -831,6 +853,14 @@ FLAGS STORAGE_POOL must be in the format projects/project/zones/zone/storagePools/storagePool + --subnetwork=SUBNETWORK + The subnetwork to use for nodes. This subnetwork must exist in the + cluster's list of additional subnetworks. + + If not specified, the node pool's node IP addresses are allocated from + the least utilized subnet and its secondary range. See details at + https://cloud.google.com/kubernetes-engine/docs/how-to/multi-subnet-clusters#create-node-pool + --system-config-from-file=PATH_TO_FILE Path of the YAML/JSON file that contains the node configuration, including Linux kernel parameters (sysctls) and kubelet configs. @@ -1089,6 +1119,12 @@ FLAGS 'veno', 'westwood', 'yeah'. + net.ipv4.neigh.default.gc_thresh1 Must be between + [0, 262144] + net.ipv4.neigh.default.gc_thresh2 Must be between + [512, 524288] + net.ipv4.neigh.default.gc_thresh3 Must be between + [1024, 1048576] net.netfilter.nf_conntrack_max Must be between [65536, 4194304] net.netfilter.nf_conntrack_buckets Must be between @@ -1104,6 +1140,10 @@ FLAGS net.netfilter.nf_conntrack_tcp_timeout_established Must be between [600, 86400] net.netfilter.nf_conntrack_acct Must be {0, 1} + kernel.keys.maxkeys Must be between + [200, 1048576] + kernel.keys.maxbytes Must be between + [20000, 2097152] kernel.shmmni Must be between [4096, 32768] kernel.shmmax Must be between diff --git a/gcloud/beta/container/node-pools/update b/gcloud/beta/container/node-pools/update index 126231b23..44ed26d83 100644 --- a/gcloud/beta/container/node-pools/update +++ b/gcloud/beta/container/node-pools/update @@ -20,6 +20,7 @@ SYNOPSIS | --logging-variant=LOGGING_VARIANT | --max-run-duration=MAX_RUN_DURATION | --network-performance-configs=[PROPERTY=VALUE,...] + | --node-architecture-taint-behavior=NODE_ARCHITECTURE_TAINT_BEHAVIOR | --node-labels=[NODE_LABEL,...] | --node-locations=ZONE,[ZONE,...] | --node-taints=[NODE_TAINT,...] | --resource-manager-tags=[KEY=VALUE,...] @@ -237,6 +238,27 @@ REQUIRED FLAGS external IP destinations. The following tier values are allowed: [TIER_UNSPECIFIED,TIER_1] + --node-architecture-taint-behavior=NODE_ARCHITECTURE_TAINT_BEHAVIOR + Control how architecture taint should be applied to nodes in an + existing node pool. + + Supported values: + * unspecified: Default behavior, currently the same as `arm`. + * arm: kubernetes.io/arch=arm:NoSchedule taint will be added for ARM nodes. + * none: No architecture taint will be applied. + + Examples: + + $ gcloud beta container node-pools update node-pool-1 \ + --cluster=example-cluster \ + --node-architecture-taint-behavior=none + + To read more about node-taints, see + https://cloud.google.com/kubernetes-engine/docs/node-taints. + + NODE_ARCHITECTURE_TAINT_BEHAVIOR must be one of: unspecified, arm, + none. + --node-labels=[NODE_LABEL,...] Replaces all the user specified Kubernetes labels on all nodes in an existing node pool with the given labels. @@ -595,6 +617,12 @@ REQUIRED FLAGS 'veno', 'westwood', 'yeah'. + net.ipv4.neigh.default.gc_thresh1 Must be between + [0, 262144] + net.ipv4.neigh.default.gc_thresh2 Must be between + [512, 524288] + net.ipv4.neigh.default.gc_thresh3 Must be between + [1024, 1048576] net.netfilter.nf_conntrack_max Must be between [65536, 4194304] net.netfilter.nf_conntrack_buckets Must be between @@ -612,6 +640,10 @@ REQUIRED FLAGS net.netfilter.nf_conntrack_tcp_timeout_established Must be between [600, 86400] net.netfilter.nf_conntrack_acct Must be {0, 1} + kernel.keys.maxkeys Must be between + [200, 1048576] + kernel.keys.maxbytes Must be between + [20000, 2097152] kernel.shmmni Must be between [4096, 32768] kernel.shmmax Must be between diff --git a/gcloud/beta/dataflow/flex-template/run b/gcloud/beta/dataflow/flex-template/run index d3d975aba..27df65385 100644 --- a/gcloud/beta/dataflow/flex-template/run +++ b/gcloud/beta/dataflow/flex-template/run @@ -10,6 +10,7 @@ SYNOPSIS [--dataflow-kms-key=DATAFLOW_KMS_KEY] [--disable-public-ips] [--enable-streaming-engine] [--flexrs-goal=FLEXRS_GOAL] [--launcher-machine-type=LAUNCHER_MACHINE_TYPE] + [--launcher-vm-timeout-secs=LAUNCHER_VM_TIMEOUT_SECS] [--max-workers=MAX_WORKERS] [--network=NETWORK] [--num-workers=NUM_WORKERS] [--parameters=[PARAMETERS,...]] [--region=REGION_ID] [--service-account-email=SERVICE_ACCOUNT_EMAIL] @@ -76,6 +77,10 @@ OPTIONAL FLAGS The machine type to use for launching the job. If not set, Dataflow will select a default machine type. + --launcher-vm-timeout-secs=LAUNCHER_VM_TIMEOUT_SECS + The timeout in seconds for the launcher VM. If not set, Dataflow uses a + default timeout. + --max-workers=MAX_WORKERS Maximum number of workers to run. diff --git a/gcloud/beta/dataproc/clusters/create b/gcloud/beta/dataproc/clusters/create index f96e9f533..0916ca215 100644 --- a/gcloud/beta/dataproc/clusters/create +++ b/gcloud/beta/dataproc/clusters/create @@ -13,10 +13,12 @@ SYNOPSIS [--driver-pool-machine-type=DRIVER_POOL_MACHINE_TYPE] [--driver-pool-min-cpu-platform=PLATFORM] [--driver-pool-size=DRIVER_POOL_SIZE] [--enable-component-gateway] + [--engine=ENGINE] [--initialization-action-timeout=TIMEOUT; default="10m"] [--initialization-actions=CLOUD_STORAGE_URI,[...]] [--labels=[KEY=VALUE,...]] [--master-accelerator=[type=TYPE,[count=COUNT],...]] + [--master-attached-disks=MASTER_ATTACHED_DISKS] [--master-boot-disk-provisioned-iops=MASTER_BOOT_DISK_PROVISIONED_IOPS] [--master-boot-disk-provisioned-throughput=MASTER_BOOT_DISK_PROVISIONED_THROUGHPUT] [--master-boot-disk-size=MASTER_BOOT_DISK_SIZE] @@ -35,6 +37,7 @@ SYNOPSIS [--private-ipv6-google-access-type=PRIVATE_IPV6_GOOGLE_ACCESS_TYPE] [--properties=[PREFIX:PROPERTY=VALUE,...]] [--secondary-worker-accelerator=[type=TYPE,[count=COUNT],...]] + [--secondary-worker-attached-disks=SECONDARY_WORKER_ATTACHED_DISKS] [--secondary-worker-boot-disk-size=SECONDARY_WORKER_BOOT_DISK_SIZE] [--secondary-worker-boot-disk-type=SECONDARY_WORKER_BOOT_DISK_TYPE] [--secondary-worker-local-ssd-interface=SECONDARY_WORKER_LOCAL_SSD_INTERFACE] @@ -44,8 +47,9 @@ SYNOPSIS [--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] [--tier=TIER] + [--temp-bucket=TEMP_BUCKET] [--worker-accelerator=[type=TYPE,[count=COUNT],...]] + [--worker-attached-disks=WORKER_ATTACHED_DISKS] [--worker-boot-disk-provisioned-iops=WORKER_BOOT_DISK_PROVISIONED_IOPS] [--worker-boot-disk-provisioned-throughput=WORKER_BOOT_DISK_PROVISIONED_THROUGHPUT] [--worker-boot-disk-size=WORKER_BOOT_DISK_SIZE] @@ -206,6 +210,9 @@ FLAGS Enable access to the web UIs of selected components on the cluster through the component gateway. + --engine=ENGINE + Cluster engine. ENGINE must be one of: default, lightning. + --initialization-action-timeout=TIMEOUT; default="10m" The maximum duration of each initialization action. See $ gcloud topic datetimes for information on duration formats. @@ -234,6 +241,42 @@ FLAGS The number of accelerators to attach to each instance. The default value is 1. + --master-attached-disks=MASTER_ATTACHED_DISKS + A list of disk configurations to attach to each instance in this group. + Disk configurations are separated by semicolons. Each disk + configuration is a comma-separated list of the following parameters. + + type - required + The type of disk to attach to the instances + (https://cloud.google.com/compute/docs/disks/hyperdisks). + Allowed disk types are: hyperdisk-balanced, hyperdisk-extreme, + hyperdisk-ml, hyperdisk-throughput. + + size - optional + The size of the disk. The value must be a whole number followed by + a size unit GB for gigabyte, or TB for terabyte. For example, + 10GB produces a 10 gigabyte disk. + + iops - optional + Indicates the IOPS + (https://cloud.google.com/compute/docs/disks/hyperdisks#iops) to + provision for the attached hyperdisk. This parameter sets the limit + for disk I/O operations per second. + + throughput - optional + Indicates the throughput + (https://cloud.google.com/compute/docs/disks/hyperdisks#throughput) + to provision for the attached hyperdisk. This parameter sets the + limit for throughput in MiB per second. + + Example: + type='hyperdisk-balanced,iops=5000,throughput=200,size=100G;type=hyperdisk-throughput,size=9000G' + + Attaches two disks to the instances. The first disk is a + hyperdisk-balanced disk with 5000 IOPS, 200 MiB/s throughput, and 100 + GiB size. The second disk is a hyperdisk-throughput disk with 9000 + GiB size. + --master-boot-disk-provisioned-iops=MASTER_BOOT_DISK_PROVISIONED_IOPS Indicates the IOPS (https://cloud.google.com/compute/docs/disks/hyperdisks#iops) to @@ -372,6 +415,42 @@ FLAGS The number of accelerators to attach to each instance. The default value is 1. + --secondary-worker-attached-disks=SECONDARY_WORKER_ATTACHED_DISKS + A list of disk configurations to attach to each instance in this group. + Disk configurations are separated by semicolons. Each disk + configuration is a comma-separated list of the following parameters. + + type - required + The type of disk to attach to the instances + (https://cloud.google.com/compute/docs/disks/hyperdisks). + Allowed disk types are: hyperdisk-balanced, hyperdisk-extreme, + hyperdisk-ml, hyperdisk-throughput. + + size - optional + The size of the disk. The value must be a whole number followed by + a size unit GB for gigabyte, or TB for terabyte. For example, + 10GB produces a 10 gigabyte disk. + + iops - optional + Indicates the IOPS + (https://cloud.google.com/compute/docs/disks/hyperdisks#iops) to + provision for the attached hyperdisk. This parameter sets the limit + for disk I/O operations per second. + + throughput - optional + Indicates the throughput + (https://cloud.google.com/compute/docs/disks/hyperdisks#throughput) + to provision for the attached hyperdisk. This parameter sets the + limit for throughput in MiB per second. + + Example: + type='hyperdisk-balanced,iops=5000,throughput=200,size=100G;type=hyperdisk-throughput,size=9000G' + + Attaches two disks to the instances. The first disk is a + hyperdisk-balanced disk with 5000 IOPS, 200 MiB/s throughput, and 100 + GiB size. The second disk is a hyperdisk-throughput disk with 9000 + GiB size. + --secondary-worker-boot-disk-size=SECONDARY_WORKER_BOOT_DISK_SIZE The size of the boot disk. The value must be a whole number followed by a size unit of KB for kilobyte, MB for megabyte, GB for gigabyte, or TB @@ -434,9 +513,6 @@ FLAGS The Google Cloud Storage bucket to use by default to store ephemeral cluster and jobs data, such as Spark and MapReduce history files. - --tier=TIER - Cluster tier. TIER must be one of: premium, standard. - --worker-accelerator=[type=TYPE,[count=COUNT],...] Attaches accelerators, such as GPUs, to the worker instance(s). @@ -449,6 +525,42 @@ FLAGS The number of accelerators to attach to each instance. The default value is 1. + --worker-attached-disks=WORKER_ATTACHED_DISKS + A list of disk configurations to attach to each instance in this group. + Disk configurations are separated by semicolons. Each disk + configuration is a comma-separated list of the following parameters. + + type - required + The type of disk to attach to the instances + (https://cloud.google.com/compute/docs/disks/hyperdisks). + Allowed disk types are: hyperdisk-balanced, hyperdisk-extreme, + hyperdisk-ml, hyperdisk-throughput. + + size - optional + The size of the disk. The value must be a whole number followed by + a size unit GB for gigabyte, or TB for terabyte. For example, + 10GB produces a 10 gigabyte disk. + + iops - optional + Indicates the IOPS + (https://cloud.google.com/compute/docs/disks/hyperdisks#iops) to + provision for the attached hyperdisk. This parameter sets the limit + for disk I/O operations per second. + + throughput - optional + Indicates the throughput + (https://cloud.google.com/compute/docs/disks/hyperdisks#throughput) + to provision for the attached hyperdisk. This parameter sets the + limit for throughput in MiB per second. + + Example: + type='hyperdisk-balanced,iops=5000,throughput=200,size=100G;type=hyperdisk-throughput,size=9000G' + + Attaches two disks to the instances. The first disk is a + hyperdisk-balanced disk with 5000 IOPS, 200 MiB/s throughput, and 100 + GiB size. The second disk is a hyperdisk-throughput disk with 9000 + GiB size. + --worker-boot-disk-provisioned-iops=WORKER_BOOT_DISK_PROVISIONED_IOPS Indicates the IOPS (https://cloud.google.com/compute/docs/disks/hyperdisks#iops) to diff --git a/gcloud/beta/dataproc/workflow-templates/set-managed-cluster b/gcloud/beta/dataproc/workflow-templates/set-managed-cluster index 9e47be0f4..a92007e23 100644 --- a/gcloud/beta/dataproc/workflow-templates/set-managed-cluster +++ b/gcloud/beta/dataproc/workflow-templates/set-managed-cluster @@ -6,11 +6,12 @@ SYNOPSIS gcloud beta dataproc workflow-templates set-managed-cluster (TEMPLATE : --region=REGION) [--autoscaling-policy=AUTOSCALING_POLICY] [--bucket=BUCKET] [--cluster-name=CLUSTER_NAME] [--cluster-type=TYPE] - [--enable-component-gateway] + [--enable-component-gateway] [--engine=ENGINE] [--initialization-action-timeout=TIMEOUT; default="10m"] [--initialization-actions=CLOUD_STORAGE_URI,[...]] [--labels=[KEY=VALUE,...]] [--master-accelerator=[type=TYPE,[count=COUNT],...]] + [--master-attached-disks=MASTER_ATTACHED_DISKS] [--master-boot-disk-provisioned-iops=MASTER_BOOT_DISK_PROVISIONED_IOPS] [--master-boot-disk-provisioned-throughput=MASTER_BOOT_DISK_PROVISIONED_THROUGHPUT] [--master-boot-disk-size=MASTER_BOOT_DISK_SIZE] @@ -28,6 +29,7 @@ SYNOPSIS [--private-ipv6-google-access-type=PRIVATE_IPV6_GOOGLE_ACCESS_TYPE] [--properties=[PREFIX:PROPERTY=VALUE,...]] [--secondary-worker-accelerator=[type=TYPE,[count=COUNT],...]] + [--secondary-worker-attached-disks=SECONDARY_WORKER_ATTACHED_DISKS] [--secondary-worker-boot-disk-size=SECONDARY_WORKER_BOOT_DISK_SIZE] [--secondary-worker-boot-disk-type=SECONDARY_WORKER_BOOT_DISK_TYPE] [--secondary-worker-local-ssd-interface=SECONDARY_WORKER_LOCAL_SSD_INTERFACE] @@ -36,8 +38,9 @@ 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] [--temp-bucket=TEMP_BUCKET] [--tier=TIER] + [--shielded-vtpm] [--temp-bucket=TEMP_BUCKET] [--worker-accelerator=[type=TYPE,[count=COUNT],...]] + [--worker-attached-disks=WORKER_ATTACHED_DISKS] [--worker-boot-disk-provisioned-iops=WORKER_BOOT_DISK_PROVISIONED_IOPS] [--worker-boot-disk-provisioned-throughput=WORKER_BOOT_DISK_PROVISIONED_THROUGHPUT] [--worker-boot-disk-size=WORKER_BOOT_DISK_SIZE] @@ -137,6 +140,9 @@ FLAGS Enable access to the web UIs of selected components on the cluster through the component gateway. + --engine=ENGINE + Cluster engine. ENGINE must be one of: default, lightning. + --initialization-action-timeout=TIMEOUT; default="10m" The maximum duration of each initialization action. See $ gcloud topic datetimes for information on duration formats. @@ -165,6 +171,42 @@ FLAGS The number of accelerators to attach to each instance. The default value is 1. + --master-attached-disks=MASTER_ATTACHED_DISKS + A list of disk configurations to attach to each instance in this group. + Disk configurations are separated by semicolons. Each disk + configuration is a comma-separated list of the following parameters. + + type - required + The type of disk to attach to the instances + (https://cloud.google.com/compute/docs/disks/hyperdisks). + Allowed disk types are: hyperdisk-balanced, hyperdisk-extreme, + hyperdisk-ml, hyperdisk-throughput. + + size - optional + The size of the disk. The value must be a whole number followed by + a size unit GB for gigabyte, or TB for terabyte. For example, + 10GB produces a 10 gigabyte disk. + + iops - optional + Indicates the IOPS + (https://cloud.google.com/compute/docs/disks/hyperdisks#iops) to + provision for the attached hyperdisk. This parameter sets the limit + for disk I/O operations per second. + + throughput - optional + Indicates the throughput + (https://cloud.google.com/compute/docs/disks/hyperdisks#throughput) + to provision for the attached hyperdisk. This parameter sets the + limit for throughput in MiB per second. + + Example: + type='hyperdisk-balanced,iops=5000,throughput=200,size=100G;type=hyperdisk-throughput,size=9000G' + + Attaches two disks to the instances. The first disk is a + hyperdisk-balanced disk with 5000 IOPS, 200 MiB/s throughput, and 100 + GiB size. The second disk is a hyperdisk-throughput disk with 9000 + GiB size. + --master-boot-disk-provisioned-iops=MASTER_BOOT_DISK_PROVISIONED_IOPS Indicates the IOPS (https://cloud.google.com/compute/docs/disks/hyperdisks#iops) to @@ -300,6 +342,42 @@ FLAGS The number of accelerators to attach to each instance. The default value is 1. + --secondary-worker-attached-disks=SECONDARY_WORKER_ATTACHED_DISKS + A list of disk configurations to attach to each instance in this group. + Disk configurations are separated by semicolons. Each disk + configuration is a comma-separated list of the following parameters. + + type - required + The type of disk to attach to the instances + (https://cloud.google.com/compute/docs/disks/hyperdisks). + Allowed disk types are: hyperdisk-balanced, hyperdisk-extreme, + hyperdisk-ml, hyperdisk-throughput. + + size - optional + The size of the disk. The value must be a whole number followed by + a size unit GB for gigabyte, or TB for terabyte. For example, + 10GB produces a 10 gigabyte disk. + + iops - optional + Indicates the IOPS + (https://cloud.google.com/compute/docs/disks/hyperdisks#iops) to + provision for the attached hyperdisk. This parameter sets the limit + for disk I/O operations per second. + + throughput - optional + Indicates the throughput + (https://cloud.google.com/compute/docs/disks/hyperdisks#throughput) + to provision for the attached hyperdisk. This parameter sets the + limit for throughput in MiB per second. + + Example: + type='hyperdisk-balanced,iops=5000,throughput=200,size=100G;type=hyperdisk-throughput,size=9000G' + + Attaches two disks to the instances. The first disk is a + hyperdisk-balanced disk with 5000 IOPS, 200 MiB/s throughput, and 100 + GiB size. The second disk is a hyperdisk-throughput disk with 9000 + GiB size. + --secondary-worker-boot-disk-size=SECONDARY_WORKER_BOOT_DISK_SIZE The size of the boot disk. The value must be a whole number followed by a size unit of KB for kilobyte, MB for megabyte, GB for gigabyte, or TB @@ -357,9 +435,6 @@ FLAGS The Google Cloud Storage bucket to use by default to store ephemeral cluster and jobs data, such as Spark and MapReduce history files. - --tier=TIER - Cluster tier. TIER must be one of: premium, standard. - --worker-accelerator=[type=TYPE,[count=COUNT],...] Attaches accelerators, such as GPUs, to the worker instance(s). @@ -372,6 +447,42 @@ FLAGS The number of accelerators to attach to each instance. The default value is 1. + --worker-attached-disks=WORKER_ATTACHED_DISKS + A list of disk configurations to attach to each instance in this group. + Disk configurations are separated by semicolons. Each disk + configuration is a comma-separated list of the following parameters. + + type - required + The type of disk to attach to the instances + (https://cloud.google.com/compute/docs/disks/hyperdisks). + Allowed disk types are: hyperdisk-balanced, hyperdisk-extreme, + hyperdisk-ml, hyperdisk-throughput. + + size - optional + The size of the disk. The value must be a whole number followed by + a size unit GB for gigabyte, or TB for terabyte. For example, + 10GB produces a 10 gigabyte disk. + + iops - optional + Indicates the IOPS + (https://cloud.google.com/compute/docs/disks/hyperdisks#iops) to + provision for the attached hyperdisk. This parameter sets the limit + for disk I/O operations per second. + + throughput - optional + Indicates the throughput + (https://cloud.google.com/compute/docs/disks/hyperdisks#throughput) + to provision for the attached hyperdisk. This parameter sets the + limit for throughput in MiB per second. + + Example: + type='hyperdisk-balanced,iops=5000,throughput=200,size=100G;type=hyperdisk-throughput,size=9000G' + + Attaches two disks to the instances. The first disk is a + hyperdisk-balanced disk with 5000 IOPS, 200 MiB/s throughput, and 100 + GiB size. The second disk is a hyperdisk-throughput disk with 9000 + GiB size. + --worker-boot-disk-provisioned-iops=WORKER_BOOT_DISK_PROVISIONED_IOPS Indicates the IOPS (https://cloud.google.com/compute/docs/disks/hyperdisks#iops) to diff --git a/gcloud/beta/firestore/databases/create b/gcloud/beta/firestore/databases/create index 1493059ae..68ebb3629 100644 --- a/gcloud/beta/firestore/databases/create +++ b/gcloud/beta/firestore/databases/create @@ -4,6 +4,7 @@ NAME SYNOPSIS gcloud beta firestore databases create --location=LOCATION + [--concurrency-mode=CONCURRENCY_MODE] [--database=DATABASE; default="(default)"] [--delete-protection] [--edition=EDITION; default="standard"] [--enable-firestore-data-access] @@ -82,6 +83,14 @@ REQUIRED FLAGS $ gcloud beta firestore databases create --location='us-east1' OPTIONAL FLAGS + --concurrency-mode=CONCURRENCY_MODE + The concurrency control mode to use for this database. + + When not specified, Firestore will pick a default concurrency mode + based on the database edition. + + CONCURRENCY_MODE must be one of: optimistic, pessimistic. + --database=DATABASE; default="(default)" The ID to use for the database, which will become the final component of the database's resource name. If database ID is not provided, diff --git a/gcloud/beta/firestore/databases/update b/gcloud/beta/firestore/databases/update index 27225f1d2..00bfad5b7 100644 --- a/gcloud/beta/firestore/databases/update +++ b/gcloud/beta/firestore/databases/update @@ -3,7 +3,8 @@ NAME of a Cloud Firestore database SYNOPSIS - gcloud beta firestore databases update [--async] [--database=DATABASE] + gcloud beta firestore databases update [--async] + [--concurrency-mode=CONCURRENCY_MODE] [--database=DATABASE] [--delete-protection] [--enable-pitr] [--type=TYPE] [GCLOUD_WIDE_FLAG ...] @@ -21,6 +22,10 @@ FLAGS Return immediately, without waiting for the operation in progress to complete. + --concurrency-mode=CONCURRENCY_MODE + The concurrency control mode to use for this database. CONCURRENCY_MODE + must be one of: optimistic, pessimistic. + Database resource - Cloud Firestore database to update. This represents a Cloud resource. (NOTE) Some attributes are not given arguments in this group but can be set in other ways. diff --git a/gcloud/beta/firestore/fields/ttls/update b/gcloud/beta/firestore/fields/ttls/update index 563238dbc..acabb8978 100644 --- a/gcloud/beta/firestore/fields/ttls/update +++ b/gcloud/beta/firestore/fields/ttls/update @@ -5,7 +5,9 @@ NAME SYNOPSIS gcloud beta firestore fields ttls update (FIELD : --collection-group=COLLECTION_GROUP --database=DATABASE) - (--disable-ttl | --enable-ttl) [--async] [GCLOUD_WIDE_FLAG ...] + (--disable-ttl + | [--enable-ttl : --expiration-offset=EXPIRATION_OFFSET]) [--async] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) Update the TTL configuration of the given field. @@ -27,6 +29,12 @@ EXAMPLES $ gcloud beta firestore fields ttls update expiry \ --collection-group=Events --disable-ttl + The following command sets the expiry field of the Events collection group + (kind) to be the TTL field, with an expiration offset of one week: + + $ gcloud beta firestore fields ttls update expiry \ + --collection-group=Events --enable-ttl --expiration-offset=7d + POSITIONAL ARGUMENTS Field resource - Field to update. The arguments in this group can be used to specify the attributes of this resource. (NOTE) Some attributes are not @@ -72,8 +80,18 @@ REQUIRED FLAGS --disable-ttl Set to make this field no longer the TTL for its collection group. - --enable-ttl - Set to enable this field as the TTL for its collection group. + Or at least one of these can be specified: + + --enable-ttl + Set to enable this field as the TTL for its collection group. + + This flag argument must be specified if any of the other arguments + in this group are specified. + + --expiration-offset=EXPIRATION_OFFSET + The offset, relative to the timestamp value from the TTL-enabled + field, used to determine the document's expiration time. If unset, + defaults to 0. OPTIONAL FLAGS --async diff --git a/gcloud/beta/firestore/indexes/composite/create b/gcloud/beta/firestore/indexes/composite/create index ec8c24a60..6ffa2e29e 100644 --- a/gcloud/beta/firestore/indexes/composite/create +++ b/gcloud/beta/firestore/indexes/composite/create @@ -4,13 +4,16 @@ NAME SYNOPSIS gcloud beta firestore indexes composite create - --field-config=[array-config=ARRAY-CONFIG], - [field-path=FIELD-PATH],[order=ORDER],[vector-config=VECTOR-CONFIG] + --field-config=[array-config=ARRAY-CONFIG],[field-path=FIELD-PATH], + [order=ORDER], + [search-config=SEARCH-CONFIG],[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"] [--unique] - [GCLOUD_WIDE_FLAG ...] + [--query-scope=QUERY_SCOPE; default="collection"] + [--search-index-options=[text-language=TEXT-LANGUAGE], + [text-language-override-field-path=TEXT-LANGUAGE-OVERRIDE-FIELD-PATH]] + [--unique] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) Create a new composite index. @@ -31,7 +34,7 @@ EXAMPLES --field-config=field-path=timestamp,order=descending REQUIRED FLAGS - --field-config=[array-config=ARRAY-CONFIG],[field-path=FIELD-PATH],[order=ORDER],[vector-config=VECTOR-CONFIG] + --field-config=[array-config=ARRAY-CONFIG],[field-path=FIELD-PATH],[order=ORDER],[search-config=SEARCH-CONFIG],[vector-config=VECTOR-CONFIG] Required, Configuration for an index field. array-config @@ -47,6 +50,53 @@ REQUIRED FLAGS Exactly one of 'order', 'array-config', or 'vector-config' must be specified. + search-config + Specifies the configuration for a search field. An index definition + must contain either only 'search-config' fields or only non + 'search-config' fields. + + Examples: + + Text search: + + --field-config=field-path=title,search-config='{"text-spec": {"index-specs": [{"index-type": "TOKENIZED", "match-type": "MATCH_GLOBALLY"}]}}' + + Geo search: + + --field-config=field-path=location,search-config='{"geo-spec": {"geo-json-indexing-disabled": true}}' + + With file: + + --field-config=field-path=text,search-config='/path/to/configs/search-config.json' + + For complex configurations, it is recommended to use a file. + + geo-spec + Optional. The specification for building a geo search index for + a field. + + geo-json-indexing-disabled + Optional. Disables geoJSON indexing for the field. By + default, geoJSON points are indexed. + + text-spec + Optional. The specification for building a text search index + for a field. + + index-specs + Optional. Array of specifications for how the field should + be indexed. + + index-type + Required. How to index the text field value. Valid + options are: + ▹ TOKENIZED: Field values are tokenized. + + match-type + Required. How to match the text field value. Valid + options are: + ▹ MATCH_GLOBALLY: Match on any indexed field. + vector-config Specifies the configuration for a vector field. Exactly one of 'order', 'array-config', or 'vector-config' must be specified. @@ -59,11 +109,11 @@ REQUIRED FLAGS Shorthand Example: - --field-config=array-config=string,field-path=string,order=string,vector-config={dimension=int,flat} --field-config=array-config=string,field-path=string,order=string,vector-config={dimension=int,flat} + --field-config=array-config=string,field-path=string,order=string,search-config={geo-spec={geo-json-indexing-disabled=boolean},text-spec={index-specs=[{index-type=string,match-type=string}]}},vector-config={dimension=int,flat} --field-config=array-config=string,field-path=string,order=string,search-config={geo-spec={geo-json-indexing-disabled=boolean},text-spec={index-specs=[{index-type=string,match-type=string}]}},vector-config={dimension=int,flat} JSON Example: - --field-config='[{"array-config": "string", "field-path": "string", "order": "string", "vector-config": {"dimension": int, "flat": {}}}]' + --field-config='[{"array-config": "string", "field-path": "string", "order": "string", "search-config": {"geo-spec": {"geo-json-indexing-disabled": boolean}, "text-spec": {"index-specs": [{"index-type": "string", "match-type": "string"}]}}, "vector-config": {"dimension": int, "flat": {}}}]' File Example: @@ -121,12 +171,42 @@ OPTIONAL FLAGS 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. + 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. + --search-index-options=[text-language=TEXT-LANGUAGE],[text-language-override-field-path=TEXT-LANGUAGE-OVERRIDE-FIELD-PATH] + Optional. Configuration options for search indexes. + + text-language + Optional. The language to use for text search indexes. Used as the + default language if not overridden at the document level by + specifying the 'text-language-override-field-path'. The language is + specified as a BCP 47 language code. For indexes with + 'MONGODB_COMPATIBLE_API' ApiScope: If unspecified, the default + language is English. For indexes with 'ANY_API' ApiScope: If + unspecified, the default behavior is autodetect. + + text-language-override-field-path + Optional. The field in the document that specifies which language + to use for that specific document. If unspecified, the language is + taken from the 'language' document field if it exists or from + 'text-language' if it does not. + + Shorthand Example: + + --search-index-options=text-language=string,text-language-override-field-path=string + + JSON Example: + + --search-index-options='{"text-language": "string", "text-language-override-field-path": "string"}' + + File Example: + + --search-index-options=path_to_file.(yaml|json) + --unique Optional. Whether it is an unique index. Unique index ensures all values for the indexed field(s) are unique across documents. diff --git a/gcloud/beta/iam/access-policies/create b/gcloud/beta/iam/access-policies/create index e52b54bc7..4556f59b4 100644 --- a/gcloud/beta/iam/access-policies/create +++ b/gcloud/beta/iam/access-policies/create @@ -19,7 +19,7 @@ EXAMPLES To create a policy instance called my-policy, run: $ gcloud beta iam access-policies create my-policy \ - --organization=123 --location=global --details.rules=rule1.json + --organization=123 --location=global --details-rules=rule1.json POSITIONAL ARGUMENTS AccessPolicy resource - Identifier. The resource name of the access @@ -120,10 +120,10 @@ FLAGS The conditions that determine whether this rule applies to a request. Conditions are identified by their key, which is the FQDN of the service that they are relevant to. For example: - "conditions": { "iam.googleapis.com": }. Each rule - is evaluated independently. If this rule does not apply to a - request, other rules might still apply. Currently supported keys - are as follows: + "conditions": { "iam.googleapis.com": { "expression": } }. Each rule is evaluated independently. If this rule + does not apply to a request, other rules might still apply. + Currently supported keys are as follows: ▸ eventarc.googleapis.com: Can use CEL functions that evaluate resource fields. diff --git a/gcloud/beta/iam/access-policies/update b/gcloud/beta/iam/access-policies/update index a3ad675e8..ae7b9e750 100644 --- a/gcloud/beta/iam/access-policies/update +++ b/gcloud/beta/iam/access-policies/update @@ -203,10 +203,10 @@ FLAGS The conditions that determine whether this rule applies to a request. Conditions are identified by their key, which is the FQDN of the service that they are relevant to. For example: - "conditions": { "iam.googleapis.com": }. Each - rule is evaluated independently. If this rule does not apply to a - request, other rules might still apply. Currently supported keys - are as follows: + "conditions": { "iam.googleapis.com": { "expression": } }. Each rule is evaluated independently. If this + rule does not apply to a request, other rules might still apply. + Currently supported keys are as follows: ▫ eventarc.googleapis.com: Can use CEL functions that evaluate resource fields. @@ -332,10 +332,10 @@ FLAGS The conditions that determine whether this rule applies to a request. Conditions are identified by their key, which is the FQDN of the service that they are relevant to. For example: - "conditions": { "iam.googleapis.com": }. Each - rule is evaluated independently. If this rule does not apply to - a request, other rules might still apply. Currently supported - keys are as follows: + "conditions": { "iam.googleapis.com": { "expression": } }. Each rule is evaluated independently. If this + rule does not apply to a request, other rules might still + apply. Currently supported keys are as follows: ◇ eventarc.googleapis.com: Can use CEL functions that evaluate resource fields. @@ -467,10 +467,10 @@ FLAGS The conditions that determine whether this rule applies to a request. Conditions are identified by their key, which is the FQDN of the service that they are relevant to. For example: - "conditions": { "iam.googleapis.com": }. - Each rule is evaluated independently. If this rule does not - apply to a request, other rules might still apply. Currently - supported keys are as follows: + "conditions": { "iam.googleapis.com": { "expression": } }. Each rule is evaluated independently. If + this rule does not apply to a request, other rules might + still apply. Currently supported keys are as follows: ▹ eventarc.googleapis.com: Can use CEL functions that evaluate resource fields. diff --git a/gcloud/beta/iam/workforce-pools/providers/create-oidc b/gcloud/beta/iam/workforce-pools/providers/create-oidc index 25cffee4b..6c73829e9 100644 --- a/gcloud/beta/iam/workforce-pools/providers/create-oidc +++ b/gcloud/beta/iam/workforce-pools/providers/create-oidc @@ -202,6 +202,9 @@ REQUIRED FLAGS Each additional scope may be at most 256 characters. A maximum of 10 additional scopes may be configured. + Updating this field replaces any existing values. Include the full + list of additional scopes to avoid losing existing values. + OPTIONAL FLAGS --async Return immediately, without waiting for the operation in progress to diff --git a/gcloud/beta/iam/workforce-pools/providers/update-oidc b/gcloud/beta/iam/workforce-pools/providers/update-oidc index 0b449feb3..fd3050f09 100644 --- a/gcloud/beta/iam/workforce-pools/providers/update-oidc +++ b/gcloud/beta/iam/workforce-pools/providers/update-oidc @@ -239,6 +239,9 @@ FLAGS Each additional scope may be at most 256 characters. A maximum of 10 additional scopes may be configured. + Updating this field replaces any existing values. Include the full list + of additional scopes to avoid losing existing values. + --web-sso-assertion-claims-behavior=WEB_SSO_ASSERTION_CLAIMS_BEHAVIOR The behavior for how OIDC Claims are included in the assertion object used for attribute mapping and attribute condition. Use diff --git a/gcloud/beta/iap/tcp/help b/gcloud/beta/iap/tcp/help index 06c395576..ada1cb30f 100644 --- a/gcloud/beta/iap/tcp/help +++ b/gcloud/beta/iap/tcp/help @@ -2,7 +2,7 @@ NAME gcloud beta iap tcp - manage IAP TCP resources SYNOPSIS - gcloud beta iap tcp GROUP [GCLOUD_WIDE_FLAG ...] + gcloud beta iap tcp GROUP | COMMAND [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) Manage IAP TCP resources. diff --git a/gcloud/beta/iap/web/add-iam-policy-binding b/gcloud/beta/iap/web/add-iam-policy-binding index fee067f1d..5fa7db82c 100644 --- a/gcloud/beta/iap/web/add-iam-policy-binding +++ b/gcloud/beta/iap/web/add-iam-policy-binding @@ -5,8 +5,9 @@ NAME SYNOPSIS gcloud beta iap web add-iam-policy-binding --member=PRINCIPAL --role=ROLE [--condition=[KEY=VALUE,...] | --condition-from-file=PATH_TO_FILE] - [--region=REGION - --resource-type=RESOURCE_TYPE --service=SERVICE --version=VERSION] + [--region=REGION --resource-type=RESOURCE_TYPE + --service=SERVICE --version=VERSION --agent=AGENT + | --endpoint=ENDPOINT | --mcp-server=MCP_SERVER] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -122,7 +123,8 @@ OPTIONAL FLAGS --resource-type=RESOURCE_TYPE Resource type of the IAP resource. RESOURCE_TYPE must be one of: - app-engine, backend-services, forwarding-rule, cloud-run. + app-engine, backend-services, forwarding-rule, cloud-run, + agent-registry. --service=SERVICE Service name. @@ -131,6 +133,17 @@ OPTIONAL FLAGS Service version. Should only be specified with --resource-type=app-engine. + At most one of these can be specified: + + --agent=AGENT + Agent ID for the agent-registry resource type. + + --endpoint=ENDPOINT + Endpoint ID for the agent-registry resource type. + + --mcp-server=MCP_SERVER + MCP server ID for the agent-registry resource type. + 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/iap/web/get-iam-policy b/gcloud/beta/iap/web/get-iam-policy index e9e15e89f..eecb318e0 100644 --- a/gcloud/beta/iap/web/get-iam-policy +++ b/gcloud/beta/iap/web/get-iam-policy @@ -3,8 +3,9 @@ NAME SYNOPSIS gcloud beta iap web get-iam-policy - [--region=REGION - --resource-type=RESOURCE_TYPE --service=SERVICE --version=VERSION] + [--region=REGION --resource-type=RESOURCE_TYPE + --service=SERVICE --version=VERSION --agent=AGENT + | --endpoint=ENDPOINT | --mcp-server=MCP_SERVER] [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [GCLOUD_WIDE_FLAG ...] @@ -76,7 +77,8 @@ FLAGS --resource-type=RESOURCE_TYPE Resource type of the IAP resource. RESOURCE_TYPE must be one of: - app-engine, backend-services, forwarding-rule, cloud-run. + app-engine, backend-services, forwarding-rule, cloud-run, + agent-registry. --service=SERVICE Service name. @@ -85,6 +87,17 @@ FLAGS Service version. Should only be specified with --resource-type=app-engine. + At most one of these can be specified: + + --agent=AGENT + Agent ID for the agent-registry resource type. + + --endpoint=ENDPOINT + Endpoint ID for the agent-registry resource type. + + --mcp-server=MCP_SERVER + MCP server ID for the agent-registry resource type. + LIST COMMAND FLAGS --filter=EXPRESSION Apply a Boolean filter EXPRESSION to each resource item to be listed. diff --git a/gcloud/beta/iap/web/remove-iam-policy-binding b/gcloud/beta/iap/web/remove-iam-policy-binding index 742276722..11ac24cf4 100644 --- a/gcloud/beta/iap/web/remove-iam-policy-binding +++ b/gcloud/beta/iap/web/remove-iam-policy-binding @@ -7,8 +7,9 @@ SYNOPSIS --role=ROLE [--all | --condition=[KEY=VALUE,...] | --condition-from-file=PATH_TO_FILE] - [--region=REGION - --resource-type=RESOURCE_TYPE --service=SERVICE --version=VERSION] + [--region=REGION --resource-type=RESOURCE_TYPE + --service=SERVICE --version=VERSION --agent=AGENT + | --endpoint=ENDPOINT | --mcp-server=MCP_SERVER] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -139,7 +140,8 @@ OPTIONAL FLAGS --resource-type=RESOURCE_TYPE Resource type of the IAP resource. RESOURCE_TYPE must be one of: - app-engine, backend-services, forwarding-rule, cloud-run. + app-engine, backend-services, forwarding-rule, cloud-run, + agent-registry. --service=SERVICE Service name. @@ -148,6 +150,17 @@ OPTIONAL FLAGS Service version. Should only be specified with --resource-type=app-engine. + At most one of these can be specified: + + --agent=AGENT + Agent ID for the agent-registry resource type. + + --endpoint=ENDPOINT + Endpoint ID for the agent-registry resource type. + + --mcp-server=MCP_SERVER + MCP server ID for the agent-registry resource type. + 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/iap/web/set-iam-policy b/gcloud/beta/iap/web/set-iam-policy index abc7e8b40..b16a4f895 100644 --- a/gcloud/beta/iap/web/set-iam-policy +++ b/gcloud/beta/iap/web/set-iam-policy @@ -4,8 +4,9 @@ NAME SYNOPSIS gcloud beta iap web set-iam-policy POLICY_FILE - [--region=REGION - --resource-type=RESOURCE_TYPE --service=SERVICE --version=VERSION] + [--region=REGION --resource-type=RESOURCE_TYPE + --service=SERVICE --version=VERSION --agent=AGENT + | --endpoint=ENDPOINT | --mcp-server=MCP_SERVER] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -85,7 +86,8 @@ FLAGS --resource-type=RESOURCE_TYPE Resource type of the IAP resource. RESOURCE_TYPE must be one of: - app-engine, backend-services, forwarding-rule, cloud-run. + app-engine, backend-services, forwarding-rule, cloud-run, + agent-registry. --service=SERVICE Service name. @@ -94,6 +96,17 @@ FLAGS Service version. Should only be specified with --resource-type=app-engine. + At most one of these can be specified: + + --agent=AGENT + Agent ID for the agent-registry resource type. + + --endpoint=ENDPOINT + Endpoint ID for the agent-registry resource type. + + --mcp-server=MCP_SERVER + MCP server ID for the agent-registry resource type. + 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/kms/asymmetric-sign b/gcloud/beta/kms/asymmetric-sign index 03f0b7b01..a1016e7db 100644 --- a/gcloud/beta/kms/asymmetric-sign +++ b/gcloud/beta/kms/asymmetric-sign @@ -19,6 +19,11 @@ DESCRIPTION received from Cloud KMS. Use --skip-integrity-verification to disable integrity verification. + For the ML-DSA EXTERNAL-MU algorithms, the digest external-mu should be + used that depends on the public key. This command will fetch the public key + from KMS and compute the external-mu digest. Note that this requires signer + permissions on the associated CryptoKeyVersion. + EXAMPLES The following command will read the file '/tmp/my/file.to.sign', digest it with the digest algorithm 'sha256' and sign it using the asymmetric @@ -40,7 +45,7 @@ REQUIRED FLAGS OPTIONAL FLAGS --digest-algorithm=DIGEST_ALGORITHM The algorithm to digest the input. DIGEST_ALGORITHM must be one of: - sha256, sha384, sha512. + external-mu, sha256, sha384, sha512. --key=KEY to use for signing. diff --git a/gcloud/beta/kms/key-handles/create b/gcloud/beta/kms/key-handles/create index 4cc3dde0f..173697039 100644 --- a/gcloud/beta/kms/key-handles/create +++ b/gcloud/beta/kms/key-handles/create @@ -19,8 +19,8 @@ EXAMPLES $ gcloud beta kms key-handles create --key-handle-id=my-key-handle \ --location=global --resource-type=compute.googleapis.com/Disk - In case we want to generate a random KeyHandle id, we can use the - --generate-key-handle-id flag instead of the --key-handle-id flag. + To generate a random KeyHandle id, the --generate-key-handle-id flag can be + used instead of --key-handle-id. REQUIRED FLAGS Location resource - The KMS location resource. This represents a Cloud diff --git a/gcloud/beta/kms/single-tenant-hsm/create b/gcloud/beta/kms/single-tenant-hsm/create index c88872afc..67c10b30a 100644 --- a/gcloud/beta/kms/single-tenant-hsm/create +++ b/gcloud/beta/kms/single-tenant-hsm/create @@ -4,7 +4,7 @@ NAME SYNOPSIS gcloud beta kms single-tenant-hsm create --location=LOCATION - --total-approver-count=TOTAL_APPROVER_COUNT + --total-approver-count=TOTAL_APPROVER_COUNT [--key-portability-enabled] [--single-tenant-hsm-instance-id=SINGLE_TENANT_HSM_INSTANCE_ID] [GCLOUD_WIDE_FLAG ...] @@ -47,6 +47,10 @@ REQUIRED FLAGS to 16. OPTIONAL FLAGS + --key-portability-enabled + If set, the single tenant HSM instance will be able to perform key + portability operations. + --single-tenant-hsm-instance-id=SINGLE_TENANT_HSM_INSTANCE_ID Specify an ID for the single tenant HSM instance. It must be unique within a location and match the regular expression [a-zA-Z0-9-]{1,63}. diff --git a/gcloud/beta/kms/single-tenant-hsm/describe b/gcloud/beta/kms/single-tenant-hsm/describe index 87a937d5f..c6e874f30 100644 --- a/gcloud/beta/kms/single-tenant-hsm/describe +++ b/gcloud/beta/kms/single-tenant-hsm/describe @@ -10,14 +10,14 @@ SYNOPSIS DESCRIPTION (BETA) Returns metadata for the given single tenant HSM instance. - ## EXAMPLES - +EXAMPLES The following command returns the metadata for the single tenant HSM - instance with the name my_sthi in the location us-east1`using the fully + instance with the name my_sthi in the location us-east1 using the fully specified name: - $ gcloud beta kms single-tenant-hsm describe - projects/my-project/locations/us-east1/singleTenantHsmInstances/mysthi + $ gcloud beta kms single-tenant-hsm describe \ + projects/my-project/locations/us-east1/\ + singleTenantHsmInstances/mysthi The following command returns the metadata for the singletenanthsm instance with the name mysthi in the location us-east1 using the location and diff --git a/gcloud/beta/kms/single-tenant-hsm/proposal/describe b/gcloud/beta/kms/single-tenant-hsm/proposal/describe index 6fa02d81a..70c49bde4 100644 --- a/gcloud/beta/kms/single-tenant-hsm/proposal/describe +++ b/gcloud/beta/kms/single-tenant-hsm/proposal/describe @@ -13,16 +13,16 @@ EXAMPLES instance proposal with the name my_proposal, of the instance my_sthi, and in the location us-east1 using the fully specified resource name. - $ gcloud beta kms single-tenant-hsm proposal describe \ - projects/my-project/locations/us-east1/\ - singleTenantHsmInstances/ my_sthi/proposals/my_proposal ``` + $ gcloud beta kms single-tenant-hsm proposal describe \ + projects/my-project/locations/us-east1/\ + singleTenantHsmInstances/my_sthi/proposals/my_proposal - The following command returns the metadata for the single tenant HSM instance - proposal with the name `my_proposal`, of the instance `my_sthi`, and in the - location `us-east1` using the location, instance id, and proposal id. + The following command returns the metadata for the single tenant HSM + instance proposal with the name my_proposal, of the instance my_sthi, and + in the location us-east1 using the location, instance id, and proposal id. $ gcloud beta kms single-tenant-hsm proposal describe my_proposal \ - --single_tenant_hsm_instance=my_sthi --location=us-east1 ``` + --single_tenant_hsm_instance=my_sthi --location=us-east1 POSITIONAL ARGUMENTS SingleTenantHsmInstanceProposal resource - The KMS single tenant HSM diff --git a/gcloud/beta/lifesciences/help b/gcloud/beta/lifesciences/help deleted file mode 100644 index ca213e7e1..000000000 --- a/gcloud/beta/lifesciences/help +++ /dev/null @@ -1,32 +0,0 @@ -NAME - gcloud beta lifesciences - manage Cloud Life Sciences resources - -SYNOPSIS - gcloud beta lifesciences GROUP [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (BETA) Manage Cloud Life Sciences resources. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --help. - - Run $ gcloud help for details. - -GROUPS - GROUP is one of the following: - - locations - (BETA) Query Cloud Life Sciences locations. - - operations - (BETA) Manage Cloud Life Sciences operations. - - pipelines - (BETA) Commands for Life Sciences pipelines. - -NOTES - This command is currently in beta and might change without notice. This - variant is also available: - - $ gcloud alpha lifesciences - diff --git a/gcloud/beta/lifesciences/locations/describe b/gcloud/beta/lifesciences/locations/describe deleted file mode 100644 index a0028861a..000000000 --- a/gcloud/beta/lifesciences/locations/describe +++ /dev/null @@ -1,53 +0,0 @@ -NAME - gcloud beta lifesciences locations describe - describe a Cloud Life - Sciences location - -SYNOPSIS - gcloud beta lifesciences locations describe [LOCATION] - [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (BETA) Describe a Cloud Life Sciences location. - -EXAMPLES - To describe a location (for example, us-central1) called my-location, run: - - $ gcloud beta lifesciences locations describe my-location - -POSITIONAL ARGUMENTS - Location resource - Cloud Life Sciences location to describe. This - represents a Cloud resource. (NOTE) Some attributes are not given - arguments in this group but can be set in other ways. - - To set the project attribute: - ◆ provide the argument location on the command line with a fully - specified name; - ◆ set the property lifesciences/location with a fully specified name; - ◆ provide the argument --project on the command line; - ◆ set the property core/project. - - [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 lifesciences/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 lifesciences/v2beta API. The full documentation for - this API can be found at: https://cloud.google.com/life-sciences - -NOTES - This command is currently in beta and might change without notice. This - variant is also available: - - $ gcloud alpha lifesciences locations describe - diff --git a/gcloud/beta/lifesciences/locations/help b/gcloud/beta/lifesciences/locations/help deleted file mode 100644 index a8fb9e7d0..000000000 --- a/gcloud/beta/lifesciences/locations/help +++ /dev/null @@ -1,29 +0,0 @@ -NAME - gcloud beta lifesciences locations - query Cloud Life Sciences locations - -SYNOPSIS - gcloud beta lifesciences locations COMMAND [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (BETA) Query Cloud Life Sciences locations. - -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 Cloud Life Sciences location. - - list - (BETA) List all locations where Cloud Life Sciences is available. - -NOTES - This command is currently in beta and might change without notice. This - variant is also available: - - $ gcloud alpha lifesciences locations - diff --git a/gcloud/beta/lifesciences/operations/help b/gcloud/beta/lifesciences/operations/help deleted file mode 100644 index 187b406fe..000000000 --- a/gcloud/beta/lifesciences/operations/help +++ /dev/null @@ -1,35 +0,0 @@ -NAME - gcloud beta lifesciences operations - manage Cloud Life Sciences operations - -SYNOPSIS - gcloud beta lifesciences operations COMMAND [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (BETA) Manage Cloud Life Sciences 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 - (BETA) Cancel a Cloud Life Sciences operation. - - describe - (BETA) Describe a Cloud Life Sciences operation. - - list - (BETA) List Cloud Life Sciences operations. - - wait - (BETA) Wait for Cloud Life Sciences operation to complete. - -NOTES - This command is currently in beta and might change without notice. This - variant is also available: - - $ gcloud alpha lifesciences operations - diff --git a/gcloud/beta/lifesciences/pipelines/help b/gcloud/beta/lifesciences/pipelines/help deleted file mode 100644 index e8d9b6f48..000000000 --- a/gcloud/beta/lifesciences/pipelines/help +++ /dev/null @@ -1,26 +0,0 @@ -NAME - gcloud beta lifesciences pipelines - commands for Life Sciences pipelines - -SYNOPSIS - gcloud beta lifesciences pipelines COMMAND [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (BETA) Command to run pipelines. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --help. - - Run $ gcloud help for details. - -COMMANDS - COMMAND is one of the following: - - run - (BETA) Defines and runs a pipeline. - -NOTES - This command is currently in beta and might change without notice. This - variant is also available: - - $ gcloud alpha lifesciences pipelines - diff --git a/gcloud/beta/lifesciences/pipelines/run b/gcloud/beta/lifesciences/pipelines/run deleted file mode 100644 index d46da8fe1..000000000 --- a/gcloud/beta/lifesciences/pipelines/run +++ /dev/null @@ -1,197 +0,0 @@ -NAME - gcloud beta lifesciences pipelines run - defines and runs a pipeline - -SYNOPSIS - gcloud beta lifesciences pipelines run - (--command-line=COMMAND_LINE | --pipeline-file=PIPELINE_FILE) - [--disk-size=DISK_SIZE] - [--docker-image=DOCKER_IMAGE; default="google/cloud-sdk:slim"] - [--env-vars=[NAME=VALUE,...]] [--inputs=[NAME=VALUE,...]] - [--inputs-from-file=[NAME=FILE,...]] [--logging=LOGGING] - [--outputs=[NAME=VALUE,...]] [--preemptible] - [--boot-disk-size=BOOT_DISK_SIZE] [--labels=[KEY=VALUE,...]] - [--location=LOCATION] - [--machine-type=MACHINE_TYPE; default="n1-standard-1"] - [--network=NETWORK] [--regions=[REGION,...]] - [--service-account-email=SERVICE_ACCOUNT_EMAIL; default="default"] - [--service-account-scopes=[SCOPE,...]] [--subnetwork=SUBNETWORK] - [--zones=[ZONE,...]] [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (BETA) A pipeline is a transformation of a set of inputs to a set of - outputs. Supports Docker-based commands. - -EXAMPLES - To run a pipeline described in the pipeline.json file, run: - - $ gcloud beta lifesciences pipelines run \ - --pipeline-file=pipeline.json - -REQUIRED FLAGS - Exactly one of these must be specified: - - --command-line=COMMAND_LINE - Command line to run with /bin/sh in the specified Docker image. - Cannot be used with --pipeline-file. - - --pipeline-file=PIPELINE_FILE - A YAML or JSON file containing a Pipeline object. See - https://cloud.google.com/life-sciences/docs/reference/rest/v2beta/projects.locations.pipelines/run#pipeline - -COMMONLY USED FLAGS - --disk-size=DISK_SIZE - The disk size(s) in GB, specified as a comma-separated list of pairs of - disk name and size. For example: --disk-size "name:size,name2:size2". - Overrides any values specified in the pipeline-file. - - --docker-image=DOCKER_IMAGE; default="google/cloud-sdk:slim" - A Docker image to run. Requires --command-line to be specified and - cannot be used with --pipeline-file. - - --env-vars=[NAME=VALUE,...] - List of key-value pairs to set as environment variables. - - --inputs=[NAME=VALUE,...] - Map of input PipelineParameter names to values. Used to pass literal - parameters to the pipeline, and to specify input files in Google Cloud - Storage that will have a localCopy made. Specified as a comma-separated - list: --inputs file=gs://my-bucket/in.txt,name=hello - - --inputs-from-file=[NAME=FILE,...] - Map of input PipelineParameter names to values. Used to pass literal - parameters to the pipeline where values come from local files; this can - be used to send large pipeline input parameters, such as code, data, or - configuration values. Specified as a comma-separated list: - --inputs-from-file script=myshellscript.sh,pyfile=mypython.py - - --logging=LOGGING - The location in Google Cloud Storage to which the pipeline logs will be - copied. Can be specified as a fully qualified directory path, in which - case logs will be output with a unique identifier as the filename in - that directory, or as a fully specified path, which must end in .log, - in which case that path will be used. Stdout and stderr logs from the - run are also generated and output as -stdout.log and -stderr.log. - - --outputs=[NAME=VALUE,...] - Map of output PipelineParameter names to values. Used to specify output - files in Google Cloud Storage that will be made from a localCopy. - Specified as a comma-separated list: --outputs - ref=gs://my-bucket/foo,ref2=gs://my-bucket/bar - - --preemptible - Whether to use a preemptible VM for this pipeline. The "resource" - section of the pipeline-file must also set preemptible to "true" for - this flag to take effect. - -OTHER FLAGS - --boot-disk-size=BOOT_DISK_SIZE - The size of the boot disk in GB. - - The boot disk size must be large enough to accommodate all Docker - images from each action in the pipeline at the same time. If not - specified, a small but reasonable default value is used. - - --labels=[KEY=VALUE,...] - List of label KEY=VALUE pairs to add. - - Keys must start with a lowercase character and contain only hyphens - (-), underscores (_), lowercase characters, and numbers. Values must - contain only hyphens (-), underscores (_), lowercase characters, and - numbers. - - Location resource - The Google Cloud location to run the pipeline. 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 lifesciences/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 lifesciences/location. - - --machine-type=MACHINE_TYPE; default="n1-standard-1" - The type of VirtualMachine to use. Defaults to n1-standard-1. - - --network=NETWORK - The network name to attach the VM's network interface to. - - The value will be prefixed with global/networks/ unless it contains a - /, in which case it is assumed to be a fully specified network resource - URL. - - If unspecified, the global default network is used. - - --regions=[REGION,...] - List of Compute Engine regions the pipeline can run in. - - If no regions are specified with the regions flag, then regions in the - pipeline definition file will be used. - - If no regions are specified in the pipeline definition, then the - default region in your local client configuration is used. - - At least one region or region must be specified. - - For more information on default regions, see - https://cloud.google.com/compute/docs/gcloud-compute/#set_default_zone_and_region_in_your_local_client - - --service-account-email=SERVICE_ACCOUNT_EMAIL; default="default" - The service account used on the Compute Engine VMs that run the - pipeline. If unspecified, defaults to the Compute Engine service - account for your project. - - --service-account-scopes=[SCOPE,...] - List of additional scopes to be made available for this service - account. The following scopes are always requested: - - https://www.googleapis.com/auth/cloud-platform - - --subnetwork=SUBNETWORK - The subnetwork to use on the provided network. - - If the specified network is configured for custom subnet creation, the - name of the subnetwork to attach the instance to must be specified - here. - - The value is prefixed with regions/*/subnetworks/ unless it contains a - /, in which case it is assumed to be a fully specified subnetwork - resource URL. - - If the * character appears in the value, it is replaced with the region - that the virtual machine has been allocated in. - - --zones=[ZONE,...] - List of Compute Engine zones the pipeline can run in. - - If no zones are specified with the zones flag, then zones in the - pipeline definition file will be used. - - If no zones are specified in the pipeline definition, then the default - zone in your local client configuration is used (and must be - specified). - - For more information on default zones, see - https://cloud.google.com/compute/docs/gcloud-compute/#set_default_zone_and_region_in_your_local_client - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --configuration, --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 lifesciences pipelines run - diff --git a/gcloud/beta/memorystore/instances/create b/gcloud/beta/memorystore/instances/create index 66f5d8c3a..1ba89441e 100644 --- a/gcloud/beta/memorystore/instances/create +++ b/gcloud/beta/memorystore/instances/create @@ -282,12 +282,24 @@ FLAGS Machine type for individual nodes of the instance. NODE_TYPE must be one of: + custom-micro + Custom micro. + custom-mini + Custom mini. + custom-pico + Custom pico. + highcpu-medium + High cpu medium. + highmem-2xlarge + High memory 2xlarge. highmem-medium High memory medium. highmem-xlarge High memory extra large. shared-core-nano Shared core nano. + standard-large + Standard large. standard-small Standard small. diff --git a/gcloud/beta/memorystore/instances/create-token-auth-user b/gcloud/beta/memorystore/instances/create-token-auth-user new file mode 100644 index 000000000..4199d2f5e --- /dev/null +++ b/gcloud/beta/memorystore/instances/create-token-auth-user @@ -0,0 +1,77 @@ +NAME + gcloud beta memorystore instances create-token-auth-user - create token + auth user for a Memorystore instance + +SYNOPSIS + gcloud beta memorystore instances create-token-auth-user + (INSTANCE : --location=LOCATION) --token-auth-user=TOKEN_AUTH_USER + [--async] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) create token auth user for a Memorystore instance + +EXAMPLES + To create a token auth user for a Memorystore instance, run: + + $ gcloud beta memorystore instances create-token-auth-user + +POSITIONAL ARGUMENTS + Instance resource - The instance resource that this token auth user will + be created for. Format: + projects/{project}/locations/{location}/instances/{instance} 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 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 + ID of the instance or fully qualified identifier for the instance. + + To set the instance attribute: + ▸ provide the argument instance 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 instance resource. + + To set the location attribute: + ▸ provide the argument instance on the command line with a fully + specified name; + ▸ provide the argument --location on the command line. + +REQUIRED FLAGS + --token-auth-user=TOKEN_AUTH_USER + The name of the token auth user to create. + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the memorystore/v1beta API. The full documentation for + this API can be found at: https://cloud.google.com/memorystore/ + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha memorystore instances create-token-auth-user + diff --git a/gcloud/beta/memorystore/instances/help b/gcloud/beta/memorystore/instances/help index 655da72ad..fd29d2ebc 100644 --- a/gcloud/beta/memorystore/instances/help +++ b/gcloud/beta/memorystore/instances/help @@ -12,6 +12,12 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. +GROUPS + GROUP is one of the following: + + token-auth-users + (BETA) Manage Token Auth User resources. + COMMANDS COMMAND is one of the following: @@ -21,6 +27,9 @@ COMMANDS create (BETA) Create a Memorystore instance. + create-token-auth-user + (BETA) create token auth user for a Memorystore instance. + delete (BETA) Delete a Memorystore instance. diff --git a/gcloud/beta/memorystore/instances/token-auth-users/auth-tokens/delete b/gcloud/beta/memorystore/instances/token-auth-users/auth-tokens/delete new file mode 100644 index 000000000..8a184bb04 --- /dev/null +++ b/gcloud/beta/memorystore/instances/token-auth-users/auth-tokens/delete @@ -0,0 +1,92 @@ +NAME + gcloud beta memorystore instances token-auth-users auth-tokens delete - + delete authTokens + +SYNOPSIS + gcloud beta memorystore instances token-auth-users auth-tokens delete + (AUTH_TOKEN : --instance=INSTANCE + --location=LOCATION --token-auth-user=TOKEN_AUTH_USER) [--async] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Delete an authToken + +EXAMPLES + To delete the authToken, run: + + $ gcloud beta memorystore instances token-auth-users auth-tokens \ + delete + +POSITIONAL ARGUMENTS + AuthToken resource - The name of the token auth user resource that this + token will be deleted from. Format: + projects/{project}/locations/{location}/instances/{instance}/tokenAuthUsers/{token_auth_user}/authTokens/{name} + The arguments in this group can be used to specify the attributes of this + resource. (NOTE) Some attributes are not given arguments in this group but + can be set in other ways. + + To set the project attribute: + ◆ provide the argument auth_token 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. + + AUTH_TOKEN + ID of the authToken or fully qualified identifier for the authToken. + + To set the auth_token attribute: + ▸ provide the argument auth_token on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --instance=INSTANCE + The instance id of the authToken resource. + + To set the instance attribute: + ▸ provide the argument auth_token on the command line with a fully + specified name; + ▸ provide the argument --instance on the command line. + + --location=LOCATION + The location id of the authToken resource. + + To set the location attribute: + ▸ provide the argument auth_token on the command line with a fully + specified name; + ▸ provide the argument --location on the command line. + + --token-auth-user=TOKEN_AUTH_USER + The tokenAuthUser id of the authToken resource. + + To set the token-auth-user attribute: + ▸ provide the argument auth_token on the command line with a fully + specified name; + ▸ provide the argument --token-auth-user 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 memorystore/v1beta API. The full documentation for + this API can be found at: https://cloud.google.com/memorystore/ + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha memorystore instances token-auth-users auth-tokens \ + delete + diff --git a/gcloud/beta/memorystore/instances/token-auth-users/auth-tokens/describe b/gcloud/beta/memorystore/instances/token-auth-users/auth-tokens/describe new file mode 100644 index 000000000..3c2022767 --- /dev/null +++ b/gcloud/beta/memorystore/instances/token-auth-users/auth-tokens/describe @@ -0,0 +1,87 @@ +NAME + gcloud beta memorystore instances token-auth-users auth-tokens describe - + describe authTokens + +SYNOPSIS + gcloud beta memorystore instances token-auth-users auth-tokens describe + (AUTH_TOKEN : --instance=INSTANCE + --location=LOCATION --token-auth-user=TOKEN_AUTH_USER) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Describe an authToken + +EXAMPLES + To describe the authToken, run: + + $ gcloud beta memorystore instances token-auth-users auth-tokens \ + describe + +POSITIONAL ARGUMENTS + AuthToken resource - The name of token auth user for a token auth enabled + instance. Format: + projects/{project}/locations/{location}/instances/{instance}/tokenAuthUsers/{token_auth_user}/authTokens/{auth_token} + 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 auth_token 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. + + AUTH_TOKEN + ID of the authToken or fully qualified identifier for the authToken. + + To set the auth_token attribute: + ▸ provide the argument auth_token on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --instance=INSTANCE + The instance id of the authToken resource. + + To set the instance attribute: + ▸ provide the argument auth_token on the command line with a fully + specified name; + ▸ provide the argument --instance on the command line. + + --location=LOCATION + The location id of the authToken resource. + + To set the location attribute: + ▸ provide the argument auth_token on the command line with a fully + specified name; + ▸ provide the argument --location on the command line. + + --token-auth-user=TOKEN_AUTH_USER + The tokenAuthUser id of the authToken resource. + + To set the token-auth-user attribute: + ▸ provide the argument auth_token on the command line with a fully + specified name; + ▸ provide the argument --token-auth-user 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 memorystore/v1beta API. The full documentation for + this API can be found at: https://cloud.google.com/memorystore/ + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha memorystore instances token-auth-users auth-tokens \ + describe + diff --git a/gcloud/beta/memorystore/instances/token-auth-users/auth-tokens/help b/gcloud/beta/memorystore/instances/token-auth-users/auth-tokens/help new file mode 100644 index 000000000..08e3addb8 --- /dev/null +++ b/gcloud/beta/memorystore/instances/token-auth-users/auth-tokens/help @@ -0,0 +1,34 @@ +NAME + gcloud beta memorystore instances token-auth-users auth-tokens - manage + Auth Token resources + +SYNOPSIS + gcloud beta memorystore instances token-auth-users auth-tokens COMMAND + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Manage Auth Token resources. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + delete + (BETA) Delete authTokens. + + describe + (BETA) Describe authTokens. + + list + (BETA) List authTokens. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha memorystore instances token-auth-users auth-tokens + diff --git a/gcloud/beta/memorystore/instances/token-auth-users/auth-tokens/list b/gcloud/beta/memorystore/instances/token-auth-users/auth-tokens/list new file mode 100644 index 000000000..330a2ef8c --- /dev/null +++ b/gcloud/beta/memorystore/instances/token-auth-users/auth-tokens/list @@ -0,0 +1,111 @@ +NAME + gcloud beta memorystore instances token-auth-users auth-tokens list - list + authTokens + +SYNOPSIS + gcloud beta memorystore instances token-auth-users auth-tokens list + (--token-auth-user=TOKEN_AUTH_USER + : --instance=INSTANCE --location=LOCATION) [--filter=EXPRESSION] + [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) List authTokens + +EXAMPLES + To list all authTokens, run: + + $ gcloud beta memorystore instances token-auth-users auth-tokens list + +REQUIRED FLAGS + TokenAuthUser resource - The parent to list auth tokens from. Format: + projects/{project}/locations/{location}/instances/{instance}/tokenAuthUsers/{token_auth_user} + 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 --token-auth-user 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. + + --token-auth-user=TOKEN_AUTH_USER + ID of the tokenAuthUser or fully qualified identifier for the + tokenAuthUser. + + To set the token-auth-user attribute: + ▸ provide the argument --token-auth-user on the command line. + + This flag argument must be specified if any of the other arguments in + this group are specified. + + --instance=INSTANCE + The instance id of the tokenAuthUser resource. + + To set the instance attribute: + ▸ provide the argument --token-auth-user on the command line with a + fully specified name; + ▸ provide the argument --instance on the command line. + + --location=LOCATION + The location id of the tokenAuthUser resource. + + To set the location attribute: + ▸ provide the argument --token-auth-user 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 memorystore/v1beta API. The full documentation for + this API can be found at: https://cloud.google.com/memorystore/ + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha memorystore instances token-auth-users auth-tokens \ + list + diff --git a/gcloud/beta/memorystore/instances/token-auth-users/create-auth-token b/gcloud/beta/memorystore/instances/token-auth-users/create-auth-token new file mode 100644 index 000000000..800ff1874 --- /dev/null +++ b/gcloud/beta/memorystore/instances/token-auth-users/create-auth-token @@ -0,0 +1,82 @@ +NAME + gcloud beta memorystore instances token-auth-users create-auth-token - + create an auth token for a token auth user + +SYNOPSIS + gcloud beta memorystore instances token-auth-users create-auth-token + (TOKEN_AUTH_USER : --instance=INSTANCE --location=LOCATION) [--async] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) create an auth token for a token auth user + +EXAMPLES + To create an auth token for a token auth user, run: + + $ gcloud beta memorystore instances token-auth-users \ + create-auth-token + +POSITIONAL ARGUMENTS + TokenAuthUser resource - The name of the token auth user resource that + this token will be created for. The arguments in this group can be used to + specify the attributes of this resource. (NOTE) Some attributes are not + given arguments in this group but can be set in other ways. + + To set the project attribute: + ◆ provide the argument token_auth_user 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. + + TOKEN_AUTH_USER + ID of the tokenAuthUser or fully qualified identifier for the + tokenAuthUser. + + To set the token_auth_user attribute: + ▸ provide the argument token_auth_user on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --instance=INSTANCE + The instance id of the tokenAuthUser resource. + + To set the instance attribute: + ▸ provide the argument token_auth_user on the command line with a + fully specified name; + ▸ provide the argument --instance on the command line. + + --location=LOCATION + The location id of the tokenAuthUser resource. + + To set the location attribute: + ▸ provide the argument token_auth_user 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 memorystore/v1beta API. The full documentation for + this API can be found at: https://cloud.google.com/memorystore/ + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha memorystore instances token-auth-users \ + create-auth-token + diff --git a/gcloud/beta/memorystore/instances/token-auth-users/delete b/gcloud/beta/memorystore/instances/token-auth-users/delete new file mode 100644 index 000000000..68f9fb29a --- /dev/null +++ b/gcloud/beta/memorystore/instances/token-auth-users/delete @@ -0,0 +1,102 @@ +NAME + gcloud beta memorystore instances token-auth-users delete - delete + tokenAuthUsers + +SYNOPSIS + gcloud beta memorystore instances token-auth-users delete + (TOKEN_AUTH_USER : --instance=INSTANCE --location=LOCATION) [--async] + [--no-force] [--request-id=REQUEST_ID] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Delete a tokenAuthUser + +EXAMPLES + To delete the tokenAuthUser, run: + + $ gcloud beta memorystore instances token-auth-users delete + +POSITIONAL ARGUMENTS + TokenAuthUser resource - The name of the token auth user to delete. + Format: + projects/{project}/locations/{location}/instances/{instance}/tokenAuthUsers/{token_auth_user} + 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 token_auth_user 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. + + TOKEN_AUTH_USER + ID of the tokenAuthUser or fully qualified identifier for the + tokenAuthUser. + + To set the token_auth_user attribute: + ▸ provide the argument token_auth_user on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --instance=INSTANCE + The instance id of the tokenAuthUser resource. + + To set the instance attribute: + ▸ provide the argument token_auth_user on the command line with a + fully specified name; + ▸ provide the argument --instance on the command line. + + --location=LOCATION + The location id of the tokenAuthUser resource. + + To set the location attribute: + ▸ provide the argument token_auth_user 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. + + --force + If set to true, any auth tokens from this user will also be deleted. + Otherwise, the request will only work if the user has no auth tokens. + Enabled by default, use --no-force 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 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 memorystore/v1beta API. The full documentation for + this API can be found at: https://cloud.google.com/memorystore/ + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha memorystore instances token-auth-users delete + diff --git a/gcloud/beta/memorystore/instances/token-auth-users/describe b/gcloud/beta/memorystore/instances/token-auth-users/describe new file mode 100644 index 000000000..dd57189d1 --- /dev/null +++ b/gcloud/beta/memorystore/instances/token-auth-users/describe @@ -0,0 +1,77 @@ +NAME + gcloud beta memorystore instances token-auth-users describe - describe + tokenAuthUsers + +SYNOPSIS + gcloud beta memorystore instances token-auth-users describe + (TOKEN_AUTH_USER : --instance=INSTANCE --location=LOCATION) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Describe a tokenAuthUser + +EXAMPLES + To describe the tokenAuthUser, run: + + $ gcloud beta memorystore instances token-auth-users describe + +POSITIONAL ARGUMENTS + TokenAuthUser resource - The name of token auth user for a basic auth + enabled instance. Format: + projects/{project}/locations/{location}/instances/{instance}/tokenAuthUsers/{token_auth_user} + 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 token_auth_user 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. + + TOKEN_AUTH_USER + ID of the tokenAuthUser or fully qualified identifier for the + tokenAuthUser. + + To set the token_auth_user attribute: + ▸ provide the argument token_auth_user on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --instance=INSTANCE + The instance id of the tokenAuthUser resource. + + To set the instance attribute: + ▸ provide the argument token_auth_user on the command line with a + fully specified name; + ▸ provide the argument --instance on the command line. + + --location=LOCATION + The location id of the tokenAuthUser resource. + + To set the location attribute: + ▸ provide the argument token_auth_user 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 memorystore/v1beta API. The full documentation for + this API can be found at: https://cloud.google.com/memorystore/ + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha memorystore instances token-auth-users describe + diff --git a/gcloud/beta/memorystore/instances/token-auth-users/help b/gcloud/beta/memorystore/instances/token-auth-users/help new file mode 100644 index 000000000..d1f39e963 --- /dev/null +++ b/gcloud/beta/memorystore/instances/token-auth-users/help @@ -0,0 +1,43 @@ +NAME + gcloud beta memorystore instances token-auth-users - manage Token Auth User + resources + +SYNOPSIS + gcloud beta memorystore instances token-auth-users GROUP | COMMAND + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Manage Token Auth User resources. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +GROUPS + GROUP is one of the following: + + auth-tokens + (BETA) Manage Auth Token resources. + +COMMANDS + COMMAND is one of the following: + + create-auth-token + (BETA) create an auth token for a token auth user. + + delete + (BETA) Delete tokenAuthUsers. + + describe + (BETA) Describe tokenAuthUsers. + + list + (BETA) List tokenAuthUsers. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha memorystore instances token-auth-users + diff --git a/gcloud/beta/memorystore/instances/token-auth-users/list b/gcloud/beta/memorystore/instances/token-auth-users/list new file mode 100644 index 000000000..af0caa776 --- /dev/null +++ b/gcloud/beta/memorystore/instances/token-auth-users/list @@ -0,0 +1,100 @@ +NAME + gcloud beta memorystore instances token-auth-users list - list + tokenAuthUsers + +SYNOPSIS + gcloud beta memorystore instances token-auth-users list + (--instance=INSTANCE : --location=LOCATION) [--filter=EXPRESSION] + [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) List tokenAuthUsers + +EXAMPLES + To list all tokenAuthUsers, run: + + $ gcloud beta memorystore instances token-auth-users list + +REQUIRED FLAGS + Instance resource - The parent to list token auth users from. Format: + projects/{project}/locations/{location}/instances/{instance} 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 --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. + + This flag argument must be specified if any of the other arguments in + this group are specified. + + --location=LOCATION + The location id of the instance resource. + + To set the location attribute: + ▸ provide the argument --instance 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 memorystore/v1beta API. The full documentation for + this API can be found at: https://cloud.google.com/memorystore/ + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha memorystore instances token-auth-users list + diff --git a/gcloud/beta/memorystore/instances/update b/gcloud/beta/memorystore/instances/update index 39e04bb7a..165eb5942 100644 --- a/gcloud/beta/memorystore/instances/update +++ b/gcloud/beta/memorystore/instances/update @@ -5,10 +5,10 @@ NAME SYNOPSIS gcloud beta memorystore instances update INSTANCE [--async] [--[no-]async-instance-endpoints-deletion-enabled] - [--auth-mode=AUTH_MODE] [--[no-]deletion-protection-enabled] - [--engine-version=ENGINE_VERSION] [--location=LOCATION] - [--maintenance-version=MAINTENANCE_VERSION] [--mode=MODE] - [--node-type=NODE_TYPE] [--[no-]ondemand-maintenance] + [--authorization-mode=AUTHORIZATION_MODE] + [--[no-]deletion-protection-enabled] [--engine-version=ENGINE_VERSION] + [--location=LOCATION] [--maintenance-version=MAINTENANCE_VERSION] + [--mode=MODE] [--node-type=NODE_TYPE] [--[no-]ondemand-maintenance] [--replica-count=REPLICA_COUNT] [--request-id=REQUEST_ID] [--[no-]rotate-server-certificate] [--shard-count=SHARD_COUNT] [--[no-]simulate-maintenance-event] @@ -99,8 +99,8 @@ FLAGS --async-instance-endpoints-deletion-enabled to enable and --no-async-instance-endpoints-deletion-enabled to disable. - --auth-mode=AUTH_MODE - Authorization mode of the instance. AUTH_MODE must be one of: + --authorization-mode=AUTHORIZATION_MODE + Authorization mode of the instance. AUTHORIZATION_MODE must be one of: auth-disabled Authorization disabled. @@ -144,12 +144,24 @@ FLAGS Machine type for individual nodes of the instance. NODE_TYPE must be one of: + custom-micro + Custom micro. + custom-mini + Custom mini. + custom-pico + Custom pico. + highcpu-medium + High cpu medium. + highmem-2xlarge + High memory 2xlarge. highmem-medium High memory medium. highmem-xlarge High memory extra large. shared-core-nano Shared core nano. + standard-large + Standard large. standard-small Standard small. diff --git a/gcloud/beta/netapp/backup-vaults/backups/create b/gcloud/beta/netapp/backup-vaults/backups/create index 570e77cbd..52d8d42c7 100644 --- a/gcloud/beta/netapp/backup-vaults/backups/create +++ b/gcloud/beta/netapp/backup-vaults/backups/create @@ -4,10 +4,12 @@ NAME SYNOPSIS gcloud beta netapp backup-vaults backups create - (BACKUP : --location=LOCATION) [--async] [--backup-vault=BACKUP_VAULT] - [--description=DESCRIPTION] [--labels=[KEY=VALUE,...]] - [--source-snapshot=SOURCE_SNAPSHOT] [--source-volume=SOURCE_VOLUME] - [GCLOUD_WIDE_FLAG ...] + (BACKUP : --location=LOCATION) + (--ontap-source=[snapshot-uuid=SNAPSHOT-UUID], + [storage-pool=STORAGE-POOL],[volume-uuid=VOLUME-UUID] + | --source-snapshot=SOURCE_SNAPSHOT --source-volume=SOURCE_VOLUME) + [--async] [--backup-vault=BACKUP_VAULT] [--description=DESCRIPTION] + [--labels=[KEY=VALUE,...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) Create a Cloud NetApp Backup. @@ -57,7 +59,76 @@ POSITIONAL ARGUMENTS ▸ provide the argument --location on the command line; ▸ set the property netapp/location. -FLAGS +REQUIRED FLAGS + Exactly one of these must be specified: + + --ontap-source=[snapshot-uuid=SNAPSHOT-UUID],[storage-pool=STORAGE-POOL],[volume-uuid=VOLUME-UUID] + ONTAP source for the backup. + + It consists of the following fields: + ▸ storage-pool: The storage pool of the source volume. + ▸ volume-uuid: The UUID of the source volume. + ▸ snapshot-uuid: The UUID of the source snapshot (optional). + + Or at least one of these can be specified: + + Snapshot resource - The full name of the Source Snapshot that the + Backup is based on', Format: + projects/{project_id}/locations/{location}/volumes/{volume_id}/snapshots/{snapshot_id} + 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-snapshot 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-snapshot on the command line with a + fully specified name; + ▫ set the property netapp/location. + + To set the volume attribute: + ▫ provide the argument --source-snapshot on the command line with a + fully specified name. + + --source-snapshot=SOURCE_SNAPSHOT + ID of the snapshot or fully qualified identifier for the snapshot. + + To set the snapshot attribute: + ▫ provide the argument --source-snapshot on the command line. + + Volume resource - The full name of the Source Volume that the Backup + is based on', Format: + projects/{projects_id}/locations/{location}/volumes/{volume_id} 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-volume on the command line with a + fully specified name; + ▫ provide the argument --volume 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-volume on the command line with a + fully specified name; + ▫ provide the argument --volume on the command line with a fully + specified name; + ▫ provide the argument --location on the command line; + ▫ set the property netapp/location. + + --source-volume=SOURCE_VOLUME + ID of the volume or fully qualified identifier for the volume. + + To set the volume attribute: + ▫ provide the argument --source-volume on the command line; + ▫ provide the argument --volume on the command line. + +OPTIONAL FLAGS --async Return immediately, without waiting for the operation in progress to complete. @@ -96,62 +167,6 @@ FLAGS contain only hyphens (-), underscores (_), lowercase characters, and numbers. - Snapshot resource - The full name of the Source Snapshot that the Backup - is based on', Format: - projects/{project_id}/locations/{location}/volumes/{volume_id}/snapshots/{snapshot_id} - 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-snapshot 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-snapshot on the command line with a - fully specified name; - ◆ set the property netapp/location. - - To set the volume attribute: - ◆ provide the argument --source-snapshot on the command line with a - fully specified name. - - --source-snapshot=SOURCE_SNAPSHOT - ID of the snapshot or fully qualified identifier for the snapshot. - - To set the snapshot attribute: - ◆ provide the argument --source-snapshot on the command line. - - Volume resource - The full name of the Source Volume that the Backup is - based on', Format: - projects/{projects_id}/locations/{location}/volumes/{volume_id} 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-volume on the command line with a fully - specified name; - ◆ provide the argument --volume 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-volume on the command line with a fully - specified name; - ◆ provide the argument --volume on the command line with a fully - specified name; - ◆ provide the argument --location on the command line; - ◆ set the property netapp/location. - - --source-volume=SOURCE_VOLUME - ID of the volume or fully qualified identifier for the volume. - - To set the volume attribute: - ◆ provide the argument --source-volume on the command line; - ◆ provide the argument --volume on the command line. - GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, diff --git a/gcloud/beta/netapp/backup-vaults/create b/gcloud/beta/netapp/backup-vaults/create index a39ee870c..36bcdaff1 100644 --- a/gcloud/beta/netapp/backup-vaults/create +++ b/gcloud/beta/netapp/backup-vaults/create @@ -11,9 +11,9 @@ SYNOPSIS [manual-backup-immutable=MANUAL-BACKUP-IMMUTABLE], [monthly-backup-immutable=MONTHLY-BACKUP-IMMUTABLE], [weekly-backup-immutable=WEEKLY-BACKUP-IMMUTABLE]] - [--backup-vault-type=BACKUP_VAULT_TYPE] [--description=DESCRIPTION] - [--kms-config=KMS_CONFIG] [--labels=[KEY=VALUE,...]] - [GCLOUD_WIDE_FLAG ...] + [--backup-vault-type=BACKUP_VAULT_TYPE] [--[no-]cross-project-vault] + [--description=DESCRIPTION] [--kms-config=KMS_CONFIG] + [--labels=[KEY=VALUE,...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) Create a Cloud NetApp Backup Vault. @@ -85,6 +85,11 @@ FLAGS String indicating the type of backup vault. The supported values are: 'IN_REGION','CROSS_REGION' + --[no-]cross-project-vault + Indicates whether the backup vault is a cross project vault. Use + --cross-project-vault to enable and --no-cross-project-vault to + disable. + --description=DESCRIPTION A description of the Cloud NetApp Backup Vault diff --git a/gcloud/beta/netapp/storage-pools/create b/gcloud/beta/netapp/storage-pools/create index dc51b29c3..0a6c679f4 100644 --- a/gcloud/beta/netapp/storage-pools/create +++ b/gcloud/beta/netapp/storage-pools/create @@ -14,9 +14,9 @@ SYNOPSIS [--enable-ldap=ENABLE_LDAP] [--hot-tier-size=HOT_TIER_SIZE] [--kms-config=KMS_CONFIG] [--labels=[KEY=VALUE,...]] [--mode=MODE] [--qos-type=QOS_TYPE] [--replica-zone=REPLICA_ZONE] - [--scale-tier=SCALE_TIER] [--total-iops=TOTAL_IOPS] - [--total-throughput=TOTAL_THROUGHPUT] [--type=TYPE] [--zone=ZONE] - [GCLOUD_WIDE_FLAG ...] + [--scale-tier=SCALE_TIER] [--scale-type=SCALE_TYPE] + [--total-iops=TOTAL_IOPS] [--total-throughput=TOTAL_THROUGHPUT] + [--type=TYPE] [--zone=ZONE] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) Creates a Storage Pool to contain Volumes with a specified Service @@ -214,10 +214,17 @@ OPTIONAL FLAGS String indicating replica zone for the Storage Pool --scale-tier=SCALE_TIER - The scale tier of the Storage Pool. standard scale tier is for standard - capacity and performance tier. enterprise scale tier is for higher - capacity and performance tier. SCALE_TIER must be one of: enterprise, - standard. + (DEPRECATED) The scale tier of the Storage Pool. standard scale tier is + for standard capacity and performance tier. enterprise scale tier is + for higher capacity and performance tier. + + The --scale-tier flag is deprecated. Use --scale-type instead. + SCALE_TIER must be one of: enterprise, standard. + + --scale-type=SCALE_TYPE + The scale type of the Storage Pool. default scale type is for standard + capacity and performance. scaleout scale type is for higher capacity + and performance. SCALE_TYPE must be one of: default, scaleout. --total-iops=TOTAL_IOPS Integer indicating total IOPS of the Storage Pool diff --git a/gcloud/beta/netapp/storage-pools/execute b/gcloud/beta/netapp/storage-pools/execute index 2032ee9eb..900f32983 100644 --- a/gcloud/beta/netapp/storage-pools/execute +++ b/gcloud/beta/netapp/storage-pools/execute @@ -54,8 +54,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 netapp storage-pools execute $ gcloud alpha netapp storage-pools execute diff --git a/gcloud/beta/netapp/storage-pools/help b/gcloud/beta/netapp/storage-pools/help index abea122a9..4bcde7319 100644 --- a/gcloud/beta/netapp/storage-pools/help +++ b/gcloud/beta/netapp/storage-pools/help @@ -31,12 +31,24 @@ COMMANDS list (BETA) List Cloud NetApp Storage Pools. + list-backup-configs + (BETA) A command to list backup configurations for all volumes in an + ONTAP-mode Storage Pool. + + restore-volume + (BETA) Restores a backup to a volume in a specified ONTAP-mode Storage + Pool. + switch (BETA) Switch a Regional Cloud NetApp Flex Storage Pool zone. update (BETA) Update a Cloud NetApp Storage Pool. + update-backup-config + (BETA) A command to update backup config of a volume in an ONTAP-mode + Storage Pool. + validate-directory-service (BETA) Validate directory service for a Cloud Netapp storage pool. diff --git a/gcloud/beta/netapp/storage-pools/list-backup-configs b/gcloud/beta/netapp/storage-pools/list-backup-configs new file mode 100644 index 000000000..75417a603 --- /dev/null +++ b/gcloud/beta/netapp/storage-pools/list-backup-configs @@ -0,0 +1,100 @@ +NAME + gcloud beta netapp storage-pools list-backup-configs - a command to list + backup configurations for all volumes in an ONTAP-mode Storage Pool + +SYNOPSIS + gcloud beta netapp storage-pools list-backup-configs + (STORAGE_POOL : --location=LOCATION) [--filter=EXPRESSION] + [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Lists backup configurations for all volumes in an ONTAP-mode Storage + Pool. + +EXAMPLES + The following command lists backup configurations in Storage Pool named + NAME in location us-central1: + + $ gcloud beta netapp storage-pools list-backup-configs NAME \ + --location=us-central1 + +POSITIONAL ARGUMENTS + Storage pool resource - The Storage Pool to list backup configs for. The + arguments in this group can be used to specify the attributes of this + resource. (NOTE) Some attributes are not given arguments in this group but + can be set in other ways. + + To set the project attribute: + ◆ provide the argument storage_pool on the command line with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + STORAGE_POOL + ID of the storage_pool or fully qualified identifier for the + storage_pool. + + To set the storage_pool attribute: + ▸ provide the argument storage_pool 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 of the storage_pool. + + To set the location attribute: + ▸ provide the argument storage_pool on the command line with a + fully specified name; + ▸ provide the argument --location on the command line; + ▸ set the property netapp/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. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha netapp storage-pools list-backup-configs + diff --git a/gcloud/beta/netapp/storage-pools/restore-volume b/gcloud/beta/netapp/storage-pools/restore-volume new file mode 100644 index 000000000..f6da3b533 --- /dev/null +++ b/gcloud/beta/netapp/storage-pools/restore-volume @@ -0,0 +1,153 @@ +NAME + gcloud beta netapp storage-pools restore-volume - restores a backup to a + volume in a specified ONTAP-mode Storage Pool + +SYNOPSIS + gcloud beta netapp storage-pools restore-volume + (STORAGE_POOL : --location=LOCATION) --volume-uuid=VOLUME_UUID + (--backup=BACKUP : --backup_vault=BACKUP_VAULT) [--async] + [--file-list=[FILE_LIST,...]] + [--restore-destination-path=RESTORE_DESTINATION_PATH] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Restores a backup to a volume within the specified Storage Pool. + + This command supports both full backup restore and selective file restore: + + Full Backup Restore: The --volume-uuid must reference a Data Protection + (DP) volume where the backup will be restored. + + File Restore: The --volume-uuid must reference a Read-Write (RW) volume + where the file(s) from the backup will be restored. For file restore, + --file-list and --restore-destination-path must be included in the request + payload. + + For the complete backup restore, users should first create a Data + Protection volume via the ONTAP Mode APIs whereas a Read-Write volume must + be created first for selective file restore. + +EXAMPLES + The following command restores full backup from a backup with full resource + name + projects/my-project/locations/us-central1/backupVaults/my-vault/backups/backup-1 + to an ONTAP-mode volume with UUID 5dc61a44-3d99-11f1-b8ff-39021cc41d7a in + Storage Pool named NAME. + + $ gcloud beta netapp storage-pools restore-volume NAME \ + --location=us-central1 \ + --backup=projects/my-project/locations/us-central1/\ + backupVaults/my-vault/backups/backup-1 \ + --volume-uuid=5dc61a44-3d99-11f1-b8ff-39021cc41d7a + + The following command restores file1.txt from the same backup to an + ONTAP-mode volume with UUID 5dc61a44-3d99-11f1-b8ff-39021cc41d7a in Storage + Pool named NAME to the directory /my_restore_destination. + + $ gcloud beta netapp storage-pools restore-volume NAME \ + --location=us-central1 \ + --backup=projects/my-project/locations/us-central1/\ + backupVaults/my-vault/backups/backup-1 \ + --volume-uuid=5dc61a44-3d99-11f1-b8ff-39021cc41d7a \ + --file-list=/path/to/file1.txt \ + --restore-destination-path=/my_restore_destination + +POSITIONAL ARGUMENTS + Storage pool resource - The Storage Pool to restore into. 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 storage_pool on the command line with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + STORAGE_POOL + ID of the storage_pool or fully qualified identifier for the + storage_pool. + + To set the storage_pool attribute: + ▸ provide the argument storage_pool 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 of the storage_pool. + + To set the location attribute: + ▸ provide the argument storage_pool on the command line with a + fully specified name; + ▸ provide the argument --location on the command line; + ▸ set the property netapp/location. + +REQUIRED FLAGS + --volume-uuid=VOLUME_UUID + The UUID of the ONTAP-mode volume to restore to. + + Backup resource - The Backup from which files are restored back to the + Volume. 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 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 --backup on the command line with a fully + specified name; + ◆ set the property netapp/location. + + This must be specified. + + --backup=BACKUP + ID of the backup or fully qualified identifier for the backup. + + To set the backup attribute: + ▸ provide the argument --backup on the command line. + + This flag argument must be specified if any of the other arguments in + this group are specified. + + --backup_vault=BACKUP_VAULT + The Backup Vault of the backup. + + To set the backup_vault attribute: + ▸ provide the argument --backup on the command line with a fully + specified name; + ▸ provide the argument --backup_vault on the command line; + ▸ provide the argument --backup-vault on the command line. + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --file-list=[FILE_LIST,...] + List of files to be restored in the form of their absolute path as in + source volume. + + --restore-destination-path=RESTORE_DESTINATION_PATH + Name of the absolute directory path in the destination volume. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --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 netapp storage-pools restore-volume + diff --git a/gcloud/beta/netapp/storage-pools/update-backup-config b/gcloud/beta/netapp/storage-pools/update-backup-config new file mode 100644 index 000000000..b09c46508 --- /dev/null +++ b/gcloud/beta/netapp/storage-pools/update-backup-config @@ -0,0 +1,97 @@ +NAME + gcloud beta netapp storage-pools update-backup-config - a command to update + backup config of a volume in an ONTAP-mode Storage Pool + +SYNOPSIS + gcloud beta netapp storage-pools update-backup-config + (STORAGE_POOL : --location=LOCATION) + --backup-config=[backup-policies=BACKUP-POLICIES], + [backup-vault=BACKUP-VAULT], + [enable-scheduled-backups=ENABLE-SCHEDULED-BACKUPS] + --volume-uuid=VOLUME_UUID [--async] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Updates the backup configuration of a volume within the specified + Storage Pool. + +EXAMPLES + The following command updates the backup configuration of a volume with + UUID 5dc61a44-3d99-11f1-b8ff-39021cc41d7a in an ONTAP-mode Storage Pool + named NAME. + + $ gcloud beta netapp storage-pools update-backup-config NAME \ + --location=us-central1 \ + --volume-uuid=5dc61a44-3d99-11f1-b8ff-39021cc41d7a \ + --backup-config=backup-vault=my-vault,\ + enable-scheduled-backups=true + +POSITIONAL ARGUMENTS + Storage pool resource - The Storage Pool. 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 storage_pool on the command line with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + STORAGE_POOL + ID of the storage_pool or fully qualified identifier for the + storage_pool. + + To set the storage_pool attribute: + ▸ provide the argument storage_pool 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 of the storage_pool. + + To set the location attribute: + ▸ provide the argument storage_pool on the command line with a + fully specified name; + ▸ provide the argument --location on the command line; + ▸ set the property netapp/location. + +REQUIRED FLAGS + --backup-config=[backup-policies=BACKUP-POLICIES],[backup-vault=BACKUP-VAULT],[enable-scheduled-backups=ENABLE-SCHEDULED-BACKUPS] + Backup Config contains backup related config on a volume in ONTAP-mode + Storage Pool. + + Backup Config will have the following format + --backup-config=backup-policies=BACKUP_POLICIES, + backup-vault=BACKUP_VAULT_NAME, + enable-scheduled-backups=ENABLE_SCHEDULED_BACKUPS + + backup-policies is a pound-separated (#) list of backup policy names, + backup-vault can include a single backup-vault resource name, and + enable-scheduled-backups is a Boolean value indicating whether or not + scheduled backups are enabled on the volume in the ONTAP-mode Storage + Pool. + + --volume-uuid=VOLUME_UUID + The UUID of the volume to update backup config for. + +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. This + variant is also available: + + $ gcloud alpha netapp storage-pools update-backup-config + diff --git a/gcloud/beta/network-connectivity/spokes/linked-producer-vpc-network/create b/gcloud/beta/network-connectivity/spokes/linked-producer-vpc-network/create index 8de43d06c..35b78ea35 100644 --- a/gcloud/beta/network-connectivity/spokes/linked-producer-vpc-network/create +++ b/gcloud/beta/network-connectivity/spokes/linked-producer-vpc-network/create @@ -6,7 +6,7 @@ SYNOPSIS gcloud beta network-connectivity spokes linked-producer-vpc-network create SPOKE --hub=HUB --network=NETWORK --peering=PEERING [--async] [--description=DESCRIPTION] [--exclude-export-ranges=[CIDR_RANGE,...]] - [--global] [--include-export-ranges=[CIDR_RANGE,...]] + [--global] [--group=GROUP] [--include-export-ranges=[CIDR_RANGE,...]] [--labels=[KEY=VALUE,...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -75,6 +75,9 @@ OPTIONAL FLAGS --global Indicates that the spoke is global. + --group=GROUP + Group that the spoke will be part of. The group must already exist. + --include-export-ranges=[CIDR_RANGE,...] Subnet IP address range(s) to export to other VPC networks that are connected through Network Connectivity Center. diff --git a/gcloud/beta/network-connectivity/spokes/linked-vpc-network/create b/gcloud/beta/network-connectivity/spokes/linked-vpc-network/create index 79972f327..5a9059cda 100644 --- a/gcloud/beta/network-connectivity/spokes/linked-vpc-network/create +++ b/gcloud/beta/network-connectivity/spokes/linked-vpc-network/create @@ -6,7 +6,7 @@ SYNOPSIS gcloud beta network-connectivity spokes linked-vpc-network create SPOKE --hub=HUB --vpc-network=VPC_NETWORK [--async] [--description=DESCRIPTION] [--exclude-export-ranges=[CIDR_RANGE,...]] - [--global] [--include-export-ranges=[CIDR_RANGE,...]] + [--global] [--group=GROUP] [--include-export-ranges=[CIDR_RANGE,...]] [--labels=[KEY=VALUE,...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -69,6 +69,9 @@ OPTIONAL FLAGS --global Indicates that the spoke is global. + --group=GROUP + Group that the spoke will be part of. The group must already exist. + --include-export-ranges=[CIDR_RANGE,...] Subnet IP address range(s) to export to other VPC networks that are connected through Network Connectivity Center. diff --git a/gcloud/beta/network-connectivity/transports/create b/gcloud/beta/network-connectivity/transports/create index 85dd71fed..f34c04f27 100644 --- a/gcloud/beta/network-connectivity/transports/create +++ b/gcloud/beta/network-connectivity/transports/create @@ -6,10 +6,11 @@ SYNOPSIS (--activation-key=ACTIVATION_KEY | --bandwidth=BANDWIDTH --remote-account-id=REMOTE_ACCOUNT_ID --remote-profile=REMOTE_PROFILE) - [--advertised-routes=[CIDR_RANGE,...]] [--async] [--auto-accept] - [--description=DESCRIPTION] [--no-enable-admin] [--hub=HUB] - [--labels=[KEY=VALUE,...]] [--network=NETWORK] [--psc-routing-enabled] - [--region=REGION] [--stack-type=STACK_TYPE] [GCLOUD_WIDE_FLAG ...] + (--network=NETWORK | [--hub=HUB : --auto-accept --psc-routing-enabled]) + [--advertised-routes=[CIDR_RANGE,...]] [--async] + [--description=DESCRIPTION] [--no-enable-admin] + [--labels=[KEY=VALUE,...]] [--region=REGION] + [--stack-type=STACK_TYPE; default="ipv4-only"] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) Create a transport with the given name to a remote provider. @@ -27,11 +28,13 @@ EXAMPLES $ gcloud beta network-connectivity transports create my-cci-aws \ --activation-key ABC1234 --network default - To create a transport using NCC Hubs to aws-us-east-1. + To create a transport with an NCC hub: $ gcloud beta network-connectivity transports create my-cci-aws \ - --bandwidth 1G --remote-profile aws-us-east-1 \ - --remote-account-id 12345 --hub my-hub --auto-accept + --bandwidth 1G --profile aws-us-east-1 \ + --remote-account-id 12345 \ + --hub projects/12345/locations/us-central1/hubs/my-hub \ + --auto-accept POSITIONAL ARGUMENTS Transport resource - Name of the Transport to be created. This represents @@ -109,6 +112,50 @@ REQUIRED FLAGS To set the remote_transport_profile attribute: ◇ provide the argument --remote-profile on the command line. + Exactly one of these must be specified: + + Network resource - VPC that will be peered to the provider via the + Transport. This represents a Cloud resource. (NOTE) Some attributes are + not given arguments in this group but can be set in other ways. + + To set the project attribute: + ▸ provide the argument --network on the command line with a fully + specified name; + ▸ provide the argument --project on the command line; + ▸ set the property core/project. + + --network=NETWORK + ID of the network or fully qualified identifier for the network. + + To set the network attribute: + ▸ provide the argument --network on the command line. + + Parameters for creating a transport with an NCC hub. + + Hub resource - Hub that the transport will be attached 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 --hub 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. + + --hub=HUB + ID of the hub or fully qualified identifier for the hub. + + To set the hub attribute: + ▫ provide the argument --hub on the command line. + + --auto-accept + Whether to auto-accept spoke proposals for this transport. + + --psc-routing-enabled + Whether a VPC spoke is created for PSC routing over the transport. + OPTIONAL FLAGS --advertised-routes=[CIDR_RANGE,...] List of routes to advertise from the VPC network toward the provider. @@ -117,9 +164,6 @@ OPTIONAL FLAGS Return immediately, without waiting for the operation in progress to complete. - --auto-accept - Whether to auto-accept NCC proposals. - --description=DESCRIPTION Description of the transport. @@ -127,22 +171,6 @@ OPTIONAL FLAGS Administrative state of the underlying connectivity. Enabled by default, use --no-enable-admin to disable. - Hub resource - Hub that the transport will be attached 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 --hub on the command line with a fully specified - name; - ◆ provide the argument --project on the command line; - ◆ set the property core/project. - - --hub=HUB - ID of the hub or fully qualified identifier for the hub. - - To set the hub attribute: - ◆ provide the argument --hub on the command line. - --labels=[KEY=VALUE,...] List of label KEY=VALUE pairs to add. @@ -151,31 +179,12 @@ OPTIONAL FLAGS contain only hyphens (-), underscores (_), lowercase characters, and numbers. - Network resource - VPC that will be peered to the provider via the - Transport. This represents a Cloud resource. (NOTE) Some attributes are - not given arguments in this group but can be set in other ways. - - To set the project attribute: - ◆ provide the argument --network on the command line with a fully - specified name; - ◆ provide the argument --project on the command line; - ◆ set the property core/project. - - --network=NETWORK - ID of the network or fully qualified identifier for the network. - - To set the network attribute: - ◆ provide the argument --network on the command line. - - --psc-routing-enabled - Whether PSC routing is enabled for the transport. - --region=REGION For resources [transport, remote-profile], provides fallback value for resource region attribute. When the resource's full URI path is not provided, region will fallback to this flag value. - --stack-type=STACK_TYPE + --stack-type=STACK_TYPE; default="ipv4-only" IP version of the routes to be exchanged. STACK_TYPE must be one of: ipv4-ipv6, ipv4-only. @@ -193,5 +202,8 @@ API REFERENCE https://cloud.google.com/network-connectivity/docs/reference/networkconnectivity/rest NOTES - This command is currently in beta and might change without notice. + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud network-connectivity transports create diff --git a/gcloud/beta/network-connectivity/transports/delete b/gcloud/beta/network-connectivity/transports/delete index 58cc5133b..0a23a14fb 100644 --- a/gcloud/beta/network-connectivity/transports/delete +++ b/gcloud/beta/network-connectivity/transports/delete @@ -64,5 +64,8 @@ API REFERENCE https://cloud.google.com/network-connectivity/docs/reference/networkconnectivity/rest NOTES - This command is currently in beta and might change without notice. + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud network-connectivity transports delete diff --git a/gcloud/beta/network-connectivity/transports/describe b/gcloud/beta/network-connectivity/transports/describe index c8fbd9f33..7a7dfc957 100644 --- a/gcloud/beta/network-connectivity/transports/describe +++ b/gcloud/beta/network-connectivity/transports/describe @@ -60,5 +60,8 @@ API REFERENCE https://cloud.google.com/network-connectivity/docs/reference/networkconnectivity/rest NOTES - This command is currently in beta and might change without notice. + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud network-connectivity transports describe diff --git a/gcloud/beta/network-connectivity/transports/help b/gcloud/beta/network-connectivity/transports/help index f926632fb..f9df4323a 100644 --- a/gcloud/beta/network-connectivity/transports/help +++ b/gcloud/beta/network-connectivity/transports/help @@ -39,5 +39,8 @@ COMMANDS (BETA) Update a transport. NOTES - This command is currently in beta and might change without notice. + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud network-connectivity transports diff --git a/gcloud/beta/network-connectivity/transports/list b/gcloud/beta/network-connectivity/transports/list index 896573c43..37d24a8f8 100644 --- a/gcloud/beta/network-connectivity/transports/list +++ b/gcloud/beta/network-connectivity/transports/list @@ -71,5 +71,8 @@ API REFERENCE https://cloud.google.com/network-connectivity/docs/reference/networkconnectivity/rest NOTES - This command is currently in beta and might change without notice. + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud network-connectivity transports list diff --git a/gcloud/beta/network-connectivity/transports/remote-profiles/describe b/gcloud/beta/network-connectivity/transports/remote-profiles/describe index a12cacab3..ecfc56fae 100644 --- a/gcloud/beta/network-connectivity/transports/remote-profiles/describe +++ b/gcloud/beta/network-connectivity/transports/remote-profiles/describe @@ -63,5 +63,8 @@ API REFERENCE https://cloud.google.com/network-connectivity/docs/reference/networkconnectivity/rest NOTES - This command is currently in beta and might change without notice. + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud network-connectivity transports remote-profiles describe diff --git a/gcloud/beta/network-connectivity/transports/remote-profiles/help b/gcloud/beta/network-connectivity/transports/remote-profiles/help index e73789056..a154ca4e2 100644 --- a/gcloud/beta/network-connectivity/transports/remote-profiles/help +++ b/gcloud/beta/network-connectivity/transports/remote-profiles/help @@ -24,5 +24,8 @@ COMMANDS (BETA) List remote transport profiles. NOTES - This command is currently in beta and might change without notice. + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud network-connectivity transports remote-profiles diff --git a/gcloud/beta/network-connectivity/transports/remote-profiles/list b/gcloud/beta/network-connectivity/transports/remote-profiles/list index 6096c5d42..e6993e644 100644 --- a/gcloud/beta/network-connectivity/transports/remote-profiles/list +++ b/gcloud/beta/network-connectivity/transports/remote-profiles/list @@ -73,5 +73,8 @@ API REFERENCE https://cloud.google.com/network-connectivity/docs/reference/networkconnectivity/rest NOTES - This command is currently in beta and might change without notice. + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud network-connectivity transports remote-profiles list diff --git a/gcloud/beta/network-connectivity/transports/update b/gcloud/beta/network-connectivity/transports/update index b4fcbdb52..c75bbcb64 100644 --- a/gcloud/beta/network-connectivity/transports/update +++ b/gcloud/beta/network-connectivity/transports/update @@ -112,5 +112,8 @@ API REFERENCE https://cloud.google.com/network-connectivity/docs/reference/networkconnectivity/rest NOTES - This command is currently in beta and might change without notice. + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud network-connectivity transports update diff --git a/gcloud/beta/network-security/firewall-endpoint-associations/create b/gcloud/beta/network-security/firewall-endpoint-associations/create index fb70adc54..bb715e1a5 100644 --- a/gcloud/beta/network-security/firewall-endpoint-associations/create +++ b/gcloud/beta/network-security/firewall-endpoint-associations/create @@ -4,11 +4,11 @@ NAME SYNOPSIS gcloud beta network-security firewall-endpoint-associations create - [ASSOCIATION_ID] --network=NETWORK --zone=ZONE - (--endpoint=ENDPOINT - : --endpoint-zone=ENDPOINT_ZONE --organization=ORGANIZATION) - [--async] [--labels=[KEY=VALUE,...]] - [--max-wait=MAX_WAIT; default="60m"] + [ASSOCIATION_ID] --network=NETWORK + (--endpoint=ENDPOINT : --endpoint-project=ENDPOINT_PROJECT + --endpoint-zone=ENDPOINT_ZONE --organization=ORGANIZATION) + (--location=LOCATION | --zone=ZONE) [--async] + [--labels=[KEY=VALUE,...]] [--max-wait=MAX_WAIT; default="60m"] [--tls-inspection-policy=TLS_INSPECTION_POLICY : --tls-inspection-policy-project=TLS_INSPECTION_POLICY_PROJECT --tls-inspection-policy-region=TLS_INSPECTION_POLICY_REGION] @@ -55,12 +55,11 @@ REQUIRED FLAGS To set the network-name attribute: ▸ provide the argument --network on the command line. - --zone=ZONE - Zone of a firewall endpoint association - Firewall endpoint resource - Firewall Plus. The arguments in this group can be used to specify the attributes of this resource. This resource can - be one of the following types: [firewall endpoint]. + be one of the following types: + [networksecurity.organizations.locations.firewallEndpoints, + networksecurity.projects.locations.firewallEndpoints]. This must be specified. @@ -74,6 +73,18 @@ REQUIRED FLAGS This flag argument must be specified if any of the other arguments in this group are specified. + --endpoint-project=ENDPOINT_PROJECT + Project ID of the firewall endpoint. + + To set the endpoint-project attribute: + ▸ provide the argument --endpoint on the command line with a fully + specified name; + ▸ provide the argument --endpoint-project on the command line; + ▸ set the property core/project; + ▸ provide the argument FIREWALL_ENDPOINT_ASSOCIATION on the command + line with a fully specified name. Must be specified for resource of + type [networksecurity.projects.locations.firewallEndpoints]. + --endpoint-zone=ENDPOINT_ZONE Zone of the firewall endpoint. @@ -82,6 +93,7 @@ REQUIRED FLAGS specified name; ▸ provide the argument --endpoint-zone on the command line; ▸ provide the argument --zone on the command line; + ▸ provide the argument --location on the command line; ▸ provide the argument FIREWALL_ENDPOINT_ASSOCIATION on the command line with a fully specified name. @@ -91,7 +103,17 @@ REQUIRED FLAGS To set the organization attribute: ▸ provide the argument --endpoint on the command line with a fully specified name; - ▸ provide the argument --organization on the command line. + ▸ provide the argument --organization on the command line. Must be + specified for resource of type + [networksecurity.organizations.locations.firewallEndpoints]. + + Exactly one of these must be specified: + + --location=LOCATION + Location of the firewall endpoint association + + --zone=ZONE + Zone of the firewall endpoint association OPTIONAL FLAGS --async diff --git a/gcloud/beta/network-security/firewall-endpoint-associations/delete b/gcloud/beta/network-security/firewall-endpoint-associations/delete index c58532841..a2736d0a0 100644 --- a/gcloud/beta/network-security/firewall-endpoint-associations/delete +++ b/gcloud/beta/network-security/firewall-endpoint-associations/delete @@ -5,7 +5,8 @@ NAME SYNOPSIS gcloud beta network-security firewall-endpoint-associations delete (FIREWALL_ENDPOINT_ASSOCIATION : --zone=ZONE) [--async] - [--max-wait=MAX_WAIT; default="60m"] [GCLOUD_WIDE_FLAG ...] + [--location=LOCATION] [--max-wait=MAX_WAIT; default="60m"] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) Unassociate the specified network from a firewall endpoint. Check @@ -55,7 +56,8 @@ POSITIONAL ARGUMENTS To set the zone attribute: ▸ provide the argument FIREWALL_ENDPOINT_ASSOCIATION on the command line with a fully specified name; - ▸ provide the argument --zone on the command line. + ▸ provide the argument --zone on the command line; + ▸ provide the argument --location on the command line. FLAGS --async @@ -63,6 +65,9 @@ FLAGS complete. The default is True. Enabled by default, use --no-async to disable. + --location=LOCATION + Location of the firewall endpoint association + --max-wait=MAX_WAIT; default="60m" Time to synchronously wait for the operation to complete, after which the operation continues asynchronously. Ignored if --no-async isn't diff --git a/gcloud/beta/network-security/firewall-endpoint-associations/describe b/gcloud/beta/network-security/firewall-endpoint-associations/describe index 724c4694c..be1dd7ea2 100644 --- a/gcloud/beta/network-security/firewall-endpoint-associations/describe +++ b/gcloud/beta/network-security/firewall-endpoint-associations/describe @@ -4,7 +4,8 @@ NAME SYNOPSIS gcloud beta network-security firewall-endpoint-associations describe - (FIREWALL_ENDPOINT_ASSOCIATION : --zone=ZONE) [GCLOUD_WIDE_FLAG ...] + (FIREWALL_ENDPOINT_ASSOCIATION : --zone=ZONE) [--location=LOCATION] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) Describe a firewall endpoint association. @@ -54,7 +55,12 @@ POSITIONAL ARGUMENTS To set the zone attribute: ▸ provide the argument FIREWALL_ENDPOINT_ASSOCIATION on the command line with a fully specified name; - ▸ provide the argument --zone on the command line. + ▸ provide the argument --zone on the command line; + ▸ provide the argument --location on the command line. + +FLAGS + --location=LOCATION + Location of the firewall endpoint association GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/beta/network-security/firewall-endpoint-associations/list b/gcloud/beta/network-security/firewall-endpoint-associations/list index eb9f5af88..681e2f4ff 100644 --- a/gcloud/beta/network-security/firewall-endpoint-associations/list +++ b/gcloud/beta/network-security/firewall-endpoint-associations/list @@ -4,8 +4,8 @@ NAME SYNOPSIS gcloud beta network-security firewall-endpoint-associations list - [--zone=ZONE; default="-"] [--filter=EXPRESSION] [--limit=LIMIT] - [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [--location=LOCATION | --zone=ZONE] [--filter=EXPRESSION] + [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -28,8 +28,13 @@ EXAMPLES defined. FLAGS - --zone=ZONE; default="-" - Zone for the list operation + At most one of these can be specified: + + --location=LOCATION + Location of the firewall endpoint association + + --zone=ZONE + Zone of the firewall endpoint association LIST COMMAND FLAGS --filter=EXPRESSION diff --git a/gcloud/beta/network-security/firewall-endpoint-associations/update b/gcloud/beta/network-security/firewall-endpoint-associations/update index 6d40f474f..d63fe7a40 100644 --- a/gcloud/beta/network-security/firewall-endpoint-associations/update +++ b/gcloud/beta/network-security/firewall-endpoint-associations/update @@ -5,7 +5,7 @@ NAME SYNOPSIS gcloud beta network-security firewall-endpoint-associations update (FIREWALL_ENDPOINT_ASSOCIATION : --zone=ZONE) [--async] - [--max-wait=MAX_WAIT; default="60m"] + [--location=LOCATION] [--max-wait=MAX_WAIT; default="60m"] [--disabled | --update-labels=[KEY=VALUE,...] --clear-labels | --remove-labels=[KEY,...] --no-tls-inspection-policy | [--tls-inspection-policy=TLS_INSPECTION_POLICY @@ -70,7 +70,8 @@ POSITIONAL ARGUMENTS To set the zone attribute: ▸ provide the argument FIREWALL_ENDPOINT_ASSOCIATION on the command line with a fully specified name; - ▸ provide the argument --zone on the command line. + ▸ provide the argument --zone on the command line; + ▸ provide the argument --location on the command line. FLAGS --async @@ -78,6 +79,9 @@ FLAGS complete. The default is True. Enabled by default, use --no-async to disable. + --location=LOCATION + Location of the firewall endpoint association + --max-wait=MAX_WAIT; default="60m" Time to synchronously wait for the operation to complete, after which the operation continues asynchronously. Ignored if --no-async isn't diff --git a/gcloud/beta/network-security/firewall-endpoints/create b/gcloud/beta/network-security/firewall-endpoints/create index 08b1b102e..1df125a97 100644 --- a/gcloud/beta/network-security/firewall-endpoints/create +++ b/gcloud/beta/network-security/firewall-endpoints/create @@ -7,7 +7,8 @@ SYNOPSIS (FIREWALL_ENDPOINT : --organization=ORGANIZATION --zone=ZONE) [--async] [--billing-project=BILLING_PROJECT] [--description=DESCRIPTION] [--enable-jumbo-frames] [--labels=[KEY=VALUE,...]] - [--max-wait=MAX_WAIT; default="60m"] [GCLOUD_WIDE_FLAG ...] + [--location=LOCATION] [--max-wait=MAX_WAIT; default="60m"] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) Create a firewall endpoint. Successful creation of an endpoint @@ -25,8 +26,17 @@ EXAMPLES POSITIONAL ARGUMENTS Firewall endpoint resource - Firewall Plus. The arguments in this group - can be used to specify the attributes of this resource. This resource can - be one of the following types: [firewall endpoint]. + 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 FIREWALL_ENDPOINT on the command line with a + fully specified name; + ◆ set the property core/project. This resource can be one of the + following types: + [networksecurity.organizations.locations.firewallEndpoints, + networksecurity.projects.locations.firewallEndpoints]. This must be specified. @@ -46,7 +56,9 @@ POSITIONAL ARGUMENTS To set the organization attribute: ▸ provide the argument FIREWALL_ENDPOINT on the command line with a fully specified name; - ▸ provide the argument --organization on the command line. + ▸ provide the argument --organization on the command line. Must be + specified for resource of type + [networksecurity.organizations.locations.firewallEndpoints]. --zone=ZONE Zone of the firewall endpoint. @@ -54,7 +66,8 @@ POSITIONAL ARGUMENTS To set the zone attribute: ▸ provide the argument FIREWALL_ENDPOINT on the command line with a fully specified name; - ▸ provide the argument --zone on the command line. + ▸ provide the argument --zone on the command line; + ▸ provide the argument --location on the command line. FLAGS --async @@ -82,6 +95,9 @@ FLAGS contain only hyphens (-), underscores (_), lowercase characters, and numbers. + --location=LOCATION + Location of the endpoint + --max-wait=MAX_WAIT; default="60m" Time to synchronously wait for the operation to complete, after which the operation continues asynchronously. Ignored if --no-async isn't diff --git a/gcloud/beta/network-security/firewall-endpoints/delete b/gcloud/beta/network-security/firewall-endpoints/delete index 18f6b0d5c..633961df0 100644 --- a/gcloud/beta/network-security/firewall-endpoints/delete +++ b/gcloud/beta/network-security/firewall-endpoints/delete @@ -5,7 +5,8 @@ NAME SYNOPSIS gcloud beta network-security firewall-endpoints delete (FIREWALL_ENDPOINT : --organization=ORGANIZATION --zone=ZONE) [--async] - [--max-wait=MAX_WAIT; default="60m"] [GCLOUD_WIDE_FLAG ...] + [--location=LOCATION] [--max-wait=MAX_WAIT; default="60m"] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) Delete a firewall endpoint. Check the progress of endpoint deletion @@ -28,8 +29,17 @@ EXAMPLES POSITIONAL ARGUMENTS Firewall endpoint resource - Firewall Plus. The arguments in this group - can be used to specify the attributes of this resource. This resource can - be one of the following types: [firewall endpoint]. + 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 FIREWALL_ENDPOINT on the command line with a + fully specified name; + ◆ set the property core/project. This resource can be one of the + following types: + [networksecurity.organizations.locations.firewallEndpoints, + networksecurity.projects.locations.firewallEndpoints]. This must be specified. @@ -49,7 +59,9 @@ POSITIONAL ARGUMENTS To set the organization attribute: ▸ provide the argument FIREWALL_ENDPOINT on the command line with a fully specified name; - ▸ provide the argument --organization on the command line. + ▸ provide the argument --organization on the command line. Must be + specified for resource of type + [networksecurity.organizations.locations.firewallEndpoints]. --zone=ZONE Zone of the firewall endpoint. @@ -57,7 +69,8 @@ POSITIONAL ARGUMENTS To set the zone attribute: ▸ provide the argument FIREWALL_ENDPOINT on the command line with a fully specified name; - ▸ provide the argument --zone on the command line. + ▸ provide the argument --zone on the command line; + ▸ provide the argument --location on the command line. FLAGS --async @@ -65,6 +78,9 @@ FLAGS complete. The default is True. Enabled by default, use --no-async to disable. + --location=LOCATION + Location of the endpoint + --max-wait=MAX_WAIT; default="60m" Time to synchronously wait for the operation to complete, after which the operation continues asynchronously. Ignored if --no-async isn't diff --git a/gcloud/beta/network-security/firewall-endpoints/describe b/gcloud/beta/network-security/firewall-endpoints/describe index b49316f61..fb30842fd 100644 --- a/gcloud/beta/network-security/firewall-endpoints/describe +++ b/gcloud/beta/network-security/firewall-endpoints/describe @@ -5,7 +5,7 @@ NAME SYNOPSIS gcloud beta network-security firewall-endpoints describe (FIREWALL_ENDPOINT : --organization=ORGANIZATION --zone=ZONE) - [GCLOUD_WIDE_FLAG ...] + [--location=LOCATION] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) Describe a firewall endpoint. @@ -27,8 +27,17 @@ EXAMPLES POSITIONAL ARGUMENTS Firewall endpoint resource - Firewall Plus. The arguments in this group - can be used to specify the attributes of this resource. This resource can - be one of the following types: [firewall endpoint]. + 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 FIREWALL_ENDPOINT on the command line with a + fully specified name; + ◆ set the property core/project. This resource can be one of the + following types: + [networksecurity.organizations.locations.firewallEndpoints, + networksecurity.projects.locations.firewallEndpoints]. This must be specified. @@ -48,7 +57,9 @@ POSITIONAL ARGUMENTS To set the organization attribute: ▸ provide the argument FIREWALL_ENDPOINT on the command line with a fully specified name; - ▸ provide the argument --organization on the command line. + ▸ provide the argument --organization on the command line. Must be + specified for resource of type + [networksecurity.organizations.locations.firewallEndpoints]. --zone=ZONE Zone of the firewall endpoint. @@ -56,7 +67,12 @@ POSITIONAL ARGUMENTS To set the zone attribute: ▸ provide the argument FIREWALL_ENDPOINT on the command line with a fully specified name; - ▸ provide the argument --zone on the command line. + ▸ provide the argument --zone on the command line; + ▸ provide the argument --location on the command line. + +FLAGS + --location=LOCATION + Location of the endpoint GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/beta/network-security/firewall-endpoints/list b/gcloud/beta/network-security/firewall-endpoints/list index b3356f983..909d718c1 100644 --- a/gcloud/beta/network-security/firewall-endpoints/list +++ b/gcloud/beta/network-security/firewall-endpoints/list @@ -4,9 +4,10 @@ NAME SYNOPSIS gcloud beta network-security firewall-endpoints list - [--organization=ORGANIZATION] [--zone=ZONE] [--filter=EXPRESSION] - [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] - [GCLOUD_WIDE_FLAG ...] + [--location=LOCATION | --zone=ZONE] + [--organization=ORGANIZATION --project=PROJECT_ID] + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) List firewall endpoints. @@ -20,11 +21,30 @@ EXAMPLES --organization=1234 FLAGS + At most one of these can be specified: + + --location=LOCATION + The location for a list operation + + --zone=ZONE + The zone for a list operation + --organization=ORGANIZATION The organization for a list operation - --zone=ZONE - The zone for a list operation + --project=PROJECT_ID + The project for a list operation + + The Google Cloud project ID to use for this invocation. If omitted, + then the current project is assumed; the current project can be listed + using gcloud config list --format='text(core.project)' and can be set + using gcloud config set project PROJECTID. + + --project and its fallback core/project property play two roles in the + invocation. It specifies the project of the resource to operate on. It + also specifies the project for API enablement check, quota, and + billing. To specify a different project for quota and billing, use + --billing-project or billing/quota_project property. LIST COMMAND FLAGS --filter=EXPRESSION diff --git a/gcloud/beta/network-security/firewall-endpoints/update b/gcloud/beta/network-security/firewall-endpoints/update index 8f9894561..1e2accf15 100644 --- a/gcloud/beta/network-security/firewall-endpoints/update +++ b/gcloud/beta/network-security/firewall-endpoints/update @@ -5,7 +5,8 @@ NAME SYNOPSIS gcloud beta network-security firewall-endpoints update (FIREWALL_ENDPOINT : --organization=ORGANIZATION --zone=ZONE) [--async] - [--description=DESCRIPTION] [--max-wait=MAX_WAIT; default="60m"] + [--description=DESCRIPTION] [--location=LOCATION] + [--max-wait=MAX_WAIT; default="60m"] [--update-billing-project=BILLING_PROJECT] [--update-labels=[KEY=VALUE,...]] [--clear-labels | --remove-labels=[KEY,...]] [GCLOUD_WIDE_FLAG ...] @@ -37,8 +38,17 @@ EXAMPLES POSITIONAL ARGUMENTS Firewall endpoint resource - Firewall Plus. The arguments in this group - can be used to specify the attributes of this resource. This resource can - be one of the following types: [firewall endpoint]. + 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 FIREWALL_ENDPOINT on the command line with a + fully specified name; + ◆ set the property core/project. This resource can be one of the + following types: + [networksecurity.organizations.locations.firewallEndpoints, + networksecurity.projects.locations.firewallEndpoints]. This must be specified. @@ -58,7 +68,9 @@ POSITIONAL ARGUMENTS To set the organization attribute: ▸ provide the argument FIREWALL_ENDPOINT on the command line with a fully specified name; - ▸ provide the argument --organization on the command line. + ▸ provide the argument --organization on the command line. Must be + specified for resource of type + [networksecurity.organizations.locations.firewallEndpoints]. --zone=ZONE Zone of the firewall endpoint. @@ -66,7 +78,8 @@ POSITIONAL ARGUMENTS To set the zone attribute: ▸ provide the argument FIREWALL_ENDPOINT on the command line with a fully specified name; - ▸ provide the argument --zone on the command line. + ▸ provide the argument --zone on the command line; + ▸ provide the argument --location on the command line. FLAGS --async @@ -77,6 +90,9 @@ FLAGS --description=DESCRIPTION Description of the endpoint + --location=LOCATION + Location of the endpoint + --max-wait=MAX_WAIT; default="60m" Time to synchronously wait for the operation to complete, after which the operation continues asynchronously. Ignored if --no-async isn't diff --git a/gcloud/beta/network-security/security-profile-groups/create b/gcloud/beta/network-security/security-profile-groups/create index 624119de5..a5a6c2d56 100644 --- a/gcloud/beta/network-security/security-profile-groups/create +++ b/gcloud/beta/network-security/security-profile-groups/create @@ -7,7 +7,7 @@ SYNOPSIS (SECURITY_PROFILE_GROUP : --location=LOCATION --organization=ORGANIZATION) ([--custom-intercept-profile=CUSTOM_INTERCEPT_PROFILE - : --custom-intercept-profile-location=CUSTOM_INTERCEPT_PROFILE_LOCATION --custom-intercept-profile-organization=CUSTOM_INTERCEPT_PROFILE_ORGANIZATION] [--custom-mirroring-profile=CUSTOM_MIRRORING_PROFILE : --custom-mirroring-profile-location=CUSTOM_MIRRORING_PROFILE_LOCATION --custom-mirroring-profile-organization=CUSTOM_MIRRORING_PROFILE_ORGANIZATION] [--threat-prevention-profile=THREAT_PREVENTION_PROFILE : --threat-prevention-profile-location=THREAT_PREVENTION_PROFILE_LOCATION --threat-prevention-profile-organization=THREAT_PREVENTION_PROFILE_ORGANIZATION] [--url-filtering-profile=URL_FILTERING_PROFILE : --url-filtering-profile-location=URL_FILTERING_PROFILE_LOCATION --url-filtering-profile-organization=URL_FILTERING_PROFILE_ORGANIZATION]) + : --custom-intercept-profile-location=CUSTOM_INTERCEPT_PROFILE_LOCATION --custom-intercept-profile-organization=CUSTOM_INTERCEPT_PROFILE_ORGANIZATION --custom-intercept-profile-project=CUSTOM_INTERCEPT_PROFILE_PROJECT] [--custom-mirroring-profile=CUSTOM_MIRRORING_PROFILE : --custom-mirroring-profile-location=CUSTOM_MIRRORING_PROFILE_LOCATION --custom-mirroring-profile-organization=CUSTOM_MIRRORING_PROFILE_ORGANIZATION --custom-mirroring-profile-project=CUSTOM_MIRRORING_PROFILE_PROJECT] [--threat-prevention-profile=THREAT_PREVENTION_PROFILE : --threat-prevention-profile-location=THREAT_PREVENTION_PROFILE_LOCATION --threat-prevention-profile-organization=THREAT_PREVENTION_PROFILE_ORGANIZATION --threat-prevention-profile-project=THREAT_PREVENTION_PROFILE_PROJECT] [--url-filtering-profile=URL_FILTERING_PROFILE : --url-filtering-profile-location=URL_FILTERING_PROFILE_LOCATION --url-filtering-profile-organization=URL_FILTERING_PROFILE_ORGANIZATION --url-filtering-profile-project=URL_FILTERING_PROFILE_PROJECT]) [--async] [--description=DESCRIPTION] [--labels=[KEY=VALUE,...]] [GCLOUD_WIDE_FLAG ...] @@ -29,8 +29,16 @@ EXAMPLES POSITIONAL ARGUMENTS Security profile group resource - Security Profile Group Name. The arguments in this group can be used to specify the attributes of this - resource. This resource can be one of the following types: - [security_profile_group]. + resource. (NOTE) Some attributes are not given arguments in this group but + can be set in other ways. + + To set the project attribute: + ◆ provide the argument security_profile_group on the command line with + a fully specified name; + ◆ set the property core/project. This resource can be one of the + following types: + [networksecurity.organizations.locations.securityProfileGroups, + networksecurity.projects.locations.securityProfileGroups]. This must be specified. @@ -58,7 +66,9 @@ POSITIONAL ARGUMENTS To set the organization attribute: ▸ provide the argument security_profile_group on the command line with a fully specified name; - ▸ provide the argument --organization on the command line. + ▸ provide the argument --organization on the command line. Must be + specified for resource of type + [networksecurity.organizations.locations.securityProfileGroups]. REQUIRED FLAGS At least one of these must be specified: @@ -66,7 +76,8 @@ REQUIRED FLAGS Custom intercept profile resource - Path to Custom Intercept Profile resource. The arguments in this group can be used to specify the attributes of this resource. This resource can be one of the following - types: [custom_intercept_profile]. + types: [networksecurity.organizations.locations.securityProfiles, + networksecurity.projects.locations.securityProfiles]. --custom-intercept-profile=CUSTOM_INTERCEPT_PROFILE ID of the custom_intercept_profile or fully qualified identifier for @@ -102,12 +113,27 @@ REQUIRED FLAGS the command line; ▸ provide the argument --organization on the command line; ▸ provide the argument security_profile_group on the command line - with a fully specified name. + with a fully specified name. Must be specified for resource of type + [networksecurity.organizations.locations.securityProfiles]. + + --custom-intercept-profile-project=CUSTOM_INTERCEPT_PROFILE_PROJECT + Project ID of the custom_intercept_profile. + + To set the project attribute: + ▸ provide the argument --custom-intercept-profile on the command + line with a fully specified name; + ▸ provide the argument --custom-intercept-profile-project on the + command line; + ▸ set the property core/project; + ▸ provide the argument security_profile_group on the command line + with a fully specified name. Must be specified for resource of type + [networksecurity.projects.locations.securityProfiles]. Custom mirroring profile resource - Path to Custom Mirroring Profile resource. The arguments in this group can be used to specify the attributes of this resource. This resource can be one of the following - types: [custom_mirroring_profile]. + types: [networksecurity.organizations.locations.securityProfiles, + networksecurity.projects.locations.securityProfiles]. --custom-mirroring-profile=CUSTOM_MIRRORING_PROFILE ID of the custom_mirroring_profile or fully qualified identifier for @@ -143,12 +169,27 @@ REQUIRED FLAGS the command line; ▸ provide the argument --organization on the command line; ▸ provide the argument security_profile_group on the command line - with a fully specified name. + with a fully specified name. Must be specified for resource of type + [networksecurity.organizations.locations.securityProfiles]. + + --custom-mirroring-profile-project=CUSTOM_MIRRORING_PROFILE_PROJECT + Project ID of the custom_mirroring_profile. + + To set the project attribute: + ▸ provide the argument --custom-mirroring-profile on the command + line with a fully specified name; + ▸ provide the argument --custom-mirroring-profile-project on the + command line; + ▸ set the property core/project; + ▸ provide the argument security_profile_group on the command line + with a fully specified name. Must be specified for resource of type + [networksecurity.projects.locations.securityProfiles]. Threat prevention profile resource - Path to Threat Prevention Profile resource. The arguments in this group can be used to specify the attributes of this resource. This resource can be one of the following - types: [threat_prevention_profile]. + types: [networksecurity.organizations.locations.securityProfiles, + networksecurity.projects.locations.securityProfiles]. --threat-prevention-profile=THREAT_PREVENTION_PROFILE ID of the threat_prevention_profile or fully qualified identifier for @@ -188,12 +229,27 @@ REQUIRED FLAGS command line; ▸ provide the argument --organization on the command line; ▸ provide the argument security_profile_group on the command line - with a fully specified name. + with a fully specified name. Must be specified for resource of type + [networksecurity.organizations.locations.securityProfiles]. + + --threat-prevention-profile-project=THREAT_PREVENTION_PROFILE_PROJECT + Project ID of the threat_prevention_profile. + + To set the project attribute: + ▸ provide the argument --threat-prevention-profile on the command + line with a fully specified name; + ▸ provide the argument --threat-prevention-profile-project on the + command line; + ▸ set the property core/project; + ▸ provide the argument security_profile_group on the command line + with a fully specified name. Must be specified for resource of type + [networksecurity.projects.locations.securityProfiles]. Url filtering profile resource - Path to URL Filtering Profile resource. The arguments in this group can be used to specify the attributes of this resource. This resource can be one of the following types: - [url_filtering_profile]. + [networksecurity.organizations.locations.securityProfiles, + networksecurity.projects.locations.securityProfiles]. --url-filtering-profile=URL_FILTERING_PROFILE ID of the url_filtering_profile or fully qualified identifier for the @@ -228,7 +284,21 @@ REQUIRED FLAGS command line; ▸ provide the argument --organization on the command line; ▸ provide the argument security_profile_group on the command line - with a fully specified name. + with a fully specified name. Must be specified for resource of type + [networksecurity.organizations.locations.securityProfiles]. + + --url-filtering-profile-project=URL_FILTERING_PROFILE_PROJECT + Project ID of the url_filtering_profile. + + To set the project attribute: + ▸ provide the argument --url-filtering-profile on the command line + with a fully specified name; + ▸ provide the argument --url-filtering-profile-project on the + command line; + ▸ set the property core/project; + ▸ provide the argument security_profile_group on the command line + with a fully specified name. Must be specified for resource of type + [networksecurity.projects.locations.securityProfiles]. OPTIONAL FLAGS --async diff --git a/gcloud/beta/network-security/security-profile-groups/delete b/gcloud/beta/network-security/security-profile-groups/delete index 46685ddf7..bc573070a 100644 --- a/gcloud/beta/network-security/security-profile-groups/delete +++ b/gcloud/beta/network-security/security-profile-groups/delete @@ -20,8 +20,16 @@ EXAMPLES POSITIONAL ARGUMENTS Security profile group resource - Security Profile Group Name. The arguments in this group can be used to specify the attributes of this - resource. This resource can be one of the following types: - [security_profile_group]. + resource. (NOTE) Some attributes are not given arguments in this group but + can be set in other ways. + + To set the project attribute: + ◆ provide the argument security_profile_group on the command line with + a fully specified name; + ◆ set the property core/project. This resource can be one of the + following types: + [networksecurity.organizations.locations.securityProfileGroups, + networksecurity.projects.locations.securityProfileGroups]. This must be specified. @@ -49,7 +57,9 @@ POSITIONAL ARGUMENTS To set the organization attribute: ▸ provide the argument security_profile_group on the command line with a fully specified name; - ▸ provide the argument --organization on the command line. + ▸ provide the argument --organization on the command line. Must be + specified for resource of type + [networksecurity.organizations.locations.securityProfileGroups]. FLAGS --async diff --git a/gcloud/beta/network-security/security-profile-groups/describe b/gcloud/beta/network-security/security-profile-groups/describe index c64530e10..11230bbb3 100644 --- a/gcloud/beta/network-security/security-profile-groups/describe +++ b/gcloud/beta/network-security/security-profile-groups/describe @@ -21,8 +21,16 @@ EXAMPLES POSITIONAL ARGUMENTS Security profile group resource - Security Profile Group Name. The arguments in this group can be used to specify the attributes of this - resource. This resource can be one of the following types: - [security_profile_group]. + resource. (NOTE) Some attributes are not given arguments in this group but + can be set in other ways. + + To set the project attribute: + ◆ provide the argument security_profile_group on the command line with + a fully specified name; + ◆ set the property core/project. This resource can be one of the + following types: + [networksecurity.organizations.locations.securityProfileGroups, + networksecurity.projects.locations.securityProfileGroups]. This must be specified. @@ -50,7 +58,9 @@ POSITIONAL ARGUMENTS To set the organization attribute: ▸ provide the argument security_profile_group on the command line with a fully specified name; - ▸ provide the argument --organization on the command line. + ▸ provide the argument --organization on the command line. Must be + specified for resource of type + [networksecurity.organizations.locations.securityProfileGroups]. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/beta/network-security/security-profile-groups/list b/gcloud/beta/network-security/security-profile-groups/list index 62c835a21..6eac5f893 100644 --- a/gcloud/beta/network-security/security-profile-groups/list +++ b/gcloud/beta/network-security/security-profile-groups/list @@ -19,8 +19,16 @@ EXAMPLES REQUIRED FLAGS Location resource - Parent resource for the list operation. The arguments - in this group can be used to specify the attributes of this resource. This - resource can be one of the following types: [location]. + 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 --location on the command line with a fully + specified name; + ◆ set the property core/project. This resource can be one of the + following types: [networksecurity.organizations.locations, + networksecurity.projects.locations]. This must be specified. @@ -39,7 +47,9 @@ REQUIRED FLAGS To set the organization attribute: ▸ provide the argument --location on the command line with a fully specified name; - ▸ provide the argument --organization on the command line. + ▸ provide the argument --organization on the command line. Must be + specified for resource of type + [networksecurity.organizations.locations]. LIST COMMAND FLAGS --filter=EXPRESSION diff --git a/gcloud/beta/network-security/security-profile-groups/update b/gcloud/beta/network-security/security-profile-groups/update index afd013b80..d77a17654 100644 --- a/gcloud/beta/network-security/security-profile-groups/update +++ b/gcloud/beta/network-security/security-profile-groups/update @@ -10,11 +10,11 @@ SYNOPSIS [--clear-labels | --remove-labels=[KEY,...]] [--clear-threat-prevention-profile | [--threat-prevention-profile=THREAT_PREVENTION_PROFILE - : --threat-prevention-profile-location=THREAT_PREVENTION_PROFILE_LOCATION --threat-prevention-profile-organization=THREAT_PREVENTION_PROFILE_ORGANIZATION]] + : --threat-prevention-profile-location=THREAT_PREVENTION_PROFILE_LOCATION --threat-prevention-profile-organization=THREAT_PREVENTION_PROFILE_ORGANIZATION --threat-prevention-profile-project=THREAT_PREVENTION_PROFILE_PROJECT]] [--clear-url-filtering-profile | [--url-filtering-profile=URL_FILTERING_PROFILE : --url-filtering-profile-location=URL_FILTERING_PROFILE_LOCATION - --url-filtering-profile-organization=URL_FILTERING_PROFILE_ORGANIZATION]] + --url-filtering-profile-organization=URL_FILTERING_PROFILE_ORGANIZATION --url-filtering-profile-project=URL_FILTERING_PROFILE_PROJECT]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -34,8 +34,16 @@ EXAMPLES POSITIONAL ARGUMENTS Security profile group resource - Security Profile Group Name. The arguments in this group can be used to specify the attributes of this - resource. This resource can be one of the following types: - [security_profile_group]. + resource. (NOTE) Some attributes are not given arguments in this group but + can be set in other ways. + + To set the project attribute: + ◆ provide the argument security_profile_group on the command line with + a fully specified name; + ◆ set the property core/project. This resource can be one of the + following types: + [networksecurity.organizations.locations.securityProfileGroups, + networksecurity.projects.locations.securityProfileGroups]. This must be specified. @@ -63,7 +71,9 @@ POSITIONAL ARGUMENTS To set the organization attribute: ▸ provide the argument security_profile_group on the command line with a fully specified name; - ▸ provide the argument --organization on the command line. + ▸ provide the argument --organization on the command line. Must be + specified for resource of type + [networksecurity.organizations.locations.securityProfileGroups]. FLAGS --async @@ -113,7 +123,8 @@ FLAGS Threat prevention profile resource - Path to Threat Prevention Profile resource. The arguments in this group can be used to specify the attributes of this resource. This resource can be one of the following - types: [threat_prevention_profile]. + types: [networksecurity.organizations.locations.securityProfiles, + networksecurity.projects.locations.securityProfiles]. --threat-prevention-profile=THREAT_PREVENTION_PROFILE ID of the threat_prevention_profile or fully qualified identifier @@ -153,7 +164,21 @@ FLAGS command line; ▫ provide the argument --organization on the command line; ▫ provide the argument security_profile_group on the command line - with a fully specified name. + with a fully specified name. Must be specified for resource of + type [networksecurity.organizations.locations.securityProfiles]. + + --threat-prevention-profile-project=THREAT_PREVENTION_PROFILE_PROJECT + Project ID of the threat_prevention_profile. + + To set the project attribute: + ▫ provide the argument --threat-prevention-profile on the command + line with a fully specified name; + ▫ provide the argument --threat-prevention-profile-project on the + command line; + ▫ set the property core/project; + ▫ provide the argument security_profile_group on the command line + with a fully specified name. Must be specified for resource of + type [networksecurity.projects.locations.securityProfiles]. At most one of these can be specified: @@ -165,7 +190,8 @@ FLAGS Url filtering profile resource - Path to URL Filtering Profile resource. The arguments in this group can be used to specify the attributes of this resource. This resource can be one of the following - types: [url_filtering_profile]. + types: [networksecurity.organizations.locations.securityProfiles, + networksecurity.projects.locations.securityProfiles]. --url-filtering-profile=URL_FILTERING_PROFILE ID of the url_filtering_profile or fully qualified identifier for @@ -201,7 +227,21 @@ FLAGS the command line; ▫ provide the argument --organization on the command line; ▫ provide the argument security_profile_group on the command line - with a fully specified name. + with a fully specified name. Must be specified for resource of + type [networksecurity.organizations.locations.securityProfiles]. + + --url-filtering-profile-project=URL_FILTERING_PROFILE_PROJECT + Project ID of the url_filtering_profile. + + To set the project attribute: + ▫ provide the argument --url-filtering-profile on the command + line with a fully specified name; + ▫ provide the argument --url-filtering-profile-project on the + command line; + ▫ set the property core/project; + ▫ provide the argument security_profile_group on the command line + with a fully specified name. Must be specified for resource of + type [networksecurity.projects.locations.securityProfiles]. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/beta/network-security/security-profiles/custom-intercept/create b/gcloud/beta/network-security/security-profiles/custom-intercept/create index d82c20488..f88728061 100644 --- a/gcloud/beta/network-security/security-profiles/custom-intercept/create +++ b/gcloud/beta/network-security/security-profiles/custom-intercept/create @@ -24,8 +24,17 @@ EXAMPLES POSITIONAL ARGUMENTS Security profile resource - Security Profile Name. The arguments in this - group can be used to specify the attributes of this resource. This - resource can be one of the following types: [security_profile]. + 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 security_profile on the command line with a + fully specified name; + ◆ set the property core/project. This resource can be one of the + following types: + [networksecurity.organizations.locations.securityProfiles, + networksecurity.projects.locations.securityProfiles]. This must be specified. @@ -53,7 +62,9 @@ POSITIONAL ARGUMENTS To set the organization attribute: ▸ provide the argument security_profile on the command line with a fully specified name; - ▸ provide the argument --organization on the command line. + ▸ provide the argument --organization on the command line. Must be + specified for resource of type + [networksecurity.organizations.locations.securityProfiles]. REQUIRED FLAGS Intercept endpoint group resource - Intercept Endpoint Group. The @@ -94,7 +105,9 @@ REQUIRED FLAGS ▸ provide the argument --intercept-endpoint-group-project on the command line; ▸ provide the argument --project on the command line; - ▸ set the property core/project. + ▸ set the property core/project; + ▸ provide the argument security_profile on the command line with a + fully specified name. OPTIONAL FLAGS --async diff --git a/gcloud/beta/network-security/security-profiles/custom-intercept/delete b/gcloud/beta/network-security/security-profiles/custom-intercept/delete index e4ffd35f6..952588cbf 100644 --- a/gcloud/beta/network-security/security-profiles/custom-intercept/delete +++ b/gcloud/beta/network-security/security-profiles/custom-intercept/delete @@ -18,8 +18,17 @@ EXAMPLES POSITIONAL ARGUMENTS Security profile resource - Security Profile Name. The arguments in this - group can be used to specify the attributes of this resource. This - resource can be one of the following types: [security_profile]. + 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 security_profile on the command line with a + fully specified name; + ◆ set the property core/project. This resource can be one of the + following types: + [networksecurity.organizations.locations.securityProfiles, + networksecurity.projects.locations.securityProfiles]. This must be specified. @@ -47,7 +56,9 @@ POSITIONAL ARGUMENTS To set the organization attribute: ▸ provide the argument security_profile on the command line with a fully specified name; - ▸ provide the argument --organization on the command line. + ▸ provide the argument --organization on the command line. Must be + specified for resource of type + [networksecurity.organizations.locations.securityProfiles]. FLAGS --async diff --git a/gcloud/beta/network-security/security-profiles/custom-intercept/describe b/gcloud/beta/network-security/security-profiles/custom-intercept/describe index 4e54ac5f0..4f3461f96 100644 --- a/gcloud/beta/network-security/security-profiles/custom-intercept/describe +++ b/gcloud/beta/network-security/security-profiles/custom-intercept/describe @@ -18,8 +18,17 @@ EXAMPLES POSITIONAL ARGUMENTS Security profile resource - Security Profile Name. The arguments in this - group can be used to specify the attributes of this resource. This - resource can be one of the following types: [security_profile]. + 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 security_profile on the command line with a + fully specified name; + ◆ set the property core/project. This resource can be one of the + following types: + [networksecurity.organizations.locations.securityProfiles, + networksecurity.projects.locations.securityProfiles]. This must be specified. @@ -47,7 +56,9 @@ POSITIONAL ARGUMENTS To set the organization attribute: ▸ provide the argument security_profile on the command line with a fully specified name; - ▸ provide the argument --organization on the command line. + ▸ provide the argument --organization on the command line. Must be + specified for resource of type + [networksecurity.organizations.locations.securityProfiles]. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/beta/network-security/security-profiles/custom-intercept/list b/gcloud/beta/network-security/security-profiles/custom-intercept/list index 5c4a7123e..4ebf35721 100644 --- a/gcloud/beta/network-security/security-profiles/custom-intercept/list +++ b/gcloud/beta/network-security/security-profiles/custom-intercept/list @@ -20,8 +20,16 @@ EXAMPLES FLAGS Location resource - Parent resource for the list operation. The arguments - in this group can be used to specify the attributes of this resource. This - resource can be one of the following types: [location]. + 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 --location on the command line with a fully + specified name; + ◆ set the property core/project. This resource can be one of the + following types: [networksecurity.organizations.locations, + networksecurity.projects.locations]. --location=LOCATION ID of the location or fully qualified identifier for the location. @@ -38,7 +46,9 @@ FLAGS To set the organization attribute: ◆ provide the argument --location on the command line with a fully specified name; - ◆ provide the argument --organization on the command line. + ◆ provide the argument --organization on the command line. Must be + specified for resource of type + [networksecurity.organizations.locations]. LIST COMMAND FLAGS --filter=EXPRESSION diff --git a/gcloud/beta/network-security/security-profiles/custom-intercept/update b/gcloud/beta/network-security/security-profiles/custom-intercept/update index 915a46f49..c411d7c27 100644 --- a/gcloud/beta/network-security/security-profiles/custom-intercept/update +++ b/gcloud/beta/network-security/security-profiles/custom-intercept/update @@ -32,8 +32,17 @@ EXAMPLES POSITIONAL ARGUMENTS Security profile resource - Security Profile Name. The arguments in this - group can be used to specify the attributes of this resource. This - resource can be one of the following types: [security_profile]. + 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 security_profile on the command line with a + fully specified name; + ◆ set the property core/project. This resource can be one of the + following types: + [networksecurity.organizations.locations.securityProfiles, + networksecurity.projects.locations.securityProfiles]. This must be specified. @@ -61,7 +70,9 @@ POSITIONAL ARGUMENTS To set the organization attribute: ▸ provide the argument security_profile on the command line with a fully specified name; - ▸ provide the argument --organization on the command line. + ▸ provide the argument --organization on the command line. Must be + specified for resource of type + [networksecurity.organizations.locations.securityProfiles]. FLAGS --async diff --git a/gcloud/beta/network-security/security-profiles/custom-mirroring/create b/gcloud/beta/network-security/security-profiles/custom-mirroring/create index 459d7fc6b..b02d61fc3 100644 --- a/gcloud/beta/network-security/security-profiles/custom-mirroring/create +++ b/gcloud/beta/network-security/security-profiles/custom-mirroring/create @@ -24,8 +24,17 @@ EXAMPLES POSITIONAL ARGUMENTS Security profile resource - Security Profile Name. The arguments in this - group can be used to specify the attributes of this resource. This - resource can be one of the following types: [security_profile]. + 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 security_profile on the command line with a + fully specified name; + ◆ set the property core/project. This resource can be one of the + following types: + [networksecurity.organizations.locations.securityProfiles, + networksecurity.projects.locations.securityProfiles]. This must be specified. @@ -53,7 +62,9 @@ POSITIONAL ARGUMENTS To set the organization attribute: ▸ provide the argument security_profile on the command line with a fully specified name; - ▸ provide the argument --organization on the command line. + ▸ provide the argument --organization on the command line. Must be + specified for resource of type + [networksecurity.organizations.locations.securityProfiles]. REQUIRED FLAGS Mirroring endpoint group resource - Mirroring Endpoint Group. The @@ -94,7 +105,9 @@ REQUIRED FLAGS ▸ provide the argument --mirroring-endpoint-group-project on the command line; ▸ provide the argument --project on the command line; - ▸ set the property core/project. + ▸ set the property core/project; + ▸ provide the argument security_profile on the command line with a + fully specified name. OPTIONAL FLAGS --async diff --git a/gcloud/beta/network-security/security-profiles/custom-mirroring/delete b/gcloud/beta/network-security/security-profiles/custom-mirroring/delete index d4b764f87..0d66a1d92 100644 --- a/gcloud/beta/network-security/security-profiles/custom-mirroring/delete +++ b/gcloud/beta/network-security/security-profiles/custom-mirroring/delete @@ -18,8 +18,17 @@ EXAMPLES POSITIONAL ARGUMENTS Security profile resource - Security Profile Name. The arguments in this - group can be used to specify the attributes of this resource. This - resource can be one of the following types: [security_profile]. + 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 security_profile on the command line with a + fully specified name; + ◆ set the property core/project. This resource can be one of the + following types: + [networksecurity.organizations.locations.securityProfiles, + networksecurity.projects.locations.securityProfiles]. This must be specified. @@ -47,7 +56,9 @@ POSITIONAL ARGUMENTS To set the organization attribute: ▸ provide the argument security_profile on the command line with a fully specified name; - ▸ provide the argument --organization on the command line. + ▸ provide the argument --organization on the command line. Must be + specified for resource of type + [networksecurity.organizations.locations.securityProfiles]. FLAGS --async diff --git a/gcloud/beta/network-security/security-profiles/custom-mirroring/describe b/gcloud/beta/network-security/security-profiles/custom-mirroring/describe index 6c8d82c6e..e195768f4 100644 --- a/gcloud/beta/network-security/security-profiles/custom-mirroring/describe +++ b/gcloud/beta/network-security/security-profiles/custom-mirroring/describe @@ -18,8 +18,17 @@ EXAMPLES POSITIONAL ARGUMENTS Security profile resource - Security Profile Name. The arguments in this - group can be used to specify the attributes of this resource. This - resource can be one of the following types: [security_profile]. + 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 security_profile on the command line with a + fully specified name; + ◆ set the property core/project. This resource can be one of the + following types: + [networksecurity.organizations.locations.securityProfiles, + networksecurity.projects.locations.securityProfiles]. This must be specified. @@ -47,7 +56,9 @@ POSITIONAL ARGUMENTS To set the organization attribute: ▸ provide the argument security_profile on the command line with a fully specified name; - ▸ provide the argument --organization on the command line. + ▸ provide the argument --organization on the command line. Must be + specified for resource of type + [networksecurity.organizations.locations.securityProfiles]. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/beta/network-security/security-profiles/custom-mirroring/list b/gcloud/beta/network-security/security-profiles/custom-mirroring/list index 30788d124..84a8b5066 100644 --- a/gcloud/beta/network-security/security-profiles/custom-mirroring/list +++ b/gcloud/beta/network-security/security-profiles/custom-mirroring/list @@ -20,8 +20,16 @@ EXAMPLES FLAGS Location resource - Parent resource for the list operation. The arguments - in this group can be used to specify the attributes of this resource. This - resource can be one of the following types: [location]. + 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 --location on the command line with a fully + specified name; + ◆ set the property core/project. This resource can be one of the + following types: [networksecurity.organizations.locations, + networksecurity.projects.locations]. --location=LOCATION ID of the location or fully qualified identifier for the location. @@ -38,7 +46,9 @@ FLAGS To set the organization attribute: ◆ provide the argument --location on the command line with a fully specified name; - ◆ provide the argument --organization on the command line. + ◆ provide the argument --organization on the command line. Must be + specified for resource of type + [networksecurity.organizations.locations]. LIST COMMAND FLAGS --filter=EXPRESSION diff --git a/gcloud/beta/network-security/security-profiles/custom-mirroring/update b/gcloud/beta/network-security/security-profiles/custom-mirroring/update index 5224fd9f0..5f6d96948 100644 --- a/gcloud/beta/network-security/security-profiles/custom-mirroring/update +++ b/gcloud/beta/network-security/security-profiles/custom-mirroring/update @@ -32,8 +32,17 @@ EXAMPLES POSITIONAL ARGUMENTS Security profile resource - Security Profile Name. The arguments in this - group can be used to specify the attributes of this resource. This - resource can be one of the following types: [security_profile]. + 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 security_profile on the command line with a + fully specified name; + ◆ set the property core/project. This resource can be one of the + following types: + [networksecurity.organizations.locations.securityProfiles, + networksecurity.projects.locations.securityProfiles]. This must be specified. @@ -61,7 +70,9 @@ POSITIONAL ARGUMENTS To set the organization attribute: ▸ provide the argument security_profile on the command line with a fully specified name; - ▸ provide the argument --organization on the command line. + ▸ provide the argument --organization on the command line. Must be + specified for resource of type + [networksecurity.organizations.locations.securityProfiles]. FLAGS --async diff --git a/gcloud/beta/network-security/security-profiles/delete b/gcloud/beta/network-security/security-profiles/delete index 07448f51c..0163173d5 100644 --- a/gcloud/beta/network-security/security-profiles/delete +++ b/gcloud/beta/network-security/security-profiles/delete @@ -18,8 +18,17 @@ EXAMPLES POSITIONAL ARGUMENTS Security profile resource - Security Profile Name. The arguments in this - group can be used to specify the attributes of this resource. This - resource can be one of the following types: [security_profile]. + 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 security_profile on the command line with a + fully specified name; + ◆ set the property core/project. This resource can be one of the + following types: + [networksecurity.organizations.locations.securityProfiles, + networksecurity.projects.locations.securityProfiles]. This must be specified. @@ -47,7 +56,9 @@ POSITIONAL ARGUMENTS To set the organization attribute: ▸ provide the argument security_profile on the command line with a fully specified name; - ▸ provide the argument --organization on the command line. + ▸ provide the argument --organization on the command line. Must be + specified for resource of type + [networksecurity.organizations.locations.securityProfiles]. FLAGS --async diff --git a/gcloud/beta/network-security/security-profiles/describe b/gcloud/beta/network-security/security-profiles/describe index 85899eca4..bc096a628 100644 --- a/gcloud/beta/network-security/security-profiles/describe +++ b/gcloud/beta/network-security/security-profiles/describe @@ -18,8 +18,17 @@ EXAMPLES POSITIONAL ARGUMENTS Security profile resource - Security Profile Name. The arguments in this - group can be used to specify the attributes of this resource. This - resource can be one of the following types: [security_profile]. + 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 security_profile on the command line with a + fully specified name; + ◆ set the property core/project. This resource can be one of the + following types: + [networksecurity.organizations.locations.securityProfiles, + networksecurity.projects.locations.securityProfiles]. This must be specified. @@ -47,7 +56,9 @@ POSITIONAL ARGUMENTS To set the organization attribute: ▸ provide the argument security_profile on the command line with a fully specified name; - ▸ provide the argument --organization on the command line. + ▸ provide the argument --organization on the command line. Must be + specified for resource of type + [networksecurity.organizations.locations.securityProfiles]. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/beta/network-security/security-profiles/export b/gcloud/beta/network-security/security-profiles/export index b8b9bfc16..856d9ca8d 100644 --- a/gcloud/beta/network-security/security-profiles/export +++ b/gcloud/beta/network-security/security-profiles/export @@ -19,8 +19,17 @@ EXAMPLES POSITIONAL ARGUMENTS Security profile resource - Security Profile Name. The arguments in this - group can be used to specify the attributes of this resource. This - resource can be one of the following types: [security_profile]. + 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 security_profile on the command line with a + fully specified name; + ◆ set the property core/project. This resource can be one of the + following types: + [networksecurity.organizations.locations.securityProfiles, + networksecurity.projects.locations.securityProfiles]. This must be specified. @@ -48,7 +57,9 @@ POSITIONAL ARGUMENTS To set the organization attribute: ▸ provide the argument security_profile on the command line with a fully specified name; - ▸ provide the argument --organization on the command line. + ▸ provide the argument --organization on the command line. Must be + specified for resource of type + [networksecurity.organizations.locations.securityProfiles]. FLAGS --destination=DESTINATION diff --git a/gcloud/beta/network-security/security-profiles/import b/gcloud/beta/network-security/security-profiles/import index e13e177e5..1ff74dd33 100644 --- a/gcloud/beta/network-security/security-profiles/import +++ b/gcloud/beta/network-security/security-profiles/import @@ -19,8 +19,17 @@ EXAMPLES POSITIONAL ARGUMENTS Security profile resource - Security Profile Name. The arguments in this - group can be used to specify the attributes of this resource. This - resource can be one of the following types: [security_profile]. + 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 security_profile on the command line with a + fully specified name; + ◆ set the property core/project. This resource can be one of the + following types: + [networksecurity.organizations.locations.securityProfiles, + networksecurity.projects.locations.securityProfiles]. This must be specified. @@ -48,7 +57,9 @@ POSITIONAL ARGUMENTS To set the organization attribute: ▸ provide the argument security_profile on the command line with a fully specified name; - ▸ provide the argument --organization on the command line. + ▸ provide the argument --organization on the command line. Must be + specified for resource of type + [networksecurity.organizations.locations.securityProfiles]. FLAGS --async diff --git a/gcloud/beta/network-security/security-profiles/list b/gcloud/beta/network-security/security-profiles/list index 6d9a59a77..32b3c2a5f 100644 --- a/gcloud/beta/network-security/security-profiles/list +++ b/gcloud/beta/network-security/security-profiles/list @@ -19,8 +19,16 @@ EXAMPLES REQUIRED FLAGS Location resource - Parent resource for the list operation. The arguments - in this group can be used to specify the attributes of this resource. This - resource can be one of the following types: [location]. + 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 --location on the command line with a fully + specified name; + ◆ set the property core/project. This resource can be one of the + following types: [networksecurity.organizations.locations, + networksecurity.projects.locations]. This must be specified. @@ -39,7 +47,9 @@ REQUIRED FLAGS To set the organization attribute: ▸ provide the argument --location on the command line with a fully specified name; - ▸ provide the argument --organization on the command line. + ▸ provide the argument --organization on the command line. Must be + specified for resource of type + [networksecurity.organizations.locations]. LIST COMMAND FLAGS --filter=EXPRESSION diff --git a/gcloud/beta/network-security/security-profiles/threat-prevention/add-override b/gcloud/beta/network-security/security-profiles/threat-prevention/add-override index abfa918db..25facdda3 100644 --- a/gcloud/beta/network-security/security-profiles/threat-prevention/add-override +++ b/gcloud/beta/network-security/security-profiles/threat-prevention/add-override @@ -35,8 +35,17 @@ EXAMPLES POSITIONAL ARGUMENTS Security profile resource - Security Profile Name. The arguments in this - group can be used to specify the attributes of this resource. This - resource can be one of the following types: [security_profile]. + 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 security_profile on the command line with a + fully specified name; + ◆ set the property core/project. This resource can be one of the + following types: + [networksecurity.organizations.locations.securityProfiles, + networksecurity.projects.locations.securityProfiles]. This must be specified. @@ -64,7 +73,9 @@ POSITIONAL ARGUMENTS To set the organization attribute: ▸ provide the argument security_profile on the command line with a fully specified name; - ▸ provide the argument --organization on the command line. + ▸ provide the argument --organization on the command line. Must be + specified for resource of type + [networksecurity.organizations.locations.securityProfiles]. REQUIRED FLAGS --action=ACTION diff --git a/gcloud/beta/network-security/security-profiles/threat-prevention/create b/gcloud/beta/network-security/security-profiles/threat-prevention/create index f30270ec3..071b7c5e8 100644 --- a/gcloud/beta/network-security/security-profiles/threat-prevention/create +++ b/gcloud/beta/network-security/security-profiles/threat-prevention/create @@ -20,8 +20,17 @@ EXAMPLES POSITIONAL ARGUMENTS Security profile resource - Security Profile Name. The arguments in this - group can be used to specify the attributes of this resource. This - resource can be one of the following types: [security_profile]. + 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 security_profile on the command line with a + fully specified name; + ◆ set the property core/project. This resource can be one of the + following types: + [networksecurity.organizations.locations.securityProfiles, + networksecurity.projects.locations.securityProfiles]. This must be specified. @@ -49,7 +58,9 @@ POSITIONAL ARGUMENTS To set the organization attribute: ▸ provide the argument security_profile on the command line with a fully specified name; - ▸ provide the argument --organization on the command line. + ▸ provide the argument --organization on the command line. Must be + specified for resource of type + [networksecurity.organizations.locations.securityProfiles]. FLAGS --async diff --git a/gcloud/beta/network-security/security-profiles/threat-prevention/delete b/gcloud/beta/network-security/security-profiles/threat-prevention/delete index 9a65ac829..1ca836687 100644 --- a/gcloud/beta/network-security/security-profiles/threat-prevention/delete +++ b/gcloud/beta/network-security/security-profiles/threat-prevention/delete @@ -18,8 +18,17 @@ EXAMPLES POSITIONAL ARGUMENTS Security profile resource - Security Profile Name. The arguments in this - group can be used to specify the attributes of this resource. This - resource can be one of the following types: [security_profile]. + 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 security_profile on the command line with a + fully specified name; + ◆ set the property core/project. This resource can be one of the + following types: + [networksecurity.organizations.locations.securityProfiles, + networksecurity.projects.locations.securityProfiles]. This must be specified. @@ -47,7 +56,9 @@ POSITIONAL ARGUMENTS To set the organization attribute: ▸ provide the argument security_profile on the command line with a fully specified name; - ▸ provide the argument --organization on the command line. + ▸ provide the argument --organization on the command line. Must be + specified for resource of type + [networksecurity.organizations.locations.securityProfiles]. FLAGS --async diff --git a/gcloud/beta/network-security/security-profiles/threat-prevention/delete-override b/gcloud/beta/network-security/security-profiles/threat-prevention/delete-override index 4d2b51765..78a32c82d 100644 --- a/gcloud/beta/network-security/security-profiles/threat-prevention/delete-override +++ b/gcloud/beta/network-security/security-profiles/threat-prevention/delete-override @@ -33,8 +33,17 @@ EXAMPLES POSITIONAL ARGUMENTS Security profile resource - Security Profile Name. The arguments in this - group can be used to specify the attributes of this resource. This - resource can be one of the following types: [security_profile]. + 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 security_profile on the command line with a + fully specified name; + ◆ set the property core/project. This resource can be one of the + following types: + [networksecurity.organizations.locations.securityProfiles, + networksecurity.projects.locations.securityProfiles]. This must be specified. @@ -62,7 +71,9 @@ POSITIONAL ARGUMENTS To set the organization attribute: ▸ provide the argument security_profile on the command line with a fully specified name; - ▸ provide the argument --organization on the command line. + ▸ provide the argument --organization on the command line. Must be + specified for resource of type + [networksecurity.organizations.locations.securityProfiles]. REQUIRED FLAGS Exactly one of these must be specified: diff --git a/gcloud/beta/network-security/security-profiles/threat-prevention/describe b/gcloud/beta/network-security/security-profiles/threat-prevention/describe new file mode 100644 index 000000000..02b3a09db --- /dev/null +++ b/gcloud/beta/network-security/security-profiles/threat-prevention/describe @@ -0,0 +1,89 @@ +NAME + gcloud beta network-security security-profiles threat-prevention describe - + describe a Threat Prevention Security Profile + +SYNOPSIS + gcloud beta network-security security-profiles threat-prevention describe + (SECURITY_PROFILE : --location=LOCATION --organization=ORGANIZATION) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Show details of a Threat Prevention Security Profile. + + For more examples, refer to the EXAMPLES section below. + +EXAMPLES + To show details of a Threat Prevention security profile named + my-security-profile in an organization, run: + + $ gcloud beta network-security security-profiles threat-prevention \ describe my-security-profile --organization=1234 \ + --location=global + + To show details of a Threat Prevention security profile named + my-security-profile in a project, run: + + $ gcloud beta network-security security-profiles threat-prevention \ describe my-security-profile --project=my-project \ + --location=global + +POSITIONAL ARGUMENTS + Security profile resource - Security Profile Name. The arguments in this + group can be used to specify the attributes of this resource. (NOTE) Some + attributes are not given arguments in this group but can be set in other + ways. + + To set the project attribute: + ◆ provide the argument security_profile on the command line with a + fully specified name; + ◆ set the property core/project. This resource can be one of the + following types: + [networksecurity.organizations.locations.securityProfiles, + networksecurity.projects.locations.securityProfiles]. + + This must be specified. + + SECURITY_PROFILE + ID of the security_profile or fully qualified identifier for the + security_profile. + + To set the security_profile attribute: + ▸ provide the argument security_profile on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + Location of the security profile. + + To set the location attribute: + ▸ provide the argument security_profile on the command line with a + fully specified name; + ▸ provide the argument --location on the command line. + + --organization=ORGANIZATION + Organization ID to which the changes should apply. + + To set the organization attribute: + ▸ provide the argument security_profile on the command line with a + fully specified name; + ▸ provide the argument --organization on the command line. Must be + specified for resource of type + [networksecurity.organizations.locations.securityProfiles]. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --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 network-security security-profiles threat-prevention \ + describe + + $ gcloud alpha network-security security-profiles \ + threat-prevention describe + diff --git a/gcloud/beta/network-security/security-profiles/threat-prevention/help b/gcloud/beta/network-security/security-profiles/threat-prevention/help index e8fe2a27d..b7912f466 100644 --- a/gcloud/beta/network-security/security-profiles/threat-prevention/help +++ b/gcloud/beta/network-security/security-profiles/threat-prevention/help @@ -68,6 +68,11 @@ EXAMPLES $ gcloud beta network-security security-profiles threat-prevention \ list --location=global + To describe a Security Profile called my-security-profile, run: + + $ gcloud beta network-security security-profiles threat-prevention \ + describe my-security-profile + To delete a Security Profile called my-security-profile which includes location as global or region specified and organization ID, run: @@ -94,6 +99,9 @@ COMMANDS delete-override (BETA) Delete overrides of Threat Prevention Profile. + describe + (BETA) Describe a Threat Prevention Security Profile. + list (BETA) List Threat Prevention Security Profiles. diff --git a/gcloud/beta/network-security/security-profiles/threat-prevention/list b/gcloud/beta/network-security/security-profiles/threat-prevention/list index 826716d9b..ca558c4cc 100644 --- a/gcloud/beta/network-security/security-profiles/threat-prevention/list +++ b/gcloud/beta/network-security/security-profiles/threat-prevention/list @@ -20,8 +20,16 @@ EXAMPLES REQUIRED FLAGS Location resource - Parent resource for the list operation. The arguments - in this group can be used to specify the attributes of this resource. This - resource can be one of the following types: [location]. + 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 --location on the command line with a fully + specified name; + ◆ set the property core/project. This resource can be one of the + following types: [networksecurity.organizations.locations, + networksecurity.projects.locations]. This must be specified. @@ -40,7 +48,9 @@ REQUIRED FLAGS To set the organization attribute: ▸ provide the argument --location on the command line with a fully specified name; - ▸ provide the argument --organization on the command line. + ▸ provide the argument --organization on the command line. Must be + specified for resource of type + [networksecurity.organizations.locations]. LIST COMMAND FLAGS --filter=EXPRESSION diff --git a/gcloud/beta/network-security/security-profiles/threat-prevention/list-overrides b/gcloud/beta/network-security/security-profiles/threat-prevention/list-overrides index 449da0a90..52d2daf57 100644 --- a/gcloud/beta/network-security/security-profiles/threat-prevention/list-overrides +++ b/gcloud/beta/network-security/security-profiles/threat-prevention/list-overrides @@ -28,8 +28,17 @@ EXAMPLES POSITIONAL ARGUMENTS Security profile resource - Security Profile Name. The arguments in this - group can be used to specify the attributes of this resource. This - resource can be one of the following types: [security_profile]. + 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 security_profile on the command line with a + fully specified name; + ◆ set the property core/project. This resource can be one of the + following types: + [networksecurity.organizations.locations.securityProfiles, + networksecurity.projects.locations.securityProfiles]. This must be specified. @@ -57,7 +66,9 @@ POSITIONAL ARGUMENTS To set the organization attribute: ▸ provide the argument security_profile on the command line with a fully specified name; - ▸ provide the argument --organization on the command line. + ▸ provide the argument --organization on the command line. Must be + specified for resource of type + [networksecurity.organizations.locations.securityProfiles]. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/beta/network-security/security-profiles/threat-prevention/update-override b/gcloud/beta/network-security/security-profiles/threat-prevention/update-override index bcb522741..84b12c522 100644 --- a/gcloud/beta/network-security/security-profiles/threat-prevention/update-override +++ b/gcloud/beta/network-security/security-profiles/threat-prevention/update-override @@ -35,8 +35,17 @@ EXAMPLES POSITIONAL ARGUMENTS Security profile resource - Security Profile Name. The arguments in this - group can be used to specify the attributes of this resource. This - resource can be one of the following types: [security_profile]. + 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 security_profile on the command line with a + fully specified name; + ◆ set the property core/project. This resource can be one of the + following types: + [networksecurity.organizations.locations.securityProfiles, + networksecurity.projects.locations.securityProfiles]. This must be specified. @@ -64,7 +73,9 @@ POSITIONAL ARGUMENTS To set the organization attribute: ▸ provide the argument security_profile on the command line with a fully specified name; - ▸ provide the argument --organization on the command line. + ▸ provide the argument --organization on the command line. Must be + specified for resource of type + [networksecurity.organizations.locations.securityProfiles]. REQUIRED FLAGS --action=ACTION diff --git a/gcloud/beta/network-security/security-profiles/url-filtering/create b/gcloud/beta/network-security/security-profiles/url-filtering/create index f0de73282..38cc97baa 100644 --- a/gcloud/beta/network-security/security-profiles/url-filtering/create +++ b/gcloud/beta/network-security/security-profiles/url-filtering/create @@ -21,8 +21,17 @@ EXAMPLES POSITIONAL ARGUMENTS Security profile resource - Security Profile Name. The arguments in this - group can be used to specify the attributes of this resource. This - resource can be one of the following types: [security_profile]. + 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 security_profile on the command line with a + fully specified name; + ◆ set the property core/project. This resource can be one of the + following types: + [networksecurity.organizations.locations.securityProfiles, + networksecurity.projects.locations.securityProfiles]. This must be specified. @@ -50,7 +59,9 @@ POSITIONAL ARGUMENTS To set the organization attribute: ▸ provide the argument security_profile on the command line with a fully specified name; - ▸ provide the argument --organization on the command line. + ▸ provide the argument --organization on the command line. Must be + specified for resource of type + [networksecurity.organizations.locations.securityProfiles]. FLAGS --async diff --git a/gcloud/beta/network-security/security-profiles/url-filtering/delete b/gcloud/beta/network-security/security-profiles/url-filtering/delete index 5a2f00b32..c891e0ce7 100644 --- a/gcloud/beta/network-security/security-profiles/url-filtering/delete +++ b/gcloud/beta/network-security/security-profiles/url-filtering/delete @@ -18,8 +18,17 @@ EXAMPLES POSITIONAL ARGUMENTS Security profile resource - Security Profile Name. The arguments in this - group can be used to specify the attributes of this resource. This - resource can be one of the following types: [security_profile]. + 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 security_profile on the command line with a + fully specified name; + ◆ set the property core/project. This resource can be one of the + following types: + [networksecurity.organizations.locations.securityProfiles, + networksecurity.projects.locations.securityProfiles]. This must be specified. @@ -47,7 +56,9 @@ POSITIONAL ARGUMENTS To set the organization attribute: ▸ provide the argument security_profile on the command line with a fully specified name; - ▸ provide the argument --organization on the command line. + ▸ provide the argument --organization on the command line. Must be + specified for resource of type + [networksecurity.organizations.locations.securityProfiles]. FLAGS --async diff --git a/gcloud/beta/network-security/security-profiles/url-filtering/describe b/gcloud/beta/network-security/security-profiles/url-filtering/describe index d0b8f1079..56de0f109 100644 --- a/gcloud/beta/network-security/security-profiles/url-filtering/describe +++ b/gcloud/beta/network-security/security-profiles/url-filtering/describe @@ -18,8 +18,17 @@ EXAMPLES POSITIONAL ARGUMENTS Security profile resource - Security Profile Name. The arguments in this - group can be used to specify the attributes of this resource. This - resource can be one of the following types: [security_profile]. + 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 security_profile on the command line with a + fully specified name; + ◆ set the property core/project. This resource can be one of the + following types: + [networksecurity.organizations.locations.securityProfiles, + networksecurity.projects.locations.securityProfiles]. This must be specified. @@ -47,7 +56,9 @@ POSITIONAL ARGUMENTS To set the organization attribute: ▸ provide the argument security_profile on the command line with a fully specified name; - ▸ provide the argument --organization on the command line. + ▸ provide the argument --organization on the command line. Must be + specified for resource of type + [networksecurity.organizations.locations.securityProfiles]. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/beta/network-security/security-profiles/url-filtering/list b/gcloud/beta/network-security/security-profiles/url-filtering/list index 757542004..905502a43 100644 --- a/gcloud/beta/network-security/security-profiles/url-filtering/list +++ b/gcloud/beta/network-security/security-profiles/url-filtering/list @@ -20,8 +20,16 @@ EXAMPLES REQUIRED FLAGS Location resource - Parent resource for the list operation. The arguments - in this group can be used to specify the attributes of this resource. This - resource can be one of the following types: [location]. + 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 --location on the command line with a fully + specified name; + ◆ set the property core/project. This resource can be one of the + following types: [networksecurity.organizations.locations, + networksecurity.projects.locations]. This must be specified. @@ -40,7 +48,9 @@ REQUIRED FLAGS To set the organization attribute: ▸ provide the argument --location on the command line with a fully specified name; - ▸ provide the argument --organization on the command line. + ▸ provide the argument --organization on the command line. Must be + specified for resource of type + [networksecurity.organizations.locations]. LIST COMMAND FLAGS --filter=EXPRESSION diff --git a/gcloud/beta/network-services/agent-gateways/delete b/gcloud/beta/network-services/agent-gateways/delete new file mode 100644 index 000000000..dc7606bdf --- /dev/null +++ b/gcloud/beta/network-services/agent-gateways/delete @@ -0,0 +1,71 @@ +NAME + gcloud beta network-services agent-gateways delete - delete an AgentGateway + +SYNOPSIS + gcloud beta network-services agent-gateways delete + (AGENT_GATEWAY : --location=LOCATION) [--async] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Delete the specified AgentGateway. + +EXAMPLES + To delete a AgentGateway named 'my-agentgateway', run: + + $ gcloud beta network-services agent-gateways delete \ + my-agent-gateway --location=us-central1 + +POSITIONAL ARGUMENTS + Agent gateway resource - Name of the agent gateway 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 agent_gateway 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. + + AGENT_GATEWAY + ID of the agent gateway or fully qualified identifier for the agent + gateway. + + To set the agent_gateway attribute: + ▸ provide the argument agent_gateway 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 agent_gateway on the command line with a + fully specified name; + ▸ provide the argument --location on the command line. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the networkservices/v1beta1 API. The full documentation + for this API can be found at: https://cloud.google.com/networking + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha network-services agent-gateways delete + diff --git a/gcloud/beta/lifesciences/operations/cancel b/gcloud/beta/network-services/agent-gateways/describe similarity index 50% rename from gcloud/beta/lifesciences/operations/cancel rename to gcloud/beta/network-services/agent-gateways/describe index ffe6525fb..20b0a5e0e 100644 --- a/gcloud/beta/lifesciences/operations/cancel +++ b/gcloud/beta/network-services/agent-gateways/describe @@ -1,50 +1,51 @@ NAME - gcloud beta lifesciences operations cancel - cancel a Cloud Life Sciences - operation + gcloud beta network-services agent-gateways describe - describe a Agent + Gateway SYNOPSIS - gcloud beta lifesciences operations cancel - (OPERATION : --location=LOCATION) [GCLOUD_WIDE_FLAG ...] + gcloud beta network-services agent-gateways describe + (AGENT_GATEWAY : --location=LOCATION) [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) Cancel a Cloud Life Sciences operation. + (BETA) Show details of an Agent Gateway. EXAMPLES - To cancel an operation called my-operation, run: + Show details about an Agent Gateway named 'my-agent-gateway'. - $ gcloud beta lifesciences operations cancel my-operation + $ gcloud beta network-services agent-gateways describe \ + my-agent-gateway --location=us-central1 POSITIONAL ARGUMENTS - Operation resource - Cloud Life Sciences operation to cancel. The + Agent gateway resource - Name of the agent gateway 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 + ◆ provide the argument agent_gateway 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. + AGENT_GATEWAY + ID of the agent gateway or fully qualified identifier for the agent + gateway. - To set the operation attribute: - ▸ provide the argument operation on the command line. + To set the agent_gateway attribute: + ▸ provide the argument agent_gateway 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. + 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; - ▸ set the property lifesciences/location. + ▸ provide the argument agent_gateway on the command line with a + fully specified name; + ▸ provide the argument --location on the command line. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, @@ -55,12 +56,12 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. API REFERENCE - This command uses the lifesciences/v2beta API. The full documentation for - this API can be found at: https://cloud.google.com/life-sciences + This command uses the networkservices/v1beta1 API. The full documentation + for this API can be found at: https://cloud.google.com/networking NOTES This command is currently in beta and might change without notice. This variant is also available: - $ gcloud alpha lifesciences operations cancel + $ gcloud alpha network-services agent-gateways describe diff --git a/gcloud/beta/network-services/agent-gateways/export b/gcloud/beta/network-services/agent-gateways/export new file mode 100644 index 000000000..8def6e343 --- /dev/null +++ b/gcloud/beta/network-services/agent-gateways/export @@ -0,0 +1,76 @@ +NAME + gcloud beta network-services agent-gateways export - export an AgentGateway + +SYNOPSIS + gcloud beta network-services agent-gateways export + (AGENT_GATEWAY : --location=LOCATION) [--destination=DESTINATION] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Export an AgentGateway. + +EXAMPLES + To export an AgentGateway named 'my-agentgateway' to a YAML file, run: + + $ gcloud beta network-services agent-gateways export \ + my-agent-gateway --location=us-central1 \ + --destination=my-agentgateway.yaml + +POSITIONAL ARGUMENTS + Agent gateway resource - Name of the agent gateway to export. 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 agent_gateway 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. + + AGENT_GATEWAY + ID of the agent gateway or fully qualified identifier for the agent + gateway. + + To set the agent_gateway attribute: + ▸ provide the argument agent_gateway 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 agent_gateway on the command line with a + fully specified name; + ▸ provide the argument --location on the command line. + +FLAGS + --destination=DESTINATION + Path to a YAML file where the configuration will be exported. The + exported data will not contain any output-only fields. Alternatively, + you may omit this flag to write to standard output. For a schema + describing the export/import format, see + $CLOUDSDKROOT/lib/googlecloudsdk/schemas/... + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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/v1beta1 API. The full documentation + for this API can be found at: https://cloud.google.com/networking + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha network-services agent-gateways export + diff --git a/gcloud/beta/network-services/agent-gateways/help b/gcloud/beta/network-services/agent-gateways/help new file mode 100644 index 000000000..804881de3 --- /dev/null +++ b/gcloud/beta/network-services/agent-gateways/help @@ -0,0 +1,39 @@ +NAME + gcloud beta network-services agent-gateways - manage Network Services + AgentGateways + +SYNOPSIS + gcloud beta network-services agent-gateways COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Manage Network Services AgentGateways. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + delete + (BETA) Delete an AgentGateway. + + describe + (BETA) Describe a Agent Gateway. + + export + (BETA) Export an AgentGateway. + + import + (BETA) Import an AgentGateway. + + list + (BETA) List AgentGateways. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha network-services agent-gateways + diff --git a/gcloud/beta/network-services/agent-gateways/import b/gcloud/beta/network-services/agent-gateways/import new file mode 100644 index 000000000..459974ad6 --- /dev/null +++ b/gcloud/beta/network-services/agent-gateways/import @@ -0,0 +1,83 @@ +NAME + gcloud beta network-services agent-gateways import - import an AgentGateway + +SYNOPSIS + gcloud beta network-services agent-gateways import + (AGENT_GATEWAY : --location=LOCATION) [--async] [--source=SOURCE] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Import a agent gateway. + +EXAMPLES + To import a agent gateway named 'my-agentgateway' from a YAML file, run: + + $ gcloud beta network-services agent-gateways import \ + my-agent-gateway --location=us-central1 \ + --source=my-agentgateway.yaml + +POSITIONAL ARGUMENTS + Agent gateway resource - Name of the agent gateway to import. 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 agent_gateway 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. + + AGENT_GATEWAY + ID of the agent gateway or fully qualified identifier for the agent + gateway. + + To set the agent_gateway attribute: + ▸ provide the argument agent_gateway 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 agent_gateway on the command line with a + fully specified name; + ▸ provide the argument --location on the command line. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --source=SOURCE + Path to a YAML file containing the configuration export data. The YAML + file must not contain any output-only fields. Alternatively, you may + omit this flag to read from standard input. For a schema describing the + export/import format, see: $CLOUDSDKROOT/lib/googlecloudsdk/schemas/... + + $CLOUDSDKROOT is can be obtained with the following command: + + $ gcloud info --format='value(installation.sdk_root)' + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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/v1beta1 API. The full documentation + for this API can be found at: https://cloud.google.com/networking + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha network-services agent-gateways import + diff --git a/gcloud/beta/network-services/agent-gateways/list b/gcloud/beta/network-services/agent-gateways/list new file mode 100644 index 000000000..ad0a646c9 --- /dev/null +++ b/gcloud/beta/network-services/agent-gateways/list @@ -0,0 +1,87 @@ +NAME + gcloud beta network-services agent-gateways list - list AgentGateways + +SYNOPSIS + gcloud beta network-services agent-gateways list --location=LOCATION + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) List all agent gateways in the specified location of the current + project. + +EXAMPLES + To list agent gateways in the current project, run: + + $ gcloud beta network-services agent-gateways list \ + --location=us-central1 + +REQUIRED FLAGS + Location resource - Location to list agent gateways in. 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/v1beta1 API. The full documentation + for this API can be found at: https://cloud.google.com/networking + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha network-services agent-gateways list + diff --git a/gcloud/beta/network-services/help b/gcloud/beta/network-services/help index ff3206ed7..e0da2078b 100644 --- a/gcloud/beta/network-services/help +++ b/gcloud/beta/network-services/help @@ -15,6 +15,9 @@ GCLOUD WIDE FLAGS GROUPS GROUP is one of the following: + agent-gateways + (BETA) Manage Network Services AgentGateways. + endpoint-policies (BETA) Manage Network Services EndpointPolicies. diff --git a/gcloud/beta/pam/grants/create b/gcloud/beta/pam/grants/create index 116978503..9580eb59e 100644 --- a/gcloud/beta/pam/grants/create +++ b/gcloud/beta/pam/grants/create @@ -8,6 +8,7 @@ SYNOPSIS : --folder=FOLDER --location=LOCATION --organization=ORGANIZATION) [--additional-email-recipients=[ADDITIONAL_EMAIL_RECIPIENTS,...]] [--justification=JUSTIFICATION] + [--scheduled-activation-time=SCHEDULED_ACTIVATION_TIME] [--requested-access-from-file=[REQUESTED_ACCESS_FROM_FILE,...] | --requested-resources=[REQUESTED_RESOURCES,...]] [GCLOUD_WIDE_FLAG ...] @@ -94,6 +95,11 @@ OPTIONAL FLAGS --justification=JUSTIFICATION Justification for the grant. + --scheduled-activation-time=SCHEDULED_ACTIVATION_TIME + To schedule the grant, specify a start date and time up to 7 days in + the future. If not scheduled, the grant activates immediately upon + creation or approval(s). + Specify the grant's scope using either high-level resource or a fine-grained scope configuration. diff --git a/gcloud/beta/redis/clusters/create b/gcloud/beta/redis/clusters/create index 544a25255..6c9590821 100644 --- a/gcloud/beta/redis/clusters/create +++ b/gcloud/beta/redis/clusters/create @@ -184,7 +184,8 @@ FLAGS --node-type=NODE_TYPE Node Type of the redis cluster Node. NODE_TYPE must be one of: - redis-highmem-medium, redis-highmem-xlarge, redis-shared-core-nano, + redis-highcpu-medium, redis-highmem-2xlarge, redis-highmem-medium, + redis-highmem-xlarge, redis-shared-core-nano, redis-standard-large, redis-standard-small. --persistence-mode=PERSISTENCE_MODE diff --git a/gcloud/beta/redis/clusters/create-token-auth-user b/gcloud/beta/redis/clusters/create-token-auth-user new file mode 100644 index 000000000..570fe045c --- /dev/null +++ b/gcloud/beta/redis/clusters/create-token-auth-user @@ -0,0 +1,73 @@ +NAME + gcloud beta redis clusters create-token-auth-user - create a token auth + user for a Redis cluster + +SYNOPSIS + gcloud beta redis clusters create-token-auth-user + (CLUSTER : --region=REGION) [--async] + [--token-auth-user=TOKEN_AUTH_USER] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Create a token-auth user for a token-auth-enabled Redis cluster. An + initial token will be generated for the user. The username and token can be + used to authenticate a client connecting to the cluster. + +POSITIONAL ARGUMENTS + Cluster resource - Arguments and flags that specify the Memorystore Redis + cluster to create a backup for. The arguments in this group can be used to + specify the attributes of this resource. (NOTE) Some attributes are not + given arguments in this group but can be set in other ways. + + To set the project attribute: + ◆ provide the argument cluster on the command line with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + CLUSTER + ID of the cluster or fully qualified identifier for the cluster. + + To set the cluster attribute: + ▸ provide the argument cluster on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --region=REGION + The name of the Redis region of the cluster. Overrides the default + redis/region property value for this command invocation. + + To set the region attribute: + ▸ provide the argument cluster on the command line with a fully + specified name; + ▸ provide the argument --region on the command line; + ▸ set the property redis/region. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --token-auth-user=TOKEN_AUTH_USER + The name of the token auth user to be created. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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 redis/v1beta1 API. The full documentation for this + API can be found at: https://cloud.google.com/memorystore/docs/redis/ + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha redis clusters create-token-auth-user + diff --git a/gcloud/beta/redis/clusters/help b/gcloud/beta/redis/clusters/help index c140c821b..d3831a062 100644 --- a/gcloud/beta/redis/clusters/help +++ b/gcloud/beta/redis/clusters/help @@ -22,6 +22,10 @@ GROUPS backups (BETA) Manage backups of Memorystore for Redis Cluster instances. + token-auth-users + (BETA) Manage token auth users of Memorystore for Redis Cluster + instances. + COMMANDS COMMAND is one of the following: @@ -34,6 +38,9 @@ COMMANDS create-backup (BETA) Create a backup of a Redis cluster. + create-token-auth-user + (BETA) Create a token auth user for a Redis cluster. + delete (BETA) Delete a Memorystore for Redis Cluster instance. diff --git a/gcloud/beta/redis/clusters/token-auth-users/auth-tokens/delete b/gcloud/beta/redis/clusters/token-auth-users/auth-tokens/delete new file mode 100644 index 000000000..bc4077539 --- /dev/null +++ b/gcloud/beta/redis/clusters/token-auth-users/auth-tokens/delete @@ -0,0 +1,99 @@ +NAME + gcloud beta redis clusters token-auth-users auth-tokens delete - delete a + Memorystore for Redis Cluster auth token + +SYNOPSIS + gcloud beta redis clusters token-auth-users auth-tokens delete + (AUTH_TOKEN : --cluster=CLUSTER + --region=REGION --token-auth-user=TOKEN_AUTH_USER) [--async] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Delete a Memorystore for Redis Cluster auth token. + + This command can fail for the following reasons: + ▪ The auth token specified does not exist. + ▪ The active account does not have permission to access the given auth + token. + +EXAMPLES + To delete an auth token with the name my-auth-token of token auth user + my-token-auth-user under cluster my-cluster in us-central1 region, run: + + $ gcloud beta redis clusters token-auth-users auth-tokens delete \ + my-auth-token --token-auth-user=my-token-auth-user \ + --cluster=my-cluster --region=us-central1 + +POSITIONAL ARGUMENTS + Auth token resource - Arguments and flags that specify the Redis auth + token you want to delete. The arguments in this group can be used to + specify the attributes of this resource. (NOTE) Some attributes are not + given arguments in this group but can be set in other ways. + + To set the project attribute: + ◆ provide the argument auth_token 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. + + AUTH_TOKEN + ID of the auth token or fully qualified identifier for the auth + token. + + To set the auth_token attribute: + ▸ provide the argument auth_token on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --cluster=CLUSTER + The name of the Redis cluster. + + To set the cluster attribute: + ▸ provide the argument auth_token on the command line with a fully + specified name; + ▸ provide the argument --cluster on the command line. + + --region=REGION + The name of the Redis region of the auth token. Overrides the default + redis/region property value for this command invocation. + + To set the region attribute: + ▸ provide the argument auth_token on the command line with a fully + specified name; + ▸ provide the argument --region on the command line; + ▸ set the property redis/region. + + --token-auth-user=TOKEN_AUTH_USER + The name of the Redis cluster token auth user. + + To set the token-auth-user attribute: + ▸ provide the argument auth_token on the command line with a fully + specified name; + ▸ provide the argument --token-auth-user 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 redis/v1beta1 API. The full documentation for this + API can be found at: https://cloud.google.com/memorystore/docs/redis/ + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha redis clusters token-auth-users auth-tokens delete + diff --git a/gcloud/beta/redis/clusters/token-auth-users/auth-tokens/describe b/gcloud/beta/redis/clusters/token-auth-users/auth-tokens/describe new file mode 100644 index 000000000..0209fec61 --- /dev/null +++ b/gcloud/beta/redis/clusters/token-auth-users/auth-tokens/describe @@ -0,0 +1,97 @@ +NAME + gcloud beta redis clusters token-auth-users auth-tokens describe - show + metadata for a Memorystore for Redis Cluster auth token + +SYNOPSIS + gcloud beta redis clusters token-auth-users auth-tokens describe + (AUTH_TOKEN : --cluster=CLUSTER + --region=REGION --token-auth-user=TOKEN_AUTH_USER) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Show metadata for a Memorystore for Redis Cluster auth token. + + Displays all metadata associated with an auth token given a valid auth + token name. + + This command can fail for the following reasons: + ▪ The auth token specified does not exist. + ▪ The active account does not have permission to access the given auth + token. + +EXAMPLES + To display metadata for an auth token named my-auth-token for the user + my-token-auth-user in the my-cluster cluster in us-central1 region, run: + + $ gcloud beta redis clusters token-auth-users auth-tokens describe \ + my-auth-token --cluster=my-cluster \ + --token-auth-user=my-token-auth-user --region=us-central1 + +POSITIONAL ARGUMENTS + Auth token resource - The name of the Redis cluster auth token you want to + describe. The arguments in this group can be used to specify the + attributes of this resource. (NOTE) Some attributes are not given + arguments in this group but can be set in other ways. + + To set the project attribute: + ◆ provide the argument auth_token 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. + + AUTH_TOKEN + ID of the auth token or fully qualified identifier for the auth + token. + + To set the auth_token attribute: + ▸ provide the argument auth_token on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --cluster=CLUSTER + The name of the Redis cluster. + + To set the cluster attribute: + ▸ provide the argument auth_token on the command line with a fully + specified name; + ▸ provide the argument --cluster on the command line. + + --region=REGION + The name of the Redis region of the auth token. Overrides the default + redis/region property value for this command invocation. + + To set the region attribute: + ▸ provide the argument auth_token on the command line with a fully + specified name; + ▸ provide the argument --region on the command line; + ▸ set the property redis/region. + + --token-auth-user=TOKEN_AUTH_USER + The name of the Redis cluster token auth user. + + To set the token-auth-user attribute: + ▸ provide the argument auth_token on the command line with a fully + specified name; + ▸ provide the argument --token-auth-user 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 redis/v1beta1 API. The full documentation for this + API can be found at: https://cloud.google.com/memorystore/docs/redis/ + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha redis clusters token-auth-users auth-tokens describe + diff --git a/gcloud/beta/redis/clusters/token-auth-users/auth-tokens/help b/gcloud/beta/redis/clusters/token-auth-users/auth-tokens/help new file mode 100644 index 000000000..14eb76d05 --- /dev/null +++ b/gcloud/beta/redis/clusters/token-auth-users/auth-tokens/help @@ -0,0 +1,34 @@ +NAME + gcloud beta redis clusters token-auth-users auth-tokens - manage auth + tokens of Memorystore for Redis Cluster instances + +SYNOPSIS + gcloud beta redis clusters token-auth-users auth-tokens COMMAND + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Manage auth tokens of Memorystore for Redis Cluster instances. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + delete + (BETA) Delete a Memorystore for Redis Cluster auth token. + + describe + (BETA) Show metadata for a Memorystore for Redis Cluster auth token. + + list + (BETA) List auth tokens for a token auth user. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha redis clusters token-auth-users auth-tokens + diff --git a/gcloud/beta/redis/clusters/token-auth-users/auth-tokens/list b/gcloud/beta/redis/clusters/token-auth-users/auth-tokens/list new file mode 100644 index 000000000..fa7411aff --- /dev/null +++ b/gcloud/beta/redis/clusters/token-auth-users/auth-tokens/list @@ -0,0 +1,114 @@ +NAME + gcloud beta redis clusters token-auth-users auth-tokens list - list auth + tokens for a token auth user + +SYNOPSIS + gcloud beta redis clusters token-auth-users auth-tokens list + (--token-auth-user=TOKEN_AUTH_USER : --cluster=CLUSTER --region=REGION) + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) List auth tokens for a token auth user. + +EXAMPLES + To list up to 2 auth tokens for a token auth user named + 'my-token-auth-user' on a cluster named 'my-cluster' in the us-central1 + region, run: + + $ gcloud beta redis clusters token-auth-users auth-tokens list \ + --cluster=my-cluster --token-auth-user=my-token-auth-user \ + --region=us-central1 --limit=2 + +REQUIRED FLAGS + Token auth user resource - The token auth user to whom the auth tokens + belong. 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 --token-auth-user 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. + + --token-auth-user=TOKEN_AUTH_USER + ID of the token auth user or fully qualified identifier for the token + auth user. + + To set the token-auth-user attribute: + ▸ provide the argument --token-auth-user on the command line. + + This flag argument must be specified if any of the other arguments in + this group are specified. + + --cluster=CLUSTER + The name of the Redis cluster. + + To set the cluster attribute: + ▸ provide the argument --token-auth-user on the command line with a + fully specified name; + ▸ provide the argument --cluster on the command line. + + --region=REGION + The name of the Redis region of the token auth user. Overrides the + default redis/region property value for this command invocation. + + To set the region attribute: + ▸ provide the argument --token-auth-user on the command line with a + fully specified name; + ▸ provide the argument --region on the command line; + ▸ set the property redis/region. + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + + --uri + Print a list of resource URIs instead of the default output, and change + the command output to a list of URIs. If this flag is used with + --format, the formatting is applied on this URI list. To display URIs + alongside other keys instead, use the uri() transform. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the redis/v1beta1 API. The full documentation for this + API can be found at: https://cloud.google.com/memorystore/docs/redis/ + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha redis clusters token-auth-users auth-tokens list + diff --git a/gcloud/beta/redis/clusters/token-auth-users/create-auth-token b/gcloud/beta/redis/clusters/token-auth-users/create-auth-token new file mode 100644 index 000000000..411116d08 --- /dev/null +++ b/gcloud/beta/redis/clusters/token-auth-users/create-auth-token @@ -0,0 +1,79 @@ +NAME + gcloud beta redis clusters token-auth-users create-auth-token - create an + auth token for a token auth user of a Redis cluster + +SYNOPSIS + gcloud beta redis clusters token-auth-users create-auth-token + (USER : --cluster=CLUSTER --region=REGION) [--async] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Create an auth token for a token auth user of a token auth enabled + Redis cluster. + +POSITIONAL ARGUMENTS + Token auth user resource - Arguments and flags that specify the + Memorystore Redis token auth user to create an auth token for. The + arguments in this group can be used to specify the attributes of this + resource. (NOTE) Some attributes are not given arguments in this group but + can be set in other ways. + + To set the project attribute: + ◆ provide the argument user 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. + + USER + ID of the token auth user or fully qualified identifier for the token + auth user. + + To set the token-auth-user attribute: + ▸ provide the argument user on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --cluster=CLUSTER + The name of the Redis cluster. + + To set the cluster attribute: + ▸ provide the argument user on the command line with a fully + specified name; + ▸ provide the argument --cluster on the command line. + + --region=REGION + The name of the Redis region of the token auth user. Overrides the + default redis/region property value for this command invocation. + + To set the region attribute: + ▸ provide the argument user on the command line with a fully + specified name; + ▸ provide the argument --region on the command line; + ▸ set the property redis/region. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the redis/v1beta1 API. The full documentation for this + API can be found at: https://cloud.google.com/memorystore/docs/redis/ + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha redis clusters token-auth-users create-auth-token + diff --git a/gcloud/beta/redis/clusters/token-auth-users/delete b/gcloud/beta/redis/clusters/token-auth-users/delete new file mode 100644 index 000000000..d234ceec6 --- /dev/null +++ b/gcloud/beta/redis/clusters/token-auth-users/delete @@ -0,0 +1,93 @@ +NAME + gcloud beta redis clusters token-auth-users delete - delete a Memorystore + for Redis Cluster token auth user + +SYNOPSIS + gcloud beta redis clusters token-auth-users delete + (TOKEN_AUTH_USER : --cluster=CLUSTER --region=REGION) [--async] + [--no-force] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Delete a Memorystore for Redis Cluster token auth user. + + This command can fail for the following reasons: + ▪ The token auth user specified does not exist. + ▪ The active account does not have permission to access the given token + auth user. + +EXAMPLES + To delete a token auth user with the name my-token-auth-user for cluster + my-cluster in us-central1 region, run: + + $ gcloud beta redis clusters token-auth-users delete \ + my-token-auth-user --cluster=my-cluster --region=us-central1 + +POSITIONAL ARGUMENTS + Token auth user resource - Arguments and flags that specify the Redis + token auth user you want to delete. The arguments in this group can be + used to specify the attributes of this resource. (NOTE) Some attributes + are not given arguments in this group but can be set in other ways. + + To set the project attribute: + ◆ provide the argument token_auth_user 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. + + TOKEN_AUTH_USER + ID of the token auth user or fully qualified identifier for the token + auth user. + + To set the token_auth_user attribute: + ▸ provide the argument token_auth_user on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --cluster=CLUSTER + The name of the Redis cluster. + + To set the cluster attribute: + ▸ provide the argument token_auth_user on the command line with a + fully specified name; + ▸ provide the argument --cluster on the command line. + + --region=REGION + The name of the Redis region of the token auth user. Overrides the + default redis/region property value for this command invocation. + + To set the region attribute: + ▸ provide the argument token_auth_user on the command line with a + fully specified name; + ▸ provide the argument --region on the command line; + ▸ set the property redis/region. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --force + If set to true, the token auth user and its nested resources will be + deleted. Enabled by default, use --no-force to disable. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the redis/v1beta1 API. The full documentation for this + API can be found at: https://cloud.google.com/memorystore/docs/redis/ + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha redis clusters token-auth-users delete + diff --git a/gcloud/beta/redis/clusters/token-auth-users/describe b/gcloud/beta/redis/clusters/token-auth-users/describe new file mode 100644 index 000000000..d83aed85b --- /dev/null +++ b/gcloud/beta/redis/clusters/token-auth-users/describe @@ -0,0 +1,87 @@ +NAME + gcloud beta redis clusters token-auth-users describe - show metadata for a + Memorystore for Redis Cluster token auth user + +SYNOPSIS + gcloud beta redis clusters token-auth-users describe + (TOKEN_AUTH_USER : --cluster=CLUSTER --region=REGION) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Show metadata for a Memorystore for Redis Cluster token auth user. + + Displays all metadata associated with a token auth user given a valid token + auth user name. + + This command can fail for the following reasons: + ▪ The token auth user specified does not exist. + ▪ The active account does not have permission to access the given token + auth user. + +EXAMPLES + To display the metadata for a token auth user named my-token-auth-user for + cluster my-cluster in us-central1 region, run: + + $ gcloud beta redis clusters token-auth-users describe \ + my-token-auth-user --cluster=my-cluster --region=us-central1 + +POSITIONAL ARGUMENTS + Token auth user resource - The name of the Redis cluster token auth user + you want to describe. The arguments in this group can be used to specify + the attributes of this resource. (NOTE) Some attributes are not given + arguments in this group but can be set in other ways. + + To set the project attribute: + ◆ provide the argument token_auth_user 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. + + TOKEN_AUTH_USER + ID of the token auth user or fully qualified identifier for the token + auth user. + + To set the token_auth_user attribute: + ▸ provide the argument token_auth_user on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --cluster=CLUSTER + The name of the Redis cluster. + + To set the cluster attribute: + ▸ provide the argument token_auth_user on the command line with a + fully specified name; + ▸ provide the argument --cluster on the command line. + + --region=REGION + The name of the Redis region of the token auth user. Overrides the + default redis/region property value for this command invocation. + + To set the region attribute: + ▸ provide the argument token_auth_user on the command line with a + fully specified name; + ▸ provide the argument --region on the command line; + ▸ set the property redis/region. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the redis/v1beta1 API. The full documentation for this + API can be found at: https://cloud.google.com/memorystore/docs/redis/ + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha redis clusters token-auth-users describe + diff --git a/gcloud/beta/redis/clusters/token-auth-users/help b/gcloud/beta/redis/clusters/token-auth-users/help new file mode 100644 index 000000000..f86a8ea98 --- /dev/null +++ b/gcloud/beta/redis/clusters/token-auth-users/help @@ -0,0 +1,44 @@ +NAME + gcloud beta redis clusters token-auth-users - manage token auth users of + Memorystore for Redis Cluster instances + +SYNOPSIS + gcloud beta redis clusters token-auth-users GROUP | COMMAND + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Manage token auth users of Memorystore for Redis Cluster instances. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +GROUPS + GROUP is one of the following: + + auth-tokens + (BETA) Manage auth tokens of Memorystore for Redis Cluster instances. + +COMMANDS + COMMAND is one of the following: + + create-auth-token + (BETA) Create an auth token for a token auth user of a Redis cluster. + + delete + (BETA) Delete a Memorystore for Redis Cluster token auth user. + + describe + (BETA) Show metadata for a Memorystore for Redis Cluster token auth + user. + + list + (BETA) List token auth users of a Redis cluster in a region. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha redis clusters token-auth-users + diff --git a/gcloud/beta/redis/clusters/token-auth-users/list b/gcloud/beta/redis/clusters/token-auth-users/list new file mode 100644 index 000000000..6c218c4c7 --- /dev/null +++ b/gcloud/beta/redis/clusters/token-auth-users/list @@ -0,0 +1,103 @@ +NAME + gcloud beta redis clusters token-auth-users list - list token auth users of + a Redis cluster in a region + +SYNOPSIS + gcloud beta redis clusters token-auth-users list + (--cluster=CLUSTER : --region=REGION) [--filter=EXPRESSION] + [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) List token auth users of a Redis cluster in a region. + +EXAMPLES + To list up to 5 token auth users for a cluster named 'my-cluster' in the + us-central1 region, run: + + $ gcloud beta redis clusters token-auth-users list \ + --cluster=my-cluster --region=us-central1 --limit=5 + +REQUIRED FLAGS + Cluster resource - The cluster of the token auth users to display. The + arguments in this group can be used to specify the attributes of this + resource. (NOTE) Some attributes are not given arguments in this group but + can be set in other ways. + + To set the project attribute: + ◆ provide the argument --cluster on the command line with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + --cluster=CLUSTER + ID of the cluster or fully qualified identifier for the cluster. + + To set the cluster attribute: + ▸ provide the argument --cluster on the command line. + + This flag argument must be specified if any of the other arguments in + this group are specified. + + --region=REGION + The name of the Redis region of the cluster. Overrides the default + redis/region property value for this command invocation. + + To set the region attribute: + ▸ provide the argument --cluster on the command line with a fully + specified name; + ▸ provide the argument --region on the command line; + ▸ set the property redis/region. + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + + --uri + Print a list of resource URIs instead of the default output, and change + the command output to a list of URIs. If this flag is used with + --format, the formatting is applied on this URI list. To display URIs + alongside other keys instead, use the uri() transform. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the redis/v1beta1 API. The full documentation for this + API can be found at: https://cloud.google.com/memorystore/docs/redis/ + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha redis clusters token-auth-users list + diff --git a/gcloud/beta/redis/clusters/update b/gcloud/beta/redis/clusters/update index 74423dde4..59a9e395f 100644 --- a/gcloud/beta/redis/clusters/update +++ b/gcloud/beta/redis/clusters/update @@ -129,7 +129,8 @@ FLAGS --node-type=NODE_TYPE Node Type of the redis cluster Node. NODE_TYPE must be one of: - redis-highmem-medium, redis-highmem-xlarge, redis-shared-core-nano, + redis-highcpu-medium, redis-highmem-2xlarge, redis-highmem-medium, + redis-highmem-xlarge, redis-shared-core-nano, redis-standard-large, redis-standard-small. --persistence-mode=PERSISTENCE_MODE diff --git a/gcloud/beta/run/deploy b/gcloud/beta/run/deploy index 95f2a9427..232bd9c44 100644 --- a/gcloud/beta/run/deploy +++ b/gcloud/beta/run/deploy @@ -15,6 +15,8 @@ SYNOPSIS [--min-instances=MIN_INSTANCES] [--region=REGION] [--regions=REGIONS] [--remove-containers=[CONTAINER,...]] [--revision-suffix=REVISION_SUFFIX] [--scaling=SCALING] + [--scaling-concurrency-target=SCALING_CONCURRENCY_TARGET] + [--scaling-cpu-target=SCALING_CPU_TARGET] [--service-account=SERVICE_ACCOUNT] [--[no-]session-affinity] [--tag=TAG] [--timeout=TIMEOUT] [--no-traffic] [--vpc-connector=VPC_CONNECTOR] [--vpc-egress=VPC_EGRESS] @@ -283,6 +285,22 @@ FLAGS "auto" for automatic scaling, or a positive integer to configure manual scaling with the given integer as a fixed instance count. + --scaling-concurrency-target=SCALING_CONCURRENCY_TARGET + This represents the concurrency utilization target threshold for + scaling up new instances. Set any value between 0.1 and 0.95 inclusive. + To unset this field, pass the special value "default". To disable this + scaling factor, pass the value "disabled". Please note that values are + rounded at the second decimal place, and that CPU and concurrency + scaling cannot both be disabled. + + --scaling-cpu-target=SCALING_CPU_TARGET + This represents the CPU utilization target threshold for scaling up new + instances. Set any value between 0.1 and 0.95 inclusive. To unset this + field, pass the special value "default". To disable this scaling + factor, pass the value "disabled". Please note that values are rounded + at the second decimal place, and that CPU and concurrency scaling + cannot both be disabled. + --service-account=SERVICE_ACCOUNT the email address of an IAM service account associated with the revision of the service. The service account represents the identity of diff --git a/gcloud/beta/run/multi-region-services/update b/gcloud/beta/run/multi-region-services/update index ded3a39cd..a95baba53 100644 --- a/gcloud/beta/run/multi-region-services/update +++ b/gcloud/beta/run/multi-region-services/update @@ -17,6 +17,8 @@ SYNOPSIS [--min-instances=MIN_INSTANCES] [--region=REGION] [--remove-containers=[CONTAINER,...]] [--revision-suffix=REVISION_SUFFIX] [--scaling=SCALING] + [--scaling-concurrency-target=SCALING_CONCURRENCY_TARGET] + [--scaling-cpu-target=SCALING_CPU_TARGET] [--service-account=SERVICE_ACCOUNT] [--[no-]session-affinity] [--tag=TAG] [--timeout=TIMEOUT] [--no-traffic] [--vpc-connector=VPC_CONNECTOR] [--vpc-egress=VPC_EGRESS] @@ -238,6 +240,22 @@ FLAGS "auto" for automatic scaling, or a positive integer to configure manual scaling with the given integer as a fixed instance count. + --scaling-concurrency-target=SCALING_CONCURRENCY_TARGET + This represents the concurrency utilization target threshold for + scaling up new instances. Set any value between 0.1 and 0.95 inclusive. + To unset this field, pass the special value "default". To disable this + scaling factor, pass the value "disabled". Please note that values are + rounded at the second decimal place, and that CPU and concurrency + scaling cannot both be disabled. + + --scaling-cpu-target=SCALING_CPU_TARGET + This represents the CPU utilization target threshold for scaling up new + instances. Set any value between 0.1 and 0.95 inclusive. To unset this + field, pass the special value "default". To disable this scaling + factor, pass the value "disabled". Please note that values are rounded + at the second decimal place, and that CPU and concurrency scaling + cannot both be disabled. + --service-account=SERVICE_ACCOUNT the email address of an IAM service account associated with the revision of the service. The service account represents the identity of diff --git a/gcloud/beta/run/services/update b/gcloud/beta/run/services/update index a2372ff53..16473541f 100644 --- a/gcloud/beta/run/services/update +++ b/gcloud/beta/run/services/update @@ -15,6 +15,8 @@ SYNOPSIS [--min-instances=MIN_INSTANCES] [--region=REGION] [--remove-containers=[CONTAINER,...]] [--revision-suffix=REVISION_SUFFIX] [--scaling=SCALING] + [--scaling-concurrency-target=SCALING_CONCURRENCY_TARGET] + [--scaling-cpu-target=SCALING_CPU_TARGET] [--service-account=SERVICE_ACCOUNT] [--[no-]session-affinity] [--tag=TAG] [--timeout=TIMEOUT] [--no-traffic] [--vpc-connector=VPC_CONNECTOR] [--vpc-egress=VPC_EGRESS] @@ -254,6 +256,22 @@ FLAGS "auto" for automatic scaling, or a positive integer to configure manual scaling with the given integer as a fixed instance count. + --scaling-concurrency-target=SCALING_CONCURRENCY_TARGET + This represents the concurrency utilization target threshold for + scaling up new instances. Set any value between 0.1 and 0.95 inclusive. + To unset this field, pass the special value "default". To disable this + scaling factor, pass the value "disabled". Please note that values are + rounded at the second decimal place, and that CPU and concurrency + scaling cannot both be disabled. + + --scaling-cpu-target=SCALING_CPU_TARGET + This represents the CPU utilization target threshold for scaling up new + instances. Set any value between 0.1 and 0.95 inclusive. To unset this + field, pass the special value "default". To disable this scaling + factor, pass the value "disabled". Please note that values are rounded + at the second decimal place, and that CPU and concurrency scaling + cannot both be disabled. + --service-account=SERVICE_ACCOUNT the email address of an IAM service account associated with the revision of the service. The service account represents the identity of diff --git a/gcloud/beta/run/worker-pools/add-iam-policy-binding b/gcloud/beta/run/worker-pools/add-iam-policy-binding index 4e20d42ec..5321112a3 100644 --- a/gcloud/beta/run/worker-pools/add-iam-policy-binding +++ b/gcloud/beta/run/worker-pools/add-iam-policy-binding @@ -131,8 +131,10 @@ API REFERENCE be found at: https://cloud.google.com/run/ 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 run worker-pools add-iam-policy-binding $ gcloud alpha run worker-pools add-iam-policy-binding diff --git a/gcloud/beta/run/worker-pools/delete b/gcloud/beta/run/worker-pools/delete index ff777c3a9..605ae8d64 100644 --- a/gcloud/beta/run/worker-pools/delete +++ b/gcloud/beta/run/worker-pools/delete @@ -62,8 +62,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 run worker-pools delete $ gcloud alpha run worker-pools delete diff --git a/gcloud/beta/run/worker-pools/deploy b/gcloud/beta/run/worker-pools/deploy index 5b18f81b9..5b50fa8d1 100644 --- a/gcloud/beta/run/worker-pools/deploy +++ b/gcloud/beta/run/worker-pools/deploy @@ -503,8 +503,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 run worker-pools deploy $ gcloud alpha run worker-pools deploy diff --git a/gcloud/beta/run/worker-pools/describe b/gcloud/beta/run/worker-pools/describe index b56969dbc..0b9c356c1 100644 --- a/gcloud/beta/run/worker-pools/describe +++ b/gcloud/beta/run/worker-pools/describe @@ -59,8 +59,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 run worker-pools describe $ gcloud alpha run worker-pools describe diff --git a/gcloud/beta/run/worker-pools/get-iam-policy b/gcloud/beta/run/worker-pools/get-iam-policy index 0fa3aecb4..d3e81c34f 100644 --- a/gcloud/beta/run/worker-pools/get-iam-policy +++ b/gcloud/beta/run/worker-pools/get-iam-policy @@ -93,8 +93,10 @@ API REFERENCE be found at: https://cloud.google.com/run/ 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 run worker-pools get-iam-policy $ gcloud alpha run worker-pools get-iam-policy diff --git a/gcloud/beta/run/worker-pools/help b/gcloud/beta/run/worker-pools/help index 9d7df96d9..91a2b3688 100644 --- a/gcloud/beta/run/worker-pools/help +++ b/gcloud/beta/run/worker-pools/help @@ -66,8 +66,10 @@ COMMANDS (BETA) Adjust the instance assignments for a Cloud Run worker-pool. 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 run worker-pools $ gcloud alpha run worker-pools diff --git a/gcloud/beta/run/worker-pools/list b/gcloud/beta/run/worker-pools/list index 689e297af..c6024857e 100644 --- a/gcloud/beta/run/worker-pools/list +++ b/gcloud/beta/run/worker-pools/list @@ -60,8 +60,10 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud run worker-pools list $ gcloud alpha run worker-pools list diff --git a/gcloud/beta/run/worker-pools/logs/help b/gcloud/beta/run/worker-pools/logs/help index 68c3ceee5..4ca2e26f2 100644 --- a/gcloud/beta/run/worker-pools/logs/help +++ b/gcloud/beta/run/worker-pools/logs/help @@ -37,8 +37,10 @@ COMMANDS (BETA) Tail logs for a Cloud Run worker pool. 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 run worker-pools logs $ gcloud alpha run worker-pools logs diff --git a/gcloud/beta/run/worker-pools/logs/read b/gcloud/beta/run/worker-pools/logs/read index 98dd834d2..32e1b4f5f 100644 --- a/gcloud/beta/run/worker-pools/logs/read +++ b/gcloud/beta/run/worker-pools/logs/read @@ -77,8 +77,10 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud run worker-pools logs read $ gcloud alpha run worker-pools logs read diff --git a/gcloud/beta/run/worker-pools/logs/tail b/gcloud/beta/run/worker-pools/logs/tail index baab980eb..ac0191a83 100644 --- a/gcloud/beta/run/worker-pools/logs/tail +++ b/gcloud/beta/run/worker-pools/logs/tail @@ -47,8 +47,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 run worker-pools logs tail $ gcloud alpha run worker-pools logs tail diff --git a/gcloud/beta/run/worker-pools/remove-iam-policy-binding b/gcloud/beta/run/worker-pools/remove-iam-policy-binding index 60f6d1ed4..85f88fda7 100644 --- a/gcloud/beta/run/worker-pools/remove-iam-policy-binding +++ b/gcloud/beta/run/worker-pools/remove-iam-policy-binding @@ -136,8 +136,10 @@ API REFERENCE be found at: https://cloud.google.com/run/ 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 run worker-pools remove-iam-policy-binding $ gcloud alpha run worker-pools remove-iam-policy-binding diff --git a/gcloud/beta/run/worker-pools/replace b/gcloud/beta/run/worker-pools/replace index de3158a05..84e7bc2b9 100644 --- a/gcloud/beta/run/worker-pools/replace +++ b/gcloud/beta/run/worker-pools/replace @@ -39,8 +39,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 run worker-pools replace $ gcloud alpha run worker-pools replace diff --git a/gcloud/beta/run/worker-pools/revisions/delete b/gcloud/beta/run/worker-pools/revisions/delete index f8a35cb7f..558a05086 100644 --- a/gcloud/beta/run/worker-pools/revisions/delete +++ b/gcloud/beta/run/worker-pools/revisions/delete @@ -14,7 +14,7 @@ EXAMPLES To delete a revision rev1 of a worker pool worker1 in us-central1: $ gcloud beta run worker-pools revisions delete rev1 \ - --region=us-central1 --workerpool=worker1 + --region=us-central1 --worker-pool=worker1 POSITIONAL ARGUMENTS WorkerPoolRevision resource - Worker pool revision to delete. The @@ -74,8 +74,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 run worker-pools revisions delete $ gcloud alpha run worker-pools revisions delete diff --git a/gcloud/beta/run/worker-pools/revisions/describe b/gcloud/beta/run/worker-pools/revisions/describe index 519a1a292..13606d051 100644 --- a/gcloud/beta/run/worker-pools/revisions/describe +++ b/gcloud/beta/run/worker-pools/revisions/describe @@ -10,10 +10,10 @@ DESCRIPTION (BETA) Obtain details about a given worker pool revision. EXAMPLES - To describe a revision rev.1 of a worker pool worker1 in us-central1: + To describe a revision rev.1 in us-central1: $ gcloud beta run worker-pools revisions describe rev.1 \ - --region=us-central1 --workerpool=worker1 + --region=us-central1 POSITIONAL ARGUMENTS Revision resource - Worker pool revision to describe. This represents a @@ -48,8 +48,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 run worker-pools revisions describe $ gcloud alpha run worker-pools revisions describe diff --git a/gcloud/beta/run/worker-pools/revisions/help b/gcloud/beta/run/worker-pools/revisions/help index ef000317d..3a91e6524 100644 --- a/gcloud/beta/run/worker-pools/revisions/help +++ b/gcloud/beta/run/worker-pools/revisions/help @@ -32,8 +32,10 @@ COMMANDS (BETA) List available worker pool revisions. 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 run worker-pools revisions $ gcloud alpha run worker-pools revisions diff --git a/gcloud/beta/run/worker-pools/revisions/list b/gcloud/beta/run/worker-pools/revisions/list index c2db75907..ea22ac57a 100644 --- a/gcloud/beta/run/worker-pools/revisions/list +++ b/gcloud/beta/run/worker-pools/revisions/list @@ -65,8 +65,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 run worker-pools revisions list $ gcloud alpha run worker-pools revisions list diff --git a/gcloud/beta/run/worker-pools/set-iam-policy b/gcloud/beta/run/worker-pools/set-iam-policy index a03832065..d88c6cbb6 100644 --- a/gcloud/beta/run/worker-pools/set-iam-policy +++ b/gcloud/beta/run/worker-pools/set-iam-policy @@ -80,8 +80,10 @@ API REFERENCE be found at: https://cloud.google.com/run/ 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 run worker-pools set-iam-policy $ gcloud alpha run worker-pools set-iam-policy diff --git a/gcloud/beta/run/worker-pools/update b/gcloud/beta/run/worker-pools/update index 744337265..3bf571fdb 100644 --- a/gcloud/beta/run/worker-pools/update +++ b/gcloud/beta/run/worker-pools/update @@ -481,8 +481,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 run worker-pools update $ gcloud alpha run worker-pools update diff --git a/gcloud/beta/run/worker-pools/update-instance-split b/gcloud/beta/run/worker-pools/update-instance-split index 147256449..d9f4dfdd1 100644 --- a/gcloud/beta/run/worker-pools/update-instance-split +++ b/gcloud/beta/run/worker-pools/update-instance-split @@ -126,8 +126,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 run worker-pools update-instance-split $ gcloud alpha run worker-pools update-instance-split diff --git a/gcloud/beta/saas-runtime/flags/attributes/create b/gcloud/beta/saas-runtime/flags/attributes/create index 5f0aa480f..8aed5adf7 100644 --- a/gcloud/beta/saas-runtime/flags/attributes/create +++ b/gcloud/beta/saas-runtime/flags/attributes/create @@ -9,12 +9,16 @@ SYNOPSIS [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) Create a Flag Attribute + (BETA) Create a new flag attribute resource. Flag attributes define the + data schema for targeting rules and percentage-based rollouts. These + attributes correspond to the keys in the OpenFeature EvaluationContext used + by the application SDK to provide contextual data for flag evaluation. EXAMPLES - To create a Flag Attribute, run: + To create a string attribute for user IDs in the global location, run: - $ gcloud beta saas-runtime flags attributes create + $ gcloud beta saas-runtime flags attributes create user-id-attr \ + --key=userID --attribute-value-type=string --location=global POSITIONAL ARGUMENTS FlagAttribute resource - Flag Attribute ID. Google Cloud resource name diff --git a/gcloud/beta/saas-runtime/flags/attributes/delete b/gcloud/beta/saas-runtime/flags/attributes/delete index 4cb473b70..3d06a0ce3 100644 --- a/gcloud/beta/saas-runtime/flags/attributes/delete +++ b/gcloud/beta/saas-runtime/flags/attributes/delete @@ -6,12 +6,30 @@ SYNOPSIS (FLAG_ATTRIBUTE : --location=LOCATION) [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) Delete a Flag Attribute + (BETA) Delete a Flag Attribute resource. + + This operation is permanent. To prevent evaluation errors in production, + the attribute MUST be removed from all active Flag evaluation + specifications before it is deleted. + + The safe deletion workflow is: + + 1. Identify all flags that reference this attribute in their `evaluation-spec`. + 2. Remove the attribute reference from those flags using `flags update` or delete the flags. + 3. Execute a `Rollout` for any affected flags to ensure the updated configuration is deployed to all units. + 4. Run this `delete` command to permanently remove the attribute definition. EXAMPLES - To delete a Flag Attribute, run: + To delete a Flag Attribute named user-id-attr in the global location, run: - $ gcloud beta saas-runtime flags attributes delete + $ gcloud beta saas-runtime flags attributes delete user-id-attr \ + --location=global + + To delete a Flag Attribute using a fully qualified resource name (useful + for automation), run: + + $ gcloud beta saas-runtime flags attributes delete \ + projects/my-project/locations/global/flagAttributes/user-id-attr POSITIONAL ARGUMENTS FlagAttribute resource - Flag Attribute ID of the Flag Attribute to diff --git a/gcloud/beta/saas-runtime/flags/attributes/describe b/gcloud/beta/saas-runtime/flags/attributes/describe index 5e19fad90..97bc54d74 100644 --- a/gcloud/beta/saas-runtime/flags/attributes/describe +++ b/gcloud/beta/saas-runtime/flags/attributes/describe @@ -7,12 +7,34 @@ SYNOPSIS (FLAG_ATTRIBUTE : --location=LOCATION) [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) Describe a Flag Attribute + (BETA) Show detailed information about a Flag Attribute resource. + + This command retrieves the metadata and configuration of a Flag Attribute. + Flag Attributes are the fundamental building blocks for targeted rollouts + and randomization, defining the keys (such as userID or version) that are + referenced in a flag's evaluation specification. + + For automated processing, use --format=json or --format=yaml to retrieve + the structured representation of the attribute, which can be useful for + programmatically verifying targeting schemas across environments. EXAMPLES - To describe a Flag Attribute, run: + To describe a Flag Attribute named user-id-attr in the global location, + run: - $ gcloud beta saas-runtime flags attributes describe + $ gcloud beta saas-runtime flags attributes describe user-id-attr \ + --location=global + + To describe a Flag Attribute using its fully qualified resource name, run: + + $ gcloud beta saas-runtime flags attributes describe \ + projects/my-project/locations/global/flagAttributes/user-id-attr + + To inspect the attribute configuration in JSON format for automated + auditing, run: + + $ gcloud beta saas-runtime flags attributes describe user-id-attr \ + --location=global --format=json POSITIONAL ARGUMENTS FlagAttribute resource - Flag Attribute ID of the Flag Attribute to diff --git a/gcloud/beta/saas-runtime/flags/attributes/list b/gcloud/beta/saas-runtime/flags/attributes/list index 20827143b..6fd0e4960 100644 --- a/gcloud/beta/saas-runtime/flags/attributes/list +++ b/gcloud/beta/saas-runtime/flags/attributes/list @@ -7,13 +7,39 @@ SYNOPSIS [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) List Flags Attributes + (BETA) List Flag Attributes available in a specific location for your SaaS + offerings. + + Use this command to audit available attributes (such as userID or tenantID) + used in feature flag evaluation specs to determine variant assignment. + These attributes are typically defined in the global location and must + exist before they can be referenced in a flag's evaluation criteria. EXAMPLES - To list all Flags Attributes, run: + To list all Flag Attributes across all locations in the current project, + run: $ gcloud beta saas-runtime flags attributes list + To list Flag Attributes for a specific location (e.g., global), run: + + $ gcloud beta saas-runtime flags attributes list --location=global + + To find a specific attribute by its key (e.g., userID), run: + + $ gcloud beta saas-runtime flags attributes list \ + --filter="key:userID" + + To get the full resource URIs for use in a flag's evaluation-spec JSON, + run: + + $ gcloud beta saas-runtime flags attributes list --location=global \ + --uri + + To list attributes and output in JSON format for automation/scripting, run: + + $ gcloud beta saas-runtime flags attributes list --format=json + FLAGS Location resource - Location in which to list Flag Attributes. This represents a Cloud resource. (NOTE) Some attributes are not given diff --git a/gcloud/beta/saas-runtime/flags/attributes/update b/gcloud/beta/saas-runtime/flags/attributes/update index 125bd1405..f58666507 100644 --- a/gcloud/beta/saas-runtime/flags/attributes/update +++ b/gcloud/beta/saas-runtime/flags/attributes/update @@ -12,12 +12,23 @@ SYNOPSIS | --remove-labels=REMOVE_LABELS] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) Update a Flag Attribute. + (BETA) Update the metadata of a Flag Attribute. This command allows you to + modify labels and annotations associated with the resource. + + Flag Attributes are foundational resources that define the evaluation + context such as 'userID', 'tenantID', or 'region' used by targeting rules + and randomization algorithms to determine flag values. + + Note that core fields like the attribute key and value type are immutable + after creation to maintain evaluation consistency across your service. This + command is primarily used for categorization via labels or for attaching + audit metadata via annotations. EXAMPLES - To update Flag Attribute, run: + To update labels and annotations for a flag attribute, run: - $ gcloud beta saas-runtime flags attributes update + $ gcloud beta saas-runtime flags attributes update my-attribute \ + --location=global --labels=env=prod --annotations=ticket=123 POSITIONAL ARGUMENTS FlagAttribute resource - Flag Attribute ID. Flag Attribute ID. Google diff --git a/gcloud/beta/saas-runtime/flags/create b/gcloud/beta/saas-runtime/flags/create index 8daa09aa6..a341898b4 100644 --- a/gcloud/beta/saas-runtime/flags/create +++ b/gcloud/beta/saas-runtime/flags/create @@ -5,20 +5,43 @@ SYNOPSIS gcloud beta saas-runtime flags create FLAG --flag-value-type=FLAG_VALUE_TYPE --key=KEY --unit-kind=UNIT_KIND [--annotations=[ANNOTATIONS,...]] [--description=DESCRIPTION] - [--evaluation-spec=[defaultTarget=DEFAULTTARGET]] [--flag-set=FLAG_SET] - [--labels=[LABELS,...]] [--location=LOCATION] [--state=STATE] + [--evaluation-spec=[allocations=ALLOCATIONS], + [attributes=ATTRIBUTES],[defaultTarget=DEFAULTTARGET],[rules=RULES]] + [--flag-set=FLAG_SET] [--labels=[LABELS,...]] [--location=LOCATION] + [--state=STATE] [--variants=[booleanValue=BOOLEANVALUE],[description=DESCRIPTION], [doubleValue=DOUBLEVALUE], [id=ID],[integerValue=INTEGERVALUE],[stringValue=STRINGVALUE]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) Create a Flag + (BETA) Create a new feature flag resource. Flags define toggleable features + or configurations that can be evaluated at runtime by applications. EXAMPLES - To create a Flag, run: + To create a simple boolean flag with a default Disabled state, run: - $ gcloud beta saas-runtime flags create + $ gcloud beta saas-runtime flags create my-feature-flag \ + --key=enable_new_feature --flag-value-type=bool \ + --unit-kind=my-service-unit \ + --variants='[{"id": "Enabled", "booleanValue": true}, {"id": + "Disabled", "booleanValue": false}]' \ + --evaluation-spec='{"defaultTarget": "Disabled"}' \ + --location=global + + To create a percentage rollout (10% Enabled) using a userID attribute, run: + + $ gcloud beta saas-runtime flags create beta-feature \ + --key=beta_rollout --flag-value-type=bool \ + --unit-kind=my-service-unit \ + --variants='[{"id": "Enabled", "booleanValue": true}, {"id": + "Disabled", "booleanValue": false}]' \ + --evaluation-spec='{"allocations": [{"id": "p10", + "randomizedOn": "userID", "slots": [{"variant": "Disabled", + "weight": 90}, {"variant": "Enabled", "weight": 10}]}], + "defaultTarget": "p10", "attributes": + ["projects/my-project/locations/global/flagAttributes/id-attr"]}' \ + --location=global POSITIONAL ARGUMENTS Flag resource - ID of the Flag: @@ -116,19 +139,62 @@ OPTIONAL FLAGS --description=DESCRIPTION A description of the flag. Max length: 500 bytes. - --evaluation-spec=[defaultTarget=DEFAULTTARGET] + --evaluation-spec=[allocations=ALLOCATIONS],[attributes=ATTRIBUTES],[defaultTarget=DEFAULTTARGET],[rules=RULES] Specification of how the Flag value should be evaluated. + allocations + A list of allocations. + + description + A description of the allocation. Max length: 500 bytes. + + id + Id of the allocation. Max length: 128 bytes. + + randomizedOn + Key of the context attribute that is used for traffic + splitting. + + slots + Slots defines the weighted distribution of variants. + + variant + Variant of the allocation slot. + + weight + Weight defines the proportion of traffic to allocate to the + variant, relative to other slots in the same allocation. + + attributes + Names of the context attributes that are used in the evaluation + rules and allocations. + defaultTarget Default variant for the flag. + rules + Define the logic for evaluating the flag against a given context. + The rules are evaluated sequentially in their specified order. + + condition + A Common Expression Language (CEL cel.dev) expression evaluated + against the evaluation context. For example: plan == "premium" + && country == "DE". + + id + A unique identifier for the rule. + + target + The ID of the variant to return if the condition evaluates to + true. + Shorthand Example: - --evaluation-spec=defaultTarget=string + --evaluation-spec=allocations=[{description=string,id=string,randomizedOn=string,slots=[{variant=string,weight=int}]}],attributes=[string],defaultTarget=string,rules=[{condition=string,id=string,target=string}] JSON Example: - --evaluation-spec='{"defaultTarget": "string"}' + --evaluation-spec='{"allocations": [{"description": "string", "id": "string", "randomizedOn": "string", "slots": [{"variant": "string", "weight": int}]}], "attributes": ["string"], "defaultTarget": "string", "rules": [{"condition": "string", "id": "string", "target": "string"}]}' File Example: diff --git a/gcloud/beta/saas-runtime/flags/delete b/gcloud/beta/saas-runtime/flags/delete index 9082b892e..fb59a5bad 100644 --- a/gcloud/beta/saas-runtime/flags/delete +++ b/gcloud/beta/saas-runtime/flags/delete @@ -6,12 +6,31 @@ SYNOPSIS [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) Delete a Flag + (BETA) Delete a feature flag resource. + + This operation is permanent. To prevent production outages, the flag MUST + be detached from all Units and UnitKinds via a rollout before it is + deleted. + + The safe deletion workflow is: + + 1. Ensure all application code using the flag has been removed and the updated binary is deployed to production. + 2. Confirm that no active Units are still requesting evaluations for that specific flag key. + 3. Detach from Units: create a new FlagRelease that includes Flag to remove and initiate a Rollout. + 4. Once the cleanup rollout is complete, you can safely delete the FlagRelease and FlagRevision. + 5. Run this delete command to permanently remove the Flag. EXAMPLES - To delete a Flag, run: + To delete a flag named my-feature-flag in the global location, run: - $ gcloud beta saas-runtime flags delete + $ gcloud beta saas-runtime flags delete my-feature-flag \ + --location=global + + To delete a flag using a fully qualified resource name (useful for + automation), run: + + $ gcloud beta saas-runtime flags delete \ + projects/my-project/locations/global/flags/my-feature-flag POSITIONAL ARGUMENTS Flag resource - Flag ID of the Flag to delete. The arguments in this group diff --git a/gcloud/beta/saas-runtime/flags/describe b/gcloud/beta/saas-runtime/flags/describe index 9a35dc7b0..646199402 100644 --- a/gcloud/beta/saas-runtime/flags/describe +++ b/gcloud/beta/saas-runtime/flags/describe @@ -6,18 +6,39 @@ SYNOPSIS [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) Describe a Flag + (BETA) Show detailed information about a feature flag resource. + + This command retrieves the complete configuration and status of a flag. It + is the primary tool for auditing flag definitions and troubleshooting + rollout discrepancies. + + For automated processing, use --format=json or --format=yaml to retrieve + the structured representation of the flag's evaluation specification, which + can be used to programmatically verify rollout configurations before + deployment. EXAMPLES - To describe a Flag, run: + To describe a flag named my-feature-flag in the global location, run: - $ gcloud beta saas-runtime flags describe + $ gcloud beta saas-runtime flags describe my-feature-flag \ + --location=global + + To describe a flag using its fully qualified resource name, run: + + $ gcloud beta saas-runtime flags describe \ + projects/my-project/locations/global/flags/my-feature-flag + + To inspect the evaluation specification in JSON format for automated + auditing, run: + + $ gcloud beta saas-runtime flags describe my-feature-flag \ + --location=global --format=json POSITIONAL ARGUMENTS - Flag resource - Flag ID of the Flag 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. + Flag resource - Flag ID of the Flag to describe or the fully qualified + resource name. The arguments in this group can be used to specify the + attributes of this resource. (NOTE) Some attributes are not given + arguments in this group but can be set in other ways. To set the project attribute: ◆ provide the argument flag on the command line with a fully specified diff --git a/gcloud/beta/saas-runtime/flags/list b/gcloud/beta/saas-runtime/flags/list index 833f9820a..823fa4599 100644 --- a/gcloud/beta/saas-runtime/flags/list +++ b/gcloud/beta/saas-runtime/flags/list @@ -7,13 +7,30 @@ SYNOPSIS [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) List Flags + (BETA) List all feature flags available in a specific location for your + SaaS offerings. + + Use this command to audit available flags and their associated UnitKind + assignments. EXAMPLES - To list Flags, run: + To list all flags across all locations in the current project, run: $ gcloud beta saas-runtime flags list + To list flags for a specific location (e.g., us-central1), run: + + $ gcloud beta saas-runtime flags list --location=us-central1 + + To filter flags belonging to a specific UnitKind, run: + + $ gcloud beta saas-runtime flags list \ + --filter="unitKind:my-unit-kind" + + To list flags and output in JSON format for automation/scripting, run: + + $ gcloud beta saas-runtime flags list --format=json + FLAGS Location resource - Location in which to list Flags. This represents a Cloud resource. (NOTE) Some attributes are not given arguments in this diff --git a/gcloud/beta/saas-runtime/flags/releases/create b/gcloud/beta/saas-runtime/flags/releases/create index e42ef670f..71954b491 100644 --- a/gcloud/beta/saas-runtime/flags/releases/create +++ b/gcloud/beta/saas-runtime/flags/releases/create @@ -5,16 +5,27 @@ SYNOPSIS gcloud beta saas-runtime flags releases create FLAG_RELEASE --unit-kind=UNIT_KIND [--annotations=[ANNOTATIONS,...]] [--labels=[LABELS,...]] [--location=LOCATION] + [--obsolete-flags=[OBSOLETE_FLAGS,...]] [--all-flags | --flag-sets=[FLAG_SETS,...] | --revisions=[REVISIONS,...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) Create a Flag Release. + (BETA) Create a new Flag Release resource. A Flag Release defines a + specific set of flag revisions to be applied to a UnitKind. It serves as + the immutable input for a Rollout. EXAMPLES - To create a Flag Release, run: + To create a targeted Flag Release for specific flag revisions, run: - $ gcloud beta saas-runtime flags releases create + $ gcloud beta saas-runtime flags releases create my-release \ + --unit-kind=my-unit-kind --revisions=rev-1,rev-2 \ + --location=global + + To create a Flag Release that includes all current flags in a UnitKind, + run: + + $ gcloud beta saas-runtime flags releases create full-sync \ + --unit-kind=my-unit-kind --all-flags --location=global POSITIONAL ARGUMENTS FlagRelease resource - ID of the Flag Release: @@ -117,9 +128,33 @@ OPTIONAL FLAGS --labels=path_to_file.(yaml|json) --location=LOCATION - For resources [flag_release, revisions, unit-kind], provides fallback - value for resource location attribute. When the resource's full URI - path is not provided, location will fallback to this flag value. + For resources [flag_release, obsolete-flags, revisions, unit-kind], + provides fallback value for resource location attribute. When the + resource's full URI path is not provided, location will fallback to + this flag value. + + Flag resource - Flags (IDs) to be removed from the given UnitKind and all + the related Units. If Flag (ID) is provided here, its Flag Revisions will + be removed from the UnitKind and Units. 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 --obsolete-flags 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 --obsolete-flags on the command line with a + fully specified name; + ◆ provide the argument --location on the command line. + + --obsolete-flags=[OBSOLETE_FLAGS,...] + IDs of the flags or fully qualified identifiers for the flags. + + To set the flag attribute: + ◆ provide the argument --obsolete-flags on the command line. Flags for specifying the content of the release. You can use only one of the following flags. diff --git a/gcloud/beta/saas-runtime/flags/releases/delete b/gcloud/beta/saas-runtime/flags/releases/delete index 747408e27..126691d2a 100644 --- a/gcloud/beta/saas-runtime/flags/releases/delete +++ b/gcloud/beta/saas-runtime/flags/releases/delete @@ -6,12 +6,28 @@ SYNOPSIS (FLAG_RELEASE : --location=LOCATION) [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) Delete a Flag Release + (BETA) Delete a Flag Release resource. + + Flag Releases are resources that groups one or more FlagRevision resources + that are intended to be deployed together as a single payload for a + Rollout. + + The safe deletion workflow is: + + 1. Ensure no active Rollouts reference this Flag Release. + 2. Run this `delete` command to permanently remove the Flag Release. EXAMPLES - To delete a Flag Release, run: + To delete a Flag Release named 'v1-release' in the 'global' location, run: - $ gcloud beta saas-runtime flags releases delete + $ gcloud beta saas-runtime flags releases delete v1-release \ + --location=global + + To delete a Flag Release using a fully qualified resource name (useful for + automation), run: + + $ gcloud beta saas-runtime flags releases delete \ + projects/my-project/locations/global/flagReleases/v1-release POSITIONAL ARGUMENTS FlagRelease resource - Flag Release ID of the Flag Release to delete. The diff --git a/gcloud/beta/saas-runtime/flags/releases/describe b/gcloud/beta/saas-runtime/flags/releases/describe index 39988a630..abebdc8fc 100644 --- a/gcloud/beta/saas-runtime/flags/releases/describe +++ b/gcloud/beta/saas-runtime/flags/releases/describe @@ -1,17 +1,39 @@ NAME - gcloud beta saas-runtime flags releases describe - describe Flag Revision + gcloud beta saas-runtime flags releases describe - describe Flag Release SYNOPSIS gcloud beta saas-runtime flags releases describe (FLAG_RELEASE : --location=LOCATION) [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) Describe a Flag Release + (BETA) Show detailed information about a Flag Release resource. + + A Flag Release is a configuration snapshot that groups one or more Flag + Revisions for a specific UnitKind. This command retrieves the list of + revisions, target UnitKind, and other metadata. It is the primary tool for + auditing the content of a rollout. + + For automated processing, use --format=json or --format=yaml to retrieve + the structured representation of the release, which can be used to + programmatically verify rollout configurations or generate recovery + scripts. EXAMPLES - To describe a Flag Release, run: + To describe a Flag Release named my-release in the global location, run: - $ gcloud beta saas-runtime flags releases describe + $ gcloud beta saas-runtime flags releases describe my-release \ + --location=global + + To describe a Flag Release using its fully qualified resource name, run: + + $ gcloud beta saas-runtime flags releases describe \ + projects/my-project/locations/global/flagReleases/my-release + + To inspect the revisions in JSON format for automated auditing or recovery, + run: + + $ gcloud beta saas-runtime flags releases describe my-release \ + --location=global --format=json POSITIONAL ARGUMENTS FlagRelease resource - Flag Release ID of the Flag Release to describe. diff --git a/gcloud/beta/saas-runtime/flags/releases/help b/gcloud/beta/saas-runtime/flags/releases/help index 271a47b18..037aff179 100644 --- a/gcloud/beta/saas-runtime/flags/releases/help +++ b/gcloud/beta/saas-runtime/flags/releases/help @@ -23,13 +23,13 @@ COMMANDS (BETA) Delete Flag Release. describe - (BETA) Describe Flag Revision. + (BETA) Describe Flag Release. list - (BETA) List Flags Releases. + (BETA) List Flag Releases. update - (BETA) Update Flag Release. + (BETA) Update a Flag Release. NOTES This command is currently in beta and might change without notice. diff --git a/gcloud/beta/saas-runtime/flags/releases/list b/gcloud/beta/saas-runtime/flags/releases/list index 0cb1705f4..29b50edfd 100644 --- a/gcloud/beta/saas-runtime/flags/releases/list +++ b/gcloud/beta/saas-runtime/flags/releases/list @@ -1,5 +1,5 @@ NAME - gcloud beta saas-runtime flags releases list - list Flags Releases + gcloud beta saas-runtime flags releases list - list Flag Releases SYNOPSIS gcloud beta saas-runtime flags releases list [--location=LOCATION] @@ -7,13 +7,32 @@ SYNOPSIS [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) List Flags Releases + (BETA) List all Flag Releases available in a specific location for your + SaaS offerings. + + A Flag Release represents a versioned snapshot of one or more flags + associated with a specific UnitKind. It serves as the baseline for flag + rollouts and is the primary mechanism for synchronizing flag configurations + across a fleet of units. EXAMPLES - To list all Flags Releases, run: + To list all Flag Releases across all locations in the current project, run: $ gcloud beta saas-runtime flags releases list + To list Flag Releases for a specific location (e.g., us-central1), run: + + $ gcloud beta saas-runtime flags releases list --location=us-central1 + + To filter releases belonging to a specific UnitKind, run: + + $ gcloud beta saas-runtime flags releases list \ + --filter="unitKind:my-unit-kind" + + To list releases and output in JSON format for automation/scripting, run: + + $ gcloud beta saas-runtime flags releases list --format=json + FLAGS Location resource - Location in which to list Flag Releases. This represents a Cloud resource. (NOTE) Some attributes are not given diff --git a/gcloud/beta/saas-runtime/flags/releases/update b/gcloud/beta/saas-runtime/flags/releases/update index 24ba4c473..3706733d6 100644 --- a/gcloud/beta/saas-runtime/flags/releases/update +++ b/gcloud/beta/saas-runtime/flags/releases/update @@ -1,5 +1,5 @@ NAME - gcloud beta saas-runtime flags releases update - update Flag Release + gcloud beta saas-runtime flags releases update - update a Flag Release SYNOPSIS gcloud beta saas-runtime flags releases update @@ -12,12 +12,23 @@ SYNOPSIS | --remove-labels=REMOVE_LABELS] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) Update a Flag Release + (BETA) Update the administrative metadata of an existing Flag Release. This + command modifies the resource's labels (for categorization and filtering) + and annotations (for external tool metadata). + + Note that Flag Releases are immutable snapshots of flag configurations. + This command does not modify the flag revisions or the associated UnitKind. + To change the flag logic or revisions associated with a UnitKind, you must + create a new Flag Release and initiate a Rollout. This architecture ensures + that once a release is created, its behavioral payload remains constant + while allowing for operational metadata updates. EXAMPLES - To update a Flag Release, run: + To update labels and annotations for a flag release, run: - $ gcloud beta saas-runtime flags releases update + $ gcloud beta saas-runtime flags releases update my-release \ + --location=us-central1 --labels=env=prod \ + --annotations=ticket=123 POSITIONAL ARGUMENTS FlagRelease resource - ID of the Flag Release: diff --git a/gcloud/beta/saas-runtime/flags/revisions/create b/gcloud/beta/saas-runtime/flags/revisions/create index 2e19b4550..9c4640729 100644 --- a/gcloud/beta/saas-runtime/flags/revisions/create +++ b/gcloud/beta/saas-runtime/flags/revisions/create @@ -7,12 +7,34 @@ SYNOPSIS [--location=LOCATION] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) Create a Flag Revision. + (BETA) Create a new flag revision resource. Flag revisions act as immutable + snapshots of a flag's configuration (variants, rules, and allocations) at a + specific point in time. + + This snapshot is a required prerequisite for creating a Flag Release and + initiating a Flag Rollout. Creating a revision ensures that the + configuration state is frozen and safely decoupled from the live flag + definition during the rollout process. EXAMPLES - To create a Flag Revision, run: + To create a Flag Revision for a flag named my-flag in the global location, + run: - $ gcloud beta saas-runtime flags revisions create + $ gcloud beta saas-runtime flags revisions create my-revision-v1 \ + --flag=my-flag --location=global + + To create a revision using a fully qualified resource name for the revision + ID, run: + + $ gcloud beta saas-runtime flags revisions create \ + projects/my-project/locations/global/flagRevisions/\ + my-revision-v1 --flag=my-flag + + To create a revision with metadata for tracking, run: + + $ gcloud beta saas-runtime flags revisions create prod-ready-rev \ + --flag=search-optimizations --location=us-central1 \ + --labels=env=prod,owner=search-team --annotations=ticket=123 POSITIONAL ARGUMENTS FlagRevision resource - Flag Revision ID. Google Cloud resource name (full diff --git a/gcloud/beta/saas-runtime/flags/revisions/delete b/gcloud/beta/saas-runtime/flags/revisions/delete index dfd198793..e0b95894b 100644 --- a/gcloud/beta/saas-runtime/flags/revisions/delete +++ b/gcloud/beta/saas-runtime/flags/revisions/delete @@ -6,12 +6,39 @@ SYNOPSIS (FLAG_REVISION : --location=LOCATION) [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) Delete a Flag Revision + (BETA) Delete a flag revision resource. + + This operation is permanent. To prevent production outages, ensure the + revision is no longer referenced by any active Flag Releases, Rollouts, + UnitKinds, or Units before it is deleted. + + The safe deletion workflow is: + + 1. Confirm the FlagRevision is not used by any active Units or + UnitKinds (the baseline configuration). + 2. If the revision is active, initiate a Rollout to detach it from + your fleet. This is typically done by rolling out a new FlagRelease + that references a different revision or, if the flag is being + decommissioned, a cleanup FlagRelease. + 3. Run this delete command to permanently remove Flag Revision. EXAMPLES - To delete a Flag Revision, run: + To delete a flag revision named my-revision-v1 in the global location, run: - $ gcloud beta saas-runtime flags revisions delete + $ gcloud beta saas-runtime flags revisions delete my-revision-v1 \ + --location=global + + To delete a flag revision using a fully qualified resource name, run: + + $ gcloud beta saas-runtime flags revisions delete \ + projects/my-project/locations/global/flagRevisions/\ + my-revision-v1 + + To delete a revision as part of a script without interactive confirmation, + run: + + $ gcloud beta saas-runtime flags revisions delete my-revision-v1 \ + --location=global --quiet POSITIONAL ARGUMENTS FlagRevision resource - Flag Revision ID of the Flag Revision to delete. diff --git a/gcloud/beta/saas-runtime/flags/revisions/describe b/gcloud/beta/saas-runtime/flags/revisions/describe index 9d3fab4fe..826e8751a 100644 --- a/gcloud/beta/saas-runtime/flags/revisions/describe +++ b/gcloud/beta/saas-runtime/flags/revisions/describe @@ -6,18 +6,40 @@ SYNOPSIS (FLAG_REVISION : --location=LOCATION) [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) Describe a Flag Revision + (BETA) Show detailed information about a flag revision resource. + + This command retrieves the complete configuration of a specific flag + revision. It is the primary tool for auditing historical flag definitions + and inspecting snapshots before they are included in a Flag Release. + + For automated processing, use --format=json or --format=yaml to retrieve + the structured representation of the revision's evaluation logic, which can + be used to programmatically verify configurations. EXAMPLES - To describe a Flag Revision, run: + To describe a flag revision named my-revision-v1 in the global location, + run: - $ gcloud beta saas-runtime flags revisions describe + $ gcloud beta saas-runtime flags revisions describe my-revision-v1 \ + --location=global + + To describe a flag revision using its fully qualified resource name, run: + + $ gcloud beta saas-runtime flags revisions describe \ + projects/my-project/locations/global/flagRevisions/\ + my-revision-v1 + + To inspect the revision configuration in JSON format for automated + auditing, run: + + $ gcloud beta saas-runtime flags revisions describe my-revision-v1 \ + --location=global --format=json POSITIONAL ARGUMENTS - FlagRevision resource - Flag Revision ID of the Flag Revision to describe. - The arguments in this group can be used to specify the attributes of this - resource. (NOTE) Some attributes are not given arguments in this group but - can be set in other ways. + FlagRevision resource - Flag Revision ID of the Flag Revision to describe + or the fully qualified resource name. The arguments in this group can be + used to specify the attributes of this resource. (NOTE) Some attributes + are not given arguments in this group but can be set in other ways. To set the project attribute: ◆ provide the argument flag_revision on the command line with a fully diff --git a/gcloud/beta/saas-runtime/flags/revisions/help b/gcloud/beta/saas-runtime/flags/revisions/help index b28a105ba..4b13d39bc 100644 --- a/gcloud/beta/saas-runtime/flags/revisions/help +++ b/gcloud/beta/saas-runtime/flags/revisions/help @@ -26,7 +26,7 @@ COMMANDS (BETA) Describe Flag Revision. list - (BETA) List Flags Revisions. + (BETA) List Flag Revisions. update (BETA) Update Flag Revision. diff --git a/gcloud/beta/saas-runtime/flags/revisions/list b/gcloud/beta/saas-runtime/flags/revisions/list index 4c4095a15..acbd3388e 100644 --- a/gcloud/beta/saas-runtime/flags/revisions/list +++ b/gcloud/beta/saas-runtime/flags/revisions/list @@ -1,5 +1,5 @@ NAME - gcloud beta saas-runtime flags revisions list - list Flags Revisions + gcloud beta saas-runtime flags revisions list - list Flag Revisions SYNOPSIS gcloud beta saas-runtime flags revisions list [--location=LOCATION] @@ -7,15 +7,40 @@ SYNOPSIS [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) List Flags Revisions + (BETA) List all flag revisions available in a specific location. Flag + revisions are immutable, point-in-time snapshots of a flag's configuration. + + Use this command to audit configuration history, verify revision creation + success, or identify specific revision IDs for manual recovery or inclusion + in a Flag Release. EXAMPLES - To list Flags Revisions, run: + To list all flag revisions across all locations in the current project, + run: $ gcloud beta saas-runtime flags revisions list + To list all flag revisions in the global location, run: + + $ gcloud beta saas-runtime flags revisions list --location=global + + To list revisions specifically for a flag named my-flag, run: + + $ gcloud beta saas-runtime flags revisions list --location=global \ + --filter="flag:my-flag" + + To list the 5 most recent revisions to identify the latest configuration + state, run: + + $ gcloud beta saas-runtime flags revisions list --location=global \ + --limit=5 --sort-by=~createTime + + To list revisions and output in JSON format for automation/scripting, run: + + $ gcloud beta saas-runtime flags revisions list --format=json + FLAGS - Location resource - Parent value for ListFlagRevisionsRequest This + Location resource - Location in which to list Flag Revisions. This represents a Cloud resource. (NOTE) Some attributes are not given arguments in this group but can be set in other ways. diff --git a/gcloud/beta/saas-runtime/flags/revisions/update b/gcloud/beta/saas-runtime/flags/revisions/update index 6105ab3d5..b93267b62 100644 --- a/gcloud/beta/saas-runtime/flags/revisions/update +++ b/gcloud/beta/saas-runtime/flags/revisions/update @@ -12,12 +12,21 @@ SYNOPSIS | --remove-labels=REMOVE_LABELS] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) Update a Flag Revision. + (BETA) Update the metadata of a flag revision. This command modifies the + revision's labels and annotations without altering the underlying flag + configuration. + + Note that a flag revision serves as an immutable snapshot of a flag's + definition at a specific point in time. While the configuration (variants + and evaluation logic) cannot be modified once created, this command allows + you to add labels and annotations to the revision for categorization and + tracking. EXAMPLES - To update Flag Revision, run: + To update labels and annotations for a flag revision, run: - $ gcloud beta saas-runtime flags revisions update + $ gcloud beta saas-runtime flags revisions update my-revision \ + --location=global --labels=env=prod --annotations=ticket=123 POSITIONAL ARGUMENTS FlagRevision resource - Flag Revision ID. Google Cloud resource name (full diff --git a/gcloud/beta/saas-runtime/flags/update b/gcloud/beta/saas-runtime/flags/update index 778da6448..c23fdb054 100644 --- a/gcloud/beta/saas-runtime/flags/update +++ b/gcloud/beta/saas-runtime/flags/update @@ -3,7 +3,8 @@ NAME SYNOPSIS gcloud beta saas-runtime flags update (FLAG : --location=LOCATION) - [--evaluation-spec=[defaultTarget=DEFAULTTARGET],[variants=VARIANTS]] + [--evaluation-spec=[allocations=ALLOCATIONS], + [attributes=ATTRIBUTES],[defaultTarget=DEFAULTTARGET],[rules=RULES]] [--state=STATE] [--variants=[booleanValue=BOOLEANVALUE],[description=DESCRIPTION], [doubleValue=DOUBLEVALUE], @@ -18,12 +19,66 @@ SYNOPSIS | --remove-labels=REMOVE_LABELS] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) Update a Flag + (BETA) Update the definition of a feature flag. This command modifies the + flag's configuration such as variants, evaluation logic, or metadata within + its parent UnitKind. + + Feature flags follow a lifecycle managed through their state: + + The in-development state is the initial state for a feature flag. It + indicates that the flag is currently being defined, variants are being + added, and evaluation logic is being refined. Flags in this state are + typically used for initial setup and testing and are not yet intended for + production rollouts. + + The active state is the default state for a feature flag. It signifies that + the flag is in use, authorized for production rollouts, and actively being + evaluated by application services. Active flags are included in + configuration manifests and release snapshots for the fleet. + + The sunsetting state indicates that a feature flag is being phased out. It + serves as a signal to engineering teams that the code associated with the + flag should be removed. While still functional, sunsetting flags should not + be used for new feature logic and are candidates for future cleanup. + + When a flag is no longer needed, its state can be updated to cleanup. + Performing a rollout with a flag in this state will remove all its + revisions from the Units. This is a mandatory step in the flag deletion + flow. + + Note that updating a flag definition does not immediately change the flag's + value in production units. To apply these changes to your fleet, you must + subsequently create a new FlagRelease and initiate a Rollout. This + architecture enables the decoupling of feature releases from code + deployments, facilitating safe, progressive rollouts and instant rollbacks. EXAMPLES - To update a Flag, run: + To initialize a flag in the in-development state for testing, run: - $ gcloud beta saas-runtime flags update + $ gcloud beta saas-runtime flags update my-flag --location=global \ + --state=in-development + + To guarantee a flag is active for a new production rollout, run: + + $ gcloud beta saas-runtime flags update my-flag --location=global \ + --state=active + + To update the variants of a boolean flag, run: + + $ gcloud beta saas-runtime flags update my-flag --location=global \ + --variants='[{"id": "Enabled", "booleanValue": true}, {"id": + "Disabled", "booleanValue": false}]' + + To mark a flag as sunsetting to signal code removal, run: + + $ gcloud beta saas-runtime flags update my-flag --location=global \ + --state=sunsetting \ + --description="Feature fully launched. Starting code removal." + + To mark a flag for cleanup (remove from Units in the next rollout), run: + + $ gcloud beta saas-runtime flags update my-flag --location=global \ + --state=cleanup --description="Ready for permanent deletion." POSITIONAL ARGUMENTS Flag resource - ID of the Flag: @@ -61,29 +116,62 @@ POSITIONAL ARGUMENTS ▸ provide the argument --location on the command line. FLAGS - --evaluation-spec=[defaultTarget=DEFAULTTARGET],[variants=VARIANTS] + --evaluation-spec=[allocations=ALLOCATIONS],[attributes=ATTRIBUTES],[defaultTarget=DEFAULTTARGET],[rules=RULES] Specification of how the Flag value should be evaluated. + allocations + A list of allocations. + + description + A description of the allocation. Max length: 500 bytes. + + id + Id of the allocation. Max length: 128 bytes. + + randomizedOn + Key of the context attribute that is used for traffic + splitting. + + slots + Slots defines the weighted distribution of variants. + + variant + Variant of the allocation slot. + + weight + Weight defines the proportion of traffic to allocate to the + variant, relative to other slots in the same allocation. + + attributes + Names of the context attributes that are used in the evaluation + rules and allocations. + defaultTarget Default variant for the flag. - variants - A list of variants. Variant is an identifier for a value (name - assigned to a value). + rules + Define the logic for evaluating the flag against a given context. + The rules are evaluated sequentially in their specified order. - boolValue - Value is a single boolean flag value for the variant. + condition + A Common Expression Language (CEL cel.dev) expression evaluated + against the evaluation context. For example: plan == "premium" + && country == "DE". - name - Name of the variant. Max length: 128 bytes. + id + A unique identifier for the rule. + + target + The ID of the variant to return if the condition evaluates to + true. Shorthand Example: - --evaluation-spec=defaultTarget=string,variants=[{boolValue=boolean,name=string}] + --evaluation-spec=allocations=[{description=string,id=string,randomizedOn=string,slots=[{variant=string,weight=int}]}],attributes=[string],defaultTarget=string,rules=[{condition=string,id=string,target=string}] JSON Example: - --evaluation-spec='{"defaultTarget": "string", "variants": [{"boolValue": boolean, "name": "string"}]}' + --evaluation-spec='{"allocations": [{"description": "string", "id": "string", "randomizedOn": "string", "slots": [{"variant": "string", "weight": int}]}], "attributes": ["string"], "defaultTarget": "string", "rules": [{"condition": "string", "id": "string", "target": "string"}]}' File Example: diff --git a/gcloud/beta/saas-runtime/saas/create b/gcloud/beta/saas-runtime/saas/create index da12ab243..149b38b77 100644 --- a/gcloud/beta/saas-runtime/saas/create +++ b/gcloud/beta/saas-runtime/saas/create @@ -3,7 +3,10 @@ NAME SYNOPSIS gcloud beta saas-runtime saas create (SAAS : --location=LOCATION) - --locations=[name=NAME] [--labels=[LABELS,...]] [GCLOUD_WIDE_FLAG ...] + --locations=[name=NAME] [--labels=[LABELS,...]] + [--application-template=APPLICATION_TEMPLATE + : --application-template-revision=APPLICATION_TEMPLATE_REVISION] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) Create a SaaS @@ -90,6 +93,19 @@ OPTIONAL FLAGS --labels=path_to_file.(yaml|json) + CompositeRef represents a reference to a composite resource. + + --application-template=APPLICATION_TEMPLATE + Reference to the ApplicationTemplate resource. + + This flag argument must be specified if any of the other arguments in + this group are specified. + + --application-template-revision=APPLICATION_TEMPLATE_REVISION + Revision of the ApplicationTemplate to use. Changes to revision will + trigger manual resynchronization. If empty, ApplicationTemplate will be + ignored. + 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/saas-runtime/saas/update b/gcloud/beta/saas-runtime/saas/update index d25cda14c..5d255b76c 100644 --- a/gcloud/beta/saas-runtime/saas/update +++ b/gcloud/beta/saas-runtime/saas/update @@ -3,6 +3,9 @@ NAME SYNOPSIS gcloud beta saas-runtime saas update (SAAS : --location=LOCATION) + [--application-template=APPLICATION_TEMPLATE + --application-template-revision=APPLICATION_TEMPLATE_REVISION + --clear-application-template] [--labels=[LABELS,...] | --update-labels=[UPDATE_LABELS,...] --clear-labels | --remove-labels=REMOVE_LABELS] @@ -50,6 +53,19 @@ POSITIONAL ARGUMENTS ▸ provide the argument --location on the command line. FLAGS + CompositeRef represents a reference to a composite resource. + + --application-template=APPLICATION_TEMPLATE + Reference to the ApplicationTemplate resource. + + --application-template-revision=APPLICATION_TEMPLATE_REVISION + Revision of the ApplicationTemplate to use. Changes to revision will + trigger manual resynchronization. If empty, ApplicationTemplate will be + ignored. + + --clear-application-template + Set saas.applicationTemplate back to default value. + Update labels. At most one of these can be specified: diff --git a/gcloud/beta/saas-runtime/unit-kinds/create b/gcloud/beta/saas-runtime/unit-kinds/create index 99cab027e..c2ad83de9 100644 --- a/gcloud/beta/saas-runtime/unit-kinds/create +++ b/gcloud/beta/saas-runtime/unit-kinds/create @@ -8,6 +8,7 @@ SYNOPSIS [--input-variable-mappings=[from=FROM],[to=TO],[variable=VARIABLE]] [--labels=[LABELS,...]] [--location=LOCATION] [--output-variable-mappings=[from=FROM],[to=TO],[variable=VARIABLE]] + [--app-params-group=APP_PARAMS_GROUP --scope-type=SCOPE_TYPE] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -232,6 +233,24 @@ OPTIONAL FLAGS --output-variable-mappings=path_to_file.(yaml|json) + AppParams contains the parameters for creating an AppHub Application. + + --app-params-group=APP_PARAMS_GROUP + Grouping used to construct the name of the AppHub Application. Multiple + UnitKinds can specify the same group to use the same Application across + their respective units. Corresponds to the app_boundary_id in the ADC + composite ApplicationTemplate. Defaults to UnitKind.name + + Scope of an application. + + --scope-type=SCOPE_TYPE + Scope Type. SCOPE_TYPE must be one of: + + type-global + Global type. + type-regional + Regional type. + 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/saas-runtime/unit-kinds/update b/gcloud/beta/saas-runtime/unit-kinds/update index 4464f3410..16969d7ea 100644 --- a/gcloud/beta/saas-runtime/unit-kinds/update +++ b/gcloud/beta/saas-runtime/unit-kinds/update @@ -4,6 +4,8 @@ NAME SYNOPSIS gcloud beta saas-runtime unit-kinds update UNIT_KIND [--location=LOCATION] [--saas=SAAS] + [--app-params-group=APP_PARAMS_GROUP + --clear-app-params --scope-type=SCOPE_TYPE] [--clear-default-release | --default-release=DEFAULT_RELEASE] [--dependencies=[alias=ALIAS],[unitKind=UNITKIND] | --add-dependencies=[alias=ALIAS],[unitKind=UNITKIND] @@ -85,6 +87,27 @@ FLAGS To set the saas attribute: ◆ provide the argument --saas on the command line. + AppParams contains the parameters for creating an AppHub Application. + + --app-params-group=APP_PARAMS_GROUP + Grouping used to construct the name of the AppHub Application. Multiple + UnitKinds can specify the same group to use the same Application across + their respective units. Corresponds to the app_boundary_id in the ADC + composite ApplicationTemplate. Defaults to UnitKind.name + + --clear-app-params + Set unitKind.appParams back to default value. + + Scope of an application. + + --scope-type=SCOPE_TYPE + Scope Type. SCOPE_TYPE must be one of: + + type-global + Global type. + type-regional + Regional type. + Update default_release. At most one of these can be specified: diff --git a/gcloud/beta/saas-runtime/units/create b/gcloud/beta/saas-runtime/units/create index 8402d79c6..766795ddf 100644 --- a/gcloud/beta/saas-runtime/units/create +++ b/gcloud/beta/saas-runtime/units/create @@ -2,7 +2,7 @@ NAME gcloud beta saas-runtime units create - create a Unit SYNOPSIS - gcloud beta saas-runtime units create UNIT + gcloud beta saas-runtime units create UNIT [--application=APPLICATION] [--flag-revisions=[FLAG_REVISIONS,...]] [--labels=[LABELS,...]] [--location=LOCATION] [--maintenance-pinned-until-time=MAINTENANCE_PINNED_UNTIL_TIME] @@ -43,6 +43,11 @@ POSITIONAL ARGUMENTS ▸ provide the argument unit on the command line. FLAGS + --application=APPLICATION + Reference to the AppHub Application this unit belongs to. All resources + deployed in this Unit will be associated with the specified + Application. + FlagRevision resource - List of flag revisions used by this unit This represents a Cloud resource. (NOTE) Some attributes are not given arguments in this group but can be set in other ways. diff --git a/gcloud/beta/saas-runtime/units/update b/gcloud/beta/saas-runtime/units/update index d595858ff..2d83f6fdf 100644 --- a/gcloud/beta/saas-runtime/units/update +++ b/gcloud/beta/saas-runtime/units/update @@ -4,6 +4,7 @@ NAME SYNOPSIS gcloud beta saas-runtime units update UNIT [--location=LOCATION] [--maintenance-pinned-until-time=MAINTENANCE_PINNED_UNTIL_TIME] + [--application=APPLICATION | --clear-application] [--clear-tenant | --tenant=TENANT] [--clear-unit-kind | --unit-kind=UNIT_KIND] [--flag-revisions=[FLAG_REVISIONS,...] @@ -64,6 +65,16 @@ FLAGS changes to the release field will be rejected. Rollouts should and will also respect this by not requesting an upgrade in the first place. + Update application. + + At most one of these can be specified: + + --application=APPLICATION + Set application to new value. + + --clear-application + Clear application value and set to null. + Update tenant. At most one of these can be specified: diff --git a/gcloud/beta/scc/sources/help b/gcloud/beta/scc/sources/help index 666d64ca1..d789b51de 100644 --- a/gcloud/beta/scc/sources/help +++ b/gcloud/beta/scc/sources/help @@ -19,6 +19,9 @@ COMMANDS describe (BETA) Describe a source given its display name or source id. + list + (BETA) List Cloud Security Command Center sources. + NOTES This command is currently in beta and might change without notice. These variants are also available: diff --git a/gcloud/beta/scc/sources/list b/gcloud/beta/scc/sources/list new file mode 100644 index 000000000..965fab141 --- /dev/null +++ b/gcloud/beta/scc/sources/list @@ -0,0 +1,83 @@ +NAME + gcloud beta scc sources list - list Cloud Security Command Center sources + +SYNOPSIS + gcloud beta scc sources list [PARENT] [--filter=EXPRESSION] [--limit=LIMIT] + [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) List Cloud Security Command Center sources. + +EXAMPLES + List all sources under organization 123456: + + $ gcloud beta scc sources list organizations/123456 + + List all sources under folder 456: + + $ gcloud beta scc sources list folders/456 + + List all sources under project example-project: + + $ gcloud beta scc sources list projects/example-project + +POSITIONAL ARGUMENTS + Parent resource - parent organization, folder, or project in the Google + Cloud resource hierarchy to be used for the gcloud scc command. Specify + the argument as either [RESOURCE_TYPE/RESOURCE_ID] or [RESOURCE_ID], as + shown in the preceding examples. This represents a Cloud resource. + + [PARENT] + ID of the parent or fully qualified identifier for the parent. + + To set the parent attribute: + ◆ provide the argument parent on the command line; + ◆ Set the parent property in configuration using gcloud config set + scc/parent if it is not specified in command line. + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the securitycenter/v2 API. The full documentation for + this API can be found at: https://cloud.google.com/security-command-center + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud scc sources list + + $ gcloud alpha scc sources list + diff --git a/gcloud/beta/service-health/artifacts/describe b/gcloud/beta/service-health/artifacts/describe new file mode 100644 index 000000000..d498e54cd --- /dev/null +++ b/gcloud/beta/service-health/artifacts/describe @@ -0,0 +1,80 @@ +NAME + gcloud beta service-health artifacts describe - get details of an artifact + for a project + +SYNOPSIS + gcloud beta service-health artifacts describe + (ARTIFACT : --location=LOCATION) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Retrieves a resource containing information about an artifact, such + as an incident report. + + To get artifacts for incident events, use location global. + +EXAMPLES + To get the details of artifact my-artifact in project my-project and + location global, run: + + $ gcloud beta service-health artifacts describe my-artifact \ + --project=my-project --location=global + +POSITIONAL ARGUMENTS + Artifact resource - Name of the resource using the form + projects/{project_id}/locations/{location}/artifacts/{artifact_id}. + + project_id - Project ID of the project that contains the artifact. + + location - The location of the event that the artifact is associated with. + Set this field to global. + + artifact_id - Artifact ID to retrieve. 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 artifact 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. + + ARTIFACT + ID of the artifact or fully qualified identifier for the artifact. + + To set the artifact attribute: + ▸ provide the argument artifact 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 to use when working with Service Health resources. + + If not specified, will use default servicehealth/location. + + To set the location attribute: + ▸ provide the argument artifact on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ set the property servicehealth/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 servicehealth/v1beta API. The full documentation for + this API can be found at: https://cloud.google.com/service-health/ + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha service-health artifacts describe + diff --git a/gcloud/beta/service-health/artifacts/help b/gcloud/beta/service-health/artifacts/help new file mode 100644 index 000000000..9a0c7844d --- /dev/null +++ b/gcloud/beta/service-health/artifacts/help @@ -0,0 +1,30 @@ +NAME + gcloud beta service-health artifacts - represents a report for a Google + Cloud outage + +SYNOPSIS + gcloud beta service-health artifacts COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Represents a report for a Google Cloud outage. + +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) Get details of an artifact for a project. + + list + (BETA) List artifacts for a project. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha service-health artifacts + diff --git a/gcloud/beta/service-health/artifacts/list b/gcloud/beta/service-health/artifacts/list new file mode 100644 index 000000000..32249008b --- /dev/null +++ b/gcloud/beta/service-health/artifacts/list @@ -0,0 +1,93 @@ +NAME + gcloud beta service-health artifacts list - list artifacts for a project + +SYNOPSIS + gcloud beta service-health artifacts list [--location=LOCATION] + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) List artifacts under a given project and location. + + To retrieve artifacts for incident events, use location global. + +EXAMPLES + To list all artifacts in project my-project and location global, run: + + $ gcloud beta service-health artifacts list --project=my-project \ + --location=global + +FLAGS + Location resource - Parent value for ListArtifactsRequest + projects/{project_id}/locations/{location_id}. + + project_id - Project ID of the project that contains the artifact. + + location - The location to get the service health artifacts from. Set this + field to global. 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 servicehealth/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 servicehealth/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 servicehealth/v1beta API. The full documentation for + this API can be found at: https://cloud.google.com/service-health/ + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha service-health artifacts list + diff --git a/gcloud/beta/service-health/events/describe b/gcloud/beta/service-health/events/describe new file mode 100644 index 000000000..7888880b1 --- /dev/null +++ b/gcloud/beta/service-health/events/describe @@ -0,0 +1,82 @@ +NAME + gcloud beta service-health events describe - get details of an event + affecting a project + +SYNOPSIS + gcloud beta service-health events describe (EVENT : --location=LOCATION) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Retrieves a resource containing information about an event. + + To get service health incident event, use location global. + +EXAMPLES + To get the details of event my-event in project my-project and location + global, run: + + $ gcloud beta service-health events describe my-event \ + --project=my-project --location=global + +POSITIONAL ARGUMENTS + Event resource - Unique name of the event in this scope including project + and location using the form + projects/{project_id}/locations/{location}/events/{event_id}. + + project_id - Project ID of the project that contains the event. + + location - The location to get the service health events from. Set this + field to global. + + event_id - Event ID to retrieve. 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 event 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. + + EVENT + ID of the event or fully qualified identifier for the event. + + To set the event attribute: + ▸ provide the argument event 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 to use when working with Service Health resources. + + If not specified, will use default servicehealth/location. + + To set the location attribute: + ▸ provide the argument event on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ set the property servicehealth/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 servicehealth/v1beta API. The full documentation for + this API can be found at: https://cloud.google.com/service-health/ + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud service-health events describe + + $ gcloud alpha service-health events describe + diff --git a/gcloud/beta/service-health/events/help b/gcloud/beta/service-health/events/help new file mode 100644 index 000000000..142f1b90b --- /dev/null +++ b/gcloud/beta/service-health/events/help @@ -0,0 +1,32 @@ +NAME + gcloud beta service-health events - represents events that may affect + Google Cloud products + +SYNOPSIS + gcloud beta service-health events COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Represents events that may affect Google Cloud products. + +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) Get details of an event affecting a project. + + list + (BETA) List events under a given project and location. + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud service-health events + + $ gcloud alpha service-health events + diff --git a/gcloud/beta/service-health/events/list b/gcloud/beta/service-health/events/list new file mode 100644 index 000000000..c582eb97d --- /dev/null +++ b/gcloud/beta/service-health/events/list @@ -0,0 +1,104 @@ +NAME + gcloud beta service-health events list - list events under a given project + and location + +SYNOPSIS + gcloud beta service-health events list [--location=LOCATION] [--view=VIEW] + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) List events under a given project and location. + + To retrieve service health incident events, use location global. + +EXAMPLES + To list all events in project my-project and location global, run: + + $ gcloud beta service-health events list --project=my-project \ + --location=global + +FLAGS + Location resource - Parent value using the form + projects/{project_id}/locations/{location}/events. + + project_id - ID of the project for which to list service health events. + location - The location to get service health events from. Set this field + to global. 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 servicehealth/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 servicehealth/location. + + --view=VIEW + Event fields to include in response. VIEW must be one of: + + event-view-basic + Includes all fields except updates. This view is the default for + ListEvents API. + event-view-full + Includes all event fields. + +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 servicehealth/v1beta API. The full documentation for + this API can be found at: https://cloud.google.com/service-health/ + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud service-health events list + + $ gcloud alpha service-health events list + diff --git a/gcloud/beta/service-health/help b/gcloud/beta/service-health/help new file mode 100644 index 000000000..d73dbfde7 --- /dev/null +++ b/gcloud/beta/service-health/help @@ -0,0 +1,39 @@ +NAME + gcloud beta service-health - request events that are relevant to your + project or organization + +SYNOPSIS + gcloud beta service-health GROUP [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Request events that are relevant to your project or organization. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +GROUPS + GROUP is one of the following: + + artifacts + (BETA) Represents a report for a Google Cloud outage. + + events + (BETA) Represents events that may affect Google Cloud products. + + organization-events + (BETA) Represents events that may affect products used across the + organization. + + organization-impacts + (BETA) Represents impact to assets at organizational level. + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud service-health + + $ gcloud alpha service-health + diff --git a/gcloud/beta/service-health/organization-events/describe b/gcloud/beta/service-health/organization-events/describe new file mode 100644 index 000000000..247e07bab --- /dev/null +++ b/gcloud/beta/service-health/organization-events/describe @@ -0,0 +1,85 @@ +NAME + gcloud beta service-health organization-events describe - get details of an + event affecting an organization + +SYNOPSIS + gcloud beta service-health organization-events describe + (ORGANIZATION_EVENT : --location=LOCATION --organization=ORGANIZATION) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Retrieves a resource containing information about an event affecting + an organization. + + To get service health incident event, use location global. + +EXAMPLES + To get the details of organization event my-event in location global for + organization 123456789, run: + + $ gcloud beta service-health organization-events describe my-event \ + --organization=123456789 --location=global + +POSITIONAL ARGUMENTS + OrganizationEvent resource - Unique name of the event in this scope + including organization and event ID using the form + organizations/{organization_id}/locations/locations/global/organizationEvents/{event_id}. + + organization_id - ID (number) of the organization that contains the event. + To get your organization_id, see Getting your organization resource ID + (https://cloud.google.com/resource-manager/docs/creating-managing-organization#retrieving_your_organization_id). + + event_id - Organization event ID to retrieve. The arguments in this group + can be used to specify the attributes of this resource. + + This must be specified. + + ORGANIZATION_EVENT + ID of the organizationEvent or fully qualified identifier for the + organizationEvent. + + To set the organization_event attribute: + ▸ provide the argument organization_event 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 to use when working with Service Health resources. + + If not specified, will use default servicehealth/location. + + To set the location attribute: + ▸ provide the argument organization_event on the command line with + a fully specified name; + ▸ provide the argument --location on the command line; + ▸ set the property servicehealth/location. + + --organization=ORGANIZATION + The organization id of the organizationEvent resource. + + To set the organization attribute: + ▸ provide the argument organization_event on the command line with + a fully specified name; + ▸ provide the argument --organization 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 servicehealth/v1beta API. The full documentation for + this API can be found at: https://cloud.google.com/service-health/ + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud service-health organization-events describe + + $ gcloud alpha service-health organization-events describe + diff --git a/gcloud/beta/service-health/organization-events/help b/gcloud/beta/service-health/organization-events/help new file mode 100644 index 000000000..c0d15e7af --- /dev/null +++ b/gcloud/beta/service-health/organization-events/help @@ -0,0 +1,34 @@ +NAME + gcloud beta service-health organization-events - represents events that may + affect products used across the organization + +SYNOPSIS + gcloud beta service-health organization-events COMMAND + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Represents events that may affect products used across the + organization. + +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) Get details of an event affecting an organization. + + list + (BETA) List events under a given organization and location. + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud service-health organization-events + + $ gcloud alpha service-health organization-events + diff --git a/gcloud/beta/service-health/organization-events/list b/gcloud/beta/service-health/organization-events/list new file mode 100644 index 000000000..13dfb6dbc --- /dev/null +++ b/gcloud/beta/service-health/organization-events/list @@ -0,0 +1,112 @@ +NAME + gcloud beta service-health organization-events list - list events under a + given organization and location + +SYNOPSIS + gcloud beta service-health organization-events list [--view=VIEW] + [--location=LOCATION --organization=ORGANIZATION] [--filter=EXPRESSION] + [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Lists organization events under a given organization and location. + + To retrieve service health incident events, use location global. + +EXAMPLES + To list all organization events in location global for organization + 123456789, run: + + $ gcloud beta service-health organization-events list \ + --organization=123456789 --location=global + +FLAGS + --view=VIEW + OrganizationEvent fields to include in response. VIEW must be one of: + + organization-event-view-basic + Includes all organization event fields except updates. This view is + the default for ListOrganizationEvents API. + organization-event-view-full + Includes all organization event fields. + + Location resource - Parent value using the form + organizations/{organization_id}/locations/{location}/organizationEvents. + + organization_id - ID (number) of the organization that contains the event. + To get your organization_id, see Getting your organization resource ID + (https://cloud.google.com/resource-manager/docs/creating-managing-organization#retrieving_your_organization_id). + + location - The location to get organization events from. Set this field to + global. The arguments in this group can be used to specify the attributes + of this resource. + + --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 servicehealth/location. + + --organization=ORGANIZATION + The organization id of the location resource. + + To set the organization attribute: + ◆ provide the argument --location on the command line with a fully + specified name; + ◆ set the property servicehealth/location with a fully specified + name; + ◆ provide the argument --organization 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 servicehealth/v1beta API. The full documentation for + this API can be found at: https://cloud.google.com/service-health/ + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud service-health organization-events list + + $ gcloud alpha service-health organization-events list + diff --git a/gcloud/beta/service-health/organization-impacts/describe b/gcloud/beta/service-health/organization-impacts/describe new file mode 100644 index 000000000..5dfdbd557 --- /dev/null +++ b/gcloud/beta/service-health/organization-impacts/describe @@ -0,0 +1,85 @@ +NAME + gcloud beta service-health organization-impacts describe - get details of + an asset impact by an event under an organization + +SYNOPSIS + gcloud beta service-health organization-impacts describe + (ORGANIZATION_IMPACT : --location=LOCATION --organization=ORGANIZATION) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Retrieves a resource containing information about impact to an asset + under an organization affected by a service health event. + + To retrieve impact for service health incident events, use location global. + +EXAMPLES + To get the details of organization impact my-impact in location global for + organization 123456789, run: + + $ gcloud beta service-health organization-impacts describe \ + my-impact --organization=123456789 --location=global + +POSITIONAL ARGUMENTS + OrganizationImpact resource - Name of the resource using the form + organizations/{organization_id}/locations/global/organizationImpacts/{organization_impact_id}. + + organization_id - ID (number) of the organization that contains the event. + To get your organization_id, see Getting your organization resource ID + (https://cloud.google.com/resource-manager/docs/creating-managing-organization#retrieving_your_organization_id). + + organization_impact_id - ID of the OrganizationImpact resource. The + arguments in this group can be used to specify the attributes of this + resource. + + This must be specified. + + ORGANIZATION_IMPACT + ID of the organizationImpact or fully qualified identifier for the + organizationImpact. + + To set the organization_impact attribute: + ▸ provide the argument organization_impact 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 to use when working with Service Health resources. + + If not specified, will use default servicehealth/location. + + To set the location attribute: + ▸ provide the argument organization_impact on the command line with + a fully specified name; + ▸ provide the argument --location on the command line; + ▸ set the property servicehealth/location. + + --organization=ORGANIZATION + The organization id of the organizationImpact resource. + + To set the organization attribute: + ▸ provide the argument organization_impact on the command line with + a fully specified name; + ▸ provide the argument --organization 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 servicehealth/v1beta API. The full documentation for + this API can be found at: https://cloud.google.com/service-health/ + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud service-health organization-impacts describe + + $ gcloud alpha service-health organization-impacts describe + diff --git a/gcloud/beta/service-health/organization-impacts/help b/gcloud/beta/service-health/organization-impacts/help new file mode 100644 index 000000000..8ab9c8e01 --- /dev/null +++ b/gcloud/beta/service-health/organization-impacts/help @@ -0,0 +1,34 @@ +NAME + gcloud beta service-health organization-impacts - represents impact to + assets at organizational level + +SYNOPSIS + gcloud beta service-health organization-impacts COMMAND + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Represents impact to assets at organizational level. + +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) Get details of an asset impact by an event under an + organization. + + list + (BETA) List assets impacted by events under an organization. + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud service-health organization-impacts + + $ gcloud alpha service-health organization-impacts + diff --git a/gcloud/beta/service-health/organization-impacts/list b/gcloud/beta/service-health/organization-impacts/list new file mode 100644 index 000000000..ba4c3cecd --- /dev/null +++ b/gcloud/beta/service-health/organization-impacts/list @@ -0,0 +1,105 @@ +NAME + gcloud beta service-health organization-impacts list - list assets impacted + by events under an organization + +SYNOPSIS + gcloud beta service-health organization-impacts list + [--location=LOCATION --organization=ORGANIZATION] [--filter=EXPRESSION] + [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Lists assets impacted by organization events under a given + organization and location. + + To retrieve projects impacted by service health incident events, use + location global. + +EXAMPLES + To list all organization impacts in location global for organization + 123456789, run: + + $ gcloud beta service-health organization-impacts list \ + --organization=123456789 --location=global + +FLAGS + Location resource - Parent value using the form + organizations/{organization_id}/locations/{location}/organizationImpacts. + + organization_id - ID (number) of the project that contains the event. To + get your organization_id, see Getting your organization resource ID + (https://cloud.google.com/resource-manager/docs/creating-managing-organization#retrieving_your_organization_id). + + location - The location to get organization impacts from. Set this field + to global. The arguments in this group can be used to specify the + attributes of this resource. + + --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 servicehealth/location. + + --organization=ORGANIZATION + The organization id of the location resource. + + To set the organization attribute: + ◆ provide the argument --location on the command line with a fully + specified name; + ◆ set the property servicehealth/location with a fully specified + name; + ◆ provide the argument --organization 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 servicehealth/v1beta API. The full documentation for + this API can be found at: https://cloud.google.com/service-health/ + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud service-health organization-impacts list + + $ gcloud alpha service-health organization-impacts list + diff --git a/gcloud/beta/services/api-keys/update b/gcloud/beta/services/api-keys/update index bf7e6c458..d99c7de19 100644 --- a/gcloud/beta/services/api-keys/update +++ b/gcloud/beta/services/api-keys/update @@ -19,49 +19,54 @@ EXAMPLES To remove all restrictions of the key: $ gcloud beta services api-keys update \ - projects/myproject/keys/my-key-id --clear-restrictions + projects/myproject/locations/global/keys/my-key-id \ + --clear-restrictions To update display name and set allowed ips as server key restrictions: $ gcloud beta services api-keys update \ - projects/myproject/keys/my-key-id --display-name="test name" \ + projects/myproject/locations/global/keys/my-key-id \ + --display-name="test name" \ --allowed-ips=2620:15c:2c4:203:2776:1f90:6b3b:217,104.133.8.78 To update annotations: $ gcloud beta services api-keys update \ - projects/myproject/keys/my-key-id --annotations=foo=bar,abc=def + projects/myproject/locations/global/keys/my-key-id \ + --annotations=foo=bar,abc=def To update key's allowed referrers restriction: $ gcloud beta services api-keys update \ - projects/myproject/keys/my-key-id \ + projects/myproject/locations/global/keys/my-key-id \ --allowed-referrers="https://www.example.com/*,http://sub.exampl\ e.com/*" To update key's allowed ios app bundle ids: $ gcloud beta services api-keys update \ - projects/myproject/keys/my-key-id --allowed-bundle-ids=my.app + projects/myproject/locations/global/keys/my-key-id \ + --allowed-bundle-ids=my.app To update key's allowed android application: $ gcloud beta services api-keys update \ - projects/myproject/keys/my-key-id \ + projects/myproject/locations/global/keys/my-key-id \ --allowed-application=sha1_fingerprint=foo1,package_name=bar1 \ --allowed-application=sha1_fingerprint=foo2,package_name=bar2 To update keys' allowed api target with multiple services: $ gcloud beta services api-keys update \ - projects/myproject/keys/my-key-id \ + projects/myproject/locations/global/keys/my-key-id \ --api-target=service=bar.service.com \ --api-target=service=foo.service.com To update keys' allowed api target with service and method: $ gcloud beta services api-keys update \ - projects/myproject/keys/my-key-id --flags-file=my-flags.yaml + projects/myproject/locations/global/keys/my-key-id \ + --flags-file=my-flags.yaml The content of 'my-flags.yaml' is as following: diff --git a/gcloud/beta/spanner/databases/update b/gcloud/beta/spanner/databases/update index c37b4aa97..65e62946d 100644 --- a/gcloud/beta/spanner/databases/update +++ b/gcloud/beta/spanner/databases/update @@ -4,8 +4,8 @@ NAME SYNOPSIS gcloud beta spanner databases update (DATABASE : --instance=INSTANCE) [--async] - [--[no-]enable-drop-protection | --kms-keys=KMS_KEY,[KMS_KEY,...]] - [GCLOUD_WIDE_FLAG ...] + [--clear-kms-keys | --[no-]enable-drop-protection + | --kms-keys=KMS_KEY,[KMS_KEY,...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) Update a Cloud Spanner database. @@ -29,6 +29,11 @@ EXAMPLES $ gcloud beta spanner databases update my-database \ --kms-keys="KEY1,KEY2" + To remove all KMS key references and revert a Cloud Spanner database + 'my-database' to Google-managed encryption, run: + + $ gcloud beta spanner databases update my-database --clear-kms-keys + POSITIONAL ARGUMENTS Database resource - The Cloud Spanner database to update. The arguments in this group can be used to specify the attributes of this resource. (NOTE) @@ -68,6 +73,10 @@ FLAGS At most one of these can be specified: + --clear-kms-keys + Removes all KMS key references and reverts the database to + Google-managed encryption. + --[no-]enable-drop-protection Enable database deletion protection on this database. Use --enable-drop-protection to enable and --no-enable-drop-protection to diff --git a/gcloud/beta/sql/instances/create b/gcloud/beta/sql/instances/create index 3bf8c40cf..f17f00c41 100644 --- a/gcloud/beta/sql/instances/create +++ b/gcloud/beta/sql/instances/create @@ -33,6 +33,7 @@ SYNOPSIS [--[no-]enable-data-cache] [--[no-]enable-dataplex-integration] [--[no-]enable-google-ml-integration] [--enable-google-private-path] [--enable-password-policy] [--enable-point-in-time-recovery] + [--[no-]enable-psc-auto-dns] [--[no-]enable-psc-write-endpoint-dns] [--enforce-new-sql-network-architecture] [--failover-replica-name=FAILOVER_REPLICA_NAME] [--[no-]final-backup] [--final-backup-retention-days=FINAL_BACKUP_RETENTION_DAYS] @@ -365,6 +366,16 @@ FLAGS backups enabled to use. Make sure storage can support at least 7 days of logs. + --[no-]enable-psc-auto-dns + Enable per instance DNS records for PSC auto-connections. Use + --enable-psc-auto-dns to enable and --no-enable-psc-auto-dns to + disable. + + --[no-]enable-psc-write-endpoint-dns + Enable the global DNS record pointing to the primary, for Enterprise + Plus edition only. Use --enable-psc-write-endpoint-dns to enable and + --no-enable-psc-write-endpoint-dns to disable. + --enforce-new-sql-network-architecture Force the instance to use the new network architecture. @@ -521,9 +532,19 @@ FLAGS MySQL instance. The input should be in a format of key=value. Available case-sensitive keys are: enabled (boolean), probing-interval-seconds (integer), probe-threshold (integer), running-threads-threshold - (integer), seconds-behind-source-threshold (integer), and - transaction-duration-threshold (integer). Example: - --performance-capture-config enabled=true,probe-threshold=5 + (integer), seconds-behind-source-threshold (integer), + transaction-duration-threshold (integer), + cpu-utilization-threshold-percent (integer), + memory-usage-threshold-percent (integer), + transaction-lock-wait-threshold-count (integer), + semaphore-wait-threshold-count (integer), + history-list-length-threshold-count (integer), + transaction-kill-threshold-seconds (integer), transaction-kill-type + (string), transaction-kill-excluded-user-hosts (string, + semicolon-separated list) Example: --performance-capture-config + enabled=true,probe-threshold=5, cpu-utilization-threshold-percent=80, + transaction-kill-excluded-user-hosts=user1@host1;user2@%, + transaction-kill-type=READ_ONLY_TRANSACTIONS --psc-auto-connections=[network=NETWORK],[project=PROJECT] A comma-separated list of networks or network-project pairs. Each diff --git a/gcloud/beta/sql/instances/help b/gcloud/beta/sql/instances/help index 649c8a86e..29d89b315 100644 --- a/gcloud/beta/sql/instances/help +++ b/gcloud/beta/sql/instances/help @@ -63,6 +63,10 @@ COMMANDS (BETA) Performs a point in time restore for a Cloud SQL instance managed by Google Cloud Backup and Disaster Recovery (DR) Service. + pre-check-major-version-upgrade + (BETA) Performs pre-checks for a major version upgrade of a Cloud SQL + instance. + promote-replica (BETA) Promotes Cloud SQL read replica to a stand-alone instance. diff --git a/gcloud/beta/sql/instances/patch b/gcloud/beta/sql/instances/patch index 3e019aed9..97fe65df7 100644 --- a/gcloud/beta/sql/instances/patch +++ b/gcloud/beta/sql/instances/patch @@ -30,7 +30,8 @@ SYNOPSIS [--[no-]enable-google-ml-integration] [--[no-]enable-google-private-path] [--enable-password-policy] [--[no-]enable-point-in-time-recovery] - [--[no-]enable-private-service-connect] + [--[no-]enable-private-service-connect] [--[no-]enable-psc-auto-dns] + [--[no-]enable-psc-write-endpoint-dns] [--enforce-new-sql-network-architecture] [--failover-dr-replica-name=FAILOVER_DR_REPLICA_NAME] [--[no-]final-backup] @@ -322,6 +323,16 @@ FLAGS Connect. Use --enable-private-service-connect to enable and --no-enable-private-service-connect to disable. + --[no-]enable-psc-auto-dns + Enable per instance DNS records for PSC auto-connections. Use + --enable-psc-auto-dns to enable and --no-enable-psc-auto-dns to + disable. + + --[no-]enable-psc-write-endpoint-dns + Enable the global DNS record pointing to the primary, for Enterprise + Plus edition only. Use --enable-psc-write-endpoint-dns to enable and + --no-enable-psc-write-endpoint-dns to disable. + --enforce-new-sql-network-architecture Force the instance to use the new network architecture. @@ -487,9 +498,19 @@ FLAGS MySQL instance. The input should be in a format of key=value. Available case-sensitive keys are: enabled (boolean), probing-interval-seconds (integer), probe-threshold (integer), running-threads-threshold - (integer), seconds-behind-source-threshold (integer), and - transaction-duration-threshold (integer). Example: - --performance-capture-config enabled=true,probe-threshold=5 + (integer), seconds-behind-source-threshold (integer), + transaction-duration-threshold (integer), + cpu-utilization-threshold-percent (integer), + memory-usage-threshold-percent (integer), + transaction-lock-wait-threshold-count (integer), + semaphore-wait-threshold-count (integer), + history-list-length-threshold-count (integer), + transaction-kill-threshold-seconds (integer), transaction-kill-type + (string), transaction-kill-excluded-user-hosts (string, + semicolon-separated list) Example: --performance-capture-config + enabled=true,probe-threshold=5, cpu-utilization-threshold-percent=80, + transaction-kill-excluded-user-hosts=user1@host1;user2@%, + transaction-kill-type=READ_ONLY_TRANSACTIONS --pricing-plan=PRICING_PLAN, -p PRICING_PLAN First Generation instances only. The pricing plan for this instance. diff --git a/gcloud/beta/sql/instances/pre-check-major-version-upgrade b/gcloud/beta/sql/instances/pre-check-major-version-upgrade new file mode 100644 index 000000000..46c13b3e3 --- /dev/null +++ b/gcloud/beta/sql/instances/pre-check-major-version-upgrade @@ -0,0 +1,53 @@ +NAME + gcloud beta sql instances pre-check-major-version-upgrade - performs + pre-checks for a major version upgrade of a Cloud SQL instance + +SYNOPSIS + gcloud beta sql instances pre-check-major-version-upgrade INSTANCE + --target-database-version=TARGET_DATABASE_VERSION [--async] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) gcloud beta sql instances pre-check-major-version-upgrade performs + pre-checks for a major version upgrade of a Cloud SQL instance. + +EXAMPLES + To perform pre-checks before upgrading a PostgreSQL instance to a target + version (supported in both GA and Beta): + + $ gcloud beta sql instances pre-check-major-version-upgrade \ + test-instance --target-database-version=POSTGRES_15 + + To perform pre-checks before upgrading a MySQL instance to a target version + (supported in Beta only): + + $ gcloud beta sql instances pre-check-major-version-upgrade \ + test-instance --target-database-version=MYSQL_8_0 + +POSITIONAL ARGUMENTS + INSTANCE + Cloud SQL instance ID. + +REQUIRED FLAGS + --target-database-version=TARGET_DATABASE_VERSION + Target database version for the upgrade. + +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. This + variant is also available: + + $ gcloud sql instances pre-check-major-version-upgrade + diff --git a/gcloud/beta/vector-search/collections/create b/gcloud/beta/vector-search/collections/create index 5dd4e5e3a..bb7394559 100644 --- a/gcloud/beta/vector-search/collections/create +++ b/gcloud/beta/vector-search/collections/create @@ -5,8 +5,9 @@ SYNOPSIS gcloud beta vector-search collections create (COLLECTION : --location=LOCATION) [--async] [--data-schema=DATA_SCHEMA] [--description=DESCRIPTION] - [--display-name=DISPLAY_NAME] [--labels=[LABELS,...]] - [--request-id=REQUEST_ID] [--schema=SCHEMA] + [--display-name=DISPLAY_NAME] + [--encryption-spec-crypto-key-name=ENCRYPTION_SPEC_CRYPTO_KEY_NAME] + [--labels=[LABELS,...]] [--request-id=REQUEST_ID] [--schema=SCHEMA] [--vector-schema=[VECTOR_SCHEMA,...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -33,6 +34,18 @@ EXAMPLES 3}},"genre_embedding":{"denseVector":{"dimensions":4}},"sparse_embed\ ding":{"sparseVector":{}}}' --project=my-project + To create a CMEK-encrypted collection my-collection in project my-project + and location us-central1 to store dense embedding vectors with 100 + dimensions, run: + + $ gcloud beta vector-search collections create my-collection \ + --location=us-central1 --display-name='My Collection' \ + --vector-schema='{"my-embedding-field": {"denseVector": + {"dimensions": 100}}}' \ + --encryption-spec-crypto-key-name='projects/my-project/locations\ + /us-central1/keyRings/my-key-ring/cryptoKeys/my-key' \ + --project=my-project + POSITIONAL ARGUMENTS Collection resource - Identifier. name of resource The arguments in this group can be used to specify the attributes of this resource. (NOTE) Some @@ -81,6 +94,16 @@ FLAGS --display-name=DISPLAY_NAME User-specified display name of the collection + Represents a customer-managed encryption key specification that can be + applied to a Vector Search collection. + + --encryption-spec-crypto-key-name=ENCRYPTION_SPEC_CRYPTO_KEY_NAME + Resource name of the Cloud KMS key used to protect the resource. + + The Cloud KMS key must be in the same region as the resource. It must + have the format + projects/{project}/locations/{location}/keyRings/{key_ring}/cryptoKeys/{crypto_key}. + --labels=[LABELS,...] Labels as key value pairs. diff --git a/gcloud/beta/workbench/instances/create b/gcloud/beta/workbench/instances/create index 85b3435ee..7881f8d4b 100644 --- a/gcloud/beta/workbench/instances/create +++ b/gcloud/beta/workbench/instances/create @@ -203,9 +203,12 @@ FLAGS specified, this defaults to 100. --boot-disk-type=BOOT_DISK_TYPE - Type of boot disk attached to this instance, defaults to standard - persistent disk (PD_STANDARD). BOOT_DISK_TYPE must be one of: - PD_STANDARD, PD_SSD, PD_BALANCED, PD_EXTREME. + Type of boot disk attached to this instance. Defaults to standard + persistent disk (PD_STANDARD) on machine types that support Persistent + Disk, and to HYPERDISK_BALANCED on Hyperdisk-only machine series (e.g. + N4, C4, C4A, M4). BOOT_DISK_TYPE must be one of: PD_STANDARD, PD_SSD, + PD_BALANCED, PD_EXTREME, HYPERDISK_BALANCED, + HYPERDISK_BALANCED_HIGH_AVAILABILITY, HYPERDISK_ML. Key resource - The Cloud KMS (Key Management Service) cryptokey that will be used to protect the boot_disk. The 'Compute Engine Service Agent' @@ -303,9 +306,13 @@ FLAGS specified, this defaults to 100. --data-disk-type=DATA_DISK_TYPE - Type of data disk attached to this instance, defaults to standard - persistent disk (PD_STANDARD). DATA_DISK_TYPE must be one of: - PD_STANDARD, PD_SSD, PD_BALANCED, PD_EXTREME. + Type of data disk attached to this instance. Defaults to standard + persistent disk (PD_STANDARD) on machine types that support Persistent + Disk, and to HYPERDISK_BALANCED on Hyperdisk-only machine series (e.g. + N4, C4, C4A, M4). DATA_DISK_TYPE must be one of: PD_STANDARD, PD_SSD, + PD_BALANCED, PD_EXTREME, HYPERDISK_BALANCED, + HYPERDISK_BALANCED_HIGH_AVAILABILITY, HYPERDISK_ML, HYPERDISK_EXTREME, + HYPERDISK_THROUGHPUT. Key resource - The Cloud KMS (Key Management Service) cryptokey that will be used to protect the data_disk. The 'Compute Engine Service Agent' diff --git a/gcloud/beta/workbench/instances/update b/gcloud/beta/workbench/instances/update index a3aeaf964..9014e4124 100644 --- a/gcloud/beta/workbench/instances/update +++ b/gcloud/beta/workbench/instances/update @@ -4,7 +4,8 @@ NAME SYNOPSIS gcloud beta workbench instances update (INSTANCE : --location=LOCATION) [--async] [--labels=[KEY=VALUE,...]] - [--machine-type=MACHINE_TYPE --metadata=[KEY=VALUE,...] + [--data-disk-resource-policies=[RESOURCE_POLICIES,...] + --machine-type=MACHINE_TYPE --metadata=[KEY=VALUE,...] --tags=[TAGS,...] --accelerator-core-count=ACCELERATOR_CORE_COUNT --accelerator-type=ACCELERATOR_TYPE [--container-repository=CONTAINER_REPOSITORY @@ -75,6 +76,12 @@ FLAGS Gce Setup for the instance + Data disk configurations. + + --data-disk-resource-policies=[RESOURCE_POLICIES,...] + Resource policies to apply to the data disk. Format: + projects/{project}/regions/{region}/resourcePolicies/{policy}. + --machine-type=MACHINE_TYPE The Compute Engine machine type (https://cloud.google.com/sdk/gcloud/reference/compute/machine-types) diff --git a/gcloud/beta/workload-identity/help b/gcloud/beta/workload-identity/help new file mode 100644 index 000000000..95955c282 --- /dev/null +++ b/gcloud/beta/workload-identity/help @@ -0,0 +1,28 @@ +NAME + gcloud beta workload-identity - manage Workload Identity + +SYNOPSIS + gcloud beta workload-identity GROUP [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Manage Workload Identity. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +GROUPS + GROUP is one of the following: + + service-agents + (BETA) Manage Service Agents for Workload Identity. + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud workload-identity + + $ gcloud alpha workload-identity + diff --git a/gcloud/beta/workload-identity/service-agents/generate b/gcloud/beta/workload-identity/service-agents/generate new file mode 100644 index 000000000..ef7f998d2 --- /dev/null +++ b/gcloud/beta/workload-identity/service-agents/generate @@ -0,0 +1,76 @@ +NAME + gcloud beta workload-identity service-agents generate - generate service + agents for a service producer + +SYNOPSIS + gcloud beta workload-identity service-agents generate --service=SERVICE + (--folder=FOLDER | --organization=ORGANIZATION | --project=PROJECT) + [--location=LOCATION; default="global"] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) It can be generated in a project, folder, or organization and + location. + + gcloud beta workload-identity service-agents generate generates service + agents for a given service producer in a specific project, folder, or + organization and location. + +EXAMPLES + To generate service agents for bigquery.googleapis.com in the global + location for the project 123456, run: + + $ gcloud beta workload-identity service-agents generate \ + --service="bigquery.googleapis.com" --location="global" \ + --project="123456" + + To generate service agents for bigquery.googleapis.com in the global + location for the folder 123456, run: + + $ gcloud beta workload-identity service-agents generate \ + --service="bigquery.googleapis.com" --location="global" \ + --folder="123456" + + To generate service agents for bigquery.googleapis.com in the global + location for the organization 123456, run: + + $ gcloud beta workload-identity service-agents generate \ + --service="bigquery.googleapis.com" --location="global" \ + --organization="123456" + +REQUIRED FLAGS + --service=SERVICE + The service producer to generate service agents for (e.g. + bigquery.googleapis.com). + + Exactly one of these must be specified: + + --folder=FOLDER + The folder number to generate service agents for. + + --organization=ORGANIZATION + The organization number to generate service agents for. + + --project=PROJECT + The project number to generate service agents for. + +OPTIONAL FLAGS + --location=LOCATION; default="global" + The location for which to generate the service agents. Defaults to + global. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --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 workload-identity service-agents generate + + $ gcloud alpha workload-identity service-agents generate + diff --git a/gcloud/beta/workload-identity/service-agents/help b/gcloud/beta/workload-identity/service-agents/help new file mode 100644 index 000000000..1b5f204d9 --- /dev/null +++ b/gcloud/beta/workload-identity/service-agents/help @@ -0,0 +1,29 @@ +NAME + gcloud beta workload-identity service-agents - manage Service Agents for + Workload Identity + +SYNOPSIS + gcloud beta workload-identity service-agents COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Manage Service Agents for Workload Identity. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + generate + (BETA) Generate service agents for a service producer. + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud workload-identity service-agents + + $ gcloud alpha workload-identity service-agents + diff --git a/gcloud/beta/workstations/clusters/create b/gcloud/beta/workstations/clusters/create index 2461967ba..afd8e4dd0 100644 --- a/gcloud/beta/workstations/clusters/create +++ b/gcloud/beta/workstations/clusters/create @@ -3,9 +3,9 @@ NAME SYNOPSIS gcloud beta workstations clusters create (CLUSTER : --region=REGION) - [--async] [--domain=DOMAIN] [--enable-private-endpoint] - [--labels=[KEY=VALUE,...]] [--network=NETWORK] - [--subnetwork=SUBNETWORK] [--tags=[KEY=VALUE,...]] + [--async] [--domain=DOMAIN] [--enable-http2] + [--enable-private-endpoint] [--labels=[KEY=VALUE,...]] + [--network=NETWORK] [--subnetwork=SUBNETWORK] [--tags=[KEY=VALUE,...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -64,6 +64,9 @@ FLAGS --domain=DOMAIN Domain used by Workstations for HTTP ingress. + --enable-http2 + Whether HTTP/2 is enabled for the workstation cluster. + --enable-private-endpoint Default is false. If specified, the cluster will be assigned an internal IP address to the Cluster Gateway. This isolates the cluster's diff --git a/gcloud/beta/workstations/clusters/help b/gcloud/beta/workstations/clusters/help index 4fc5b1e11..d82e39c43 100644 --- a/gcloud/beta/workstations/clusters/help +++ b/gcloud/beta/workstations/clusters/help @@ -28,6 +28,9 @@ COMMANDS list (BETA) List workstation clusters. + update + (BETA) Update a workstation cluster. + NOTES This command is currently in beta and might change without notice. These variants are also available: diff --git a/gcloud/beta/workstations/clusters/update b/gcloud/beta/workstations/clusters/update new file mode 100644 index 000000000..d35233747 --- /dev/null +++ b/gcloud/beta/workstations/clusters/update @@ -0,0 +1,111 @@ +NAME + gcloud beta workstations clusters update - update a workstation cluster + +SYNOPSIS + gcloud beta workstations clusters update (CLUSTER : --region=REGION) + [--async] [--display-name=DISPLAY_NAME] [--enable-http2] + [--update-labels=[KEY=VALUE,...]] + [--clear-labels | --remove-labels=[KEY,...]] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Update a workstation cluster. + +EXAMPLES + To update the display name of workstation cluster my-cluster in region + us-central1, run: + + $ gcloud beta workstations clusters update my-cluster \ + --region=us-central1 --display-name='My New Cluster Name' + +POSITIONAL ARGUMENTS + Cluster resource - Arguments and flags that specify the cluster 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 cluster on the command line with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + CLUSTER + ID of the cluster or fully qualified identifier for the cluster. + + To set the cluster attribute: + ▸ provide the argument cluster on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --region=REGION + The name of the region of the cluster. + + To set the region attribute: + ▸ provide the argument cluster on the command line with a fully + specified name; + ▸ provide the argument --region on the command line; + ▸ set the property workstations/region. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --display-name=DISPLAY_NAME + Human-readable name for this workstation cluster. + + --enable-http2 + Enable or disable HTTP/2 for the workstation cluster. + + --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 workstations clusters update --clear-labels + + To remove all existing labels and create two new labels, foo and baz: + + $ gcloud beta workstations clusters 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 workstations/v1beta API. The full documentation for + this API can be found at: https://cloud.google.com/workstations + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud workstations clusters update + + $ gcloud alpha workstations clusters update + diff --git a/gcloud/beta/workstations/ssh b/gcloud/beta/workstations/ssh index 32ee37731..c0b908d18 100644 --- a/gcloud/beta/workstations/ssh +++ b/gcloud/beta/workstations/ssh @@ -6,7 +6,7 @@ SYNOPSIS (WORKSTATION : --cluster=CLUSTER --config=CONFIG --region=REGION) [--command=COMMAND] [--local-host-port=LOCAL_HOST_PORT; default="localhost:0"] - [--port=PORT; default=22] [--ssh-flag=SSH_FLAG] + [--port=PORT; default=22] [--ssh-flag=SSH_FLAG] [--start-workstation] [--user=USER; default="user"] [GCLOUD_WIDE_FLAG ...] [-- SSH_ARGS ...] DESCRIPTION @@ -113,6 +113,10 @@ FLAGS $ gcloud beta workstations ssh --ssh-flag="-vvv" \ --ssh-flag="-L 80:localhost:80" + --start-workstation + If set, automatically starts the workstation if it is currently + stopped. + --user=USER; default="user" The username with which to SSH. diff --git a/gcloud/beta/workstations/start-tcp-tunnel b/gcloud/beta/workstations/start-tcp-tunnel index ff13a4e60..f682effbf 100644 --- a/gcloud/beta/workstations/start-tcp-tunnel +++ b/gcloud/beta/workstations/start-tcp-tunnel @@ -7,7 +7,7 @@ SYNOPSIS (WORKSTATION : --cluster=CLUSTER --config=CONFIG --region=REGION) WORKSTATION_PORT [--local-host-port=LOCAL_HOST_PORT; default="localhost:0"] - [GCLOUD_WIDE_FLAG ...] + [--start-workstation] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) Start a tunnel through which a local process can forward TCP traffic @@ -87,6 +87,10 @@ FLAGS If LOCAL_PORT is 0, an arbitrary unused local port is chosen. + --start-workstation + If set, automatically starts the workstation if it is currently + stopped. + 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/beyondcorp/security-gateways/add-iam-policy-binding b/gcloud/beyondcorp/security-gateways/add-iam-policy-binding new file mode 100644 index 000000000..72ff4a2b6 --- /dev/null +++ b/gcloud/beyondcorp/security-gateways/add-iam-policy-binding @@ -0,0 +1,95 @@ +NAME + gcloud beyondcorp security-gateways add-iam-policy-binding - add an IAM + policy binding to a security gateway + +SYNOPSIS + gcloud beyondcorp security-gateways add-iam-policy-binding + (SECURITY_GATEWAY : --location=LOCATION) --member=PRINCIPAL --role=ROLE + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Adds an IAM policy binding to the given security gateway. + +EXAMPLES + To add an IAM policy binding for the role of + 'roles/beyondcorp.serviceDiscoveryUser' for the user 'test-user@gmail.com' + on a security gateway with ID 'my-security-gateway': + + $ gcloud beyondcorp security-gateways add-iam-policy-binding \ + my-security-gateway --member='user:test-user@gmail.com' \ + --role='roles/beyondcorp.serviceDiscoveryUser' --location=global + + See https://cloud.google.com/iam/docs/managing-policies for details on + policy role and member types. + +POSITIONAL ARGUMENTS + SecurityGateway resource - The security gateway for which to add the IAM + policy 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 security_gateway 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. + + SECURITY_GATEWAY + ID of the securityGateway or fully qualified identifier for the + securityGateway. + + To set the security_gateway attribute: + ▸ provide the argument security_gateway 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 securityGateway resource. We support only + global location. + + To set the location attribute: + ▸ provide the argument security_gateway on the command line with a + fully specified name; + ▸ provide the argument --location on the command line. + +REQUIRED FLAGS + --member=PRINCIPAL + The principal to add the binding for. Should be of the form + user|group|serviceAccount:email or domain:domain. + + Examples: user:test-user@gmail.com, group:admins@example.com, + serviceAccount:test123@example.domain.com, or + domain:example.domain.com. + + Some resources also accept the following special values: + ◆ allUsers - Special identifier that represents anyone who is on the + internet, with or without a Google account. + ◆ allAuthenticatedUsers - Special identifier that represents anyone + who is authenticated with a Google account or a service account. + + --role=ROLE + Role name to assign to the principal. The role name is the complete + path of a predefined role, such as roles/logging.viewer, or the role ID + for a custom role, such as + organizations/{ORGANIZATION_ID}/roles/logging.viewer. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the beyondcorp/v1 API. The full documentation for this + API can be found at: https://cloud.google.com/ + +NOTES + This variant is also available: + + $ gcloud beta beyondcorp security-gateways add-iam-policy-binding + diff --git a/gcloud/beyondcorp/security-gateways/applications/add-iam-policy-binding b/gcloud/beyondcorp/security-gateways/applications/add-iam-policy-binding new file mode 100644 index 000000000..d76b691dd --- /dev/null +++ b/gcloud/beyondcorp/security-gateways/applications/add-iam-policy-binding @@ -0,0 +1,105 @@ +NAME + gcloud beyondcorp security-gateways applications add-iam-policy-binding - + add an IAM policy binding to a security gateway application + +SYNOPSIS + gcloud beyondcorp security-gateways applications add-iam-policy-binding + (APPLICATION : --location=LOCATION --security-gateway=SECURITY_GATEWAY) + --member=PRINCIPAL --role=ROLE [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Adds an IAM policy binding to the given security gateway application. + +EXAMPLES + To add an IAM policy binding for the role of + 'roles/beyondcorp.sgApplicationUser' for the user 'test-user@gmail.com' on + a security gateway application with ID 'my-application': + + $ gcloud beyondcorp security-gateways applications \ + add-iam-policy-binding my-application \ + --member='user:test-user@gmail.com' \ + --role='roles/beyondcorp.sgApplicationUser' --location=global + + See https://cloud.google.com/iam/docs/managing-policies for details on + policy role and member types. + +POSITIONAL ARGUMENTS + Application resource - The security gateway application for which to add + the IAM policy 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 application 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. + + APPLICATION + ID of the application or fully qualified identifier for the + application. + + To set the application attribute: + ▸ provide the argument application 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 application resource. We support only global + location. + + To set the location attribute: + ▸ provide the argument application on the command line with a fully + specified name; + ▸ provide the argument --location on the command line. + + --security-gateway=SECURITY_GATEWAY + The securityGateway id of the application resource. + + To set the security-gateway attribute: + ▸ provide the argument application on the command line with a fully + specified name; + ▸ provide the argument --security-gateway on the command line. + +REQUIRED FLAGS + --member=PRINCIPAL + The principal to add the binding for. Should be of the form + user|group|serviceAccount:email or domain:domain. + + Examples: user:test-user@gmail.com, group:admins@example.com, + serviceAccount:test123@example.domain.com, or + domain:example.domain.com. + + Some resources also accept the following special values: + ◆ allUsers - Special identifier that represents anyone who is on the + internet, with or without a Google account. + ◆ allAuthenticatedUsers - Special identifier that represents anyone + who is authenticated with a Google account or a service account. + + --role=ROLE + Role name to assign to the principal. The role name is the complete + path of a predefined role, such as roles/logging.viewer, or the role ID + for a custom role, such as + organizations/{ORGANIZATION_ID}/roles/logging.viewer. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the beyondcorp/v1 API. The full documentation for this + API can be found at: https://cloud.google.com/ + +NOTES + This variant is also available: + + $ gcloud beta beyondcorp security-gateways applications \ + add-iam-policy-binding + diff --git a/gcloud/beyondcorp/security-gateways/applications/help b/gcloud/beyondcorp/security-gateways/applications/help index b99ba420a..6ce1bfd87 100644 --- a/gcloud/beyondcorp/security-gateways/applications/help +++ b/gcloud/beyondcorp/security-gateways/applications/help @@ -17,6 +17,9 @@ GCLOUD WIDE FLAGS COMMANDS COMMAND is one of the following: + add-iam-policy-binding + Add an IAM policy binding to a security gateway application. + create Create applications. @@ -32,6 +35,9 @@ COMMANDS list List applications. + remove-iam-policy-binding + Remove an IAM policy binding from a security gateway application. + set-iam-policy Set the IAM policy for a security gateway application. diff --git a/gcloud/beyondcorp/security-gateways/applications/remove-iam-policy-binding b/gcloud/beyondcorp/security-gateways/applications/remove-iam-policy-binding new file mode 100644 index 000000000..293a0e6ca --- /dev/null +++ b/gcloud/beyondcorp/security-gateways/applications/remove-iam-policy-binding @@ -0,0 +1,106 @@ +NAME + gcloud beyondcorp security-gateways applications remove-iam-policy-binding + - remove an IAM policy binding from a security gateway application + +SYNOPSIS + gcloud beyondcorp security-gateways applications remove-iam-policy-binding + (APPLICATION : --location=LOCATION --security-gateway=SECURITY_GATEWAY) + --member=PRINCIPAL --role=ROLE [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Removes an IAM policy binding from the given security gateway application. + +EXAMPLES + To remove an IAM policy binding for the role of + 'roles/beyondcorp.sgApplicationUser' for the user 'test-user@gmail.com' on + a security gateway application with ID 'my-application': + + $ gcloud beyondcorp security-gateways applications \ + remove-iam-policy-binding my-application \ + --member='user:test-user@gmail.com' \ + --role='roles/beyondcorp.sgApplicationUser' --location=global + + See https://cloud.google.com/iam/docs/managing-policies for details on + policy role and member types. + +POSITIONAL ARGUMENTS + Application resource - The security gateway application for which to + remove the IAM policy 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 application 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. + + APPLICATION + ID of the application or fully qualified identifier for the + application. + + To set the application attribute: + ▸ provide the argument application 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 application resource. We support only global + location. + + To set the location attribute: + ▸ provide the argument application on the command line with a fully + specified name; + ▸ provide the argument --location on the command line. + + --security-gateway=SECURITY_GATEWAY + The securityGateway id of the application resource. + + To set the security-gateway attribute: + ▸ provide the argument application on the command line with a fully + specified name; + ▸ provide the argument --security-gateway on the command line. + +REQUIRED FLAGS + --member=PRINCIPAL + The principal to remove the binding for. Should be of the form + user|group|serviceAccount:email or domain:domain. + + Examples: user:test-user@gmail.com, group:admins@example.com, + serviceAccount:test123@example.domain.com, or + domain:example.domain.com. + + Deleted principals have an additional deleted: prefix and a ?uid=UID + suffix, where UID is a unique identifier for the principal. Example: + deleted:user:test-user@gmail.com?uid=123456789012345678901. + + Some resources also accept the following special values: + ◆ allUsers - Special identifier that represents anyone who is on the + internet, with or without a Google account. + ◆ allAuthenticatedUsers - Special identifier that represents anyone + who is authenticated with a Google account or a service account. + + --role=ROLE + The role to remove the principal from. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the beyondcorp/v1 API. The full documentation for this + API can be found at: https://cloud.google.com/ + +NOTES + This variant is also available: + + $ gcloud beta beyondcorp security-gateways applications \ + remove-iam-policy-binding + diff --git a/gcloud/beyondcorp/security-gateways/create b/gcloud/beyondcorp/security-gateways/create index 5a575c7ce..68e086c60 100644 --- a/gcloud/beyondcorp/security-gateways/create +++ b/gcloud/beyondcorp/security-gateways/create @@ -5,7 +5,7 @@ SYNOPSIS gcloud beyondcorp security-gateways create (SECURITY_GATEWAY : --location=LOCATION) [--async] [--display-name=DISPLAY_NAME] [--hubs=[HUBS,...]] - [--logging=[LOGGING,...]] [--request-id=REQUEST_ID] + [--request-id=REQUEST_ID] [--proxy-protocol-config-allowed-client-headers=[PROXY_PROTOCOL_CONFIG_ALLOWED_CLIENT_HEADERS, ...] --proxy-protocol-config-client-ip --proxy-protocol-config-gateway-identity=PROXY_PROTOCOL_CONFIG_GATEWAY_IDENTITY --proxy-protocol-config-metadata-headers=[PROXY_PROTOCOL_CONFIG_METADATA_HEADERS, @@ -88,21 +88,6 @@ FLAGS --hubs=path_to_file.(yaml|json) - --logging=[LOGGING,...] - Configuration for Cloud Logging. - - Shorthand Example: - - --logging= - - JSON Example: - - --logging={} - - File Example: - - --logging=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 diff --git a/gcloud/beyondcorp/security-gateways/help b/gcloud/beyondcorp/security-gateways/help index f7be751aa..e863e3092 100644 --- a/gcloud/beyondcorp/security-gateways/help +++ b/gcloud/beyondcorp/security-gateways/help @@ -21,6 +21,9 @@ GROUPS COMMANDS COMMAND is one of the following: + add-iam-policy-binding + Add an IAM policy binding to a security gateway. + create Create securityGateways. @@ -36,6 +39,9 @@ COMMANDS list List securityGateways. + remove-iam-policy-binding + Remove an IAM policy binding from a security gateway. + set-iam-policy Set the IAM policy for a security gateway. diff --git a/gcloud/beyondcorp/security-gateways/remove-iam-policy-binding b/gcloud/beyondcorp/security-gateways/remove-iam-policy-binding new file mode 100644 index 000000000..aab13f270 --- /dev/null +++ b/gcloud/beyondcorp/security-gateways/remove-iam-policy-binding @@ -0,0 +1,96 @@ +NAME + gcloud beyondcorp security-gateways remove-iam-policy-binding - remove an + IAM policy binding from a security gateway + +SYNOPSIS + gcloud beyondcorp security-gateways remove-iam-policy-binding + (SECURITY_GATEWAY : --location=LOCATION) --member=PRINCIPAL --role=ROLE + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Removes an IAM policy binding from the given security gateway. + +EXAMPLES + To remove an IAM policy binding for the role of + 'roles/beyondcorp.serviceDiscoveryUser' for the user 'test-user@gmail.com' + on a security gateway with ID 'my-security-gateway': + + $ gcloud beyondcorp security-gateways remove-iam-policy-binding \ + my-security-gateway --member='user:test-user@gmail.com' \ + --role='roles/beyondcorp.serviceDiscoveryUser' --location=global + + See https://cloud.google.com/iam/docs/managing-policies for details on + policy role and member types. + +POSITIONAL ARGUMENTS + SecurityGateway resource - The security gateway for which to remove the + IAM policy 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 security_gateway 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. + + SECURITY_GATEWAY + ID of the securityGateway or fully qualified identifier for the + securityGateway. + + To set the security_gateway attribute: + ▸ provide the argument security_gateway 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 securityGateway resource. We support only + global location. + + To set the location attribute: + ▸ provide the argument security_gateway on the command line with a + fully specified name; + ▸ provide the argument --location on the command line. + +REQUIRED FLAGS + --member=PRINCIPAL + The principal to remove the binding for. Should be of the form + user|group|serviceAccount:email or domain:domain. + + Examples: user:test-user@gmail.com, group:admins@example.com, + serviceAccount:test123@example.domain.com, or + domain:example.domain.com. + + Deleted principals have an additional deleted: prefix and a ?uid=UID + suffix, where UID is a unique identifier for the principal. Example: + deleted:user:test-user@gmail.com?uid=123456789012345678901. + + Some resources also accept the following special values: + ◆ allUsers - Special identifier that represents anyone who is on the + internet, with or without a Google account. + ◆ allAuthenticatedUsers - Special identifier that represents anyone + who is authenticated with a Google account or a service account. + + --role=ROLE + The role to remove the principal from. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the beyondcorp/v1 API. The full documentation for this + API can be found at: https://cloud.google.com/ + +NOTES + This variant is also available: + + $ gcloud beta beyondcorp security-gateways remove-iam-policy-binding + diff --git a/gcloud/beyondcorp/security-gateways/update b/gcloud/beyondcorp/security-gateways/update index 586c00980..b48ce9eb3 100644 --- a/gcloud/beyondcorp/security-gateways/update +++ b/gcloud/beyondcorp/security-gateways/update @@ -5,7 +5,6 @@ SYNOPSIS gcloud beyondcorp security-gateways update (SECURITY_GATEWAY : --location=LOCATION) [--async] [--display-name=DISPLAY_NAME] [--request-id=REQUEST_ID] - [--clear-logging | --logging=[LOGGING,...]] [--clear-proxy-protocol-config --[no-]proxy-protocol-config-client-ip --proxy-protocol-config-gateway-identity=PROXY_PROTOCOL_CONFIG_GATEWAY_IDENTITY --contextual-headers-output-type=CONTEXTUAL_HEADERS_OUTPUT_TYPE --device-info-output-type=DEVICE_INFO_OUTPUT_TYPE --group-info-output-type=GROUP_INFO_OUTPUT_TYPE --user-info-output-type=USER_INFO_OUTPUT_TYPE --proxy-protocol-config-allowed-client-headers=[PROXY_PROTOCOL_CONFIG_ALLOWED_CLIENT_HEADERS, ...] @@ -90,33 +89,6 @@ FLAGS The request ID must be a valid UUID with the exception that zero UUID is not supported (00000000-0000-0000-0000-000000000000). - Set the value of - googleCloudBeyondcorpSecuritygatewaysV1SecurityGateway.logging by using - flag [logging] or flags []. - - At most one of these can be specified: - - Configuration for Cloud Logging. - - --clear-logging - Set googleCloudBeyondcorpSecuritygatewaysV1SecurityGateway.logging - back to default value. - - --logging=[LOGGING,...] - Configuration for Cloud Logging. - - Shorthand Example: - - --logging= - - JSON Example: - - --logging={} - - File Example: - - --logging=path_to_file.(yaml|json) - The configuration for the proxy. --clear-proxy-protocol-config diff --git a/gcloud/biglake/iceberg/catalogs/create b/gcloud/biglake/iceberg/catalogs/create index efb3e2e45..e241e0949 100644 --- a/gcloud/biglake/iceberg/catalogs/create +++ b/gcloud/biglake/iceberg/catalogs/create @@ -60,7 +60,7 @@ OPTIONAL FLAGS Use vended credentials to access the catalog. --description=DESCRIPTION - Description of the resource being created. + Description of the resource. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/biglake/iceberg/catalogs/update b/gcloud/biglake/iceberg/catalogs/update index ef4cbc9f0..4409d06d9 100644 --- a/gcloud/biglake/iceberg/catalogs/update +++ b/gcloud/biglake/iceberg/catalogs/update @@ -10,6 +10,12 @@ SYNOPSIS DESCRIPTION Update a BigLake Iceberg REST catalog. +EXAMPLES + To update the description of a catalog my-catalog, run: + + $ gcloud biglake iceberg catalogs update my-catalog \ + --description="updated description" + POSITIONAL ARGUMENTS Catalog resource - The Iceberg Catalog to update. This represents a Cloud resource. (NOTE) Some attributes are not given arguments in this group but @@ -40,7 +46,7 @@ FLAGS Use vended credentials to access the catalog. --description=DESCRIPTION - Description of the resource being created. + Description of the resource. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/biglake/iceberg/help b/gcloud/biglake/iceberg/help index 3c895c25f..368d4f7d2 100644 --- a/gcloud/biglake/iceberg/help +++ b/gcloud/biglake/iceberg/help @@ -21,6 +21,9 @@ GROUPS namespaces Manage BigLake Iceberg REST catalog namespaces. + tables + Manage BigLake Iceberg REST catalog tables. + NOTES These variants are also available: diff --git a/gcloud/biglake/iceberg/tables/create b/gcloud/biglake/iceberg/tables/create new file mode 100644 index 000000000..73ec05b41 --- /dev/null +++ b/gcloud/biglake/iceberg/tables/create @@ -0,0 +1,126 @@ +NAME + gcloud biglake iceberg tables create - create a BigLake Iceberg table + +SYNOPSIS + gcloud biglake iceberg tables create --create-from-file=CREATE_FROM_FILE + (--namespace=NAMESPACE : --catalog=CATALOG) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Create a BigLake Iceberg table. + +EXAMPLES + To create a table my_table in parent catalog my-catalog and namespace + my-namespace using a creation request from table_creation.json, run: + + $ gcloud biglake iceberg tables create --namespace=my-namespace \ + --catalog=my-catalog --create-from-file=table_creation.json + + The table name and schema fields are required and must be specified in + table_creation.json. + + Example table_creation.json: + + { + "name": "my_table", + "location": "gs://my-catalog/my-namespace/my_table", + "schema": { + "type": "struct", + "schema-id": 0, + "fields": [ + { + "id": 1, + "name": "user_id", + "required": true, + "type": "long", + "doc": "Unique identifier for the user" + }, + { + "id": 2, + "name": "username", + "required": false, + "type": "string" + } + ] + }, + "partition-spec": { + "spec-id": 0, + "fields": [ + { + "name": "user_id_bucket", + "transform": "bucket[5]", + "source-id": 1, + "partition-id": 1001 + } + ] + }, + "write-order": { + "order-id": 0, + "fields": [ + { + "transform": "identity", + "source-id": 1, + "direction": "asc", + "null-order": "nulls-last" + } + ] + }, + "stage-create": false, + "properties": { + "owner": "owner", + "environment": "test", + "write.format.default": "parquet", + "comment": "Creating a new table" + } + } + +REQUIRED FLAGS + --create-from-file=CREATE_FROM_FILE + Path to a JSON file containing the table creation request. The format + must follow the Apache Iceberg REST Catalog Open API specification for + CreateTableRequest. The fields name and schema must be specified. + + Namespace resource - The Iceberg Namespace 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 --namespace on the command line with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + --namespace=NAMESPACE + ID of the namespace or fully qualified identifier for the namespace. + + To set the namespace attribute: + ▸ provide the argument --namespace on the command line. + + This flag argument must be specified if any of the other arguments in + this group are specified. + + --catalog=CATALOG + The Iceberg Catalog for the resource. + + To set the catalog attribute: + ▸ provide the argument --namespace on the command line with a fully + specified name; + ▸ provide the argument --catalog on the command line. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --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 biglake iceberg tables create + + $ gcloud beta biglake iceberg tables create + diff --git a/gcloud/biglake/iceberg/tables/delete b/gcloud/biglake/iceberg/tables/delete new file mode 100644 index 000000000..4b2f06901 --- /dev/null +++ b/gcloud/biglake/iceberg/tables/delete @@ -0,0 +1,72 @@ +NAME + gcloud biglake iceberg tables delete - delete a BigLake Iceberg table + +SYNOPSIS + gcloud biglake iceberg tables delete + (TABLE : --catalog=CATALOG --namespace=NAMESPACE) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Delete a BigLake Iceberg table. + +EXAMPLES + To delete a table in parent catalog my-catalog and namespace my-namespace, + run: + + $ gcloud biglake iceberg tables delete my-table \ + --namespace=my-namespace --catalog=my-catalog + +POSITIONAL ARGUMENTS + Table resource - The Iceberg Table 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 table on the command line with a fully specified + name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + TABLE + ID of the table or fully qualified identifier for the table. + + To set the table attribute: + ▸ provide the argument table on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --catalog=CATALOG + The Iceberg Catalog for the resource. + + To set the catalog attribute: + ▸ provide the argument table on the command line with a fully + specified name; + ▸ provide the argument --catalog on the command line. + + --namespace=NAMESPACE + The Iceberg Namespace for the resource. + + To set the namespace attribute: + ▸ provide the argument table on the command line with a fully + specified name; + ▸ provide the argument --namespace on the command line. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --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 biglake iceberg tables delete + + $ gcloud beta biglake iceberg tables delete + diff --git a/gcloud/biglake/iceberg/tables/describe b/gcloud/biglake/iceberg/tables/describe new file mode 100644 index 000000000..e28b2b3e6 --- /dev/null +++ b/gcloud/biglake/iceberg/tables/describe @@ -0,0 +1,76 @@ +NAME + gcloud biglake iceberg tables describe - describe a BigLake Iceberg table + +SYNOPSIS + gcloud biglake iceberg tables describe + (TABLE : --catalog=CATALOG --namespace=NAMESPACE) + [--snapshots=SNAPSHOTS] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Describe a BigLake Iceberg table. + +EXAMPLES + To describe table my-table in parent catalog my-catalog and namespace + my-namespace, run: + + $ gcloud biglake iceberg tables describe my-table \ + --namespace=my-namespace --catalog=my-catalog + +POSITIONAL ARGUMENTS + Table resource - The Iceberg Table 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 table on the command line with a fully specified + name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + TABLE + ID of the table or fully qualified identifier for the table. + + To set the table attribute: + ▸ provide the argument table on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --catalog=CATALOG + The Iceberg Catalog for the resource. + + To set the catalog attribute: + ▸ provide the argument table on the command line with a fully + specified name; + ▸ provide the argument --catalog on the command line. + + --namespace=NAMESPACE + The Iceberg Namespace for the resource. + + To set the namespace attribute: + ▸ provide the argument table on the command line with a fully + specified name; + ▸ provide the argument --namespace on the command line. + +FLAGS + --snapshots=SNAPSHOTS + Snapshot to get. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --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 biglake iceberg tables describe + + $ gcloud beta biglake iceberg tables describe + diff --git a/gcloud/biglake/iceberg/tables/get-iam-policy b/gcloud/biglake/iceberg/tables/get-iam-policy new file mode 100644 index 000000000..7d86bbb09 --- /dev/null +++ b/gcloud/biglake/iceberg/tables/get-iam-policy @@ -0,0 +1,100 @@ +NAME + gcloud biglake iceberg tables get-iam-policy - get the IAM policy for a + BigLake Iceberg REST catalog table + +SYNOPSIS + gcloud biglake iceberg tables get-iam-policy + (TABLE : --catalog=CATALOG --namespace=NAMESPACE) [--filter=EXPRESSION] + [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Gets the IAM policy for a BigLake Iceberg REST catalog table. + +EXAMPLES + To get the IAM policy for the catalog my-catalog, namespace my-namespace, + and table my-table run: + + $ gcloud biglake iceberg tables get-iam-policy my-table \ + --catalog=my-catalog --namespace=my-namespace + +POSITIONAL ARGUMENTS + Table resource - The Iceberg Table to get the IAM policy for. The + arguments in this group can be used to specify the attributes of this + resource. (NOTE) Some attributes are not given arguments in this group but + can be set in other ways. + + To set the project attribute: + ◆ provide the argument table on the command line with a fully specified + name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + TABLE + ID of the table or fully qualified identifier for the table. + + To set the table attribute: + ▸ provide the argument table on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --catalog=CATALOG + The Iceberg Catalog for the resource. + + To set the catalog attribute: + ▸ provide the argument table on the command line with a fully + specified name; + ▸ provide the argument --catalog on the command line. + + --namespace=NAMESPACE + The Iceberg Namespace for the resource. + + To set the namespace attribute: + ▸ provide the argument table on the command line with a fully + specified name; + ▸ provide the argument --namespace on the command line. + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + These variants are also available: + + $ gcloud alpha biglake iceberg tables get-iam-policy + + $ gcloud beta biglake iceberg tables get-iam-policy + diff --git a/gcloud/biglake/iceberg/tables/help b/gcloud/biglake/iceberg/tables/help new file mode 100644 index 000000000..aef3f084e --- /dev/null +++ b/gcloud/biglake/iceberg/tables/help @@ -0,0 +1,48 @@ +NAME + gcloud biglake iceberg tables - manage BigLake Iceberg REST catalog tables + +SYNOPSIS + gcloud biglake iceberg tables COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Manage BigLake Iceberg REST catalog tables. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + create + Create a BigLake Iceberg table. + + delete + Delete a BigLake Iceberg table. + + describe + Describe a BigLake Iceberg table. + + get-iam-policy + Get the IAM policy for a BigLake Iceberg REST catalog table. + + list + List BigLake Iceberg REST tables. + + register + Register a BigLake Iceberg table. + + set-iam-policy + Set the IAM policy for a BigLake Iceberg REST catalog table. + + update + Update a BigLake Iceberg table. + +NOTES + These variants are also available: + + $ gcloud alpha biglake iceberg tables + + $ gcloud beta biglake iceberg tables + diff --git a/gcloud/biglake/iceberg/tables/list b/gcloud/biglake/iceberg/tables/list new file mode 100644 index 000000000..345947b83 --- /dev/null +++ b/gcloud/biglake/iceberg/tables/list @@ -0,0 +1,97 @@ +NAME + gcloud biglake iceberg tables list - list BigLake Iceberg REST tables + +SYNOPSIS + gcloud biglake iceberg tables list + (--namespace=NAMESPACE : --catalog=CATALOG) [--filter=EXPRESSION] + [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + List BigLake Iceberg REST tables. + +EXAMPLES + To list tables in parent catalog my-catalog and namespace my-namespace, + run: + + $ gcloud biglake iceberg tables list --namespace=my-namespace \ + --catalog=my-catalog + +REQUIRED FLAGS + Namespace resource - The Iceberg Namespace to list tables from. The + arguments in this group can be used to specify the attributes of this + resource. (NOTE) Some attributes are not given arguments in this group but + can be set in other ways. + + To set the project attribute: + ◆ provide the argument --namespace on the command line with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + --namespace=NAMESPACE + ID of the namespace or fully qualified identifier for the namespace. + + To set the namespace attribute: + ▸ provide the argument --namespace on the command line. + + This flag argument must be specified if any of the other arguments in + this group are specified. + + --catalog=CATALOG + The Iceberg Catalog for the resource. + + To set the catalog attribute: + ▸ provide the argument --namespace on the command line with a fully + specified name; + ▸ provide the argument --catalog on the command line. + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + + --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 biglake iceberg tables list + + $ gcloud beta biglake iceberg tables list + diff --git a/gcloud/biglake/iceberg/tables/register b/gcloud/biglake/iceberg/tables/register new file mode 100644 index 000000000..ff84d1d91 --- /dev/null +++ b/gcloud/biglake/iceberg/tables/register @@ -0,0 +1,89 @@ +NAME + gcloud biglake iceberg tables register - register a BigLake Iceberg table + +SYNOPSIS + gcloud biglake iceberg tables register + (TABLE : --catalog=CATALOG --namespace=NAMESPACE) + --metadata-location=METADATA_LOCATION [--overwrite] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Register a BigLake Iceberg table. + +EXAMPLES + To register table my-table in parent catalog my-catalog and namespace + my-namespace, run: + + $ gcloud biglake iceberg tables register my-table \ + --namespace=my-namespace --catalog=my-catalog \ + --metadata-location=gs://my-bucket/metadata.json + + To overwrite table my-table in parent catalog my-catalog and namespace + my-namespace, run: + + $ gcloud biglake iceberg tables register my-table \ + --namespace=my-namespace --catalog=my-catalog \ + --metadata-location=gs://my-bucket/metadata.json --overwrite + +POSITIONAL ARGUMENTS + Table resource - The Iceberg Table to register. The arguments in this + group can be used to specify the attributes of this resource. (NOTE) Some + attributes are not given arguments in this group but can be set in other + ways. + + To set the project attribute: + ◆ provide the argument table on the command line with a fully specified + name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + TABLE + ID of the table or fully qualified identifier for the table. + + To set the table attribute: + ▸ provide the argument table on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --catalog=CATALOG + The Iceberg Catalog for the resource. + + To set the catalog attribute: + ▸ provide the argument table on the command line with a fully + specified name; + ▸ provide the argument --catalog on the command line. + + --namespace=NAMESPACE + The Iceberg Namespace for the resource. + + To set the namespace attribute: + ▸ provide the argument table on the command line with a fully + specified name; + ▸ provide the argument --namespace on the command line. + +REQUIRED FLAGS + --metadata-location=METADATA_LOCATION + Metadata location of the table. + +OPTIONAL FLAGS + --overwrite + Overwrite the table if it already exists. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --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 biglake iceberg tables register + + $ gcloud beta biglake iceberg tables register + diff --git a/gcloud/biglake/iceberg/tables/set-iam-policy b/gcloud/biglake/iceberg/tables/set-iam-policy new file mode 100644 index 000000000..fae3d3aad --- /dev/null +++ b/gcloud/biglake/iceberg/tables/set-iam-policy @@ -0,0 +1,80 @@ +NAME + gcloud biglake iceberg tables set-iam-policy - set the IAM policy for a + BigLake Iceberg REST catalog table + +SYNOPSIS + gcloud biglake iceberg tables set-iam-policy + (TABLE : --catalog=CATALOG --namespace=NAMESPACE) POLICY_FILE + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Sets the IAM policy for a BigLake Iceberg REST catalog table. + +EXAMPLES + To set the IAM policy for the catalog my-catalog, namespace my-namespace, + and table my-table with the policy in policy.json run: + + $ gcloud biglake iceberg tables set-iam-policy my-table \ + policy.json --catalog=my-catalog --namespace=my-namespace + +POSITIONAL ARGUMENTS + Table resource - The Iceberg Table to set the IAM policy for. The + arguments in this group can be used to specify the attributes of this + resource. (NOTE) Some attributes are not given arguments in this group but + can be set in other ways. + + To set the project attribute: + ◆ provide the argument table on the command line with a fully specified + name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + TABLE + ID of the table or fully qualified identifier for the table. + + To set the table attribute: + ▸ provide the argument table on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --catalog=CATALOG + The Iceberg Catalog for the resource. + + To set the catalog attribute: + ▸ provide the argument table on the command line with a fully + specified name; + ▸ provide the argument --catalog on the command line. + + --namespace=NAMESPACE + The Iceberg Namespace for the resource. + + To set the namespace attribute: + ▸ provide the argument table on the command line with a fully + specified name; + ▸ provide the argument --namespace on the command line. + + POLICY_FILE + Path to a local JSON or YAML formatted file containing a valid policy. + + The output of the get-iam-policy command is a valid file, as is any + JSON or YAML file conforming to the structure of a Policy + (https://cloud.google.com/iam/reference/rest/v1/Policy). + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + These variants are also available: + + $ gcloud alpha biglake iceberg tables set-iam-policy + + $ gcloud beta biglake iceberg tables set-iam-policy + diff --git a/gcloud/biglake/iceberg/tables/update b/gcloud/biglake/iceberg/tables/update new file mode 100644 index 000000000..5b8660988 --- /dev/null +++ b/gcloud/biglake/iceberg/tables/update @@ -0,0 +1,96 @@ +NAME + gcloud biglake iceberg tables update - update a BigLake Iceberg table + +SYNOPSIS + gcloud biglake iceberg tables update + (TABLE : --catalog=CATALOG --namespace=NAMESPACE) [--clear-properties] + [--remove-properties=[KEY,...]] [--update-properties=[KEY=VALUE,...]] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Update a BigLake Iceberg table. + +EXAMPLES + To add or update properties in a table my-table in parent catalog + my-catalog and namespace my-namespace, with properties + key1=value1,key2=value2, run: + + $ gcloud biglake iceberg tables update my-table \ + --namespace=my-namespace --catalog=my-catalog \ + --update-properties=key1=value1,key2=value2 + + To remove properties key1,key2 from a table, run: + + $ gcloud biglake iceberg tables update my-table \ + --namespace=my-namespace --catalog=my-catalog \ + --remove-properties=key1,key2 + + To clear all properties from a table, run: + + $ gcloud biglake iceberg tables update my-table \ + --namespace=my-namespace --catalog=my-catalog --clear-properties + +POSITIONAL ARGUMENTS + Table resource - The Iceberg Table 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 table on the command line with a fully specified + name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + TABLE + ID of the table or fully qualified identifier for the table. + + To set the table attribute: + ▸ provide the argument table on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --catalog=CATALOG + The Iceberg Catalog for the resource. + + To set the catalog attribute: + ▸ provide the argument table on the command line with a fully + specified name; + ▸ provide the argument --catalog on the command line. + + --namespace=NAMESPACE + The Iceberg Namespace for the resource. + + To set the namespace attribute: + ▸ provide the argument table on the command line with a fully + specified name; + ▸ provide the argument --namespace on the command line. + +FLAGS + --clear-properties + Clear all properties from the namespace. + + --remove-properties=[KEY,...] + List of properties to remove. + + --update-properties=[KEY=VALUE,...] + List of properties to update or add. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --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 biglake iceberg tables update + + $ gcloud beta biglake iceberg tables update + diff --git a/gcloud/bigtable/instances/create b/gcloud/bigtable/instances/create index 8f70736aa..12b92b472 100644 --- a/gcloud/bigtable/instances/create +++ b/gcloud/bigtable/instances/create @@ -12,7 +12,7 @@ SYNOPSIS autoscaling-storage-target=AUTOSCALING_STORAGE_TARGET],...]] [--cluster-num-nodes=CLUSTER_NUM_NODES] [--cluster-storage-type=CLUSTER_STORAGE_TYPE; default="ssd"] - [--cluster-zone=CLUSTER_ZONE] + [--cluster-zone=CLUSTER_ZONE] [--edition=EDITION] [--instance-type=INSTANCE_TYPE; default="PRODUCTION"] [GCLOUD_WIDE_FLAG ...] @@ -40,6 +40,13 @@ EXAMPLES --display-name="HDD Instance" --cluster-storage-type=HDD \ --cluster-config=id=my-cluster-id,zone=us-east1-c,nodes=10 + To create an instance with edition ENTERPRISE_PLUS, run: + + $ gcloud bigtable instances create my-enterprise-plus-instance \ + --display-name="Enterprise Plus Instance" \ + --edition=ENTERPRISE_PLUS \ + --cluster-config=id=my-cluster-id,zone=us-east1-c,nodes=1 + POSITIONAL ARGUMENTS Instance resource - The instance to create. This represents a Cloud resource. (NOTE) Some attributes are not given arguments in this group but @@ -121,6 +128,10 @@ OPTIONAL FLAGS The --cluster-zone argument is deprecated; use --cluster-config instead. + --edition=EDITION + The edition of the instance. EDITION must be one of: ENTERPRISE, + ENTERPRISE_PLUS. + --instance-type=INSTANCE_TYPE; default="PRODUCTION" (DEPRECATED) The type of instance to create. diff --git a/gcloud/bigtable/instances/tables/create b/gcloud/bigtable/instances/tables/create index 200776e90..aad6e47bf 100644 --- a/gcloud/bigtable/instances/tables/create +++ b/gcloud/bigtable/instances/tables/create @@ -8,8 +8,10 @@ SYNOPSIS [--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 ...] + [--enable-automated-backup + | --automated-backup-locations=[LOCATION,...] + --automated-backup-retention-period=AUTOMATED_BACKUP_RETENTION_PERIOD] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION Create a new Cloud Bigtable table. @@ -78,6 +80,13 @@ EXAMPLES --instance=my-instance --column-families="my-family" \ --automated-backup-retention_period=30d + To create a table my-table with a custom automated backup policy configured + to take backups in only us-central1-b and us-east1-c, run: + + $ gcloud bigtable instances tables create my-table \ + --instance=my-instance \ + --automated-backup-locations=us-central1-b,us-east1-c + POSITIONAL ARGUMENTS Table resource - Cloud Bigtable table to create. The arguments in this group can be used to specify the attributes of this resource. (NOTE) Some @@ -160,15 +169,28 @@ OPTIONAL FLAGS At most one of these can be specified: - --automated-backup-retention-period=AUTOMATED_BACKUP_RETENTION_PERIOD - The retention period of automated backup in the format of 30d for 30 - days. Min retention period is 3d and max is 90d. Setting this flag - will enable automated backup for the table. - --enable-automated-backup Once set, enables the default automated backup policy (retention_period=7d, frequency=1d) for the table. + Or at least one of these can be specified: + + Group for automated backup policy parameters. + + --automated-backup-locations=[LOCATION,...] + List of Cloud Bigtable zones where automated backups are allowed to + be created. If empty, automated backups will be created in all + zones of the instance. Locations are in the format + projects/{project}/locations/{zone}. Setting this flag will enable + automated backup for the table. If automated backup retention + period is not specified, it defaults to 7 days. + + --automated-backup-retention-period=AUTOMATED_BACKUP_RETENTION_PERIOD + The retention period of automated backup in the format of 30d for + 30 days. Min retention period is 3d and max is 90d. Setting this + flag will enable automated backup for the table. If automated + backup retention period is not specified, it defaults to 7 days. + 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/instances/tables/update b/gcloud/bigtable/instances/tables/update index 7a1635c31..3c4bd3bd1 100644 --- a/gcloud/bigtable/instances/tables/update +++ b/gcloud/bigtable/instances/tables/update @@ -6,7 +6,9 @@ SYNOPSIS gcloud bigtable instances tables update (TABLE : --instance=INSTANCE) [--async] [--deletion-protection] [--row-key-schema-pre-encoded-bytes] [--automated-backup-retention-period=AUTOMATED_BACKUP_RETENTION_PERIOD - | --disable-automated-backup | --enable-automated-backup] + --automated-backup-locations=[LOCATION,...] + | --clear-automated-backup-locations | --disable-automated-backup + | --enable-automated-backup] [--change-stream-retention-period=CHANGE_STREAM_RETENTION_PERIOD | --clear-change-stream-retention-period] [--clear-row-key-schema @@ -54,7 +56,19 @@ EXAMPLES retain backups for 30 days, run: $ gcloud bigtable instances tables update my-table \ - --instance=my-instance --automated-backup-retention_period=30d + --instance=my-instance --automated-backup-retention-period=30d + + To enable or update a custom automated backup policy and configure it to + take backups in only us-central1-b and us-east1-c, run: + + $ gcloud bigtable instances tables update my-table \ + --instance=my-instance \ + --automated-backup-locations=us-central1-b,us-east1-c + + To empty the automated backup locations list, run: + + $ gcloud bigtable instances tables update my-table \ + --instance=my-instance --clear-automated-backup-locations POSITIONAL ARGUMENTS Table resource - Cloud Bigtable table to update. The arguments in this @@ -107,19 +121,35 @@ FLAGS At most one of these can be specified: + Group for automated backup policy parameters. + --automated-backup-retention-period=AUTOMATED_BACKUP_RETENTION_PERIOD The retention period of automated backup in the format of 30d for 30 days. Min retention period is 3d and max is 90d. Setting this flag will enable automated backup for the table. - --disable-automated-backup - Once set, disables automated backup policy for the table. + At most one of these can be specified: - --enable-automated-backup - Once set, enables the default automated backup policy - (retention_period=7d, frequency=1d) for the table. Note: If a table - has automated backup enabled, this flag resets it to the default - policy. + --automated-backup-locations=[LOCATION,...] + List of Cloud Bigtable zones where automated backups are allowed to + be created. If empty, automated backups will be created in all + zones of the instance. Locations are in the format + projects/{project}/locations/{zone}. Setting this flag will enable + automated backup for the table. + + --clear-automated-backup-locations + Empty the automated backup locations list if populated. + + At most one of these can be specified: + + --disable-automated-backup + Once set, disables automated backup policy for the table. + + --enable-automated-backup + Once set, enables the default automated backup policy + (retention_period=7d, frequency=1d) for the table. Note: If a table + has automated backup enabled, this flag resets it to the default + policy. At most one of these can be specified: diff --git a/gcloud/bigtable/instances/update b/gcloud/bigtable/instances/update index 956e8c076..e0f5eb536 100644 --- a/gcloud/bigtable/instances/update +++ b/gcloud/bigtable/instances/update @@ -3,7 +3,7 @@ NAME SYNOPSIS gcloud bigtable instances update INSTANCE [--display-name=DISPLAY_NAME] - [GCLOUD_WIDE_FLAG ...] + [--edition=EDITION] [GCLOUD_WIDE_FLAG ...] DESCRIPTION Modify an existing Bigtable instance. @@ -14,6 +14,11 @@ EXAMPLES $ gcloud bigtable instances update my-instance-id \ --display-name="Updated Instance Name" + To update the edition for an instance to ENTERPRISE_PLUS, run: + + $ gcloud bigtable instances update my-instance-id \ + --edition=ENTERPRISE_PLUS + POSITIONAL ARGUMENTS Instance resource - The instance to update. This represents a Cloud resource. (NOTE) Some attributes are not given arguments in this group but @@ -37,6 +42,10 @@ FLAGS --display-name=DISPLAY_NAME Friendly name of the instance. + --edition=EDITION + The edition of the instance. EDITION must be one of: ENTERPRISE, + ENTERPRISE_PLUS. + 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/tables/create b/gcloud/bigtable/tables/create index 16b0acf0b..04e214eb7 100644 --- a/gcloud/bigtable/tables/create +++ b/gcloud/bigtable/tables/create @@ -8,8 +8,10 @@ SYNOPSIS [--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 ...] + [--enable-automated-backup + | --automated-backup-locations=[LOCATION,...] + --automated-backup-retention-period=AUTOMATED_BACKUP_RETENTION_PERIOD] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION Create a new Cloud Bigtable table. @@ -72,6 +74,12 @@ EXAMPLES --column-families="my-family" \ --automated-backup-retention_period=30d + To create a table my-table with a custom automated backup policy configured + to take backups in only us-central1-b and us-east1-c, run: + + $ gcloud bigtable tables create my-table --instance=my-instance \ + --automated-backup-locations=us-central1-b,us-east1-c + POSITIONAL ARGUMENTS Table resource - Cloud Bigtable table to create. The arguments in this group can be used to specify the attributes of this resource. (NOTE) Some @@ -154,15 +162,28 @@ OPTIONAL FLAGS At most one of these can be specified: - --automated-backup-retention-period=AUTOMATED_BACKUP_RETENTION_PERIOD - The retention period of automated backup in the format of 30d for 30 - days. Min retention period is 3d and max is 90d. Setting this flag - will enable automated backup for the table. - --enable-automated-backup Once set, enables the default automated backup policy (retention_period=7d, frequency=1d) for the table. + Or at least one of these can be specified: + + Group for automated backup policy parameters. + + --automated-backup-locations=[LOCATION,...] + List of Cloud Bigtable zones where automated backups are allowed to + be created. If empty, automated backups will be created in all + zones of the instance. Locations are in the format + projects/{project}/locations/{zone}. Setting this flag will enable + automated backup for the table. If automated backup retention + period is not specified, it defaults to 7 days. + + --automated-backup-retention-period=AUTOMATED_BACKUP_RETENTION_PERIOD + The retention period of automated backup in the format of 30d for + 30 days. Min retention period is 3d and max is 90d. Setting this + flag will enable automated backup for the table. If automated + backup retention period is not specified, it defaults to 7 days. + 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/tables/update b/gcloud/bigtable/tables/update index e4f08dadf..c6ffdd8f8 100644 --- a/gcloud/bigtable/tables/update +++ b/gcloud/bigtable/tables/update @@ -5,7 +5,9 @@ SYNOPSIS gcloud bigtable tables update (TABLE : --instance=INSTANCE) [--async] [--deletion-protection] [--row-key-schema-pre-encoded-bytes] [--automated-backup-retention-period=AUTOMATED_BACKUP_RETENTION_PERIOD - | --disable-automated-backup | --enable-automated-backup] + --automated-backup-locations=[LOCATION,...] + | --clear-automated-backup-locations | --disable-automated-backup + | --enable-automated-backup] [--change-stream-retention-period=CHANGE_STREAM_RETENTION_PERIOD | --clear-change-stream-retention-period] [--clear-row-key-schema @@ -53,7 +55,18 @@ EXAMPLES retain backups for 30 days, run: $ gcloud bigtable tables update my-table --instance=my-instance \ - --automated-backup-retention_period=30d + --automated-backup-retention-period=30d + + To enable or update a custom automated backup policy and configure it to + take backups in only us-central1-b and us-east1-c, run: + + $ gcloud bigtable tables update my-table --instance=my-instance \ + --automated-backup-locations=us-central1-b,us-east1-c + + To empty the automated backup locations list, run: + + $ gcloud bigtable tables update my-table --instance=my-instance \ + --clear-automated-backup-locations POSITIONAL ARGUMENTS Table resource - Cloud Bigtable table to update. The arguments in this @@ -106,19 +119,35 @@ FLAGS At most one of these can be specified: + Group for automated backup policy parameters. + --automated-backup-retention-period=AUTOMATED_BACKUP_RETENTION_PERIOD The retention period of automated backup in the format of 30d for 30 days. Min retention period is 3d and max is 90d. Setting this flag will enable automated backup for the table. - --disable-automated-backup - Once set, disables automated backup policy for the table. + At most one of these can be specified: - --enable-automated-backup - Once set, enables the default automated backup policy - (retention_period=7d, frequency=1d) for the table. Note: If a table - has automated backup enabled, this flag resets it to the default - policy. + --automated-backup-locations=[LOCATION,...] + List of Cloud Bigtable zones where automated backups are allowed to + be created. If empty, automated backups will be created in all + zones of the instance. Locations are in the format + projects/{project}/locations/{zone}. Setting this flag will enable + automated backup for the table. + + --clear-automated-backup-locations + Empty the automated backup locations list if populated. + + At most one of these can be specified: + + --disable-automated-backup + Once set, disables automated backup policy for the table. + + --enable-automated-backup + Once set, enables the default automated backup policy + (retention_period=7d, frequency=1d) for the table. Note: If a table + has automated backup enabled, this flag resets it to the default + policy. At most one of these can be specified: diff --git a/gcloud/certificate-manager/certificates/create b/gcloud/certificate-manager/certificates/create index 55412a9b0..56e90f523 100644 --- a/gcloud/certificate-manager/certificates/create +++ b/gcloud/certificate-manager/certificates/create @@ -179,7 +179,8 @@ GCLOUD WIDE FLAGS API REFERENCE This command uses the certificatemanager/v1 API. The full documentation for - this API can be found at: https://cloud.google.com/certificate-manager + this API can be found at: + https://docs.cloud.google.com/certificate-manager/docs/overview NOTES These variants are also available: diff --git a/gcloud/certificate-manager/certificates/describe b/gcloud/certificate-manager/certificates/describe index 3bac9a66b..890782e2b 100644 --- a/gcloud/certificate-manager/certificates/describe +++ b/gcloud/certificate-manager/certificates/describe @@ -57,7 +57,8 @@ GCLOUD WIDE FLAGS API REFERENCE This command uses the certificatemanager/v1 API. The full documentation for - this API can be found at: https://cloud.google.com/certificate-manager + this API can be found at: + https://docs.cloud.google.com/certificate-manager/docs/overview NOTES These variants are also available: diff --git a/gcloud/certificate-manager/dns-authorizations/create b/gcloud/certificate-manager/dns-authorizations/create index 5c85fcb88..1f5c5f4e7 100644 --- a/gcloud/certificate-manager/dns-authorizations/create +++ b/gcloud/certificate-manager/dns-authorizations/create @@ -84,7 +84,8 @@ GCLOUD WIDE FLAGS API REFERENCE This command uses the certificatemanager/v1 API. The full documentation for - this API can be found at: https://cloud.google.com/certificate-manager + this API can be found at: + https://docs.cloud.google.com/certificate-manager/docs/overview NOTES These variants are also available: diff --git a/gcloud/certificate-manager/dns-authorizations/delete b/gcloud/certificate-manager/dns-authorizations/delete index b5591f78b..a04a1c188 100644 --- a/gcloud/certificate-manager/dns-authorizations/delete +++ b/gcloud/certificate-manager/dns-authorizations/delete @@ -64,7 +64,8 @@ GCLOUD WIDE FLAGS API REFERENCE This command uses the certificatemanager/v1 API. The full documentation for - this API can be found at: https://cloud.google.com/certificate-manager + this API can be found at: + https://docs.cloud.google.com/certificate-manager/docs/overview NOTES These variants are also available: diff --git a/gcloud/certificate-manager/dns-authorizations/describe b/gcloud/certificate-manager/dns-authorizations/describe index c6923d019..971be5e0b 100644 --- a/gcloud/certificate-manager/dns-authorizations/describe +++ b/gcloud/certificate-manager/dns-authorizations/describe @@ -58,7 +58,8 @@ GCLOUD WIDE FLAGS API REFERENCE This command uses the certificatemanager/v1 API. The full documentation for - this API can be found at: https://cloud.google.com/certificate-manager + this API can be found at: + https://docs.cloud.google.com/certificate-manager/docs/overview NOTES These variants are also available: diff --git a/gcloud/certificate-manager/dns-authorizations/list b/gcloud/certificate-manager/dns-authorizations/list index 8d985d9b3..6d13b781c 100644 --- a/gcloud/certificate-manager/dns-authorizations/list +++ b/gcloud/certificate-manager/dns-authorizations/list @@ -77,7 +77,8 @@ GCLOUD WIDE FLAGS API REFERENCE This command uses the certificatemanager/v1 API. The full documentation for - this API can be found at: https://cloud.google.com/certificate-manager + this API can be found at: + https://docs.cloud.google.com/certificate-manager/docs/overview NOTES These variants are also available: diff --git a/gcloud/certificate-manager/dns-authorizations/update b/gcloud/certificate-manager/dns-authorizations/update index 4da16d427..42ceb14cf 100644 --- a/gcloud/certificate-manager/dns-authorizations/update +++ b/gcloud/certificate-manager/dns-authorizations/update @@ -97,7 +97,8 @@ GCLOUD WIDE FLAGS API REFERENCE This command uses the certificatemanager/v1 API. The full documentation for - this API can be found at: https://cloud.google.com/certificate-manager + this API can be found at: + https://docs.cloud.google.com/certificate-manager/docs/overview NOTES These variants are also available: diff --git a/gcloud/certificate-manager/issuance-configs/create b/gcloud/certificate-manager/issuance-configs/create index 5a31fe8a1..3d2c94a30 100644 --- a/gcloud/certificate-manager/issuance-configs/create +++ b/gcloud/certificate-manager/issuance-configs/create @@ -100,7 +100,8 @@ GCLOUD WIDE FLAGS API REFERENCE This command uses the certificatemanager/v1 API. The full documentation for - this API can be found at: https://cloud.google.com/certificate-manager + this API can be found at: + https://docs.cloud.google.com/certificate-manager/docs/overview NOTES These variants are also available: diff --git a/gcloud/certificate-manager/issuance-configs/delete b/gcloud/certificate-manager/issuance-configs/delete index 4ee880a29..8833527df 100644 --- a/gcloud/certificate-manager/issuance-configs/delete +++ b/gcloud/certificate-manager/issuance-configs/delete @@ -64,7 +64,8 @@ GCLOUD WIDE FLAGS API REFERENCE This command uses the certificatemanager/v1 API. The full documentation for - this API can be found at: https://cloud.google.com/certificate-manager + this API can be found at: + https://docs.cloud.google.com/certificate-manager/docs/overview NOTES These variants are also available: diff --git a/gcloud/certificate-manager/issuance-configs/describe b/gcloud/certificate-manager/issuance-configs/describe index b9d1e59d5..d2b64343f 100644 --- a/gcloud/certificate-manager/issuance-configs/describe +++ b/gcloud/certificate-manager/issuance-configs/describe @@ -59,7 +59,8 @@ GCLOUD WIDE FLAGS API REFERENCE This command uses the certificatemanager/v1 API. The full documentation for - this API can be found at: https://cloud.google.com/certificate-manager + this API can be found at: + https://docs.cloud.google.com/certificate-manager/docs/overview NOTES These variants are also available: diff --git a/gcloud/certificate-manager/issuance-configs/list b/gcloud/certificate-manager/issuance-configs/list index 43d76ec54..0c19d4625 100644 --- a/gcloud/certificate-manager/issuance-configs/list +++ b/gcloud/certificate-manager/issuance-configs/list @@ -77,7 +77,8 @@ GCLOUD WIDE FLAGS API REFERENCE This command uses the certificatemanager/v1 API. The full documentation for - this API can be found at: https://cloud.google.com/certificate-manager + this API can be found at: + https://docs.cloud.google.com/certificate-manager/docs/overview NOTES These variants are also available: diff --git a/gcloud/certificate-manager/issuance-configs/update b/gcloud/certificate-manager/issuance-configs/update index fb1e6ef20..71d03d55e 100644 --- a/gcloud/certificate-manager/issuance-configs/update +++ b/gcloud/certificate-manager/issuance-configs/update @@ -100,7 +100,8 @@ GCLOUD WIDE FLAGS API REFERENCE This command uses the certificatemanager/v1 API. The full documentation for - this API can be found at: https://cloud.google.com/certificate-manager + this API can be found at: + https://docs.cloud.google.com/certificate-manager/docs/overview NOTES These variants are also available: diff --git a/gcloud/certificate-manager/operations/describe b/gcloud/certificate-manager/operations/describe index af074a74a..99667c2f9 100644 --- a/gcloud/certificate-manager/operations/describe +++ b/gcloud/certificate-manager/operations/describe @@ -56,7 +56,8 @@ GCLOUD WIDE FLAGS API REFERENCE This command uses the certificatemanager/v1 API. The full documentation for - this API can be found at: https://cloud.google.com/certificate-manager + this API can be found at: + https://docs.cloud.google.com/certificate-manager/docs/overview NOTES These variants are also available: diff --git a/gcloud/certificate-manager/operations/list b/gcloud/certificate-manager/operations/list index d701b603f..2d7d664fe 100644 --- a/gcloud/certificate-manager/operations/list +++ b/gcloud/certificate-manager/operations/list @@ -75,7 +75,8 @@ GCLOUD WIDE FLAGS API REFERENCE This command uses the certificatemanager/v1 API. The full documentation for - this API can be found at: https://cloud.google.com/certificate-manager + this API can be found at: + https://docs.cloud.google.com/certificate-manager/docs/overview NOTES These variants are also available: diff --git a/gcloud/certificate-manager/trust-configs/create b/gcloud/certificate-manager/trust-configs/create index ada436e19..5a71e14d5 100644 --- a/gcloud/certificate-manager/trust-configs/create +++ b/gcloud/certificate-manager/trust-configs/create @@ -109,7 +109,8 @@ GCLOUD WIDE FLAGS API REFERENCE This command uses the certificatemanager/v1 API. The full documentation for - this API can be found at: https://cloud.google.com/certificate-manager + this API can be found at: + https://docs.cloud.google.com/certificate-manager/docs/overview NOTES These variants are also available: diff --git a/gcloud/certificate-manager/trust-configs/delete b/gcloud/certificate-manager/trust-configs/delete index 05684a102..06501c436 100644 --- a/gcloud/certificate-manager/trust-configs/delete +++ b/gcloud/certificate-manager/trust-configs/delete @@ -67,7 +67,8 @@ GCLOUD WIDE FLAGS API REFERENCE This command uses the certificatemanager/v1 API. The full documentation for - this API can be found at: https://cloud.google.com/certificate-manager + this API can be found at: + https://docs.cloud.google.com/certificate-manager/docs/overview NOTES These variants are also available: diff --git a/gcloud/certificate-manager/trust-configs/describe b/gcloud/certificate-manager/trust-configs/describe index 458978be3..2eb9929dd 100644 --- a/gcloud/certificate-manager/trust-configs/describe +++ b/gcloud/certificate-manager/trust-configs/describe @@ -57,7 +57,8 @@ GCLOUD WIDE FLAGS API REFERENCE This command uses the certificatemanager/v1 API. The full documentation for - this API can be found at: https://cloud.google.com/certificate-manager + this API can be found at: + https://docs.cloud.google.com/certificate-manager/docs/overview NOTES These variants are also available: diff --git a/gcloud/certificate-manager/trust-configs/export b/gcloud/certificate-manager/trust-configs/export index db283b10b..fc60a7a42 100644 --- a/gcloud/certificate-manager/trust-configs/export +++ b/gcloud/certificate-manager/trust-configs/export @@ -66,7 +66,8 @@ GCLOUD WIDE FLAGS API REFERENCE This command uses the certificatemanager/v1 API. The full documentation for - this API can be found at: https://cloud.google.com/certificate-manager + this API can be found at: + https://docs.cloud.google.com/certificate-manager/docs/overview NOTES These variants are also available: diff --git a/gcloud/certificate-manager/trust-configs/import b/gcloud/certificate-manager/trust-configs/import index 7da7ced57..26dc8a659 100644 --- a/gcloud/certificate-manager/trust-configs/import +++ b/gcloud/certificate-manager/trust-configs/import @@ -80,7 +80,8 @@ GCLOUD WIDE FLAGS API REFERENCE This command uses the certificatemanager/v1 API. The full documentation for - this API can be found at: https://cloud.google.com/certificate-manager + this API can be found at: + https://docs.cloud.google.com/certificate-manager/docs/overview NOTES These variants are also available: diff --git a/gcloud/certificate-manager/trust-configs/list b/gcloud/certificate-manager/trust-configs/list index b1d64ef79..a3a60ffba 100644 --- a/gcloud/certificate-manager/trust-configs/list +++ b/gcloud/certificate-manager/trust-configs/list @@ -77,7 +77,8 @@ GCLOUD WIDE FLAGS API REFERENCE This command uses the certificatemanager/v1 API. The full documentation for - this API can be found at: https://cloud.google.com/certificate-manager + this API can be found at: + https://docs.cloud.google.com/certificate-manager/docs/overview NOTES These variants are also available: diff --git a/gcloud/certificate-manager/trust-configs/update b/gcloud/certificate-manager/trust-configs/update index 27b670cb3..465b27d86 100644 --- a/gcloud/certificate-manager/trust-configs/update +++ b/gcloud/certificate-manager/trust-configs/update @@ -148,7 +148,8 @@ GCLOUD WIDE FLAGS API REFERENCE This command uses the certificatemanager/v1 API. The full documentation for - this API can be found at: https://cloud.google.com/certificate-manager + this API can be found at: + https://docs.cloud.google.com/certificate-manager/docs/overview NOTES These variants are also available: diff --git a/gcloud/compute/addresses/help b/gcloud/compute/addresses/help index e897d06c3..560a6601c 100644 --- a/gcloud/compute/addresses/help +++ b/gcloud/compute/addresses/help @@ -36,6 +36,9 @@ COMMANDS move Move an address to another project. + update + Update an address's labels. + NOTES These variants are also available: diff --git a/gcloud/compute/addresses/update b/gcloud/compute/addresses/update new file mode 100644 index 000000000..963df5490 --- /dev/null +++ b/gcloud/compute/addresses/update @@ -0,0 +1,87 @@ +NAME + gcloud compute addresses update - update an address's labels + +SYNOPSIS + gcloud compute addresses update NAME [--update-labels=[KEY=VALUE,...]] + [--clear-labels | --remove-labels=[KEY,...]] + [--global | --region=REGION] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + gcloud compute addresses update updates labels for a Compute Engine + address. + +EXAMPLES + To add/update labels 'k0' and 'k1' and remove labels with key 'k3' for + address 'example-address', run: + + $ gcloud compute addresses update example-address \ + --region=us-central1 --update-labels=k0=value1,k1=value2 \ + --remove-labels=k3 + + Labels can be used to identify the address and to filter them as in: + + $ gcloud compute addresses list --filter='labels.k1:value2' + + To list existing labels for address 'example-address', run: + + $ gcloud compute addresses describe example-address \ + --format="default(labels)" + +POSITIONAL ARGUMENTS + NAME + Name of the address to operate on. + +FLAGS + --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 compute addresses update --clear-labels + + To remove all existing labels and create two new labels, foo and baz: + + $ gcloud compute addresses 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. + + At most one of these can be specified: + + --global + If set, the address is global. + + --region=REGION + Region of the address to operate on. Overrides the default + compute/region property value for this command invocation. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + These variants are also available: + + $ gcloud alpha compute addresses update + + $ gcloud beta compute addresses update + diff --git a/gcloud/compute/backend-buckets/add-iam-policy-binding b/gcloud/compute/backend-buckets/add-iam-policy-binding index 81e985d91..34a4402ab 100644 --- a/gcloud/compute/backend-buckets/add-iam-policy-binding +++ b/gcloud/compute/backend-buckets/add-iam-policy-binding @@ -4,7 +4,8 @@ NAME SYNOPSIS gcloud compute backend-buckets add-iam-policy-binding BACKEND_BUCKET - --member=PRINCIPAL --role=ROLE [GCLOUD_WIDE_FLAG ...] + --member=PRINCIPAL --role=ROLE [--global | --region=REGION] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION Add an IAM policy binding to a Compute Engine backend bucket. @@ -12,34 +13,35 @@ DESCRIPTION EXAMPLES To add an IAM policy binding for the role of 'compute.loadBalancerServiceUser' for the user 'test-user@gmail.com' with - backend bucket 'my-backend-bucket' run: + backend bucket 'my-backend-bucket' and region 'REGION', run: $ gcloud compute backend-buckets add-iam-policy-binding \ - my-backend-bucket --member='user:test-user@gmail.com' \ - --role='roles/compute.loadBalancerServiceUser' + my-backend-bucket --region=REGION \ + --member='user:test-user@gmail.com' \ + --role='roles/compute.loadBalancerServiceUser' + + To add an IAM policy binding for the role of + 'compute.loadBalancerServiceUser' for the user 'test-user@gmail.com' with + global backend bucket 'my-backend-bucket', run either of the following: + + $ gcloud compute backend-buckets add-iam-policy-binding \ + my-backend-bucket --global --member='user:test-user@gmail.com' \ + --role='roles/compute.loadBalancerServiceUser' + + $ gcloud compute backend-buckets add-iam-policy-binding \ + my-backend-bucket --member='user:test-user@gmail.com' \ + --role='roles/compute.loadBalancerServiceUser' See https://cloud.google.com/iam/docs/managing-policies for details of policy role and member types. POSITIONAL ARGUMENTS - Backend bucket resource - The backend bucket for which to add the IAM - policy to. This represents a Cloud resource. (NOTE) Some attributes are - not given arguments in this group but can be set in other ways. + BACKEND_BUCKET + ID of the backend bucket or fully qualified identifier for the backend + bucket. - To set the project attribute: - ◆ provide the argument backend_bucket 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. - - BACKEND_BUCKET - ID of the backend bucket or fully qualified identifier for the - backend bucket. - - To set the backend_bucket attribute: - ▸ provide the argument backend_bucket on the command line. + To set the backend_bucket attribute: + + provide the argument backend_bucket on the command line. REQUIRED FLAGS --member=PRINCIPAL @@ -62,6 +64,16 @@ REQUIRED FLAGS for a custom role, such as organizations/{ORGANIZATION_ID}/roles/logging.viewer. +OPTIONAL FLAGS + At most one of these can be specified: + + --global + If set, the backend bucket is global. + + --region=REGION + Region of the backend bucket to operate on. Overrides the default + compute/region property value for this command invocation. + GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, @@ -71,8 +83,8 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. API REFERENCE - This command uses the compute/v1 API. The full documentation for this API - can be found at: https://cloud.google.com/compute/ + This command uses the compute API. The full documentation for this API can + be found at: https://cloud.google.com/compute/ NOTES These variants are also available: diff --git a/gcloud/compute/backend-buckets/create b/gcloud/compute/backend-buckets/create index 6468de944..e8abe789f 100644 --- a/gcloud/compute/backend-buckets/create +++ b/gcloud/compute/backend-buckets/create @@ -17,7 +17,7 @@ SYNOPSIS [--[no-]request-coalescing] [--resource-manager-tags=[KEY=VALUE,...]] [--serve-while-stale=SERVE_WHILE_STALE] [--signed-url-cache-max-age=SIGNED_URL_CACHE_MAX_AGE] - [GCLOUD_WIDE_FLAG ...] + [--global | --region=REGION] [GCLOUD_WIDE_FLAG ...] DESCRIPTION gcloud compute backend-buckets create is used to create backend buckets. @@ -163,7 +163,7 @@ OPTIONAL FLAGS The load balancing scheme of the backend bucket. If left blank, the backend bucket will be compatible with Global External Application Load Balancer or Classic Application Load Balancer. LOAD_BALANCING_SCHEME - must be (only one value is supported): INTERNAL_MANAGED. + must be one of: INTERNAL_MANAGED, EXTERNAL_MANAGED. --max-ttl=MAX_TTL Specifies the maximum allowed TTL for cached content served by this @@ -294,6 +294,15 @@ OPTIONAL FLAGS This flag only affects signed URL requests. + At most one of these can be specified: + + --global + If set, the backend bucket is global. + + --region=REGION + Region of the backend bucket to create. Overrides the default + compute/region property value for this command invocation. + GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, diff --git a/gcloud/compute/backend-buckets/delete b/gcloud/compute/backend-buckets/delete index 2768d79e4..aa6d77908 100644 --- a/gcloud/compute/backend-buckets/delete +++ b/gcloud/compute/backend-buckets/delete @@ -3,7 +3,8 @@ NAME SYNOPSIS gcloud compute backend-buckets delete BACKEND_BUCKET_NAME - [BACKEND_BUCKET_NAME ...] [GCLOUD_WIDE_FLAG ...] + [BACKEND_BUCKET_NAME ...] [--global | --region=REGION] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION gcloud compute backend-buckets delete deletes one or more backend buckets. @@ -12,6 +13,16 @@ POSITIONAL ARGUMENTS BACKEND_BUCKET_NAME [BACKEND_BUCKET_NAME ...] Names of the backend buckets to delete. +FLAGS + At most one of these can be specified: + + --global + If set, the backend buckets are global. + + --region=REGION + Region of the backend buckets to delete. Overrides the default + compute/region property value for this command invocation. + GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, diff --git a/gcloud/compute/backend-buckets/describe b/gcloud/compute/backend-buckets/describe index 4b1325a48..3d3872b53 100644 --- a/gcloud/compute/backend-buckets/describe +++ b/gcloud/compute/backend-buckets/describe @@ -3,7 +3,7 @@ NAME SYNOPSIS gcloud compute backend-buckets describe BACKEND_BUCKET_NAME - [GCLOUD_WIDE_FLAG ...] + [--global | --region=REGION] [GCLOUD_WIDE_FLAG ...] DESCRIPTION gcloud compute backend-buckets describe displays all data associated with a @@ -13,6 +13,16 @@ POSITIONAL ARGUMENTS BACKEND_BUCKET_NAME Name of the backend bucket to describe. +FLAGS + At most one of these can be specified: + + --global + If set, the backend bucket is global. + + --region=REGION + Region of the backend bucket to describe. Overrides the default + compute/region property value for this command invocation. + GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, diff --git a/gcloud/compute/backend-buckets/get-iam-policy b/gcloud/compute/backend-buckets/get-iam-policy index 2ee97a919..231967981 100644 --- a/gcloud/compute/backend-buckets/get-iam-policy +++ b/gcloud/compute/backend-buckets/get-iam-policy @@ -4,8 +4,8 @@ NAME SYNOPSIS gcloud compute backend-buckets get-iam-policy BACKEND_BUCKET - [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] - [--sort-by=[FIELD,...]] [GCLOUD_WIDE_FLAG ...] + [--global | --region=REGION] [--filter=EXPRESSION] [--limit=LIMIT] + [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION gcloud compute backend-buckets get-iam-policy displays the IAM policy @@ -16,29 +16,36 @@ DESCRIPTION set-iam-policy for additional details. EXAMPLES - To print the IAM policy for a given backend bucket, run: + To print the IAM policy for a given regional backend bucket, run: + + $ gcloud compute backend-buckets get-iam-policy my-backend-bucket \ + --region=REGION + + To print the IAM policy for a given global backend bucket, run either of + the following: + + $ gcloud compute backend-buckets get-iam-policy my-backend-bucket \ + --global $ gcloud compute backend-buckets get-iam-policy my-backend-bucket POSITIONAL ARGUMENTS - Backend bucket resource - The network to display the IAM policy for. This - represents a Cloud resource. (NOTE) Some attributes are not given - arguments in this group but can be set in other ways. + BACKEND_BUCKET + ID of the backend bucket or fully qualified identifier for the backend + bucket. - To set the project attribute: - ◆ provide the argument backend_bucket 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 backend_bucket attribute: + + provide the argument backend_bucket on the command line. - This must be specified. +FLAGS + At most one of these can be specified: - BACKEND_BUCKET - ID of the backend bucket or fully qualified identifier for the - backend bucket. + --global + If set, the backend bucket is global. - To set the backend_bucket attribute: - ▸ provide the argument backend_bucket on the command line. + --region=REGION + Region of the backend bucket to operate on. Overrides the default + compute/region property value for this command invocation. LIST COMMAND FLAGS --filter=EXPRESSION @@ -75,8 +82,8 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. API REFERENCE - This command uses the compute/v1 API. The full documentation for this API - can be found at: https://cloud.google.com/compute/ + This command uses the compute API. The full documentation for this API can + be found at: https://cloud.google.com/compute/ NOTES These variants are also available: diff --git a/gcloud/compute/backend-buckets/list b/gcloud/compute/backend-buckets/list index c90e898cf..c61bc2a74 100644 --- a/gcloud/compute/backend-buckets/list +++ b/gcloud/compute/backend-buckets/list @@ -4,8 +4,9 @@ NAME SYNOPSIS gcloud compute backend-buckets list [NAME ...] [--regexp=REGEXP, -r REGEXP] - [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] - [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + [--global | --regions=[REGION,...]] [--filter=EXPRESSION] + [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION gcloud compute backend-buckets list displays all Google Compute Engine @@ -36,6 +37,15 @@ FLAGS Flag --regexp is deprecated. Use --filter="name~'REGEXP'" instead. + At most one of these can be specified: + + --global + If provided, only global resources are shown. + + --regions=[REGION,...] + If provided, only regional resources are shown. If arguments are + provided, only resources from the given regions are shown. + LIST COMMAND FLAGS --filter=EXPRESSION Apply a Boolean filter EXPRESSION to each resource item to be listed. diff --git a/gcloud/compute/backend-buckets/remove-iam-policy-binding b/gcloud/compute/backend-buckets/remove-iam-policy-binding index bf8101e64..270519703 100644 --- a/gcloud/compute/backend-buckets/remove-iam-policy-binding +++ b/gcloud/compute/backend-buckets/remove-iam-policy-binding @@ -4,7 +4,8 @@ NAME SYNOPSIS gcloud compute backend-buckets remove-iam-policy-binding BACKEND_BUCKET - --member=PRINCIPAL --role=ROLE [GCLOUD_WIDE_FLAG ...] + --member=PRINCIPAL --role=ROLE [--global | --region=REGION] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION Remove an IAM policy binding from a Compute Engine backend bucket. @@ -12,34 +13,35 @@ DESCRIPTION EXAMPLES To remove an IAM policy binding for the role of 'roles/compute.loadBalancerServiceUser' for the user 'test-user@gmail.com' - with backend bucket 'my-backend-bucket' run: + with backend bucket 'my-backend-bucket' and region 'REGION', run: $ gcloud compute backend-buckets remove-iam-policy-binding \ - my-backend-bucket --member='user:test-user@gmail.com' \ - --role='roles/compute.loadBalancerServiceUser' + my-backend-bucket --region=REGION \ + --member='user:test-user@gmail.com' \ + --role='roles/compute.loadBalancerServiceUser' + + To remove an IAM policy binding for the role of + 'roles/compute.loadBalancerServiceUser' for the user 'test-user@gmail.com' + with globalbackend bucket 'my-backend-bucket', run either of the following: + + $ gcloud compute backend-buckets remove-iam-policy-binding \ + my-backend-bucket --global --member='user:test-user@gmail.com' \ + --role='roles/compute.loadBalancerServiceUser' + + $ gcloud compute backend-buckets remove-iam-policy-binding \ + my-backend-bucket --member='user:test-user@gmail.com' \ + --role='roles/compute.loadBalancerServiceUser' See https://cloud.google.com/iam/docs/managing-policies for details of policy role and member types. POSITIONAL ARGUMENTS - Backend bucket resource - The backend bucket for which to remove the IAM - policy from. This represents a Cloud resource. (NOTE) Some attributes are - not given arguments in this group but can be set in other ways. + BACKEND_BUCKET + ID of the backend bucket or fully qualified identifier for the backend + bucket. - To set the project attribute: - ◆ provide the argument backend_bucket 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. - - BACKEND_BUCKET - ID of the backend bucket or fully qualified identifier for the - backend bucket. - - To set the backend_bucket attribute: - ▸ provide the argument backend_bucket on the command line. + To set the backend_bucket attribute: + + provide the argument backend_bucket on the command line. REQUIRED FLAGS --member=PRINCIPAL @@ -63,6 +65,16 @@ REQUIRED FLAGS --role=ROLE The role to remove the principal from. +OPTIONAL FLAGS + At most one of these can be specified: + + --global + If set, the backend bucket is global. + + --region=REGION + Region of the backend bucket to operate on. Overrides the default + compute/region property value for this command invocation. + GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, @@ -72,8 +84,8 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. API REFERENCE - This command uses the compute/v1 API. The full documentation for this API - can be found at: https://cloud.google.com/compute/ + This command uses the compute API. The full documentation for this API can + be found at: https://cloud.google.com/compute/ NOTES These variants are also available: diff --git a/gcloud/compute/backend-buckets/set-iam-policy b/gcloud/compute/backend-buckets/set-iam-policy index 2d8004ed2..4f6675c35 100644 --- a/gcloud/compute/backend-buckets/set-iam-policy +++ b/gcloud/compute/backend-buckets/set-iam-policy @@ -4,16 +4,24 @@ NAME SYNOPSIS gcloud compute backend-buckets set-iam-policy BACKEND_BUCKET POLICY_FILE - [GCLOUD_WIDE_FLAG ...] + [--global | --region=REGION] [GCLOUD_WIDE_FLAG ...] DESCRIPTION Sets the IAM policy for the given backend bucket as defined in a JSON or YAML file. EXAMPLES - The following command reads an IAM policy defined in a JSON file called - 'policy.json' and sets it for the backend bucket called - 'my-backend-bucket': + The following command will read an IAM policy defined in a JSON file + 'policy.json' and set it for the regional backend bucket my-backend-bucket: + + $ gcloud compute backend-buckets set-iam-policy my-backend-bucket \ + policy.json --region=REGION + + The following commands will read an IAM policy defined in a JSON file + 'policy.json' and set it for the global backend bucket my-backend-bucket: + + $ gcloud compute backend-buckets set-iam-policy my-backend-bucket \ + policy.json --global $ gcloud compute backend-buckets set-iam-policy my-backend-bucket \ policy.json @@ -22,24 +30,12 @@ EXAMPLES policy file format and contents. POSITIONAL ARGUMENTS - Backend bucket resource - The backend bucket to set the IAM policy for. - This represents a Cloud resource. (NOTE) Some attributes are not given - arguments in this group but can be set in other ways. + BACKEND_BUCKET + ID of the backend bucket or fully qualified identifier for the backend + bucket. - To set the project attribute: - ◆ provide the argument backend_bucket 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. - - BACKEND_BUCKET - ID of the backend bucket or fully qualified identifier for the - backend bucket. - - To set the backend_bucket attribute: - ▸ provide the argument backend_bucket on the command line. + To set the backend_bucket attribute: + + provide the argument backend_bucket on the command line. POLICY_FILE Path to a local JSON or YAML formatted file containing a valid policy. @@ -48,6 +44,16 @@ POSITIONAL ARGUMENTS JSON or YAML file conforming to the structure of a Policy (https://cloud.google.com/iam/reference/rest/v1/Policy). +FLAGS + At most one of these can be specified: + + --global + If set, the backend bucket is global. + + --region=REGION + Region of the backend bucket to setIamPolicy. Overrides the default + compute/region property value for this command invocation. + GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, @@ -57,8 +63,8 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. API REFERENCE - This command uses the compute/v1 API. The full documentation for this API - can be found at: https://cloud.google.com/compute/ + This command uses the compute API. The full documentation for this API can + be found at: https://cloud.google.com/compute/ NOTES These variants are also available: diff --git a/gcloud/compute/backend-buckets/update b/gcloud/compute/backend-buckets/update index b4fadcfed..e5ae9057e 100644 --- a/gcloud/compute/backend-buckets/update +++ b/gcloud/compute/backend-buckets/update @@ -16,7 +16,7 @@ SYNOPSIS [--custom-response-header=CUSTOM_RESPONSE_HEADER | --no-custom-response-headers] [--default-ttl=DEFAULT_TTL | --no-default-ttl] - [--max-ttl=MAX_TTL | --no-max-ttl] + [--global | --region=REGION] [--max-ttl=MAX_TTL | --no-max-ttl] [--[no-]negative-caching | --no-negative-caching-policies | --negative-caching-policy=[[CODE=TTL],...]] [--serve-while-stale=SERVE_WHILE_STALE | --no-serve-while-stale] @@ -222,6 +222,15 @@ FLAGS --no-default-ttl Clears default TTL value. + At most one of these can be specified: + + --global + If set, the backend bucket is global. + + --region=REGION + Region of the backend bucket to update. Overrides the default + compute/region property value for this command invocation. + At most one of these can be specified: --max-ttl=MAX_TTL diff --git a/gcloud/compute/backend-services/add-backend b/gcloud/compute/backend-services/add-backend index b19bdb003..cdcf65b20 100644 --- a/gcloud/compute/backend-services/add-backend +++ b/gcloud/compute/backend-services/add-backend @@ -14,14 +14,15 @@ SYNOPSIS [--balancing-mode=BALANCING_MODE] [--capacity-scaler=CAPACITY_SCALER] [--description=DESCRIPTION] [--failover] [--max-utilization=MAX_UTILIZATION] [--preference=PREFERENCE] + [--traffic-duration=TRAFFIC_DURATION] [--custom-metrics=[CUSTOM_METRICS,...] | --custom-metrics-file=[CUSTOM_METRICS,...]] [--global | --region=REGION] [--max-connections=MAX_CONNECTIONS | --max-connections-per-endpoint=MAX_CONNECTIONS_PER_ENDPOINT | --max-connections-per-instance=MAX_CONNECTIONS_PER_INSTANCE - | --max-rate=MAX_RATE | --max-rate-per-endpoint=MAX_RATE_PER_ENDPOINT - | --max-rate-per-instance=MAX_RATE_PER_INSTANCE] + | --max-in-flight-requests=MAX_IN_FLIGHT_REQUESTS + | --max-in-flight-requests-per-endpoint=MAX_IN_FLIGHT_REQUESTS_PER_ENDPOINT | --max-in-flight-requests-per-instance=MAX_IN_FLIGHT_REQUESTS_PER_INSTANCE | --max-rate=MAX_RATE | --max-rate-per-endpoint=MAX_RATE_PER_ENDPOINT | --max-rate-per-instance=MAX_RATE_PER_INSTANCE] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -187,6 +188,19 @@ OPTIONAL FLAGS CUSTOM_METRICS Spreads load based on custom defined and reported metrics. + IN_FLIGHT + Available if the backend service's load balancing scheme is + INTERNAL_MANAGED, INTERNAL_SELF_MANAGED, or EXTERNAL_MANAGED. + Available if the backend service's protocol is one of HTTP, HTTPS, + or HTTP/2. + + Spreads load based on how many in-flight requests the backend can + handle. + + You must specify exactly one of these additional parameters: + --max-in-flight-requests, --max-in-flight-requests-per-instance, or + --max-in-flight-requests-per-endpoint, and --traffic-duration=LONG. + RATE Available if the backend service's load balancing scheme is INTERNAL_MANAGED, INTERNAL_SELF_MANAGED, or EXTERNAL. Available if @@ -255,6 +269,20 @@ OPTIONAL FLAGS Backends with this preference setting are used up to their capacity limits first, while optimizing overall network latency. + --traffic-duration=TRAFFIC_DURATION + The expected traffic duration for this service. TRAFFIC_DURATION must + be one of: + + LONG + Most of the requests are expected to take more than multiple + seconds to finish. + + SHORT + Most requests are expected to finish with a sub-second latency. + + TRAFFIC_DURATION_UNSPECIFIED + Default value. Defaults to SHORT. + At most one of these can be specified: --custom-metrics=[CUSTOM_METRICS,...] @@ -371,6 +399,29 @@ OPTIONAL FLAGS number of instances in the instance group, and then dividing by the number of healthy instances. + --max-in-flight-requests=MAX_IN_FLIGHT_REQUESTS + Maximum number of in-flight requests that the backend can handle. + + This cannot be used when the endpoint type of an attached network + endpoint group is INTERNET_IP_PORT, INTERNET_FQDN_PORT, or + SERVERLESS. + + --max-in-flight-requests-per-endpoint=MAX_IN_FLIGHT_REQUESTS_PER_ENDPOINT + Only valid for network endpoint group backends. Defines the maximum + number of in-flight requests per endpoint. + + This cannot be used when the endpoint type of an attached network + endpoint group is INTERNET_IP_PORT, INTERNET_FQDN_PORT, or + SERVERLESS. + + --max-in-flight-requests-per-instance=MAX_IN_FLIGHT_REQUESTS_PER_INSTANCE + Only valid for instance group backends. Defines the maximum number of + in-flight requests per instance. + + This cannot be used when the endpoint type of an attached network + endpoint group is INTERNET_IP_PORT, INTERNET_FQDN_PORT, or + SERVERLESS. + --max-rate=MAX_RATE Maximum number of HTTP requests per second (RPS) that the backend can handle. Valid for network endpoint group and instance group backends diff --git a/gcloud/compute/backend-services/update b/gcloud/compute/backend-services/update index d3e60483d..634ca306a 100644 --- a/gcloud/compute/backend-services/update +++ b/gcloud/compute/backend-services/update @@ -310,7 +310,16 @@ FLAGS IPV6_ONLY. --load-balancing-scheme=LOAD_BALANCING_SCHEME - Only for the Global external Application Load Balancer migration. + Specifies the load balancer type. Choose EXTERNAL for the classic + Application Load Balancers. Choose EXTERNAL_MANAGED for the Envoy-based + global external Application Load Balancers For more information, refer + to this guide: + https://cloud.google.com/load-balancing/docs/choosing-load-balancer. + + This field should only be used for migration from the Classic + Application Load Balancer to the global external Application Load + Balancer. The --load-balancing-scheme is immutable for all other use + cases. The value of this field must be EXTERNAL or EXTERNAL_MANAGED. diff --git a/gcloud/compute/backend-services/update-backend b/gcloud/compute/backend-services/update-backend index 327ba4c2e..35834ae52 100644 --- a/gcloud/compute/backend-services/update-backend +++ b/gcloud/compute/backend-services/update-backend @@ -12,14 +12,15 @@ SYNOPSIS [--balancing-mode=BALANCING_MODE] [--capacity-scaler=CAPACITY_SCALER] [--description=DESCRIPTION] [--failover] [--max-utilization=MAX_UTILIZATION] [--preference=PREFERENCE] + [--traffic-duration=TRAFFIC_DURATION] [--clear-custom-metrics | --custom-metrics=[CUSTOM_METRICS,...] | --custom-metrics-file=[CUSTOM_METRICS,...]] [--global | --region=REGION] [--max-connections=MAX_CONNECTIONS | --max-connections-per-endpoint=MAX_CONNECTIONS_PER_ENDPOINT | --max-connections-per-instance=MAX_CONNECTIONS_PER_INSTANCE - | --max-rate=MAX_RATE | --max-rate-per-endpoint=MAX_RATE_PER_ENDPOINT - | --max-rate-per-instance=MAX_RATE_PER_INSTANCE] + | --max-in-flight-requests=MAX_IN_FLIGHT_REQUESTS + | --max-in-flight-requests-per-endpoint=MAX_IN_FLIGHT_REQUESTS_PER_ENDPOINT | --max-in-flight-requests-per-instance=MAX_IN_FLIGHT_REQUESTS_PER_INSTANCE | --max-rate=MAX_RATE | --max-rate-per-endpoint=MAX_RATE_PER_ENDPOINT | --max-rate-per-instance=MAX_RATE_PER_INSTANCE] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -152,6 +153,19 @@ OPTIONAL FLAGS CUSTOM_METRICS Spreads load based on custom defined and reported metrics. + IN_FLIGHT + Available if the backend service's load balancing scheme is + INTERNAL_MANAGED, INTERNAL_SELF_MANAGED, or EXTERNAL_MANAGED. + Available if the backend service's protocol is one of HTTP, HTTPS, + or HTTP/2. + + Spreads load based on how many in-flight requests the backend can + handle. + + You must specify exactly one of these additional parameters: + --max-in-flight-requests, --max-in-flight-requests-per-instance, or + --max-in-flight-requests-per-endpoint, and --traffic-duration=LONG. + RATE Available if the backend service's load balancing scheme is INTERNAL_MANAGED, INTERNAL_SELF_MANAGED, or EXTERNAL. Available if @@ -217,6 +231,20 @@ OPTIONAL FLAGS Backends with this preference setting are used up to their capacity limits first, while optimizing overall network latency. + --traffic-duration=TRAFFIC_DURATION + The expected traffic duration for this service. TRAFFIC_DURATION must + be one of: + + LONG + Most of the requests are expected to take more than multiple + seconds to finish. + + SHORT + Most requests are expected to finish with a sub-second latency. + + TRAFFIC_DURATION_UNSPECIFIED + Default value. Defaults to SHORT. + At most one of these can be specified: --clear-custom-metrics @@ -328,6 +356,17 @@ OPTIONAL FLAGS number of instances in the instance group, and then dividing by the number of healthy instances. + --max-in-flight-requests=MAX_IN_FLIGHT_REQUESTS + Maximum number of in-flight requests that the backend can handle. + + --max-in-flight-requests-per-endpoint=MAX_IN_FLIGHT_REQUESTS_PER_ENDPOINT + Only valid for network endpoint group backends. Defines the maximum + number of in-flight requests per endpoint. + + --max-in-flight-requests-per-instance=MAX_IN_FLIGHT_REQUESTS_PER_INSTANCE + Only valid for instance group backends. Defines the maximum number of + in-flight requests per instance. + --max-rate=MAX_RATE Maximum number of HTTP requests per second (RPS) that the backend can handle. Valid for network endpoint group and instance group backends diff --git a/gcloud/compute/commitments/create b/gcloud/compute/commitments/create index 4b40ffa89..404d58e97 100644 --- a/gcloud/compute/commitments/create +++ b/gcloud/compute/commitments/create @@ -110,8 +110,8 @@ OPTIONAL FLAGS general-purpose-c4d, general-purpose-e2, general-purpose-n2, general-purpose-n2d, general-purpose-n4, general-purpose-n4a, general-purpose-n4d, general-purpose-t2d, graphics-optimized, - graphics-optimized-g4, graphics-optimized-g4-vgpu, memory-optimized, - memory-optimized-m3, memory-optimized-m4, memory-optimized-m4-6tb, + graphics-optimized-g4, memory-optimized, memory-optimized-m3, + memory-optimized-m4, memory-optimized-m4-6tb, memory-optimized-x4-1440-24t, memory-optimized-x4-16tb, memory-optimized-x4-1920-32t, memory-optimized-x4-24tb, memory-optimized-x4-32tb, memory-optimized-x4-480-6t, diff --git a/gcloud/compute/composite-health-checks/create b/gcloud/compute/composite-health-checks/create new file mode 100644 index 000000000..3a07824ca --- /dev/null +++ b/gcloud/compute/composite-health-checks/create @@ -0,0 +1,95 @@ +NAME + gcloud compute composite-health-checks create - create a composite health + check + +SYNOPSIS + gcloud compute composite-health-checks create + (COMPOSITE_HEALTH_CHECK : --region=REGION) + --health-destination=HEALTH_DESTINATION + --health-sources=HEALTH_SOURCES,[...] [--async] + [--description=DESCRIPTION] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Create a composite health check. + +EXAMPLES + The following command creates a new composite health check: + + $ gcloud compute composite-health-checks create \ + --region= \ + --health-sources=my-hs --health-destination=my-fr + +POSITIONAL ARGUMENTS + Composite health check resource - The name of the composite health check + you want to create. The arguments in this group can be used to specify the + attributes of this resource. (NOTE) Some attributes are not given + arguments in this group but can be set in other ways. + + To set the project attribute: + ◆ provide the argument composite_health_check on the command line with + a fully specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + COMPOSITE_HEALTH_CHECK + ID of the composite health check or fully qualified identifier for + the composite health check. + + To set the composite_health_check attribute: + ▸ provide the argument composite_health_check on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --region=REGION + The name of the Google Compute Engine region. + + To set the region attribute: + ▸ provide the argument composite_health_check on the command line + with a fully specified name; + ▸ provide the argument --region on the command line; + ▸ set the property compute/region. + +REQUIRED FLAGS + --health-destination=HEALTH_DESTINATION + URL to the destination resource. Must be set. Must be a ForwardingRule. + The ForwardingRule must have load balancing scheme INTERNAL or + INTERNAL_MANAGED and must be regional and in the same region as the + CompositeHealthCheck (cross-region deployment for INTERNAL_MANAGED is + not supported). Can be mutated. + + --health-sources=HEALTH_SOURCES,[...] + URLs to the HealthSource resources whose results are AND'ed. I.e. the + aggregated result is HEALTHY only if all sources are HEALTHY. Must have + at least 1. Must not have more than 10. Must be regional and in the + same region as the CompositeHealthCheck. Can be mutated. + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --description=DESCRIPTION + A textual description of this resource. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the compute/v1 API. The full documentation for this API + can be found at: https://cloud.google.com/compute/ + +NOTES + These variants are also available: + + $ gcloud alpha compute composite-health-checks create + + $ gcloud beta compute composite-health-checks create + diff --git a/gcloud/compute/composite-health-checks/delete b/gcloud/compute/composite-health-checks/delete new file mode 100644 index 000000000..8eb2801e1 --- /dev/null +++ b/gcloud/compute/composite-health-checks/delete @@ -0,0 +1,75 @@ +NAME + gcloud compute composite-health-checks delete - delete a composite health + check + +SYNOPSIS + gcloud compute composite-health-checks delete + (COMPOSITE_HEALTH_CHECK : --region=REGION) [--async] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Delete a composite health check. + +EXAMPLES + To delete a single composite health check, run the following command: + + $ gcloud compute composite-health-checks delete \ + --region= + +POSITIONAL ARGUMENTS + Composite health check resource - Name of the composite health check you + want to delete. The arguments in this group can be used to specify the + attributes of this resource. (NOTE) Some attributes are not given + arguments in this group but can be set in other ways. + + To set the project attribute: + ◆ provide the argument composite_health_check on the command line with + a fully specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + COMPOSITE_HEALTH_CHECK + ID of the composite health check or fully qualified identifier for + the composite health check. + + To set the composite_health_check attribute: + ▸ provide the argument composite_health_check on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --region=REGION + The name of the Google Compute Engine region. + + To set the region attribute: + ▸ provide the argument composite_health_check on the command line + with a fully specified name; + ▸ provide the argument --region on the command line; + ▸ set the property compute/region. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the compute/v1 API. The full documentation for this API + can be found at: https://cloud.google.com/compute/ + +NOTES + These variants are also available: + + $ gcloud alpha compute composite-health-checks delete + + $ gcloud beta compute composite-health-checks delete + diff --git a/gcloud/compute/composite-health-checks/describe b/gcloud/compute/composite-health-checks/describe new file mode 100644 index 000000000..d5f00c9c8 --- /dev/null +++ b/gcloud/compute/composite-health-checks/describe @@ -0,0 +1,70 @@ +NAME + gcloud compute composite-health-checks describe - describe a composite + health check + +SYNOPSIS + gcloud compute composite-health-checks describe + (COMPOSITE_HEALTH_CHECK : --region=REGION) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Describe a composite health check. + +EXAMPLES + To retrieve a single composite health check and print its properties, run + the following command: + + $ gcloud compute composite-health-checks describe \ + --region= + +POSITIONAL ARGUMENTS + Composite health check resource - Name of the composite health check you + want to inspect. The arguments in this group can be used to specify the + attributes of this resource. (NOTE) Some attributes are not given + arguments in this group but can be set in other ways. + + To set the project attribute: + ◆ provide the argument composite_health_check on the command line with + a fully specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + COMPOSITE_HEALTH_CHECK + ID of the composite health check or fully qualified identifier for + the composite health check. + + To set the composite_health_check attribute: + ▸ provide the argument composite_health_check on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --region=REGION + The name of the Google Compute Engine region. + + To set the region attribute: + ▸ provide the argument composite_health_check on the command line + with a fully specified name; + ▸ provide the argument --region on the command line; + ▸ set the property compute/region. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the compute/v1 API. The full documentation for this API + can be found at: https://cloud.google.com/compute/ + +NOTES + These variants are also available: + + $ gcloud alpha compute composite-health-checks describe + + $ gcloud beta compute composite-health-checks describe + diff --git a/gcloud/compute/composite-health-checks/get-health b/gcloud/compute/composite-health-checks/get-health new file mode 100644 index 000000000..444934a6c --- /dev/null +++ b/gcloud/compute/composite-health-checks/get-health @@ -0,0 +1,41 @@ +NAME + gcloud compute composite-health-checks get-health - get health status of a + composite health check + +SYNOPSIS + gcloud compute composite-health-checks get-health COMPOSITE_HEALTH_CHECK + [--region=REGION] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Get health status of a composite health check. + +EXAMPLES + To get health of a composite health check, run: + + $ gcloud compute composite-health-checks get-health \ + COMPOSITE_HEALTH_CHECK --region=REGION + +POSITIONAL ARGUMENTS + COMPOSITE_HEALTH_CHECK + Name of the composite health check to operate on. + +FLAGS + --region=REGION + Region of the composite health check to operate on. Overrides the + default compute/region property value for this command invocation. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + These variants are also available: + + $ gcloud alpha compute composite-health-checks get-health + + $ gcloud beta compute composite-health-checks get-health + diff --git a/gcloud/compute/composite-health-checks/help b/gcloud/compute/composite-health-checks/help new file mode 100644 index 000000000..2d63bafec --- /dev/null +++ b/gcloud/compute/composite-health-checks/help @@ -0,0 +1,42 @@ +NAME + gcloud compute composite-health-checks - manage composite health checks + +SYNOPSIS + gcloud compute composite-health-checks COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Manage composite health checks. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + create + Create a composite health check. + + delete + Delete a composite health check. + + describe + Describe a composite health check. + + get-health + Get health status of a composite health check. + + list + List composite health checks. + + update + Update a composite health check. + +NOTES + These variants are also available: + + $ gcloud alpha compute composite-health-checks + + $ gcloud beta compute composite-health-checks + diff --git a/gcloud/compute/composite-health-checks/list b/gcloud/compute/composite-health-checks/list new file mode 100644 index 000000000..496de1fe3 --- /dev/null +++ b/gcloud/compute/composite-health-checks/list @@ -0,0 +1,78 @@ +NAME + gcloud compute composite-health-checks list - list composite health checks + +SYNOPSIS + gcloud compute composite-health-checks list [NAME ...] + [--regexp=REGEXP, -r REGEXP] [--regions=REGION,[REGION,...]] + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + List composite health checks. + +POSITIONAL ARGUMENTS + [NAME ...] + (DEPRECATED) If provided, show details for the specified names and/or + URIs of resources. + + Argument NAME is deprecated. Use --filter="name=( 'NAME' ... )" + instead. + +FLAGS + --regexp=REGEXP, -r REGEXP + (DEPRECATED) Regular expression to filter the names of the results on. + Any names that do not match the entire regular expression will be + filtered out. + + Flag --regexp is deprecated. Use --filter="name~'REGEXP'" instead. + + --regions=REGION,[REGION,...] + If provided, only resources from the given regions are queried. + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + + --uri + Print a list of resource URIs instead of the default output, and change + the command output to a list of URIs. If this flag is used with + --format, the formatting is applied on this URI list. To display URIs + alongside other keys instead, use the uri() transform. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + These variants are also available: + + $ gcloud alpha compute composite-health-checks list + + $ gcloud beta compute composite-health-checks list + diff --git a/gcloud/compute/composite-health-checks/update b/gcloud/compute/composite-health-checks/update new file mode 100644 index 000000000..e1de6b9fe --- /dev/null +++ b/gcloud/compute/composite-health-checks/update @@ -0,0 +1,97 @@ +NAME + gcloud compute composite-health-checks update - update a composite health + check + +SYNOPSIS + gcloud compute composite-health-checks update + (COMPOSITE_HEALTH_CHECK : --region=REGION) + (--description=DESCRIPTION --health-destination=HEALTH_DESTINATION + --health-sources=HEALTH_SOURCES,[...]) [--async] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Update a composite health check. + +EXAMPLES + The following command updates an existing composite health check: + + $ gcloud compute composite-health-checks update \ + --region= \ + --health-destination=my-new-fr + +POSITIONAL ARGUMENTS + Composite health check resource - The name of the composite health check + you want to update. The arguments in this group can be used to specify the + attributes of this resource. (NOTE) Some attributes are not given + arguments in this group but can be set in other ways. + + To set the project attribute: + ◆ provide the argument composite_health_check on the command line with + a fully specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + COMPOSITE_HEALTH_CHECK + ID of the composite health check or fully qualified identifier for + the composite health check. + + To set the composite_health_check attribute: + ▸ provide the argument composite_health_check on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --region=REGION + The name of the Google Compute Engine region. + + To set the region attribute: + ▸ provide the argument composite_health_check on the command line + with a fully specified name; + ▸ provide the argument --region on the command line; + ▸ set the property compute/region. + +REQUIRED FLAGS + At least one of these must be specified: + + --description=DESCRIPTION + A textual description of this resource. + + --health-destination=HEALTH_DESTINATION + URL to the destination resource. Must be set. Must be a + ForwardingRule. The ForwardingRule must have load balancing scheme + INTERNAL or INTERNAL_MANAGED and must be regional and in the same + region as the CompositeHealthCheck (cross-region deployment for + INTERNAL_MANAGED is not supported). Can be mutated. + + --health-sources=HEALTH_SOURCES,[...] + URLs to the HealthSource resources whose results are AND'ed. I.e. the + aggregated result is HEALTHY only if all sources are HEALTHY. Must + have at least 1. Must not have more than 10. Must be regional and in + the same region as the CompositeHealthCheck. Can be mutated. + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the compute/v1 API. The full documentation for this API + can be found at: https://cloud.google.com/compute/ + +NOTES + These variants are also available: + + $ gcloud alpha compute composite-health-checks update + + $ gcloud beta compute composite-health-checks update + diff --git a/gcloud/compute/disks/bulk/create b/gcloud/compute/disks/bulk/create index a9d6f96b5..d41b2831a 100644 --- a/gcloud/compute/disks/bulk/create +++ b/gcloud/compute/disks/bulk/create @@ -1,15 +1,19 @@ NAME - gcloud compute disks bulk create - create multiple Compute Engine disks + gcloud compute disks bulk create - create multiple Compute Engine disks or + a consistency group of instant snapshots SYNOPSIS - gcloud compute disks bulk create - --source-consistency-group-policy=SOURCE_CONSISTENCY_GROUP_POLICY - (--region=REGION | --zone=ZONE) [GCLOUD_WIDE_FLAG ...] + gcloud compute disks bulk create (--region=REGION | --zone=ZONE) + [--source-consistency-group-policy=SOURCE_CONSISTENCY_GROUP_POLICY] + [--source-instant-snapshot-group=SOURCE_INSTANT_SNAPSHOT_GROUP] + [--source-instant-snapshot-group-region=SOURCE_INSTANT_SNAPSHOT_GROUP_REGION | --source-instant-snapshot-group-zone=SOURCE_INSTANT_SNAPSHOT_GROUP_ZONE] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION gcloud compute disks bulk create facilitates the creation of multiple Compute Engine disks with a single command. This includes cloning a set of - Async PD secondary disks with the same consistency group policy. + Async PD secondary disks with the same consistency group policy or a + consistency group of instant snapshots. EXAMPLES To consistently clone secondary disks with the same consistency group @@ -23,10 +27,6 @@ EXAMPLES --zone=us-central1-a REQUIRED FLAGS - --source-consistency-group-policy=SOURCE_CONSISTENCY_GROUP_POLICY - URL of the source consistency group resource policy. The resource - policy is always the same region as the source disks. - Exactly one of these must be specified: --region=REGION @@ -71,6 +71,29 @@ REQUIRED FLAGS Alternatively, the zone can be stored in the environment variable CLOUDSDK_COMPUTE_ZONE. +OPTIONAL FLAGS + --source-consistency-group-policy=SOURCE_CONSISTENCY_GROUP_POLICY + URL of the format regions//resourcePolicies/ + of the source consistency group resource policy. The resource policy is + always in the same region as the source disks. + + --source-instant-snapshot-group=SOURCE_INSTANT_SNAPSHOT_GROUP + URL of the format + regions//instantSnapshotGroups/ or + zones//instantSnapshotGroups/ of the + source consistency group of instant snapshots used to create the disks. + + At most one of these can be specified: + + --source-instant-snapshot-group-region=SOURCE_INSTANT_SNAPSHOT_GROUP_REGION + Region of the source instant snapshot group to operate on. Overrides + the default compute/region property value for this command + invocation. + + --source-instant-snapshot-group-zone=SOURCE_INSTANT_SNAPSHOT_GROUP_ZONE + Zone of the source instant snapshot group to operate on. 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, diff --git a/gcloud/compute/disks/bulk/help b/gcloud/compute/disks/bulk/help index d39cda819..a4674a830 100644 --- a/gcloud/compute/disks/bulk/help +++ b/gcloud/compute/disks/bulk/help @@ -17,7 +17,8 @@ COMMANDS COMMAND is one of the following: create - Create multiple Compute Engine disks. + Create multiple Compute Engine disks or a consistency group of instant + snapshots. NOTES These variants are also available: diff --git a/gcloud/compute/disks/help b/gcloud/compute/disks/help index ce26e5d08..ddece265d 100644 --- a/gcloud/compute/disks/help +++ b/gcloud/compute/disks/help @@ -86,10 +86,10 @@ COMMANDS Consistently stops a group of asynchronously replicating disks. update - Update a Compute Engine persistent disk. + Update a Compute Engine Hyperdisk or Persistent Disk. update-kms-key - Update the KMS key of a persistent disk. + Update the KMS key of a Hyperdisk or Persistent Disk. NOTES These variants are also available: diff --git a/gcloud/compute/disks/update b/gcloud/compute/disks/update index 903b19baa..3c38438db 100644 --- a/gcloud/compute/disks/update +++ b/gcloud/compute/disks/update @@ -1,5 +1,6 @@ NAME - gcloud compute disks update - update a Compute Engine persistent disk + gcloud compute disks update - update a Compute Engine Hyperdisk or + Persistent Disk SYNOPSIS gcloud compute disks update DISK_NAME [--access-mode=ACCESS_MODE] @@ -14,7 +15,8 @@ SYNOPSIS [--region=REGION | --zone=ZONE] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - gcloud compute disks update updates a Compute Engine persistent disk. + gcloud compute disks update updates a Compute Engine Hyperdisk or + Persistent Disk. EXAMPLES To update labels 'k0' and 'k1' and remove label 'k3' of a disk, run: diff --git a/gcloud/compute/disks/update-kms-key b/gcloud/compute/disks/update-kms-key index 8ea693adb..2bbc5f62c 100644 --- a/gcloud/compute/disks/update-kms-key +++ b/gcloud/compute/disks/update-kms-key @@ -1,6 +1,6 @@ NAME - gcloud compute disks update-kms-key - update the KMS key of a persistent - disk + gcloud compute disks update-kms-key - update the KMS key of a Hyperdisk or + Persistent Disk SYNOPSIS gcloud compute disks update-kms-key DISK_NAME @@ -9,12 +9,12 @@ SYNOPSIS [--region=REGION | --zone=ZONE] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - ▪ gcloud compute disks update-kms-key * updates the KMS key of a - Compute Engine persistent disk by rotating it to the primary version of - the key or to the primary version of a new KMS key. + gcloud compute disks update-kms-key updates the KMS key of a Compute Engine + Persistent or Hyperdisk Disk by rotating it to the primary version of the + key or to the primary version of a new KMS key. EXAMPLES - To rotate the KMS key of a disk named example-disk-1 to the primary + To change the KMS key of a disk named example-disk-1 to the primary version, run: $ gcloud compute disks update-kms-key example-disk-1 \ diff --git a/gcloud/compute/future-reservations/create b/gcloud/compute/future-reservations/create index 22d908fef..bee35d348 100644 --- a/gcloud/compute/future-reservations/create +++ b/gcloud/compute/future-reservations/create @@ -17,6 +17,7 @@ SYNOPSIS [--[no-]require-specific-reservation] [--reservation-mode=RESERVATION_MODE] [--reservation-name=RESERVATION_NAME] + [--resource-manager-tags=[KEY=VALUE,...]] [--scheduling-type=SCHEDULING_TYPE] [--total-count=TOTAL_COUNT] [--zone=ZONE] [--auto-created-reservations-delete-time=AUTO_CREATED_RESERVATIONS_DELETE_TIME | --auto-created-reservations-duration=AUTO_CREATED_RESERVATIONS_DURATION] @@ -217,6 +218,9 @@ OPTIONAL FLAGS Approval with INACTIVE state till specified start-time. Either provide the reservation_name or a name_prefix. + --resource-manager-tags=[KEY=VALUE,...] + Resource manager tags to be bound to the future reservation. + --scheduling-type=SCHEDULING_TYPE Maintenance for the reserved capacity. SCHEDULING_TYPE must be one of: diff --git a/gcloud/compute/global-vm-extension-policies/create b/gcloud/compute/global-vm-extension-policies/create new file mode 100644 index 000000000..b4dd2a1e7 --- /dev/null +++ b/gcloud/compute/global-vm-extension-policies/create @@ -0,0 +1,144 @@ +NAME + gcloud compute global-vm-extension-policies create - create a Compute + Engine global VM extension policy + +SYNOPSIS + gcloud compute global-vm-extension-policies create NAME + --extensions=EXTENSION_NAME,[...] [--config=KEY=VALUE,[KEY=VALUE,...]] + [--config-from-file=KEY=FILE_PATH,[...]] [--description=DESCRIPTION] + [--inclusion-labels=INCLUSION_LABELS] + [--priority=PRIORITY; default=1000] + [--rollout-conflict-behavior=ROLLOUT_CONFLICT_BEHAVIOR] + [--rollout-custom-plan=ROLLOUT_CUSTOM_PLAN] + [--rollout-predefined-plan=ROLLOUT_PREDEFINED_PLAN] + [--version=KEY=VALUE,[KEY=VALUE,...]] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Create a Compute Engine global VM extension policy. + +EXAMPLES + To create a global VM extension policy, run: + + $ gcloud compute global-vm-extension-policies create \ + test-policy-name --description="test policy" \ + --extensions=extension1,extension2 \ + --version=extension1=version1,extension2=version2 \ + --config=extension1="config1",extension2="config2" \ + --inclusion-labels=env=prod \ + --inclusion-labels=env=preprod,workload=load-test \ + --rollout-predefined-plan=slow_rollout --priority=1000 + +POSITIONAL ARGUMENTS + NAME + Name of the global vm extension policy to create. + +REQUIRED FLAGS + --extensions=EXTENSION_NAME,[...] + One or more extensions to be added to the policy. + +OPTIONAL FLAGS + --config=KEY=VALUE,[KEY=VALUE,...] + A comma separated key:value list where the key is the extension name + and the value is the desired config for the given extension. The + extension name must be one of the extensions specified in the + --extensions flag. + + E.g. --config=filestore='filestore config',ops-agent='ops agent config' + + Raises: ArgumentTypeError: If the extension name is not specified in + the --extensions flag. + + --config-from-file=KEY=FILE_PATH,[...] + Same as --config except that the value for the entry will be read from + a local file. The extension name must be one of the extensions + specified in the --extensions flag. + + It is an error to specify the same extension in both --config and + --config-from-file. + + --description=DESCRIPTION + An optional text description for the extension policy. + + --inclusion-labels=INCLUSION_LABELS + A list of inclusion labels to select the target VMs. + + The expected format for a single selector is "key1=value1,key2=value2". + A VM is selected if it has ALL the inclusion labels. + + When the option is specified multiple times, it assumes a logical OR + between the selectors. + + For example, if the inclusion labels are ["env=prod,workload=frontend", + "workload=backend"], the following VMs will be selected: + ◆ VM1: env=prod, workload=frontend, something=else + ◆ VM2: env=prod, workload=backend But not: + ◆ VM3: env=prod + + If not specified, ALL VMs in the project/folder will be selected. + + --priority=PRIORITY; default=1000 + The priority of the policy. Lower the number, higher the priority. When + two policies try to apply the same extension to a VM, the policy with + higher priority takes precedence. If the priorities are the same, the + policy with the more recent update timestamp takes precedence. If a + policy is deleted, the extension remains installed on the VM if a + lower-priority policy still applies. + + Range from 0 to 65535. Default is 1000. + + --rollout-conflict-behavior=ROLLOUT_CONFLICT_BEHAVIOR + Specifies the behavior of a rollout if a conflict is detected between a + zonal policy and a global policy. See gcloud compute + zone-vm-extension-policies for more details on zonal policies. + + The possible values are: + ◆ "": The zonal policy value is used in case of a conflict. This is + the default behavior. + ◆ overwrite: The global policy overwrites the zonal policy. + + If you set --rollout-conflict-behavior to overwrite and want to revert + to the default behavior, use the update command and omit the + --rollout-conflict-behavior flag. + + --rollout-custom-plan=ROLLOUT_CUSTOM_PLAN + Provide the name of a custom rollout plan to be used for the rollout. + + One of either --rollout-predefined-plan or --rollout-custom-plan must + be specified, but not both. + + --rollout-predefined-plan=ROLLOUT_PREDEFINED_PLAN + Provide the name of a predefined rollout plan from [fast_rollout, + slow_rollout] to be used for the rollout. + + One of either --rollout-predefined-plan or --rollout-custom-plan must + be specified, but not both. + + ROLLOUT_PREDEFINED_PLAN must be one of: fast_rollout, slow_rollout. + + --version=KEY=VALUE,[KEY=VALUE,...] + A comma separated key:value list where the key is the extension name + and the value is the desired version for the given extension. The + extension name must be one of the extensions specified in the + --extensions flag. If no version is specified for an extension, the + latest version will be used and will be upgraded automatically. + + E.g. --version=filestore=123ABC,ops-agent=456DEF + + Raises: ArgumentTypeError: If the extension name is not specified in + the --extensions flag. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + These variants are also available: + + $ gcloud alpha compute global-vm-extension-policies create + + $ gcloud beta compute global-vm-extension-policies create + diff --git a/gcloud/compute/global-vm-extension-policies/delete b/gcloud/compute/global-vm-extension-policies/delete new file mode 100644 index 000000000..33a558f0e --- /dev/null +++ b/gcloud/compute/global-vm-extension-policies/delete @@ -0,0 +1,57 @@ +NAME + gcloud compute global-vm-extension-policies delete - delete a Compute + Engine global VM extension policy + +SYNOPSIS + gcloud compute global-vm-extension-policies delete NAME + [--rollout-custom-plan=ROLLOUT_CUSTOM_PLAN] + [--rollout-predefined-plan=ROLLOUT_PREDEFINED_PLAN] + [--rollout-retry-uuid=ROLLOUT_RETRY_UUID] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Delete a Compute Engine global VM extension policy. + +EXAMPLES + To delete a global VM extension policy, run: + + $ gcloud compute global-vm-extension-policies delete test-policy-name + +POSITIONAL ARGUMENTS + NAME + Name of the global vm extension policy to delete. + +FLAGS + --rollout-custom-plan=ROLLOUT_CUSTOM_PLAN + Provide the name of a custom rollout plan to be used for the rollout. + + One of either --rollout-predefined-plan or --rollout-custom-plan must + be specified, but not both. + + --rollout-predefined-plan=ROLLOUT_PREDEFINED_PLAN + Provide the name of a predefined rollout plan from [fast_rollout, + slow_rollout] to be used for the rollout. + + One of either --rollout-predefined-plan or --rollout-custom-plan must + be specified, but not both. + + ROLLOUT_PREDEFINED_PLAN must be one of: fast_rollout, slow_rollout. + + --rollout-retry-uuid=ROLLOUT_RETRY_UUID + The UUID of the rollout retry action. Only set it if this is a retry + for an existing resource. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + These variants are also available: + + $ gcloud alpha compute global-vm-extension-policies delete + + $ gcloud beta compute global-vm-extension-policies delete + diff --git a/gcloud/compute/global-vm-extension-policies/describe b/gcloud/compute/global-vm-extension-policies/describe new file mode 100644 index 000000000..e9c23d41e --- /dev/null +++ b/gcloud/compute/global-vm-extension-policies/describe @@ -0,0 +1,36 @@ +NAME + gcloud compute global-vm-extension-policies describe - describe a Compute + Engine global VM extension policy + +SYNOPSIS + gcloud compute global-vm-extension-policies describe NAME + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Describe a Compute Engine global VM extension policy. + +EXAMPLES + To describe a global VM extension policy, run: + + $ gcloud compute global-vm-extension-policies describe \ + test-policy-name + +POSITIONAL ARGUMENTS + NAME + Name of the global vm extension policy to describe. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + These variants are also available: + + $ gcloud alpha compute global-vm-extension-policies describe + + $ gcloud beta compute global-vm-extension-policies describe + diff --git a/gcloud/compute/global-vm-extension-policies/help b/gcloud/compute/global-vm-extension-policies/help new file mode 100644 index 000000000..4c60c4c69 --- /dev/null +++ b/gcloud/compute/global-vm-extension-policies/help @@ -0,0 +1,40 @@ +NAME + gcloud compute global-vm-extension-policies - compute Engine global VM + extension policies + +SYNOPSIS + gcloud compute global-vm-extension-policies COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Compute Engine global VM extension policies. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + create + Create a Compute Engine global VM extension policy. + + delete + Delete a Compute Engine global VM extension policy. + + describe + Describe a Compute Engine global VM extension policy. + + list + List Compute Engine global VM extension policies. + + update + Update a Compute Engine global VM extension policy. + +NOTES + These variants are also available: + + $ gcloud alpha compute global-vm-extension-policies + + $ gcloud beta compute global-vm-extension-policies + diff --git a/gcloud/beta/lifesciences/locations/list b/gcloud/compute/global-vm-extension-policies/list similarity index 76% rename from gcloud/beta/lifesciences/locations/list rename to gcloud/compute/global-vm-extension-policies/list index 170896648..0dab7e938 100644 --- a/gcloud/beta/lifesciences/locations/list +++ b/gcloud/compute/global-vm-extension-policies/list @@ -1,19 +1,19 @@ NAME - gcloud beta lifesciences locations list - list all locations where Cloud - Life Sciences is available + gcloud compute global-vm-extension-policies list - list Compute Engine + global VM extension policies SYNOPSIS - gcloud beta lifesciences locations list [--filter=EXPRESSION] + gcloud compute global-vm-extension-policies list [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) List all locations where Cloud Life Sciences is available. + List Compute Engine global VM extension policies. EXAMPLES - To list all locations, run: + To list all global VM extension policy, run: - $ gcloud beta lifesciences locations list + $ gcloud compute global-vm-extension-policies list LIST COMMAND FLAGS --filter=EXPRESSION @@ -55,13 +55,10 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. -API REFERENCE - This command uses the lifesciences/v2beta API. The full documentation for - this API can be found at: https://cloud.google.com/life-sciences - NOTES - This command is currently in beta and might change without notice. This - variant is also available: + These variants are also available: - $ gcloud alpha lifesciences locations list + $ gcloud alpha compute global-vm-extension-policies list + + $ gcloud beta compute global-vm-extension-policies list diff --git a/gcloud/compute/global-vm-extension-policies/update b/gcloud/compute/global-vm-extension-policies/update new file mode 100644 index 000000000..b835fe3ea --- /dev/null +++ b/gcloud/compute/global-vm-extension-policies/update @@ -0,0 +1,149 @@ +NAME + gcloud compute global-vm-extension-policies update - update a Compute + Engine global VM extension policy + +SYNOPSIS + gcloud compute global-vm-extension-policies update NAME + --extensions=EXTENSION_NAME,[...] [--config=KEY=VALUE,[KEY=VALUE,...]] + [--config-from-file=KEY=FILE_PATH,[...]] [--description=DESCRIPTION] + [--inclusion-labels=INCLUSION_LABELS] + [--priority=PRIORITY; default=1000] + [--rollout-conflict-behavior=ROLLOUT_CONFLICT_BEHAVIOR] + [--rollout-custom-plan=ROLLOUT_CUSTOM_PLAN] + [--rollout-predefined-plan=ROLLOUT_PREDEFINED_PLAN] + [--rollout-retry-uuid=ROLLOUT_RETRY_UUID] + [--version=KEY=VALUE,[KEY=VALUE,...]] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Update a Compute Engine global VM extension policy. + +EXAMPLES + To update a global VM extension policy, run: + + $ gcloud compute global-vm-extension-policies update \ + test-policy-name --description="test policy" \ + --extensions=extension1,extension2 \ + --version=extension1=version1,extension2=version2 \ + --config=extension1="config1",extension2="config2" \ + --inclusion-labels=env=prod \ + --inclusion-labels=env=preprod,workload=load-test \ + --rollout-predefined-plan=slow_rollout --priority=1000 + +POSITIONAL ARGUMENTS + NAME + Name of the global vm extension policy to update. + +REQUIRED FLAGS + --extensions=EXTENSION_NAME,[...] + One or more extensions to be added to the policy. + +OPTIONAL FLAGS + --config=KEY=VALUE,[KEY=VALUE,...] + A comma separated key:value list where the key is the extension name + and the value is the desired config for the given extension. The + extension name must be one of the extensions specified in the + --extensions flag. + + E.g. --config=filestore='filestore config',ops-agent='ops agent config' + + Raises: ArgumentTypeError: If the extension name is not specified in + the --extensions flag. + + --config-from-file=KEY=FILE_PATH,[...] + Same as --config except that the value for the entry will be read from + a local file. The extension name must be one of the extensions + specified in the --extensions flag. + + It is an error to specify the same extension in both --config and + --config-from-file. + + --description=DESCRIPTION + An optional text description for the extension policy. + + --inclusion-labels=INCLUSION_LABELS + A list of inclusion labels to select the target VMs. + + The expected format for a single selector is "key1=value1,key2=value2". + A VM is selected if it has ALL the inclusion labels. + + When the option is specified multiple times, it assumes a logical OR + between the selectors. + + For example, if the inclusion labels are ["env=prod,workload=frontend", + "workload=backend"], the following VMs will be selected: + ◆ VM1: env=prod, workload=frontend, something=else + ◆ VM2: env=prod, workload=backend But not: + ◆ VM3: env=prod + + If not specified, ALL VMs in the project/folder will be selected. + + --priority=PRIORITY; default=1000 + The priority of the policy. Lower the number, higher the priority. When + two policies try to apply the same extension to a VM, the policy with + higher priority takes precedence. If the priorities are the same, the + policy with the more recent update timestamp takes precedence. If a + policy is deleted, the extension remains installed on the VM if a + lower-priority policy still applies. + + Range from 0 to 65535. Default is 1000. + + --rollout-conflict-behavior=ROLLOUT_CONFLICT_BEHAVIOR + Specifies the behavior of a rollout if a conflict is detected between a + zonal policy and a global policy. See gcloud compute + zone-vm-extension-policies for more details on zonal policies. + + The possible values are: + ◆ "": The zonal policy value is used in case of a conflict. This is + the default behavior. + ◆ overwrite: The global policy overwrites the zonal policy. + + If you set --rollout-conflict-behavior to overwrite and want to revert + to the default behavior, use the update command and omit the + --rollout-conflict-behavior flag. + + --rollout-custom-plan=ROLLOUT_CUSTOM_PLAN + Provide the name of a custom rollout plan to be used for the rollout. + + One of either --rollout-predefined-plan or --rollout-custom-plan must + be specified, but not both. + + --rollout-predefined-plan=ROLLOUT_PREDEFINED_PLAN + Provide the name of a predefined rollout plan from [fast_rollout, + slow_rollout] to be used for the rollout. + + One of either --rollout-predefined-plan or --rollout-custom-plan must + be specified, but not both. + + ROLLOUT_PREDEFINED_PLAN must be one of: fast_rollout, slow_rollout. + + --rollout-retry-uuid=ROLLOUT_RETRY_UUID + The UUID of the rollout retry action. Only set it if this is a retry + for an existing resource. + + --version=KEY=VALUE,[KEY=VALUE,...] + A comma separated key:value list where the key is the extension name + and the value is the desired version for the given extension. The + extension name must be one of the extensions specified in the + --extensions flag. If no version is specified for an extension, the + latest version will be used and will be upgraded automatically. + + E.g. --version=filestore=123ABC,ops-agent=456DEF + + Raises: ArgumentTypeError: If the extension name is not specified in + the --extensions flag. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + These variants are also available: + + $ gcloud alpha compute global-vm-extension-policies update + + $ gcloud beta compute global-vm-extension-policies update + diff --git a/gcloud/compute/health-aggregation-policies/create b/gcloud/compute/health-aggregation-policies/create new file mode 100644 index 000000000..136c1d186 --- /dev/null +++ b/gcloud/compute/health-aggregation-policies/create @@ -0,0 +1,115 @@ +NAME + gcloud compute health-aggregation-policies create - create a health + aggregation policy + +SYNOPSIS + gcloud compute health-aggregation-policies create + (HEALTH_AGGREGATION_POLICY : --region=REGION) [--async] + [--description=DESCRIPTION] + [--healthy-percent-threshold=HEALTHY_PERCENT_THRESHOLD; default=60] + [--min-healthy-threshold=MIN_HEALTHY_THRESHOLD; default=1] + [--policy-type=POLICY_TYPE; default="backend-service-policy"] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Create a health aggregation policy. + +EXAMPLES + The following command creates a new health aggregation policy: + + $ gcloud compute health-aggregation-policies create \ + --region= \ + --healthy-percent-threshold 60 --min-healthy-threshold 2 \ + --policy-type=BACKEND_SERVICE_POLICY + +POSITIONAL ARGUMENTS + Health aggregation policy resource - The name of the health aggregation + policy you want to create. The arguments in this group can be used to + specify the attributes of this resource. (NOTE) Some attributes are not + given arguments in this group but can be set in other ways. + + To set the project attribute: + ◆ provide the argument health_aggregation_policy on the command line + with a fully specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + HEALTH_AGGREGATION_POLICY + ID of the health aggregation policy or fully qualified identifier for + the health aggregation policy. + + To set the health_aggregation_policy attribute: + ▸ provide the argument health_aggregation_policy on the command + line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --region=REGION + The name of the Google Compute Engine region. + + To set the region attribute: + ▸ provide the argument health_aggregation_policy on the command + line with a fully specified name; + ▸ provide the argument --region on the command line; + ▸ set the property compute/region. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --description=DESCRIPTION + A textual description of the health aggregation policy. + + --healthy-percent-threshold=HEALTHY_PERCENT_THRESHOLD; default=60 + Can only be set if the policyType field is BACKEND_SERVICE_POLICY. + Specifies the threshold (as a percentage) of healthy endpoints required + in order to consider the aggregated health result HEALTHY. Defaults to + 60. Must be in range [0, 100]. Not applicable if the policyType field + is DNS_PUBLIC_IP_POLICY. Can be mutated. This field is optional, and + will be set to the default if unspecified. Note that both this + threshold and minHealthyThreshold must be satisfied in order for + HEALTHY to be the aggregated result. "Endpoints" refers to network + endpoints within a Network Endpoint Group or instances within an + Instance Group. + + --min-healthy-threshold=MIN_HEALTHY_THRESHOLD; default=1 + Can only be set if the policyType field is BACKEND_SERVICE_POLICY. + Specifies the minimum number of healthy endpoints required in order to + consider the aggregated health result HEALTHY. Defaults to 1. Must be + positive. Not applicable if the policyType field is + DNS_PUBLIC_IP_POLICY. Can be mutated. This field is optional, and will + be set to the default if unspecified. Note that both this threshold and + healthyPercentThreshold must be satisfied in order for HEALTHY to be + the aggregated result. "Endpoints" refers to network endpoints within a + Network Endpoint Group or instances within an Instance Group. + + --policy-type=POLICY_TYPE; default="backend-service-policy" + Specifies the type of the healthAggregationPolicy. The only allowed + value for regional resources is BACKEND_SERVICE_POLICY. Must be + specified when the healthAggregationPolicy is created, and cannot be + mutated. POLICY_TYPE must be one of: backend-service-policy, + dns-public-ip-policy. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the compute/v1 API. The full documentation for this API + can be found at: https://cloud.google.com/compute/ + +NOTES + These variants are also available: + + $ gcloud alpha compute health-aggregation-policies create + + $ gcloud beta compute health-aggregation-policies create + diff --git a/gcloud/compute/health-aggregation-policies/delete b/gcloud/compute/health-aggregation-policies/delete new file mode 100644 index 000000000..122dba604 --- /dev/null +++ b/gcloud/compute/health-aggregation-policies/delete @@ -0,0 +1,76 @@ +NAME + gcloud compute health-aggregation-policies delete - delete a health + aggregation policy + +SYNOPSIS + gcloud compute health-aggregation-policies delete + (HEALTH_AGGREGATION_POLICY : --region=REGION) [--async] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Delete a health aggregation policy. + +EXAMPLES + To delete a single health aggregation policy, run the following command: + + $ gcloud compute health-aggregation-policies delete \ + --region= + +POSITIONAL ARGUMENTS + Health aggregation policy resource - Name of the health aggregation policy + you want to delete. The arguments in this group can be used to specify the + attributes of this resource. (NOTE) Some attributes are not given + arguments in this group but can be set in other ways. + + To set the project attribute: + ◆ provide the argument health_aggregation_policy on the command line + with a fully specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + HEALTH_AGGREGATION_POLICY + ID of the health aggregation policy or fully qualified identifier for + the health aggregation policy. + + To set the health_aggregation_policy attribute: + ▸ provide the argument health_aggregation_policy on the command + line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --region=REGION + The name of the Google Compute Engine region. + + To set the region attribute: + ▸ provide the argument health_aggregation_policy on the command + line with a fully specified name; + ▸ provide the argument --region on the command line; + ▸ set the property compute/region. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the compute/v1 API. The full documentation for this API + can be found at: https://cloud.google.com/compute/ + +NOTES + These variants are also available: + + $ gcloud alpha compute health-aggregation-policies delete + + $ gcloud beta compute health-aggregation-policies delete + diff --git a/gcloud/compute/health-aggregation-policies/describe b/gcloud/compute/health-aggregation-policies/describe new file mode 100644 index 000000000..96da6ed71 --- /dev/null +++ b/gcloud/compute/health-aggregation-policies/describe @@ -0,0 +1,71 @@ +NAME + gcloud compute health-aggregation-policies describe - describe a health + aggregation policy + +SYNOPSIS + gcloud compute health-aggregation-policies describe + (HEALTH_AGGREGATION_POLICY : --region=REGION) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Describe a health aggregation policy. + +EXAMPLES + To retrieve a single health aggregation policy and print its properties, + run the following command: + + $ gcloud compute health-aggregation-policies describe \ + --region= + +POSITIONAL ARGUMENTS + Health aggregation policy resource - Name of the health aggregation policy + you want to inspect. The arguments in this group can be used to specify + the attributes of this resource. (NOTE) Some attributes are not given + arguments in this group but can be set in other ways. + + To set the project attribute: + ◆ provide the argument health_aggregation_policy on the command line + with a fully specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + HEALTH_AGGREGATION_POLICY + ID of the health aggregation policy or fully qualified identifier for + the health aggregation policy. + + To set the health_aggregation_policy attribute: + ▸ provide the argument health_aggregation_policy on the command + line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --region=REGION + The name of the Google Compute Engine region. + + To set the region attribute: + ▸ provide the argument health_aggregation_policy on the command + line with a fully specified name; + ▸ provide the argument --region on the command line; + ▸ set the property compute/region. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the compute/v1 API. The full documentation for this API + can be found at: https://cloud.google.com/compute/ + +NOTES + These variants are also available: + + $ gcloud alpha compute health-aggregation-policies describe + + $ gcloud beta compute health-aggregation-policies describe + diff --git a/gcloud/compute/health-aggregation-policies/help b/gcloud/compute/health-aggregation-policies/help new file mode 100644 index 000000000..96d3017c0 --- /dev/null +++ b/gcloud/compute/health-aggregation-policies/help @@ -0,0 +1,40 @@ +NAME + gcloud compute health-aggregation-policies - manage health aggregation + policies + +SYNOPSIS + gcloud compute health-aggregation-policies COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Manage health aggregation policies. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + create + Create a health aggregation policy. + + delete + Delete a health aggregation policy. + + describe + Describe a health aggregation policy. + + list + List health aggregation policies. + + update + Update a health aggregation policy. + +NOTES + These variants are also available: + + $ gcloud alpha compute health-aggregation-policies + + $ gcloud beta compute health-aggregation-policies + diff --git a/gcloud/compute/health-aggregation-policies/list b/gcloud/compute/health-aggregation-policies/list new file mode 100644 index 000000000..9dd8efd1f --- /dev/null +++ b/gcloud/compute/health-aggregation-policies/list @@ -0,0 +1,79 @@ +NAME + gcloud compute health-aggregation-policies list - list health aggregation + policies + +SYNOPSIS + gcloud compute health-aggregation-policies list [NAME ...] + [--regexp=REGEXP, -r REGEXP] [--regions=REGION,[REGION,...]] + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + List health aggregation policies. + +POSITIONAL ARGUMENTS + [NAME ...] + (DEPRECATED) If provided, show details for the specified names and/or + URIs of resources. + + Argument NAME is deprecated. Use --filter="name=( 'NAME' ... )" + instead. + +FLAGS + --regexp=REGEXP, -r REGEXP + (DEPRECATED) Regular expression to filter the names of the results on. + Any names that do not match the entire regular expression will be + filtered out. + + Flag --regexp is deprecated. Use --filter="name~'REGEXP'" instead. + + --regions=REGION,[REGION,...] + If provided, only resources from the given regions are queried. + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + + --uri + Print a list of resource URIs instead of the default output, and change + the command output to a list of URIs. If this flag is used with + --format, the formatting is applied on this URI list. To display URIs + alongside other keys instead, use the uri() transform. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + These variants are also available: + + $ gcloud alpha compute health-aggregation-policies list + + $ gcloud beta compute health-aggregation-policies list + diff --git a/gcloud/compute/health-aggregation-policies/update b/gcloud/compute/health-aggregation-policies/update new file mode 100644 index 000000000..612db9ca6 --- /dev/null +++ b/gcloud/compute/health-aggregation-policies/update @@ -0,0 +1,110 @@ +NAME + gcloud compute health-aggregation-policies update - update a health + aggregation policy + +SYNOPSIS + gcloud compute health-aggregation-policies update + (HEALTH_AGGREGATION_POLICY : --region=REGION) + (--description=DESCRIPTION + --healthy-percent-threshold=HEALTHY_PERCENT_THRESHOLD + --min-healthy-threshold=MIN_HEALTHY_THRESHOLD) [--async] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Update a health aggregation policy. + +EXAMPLES + The following command updates a health aggregation policy: + + $ gcloud compute health-aggregation-policies update \ + --region= \ + --healthy-percent-threshold 60 --min-healthy-threshold 2 \ + +POSITIONAL ARGUMENTS + Health aggregation policy resource - The health aggregation policy you + want to update. The arguments in this group can be used to specify the + attributes of this resource. (NOTE) Some attributes are not given + arguments in this group but can be set in other ways. + + To set the project attribute: + ◆ provide the argument health_aggregation_policy on the command line + with a fully specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + HEALTH_AGGREGATION_POLICY + ID of the health aggregation policy or fully qualified identifier for + the health aggregation policy. + + To set the health_aggregation_policy attribute: + ▸ provide the argument health_aggregation_policy on the command + line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --region=REGION + The name of the Google Compute Engine region. + + To set the region attribute: + ▸ provide the argument health_aggregation_policy on the command + line with a fully specified name; + ▸ provide the argument --region on the command line; + ▸ set the property compute/region. + +REQUIRED FLAGS + At least one of these must be specified: + + --description=DESCRIPTION + A textual description of the health aggregation policy. + + --healthy-percent-threshold=HEALTHY_PERCENT_THRESHOLD + Can only be set if the policyType field is BACKEND_SERVICE_POLICY. + Specifies the threshold (as a percentage) of healthy endpoints + required in order to consider the aggregated health result HEALTHY. + Defaults to 60. Must be in range [0, 100]. Not applicable if the + policyType field is DNS_PUBLIC_IP_POLICY. Can be mutated. This field + is optional, and will be set to the default if unspecified. Note that + both this threshold and minHealthyThreshold must be satisfied in + order for HEALTHY to be the aggregated result. "Endpoints" refers to + network endpoints within a Network Endpoint Group or instances within + an Instance Group. + + --min-healthy-threshold=MIN_HEALTHY_THRESHOLD + Can only be set if the policyType field is BACKEND_SERVICE_POLICY. + Specifies the minimum number of healthy endpoints required in order + to consider the aggregated health result HEALTHY. Defaults to 1. Must + be positive. Not applicable if the policyType field is + DNS_PUBLIC_IP_POLICY. Can be mutated. This field is optional, and + will be set to the default if unspecified. Note that both this + threshold and healthyPercentThreshold must be satisfied in order for + HEALTHY to be the aggregated result. "Endpoints" refers to network + endpoints within a Network Endpoint Group or instances within an + Instance Group. + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the compute/v1 API. The full documentation for this API + can be found at: https://cloud.google.com/compute/ + +NOTES + These variants are also available: + + $ gcloud alpha compute health-aggregation-policies update + + $ gcloud beta compute health-aggregation-policies update + diff --git a/gcloud/compute/health-sources/create b/gcloud/compute/health-sources/create new file mode 100644 index 000000000..6b78e7b71 --- /dev/null +++ b/gcloud/compute/health-sources/create @@ -0,0 +1,101 @@ +NAME + gcloud compute health-sources create - create a health source + +SYNOPSIS + gcloud compute health-sources create (HEALTH_SOURCE : --region=REGION) + --health-aggregation-policy=HEALTH_AGGREGATION_POLICY + --sources=SOURCES,[SOURCES,...] [--async] [--description=DESCRIPTION] + [--source-type=SOURCE_TYPE; default="backend-service"] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Create a health source. + +EXAMPLES + The following command creates a new health source: + + $ gcloud compute health-sources create \ + --region= --source-type=BACKEND_SERVICE \ + --sources=my-backend-service \ + --health-aggregation-policy=my-health-aggregation-policy + +POSITIONAL ARGUMENTS + Health source resource - The name of the health source you want to create. + The arguments in this group can be used to specify the attributes of this + resource. (NOTE) Some attributes are not given arguments in this group but + can be set in other ways. + + To set the project attribute: + ◆ provide the argument health_source on the command line with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + HEALTH_SOURCE + ID of the health source or fully qualified identifier for the health + source. + + To set the health_source attribute: + ▸ provide the argument health_source on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --region=REGION + The name of the Google Compute Engine region. + + To set the region attribute: + ▸ provide the argument health_source on the command line with a + fully specified name; + ▸ provide the argument --region on the command line; + ▸ set the property compute/region. + +REQUIRED FLAGS + --health-aggregation-policy=HEALTH_AGGREGATION_POLICY + URL to the health aggregation policy resource. Must be set. Must be + regional and in the same region as the HealthSource. Can be mutated. + + --sources=SOURCES,[SOURCES,...] + URLs to the source resources. Must be size 1. Must be a BackendService + if the sourceType is BACKEND_SERVICE. The BackendService must have load + balancing scheme INTERNAL or INTERNAL_MANAGED and must be regional and + in the same region as the HealthSource (cross-region deployment for + INTERNAL_MANAGED is not supported). The BackendService may use only + IGs, MIGs, or NEGs of type GCE_VM_IP or GCE_VM_IP_PORT. The + BackendService may not use haPolicy. Can be mutated. + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --description=DESCRIPTION + A textual description of the HealthSource. + + --source-type=SOURCE_TYPE; default="backend-service" + Specifies the type of the HealthSource. The only allowed value is + BACKEND_SERVICE. Must be specified when the HealthSource is created, + and cannot be mutated. SOURCE_TYPE must be (only one value is + supported): backend-service. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the compute/v1 API. The full documentation for this API + can be found at: https://cloud.google.com/compute/ + +NOTES + These variants are also available: + + $ gcloud alpha compute health-sources create + + $ gcloud beta compute health-sources create + diff --git a/gcloud/compute/health-sources/delete b/gcloud/compute/health-sources/delete new file mode 100644 index 000000000..3b820624e --- /dev/null +++ b/gcloud/compute/health-sources/delete @@ -0,0 +1,73 @@ +NAME + gcloud compute health-sources delete - delete a health source + +SYNOPSIS + gcloud compute health-sources delete (HEALTH_SOURCE : --region=REGION) + [--async] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Delete a health source. + +EXAMPLES + To delete a single health source, run the following command: + + $ gcloud compute health-sources delete \ + --region= + +POSITIONAL ARGUMENTS + Health source resource - Name of the health source you want to delete. The + arguments in this group can be used to specify the attributes of this + resource. (NOTE) Some attributes are not given arguments in this group but + can be set in other ways. + + To set the project attribute: + ◆ provide the argument health_source on the command line with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + HEALTH_SOURCE + ID of the health source or fully qualified identifier for the health + source. + + To set the health_source attribute: + ▸ provide the argument health_source on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --region=REGION + The name of the Google Compute Engine region. + + To set the region attribute: + ▸ provide the argument health_source on the command line with a + fully specified name; + ▸ provide the argument --region on the command line; + ▸ set the property compute/region. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the compute/v1 API. The full documentation for this API + can be found at: https://cloud.google.com/compute/ + +NOTES + These variants are also available: + + $ gcloud alpha compute health-sources delete + + $ gcloud beta compute health-sources delete + diff --git a/gcloud/compute/health-sources/describe b/gcloud/compute/health-sources/describe new file mode 100644 index 000000000..0b35818cc --- /dev/null +++ b/gcloud/compute/health-sources/describe @@ -0,0 +1,69 @@ +NAME + gcloud compute health-sources describe - describe a health source + +SYNOPSIS + gcloud compute health-sources describe (HEALTH_SOURCE : --region=REGION) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Describe a health source. + +EXAMPLES + To retrieve a single health source and print its properties, run the + following command: + + $ gcloud compute health-sources describe \ + --region= + +POSITIONAL ARGUMENTS + Health source resource - Name of the health source you want to inspect. + The arguments in this group can be used to specify the attributes of this + resource. (NOTE) Some attributes are not given arguments in this group but + can be set in other ways. + + To set the project attribute: + ◆ provide the argument health_source on the command line with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + HEALTH_SOURCE + ID of the health source or fully qualified identifier for the health + source. + + To set the health_source attribute: + ▸ provide the argument health_source on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --region=REGION + The name of the Google Compute Engine region. + + To set the region attribute: + ▸ provide the argument health_source on the command line with a + fully specified name; + ▸ provide the argument --region on the command line; + ▸ set the property compute/region. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the compute/v1 API. The full documentation for this API + can be found at: https://cloud.google.com/compute/ + +NOTES + These variants are also available: + + $ gcloud alpha compute health-sources describe + + $ gcloud beta compute health-sources describe + diff --git a/gcloud/compute/health-sources/get-health b/gcloud/compute/health-sources/get-health new file mode 100644 index 000000000..e650d84d3 --- /dev/null +++ b/gcloud/compute/health-sources/get-health @@ -0,0 +1,41 @@ +NAME + gcloud compute health-sources get-health - get health status of a health + source + +SYNOPSIS + gcloud compute health-sources get-health HEALTH_SOURCE [--region=REGION] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Get health status of a health source. + +EXAMPLES + To get health status of a single health source, run: + + $ gcloud compute health-sources get-health HEALTH_SOURCE \ + --region=REGION + +POSITIONAL ARGUMENTS + HEALTH_SOURCE + Name of the health source to operate on. + +FLAGS + --region=REGION + Region of the health source to operate on. Overrides the default + compute/region property value for this command invocation. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + These variants are also available: + + $ gcloud alpha compute health-sources get-health + + $ gcloud beta compute health-sources get-health + diff --git a/gcloud/compute/health-sources/help b/gcloud/compute/health-sources/help new file mode 100644 index 000000000..5734db55f --- /dev/null +++ b/gcloud/compute/health-sources/help @@ -0,0 +1,42 @@ +NAME + gcloud compute health-sources - manage health sources + +SYNOPSIS + gcloud compute health-sources COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Manage health sources. + +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 health source. + + delete + Delete a health source. + + describe + Describe a health source. + + get-health + Get health status of a health source. + + list + List health sources. + + update + Update a health source. + +NOTES + These variants are also available: + + $ gcloud alpha compute health-sources + + $ gcloud beta compute health-sources + diff --git a/gcloud/compute/health-sources/list b/gcloud/compute/health-sources/list new file mode 100644 index 000000000..b177792b5 --- /dev/null +++ b/gcloud/compute/health-sources/list @@ -0,0 +1,78 @@ +NAME + gcloud compute health-sources list - list health sources + +SYNOPSIS + gcloud compute health-sources list [NAME ...] [--regexp=REGEXP, -r REGEXP] + [--regions=REGION,[REGION,...]] [--filter=EXPRESSION] [--limit=LIMIT] + [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + List health sources. + +POSITIONAL ARGUMENTS + [NAME ...] + (DEPRECATED) If provided, show details for the specified names and/or + URIs of resources. + + Argument NAME is deprecated. Use --filter="name=( 'NAME' ... )" + instead. + +FLAGS + --regexp=REGEXP, -r REGEXP + (DEPRECATED) Regular expression to filter the names of the results on. + Any names that do not match the entire regular expression will be + filtered out. + + Flag --regexp is deprecated. Use --filter="name~'REGEXP'" instead. + + --regions=REGION,[REGION,...] + If provided, only resources from the given regions are queried. + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + + --uri + Print a list of resource URIs instead of the default output, and change + the command output to a list of URIs. If this flag is used with + --format, the formatting is applied on this URI list. To display URIs + alongside other keys instead, use the uri() transform. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + These variants are also available: + + $ gcloud alpha compute health-sources list + + $ gcloud beta compute health-sources list + diff --git a/gcloud/compute/health-sources/update b/gcloud/compute/health-sources/update new file mode 100644 index 000000000..2802c846d --- /dev/null +++ b/gcloud/compute/health-sources/update @@ -0,0 +1,96 @@ +NAME + gcloud compute health-sources update - update a health source + +SYNOPSIS + gcloud compute health-sources update (HEALTH_SOURCE : --region=REGION) + (--description=DESCRIPTION + --health-aggregation-policy=HEALTH_AGGREGATION_POLICY + --sources=SOURCES,[SOURCES,...]) [--async] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Update a health source. + +EXAMPLES + The following command updates a new health source named "my-health-source": + + $ gcloud compute health-sources update \ + --region= --sources=my-backend-service \ + --health-aggregation-policy=my-health-aggregation-policy + +POSITIONAL ARGUMENTS + Health source resource - The name of the health source you want to create. + The arguments in this group can be used to specify the attributes of this + resource. (NOTE) Some attributes are not given arguments in this group but + can be set in other ways. + + To set the project attribute: + ◆ provide the argument health_source on the command line with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + HEALTH_SOURCE + ID of the health source or fully qualified identifier for the health + source. + + To set the health_source attribute: + ▸ provide the argument health_source on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --region=REGION + The name of the Google Compute Engine region. + + To set the region attribute: + ▸ provide the argument health_source on the command line with a + fully specified name; + ▸ provide the argument --region on the command line; + ▸ set the property compute/region. + +REQUIRED FLAGS + At least one of these must be specified: + + --description=DESCRIPTION + A textual description of the health source. + + --health-aggregation-policy=HEALTH_AGGREGATION_POLICY + URL to the health aggregation policy resource. Must be set. Must be + regional and in the same region as the HealthSource. Can be mutated. + + --sources=SOURCES,[SOURCES,...] + URLs to the source resources. Must be size 1. Must be a + BackendService if the sourceType is BACKEND_SERVICE. The + BackendService must have load balancing scheme INTERNAL or + INTERNAL_MANAGED and must be regional and in the same region as the + HealthSource (cross-region deployment for INTERNAL_MANAGED is not + supported). The BackendService may use only IGs, MIGs, or NEGs of + type GCE_VM_IP or GCE_VM_IP_PORT. The BackendService may not use + haPolicy. Can be mutated. + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the compute/v1 API. The full documentation for this API + can be found at: https://cloud.google.com/compute/ + +NOTES + These variants are also available: + + $ gcloud alpha compute health-sources update + + $ gcloud beta compute health-sources update + diff --git a/gcloud/compute/help b/gcloud/compute/help index aa17c56b1..00d200829 100644 --- a/gcloud/compute/help +++ b/gcloud/compute/help @@ -43,6 +43,9 @@ GROUPS commitments Manage Compute Engine commitments. + composite-health-checks + Manage composite health checks. + diagnose Debugging tools for Compute Engine virtual machine instances. @@ -67,9 +70,18 @@ GROUPS future-reservations Manage Compute Engine future reservations. + global-vm-extension-policies + Compute Engine global VM extension policies. + + health-aggregation-policies + Manage health aggregation policies. + health-checks Read and manipulate health checks for load balanced instances. + health-sources + Manage health sources. + http-health-checks Read and manipulate HTTP health checks for load balanced instances. @@ -88,6 +100,9 @@ GROUPS instances Read and manipulate Compute Engine virtual machine instances. + instant-snapshot-groups + Create, list and delete Compute Engine instant snapshot groups. + instant-snapshots Create, list and delete Compute Engine instant snapshots. @@ -161,6 +176,12 @@ GROUPS resource-policies Manage Compute Engine Resource Policies. + rollout-plans + Read and manipulate Compute Engine Rollout Plans. + + rollouts + Read and manipulate Compute Engine Rollouts. + routers List, create, and delete Compute Engine routers. @@ -233,6 +254,9 @@ GROUPS vpn-tunnels Read and manipulate Compute Engine VPN tunnels. + zone-vm-extension-policies + Compute Engine zone VM extension policies. + zones List Compute Engine zones. diff --git a/gcloud/compute/instances/add-metadata b/gcloud/compute/instances/add-metadata index 0b265250f..bff147d26 100644 --- a/gcloud/compute/instances/add-metadata +++ b/gcloud/compute/instances/add-metadata @@ -30,10 +30,10 @@ DESCRIPTION If you are using this command to manage SSH keys for your project, please note the risks - (https://cloud.google.com/compute/docs/instances/adding-removing-ssh-keys#risks) + (https://docs.cloud.google.com/compute/docs/instances/access-overview#risks) of manual SSH key management as well as the required format for SSH key metadata, available at - https://cloud.google.com/compute/docs/instances/adding-removing-ssh-keys. + https://docs.cloud.google.com/compute/docs/connect/add-ssh-keys. EXAMPLES To add metadata under key important-data to an instance named diff --git a/gcloud/compute/instances/update-from-file b/gcloud/compute/instances/update-from-file index c70dba0f8..57340a734 100644 --- a/gcloud/compute/instances/update-from-file +++ b/gcloud/compute/instances/update-from-file @@ -4,7 +4,7 @@ NAME SYNOPSIS gcloud compute instances update-from-file INSTANCE_NAME - [--minimal-action=MINIMAL_ACTION] + [--discard-local-ssd] [--minimal-action=MINIMAL_ACTION] [--most-disruptive-allowed-action=MOST_DISRUPTIVE_ALLOWED_ACTION] [--source=SOURCE] [--zone=ZONE] [GCLOUD_WIDE_FLAG ...] @@ -26,6 +26,11 @@ POSITIONAL ARGUMENTS https://cloud.google.com/compute/docs/reference/rest/v1/instances FLAGS + --discard-local-ssd + If specified, all local SSDs data attached to this instance will be + discarded. This is only used with most-disruptive-allowed-action set to + RESTART. + --minimal-action=MINIMAL_ACTION If specified, this action or higher level action is performed on the instance irrespective of what action is required for the update to take diff --git a/gcloud/compute/instant-snapshot-groups/create b/gcloud/compute/instant-snapshot-groups/create new file mode 100644 index 000000000..480e000cc --- /dev/null +++ b/gcloud/compute/instant-snapshot-groups/create @@ -0,0 +1,93 @@ +NAME + gcloud compute instant-snapshot-groups create - create a Compute Engine + consistency group of instant snapshots + +SYNOPSIS + gcloud compute instant-snapshot-groups create INSTANT_SNAPSHOT_GROUP_NAME + --source-consistency-group=SOURCE_CONSISTENCY_GROUP + [--region=REGION | --zone=ZONE] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + gcloud compute instant-snapshot-groups create creates an instant snapshot + group of the consistency group. An Instant Snapshot Group is a Point In + Time view of the constituent disks of a Consistency Group, they are stored + in-place as Instant Snapshots on the corresponding disks. + +EXAMPLES + To create an instant snapshot group 'my-instant-snapshot-group' in zone + 'us-east1-a' from a consistency group 'my-consistency-group' in region + 'us-east1', run: $ gcloud compute instant-snapshot-groups create \ + my-instant-snapshot-group --zone us-east1-a \ + --source-consistency-group=regions/us-east1/resourcePolicies/\ + policy1 + +POSITIONAL ARGUMENTS + INSTANT_SNAPSHOT_GROUP_NAME + Name of the instant snapshot group to create. + +REQUIRED FLAGS + --source-consistency-group=SOURCE_CONSISTENCY_GROUP + Specifies the source consistency group resource policy. The value + should be the relative name of the resource policy, in the format + ``regions/REGION/resourcePolicies/POLICY_NAME``. The resource policy is + always in the same region as the source disks. + +OPTIONAL FLAGS + At most one of these can be specified: + + --region=REGION + Region of the instant snapshot group to create. If not specified, you + might be prompted to select a region (interactive mode only). + + To avoid prompting when this flag is omitted, you can set the + compute/region property: + + $ gcloud config set compute/region REGION + + A list of regions can be fetched by running: + + $ gcloud compute regions list + + To unset the property, run: + + $ gcloud config unset compute/region + + Alternatively, the region can be stored in the environment variable + CLOUDSDK_COMPUTE_REGION. + + --zone=ZONE + Zone of the instant snapshot group to create. If not specified and + the compute/zone property isn't set, you might be prompted to select + a zone (interactive mode only). + + To avoid prompting when this flag is omitted, you can set the + compute/zone property: + + $ gcloud config set compute/zone ZONE + + A list of zones can be fetched by running: + + $ gcloud compute zones list + + To unset the property, run: + + $ gcloud config unset compute/zone + + Alternatively, the zone can be stored in the environment variable + CLOUDSDK_COMPUTE_ZONE. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + These variants are also available: + + $ gcloud alpha compute instant-snapshot-groups create + + $ gcloud beta compute instant-snapshot-groups create + diff --git a/gcloud/compute/instant-snapshot-groups/delete b/gcloud/compute/instant-snapshot-groups/delete new file mode 100644 index 000000000..45482bb26 --- /dev/null +++ b/gcloud/compute/instant-snapshot-groups/delete @@ -0,0 +1,75 @@ +NAME + gcloud compute instant-snapshot-groups delete - delete a Compute Engine + consistency group of instant snapshots + +SYNOPSIS + gcloud compute instant-snapshot-groups delete INSTANT_SNAPSHOT_GROUP_NAME + [INSTANT_SNAPSHOT_GROUP_NAME ...] [--region=REGION | --zone=ZONE] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Delete a Compute Engine consistency group of instant snapshots. + +POSITIONAL ARGUMENTS + INSTANT_SNAPSHOT_GROUP_NAME [INSTANT_SNAPSHOT_GROUP_NAME ...] + Names of the instant snapshot groups to delete. + +FLAGS + At most one of these can be specified: + + --region=REGION + Region of the instant snapshot groups to delete. If not specified, + you might be prompted to select a region (interactive mode only). + + To avoid prompting when this flag is omitted, you can set the + compute/region property: + + $ gcloud config set compute/region REGION + + A list of regions can be fetched by running: + + $ gcloud compute regions list + + To unset the property, run: + + $ gcloud config unset compute/region + + Alternatively, the region can be stored in the environment variable + CLOUDSDK_COMPUTE_REGION. + + --zone=ZONE + Zone of the instant snapshot groups to delete. If not specified and + the compute/zone property isn't set, you might be prompted to select + a zone (interactive mode only). + + To avoid prompting when this flag is omitted, you can set the + compute/zone property: + + $ gcloud config set compute/zone ZONE + + A list of zones can be fetched by running: + + $ gcloud compute zones list + + To unset the property, run: + + $ gcloud config unset compute/zone + + Alternatively, the zone can be stored in the environment variable + CLOUDSDK_COMPUTE_ZONE. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + These variants are also available: + + $ gcloud alpha compute instant-snapshot-groups delete + + $ gcloud beta compute instant-snapshot-groups delete + diff --git a/gcloud/compute/instant-snapshot-groups/describe b/gcloud/compute/instant-snapshot-groups/describe new file mode 100644 index 000000000..4416c0b53 --- /dev/null +++ b/gcloud/compute/instant-snapshot-groups/describe @@ -0,0 +1,83 @@ +NAME + gcloud compute instant-snapshot-groups describe - describe a Compute Engine + consistency group of instant snapshots + +SYNOPSIS + gcloud compute instant-snapshot-groups describe INSTANT_SNAPSHOT_GROUP_NAME + [--region=REGION | --zone=ZONE] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + gcloud compute instant-snapshot-groups describe displays all data + associated with a Compute Engine consistency group of instant snapshots in + a project. + +EXAMPLES + To describe the consistency group of instant snapshots + 'instant-snapshot-group-1' in zone 'us-east1-a', run: + + $ gcloud compute instant-snapshot-groups describe \ + instant-snapshot-group-1 --zone=us-east1-a + +POSITIONAL ARGUMENTS + INSTANT_SNAPSHOT_GROUP_NAME + Name of the instant snapshot group to describe. + +FLAGS + At most one of these can be specified: + + --region=REGION + Region of the instant snapshot group to describe. If not specified, + you might be prompted to select a region (interactive mode only). + + To avoid prompting when this flag is omitted, you can set the + compute/region property: + + $ gcloud config set compute/region REGION + + A list of regions can be fetched by running: + + $ gcloud compute regions list + + To unset the property, run: + + $ gcloud config unset compute/region + + Alternatively, the region can be stored in the environment variable + CLOUDSDK_COMPUTE_REGION. + + --zone=ZONE + Zone of the instant snapshot group to describe. If not specified and + the compute/zone property isn't set, you might be prompted to select + a zone (interactive mode only). + + To avoid prompting when this flag is omitted, you can set the + compute/zone property: + + $ gcloud config set compute/zone ZONE + + A list of zones can be fetched by running: + + $ gcloud compute zones list + + To unset the property, run: + + $ gcloud config unset compute/zone + + Alternatively, the zone can be stored in the environment variable + CLOUDSDK_COMPUTE_ZONE. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + These variants are also available: + + $ gcloud alpha compute instant-snapshot-groups describe + + $ gcloud beta compute instant-snapshot-groups describe + diff --git a/gcloud/compute/instant-snapshot-groups/help b/gcloud/compute/instant-snapshot-groups/help new file mode 100644 index 000000000..4abc12433 --- /dev/null +++ b/gcloud/compute/instant-snapshot-groups/help @@ -0,0 +1,37 @@ +NAME + gcloud compute instant-snapshot-groups - create, list and delete Compute + Engine instant snapshot groups + +SYNOPSIS + gcloud compute instant-snapshot-groups COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Create, list and delete Compute Engine instant snapshot groups. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + create + Create a Compute Engine consistency group of instant snapshots. + + delete + Delete a Compute Engine consistency group of instant snapshots. + + describe + Describe a Compute Engine consistency group of instant snapshots. + + list + List Google Compute Engine instant snapshot groups. + +NOTES + These variants are also available: + + $ gcloud alpha compute instant-snapshot-groups + + $ gcloud beta compute instant-snapshot-groups + diff --git a/gcloud/compute/instant-snapshot-groups/list b/gcloud/compute/instant-snapshot-groups/list new file mode 100644 index 000000000..e1c0c2886 --- /dev/null +++ b/gcloud/compute/instant-snapshot-groups/list @@ -0,0 +1,97 @@ +NAME + gcloud compute instant-snapshot-groups list - list Google Compute Engine + instant snapshot groups + +SYNOPSIS + gcloud compute instant-snapshot-groups list + [--regions=[REGION,...] | --zones=[ZONE,...]] [--filter=EXPRESSION] + [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + gcloud compute instant-snapshot-groups list displays all Google Compute + Engine instant snapshot groups in a project. + + By default, instant snapshot groups from all regions and instant snapshot + groups from all zones are listed. The results can be narrowed down by + providing the --regions or --zones flag. + +EXAMPLES + To list all instant snapshot groups in a project in table form, run: + + $ gcloud compute instant-snapshot-groups list + + To list the URIs of all instant snapshot groups in a project, run: + + $ gcloud compute instant-snapshot-groups list --uri + + To list all instant snapshot groups in the us-central1 and europe-west1 + regions, given they are regional resources, run: + + $ gcloud compute instant-snapshot-groups list \ + --filter="region:( europe-west1 us-central1 )" + + To list all instant snapshot groups in zones us-central1-b and + europe-west1-d, given they are zonal resources, run: + + $ gcloud compute instant-snapshot-groups list \ + --filter="zone:( europe-west1-d us-central1-b )" + +FLAGS + At most one of these can be specified: + + --regions=[REGION,...] + If provided, only regional resources are shown. If arguments are + provided, only resources from the given regions are shown. + + --zones=[ZONE,...] + If provided, only zonal resources are shown. If arguments are + provided, only resources from the given zones are shown. + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + + --uri + Print a list of resource URIs instead of the default output, and change + the command output to a list of URIs. If this flag is used with + --format, the formatting is applied on this URI list. To display URIs + alongside other keys instead, use the uri() transform. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + These variants are also available: + + $ gcloud alpha compute instant-snapshot-groups list + + $ gcloud beta compute instant-snapshot-groups list + diff --git a/gcloud/compute/interconnects/groups/create-members b/gcloud/compute/interconnects/groups/create-members index 5f05a4889..f5871be17 100644 --- a/gcloud/compute/interconnects/groups/create-members +++ b/gcloud/compute/interconnects/groups/create-members @@ -28,7 +28,12 @@ EXAMPLES example-interconnect-group --interconnect-type=DEDICATED \ --link-type=LINK_TYPE_ETHERNET_10G_LR --requested-link-count=1 \ --facility=iad-1 --interconnect="name=interconnect1" \ - --interconnect="name=interconnect2" + --interconnect="name=interconnect2,facility=iad-5467" + + Note that facility is required for each member interconnect. + interconnect1's facility is set to the default value iad-1 and + interconnect2's facility is overridden to iad-5467 in the --interconnect + flag. POSITIONAL ARGUMENTS NAME @@ -44,12 +49,9 @@ REQUIRED FLAGS must be specified. These flags are defined as a comma separated list of flag=value pairs. - Example: --interconnect - name=interconnect1,facility=iad-1,description="my - interconnect",link-type=LINK_TYPE_ETHERNET_10G_LR,requested-link-count=1, - interconnect-type=DEDICATED,admin-enabled, - noc-contact-email=noc@google.com,customer-name=customer-name - requested-features=MACSEC:CROSS_SITE_NETWORK + Example: + + --interconnect name=interconnect1,facility=iad-1,description="my interconnect",link-type=LINK_TYPE_ETHERNET_10G_LR,requested-link-count=1,interconnect-type=DEDICATED,admin-enabled,noc-contact-email=noc@google.com,customer-name=customer-name,requested-features=MACSEC:CROSS_SITE_NETWORK Note that for multiple requested-features, use a colon (:) as the delimiter, as the comma is used to separate the flags. Similarly, if @@ -136,6 +138,21 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. +DEFAULTABLE PER-INTERCONNECT FLAGS + All flags except --intent-mismatch-behavior in the OPTIONAL FLAGS section + are defaultable per-interconnect. This means that you can set a default + value by using these flags, or you can override the value for each + interconnect by using the --interconnect flag. + + Furthermore, if the default values for the following flags are not + specified, then they must be specified per-interconnect in the + --interconnect flag: + + ▪ --facility + ▪ --interconnect-type + ▪ --link-type + ▪ --requested-link-count + NOTES These variants are also available: diff --git a/gcloud/compute/migration/image-imports/help b/gcloud/compute/migration/image-imports/help index 2a96f181a..6ce1665dc 100644 --- a/gcloud/compute/migration/image-imports/help +++ b/gcloud/compute/migration/image-imports/help @@ -6,22 +6,22 @@ SYNOPSIS gcloud compute migration image-imports COMMAND [GCLOUD_WIDE_FLAG ...] DESCRIPTION - gcloud alpha migration vms image-imports provides a more robust and better + gcloud compute migration image-imports provides a more robust and better supported method for importing images to Google Compute Engine. Other image-related operations (for example, list) can be done using gcloud compute images, as usual. - The commands use VM Migartion API which supports importing of an image from + The commands use VM Migration API which supports importing of an image from a Google Cloud Storage file (gs://...) to a target project. VM Migration API must be enabled in your project. - gcloud alpha migration vms image-imports create creates an Image Import + gcloud compute migration image-imports create creates an Image Import resource with a nested Image Import Job resource. The Image Import Job resource tracks the image import progress. After the Image Import Job completes, successfully or otherwise, there's no further use for the Image Import resource. - The image is imported to a Google Cloud Project, desginated by the Target + The image is imported to a Google Cloud Project, designated by the Target Project resource. To get a list of Target Projects, run the gcloud alpha migration vms target-projects list command. Use the Google Cloud console to add target project resources. For information on adding target projects, diff --git a/gcloud/compute/network-endpoint-groups/create b/gcloud/compute/network-endpoint-groups/create index b55b719ba..7cd2840d4 100644 --- a/gcloud/compute/network-endpoint-groups/create +++ b/gcloud/compute/network-endpoint-groups/create @@ -48,8 +48,14 @@ FLAGS private-service-connect. --network=NETWORK - Name of the network in which the NEG is created. default project - network is used if unspecified. + Name of the network in which the NEG is created. For + networkEndpointType GCE_VM_IP_PORT, GCE_VM_IP_PORTMAP or + NON_GCP_PRIVATE_IP_PORT, if this field is not specified, a default + network will be used. This field cannot be set for NEGs with + networkEndpointType set to SERVERLESS or PRIVATE_SERVICE_CONNECT and + for global NEGs. + + For all other network endpoint types, this field is required. This is only supported for NEGs with endpoint type gce-vm-ip-port, non-gcp-private-ip-port, gce-vm-ip, private-service-connect, diff --git a/gcloud/compute/networks/peerings/cancel-request-delete b/gcloud/compute/networks/peerings/cancel-request-delete new file mode 100644 index 000000000..73d33ed0a --- /dev/null +++ b/gcloud/compute/networks/peerings/cancel-request-delete @@ -0,0 +1,51 @@ +NAME + gcloud compute networks peerings cancel-request-delete - cancel deletion + request of a Compute Engine network peering + +SYNOPSIS + gcloud compute networks peerings cancel-request-delete NAME + --network=NETWORK [--async] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + gcloud compute networks peerings cancel-request-delete is used to cancel a + pending request to delete a consensus peering between two networks. + +EXAMPLES + To cancel a request to delete a consensus peering with the name + 'peering-name' between the network 'local-network' and the network + 'peer-network', run: + + $ gcloud compute networks peerings cancel-request-delete \ + peering-name --network=local-network + + $ gcloud compute networks peerings cancel-request-delete \ + peering-name --network=peer-network + +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 + These variants are also available: + + $ gcloud alpha compute networks peerings cancel-request-delete + + $ gcloud beta compute networks peerings cancel-request-delete + diff --git a/gcloud/compute/networks/peerings/help b/gcloud/compute/networks/peerings/help index 874d5dfad..73b02d753 100644 --- a/gcloud/compute/networks/peerings/help +++ b/gcloud/compute/networks/peerings/help @@ -22,6 +22,9 @@ GCLOUD WIDE FLAGS COMMANDS COMMAND is one of the following: + cancel-request-delete + Cancel deletion request of a Compute Engine network peering. + create Create a Compute Engine network peering. diff --git a/gcloud/compute/project-info/add-metadata b/gcloud/compute/project-info/add-metadata index bfacfbb4a..f839dd60f 100644 --- a/gcloud/compute/project-info/add-metadata +++ b/gcloud/compute/project-info/add-metadata @@ -20,10 +20,10 @@ DESCRIPTION If you are using this command to manage SSH keys for your project, please note the risks - (https://cloud.google.com/compute/docs/instances/adding-removing-ssh-keys#risks) + (https://docs.cloud.google.com/compute/docs/instances/access-overview#risks) of manual SSH key management as well as the required format for SSH key metadata, available at - https://cloud.google.com/compute/docs/instances/adding-removing-ssh-keys + https://docs.cloud.google.com/compute/docs/connect/add-ssh-keys FLAGS --metadata=KEY=VALUE,[KEY=VALUE,...] diff --git a/gcloud/compute/resource-policies/create/group-placement b/gcloud/compute/resource-policies/create/group-placement index 0afcfe374..c9d94455f 100644 --- a/gcloud/compute/resource-policies/create/group-placement +++ b/gcloud/compute/resource-policies/create/group-placement @@ -4,6 +4,7 @@ NAME SYNOPSIS gcloud compute resource-policies create group-placement NAME + [--accelerator-topology-mode=ACCELERATOR_TOPOLOGY_MODE] [--availability-domain-count=AVAILABILITY_DOMAIN_COUNT] [--collocation=COLLOCATION] [--description=DESCRIPTION] [--gpu-topology=GPU_TOPOLOGY] [--region=REGION] [--vm-count=VM_COUNT] @@ -22,6 +23,16 @@ POSITIONAL ARGUMENTS Name of the resource policy to operate on. FLAGS + --accelerator-topology-mode=ACCELERATOR_TOPOLOGY_MODE + Defines the accelerator connection strategy for accelerator machine + types like TPUs. ACCELERATOR_TOPOLOGY_MODE must be one of: + + AUTO_CONNECT + This creates a static, pre-formed accelerator topology. + PROVISION_ONLY + The interconnected chips are connected on demand. At the time of VM + creation, the chips are not connected. + --availability-domain-count=AVAILABILITY_DOMAIN_COUNT Number of availability domain in the group placement policy. diff --git a/gcloud/compute/resource-policies/create/workload-policy b/gcloud/compute/resource-policies/create/workload-policy index 510b2b896..93d3916d8 100644 --- a/gcloud/compute/resource-policies/create/workload-policy +++ b/gcloud/compute/resource-policies/create/workload-policy @@ -4,6 +4,7 @@ NAME SYNOPSIS gcloud compute resource-policies create workload-policy NAME --type=TYPE + [--accelerator-topology-mode=ACCELERATOR_TOPOLOGY_MODE] [--description=DESCRIPTION] [--region=REGION] [--accelerator-topology=ACCELERATOR_TOPOLOGY | --max-topology-distance=MAX_TOPOLOGY_DISTANCE] @@ -38,6 +39,16 @@ REQUIRED FLAGS latency between VMs. OPTIONAL FLAGS + --accelerator-topology-mode=ACCELERATOR_TOPOLOGY_MODE + Defines the accelerator connection strategy for accelerator machine + types like TPUs. ACCELERATOR_TOPOLOGY_MODE must be one of: + + AUTO_CONNECT + This creates a static, pre-formed accelerator topology. + PROVISION_ONLY + The interconnected chips are connected on demand. At the time of VM + creation, the chips are not connected. + --description=DESCRIPTION An optional, textual description for the backend. diff --git a/gcloud/compute/rollout-plans/create b/gcloud/compute/rollout-plans/create new file mode 100644 index 000000000..ffde2f92e --- /dev/null +++ b/gcloud/compute/rollout-plans/create @@ -0,0 +1,69 @@ +NAME + gcloud compute rollout-plans create - create a Google Compute Engine + rollout plan + +SYNOPSIS + gcloud compute rollout-plans create NAME --waves-from-file=WAVES_FROM_FILE + [--description=DESCRIPTION] + [--location-scope=LOCATION_SCOPE; default="ZONAL"] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Create a Google Compute Engine rollout plan. + +EXAMPLES + To create a rollout plan named my-rollout-plan from a wave definition file + named waves.json, run: + + $ gcloud compute rollout-plans create my-rollout-plan \ + --description="rollout plan description" \ + --location-scope=ZONAL --waves-from-file=waves.json + +POSITIONAL ARGUMENTS + Rollout plan resource - Name of the rollout plan to create. This + represents a Cloud resource. (NOTE) Some attributes are not given + arguments in this group but can be set in other ways. + + To set the project attribute: + ◆ provide the argument name 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. + + NAME + ID of the rollout plan or fully qualified identifier for the rollout + plan. + + To set the name attribute: + ▸ provide the argument name on the command line. + +REQUIRED FLAGS + --waves-from-file=WAVES_FROM_FILE + Path to a YAML or JSON file containing the wave definitions for the + rollout plan. + +OPTIONAL FLAGS + --description=DESCRIPTION + An optional description of this rollout plan. + + --location-scope=LOCATION_SCOPE; default="ZONAL" + The location scope of the rollout plan. LOCATION_SCOPE must be one of: + ZONAL, REGIONAL. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + These variants are also available: + + $ gcloud alpha compute rollout-plans create + + $ gcloud beta compute rollout-plans create + diff --git a/gcloud/compute/rollout-plans/delete b/gcloud/compute/rollout-plans/delete new file mode 100644 index 000000000..dd5dee177 --- /dev/null +++ b/gcloud/compute/rollout-plans/delete @@ -0,0 +1,50 @@ +NAME + gcloud compute rollout-plans delete - delete a Google Compute Engine + rollout plan + +SYNOPSIS + gcloud compute rollout-plans delete NAME [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Delete a Google Compute Engine rollout plan. + +EXAMPLES + To delete a rollout plan named 'my-rollout-plan', run: + + $ gcloud compute rollout-plans delete my-rollout-plan + +POSITIONAL ARGUMENTS + Rollout plan resource - Name of the rollout plan to delete. This + represents a Cloud resource. (NOTE) Some attributes are not given + arguments in this group but can be set in other ways. + + To set the project attribute: + ◆ provide the argument name 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. + + NAME + ID of the rollout plan or fully qualified identifier for the rollout + plan. + + To set the name attribute: + ▸ provide the argument name 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 compute rollout-plans delete + + $ gcloud beta compute rollout-plans delete + diff --git a/gcloud/compute/rollout-plans/describe b/gcloud/compute/rollout-plans/describe new file mode 100644 index 000000000..d4ef5ac7d --- /dev/null +++ b/gcloud/compute/rollout-plans/describe @@ -0,0 +1,54 @@ +NAME + gcloud compute rollout-plans describe - describe a rollout plan + +SYNOPSIS + gcloud compute rollout-plans describe ROLLOUT_PLAN [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Describe a rollout plan. + +EXAMPLES + To retrieve a single rollout plan and print its properties, run the + following command: + + $ gcloud compute rollout-plans describe my-rollout-plan + +POSITIONAL ARGUMENTS + Rollout Plan resource - Name of the rollout plan you want to inspect. This + represents a Cloud resource. (NOTE) Some attributes are not given + arguments in this group but can be set in other ways. + + To set the project attribute: + ◆ provide the argument rollout_plan 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. + + ROLLOUT_PLAN + ID of the Rollout Plan or fully qualified identifier for the Rollout + Plan. + + To set the rollout_plan attribute: + ▸ provide the argument rollout_plan on the command line. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the compute/v1 API. The full documentation for this API + can be found at: https://cloud.google.com/compute/ + +NOTES + These variants are also available: + + $ gcloud alpha compute rollout-plans describe + + $ gcloud beta compute rollout-plans describe + diff --git a/gcloud/compute/rollout-plans/help b/gcloud/compute/rollout-plans/help new file mode 100644 index 000000000..0d83e79e9 --- /dev/null +++ b/gcloud/compute/rollout-plans/help @@ -0,0 +1,37 @@ +NAME + gcloud compute rollout-plans - read and manipulate Compute Engine Rollout + Plans + +SYNOPSIS + gcloud compute rollout-plans COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Read and manipulate Compute Engine Rollout Plans. + +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 Google Compute Engine rollout plan. + + delete + Delete a Google Compute Engine rollout plan. + + describe + Describe a rollout plan. + + list + List Google Compute Engine Rollout Plans. + +NOTES + These variants are also available: + + $ gcloud alpha compute rollout-plans + + $ gcloud beta compute rollout-plans + diff --git a/gcloud/compute/rollout-plans/list b/gcloud/compute/rollout-plans/list new file mode 100644 index 000000000..478ccee9b --- /dev/null +++ b/gcloud/compute/rollout-plans/list @@ -0,0 +1,68 @@ +NAME + gcloud compute rollout-plans list - list Google Compute Engine Rollout + Plans + +SYNOPSIS + gcloud compute rollout-plans list [--filter=EXPRESSION] [--limit=LIMIT] + [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + List Google Compute Engine Rollout Plans in a project. + +EXAMPLES + To list all rollout plans in your project, run: + + $ gcloud compute rollout-plans list + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + + --uri + Print a list of resource URIs instead of the default output, and change + the command output to a list of URIs. If this flag is used with + --format, the formatting is applied on this URI list. To display URIs + alongside other keys instead, use the uri() transform. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the compute/v1 API. The full documentation for this API + can be found at: https://cloud.google.com/compute/ + +NOTES + These variants are also available: + + $ gcloud alpha compute rollout-plans list + + $ gcloud beta compute rollout-plans list + diff --git a/gcloud/compute/rollouts/cancel b/gcloud/compute/rollouts/cancel new file mode 100644 index 000000000..795996aec --- /dev/null +++ b/gcloud/compute/rollouts/cancel @@ -0,0 +1,53 @@ +NAME + gcloud compute rollouts cancel - cancel a Google Compute Engine rollout + +SYNOPSIS + gcloud compute rollouts cancel NAME [--rollback] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Cancel a Google Compute Engine rollout. + +EXAMPLES + To cancel a rollout named 'my-rollout', run: + + $ gcloud compute rollouts cancel my-rollout + +POSITIONAL ARGUMENTS + Rollout resource - Name of the rollout to cancel. This represents a Cloud + resource. (NOTE) Some attributes are not given arguments in this group but + can be set in other ways. + + To set the project attribute: + ◆ provide the argument name 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. + + NAME + ID of the rollout or fully qualified identifier for the rollout. + + To set the name attribute: + ▸ provide the argument name on the command line. + +FLAGS + --rollback + If true, then the ongoing rollout must be rolled back. Else, just + cancel the rollout without taking any further actions. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + These variants are also available: + + $ gcloud alpha compute rollouts cancel + + $ gcloud beta compute rollouts cancel + diff --git a/gcloud/compute/rollouts/delete b/gcloud/compute/rollouts/delete new file mode 100644 index 000000000..ae4272a17 --- /dev/null +++ b/gcloud/compute/rollouts/delete @@ -0,0 +1,48 @@ +NAME + gcloud compute rollouts delete - delete a Google Compute Engine rollout + +SYNOPSIS + gcloud compute rollouts delete NAME [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Delete a Google Compute Engine rollout. + +EXAMPLES + To delete a rollout named 'my-rollout', run: + + $ gcloud compute rollouts delete my-rollout + +POSITIONAL ARGUMENTS + Rollout resource - Name of the rollout to delete. This represents a Cloud + resource. (NOTE) Some attributes are not given arguments in this group but + can be set in other ways. + + To set the project attribute: + ◆ provide the argument name 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. + + NAME + ID of the rollout or fully qualified identifier for the rollout. + + To set the name attribute: + ▸ provide the argument name 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 compute rollouts delete + + $ gcloud beta compute rollouts delete + diff --git a/gcloud/compute/rollouts/describe b/gcloud/compute/rollouts/describe new file mode 100644 index 000000000..66f6eee4d --- /dev/null +++ b/gcloud/compute/rollouts/describe @@ -0,0 +1,53 @@ +NAME + gcloud compute rollouts describe - describe a rollout + +SYNOPSIS + gcloud compute rollouts describe ROLLOUT [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Describe a rollout. + +EXAMPLES + To retrieve a single rollout and print its properties, run the following + command: + + $ gcloud compute rollouts describe my-rollout + +POSITIONAL ARGUMENTS + Rollout resource - Name of the rollout you want to inspect. This + represents a Cloud resource. (NOTE) Some attributes are not given + arguments in this group but can be set in other ways. + + To set the project attribute: + ◆ provide the argument rollout 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. + + ROLLOUT + ID of the Rollout or fully qualified identifier for the Rollout. + + To set the rollout attribute: + ▸ provide the argument rollout on the command line. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the compute/v1 API. The full documentation for this API + can be found at: https://cloud.google.com/compute/ + +NOTES + These variants are also available: + + $ gcloud alpha compute rollouts describe + + $ gcloud beta compute rollouts describe + diff --git a/gcloud/compute/rollouts/help b/gcloud/compute/rollouts/help new file mode 100644 index 000000000..86ab0524d --- /dev/null +++ b/gcloud/compute/rollouts/help @@ -0,0 +1,36 @@ +NAME + gcloud compute rollouts - read and manipulate Compute Engine Rollouts + +SYNOPSIS + gcloud compute rollouts COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Read and manipulate Compute Engine Rollouts. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + cancel + Cancel a Google Compute Engine rollout. + + delete + Delete a Google Compute Engine rollout. + + describe + Describe a rollout. + + list + List Google Compute Engine Rollouts. + +NOTES + These variants are also available: + + $ gcloud alpha compute rollouts + + $ gcloud beta compute rollouts + diff --git a/gcloud/compute/rollouts/list b/gcloud/compute/rollouts/list new file mode 100644 index 000000000..ca25452fc --- /dev/null +++ b/gcloud/compute/rollouts/list @@ -0,0 +1,67 @@ +NAME + gcloud compute rollouts list - list Google Compute Engine Rollouts + +SYNOPSIS + gcloud compute rollouts list [--filter=EXPRESSION] [--limit=LIMIT] + [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + List Google Compute Engine Rollouts in a project. + +EXAMPLES + To list all rollouts in your project, run: + + $ gcloud compute rollouts list + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + + --uri + Print a list of resource URIs instead of the default output, and change + the command output to a list of URIs. If this flag is used with + --format, the formatting is applied on this URI list. To display URIs + alongside other keys instead, use the uri() transform. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the compute/v1 API. The full documentation for this API + can be found at: https://cloud.google.com/compute/ + +NOTES + These variants are also available: + + $ gcloud alpha compute rollouts list + + $ gcloud beta compute rollouts list + diff --git a/gcloud/compute/snapshots/help b/gcloud/compute/snapshots/help index 67f149128..9fa53a2b4 100644 --- a/gcloud/compute/snapshots/help +++ b/gcloud/compute/snapshots/help @@ -56,7 +56,7 @@ COMMANDS Update a Compute Engine snapshot. update-kms-key - Update the KMS key of a Compute Engine snapshot. + Update the KMS key of a Compute Engine standard or archive snapshot. NOTES These variants are also available: diff --git a/gcloud/compute/snapshots/update-kms-key b/gcloud/compute/snapshots/update-kms-key index d2f6e6b47..6786fc7ed 100644 --- a/gcloud/compute/snapshots/update-kms-key +++ b/gcloud/compute/snapshots/update-kms-key @@ -1,6 +1,6 @@ NAME gcloud compute snapshots update-kms-key - update the KMS key of a Compute - Engine snapshot + Engine standard or archive snapshot SYNOPSIS gcloud compute snapshots update-kms-key SNAPSHOT_NAME [--region=REGION] @@ -9,9 +9,9 @@ SYNOPSIS [GCLOUD_WIDE_FLAG ...] DESCRIPTION - ▪ gcloud compute snapshots update-kms-key updates the KMS key of a - Compute Engine persistent snapshot by rotating it to the primary - version of the key or to the primary version of a new KMS key. + gcloud compute snapshots update-kms-key updates the KMS key of a Compute + Engine standard or archive snapshot by rotating it to the primary version + of the key or to the primary version of a new KMS key. EXAMPLES To update the KMS key of a snapshot named example-snapshot-1, run: diff --git a/gcloud/compute/zone-vm-extension-policies/create b/gcloud/compute/zone-vm-extension-policies/create new file mode 100644 index 000000000..0510aebae --- /dev/null +++ b/gcloud/compute/zone-vm-extension-policies/create @@ -0,0 +1,139 @@ +NAME + gcloud compute zone-vm-extension-policies create - create a Compute Engine + zone VM extension policy + +SYNOPSIS + gcloud compute zone-vm-extension-policies create NAME + --extensions=EXTENSION_NAME,[...] [--config=KEY=VALUE,[KEY=VALUE,...]] + [--config-from-file=KEY=FILE_PATH,[...]] [--description=DESCRIPTION] + [--inclusion-labels=INCLUSION_LABELS] + [--priority=PRIORITY; default=1000] + [--version=KEY=VALUE,[KEY=VALUE,...]] [--zone=ZONE] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Create a Compute Engine zone VM extension policy. + +EXAMPLES + To create a zone VM extension policy, run: + + $ gcloud compute zone-vm-extension-policies create \ + test-policy-name --description="test policy" \ + --extensions=extension1,extension2 \ + --version=extension1=version1,extension2=version2 \ + --config=extension1="config1",extension2="config2" \ + --inclusion-labels=env=prod \ + --inclusion-labels=env=preprod,workload=load-test \ + --priority=1000 + + Available extensions: + ops-agent + google-cloud-sap-extension + google-cloud-workload-extension + +POSITIONAL ARGUMENTS + NAME + Name of the zone vm extension policy to create. + +REQUIRED FLAGS + --extensions=EXTENSION_NAME,[...] + One or more extensions to be added to the policy. + +OPTIONAL FLAGS + --config=KEY=VALUE,[KEY=VALUE,...] + A comma separated key:value list where the key is the extension name + and the value is the desired config for the given extension. The + extension name must be one of the extensions specified in the + --extensions flag. + + E.g. --config=filestore='filestore config',ops-agent='ops agent config' + + Raises: ArgumentTypeError: If the extension name is not specified in + the --extensions flag. + + --config-from-file=KEY=FILE_PATH,[...] + Same as --config except that the value for the entry will be read from + a local file. The extension name must be one of the extensions + specified in the --extensions flag. + + It is an error to specify the same extension in both --config and + --config-from-file. + + --description=DESCRIPTION + An optional text description for the extension policy. + + --inclusion-labels=INCLUSION_LABELS + A list of inclusion labels to select the target VMs. + + The expected format for a single selector is "key1=value1,key2=value2". + A VM is selected if it has ALL the inclusion labels. + + When the option is specified multiple times, it assumes a logical OR + between the selectors. + + For example, if the inclusion labels are ["env=prod,workload=frontend", + "workload=backend"], the following VMs will be selected: + ◆ VM1: env=prod, workload=frontend, something=else + ◆ VM2: env=prod, workload=backend But not: + ◆ VM3: env=prod + + If not specified, ALL VMs in the zone will be selected. + + --priority=PRIORITY; default=1000 + The priority of the policy. Lower the number, higher the priority. When + two policies try to apply the same extension to a VM, the policy with + higher priority takes precedence. If the priorities are the same, the + policy with the more recent update timestamp takes precedence. If a + policy is deleted, the extension remains installed on the VM if a + lower-priority policy still applies. + + Range from 0 to 65535. Default is 1000. + + --version=KEY=VALUE,[KEY=VALUE,...] + A comma separated key:value list where the key is the extension name + and the value is the desired version for the given extension. The + extension name must be one of the extensions specified in the + --extensions flag. If no version is specified for an extension, the + latest version will be used and will be upgraded automatically. + + E.g. --version=filestore=123ABC,ops-agent=456DEF + + Raises: ArgumentTypeError: If the extension name is not specified in + the --extensions flag. + + --zone=ZONE + Zone of the zone vm extension policy to create. If not specified and + the compute/zone property isn't set, you might be prompted to select a + zone (interactive mode only). + + To avoid prompting when this flag is omitted, you can set the + compute/zone property: + + $ gcloud config set compute/zone ZONE + + A list of zones can be fetched by running: + + $ gcloud compute zones list + + To unset the property, run: + + $ gcloud config unset compute/zone + + Alternatively, the zone can be stored in the environment variable + CLOUDSDK_COMPUTE_ZONE. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + These variants are also available: + + $ gcloud alpha compute zone-vm-extension-policies create + + $ gcloud beta compute zone-vm-extension-policies create + diff --git a/gcloud/compute/zone-vm-extension-policies/delete b/gcloud/compute/zone-vm-extension-policies/delete new file mode 100644 index 000000000..9df5e08de --- /dev/null +++ b/gcloud/compute/zone-vm-extension-policies/delete @@ -0,0 +1,57 @@ +NAME + gcloud compute zone-vm-extension-policies delete - delete a Compute Engine + zone VM extension policy + +SYNOPSIS + gcloud compute zone-vm-extension-policies delete NAME [--zone=ZONE] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Delete a Compute Engine zone VM extension policy. + +EXAMPLES + To delete a zone VM extension policy, run: + + $ gcloud compute zone-vm-extension-policies delete test-policy-name + +POSITIONAL ARGUMENTS + NAME + Name of the zone vm extension policy to delete. + +FLAGS + --zone=ZONE + Zone of the zone vm extension policy to delete. If not specified and + the compute/zone property isn't set, you might be prompted to select a + zone (interactive mode only). + + To avoid prompting when this flag is omitted, you can set the + compute/zone property: + + $ gcloud config set compute/zone ZONE + + A list of zones can be fetched by running: + + $ gcloud compute zones list + + To unset the property, run: + + $ gcloud config unset compute/zone + + Alternatively, the zone can be stored in the environment variable + CLOUDSDK_COMPUTE_ZONE. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + These variants are also available: + + $ gcloud alpha compute zone-vm-extension-policies delete + + $ gcloud beta compute zone-vm-extension-policies delete + diff --git a/gcloud/compute/zone-vm-extension-policies/describe b/gcloud/compute/zone-vm-extension-policies/describe new file mode 100644 index 000000000..0287cdb3c --- /dev/null +++ b/gcloud/compute/zone-vm-extension-policies/describe @@ -0,0 +1,57 @@ +NAME + gcloud compute zone-vm-extension-policies describe - describe a Compute + Engine zone VM extension policy + +SYNOPSIS + gcloud compute zone-vm-extension-policies describe NAME [--zone=ZONE] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Describe a Compute Engine zone VM extension policy. + +EXAMPLES + To describe a zone VM extension policy, run: + + $ gcloud compute zone-vm-extension-policies describe test-policy-name + +POSITIONAL ARGUMENTS + NAME + Name of the zone vm extension policy to describe. + +FLAGS + --zone=ZONE + Zone of the zone vm extension policy to describe. If not specified and + the compute/zone property isn't set, you might be prompted to select a + zone (interactive mode only). + + To avoid prompting when this flag is omitted, you can set the + compute/zone property: + + $ gcloud config set compute/zone ZONE + + A list of zones can be fetched by running: + + $ gcloud compute zones list + + To unset the property, run: + + $ gcloud config unset compute/zone + + Alternatively, the zone can be stored in the environment variable + CLOUDSDK_COMPUTE_ZONE. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + These variants are also available: + + $ gcloud alpha compute zone-vm-extension-policies describe + + $ gcloud beta compute zone-vm-extension-policies describe + diff --git a/gcloud/compute/zone-vm-extension-policies/help b/gcloud/compute/zone-vm-extension-policies/help new file mode 100644 index 000000000..6768b19e3 --- /dev/null +++ b/gcloud/compute/zone-vm-extension-policies/help @@ -0,0 +1,40 @@ +NAME + gcloud compute zone-vm-extension-policies - compute Engine zone VM + extension policies + +SYNOPSIS + gcloud compute zone-vm-extension-policies COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Compute Engine zone VM extension policies. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + create + Create a Compute Engine zone VM extension policy. + + delete + Delete a Compute Engine zone VM extension policy. + + describe + Describe a Compute Engine zone VM extension policy. + + list + List Compute Engine zone VM extension policies. + + update + Update a Compute Engine zone VM extension policy. + +NOTES + These variants are also available: + + $ gcloud alpha compute zone-vm-extension-policies + + $ gcloud beta compute zone-vm-extension-policies + diff --git a/gcloud/compute/zone-vm-extension-policies/list b/gcloud/compute/zone-vm-extension-policies/list new file mode 100644 index 000000000..77bb8b0ef --- /dev/null +++ b/gcloud/compute/zone-vm-extension-policies/list @@ -0,0 +1,68 @@ +NAME + gcloud compute zone-vm-extension-policies list - list Compute Engine zone + VM extension policies + +SYNOPSIS + gcloud compute zone-vm-extension-policies list --zone=ZONE + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + List Compute Engine zone VM extension policies. + +EXAMPLES + To list all zone VM extension policy, run: + + $ gcloud compute zone-vm-extension-policies list --zone= + +REQUIRED FLAGS + --zone=ZONE + The zone to list the extension policies from. + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + + --uri + Print a list of resource URIs instead of the default output, and change + the command output to a list of URIs. If this flag is used with + --format, the formatting is applied on this URI list. To display URIs + alongside other keys instead, use the uri() transform. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + These variants are also available: + + $ gcloud alpha compute zone-vm-extension-policies list + + $ gcloud beta compute zone-vm-extension-policies list + diff --git a/gcloud/compute/zone-vm-extension-policies/update b/gcloud/compute/zone-vm-extension-policies/update new file mode 100644 index 000000000..c6785a8f5 --- /dev/null +++ b/gcloud/compute/zone-vm-extension-policies/update @@ -0,0 +1,134 @@ +NAME + gcloud compute zone-vm-extension-policies update - update a Compute Engine + zone VM extension policy + +SYNOPSIS + gcloud compute zone-vm-extension-policies update NAME + --extensions=EXTENSION_NAME,[...] [--config=KEY=VALUE,[KEY=VALUE,...]] + [--config-from-file=KEY=FILE_PATH,[...]] [--description=DESCRIPTION] + [--inclusion-labels=INCLUSION_LABELS] + [--priority=PRIORITY; default=1000] + [--version=KEY=VALUE,[KEY=VALUE,...]] [--zone=ZONE] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Update a Compute Engine zone VM extension policy. + +EXAMPLES + To update a zone VM extension policy, run: + + $ gcloud compute zone-vm-extension-policies update \ + test-policy-name --description="test policy" \ + --extensions=extension1,extension2 \ + --version=extension1=version1,extension2=version2 \ + --config=extension1="config1",extension2="config2" \ + --inclusion-labels=env=prod \ + --inclusion-labels=env=preprod,workload=load-test \ + --priority=1000 + +POSITIONAL ARGUMENTS + NAME + Name of the zone vm extension policy to update. + +REQUIRED FLAGS + --extensions=EXTENSION_NAME,[...] + One or more extensions to be added to the policy. + +OPTIONAL FLAGS + --config=KEY=VALUE,[KEY=VALUE,...] + A comma separated key:value list where the key is the extension name + and the value is the desired config for the given extension. The + extension name must be one of the extensions specified in the + --extensions flag. + + E.g. --config=filestore='filestore config',ops-agent='ops agent config' + + Raises: ArgumentTypeError: If the extension name is not specified in + the --extensions flag. + + --config-from-file=KEY=FILE_PATH,[...] + Same as --config except that the value for the entry will be read from + a local file. The extension name must be one of the extensions + specified in the --extensions flag. + + It is an error to specify the same extension in both --config and + --config-from-file. + + --description=DESCRIPTION + An optional text description for the extension policy. + + --inclusion-labels=INCLUSION_LABELS + A list of inclusion labels to select the target VMs. + + The expected format for a single selector is "key1=value1,key2=value2". + A VM is selected if it has ALL the inclusion labels. + + When the option is specified multiple times, it assumes a logical OR + between the selectors. + + For example, if the inclusion labels are ["env=prod,workload=frontend", + "workload=backend"], the following VMs will be selected: + ◆ VM1: env=prod, workload=frontend, something=else + ◆ VM2: env=prod, workload=backend But not: + ◆ VM3: env=prod + + If not specified, ALL VMs in the zone will be selected. + + --priority=PRIORITY; default=1000 + The priority of the policy. Lower the number, higher the priority. When + two policies try to apply the same extension to a VM, the policy with + higher priority takes precedence. If the priorities are the same, the + policy with the more recent update timestamp takes precedence. If a + policy is deleted, the extension remains installed on the VM if a + lower-priority policy still applies. + + Range from 0 to 65535. Default is 1000. + + --version=KEY=VALUE,[KEY=VALUE,...] + A comma separated key:value list where the key is the extension name + and the value is the desired version for the given extension. The + extension name must be one of the extensions specified in the + --extensions flag. If no version is specified for an extension, the + latest version will be used and will be upgraded automatically. + + E.g. --version=filestore=123ABC,ops-agent=456DEF + + Raises: ArgumentTypeError: If the extension name is not specified in + the --extensions flag. + + --zone=ZONE + Zone of the zone vm extension policy to update. If not specified and + the compute/zone property isn't set, you might be prompted to select a + zone (interactive mode only). + + To avoid prompting when this flag is omitted, you can set the + compute/zone property: + + $ gcloud config set compute/zone ZONE + + A list of zones can be fetched by running: + + $ gcloud compute zones list + + To unset the property, run: + + $ gcloud config unset compute/zone + + Alternatively, the zone can be stored in the environment variable + CLOUDSDK_COMPUTE_ZONE. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + These variants are also available: + + $ gcloud alpha compute zone-vm-extension-policies update + + $ gcloud beta compute zone-vm-extension-policies update + diff --git a/gcloud/config/get b/gcloud/config/get index 5ce2ea0b3..d55fab1b7 100644 --- a/gcloud/config/get +++ b/gcloud/config/get @@ -208,6 +208,10 @@ AVAILABLE PROPERTIES Overrides API endpoint for gcloud apphub command group. Defaults to https://apphub.googleapis.com/ + appoptimize + Overrides API endpoint for gcloud app-optimize command group. + Defaults to https://appoptimize.googleapis.com/ + artifactregistry Overrides API endpoint for gcloud artifacts command group. Defaults to https://artifactregistry.googleapis.com/ @@ -384,7 +388,6 @@ AVAILABLE PROPERTIES faultinjectiontesting Overrides API endpoint for gcloud fault-injection command group. - Defaults to https://faultinjectiontesting.googleapis.com/ faulttesting Overrides API endpoint for gcloud fault-testing command group. @@ -446,10 +449,6 @@ AVAILABLE PROPERTIES Overrides API endpoint for gcloud ml language command group. Defaults to https://language.googleapis.com/ - lifesciences - Overrides API endpoint for gcloud lifesciences command group. - Defaults to https://lifesciences.googleapis.com/ - logging Overrides API endpoint for gcloud logging command group. Defaults to https://logging.googleapis.com/ @@ -570,6 +569,10 @@ AVAILABLE PROPERTIES Overrides API endpoint for gcloud service-directory command group. Defaults to https://servicedirectory.googleapis.com/ + servicehealth + Overrides API endpoint for gcloud servicehealth command group. + Defaults to https://servicehealth.googleapis.com/ + servicemanagement Overrides API endpoint for gcloud endpoints command group. Defaults to https://servicemanagement.googleapis.com/ @@ -1049,12 +1052,6 @@ AVAILABLE PROPERTIES suggest If True, add command line suggestions based on history. - lifesciences - location - Default location to use when working with Cloud Life Sciences - resources. When a --location flag is required but not provided, the - command will fall back to this value. - looker region Default region to use when working with Cloud Looker resources. diff --git a/gcloud/config/help b/gcloud/config/help index 3ab9de2ee..1ddfc40b7 100644 --- a/gcloud/config/help +++ b/gcloud/config/help @@ -240,6 +240,10 @@ AVAILABLE PROPERTIES Overrides API endpoint for gcloud apphub command group. Defaults to https://apphub.googleapis.com/ + appoptimize + Overrides API endpoint for gcloud app-optimize command group. + Defaults to https://appoptimize.googleapis.com/ + artifactregistry Overrides API endpoint for gcloud artifacts command group. Defaults to https://artifactregistry.googleapis.com/ @@ -416,7 +420,6 @@ AVAILABLE PROPERTIES faultinjectiontesting Overrides API endpoint for gcloud fault-injection command group. - Defaults to https://faultinjectiontesting.googleapis.com/ faulttesting Overrides API endpoint for gcloud fault-testing command group. @@ -478,10 +481,6 @@ AVAILABLE PROPERTIES Overrides API endpoint for gcloud ml language command group. Defaults to https://language.googleapis.com/ - lifesciences - Overrides API endpoint for gcloud lifesciences command group. - Defaults to https://lifesciences.googleapis.com/ - logging Overrides API endpoint for gcloud logging command group. Defaults to https://logging.googleapis.com/ @@ -602,6 +601,10 @@ AVAILABLE PROPERTIES Overrides API endpoint for gcloud service-directory command group. Defaults to https://servicedirectory.googleapis.com/ + servicehealth + Overrides API endpoint for gcloud servicehealth command group. + Defaults to https://servicehealth.googleapis.com/ + servicemanagement Overrides API endpoint for gcloud endpoints command group. Defaults to https://servicemanagement.googleapis.com/ @@ -1081,12 +1084,6 @@ AVAILABLE PROPERTIES suggest If True, add command line suggestions based on history. - lifesciences - location - Default location to use when working with Cloud Life Sciences - resources. When a --location flag is required but not provided, the - command will fall back to this value. - looker region Default region to use when working with Cloud Looker resources. diff --git a/gcloud/config/list b/gcloud/config/list index 85a0a9e28..5d000475d 100644 --- a/gcloud/config/list +++ b/gcloud/config/list @@ -252,6 +252,10 @@ AVAILABLE PROPERTIES Overrides API endpoint for gcloud apphub command group. Defaults to https://apphub.googleapis.com/ + appoptimize + Overrides API endpoint for gcloud app-optimize command group. + Defaults to https://appoptimize.googleapis.com/ + artifactregistry Overrides API endpoint for gcloud artifacts command group. Defaults to https://artifactregistry.googleapis.com/ @@ -428,7 +432,6 @@ AVAILABLE PROPERTIES faultinjectiontesting Overrides API endpoint for gcloud fault-injection command group. - Defaults to https://faultinjectiontesting.googleapis.com/ faulttesting Overrides API endpoint for gcloud fault-testing command group. @@ -490,10 +493,6 @@ AVAILABLE PROPERTIES Overrides API endpoint for gcloud ml language command group. Defaults to https://language.googleapis.com/ - lifesciences - Overrides API endpoint for gcloud lifesciences command group. - Defaults to https://lifesciences.googleapis.com/ - logging Overrides API endpoint for gcloud logging command group. Defaults to https://logging.googleapis.com/ @@ -614,6 +613,10 @@ AVAILABLE PROPERTIES Overrides API endpoint for gcloud service-directory command group. Defaults to https://servicedirectory.googleapis.com/ + servicehealth + Overrides API endpoint for gcloud servicehealth command group. + Defaults to https://servicehealth.googleapis.com/ + servicemanagement Overrides API endpoint for gcloud endpoints command group. Defaults to https://servicemanagement.googleapis.com/ @@ -1093,12 +1096,6 @@ AVAILABLE PROPERTIES suggest If True, add command line suggestions based on history. - lifesciences - location - Default location to use when working with Cloud Life Sciences - resources. When a --location flag is required but not provided, the - command will fall back to this value. - looker region Default region to use when working with Cloud Looker resources. diff --git a/gcloud/config/set b/gcloud/config/set index 7c422b0d4..346bb6b50 100644 --- a/gcloud/config/set +++ b/gcloud/config/set @@ -255,6 +255,10 @@ AVAILABLE PROPERTIES Overrides API endpoint for gcloud apphub command group. Defaults to https://apphub.googleapis.com/ + appoptimize + Overrides API endpoint for gcloud app-optimize command group. + Defaults to https://appoptimize.googleapis.com/ + artifactregistry Overrides API endpoint for gcloud artifacts command group. Defaults to https://artifactregistry.googleapis.com/ @@ -431,7 +435,6 @@ AVAILABLE PROPERTIES faultinjectiontesting Overrides API endpoint for gcloud fault-injection command group. - Defaults to https://faultinjectiontesting.googleapis.com/ faulttesting Overrides API endpoint for gcloud fault-testing command group. @@ -493,10 +496,6 @@ AVAILABLE PROPERTIES Overrides API endpoint for gcloud ml language command group. Defaults to https://language.googleapis.com/ - lifesciences - Overrides API endpoint for gcloud lifesciences command group. - Defaults to https://lifesciences.googleapis.com/ - logging Overrides API endpoint for gcloud logging command group. Defaults to https://logging.googleapis.com/ @@ -617,6 +616,10 @@ AVAILABLE PROPERTIES Overrides API endpoint for gcloud service-directory command group. Defaults to https://servicedirectory.googleapis.com/ + servicehealth + Overrides API endpoint for gcloud servicehealth command group. + Defaults to https://servicehealth.googleapis.com/ + servicemanagement Overrides API endpoint for gcloud endpoints command group. Defaults to https://servicemanagement.googleapis.com/ @@ -1096,12 +1099,6 @@ AVAILABLE PROPERTIES suggest If True, add command line suggestions based on history. - lifesciences - location - Default location to use when working with Cloud Life Sciences - resources. When a --location flag is required but not provided, the - command will fall back to this value. - looker region Default region to use when working with Cloud Looker resources. diff --git a/gcloud/config/unset b/gcloud/config/unset index 4cb246158..df473f93a 100644 --- a/gcloud/config/unset +++ b/gcloud/config/unset @@ -216,6 +216,10 @@ AVAILABLE PROPERTIES Overrides API endpoint for gcloud apphub command group. Defaults to https://apphub.googleapis.com/ + appoptimize + Overrides API endpoint for gcloud app-optimize command group. + Defaults to https://appoptimize.googleapis.com/ + artifactregistry Overrides API endpoint for gcloud artifacts command group. Defaults to https://artifactregistry.googleapis.com/ @@ -392,7 +396,6 @@ AVAILABLE PROPERTIES faultinjectiontesting Overrides API endpoint for gcloud fault-injection command group. - Defaults to https://faultinjectiontesting.googleapis.com/ faulttesting Overrides API endpoint for gcloud fault-testing command group. @@ -454,10 +457,6 @@ AVAILABLE PROPERTIES Overrides API endpoint for gcloud ml language command group. Defaults to https://language.googleapis.com/ - lifesciences - Overrides API endpoint for gcloud lifesciences command group. - Defaults to https://lifesciences.googleapis.com/ - logging Overrides API endpoint for gcloud logging command group. Defaults to https://logging.googleapis.com/ @@ -578,6 +577,10 @@ AVAILABLE PROPERTIES Overrides API endpoint for gcloud service-directory command group. Defaults to https://servicedirectory.googleapis.com/ + servicehealth + Overrides API endpoint for gcloud servicehealth command group. + Defaults to https://servicehealth.googleapis.com/ + servicemanagement Overrides API endpoint for gcloud endpoints command group. Defaults to https://servicemanagement.googleapis.com/ @@ -1057,12 +1060,6 @@ AVAILABLE PROPERTIES suggest If True, add command line suggestions based on history. - lifesciences - location - Default location to use when working with Cloud Life Sciences - resources. When a --location flag is required but not provided, the - command will fall back to this value. - looker region Default region to use when working with Cloud Looker resources. diff --git a/gcloud/container/clusters/create b/gcloud/container/clusters/create index 010805d00..abb9dab13 100644 --- a/gcloud/container/clusters/create +++ b/gcloud/container/clusters/create @@ -27,6 +27,7 @@ SYNOPSIS [--cluster-version=CLUSTER_VERSION] [--confidential-node-type=CONFIDENTIAL_NODE_TYPE] [--containerd-config-from-file=PATH_TO_FILE] + [--control-plane-egress=CONTROL_PLANE_EGRESS] [--create-subnetwork=[KEY=VALUE,...]] [--data-cache-count=DATA_CACHE_COUNT] [--database-encryption-key=DATABASE_ENCRYPTION_KEY] @@ -74,6 +75,7 @@ SYNOPSIS [--min-cpu-platform=PLATFORM] [--monitoring=[COMPONENT,...]] [--network=NETWORK] [--network-performance-configs=[PROPERTY1=VALUE1,...]] + [--node-architecture-taint-behavior=NODE_ARCHITECTURE_TAINT_BEHAVIOR] [--node-labels=[NODE_LABEL,...]] [--node-locations=ZONE,[ZONE,...]] [--node-taints=[NODE_TAINT,...]] [--node-version=NODE_VERSION] [--notification-config=[pubsub=ENABLED|DISABLED, @@ -110,13 +112,12 @@ SYNOPSIS | --disable-dataplane-v2-flow-observability | --enable-dataplane-v2-flow-observability] [--disable-dataplane-v2-metrics | --enable-dataplane-v2-metrics] - [[--enable-autoprovisioning - : --autoprovisioning-config-file=PATH_TO_FILE - | [--max-cpu=MAX_CPU --max-memory=MAX_MEMORY - : --autoprovisioning-image-type=AUTOPROVISIONING_IMAGE_TYPE + [--disable-pod-snapshots | --enable-pod-snapshots] + [--enable-autoprovisioning --autoprovisioning-config-file=PATH_TO_FILE + | --autoprovisioning-image-type=AUTOPROVISIONING_IMAGE_TYPE --autoprovisioning-locations=ZONE,[ZONE,...] - --autoprovisioning-min-cpu-platform=PLATFORM --min-cpu=MIN_CPU - --min-memory=MIN_MEMORY + --autoprovisioning-min-cpu-platform=PLATFORM --max-cpu=MAX_CPU + --max-memory=MAX_MEMORY --min-cpu=MIN_CPU --min-memory=MIN_MEMORY --autoprovisioning-max-surge-upgrade=AUTOPROVISIONING_MAX_SURGE_UPGRADE --autoprovisioning-max-unavailable-upgrade=AUTOPROVISIONING_MAX_UNAVAILABLE_UPGRADE --autoprovisioning-node-pool-soak-duration=AUTOPROVISIONING_NODE_POOL_SOAK_DURATION --autoprovisioning-standard-rollout-policy=[batch-node-count=BATCH_NODE_COUNT, batch-percent=BATCH_NODE_PERCENTAGE, batch-soak-duration=BATCH_SOAK_DURATION,...] @@ -127,7 +128,7 @@ SYNOPSIS --enable-autoprovisioning-autorepair --enable-autoprovisioning-autoupgrade [--max-accelerator=[type=TYPE,count=COUNT,...] - : --min-accelerator=[type=TYPE,count=COUNT,...]]]]] + : --min-accelerator=[type=TYPE,count=COUNT,...]]] [--enable-autoscaling --location-policy=LOCATION_POLICY --max-nodes=MAX_NODES --min-nodes=MIN_NODES --total-max-nodes=TOTAL_MAX_NODES --total-min-nodes=TOTAL_MIN_NODES] @@ -493,6 +494,23 @@ FLAGS Use a full or relative path to a local file containing the value of containerd_config. + --control-plane-egress=CONTROL_PLANE_EGRESS + Configures the egress policy for the GKE control plane to control + outbound traffic from the kube-apiserver. CONTROL_PLANE_EGRESS must be + one of: + + NONE + (Recommended) Provides maximum security. This mode removes the + control plane's public IP address and blocks all outbound traffic + from the kube-apiserver by default, preventing unexpected data + exfiltration. Webhooks that use clientConfig.url will be disabled. + Essential GKE-managed services are still permitted to function via + an internal allowlist. + VIA_CONTROL_PLANE + (Default) Maintains backward compatibility. The control plane + retains its public IP address and allows egress traffic from the + kube-apiserver. + --create-subnetwork=[KEY=VALUE,...] Create a new subnetwork for the cluster. The name and range of the subnetwork can be customized via optional 'name' and 'range' key-value @@ -1133,6 +1151,26 @@ FLAGS https://cloud.google.com/compute/docs/networking/configure-vm-with-high-bandwidth-configuration for more information. + --node-architecture-taint-behavior=NODE_ARCHITECTURE_TAINT_BEHAVIOR + Control how architecture taint should be applied to nodes in default + node pool(s) in new cluster. + + Supported values: + * unspecified: Default behavior, currently the same as `arm`. + * arm: kubernetes.io/arch=arm:NoSchedule taint will be added for ARM nodes. + * none: No architecture taint will be applied. + + Examples: + + $ gcloud container clusters create example-cluster \ + --node-architecture-taint-behavior=none + + To read more about node-taints, see + https://cloud.google.com/kubernetes-engine/docs/node-taints. + + NODE_ARCHITECTURE_TAINT_BEHAVIOR must be one of: unspecified, arm, + none. + --node-labels=[NODE_LABEL,...] Applies the given Kubernetes labels on all nodes in the new node pool. @@ -1715,6 +1753,12 @@ FLAGS 'veno', 'westwood', 'yeah'. + net.ipv4.neigh.default.gc_thresh1 Must be between + [0, 262144] + net.ipv4.neigh.default.gc_thresh2 Must be between + [512, 524288] + net.ipv4.neigh.default.gc_thresh3 Must be between + [1024, 1048576] net.netfilter.nf_conntrack_max Must be between [65536, 4194304] net.netfilter.nf_conntrack_buckets Must be between @@ -1730,6 +1774,10 @@ FLAGS net.netfilter.nf_conntrack_tcp_timeout_established Must be between [600, 86400] net.netfilter.nf_conntrack_acct Must be {0, 1} + kernel.keys.maxkeys Must be between + [200, 1048576] + kernel.keys.maxbytes Must be between + [20000, 2097152] kernel.shmmni Must be between [4096, 32768] kernel.shmmax Must be between @@ -2144,6 +2192,14 @@ FLAGS --enable-dataplane-v2-metrics Exposes advanced datapath flow metrics on node port. + At most one of these can be specified: + + --disable-pod-snapshots + Disable the Pod Snapshot feature on the cluster. + + --enable-pod-snapshots + Enable the Pod Snapshot feature on the cluster. + Node autoprovisioning --enable-autoprovisioning @@ -2152,9 +2208,6 @@ FLAGS Cluster Autoscaler will be able to create new node pools. Requires maximum CPU and memory limits to be specified. - This flag argument must be specified if any of the other arguments in - this group are specified. - At most one of these can be specified: --autoprovisioning-config-file=PATH_TO_FILE @@ -2231,23 +2284,6 @@ FLAGS Flags to configure autoprovisioned nodes - --max-cpu=MAX_CPU - Maximum number of cores in the cluster. - - Maximum number of cores to which the cluster can scale. - - This flag argument must be specified if any of the other arguments - in this group are specified. - - --max-memory=MAX_MEMORY - Maximum memory in the cluster. - - Maximum number of gigabytes of memory to which the cluster can - scale. - - This flag argument must be specified if any of the other arguments - in this group are specified. - --autoprovisioning-image-type=AUTOPROVISIONING_IMAGE_TYPE Node Autoprovisioning will create new nodes with the specified image type @@ -2266,6 +2302,18 @@ FLAGS be removed in an upcoming release. More info: https://cloud.google.com/kubernetes-engine/docs/release-notes#March_08_2022 + --max-cpu=MAX_CPU + Maximum number of cores in the cluster. + + Maximum number of cores to which the cluster can scale. Required to + be set when --enable-autoprovisioning is used. + + --max-memory=MAX_MEMORY + Maximum memory in the cluster. + + Maximum number of gigabytes of memory to which the cluster can + scale. Required to be set when --enable-autoprovisioning is used. + --min-cpu=MIN_CPU Minimum number of cores in the cluster. diff --git a/gcloud/container/clusters/create-auto b/gcloud/container/clusters/create-auto index 701e3c77d..27fe6a1db 100644 --- a/gcloud/container/clusters/create-auto +++ b/gcloud/container/clusters/create-auto @@ -16,7 +16,9 @@ SYNOPSIS [--cluster-ipv4-cidr=CLUSTER_IPV4_CIDR] [--cluster-secondary-range-name=NAME] [--cluster-version=CLUSTER_VERSION] + [--confidential-node-type=CONFIDENTIAL_NODE_TYPE] [--containerd-config-from-file=PATH_TO_FILE] + [--control-plane-egress=CONTROL_PLANE_EGRESS] [--create-subnetwork=[KEY=VALUE,...]] [--database-encryption-key=DATABASE_ENCRYPTION_KEY] [--disable-l4-lb-firewall-reconciliation] [--disable-multi-nic-lustre] @@ -51,6 +53,7 @@ SYNOPSIS [--dataplane-v2-observability-mode=DATAPLANE_V2_OBSERVABILITY_MODE | --disable-dataplane-v2-flow-observability | --enable-dataplane-v2-flow-observability] + [--disable-pod-snapshots | --enable-pod-snapshots] [--enable-insecure-binding-system-authenticated --enable-insecure-binding-system-unauthenticated] [--enable-master-authorized-networks @@ -280,6 +283,12 @@ FLAGS $ gcloud container get-server-config + --confidential-node-type=CONFIDENTIAL_NODE_TYPE + Enable confidential nodes for the cluster. Enabling Confidential Nodes + will create nodes using Confidential VM + https://docs.cloud.google.com/compute/docs/about-confidential-vm. + CONFIDENTIAL_NODE_TYPE must be one of: sev, sev_snp, tdx. + --containerd-config-from-file=PATH_TO_FILE Path of the YAML file that contains containerd configuration entries like configuring access to private image registries. @@ -294,6 +303,23 @@ FLAGS Use a full or relative path to a local file containing the value of containerd_config. + --control-plane-egress=CONTROL_PLANE_EGRESS + Configures the egress policy for the GKE control plane to control + outbound traffic from the kube-apiserver. CONTROL_PLANE_EGRESS must be + one of: + + NONE + (Recommended) Provides maximum security. This mode removes the + control plane's public IP address and blocks all outbound traffic + from the kube-apiserver by default, preventing unexpected data + exfiltration. Webhooks that use clientConfig.url will be disabled. + Essential GKE-managed services are still permitted to function via + an internal allowlist. + VIA_CONTROL_PLANE + (Default) Maintains backward compatibility. The control plane + retains its public IP address and allows egress traffic from the + kube-apiserver. + --create-subnetwork=[KEY=VALUE,...] Create a new subnetwork for the cluster. The name and range of the subnetwork can be customized via optional 'name' and 'range' key-value @@ -735,6 +761,14 @@ FLAGS Enables Advanced Datapath Observability which allows for a real-time view into pod-to-pod traffic within your cluster. + At most one of these can be specified: + + --disable-pod-snapshots + Disable the Pod Snapshot feature on the cluster. + + --enable-pod-snapshots + Enable the Pod Snapshot feature on the cluster. + --enable-insecure-binding-system-authenticated Allow using system:authenticated as a subject in ClusterRoleBindings and RoleBindings. Allowing bindings that reference system:authenticated diff --git a/gcloud/container/clusters/update b/gcloud/container/clusters/update index 876847ba2..d65f765ae 100644 --- a/gcloud/container/clusters/update +++ b/gcloud/container/clusters/update @@ -15,6 +15,7 @@ SYNOPSIS | --autoscaling-profile=AUTOSCALING_PROFILE | --complete-credential-rotation | --complete-ip-rotation | --containerd-config-from-file=PATH_TO_FILE + | --control-plane-egress=CONTROL_PLANE_EGRESS | --database-encryption-key=DATABASE_ENCRYPTION_KEY | --disable-database-encryption | --disable-default-snat | --disable-multi-nic-lustre | --disable-workload-identity @@ -69,9 +70,9 @@ SYNOPSIS --fleet-project=PROJECT_ID_OR_NUMBER --membership-type=MEMBERSHIP_TYPE --unset-membership-type | --clear-maintenance-minor-version-disruption-interval - | --maintenance-minor-version-disruption-interval=MAINTENANCE_MINOR_VERSION_DISRUPTION_INTERVAL --clear-maintenance-patch-version-disruption-interval | --maintenance-patch-version-disruption-interval=MAINTENANCE_PATCH_VERSION_DISRUPTION_INTERVAL | --clear-maintenance-window | --remove-maintenance-exclusion=NAME | [(--add-maintenance-exclusion-end=TIME_STAMP | --add-maintenance-exclusion-until-end-of-support) : --add-maintenance-exclusion-name=NAME --add-maintenance-exclusion-scope=SCOPE --add-maintenance-exclusion-start=TIME_STAMP] | --maintenance-window-end=TIME_STAMP --maintenance-window-recurrence=RRULE --maintenance-window-start=TIME_STAMP | --clear-resource-usage-bigquery-dataset | --enable-network-egress-metering --enable-resource-consumption-metering --resource-usage-bigquery-dataset=RESOURCE_USAGE_BIGQUERY_DATASET | --cluster-dns=CLUSTER_DNS --cluster-dns-domain=CLUSTER_DNS_DOMAIN --cluster-dns-scope=CLUSTER_DNS_SCOPE --additive-vpc-scope-dns-domain=ADDITIVE_VPC_SCOPE_DNS_DOMAIN | --disable-additive-vpc-scope | --dataplane-v2-observability-mode=DATAPLANE_V2_OBSERVABILITY_MODE | --disable-dataplane-v2-flow-observability | --enable-dataplane-v2-flow-observability --disable-dataplane-v2-metrics | --enable-dataplane-v2-metrics | --disable-auto-ipam | --enable-auto-ipam | --disable-l4-lb-firewall-reconciliation | --enable-l4-lb-firewall-reconciliation | --enable-authorized-networks-on-private-endpoint --enable-dns-access --enable-google-cloud-access --enable-ip-access --enable-k8s-certs-via-dns --enable-k8s-tokens-via-dns --enable-master-global-access --enable-private-endpoint --enable-master-authorized-networks --master-authorized-networks=NETWORK, - [NETWORK,...] | [--enable-autoprovisioning - : --autoprovisioning-config-file=PATH_TO_FILE + | --maintenance-minor-version-disruption-interval=MAINTENANCE_MINOR_VERSION_DISRUPTION_INTERVAL --clear-maintenance-patch-version-disruption-interval | --maintenance-patch-version-disruption-interval=MAINTENANCE_PATCH_VERSION_DISRUPTION_INTERVAL | --clear-maintenance-window | --remove-maintenance-exclusion=NAME | [(--add-maintenance-exclusion-end=TIME_STAMP | --add-maintenance-exclusion-until-end-of-support) : --add-maintenance-exclusion-name=NAME --add-maintenance-exclusion-scope=SCOPE --add-maintenance-exclusion-start=TIME_STAMP] | --maintenance-window-end=TIME_STAMP --maintenance-window-recurrence=RRULE --maintenance-window-start=TIME_STAMP | --clear-resource-usage-bigquery-dataset | --enable-network-egress-metering --enable-resource-consumption-metering --resource-usage-bigquery-dataset=RESOURCE_USAGE_BIGQUERY_DATASET | --cluster-dns=CLUSTER_DNS --cluster-dns-domain=CLUSTER_DNS_DOMAIN --cluster-dns-scope=CLUSTER_DNS_SCOPE --additive-vpc-scope-dns-domain=ADDITIVE_VPC_SCOPE_DNS_DOMAIN | --disable-additive-vpc-scope | --dataplane-v2-observability-mode=DATAPLANE_V2_OBSERVABILITY_MODE | --disable-dataplane-v2-flow-observability | --enable-dataplane-v2-flow-observability --disable-dataplane-v2-metrics | --enable-dataplane-v2-metrics | --disable-auto-ipam | --enable-auto-ipam | --disable-l4-lb-firewall-reconciliation | --enable-l4-lb-firewall-reconciliation | --disable-pod-snapshots | --enable-pod-snapshots | --enable-authorized-networks-on-private-endpoint --enable-dns-access --enable-google-cloud-access --enable-ip-access --enable-k8s-certs-via-dns --enable-k8s-tokens-via-dns --enable-master-global-access --enable-private-endpoint --enable-master-authorized-networks --master-authorized-networks=NETWORK, + [NETWORK,...] | --enable-autoprovisioning + --autoprovisioning-config-file=PATH_TO_FILE | --autoprovisioning-image-type=AUTOPROVISIONING_IMAGE_TYPE --autoprovisioning-locations=ZONE,[ZONE,...] --autoprovisioning-min-cpu-platform=PLATFORM --max-cpu=MAX_CPU @@ -86,7 +87,7 @@ SYNOPSIS --enable-autoprovisioning-autorepair --enable-autoprovisioning-autoupgrade [--max-accelerator=[type=TYPE,count=COUNT,...] - : --min-accelerator=[type=TYPE,count=COUNT,...]]] + : --min-accelerator=[type=TYPE,count=COUNT,...]] | --enable-insecure-binding-system-authenticated --enable-insecure-binding-system-unauthenticated | --logging-service=LOGGING_SERVICE @@ -343,6 +344,23 @@ REQUIRED FLAGS Use a full or relative path to a local file containing the value of containerd_config. + --control-plane-egress=CONTROL_PLANE_EGRESS + Configures the egress policy for the GKE control plane to control + outbound traffic from the kube-apiserver. CONTROL_PLANE_EGRESS must + be one of: + + NONE + (Recommended) Provides maximum security. This mode removes the + control plane's public IP address and blocks all outbound traffic + from the kube-apiserver by default, preventing unexpected data + exfiltration. Webhooks that use clientConfig.url will be + disabled. Essential GKE-managed services are still permitted to + function via an internal allowlist. + VIA_CONTROL_PLANE + (Default) Maintains backward compatibility. The control plane + retains its public IP address and allows egress traffic from the + kube-apiserver. + --database-encryption-key=DATABASE_ENCRYPTION_KEY Enable Database Encryption. @@ -1366,6 +1384,14 @@ REQUIRED FLAGS firewalls targeting ingress traffic. L4 LB VPC firewall reconciliation is enabled by default. + Or at most one of these can be specified: + + --disable-pod-snapshots + Disable the Pod Snapshot feature on the cluster. + + --enable-pod-snapshots + Enable the Pod Snapshot feature on the cluster. + Or at least one of these can be specified: --enable-authorized-networks-on-private-endpoint @@ -1438,9 +1464,6 @@ REQUIRED FLAGS Cluster Autoscaler will be able to create new node pools. Requires maximum CPU and memory limits to be specified. - This flag argument must be specified if any of the other arguments - in this group are specified. - At most one of these can be specified: --autoprovisioning-config-file=PATH_TO_FILE @@ -1543,12 +1566,14 @@ REQUIRED FLAGS Maximum number of cores in the cluster. Maximum number of cores to which the cluster can scale. + Required to be set when --enable-autoprovisioning is used. --max-memory=MAX_MEMORY Maximum memory in the cluster. Maximum number of gigabytes of memory to which the cluster can - scale. + scale. Required to be set when --enable-autoprovisioning is + used. --min-cpu=MIN_CPU Minimum number of cores in the cluster. diff --git a/gcloud/container/fleet/memberships/get-credentials b/gcloud/container/fleet/memberships/get-credentials index 3b836ba61..ee5d28ea1 100644 --- a/gcloud/container/fleet/memberships/get-credentials +++ b/gcloud/container/fleet/memberships/get-credentials @@ -20,6 +20,13 @@ DESCRIPTION Upon success, this command will switch the current context to the target cluster if other contexts are already present in the kubeconfig file. + To force the use of Application Default Credentials (ADC) for + authentication, you can set the + container/use_application_default_credentials property to true: + + $ gcloud config set container/use_application_default_credentials \ + true + EXAMPLES Get the Gateway kubeconfig for a globally registered cluster: diff --git a/gcloud/container/help b/gcloud/container/help index 241517f41..886c30dcb 100644 --- a/gcloud/container/help +++ b/gcloud/container/help @@ -72,6 +72,9 @@ GROUPS vmware Deploy and manage Anthos clusters on VMware for running containers. + workload + Manage Workload Optimizer related workloads for GKE. + COMMANDS COMMAND is one of the following: diff --git a/gcloud/container/hub/memberships/get-credentials b/gcloud/container/hub/memberships/get-credentials index c9049db92..939c085d1 100644 --- a/gcloud/container/hub/memberships/get-credentials +++ b/gcloud/container/hub/memberships/get-credentials @@ -20,6 +20,13 @@ DESCRIPTION Upon success, this command will switch the current context to the target cluster if other contexts are already present in the kubeconfig file. + To force the use of Application Default Credentials (ADC) for + authentication, you can set the + container/use_application_default_credentials property to true: + + $ gcloud config set container/use_application_default_credentials \ + true + EXAMPLES Get the Gateway kubeconfig for a globally registered cluster: diff --git a/gcloud/container/node-pools/create b/gcloud/container/node-pools/create index bf2dd0e84..290bc5afe 100644 --- a/gcloud/container/node-pools/create +++ b/gcloud/container/node-pools/create @@ -42,6 +42,7 @@ SYNOPSIS [--metadata-from-file=KEY=LOCAL_FILE_PATH,[...]] [--min-cpu-platform=PLATFORM] [--network-performance-configs=[PROPERTY=VALUE,...]] + [--node-architecture-taint-behavior=NODE_ARCHITECTURE_TAINT_BEHAVIOR] [--node-group=NODE_GROUP] [--node-labels=[NODE_LABEL,...]] [--node-locations=ZONE,[ZONE,...]] [--node-pool-soak-duration=NODE_POOL_SOAK_DURATION] @@ -61,7 +62,7 @@ SYNOPSIS [--standard-rollout-policy=[batch-node-count=BATCH_NODE_COUNT, batch-percent=BATCH_NODE_PERCENTAGE, batch-soak-duration=BATCH_SOAK_DURATION,...]] - [--storage-pools=STORAGE_POOL,[...]] + [--storage-pools=STORAGE_POOL,[...]] [--subnetwork=SUBNETWORK] [--system-config-from-file=PATH_TO_FILE] [--tags=TAG,[TAG,...]] [--threads-per-core=THREADS_PER_CORE] [--tpu-topology=TPU_TOPOLOGY] [--windows-os-version=WINDOWS_OS_VERSION] @@ -547,6 +548,27 @@ FLAGS external IP destinations. The following tier values are allowed: [TIER_UNSPECIFIED,TIER_1] + --node-architecture-taint-behavior=NODE_ARCHITECTURE_TAINT_BEHAVIOR + Control how architecture taint should be applied to nodes in a new node + pool. + + Supported values: + * unspecified: Default behavior, currently the same as `arm`. + * arm: kubernetes.io/arch=arm:NoSchedule taint will be added for ARM nodes. + * none: No architecture taint will be applied. + + Examples: + + $ gcloud container node-pools create node-pool-1 \ + --cluster=example-cluster \ + --node-architecture-taint-behavior=none + + To read more about node-taints, see + https://cloud.google.com/kubernetes-engine/docs/node-taints. + + NODE_ARCHITECTURE_TAINT_BEHAVIOR must be one of: unspecified, arm, + none. + --node-group=NODE_GROUP Assign instances of this pool to run on the specified Google Compute Engine node group. This is useful for running workloads on sole tenant @@ -819,6 +841,14 @@ FLAGS STORAGE_POOL must be in the format projects/project/zones/zone/storagePools/storagePool + --subnetwork=SUBNETWORK + The subnetwork to use for nodes. This subnetwork must exist in the + cluster's list of additional subnetworks. + + If not specified, the node pool's node IP addresses are allocated from + the least utilized subnet and its secondary range. See details at + https://cloud.google.com/kubernetes-engine/docs/how-to/multi-subnet-clusters#create-node-pool + --system-config-from-file=PATH_TO_FILE Path of the YAML/JSON file that contains the node configuration, including Linux kernel parameters (sysctls) and kubelet configs. @@ -1077,6 +1107,12 @@ FLAGS 'veno', 'westwood', 'yeah'. + net.ipv4.neigh.default.gc_thresh1 Must be between + [0, 262144] + net.ipv4.neigh.default.gc_thresh2 Must be between + [512, 524288] + net.ipv4.neigh.default.gc_thresh3 Must be between + [1024, 1048576] net.netfilter.nf_conntrack_max Must be between [65536, 4194304] net.netfilter.nf_conntrack_buckets Must be between @@ -1092,6 +1128,10 @@ FLAGS net.netfilter.nf_conntrack_tcp_timeout_established Must be between [600, 86400] net.netfilter.nf_conntrack_acct Must be {0, 1} + kernel.keys.maxkeys Must be between + [200, 1048576] + kernel.keys.maxbytes Must be between + [20000, 2097152] kernel.shmmni Must be between [4096, 32768] kernel.shmmax Must be between diff --git a/gcloud/container/node-pools/update b/gcloud/container/node-pools/update index 2edb0145c..6e4a7ab1d 100644 --- a/gcloud/container/node-pools/update +++ b/gcloud/container/node-pools/update @@ -20,6 +20,7 @@ SYNOPSIS | --logging-variant=LOGGING_VARIANT | --max-run-duration=MAX_RUN_DURATION | --network-performance-configs=[PROPERTY=VALUE,...] + | --node-architecture-taint-behavior=NODE_ARCHITECTURE_TAINT_BEHAVIOR | --node-labels=[NODE_LABEL,...] | --node-locations=ZONE,[ZONE,...] | --node-taints=[NODE_TAINT,...] | --resource-manager-tags=[KEY=VALUE,...] @@ -237,6 +238,27 @@ REQUIRED FLAGS external IP destinations. The following tier values are allowed: [TIER_UNSPECIFIED,TIER_1] + --node-architecture-taint-behavior=NODE_ARCHITECTURE_TAINT_BEHAVIOR + Control how architecture taint should be applied to nodes in an + existing node pool. + + Supported values: + * unspecified: Default behavior, currently the same as `arm`. + * arm: kubernetes.io/arch=arm:NoSchedule taint will be added for ARM nodes. + * none: No architecture taint will be applied. + + Examples: + + $ gcloud container node-pools update node-pool-1 \ + --cluster=example-cluster \ + --node-architecture-taint-behavior=none + + To read more about node-taints, see + https://cloud.google.com/kubernetes-engine/docs/node-taints. + + NODE_ARCHITECTURE_TAINT_BEHAVIOR must be one of: unspecified, arm, + none. + --node-labels=[NODE_LABEL,...] Replaces all the user specified Kubernetes labels on all nodes in an existing node pool with the given labels. @@ -595,6 +617,12 @@ REQUIRED FLAGS 'veno', 'westwood', 'yeah'. + net.ipv4.neigh.default.gc_thresh1 Must be between + [0, 262144] + net.ipv4.neigh.default.gc_thresh2 Must be between + [512, 524288] + net.ipv4.neigh.default.gc_thresh3 Must be between + [1024, 1048576] net.netfilter.nf_conntrack_max Must be between [65536, 4194304] net.netfilter.nf_conntrack_buckets Must be between @@ -612,6 +640,10 @@ REQUIRED FLAGS net.netfilter.nf_conntrack_tcp_timeout_established Must be between [600, 86400] net.netfilter.nf_conntrack_acct Must be {0, 1} + kernel.keys.maxkeys Must be between + [200, 1048576] + kernel.keys.maxbytes Must be between + [20000, 2097152] kernel.shmmni Must be between [4096, 32768] kernel.shmmax Must be between diff --git a/gcloud/container/workload/help b/gcloud/container/workload/help new file mode 100644 index 000000000..d0c78bdfd --- /dev/null +++ b/gcloud/container/workload/help @@ -0,0 +1,20 @@ +NAME + gcloud container workload - manage Workload Optimizer related workloads for + GKE + +SYNOPSIS + gcloud container workload GROUP [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Manage Workload Optimizer related workloads for GKE. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +GROUPS + GROUP is one of the following: + + profiles + Quickstart engine for GKE workload optimization. diff --git a/gcloud/container/workload/profiles/help b/gcloud/container/workload/profiles/help new file mode 100644 index 000000000..630b84124 --- /dev/null +++ b/gcloud/container/workload/profiles/help @@ -0,0 +1,20 @@ +NAME + gcloud container workload profiles - quickstart engine for GKE workload + optimization + +SYNOPSIS + gcloud container workload profiles GROUP [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Quickstart engine for GKE workload optimization. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +GROUPS + GROUP is one of the following: + + manifests + Generate optimized Kubernetes manifests. diff --git a/gcloud/container/workload/profiles/manifests/create b/gcloud/container/workload/profiles/manifests/create new file mode 100644 index 000000000..06953ccc2 --- /dev/null +++ b/gcloud/container/workload/profiles/manifests/create @@ -0,0 +1,43 @@ +NAME + gcloud container workload profiles manifests create - generate optimized + Kubernetes manifests for a given workload profile + +SYNOPSIS + gcloud container workload profiles manifests create + --cluster-version=CLUSTER_VERSION --workload=WORKLOAD + [--options=[KEY=VALUE,...]] [--output=OUTPUT; default="all"] + [--output-path=OUTPUT_PATH] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Generate optimized Kubernetes manifests for a given workload profile. + +REQUIRED FLAGS + --cluster-version=CLUSTER_VERSION + The GKE version to generate the manifest for. + + --workload=WORKLOAD + The name of the optimization set to generate the manifest for. This + specifies the workload, workload version, and workload characterization + to optimize for (e.g., "redis-7-caching"). + +OPTIONAL FLAGS + --options=[KEY=VALUE,...] + Additional key-value pair options for generating the manifest. For + example, to specify allowed machine types: + --options=machineType=type1,type2 + + --output=OUTPUT; default="all" + The output to display. Default is all. OUTPUT must be one of: manifest, + all. + + --output-path=OUTPUT_PATH + The path to save the output to. If not specified, output to the + terminal. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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/container/workload/profiles/manifests/help b/gcloud/container/workload/profiles/manifests/help new file mode 100644 index 000000000..668c07c63 --- /dev/null +++ b/gcloud/container/workload/profiles/manifests/help @@ -0,0 +1,20 @@ +NAME + gcloud container workload profiles manifests - generate optimized + Kubernetes manifests + +SYNOPSIS + gcloud container workload profiles manifests COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Generate optimized Kubernetes manifests. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + create + Generate optimized Kubernetes manifests for a given workload profile. diff --git a/gcloud/database-migration/connection-profiles/create/postgresql b/gcloud/database-migration/connection-profiles/create/postgresql index 50c2ffa51..37461e8be 100644 --- a/gcloud/database-migration/connection-profiles/create/postgresql +++ b/gcloud/database-migration/connection-profiles/create/postgresql @@ -150,7 +150,9 @@ FLAGS Network port of the database. --database=DATABASE - The name of the specific database within the host. + The name of the specific database within the host. For Native Logical + Postgres migrations, one of the replicating databases must be + specified. Authentication method. diff --git a/gcloud/database-migration/migration-jobs/create b/gcloud/database-migration/migration-jobs/create index 112c8f802..ba19a3348 100644 --- a/gcloud/database-migration/migration-jobs/create +++ b/gcloud/database-migration/migration-jobs/create @@ -11,6 +11,8 @@ SYNOPSIS [--dump-parallel-level=DUMP_PARALLEL_LEVEL] [--dump-type=DUMP_TYPE] [--filter=FILTER] [--labels=[KEY=VALUE,...]] [--original-migration-name=ORIGINAL_MIGRATION_NAME] + [--postgres-max-additional-subscriptions=POSTGRES_MAX_ADDITIONAL_SUBSCRIPTIONS] + [--use-postgres-native] [--all-databases | --databases-filter=databaseName,[...]] [--cmek-key=CMEK_KEY : --cmek-keyring=CMEK_KEYRING --cmek-project=CMEK_PROJECT] @@ -243,6 +245,13 @@ OPTIONAL FLAGS To set the migration_job attribute: ◆ provide the argument --original-migration-name on the command line. + --postgres-max-additional-subscriptions=POSTGRES_MAX_ADDITIONAL_SUBSCRIPTIONS + Maximum number of additional subscriptions to use for the PostgreSQL + migration job. + + --use-postgres-native + Use native logical replication for PostgreSQL migration. + The migration job objects config. The migration job objects config for databases. diff --git a/gcloud/database-migration/migration-jobs/update b/gcloud/database-migration/migration-jobs/update index 90a77682d..69ac54e9f 100644 --- a/gcloud/database-migration/migration-jobs/update +++ b/gcloud/database-migration/migration-jobs/update @@ -7,8 +7,9 @@ SYNOPSIS (MIGRATION_JOB : --region=REGION) [--no-async] [--commit-id=COMMIT_ID] [--destination=DESTINATION] [--display-name=DISPLAY_NAME] [--dump-parallel-level=DUMP_PARALLEL_LEVEL] [--dump-type=DUMP_TYPE] - [--filter=FILTER] [--source=SOURCE] [--type=TYPE] - [--update-labels=[KEY=VALUE,...]] + [--filter=FILTER] + [--postgres-max-additional-subscriptions=POSTGRES_MAX_ADDITIONAL_SUBSCRIPTIONS] + [--source=SOURCE] [--type=TYPE] [--update-labels=[KEY=VALUE,...]] [--all-databases | --databases-filter=databaseName,[...]] [--clear-labels | --remove-labels=[KEY,...]] [--dump-flags=[KEY=VALUE,...] | --dump-path=DUMP_PATH] @@ -122,6 +123,10 @@ FLAGS "Employee" and are present under schema "Company", use filter as "Company.Employee* AND type=TABLE" + --postgres-max-additional-subscriptions=POSTGRES_MAX_ADDITIONAL_SUBSCRIPTIONS + Maximum number of additional subscriptions to use for the PostgreSQL + migration job. + Connection profile resource - ID of the source connection profile, representing the source database. This represents a Cloud resource. (NOTE) Some attributes are not given arguments in this group but can be set in diff --git a/gcloud/dataflow/flex-template/run b/gcloud/dataflow/flex-template/run index ecd1dd0fb..677f7aecd 100644 --- a/gcloud/dataflow/flex-template/run +++ b/gcloud/dataflow/flex-template/run @@ -10,6 +10,7 @@ SYNOPSIS [--dataflow-kms-key=DATAFLOW_KMS_KEY] [--disable-public-ips] [--enable-streaming-engine] [--flexrs-goal=FLEXRS_GOAL] [--launcher-machine-type=LAUNCHER_MACHINE_TYPE] + [--launcher-vm-timeout-secs=LAUNCHER_VM_TIMEOUT_SECS] [--max-workers=MAX_WORKERS] [--network=NETWORK] [--num-workers=NUM_WORKERS] [--parameters=[PARAMETERS,...]] [--region=REGION_ID] [--service-account-email=SERVICE_ACCOUNT_EMAIL] @@ -76,6 +77,10 @@ OPTIONAL FLAGS The machine type to use for launching the job. If not set, Dataflow will select a default machine type. + --launcher-vm-timeout-secs=LAUNCHER_VM_TIMEOUT_SECS + The timeout in seconds for the launcher VM. If not set, Dataflow uses a + default timeout. + --max-workers=MAX_WORKERS Maximum number of workers to run. diff --git a/gcloud/dataplex/context/help b/gcloud/dataplex/context/help index 5c88d5a87..94a3cbcc6 100644 --- a/gcloud/dataplex/context/help +++ b/gcloud/dataplex/context/help @@ -16,7 +16,7 @@ COMMANDS COMMAND is one of the following: lookup - Looks up LLM context for data assets. + Looks up metadata that can be used as context by agents. NOTES This variant is also available: diff --git a/gcloud/dataplex/context/lookup b/gcloud/dataplex/context/lookup index dde9a56d5..1ae6511b1 100644 --- a/gcloud/dataplex/context/lookup +++ b/gcloud/dataplex/context/lookup @@ -1,20 +1,22 @@ NAME - gcloud dataplex context lookup - looks up LLM context for data assets + gcloud dataplex context lookup - looks up metadata that can be used as + context by agents SYNOPSIS gcloud dataplex context lookup --resources=[RESOURCES,...] - [--location=LOCATION] [GCLOUD_WIDE_FLAG ...] + [--context-format=CONTEXT_FORMAT; default="yaml"] [--location=LOCATION] + [--options=OPTIONS] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - Looks up LLM context for data assets. + Looks up metadata that can be used as context by agents. Fetches detailed contextual metadata for the specified data assets. Data - assets can be identified by their Dataplex entry name, source system - resource name or fully qualified name. The returned context can include - schema, descriptions, business annotations, data quality insights, and - relationships, structured for application use. This output is particularly - useful for providing grounding to Large Language Models (LLMs), enabling - more accurate and context-aware interactions with your data. + assets can be identified by their Dataplex entry name. The returned context + can include schema, descriptions, business annotations, data quality + insights, and relationships, structured for application use. This output is + particularly useful for providing grounding to Large Language Models + (LLMs), enabling more accurate and context-aware interactions with your + data. EXAMPLES To look up Dataplex Context for BigQuery tables 'table1' and 'table2' in @@ -38,14 +40,14 @@ EXAMPLES REQUIRED FLAGS --resources=[RESOURCES,...] - The identifier describing the resource, - ◆ in the form of a entry name, or - ◆ in the form of a linked resource name, or - ◆ in the form of a fully qualified name. Examples: - ◆ projects/{project}/locations/{location}/entryGroups/{entry_group}/entries/{entry} - ◆ bigquery:{project}.{dataset}.{table} + The identifier describing the resource, for example: + projects/{project}/locations/{location}/entryGroups/{entry_group}/entries/{entry} OPTIONAL FLAGS + --context-format=CONTEXT_FORMAT; default="yaml" + The output format of the command. CONTEXT_FORMAT must be one of: json, + xml, yaml. + Location resource - The Dataplex location for the context lookup. If not specified, the location will be taken from the dataplex/location property in your gcloud configuration. This represents a Cloud resource. (NOTE) @@ -66,6 +68,10 @@ OPTIONAL FLAGS ◆ provide the argument --location on the command line; ◆ set the property dataplex/location. + --options=OPTIONS + Additional options for the command. This can be provided as a JSON + string. Example: --options='{"key": "value"}' + 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/dataplex/datascans/create/data-profile b/gcloud/dataplex/datascans/create/data-profile index 7959eb2cd..495f19df8 100644 --- a/gcloud/dataplex/datascans/create/data-profile +++ b/gcloud/dataplex/datascans/create/data-profile @@ -16,8 +16,9 @@ SYNOPSIS --include-field-names=INCLUDE_FIELD_NAMES --row-filter=ROW_FILTER --sampling-percent=SAMPLING_PERCENT] [--incremental-field=INCREMENTAL_FIELD --on-demand=ON_DEMAND - | --schedule=SCHEDULE - | --one-time --ttl-after-scan-completion=TTL_AFTER_SCAN_COMPLETION] + | --schedule=SCHEDULE | --one-time + --ttl-after-scan-completion=TTL_AFTER_SCAN_COMPLETION + --service-account=SERVICE_ACCOUNT | --use-user-credential] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -190,6 +191,16 @@ OPTIONAL FLAGS "100s" for 100 seconds.The argument is only valid when --one-time is set. + Identity to run the datascan. + + At most one of these can be specified: + + --service-account=SERVICE_ACCOUNT + Service account email to run the scan as. + + --use-user-credential + If set, the scan runs with the caller's credential. + 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/dataplex/datascans/create/data-quality b/gcloud/dataplex/datascans/create/data-quality index b573af02f..ca9bd9767 100644 --- a/gcloud/dataplex/datascans/create/data-quality +++ b/gcloud/dataplex/datascans/create/data-quality @@ -11,8 +11,9 @@ SYNOPSIS [--description=DESCRIPTION] [--display-name=DISPLAY_NAME] [--labels=[KEY=VALUE,...]] [--async | --validate-only] [--incremental-field=INCREMENTAL_FIELD --on-demand=ON_DEMAND - | --schedule=SCHEDULE - | --one-time --ttl-after-scan-completion=TTL_AFTER_SCAN_COMPLETION] + | --schedule=SCHEDULE | --one-time + --ttl-after-scan-completion=TTL_AFTER_SCAN_COMPLETION + --service-account=SERVICE_ACCOUNT | --use-user-credential] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -154,6 +155,16 @@ OPTIONAL FLAGS "100s" for 100 seconds.The argument is only valid when --one-time is set. + Identity to run the datascan. + + At most one of these can be specified: + + --service-account=SERVICE_ACCOUNT + Service account email to run the scan as. + + --use-user-credential + If set, the scan runs with the caller's credential. + 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/dataplex/entries/help b/gcloud/dataplex/entries/help index bfe1cb1e4..5f55ea3ec 100644 --- a/gcloud/dataplex/entries/help +++ b/gcloud/dataplex/entries/help @@ -30,6 +30,9 @@ COMMANDS lookup Lookup a Dataplex entry. + modify + Modify a Dataplex Entry. + remove-aspects Remove aspects from a Dataplex Entry. diff --git a/gcloud/dataplex/entries/modify b/gcloud/dataplex/entries/modify new file mode 100644 index 000000000..a5fde8f2d --- /dev/null +++ b/gcloud/dataplex/entries/modify @@ -0,0 +1,288 @@ +NAME + gcloud dataplex entries modify - modify a Dataplex Entry + +SYNOPSIS + gcloud dataplex entries modify + (ENTRY : --entry-group=ENTRY_GROUP --location=LOCATION) + [--remove-aspects=[ASPECT_TYPE@PATH,...]] + [--update-aspects=YAML_OR_JSON_FILE] + [--clear-fully-qualified-name + | --fully-qualified-name=FULLY_QUALIFIED_NAME] + [--entry-source-update-time=DATE_TIME + : --clear-entry-source-create-time + | --entry-source-create-time=DATE_TIME + --clear-entry-source-description + | --entry-source-description=DESCRIPTION + --clear-entry-source-display-name + | --entry-source-display-name=DISPLAY_NAME + --clear-entry-source-labels + | --entry-source-labels=[KEY=VALUE,...] --clear-entry-source-platform + | --entry-source-platform=PLATFORM_NAME --clear-entry-source-resource + | --entry-source-resource=RESOURCE --clear-entry-source-system + | --entry-source-system=SYSTEM_NAME] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Modify specified fields in a given Dataplex Entry. + +EXAMPLES + To modify fully qualified name (FQN) of an entry, run: + + $ gcloud dataplex entries modify entry1 --project=test-project \ + --location=us-central1 --entry-group entry-group1 \ + --fully-qualified-name='custom:a.b.c' + + To modify description of an entry, run: + + $ gcloud dataplex entries modify entry1 --project=test-project \ + --location=us-central1 --entry-group entry-group1 \ + --entry-source-description='Updated description' \ + --entry-source-update-time='1998-09-04T12:00:00-0700' + + To clear the description of an entry, run: + + $ gcloud dataplex entries modify entry1 --project=test-project \ + --location=us-central1 --entry-group entry-group1 \ + --clear-entry-source-description \ + --entry-source-update-time='1998-09-04T12:00:00-0700' + + To add or update aspects from the YAML/JSON file, run: + + $ gcloud dataplex entries modify entry1 --project=test-project \ + --location=us-central1 --entry-group entry-group1 \ + --update-aspects=path-to-a-file-with-aspects.json + + To remove all aspects of type test-project.us-central1.some-aspect-type + from the entry, run: + + $ gcloud dataplex entries modify entry1 --project=test-project \ + --location=us-central1 --entry-group entry-group1 \ + --remove-aspects='test-project.us-central1.some-aspect-type@*' + + To remove all aspects on path Schema.column1 from the entry, run: + + $ gcloud dataplex entries modify entry1 --project=test-project \ + --location=us-central1 --entry-group entry-group1 \ + --remove-aspects='*@Schema.column1' + + To remove exact aspects + test-project.us-central1.some-aspect-type@Schema.column1 and + test-project.us-central1.some-aspect-type2@Schema.column2 from the entry, + run: + + $ gcloud dataplex entries modify entry1 --project=test-project \ + --location=us-central1 --entry-group entry-group1 \ + --remove-aspects=test-project.us-central1.some-aspect-type@Schem\ + a.column1,test-project.us-central2.some-aspect-type@Schema.column2 + +POSITIONAL ARGUMENTS + Entry resource - Arguments and flags that define the Dataplex Entry you + want to reference. 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 entry 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. + + ENTRY + ID of the entry or fully qualified identifier for the entry. + + To set the entry attribute: + ▸ provide the argument entry on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --entry-group=ENTRY_GROUP + Entry group containing Dataplex Entries. + + To set the entry-group attribute: + ▸ provide the argument entry on the command line with a fully + specified name; + ▸ provide the argument --entry-group on the command line. + + --location=LOCATION + Location of the Dataplex resource. + + To set the location attribute: + ▸ provide the argument entry on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ set the property dataplex/location. + +FLAGS + --remove-aspects=[ASPECT_TYPE@PATH,...] + List of Aspect keys, identifying Aspects to remove from the entry. + + Keys are in the format ASPECT_TYPE@PATH, or just ASPECT_TYPE, if the + Aspect is attached to an entry itself rather than to a specific column + defined in the schema. + + ASPECT_TYPE is expected to be in a format + PROJECT_ID.LOCATION.ASPECT_TYPE_ID or a wildcard *, which targets all + aspect types. + + PATH can be either empty (which means a 'root' path, such that Aspect + is attached to the entry itself), point to a specific column defined in + the schema (for example: Schema.some_column) or a wildcard * (target + all paths). + + ASPECT_TYPE and PATH cannot be both specified as wildcards *. + + If both --update-aspects and --remove-aspects flags are specified, and + the same aspect key is used in both flags, then --update-aspects takes + precedence, and such an aspect will be updated and not removed. + + --update-aspects=YAML_OR_JSON_FILE + Path to a YAML or JSON file containing Aspects to add or update. + + When this flag is specified, only Aspects referenced in the file are + going to be added or updated. Specifying this flag does not remove any + Aspects from the entry. In other words, specifying this flag will not + lead to a full replacement of Aspects with a contents of the provided + file. + + Content of the file contains a map, where keys are in the format + ASPECT_TYPE@PATH, or just ASPECT_TYPE, if the Aspect is attached to an + entry itself rather than to a specific column defined in the schema. + + Values in the map represent Aspect's content, which must conform to a + template defined for a given ASPECT_TYPE. Each Aspect will be replaced + fully by the provided content. That means data in the Aspect will be + replaced and not merged with existing contents of that Aspect in the + Entry. + + ASPECT_TYPE is expected to be in a format + PROJECT_ID.LOCATION.ASPECT_TYPE_ID. + + PATH can be either empty (which means a 'root' path, such that Aspect + is attached to the entry itself) or point to a specific column defined + in the schema. For example: Schema.some_column. + + Example YAML format: + + project-id1.us-central1.my-aspect-type1: + data: + aspectField1: someValue + aspectField2: someOtherValue + project-id2.us-central1.my-aspect-type2@Schema.column1: + data: + aspectField3: someValue3 + + Example JSON format: + + { + "project-id1.us-central1.my-aspect-type1": { + "data": { + "aspectField1": "someValue", + "aspectField2": "someOtherValue" + } + }, + "project-id2.us-central1.my-aspect-type2@Schema.column1": { + "data": { + "aspectField3": "someValue3" + } + } + } + + If both --update-aspects and --remove-aspects flags are specified, and + the same aspect key is used in both flags, then --update-aspects takes + precedence, and such an aspect will be updated and not removed. + + At most one of these can be specified: + + --clear-fully-qualified-name + Clear the FQN for the Entry. + + --fully-qualified-name=FULLY_QUALIFIED_NAME + FQN, a name for the entry that can reference it in an external + system. + + Source system related information for an entry. If any of the entry source + fields are specified, then ``--entry-source-update-time must be specified + as well. + + --entry-source-update-time=DATE_TIME + The update date and time of the resource in the source system. + + This flag argument must be specified if any of the other arguments in + this group are specified. + + At most one of these can be specified: + + --clear-entry-source-create-time + Clear the value for the create_time field in the Entry Source. + + --entry-source-create-time=DATE_TIME + The creation date and time of the resource in the source system. + + At most one of these can be specified: + + --clear-entry-source-description + Clear the value for the description field in the Entry Source. + + --entry-source-description=DESCRIPTION + Description of the Entry. + + At most one of these can be specified: + + --clear-entry-source-display-name + Clear the value for the display_name field in the Entry Source. + + --entry-source-display-name=DISPLAY_NAME + User friendly display name. + + At most one of these can be specified: + + --clear-entry-source-labels + Clear the labels for the Entry Source. + + --entry-source-labels=[KEY=VALUE,...] + List of label KEY=VALUE pairs to add. + + Keys must start with a lowercase character and contain only hyphens + (-), underscores (_), lowercase characters, and numbers. Values must + contain only hyphens (-), underscores (_), lowercase characters, and + numbers. + + At most one of these can be specified: + + --clear-entry-source-platform + Clear the value for the platform field in the Entry Source. + + --entry-source-platform=PLATFORM_NAME + The platform containing the source system. + + At most one of these can be specified: + + --clear-entry-source-resource + Clear the value for the resource field in the Entry Source. + + --entry-source-resource=RESOURCE + The name of the resource in the source system. + + At most one of these can be specified: + + --clear-entry-source-system + Clear the value for the system field in the Entry Source. + + --entry-source-system=SYSTEM_NAME + The name of the source system. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This variant is also available: + + $ gcloud alpha dataplex entries modify + diff --git a/gcloud/dataproc/clusters/create b/gcloud/dataproc/clusters/create index 2f2a461e8..a22356d5b 100644 --- a/gcloud/dataproc/clusters/create +++ b/gcloud/dataproc/clusters/create @@ -16,10 +16,12 @@ SYNOPSIS [--driver-pool-machine-type=DRIVER_POOL_MACHINE_TYPE] [--driver-pool-min-cpu-platform=PLATFORM] [--driver-pool-size=DRIVER_POOL_SIZE] [--enable-component-gateway] + [--engine=ENGINE] [--initialization-action-timeout=TIMEOUT; default="10m"] [--initialization-actions=CLOUD_STORAGE_URI,[...]] [--labels=[KEY=VALUE,...]] [--master-accelerator=[type=TYPE,[count=COUNT],...]] + [--master-attached-disks=MASTER_ATTACHED_DISKS] [--master-boot-disk-provisioned-iops=MASTER_BOOT_DISK_PROVISIONED_IOPS] [--master-boot-disk-provisioned-throughput=MASTER_BOOT_DISK_PROVISIONED_THROUGHPUT] [--master-boot-disk-size=MASTER_BOOT_DISK_SIZE] @@ -38,6 +40,7 @@ SYNOPSIS [--private-ipv6-google-access-type=PRIVATE_IPV6_GOOGLE_ACCESS_TYPE] [--properties=[PREFIX:PROPERTY=VALUE,...]] [--secondary-worker-accelerator=[type=TYPE,[count=COUNT],...]] + [--secondary-worker-attached-disks=SECONDARY_WORKER_ATTACHED_DISKS] [--secondary-worker-boot-disk-size=SECONDARY_WORKER_BOOT_DISK_SIZE] [--secondary-worker-boot-disk-type=SECONDARY_WORKER_BOOT_DISK_TYPE] [--secondary-worker-local-ssd-interface=SECONDARY_WORKER_LOCAL_SSD_INTERFACE] @@ -47,8 +50,9 @@ SYNOPSIS [--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] [--tier=TIER] + [--temp-bucket=TEMP_BUCKET] [--worker-accelerator=[type=TYPE,[count=COUNT],...]] + [--worker-attached-disks=WORKER_ATTACHED_DISKS] [--worker-boot-disk-provisioned-iops=WORKER_BOOT_DISK_PROVISIONED_IOPS] [--worker-boot-disk-provisioned-throughput=WORKER_BOOT_DISK_PROVISIONED_THROUGHPUT] [--worker-boot-disk-size=WORKER_BOOT_DISK_SIZE] @@ -235,6 +239,9 @@ FLAGS Enable access to the web UIs of selected components on the cluster through the component gateway. + --engine=ENGINE + Cluster engine. ENGINE must be one of: default, lightning. + --initialization-action-timeout=TIMEOUT; default="10m" The maximum duration of each initialization action. See $ gcloud topic datetimes for information on duration formats. @@ -263,6 +270,42 @@ FLAGS The number of accelerators to attach to each instance. The default value is 1. + --master-attached-disks=MASTER_ATTACHED_DISKS + A list of disk configurations to attach to each instance in this group. + Disk configurations are separated by semicolons. Each disk + configuration is a comma-separated list of the following parameters. + + type - required + The type of disk to attach to the instances + (https://cloud.google.com/compute/docs/disks/hyperdisks). + Allowed disk types are: hyperdisk-balanced, hyperdisk-extreme, + hyperdisk-ml, hyperdisk-throughput. + + size - optional + The size of the disk. The value must be a whole number followed by + a size unit GB for gigabyte, or TB for terabyte. For example, + 10GB produces a 10 gigabyte disk. + + iops - optional + Indicates the IOPS + (https://cloud.google.com/compute/docs/disks/hyperdisks#iops) to + provision for the attached hyperdisk. This parameter sets the limit + for disk I/O operations per second. + + throughput - optional + Indicates the throughput + (https://cloud.google.com/compute/docs/disks/hyperdisks#throughput) + to provision for the attached hyperdisk. This parameter sets the + limit for throughput in MiB per second. + + Example: + type='hyperdisk-balanced,iops=5000,throughput=200,size=100G;type=hyperdisk-throughput,size=9000G' + + Attaches two disks to the instances. The first disk is a + hyperdisk-balanced disk with 5000 IOPS, 200 MiB/s throughput, and 100 + GiB size. The second disk is a hyperdisk-throughput disk with 9000 + GiB size. + --master-boot-disk-provisioned-iops=MASTER_BOOT_DISK_PROVISIONED_IOPS Indicates the IOPS (https://cloud.google.com/compute/docs/disks/hyperdisks#iops) to @@ -401,6 +444,42 @@ FLAGS The number of accelerators to attach to each instance. The default value is 1. + --secondary-worker-attached-disks=SECONDARY_WORKER_ATTACHED_DISKS + A list of disk configurations to attach to each instance in this group. + Disk configurations are separated by semicolons. Each disk + configuration is a comma-separated list of the following parameters. + + type - required + The type of disk to attach to the instances + (https://cloud.google.com/compute/docs/disks/hyperdisks). + Allowed disk types are: hyperdisk-balanced, hyperdisk-extreme, + hyperdisk-ml, hyperdisk-throughput. + + size - optional + The size of the disk. The value must be a whole number followed by + a size unit GB for gigabyte, or TB for terabyte. For example, + 10GB produces a 10 gigabyte disk. + + iops - optional + Indicates the IOPS + (https://cloud.google.com/compute/docs/disks/hyperdisks#iops) to + provision for the attached hyperdisk. This parameter sets the limit + for disk I/O operations per second. + + throughput - optional + Indicates the throughput + (https://cloud.google.com/compute/docs/disks/hyperdisks#throughput) + to provision for the attached hyperdisk. This parameter sets the + limit for throughput in MiB per second. + + Example: + type='hyperdisk-balanced,iops=5000,throughput=200,size=100G;type=hyperdisk-throughput,size=9000G' + + Attaches two disks to the instances. The first disk is a + hyperdisk-balanced disk with 5000 IOPS, 200 MiB/s throughput, and 100 + GiB size. The second disk is a hyperdisk-throughput disk with 9000 + GiB size. + --secondary-worker-boot-disk-size=SECONDARY_WORKER_BOOT_DISK_SIZE The size of the boot disk. The value must be a whole number followed by a size unit of KB for kilobyte, MB for megabyte, GB for gigabyte, or TB @@ -463,9 +542,6 @@ FLAGS The Google Cloud Storage bucket to use by default to store ephemeral cluster and jobs data, such as Spark and MapReduce history files. - --tier=TIER - Cluster tier. TIER must be one of: premium, standard. - --worker-accelerator=[type=TYPE,[count=COUNT],...] Attaches accelerators, such as GPUs, to the worker instance(s). @@ -478,6 +554,42 @@ FLAGS The number of accelerators to attach to each instance. The default value is 1. + --worker-attached-disks=WORKER_ATTACHED_DISKS + A list of disk configurations to attach to each instance in this group. + Disk configurations are separated by semicolons. Each disk + configuration is a comma-separated list of the following parameters. + + type - required + The type of disk to attach to the instances + (https://cloud.google.com/compute/docs/disks/hyperdisks). + Allowed disk types are: hyperdisk-balanced, hyperdisk-extreme, + hyperdisk-ml, hyperdisk-throughput. + + size - optional + The size of the disk. The value must be a whole number followed by + a size unit GB for gigabyte, or TB for terabyte. For example, + 10GB produces a 10 gigabyte disk. + + iops - optional + Indicates the IOPS + (https://cloud.google.com/compute/docs/disks/hyperdisks#iops) to + provision for the attached hyperdisk. This parameter sets the limit + for disk I/O operations per second. + + throughput - optional + Indicates the throughput + (https://cloud.google.com/compute/docs/disks/hyperdisks#throughput) + to provision for the attached hyperdisk. This parameter sets the + limit for throughput in MiB per second. + + Example: + type='hyperdisk-balanced,iops=5000,throughput=200,size=100G;type=hyperdisk-throughput,size=9000G' + + Attaches two disks to the instances. The first disk is a + hyperdisk-balanced disk with 5000 IOPS, 200 MiB/s throughput, and 100 + GiB size. The second disk is a hyperdisk-throughput disk with 9000 + GiB size. + --worker-boot-disk-provisioned-iops=WORKER_BOOT_DISK_PROVISIONED_IOPS Indicates the IOPS (https://cloud.google.com/compute/docs/disks/hyperdisks#iops) to diff --git a/gcloud/dataproc/workflow-templates/set-managed-cluster b/gcloud/dataproc/workflow-templates/set-managed-cluster index 4167525d8..7793d6ad4 100644 --- a/gcloud/dataproc/workflow-templates/set-managed-cluster +++ b/gcloud/dataproc/workflow-templates/set-managed-cluster @@ -7,11 +7,12 @@ SYNOPSIS (TEMPLATE : --region=REGION) [--autoscaling-policy=AUTOSCALING_POLICY] [--bucket=BUCKET] [--cluster-name=CLUSTER_NAME] [--cluster-type=TYPE] [--confidential-compute] [--dataproc-metastore=DATAPROC_METASTORE] - [--enable-component-gateway] + [--enable-component-gateway] [--engine=ENGINE] [--initialization-action-timeout=TIMEOUT; default="10m"] [--initialization-actions=CLOUD_STORAGE_URI,[...]] [--labels=[KEY=VALUE,...]] [--master-accelerator=[type=TYPE,[count=COUNT],...]] + [--master-attached-disks=MASTER_ATTACHED_DISKS] [--master-boot-disk-provisioned-iops=MASTER_BOOT_DISK_PROVISIONED_IOPS] [--master-boot-disk-provisioned-throughput=MASTER_BOOT_DISK_PROVISIONED_THROUGHPUT] [--master-boot-disk-size=MASTER_BOOT_DISK_SIZE] @@ -29,6 +30,7 @@ SYNOPSIS [--private-ipv6-google-access-type=PRIVATE_IPV6_GOOGLE_ACCESS_TYPE] [--properties=[PREFIX:PROPERTY=VALUE,...]] [--secondary-worker-accelerator=[type=TYPE,[count=COUNT],...]] + [--secondary-worker-attached-disks=SECONDARY_WORKER_ATTACHED_DISKS] [--secondary-worker-boot-disk-size=SECONDARY_WORKER_BOOT_DISK_SIZE] [--secondary-worker-boot-disk-type=SECONDARY_WORKER_BOOT_DISK_TYPE] [--secondary-worker-local-ssd-interface=SECONDARY_WORKER_LOCAL_SSD_INTERFACE] @@ -37,8 +39,9 @@ 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] [--temp-bucket=TEMP_BUCKET] [--tier=TIER] + [--shielded-vtpm] [--temp-bucket=TEMP_BUCKET] [--worker-accelerator=[type=TYPE,[count=COUNT],...]] + [--worker-attached-disks=WORKER_ATTACHED_DISKS] [--worker-boot-disk-provisioned-iops=WORKER_BOOT_DISK_PROVISIONED_IOPS] [--worker-boot-disk-provisioned-throughput=WORKER_BOOT_DISK_PROVISIONED_THROUGHPUT] [--worker-boot-disk-size=WORKER_BOOT_DISK_SIZE] @@ -154,6 +157,9 @@ FLAGS Enable access to the web UIs of selected components on the cluster through the component gateway. + --engine=ENGINE + Cluster engine. ENGINE must be one of: default, lightning. + --initialization-action-timeout=TIMEOUT; default="10m" The maximum duration of each initialization action. See $ gcloud topic datetimes for information on duration formats. @@ -182,6 +188,42 @@ FLAGS The number of accelerators to attach to each instance. The default value is 1. + --master-attached-disks=MASTER_ATTACHED_DISKS + A list of disk configurations to attach to each instance in this group. + Disk configurations are separated by semicolons. Each disk + configuration is a comma-separated list of the following parameters. + + type - required + The type of disk to attach to the instances + (https://cloud.google.com/compute/docs/disks/hyperdisks). + Allowed disk types are: hyperdisk-balanced, hyperdisk-extreme, + hyperdisk-ml, hyperdisk-throughput. + + size - optional + The size of the disk. The value must be a whole number followed by + a size unit GB for gigabyte, or TB for terabyte. For example, + 10GB produces a 10 gigabyte disk. + + iops - optional + Indicates the IOPS + (https://cloud.google.com/compute/docs/disks/hyperdisks#iops) to + provision for the attached hyperdisk. This parameter sets the limit + for disk I/O operations per second. + + throughput - optional + Indicates the throughput + (https://cloud.google.com/compute/docs/disks/hyperdisks#throughput) + to provision for the attached hyperdisk. This parameter sets the + limit for throughput in MiB per second. + + Example: + type='hyperdisk-balanced,iops=5000,throughput=200,size=100G;type=hyperdisk-throughput,size=9000G' + + Attaches two disks to the instances. The first disk is a + hyperdisk-balanced disk with 5000 IOPS, 200 MiB/s throughput, and 100 + GiB size. The second disk is a hyperdisk-throughput disk with 9000 + GiB size. + --master-boot-disk-provisioned-iops=MASTER_BOOT_DISK_PROVISIONED_IOPS Indicates the IOPS (https://cloud.google.com/compute/docs/disks/hyperdisks#iops) to @@ -317,6 +359,42 @@ FLAGS The number of accelerators to attach to each instance. The default value is 1. + --secondary-worker-attached-disks=SECONDARY_WORKER_ATTACHED_DISKS + A list of disk configurations to attach to each instance in this group. + Disk configurations are separated by semicolons. Each disk + configuration is a comma-separated list of the following parameters. + + type - required + The type of disk to attach to the instances + (https://cloud.google.com/compute/docs/disks/hyperdisks). + Allowed disk types are: hyperdisk-balanced, hyperdisk-extreme, + hyperdisk-ml, hyperdisk-throughput. + + size - optional + The size of the disk. The value must be a whole number followed by + a size unit GB for gigabyte, or TB for terabyte. For example, + 10GB produces a 10 gigabyte disk. + + iops - optional + Indicates the IOPS + (https://cloud.google.com/compute/docs/disks/hyperdisks#iops) to + provision for the attached hyperdisk. This parameter sets the limit + for disk I/O operations per second. + + throughput - optional + Indicates the throughput + (https://cloud.google.com/compute/docs/disks/hyperdisks#throughput) + to provision for the attached hyperdisk. This parameter sets the + limit for throughput in MiB per second. + + Example: + type='hyperdisk-balanced,iops=5000,throughput=200,size=100G;type=hyperdisk-throughput,size=9000G' + + Attaches two disks to the instances. The first disk is a + hyperdisk-balanced disk with 5000 IOPS, 200 MiB/s throughput, and 100 + GiB size. The second disk is a hyperdisk-throughput disk with 9000 + GiB size. + --secondary-worker-boot-disk-size=SECONDARY_WORKER_BOOT_DISK_SIZE The size of the boot disk. The value must be a whole number followed by a size unit of KB for kilobyte, MB for megabyte, GB for gigabyte, or TB @@ -374,9 +452,6 @@ FLAGS The Google Cloud Storage bucket to use by default to store ephemeral cluster and jobs data, such as Spark and MapReduce history files. - --tier=TIER - Cluster tier. TIER must be one of: premium, standard. - --worker-accelerator=[type=TYPE,[count=COUNT],...] Attaches accelerators, such as GPUs, to the worker instance(s). @@ -389,6 +464,42 @@ FLAGS The number of accelerators to attach to each instance. The default value is 1. + --worker-attached-disks=WORKER_ATTACHED_DISKS + A list of disk configurations to attach to each instance in this group. + Disk configurations are separated by semicolons. Each disk + configuration is a comma-separated list of the following parameters. + + type - required + The type of disk to attach to the instances + (https://cloud.google.com/compute/docs/disks/hyperdisks). + Allowed disk types are: hyperdisk-balanced, hyperdisk-extreme, + hyperdisk-ml, hyperdisk-throughput. + + size - optional + The size of the disk. The value must be a whole number followed by + a size unit GB for gigabyte, or TB for terabyte. For example, + 10GB produces a 10 gigabyte disk. + + iops - optional + Indicates the IOPS + (https://cloud.google.com/compute/docs/disks/hyperdisks#iops) to + provision for the attached hyperdisk. This parameter sets the limit + for disk I/O operations per second. + + throughput - optional + Indicates the throughput + (https://cloud.google.com/compute/docs/disks/hyperdisks#throughput) + to provision for the attached hyperdisk. This parameter sets the + limit for throughput in MiB per second. + + Example: + type='hyperdisk-balanced,iops=5000,throughput=200,size=100G;type=hyperdisk-throughput,size=9000G' + + Attaches two disks to the instances. The first disk is a + hyperdisk-balanced disk with 5000 IOPS, 200 MiB/s throughput, and 100 + GiB size. The second disk is a hyperdisk-throughput disk with 9000 + GiB size. + --worker-boot-disk-provisioned-iops=WORKER_BOOT_DISK_PROVISIONED_IOPS Indicates the IOPS (https://cloud.google.com/compute/docs/disks/hyperdisks#iops) to diff --git a/gcloud/firestore/databases/create b/gcloud/firestore/databases/create index f592ba5f5..97f81159f 100644 --- a/gcloud/firestore/databases/create +++ b/gcloud/firestore/databases/create @@ -4,6 +4,7 @@ NAME SYNOPSIS gcloud firestore databases create --location=LOCATION + [--concurrency-mode=CONCURRENCY_MODE] [--database=DATABASE; default="(default)"] [--delete-protection] [--edition=EDITION; default="standard"] [--enable-firestore-data-access] @@ -81,6 +82,14 @@ REQUIRED FLAGS $ gcloud firestore databases create --location='us-east1' OPTIONAL FLAGS + --concurrency-mode=CONCURRENCY_MODE + The concurrency control mode to use for this database. + + When not specified, Firestore will pick a default concurrency mode + based on the database edition. + + CONCURRENCY_MODE must be one of: optimistic, pessimistic. + --database=DATABASE; default="(default)" The ID to use for the database, which will become the final component of the database's resource name. If database ID is not provided, diff --git a/gcloud/firestore/databases/update b/gcloud/firestore/databases/update index 9f6410b68..3866a4bcf 100644 --- a/gcloud/firestore/databases/update +++ b/gcloud/firestore/databases/update @@ -3,7 +3,8 @@ NAME Cloud Firestore database SYNOPSIS - gcloud firestore databases update [--async] [--database=DATABASE] + gcloud firestore databases update [--async] + [--concurrency-mode=CONCURRENCY_MODE] [--database=DATABASE] [--delete-protection] [--enable-pitr] [--type=TYPE] [GCLOUD_WIDE_FLAG ...] @@ -21,6 +22,10 @@ FLAGS Return immediately, without waiting for the operation in progress to complete. + --concurrency-mode=CONCURRENCY_MODE + The concurrency control mode to use for this database. CONCURRENCY_MODE + must be one of: optimistic, pessimistic. + Database resource - Cloud Firestore database to update. This represents a Cloud resource. (NOTE) Some attributes are not given arguments in this group but can be set in other ways. diff --git a/gcloud/firestore/fields/ttls/update b/gcloud/firestore/fields/ttls/update index edb554546..a70c9b061 100644 --- a/gcloud/firestore/fields/ttls/update +++ b/gcloud/firestore/fields/ttls/update @@ -5,7 +5,9 @@ NAME SYNOPSIS gcloud firestore fields ttls update (FIELD : --collection-group=COLLECTION_GROUP --database=DATABASE) - (--disable-ttl | --enable-ttl) [--async] [GCLOUD_WIDE_FLAG ...] + (--disable-ttl + | [--enable-ttl : --expiration-offset=EXPIRATION_OFFSET]) [--async] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION Update the TTL configuration of the given field. @@ -27,6 +29,12 @@ EXAMPLES $ gcloud firestore fields ttls update expiry \ --collection-group=Events --disable-ttl + The following command sets the expiry field of the Events collection group + (kind) to be the TTL field, with an expiration offset of one week: + + $ gcloud firestore fields ttls update expiry \ + --collection-group=Events --enable-ttl --expiration-offset=7d + POSITIONAL ARGUMENTS Field resource - Field to update. The arguments in this group can be used to specify the attributes of this resource. (NOTE) Some attributes are not @@ -72,8 +80,18 @@ REQUIRED FLAGS --disable-ttl Set to make this field no longer the TTL for its collection group. - --enable-ttl - Set to enable this field as the TTL for its collection group. + Or at least one of these can be specified: + + --enable-ttl + Set to enable this field as the TTL for its collection group. + + This flag argument must be specified if any of the other arguments + in this group are specified. + + --expiration-offset=EXPIRATION_OFFSET + The offset, relative to the timestamp value from the TTL-enabled + field, used to determine the document's expiration time. If unset, + defaults to 0. OPTIONAL FLAGS --async diff --git a/gcloud/firestore/indexes/composite/create b/gcloud/firestore/indexes/composite/create index 9d1263116..b6d37f52e 100644 --- a/gcloud/firestore/indexes/composite/create +++ b/gcloud/firestore/indexes/composite/create @@ -120,7 +120,7 @@ OPTIONAL FLAGS 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. + 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: diff --git a/gcloud/iam/help b/gcloud/iam/help index 83a31f209..cb9a83fb2 100644 --- a/gcloud/iam/help +++ b/gcloud/iam/help @@ -34,7 +34,7 @@ GROUPS Manage IAM deny policies. policy-bindings - Manage policy bindings. + Manage PolicyBinding instances. principal-access-boundary-policies Manage principal access boundary policies. diff --git a/gcloud/iam/policy-bindings/help b/gcloud/iam/policy-bindings/help index 316eeeb15..13fe020e9 100644 --- a/gcloud/iam/policy-bindings/help +++ b/gcloud/iam/policy-bindings/help @@ -1,11 +1,11 @@ NAME - gcloud iam policy-bindings - manage policy bindings + gcloud iam policy-bindings - manage PolicyBinding instances SYNOPSIS gcloud iam policy-bindings COMMAND [GCLOUD_WIDE_FLAG ...] DESCRIPTION - Manage policy bindings. + Manage PolicyBinding instances. GCLOUD WIDE FLAGS These flags are available to all commands: --help. diff --git a/gcloud/iam/workforce-pools/providers/create-oidc b/gcloud/iam/workforce-pools/providers/create-oidc index cba3c3709..bbd906a49 100644 --- a/gcloud/iam/workforce-pools/providers/create-oidc +++ b/gcloud/iam/workforce-pools/providers/create-oidc @@ -202,6 +202,9 @@ REQUIRED FLAGS Each additional scope may be at most 256 characters. A maximum of 10 additional scopes may be configured. + Updating this field replaces any existing values. Include the full + list of additional scopes to avoid losing existing values. + OPTIONAL FLAGS --async Return immediately, without waiting for the operation in progress to diff --git a/gcloud/iam/workforce-pools/providers/update-oidc b/gcloud/iam/workforce-pools/providers/update-oidc index bbac60dc3..529855383 100644 --- a/gcloud/iam/workforce-pools/providers/update-oidc +++ b/gcloud/iam/workforce-pools/providers/update-oidc @@ -239,6 +239,9 @@ FLAGS Each additional scope may be at most 256 characters. A maximum of 10 additional scopes may be configured. + Updating this field replaces any existing values. Include the full list + of additional scopes to avoid losing existing values. + --web-sso-assertion-claims-behavior=WEB_SSO_ASSERTION_CLAIMS_BEHAVIOR The behavior for how OIDC Claims are included in the assertion object used for attribute mapping and attribute condition. Use diff --git a/gcloud/kms/asymmetric-sign b/gcloud/kms/asymmetric-sign index df95252e2..3c2e11892 100644 --- a/gcloud/kms/asymmetric-sign +++ b/gcloud/kms/asymmetric-sign @@ -19,6 +19,11 @@ DESCRIPTION received from Cloud KMS. Use --skip-integrity-verification to disable integrity verification. + For the ML-DSA EXTERNAL-MU algorithms, the digest external-mu should be + used that depends on the public key. This command will fetch the public key + from KMS and compute the external-mu digest. Note that this requires signer + permissions on the associated CryptoKeyVersion. + EXAMPLES The following command will read the file '/tmp/my/file.to.sign', digest it with the digest algorithm 'sha256' and sign it using the asymmetric @@ -40,7 +45,7 @@ REQUIRED FLAGS OPTIONAL FLAGS --digest-algorithm=DIGEST_ALGORITHM The algorithm to digest the input. DIGEST_ALGORITHM must be one of: - sha256, sha384, sha512. + external-mu, sha256, sha384, sha512. --key=KEY to use for signing. diff --git a/gcloud/kms/key-handles/create b/gcloud/kms/key-handles/create index a66ba826d..3a95b7d3d 100644 --- a/gcloud/kms/key-handles/create +++ b/gcloud/kms/key-handles/create @@ -19,8 +19,8 @@ EXAMPLES $ gcloud kms key-handles create --key-handle-id=my-key-handle \ --location=global --resource-type=compute.googleapis.com/Disk - In case we want to generate a random KeyHandle id, we can use the - --generate-key-handle-id flag instead of the --key-handle-id flag. + To generate a random KeyHandle id, the --generate-key-handle-id flag can be + used instead of --key-handle-id. REQUIRED FLAGS Location resource - The KMS location resource. This represents a Cloud diff --git a/gcloud/kms/single-tenant-hsm/create b/gcloud/kms/single-tenant-hsm/create index 0c81534b9..6e8955df5 100644 --- a/gcloud/kms/single-tenant-hsm/create +++ b/gcloud/kms/single-tenant-hsm/create @@ -3,7 +3,7 @@ NAME SYNOPSIS gcloud kms single-tenant-hsm create --location=LOCATION - --total-approver-count=TOTAL_APPROVER_COUNT + --total-approver-count=TOTAL_APPROVER_COUNT [--key-portability-enabled] [--single-tenant-hsm-instance-id=SINGLE_TENANT_HSM_INSTANCE_ID] [GCLOUD_WIDE_FLAG ...] @@ -46,6 +46,10 @@ REQUIRED FLAGS to 16. OPTIONAL FLAGS + --key-portability-enabled + If set, the single tenant HSM instance will be able to perform key + portability operations. + --single-tenant-hsm-instance-id=SINGLE_TENANT_HSM_INSTANCE_ID Specify an ID for the single tenant HSM instance. It must be unique within a location and match the regular expression [a-zA-Z0-9-]{1,63}. diff --git a/gcloud/kms/single-tenant-hsm/describe b/gcloud/kms/single-tenant-hsm/describe index d19c3f50a..84ddedbe0 100644 --- a/gcloud/kms/single-tenant-hsm/describe +++ b/gcloud/kms/single-tenant-hsm/describe @@ -10,14 +10,14 @@ SYNOPSIS DESCRIPTION Returns metadata for the given single tenant HSM instance. - ## EXAMPLES - +EXAMPLES The following command returns the metadata for the single tenant HSM - instance with the name my_sthi in the location us-east1`using the fully + instance with the name my_sthi in the location us-east1 using the fully specified name: - $ gcloud kms single-tenant-hsm describe - projects/my-project/locations/us-east1/singleTenantHsmInstances/mysthi + $ gcloud kms single-tenant-hsm describe \ + projects/my-project/locations/us-east1/\ + singleTenantHsmInstances/mysthi The following command returns the metadata for the singletenanthsm instance with the name mysthi in the location us-east1 using the location and diff --git a/gcloud/kms/single-tenant-hsm/proposal/describe b/gcloud/kms/single-tenant-hsm/proposal/describe index e9f9566ee..71174d9ba 100644 --- a/gcloud/kms/single-tenant-hsm/proposal/describe +++ b/gcloud/kms/single-tenant-hsm/proposal/describe @@ -13,16 +13,16 @@ EXAMPLES instance proposal with the name my_proposal, of the instance my_sthi, and in the location us-east1 using the fully specified resource name. - $ gcloud kms single-tenant-hsm proposal describe \ - projects/my-project/locations/us-east1/\ - singleTenantHsmInstances/ my_sthi/proposals/my_proposal ``` + $ gcloud kms single-tenant-hsm proposal describe \ + projects/my-project/locations/us-east1/\ + singleTenantHsmInstances/my_sthi/proposals/my_proposal - The following command returns the metadata for the single tenant HSM instance - proposal with the name `my_proposal`, of the instance `my_sthi`, and in the - location `us-east1` using the location, instance id, and proposal id. + The following command returns the metadata for the single tenant HSM + instance proposal with the name my_proposal, of the instance my_sthi, and + in the location us-east1 using the location, instance id, and proposal id. $ gcloud kms single-tenant-hsm proposal describe my_proposal \ - --single_tenant_hsm_instance=my_sthi --location=us-east1 ``` + --single_tenant_hsm_instance=my_sthi --location=us-east1 POSITIONAL ARGUMENTS SingleTenantHsmInstanceProposal resource - The KMS single tenant HSM diff --git a/gcloud/logging/help b/gcloud/logging/help index c1c3cafc1..35739152b 100644 --- a/gcloud/logging/help +++ b/gcloud/logging/help @@ -33,9 +33,15 @@ GROUPS operations Manage long running operations. + recent-queries + Manage Cloud Logging recent queries. + resource-descriptors Get information about resource descriptors. + saved-queries + Manage Cloud Logging saved queries. + scopes Manages Cloud Logging log scopes. diff --git a/gcloud/logging/recent-queries/help b/gcloud/logging/recent-queries/help new file mode 100644 index 000000000..67d2ae03e --- /dev/null +++ b/gcloud/logging/recent-queries/help @@ -0,0 +1,21 @@ +NAME + gcloud logging recent-queries - manage Cloud Logging recent queries + +SYNOPSIS + gcloud logging recent-queries COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Commands for managing Cloud Logging recent queries. A recent query + describes a query executed on the Logs Explorer or Log Analytics page + within the last ~ 30 days. + +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 Logging recent queries. diff --git a/gcloud/logging/recent-queries/list b/gcloud/logging/recent-queries/list new file mode 100644 index 000000000..5a3c6f29d --- /dev/null +++ b/gcloud/logging/recent-queries/list @@ -0,0 +1,89 @@ +NAME + gcloud logging recent-queries list - list Logging recent queries + +SYNOPSIS + gcloud logging recent-queries list --location=LOCATION + [--billing-account=BILLING_ACCOUNT_ID | --folder=FOLDER_ID + | --organization=ORGANIZATION_ID | --project=PROJECT_ID] + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + List recent queries for a parent resource (project, billing account, + folder, or organization). + +EXAMPLES + To list recent queries in a project, run: + + $ gcloud logging recent-queries list --project=my-project \ + --location=global + +REQUIRED FLAGS + --location=LOCATION + Location of the recent queries to list. + +FLAGS + At most one of these can be specified: + + --billing-account=BILLING_ACCOUNT_ID + Billing account of the parent resource for recent queries to list. + + --folder=FOLDER_ID + Folder of the parent resource for recent queries to list. + + --organization=ORGANIZATION_ID + Organization of the parent resource for recent queries to list. + + --project=PROJECT_ID + Project of the parent resource for recent queries to list. + + The Google Cloud project ID to use for this invocation. If omitted, + then the current project is assumed; the current project can be + listed using gcloud config list --format='text(core.project)' and can + be set using gcloud config set project PROJECTID. + + --project and its fallback core/project property play two roles in + the invocation. It specifies the project of the resource to operate + on. It also specifies the project for API enablement check, quota, + and billing. To specify a different project for quota and billing, + use --billing-project or billing/quota_project property. + +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. diff --git a/gcloud/logging/saved-queries/create b/gcloud/logging/saved-queries/create new file mode 100644 index 000000000..ba303ccca --- /dev/null +++ b/gcloud/logging/saved-queries/create @@ -0,0 +1,101 @@ +NAME + gcloud logging saved-queries create - create a Logging saved query + +SYNOPSIS + gcloud logging saved-queries create --display-name=DISPLAY_NAME + --location=LOCATION --visibility=VISIBILITY + (--sql-query-text=SQL_QUERY_TEXT | --log-filter=LOG_FILTER + --summary-fields=SUMMARY_FIELDS --summary-field-end=SUMMARY_FIELD_END + | --summary-field-start=SUMMARY_FIELD_START) + [--description=DESCRIPTION] [--id=ID] + [--billing-account=BILLING_ACCOUNT_ID | --folder=FOLDER_ID + | --organization=ORGANIZATION_ID | --project=PROJECT_ID] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Create a saved query. + +EXAMPLES + To create a saved query in a project, run: + + $ gcloud logging saved-queries create --id=my-saved-query \ + --location=global --display-name="My saved query" \ + --visibility=private --sql-query-text="SELECT * FROM my_table" + +REQUIRED FLAGS + --display-name=DISPLAY_NAME + Display name for the saved query. + + --location=LOCATION + Location to create the saved query in. + + --visibility=VISIBILITY + Visibility of the saved query. VISIBILITY must be one of: private, + shared. + + Exactly one of these must be specified: + + --sql-query-text=SQL_QUERY_TEXT + SQL query text. + + Or at least one of these can be specified: + + --log-filter=LOG_FILTER + Filter expression for the log-based query. + + --summary-fields=SUMMARY_FIELDS + Comma-separated list of fields to include in the summary. This flag + must be specified if --summary-field-start or --summary-field-end + are provided. + + At most one of these can be specified: + + --summary-field-end=SUMMARY_FIELD_END + Setting for number of characters to display for each summary + field: characters will be counted from the end of the string. + Requires the --summary-fields flag to be specified as well. + + --summary-field-start=SUMMARY_FIELD_START + Setting for number of characters to display for each summary + field: characters will be counted from the start of the string. + Requires the --summary-fields flag to be specified as well. + +OPTIONAL FLAGS + --description=DESCRIPTION + A textual description for the saved query. + + --id=ID + ID of the saved query to create. + + At most one of these can be specified: + + --billing-account=BILLING_ACCOUNT_ID + Billing account of the saved query to create. + + --folder=FOLDER_ID + Folder of the saved query to create. + + --organization=ORGANIZATION_ID + Organization of the saved query to create. + + --project=PROJECT_ID + Project of the saved query to create. + + The Google Cloud project ID to use for this invocation. If omitted, + then the current project is assumed; the current project can be + listed using gcloud config list --format='text(core.project)' and can + be set using gcloud config set project PROJECTID. + + --project and its fallback core/project property play two roles in + the invocation. It specifies the project of the resource to operate + on. It also specifies the project for API enablement check, quota, + and billing. To specify a different project for quota and billing, + use --billing-project or billing/quota_project property. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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/logging/saved-queries/delete b/gcloud/logging/saved-queries/delete new file mode 100644 index 000000000..75470a690 --- /dev/null +++ b/gcloud/logging/saved-queries/delete @@ -0,0 +1,59 @@ +NAME + gcloud logging saved-queries delete - delete a Logging saved query + +SYNOPSIS + gcloud logging saved-queries delete ID --location=LOCATION + [--billing-account=BILLING_ACCOUNT_ID | --folder=FOLDER_ID + | --organization=ORGANIZATION_ID | --project=PROJECT_ID] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Delete a saved query. + +EXAMPLES + To delete a saved query in a project, run: + + $ gcloud logging saved-queries delete MY_QUERY_ID \ + --project=MY_PROJECT_ID --location=global + +POSITIONAL ARGUMENTS + ID + ID of the saved query to delete. + +REQUIRED FLAGS + --location=LOCATION + Location of the saved query to delete. + +OPTIONAL FLAGS + At most one of these can be specified: + + --billing-account=BILLING_ACCOUNT_ID + Billing account of the saved query to delete. + + --folder=FOLDER_ID + Folder of the saved query to delete. + + --organization=ORGANIZATION_ID + Organization of the saved query to delete. + + --project=PROJECT_ID + Project of the saved query to delete. + + The Google Cloud project ID to use for this invocation. If omitted, + then the current project is assumed; the current project can be + listed using gcloud config list --format='text(core.project)' and can + be set using gcloud config set project PROJECTID. + + --project and its fallback core/project property play two roles in + the invocation. It specifies the project of the resource to operate + on. It also specifies the project for API enablement check, quota, + and billing. To specify a different project for quota and billing, + use --billing-project or billing/quota_project property. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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/logging/saved-queries/describe b/gcloud/logging/saved-queries/describe new file mode 100644 index 000000000..81bbb76e5 --- /dev/null +++ b/gcloud/logging/saved-queries/describe @@ -0,0 +1,60 @@ +NAME + gcloud logging saved-queries describe - a command that describes a Logging + saved query + +SYNOPSIS + gcloud logging saved-queries describe ID --location=LOCATION + [--billing-account=BILLING_ACCOUNT_ID | --folder=FOLDER_ID + | --organization=ORGANIZATION_ID | --project=PROJECT_ID] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Describe a saved query. + +EXAMPLES + To describe a saved query in a project, run: + + $ gcloud logging saved-queries describe ID --project=PROJECT_ID \ + --location=LOCATION + +POSITIONAL ARGUMENTS + ID + ID of the saved query to describe. + +REQUIRED FLAGS + --location=LOCATION + Location of the saved query to describe. + +OPTIONAL FLAGS + At most one of these can be specified: + + --billing-account=BILLING_ACCOUNT_ID + Billing account of the saved query to describe. + + --folder=FOLDER_ID + Folder of the saved query to describe. + + --organization=ORGANIZATION_ID + Organization of the saved query to describe. + + --project=PROJECT_ID + Project of the saved query to describe. + + The Google Cloud project ID to use for this invocation. If omitted, + then the current project is assumed; the current project can be + listed using gcloud config list --format='text(core.project)' and can + be set using gcloud config set project PROJECTID. + + --project and its fallback core/project property play two roles in + the invocation. It specifies the project of the resource to operate + on. It also specifies the project for API enablement check, quota, + and billing. To specify a different project for quota and billing, + use --billing-project or billing/quota_project property. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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/logging/saved-queries/help b/gcloud/logging/saved-queries/help new file mode 100644 index 000000000..d5517a488 --- /dev/null +++ b/gcloud/logging/saved-queries/help @@ -0,0 +1,32 @@ +NAME + gcloud logging saved-queries - manage Cloud Logging saved queries + +SYNOPSIS + gcloud logging saved-queries COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Commands for managing Cloud Logging saved queries. A saved query describes + a query that has been saved by a user. + +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 Logging saved query. + + delete + Delete a Logging saved query. + + describe + A command that describes a Logging saved query. + + list + List Logging saved queries. + + update + Update Logging saved queries. diff --git a/gcloud/logging/saved-queries/list b/gcloud/logging/saved-queries/list new file mode 100644 index 000000000..41970cff6 --- /dev/null +++ b/gcloud/logging/saved-queries/list @@ -0,0 +1,89 @@ +NAME + gcloud logging saved-queries list - list Logging saved queries + +SYNOPSIS + gcloud logging saved-queries list --location=LOCATION + [--billing-account=BILLING_ACCOUNT_ID | --folder=FOLDER_ID + | --organization=ORGANIZATION_ID | --project=PROJECT_ID] + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + List saved queries for a parent resource. (project, billing account, + folder, or organization) + +EXAMPLES + To list saved queries in a project, run: + + $ gcloud logging saved-queries list --location=LOCATION \ + --project=PROJECT_ID + +REQUIRED FLAGS + --location=LOCATION + Location of the saved queries to list. + +FLAGS + At most one of these can be specified: + + --billing-account=BILLING_ACCOUNT_ID + Billing account of the parent resource for saved queries to list. + + --folder=FOLDER_ID + Folder of the parent resource for saved queries to list. + + --organization=ORGANIZATION_ID + Organization of the parent resource for saved queries to list. + + --project=PROJECT_ID + Project of the parent resource for saved queries to list. + + The Google Cloud project ID to use for this invocation. If omitted, + then the current project is assumed; the current project can be + listed using gcloud config list --format='text(core.project)' and can + be set using gcloud config set project PROJECTID. + + --project and its fallback core/project property play two roles in + the invocation. It specifies the project of the resource to operate + on. It also specifies the project for API enablement check, quota, + and billing. To specify a different project for quota and billing, + use --billing-project or billing/quota_project property. + +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. diff --git a/gcloud/logging/saved-queries/update b/gcloud/logging/saved-queries/update new file mode 100644 index 000000000..549e68769 --- /dev/null +++ b/gcloud/logging/saved-queries/update @@ -0,0 +1,105 @@ +NAME + gcloud logging saved-queries update - update Logging saved queries + +SYNOPSIS + gcloud logging saved-queries update SAVED_QUERY_ID + [--description=DESCRIPTION] [--display-name=DISPLAY_NAME] + [--location=LOCATION] [--name=NAME] [--visibility=VISIBILITY] + [--billing-account=BILLING_ACCOUNT_ID | --folder=FOLDER_ID + | --organization=ORGANIZATION_ID | --project=PROJECT_ID] + [--sql-query-text=SQL_QUERY_TEXT + | --add-summary-field=ADD_SUMMARY_FIELD --clear-summary-fields + --log-filter=LOG_FILTER --remove-summary-field=REMOVE_SUMMARY_FIELD + --summary-field-end=SUMMARY_FIELD_END + | --summary-field-start=SUMMARY_FIELD_START] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Update a saved query. + +EXAMPLES + To update the display name and description of a saved query, run: + + $ gcloud logging saved-queries update my-saved-query \ + --display-name="New Name" --description="New Description" + +POSITIONAL ARGUMENTS + SAVED_QUERY_ID + ID of the saved query to update. + +FLAGS + --description=DESCRIPTION + The description of the saved query. + + --display-name=DISPLAY_NAME + The display name of the saved query. + + --location=LOCATION + Location of the saved query. + + --name=NAME + The resource name of the saved query. + + --visibility=VISIBILITY + The visibility of the saved query. + + At most one of these can be specified: + + --billing-account=BILLING_ACCOUNT_ID + Billing account of the saved query to update. + + --folder=FOLDER_ID + Folder of the saved query to update. + + --organization=ORGANIZATION_ID + Organization of the saved query to update. + + --project=PROJECT_ID + Project of the saved query to update. + + The Google Cloud project ID to use for this invocation. If omitted, + then the current project is assumed; the current project can be + listed using gcloud config list --format='text(core.project)' and can + be set using gcloud config set project PROJECTID. + + --project and its fallback core/project property play two roles in + the invocation. It specifies the project of the resource to operate + on. It also specifies the project for API enablement check, quota, + and billing. To specify a different project for quota and billing, + use --billing-project or billing/quota_project property. + + At most one of these can be specified: + + --sql-query-text=SQL_QUERY_TEXT + The SQL query text. If this argument is specified, no LoggingQuery + arguments (--log-filter, --add-summary-field, etc.) may be specified. + + Or at least one of these can be specified: + + --add-summary-field=ADD_SUMMARY_FIELD + Add a summary field. + + --clear-summary-fields + Clear all summary fields. + + --log-filter=LOG_FILTER + The logging filter. If this argument is specified, --sql-query-text + may not be specified. + + --remove-summary-field=REMOVE_SUMMARY_FIELD + Remove a summary field. + + At most one of these can be specified: + + --summary-field-end=SUMMARY_FIELD_END + Summary field end. + + --summary-field-start=SUMMARY_FIELD_START + Summary field start. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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/lustre/instances/update b/gcloud/lustre/instances/update index e6d8398c4..c3ec066d5 100644 --- a/gcloud/lustre/instances/update +++ b/gcloud/lustre/instances/update @@ -17,8 +17,6 @@ SYNOPSIS [name=NAME],[squashMode=SQUASHMODE] --clear-access-rules | --remove-access-rules=[ipAddressRanges=IPADDRESSRANGES], [name=NAME],[squashMode=SQUASHMODE]] - [--clear-dynamic-tier-options - --dynamic-tier-options-mode=DYNAMIC_TIER_OPTIONS_MODE] [--clear-maintenance-policy --maintenance-policy-exclusion-window=[endDate=ENDDATE], [startDate=STARTDATE],[time=TIME] @@ -277,20 +275,6 @@ FLAGS --remove-access-rules=path_to_file.(yaml|json) - Dynamic tier options for a Managed Lustre instance. - - --clear-dynamic-tier-options - Set instance.dynamicTierOptions back to default value. - - --dynamic-tier-options-mode=DYNAMIC_TIER_OPTIONS_MODE - The dynamic tier mode of the instance. DYNAMIC_TIER_OPTIONS_MODE must - be one of: - - default-cache - The dynamic tier is enabled. - disabled - The dynamic tier is explicitly disabled. - Defines a maintenance policy for a resource. --clear-maintenance-policy diff --git a/gcloud/memorystore/instances/create b/gcloud/memorystore/instances/create index a877ce5e4..dc1ad0145 100644 --- a/gcloud/memorystore/instances/create +++ b/gcloud/memorystore/instances/create @@ -280,12 +280,24 @@ FLAGS Machine type for individual nodes of the instance. NODE_TYPE must be one of: + custom-micro + Custom micro. + custom-mini + Custom mini. + custom-pico + Custom pico. + highcpu-medium + High cpu medium. + highmem-2xlarge + High memory 2xlarge. highmem-medium High memory medium. highmem-xlarge High memory extra large. shared-core-nano Shared core nano. + standard-large + Standard large. standard-small Standard small. diff --git a/gcloud/memorystore/instances/update b/gcloud/memorystore/instances/update index 634853705..cd8f30dfc 100644 --- a/gcloud/memorystore/instances/update +++ b/gcloud/memorystore/instances/update @@ -135,12 +135,24 @@ FLAGS Machine type for individual nodes of the instance. NODE_TYPE must be one of: + custom-micro + Custom micro. + custom-mini + Custom mini. + custom-pico + Custom pico. + highcpu-medium + High cpu medium. + highmem-2xlarge + High memory 2xlarge. highmem-medium High memory medium. highmem-xlarge High memory extra large. shared-core-nano Shared core nano. + standard-large + Standard large. standard-small Standard small. diff --git a/gcloud/migration/vms/image-imports/help b/gcloud/migration/vms/image-imports/help index 84bf6ae42..f586c8800 100644 --- a/gcloud/migration/vms/image-imports/help +++ b/gcloud/migration/vms/image-imports/help @@ -6,22 +6,22 @@ SYNOPSIS gcloud migration vms image-imports COMMAND [GCLOUD_WIDE_FLAG ...] DESCRIPTION - gcloud alpha migration vms image-imports provides a more robust and better + gcloud migration vms image-imports provides a more robust and better supported method for importing images to Google Compute Engine. Other image-related operations (for example, list) can be done using gcloud compute images, as usual. - The commands use VM Migartion API which supports importing of an image from + The commands use VM Migration API which supports importing of an image from a Google Cloud Storage file (gs://...) to a target project. VM Migration API must be enabled in your project. - gcloud alpha migration vms image-imports create creates an Image Import - resource with a nested Image Import Job resource. The Image Import Job - resource tracks the image import progress. After the Image Import Job - completes, successfully or otherwise, there's no further use for the Image - Import resource. + gcloud migration vms image-imports create creates an Image Import resource + with a nested Image Import Job resource. The Image Import Job resource + tracks the image import progress. After the Image Import Job completes, + successfully or otherwise, there's no further use for the Image Import + resource. - The image is imported to a Google Cloud Project, desginated by the Target + The image is imported to a Google Cloud Project, designated by the Target Project resource. To get a list of Target Projects, run the gcloud alpha migration vms target-projects list command. Use the Google Cloud console to add target project resources. For information on adding target projects, diff --git a/gcloud/netapp/storage-pools/create b/gcloud/netapp/storage-pools/create index fa70dd91b..c20b82086 100644 --- a/gcloud/netapp/storage-pools/create +++ b/gcloud/netapp/storage-pools/create @@ -8,10 +8,11 @@ SYNOPSIS [--allow-auto-tiering=ALLOW_AUTO_TIERING] [--async] [--custom-performance-enabled=CUSTOM_PERFORMANCE_ENABLED] [--description=DESCRIPTION] [--enable-ldap=ENABLE_LDAP] - [--kms-config=KMS_CONFIG] [--labels=[KEY=VALUE,...]] + [--kms-config=KMS_CONFIG] [--labels=[KEY=VALUE,...]] [--mode=MODE] [--qos-type=QOS_TYPE] [--replica-zone=REPLICA_ZONE] - [--total-iops=TOTAL_IOPS] [--total-throughput=TOTAL_THROUGHPUT] - [--type=TYPE] [--zone=ZONE] [GCLOUD_WIDE_FLAG ...] + [--scale-type=SCALE_TYPE] [--total-iops=TOTAL_IOPS] + [--total-throughput=TOTAL_THROUGHPUT] [--type=TYPE] [--zone=ZONE] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION Creates a Storage Pool to contain Volumes with a specified Service Level @@ -186,6 +187,12 @@ OPTIONAL FLAGS contain only hyphens (-), underscores (_), lowercase characters, and numbers. + --mode=MODE + The mode of the Storage Pool. ONTAP mode is for performing ONTAP + operations with ONTAP Mode APIs. DEFAULT mode is for performing + operations allowed with NetApp Files APIs. MODE must be one of: + default, ontap. + --qos-type=QOS_TYPE Quality of service (QoS) type for the Storage Pool. QOS_TYPE must be one of: auto, manual, qos-type-unspecified. @@ -193,6 +200,11 @@ OPTIONAL FLAGS --replica-zone=REPLICA_ZONE String indicating replica zone for the Storage Pool + --scale-type=SCALE_TYPE + The scale type of the Storage Pool. default scale type is for standard + capacity and performance. scaleout scale type is for higher capacity + and performance. SCALE_TYPE must be one of: default, scaleout. + --total-iops=TOTAL_IOPS Integer indicating total IOPS of the Storage Pool diff --git a/gcloud/netapp/storage-pools/execute b/gcloud/netapp/storage-pools/execute new file mode 100644 index 000000000..7bd9d6eaf --- /dev/null +++ b/gcloud/netapp/storage-pools/execute @@ -0,0 +1,61 @@ +NAME + gcloud netapp storage-pools execute - execute an ONTAP CLI command + +SYNOPSIS + gcloud netapp storage-pools execute (STORAGE_POOL : --location=LOCATION) + ONTAP_COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Execute an ONTAP CLI command. + +POSITIONAL ARGUMENTS + Storage pool resource - The Storage Pool to target. 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 storage_pool on the command line with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + STORAGE_POOL + ID of the storage_pool or fully qualified identifier for the + storage_pool. + + To set the storage_pool attribute: + ▸ provide the argument storage_pool 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 of the storage_pool. + + To set the location attribute: + ▸ provide the argument storage_pool on the command line with a + fully specified name; + ▸ provide the argument --location on the command line; + ▸ set the property netapp/location. + + ONTAP_COMMAND + The ONTAP command to execute. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --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 netapp storage-pools execute + + $ gcloud beta netapp storage-pools execute + diff --git a/gcloud/netapp/storage-pools/help b/gcloud/netapp/storage-pools/help index 777085297..f07618b5c 100644 --- a/gcloud/netapp/storage-pools/help +++ b/gcloud/netapp/storage-pools/help @@ -24,6 +24,9 @@ COMMANDS describe Show metadata for a Cloud NetApp Storage Pool. + execute + Execute an ONTAP CLI command. + list List Cloud NetApp Storage Pools. diff --git a/gcloud/netapp/volumes/create b/gcloud/netapp/volumes/create index 9c2878e2e..a92e477b4 100644 --- a/gcloud/netapp/volumes/create +++ b/gcloud/netapp/volumes/create @@ -37,6 +37,7 @@ SYNOPSIS [peer-volume-name=PEER-VOLUME-NAME],[replication=REPLICATION], [replication-schedule=REPLICATION-SCHEDULE]] [--labels=[KEY=VALUE,...]] [--large-capacity=LARGE_CAPACITY] + [--large-capacity-config[=[constituent-count=CONSTITUENT-COUNT]]] [--multiple-endpoints=MULTIPLE_ENDPOINTS] [--restricted-actions=RESTRICTED_ACTION,[...]] [--security-style=SECURITY_STYLE; default="SECURITY_STYLE_UNSPECIFIED"] @@ -277,6 +278,17 @@ OPTIONAL FLAGS Boolean flag indicating whether Volume is a large capacity Volume or not + --large-capacity-config[=[constituent-count=CONSTITUENT-COUNT]] + Large Capacity Config contains configuration for large capacity + volumes. + + Large Capacity Config has the following format: + --large-capacity-config=constituent-count=CONSTITUENT_COUNT + --large-capacity-config + + constituent-count + (optional) The number of constituents for a large capacity volume. + --multiple-endpoints=MULTIPLE_ENDPOINTS Boolean flag indicating whether Volume is a multiple endpoints Volume or not diff --git a/gcloud/network-connectivity/help b/gcloud/network-connectivity/help index 84909f728..2c5515ce5 100644 --- a/gcloud/network-connectivity/help +++ b/gcloud/network-connectivity/help @@ -45,6 +45,9 @@ GROUPS spokes Manage Network Connectivity Center spokes. + transports + Manage Network Connectivity Center transports. + NOTES These variants are also available: diff --git a/gcloud/network-connectivity/spokes/linked-producer-vpc-network/create b/gcloud/network-connectivity/spokes/linked-producer-vpc-network/create index 69bfd02d5..5c58312c1 100644 --- a/gcloud/network-connectivity/spokes/linked-producer-vpc-network/create +++ b/gcloud/network-connectivity/spokes/linked-producer-vpc-network/create @@ -6,7 +6,7 @@ SYNOPSIS gcloud network-connectivity spokes linked-producer-vpc-network create SPOKE --hub=HUB --network=NETWORK --peering=PEERING [--async] [--description=DESCRIPTION] [--exclude-export-ranges=[CIDR_RANGE,...]] - [--global] [--include-export-ranges=[CIDR_RANGE,...]] + [--global] [--group=GROUP] [--include-export-ranges=[CIDR_RANGE,...]] [--labels=[KEY=VALUE,...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -75,6 +75,9 @@ OPTIONAL FLAGS --global Indicates that the spoke is global. + --group=GROUP + Group that the spoke will be part of. The group must already exist. + --include-export-ranges=[CIDR_RANGE,...] Subnet IP address range(s) to export to other VPC networks that are connected through Network Connectivity Center. diff --git a/gcloud/network-connectivity/spokes/linked-vpc-network/create b/gcloud/network-connectivity/spokes/linked-vpc-network/create index e18f4b870..a607d0540 100644 --- a/gcloud/network-connectivity/spokes/linked-vpc-network/create +++ b/gcloud/network-connectivity/spokes/linked-vpc-network/create @@ -6,7 +6,7 @@ SYNOPSIS gcloud network-connectivity spokes linked-vpc-network create SPOKE --hub=HUB --vpc-network=VPC_NETWORK [--async] [--description=DESCRIPTION] [--exclude-export-ranges=[CIDR_RANGE,...]] - [--global] [--include-export-ranges=[CIDR_RANGE,...]] + [--global] [--group=GROUP] [--include-export-ranges=[CIDR_RANGE,...]] [--labels=[KEY=VALUE,...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -69,6 +69,9 @@ OPTIONAL FLAGS --global Indicates that the spoke is global. + --group=GROUP + Group that the spoke will be part of. The group must already exist. + --include-export-ranges=[CIDR_RANGE,...] Subnet IP address range(s) to export to other VPC networks that are connected through Network Connectivity Center. diff --git a/gcloud/network-connectivity/transports/create b/gcloud/network-connectivity/transports/create new file mode 100644 index 000000000..83fbd1323 --- /dev/null +++ b/gcloud/network-connectivity/transports/create @@ -0,0 +1,157 @@ +NAME + gcloud network-connectivity transports create - create a transport + +SYNOPSIS + gcloud network-connectivity transports create TRANSPORT --network=NETWORK + (--activation-key=ACTIVATION_KEY | --bandwidth=BANDWIDTH + --remote-account-id=REMOTE_ACCOUNT_ID + --remote-profile=REMOTE_PROFILE) + [--advertised-routes=[CIDR_RANGE,...]] [--async] + [--description=DESCRIPTION] [--labels=[KEY=VALUE,...]] + [--region=REGION] [--stack-type=STACK_TYPE; default="ipv4-only"] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Create a transport with the given name to a remote provider. + +EXAMPLES + To create a transport that generates a key to aws-us-east-1. + + $ gcloud network-connectivity transports create my-cci-aws \ + --bandwidth 1G --profile aws-us-east-1 \ + --remote-account-id 12345 --network default \ + --advertised-routes '10.128.0.0/9' + + To accept a key: + + $ gcloud network-connectivity transports create my-cci-aws \ + --activation-key ABC1234 --network default + +POSITIONAL ARGUMENTS + Transport resource - Name of the Transport to be created. 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 transport 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 region attribute: + ◆ provide the argument transport on the command line with a fully + specified name; + ◆ provide the argument --region on the command line. + + This must be specified. + + TRANSPORT + ID of the transport or fully qualified identifier for the transport. + + To set the transport attribute: + ▸ provide the argument transport on the command line. + +REQUIRED FLAGS + --network=NETWORK + ID of the network or fully qualified identifier for the network. + + To set the network attribute: + ◆ provide the argument --network on the command line. + + Exactly one of these must be specified: + + --activation-key=ACTIVATION_KEY + Key from the remote provider to establish a connection over the + Transport. + + Or at least one of these can be specified: + + These values must all be specified if Google is expected to generate + the key. + + --bandwidth=BANDWIDTH + Bandwidth of the transport to create. Must be a supported bandwidth + on the remote profile. BANDWIDTH must be one of: 100g, 100m, 10g, + 1g, 200m, 20g, 2g, 300m, 400m, 500m, 50g, 50m, 5g. + + This flag argument must be specified if any of the other arguments + in this group are specified. + + --remote-account-id=REMOTE_ACCOUNT_ID + Account ID in the remote provider to associate with the generated + key. + + This flag argument must be specified if any of the other arguments + in this group are specified. + + RemoteTransportProfile resource - Remote transport profile + representing the provider and their 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 --remote-profile 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 region attribute: + ▫ provide the argument --remote-profile on the command line with a + fully specified name; + ▫ provide the argument --region on the command line. + + This must be specified. + + --remote-profile=REMOTE_PROFILE + ID of the remoteTransportProfile or fully qualified identifier + for the remoteTransportProfile. + + To set the remote_transport_profile attribute: + ◇ provide the argument --remote-profile on the command line. + +OPTIONAL FLAGS + --advertised-routes=[CIDR_RANGE,...] + List of routes to advertise from the VPC network toward the provider. + + --async + Return immediately, without waiting for the operation in progress to + complete. + + --description=DESCRIPTION + Description of the transport. + + --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. + + --region=REGION + For resources [transport, remote-profile], provides fallback value for + resource region attribute. When the resource's full URI path is not + provided, region will fallback to this flag value. + + --stack-type=STACK_TYPE; default="ipv4-only" + IP version of the routes to be exchanged. STACK_TYPE must be one of: + ipv4-ipv6, ipv4-only. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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 networkconnectivity/v1 API. The full documentation + for this API can be found at: + https://cloud.google.com/network-connectivity/docs/reference/networkconnectivity/rest + +NOTES + This variant is also available: + + $ gcloud beta network-connectivity transports create + diff --git a/gcloud/network-connectivity/transports/delete b/gcloud/network-connectivity/transports/delete new file mode 100644 index 000000000..bbddb470b --- /dev/null +++ b/gcloud/network-connectivity/transports/delete @@ -0,0 +1,70 @@ +NAME + gcloud network-connectivity transports delete - delete a transport + +SYNOPSIS + gcloud network-connectivity transports delete (TRANSPORT : --region=REGION) + [--async] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Delete the specified transport. + +EXAMPLES + To delete a transport named mytransport in the us-east4 region, run: + + $ gcloud network-connectivity transports delete mytransport \ + --region=us-east4 + +POSITIONAL ARGUMENTS + Transport resource - Name of the Transport to be deleted. 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 transport 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. + + TRANSPORT + ID of the transport or fully qualified identifier for the transport. + + To set the transport attribute: + ▸ provide the argument transport on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --region=REGION + The location Id. + + To set the region attribute: + ▸ provide the argument transport on the command line with a fully + specified name; + ▸ provide the argument --region 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 networkconnectivity/v1 API. The full documentation + for this API can be found at: + https://cloud.google.com/network-connectivity/docs/reference/networkconnectivity/rest + +NOTES + This variant is also available: + + $ gcloud beta network-connectivity transports delete + diff --git a/gcloud/network-connectivity/transports/describe b/gcloud/network-connectivity/transports/describe new file mode 100644 index 000000000..e4b51bb58 --- /dev/null +++ b/gcloud/network-connectivity/transports/describe @@ -0,0 +1,66 @@ +NAME + gcloud network-connectivity transports describe - describe a transport + +SYNOPSIS + gcloud network-connectivity transports describe + (TRANSPORT : --region=REGION) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Retrieve and display details about a transport. + +EXAMPLES + To display details about a transport named mytransport in the us-central1 + region, run: + + $ gcloud network-connectivity transports describe mytransport \ + --region=us-central1 + +POSITIONAL ARGUMENTS + Transport resource - Name of the Transport to be described. 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 transport 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. + + TRANSPORT + ID of the transport or fully qualified identifier for the transport. + + To set the transport attribute: + ▸ provide the argument transport on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --region=REGION + The location Id. + + To set the region attribute: + ▸ provide the argument transport on the command line with a fully + specified name; + ▸ provide the argument --region on the command line. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --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 networkconnectivity/v1 API. The full documentation + for this API can be found at: + https://cloud.google.com/network-connectivity/docs/reference/networkconnectivity/rest + +NOTES + This variant is also available: + + $ gcloud beta network-connectivity transports describe + diff --git a/gcloud/network-connectivity/transports/help b/gcloud/network-connectivity/transports/help new file mode 100644 index 000000000..0572ca0ae --- /dev/null +++ b/gcloud/network-connectivity/transports/help @@ -0,0 +1,45 @@ +NAME + gcloud network-connectivity transports - manage Network Connectivity Center + transports + +SYNOPSIS + gcloud network-connectivity transports GROUP | COMMAND + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Manage Network Connectivity Center transports. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +GROUPS + GROUP is one of the following: + + remote-profiles + Manage Network Connectivity Center remote transport profiles. + +COMMANDS + COMMAND is one of the following: + + create + Create a transport. + + delete + Delete a transport. + + describe + Describe a transport. + + list + List transports. + + update + Update a transport. + +NOTES + This variant is also available: + + $ gcloud beta network-connectivity transports + diff --git a/gcloud/network-connectivity/transports/list b/gcloud/network-connectivity/transports/list new file mode 100644 index 000000000..4d27fc32d --- /dev/null +++ b/gcloud/network-connectivity/transports/list @@ -0,0 +1,75 @@ +NAME + gcloud network-connectivity transports list - list transports + +SYNOPSIS + gcloud network-connectivity transports list [--region=REGION; default="-"] + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Retrieve and display a list of all transports in the specified project. + +EXAMPLES + To list all transports in the us-east4 region, run: + + $ gcloud network-connectivity transports list --region=us-east4 + + To list all transports in all regions, run: + + $ gcloud network-connectivity transports list + +FLAGS + --region=REGION; default="-" + The region of the transports to list. Provide "-" to list all + transports. + +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 networkconnectivity/v1 API. The full documentation + for this API can be found at: + https://cloud.google.com/network-connectivity/docs/reference/networkconnectivity/rest + +NOTES + This variant is also available: + + $ gcloud beta network-connectivity transports list + diff --git a/gcloud/network-connectivity/transports/remote-profiles/describe b/gcloud/network-connectivity/transports/remote-profiles/describe new file mode 100644 index 000000000..fabec5914 --- /dev/null +++ b/gcloud/network-connectivity/transports/remote-profiles/describe @@ -0,0 +1,70 @@ +NAME + gcloud network-connectivity transports remote-profiles describe - describe + a remote transport profile + +SYNOPSIS + gcloud network-connectivity transports remote-profiles describe + (REMOTE_TRANSPORT_PROFILE : --region=REGION) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Retrieve and display details about a remote transport profile. + +EXAMPLES + To display details about a remote transport profile named myprofile in the + us-central1 region, run: + + $ gcloud network-connectivity transports remote-profiles describe \ + myprofile --region=us-central1 + +POSITIONAL ARGUMENTS + RemoteTransportProfile resource - Name of the remote transport profile to + be described. 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 remote_transport_profile 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. + + REMOTE_TRANSPORT_PROFILE + ID of the remoteTransportProfile or fully qualified identifier for + the remoteTransportProfile. + + To set the remote_transport_profile attribute: + ▸ provide the argument remote_transport_profile on the command + line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --region=REGION + The location Id. + + To set the region attribute: + ▸ provide the argument remote_transport_profile on the command line + with a fully specified name; + ▸ provide the argument --region on the command line. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --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 networkconnectivity/v1 API. The full documentation + for this API can be found at: + https://cloud.google.com/network-connectivity/docs/reference/networkconnectivity/rest + +NOTES + This variant is also available: + + $ gcloud beta network-connectivity transports remote-profiles \ + describe + diff --git a/gcloud/network-connectivity/transports/remote-profiles/help b/gcloud/network-connectivity/transports/remote-profiles/help new file mode 100644 index 000000000..3c06c7952 --- /dev/null +++ b/gcloud/network-connectivity/transports/remote-profiles/help @@ -0,0 +1,30 @@ +NAME + gcloud network-connectivity transports remote-profiles - manage Network + Connectivity Center remote transport profiles + +SYNOPSIS + gcloud network-connectivity transports remote-profiles COMMAND + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Manage Network Connectivity Center remote transport profiles. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + describe + Describe a remote transport profile. + + list + List remote transport profiles. + +NOTES + This variant is also available: + + $ gcloud beta network-connectivity transports remote-profiles + diff --git a/gcloud/network-connectivity/transports/remote-profiles/list b/gcloud/network-connectivity/transports/remote-profiles/list new file mode 100644 index 000000000..7a6bb19d5 --- /dev/null +++ b/gcloud/network-connectivity/transports/remote-profiles/list @@ -0,0 +1,79 @@ +NAME + gcloud network-connectivity transports remote-profiles list - list remote + transport profiles + +SYNOPSIS + gcloud network-connectivity transports remote-profiles list + [--region=REGION; default="-"] [--filter=EXPRESSION] [--limit=LIMIT] + [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Retrieve and display a list of all remote transport profiles in the + specified project. + +EXAMPLES + To list all remote transport profiles in the "us-east4" region, run: + + $ gcloud network-connectivity transports remote-profiles list \ + --region=us-east4 + + To list all remote transport profiles in all regions, run: + + $ gcloud network-connectivity transports remote-profiles list + +FLAGS + --region=REGION; default="-" + The region of the remote transport profiles to list. Use "-" to list + all profiles. + +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 networkconnectivity/v1 API. The full documentation + for this API can be found at: + https://cloud.google.com/network-connectivity/docs/reference/networkconnectivity/rest + +NOTES + This variant is also available: + + $ gcloud beta network-connectivity transports remote-profiles list + diff --git a/gcloud/network-connectivity/transports/update b/gcloud/network-connectivity/transports/update new file mode 100644 index 000000000..32d9e1bd6 --- /dev/null +++ b/gcloud/network-connectivity/transports/update @@ -0,0 +1,118 @@ +NAME + gcloud network-connectivity transports update - update a transport + +SYNOPSIS + gcloud network-connectivity transports update (TRANSPORT : --region=REGION) + [--advertised-routes=[CIDR_RANGE,...]] [--async] + [--bandwidth=BANDWIDTH] [--description=DESCRIPTION] + [--stack-type=STACK_TYPE] [--update-labels=[KEY=VALUE,...]] + [--clear-labels | --remove-labels=[KEY,...]] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Update a transport with the given name to a remote provider. + +EXAMPLES + To update a transport named mytransport in the us-east4 region, run: + + $ gcloud network-connectivity transports update mytransport \ + --region=us-east4 --description="new description" \ + --advertised-routes="10.0.0.0/8,10.1.0.0/16" --bandwidth=1G + +POSITIONAL ARGUMENTS + Transport resource - Name of the Transport to be updated. 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 transport 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. + + TRANSPORT + ID of the transport or fully qualified identifier for the transport. + + To set the transport attribute: + ▸ provide the argument transport on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --region=REGION + The location Id. + + To set the region attribute: + ▸ provide the argument transport on the command line with a fully + specified name; + ▸ provide the argument --region on the command line. + +FLAGS + --advertised-routes=[CIDR_RANGE,...] + List of routes to advertise from the VPC network toward the provider. + + --async + Return immediately, without waiting for the operation in progress to + complete. + + --bandwidth=BANDWIDTH + Bandwidth of the transport to create. Must be a supported bandwidth on + the remote profile. BANDWIDTH must be one of: 100g, 100m, 10g, 1g, + 200m, 20g, 2g, 300m, 400m, 500m, 50g, 50m, 5g. + + --description=DESCRIPTION + Description of the transport. + + --stack-type=STACK_TYPE + IP version of the routes to be exchanged. STACK_TYPE must be one of: + ipv4-ipv6, ipv4-only. + + --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 network-connectivity transports update --clear-labels + + To remove all existing labels and create two new labels, foo and baz: + + $ gcloud network-connectivity transports 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 networkconnectivity/v1 API. The full documentation + for this API can be found at: + https://cloud.google.com/network-connectivity/docs/reference/networkconnectivity/rest + +NOTES + This variant is also available: + + $ gcloud beta network-connectivity transports update + diff --git a/gcloud/network-security/firewall-endpoint-associations/create b/gcloud/network-security/firewall-endpoint-associations/create index daf51fc5b..32c4ebc72 100644 --- a/gcloud/network-security/firewall-endpoint-associations/create +++ b/gcloud/network-security/firewall-endpoint-associations/create @@ -4,11 +4,11 @@ NAME SYNOPSIS gcloud network-security firewall-endpoint-associations create - [ASSOCIATION_ID] --network=NETWORK --zone=ZONE + [ASSOCIATION_ID] --network=NETWORK (--endpoint=ENDPOINT : --endpoint-zone=ENDPOINT_ZONE --organization=ORGANIZATION) - [--async] [--labels=[KEY=VALUE,...]] - [--max-wait=MAX_WAIT; default="60m"] + (--location=LOCATION | --zone=ZONE) [--async] + [--labels=[KEY=VALUE,...]] [--max-wait=MAX_WAIT; default="60m"] [--tls-inspection-policy=TLS_INSPECTION_POLICY : --tls-inspection-policy-project=TLS_INSPECTION_POLICY_PROJECT --tls-inspection-policy-region=TLS_INSPECTION_POLICY_REGION] @@ -55,9 +55,6 @@ REQUIRED FLAGS To set the network-name attribute: ▸ provide the argument --network on the command line. - --zone=ZONE - Zone of a firewall endpoint association - Firewall endpoint resource - Firewall Plus. The arguments in this group can be used to specify the attributes of this resource. This resource can be one of the following types: [firewall endpoint]. @@ -82,6 +79,7 @@ REQUIRED FLAGS specified name; ▸ provide the argument --endpoint-zone on the command line; ▸ provide the argument --zone on the command line; + ▸ provide the argument --location on the command line; ▸ provide the argument FIREWALL_ENDPOINT_ASSOCIATION on the command line with a fully specified name. @@ -93,6 +91,14 @@ REQUIRED FLAGS specified name; ▸ provide the argument --organization on the command line. + Exactly one of these must be specified: + + --location=LOCATION + Location of the firewall endpoint association + + --zone=ZONE + Zone of the firewall endpoint association + OPTIONAL FLAGS --async Return immediately, without waiting for the operation in progress to diff --git a/gcloud/network-security/firewall-endpoint-associations/delete b/gcloud/network-security/firewall-endpoint-associations/delete index 2a7a65df1..619f9575e 100644 --- a/gcloud/network-security/firewall-endpoint-associations/delete +++ b/gcloud/network-security/firewall-endpoint-associations/delete @@ -5,7 +5,8 @@ NAME SYNOPSIS gcloud network-security firewall-endpoint-associations delete (FIREWALL_ENDPOINT_ASSOCIATION : --zone=ZONE) [--async] - [--max-wait=MAX_WAIT; default="60m"] [GCLOUD_WIDE_FLAG ...] + [--location=LOCATION] [--max-wait=MAX_WAIT; default="60m"] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION Unassociate the specified network from a firewall endpoint. Check the @@ -54,7 +55,8 @@ POSITIONAL ARGUMENTS To set the zone attribute: ▸ provide the argument FIREWALL_ENDPOINT_ASSOCIATION on the command line with a fully specified name; - ▸ provide the argument --zone on the command line. + ▸ provide the argument --zone on the command line; + ▸ provide the argument --location on the command line. FLAGS --async @@ -62,6 +64,9 @@ FLAGS complete. The default is True. Enabled by default, use --no-async to disable. + --location=LOCATION + Location of the firewall endpoint association + --max-wait=MAX_WAIT; default="60m" Time to synchronously wait for the operation to complete, after which the operation continues asynchronously. Ignored if --no-async isn't diff --git a/gcloud/network-security/firewall-endpoint-associations/describe b/gcloud/network-security/firewall-endpoint-associations/describe index 4df656255..022f36618 100644 --- a/gcloud/network-security/firewall-endpoint-associations/describe +++ b/gcloud/network-security/firewall-endpoint-associations/describe @@ -4,7 +4,8 @@ NAME SYNOPSIS gcloud network-security firewall-endpoint-associations describe - (FIREWALL_ENDPOINT_ASSOCIATION : --zone=ZONE) [GCLOUD_WIDE_FLAG ...] + (FIREWALL_ENDPOINT_ASSOCIATION : --zone=ZONE) [--location=LOCATION] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION Describe a firewall endpoint association. @@ -52,7 +53,12 @@ POSITIONAL ARGUMENTS To set the zone attribute: ▸ provide the argument FIREWALL_ENDPOINT_ASSOCIATION on the command line with a fully specified name; - ▸ provide the argument --zone on the command line. + ▸ provide the argument --zone on the command line; + ▸ provide the argument --location on the command line. + +FLAGS + --location=LOCATION + Location of the firewall endpoint association GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/network-security/firewall-endpoint-associations/list b/gcloud/network-security/firewall-endpoint-associations/list index 7f934bf39..5b23afe0c 100644 --- a/gcloud/network-security/firewall-endpoint-associations/list +++ b/gcloud/network-security/firewall-endpoint-associations/list @@ -4,8 +4,8 @@ NAME SYNOPSIS gcloud network-security firewall-endpoint-associations list - [--zone=ZONE; default="-"] [--filter=EXPRESSION] [--limit=LIMIT] - [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [--location=LOCATION | --zone=ZONE] [--filter=EXPRESSION] + [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -28,8 +28,13 @@ EXAMPLES defined. FLAGS - --zone=ZONE; default="-" - Zone for the list operation + At most one of these can be specified: + + --location=LOCATION + Location of the firewall endpoint association + + --zone=ZONE + Zone of the firewall endpoint association LIST COMMAND FLAGS --filter=EXPRESSION diff --git a/gcloud/network-security/firewall-endpoint-associations/update b/gcloud/network-security/firewall-endpoint-associations/update index 0e28ac659..f7036383e 100644 --- a/gcloud/network-security/firewall-endpoint-associations/update +++ b/gcloud/network-security/firewall-endpoint-associations/update @@ -5,7 +5,7 @@ NAME SYNOPSIS gcloud network-security firewall-endpoint-associations update (FIREWALL_ENDPOINT_ASSOCIATION : --zone=ZONE) [--async] - [--max-wait=MAX_WAIT; default="60m"] + [--location=LOCATION] [--max-wait=MAX_WAIT; default="60m"] [--disabled | --update-labels=[KEY=VALUE,...] --clear-labels | --remove-labels=[KEY,...] --no-tls-inspection-policy | [--tls-inspection-policy=TLS_INSPECTION_POLICY @@ -69,7 +69,8 @@ POSITIONAL ARGUMENTS To set the zone attribute: ▸ provide the argument FIREWALL_ENDPOINT_ASSOCIATION on the command line with a fully specified name; - ▸ provide the argument --zone on the command line. + ▸ provide the argument --zone on the command line; + ▸ provide the argument --location on the command line. FLAGS --async @@ -77,6 +78,9 @@ FLAGS complete. The default is True. Enabled by default, use --no-async to disable. + --location=LOCATION + Location of the firewall endpoint association + --max-wait=MAX_WAIT; default="60m" Time to synchronously wait for the operation to complete, after which the operation continues asynchronously. Ignored if --no-async isn't diff --git a/gcloud/network-security/firewall-endpoints/create b/gcloud/network-security/firewall-endpoints/create index 83d2c8e6a..a13844bc0 100644 --- a/gcloud/network-security/firewall-endpoints/create +++ b/gcloud/network-security/firewall-endpoints/create @@ -7,7 +7,8 @@ SYNOPSIS (FIREWALL_ENDPOINT : --organization=ORGANIZATION --zone=ZONE) [--async] [--billing-project=BILLING_PROJECT] [--description=DESCRIPTION] [--enable-jumbo-frames] [--labels=[KEY=VALUE,...]] - [--max-wait=MAX_WAIT; default="60m"] [GCLOUD_WIDE_FLAG ...] + [--location=LOCATION] [--max-wait=MAX_WAIT; default="60m"] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION Create a firewall endpoint. Successful creation of an endpoint results in @@ -54,7 +55,8 @@ POSITIONAL ARGUMENTS To set the zone attribute: ▸ provide the argument FIREWALL_ENDPOINT on the command line with a fully specified name; - ▸ provide the argument --zone on the command line. + ▸ provide the argument --zone on the command line; + ▸ provide the argument --location on the command line. FLAGS --async @@ -82,6 +84,9 @@ FLAGS contain only hyphens (-), underscores (_), lowercase characters, and numbers. + --location=LOCATION + Location of the endpoint + --max-wait=MAX_WAIT; default="60m" Time to synchronously wait for the operation to complete, after which the operation continues asynchronously. Ignored if --no-async isn't diff --git a/gcloud/network-security/firewall-endpoints/delete b/gcloud/network-security/firewall-endpoints/delete index f4d8fdc8c..4668ddcc0 100644 --- a/gcloud/network-security/firewall-endpoints/delete +++ b/gcloud/network-security/firewall-endpoints/delete @@ -5,7 +5,8 @@ NAME SYNOPSIS gcloud network-security firewall-endpoints delete (FIREWALL_ENDPOINT : --organization=ORGANIZATION --zone=ZONE) [--async] - [--max-wait=MAX_WAIT; default="60m"] [GCLOUD_WIDE_FLAG ...] + [--location=LOCATION] [--max-wait=MAX_WAIT; default="60m"] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION Delete a firewall endpoint. Check the progress of endpoint deletion by @@ -57,7 +58,8 @@ POSITIONAL ARGUMENTS To set the zone attribute: ▸ provide the argument FIREWALL_ENDPOINT on the command line with a fully specified name; - ▸ provide the argument --zone on the command line. + ▸ provide the argument --zone on the command line; + ▸ provide the argument --location on the command line. FLAGS --async @@ -65,6 +67,9 @@ FLAGS complete. The default is True. Enabled by default, use --no-async to disable. + --location=LOCATION + Location of the endpoint + --max-wait=MAX_WAIT; default="60m" Time to synchronously wait for the operation to complete, after which the operation continues asynchronously. Ignored if --no-async isn't diff --git a/gcloud/network-security/firewall-endpoints/describe b/gcloud/network-security/firewall-endpoints/describe index 3b28dd435..b0be53b2a 100644 --- a/gcloud/network-security/firewall-endpoints/describe +++ b/gcloud/network-security/firewall-endpoints/describe @@ -5,7 +5,7 @@ NAME SYNOPSIS gcloud network-security firewall-endpoints describe (FIREWALL_ENDPOINT : --organization=ORGANIZATION --zone=ZONE) - [GCLOUD_WIDE_FLAG ...] + [--location=LOCATION] [GCLOUD_WIDE_FLAG ...] DESCRIPTION Describe a firewall endpoint. @@ -56,7 +56,12 @@ POSITIONAL ARGUMENTS To set the zone attribute: ▸ provide the argument FIREWALL_ENDPOINT on the command line with a fully specified name; - ▸ provide the argument --zone on the command line. + ▸ provide the argument --zone on the command line; + ▸ provide the argument --location on the command line. + +FLAGS + --location=LOCATION + Location of the endpoint GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/network-security/firewall-endpoints/list b/gcloud/network-security/firewall-endpoints/list index 3cb6a5958..3212b5a5c 100644 --- a/gcloud/network-security/firewall-endpoints/list +++ b/gcloud/network-security/firewall-endpoints/list @@ -4,9 +4,9 @@ NAME SYNOPSIS gcloud network-security firewall-endpoints list - [--organization=ORGANIZATION] [--zone=ZONE] [--filter=EXPRESSION] - [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] - [GCLOUD_WIDE_FLAG ...] + [--organization=ORGANIZATION] [--location=LOCATION | --zone=ZONE] + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] DESCRIPTION List firewall endpoints. @@ -22,8 +22,13 @@ FLAGS --organization=ORGANIZATION The organization for a list operation - --zone=ZONE - The zone for a list operation + At most one of these can be specified: + + --location=LOCATION + The location for a list operation + + --zone=ZONE + The zone for a list operation LIST COMMAND FLAGS --filter=EXPRESSION diff --git a/gcloud/network-security/firewall-endpoints/update b/gcloud/network-security/firewall-endpoints/update index 93eb23918..9aa4bb347 100644 --- a/gcloud/network-security/firewall-endpoints/update +++ b/gcloud/network-security/firewall-endpoints/update @@ -5,7 +5,8 @@ NAME SYNOPSIS gcloud network-security firewall-endpoints update (FIREWALL_ENDPOINT : --organization=ORGANIZATION --zone=ZONE) [--async] - [--description=DESCRIPTION] [--max-wait=MAX_WAIT; default="60m"] + [--description=DESCRIPTION] [--location=LOCATION] + [--max-wait=MAX_WAIT; default="60m"] [--update-billing-project=BILLING_PROJECT] [--update-labels=[KEY=VALUE,...]] [--clear-labels | --remove-labels=[KEY,...]] [GCLOUD_WIDE_FLAG ...] @@ -64,7 +65,8 @@ POSITIONAL ARGUMENTS To set the zone attribute: ▸ provide the argument FIREWALL_ENDPOINT on the command line with a fully specified name; - ▸ provide the argument --zone on the command line. + ▸ provide the argument --zone on the command line; + ▸ provide the argument --location on the command line. FLAGS --async @@ -75,6 +77,9 @@ FLAGS --description=DESCRIPTION Description of the endpoint + --location=LOCATION + Location of the endpoint + --max-wait=MAX_WAIT; default="60m" Time to synchronously wait for the operation to complete, after which the operation continues asynchronously. Ignored if --no-async isn't diff --git a/gcloud/network-security/security-profiles/threat-prevention/describe b/gcloud/network-security/security-profiles/threat-prevention/describe new file mode 100644 index 000000000..7e6fb7de1 --- /dev/null +++ b/gcloud/network-security/security-profiles/threat-prevention/describe @@ -0,0 +1,77 @@ +NAME + gcloud network-security security-profiles threat-prevention describe - + describe a Threat Prevention Security Profile + +SYNOPSIS + gcloud network-security security-profiles threat-prevention describe + (SECURITY_PROFILE : --location=LOCATION --organization=ORGANIZATION) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Show details of a Threat Prevention Security Profile. + + For more examples, refer to the EXAMPLES section below. + +EXAMPLES + To show details of a Threat Prevention security profile named + my-security-profile in an organization, run: + + $ gcloud network-security security-profiles threat-prevention \ describe my-security-profile --organization=1234 \ + --location=global + + To show details of a Threat Prevention security profile named + my-security-profile in a project, run: + + $ gcloud network-security security-profiles threat-prevention \ describe my-security-profile --project=my-project \ + --location=global + +POSITIONAL ARGUMENTS + Security profile resource - Security Profile Name. The arguments in this + group can be used to specify the attributes of this resource. This + resource can be one of the following types: [security_profile]. + + This must be specified. + + SECURITY_PROFILE + ID of the security_profile or fully qualified identifier for the + security_profile. + + To set the security_profile attribute: + ▸ provide the argument security_profile on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + Location of the security profile. + + To set the location attribute: + ▸ provide the argument security_profile on the command line with a + fully specified name; + ▸ provide the argument --location on the command line. + + --organization=ORGANIZATION + Organization ID to which the changes should apply. + + To set the organization attribute: + ▸ provide the argument security_profile on the command line with a + fully specified name; + ▸ provide the argument --organization 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 network-security security-profiles \ + threat-prevention describe + + $ gcloud beta network-security security-profiles threat-prevention \ + describe + diff --git a/gcloud/network-security/security-profiles/threat-prevention/help b/gcloud/network-security/security-profiles/threat-prevention/help index 6d518beca..763c1514e 100644 --- a/gcloud/network-security/security-profiles/threat-prevention/help +++ b/gcloud/network-security/security-profiles/threat-prevention/help @@ -68,6 +68,11 @@ EXAMPLES $ gcloud network-security security-profiles threat-prevention list \ --location=global + To describe a Security Profile called my-security-profile, run: + + $ gcloud network-security security-profiles threat-prevention \ + describe my-security-profile + To delete a Security Profile called my-security-profile which includes location as global or region specified and organization ID, run: @@ -94,6 +99,9 @@ COMMANDS delete-override Delete overrides of Threat Prevention Profile. + describe + Describe a Threat Prevention Security Profile. + list List Threat Prevention Security Profiles. diff --git a/gcloud/oracle-database/databases/help b/gcloud/oracle-database/databases/help index 8067c861f..ded375b47 100644 --- a/gcloud/oracle-database/databases/help +++ b/gcloud/oracle-database/databases/help @@ -19,4 +19,4 @@ COMMANDS Get details of a Database. list - List all Databases. + List databases. diff --git a/gcloud/oracle-database/databases/list b/gcloud/oracle-database/databases/list index 436efe911..26eed0dc3 100644 --- a/gcloud/oracle-database/databases/list +++ b/gcloud/oracle-database/databases/list @@ -1,5 +1,5 @@ NAME - gcloud oracle-database databases list - list all Databases + gcloud oracle-database databases list - list databases SYNOPSIS gcloud oracle-database databases list --location=LOCATION @@ -7,21 +7,24 @@ SYNOPSIS [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - List all Databases. + Lists all Databases for the specified location. EXAMPLES - To list all Databases in the location us-east4 for a given DbSystem with id - my-db-system, run: + To list all databases in the location us-east4, run: + + $ gcloud oracle-database databases list --location=us-east4 + + To list all databases for a DbSystem with id my-db-system in the location + us-east4, run: $ gcloud oracle-database databases list --location=us-east4 \ - --filter="dbSystem=projects/project-id/locations/us-east4/dbSyst\ - ems/my-db-system" + --filter='dbSystem="projects/my-project/locations/us-east4/dbSys\ + tems/my-db-system"' REQUIRED FLAGS - Location resource - The parent resource name in the following format: - projects/{project}/locations/{region} This represents a Cloud resource. - (NOTE) Some attributes are not given arguments in this group but can be - set in other ways. + Location resource - The location you want to list the databases 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 --location on the command line with a fully @@ -39,11 +42,8 @@ REQUIRED FLAGS 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. + Apply a filter in the format : + --filter='dbSystem="projects/my-project/locations/us-east4/dbSystems/my-db-system"' --limit=LIMIT Maximum number of resources to list. The default is unlimited. This @@ -76,7 +76,3 @@ GCLOUD WIDE FLAGS --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/gi-versions/help b/gcloud/oracle-database/gi-versions/help index e1e16850f..8e6cc2d05 100644 --- a/gcloud/oracle-database/gi-versions/help +++ b/gcloud/oracle-database/gi-versions/help @@ -22,4 +22,4 @@ COMMANDS COMMAND is one of the following: list - List all GiVersions. + List Grid Infrastructure versions. diff --git a/gcloud/oracle-database/gi-versions/list b/gcloud/oracle-database/gi-versions/list index 049d3a6e0..b6bf040f6 100644 --- a/gcloud/oracle-database/gi-versions/list +++ b/gcloud/oracle-database/gi-versions/list @@ -1,5 +1,5 @@ NAME - gcloud oracle-database gi-versions list - list all GiVersions + gcloud oracle-database gi-versions list - list Grid Infrastructure versions SYNOPSIS gcloud oracle-database gi-versions list --location=LOCATION @@ -7,18 +7,23 @@ SYNOPSIS [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - List all GiVersions. + Lists all Grid Infrastructure versions for the specified location. EXAMPLES - To list all GiVersions in the location us-east4, run: + To list all Grid Infrastructure versions in the location us-east4, run: $ gcloud oracle-database gi-versions list --location=us-east4 + To list a specific Grid Infrastructure version in the location us-east4, + run: + + $ gcloud oracle-database gi-versions list --location=us-east4 \ + --filter='gi_version="19.0.0.0"' + REQUIRED FLAGS - Location resource - The parent value for Grid Infrastructure Version in - the following format: Format: projects/{project}/locations/{location}. - This represents a Cloud resource. (NOTE) Some attributes are not given - arguments in this group but can be set in other ways. + Location resource - The location you want to list the Grid Infrastructure + versions 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 --location on the command line with a fully @@ -36,11 +41,7 @@ REQUIRED FLAGS 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. + Apply a filter in the format : --filter='gi_version="19.0.0.0"' --limit=LIMIT Maximum number of resources to list. The default is unlimited. This @@ -73,7 +74,3 @@ GCLOUD WIDE FLAGS --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/gi-versions/minor-versions/help b/gcloud/oracle-database/gi-versions/minor-versions/help index 9af755e0c..d7f301d43 100644 --- a/gcloud/oracle-database/gi-versions/minor-versions/help +++ b/gcloud/oracle-database/gi-versions/minor-versions/help @@ -18,4 +18,4 @@ COMMANDS COMMAND is one of the following: list - List minorVersions. + List minor versions. diff --git a/gcloud/oracle-database/gi-versions/minor-versions/list b/gcloud/oracle-database/gi-versions/minor-versions/list index db60ebbf2..a53c2fdc5 100644 --- a/gcloud/oracle-database/gi-versions/minor-versions/list +++ b/gcloud/oracle-database/gi-versions/minor-versions/list @@ -1,5 +1,6 @@ NAME - gcloud oracle-database gi-versions minor-versions list - list minorVersions + gcloud oracle-database gi-versions minor-versions list - list minor + versions SYNOPSIS gcloud oracle-database gi-versions minor-versions list @@ -8,20 +9,29 @@ SYNOPSIS [GCLOUD_WIDE_FLAG ...] DESCRIPTION - List minorVersions + Lists all minor versions for the specified Grid Infrastructure version and + location. EXAMPLES - To list all minorVersions, run: + To list all minor versions for a Grid Infrastructure version with ID + 19.0.0.0 in the location us-east4, run: - $ gcloud oracle-database gi-versions minor-versions list + $ gcloud oracle-database gi-versions minor-versions list \ + --gi-version=19.0.0.0 --location=us-east4 + + To list all minor versions for a given shape family with ID EXADATA.X9M in + the location us-east4 and Grid Infrastructure version with ID 19.0.0.0, + run: + + $ gcloud oracle-database gi-versions minor-versions list \ + --gi-version=19.0.0.0 --location=us-east4 \ + --filter='shape_family="EXADATA.X9M"' REQUIRED FLAGS - GiVersion resource - The parent value for the MinorVersion resource with - the format: - projects/{project}/locations/{location}/giVersions/{gi_version} 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. + Gi version resource - The GI version you want to list the minor versions + for. The arguments in this group can be used to specify the attributes of + this resource. (NOTE) Some attributes are not given arguments in this + group but can be set in other ways. To set the project attribute: ◆ provide the argument --gi-version on the command line with a fully @@ -32,7 +42,8 @@ REQUIRED FLAGS This must be specified. --gi-version=GI_VERSION - ID of the giVersion or fully qualified identifier for the giVersion. + ID of the gi-version or fully qualified identifier for the + gi-version. To set the gi-version attribute: ▸ provide the argument --gi-version on the command line. @@ -41,7 +52,7 @@ REQUIRED FLAGS this group are specified. --location=LOCATION - The location id of the giVersion resource. + The Cloud location for the gi-version. To set the location attribute: ▸ provide the argument --gi-version on the command line with a @@ -50,11 +61,7 @@ REQUIRED FLAGS 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. + Apply a filter in the format: --filter='shape_family="EXADATA.X9M"' --limit=LIMIT Maximum number of resources to list. The default is unlimited. This @@ -87,7 +94,3 @@ GCLOUD WIDE FLAGS --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/pluggable-databases/help b/gcloud/oracle-database/pluggable-databases/help index e9c240fea..a13f3e001 100644 --- a/gcloud/oracle-database/pluggable-databases/help +++ b/gcloud/oracle-database/pluggable-databases/help @@ -20,4 +20,4 @@ COMMANDS Get details of a PluggableDatabase. list - List pluggableDatabases. + List pluggable databases. diff --git a/gcloud/oracle-database/pluggable-databases/list b/gcloud/oracle-database/pluggable-databases/list index 847fd3e61..d7413a61c 100644 --- a/gcloud/oracle-database/pluggable-databases/list +++ b/gcloud/oracle-database/pluggable-databases/list @@ -1,5 +1,5 @@ NAME - gcloud oracle-database pluggable-databases list - list pluggableDatabases + gcloud oracle-database pluggable-databases list - list pluggable databases SYNOPSIS gcloud oracle-database pluggable-databases list --location=LOCATION @@ -7,18 +7,21 @@ SYNOPSIS [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - List pluggableDatabases + Lists all PluggableDatabases for the specified Database. EXAMPLES - To list all pluggableDatabases, run: + To list all pluggable databases for a Database with id my-instance in the + location us-east4, run: - $ gcloud oracle-database pluggable-databases list + $ gcloud oracle-database pluggable-databases list \ + --location=us-east4 \ + --filter='database="projects/my-project/locations/us-east4/datab\ + ases/my-instance"' REQUIRED FLAGS - Location resource - The parent, which owns this collection of - PluggableDatabases. Format: projects/{project}/locations/{location} This - represents a Cloud resource. (NOTE) Some attributes are not given - arguments in this group but can be set in other ways. + Location resource - The location you want to list the pluggable databases + 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 --location on the command line with a fully @@ -36,11 +39,8 @@ REQUIRED FLAGS 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. + Apply a filter in the format: + --filter='database="projects/my-project/locations/us-east4/databases/my-instance"' --limit=LIMIT Maximum number of resources to list. The default is unlimited. This @@ -73,7 +73,3 @@ GCLOUD WIDE FLAGS --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/privateca/roots/list b/gcloud/privateca/roots/list index 064db4a2c..169891fc7 100644 --- a/gcloud/privateca/roots/list +++ b/gcloud/privateca/roots/list @@ -3,8 +3,9 @@ NAME SYNOPSIS gcloud privateca roots list [--location=LOCATION] [--pool=POOL] - [--limit=LIMIT] [--page-size=PAGE_SIZE; default=100] - [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + [--filter=EXPRESSION] [--limit=LIMIT] + [--page-size=PAGE_SIZE; default=100] [--sort-by=[FIELD,...]] [--uri] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION List the root certificate authorities within a project. @@ -26,14 +27,21 @@ EXAMPLES FLAGS --location=LOCATION - Location of the certificate authorities. If ommitted, root CAs across + Location of the certificate authorities. If omitted, root CAs across all regions will be listed. --pool=POOL - ID of the CA Pool where the certificate authorities reside. If - ommitted, root CAs across all CA pools will be listed. + ID of the CA Pool where the certificate authorities reside. If omitted, + root CAs across all CA pools will be listed. 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: diff --git a/gcloud/redis/clusters/create b/gcloud/redis/clusters/create index 7ad3cc304..b3d46b688 100644 --- a/gcloud/redis/clusters/create +++ b/gcloud/redis/clusters/create @@ -181,7 +181,8 @@ FLAGS --node-type=NODE_TYPE Node Type of the redis cluster Node. NODE_TYPE must be one of: - redis-highmem-medium, redis-highmem-xlarge, redis-shared-core-nano, + redis-highcpu-medium, redis-highmem-2xlarge, redis-highmem-medium, + redis-highmem-xlarge, redis-shared-core-nano, redis-standard-large, redis-standard-small. --persistence-mode=PERSISTENCE_MODE diff --git a/gcloud/redis/clusters/update b/gcloud/redis/clusters/update index e99bfde0c..e08d30e5d 100644 --- a/gcloud/redis/clusters/update +++ b/gcloud/redis/clusters/update @@ -117,7 +117,8 @@ FLAGS --node-type=NODE_TYPE Node Type of the redis cluster Node. NODE_TYPE must be one of: - redis-highmem-medium, redis-highmem-xlarge, redis-shared-core-nano, + redis-highcpu-medium, redis-highmem-2xlarge, redis-highmem-medium, + redis-highmem-xlarge, redis-shared-core-nano, redis-standard-large, redis-standard-small. --persistence-mode=PERSISTENCE_MODE diff --git a/gcloud/run/deploy b/gcloud/run/deploy index 38b4cdadf..bfd96016e 100644 --- a/gcloud/run/deploy +++ b/gcloud/run/deploy @@ -353,10 +353,11 @@ FLAGS --add-volume=[KEY=VALUE,...] Adds a volume to the Cloud Run resource. To add more than one volume, - specify this flag multiple times. Volumes must have a name and type - key. Only certain values are supported for type. Depending on the - provided type, other keys will be required. The following types are - supported with the specified additional keys: + specify this flag multiple times. Volumes must have a type key. Volumes + must have a name key if mount-path is not specified. A name key is + optional if mount-path is specified.Only certain values are supported + for type. Depending on the provided type, other keys will be required. + The following types are supported with the specified additional keys: cloud-storage: A volume representing a Cloud Storage bucket. This volume type is mounted using Cloud Storage FUSE. See @@ -369,11 +370,21 @@ FLAGS ◆ mount-options: (optional) A list of flags to pass to GCSFuse. Flags should be specified without leading dashes and separated by semicolons. + ◆ mount-path: (optional) The path at which the volume should be + mounted. The mount-path parameter is only supported for single + container services which do not make use of the --container flag. For + multi-container services, specify the mount-path parameter under the + --add-volume-mount flag. in-memory: An ephemeral volume that stores data in the instance's memory. With this type of volume, data is not shared between instances and all data will be lost when the instance it is on is terminated. Additional keys: + ◆ mount-path: (optional) The path at which the volume should be + mounted. The mount-path parameter is only supported for single + container services which do not make use of the --container flag. For + multi-container services, specify the mount-path parameter under the + --add-volume-mount flag. ◆ size-limit: (optional) A quantity representing the maximum amount of memory allocated to this volume, such as "512Mi" or "3G". Data stored in an in-memory volume consumes the memory allocation of the @@ -383,6 +394,11 @@ FLAGS nfs: Represents a volume backed by an NFS server. Additional keys: ◆ location: (required) The location of the NFS Server, in the form SERVER:/PATH + ◆ mount-path: (optional) The path at which the volume should be + mounted. The mount-path parameter is only supported for single + container services which do not make use of the --container flag. For + multi-container services, specify the mount-path parameter under the + --add-volume-mount flag. ◆ readonly: (optional) A boolean. If true, this volume will be read-only from all mounts. diff --git a/gcloud/run/help b/gcloud/run/help index 24a11e651..047842f77 100644 --- a/gcloud/run/help +++ b/gcloud/run/help @@ -44,6 +44,9 @@ GROUPS services View and manage your Cloud Run services. + worker-pools + View and manage your Cloud Run worker pools. + COMMANDS COMMAND is one of the following: diff --git a/gcloud/run/jobs/create b/gcloud/run/jobs/create index aff3f2718..92f0b6a3e 100644 --- a/gcloud/run/jobs/create +++ b/gcloud/run/jobs/create @@ -156,10 +156,11 @@ FLAGS --add-volume=[KEY=VALUE,...] Adds a volume to the Cloud Run resource. To add more than one volume, - specify this flag multiple times. Volumes must have a name and type - key. Only certain values are supported for type. Depending on the - provided type, other keys will be required. The following types are - supported with the specified additional keys: + specify this flag multiple times. Volumes must have a type key. Volumes + must have a name key if mount-path is not specified. A name key is + optional if mount-path is specified.Only certain values are supported + for type. Depending on the provided type, other keys will be required. + The following types are supported with the specified additional keys: cloud-storage: A volume representing a Cloud Storage bucket. This volume type is mounted using Cloud Storage FUSE. See @@ -172,11 +173,21 @@ FLAGS ◆ mount-options: (optional) A list of flags to pass to GCSFuse. Flags should be specified without leading dashes and separated by semicolons. + ◆ mount-path: (optional) The path at which the volume should be + mounted. The mount-path parameter is only supported for single + container services which do not make use of the --container flag. For + multi-container services, specify the mount-path parameter under the + --add-volume-mount flag. in-memory: An ephemeral volume that stores data in the instance's memory. With this type of volume, data is not shared between instances and all data will be lost when the instance it is on is terminated. Additional keys: + ◆ mount-path: (optional) The path at which the volume should be + mounted. The mount-path parameter is only supported for single + container services which do not make use of the --container flag. For + multi-container services, specify the mount-path parameter under the + --add-volume-mount flag. ◆ size-limit: (optional) A quantity representing the maximum amount of memory allocated to this volume, such as "512Mi" or "3G". Data stored in an in-memory volume consumes the memory allocation of the @@ -186,6 +197,11 @@ FLAGS nfs: Represents a volume backed by an NFS server. Additional keys: ◆ location: (required) The location of the NFS Server, in the form SERVER:/PATH + ◆ mount-path: (optional) The path at which the volume should be + mounted. The mount-path parameter is only supported for single + container services which do not make use of the --container flag. For + multi-container services, specify the mount-path parameter under the + --add-volume-mount flag. ◆ readonly: (optional) A boolean. If true, this volume will be read-only from all mounts. diff --git a/gcloud/run/jobs/deploy b/gcloud/run/jobs/deploy index 1578b5291..6efa1e920 100644 --- a/gcloud/run/jobs/deploy +++ b/gcloud/run/jobs/deploy @@ -161,10 +161,11 @@ FLAGS --add-volume=[KEY=VALUE,...] Adds a volume to the Cloud Run resource. To add more than one volume, - specify this flag multiple times. Volumes must have a name and type - key. Only certain values are supported for type. Depending on the - provided type, other keys will be required. The following types are - supported with the specified additional keys: + specify this flag multiple times. Volumes must have a type key. Volumes + must have a name key if mount-path is not specified. A name key is + optional if mount-path is specified.Only certain values are supported + for type. Depending on the provided type, other keys will be required. + The following types are supported with the specified additional keys: cloud-storage: A volume representing a Cloud Storage bucket. This volume type is mounted using Cloud Storage FUSE. See @@ -177,11 +178,21 @@ FLAGS ◆ mount-options: (optional) A list of flags to pass to GCSFuse. Flags should be specified without leading dashes and separated by semicolons. + ◆ mount-path: (optional) The path at which the volume should be + mounted. The mount-path parameter is only supported for single + container services which do not make use of the --container flag. For + multi-container services, specify the mount-path parameter under the + --add-volume-mount flag. in-memory: An ephemeral volume that stores data in the instance's memory. With this type of volume, data is not shared between instances and all data will be lost when the instance it is on is terminated. Additional keys: + ◆ mount-path: (optional) The path at which the volume should be + mounted. The mount-path parameter is only supported for single + container services which do not make use of the --container flag. For + multi-container services, specify the mount-path parameter under the + --add-volume-mount flag. ◆ size-limit: (optional) A quantity representing the maximum amount of memory allocated to this volume, such as "512Mi" or "3G". Data stored in an in-memory volume consumes the memory allocation of the @@ -191,6 +202,11 @@ FLAGS nfs: Represents a volume backed by an NFS server. Additional keys: ◆ location: (required) The location of the NFS Server, in the form SERVER:/PATH + ◆ mount-path: (optional) The path at which the volume should be + mounted. The mount-path parameter is only supported for single + container services which do not make use of the --container flag. For + multi-container services, specify the mount-path parameter under the + --add-volume-mount flag. ◆ readonly: (optional) A boolean. If true, this volume will be read-only from all mounts. diff --git a/gcloud/run/jobs/update b/gcloud/run/jobs/update index 722f79069..b3e1567ff 100644 --- a/gcloud/run/jobs/update +++ b/gcloud/run/jobs/update @@ -172,10 +172,11 @@ FLAGS --add-volume=[KEY=VALUE,...] Adds a volume to the Cloud Run resource. To add more than one volume, - specify this flag multiple times. Volumes must have a name and type - key. Only certain values are supported for type. Depending on the - provided type, other keys will be required. The following types are - supported with the specified additional keys: + specify this flag multiple times. Volumes must have a type key. Volumes + must have a name key if mount-path is not specified. A name key is + optional if mount-path is specified.Only certain values are supported + for type. Depending on the provided type, other keys will be required. + The following types are supported with the specified additional keys: cloud-storage: A volume representing a Cloud Storage bucket. This volume type is mounted using Cloud Storage FUSE. See @@ -188,11 +189,21 @@ FLAGS ◆ mount-options: (optional) A list of flags to pass to GCSFuse. Flags should be specified without leading dashes and separated by semicolons. + ◆ mount-path: (optional) The path at which the volume should be + mounted. The mount-path parameter is only supported for single + container services which do not make use of the --container flag. For + multi-container services, specify the mount-path parameter under the + --add-volume-mount flag. in-memory: An ephemeral volume that stores data in the instance's memory. With this type of volume, data is not shared between instances and all data will be lost when the instance it is on is terminated. Additional keys: + ◆ mount-path: (optional) The path at which the volume should be + mounted. The mount-path parameter is only supported for single + container services which do not make use of the --container flag. For + multi-container services, specify the mount-path parameter under the + --add-volume-mount flag. ◆ size-limit: (optional) A quantity representing the maximum amount of memory allocated to this volume, such as "512Mi" or "3G". Data stored in an in-memory volume consumes the memory allocation of the @@ -202,6 +213,11 @@ FLAGS nfs: Represents a volume backed by an NFS server. Additional keys: ◆ location: (required) The location of the NFS Server, in the form SERVER:/PATH + ◆ mount-path: (optional) The path at which the volume should be + mounted. The mount-path parameter is only supported for single + container services which do not make use of the --container flag. For + multi-container services, specify the mount-path parameter under the + --add-volume-mount flag. ◆ readonly: (optional) A boolean. If true, this volume will be read-only from all mounts. diff --git a/gcloud/run/services/update b/gcloud/run/services/update index ad5e783e6..a6b5ce70b 100644 --- a/gcloud/run/services/update +++ b/gcloud/run/services/update @@ -322,10 +322,11 @@ FLAGS --add-volume=[KEY=VALUE,...] Adds a volume to the Cloud Run resource. To add more than one volume, - specify this flag multiple times. Volumes must have a name and type - key. Only certain values are supported for type. Depending on the - provided type, other keys will be required. The following types are - supported with the specified additional keys: + specify this flag multiple times. Volumes must have a type key. Volumes + must have a name key if mount-path is not specified. A name key is + optional if mount-path is specified.Only certain values are supported + for type. Depending on the provided type, other keys will be required. + The following types are supported with the specified additional keys: cloud-storage: A volume representing a Cloud Storage bucket. This volume type is mounted using Cloud Storage FUSE. See @@ -338,11 +339,21 @@ FLAGS ◆ mount-options: (optional) A list of flags to pass to GCSFuse. Flags should be specified without leading dashes and separated by semicolons. + ◆ mount-path: (optional) The path at which the volume should be + mounted. The mount-path parameter is only supported for single + container services which do not make use of the --container flag. For + multi-container services, specify the mount-path parameter under the + --add-volume-mount flag. in-memory: An ephemeral volume that stores data in the instance's memory. With this type of volume, data is not shared between instances and all data will be lost when the instance it is on is terminated. Additional keys: + ◆ mount-path: (optional) The path at which the volume should be + mounted. The mount-path parameter is only supported for single + container services which do not make use of the --container flag. For + multi-container services, specify the mount-path parameter under the + --add-volume-mount flag. ◆ size-limit: (optional) A quantity representing the maximum amount of memory allocated to this volume, such as "512Mi" or "3G". Data stored in an in-memory volume consumes the memory allocation of the @@ -352,6 +363,11 @@ FLAGS nfs: Represents a volume backed by an NFS server. Additional keys: ◆ location: (required) The location of the NFS Server, in the form SERVER:/PATH + ◆ mount-path: (optional) The path at which the volume should be + mounted. The mount-path parameter is only supported for single + container services which do not make use of the --container flag. For + multi-container services, specify the mount-path parameter under the + --add-volume-mount flag. ◆ readonly: (optional) A boolean. If true, this volume will be read-only from all mounts. diff --git a/gcloud/run/worker-pools/add-iam-policy-binding b/gcloud/run/worker-pools/add-iam-policy-binding new file mode 100644 index 000000000..986a5baee --- /dev/null +++ b/gcloud/run/worker-pools/add-iam-policy-binding @@ -0,0 +1,139 @@ +NAME + gcloud run worker-pools add-iam-policy-binding - add IAM policy binding to + a Cloud Run worker pool + +SYNOPSIS + gcloud run worker-pools add-iam-policy-binding + (WORKERPOOL : --region=REGION) --member=PRINCIPAL --role=ROLE + [--condition=[KEY=VALUE,...] | --condition-from-file=PATH_TO_FILE] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Add an IAM policy binding to the IAM policy of a Cloud Run worker pool. One + binding consists of a member, and a role. + +EXAMPLES + To add an IAM policy binding for the role of 'roles/run.developer' for the + user 'test-user@gmail.com' with worker pool 'my-worker-pool' and region + 'us-central1', run: + + $ gcloud run worker-pools add-iam-policy-binding my-worker-pool \ + --region='us-central1' --member='user:test-user@gmail.com' \ + --role='roles/run.developer' + + See https://cloud.google.com/iam/docs/managing-policies for details of + policy role and member types. + +POSITIONAL ARGUMENTS + Workerpool resource - The worker pool for which to add IAM policy binding + to. 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 workerpool 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. + + WORKERPOOL + ID of the workerpool or fully qualified identifier for the + workerpool. + + To set the workerpool attribute: + ▸ provide the argument workerpool on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --region=REGION + The Cloud Run region. + + To set the region attribute: + ▸ provide the argument workerpool on the command line with a fully + specified name; + ▸ provide the argument --region on the command line; + ▸ set the property run/region; + ▸ specify from a list of available regions in a prompt. + +REQUIRED FLAGS + --member=PRINCIPAL + The principal to add the binding for. Should be of the form + user|group|serviceAccount:email or domain:domain. + + Examples: user:test-user@gmail.com, group:admins@example.com, + serviceAccount:test123@example.domain.com, or + domain:example.domain.com. + + Some resources also accept the following special values: + ◆ allUsers - Special identifier that represents anyone who is on the + internet, with or without a Google account. + ◆ allAuthenticatedUsers - Special identifier that represents anyone + who is authenticated with a Google account or a service account. + + --role=ROLE + Role name to assign to the principal. The role name is the complete + path of a predefined role, such as roles/logging.viewer, or the role ID + for a custom role, such as + organizations/{ORGANIZATION_ID}/roles/logging.viewer. + +OPTIONAL FLAGS + At most one of these can be specified: + + --condition=[KEY=VALUE,...] + A condition to include in the binding. When the condition is + explicitly specified as None (--condition=None), a binding without a + condition is added. When the condition is specified and is not None, + --role cannot be a basic role. Basic roles are roles/editor, + roles/owner, and roles/viewer. For more on conditions, refer to the + conditions overview guide: + https://cloud.google.com/iam/docs/conditions-overview + + When using the --condition flag, include the following key-value + pairs: + + expression + (Required) Condition expression that evaluates to True or False. + This uses a subset of Common Expression Language syntax. + + If the condition expression includes a comma, use a different + delimiter to separate the key-value pairs. Specify the delimiter + before listing the key-value pairs. For example, to specify a + colon (:) as the delimiter, do the following: + --condition=^:^title=TITLE:expression=EXPRESSION. For more + information, see + https://cloud.google.com/sdk/gcloud/reference/topic/escaping. + + title + (Required) A short string describing the purpose of the + expression. + + description + (Optional) Additional description for the expression. + + --condition-from-file=PATH_TO_FILE + Path to a local JSON or YAML file that defines the condition. To see + available fields, see the help for --condition. Use a full or + relative path to a local file containing the value of condition. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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 run/v1 API. The full documentation for this API can + be found at: https://cloud.google.com/run/ + +NOTES + These variants are also available: + + $ gcloud alpha run worker-pools add-iam-policy-binding + + $ gcloud beta run worker-pools add-iam-policy-binding + diff --git a/gcloud/run/worker-pools/delete b/gcloud/run/worker-pools/delete new file mode 100644 index 000000000..d2d02c184 --- /dev/null +++ b/gcloud/run/worker-pools/delete @@ -0,0 +1,70 @@ +NAME + gcloud run worker-pools delete - delete a worker-pool + +SYNOPSIS + gcloud run worker-pools delete (WORKER_POOL : --region=REGION) [--async] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Delete a worker-pool. + +EXAMPLES + To delete a worker-pool: + + $ gcloud run worker-pools delete + +POSITIONAL ARGUMENTS + WorkerPool resource - WorkerPool 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 WORKER_POOL on the command line with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + WORKER_POOL + ID of the WorkerPool or fully qualified identifier for the + WorkerPool. + + To set the worker-pool attribute: + ▸ provide the argument WORKER_POOL on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --region=REGION + The Cloud region for the WorkerPool. Overrides the default run/region + property value for this command invocation. + + To set the region attribute: + ▸ provide the argument WORKER_POOL on the command line with a fully + specified name; + ▸ provide the argument --region on the command line; + ▸ set the property run/region; + ▸ specify the region from an interactive prompt. + +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 run worker-pools delete + + $ gcloud beta run worker-pools delete + diff --git a/gcloud/run/worker-pools/deploy b/gcloud/run/worker-pools/deploy new file mode 100644 index 000000000..1a92949f4 --- /dev/null +++ b/gcloud/run/worker-pools/deploy @@ -0,0 +1,494 @@ +NAME + gcloud run worker-pools deploy - create or update a Cloud Run worker-pool + +SYNOPSIS + gcloud run worker-pools deploy [[WORKER_POOL] --region=REGION] [--async] + [--breakglass=JUSTIFICATION] [--container=CONTAINER] + [--description=DESCRIPTION] [--gpu-type=GPU_TYPE] + [--[no-]gpu-zonal-redundancy] [--instances=INSTANCES] [--no-promote] + [--remove-containers=[CONTAINER,...]] + [--revision-suffix=REVISION_SUFFIX] [--service-account=SERVICE_ACCOUNT] + [--vpc-egress=VPC_EGRESS] + [--add-cloudsql-instances=[CLOUDSQL-INSTANCES,...] + | --clear-cloudsql-instances + | --remove-cloudsql-instances=[CLOUDSQL-INSTANCES,...] + | --set-cloudsql-instances=[CLOUDSQL-INSTANCES,...]] + [--add-volume=[KEY=VALUE,...] + --clear-volumes --remove-volume=[VOLUME,...]] + [--add-volume-mount=[volume=NAME,mount-path=MOUNT_PATH,...] + --args=[ARG,...] --clear-volume-mounts --command=[COMMAND,...] + --cpu=CPU --depends-on=[CONTAINER,...] --gpu=GPU --memory=MEMORY + --remove-volume-mount=[MOUNT_PATH,...] --clear-env-vars + | --env-vars-file=FILE_PATH | --set-env-vars=[KEY=VALUE,...] + | --remove-env-vars=[KEY,...] + --update-env-vars=[KEY=VALUE,...] --clear-secrets + | --set-secrets=[KEY=VALUE,...] | --remove-secrets=[KEY,...] + --update-secrets=[KEY=VALUE,...] --image=IMAGE | --source=SOURCE] + [--binary-authorization=POLICY | --clear-binary-authorization] + [--clear-encryption-key-shutdown-hours + | --encryption-key-shutdown-hours=ENCRYPTION_KEY_SHUTDOWN_HOURS] + [--clear-key | --key=KEY] + [--clear-labels | --remove-labels=[KEY,...] --labels=[KEY=VALUE,...] + | --update-labels=[KEY=VALUE,...]] + [--clear-network + | --network=NETWORK --subnet=SUBNET --clear-network-tags + | --network-tags=[TAG,...]] + [--clear-post-key-revocation-action-type + | --post-key-revocation-action-type=POST_KEY_REVOCATION_ACTION_TYPE] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Creates or updates a Cloud Run worker-pool. + +EXAMPLES + To deploy a container to the worker-pool my-backend on Cloud Run: + + $ gcloud run worker-pools deploy my-backend \ + --image=us-docker.pkg.dev/project/image + + You may also omit the worker-pool name. Then a prompt will be displayed + with a suggested default value: + + $ gcloud run worker-pools deploy \ + --image=us-docker.pkg.dev/project/image + +POSITIONAL ARGUMENTS + WorkerPool resource - WorkerPool to deploy to. 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 WORKER_POOL on the command line with a fully + specified name; + ◆ specify the workerpool name from an interactive prompt with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + [WORKER_POOL] + ID of the WorkerPool or fully qualified identifier for the WorkerPool. + + To set the worker-pool attribute: + ◆ provide the argument WORKER_POOL on the command line; + ◆ specify the workerpool name from an interactive prompt. + + --region=REGION + The Cloud region for the WorkerPool. Overrides the default run/region + property value for this command invocation. + + To set the region attribute: + ◆ provide the argument WORKER_POOL on the command line with a fully + specified name; + ◆ specify the workerpool name from an interactive prompt with a fully + specified name; + ◆ provide the argument --region on the command line; + ◆ set the property run/region; + ◆ specify the region from an interactive prompt. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --breakglass=JUSTIFICATION + Justification to bypass Binary Authorization policy constraints and + allow the operation. See + https://cloud.google.com/binary-authorization/docs/using-breakglass for + more information. Next update or deploy command will automatically + clear existing breakglass justification. + + --container=CONTAINER + Specifies a container by name. Flags following --container will apply + to the specified container. + + Flags that are not container-specific must be specified before + --container. + + --description=DESCRIPTION + Provides an optional, human-readable description of the service. + + --gpu-type=GPU_TYPE + The GPU type to use. + + --[no-]gpu-zonal-redundancy + Set GPU zonal redundancy. Use --gpu-zonal-redundancy to enable and + --no-gpu-zonal-redundancy to disable. + + --instances=INSTANCES + The number of instances to run for this WorkerPool. Flag value should + be a positive integer to configure manual scaling with the given + integer as a fixed instance count. + + --no-promote + True to avoid assign instances to the worker revision being deployed. + Setting this flag assigns any instances assigned to the LATEST revision + to the specific revision bound to LATEST before the deployment. The + effect is that the revision being deployed will not receive instance + split. + + After a deployment with this flag the LATEST revision will not receive + instances on future deployments. To restore assigning instances to the + LATEST revision by default, run the gcloud run worker-pools + update-instance-split command with --to-latest. + + --remove-containers=[CONTAINER,...] + List of containers to remove. + + --revision-suffix=REVISION_SUFFIX + Specify the suffix of the revision name. Revision names always start + with the service name automatically. For example, specifying + [--revision-suffix=v1] for a service named 'helloworld', would lead to + a revision named 'helloworld-v1'. Set empty string to clear the suffix + and resume server-assigned naming. + + --service-account=SERVICE_ACCOUNT + the email address of an IAM service account associated with the + revision of the service. The service account represents the identity of + the running revision, and determines what permissions the revision has. + + --vpc-egress=VPC_EGRESS + Specify which of the outbound traffic to send through Direct VPC egress + or the VPC connector for this resource. This resource must have Direct + VPC egress enabled or a VPC connector to set this flag. VPC_EGRESS must + be one of: + + all + (DEPRECATED) Sends all outbound traffic through Direct VPC egress + or the VPC connector. Provides the same functionality as + 'all-traffic'. Prefer to use 'all-traffic' instead. + all-traffic + Sends all outbound traffic through Direct VPC egress or the VPC + connector. + private-ranges-only + Default option. Sends outbound traffic to private IP addresses (RFC + 1918 and Private Google Access IPs) through Direct VPC egress or + the VPC connector. + + Traffic to other Cloud Run services might require additional + configuration. See + https://cloud.google.com/run/docs/securing/private-networking#send_requests_to_other_services_and_services + for more information. + + These flags modify the Cloud SQL instances this WorkerPool connects to. + You can specify a name of a Cloud SQL instance if it's in the same project + and region as your Cloud Run worker pool; otherwise specify + :: for the instance. + + At most one of these can be specified: + + --add-cloudsql-instances=[CLOUDSQL-INSTANCES,...] + Append the given values to the current Cloud SQL instances. + + --clear-cloudsql-instances + Empty the current Cloud SQL instances. + + --remove-cloudsql-instances=[CLOUDSQL-INSTANCES,...] + Remove the given values from the current Cloud SQL instances. + + --set-cloudsql-instances=[CLOUDSQL-INSTANCES,...] + Completely replace the current Cloud SQL instances with the given + values. + + --add-volume=[KEY=VALUE,...] + Adds a volume to the Cloud Run resource. To add more than one volume, + specify this flag multiple times. Volumes must have a type key. Volumes + must have a name key if mount-path is not specified. A name key is + optional if mount-path is specified.Only certain values are supported + for type. Depending on the provided type, other keys will be required. + The following types are supported with the specified additional keys: + + cloud-storage: A volume representing a Cloud Storage bucket. This + volume type is mounted using Cloud Storage FUSE. See + https://cloud.google.com/storage/docs/gcs-fuse for the details and + limitations of this filesystem. Additional keys: + ◆ bucket: (required) the name of the bucket to use as the source of + this volume + ◆ readonly: (optional) A boolean. If true, this volume will be + read-only from all mounts. + ◆ mount-options: (optional) A list of flags to pass to GCSFuse. Flags + should be specified without leading dashes and separated by + semicolons. + ◆ mount-path: (optional) The path at which the volume should be + mounted. The mount-path parameter is only supported for single + container services which do not make use of the --container flag. For + multi-container services, specify the mount-path parameter under the + --add-volume-mount flag. + + in-memory: An ephemeral volume that stores data in the instance's + memory. With this type of volume, data is not shared between instances + and all data will be lost when the instance it is on is terminated. + Additional keys: + ◆ mount-path: (optional) The path at which the volume should be + mounted. The mount-path parameter is only supported for single + container services which do not make use of the --container flag. For + multi-container services, specify the mount-path parameter under the + --add-volume-mount flag. + ◆ size-limit: (optional) A quantity representing the maximum amount + of memory allocated to this volume, such as "512Mi" or "3G". Data + stored in an in-memory volume consumes the memory allocation of the + container that wrote the data. If size-limit is not specified, the + maximum size will be half the total memory limit of all containers. + + nfs: Represents a volume backed by an NFS server. Additional keys: + ◆ location: (required) The location of the NFS Server, in the form + SERVER:/PATH + ◆ mount-path: (optional) The path at which the volume should be + mounted. The mount-path parameter is only supported for single + container services which do not make use of the --container flag. For + multi-container services, specify the mount-path parameter under the + --add-volume-mount flag. + ◆ readonly: (optional) A boolean. If true, this volume will be + read-only from all mounts. + + --clear-volumes + Remove all existing volumes from the Cloud Run resource, including + volumes mounted as secrets + + --remove-volume=[VOLUME,...] + Removes volumes from the Cloud Run resource. + + Container Flags + + The following flags apply to the container. + + --add-volume-mount=[volume=NAME,mount-path=MOUNT_PATH,...] + Adds a mount to the current container. Must contain the keys + volume=NAME and mount-path=/PATH where NAME is the name of a volume on + this resource and PATH is the path within the container's filesystem to + mount this volume. + + --args=[ARG,...] + Comma-separated arguments passed to the command run by the container + image. If not specified and no '--command' is provided, the container + image's default Cmd is used. Otherwise, if not specified, no arguments + are passed. To reset this field to its default, pass an empty string. + + --clear-volume-mounts + Remove all existing mounts from the current container. + + --command=[COMMAND,...] + Entrypoint for the container image. If not specified, the container + image's default Entrypoint is run. To reset this field to its default, + pass an empty string. + + --cpu=CPU + Set a CPU limit in Kubernetes cpu units. + + Cloud Run supports values fractional values below 1, 1, 2, 4, and 8. + Some CPU values requires a minimum Memory --memory value. + + --depends-on=[CONTAINER,...] + List of container dependencies to add to the current container. + + --gpu=GPU + Cloud Run supports values 0 or 1. 1 gpu also requires a minimum 4 --cpu + value and a minimum 16Gi --memory value. + + --memory=MEMORY + Set a memory limit. Ex: 1024Mi, 4Gi. + + --remove-volume-mount=[MOUNT_PATH,...] + Removes the volume mounted at the specified path from the current + container. + + At most one of these can be specified: + + --clear-env-vars + Remove all environment variables. + + --env-vars-file=FILE_PATH + Path to a local YAML or ENV file with definitions for all environment + variables. All existing environment variables will be removed before + the new environment variables are added. Example YAML content: + + KEY_1: "value1" + KEY_2: "value 2" + + Example ENV content: + + KEY_1="value1" + KEY_2="value 2" + + --set-env-vars=[KEY=VALUE,...] + List of key-value pairs to set as environment variables. All existing + environment variables will be removed first. + + Or at least one of these can be specified: + + Only --update-env-vars and --remove-env-vars can be used together. If + both are specified, --remove-env-vars will be applied first. + + --remove-env-vars=[KEY,...] + List of environment variables to be removed. + + --update-env-vars=[KEY=VALUE,...] + List of key-value pairs to set as environment variables. + + Specify secrets to provide as environment variables. For example: + '--set-secrets=ENV=mysecret:latest,OTHER_ENV=othersecret:1' will create an + environment variable named ENV whose value is the latest version of secret + 'mysecret' and an environment variable OTHER_ENV whose value is version of + 1 of secret 'othersecret'. + + At most one of these can be specified: + + --clear-secrets + Remove all secrets. + + --set-secrets=[KEY=VALUE,...] + List of key-value pairs to set as secrets. All existing secrets will + be removed first. + + Or at least one of these can be specified: + + Only --update-secrets and --remove-secrets can be used together. If + both are specified, --remove-secrets will be applied first. + + --remove-secrets=[KEY,...] + List of secrets to be removed. + + --update-secrets=[KEY=VALUE,...] + List of key-value pairs to set as secrets. + + At most one of these can be specified: + + --image=IMAGE + Name of the container image to deploy (e.g. + us-docker.pkg.dev/cloudrun/container/hello:latest). + + --source=SOURCE + The location of the source to build. If a Dockerfile is present in + the source code directory, it will be built using that Dockerfile, + otherwise it will use Google Cloud buildpacks. See + https://cloud.google.com/run/docs/deploying-source-code for more + details. The location can be a directory on a local disk or a gzipped + archive file (.tar.gz) in Google Cloud Storage. If the source is a + local directory, this command skips the files specified in the + --ignore-file. If --ignore-file is not specified, use .gcloudignore + file. If a .gcloudignore file is absent and a .gitignore file is + present in the local source directory, gcloud will use a generated + Git-compatible .gcloudignore file that respects your .gitignored + files. The global .gitignore is not respected. For more information + on .gcloudignore, see gcloud topic gcloudignore. + + At most one of these can be specified: + + --binary-authorization=POLICY + Binary Authorization policy to check against. This must be set to + "default". + + --clear-binary-authorization + Remove any previously set Binary Authorization policy. + + At most one of these can be specified: + + --clear-encryption-key-shutdown-hours + Remove any previously set CMEK key shutdown hours setting. + + --encryption-key-shutdown-hours=ENCRYPTION_KEY_SHUTDOWN_HOURS + The number of hours to wait before an automatic shutdown server after + CMEK key revocation is detected. + + At most one of these can be specified: + + --clear-key + Remove any previously set CMEK key reference. + + --key=KEY + CMEK key reference to encrypt the container with. + + 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 run worker-pools deploy --clear-labels + + To remove all existing labels and create two new labels, foo and baz: + + $ gcloud run worker-pools deploy --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. + + At most one of these can be specified: + + --labels=[KEY=VALUE,...] + List of label KEY=VALUE pairs to add. + + An alias to --update-labels. + + --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. + + At most one of these can be specified: + + --clear-network + Disconnect this Cloud Run worker from the VPC network it is connected + to. + + Or at least one of these can be specified: + + Direct VPC egress setting flags group. + + --network=NETWORK + The VPC network that the Cloud Run worker will be able to send + traffic to. If --subnet is also specified, subnet must be a + subnetwork of the network specified by this --network flag. To + clear existing VPC network settings, use --clear-network. + + --subnet=SUBNET + The VPC subnetwork that the Cloud Run worker will get IPs from. The + subnetwork must be /26 or larger. If --network is also specified, + subnet must be a subnetwork of the network specified by the + --network flag. If --network is not specified, network will be + looked up from this subnetwork. To clear existing VPC network + settings, use --clear-network. + + At most one of these can be specified: + + --clear-network-tags + Clears all existing network tags from the Cloud Run worker. + + --network-tags=[TAG,...] + Applies the given network tags (comma separated) to the Cloud Run + worker. To clear existing tags, use --clear-network-tags. + + At most one of these can be specified: + + --clear-post-key-revocation-action-type + Remove any previously set post CMEK key revocation action type. + + --post-key-revocation-action-type=POST_KEY_REVOCATION_ACTION_TYPE + Action type after CMEK key revocation. + POST_KEY_REVOCATION_ACTION_TYPE must be one of: + + prevent-new + No new instances will be started after CMEK key revocation. + shut-down + No new instances will be started and the existing instances will + be shut down after CMEK key revocation. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --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 run worker-pools deploy + + $ gcloud beta run worker-pools deploy + diff --git a/gcloud/run/worker-pools/describe b/gcloud/run/worker-pools/describe new file mode 100644 index 000000000..9f1867026 --- /dev/null +++ b/gcloud/run/worker-pools/describe @@ -0,0 +1,64 @@ +NAME + gcloud run worker-pools describe - obtain details about a given worker-pool + +SYNOPSIS + gcloud run worker-pools describe WORKER_POOL [--region=REGION] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Obtain details about a given worker-pool. + +EXAMPLES + To obtain details about a given worker-pool: + + $ gcloud run worker-pools describe + + To get those details in the YAML format: + + $ gcloud run worker-pools describe --format=yaml + + To get them in YAML format suited to export (omitting metadata specific to + this deployment and status info): + + $ gcloud run worker-pools describe --format=export + +POSITIONAL ARGUMENTS + WorkerPool resource - WorkerPool to describe. This represents a Cloud + resource. (NOTE) Some attributes are not given arguments in this group but + can be set in other ways. + + To set the project attribute: + ◆ provide the argument WORKER_POOL on the command line with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + WORKER_POOL + ID of the WorkerPool or fully qualified identifier for the + WorkerPool. + + To set the worker-pool attribute: + ▸ provide the argument WORKER_POOL on the command line. + +FLAGS + --region=REGION + Region in which the resource can be found. Alternatively, set the + property [run/region]. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + These variants are also available: + + $ gcloud alpha run worker-pools describe + + $ gcloud beta run worker-pools describe + diff --git a/gcloud/run/worker-pools/get-iam-policy b/gcloud/run/worker-pools/get-iam-policy new file mode 100644 index 000000000..2563df389 --- /dev/null +++ b/gcloud/run/worker-pools/get-iam-policy @@ -0,0 +1,101 @@ +NAME + gcloud run worker-pools get-iam-policy - get the IAM policy for a Cloud Run + worker pool + +SYNOPSIS + gcloud run worker-pools get-iam-policy (WORKERPOOL : --region=REGION) + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + This command gets the IAM policy for a worker pool. If formatted as JSON, + the output can be edited and used as a policy file for set-iam-policy. The + output includes an "etag" field identifying the version emitted and + allowing detection of concurrent policy updates; see $ gcloud alpha run + registries set-iam-policy for additional details. + +EXAMPLES + To print the IAM policy for a given worker pool, run: + + $ gcloud run worker-pools get-iam-policy --region=us-central1 \ + my-worker-pool + +POSITIONAL ARGUMENTS + Workerpool resource - The worker pool for which to display the IAM policy. + The arguments in this group can be used to specify the attributes of this + resource. (NOTE) Some attributes are not given arguments in this group but + can be set in other ways. + + To set the project attribute: + ◆ provide the argument workerpool 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. + + WORKERPOOL + ID of the workerpool or fully qualified identifier for the + workerpool. + + To set the workerpool attribute: + ▸ provide the argument workerpool on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --region=REGION + The Cloud Run region. + + To set the region attribute: + ▸ provide the argument workerpool on the command line with a fully + specified name; + ▸ provide the argument --region on the command line; + ▸ set the property run/region; + ▸ specify from a list of available regions in a prompt. + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the run/v1 API. The full documentation for this API can + be found at: https://cloud.google.com/run/ + +NOTES + These variants are also available: + + $ gcloud alpha run worker-pools get-iam-policy + + $ gcloud beta run worker-pools get-iam-policy + diff --git a/gcloud/run/worker-pools/help b/gcloud/run/worker-pools/help new file mode 100644 index 000000000..e46ccc7a1 --- /dev/null +++ b/gcloud/run/worker-pools/help @@ -0,0 +1,73 @@ +NAME + gcloud run worker-pools - view and manage your Cloud Run worker pools + +SYNOPSIS + gcloud run worker-pools GROUP | COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + This set of commands can be used to view and manage your Cloud Run worker + pools. + +EXAMPLES + To list your existing worker-pools, run: + + $ gcloud run worker-pools list + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +GROUPS + GROUP is one of the following: + + logs + Read logs for Cloud Run worker pools. + + revisions + View and manage your Cloud Run WorkerPools revisions. + +COMMANDS + COMMAND is one of the following: + + add-iam-policy-binding + Add IAM policy binding to a Cloud Run worker pool. + + delete + Delete a worker-pool. + + deploy + Create or update a Cloud Run worker-pool. + + describe + Obtain details about a given worker-pool. + + get-iam-policy + Get the IAM policy for a Cloud Run worker pool. + + list + List available worker-pools. + + remove-iam-policy-binding + Remove IAM policy binding of a Cloud Run worker pool. + + replace + Create or replace a worker-pool from a YAML worker-pool specification. + + set-iam-policy + Set the IAM policy for a worker pool. + + update + Update Cloud Run environment variables and other configuration + settings. + + update-instance-split + Adjust the instance assignments for a Cloud Run worker-pool. + +NOTES + These variants are also available: + + $ gcloud alpha run worker-pools + + $ gcloud beta run worker-pools + diff --git a/gcloud/alpha/lifesciences/locations/list b/gcloud/run/worker-pools/list similarity index 71% rename from gcloud/alpha/lifesciences/locations/list rename to gcloud/run/worker-pools/list index 48825caaf..bb4e5bec3 100644 --- a/gcloud/alpha/lifesciences/locations/list +++ b/gcloud/run/worker-pools/list @@ -1,19 +1,23 @@ NAME - gcloud alpha lifesciences locations list - list all locations where Cloud - Life Sciences is available + gcloud run worker-pools list - list available worker-pools SYNOPSIS - gcloud alpha lifesciences locations list [--filter=EXPRESSION] + gcloud run worker-pools list [--region=REGION] [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) List all locations where Cloud Life Sciences is available. + List available worker-pools. EXAMPLES - To list all locations, run: + To list available worker-pools: - $ gcloud alpha lifesciences locations list + $ gcloud run worker-pools list + +FLAGS + --region=REGION + Region in which the resource can be found. Alternatively, set the + property [run/region]. LIST COMMAND FLAGS --filter=EXPRESSION @@ -55,15 +59,10 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. -API REFERENCE - This command uses the lifesciences/v2beta API. The full documentation for - this API can be found at: https://cloud.google.com/life-sciences - NOTES - This command is currently in alpha and might change without notice. If this - command fails 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: + These variants are also available: - $ gcloud beta lifesciences locations list + $ gcloud alpha run worker-pools list + + $ gcloud beta run worker-pools list diff --git a/gcloud/run/worker-pools/logs/help b/gcloud/run/worker-pools/logs/help new file mode 100644 index 000000000..a9857bcbe --- /dev/null +++ b/gcloud/run/worker-pools/logs/help @@ -0,0 +1,45 @@ +NAME + gcloud run worker-pools logs - read logs for Cloud Run worker pools + +SYNOPSIS + gcloud run worker-pools logs COMMAND [--region=REGION] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Read logs for Cloud Run worker pools. + +EXAMPLES + To tail logs for a worker pool, run: + + $ gcloud run worker-pools logs tail my-worker-pool + + To read logs for a worker pool, run: + + $ gcloud run worker-pools logs read my-worker-pool + +FLAGS + --region=REGION + Region in which the resource can be found. Alternatively, set the + property [run/region]. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + read + Read logs for a Cloud Run worker pool. + + tail + Tail logs for a Cloud Run worker pool. + +NOTES + These variants are also available: + + $ gcloud alpha run worker-pools logs + + $ gcloud beta run worker-pools logs + diff --git a/gcloud/run/worker-pools/logs/read b/gcloud/run/worker-pools/logs/read new file mode 100644 index 000000000..c8884d45f --- /dev/null +++ b/gcloud/run/worker-pools/logs/read @@ -0,0 +1,84 @@ +NAME + gcloud run worker-pools logs read - read logs for a Cloud Run worker pool + +SYNOPSIS + gcloud run worker-pools logs read WORKER_POOL + [--freshness=FRESHNESS; default="1d"] [--log-filter=LOG_FILTER] + [--order=ORDER; default="desc"] [--region=REGION] [--limit=LIMIT] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + gcloud run worker-pools logs read reads log entries. Log entries matching + --log-filter are returned according to the specified --order. If the log + entries come from multiple logs, then entries from different logs might be + intermingled in the results. + +EXAMPLES + To read log entries from for a Cloud Run Worker Pool, run: + + $ gcloud run worker-pools logs read my-worker-pool + + To read log entries with severity ERROR or higher, run: + + $ gcloud run worker-pools logs read my-worker-pool \ + --log-filter="severity>=ERROR" + + To read log entries written in a specific time window, run: + + $ gcloud run worker-pools logs read my-worker-pool \ + --log-filter='timestamp<="2015-05-31T23:59:59Z" AND + timestamp>="2015-05-31T00:00:00Z"' + + To read up to 10 log entries in your worker pool payloads that include the + word SearchText and format the output in JSON format, run: + + $ gcloud run worker-pools logs read my-worker-pool \ + --log-filter="textPayload:SearchText" --limit=10 --format=json + + Detailed information about filters can be found at: + https://cloud.google.com/logging/docs/view/advanced_filters + +POSITIONAL ARGUMENTS + WORKER_POOL + Name for a Cloud Run worker pool. + +FLAGS + --freshness=FRESHNESS; default="1d" + Return entries that are not older than this value. Works only with DESC + ordering and filters without a timestamp. See $ gcloud topic datetimes + for information on duration formats. + + --log-filter=LOG_FILTER + Filter expression that specifies the log entries to return. Detailed + information about filters can be found at: + https://cloud.google.com/logging/docs/view/logging-query-language + + --order=ORDER; default="desc" + Ordering of returned log entries based on timestamp field. ORDER must + be one of: desc, asc. + + --region=REGION + Region in which the resource can be found. Alternatively, set the + property [run/region]. + +LIST COMMAND FLAGS + --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. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --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 run worker-pools logs read + + $ gcloud beta run worker-pools logs read + diff --git a/gcloud/run/worker-pools/logs/tail b/gcloud/run/worker-pools/logs/tail new file mode 100644 index 000000000..c7bc87d7d --- /dev/null +++ b/gcloud/run/worker-pools/logs/tail @@ -0,0 +1,54 @@ +NAME + gcloud run worker-pools logs tail - tail logs for a Cloud Run worker pool + +SYNOPSIS + gcloud run worker-pools logs tail WORKER_POOL [--log-filter=LOG_FILTER] + [--region=REGION] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + gcloud run worker-pools logs tail tails log-entries for a particular Cloud + Run worker pool in real time. The log entries are formatted for consumption + in a terminal. + +EXAMPLES + To tail log entries for a Cloud Run Worker Pool, run: + + $ gcloud run worker-pools logs tail my-worker-pool + + To tail log entries with severity ERROR or higher, run: + + $ gcloud run worker-pools logs tail my-worker-pool \ + --log-filter="severity>=ERROR" + + Detailed information about filters can be found at: + https://cloud.google.com/logging/docs/view/advanced_filters + +POSITIONAL ARGUMENTS + WORKER_POOL + Name for a Cloud Run worker pool. + +FLAGS + --log-filter=LOG_FILTER + Filter expression that specifies the log entries to return. Detailed + information about filters can be found at: + https://cloud.google.com/logging/docs/view/logging-query-language + + --region=REGION + Region in which the resource can be found. Alternatively, set the + property [run/region]. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + These variants are also available: + + $ gcloud alpha run worker-pools logs tail + + $ gcloud beta run worker-pools logs tail + diff --git a/gcloud/run/worker-pools/remove-iam-policy-binding b/gcloud/run/worker-pools/remove-iam-policy-binding new file mode 100644 index 000000000..8d5e5265f --- /dev/null +++ b/gcloud/run/worker-pools/remove-iam-policy-binding @@ -0,0 +1,144 @@ +NAME + gcloud run worker-pools remove-iam-policy-binding - remove IAM policy + binding of a Cloud Run worker pool + +SYNOPSIS + gcloud run worker-pools remove-iam-policy-binding + (WORKERPOOL : --region=REGION) --member=PRINCIPAL --role=ROLE + [--all | --condition=[KEY=VALUE,...] + | --condition-from-file=PATH_TO_FILE] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Remove an IAM policy binding from the IAM policy of a worker pool. One + binding consists of a member, and a role. + +EXAMPLES + To remove an IAM policy binding for the role of 'roles/run.developer' for + the user 'test-user@gmail.com' with worker pool 'my-worker-pool' and region + 'us-central1', run: + + $ gcloud run worker-pools remove-iam-policy-binding my-worker-pool \ + --region='us-central1' --member='user:test-user@gmail.com' \ + --role='roles/run.developer' + + See https://cloud.google.com/iam/docs/managing-policies for details of + policy role and member types. + +POSITIONAL ARGUMENTS + Workerpool resource - The service for which to remove the IAM policy + 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 workerpool 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. + + WORKERPOOL + ID of the workerpool or fully qualified identifier for the + workerpool. + + To set the workerpool attribute: + ▸ provide the argument workerpool on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --region=REGION + The Cloud Run region. + + To set the region attribute: + ▸ provide the argument workerpool on the command line with a fully + specified name; + ▸ provide the argument --region on the command line; + ▸ set the property run/region; + ▸ specify from a list of available regions in a prompt. + +REQUIRED FLAGS + --member=PRINCIPAL + The principal to remove the binding for. Should be of the form + user|group|serviceAccount:email or domain:domain. + + Examples: user:test-user@gmail.com, group:admins@example.com, + serviceAccount:test123@example.domain.com, or + domain:example.domain.com. + + Deleted principals have an additional deleted: prefix and a ?uid=UID + suffix, where UID is a unique identifier for the principal. Example: + deleted:user:test-user@gmail.com?uid=123456789012345678901. + + Some resources also accept the following special values: + ◆ allUsers - Special identifier that represents anyone who is on the + internet, with or without a Google account. + ◆ allAuthenticatedUsers - Special identifier that represents anyone + who is authenticated with a Google account or a service account. + + --role=ROLE + The role to remove the principal from. + +OPTIONAL FLAGS + At most one of these can be specified: + + --all + Remove all bindings with this role and principal, irrespective of any + conditions. + + --condition=[KEY=VALUE,...] + The condition of the binding that you want to remove. When the + condition is explicitly specified as None (--condition=None), a + binding without a condition is removed. Otherwise, only a binding + with a condition that exactly matches the specified condition + (including the optional description) is removed. For more on + conditions, refer to the conditions overview guide: + https://cloud.google.com/iam/docs/conditions-overview + + When using the --condition flag, include the following key-value + pairs: + + expression + (Required) Condition expression that evaluates to True or False. + This uses a subset of Common Expression Language syntax. + + If the condition expression includes a comma, use a different + delimiter to separate the key-value pairs. Specify the delimiter + before listing the key-value pairs. For example, to specify a + colon (:) as the delimiter, do the following: + --condition=^:^title=TITLE:expression=EXPRESSION. For more + information, see + https://cloud.google.com/sdk/gcloud/reference/topic/escaping. + + title + (Required) A short string describing the purpose of the + expression. + + description + (Optional) Additional description for the expression. + + --condition-from-file=PATH_TO_FILE + Path to a local JSON or YAML file that defines the condition. To see + available fields, see the help for --condition. Use a full or + relative path to a local file containing the value of condition. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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 run/v1 API. The full documentation for this API can + be found at: https://cloud.google.com/run/ + +NOTES + These variants are also available: + + $ gcloud alpha run worker-pools remove-iam-policy-binding + + $ gcloud beta run worker-pools remove-iam-policy-binding + diff --git a/gcloud/run/worker-pools/replace b/gcloud/run/worker-pools/replace new file mode 100644 index 000000000..a097437c3 --- /dev/null +++ b/gcloud/run/worker-pools/replace @@ -0,0 +1,46 @@ +NAME + gcloud run worker-pools replace - create or replace a worker-pool from a + YAML worker-pool specification + +SYNOPSIS + gcloud run worker-pools replace FILE [--async] [--dry-run] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Creates or replaces a worker-pool from a YAML worker-pool specification. + +EXAMPLES + To replace the specification for a worker-pool defined in + my-worker-pool.yaml + + $ gcloud run worker-pools replace my-worker-pool.yaml + +POSITIONAL ARGUMENTS + FILE + The absolute path to the YAML file with a Cloud Run worker-pool + definition for the worker-pool to update or create. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --dry-run + If set to true, only validates the configuration. The configuration + will not be applied. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --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 run worker-pools replace + + $ gcloud beta run worker-pools replace + diff --git a/gcloud/run/worker-pools/revisions/delete b/gcloud/run/worker-pools/revisions/delete new file mode 100644 index 000000000..5448e1aa6 --- /dev/null +++ b/gcloud/run/worker-pools/revisions/delete @@ -0,0 +1,81 @@ +NAME + gcloud run worker-pools revisions delete - delete a worker pool revision + +SYNOPSIS + gcloud run worker-pools revisions delete + (WORKER_POOL_REVISION : --region=REGION --worker-pool=WORKER_POOL) + [--async] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Delete a worker pool revision. + +EXAMPLES + To delete a revision rev1 of a worker pool worker1 in us-central1: + + $ gcloud run worker-pools revisions delete rev1 \ + --region=us-central1 --worker-pool=worker1 + +POSITIONAL ARGUMENTS + WorkerPoolRevision resource - Worker pool revision 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 WORKER_POOL_REVISION on the command line with a + fully specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + WORKER_POOL_REVISION + ID of the WorkerPoolRevision or fully qualified identifier for the + WorkerPoolRevision. + + To set the revision attribute: + ▸ provide the argument WORKER_POOL_REVISION on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --region=REGION + The Cloud region for the WorkerPoolRevision. Overrides the default + run/region property value for this command invocation. + + To set the region attribute: + ▸ provide the argument WORKER_POOL_REVISION on the command line + with a fully specified name; + ▸ provide the argument --region on the command line; + ▸ set the property run/region; + ▸ specify the region from an interactive prompt. + + --worker-pool=WORKER_POOL + WorkerPool for the WorkerPoolRevision. + + To set the worker-pool attribute: + ▸ provide the argument WORKER_POOL_REVISION on the command line + with a fully specified name; + ▸ provide the argument --worker-pool on the command line; + ▸ specify the workerpool name from an interactive prompt. + +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 run worker-pools revisions delete + + $ gcloud beta run worker-pools revisions delete + diff --git a/gcloud/run/worker-pools/revisions/describe b/gcloud/run/worker-pools/revisions/describe new file mode 100644 index 000000000..2742b6d35 --- /dev/null +++ b/gcloud/run/worker-pools/revisions/describe @@ -0,0 +1,56 @@ +NAME + gcloud run worker-pools revisions describe - obtain details about a given + worker pool revision + +SYNOPSIS + gcloud run worker-pools revisions describe WORKER_POOL_REVISION + [--region=REGION] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Obtain details about a given worker pool revision. + +EXAMPLES + To describe a revision rev.1 in us-central1: + + $ gcloud run worker-pools revisions describe rev.1 \ + --region=us-central1 + +POSITIONAL ARGUMENTS + Revision resource - Worker pool revision to describe. This represents a + Cloud resource. (NOTE) Some attributes are not given arguments in this + group but can be set in other ways. + + To set the project attribute: + ◆ provide the argument WORKER_POOL_REVISION on the command line with a + fully specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + WORKER_POOL_REVISION + ID of the revision or fully qualified identifier for the revision. + + To set the revision attribute: + ▸ provide the argument WORKER_POOL_REVISION on the command line. + +FLAGS + --region=REGION + Region in which the resource can be found. Alternatively, set the + property [run/region]. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + These variants are also available: + + $ gcloud alpha run worker-pools revisions describe + + $ gcloud beta run worker-pools revisions describe + diff --git a/gcloud/run/worker-pools/revisions/help b/gcloud/run/worker-pools/revisions/help new file mode 100644 index 000000000..7ccdac2f1 --- /dev/null +++ b/gcloud/run/worker-pools/revisions/help @@ -0,0 +1,40 @@ +NAME + gcloud run worker-pools revisions - view and manage your Cloud Run + WorkerPools revisions + +SYNOPSIS + gcloud run worker-pools revisions COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + This set of commands can be used to view and manage your existing Cloud Run + WorkerPools revisions. + +EXAMPLES + To list your existing worker pools revisions, run: + + $ gcloud run worker-pools revisions list + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + delete + Delete a worker pool revision. + + describe + Obtain details about a given worker pool revision. + + list + List available worker pool revisions. + +NOTES + These variants are also available: + + $ gcloud alpha run worker-pools revisions + + $ gcloud beta run worker-pools revisions + diff --git a/gcloud/run/worker-pools/revisions/list b/gcloud/run/worker-pools/revisions/list new file mode 100644 index 000000000..3d7287e05 --- /dev/null +++ b/gcloud/run/worker-pools/revisions/list @@ -0,0 +1,73 @@ +NAME + gcloud run worker-pools revisions list - list available worker pool + revisions + +SYNOPSIS + gcloud run worker-pools revisions list [--region=REGION] + [--worker-pool=WORKER_POOL] [--filter=EXPRESSION] [--limit=LIMIT] + [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + List available worker pool revisions. + +EXAMPLES + To list all revisions in a worker pool foo: + + $ gcloud run worker-pools revisions list --worker-pool=foo + +FLAGS + --region=REGION + Region in which the resource can be found. Alternatively, set the + property [run/region]. + + --worker-pool=WORKER_POOL + Limit matched revisions to the given worker. + +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 run worker-pools revisions list + + $ gcloud beta run worker-pools revisions list + diff --git a/gcloud/run/worker-pools/set-iam-policy b/gcloud/run/worker-pools/set-iam-policy new file mode 100644 index 000000000..acf6af1b7 --- /dev/null +++ b/gcloud/run/worker-pools/set-iam-policy @@ -0,0 +1,88 @@ +NAME + gcloud run worker-pools set-iam-policy - set the IAM policy for a worker + pool + +SYNOPSIS + gcloud run worker-pools set-iam-policy (WORKERPOOL : --region=REGION) + POLICY_FILE [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + This command replaces the existing IAM policy for a worker pool, given a + worker pool and a file encoded in JSON or YAML that contains the IAM + policy. If the given policy file specifies an "etag" value, then the + replacement will succeed only if the policy already in place matches that + etag. (An etag obtain via get-iam-policy will prevent the replacement if + the policy for the worker pool has been subsequently updated.) A policy + file that does not contain an etag value will replace any existing policy + for the worker pool. + +EXAMPLES + The following command will read an IAM policy defined in a JSON file + 'policy.json' and set it for a worker pool with identifier 'my-worker-pool' + + $ gcloud run worker-pools set-iam-policy --region=us-central1 \ + my-worker-pool policy.json + + See https://cloud.google.com/iam/docs/managing-policies for details of the + policy file format and contents. + +POSITIONAL ARGUMENTS + Workerpool resource - The service for which to set the IAM policy. The + arguments in this group can be used to specify the attributes of this + resource. (NOTE) Some attributes are not given arguments in this group but + can be set in other ways. + + To set the project attribute: + ◆ provide the argument workerpool 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. + + WORKERPOOL + ID of the workerpool or fully qualified identifier for the + workerpool. + + To set the workerpool attribute: + ▸ provide the argument workerpool on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --region=REGION + The Cloud Run region. + + To set the region attribute: + ▸ provide the argument workerpool on the command line with a fully + specified name; + ▸ provide the argument --region on the command line; + ▸ set the property run/region; + ▸ specify from a list of available regions in a prompt. + + POLICY_FILE + Path to a local JSON or YAML formatted file containing a valid policy. + + The output of the get-iam-policy command is a valid file, as is any + JSON or YAML file conforming to the structure of a Policy + (https://cloud.google.com/iam/reference/rest/v1/Policy). + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the run/v1 API. The full documentation for this API can + be found at: https://cloud.google.com/run/ + +NOTES + These variants are also available: + + $ gcloud alpha run worker-pools set-iam-policy + + $ gcloud beta run worker-pools set-iam-policy + diff --git a/gcloud/run/worker-pools/update b/gcloud/run/worker-pools/update new file mode 100644 index 000000000..25278e379 --- /dev/null +++ b/gcloud/run/worker-pools/update @@ -0,0 +1,473 @@ +NAME + gcloud run worker-pools update - update Cloud Run environment variables and + other configuration settings + +SYNOPSIS + gcloud run worker-pools update [[WORKER_POOL] --region=REGION] [--async] + [--breakglass=JUSTIFICATION] [--container=CONTAINER] + [--description=DESCRIPTION] [--gpu-type=GPU_TYPE] + [--[no-]gpu-zonal-redundancy] [--instances=INSTANCES] [--no-promote] + [--remove-containers=[CONTAINER,...]] + [--revision-suffix=REVISION_SUFFIX] [--service-account=SERVICE_ACCOUNT] + [--vpc-egress=VPC_EGRESS] + [--add-cloudsql-instances=[CLOUDSQL-INSTANCES,...] + | --clear-cloudsql-instances + | --remove-cloudsql-instances=[CLOUDSQL-INSTANCES,...] + | --set-cloudsql-instances=[CLOUDSQL-INSTANCES,...]] + [--add-volume=[KEY=VALUE,...] + --clear-volumes --remove-volume=[VOLUME,...]] + [--add-volume-mount=[volume=NAME,mount-path=MOUNT_PATH,...] + --args=[ARG,...] --clear-volume-mounts --command=[COMMAND,...] + --cpu=CPU --depends-on=[CONTAINER,...] --gpu=GPU --image=IMAGE + --memory=MEMORY + --remove-volume-mount=[MOUNT_PATH,...] --clear-env-vars + | --env-vars-file=FILE_PATH | --set-env-vars=[KEY=VALUE,...] + | --remove-env-vars=[KEY,...] + --update-env-vars=[KEY=VALUE,...] --clear-secrets + | --set-secrets=[KEY=VALUE,...] + | --remove-secrets=[KEY,...] --update-secrets=[KEY=VALUE,...]] + [--binary-authorization=POLICY | --clear-binary-authorization] + [--clear-encryption-key-shutdown-hours + | --encryption-key-shutdown-hours=ENCRYPTION_KEY_SHUTDOWN_HOURS] + [--clear-key | --key=KEY] + [--clear-labels | --remove-labels=[KEY,...] --labels=[KEY=VALUE,...] + | --update-labels=[KEY=VALUE,...]] + [--clear-network + | --network=NETWORK --subnet=SUBNET --clear-network-tags + | --network-tags=[TAG,...]] + [--clear-post-key-revocation-action-type + | --post-key-revocation-action-type=POST_KEY_REVOCATION_ACTION_TYPE] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Update Cloud Run environment variables and other configuration settings. + +EXAMPLES + To update one or more env vars: + + $ gcloud run worker-pools update myworkerpool \ + --update-env-vars=KEY1=VALUE1,KEY2=VALUE2 + +POSITIONAL ARGUMENTS + WorkerPool resource - WorkerPool to update the configuration of. 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 WORKER_POOL on the command line with a fully + specified name; + ◆ specify the workerpool name from an interactive prompt with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + [WORKER_POOL] + ID of the WorkerPool or fully qualified identifier for the WorkerPool. + + To set the worker-pool attribute: + ◆ provide the argument WORKER_POOL on the command line; + ◆ specify the workerpool name from an interactive prompt. + + --region=REGION + The Cloud region for the WorkerPool. Overrides the default run/region + property value for this command invocation. + + To set the region attribute: + ◆ provide the argument WORKER_POOL on the command line with a fully + specified name; + ◆ specify the workerpool name from an interactive prompt with a fully + specified name; + ◆ provide the argument --region on the command line; + ◆ set the property run/region; + ◆ specify the region from an interactive prompt. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --breakglass=JUSTIFICATION + Justification to bypass Binary Authorization policy constraints and + allow the operation. See + https://cloud.google.com/binary-authorization/docs/using-breakglass for + more information. Next update or deploy command will automatically + clear existing breakglass justification. + + --container=CONTAINER + Specifies a container by name. Flags following --container will apply + to the specified container. + + Flags that are not container-specific must be specified before + --container. + + --description=DESCRIPTION + Provides an optional, human-readable description of the service. + + --gpu-type=GPU_TYPE + The GPU type to use. + + --[no-]gpu-zonal-redundancy + Set GPU zonal redundancy. Use --gpu-zonal-redundancy to enable and + --no-gpu-zonal-redundancy to disable. + + --instances=INSTANCES + The number of instances to run for this WorkerPool. Flag value should + be a positive integer to configure manual scaling with the given + integer as a fixed instance count. + + --no-promote + True to avoid assign instances to the worker revision being deployed. + Setting this flag assigns any instances assigned to the LATEST revision + to the specific revision bound to LATEST before the deployment. The + effect is that the revision being deployed will not receive instance + split. + + After a deployment with this flag the LATEST revision will not receive + instances on future deployments. To restore assigning instances to the + LATEST revision by default, run the gcloud run worker-pools + update-instance-split command with --to-latest. + + --remove-containers=[CONTAINER,...] + List of containers to remove. + + --revision-suffix=REVISION_SUFFIX + Specify the suffix of the revision name. Revision names always start + with the service name automatically. For example, specifying + [--revision-suffix=v1] for a service named 'helloworld', would lead to + a revision named 'helloworld-v1'. Set empty string to clear the suffix + and resume server-assigned naming. + + --service-account=SERVICE_ACCOUNT + the email address of an IAM service account associated with the + revision of the service. The service account represents the identity of + the running revision, and determines what permissions the revision has. + + --vpc-egress=VPC_EGRESS + Specify which of the outbound traffic to send through Direct VPC egress + or the VPC connector for this resource. This resource must have Direct + VPC egress enabled or a VPC connector to set this flag. VPC_EGRESS must + be one of: + + all + (DEPRECATED) Sends all outbound traffic through Direct VPC egress + or the VPC connector. Provides the same functionality as + 'all-traffic'. Prefer to use 'all-traffic' instead. + all-traffic + Sends all outbound traffic through Direct VPC egress or the VPC + connector. + private-ranges-only + Default option. Sends outbound traffic to private IP addresses (RFC + 1918 and Private Google Access IPs) through Direct VPC egress or + the VPC connector. + + Traffic to other Cloud Run services might require additional + configuration. See + https://cloud.google.com/run/docs/securing/private-networking#send_requests_to_other_services_and_services + for more information. + + These flags modify the Cloud SQL instances this WorkerPool connects to. + You can specify a name of a Cloud SQL instance if it's in the same project + and region as your Cloud Run worker pool; otherwise specify + :: for the instance. + + At most one of these can be specified: + + --add-cloudsql-instances=[CLOUDSQL-INSTANCES,...] + Append the given values to the current Cloud SQL instances. + + --clear-cloudsql-instances + Empty the current Cloud SQL instances. + + --remove-cloudsql-instances=[CLOUDSQL-INSTANCES,...] + Remove the given values from the current Cloud SQL instances. + + --set-cloudsql-instances=[CLOUDSQL-INSTANCES,...] + Completely replace the current Cloud SQL instances with the given + values. + + --add-volume=[KEY=VALUE,...] + Adds a volume to the Cloud Run resource. To add more than one volume, + specify this flag multiple times. Volumes must have a type key. Volumes + must have a name key if mount-path is not specified. A name key is + optional if mount-path is specified.Only certain values are supported + for type. Depending on the provided type, other keys will be required. + The following types are supported with the specified additional keys: + + cloud-storage: A volume representing a Cloud Storage bucket. This + volume type is mounted using Cloud Storage FUSE. See + https://cloud.google.com/storage/docs/gcs-fuse for the details and + limitations of this filesystem. Additional keys: + ◆ bucket: (required) the name of the bucket to use as the source of + this volume + ◆ readonly: (optional) A boolean. If true, this volume will be + read-only from all mounts. + ◆ mount-options: (optional) A list of flags to pass to GCSFuse. Flags + should be specified without leading dashes and separated by + semicolons. + ◆ mount-path: (optional) The path at which the volume should be + mounted. The mount-path parameter is only supported for single + container services which do not make use of the --container flag. For + multi-container services, specify the mount-path parameter under the + --add-volume-mount flag. + + in-memory: An ephemeral volume that stores data in the instance's + memory. With this type of volume, data is not shared between instances + and all data will be lost when the instance it is on is terminated. + Additional keys: + ◆ mount-path: (optional) The path at which the volume should be + mounted. The mount-path parameter is only supported for single + container services which do not make use of the --container flag. For + multi-container services, specify the mount-path parameter under the + --add-volume-mount flag. + ◆ size-limit: (optional) A quantity representing the maximum amount + of memory allocated to this volume, such as "512Mi" or "3G". Data + stored in an in-memory volume consumes the memory allocation of the + container that wrote the data. If size-limit is not specified, the + maximum size will be half the total memory limit of all containers. + + nfs: Represents a volume backed by an NFS server. Additional keys: + ◆ location: (required) The location of the NFS Server, in the form + SERVER:/PATH + ◆ mount-path: (optional) The path at which the volume should be + mounted. The mount-path parameter is only supported for single + container services which do not make use of the --container flag. For + multi-container services, specify the mount-path parameter under the + --add-volume-mount flag. + ◆ readonly: (optional) A boolean. If true, this volume will be + read-only from all mounts. + + --clear-volumes + Remove all existing volumes from the Cloud Run resource, including + volumes mounted as secrets + + --remove-volume=[VOLUME,...] + Removes volumes from the Cloud Run resource. + + Container Flags + + The following flags apply to the container. + + --add-volume-mount=[volume=NAME,mount-path=MOUNT_PATH,...] + Adds a mount to the current container. Must contain the keys + volume=NAME and mount-path=/PATH where NAME is the name of a volume on + this resource and PATH is the path within the container's filesystem to + mount this volume. + + --args=[ARG,...] + Comma-separated arguments passed to the command run by the container + image. If not specified and no '--command' is provided, the container + image's default Cmd is used. Otherwise, if not specified, no arguments + are passed. To reset this field to its default, pass an empty string. + + --clear-volume-mounts + Remove all existing mounts from the current container. + + --command=[COMMAND,...] + Entrypoint for the container image. If not specified, the container + image's default Entrypoint is run. To reset this field to its default, + pass an empty string. + + --cpu=CPU + Set a CPU limit in Kubernetes cpu units. + + Cloud Run supports values fractional values below 1, 1, 2, 4, and 8. + Some CPU values requires a minimum Memory --memory value. + + --depends-on=[CONTAINER,...] + List of container dependencies to add to the current container. + + --gpu=GPU + Cloud Run supports values 0 or 1. 1 gpu also requires a minimum 4 --cpu + value and a minimum 16Gi --memory value. + + --image=IMAGE + Name of the container image to deploy (e.g. + us-docker.pkg.dev/cloudrun/container/hello:latest). + + --memory=MEMORY + Set a memory limit. Ex: 1024Mi, 4Gi. + + --remove-volume-mount=[MOUNT_PATH,...] + Removes the volume mounted at the specified path from the current + container. + + At most one of these can be specified: + + --clear-env-vars + Remove all environment variables. + + --env-vars-file=FILE_PATH + Path to a local YAML or ENV file with definitions for all environment + variables. All existing environment variables will be removed before + the new environment variables are added. Example YAML content: + + KEY_1: "value1" + KEY_2: "value 2" + + Example ENV content: + + KEY_1="value1" + KEY_2="value 2" + + --set-env-vars=[KEY=VALUE,...] + List of key-value pairs to set as environment variables. All existing + environment variables will be removed first. + + Or at least one of these can be specified: + + Only --update-env-vars and --remove-env-vars can be used together. If + both are specified, --remove-env-vars will be applied first. + + --remove-env-vars=[KEY,...] + List of environment variables to be removed. + + --update-env-vars=[KEY=VALUE,...] + List of key-value pairs to set as environment variables. + + Specify secrets to provide as environment variables. For example: + '--set-secrets=ENV=mysecret:latest,OTHER_ENV=othersecret:1' will create an + environment variable named ENV whose value is the latest version of secret + 'mysecret' and an environment variable OTHER_ENV whose value is version of + 1 of secret 'othersecret'. + + At most one of these can be specified: + + --clear-secrets + Remove all secrets. + + --set-secrets=[KEY=VALUE,...] + List of key-value pairs to set as secrets. All existing secrets will + be removed first. + + Or at least one of these can be specified: + + Only --update-secrets and --remove-secrets can be used together. If + both are specified, --remove-secrets will be applied first. + + --remove-secrets=[KEY,...] + List of secrets to be removed. + + --update-secrets=[KEY=VALUE,...] + List of key-value pairs to set as secrets. + + At most one of these can be specified: + + --binary-authorization=POLICY + Binary Authorization policy to check against. This must be set to + "default". + + --clear-binary-authorization + Remove any previously set Binary Authorization policy. + + At most one of these can be specified: + + --clear-encryption-key-shutdown-hours + Remove any previously set CMEK key shutdown hours setting. + + --encryption-key-shutdown-hours=ENCRYPTION_KEY_SHUTDOWN_HOURS + The number of hours to wait before an automatic shutdown server after + CMEK key revocation is detected. + + At most one of these can be specified: + + --clear-key + Remove any previously set CMEK key reference. + + --key=KEY + CMEK key reference to encrypt the container with. + + 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 run worker-pools update --clear-labels + + To remove all existing labels and create two new labels, foo and baz: + + $ gcloud run worker-pools 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. + + At most one of these can be specified: + + --labels=[KEY=VALUE,...] + List of label KEY=VALUE pairs to add. + + An alias to --update-labels. + + --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. + + At most one of these can be specified: + + --clear-network + Disconnect this Cloud Run worker from the VPC network it is connected + to. + + Or at least one of these can be specified: + + Direct VPC egress setting flags group. + + --network=NETWORK + The VPC network that the Cloud Run worker will be able to send + traffic to. If --subnet is also specified, subnet must be a + subnetwork of the network specified by this --network flag. To + clear existing VPC network settings, use --clear-network. + + --subnet=SUBNET + The VPC subnetwork that the Cloud Run worker will get IPs from. The + subnetwork must be /26 or larger. If --network is also specified, + subnet must be a subnetwork of the network specified by the + --network flag. If --network is not specified, network will be + looked up from this subnetwork. To clear existing VPC network + settings, use --clear-network. + + At most one of these can be specified: + + --clear-network-tags + Clears all existing network tags from the Cloud Run worker. + + --network-tags=[TAG,...] + Applies the given network tags (comma separated) to the Cloud Run + worker. To clear existing tags, use --clear-network-tags. + + At most one of these can be specified: + + --clear-post-key-revocation-action-type + Remove any previously set post CMEK key revocation action type. + + --post-key-revocation-action-type=POST_KEY_REVOCATION_ACTION_TYPE + Action type after CMEK key revocation. + POST_KEY_REVOCATION_ACTION_TYPE must be one of: + + prevent-new + No new instances will be started after CMEK key revocation. + shut-down + No new instances will be started and the existing instances will + be shut down after CMEK key revocation. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --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 run worker-pools update + + $ gcloud beta run worker-pools update + diff --git a/gcloud/run/worker-pools/update-instance-split b/gcloud/run/worker-pools/update-instance-split new file mode 100644 index 000000000..00ec37baf --- /dev/null +++ b/gcloud/run/worker-pools/update-instance-split @@ -0,0 +1,133 @@ +NAME + gcloud run worker-pools update-instance-split - adjust the instance + assignments for a Cloud Run worker-pool + +SYNOPSIS + gcloud run worker-pools update-instance-split + [[WORKER_POOL] --region=REGION] [--async] [--breakglass=JUSTIFICATION] + [--to-latest | --to-revisions=[REVISION-NAME=PERCENTAGE,...]] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Adjust the instance assignments for a Cloud Run worker-pool. + +EXAMPLES + To assign 10% of instances to revision my-worker-pool-s5sxn and 90% of + instances to revision my-worker-pool-cp9kw run: + + $ gcloud run worker-pools update-instance-split my-worker-pool \ + --to-revisions=my-worker-pool-s5sxn=10,my-worker-pool-cp9kw=90 + + To increase the instances to revision my-worker-pool-s5sxn to 20% and by + reducing the instances to revision my-worker-pool-cp9kw to 80% run: + + $ gcloud run worker-pools update-instance-split my-worker-pool \ + --to-revisions=my-worker-pool-s5sxn=20 + + To rollback to revision my-worker-pool-cp9kw run: + + $ gcloud run worker-pools update-instance-split my-worker-pool \ + --to-revisions=my-worker-pool-cp9kw=100 + + To assign 100% of instances to the current or future LATEST revision run: + + $ gcloud run worker-pools update-instance-split my-worker-pool \ + --to-latest + + You can also refer to the current or future LATEST revision in + --to-revisions by the string "LATEST". For example, to set 10% of instances + to always float to the latest revision: + + $ gcloud run worker-pools update-instance-split my-worker-pool \ + --to-revisions=LATEST=10 + +POSITIONAL ARGUMENTS + WorkerPool resource - WorkerPool to update instance split of. 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 WORKER_POOL on the command line with a fully + specified name; + ◆ specify the workerpool name from an interactive prompt with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + [WORKER_POOL] + ID of the WorkerPool or fully qualified identifier for the WorkerPool. + + To set the worker-pool attribute: + ◆ provide the argument WORKER_POOL on the command line; + ◆ specify the workerpool name from an interactive prompt. + + --region=REGION + The Cloud region for the WorkerPool. Overrides the default run/region + property value for this command invocation. + + To set the region attribute: + ◆ provide the argument WORKER_POOL on the command line with a fully + specified name; + ◆ specify the workerpool name from an interactive prompt with a fully + specified name; + ◆ provide the argument --region on the command line; + ◆ set the property run/region; + ◆ specify the region from an interactive prompt. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --breakglass=JUSTIFICATION + Justification to bypass Binary Authorization policy constraints and + allow the operation. See + https://cloud.google.com/binary-authorization/docs/using-breakglass for + more information. Next update or deploy command will automatically + clear existing breakglass justification. + + At most one of these can be specified: + + --to-latest + True to assign 100 percent of instances to the 'latest' revision of + this service. Note that when a new revision is created, it will + become the 'latest' and instances will be fully assigned to it unless + configured otherwise using --[no-]promote flag. Defaults to False. + Synonymous with '--to-revisions=LATEST=100'. + + --to-revisions=[REVISION-NAME=PERCENTAGE,...] + Comma separated list of instance assignments in the form + REVISION-NAME=PERCENTAGE. REVISION-NAME must be the name for a + revision for the worker as returned by 'gcloud run workers revisions + list --worker=WORKER' . PERCENTAGE must be an integer percentage + between 0 and 100 inclusive. Ex worker-nw9hs=10,worker-nw9hs=20 Up to + 100 percent of instances may be assigned. If the total of 100 percent + of instances is assigned, the Worker instance split is updated as + specified. If under 100 percent of instance split is assigned, the + Worker instance split is updated as specified for revisions with + assignments and instance split is scaled up or down proportionally as + needed for revision that are currently serving workload but that do + not have new assignments. For example assume revision-1 is serving 40 + percent of workload and revision-2 is serving 60 percent. If + revision-1 is assigned 45 percent of instances and no assignment is + made for revision-2, the worker is updated with revsion-1 assigned 45 + percent of instances and revision-2 scaled down to 55 percent. You + can use "LATEST" as a special revision name to always put the given + percentage of instance split on the latest ready revision. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --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 run worker-pools update-instance-split + + $ gcloud beta run worker-pools update-instance-split + diff --git a/gcloud/scc/sources/help b/gcloud/scc/sources/help index ab955e5b3..2162724ca 100644 --- a/gcloud/scc/sources/help +++ b/gcloud/scc/sources/help @@ -19,6 +19,9 @@ COMMANDS describe Describe a source given its display name or source id. + list + List Cloud Security Command Center sources. + NOTES These variants are also available: diff --git a/gcloud/scc/sources/list b/gcloud/scc/sources/list new file mode 100644 index 000000000..882e7feff --- /dev/null +++ b/gcloud/scc/sources/list @@ -0,0 +1,82 @@ +NAME + gcloud scc sources list - list Cloud Security Command Center sources + +SYNOPSIS + gcloud scc sources list [PARENT] [--filter=EXPRESSION] [--limit=LIMIT] + [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + List Cloud Security Command Center sources. + +EXAMPLES + List all sources under organization 123456: + + $ gcloud scc sources list organizations/123456 + + List all sources under folder 456: + + $ gcloud scc sources list folders/456 + + List all sources under project example-project: + + $ gcloud scc sources list projects/example-project + +POSITIONAL ARGUMENTS + Parent resource - parent organization, folder, or project in the Google + Cloud resource hierarchy to be used for the gcloud scc command. Specify + the argument as either [RESOURCE_TYPE/RESOURCE_ID] or [RESOURCE_ID], as + shown in the preceding examples. This represents a Cloud resource. + + [PARENT] + ID of the parent or fully qualified identifier for the parent. + + To set the parent attribute: + ◆ provide the argument parent on the command line; + ◆ Set the parent property in configuration using gcloud config set + scc/parent if it is not specified in command line. + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the securitycenter/v2 API. The full documentation for + this API can be found at: https://cloud.google.com/security-command-center + +NOTES + These variants are also available: + + $ gcloud alpha scc sources list + + $ gcloud beta scc sources list + diff --git a/gcloud/service-health/events/describe b/gcloud/service-health/events/describe new file mode 100644 index 000000000..a933b0f8b --- /dev/null +++ b/gcloud/service-health/events/describe @@ -0,0 +1,81 @@ +NAME + gcloud service-health events describe - get details of an event affecting a + project + +SYNOPSIS + gcloud service-health events describe (EVENT : --location=LOCATION) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Retrieves a resource containing information about an event. + + To get service health incident event, use location global. + +EXAMPLES + To get the details of event my-event in project my-project and location + global, run: + + $ gcloud service-health events describe my-event \ + --project=my-project --location=global + +POSITIONAL ARGUMENTS + Event resource - Unique name of the event in this scope including project + and location using the form + projects/{project_id}/locations/{location}/events/{event_id}. + + project_id - Project ID of the project that contains the event. + + location - The location to get the service health events from. Set this + field to global. + + event_id - Event ID to retrieve. 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 event 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. + + EVENT + ID of the event or fully qualified identifier for the event. + + To set the event attribute: + ▸ provide the argument event 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 to use when working with Service Health resources. + + If not specified, will use default servicehealth/location. + + To set the location attribute: + ▸ provide the argument event on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ set the property servicehealth/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 servicehealth/v1 API. The full documentation for this + API can be found at: https://cloud.google.com/service-health/ + +NOTES + These variants are also available: + + $ gcloud alpha service-health events describe + + $ gcloud beta service-health events describe + diff --git a/gcloud/service-health/events/help b/gcloud/service-health/events/help new file mode 100644 index 000000000..de1cfb172 --- /dev/null +++ b/gcloud/service-health/events/help @@ -0,0 +1,31 @@ +NAME + gcloud service-health events - represents events that may affect Google + Cloud products + +SYNOPSIS + gcloud service-health events COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Represents events that may affect Google Cloud products. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + describe + Get details of an event affecting a project. + + list + List events under a given project and location. + +NOTES + These variants are also available: + + $ gcloud alpha service-health events + + $ gcloud beta service-health events + diff --git a/gcloud/service-health/events/list b/gcloud/service-health/events/list new file mode 100644 index 000000000..9937d98fe --- /dev/null +++ b/gcloud/service-health/events/list @@ -0,0 +1,103 @@ +NAME + gcloud service-health events list - list events under a given project and + location + +SYNOPSIS + gcloud service-health events list [--location=LOCATION] [--view=VIEW] + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + List events under a given project and location. + + To retrieve service health incident events, use location global. + +EXAMPLES + To list all events in project my-project and location global, run: + + $ gcloud service-health events list --project=my-project \ + --location=global + +FLAGS + Location resource - Parent value using the form + projects/{project_id}/locations/{location}/events. + + project_id - ID of the project for which to list service health events. + location - The location to get the service health events from. Set this + field to global. 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 servicehealth/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 servicehealth/location. + + --view=VIEW + Event fields to include in response. VIEW must be one of: + + event-view-basic + Includes all fields except updates. This view is the default for + ListEvents API. + event-view-full + Includes all event fields. + +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 servicehealth/v1 API. The full documentation for this + API can be found at: https://cloud.google.com/service-health/ + +NOTES + These variants are also available: + + $ gcloud alpha service-health events list + + $ gcloud beta service-health events list + diff --git a/gcloud/service-health/help b/gcloud/service-health/help new file mode 100644 index 000000000..29233becd --- /dev/null +++ b/gcloud/service-health/help @@ -0,0 +1,35 @@ +NAME + gcloud service-health - request events that are relevant to your project or + organization + +SYNOPSIS + gcloud service-health GROUP [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Request events that are relevant to your project or organization. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +GROUPS + GROUP is one of the following: + + events + Represents events that may affect Google Cloud products. + + organization-events + Represents events that may affect products used across the + organization. + + organization-impacts + Represents impact to assets at organizational level. + +NOTES + These variants are also available: + + $ gcloud alpha service-health + + $ gcloud beta service-health + diff --git a/gcloud/service-health/organization-events/describe b/gcloud/service-health/organization-events/describe new file mode 100644 index 000000000..38ccd7ace --- /dev/null +++ b/gcloud/service-health/organization-events/describe @@ -0,0 +1,83 @@ +NAME + gcloud service-health organization-events describe - get details of an + event affecting an organization + +SYNOPSIS + gcloud service-health organization-events describe + (ORGANIZATION_EVENT : --location=LOCATION --organization=ORGANIZATION) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Retrieves a resource containing information about an event affecting an + organization. + + To get service health incident event, use location global. + +EXAMPLES + To get the details of organization event my-event in location global for + organization 123456789, run: + + $ gcloud service-health organization-events describe my-event \ + --organization=123456789 --location=global + +POSITIONAL ARGUMENTS + OrganizationEvent resource - Unique name of the event in this scope + including organization and event ID using the form + organizations/{organization_id}/locations/locations/global/organizationEvents/{event_id}. + + organization_id - ID (number) of the organization that contains the event. + To get your organization_id, see Getting your organization resource ID + (https://cloud.google.com/resource-manager/docs/creating-managing-organization#retrieving_your_organization_id).
+ event_id - Organization event ID to retrieve. The arguments in this group + can be used to specify the attributes of this resource. + + This must be specified. + + ORGANIZATION_EVENT + ID of the organizationEvent or fully qualified identifier for the + organizationEvent. + + To set the organization_event attribute: + ▸ provide the argument organization_event 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 to use when working with Service Health resources. + + If not specified, will use default servicehealth/location. + + To set the location attribute: + ▸ provide the argument organization_event on the command line with + a fully specified name; + ▸ provide the argument --location on the command line; + ▸ set the property servicehealth/location. + + --organization=ORGANIZATION + The organization id of the organizationEvent resource. + + To set the organization attribute: + ▸ provide the argument organization_event on the command line with + a fully specified name; + ▸ provide the argument --organization 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 servicehealth/v1 API. The full documentation for this + API can be found at: https://cloud.google.com/service-health/ + +NOTES + These variants are also available: + + $ gcloud alpha service-health organization-events describe + + $ gcloud beta service-health organization-events describe + diff --git a/gcloud/service-health/organization-events/help b/gcloud/service-health/organization-events/help new file mode 100644 index 000000000..706871b10 --- /dev/null +++ b/gcloud/service-health/organization-events/help @@ -0,0 +1,31 @@ +NAME + gcloud service-health organization-events - represents events that may + affect products used across the organization + +SYNOPSIS + gcloud service-health organization-events COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Represents events that may affect products used across the organization. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + describe + Get details of an event affecting an organization. + + list + List events under a given organization and location. + +NOTES + These variants are also available: + + $ gcloud alpha service-health organization-events + + $ gcloud beta service-health organization-events + diff --git a/gcloud/service-health/organization-events/list b/gcloud/service-health/organization-events/list new file mode 100644 index 000000000..c47e8225b --- /dev/null +++ b/gcloud/service-health/organization-events/list @@ -0,0 +1,110 @@ +NAME + gcloud service-health organization-events list - list events under a given + organization and location + +SYNOPSIS + gcloud service-health organization-events list [--view=VIEW] + [--location=LOCATION --organization=ORGANIZATION] [--filter=EXPRESSION] + [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Lists organization events under a given organization and location. + + To retrieve service health incident events, use location global. + +EXAMPLES + To list all organization events in location global for organization + 123456789, run: + + $ gcloud service-health organization-events list \ + --organization=123456789 --location=global + +FLAGS + --view=VIEW + OrganizationEvent fields to include in response. VIEW must be one of: + + organization-event-view-basic + Includes all organization event fields except updates. This view is + the default for ListOrganizationEvents API. + organization-event-view-full + Includes all organization event fields. + + Location resource - Parent value using the form + organizations/{organization_id}/locations/{location}/organizationEvents. + + organization_id - ID (number) of the organization that contains the event. + To get your organization_id, see Getting your organization resource ID + (https://cloud.google.com/resource-manager/docs/creating-managing-organization#retrieving_your_organization_id).
+ location - The location to get the organization events from. Set this + field to global. The arguments in this group can be used to specify the + attributes of this resource. + + --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 servicehealth/location. + + --organization=ORGANIZATION + The organization id of the location resource. + + To set the organization attribute: + ◆ provide the argument --location on the command line with a fully + specified name; + ◆ set the property servicehealth/location with a fully specified + name; + ◆ provide the argument --organization 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 servicehealth/v1 API. The full documentation for this + API can be found at: https://cloud.google.com/service-health/ + +NOTES + These variants are also available: + + $ gcloud alpha service-health organization-events list + + $ gcloud beta service-health organization-events list + diff --git a/gcloud/service-health/organization-impacts/describe b/gcloud/service-health/organization-impacts/describe new file mode 100644 index 000000000..5379b22ea --- /dev/null +++ b/gcloud/service-health/organization-impacts/describe @@ -0,0 +1,83 @@ +NAME + gcloud service-health organization-impacts describe - get details of an + asset impact by an event under an organization + +SYNOPSIS + gcloud service-health organization-impacts describe + (ORGANIZATION_IMPACT : --location=LOCATION --organization=ORGANIZATION) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Retrieves a resource containing information about impact to an asset under + an organization affected by a service health event. + + To retrieve impact for service health incident events, use location global. + +EXAMPLES + To get the details of organization impact my-impact in location global for + organization 123456789, run: + + $ gcloud service-health organization-impacts describe my-impact \ + --organization=123456789 --location=global + +POSITIONAL ARGUMENTS + OrganizationImpact resource - Name of the resource using the form + organizations/{organization_id}/locations/global/organizationImpacts/{organization_impact_id}. + + organization_id - ID (number) of the organization that contains the event. + To get your organization_id, see Getting your organization resource ID + (https://cloud.google.com/resource-manager/docs/creating-managing-organization#retrieving_your_organization_id).
+ organization_impact_id - ID of the OrganizationImpact resource. The + arguments in this group can be used to specify the attributes of this + resource. + + This must be specified. + + ORGANIZATION_IMPACT + ID of the organizationImpact or fully qualified identifier for the + organizationImpact. + + To set the organization_impact attribute: + ▸ provide the argument organization_impact 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 to use when working with Service Health resources. + + If not specified, will use default servicehealth/location. + + To set the location attribute: + ▸ provide the argument organization_impact on the command line with + a fully specified name; + ▸ provide the argument --location on the command line; + ▸ set the property servicehealth/location. + + --organization=ORGANIZATION + The organization id of the organizationImpact resource. + + To set the organization attribute: + ▸ provide the argument organization_impact on the command line with + a fully specified name; + ▸ provide the argument --organization 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 servicehealth/v1 API. The full documentation for this + API can be found at: https://cloud.google.com/service-health/ + +NOTES + These variants are also available: + + $ gcloud alpha service-health organization-impacts describe + + $ gcloud beta service-health organization-impacts describe + diff --git a/gcloud/service-health/organization-impacts/help b/gcloud/service-health/organization-impacts/help new file mode 100644 index 000000000..8148b87d9 --- /dev/null +++ b/gcloud/service-health/organization-impacts/help @@ -0,0 +1,31 @@ +NAME + gcloud service-health organization-impacts - represents impact to assets at + organizational level + +SYNOPSIS + gcloud service-health organization-impacts COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Represents impact to assets at organizational level. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + describe + Get details of an asset impact by an event under an organization. + + list + List assets impacted by events under an organization. + +NOTES + These variants are also available: + + $ gcloud alpha service-health organization-impacts + + $ gcloud beta service-health organization-impacts + diff --git a/gcloud/service-health/organization-impacts/list b/gcloud/service-health/organization-impacts/list new file mode 100644 index 000000000..4f6f88559 --- /dev/null +++ b/gcloud/service-health/organization-impacts/list @@ -0,0 +1,104 @@ +NAME + gcloud service-health organization-impacts list - list assets impacted by + events under an organization + +SYNOPSIS + gcloud service-health organization-impacts list + [--location=LOCATION --organization=ORGANIZATION] [--filter=EXPRESSION] + [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Lists assets impacted by organization events under a given organization and + location. + + To retrieve projects impacted by service health incident events, use + location global. + +EXAMPLES + To list all organization impacts in location global for organization + 123456789, run: + + $ gcloud service-health organization-impacts list \ + --organization=123456789 --location=global + +FLAGS + Location resource - Parent value using the form + organizations/{organization_id}/locations/{location}/organizationImpacts. + + location - The location to get organization impacts from. Set this field + to global.
organization_id - ID (number) of the organization that + contains the event. To get your organization_id, see Getting your + organization resource ID + (https://cloud.google.com/resource-manager/docs/creating-managing-organization#retrieving_your_organization_id). + The arguments in this group can be used to specify the attributes of this + resource. + + --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 servicehealth/location. + + --organization=ORGANIZATION + The organization id of the location resource. + + To set the organization attribute: + ◆ provide the argument --location on the command line with a fully + specified name; + ◆ set the property servicehealth/location with a fully specified + name; + ◆ provide the argument --organization 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 servicehealth/v1 API. The full documentation for this + API can be found at: https://cloud.google.com/service-health/ + +NOTES + These variants are also available: + + $ gcloud alpha service-health organization-impacts list + + $ gcloud beta service-health organization-impacts list + diff --git a/gcloud/services/api-keys/update b/gcloud/services/api-keys/update index 1efbb2186..e8480aa98 100644 --- a/gcloud/services/api-keys/update +++ b/gcloud/services/api-keys/update @@ -19,49 +19,54 @@ EXAMPLES To remove all restrictions of the key: $ gcloud services api-keys update \ - projects/myproject/keys/my-key-id --clear-restrictions + projects/myproject/locations/global/keys/my-key-id \ + --clear-restrictions To update display name and set allowed ips as server key restrictions: $ gcloud services api-keys update \ - projects/myproject/keys/my-key-id --display-name="test name" \ + projects/myproject/locations/global/keys/my-key-id \ + --display-name="test name" \ --allowed-ips=2620:15c:2c4:203:2776:1f90:6b3b:217,104.133.8.78 To update annotations: $ gcloud services api-keys update \ - projects/myproject/keys/my-key-id --annotations=foo=bar,abc=def + projects/myproject/locations/global/keys/my-key-id \ + --annotations=foo=bar,abc=def To update key's allowed referrers restriction: $ gcloud services api-keys update \ - projects/myproject/keys/my-key-id \ + projects/myproject/locations/global/keys/my-key-id \ --allowed-referrers="https://www.example.com/*,http://sub.exampl\ e.com/*" To update key's allowed ios app bundle ids: $ gcloud services api-keys update \ - projects/myproject/keys/my-key-id --allowed-bundle-ids=my.app + projects/myproject/locations/global/keys/my-key-id \ + --allowed-bundle-ids=my.app To update key's allowed android application: $ gcloud services api-keys update \ - projects/myproject/keys/my-key-id \ + projects/myproject/locations/global/keys/my-key-id \ --allowed-application=sha1_fingerprint=foo1,package_name=bar1 \ --allowed-application=sha1_fingerprint=foo2,package_name=bar2 To update keys' allowed api target with multiple services: $ gcloud services api-keys update \ - projects/myproject/keys/my-key-id \ + projects/myproject/locations/global/keys/my-key-id \ --api-target=service=bar.service.com \ --api-target=service=foo.service.com To update keys' allowed api target with service and method: $ gcloud services api-keys update \ - projects/myproject/keys/my-key-id --flags-file=my-flags.yaml + projects/myproject/locations/global/keys/my-key-id \ + --flags-file=my-flags.yaml The content of 'my-flags.yaml' is as following: diff --git a/gcloud/spanner/databases/update b/gcloud/spanner/databases/update index 98a67e3f6..954750558 100644 --- a/gcloud/spanner/databases/update +++ b/gcloud/spanner/databases/update @@ -3,8 +3,8 @@ NAME SYNOPSIS gcloud spanner databases update (DATABASE : --instance=INSTANCE) [--async] - [--[no-]enable-drop-protection | --kms-keys=KMS_KEY,[KMS_KEY,...]] - [GCLOUD_WIDE_FLAG ...] + [--clear-kms-keys | --[no-]enable-drop-protection + | --kms-keys=KMS_KEY,[KMS_KEY,...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION Update a Cloud Spanner database. @@ -27,6 +27,11 @@ EXAMPLES $ gcloud spanner databases update my-database --kms-keys="KEY1,KEY2" + To remove all KMS key references and revert a Cloud Spanner database + 'my-database' to Google-managed encryption, run: + + $ gcloud spanner databases update my-database --clear-kms-keys + POSITIONAL ARGUMENTS Database resource - The Cloud Spanner database to update. The arguments in this group can be used to specify the attributes of this resource. (NOTE) @@ -66,6 +71,10 @@ FLAGS At most one of these can be specified: + --clear-kms-keys + Removes all KMS key references and reverts the database to + Google-managed encryption. + --[no-]enable-drop-protection Enable database deletion protection on this database. Use --enable-drop-protection to enable and --no-enable-drop-protection to diff --git a/gcloud/sql/instances/create b/gcloud/sql/instances/create index d78170477..84cc41ce9 100644 --- a/gcloud/sql/instances/create +++ b/gcloud/sql/instances/create @@ -52,6 +52,7 @@ SYNOPSIS [--password-policy-min-length=PASSWORD_POLICY_MIN_LENGTH] [--password-policy-password-change-interval=PASSWORD_POLICY_PASSWORD_CHANGE_INTERVAL] [--password-policy-reuse-interval=PASSWORD_POLICY_REUSE_INTERVAL] + [--performance-capture-config=KEY=VALUE,[KEY=VALUE,...]] [--psc-auto-connections=[network=NETWORK],[project=PROJECT]] [--[no-]recreate-replicas-on-primary-crash] [--replica-type=REPLICA_TYPE] [--replication=REPLICATION] @@ -501,6 +502,25 @@ FLAGS Number of previous passwords that cannot be reused. The valid range is 0 to 100. + --performance-capture-config=KEY=VALUE,[KEY=VALUE,...] + A comma-separated list of performance capture settings to add to the + MySQL instance. The input should be in a format of key=value. Available + case-sensitive keys are: enabled (boolean), probing-interval-seconds + (integer), probe-threshold (integer), running-threads-threshold + (integer), seconds-behind-source-threshold (integer), + transaction-duration-threshold (integer), + cpu-utilization-threshold-percent (integer), + memory-usage-threshold-percent (integer), + transaction-lock-wait-threshold-count (integer), + semaphore-wait-threshold-count (integer), + history-list-length-threshold-count (integer), + transaction-kill-threshold-seconds (integer), transaction-kill-type + (string), transaction-kill-excluded-user-hosts (string, + semicolon-separated list) Example: --performance-capture-config + enabled=true,probe-threshold=5, cpu-utilization-threshold-percent=80, + transaction-kill-excluded-user-hosts=user1@host1;user2@%, + transaction-kill-type=READ_ONLY_TRANSACTIONS + --psc-auto-connections=[network=NETWORK],[project=PROJECT] A comma-separated list of networks or network-project pairs. Each project is represented by a project number (numeric) or by a project ID diff --git a/gcloud/sql/instances/patch b/gcloud/sql/instances/patch index 981c7b9af..4654bd93e 100644 --- a/gcloud/sql/instances/patch +++ b/gcloud/sql/instances/patch @@ -51,6 +51,7 @@ SYNOPSIS [--password-policy-min-length=PASSWORD_POLICY_MIN_LENGTH] [--password-policy-password-change-interval=PASSWORD_POLICY_PASSWORD_CHANGE_INTERVAL] [--password-policy-reuse-interval=PASSWORD_POLICY_REUSE_INTERVAL] + [--performance-capture-config=KEY=VALUE,[KEY=VALUE,...]] [--pricing-plan=PRICING_PLAN, -p PRICING_PLAN] [--reconcile-psa-networking] [--[no-]recreate-replicas-on-primary-crash] @@ -479,6 +480,25 @@ FLAGS Number of previous passwords that cannot be reused. The valid range is 0 to 100. + --performance-capture-config=KEY=VALUE,[KEY=VALUE,...] + A comma-separated list of performance capture settings to add to the + MySQL instance. The input should be in a format of key=value. Available + case-sensitive keys are: enabled (boolean), probing-interval-seconds + (integer), probe-threshold (integer), running-threads-threshold + (integer), seconds-behind-source-threshold (integer), + transaction-duration-threshold (integer), + cpu-utilization-threshold-percent (integer), + memory-usage-threshold-percent (integer), + transaction-lock-wait-threshold-count (integer), + semaphore-wait-threshold-count (integer), + history-list-length-threshold-count (integer), + transaction-kill-threshold-seconds (integer), transaction-kill-type + (string), transaction-kill-excluded-user-hosts (string, + semicolon-separated list) Example: --performance-capture-config + enabled=true,probe-threshold=5, cpu-utilization-threshold-percent=80, + transaction-kill-excluded-user-hosts=user1@host1;user2@%, + transaction-kill-type=READ_ONLY_TRANSACTIONS + --pricing-plan=PRICING_PLAN, -p PRICING_PLAN First Generation instances only. The pricing plan for this instance. PRICING_PLAN must be one of: PER_USE, PACKAGE. diff --git a/gcloud/sql/instances/pre-check-major-version-upgrade b/gcloud/sql/instances/pre-check-major-version-upgrade index d5617ab97..3b3bf4a30 100644 --- a/gcloud/sql/instances/pre-check-major-version-upgrade +++ b/gcloud/sql/instances/pre-check-major-version-upgrade @@ -12,11 +12,18 @@ DESCRIPTION for a major version upgrade of a Cloud SQL instance. EXAMPLES - To perform pre-checks before upgrading to a target version: + To perform pre-checks before upgrading a PostgreSQL instance to a target + version (supported in both GA and Beta): $ gcloud sql instances pre-check-major-version-upgrade \ test-instance --target-database-version=POSTGRES_15 + To perform pre-checks before upgrading a MySQL instance to a target version + (supported in Beta only): + + $ gcloud sql instances pre-check-major-version-upgrade \ + test-instance --target-database-version=MYSQL_8_0 + POSITIONAL ARGUMENTS INSTANCE Cloud SQL instance ID. @@ -37,3 +44,9 @@ GCLOUD WIDE FLAGS --trace-token, --user-output-enabled, --verbosity. Run $ gcloud help for details. + +NOTES + This variant is also available: + + $ gcloud beta sql instances pre-check-major-version-upgrade + diff --git a/gcloud/storage/batch-operations/jobs/create b/gcloud/storage/batch-operations/jobs/create index 3161901b0..797b96d5a 100644 --- a/gcloud/storage/batch-operations/jobs/create +++ b/gcloud/storage/batch-operations/jobs/create @@ -3,9 +3,9 @@ NAME job SYNOPSIS - gcloud storage batch-operations jobs create BATCH_JOB --bucket=BUCKET - (--included-object-prefixes=[PREFIXES,...] - | --manifest-location=MANIFEST_LOCATION) + gcloud storage batch-operations jobs create BATCH_JOB + (--bucket=BUCKET (--included-object-prefixes=[PREFIXES,...] + | --manifest-location=MANIFEST_LOCATION)) (--put-metadata=KEY=VALUE,[KEY=VALUE,...] | --rewrite-object=KEY=VALUE,[KEY=VALUE,...] | --clear-all-object-custom-contexts @@ -95,26 +95,33 @@ POSITIONAL ARGUMENTS ▸ provide the argument batch_job on the command line. REQUIRED FLAGS - --bucket=BUCKET - Bucket containing the objects that the batch job will operate on. + This must be specified. - Source specifying objects to perform batch operations on. Must be one of - --manifest-location=``MANIFEST_LOCATION or - --included-object-prefixes=``COMMA_SEPARATED_PREFIXES + Use bucket(s) as the source. - Exactly one of these must be specified: + --bucket=BUCKET + Bucket containing the objects that the batch job will operate on. - --included-object-prefixes=[PREFIXES,...] - A comma-separated list of object prefixes to describe the objects - being transformed. An empty string means all objects in the bucket. + This flag argument must be specified if any of the other arguments in + this group are specified. - --manifest-location=MANIFEST_LOCATION - An absolute path to the manifest source file in a Google Cloud - Storage bucket. The file must be a CSV file where each row specifies - the object details i.e. ProjectId, BucketId, and Name. Generation may - optionally be specified. When generation is not specified, the live - object is acted upon. Format: - --manifest-location=gs://bucket_name/path/manifest_name.csv + Source specifying objects to perform batch operations on. Must be one of + --manifest-location=``MANIFEST_LOCATION or + --included-object-prefixes=``COMMA_SEPARATED_PREFIXES + + Exactly one of these must be specified: + + --included-object-prefixes=[PREFIXES,...] + A comma-separated list of object prefixes to describe the objects + being transformed. An empty string means all objects in the bucket. + + --manifest-location=MANIFEST_LOCATION + An absolute path to the manifest source file in a Google Cloud + Storage bucket. The file must be a CSV file where each row + specifies the object details i.e. ProjectId, BucketId, and Name. + Generation may optionally be specified. When generation is not + specified, the live object is acted upon. Format: + --manifest-location=gs://bucket_name/path/manifest_name.csv Transformation to be performed on the objects. diff --git a/gcloud/storage/objects/compose b/gcloud/storage/objects/compose index 104689e77..cb058293e 100644 --- a/gcloud/storage/objects/compose +++ b/gcloud/storage/objects/compose @@ -4,7 +4,7 @@ NAME SYNOPSIS gcloud storage objects compose SOURCE [SOURCE ...] DESTINATION - [--additional-headers=HEADER=VALUE] + [--additional-headers=HEADER=VALUE] [--delete-source-objects] [--clear-custom-contexts | --custom-contexts=[CUSTOM_CONTEXTS_KEYS_AND_VALUES,...] | --custom-contexts-file=CUSTOM_CONTEXTS_FILE] @@ -37,6 +37,13 @@ EXAMPLES gs://bucket/b.txt gs://bucket/target.txt \ --custom-contexts=key1=value1,key2=value2 + The following command creates a new object target.txt by concatenating + a.txt and b.txt, and deletes the source objects after a successful + composition: + + $ gcloud storage objects compose gs://bucket/a.txt \ + gs://bucket/b.txt gs://bucket/target.txt --delete-source-objects + POSITIONAL ARGUMENTS SOURCE [SOURCE ...] The list of source objects that will be concatenated into a single @@ -52,6 +59,11 @@ FLAGS Overrides the default storage/additional_headers property value for this command invocation. + --delete-source-objects + If set, the source objects will be deleted after a successful + composition. Note that this deletion bypasses the soft delete policy if + configured on the bucket. + OBJECT CONTEXTS FLAGS Group that allow users to handle object contexts. diff --git a/gcloud/vector-search/collections/create b/gcloud/vector-search/collections/create index 4349a73f7..05172af67 100644 --- a/gcloud/vector-search/collections/create +++ b/gcloud/vector-search/collections/create @@ -4,9 +4,10 @@ NAME SYNOPSIS gcloud vector-search collections create (COLLECTION : --location=LOCATION) [--async] [--data-schema=DATA_SCHEMA] [--description=DESCRIPTION] - [--display-name=DISPLAY_NAME] [--labels=[LABELS,...]] - [--request-id=REQUEST_ID] [--vector-schema=[VECTOR_SCHEMA,...]] - [GCLOUD_WIDE_FLAG ...] + [--display-name=DISPLAY_NAME] + [--encryption-spec-crypto-key-name=ENCRYPTION_SPEC_CRYPTO_KEY_NAME] + [--labels=[LABELS,...]] [--request-id=REQUEST_ID] + [--vector-schema=[VECTOR_SCHEMA,...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION Create a collection. @@ -32,6 +33,18 @@ EXAMPLES 3}},"genre_embedding":{"denseVector":{"dimensions":4}},"sparse_embed\ ding":{"sparseVector":{}}}' --project=my-project + To create a CMEK-encrypted collection my-collection in project my-project + and location us-central1 to store dense embedding vectors with 100 + dimensions, run: + + $ gcloud vector-search collections create my-collection \ + --location=us-central1 --display-name='My Collection' \ + --vector-schema='{"my-embedding-field": {"denseVector": + {"dimensions": 100}}}' \ + --encryption-spec-crypto-key-name='projects/my-project/locations\ + /us-central1/keyRings/my-key-ring/cryptoKeys/my-key' \ + --project=my-project + POSITIONAL ARGUMENTS Collection resource - Identifier. name of resource The arguments in this group can be used to specify the attributes of this resource. (NOTE) Some @@ -80,6 +93,16 @@ FLAGS --display-name=DISPLAY_NAME User-specified display name of the collection + Represents a customer-managed encryption key specification that can be + applied to a Vector Search collection. + + --encryption-spec-crypto-key-name=ENCRYPTION_SPEC_CRYPTO_KEY_NAME + Resource name of the Cloud KMS key used to protect the resource. + + The Cloud KMS key must be in the same region as the resource. It must + have the format + projects/{project}/locations/{location}/keyRings/{key_ring}/cryptoKeys/{crypto_key}. + --labels=[LABELS,...] Labels as key value pairs. diff --git a/gcloud/workbench/instances/create b/gcloud/workbench/instances/create index 5bf38fe97..20d1c999a 100644 --- a/gcloud/workbench/instances/create +++ b/gcloud/workbench/instances/create @@ -203,9 +203,12 @@ FLAGS specified, this defaults to 100. --boot-disk-type=BOOT_DISK_TYPE - Type of boot disk attached to this instance, defaults to standard - persistent disk (PD_STANDARD). BOOT_DISK_TYPE must be one of: - PD_STANDARD, PD_SSD, PD_BALANCED, PD_EXTREME. + Type of boot disk attached to this instance. Defaults to standard + persistent disk (PD_STANDARD) on machine types that support Persistent + Disk, and to HYPERDISK_BALANCED on Hyperdisk-only machine series (e.g. + N4, C4, C4A, M4). BOOT_DISK_TYPE must be one of: PD_STANDARD, PD_SSD, + PD_BALANCED, PD_EXTREME, HYPERDISK_BALANCED, + HYPERDISK_BALANCED_HIGH_AVAILABILITY, HYPERDISK_ML. Key resource - The Cloud KMS (Key Management Service) cryptokey that will be used to protect the boot_disk. The 'Compute Engine Service Agent' @@ -303,9 +306,13 @@ FLAGS specified, this defaults to 100. --data-disk-type=DATA_DISK_TYPE - Type of data disk attached to this instance, defaults to standard - persistent disk (PD_STANDARD). DATA_DISK_TYPE must be one of: - PD_STANDARD, PD_SSD, PD_BALANCED, PD_EXTREME. + Type of data disk attached to this instance. Defaults to standard + persistent disk (PD_STANDARD) on machine types that support Persistent + Disk, and to HYPERDISK_BALANCED on Hyperdisk-only machine series (e.g. + N4, C4, C4A, M4). DATA_DISK_TYPE must be one of: PD_STANDARD, PD_SSD, + PD_BALANCED, PD_EXTREME, HYPERDISK_BALANCED, + HYPERDISK_BALANCED_HIGH_AVAILABILITY, HYPERDISK_ML, HYPERDISK_EXTREME, + HYPERDISK_THROUGHPUT. Key resource - The Cloud KMS (Key Management Service) cryptokey that will be used to protect the data_disk. The 'Compute Engine Service Agent' diff --git a/gcloud/workbench/instances/update b/gcloud/workbench/instances/update index c288baf62..88774936e 100644 --- a/gcloud/workbench/instances/update +++ b/gcloud/workbench/instances/update @@ -4,7 +4,8 @@ NAME SYNOPSIS gcloud workbench instances update (INSTANCE : --location=LOCATION) [--async] [--labels=[KEY=VALUE,...]] - [--machine-type=MACHINE_TYPE --metadata=[KEY=VALUE,...] + [--data-disk-resource-policies=[RESOURCE_POLICIES,...] + --machine-type=MACHINE_TYPE --metadata=[KEY=VALUE,...] --tags=[TAGS,...] --accelerator-core-count=ACCELERATOR_CORE_COUNT --accelerator-type=ACCELERATOR_TYPE [--container-repository=CONTAINER_REPOSITORY @@ -75,6 +76,12 @@ FLAGS Gce Setup for the instance + Data disk configurations. + + --data-disk-resource-policies=[RESOURCE_POLICIES,...] + Resource policies to apply to the data disk. Format: + projects/{project}/regions/{region}/resourcePolicies/{policy}. + --machine-type=MACHINE_TYPE The Compute Engine machine type (https://cloud.google.com/sdk/gcloud/reference/compute/machine-types) diff --git a/gcloud/workload-identity/help b/gcloud/workload-identity/help new file mode 100644 index 000000000..86182cd53 --- /dev/null +++ b/gcloud/workload-identity/help @@ -0,0 +1,27 @@ +NAME + gcloud workload-identity - manage Workload Identity + +SYNOPSIS + gcloud workload-identity GROUP [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Manage Workload Identity. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +GROUPS + GROUP is one of the following: + + service-agents + Manage Service Agents for Workload Identity. + +NOTES + These variants are also available: + + $ gcloud alpha workload-identity + + $ gcloud beta workload-identity + diff --git a/gcloud/workload-identity/service-agents/generate b/gcloud/workload-identity/service-agents/generate new file mode 100644 index 000000000..f9122672d --- /dev/null +++ b/gcloud/workload-identity/service-agents/generate @@ -0,0 +1,74 @@ +NAME + gcloud workload-identity service-agents generate - generate service agents + for a service producer + +SYNOPSIS + gcloud workload-identity service-agents generate --service=SERVICE + (--folder=FOLDER | --organization=ORGANIZATION | --project=PROJECT) + [--location=LOCATION; default="global"] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + It can be generated in a project, folder, or organization and location. + + gcloud workload-identity service-agents generate generates service agents + for a given service producer in a specific project, folder, or organization + and location. + +EXAMPLES + To generate service agents for bigquery.googleapis.com in the global + location for the project 123456, run: + + $ gcloud workload-identity service-agents generate \ + --service="bigquery.googleapis.com" --location="global" \ + --project="123456" + + To generate service agents for bigquery.googleapis.com in the global + location for the folder 123456, run: + + $ gcloud workload-identity service-agents generate \ + --service="bigquery.googleapis.com" --location="global" \ + --folder="123456" + + To generate service agents for bigquery.googleapis.com in the global + location for the organization 123456, run: + + $ gcloud workload-identity service-agents generate \ + --service="bigquery.googleapis.com" --location="global" \ + --organization="123456" + +REQUIRED FLAGS + --service=SERVICE + The service producer to generate service agents for (e.g. + bigquery.googleapis.com). + + Exactly one of these must be specified: + + --folder=FOLDER + The folder number to generate service agents for. + + --organization=ORGANIZATION + The organization number to generate service agents for. + + --project=PROJECT + The project number to generate service agents for. + +OPTIONAL FLAGS + --location=LOCATION; default="global" + The location for which to generate the service agents. Defaults to + global. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --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 workload-identity service-agents generate + + $ gcloud beta workload-identity service-agents generate + diff --git a/gcloud/workload-identity/service-agents/help b/gcloud/workload-identity/service-agents/help new file mode 100644 index 000000000..155dd061d --- /dev/null +++ b/gcloud/workload-identity/service-agents/help @@ -0,0 +1,28 @@ +NAME + gcloud workload-identity service-agents - manage Service Agents for + Workload Identity + +SYNOPSIS + gcloud workload-identity service-agents COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Manage Service Agents for Workload Identity. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + generate + Generate service agents for a service producer. + +NOTES + These variants are also available: + + $ gcloud alpha workload-identity service-agents + + $ gcloud beta workload-identity service-agents + diff --git a/gcloud/workstations/clusters/create b/gcloud/workstations/clusters/create index de15e6d98..21ffedec3 100644 --- a/gcloud/workstations/clusters/create +++ b/gcloud/workstations/clusters/create @@ -3,7 +3,7 @@ NAME SYNOPSIS gcloud workstations clusters create (CLUSTER : --region=REGION) [--async] - [--domain=DOMAIN] [--enable-private-endpoint] + [--domain=DOMAIN] [--enable-http2] [--enable-private-endpoint] [--labels=[KEY=VALUE,...]] [--network=NETWORK] [--subnetwork=SUBNETWORK] [--tags=[KEY=VALUE,...]] [GCLOUD_WIDE_FLAG ...] @@ -63,6 +63,9 @@ FLAGS --domain=DOMAIN Domain used by Workstations for HTTP ingress. + --enable-http2 + Whether HTTP/2 is enabled for the workstation cluster. + --enable-private-endpoint Default is false. If specified, the cluster will be assigned an internal IP address to the Cluster Gateway. This isolates the cluster's diff --git a/gcloud/workstations/clusters/help b/gcloud/workstations/clusters/help index 49ca14d60..aabf87548 100644 --- a/gcloud/workstations/clusters/help +++ b/gcloud/workstations/clusters/help @@ -27,6 +27,9 @@ COMMANDS list List workstation clusters. + update + Update a workstation cluster. + NOTES These variants are also available: diff --git a/gcloud/workstations/clusters/update b/gcloud/workstations/clusters/update new file mode 100644 index 000000000..b4f65b43a --- /dev/null +++ b/gcloud/workstations/clusters/update @@ -0,0 +1,110 @@ +NAME + gcloud workstations clusters update - update a workstation cluster + +SYNOPSIS + gcloud workstations clusters update (CLUSTER : --region=REGION) [--async] + [--display-name=DISPLAY_NAME] [--enable-http2] + [--update-labels=[KEY=VALUE,...]] + [--clear-labels | --remove-labels=[KEY,...]] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Update a workstation cluster. + +EXAMPLES + To update the display name of workstation cluster my-cluster in region + us-central1, run: + + $ gcloud workstations clusters update my-cluster \ + --region=us-central1 --display-name='My New Cluster Name' + +POSITIONAL ARGUMENTS + Cluster resource - Arguments and flags that specify the cluster 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 cluster on the command line with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + CLUSTER + ID of the cluster or fully qualified identifier for the cluster. + + To set the cluster attribute: + ▸ provide the argument cluster on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --region=REGION + The name of the region of the cluster. + + To set the region attribute: + ▸ provide the argument cluster on the command line with a fully + specified name; + ▸ provide the argument --region on the command line; + ▸ set the property workstations/region. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --display-name=DISPLAY_NAME + Human-readable name for this workstation cluster. + + --enable-http2 + Enable or disable HTTP/2 for the workstation cluster. + + --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 workstations clusters update --clear-labels + + To remove all existing labels and create two new labels, foo and baz: + + $ gcloud workstations clusters 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 workstations/v1 API. The full documentation for this + API can be found at: https://cloud.google.com/workstations + +NOTES + These variants are also available: + + $ gcloud alpha workstations clusters update + + $ gcloud beta workstations clusters update + diff --git a/gcloud/workstations/ssh b/gcloud/workstations/ssh index f577f7271..50ba1f4a0 100644 --- a/gcloud/workstations/ssh +++ b/gcloud/workstations/ssh @@ -6,7 +6,7 @@ SYNOPSIS (WORKSTATION : --cluster=CLUSTER --config=CONFIG --region=REGION) [--command=COMMAND] [--local-host-port=LOCAL_HOST_PORT; default="localhost:0"] - [--port=PORT; default=22] [--ssh-flag=SSH_FLAG] + [--port=PORT; default=22] [--ssh-flag=SSH_FLAG] [--start-workstation] [--user=USER; default="user"] [GCLOUD_WIDE_FLAG ...] [-- SSH_ARGS ...] DESCRIPTION @@ -113,6 +113,10 @@ FLAGS $ gcloud workstations ssh --ssh-flag="-vvv" \ --ssh-flag="-L 80:localhost:80" + --start-workstation + If set, automatically starts the workstation if it is currently + stopped. + --user=USER; default="user" The username with which to SSH. diff --git a/gcloud/workstations/start-tcp-tunnel b/gcloud/workstations/start-tcp-tunnel index f4b46f9ec..8a4f1ee14 100644 --- a/gcloud/workstations/start-tcp-tunnel +++ b/gcloud/workstations/start-tcp-tunnel @@ -7,7 +7,7 @@ SYNOPSIS (WORKSTATION : --cluster=CLUSTER --config=CONFIG --region=REGION) WORKSTATION_PORT [--local-host-port=LOCAL_HOST_PORT; default="localhost:0"] - [GCLOUD_WIDE_FLAG ...] + [--start-workstation] [GCLOUD_WIDE_FLAG ...] DESCRIPTION Start a tunnel through which a local process can forward TCP traffic to the @@ -87,6 +87,10 @@ FLAGS If LOCAL_PORT is 0, an arbitrary unused local port is chosen. + --start-workstation + If set, automatically starts the workstation if it is currently + stopped. + GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format,